David's Astronomy Pages Notes - Session 1330 (2025-05-27)

Notes (S1329)

Notes Main

Home Page

Notes (S1331)

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

Session Aims & Highlights (2025-05-27)

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.74.21,  AstroPlan 1.43.9,  AstroShCap 1.3.15, AstroGuard 1.10.6   (any new items or versions in bold)
  AstroMag 1.4.16, AstroVOE 1.15.1,  AstroSN 1.14,  AstroProtect 1.10.6,  AstroMove 1.16
  AstroWeather 1.27.9, AstroAllSky 3.23.8,  AstroObsCam 1.11.4 (not 1.11.5), AstroNorthCam 1.4.2, AstroLaunch 1.13.1

Highlights

• Targets. 5/9 planned target observations were completed, with 2 targets partially completed. Remaining 2 targets at beginning of session failed due to cloud/too few stars
• CCD Camera. There was an issues with the CCDSoft / CCDCamera, but were automatically resolved using RestartCCDSoft operations where applied.
•   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 Plan not created for this session

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 22:40:43 Session Monitoring AutoStart monitoring for Live Session opportunity between 23:28 & 01:30 22:40:48   AutoStart Waiting AutoStart waiting till earliest start time at 23:28 23:28:32   AutoStart Delayed Session delayed due to too few stars 00:02:35 Session AutoStarting Session autostarting (00:02) 00:02:56   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.) 00:03:23   Camera1 Connected SBIG Camera connected (Set point -20°C) 00:03:25 Session Created Session Created (Live, 2025-05-27 S01330, ImageSaveNum: 1330001) 00:03:30   Scope Switched On Telescope Power has been switched on via UPB Switch 00:05:35   Services Started Observatory Services started 00:05:43 Observatory (Auto) Observatory placed in Fully-Automated Mode 00:05:45   AutoStart Delayed Session delayed due to too few stars 00:05:47 Session Pending Session pending (2025-05-27) 00:05:49 Session Initiating Session initiating (2025-05-27) 00:05:57   Camera1 Connected SBIG Camera connected (Set point -15°C) 00:06:04   Plan Requested Observing Plan requested from AstroPlan (1.43.9) 00:07:04   Plan Loaded Observing Plan loaded to queue (Plan ID: 1115) 00:07:45   Telescope Connected Telescope connected (TheSky6) 00:08:11 Session Equilibration Session ready to Open Dome 00:08:56   Dome Opened Dome opened (Opening time 45s, Zigbee 41s) 00:09:06 Session Running Session running 00:09:09   Queue Started Observing Queue started (9 targets selected) 00:09:12     Target Started (NrZen) Target started (Focus Field 15, HIP 73454) 00:09:28       Dome Unparked Dome unparked 00:11:15   SBIG Camera Take Image failed (Command timed-out) 00:14:20       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 00:16:08       Focusing Completed Foc2 AutoFocus Completed (Profile No 1, wide) 00:18:06       Focusing Completed Foc2 AutoFocus Completed (Profile No 1) 00:18:28     Target Completed (NrZen) Target completed (Focus Field 15, HIP 73454) 00:21:33       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (reducing clarity) 00:21:35   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 00:21:37   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 00:21:39   Queue Paused Observing Queue pausing for Session Suspension 00:21:41 Session Suspending Session suspending 00:22:28   Dome Closed Dome closed (Closing time 50s, Zigbee 43s) 00:22:31 Session Suspended Session suspended 00:31:46     Target Cancelled Target cancelled (1/9, GCVS CY Lyr) due to too few stars 00:42:04     Target Cancelled Target cancelled (2/9, GCVS BL Lac) due to too few stars 00:43:20 Session Resuming Session resuming 00:44:05     Target Started (NrZen) Target started (Focus Field 16, HIP 78946) 00:44:07   Dome Opened Dome opened (Opening time 45s, Zigbee 41s) 00:44:09 Session Running Session running 00:44:11   Queue Resumed Observing Queue resumed 00:45:29   CCDSoft Issue CCDSoft has encountered an image save issue [0000] 00:45:31   CCDSoft Restarting CCDSoft being restarted (attempt to fix unsaved file issue) 00:45:38   SBIG Camera Reset SBIG Camera being power-cycled 00:46:30   Camera1 Connected SBIG Camera connected (Set point -15°C) 00:46:53   SBIG Camera Take Image successfully completed (earlier flags are reset) 00:49:12       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:51:54       Focusing Completed Foc1 AutoFocus Completed (Profile No 2, wide) 00:53:49       Focusing Completed Foc1 AutoFocus Completed (Profile No 2) 00:53:51     Target Completed (NrZen) Target completed (Focus Field 16, HIP 78946) 00:53:53     Target Started (3/9) Target started (3/9, IC 4408 w/SN2025kfm) 01:00:44       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:02:52       Focusing Failed Foc1 focusing failed (failed QC check - RmsE) 01:10:12     Target Completed Target partially completed (3/9, IC 4408 w/SN2025kfm) 01:10:16     Target Started (4/9) Target started (4/9, NGC 4395 w/AT2025lwi) 01:32:18     Target Completed Target completed (4/9, NGC 4395 w/AT2025lwi) 01:32:22     Target Started (5/9) Target started (5/9, UGC 10058 w/SN2025gvs) 01:52:16     Target Completed Target completed (5/9, UGC 10058 w/SN2025gvs) 01:52:20     Target Started (6/9) Target started (6/9, T CrB) 01:55:41       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:57:46   SBIG Camera Take Image failed (Command timed-out) 01:57:50   CCDSoft Restarting CCDSoft being restarted (attempt to fix frozen CcdCamera) 01:57:57   SBIG Camera Reset SBIG Camera being power-cycled 01:58:49   Camera1 Connected SBIG Camera connected (Set point -20°C) 01:58:57   SBIG Camera Take Image successfully completed (earlier flags are reset) 01:59:28       Focusing Completed Foc1 AutoFocus Completed (Profile No 4) 02:01:53   SBIG Camera Take Image failed (Command timed-out) 02:02:00   CCDSoft Restarting CCDSoft being restarted (attempt to fix locked thread) 02:02:08   SBIG Camera Reset SBIG Camera being power-cycled 02:02:59   Camera1 Connected SBIG Camera connected (Set point -20°C) 02:03:46   SBIG Camera Take Image successfully completed (earlier flags are reset) 02:05:22     Target Completed Target partially completed (6/9, T CrB) 02:05:26     Target Started (7/9) Target started (7/9, HIP 87937) 02:12:18     Target Completed Target completed (7/9, HIP 87937) 02:12:22     Target Started (8/9) Target started (8/9, AT2025kej (CV)) 02:16:41   SBIG Camera Take Image failed (Command timed-out) 02:16:45   CCDSoft Restarting CCDSoft being restarted (attempt to fix frozen CcdCamera) 02:16:52   SBIG Camera Reset SBIG Camera being power-cycled 02:21:47     Target Completed Target completed (8/9, AT2025kej (CV)) 02:23:56     Target Started (9/9) Target started (9/9, GCVS AM Her) 02:25:22   CCDSoft Issue CCDSoft has encountered an image save issue [0000] 02:25:24   CCDSoft Restarting CCDSoft being restarted (attempt to fix unsaved file issue) 02:25:31   SBIG Camera Reset SBIG Camera being power-cycled 02:26:23   Camera1 Connected SBIG Camera connected (Set point -20°C) 02:26:35   SBIG Camera Take Image successfully completed (earlier flags are reset) 02:28:24       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:30:59       Focusing Completed Foc1 AutoFocus Completed (Profile No 5) 02:34:07   CcdCamera Frozen CcdCamera appears to be frozen at around 02:34 in section 'GetCameraProperties / Status' 02:34:43   CCDSoft Restarting CCDSoft being restarted (attempt to fix frozen CcdCamera) 02:34:50   SBIG Camera Reset SBIG Camera being power-cycled 02:35:42   Camera1 Connected SBIG Camera connected (Set point -20°C) 02:39:14     Target Completed Target completed (9/9, GCVS AM Her) 02:39:16   Queue Completed Job Queue completed 02:39:18 Session Closing Session closing 02:40:11   Dome Closed Dome closed (Closing time 50s, Zigbee 43s) 02:40:51   Dome Parked Dome parked (parking time 33s), Az: 90.0 deg 02:41:40   Telescope Parked Telescope parked (parking time 42s total) 02:42:04   Telescope State Handbox reads 'Scope parked Turn scope off.' 02:42:26   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 02:43:53   Services Stopped Night Services stopped 02:43:56 Session Finishing Session Finishing started (Create Fits Summary, Transfer Files) 02:44:08     Dome (Find Park) Find Park started (Search Az 88.0 to 92.0°, Step 0.2°, Narrow) 02:44:54     Dome Find Park found (Best Park Az 90.2°) 02:45:00     Dome Dome has been synced at park position (Az 90.0°, Adjustment: -0.2°) 02:45:02   Dome Parked Dome parked 02:45:16   Dome Charging Dome is parked and re-charging Ok (10mA) 02:45:18 Session Finished Session Finished

Session Alerts & Alarms

Time     Type       Name Detail 00:11:15 Red Alert SBIG Camera Alert Take Image failed (Command timed-out) 00:45:29 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 00:46:53 Green Clear SBIG Camera Take Image successfully completed (earlier flags are reset) 00:48:05 Green Clear CCDSoft Image file has been saved to disk following CCDSoft Restart 01:57:46 Red Alert SBIG Camera Alert Take Image failed (Command timed-out) 01:58:57 Green Clear SBIG Camera Take Image successfully completed (earlier flags are reset) 02:01:53 Red Alert SBIG Camera Alert Take Image failed (Command timed-out) 02:03:46 Green Clear SBIG Camera Take Image successfully completed (earlier flags are reset) 02:16:41 Red Alert SBIG Camera Alert Take Image failed (Command timed-out) 02:25:22 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 02:26:35 Green Clear SBIG Camera Take Image successfully completed (earlier flags are reset) 02:33:23 Green Clear CCDSoft Image file has been saved to disk following CCDSoft Restart 02:34:41 Red Alert CcdCamera CcdCamera appears to be frozen (last cycle at 02:34:07) in section 'GetCameraProperties / Status' 02:45:16 Green Clear Dome Charging Dome is parked and re-charging Ok (10mA)

Back to Top

Operational Issues (2025-05-27, S1330)

• Critical Issues (0)
• Major Issues (0)
• Minor Issues (7)
• Small Defects (5)
• Continuous Improvement (15)
  

[ Prev | Next ]

Critical Issues

• None

Major Issues

• None

Minor Issues

• Initial NearZenith Foc1 Focusing failed due to Camera Issue (00:10).  After slew to Near Zenith Focus Field, centering operations failed as all 4 locate frames failed with the message "Image failed (Timed-out)" . The 4th locate fram failure was occuoied with an Obs.Overseer warning with the message "Camera.TakeImageTask in TakeImage/TakeImage is taking a long time".  The Focus Locate Frame similarly failed with the message  "Image failed (Timed-out)".  A red 'SBIG Camera' alert was raised at 00:11:15 with the message "Image failed (Command timed-out)".  There was no automated attempt to call RestartCCDSoft, and this led to continuing problems during the following Target. Log file shows expection in CCDCamera.Get Property IsExposureComplete with the exception message "Error: SBIG driver: Operating system error."  Fixes attempted in AstroMain 3.74.22.   i) TakeImageAsync() routine modified to recognise that an exception has occured in CCDCamera.IsExposureComplete and immediately exit the routine, ii) TakeImage() and TakeFocusImage() routines reworked to handle failed image attempts and to call RestartCCDSoft() unless an Abort Flag is raised , iii) RunAutoPickFocusStar() routine modified to make a second attempt to take Focus Locate Frame if first first attempt fails.
   Fix attempt 2025-05-28 (AstroMain 3.74.22)
   
• Camera Issue occured during 2nd Near Zenith Focusing attempt (00:44).  After a short session suspension due to cloud/too few stars, a second Near Zenith Focus attempt was made. Camera Issues during first attempt which weren't fixed led to the 1st new Locate Frame also failing with the message "Image failed (Timed-out)". A 'CCDSoft' red alert was raised at 00:45:29 with the message "Image file [0000] hasn't been saved to disk, possible CCDSoft issue". A RestartCCDSoft operation was initiated which successfully restored Camera operability and the Centering & Focusing were succcessfuly achieved. AstroMain performed as per design in this case. Issue closed after review (the issue was deemed to have been caused by the above problem whereby the Camera Issue wasn't resolved when it first appeared at 00:10).
   Closed after review  2025-05-28 (Session, AstroMain 3.74.21)
   
• CCD Camera Froze and a image failed during Target 6/9 (01:55).  During Foc1 Focussing for Target 6/9 (T CrB) the Focus Frame 11/14 failed due to 'frozen CCD Camera'. RestartCCDSoft was automatically initiated which restored Camera Operability and the Focus Frame 11/14 was successfully repeated and both Focusing & 1st Main Frame were  successfully completed.  However the 2nd Main Fram (20s V) also failed with message "Camera.TakeImageTask in TakeImage/TakeImage is taking a long time". Red 'SBIG Camera' alerts raised at 01:57:46 and 02:01:53. A RestartCCDSoft operation was again automatically initiated  to 'fix locked thread'. which successfully restored Camera operabiility and allowed the remaining planned image frames to be were successfully taken.  Issue closed after review - AstroMain performed as per design in this case, though the frequency of this issue continues to give concern.
   Closed after review  2025-05-28 (Session, AstroMain 3.74.21)
   
• Take Focus Locate frame failed during Target 8/9, Job Executor didn't enter a wait loop during automatically initiated RestartCCDSoft operation (02:16).  After centering Target 8/9 (AT2025kej) the Foucs Locate Frame failed with message "Image failed (Timed-out)" . An automatically initiated RestartCCDSoft operation wasn't successful as both attempts to Connect Camera failed with the message "SBIG Driver: Device not found"  and after cancellation of focusing  all 5 main images frames (90s C) failed with the message "Image failed (Command timed-out)" and "Camera.TakeImageTask in TakeImage/TakeImage is taking a long time".  A red 'SBIG Camera' alert was raised at 02:16:41 with the message "Image failed (Command timed-out)".   It is noted that the job executor didn't enter a wait loop whilst RestartCCDSoft operation was running, but continued to report GuideStats (focusing) & entered the TakeMainFrames routine causing interlaced report messages. It is unclear if this contributed to the Connect Camera failures or not.  Fixes attempted in AstroMain 3.74.22 (see top-most issue above)
   Fix attempt 2025-05-28 (AstroMain 3.74.22)
   
• 1st Locate Frame and 2nd Main Frame failed during Target 9/9 due to Camera problem  (02:24, 02:34).  After execution moved onto Target 9/9 (AM Her) with the Camera Issue still unresolved, it was of no surprise that 1st Locate Frame failed with an alert message "CCD Image [0000] has not saved to disk"  and a RestartCCDSoft operation was automatically initiated as per design. This successful restored Camera operability and Centering & Focusing were successfully completed.   However during the 2nd Main Frame (45s V) the Image failed with the messages "CcdCamera is frozen (02:34) in section 'GetCameraProperties / Status' "  and "Image failed  (CCDSoft was restarted) ". A automatically initiated RestartCCDSoft operation restored Camera operability and the remaining Main Frames were successfully acquired. Issue closed after review - AstroMain performed as per design in this case (the first failure was deemed to have been caused by the above problem whereby the Camera Issue wasn't resolved when it occured during the preceeding target (02:16) .
   Closed after review  2025-05-28 (Session, AstroMain 3.74.21)
   
• Observatory Computer unexpectedly restarted 2025-05-29 10:47).  The Observatory Computer stopped updates files at around 2025-05-29 10:47. At first it was thought that this was due to a computer crash, but more checks showed that this was associated with a Windows Update that had installed  "2025-05 Cumulative Update for Windows10 Version 22H2 for x64-based Systems (KB5058379)".  Issue understood.  Issue caused a 2 hour outage in Observatory operations. Windows is set to not check updates for 5 weeks and not to install during night time hours (when Observatory Session could be live.  However it is currently up to user to spot that a Windows Updates is wanting to install updates and safely close down programs which are running and manually initiate restart computer to install updates.  It would be nice to be able to programatically tell that Windows has Updates to Install. A separate Continuous Improvement ticket has been added to make AstroMain check daily if there is a AutoUpdate/Reboot Flag raised on the Computer and raise an Alert if there is.
   Resolved 2025-05-29 (Observatory Computer, Windows, User Awareness)
   
• The UltraVNC program running on the Observatory Computer is being hit with lots of connection attempts from the Internet. Whilst reviewing logged Events on the Observatory Computer using Event Viewer, it was noticed that there are multiple events for the UltraVNC Application, with event number associated with an attempted Connection on Port 5900.  Examination of IP addresses showed multiple different IP, all external to my network.  It would seem these are all port scanning attempts by miscellaneous bots trying to find entry to a random computer, rather than a specific attack. The UltraVNC Server(s) are all password protected, so the security issue is minimum but potentially not zero.  The numbers of connection attempts might slow down UltraVNC to a small degree.  The router was previously set to forward port 5900 to the Observatory to allow remote access to the Observatory by myself from outside the local network,  but since this is rarely used, it has been decided to delete the port forwarding to Observatory and AllSky/Weather Computers.
   Resolved 2025-05-29 (Observtory Computer, UltraVNC)

Small Defects

• Yellow coloured records on AstroMag Polar Charts are not particular visible due to white background. X/Y points and D/I points in the 3-6h age bin are drawn with a yellow coloured track which is not particularly visible.  It is proposed to shuffle the colour of age binned data, such that the yellow colouration is replaced by cyan colouration. Fixed in AstroMag 1.4.19.  The previous 12-24h binned data is also now split into 12-18h (violet) and 18-24h (purple).  
   Fixed 2025-05-29 (AstroMag 1.4.19)
   
• NorthCam Altitude axis line is missing in AstroAllSky 3.24 (2025-05-31). AstroAllSky 3.24 was released with a relocation of NorthCam altitude axis & labelling to a secondary axis position on the NightSummaryPlot.  This was to allow primary axis position to be used for NorthCam Stars.  The axis intended axis NorthCam Altitude was missing due to a minor bug.   Fixed in AstroAllSky 3.24.
   Fixed 2025-06-01 (AstroMag AstroAllSky 3.24.1)
   
• NorthCam Star graph line was missing in AstroAllSky 3.24 (2025-05-31). AstroAllSky 3.24 was released with an intended new feature which should plot a white graph line showing NorthCam StarCount (which is now output by AstroNorthCam 1.4.5).  The line didn't plot due to several factors i) the star count was generally very low and would exceed the threshold number of stars (3), ii) there was a bug in new code that would likely have tried to plot the graph line on the AllSky Track rather than on the NorthCam Track, iii) the white graph line (especially with a low star count) if plotted in the NorthCam Track would likely not be seen due to the bright summer twilight sky below 10deg Altitude.   Fixed in AstroAllSky 3.24, i) threshole has been relaxed right down to just 1 star,  ii) bug in plot positioning has been located & fixed, iii) the Zero Stars position has been offset so that it lies above the zone of brightest summer twilight sky.
   Fixed 2025-06-01 (AstroMag AstroAllSky 3.24.1)
   
• Dew inside the upper parts of the AllSky Camera Hemisphere is severely affecting the sky view and the star count (2025-05-31). Due to bout of recent rain and associated elevated humidity, condensation inside the AllSky Camera over last couple of days has formed into large dew drops which are not clearing by themselves (Fig 1). Star count are affected by either blocking/hidding stars (reducing the star count) or creating light artefacts (that incorrectly increase the star count).  Problem fixed 2025-06-01 by opening the AllSky Camera Hemisphere and wiping the interior of the hemisphere.  Opportunity was also also taken to clear cob-webs and a spider that had taken up residence as seen on recent AllSky Images (Fig 2).
   Fixed 2025-06-01 (AllSky Camera)
   
• AstroNorthCam's 'find stars' routine is picking up to many false positive from clouds close to horizon (2025-05-31 early night).  AstroNorthCam 1.4.5 has been released with a new feature to detect stars in nighttime images. This was developed/tested on images from Jan 2025 and hasn't really been tested with images from late May/June.  During the first part of the night 2025-05-31 there were some cloud moving eastwards along the northern horizon and appeared to attract a lot of false - 'star' detections  (see Fig 3 & Fig 4) .  Prehaps introducing an altitude (y-pixel based) cutoff might reduce this problem in a sky zone, where stars will naturally be dimmed by atmospheric / airmass extinction.
   To investigate  2025-06-01+ (AstroNorthCam 1.4.6+)
   
• AstroNorthCam's 'find stars' routine is picking up too few stars in sky regions where images shows faint but distinct stars. (2025-05-31 middle of night). AstroNorthCam 1.4.5 has been released with a new feature to detect stars in nighttime images. This was developed/tested on images from Jan 2025 and hasn't really been tested with images from late May/June.  During the middle part of the night 2025-05-31 the sky was clear and there were faint stars visible in the images (eg stars in constellation Cassiopeia) which weren't detected even though 2 stars (Capella and Castor) were detected ok (see Fig 4) . They are relative faint due to the twilight sky (Sun Alt -10) there were some cloud moving eastwards along the northern horizon and appeared to attract a lot of false - 'star' detections Prehaps introducing an altitude (y-pixel based) cutoff might reduce this problem in a sky zone, where stars will naturally be dimmed by atmospheric / airmass extinction.
   To investigate  2025-06-01+ (AstroNorthCam 1.4.6+)
   
• AllSky/Weather Computer is logging multiple event warnings concerning WHEA-Logger / PCI Express Root Port .  Whilst reviewing logged Events on AllSky/Weather Computer using Event Viewer, it was noticed that there was multiple events with WHEA logger with message "A corrected hardware error has occurred"  on Component 'PCI Express Root Port'. Whilst the issue seems to cause no noticeable problem to computer operation, it may potentially be slowing down the system to some extent ?.   It is noted that existing driver for PCI Express Root is dated from 2006.   To examine whether there is a driver update that can fix this.
   To investigate 2025-05-30 (AllSky/Weather Computer, Windows)

Continuous Improvement

• Make a number of small corrections and improvements to charts produced by AstroMag.  Make small corrections and improvements :  i) correct 'I' labelling on DIF Chart., ii) Clair data in X, Y, Z Stackplots should be suffixed with the component name.  iii) increase scale of vertical axis on DI Polar
   Done  2025-05-29 (AstroMag 1.4.17)
   
• Add routine to AstroMain to raise alert if Windows has updates to install.  This has been a requirement for some time, but is wasn't known how this could be done. GitHub Copilot Chat was asked "How to programmatically check if Windows has updates to install", which provided a suggested to use WUApiLib but it wasn't helpful and hasn't been committed.  A better solution came from the query "   " which resulted in a new routine called ObsManager.CheckForRequiredWindowsReboot() that checks the Registry key  
    "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired"
and if the key exists, it indicates that updates are downloaded and waiting for installation or a system reboot.   The new routine is run each time a new general session is created (ie it run daily around 09:00) and if an installation/or reboot is required it raises a red 'Windows Update' alert.  Implemented in AstroMain 3.74.23 (it may take a few weeks before it is known that the new routine performs as per requirement).
   Done 2025-05-29 (AstroMain 3.74.23)
   
• Make a button to AstroLaunch to open CumulusMX Dashboard (localhost:8998) in a browser to check operating status of CumulusMX.  Sometimes following a reboot AllSky/Weather Computer the CumulusMX program will stop functioning correctly, and stops recording Weather Data from Ecowitt Weather Station, which stops supply of weather data to AstroWeather, AstroAllSky & AstroMain.  The status of the program is most easily check by entering 'localhost:8998' in a web browser on the computer, or 192.168.1.55:8998 from another computer on the network.  It would be handy if there was button in AstroLaunch to open the CumulusMX Dasboard using the relevant :8998 address. Implemented in AstroLaunch 1.13.3 - button named 'CumulusMX' placed on the 'Support Apps' tab.
   Done 2025-05-30 (AstroLaunch 1.13.3)
   
• Add process to AstroNorthCam that can recognise & count the number of stars in NorthCam Images and make the star count available to AstroAllSky.  As part of a separate Continuous Improvement attempt to recognise & highlight transient objects in nighttime NorthCam Images (which is proving quite a difficult task), it was discovered on 2025-05-30 (AstroNorthCam 1.4.4) that it was relatively easy to detect and count the number of stars in NorthCam images.  It is formalise the process and write the starcount out to a transfer file,  making it available to AstroAllSky for plotting it on NightSummaryPlot and for onward transfer to AstroMain. Implemented in AstroNorthCam 1.4.5.  The StarCount is produced by the DetectNightObjectsInImage() routine, and written to "C:\Data\AllSky Imaging\Latest\Latest.NorthCamStarCount.dat" by new WriteNorthCamStarCount() routine with format 'UtcNow, nStars'.
   Done 2025-05-31  (AstroNorthCam 1.4.5)
   
• Add new routines / code to AstroAllSky to import and use the number of stars in NorthCam Images and make the star count available to AstroMain. AstroNorthCam 1.4.5 has been recently released that determines the number of stars in NorthCam Images and writes the star count to a transfer file "C:\Data\AllSky Imaging\Latest\Latest.NorthCamStarCount.dat" with a single line with format  'UTCnow, nStars'. AstroAllSky needs to be extended to include a ReadNorthCamStarCount() routine and change to NightSummaryPlot to plot the NorthCam Star count as a white 'stars' line on the right hand 'NorthCam' track.  Value should also be recorded in the Stars file and in the record sent to AstroMain.  Implemented in AstroAllSky 3.24.   ReadNorthCamStarCount()  added. Additions also made to several existing routines : AllSkyOpenDatFile,  AllSkyWriteDatFileRecord_DayTime(),  AllSkyWriteDatFileRecord(), AllSkyTakeFrames(), AllSkyProcessFolder(), DrawNightSummaryPlotLine(), DrawNightSummaryPlotLineInfo().  Onward Transfer files :  "AllSky (stars).dat",   LocalSessionName + " (data).dat.  Scorecard.DrawScore(),  ScorecardSender.BuildRecord(). AstroMain 3.75 and AstroGuard 1.11 modified to correctly import the modfied Synopsis/Scorecard records (which are otherwise impacted by insertion of NorthCamStarsCount into the Synopsis record).  NorthCamStars (count) is displayed on AstroMain's Manager Tab in AstroMain 3.75 but is not used as yet by ObsManager, MustClose(), CanOpen() routines.   A night with Stars is needed to test plotting of NorthCamStars on NightSummaryPlot and confirm its correct transfer through to AstroMain
   Done 2025-05-31  (AstroAllSky 3.24, AstroMain 3.75 and AstroGuard 1.11)
   
• Add 50nT, 100nT buttons to AstroMag Charts tab to make it easier to switch the Magnetogram Scale.  Adding button routine to change the magnetogram scale it easier and safer. Changing the field by manually editing the field carries a minute chance of causing and unwanted consequence or exception if charts (produced every 10 mins) happen to be built at the same time that user is manually editing the field.  
   Done 2025-05-31 (AstroMag 1.4.18)
   
• Add a settings field to AstroMag to allow the temperature range of Magnetometer Temperature Chart to be adjusted upwards or downwards.  In AstroMag 1.4.17 the temperature range on the Magnetometer Temperature Chart is harded code to be -2 to 22°C, but on 2025-05-29 Outdoor Temperature reached 22°C with Observatory Temperatures reaching 24.5°C and thus outside of the chart range.  This situation is likely to be increasingly common as with move into summer. Improvement implemented in AstroMag 1.4.18 so that the temperature range can be shifted upwards (or downwards) as required for the season.
   Done 2025-05-31 (AstroMag 1.4.18)
   
• Remove 'Rain (Ws)' field from AstroMain's Manager Tab. 'Rain Ws' is a rain measurement from the weather station and whilst useful for determining a cumulative rain total, it is proven to be not particularly useful for precise indication of realtime rain.  The CloudSensor rain sensor value shown on the Manager Tab already provides this role. Given that space on the Manager Tab is at a premium, it is proposed to remove the 'Rain Ws' field and use the space for a more beneficial field or for better layout. 
   Done 2025-05-31 (AstroMain 3.75)
   
• Relax threshold levels on AstroMag's Activity Charts.  To reflect the lower amplitude variations at the latitude of Clair Geomagnetic Station compared to Sumburgh Head Station in Shetlands, the threshold levels for yellow, orange & red colourations need to be relaxed by c. 75%.   Yellow Threshold relaxed from 50 to 35 nT, Orange Threshold relaxed from 100 to 75nT.  Red Threshold relaxed from 200 to 150 nT. Implemented in AstroMag 1.4.19.
   Done 2025-06-01 (AstroMag 1.4.19)
   
• Modify AstroMag to work with up to 5 day's worth of Magnetometer Data.  AstroMag 1.4.18 and earlier versions worked with a maximum of 24 hours worth of data.  This is fine when creating 24 hour rolling charts.  However it it planned to add some extra graphs that show the last 5 days worth of data, and to add GA code that uses 5 day's worth of data from the Clair station in order to determine the best correction parameters for temperatures etc. AstroMag 1.4.19 has been modified to store up to 5 days worth of magnetometer data.  5 days of minute data requires array sizes that can handle ~ 7200 records (5 x 24 x 60). The size of the MagRecord() array increased from 5000 to 10000.  Similarly the size of MagRecord() for Comparison Sites using TDataSet class object is also increased from 5000 to 10000. The  LoadRecords() routine modified to load records where Date > RefDateX.AddDays(-4)  (ie an extra 4 days worth of data).  Code to 'Refresh MagRecord array' in the SamMonitor()  routine modified to work worth with the extra 4 days of data.
  '   New Code     If MagRecord(i).DateX < RefDateX.AddDays(-4)then
  Implemented in AstroMag 1.4.19.  (Note that code to actually load 5 days worth of Comparison Station data - ie up to 6 days gross instead of 2 days gross- still need to be added).  An extra condition had to be added in PolarCharts.PlotData to ensure that only data from the last 24 hours is plotted. (initial implementation saw all 5 days worth of data being plotted).
   Done 2025-06-01 (AstroMag 1.4.19)
   
• Modify Import of Comparison Station Data into AstroMag.  In AstroMag Comparison Station data is accessed into order to generate Stackplot Charts for X, Y & Z Axis (https://www.astro-richweb.net/astro/geomagnetic_station.htm#Stackplots).  Currently in AstroMag 1.4.19 & before the last 2 days worth of station data is downloaded every time the chart building routines are run which is every 10 mins.  With the change in AstroMag 1.4.19 to work towards handling of up to 5 days worth of data, up to 6 days worth of comparison data needs to be accessed every 10 mins. Given that only data from the current day is getting refreshed, it is an unnecessary overhead to download the entire 6 days of data every time a set of stackplots are created. It is proposed that data from past days is stored locally and accessed from disk instead of being re-downloaded.
   To develop & implement  2025-06-02+ AstroMag 1.4.19+)
   
• Add process to AstroNorthCam that can extract timestamped cropped images of detected objects. AstroNorthCam has been recently modified to detect objects/birds in daytime images and, with less success,  objects in nighttime images.  It is proposed to extract the detected objects into cropped and time labelled pictures.  For detected objects meeting a certain threshold the cropped & labelled picture should be copied to live folder to main a set of 12 recent objects.   NorthCam.LatestObject01.jpg,  NorthCam.LatestObject02.jpg etc. In the first instance pictures wouldn't be presented in strict time order on website, but this is a future option. AstroAllSky 3.24.2 modified to upload pictures to Observatory website.
   Done 2025-06-03 (AstroNorthCam 1.4.6,  AstroAllSky 3.24.2, Website)
   
• Modify AstroMag Settings and Handling to support time dependant variation of expected magnetometer field values.  AstroMag 1.4.19 and earlier operates with expected magnetic fields strengths for the Station Site at 2025-04-01 as forecast by the World Magnetic Model  (World Magnetic Model 2025 Calculator (geomag.bgs.ac.uk).  However the strength's change with time, in the case of Y Axis the change amounts to 59.1 nT/year.  It is proposed to modify program settings to store a reference date (eg.  2025-04-01 ) and rate of change along with the 3 axis field strength values  and other terms D, I, F etc.  Handling with need to be able to calculate and use time-modified expected values.
   To develop & implement  2025-06-02+ AstroMag 1.4.19+)
   
• Add process to AstroNorthCam that can calculate Cloud Cover from NorthCam Images and be made available to AstroMain as an Early Warning Indicator for cloud approaching from the north.   AstroMain includes a number of indicators for determining the need to close the Dome, which include data from Eurotech Cloud/Rain Sensor, a Star Count derived from AllSky Camera Images, and a Rain Threat data from online RainRadar/Weather data.  The Cloud Sensor box (Aurora Eurotech) is tilted at around 10-20 deg to enable heavy water to drain off the ceramic rain detector as recommended by the Cloud Sensor user manual. The tilt is a southward direction, and a negative result of this is that the sensor is less suited for picking up cloud approaching from the north.  This is particular hazard during wintertime, when snow showers can approach rapidly from the north, with snow carried by the wind ahead of the main shower, and the possibility that snow is not immediately picked up by rain sensor. To help fill this gap it is proposed to develop a realtime analysis routine in AstroNorthCam that can calculate Cloud Cover from NorthCam Images, and make that data available to AstroMain.  This may not be so easy due to the difficult of distinguishing cloud during the changing light condition during the dawn/dusk/twilight period (and during Aurora ?).  A more promising route is the recognition of stars and the transfer of number of stars (NorthCam StarCount) through to AstroAllSky & AstroMain.
   To experiement & implement  2025-05-30+ (AstroNorthCam 1.4.6+)
   
• Add process to create 1 year rolling plots of particular weather data.  Particular weather data would be suitable for creating 1 years Weather Charts.  Suggested weather data are Solar Radiation, Outside Temperature, Wind Speed, Wind Direction,  Rain,  Clarity, Pressure. It is assumed that Charting would be performed in AstroWeather where existing 5h, 16h and 5d charts are built.  1y charts would only need to be built once a day, there is no advantage in making the frequency any shorter than this. AstroAllSky would need to be modified to support the upload of new charts.
   To develop & implement  2025-06-01+ (AstroWeather 1.28+)

[ Prev | Next ]

[ Prev | Next ]

Back to Top