Could ASCOMRemote provide a way to detect and recover a failed connection to an underlying ASCOM driver or device from the remote side?
In my setup, I have seen devices accessed through for instance GSS or ScopeDome remain available through ASCOMRemote after a hardware power cycle, connection interruption or driver restart, while subsequent attempts to use them no longer work. ASCOMRemote does not appear to recover the connection automatically.
I understand that Alpaca clients can change the driver's Connected property, where permitted by the ASCOMRemote settings, and that the server management restart command can unload and reload all drivers. What I would like is a way to recover an individual device when a normal disconnect/reconnect is insufficient, without interrupting the other devices served by ASCOMRemote.
Ideally, ASCOMRemote would report when communication with a driver has failed and allow a remote client or operator to request reconnection or recreation of that driver's instance. Ideally an automatic recovery mechanism would be useful if this can be done reliably.
I realise that detection depends on what the underlying driver reports, and that recreating a driver instance may not recover a crashed or unresponsive driver application. Is this something ASCOMRemote could support, or is there an existing recovery approach I should be using?
Could ASCOMRemote provide a way to detect and recover a failed connection to an underlying ASCOM driver or device from the remote side?
In my setup, I have seen devices accessed through for instance GSS or ScopeDome remain available through ASCOMRemote after a hardware power cycle, connection interruption or driver restart, while subsequent attempts to use them no longer work. ASCOMRemote does not appear to recover the connection automatically.
I understand that Alpaca clients can change the driver's Connected property, where permitted by the ASCOMRemote settings, and that the server management restart command can unload and reload all drivers. What I would like is a way to recover an individual device when a normal disconnect/reconnect is insufficient, without interrupting the other devices served by ASCOMRemote.
Ideally, ASCOMRemote would report when communication with a driver has failed and allow a remote client or operator to request reconnection or recreation of that driver's instance. Ideally an automatic recovery mechanism would be useful if this can be done reliably.
I realise that detection depends on what the underlying driver reports, and that recreating a driver instance may not recover a crashed or unresponsive driver application. Is this something ASCOMRemote could support, or is there an existing recovery approach I should be using?