David's Astronomy Pages Notes - Session 1306 (2025-03-28)

Notes (S1305)

Notes Main

Home Page

Notes (S1306)

	Session Aims & Highlights
	- Observing Result  - Night Summary Plot  - Session Event Log
	Operational Issues
	- Critical Issues (0),  Major Issues (1),  Minor Issues (5),  Small Defects (2),  Continuous Improvement (3)
	Images from 2025-03-28 >>
	Current/Latest Session >>

Session Aims & Highlights (2025-03-23)

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 7.0.3 RC3.4694, MeadeGeneric 1.3.12.522 , UPB 1.5,  Pulsar Dome Firmware 1.51 & Driver 6.3.10
• Pegasus UPB & Motor Focus, TCF-S 6.0.6
• SharpCap 3.2, PHD2  2.6.13, Siril 1.0.6, deCONZ 1.18.2, ASCOM 7.0.3 RC3
• [ DomeLink 1.0 / 1.1 - not used ]
   
• AstroMain 3.73.14,  AstroPlan 1.43,  AstroShCap 1.3.15, AstroGuard 1.10.6   (any new items or versions in bold)
  AstroVOE 1.15.1,  AstroSN 1.14,  AstroProtect 1.10.6,  AstroMove 1.15.2 
  AstroWeather 1.27.5, AstroAllSky 3.23.1,  AstroObsCam 1.11.4 (not 1.11.5), AstroColorCam 1.2.2, AstroLaunch 1.11.14

Highlights

• Targets. 18/24 planned targets observations were completed, with 3 other targets partially completed. Other targets (3) failed due to cloud/shower & session suspension.
•   Dome. There was no issues opening/closing the shutter during the session. Dome closed and parked at end of session Ok.

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 20:34:33 Session Monitoring AutoStart monitoring for Live Session opportunity between 20:34 & 03:37 20:34:35 Session AutoStarting Session autostarting (20:34) 20:34:58   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.) 20:35:26   Camera1 Connected SBIG Camera connected (Set point -20°C) 20:35:29 Session Created Session Created (Live, 2025-03-28 S01306, ImageSaveNum: 1306001) 20:35:34   Scope Switched On Telescope Power has been switched on via UPB Powerbox. 20:37:17   Services Started Observatory Services started 20:37:25 Observatory (Auto) Observatory placed in Fully-Automated Mode 20:37:28 Session Pending Session pending (2025-03-28) 20:37:30 Session Initiating Session initiating (2025-03-28) 20:37:37   Camera1 Connected SBIG Camera connected (Set point -20°C) 20:37:44   Plan Requested Observing Plan requested from AstroPlan (1.43) 20:38:21   Plan Loaded Observing Plan loaded to queue (Plan ID: 1090) 20:39:00   Telescope Connected Telescope connected (TheSky6) 20:39:25 Session Equilibration Session ready to Open Dome 20:40:10   Dome Opened Dome opened (Opening time 45s, Zigbee 41s) 20:40:45 Session Running Session running 20:40:48   Queue Started Observing Queue started (24 targets selected) 20:40:52     Target Started (NrZen) Target started (Focus Field 10, HIP 49253) 20:41:07       Dome Unparked Dome unparked 20:43:26       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 20:46:06       Focusing Completed Foc1 AutoFocus Completed (Profile No 1, wide) 20:48:30       Focusing Completed Foc1 AutoFocus Completed (Profile No 1) 20:48:34       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 20:50:46       Focusing Completed Foc2 AutoFocus Completed (Profile No 2, wide) 20:52:39       Focusing Completed Foc2 AutoFocus Completed (Profile No 2) 20:52:58     Target Completed (NrZen) Target completed (Focus Field 10, HIP 49253) 20:54:12     Target Started (1/24) Target started (1/24, GCVS DX Cnc) 20:58:02       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 21:03:58     Target Completed Target completed (1/24, GCVS DX Cnc) 21:05:24     Target Started (2/24) Target started (2/24, ESO 565-G19 w/SN2025efc) 21:11:36       Focusing Skipped Foc1 focusing skipped - unable to find a star (TCF-S) 21:18:14   Critical RainThreat Alert Critical Rain Threat Alert (Obs.Manager will close the Dome) 21:18:16   HardSuspend Called Hard Suspend called due to Critical Conditions (threat of rain) 21:18:21     Target Aborted (2/24) Target aborted (2/24, ESO 565-G19 w/SN2025efc) due to threat of rain 21:18:23   Queue Paused Queue paused for Session Suspension 21:18:25 Session Suspending Session suspending 21:19:15   Dome Closed Dome closed (Closing time 50s, Zigbee 43s) 21:19:16 Session Suspended Session suspended 21:21:19 Session Resuming Session resuming 21:22:04   Dome Opened Dome opened (Opening time 45s, Zigbee 41s) 21:22:07 Session Running Session running 21:22:10   Queue Resumed Observing Queue resumed 21:22:12     Target Started (2/24) Target started (2/24, ESO 565-G19 w/SN2025efc) 21:29:46       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (too few stars) 21:29:55       SoftSuspend Cancelled Soft Suspend is cancelled due to improved conditions 21:32:25     Target Completed Target partially completed (2/24, ESO 565-G19 w/SN2025efc) 21:32:29     Target Started (3/24) Target started (3/24, NGC 2986 w/SN2025gj) 21:33:16       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (too few stars) 21:34:31       SoftSuspend Cancelled Soft Suspend is cancelled due to improved conditions 21:37:11       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (too few stars) 21:39:02   Critical Rain Alert Critical Rain Alert (Obs.Manager will close the Dome) 21:39:04   HardSuspend Called Hard Suspend called due to Critical Conditions (rain) 21:39:06     Target Aborted (3/24) Target aborted (3/24, NGC 2986 w/SN2025gj) due to rain 21:39:08   Queue Paused Queue paused for Session Suspension 21:39:12 Session Suspending Session suspending 21:40:01   Dome Closed Dome closed (Closing time 50s, Zigbee 43s) 21:40:04 Session Suspended Session suspended 21:47:00     Target Cancelled Target cancelled (3/24, NGC 2986 w/SN2025gj) due to threat of rain 21:49:42 Session Resuming Session resuming 21:50:27   Dome Opened Dome opened (Opening time 45s, Zigbee 41s) 21:50:30 Session Running Session running 21:50:33   Queue Resumed Observing Queue resumed 21:50:35     Target Started (4/24) Target started (4/24, AT2025lr) 21:54:59       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 21:57:39       Focusing Completed Foc1 AutoFocus Completed (Profile No 3) 22:14:16     Target Completed Target completed (4/24, AT2025lr) 22:14:20     Target Started (5/24) Target started (5/24, M86) 22:17:40   Critical Rain Alert Critical Rain Alert (Obs.Manager will close the Dome) 22:17:42   HardSuspend Called Hard Suspend called due to Critical Conditions (rain) 22:17:44     Target Aborted (5/24) Target aborted (5/24, M86) due to rain 22:17:46   Queue Paused Queue paused for Session Suspension 22:17:48 Session Suspending Session suspending 22:18:35   Dome Closed Dome closed (Closing time 49s, Zigbee 43s) 22:18:38 Session Suspended Session suspended 22:31:40     Target Cancelled Target cancelled (5/24, M86) due to too few stars 22:31:42 Session Resuming Session resuming 22:32:27   Dome Opened Dome opened (Opening time 45s, Zigbee 41s) 22:32:30 Session Running Session running 22:32:32   Queue Resumed Observing Queue resumed 22:32:35     Target Started (6/24) Target started (6/24, AT2025euu) 22:38:25       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 22:39:19       Focusing Failed Foc1 focusing failed - star lost 22:55:52     Target Completed Target completed (6/24, AT2025euu) 22:56:44     Target Started (7/24) Target started (7/24, LEDA 2155454 w/SN2025erh) 23:00:50       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:03:47       Focusing Completed Foc1 AutoFocus Completed (Profile No 5) 23:14:56       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (reducing clarity) 23:20:03     Target Completed Target completed (7/24, LEDA 2155454 w/SN2025erh) 23:20:05   Queue Paused Queue paused for Session Suspension 23:20:07 Session Suspending Session suspending 23:20:57   Dome Closed Dome closed (Closing time 50s, Zigbee 44s) 23:20:58 Session Suspended Session suspended 23:38:20     Target Cancelled Target cancelled (8/24, UGC 5695 w/SN2025cfc) due to cloud 00:00:40     Target Cancelled Target cancelled (9/24, NGC 3277 w/SN2025coe) due to cloud 00:05:27 Session Resuming Session resuming 00:06:11   Dome Opened Dome opened (Opening time 45s, Zigbee 41s) 00:06:15 Session Running Session running 00:06:17   Queue Resumed Observing Queue resumed 00:06:19     Target Started (10/24) Target started (10/24, M99) 00:10:04       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 00:27:08     Target Completed Target completed (10/24, M99) 00:27:12     Target Started (11/24) Target started (11/24, UGC 8239 w/SN2025N) 00:30:32       Focusing Skipped Foc1 focusing skipped - unable to find a star (TCF-S) 00:46:41     Target Completed Target completed (11/24, UGC 8239 w/SN2025N) 00:48:25     Target Started (12/24) Target started (12/24, NGC 5957 w/SN2025fvw) 00:51:58       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:54:52       Focusing Completed Foc1 AutoFocus Completed (Profile No 6) 01:11:30     Target Completed Target completed (12/24, NGC 5957 w/SN2025fvw) 01:11:34     Target Started (13/24) Target started (13/24, T CrB) 01:14:52       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:17:28       Focusing Completed Foc1 AutoFocus Completed (Profile No 7) 01:22:53     Target Completed Target completed (13/24, T CrB) 01:22:57     Target Started (14/24) Target started (14/24, 29P/Schwassmann-Wachmann) 01:27:06       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 01:43:40     Target Completed Target completed (14/24, 29P/Schwassmann-Wachmann) 01:43:44     Target Started (15/24) Target started (15/24, AT2025lc (CV)) 01:47:37       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:50:13       Focusing Completed Foc1 AutoFocus Completed (Profile No 8) 01:56:30     Target Completed Target completed (15/24, AT2025lc (CV)) 01:56:34     Target Started (16/24) Target started (16/24, AT2025md (CV)) 01:59:35       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:02:21       Focusing Completed Foc1 AutoFocus Completed (Profile No 9) 02:09:51     Target Completed Target completed (16/24, AT2025md (CV)) 02:09:56     Target Started (17/24) Target started (17/24, 61 Cyg) 02:13:17       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 02:15:05     Target Completed Target completed (17/24, 61 Cyg) 02:15:09     Target Started (18/24) Target started (18/24, AT2025la) 02:19:09       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-S) 02:35:12     Target Completed Target completed (18/24, AT2025la) 02:37:11     Target Started (19/24) Target started (19/24, GCVS BL Lac) 02:41:03       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:43:45       Focusing Completed Foc1 AutoFocus Completed (Profile No 10) 02:48:07     Target Completed Target completed (19/24, GCVS BL Lac) 02:48:11     Target Started (20/24) Target started (20/24, M31 w/AT2025etj) 02:52:25       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 03:09:30     Target Completed Target completed (20/24, M31 w/AT2025etj) 03:09:49     Target Started (21/24) Target started (21/24, AT2025esy) 03:13:47       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 03:27:04   SBIG Camera Take Image failed (Command timed-out) 03:27:06   CCDSoft Restarting CCDSoft being restarted (attempt to fix locked thread) 03:27:13   SBIG Camera Reset SBIG Camera being power-cycled 03:28:08   Camera1 Connected SBIG Camera connected (Set point -25°C) 03:28:11   SBIG Camera Take Image command accepted (bSbigDriverException flag is reset) 03:31:25     Target Completed Target completed (21/24, AT2025esy) 03:32:09     Target Started (22/24) Target started (22/24, HIP 87937) 03:47:58     Target Completed Target completed (22/24, HIP 87937) 03:48:02     Target Started (23/24) Target started (23/24, C/2023 A3 (Tsuchinshan-ATLAS)) 03:58:03     Target Completed Target partially completed (23/24, C/2023 A3 (Tsuchinshan-ATLAS)) 03:58:07     Target Started (24/24) Target started (24/24, AT2025esx) 04:19:27     Target Completed Target completed (24/24, AT2025esx) 04:19:29   Queue Completed Job Queue completed 04:19:32 Session Closing Session closing 04:20:28   Dome Closed Dome closed (Closing time 50s, Zigbee 44s) 04:21:11   Dome Parked Dome parked (parking time 35s), Az: 90.0 deg 04:21:49   Telescope Parked Telescope parked (parking time 30s total) 04:22:13   Telescope State Handbox reads 'Scope parked Turn scope off.' 04:22:35   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 04:24:00   Services Stopped Night Services stopped 04:24:02 Session Finishing Session Finishing started (Create Fits Summary, Transfer Files) 04:24:35     Dome (Find Park) Find Park started (Search Az 88.0 to 92.0°, Step 0.2°, Narrow) 04:25:20     Dome Find Park found (Best Park Az 90.4°) 04:25:26     Dome Dome has been synced at park position (Az 90.0°, Adjustment: -0.4°) 04:25:28   Dome Parked Dome parked 04:27:18   Dome Charging Dome is parked and re-charging Ok (26mA) 04:27:20 Session Finished Session Finished

Session Alerts & Alarms

Time     Type       Name Detail 21:39:26 Red Alarm Dome Unsafe CloudSensor detects Rain, but Shutter Sensor is open 21:39:57 Green Clear Dome Safe Shutter Sensor indicates that Dome is now closed 03:27:04 Red Alert SBIG Camera Alert Take Image failed (Command timed-out) 03:28:11 Green Clear SBIG Camera Take Image command accepted (bSbigDriverException flag is reset) 04:27:18 Green Clear Dome Charging Dome is parked and re-charging Ok (26mA)

Back to Top

Operational Issues (2025-03-28, S1306)

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

[ Prev | Next ]

Critical Issues

• None

Major Issues

• An unexpected power cut affected the Observatory (2025-03-30 09:00).  There was another power cut to Observatory today, 2025-03-30 at 09:00, at almost the same time as the power cut yesterday (2025-03-29 08:58). Again the power cut was due to a particular circuit in the house tripping.  This is the one serving kitchen appliances, garage & the observatory.   This cut was noticed until 11:09 when it was noted that the kitchen fridge was off, and the circuit had tripped on the supply board. The circuit was reset which restored power to the kitchen appliances and presumably to the Observatory as well. Remote connection to AllSky/Weather Computer show that power to the AllSky/Weather Computing Bay went off at 09:00:30 and its UPS Battery became fully drained over the course of the next hour and output turned off at 10:01:50.  AllSky/Weather Computer had continued to function on battery and it was still operating at 11:09:06 when power was restored.. Services had recovered,  except for ObsEnv (due to Observatory Computer stopping) . Weather Station data in AstroWeather showed a reg flag but this is likely due to DST Change Issue. The Observatory Computer wasn't connectable via VNC, which is likely due to the Computer's Battery having become drained and the computer going into hibernation. A visit to the Observatory showed that the Observatory Computer had indeed hibernated prior to the Power being restored. The Computer was started up from hibernation (~ 12:38) and after restoring UPB & TCF-S Focuser services, the computer logs & records were examined. These showed that the Power Outage began at 09:00:30, that the UPS Output turned off at 10:12:40, and Observatory Computer hibernated at around 10:33.   Although the time (9:00) corresponds to a change in Night Date and used to define a new general session there are no particular hardware/services that are brought online at that time in the Observatory, and the source of the trip is likely within the house. It is conjectured that the tripping of the particular power circuit is caused by the gas boiler electronics getting a signal to start to the gas boiler for increasing radiator heating at a set time.  The circuit tripped again at 16:43:48 and after turning off the Gas Boiler's Thermostat / Timer Controller the circuit was reset at 16:48:25.  Situation will be monitored. Turning on the Timer Controller again at 20:10 in the evening led to the attempted activation of the gas boiler / radiator heating and caused the associated power circuit to immediately trip, proving that the gas boiler is the root cause for the power-cuts to the Observatory. Circuit was quickly reset meaning that outage to Observatory lasted only 90s. Aberdeen Boiler Company will be contacted on Monday morning  (2025-03-31) to come out and repair the boiler.
  Power Restored 2025-03-30  (Observatory, Power Supply, Gas Boiler)

Minor Issues

• A red 'Dome Unsafe' alert was raised with message "CloudSensor detects Rain, but Shutter Sensor is open" (21:39).  During live session a red ''Dome Unsafe' alert was raised at 21:39:26 with the message "CloudSensor detects Rain, but Shutter Sensor is open". This was followed by a green all-clear alert at 21:39:57 with the message "Shutter Sensor indicates that Dome is now closed".  During Target 3/24 (NGC 2986 w/SN2025gj ) a SoftSuspend Flag was raised at 21:37:11 after Star Count fell to 10 (below the active threshold of 18 stars) with Clarity at a value of 26.3. Before the Target finished (which would have triggered a suspension of SoftSuspend flag was still raised), a Critical Rain Conditions alert was raised due to Rain Sensor detecting rain (2.3) and a hard suspend was called at 21:39:02. The Shutter began closing at 21:39:13 and was fully closed at 21:39:56.  It was during the closure of the dome shutter that the red-alert was correctly raised, with the green-alert correctly raised when the dome closure was completed.  Night Summary plot and AllSky Image covering the time of this rain event at 21:39 is shown in Fig 1 & Fig 2. It would seem that rain event comprised a few drops of rain coming from the tail end of some relatively minor passing cloud. The NightSummary plot shows a very minor rain event at around 21:20 and a short shower at 22:17.  The possibility of minor rain was indicated in OpenWeather API  Minutely Forecast beforehand (with the session suspending from 21:19 to 21:21 due to threat of rain) and again later on, but there was no 'Threat Of Rain' warning at the time of the rain event. Critical Rain Conditions were also detected with rain at 2.2 (clarity 27.6, stars 36) and a hard suspend was called at 22:17:40 which lead to the Observatory Closing between 22:17:47 & 22:18:31).  An AllSky Image covering the time of the rain event at 21:19 is shown in Fig 3 This didn't result in a Dome Unsafe alert (even though situation was essentially the same as the rain event at 21:39.  An AllSky Image covering the time of the rain event at 22:17 is shown in Fig 4. With the thresholds in place the Observatory reacted as quickly as it could in response to the detection of rain by the rain sensor at 21:39.  An outstanding continuous improvement ticket that calls for the addition of a second 'Too few stars' threshold that would lead to a Hard Suspend rather than simply a SoftSuspend but this hasn't been implemented yet. This improvement would have allowed the session to be suspended a couple of minutes earlier in case of 21:39 event, but this would not have led to an earlier suspension in the case of the 22:17 event.  A second TooFewStars threshold field to enable the forcing of a hard suspend has been added to AstroMain 3.74 (2025-03-30).
  Closed after review 2025-03-29 (Observatory, AstroMain, CloudSensor)
   
• Guiding was relatively poor during session  DGuiding was relatively poor during the session, as shown by Guiding Performance chart above, with several targets have av guiding error > 5 arc secs (black points).  Investigating show that passing cloud causing seeing problems and lost star events is the main culprit. Issue closed after review on 2025-03-29.
  Closed after review 2025-03-29 (Session, Guding)
   
• An unexpected power cut affected the Observatory (2025-03-29 08:58). Whilst checking the Observatory Status in the morning  following the live session the previous night, it was noted at around 09:02 that multiple systems were showing up with white traffice lights indicating an outage of the several pieces of observatory hardware & service. Investigating showed that power to the Observatory Computer and AllSky/Weather Computer was out and that they were both on battery and that other systems UPS Systems were operating on battery.  The outage began at 08:53:57 and Outage Management had automatically turned off Dew Heaters, Camera & TCF-S Focuser (Scope was already turned off).  Investigating further showed the electricity circuite serving the garage and observatory had tripped for some reason.   The circuit was reset by the user and power to the Observatory was restored at 09:09:17 (outage 15.3 minutes).  AstroMain running on the Observatory Computer went through steps to recover after the power cut. 
  A separate ticket is raised in connection with the reconnection of the CCD Camera during the Recovery Steps.  The same issue occurred the following day (2025-03-30 09:00), and is recorded above as a Major Issue.
  Resolved 2025-03-29 (Observatory, Power Supply) and underlying cause is still of concern.
   
• Weather Data is red-flagged in AstroWeather and is showing as being out-of-date by 60mins (2025-03-30).  Given that clocks came forward by 1 hour last night this is almost certainly a DST Issue. This is the first clock change since installing the Ekowitt Weather Station and given that CumulusMX Dashboard (at http://localhost:8998/)  is showing data ok and has the correct current time, the issue is most-likely due to a data parsing flaw in AstroWeather. The realtimegauges.txt produced by CumulusMX has a UT date/time, and these are compiled into Ws_yyyy_mm.dat data files by AstroWeather which likewise contain UT date/times.  Graphs produced by AstroWeather/Create Graphs appear to correctly interpret and use the date/time in these data files, but the realtime data interpretor in AstroWeather evidentally doesn't. Fixed in AstroWeather 1.27.6, The date/times displayed and used for calculating data age are converted to local date/time using Datetime's  .ToLocalTime function.
  Fixed 2025-03-30  (AstroWeather 1.27.6, DST Issue) 
   
• Weather Data is white-flagged in AstroMain's ObsViewer window (2025-03-30 13:58).  Given that clocks came forward by 1 hour last night this is possibly but not necessarily a DST Issue. Last night was the first clock change since installing the Ekowitt Weather Station and given that CumulusMX Dashboard (at http://localhost:8998/) is showing data ok and has the correct current time, the issue is most-likely due to a data parsing flaw in AstroWeather or AstroMain.  The flags remained green flagged through the change in clock time and only became white flagged at 16:47 when AstroMain was restarted following an unhandled exception/crash at 15:31.  The problem wasn't expressed on the Development Computer which showed an ObsViewer window with the Weather Station related items green-flagged.  Both computers show the same weather station values.  AstroMain was restarted again on the Observatory Computer and this time it show the items as green flagged.  Issue closed after review and the problem couldn't be recreated, and is put down as a one-off unexplained glitch.
  Closed after review 2025-03-30  (Session, AstroMain, AstroWeather) 
   
• SAM View application isn't displaying or logging magnetometer data from SAM III system.  During indoor testing of SAM Magnetometers & SAM III system on the Development Computer it was found that the SAM View isn't displaying or logging any magnetometer data, even though SAM III is actively reading the 3 magnetometers, a Serial Port Monitor confirms that data records are being set every few seconds over COM4 Port and SAM View is setup to log data from COM4. SAM INI works to download and upload parameters to the SAM III unit. Contacted Whitham Reeve regarding the issue and found that I need to create a shortcut to the 'SAM_View_v2-8.exe' executable and use a log switch. Setting Target of shortcut to
    "C:\More Programs\SAM\SAM_View_v2-8.exe" log,  as described on p.25 of the software guide ("SAM3SoftwareSetup.pdf")
  and then using the shortcut to start SAM_View now enables logging and display of realtime magnetometer data.
  Fixed  2025-03-30  (SAM III, SAM View) 

Small Defects

• AstroMain crashed (2025-03-30 15:31). AstroMain crashed due to a unhandled exception. Just in Time debugging in VisualStudio indicated that problem related to a System.ArgumentException exception 'Parameter is not valid' which wasn't handled. It wasn't possible to ascertain what the parameter was and what code line it occured on as the Application was in Break Mode.  Visual Studio seemed to suggest that it occured in external code and gave the following Stack Trace
   StackTrace:
  at System.Drawing.Graphics.GetHdc()
  at System.Windows.Forms.Internal.WindowsGraphics.FromGraphics(Graphics g, ApplyGraphicsProperties properties)
  at System.Windows.Forms.ControlPaint.DrawFrameControl(Graphics graphics, Int32 x, Int32 y, Int32 width, Int32 height, Int32 kind, Int32 state, Color foreColor, Color backColor)
  at System.Windows.Forms.ControlPaint.DrawCheckBox(Graphics graphics, Int32 x, Int32 y, Int32 width, Int32 height, ButtonState state)
  at System.Windows.Forms.ControlPaint.DrawCheckBox(Graphics graphics, Rectangle rectangle, ButtonState state)
  at System.Windows.Forms.ButtonInternal.CheckBoxBaseAdapter.DrawCheckBox(PaintEventArgs e, LayoutData layout)
  at System.Windows.Forms.ButtonInternal.CheckBoxStandardAdapter.PaintUp(PaintEventArgs e, CheckState state)
  at System.Windows.Forms.ButtonBase.OnPaint(PaintEventArgs pevent)
  at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer)
  at System.Windows.Forms.Control.WmPaint(Message& m)
  at System.Windows.Forms.Control.WndProc(Message& m)
  at System.Windows.Forms.ButtonBase.WndProc(Message& m)
  at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
  Log files indicates that ObsManager, Obs Work, ObsMonitor and UI were all frozen. These seemed to all become frozen at the same time (15:31:54) following an exception in RunPulsarDomeMonitor at 15:31:53.25 with the message "Insufficient system resources exist to complete the requested service".  It is possible that the problem relates to the Pulsar Dome Log reaching a certain large size or a row number parameter exceeding it type allowance. Unable to take the issue any further it was decided to close the ticket after review and monitor for any future occurances.
  Closed after review 2025-03-30 (AstroMain, Session, Observatory Computer)
   
• Following a power outage the CCD Camera was unexpected reconnected by AstroMain's Post-Outage Recovery Routines (2025-03-29 09:10). A power outage to the Observatory occurred between 08:53 and 09:09. At the time of the outage the SBIG CCD Camera wasn't connected, having been disconnected earlier at 04:53 when the S1306 session was closed. After power to the Observatory was restored at 09:09:17,  AstroMain's ObsManager went through steps to check/restore connections/services following power outage. As part of this the SBIG Camera was reconnected at 09:10:16.  Even though the logs show Temperture Regulation being turned on at 09-10:18 with set point temperature at -20°C, temperature regulation was turned off less than a second later. Subsequent ObsPics show the Cam1 CCD camera connected (but with cooling off). Given that Camera was disconnected prior to the outage, it wouldn't be expected that AstroMain would then connect the Camera after the outage ended (other than to check that the SBIG Camera is operating correctly as a check. User disconnected the camera using AstroMain Disconnect Camera button at 09:30. Review what the correct course of action should be in this situation, and update AstroMain ObsManager's 'Recover after PowerCut' logic as appropriate.
  To review 2025-03-29 (AstroMain ObsManager)

Continuous Improvement

• Add 'Serial Port Monitor' as a support app that can be launched from AstroLaunch. Add a 'Serial Port Monitor' button to AstroLaunch/Support Apps Tab that will allow 'serialportmon.exe' (C:\More Programs\SerialPort Monitor) to be started. Implemented in AstroLaunch 1.11.16.  Serial Port Monitor also added to Observatory and AllSky Computers to allow the app to be started there.
  Done 2025-03-30  (AstroLaunch 1.11.16) 
   
• Add 'SAM INI' and 'SAM View'  as support apps that can be launched from AstroLaunch. Add  'SAM INI' & 'SAM View' buttons to AstroLaunch/Support Apps Tab that will allow SAM applications to be started. . Implemented in AstroLaunch 1.11.16.  In due course SAM View will probably be transferred to the Observatory Tab..
  Done 2025-03-30  (AstroLaunch 1.12) 
   
• Add 'AstroMag' as software that can be launched from AstroLaunch/Observatory. Add AstroMag to list of software that can be launched from AstroLaunches/Observatory Tab.  Implemented in AstroLaunch 1.12. 
  Done 2025-03-30  (AstroLaunch 1.12)

[ Prev | Next ]

[ Prev | Next ]

Back to Top