David's Astronomy Pages Notes - Session 1226 (2024-08-10)

Notes (S1225)

Notes Main

Home Page

Notes (S1227)

	Session Aims & Highlights
	- Observing Result  - Night Summary Plot  - Session Event Log
	Operational Issues
	- Critical Issues (0),  Major Issues (0),  Minor Issues (7),  Small Defects (5),  Continuous Improvement (2)
	Images from 2024-08-10 >>

Session Aims & Highlights (2024-08-10)

Main aims

1. Targets.  Acquire images of a selection of variable stars, nearby stars, comets & deep sky targets as allowed by sky conditions.
2. Autostart.  Test modified routine in AstroMain 3.69.2 with workaround fix to reliably connect to Telescope during AutoStart

 Equipment & Software

• 12" LX200 and ST-10XME
• 80mm APO and ZWO ASI 178MC
• TheSky6, CCDSoft5, DeviceHub 6.6.1.1,  MeadeGeneric 1.3.9, 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.13, Siril 1.0.6, deCONZ 1.18.2, ASCOM 6.6 SP1
• [ DomeLink 1.0 / 1.1 - not used ]
   
• AstroMain 3.69.2,  AstroPlan 1.40.6,  AstroShCap 1.3.15, AstroGuard 1.10.5   (any new items or versions in bold)
  AstroVOE 1.13.2,  AstroSN 1.10.4,  AstroProtect 1.7,  AstroMove 1.12.12
  AstroWeather 1.24.3, AstroAllSky 3.20.4,  AstroObsCam 1.11.4 (not 1.11.5), AstroLaunch 1.11.3

Highlights-

• Autostart.  Telescope Connection was successfully made upon 2nd automated attempt during initial Autostart operation to Start Observatory Services.
• Targets. 13/14 planned targets observations were completed, with 1 other target partially completed .
• Dome. No issues opening/closing shutter during session. Dome closed and parked ok at end of session.

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 23:53:52 Session Monitoring AutoStart monitoring for Live Session opportunity between 23:53 & 03:11 23:53:56 Session AutoStarting Session autostarting (23:53) 23:54:18   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.) 23:54:47   Camera1 Connected SBIG Camera connected (Set point -10°C) 23:54:49 Session Created Session Created (Live, 2024-08-10 S01226, ImageSaveNum: 1226001) 23:54:54   Scope Switched On Telescope Power has been switched on via UPB Powerbox. 23:56:52   Services Started Observatory Services started 23:56:59 Observatory (Auto) Observatory placed in Fully-Automated Mode 23:57:01 Session Pending Session pending (2024-08-10) 23:57:03 Session Initiating Session initiating (2024-08-10) 23:57:12   Camera1 Connected SBIG Camera connected (Set point -10°C) 23:57:19   Plan Requested Observing Plan requested from AstroPlan (1.40.6) 23:58:10   Plan Loaded Observing Plan loaded to queue (Plan ID: 1001) 23:58:51   Telescope Connected Telescope connected (TheSky6) 23:59:15 Session Equilibration Session ready to Open Dome 00:00:00   Dome Opened Dome opened (Opening time 45s, Zigbee 40s) 00:00:20 Session Running Session running 00:00:23   Queue Started Observing Queue started (14 targets selected) 00:00:26     Target Started (NrZen) Target started (Focus Field 20, HIP 98535) 00:00:37       Dome Unparked Dome unparked 00:03:43       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:08:13       Focusing Completed Foc1 AutoFocus Completed (Profile No 1, wide) 00:10:47       Focusing Failed Foc1 focusing failed (failed QC check - RmsE) 00:10:50       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 00:13:00       Focusing Completed Foc2 AutoFocus Completed (Profile No 2, wide) 00:14:44       Focusing Completed Foc2 AutoFocus Completed (Profile No 2) 00:15:01     Target Completed (NrZen) Target completed (Focus Field 20, HIP 98535) 00:15:05     Target Started (1/14) Target started (1/14, HIP 87937) 00:18:10       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:22:05       Focusing Completed Foc1 AutoFocus Completed (Profile No 3, wide) 00:24:16       Focusing Completed Foc1 AutoFocus Completed (Profile No 3) 00:26:56     Target Completed Target completed (1/14, HIP 87937) 00:27:00     Target Started (2/14) Target started (2/14, C/2023 V4 (Camarasa-Duszanowi) 00:44:19     Target Completed Target completed (2/14, C/2023 V4 (Camarasa-Duszanowi) 00:44:23     Target Started (3/14) Target started (3/14, AT2022pix (CV)) 00:53:18     Target Completed Target completed (3/14, AT2022pix (CV)) 00:53:22     Target Started (4/14) Target started (4/14, C/2021 S3 (PANSTARRS)) 00:56:25       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:58:53       Focusing Completed Foc1 AutoFocus Completed (Profile No 4) 01:06:57     Target Completed Target completed (4/14, C/2021 S3 (PANSTARRS)) 01:07:01     Target Started (5/14) Target started (5/14, 61 Cyg) 01:10:33       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:12:47       Focusing Completed Foc1 AutoFocus Completed (Profile No 5) 01:14:27     Target Completed Target completed (5/14, 61 Cyg) 01:14:31     Target Started (6/14) Target started (6/14, GCVS SS Cyg) 01:17:23       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:19:51       Focusing Completed Foc1 AutoFocus Completed (Profile No 6) 01:24:11     Target Completed Target completed (6/14, GCVS SS Cyg) 01:27:55   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 01:27:57   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 01:27:59   Queue Paused Observing Queue pausing for Session Suspension 01:28:00 Session Suspending Session suspending 01:28:50   Dome Closed Dome closed (Closing time 50s, Zigbee 43s) 01:28:53 Session Suspended Session suspended 01:31:01 Session Resuming Session resuming 01:31:46   Dome Opened Dome opened (Opening time 45s, Zigbee 40s) 01:31:48 Session Running Session running 01:31:50   Queue Resumed Observing Queue resumed 01:32:05     Target Started (7/14) Target started (7/14, GCVS HH And) 01:35:33       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 01:37:44     Target Completed Target completed (7/14, GCVS HH And) 01:40:33     Target Started (8/14) Target started (8/14, GCVS BL Lac) 01:43:20       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:45:48       Focusing Completed Foc1 AutoFocus Completed (Profile No 7) 01:49:44     Target Completed Target completed (8/14, GCVS BL Lac) 01:50:51     Target Started (9/14) Target started (9/14, WDS GRB 34) 01:53:47       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:56:06       Focusing Completed Foc1 AutoFocus Completed (Profile No 8) 01:58:14     Target Completed Target completed (9/14, WDS GRB 34) 01:59:18     Target Started (10/14) Target started (10/14, NGC 7171 w/SN2023yoo) 02:02:51       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 02:19:22     Target Completed Target completed (10/14, NGC 7171 w/SN2023yoo) 02:21:38     Target Started (11/14) Target started (11/14, 54P/de Vico-Swift-NEAT) 02:24:44       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-S) 02:36:42     Target Completed Target completed (11/14, 54P/de Vico-Swift-NEAT) 02:39:40     Target Started (12/14) Target started (12/14, M33 w/Nova M33 AT2023ypg) 02:42:41       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-S) 02:59:12     Target Completed Target completed (12/14, M33 w/Nova M33 AT2023ypg) 03:02:01     Target Started (13/14) Target started (13/14, AT2024pxr) 03:06:27       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 03:14:58   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 03:15:00   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 03:15:03     Target Aborted (13/14) Target aborted (13/14, AT2024pxr) due to cloud 03:15:05   Queue Paused Queue paused for Session Suspension 03:15:07 Session Suspending Session suspending 03:15:53   Dome Closed Dome closed (Closing time 50s, Zigbee 43s) 03:15:56 Session Suspended Session suspended 03:18:13 Session Resuming Session resuming 03:18:58   Dome Opened Dome opened (Opening time 45s, Zigbee 40s) 03:19:01 Session Running Session running 03:19:03   Queue Resumed Observing Queue resumed 03:19:05     Target Started (13/14) Target started (13/14, AT2024pxr) 03:26:48     Target Completed Target partially completed (13/14, AT2024pxr) 03:26:52     Target Started (14/14) Target started (14/14, AT2022obq (CV)) 03:29:41       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 03:35:40     Target Completed Target completed (14/14, AT2022obq (CV)) 03:35:42   Queue Completed Job Queue completed 03:35:45 Session Closing Session closing 03:36:40   Dome Closed Dome closed (Closing time 50s, Zigbee 43s) 03:37:02   Dome Parked Dome parked (parking time 14s), Az: 90.0 deg 03:38:23   Telescope Parked Telescope parked (parking time 75s total) 03:38:38   Telescope State Handbox reads 'Scope parked Turn scope off.' 03:39:00   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 03:40:23   Services Stopped Night Services stopped 03:40:26 Session Finishing Session Finishing started (Create Fits Summary, Transfer Files) 03:40:48     Dome (Find Park) Find Park started (Search Az 88.0 to 92.0°, Step 0.2°, Narrow) 03:41:42     Dome Find Park found (Best Park Az 90.2°) 03:41:48     Dome Dome has been synced at park position (Az 90.0°, Adjustment: -0.2°) 03:41:50   Dome Parked Dome parked 03:43:26   Dome Charging Dome is parked and re-charging Ok (58mA) 03:43:28 Session Finished Session Finished

Session Alerts & Alarms

Time     Type       Name Detail 03:02:11 Yellow Alert Anomalous Dome Slew Dome slew resumed at Az 131.7° (T+5.4s) 03:43:26 Green Clear Dome Charging Dome is parked and re-charging Ok (58mA)

Back to Top

Operational Issues (2024-08-10 S1226)

• Critical Issues (0)
• Major Issues (0)
• Minor Issues (7)
• Small Defects (5)
• Continuous Improvement (2)
  

[ Prev | Next ]

Critical Issues

• None

Major Issues

• None

Minor Issues

• Unable to reach Observatory & AllSky/Weather Computers (2024-08-11 21:17).  Latest AllSky Image on AllSky/Weather Computer couldn't be accessed from Development Computer at 2024-08-11 23:20.  Checking AstroMove's Remote Tab showed that both computers in the observatory ( AllSky/Weather Computer and Observatory Computer) hadn't been reachable since 21:17.  Checking the Observatory's website showed that it hadn't been updated with live pictures since 21:16.  A similar issue occurred on 2024-07-12. The likelihood is that the two computers are still connected to each other and collecting data normally.   Resetting the Ethernet Over Powerline adapter nearest the Household Router didn't resolve the issue.   Resolved following afternoon, by replugging the Ethernet Cable between Observatory's Ethernet Over PowerLine adapter & Observatory's Network Switch, and replugging the Ethernet cable going into each observatory computer (ie LAN cable into Observatory Computer and LAN cable into AllSky/Weather Computer).  Earlier in the day 2 short power cuts and/or surges related to Thunderstorm (including Lightening/Thunderclap directly above property, is likely to have reset the observatory's Network Switch.
  Resolved 2024-08-12 (Observatory, Ethernet/LAN)
   
• Short Power Outage to Observatory due to supply outage (2024-08-12 09:58).  A short power outage (5s) occurred at 09:58:28 and the UPS System went onto battery power. . Power returned at 09:58:33.  The outage was too short for implementation of safeguard / shutdown protocols to begin. This outage may or may not be associated with the impact of more distant thunderstorms on the wider electrical network.   The outage didn't have any lasting impact on data flow between the Observatory & AllSky/Weather Computers.
  Closed 2024-08-12 (Observatory, Power Supply)
   
• Communication of fresh ObsEnv data to AllSky/Weather Computer stopped (2024-08-12 12:47).  Observatory Environment & Weather Charts record an outage in OTA Temperature beginning at around 12:50 which lasted until 18:05, when the USB Cable to the UPB Powerbox was relocated from 7 Port USB Hub to Lindy USB Hub, after determining that the 7 Port USB Hub appears to have been be permanently knocked out by a likely power surge at occurred around 12:47 that corresponded with a lightening and a very load clap of thunder directly over the Observatory / House. Resetting power to the UPB Power and restarted the USB hub couldn't bring COM4 (com port to UPB Powerbox), COM5 (com port to TCF-S Focuser)  & COM6 (com port to the LX200 telescope).  The only way to get these COM ports back was to move the USB Cable to the UPB Powerbox to the Lindy USB Hub.  Moving the USB Cable back to the original 7 port USB Hub didn't work showing the the USB Hub was truely knocked out. The Eaton UPS Log show that communication with the UPS system failed at 12:43:26 before restoring at 12:43:51, indicating an outage of 25s. AstroMain records that the UPB Powerbox port as appearing to be lost at 12:43:06.
  Closed 2024-08-12 (Observatory, UPB Powerbox, USB Hubs)
   
• Short Power Outage to Observatory due to supply outage (2024-08-12 13:17).  A short power outage (5s) occurred at 13:17:30 and the UPS System went onto battery power.  Power returned at 13:17:35.  The outage was too short for implementation of safeguard / shutdown protocols to begin. This outage is likely associated with the impact of thunderstorms on the electrical network (either directly associated with lightening strike on the network or as a management response).
  Closed 2024-08-12 (Observatory, Power Supply)
   
• Failure of USB Hub (2024-08-12 12:43), Unable to connect to TCF-S Focuser &  UPB Controller (2024-08-12 17:30). Whilst trying to restore the Observatory Computer back on to the LAN Network in late afternoon on 2024-08-12 (after it had dropped out on the previous evening 2024-08-11 21:17),  it was noted that the TCF-S Focuser Service had stopped and couldn't  be restored (by restarting the UPB Software & TCF-S Service).  It was found that the UPB Software was showing an error that it couldn't find the UPB Controller.  Investigating the Device Manager showed that COM4 (com port to UPB Powerbox), COM5 (com port to TCF-S Focuser)  & COM6 (com port to the LX200 telescope) were all missing from the Ports List. Resetting power to the UPB Powerbox didn't resolve things - the 3 COM ports were still missing. Unplugging/repluging the USB Cable into the USB Hub didn't resolve the communication issue, nor did restarting the UPB Powerbox or restarting the Observatory Computer (17:07 to 17:23).  The 3 missing COM Ports were eventually restored by moving the USB Cable/Adapter that goes to the UPB Powerbox from  '7 Port USB Hub' (where it is normally connected) to an empty USB port on the 'Lindy USB Hub'.   Moving the USB Cable adapter back to the original '7 port USB Hub' for a test caused the 3 COM ports to disappear again demonstrating that the 7-Port USB Hub had been knocked out and is no longer worked. This is presumed to be associated with damage from an electrical surge event that was associated with by nearby lightning or lightening strike (heard as a very large thunder clap directly above the Observatory / House) at 12:43. Eaton UPS logs record a 25s outage in communication with the UPS System (12:43:26 to 12:43:51).  AstroMain records that communication with UPS System had failed (12:43:26), but doesn't record any outage in power.  ObsPics show Scope Power, Dew heaters & Focuser2 values suddenly becoming Unkn (white flags) at 12:43 (only returning to normal at 17:24) .  Taken together this suggests there was a brief electrical surge at around that took out the USB Hub  that was not accompanied by a power outage (or by no more than a momentary outage).  Alternatively the Hub just coincidentally happened to fail at this time.  The 7-Port USB Hub needs to be checked / tested to confirm its failure.   System to be monitored to see if it can continue using just a single USB Hub, or it requires a replacement second USB Hub.  Lightning records (https://www.lightningmaps.org/) indicate three lightning events in the immediate area between at 11:59:54 (LT or UT ?) and a further event at 12:00:15 (LT or UT). 
  Closed 2024-08-12 (Observatory, USB Hub(s) )
   
• Phone & Broadband went down (2024-08-12 18:00).  An outage in Phone and Broadband service begun around 18:00-19:00, and didn't return that evening. Problem reported to Plusnet.net the following day who indicated that our line  was affected by a "Major Service Outage" (MSO)/"Planned Engineering Works" (PEW) declared by their suppliers with a current estimated resolution time (ERT) of 2024-08-13 19:00.   Broadband service returned by this ERT time, but the phone service seemed to still be down.  Tests showed that the telephone service was working ok using an old (previous) telephone retrieved from storage and it appeared that there had been a failure of the household phone's base unit (due to electrical surge?), and the  showed that the phone service had likely returned at the same time as the Broadband service.
  Resolved 2024-08-13 (Observatory, Power Supply)
   
• AstroPlan unexpectedly crashed (2024-08-12 22:00).  Visual Studio indicates AstroPlan encountered an unhandled System.Net.NetworkInformation.PingException: 'An exception occurred during a Ping request.' in FtpOverseer() routine at line 590 (WebUpload.vb).  This occurred during period of Internet/Router outage.
     If My.Computer.Network.Ping("www.google.com", 300) OrElse My.Computer.Network.Ping("www.bbc.co.uk", 300) Then
  Code needs be embedded inside a Try..Catch..End Try block.  Fixed in AstroPlan 1.40.7
  Fixed 2024-08-13 (AstroPlan 1.40.7)

Small Defects

• Condensation/frost slugs in corners of initial CCD Images. Dessicator in SBIG Camera needs to be regenerated.  Dessicator was renewed in oven on 2024-08-14 and then returned to SBIG Camera on 2024-08-15.
  Done 2024-08-15 (SBIG Camera)
   
• UPS Monitor incorrectly reports a main power outage time as being 199 minutes long instead of 5 seconds (2024-08-12 13:17).  AstroMain reports a 'UPS Monitor / Mains Power Restored'  at 13:17:35 with the message "Mains Power restored  (...outage 199.1 min)" and doesn't report a "Running on UPS Battery" message at 13:17:30 (see Fig 1). The duration of 199.1 minutes is much longer that the duration indicated by the UPS System which was a power outage duration of only 5s (see Fig 2).  The problem seems to be that AstroMain didn't recognise & record the start of a 5s power outage ("The system is powered by the UPS battery") that occurred at 01:17:30 according to the UPS Software.  Substracting 199.1 minutes from the end of power outage (13:17:35) indicates that AstroMain was holding a Power Outage start time around 09:58, which is roughly the start time for the earlier 5s power outage. This would seem to be a bug in AstroMain's UPS Monitor and/or Power Monitor routines. Investigating further.  Was the "..system is powered by the UPS battery" record not read or it was read but it wasn't interpreted correctly.  The UpsMonitor CycleTime is 2s, which means that if UPS Software generates two records within 2s period, the first message might not be recognised by the UPS Monitor. In this case it seems likely that parsing of "Communication with UPS is restored" at 12:43:51 set 'SupplyState = PowerState.Reachable', so that when "The system is powered by the UPS battery" record was read at 13:17:30 it didn't trigger the reporting of "Running on UPS Battery",  as it failed the condition
     SupplyState = PowerState.Battery And LastSupplyState = PowerState.MainsPower
  as LastSupplyState held the value PowerState.Reachable
  Fix attemped in AstroMain 3.69.3 by reducing UpsMonitor's CycleTime from 2s to 0.5s (to reduce the chances that a new record is missed), by adding trace log messages when new UPS records are read.
  Fix attempted 2024-08-15 (AstroMain 3.69.3)
   
• AstroMain didn't report a "Communication with UPS is restored" message (2024-08-12 12:43).  Associated with an electrical storm around lunchtime on 2024-08-12 there was a temporary loss of communication with the observatory's Eaton UPS System that started at 12:43:26 which lasted until 12:43:51, an outage of 25s duration (see Fig 2). AstroMain reported the start of the communication outage at with a 'UPS Monitor Alert' with the message "Communication with UPS has failed (12:43:26)". However there was no reporting of the restoration of communications that should have been given after reading the "12:43:51 pm  Communication with UPS is restored" record from the Eaton UPS / Alarms log (see Fig 1). Investigating showed that the relevant reporting logic for restoration of UPS communications was missing from   RunUpsMonitor() routine.  Fixed in AstroMain 3.69.3.
  Fixed 2024-08-15 (AstroMain 3.69.3)
   
• AstroMain logging exceptions in PulsarDomeMonitor.CheckRelayProtection (2024-08-12 12:43).  AstroMain logging "Conversion from string "" to type 'Date' is not valid" exceptions in PulsarDomeMonitor.CheckRelayProtection. Exceptions logged between 12:43:14 and 17:07:12, and then at 17:30:05 (starting services) & 22:17:55 (starting services). Exceptions seem related to specific problem caused by thunderstorm & likely surge event at 12:43, and lthe oss of a USB hub.   Added condition 'ObsServicesThreadIsRunning() = False' to prevent exception from being logged when services are starting, as they seem to be related to an atypical transient state.
  Fixed 2024-08-15 (AstroMain 3.69.4)
   
• AstroMain's Network Monitor loop is producing excessive number of log messages.  Following the loss of LAN Network connection to / from the Observatory  at 2024-08-11 21:17 the session log file recorded an excessive number of log messages with pairs of messages every 15-16s like
  
    12:00:14.56 | Finished (Monitor) Check Network   Info | Network Monitor loop has taken 7.5s
  12:00:15.03 | Finished (Monitor) Check Network   Ok   | Network Monitor loop is operating normally again
  12:00:32.05 | Finished (Monitor) Check Network   Info | Network Monitor loop has taken 7.5s
  12:00:32.52 | Finished (Monitor) Check Network   Ok   | Network Monitor loop is operating normally again
  Messages began at 2024-08-11 21:18:29,  But before this there are random messages at various frequency (every 5-15 mins) like
  
    10:17:51.67 | Finished (Monitor) Check Network   Info | Network Monitor loop has taken 1.2s
  Changes/additions made to AstroMain 3.69.3 to help trace the issue better. Issue fixed in AstroMain 3.69.6 through a revamp of the RunNetworkMonitor() routine that was undertaken to address a somewhat related issue/defect in session S1229 (2024-09-06).
  Fixed 2024-09-08 (AstroMain 3.69.6)

Continuous Improvement

• Update AstroWeather to use OpenWeather's One-Call 3.0 API instead of previous 2.5 API.  OpenWeather's One Call 2.5 API is being depreciated, and access to the product will be stopped on 2024-08-19 according to email to OpenWeather Clients that was received 2024-08-12.  A subscription to 3.0 API is required, but previous API keys will still work.
  AstroWeather's TOpenWeather.BuildRequest() routine requires changing  "//api.openweathermap.org/data/2.5/" to api.openweathermap.org/data/3.0/.  The new API is largely unchanged, and shouldn't require any additional changes to the AstroWeather.  Changed to use 3.0 API in AstroWeather 1.25.
  Done 2024-08-13 (AstroWeather 1.25)
   
• Consider the need to replace the failed 7-port USB Hub associated with the Observatory Computing Bay. The Observatory Computer has been using 2 USB Hubs - a Lindy USB Hub and an earlier 7-port 'Other' USB Hub.  The latter 7-Port Hub has been used for connecting USB cables to the Pegasus UPB Powerbox attached to the LX200 telescope (that serves the LX200 Telescope, SBIG Camera & TCF-S Focuser) and to a external mini-hard drive., but is believed to have been knocked out (damaged) by an electrical surge that occurred during a lightening event (2024-08-12 12:43), and the USB cables for the attached devices relocated to empty ports on the Lindy USB Hub.   The 7-Port USB Hub which has seemingly should be checked / tested to confirm that it has indeed failed.   Observatory System to be monitored to see if it can continue using just a single USB Hub, or it requires a replacement second USB Hub.  A successful all-night observing session on 2024-08-13 (S1227) indicates no obvious impact of using just a single USB hub attached to Observatory Computer instead of the previous 2 Hubs, and this ticket to potentially replace the 7-Port USB Hub is therefore closed (new Hub not required).  The 7-Port (Other) USB Hub was removed from the Observatory on 2024-08-14 and indoor tests confirmed that it was no longer working correctly.  A picture showing the updated Power Configuration in the Observatory Computing Bay as at 2024-08-14 is shown in Fig 3 and incorporated into the earlier Power Configuration Notes (see Review - Uninterruptible Power Supply (UPS) for the Observatory Telescope, 2024-03-03). 
  Done 2024-08-14 (Observatory, USB Hub(s) )  *Replacement Hub not required*

[ Prev | Next ]

[ Prev | Next ]

Back to Top