David's Astronomy Pages Notes - Session 1457 (2026-10-01)

Notes (S1456)

Notes Main

Home Page

Notes (S1458)

	Session Aims & Highlights
	- Observing Result  - Night Summary Plot  - Session Event Log
	Operational Issues
	- Critical Issues (0),  Major Issues (0),  Minor Issues (1),  Small Defects (6),  Continuous Improvement (4)
	- Figures (0)
	Images from 2026-10-01  >>

Session Aims & Highlights (2026-10-01)

Main aims

1. AstroMain. Check new AstroMain 3.83.14  version for any issues or problems associated with changes to RestartCCDSoftCamera() and changes to allow an Observing Session run without normal support from AllSky/Weather Computer (Laptop7)
    
2. Reduced Support Mode. Carry out Live Session to demonstrate that an observing session can be carried out without normal AllSky/Weather Computer support by using local CloudSensor / AstroWeather support instead.
   
   The AllSky/Weather Computer failed on 2026-09-28, and is not yet repaired or replaced. This would normally prevent a live Observing Sesson from taking place, but by patching the CloudSensor through to the Observatory Computer and changes to AstroWeather and AstroMain, it seems feasible to run a session based on CloudSensor values alone, without Weather Date/AllSky Star Count/NorthCam Star Count provided the weather forecast is dry.
    
   
3. 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, 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.83.14, AstroPlan 1.47.2, 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.4
  AstroWeather 1.30.5, AstroLaunch 1.14.9
  
  (No AstroAllSky),  (No AstroObsCam), (No AstroNorthCam)  - due to failed AllSky/Weather Computer

Highlights

• Targets. 11/18 planned targets were completed with 2 targets partially completely. Other targets failed due to cloud / session suspension
• AstroMain. New version of AstroMain (3.83.14) operated without any serious issues.
• Reduced Support Mode.  The Session proved that it was possible to run a live session with AllSky/Weather Computer support, further improvements can be made to suppress certain errors messages, and support weather forcast access.
• CCDSoft Camera. Camera operated normally with not image failures.  There were 'Image not saved' messages associated with LocateFrame1 and FocusLocate frames, but these were all false alerts.
• CloudSensor.  Cloud sensor operated fine for first part of session, but produced a data glitch that caused the ObsManager to think it was raining when it wasn't
•  Dome. No issues open/closing shutter. Dome was successfully parked at the end of the session.

Notes

• Session run without normal AllSky/Weather Computer support

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)

Not available

Actual Weather vs Pre-Session Weather Forecast  Not Available

Session Event Log

Time     Event Detail 23:35:08 Session Monitoring AutoStart monitoring for Live Session opportunity between 23:35 & 05:38 23:35:09 Session AutoStarting Session autostarting (23:35) 23:35:15 Session Created Session Created (Live, 2026-10-01 S01457) 23:35:17   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.) 23:35:43   Camera1 Connected SBIG Camera connected (Set point -15°C) 23:35:58   Scope Switched On Telescope Power has been switched on via UPB Switch 23:37:45   Services Started Observatory Services started 23:37:54 Observatory (Auto) Observatory placed in Fully-Automated Mode 23:37:59 Session Pending Session pending (2026-10-01) 23:38:01 Session Initiating Session initiating (2026-10-01) 23:38:14   Camera1 Connected SBIG Camera connected (Set point -15°C) 23:38:21   Plan Requested Observing Plan requested from AstroPlan (1.47.2) 23:39:07   Plan Loaded Observing Plan loaded to queue (PlanID: 1258) 23:39:48   Telescope Connected Telescope connected (TheSky6) 23:40:12 Session Equilibration Session ready to Open Dome 23:40:58   Dome Opened Dome opened (Opening time 45s, Zigbee 40s) 23:41:00 Session Running Session running 23:41:02   Queue Started Observing Queue started (18 targets selected) 23:41:07     Target Started (NrZen) Target started (Focus Field 23, HIP 113729) 23:41:22       Dome Unparked Dome unparked 23:42:29       CCDSoft Issue CCDSoft has encountered an image save issue [0000] 23:44:30       CCDSoft Issue CCDSoft has encountered an image save issue [0000] 23:44:42       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:46:55       Focusing Completed Foc1 AutoFocus Completed (Profile No 1, wide) 23:48:49       Focusing Completed Foc1 AutoFocus Completed (Profile No 1) 23:48:57       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 23:50:50       Focusing Completed Foc2 AutoFocus Completed (Profile No 2, wide) 23:52:31       Focusing Completed Foc2 AutoFocus Completed (Profile No 2) 23:52:51     Target Completed (NrZen) Target completed (Focus Field 23, HIP 113729) 23:54:49     Target Started (1/18) Target started (1/18, Nova Aql 2026 (Nova)) 23:55:53       CCDSoft Issue CCDSoft has encountered an image save issue [0000] 23:58:38       CCDSoft Issue CCDSoft has encountered an image save issue [0000] 23:58:51       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-LSI) 00:04:55     Target Completed Target completed (1/18, Nova Aql 2026 (Nova)) 00:07:09     Target Started (2/18) Target started (2/18, GCVS BL Lac) 00:08:10       CCDSoft Issue CCDSoft has encountered an image save issue [0000] 00:10:21       CCDSoft Issue CCDSoft has encountered an image save issue [0000] 00:10:30       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:12:34       Focusing Completed Foc1 AutoFocus Completed (Profile No 3) 00:16:23     Target Completed Target completed (2/18, GCVS BL Lac) 00:17:27     Target Started (3/18) Target started (3/18, NGC 7331 w/SN2026aaiv) 00:18:30       CCDSoft Issue CCDSoft has encountered an image save issue [0000] 00:20:42       CCDSoft Issue CCDSoft has encountered an image save issue [0000] 00:20:52       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:23:09       Focusing Completed Foc1 AutoFocus Completed (Profile No 4) 00:39:10     Target Completed Target completed (3/18, NGC 7331 w/SN2026aaiv) 00:39:47     Target Started (4/18) Target started (4/18, UGC 242 w/SN2026yum) 00:40:52       CCDSoft Issue CCDSoft has encountered an image save issue [0000] 00:43:38       CCDSoft Issue CCDSoft has encountered an image save issue [0000] 00:43:47       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:45:59       Focusing Completed Foc1 AutoFocus Completed (Profile No 5) 00:57:09   Critical Rain Alert Critical Rain Alert (Obs.Manager will close the Dome) 00:57:11   HardSuspend Called Hard Suspend called due to Critical Conditions (rain) 00:57:14     Target Aborted (4/18) Target aborted (4/18, UGC 242 w/SN2026yum) due to rain 00:57:16   Queue Paused Queue paused for Session Suspension 00:57:18 Session Suspending Session suspending 00:58:00   Dome Closed Dome closed (Closing time 51s, Zigbee 43s) 00:58:02 Session Suspended Session suspended 00:59:03     Target Cancelled Target cancelled (4/18, UGC 242 w/SN2026yum) due to recent rain 01:12:56 Session Resuming Session resuming 01:13:41   Dome Opened Dome opened (Opening time 45s, Zigbee 40s) 01:13:44 Session Running Session running 01:13:46   Queue Resumed Observing Queue resumed 01:13:48     Target Started (5/18) Target started (5/18, UGC 279 w/SN2026zyf) 01:14:46       CCDSoft Issue CCDSoft has encountered an image save issue [0000] 01:20:01       CCDSoft Issue CCDSoft has encountered an image save issue [0000] 01:26:43     Target Completed Target partially completed (5/18, UGC 279 w/SN2026zyf) 01:26:47     Target Started (6/18) Target started (6/18, Gliese 65) 01:28:02       CCDSoft Issue CCDSoft has encountered an image save issue [0000] 01:30:27       CCDSoft Issue CCDSoft has encountered an image save issue [0000] 01:30:36       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:33:03       Focusing Completed Foc1 AutoFocus Completed (Profile No 6) 01:39:44     Target Completed Target completed (6/18, Gliese 65) 01:39:48     Target Started (7/18) Target started (7/18, NGC 383) 01:40:56       CCDSoft Issue CCDSoft has encountered an image save issue [0000] 01:42:57       CCDSoft Issue CCDSoft has encountered an image save issue [0000] 01:43:07       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:45:48       Focusing Completed Foc1 AutoFocus Completed (Profile No 7) 02:02:35     Target Completed Target completed (7/18, NGC 383) 02:02:40     Target Started (8/18) Target started (8/18, NGC 507) 02:03:32       CCDSoft Issue CCDSoft has encountered an image save issue [0000] 02:05:39       CCDSoft Issue CCDSoft has encountered an image save issue [0000] 02:05:48       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:07:48       Focusing Completed Foc1 AutoFocus Completed (Profile No 8) 02:24:34     Target Completed Target completed (8/18, NGC 507) 02:24:38     Target Started (9/18) Target started (9/18, 11P/Tempel-Swift-LINEAR) 02:25:32       CCDSoft Issue CCDSoft has encountered an image save issue [0000] 02:27:25       CCDSoft Issue CCDSoft has encountered an image save issue [0000] 02:27:33       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:30:00       Focusing Completed Foc1 AutoFocus Completed (Profile No 9) 02:38:12     Target Completed Target completed (9/18, 11P/Tempel-Swift-LINEAR) 02:38:16     Target Started (10/18) Target started (10/18, GCVS RX And) 02:39:11       CCDSoft Issue CCDSoft has encountered an image save issue [0000] 02:43:07       CCDSoft Issue CCDSoft has encountered an image save issue [0000] 02:43:16       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:45:31       Focusing Completed Foc1 AutoFocus Completed (Profile No 10) 02:48:11     Target Completed Target completed (10/18, GCVS RX And) 02:48:15     Target Started (11/18) Target started (11/18, NGC 488) 02:49:28       CCDSoft Issue CCDSoft has encountered an image save issue [0000] 02:51:43       CCDSoft Issue CCDSoft has encountered an image save issue [0000] 02:51:51       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:54:23       Focusing Completed Foc1 AutoFocus Completed (Profile No 11) 03:10:22     Target Completed Target completed (11/18, NGC 488) 03:10:26     Target Started (12/18) Target started (12/18, M31 w/AT2026aabo) 03:11:28       CCDSoft Issue CCDSoft has encountered an image save issue [0000] 03:14:05       CCDSoft Issue CCDSoft has encountered an image save issue [0000] 03:14:13       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-LSI) 03:30:21     Target Completed Target completed (12/18, M31 w/AT2026aabo) 03:30:25     Target Started (13/18) Target started (13/18, 220P/McNaught) 03:31:39       CCDSoft Issue CCDSoft has encountered an image save issue [0000] 03:34:22       CCDSoft Issue CCDSoft has encountered an image save issue [0000] 03:34:32       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-LSI) 03:45:37     Target Completed Target completed (13/18, 220P/McNaught) 03:46:58     Target Started (14/18) Target started (14/18, GCVS RZ LMi) 03:48:33       CCDSoft Issue CCDSoft has encountered an image save issue [0000] 03:53:52       CCDSoft Issue CCDSoft has encountered an image save issue [0000] 03:54:00       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:54:40   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 03:54:42   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 03:54:44       Focusing Aborted Foc1 Focusing Aborted 03:54:46     Target Aborted (14/18) Target aborted (14/18, GCVS RZ LMi) due to cloud 03:54:48   Queue Paused Queue paused for Session Suspension 03:54:50 Session Suspending Session suspending 03:55:31   Dome Closed Dome closed (Closing time 45s, Zigbee 43s) 03:55:34 Session Suspended Session suspended 03:57:02     Target Cancelled Target cancelled (14/18, GCVS RZ LMi) due to cloud 04:17:52     Target Cancelled Target cancelled (15/18, NGC 3310 w/SN2026sqf) due to recent rain 04:40:12     Target Cancelled Target cancelled (16/18, NGC 2998 w/SN2026acpp) due to rain 05:02:33     Target Cancelled Target cancelled (17/18, NGC 3437 w/SN2026kie) due to recent rain 05:34:52     Target Cancelled Target cancelled (18/18, NGC 3689 w/SN2026gwx) due to cloud 05:34:56   Queue Completed Job Queue completed 05:35:00 Session Closing Session closing 05:35:02   Dome Closed Dome already closed (closed at 03:55, closing time 45s, zigbee 43s) 05:35:25   Dome Parked Dome parked (parking time 13s), Az: 90.0 deg 05:36:16   Telescope Parked Telescope parked (parking time 43s total) 05:36:40   Telescope State Handbox reads 'Scope parked Turn scope off.' 05:37:31   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 05:38:57   Services Stopped Night Services stopped 05:39:00 Session Finishing Session Finishing started (Create Fits Summary, Transfer Files) 05:39:32     Dome (Find Park) Find Park started (Search Az 88.0 to 92.0°, Step 0.2°, Narrow) 05:40:17     Dome Find Park found (Best Park Az 90.3°) 05:40:23     Dome Dome has been synced at park position (Az 90.0°, Adjustment: -0.3°) 05:40:25   Dome Parked Dome parked 05:43:25   Dome Charging Dome is parked and well charged (96%, 15.0v) 05:43:27 Session Finished Session Finished

Session Alerts & Alarms

Time     Type       Name Detail 23:42:29 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 23:44:30 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 23:55:53 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 23:58:38 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 00:08:10 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 00:10:21 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 00:18:30 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 00:20:42 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 00:40:52 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 00:43:38 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 00:57:09 Red Alarm Dome Unsafe CloudSensor detects Rain, but Shutter Sensor is open 00:57:54 Green Clear Dome Safe Shutter Sensor indicates that Dome is now closed 01:14:46 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 01:20:01 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 01:28:02 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 01:30:27 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 01:40:56 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 01:42:57 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 02:03:32 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 02:05:39 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 02:25:32 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 02:27:25 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 02:39:11 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 02:43:07 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 02:49:28 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 02:51:43 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 03:11:28 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 03:14:05 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 03:31:39 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 03:34:22 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 03:48:33 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 03:53:52 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 05:43:25 Yellow Alert Dome Charging Dome is parked and well charged (96%, 15.0v) 06:40:42 Green Clear Dome Charging Dome is parked and re-charging Ok (13mA)

Back to Top

Operational Issues (2026-10-01 S1457)

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

[ Prev | Next ]

Critical Issues

• None

Major Issues

• None

Minor Issues

• Session was unexpectedly suspended due to critical Rain alert caused by a glitch in CloudSensor data (00:57).   A Critical Rain Condition/Alert was raised by ObsManager at 00:57:09 and a Red 'Dome Unsafe' Alert raised with the message "CloudSensor detects Rain, but Shutter Sensor is open" . A bHardSuspend flag was raised and the Observatory Dome was immediately commanded to shut and the session suspended.  Dome was fully closed by 00:57:54.  The system operated as per design.  However the closure was unexpectedly as skies were clear at the time. The Critical Rain Condition was raised because the raw Rain value jumped from -220 to 0.0 which was interpreted as Rain with value of  25.3. This is a new issue with CloudSensor III since installing the Cloud Sensor's USB-Serial adapter as COM 11 on the Observatory Computer.   Cloud Sensor values will be stable for several hours (2+), but then become unstable which can only be resolved by restarting the CloudSensor III program. A fix for the underlying issue is still being sought. In the mean time a possible workaround is to introduce handing to kill and restart CloudSensor III program every 2 hours.    To fix or workaround in AstroMain 3.84+. . Underlying issue seems to have been resolved (possibly solved by Computer Restart). CloudSensor values have now been stable for >24 hours. Issue deemed to have been resolved and ticket can be closed.
   Resolved 2026-10-03 (Observatory Computer, AstroMain 3.84, CloudSensor III)

Small Defects

• Mutiple cases reporting "CCD Image [0000] not saved to disk" seem to be all false (23:42 - 00:20) . There were multiple cases through the course of the session where the Job Executor reported an alert with message "CCD Image [0000] not saved to disk. Restarting CCDSoft", however the image appears to have been saved and used in a completely normal manner. This suggests that the report message are a false alerts. In total there was a total of 30 such alerts during the session between 23:42 and 03:53.  Changes were made in AstroMain 3.83.14 to resolve certain CCDSoft/Camera issues in the last session (S1456, 2026-09-27), and these false alerts may be an un-intended consequence of code changes. These  'false' message included ones at the following times :  23:42, 23:44, 23:55, 23:58, 00:08, 00:10, 00:18, 00:20 (other cases not listed). These occurances correspond exclusively with 'Locate Frame 1' and 'Focus Locate Frame' images. These false alerts don't occur with LocateFrame2, LocateFrame3,  FocusFrames or Main Frames. Fixed in AstroMain 3.84, the call to ' SignalUnsavedImageFile() removed.from TakeImage(). A functionally similar routine 'SignalFailedImage()' has been incorporated into failure case reporting for recording failure events / alerts in the database. The following S1458 Session (2026-10-02) using the new AstroMain 3.84 version confirmed that fix was working.
   Fixed 2026-10-02 (Session, AstroMain 3.84)
   
• AstroMain's Log file contains multiple error messages associated with the AllSky/Weather Computer being missing from the LAN network. The presence of a connected AllSky/Weather Computer was previously deemed critical for operating a live Observatory Session, but as the AllSky/Weather has failed and is away for repair and possible replacement, modifications have been made on the Observatory Computer side to permit a live session to be made in the meantime, including installing / connecting the CloudSensor and installing/running AstroWeather in a reduced service mode. The session ran ok, but there are some teething issues/unwanted side effects including varous exceptions associated the missing AllSky/Weather Computer (LAPTOP7):
   - Exception in Telecomms.SetIPAddress 'No such host is known'
 - Exception in ObsEnv.SetIPAddress ' No such host is known'
 - Exception: An exception occurred during a Ping Request
  The value of a newly added checkbox (cboxUsingAllSkyComputer) that is accessed via VM.UsingAllSkyComputer, can be used to suppress the message associated with these exception. Fixed in AstroMain 3.84.
   Fixed 2026-10-02 (Observatory Computer, AstroMain 3.84)
   
• Capture fresh views of AstroMain's Manager and Observatory panels/tabs stopped working (01:17 - 09:00). AstroMain 3.83.14 and earlier versions have a worker that captures and saves an image of the Manager tab and Observatory Tab every 2 minutes, which get uploaded to WebSite and display on the Observatory Status and Current/Latest Session web pages.   But this functionality wasn't working between 01:17 and  09:00.   The functionality unexpectedly stopped working at 01:17 with no obvious reason or cause, and produced 'Parameter is not valid' exceptions with messages like "Exception whilst trying to capture Manager ( filename )". The functionality automatically began working again when new "2026-10-02" general session was created at 09:00 (however it wasn't resolved when the '2026-09-01' general session resumed at 05:43). Exception is potentally  arising because the control is sized 0,0 for some reason (e.g. the form was accidentally minimized or the selected tab could not be shown). Guards added in AstroMain 3.84 to check the control & control size and to exit the CaptureControl() routine gracefully without producing an exception. Issue closed 2026-10-02, but will be monitored.
   Closed 2026-10-02 (Session, AstroMain 3.84)
   
• AstroMain's Htm Log file doesn't contain any form of divide associated with the log file being reopened (05:43).   Messages in the Htm log file go directly from 23:35:15 to 05:43:56 with no divide where 05:43:56 corresponds to the time that a general session was resumed after the intervening S1457 live session.  The source file contains a message line "REOPENING LOG FILE (2026-10-02 05:43)" bounded by two blank lines.  AstroMain's HTM log builder needs to be modified to recognise the 'REOPENING LOG FILE' line and incorporate it into the Htm file version. A bookmark should be defined on the line and included as a hyperlinked entry in the files Contents section. Fixed in AstroMain 3.84. Examining code shows there is a block for inserting divide and adding a hyperlinked entry in contents, but it is bypassed due to the 'Len(S) > 53 - fc' condition.  Section copied to place that doesn't get bypassed.
   Fixed 2026-10-02 (Observatory Computer, AstroMain 3.84)
   
• Two targets were recorded in Sessions Plan table with blank Failure mode (04:24, 05:09). Two targets, Target 15/18 (NGC 3310 w/SN) and Target 17/18 (NGC 3437 w/SN) failed whilst session was suspended due to cloud.  Both of the planned targets were updated with a blank Failure Mode.  Examining the report file shows that the Target wer report as failed due to 'Other - Recent Rain' . AstroPlan/AstroMain should be modified to include an enum 'RecentRain' and used when saving/updating a planned target in such a circumstance. Whilst there is already a 'RecentRain = 38'  member of the 'FailureState' enum in AstroMain, it is missing as a member from FailureState enum in AstroPlan.  Fixed in AstroPlan 1.47.3, the S1457 plan now shows RecentRain failure modes for the two targets, Target 15/18 & Target 17/18.
   Fixed  2026-10-02 (AstroPlan 1.47.3)
   
• Weather Forecast data is not being received by AstroMain Program. As part of a project to explore the possibility of running a live Observatory Session whilst the AllSky/Weather Computer is unavailable, various changes were made to allow Cloud Sensor data to be accessible on the Observatory Computer, and passed to AstroMain from AstroWeather program running in a reduced mode on the Observatory Computer. Whilst AstroWeather is receiving weather forecast data from OpenWeather, it is not being communicated through to AstroMain program.  This may be because of the absence of a base Synopsis Data record  from AstroAllSky to which Weather Forecast information is appended or due to a MachineName guard in AstroWeather. It may be necessary to split Weather/WeatherForcast record communication into separate  Weather and Weather Forecast records.  A continuous improvement ticket has been raised to implement a separate TCP/IP channel for sending WeatherForecast to AstroMain.
   Issue understood 2026-10-02 (Observatory Computer, AstroWeather, AstroMain)

Continuous Improvement

• TakeObsCam Image requests from AstroMain should be suppressed when the AllSky/Weather Computer is not in use.  During the course of a live session various 'TakeObsCam' requests are made to AstroObsCam on the AllSky/Weather Computer. Some of these are 'inline' requests whilst others involve turning the Observatory Light on/off and waiting for request to be communicated and actioned. The value of a checkbox (cboxUsingAllSkyComputer), accessed via VM.UsingAllSkyComputer, can be used to suppress the TakeObsCam requests, wait period and to modifiy AstroMain reporting to shows terms like 'Skipped' .Implemented in AstroMain 3.84 by addition of a skip/exit sub condition in TakeSpecialObsCamImage() when VM.UsingAllSkyComputer=False.
   Done 2026-10-02 (Observatory Computer, AstroMain 3.84)
   
• AstroMain's Scorcard Activity flag should be red when the scorecard listener is not recording any activity. AllSky/Weather Computer is currently unavailable having recently failed and is away for repair/replacement, and this means that Weather and Scorecard records aren't being passed on to AstroMain from AstroWeather whilst is runs in reduced service mode.   Whilst the 'Weather' activity flag is red, the Scorecard activity flag is green - it should be red.
   Done 2026-10-02 (Observatory Computer, AstroMain 3.84)
   
• Implement a separate TCP/IP channel for sending Weather Forecast data from AstroWeather to AstroMain. As part of a project to enable running a live Observatory Session whilst the AllSky/Weather Computer is unavailable, various changes have been made to allow Cloud Sensor data to be accessible on the Observatory Computer, and passed to AstroMain from AstroWeather program running in a reduced mode on the Observatory Computer. In the first two sessions using restricted data (S1457 & S1458) AstroWeather is receiving weather forecast data from OpenWeather, but it is not being communicated through to the AstroMain program.  In AstroMain 3.84 weather forecast data is received from AstroAllSky via the Scorecard/Synopsis record, but of course AllSy Computer with AstroAllSky is not currently unavailable.  It is proposed to create a new TCP/IP channel on Port 4013 so that AstroWeather can supply AstroMain with weather forecast date directly.   A new sender (WeatherForecasterB) had been added to AstroWeather 1.30.6, and a new Listener ( ForecastListener) has been added to AstroMain 3.84.1.  The new arrangement works but needs further optimisation  and removal of duplicated operations, in particular there is overlap between the WeatherForecaster and WeatherForecasterB operations in AstroWeather, and between the ScorecardListener and ForecastListener in AstroMain, where forecast data is still also loaded from the Scorecard records.  A later refinement of the AstroMain/AstroWeather using the new TCP/IP channel was made on 2026-10-04.
   Done 2026-10-03 (Observatory Computer, AstroWeather 1.30.6, AstroMain 1.84.1)
   
• Consider changing AstroWeather to access CloudSensor data via Port 4000 instead of from CSV file.  CurrentlyAstroWeather 1.30.5 and earlier versions access CloudSensor values by reading a 'date_current.csv' file that is written to the CloudSensor program folder every 2s.  An alternative would be to access the same information by setting CloudSensor to write to a speciifc port (4000) and incorporate a listener in AstroWeather to listen to Port 4000 and parse the records being sent to the port by Cloud Sensor. CloudSensor is configured to write to port by changing 'PortEnable=0' to 'PortEnable=1' in the program's CloudSensor.cfg file. (Port number can be configured, but 4000 is the default and is free port for AstroWeather/AstroSuite programs.   Enabling the port, restarting CloudSensor III and and running 'telnet localhost 4000' confirms that port is receiving data records every 5s like:
    2/10/2026 11:45.26,10247,1,3-2-41,130,26.4,-4.3,30.6,32.5,-216.9
  2/10/2026 11:45.31,10247,1,3-2-41,131,26.4,-4.3,30.5,32.6,-216.8
  The option has somewhat limited benefit because the Port 4000 record doesn't contain Relay flags which still have to extracted from the file clarity_2.dat.  There is no immediate plan to make the required modification to AstroWeather but it remains an future option, and in the meantime the ticket is placed on hold.
  On hold 2026-10-02 (AstroWeather)

[ Prev | Next ]

Back to Top Issue,  Back to Top

[ Prev | Next ]

Back to Top Issue,  Back to Top