Re: Issue with starting ASCOM driver from SGP #ASCOM_V2_Driver


DiscoDuck
 
Edited

Thanks Brian. I am concerned though that it used to work and now does not.

The error log starts
000001 # AP ASCOM Driver - 5.20.09
000002 # Controller: GTOCP4
000003 # Mount Type: 
000004 # O/S: Windows 7
000005 # Admin: False
000006 2020-07-25 18:03:57.257:             Load: Info      : OnTop=-1,RestorePosition=0,Left = 0, Top = 0
000007 2020-07-25 18:03:57.278:       Initialize: Info      : SafeSlewRaDec = 1
000008 2020-07-25 18:03:57.288:            ASCOM: Info      : GET InterfaceVersion = 2
000009 2020-07-25 18:03:57.298:            ASCOM: Info      : SET Connected = True
000010 2020-07-25 18:03:57.362:           Serial: Info      : Setting serial receive timeout (mSecs): 1000
000011 2020-07-25 18:03:57.362:           Serial: Info      : AP Serial - Port = 21, Speed = 9600, Timeout = 1000ms
000012 2020-07-25 18:03:57.364:           Serial: Error     : Failed to connect: Error = -3
000013 2020-07-25 18:03:57.364:     ClearBuffers: Info      : Removed 0 bytes in 0 Ticks
000014 2020-07-25 18:03:57.364:        Telescope: Info      : CommandString TX=':V#'
000015 2020-07-25 18:03:57.364:        Telescope: Warning   : Retransmits: 1
000016 2020-07-25 18:03:57.364:        Telescope: Error     : CommandString: NO Response or bad response: ':V#', Response='' -> Giving up!
000017 2020-07-25 18:03:57.364:        Telescope: Error     : RECEIVE TERMINATED ERRORS: 1
000018 2020-07-25 18:03:57.364:           Driver: Info      : CommandClear()
000019 2020-07-25 18:03:57.385:     ClearBuffers: Info      : Removed 0 bytes in 0 Ticks

And then it continues to try the same port until it gives up.
It doesn't seem to get any response. But if the timestamps are to be believed it doesn't seem to wait long enough for it to be a timeout.

Join main@ap-gto.groups.io to automatically receive all group messages.