David's Astronomy Pages Notes - Session 1313 (2025-04-09)

Notes (S1312)

Notes Main

Home Page

Notes (S1314)

	Session Aims & Highlights
	- Observing Result  - Night Summary Plot  - Session Event Log
	Operational Issues
	- Critical Issues (0),  Major Issues (0),  Minor Issues (4),  Small Defects (5),  Continuous Improvement (2)
	- Figures (2)
	Images from 2025-04-09 >>

Session Aims & Highlights (2025-04-09)

Main aims

1. Targets.  Acquire images of a selection of variable stars, nearby stars, comets & deep sky targets as allowed by sky conditions.
2. C/2025 F2 (SWAN). Acquire images of new comet C/2025 F2 (SWAN)

 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.74.5,  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.6
  AstroWeather 1.27.5, AstroAllSky 3.23.1,  AstroObsCam 1.11.4 (not 1.11.5), AstroColorCam 1.2.2, AstroLaunch 1.12.2

Highlights

• Targets. 22/24 planned target observations were completed along with 1 ToO target (C/2025 F2 (SWAN) ). 1 target failed due to CCDCamera issue (GCVS RZ LMi) and 1 target failed due to its time slot being replaced by the ToO target.
•   Dome. There was no issues opening/closing the shutter during the session. Dome closed and parked at end of session Ok.

Notes

• DRichards995
  
  

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 21:06:35 Session Monitoring AutoStart monitoring for Live Session opportunity between 21:06 & 03:59 21:06:39   AutoStart Delayed Session delayed due to too few stars 21:35:32 Session AutoStarting Session autostarting (21:35) 21:35:53   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.) 21:36:21   Camera1 Connected SBIG Camera connected (Set point -20°C) 21:36:24 Session Created Session Created (Live, 2025-04-09 S01313, ImageSaveNum: 1313001) 21:36:29   Scope Switched On Telescope Power has been switched on via UPB Powerbox. 21:38:16   Services Started Observatory Services started 21:38:24 Observatory (Auto) Observatory placed in Fully-Automated Mode 21:38:26   AutoStart Delayed Session delayed due to too few stars 21:38:27 Session Pending Session pending (2025-04-09) 21:38:29 Session Initiating Session initiating (2025-04-09) 21:38:39   Camera1 Connected SBIG Camera connected (Set point -20°C) 21:38:41   Plan Requested Observing Plan requested from AstroPlan (1.43) 21:39:08   Plan Loaded Observing Plan loaded to queue (Plan ID: 1097) 21:39:48   Telescope Connected Telescope connected (TheSky6) 21:40:12 Session Equilibration Session ready to Open Dome 21:40:57   Dome Opened Dome opened (Opening time 45s, Zigbee 41s) 21:41:42 Session Running Session running 21:41:45   Queue Started Observing Queue started (24 targets selected) 21:41:48     Target Started (NrZen) Target started (Focus Field 10, HIP 49253) 21:42:03       Dome Unparked Dome unparked 21:46:21   CcdCamera Frozen CcdCamera appears to be frozen at around 21:46 in section 'GetCameraProperties / CoolerPower' 21:46:57   CCDSoft Restarting CCDSoft being restarted (attempt to fix frozen CcdCamera) 21:47:04   SBIG Camera Reset SBIG Camera being power-cycled 21:47:59   Camera1 Connected SBIG Camera connected (Set point -20°C) 21:49:15   SBIG Camera Take Image failed (Command timed-out) 21:49:42       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 21:58:50       Focusing Failed Foc2 focusing failed (failed QC check - Range) 21:58:53     Target Completed (NrZen) Target completed (Focus Field 10, HIP 49253) 21:59:07     Target Started (1/24) Target started (1/24, GCVS RZ LMi) 22:00:34   SBIG Camera Take Image command accepted (bSbigDriverException flag is reset) 22:01:06   SBIG Camera Take Image failed (Command timed-out) 22:01:23   CCDSoft Issue CCDSoft has encountered an image save issue [0000] 22:01:26   CCDSoft Restarting CCDSoft being restarted (attempt to fix unsaved file issue) 22:01:33   SBIG Camera Reset SBIG Camera being power-cycled 22:02:27   Camera1 Connected SBIG Camera connected (Set point -20°C) 22:02:36   SBIG Camera Take Image command accepted (bSbigDriverException flag is reset) 22:07:12       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 22:10:21       Focusing Completed Foc1 AutoFocus Completed (Profile No 1, wide) 22:12:33       Focusing Completed Foc1 AutoFocus Completed (Profile No 1) 22:12:38     Target Failed (1/24) Target failed due to other condition - ExceededTimeSlot (1/24, GCVS RZ LMi) 22:12:42     Target Started (2/24) Target started (2/24, AT2025gnb) 22:32:42     Target Completed Target completed (2/24, AT2025gnb) 22:32:46     Target Started (3/24) Target started (3/24, GCVS SY Cnc) 22:39:57     Target Completed Target completed (3/24, GCVS SY Cnc) 22:40:02     Target Started (4/24) Target started (4/24, 29P/Schwassmann-Wachmann) 22:43:33       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 22:45:58       Focusing Completed Foc1 AutoFocus Completed (Profile No 2) 23:01:07     Target Completed Target completed (4/24, 29P/Schwassmann-Wachmann) 23:01:11     Target Started (5/24) Target started (5/24, LEDA 2155454 w/SN2025erh) 23:04:30       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:07:26       Focusing Completed Foc1 AutoFocus Completed (Profile No 3) 23:23:53     Target Completed Target completed (5/24, LEDA 2155454 w/SN2025erh) 23:23:57     Target Started (6/24) Target started (6/24, AT2025ghv) 23:27:51       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:30:47       Focusing Completed Foc1 AutoFocus Completed (Profile No 4) 23:47:24     Target Completed Target completed (6/24, AT2025ghv) 23:47:28     Target Started (7/24) Target started (7/24, GCVS ER UMa) 23:50:54       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:53:47       Focusing Completed Foc1 AutoFocus Completed (Profile No 5) 23:57:50     Target Completed Target completed (7/24, GCVS ER UMa) 23:57:54     Target Started (8/24) Target started (8/24, AT2025md (CV)) 00:02:01       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:04:30       Focusing Completed Foc1 AutoFocus Completed (Profile No 6) 00:11:05     Target Completed Target completed (8/24, AT2025md (CV)) 00:11:09     Target Started (9/24) Target started (9/24, AT2024ger) 00:30:46     Target Completed Target completed (9/24, AT2024ger) 00:30:51     Target Started (10/24) Target started (10/24, LEDA 2243580 w/SN2025gp) 00:34:20       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:37:07       Focusing Completed Foc1 AutoFocus Completed (Profile No 7) 00:53:57     Target Completed Target completed (10/24, LEDA 2243580 w/SN2025gp) 00:54:01     Target Started (11/24) Target started (11/24, AT2025gsf) 00:57:26       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:00:23       Focusing Completed Foc1 AutoFocus Completed (Profile No 8) 01:17:02     Target Completed Target completed (11/24, AT2025gsf) 01:17:06     Target Started (12/24) Target started (12/24, MCG -3-35-3 w/SN2023hjq) 01:38:30     Target Completed Target completed (12/24, MCG -3-35-3 w/SN2023hjq) 01:38:34     Target Started (13/24) Target started (13/24, AT2024evp) 01:43:03       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:45:11       Focusing Completed Foc1 AutoFocus Completed (Profile No 9) 02:02:23     Target Completed Target completed (13/24, AT2024evp) 02:02:27     Target Started (14/24) Target started (14/24, T CrB) 02:10:28     Target Completed Target completed (14/24, T CrB) 02:10:32     Target Started (15/24) Target started (15/24, NGC 5957 w/SN2025fvw) 02:14:50       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:17:42       Focusing Completed Foc1 AutoFocus Completed (Profile No 10) 02:34:35     Target Completed Target completed (15/24, NGC 5957 w/SN2025fvw) 02:34:39     Target Started (16/24) Target started (16/24, UGC 10058 w/SN2025gvs) 02:38:03       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:40:28       Focusing Completed Foc1 AutoFocus Completed (Profile No 11) 02:57:16     Target Completed Target completed (16/24, UGC 10058 w/SN2025gvs) 02:57:20     Target Started (17/24) Target started (17/24, HIP 87937) 02:59:34       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:01:49       Focusing Completed Foc1 AutoFocus Completed (Profile No 12) 03:05:20     Target Completed Target completed (17/24, HIP 87937) 03:05:24     Target Started (18/24) Target started (18/24, AT2024aapf) 03:08:59       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:11:27       Focusing Completed Foc1 AutoFocus Completed (Profile No 13) 03:27:48     Target Completed Target completed (18/24, AT2024aapf) 03:27:52     Target Started (19/24) Target started (19/24, 61 Cyg) 03:30:07       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:32:15       Focusing Completed Foc1 AutoFocus Completed (Profile No 14) 03:34:21     Target Completed Target completed (19/24, 61 Cyg) 03:34:25     Target Started (20/24) Target started (20/24, GCVS BL Lac) 03:37:34       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:40:09       Focusing Completed Foc1 AutoFocus Completed (Profile No 15) 03:44:52     Target Completed Target completed (20/24, GCVS BL Lac) 03:44:56     Target Started (21/24) Target started (21/24, GCVS AM Her) 03:48:15       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:50:45       Focusing Completed Foc1 AutoFocus Completed (Profile No 16) 03:56:30     Target Completed Target completed (21/24, GCVS AM Her) 03:56:35     Target Started (22/24) Target started (22/24, AT2025lc (CV)) 03:59:55       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 04:02:29       Focusing Completed Foc1 AutoFocus Completed (Profile No 17) 04:09:21     Target Completed Target completed (22/24, AT2025lc (CV)) 04:09:25     Target Started (23/24) Target started (23/24, GCVS SS Cyg) 04:12:41       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 04:14:40       Focusing Completed Foc1 AutoFocus Completed (Profile No 18) 04:20:22     Target Completed Target completed (23/24, GCVS SS Cyg) 04:20:26     Target Started (24/25) Target started (24/25, C/2025 F2 (SWAN), ToO) 04:24:42       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 04:27:18       Focusing Completed Foc1 AutoFocus Completed (Profile No 19) 04:48:01     Target Completed Target completed (24/25, C/2025 F2 (SWAN), ToO) 04:48:05     Target Started (25/26) Target started (25/26, C/2025 F2 (SWAN), ToO) 04:51:16       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 04:53:46       Focusing Completed Foc1 AutoFocus Completed (Profile No 20) 05:13:03     Target Completed Target completed (25/26, C/2025 F2 (SWAN), ToO) 05:13:05     Target Missed (26/26) Target's time slot was missed (26/26, UGC 12293 w/AT2025gyi) 05:13:07   Queue Completed Job Queue completed 05:13:09 Session Closing Session closing 05:14:02   Dome Closed Dome closed (Closing time 50s, Zigbee 43s) 05:14:24   Dome Parked Dome parked (parking time 13s), Az: 90.0 deg 05:15:17   Telescope Parked Telescope parked (parking time 48s total) 05:15:53   Telescope State Handbox reads 'Scope parked Turn scope off.' 05:16:15   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 05:17:40   Services Stopped Night Services stopped 05:17:43 Session Finishing Session Finishing started (Create Fits Summary, Transfer Files) 05:18:25     Dome (Find Park) Find Park started (Search Az 88.0 to 92.0°, Step 0.2°, Narrow) 05:19:14     Dome Find Park found (Best Park Az 90.5°) 05:19:19     Dome Dome has been synced at park position (Az 90.0°, Adjustment: -0.5°) 05:19:22   Dome Parked Dome parked 05:22:23   Dome Charging Dome is parked and well charged (95%, 14.9v 05:22:25 Session Finished Session Finished

Session Alerts & Alarms

Time     Type       Name Detail 21:46:55 Red Alert CcdCamera CcdCamera appears to be frozen (last cycle at 21:46:21) in section 'GetCameraProperties / CoolerPower' 21:49:15 Red Alert SBIG Camera Alert Take Image failed (Command timed-out) 22:00:34 Green Clear SBIG Camera Take Image command accepted (bSbigDriverException flag is reset) 22:01:06 Red Alert SBIG Camera Alert Take Image failed (Command timed-out) 22:01:23 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 22:02:36 Green Clear SBIG Camera Take Image command accepted (bSbigDriverException flag is reset) 22:03:32 Green Clear CCDSoft Image file has been saved to disk following CCDSoft Restart 05:22:23 Yellow Alert Dome Charging Dome is parked and well charged (95%, 14.9v

Back to Top

Operational Issues (2025-04-09, S1313)

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

[ Prev | Next ]

Critical Issues

• None

Major Issues

• None

Minor Issues

• Near Zenith Focusing failed both Telescope/Focus systems (21:42-21:58). Both Foc1 and Foc2 focusing failed, due to CCDSoft/SBIG Camera issue for Foc1 and a SharpCap issue for Foc2. These will be investigated separately. Fortunately both telescope/focus systems were sufficiently well focused based on previous session focus offsets that it didn't effect the session unduly.
  Closed 2025-04-09 (Session, AstroMain, SharpCap)
   
• Red 'CCDCamera' alert raised with message "CcdCamera appears to be frozen" (21:46).   A red 'CCDCamera' red alert was raised at 21:46:55 with the message  "CcdCamera appears to be frozen (last cycle at 21:46:21) in section 'GetCameraProperties / CoolerPower' ". Logs show that after successfully taking Locate Frame 1 for Near Zenith Focus Field 10 at 21:44, the alert was raised whilst attempting to take Locate Frame 2 at 21:46, and CCDSoft/SBIG Camera were automatically restarted. Locate Frame 3 was then successfully taken at 21:48 (no jog required).  An attempt to take a Focus Locate Frame at 21:48/21:49 failed due to a timeout with the ObsOverseer message "Camera.TakeImageTask in TakeImage/TakeImage is taking a long time? (21:49)".  No corrective operation was made at this time. Foc1 focusing was skipped and execution moved to Foc2 focusing. A 'Locate_01_wide.fits' was successfully taken by ShCap/SharpCap,  but the progress then stalled with ObsOverseer reporting "AutoFocus Scope2Task in AutoFocusScope2/Start is taking a long time? (21:53)".  This is likely due to CCDSoft being unresponsive at this time or at least running very slowly based on logs showing multiple  "CcdCamera is Pending" and "Obs.Monitor is Pending " message and broken by occasional "CcdCamera has resumed"  and "Obs.Monitor has resumed" messages.  Seeing the problem with Foc2 Focusing the user used backdoor operation to Restart ShCap Service. (This proceeded but was unlikely not neccessary as the problem was with CCDCamera/CCDSoft and not with SharpCap. The Foc2 focusing the proceeded  but no focus results were obtained. The Job Executor then proceeded with Target 1/24 (RZ LMi), but Locate Frame 1 failed. ObsOverseer gave the warning "Camera.TakeImageTask in TakeImage/TakeImage is taking a long time? (22:01)".  and commanded CCDSoft/SBIG Camera to be restarted.   This finally resolved the issue and centering & focusing proceeded successfully, but unfortunately there wasn't time left for Main Images and the target consequentially failed.  If user hadn't intervened to Restart ShCap Service would the Foc2 focussing progress (though unsuccesful) or would execution have been stuck ?
  Automatically resolved in-session 2025-04-09 (Session, AstroMain, SharpCap, User Awareness)
   
• Weather, CloudSensor and Synopsis data went offline (05:40) . Checking Observatory Status in the morning after previous night session showed that there was an outage in Weather Data, Cloud Sensor Data and Synopsis data and that network connection to Laptop 7 (AllSky/Weather Computer) wasn't accessible. General Alerts are shown in Fig 2.  The 'Current Weather webpage' indicated that data upload to the website has stopped at around 05:44. A remote VNC connection to the AllSky/Weather Computer couldn't be made.  A visit to the Observatory showed the AllSky/Weather Computer Screen was off.  Pressing the Power button on the computer brough the computer out of a Sleep State.  Cloud Sensor & Weather Station programs weren't running, but other programs AllSkyAstro, iSpy, AstroCam began activity again (08:27). Examining Synopsis records indicated that the AstroAllSky was running till at 05:53:44 with logfile showing that AstroAllSky stopped logging at 05:44:10 and begun logging again at 08:27:06.  It is unclear what caused the glitch on the AllSky/Weather Computer and when & what caused the CloudSensor & CumulusMX programs to stop running.  Examining the Windows Event log in 'Event Viewer' shows following Events at around this time
    05:44:02 Kernal Power : Critical Battery Trigger Met
  05:44:06 Kernal Power : The system is entering sleep (Sleep Reason: Battery)
  05:44:12 Kernal Power : The system has resumed from sleep  (? finished initiating sleep, rather than 'resumed' ?)
  08:27:06 Kernal-Boot : The firmware reported boot metrics.
  So it is clear that Window thought that the battery had reached a critical level and this caused it to put the computer to sleep at 05:44.  This would seem to be glitch in Windows or the Computer, as there is no indication from Eaton UPS Companion or AstroWeather's Power Monitor that there was a main supply outage or an issue with computer's battery level.  Closed after review 2025-04-10, issue is put down to a computer/windows glitch
  Closed after review 2025-04-10 (Session, AllSky/Weather Computer, Windows, Battery). Continue to monitor.
   
• Weather Station data still offline after restarting CumulusMX (2024-04-10 08:30). Weather Station data remained offline, after bringing Computer out of sleep state and restarting CumulusMX.. Running 'localhost:8998'  shows that last data was at 05:44, and that there was no new data coming through.   Logs show the following
    2025-04-10 08:30:08.428 GetLiveData: Error - Exception Type: System.AggregateException
  Message: One or more errors occurred. (An error occurred while sending the request.)
  Inner Exception...
  Exception Type: System.Net.Http.HttpRequestException
  Message: An error occurred while sending the request.
  Inner Exception...
  Exception Type: System.IO.IOException
  Message: Unable to read data from the transport connection: An established connection was
   aborted by the software in your host machine..
  Inner Exception...
  Exception Type: System.Net.Sockets.SocketException
  Message: An established connection was aborted by the software in your host machine.
  An attempt to use Serial Port Monitor was made to see what the GS2000 was passing to the computer via COM5 but it gave the error dialog "Unable to connect to COM5" suggesting that the port is locked up, probably due to  Window Kernal operation at 05:44 which put the computer to Sleep.  
  Removing / reinserting USB cable to GW2000 unit or turning off/turning on the USB port using Pegasus Hub software, and finally restarting the computer didn't resolve problem. Finally copied /CumulusMX4 directory to a new /CumulusMX5 directory and then started CumulusMX.exe from there.
  (Note.  AstroLaunch's start CumulusMX will be affected by this)
  Resolved 2025-04-10 (Session, AllSky/Weather Computer, COM Port)

Small Defects

• AstroSN seemed to freeze trying to get 'Active SN List'.  AstroSN seemed to get stuck whilst trying to "Read source file" whilst being run on the Development Computer.  A little while later an separate examination of the source file "http://www.rochesterastronomy.org/snimages/snname.html" showed it to be accessible ok via MS Edge browser. AstroSN was run in Visual Studio and it was able to retrieve and process the 'Active SN List' without any issue. Unclear what the initial problem was - maybe a temporary glitch with the server providing rochesterastronomy.org,  internet or LAN. Closed after review 2025-04-09.
  Closed after review 2025-04-09 (AstroSN)
   
• AllSky Session for 205-04-09 wasn't moved to External Drive.  'AllSky 2025-04-09' folders weren't moved to G:/ Drive (2025-04-10). This was due to AllSky/Weather Computer being asleep at the time that 2025-04-09 Night Session ended. Folders were subsequently moved to the G Drive by user. Closed after review 2025-04-10
  Closed after review 2025-04-10 (AllSky/Weather Computer, AstroAllSky)
   
• AstroAllSky log contains multiple messages like "1900-01-01 00:00:00, age=60.30 mins". The '2025-04-09 AllSky (run).log contains multiple message lines like "1900-01-01 00:00:00, age=60.30 mins" (at 05:43:40). The log contains 11253 instances.  The message line seems to follow a 'Trace TeleComms' message line in most  / all cases.  The fact that age is around 60min suggests a DST related issue,  but why "1900-01-01 00:00:00" is given is unclear. Formating of line indicates that a normal log file timestamp suggests that line is written by a 'LogFile.Writeline()' command instead of the normally used 'WriteLogFile()' command. Investigating code indicates that message is associated with logging a WeatherData date issue in the CheckWeatherDataValidity() routine (which is called by GetWeatherData()()).
    With WeatherData
    GetDataAgeX(IV.WeatherDateX, DataAgeMins)
    If DataAgeMins > DataAgeMinsCutoff Then
       ..
       IV.WeatherDateX = vcNullDate
       LogFile.WriteLine(IV.WeatherDateX.ToString("yyyy-MM-dd HH:mm:ss") + ", age=" + FormatNumber(DataAgeMins, 2) + " mins")
    Else
      ..
    End If
  End With
  It is unclear why the routine uses 'GetDataAgeX(IV.WeatherDateX, DataAgeMins)' inside a 'With WeatherData..EndWith block and not use WeatherDate.DateX.  Code shows that calling routine (GetWeatherData() ) sets IV.WeatherDateX = WeatherDate.DateX before calling CheckWeatherDataValidity() so they should be the same value anyway (IV is a global class object)
  It was initially unclear why IV.WeatherDateX seems to have a valid date (though out by 1 hour date) at the GetDataAgeX()  line but has a null date when logged.  but this was found to be due to setting IV.WeatherDateX = vcNullDate after finding DataAge. 
  Fix attempted in AstroAllSky 3.23.2, by using a .ToLocalTime modifier before calling GetDateAgeX and in the logging.  LogFile.WriteLine () changed to a WriteLogFile() call and moved ahead of the vcNullDate setting.  The issue seems to have been causing Weather Information to not be drawn in the Annotation on side of AllSky Images since the clocks changed on Mar 30th.
  Fix attempted 2025-04-10 (AstroAllSky 3.23.2, DST Issue)
   
• AstroWeather produces LastUpdate GraphBox which are incorrect by 1 hour. AstroWeather outputs LastUpdate graph boxes for WeatherStation (Graph 74) and CloudSensor (Graph75).  The times shown are 1 hour less that the times expected (e.g 10:01:50 instead of 11:01:50).  It would seem that the time shown is a UT time and not a Local Time, and that this is a DST Issue, which has begun since clocks moved to British Summer Time (Daylight Savings). Fixed in AstroWeather 1.27.7 by including '.ToLocalTime' command in the line that creates the output date/time.
  Fixed 2025-04-10 (AstroWeather 1.27.7)
   
• 'Cam1 CCD' is red-flagged in AstroMain's Obs Viewer & ObsPics (21:47 to 05:22) .  Cam1 CCD flag turned red at 21:47 and remained red until the end of session when the Camera was turned off. It was also notice that CCD Temperature/Cooling level was shown with null (-99) values in status bar at bottom of AstroMain's main console form.  CCD Temperature, Cooling, Set Point stopped being recorded in Session's Monitor File, which prevented seeing a CCD Temperature chart for the session. Despite this the camera remained functional and images were acquired ok (see Fig 1) and CCD Temperature was recorded in FITS header ok.  These issue would appear to be due to a problem with the Temperature Monitor. It seems that problem began after a CCDSoft/SBIG Camera Restart at 21:47.  The logfile doesn't indicate a problem with the CCD Temperature monitor., though there were other problems recorded concerning CCDCamera/ObsMonitor at 21:46 to 22:00. In particular the log file doesn't record any exceptions in  RunTempMonitor (in neither inner or outer Try.Catch.EndTry blocks).  It is unclear if the issue would have prevented the automated selection of a new set point temperature if temperature conditions changed to keep the CCD regulation / Cooling within a suitable range.  Examining the RunTempMonitor code shows it is responsible for outputting monitoring records the session's 'Observatory (monitor).dat' file and this was output ok proving that the TempMonitor was looping ok, but it began outputting Null values for CCD Temperature and Cooling Power from 21:47 onwards. The loop reads CCD Temperature, CoolerPower & TemperatureSetPoint from corresponding CCDCamera properties, provided that the following conditions are true
    gCameraConnected = True
  bRestartingCCDSoft = False
  bCcdCameraCycleIsPending = False Then ' added bCcdCameraCycleIsPending condition 2024-10-29 (MI S1161A)
  Camera1_IsAccessible() = True
  SU.DemoMode = False
otherwise it uses Null values
Camera1_IsAccessible() only returns True if the following conditions are true
  ( bCamera1TakingImage = false or Now() <= Camera1ExpectedStartDownloadTime)
  bRestartingCCDSoft = False
  bRunningConnectCamera = False
  gCameraConnected = True
  bCcdCameraCycleIsPending = False
  bCcdCameraReportedAsFrozen = False
  The detailed checks are there to prevent CCDCamera / CCDSoft was locking up during critical activity, but the fact that null values were being persistantly used suggests  that the opposing flags state or condition was blocking any calls to read CCDCamera Properties. It is probable that a flag was raised at the time of the camera issues at around 21:47 and didn't become lowered. But which one ?.   There is insufficient data to diagnose the issue further and it hasn't been seen before, the issue is closed after review 2025-04-11. A separate Continuous Improvement ticket has been raised to look into whether the ObsOverseer actually checks the CCD Temperature Monitor for any issues.
  Closed after review 2025-04-11 (Session, AstroMain, ObsOverseer / Monitor)

Continuous Improvement

• Draw an Scope Path segments by interpolating in Az/Alt Space rather than as a simple straight line in X/Y space. The Telescope SlewPath is drawn on Dome/Scope Slew Chart is frequently appears as series of straight line segments, rather than a nice semi-curved path. This is particularly the case where points are widely separated, which is a function of how quickly fresh coordinates can be read from the telescope during a slew. The lines are drawn in XY space and each segment appears as a straight line.  It is thought that this situation could be improved by dividing a segment up into 10 points where Az/Alt values are interpolated in Az/Alt space, and then converted to X/Y space.   This ticket was retrospectively added here on 2025-04-17.  Solution implemented in AstroMain 3.74.6, and tested in session S1316 (2025-04-22, see Result), but may needs further live sessions to confirm this solution has successfully resolves the orginal issue..
  Done 2025-04-17 (AstroMain 3.74.6)
   
• Query.  Does AstroMain's ObsOverseer routine monitor the proper running of the TempMonitor Service.  AstroMain's TempMonitor appear to have stopped running or froze during the S1313 session with 'Cam1 CCD' becoming red-flagged in AstroMain's Obs Viewer & ObsPics (21:47 to 05:22)  and active Monitoring of Cam1 CCD despite the camera running ok and was able to be used to successfully acquire images of targets.  Cam1/  The logfile doesn't indicate a problem with the CCD Temperature monitor., though there were other problems recorded concerning CCDCamera/ObsMonitor at 21:46 to 22:00. There was insufficient data to diagnose the problem further and the issue had to be closed.  Does the ObsOverseer actually checks the CCD Temperature Monitor (TempMonitor) for any issues.   Code checked 2025-07-05 and confirms that Obs.Overseer does indeed check for a frozen TempMonitor and raises a red alert, but beyond it doesn't perform any remedial action (should it ?).
  Done 2025-07-05 (AstroMain, ObsOverseer / TempMonitor)

[ Prev | Next ]

Back to Top Issue,  Back to Top

[ Prev | Next ]

Back to Top Issue,  Back to Top