David's Astronomy Pages Notes - Session 1373 (2025-11-08)

Notes (S1372)

Notes Main

Home Page

Notes (S1374)

	Session Aims & Highlights
	- Observing Result  - Night Summary Plot  - Session Event Log
	Operational Issues
	- Critical Issues (0),  Major Issues (1),  Minor Issues (7),  Small Defects (5),  Continuous Improvement (9)
	- Figures (3)
	Images from 2025-11-08  >>
	2025-11-09
	Pegasus Unity Platform 2.12 & UPB v3 1.6 Firmware
	2025-11-10
	Investigation - Telescope's Dew Heater / UPB Outputs
	CumulusMX issue getting fresh station data

Session Aims & Highlights (2025-11-08)

Main aims

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

 Equipment & Software

• 12" LX200 and ST-10XME
• 80mm APO and ZWO ASI 178MC
• TheSky6 6.0.0.65, CCDSoft 5.00.201, DeviceHub 7.1.0.4707, MeadeGeneric 1.3.12.522, UPB 3,  Pulsar Dome Firmware 1.51 & Driver 6.3.10
• Pegasus-UI 2.10, Peg-Focuser 2.10, Peg-Switch 2.10, TCF-LSI 3.3.5
• SharpCap 3.2, PHD2  2.6.13, Siril 1.0.6, deCONZ 1.18.2, ASCOM 7.1.0.4707
• [ DomeLink 1.0 / 1.1 - not used ]
   
• AstroMain 3.78.3,  AstroPlan 1.43.14, AstroShCap 1.3.16, AstroGuard 1.12.1  (any new items or versions in bold)
  AstroMag 1.5.9, AstroVOE 1.15.1,  AstroSN 1.14,  AstroProtect 1.10.6,  AstroMove 1.16.3
  AstroWeather 1.28.1, AstroAllSky 3.25.3,  AstroObsCam 1.11.7, AstroNorthCam 1.6.4, AstroLaunch 1.13.7

Highlights

• Targets. 4/34 planned targets were completed with a further 1 target partially completed.  Other targets failed due to fog, cloud &  session suspension.
• CCD Camera.   No issues with CCD Camera during session..
•  Dome. No issues opening/closing the shutter during the session, and the dome was successfully parked at the end of the session..

NotesNotes

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 20:02:07 Session Monitoring AutoStart monitoring for Live Session opportunity between 20:02 & 05:46 20:02:10 Session AutoStarting Session autostarting (20:02) 20:02:23   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.) 20:02:37 Session Created Session Created (Live, 2025-11-08 S01373, ImageSaveNum: 1373001) 20:02:45   Scope Switched On Telescope Power has been switched on via UPB Switch 20:04:35   Services Started Observatory Services started 20:04:44 Observatory (Auto) Observatory placed in Fully-Automated Mode 20:04:47 Session Pending Session pending (2025-11-08) 20:04:49 Session Initiating Session initiating (2025-11-08) 20:05:09   Camera1 Connected SBIG Camera connected (Set point -10°C) 20:05:14   Plan Requested Observing Plan requested from AstroPlan (1.43.14) 20:06:27   Plan Loaded Observing Plan loaded to queue (Plan ID: 1160) 20:07:11   Telescope Connected Telescope connected (TheSky6) 20:07:35 Session Equilibration Session ready to Open Dome 20:08:20   Dome Opened Dome opened (Opening time 45s, Zigbee 40s) 20:08:22 Session Running Session running 20:08:25   Queue Started Observing Queue started (34 targets selected) 20:08:27     Target Started (NrZen) Target started (Focus Field 23, HIP 113729) 20:08:41       Dome Unparked Dome unparked 20:11:22       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 20:13:51       Focusing Completed Foc1 AutoFocus Completed (Profile No 1, wide) 20:16:14       Focusing Completed Foc1 AutoFocus Completed (Profile No 1) 20:16:18       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 20:18:15       Focusing Completed Foc2 AutoFocus Completed (Profile No 2, wide) 20:20:03       Focusing Completed Foc2 AutoFocus Completed (Profile No 2) 20:20:26     Target Completed (NrZen) Target completed (Focus Field 23, HIP 113729) 20:21:42     Target Started (1/34) Target started (1/34, C/2025 R2 (SWAN)) 20:26:21       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-LSI) 20:35:57     Target Completed Target completed (1/34, C/2025 R2 (SWAN)) 20:37:20     Target Started (2/34) Target started (2/34, GCVS CY Lyr) 20:41:12       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 20:43:49       Focusing Completed Foc1 AutoFocus Completed (Profile No 3) 20:45:09       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (too few stars) 20:47:38     Target Completed Target completed (2/34, GCVS CY Lyr) 20:47:40   Queue Paused Queue paused for Session Suspension 20:47:42 Session Suspending Session suspending 20:48:25   Dome Closed Dome closed (Closing time 45s, Zigbee 43s) 20:48:26 Session Suspended Session suspended 21:06:54     Target Cancelled Target cancelled (3/34, SN 2025taz) due to cloud 21:29:14     Target Cancelled Target cancelled (4/34, M31 w/AT2025abws) due to too few stars 21:30:19 Session Resuming Session resuming 21:31:04   Dome Opened Dome opened (Opening time 45s, Zigbee 40s) 21:31:05 Session Running Session running 21:31:08   Queue Resumed Observing Queue resumed 21:31:10     Target Started (5/34) Target started (5/34, IC 1529 w/SN2025kjo) 21:35:27       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-LSI) 21:40:45       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (too few stars) 21:42:50       SoftSuspend Cancelled Soft Suspend is cancelled due to improved conditions 21:51:52     Target Completed Target completed (5/34, IC 1529 w/SN2025kjo) 21:54:18     Target Started (6/34) Target started (6/34, NGC 7606 w/SN2025vzq) 21:58:42       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-LSI) 22:03:02       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (too few stars) 22:06:23       SoftSuspend Cancelled Soft Suspend is cancelled due to improved conditions 22:08:48       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (reducing clarity) 22:08:50   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 22:08:52   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 22:08:54     Target Aborted (6/34) Target aborted (6/34, NGC 7606 w/SN2025vzq) due to cloud 22:08:56   Queue Paused Queue paused for Session Suspension 22:08:59 Session Suspending Session suspending 22:09:48   Dome Closed Dome closed (Closing time 50s, Zigbee 43s) 22:09:50 Session Suspended Session suspended 22:13:14     Target Cancelled Target cancelled (6/34, NGC 7606 w/SN2025vzq) due to cloud 22:35:34     Target Cancelled Target cancelled (7/34, AT2024wqf) due to cloud 22:49:54     Target Cancelled Target cancelled (8/34, AT2025md (CV)) due to cloud 23:01:02     Target Cancelled Target cancelled (9/34, GCVS SS Cyg) due to cloud 23:16:13     Target Cancelled Target cancelled (10/34, GCVS U And) due to cloud 23:27:01     Target Cancelled Target cancelled (11/34, GCVS BL Lac) due to cloud 23:47:01     Target Cancelled Target cancelled (12/34, M31 w/Nova M31 2025-10a?) due to cloud 23:59:11     Target Cancelled Target cancelled (13/34, GCVS RX And) due to cloud 00:18:21     Target Cancelled Target cancelled (14/34, NGC 600 w/AT2025abzu) due to cloud 00:33:32     Target Cancelled Target cancelled (15/34, GCVS TT Ari) due to cloud 00:53:37     Target Cancelled Target cancelled (16/34, SN 2025aarn) due to cloud 01:15:37     Target Cancelled Target cancelled (17/34, LEDA 3092696 w/AT2025nzh) due to cloud 01:37:38     Target Cancelled Target cancelled (18/34, AT2025abne) due to cloud 01:48:41     Target Cancelled Target cancelled (19/34, Capella) due to cloud 02:02:13     Target Cancelled Target cancelled (20/34, C/2022 N2 (PANSTARRS)) due to cloud 02:12:39     Target Cancelled Target cancelled (21/34, GCVS GK Per) due to too few stars 02:17:38 Session Resuming Session resuming 02:18:23   Dome Opened Dome opened (Opening time 45s, Zigbee 41s) 02:18:25 Session Running Session running 02:18:27   Queue Resumed Observing Queue resumed 02:18:30     Target Started (22/34) Target started (22/34, GCVS RZ LMi) 02:23:46       Dome Unparked Dome unparked 02:24:54       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (too few stars) 02:28:27     Target Completed Target completed (22/34, GCVS RZ LMi) 02:28:29   Queue Paused Queue paused for Session Suspension 02:28:32 Session Suspending Session suspending 02:29:19   Dome Closed Dome closed (Closing time 50s, Zigbee 43s) 02:29:21 Session Suspended Session suspended 02:36:31     Target Cancelled Target cancelled (23/34, GCVS RR Tau) due to cloud 02:46:04     Target Cancelled Target cancelled (24/34, GCVS U Gem) due to cloud 02:57:52     Target Cancelled Target cancelled (25/34, GCVS DX Cnc) due to cloud 03:17:21     Target Cancelled Target cancelled (26/34, NGC 3106 w/SN2025aauj) due to cloud 03:39:21     Target Cancelled Target cancelled (27/34, AT2023clj (CV)) due to cloud 04:01:21     Target Cancelled Target cancelled (28/34, LEDA 3089972 w/SN2025lxm) due to cloud 04:23:21     Target Cancelled Target cancelled (29/34, NGC 4710 w/AT2025acfi) due to cloud 04:48:41     Target Cancelled Target cancelled (30/34, C/2025 K1 (ATLAS)) due to cloud 05:09:25     Target Cancelled Target cancelled (31/34, 29P/Schwassmann-Wachmann) due to cloud 05:30:15     Target Cancelled Target cancelled (32/34, ESO 565-G19 w/SN2025efc) due to cloud 05:52:35     Target Cancelled Target cancelled (33/34, NGC 2986 w/SN2025gj) due to cloud 06:17:01     Target Cancelled Target cancelled (34/34, GCVS RR Leo) due to cloud 06:17:05   Queue Completed Job Queue completed 06:17:08 Session Closing Session closing 06:17:13   Dome Closed Dome already closed (closed at 02:29, closing time 50s, zigbee 43s) 06:17:32   Dome Parked Dome parked (parking time 10s), Az: 90.0 deg 06:18:22   Telescope Parked Telescope parked (parking time 42s total) 06:18:46   Telescope State Handbox reads 'Scope parked Turn scope off.' 06:19:09   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 06:20:35   Services Stopped Night Services stopped 06:20:38 Session Finishing Session Finishing started (Create Fits Summary, Transfer Files) 06:20:55     Dome (Find Park) Find Park started (Search Az 88.0 to 92.0°, Step 0.2°, Narrow) 06:21:40     Dome Find Park found (Best Park Az 90.2°) 06:21:46     Dome Dome has been synced at park position (Az 90.0°, Adjustment: -0.2°) 06:21:48   Dome Parked Dome parked 06:23:38   Dome Charging Dome is parked and re-charging Ok (15mA) 06:23:40 Session Finished Session Finished

Session Alerts & Alarms

Time     Type       Name Detail 06:23:38 Green Clear Dome Charging Dome is parked and re-charging Ok (15mA)

Back to Top

Operational Issues (2025-11-08 S1373)

• Critical Issues (0)
• Major Issues (1)
• Minor Issues (7)
• Small Defects (4)
• Continuous Improvement (9)
• Figures (3)
  

Critical Issues

• None

Major Issues

• Couldn't properly login into Observatory Computer following computer reboot (2025-11-09). After restarting Observatory Computer at 15:10 following a Device/Memory Security Change (believed to be 'Turn on Memory Integrity') at around 15:10, the main user account couldn't be properly accessed after logging in.  The account could be logged into but the screen would then go completely black.  The computer was restarted again a couple of times but the result was the same.   Fortunately rebooting and logging into Admin account was successful. But the problem with main user account continued when trying to log- in.   Problem would seem to be a corruption of the registry associated with main account user.  Restore operation took a long time. Other recent changes have been i) Regedit used to change ScrollHeight/ScrollWidth, ii) Device Manager used to disable the computer from turning off USB device to save power.   Eventually proceeded to performed a System Restore back to the recommended restore point earlier in afternoon (14:00) just prior to installation of Pegasus Unity 2.12 (no reason to believe that Unity platform was in any way related to problem, as computer was working ok after the install).  Currently (17:00) the Restore operation has passed the Restoring Files, and Restoring Registry stages but is held-up in the 'System restore is removing temporary files' stage.  Google search on 'system restore stuck whilst removing temporary files' says this can take hours and to wait, with advice "If System Restore is stuck on temporary files, force shut down the computer by holding the power button, then restart it and let it boot up on its own or into Startup Repair. If that doesn't work, try booting into Safe Mode (F8 or Shift-F8) and performing a System Restore again or running checks like SFC/DISM to repair system files. "  After 5 hours the computer was restarted using computer Power button. An dialog signalled that the restore had failed,  and a couple of System Restores to earlier points on 2025-11-09 and 2025-11-06 were tried and again the restores failed or caused boot failures (though they did run faster than the first attempt which stalled).  The problem then widened and the boot failed with some sort of CONFIG_SYSTEM.. failure.  Computer was rebooted to safe mode and a restore made back to a restore point on 2025-11-05.  This succeeded and the main user account was again accessible.  Applications updated since the restore point (Pegasus Unity, AstroMain, AstroLaunch, AstroGuard) were either reinstalled or replaced. Recently changed settings (SAM View UTC Offset) were also reset / changed.  Observatory Suite was tested and checked. A new restore point was created.
  Fixed 2025-11-09 (Observatory Computer) 

Minor Issues

• AstroMain still recording 'AllSky/Synopsis' alert in morning around daybreak (2025-11-09).  AstroMain is still recording 'AllSky/Synopsis' red alerts around daybreak (~ 07:30) each morning with the message "AllSky Star & Synopsis data has been inactive for more than 5 mins", followed by all-clear alerts with message like "AllSky Star & Synopsis data is active again (outage 5.8 mins)".   New alert on 2025-11-09. This is despite a fix being implemented on 2025-11-07 in AstroAllSky 3.25.3 and the absence of the issue on 2025-11-08.
    2025-11-05  07:24:46,  outage 6.1 mins
  2025-11-06  07:27:07,  outage 7.5 mins
  2025-11-07  07:29:13,  outage 5.2 mins
  2025-11-09  07:35:11,  outage 5.8 mins
To be investigated. Examining this morning's case (2025-11-09) the red alert time indicates that last valid Synposis record was at 07:30:11.   AllSky Logs show that all Synopsis records between 07:30:14 and 07:36:05 were written out with the timestamp '2025-11-09T07:30:10Z'. This period (5.7 mins) is longer than 5 min which explains why AstroMain produced a red alert.   The previous day (2025-11-08), Synposis record timestamps  were 'stuck' on 07:27:38Z between 07:27:42 and 07:31:02, but this period (3.23 mins) is less than 5 mins and therefore didn't lead to a red alert.  Conclusion is that the fix attempted in AstroAllSky 3.25.3 didn't work.  Examining code showed that the attempted fix had a flaw so that Synopsis Time wasn't getting updated after each Panorama Video creation.  Flaw corrected in AstroAllSky 3.25.4, which finally fixes the issue. A 'Synopsis.Time = DateTime.UtcNow' code line has now been added to CreatePanoramaVideo(), complementing the previous addition to CreateAllSkyVideo().
  Fixed 2025-11-09 (AstroAllSky 3.25.4) 
   
• Light pollution in northern sky affecting NorthCam Images & Keogram (2025-11-08).  There was very noticeable light pollution in northern sky during the evening of 2025-11-08. This is evident in the two example NorthCam Images taken at 21:52 & 22:14 (see Fig 1) . The impact of the orange glow through the evening os also very noticeable on the night's NorthCam Keogram (see Fig 1b)  At times the glow reaches up to 35° altitude and would have affected the quality of aurora monitoring (had there been any activity that night) The orange glow comes from low level fog and occasional passing clouds being lit up by the light from a line of lanterns / lights along a garden fence line in the neighbouring estate to the north, around 150m away. There is also increased glow from streetlights on the estate. Fortunately this seems to have been a single night issue (a weekend Guy Fawkes party ?) combined with foggy conditions. Closed after review 2025-11-10.
  Closed after review 2025-11-10 (NorthCam Imaging) 
   
• Dew Heater Band on LX200 Telescope as it is suspected of not working. OTA (telescope tube) temperature has been noticed to more or less track the UPB Env Temperature and doesn't seem to rise with increased Dew Heater Power. Even though Power is at 100% it doesn't seem to increase OTA Temp above that of the UPB Env Temperature and doesn't increase it to the point of being 2°C above the Outside Dew Point (see Fig 2). The issue was investigated which determined that the LX200's dew heater cable had been mistakenly plugged into the wrong Output on the UPB v3 box during installation & cable hookup. Cable had been plugged into Output 3 instead of Output A as planned. (see Investigation - Telescope's Dew Heater / UPB Outputs). The error was correctly after when the LX200 dew heater began working and allowed AstroMain to maintain the OTA temperature above Dew Point by the required amount (typically 1°C) (see Fig 2b)
  Fixed 2025-11-10 (Observatory, UPB, Dew Heaters)
   
• Temperature readings from the EcoWitt 2000 Gateway Hub are not representative of the Observatory. The Ecowitt Weather Station's  Indoor Temperature is used as the Observatory Temperature, however its temperature values are around 2.5°C higher than UPB Env (see Fig 3). Temperature. Humidity value is corresponding lower than UPB Env. humidity.  The Indoor Temperature sensor is located in the Weather Stations GW2000 Gateway Hub.  This is positioned on the upper shelf of the AllSky/Weather Computing Bay and just behind the AllSky/Weather Computer.  In this position it is subject to heating effect from the heating carrying air vents on the back of the computer. The Gateway Hub was relocated on 2025-11-10 to a position on the lower shelf which should be more representative of the Observatory's general environment, though it might still to be effected by heat coming from other equipment in the AllSky/Computing Bay - but much less than output by the computer on the top shelf. The temperature measured in its new sensor location will be monitored over the next few days to see if there is an improvement. This showed that the Observatory Temperature from the Ekowitt Gateway Hub is now much more representative of the temperature in the Observatory (see Fig 3b)
  Resolved  2025-11-13 (Observatory, Ecowitt GW2000 Gateway Hub,  AllSky Computing Bay) 
   
• Development and Observatory Computers lost connection to AllSky/Weather Computer (2025-11-09 20:04). AstroMove's ping monitor showed that the AllSky/Weather Computer was not accessible (red flag).  Observatory Computer showed red flag against Cloud Sensor, Weather Station and Scorcard indicating no connection with the AllSky/Computer.  An observatory visit, showed that 'AllSky/Weather Computer was still running, but it didn't have Lan/Internet Connection, however it was quickly reestablised (seemingly by itself). AstroAllSky was unexpectedly not running and the CloudSensor III was showing 0, 0 , 0 values.  Before intervening the CloudSensor III began showing real values again.  AstroAllSky was manually restarted via AstroLaunch and a check of the Observatory Computer showed that it was recieving Cloud Sensor, Weather Station and Scorcard data again.  Subsequently it was shown that the AllSky/Weather computer could be pinged and otherwise accessed from the Development Computer.   Issue seems to have been a glitch of some kind.  Unclear if this related to the restarting the Observatory Computer & restarting AstroMain following System Restore.   Could a bad ObsEnv record from AstroPlan have caused AstroAllSky to crash and give rise to the network connection problem.  Issue closed after review.  NightSummary Plot reveals that CloudSensor and NorthCam data flow stopped at 19:42, with Weather data stopping at 19:47 and AllSky Imaging stopping at 20:33  (see Fig 4)The resumption of all data services is shown at around 20:42.
  Resolved / Closed after review 2025-11-09 (AllSky/Weather Computer) 
   
• Dimension 4 icon not appearing in System Tray since upgrading to Windows 11. Dimension4 is used to keep computer time in sync on the Observatory an AllSky/Weather Computers as well as the Development Computer. Whilst the D4 application is running on the computers, the D4 icon is no longer appearing in the computer's system tray since upgrading the computers from Windows 10 to Windows 11.  It is unclear if the issue can be resolved or not.  Resinstalling the application might potentialy fix the issue  The latest available version (5.3) is being used, however it hasn't been updated since 2004 and wasn't written with Windows 10//1 in mind.  There is no specific evidence apparently to indicate that the system tray issue in Windows 11 is related to the Dimension 4 version 5.3 software itself. Instead, numerous sources confirm there are general, ongoing system tray bugs and inconsistencies within Windows 11 itself, which affect various applications, with icons disappearing or not loading correctly on boot, and the system tray becoming unresponsive or non-functional after being clicked, sometimes requiring a restart of the explorer.exe process or the PC itself to temporarily resolve.   Some other products suggested by google are BktTimeSync and NetTime. Using Microsoft's own automatic time adjustment and the standard time server (time.windows.com) has been proven problematic (changed time server to ntp2.uk.uu.net - UK London).   Unistalled D4 v5.0 and D4 v5.3.1 on AllSky/Weather Computer, reinstalled D4 v5.3.1, remove D4 shortcut from StartMenu/Programs/Start-up (to ensure two copies of D4.exe aren't run as currently happens), opened D4 and ensured that the normally used TimeServer (ntp2.uk.uu.net) was set and that the 'Load Dimension 4 at startup' option was enabled, minimized D4, and checked that D4 icon appeared in the Task Tray ok.   A reboot will be required to check the implementation from start-up is working and that D4 icon continues to show-up in the system tray.
  Fix attempted  2025-11-11 (Observatory Computer, AllSky Computer, Dimension 4)
   
• After restarting Ecokwitt WeatherStation and restarting CumulusMX the localhost:8998 indicated that there was no fresh updates coming from the station.   After disconnecting power and ethernet cables to weather station's GW2000 Gateway Hub in order to move the gateway Hub to a new location (that was further from heating effects from the AllSky/Weather Computer) cables were reconnected to Gateway and after lights on the hub stopped flashing. CumulusMX was again started. Checking localhost:8998 in browser (which opens the CumulusMX dashboard) showed that Last Station Update time was being refreshed and data fields all showed values like 0 or 0.0.  This indicates that there is an issue that needs to be corrected before the weather station data can be streamed to AstroWeather, AstroAllSky, AstroMain, AstroGuard programs which ensure that observatory is safe as well as permitting many other monitoring services and data use., data graphing etc.  When CumulusMX behaves in this way the only solution has formerly been to copy the CumulusMX program area to a new folder and start CumulusMX.exe from there. The clone CumulusMX facility previous added to AstroLaunch was used to copy the CumulusMX9 to CumulusMX10.  But on this occasion attempting to open CumulusMX from the new CumulusMX10 location didn't resolve the problem. Adjusting the Ethernet cable connection to the Gateway Hub (possibly resetting the LAN/Internet connection) magically resolved the problem problem.   It seems that the CumulusMX or the Gateway Hub requires LAN or Ethernet or LAN access for it to work and at least initialise correctly.  It seems to need to make a check on whether CumulusMX is running with latest version or not. I'm currently using Cumulus MX v.4.2.1 build 4043  I purposedly don't have the latest version (due to uncertain upgrade pathfor preserving data and settings), and when CumulusMX is started (and thereafter on a regular base whilst running) it will display the console line "You are not running the latest version of Cumulus M, build Version 4.6.4 - Build 4128 is available".  If this message appears I know everything is fine, but if it doesn't I can use it as a strong indicator that Cumulus MX is not sending fresh station data to local host or the applications relying on weather station data.  With the issue understood and resolved (2025-11-11) , the 'live' Cumulus MX folder was changed back to 'CumulusMX9' and the unnecessarily cloned 'CumulusMX10' folder deleted.
  Resolved  2025-11-10 (AllSky/Weather Computer, CumulusMX, User Awareness)

Small Defects

• ACDSee32 Application on Observatory Computer has lost its registration details (2025-11-10).  ACDSee32 application on Observatory Computer had previously had registration details entered, but today (2025-11-10) it reports that it is unregistration. Registration details migt have been lost during the recent upgrade to Windows 11 on 2025-11-03 or during yesterday's the system restore (2025-11-09, restored back to 2025-11-05). Issue resolved by re-entering registration details. .
  Resolved  2025-11-10 (Observatory Computer, ACDSee)
   
• Focuser1 was likely incorrectly reported as being inaccessible and caused a unnecessary red alert (2025-11-09).  Focuser1 (TCF-LSI) was reported to be inaccessible at 20:31:25 with a last valid time of 20:29:48 and a red alert raised. The Focuser service was automatically restarted with a outage reported as being 107s.  Examining the context of the alert, logs show that  the Observatory Services were restarted by user at 20:29:11 following a frozen CCD Monitor thread at a time with an issue with connection to AllSky/Weather Computer.  The Focuser1 service started at 20:29:26 and evidentally gained a valid Temperature/Position information from the Focuser at 20:29:48, at which point the user stopped observatory services and then restarted them at 20:31:13. Whilst Focuser1 service was being restarted at around 20:31:25, the ObsManager reported that the Focuser1 was not accessible at 20:31:25, and commanded a restart of the Focuser1 service. Whilst the restart of the Focuser was successful the alert was quite possibly false, and was due to the ObsManager code calculating the time since last valid data as being 119s and triggered the automatic response made.   The ObsManager code should not allow the trigger to be met when the Focuser1 has only just been started, as the Focuser1 is most likely working ok if more time is allowed for a fresh values to be obtained. Fixed in AstroMain 3.78.4 by adding variable StartObsManagerTime that is set when ObsManager starts and adding a condition to Focuser1 status check to ensure than SecondSince(StartObsManagerTime) is > 90.
  Fixed 2025-11-11  (AstroMain 3.78.4)
   
• Certain Focuser1 alerts and reporting is using the text 'TCF-S'  when it should be picking up 'TCF-LSI'. Certain alerts and reporting are used a legacy hard-coded text like 'TCF-S' or '(TCF-S)'.  Instead of the hardcoded text, the relevant alert or report code line should use the variable 'Focuser1.Name'  so that it can pick up the currently assigned name 'TCF-LSI'. Fixed in AstroMain 3.78.4.
  Fixed 2025-11-11  (AstroMain 3.78.4)
   
• Status flag for CloudSensor and Weather services in AstroWeather are regulary flashing between green and yellow.  Status flags on the AstroWeather Console are used to indicate activiy of the various services with Green flagging that the service is working corrrectly and Red flagging a problem such as no fresh/recent values.  A yellow flag is meant to show that new values are pending but not yet recieved.  Having the CloudSensor and Weather service flags flash from green to yellow and back to green within the same minute is annoying.  The timing tolarance for receiving fresh data should be relaxed (a value of something like 40s or 65s should probably be used.   Examination of code shows that yellow traffic light is shown against Ws or Cs service when the bWsCycleOverrun or bCsCycleOverrun flag is True. These flags are set to true when ElapsedCycleSecs - DesiredCycleSecs >= 0.1. Problem fixed by relaxing the tolerance to >=5 secs
  Fixed 2025-11-11 (AstroWeather 1.28.3)
   
• The magnetometer graph image on home page doesn't show the latest image. The magnetometer image shown on the home page (../astro/image.htm) under the 'Magnetometers (Latest)' banner doesn't ever show the latest magnetometer chart, but always present the same image.  Opening the image in MSEde using 'Open image in new tab' presents the same image with url https://www.astro-richweb.net/astro/live/Latest.MagnetogramChart.png. The correct file name for latest chart is 'Latest.MagnetogramChart_XYZ.png'.  This explains the issue.  PIcture url corrected in index.htm on 2025-12-17 (picture width set to 290 px) .
  Fixed 2025-11-17.  (Observatory Website / Home Page)