David's Astronomy - Notes 2023-12-02 (S1171)

David's Astronomy Pages
Notes - Session 1171 (2023-12-02)

Notes
(S1170)

Notes
Main

Home
Page

Notes
(S1172)

	2023-12-03

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

	Operational Issues
	- Critical Issues (0), Major Issues (0), Minor Issues (5), Small Defects (3), Continuous Improvement (8)

	Images from 2023-12-02 >>

	Pulsar Dome - Recalibration
	Pulsar Dome - ASCOM Conformance Tests
	Pulsar Dome - Shutter Software Reinstall (Shutter 1.25)

	Zigbee - Smart Plug for Greenhouse Heater

	2023-12-04
	Investigation - OpenWeather JSON Parsing Issue

Session Aims & Highlights (2023-12-02)

Main aims

Targets. Acquire images of a selection of variable stars, nearby stars, comets & deep sky targets as allowed by sky conditions.
Dome Shutter. Check Dome Shutter Communication following issues early in the day.
Dome Slews. Check Dome Slew following Communication following issues early in the day.
12P/Pons-Brooks. Acquire images of Comet 12P/Pons-Brooks which has been undergoing an outburst.
Nebula. Retake interesting Nebula fetaure lying in Mosaic Point 6 seen in TR 37 Mosaic in S1171 session but with more frames and longer exposure.

Equipment & Software

12" LX200 and ST-10XME
80mm APO and ZWO ASI 178MC
CCDApp2, TheSky6, CCDSoft5, DeviceHub 6.6.1.1, MeadeGeneric 1.3.5.414, UPB 1.5, ASCOM 6.6, Pulsar Dome Firmware 1.51 & Driver 6.3.10
Pegasus UPB & Motor Focus, TCF-S
SharpCap 3.2, PHD2 2.6.11dev4, Siril 1.0.6, deCONZ 1.18.2, ASCOM 6.6 SP1
AstroMain 3.64.10, AstroPlan 1.39, AstroShCap 1.3.15, AstroGuard 1.10.2
AstroVOE 1.13 AstroSN 1.10.2, AstroProtect 1.7, AstroMove 1.12.7
(AstroWeather 1.23, AstroAllSky 3.19.7, AstroObsCam 1.11.4, AstroLaunch 1.11.1

Highlights

Targets. 27/45 planned targets observations were completed, with 3 other targets partially completed. One target missed its planned time slots due to insertion of a ToO (GCVS V0390 Cep) into the night's observing queue at around 19:00. Other targets failed due to cloud or session suspension.
Dome Shutter. Dome Shutter operated without issue during the session including two unscheduled Suspend/Resume operations.
Dome Slews. Dome slews worked perfectly following earlier remedial fixes.
12P/Pons-Brooks. Images of Comet 12P/Pons-Brooks were successfully acquired.
Nebula. Images successfully taken of the Nebula feature centered on GCVS V0390 Cep that was seen in Mosaic Point 6 in TR 37 Mosaic in the previous S1171 Session
Dome Parking. Dome wasn't parked at correct physical Az at the end of session, lying at a physical Az 88.2° instead of the required physical Az 90.0° (Error 1.8°). Because of this the Dome didn't automatically begin re-charging at end of session, and had to be rotated to correct position and synced to the park (Az 90.0) by the user. This happened despite performing a Dome Calibration earlier in the day.

Notes:

Summary Plots & Logs

Observing Plan

Observing Result

Dome & Scope Slewing Performance

Slew/Centering Performance

Guiding Performance

Sky Conditions (Locate Frames)

Night Sky Summary Plot
Top axis: Sky Brightness at Zenith (in ADU/s)
Lefthand axis: Local Time (hh LT). Righthand axis: Sun Altitude (degs)

Actual Weather vs Pre-Session Weather Forecast

Session Event Log

Time	Event	Detail
17:41:42	Session Monitoring	AutoStart monitoring for Live Session opportunity between 17:41 & 06:07
17:41:43	Session AutoStarting	Session autostarting (17:41)
17:41:52	CCDSoft Restarting	CCDSoft being restarted (to set AutoSave No.)
17:41:56	Observatory Door	Observatory Door has opened
17:42:11	Observatory Door	Observatory Door has closed (open time 15s)
17:42:17	Camera1 Connected	SBIG Camera connected (Set point -30°C)
17:42:19	Session Created	Session Created (Live, 2023-12-02 S01171, ImageSaveNum: 1171001)
17:42:24	Scope Switched On	Telescope Power has been switched on via UPB Powerbox.
17:44:10	Services Started	Observatory Services started
17:44:17	Observatory (Auto)	Observatory placed in Fully-Automated Mode
17:44:19	Session Pending	Session pending (2023-12-02)
17:44:21	Session Initiating	Session initiating (2023-12-02)
17:44:24	Plan Requested	Observing Plan requested from AstroPlan (1.39)
17:46:05	Plan Loaded	Observing Plan loaded to queue (Plan ID: 945)
17:46:19	Camera1 Connected	SBIG Camera connected (Set point -25°C)
17:46:54	Telescope Connected	Telescope connected (TheSky6)
17:47:19	Session Equilibration	Session ready to Open Dome
17:48:49	Dome Opened	Dome opened (opening time 90s)
17:48:51	Session Running	Session running
17:48:54	Queue Started	Observing Queue started (45 targets selected)
17:48:55	Target Started (NrZen)	Target started (Focus Field 22, HIP 108888)
17:49:09	Dome Unparked	Dome unparked
17:52:38	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
17:54:58	Focusing Completed	Foc1 AutoFocus Completed (Profile No 1, wide)
17:57:01	Focusing Completed	Foc1 AutoFocus Completed (Profile No 1)
17:57:03	Focusing Started-Foc2	Foc2 Focusing Started (Secondary Scope, using ShCap)
17:59:18	Focusing Completed	Foc2 AutoFocus Completed (Profile No 2, wide)
18:01:04	Focusing Completed	Foc2 AutoFocus Completed (Profile No 2)
18:01:21	Target Completed (NrZen)	Target completed (Focus Field 22, HIP 108888)
18:01:26	Target Started (1/45)	Target started (1/45, NGC 7171 w/SN2023yoo)
18:06:12	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
18:08:44	Focusing Completed	Foc1 AutoFocus Completed (Profile No 3)
18:25:11	Target Completed	Target completed (1/45, NGC 7171 w/SN2023yoo)
18:25:15	Target Started (2/45)	Target started (2/45, WDS GRB 34)
18:33:49	Target Completed	Target completed (2/45, WDS GRB 34)
18:33:54	Target Started (3/45)	Target started (3/45, 144P/Kushida)
18:36:58	Focusing Skipped	Foc1 focusing skipped - unable to find a star (TCF-S)
18:48:13	Target Completed	Target completed (3/45, 144P/Kushida)
18:48:18	Target Started (4/46)	Target started (4/46, GCVS V0390 Cep, ToO)
18:51:59	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
18:54:19	Focusing Completed	Foc1 AutoFocus Completed (Profile No 4)
19:03:48	SoftSuspend Called	Soft Suspend is called due to Deteriorating Conditions (too few stars)
19:03:53	SoftSuspend Cancelled	Soft Suspend is cancelled due to improved conditions
19:07:04	SoftSuspend Called	Soft Suspend is called due to Deteriorating Conditions (too few stars)
19:09:24	Target Completed	Target completed (4/46, GCVS V0390 Cep, ToO)
19:09:26	Queue Paused	Queue paused for Session Suspension
19:09:28	Session Suspending	Session suspending
19:10:14	Dome Closed	Dome closed (closing time 50s)
19:10:16	Session Suspended	Session suspended
19:10:44	Target Missed (5/46)	Target's time slot was missed (5/46, AT2021afdl (CV))
19:22:10	Session Resuming	Session resuming
19:23:46	Dome Opened	Dome opened (opening time 95s)
19:23:48	Session Running	Session running
19:23:50	Queue Resumed	Observing Queue resumed
19:23:53	Target Started (6/46)	Target started (6/46, AT2023rfq)
19:36:31	Target Completed	Target partially completed (6/46, AT2023rfq)
19:36:35	Target Started (7/46)	Target started (7/46, AT2023rao (CV))
19:58:35	Target Completed	Target completed (7/46, AT2023rao (CV))
19:58:39	Target Started (8/46)	Target started (8/46, GCVS BL Lac)
20:01:39	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
20:03:37	Focusing Completed	Foc1 AutoFocus Completed (Profile No 5)
20:07:32	Target Completed	Target completed (8/46, GCVS BL Lac)
20:07:36	Target Started (9/46)	Target started (9/46, AT2022szi)
20:10:31	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
20:12:41	Focusing Completed	Foc1 AutoFocus Completed (Profile No 6)
20:29:06	Target Completed	Target completed (9/46, AT2022szi)
20:29:10	Target Started (10/46)	Target started (10/46, 12P/Pons-Brooks)
20:32:42	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
20:34:58	Focusing Completed	Foc1 AutoFocus Completed (Profile No 7)
20:47:03	Target Completed	Target completed (10/46, 12P/Pons-Brooks)
20:47:07	Target Started (11/46)	Target started (11/46, Nova Cas 2021)
20:50:04	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
20:52:03	Focusing Completed	Foc1 AutoFocus Completed (Profile No 8)
21:03:52	Target Completed	Target completed (11/46, Nova Cas 2021)
21:04:09	Target Started (12/46)	Target started (12/46, GCVS TT Ari)
21:07:47	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
21:09:58	Focusing Completed	Foc1 AutoFocus Completed (Profile No 9)
21:16:39	Target Completed	Target completed (12/46, GCVS TT Ari)
21:17:05	Target Started (13/46)	Target started (13/46, AT2022weo)
21:20:38	Focusing Skipped	Foc1 focusing skipped - star is too dim (TCF-S)
21:26:29	Target Completed	Target completed (13/46, AT2022weo)
21:29:25	Target Started (14/46)	Target started (14/46, AT2023srw (CV))
21:32:19	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
21:34:19	Focusing Completed	Foc1 AutoFocus Completed (Profile No 10)
21:40:07	Target Completed	Target completed (14/46, AT2023srw (CV))
21:41:26	Target Started (15/46)	Target started (15/46, UGC 68 w/SN2023xqn)
21:45:05	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
21:47:30	Focusing Completed	Foc1 AutoFocus Completed (Profile No 11)
22:03:18	Target Completed	Target completed (15/46, UGC 68 w/SN2023xqn)
22:03:22	Target Started (16/46)	Target started (16/46, M31 w/Nova M31 AT2023veq)
22:06:02	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
22:07:59	Focusing Completed	Foc1 AutoFocus Completed (Profile No 12)
22:24:00	Target Completed	Target completed (16/46, M31 w/Nova M31 AT2023veq)
22:25:25	Target Started (17/46)	Target started (17/46, GCVS RX And)
22:27:48	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
22:29:49	Focusing Completed	Foc1 AutoFocus Completed (Profile No 13)
22:32:53	Target Completed	Target completed (17/46, GCVS RX And)
22:34:45	Target Started (18/46)	Target started (18/46, GCVS GK Per)
22:37:49	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
22:39:59	Focusing Completed	Foc1 AutoFocus Completed (Profile No 14)
22:43:25	Target Completed	Target completed (18/46, GCVS GK Per)
22:44:26	Target Started (19/46)	Target started (19/46, UGC 3174 w/SN2023mut)
22:48:02	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
22:50:07	Focusing Completed	Foc1 AutoFocus Completed (Profile No 15)
23:05:57	Target Completed	Target completed (19/46, UGC 3174 w/SN2023mut)
23:06:26	Target Started (20/46)	Target started (20/46, CGCG 420-018 w/AT2023nbs)
23:10:26	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
23:12:51	Focusing Completed	Foc1 AutoFocus Completed (Profile No 16)
23:28:52	Target Completed	Target completed (20/46, CGCG 420-018 w/AT2023nbs)
23:28:57	Target Started (21/46)	Target started (21/46, AT2023wox)
23:31:59	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
23:33:59	Focusing Completed	Foc1 AutoFocus Completed (Profile No 17)
23:49:50	Target Completed	Target completed (21/46, AT2023wox)
23:50:26	Target Started (22/46)	Target started (22/46, AT2023uzx (CV))
23:54:33	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
23:56:39	Focusing Completed	Foc1 AutoFocus Completed (Profile No 18)
00:02:41	Target Completed	Target completed (22/46, AT2023uzx (CV))
00:02:45	Target Started (23/46)	Target started (23/46, AT2023wbv (CV))
00:06:03	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
00:08:00	Focusing Completed	Foc1 AutoFocus Completed (Profile No 19)
00:13:50	Target Completed	Target completed (23/46, AT2023wbv (CV))
00:14:46	Target Started (24/46)	Target started (24/46, AT2023xzr)
00:17:52	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
00:20:20	Focusing Completed	Foc1 AutoFocus Completed (Profile No 20)
00:36:36	Target Completed	Target completed (24/46, AT2023xzr)
00:36:40	Target Started (25/46)	Target started (25/46, AT2023cts)
00:40:41	Focusing Skipped	Foc1 focusing skipped - star is too dim (TCF-S)
00:51:58	Target Completed	Target completed (25/46, AT2023cts)
00:54:06	Target Started (26/46)	Target started (26/46, C/2017 K2 (PANSTARRS))
00:57:38	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
00:59:59	Focusing Completed	Foc1 AutoFocus Completed (Profile No 21)
01:08:00	Target Completed	Target completed (26/46, C/2017 K2 (PANSTARRS))
01:08:35	Target Started (27/46)	Target started (27/46, UGC 3274 w/SN2023cvn)
01:11:57	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
01:14:21	Focusing Completed	Foc1 AutoFocus Completed (Profile No 22)
01:18:46	SoftSuspend Called	Soft Suspend is called due to Deteriorating Conditions (too few stars)
01:27:42	Critical Cloud Alert	Critical Cloud Alert (Obs.Manager will close the Dome)
01:27:44	HardSuspend Called	Hard Suspend is called due to Critical Conditions (cloud)
01:27:47	Target Aborted (27/46)	Target aborted (27/46, UGC 3274 w/SN2023cvn) due to cloud
01:27:49	Queue Paused	Queue paused for Session Suspension
01:27:51	Session Suspending	Session suspending
01:28:37	Dome Closed	Dome closed (closing time 50s)
01:28:40	Session Suspended	Session suspended
01:49:31	Target Cancelled	Target cancelled (28/46, AT2023tkp) due to cloud
02:13:04	Target Cancelled	Target cancelled (29/46, AT2023tjz) due to cloud
02:26:32	Target Cancelled	Target cancelled (30/46, GCVS RR Tau) due to cloud
02:38:20	Target Cancelled	Target cancelled (31/46, GCVS DX Cnc) due to cloud
02:57:49	Target Cancelled	Target cancelled (32/46, NGC 3690 w/SN2023wrk) due to cloud
03:06:49	Target Cancelled	Target cancelled (33/46, NGC 4490) due to cloud
03:17:49	Target Cancelled	Target cancelled (34/46, AT2023bcg (CV)) due to cloud
03:37:49	Target Cancelled	Target cancelled (35/46, AT2023yon) due to cloud
03:52:09	Target Cancelled	Target cancelled (36/46, AT2021afkt (CV)) due to cloud
04:04:43	Target Cancelled	Target cancelled (37/46, GCVS U Mon) due to cloud
04:15:36	Target Cancelled	Target cancelled (38/46, GCVS RZ LMi) due to cloud
04:36:26	Target Cancelled	Target cancelled (39/46, UGC 6265 w/SN2023wcw) due to cloud
04:50:26	Target Cancelled	Target cancelled (40/46, AT2023cxz (CV)) due to cloud
05:10:26	Target Cancelled	Target cancelled (41/46, UGC 9002 w/SN2023pls) due to cloud
05:21:27	Session Resuming	Session resuming
05:22:42	Dome Opened	Dome opened (opening time 75s)
05:22:44	Session Running	Session running
05:22:46	Queue Resumed	Observing Queue resumed
05:22:49	Target Started (42/46)	Target started (42/46, 29P/Schwassmann-Wachmann)
05:37:03	Target Completed	Target partially completed (42/46, 29P/Schwassmann-Wachmann)
05:37:07	Target Started (43/46)	Target started (43/46, 103P/Hartley)
05:51:02	Target Completed	Target completed (43/46, 103P/Hartley)
05:51:06	Target Started (44/46)	Target started (44/46, 61P/Shajn-Schaldach)
05:54:01	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
05:56:24	Focusing Completed	Foc1 AutoFocus Completed (Profile No 23)
06:04:39	Target Completed	Target completed (44/46, 61P/Shajn-Schaldach)
06:04:43	Target Started (45/46)	Target started (45/46, AT2023ipb)
06:07:53	Focusing Skipped	Foc1 focusing skipped - star is too dim (TCF-S)
06:24:12	Target Completed	Target completed (45/46, AT2023ipb)
06:25:42	Target Started (46/46)	Target started (46/46, KUG 1227+226 w/SN2023bsg)
06:28:31	Focusing Started-Foc1	Foc1 Focusing Started (TCF-S)
06:30:43	Focusing Completed	Foc1 AutoFocus Completed (Profile No 24)
06:46:34	Target Completed	Target completed (46/46, KUG 1227+226 w/SN2023bsg)
06:46:37	Queue Completed	Job Queue completed
06:46:38	Session Closing	Session closing
06:48:08	Dome Closed	Dome closed (closing time 85s)
06:48:49	Dome Parked	Dome parked (parking time 34s), Az: 90.0 deg
06:50:08	Telescope Parked	Telescope parked (parking time 72s)
06:50:23	Telescope State	Handbox reads 'Scope parked Turn scope off.'
06:50:45	Telescope Switched Off	Telescope Power has been switched off via UPB Switch.
06:52:11	Services Stopped	Night Services stopped
06:52:13	Session Finishing	Session Finishing started (Create Fits Summary, Transfer Files)
06:52:54	Session Finished	Session Finished

Session Alerts & Alarms

Time	Type		Name	Detail
17:44:17	Yellow	Alert	Disk Space	Free Space on C:\ Drive (45.17 GB) is less than 50 GB
06:52:08	Yellow	Alert	Dome Charging	Dome hasn't started re-charging after 3.3 min. Dome may not have parked correctly
06:52:49	Yellow	Alert	Disk Space	Free Space on C:\ Drive (42.68 GB) is less than 50 GB
06:52:54	Red	Alert	Dome Charging	Dome hasn't started re-charging after 4.1 min. Dome may not have parked correctly

[ Prev | Next ]

Critical Issues

None

Major Issues

None

Minor Issues

Dome Shutter Communications not working (pre-session). This happened after removing the fuse on Shutter Unit, Waiting 60s and then replacing, in an attempt to resolve the Delayed Shutter Status updates after opening/closing shutter. This would have been a major issue accept that it happened pre-session and was (eventually) resolved by making an Observatory Visit and reinstalling Shutter Software 1.25 (see Shutter Software 1.25 Reinstall).
Resolved Pre-Session 2023-12-02 (Pulsar Dome)
Annotated Video Files aren't always being uploaded to website. The link to '.annotated .mp4 video file' in the All Sky Video (Latest)' section of the 'AllSky Latest.htm web page' frequently brings up on old 'annotated' video instead of the video from the previous night. It is suspected that this happens because the size of the .mp4 file is marginally above a threshold size used in AstroAllSky's Video Uploader. The annoted video (AllSky.LatestVideo_annotated.mp4) for 2023-12-02 is 24126 KB (23.5 MB) in size and seemingly wasn't uploaded to the website. In contrast the Annotated video from 2023-12-01 which was uploaded is 16882 KB (16.4 MB) in size. The size of the file will largely depend on the night length (files are bigger in mid-winter) and the amount of sky variation due to cloud movement (files are smaller on completely clear or completely overcast nights, but larger when clouds are passing through), which can't be controlled. Video Quality can however be reduced to reduce file size. The maximum allowed upload size is defined on AstroAllSky's Settings page. It is currently set to 20 MB which explains the behaviour seen. Setting change from 20 MB to 30 MB. Video Quality can however be reduced to reduce file size, this may be acceptable CreateAllSkyVideo() routine modified in AstroAllSky 3.19.8 so that if Image Set = "_ANNOTATED" , VideoQuality is set to SU.VideoQuality (the standard video quality) + 2. With SU.VideoQuality currently set to 24 in Program Settings, this means that the Annotated Videos will use VideoQuality = 26.
Fixed 2023-12-03 (AstroAllSky Settings, AstroAllSky 3.19.8)
Shutter Battery Charging is slower than usual (post-session). Charging rate (9 mA declining to 5 mE) is a lot lower than usual and in 21 hours the battery level had only climbed from 85% to 90% and battery voltage had only risen to 14.8v (Fig 1). Is this a function of Induction Charger positioning or due to re-installation of Shutter Software 1.25 on 2023-12-02 or a sideproduct of Shutter's interaction with new Dome Software 1.51 on 2023-11-15. It doesn't seem to be associated with the Dome Software 1.51 installation as the battery recharge rates were normal on 2023-11-16 (Fig 2). Visiting the Observatory showed that the Dome was in an acceptable Park Position for charging, but the two halves of the Induction Charger were fairly widely separated. After adjusting the tilt of the Induction Charger relative to the Induction Receiver to reduce the spacing and rotating the dome by 0.2°, the charging rate jumped up to to 30 mA, and battery level rose from 90% to fully charged level (97%, 15.0v) in just 2.75 hours. A separate continuous improvement ticket has been raised to show charge rate in AstroMain's ObsViewer/ObsPic pictures.
Fixed 2023-12-02023-12-04 (Observatory, Pulsar Dome)
AstroWeather program is crashing (2023-12-04). After a few random crashes of the AstroWeather program running on the AllSky/Weather Computer, the program began to crash shortly after starting all Services (2023-12-05 00:10). The problem is repeatable. By a process of elimination it was found that the crash only happened if Weather Forecast Service was selected. If Service wasn't selected the program will run with no problem. Investigation found that the program crash was due to an unhandled fatal exception in the TOpenWeather.GetJsonDataSet () routine that is associated with a JSON data block with an unexpected (not normally seen) format (see Investigation - OpenWeather JSON Parsing Issue). Immediate issue resolved in AstroWeather 1.23.3 by placing a Try..Catch.. End Try block around the relevant code in GetJsonDataSet () and GetJsonDataSet2() routines to handle the exception and prevent the program from crashing. [ An outer Try..Catch..End Try needs to be placed around the Weather Forecast cycle to provide catch-all handling, and prevent other possible issues bring the AstroWeather program down. ]. AstroWather is critical to safe and effective automated observing, and an issue causing the program to crash would have been treated as a Major Issue except that it occured outside a live session and has been fixed before the start of the next observing opportunity. The fix exposes a secondary issue which is the production of weather forecast charts which are only partially complete, this is described under a separate minor issue ticket.
Fixed 2023-12-04 (AstroWeather 1.23.3 ) - continue to investigate / monitor.
AstroWeather is producing weather forecast charts that are only partially complete (2023-12-05). Following a fix to AstroWeather crashing due to an unhandled fatal exception in the TOpenWeather.GetJsonDataSet () routine that is associated with a JSON data block with an unexpected (not normally seen) format, the Weather Forecast charting process continued, but the weather chart is incomplete from the problematic hourly data point onwards. Investigation shows JSON response from the OpenWeather Server is valid, but the parsing code doesn't correctly breakup the JSON response into correct data blocks (see Investigation - OpenWeather JSON Parsing Issue).   The parser in AstroWeather does currently anticipate that the "weather" data section can be an array with at least two datasets rather than just a single data set. Investigating discovered the bug in ParseHourlyBlock. Bug fixed in AstroWeather 1.23.4 by using existing routine GetJsonBlock()' which is used like
   datablock = GetJsonBlock(S.Substring(iStart - 1), "{", iEnd)
Whilst issue was believed fixed in AstroWeather 1.23.4 (2023-12-05) the problem was still occasionally occuring on 2023-12-07 (eg 22:51).   API Documents for OpenWeather at https://openweathermap.org/api (Current Weather API, Hourly Forecast 4 days API) . Debugging DrawForecast() routine using a saved Response.JSON file from 2023-12-07 22:51 and adding a Try..Catch..End Try block shows that a System.ArgumentException (Value of '15105' is not valid for 'red'. 'red' should be greater than or equal to 0 and less than or equal to 255) is generated from Forecast.Hourly.Data(i) where there is a record with DateTimeStr = "1969-12-31 23:58" which is inserted in between hour data for 2023-12-08 10:00 and 2023-12-08 11:00. Where does this extra hour record come from ?. This datetime value in close to the reference time for Unix Time which is "1970-01-01 00:00:00" which suggests that a proper "dt:" block wasn;t being accessed .   Further debugging indicates that this anomalous hour record is generated when ParseHourlyRecord is called with a block string like ""1h":0.21".   which seems to confirm the hypothesis. The prior call to ParseHourlyRecord (13) from ParseHourlyBlock is ok, but leaves a residual datablock beginning with the string {"1h":0.21}} ... This explains how ""1h":0.21" is sent to ParseHourlyRecord during the next iteration (14) through the parsing loop in ParseHourlyBlock (). Fixed in AstroWeather 1.23.6 by changing S = S.Substring(iEnd + 1) to S = S.Substring(iStart + iEnd + 1) to resolve this issue. However it requires the addition of preceeding check 'iStart + iEnd + 1 >= Len(S) to ensure than we haven't reached the end of the HourlyBlock .
Fixed 2023-12-08 (AstroWeather 1.23.6)

Small Defects

Unnecessary 'Dome Connection' activity/reporting whilst Restarting Pulsar Dome (2023-12-02 14:08). During Dome Shutter checks and tests it became necessary to Restart Dome' in an attempt to resolve and issue involving loss of communication with the Shutter. The operation ran from 14:08 to 14:09. The operation didn't resolved the Shutter communication issue but it did expose a couple of small defects in program logic. During 'Stop Dome Service', a Dome Connection error was reported with the message "Dome Connection has been lost. Attempting reconnection", which was followed by a 'Dome (COM3)' report line with message "Started (14:08) (ASCOM.Pulsar Observatories Dome.Dome, 6.3.10.0). and later during the 'Restart Dome Controller' (power cycle) code section there is a 'Dome Connection' report message "Dome Connection has been recovered' and during 'Restart Dome Service' operation the Dome Service reports that it is already started. Dome Connection has been recovered. It inapproriate to have one thread of the AstroMain program (ObsManager's PerformDomeMonitoring() routine) actioning a Dome Reconnection whilst another thread is trying to 'Stop' & controllably 'Restart' the Dome Service (incl Power Reset). The flag 'bRestartingDome' can be used to bypass the dome reconnection action in PerformDomeMonitoring(). Fixed in AstroMain 3.65.1. Code also added to the top of PerformDomeMonitoring() routine to reset 'monitor shutter opening/closing' Flags and exit the routine if program is in the process of Restarting Pulsar Dome.
Fixed 2023-12-03 (AstroMain 3.65.1)
Target Circle for BL Lac is slightly mispositioned. This problem that also affected BL Lac target in the previous S1171 session. Propose to replay target (Target ID 17, Images 1171052-56) at some stage but probably after first making the fix for 12P/Pons-Brooks circle position seen in S1169 Session. New Star Matching algorithm `added to AstroMain 3.65.4 and successfully tested against BL Lac dataset from the session.
Fixed 2023-12-10 (Session, AstroMain 3.65.4)
Reporting of Shutter Battery Warnings/Alerts should be temporarily disabled whilst Services are starting.
To fix 2023-12-03 (AstroMain 3.65+)

Continuous Improvement

Add a 'Control-Q' button to Fits Summary Workbook to make it easier to use over IPad. Control-Q is used to define a Colour Group for a photometric or other Colour group and add a 'Y' flag to signal copying of files for Photometry. This is inconvenient when specifiying Colour Group on the Development Computer when accessing via VNC from IPad. It can be done but it is awkward to call up the Virtual Keypad each time. A button 'CNTL-Q' positioned at the top of the Colour Group column would be a great aid. Implemented 2023-12-03 by assign new button to the existing 'CCD_Session_Summary.xls!X4a_SetFolderBands' macro.
Done 2023-12-03 (Excel Fits Summary)
Add Smart Plug for Greenhouse Heater to Zigbee Network and AstroMain. Add new Smart Plug for controlling power to Greenhouse Heater. Add new GreenhouseHeater object to AstroMain's Zigbee Module with associated fields on a new More/Greenhouse tab. Add basic automated operation of power to Greenhouse Heater.
Done 2023-12-03 (Greenhouse, Zigbee Network, AstroMain 3.65)
Create a new virtual picture to show the current greenhouse status. Create new 'GreenhousePic' pictures and save them to disk every 30s. and upload latest picture to website for display on 'Current Greenhouse Conditions' page (greenhouse_latest.htm).
Done 2023-12-04 (AstroMain 3.65, AstroPlan 1.39.2, Website)
Extend AstroWeather's Graph Routines to show Greenhouse Vent, Greenhouse Heater. Add Vent and Greenhouse Heater to Graph ID 14 & 59. Greenhouse Heater added in AstroWeather 1.23.1 . GreenhouseVent still to add.
Done (AstroWeather 1.23.1 )
Extend AstroWeather's Graph Routines to create a new Greenhouse Electricity Usage. Create a new 5 day graph (Graph ID = 65) to show Greenhouse Heating State, Daily Heating in hours, Daily Electricity Usage in Kwh and £ equivalent,
Done 2023-12-04 (AstroWeather 1.23.2 , Website / Greenhouse Current page)
Add Shutter Charging Amperage to AstroMain's ObsViewer/ObsPics. Adding Charge Amperage (such as 30 mA) to ObsViewer/ObsPics will provide an immediate indication that the Dome / Induction Charger are in a good position and will recharge the Shutter Battery at a normally fast rate (3 hours recharge) rather than being suboptimally placed which may take 24 hours (or more) to recharge the shutter battery, which may necessiate an observatory visit to resolve.& Dome.LastChargeAmperage is already tracked and can be used.
Done 2023-12-04 (AstroMain 3.65)
Create a routine that will automatically search for the Pulsar Dome's optimal Park Position based on Amperage Rate. Routine would slowly move from Park-3° to Park+3° or so and build a profile of Charge Amperage and use it to select optimal position and if appropriate resync scope to Park Az (90°). Ideally the ObsManager would automatically run this routine at the end of session if the dome is not charging. However if the dome isn't at its correct park position because of more serious dome rotation / hold-up issue or sensor pick-up issue, the routine may not work and/or might introduce issues iif not overseen in person by the user. Prehaps the option should be only be one that is remotely activated by the user to otherwise avoid a visit to the Observatory having ascertained there were no obvious risks based on session information. In due course the ObsManager might be able to use the routine in an automated mode provided that certain condition checks were passed, such as successful image linking of Locate Frames from the final/last target and no hold-ups moving to the Near Park Position. Prototype added to AstroMain 3.65.4. New routine (SearchForBestParkPosition()) seaches from Az 85° to Az 95° in 0.5° steps to find position have the highest charging amperage. Due to the infrequency of Shuttery Battery polling (typically once every 135s or 2m 15s, fresh amperage data can be delayed by up to 135s after jogging dome to a new azimuth position. This makes the whole process very slow. An observatory test at 2023-12-11 17:24 took 47 minutes to complete. Need to see what the width of the charging zone is in azimuthal degrees, and see whether its possible to do a wide search followed by a narrow search ? or use a narrow range based on visual observation of the dome. The test showed that the charging zone is quite narrow (+/- 0.5°)
Az: 89.0°, -3mA Az: 89.5°, 4mA Az: 90.0°, 15mA Az: 90.5°, 1mA Az: 91.0°, -2mA
With a 1° step best charging position could have been seen at Az 90.0 (15mA), but depending on difference between Pulsar Dome's Az and actual physical Az, the best charging position could equally have been seen at Az 89.5 (4 mA). The first would probably lead to fast slewing, but the second would give slow charging if used as Park Position. If a wide search used a 2° step it is possible to that the charging zone would have been totally missed (eg Az 89.0° -3mA & Az 91.0 °-2mA). Once the charging zone has been found, it would be feasible to exit the loop to speed up the operation. It is proposed to experiement with a Zigbee Open/Close Sensor to independantly indicate the Dome's Park position. Searching for Park Position would be a lot quicker using this alternative approach (see Continuous Improvement ticket on Session 2023-12-05 notes page ( S1172 CI). This might be accurate enough to determine the best park position by itself or it might at least provide a wide search capability which would be followed by a narrow Charge based search. Zigbee Open/Close Sensor acting as a proxy Unparked/Parked Sensor installed in Observatory 2023-12-13, and integrated into AstroMain. New routine using this sensor finds Best Park Position in under 4 minutes (using StartAz +/-4°, Step 0.2°).
Done / For testing 2023-12-11 (AstroMain 3.65.4)
Delay use of AstroAllSky's MoonMask until the moon in physically visible to the AllSky Camera. Currently the moon mask comes on once Moon is above the horizon, but initially when the Moon rises it is hidden behind the houses in NE or SE directions. The local horizon mask should be used to determine when the Moon Mask is applied.
To do 2023-12-04+ (AstroAllSky 3.19.9+)

[ Prev | Next ]

Fig 1. Shutter Battery Graphs
Showing anomously slow battery recharging following Session S1171 and earlier Dome Conformance Tests.
After adjustment of Induction Charger separation and position the battery recharging was fast/normal.

Fig 2. Battery Level Chart showing normal battery recharge rates on 2023-11-14 & 2023-11-16.

Pulsar Dome - Recalibration

Following remedial fixes to dome drive system, involving removal of anti-slip tape from roof flange, adjustment of the drive wheel tension, and removing restrictions to dome movement by filing down flanges at the wall segment joins the Dome was recalibrated.
Procedure

- Placed Home Magnet in its hole in roof flange, orientated in correct position (inside facing side previously marked with some paint)
- Entered Pulsar Software
- ensured under settings that Home Position is 180.0° and Park Position is at 90.0°
- clicked 'Calibrate'
- waited for calibration to complete (dome left at Az 178.6° at end of process)
- clicked Park and checked that Dome moved to correct physical position
- Removed Home Magnet for safe keeping (otherwise they will totally corrode away)

(in the event Home Magnet was left in place until after a series of ASCOM Conform tests were conducted on the Dome)

Update 2023-12-03

Pulsar Dome - ASCOM Conformance Tests

The Pulsar Dome + ASCOM Driver (ASCOM.Pulsar_Observatories_Dome.Dome) where checked today (2023-12-02) using ASCOM Device Conformance Checker 6.6.8048.17861 running on ASCOM Platform 6.6 SP1.
The Option to 'Allow Dome Shutter to open while testing' was enabled
(Since the test was to be during daylight hours the CloudSensor's Light setting was disabled during the test otherwise the Relay would intervene to close the shutter which would interfer with the Conformance Checks).
Since the physical opening & closing time of the Shutter is around 42-45s the 'Dome Shutter Timeout' was set to 60s. This was done to expose and highlight the weakness in the current Dome Software Configuration. (Dome 1.51 + Shutter 1.25).

Comformance Check Result for Pulsar Observatories Dome (2023-12-03) is shown below.

Conform Report Hash (V1): 
E4EFE4A9BFB264DBE12C6B51B103CC9837DEA5D105DC8ACF504460C848A82BEFF6F583F6E20664FBF43A60F2C0112D784DD3FC8C5F57D20645CDBD0175C000B5



ConformanceCheck ASCOM Device Conformance Checker Version 
6.6.8048.17861, Build time: 2022-01-13 09:55:26
ConformanceCheck Running on: 
ASCOM Platform 6.6 SP1 6.6.1.3673

ConformanceCheck Driver ProgID: 
ASCOM.Pulsar_Observatories_Dome.Dome

Error handling 
Error number for 
"Not Implemented" is: 80040400
Error number for "Invalid Value 1" is: 
80040405
Error number for "Value Not Set 1" is: 80040402
Error number for 
"Value Not Set 2" is: 80040403
Error messages will be interpreted to infer 
state.

13:48:57.835 Driver Access Checks OK 
13:48:57.844 AccessChecks 
About to create instance using Activator.CreateInstance
13:48:58.615 
AccessChecks OK Successfully created driver using late binding
13:48:58.622 
AccessChecks About to set Connected property true
13:48:58.789 AccessChecks 
About to set Connected property false
13:48:58.910 AccessChecks OK 
Successfully connected using late binding
13:48:58.919 AccessChecks INFO The 
driver is a .NET object
13:48:58.924 AccessChecks INFO The 
AssemblyQualifiedName is: ASCOM.Pulsar_Observatories_Dome.Dome, 
ASCOM.Pulsar_Observatories_Dome.Dome, 
13:48:58.933 AccessChecks INFO The 
driver implements interface: ASCOM.DeviceInterface.IDomeV2
13:48:58.942 
DisposeAndReleaseObject About to release AccessChecks driver instance

13:48:58.959 DisposeAndReleaseObject About to set Connected property

13:48:59.706 AccessChecks INFO Device does not expose interface IDome

13:48:59.753 AccessChecks About to set Connected property
13:49:00.081 
AccessChecks INFO Device exposes interface IDomeV2
13:49:00.091 AccessChecks 
About to set Connected property
13:49:01.505 AccessChecks OK Successfully 
created driver using driver access toolkit
13:49:01.514 AccessChecks About to 
set Connected property
13:49:01.847 AccessChecks OK Successfully connected 
using driver access toolkit
13:49:01.853 AccessChecks About to set Connected 
property

Conform is using ASCOM.DriverAccess.Dome to get a Dome object

13:49:03.283 ConformanceCheck OK Driver instance created successfully

13:49:03.366 ConformanceCheck About to set Connected property
13:49:03.375 
Connected About to set Connected property
13:49:03.696 ConformanceCheck OK 
Connected OK

Common Driver Methods 
13:49:03.772 InterfaceVersion 
About to get property InterfaceVersion
13:49:03.782 InterfaceVersion OK 2

13:49:03.827 Connected About to get property Connected
13:49:03.834 Connected 
OK True
13:49:03.894 Description About to get property Description

13:49:03.903 Description OK Pulsar Observatories Dome
13:49:03.943 DriverInfo 
About to get property DriverInfo
13:49:03.955 DriverInfo OK Pulsar 
Observatories Dome Drive Version: 6.3
13:49:04.010 DriverVersion About to get 
property DriverVersion
13:49:04.020 DriverVersion OK 6.3
13:49:04.075 Name 
About to get property Name
13:49:04.083 Name OK Pulsar Observatories Dome

13:49:04.144 CommandString INFO Conform cannot test the CommandString method

13:49:04.153 CommandBlind INFO Conform cannot test the CommandBlind method

13:49:04.158 CommandBool INFO Conform cannot test the CommandBool method

13:49:04.169 Action INFO Conform cannot test the Action method
13:49:04.176 
SupportedActions About to call method SupportedActions
13:49:04.190 
SupportedActions OK Driver returned an empty action list

Can Properties

13:49:04.304 CanFindHome About to get CanFindHome property
13:49:04.319 
CanFindHome OK True
13:49:04.383 CanPark About to get CanPark property

13:49:04.394 CanPark OK True
13:49:04.450 CanSetAltitude About to get 
CanSetAltitude property
13:49:04.468 CanSetAltitude OK False
13:49:04.527 
CanSetAzimuth About to get CanSetAzimuth property
13:49:04.535 CanSetAzimuth 
OK True
13:49:04.579 CanSetPark About to get CanSetPark property

13:49:04.591 CanSetPark OK True
13:49:04.647 CanSetShutter About to get 
CanSetShutter property
13:49:04.658 CanSetShutter OK True
13:49:04.724 
CanSlave About to get CanSlave property
13:49:04.737 CanSlave OK False

13:49:04.794 CanSyncAzimuth About to get CanSyncAzimuth property
13:49:04.804 
CanSyncAzimuth OK True

Pre-run Checks 
13:49:04.971 PreRunCheck About 
to get Slewing property
13:49:05.313 DomeSafety Attempting to open shutter as 
some tests may fail if it is closed...
13:49:05.325 PreRunCheck About to call 
OpenShutter
13:49:05.505 DomeShutterWait About to get ShutterStatus property 
repeatedly
13:50:05.718 DomeShutterWait About to get ShutterStatus property

13:50:05.730 DomeShutterWait ERROR Timed out waiting for shutter to reach state: 
shutterOpen, consider increasing the timeout setting in Options / Conformance 
Options
13:50:05.804 PreRunCheck About to get ShutterStatus property

13:50:05.817 PreRunCheck About to get ShutterStatus property
13:50:05.837 
DomeSafety WARNING Shutter status: shutterOpening

Properties 

13:50:05.935 Altitude About to get Altitude property
13:50:05.976 Altitude OK 
Optional member threw a PropertyNotImplementedException exception.

13:50:06.035 AtHome About to get AtHome property
13:50:06.045 AtHome OK False

13:50:06.103 AtPark About to get AtPark property
13:50:06.114 AtPark OK True

13:50:06.167 Azimuth About to get Azimuth property
13:50:06.177 Azimuth OK 90

13:50:06.235 ShutterStatus About to get ShutterStatus property
13:50:06.249 
ShutterStatus OK shutterOpening
13:50:06.321 Slaved Read About to get Slaved 
property
13:50:06.333 Slaved Read OK False
13:50:06.385 Slaved Write About 
to set Slaved property
13:50:06.401 Slaved Write OK Optional member threw a 
PropertyNotImplementedException exception.
13:50:06.469 Slewing About to get 
Slewing property
13:50:06.482 Slewing OK True

Methods 
13:50:06.612 
AbortSlew About to call AbortSlew method
13:50:06.646 AbortSlew About to get 
Slaved property
13:50:06.670 AbortSlew OK AbortSlew command issued 
successfully
13:50:06.738 SlewToAltitude About to call SlewToAltitude method

13:50:06.751 SlewToAltitude OK Optional member threw a 
MethodNotImplementedException exception.
13:50:06.819 SlewToAzimuth About to 
call SlewToAzimuth
13:50:06.903 SlewToAzimuth About to get Slewing property

13:50:48.896 SlewToAzimuth 0 OK Asynchronous slew OK
13:50:59.631 
SlewToAzimuth About to call SlewToAzimuth
13:50:59.776 SlewToAzimuth About to 
get Slewing property
13:50:59.784 SlewToAzimuth 45 OK Synchronous slew OK

13:51:10.412 SlewToAzimuth About to call SlewToAzimuth
13:51:10.446 
SlewToAzimuth About to get Slewing property
13:51:46.856 SlewToAzimuth 90 OK 
Asynchronous slew OK
13:51:57.631 SlewToAzimuth About to call SlewToAzimuth

13:51:57.657 SlewToAzimuth About to get Slewing property
13:51:57.670 
SlewToAzimuth 135 OK Synchronous slew OK
13:52:08.358 SlewToAzimuth About to 
call SlewToAzimuth
13:52:08.372 SlewToAzimuth About to get Slewing property

13:52:39.682 SlewToAzimuth 180 OK Asynchronous slew OK
13:52:50.350 
SlewToAzimuth About to call SlewToAzimuth
13:52:50.371 SlewToAzimuth About to 
get Slewing property
13:52:50.379 SlewToAzimuth 225 OK Synchronous slew OK

13:53:01.170 SlewToAzimuth About to call SlewToAzimuth
13:53:01.184 
SlewToAzimuth About to get Slewing property
13:53:32.342 SlewToAzimuth 270 OK 
Asynchronous slew OK
13:53:43.030 SlewToAzimuth About to call SlewToAzimuth

13:53:43.053 SlewToAzimuth About to get Slewing property
13:53:43.063 
SlewToAzimuth 315 OK Synchronous slew OK
13:53:53.809 SlewToAzimuth About to 
call SlewToAzimuth
13:53:53.819 SlewToAzimuth OK COM invalid value exception 
correctly raised for slew to -10 degrees
13:53:53.876 SlewToAzimuth About to 
call SlewToAzimuth
13:53:53.887 SlewToAzimuth OK COM invalid value exception 
correctly raised for slew to 370 degrees
13:53:53.973 SyncToAzimuth About to 
get Azimuth property
13:53:54.012 SyncToAzimuth OK Dome synced OK to within 
+- 1 degree
13:53:54.028 SyncToAzimuth About to call SyncToAzimuth method

13:53:54.073 SyncToAzimuth About to call SyncToAzimuth method
13:53:54.099 
SyncToAzimuth OK COM invalid value exception correctly raised for sync to -10 
degrees
13:53:54.170 SyncToAzimuth About to call SyncToAzimuth method

13:53:54.184 SyncToAzimuth OK COM invalid value exception correctly raised for 
sync to 370 degrees
13:53:54.279 CloseShutter About to get ShutterStatus 
property
13:53:54.293 CloseShutter About to call CloseShutter method

13:53:54.410 DomeShutterWait About to get ShutterStatus property repeatedly

13:54:54.415 DomeShutterWait About to get ShutterStatus property
13:54:54.425 
DomeShutterWait ERROR Timed out waiting for shutter to reach state: 
shutterClosed, consider increasing the timeout setting in Options / Conformance 
Options
13:54:54.441 CloseShutter OK Shutter closed successfully

13:55:15.680 OpenShutter About to get ShutterStatus property
13:55:15.854 
DomeShutterWait About to get ShutterStatus property repeatedly
13:56:15.855 
DomeShutterWait About to get ShutterStatus property
13:56:15.864 
DomeShutterWait ERROR Timed out waiting for shutter to reach state: shutterOpen, 
consider increasing the timeout setting in Options / Conformance Options

13:56:15.879 OpenShutter About to get ShutterStatus property
13:56:15.896 
OpenShutter About to get ShutterStatus property
13:56:15.916 OpenShutter 
ERROR Unable to open shutter - ShutterStatus: shutterOpening
13:56:26.672 
FindHome About to call FindHome method
13:56:26.748 FindHome About to get 
Slaved Property
13:56:26.758 FindHome About to get Slewing property 
repeatedly
13:57:31.562 FindHome About to get AtHome property
13:57:31.572 
FindHome OK Dome homed successfully
13:57:42.367 Park About to call Park 
method
13:58:22.261 Park About to get Slaved property
13:58:22.277 Park 
About to get Slewing property repeatedly
13:58:23.222 Park About to get 
AtPark property
13:58:23.233 Park OK Dome parked successfully
13:58:34.071 
SetPark About to call SetPark method
13:58:34.103 SetPark OK SetPark issued 
OK

Post-run Checks 
13:58:34.268 DomeSafety INFO Attempting to close 
shutter...
13:58:34.288 DomeSafety About to call CloseShutter
13:58:34.343 
DomeShutterWait About to get ShutterStatus property repeatedly
13:59:24.963 
DomeShutterWait About to get ShutterStatus property
13:59:24.974 DomeSafety 
OK Shutter successfully closed
13:59:24.989 DomeSafety INFO Attempting to 
park dome...
13:59:25.007 DomeSafety About to call Park
13:59:25.933 
DomeSafety OK Dome successfully parked

Conformance test complete 

13:59:26.004 DisposeAndReleaseObject About to release Dome driver instance

13:59:26.021 DisposeAndReleaseObject About to set Connected property

Your 
driver had 4 errors, 1 warning and 0 issue 

Driver Hash Value: 
E211844A88467F271239409179532BFAF38DFCDDE1FB6615B5438A51EB0C988383962AAD8B37DC507855BAD22683F80C140E35A7F9219034EBAB33850E0BB4E0

Pulsar Dome - Shutter Software Reinstall (Shutter 1.25)

Following issues with Changes in Shutter Status being significantly delayed (see xxxxx ) it was decided to try to 'reset Shutter-Dome' communication link by removing the Fuse on the Shutter Unit for >60s and then replacing it. However the Dome Controller lost all contact with the Shutter and couldn't be recovered even after rebooting the Dome Controller. Pulsar Software indicated 'No Shutter' and The Dome Controller didn't have a menu option to Open/Close the Shutter.
Proceeded to reinstall Shutter Software 1.25 using the methodology recorded at Pulsar Dome Software Update (Shutter 1.25), 2021-03-31, in an attempt to repair things.

- Moved Dome to Az 270 deg (close to computer)
- Connected USB cable from Observatory Computer to Shutter Unit
- Ran “ES Updater.exe”
- Selected COM port of shutter unit (COM 15 in my case)
- Clicked “Select File” and seleced t “Shutter_1_25.hex”
- Clicked “Update”
- Once updated removed fuse, waited one minute (60s) then replaced

[ Pulsar Software was opened at this point with the thought that it would allow the Shutter Version to be checked (it isn't actually available here, the only place to see it is via the Dome Controller Screen). As the Pulsar software was opened it put up a dialog stating that software needed to be updated, and it then proceeded to make some updates. It is assumed that this included uploading new shutter software up to the shutter as the USB Cable was still connected. It was thought this was acceptable in short term provided the fuse was removed/replaced after 60s) ]

- Checked Shutter Information on Rotation Unit LCD Panel and confirmed that shutter version had changed to 1.25 ~C
- Removed USB cable between Observatoru Computer and Shutter Unit.
- [ Should have checked that Battery Information data were being received and confirmed that values were as expected, but may have missed this step ]
- Returned Dome to its Park position (Az 090 deg)
Attempted to Open the Dome's Shutter from AstroMain / DeviceHub but whilst Shutter Status changed to 'Opening' the Shutter didn't actually open. Attempting to open/close the Shutter from Dome Controller didn't work. Attempts to Open/Close the shutter from Pulsar Software also didn't work. Rebooting the Dome Controller didn't resolve things.
Attempted to re-upload Shutter Software 1.25 to the Shutter using a USB Cable, but the ES Updater gave error message "Update Failed, Code 1011, Message: ST Prog Mode Not Found"
Proceeded to remove the fuse on Shutter Unit, wait one minute (60s) and replaced. Connection between Shutter and Dome Controller established itself and a check of Shutter Information on Dome Controller's LCD Panel, showed that the shutter version had changed to 2.09.

Problems have previously been had with v2.04 shutter driver when it became loaded as part of a 'Pulsar_Observatories_Package 1.0.38.0.exe' install on 2021-03-04, Pulsar Dome Software Update (Shutter 1.23 attempt), 2021-03-04) , the shutter motor sounds quite different during first second or two of opening/closing, and Shutter battery level and voltage are returned as 0% and 4.1v, instead of expected 95% & 15.0v.   V2 software is intended for Version 2 Shutter Hardware, whereas my Dome's Version 1 Shutter Hardware requires V1 Software.

Examining the reported battery levels under 2.09 showed the same issue with battery level 0% and voltage 4.1v.

Tests were nevertheless performed to open and close the shutter.   These tests were successful and the opening/closing times based on ShutterStatus were both normal. (ie <=50s).   e.g. Closing time 49s (based on checks every 5s) vs physical closing time of 44s.

Close Dome                              2023-12-02 17:24  (Local, GMT)
> Observatory Shutter         Info      Shutter is closing            (17:24:33, open time 1.3 min)
  Close Dome...               Ok        Dome is closing   (Clarity: 39.8, Stars: 50, Rain: -0.9, Wind: 1.3)
> Observatory Shutter         Info      Shutter has closed            (17:25:17, closing time 44s)
  Close Dome...               Ok        Dome is closed    (Closing time 49s)

Again the sound of shutter motor was noted to be different for the first second or two , as per 2.04.
As it was already dark by this point consideration was given to running the night's planned Live Session using Shutter 2.09 software version (and return to the matter in the morning) but the AstroMain's ObsManager wouldn't allow an automated session to commence with the Low Battery (0%) levels reported by the Dome.

Therefore it order to salvage the night's observing session the steps to uploaded Shutter Software Version 1.25 to the Shutter using a USB cable were again followed . This update was successfully and after removing the fuse, waiting 60s and replacing the fuse, communcation's between Shutter and Dome Controller reestablished themselves. Tests showed that the Shutter was able to be opened/closed from ASCOM Client, but again there were delays in ShutterStatus changing to 'Open' when opening or changing to 'Closed' when closing. (taking 89s and 96s respectively compared to physical opening/closing times of 42 & 44s.)

Open Dome                               2023-12-02 17:36  (Local, GMT)
> Observatory Shutter         Info      Shutter is opening            (17:36:04, close time 10.8 min)
  Open Dome...                Ok        Dome is opening   (Clarity: 39.7, Stars: 49, Rain: -0.9, Wind: 0.0)
> Observatory Shutter         Info      Shutter is open               (17:36:46, opening time 42s)
  Open Dome                   Warning   Dome opening hasn't finished after 60s
  Open Dome...                Ok        Dome is open      (Opening time 89s)

Close Dome                               2023-12-02 17:38  (Local, GMT)
> Observatory Shutter         Info      Shutter is closing            (17:38:12, open time 1.4 min)
  Close Dome...               Ok        Dome is closing   (Clarity: 39.7, Stars: 52, Rain: -0.9, Wind: 0.0)
> Observatory Shutter         Info      Shutter has closed            (17:38:57, closing time 44s)
  Close Dome...               Ok        Dome is closed    (Closing time 96s)

Update 2023-12-03

Dome Shutter operated without major issue during the S1171 session including two unscheduled Suspend/Resume operations, however there were issues with delays in the ShutterStatus arriving at an 'Open' or 'Closed' state in 66% of operations. This is a new problem that has begun after installing Dome Software Version 1.51 (with Shutter is still on Shutter Software Version 1.25).

- Of the 3 opening operations, all 3 had delays in seeing Dome.ShutterStatus arrive at the 'Open' state.

- Of the 3 closing operations 1 had a delay in seeing Dome.ShutterStatus arrive at the 'Closed' state.
(the other 2 closing operations had times that are within the 5s tolerance that is dictated by the client's cycle time)

Time	Observatory State	Shutter Operation	Physical Time from Zigbee Sensors	Time based on Dome.Shutter Status
17:47	Starting	Opening	42s	90s
19:09	Suspending	Closing	45s	50s
19:22	Resuming	Opening	42s	95s
01:27	Suspending	Closing	45s	50s
05:21	Resuming	Opening	42s	75s
06:26	Ending	Closing	45s	85s

2023-12-03

Zigbee - Smart Plug for Greenhouse Heater

Greenhouse heater has a thermostat on it for controlling its operation, however it seems ultrasensitive to the precise position at which switch is set. With one positioning turning it on and another position that notionally turns it off. The can result in heater remaining on when it needn't (costing money) or not coming on when it should (meaning plants get too cold for a while).
The Greenhouse already has a couple of Zigbee Multi-Sensors in it for recording temperature and it was always held as an option that there values could be used to auto-control the Greenhouse Heater if its own heating regulation wasn't fit enough for purpose. After 3 weeks of use it ha been decided to add a Smart Plug for the Heater tied into the Observatory's Zigbee Network, allowing automated control of the heater. The algorithum for autmatically operating the heater can be fine tuned in due course. A side benefit of the automated control is that the heater's on time can be recorded and it's KwH usage and therefore cost to be calculated and presented.
A new Philips Hue Smart Plug (of the same kind as used for other smart plugs in the observatory) was installed onto the Observatory Zigbee Network today (2023-12-03). This went onto the Zigbee network as Light ID 4.
Additions are being made to AstroMain's Zigbee Module to make a recognised switch, and to allow initial manual operation and eventually automated operation.

2023-12-04

Investigation - OpenWeather JSON Parsing Issue

Issue
1) AstroWeather program crashing in read/create Weather Forecast section
2) AstroWeather creating only half-completed 24 hour Weather Forecast Charts

Description

After a few random crashes of the AstroWeather program running on the AllSky/Weather Computer on 2023-12-04, including one at 23:28, the program began to crash almost immediately after using 'Start Service' facility. This was after installing a new AstroWeather version). The problem was repeatable, each time the program/serverces was started over the course of 10 minutes or so it crashed. By a process of elimination it was found that the crash only happened if the 'Weather Forecast' service was selected. If the service wasn't selected the program ran without problem. A new AstroWeather version is being used but changes made are restricted to ObsEnv and Graphs, which have no bearing on the Weather Forecast module. It is presumed that there is unexpected data anomaly in the Rest API dataset or less likely that the specification of the API has changed. The WeatherForecast Chart that signals the completion of a WeatherForecast Cycle was last made at 2023-12-04 23:28 (the chart and contained data is completely normal and shows no anomalies). Until a reason for the crashes is found and fixed the AstroWeather program will be run with the Weather Forecast Service, allowing the issue to be demoted from Major rank to Minor rank. The Weather Forecast Service is needed for Live Sessions, so a solution needs to be found beforehand. Assuming the issue is an unexpected data value or format, it would seem the immediate software change should be to place appropriate exception block around.

Analysis

Running Test OpenWeather Forecast on Development Computer quickly revealed a fatal exception ("System.ArgumentOutOfRangeException: 'Length cannot be less than zero" in TOpenWeather.GetJsonDataSet () routine

Function GetJsonDataSet(ByVal block As String, ByVal Keyword As String) As String '================ Dim c As Integer Dim S As String = "" Dim iStart As Integer Dim iEnd As Integer Dim TwinQuotes As String = """" Dim field As String = "" ' Find Position of keyword within input string c = InStr(block, TwinQuotes + Keyword + TwinQuotes) If c = 0 Then Return "" Exit Function Else S = block.Substring(c - 1) iStart = InStr(S, "[{") iEnd = InStr(S, "}]") - 3 field = S.Substring(iStart + 1, iEnd - iStart + 1) End If Return field End Function

In the line

field = S.Substring(iStart + 1, iEnd - iStart + 1) where Parameters to routine Block = "dt":1701766800,"temp":2.93,"feels_like":0.04,"pressure":1017,"humidity":83,"dew_point":0.31,"uvi":0, "clouds":96,"visibility":10000,"wind_speed":2.97,"wind_deg":311,"wind_gust":2.43, "weather":[{"id":500,"main":"Rain","description":"light rain","icon":"10d" Keyword = "weather" and variables at time of exception are c = 183 S = "weather":[{"id":500,"main":"Rain","description":"light rain","icon":"10d" iStart = 11 iEnd = -3 field = S.Substring(12,-13)

and It would seem the exception arises because the JSON block doesn't have the expected closing characters, ie }] are missing.
Placing a Try Catch End Tr block around the code and returning "" in the event of an exception stops the program crashing, a Forecast Graph is completed for first 10 hours of the 24 hour forecast. If this is a glitch with the JSON response from the OpenWeather Server it would seem tha tit is going to be impossible to complete the Forecast Chart, and and a half completed graph is the best that can be achieved in the circumstances.
Running the JSON Response from OpenWeather through 'JSON Validator' (free, from Microsoft App Store) produces a 'Your (JSON) code is valid". This suggests that there is an issue with the self built JSON parser in AstroWeather.

Adding tracing it is can be seen that JSON Code associated with normal hourly data that doesn't produce an exception looks like this:

{"dt":1701763200,"temp":3.54,"feels_like":1.35,"pressure":1016,"humidity":78,"dew_point":0.02, "uvi":0,"clouds":97,"visibility":10000,"wind_speed":2.31,"wind_deg":325,"wind_gust":2.06, "weather":[{"id":500,"main":"Rain","description":"light rain","icon":"10n"}], "pop":0.55,"rain":{"1h":0.23}},

GetJsonDataSet() is called with Block: "dt":1701763200,"temp":3.54,"feels_like":1.35,"pressure":1016,"humidity":78,"dew_point":0.02,"uvi":0, "clouds":97,"visibility":10000,"wind_speed":2.31,"wind_deg":325,"wind_gust":2.06, "weather":[{"id":500,"main":"Rain","description":"light rain","icon":"10n"}],"pop":0.55,"rain":{"1h":0.23} S : "weather":[{"id":500,"main":"Rain","description":"light rain","icon":"10n"}],"pop":0.55,"rain":{"1h":0.23} Return: "id":500,"main":"Rain","description":"light rain","icon":"10n"

However the JSON code associated with hourly data that produces the exception looks like this :

{"dt":1701766800,"temp":2.93,"feels_like":0.04,"pressure":1017,"humidity":83,"dew_point":0.31, "uvi":0,"clouds":96,"visibility":10000,"wind_speed":2.97,"wind_deg":311,"wind_gust":2.43, "weather":[{"id":500,"main":"Rain","description":"light rain","icon":"10d"}, {"id":511,"main":"Rain","description":"freezing rain","icon":"13d"}], "pop":0.55,"rain":{"1h":0.18}}, GetJsonDataSet() is called with Block: "dt":1701766800,"temp":2.93,"feels_like":0.04,"pressure":1017,"humidity":83,"dew_point":0.31,"uvi":0, "clouds":96,"visibility":10000,"wind_speed":2.97,"wind_deg":311,"wind_gust":2.43, "weather":[{"id":500,"main":"Rain","description":"light rain","icon":"10d" S: "dt":1701766800,"temp":2.93,"feels_like":0.04,"pressure":1017,"humidity":83,"dew_point":0.31,"uvi":0, "clouds":96,"visibility":10000,"wind_speed":2.97,"wind_deg":311,"wind_gust":2.43, "weather":[{"id":500,"main":"Rain","description":"light rain","icon":"10d"

Conclusion
It seems that Weather can be an array and when it there is more than one item (more than one id/icon) is when the JSON parser has a problem.The parser needs to be modified to recognise this situation and probably return the first item. Problem seems to be in the code that creates the Block.

The ParseHourlyBlock(ByVal block As String) routine uses

iStart = InStr(S, "{")
iEnd = InStr(S, "},") - 1

finds the string bounded by the first "{" and first "}," token however the

whilst there is a }, at end of block as in },{"dt":, there can be an earlier }, as in },{"id"
hence searching on }, isn't sufficient.

Instead the search needs to find } with equivalent rank as the initial {. After trialling some code which successfully worked, it was discovered that there was already a routine in the 'Forecast.vb' module called 'GetJsonBlock()' which is used like

datablock = GetJsonBlock(S.Substring(iStart - 1), "{", iEnd)

This Web Page:	Notes - Session 1171 (2023-12-02)
Last Updated :	2024-09-26
Site Owner :	David Richards
Home Page :	David's Astronomy Web Site

David's Astronomy Pages Notes - Session 1171 (2023-12-02)