David's Astronomy Pages Notes - Session 1196 (2024-03-04)

Notes (S1195)

Notes Main

Home Page

Notes (S1197)

	Session Aims & Highlights
	- Observing Result  - Night Summary Plot  - Session Event Log
	Operational Issues
	- Critical Issues (0),  Major Issues (0),  Minor Issues (4),  Small Defects (8),  Continuous Improvement (16)
	Images from 2024-03-04 >>
	2024-03-05
	AstroMain - Task Manager Assistant
	2024-03-11
	System Tests - Examining robustness of Observatory system to a mains power supply outage

Session Aims & Highlights (2024-03-04)

Main aims

1. Telescope Resync.  Perform Telescope re-sync on a known star or position and make a short mapping job in order to reestabish telescope pointing and to tie in the TPoint Model, following undesirable switching off of the LX200 Telescope in an unparked state.
2. MeadeGeneric.  Check that there are no issues using the new 1.3.9 version of MeadeGeneric telescope driver which has been installed since the last session.
3. Targets.  Acquire images of a selection of variable stars, nearby stars, comets & deep sky targets as allowed by sky conditions.
4. 12P/Pons-Brooks. Acquire images of Comet 12P/Pons-Brooks which has been undergoing regular outbursts.
5. 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.9, 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.66.1,  AstroPlan 1.39.7,  AstroShCap 1.3.15, AstroGuard 1.10.2   (any new items or versions in bold)
  AstroVOE 1.13,  AstroSN 1.10.2,  AstroProtect 1.7,  AstroMove 1.12.11
  (AstroWeather 1.23.11, AstroAllSky 3.20,  AstroObsCam 1.11.4, AstroLaunch 1.11.1

Highlights

•  Telescope Resync. Telescope was successfully resynced at the start field on a star field in Orion and a short mapping run made in which 12/12 points successfully mapped. This followed the insertion of 5 near-duplicate map points based on sync star field in order to give head-start tie-in to the base TPoint Model
•  MeadeGeneric Driver. The new 1.3.9 version of MeadeGeneric Telescope successfully operated without any issues.
• Targets. 9/29  planned targets observations were completed with 2 targets partially completed.. Other targets failed due to cloud /session suspension.
• AstroMain. No issues with CCDSoft Camera/SBIG Camera.
•  Zigbee Sensor.  ZIgbee open/shut sensor at the bottom end of the shutter operated without problem
•  Dome Parking.  Dome parked ok at the correct position at end of the session.
• AstroMain / CCDCamera. There were a number of issues with CCDCamera during the early part of the session.  The CCDCamera froze at 18:23 (frozen/stuck CcdCamera)  19:28 & 19:32 (on Foc1 Focus Frame 7/14), and there were 'Command timed-out' errors trying to take images at 19:32. In connection with these CCDSoft was restarted by program control (including SBIG Camera reboot) at 18:24, 19:28 &19:32, and eventually resolved the issue.
• AstroMain / PHD2. Issues with the "incomplete data stream" problem were recorded at 19:38 and 20:01.  The PHD2 Service was restarted by user at 19:22 and by programmed control at 19:39  at 20:01, which eventually resolved the issue.  
• 12P/Pons-Brooks. No images of Comet 12P/Pons-Brooks were acquired because of cloud.

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)

Actual Weather vs Pre-Session Weather Forecast

Session Event Log

Time     Event Detail 18:22:37   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.) 18:23:02   Camera1 Connected SBIG Camera connected (Set point -20°C) 18:23:04 Session Created Session Created (Live, 2024-03-04 S01196, ImageSaveNum: 1196001) 18:23:26   CcdCamera Frozen CcdCamera appears to be frozen at around 18:23 in section 'GetCameraProperties' 18:24:05   CCDSoft Restarting CCDSoft being restarted (attempt to fix frozen CcdCamera) 18:24:12   SBIG Camera Reset SBIG Camera being power-cycled 18:25:02   Camera1 Connected SBIG Camera connected (Set point -20°C) 18:25:38   Scope Switched On Telescope Power has been switched on via UPB Powerbox. 18:27:24   Services Started Observatory Services started 18:28:36   Telescope Connected Telescope connected (TheSky6) 18:31:26       Dome Unparked Dome unparked 18:51:24   Dome Opened Dome opened (Opening time 48s, Zigbee 41s) 18:55:33 Telescope Running 'ResetScopePointing' under user supervision 18:57:19 Telescope Running 'ResetScopePointing' under user supervision 18:59:36   Telescope Telescope pointing successfully synced 18:59:42   Telescope Pointing Mapping run started 18:59:45   Automapping Started Automapping started (12 points planned) 19:11:19   Automapping Completed Automapping completed (12 points mapped out of 12 points) 19:11:46   Telescope Pointing Mapping run finished (Mapped 12 / 12) 19:13:57   Telescope Parked Telescope parked (parking time 69s total) 19:14:12   Telescope State Handbox reads 'Scope parked Turn scope off.' 19:14:43   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 19:17:00   Scope Switched On Telescope Power has been switched on via UPB Powerbox. 19:18:51 Session Monitoring AutoStart monitoring for Live Session opportunity between 19:18 & 04:46 19:18:53 Observatory (AutoStart) Observatory placed in Auto-Start Mode 19:18:55 Session AutoStarting Session autostarting (19:18) 19:19:13   Services Started Observatory Services started 19:19:20 Observatory (Auto) Observatory placed in Fully-Automated Mode 19:19:23 Session Pending Session pending (2024-03-04) 19:19:25 Session Initiating Session initiating (2024-03-04) 19:19:27   Plan Requested Observing Plan requested from AstroPlan (1.39.7) 19:20:45   Plan Loaded Observing Plan loaded to queue (Plan ID: 970) 19:20:59   Camera1 Connected SBIG Camera connected (Set point -20°C) 19:21:05   Telescope Connected Telescope connected (TheSky6) 19:21:43 Session Running Session running 19:21:45   Queue Started Observing Queue started (29 targets selected) 19:21:49     Target Started (NrZen) Target started (Focus Field 6, HIP 28634) 19:25:29       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 19:28:00   SBIG Camera Take Image failed (Command timed-out) 19:28:10   CcdCamera Frozen CcdCamera appears to be frozen at around 19:28 in section 'GetCameraProperties' 19:28:48   CCDSoft Restarting CCDSoft being restarted (attempt to fix frozen CcdCamera) 19:28:55   SBIG Camera Reset SBIG Camera being power-cycled 19:29:45   Camera1 Connected SBIG Camera connected (Set point -20°C) 19:29:48   SBIG Camera Take Image command accepted (bSbigDriverException flag is reset) 19:30:27       Focusing Completed Foc1 AutoFocus Completed (Profile No 1, wide) 19:31:44   SBIG Camera Take Image failed (Command timed-out) 19:32:04   SBIG Camera Take Image failed (Command in progress. Error code = 219 (0xdb).) 19:32:09   CcdCamera Frozen CcdCamera appears to be frozen at around 19:32 in section 'GetCameraProperties' 19:32:48   CCDSoft Restarting CCDSoft being restarted (attempt to fix frozen CcdCamera) 19:32:50       Focusing Failed Foc1 focusing failed - star lost 19:32:55   SBIG Camera Reset SBIG Camera being power-cycled 19:33:18       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 19:33:52   Camera1 Connected SBIG Camera connected (Set point -20°C) 19:35:31       Focusing Completed Foc2 AutoFocus Completed (Profile No 2, wide) 19:36:25       Focusing Failed Foc2 focusing failed - star lost 19:36:29     Target Completed (NrZen) Target completed (Focus Field 6, HIP 28634) 19:36:34     Target Started (1/29) Target started (1/29, NGC 1122 w/SN2024dru) 19:37:39   SBIG Camera Take Image command accepted (bSbigDriverException flag is reset) 19:38:48   PHD2 Communication Restarting PHD2 service (14 incomplete data stream reads) 19:39:16   PHD2 Restarted PHD2 service restarted 19:41:21       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 19:44:20       Focusing Completed Foc1 AutoFocus Completed (Profile No 3, wide) 19:46:17       Focusing Completed Foc1 AutoFocus Completed (Profile No 3) 19:59:29     Target Completed Target partially completed (1/29, NGC 1122 w/SN2024dru) 19:59:33     Target Started (2/29) Target started (2/29, UGC 831 w/SN2023wdd) 20:01:28   PHD2 Communication Restarting PHD2 service (195 incomplete data stream reads) 20:01:49   PHD2 Restarted PHD2 service restarted 20:03:07       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 20:05:33       Focusing Completed Foc1 AutoFocus Completed (Profile No 4) 20:20:49       SoftSuspend Called Soft Suspend is called due to Deteriorating Conditions (too few stars) 20:21:21     Target Completed Target completed (2/29, UGC 831 w/SN2023wdd) 20:21:23   Queue Paused Queue paused for Session Suspension 20:21:27 Session Suspending Session suspending 20:22:14   Dome Closed Dome closed (Closing time 50s, Zigbee 43s) 20:22:17 Session Suspended Session suspended 20:25:15 Session Resuming Session resuming 20:26:00   Dome Opened Dome opened (Opening time 45s, Zigbee 41s) 20:26:02 Session Running Session running 20:26:04   Queue Resumed Observing Queue resumed 20:26:06     Target Started (NrZen) Target started (Focus Field 5, HIP 23569) 20:28:38       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 20:30:46       Focusing Completed Foc2 AutoFocus Completed (Profile No 5, wide) 20:31:35       Focusing Failed Foc2 focusing failed - star lost 20:31:39     Target Completed (NrZen) Target completed (Focus Field 5, HIP 23569) 20:31:44     Target Started (3/29) Target started (3/29, M101 w/SN2023ixf) 20:34:41       SoftSuspend Called Soft Suspend is called due to Deteriorating Conditions (too few stars) 20:36:06     Target Failed (3/29) Target failed due to cloud (3/29, M101 w/SN2023ixf) 20:36:08   Queue Paused Queue paused for Session Suspension 20:36:10 Session Suspending Session suspending 20:36:56   Dome Closed Dome closed (Closing time 50s, Zigbee 43s) 20:36:58 Session Suspended Session suspended 20:38:51     Target Cancelled Target cancelled (3/29, M101 w/SN2023ixf) due to cloud 20:58:23     Target Cancelled Target cancelled (4/29, 12P/Pons-Brooks) due to too few stars 21:06:55 Session Resuming Session resuming 21:07:40   Dome Opened Dome opened (Opening time 45s, Zigbee 41s) 21:07:42 Session Running Session running 21:07:44   Queue Resumed Observing Queue resumed 21:07:46     Target Started (NrZen) Target started (Focus Field 6, HIP 28634) 21:11:46       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 21:12:05       SoftSuspend Called Soft Suspend is called due to Deteriorating Conditions (too few stars) 21:13:43       Focusing Completed Foc1 AutoFocus Completed (Profile No 6) 21:13:46       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 21:14:00     Target Completed (NrZen) Target completed (Focus Field 6, HIP 28634) 21:14:04     Target Started (5/29) Target started (5/29, 13P/Olbers) 21:18:04     Target Failed (5/29) Target failed due to cloud (5/29, 13P/Olbers) 21:18:06   Queue Paused Queue paused for Session Suspension 21:18:08 Session Suspending Session suspending 21:18:56   Dome Closed Dome closed (Closing time 50s, Zigbee 43s) 21:18:58 Session Suspended Session suspended 21:32:48 Session Resuming Session resuming 21:33:33   Dome Opened Dome opened (Opening time 45s, Zigbee 40s) 21:33:35 Session Running Session running 21:33:37   Queue Resumed Observing Queue resumed 21:33:39     Target Started (NrZen) Target started (Focus Field 6, HIP 28634) 21:36:41       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 21:36:57     Target Completed (NrZen) Target completed (Focus Field 6, HIP 28634) 21:36:59     Target Missed (6/29) Target's time slot was missed (6/29, UGC 3174 w/SN2023mut) 21:37:18   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 21:37:20   HardSuspend Called Hard Suspend is called due to Critical Conditions (cloud) 21:37:22   Queue Paused Observing Queue pausing for Session Suspension 21:37:24 Session Suspending Session suspending 21:38:13   Dome Closed Dome closed (Closing time 50s, Zigbee 43s) 21:38:16 Session Suspended Session suspended 21:44:04 Session Resuming Session resuming 21:44:49   Dome Opened Dome opened (Opening time 45s, Zigbee 40s) 21:44:51 Session Running Session running 21:44:53   Queue Resumed Observing Queue resumed 21:44:55     Target Started (7/29) Target started (7/29, AT2024ll (CV)) 21:48:15       SoftSuspend Called Soft Suspend is called due to Deteriorating Conditions (too few stars) 21:52:30       SoftSuspend Cancelled Soft Suspend is cancelled due to improved conditions 21:54:42     Target Completed Target completed (7/29, AT2024ll (CV)) 21:54:46     Target Started (8/29) Target started (8/29, 207P/NEAT) 21:59:12       Focusing Skipped Foc1 focusing skipped - unable to find a star (TCF-S) 22:18:57     Target Completed Target completed (8/29, 207P/NEAT) 22:19:01     Target Started (9/29) Target started (9/29, IC 2190 w/AT2024dhp) 22:21:44       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 22:24:14       Focusing Completed Foc1 AutoFocus Completed (Profile No 7) 22:40:02     Target Completed Target completed (9/29, IC 2190 w/AT2024dhp) 22:40:06     Target Started (10/29) Target started (10/29, AT2022wlz) 22:43:04       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-S) 22:56:23       SoftSuspend Called Soft Suspend is called due to Deteriorating Conditions (too few stars) 22:57:33       SoftSuspend Cancelled Soft Suspend is cancelled due to improved conditions 23:00:00     Target Completed Target completed (10/29, AT2022wlz) 23:00:04     Target Started (11/29) Target started (11/29, 103P/Hartley) 23:02:41       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:05:04       Focusing Completed Foc1 AutoFocus Completed (Profile No 8) 23:10:24       SoftSuspend Called Soft Suspend is called due to Deteriorating Conditions (too few stars) 23:13:15       SoftSuspend Cancelled Soft Suspend is cancelled due to improved conditions 23:15:31     Target Completed Target completed (11/29, 103P/Hartley) 23:16:11     Target Started (12/29) Target started (12/29, GCVS YZ Cnc) 23:19:45       SoftSuspend Called Soft Suspend is called due to Deteriorating Conditions (too few stars) 23:20:31       Focusing Skipped Foc1 focusing skipped - unable to find a star (TCF-S) 23:20:56       SoftSuspend Cancelled Soft Suspend is cancelled due to improved conditions 23:27:19     Target Completed Target completed (12/29, GCVS YZ Cnc) 23:29:11     Target Started (13/29) Target started (13/29, C/2022 E2 (ATLAS)) 23:32:02       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 23:38:53       SoftSuspend Called Soft Suspend is called due to Deteriorating Conditions (too few stars) 23:41:11     Target Completed Target completed (13/29, C/2022 E2 (ATLAS)) 23:41:13   Queue Paused Queue paused for Session Suspension 23:41:15 Session Suspending Session suspending 23:42:03   Dome Closed Dome closed (Closing time 50s, Zigbee 43s) 23:42:06 Session Suspended Session suspended 23:54:39     Target Cancelled Target cancelled (14/29, AT2024nn (CV)) due to cloud 00:14:39     Target Cancelled Target cancelled (15/29, AT2024djo) due to cloud 00:35:35     Target Cancelled Target cancelled (16/29, 29P/Schwassmann-Wachmann) due to cloud 00:55:35     Target Cancelled Target cancelled (17/29, NGC 2642 w/SN2023aaby) due to cloud 01:08:44     Target Cancelled Target cancelled (18/29, GCVS RZ LMi) due to cloud 01:29:33     Target Cancelled Target cancelled (19/29, UGC 11858 w/SN2023rjj) due to cloud 01:43:53     Target Cancelled Target cancelled (20/29, AT2024dsj (CV)) due to cloud 02:25:55     Target Cancelled Target cancelled (21/29, Segue 1) due to cloud 02:47:55     Target Cancelled Target cancelled (22/29, UGC 5886 w/SN2024hw) due to cloud 03:10:15     Target Cancelled Target cancelled (23/29, NGC 3690 w/SN2023wrk) due to cloud 03:25:47 Session Resuming Session resuming 03:26:37   Dome Opened Dome opened (Opening time 50s, Zigbee 41s) 03:26:39 Session Running Session running 03:26:41   Queue Resumed Observing Queue resumed 03:26:43     Target Started (NrZen) Target started (Focus Field 12, HIP 58514) 03:29:08       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:31:41       Focusing Completed Foc1 AutoFocus Completed (Profile No 9) 03:31:44       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 03:33:51       Focusing Completed Foc2 AutoFocus Completed (Profile No 10, wide) 03:35:33       Focusing Completed Foc2 AutoFocus Completed (Profile No 10) 03:35:50     Target Completed (NrZen) Target completed (Focus Field 12, HIP 58514) 03:35:52     Target Missed (24/29) Target's time slot was missed (24/29, NGC 3206 w/SN2024bch) 03:35:54     Target Started (25/29) Target started (25/29, NGC 3467 w/AT2024dda) 03:39:36       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-S) 03:54:15       SoftSuspend Called Soft Suspend is called due to Deteriorating Conditions (reducing clarity) 03:55:35   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 03:55:37   HardSuspend Called Hard Suspend is called due to Critical Conditions (cloud) 03:55:40     Target Aborted (25/29) Target aborted (25/29, NGC 3467 w/AT2024dda) due to cloud 03:55:42   Queue Paused Queue paused for Session Suspension 03:55:44 Session Suspending Session suspending 03:56:35   Dome Closed Dome closed (Closing time 55s, Zigbee 43s) 03:56:38 Session Suspended Session suspended 04:14:07     Target Cancelled Target cancelled (26/29, 62P/Tsuchinshan) due to too few stars 04:17:28 Session Resuming Session resuming 04:18:13   Dome Opened Dome opened (Opening time 45s, Zigbee 41s) 04:18:15 Session Running Session running 04:18:17   Queue Resumed Observing Queue resumed 04:18:20     Target Started (27/29) Target started (27/29, NGC 5036 w/SN2024dop) 04:23:06       Focusing Skipped Foc1 focusing skipped - unable to find a star (TCF-S) 04:28:09       SoftSuspend Called Soft Suspend is called due to Deteriorating Conditions (too few stars) 04:28:39       SoftSuspend Cancelled Soft Suspend is cancelled due to improved conditions 04:32:50       SoftSuspend Called Soft Suspend is called due to Deteriorating Conditions (too few stars) 04:39:44     Target Completed Target completed (27/29, NGC 5036 w/SN2024dop) 04:39:46   Queue Paused Queue paused for Session Suspension 04:39:48 Session Suspending Session suspending 04:40:36   Dome Closed Dome closed (Closing time 50s, Zigbee 43s) 04:40:38 Session Suspended Session suspended 04:57:17     Target Cancelled Target cancelled (28/29, NGC 4995 w/SN2023gfo) due to cloud 05:29:17     Target Cancelled Target cancelled (29/29, UGC 9002 w/SN2023pls) due to cloud 05:29:23   Queue Completed Job Queue completed 05:29:27 Session Closing Session closing 05:29:32   Dome Closed Dome already closed (closed at 04:40, closing time 50s, zigbee 43s) 05:30:42   Dome Parked Dome parked (parking time 61s), Az: 90.0 deg 05:31:54   Telescope Parked Telescope parked (parking time 70s total) 05:32:09   Telescope State Handbox reads 'Scope parked Turn scope off.' 05:32:31   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 05:33:53   Dome Charging Dome is parked and re-charging Ok (15mA) 05:33:55   Services Stopped Night Services stopped 05:33:58 Session Finishing Session Finishing started (Create Fits Summary, Transfer Files) 05:34:15     Dome (Find Park) Find Park started (Search Az 87.0 to 93.0°, Step 0.2°, Narrow) 05:35:39     Dome Find Park found (Best Park Az 90.4°) 05:35:45     Dome Dome has been synced at park position (Az 90.0°, Adjustment: -0.4°) 05:35:47   Dome Parked Dome parked 05:37:03   Dome Charging Dome is parked and re-charging Ok (20mA) 05:37:05 Session Finished Session Finished

Session Alerts & Alarms

Time     Type       Name Detail 18:24:05 Red Alert CcdCamera CcdCamera appears to be frozen (last cycle at 18:23:26) in section 'GetCameraProperties' 18:24:10 Green Clear CcdCamera CcdCamera has resumed again (18:24) after 44s 19:21:47 Yellow Alert PHD2 Alert No. of incomplete PHD2 stream reads has exceeded 5 19:28:00 Red Alert SBIG Camera Alert Take Image failed (Command timed-out) 19:28:48 Red Alert CcdCamera CcdCamera appears to be frozen (last cycle at 19:28:10) in section 'GetCameraProperties' 19:28:53 Green Clear CcdCamera CcdCamera has resumed again (19:28) after 43s 19:29:46 Green Clear SBIG Camera Take Image command accepted (bSbigDriverException flag is reset) 19:31:44 Red Alert SBIG Camera Alert Take Image failed (Command timed-out) 19:32:04 Red Alert SBIG Camera Alert Take Image failed (Command in progress. Error code = 219 (0xdb).) 19:32:48 Red Alert CcdCamera CcdCamera appears to be frozen (last cycle at 19:32:09) in section 'GetCameraProperties' 19:32:53 Green Clear CcdCamera CcdCamera has resumed again (19:32) after 44s 19:37:39 Green Clear SBIG Camera Take Image command accepted (bSbigDriverException flag is reset) 19:39:54 Yellow Alert PHD2 Alert No. of incomplete PHD2 stream reads has exceeded 5 19:41:04 Red Alert PHD2 Alert No. of incomplete PHD2 stream reads has exceeded 20 20:22:54 Green Clear PHD2 Alert PHD2 stream reading has stablised again 05:37:03 Green Clear Dome Charging Dome is parked and re-charging Ok (20mA)

Back to Top

Operational Issues (2024-03-04 S1196)

• Critical Issues (0)
• Major Issues (0)
• Minor Issues (4)
• Small Defects (8)
• Continuous Improvement (16)
  

[ Prev | Next ]

Critical Issues

• None

Major Issues

• None

Minor Issues

• Unable to easily access a projects properties window in Visual Studio after making edits. After making program code edits it was found that the newly installed version of Visual Sudio 2022 (17.9.2) would give a blank project properties tab or upon trying to open a fresh Properties tab it brings a new window saying 'Working on it' but nothing comes (or at least not within the timescaleone is willing to wait).  This means that it not possible to make edits, and then update/increment the Assembly (Version) number on the Project Properties Window and then compile. The workaround is to make change to version number straight away after opening the project or by reopening the project. In both of these cases the Project Properties information appears straight away.   An alternative is to contrive to have the Project Properties Tab open & visible when a project is exited, or to always keep the Project Properties tab open in a separate, undocked window).  Issue was thankfully fixed shortly after with the download and installation of Visual Studio 2022 (17.9.4).
  Workaround found  2024-03-05 (Visual Studio 2022)
   
• Incomplete Data Stream issue occurred in association with PHD2 server/client comms (19:38 & 20:01).   Incomplete Data Stream' issue arose during the early part of the session,  reported at 19:38 and 20:01.  PHD2 Service was restarted at 19:22 (User), and at 19:39  at 20:01 (Automated Operations). The situation likely arose from the situation where the Telescope & Camera were disconnected manually in PHD2, the telescope was then parked, and connection remade. (again manually ?). The similar situation and similar Incomplete Data Stream Issue occurred in S1190 (2024-02-23).  There were ealier exception was trying to report the PHD2 Profile whilst Starting/Confirming Observatory Services at 19:12. It should be noted the actions defined after previous instances of the issue in S1190 (principally the answer to "What is the 'correct' procedure concerning PHD2 if the telescope is needing to be Parked & then restarted within the same session") haven't been completed yet.  The ParkScope2_Manual() routine already calls CloseDownPHD2() so it confirms that it is not necessary to manually disconnect equipment in the PHD2 program.  In attempt to fix the issue it is proposed that instead of calling CloseDownPHD2() that it instead calls StopPHD2() as this will calls Phd2.StopService() which will not only will disconnect equipment but will also stop AstroMain's PHD2 Client which will hopefully prevent the server/client related 'incomplete data stream' issue from occuring again.   Attempt at this fix is implemented in AstroMain 3.66.2 where a similar change has also  been made in ObsManager's Closing Stage code section. 
  Fix attempted 2024-03-05 (AstroMain 3.66.2, PHD2)
   
• CloudSensor data failed to come back after brief Power Cut (2024-03-12 00:55). Following a real 11s power cut occurred at 2024-03-12 00:55:15  CloudSensor data failed to come back online.   AstroWeather running on the AllSky/Weather Computer has been recently updated with a power monitor and after an outage ends it takes the action of killing and restarting CloudSensor program, which normally kicks starts the flow of fresh data.  However it didn't work or didn't achieve the intended restoration.  A further 11s power cut occurred at  03:40 and power monitoring actions again didn't restore the CloudSensor.  The CloudSensor was manually restarted in the morning using the 'Restart CloudSensor' button in AstroWeather, which worked.   A short power cut test to the AllSky/Weather Cabinat was watched and it was confirmed that the operation to kill & restart CloudSensor program was working ok, and CloudSensor data continued to refresh again after the outage test. AstroWeather should be modified so that if CloudSensor data doesn't come back or goes offline for any reason, the RestartCloudSensor operation is rerun. Believed fixed in AstroWeather 1.23.14.
  Fixed 2024-03-13 (AstroWeather 1.23.14)
   
• Issues with CCDCamera / SBIG Camera freezing or giving timed out exceptions (18:23 & 19:28).   There were a number of issues with CCDCamera during the early part of the session.  The CCDCamera froze at 18:23 (frozen/stuck CcdCamera)  19:28 & 19:32 (on Foc1 Focus Frame 7/14), and there were 'Command timed-out' errors trying to take images at 19:32. In connection with these CCDSoft was restarted by program control (including SBIG Camera reboot) at 18:24, 19:28 &19:32, and eventually resolved the issue.  Whilst the case was resolved automatically by AstroMain's JobExecutor there is still a need to go through the logs and code to see if anything can be leant and applied. CCDCamera has subsequently been refactored, extended and made the single point of access to CCDSoft.Camera in AstroMain 3.68 following an investiagtion into CCDCamera freezing (see Investigation - CcdCamera Loop freezing (2024-04-02) ).
  Closed 2024-04-02 (AstroMain 3.68)

Small Defects

• Job Executor report lines and report lines from a user initiated 'Restart PHD2 Service' operation were interlaced (19.22).  Following the likelihood of an issue with PHD2 during guiding on first image, a decision was taken to preempt any PHD2 / Server issues and perform a 'Restart PHD2 Service. AT this time the Job queue was running and some degree of interlacing of report lines was entirely exected. here was an unnecesary 'Wait On Cooler' at prior to first locate frame for Near Zenith Focus Field (19:22). Ideally the user could pause the Job Execution (at a suitable 'pause' point ) or anticipate the manager/job executor would operate to queue the action  'RestartPhd2Service'  and then run as soon as the JobExecutor could entered a flag controlled pause loop. A seprate ticket already exists for queuing 'restart' activities and the idea that user could 'request' the operation and know that it will be queued and executed at the optimal time in terms of reported.
  Issue understood 2024-03-04 (Session / User Awareness, AstroMain
   
• AstroMove crashed whilst attempting to Backup VS Project to Archive Folder on Laptop7 (2024-03-08 10:55).  AstroMove crashed whilst attempting to backup AstroMain 3.66.2 VS Project from Development Computer to AllSky/Weather Computer (Laptop7).  AstroMove restarted and crashed again trying to make the same attempt. The network computer was accessible to Windows Explorer ok at the time.  AstroMove was run in VS with Debugging and the same task attempte. This time there was no issue, so unclear what the issue using the released version of the AstroMove program (in 'C:\More Programs'). Task again repeated from the relavse version and this time there was no issue backing the AstroMain project.   Issue closed after review as it could not be reproduced, it seems to have been an indeterminate glitch of some kind.
  Closed after review 2024-03-08 (AstroMove)
   
• AstroWeather's Automated RestartCloudSensor isn't working in a timely manner. AstroWeather's has a RestartCloudSensor routine for restarting the CloudSensor following a power cut but its working on a 2 min cycle and therefore the restoration of CloudSensor functionality can be delayed by up to 2 minutes.  Also the way that the control is implemented would suggest that the CloudSensor is restarted every 2 mins, which is unnessary and bug practice.  Implemented a new PowerMonitorThread which restarts the CloudSensor 10s after a power outage has ended.
  Fixed 2024-03-12 (AstroWeather 1.23.13)
   
• AstroMain Log file containing lots of "No such host is known" exceptions (2024-03-12). Exceptions are being generated from ObsEnv.SetIPaddress and TeleCommm.SetIPaddress. These  exceptions are produced when there is a power-outage and the LAN is down. There were also "Conversion from string "" to type 'Date' is not valid" exception messages associated with PulsarDomeMonitor.CheckRelayProtection  routine.   AstroMain's ObsEnv and TeleComm routines modified to not log the exceptions when Obs.PowerState  = Obs.PowerState.Battery. T
  Fixed 2024-03-13 (AstroMain 3.66.4)
   
• AstroMain Outage Management was unable to switch off Telescope during Outage Stage 4 (2023-03-12, System Test). With the Observatory in Running/Suspended Session State, a system test was carried out involving a 10 minute Power Outage to the Observatory. Whilst the Stage 4, CloseOutageDevices() routine was being run, the Telescope was successfully parked, but it couldn't be turned off due to an existing porgramming condition that prevents Telescope Power from being turned off whilst Session State is Running, Suspending, Suspended or Resuming.  and reports "Telescope power can not be switched off at this time". This is for general 'protection' in case user makes an accidental mistake during a live session, but in this case it interferred with the newly added Outage Management operation. The inability to Switch Off the telescope had the consequence that Telescope could be restarted during the Outage Recovery Stage.  Fixed in AstroMain 3.66.4, Scope.SetPowerOff() routine modifed so that if ObsManager.bPermitPowerOff is set to True if bUnderOutageManagement is True.  Enum Switch changed from integer to short to correspond with ASCOM Switch Method
  Fixed 2024-03-13 (AstroMain 3.66.4)
   
• AstroMain Outage Management was unable to switch on & connect to Telescope during Outage Stage 6 (2023-03-12, System Test). With the Observatory in a Running/Suspended Session State, a system test was carried out involving a 10 minute Power Outage to the Observatory. After Stage 4, the LX200 Power was turned off manually from the Pegasus UPB Software.  During Stage 6, the RecoverFromOutage() routine was being run, and whilst attempting to Connect Scope the message "Telescope Power is off" was reported instead of turning on the Scope Power & Connecting it.  Examining code and log message seems to indicate that objPowerBox.GetSwitch(Switch.LX200) = True, suggesting LX200 power is already on.
  Fixed in AstroMain 3.66.4, Scope.SetPowerOn_Quiet() required an condition ( Or (ObsManager.bRunning = True And ObsManager.bUnderOutageManagement)  ) to allow Scope Power to be turned on.
  Fixed 2024-03-13 (AstroMain 3.66.4)
   
• New RecoverFromOutage () routine held up for 3 mins after attempting to connect TheSky Telescope (2023-03-12, System Test).  A system test involving a 10 minute Power Outage to the Observatory was being run and during Stage 6 the RestoreFromOutage() routine was being run. The routine appeared to unexpectedly stop whilst attempting to Connect the TheSkyTelescope (confusing the user)  It would seem that the ConnectTheSkyTelescope routine had maybe encountered an unhandled exception which then brought dow the thread running the task and led to RestoreOutageDevices() being held in a 3 min wait loop.  However although it was initially throught to be due to an unhandled exception detailed checking  showed that appropriate exception trapping was in place and that the issue was actually due to the routine having exited early (as the Telescope Service hadn't been started first) and without setting the 'bConnectTelescopeDone' completion' flag.  Fixed in AstroMain 3.66.4, completion flag name changed to bRunningConnectTheSkyTelescope and set to True at each point that the routine can be exited.
  Fixed 2024-03-13 (AstroMain 3.66.4)
   
• There was an unnecesary 'Wait On Cooler' hold prior to first locate frame for Near Zenith Focus Field (19:22). Job executor entered a 'Waiting on CCD cooler' loop ahead of the first locate frame for NearZenith Focus Field to wait for CCD Temperature to reach set point of -20°C when the camera had already been sitting 20 mins or so at the this temperature setpoint. Does Job Executor / CCD Monitor restart the clock when session enters the 'Starting Session' Stage or when the Camera is connected (even if it is really a 'continuation' of the same connection).  Examination of code shows that CcdMonitor.PhaseStartTime is reset whenever ConnectCamera() routine is called regardless of any prior Camera state.
  Fixed 2024-03-17 (AstroMain 3.66.6)
   
• ObsViewer is showing a Focuser1 Steps value whilst power to TCF-S is off (2024-03-11). During 'power outage' system tests on 2024-03-11 the TCF-S focuser was turned off for a 3-4 minute period by the Outage Management in order to conserve the UPS Battery.  But ObsPics for the corresponding period show Focuser1 Steps with a green flag.  Flag should be red with Power Off text.  Fixed (but precise AstroMain version and date of fix are uncertain).
  Fixed 2024-03-12 (AstroMain 3.66.4)

Continuous Improvement

• Display the total number of targets listed & the total number of targets in the database on AstroPlan's Target List form.  This was idea that came out of a recent Observatory demonstration and it was noted that i would have been useful to have this information readiy available in AstroPlan. The Targets List already displays the number of rows shown in the list, so turning off all filters and redisplaying shows the total number of targets in the database - the current number is 3142 as at 2024-03-05.  numRows field changed to show the number of targets listed and the total number in database in format like  100 / 3142 targets listed.
  Done 2024-03-05 (AstroPlan 1.39.9)
   
• Add a blank row to Contents section of the Session Report File before 'Session Initiating' items. A blank line break make the contents list a bit clearer, particularly in the situation where there manual directed telescope sync & mapping before the start of fully automated operations.  Implemented in AstroMain 3.66.2 through modifiication to the ReportLineTitle() routine.
  Done 2024-03-05 (AstroMain 3.66.2)
   
• AstroMain's 'Reset Scope Pointing' routine should report any cancellation of the operation by the user or any other exited/aborted operations. Implemented in AstroMain 3.66.2 through either setting jobError = True or setting jobCancel = True as appropriate before each Exit Sub statement..
  Done  2024-03-05 (AstroMain 3.66.2)
    
• When connecting Hub Services, Telescope should be reported as 'Service not selected' if that is the case (19:15). Following a Re-Sync & Short Mapping Run the telescope was parked and as per design the telescope service was unchecked.  Upon clicking the 'C' button to connect Hub Services (Dome & Scope) and restart the telescope operations from parked state, the dome service was reported to have already started. There was the a log wait whilst the user was confused whether the Connect Hub Services routine had stalled or it was waiting 60s to connect after restarting the scope.  As it turns out the Start Hub Services routine ('C') had done its job and started/checked the Dome and finished, as Telescope Services hadn't been selected, which is consistent with the design.  In this situation the Start Hub Services should be helpful and report       "Telescope...... Info......Service not selected".   Implemented in AstroMain 3.66.2, the StartHubServices() routine is modified  to report the proposed line when called with CallMode.Manual.   .
  Done 2024-03-05 (AstroMain 3.66.2)
   
• Install new UPS unit into Observatory and test.  An Eaton 3C 850B (850VA) UPS Unit with Battery Backup has been recently acquired and tested (see Notes - Eaton 3C 850B UPS, 2024-03-05) , and now needs to be installed into the Observatory Computer Bay in the Observatory.  The unit will provide support to the UPB Powerbox, LX200 Telescope, SBIG Camera and USB Hubs during a short mains supply outage, to enable session to be continued if power returns or for the attached equipment to be gracefully closed down, in particular the Observatory's LX200 Telescope which must be parked before battey discharged. to ve   A diagram illustarting the existing and proposed new cabling can be see in Notes - Observatory Computing Bay Congfiguration, 2024-03-03 and in Fig 1 below.  Following indoor testing the UPS was installed in the Observatory on 2024-03--07. It wasn't possible to fit the 4 planned plugs directly into the 4 sockets with battery backup on the UPS, due to the 3 of the plugs having a wider footprint than a conventional plug (one a square smart plug for SBIG Camera and two A/C Adpater Plugs for USB Hubs). To get around this a small power strip had to be employed. (see Fig 2). Following the installation of UPS (including USB cable to computer), UPS Companion Software was installed, settings checked and relevant tests successfully carried out, switching off / switching on mains power to the UPS Unit.
  To do 2024-03-07(Observatory, UPS)
   
• Rename AstroMain's 'ObservatoryManager' class object to 'ObsManager'. Shortening the object name makes the code easier to read & write, the name ObsManager is already used to refer to the Observatory Manager.  Implemented in AstroMain 3.66.2.
  Done 2024-03-07 (AstroMain 3.66.2)
   
• Refactor the way that Camera properties are set within CCDCamera. Refactor the setting of Camera Properties by the CcdCamera object, introducing a new SetProperty(xProperty) method where the properties to change are flagged & update actioned,  the creation of new enum CcdProperty with list of camera properties that can be set, and  changes in.  Implemented in AstroMain 3.66.2.
  Done 2024-03-10 (AstroMain 3.66.2)
   
• Extend AstroMain's observatory control to manage UPS Battery power consumption during a mains supply outage and safely park the observatory Telescope. With a Eaton 3C 850B UPS System added to the Observatory Computing Bay with 850 VA / 9 Ah Battery Power to support the UPB Powerbox, LX200 Telescope, SBIG Camera and USB Hub during a Mains Power Supply outage, AstroMain's functions need to be extended to provide a logical & progressive reduction in power consumption by the connected devices, and critically to safely park the LX200, following guidelines defined in earlier evaluation (see Notes - Equipment &/ UPS Battery Management during a Power Supply Outage , 2024-03-03).  In progress.  Obs.PowerState holds the official Power Status of the observatory.    Values are 'Mains'  &  'Battery'.   New variables added are :  bUnderOutageManagement,  OutageStageNo.  bRunningOutageRecovery,  OutageRecoveryThread.  Implemented in AstroMain 3.66.2, but not yet tested in the Observatory.
  Done 2024-03-10 (AstroMain 3.66.2)
   
• Extend AstroMain's observatory control to recover equipment/devices that were turned off during Outage Management.  NNew code in AstroMain 3.66.2 progressively shuts down specific devices/equipment (LX200 Telescope, CCD Camera, TCF-S Focuser) to preserve UPS Battery life.  After Mains Power Supply has been restored, AstroMain's ObsManager need to restart those devices & equipment again, so that a session can continue again or be in a good position to begin a new one. The ObsManager also need to check and ensure that connection to the Pulsar Dome (which would have powerered down during the power outage) and to the AllSky/Weather computer are re-establised.  Implemented in AstroMain 3.66.2, but not yet tested in the Observatory.
  Done 2024-03-10 (AstroMain 3.66.2)
   
• ObsViewer pictures to show a white flag against the 3 Cloud Sensor fields, Rain, Clarity & Light when the Mains Power is off.  During a power outage the Pegasus USB Hub in the AllSky/Weather cabinat stops working and there is a lost in communication with the CloudSensor until the UCB Com Port is restarted (disable, followed by enable).  The fields should be shown with a flag at this time to signify that the data is no longer fresh.
  Done 2024-03-11 (AstroMain 3.66.3)
   
• ObsViewer pictures to show a white flag and '--' when the Mains Power is off.  During a power outage the Pulsar Dome controller isn't working and the driver produces volatile message with mostly zero values. ObsPic is currently drawing a cyan field with text 0.0°C.  This is misleading/incorrect. Instead a white flag with the text '--' should be drawn..
  Done 2024-03-11 (AstroMain 3.66.3)
   
• Add power monitoring to AstroPlan and AstroAllSky and use power state to restart WebLoader following a power outage. During system tests on 2024-03-11 when a Observatory mains power outage was introduced, neither AstroPlan or AstroAllSky were able to automatically begin uploading of files to the Observatory's website.  Whilst both programs have a routines that automatically restart the Web Uploaders in certain situatons, they would seem not to be able to recognise the power outage as one of those situations. The failure of the Ethernet Switch unit to reconnect to the router & internet following the outage, may have complicated the situation, but in due course a Zigbee Smart Plug will be added to allow the Ethernet Switch to be rebooted.  Implemented in AstroPlan 1.39.10, AstroAllSky 3.20.1, the WebUploader is restarted 45s after power is restored to allow time for Switch / LAN to be restarted.  This may still be too short and may need to be increased to allow more time for LAN to be restored.  (Prehaps LAN Ping time can be checked ?) .
  Done 2024-03-12 (AstroPlan 1.39.10, AstroAllSky 3.20.1)
   
• Modify AstroWeather to automatically restart CloudSensor and Virtual Weather Station programs if their data records are more than 4 minutes old.  Following system testing it is apparent that CloudSensor and WeatherStation data doesn't always begin refreshing again after a power cut (even though CloudSensor program is restarted by AstroWeather's new Power Monitor).  As a contingency an extra backup is required to restart either program after 4 minutes if data is not getting refreshed.
  Done 2024-03-13 (AstroWeather 1.23.14 )
   
• Add a zigbee smart plug to allow observatory's Ethernet Switch to be reset in order to restore LAN & Ethernet connection.  Following an 11 min power outage in the Observatory, part of a series of system tests,on 2024-03-11 (see here),  both the observatory computer's lacked LAN/internet access after the power was restored.  Resetting the Ethernet over Powerline adapter (manually) didn't resolve things, but resetting the observatory's Netgear Ethernet Switch did..  It is proposed to add a Zigbee SmartPlug to the Observatory's Zigbee Network to allow this Network Switch to be reset by the AstroMain Observatory Control Manager in order to regain LAN/Internet access. The Smart Plug arrived 2024-03-13 and has been added to the zigbee network as Light ID 8 with the name 'Ethernet Switch', and has been integrated into AstroMain 3.66.6 allowing a restart of Ethernet Switch to be made via button routines. In practice any reason that requires a restart (turn off/turn on) of the Ethernet Switch very likely prevents means that the LAN communications to the Observatory are down, and therefore would prevent a remote connection and necessiate an Observatory visit to resolve. However it does provide a basis for adding automated control over the Ethernet Switch in due course.
  Done 2024-03-15 (AstroMain 3.66.6)
   
• AstroMain's reporting needs a blank line between the end of 'Connect TheSky Telescope' and a follow up user operation (18:28).  Under manual control the 'Connect TheSky6 Telescope'  button was used to connect the telescope in TheSky6, after which the user click clicked 'Slave Dome'. It was noted that the report line with message 'Slaving is On (User) " and subsequent Zigbee event reporting with message "Dome has unparked (18:31:25, Zigbee sensor)" appear directly after the final line of the Connect TheSky Telescope section "SideOfPier = Not implemented".   A line or blank row should be inserted.   This is a tricky one to implement successfully, how to avoid double lines or double blank lines during live session. Finalise Report can remove the repeats.  Code has been added to ReportComment () routine in AstroMain 3.66.7 that should avoid the writing of two successive blank rows to both console & report file. A blank row is written at the end of ConnectTheSkyTelescope() routine
  Done 2024-03-21 (AstroMain 3.66.7)
   
• Add logic to AstroMain's ObsManage / Outage Manager to automatically restart Ethernet Switch in attempt to restore LAN & Ethernet connection to the Observatory. A Zigbee Smart plug has been recently been installed in the Observatory that can allow power to the Ethernet Switch to be turned off & turned on via the Observatory's Zigbee Network in order to restart the Ethernet Switch.  In some cases this action can bring back a failed LAN / Ethernet Connection.   Operation of the Smart Plug has been integrated into AstroMain 3.66.6, but it requires logic to be added to Obs.Manger / Outage Manger to recognise a condition that it would be worth trying to restart the Ethernet Switch and then to action it automatically.   The logic would be that Obs.PowerState =  MainPower and LAN ok, but Internet is down (ping (google.com) = false and ping ping (bbc.co.uk) = false) or  LAN not ok for > 10 mins and TimeSInceLastReset > 5 mins.  After further review (following a bout of problems in Sep 2024) it was established that restarting the Ethernet Switch doesn't guarentee a resolution of the Lan/Ethernet connectivity but what it does is stop communication between the Observatory Computer and the AllSky/Weather Computer, which lead to problem if a session is in progress.
  Closed (not done)  2024-10-04 (Observatory, LAN/Ethernet Connection)
   
• Carry out a series of System Tests to re-test the robustness of the Observatory/Sessions to a main power outage.  Following multiple actions and improvements to the Observatory (including installtion of a UPS System to support the LX200 Telescope) and modifications to various operating & management programs (AstroMain, AstroWeather, AstroAllSky) a series of System Tests should be carried out to re-test the robustness of the Observatory/Sessions to a main power outage in order to verify the efficiency of work recently undertaken and to identify any remaining issues & gaps. First pair of tests carried (Daytime without Telescope, 10s & 11 min outages) carried out 2024-03-11.  (See System Tests - Examining robustness of Observatory system to a mains power supply outage).  After updating AstroMain further tests were carried during the live session S1197 (2024-03-13).  This uncovered an previously unknown issue that Pulsar Dome can encounter a glitch where is resets all it settings.
  In Progress 2024-03-12 (Observatory, Power Supply)

[ Prev | Next ]

Back to Top

2024-03-05

AstroMain - Task Manager Assistant

Back to Top

2024-03-11

System Tests - Examining robustness of Observatory Operations to a mains power supply outage

Back to Top