David's Astronomy Pages Notes - Session 1372 (2025-11-01)

Notes (S1371)

Notes Main

Home Page

Notes (S1372)

	Session Aims & Highlights
	- Observing Result  - Night Summary Plot  - Session Event Log
	Operational Issues
	- Critical Issues (0),  Major Issues (0),  Minor Issues (4),  Small Defects (4),  Continuous Improvement (6)
	- Figures (0)
	Images from 2025-11-01  >>
	2025-11-02
	ASCOM - Platform 7.1
	DeviceHub - Version 7.1
	2025-11-03
	Development Computer - Windows 11 Update (Version 25H2)

Session Aims & Highlights (2025-11-01)

Main aims

1. Targets.  Acquire images of a selection of variable stars, nearby stars, comets & deep sky targets as allowed by sky conditions.
2. Windows 11. Check observatory system after upgrading Observatory and AllSky/Weather Computers from Windows 10 to Windows 11
       (AllSky/Weather Computer - Upgrade to Windows 11 (2025-10-28)  and
        Observatory Computer - Upgrade to Windows 11 (2025-10-29) )

 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.78.2,  AstroPlan 1.43.14, AstroShCap 1.3.16, AstroGuard 1.12  (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.2
  AstroWeather 1.28, AstroAllSky 3.25.1,  AstroObsCam 1.11.7, AstroNorthCam 1.6.4, AstroLaunch 1.13.6

Highlights

• Targets. 14/37 planned targets were completed (12 at their original plan times and 2 as ToO targets (C/2025 R2 Swan and T CrB) due to cloud) with a further 6 targets partially completed.  Other targets failed due to cloud / session suspension.. Image sets from two targets were later rejected due to cloud.
• Windows 11.  This was the second live session after updating Observatory & AllSky/Weather Computers to Windows 11, and the first since updating the AllSky/Weather Computer from Windows 11 version 23H2 to version 25H2. There were no significant issues apart from an initial issue with CloudSensor III.
• 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.

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 18:12:54 Session Monitoring AutoStart monitoring for Live Session opportunity between 18:12 & 05:32 18:12:59   AutoStart Delayed Session delayed due to missing sky/weather information 18:23:10 Session AutoStarting Session autostarting (18:23) 18:23:23   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.) 18:23:37 Session Created Session Created (Live, 2025-11-01 S01372, ImageSaveNum: 1372001) 18:23:47   Scope Switched On Telescope Power has been switched on via UPB Switch 18:25:35   Services Started Observatory Services started 18:25:45 Observatory (Auto) Observatory placed in Fully-Automated Mode 18:25:47   AutoStart Delayed Session delayed due to missing sky/weather information 18:25:49 Session Pending Session pending (2025-11-01) 18:25:51 Session Initiating Session initiating (2025-11-01) 18:26:10   Camera1 Connected SBIG Camera connected (Set point -20°C) 18:26:14   Plan Requested Observing Plan requested from AstroPlan (1.43.14) 18:27:22   Plan Loaded Observing Plan loaded to queue (Plan ID: 1159) 18:28:01   Telescope Connected Telescope connected (TheSky6) 18:28:25 Session Equilibration Session ready to Open Dome 18:29:10   Dome Opened Dome opened (Opening time 45s, Zigbee 41s) 18:29:15 Session Running Session running 18:29:18   Queue Started Observing Queue started (37 targets selected) 18:29:21     Target Started (NrZen) Target started (Focus Field 21, HIP 103850) 18:29:35       Dome Unparked Dome unparked 18:32:47       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 18:35:14       Focusing Completed Foc1 AutoFocus Completed (Profile No 1, wide) 18:37:36       Focusing Completed Foc1 AutoFocus Completed (Profile No 1) 18:37:57       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 18:39:49       Focusing Completed Foc2 AutoFocus Completed (Profile No 2, wide) 18:41:38       Focusing Completed Foc2 AutoFocus Completed (Profile No 2) 18:42:00     Target Completed (NrZen) Target completed (Focus Field 21, HIP 103850) 18:42:42     Target Started (1/37) Target started (1/37, C/2024 E1 (Wierzchos)) 18:46:46       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-LSI) 18:55:16     Target Completed Target completed (1/37, C/2024 E1 (Wierzchos)) 18:56:14     Target Aborted (2/37) Target aborted (2/37, GCVS CY Lyr) due to Priority 1 ToO Target 18:56:18     Target Started (3/38) Target started (3/38, C/2025 R2 (SWAN), ToO) 19:00:12       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 19:02:52       Focusing Completed Foc1 AutoFocus Completed (Profile No 3) 19:12:28     Target Completed Target completed (3/38, C/2025 R2 (SWAN), ToO) 19:12:32     Target Started (4/38) Target started (4/38, UGC 10058 w/SN2025gvs) 19:14:05       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (too few stars) 19:17:07     Target Failed (4/38) Target failed due to cloud (4/38, UGC 10058 w/SN2025gvs) 19:17:09   Queue Paused Queue paused for Session Suspension 19:17:11 Session Suspending Session suspending 19:18:01   Dome Closed Dome closed (Closing time 50s, Zigbee 43s) 19:18:02 Session Suspended Session suspended 19:26:48     Target Cancelled Target cancelled (4/38, UGC 10058 w/SN2025gvs) due to cloud 19:40:14     Target Cancelled Target cancelled (5/38, T CrB) due to cloud 20:00:04     Target Cancelled Target cancelled (6/38, 2MFGC 13744 w/SN2024afyu) due to cloud 20:12:22     Target Cancelled Target cancelled (7/38, GCVS BL Lac) due to cloud 20:32:42     Target Cancelled Target cancelled (8/38, M31 w/AT2025abws) due to cloud 20:47:02     Target Cancelled Target cancelled (9/38, AT2023hxd (CV)) due to too few stars 20:47:39 Session Resuming Session resuming 20:48:24   Dome Opened Dome opened (Opening time 45s, Zigbee 40s) 20:48:26 Session Running Session running 20:48:28   Queue Resumed Observing Queue resumed 20:48:31     Target Started (10/38) Target started (10/38, UGC 10809 w/SN2025vaw) 20:54:03       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 20:56:44       Focusing Completed Foc1 AutoFocus Completed (Profile No 4) 21:13:05     Target Completed Target completed (10/38, UGC 10809 w/SN2025vaw) 21:13:09     Target Started (11/39) Target started (11/39, T CrB, ToO) 21:22:21     Target Completed Target completed (11/39, T CrB, ToO) 21:22:25     Target Started (12/39) Target started (12/39, SN 2025taz) 21:35:52     Target Completed Target partially completed (12/39, SN 2025taz) 21:35:56     Target Started (13/39) Target started (13/39, AT2024advw) 21:40:01       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 21:42:16       Focusing Completed Foc1 AutoFocus Completed (Profile No 5) 21:58:49     Target Completed Target completed (13/39, AT2024advw) 21:58:53     Target Started (14/39) Target started (14/39, C/2025 R2 (SWAN)) 22:14:39     Target Completed Target partially completed (14/39, C/2025 R2 (SWAN)) 22:14:43     Target Started (15/39) Target started (15/39, AT2025ygh) 22:14:49     Target Failed (15/39) Target failed due to dec limit (15/39, AT2025ygh) 22:32:24     Target Started (16/39) Target started (16/39, AT2025tes) 22:36:33       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 22:38:57       Focusing Completed Foc1 AutoFocus Completed (Profile No 6) 22:55:16     Target Completed Target completed (16/39, AT2025tes) 22:55:20     Target Started (17/39) Target started (17/39, UGC 3458 w/SN2025yao) 22:55:42       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (too few stars) 22:56:47   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 22:56:49   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 22:56:58     Target Aborted (17/39) Target aborted (17/39, UGC 3458 w/SN2025yao) due to cloud 22:57:00   Queue Paused Queue paused for Session Suspension 22:57:02 Session Suspending Session suspending 22:57:52   Dome Closed Dome closed (Closing time 50s, Zigbee 43s) 22:57:53 Session Suspended Session suspended 23:05:22 Session Resuming Session resuming 23:06:08   Dome Opened Dome opened (Opening time 46s, Zigbee 41s) 23:06:10 Session Running Session running 23:06:13   Queue Resumed Observing Queue resumed 23:06:15     Target Started (17/39) Target started (17/39, UGC 3458 w/SN2025yao) 23:18:25     Target Completed Target partially completed (17/39, UGC 3458 w/SN2025yao) 23:18:29     Target Started (18/39) Target started (18/39, AT2025aaeg) 23:40:47     Target Completed Target completed (18/39, AT2025aaeg) 23:40:51     Target Started (19/39) Target started (19/39, SN 2025aarn) 23:48:52       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (too few stars) 00:02:32     Target Aborted (19/39) Target aborted (19/39, SN 2025aarn) due to User Intervention 00:02:34   Queue Paused Queue paused for Session Suspension 00:02:36 Session Suspending Session suspending 00:03:24   Dome Closed Dome closed (Closing time 50s, Zigbee 43s) 00:03:26 Session Suspended Session suspended 00:13:05 Session Resuming Session resuming 00:13:50   Dome Opened Dome opened (Opening time 45s, Zigbee 41s) 00:13:51 Session Running Session running 00:13:54   Queue Resumed Observing Queue resumed 00:13:56     Target Started (20/39) Target started (20/39, AT2025abne) 00:24:48     Target Completed Target partially completed (20/39, AT2025abne) 00:24:52     Target Started (21/39) Target started (21/39, GCVS HH And) 00:28:16       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (too few stars) 00:28:50       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-LSI) 00:29:26       SoftSuspend Cancelled Soft Suspend is cancelled due to improved conditions 00:30:49     Target Completed Target completed (21/39, GCVS HH And) 00:31:01     Target Started (22/39) Target started (22/39, GCVS FU Ori) 00:36:11       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:38:59       Focusing Completed Foc1 AutoFocus Completed (Profile No 7) 00:39:17       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (too few stars) 00:39:27       SoftSuspend Cancelled Soft Suspend is cancelled due to improved conditions 00:41:58       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (too few stars) 00:42:07     Target Completed Target completed (22/39, GCVS FU Ori) 00:42:09   Queue Paused Queue paused for Session Suspension 00:42:11 Session Suspending Session suspending 00:42:58   Dome Closed Dome closed (Closing time 50s, Zigbee 43s) 00:42:59 Session Suspended Session suspended 00:59:17     Target Cancelled Target cancelled (23/39, AT2023ctk) due to cloud 01:21:18     Target Cancelled Target cancelled (24/39, GCVS GW Ori) due to cloud 01:41:18     Target Cancelled Target cancelled (25/39, M31 w/Nova M31 2025-10a?) due to cloud 01:55:38     Target Cancelled Target cancelled (26/39, AT2025md (CV)) due to cloud 02:06:46     Target Cancelled Target cancelled (27/39, GCVS SS Cyg) due to cloud 02:15:44     Target Cancelled Target cancelled (28/39, GCVS TV Cas) due to cloud 02:41:20     Target Cancelled Target cancelled (29/39, Jones 1) due to cloud 02:53:30     Target Cancelled Target cancelled (30/39, GCVS RX And) due to cloud 03:12:40     Target Cancelled Target cancelled (31/39, AT2024jfs) due to cloud 03:26:43     Target Cancelled Target cancelled (32/39, GCVS DX Cnc) due to cloud 03:45:53     Target Cancelled Target cancelled (33/39, CGCG 091-101 w/AT2025yhi) due to too few stars 03:57:06 Session Resuming Session resuming 03:57:51   Dome Opened Dome opened (Opening time 45s, Zigbee 41s) 03:57:53 Session Running Session running 03:57:55   Queue Resumed Observing Queue resumed 03:57:58     Target Started (34/39) Target started (34/39, GCVS RZ LMi) 04:04:35     Target Completed Target partially completed (34/39, GCVS RZ LMi) 04:04:39     Target Started (35/39) Target started (35/39, NGC 3040 w/SN2025nkf) 04:08:07       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-LSI) 04:24:16     Target Completed Target completed (35/39, NGC 3040 w/SN2025nkf) 04:24:21     Target Started (36/39) Target started (36/39, NGC 3106 w/SN2025aauj) 04:27:37       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 04:30:38       Focusing Completed Foc1 AutoFocus Completed (Profile No 8) 04:47:22     Target Completed Target completed (36/39, NGC 3106 w/SN2025aauj) 04:47:26     Target Started (37/39) Target started (37/39, 29P/Schwassmann-Wachmann) 05:08:48     Target Completed Target completed (37/39, 29P/Schwassmann-Wachmann) 05:08:52     Target Started (38/39) Target started (38/39, C/2025 K1 (ATLAS)) 05:33:51     Target Completed Target completed (38/39, C/2025 K1 (ATLAS)) 05:33:55     Target Started (39/39) Target started (39/39, AT2023tsk) 05:53:50     Target Completed Target completed (39/39, AT2023tsk) 05:53:52   Queue Completed Job Queue completed 05:53:54 Session Closing Session closing 05:54:49   Dome Closed Dome closed (Closing time 50s, Zigbee 44s) 05:55:17   Dome Parked Dome parked (parking time 20s), Az: 90.1 deg 05:56:11   Telescope Parked Telescope parked (parking time 46s total) 05:56:35   Telescope State Handbox reads 'Scope parked Turn scope off.' 05:56:57   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 05:58:21   Services Stopped Night Services stopped 05:58:24 Session Finishing Session Finishing started (Create Fits Summary, Transfer Files) 05:59:21     Dome (Find Park) Find Park started (Search Az 88.0 to 92.0°, Step 0.2°, Narrow) 06:00:03     Dome Find Park found (Best Park Az 90.6°) 06:00:08     Dome Dome has been synced at park position (Az 90.0°, Adjustment: -0.7°) 06:00:10   Dome Parked Dome parked 06:00:24   Dome Charging Dome is parked and re-charging Ok (8mA) 06:00:26 Session Finished Session Finished

Session Alerts & Alarms

Time     Type       Name Detail 06:00:24 Green Clear Dome Charging Dome is parked and re-charging Ok (8mA)

Back to Top

Operational Issues (2025-11-01 S1372)

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

Critical Issues

• None

Major Issues

• None

Minor Issues

• Cloud Sensor III crashed and wouldn't connect to sensor head when restarted. Cloud Sensor III appeared to crash / stopped working a short while after starting it up after AllSky/Weather Computer had restarted following update from Windows 11 23H2 to 25H2. This delayed the start of the S1372 session (whilst waiting for AllSky/Weather ).  Power to CloudSensor was turned off turned on via Zigbee Network and Cloud Sensor program restarted. which seemed to resolve the issue.
  Fixed in-session 2025-11-01 (CloudSensor III)
   
• Occasional continuing problem with AstroLaunch not updating launch program statuses when AstroLaunch gets window focus. Look for alternative (better) method than the one currently used. Copilot has suggested a couple of methods that need to be looked into  Fixed in AstroLaunch 1.13.7 by adding routines that override OnActivated() and OnDeactivate() events.  A separate Continuous Improvement ticket has been raised to make a similar fix/improvement to AstroMove.
  Fixed 2025-11-04 (AstroLaunch 1.13.7)
   
• AstroMag is plotting magnetometer data one hour ahead of correct UT time (2025-11-06). Whilst only just noted today (2025-11-06), AstroMag graphs have been plotting Clair Magnetometer data one hour ahead of correct UT time since daylight savings time ended on Sunday, 2025-10-26  02:00.   Fixed by going into SAM View /Edit /Setup/Logging and changing UTC Offset from 1 (BST) to 0 (GMT). [ Use PC Clock is left enabled ]. A script will need to be built and used to retrospectively correct date/times in AstroMag's data file (mag_data.dat).  A user procedure will need to be used so that UTC offset is modified at the start and end of daylight savings time. A separate Continuous Improvement Ticket has been raised to add a backdoor facility to 'Fix DST Data Issue'.
  Fixed 2025-11-06 (AstroMag, SAM View, User Awareness)
   
• Connection to TCF-Lynx Focuser is being unexpectedly lost (2025-11-02 20:42). Outside of live observing session, connection from AstroMain to TCF-Lynx Focuser data (OTA Temperature & Focuser1 Position) is being unexpectedly lost. The loss of OTA Temperature data was noticed on 2025-11-04 when looking at Observatory/Weather Temperature charts but examination of Monitor data files show data values being lost at around 2025-11-02  20:40-20:42. Report file doesn't record any thing specific happening at this time. Log file records TubeTemperature (OTA) becoming vcNull at 20:40:42.  This was noticed  once before.  Problem resolved in both cases by using the backdoor facility to 'Restart TCF Service'.  Does the TCF-Lynx device or its driver enter a standby state are a certain period of time ? . Monitored,
    Service restarted 2025-10-30 12:16    Connection lost at 2025-10-30 20:32:00. Uptime 8h 16m
  Service restarted 2025-11-02 15:23    Connection lost at 2025-11-02 20:40:42. Uptime 5h 17m
  Service restarted 2025-11-04 17:20    Connection lost at 2025-11-04 23:44:51. Uptime 6h 25m. 
                                          (CcdCamera was Pending from 23:44:01 to 23:44:05 ). 
  Service restarted 2025-11-05 11:40    Closed Service when AstroMain closed in order to updated version to AstroMain 3.73.3,
                    2025-11-05 11:55    Disabled USB Power Management Setting
                                         "Allow the computer to turn off this device to save power".
                    2025-11-05 21:30    Laptop9 restarted
  Service restarted 2025-11-05 23:30    Connection lost at 2025-11-06 18:43:46. Uptime 19h 14m. 
  Service restarted 2025-11-07 01:59    Connection lost at 2025-11-08 08:24, and auto re-started. Uptime 30.4h
                                       
  Service restarted 2025-11-??          Connection lost at 2025-11-17 15:49, and auto re-started. Uptime ???
  Service restarted 2025-11-17 15:50    Connection lost at 2025-11-18 03:49, and auto re-started. Uptime 12.0h
  Service restarted 2025-11-18 03:50    Connection lost at 2025-11-19 03:49, and auto re-started. Uptime 24.0h
  Service restarted 2025-11-19 03:50    Connection lost at 2025-11-20 11:49, and auto re-started. Uptime 32.0h
  Service restarted 2025-11-20 11:50    Connection lost at 2025-11-20 15:49, and auto re-started. Uptime  4.0h
  Service restarted 2025-11-20 15:50    Connection lost at 2025-11-21 06:36, and auto re-started. Uptime 14.77h
  Service restarted 2025-11-21 06:36    Connection lost at 2025-11-21 11:49, and auto re-started. Uptime  5.22h,  24h offset from 2025-11-20 11:50 lost
  Service restarted 2025-11-21 11:50    Connection lost at 2025-11-22 11:10, and auto re-started. Uptime 25.33h
  Service restarted 2025-11-22 11:11    Connection lost at 2025-11-23 06:45, and auto re-started. Uptime 19.57h
  Service restarted 2025-11-23 06:46    Connection lost at 2025-11-23 19:14, and auto re-started. Uptime 12.47h
  Service restarted 2025-11-23 19:14    Connection lost at 2025-11-23 23:14, and auto re-started. Uptime  4.00h
  Service restarted 2025-11-23 23:15    Connection lost at 2025-11-24 11:14, and auto re-started. Uptime 12.00h
  Service restarted 2025-11-24 11:15    ??
    ??                                  Connection lost at 2025-11-27 04:42, and auto re-started. Uptime ??
  Service restarted 2025-11-27 04:43    Connection lost at 2025-11-27 08:42, and auto re-started. Uptime 4.00h
  Service restarted 2025-11-27 08:43    Connection lost at 2025-11-27 12:48, and auto re-started. Uptime 4.00h
  Service restarted 2025-11-27 12:48
                                        Connection lost at 2025-11-29 19:56, and auto re-started.
  Service restarted 2025-11-29 17:56    Connection lost at 2025-11-30 12:41, and auto re-started. Uptime
  Service restarted 2025-11-30 12:41    Connection lost at 2025-11-30 17:36, and auto re-started. Uptime
  Service restarted 2025-11-30 17:36    Connection lost at 2025-11-30 22:31, and auto re-started. Uptime
  Service restarted 2025-11-30 22:31    Connection lost at 2025-12-01 07:11, and auto re-started. Uptime
  Service restarted 2025-12-01 07:11    Connection lost at 2025-12-01 09:24, and auto re-started. Uptime
                                        Connection lost at 2025-12-04 07:27, and auto re-started.
  Service restarted 2025-12-04 07:28 
   
  Issue might relate to Window11 turning off USB ports to save energy during periods of inactivity. Checking properties of USB related devices in Device Manager showed that USB Root Hub (USB 3.0) has a power management setting enabled to "Allow the computer to turn off this device to save power".   The setting was disabled 2025-11-05 11:55 .  Similar settings for 'Generic Superspeed USB Hub','Generic USB Hub', 'Intel USB 3.1 eXtensible Host Controller - 1.10' were modified from Enabled to Disabled.  The Ascom Lynx driver doesn't have a Trace option which would have helped with diagnosis.  TCFLynx Commander indicates that the focuser is using firmware version 3.0.2 (which is the latest firmware). The latest ascom driver is also confirmed to be the latest.  Connection to TCF-Lynx no longer being lost (2025-11-06).  Issue was thought to have been fixed after the uptime on 2025-11-06 had exceeded 18 hours but a further loss of connection to the TCF-Lynx focuser (after 19h 14m) showed that the issue still remains.    "Tube Temperature is vcNull" is written to log file when MonitorFoc1Temperature = vcNull and Obs.bFoc1Connected = True.   MonitorFoc1Temperature is read from Focuser1.PreciseTemperature (and if valid MonitorLastValidFoc1TemperatureTime is updated).   AstroMag 3.78.3 modified in RunObsManager() routine to log exception message when connection to focuser is lost. and ObsManager Main Loop modified to force Focuser1 to be restarted after 60-90s outage, provided its been more than 20 mins since last attempt.  Connection was lost again on 2025-11-08 08:24 but no exception message was logged, however the auto-Restart TCF Focuser process successfully intervened and restarted the TCF Focuser Service.  Issue is deemed to acceptably mitigated and is thereby closed (2025-11-08).   The underlying reason why the focuser connection drops out after the move to Windows 11 remains unclear.  A further 'Allow the computer to turn off this device to save power' setting has been diabled but the computer hasn't yet been rebooted. The times of connection restarts & connection losses will be monitored and logged in the table above to see if there is any pattern. Latency Time in Advanced Settings for COM12 reduced from 16 msec to new value of 4 msec on 2025-11-25 10:00 based on a suggestion from CoPilot.  AstroMag 3.78.9 modified (2025-11-25) to make a diagnosis of the COM12 port when there is a lost of connection to Focuser, which will help determine is problem lies with the USB-Serial Device/driver or with the ASCOM Driver The routine CheckFocuserPort can also be run manually via a new Backdoor button ("Check Foc1 Port") .Issue appears to have been resolved around 2025-12-26 with changes to ObsManager loop in AstroMain 3.79.10 or 3.79.11, but the specific code change that fixed the issue is unclear.
  Fixed 2025-12-31 (Session, Focuser 1, AstroMain 3.79.11)

Small Defects

• Some Detailed JPG pictures are produced without Title or Bottom Description. During session S1372 the 125% cropped detail pictures for following targets didn't have any title or description text drawn on the respective JPG picture:  AT2025aaeg, SN 2025aarn, 29P/Schwassmann-Wachmann, C/2025 K1 (ATLAS).  Thes 4 targets were all ones that didn't have a locate information.  Due to cloud / too few stars none of the Locate frames or first main frame could be image linked. The detail image has still been generated, but without any locate data the detail frame presumably must have assumed that without available data that the target was at the centre of the FOV, and cropped the image accordingly, but without drawing any title/description.  Propose to replay target AT2025aaeg (id :  3651, raw frames : 1372080 - 1372088).  Target replayed on Development Computer on 2025-11-05 which showed that the bug was repeatable. Running it in debugger shows that title(3) and detail(3) are set and an command line is produced
    "C:\Program Files\ImageMagick\magick.exe" "C:\Data\CCD Imaging\New\2025-11-01 S01372\01372084.FIT" -level 21499,22780 -flip -rotate 180 -crop 400x270+164+110 -resize 500x -gravity center -undercolor black -fill white -font arial-bold -pointsize 16 -strokewidth 1 -annotate +518+214 "AT2025aaeg (T+20.4d) (125%%)" -gravity center -undercolor black -fill white -strokewidth 1 -font arial-bold -pointsize 16 -annotate +518+522 "180s, 3x3, C, #1372084 0001, 2025-11-05 12:23 UT" -quality 80 "C:\Data\CCD Imaging\Sessions\2025-11-05 TEST\_JPGS_detail\0014.oid003.1372084.AT2025aaeg.0001_detail.jpg"
  In comparison Replaying AT2023tsk  (Boo, ID: 2974, 1372171-1372177), which was linked ok during centering and annotated title and detail ok,created the following command line :
    "C:\Program Files\ImageMagick\magick.exe" "C:\Data\CCD Imaging\New\2025-11-01 S01372\01372173.FIT" -level 3470,4258 -flip -rotate 180 -crop 400x270+166+122 -resize 500x -gravity center -undercolor black -fill white -font arial-bold -pointsize 16 -strokewidth 1 -annotate +2-139 "AT2023tsk (T+768.4d) (125%%)" -gravity center -undercolor black -fill white -strokewidth 1 -font arial-bold -pointsize 16 -annotate +2+169 "180s, 3x3, C, #1372173 0001, 2025-11-05 13:01 UT" -stroke DeepSkyBlue -fill none -strokewidth 2 -draw "circle 239, 172, 239, 199" -quality 80 "C:\Data\CCD Imaging\Sessions\2025-11-05 TEST\_JPGS_detail\0017.oid006.1372173.AT2023tsk.0001_detail_test.jpg"
  With some experimentation the problem is fixed when using the command line
    "C:\Program Files\ImageMagick\magick.exe" "C:\Data\CCD Imaging\New\2025-11-01 S01372\01372084.FIT" -level 21499,22780 -flip -rotate 180 -crop 400x270+164+110 -resize 500x -gravity center -undercolor black -fill white -font arial-bold -pointsize 16 -strokewidth 1 -annotate +2-153 "Title (125%%)" -gravity center -undercolor black -fill white -strokewidth 1 -font arial-bold -pointsize 16 -annotate +2+156 "Detail" -quality 80 "C:\Data\CCD Imaging\Sessions\2025-11-05 TEST\_JPGS_detail\Test.0001_detail_test.jpg"
Taking the command line, adjusting it and running it in a cmd console shows that the problem relates to the 'annotate' coordinates used for drawing the Title and Detail annotation which doesn't allow for change in '-gravity north' &  '-gravity south' for regular pictures to ''-gravity center' for Detailed images. Fix attempted in AstroMain 3.78.3,  '-annotate +2-153' and '-annotate +2+156' used for Title & Detail when  LocateInfo.x=vcNull or LocateInfo.Y=vcNull. The fix works when replaying AT2025aaeg (not linked) and AT2023tsk (linked), which use 3x3 binned images.  The fix may not work when using 2x2 binned or 1x1 images.
  Fix attempted 2025-11-05 (AstroMain 3.78.3, ConvertFitsToJpg() )
   
• AstroWeather's Laptop 10 & Laptop 11 Connection Flags show unexpected colours. With AstroWeather running on the AllSky/Weather Computer (Laptop7), the active flag for Laptop10 (old Development Computer) shows green, whilst the active flag for Laptop11 (current Development Computer) shows red.  These are shown regardless of whether Laptop11 is currently on and cabable of responding.   Log file shows ping request to Laptop11 is failing with exception, and interpreted as 'not reached'.  Making a making a ping request via cmd terminal results in  'Request timed out' message. It is presumed that the Development Computer is blocking Ping Requests. Copilot used to get the steps required to enable Ping Responses on Windows Firewall. In Windows Defender Firewall ,  create new Inbound Rule, with Rule Type Custom, Program : All Programs, Protcols 7 Ports: Protocol ICMPv4, Customize, Specific ICMP types, check Echo Request, Scope: These Remote IP addresses (subnet) 192.168.1.0/24.
  Fixed 2025-11-05 (AstroWeather,  Development Computer)
   
• An unnamed checkbox sits over the 'Restart TCF Focuser' button on AstroMain's More/Backdoor Tab.  An unnamed check box is sitting above the 'Restart TCF Focuser' button.  This is confusing and not appropriate.  Investigating shows that the checkbox is named 'cboxIncludeTcfsPowerReset' and is functionally active in the RestartTcfFocuser.  Fixed in AstroMain 3.78.3.  Button/field positions on the More/Backdoor tab have been adjusted so that  cboxIncludeTcfsPowerReset checkbox has its own space and has been given the text name "Include Tcf PowerReset".
  Fixed 2025-11-06 (AstroMain 3.78.3)
   
• AstroMain recording 'AllSky/Synopsis' red alerts each morning around daybreak (2025-11-07).  AstroMain is 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 6.1 mins)".   Time of red alert over last 3 days have been as follows
    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
  Issue has been seen before but then disappeared until seen again.  Issue occurs at around daybreak and is seaonable and relates to whether a pause in AstroAllSky looping, that is dependant on rate of Sun Alt change at daybreak takes more than 5 minutes or not.  AstrolAllSky should be modifed so that it forces the update of AllSky Synopsis during the wait period at day break.  Examining the case on 2025-11-07 the the last Synopsis data (5 mins before red alert time) before the outage was at 07:24:13 and the next Synosis data was at 07:29:23  (the time of the green alert).   The later is most-likely associated with record in 2025-11-07 log file recorded as 'Synposis Record : 2025-11-07T07:29:17Z'.  The log file records Synposis Record : 2025-11-07T07:24:12Z'  (around 2s after 'Starting Main Cycle') but this was at 07:29:11 and might have been marked in AstroMain as invalid ?.  Examining the tail of the 2025-11-06 log file shows 'Starting Morning Admin' at 07:24:15.72 after which following Synopsis Records all have the date/time value '2025-11-07T07:24:12Z' .  The Synopsis Record is built and communicated to Observatory Computer by regular calls from ScoreCard Main Loop. however the time value sent is set by code line
  Synopsis.Time = DateTime.UtcNow  in the ScorecardModule.DrawScoreCard.  Hypothesis is that this routine is not called during this period.  Looking at the _Scorecard folder for 2025-11-06 and 2025-11-07 shows that there were no scorcards created/saved between 'Scorecard.20251107.072405.png.png and  'Scorecard.20251107.072912.png.  So fix to issue relies on calling CreateScoreCard() / DrawScoreCard() during the intervening 5-7 minute time window.  SU.ImagingStartStopAltitude is -2.0    .   At 07:24:05 the Sun is at -01 57 27.   At 072912 the Sun is at -01 21 02.   Down-down may be due to VideoCreation time.
    07:24:33.70 | Video Creation Started
  07:28:52.94 | Video Creation Completed
  Fixed attempted in AstroAllSky 3.25.3. BuildAllSkyVideos() routines modified so that a  Synopsis.Time = DateTime.UtcNow code line is placed in CreateAllSkyVideo() after each Video Build. Issue still present on 2025-11-09.  Examination of code showed that there was a flaw in the initially attempted fix. This has now been corrected in AstroMain 3.25.4.
  Fixed 2025-11-09 (AstroAllSky 3.25.4)