David's Astronomy Pages Notes - Session 1173 (2023-12-16)

Notes (S1172)

Notes Main

Home Page

Notes (S1174)

	Session Aims & Highlights
	- Observing Result  - Night Summary Plot  - Session Event Log
	Operational Issues
	- Critical Issues (0),  Major Issues (0),  Minor Issues (3),  Small Defects (6),  Continuous Improvement (9)
	Images from 2023-12-16 >>
	Investigation - LX200 continued tracking even though tracking had been turned off

Session Aims & Highlights (2023-12-16)

Main aims

1. Observatory Software. Check overall stability in Observatory Software following updates to AstroMain, AstroPlan and AstroAllSky since previous session, 11 days ago
2. Targets.  Acquire images of a selection of variable stars, nearby stars, comets & deep sky targets as allowed by sky conditions.
3. Dome Slewing.  Check out Dome Slewing since introduction of DomeLink driver that sits between DeviceHub and Pulsar Observatories Dome Drive.
4. FindPark.  Try out new FindPark routine in a Live Session under automated control (this will be tried during Finishing State right at the end of the Session)
5. 12P/Pons-Brooks. Acquire images of Comet 12P/Pons-Brooks which has been undergoing an outburst.

 Equipment & Software

• 12" LX200 and ST-10XME
• 80mm APO and ZWO ASI 178MC
• CCDApp2, 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.11dev4, Siril 1.0.6, deCONZ 1.18.2, ASCOM 6.6 SP1
   
• AstroMain 3.65.5, AstroPlan 1.39.4,  AstroShCap 1.3.15, AstroGuard 1.10.2
  AstroVOE 1.13  AstroSN 1.10.2,  AstroProtect 1.7,  AstroMove 1.12.10
  (AstroWeather 1.23.7, AstroAllSky 3.19.10,  AstroObsCam 1.11.4, AstroLaunch 1.11.1

Highlights

• Observatory Software. AstroMain, AstroPlan & AstroAllSky all functioned correctly.  Improvements and fixes in AstroMain broadly worked ok, but a few further tweaks can usefully made.
  Targets. 10/44 planned targets observations were completed, with 3 other targets partially completed. Other targets failed due to cloud / session suspension or were cancelled as the session was ended early due to low likelihood of further clear sky.
• 12P/Pons-Brooks. Images of Comet 12P/Pons-Brooks were acquired
•  Dome slewing. Dome Slewing was ok with none of the 16 slews affected by any delay or hold-up,
•  Dome Parking.  Dome Parked ok in correct position, allowing Shutter Battery to automatically recharge.
•  FIndPark.  FindPark operated ok by automated call during Finishing Stage and found Park Position ok (profile run at 0.5° steps, rather than 0.2° steps would have been better).

NotesNotes:

• .
  

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 17:03:19 Session Monitoring AutoStart monitoring for Live Session opportunity between 17:03 & 06:22 17:03:20 Session AutoStarting Session autostarting (17:03) 17:03:29   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.) 17:03:54   Camera1 Connected SBIG Camera connected (Set point -30°C) 17:03:56 Session Created Session Created (Live, 2023-12-16 S01173, ImageSaveNum: 1173001) 17:04:01   Scope Switched On Telescope Power has been switched on via UPB Powerbox. 17:05:47   Services Started Observatory Services started 17:05:53 Observatory (Auto) Observatory placed in Fully-Automated Mode 17:05:56 Session Pending Session pending (2023-12-16) 17:05:58 Session Initiating Session initiating (2023-12-16) 17:06:00   Plan Requested Observing Plan requested from AstroPlan (1.39.4) 17:07:16   Plan Loaded Observing Plan loaded to queue (Plan ID: 947) 17:07:31   Camera1 Connected SBIG Camera connected (Set point -10°C) 17:08:06   Telescope Connected Telescope connected (TheSky6) 17:08:30 Session Equilibration Session ready to Open Dome 17:09:15   Dome Opened Dome opened (opening time 45s) 17:09:18 Session Running Session running 17:09:20   Queue Started Observing Queue started (44 targets selected) 17:09:21     Target Started (NrZen) Target started (Focus Field 0, HIP 106) 17:09:35       Dome Unparked Dome unparked 17:12:20       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 17:14:56       Focusing Completed Foc1 AutoFocus Completed (Profile No 1, wide) 17:16:52       Focusing Completed Foc1 AutoFocus Completed (Profile No 1) 17:17:18       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 17:19:01       Focusing Completed Foc2 AutoFocus Completed (Profile No 2, wide) 17:20:44       Focusing Completed Foc2 AutoFocus Completed (Profile No 2) 17:21:01     Target Completed (NrZen) Target completed (Focus Field 0, HIP 106) 17:22:26     Target Started (1/44) Target started (1/44, M31 w/Nova M31 AT2023yij) 17:25:26       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 17:27:53       Focusing Completed Foc1 AutoFocus Completed (Profile No 3) 17:37:26   Observatory Door Observatory Door has opened 17:39:56   Observatory Door Observatory Door has closed (open time 2.5 min) 17:43:42     Target Completed Target completed (1/44, M31 w/Nova M31 AT2023yij) 17:44:46     Target Started (2/44) Target started (2/44, AT2023cz (CV)) 17:47:12   Observatory Door Observatory Door has opened 17:47:18   Observatory Door Observatory Door has closed (open time 6s) 17:50:10       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 17:52:18       Focusing Completed Foc1 AutoFocus Completed (Profile No 4) 17:52:44   Observatory Door Observatory Door has opened 17:52:50   Observatory Door Observatory Door has closed (open time 6s) 17:58:22     Target Completed Target completed (2/44, AT2023cz (CV)) 17:58:26     Target Started (3/44) Target started (3/44, M31 w/Nova M31 AT2023yqt) 18:00:58       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 18:17:01     Target Completed Target completed (3/44, M31 w/Nova M31 AT2023yqt) 18:19:26     Target Started (4/44) Target started (4/44, UGC 831 w/AT2023wdd) 18:21:57       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 18:24:09   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 18:24:11   HardSuspend Called Hard Suspend is called due to Critical Conditions (cloud) 18:24:14     Target Aborted (4/44) Target aborted (4/44, UGC 831 w/AT2023wdd) due to cloud 18:24:16   Queue Paused Queue paused for Session Suspension 18:24:18 Session Suspending Session suspending 18:25:45   Dome Closed Dome closed (closing time 90s) 18:25:47 Session Suspended Session suspended 18:31:35 Session Resuming Session resuming 18:32:30   Dome Opened Dome opened (opening time 55s) 18:32:33 Session Running Session running 18:32:35   Queue Resumed Observing Queue resumed 18:32:37     Target Started (4/44) Target started (4/44, UGC 831 w/AT2023wdd) 18:35:16       SoftSuspend Called Soft Suspend is called due to Deteriorating Conditions (reducing clarity) 18:36:41   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 18:36:43   HardSuspend Called Hard Suspend is called due to Critical Conditions (cloud) 18:36:45     Target Aborted (4/44) Target aborted (4/44, UGC 831 w/AT2023wdd) due to cloud 18:36:47   Queue Paused Queue paused for Session Suspension 18:36:49 Session Suspending Session suspending 18:37:31   Dome Closed Dome closed (closing time 45s) 18:37:33 Session Suspended Session suspended 18:38:22     Target Cancelled Target cancelled (4/44, UGC 831 w/AT2023wdd) due to cloud 18:50:33 Session Resuming Session resuming 18:51:18   Dome Opened Dome opened (opening time 45s) 18:51:20 Session Running Session running 18:51:22   Queue Resumed Observing Queue resumed 18:51:24     Target Started (5/44) Target started (5/44, C/2021 O3 (PANSTARRS)) 19:03:47     Target Completed Target partially completed (5/44, C/2021 O3 (PANSTARRS)) 19:03:51     Target Started (6/44) Target started (6/44, AT2022epv (CV)) 19:06:42       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 19:08:31       Focusing Completed Foc1 AutoFocus Completed (Profile No 5) 19:14:19     Target Completed Target completed (6/44, AT2022epv (CV)) 19:14:24     Target Started (7/44) Target started (7/44, 12P/Pons-Brooks) 19:17:42       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 19:29:35     Target Completed Target completed (7/44, 12P/Pons-Brooks) 19:29:50     Target Started (8/44) Target started (8/44, AT2023tvi (CV)) 19:32:55       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 19:35:07       Focusing Completed Foc1 AutoFocus Completed (Profile No 6) 19:40:55     Target Completed Target completed (8/44, AT2023tvi (CV)) 19:41:50     Target Started (9/44) Target started (9/44, GCVS CY Lyr) 19:46:03       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-S) 19:50:17     Target Completed Target completed (9/44, GCVS CY Lyr) 19:52:08     Target Started (10/44) Target started (10/44, AT2023qou (CV)) 19:55:29       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 19:57:29       Focusing Completed Foc1 AutoFocus Completed (Profile No 7) 20:03:17     Target Completed Target completed (10/44, AT2023qou (CV)) 20:04:08     Target Started (11/44) Target started (11/44, NGC 3690 w/SN2023wrk) 20:06:47   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 20:06:49   HardSuspend Called Hard Suspend is called due to Critical Conditions (cloud) 20:06:51     Target Aborted (11/44) Target aborted (11/44, NGC 3690 w/SN2023wrk) due to cloud 20:06:53   Queue Paused Queue paused for Session Suspension 20:06:55 Session Suspending Session suspending 20:07:47   Dome Closed Dome closed (closing time 55s) 20:07:50 Session Suspended Session suspended 20:23:24     Target Cancelled Target cancelled (11/44, NGC 3690 w/SN2023wrk) due to cloud 20:23:49 Session Resuming Session resuming 20:25:30 Session Suspended Session suspended 20:26:15   Dome Closed Dome closed (closing time 45s) 20:28:00 Session Resuming Session resuming 20:28:45   Dome Opened Dome opened (opening time 45s) 20:28:47 Session Running Session running 20:28:49   Queue Resumed Observing Queue resumed 20:28:51     Target Started (12/44) Target started (12/44, AT2022trk (CV)) 20:31:45       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 20:33:42       Focusing Completed Foc1 AutoFocus Completed (Profile No 8) 20:40:30     Target Completed Target completed (12/44, AT2022trk (CV)) 20:40:34     Target Started (13/44) Target started (13/44, AT2023tjz) 20:43:23       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 20:59:20     Target Completed Target completed (13/44, AT2023tjz) 21:00:50     Target Started (14/44) Target started (14/44, 29P/Schwassmann-Wachmann) 21:04:06       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 21:06:35       Focusing Completed Foc1 AutoFocus Completed (Profile No 9) 21:13:56       SoftSuspend Called Soft Suspend is called due to Deteriorating Conditions (too few stars) 21:17:36   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 21:17:38   HardSuspend Called Hard Suspend is called due to Critical Conditions (cloud) 21:17:41     Target Aborted (14/44) Target aborted (14/44, 29P/Schwassmann-Wachmann) due to cloud 21:17:43   Queue Paused Queue paused for Session Suspension 21:17:45 Session Suspending Session suspending 21:18:31   Dome Closed Dome closed (closing time 50s) 21:18:34 Session Suspended Session suspended 21:38:42     Target Cancelled Target cancelled (15/44, AT2023wue) due to cloud 21:58:20     Target Cancelled Target cancelled (16/44, Nova Cas 2021) due to cloud 22:00:19       Dome Unparked Dome unparked 22:18:50     Target Cancelled Target cancelled (17/44, AT2023yyz) due to cloud 22:30:12     Target Cancelled Target cancelled (18/44, GCVS HH And) due to cloud 22:49:17     Target Cancelled Target cancelled (19/44, UGC 4582 w/SN2023twg) due to cloud 23:11:37     Target Cancelled Target cancelled (20/44, AT2023twu) due to cloud 23:23:55     Target Cancelled Target cancelled (21/44, GCVS BL Lac) due to cloud 23:36:15     Target Cancelled Target cancelled (22/44, AT2022whd (CV)) due to cloud 23:54:30 User Intervention User request to close and finish session 23:54:33   Queue Aborted Job Queue aborted 23:54:35 Session Closing Session closing 23:54:40   Dome Closed Dome already closed (closed at 21:18, closing time 50s, zigbee 42s) 23:55:04   Dome Parked Dome parked (parking time 15s), Az: 90.0 deg 23:56:17   Telescope Parked Telescope parked (parking time 69s) 23:56:31   Telescope State Handbox reads 'Scope parked Turn scope off.' 23:56:54   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 23:58:16   Dome Charging Dome is parked and re-charging ok 23:58:18   Services Stopped Night Services stopped 23:58:21 Session Finishing Session Finishing started (Create Fits Summary, Transfer Files) 23:58:37     Dome (Find Park) Find Park started (Search Az 86.0 to 94.0°, Step 0.5°) 23:59:32     Dome Find Park found (Best Park Az 90.0°) 23:59:38     Dome Find Park completed (Dome at Az: 90.0°) 23:59:41 Session Finished Session Finished

Session Alerts & Alarms

Time     Type       Name Detail 17:05:54 Yellow Alert Disk Space Free Space on C:\ Drive (33.38 GB) is less than 50 GB 23:58:32 Yellow Alert Disk Space Free Space on C:\ Drive (31.84 GB) is less than 50 GB

Back to Top

Operational Issues (2023-12-16, S1173)

• Critical Issues (0)
• Major Issues (0)
• Minor Issues (3)
• Small Defects (6)
• Continuous Improvement (9)
  

[ Prev | Next ]

Critical Issues

• None

Major Issues

• None

Minor Issues

• Safari Browser on IPad not showing fresh Started, Suspended, FInishing ObsCam pictures but shows pictures from the previous session (22:00). This is an ongoing issue associated with cache behaviour on the IPad.  Old images are still shown when the Observatory Status and the Latest Session pages are refreshed.  Checking confirmed that the fresh images were created and were present on the webserver with the correct name. The fresh images appeared ok in MS Edge on AllSky/Weather Computer.  But continued to not appear in Safari on IPAD.   The  fresh images were made to appear by temporarily disabling IPads Wifi connection, performing a page refresh (which obviously fails), then turning on wifi again and redoing page refresh. Although its a workaround when needed it is inconvenient and shouldn't be necessary. Pages should be check to see if they are using " ?<?=rand(1,1000000)?" suffix to the respective image URLs.   Checking the pages show a typos,  instead links like  "ObsCam_SessionStarted.jpg?<?=rand(1,1000000)?" the links were like "ObsCam_SessionStarted.jpg?&lt;?=rand(1,1000000)?".  The &lt;  (which stands for "<" in html ) was somehow employed by web authoring / edits and then duplicated to other links via cut & paste. The "&lt;"  isn't interpretated in the same way as "<"  when in come to url's in Safari. Fixed by changing links to use ">" . This of course may not neccessarily resolve the issue it only explains why fresh images might not be appearing on Observatory Status page, as the Latest Session Page didn't have this url issue.
  Fixed 2023-12-17 (Website, IPAD/Safari) , fixed but monitor in future sessions
   
• Telescope Focusing was thrown off due to use of a poor Focus Profile result that should have been rejected by automated QC checks (21:06).  During a spot monitoring of the session using the Observatory website it was noticed that Focus Profile 9 point in the session's Best Focus Graph and subsequent focuser values deviated significantly from the prior values & trend shown by the previous 8 focus profiles (See Fig 1a). The offset was around 440 steps which is outside the telescope's system Critical Focus Zones, and would have led to suboptimal pictures for the following target(s). Examining the Profile 9 Chart (See Fig 1b) showed the FWHM data to be of very poor quality, and the calculated Best Focus should clearly have been rejected and not used. However it wasn't rejected and was used to reset the Focus Offset from 841 to 398.  As it turned out the issue was spotted during remote monitoring and a intervention made to reset the offset value back to the prior value.   Examination of focus frames at a later date (2024-03-19) indicates that the presence of a hot pixel is most-likely throwing off the FWHM calculation for the first two points in the profile and their result thows off the current find best focus position algorithums. Looking at the picture it is obvious to the profile result should be rejected but it sort of needs fuzzy logic to program this in a computer algorithum.  The data shows a very poor quality of match to the computed best fit curve, can this be calculated and used as a 'pass or reject' discriminator ? . Fixed in AstroMain 3.66.6, the dataset now undergoes a 'quality of fit' calculation in the 'CalculateBestFitQuadratic()' routine that generates a rms error 'RmsE' term, and is passed back. If the value is > 1.25 and profile type <> 'wide the profile is rejected.  Normal datsets have value of 0.1 to 0.5,  whilst Profile 9  has an RmsE value of 3.01 and would therefore now be rejected.  The RmsE value is reported and also posted on the Focus Profile Chart. 
  Fixed 2024-03-18 (AstroMain 3.66.6) 
   
• Telescope continued tracking after 21:33 even though a Turn-Off Tracking operation took place (21:33). Whilst investigating why a 'Dome Unparked' event was unexpectedly recorded at 22:00:19. it was determined that this was because the dome was incrementally moving in response to Slaving Calculations and commands from DeviceHub, and this was due to the telescope continuing to track after 21:33 when it was thought that the Tracking was turned off at a time point 15 minutes into a session suspension which had begun at 21:18. ObsPics show a Telescope Status to change from Tracking to Stationary at 21:33 and log file records the operation to Turn Off Tracking at 21:33:33.6.  Issue has been investigated (see Investigation - LX200 continued tracking even though tracking had been turned off 2023-12-16) which concluded that the issue is likely a one-off glitch with the LX200.   No further cases have been noted in the 24 sessions since (as of 2024-03-15) and it is decided to close the issue. A separate continuous improvement ticket has been raised for AstroMain to monitor the LX200 Az/Alt position whilst Tracking is off and raise an alert if the scope moves, and potentially intervene to turn tracking on & then off again in attempt to resolve issue, should it happen again.
  Closed after review 2023-12-18 (Session, LX200)

Small Defects

• Zigbee derived Shutter Opening/Closing Times are not been recorded in Session Events (17:09). AstroMain 3.65.4 /3.64.5 was modified to report the times to Open / Close the Obseravtory Shutter based on Zigbee Open/Closed Sensors at the top and bottom of the Shutter (e.g.  "Dome is open      (Opening time 45s, Zigbee 40s)" . Code was also changed to include the 'Zigbee' time in the Open Shutter / Close Shutter events recorded in the Session's Event table, but the events saved from the session (eg.  "17:09:15 Dome Opened     Dome opened (opening time 45s) "  don't include the 'zigbee time' as expected. Code needs to be checked and fixed.  Looking at code shows that intended addition for zigbee wasn't applied to all the code lines that prepares/saves the 'Dome Closed' & 'Dome Opened' Events.
  Fixed 2023-12-17 (AstroMain 3.65.6)
   
• Dome Azimuth reported during Search For Dome Park are sometime not as expected (2023-12-17). Whilst conducting a wide search whilst testing new wide/narrow Find Park (auto) the first few points were reported as
  
   Jog Dome (80.0°)  Ok   Az: 80.0°
 Jog Dome (81.0°)  Ok   Az: 81.0°
 Jog Dome (82.0°)  Ok   Az: 81.7°
 Jog Dome (83.0°)  Ok   Az: 82.0°
 Jog Dome (84.0°)  Ok   Az: 84.0°
  Examination of DomeLink log shows that the expected call SlewToAzimuth(83.0) is missing.
  17:49:05.176 SlewToAzimuth SlewToAzimuth(82.0)
17:49:05.180 Azimuth Get Azimuth = 81.0
17:49:05.180 Slewing Get True (Slewing forced to True for 500ms after calling SlewToAzimuth()
17:49:05.180 Azimuth Get Azimuth = 81.0
17:49:05.180 Slewing Get True (Slewing forced to True for 500ms after calling SlewToAzimuth()
17:49:05.954 Azimuth Get Azimuth = 81.0
17:49:05.954 Slewing Get False
17:49:06.954 Azimuth Get Azimuth = 81.7
17:49:06.954 Slewing Get True
17:49:07.948 Azimuth Get Azimuth = 82.0
17:49:07.948 Slewing Get False
  The issue is arises at 17:49:05.954  (778 ms after the SlewToAzimuth() command and 278 ms after the 500ms period where DomeLink forces return of Slewing=True) the defect in Pulsar Dome's driver kicks in and Dome reports Slewing=False when according to ASCOM principles in should be reporting Slewing = True).   DeviceHub sees Slewing = False and considers the Slew to Az 82 to have finished (at a point when it has dome azimuth 81.7 (which is recieved and reported by AstroMain). When AstroMain sends the SlewToAzimuth (83),  DeviceHub blocks this and doesn't pass it on as it sees that the Dome is in the act of slewing. (still slewing from its slew to Az 82).   DomeLink 1.1 modified to increase the period where it forces Slewing=True from 500ms to 1500ms.
  Fixed 2023-12-18 (DomeLink 1.1)
   
• Zigbee Sensor Monitoring isn't correctly reporting changes in Greenhouse Door states (2023-12-17).   Zigbee monitoring is picking up changes is Open/Closed state of the Greenhouse Door Sensor (recently added on 2023-12-13) and although it reports the event it doesn't include the key detail as to whether the Door has opened or it has closed..
  Fixed  2023-12-18 (AstroMain 3.65.7)
   
• After restarting up AstroMain and making a Slew action the ObsMonitor logged an inappropriate stationary time  (2023-12-17 17:48).  After restarting AstroMan and reconnecting to Dome etc and then trying out new SearchForDomePark() routines ObsMonitor picked up dome movement at 17:48:56 that was associated with the first part of slew from an initial Dome.SlewToAzimth(8).  The ObsMonitor logged the message Dome has moved 4.1 deg (Az 90.0 -> 85.9) after being stationary for 1,063,973,868.9 mins (THIS Is > 8 MINS).  This large number is result of a  MinutesSince  based on vcNullDate or a Null Date and should have been caught before posting the number to the log. ' THIS Is >' should be written 'This is > .
  Fixed  2023-12-18 (AstroMain 3.65.7) 
   
• Fits Summary 'CNTL-Q' function created ImageGroup with name RBV when the name BRV would be more appropriate.   The group name RBV was created as this was the order of the filters used.  Custom handling should be used such that if Image group is VBR or BRV or RBV or VBR or VRB the image group name is replaced by BVR.
  Fixed  2023-12-18 (Excel FITS Summary)
   
• The SBIG (Cam1) Camera Angle isn't centered on 180.0° but averages out at around 180.4°.   See Fig 2. Orientation of Camera should be changed so that Camera Angle is at 180.0° when telescope is pointing due south.  Note that due to the slight Polar Axis mis-alignment the camera angle will vary slightly from 180.0° depending on whether the telescope is pointing east or west of the meridian. Fixed in session S1187 (2024-02-20).
  Fixed 2024-02-20 (Observatory, SBIG Camera)

Continuous Improvement

• The session log has a lot of Relay trace messages which are probably no longer neccessary.  Too many trace message interfer with the reading of overall log file and deciphering of main observatory operations. Review and cut down the relay messages since many of them are no longer appropriate now that the Relay Protection monitoring is embedded and functioning ok .  Changed in AstroMain 3.65.6 so that the trace message is only written to log file if either SecondsSince(Dome.RelayChangeTime)  < 180 or  SecondsSince(CloudSensorData.RelayChangeTime) < 180.
  Done 2023-12-17 (AstroMain 3.65.6)
   
• 'Search For Dome Park' section of Report should use a Subtitle heading when called from the ObsManager.  When SearchForDomePark is called with CallMode.Auto (as happens from ObsManager's  Finishing Stage operations) it should use a SubTitle heading rather than a main Title heading in order to tie-in with the overall reporting of automated operations.  A Main title should still be used when the routine is initiated by a user call (CallMode.Manual)
  Done 2023-12-17  2023-12-17 (AstroMain 3.65.6)
   
• 'Search For Dome Park' section should use a finer step value than the value used in the session. Search For Best Park was used by ObsManager for first time in Session S1173, and used the a step value of 0.5° that was taken from a field on AstroMain's More/Dome tab. Following testing the position of the sensor elements was adjusted to narrow the width of the AtPark zone from 3° to just 1.2°. In this configurtion a step size of 0.2° is needed to more accurately resolve the boundaries of the 'AtPark' zone and hence achivee a better estimate of the Azimuth at centre of the AtPark range that is used for 'BestParkAz' .  Made SearchAz (centre),  Search Range and Step Size global values to allow them to be passed. Added initial wide search (1° steps) followed by narrow search (0.2°) . Added checkbox so used can use custom search range/steps or use auto settings.
  Done 2023-12-17 (AstroMain 3.65.6)
   
• Zigbee Report Section should be right-justify the 'Battery' values and use a fixed width so that report columns are better aligned.
  Done 2023-12-17  (AstroMain 3.65.6)
   
• Greenhouse Door & Vent Temperature fields on AstroMain's Greenhouse Tab should be removed or replaced by the Battery fields. The temperature values assoicated with Aqara Open/Closed Sensors used in the Observatory & Greenhouse are inaccurate and are rarely updated.  They are typically 5-8° different from actual temperature and don't necessarily follow temperature trends associated with dedicated temperature sensors.  Seeing the temperatures is unhelpful, distracting and should be removed. Temperature is provided by two Temperature/Humidity sensors which produce far better quality data.
  Done 2023-12-17 (AstroMain 3.65.6)
   
• A 'Dome Unparked' event was recorded at an unexpected time (22:00). A Dome Unparked' event was recorded in the Session Events table at 22:00:19. This was 42 mins after session suspension when the scope and the dome should have both been stationary, and the dome was not at its park position prior to the event so its unclear how the event was generated.  Earlier in the session at 17:09:35 there was a similar "Dome Unparked" event but this was produced directly after the dome moved away from it's initially Parked state at Az 90, and was totally expected.   The event is generated in conditions where Dome.AtPark = False and the previous value recorded under the property Dome.Parked = True. Looking through ObsPics from the session around this time it can be seen that Dome was lying at Az 82° when session was suspended at 21:18, and then proceeded to incrementally move to Az 85° at 21:33 (under supposed Slaved Dome commands from DeviceHub) at which point, telescope tracking was turned off and the scope became stationary, until it was parked at the end of the session at .   The dome remained slaved to the scope during this time and since the scope was stationary the dome should have remained stationary. However the ObsPics show the dome continue to incremental move during this time.  At 21:55 the Dome had reached Az 90 and the AtPark status became True (Zigbee monitoring independantly produces a "Dome has parked   (21:55:11, Zigbee sensor)" message at this time). Continuing to move, the Dome moved to Az 91° at 22:00 and AtPark status because False (again Zigbee monitoring independantly produces a "Dome has unparked (22:00:18, Zigbee sensor) message at this time). This change in state was picked up by AstroMain's ObsMonitor and this triggered the 'Dome Unparked' event.  Examination of logs and more detailed examination of ObsPics show that although the Scope was believed to have become stationary (IObsPics show a Stationary Flag) the telescope continued to track after 21:33. The occurance of the event is thus explained and the query ticket is therefore closed.  However why the scope continued to track after 21:33 instead of being stationary is treated under a separate Issue ticket.
  Close 2023-12-17   (AstroMain)
   
• Time at which Telescope Tracking is turned off/on should be reported. When Telescope tracking is turned off it is reported as "Turn Off Telescope Tracking   Ok        Tracking is OFF" . Whilst the session report shows the time that Tracking is changed it would be helpful if the time of the tracking change was reported in the Session Report File, eg When Tracking is turned off it comes after 15 mins after a session suspension and the time appears between report rows like "Wait for conditions to improve (21:19)" and "Continue   2023-12-16 21:38  (Local, GMT)" , it is uncertain when the Tracking was changed, other than it was between 21:19 to 21:38.
  Done  2023-12-18 (AstroMain 3.65.7)
   
• Cam1 & Cam2 Camera Angle Graphs should have use a bold line for grid-lines at 180° and 0° respectively.  Camera Angle graphs can be improved by highlighting the intended Camera Angles for the two telescope cameras (Cam1 on the LX200 main scope and Cam2 on the TS80 secondary scope). This will be helpful for picking up on any shift in Camera Angles at an earlier stage.
  Done  2023-12-22 (AstroWeather 1.23.8)
   
• Modify AstroMain to monitor the LX200 Az/Alt position whilst Tracking is off and raise an alert if the scope moves.  This ticket follows from issue during the session when scope continued tracking even though tracking had been turned off (see Investigation - LX200 continued tracking even though tracking had been turned off 2023-12-16. Examining code shows this monitoring is partially already in place.  Scope.TrackOffAz & Scope.TrackOffAlt are recorded when tracking are turned off, and a section in RunObsMonitor. Implemented in AstroMain 3.66.6, code now reports and raises alert when the azimuth movement reaches 2°.  AstroMain could potentially intervene to send a Set Tracking = True command, followed by a new Set Tracking = False command in an attempt to fix the situation but this is not yet implemented, though a Scope.ResetTrackingOff() routine is written to perform this function if called.
  Done 2024-03-18 (AstroMain 3.66.6)

[ Prev | Next ]

---

Fig 1a.   Focus Chart from S1173 Session showing anomalous result from Focus Profile 9.


 

Fig 1b.   Focus Profile 9
Profile somehow passed QC checks when it it should have been dismissed and not used.

 

Fig 2. Cam1 (SBIG) Camera Angle . Camera Angle up to 180.4° instead of ideal angle (180.0°)

Back to Top

Investigation - LX200 continued tracking even though tracking had been turned off

Back to Top