David's Astronomy Pages Notes - Session 1459 (2026-10-07)

Notes (S1458)

Notes Main

Home Page

Notes (S1460)

	Session Aims & Highlights
	- Observing Result  - Night Summary Plot  - Session Event Log
	Operational Issues
	- Critical Issues (0),  Major Issues (0),  Minor Issues (3),  Small Defects (3),  Continuous Improvement (6)
	- Figures (0)
	Images from 2026-10-07  >>
	AllSky/Weather Computer Replacement (2026) - Software Installation Plan

Session Aims & Highlights (2026-10-07)

Main aims

1. Targets.  Acquire images of a selection of variable stars, nearby stars, comets & deep sky targets as allowed by sky conditions.
2. AstroMain. Check new AstroMain 3.84.4  version for any issues or problems following introduction of a number of changes.

 Equipment & Software

• 12" LX200 and ST-10XME
• 80mm APO and ZWO ASI 178MC
• TheSky6 6.0.0.65, CCDSoft5 5.0.201, DeviceHub 7.1.0.4707, MeadeGeneric 1.3.12.522, UPB 3, PulsarDome 6.4.0.0
• Peg-Unity 2.12, Peg-Focuser 2.12, Peg-Switch 2.12, TCF-LSI 3.3.5
• SharpCap 3.2.6482, PHD2 2.6.14, Siril 1.4.2, deCONZ 2.18.2, ASCOM 7.1.0.4707
   
• AstroMain 3.84.4, AstroPlan 1.47.4, AstroShCap 1.3.23, AstroGuard 1.13.2
  AstroMag 1.5.12, AstroVOE 2.0.1, AstroSN 1.16.2, AstroProtect 1.7, AstroMove 1.18.7
  AstroWeather 1.31, AstroLaunch 1.14.9
  
  Note:  Not using AstroAllSky,  AstroObsCam or AstroNorthCam (due to failed AllSky/Weather Computer)

Highlights

• Targets. 27/x planned targets were completed with 5 targets partially completed.
•  Dome. No issues open/closing shutter. Dome was successfully parked at the end of the session.

Notes

• Using Observatory in Reduced AllSky/Weather Support Mode

Summary Plots & Logs

Observing Plan

Observing Result

Dome & Scope Slewing Performance

Slew/Centering Performance

Guiding Performance

Sky Conditions (Locate Frames)

Night Sky Summary Plot

Not available

Actual Weather vs Pre-Session Weather Forecast

Not available

Session Event Log

Time     Event Detail 19:49:33 Session Created Session Created (Live, 2026-10-07 S01459) 19:49:35   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.) 19:49:40 Observatory (Manual) Observatory placed in Manual Mode 19:50:01   Scope Switched On Telescope Power has been switched on via UPB Switch 19:50:03 Session Monitoring AutoStart monitoring for Live Session opportunity between 19:49 & 05:50 19:50:05 Observatory (AutoStart) Observatory placed in Auto-Start Mode 19:50:47 Observatory (Manual) Observatory placed in Manual Mode 19:51:01 Session Monitoring AutoStart monitoring for Live Session opportunity between 19:50 & 05:50 19:51:03 Observatory (AutoStart) Observatory placed in Auto-Start Mode 19:51:48   Services Started Observatory Services started 19:51:59 Observatory (Auto) Observatory placed in Fully-Automated Mode 19:52:02 Session Pending Session pending (2026-10-07) 19:52:04 Session Initiating Session initiating (2026-10-07) 19:52:29   Camera1 Connected SBIG Camera connected (Set point -15°C) 19:52:34   Plan Requested Observing Plan requested from AstroPlan (1.47.4) 19:53:25   Plan Loaded Observing Plan loaded to queue (PlanID: 1260) 19:53:40   Telescope Connected Telescope connected (TheSky6) 19:54:05 Session Equilibration Session ready to Open Dome 19:54:19 Observatory (Manual) Observatory placed in Manual Mode 19:54:50   Dome Opened Dome opened (Opening time 46s, Zigbee 40s) 19:55:02   Services Stopped Observatory Services stopped 19:55:39 Program Opened Program Opened (AstroMain 3.84.4) 19:55:48   Obs.Overseer Started Obs.Overseer started 19:56:25   Obs.Manager Started Obs.Manager started 19:56:27   Services Started Observatory Services started 19:56:44 Session Monitoring AutoStart monitoring for Live Session opportunity between 19:56 & 05:50 19:56:46 Observatory (AutoStart) Observatory placed in Auto-Start Mode 19:57:00 Session AutoStarting Session autostarting (19:57) 19:57:06 Session Resumed Session Resumed (Live, 2026-10-07 S01459) 19:57:58   Services Started Observatory Services started 19:58:08 Observatory (Auto) Observatory placed in Fully-Automated Mode 19:58:10 Session Pending Session pending (2026-10-07) 19:58:12 Session Initiating Session initiating (2026-10-07) 19:58:25   Camera1 Connected SBIG Camera connected (Set point -15°C) 19:58:38   Plan Loaded Observing Plan loaded to queue (PlanID: 1260) 19:58:49   Telescope Connected Telescope connected (TheSky6) 19:59:14 Session Running Session running 19:59:17   Queue Started Observing Queue started (32 targets selected) 19:59:23     Target Started (NrZen) Target started (Focus Field 20, HIP 99625) 19:59:37       Dome Unparked Dome unparked 20:03:21       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 20:05:40       Focusing Completed Foc1 AutoFocus Completed (Profile No 1, wide) 20:07:52       Focusing Failed Foc1 focusing failed (failed QC check - RmsE) 20:08:00       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 20:09:50       Focusing Completed Foc2 AutoFocus Completed (Profile No 2, wide) 20:11:38       Focusing Completed Foc2 AutoFocus Completed (Profile No 2) 20:11:59     Target Completed (NrZen) Target completed (Focus Field 20, HIP 99625) 20:12:03     Target Started (1/32) Target started (1/32, GCVS CY Lyr) 20:15:40       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 20:18:14       Focusing Completed Foc1 AutoFocus Completed (Profile No 3, wide) 20:20:03       Focusing Completed Foc1 AutoFocus Completed (Profile No 3) 20:23:53     Target Completed Target completed (1/32, GCVS CY Lyr) 20:23:57     Target Started (2/32) Target started (2/32, Nova Sge 2026) 20:36:47     Target Completed Target partially completed (2/32, Nova Sge 2026) 20:36:51     Target Started (3/32) Target started (3/32, T CrB) 20:44:34     Target Completed Target completed (3/32, T CrB) 20:44:38     Target Started (4/32) Target started (4/32, GCVS AM Her) 20:48:12       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 20:50:43       Focusing Completed Foc1 AutoFocus Completed (Profile No 4) 20:55:26 Session Resumed Session Resumed (Live, 2026-10-07 S01459) 20:55:40     Target Completed Target completed (4/32, GCVS AM Her) 20:55:44     Target Started (5/32) Target started (5/32, NGC 4205 w/SN2026fvx) 21:00:17       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-LSI) 21:16:46     Target Completed Target completed (5/32, NGC 4205 w/SN2026fvx) 21:16:50     Target Started (6/32) Target started (6/32, AT2026lxf (CV)) 21:21:12       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-LSI) 21:27:19     Target Completed Target completed (6/32, AT2026lxf (CV)) 21:28:47     Target Started (7/32) Target started (7/32, CGCG 248-049 w/SN2026aeaq) 21:32:43       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-LSI) 21:49:22     Target Completed Target completed (7/32, CGCG 248-049 w/SN2026aeaq) 21:51:07     Target Started (8/32) Target started (8/32, ZTF26aatyimr) 21:54:49       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 21:57:50       Focusing Completed Foc1 AutoFocus Completed (Profile No 5) 22:12:25     Target Completed Target completed (8/32, ZTF26aatyimr) 22:12:29     Target Started (9/32) Target started (9/32, Nova Aql 2026 (Nova)) 22:16:25       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-LSI) 22:22:26     Target Completed Target completed (9/32, Nova Aql 2026 (Nova)) 22:23:27     Target Started (10/32) Target started (10/32, AT2026nsw (CV)) 22:26:41       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 22:28:55       Focusing Completed Foc1 AutoFocus Completed (Profile No 6) 22:44:57     Target Completed Target completed (10/32, AT2026nsw (CV)) 22:45:28     Target Started (11/32) Target started (11/32, GCVS BL Lac) 22:48:42       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 22:50:53       Focusing Completed Foc1 AutoFocus Completed (Profile No 7) 22:54:40     Target Completed Target completed (11/32, GCVS BL Lac) 22:55:45     Target Started (12/32) Target started (12/32, NGC 7331 w/SN2026aaiv) 22:59:02       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:01:30       Focusing Completed Foc1 AutoFocus Completed (Profile No 8) 23:18:01     Target Completed Target completed (12/32, NGC 7331 w/SN2026aaiv) 23:18:05     Target Started (13/32) Target started (13/32, GCVS HH And) 23:21:16       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:23:37       Focusing Completed Foc1 AutoFocus Completed (Profile No 9) 23:25:29     Target Completed Target completed (13/32, GCVS HH And) 23:26:22     Target Started (14/32) Target started (14/32, M31 w/AT2026aabo) 23:28:48       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (reducing clarity) 23:29:18   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 23:29:20   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 23:29:22     Target Aborted (14/32) Target aborted (14/32, M31 w/AT2026aabo) due to cloud 23:29:24   Queue Paused Queue paused for Session Suspension 23:29:26 Session Suspending Session suspending 23:30:13   Dome Closed Dome closed (Closing time 50s, Zigbee 44s) 23:30:16 Session Suspended Session suspended 23:33:53 Session Resuming Session resuming 23:34:38   Dome Opened Dome opened (Opening time 45s, Zigbee 40s) 23:34:41 Session Running Session running 23:34:43   Queue Resumed Observing Queue resumed 23:34:45     Target Started (14/32) Target started (14/32, M31 w/AT2026aabo) 23:52:34     Target Completed Target completed (14/32, M31 w/AT2026aabo) 23:52:38     Target Started (15/32) Target started (15/32, GCVS RX And) 23:55:44       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:57:53       Focusing Completed Foc1 AutoFocus Completed (Profile No 10) 00:00:26     Target Completed Target completed (15/32, GCVS RX And) 00:00:30     Target Started (16/32) Target started (16/32, IC 167) 00:03:55       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:06:40       Focusing Completed Foc1 AutoFocus Completed (Profile No 11) 00:29:33     Target Completed Target completed (16/32, IC 167) 00:29:37     Target Started (17/32) Target started (17/32, 11P/Tempel-Swift-LINEAR) 00:32:58       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:35:44       Focusing Completed Foc1 AutoFocus Completed (Profile No 12) 00:41:29       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (reducing clarity) 00:42:19   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 00:42:21   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 00:42:24     Target Aborted (17/32) Target aborted (17/32, 11P/Tempel-Swift-LINEAR) due to cloud 00:42:26   Queue Paused Queue paused for Session Suspension 00:42:28 Session Suspending Session suspending 00:43:14   Dome Closed Dome closed (Closing time 50s, Zigbee 44s) 00:43:17 Session Suspended Session suspended 00:45:19 Session Resuming Session resuming 00:46:05   Dome Opened Dome opened (Opening time 45s, Zigbee 41s) 00:46:07 Session Running Session running 00:46:09   Queue Resumed Observing Queue resumed 00:46:12     Target Started (18/32) Target started (18/32, GSC 1224:29) 00:55:48     Target Completed Target completed (18/32, GSC 1224:29) 00:55:53     Target Started (19/32) Target started (19/32, Nova Tau 2026) 01:00:02       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-LSI) 01:06:51       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (reducing clarity) 01:07:16   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 01:07:18   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 01:07:20     Target Aborted (19/32) Target aborted (19/32, Nova Tau 2026) due to cloud 01:07:22   Queue Paused Queue paused for Session Suspension 01:07:24 Session Suspending Session suspending 01:08:12   Dome Closed Dome closed (Closing time 50s, Zigbee 43s) 01:08:15 Session Suspended Session suspended 01:10:17 Session Resuming Session resuming 01:11:02   Dome Opened Dome opened (Opening time 46s, Zigbee 41s) 01:11:05 Session Running Session running 01:11:07   Queue Resumed Observing Queue resumed 01:11:09     Target Started (20/32) Target started (20/32, NGC 1052-DF9) 01:40:15       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (reducing clarity) 01:41:04   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 01:41:06   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 01:41:09     Target Aborted (20/32) Target aborted (20/32, NGC 1052-DF9) due to cloud 01:41:11   Queue Paused Queue paused for Session Suspension 01:41:13 Session Suspending Session suspending 01:42:00   Dome Closed Dome closed (Closing time 50s, Zigbee 44s) 01:42:03 Session Suspended Session suspended 01:48:55 Session Resuming Session resuming 01:49:41   Dome Opened Dome opened (Opening time 45s, Zigbee 41s) 01:49:43 Session Running Session running 01:49:45   Queue Resumed Observing Queue resumed 01:49:47     Target Started (21/32) Target started (21/32, NGC 1052-DF4) 02:04:47       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (reducing clarity) 02:05:22   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 02:05:24   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 02:05:26     Target Aborted (21/32) Target aborted (21/32, NGC 1052-DF4) due to cloud 02:05:28   Queue Paused Queue paused for Session Suspension 02:05:30 Session Suspending Session suspending 02:06:17   Dome Closed Dome closed (Closing time 50s, Zigbee 44s) 02:06:19 Session Suspended Session suspended 02:11:58 Session Resuming Session resuming 02:12:42   Dome Opened Dome opened (Opening time 45s, Zigbee 41s) 02:12:45 Session Running Session running 02:12:47   Queue Resumed Observing Queue resumed 02:12:49     Target Started (21/32) Target started (21/32, NGC 1052-DF4) 02:13:33       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (reducing clarity) 02:15:03       SoftSuspend Cancelled Soft Suspend is cancelled due to improved conditions 02:17:38       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (reducing clarity) 02:18:08   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 02:18:10   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 02:18:13     Target Aborted (21/32) Target aborted (21/32, NGC 1052-DF4) due to cloud 02:18:15   Queue Paused Queue paused for Session Suspension 02:18:18 Session Suspending Session suspending 02:19:08   Dome Closed Dome closed (Closing time 50s, Zigbee 44s) 02:19:11 Session Suspended Session suspended 02:22:44 Session Resuming Session resuming 02:23:29   Dome Opened Dome opened (Opening time 45s, Zigbee 41s) 02:23:32 Session Running Session running 02:23:34   Queue Resumed Observing Queue resumed 02:23:36     Target Started (22/32) Target started (22/32, NGC 1052-DF2) 03:01:16     Target Completed Target completed (22/32, NGC 1052-DF2) 03:01:20     Target Started (23/32) Target started (23/32, 220P/McNaught) 03:04:38       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-LSI) 03:15:20     Target Completed Target completed (23/32, 220P/McNaught) 03:15:54     Target Started (24/32) Target started (24/32, AT2026eva) 03:19:08       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:21:36       Focusing Completed Foc1 AutoFocus Completed (Profile No 13) 03:37:53     Target Completed Target completed (24/32, AT2026eva) 03:38:14     Target Started (25/32) Target started (25/32, C/2022 N2 (PANSTARRS)) 03:41:34       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:44:04       Focusing Completed Foc1 AutoFocus Completed (Profile No 14) 03:52:22     Target Completed Target completed (25/32, C/2022 N2 (PANSTARRS)) 03:52:46     Target Started (26/32) Target started (26/32, UGC 4424 w/SN2026aaee) 03:56:21       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-LSI) 04:12:43     Target Completed Target completed (26/32, UGC 4424 w/SN2026aaee) 04:15:06     Target Started (27/32) Target started (27/32, UGC 4316 w/SN2025advo) 04:19:40       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 04:22:12       Focusing Completed Foc1 AutoFocus Completed (Profile No 15) 04:38:46     Target Completed Target completed (27/32, UGC 4316 w/SN2025advo) 04:38:50     Target Started (28/32) Target started (28/32, GCVS ER UMa) 04:42:54       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-LSI) 04:46:50     Target Completed Target completed (28/32, GCVS ER UMa) 04:47:24     Target Started (29/32) Target started (29/32, NGC 3310 w/SN2026sqf) 04:51:01       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-LSI) 05:07:29     Target Completed Target completed (29/32, NGC 3310 w/SN2026sqf) 05:09:44     Target Started (30/32) Target started (30/32, NGC 2998 w/SN2026acpp) 05:12:53       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 05:15:21       Focusing Completed Foc1 AutoFocus Completed (Profile No 16) 05:31:39     Target Completed Target completed (30/32, NGC 2998 w/SN2026acpp) 05:32:04     Target Started (31/32) Target started (31/32, GCVS RZ LMi) 05:36:03       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 05:38:16       Focusing Completed Foc1 AutoFocus Completed (Profile No 17) 05:43:31     Target Completed Target completed (31/32, GCVS RZ LMi) 05:43:42     Target Started (32/32) Target started (32/32, NGC 3861 w/SN2026ihi) 05:50:01       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-LSI) 06:06:12     Target Completed Target completed (32/32, NGC 3861 w/SN2026ihi) 06:06:14   Queue Completed Job Queue completed 06:06:16 Session Closing Session closing 06:07:04   Dome Closed Dome closed (Closing time 49s, Zigbee 44s) 06:07:21   Dome Parked Dome parked (parking time 10s), Az: 90.0 deg 06:08:12   Telescope Parked Telescope parked (parking time 45s total) 06:08:36   Telescope State Handbox reads 'Scope parked Turn scope off.' 06:09:33   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 06:10:26   Services Stopped Night Services stopped 06:10:29 Session Finishing Session Finishing started (Create Fits Summary, Transfer Files) 06:11:46     Dome (Find Park) Find Park started (Search Az 88.0 to 92.0°, Step 0.2°, Narrow) 06:12:36     Dome Find Park found (Best Park Az 90.6°) 06:12:42     Dome Dome has been synced at park position (Az 90.0°, Adjustment: -0.6°) 06:12:44   Dome Parked Dome parked 06:12:54   Dome Charging Dome is parked and re-charging Ok (11mA) 06:12:56 Session Finished Session Finished

Session Alerts & Alarms

Time     Type       Name Detail 06:12:54 Green Clear Dome Charging Dome is parked and re-charging Ok (11mA)

Back to Top

Operational Issues (2026-10-07 S1459)

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

[ Prev | Next ]

Critical Issues

• None

Major Issues

• None

Minor Issues

• Unable to begin Autostart due to Cloud, when clarity was 36.5 (19:28).  An attempt to begin Autostart at 19:28 was reported to be not allowed 'due to Cloud'. The Sky Conditions indicate Clarity 36.5, Rain 0, so the conditions were fine, so why couldn't Autostart proceed. CloudSensor data supply was ok. To investigate. There was nothing preventing AstroMain from opening the Dome on Development Computer shortly after using same data, so why the message preventing Autostart from proceeding on the Observatory Computer. Issue resolved in session but no without complications / program restart.   It's thought that the 'Due to Cloud' was a false reason, and the likely reason was 'Waiting For SunAlt/Time' to start, but came across as 'Due to Cloud' for some reason, code need reviewing again. The program has a current Start Autostart Window setting of SunAlt -11° minus 20 mins. At 19:28 SunAlt was only -9.23°,   Sun Alt -11° was at 19:42, so the scheduled Start of AutoStart Window would be at around 19:22. In the event the AutoStart monitoring deemed that conditions were finally suitable to start the session at 19:49 (when Clarity was 36.0). Issue reviewed but the reason why autostart wouldn't commence between 19:28 and 19:48 is unexplained. Issue closed after review 2026-10-10
   Unexplained 2026-10-10 (Session, AstroMain, AstroWeather, Cloud Sensor)
   
• Observatory Manager reporting 'AutoStart Thread is busy' (19:50).  After the unexpected 'Cannot begin AutoStart at 19:28 due to Cloud' message the session was returned to Manual using the 'Manual' button, and a new attempt made to initiate AutoStart.  This resulted in a message ">ObsManager   AutoStartThread is busy."   The AutoStart button may or may not have been clicked again.   A series of AutoStarting messages appeared and there was interlacing of messages suggesting that two Autostarting operations were taking place in parallel.   The Session was aborted, and AstroMain was closed and restarted, and Autostart initiated again. This time AutoStart proceeded as normal.  Whilst issue resolved in-session, investigation should be made to understand what happened and why two AutoStarts were seemingly allowed to run at the same time.  Reviewing the Observatory Report revealed that the problem was essentially due to user error, but the program could have been a little more helpful. The timeline was
   19:28 AutoStart Monitoring started (Clarity 36.5)
 19:28 "Unable to begin Autostart as 19:28 due to Cloud". 
 19:28 "Waiting till conditions are fully suitable for Observing"
 19:49 "AutoStart Check at 19:49 (Clarity 36.0)
 19:49 "Conditions at 19:49 are suitable for starting an Observing Session"
 19:49 "Starting Autostart at 19:49" / "Restarting CCDSoft to set Autosave No"
 19:49 User Clicked 'Manual' button
 19:50 "Setting Mode: Autostart" - suggests user had probably clicked Autostart again
 19:50 "Autostart Monitoring begun /
 19:50  "Starting AutoStart at 19:50 / Alert "AutoStartThread us busy, cannot resubmit AutoStartSession
 19:51 Original AutoStart process progressed to Starting Stage and begun opening the dome (there was no interlacing / no parallel operations)
 19:52 Thinking (incorrectly) there was interlacing from two autostart operations, user click manual, close the session/program, and then restarts
   The timeline shows
  - the user needlessly went to manal / needlesly submitted a further Autostart operation at 19:59/19:50 as the original AutoStart had already started.
- the ObsManager / system correctly rejected the second attempt to autostart
  (there was minor interlacing, but only to say that the 'second' AutoStartSession couldn't be resubmitted)
- The user needlessly went to manual a second time and needlessly restarted the AstroMain program
- Messages and timing could have been clearer / quicker .
  Issue resolved in-session without material impact.  A separate Continuous Ticket is raised to examine/improve the messages reported.
   Resolved in session  2026-10-07 (Session, AstroMain, User Awarenss)
   
• Remote VNC Connection to Observatory Computer went to full-screen and it was unclear how to resort to a normal view. Ultra VNC unexpectedly went to full-screen.  Eventually researched and found that Cntl-Alt-F12 was the keypad operation to put VNC session back to windowed view.
   Resolved in session (Session, UltraVNC, User Awareness)

Small Defects

• AstroMain's COM Port Listing shows COM 11 put without any associated Device name .  When CloudSensor was installed it went on COM11.  AstroMain should be updated so theat if present it should list the name as CloudSensor to make it clearer what is using COM11. Fixed in AstroMain 3.84.6.  Port given name 'CloudSensor' with description "(temporary port)".
   Fixed 2026-10-08 (AstroMain 3.84.5)
   
• Three CcdCamera GetProperty calls timed-out during the session at common points in Job Execution Sequence (20:47, 00:31, 01:16). Error Logs from the S1459 Session show that there were three CcdCamera GetProperty time-out events.  None of these progressed to becoming  a CcdCamera freeze, but they share a common origin so it is worth documenting their occurance. The three events were :
   - GetFilterIndexZeroBased at 20:47:00.22 on Target 4/31
 - GetFilterIndexZeroBased at 00:31:42.59 on Target 17/32
 - GetTemperatureSetProperty / GetState at 01:16:24.32 on Target 20/31
  These all occurred at the same point in the Job Execution Sequence where a 12.2 MB Guider Reference Image (10s exposure) shot using TS80/Cam2 using SharpCap was being opened in CCDSoft for Plate Solving.  Only 3 of 31 targets suffered from the issue so the problem likely represent a timing edge case. The sequence of operations associated with the first of these events (but also representative of the other two events) is shown below:
    20:46:56.22  Approx time of call GetFilterIndexZeroBased (~2s before timeout)
  20:46:56.94  Capture Single Frame    Ok    Single Frame has been taken (exp 10s)
  20:46:57.17  Save GuideFrameImage    Ok    Image Saved (Guider Saved  Guider.20261007... Guide04.Ref10.FIT)
  20:47:00.22  GetProperty             Fail  GetFilterIndexZeroBased   timed out after 2s
The precise time that the FIT image was opened in CCDSoft isn't logged but is likely to have been just after the 'Save GuideFrameImage' message. In this case 1 example the estimated call point  came 65s after 'Save Guide FrameImage'  message (in case 2 call point was 0.73s after the   'Save Guide FrameImage'  message whilst in case 3 the call point was 51s after). The occurance seems to be due to CCDSoft being busy opening a large image file and seemingly therefore unable to serve the particular GetProperty request in a timely manner.  Possibilities are to suspend GetProperty Ccd Requests at around this point in the Job Execution or except the occasional Time-Out error. WriteGetPropertyTimeOut() routine modified in AstroMain 3.84.6 to make the 2s time-out log message to be an orange '(warn)' message rather than a red '(error)' message if Flag.bOpeningGuideReferenceFrame is raised (which is raised/lowered in ImageAndLink_PHD2() routine).   The attempted fix in AstroMain 3.84.6 is not totally successful and final improvement/fix made in AstroMain 3.46.7. But even these didn't resolve the issue. Added similar fix/modification to LinkCam2GuideFrame () in AstroMain 3.84.9. Following session showed that occassionally a red "CcdCamera pending (2s)" log message occurs at the time that the GetProperty calls time-out.  Later investigation demonstrated that the timeouts occurred whilst an Image.InsertWCS was being performed on Cam2Reference image. AstroMain 3.84.10 modified to make  GetProperty timeouts during this time have orange '(warn)' log messages.
   Fixed 2026-10-12 (Session, AstroMain 3.84.7 - AstroMain 3.84.9, CCDSoft, User Awareness)
   
• Unable to perform Photometric Analysis on RX And Image (post-session). During VMA analysis of photometric dataset the 10s V and 8s R images from RX And (acquired at -20°C) couldn't be plate solved using UCA/USNO and GSC link methods (nObjects 90-155, nStars 40-52) and were solved using ASTAP instead. After setting Detection Threshold to 2, the nObjects value rose to 2000-3000 with multiple pin-point false stars.  Whilst C and K stars were found the V Star (RX And) couldn't be found , nearest star offset of 20-35" were rejected. To investigate. Is there an issue with the RX And coordinates being employed or is this an image / dark / flat issue. RX And is clearly visible in Locate Frame - compare Locate Frame (Fig 1) with Reference Image (Fig 2).  Analysis during earlier S1457 session showed star offset errors of only 0.4-0.6". Issue closed as unexplained.
   Unexplained 2026-10-07 (Session, AstroMain/VMA)

Continuous Improvement

• Install AstroNorthCam program onto Observatory Computer to allow the NorthCam view to be seen. Whilst the AllSky/Weather Computer is out of action, the usual remote sight of the night sky / automated star counts information is limited to looking out of the window.  One interim option is to use the Observatory's NorthCam Camera (Tapo C325WB NightVision Camera) which is accessible via IP and doesn't require any wiring modifications in order to be accessed from the Observatory Computer.  iSpy 64 software was installed and configured on the Observatory Computer on 2026-10-08.  It is now proposed to install AstroNorthCam on to the Observatory Computer.  This was done on 2026-10-09.and after some teething issues (involving an RawIngest is nothing exception in NorthCam' outer catch requiring fix in AstroNorthCam 1.13.2)  main imaging was able to be successfully run. There was an issue running Metaframe with error "Grab Folder not found" but this was fixed by creating the expected folder (..\TapoCam\Metaframe\Raw Frames)
   Done  2026-10-09 (Observatory Computer, AstroNorthCam, NorthCam)
   
• Relocate WebUpload functionality from AstroAllSky to AstroWeather. For historical reasons AstroAllSky has had the function of uploading web files/images from the AllSky/Server folder on the AllSky/Weather Computer to the Observatory Web Site. However at the moment AstroAllSky program isn't being run due to the failed AllSky/Weather Computer and this program can't be readily run on the Observatory Computer because of its required dedicated Camera Control in CCDSoft which would clash with SBIG Camera requirements from AstroMain program.  The AllSky/Weather Computer is expected to be replaced and functioning to the end of October.  AstroWeather and now AstroNorthCam are running on the Observatory computer and there is a lot of data that isn't getting uploaded to the Observatory WebSite: Weather/Environment Charts, and now NorthCam images and videos.  It is proposed to relocate AstroAllSky's WebUpload functionality into AstroWeather, making the latter responsible for upload of all AllSky/Weather/NorthCam data to the Observatory WebSite.  This will involve creating a new service in AstroWeather, copying in WebUpload routines, and including referencing and use of WinSCP.  In due course and before the new AllSky/Weather Computer comes into operation, AstroAllSky needs to be modified to remove its Web Upload functionality (see separate ticket below).  Once AstroWeather's WebUpload Service is working, the 'Include Laptop7 files' facility in AstroPlan can be removed.  Implemented in AstroWeather 1.32.1
   Done 2026-10-09 (AstroWeather 1.32.1, AstroAllSky)
   
• Develop new (possibly temporary) procedure for delivering NorthCam Star Count to AstroMain.   Currently in AstroMain 3.84.6 / AstroNorthCam 1.13.2 and earlier versions the NorthCam Star Count is transferred to AstroMain via the AstroAllSky program and Synopsis/Scorecard Record. However in the current situation where the AllSky/Weather Computer is not operational (pending arrival and setup of a replacement computer at end Oct) the AstroAllSky program isn't being run and therefore the NorthCam StarCount isn't being delivered to AstroMain, even though AstroNorthCam is now running again (as of 2026-10-09) and producing a Star Count values.   Options to deliver NorthCam Star Count are :
   a) by file (Latest.NorthCamStarCount.dat)
 b) by UPD Chat (port 5000)
 c) by a custom Scorecard record
  Currently AstroNorthCam write Star Count to  "C:\Data\AllSky Imaging\Latest\Latest.NorthCamStarCount.dat" which is read by AstroAllSky, and therefore given that AstroNorthCam is currently running on the same computer as AstroMain, an interim solution is for AstroMain to simply read this file and import NorthCamStarCount. This won't be suitable as a longer term procedure once AstroNorthCam goes back to running on the AllSky/Weather Computer. Use of a pseudo Scorecard (blank scorecard fields  + NorthCamStarCount field) is probably the most difficult to implement.  Implemented in AstroMain 3.84.6
   Done 2026-10-09 (AstroMain 3.84.6, AstroNorthCam)
   
• Clean-up AstroAllSky after relocate WebUpload functionality to AstroWeather. AstroAllSky's WebUpload functionality has been moved to AstroWeather 1.32 / 1.32.1 and is successfully operating in its new location.  AstroAllSky nowq needs to be modified to remove its Web Upload functionality. Implemented in AstroAllSky 3.29.
   Done  2026-10-12 (AstroAllSky 3.29)
   
• Examine the response to user clicking Manual whilst Autostart Session was running and the clarity of the messages.  After the unexpected 'Cannot begin AutoStart at 19:28 due to Cloud' message the session was returned to Manual using the 'Manual' button at 19:50, and a new attempt made to initiate AutoStart.  This resulted in a message ">ObsManager   AutoStartThread is busy."   The AutoStart button may or may not have been clicked again.   A series of AutoStarting messages appeared and there was interlacing of messages suggesting that two Autostarting operations were taking place in parallel.   The Session was aborted, and AstroMain was closed and restarted, and Autostart initiated again. This time AutoStart proceeded as normal.  Whilst issue resolved in-session, investigation should be made to understand what happened and why two AutoStarts were seemingly allowed to run at the same time.  A review showed that the problem was essentially due to user error, but the program could have been a little more helpful. Extra guard added to btnSetAutoStartObservatoryMode in AstroMain 3.84.6 to ensure that Session State isn't already AutoWaiting/AutoStarting
   Done 2026-10-10 (AstroMain 3.84.6)
   
• Create a Session Chart showing Guiding Quality (RMS Error) vs Session Time.   It would be useful to see a chart showing Guiding Quaity through the session.  Charts show probably show the Median of average RMS across all Target frames, with an 'error' or 'range' bar showing the range in Av RMS by individual frame.  Additional chart options might be Guiding Quality (Av RMS) vs Hour Angle. Annotations could protentially show the Target Name and/or Altitude. Due to the large range of Av Rms value it is proposed to make the Y-Axis (RMS) have a log scale from 0.1 to 100.   A new chart 'GuideQualityChart' was implemented in AstroMain 3.84.8 and was tested in second part of S1462 Session on 2026-10-11. Whilst the graph was setup, started and extended ok, it was devoid of expected data points, even though prior testing had plotted test data.   Bug fixed in AstroMain 3.84.9.  The new Guiding Quality Chart was first fully used in session S1463 (2026-10-13) - see Fig 3 below.
   Done  2026-10-12 (AstroMain 3.84.9)

[ Prev | Next ]

Back to Top Issue,  Back to Top

[ Prev | Next ]

Back to Top Issue,  Back to Top