Voyager
December 22, 2021, 9:01am
2
Hi Paul,
i’ve a friend using this camera with Voyager. The first versions of firmware have this problem but they have fixed in the last. Was a problem on a temperature management (just try without cooling to check). Try to reach the QSI support.
About your request, you can manage the sequence specific error using the DragScript Environment Variables:
Guiding watchdogs are in the sequence and with them all the retry management systems and exit for error.
You can check the exit status of Sequence (IF ERROR) and decide what to do … for your info before exit for error due to a guide problem a lot of retry will be done in Sequence.
Also when a sequence block exit in dragscript you can check the error type:
https://wiki.starkeeper.it/index.php/DragScript_Environment_Variables
$$SEQUENCE_FAIL_STATUS
https://wiki.starkeeper.it/index.php/DragScript_Environment_Variables
In the IF ERROR block of Sequence use the variable check blocks DO IF COUNTER VALUE on $$SEQUENCE_FAIL_STATUS variable for the error code you need (CAMERA_SHOT_ERROR = 37):https://wiki.starkeeper.it/index.php/DragScript_Flow_of_Control#Variable_Check
This allow you to do different thing for all the possible exit error of a Sequence.
Other example of environment variables use:
An example on how to use the environment variables managed by Voyager internally and ready to use in your DragScript.
In this case we use the Emergency variables:
$$EMEVENT_EXIT_LASTREASON
$$EMEVENT_EXIT_LASTTIME
$$EMEVENT_SUSPEND_LASTREASON
$$EMEVENT_SUSPEND_LASTTIME
and the Sequence Fail Status variable:
$$SEQUENCE_FAIL_STATUS
A DragScript to send more info on exit status and on sequence error:
1 - Start: Events At Start are ENABLE
2 - Script
3 - Sequence: Interval of 01:00:0…
All the best
1 Like