David's Astronomy Pages Notes - Session 1428 (2026-04-30)

Notes (S1427)

Notes Main

Home Page

Notes (S1429)

	Session Aims & Highlights
	- Observing Result  - Night Summary Plot  - Session Event Log
	Operational Issues
	- Critical Issues (0),  Major Issues (3),  Minor Issues (6),  Small Defects (1),  Continuous Improvement (5)
	- Figures (0)
	Images from 2026-04-30  >>
	2026-05-05
	Observatory Computer - Reinstallation of Windows 11

Session Aims & Highlights (2026-04-30)

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 6.0.0.65, CCDSoft 5.00.201 (Reinstall), DeviceHub 7.1.0.4707, MeadeGeneric 1.3.12.522, UPB 3,  Pulsar Dome Firmware 1.51 & Driver 6.3.10
• Pegasus-UI 2.10, Peg-Focuser 2.10, Peg-Switch 2.10, TCF-LSI 3.3.5
• SharpCap 3.2, PHD2  2.6.13, Siril 1.4.1, deCONZ 1.18.2, ASCOM 7.1.0.4707
   
• AstroMain 3.81.11  AstroPlan 1.46.2, AstroShCap 1.3.23, AstroGuard 1.13.2  (any new items or versions in bold)
  AstroMag 1.5.12, AstroVOE 1.16,  AstroSN 1.16,  AstroProtect 1.10.6,  AstroMove 1.18.1
  AstroAllSky 3.27.10, AstroWeather 1.30.3   AstroObsCam 1.13.1, AstroNorthCam 1.8.2, AstroLaunch 1.14.9

Highlights

• Targets. 19/19 planned targets were completed. .
•  Dome. No issues open/closing shutter. Dome was successfully parked at the end of the session.

Notes

• .Skies clear, but affected by bright moon.

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) Note:  The NorthCam Star Count line is unreliable and should be ignored (The AstroNorthCam 'Find' Star method is producing many false positives from clouds)

Actual Weather vs Pre-Session Weather Forecast

Session Event Log

Time     Event Detail 21:36:49 Session Monitoring AutoStart monitoring for Live Session opportunity between 21:51 & 03:19 21:36:52   AutoStart Waiting AutoStart waiting till earliest start time at 21:51 21:51:13 Session AutoStarting Session autostarting (21:51) 21:51:20 Session Created Session Created (Live, 2026-04-30 S01428) 21:51:22   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.) 21:51:42   Scope Switched On Telescope Power has been switched on via UPB Switch 21:53:26   Services Started Observatory Services started 21:53:35 Observatory (Auto) Observatory placed in Fully-Automated Mode 21:53:39 Session Pending Session pending (2026-04-30) 21:53:41 Session Initiating Session initiating (2026-04-30) 21:54:04   Camera1 Connected SBIG Camera connected (Set point -15°C) 21:54:11   Plan Requested Observing Plan requested from AstroPlan (1.46.2) 21:54:36   Plan Loaded Observing Plan loaded to queue (PlanID: 1228) 21:55:18   Telescope Connected Telescope connected (TheSky6) 21:55:42 Session Equilibration Session ready to Open Dome 21:56:28   Dome Opened Dome opened (Opening time 45s, Zigbee 69,414s) 21:56:29   Equilibration Started Dome Equilibration started 21:56:32   Equilibration Ended Dome Equilibration ended (0.0 mins total) 21:56:34 Session Running Session running 21:56:36   Queue Started Observing Queue started (19 targets selected) 21:56:39     Target Started (NrZen) Target started (Focus Field 13, HIP 63666) 21:56:54       Dome Unparked Dome unparked 22:02:03       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 22:04:17       Focusing Completed Foc1 AutoFocus Completed (Profile No 1, wide) 22:06:20       Focusing Completed Foc1 AutoFocus Completed (Profile No 1) 22:06:28       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 22:08:30       Focusing Completed Foc2 AutoFocus Completed (Profile No 2, wide) 22:10:13       Focusing Completed Foc2 AutoFocus Completed (Profile No 2) 22:10:33     Target Completed (NrZen) Target completed (Focus Field 13, HIP 63666) 22:26:14     Target Started (1/19) Target started (1/19, C/2022 N2 (PANSTARRS)) 22:30:54       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 22:33:36       Focusing Completed Foc1 AutoFocus Completed (Profile No 3) 22:42:24     Target Completed Target completed (1/19, C/2022 N2 (PANSTARRS)) 22:42:28     Target Started (2/19) Target started (2/19, NGC 5907 w/SN2026kid) 22:47:36       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 22:50:19       Focusing Completed Foc1 AutoFocus Completed (Profile No 4) 23:06:36     Target Completed Target completed (2/19, NGC 5907 w/SN2026kid) 23:06:40     Target Started (3/19) Target started (3/19, T CrB) 23:14:25     Target Completed Target completed (3/19, T CrB) 23:14:29     Target Started (4/19) Target started (4/19, GCVS AM Her) 23:18:15       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:20:33       Focusing Completed Foc1 AutoFocus Completed (Profile No 5) 23:25:55     Target Completed Target completed (4/19, GCVS AM Her) 23:26:00     Target Started (5/19) Target started (5/19, KIC 8462852) 23:30:35       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:33:15       Focusing Completed Foc1 AutoFocus Completed (Profile No 6) 23:37:49     Target Completed Target completed (5/19, KIC 8462852) 23:37:54     Target Started (6/19) Target started (6/19, AT2026koc) 23:41:14       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:43:25       Focusing Completed Foc1 AutoFocus Completed (Profile No 7) 23:59:42     Target Completed Target completed (6/19, AT2026koc) 23:59:46     Target Started (7/19) Target started (7/19, GCVS ER UMa) 00:10:07     Target Completed Target completed (7/19, GCVS ER UMa) 00:10:11     Target Started (8/19) Target started (8/19, GCVS RZ LMi) 00:13:35       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:15:44       Focusing Completed Foc1 AutoFocus Completed (Profile No 8) 00:21:01     Target Completed Target completed (8/19, GCVS RZ LMi) 00:21:05     Target Started (9/19) Target started (9/19, GCVS RR Leo) 00:24:30       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:26:53       Focusing Completed Foc1 AutoFocus Completed (Profile No 9) 00:32:23     Target Completed Target completed (9/19, GCVS RR Leo) 00:32:28     Target Started (10/19) Target started (10/19, NGC 3437 w/SN2026kie) 00:35:52       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:38:59       Focusing Completed Foc1 AutoFocus Completed (Profile No 10) 00:55:01     Target Completed Target completed (10/19, NGC 3437 w/SN2026kie) 00:55:05     Target Started (11/19) Target started (11/19, 29P/Schwassmann-Wachmann) 00:58:42       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-LSI) 01:10:32     Target Completed Target completed (11/19, 29P/Schwassmann-Wachmann) 01:12:29     Target Started (12/19) Target started (12/19, NGC 3861 w/SN2026ihi) 01:15:44       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:17:46       Focusing Completed Foc1 AutoFocus Completed (Profile No 11) 01:33:48     Target Completed Target completed (12/19, NGC 3861 w/SN2026ihi) 01:34:29     Target Started (13/19) Target started (13/19, M31 w/M31N 2026-04b?) 01:38:41       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:41:14       Focusing Completed Foc1 AutoFocus Completed (Profile No 12) 01:57:16     Target Completed Target completed (13/19, M31 w/M31N 2026-04b?) 01:57:20     Target Started (14/19) Target started (14/19, GCVS CI Cyg) 02:00:44       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:02:54       Focusing Completed Foc1 AutoFocus Completed (Profile No 13) 02:06:06     Target Completed Target completed (14/19, GCVS CI Cyg) 02:06:52     Target Started (15/19) Target started (15/19, UGC 12040 w/AT2026kux) 02:10:49       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:13:17       Focusing Completed Foc1 AutoFocus Completed (Profile No 14) 02:29:35     Target Completed Target completed (15/19, UGC 12040 w/AT2026kux) 02:29:39     Target Started (16/19) Target started (16/19, AT2026kay) 02:34:16       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:36:42       Focusing Completed Foc1 AutoFocus Completed (Profile No 15) 02:53:23     Target Completed Target completed (16/19, AT2026kay) 02:53:28     Target Started (17/19) Target started (17/19, AT2026jyw) 02:57:36       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-LSI) 03:13:59     Target Completed Target completed (17/19, AT2026jyw) 03:14:04     Target Started (18/19) Target started (18/19, GCVS BL Lac) 03:17:40       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:19:58       Focusing Completed Foc1 AutoFocus Completed (Profile No 16) 03:24:03     Target Completed Target completed (18/19, GCVS BL Lac) 03:24:07     Target Started (19/19) Target started (19/19, GCVS HH And) 03:27:49       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:30:14       Focusing Completed Foc1 AutoFocus Completed (Profile No 17) 03:32:05     Target Completed Target completed (19/19, GCVS HH And) 03:32:07   Queue Completed Job Queue completed 03:32:08 Session Closing Session closing 03:33:03   Dome Closed Dome closed (Closing time 55s, Zigbee 0s) 03:33:31   Dome Parked Dome parked (parking time 20s), Az: 90.0 deg 03:34:21   Telescope Parked Telescope parked (parking time 47s total) 03:34:45   Telescope State Handbox reads 'Scope parked Turn scope off.' 03:35:24   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 03:36:50   Services Stopped Night Services stopped 03:36:53 Session Finishing Session Finishing started (Create Fits Summary, Transfer Files) 03:37:40     Dome (Find Park) Find Park started (Search Az 88.0 to 92.0°, Step 0.2°, Narrow) 03:38:25     Dome Find Park found (Best Park Az 90.6°) 03:38:31     Dome Dome has been synced at park position (Az 90.0°, Adjustment: -0.6°) 03:38:33   Dome Parked Dome parked 03:41:34   Dome Charging Dome is parked and well charged (96%, 15.0v) 03:41:36 Session Finished Session Finished

Session Alerts & Alarms

Time     Type       Name Detail 02:53:40 Yellow Alert Dome Shutter Pulsar Shutter appears to be asleep (last fresh data was at 1990-01-01 00:00:00) 02:53:42 Green Clear Dome Shutter Pulsar Shutter has woken up (fresh data at 01:53:32, outage 19,107,473.7 min) 03:41:34 Yellow Alert Dome Charging Dome is parked and well charged (96%, 15.0v)

Back to Top

Operational Issues (2026-04-30 S1428)

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

[ Prev | Next ]

Critical Issues

• None

Major Issues

• Admin account on the Observatory Computer and new account couldn't be created (2026-05-03). Whilst preparing the Observatory Computer for installation of new SSD at local Computer Repair Shop the Admin account on the computer was checked.  Although the 'Admin' account could be initially opend  it would go to a black screen and wouldn't go to a windows desktop.  An attempt was made to create a new account, but it would bring up a blank dialog and the operation couldn't be progressed (see Fig 1).  This is a major issue as it leaves the computer without a fall-back account, in case there is some issue with the main user account.   After the installation of the new SSD , a backdoor method  of creating a new user account  ('netplwiz' from Command prompt) was used to create an Admin2 account (see Fig 1b).  However the new account wouldn't successfully finish its initial setup operation and would stall on a black screen. An in-place Windows repair of  (using Window ISO/Mount/Setup.exe method) was attempted.  Whilst this resolved the black screen issue for the original Admin account, it still left the computer unable to create an account using nornal Windows Settings, and would allow successful setup of new 'Admin3' account that was created via the backdoor method.  Due to a critical issue starting PHD2 following the Repair attempt, it will be necessary to reinstall Windows in the coming days.
  -  Admin account was broken in a shallow, user specific way. The repair install fixed the system-level shell components it depended on.
   - Admin2 and 3 accounts depend on the corrupted Default User Profile and provisioning templates, which can not be fixed by in-place re-install.
  Issue is placed on hold, as it requires a Window Reinstall, which is deferred till further notice.
  On Hold 2026-05-07 (Observatory Computer, Windows/User Accounts)
   
• Unable to access and replace NVMe SSD drive in the Observatory Computer (2026-05-03).  The existing 0.5 TB NVMe (Non-Volatile Memory Express) SSD in the Observatory Computer has nearly reached the end of its life due to number of bad sectors, and a persisant S.M.A.R.T warning upon each boot-tup.  A new 1 TB  SSD (WD_Black) has been sourced and an attempt was made on 2026-05-03 to install the new SSD, however the position of the old one couldn't be located after opening the back of the laptop.  It was suspected that the SSD might lie below a 10 x 10 cm metail grill on the motherboard, but it wasn't obvious how the grill could be removed without damaging the motherboard. Copilot suggested that the SSD might lay on the underside of the motherboard.  Eitherway it as beyond my skill levels to fix, and the computer was taken to a local Repair Computer Shop on 2026-05-04. They migrated existing disk image onto new SSD, installed it and expanded the C:/Drive to the include the new capacity provided by the new 1 TB SSD. The work took around 3-4 hours and cost £80. The SSD location turned out to be below the metal grill and not therefore wasn't on the underside of the motherboard meaning that there was no requirement to disconnect wires and take out the motherboard) . The installation of new SSD was successful and the computer returned the same day. Underlying defects in the Windows Operating system remain, but they are unconnected to the new SSD installation, but they may or may not be related to the corruptions / damaged sectors on the original SSD.
  Fixed 2026-05-04 (Observatory Computer)
   
• PHD2 could not be started after performing Windows In-place repair (2026-05-04). After attempting an in-place Windows repair on the Observatory Computer (using Window ISO/Mount/Setup.exe method) in order to fix Admin account and/or create a new fall-back account, the PHD2 application couldn't be opened. It would immediately produce an unhandled exception and crash.  Neither reinstalling the existing PHD2 version or uninstalling PHD2 and installing the latest PHD2 version was able to resolve issue.  Indictaions are that there is a deep level Windows corruption.  Since PHD2 is critical for observatory operations the only fix left is to reinstall Windows 11 (with 'keep files' option). Since all installed applications will be lost during the reinstall carefull preparation is required to capture as many settings as possible (files, screenshots etc).   Later on (206-05-07) it was found that PHD2 was able to be launched without the earlier exception.  Existing profiles were re-added to PHD2 from a backup folder, and profile ids updated in AstroMain 3.81.12.
  Fixed 2026-05-07 (Observatory Computer, PHD2)

Minor Issues

• Zigbee 'Shutter Bot' sensor is not reachable (post-session).  The Zigbee ope/close sensor ('Shutter Bot') at the bottom of the Observatory shutter used for detecting when the shutter is closed in no longer reachable.  It is likely that its battery level is too low, and needs to  be replaced and reconnected to the DeConz Network in Phoscon. A new battery (CR1631 3V) was installed 2026-05-04, but reconnecting it to the Zigbee Network will have to wait to the operating system on the Observatory Computer is repaired and the computer returned to service.   Fixed on 2026-05-07 after returning the Observatory Computer to the Observatory and using Phoscon / Add Sensor and button press/reset on sensor to reconnect to Zigbee network.  Battery levels in 'Top Shutter' and 'Bot Shutter' sensors are 91% and 100% respectively. Battery level in the 'Dome Park' sensor is also good (91%) but the battery level in the 'Observatory Door' sensor (45%) is poor and needs to be monitored.
  Fixed 2026-05-07 (Observatory, Zigbee Network, Pulsar Dome)
   
• CCDSoft could not be started due to missing .dlls after performing Windows In-place repair (2026-05-04). After attempting an in-place Windows repair of the Observatory Computer (using Window ISO/Mount/Setup.exe method) in order to fix the issue with Admin account / account creation, the CCDSoft  application couldn't be opened. It would produce a series of CCDSoft System Errors dialogs (see Fig 2).  This issue also occurred previously on 2026-03-27 (see notes S1411, 2026-03-27) and it was determined that replacing the '.dll's' with backup copies (used to work in certain circumstances) wouldn't resolve the issue and a reinstallation of CCDSoft is required.  This was done by reinstalling from a disk copy of the original program CDROM (avoiding the need to use original disk),  and then after the restarting computer and initially running the program as Administrator (a previous known key step),  the following version updates were installed 6.0.135 (New), 6.0.156 (Key), 6.0.201 (Latest). This was relatively quick as only selected updates were made and setup to install SBIG drivers were skipped/cancelled. Due to other issues there was no time to make the necessary update to the permissions on the 'C:\Program Files (x86)\Software Bisque\CCDSoft Version 5\Configuration Files\DEFAULT.sxt'  file to allow full control to users. This is to avoid the issues that affected S1413 session (see notes S1413, 2026-03-29)  Whilst this fixed the issue for CCDSoft there are some underlying deep level defects in the Windows Operating system that still prevent successful creation of new accounts and prevent PHD2 from starting, and it will be necessary to perform a Windows Reinstall in the coming days. After this a fresh install of CCDSoft will be required. It would be interesting if the new  installation can go directly from original CDROM version to 6.0.156 (Key).
  Fixed 2026-05-04 (Observatory Computer, CCDSoft)
   
• TeleAPI not available after performing Windows In-place repair (2026-05-04). After attempting an in-place Windows repair of the Observatory Computer (using Window ISO/Mount/Setup.exe method) the TeleAPI couldn't be used in TheSky6 to connect the TheSky6 Telescope to TeleLink / DeviceHub Telescope.  This issue was seen after upgrade of  application couldn't be opened. It would produce a series of CCDSoft System Errors dialogs see Fig 1.  This issue also occurred previously on 2026-10-29 following upgrage of computer from Windows 10 to Windows 11 (see notes S1371 2025-10-29). The same fix was used which was to reinstall TeleAPI ( ..\ASCOM Plugin TeleAPI\TeleAPI(5.0.4)Setup.exe ).  
  Fixed 2026-05-07 (Observatory Computer, TeleAPI)
   
• AstroMain is not able to set PHD2 profiles on Observatory Computer. After issues with PHD2 /  Windows, during which PHD2 was reinstalled,  profile backups were re-imported. However the profile ids of the imported profiles are seeming changed from what AstroMain has previously used.  Previously in AstroMain 3.81.11 the Cam1ProfileID (for LX200-ST10) returned the value 2, whilst the Cam2Profile ID (for TS80=178MC) returned the value 1.  A new button : list profiles has been added to AstroMain 3.81.12 to get a tabulated list of profile id's.  This established that the new Cam1 (LX200-ST10) profile id is 4 and new Cam2 (TS80-178MC) is profile id is 3.  Fixed in AstroMain 3.81.12, this was done by updating the hardcoded profile id's associated with Cam1 and Cam2  (ideally they would be would be changeabe via setttings)
  Fixed  2026-05-07 (Observatory Computer, PHD2)
   
• Eaton UPS not appearing in System Tray on Taskbar .  Although Eaton UPSCompanion service is running (mc2.exe) is running and confirmed by the UPS Companion frontend, it doesn't have an icon showing in the system tray.  In contrast UPSCompanion has an icon showing on the AllSkey/Weather Computer for the UPS sitting in its computing bay.  Tests suggest that the tray icon disappears when mc2.exe (user) task is closed and can't be made to appear again until (likely) the next time the computer reboots. Tray Icon appeared again after restarting computer on 2026-05-14 for a Windows Update.
  Resolved 2026-05-14 (Observatory Computer, Eaton UPSCompanion)
    
• The inferred state of the Eaton UPS can be incorrect in a specific situation.  AstroMain (and AstroWeather/AstroAllSky) can not determine the defiinitive current state of the Observatory's UPS, as  It can not read the UPS directly like the Eaton UPSCompanion and the UPS Companion UI Form can. Instead it has to infer the state of the UPS based on the last alert/notifcation generated and saved in the 'euc.log' file.  This generally works ok during normal operations. However if the USB cable to the UPS box is removed (as might happen when computer was removed from the Observatory over the last few days, the last message in the log file is "Communication with UPS has failed" (see Fig 3). There is no corresponding message to say the 'Communication with UPS has restored'. Hence AstroMain can only infer that UPS is not connected (and therefore its power state is unknown). The only way round this is to briefly turn off the power to UPS and then turn it on again.  This generates new alert message finishing with "The system is powered by the utility" and inferences can then be normalised again.   A separate Continuous Improvement Ticket has been added to test presence of Eaton UPS is present in Device Manager or not.
  Closed  2026-05-07 (Observatory, Eaton UPS, User Awareness)

Small Defects

• Pulsar Shutter reported to be asleep with a znon last fresh data time (02:53).  A yellow Dome Shutter alert was raised at 02:53:40 was raised with the message "Pulsar Shutter appears to be asleep (last fresh data was at 1990-01-01 00:00:00) " , and 2s later at 02:53:42 a green all-clear was raised with the message "Pulsar Shutter has woken up (fresh data at 01:53:32, outage 19,107,473.7 min" .  Clearly a znon value for last fresh data time was being referenced in the yellow alert and a time since znon time is referenced in the green alert. Given that this was so late into the session, it is unclear why a latest fresh date time would still be znon, otherwise it would have been set to a real time much earlier. To investigate and fix.  The (Observatory) Dome Log (summarising the Pulsar ASCOM Log) records a  'System.ApplicationException'  exception at 02:53:13.35 with the message "Object synchronization method was called from an unsynchronized block of code.[0D][0A] at System.Threading.Mutex.ReleaseMutex()[0D][0A] at ASCOM.Utilities.TraceLogger.LogMessage(String Identifier, String Message) in C:\ASCOM Build\Export\ASCOM.Utilities\ASCOM.Utilities\TraceLogger.cs:line 573[0D][0A] at ASCOM.Pulsar_Observatories_Dome.Dome.CommandString(String command, Boolean raw)" . On the presence of a 'Volatile Exception'  the SetNullDomeRecord() routine is called which besides setting all other DomeRecord fields to null, it sets DomeRecord.LastDateTime to vcNullDate, which explains the '1990-01-01 00:00:00' time in the alert message.   Fix attempted  in AstroMain 3.82.1 - the logic is changed so that SetNullDomeRecord() is not called in event of a 'Volatile Exception'.  DomeRecord remains as it was, data simply become stale if exceptions continue,  or refresh on the next valid Volatile record.
  Fixed 2026-05-14 (Pulsar Dome, AstroMain 3.82.1)

Continuous Improvement

• Extend AstroVma's  VarStar/Graph Configuration tool to include multiple name handling.  A new VarStar/Graph Configuration tool is being added to AstroVma with database tables (varstar, graph and graphlayer) and new UI forms (VarStarsForm and GraphConfigForm) to support the creation of configurations that allow Protometric Charts to be easily created and updated by AstroMain.   Currently the tool (0.2.4 / 0.2.5) supports just one name 'VarStarName' but it is recognised that the tool needs to support multiple names (ObjectName,  VmaName and OtherName).  These have been added to the database and UI Forms in AstroVma 0.3. Use of them requires changes to AstroMain's Build Plots.
  Done 2026-05-04 (AstroVma 0.3)
   
• Perform user testing of AstroVma's  VarStar/Graph Configuration tool before acceptance.  A new VarStar/Graph Configuration tool is being added to AstroVma with database tables (varstar, graph and graphlayer) and new UI forms (VarStarsForm and GraphConfigForm) to support the creation of configurations that allow Protometric Charts to be easily created and updated by AstroMain.   The tool has been further extended to support multiple names (ObjectName,  VmaName and OtherName) in AstroVma 0.3. The tool requires extensive testing before it is ready to input live configurations.
  Done 2026-05-05 (AstroVma 0.3)
   
• Modify AstroMain/PageBuilder's btnPlotGraphTest() routine to read Graph Specification from Database.   A new VarStar/Graph Configuration tool is being added to AstroVma with along with three PhotDatabase tables (varstar, graph and graphlayer) and new UI forms (VarStarsForm and GraphConfigForm) to support the creation of configurations that allow Protometric Charts to be easily created and updated by AstroMain.  AstroMain however needs to be modified to read graph configurations from the PhotDatabase instead of reading hard-coded configurations.  Being implemented in AstroMain 3.81.12. and tested with 'T CrB' but need to be made generic and work with any VarStar/Object.
  Done  2026-05-06 (AstroMain 3.81.12)
   
• Incorporate a check for Eaton UPS in DeviceManger when last UPS alert is showing "Communication with UPS has failed". AstroMain (and AstroWeather/AstroAllSky) can not directly determine the current state of the UPS - it can not read the UPS like the Eaton UPSCompanion server and UI form do - and has to infer the state of the UPS based on the last alert/notifcation generated and written to the euc.log file.  This generally works ok during normal operations. However if the USB cable to the UPS box is removed (as might happen when computer was removed from the Observatory over the last few days), the last message in the log file is "Communication with UPS has failed" (see Fig 3). There is no corresponding message to say the 'Communication with UPS has restored'. Hence AstroMain can only infer that UPS is not connected (and therefore its power state is unknown). The only way round this is to briefly turn off the power to UPS and then turn it on again.  This generates new alert message finishing with "The system is powered by the utility" and inferences can then be correctly made again.  It is proposed to incorporate a "IsEatonUPSConnected()" routine into AstroMain that can establish whether Device Manager contains a 'Eaton UPS'  item or not and modify reporting/actions accordingly. A trial implemented has been included in AstroMain 3.82.5 / 3.28.6, but needs to be tested by unplugging and replugging the USB cable to Eaton UPS box.
    Done  2026-05-28 (AstroMain 3.82,6, Eaton UPS, DeviceManager)
   
• Consider the value of upgrading PemProV2 to PemProV3. CCDWare's PemPro is a tool for correcting a mount's periodic error, polar alignment and baklash using a Camera to improve tracking and guiding. It has has been used in past for analysing and updating periodic error on the Observatory's 12" LX200 Telecope using CCDSoft for star capture. However the scope's PEC file hasn't been updated for some time and is due a 'refresh'. A survey of 9 PemPro users reported that average PE for LX200 GPS Telescopes went from 45.9" before to 7.5" after PEC. The Obervatory currently has a license to use PemPro v2 only.  The current version of PemPro is V3, but the license upgrade cost is $75.  Several features in the new V3 version are still reported as 'coming soon'. Is there any benefit over spending the upgrade cost.  New features in V3 relating specifically to Periodic Error Correction are:
  - The Create PEC curve window has improvements to better select wanted and filter unwanted frequencies
  - A new 3D FFT graph shows frequency/time relationships
  - One-click PEC automated the whole process of programming periodic error for some mounts (coming soon)
  - Programmable API to automate PEMPro (coming soon)
  To do 2026-05-08+ (PemPro)

[ Prev | Next ]

Back to Top Issue,  Back to Top

[ Prev | Next ]

Back to Top Issue,  Back to Top