Once in a while my mount will disconnect from The SkyX randomly, which looks to be a WIFI issue that I’m trying to sort out. Is there a way to script a response to this event that would tell The SkyX to re-connect to the mount?
This is the error I get in the logs when this happens:
2023/04/11 23:01:22 106 - CRITICAL - [Telescopio ] - [PushFunction ] - Error [1000] : The operation failed because there is no connection to the device. Error = 200.
2023/04/11 23:01:23 049 - CRITICAL - [Telescopio ] - [PushFunction ] - Error [1000] : The operation failed because there is no connection to the device. Error = 200.
2023/04/11 23:01:23 076 - CRITICAL - [Telescopio ] - [PushFunction ] - Please Check your Telescope Drive and/or Restart it. SEVERE ERROR From Telescope Data [1000] : The operation failed because there is no connection to the device. Error = 200
Stay away from non-wired connections to devices. If you cannot do this, make sure that the drivers that manage them also manage disconnections and reconnections by checking their connection status. I talk of drivers and not Voyager.
That error you report is very dangerous, it can depend on many reasons and you can’t just automatically reconnect the connection. For example, the power to the mount may have gone out and the mount may no longer be aligned correctly.
It must always be verified by a human, an automation system cannot do this.
However if it happens during the sequence you can catch the error of the sequence action and maybe decide to disconnect the setup and reconnect. but at your own risk
SETUP_NOT_CONNECTED = 3 is thrown when you start a sequence but you do not have connected the setup from startup or from dragscript TELESCOPE_NOT_CONFIGURED_CONNECTED_ERROR = 15 is thrown when you ask a goto but the telescope is not configured in the setup controls in voyager