David's Astronomy Pages Notes - Session 1245 (2024-09-16)

Notes (S1244)

Notes Main

Home Page

Notes (S1246)

	Session Aims & Highlights
	- Observing Result  - Night Summary Plot  - Session Event Log
	Operational Issues
	- Critical Issues (0),  Major Issues (0),  Minor Issues (1),  Small Defects (2),  Continuous Improvement (1)
	Images from 2024-09-16 >>
	Replacement Temperature/Humidity Sensor (Greenhouse2)

Session Aims & Highlights (2024-09-16)

Main aims

1. Targets.  Acquire images of a selection of variable stars, nearby stars, comets & deep sky targets as allowed by sky conditions.
2. AstroMain.  Check new 3.69.8 version of AstroMain to ensure new code in ObsManager for handling JobQueue/TheSky6 freezes has no negative effects or problems
3. ImageLink/TheSky6.  Monitor session for any further incidents of the issue where the ImageLink process freezes for 5 minutes leading to Target Abort & Session Suspension.  Tracing was further extended in AstroMain 3.69.8. The new version also contains some statements tha might potentially resolve the ongoing issue.

 Equipment & Software

• 12" LX200 and ST-10XME
• 80mm APO and ZWO ASI 178MC
• TheSky6, CCDSoft5, DeviceHub 6.6.1.1,  MeadeGeneric 1.3.9, UPB 1.5, ASCOM 6.6,   Pulsar Dome Firmware 1.51 & Driver 6.3.10
• Pegasus UPB & Motor Focus, TCF-S
• SharpCap 3.2, PHD2  2.6.13, Siril 1.0.6, deCONZ 1.18.2, ASCOM 6.6 SP1
• [ DomeLink 1.0 / 1.1 - not used ]
   
• AstroMain 3.69.8,  AstroPlan 1.40.9,  AstroShCap 1.3.15, AstroGuard 1.10.5   (any new items or versions in bold)
  AstroVOE 1.13.2,  AstroSN 1.12,  AstroProtect 1.7,  AstroMove 1.12.14    when did astroSN 1.10.4 go to 1.11 ?
  AstroWeather 1.25, AstroAllSky 3.20.5,  AstroObsCam 1.11.4 (not 1.11.5), AstroLaunch 1.11.3

Highlights-

• Targets. 10/30 planned targets observations were completed, with one other target partially completed. Other targets failed due to cloud / session suspension.
• AstroMain.  There were no issues with the new version (AstroMain 3.69.8) however new code sections for tracing/reacting to Job Queue/TheSky6 freezes wasn't tested as no freezes occurred.
• ImageLink/TheSky6.  There were 0 incidents of the issue where the ImageLink process freezes for 5 minutes, leading to Target Abort and Session Suspension. 
  (is this because of the small changes made to Plate Solution routines or that the random occuring issue simply didn't occur during the session.
• Dome. No issues opening/closing shutter during session.  Dome closed and parked ok at end of session.

Notes:

• Aurora Images/Video from night, 2024-09-16/17 >>
  

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 20:40:31 Session Monitoring AutoStart monitoring for Live Session opportunity between 20:40 & 04:37 20:40:36 Session AutoStarting Session autostarting (20:40) 20:40:58   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.) 20:41:26   Camera1 Connected SBIG Camera connected (Set point -20°C) 20:41:29 Session Created Session Created (Live, 2024-09-16 S01245, ImageSaveNum: 1245001) 20:41:34   Scope Switched On Telescope Power has been switched on via UPB Powerbox. 20:43:35   Services Started Observatory Services started 20:43:42 Observatory (Auto) Observatory placed in Fully-Automated Mode 20:43:46 Session Pending Session pending (2024-09-16) 20:43:48 Session Initiating Session initiating (2024-09-16) 20:43:57   Camera1 Connected SBIG Camera connected (Set point -10°C) 20:44:04   Plan Requested Observing Plan requested from AstroPlan (1.40.9) 20:44:55   Plan Loaded Observing Plan loaded to queue (Plan ID: 1020) 20:45:36   Telescope Connected Telescope connected (TheSky6) 20:46:00 Session Equilibration Session ready to Open Dome 20:46:45   Dome Opened Dome opened (Opening time 45s, Zigbee 40s) 20:47:05 Session Running Session running 20:47:08   Queue Started Observing Queue started (30 targets selected) 20:47:11     Target Started (NrZen) Target started (Focus Field 19, HIP 93376) 20:47:26       Dome Unparked Dome unparked 20:50:31       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 20:52:57       Focusing Completed Foc1 AutoFocus Completed (Profile No 1, wide) 20:55:12       Focusing Completed Foc1 AutoFocus Completed (Profile No 1) 20:55:14       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 20:57:06       Focusing Completed Foc2 AutoFocus Completed (Profile No 2, wide) 20:58:48       Focusing Completed Foc2 AutoFocus Completed (Profile No 2) 20:59:05     Target Completed (NrZen) Target completed (Focus Field 19, HIP 93376) 21:00:32     Target Started (1/30) Target started (1/30, IC 1125 w/SN2024jz) 21:02:27       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (too few stars) 21:05:57     Target Failed (1/30) Target failed due to cloud (1/30, IC 1125 w/SN2024jz) 21:05:59   Queue Paused Queue paused for Session Suspension 21:06:01 Session Suspending Session suspending 21:06:47   Dome Closed Dome closed (Closing time 50s, Zigbee 43s) 21:06:49 Session Suspended Session suspended 21:19:28     Target Cancelled Target cancelled (1/30, IC 1125 w/SN2024jz) due to cloud 21:41:48     Target Cancelled Target cancelled (2/30, LEDA 1846725 w/SN2024iss) due to cloud 21:55:48     Target Cancelled Target cancelled (3/30, AT2024re (CV)) due to cloud 22:08:08     Target Cancelled Target cancelled (4/30, AT2022aeet (CV)) due to cloud 22:20:28     Target Cancelled Target cancelled (5/30, AT2022fkp (CV)) due to cloud 22:31:42     Target Cancelled Target cancelled (6/30, GCVS Z And) due to cloud 22:42:57     Target Cancelled Target cancelled (7/30, AT2023eu (CV)) due to cloud 22:53:15     Target Cancelled Target cancelled (8/30, GCVS CY Lyr) due to cloud 23:13:15     Target Cancelled Target cancelled (9/30, AT2023cuj) due to cloud 23:27:51     Target Cancelled Target cancelled (10/30, GCVS T CrB) due to cloud 23:47:12     Target Cancelled Target cancelled (11/30, AT2023ygv) due to cloud 23:59:31     Target Cancelled Target cancelled (12/30, Nova Vul 2024) due to cloud 00:09:19     Target Cancelled Target cancelled (13/30, KIC 8462852) due to cloud 00:21:39     Target Cancelled Target cancelled (14/30, AT2021aesn (CV)) due to cloud 00:41:59     Target Cancelled Target cancelled (15/30, CGCG 478-048 w/SN2022xzm) due to cloud 01:03:59     Target Cancelled Target cancelled (16/30, AT2024ges) due to cloud 01:26:19     Target Cancelled Target cancelled (17/30, AT2024vhz) due to cloud 01:40:19     Target Cancelled Target cancelled (18/30, AT2023abtp (CV)) due to cloud 01:52:19     Target Cancelled Target cancelled (19/30, AT2024epi (CV)) due to cloud 02:12:19     Target Cancelled Target cancelled (20/30, M31 w/AT2024dya) due to cloud 02:28:23 Session Resuming Session resuming 02:29:08   Dome Opened Dome opened (Opening time 45s, Zigbee 40s) 02:29:11 Session Running Session running 02:29:13   Queue Resumed Observing Queue resumed 02:29:15     Target Started (21/30) Target started (21/30, AT2024ugc) 02:32:53       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:35:04       Focusing Completed Foc1 AutoFocus Completed (Profile No 3) 02:41:49     Target Completed Target partially completed (21/30, AT2024ugc) 02:41:53     Target Started (22/30) Target started (22/30, NGC 3206 w/SN2024bch) 03:03:48     Target Completed Target completed (22/30, NGC 3206 w/SN2024bch) 03:03:52     Target Started (23/30) Target started (23/30, GCVS BL Lac) 03:07:30       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:09:31       Focusing Completed Foc1 AutoFocus Completed (Profile No 4) 03:13:24     Target Completed Target completed (23/30, GCVS BL Lac) 03:13:28     Target Started (24/30) Target started (24/30, AT2024uue (CV)) 03:16:40       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:19:08       Focusing Completed Foc1 AutoFocus Completed (Profile No 5) 03:25:01     Target Completed Target completed (24/30, AT2024uue (CV)) 03:25:05     Target Started (25/30) Target started (25/30, GCVS U And) 03:27:59       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:30:12       Focusing Completed Foc1 AutoFocus Completed (Profile No 6) 03:40:53     Target Completed Target completed (25/30, GCVS U And) 03:40:58     Target Started (26/30) Target started (26/30, UGC 2028 w/SN2022xkt) 03:44:07       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:46:36       Focusing Completed Foc1 AutoFocus Completed (Profile No 7) 04:03:04     Target Completed Target completed (26/30, UGC 2028 w/SN2022xkt) 04:03:08     Target Started (27/30) Target started (27/30, AT2023sqo (CV)) 04:14:50     Target Completed Target completed (27/30, AT2023sqo (CV)) 04:14:54     Target Started (28/30) Target started (28/30, LEDA 16241 w/SN2024qiw) 04:18:00       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 04:20:30       Focusing Completed Foc1 AutoFocus Completed (Profile No 8) 04:36:41     Target Completed Target completed (28/30, LEDA 16241 w/SN2024qiw) 04:36:45     Target Started (29/30) Target started (29/30, AT2024eja) 04:39:51       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 04:42:49       Focusing Completed Foc1 AutoFocus Completed (Profile No 9) 04:59:05     Target Completed Target completed (29/30, AT2024eja) 04:59:09     Target Started (30/30) Target started (30/30, AT2024vid) 05:02:49       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 05:05:22       Focusing Completed Foc1 AutoFocus Completed (Profile No 10) 05:19:53     Target Completed Target completed (30/30, AT2024vid) 05:19:55   Queue Completed Job Queue completed 05:19:59 Session Closing Session closing 05:20:54   Dome Closed Dome closed (Closing time 50s, Zigbee 43s) 05:22:15   Dome Parked Dome parked (parking time 73s), Az: 90.1 deg 05:23:28   Telescope Parked Telescope parked (parking time 67s total) 05:23:43   Telescope State Handbox reads 'Scope parked Turn scope off.' 05:24:06   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 05:25:32   Services Stopped Night Services stopped 05:25:35 Session Finishing Session Finishing started (Create Fits Summary, Transfer Files) 05:25:47     Dome (Find Park) Find Park started (Search Az 80.0 to 100.0°, Step 1.0°, Wide) 05:26:52     Dome Find Park found (Best Park Az 91.5°) 05:26:59     Dome (Find Park) Find Park started (Search Az 89.6 to 93.6°, Step 0.2°, Narrow) 05:27:51     Dome Find Park found (Best Park Az 91.4°) 05:27:57     Dome Dome has been synced at park position (Az 90.0°, Adjustment: -1.5°) 05:27:59   Dome Parked Dome parked 05:30:00   Dome Charging Dome is parked and re-charging Ok (29mA) 05:30:02 Session Finished Session Finished

Session Alerts & Alarms

Time     Type       Name Detail 03:05:00 Yellow Alert Dome Discrepency Difference between Dome Az and Slave Az is > 1 deg (GCVS BL Lac) 05:30:00 Green Clear Dome Charging Dome is parked and re-charging Ok (29mA)

Back to Top

Operational Issues (2024-09-16 S1245)

• Critical Issues (0)
• Major Issues (0)
• Minor Issues (1)
• Small Defects (2)
• Continuous Improvement (1)
  

[ Prev | Next ]

Critical Issues

• None

Major Issues

• None

Minor Issues

• Connectivity to observatory computers was lost (2024-09-17, 08:40). Connectivity to both observatory computer was lost at around 08:40 *several hours after the S1245 session finished). This is most likely due to a Lan/Internet Outage to Observatory which was a problem that previously affected the Observatory 5 times on 2024-09-07 & 2024-09-08. The issue was previously investigated (see Investigation - Interruptions in LAN & Internet Connectivity (2024-09-08) and showed that user attempts to fix/shortern the outages are typically non-effective and that the connection typically reestablishes itself within a 15-88 min period.  On this occasion the connectivity to Observatory will be monitored and intervention only made in the event that the outage lasts more than 24 hours.  This issue strengthens the case for retrospectivly install a CAT5/6 cable to the Observatory. After the outage had reached 10.5 hours and with a live session imminent, a partial intervention was made. The two observatory computers were purposedly left connnected via the Observatory's Ethernet Switch (which would allow a live session to proceed but without ability to get Weather Forcast data or upload live files). A number of attempts were made to reset the Ethernet-over-Powerline adapters in the Observatory and in the house next to the router.   Initial attempts didn't work, but eventually the LAN/router came back at 19:44. Did one of the user-initiated adapter resets trigger the successful econnection or was the connection going to reestablish itself anyway ?).  Given that the outage of just over 11 hours was a lot longer than the 15-88 min outages seen previously (2024-09-08), it would seem reasonable to believe that the adapter resets did trigger the reestablishment of the LAN/Router connection.  Later examination of ObsPics showed the LAN/Router connection was lost at 08:42 (rather than 08:40), that it was reestablished at 19:44, but lost again at 19:45, before finally being reestablished at 19:51.
  Resolved after 11 hours 2024-09-17 (Observatory, Ethernet Connection)

Small Defects

• AstroMove program showing ambiguous connection off-times to the two observatory computers  (2024-09-17, 10:00 ).  During the time that Observatory was affected by outage in LAN/Router connectivity, it was noticed that whilst both observatory computers (Laptop7 & Laptop9) showed an outage start time (Last Off) of 08:40:59, the Off-Time for Laptop7 (as at 10:56) was shown as being 2.2 hours (txtLastOffDuration2) , whilst the Off-Time for Laptop 9 was shown as 55.7 mins  (txtLastOffDuration1).   Since outage for both computers began at the same time, the offtime should be the same.  Examining the code in PingCheck() routine it can been seen that if ping attempt to a particular computer times-out the Last Off-Time will be updated, but if the ping attempt results in an exception the Last Off-Time is not updated.  It is assumed that after 55.7 mins the pings to Laptop9 produced exceptions but Pings to Laptop7 didn't. Fix attempted in AstroMove 1.12.15 so that in case of a ping exception the Last Off-Time is updated.
  Fix attempted 2024-09-17 (AstroMove 1.12:15)
   
• Both observatory computers showing 'No Internet access' yet they have access. After 11 hour outage in LAN/Internet connectivity (pings to observatory computers not returning,  AstroMove Connection flags red, No VNC access), the connectivity was eventually reestablished (AstroMove Connection Flags Green and VNC Connection made), however it was noticed over VNC that both computers were display the 'No Internet access' icon and "No Internet access" text pop-up. Opening an internet page confirmed that Internet Access did exist. It seems to be an Windows bug.  Earlier when resetting the Ethernet Over Powerline adapters, the 'No Internet Access' icon in system tray was used as a visual indicator that LAN/Internet Connection had reestablished or not,  but obviously it isn't a reliable indicator at all.  Other methods need to be used to confirm LAN/Internet Connection. A Continuous Improvement is raised to develop a tool to quickly shown the status of LAN/Internet Connection.  About 15 mins later both computers began showing the 'Internet' Access icon
  Closed  2024-09-17 (Windows,  Observatory Computer, AllSky/Weather Computer)

Continuous Improvement

• Develop a new facility or process to quickly determine the status of the observatory's LAN/Internet Connection from either of the observatory's two computer.  It was established that the presence of a 'No Internet Access' icon in a computer's system tray is not a reliable indicator as to whether the computer doesn't have LAN/Internet Connection.  The LAN flag can be used as indicator that LAN connection is a alive.  Prehaps there needs to be an Internet Flag ?.  AstroPlan's Main Form shows a Traffic Light flag showing the current status of the LAN connection.   This is sufficient for quiickly determining the status of the Observatory's LAN connection.
  Closed 2024-09-17 (Observatory Computer)

[ Prev | Next ]

Back to Top Issue,  Back to Top

Replacement Temperature/Humidity Sensor (Greenhouse2)

Back to Top