Specifying response to specific errors? (Mount Connection)

[Psyire]

Hello,

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

[Voyager]

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

The sequence error codes are here and are trappable by DragScript:
https://wiki.starkeeper.it/index.php/DragScript_Environment_Variables

Management of specific errors

I have been evaluating Voyager on a friends equipment, and his camera (A QSI 6162) appears to be a little on the fussy side, occasionally the camera will start throwing exposure errors (A generic error first time and after that “Camera not idle”) The only way to recover it is to disconnect the setup, power cycle the camera and reconnect the setup. I am sure I could manage it with a dragscript, Viking and a relay board to remotely power cycle the camera, but all sequence errors would result in t…

[Psyire]

Ok, so I understand the risks but would like to explore these options further.

I create a counter @ the beginning of the script : Counter: $$SEQUENCE_FAIL_STATUS - Init Value= 0

Then in my Sequence Error logic I have something like:

DO IF COUNTER Value : $$SEQUENCE_FAIL_STATUS is Equal to X

• Disconnect Setup
• Reconnect Setup

Question: My Errors according to the log file are:

ERROR (FINISHED) Sequence : Precise Pointing M101 - Pinwheel (Goto Target Error ([TheSky64] not connected))

&

Error [1000] : The operation failed because there is no connection to the device. Error = 200

What SEQUENCE_FAIL_STATUS variable do these correspond to? 3? 15?

[Voyager]

Error [1000] : The operation failed because there is no connection to the device. Error = 200

These are error codes outside Voyager so you cannot catch by number showed.

Answer to your request: depends on when happens the problem, in which actions
probably :

PRECISE_POINTING_ERROR = 10
GOTO_ERROR = 31
MOUNT_TRACKING_STOPPED_WATCHDOG_RETRY_END = 36

[Voyager]

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

so aren’t the ones you need