David's Astronomy Pages
Notes - Session 1167 (2023-11-15)

 
Bullet Session Aims & Highlights
 - Observing Result
 - Night Summary Plot
 - Session Event Log
Bullet Operational Issues
  - Critical Issues (0),  Major Issues (3),  Minor Issues (0),  Small Defects (2),  Continuous Improvement (2)
Bullet Images from 2023-11-15 >>         
   
Bullet Pulsar Dome - Software Update (1.51 Firmware & ASCOM Driver 6.3.10)
   
Bullet AllSky Camera - Ventilation holes (attempt to cure dew problem)
   
Bullet Investigation - Target Circle mispositioned on real time JPG Pictures
   

Session Aims & Highlights (2023-11-15)

Main aims

  1. Targets.  Acquire images of a selection of variable stars, nearby stars, comets & deep sky targets as allowed by sky conditions.
  2. Detailed JPG Pictures.  Test that the newly updated ConvertFitsToJpg() routine to see that cropping around target object and/or host object and associated labelling is working correctly (AstroMain 3.64.6)
  3. AstroMain. Check that operations involving the newly renamed Session.Finishing State (formerl Session.Housekeeping State) is working correctly (AstroMain 3.64.6)
  4. Pulsar Driver. Check out how the newly installed Pulsar Software (Dome Firmware Version 1.51 and ASCOM 6.3.10) operates during a live session.
    This was particular important as an issue with Shutter Opening / Closing had already noted during earlier daytime & pre-session testing.

 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
16:27:32 Session Monitoring AutoStart monitoring for Live Session opportunity between 16:55 & 05:40
16:27:35   AutoStart Waiting AutoStart waiting till earliest start time at 16:55
17:11:11   AutoStart Delayed Session delayed due to cloud
17:24:17 Session AutoStarting Session autostarting (17:24)
17:24:28   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.)
17:24:41 Session Created Session Created (Live, 2023-11-15 S01167, ImageSaveNum: 1167001)
17:24:48   Scope Switched On Telescope Power has been switched on via UPB Powerbox.
17:26:37   Services Started Observatory Services started
17:26:44 Observatory (Auto) Observatory placed in Fully-Automated Mode
17:26:48 Session Pending Session pending (2023-11-15)
17:26:50 Session Initiating Session initiating (2023-11-15)
17:26:52   Plan Requested Observing Plan requested from AstroPlan (1.39)
17:28:08   Plan Loaded Observing Plan loaded to queue (Plan ID: 941)
17:28:33   Camera1 Connected SBIG Camera connected (Set point -20°C)
17:28:40   Telescope Connected Telescope connected (TheSky6)
17:29:04 Session Running Session running
17:29:06   Queue Started Observing Queue started (45 targets selected)
17:29:10     Target Started (NrZen) Target started (Focus Field 21, HIP 103850)
17:34:39       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
17:37:11       Focusing Completed Foc1 AutoFocus Completed (Profile No 1, wide)
17:39:07       Focusing Completed Foc1 AutoFocus Completed (Profile No 1)
17:39:09       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap)
17:41:01       Focusing Completed Foc2 AutoFocus Completed (Profile No 2, wide)
17:42:43       Focusing Completed Foc2 AutoFocus Completed (Profile No 2)
17:43:00     Target Completed (NrZen) Target completed (Focus Field 21, HIP 103850)
17:43:05     Target Started (1/45) Target started (1/45, NGC 6745 w/SN2023ucy)
17:46:09       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
17:48:15       Focusing Completed Foc1 AutoFocus Completed (Profile No 3)
18:04:26     Target Completed Target completed (1/45, NGC 6745 w/SN2023ucy)
18:04:40     Target Started (2/45) Target started (2/45, HIP 87937)
18:08:35       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
18:10:46       Focusing Completed Foc1 AutoFocus Completed (Profile No 4)
18:13:23     Target Completed Target completed (2/45, HIP 87937)
18:13:27     Target Started (3/45) Target started (3/45, AT2023tow)
18:17:21       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
18:19:32       Focusing Completed Foc1 AutoFocus Completed (Profile No 5)
18:35:19     Target Completed Target completed (3/45, AT2023tow)
18:35:23     Target Started (4/45) Target started (4/45, C/2023 H2 (Lemmon))
18:39:03       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
18:41:27       Focusing Completed Foc1 AutoFocus Completed (Profile No 6)
18:54:50     Target Completed Target completed (4/45, C/2023 H2 (Lemmon))
18:54:54     Target Started (5/45) Target started (5/45, 61 Cyg)
18:57:38       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
18:59:35       Focusing Completed Foc1 AutoFocus Completed (Profile No 7)
19:01:09     Target Completed Target completed (5/45, 61 Cyg)
19:01:54     Target Started (6/45) Target started (6/45, M101 w/SN2023ixf)
19:05:38       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S)
19:21:59     Target Completed Target completed (6/45, M101 w/SN2023ixf)
19:24:14     Target Started (7/45) Target started (7/45, 12P/Pons-Brooks)
19:27:39       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S)
19:39:12     Target Completed Target completed (7/45, 12P/Pons-Brooks)
19:42:16     Target Started (8/45) Target started (8/45, Vega)
19:45:24     Target Completed Target completed (8/45, Vega)
19:49:42     Target Started (9/45) Target started (9/45, GCVS RR Lyr)
19:52:34       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
19:54:41       Focusing Completed Foc1 AutoFocus Completed (Profile No 8)
20:03:05     Target Completed Target completed (9/45, GCVS RR Lyr)
20:04:25     Target Started (10/45) Target started (10/45, Vega)
20:07:43     Target Completed Target completed (10/45, Vega)
20:11:52     Target Started (11/45) Target started (11/45, AT2023tvi (CV))
20:14:53       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
20:16:51       Focusing Completed Foc1 AutoFocus Completed (Profile No 9)
20:22:50     Target Completed Target completed (11/45, AT2023tvi (CV))
20:23:52     Target Started (12/45) Target started (12/45, AT2023txn)
20:26:42       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
20:28:53       Focusing Completed Foc1 AutoFocus Completed (Profile No 10)
20:34:51     Target Completed Target completed (12/45, AT2023txn)
20:35:52     Target Started (13/45) Target started (13/45, C/2022 A2 (PANSTARRS))
20:40:12       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S)
20:46:15     Target Completed Target completed (13/45, C/2022 A2 (PANSTARRS))
20:48:12     Target Started (14/45) Target started (14/45, NGC 7620 w/SN2022zic)
20:51:11       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
20:53:36       Focusing Completed Foc1 AutoFocus Completed (Profile No 11)
21:09:29     Target Completed Target completed (14/45, NGC 7620 w/SN2022zic)
21:10:32     Target Started (15/45) Target started (15/45, AT2023ev (CV))
21:13:23   Observatory Door Observatory Door has opened
21:13:38       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
21:15:58       Focusing Completed Foc1 AutoFocus Completed (Profile No 12)
21:21:07   Observatory Door Observatory Door has closed (open time 7.7 min)
21:21:46     Target Completed Target completed (15/45, AT2023ev (CV))
21:22:32     Target Started (16/45) Target started (16/45, AT2023wba (CV))
21:26:15       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
21:28:42       Focusing Completed Foc1 AutoFocus Completed (Profile No 13)
21:34:30     Target Completed Target completed (16/45, AT2023wba (CV))
21:34:35     Target Started (17/45) Target started (17/45, GCVS HH And)
21:37:19       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
21:39:30       Focusing Completed Foc1 AutoFocus Completed (Profile No 14)
21:41:32     Target Completed Target completed (17/45, GCVS HH And)
21:42:59     Target Started (18/45) Target started (18/45, M33 w/Nova M33 2023-11a?)
21:46:10       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
21:48:35       Focusing Completed Foc1 AutoFocus Completed (Profile No 15)
22:06:38     Target Completed Target completed (18/45, M33 w/Nova M33 2023-11a?)
22:06:42     Target Started (19/45) Target started (19/45, AT2022adzf (CV))
22:09:47       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
22:11:58       Focusing Completed Foc1 AutoFocus Completed (Profile No 16)
22:17:59     Target Completed Target completed (19/45, AT2022adzf (CV))
22:18:03     Target Started (20/45) Target started (20/45, Nova Cas 2021)
22:21:19       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
22:23:23       Focusing Completed Foc1 AutoFocus Completed (Profile No 17)
22:35:00     Target Completed Target completed (20/45, Nova Cas 2021)
22:35:27     Target Started (21/45) Target started (21/45, AT2023jbs)
22:38:22       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
22:40:48       Focusing Completed Foc1 AutoFocus Completed (Profile No 18)
22:56:45     Target Completed Target completed (21/45, AT2023jbs)
22:57:27     Target Started (22/45) Target started (22/45, M31 w/AT2023gvz)
22:59:58       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
23:02:08       Focusing Completed Foc1 AutoFocus Completed (Profile No 19)
23:18:07     Target Completed Target completed (22/45, M31 w/AT2023gvz)
23:19:47     Target Started (23/45) Target started (23/45, AT2023rrr)
23:22:30       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
23:24:55       Focusing Completed Foc1 AutoFocus Completed (Profile No 20)
23:40:44     Target Completed Target completed (23/45, AT2023rrr)
23:41:47     Target Started (24/45) Target started (24/45, AT2023wvl (CV))
23:45:13       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
23:47:28       Focusing Completed Foc1 AutoFocus Completed (Profile No 21)
23:53:39     Target Completed Target completed (24/45, AT2023wvl (CV))
23:53:43     Target Started (25/45) Target started (25/45, NGC 7625 w/SN2023vyl)
23:57:24       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
23:59:30       Focusing Completed Foc1 AutoFocus Completed (Profile No 22)
00:15:19     Target Completed Target completed (25/45, NGC 7625 w/SN2023vyl)
00:15:47     Target Started (26/45) Target started (26/45, UGC 831 w/AT2023wdd)
00:18:58       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
00:21:25       Focusing Completed Foc1 AutoFocus Completed (Profile No 23)
00:37:12     Target Completed Target completed (26/45, UGC 831 w/AT2023wdd)
00:37:47     Target Started (27/45) Target started (27/45, AT2023wbv (CV))
00:40:45       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
00:42:56       Focusing Completed Foc1 AutoFocus Completed (Profile No 24)
00:48:43     Target Completed Target completed (27/45, AT2023wbv (CV))
00:49:47     Target Started (28/45) Target started (28/45, NGC 3893 w/AT2023uhx)
00:50:39       Dome Unparked Dome unparked
00:53:40       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
00:55:59       Focusing Completed Foc1 AutoFocus Completed (Profile No 25)
01:11:47     Target Completed Target completed (28/45, NGC 3893 w/AT2023uhx)
01:11:51     Target Started (29/45) Target started (29/45, GCVS BL Lac)
01:15:56       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
01:18:06       Focusing Completed Foc1 AutoFocus Completed (Profile No 26)
01:22:09     Target Completed Target completed (29/45, GCVS BL Lac)
01:22:13     Target Started (30/45) Target started (30/45, UGC 3174 w/SN2023mut)
01:26:19     Dome Slew Dome slew held up at Az. 270.7° (Delay 219s)
01:46:32     Target Completed Target partially completed (30/45, UGC 3174 w/SN2023mut)
01:46:36     Target Started (31/45) Target started (31/45, AT2023tjz)
01:50:11     Dome Slew Dome slew held up at Az. 222.4° (Delay 205s)
01:51:17 User Intervention User request to close and finish session
01:51:19     Target Failed (31/45) Target failed due to centering error (31/45, AT2023tjz)
01:51:21   Queue Aborted Job Queue aborted
01:51:24 Session Closing Session closing
01:52:53   Dome Closed Dome closed (closing time 85s)
01:52:59   Dome Park Aborted Dome Park aborted (0s, Az=222.4°)
01:54:16   Telescope Parked Telescope parked (parking time 72s)
01:54:31   Telescope State Handbox reads 'Scope parked Turn scope off.'
01:54:55   Telescope Switched Off Telescope Power has been switched off via UPB Switch.
01:56:20   Services Stopped Night Services stopped
01:56:23 Session Finishing Session Finishing started (Create Fits Summary, Transfer Files)
01:56:58 Session Finished Session Finished
 
 
Session Alerts & Alarms
Time     Type       Name Detail
23:19:54 Yellow Alert Anomalous Dome Slew Dome slew resumed at Az 239.9° (T+2.0s)
01:26:20 Red Alert Dome Slew Dome slew held up at Az. 270.7° (Delay 219s)
01:29:25 Yellow Alert Dome Discrepency Difference between Dome Az and Telescope Az is > 8 deg (UGC 3174)
01:29:27 Yellow Alert Dome Discrepency Difference between Dome Az and Slave Az is > 1 deg (UGC 3174)
01:29:29 Yellow Alert Dome Dome position has been static for more than 5 mins
01:47:42 Yellow Alert Anomalous Dome Slew Dome slew resumed at Az 222.4° (T+60.1s)
01:48:02 Yellow Alert Anomalous Dome Slew Dome slew resumed at Az 222.4° (T+80.3s)
01:48:22 Yellow Alert Anomalous Dome Slew Dome slew resumed at Az 222.4° (T+100.4s)
01:48:43 Yellow Alert Anomalous Dome Slew Dome slew resumed at Az 222.4° (T+120.5s)
01:49:03 Yellow Alert Anomalous Dome Slew Dome slew resumed at Az 222.4° (T+140.7s)
01:49:23 Yellow Alert Anomalous Dome Slew Dome slew resumed at Az 222.4° (T+161.0s)
01:49:43 Yellow Alert Anomalous Dome Slew Dome slew resumed at Az 222.4° (T+181.0s)
01:50:03 Yellow Alert Anomalous Dome Slew Dome slew resumed at Az 222.4° (T+201.2s)
01:50:11 Red Alert Dome Slew Dome slew held up at Az. 222.4° (Delay 205s)
01:50:48 Yellow Alert Dome Discrepency Difference between Dome Az and Telescope Az is > 8 deg (AT2023tjz)
01:50:50 Yellow Alert Dome Discrepency Difference between Dome Az and Slave Az is > 1 deg (AT2023tjz)
01:50:52 Red Alert Dome Dome position has been static for more than 10 mins
01:52:59 Red Alert Dome Failed To Park Dome at Az 222.4°
 
 

Back to Top


Operational Issues (2023-11-15, S1167)

[ Prev | Next ]

Critical Issues

Major Issues

Minor Issues

Small Defects

Continuous Improvement

[ Prev | Next ]

Back to Top


Pulsar Dome - Software Update (Firmware 1.51 & ASCOM Driver 6.3.10)

Update 2023-11-16

At the end of session S1167, the dome closing operation was also anomalous with the shutter taking 44s to physically close, but with ShutterStatus remaining in the 'Closing' state for 85s (ie for 41s after the shutter was actually closed).

A test was made the following morning (2023-11-16) in which the shutter was opened and closed   directly from the Pulsar Client Program (so no DeviceHub / ASCOM involvement). Results were similar for both opening and closing tests and the cases the previous day. The Shutter took 41s and 44s to physically open & close respectively, but the Pulsar Client showed the shutter state to be 'Shutter opening' and 'Shutter closing' for some 90-120s range.

This would seem to point to the problem being with the new 1.51 firmware, or a comms incompatibility between the new Dome firmware (1.51) and the Shutter firmware (1.25).

SlewToAzimuth 190 (Test at 13:31)
Logs from yesterday's Slewing Tests were examined today

Device Hub activity logs records SlewToAzimuth 190 request at 13:31:27. Because slewing doesn't immediately become true, and the property returns False  DeviceHub thinks the SlewToAzimuth has been achieved, and changes polling to standard rate. I pick this up as an anomalous slew and I can see parts of the ASCOM Dome Compliance run are not completed.    Only at 5s after the request does DeviceHub pick up that the Dome is slewing.  (Early time Az changes are lost to my client program, Az is seen to suddenly jump from Az 110 to Az 119.8). 

13:31:22.439: Dome - Statuses: Get Azimuth: 110   (Starting Az: 110)
13:31:22.439: Dome - Statuses: Get Slewing: False
13:31:27.047: Dome - Commands: SlewToAzimuth (190.00000°): (slew started)
13:31:27.049: Dome - Statuses: Get Slewing: False (this should immediately go to True but doesn't
13:31:27.049: Dome - Statuses: Get Azimuth: 110
13:31:27.049: Dome - Statuses: Get Slewing: False
13:31:27.049: Dome - Commands: Started fast polling every 1000 ms.
13:31:27.049: Dome - Statuses: Get Azimuth: 110
13:31:27.050: Dome - Statuses: Get Slewing: False (slewing still returning as False)
13:31:27.050: Dome - Commands: Returning to normal polling every 5000 ms.
13:31:32.064: Dome - Statuses: Get Azimuth: 119.8 
13:31:32.065: Dome - Statuses: Get Slewing: True  (Slewing only recognised as True, 5s after Slew request)
13:31:33.065: Dome - Statuses: Get Azimuth: 121.9 
13:31:33.065: Dome - Statuses: Get Slewing: True
13:31:34.060: Dome - Statuses: Get Azimuth: 124.3
13:31:34.060: Dome - Statuses: Get Slewing: True
 Immediate Messages  (Slewing = True, Azimuth gradually increasing)
13:32:04.090: Dome - Statuses: Get Azimuth: 188.9
13:32:04.090: Dome - Statuses: Get Slewing: True
13:32:05.090: Dome - Statuses: Get Azimuth: 189.8
13:32:05.090: Dome - Statuses: Get Slewing: True
13:32:06.090: Dome - Statuses: Get Azimuth: 190    (Destination Az: 190 )
13:32:06.091: Dome - Statuses: Get Slewing: False  (Slewing Stopped)
13:32:07.104: Dome - Statuses: Get Azimuth: 190
13:32:07.105: Dome - Statuses: Get Slewing: False

Pulsar Log records SlewToAzimuth request at 13:31:27

13:31:21.643 Volatile 110.0 0 0.000000 0.0 0 1 940 14907 -2 1 8500 2422 0 0
13:31:22.439 Azimuth Get Azimuth = 110
13:31:22.439 Slewing Get True      (Slewing state in log is completely reliable as it is always reported as True here though Dome is not slewing)
13:31:22.666 Volatile 110.0 0 0.000000 0.0 0 1 940 14907 -2 1 8500 2422 0 0
13:31:23.674 Volatile 110.0 0 0.000000 0.0 0 1 940 14907 -2 1 8500 2422 0 0
13:31:24.697 Volatile 110.0 0 0.000000 0.0 0 1 940 14907 -2 1 8500 2422 0 0
13:31:25.705 Volatile 110.0 0 0.000000 0.0 0 1 940 14907 -2 1 8500 2422 0 0
13:31:26.729 Volatile 110.0 0 0.000000 0.0 0 1 940 14907 -2 1 8500 2422 0 0
13:31:27.030 SlewToAzimuth Start 190   (SlewToAzimuth request received)
13:31:27.030 CommandString TX GO 190
13:31:27.047 CommandString RX A
13:31:27.047 SlewToAzimuth Request sent
13:31:27.049 Azimuth Get Azimuth = 110 (Dome hasn't physically / measurable started to move but Client expects to see Slewing=True at this point)
13:31:27.049 Slewing Get True          (Client is sent False at this point though reported as True in this Pulsar Log)
13:31:27.049 Azimuth Get Azimuth = 110
13:31:27.049 Slewing Get True          (Client is sent False at this point though reported as True in this Pulsar Log)
13:31:27.049 Azimuth Get Azimuth = 110
13:31:27.050 Slewing Get True          (Client is sent False at this point though reported as True in this Pulsar Log)
13:31:27.049 Azimuth Get Azimuth = 110
13:31:27.049 Slewing Get True          (Client is sent False at this point though reported as True in this Pulsar Log)
13:31:27.050 Slewing Get True          (Slewing state in log is unreliable as it is always reported as True even when Dome is definately not slewing)
13:31:27.704 CommandString RX 110.9 1 0.000000 190.0 1 1 940 14907 -2 60 8500 2422 0 0    (Dome is moving at this point)
13:31:27.927 Volatile 110.9 1 0.000000 190.0 1 1 940 14907 -2 60 8500 2422 0 0
13:31:28.936 Volatile 113.3 1 0.000000 190.0 1 1 940 14907 -2 227 8500 2422 0 0
13:31:29.911 Volatile 115.6 1 0.000000 190.0 1 1 940 14907 -2 390 8500 2422 0 0    (Early Time Az changes not available to end Client)
13:31:30.871 Volatile 117.6 1 0.000000 190.0 1 1 940 14907 -2 531 8500 2422 0 0
13:31:31.846 Volatile 119.8 1 0.000000 190.0 1 1 940 14907 -2 687 8500 2422 0 0
13:31:32.064 Azimuth Get Azimuth = 119.8
13:31:32.065 Slewing Get False    (Log reports Slewing False even though Dome is Slewing and the Client is sent Slewing=True)
13:31:32.838 Volatile 121.9 1 0.000000 190.0 1 1 940 14907 -2 830 8500 2422 0 0
13:31:33.065 Azimuth Get Azimuth = 121.9
13:31:33.065 Slewing Get False    (Log reports Slewing False even though Dome is Slewing and the Client is sent Slewing=True)
13:31:33.814 CommandString RX 124.3 1 0.000000 190.0 1 1 940 14907 -2 999 8500 2422 0 0


ASCOM Driver 6.3.10

A comparison between new ASCOM Driver 6.3.10 and previous 6.3.x version.

  Required ASCOM Behaviour Previous Version (6.3.x), 2021   Version 6.3.10, 2023 Notes
1) Dome.Slewing property should be True if any part of the
dome is currently moving or False if no part is currently moving
Slewing stayed False when Shutter was
Opening or Closing
  Slewing now correctly becomes True
when the Shutter is Opening or Closing
Confirmed fixed.
2) Dome.Slewing property should become True immediately
upon receiving SlewToAzimuth, OpenShutter or CloseShutter
       
           
  Things associated with the Pulsar ASCOM log        
3) Logfile should report the full version details Log reports : DriverInfo Get     
Pulsar Observatories Dome Drive Version: 6.3

(spelling: Drive should be Driver)
  Log reports : DriverInfo Get     
Pulsar Observatories Dome Drive Version: 6.3

(spelling: Drive should be Driver)
Still an issue.
I'd expect to see Version 6.3.10
for the current driver 
(this may be an ASCOM limitation ?)
4) Logfile should report the same Slewing state that it is sending to the Client Log reports Slewing False when Dome is Slewing and reports Slewing True when the Dome is not slewing (even though correct values are sent to client)   Log reports Slewing True when Dome is Slewing and reports Slewing True when the Dome is not slewing (even though correct values are sent to client at all times) Issue partly fixed but still a half-defect

Update 2024-01-05
A new version of Pulsar Software and new version of ASCOM driver were supplied by Pulsar Observatories and installed onto the Observatory Computer today (2024-01-05).  (See Pulsar Dome - Software Update (Firmware 1.52 & ASCOM Driver 6.4), 2024-01-05 )

Back to Top


AllSky Camera - Ventilation holes (attempt to cure dew problem)

Condensation & dew inside the Observatory's AllSky Camera's Hemisphere has been an outgoing issue in past 2-3 years and a source of much frustration, sometimes degrading the quality of Aurora Imaging/Monitoring and/or leading to the unreliablity in the AllSky Star Count provided to the Observatory Control Program undertaking automated observing/imaging.

After re-reading a 2019 conversation about "Oculus All Sky Camera and Dome - Condensation Problem" on the Stargazers Lounge forum (https://stargazerslounge.com/topic/325447-oculus-all-sky-camera-and-dome-condensation-problem/) it was noticed that a follow-up post from PhotoGav covered a 'solution' that had been supplied to him by Terry (Platt) of Starlight Xpress.  

Original post from PhotoGav,  2018-11-11

"As you can clearly see from this image, I have a condensation problem inside the dome of my Oculus All Sky Camera. After a particularly rainy period it invariably has condensation inside the acrylic dome. I cleaned the inside of the dome only two days ago, it poured yesterday and overnight and now I have condensation. I have the internal dew heater on a timer to come on at nighttime only every night. The camera lens is fine. The dome is not fine! It does evaporate eventually, but takes quite a while and obscures a clear view for the start of a night and beyond."

Later post/reply from PhotoGav, 2019-02-08

"I thought I would update this thread as I am delighted to report a successful solution has been supplied by Starlight Xpress. Terry at SX was very helpful and after discussion and various failed experiments he sent me a new base plate that has two 1 cm holes drilled in it. I swapped out the base plate and for once I was happy that it rained. The good news is that the dome no longer mists up inside. I’ve run it for the last few nights and it continues to work perfectly. So, ventilation was indeed the issue. .." .   

PhotoGav's issue sounds very similar to the issue I experience with my own Oculus AllSky Camera and the mention of a solution provided by Starlight Xpress (the makers of the Oculus AllSky Camera) suggests this is something I should probably consider myself.

So today (2023-11-15) I decided to bit the bullet and have a go at implementing the same fix to my Observatory's Oculus Camera, and drilled two 1cm diameter holes in the base plate of the camera to increase ventilation in the manner described by PhotoGav's posting.

Secondary aims for bringing the camera down from its mounting was to see if there was an way of retrofitting a small computer fan inside the casing to further increase ventilation and to also check the camera's dew heating system. As it turned out things didn't go completely to plan, but the two 1 cm diameter did get drilled and the camera has been returned to its mounting again.

AllSky Camera with internal dew - Side View
Camera lens is clear of condensation,
problem is the camera's dome/hemisphere
  AllSky Camera with internal dew - Top View
Adjacent to AllSky Camera is
the Observatory's CloudSensor
Image   Image
       
Hemisphere/Dome after wiping dry
 but before screwing back its retainer
Vent holes inside dome around fish-eye lens,
small drain holes outside of dome,
white powder inside dome is to kill earwigs which
somehow find their way into the camera
  Existing Base Plate of Camera
View from below
Image   Image
       
Existing Base Plate of Camera 
(camera removed from its mounting)
  Failed attempt to unscrew the two retaining bolts
Both bolts were completely stuck and both snapped off
when applying force making the base plate unremovable
Image   Image
       
Bottom Plate after drilling two 1cm diameter holes
Being unable to remove the base plate, two pilot holes were drilled first
to check there wasn't anything important behind the plater
  AllSky Camera re-attached to its mount
View from below
showing the two new ventilation holes
Image   Image
       



An update will be added later to with information about whether these ventilation holes improve the condensation/dew issue or not.

There is a slight concern that the two new holes provide an easy route for more critters to enter the camera/dome. On the other hand it might allow adult earwigs (which originally entered the camera as small young earwigs) a way of getting out instead of clambering all over the fish eye lens as they sometimes have.  

The sheared bolts unfortunately mean there is no way to get into the camera body (unless the broken bolt ends are drilled out). This prevented an examination as to whether the addition of a computer fan in future was a feasible retrofit.

There is one school of thought that says there should be a gap around the bottom edges of the hemisphere/dome to allow ventilation but in my case I suspect that original small patches of velcro to allow this have worn away or lost over the years (only one partial section remains). This might explain why the condensation/dewing seems to have been worse in the last 2-3 years than during the first few years of using the camera.

Supply of 12v power to the AllSky Camera's dew heater was checked at the socket end using a desk-lamp temporarily plugged into the Zigbee Smart Plug that is used for controlling the dew heater and turned on/off using Zigbee, and at the plug end using a voltmeter which indicated 12-13v.  Of concern is that during visits to the Camera to wipe hemisphere dry, I have being having any sensation of warmth around the top of the camera. Last time I remember feeling it warm was back in the spring. Have the dew heaters failed ?

Back to Top


Investigation - Target Circle mispositioned on real time JPG Pictures

Issue:  Target Circle for BL Lac is mis-positioned on JPG Pictures (S1167, 01:19)

Description
Target Circle for BL Lac is mispositioned on  Main Frame JPG pictures (but correct on Locate and Focus Pictures).  The circle is mispositioned by around 35".  In other sessions BL Lac target circle has been correctly drawn.  Replaying the target in AstroMain On-the-Fly Observing at a later time (2023-11-17) showed that the issue was repeatable.

Images below shows Realtime JPG pictures for the Locate 3 image (left) and for 1st Main Image (right), with BL Lac Target Circles (in blue)
The blue circle in the lefthand picture shows the position of BL Lac object. The blue circle is right-hand image is clearly mispositioned.

Image  Image


The Target Circle & Host Ellipse for AT 2023uhx/ NGC 3893 were also mispositioned in JPG pictures and is probably a further example of the same issue (S1167, 00:59).

Analysis
Replaying the BL Lac target in AstroMain OnTheFly Observing (using Target ID 17 & Images 1167249-54) showed that the bug was repeatable (a pleasant surprise as , replays typically fail to replicate ConvertFitsToJpg() bugs).  
 
The replay produced the following error for each main frames (the error wasn't reported during live session- is the error a sideeffect of image substitution used for the replay or is the report of this error one that is specifically withheld during live sessions ?

   ImageShift : Fail     Not enough stars (nStars 8, n 0)  

Examining log files showed that both test session and the live session contain messages like

   23:18:15.82 | GCVS BL Lac    Calc ImageShift(WrtLoc)   Fail | Not enough stars (nStars 8, n 0)

indicating that the report message is intentionally withheld during the live session. 

Comparing the Locate 3 Picture with the Picture from the first Main Frame shows that the BL Lac Target Circle is positioned in exactly the same XY location.   In the Locate 3 Picture the Circle honors the position of the BL Lac object,  but it doesn't in the Main Frame picture.  Stars shift noticeably between the two pictures and with the Calc ImageShift failing it explains why, without an Image Shift correction,  the Target Circle is mis-positioned in the  Main Frame pictures.   The Locate Frame and Main Frame pictures have plenty of stars and the method of finding stars and calculating ImageShift should have been successful. Examing raw FITS images the BL Lac object shifts 25.7 px (36.0") between Locate 3 and Focus Frame,  or 25.4 px (35.6" ) between Locate 3 and 1st Main Frame. Even though the physical shift is similar in both cases the shift calculation is successfully performed for the Focus Frame Image but fails for the Main Frame Image.  One hypothesis might be that the brightest stars in Main Frame picture are different because it is taken with R filter, instead of the C filter using by Locate 3 and Focus Frame Images. Another hypothesis is that due to the relatively large image shift (35-36"), there is greater risk of a dimmer star interferring with star offset determinations in the longer 60s exposures used by Main Frames.

Examining MatchBrightestStar results for 1st Main Frame in AstroMain 3.64.8 (which fixes 'duplicated Star 1 and Star 2' bug) we see the following :

  1 , X: 102.5, Y:  92.7, ClosestOffset: 25.6, OffsetX:  25.6, OffsetY:   0.7
  2 , X: 165.0, Y: 128.4, ClosestOffset: 25.6, OffsetX:  25.6, OffsetY:   0.6
  3 , X: 357.2, Y: 279.8, ClosestOffset: 24.5, OffsetX: -16.9, OffsetY:  17.8
  4 , X: 590.8, Y: 465.2, ClosestOffset: 10.5, OffsetX:  -8.0, OffsetY:  -6.8
  5 , X:  37.0, Y: 293.3, ClosestOffset: 24.3, OffsetX:   3.3, OffsetY: -24.1
  6 , X: 446.7, Y:  91.9, ClosestOffset: 19.0, OffsetX:  -8.6, OffsetY: -17.0
  7 , X: 658.8, Y: 213.7, ClosestOffset: 25.4, OffsetX:  25.4, OffsetY:   0.7
  8 , X: 362.9, Y: 303.5, ClosestOffset: 23.0, OffsetX:   6.9, OffsetY:  22.0

Of these matches only 3 matches (stars 1,2, 7) with Offsets of 25.4-25.6 pixels reflect 'correctly matched' stars. The other 5 rows are mismatches.

The Median offset is calculated to be 5.2 (X: 5.1, Y: 0.6) and none of the stars have an offset anywhere close to 5.2 and hence the routine's judges that there are not enough stars to determine a shift. 

Code was modified to show which particular Star in the new image was being matching and where it ranked in term of brightest to dimmest star in the image, and the target replayed with the following results for Main Image Frame 1

  1 , X: 102.5, Y:  92.7, ClosestOffset: 25.6, OffsetX:  25.6, OffsetY:   0.7, MatchedStar: 0/95
  2 , X: 165.0, Y: 128.4, ClosestOffset: 25.6, OffsetX:  25.6, OffsetY:   0.6, MatchedStar: 1/95
  3 , X: 357.2, Y: 279.8, ClosestOffset: 24.5, OffsetX: -16.9, OffsetY:  17.8, MatchedStar: 29/95
  4 , X: 590.8, Y: 465.2, ClosestOffset: 10.5, OffsetX:  -8.0, OffsetY:  -6.8, MatchedStar: 93/95
  5 , X:  37.0, Y: 293.3, ClosestOffset: 24.3, OffsetX:   3.3, OffsetY: -24.1, MatchedStar: 35/95
  6 , X: 446.7, Y:  91.9, ClosestOffset: 19.0, OffsetX:  -8.6, OffsetY: -17.0, MatchedStar: 79/95
  7 , X: 658.8, Y: 213.7, ClosestOffset: 25.4, OffsetX:  25.4, OffsetY:   0.7, MatchedStar: 7/95
  8 , X: 362.9, Y: 303.5, ClosestOffset: 23.0, OffsetX:   6.9, OffsetY:  22.0, MatchedStar: 32/95

Looking at the new revised table listing that shows the relative brightness of the matched star (based on its position within the inventory list) we can see for example that the 3rd brightest star in reference image was matched to the 29th brightest star in the new image, the 4th brightest star if matched with the 93rd brightest star etc.

The findings confirm that what the source of the problem is.

Conclusion

Fix 

Issue is fixed in AstroMain 3.64.8 on 2023-11-18 by modifying the CalcImageShift() routine to preferentially look for the closest star to each reference star position that is one of the top 12 brightest stars in the new image.  

Running the new AstroMain version and again replying the BL Lac target from the S1167 session produces JPG Pictures for the Main Image Frames that are correct:

The blue target circle in right hand picture showing the 1st Main Image frame is now correctly positioned.

Image  Image

The table of matched stars for the 1st Main Image frame shows that stars have been correctly match and show consistent shifts in the narrrow range 25.4 to 25.6 pixels.

1 , X: 102.5, Y:  92.7, ClosestOffset: 25.6, OffsetX: 25.6, OffsetY: 0.7, MatchedStar: 0/95
2 , X: 165.0, Y: 128.4, ClosestOffset: 25.6, OffsetX: 25.6, OffsetY: 0.6, MatchedStar: 1/95
3 , X: 357.2, Y: 279.8, ClosestOffset: 25.6, OffsetX: 25.6, OffsetY: 0.8, MatchedStar: 2/95
4 , X: 590.8, Y: 465.2, ClosestOffset: 25.5, OffsetX: 25.5, OffsetY: 0.9, MatchedStar: 3/95
5 , X:  37.0, Y: 293.3, ClosestOffset: 25.5, OffsetX: 25.5, OffsetY: 0.8, MatchedStar: 5/95
6 , X: 446.7, Y:  91.9, ClosestOffset: 25.5, OffsetX: 25.5, OffsetY: 0.6, MatchedStar: 6/95
7 , X: 658.8, Y: 213.7, ClosestOffset: 25.4, OffsetX: 25.4, OffsetY: 0.7, MatchedStar: 7/95
8 , X: 362.9, Y: 303.5, ClosestOffset: 25.6, OffsetX: 25.6, OffsetY: 0.9, MatchedStar: 8/95

A replay of NGC 3893 w/AT 2023uhx  confirms that the fix has also worked with this target set.

Back to Top