David's Astronomy - Notes 2025-10-20 (S1369)

David's Astronomy Pages
Notes - Session 1369 (2025-10-20)

Notes
(S1368)

Notes
Main

Home
Page

Notes
(S1370)

	2025-10-26

	Session Aims & Highlights
	- Observing Result - Night Summary Plot - Session Event Log

	Operational Issues
	- Critical Issues (0), Major Issues (1), Minor Issues (4), Small Defects (0), Continuous Improvement (5)
	- Figures (5)

	Images from 2025-10-20 >>

	Observatory Computer - BIOS Upgrade from v303 to v318 to enable TPM 2.0 & meet Windows 11 requirements

Session Aims & Highlights (2025-10-20)

Main aims

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.78.1, AstroPlan 1.43.14, AstroShCap 1.3.16, AstroGuard 1.12 (any new items or versions in bold)
AstroMag 1.5.9, AstroVOE 1.15.1, AstroSN 1.14, AstroProtect 1.10.6, AstroMove 1.16.2
AstroWeather 1.28, AstroAllSky 3.25, AstroObsCam 1.11.7, AstroNorthCam 1.6.2, AstroLaunch 1.13.6

Highlights

Targets. 3/24 planned targets were completed with 6 targets partially completed. Other planned targets failed due to cloud. Images from 2 targets (Gilese 65, UGC 5695 w/SN2025cfc) were later rejected due to cloud.
CCD Camera. No issues with CCD Camera during session.
Dome. There were no issues opening/closing the shutter during the session, and dome was closed ok at end of session. However it wasn't parked correctly at end of session (due to dome azimuth discrepency of 15°) and may have been operating in a state that sky views were partially occluded by the dome's roof. Issue has been subsequently fixed (2025-10-22, see notes-2025-10-20.htm#Major_Issues)

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:23:49		Session Monitoring	AutoStart monitoring for Live Session opportunity between 23:23 & 06:08
23:23:52		Session AutoStarting	Session autostarting (23:23)
23:24:06		CCDSoft Restarting	CCDSoft being restarted (to set AutoSave No.)
23:24:20		Session Created	Session Created (Live, 2025-10-20 S01369, ImageSaveNum: 1369001)
23:24:29		Scope Switched On	Telescope Power has been switched on via UPB Switch
23:26:17		Services Started	Observatory Services started
23:26:31		Observatory (Auto)	Observatory placed in Fully-Automated Mode
23:26:33		Session Pending	Session pending (2025-10-20)
23:26:35		Session Initiating	Session initiating (2025-10-20)
23:26:55		Camera1 Connected	SBIG Camera connected (Set point -10°C)
23:27:01		Plan Requested	Observing Plan requested from AstroPlan (1.43.14)
23:27:55		Plan Loaded	Observing Plan loaded to queue (Plan ID: 1156)
23:28:43		Telescope Connected	Telescope connected (TheSky6)
23:29:25		Session Equilibration	Session ready to Open Dome
23:30:11		Dome Opened	Dome opened (Opening time 45s, Zigbee 40s)
23:30:13		Session Running	Session running
23:30:16		Queue Started	Observing Queue started (24 targets selected)
23:30:19		Target Started (NrZen)	Target started (Focus Field 0, HIP 106)
23:30:34		Dome Unparked	Dome unparked
23:35:11		Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
23:38:17		Focusing Completed	Foc1 AutoFocus Completed (Profile No 1, wide)
23:40:48		Focusing Completed	Foc1 AutoFocus Completed (Profile No 1)
23:40:50		Focusing Started-Foc2	Foc2 Focusing Started (Secondary Scope, using ShCap)
23:42:30		Focusing Completed	Foc2 AutoFocus Completed (Profile No 2, wide)
23:43:56		Focusing Completed	Foc2 AutoFocus Completed (Profile No 2)
23:44:15		Target Completed (NrZen)	Target completed (Focus Field 0, HIP 106)
23:44:28		Target Started (1/24)	Target started (1/24, GCVS CY Lyr)
23:52:43		Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
23:54:42		Focusing Completed	Foc1 AutoFocus Completed (Profile No 3)
23:58:35		Target Completed	Target completed (1/24, GCVS CY Lyr)
23:58:39		Target Started (2/24)	Target started (2/24, GCVS HH And)
00:05:29		Target Completed	Target completed (2/24, GCVS HH And)
00:05:34		Target Started (3/24)	Target started (3/24, M31 w/Nova M31 AT2025wwe)
00:09:37		Critical Cloud Alert	Critical Cloud Alert (Obs.Manager will close the Dome)
00:09:39		HardSuspend Called	Hard Suspend called due to Critical Conditions (cloud)
00:09:42		Target Aborted (3/24)	Target aborted (3/24, M31 w/Nova M31 AT2025wwe) due to cloud
00:09:44		Queue Paused	Queue paused for Session Suspension
00:09:47		Session Suspending	Session suspending
00:10:32		Dome Closed	Dome closed (Closing time 46s, Zigbee 43s)
00:10:35		Session Suspended	Session suspended
00:21:20		Target Cancelled	Target cancelled (3/24, M31 w/Nova M31 AT2025wwe) due to cloud
00:43:20		Target Cancelled	Target cancelled (4/24, UGC 1206 w/SN2025pao) due to cloud
01:17:44		Session Resuming	Session resuming
01:18:04		Target Missed (5/24)	Target's time slot was missed (5/24, WHL0137-08)
01:18:28		Dome Opened	Dome opened (Opening time 45s, Zigbee 40s)
01:18:31		Session Running	Session running
01:18:33		Queue Resumed	Observing Queue resumed
01:18:36		Target Started (6/24)	Target started (6/24, Gliese 65)
01:25:40		Focusing Skipped	Foc1 focusing skipped - unable to find a star (TCF-LSI)
01:32:45		Critical Cloud Alert	Critical Cloud Alert (Obs.Manager will close the Dome)
01:32:47		HardSuspend Called	Hard Suspend called due to Critical Conditions (cloud)
01:32:49		Target Aborted (6/24)	Target aborted (6/24, Gliese 65) due to cloud
01:32:52		Queue Paused	Queue paused for Session Suspension
01:32:54		Session Suspending	Session suspending
01:33:40		Dome Closed	Dome closed (Closing time 50s, Zigbee 43s)
01:33:42		Session Suspended	Session suspended
01:46:14		Target Cancelled	Target cancelled (7/24, GSC 1224:29) due to cloud
01:55:55		Target Cancelled	Target cancelled (8/24, GCVS GK Per) due to cloud
02:04:33		Target Cancelled	Target cancelled (9/24, WDS GRB 34) due to cloud
02:13:57		Target Cancelled	Target cancelled (10/24, GCVS BL Lac) due to cloud
02:23:48		Target Cancelled	Target cancelled (11/24, GCVS EV Lac) due to cloud
02:35:18		Target Cancelled	Target cancelled (12/24, AT2022vdr (CV)) due to cloud
02:55:19		Target Cancelled	Target cancelled (13/24, GCVS GW Ori) due to too few stars
03:02:00		Session Resuming	Session resuming
03:02:45		Dome Opened	Dome opened (Opening time 45s, Zigbee 40s)
03:02:48		Session Running	Session running
03:02:50		Queue Resumed	Observing Queue resumed
03:02:52		Target Started (14/24)	Target started (14/24, C/2022 N2 (PANSTARRS))
03:05:05		Critical Cloud Alert	Critical Cloud Alert (Obs.Manager will close the Dome)
03:05:07		HardSuspend Called	Hard Suspend called due to Critical Conditions (cloud)
03:05:10		SoftSuspend Called	Soft Suspend called due to Deteriorating Conditions (too few stars)
03:05:12		Target Aborted (14/24)	Target aborted (14/24, C/2022 N2 (PANSTARRS)) due to cloud
03:05:14		Queue Paused	Queue paused for Session Suspension
03:05:17		Session Suspending	Session suspending
03:06:06		Dome Closed	Dome closed (Closing time 49s, Zigbee 43s)
03:06:08		Session Suspended	Session suspended
03:09:51		Target Cancelled	Target cancelled (14/24, C/2022 N2 (PANSTARRS)) due to
03:09:54		Session Resuming	Session resuming
03:10:36		Dome Opened	Dome opened (Opening time 44s, Zigbee 40s)
03:10:39		Session Running	Session running
03:10:42		Queue Resumed	Observing Queue resumed
03:10:44		Target Started (15/24)	Target started (15/24, NGC 7753 w/SN2025kyg)
03:15:37		SoftSuspend Called	Soft Suspend called due to Deteriorating Conditions (too few stars)
03:15:39		Critical Cloud Alert	Critical Cloud Alert (Obs.Manager will close the Dome)
03:15:41		HardSuspend Called	Hard Suspend called due to Critical Conditions (cloud)
03:15:43		Target Aborted (15/24)	Target aborted (15/24, NGC 7753 w/SN2025kyg) due to cloud
03:15:45		Queue Paused	Queue paused for Session Suspension
03:15:47		Session Suspending	Session suspending
03:16:31		Dome Closed	Dome closed (Closing time 49s, Zigbee 43s)
03:16:35		Session Suspended	Session suspended
03:25:03		Session Resuming	Session resuming
03:25:48		Dome Opened	Dome opened (Opening time 45s, Zigbee 40s)
03:25:50		Session Running	Session running
03:25:52		Queue Resumed	Observing Queue resumed
03:25:55		Target Started (15/24)	Target started (15/24, NGC 7753 w/SN2025kyg)
03:35:19		Target Completed	Target partially completed (15/24, NGC 7753 w/SN2025kyg)
03:35:23		Target Started (16/24)	Target started (16/24, M31 w/Nova M31 2025-10a?)
03:39:07		Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
03:42:27		Focusing Completed	Foc1 AutoFocus Completed (Profile No 4)
03:58:46		Target Completed	Target completed (16/24, M31 w/Nova M31 2025-10a?)
03:58:50		Target Started (17/24)	Target started (17/24, GCVS U And)
03:59:17		Critical Cloud Alert	Critical Cloud Alert (Obs.Manager will close the Dome)
03:59:19		HardSuspend Called	Hard Suspend called due to Critical Conditions (cloud)
03:59:21		SoftSuspend Called	Soft Suspend called due to Deteriorating Conditions (too few stars)
03:59:31		Target Aborted (17/24)	Target aborted (17/24, GCVS U And) due to cloud
03:59:33		Queue Paused	Queue paused for Session Suspension
03:59:35		Session Suspending	Session suspending
04:00:21		Dome Closed	Dome closed (Closing time 49s, Zigbee 43s)
04:00:23		Session Suspended	Session suspended
04:09:47		Target Cancelled	Target cancelled (17/24, GCVS U And) due to cloud
04:22:38		Target Cancelled	Target cancelled (18/24, AT2025md (CV)) due to cloud
04:34:58		Target Cancelled	Target cancelled (19/24, AT2025lc (CV)) due to cloud
04:44:51		Session Resuming	Session resuming
04:45:36		Dome Opened	Dome opened (Opening time 45s, Zigbee 40s)
04:45:39		Session Running	Session running
04:45:40		Queue Resumed	Observing Queue resumed
04:45:45		Target Started (20/24)	Target started (20/24, AT2025ygh)
04:45:54		Target Failed (20/24)	Target failed due to dec limit (20/24, AT2025ygh)
04:58:02		Target Started (21/24)	Target started (21/24, UGC 3458 w/SN2025yao)
05:03:47		Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
05:06:59		Focusing Completed	Foc1 AutoFocus Completed (Profile No 5)
05:22:06		Critical Cloud Alert	Critical Cloud Alert (Obs.Manager will close the Dome)
05:22:08		HardSuspend Called	Hard Suspend called due to Critical Conditions (cloud)
05:22:12		Target Aborted (21/24)	Target aborted (21/24, UGC 3458 w/SN2025yao) due to cloud
05:22:14		Queue Paused	Queue paused for Session Suspension
05:22:15		Session Suspending	Session suspending
05:23:06		Dome Closed	Dome closed (Closing time 50s, Zigbee 43s)
05:23:09		Session Suspended	Session suspended
05:25:11		Session Resuming	Session resuming
05:25:56		Dome Opened	Dome opened (Opening time 45s, Zigbee 40s)
05:25:59		Session Running	Session running
05:26:01		Queue Resumed	Observing Queue resumed
05:26:03		Target Started (22/24)	Target started (22/24, UGC 5695 w/SN2025cfc)
05:38:27		SoftSuspend Called	Soft Suspend called due to Deteriorating Conditions (too few stars)
05:38:32		Critical Cloud Alert	Critical Cloud Alert (Obs.Manager will close the Dome)
05:38:34		HardSuspend Called	Hard Suspend called due to Critical Conditions (cloud)
05:38:40		Target Aborted (22/24)	Target aborted (22/24, UGC 5695 w/SN2025cfc) due to cloud
05:38:42		Queue Paused	Queue paused for Session Suspension
05:38:44		Session Suspending	Session suspending
05:39:32		Dome Closed	Dome closed (Closing time 50s, Zigbee 44s)
05:39:36		Session Suspended	Session suspended
06:01:37		Target Cancelled	Target cancelled (23/24, NGC 3106 w/SN2025aauj) due to cloud
06:17:41		Session Resuming	Session resuming
06:18:26		Dome Opened	Dome opened (Opening time 44s, Zigbee 40s)
06:18:30		Session Running	Session running
06:18:32		Queue Resumed	Observing Queue resumed
06:18:34		Target Started (24/24)	Target started (24/24, 29P/Schwassmann-Wachmann)
06:40:05		Target Completed	Target partially completed (24/24, 29P/Schwassmann-Wachmann)
06:40:07		Queue Completed	Job Queue completed
06:40:09		Session Closing	Session closing
06:41:04		Dome Closed	Dome closed (Closing time 50s, Zigbee 44s)
06:41:31		Dome Parked	Dome parked (parking time 16s), Az: 90.0 deg
06:42:47		Telescope Parked	Telescope parked (parking time 57s total)
06:43:11		Telescope State	Handbox reads 'Scope parked Turn scope off.'
06:43:41		Telescope Switched Off	Telescope Power has been switched off via UPB Switch.
06:45:06		Services Stopped	Night Services stopped
06:45:09		Session Finishing	Session Finishing started (Create Fits Summary, Transfer Files)
06:45:26		Dome (Find Park)	Find Park started (Search Az 80.0 to 100.0°, Step 1.0°, Wide)
06:46:40		Dome	Find Park failed (Unable to detect Park Sensor in the range searched)
06:46:44		Session Finished	Session Finished

Session Alerts & Alarms

Time		Type			Name	Detail
--					No Alerts	--

Back to Top

Operational Issues (2025-10-20 S1369)

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

[ Prev | Next ]

Critical Issues

None

Major Issues

Dome wasn't parked corrrectly at end of session. Dome was slewed to Park Azimuth (90°) at end of session during Closing Stage and a search of Park Position was commenced during finishing stage which saw the dome make a wide search from 80° to 100°, but was able to find the Zigbee Park Sensor. The dome was left at 100°. Dome was noticed to be lying at a physical position 116° (and implies that the park position was at 74° (an azimuth discrepency of 16°). The dome calibration has clearly drifted at some point prior to S1365 & S1368 sessions and is reaching the point that park search routine looking at a +/-10° search window can not find the park position, and meaning that the shutter battery can not commence recharging without user interventation post-session. The same issue affected the previous session (2025-09-28) and has occurred even though the dome was recalibrated. Problem was eventually tracked down as being due to a weakly tensioned rotation sensor wheel (that was estimated to be measuring rotations to only 95% accuracy). Issue fixed on 2025-10-22 using a new tighter length of elastic banding. The issue was confirmed to have been fixed during the following S1370 session (2025-10-27) with the dome being successfully parked at end of session , with a total net dome azimuth discrepency of only 0.2 degs.
Fixed 2025-10-22 (Pulsar Dome)

Minor Issues

A black spodge has been present on the AllSkyCamera image for around one month and spoils images. Something is causing a black, light occluding splodge on the AllSkyCamera image due to dirt or some object (see Fig 1). The dirt doesn't lie on the perspex hemisphere and a wipe over the surface of fisheye lens in late September (2025-09-27) didn't resolve the problem. The fisheye lens was wiped over again on 2025-10-22 but again it didn't fix the issue and it was hypothesized that the splodge might be inside the optics (on the bottom of the fish eye lens or on top of the CCD Sensor)
- The black splodge appears first in the image frame taken at 2025-09-20 04:35:20 (03:35:20 UT) during a period of spider activity, and is presumed to be a spider eggsac (see Fig 2 and Video showing spider activity and the appearance of black splodge on 2025-09-20 04:35). How the spider could have got inside the camera's optics is unclear (with the fish eye lens screwed to the camera's internal body it is hard to imagine the presence of any sort of path way). Accessing the internal optics near the camera sensor which will be difficult, as the camera body can no longer be opened.
- A help request has been sent to Starlight Xpress on 2025-10-23 regarding how to open up the camera optics in order to remove the object (eggsac) and the following response was recieved "You can unscrew the ring that holds the dome in place. Once removed, you can then unscrew the lens from the front of the camera and look down on to the CCD to see if there is anything on the CCD or on the lens itself". Michael Hattey from Starlight Xpress also couldn't see how a spider would get behind the lens/on the CCD.
- Although the surface of the fish-eye lens was wiped / cleaned on two occasions (2025-09-27 & 2025-10-22) the southward facing side of the lens was not directly visible from the ladder placed next to the mast on which the camera is mounted, and it was not possible to confirm that the assumed eggsac had been removed/cleaned by cleaning. The surface of the fish eye lens will therefore be examined in more detail first (before moving to the unscrewing/removal of the fish eye lens).
- Viewing the top surface with a mirror on 2025-10-27 finally revealed the presence of the object that has been causing the 'black' splodge on AllSky Camera images. A photo of the top surface was captured with a phone camera (see Fig 3). It appears to be consistent with an eggsace (now flattened or empty) whose deposition by a spider was captured a month earlier. With the object presence & position confidently established a fresh attempt was made to remove it with a dampened paper towel. However it was stubbornly stuck to the lens surface and remained in place (explaining why the earlier casual cleaning didn't work). A second, firmer cleaning of the lens finally removed the object. Images collected on the night 2025-10-27 confirmed that the issue has been fixed.
- There are scratches / blemishes of the polycarbonate hemisphere/dome which can't be fixed by cleaning (a new dome was ordered under a separate ticket on 2025-10-22)
Fixed 2025-10-227 (AllSky Camera)
AstroMain's 'Estimate Mag Limit' function fails when number of stars in image is <10. The 'Estimate Mag Limit' routine uses linked stars with catalog magnitude to calculate the calibrated magnitude of faint stars and to infer the limiting magnitude of the image under analysis. When the image contains few comparison stars (e.g. only 6 stars) the routine failures with message like
"OBJCT006 Fail Error: command failed".
The FITs header for file 'IC_2567.20250929.im1368238-42.av5x180s.C.FIT ' contains catalog RA/Dec and magnitude data for the 6 comparison in keywords 'OBJCT000' to 'OBJCT005'. Investigating code in EstimateMagLimit() routine shows a loop that attempts to access keywords for 10 stars ('OBJCT000' to 'OBJCT009') and if the FIT file doesn't contain the keyword (eg 'OBJCT006') and resulting exception is caught and error message is produced and the routine exited (via an 'Exit Sub' line). Fixed in AstroMain 3.78.2.
Fixed 2025-10-24 (AstroMain 3.78.2)
Observatory Computer began producing a 'Something Went Wrong [0x8019000]' error dialog when restarting (2025-10-25). After installing MyASUS and attempting to use its System Update facility to update the computer to the latest ASUS Bios version (see notes) the computer began producing a 'Something Went Wrong 0x8019000' error dialog each time that computer was restarted (See Fig 4) and 'Cancel' button has to be used to dismiss the dailog and stop the running process. The ASUS Bios was subsequently updated to the latest using a different method that involved downloading the latest BIOS installer file (from the ASUS Support Page) and running it in Windows, however the 'Something Went Wrong' dialog continued to appear after restarting the computer. This variety of the issue resolved itself after update to Window 11 on 2025-10-29, but seems to have been replaced instead by a 'Something Went Wrong [7a6ca]' error upon restarting the computer. It also seems to have evolved somewhat or widened (see Fig 4b) with an error tag of '7q6ca' . Apparently the 7q6ca' tag points to "a Microsoft Office sign-in issue that can often be resolved by updating and repairing Office, resetting credentials, checking network settings, or disabling add-ins. Other solutions include checking your device's time and date settings and ensuring relevant services, like the "Web Account Manager" service, are enabled". On one restart, cancelling the dialog simply saw the dialog appear again after 5s or so. Eventually stopped the dialogs from repeatedly appearing by killing the WWH task. MyASUS was uninstalled 2025-11-05, to follow-up & fulfil an earlier idea if the issue continued. The issue has been elevated from 'Small Defect' to 'Minor Issue' on 2025-11-05. Ticket closed, as not directly relevant since move to Windows 11. New 'Something Went Wrong' issue (post Windows 11 upgrade) covered under notes 2025-10-29.
Closed 2025-11-05 (Observatory Computer / Restart)
Issue with rain sensor values between 2025-10-03 and 2025-10-20. After earlier issue with rain sensor values coming from the Eurotech CloudSensor during earlier Oct 2025, a fix was implemented 2025-09-16 (MI S1363A) to adjust rain values back to original value range using the formula "correct value = (raw value + 200) * 0.25". This was generally worked ok since, however continuous high rain values (>25) were generated during the period from 2025-10-03 (starting around 13:00) to 2025-10-20. The values dropped went back to new normal (raw dry = - 202) on 2025-10-21 though values after two subsequent rain events have been slow to return back to dry values (potentially high humidity/condensation). Investigating showed that during the problem period the raw rain values temporarily returned to normal values (raw dry = - 0.5) , but were made invalid by the application of the correction formula. During part of the time (2025-10-19 22:00 to 2025-10-20 04:00) there have been very anomalous raw rain sensor values between -300 and -900, which a different, more aggressive correction formula would have been necessary. Whilst things are stable now all told things to the likely need for a replacement rain sensor, particularly as the cloud sensor can no longer trigger the dome relay in event of rain. Eurotech (2025-11-03) suggest temporarily bringing the sensor indoors and thoroughly drying out the electonics, and cleaning the sensor heads.
To monitor and consider way forward 2025-10-22 (CloudSensor,Dome Protection)

Small Defects

None

Continuous Improvement

Dome should be slewed to 90° in the event that 'Search For Park Position' fails. At end of S1368 & S1369 sessions a search for Park Position was automatically made during which a wide search was made from 80° to 100°, but in both cases the search was able to find the Zigbee Park Sensor and the dome was left at Az 100°. AstroMain should be modified so that the dome is moved to the 90° position instead of being left at 100°. AstroMain was also modified to store a Session Alert when the search fails to find the park sensor in range specified. Implemented in AstroMain 3.78.2.
Done 2025-10-22 (AstroMain 3.78.2)
Upgrade AllSky/Weather Computer to Windows 11. AllSky/Weather Computer is currently running Windows 10, which is no longer supported by Microsoft as of 2025-10-14. Upgrading the computer including installing Windows 11, reinstallation of all necessary software programs (id necessary), checking, testing and resolving all teething issues, will take 1-4 days. Update to Windows11 successfully achieved on 2025-10-28, taking around 4 hours, excluding precaution back-up of key files & settings. Fortunately there was no requirement to reinstall applications, though CCDSoft DLL's had to be copied into 'C:\Program Files (x86)\Common Files\System' from a pre-prepared restoration folder.
Done 2025-10-28 (AllSky/Weather Computer)
Upgrade Observatory Computer to Windows 11. AllSky/Weather Computer (ASUS ExpertBook, P245FA.303, Core i7-10510U ) is currently running Windows 10, which is no longer supported by Microsoft as of 2025-10-14. Upgrading the computer including installing Windows 11, reinstallation of all necessary software programs (i necessary), checking, testing and resolving all teething issues, will take 1-4 days.. Since observatory operations will be affected during this time there may be benefit in upgrading the AllSky//Weather Computer to Window 11 at the same time. However there may be risks if both computers have issues that prevent inter-related functions, and it proposed to upgrade the AllSky/Weather Computer first and the Observatory Computer second. PC Health Checks against the Observatory Computer 2025-08-12 (see notes 2025-08-12) indicated that the computer did not meet Windows 11 system requirements with the message "TPM 2.0 must be supported and enabled on this PC, TPM not detected". This problem was resolved on 2025-10-26 by updating computer's BIOS version from v303 to v318 (see Fig 2 on Notes 2025-08-12), confimed by rerunning PC Health Check which showed that the Observatory Computer now meets Windows 11 requirements (see Fig 3 on Notes 2025-08-12) Update to Windows11 successfully achieved on 2025-10-29, taking around 3 hours, excluding precautionary back-up of key files & settings. Fortunately there was no requirement to reinstall applications, though CCDSoft DLL's had to be copied into 'C:\Program Files (x86)\Common Files\System' from a pre-prepared restoration folder.
Done 2025-10-29 (Observatory Computer)

Order and install new perspex dome for Oculus AllSky Camera. There are also scratches and blemishes on the topof the AllSky Camera's dome/hemisphere, like due to birds, and the dome is generally discoloured potentially reducing transmissibility. None of which can be fixed by cleaning. A new dome was ordered from Starlight Xpress today (2025-10-22). Upon eventual arrival of the new perspex dome (2025-11-03) it was fitted to the AllSky Camera. A photo comparing the old and new dome is shown in Fig 5.
Done 2025-11-03 (AllSky Camera)

Make enquiry to Eurotech regarding the rain sensor issues experienced and their 'Aurora' CloudSensor product which is currently out of stock. Enquiry made to Eurotech on 2025-10-22. Waiting on reply as of 2025-11-03. Telephoned Eurotech diret (Tel: 01507 363846 ) who indicated that small batch might be available in the spring. In meantime worth bringing the sensor indoors and allow it to thoroughly dry out for 2-3 days, clean the sensor and reinstall outdoors. Need to look how this would be done given the cabling involved including the adapters and relay connection. A separate Continuous Improvement ticket has been raised to try to renovate the Rain Sensor.
Done 2025-11-03 (Eurotech CloudSensor)

[ Prev | Next ]

Back to Top Issue, Back to Top

Fig 1. Black splodge on AllSky Camera Images (2025-10-20)

Frame Before (04:34:08)

Fig 2. Appearance of black splodge (?spider egg sac) on 2025-09-20 04:35

2a) Earlier Frame - Spider carrying Egg Sac 10 mins before appearance of black splodge (04:25:25)

2b) Frame Before (04:34:08),
30s before appearance of black splodge, spider is close to/at the scene of the crime.

2c) Frame After (04:35:20)
Black splodge has appeared and spider is still in view.

Video showing spider activity and the appearance of black splodge on 2025-09-20 04:35

Fig 3. AllSky Camera - splodge located (2025-10-27)

Although the surface of the fish-eye lens was wiped / cleaned on two occasions (2025-09-27 & 2025-10-22) the southward facing side of the lens was not directly visible from the ladder placed next to the mast on which the camera is mounted, and it was not possible to confirm that the assumed eggsac had been removed/cleaned by cleaning.

Viewing the top surface with a mirror on 2025-10-27 finally revealed the object that has been causing the 'black' splodge on AllSky Camera object. A photo of the top surface was then captured with a phone camera. It appears to be consistent with an eggsace (now flattened/empty) whose deposition by a spider was captured a month earlier. With the object presence & position confidently established a fresh attempt was made to remove it with a dampened paper towel. However it was stubbornly stuck to the lens surface and remained in place (explaining why the earlier 'blind' cleaning didn't work). A second, firmer cleaning of the lens finally removed the object.

Images collected on the night 2025-10-27 confirmed that the issue has been fixed.

Fig 4. 'Something went wrong' dialog after restarting Observatory Computer (2025-10-25)

Fig 5. Comparison of old and new AllSky Camera dome (2025-11-03)

Old Dome showing defecting in surface (only noticeable at certain angles / illumination)

Comparison of Old Dome (Left) and New Dome Right)

[ Prev | Next ]

Back to Top Issue, Back to Top

2025-10-26

Upgrading Observatory Computer BIOS from v303 to v318 to enable TPM 2.0 & meet Windows 11 requirements

Introduction

The Observatory Computer (an ASUS ExpertBook P2451FA, i7-10510U, 8GB RAM, 512GB, 14 Inch Windows 10 ) is still running Windows 10 in Oct 2025, but this is no longer supported by Microsoft as of 2025-10-14. It is planned to upgrade the computer to Windows 11 to maintain security protection etc.

A PC Health Check previously indicated that the computer didn't meet Windows 11 requirements giving the fail message "TPM 2.0 must be supported and enabled on this PC, TPM not detected"

Figure - PC Health Check Result (2025-08-12)

See Issue - Observatory Computer doesn't currently meet Window 11 system requirements (2025-08-12)

Analysis
TPM (Trusted Platform Module) enables secure storage and authentication functions, and is typcially provided by Platform Trust Technology (PTT) that provides TPM capabilities for a computer without needing a separate hardware chip Attempting to run 'TPM.msc' confirmed that TPM was unavaillable.

Since the computer is reasonably high spec and only 3 years old, TPM should theoretically be available, but may require a modification to the system BIOS to make it available.

Attempted Fix (2025-10-25)
An attempt was made on 2025-10-25 to see if TPM 2.0 could be enabled my making an adjustment to the current BIOS. This was done by restarting the computer and entering BIOS setup (F2 at start-up) and looking for a setting where TPM could be enabled. Advanced options were searched looking for 'Intel PTT' or 'Trusted Computing'. Unfortunately there didn't seem to be any obvious option or way of enabling PTT / TPM.

After some research it was decided to update the BIOS with a new version as that the currently installed BIOS version (v303) is some 3 or 4 years and the latest version (established to be v318) might have a setting to enable TPM 2.0 or otherwise automatically enables TPM 2.0. The first attempt to install Latest BIOS was made by downloading/installing MyASUS app and using its System Update feature to select/install Latest BIOS, however the installation failed for some unknown reason.

Final Fix (2025-10-26)
After some more reseach, a second attempt was made the following day by downloading the relevant latest BIOS Installer executable (ASUS_P2451FA_318_BIOS_Update_1.exe) from ASUS Support Page by searching under using the computer's Serial Number to find the correct support files.

The installer was run via Windows to update the BIOS to v318.

Figure - ASUS P2451FA.318 Bios Installation (2025-10-26)

After BIOS Installation and Computer Restart a quick check comfirmed that the computer was functioning ok under Windows, and was using the v318 bios, confirming that the BIOS had been successfully updated from v303 to v318

Figure - System Information post BIOS upgrade (2025-10-26)

Computer was restarted again and F2 button held down to allow the BIOS Interface to be entered. Searching Advanced options failed to find one for enabling PTT/TPM.

However after exiting the BIOS and entering Windows, running the command "TPM.msc" indicated that TPM 2.0 was present and enabled :

Figure - TMP Management Window confirming TPM 2.0 is ready to use (2025-10-26)

Running the PC Health Check again, now generates the result "TPM 2.0 enabled on this PC" and "This PC meets Windows 11 requirements"

Figure - PC Health Check on Observatory Computer after upgrading BIOS from v303 to v318 (2025-10-26) - TPM 2.0 enabled.

This Web Page:	Notes - Session 1369 (2025-10-20)
Last Updated :	2025-12-21
Site Owner :	David Richards
Home Page :	David's Astronomy Web Site