[Daily Build] Voyager 2.3.7k version ready

Ready to download the daily build 2.3.7k of Voyager:
https://www.starkeeper.it/voyager/Voyager_Setup_2.3.7k.zip

NEW => Pattern File → Added new Pattern $$UTCDATE$$ which represents the UTC date in YYYY-MM-DD format

NEW => Pattern File → Added new Pattern $$UTCTIME$$ which represents the UTC time in HH-MM-SS format

NEW => DragScript → Added new DO IF EVEN DAY Decision block, true if the day of the month is an even number

NEW => DragScript → Added new DO IF ODD DAY Decision block, true if the day of the month is an odd number

NEW => DragScript → Added new DO IF DAY OF WEEK Decision block, true if the day of the week is one of those indicated

NEW => RoboTarget → Added new Environment variable $$RTEVENT_SUBCODE containing any Sequence error code (as for the $$SEQUENCE_FAIL_STATUS variable) readable by RoboTarget DragScript event manager

NEW → Sequence → Added new Watchdog “On Exposure Error : Abort Immediatly Sequence in Case of CameraShot Error” in the Shot tab of the Sequence Configurator

NEW → Sequence → Added new Watchdog “On Exposure Error : Abort Sequence After Consecutive CameraShot Error x” in the Shot tab of the Sequence Configurator

Thanks to everyone have contributed to this daily build with their test and report.

Daily Build is declared potentially unstable … download the last official release version to rollback

All the best
Leonardo

1 Like

We have strengthened and made the detection of errors in sequence (especially for the camera shot error) more effective. Below is an example of interception of the generic sequence error with a further decision in case of camera shot error

In this send email block a resume of all the events code and info coming from the RoboTarget printed using the ##VAR- directive. This is the text received by email:

-$$RTEVENT_CODE=2000
-$$RTEVENT_CODE_TEXT=Sequence Finished with Error
-$$RTEVENT_OPTIONAL_TEXT=12950-0-NGC1952_G - [Code=37] - CameraShot Error Consecutive [5] Exit Flag => Expose Error (12950-0-NGC1952_G_LIGHT_L__300s_BIN1_NoCoolingC_0005_20230416_163020_701_GA_OF_RPA_W_F.FIT) => CameraShot Error (Exposure Error (Server RPC non disponibile. (Eccezione da HRESULT: 0x800706BA)))
-$$RTEVENT_SUBCODE=37
-$$RTEVENT_TYPE=1
-$$RTEVENT_TYPE_TEXT=ERROR
-$$RTEVENT_TARGET=12950-0-NGC1952_G
-$$RTEVENT_TARGET_UID=5c2ae615-e715-44cb-82f9-f379f8ece4b0
-$$RTEVENT_TARGET_SET=12950-0-NGC1952
-$$RTEVENT_TARGET_SET_UID=72cc7250-b792-4f77-9f5c-ff2e5ff86357
-$$RTEVENT_TARGET_TAG=
-$$RTEVENT_TARGET_SET_TAG=420

List of environment variables and sequence exit code:
https://wiki.starkeeper.it/index.php/DragScript_Environment_Variables

THE ERROR DETECTION WORK ALSO FOR NORMAL SEQUENCE (not only for RoboTarget)!

Looks great Leonardo and should help out no end with my friends somewhat troublesome camera, being able to specifically filter out exposure errors from more generic problems.

Hi Paul, its really bad that Atik doesn’t fix the firmware/driver of this QSI camera.

All the best
Leonardo

It would be nice if we could get that sorted out but at least with these extra ways to catch errors we should be able to split out the camera errors from more generic errors like passing cloud causing guide failure, which RoboTarget manages very well without any intervention.

This is great stuff. Thank you Leo

1 Like

Thank you Leo for adding the $UTCDATE and $UTCTIME to the file naming pattern.

1 Like