David's Astronomy Pages Notes - Session 1336 (2025-06-26)

Notes (S1335)

Notes Main

Home Page

Notes (S1337)

	Session Aims & Highlights
	- Observing Result  - Night Summary Plot  - Session Event Log
	Operational Issues
	- Critical Issues (0),  Major Issues (2),  Minor Issues (4),  Small Defects (6),  Continuous Improvement (5)
	- Figures (2)
	Images from 2025-06-26  >>

Session Aims & Highlights (2025-06-26)

Main aims

1. Targets.  Acquire images of a selection of variable stars, nearby stars, comets & deep sky targets as allowed by sky conditions and the short summer night.

 Equipment & Software

• 12" LX200 and ST-10XME
• 80mm APO and ZWO ASI 178MC
• TheSky6, CCDSoft5, DeviceHub 7.0.3 RC3.4694, MeadeGeneric 1.3.12.522 , UPB 1.5,  Pulsar Dome Firmware 1.51 & Driver 6.3.10
• Pegasus UPB & Motor Focus, TCF-S 6.0.6
• SharpCap 3.2, PHD2  2.6.13, Siril 1.0.6, deCONZ 1.18.2, ASCOM 7.0.3 RC3
• [ DomeLink 1.0 / 1.1 - not used ]
   
• AstroMain 3.75.6,  AstroPlan 1.43.12, AstroShCap 1.3.15, AstroGuard 1.11  (any new items or versions in bold)
  AstroMag 1.5.2, AstroVOE 1.15.1,  AstroSN 1.14,  AstroProtect 1.10.6,  AstroMove 1.16
  AstroWeather 1.27.9, AstroAllSky 3.24.4,  AstroObsCam 1.11.4 (not 1.11.5), AstroNorthCam 1.5.3, AstroLaunch 1.13.3

Highlights

• Targets.  2/6 planned target observations were completed, with 1 targets partially completed. Other targets failed due to cloud or missed start.
• CCD Camera. There were some issues with the CCDSoft / CCDCamera during the session.
•  Dome. There was no issues opening/closing the shutter during the session. Dome closed and parked at end of session ok.

Notes

Summary Plots & Logs

Observing Plan

Observing Result

Dome & Scope Slewing Performance

Slew/Centering Performance

Guiding Performance

Sky Conditions (Locate Frames)

Night Sky Summary Plot Top axis: Sky Brightness at Zenith (in ADU/s) Lefthand axis: Local Time (hh LT). Righthand axis: Sun Altitude (degs) Note:  The NorthCam Star Count line is unreliable and should be ignored (The AstroNorthCam 'Find' Star method is producing many false positives from clouds)

Actual Weather vs Pre-Session Weather Forecast

Session Event Log

Time     Event Detail 00:05:15 Session Monitoring AutoStart monitoring for Live Session opportunity between 00:05 & 01:17 00:05:16 Session AutoStarting Session autostarting (00:05) 00:05:37   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.) 00:06:04   Camera1 Connected SBIG Camera connected (Set point -5°C) 00:06:07 Session Created Session Created (Live, 2025-06-26 S01336, ImageSaveNum: 1336001) 00:06:13   Scope Switched On Telescope Power has been switched on via UPB Switch 00:08:03   Services Started Observatory Services started 00:08:15 Observatory (Auto) Observatory placed in Fully-Automated Mode 00:08:18 Session Pending Session pending (2025-06-26) 00:08:20 Session Initiating Session initiating (2025-06-26) 00:08:28   Camera1 Connected SBIG Camera connected (Set point -10°C) 00:08:34   Plan Requested Observing Plan requested from AstroPlan (1.43.12) 00:10:54   Plan Loaded Observing Plan loaded to queue (Plan ID: 1121) 00:11:36   Telescope Connected Telescope connected (TheSky6) 00:12:01 Session Equilibration Session ready to Open Dome 00:12:47   Dome Opened Dome opened (Opening time 46s, Zigbee 41s) 00:12:52   Equilibration Started Dome Equilibration started 00:16:37   Equilibration Skipped Dome Equilibration skipped by user 00:16:39 Session Running Session running 00:16:42   Queue Started Observing Queue started (6 targets selected) 00:16:43     Target Started (NrZen) Target started (Focus Field 17, HIP 83575) 00:16:58       Dome Unparked Dome unparked 00:20:02       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (reducing clarity) 00:20:05   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 00:20:07   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 00:20:09     Target Aborted (NrZen) Target aborted (Focus Field 17, HIP 83575) due to cloud 00:20:10   Queue Paused Observing Queue pausing for Session Suspension 00:20:14 Session Suspending Session suspending 00:21:03   Dome Closed Dome closed (Closing time 49s, Zigbee 44s) 00:21:07 Session Suspended Session suspended 00:27:29 Session Resuming Session resuming 00:28:14   Dome Opened Dome opened (Opening time 45s, Zigbee 41s) 00:28:17 Session Running Session running 00:28:20   Queue Resumed Observing Queue resumed 00:28:22     Target Started (1/6) Target started (1/6, GCVS CY Lyr) 00:31:33       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 00:33:23       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:33:38         CcdCamera Frozen CcdCamera appears to be frozen at around 00:33 in section 'GetCameraProperties / FilterIndexZeroBased' 00:34:10         CCDSoft Restarting CCDSoft being restarted (attempt to fix frozen CcdCamera) 00:34:17         SBIG Camera Reset SBIG Camera being power-cycled 00:35:12         Camera1 Connected SBIG Camera connected (Set point -10°C) 00:35:28         SBIG Camera Take Image failed (Command timed-out) 00:35:30         CCDSoft Restarting CCDSoft being restarted (attempt to fix frozen CcdCamera) 00:35:37         SBIG Camera Reset SBIG Camera being power-cycled 00:36:29         Camera1 Connected SBIG Camera connected (Set point -10°C) 00:36:38         SBIG Camera Take Image successfully completed (earlier flags are reset) 00:39:36       Focusing Completed Foc1 AutoFocus Completed (Profile No 1, wide) 00:42:07       Focusing Completed Foc1 AutoFocus Completed (Profile No 1) 00:45:00     Target Completed Target partially completed (1/6, GCVS CY Lyr) 00:45:05     Target Started (2/6) Target started (2/6, AT2025lc (CV)) 00:54:46     Target Completed Target completed (2/6, AT2025lc (CV)) 00:54:50     Target Started (3/6) Target started (3/6, T CrB) 01:06:00     Target Completed Target completed (3/6, T CrB) 01:06:05     Target Started (4/6) Target started (4/6, AT2025kej (CV)) 01:09:58       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (reducing clarity) 01:10:00   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 01:10:02   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 01:10:09       SoftSuspend Cancelled Soft Suspend is cancelled due to improved conditions 01:10:11     Target Aborted (4/6) Target aborted (4/6, AT2025kej (CV)) due to cloud 01:10:13   Queue Paused Queue paused for Session Suspension 01:10:16 Session Suspending Session suspending 01:11:05   Dome Closed Dome closed (Closing time 51s, Zigbee 44s) 01:11:08 Session Suspended Session suspended 01:16:52     Target Cancelled Target cancelled (4/6, AT2025kej (CV)) due to cloud 01:22:26 Session Resuming Session resuming 01:23:10   Dome Opened Dome opened (Opening time 44s, Zigbee 40s) 01:23:12     Target Started (NrZen) Target started (Focus Field 19, HIP 93376) 01:23:15 Session Running Session running 01:23:17   Queue Resumed Observing Queue resumed 01:26:40       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (reducing clarity) 01:27:15       SoftSuspend Cancelled Soft Suspend is cancelled due to improved conditions 01:27:20       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:29:44         SBIG Camera Take Image failed (Command timed-out) 01:29:46         CCDSoft Restarting CCDSoft being restarted (attempt to fix frozen CcdCamera) 01:29:53         SBIG Camera Reset SBIG Camera being power-cycled 01:30:45         Camera1 Connected SBIG Camera connected (Set point -10°C) 01:30:55         SBIG Camera Take Image successfully completed (earlier flags are reset) 01:31:15       Focusing Completed Foc1 AutoFocus Completed (Profile No 2) 01:31:18       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 01:33:31       Focusing Failed Foc2 focusing failed (failed QC check - Range) 01:33:35     Target Completed (NrZen) Target completed (Focus Field 19, HIP 93376) 01:33:37     Target Missed (5/6) Target's time slot was missed (5/6, 61 Cyg) 01:33:40     Target Started (6/6) Target started (6/6, GCVS CI Cyg) 01:37:31   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 01:37:33   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 01:37:49     Target Aborted (6/6) Target aborted (6/6, GCVS CI Cyg) due to cloud 01:37:51   Queue Paused Queue paused for Session Suspension 01:37:54 Session Suspending Session suspending 01:38:44   Dome Closed Dome closed (Closing time 52s, Zigbee 43s) 01:38:47 Session Suspended Session suspended 01:45:47     Target Cancelled Target cancelled (6/6, GCVS CI Cyg) due to cloud 01:45:51   Queue Completed Job Queue completed 01:46:04 Session Closing Session closing 01:46:09   Dome Closed Dome already closed (closed at 01:38, closing time 52s, zigbee 43s) 01:46:50   Dome Parked Dome parked (parking time 31s), Az: 90.0 deg 01:47:52   Telescope Parked Telescope parked (parking time 49s total) 01:48:16   Telescope State Handbox reads 'Scope parked Turn scope off.' 01:49:13   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 01:50:36   Services Stopped Night Services stopped 01:50:39 Session Finishing Session Finishing started (Create Fits Summary, Transfer Files) 01:50:46     Dome (Find Park) Find Park started (Search Az 88.0 to 92.0°, Step 0.2°, Narrow) 01:51:32     Dome Find Park found (Best Park Az 90.2°) 01:51:38     Dome Dome has been synced at park position (Az 90.0°, Adjustment: -0.2°) 01:51:40   Dome Parked Dome parked 01:51:59   Dome Charging Dome is parked and re-charging Ok (20mA) 01:52:01 Session Finished Session Finished

Session Alerts & Alarms

Time     Type       Name Detail 00:34:08 Red Alert CcdCamera CcdCamera appears to be frozen (last cycle at 00:33:38) in section 'GetCameraProperties / FilterIndexZeroBased' 00:35:12 Green Clear CcdCamera SBIG Camera has been successfully restarted 00:35:28 Red Alert SBIG Camera Alert Take Image failed (Command timed-out) 00:36:39 Green Clear SBIG Camera Take Image successfully completed (earlier flags are reset) 01:29:44 Red Alert SBIG Camera Alert Take Image failed (Command timed-out) 01:30:55 Green Clear SBIG Camera Take Image successfully completed (earlier flags are reset) 01:51:59 Green Clear Dome Charging Dome is parked and re-charging Ok (20mA)

Back to Top

Operational Issues (2025-06-26, S1336)

• Critical Issues (0)
• Major Issues (2)
• Minor Issues (4)
• Small Defects (6)
• Continuous Improvement (5)
• Figures (2)
  

[ Prev | Next ]

Critical Issues

• None

Major Issues

• 'AutoStart' failed due to Camera Issue and Session Mode returned to Manual (23:54). After setting Observatory to Autostart at 22:54, conditions became suitable for starting the observing session at 23:54, but during the initial CCD Check there was a problem connecting to the CCD Camera and alert raised with the reported error "SBIG Driver: Device not found". The Autostart routine made an attempt to RestartCCDSoft (including Camera restart) but the camera connection again failed with same error at 23:55.  As a result Autostart was aborted and the Observatory was returned to Manual Mode. After spotting the issue the a user intervention was made at 00:04 to manually initiate a further RestartCCDSoft() operation (which was successful) and again move the Observatory to Autostart Mode at 00:05.  The issue is ranked as 'Major' since without user intervention the Session will have failed and no targets will have been observed.  Given that the manually initiated RestartedCCDSoft() operation worked and allowed connection to the CCD Camera it suggests that AutoStart should have made more effort to restart the Camera before giving up.  Fixed made to AstroMain 3.75.7. The AutoStartSession() has been modified to make up to 3 attempts to call RestartCCDSoft() in an attempt to resolve camera issue.
   Fixed 2025-06-27 (AstroMain 3.75.7)
   
• AllSky/Weather Computer 'crashed' and can't be turned on again (2025-06-29). The AllSky/Weather Computer has seemingly crashed around 20:32. Visit made to Observatory at 23:50.  Attempted to restart computer but it wouldn't start at all.  The consequential missing Weather/Cloud Sensor data prevents running a live session on the Observatory Computer.  Computer was checked again the following day, and it was again difficult to turn on the computer. Pushing the computer's power button didn't work, reseating the power lead and pushing power button didn't work.  Finally the A/C Adapter was unplugged/replugged and and this time pushing the power button worked. Relief !!. 
   Resolved 2025-06-29 (AllSky/Weather Computer)

Minor Issues

• A CCDSoft warning dialog was unexpectedly shown with the message "You are about to start another instance of CCDSoft (23:55 ?, 00:34 ?).  During operations a CCDSoft warning dialog was unexpectedly shown with the message "You are about to start another instance of CCDSoft. Are you sure you want to continue?". The precise point when this occured is somewhat uncertain. User intervened to dismiss/cancel the starting of a second instance (unfortunately without capturing the rough time & context of the message, a screen shot should have been captured by the user).  The same issue occured on two ocassions during the following S1337 Session (2025-06-29) - see details.  Ticket was closed after initial review on 2025-05-27 due to insufficient information to fully diagnose the issue, but reopened on 2026-05-30 in order to examine new evidence from the S1337 Session..   Fix attempted in AstroMain 3.75.9 .  Foc2 Focusing now enters a wait loop if RestartCCDSoft is in progress. RestartCCDSoft to not be called if Foc2 Focusing is in progress.(indicated by new  bRunningAutoFocusScope2  flag)
   Fix attempted 2025-07-01 (AstroMain 3.75.9)
   
• CCDCamera froze during Focus Frame 1/23 from Target 1/6 (00:33).  After Near Zenith Focus operation was aborted after  to being unable to link four Locate Frames due to cloud, and a short session suspension execution, execution resumed with Target 1/6 (CY Lyr). After successfully centered the target, Foc1 (Wide) focusing was started and a Focus Locate Frame was successfully taken, but during Focus Frame 1/23  the CCDCamera became frozn in section section 'GetCameraProperties / FilterIndexZeroBased.  (Red Alert at 00:34:08).  A RestartCCDSoft() operation was initiated (presumably by the Job Executor).  Even though Camera Connection appeared to be successfully made, the following Focus Frame 2/23 also failed due to Frozen CCDCamera (Red Alert at 00:35:28). and a further RestartCCDSoft() operation was made.  This was successfully and the remaining Focus Frames, beginning with Frame 2/23*,  were all successfully taken. Again it is unclear why CCDCamera became frozen.  Logs show that CCDCamera was evidentally having GetProperty State / GetProperty  GetFilterIndexZeroBased timeouts from around 00:33:38 (whilst Focuser movement to 1st point was being conducted) and CCDcamera was already pending for around 20s when the call to CCDCamera.TakeImage was made at 00:33:58.  Since AstroMain automatically resolved issue and the Focusing was successfully performed this instance of this ongoing problem is closed after review 2025-06-27. A separate Continuous Improvement ticket is added to review whether TakeImage should be allowed to be called with a CCDCamera is a Pending State.
   Closed after review 2025-06-27 (Session, CCDSoft,  AstroMain)
   
• CCDCamera froze during Focus Frame 13/14 from Target 5/6 (01:29).  After starting a Foc1 Focus Profile for Target 5/6 (61 Cyg), Focus Frame 13/14 failed due to Frozen CCDcamera, with a Red Alert raised at 01:29:44 . The routine called RestartCCDSoft() which seemed to resolve the problem and Focus Frame 13/14* and 14/14 were successfully acquired. Logs show that CCDCamera became frozen after the call to TakeImage().   Since AstroMain automatically resolved issue and the Focusing was successfully performed this instance of this ongoing problem is closed after review 2025-06-27.
   Closed after review 2025-06-27 (Session, CCDSoft,  AstroMain)
   
• SAM III Y readings showed unacceptable spikes & shifts in value (2025-06-26 21:00). Coming just 4.4 days after Remedial Fix 2 ( see Geomagnetic Station -  Remedial Fix 2, grounding unused wires (2025-05-22) ) there was a significant spikes and shift in Y reading of around +570 nT at around 21:00.  (see Fig 1).  This was disappointing outcome.  Proposal is to make Remedial Fix 2b in order to replace the 1M ohm inline resistor used in the fix with one of much lower value (around 100-200 ohm). Problems continued on 2025-06-27 through to 2025-06-29 (see Fig 2) with spikes/shifts up to 3400-4500 nT and as a result Remedial Fix 2b was carried out 2025-06-29 in order to use a lower valued resistor.  A 100-200 ohm resistor wasn't to hand and a 330 ohm resistor was used instead. 
   Fix attempted  2025-06-29 (SAM III, Geomagnetic Station, Remedial  Fix)

Small Defects

• A blank line isn't being placed between 'Planned Targets' table and the the "See Targets of Opportunity" report line (00:11). At the end of the 'Session Initiating' stage and after loading the observing plan AstroMain reports a table of Planned Targets.  A blank line should then appear before the final line  "See Targets of Opportunity  "ToO's acquired will be listed near end of report".  Whilst the code shows a 'ReportComment("")' line before the final  ReportLink() line, the blank line isn't shown.  Unclear why the blank line isn't being shown.  Workaround attempted by added an additional code line 'ReportComment(Tab2)'. Fixed attempted in AstroMain 3.75.7.  Check outcome in next session.
   Fixed 2025-06-27 (AstroMain 3.75.7)
   
• Target name "FocusField 19" was reset to "Running" (01:23).  After conditions improved following a short suspension, the session state moved to 'Resuming Session' and the Dome opened at 01:23, and Job Executor chose to Insert Near Zenith Focusing (as this had failed at the start of the session due to Conditions). The NearZenithFocusing selected 'Focus Field 19' as the optimal focus field, and szTargetName was set to 'Focus Field 19' as shown by a series of log messages at 01:23:10 to 01:23:11 .Session State moved to 'Running Again'  and szTargetName was set to 'Running' overriding the 'Focus Field 19' name.  Target name remained as "Running"  throughout the Focus Field task,  JPG pictures were named "Running".  Job Queue executor has code to reset szTargetName after session is running again, but the FocusScopeNearZenith() routine evidentally doesn't.  Examination of ExecuteQueue() routine shows two places where FocusScopeNearZenith(CallMode.Auto) can be called, one of then is when Session is running, but the other one is potentially where Session is still suspended or resuming again.  Fixed in AstroMain 3.75.7 , the code for the latter case is deactivated.
   Fixed 2025-06-27 (AstroMain 3.75.7)
   
• ObsPic and GreenhousePic are showing inappropriate flags for Weather Station and CloudSensor data (2025-06-29). With AllSky/Weather Computer out of action it exposes a number of issues with ObsPic & GreenhousePic pictures. In particular ObsPic and GreenhousePic show green flags against Light, Clarity & Rain, a red flag against ObsT, a green flag & 0% against ObsH and a green flag and 0.0 mph against Wind.   The Manager Tab shows  Green Flag against Rain Forecast and Precip. Next 15 mins' . White Flags shown be displayed when data from AllSky/Weather Computer is not available.   Fixes made to AstroMain 3.75.7.  Initialise Synopsis.Valid to false in StartListening.
   Fixed 2025-06-29 (AstroMain 3.75.7)
   
• A Start Focus Point was logged whilst RestartCCDSoft was being run. "Start Focus Point 2/23" was logged whilst RestartCCDSoft() was running.  A check / wait loop should be placed before starting a new Focus Point.
   Fixed 2025-06-29 (AstroMain 3.75.7)
   
• AstroMain is logging Laptop7 Ping Request exceptions every 5s (2025-06-28).  Due to the AllSky/Weather Computer being down, AstroMain's 'Check Network_Laptop9' is given an exception every 5s with message "an exception occurred during  a Ping request". logfile contained 8293 logged exceptions.  The number of exception logged should be reduced to a manageable number.  Fixed in AstroMain 3.75.7, so that logging of exception is limited to 1 every 5 minutes.
   Fixed 2025-06-29+ (AstroMain 3.75.8)
   
• TheSky.Telescope.IsConnected function is sometimes taking up to 6 - 10s to return a result (2025-06-29).  Log messages that are inserted into RunTheSkyScopeMonitor() routine to trace certain operations are reporting that  'Get Telescope.IsConnected' is sometimes taking some 6 - 10s to return a True/False result.  It is unclear why it should take this long, when the Telescope is clearly not connected.  The logfile for 2025-06-29 contains 518 occurances of log message up until 22:30. Tracing added to 3.75.8 to understand what the normal time is for making this function call.  Results from a general session (2025-07-01) show that the function is normally recorded as taking 0.0s,  and it will sometimes  take 1-12s which doesn' trigger a warning, occasionally (when time is 15s or more) it will trigger a 'ScopeMonitor is Pending' message but the ScopeMonitor then typically resumes after 16-19s.  The traces of a pattern can sometimes be seen. Occasionally the ScopeMonitor will be pending for up to 40s and sometimes up to 90s of which there was just a single instance in the 2025-07-01 log file. Temporary trace logging removed 2025-07-02.  "Resume ScopeMonitor  Info" changed to "Check  ScopeMonitor Ok" . A possible relationship between TheSkyScopeMonitor holds up and Image Failure/CCDCamera freezes has been noticed and the active part of TheSkyScopeMonitor was temporarily commented out in code for daytime testing following session S1338A (2025-07-02).  More recently (2025-07-05 AstroMain 3.75.11) TheSkyScopeMonitor has been reinstated with a user controlled checkbox allowing the active part of the monitoring loop (involving the call to Telescope.IsConnected) to be disabled or re-enabled.  Propose to monitor the performance of TheSkyScopeMonitor in view of the changes made to CCDCamera/DrawObservatoryPicture().
   To monitor 2025-06-29+ (AstroMain 3.75.9)

Continuous Improvement

• Log files from 'General' Sessions to be finalised just before Session progresses to next date. It will be sometime handy to have general session log files available in htm format.  Implemented in AstroMain 3.75.7.   FinaliseLogFile() is called in ProgressSessionDate() routine before calling AssignObservatorySession().
   Done 2025-06-27 (AstroMain 3.75.7)
   
• Modify AstroMain's CopyGeneralFiles() routine to also copy '(log).htm' and (log_trace).htm' files. AstroMain 3.75.7 has been extended to finalise log files before progressing to a new session date.  AstroMove should be extended to include copying of 'Observatory (log).htm' and 'Observatory (log-trace).htm' files. Implemented in AstroMove 1.10.1.  Note that these files are not created until c. 09:00 which is after Session files would normally be copied from the Obseravtory, but these .htm files will nevertheless be available if session file transfer is delayed till after 09:00 or is manually transferred across.
   Done 2025-06-27 (AstroMove 1.10.1)
   
• Make further changes/improvements to AstroMain Session Logs. Continue with project started in AstroMain 3.75.5/3.75.6 (CI S1335) to improve the logging of records/messages to Session Log File, including
  - added log line before Starting ConvertFitsToJpg
  - tidied up "Get", "Log" statements
  - changed "Setting GuideCam", "Created GuideCam object" &  "By passing Garbage Collection"  lines to '(trace)' statements
  - added log line before "Start  Foc1Profile"
  - added "Wide" suffix to "Start Foc1Profile" & "Measure FocProfile"
  - shortened "FocusScopeNearZenith" to "FocusNearZenith"
  - added List to COM Ports, Program Versions, Zigbee Network
  - added "(warn)", "(error)",  "(alert)" , "(fail)" verbs
   Done 2025-07-05 (AstroMain 3.75.7 to AstroMain 3.75.11)
   
• Add Background Colours to Finalised Log Files.   Log tags were introduced in AstroMain 3.75.7, such as "(warn)", '"(error)", "(trace)" can be used to present colour coded log message lines in .htm files generated by FinalisedLogFiles() routine . Implemented in AstroMain 3.75.9
     (error) : Red
   (fail) : Red
   (warn) : DarkOrange
   (trace) : Gray
   (event) : Blue
  Done 2025-067-05 (AstroMain 3.75.11)
   
• Prevent calling CcdCamera.TakeImageAsync() when CCDCamera is in a Pending state. During the S1336 session,  Focus Frame 1/23 for Target 1/6 (CY Lyr) failed due to a frozen CCDCamera.  Logs show that CCDCamera was evidentally having GetProperty State / GetProperty  GetFilterIndexZeroBased timeouts from around 00:33:38 (whilst Focuser movement to 1st point was being conducted) and CCDcamera was already pending for around 20s when the call to CCDCamera.TakeImage was made at 00:33:58.  Review should look at the introducing code to recognise this situation and preemptively call RestartCCDSoft() before repeating the call to CCDCamera.TakeImage.  The matter was previously raised in Nov 2024 (CI S1030).  The problem with simply repeating the call to CCDCamera.TakeImage is that CCDSoft will have lost all image specification (binning, exposure, filter, subframe etc)  when it was killed/restarted.  This would require TakeImageASync to be able to access the entire specification and set up all relevant parameters in CCDSoft's Camera Object. (ObsOverseer sets  bCcdMonitorCycleIsPending = True when it is stalled and this flag can be checked by TakeImageAsync (). Improvement implemented in AstroMain 3.75.11
  Done 2025-07-05 (AstroMain 3.75.11)

[ Prev | Next ]

Back to Top Issue,  Back to Top

[ Prev | Next ]

Back to Top Issue,  Back to Top