David's Astronomy - Notes 2020-09-09 (S0807)

2020-09-09 (Session 807)

Session Aims & Highlights

- Observing Result
- Night Summary Plot
- Session Event Log

Operational Issues

- Critical Issues (0), Major Issues (1), Minor Issues (9), Continuous Improvement (0)

Images from 2020-09-09 >>

2020-09-11

Dome Connection Issues

2020-09-11

Event 1
Obs.Manager monitoring picked up that Dome Port had changed from COM9 to COM14 at 2020-09-10 20:07:55. DeviceHub Dome was automatically stopped and then successfully restarted

  Obs.Manager, DomePort:      Fail      Dome Port has changed at 2020-09-10 20:07:55
  Obs.Manager, DomePort:      Fail      Dome Port has changed from COM9 to COM14

  Obs.Manager, DomePort:      Info      An attempt will be made to restart the dome connection
  DeviceHub Dome:             Ok        Stopped
  DeviceHub Dome (COM14):     Ok        Started            (ASCOM.Pulsar_Observatories_Dome.Dome)

Restarting the dome connection saw the opening a new Pulsar ASCOM Trace log:

ASCOM.Pulsar_Observatories_Dome.2008.554720.txt

ObsPics confirm the changing of COM Port from COM9 to COM14 at ~20:08.

Event 2
Obs.Manager monitoring picked up that Dome Port had been lost at 2020-09-11 00:18

Obs.Manager, DomePort: Fail Dome Port lost at 2020-09-11 00:18:28

Pulsar Trace Log shows that Volatile messages from the dome stopped at 00:18:26. However the recording of groups of Get requests every 5s (from DeviceHub) shows that the Pulsar Driver was still active Volatile records didn't resumed again until 13:19 when user intervention was made to manually stop and restart the DeviceHub.Dome.

ObsPics shows dome information (battery level, voltage etc) dropping out at 00:21:39, and remaining unavailable until the DeviceHub.Dome restart at 13:19.

Work Required

Extend 'Monitor For Change in Dome Port' section of Obs.Manager Main Cycle to report if/when a 'lost' Dome.Port resumes. This is designed to see if Dome.Port="" events are transient or extended.
Done 2020-09-11 (AstroMain 3.28.6)

Event 3
Dome Record Information stopped refreshing at 2020-09-11 19:55:34. No report / log messages or everts were generated.
The Pulsar Trace Log showed exception messages:

19:55:34.871 CommandString Exception System.IO.IOException: The I/O operation 
has been aborted because of either a thread exit or an application 
request.[0D][0A][0D][0A] at System.IO.Ports.InternalResources.WinIOError(Int32 
errorCode, String str)[0D][0A] at 
System.IO.Ports.SerialStream.EndRead(IAsyncResult asyncResult)[0D][0A] at 
System.IO.Ports.SerialStream.Read(Byte[] array, Int32 offset, Int32 count, Int32 
timeout)[0D][0A] at System.IO.Ports.SerialStream.Read(Byte[] array, Int32 
offset, Int32 count)[0D][0A] at System.IO.Ports.SerialPort.InternalRead(Char[] 
buffer, Int32 offset, Int32 count, Int32 timeout, Boolean 
countMultiByteCharsAsOne)[0D][0A] at System.IO.Ports.SerialPort.ReadTo(String 
value)[0D][0A] at System.IO.Ports.SerialPort.ReadLine()[0D][0A] at 
ASCOM.Pulsar_Observatories_Dome.Dome.CommandString(String command, Boolean raw)


19:55:34.871 Command<> Exception System.IO.IOException: The I/O operation 
has been aborted because of either a thread exit or an application 
request.[0D][0A][0D][0A] at 
ASCOM.Pulsar_Observatories_Dome.Dome.CommandString(String command, Boolean 
raw)[0D][0A] at ASCOM.Pulsar_Observatories_Dome.Dome.Command[T](String command, 
Boolean raw)

19:55:34.871 Volatile Exception System.IO.IOException: The 
I/O operation has been aborted because of either a thread exit or an application 
request.[0D][0A][0D][0A] at 
ASCOM.Pulsar_Observatories_Dome.Dome.Command[T](String command, Boolean 
raw)[0D][0A] at ASCOM.Pulsar_Observatories_Dome.Dome.CommandBool(String command, 
Boolean raw)[0D][0A] at 
ASCOM.Pulsar_Observatories_Dome.Dome.UpdateAtPark()[0D][0A] at 
ASCOM.Pulsar_Observatories_Dome.Dome.Volatile()

As a test of residual dome operability in a situation where Volatile dome records weren't refreshing an attempt was made to move the dome from 090 deg (Park Position) to 095 deg using Device Hub at 22:00 . The dome didn't move and the ASCOM Trace Log showed exception messages indicating that the Port had closed.

22:00:45.233 CommandString Exception System.InvalidOperationException: The port 
is closed.[0D][0A] at System.IO.Ports.SerialPort.Write(String text)[0D][0A] at 
System.IO.Ports.SerialPort.WriteLine(String text)[0D][0A] at 
ASCOM.Pulsar_Observatories_Dome.Dome.CommandString(String command, Boolean raw)

22:00:45.233 SlewToAzimuth Exception System.InvalidOperationException: The port 
is closed.[0D][0A] at ASCOM.Pulsar_Observatories_Dome.Dome.CommandString(String 
command, Boolean raw)[0D][0A] at 
ASCOM.Pulsar_Observatories_Dome.Dome.CommandBlind(String command, Boolean 
raw)[0D][0A] at ASCOM.Pulsar_Observatories_Dome.Dome.SlewToAzimuth(Double 
Azimuth)

Event 4
Dome Record Information stopped refreshing at 2020-09-12 07:08:33. No report / log messages or events were generated.
There were no exceptions reported in the Pulsar Trace Log.

What happening to DomeRecords stopped updating message ?

This Web Page:

Notes - Session 807 (2020-09-09)

Last Updated :

2023-02-17

Site Owner :

David Richards

Home Page :

David's Astronomy Web Site

David's Astronomy Pages
Notes - Session 807 (2020-09-09)

Session Aims & Highlights (2020-09-09)

Operational Issues (2020-09-09, S807)

2020-09-11

Dome Connection Issues

David's Astronomy Pages Notes - Session 807 (2020-09-09)

Session Aims & Highlights (2020-09-09)

Operational Issues (2020-09-09, S807)

2020-09-11

Dome Connection Issues

David's Astronomy Pages
Notes - Session 807 (2020-09-09)