David's Astronomy Pages Notes - Session 1426 (2026-04-28)

Notes (S1425)

Notes Main

Home Page

Notes (S1427)

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

Session Aims & Highlights (2026-04-28)

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. 13/13 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 23:31:14 Session Monitoring AutoStart monitoring for Live Session opportunity between 23:31 & 03:26 23:31:15 Session AutoStarting Session autostarting (23:31) 23:31:21 Session Created Session Created (Live, 2026-04-28 S01426) 23:31:24   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.) 23:31:43   Scope Switched On Telescope Power has been switched on via UPB Switch 23:33:30   Services Started Observatory Services started 23:33:40 Observatory (Auto) Observatory placed in Fully-Automated Mode 23:33:43 Session Pending Session pending (2026-04-28) 23:33:45 Session Initiating Session initiating (2026-04-28) 23:34:08   Camera1 Connected SBIG Camera connected (Set point -20°C) 23:34:12   Plan Requested Observing Plan requested from AstroPlan (1.46.2) 23:35:22   Plan Loaded Observing Plan loaded to queue (PlanID: 1226) 23:36:04   Telescope Connected Telescope connected (TheSky6) 23:36:29 Session Equilibration Session ready to Open Dome 23:37:14   Dome Opened Dome opened (Opening time 45s, Zigbee --) 23:37:16 Session Running Session running 23:37:18   Queue Started Observing Queue started (13 targets selected) 23:37:24     Target Started (NrZen) Target started (Focus Field 13, HIP 63666) 23:37:38       Dome Unparked Dome unparked 23:42:17       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:44:54       Focusing Completed Foc1 AutoFocus Completed (Profile No 1, wide) 23:47:00       Focusing Completed Foc1 AutoFocus Completed (Profile No 1) 23:47:09       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 23:49:05       Focusing Completed Foc2 AutoFocus Completed (Profile No 2, wide) 23:50:56       Focusing Completed Foc2 AutoFocus Completed (Profile No 2) 23:51:17     Target Completed (NrZen) Target completed (Focus Field 13, HIP 63666) 23:51:22     Target Started (1/13) Target started (1/13, NGC 4205 w/SN2026fvx) 23:55:50       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:58:30       Focusing Completed Foc1 AutoFocus Completed (Profile No 3) 00:14:32     Target Completed Target completed (1/13, NGC 4205 w/SN2026fvx) 00:14:37     Target Started (2/13) Target started (2/13, NGC 4914 w/SN2026fjc) 00:19:24       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:22:03       Focusing Completed Foc1 AutoFocus Completed (Profile No 4) 00:38:20     Target Completed Target completed (2/13, NGC 4914 w/SN2026fjc) 00:38:25     Target Started (3/13) Target started (3/13, NGC 5907 w/SN2026kid) 00:42:35       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-LSI) 00:58:40     Target Completed Target completed (3/13, NGC 5907 w/SN2026kid) 00:58:45     Target Started (4/13) Target started (4/13, T CrB) 01:02:27       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:04:51       Focusing Completed Foc1 AutoFocus Completed (Profile No 5) 01:09:02     Target Completed Target completed (4/13, T CrB) 01:09:06     Target Started (5/13) Target started (5/13, NGC 6070 w/SN2026ejy) 01:13:02       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-LSI) 01:29:13     Target Completed Target completed (5/13, NGC 6070 w/SN2026ejy) 01:30:57     Target Started (6/13) Target started (6/13, GCVS CY Lyr) 01:35:12       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:37:28       Focusing Completed Foc1 AutoFocus Completed (Profile No 6) 01:41:48     Target Completed Target completed (6/13, GCVS CY Lyr) 01:41:53     Target Started (7/13) Target started (7/13, IC 4556 w/SN2026fuz) 01:46:23       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:48:43       Focusing Completed Foc1 AutoFocus Completed (Profile No 7) 02:04:48     Target Completed Target completed (7/13, IC 4556 w/SN2026fuz) 02:04:52     Target Started (8/13) Target started (8/13, UGC 11058 w/SN2026ewd) 02:08:28       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:10:40       Focusing Completed Foc1 AutoFocus Completed (Profile No 8) 02:27:30     Target Completed Target completed (8/13, UGC 11058 w/SN2026ewd) 02:27:34     Target Started (9/13) Target started (9/13, AT2026iul (CV)) 02:31:07       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:33:22       Focusing Completed Foc1 AutoFocus Completed (Profile No 9) 02:39:40     Target Completed Target completed (9/13, AT2026iul (CV)) 02:39:44     Target Started (10/13) Target started (10/13, GCVS BL Lac) 02:43:02       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:45:21       Focusing Completed Foc1 AutoFocus Completed (Profile No 10) 02:49:10     Target Completed Target completed (10/13, GCVS BL Lac) 02:49:14     Target Started (11/13) Target started (11/13, AT2026jyw) 02:53:53       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-LSI) 03:09:57     Target Completed Target completed (11/13, AT2026jyw) 03:10:52     Target Started (12/13) Target started (12/13, AT2026hur) 03:14:26       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:16:50       Focusing Completed Foc1 AutoFocus Completed (Profile No 11) 03:32:51     Target Completed Target completed (12/13, AT2026hur) 03:33:12     Target Started (13/13) Target started (13/13, HIP 87937) 03:35:18       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:37:37       Focusing Completed Foc1 AutoFocus Completed (Profile No 12) 03:40:54     Target Completed Target completed (13/13, HIP 87937) 03:40:57   Queue Completed Job Queue completed 03:40:59 Session Closing Session closing 03:41:46   Dome Closed Dome closed (Closing time 49s, Zigbee 0s) 03:42:29   Dome Parked Dome parked (parking time 36s), Az: 90.0 deg 03:43:07   Telescope Parked Telescope parked (parking time 34s total) 03:43:31   Telescope State Handbox reads 'Scope parked Turn scope off.' 03:44:28   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 03:45:53   Services Stopped Night Services stopped 03:45:56 Session Finishing Session Finishing started (Create Fits Summary, Transfer Files) 03:46:33     Dome (Find Park) Find Park started (Search Az 88.0 to 92.0°, Step 0.2°, Narrow) 03:47:20     Dome Find Park found (Best Park Az 90.4°) 03:47:26     Dome Dome has been synced at park position (Az 90.0°, Adjustment: -0.4°) 03:47:28   Dome Parked Dome parked 03:50:26   Dome Charging Dome is parked and well charged (97%, 15.0v) 03:50:28 Session Finished Session Finished

Session Alerts & Alarms

Time     Type       Name Detail 03:50:26 Yellow Alert Dome Charging Dome is parked and well charged (97%, 15.0v)

Back to Top

Operational Issues (2026-04-28 S1426)

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

[ Prev | Next ]

Critical Issues

• None

Major Issues

• Unable to start Visual Studio 2022 in order to confirm successful build of latest AstroMain version (pre-session). Prior to publishing latest AstroMain 3.81.11 version from the Development Comuter to the Observatory Computer, it was necessary to confirm successful building of the AstroMain version in Visual Studio (VS 2022). Each timeVisual Studio tried to be opened a dialog would appear stating that that the Visual Studio program couldn't be started as a setup was in progress.  This is believed to be related to a behind the scene update of Visual Studio being made when the computer was forcibly shut-down earlier due to an issue with Windows hanging.  Starting Visual Studio Installer showed that the set-up had failed and that Visual Studio 2022 no longer appeared an installed product. The set up failed 'blockage' was got around by deleting a 'status.json' file in the Visual Studio's installation folder.  After then trying to start Visual Studio a dialog appeared indicate twith the message "The 'GlobalHubClientPackage' package did not load correctly.”.  After dismissing the message AstroMain prroject was able to be opened and build confirmed and the new executable was uploaded to the Obseratory Computer.  Attempts to fix Visual Studio 2022  in Visual Studio Installer failed, and it it seems that the Visual Studio 2022 is missing certain files that are needed to be recognised by the installer.  Issue worked around and allowed the S1426 session to be run.  Issue with VS 2022 was worked around by installing the new VS 2026 product.
  Resolved 2026-04-29 (Development Computer, Visual Studio)

Minor Issues

• Visual Studio Installer stopped recognising Visual Studio installation. Due to an issue with Development computer hanging there was no option other than to turn off the computer from the Power Button.   This however seem to cause an issue as Visual Studio was been updated in the background.  Whilst the VS setup program was stopped it left Visual Studio in an unstable state.  Although VS2022 could still be run, the Visual Studio Installer stopped recognising the VS2022 installation due to some corruption. Despite several attempts the installation couldn't be repaired and rather than install a fresh installation of VS2022, it was decided to move onto VS2026.   Visual Studio 2026 Community (version 18.5.2) was installed onto the Development Computer. .Net Framework 3.5 Development was installed as a individual component.  It was confirmed that projects from VS2022 still load/build ok in VS2026. In order to not affect software 'publishing' to local computer or observatory computers and project backups (in AstroMove) existing projects will, at least for time being, be left in the './documents/Visual Studio 2022/Projects folder.
  Resolved 2026-04-29 (Development Computer, Visual Studio)
   
• Observatory Computer restart for a windows update stalled, leaving the computer unaccessible from a VNC remote connection (post-session). The Observatory Computer couldn't be connected to remotely when trying to download files in the morning following the overnight session.  AstroWeather running on the AllSky/Weather Computer showed that the connection to the Observatory Computer had been lost at around 06:29, fortunately this was well after the S1426 session had finished. AllSky/Weather Computer and Development both had Windows Updates pending or ready to install. It is conjectured that Windows Update might be involved in the outage of the Observatory Computer, and later examination of Event Monitor logs confirmed that a restart computer operation had been initiated by Window.  Visiting the Observatory later in the morning showed that it was stalled and showing the following boot time message, waiting for user input.
    S.M.A.R.T. Test Warning
  SAMSUNG MZVLQ512HALU00000 S.M.A.R.T Status is Bad.
  Please backup and Replace the Device.
  The warning is a system level indicator that the computer's 0.5 TB NVMe SSD has crossed a manufacturer defined failure threshold. and is close to potential failure. After proceeding with boot, windows updates were installed and computer rebooted (with the same SMART Test Warning) and then proceeded to start Windows Ok.   A separate Continuous Improvement Ticket has been created to acquire and install a new SSD.
  Resolved temporarily 2026-04-29 (Observatory Computer, SSD, User Awareness)

Small Defects

• None

Continuous Improvement

• Modify AstroLaunch's process to launch Visual Studio to point to VS2026.  AstroLaunch currently launches VS 2022  by submitting a .bat file (LaunchVisualStudio.bat), which has the line
     "C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\devenv.exe"
  But now that Visual Studio 2026 has been installed on the Development Computer, AstroLaunch needs modifying to launch VS2026 instead of VS2022.
  Implemented in AstroLaunch 1.14.10 by modifying the .bat file to
     "C:\Program Files\Microsoft Visual Studio\18\Community\Common7\IDE\devenv.exe"
  Done 2026-04-28 (Development Computer, AstroLaunch 1.14.10)
   
• Order and Replace failing SSD drive on Observatory Computer. SMART Test Warnings during booting of the Observatory Computer indicate that its SAMSUUNG SSD drive (0.5 TB) has crossed a manufacturer‑defined failure threshold, and is close to failing. The NVMe (Non-Volatile Memory Express) SSD is user-replaceable, and a new SSD drive has been ordered from Amazon for delivery tomorrow.  The new drive (a  WD_BLACK SN7100 1TB NVMe SSD, M.2 2280 (Read speeds up to 7250 MB/s, Write Speed up to 6,900 MB/s) has twice the capacity of the current drive. A back up System Image will be taken using Macrium Reflect (Trial Version) and a rescue disk created (Macrium Reflect is supposedly more robust than Windows own backup in situations where SSD drive is in the process of failing). After installing the new SSD the system image wil be loaded to the new drive, use Macrium's rescue disk.  Creating a System Image of the existing SSD Drive (with 399 GB Used Space) took around 40 minutes and produced a .mrimgx file of size 157 GB. A rescue Disk (USB Flash Drive) was created and checked as working.  The new SSD drive arrived today (2026-04-30), 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 drive.
  Fixed 2026-05-04 (Observatory Computer,  SSD, Macrium Reflect)

[ Prev | Next ]

Back to Top Issue,  Back to Top