David's Astronomy Pages Notes - Session 1231 (2024-08-20)

Notes (S1230)

Notes Main

Home Page

Notes (S1232)

	Session Aims & Highlights
	- Observing Result  - Night Summary Plot  - Session Event Log
	Operational Issues
	- Critical Issues (0),  Major Issues (0),  Minor Issues (3),  Small Defects (4),  Continuous Improvement (3)
	Images from 2024-08-20 >>

Session Aims & Highlights (2024-08-20)

Main aims

1. Targets.  Acquire images of a selection of variable stars, nearby stars, comets & deep sky targets as allowed by sky conditions.

 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.5,  AstroPlan 1.40.7,  AstroShCap 1.3.15, AstroGuard 1.10.5   (any new items or versions in bold)
  AstroVOE 1.13.2,  AstroSN 1.11.1,  AstroProtect 1.7,  AstroMove 1.12.12    when did astroSN 1.10.4 go to 1.11 ?
  AstroWeather 1.25, AstroAllSky 3.20.4,  AstroObsCam 1.11.4 (not 1.11.5), AstroLaunch 1.11.3

Highlights-

• Targets. 8/10 planned targets observations were completed, with 1 other target partially completed.  One target failed due to cloud.
• Dome. No issues opening/closing shutter during session. Dome closed and parked ok at end of session.

Notes:

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 23:57:16 Session Monitoring AutoStart monitoring for Live Session opportunity between 23:57 & 03:41 23:57:17   AutoStart Delayed Session delayed due to too few stars 00:49:47 Session AutoStarting Session autostarting (00:49) 00:50:09   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.) 00:50:37   Camera1 Connected SBIG Camera connected (Set point -10°C) 00:50:40 Session Created Session Created (Live, 2024-08-20 S01231, ImageSaveNum: 1231001) 00:50:45   Scope Switched On Telescope Power has been switched on via UPB Powerbox. 00:52:40   Services Started Observatory Services started 00:52:47 Observatory (Auto) Observatory placed in Fully-Automated Mode 00:52:49   AutoStart Delayed Session delayed due to too few stars 00:52:51 Session Pending Session pending (2024-08-20) 00:52:53 Session Initiating Session initiating (2024-08-20) 00:52:59   Camera1 Connected SBIG Camera connected (Set point -10°C) 00:53:06   Plan Requested Observing Plan requested from AstroPlan (1.40.7) 00:53:56   Plan Loaded Observing Plan loaded to queue (Plan ID: 1006) 00:54:37   Telescope Connected Telescope connected (TheSky6) 00:55:01 Session Equilibration Session ready to Open Dome 00:55:51   Dome Opened Dome opened (Opening time 45s, Zigbee 40s) 00:56:06 Session Running Session running 00:56:09   Queue Started Observing Queue started (10 targets selected) 00:56:12     Target Started (NrZen) Target started (Focus Field 22, HIP 108888) 00:56:28       Dome Unparked Dome unparked 00:59:13       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:02:25       Focusing Completed Foc1 AutoFocus Completed (Profile No 1, wide) 01:04:49       Focusing Completed Foc1 AutoFocus Completed (Profile No 1) 01:04:51       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 01:07:00       Focusing Completed Foc2 AutoFocus Completed (Profile No 2, wide) 01:08:44       Focusing Completed Foc2 AutoFocus Completed (Profile No 2) 01:09:01     Target Completed (NrZen) Target completed (Focus Field 22, HIP 108888) 01:09:34     Target Started (1/10) Target started (1/10, NGC 6384 w/SN2024pxl) 01:16:25       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:19:08       Focusing Completed Foc1 AutoFocus Completed (Profile No 3) 01:35:32     Target Completed Target completed (1/10, NGC 6384 w/SN2024pxl) 01:35:36     Target Started (2/10) Target started (2/10, AT2023abtv (CV)) 01:38:40       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:41:10       Focusing Completed Foc1 AutoFocus Completed (Profile No 4) 01:47:06     Target Completed Target completed (2/10, AT2023abtv (CV)) 01:47:10     Target Started (3/10) Target started (3/10, GCVS BL Lac) 01:49:59       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:52:34       Focusing Completed Foc1 AutoFocus Completed (Profile No 5) 01:56:31     Target Completed Target completed (3/10, GCVS BL Lac) 01:56:35     Target Started (4/10) Target started (4/10, AT2022vxe) 01:59:31       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:02:28       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (too few stars) 02:02:34       Focusing Failed Foc1 focusing check failed 02:02:36       Focusing Completed Foc1 AutoFocus Completed (Profile No 6) 02:04:18       SoftSuspend Cancelled Soft Suspend is cancelled due to improved conditions 02:06:38       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (too few stars) 02:11:15     Target Completed Target completed (4/10, AT2022vxe) 02:11:17   Queue Paused Queue paused for Session Suspension 02:11:19 Session Suspending Session suspending 02:12:09   Dome Closed Dome closed (Closing time 50s, Zigbee 42s) 02:12:12 Session Suspended Session suspended 02:17:40     Target Cancelled Target cancelled (5/10, GCVS HH And) due to too few stars 02:20:25 Session Resuming Session resuming 02:21:10   Dome Opened Dome opened (Opening time 45s, Zigbee 40s) 02:21:12 Session Running Session running 02:21:14   Queue Resumed Observing Queue resumed 02:21:18     Target Started (6/10) Target started (6/10, AT2024koe) 02:24:47       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:27:31       Focusing Completed Foc1 AutoFocus Completed (Profile No 7) 02:44:28     Target Completed Target completed (6/10, AT2024koe) 02:44:32     Target Started (7/10) Target started (7/10, M33 w/Nova M33 2024-08a?) 03:00:28       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (reducing clarity) 03:03:02     Target Completed Target completed (7/10, M33 w/Nova M33 2024-08a?) 03:03:04   Queue Paused Queue paused for Session Suspension 03:03:06 Session Suspending Session suspending 03:03:53   Dome Closed Dome closed (Closing time 50s, Zigbee 43s) 03:03:56 Session Suspended Session suspended 03:05:04 User Intervention User Intervention to abort job queue & switch back to Manual Mode 03:05:06   Queue Aborted Job Queue aborted 03:05:22   Services Stopped Observatory Services stopped 03:05:26 Session Closed Session closed by User 03:05:30 Program Closed Program closed by User 03:06:20 Program Opened Program Opened (AstroMain 3.69.5) 03:06:22 Session Resumed Session Resumed (Live, 2024-08-20 S01231, ImageSaveNum: 1231045) 03:06:27   Obs.Overseer Started Obs.Overseer started 03:06:39   Obs.Manager Started Obs.Manager started 03:06:47   Services Started Observatory Services started 03:08:08   Services Started Observatory Services started 03:08:27   Camera1 Connected SBIG Camera connected (Set point -10°C) 03:08:48   Telescope Connected Telescope connected (TheSky6) 03:09:33 Observatory (Auto) Observatory placed in Fully-Automated Mode 03:09:36 Session Pending Session pending (2024-08-20) 03:09:38 Session Initiating Session initiating (2024-08-20) 03:09:45   Camera1 Connected SBIG Camera connected (Set point -10°C) 03:09:52   Plan Loaded Observing Plan loaded to queue (Plan ID: 1006) 03:10:34   Telescope Connected Telescope connected (TheSky6) 03:10:53 Session Equilibration Session ready to Open Dome 03:10:55   Wait On Weather Waiting for acceptable conditions 03:10:57 Session Suspending Session suspending 03:10:59   Dome Closed Dome already closed (closed at 03:03, Closing time 50s, Zigbee 0s 03:11:01 Session Suspended Session suspended 03:11:25   Queue Started Observing Queue started (3 targets selected) 03:13:59 Session Resuming Session resuming 03:14:44   Dome Opened Dome opened (Opening time 45s, Zigbee 40s) 03:14:47 Session Running Session running 03:14:49   Queue Resumed Observing Queue resumed 03:14:51     Target Started (8/10) Target started (8/10, AT2023pua (CV)) 03:27:37     Target Completed Target partially completed (8/10, AT2023pua (CV)) 03:27:41     Target Started (9/10) Target started (9/10, UGC 1595 w/AT2024kcu) 03:49:00     Target Completed Target completed (9/10, UGC 1595 w/AT2024kcu) 03:49:04     Target Started (10/10) Target started (10/10, NGC 797 w/SN2024jjc) 03:51:52       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:54:19       Focusing Completed Foc1 AutoFocus Completed (Profile No 10) 04:11:10     Target Completed Target completed (10/10, NGC 797 w/SN2024jjc) 04:11:12   Queue Completed Job Queue completed 04:11:14 Session Closing Session closing 04:12:09   Dome Closed Dome closed (Closing time 50s, Zigbee 43s) 04:12:46   Dome Parked Dome parked (parking time 30s), Az: 90.0 deg 04:14:07   Telescope Parked Telescope parked (parking time 75s total) 04:14:22   Telescope State Handbox reads 'Scope parked Turn scope off.' 04:14:44   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 04:16:07   Services Stopped Night Services stopped 04:16:09 Session Finishing Session Finishing started (Create Fits Summary, Transfer Files) 04:16:22     Dome (Find Park) Find Park started (Search Az 88.0 to 92.0°, Step 0.2°, Narrow) 04:17:24     Dome Find Park found (Best Park Az 90.0°) 04:19:10   Dome Charging Dome is parked and re-charging Ok (58mA) 04:19:12 Session Finished Session Finished

Session Alerts & Alarms

Time     Type       Name Detail 04:19:10 Green Clear Dome Charging Dome is parked and re-charging Ok (58mA)

Back to Top

Operational Issues (2024-08-20 S1231)

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

[ Prev | Next ]

Critical Issues

• None

Major Issues

• None

Minor Issues

• AstroSN is crashing with unhandled"Object reference not set to an instance of an object." exception (pre-session).  AstroSN's 'Get Active SN' operation failing with unhandled System.NullReferenceException with the message "Object reference not set to an instance of an object.".  Running the program in VS Debugger shows that the error occurs in the 'Dim rows.." codeline in GetActiveSnData() routine
    Dim doc As HtmlDocument = web.Load(SnFileUrl)
  Dim tables As HtmlNodeCollection = doc.DocumentNode.SelectNodes("//table")   ' Get all tables in the document
  Dim rows As HtmlNodeCollection = tables(1).SelectNodes("tr")   ' look at rows in the first table

  Problem seems to be due to the intended source data page (https://www.rochesterastronomy.org/snimages/snname.html ) ( loaded as an HtmlDocument) returning a  '404 error' page, which doesn't have the expected structure.  Code should be modified so that 'rows  = tables(1).SelectNodes("tr")  is placed within a Try..Catch..End Try block so that the program doesn't crash, and can give a suitable report message and MsgBox.  Program was run again the following day and the problem of the missing snname.html file has resolved itself.
  Fixed 2024-08-21 (AstroSN 1.11.1)
   
• AstroAllSky not producing annotated 'Scope' AllSky Images & not showing Telescope/Dome activity on NightSummary Plot.  Whilst checking status of session it was notice that AllSky Images didn't show Scope/Next Targets position and that AllSky 'Scope' images were been produced. It was also noticed that the NIghtSummary6 Chart wasn't showing the expected Telescope/Dome activity bars.  ObsEnv data communication to AstroWeather & AstroObsCam both appeared to working ok.  AstroAllSky was restarted, but it didn't resolve the issue.  It is presumed to be due to a TCP/IP communication failure associated with sending TelePosition records to AllSky/Weather Computer.   Finally (as a test & last resort) an interventation was made at 03:05 (during a Session Suspension) to close AstroMain's Observatory Services and to then restart the AstroMain & Services.  This resolved the session, with 11 _Scope images being subsequently created.
  Resolved In-Session 2024-08-21 (Session, AstroAllSky/AstroMain)
   
• Weather Station's Outside Temp Sensor appears to be reading too high. In recent sessions the Weather Station's Outside Temperature Sensor (located under the observatory's 'Observatory Computing' bay for better reception) seems to be reading too high (see Fig 1).   No such discrepency was observed in the S1231 session however (see Fig 2).  No action required at present, continue to monitor in future sessions.  A trim setting on AstroMain's ObsManager tab could potentially be used to 'correct' values if required.
  Closed 2024-08-22 (Session, Outside Temperature) , closed but continue to monitor in future sessions
   
• A table of General Alerts on the Latest/Current Session web page indicated a 14s power outage (20:17) The table of General Alert indicated Mains Power Outage at 20:17:43, with power restoration at 20:17:57, an outage of 14s, however Report Files/Logs for the time period (2024-08-20) on the Observatory Computer didn't report or record such an outage, and thus the messages are likely to be 'False' . Investigating showed that the power outage was a brief disconnnection of the power cable to the Development/Analysis Laptop Computer, and is not a general problem to the power supply to the household & to the Observatory.  The alerts simply shouldn't have made there way onto the Observatory Website.  The problem is due to the transfer of the latest Targets Database (including Session Alerts table) from the Development/Analysis Computer to the Observatory Computer prior to the S1231 Session.  This action ensures the Observatory Computer has the latest Targets etc, but it has the unfortunately side-effect that the General Event / General Alert database tables on the Observatory Computer (with any recent events & alerts) become over-written with recent events & alerts on the Development/Analysis Computer).   The database transfer to the Observatory Computer shouldn't move general alerts associated with the Development/Analsis Computer, but instead preserve those that are associated with the Observatory.  It isn't clear how this can be achieved.  A separate Continuous Improvement ticket is raised to review the issue & develop a strategy/way forward.
  Issue Understoof 2024-08-28 (Session, Targets Database, AstroMove, User Awareness)

Small Defects

• AstroMain not copying the '_Scope' folder/files from G Drive on AllSky/Weather to the Session Folder area on the Development Computer.  During post-session copying of S1231 session files from the observatory computers to the Development/Analyis Computer at 09:12 the _Scope Folder/Files weren't copied, although the AstroMove console reported "Transferring .\AllSky 2024-08-20\_Scope\..." without any error or fail message but flagged on the form label as 'Empty Source".  Checking the "G\All Sky - Sessions\AllSky 2024-08-20\_SCOPE" folder on the AllSky/Weather computer shows that it contains 11 .Jpg images, (and these were all perfectly readable.   Tested the operation by running AstroMove program in Visual Studio debugger.  Problem appears to be due to 'Data\AllSky Imaging\Sessions' folder unexpectedly containing a 'AllSky 2024-08-20' folder with an empty '_Scope' subfolder.  Updated AstroMove 1.12.13 to report a 'Fail  Source Folder is empty" message. Fixed 2024-08-22 by deleting the empty 'Sessions\AllSky 2024-08-20\_Scope' foldet on AllSky/Weather's C Drive and rerunning AstroMove's 'Copy Files From Observatory' routine.
  Closed 2024-08-21 (Session, AstroMove 1.12.13)
   
• AstroMove isn't always able to move files from AllSky/Weather Computer, producing "Fail  -Source File not found" errors.  A second or third attempt frequently work (unless there is a network issue).  Problem typically occurs after resuming Development/Analysis computer and Windows is unable to resolve the host name (LAPTOP7) or otherwise is able to find the AllSky/Weather Computer.  Fixed in AstroMove 1.12.13, 4 attempts are made to access the AllSky/Weather computer with 2s wait period in between each attempt.
  Closed 2024-08-21 (AstroMove 1.12.13)
   
• Main Images of UGC 1595 w/AT2024kcu failed to output pointing error to 'Reduced (pointing).dat' file/excel  during Reduced Files Analysis (post-session).  Although the Locate frames link (plate solve) ok during 'the Analyse Reduced Folder' operation, all 5 main image subframes for this target didn't output normal pointing error data to the session's '...Reduced (pointing).dat' file, but output vcNull (-99) instead. This made it appear that the frames hadn't linked, possibily due to cloud.  This happened although looking normal and star bearing (36 stars), and a plate solution was achieved on 0.3 - 0.4s. Issue appears to be due to rejection of the Plate Solution as the Image Linking didn't populate the FITs header with expected keywords for WCS center (CRVAL1, CRVAL2)
  
    Analysing image 52 of 63 (01231052.REDUCED.FIT)
  Image/Object                 REDUCED UGC 1595
  - FileName                   Ok      01231052.REDUCED.FIT
  - Exposure                   180s    [01231052] (3x3 180s C -14.8°C)
  - Date/Time                  Ok      2024-08-21 02:32:56 UT
  - Star Inventory             Ok      nObjects = 37 (nStars = 37)
  Linking image (UCA/USNO*)... Ok      Solved in 0.4s (Stars 37, Scale 1.401, Angle 179.80°)
  - Checking WCS               Fail    Image doesn't contain keywords for WCS center (CRVAL1, CRVAL2)
  - Plate Coordinates (RA)     Ok      02 06 26.744 (RA J2000)
  - Plate Coordinates (Dec)    Ok      +27 02 02.43 (Dec J2000)
  - Pointing Error             Ok      0.16' [N: 0.06', W: 0.14']
  - Analysing stars ...        Ok      Stars= 0/0 (0.0s)
  Closed after review 2024-08-21 (AstroMain, User Awarness)
   
• Greenhouse Temp/Humidity Sensor 2 is unreachable. The Greenhouse2 T/H sensor is unreachable, reducing greenhouse environmental data collection and removing backup T/H measurements in the event that the Greenhouse(1) T/H Sensor becomes unreachable or fails, which if uncorrected could have with serious impact on Greenhouse Heating Control during the forthcoming winter season (starting in 3 months time) . Looking back at observatory logs the Greenhouse2 sensor became unreachable some time between  2024-08-15 09:00 (new General Session) and 2024-08-15 21:35 (AstroMain restarted). ObsEnv file shows that Sensor2 values have been flat-lining at T. 34.5°C  / H. 36.5%,  since 2024-08-14 11:15.  Log file show that the last vaid Temperature2/Humidty values were at 2024-08-14 12:39:52.  The problem seems to be unrelated to the Lightning Storm on 2024-08-12 (with associated power outages & likely power surge event) on as this was a full 2 days before the sensor values flat-lined.  A fix was attempted on 2024-09-07.  The Greenhouse2 sensor was taken to the Observatory, reset and an attempt made to re-add the Sensor using the Phoscon App. This didn't work, the sensor wasn't detected & the sensor continued to show as 'Unreachable'.  After trying several times, the sensor was deleted in the Phoscon App, and a fresh attempt made to reset the sensor and add it but again it wasn't detected. Eventually reloaded the last saved settings backup file (raspbee_gateway_config_2024-03-13.dat) and this time the sensor appeared as 'Reachable' but unfortunately had T/H values of 13.6°C / 50% which remained flat. A sensor 'query' showed that whilst Reachable now had the value 'true'  the state data had a 'lastupdated' value of 2024-03-01T18:16:30.  and looking at archived ObsEnv file  Greenhouse2 T/H values were 8.6°C / 69.6% at this time, however at 2024-03-13T17:36 (the date of the newly loaded config file the T/H values were 13.6°C /  50.4%. It appears that there is a problem with either the sensor not reading fresh T/H values or not being able to probably reconnect with the Zigbee Network.  If a solution can't be found the sensor will need to be replaced before the winter, as it is necessary to have a working back-up T/H sensor in the Greenhouse in order for Regulated Temperature Control to operate correctly during cold winter weather. Fixed, a new replacement sensor has been installed on the Zigbee Network on 2024-09-16 (see Replacement Temperature/Humidity Sensor (Greenhouse2), 2024-09-16 ).
  Fixed 2024-09-16 (Zigbee Network, Greenhouse2 Sensor) 

Continuous Improvement

• Add 'Latest Southern Sky' Panaromic Image to Current Session Page. Add 'Latest South Sky' Panoramic Image to 'session_current' web page, to save the user from having to jump acrpss to the 'Latest AllSky Images' Page.
  Done 2024-08-21 (Website)
   
• Review method of transferring targets database to Observatory Computer in regard to preserving General Event/Alerts associated with the Observatory. A table of General Alerts on the Latest/Current Session web page indicated a 14s power outage (202408-20 20:17)  however this was associated with a  brief disconnnection of the power cable to the Development/Analysis Laptop Computer, and was not a problem to the power supply to the Observatory at all and the alert shouldn't have made its way onto the Observatory Website.  The problem is due to the transfer of the latest Targets Database (including Session Alerts table) from the Development/Analysis Computer to the Observatory Computer prior to the S1231 Session.  This action ensures the Observatory Computer has the latest Targets etc, but it has the unfortunately side-effect that the General Event / General Alert database tables on the Observatory Computer (with any recent events & alerts) become over-written with recent events & alerts on the Development/Analysis Computer.   The database transfer to the Observatory Computer shouldn't move general alerts associated with the Development/Analsis Computer, but instead preserve those that are associated with the Observatory. This ticket is raised to review the issue & develop a strategy/way forward, as it isn't clear how this can be easily achieved.  Implemented in AstroPlan 1.41, by creating a new "Local.sqlite" database (CreateLocalDatabase), with 'sessionevent" and "sessionalert" tables (CreateLocalTables) and then modify existing AstroPlan database routines to select, insert or delete events & alerts from the relevant table in LocalDB when SessionID = -10 (General) or to select, insert or delete events & alerts from relevant table in MainDB (was objConn). when SessionID = a live Session ID. Support for new Local Database implemented in AstroMain 3.70 & AstroMove 1.13
  Done 2024-09-17 (AstroPlan, 1.41,  AstroMain 3.70, AstroMove 1.13,  Local Database)
   
• Query. Are date/times being corrected output to ObsEnv Record.  Date/Time (Z) for last Greenhouse1 &Greenhouse2 sensor changes appear to have a  1 hour discrepency with the record's date/time (Z).
  To investigate 2024-08-21+ (AstroMain, ObsEnv, Zigbee)
   
• Query. Visual Studio has started posting Solution File into 'Recent' list, can this be surpressed. Prior to the currently used VS version (17.11.0), selecting a vbproj to resume from Recent Files list would just update Recent list with the vbProj's new access date. Now the Recent  list becomes populated by the solution file which effectively halves the number of projects that can be seen in the 'Recent'  list (2 items, /sln and /vbproj file for each project).
  To investigate 2024-08-21+ (AstroMain, ObsEnv, Zigbee)

[ Prev | Next ]

[ Prev | Next ]

Back to Top