David's Astronomy Pages
Notes - Session 1074 (2022-12-20)

 
Bullet Session Aims & Highlights
 - Observing Result
 - Night Summary Plot
 - Session Event Log
Bullet Operational Issues
  - Critical Issues (1),  Major Issues (1),  Minor Issues (3),  Small Defects (6),  Continuous Improvement (4)
 
Bullet Images from 2022-12-20 >>       
2022-12-22
Bullet Investigation - Loss of Ethernet Connection (2022-12-20 & 2022-12-21)
   
   

Session Aims & Highlights (2022-12-20)

Main aims

  1. Targets.  Acquire images of a selection of variable stars, nearby stars, comets & deep sky targets as allowed by sky conditions.
  2. 29P/Schwassmann-Wachmann. Acquire further images of 29P/Schwassmann-Wachmann, as followup to images taken in previous sessions (S1061 - S1072) . Continue to look out for expanding coma following 4 mag outburst on Nov 22nd 2022.
  3. AstroMain.  Check new AstroMain version (3.59.8) for any issues introduced by recent changes, bug fixes and additions

 Equipment & Software

Highlights

Notes:

Summary Plots & Logs

Observing Plan
Image
  
Observing Result
Image
   
Image
 
Dome & Scope Slewing Performance
Image
  
Slew/Centering Performance
Image
  
Guiding Performance
Image
 
  
Sky Conditions (Locate Frames)
Image
  
Night Sky Summary Plot
Top axis: Sky Brightness at Zenith (in ADU/s)
Lefthand axis: Local Time (hh LT). Righthand axis: Sun Altitude (degs)
Image   
  
Actual Weather vs Pre-Session Weather Forecast
Image
Image   
  
Session Event Log
Time     Event Detail
18:28:41 Session Monitoring AutoStart monitoring for Live Session opportunity between 18:28 & 06:29
18:28:42 Session AutoStarting Session autostarting (18:28)
18:29:02   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.)
18:29:15 Session Created Session Created (Live, 2022-12-20 S01074, ImageSaveNum: 1074001)
18:29:42   Scope Switched On Telescope Power has been switched on via UPB Powerbox.
18:31:25   Services Started Observatory Services started
18:31:32 Observatory (Auto) Observatory placed in Fully-Automated Mode
18:31:37 Session Pending Session pending (2022-12-20)
18:31:39 Session Initiating Session initiating (2022-12-20)
18:31:41   Plan Requested Observing Plan requested from AstroPlan (1.35.3)
18:32:36   Plan Loaded Observing Plan loaded to queue (Plan ID: 845)
18:32:57   Camera1 Connected SBIG Camera connected (set point -20°C)
18:33:34   Telescope Connected Telescope connected (TheSky6)
18:33:58 Session Equilibration Session ready to Open Dome
18:34:43   Dome Opened Dome opened (opening time 45s)
18:34:44   Equilibration Started Dome Equilibration started
18:38:43   Equilibration Ended Dome Equilibration ended (4.0 mins total)
18:38:45 Session Running Session running
18:38:48   Queue Started Observing Queue started (38 targets selected)
18:38:49     Target Started (NrZen) Target started (Focus Field 2, HIP 9508)
18:39:05       Dome Unparked Dome unparked
18:42:24       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
18:45:00       Focusing Completed Foc1 AutoFocus Completed (Profile No 1, wide)
18:47:04       Focusing Completed Foc1 AutoFocus Completed (Profile No 1)
18:47:06       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap)
18:49:05       Focusing Completed Foc2 AutoFocus Completed (Profile No 2, wide)
18:50:48       Focusing Completed Foc2 AutoFocus Completed (Profile No 2)
18:51:05     Target Completed (NrZen) Target completed (Focus Field 2, HIP 9508)
18:52:09     Target Started (1/38) Target started (1/38, C/2021 Y1 (ATLAS))
18:57:29       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S)
19:06:38     Target Completed Target completed (1/38, C/2021 Y1 (ATLAS))
19:06:42     Target Started (2/38) Target started (2/38, GCVS GK Per)
19:10:38       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
19:12:48       Focusing Completed Foc1 AutoFocus Completed (Profile No 3)
19:16:13     Target Completed Target completed (2/38, GCVS GK Per)
19:16:18     Target Started (3/38) Target started (3/38, P/2010 H2 (Vales))
19:20:26       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
19:22:53       Focusing Completed Foc1 AutoFocus Completed (Profile No 4)
19:33:55     Target Completed Target completed (3/38, P/2010 H2 (Vales))
19:33:59     Target Started (4/38) Target started (4/38, UGC 2926 w/SN2022acyd)
19:37:55       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
19:40:22       Focusing Completed Foc1 AutoFocus Completed (Profile No 5)
19:56:10     Target Completed Target completed (4/38, UGC 2926 w/SN2022acyd)
19:56:14     Target Started (5/38) Target started (5/38, 29P/Schwassmann-Wachmann)
20:00:14       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
20:02:27       Focusing Completed Foc1 AutoFocus Completed (Profile No 6)
20:15:38     Target Completed Target completed (5/38, 29P/Schwassmann-Wachmann)
20:15:42     Target Started (6/38) Target started (6/38, UGC 3554 w/SN2022rbo)
20:15:44       Dome Unparked Dome unparked
20:18:37       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
20:21:03       Focusing Completed Foc1 AutoFocus Completed (Profile No 7)
20:37:47     Target Completed Target completed (6/38, UGC 3554 w/SN2022rbo)
20:37:51     Target Started (7/38) Target started (7/38, 107P/Wilson-Harrington)
20:40:57       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
20:43:12       Focusing Completed Foc1 AutoFocus Completed (Profile No 8)
20:53:06       Dome Unparked Dome unparked
20:56:45     Target Completed Target completed (7/38, 107P/Wilson-Harrington)
20:56:50     Target Started (8/38) Target started (8/38, AT2022usq)
20:59:31       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
21:01:43       Focusing Completed Foc1 AutoFocus Completed (Profile No 9)
21:18:03     Target Completed Target completed (8/38, AT2022usq)
21:18:07     Target Started (9/38) Target started (9/38, UGC 8046 w/SN2022zxr)
21:18:18       Dome Unparked Dome unparked
21:23:07       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-S)
21:39:26     Target Completed Target completed (9/38, UGC 8046 w/SN2022zxr)
21:39:30     Target Started (10/38) Target started (10/38, NGC 5631 w/SN2022acsj)
21:43:05       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S)
21:59:02     Target Completed Target completed (10/38, NGC 5631 w/SN2022acsj)
22:00:50     Target Started (11/38) Target started (11/38, GCVS BL Lac)
22:04:42       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
22:06:24       Focusing Failed Foc1 focusing failed (failed QC check - Ambiguous)
22:10:15     Target Completed Target completed (11/38, GCVS BL Lac)
22:10:56     Target Started (12/38) Target started (12/38, GCVS Z And)
22:13:37       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
22:15:48       Focusing Completed Foc1 AutoFocus Completed (Profile No 11)
22:20:09     Target Completed Target completed (12/38, GCVS Z And)
22:20:49     Target Started (13/38) Target started (13/38, AT2022xao)
22:24:37       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
22:27:16       Focusing Completed Foc1 AutoFocus Completed (Profile No 12)
22:43:36     Target Completed Target completed (13/38, AT2022xao)
22:43:40     Target Started (14/38) Target started (14/38, UGC 3937 w/SN2022acfz)
22:46:33       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
22:48:59       Focusing Completed Foc1 AutoFocus Completed (Profile No 13)
23:06:52     Target Completed Target completed (14/38, UGC 3937 w/SN2022acfz)
23:06:56     Target Started (15/38) Target started (15/38, AT2022xio (CV))
23:10:30       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
23:12:43       Focusing Completed Foc1 AutoFocus Completed (Profile No 14)
23:28:30     Target Completed Target completed (15/38, AT2022xio (CV))
23:28:34     Target Started (16/38) Target started (16/38, AT2022vry)
23:32:04       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S)
23:48:35     Target Completed Target completed (16/38, AT2022vry)
23:48:49     Target Started (17/38) Target started (17/38, NGC 2777 w/SN2022aagp)
23:52:29       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S)
00:08:43     Target Completed Target completed (17/38, NGC 2777 w/SN2022aagp)
00:10:49     Target Started (18/38) Target started (18/38, GCVS U And)
00:14:30       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
00:16:27       Focusing Completed Foc1 AutoFocus Completed (Profile No 15)
00:27:10     Target Completed Target completed (18/38, GCVS U And)
00:27:14     Target Started (19/38) Target started (19/38, GCVS SS Cyg)
00:30:07       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
00:32:16       Focusing Completed Foc1 AutoFocus Completed (Profile No 16)
00:36:33     Target Completed Target completed (19/38, GCVS SS Cyg)
00:42:42     Target Started (20/38) Target started (20/38, AT2022yeu (CV))
00:46:57       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
00:49:11       Focusing Completed Foc1 AutoFocus Completed (Profile No 17)
01:05:15     Target Completed Target completed (20/38, AT2022yeu (CV))
01:05:19     Target Started (21/38) Target started (21/38, M31 w/Nova M31 2022-12a?)
01:08:12       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
01:10:07       Focusing Completed Foc1 AutoFocus Completed (Profile No 18)
01:26:12     Target Completed Target completed (21/38, M31 w/Nova M31 2022-12a?)
01:26:42     Target Started (22/38) Target started (22/38, M33 w/Nova M33 2022-11a?)
01:30:03       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S)
01:46:00     Target Completed Target completed (22/38, M33 w/Nova M33 2022-11a?)
01:48:42     Target Started (23/38) Target started (23/38, NGC 5548 w/AT2022abcs)
01:53:19       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S)
02:09:13     Target Completed Target completed (23/38, NGC 5548 w/AT2022abcs)
02:10:42     Target Started (24/38) Target started (24/38, GCVS CN Leo)
02:14:43       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
02:17:09       Focusing Completed Foc1 AutoFocus Completed (Profile No 19)
02:24:25     Target Completed Target completed (24/38, GCVS CN Leo)
02:24:30     Target Started (25/38) Target started (25/38, NGC 3705 w/SN2022xxf)
02:28:11       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
02:30:38       Focusing Completed Foc1 AutoFocus Completed (Profile No 20)
02:46:26     Target Completed Target completed (25/38, NGC 3705 w/SN2022xxf)
02:46:30     Target Started (26/38) Target started (26/38, NGC 4340 w/SN2022zzz)
02:49:57       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-S)
03:06:38     Target Completed Target completed (26/38, NGC 4340 w/SN2022zzz)
03:07:32     Target Started (27/38) Target started (27/38, NGC 3938 w/SN2022xlp)
03:10:19       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S)
03:26:28     Target Completed Target completed (27/38, NGC 3938 w/SN2022xlp)
03:29:32     Target Started (28/38) Target started (28/38, M64)
03:32:30       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S)
03:48:30     Target Completed Target completed (28/38, M64)
03:51:32     Target Started (29/38) Target started (29/38, ARP 79)
03:54:47       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S)
04:10:44     Target Completed Target completed (29/38, ARP 79)
04:13:32     Target Started (30/38) Target started (30/38, NGC 5230)
04:16:54       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-S)
04:33:08     Target Completed Target completed (30/38, NGC 5230)
04:35:32     Target Started (31/38) Target started (31/38, C/2019 U5 (PANSTARRS))
04:39:22       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S)
04:51:23     Target Completed Target completed (31/38, C/2019 U5 (PANSTARRS))
04:51:40     Target Started (32/38) Target started (32/38, UGC 8317 w/AT2022qvu)
04:54:26       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S)
05:10:50     Target Completed Target completed (32/38, UGC 8317 w/AT2022qvu)
05:13:40     Target Started (33/38) Target started (33/38, M63)
05:15:59       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
05:18:16       Focusing Completed Foc1 AutoFocus Completed (Profile No 21)
05:21:34       SoftSuspend Called Soft Suspend is called due to Deteriorating Conditions (too few stars)
05:34:23     Target Completed Target completed (33/38, M63)
05:34:25   Queue Paused Queue paused for Session Suspension
05:34:27 Session Suspended Session suspended
05:35:15   Dome Closed Dome closed (closing time 50s)
05:46:36     Target Cancelled Target cancelled (34/38, AT2022evu (CV)) due to cloud
06:06:36     Target Cancelled Target cancelled (35/38, NGC 5631 w/SN2022aaiq) due to cloud
06:28:37     Target Cancelled Target cancelled (36/38, NGC 5894 w/SN2022pgf) due to cloud
06:47:41     Target Cancelled Target cancelled (37/38, C/2022 E3 (ZTF)) due to cloud
07:18:10     Target Cancelled Target cancelled (38/38, NGC 5853 w/SN2022mkj) due to too few stars
07:18:15   Queue Completed Job Queue completed
07:18:18 Session Closing Session closing
07:18:23   Dome Closed Dome already closed (closed at 05:35, closing time 50s)
07:18:53   Dome Parked Dome parked (parking time 21s), Az: 90.0 deg
07:19:35   Telescope Parked Telescope parked (parking time 41s)
07:19:50   Telescope State Handbox reads 'Scope parked Turn scope off.'
07:20:12   Telescope Switched Off Telescope Power has been switched off via UPB Switch.
07:21:36   Services Stopped Night Services stopped
07:21:39 Session Housekeeping Session Housekeeping started (Create Fits Summary, Transfer Files)
07:22:09 Session Finished Session Finished
 
Session Alerts & Alarms
Time     Type       Name Detail
01:05:53 Yellow Alert Dome Dome position has been static for more than 5 mins
 

Back to Top


Operational Issues (2022-12-20, S1074)

[ Prev | Next ]

Critical Issues

Major Issues

Minor Issues

Small Defects

Continuous Improvement

[ Prev | Next ]

Back to Top


2022-12-22


Investigation - Loss of Ethernet Connection (2022-12-20 & 2022-12-21)

Issue.    Loss of Ethernet Connection to/from Observatory before, during and after session S1074 (2022-12-20 & 2022-12-21)

1) Unable to make VNC Connection from or open Windows Explorer Views from Development Computer to either Observatory Computer or the AllSky/Weather Computer (pre-session, 2022-12-20 16:00)

2) Observatory and AllSky/Weather Computers stopped updating website less than 2 hours into Session (20:15).

3) Observatory remains non-operational due to the Observatory's Ethernet Connection being down or unreliable (2022-12-21)

Background
Connection to the household LAN and to the Internet is normally provided by 'Ethernet over Powerline', and is generally very reliable in comparison with WIFI connectivity to the Observatory which is normally unreliable and very slow/problematic.   LAN in critical to Observatory Operations to allow i) TCP/ IP Communication between Observatory Computer and AllSky/Weather Computer ii) VNC Connections for Remote Monitoring of Observatory Operations,  iii) File transfer to/from Observatory (software updates, targets database handover, session results),  whilst Intenet access is critical for  iv) Uploading of files and data to Observatory's WebSite for Remote Monitoring, and v) Download of weather forecast data including minutely rain radar based precipitation forecast.

Description

1) Before the S1074 session at around 16:00 the VNC connection from the Development (House) Computer to the Observatory Computer went down and couldn't be readily restored.  Also unable to connect to AllSky/Weather Computer or successfully ping either computer. Tried power-resetting Ethernet over Power Plugs at both router end and observatory end, but unable to restore connection.  Observatory Computer able to see files on the AllSky/Weather Computer.

- Some question over whether the Development Computer was able to see the Internet ok. 
- Unclear if files from Observatory are being uploaded to website or not (they are borderline overdue)
   (last VWS picture 15:35, Last Obs Status 15:43, last 60 min rain,  15:44 (later 17:10 but through weak WIFI link). 
- Rebooting Development Computer, rebooting Observatory Computer and rebooting Router didn't resolve the issue.
- Power resetting Ethernet over power plugs (both ends) and power-resetting Observatory Ethernet Switch didn't resolve the issue. 
- By passing the Ethernet Switch didn't resolve issue. 
- Ethernet over Power confirmed to be working in the house.  
- Ethernet over power plug taken from Observatory confirmed to work when located inside the house. 
- Employing a different (working) Ethernet over Power plug in the observatory didn't resolve the issue. 
- WIFI connection to Router working ok (one user querying about the quality of WIFI connection ?).  
- The Observatory and AllSky Computers remained in communication to each other up until 04:30 which is presumed to be the point where the Ethernet Hub in the Observatory was reset in a vain attempt to restore connectivity with the house. 
- Ethernet connectivity restored by itself at around around 18:10 or so. Thinking that the problems were fully resolved a live Observatory Session was kicked off at 18:28 using AuoStart.

2) Observatory and AllSky/Weather Computers stopped updating website less than 2 hours into Session (20:15).  At the same time there was a return of the pre-session problem whereby both the Development Computer and IPad couldn't make a VNC connection to either of the computers in the observatory.   As weather was fine and forecast to be remain so until the follwoing day, the Observatory was allowed to operate under total automonous control. Observatory was checked in the morning and everything was closed and parked up as expected. Checking the Computer showed that the session had run successfully and data had collected the whole night.

Whilst the session was succcessful it is a nevertheless a major issue that the status of the session and any alerts weren't available for the majority of the session.  Connectivity problem prevented the download of data from the session until two days later (2022-12-22) when a temporary powerline was put out to the observatory and the Observatory's Ethernet over PowerLine plug attached to it.

Analysis and Remediation

2022-12-21
Attempts were made on 2022-12-21 to use WIFI connection to return some operational capability back or at least to help diagnostics, but the WIFI connection was not reliable enough or fast enough to permit any more than occasional use. This was consistent with past experience and it why Ethernet over Powerline was adopted for the Observatory Connectivity,

Since it had been pretty much confirmed that Router and Ethernet over Powerline were working ok within the house,  that Ethernet Over Powerline pugs and Ethernet Cables were working ok, and the Computer involved were all working ok it was beginning to look like that there was an issue with the Main Powerline between house and Observatory or with the electrics in the Observatory. 

2022-12-22 am
A temporary power cable was laid out between the house and the observatory the following day (2022-12-22).  The plug end was connected to a plug socket in house/garage that is directly adjacent to the socket used for the main powerline to the Observatory), whilst the EtherNet over PowerLine plug was connected to the socket end located in the Observatory.  Turning on power, and checking the Observatory Computer it was confirmed that Ethernet over Powerline is working.    With the temporary powerline in place, data and results from the session was finally downloaded from the Observatory at 2022-12-22 11:00.

2022-12-22 pm

The following observations were evident following the basic investigations and observations :

- Router was working ok. All computers were working ok.
- Power to the observatory is operating ok through the main powerline. All devices operating normally.  ~
- 'Ethernet over Powerline' is working ok within the house
- The 'Ethernet over PowerIine' plugs themselves are functioning ok
- Ethernet cables seem to be all functioning ok
- 'Ethernet over Powerline' to Observatory works ok through temporarily laid powerline
- 'Ethernet over Powerline' has previously operated ok through the main powerline, and worked again for the nearly two hour period on 2022-12-20 (18:30 to 20:15)

It would seem that there is some sort of interference issue with the power circuit to the observatory or within the observatory itself ? 

Began a series of random tests and eventually got the Ethernet working over Observatory's Powerline again for a short time (60 minutes) before it went down again.   Triggeing the resumption may or may not have been a result of temporarily disabling the Zigbee Network, removing the Conbee II USB stick and turning off the Hue Smart Plugs in the AllSky/Weather Cabinet (Pulsar Dome, Dehumidifier, AllSky Heater and Aux Light).   Ethernet was up for over an hour but then went down again at around 14:25.  

Got Ethernet running again at 15:50  (again this was after disabling Zigbee Network but again it was unclear if this was critical or it was the effect of turning off/turning on the Ethernet over Powerline Plug (probably not) or leaving it off for 5 minutes and only then turning it back on again (but later on showed that turning Ethernet OverPowerline at router end for 10 mins didn't resolve issue)

The temporary Powerline whilst useful for diagostics is not viable workaround even for a short period as it mean leaving Observatory Door and Garage Door open.

So what could be preventing reliable use of the Observatory Main Powerline

 - Is it due to issue in the powerline to Observatory, a small short of something. ? (But has been working and still works at least part time, so not a terminal failure )
 - Could it be an intermittant issue with Ethernet Hub in Observatory.  However it was running ok with the temporary powerline and works ok for at least some of the time when using ethernet over Observatory's main powerline.  (Could test by connecting Observatory Computer directly to the Ethenet PowerLine plug ?)
 - Could it be related to ground currents ? (powerline to observatory runs underground and could be affected)
 - Could it be related to power glitches in the power-supply ? (Powerline to Observatory carries lower voltage due to its distance and might be more exposed to a weakness or instability in the supply
-  Could it be related to Power Socket issue on one particular socket in the kitchen whose switch has become stuck in last few days (could it be weakening the ethernet over powerline signal just enough to cause the issues). 
- Could it be related to Zigbee Network  (But Zigbee Network has been running with problems for the Ethernet Connectivity in the past 8 weeks). Could tTest by disabling network, regain Ethernet connectivity)
- Could it be a Kaspersky Firewall issue. (Ethernet again went down at 16:08.  Connection to both computers is lost at the same time ?, so why would Kaspersky kick in at the same time ?)
- Issue is unrelated to AllSky Heater/Dehumidifier, as the power to both Smart Plugs was turned off at time of the 16:09 disconnection).

Disabled Zigbee Network at 16:40 (pulling out the Conbee II USB stick) but it didn't immediately resolve problem,

With the Zigbee still disabled, turned off Power Sockets using Zigbee Smart Plugs (Pulsar Dome, Dehumidifier, AllSky Heater and Aux Light) and reset the Ethernet Over Powerline  Adapter, and eventually got Ethernet Connectivity back again (unclear what the precise critical factor was).    Left the Zigbee Network and associated plugs disconnected, and monitored the situation over the next 12- 18 hours using a combibation of green Ping flags in AstroMove and up to date timestamps on  AllSkyWeather and Observatory charts on Website.

2022-12-23
a)  Ethernet Connectivity is working ok with the Zigbee Network disabled and with plugs to Pulsar Dome, Dehumidifier, AllSky Heater and Aux Light all turned off  (15 hour test)

b) Dome noted to be a couple of degrees from its standard park position (Az 90) meaning that Induction Charging was also certainly compromised.  Could this have set up current fluctuations that   caused problems to the 'Ethernet over PowerLine' signal . Dome moved to its correct Park position and resynced it to Az 90 using DeviceHub's Dome Tab.

c)  Ethernet Connectivity is working ok with the Zigbee Network Connected and with power connected to Aux Light's smart plug  and with power connected directly to Pulsar Dome (ie without Smart Plug)   (6 hour test)

c)  Ethernet Connectivity is working ok  with the Zigbee Network Connected and with power connected to the  Aux Light's, Dehumidifier's and AllSky Heater's smart plugs and with power connected directly to Pulsar Dome (ie without Smart Plug)   (4 hour test)

d) Ethernet Connectivity issue returned after 35 mins with the Zigbee Network Connected and with power connected to the Aux Light, Dehumidifier, AllSky Heater and Pulsar Dome via smart plugs  (started at 22:15, Ethernet went down at 22:50 as part of planned 9 hour test, but came on before midnight

2022-12-24.
a) Added a LAN Ping monitor to AstroMove 1.9.9 to record when computers are reachable with a ping and when they are not.
b) No outages in Observatory Ethernet

2022-12-25.
a) No outages in Observatory Ethernet

2022-12-26.
a) Added a LAN Speed Check to measure LAN performance and help in the identification of improvements to improve LAN performance & speed

b) Measurements identified that earlier relocation of Observatory Ethernet Over Powerline adapter has a deterimental affect on LAN performance
-  Av Speed with adapter in socket 3  :    5.78 Mbps, 0.72 MB/s (Laptop9),    4.58 Mbps, 0.57 MB/s (Laptop7)
-  Av Speed with adapter in socket 1  :  19.72 Mbps, 2.47 MB/s (Laptop9),  23.91 Mbps, 2.99 MB/s (Laptop7),   VNC to Laptop9 on
-  Av Speed with adapter in socket 1  :  23.67 Mbps, 2.96 MB/s (Laptop9),  23.84 Mbps, 2.98 MB/s (Laptop7) ,  VNC to Laptop9 off

c) No outages in Observatory Ethernet

Findings & Conclusions

The exact cause of the issue before, during and after session S1074 is uncertain.

 - It could have been due to a temporary issue with the Power Supply (spikes, lowered voltage ?)
 - It may have been due to the interference effect of a particular fluctuation in current supply due to power induction charging of the Dome Shutter when it was sitting at a particular offset (but this hasn't been previously seen)

An important finding was that even if the LAN connection to house computer and to internet does down the normal LAN communications between Observatory and AllSkyWeather Computers wasn't interrupted. This is significant and means that a session can be expected to and be permitted to continue as the session can still be conducted safely based on the Observatory Cloud Sensor and AllSky Camera. The chance of success session is probably similar.  The one area of slightly enhanced risk is that the usually available 60 min precipitation forecast from radar wouldn't be available unless it can still be gleaned over wifi.

Actions
Image  Make a number of small fixes and improvements to AstroMain Zigbee reporting & ObsViewer picture drawing.

Image  Keep Observatory's Ethernet over Powerline adapter on Socket 1 (one that is closed to observatory's power supply input).

Issue deemed to be resolved 2022-12-25.  No LAN or Ethernet connection issues during sessions S1075 & S1076 (2022-12-26 & 2022-12-27).


Update:
There was a further period of interruption to LAN/Router & Internet Connection in Sept 2024 during which there were 5 outages within a 24 hour period (see Investigation - Interruptions in LAN & Internet Connectivity, 2024-09-08 ). An investigation concluded that user attempts to fix/shortern the outages probably didn't work and that certain actions like resetting the Observatory's Ethernet Switch can actually lead to more problems. It is probably best to leave thing to resolve themselves and only intervene if connection is still down after 24 hours. An improvement was made in AstroMain 3.69.6 to provide better recording & alerting of LAN/Internet Outages.  A proposal was made to consider installing a dedicated Ethernet Cable between Observatory and House/Router.

Update 2024-10-19
A Cat 6 Ethernet Cable was finally installed between Router and Observatory's Ethernet Switch on 2024-10-18 / 2024-10-19. As well as the expected better reliability intial speed tests show that the Cat6 Wired Ethernet Connection to Observatory is 4x faster than the preceeding Ethernet Over PowerLine Connection. For more details see Observatory - Wired Ethernet Cable Connection, 2024-10-18/19 .

Back to Top