David's Astronomy Pages Notes - Session 1187 (2024-02-20)

Notes (S1187A)

Notes Main

Home Page

Notes (S1188)

	Session Aims & Highlights
	- Observing Result  - Night Summary Plot  - Session Event Log
	Operational Issues
	- Critical Issues (0),  Major Issues (0),  Minor Issues (0),  Small Defects (2),  Continuous Improvement (5)
	Images from 2024-02-20 >>

Session Aims & Highlights (2024-02-20)

Main aims

1. Targets.  Acquire images of a selection of variable stars, nearby stars, comets & deep sky targets as allowed by sky conditions.
2. 12P/Pons-Brooks. Acquire images of Comet 12P/Pons-Brooks which has been undergoing regular outbursts.
3. PHD2/Guiding. First live usage of new PHD2 version 2.6.13. Check for any issues or problems.
4. AstroMain. Continue to test fixes to CCDSoft Camera/SBIG Camera operations to prevent stalled execution during starting, fix issues due to occasional repeated failures during Cam1 focusing and occassional unexpected CCD Temperature regulation.

 Equipment & Software

• 12" LX200 and ST-10XME
• 80mm APO and ZWO ASI 178MC
• TheSky6, CCDSoft5, DeviceHub 6.6.1.1,  MeadeGeneric 1.3.5.414, UPB 1.5, ASCOM 6.6,   Pulsar Dome Firmware 1.51 & Driver 6.3.10
• Pegasus UPB & Motor Focus, TCF-S
• SharpCap 3.2, PHD2  2.6.13, Siril 1.0.6, deCONZ 1.18.2, ASCOM 6.6 SP1
• [ DomeLink 1.0 / 1.1 - not used ]
   
• AstroMain 3.65.16, AstroPlan 1.39.5,  AstroShCap 1.3.15, AstroGuard 1.10.2
  AstroVOE 1.13,  AstroSN 1.10.2,  AstroProtect 1.7,  AstroMove 1.12.10
  (AstroWeather 1.23.10, AstroAllSky 3.19.11,  AstroObsCam 1.11.4, AstroLaunch 1.11.1

Highlights

• Targets.19/32 planned targets observations were completed, with 2 other targets partially completed. Other targets failed/cancelled due to cloud.
• 12P/Pons-Brooks. Images of Comet 12P/Pons-Brooks failed to be acquired due to cloud/session suspension.
• PHD2/Guiding. There were no issues using the new PHD2 2.6.13 version. Guiding was performed on 21 targets.
• AstroMain. No issues with CCDSoft Camera/SBIG Camera.
•  Dome Parking.  Dome parked ok at the correct position at end of the session.

Notes:

• Session was interrupted after Target 6/32 (NGC 3206 w/SN2024bch) in order to adjust the Camera Angle for Cam1  (SBIG ST10 on 12" LX200).  For a star field in due South sky camera angle was changed from 180.14° to 179.85°, in an attempt to make average camera angle which has become c 180.3° close to at Az 180.0°
  See Fig 1.

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)

Actual Weather vs Pre-Session Weather Forecast

Session Event Log

Time     Event Detail 19:57:44 Session Monitoring AutoStart monitoring for Live Session opportunity between 19:57 & 05:19 19:57:47 Session AutoStarting Session autostarting (19:57) 19:57:57   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.) 19:58:10 Session Created Session Created (Live, 2024-02-20 S01187, ImageSaveNum: 1187001) 19:58:17   Scope Switched On Telescope Power has been switched on via UPB Powerbox. 20:00:03   Services Started Observatory Services started 20:00:09 Observatory (Auto) Observatory placed in Fully-Automated Mode 20:00:12 Session Pending Session pending (2024-02-20) 20:00:14 Session Initiating Session initiating (2024-02-20) 20:00:16   Plan Requested Observing Plan requested from AstroPlan (1.39.5) 20:01:12   Plan Loaded Observing Plan loaded to queue (Plan ID: 961) 20:01:37   Camera1 Connected SBIG Camera connected (Set point -20°C) 20:02:14   Telescope Connected Telescope connected (TheSky6) 20:02:38 Session Equilibration Session ready to Open Dome 20:03:23   Dome Opened Dome opened (Opening time 45s, Zigbee 41s) 20:03:26 Session Running Session running 20:03:28   Queue Started Observing Queue started (32 targets selected) 20:03:29     Target Started (NrZen) Target started (Focus Field 7, HIP 34070) 20:03:43       Dome Unparked Dome unparked 20:08:50       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 20:11:14       Focusing Completed Foc1 AutoFocus Completed (Profile No 1, wide) 20:13:11       Focusing Completed Foc1 AutoFocus Completed (Profile No 1) 20:13:14       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 20:15:19       Focusing Completed Foc2 AutoFocus Completed (Profile No 2, wide) 20:17:01       Focusing Completed Foc2 AutoFocus Completed (Profile No 2) 20:17:18     Target Completed (NrZen) Target completed (Focus Field 7, HIP 34070) 20:17:22     Target Started (1/32) Target started (1/32, AT2023aais (CV)) 20:21:19       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 20:27:45     Target Completed Target completed (1/32, AT2023aais (CV)) 20:28:44     Target Started (2/32) Target started (2/32, NGC 3893 w/AT2023uhx) 20:32:52       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 20:35:09       Focusing Completed Foc1 AutoFocus Completed (Profile No 3) 20:51:16     Target Completed Target completed (2/32, NGC 3893 w/AT2023uhx) 20:51:20     Target Started (3/32) Target started (3/32, NGC 4216 w/SN2024gy) 20:56:51       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-S) 21:13:33     Target Completed Target completed (3/32, NGC 4216 w/SN2024gy) 21:13:37     Target Started (4/32) Target started (4/32, AT2023cub (CV)) 21:17:03       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 21:19:14       Focusing Completed Foc1 AutoFocus Completed (Profile No 4) 21:25:29     Target Completed Target completed (4/32, AT2023cub (CV)) 21:25:33     Target Started (5/32) Target started (5/32, 103P/Hartley) 21:29:18       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 21:31:29       Focusing Completed Foc1 AutoFocus Completed (Profile No 5) 21:41:56     Target Completed Target completed (5/32, 103P/Hartley) 21:42:08     Target Started (6/32) Target started (6/32, NGC 3206 w/SN2024bch) 21:45:22       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 22:01:33     Target Completed Target completed (6/32, NGC 3206 w/SN2024bch) 22:01:35   Queue Aborted Job Queue aborted 22:03:52   Observatory Door Observatory Door has opened 22:03:59   Observatory Door Observatory Door has closed (open time 7s) 22:04:07   Observatory Door Observatory Door has opened 22:04:08   Observatory Door Observatory Door has closed (open time 1s) 22:12:24 Session Monitoring AutoStart monitoring for Live Session opportunity between 22:12 & 05:19 22:12:26 Observatory (AutoStart) Observatory placed in Auto-Start Mode 22:12:29 Session AutoStarting Session autostarting (22:12) 22:12:40   Services Started Observatory Services started 22:12:44 Observatory (Auto) Observatory placed in Fully-Automated Mode 22:12:49 Session Pending Session pending (2024-02-20) 22:12:51 Session Initiating Session initiating (2024-02-20) 22:12:57   Plan Loaded Observing Plan loaded to queue (Plan ID: 961) 22:13:10   Camera1 Connected SBIG Camera connected (Set point -20°C) 22:13:15   Telescope Connected Telescope connected (TheSky6) 22:13:34 Session Running Session running 22:13:37   Queue Started Observing Queue started (26 targets selected) 22:13:43     Target Started (7/32) Target started (7/32, AT2023us) 22:14:12   Observatory Door Observatory Door has opened 22:14:17   Observatory Door Observatory Door has closed (open time 5s) 22:28:19     Target Completed Target partially completed (7/32, AT2023us) 22:28:23     Target Started (8/32) Target started (8/32, SN 2023nj) 22:31:36       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 22:34:02       Focusing Completed Foc1 AutoFocus Completed (Profile No 6) 22:50:02     Target Completed Target completed (8/32, SN 2023nj) 22:50:06     Target Started (9/32) Target started (9/32, GCVS RR Leo) 22:53:28       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 22:55:40       Focusing Completed Foc1 AutoFocus Completed (Profile No 7) 23:01:28     Target Completed Target completed (9/32, GCVS RR Leo) 23:01:33     Target Started (10/32) Target started (10/32, 2MFGC 08659 w/SN2023xyr) 23:04:22       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:06:33       Focusing Completed Foc1 AutoFocus Completed (Profile No 8) 23:23:00     Target Completed Target completed (10/32, 2MFGC 08659 w/SN2023xyr) 23:23:04     Target Started (11/32) Target started (11/32, WDS GRB 34) 23:27:15       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:29:25       Focusing Completed Foc1 AutoFocus Completed (Profile No 9) 23:31:26     Target Completed Target completed (11/32, WDS GRB 34) 23:31:30     Target Started (12/32) Target started (12/32, M31 w/Nova M31 AT2024ccb) 23:35:11       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 23:51:53     Target Completed Target completed (12/32, M31 w/Nova M31 AT2024ccb) 23:52:46     Target Started (13/32) Target started (13/32, 32P/Comas Sola) 23:56:07       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 00:05:09     Target Completed Target completed (13/32, 32P/Comas Sola) 00:07:36     Target Started (14/32) Target started (14/32, Nova Per 2020) 00:10:29       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:12:27       Focusing Completed Foc1 AutoFocus Completed (Profile No 10) 00:23:17     Target Completed Target completed (14/32, Nova Per 2020) 00:24:56     Target Started (15/32) Target started (15/32, NGC 3052 w/SN2024chx) 00:28:42       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 00:45:02     Target Completed Target completed (15/32, NGC 3052 w/SN2024chx) 00:46:57     Target Started (16/32) Target started (16/32, MCG -1-33-30 w/SN2024byg) 00:51:38       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 01:07:30     Target Completed Target completed (16/32, MCG -1-33-30 w/SN2024byg) 01:09:16     Target Started (17/32) Target started (17/32, 62P/Tsuchinshan) 01:13:54       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 01:25:35     Target Completed Target completed (17/32, 62P/Tsuchinshan) 01:27:18     Target Started (18/32) Target started (18/32, AT2024crd) 01:30:16       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:32:35       Focusing Completed Foc1 AutoFocus Completed (Profile No 11) 01:49:08     Target Completed Target completed (18/32, AT2024crd) 01:50:18     Target Started (19/32) Target started (19/32, IC 1125 w/SN2024jz) 01:54:14       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 02:10:23     Target Completed Target completed (19/32, IC 1125 w/SN2024jz) 02:12:18     Target Started (20/32) Target started (20/32, NGC 6004 w/SN2024cld) 02:15:20       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 02:24:59       SoftSuspend Called Soft Suspend is called due to Deteriorating Conditions (too few stars) 02:31:35     Target Completed Target completed (20/32, NGC 6004 w/SN2024cld) 02:31:37   Queue Paused Queue paused for Session Suspension 02:31:39 Session Suspending Session suspending 02:32:25   Dome Closed Dome closed (Closing time 50s, Zigbee 44s) 02:32:28 Session Suspended Session suspended 02:42:37 Session Resuming Session resuming 02:43:22   Dome Opened Dome opened (Opening time 45s, Zigbee 41s) 02:43:25 Session Running Session running 02:43:27   Queue Resumed Observing Queue resumed 02:43:29     Target Started (21/32) Target started (21/32, M101 w/SN2023ixf) 02:55:28       SoftSuspend Called Soft Suspend is called due to Deteriorating Conditions (too few stars) 02:59:29     Target Completed Target partially completed (21/32, M101 w/SN2023ixf) 02:59:31   Queue Paused Queue paused for Session Suspension 02:59:34 Session Suspending Session suspending 03:00:24   Dome Closed Dome closed (Closing time 50s, Zigbee 44s) 03:00:25 Session Suspended Session suspended 03:15:54     Target Cancelled Target cancelled (22/32, NGC 6106 w/SN2024ahv) due to cloud 03:38:14     Target Cancelled Target cancelled (23/32, MCG +9-27-70 w/SN2023acha) due to cloud 04:00:14     Target Cancelled Target cancelled (24/32, UGC 11097 w/AT2024ajp) due to cloud 04:11:35     Target Cancelled Target cancelled (25/32, HIP 87937) due to cloud 04:22:57     Target Cancelled Target cancelled (26/32, AT2023wvl (CV)) due to cloud 04:40:34     Target Cancelled Target cancelled (27/32, Nova Cas 2021) due to cloud 04:50:27     Target Cancelled Target cancelled (28/32, GCVS HH And) due to cloud 05:07:04     Target Cancelled Target cancelled (29/32, 12P/Pons-Brooks) due to cloud 05:19:54     Target Cancelled Target cancelled (30/32, AT2023txn) due to cloud 05:31:54     Target Cancelled Target cancelled (31/32, AT2023abtv (CV)) due to cloud 06:00:25     Target Cancelled Target cancelled (32/32, GCVS SS Cyg) due to too few stars 06:00:30   Queue Completed Job Queue completed 06:00:36 Session Closing Session closing 06:00:41   Dome Closed Dome already closed (closed at 03:00, closing time 50s, zigbee 44s) 06:01:07   Dome Parked Dome parked (parking time 18s), Az: 90.1 deg 06:02:31   Telescope Parked Telescope parked (parking time 79s) 06:02:46   Telescope State Handbox reads 'Scope parked Turn scope off.' 06:03:17   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 06:04:41   Dome Charging Dome is parked and re-charging Ok (18mA) 06:04:43   Services Stopped Night Services stopped 06:04:46 Session Finishing Session Finishing started (Create Fits Summary, Transfer Files) 06:05:08     Dome (Find Park) Find Park started (Search Az 87.0 to 93.0°, Step 0.2°, Narrow) 06:06:39     Dome Find Park found (Best Park Az 90.2°) 06:06:46     Dome Dome has been synced at park position (Az 90.0°, Adjustment: -0.3°) 06:06:48   Dome Parked Dome parked 06:06:51   Dome Charging Dome is parked and re-charging Ok (18mA) 06:06:53 Session Finished Session Finished

Session Alerts & Alarms

Time     Type       Name Detail 20:29:09 Yellow Alert Anomalous Dome Slew Dome slew resumed at Az 150.5° (T+20.4s) 06:06:51 Green Clear Dome Charging Dome is parked and re-charging Ok (18mA)

Back to Top

Operational Issues (2024-02-20 S1187)

• Critical Issues (0)
• Major Issues (0)
• Minor Issues (0)
• Small Defects (2)
• Continuous Improvement (5)
  

[ Prev | Next ]

Critical Issues

• None

Major Issues

• None

Minor Issues

• None

Small Defects

• Title of AstroPlan's Target Form is displayed incorrectly for hostless transients objects.  The title on AstroPlan's Target Form for a hostless transient is appearing in format like "AT2024xf w/AT2024xf"  instead of simply "AT2024xf".
  Fixed  2024-02-21  (AstroPlan 1.39.6)
   
• Contradictory reasons for ongoing session suspension  (03:00). After session was suspended at 03:00 until session was closed at 06:00 each of the remaining 11 targets (beginning with Target 22/32 ,  NGC 6106 w/SN2024ahvc) repprted contradictory reasons for ongoing session suspension.  For each target the session status was first reported as "Session Suspended (Due to too few stars)" but ended by reporting "Session Suspended (Due to cloud)"  & reporting "Target failed  (Cloud)".  The one exception to this was the final target (GCVS SS Cyg) which reported '..(Due to too few stars)"  in reported first and final session state and as reason for target failure.   This was despite a low clarity value (30).  Reason for continued session suspension at start and end of a target's time slot can of course vary, but the fact that the same pattern is seen across 9 targets seems too much of a coincidence Some changes were made to CanResume () and GetFailDescription() in AstroMain 3.65.16 in an attempt to resolve an earlier issue with reason for session suspension being blank in S1182 & S1187A session  (see S1187A 2024-02-18  for details) but this is not thought unlikely to have given rise to this new issue.  Issue was investigated on 2024-02-21.  When a session is already suspended at the beginning of a target's time slot the  'due to reason' is reported using the GetSuspendReason() function, with generates a text string based on current value of the global variable 'ReasonToSuspend'.   The reason for session suspension at end of target's planned slot and the the failure for a cancelled Target (one that failed due to weather etc) is instead set by GetFailureMode() function. This can return one of 6 reasons (Rain, Wind, Light, Cloud, Rain Threat or High Humidity).  It should be noted that in the the case of 'Too Few Stars'  condition (ie ObservatoryManager.TooFewStars=True) the function returns failure mode as  'Cloud', rather than 'TooFewStars'.  This explains why it might show '..(Due to cloud)'  whilst the initial reason might shows as "..(Due to too few stars)".  It is also noted that the GetFailureMode() function doesn't have an else statement which could presumably mean that the function would return a value of 0 if none of the specified conditions applies which could theoretically mean that a Failed Target might record FailureMode = FailureState.blank (0) and thus report or display a blank reason for failing in AstroMain/AstroPlan.    Prehaps the GetFailureMode() should produce a FailureState.TooFewStars result instead of .Cloud result ?. To continue to review ( 2024-02-21+ )
  Investigation & review in progress 2024-02-21+  (AstroMain 3.65.17+)

Continuous Improvement

• Investigate Observatory response to power glitch (2024-02-21 12:45).  Household power door supply went off for a momentary spell (duration unclear) and then came back on again, noted by door chime briefly sounding and Google Home booting up, and VNC reattempting connection with Observatory Computer. Checking Observatory Computer showed error 2 dialogs that connection to Pegasus PowerBox / UPB had been lost.  It was noticed that connection to TCF-Focuser had gone down and hadn't returned.  AstroMain's backdoor button utility ' Restart TCF-S service' was used to restore it .   Also that connection to Cloud Sensor had gone down at 12:43 and hadn't returned, and AstroMain reported "Cloud Sensor data has been inactive for more than 5 min"  and later ".. more than 20 min".  The CloudSensor program stopped showing fresh values. An examination was made into ways that the connection could be reestablished in a way that could be made part of a future automated fix.  An attempt was made to reconnect to Cloud Sensor by turning off & turning on the USB to Cloud Sensor using the Pegasus USB Hub attached to the AllSky/Weather Computer.  Next CloudSensor.exe was killed and then restarted. After a little AstroWeather began receiving fresh CloudSensor readings.    Power Supply went off again at 13:12.   A backdoor utiity was added to AstroWeather to 'Restart CloudSensor Service'  as a start to developing an automated response to a CloudSensor outage ( for which a separate Continuous Improvement ticket has been raised) and under manual control this allowed CloudSensor to be quickly restarted to fix the issue.    There was no affect on ability of observatory to continue uploading files to website.  The Ethernet over Power connection seems to have not been affected by these momentary outage in power or at least the Uploaders in AstroPlan and AstroAllSky seem to not be affected and didn't make an automatic restart of the uploaders.
  Done  2024-02-21  (Observatory Computers, AstroMain, AstroWeather) 
   
• Investigate why a Critical Cloud Event was issued during General Session  (2024-02-21 13:11).  A gray-coloured Critical Cloud event was issued at 13:11:55 with the message "Critical Cloud Alert (Obs.Manager will close the Dome)" .   The Observatory Dome was closed at this time and there wouldn't normally be expected at this time.  There was a small almost momentary outage in household power supply at this time, which was separately being investigated at around this time, following an earlier power outage at 12:45.  It is assumed that the message was generated as it was cloudy and AstroMain couldn't establish that the dome was closed because the dome was not powered or was otherwise in the process of 'booting' up again. Pulsar log files show that a CloseShutter command was sent at 13:11:55.      After a closed Shutter Status = 1 at 13:11:42.8 the logs anomalously show 'ShutterStatus' = 6 at 13:11:47.8,  'ShutterStatus' = 0 at 13:11:52.8, ShutterStatus = 3 at 13:11:55.9 (following the command to close shutter at 13:11:55.9) before returning to  'ShutterStatus' = 1  at 13:11:56.9 .  There were no Shutter Status lines in log file between 13:11:42.8 and 13:11:47.8 indicating a likely 5s time window when the power outage occurred & the dome was not reachable ?.  The alert and associated action are explainable.  No action is necessay at this time and the ticket is deemed to be closed.
  Closed  2024-02-21  (Session, AstroMain, Pulsar Dome) 
   
• Investigate why Shutter Battery Alert was issued post session  (2024-02-21 12:44).  A Shutter Battery red alert was issued at 12:44:19 with the message "Shutter battery level has fallen below 85%".  This was unexpected as the Dome was parked and the Shutter Battery had recharged itself following the S1187 session.  The similarity in time with a momentary household power outage at the same time is significant.     It is assumed that the alert was generated as dome wasn't providing data as it was either not powered or was otherwise in the process of 'booting' up again following the power outage.  The Pulsar log should Volatile messages with null (0) values between 12:44:06 and 12:44:18, indicating a 12s time window when the power outage occurred & the dome was not reachable. T he alert is thus fully explainable.  No action is necessay at this time and the ticket is deemed to be closed.
  Closed  2024-02-21  (Session, AstroMain, Pulsar Dome) 
   
• Add a 'backdoor' button routine to AstroWeather to allow CloudSensor Program to be restarted.  As a part way solution to developing a fully response to an outage of CloudSensor typically caused by a short power outage, Add a 'backdoor' button routine to AstroWeather to allow CloudSensor Program to be restarted.  Implemented in AstroWeather 1.23.11. with a backdoor utiity  to 'Restart CloudSensor Service' via a threaded call to new  RestartCloudSensor() routine.  Initial testing showed the backdoor utility would kill the existing CloudSensor process ok, and then restart the CloudSensor program, but it would then immediately close it again. After thinking this was an issue with Antivirus Application Control rights in was eventually determined that on AllSky/Weather Computer (Windows 10) the new RestartCloudSensor() routine  needs to call LaunchCloudSensor("Cloud Sensor", "CloudSensor") instead of calling OpenApplicationAndWait("Cloud Sensor",...) with the BatchFilePath set to "C:\More Programs\AstroLaunch\LaunchCloudSensor.bat".   Some logic now needs to be added to AstroWeather to spot a condition where CloudSensor may have frozen and automatically call this new 'RestartCloudSensor () routine when power returns. 
  Done  2024-02-21  (AstroWeather 1.23.11)
   
• Develop an automated response to a CloudSensor outage caused by a power glitch.  Household power door supply went off for a momentary spell on 2024-02-21 and effects on Observatory operations and program responses was examined.  This showed that connection to Cloud Sensor had gone down and didn't return by itself. AstroWeather showed that the CloudSensor reading were refreshing.  AstroMain reported "Cloud Sensor data has been inactive for more than 5 min"  and later ".. more than 20 min".  The CloudSensor program stopped showing any fresh values. An examination was made into ways that the connection could be reestablished in a way that could be made part of a future automated fix.  This showed than manually killing CloudSensor.exe  and then restarting was a successful with the Cloud Sensor showing fresh readings again . After a little AstroWeather began receiving fresh CloudSensor readings.   This inprovement was also raised as a conntinuous improvement after a further data outage after sesssion S1192 (2024-02-25).  A backdoor utiity was added to AstroWeather 1.23.11 to 'Restart CloudSensor Service' via a threaded call to new  RestartCloudSensor() routine.  Logic has now been added to DisplayCloudSensorRecord()  routine in AstroWeather 1.23.12 to call new routine  SubmitRetartCloudSensorByThread()  (which then runs the recently added RestartCloudSensor() routine) when elapsedMinsCloudSensor < 2 and MinutesSince(LastCloudSensorRestartTime) > 2 and SystemInformation.PowerStatus.PowerLineStatus = PowerLineStatus.Online.
  Done  2024-02-28  (AstroWeather 1.23.12)

[ Prev | Next ]

Back to Top