David's Astronomy Pages Notes - Session 1192 (2024-02-25)

Notes (S1191)

Notes Main

Home Page

Notes (S1193)

	Session Aims & Highlights
	- Observing Result  - Night Summary Plot  - Session Event Log
	Operational Issues
	- Critical Issues (0),  Major Issues (1),  Minor Issues (7),  Small Defects (5),  Continuous Improvement (9)
	Images from 2024-02-25 >>
	Investigation - Effects of Short Power Outage (06:14)

Session Aims & Highlights (2024-02-25)

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. Telescope Pointing. Continue to c7heck pointing accuracy follow telescope sync & short mapping job during S1190 session,
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.
5. Demonstration. Demonstrate operation of the Observatory and Pulsar Dome in particular to a visitor from Glasgow.

 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.19, 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.10
  (AstroWeather 1.23.10, AstroAllSky 3.19.11,  AstroObsCam 1.11.4, AstroLaunch 1.11.1

Highlights

• Targets. 13/35 planned targets observations were completed, with 7 other targets partially completed. Other targets failed due to cloud & rain / session suspension.
• 12P/Pons-Brooks. Only some of planned images of Comet 12P/Pons-Brooks were acquired due to developing cloud/session suspension.
• Telescope Pointing. Telescope Pointing Accuracy was good with average. This continues to confirm that the Telescope ReSync & Short Mapping Run in earlier  S1190 session were successful in improving the telescope pointing accuracy.
• AstroMain. No issues with CCDSoft Camera/SBIG Camera.
•  Dome Parking.  Dome parked ok at the correct position at end of the session.
• Demonstration. Operation of the Observatory including Pulsar Dome including automated operation during live session were successfully demonstrated to visitor.

Notes:

• Short Mapping Job was eventually conducted but it it was unusually complicated and after the telescope restart from Park there were some issues with unstable communication with the PHD2 server.

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:39:23 Session Monitoring AutoStart monitoring for Live Session opportunity between 18:39 & 05:07 18:39:24 Session AutoStarting Session autostarting (18:39) 18:39:43   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.) 18:39:56 Session Created Session Created (Live, 2024-02-25 S01192, ImageSaveNum: 1192001) 18:40:03   Scope Switched On Telescope Power has been switched on via UPB Powerbox. 18:41:49   Services Started Observatory Services started 18:41:56 Observatory (Auto) Observatory placed in Fully-Automated Mode 18:41:59 Session Pending Session pending (2024-02-25) 18:42:01 Session Initiating Session initiating (2024-02-25) 18:42:03   Plan Requested Observing Plan requested from AstroPlan (1.39.7) 18:43:22   Plan Loaded Observing Plan loaded to queue (Plan ID: 966) 18:43:44   Camera1 Connected SBIG Camera connected (Set point -25°C) 18:44:21   Telescope Connected Telescope connected (TheSky6) 18:44:45 Session Equilibration Session ready to Open Dome 18:45:30   Dome Opened Dome opened (Opening time 45s, Zigbee 41s) 18:45:32 Session Running Session running 18:45:35   Queue Started Observing Queue started (35 targets selected) 18:45:36     Target Started (NrZen) Target started (Focus Field 5, HIP 23569) 18:45:50       Dome Unparked Dome unparked 18:51:18       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 18:54:06       Focusing Completed Foc1 AutoFocus Completed (Profile No 1, wide) 18:56:06       Focusing Completed Foc1 AutoFocus Completed (Profile No 1) 18:56:08       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 18:58:22       Focusing Completed Foc2 AutoFocus Completed (Profile No 2, wide) 19:00:10       Focusing Completed Foc2 AutoFocus Completed (Profile No 2) 19:00:29     Target Completed (NrZen) Target completed (Focus Field 5, HIP 23569) 19:00:34     Target Started (1/35) Target started (1/35, UGC 12639 w/SN2023jri) 19:04:49       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 19:16:04       SoftSuspend Called Soft Suspend is called due to Deteriorating Conditions (too few stars) 19:16:59   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 19:17:01   HardSuspend Called Hard Suspend is called due to Critical Conditions (cloud) 19:17:04     Target Aborted (1/35) Target aborted (1/35, UGC 12639 w/SN2023jri) due to cloud 19:17:06   Queue Paused Queue paused for Session Suspension 19:17:08 Session Suspending Session suspending 19:17:54   Dome Closed Dome closed (Closing time 50s, Zigbee 43s) 19:17:56 Session Suspended Session suspended 19:33:51 Session Resuming Session resuming 19:34:36   Dome Opened Dome opened (Opening time 45s, Zigbee 41s) 19:34:38 Session Running Session running 19:34:40   Queue Resumed Observing Queue resumed 19:34:43     Target Started (2/35) Target started (2/35, 12P/Pons-Brooks) 19:42:50     Target Completed Target partially completed (2/35, 12P/Pons-Brooks) 19:42:54     Target Started (3/35) Target started (3/35, GCVS HH And) 19:48:14     Target Completed Target completed (3/35, GCVS HH And) 19:48:18     Target Started (4/35) Target started (4/35, C/2017 K2 (PANSTARRS)) 19:51:59       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 20:00:01     Target Completed Target completed (4/35, C/2017 K2 (PANSTARRS)) 20:01:29     Target Started (5/35) Target started (5/35, UGC 3174 w/SN2023mut) 20:05:10       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 20:07:34       Focusing Completed Foc1 AutoFocus Completed (Profile No 3) 20:23:25     Target Completed Target completed (5/35, UGC 3174 w/SN2023mut) 20:23:29     Target Started (6/35) Target started (6/35, GCVS GW Ori) 20:26:15       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 20:28:25       Focusing Completed Foc1 AutoFocus Completed (Profile No 4) 20:42:08     Target Completed Target completed (6/35, GCVS GW Ori) 20:43:30     Target Started (7/35) Target started (7/35, AT2023ati) 20:46:37       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 20:48:49       Focusing Completed Foc1 AutoFocus Completed (Profile No 5) 21:04:49     Target Completed Target completed (7/35, AT2023ati) 21:05:30     Target Started (8/35) Target started (8/35, 103P/Hartley) 21:09:01       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 21:11:28       Focusing Completed Foc1 AutoFocus Completed (Profile No 6) 21:22:29     Target Completed Target completed (8/35, 103P/Hartley) 21:22:34     Target Started (9/35) Target started (9/35, GCVS YZ Cnc) 21:25:19       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 21:27:29       Focusing Completed Foc1 AutoFocus Completed (Profile No 7) 21:33:56     Target Completed Target completed (9/35, GCVS YZ Cnc) 21:35:15     Target Started (10/35) Target started (10/35, C/2021 F1 (Lemmon-PANSTARRS)) 21:38:21       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 21:46:59     Target Completed Target completed (10/35, C/2021 F1 (Lemmon-PANSTARRS)) 21:50:04     Target Started (11/35) Target started (11/35, CGCG 119-104 w/SN2024cdi) 21:53:01       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 21:55:18       Focusing Completed Foc1 AutoFocus Completed (Profile No 8) 22:11:32   Critical RainThreat Alert Critical Rain Threat Alert (Obs.Manager will close the Dome) 22:11:34   HardSuspend Called Hard Suspend is called due to Critical Conditions (threat of rain) 22:11:36     Target Aborted (11/35) Target aborted (11/35, CGCG 119-104 w/SN2024cdi) due to threat of rain 22:11:38   Queue Paused Queue paused for Session Suspension 22:11:40 Session Suspending Session suspending 22:12:27   Dome Closed Dome closed (Closing time 50s, Zigbee 44s) 22:12:29 Session Suspended Session suspended 22:31:20     Target Cancelled Target cancelled (12/35, AT2024ajf) due to cloud 22:40:21 Session Resuming Session resuming 22:41:06   Dome Opened Dome opened (Opening time 45s, Zigbee 41s) 22:41:08 Session Running Session running 22:41:10   Queue Resumed Observing Queue resumed 22:41:13     Target Started (13/35) Target started (13/35, AT2023cub (CV)) 22:43:06       SoftSuspend Called Soft Suspend is called due to Deteriorating Conditions (reducing clarity) 22:43:08   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 22:43:10   HardSuspend Called Hard Suspend is called due to Critical Conditions (cloud) 22:43:12     Target Aborted (13/35) Target aborted (13/35, AT2023cub (CV)) due to cloud 22:43:14   Queue Paused Queue paused for Session Suspension 22:43:16 Session Suspending Session suspending 22:44:01   Dome Closed Dome closed (Closing time 50s, Zigbee 44s) 22:44:04 Session Suspended Session suspended 22:45:20     Target Cancelled Target cancelled (13/35, AT2023cub (CV)) due to rain 23:05:40     Target Cancelled Target cancelled (14/35, SN 2022actt) due to threat of rain 23:11:30 Session Resuming Session resuming 23:12:15   Dome Opened Dome opened (Opening time 45s, Zigbee 41s) 23:12:17 Session Running Session running 23:12:19   Queue Resumed Observing Queue resumed 23:12:22     Target Started (15/35) Target started (15/35, NGC 3690 w/SN2023wrk) 23:16:10       SoftSuspend Called Soft Suspend is called due to Deteriorating Conditions (reducing clarity) 23:16:13   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 23:16:15   HardSuspend Called Hard Suspend is called due to Critical Conditions (cloud) 23:16:17     Target Aborted (15/35) Target aborted (15/35, NGC 3690 w/SN2023wrk) due to cloud 23:16:19   Queue Paused Queue paused for Session Suspension 23:16:21 Session Suspending Session suspending 23:17:06   Dome Closed Dome closed (Closing time 50s, Zigbee 44s) 23:17:08 Session Suspended Session suspended 23:28:00     Target Cancelled Target cancelled (15/35, NGC 3690 w/SN2023wrk) due to cloud 23:39:44 Session Resuming Session resuming 23:40:29   Dome Opened Dome opened (Opening time 45s, Zigbee 41s) 23:40:31 Session Running Session running 23:40:33   Queue Resumed Observing Queue resumed 23:40:35     Target Started (16/35) Target started (16/35, AT2023cxz (CV)) 23:47:02     Target Completed Target partially completed (16/35, AT2023cxz (CV)) 23:47:06     Target Started (17/35) Target started (17/35, SN 2023iy) 23:50:15       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:52:27       Focusing Completed Foc1 AutoFocus Completed (Profile No 9) 00:08:38     Target Completed Target completed (17/35, SN 2023iy) 00:08:42     Target Started (18/35) Target started (18/35, 65P/Gunn) 00:12:34       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:14:42       Focusing Completed Foc1 AutoFocus Completed (Profile No 10) 00:23:16     Target Completed Target completed (18/35, 65P/Gunn) 00:23:20     Target Started (19/35) Target started (19/35, IC 4305 w/SN2023edc) 00:26:42       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 00:42:54     Target Completed Target completed (19/35, IC 4305 w/SN2023edc) 00:42:59     Target Started (20/35) Target started (20/35, AT2023tsk) 00:45:41       Focusing Skipped Foc1 focusing skipped - unable to find a star (TCF-S) 01:02:18     Target Completed Target completed (20/35, AT2023tsk) 01:03:54     Target Started (21/35) Target started (21/35, NGC 3893 w/AT2023uhx) 01:07:52       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:10:17       Focusing Completed Foc1 AutoFocus Completed (Profile No 11) 01:23:53       SoftSuspend Called Soft Suspend is called due to Deteriorating Conditions (too few stars) 01:24:38   Critical RainThreat Alert Critical Rain Threat Alert (Obs.Manager will close the Dome) 01:24:40   HardSuspend Called Hard Suspend is called due to Critical Conditions (threat of rain) 01:24:43     Target Aborted (21/35) Target aborted (21/35, NGC 3893 w/AT2023uhx) due to threat of rain 01:24:45   Queue Paused Queue paused for Session Suspension 01:24:47 Session Suspending Session suspending 01:25:33   Dome Closed Dome closed (Closing time 50s, Zigbee 44s) 01:25:35 Session Suspended Session suspended 01:37:30     Target Cancelled Target cancelled (22/35, AT2021aena (CV)) due to cloud 01:55:02     Target Cancelled Target cancelled (23/35, 62P/Tsuchinshan) due to cloud 02:15:52     Target Cancelled Target cancelled (24/35, UGC 8317 w/AT2022qvu) due to cloud 02:37:52     Target Cancelled Target cancelled (25/35, NGC 5630 w/SN2023zdx) due to cloud 02:59:52     Target Cancelled Target cancelled (26/35, SN 2023zvq) due to threat of rain 03:01:41 Session Resuming Session resuming 03:02:26   Dome Opened Dome opened (Opening time 45s, Zigbee 41s) 03:02:28 Session Running Session running 03:02:30   Queue Resumed Observing Queue resumed 03:02:56     Target Started (27/35) Target started (27/35, UGC 10717 w/SN2022ybd) 03:06:09       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:07:47       SoftSuspend Called Soft Suspend is called due to Deteriorating Conditions (too few stars) 03:08:17       SoftSuspend Cancelled Soft Suspend is cancelled due to improved conditions 03:08:34       Focusing Completed Foc1 AutoFocus Completed (Profile No 12) 03:11:47       SoftSuspend Called Soft Suspend is called due to Deteriorating Conditions (reducing clarity) 03:11:49   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 03:11:51   HardSuspend Called Hard Suspend is called due to Critical Conditions (cloud) 03:11:53     Target Aborted (27/35) Target aborted (27/35, UGC 10717 w/SN2022ybd) due to cloud 03:11:55   Queue Paused Queue paused for Session Suspension 03:11:57 Session Suspending Session suspending 03:12:42   Dome Closed Dome closed (Closing time 50s, Zigbee 44s) 03:12:45 Session Suspended Session suspended 03:22:12     Target Cancelled Target cancelled (27/35, UGC 10717 w/SN2022ybd) due to rain 03:44:12     Target Cancelled Target cancelled (28/35, AT2023osr (CV)) due to cloud 03:58:32     Target Cancelled Target cancelled (29/35, AT2023txn) due to rain 04:16:31 Session Resuming Session resuming 04:17:16   Dome Opened Dome opened (Opening time 45s, Zigbee 41s) 04:17:19 Session Running Session running 04:17:21   Queue Resumed Observing Queue resumed 04:17:23     Target Started (30/35) Target started (30/35, UGC 11858 w/SN2023rjj) 04:22:42       SoftSuspend Called Soft Suspend is called due to Deteriorating Conditions (too few stars) 04:25:02   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 04:25:04   HardSuspend Called Hard Suspend is called due to Critical Conditions (cloud) 04:25:07     Target Aborted (30/35) Target aborted (30/35, UGC 11858 w/SN2023rjj) due to cloud 04:25:09   Queue Paused Queue paused for Session Suspension 04:25:11 Session Suspending Session suspending 04:25:58   Dome Closed Dome closed (Closing time 50s, Zigbee 44s) 04:26:00 Session Suspended Session suspended 04:40:52     Target Cancelled Target cancelled (31/35, AT2023akq) due to too few stars 04:41:25 Session Resuming Session resuming 04:42:10   Dome Opened Dome opened (Opening time 45s, Zigbee 41s) 04:42:12 Session Running Session running 04:42:14   Queue Resumed Observing Queue resumed 04:43:56     Target Started (32/35) Target started (32/35, AT2023abtv (CV)) 04:47:11       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 04:49:22       Focusing Completed Foc1 AutoFocus Completed (Profile No 13) 04:54:16       SoftSuspend Called Soft Suspend is called due to Deteriorating Conditions (too few stars) 04:55:46     Target Completed Target completed (32/35, AT2023abtv (CV)) 04:55:48   Queue Paused Queue paused for Session Suspension 04:55:50 Session Suspending Session suspending 04:56:37   Dome Closed Dome closed (Closing time 50s, Zigbee 44s) 04:56:39 Session Suspended Session suspended 05:05:10     Target Cancelled Target cancelled (33/35, GCVS BL Lac) due to rain 05:25:30     Target Cancelled Target cancelled (34/35, AT2023tow) due to cloud 05:49:30     Target Cancelled Target cancelled (35/35, AT2023udd (CV)) due to too few stars 05:49:36   Queue Completed Job Queue completed 05:49:39 Session Closing Session closing 05:49:44   Dome Closed Dome already closed (closed at 04:56, closing time 50s, zigbee 44s) 05:50:02   Dome Parked Dome parked (parking time 10s), Az: 90.1 deg 05:51:26   Telescope Parked Telescope parked (parking time 81s) 05:51:41   Telescope State Handbox reads 'Scope parked Turn scope off.' 05:52:04   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 05:53:25   Dome Charging Dome is parked and re-charging Ok (17mA) 05:53:27   Services Stopped Night Services stopped 05:53:30 Session Finishing Session Finishing started (Create Fits Summary, Transfer Files) 05:53:47     Dome (Find Park) Find Park started (Search Az 87.0 to 93.0°, Step 0.2°, Narrow) 05:55:19     Dome Find Park found (Best Park Az 90.4°) 05:55:25     Dome Dome has been synced at park position (Az 90.0°, Adjustment: -0.5°) 05:55:27   Dome Parked Dome parked 05:57:25   Dome Charging Dome is parked and re-charging Ok (25mA) 05:57:27 Session Finished Session Finished

Session Alerts & Alarms

Time     Type       Name Detail 19:01:00 Yellow Alert Anomalous Dome Slew Dome slew resumed at Az 195.0° (T+21.5s) 05:57:25 Green Clear Dome Charging Dome is parked and re-charging Ok (25mA)                         Post-Session    06:16:50 Yellow Alert UPB.Switch disconnected UPB.Switch has unexpectedly disconnected. Restart will be attempted 06:15:08   Yellow Alert Shutter Battery Shutter battery level has fallen below 88% 06:15:10   Red Alert Shutter Battery Shutter battery level has fallen below 85%

Back to Top

Operational Issues (2024-02-25 S1192)

• Critical Issues (0)
• Major Issues (1)
• Minor Issues (7)
• Small Defects (5)
• Continuous Improvement (9)
  

[ Prev | Next ]

Critical Issues

• None

Major Issues

• Relay function on Pulsar Dome not fully working (pre-session, shutter didn't close 12:38 & 12:44) .  The observatory dome has a relay connection to the observatory's CloudSensor . When the CloudSensor determines that conditions are unsafe (as they normally are during the daytime with its high light levels) the shutter will automatically close. The Dome's Relay settings have been set with a 30s delay, such that 30s of Unsafe conditions are needed before the Relay triggers an action to close the shutter.   During daylight demonstration of the dome/relay operation ahead of the S1192 session the shutter was commanded to open with the expectation that after 30s the dome control unit would intervene and command the shutter to begin closing.  However whilst the shutter opening stopped after 30s the shutter then remained partially open and didn't close.    DeviceHub.Dome reported that the shutter was still opening, and ObsViewer virtual view of the Observatory shows a Purple flag against 'Dome Relay' with the message " Dome Relay Error (2)" .  The shutter was closed manually via the Red button on the Shutter drive.   The test was repeated again, with the same result (ie the shutter stopped opening after 30s but didn't close leaving the shutter about 70% open)  When last tested  (around 1 year ago / check wrt to Charles Wang visit last year) the shutter would stop after 30s and then automatically close..  This is a potentially critical issue if the primary means of operating the observatory fails and it starts raining.  The dome's relay is meant to be a fail safe backup to AstroMain/AstroGuard Management Programs, but if the relay or dome aren't working correctly then the aren't providing the required last-resort protection.  Daytime tests need to be conducted - is the issue still occuring, does it still happen if the Pulsar Dome system is restarted. Is the issue due to a problem with a) the Relay, b) the Relay Settings  c) a transient/one-off problem with the Dome Controller which will go away if the Pulsar Dome is turned off and then turned on again, d) a bug introduced to Pulsar Driver installed in Q4 2024.  The "Error (2)" message is shown when Dome.RelayFlag = fRelayError (=2).   Dome.RelayFlag is set equal to DomeRecord.Relay in RunPulsarDomeMonitor() which is itself set equal to the 13th field in Pulsar Dome's 'Volatile' record.     Relay value was 1 (unsafe) up until 12:38:26 when Dome was disconnected from ASCOM./AstroMain for the demonstration and had value 2 (error) when Dome was reconnected to ASCOM/AstroMain at 12:44:28.  The DomeRecord.Relay value remained as 2 until is changed to 0 at 17:46:04.  This ties up with when CloudSensor became Safe, when Light Level fell below 20
  Tests on 2024-02-26 (after a precautionary reboot of the Pulsar Dome) should the dome is now responding correctly to the state of the Relay from the Cloud Sensor.  Despite this it is proposed to test the system on a more regualr / more frequent basis and also contact Pulsar Observatories regading the case.
  Closed after repeat testing  2024-02-26  (Pulsar Dome)
  
  Post-Session Test at 16:27 :   With Shutter fully open CloudSensor set to Unsafe (by reenabling Light Condition) at 16:27:22 , shutter began closing at 16:27:44 . This is 20s later which corresponds to the Dome Relay's 'delay' setting,. Shutter finished closing at 16:28:28 (closing time 44s), 64s after CloudSensor changed to Unsafe.
  
  Pre-Session 12:38  look at Pulsar Log regarding Shutter Status - any clues ?

Minor Issues

• ObsViewer shows 'Dome Relay' flag in purple with message "Dome Relay Error (2)" . In pre and post session daylight testing of Dome Relay / Automatic Dome Closure with the CloudSensor indicating 'Unsafe' (due to Light levels) it was observed that when Dome Closure was commanded by the Dome Closure following the prescribed  'delay' (typically set as 20 or 30s), the Relay field in the Pulsar's Volatile record changes to a 2.   Previously this has been interpreted as an 'Error'  and the ObsViewer has been coded to change the Dome Relay flag on ObsViewer/ObsPic to purple and write the text "Dome Relay Error (2)".  It had already been noticed that shortly before the S1192 started that the relay field value changed back to 0 (Safe). as the sky darkened.   Tests today show that after the relay triggers a shutter closue and Pulsar's relay field value changes from 1 to 2   and that after temporarily disabling 'Light' threshold in the CloudSensor head, the relay relay field value changes to 0 (Safe).  But then reenabling 'Light' element in CloudSensor results in the Pulsar's relay field value to revert back to 2 rather than back to 1 (Unsafe).  Reviewing the ASCOM log from the last night's S1192 session however showed the Pulsar relay value turning from 0 back to 1 during a short cloudy interval at 19:18 rather than reverting back to 2 (even though it had been 2 earlier in the same Pulsar log.  Overall it would seem that Pulsar relay field value of 2 means Dome Relay 'Unsafe'  but incorporates some knowledge by Pulsar Dome that the Relay has triggered a shutter closure, would could allow the Pulsar Dome to auto-open if the Pulsar's AutoOpen Relay setting is enabled.  (This fetaure is always disabled in the Clair Observator).  Rather than show a purple flag & error when the Relay value is 2 it is proposed to change it to a  Red Flag & Unsafe (2)'  to not cause undue concern yet record the difference from the usual value  (Unsafe (1) ). Implemented change in AstroMain 3.65.20
  Fixed  2024-02-26+  (AstroMain 3.65.20)
   
• Cloud Sensor data stopped refreshing (post-session, 06:14). At 06:14 about 15 mins after the S1192 session the Cloud Sensor data stopped refreshing. AstroWeather shows red flag against CloudSensor with last refresh time of 06:14. Investigating indicated that this corresponded with the time of a minor power outage to the Observatory, which is known to 'knock out' the CloudSensor. Dat didn't begin refreshing again the CloudSensor program was manually restarted at 11:29. Issue understood and closed after review. A separate continuous improvement ticket has been raised to make AstroWeather automatically restart CloudSensor when it appears to have stopped refreshing data.
  Closed after review 2024-02-26  (Session, CloudSensor, AstroWeather, Power Supply)
   
• AstroMain didn't seem to detect Observatory Door opening event (post session, 11:05).  The Observatory was visited around  11:05 in order to perform user testing of the Dome/Dome Relay and the door opened and left open during the visit.  AstroMain console didn't show the expected 'Door has opened' messages and the ObsViewer continued to show the door as closed, however the door was physically still open.  What was going on?   The time that the door was opened is somewhat uncertain - the first suggestion of user activity was at 11:06:35 with message related to RestartSwitch() and seems to correspond to when two 'UPB.Switch' error dialogs were dismissed after first opening Observatory Computer screen. At 11:07:37 the Zigbee log indicates that the Zigbee Network was queried, however no results of the query were reported in the report log, and then at 11:08:24 the TCF-S service was re-started as a user action as it had become upset by a short power outage earlier in the morning (06:14).  Based on the zigbee log, the zigbee/deconz network query at 11:07:37 indicates that the Observatory Door Sensor (sensor id 5) had the state "open":true (whilst in the network query at 09:00 the state was "open":false.   This implies that the sensor was responding correcly to the opening of the door, but the change in state was somehow unknown to the AstroMain's Zigbee Service. Logs indicate that there were network queries/commands at 09:00, 11:07 & 11:09, but  no zigbee events were recieved between 06:15:00 (aroundthe  time of the 06:14 power outage) and 11:13:47 (following the stopping & restarting of deConZ and the restart of Zigbee service at 11:13:27).     The Zigbee Service was stopped and restarted a little earlier at 11:09 but this didn't lead to any network events occuring, even though it did trigger the start of recording teh Door as Open on the ObsViewer/ObsPic pictures. The reason why it worked at 11:13 and not at 11:09 seems to be that the deCONZ program had been restarted at 11:12, which triggered the start of the deCONZ WebSocket service. Around this time the deCONZ II adapter was also taken out and reinserted into its USB port (an action which may/may not be important). T  he failure by AstroMain to report the Observatory door opening at 11:05 is concluded to be due to it not recieved any Opening Event for the Door due to the Zigbee WebSocket being out of action following the short power outage at 06:14. A reboot of deCONZ and a restart of the Zigbee Service should be adopted in the event of the WebSocket events stopping.    A separate Continuous Improvement ticket has been raised to provide automated monitoing of the status of the Zigbee
  Issue understood 2024-02-26  (Session, DeConz , AstroMain Zigee Service, Power Supply)
   
• Power supply to Observatory took a short outage, with impacts on various Observatory elements (post-session, 06:14).   At 06:14 there was a small power outage to the observatory.  AstroMain recorded about a Observarory / Power Alert at 06:14 with the message "Power Outage (1) Detected' . The outage caused a disconnection of the UPB Switch. with AstroMain reporting "Unexpected disconnection of UPB.Switch (06:14). Attempting restart...  " and taking the action to Restart Powerbox Services inclduing restarted Powerbox Software. The outage knocked out the CloudSensor (causing data from CloudSensor to stop at 06:14:44 until the CloudSensor program was manually restarted at 11:29.   The outage knocked out the TCF-Focuser service until manually restarted at 11:08.  The outage also resulted in deCONZ WebSocket being knocked out of action which was resolved by manually restarting program and restarting the Zigbee service at 11:13. The outage temporarily knocked out the LAN Switch as log file contains 'No such host is known' exception message whilst attempting to SetIPAdddress starting at 06:14:46 and lasting to 06:15:35. .  Problems caused by the power outage could be largely resolved by having a battery system backup  to get past any small outages, but configuring them to work for both bays and still permit Ethernet over power line would purchase of suitable backup system and possibly a reconfiguration of the observatory electrics.  ObsPics show that connection with LAN and to AllSky/Weather Computer (LAPTOP7), based on successful pings, dropped out between 06:14:30 & 06:15:07 and then came back between 06:15:38 & 06:16:19.  A separate continuous improvement ticket is raised to examine solutions or better mitigations to this issue.  (See see Investigation - Effects of Short Power Outage (06:14)  &  Review - Increasing observatory & session resistance to small power outages, 2023-02-27 )
  Issue investigated 2024-02-26  (Session, Power Supply)
   
• LX200 Handbox LCD Panel not showing any text although Panel is lit up. During daylight demonstration of telescope/dome operation it was noted that the screen, whilst lit, wasn't showing any text information.   Up/Down, Left/Right buttons weren't tested.  Telescope was operating normally over ASCOM.  This appears to be a continuation of handbox issue noted during session S1190 (2024-02-23) where the screen was blank and the up/down/ left/right buttons which were initially operating ok to centre on a star (Capella) didn't operate when attempting a scope movement some 10-20 minutes later.  Is this a failure of the handbox or a contrast/dimness setting glitch ? During the following S1193 session (2024-02-26) the observatory was visited whilst telescope was operating.  AstroMain's Virtual Handbox was brought up and 'Utilities/Brightness Adj' in order to try adjusting the handbox brightness. The screen message reads  'Adj. with arrows. Then press Enter '. Pressing arrows changed the LCD screen brightness in the range bright to dim but no text could be made to appear.  Although it messed up final frames from one target, the arrows buttons to move the telescope left, right, up, down, which proved that there is no fundamental issue with connection to the LX200 itself.  Hence it seems that the problem is with the LCD Screen or connectors to the LCD.  One thing to try next would be to bring the handbox indoors and give it a proper warming up (it sits in the cold observatory environment all winter and probably suffers as a consequence, but otherwise a new handbox is probably called for.  First Light Optics give price as £150 but noted that they are out of stiock, but due in 20-25 days.  Some people have tried removing and reseating the ribbon cable and this can bring a display back to life "There is a small plastic wedge that is used to secure the ribbon so if you pop that free first, you can pull out the ribbon. Look at the contacts and maybe clean them with a soft eraser, then refit and see what happens" https://www.cloudynights.com/topic/610966-no-text-on-autostar/ .   Also  https://www.cloudynights.com/topic/846245-autostar-ii-controller/  .   There is also an Autostar II menu option 'Utilities/Contrast Adj.'  this needs to be tried during a daytime test. Attempt made on 2024-03-02 to change Contrast on HandController using 'Contrast Adj option in the LX200's Utilities Menu option, but using the Scroll Up and Scroll Down buttons didn't make an text visible appear on the Hand Controller screen.   Will have to decide whether the cost of a new Hand Controller is worth it or not. Eventually decided 2024-03-09 to order a new handbox from First Light Optics after it had come back into Stock. (https://www.firstlightoptics.com/meade-telescopes/meade-autostar-ii-hand-controller.html).  The replacement handset arrived on 2024-03-12 and was attached to the LX200 in place of the old.  Testing confirmed that it was working. It was noted that the handbox makes encouraging small beeps when initialisation has finished and again after the scope has parked (the old handset wasn't doing this or at least not recently).
  Replaced  2024-03-12  (LX200 Autostar II Handbox)
   
• Ambigous location of comet C/2021 F1 (Lemmon-PANSTARRS).  C/2021 F1 (Lemmon-PANSTARRS) although too dim to be see, was scheduled in plans for S1190 & S1191 sessions.  On both nights a starfield in Cancer was imaged, but during post-session analysis on the Development Computer the 'Title' description produced by AstroMain reported that the comet was passing through Octans (which is would only be visible from the Southern Hemisphere.  Investigating showed that TheSky virtual view on the Observatory Computer clearly shows the comet in Cancer whilst on the Development Computer it is clearly shown in Octans, this is a very significant and unexplainable difference.  No problem noticed with any other comets.  Downloading latest  'comets.cmt file from Internet & re-importing comets on both computers (on 2024-04-12) seemed to confirm that the current location of comet is indeed in Octans. Issue closed 2024-04-12.
  Closed 2024-02-26  (TheSky6)

Small Defects

• Dialog message showing the 'Autostart' time window has two time format errors.  When clicking Autostart a series of dialog seeking user confirmation appear. One of these Autostart's Window period contains a two time format errors   the start time has a missing  ":"  (colon) and the end time includes a space that shouldn't be present.(e.g. the window appears as  "1757 to 05: 07"  instead of "17:57 to 05:07"). 
  Fixed  2024-02-26  (AstroMain 3.65.20)
   
• Logitech Wireless Mouse associated with Development Computer stopped working (22:00).  Red/Block LogiTech Wireless Mouse associated with Development Computer seemed to stop working. Battery replacement didn't resolve it and an old wired mouse had Device dropouts and couldn't be used. Carried on using touchpad bad efficiency of work drops by 50% an causes frustration.   The following morning mouse examined in detail and showed that On/Off button on mouse was in the off position.  It must have positioned off in prcoess of trying to see why mouse with old battery had stopped working (The labelling on the switch is very small/hard to read).  Putting the switch to On and trying the mouse again showed it to be working.  Issue resolved.
  Resolved  2024-02-26  (Development Computer / Mouse, User Awareness)
   
• Attempt insert ToO target into plan from AstroPlan failing message "Target lies below 5 altitude. ToO submission is aborted." (01:00). Due to cloud during the planned imaging of 12P/Pons-Brooks in the early evening, it was decided to make a repeat attempt to image the comet at around 04:40 in the early morning when the comet had climbed again.   Current RA/Dec Coordinates were updated and an attempt was made to submit to the comet to night's plan with acquistion at/after 04:40 when it would be lying at alitude 14° .   It was surprising to then get the message "Target lies below 5 altitude. ToO submission is aborted.". At the time (01:00) the comet was lying in N sky with altitude 4° .  The ToO sumbission check should look at the altitude at 04:40 (the requested time) not the current altitude.    A separate continuous improvement ticket has be raised to add a 'Now' checkbox to the ToO sumbission Form that can control the time that the ToO Az/Alt Plot is displayed for.  Fixed in AstroPlan 1.39.8 but requires Target Coordinates to be updated on main form and saved.
  Fixed 2024-02-26  (AstroPlan 1.39.8)
   
• Shutter Battery Red Alert inappropriately raised with message "Shutter battery level has fallen below 85% " (post-session 05:15) .   Following a short power outage at 06:14 firstly a yellow alert was raised at 06:15:08 with message "Shutter battery level has fallen below 88%" followed by red alert at 06:15:10 with message "Shutter battery level has fallen below 88%".  These were raised because the volatile records in the Pulsar ASCOM Log were indicating that battery voltage / battery level / temperature / amperage were all 0  during the 31s period 06:14:46  to 06:15:17.   Alerts should be raised in battery level is 0 as this represents a different issue/alert and not an intrinsic issue with the Dome's Shutter Battery Level.
  Fixed  2024-02-26  (AstroMain 3.65.21)
   
• ObsViewer/ObsPic shows numeric values associated with Focuser1  on 'OTA T.'  when Focuser1 is frozen/not connected (06:15).   When the Focuser1 comms are offline because the driver is stalled or the Focuser1 is powered off,  the Focuser steps in the 'Focuser1' field and the Tube Tempearture in 'OTA T.' continue showing numerics values instead of reflecting vcNull values shown by the text "--" . Believed to be fixed in AstroMain 3.66 or sub version. Closed after review 2024-03-20.
  Closed after review 2024-03-20  (AstroMain 3.66)

Continuous Improvement

• AstroMove's 'Copy WS, CS Files' From Observatory routine should also copy the 'CloudSensor_Data.csv' file.  The 'CloudSensor_Data.csv' file contains CloudSensor data records with a 5s frequency which surpasses that of the 'CloudSensor_Data-yyyy-MM.csv' file which has data records with only a 60s frequency. The former more detailed file is useful for investigating specific issues associated with CloudSensor data & its Relay to Dome.
  Done 2024-02-26  (AstroMove 1.12.11)
   
• Add a 'Now' checkbox to AstroPlan's ToO Submission Form that can control the time that the ToO Az/Alt Plot is displayed for.   Now (checked) should always be the default  and the At/Before time fields should be hidden. When unchecked the 'At/Before' Time fields should be revealed. When the At/Before time is changed the graph should be updated based on the new time. Basic functionality added into AstroPlan 1.39.8.  Should additional work is still require with regard to comets & updating Ra/Dec Coords and using them, when Az/Alt chart is refreshed.  
  Done 2024-02-26  (AstroPlan 1.398 )
   
• AstroWeather to automatically restart CloudSensor when it appears to have stopped refreshing data.  A small power outage at 06:14 kocked out the cloud sensor and stopping the writing of new datar records to CloudSensor_Data file(s) and stopped flow of fresh data to AstroWeather (and on AstroMain) until the CloudSensor program was manually restarted at 11:29.  AstroWeather already recognises that cloud sensor data has recently freshed, and it is proposed to extend AstroWeather facility to automatically restart CloudSensor program if there cloud sensor data has been recently refreshed and power supply is on.  This is effectively a duplicate of a conntinuous improvement item previously defined after session S1187 (S024-02-20). Implemented in AstroWeather 1.23.12 by adding new variables bRestartingCloudSensor(Boolean) & LastCloudSensorRestartTime( Date), modifying  DisplayCloudSensorRecord() 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)
   
• Extend AstroMain to log power outages in more detail and with greater accuracy. During short Power Outage at 06:14 the ObsConsole reported a Power Outage alert with message " Outage (1) Detected" however there is no information on when this occurred to nearest 1s/5s nor when power returned. There is no information about alert / outage in the log. This needs be logged for use during later analysis in the event of an incident or follow-up investigation.  Implemented in AstroMain 3.66.  PowerMonitoring and associated raised of events and reporting is moved into a new PowerMonitor thread that executes a RunPowerMontor() routine, which monitors the power state every 0.2s or so (for more details see here ).
  Done 2024-02-29 (AstroMain 3.66 , Power Supply)
   
• Commence an investigation to summarise the various effects and findings associated with small power outage that affected the observatory at 06:14.
  A web section has been kicked off below (see Investigation - Effects of Short Power Outage (06:14) and information already collected under the major/minor issues above with be transferred.
  Done 2024-02-27 (Observatory, Power Outage, Web Notes)
   
• Add small button to Fits Summary to move the Visible Cells back over to left hand side. When working with data cells on the right hand side of the Fits Summary Excel worksheet the important  'Procedures' button at top of columns I to L becomes hidden.  Whilst scroll button can be used to move back to the left hand side to reveal the key button it would be useful to have a smal button that could be clicked to immediately move to the left hand side of the spreadsheet. Test buttons  'Scroll Left' & 'Far Left' assigned to 'ScrollToFarLeft() macro have been added to 01192_FitsSummary.xls. The command to scroll to far left of spreadsheet is
    ActiveWindow.ScrollColumn = 7
  Implemented in master FitsSummary on 2024-02-29.
  Done 2024-02-29  (Excel Fits Summary)
   
• Look into solutions that workaround the issue of short power outages to the Observatory.  After the S1192 session there was a small power outage to the Observatory which caused the TCF-S Focuser, the Cloud Sensor and Zigbee WebSocket to stop .   An review should be made that looks at potential solutions to stop this issue was effecting the Observatory  (e.g backup power) and also looks at potential means to automatically recover from the problems caused by such an outage. See  Review - Increasing observatory & session resistance to small power outages, 2023-02-27 ).  A new separate MonitorPower thread has been introduced to AstroMain 3.66 which provides better monitoring and reporting of Laptop/Observatory Power Status.  Improvements made in early Mar 2024 including the installation of UPS system that protects the Telescope, TCF-S focuser, Sbig Camera & Zigbee/ Combee II.   Software solutions have also been implemented for the CloudSensor.
   Done 2024-03-03 (Observatory, Power Supply, AstroMain 3.66)
    
• AstroMain to automatically restart TCF-Service when it appears to have stopped or otherwise stalled.  A small power outage at 06:14 kocked out the TCF-S Service and prevented access to TCF-S data, in particular Focuser Position & OTA Tube Temperature,  and prevent focus movement if required.  Service should be restarted provided that A/C Power is on, indicated by Laptop being an A/C Supply rather than Battery Supply.  Existing routines involved in restarting the TCF-S Service are RestartTcfFocuserByThread(Mode) & RestartTcfFocuser(Mode).  Executing operation is indicated by bRestartingTcfsFocuser flag. New variable LastTcfServiceRestart(date).  A preliminary implementation has been added to AstroMain 3.65.22.   New version has been tested on Observatory Computer but it is unclear if it covers the complete range of possible scenairos affecting the TCF-S Focuser, nor is yet assured that the new routines don't have an unwanted sideeffect or achilles heel.
   In Progress  2024-02-28+  (AstroMain 3.65.22+ / AstroMain 3.66)
   
• Contact Pulsar Observatories regarding behaviour of Relay value=2 and the recent incident where Shutter didn't close as expected.   Also contact them regarding the issue that occured during S1197 Session (2024-03-13 22:35) when the dome's setting were somehow all reset following a power outage (part of a series of power outage system tests )
  To do 2024-02-26+  (Pulsar Dome / Pulsar Observatories)

[ Prev | Next ]

Fig 1.   Sequence of ObsPic covering the peroid when there was a power cut (~ 06:14:50)

a) 06:14:30 - Status immediately before outage

 
b) 06:15:07- Immediately after outage (No Pulsar Dome, No LAN / No Laptop 7 communication, No UPB Box.  No UPB Switch Info (No Scope, No Dew Heaters, No Focuser 2).  Focuser1 might be showing a frozen state rather than error/issue.


c) 06:15:38 - During Recovery, UPB Switch is Back (Telescope, DewHeaters)  LAN & Laptop7 communication are still down

 
d)  06:16:09 - Post Event  (LAN  & Laptop 7 communication are back, Cloud Sensor data is frozen and doesn't come back until manually restarted at 11.29.

 
e) 06:16:39 - Post Event  CloudSensor data & TCF-S data (Focuser1 & OTA T.) are both frozen and don't come back until services are manually restarted at 11:29.

Back to Top

Post Session

Investigation - Effects of Short Power Outage (06:14)

Issue

• Power to Observatory was lost for up to 30s at 2024-02-26 06:14 (just after the S1192 Session had finished
   
• Serveral elements of the Observatory were affected by the outage & the lack of automated recovery
   
• Small power cuts can knock-out a number of elements of the Observatory system which can cause loss of monitoring and equipment operation, which then remain not working, even when power is restored,  until the particular element(s) are manually restored.
   

Description

Observatory was running in General Mode and so the Telescope was not running, having been parked earlier (00:51) & powered down (05:52). The CCD Camera was running but had been disconnected earlier at 05:52.   Dome, TCF-Focuser, UPB Power Box & deCONZ/Zigbee were still connected. It was still morning twilight so AstroAllSky was still in its night mode & capturing AllSky Images.

The observed effects on different elements of the Observatory are summarised in the table below:

Observatory Element	Likely Effect & Observations		Recovery	Impact
Cloud Sensor	- Power to USB Hub linking to CloudSensor Head would have been lost , affect comms - CloudSensor program affected & stopped refreshing data files at 06:14. - AstroWeather shows red flag against CloudSensor with last refresh time of 06:14.  - AstroMain shows red flag against CloudSensor with last refresh time of 06:14.		Manual Restart required	HIGH
Telescope	- Telescope wasn't powered & operational at this time, so no observations in this case (but if it was in operation, it would have likely produced driver exceptions and lock up TheSky6 Telescope. The scope would have powered down in an 'Unparked' state, causing the scope to be at wrong position when the scope was next restarted, requiring significant recovery steps by the user)		n/a	(HIGH)
UPB Powerbox	- Power to box and connected devices (TCF-Focuser  & Telescope n/a) stopped - PDB Switch Service stopped working in AstroMain - AstroMain reports "Unexpected disconnection of UPB.Switch (06:14)" and "RestartSwitch appears to be frozen (06:15) " - AstroMain / ObOverseer Submits job to Restart UPB Software (06:15) - AstroMain responded by xxxxx		Part Recovered by AstroMain.	HIGH  -
TCF-Focuser	TCF-Focuser Service failed in AstroMain		Manual Restart required	HIGH
Zigbee Network	- deCONZ WebSocket facility stopped working prevented an light/sensor events from reaching AstroMain Zigbee system		Manual Restart required	HIGH
AllSky Camera	- Raw Pictures stopped (last image ...676  (‏‎06:14:18 to 06:14:48) - AstroAllSky repeatedly processed ...677 frame every 30s from 06:15 to 07:00 (which  explains why Sun Alt value on Annotated Pictures 'jumps from -8.4°.in ...676.jpg to -5.9° in ...677.jpg).  and why .677.jpg was produced at 06:32 & 18 mins after ...676.jpg - Raw Pictures resumed at 07:01:24 (image ...770  to ... 073..,  no raw images saved for ...678 to ...769.		Recovered itself eventually	MEDIUM
LAN	- Ethernet Switch in Observatory likely powered down (and then powered up again) - Ethernet over Powerline would have stopped (and likely resumed again) - ObsPics show that connection with LAN and to AllSky/Weather Computer (LAPTOP7) dropped out at around 06:14:30 to 06:15:07 and then came back at some point between 06:15:38 & 06:16:19.  - ObsEnv file on AllSky Weather Computer show normal record at 06:14:20, record at 06:15:01 was 11s late and has signs of null values, possible missed record at 06:15:30, record at 06:15:53 has additional null fields.		Recovered itself Ok	LOW
SBIG Camera	- SBIG Camera would have powered down (and then powered up again) - CCDSoft Camera was connected to SBIG Camera at the time, so no observations in this case		UNKN	UNKN
Web Upload	- Web Upload largely unaffected. AstroPlan seems to be have uploaded files as late as 06:14:49 before the outage and as earier as 06:15:08 after the outage		Recovered itself OK	LOW
Weather Station	- Weather Station / Virtual VWS essentially unaffected by outage.  - Possible lost data during the outage itself ?		None required	NONE

Analysis

Conclusion.

 

Actions

•   Carry out a review to look at increasing observatory & session resistance to small power outage
   In progress  see Review - Increasing observatory & session resistance to small power outages, 2023-02-27.

Back to Top