David's Astronomy Pages
Notes - Session 1193 (2024-02-26)

 
Bullet Session Aims & Highlights
 - Observing Result
 - Night Summary Plot
 - Session Event Log
Bullet Operational Issues
  - Critical Issues (0),  Major Issues (1),  Minor Issues (1),  Small Defects (0),  Continuous Improvement (4)
 
Bullet Images from 2024-02-26 >>         
   
Bullet Investigation - Targets from Planned Target 4/36 onwards failing due to Slew Error
   
   

Session Aims & Highlights (2024-02-26)

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. 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

Highlights

Notes:

Summary Plots & Logs

Observing Plan
Image
  
Observing Result
Image
   
Image
 
Dome & Scope Slewing Performance
Image
  
Slew/Centering Performance
Image
  
Guiding Performance
Image
  
Sky Conditions (Locate Frames)
Image 
  
Night Sky Summary Plot
Top axis: Sky Brightness at Zenith (in ADU/s)
Lefthand axis: Local Time (hh LT). Righthand axis: Sun Altitude (degs)
Image   
  
Actual Weather vs Pre-Session Weather Forecast
Image
Image
  
Session Event Log
Time     Event Detail
18:32:04 Session Monitoring AutoStart monitoring for Live Session opportunity between 18:32 & 05:04
18:32:07   AutoStart Delayed Session delayed due to too few stars
18:36:18 Session AutoStarting Session autostarting (18:36)
18:36:28   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.)
18:36:53   Camera1 Connected SBIG Camera connected (Set point -20°C)
18:36:56 Session Created Session Created (Live, 2024-02-26 S01193, ImageSaveNum: 1193001)
18:37:00   Scope Switched On Telescope Power has been switched on via UPB Powerbox.
18:38:46   Services Started Observatory Services started
18:38:53 Observatory (Auto) Observatory placed in Fully-Automated Mode
18:38:55 Session Pending Session pending (2024-02-26)
18:38:57 Session Initiating Session initiating (2024-02-26)
18:38:59   Plan Requested Observing Plan requested from AstroPlan (1.39.7)
18:40:25   Plan Loaded Observing Plan loaded to queue (Plan ID: 967)
18:40:40   Camera1 Connected SBIG Camera connected (Set point -25°C)
18:41:15   Telescope Connected Telescope connected (TheSky6)
18:41:39 Session Equilibration Session ready to Open Dome
18:42:24   Dome Opened Dome opened (Opening time 45s, Zigbee 41s)
18:42:27 Session Running Session running
18:42:29   Queue Started Observing Queue started (36 targets selected)
18:42:31     Target Started (NrZen) Target started (Focus Field 5, HIP 23569)
18:42:45       Dome Unparked Dome unparked
18:47:11       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-S)
18:47:13       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap)
18:49:17       Focusing Completed Foc2 AutoFocus Completed (Profile No 1, wide)
18:51:03       Focusing Completed Foc2 AutoFocus Completed (Profile No 1)
18:51:20     Target Completed (NrZen) Target completed (Focus Field 5, HIP 23569)
18:55:25     Target Started (1/36) Target started (1/36, NGC 1051)
19:01:37       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S)
19:17:49     Target Completed Target completed (1/36, NGC 1051)
19:17:53     Target Started (2/36) Target started (2/36, 12P/Pons-Brooks)
19:21:41       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S)
19:33:24     Target Completed Target completed (2/36, 12P/Pons-Brooks)
19:35:47     Target Started (3/36) Target started (3/36, UGC 831 w/AT2023wdd)
19:38:48       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-S)
19:49:26   Observatory Door Observatory Door has opened
19:49:29   Observatory Door Observatory Door has closed (open time 3s)
19:51:53   Observatory Door Observatory Door has opened
19:52:04   Observatory Door Observatory Door has closed (open time 11s)
19:54:47     Target Completed Target completed (3/36, UGC 831 w/AT2023wdd)
19:58:07     Target Started (4/36) Target started (4/36, 13P/Olbers)
19:58:43     Target Failed (4/36) Target failed due to slew error (4/36, 13P/Olbers)
20:15:57     Target Started (5/36) Target started (5/36, UGC 3174 w/SN2023mut)
20:16:30     Target Failed (5/36) Target failed due to slew error (5/36, UGC 3174 w/SN2023mut)
20:37:57     Target Started (6/36) Target started (6/36, 103P/Hartley)
20:38:35     Target Failed (6/36) Target failed due to slew error (6/36, 103P/Hartley)
20:54:41     Target Started (7/36) Target started (7/36, CGCG 119-104 w/SN2024cdi)
20:55:14     Target Failed (7/36) Target failed due to slew error (7/36, CGCG 119-104 w/SN2024cdi)
21:17:01     Target Started (8/36) Target started (8/36, NGC 3206 w/SN2024bch)
21:17:47     Target Failed (8/36) Target failed due to slew error (8/36, NGC 3206 w/SN2024bch)
21:27:04       SoftSuspend Called Soft Suspend is called due to Deteriorating Conditions (too few stars)
21:27:07   Queue Paused Observing Queue pausing for Session Suspension
21:27:10 Session Suspending Session suspending
21:28:00   Dome Closed Dome closed (Closing time 50s, Zigbee 43s)
21:28:02 Session Suspended Session suspended
21:59:40     Target Cancelled Target cancelled (9/36, Nova Cas 2021 (Nova)) due to cloud
22:15:41     Target Cancelled Target cancelled (10/36, AT2023srv (CV)) due to cloud
22:28:00     Target Cancelled Target cancelled (11/36, AT2022zkn (CV)) due to cloud
22:48:20     Target Cancelled Target cancelled (12/36, NGC 3690 w/SN2023wrk) due to cloud
23:02:20     Target Cancelled Target cancelled (13/36, AT2023srw (CV)) due to cloud
23:19:52     Target Cancelled Target cancelled (14/36, 62P/Tsuchinshan) due to cloud
23:24:58 User Intervention User request to close and finish session
23:25:01   Queue Aborted Job Queue aborted
23:25:03 Session Closing Session closing
23:25:08   Dome Closed Dome already closed (closed at 21:28, closing time 50s, zigbee 43s)
23:25:26   Dome Parked Dome parked (parking time 10s), Az: 90.0 deg
23:26:49   Telescope Parked Telescope parked (parking time 79s)
23:27:05   Telescope State Handbox reads 'Scope parked Turn scope off.'
23:27:27   Telescope Switched Off Telescope Power has been switched off via UPB Switch.
23:28:49   Dome Charging Dome is parked and re-charging Ok (13mA)
23:28:51   Services Stopped Night Services stopped
23:28:54 Session Finishing Session Finishing started (Create Fits Summary, Transfer Files)
23:29:01     Dome (Find Park) Find Park started (Search Az 87.0 to 93.0°, Step 0.2°, Narrow)
23:30:34     Dome Find Park found (Best Park Az 90.2°)
23:30:41     Dome Dome has been synced at park position (Az 90.0°, Adjustment: -0.2°)
23:30:44   Dome Parked Dome parked
23:31:49   Dome Charging Dome is parked and re-charging Ok (15mA)
23:31:51 Session Finished Session Finished

 
Session Alerts & Alarms
Time     Type       Name Detail
23:31:49 Green Clear Dome Charging Dome is parked and re-charging Ok (15mA)
 

Back to Top


Operational Issues (2024-02-26 S1193)

[ Prev | Next ]

Critical Issues

Major Issues

Minor Issues

Small Defects

Continuous Improvement

[ Prev | Next ]


Fig 1.   Information/Error dialog produced in TheSky following ASCOM.Telescope exception

Image
 

Fig 2.   Near Zenith Focus Field  (3s, 3x3) & Initial Focus Frame (1.5s, 1x1)

The Intended Focus Star centered and identified in blue square.
Note: not initial out-of-focus stars)

Image
 
Image  

Focus Frame Step      Result | DRO  | FWHM | HFD | Temp | Max |
Taking 1s box (C) 1/1     Ok | 3969 | -    | -   | 1.0  | 0   |

Fig 3.  Graphs comparing Best Focus from S1192 (previous session) with S1194 (next session)

There is a jump in Focus Offset of +875 focus step between the near zenith focusing in S1194 and the focusing at end of S1192 session.
It would seem that this jump in focus must have largely happened between the end of the S1192 session (focused images) and the start of S1193 session (out of focus images).  This is second time recently that there was been a focus jump between sessions - so is it caused by mirror shift or is it an atmospheric change ?

Image
 

Image


Back to Top


Investigation - Targets from Planned Target 4/36 onwards failing due to Slew Error

Issue

Targets from Planned Target 4/36 onwards failing due to Slew Error (19:58). 

Description

Targets beginning with Target 4/36 (13P/Olbers)  at 19:58, and continuing with the next 4 targets (5/36 to 8/36) until session suspension due to cloud at 21:27, all with the reported error 'Slew Error' and messages like "Scope isn't pointing to the target (Ang Sep. = 42.5 arc degs)"  & "Possible 'Timed out waiting for received data' problem" .

Analysis

Examination of the session's log file shows that for slew to Target 4/36 (13P/Olbers) at 19:58 with pre-Slew Scope Coords of Ra= 01 20 59.000 Dec=+39 18 46.00 & Target Coords of  RA= 03 03 58.521 Dec= +03 09 09.20, a normal Scope Path seems to have been delivered with a total movement of 44.5° (  60.6° direct ) resulting in PostSlew.Scope Coords of Ra= 03 03 58.000 Dec=+04 26 43.00 (the difference in Dec between target value and this post slew number is interpreted as just a TheSky6/TPoint vs Raw Scope difference). 

ObsCam and ObsPic pictures show the slew was made and to what seems the correct target location.  

The issue seems to be that in the post-slew check the post-slew coords are appearing as being identical to the pre-slew coords and suggest that the scope is a long way from the expected target coords .

19:58:43.39 | 13P/Olbers Report PreSlew.ScopeRaDec Data    | RA= 01 21 06.693 Dec= +38 34 34.67 | Epoch Current
19:58:43.39 | 13P/Olbers Report PostSlew.ScopeRaDec Data   | RA= 01 21 06.693 Dec= +38 34 34.67 | Epoch Current
19:58:43.39 | 13P/Olbers Report SlewDistance Data          | 0.000 arc deg (0 deg 0 min)
19:58:43.39 | 13P/Olbers Report Slew.Discrepancy Data      | 2,548.49' (W: -1,440.22', N: -2,125.42')
19:58:43.39 | 13P/Olbers Report Slew.Discrepancy Fail      | SLEWING discrepancy of AT LEAST 5'
19:58:43.41 | 13P/Olbers Finish Target Fail                | Target failed due to slew error

This is contrast to the Device Hub./Scope Path information which shows that the slew happened ok.  The DeviceHub log confirms that the correct Slew Request was sent (incidently this is request made via TheSky6 Telescope)

19:58:13.658   SlewToCoordinatesAsync:      RightAscension = 3.06599, Declination = 4.44562

Logs show a similar pattern for the other 4 targets, with the additional observation that they all record the same Pre Slew & Post Slew coords (RA= 01 21 06.693 Dec= +38 34 34.67) during the Post-Slew Check. 

 It is believed that the coordinates used in post-slew check are all derived from TheSky6.TelescopeRaDec calls and the 'frozen' coordinates indicate that TheSky's Telescope object is heldup / partially stalled.  Examining the Observatory Computer the following day showed that the TheSky6 presenting an error/information dialog associated with ASCOM.DeviceHub / Meade Generic Telescope with the message "CheckDotNetExceptions ASCOM.MeadeGeneric.Telescope Declination Get System.InvalidCastException: Conversion from string ":" to type 'Double' is not valid" .(See Fig 1).

The dialog was non-modal and didn't block access to TheSky and didn't prevent further slew calls being made but it did block access to fresh Telescope Coords via TheSky6.  The telescope, the Meade Generic driver and Device Hub clearly all continued working ok producing fresh Telescope Coords. 

DeviceHub logs show that the time of this exception occured at 19:51:11 based on the following anomalous line in one of the DeviceHub ASCOM logs from the session:

    19:51:11.104  Get Declination: (failed).

A visit to the observatory was made from 19:49 to 19:52  check & test the LX200's Autostar II hand controller, including using AstroMain's Virtual Handbox to test LCD Brightness Adjustement and a check on the action of the Controllers Directional Arrow buttons. This was during the main imaging for Target 3/36 (GC 831 w/AT2023wdd) and may or may not have led to the issue happening with Target 4/36 onwards.  

Logs record the use of the Virtual Handbox and the some not unexpected side-effects of the telescope movement directed by hand controller but there are no errors are recorded during the process.  The failure to Get Declination at 19:51:11 is around the time that virtual Handbox was being used, log shows :.

  19:50:40.47 | Handbox Read Handbox Info                    | Handbox Display : Adj. with arrowsThen press Enter
  19:51:04.65 | Handbox Send KeyToHandbox Info               | Sending 'enter' to AutoStar II Handbox
  19:51:08.84 | UGC 831 (Overseer) Check UserInterface Alert | UI is Pending (3s)
  19:51:10.28 | Handbox Read Handbox Info                    | Handbox Display : 28036:29
  19:51:17.48 | Handbox Send KeyToHandbox Info               | Sending 'mode' to AutoStar II Handbox
  19:51:17.77 | Handbox Read Handbox Info                    | Handbox Display : Select Item: Utilities
  19:51:19.42 | Handbox Send KeyToHandbox Info               | Sending 'mode' to AutoStar II Handbox
  19:51:19.68 | Handbox Read Handbox Info                    | Handbox Display : Select Item: Object

The handbox display 28036:29 at 19:51:10 is unexpected. The DeviceHub logs reports  Action Handbox, parameters readdisplay, returned 280[DF]36:29 (done) at this time  - the 280[DF]39:29 is a azimuth value.  I think this is the smoking gun that points to a conflict between messages to/from telescope at this time   

Conclusion

It is believed that that use of Virtual Handbox at this time resulted in a conflict that led to a bad Declination value / or exception being supplied and the resulting exception caused a hold-up in the TheSky6 Telescope objects  

The issue is explained and is closed after review 2024-02-27.  

Even though the dialog report ASCOM telescope exception ha been dismissed TheSky6 should neverthess be restarted before the next session as a precaution. 

The potential issues involved in manipulated the hand controller during live session must be remembered and safeguarded against better. It isn't possible to know that TheSky6 has put up an information/error dialog or to dismiss such dialogs from the AstroMain program, however that can be clues in times of inconsiencies between telescope coordinates from TheSky6 and those supplied directly from ASCOM.   

A separate continuous improvement ticket is raised to add an additional oversight function to AstroMain to spot the issue and try recovery the situation including restarting TheSky6, and informing other programs about the TheSky6 restart. 

Actions

Back to Top