David's Astronomy Pages Notes - Session 1345 (2025-08-02)

Notes (S1344)

Notes Main

Home Page

Notes (S1346)

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

Session Aims & Highlights (2025-08-02)

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.
2. Cam2 Camera Angle & TS80 alignment. Rotate guidescope camera to 0.0° position. Align TS80 guide scope pointing with that of the LX200 main scope.

 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.77.5,  AstroPlan 1.43.12, AstroShCap 1.3.15, AstroGuard 1.11  (any new items or versions in bold)
  AstroMag 1.5.8, AstroVOE 1.15.1,  AstroSN 1.14,  AstroProtect 1.10.6,  AstroMove 1.16.2
  AstroWeather 1.27.9, AstroAllSky 3.24.4,  AstroObsCam 1.11.4 (not 1.11.5), AstroNorthCam 1.5.3, AstroLaunch 1.13.6

Highlights

• Targets.  7/16 planned  targets were completed with 2 targets partially completed. Other targets failed due to cloud/rain & session suspension.
• CCD Camera.  No issues with CCD Camera during session.
• Observatory Protection. Automated protection ensured that Dome's shutter was closed ahead of a heavy rain shower at around 02:00.
  Cam2 Camera Angle & TS80 Alignment .  There was no opportunity to rotate the ZWO 178MC cameras to the target correct angles (0.0°) before the session began. The camera angles during S1343 was previously measured to be around 358.0° (ie -2.0°) which is tolerable in the short-term. The total TS80 alignment error was previously determined to be 1.61'  (Offset W -1.60', Offset N: -0.17') . Similarily there was no opportunity to improvethe alignment. These two objectives will roll forward to the next 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 22:37:39 Session Monitoring AutoStart monitoring for Live Session opportunity between 22:37 & 03:01 22:37:40 Session AutoStarting Session autostarting (22:37) 22:37:53   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.) 22:38:08 Session Created Session Created (Live, 2025-08-02 S01345, ImageSaveNum: 1345001) 22:38:15   Scope Switched On Telescope Power has been switched on via UPB Switch 22:40:01   Services Started Observatory Services started 22:40:12 Observatory (Auto) Observatory placed in Fully-Automated Mode 22:40:16 Session Pending Session pending (2025-08-02) 22:40:18 Session Initiating Session initiating (2025-08-02) 22:40:37   Camera1 Connected SBIG Camera connected (Set point -10°C) 22:40:39   Plan Requested Observing Plan requested from AstroPlan (1.43.14) 22:41:45   Plan Loaded Observing Plan loaded to queue (Plan ID: 1130) 22:42:26   Telescope Connected Telescope connected (TheSky6) 22:42:50 Session Equilibration Session ready to Open Dome 22:43:41   Wait On Weather Waiting for acceptable conditions 22:43:43 Session Suspending Session suspending 22:43:45   Dome Closed Dome already closed 22:43:47 Session Suspended Session suspended 22:44:13   Queue Started Observing Queue started (16 targets selected) 22:45:46 Session Resuming Session resuming 22:46:31   Dome Opened Dome opened (Opening time 45s, Zigbee 40s) 22:46:33 Session Running Session running 22:46:35   Queue Resumed Observing Queue resumed 22:46:37     Target Started (1/16) Target started (1/16, 2MFGC 13744 w/SN2024afyu) 22:46:49       Dome Unparked Dome unparked 22:49:39       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 22:51:30       Focusing Completed Foc2 AutoFocus Completed (Profile No 1, wide) 22:53:08       Focusing Completed Foc2 AutoFocus Completed (Profile No 1) 22:55:27       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 22:58:25       Focusing Completed Foc1 AutoFocus Completed (Profile No 2, wide) 23:01:19       Focusing Completed Foc1 AutoFocus Completed (Profile No 2) 23:17:18     Target Completed Target completed (1/16, 2MFGC 13744 w/SN2024afyu) 23:19:27     Target Started (2/16) Target started (2/16, GCVS CY Lyr) 23:22:33       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:24:32       Focusing Completed Foc1 AutoFocus Completed (Profile No 3) 23:28:19     Target Completed Target completed (2/16, GCVS CY Lyr) 23:29:45     Target Started (3/16) Target started (3/16, AT2024aane) 23:34:33       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:37:27       Focusing Completed Foc1 AutoFocus Completed (Profile No 4) 23:53:59     Target Completed Target completed (3/16, AT2024aane) 23:54:03     Target Started (4/16) Target started (4/16, AT2024wzq (CV)) 23:57:28       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:59:41       Focusing Completed Foc1 AutoFocus Completed (Profile No 5) 00:05:39     Target Completed Target completed (4/16, AT2024wzq (CV)) 00:05:43     Target Started (5/16) Target started (5/16, UGC 10058 w/SN2025gvs) 00:09:08       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:11:41       Focusing Completed Foc1 AutoFocus Completed (Profile No 6) 00:27:56     Target Completed Target completed (5/16, UGC 10058 w/SN2025gvs) 00:28:00     Target Started (6/16) Target started (6/16, T CrB) 00:31:18       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:33:32       Focusing Completed Foc1 AutoFocus Completed (Profile No 7) 00:37:37     Target Completed Target completed (6/16, T CrB) 00:37:42     Target Started (7/16) Target started (7/16, GCVS BL Lac) 00:41:27       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:43:35       Focusing Completed Foc1 AutoFocus Completed (Profile No 8) 00:47:22     Target Completed Target completed (7/16, GCVS BL Lac) 00:47:59     Target Started (8/16) Target started (8/16, UGC 386 w/SN2025kno) 00:52:03       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:54:27       Focusing Completed Foc1 AutoFocus Completed (Profile No 9) 01:05:36   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 01:05:38   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 01:05:40     Target Aborted (8/16) Target aborted (8/16, UGC 386 w/SN2025kno) due to cloud 01:05:42   Queue Paused Queue paused for Session Suspension 01:05:44 Session Suspending Session suspending 01:06:31   Dome Closed Dome closed (Closing time 50s, Zigbee 43s) 01:06:33 Session Suspended Session suspended 01:07:15     Target Cancelled Target cancelled (8/16, UGC 386 w/SN2025kno) due to cloud 01:09:26 Session Resuming Session resuming 01:10:11   Dome Opened Dome opened (Opening time 45s, Zigbee 40s) 01:10:13 Session Running Session running 01:10:15   Queue Resumed Observing Queue resumed 01:10:18     Target Started (9/16) Target started (9/16, NGC 7331 w/SN2025rbs) 01:11:21   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 01:11:23   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 01:11:25     Target Aborted (9/16) Target aborted (9/16, NGC 7331 w/SN2025rbs) due to cloud 01:11:27   Queue Paused Queue paused for Session Suspension 01:11:29 Session Suspending Session suspending 01:12:11   Dome Closed Dome closed (Closing time 45s, Zigbee 43s) 01:12:14 Session Suspended Session suspended 01:15:32 Session Resuming Session resuming 01:16:17   Dome Opened Dome opened (Opening time 45s, Zigbee 40s) 01:16:19 Session Running Session running 01:16:21   Queue Resumed Observing Queue resumed 01:16:24     Target Started (9/16) Target started (9/16, NGC 7331 w/SN2025rbs) 01:18:07   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 01:18:09   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 01:18:11     Target Aborted (9/16) Target aborted (9/16, NGC 7331 w/SN2025rbs) due to cloud 01:18:13   Queue Paused Queue paused for Session Suspension 01:18:15 Session Suspending Session suspending 01:18:57   Dome Closed Dome closed (Closing time 45s, Zigbee 43s) 01:18:59 Session Suspended Session suspended 01:21:02 Session Resuming Session resuming 01:21:47   Dome Opened Dome opened (Opening time 45s, Zigbee 40s) 01:21:49 Session Running Session running 01:21:51   Queue Resumed Observing Queue resumed 01:21:54     Target Started (9/16) Target started (9/16, NGC 7331 w/SN2025rbs) 01:36:17     Target Completed Target partially completed (9/16, NGC 7331 w/SN2025rbs) 01:36:21     Target Started (10/16) Target started (10/16, C/2022 E2 (ATLAS)) 01:39:46       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:40:29   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 01:40:31   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 01:40:33       Focusing Aborted Foc1 Focusing Aborted 01:40:35     Target Aborted (10/16) Target aborted (10/16, C/2022 E2 (ATLAS)) due to cloud 01:40:37   Queue Paused Queue paused for Session Suspension 01:40:39 Session Suspending Session suspending 01:41:24   Dome Closed Dome closed (Closing time 49s, Zigbee 43s) 01:41:27 Session Suspended Session suspended 01:44:05 Session Resuming Session resuming 01:44:50   Dome Opened Dome opened (Opening time 45s, Zigbee 40s) 01:44:52 Session Running Session running 01:44:54   Queue Resumed Observing Queue resumed 01:44:57     Target Started (10/16) Target started (10/16, C/2022 E2 (ATLAS)) 01:45:29   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 01:45:31   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 01:45:41     Target Aborted (10/16) Target aborted (10/16, C/2022 E2 (ATLAS)) due to cloud 01:45:43   Queue Paused Queue paused for Session Suspension 01:45:45 Session Suspending Session suspending 01:46:35   Dome Closed Dome closed (Closing time 50s, Zigbee 43s) 01:46:37 Session Suspended Session suspended 02:00:25     Target Cancelled Target cancelled (11/16, AT2023cuz) due to cloud 02:20:55     Target Cancelled Target cancelled (12/16, UGC 1179 w/AT2025kuz) due to rain 02:43:15     Target Cancelled Target cancelled (13/16, UGC 1814 w/SN2025oas) due to cloud 03:05:15     Target Cancelled Target cancelled (14/16, NGC 7753 w/SN2025kyg) due to rain 03:16:38     Target Cancelled Target cancelled (15/16, WDS GRB 34) due to cloud 03:34:55     Target Cancelled Target cancelled (16/16, GCVS HH And) due to cloud 03:34:59   Queue Completed Job Queue completed 03:35:01 Session Closing Session closing 03:35:07   Dome Closed Dome already closed (closed at 01:46, closing time 50s, zigbee 43s) 03:35:27   Dome Parked Dome parked (parking time 12s), Az: 90.0 deg 03:36:17   Telescope Parked Telescope parked (parking time 45s total) 03:36:41   Telescope State Handbox reads 'Scope parked Turn scope off.' 03:37:03   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 03:38:29   Services Stopped Night Services stopped 03:38:32 Session Finishing Session Finishing started (Create Fits Summary, Transfer Files) 03:38:44     Dome (Find Park) Find Park started (Search Az 88.0 to 92.0°, Step 0.2°, Narrow) 03:39:28     Dome Find Park found (Best Park Az 90.1°) 03:39:34     Dome Dome has been synced at park position (Az 90.0°, Adjustment: -0.1°) 03:39:36   Dome Parked Dome parked 03:41:32   Dome Charging Dome is parked and re-charging Ok (56mA) 03:41:34 Session Finished Session Finished

Session Alerts & Alarms

Time     Type       Name Detail 03:41:32 Green Clear Dome Charging Dome is parked and re-charging Ok (56mA)

Back to Top

Operational Issues (2025-08-02 S1345)

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

Critical Issues

• None

Major Issues

• UPB V3 Unity & TCF-LSI focuser connections affected after Power Cut (2025-08-04 19:02). There was a power outage associated with Storm Floris at 18:29 than lasted until 19:02 (an outage of 32.8 mins).  Later in the evening it was noticed that fresh OTA temperature data wasn't being graphed by AstroWeather.  Investigating showed that the were multiple failed attempts to connect to the TCF Focuser (RPC errors), since the power had been restored at 19:02).  Pegasus Unity UI was also showing an exception message or notifcation (unfortunately this wasn't captured). Observatory Services were restarted  in AstroMain but this produced Powerbox Connection failures.  Upon reopening Pegasus Unity UI (Frontend),  it was noticed that it wasn't able to connect to the UPB V3 box.  The TCF-LSI connection errors continued under 00:38 when after failing to resolve the situation by the user including Restarting AstroMain it was decided to turned off the TCF Focuser service until things could be investifgated the next morning.  Unclear what the issue was it was proposed to reboot the UPB V3 powerbox (by means of a power reset), but this wasn't feasible until the morning during to the continuing storm.  Before performing this reset it was decided to try restarting the Observatory Computer to see if that might resolve the issue.  Indeed it did - upon re-opening the Pegasus Unity UI (Frontend) the UPB V3 box was found to connect ok, and after this Observatory Software including AstroMain was reopened and showed no issue in connecting to powerbox and connecting to the TCF-LSI focuser.  Reviewing logs later showed that the ObsManager commenced Power Outage Management after the power cut began at 18:29:14 and proceeded to turned off dew-heaters & CCD Cooling (at T+ 2 mins), turned off CCD Camera and TCF-LSI focuser (at T+ 8 mins). Later on it  began Power Outage Recovery steps after the main power was restored at 19:02:06.   Issue resolved but several side-issues & defects have been recorded under separate tickets. A separate Continuous Improvement ticket is raised to check Pegasus UPB, TCF-LSI,  Zigbee Service & ObsViewer following completion of all related tickets.
  Resolved  2025-08-05 (UPB Powerbox,  TCF-LSI focuer, Power Outage)

Minor Issues

• AllSky/Weather Computer running short of disk space (2025-08-04). Disk space on C Drive and G Drive is down to around 10 GB, AllSky Sessions remaining on C Drive, due to lack of space on G Driver.  Files reduced on G (Archive) Drives and Sessions from last 7-8 days have archived.  .Free file space on C & G Drives is back up to 50 GB and 180 GB respectively.  A further thinning of files will be required before long.
  Resolved 2025-08-03 (AllSky/Weather Computer)
   
• Zigbee Network Report during Outage Management Stage 6 (recovery) showed that all Smart Plugs & Devices were unavailable (2025-08-04  19:02:28). There was a power outage associated with Storm Floris at 18:29 than lasted until 19:02:06 (an outage of 32.8 mins). After mains power was restored at 19:02:06 AstroMain's Power Outage Management entered Stage 6 (recovery) at  19:02:26.08, and proceeded to restart Zigbee Service at 19:02:02:26.12 to 19:02:02:26.63.(T+20s)  This was around the time that Network Connection to Laptop 7 resumed,  but before Network Connection to the Router has been restored (which was still giving exceptions to ping requests).  The Zigbee Network was then reported as 19:02:70  but all Smart Plugs and Sensors were reported as 'not found' with the error messages "Unable to connect to the remote server".  An attempt to reconnect to the SBIG CCD Camera  ("CCDSoft being restarted (recovery following mains outage)" was made at 19:02:30 but failed with TurnOff/TurnON SBIG Camera giving the the message "SBIG Camera is not reachable" .  The LAN/Router Connection resumed at 19:02:56 (this is 50s after power resumed). During the power outage changes to sensor values were being recieved ok according to log file, suggesting that the Zigbee Server was likely still running ok. It is thought that the recovery routine didn't need to restart the Zigbee  Network after the outage finished, and in any case shouldn't have restarted the Zigbee Service & reported it before the LAN had successfully resumed.  A separate Continuous Improvement ticket is raised to make the ObsOverseer to check Zigbee Service and automatically restart it if it has been down for some time. AstroMain 3.77.6 modified so that progress to Stage 6 (Recovery) only proceeds under the following condition, which now includes reference to the last succesful Router Ping time
  when Obs.PowerState = PowerState.MainsPower
 AndAlso ((SecondsSince(Obs.PowerOutageEndTime) > 20 And SecondsSince(LastRouterPingTime) < 8) Or SecondsSince(Obs.PowerOutageEndTime) > 90)
 And bReportedOutageStage4 = False Then
  Fixed  2025-08-05 (AstroMain 3.77.6)
  
  [ Note:  When the power cut started the UPS system initially reported that there were 68.5 mins of battery remaining, but after battery saving actions, there were still 42 minutes of battery left at the time the power was restored ]
   
• ObsViewer showed white flag against Weather & Cloud Sensor data during Power Outage even though data values were refreshing ok (2025-08-04 18:29 to 19:02).  During a 38.6 min outage ObsPic pictures showed that white flags against the various Weather & Cloud Sensor field even though data values were refreshing ok.  After mains power was restored the 3 CloudSensor flags returned to normal operation (red/green flags), but the 6 Weather station fields continued to show white flags again even though the data values were refreshing ok) until 20:02 (pointing to a DST issue).  Issue most-likely relates to some older logic in AstroMain that made assumptions about the non-validity of CS & WS data during a power cut going back to time before a UPS System was added to the AllSky/Weather Computing Bay.     Examining ObsViewer code shows that a white flag will be drawn for WS fields under the following conditions
  when Env.DataIsValid(EProp.WeatherStation)=false
or (MinutesSince(CloudSensorData.StartedMonitoringTime) > 5 And Env.MinutesSinceLastUpdate(EProp.WeatherStation) >= 1)
or Obs.PowerState = PowerState.Battery 
or (WeatherStn.bListening AndAlso Obs.PowerOutageEndTime <> vcNullDate And Env.TimeOfLastUpdate(EProp.WeatherStation) < Obs.PowerOutageEndTime) 
  Whilst a white flag will be drawn for CS field under the following conditions
   when Env.DataIsValid(EProp.CloudSensor) = false
 or MinutesSince(CloudSensorData.StartedMonitoringTime) > 5 And Env.MinutesSinceLastUpdate(EProp.CloudSensor) >= 1
 or Obs.PowerState = PowerState.Battery
 or CloudSensor.bListening AndAlso Obs.PowerOutageEndTime <> vcNullDate And Env.TimeOfLastUpdate(EProp.CloudSensor) < Obs.PowerOutageEndTime
   Obs.PowerOutageEndTime is assigned to Now() at the time that the Power Outage ends.   TimeOfLastDate is assigned as WeatherData.DateX where DateX is most like a UTC time  (so introduces a DST issue when compared with LT),  or assigned to CloudSensorData.LastCloudSensorTime where LastCloudSensorTime is Now() at the time the data record is received (date types match explaining why the Cloud Sensor fields revert back to normal flags as soon as Power Outage ends.
  Fixes applied to AstroMain 3.77.6
  1) Env.TimeOfLastUpdate(EProp.WeatherStation)  < Obs.PowerOutageEndTime
     changed to
   Env.TimeOfLastUpdate(EProp.WeatherStation).ToLocalTime < Obs.PowerOutageEndTime
2) or Obs.PowerState = PowerState.Battery
     changed to
   or (Obs.PowerState = PowerState.Battery and MinutesSince (Obs.PowerOutageStartTime) > 50) 
  Fixed 2025-08-05 (AstroMain 3.77.6)
   
• ObsViewer showed a green flag against Zigbee Network/Service even though it wasn't fully working (2025-08-04  19:02 to 00:48). Following a 38.6 min outage during which the Zigbee Network was seemingly working ok, the Zigbee Service & Websock were restarted at 19:02:02:26 as part of Post-Outage Recovery. This was done at a time when the LAN was still down, and led to reports that all Zigbee Smart Plugs and Sensors were not reachable. ObsPic pictures show that Zigbee related fields on the ObsViewer window showed white flags against Dome Power, Shutter Top/Bot Sensors, Dehumidifier and AllSky Camera Heater showing that they remained unreachable. This continued until 00:48 when user intervened to restart AstroMain & Observatory Services including the Zigbee Service.   The Zigbee Service should have shown a Red Flag. Fixed in AstroMain 3.77.6, using new CheckSelectedZigbeeDevices () routine called by thread from ObsMonitor and the raising/lower of flag Zigbee.bDevicesConnected  (check)
  Fixed 2025-08-05 (AstroMain 3.77.6)
   
• Error from CCDCamera / SBG Camera whilst attempting Dark Sequence (2025-08-05 21:06). After successfully connecting to Camera and successfully taking a Snap Frame at 17:53, and a Power Outage Test was conducted (19:49:51 and  20:29:25) during which SBIG Camera was disconnected/turned off (19:57:53), and later tunned on/reconnected (20:30:23).  A bit later a Dark Sequence (19x90s) was attempted at 21:03:00, with call to take first frame made at 21:04:36. The image failed with CCDCamera Pending messages beginning at  21:06:01, suggesting that CCDCamera/CCDSoft hung during Image Download.   Issues continued even with toggle SBIG Camera USB port etc.  A previously unseen exception in this context occured with messages   "Object reference not set to an instance of an object" and "Error: COM target does not implement IDispatch".  Problem eventually resolved by restarting both CCDSoft and AstroMain.  Logs were subsequently examined but didn't add much.   Unable to determine if the response to outage & recovery had created the situation in which the CCDSoft/SBIG Camera are destabilised or not.
  Workaround Used  2025-08-05 (Session, CCDSoft/AstroMain)

Small Defects

• ObsCam Pictures weren't active during the S1345 session. This was due to the ObsCam being turned off by the user whilst taking a series of flat & dark frames to  prevent possiibility of the infrared light from WebCam affecting the darks.  ObsCam was turned on again by the user the following day (2025-08-03).
  Closed after review 2025-08-03 (AstroObsCam, User Awareness)
   
• Report Line placed in wrong place at end of 'Restart SBIG Camera/CCDSoft' during recovery after mains outage (2025-08-04  19:02).  After the return of mains power after a 38 min outage associated with Storm FlorisCam, there was an attempt to restart the SBIG Camera (which had been turned off earlier during power outage management steps).   The RestartCCDSoft operation was finished but without the Camera being connected (SBIG Camera Smart Plug not reachable).  AstroMain's routines output a report line ( '---------' )' after finishing the final Restart CCDSoft step, but before the relevant & related report lines "Result" &  "Finished RestartCCDSoft()   Ok Finished Restart (Camera Not connected)". This is due to the Result being reported by an outer 'RestartCCDSoft' loop (up to 2 attempts) whilst the Report Line is generated by the Inner RestartCCDSoft routine.  Fixed in AstroMain 3.77.6 by means of flag bSkipFinalCCDSoftReportLine.
  Fixed 2025-08-05 (AstroMain 3.77.6)
   
• Dark Frames showing banding effect (2025-08-05 07:10). Whilst collecting dark frame set (3x3, - 15c, 180s) during early daytime hours  it was noticed that 11 of the 19 frames had a relatively distinct darker band at the bottom of the North Down  frames with a relatively brighter band above that. The ObsCam had been turned off (so IR light leakage can be ruled out). It is presumed that the banding is due to daylight entering the front of the telescope (which hadn't been covered) and was penerating the camera shutter in some way onto the CCD.  Rearside enty of light can't be ruled out.  It is presumed that sun llght illuminination of the Observatory (which penetrates the observatory glass-fibres roof & panels to some extent) was greatest during the 11 banding affected frames (taken during a sunny interval ?) and less sp during the 8 relatively normal frames (taken during a cloudy interval ?).  Fig 1 shows  a 'median average image of the frames showing banding and these are compared against a normal master dark frame.  Needless to say that these banding affected frames won't be used in the production of master darks.  Telescope should covered whilst taken future darks  or they should be taken at night.
  Closed after review 2025-08-03 (CCD Camera, Dark Frames, User Awareness) 
   
• 'CheckZigbeeDevices' shouldn't report "Device not found "whilst a Power Outage is occuring (2025-08-05). During system test  the log file contained (fail) message every 20s with the message "CheckZigbeeDevice  Device not found - AllSky Heater". These would be expected at this try as the power is off and the Smart Plugs wouldn't be connected to the Zigbee Network. Fixed in AstroMain 3.77.7 by adding extra condition ObsManager.bUnderOutageManagement <> True
  Fixed 2025-08-07 (AstroMain 3.77.7)
   
• 'Log' message during the Power Outage had an misleading szTargetName of "Snap"  (2025-08-05). After taking a Snap picture at 17:53, the same szTargetName continued to start of and throughout the Power Outage Period  (19:49 and  20:29). Reviewing code show that RunTake20sSnap() set szTargetName = "Snap" but then szTargetName back to SavedName at end of routine. but other snap routines RunTakeSnapImage() call TakeSnapImage_Detail() assign objectX = "Snap", but this isn't seemingly used to set szTargetName so it a mystery.   Fix attempted in AstroMain 3.77.7.   RunTakeSnapImage() modified to copy szTargetName to SavedName upon entry and to then restore szTargetName to SavedName (or to "Manual" if SavedName = "Snap").
  Fix attempted 2025-08-07 (AstroMain 3.77.7)
   
• During Power Outage Recovery the Zigbee Service was restarted before LAN router connection had been restarted (2025-08-05).  During Power Outage testing in which power was restored at  20:29:25, AstroMain reported that LAN had been restored as 20:30:56,  the Zigbee Service was restarted /devices  queried at 20:29:45 (T+20s). This would seem an failure to follow new management design which should wait until LAN connection had been restored.  It would seem fortunate that there wasn't a repeat of the Zigbee Device Issue that happened during the earlier actual power outage event on 2025-08-04. It calls into question the previous reasoning as to the cause of the earlier problem.  Reviewing code in AstroMain 3.77.6 the check on LAN router is only made when moving from OutageStage 4 to 6,  but not when moving from stage 2 to 6 or 3 to 6 or 5 to 6. Fixed in AstroMain 3.77.7.
  Fixed 2025-08-07 (AstroMain 3.77.7)