Voyager Wiki - User contributions [en]

Installation

2026-02-18T14:38:56Z

Leonardo: /* Third Party Applications and Versions Supported by Voyager */

Voyager is a shareware program. The demo version is free to use. The author assumes no liability resulting
from improper use or bugs in the program. As an integrator of third-party applications, VOYAGER cannot know for sure
the behavior of other software. Any damage arising from the use of VOYAGER is not covered by any insurance.

USE AT YOUR OWN RISK!

The latest version of the application can be downloaded here:
https://software.starkeeper.it/#download_voyager_section

==Prerequisites==

VOYAGER runs on Microsoft Windows operating systems, both 32 and 64 bit. Basic requirements are:

*Operating Systems 32 / 64bit Windows XP with Service Pack 3, Windows Vista, Windows 7, Windows 8 and 8.1,

Windows 10, Windows 11

*Microsoft Dot Net 4.0
*ASCOM platform from version 6.5 SP1 and newest https://ascom-standards.org<nowiki/>{{note|If you are using a version 6.5 of ASCOM Platform please be sure to use at least the SP1 to avoid problem on target pointing. This is a declared ASCOM bugs solved in 6.5 SP1 !}}
*minimum 1024x600 screen

VOYAGER has also been tested on Mac using PARALLELS virtual environment.

===Third Party Applications and Versions Supported by Voyager===

Applications, with minimum versions, that can be managed by VOYAGER:

*CAMERA CCD / CMOS / DSLR
**connected via ASCOM Platform 6.x https://ascom-standards.org All cameras have ASCOM Driver
**or Maxim DL CCD version 5.x or later (All cameras supported from Maxim DL) COM server enabled
**or TheSkyX using Camera Add On (All cameras supported from the TheSkyX Camera Add On)
**or ASI Camera (ZWO ASI native driver direct to camera with SDK)
**or QHY Camera (QHY Native driver direct to camera with SDK)
**or FLI Camera (FLI Native driver direct to camera with LibFli.dll)
**or QSI CCD (QSI COM component released by QSI to install)

*MOUNT / TELESCOPE
**connected via ASCOM Platform 6.5 SP1 https://ascom-standards.org
**or TheSky6 Professional Edition 6.0.0.24 and later
**or TheSkyX Professional Edition 10.1.11 and later
**Array Virtual Mount (Advanced version of Voyager)

*GUIDING
**PHD2 version 2.3.0 and later
**or MaximDL 5.x and later
**or TheSkyX

*PLANETARIUM
**Cartes du Ciel
**TheSkyX
**TheSky6
**Hallo Northern Sky
**Stellarium (officially tested from version 0.21.0 using remote interface)

*PLATE SOLVING / BLIND SOLVING
**PinPoint LE version 5.x
**or PinPoint FULL version 5.x and later
**or TheSkyX ImageLink
**or PlateSolve2
**or nova.astrometry.net
**or All Sky Plate Solver
**or ASTAP

*FOCUSER
**connected via ASCOM Platform 6.5 SP1 https://ascom-standards.org
**or FocusMax 3.4.40 and later
**or MaximDL 5.x and later
**or TheSkyX @focus2 and @focus3


{{note|LakeSideAstro Focuser also if have ASCOM driver are usable with Voyager only with driver v2.0.6.0 and newest !}} 

*FLAT DEVICE
**Gemini SnapCap
**Alnitak Flat-Fielding Device
**Tecnosky TecnoCap and MultiLevel
**Arduino Flat Device
**Artesky Flat Device
**Sky Flats
**ASCOM Cover Calibrator Device
**Geoptik Flat Device
**PegasusAstro Flat device
**All ASCOM CoverCalibrator compatible

*ROTATOR
**connected via ASCOM Platform 6.5 SP1 https://ascom-standards.org
**RCOS TCC Rotator

*DOME
**connected via ASCOM Platform 6.5 SP1 https://ascom-standards.org
**ScopeDome LS with ScopeSync
**NexDome

*WEATHER
**AAG Cloudwatcher / Solo
**Boltwood / Clarity II / SkyAlert Weather Station or compatible

*OBSERVING CONDITIONS
**connected via ASCOM Platform 6.5 SP1 https://ascom-standards.org
**using Viking Client

*SKY QUALITY MONITOR (SQM)
**connected via ASCOM Platform 6.5 SP1 https://ascom-standards.org

*SAFETY MONITOR (SQM)
**connected via ASCOM Platform 6.x5 SP1 https://ascom-standards.org
**Textfile Safety Monitor
*I/O CARDS
**[[Viking]] and all supported Cards


{{note|In order to use Voyager, you must at minimum connect a Camera and Mount. 
The availability of executable actions within Voyager depends on the number and capability of connected applications.}}

=Installation Video=
There is a video on how to install Voyager on the Voyager Astro Imaging YouTube channel:
<youtube>https://www.youtube.com/watch?v=bxV48S15Mkw</youtube>

=Installation Procedure=
After downloading the installation file:

1. Start by double clicking on the downloaded file:

[[File:Voyager-setup.jpg]]

2. Voyager is a signed application as of Voyager 2.2.1. It is signed by "Starkeeper di Orazi Leonardo."

[[File:Immagine.png]]

5. Choose your installation language, English or Italiano, and click OK

[[File:Voyager-install-lang.jpg]]

6. Read the license agreement, click the I accept the agreement radio button, and click the Next button to continue installing Voyager:

[[File:Voyager-accept-agreement.jpg]]

7. Optionally, check the "Create a desktop shortcut" box and click Next to continue installing Voyager:

[[File:Voyager-create-icon.jpg]]

8. Finally, click the Install button to do the installation:

[[File:Voyager-install.jpg]]

9. You will see a dialog box with a progress bar while files are extracted and installed. Click Finish to complete the installation:

[[File:Voyager-install-complete.jpg]]

{{note|For Windows 7, Windows 8, Windows 8.1 and Windows 10 users: Voyager has to run with administrator privileges so it can communicate with other software, do operation reserved to admin about process and driver release and others necessary to make reliable the automation. The installation program set administrator privileges , it is not a good idea to remove this, some part of application will be not work. Also at next installation will be fixed to admin again.}}

1

'''Congratulations, you have installed Voyager!'''

==Voyager Folders==

When you first run VOYAGER, it will create a series of folders in your Windows user's Documents directory:

[[file:Voyager-folders.jpg]]

*Advanced
Reserved to Voyager Full/Advanced version
*ConfigSequence

Configuration files of the automated imaging sequences or automatic flat taking
sequences

* Data

Database files for various pourpouse{{note|This folder is under auto backup since release 2.3.5h of Voyager}}

* Data Backup

Database backup (backup of folder Data with age system like for Profile Backup
*FIT

FITS files (image files with metadata) created by VOYAGER actions for plate solving and test shots. These files are erased at each start of Voyager.

*GuideFIT

FITS files created by guiding actions. These are the screenshot and the jpg or fit file related to a find star problem. These files can be delete whenever you choose. However, if you need help with guiding, you will need to provide one or more files from this folder to assist in troubleshooting, so you may want to keep the last session's files at least.

*Log

Text files with the log of operations performed by Voyager. The level of information is very high. These files will be required in case of bugs to fix or anomalies to interpret.

*Orbits

Database with data related to RoboOrbits Automata

*Profile

Settings files for the various imaging system configurations you define{{note|This folder is under auto backup since release 2.3.0 of Voyager}}

*ProfileBackup

AutoSaving of Profile folder with datetime naming at each start of Voyager and before an online update of Release from Voyager. You can define age of backup to retain on this folder using the Setting of VOyager, tab Voyager, Box Profile Backup

*Renting

Ticket file system access reserved to Voyager Renting Plugin

*ScreenShot

Screenshots of the program in case of watchdog events such as guiding or other failures

*Script

DragScript files used to automate imaging sessions

*Sequence

Default folder containing the FITS files generated by running sequences, the files are sorted to subfolders that are created with the name of the target. You can override this and send FITS files to a directory of your choice in the Setup section.

==Log File==

The Log folder contains the files Voyager creates as it executes tasks. There will be a file for each day of use, and each file will contain at most the logs from 24 hours of operation. Information in the log file is intended to help the developer trace the cause of a problem in the event of application failure or malfunction.

The developer may ask you to attach a zip file with the relevant portion of the log to help track down a problem. You can use a text editor, such as Notepad or the free third party editor Notepad++ to find the time of the problem, and then trim the log file down to the relevant lines. If there are more than a few lines of interest, save the relevant lines to a new text file and then compress them into a .zip file to attach to your email requesting help.

You may be asked to email the relevant portion of the log file with a text editor, and attach a zip file in your email
They will be required as necessary to send an email. In that case it will be necessary to decrease the size of the zip file and select only the necessary period. The log file entries are timestamped, so just select the entries around the time of the problem.

==SDK Platform Folder for Voyager 32 bit==

ONLY FOR 32 BIT VERSION OF VOYAGER !

The SDK platform folder contains all the SDK/DLL Library used by Voyager for external Camera/Driver. It is organized by Vendor and internally by architecture bits.

This folder is not located in document folder but in Voyager installation folder, usually '''''C:\Program Files (x86)\Voyager'''''

[[File:92ccc2197e09170744ffef98d34e0c0a3f030b68.png]]

{{note|You can add folder inside for beta SDK version where to copy your file but attention, each voyager installation (also daily build) will overwrite the folders structures and file internally needed (your structures will remain untouched). For example if you change SDK from QHY in platform\qhy\32 each file with same name will replaced with original by Voyager installation !!}}{{note|For ZWO ASI : ASI Camera V2 SDK DLL is just under ASI folder (32) , the ASI Camer SDL DLL is under V1 folder (32)}}{{note|For QHY Beta Driver : Voyager since release 2.3.0 have a control camera dedicated to Beta driver version. If you want to manually update or change this driver use the folder paltform\QHY\BETA\32}}

== SDK Platform Folder for Voyager 64 bit ==
ONLY FOR 64BIT VERSION OF VOYAGER !

The SDK platform folder contains all the SDK/DLL Library used by Voyager for external Camera/Driver. It is organized by Vendor and internally by architecture bits.

This folder is not located in document folder but in Voyager installation folder, usually '''''C:\Program Files\Voyager'''''

[[File:Immagineeberberb.png]]

{{note|You can add folder inside for beta SDK version where to copy your file but attention, each voyager installation (also daily build) will overwrite the folders structures and file internally needed (your structures will remain untouched). For example if you change SDK from QHY in platform\qhy\64 each file with same name will replaced with original by Voyager installation !!}}
{{note|For ZWO ASI : ASI Camera V2 SDK DLL is just under ASI folder (64) , the ASI Camer SDL DLL is under V1 folder (64)}}{{note|For QHY Beta Driver : Voyager since release 2.3.0 have a control camera dedicated to Beta driver version. If you want to manually update or change this driver use the folder paltform\QHY\BETA\64}}

==Installing Previous Versions==

Retrieve the old version setup from the [https://forum.starkeeper.it/c/releases/8 Releases Category] in Voyager's forum and execute the installer.

If you can't find the version you are looking for please contact [https://software.starkeeper.it/support/ support].

==Installing Daily Build Versions==

The daily Builds are development versions of Voyager based on the current official release version. They contain new features or existing bug fixes.

They can be downloaded directly from the Voyager forum [https://forum.starkeeper.it/c/releases/8 here]. They are declared unstable as they have not been tested and their installation is on a voluntary basis.

To go back from the Daily Build versions you need to reinstall the original release version.

[[Category:All]]
[[Category:Manual|C]]

Installation

2026-02-18T14:13:48Z

Leonardo: /* Third Party Applications and Versions Supported by Voyager */

Voyager is a shareware program. The demo version is free to use. The author assumes no liability resulting
from improper use or bugs in the program. As an integrator of third-party applications, VOYAGER cannot know for sure
the behavior of other software. Any damage arising from the use of VOYAGER is not covered by any insurance.

USE AT YOUR OWN RISK!

The latest version of the application can be downloaded here:
https://software.starkeeper.it/#download_voyager_section

==Prerequisites==

VOYAGER runs on Microsoft Windows operating systems, both 32 and 64 bit. Basic requirements are:

*Operating Systems 32 / 64bit Windows XP with Service Pack 3, Windows Vista, Windows 7, Windows 8 and 8.1,

Windows 10, Windows 11

*Microsoft Dot Net 4.0
*ASCOM platform from version 6.5 SP1 and newest https://ascom-standards.org<nowiki/>{{note|If you are using a version 6.5 of ASCOM Platform please be sure to use at least the SP1 to avoid problem on target pointing. This is a declared ASCOM bugs solved in 6.5 SP1 !}}
*minimum 1024x600 screen

VOYAGER has also been tested on Mac using PARALLELS virtual environment.

===Third Party Applications and Versions Supported by Voyager===

Applications, with minimum versions, that can be managed by VOYAGER:

*CAMERA CCD / CMOS / DSLR
**connected via ASCOM Platform 6.x https://ascom-standards.org All cameras have ASCOM Driver
**or Maxim DL CCD version 5.x or later (All cameras supported from Maxim DL) Only 32bit version or COM server enabled
**or TheSkyX using Camera Add On (All cameras supported from the TheSkyX Camera Add On)
**or ASI Camera (ZWO ASI native driver direct to camera with SDK)
**or QHY Camera (QHY Native driver direct to camera with SDK)
**or FLI Camera (FLI Native driver direct to camera with LibFli.dll)
**or QSI CCD (QSI COM component released by QSI to install)

*MOUNT / TELESCOPE
**connected via ASCOM Platform 6.5 SP1 https://ascom-standards.org
**or TheSky6 Professional Edition 6.0.0.24 and later
**or TheSkyX Professional Edition 10.1.11 and later
**Array Virtual Mount (Advanced version of Voyager)

*GUIDING
**PHD2 version 2.3.0 and later
**or MaximDL 5.x and later
**or TheSkyX

*PLANETARIUM
**Cartes du Ciel
**TheSkyX
**TheSky6
**Hallo Northern Sky
**Stellarium (officially tested from version 0.21.0 using remote interface)

*PLATE SOLVING / BLIND SOLVING
**PinPoint LE version 5.x
**or PinPoint FULL version 5.x and later
**or TheSkyX ImageLink
**or PlateSolve2
**or nova.astrometry.net
**or All Sky Plate Solver
**or ASTAP

*FOCUSER
**connected via ASCOM Platform 6.5 SP1 https://ascom-standards.org
**or FocusMax 3.4.40 and later
**or MaximDL 5.x and later
**or TheSkyX @focus2 and @focus3


{{note|LakeSideAstro Focuser also if have ASCOM driver are usable with Voyager only with driver v2.0.6.0 and newest !}} 

*FLAT DEVICE
**Gemini SnapCap
**Alnitak Flat-Fielding Device
**Tecnosky TecnoCap and MultiLevel
**Arduino Flat Device
**Artesky Flat Device
**Sky Flats
**ASCOM Cover Calibrator Device
**Geoptik Flat Device
**PegasusAstro Flat device
**All ASCOM CoverCalibrator compatible

*ROTATOR
**connected via ASCOM Platform 6.5 SP1 https://ascom-standards.org
**RCOS TCC Rotator

*DOME
**connected via ASCOM Platform 6.5 SP1 https://ascom-standards.org
**ScopeDome LS with ScopeSync
**NexDome

*WEATHER
**AAG Cloudwatcher / Solo
**Boltwood / Clarity II / SkyAlert Weather Station or compatible

*OBSERVING CONDITIONS
**connected via ASCOM Platform 6.5 SP1 https://ascom-standards.org
**using Viking Client

*SKY QUALITY MONITOR (SQM)
**connected via ASCOM Platform 6.5 SP1 https://ascom-standards.org

*SAFETY MONITOR (SQM)
**connected via ASCOM Platform 6.x5 SP1 https://ascom-standards.org
**Textfile Safety Monitor
*I/O CARDS
**[[Viking]] and all supported Cards


{{note|In order to use Voyager, you must at minimum connect a Camera and Mount. 
The availability of executable actions within Voyager depends on the number and capability of connected applications.}}

=Installation Video=
There is a video on how to install Voyager on the Voyager Astro Imaging YouTube channel:
<youtube>https://www.youtube.com/watch?v=bxV48S15Mkw</youtube>

=Installation Procedure=
After downloading the installation file:

1. Start by double clicking on the downloaded file:

[[File:Voyager-setup.jpg]]

2. Voyager is a signed application as of Voyager 2.2.1. It is signed by "Starkeeper di Orazi Leonardo."

[[File:Immagine.png]]

5. Choose your installation language, English or Italiano, and click OK

[[File:Voyager-install-lang.jpg]]

6. Read the license agreement, click the I accept the agreement radio button, and click the Next button to continue installing Voyager:

[[File:Voyager-accept-agreement.jpg]]

7. Optionally, check the "Create a desktop shortcut" box and click Next to continue installing Voyager:

[[File:Voyager-create-icon.jpg]]

8. Finally, click the Install button to do the installation:

[[File:Voyager-install.jpg]]

9. You will see a dialog box with a progress bar while files are extracted and installed. Click Finish to complete the installation:

[[File:Voyager-install-complete.jpg]]

{{note|For Windows 7, Windows 8, Windows 8.1 and Windows 10 users: Voyager has to run with administrator privileges so it can communicate with other software, do operation reserved to admin about process and driver release and others necessary to make reliable the automation. The installation program set administrator privileges , it is not a good idea to remove this, some part of application will be not work. Also at next installation will be fixed to admin again.}}

1

'''Congratulations, you have installed Voyager!'''

==Voyager Folders==

When you first run VOYAGER, it will create a series of folders in your Windows user's Documents directory:

[[file:Voyager-folders.jpg]]

*Advanced
Reserved to Voyager Full/Advanced version
*ConfigSequence

Configuration files of the automated imaging sequences or automatic flat taking
sequences

* Data

Database files for various pourpouse{{note|This folder is under auto backup since release 2.3.5h of Voyager}}

* Data Backup

Database backup (backup of folder Data with age system like for Profile Backup
*FIT

FITS files (image files with metadata) created by VOYAGER actions for plate solving and test shots. These files are erased at each start of Voyager.

*GuideFIT

FITS files created by guiding actions. These are the screenshot and the jpg or fit file related to a find star problem. These files can be delete whenever you choose. However, if you need help with guiding, you will need to provide one or more files from this folder to assist in troubleshooting, so you may want to keep the last session's files at least.

*Log

Text files with the log of operations performed by Voyager. The level of information is very high. These files will be required in case of bugs to fix or anomalies to interpret.

*Orbits

Database with data related to RoboOrbits Automata

*Profile

Settings files for the various imaging system configurations you define{{note|This folder is under auto backup since release 2.3.0 of Voyager}}

*ProfileBackup

AutoSaving of Profile folder with datetime naming at each start of Voyager and before an online update of Release from Voyager. You can define age of backup to retain on this folder using the Setting of VOyager, tab Voyager, Box Profile Backup

*Renting

Ticket file system access reserved to Voyager Renting Plugin

*ScreenShot

Screenshots of the program in case of watchdog events such as guiding or other failures

*Script

DragScript files used to automate imaging sessions

*Sequence

Default folder containing the FITS files generated by running sequences, the files are sorted to subfolders that are created with the name of the target. You can override this and send FITS files to a directory of your choice in the Setup section.

==Log File==

The Log folder contains the files Voyager creates as it executes tasks. There will be a file for each day of use, and each file will contain at most the logs from 24 hours of operation. Information in the log file is intended to help the developer trace the cause of a problem in the event of application failure or malfunction.

The developer may ask you to attach a zip file with the relevant portion of the log to help track down a problem. You can use a text editor, such as Notepad or the free third party editor Notepad++ to find the time of the problem, and then trim the log file down to the relevant lines. If there are more than a few lines of interest, save the relevant lines to a new text file and then compress them into a .zip file to attach to your email requesting help.

You may be asked to email the relevant portion of the log file with a text editor, and attach a zip file in your email
They will be required as necessary to send an email. In that case it will be necessary to decrease the size of the zip file and select only the necessary period. The log file entries are timestamped, so just select the entries around the time of the problem.

==SDK Platform Folder for Voyager 32 bit==

ONLY FOR 32 BIT VERSION OF VOYAGER !

The SDK platform folder contains all the SDK/DLL Library used by Voyager for external Camera/Driver. It is organized by Vendor and internally by architecture bits.

This folder is not located in document folder but in Voyager installation folder, usually '''''C:\Program Files (x86)\Voyager'''''

[[File:92ccc2197e09170744ffef98d34e0c0a3f030b68.png]]

{{note|You can add folder inside for beta SDK version where to copy your file but attention, each voyager installation (also daily build) will overwrite the folders structures and file internally needed (your structures will remain untouched). For example if you change SDK from QHY in platform\qhy\32 each file with same name will replaced with original by Voyager installation !!}}{{note|For ZWO ASI : ASI Camera V2 SDK DLL is just under ASI folder (32) , the ASI Camer SDL DLL is under V1 folder (32)}}{{note|For QHY Beta Driver : Voyager since release 2.3.0 have a control camera dedicated to Beta driver version. If you want to manually update or change this driver use the folder paltform\QHY\BETA\32}}

== SDK Platform Folder for Voyager 64 bit ==
ONLY FOR 64BIT VERSION OF VOYAGER !

The SDK platform folder contains all the SDK/DLL Library used by Voyager for external Camera/Driver. It is organized by Vendor and internally by architecture bits.

This folder is not located in document folder but in Voyager installation folder, usually '''''C:\Program Files\Voyager'''''

[[File:Immagineeberberb.png]]

{{note|You can add folder inside for beta SDK version where to copy your file but attention, each voyager installation (also daily build) will overwrite the folders structures and file internally needed (your structures will remain untouched). For example if you change SDK from QHY in platform\qhy\64 each file with same name will replaced with original by Voyager installation !!}}
{{note|For ZWO ASI : ASI Camera V2 SDK DLL is just under ASI folder (64) , the ASI Camer SDL DLL is under V1 folder (64)}}{{note|For QHY Beta Driver : Voyager since release 2.3.0 have a control camera dedicated to Beta driver version. If you want to manually update or change this driver use the folder paltform\QHY\BETA\64}}

==Installing Previous Versions==

Retrieve the old version setup from the [https://forum.starkeeper.it/c/releases/8 Releases Category] in Voyager's forum and execute the installer.

If you can't find the version you are looking for please contact [https://software.starkeeper.it/support/ support].

==Installing Daily Build Versions==

The daily Builds are development versions of Voyager based on the current official release version. They contain new features or existing bug fixes.

They can be downloaded directly from the Voyager forum [https://forum.starkeeper.it/c/releases/8 here]. They are declared unstable as they have not been tested and their installation is on a voluntary basis.

To go back from the Daily Build versions you need to reinstall the original release version.

[[Category:All]]
[[Category:Manual|C]]

MediaWiki:Sidebar

2025-12-08T11:45:43Z

Leonardo:

Version

2025-12-08T11:45:25Z

Leonardo: /* Voyager Version */

==Voyager Version==
The version of Voyager documented by this Wiki is: 2.3.14 -> (Daily Build 2025-12-08) -> 32 and 64 bit version

Voyager Release information is here: https://forum.starkeeper.it/c/releases

Camera Setup

2025-10-23T08:53:43Z

Leonardo: /* CMOS ASCOM Camera V2 */

==Camera Setup Workspace==
Click the Camera button in the Setup workspace to display the Camera setup window:

[[File:Camera-setup-217d.jpg]]
 {{Note|Camera selection must be filled out - this is mandatory for proper operation of Voyager}} 

==Color Coding==
Throughout the Setup workspace, Voyager uses color to indicate the following:

*'''Black''': A normal setting
*Gold or Yellow: Use caution when changing as things may not work well or as expected
*Red: Use extreme care when changing this setting - the wrong value can damage your equipment or the imaging session may fail

==Camera Choice==
Voyager supports the following ways to connect to a camera:

[[File:Setup-camera-216c.jpg]]

*ASCOM Camera
*ASI Camera (with ASI SDK frozen to 1.16.0 version)
*ASI Camera V2 [starting from Voyager Daily Build 2.2.16h] (for cameras need SDK equal or greater than 1.16.3 and/or using FPGA binning mode like ASI294MM Pro)
*CAM8S Camera
*CMOS ASCOM Camera V2 [starting from Voyager Daily Build 2.3.4j] (ONLY for CMOS cameras using '''ASCOM Camera Interface V2''' and having numeric '''Gain''' managed in driver - Like all MORAVIAN CMOS)
*CMOS ASCOM Camera V3 [starting from Voyager Daily Build 2.3.13] (ONLY for CMOS cameras using '''ASCOM Camera Interface V3''' and having numeric '''Gain''' and numeric '''Offset''' managed in driver - All CMOS camera support this version of ASCOM driver)
*FLI CCD Camera
*Maxim DL
*Player One Astronomy Camera
*QHY CMOS Camera
*QHY CMOS Camera BETA [starting from Voyager 2.3.0] (for using your QHY camera whit the last Beta SDK released from QHY, Beta version embedded in Voyager depend on relase or daily build creation)
*QSI Camera
*SX ASCOM Camera
*TheSkyX Camera Add On
*TheSky64 Camera Add On

Visit the [[Installation#Prerequisites|Installation Prerequisites]] section to see which versions of these third party applications are supported by Voyager.

Depending on the Camera selection, different configuration options are available, so make this selection first.

For ASCOM connected cameras, the Camera Advanced Config button brings up the ASCOM Properties dialog. The ASCOM button brings up the ASCOM chooser dialog - use this to select the specific ASCOM camera for this configuration.

== CMOS ASCOM Camera V2 ==
Choose CMOS ASCOM Camera V2 if you have a CMOS camera without native support in Voyager and you want to use the numeric Gain configurable in Sequence slots. The camera must have ASCOM driver implements ICamera V2 interface. You can ask to support if your camera are in the list of suitable for this kind of drivers. Usually all the cameras with ASCOM 5.x and newer.

The difference between normal ASCOM driver choice in Voyager is the possibility to use Gain in Sequence slots to define custom gain value for each shot.

The default Gain for plate solve and focus shot are defined in the Camera Setup tab:[[File:235eegwegweg.png]]

== CMOS ASCOM Camera V3 ==
Choose CMOS ASCOM Camera V3 if you have a CMOS camera without native support in Voyager and you want to use the numeric Gain and numeri Offset configurable in Sequence slots. The camera must have ASCOM driver implements ICamera V3 interface. You can ask to support if your camera are in the list of suitable for this kind of drivers. Usually all the cameras with ASCOM 6.5 and newer.

The difference between normal ASCOM driver choice in Voyager is the possibility to use Gain and Offset in Sequence slots to define custom gain value for each shot.

The default Gain and Offset for plate solve and focus shot are defined in the Camera Setup tab:

[[File:Immagine2dwfwef.png]]

==TheSkyX Camera Add On==
If you choose TheSkyX Camera Add On from the Camera drop-down list, Voyager will connect directly to TSX configured Camera and Filter Wheel. {{Note|Please remove the AutoSave flag in TheSkyX Camera Add On to prevents CFITSIO error during Voyager FIT data management. Voyager will save for you all the data needed.}}

==Info about Camera Driver / SDK / ASCOM Driver ==
Some clarification about level of drivers, especially for CMOS cameras:

* Camera Driver (low level file needed by Camera to work with your OS, usually contains also the firmware will be loaded on camera for some brand/models) this must be installed in anycase and usually are not included in SDK and ASCOM driver
* SDK (mid level file for allow application to talk with the camera driver, can be used to direct access to camera) this not include camera driver usually depends on camera brands
* ASCOM Driver (ASCOM platform file allow all application compatible with ASCOM to work with camera, use SDK to access to camera driver) not include camera driver but usually include SDK, location of the SDK usually is not the right one for the application use only SDK … this is the reason if you install newer ASCOM driver not mean automatically you will have your application with updated SDK.

SDK with direct access is the most performant usually especially for CMOS with big size sensor.

Voyager have direct driver using SDK for some CMOS / CCD cameras, brands usually have a Beta Release of driver for the new cameras or just released on market. So if you want to use beta driver and upate ones used in Voyager in the wiki is described how to do or in the page of each single brand. (basically download SDK file and copy on Voyager SDK Platform folder). See [https://wiki.starkeeper.it/index.php/Installation#SDK_Platform_Folder Voyager SDK Platform folder]. Some brand like ASI and QHY have double camera control in voyager to use stable or beta version of SDK.

In any case, we will not be responsible for any malfunctions or strange behaviors.

If you have problems with these drivers, first open a support ticket at your CMOS support service.

'''A last thing, like wrote in wiki, if you will update Voyager installation with a new daily build or release we will install back the choosed driver by Voyager.'''

==QSI Native Driver==
If you choose QSI Camera from the Camera drop-down list, Voyager will connect directly to your QSI camera using the COM object released with the their SDK (not via ASCOM).

Usually until 6.x version of the CD installation software of QSI this will be included in the main installation of CD, now ATIK (owner of QSI) seems to have removed it and trust only on ASCOM driver.

How to allow Voyager work with QSI SDK driver ?

'''You can use the legacy driver installation (instead of the last version):'''

https://qsimaging.com/drivers-software/#cd-and-drivers

''<code>"Our legacy installer includes our old ASCOM driver '''QSI Installer''' (.zip) 30.9MB v1.0.0.3"</code>''

'''You can download from here the SDK:'''

https://qsimaging.com/drivers-software/#custom

Open the QSI folder inside and install it like for instructions in the readme.txt:

''<code>"Installation of QSICamera.dll requires the use of regsvr32 to register the dll in the Windows Registry.</code>''

''<code>We recommend placing QSICamera.dll in C:\Windows\System32 and then calling regsvr32 from powershell run as an administrator.</code>''

''<code> PS C:\WINDOWS\system32> regsvr32 .\QSICamera.dll</code>''

''<code>Note: On a 64 bit machine</code>''

''<code> QSICamera.dll from the x64 folder should be placed in C:\Windows\System32</code>''

''<code> QSICamera.dll from the x32 folder should be placed in C:\Windows\SysWOW64</code>''

''<code>To unregister you will need to call regsvr32 with the /u argument.</code>''

''<code> PS C:\WINDOWS\system32> regsvr32 /u .\QSICamera.dll"</code>''

We do not put this on Voyager installation to avoid retro compatibility problem with camera having 5.x and 6.x version of firmware, we are not sure all working fine with the 7.x SDK.

'''If you have a 5.x or 6.x installation CD the SDK will be installed automatically with the main installation menù.'''

If you want direct support please contact us for remote checking.

==ASI Native Driver / ASI Native Driver V2==
If you choose ASI Camera or ASI Camera V2 from the Camera drop-down list, Voyager will connect directly to your ZWO ASI camera (not via ASCOM).

{{Note|Difference between the two ASI Native driver:

- ASI Camera (with ASI SDK frozen to 1.16.0 version)

- ASI Camera V2 [starting from Voyager Daily Build 2.2.16h] (for camera need SDK equal or greater than 1.16.3 and/or using FPGA binning mode like ASI294MM Pro)}}

Click the Camera Advanced Config button to bring up the ASI Camera Setup dialog:

[[File:Zwo-camera-advanced.jpg]]

The ASI Camera Setup dialog is very similar to the ZWO ASI ASCOM dialog:

[[File:Zwo-asi-native-driver.jpg]]

 {{Note|You set default values for Gain, Offset and USB Limit in this dialog. You can override these values when you define a Sequence or Research and Survey definition on a per-element (group of exposures for a given filter) basis}} 

*'''Connected Cameras:''' Choose the camera from the drop-down list
**'''Edit:''' Click the Edit button if you would like to use a different name for the camera selected from the drop-down list
**'''USB Type:''' Displays the type of USB connection, USB3 or USB2
**'''Bayer Pattern:''' Displays the Bayer Matrix pattern If the '''Connected Camera''' has a color sensor
**'''Temperature:''' Displays the sensor temperature returned by the camera
**'''MonoBin:''' If checked and If the connected camera has a color sensor, the pixels from the color sensor are binned by the camera and a monochrome image is returned
**

*'''Preset:''' Choose a preset from the drop-down list and the preset's values will be applied to the settings for Gain, Offset and USB Limit
**[[File:Asi-preset-custom.jpg]]
**Choose one of the User presets (User 1, User 2, etc.) to create a custom preset for Gain, Offset and USB Limit
**Click the '''Edit Name''' button to change the preset name from User X to a name of your choosing:
**[[File:Asi-preset-editname.jpg]]
*'''ASI Reset Voyager Preset Setting:''' Click to reset any custom (User 1, User 2, etc) presets you created in this profile. This button appears in the top-level Camera Setup dialog if you choose ASI Camera
**[[File:Asi-reset-preset.jpg]]
*'''Gain, Offset and USB Limit Sliders:''' Click and drag these sliders with your mouse, or click on the slider and use the up and down or left and right arrows to change the values. If you change the values this way, the Preset drop-down list changes to Manual
**[[File:Asi-gain-sliders.jpg]]
*'''Gain:''' Move the slider to set the gain value. See your camera's manual for an explanation of how your choice here affects your image
*'''Offset:''' Move the slider to set the offset value. See your camera's manual for an explanation of how your choice here affects your image
*'''USB Limit:''' Move the slider to set the USB limit value. This controls how fast the camera sends data to the USB port. If your download does not finish, try a lower setting.
*'''Remove Gain Limit Management:''' (Starting from Voyager 2.2.14b version) ASI Camera driver (like for ASI specific) limit the maximum gain for DSO use, calculus is automatically done. If you want to use gain up to raw max gain, check this flag and reopen the form. If you use high gain level for this cameras you can shrink in a bad way the full well capacity and increase drammatically the noise. '''Use at your risk !'''
*'''Cancel:''' Discard changes and exit this dialog
*'''OK:''' Save changes and exit this dialog 
{{Note|The ASI Camera native driver is the only way to control the Gain and Offset values of a ZWO ASI camera from Voyager. You cannot control them from Voyager if you use the ASCOM driver to connect to your ASI camera}}

==ASI Camera Name Match==
Tells Voyager to check the ASI Camera name on connection if you are using the ASI Camera (not ASCOM) driver.

[[File:Asi-camera-name-217d.jpg]]

*'''Raise Error On Camera Connect in Startup if Name Not Match:''' If checked and the ASI Camera camera type has been selected, Voyager will raise an error when connecting to the camera if the camera name specified in setup does not match the camera name returned by the driver.

 

==FLI CCD Native Driver==
If you choose FLI CCD Camera from the Camera drop-down list, Voyager will connect directly to your FLI CCD camera (not via ASCOM) and if you want directly also to your FLI Filter Wheel.

Click the Camera Advanced Config button to bring up the FLI CCD Camera Setup dialog:

[[File:FLICameraChoose.png]]

The FLI CCD Camera Setup dialog is this one:

[[File:FLISettingForm.png]]

* '''Camera Chooser:''' Choose the camera from the drop-down list, the camera must be connected to open the settings form
* '''Rescan:''' to read again the list of FLI CCD Camera connected to the PC
* '''RBI Preflood:''' to avoid ghost issue on the KAF CCD Sensor RBI can be use to remove and mitigate the effect. More info on website of vendor. This will add extra time to the shot
**'''Flood Time:''' time of exposure in milliseconds with flooding of sensor with IR internal leds
** '''Flushes:''' number of cleaning cicle after flooding (dark mode an background flush will used if avalaible from firmware)
** '''RBI Bin Factor:''' factor to use in binning for the flooding
** '''RBI Enabled:''' switch to off if you dont want to use the RBI at all and dont want to retrieve the Readout Mode dedicated to RBI (advice is to leave ON and just not use RBI mode in various shot configuration)
* '''Advanced:''' advanced features if avalaible
** '''Do One Cleaning Image After Raw Readoutmode Change:''' used to remove with/black block of data in the image after a readoutmode switch, this will ad extra time to the shot
* '''Camera Info:''' general info about the camera read directly from it
** '''Device Model:''' Name and Sigla of model
** '''Serial Number:''' serial number attribuited to camera from vendor
** '''Firmware Vesion:''' firmware version
** '''HW Revision:''' hardware version
** '''SDK Version:''' version of SDK DLL library used by Voyager to manage the Camera and the Filter Wheel
* '''Default:''' press this button to restore setting to the default
* '''Cancel:''' to exit form without saving changes
* '''OK:''' to save the changes to settings

The FLI Filter Wheel configuration form:

[[File:97831a541208ddbdcd01187517132e49bee4f8b0.png]]

* '''Filter Wheel Chooser:''' Choose the filter wheel from the drop-down list, the filter wheel must be connected to open the settings form
* '''Rescan:''' to read again the list of FLI filter wheel connected to the PC
* '''Cancel:''' to exit form without saving changes
*'''OK:''' to save the changes to settings

{{Note|If you use different camera control or software for your FLI data collect, please verify your previous calibration files work fine. We suggest to redo a set of calibration files dedicated in Voyager.}}

==QHY CMOS Native Driver==
If you choose QHY CMOS Camera or QHY CMOS Camera BETA from the Camera drop-down list, Voyager will connect directly to your QHY CMOS camera (not via ASCOM).

{{Note|Difference between the two QHY Native driver:

- QHY CMOS Camera (QHY SDK frozen for old CMOS cameras until 2020). Use with old CMOS camera.

- QHY CMOS Camera BETA [starting from Voyager Release 2.3.0] (for camera need SDK equal or greater than 2020, you can update manually this driver if needed) . Suggested for QHY600,294,268,533,461 and newest.}}

Click the Camera Advanced Config button to bring up the QHY CMOS Camera Setup dialog:

[[File:QHYCMOSSetupcmd.png]]

The QHY CMOS Camera Setup dialog is very similar to the QHY ASCOM dialog:

[[File:QHYSetupForm.png]] 
 {{Note|You set default values for Gain, Offset and USB Limit in this dialog. You can override these values when you define a Sequence or Research and Survey definition on a per-element (group of exposures for a given filter) basis}}

{{Note|If you using the direct driver in Voyager and your QHY filter wheel is setting up to use I2C you must use the dedicated Voyager driver for the filter wheel (Voyager to QHYCMOS filter wheel) because the direct driver isn't ASCOM and work on SDK so you cannot mix things with I2C that is managed from SDK.
 If you want to use the QHY filter wheel with USB please install and select the QHY ASCOM USB driver for serial. In case of use of I2C mode or USB mode.. be sure the hardware switch in the filter wheel is positioned in the right mode, you must look at flashing and color when you start the filter wheel (default mode usually is in I2C mode). Refer to the QHY documentations.}}

{{Note|Changing manually driver in the platform folder of Voyager is an operation to your entire risk and can introduce misconfiguration or issues. To go back simply reinstall Voyager. If you install a new version of Voyager or a Daily Build the SDK will be restored by installation in any case.}}

 

*'''Camera Chooser:''' Choose the camera from the drop-down list
*'''Bin Mode''': list of the allowed binning mode for the choosed camera (selection not made any change in camera settings)
*'''Preset:''' Choose a preset from the drop-down list and the preset's values will be applied to the settings for Gain, Offset and USB Limit
**Choose one of the User presets (User 1, User 2, etc.) to create a custom preset for Gain, Offset and USB Limit
**Click the '''Edit Name''' button to change the preset name from User X to a name of your choosing:
**[[File:Asi-preset-editname.jpg]]

*'''CMOS Reset Voyager Preset Setting:''' Click to reset any custom (User 1, User 2, etc) presets you created in this profile. This button appears in the top-level Camera Setup dialog if you choose QHYCMOS Camera

*[[File:Asi-reset-preset.jpg]]

*'''Gain, Offset and USB Limit Sliders:''' Click and drag these sliders with your mouse, or click on the slider and use the up and down or left and right arrows to change the values. If you change the values this way, the Preset drop-down list changes to Manal
**[[File:QHYGaincontrol.png]]
***
*'''Gain:''' Move the slider to set the gain value. See your camera's manual for an explanation of how your choice here affects your image
*'''Offset:''' Move the slider to set the offset value. See your camera's manual for an explanation of how your choice here affects your image
*'''USB Limit:''' Move the slider to set the USB limit value. This controls how fast the camera sends data to the USB port. If your download does not finish, try a higher setting. 0 value is the fastest possible.
*'''Remove Overscan Area:''' remove overscan area from data download where sensor allow this
*'''Disable 12bit ADC to enable guiding port''': Disable 12 bit ADC to enable guiding port where sensor allow this
*'''Row Noise Reduction:''' Row noise reduction where sensor allow this
*'''Speed:''' High speed or low speed in download where sensor allow this
*'''ReadMode:''' readoutmote dropdown list where to select the readout mode for the camera (cannot be changed if camera is connected). Special mode are available for QHY600 and similar cameras.
*'''Firmware Label:''' report the versione of the firmware inside the camera selected
*'''SDK Version Label:''' report the SDK version inside the Voyager Release / Daily Build you are using. You can update SDK copying the dll of a new SDK from QHY directly inside the Voyager installation directory. We suggest to you use the ones released with Voyager distributions
*'''Cancel:''' Discard changes and exit this dialog
*'''OK:''' Save changes and exit this dialog

 {{Note|The QHYCMOS Camera native driver is the only way to control the Gain and Offset values of a QHY CMOS camera from Voyager. You cannot control them from Voyager if you use the ASCOM driver to connect to your QHY CMOS camera}}

==Filters==

If your camera is connected via MaximDL or TheSkyX Camera Add On, filters must be configured in those applications and imported to Voyager using the GET button, as described below. When you choose Maxim DL or TheSkyX Camera Add On, no filter wheel selection will be presented because the filter wheel is not connected to Voyager, it is connected to Maxim DL or TheSkyX.

For ASCOM and QSI camera, you must configure a Filter Wheel from the Filter Wheel drop-down list:

[[File:Select-filter-wheel.jpg]]

For an ASCOM filter wheel, click the ASCOM button to display the ASCOM chooser and select the filter wheel for this configuration.

Once a Camera and optionally a filter wheel have been selected, next populate the Filters window with the list of available filters.

'''With Voyager disconnected to external devices''', click the GET button to retrieve a list of filters and label names from the filter device or third party application.

[[File:Filter-list.jpg]]

{{Note|For DSLR's and One Shot Color cameras (OSC), a filter named ** Bayer Matrix ** will be shown.}}{{Note|For monochrome cameras with no filter wheel, click the Clear button and the filter ** Clear ** will be created.}}

 

==Filter Setup==
Some filter wheel drivers or applications cannot return a list of filters. For those cases, click the EDIT button and manually enter the filter list:

[[File:Filter-setup-1.jpg]]

{{Note|If entering filters manually and using a third party application such as MaximDL or TheSkyX Camera Add-on, make sure the filter Name and Number match those defined in the third party software. It is preferable to use the GET button to ensure a match.}}{{Note|Max number of filters managed by Voyager is 12}}{{Note|Magnitude usable interval start from 0 to 7}} 
===RoboStar Configuration for Filters===
Set the minimum (Mag End) and maximum (Mag Start) stellar magnitudes for Voyager's RoboStar autofocus routine on a per-filter basis.

Click the "Set Broadband" or "Set NarrowBand" buttons to use the default magnitudes for these respective filter types.
 

===RoboStar LocalField Configuration for Filters===
Set the Exposure Time in seconds and Binning for the RoboStar LocalField (multiple-star) autofocus routine on a per-filter basis.

Check the box "Not Use LocalField in Sequence" if you do not want to use LocalField autofocus while a sequence is executing.

 

==Resolution Imager==
This is where the image scale of your telescope and camera is defined.
 {{Note|For correct operation of Voyager these settings are mandatory}}

[[File:Resolution-imager.jpg]]
 

*'''Telescope Focal Length''': The focal length of the primary telescope in millimeters (mm)
*'''Pixel Size''': The size of the main camera's pixels in microns

After entering these two values, Voyager will automatically calculate the image scale for binning 1x1. This value is computed in arc-seconds/pixel and appears in the Unbinned Image Scale field

*'''Camera P.A.''': The position angle of Camera updated to the last valid solving PA retrieved by Voyager during overall operations. This value will be passed to the Virtual Field of View facility in Web Dashboard to drawing your FOV over the Aladin map. The update of this value will be done at Voyager application closing.
*'''Camera Pixel''' : The size in pixel in horizontal and vertical of your camera in bin1.This value will be passed to the Virtual Field of View facility in Web Dashboard to drawing your FOV over the Aladin map. This is a readonly field. 
{{Note|Failure to define the image scale could lead to
malfunction of the Plate Solving system and the loss of image alignment}} {{Note|From Voyager 2.0.13a, Voyager will force Maxim DL to use the focal length set in Voyager}}
 
==Sensor Type==
[[File:Sensor-type.jpg]]

In this panel, select the type of camera sensor:

*'''Monochrome''': Mono cameras with or without a filter wheel
*'''Color''': Color cameras with a Bayer Matrix (OSC or One Shot Color cameras)
*'''DSLR''': Commercial cameras, modified or not

 {{Note|If you use a third party application such as MaximDL or TheSkyX to manage your camera, all cameras defined in that application can be managed in Voyager}}
 
{{Note|If you want to use a filter wheel with a color camera, please choose Monochrome like camera type. This will enable the filter wheel control where you can configure control and filters.}} 

==Cooling System==
If the camera has a cooling system (usually a Peltier cooler), Voyager can manage it using these settings:

[[File:Cooling-system.jpg]]

*'''On Connect Set Cooler''': When Voyager connects to the camera, turn the cooling system Off, On, or leave it unchanged. If you connect to your system a long time before use, you may want to leave this "Off" or "Unchanged" and then turn the cooler on using the sequence settings or a DragScript command. If you are planning to disconnect and reconnect Camera so many thank during setting up Voyager use the "Unchanged" to avoid camera cooling to be stressed.
*'''Timeout Settling Temp''': The time in minutes after which the cooling action is considered failed if the desired temperature is not reached
*'''Deviation Max under''': The absolute temperature difference in °C allowed from the desired temperature before the cooling action is considered successful. This temperature must be maintained for the amount of time indicated in the next field, "... for time span of"
*'''... for time span of''': The amount of time that the temperature must be within the "Deviation Max under" described above for a cooling action to be considered successful
*'''Default WarmUp Time''': The time in minutes after which the warmup action is considered failed if the desired temperature is not reached
*'''Default Temp. Cooling''': The desired temperature in °C for a cooling operation
*'''Default Cool Down time''': The desired time in minutes used to reach the desired cooled temperature, to avoid cooling too fast which in some cases can cause frost to form
*'''No CoolDown for Delta''': The maximum difference in °C below which the camera's native firmware cooling system is used instead of the Cool Down parameters specified here. In other words, if the camera's sensor is currently at -25 °C and you request a change to -30 °C, if the "No CoolDown for Delta" value is 10 °C, Voyager will just command the camera to cool to -30 °C without any management of cool down ramp time.
*'''Default Temp. WarmUp''': The desired temperature in °C for a WarmUp operation. Note that if this is set too high, the WarmUp operation may fail. However, in most cases this does not cause any problems.
*'''Temperature Control Allowed by Camera:''' remove flag if camera doesn't allow temperature control or not have it

These settings are used for all operations relating to setting the camera's sensor temperature. To find out how they work in detail read see the [[OnTheFly]] section.
 
{{Note|The fields "Default Cool Down Time," "Timeout Settling Temp" and "... for time span of" are closely
linked. The "Timeout Settling Temp." should be larger than the "Default Cool Down Time" plus the "...for the span of" time, or the cooling action would always result in a timeout error}}{{Note|You can use the cooling system's native firmware factory settings in the Cooling panel of the Sequence Configuration dialog}}

{{Note|The Sequence Configuration dialog's Cooling panel supports auto setpoint scaling. If the camera cannot reach the desired temperature within a defined time, it will try to reach a designated warmer temperature}} 
==Readout Mode==
Some cameras have settings to control readout speed vs. readout noise. The Readout Mode section of the Setup workspace lets you configure these settings:

[[File:Readout-mode.jpg]]
 

*'''GET''': Click this button to retrieve the list of available modes, if any. '''Voyager must be disconnected from the control systems for this to work'''
*'''Light/Dark/Bias''': Recommended setting is to have the highest quality - lowest noise, regardless of speed. But this is optional - you can choose any setting
*'''Focus''': Recommended setting is fastest speed, regardless of noise, so autofocus operations happen quickly
*'''Plate Solve''': Recommended setting is fastest speed that still results in successful plate solves. If you are not sure, set for highest quality.

 
==Speed==
Some cameras have settings to control gain in order to improve dynamic range. The Speed section of the Setup workspace lets you configure these settings in order to accelerate some Voyager features:

[[File:Camera-speed.jpg]]

*'''GET''': Click this button to retrieve the list of available modes, if any. '''Voyager must be disconnected from the control systems for this to work'''
*'''Binning 1x1''': Choose the gain to be used when taking exposures with binning 1x1
*'''Binning 2x2''': Choose the gain to be used when taking exposures with binning 2x2
*'''Other Binning''': Choose the gain to be used when taking exposures with binning other than 1x1 and 2x2

 

==TheSkyX Camera Add On Setting==
Settings for TheSkyX Camera Add On can be configured in this panel of the Camera setup workspace:

[[File:Theskyx-camera-settings.jpg]]
 

Due to a lack of commands in TheSkyX's DCOM interface (the interface used by external applications to manage TheSkyX operations), Voyager is unable to determine the current filter selected in the filter wheel. To ensure the correct filter is used, Voyager takes a very short "dummy exposure" and sets the filter to the desired value. The "dummy image" is not saved. The default values here should be good for most setups. The goal is to make this a very short exposure with a fast download, so if you know of better settings for your camera, you can set them here.

*'''Dummy Exposure Bin''': Binning level to be used when taking dummy exposures
*'''Dummy Exposure ROI''': Region Of Interest size to be used when taking dummy exposures
*'''Dummy Exposure Time:''' Exposure time to be used when taking dummy exposures

 
{{Note|Be sure your dummy exposure time is not under the minimum value accepted from the camera. This could be thrown an error in the camera driver}}
 

==Maxim DL==
Settings dedicated to Maxim DL Camera additional features:

[[File:Immaginefr3fwf.png]]

* '''Quit Camera Connection on Voyager Setup Disconnect:''' disconnect camera in Maxim DL when disconnect setup from Voyager

==Various==
Miscellaneous settings are contained in the Various panel of the Camera setup workspace:

[[File:Camera-various.jpg]]

*'''Download Save Timeout''': Time in seconds after which the download of an image from the camera times out (fails)
*'''ASCOM ImageReady Slow Polling''': Delay before polling the ASCOM driver to see if the image is ready to download. This is used if the camera's firmware is slow and needs some time between ImageReady queries (see [https://forum.starkeeper.it/t/camera-communication-speed-adjustment/276/4 discussion] in the Voyager forum)
*'''ASCOM Polling De-Throttle''': Controls the amount of delay between requests to the ASCOM camera driver to avoid overflowing a slow camera's command buffer.
*'''Use Canopus FIT fix''': [http://www.minorplanetobserver.com/MPOSoftware/MPOCanopus.htm MPO Canopus] is an astrometry and photometry application usually used in Astronomical Research . This flag fix a ''OBJCTDEC'' key in saved FIT Header adding a + for a positive value. Without this flag Canopus cannot handle correctly the FIT made by Voyager (or others FIT generator)
*'''Not Manage AIRMASS in FIT''': Voyager will not write AIRMASS calculated value in the FIT Header, if camera control in Voyager is an external application, this application will be delegated to write the AIRMASS header (like Maxim or TSX Camera add on)
*'''Additional Safe Time after Filter Wheel filter change:''' add an extra time wait of x seconds after the driver of the filter wheel report changing of filter is finished. This to avoid that filter wheel that report wheel have finished to move but is not true might affect the next image in shot
*'''Hide Personal Info in FITS Header''': remove personal data from FIT Headers (SITELAT, SITELONG, OWNER, SWOWNER, OBSERVER)
*'''Leave FILTER FIT Header content blank:''' regardless of the filter used to trigger the FIT, no text will be inserted in the headers for the FILTER header 

==FIT Headers Custom==
Various FIT Headers that can be written with the values in the settings:

[[File:Immaginevbdfvdf.png]]

* '''BAYERPAT''': bayern pattern of the color sensor
* '''XBAYROFF''': offset of the bayer pattern in X
* '''YBAYROFF''': offset of the bayer pattern in Y
* '''ROWORDER''': This keyword is <code>ROWORDER</code> of type <code>TSTRING</code>. It can take two values: <code>BOTTOM-UP</code> and <code>TOP-DOWN</code>.

==Other Setup Pages==
<categorytree mode="pages" depth="1">Setup</categorytree>

[[Category:Setup]]
[[Category:All]]
[[Category:Manual|Ha]]

File:235eegwegweg.png

2025-10-23T08:52:49Z

Leonardo:

erferferf

File:Immagine2dwfwef.png

2025-10-23T08:51:11Z

Leonardo: Leonardo uploaded a new version of File:Immagine2dwfwef.png

Immagine2dwfwef

Camera Setup

2025-10-23T08:48:41Z

Leonardo: /* Camera Choice */

==Camera Setup Workspace==
Click the Camera button in the Setup workspace to display the Camera setup window:

[[File:Camera-setup-217d.jpg]]
 {{Note|Camera selection must be filled out - this is mandatory for proper operation of Voyager}} 

==Color Coding==
Throughout the Setup workspace, Voyager uses color to indicate the following:

*'''Black''': A normal setting
*Gold or Yellow: Use caution when changing as things may not work well or as expected
*Red: Use extreme care when changing this setting - the wrong value can damage your equipment or the imaging session may fail

==Camera Choice==
Voyager supports the following ways to connect to a camera:

[[File:Setup-camera-216c.jpg]]

*ASCOM Camera
*ASI Camera (with ASI SDK frozen to 1.16.0 version)
*ASI Camera V2 [starting from Voyager Daily Build 2.2.16h] (for cameras need SDK equal or greater than 1.16.3 and/or using FPGA binning mode like ASI294MM Pro)
*CAM8S Camera
*CMOS ASCOM Camera V2 [starting from Voyager Daily Build 2.3.4j] (ONLY for CMOS cameras using '''ASCOM Camera Interface V2''' and having numeric '''Gain''' managed in driver - Like all MORAVIAN CMOS)
*CMOS ASCOM Camera V3 [starting from Voyager Daily Build 2.3.13] (ONLY for CMOS cameras using '''ASCOM Camera Interface V3''' and having numeric '''Gain''' and numeric '''Offset''' managed in driver - All CMOS camera support this version of ASCOM driver)
*FLI CCD Camera
*Maxim DL
*Player One Astronomy Camera
*QHY CMOS Camera
*QHY CMOS Camera BETA [starting from Voyager 2.3.0] (for using your QHY camera whit the last Beta SDK released from QHY, Beta version embedded in Voyager depend on relase or daily build creation)
*QSI Camera
*SX ASCOM Camera
*TheSkyX Camera Add On
*TheSky64 Camera Add On

Visit the [[Installation#Prerequisites|Installation Prerequisites]] section to see which versions of these third party applications are supported by Voyager.

Depending on the Camera selection, different configuration options are available, so make this selection first.

For ASCOM connected cameras, the Camera Advanced Config button brings up the ASCOM Properties dialog. The ASCOM button brings up the ASCOM chooser dialog - use this to select the specific ASCOM camera for this configuration.

== CMOS ASCOM Camera V2 ==
Choose CMOS ASCOM Camera V2 if you have a CMOS camera without native support in Voyager and you want to use the numeric Gain configurable in Sequence slots. The camera must have ASCOM driver implements ICamera V2 interface. You can ask to support if your camera are in the list of suitable for this kind of drivers. Usually all the cameras with ASCOM 5.x and newer.

The difference between normal ASCOM driver choice in Voyager is the possibility to use Gain in Sequence slots to define custom gain value for each shot.

The default Gain for plate solve and focus shot are defined in the Camera Setup tab:

[[File:Immagine2dwfwef.png]]

== CMOS ASCOM Camera V3 ==
Choose CMOS ASCOM Camera V3 if you have a CMOS camera without native support in Voyager and you want to use the numeric Gain and numeri Offset configurable in Sequence slots. The camera must have ASCOM driver implements ICamera V3 interface. You can ask to support if your camera are in the list of suitable for this kind of drivers. Usually all the cameras with ASCOM 6.5 and newer.

The difference between normal ASCOM driver choice in Voyager is the possibility to use Gain and Offset in Sequence slots to define custom gain value for each shot.

The default Gain for plate solve and focus shot are defined in the Camera Setup tab:

[[File:Immagine2dwfwef.png]]

==TheSkyX Camera Add On==
If you choose TheSkyX Camera Add On from the Camera drop-down list, Voyager will connect directly to TSX configured Camera and Filter Wheel. {{Note|Please remove the AutoSave flag in TheSkyX Camera Add On to prevents CFITSIO error during Voyager FIT data management. Voyager will save for you all the data needed.}}

==Info about Camera Driver / SDK / ASCOM Driver ==
Some clarification about level of drivers, especially for CMOS cameras:

* Camera Driver (low level file needed by Camera to work with your OS, usually contains also the firmware will be loaded on camera for some brand/models) this must be installed in anycase and usually are not included in SDK and ASCOM driver
* SDK (mid level file for allow application to talk with the camera driver, can be used to direct access to camera) this not include camera driver usually depends on camera brands
* ASCOM Driver (ASCOM platform file allow all application compatible with ASCOM to work with camera, use SDK to access to camera driver) not include camera driver but usually include SDK, location of the SDK usually is not the right one for the application use only SDK … this is the reason if you install newer ASCOM driver not mean automatically you will have your application with updated SDK.

SDK with direct access is the most performant usually especially for CMOS with big size sensor.

Voyager have direct driver using SDK for some CMOS / CCD cameras, brands usually have a Beta Release of driver for the new cameras or just released on market. So if you want to use beta driver and upate ones used in Voyager in the wiki is described how to do or in the page of each single brand. (basically download SDK file and copy on Voyager SDK Platform folder). See [https://wiki.starkeeper.it/index.php/Installation#SDK_Platform_Folder Voyager SDK Platform folder]. Some brand like ASI and QHY have double camera control in voyager to use stable or beta version of SDK.

In any case, we will not be responsible for any malfunctions or strange behaviors.

If you have problems with these drivers, first open a support ticket at your CMOS support service.

'''A last thing, like wrote in wiki, if you will update Voyager installation with a new daily build or release we will install back the choosed driver by Voyager.'''

==QSI Native Driver==
If you choose QSI Camera from the Camera drop-down list, Voyager will connect directly to your QSI camera using the COM object released with the their SDK (not via ASCOM).

Usually until 6.x version of the CD installation software of QSI this will be included in the main installation of CD, now ATIK (owner of QSI) seems to have removed it and trust only on ASCOM driver.

How to allow Voyager work with QSI SDK driver ?

'''You can use the legacy driver installation (instead of the last version):'''

https://qsimaging.com/drivers-software/#cd-and-drivers

''<code>"Our legacy installer includes our old ASCOM driver '''QSI Installer''' (.zip) 30.9MB v1.0.0.3"</code>''

'''You can download from here the SDK:'''

https://qsimaging.com/drivers-software/#custom

Open the QSI folder inside and install it like for instructions in the readme.txt:

''<code>"Installation of QSICamera.dll requires the use of regsvr32 to register the dll in the Windows Registry.</code>''

''<code>We recommend placing QSICamera.dll in C:\Windows\System32 and then calling regsvr32 from powershell run as an administrator.</code>''

''<code> PS C:\WINDOWS\system32> regsvr32 .\QSICamera.dll</code>''

''<code>Note: On a 64 bit machine</code>''

''<code> QSICamera.dll from the x64 folder should be placed in C:\Windows\System32</code>''

''<code> QSICamera.dll from the x32 folder should be placed in C:\Windows\SysWOW64</code>''

''<code>To unregister you will need to call regsvr32 with the /u argument.</code>''

''<code> PS C:\WINDOWS\system32> regsvr32 /u .\QSICamera.dll"</code>''

We do not put this on Voyager installation to avoid retro compatibility problem with camera having 5.x and 6.x version of firmware, we are not sure all working fine with the 7.x SDK.

'''If you have a 5.x or 6.x installation CD the SDK will be installed automatically with the main installation menù.'''

If you want direct support please contact us for remote checking.

==ASI Native Driver / ASI Native Driver V2==
If you choose ASI Camera or ASI Camera V2 from the Camera drop-down list, Voyager will connect directly to your ZWO ASI camera (not via ASCOM).

{{Note|Difference between the two ASI Native driver:

- ASI Camera (with ASI SDK frozen to 1.16.0 version)

- ASI Camera V2 [starting from Voyager Daily Build 2.2.16h] (for camera need SDK equal or greater than 1.16.3 and/or using FPGA binning mode like ASI294MM Pro)}}

Click the Camera Advanced Config button to bring up the ASI Camera Setup dialog:

[[File:Zwo-camera-advanced.jpg]]

The ASI Camera Setup dialog is very similar to the ZWO ASI ASCOM dialog:

[[File:Zwo-asi-native-driver.jpg]]

 {{Note|You set default values for Gain, Offset and USB Limit in this dialog. You can override these values when you define a Sequence or Research and Survey definition on a per-element (group of exposures for a given filter) basis}} 

*'''Connected Cameras:''' Choose the camera from the drop-down list
**'''Edit:''' Click the Edit button if you would like to use a different name for the camera selected from the drop-down list
**'''USB Type:''' Displays the type of USB connection, USB3 or USB2
**'''Bayer Pattern:''' Displays the Bayer Matrix pattern If the '''Connected Camera''' has a color sensor
**'''Temperature:''' Displays the sensor temperature returned by the camera
**'''MonoBin:''' If checked and If the connected camera has a color sensor, the pixels from the color sensor are binned by the camera and a monochrome image is returned
**

*'''Preset:''' Choose a preset from the drop-down list and the preset's values will be applied to the settings for Gain, Offset and USB Limit
**[[File:Asi-preset-custom.jpg]]
**Choose one of the User presets (User 1, User 2, etc.) to create a custom preset for Gain, Offset and USB Limit
**Click the '''Edit Name''' button to change the preset name from User X to a name of your choosing:
**[[File:Asi-preset-editname.jpg]]
*'''ASI Reset Voyager Preset Setting:''' Click to reset any custom (User 1, User 2, etc) presets you created in this profile. This button appears in the top-level Camera Setup dialog if you choose ASI Camera
**[[File:Asi-reset-preset.jpg]]
*'''Gain, Offset and USB Limit Sliders:''' Click and drag these sliders with your mouse, or click on the slider and use the up and down or left and right arrows to change the values. If you change the values this way, the Preset drop-down list changes to Manual
**[[File:Asi-gain-sliders.jpg]]
*'''Gain:''' Move the slider to set the gain value. See your camera's manual for an explanation of how your choice here affects your image
*'''Offset:''' Move the slider to set the offset value. See your camera's manual for an explanation of how your choice here affects your image
*'''USB Limit:''' Move the slider to set the USB limit value. This controls how fast the camera sends data to the USB port. If your download does not finish, try a lower setting.
*'''Remove Gain Limit Management:''' (Starting from Voyager 2.2.14b version) ASI Camera driver (like for ASI specific) limit the maximum gain for DSO use, calculus is automatically done. If you want to use gain up to raw max gain, check this flag and reopen the form. If you use high gain level for this cameras you can shrink in a bad way the full well capacity and increase drammatically the noise. '''Use at your risk !'''
*'''Cancel:''' Discard changes and exit this dialog
*'''OK:''' Save changes and exit this dialog 
{{Note|The ASI Camera native driver is the only way to control the Gain and Offset values of a ZWO ASI camera from Voyager. You cannot control them from Voyager if you use the ASCOM driver to connect to your ASI camera}}

==ASI Camera Name Match==
Tells Voyager to check the ASI Camera name on connection if you are using the ASI Camera (not ASCOM) driver.

[[File:Asi-camera-name-217d.jpg]]

*'''Raise Error On Camera Connect in Startup if Name Not Match:''' If checked and the ASI Camera camera type has been selected, Voyager will raise an error when connecting to the camera if the camera name specified in setup does not match the camera name returned by the driver.

 

==FLI CCD Native Driver==
If you choose FLI CCD Camera from the Camera drop-down list, Voyager will connect directly to your FLI CCD camera (not via ASCOM) and if you want directly also to your FLI Filter Wheel.

Click the Camera Advanced Config button to bring up the FLI CCD Camera Setup dialog:

[[File:FLICameraChoose.png]]

The FLI CCD Camera Setup dialog is this one:

[[File:FLISettingForm.png]]

* '''Camera Chooser:''' Choose the camera from the drop-down list, the camera must be connected to open the settings form
* '''Rescan:''' to read again the list of FLI CCD Camera connected to the PC
* '''RBI Preflood:''' to avoid ghost issue on the KAF CCD Sensor RBI can be use to remove and mitigate the effect. More info on website of vendor. This will add extra time to the shot
**'''Flood Time:''' time of exposure in milliseconds with flooding of sensor with IR internal leds
** '''Flushes:''' number of cleaning cicle after flooding (dark mode an background flush will used if avalaible from firmware)
** '''RBI Bin Factor:''' factor to use in binning for the flooding
** '''RBI Enabled:''' switch to off if you dont want to use the RBI at all and dont want to retrieve the Readout Mode dedicated to RBI (advice is to leave ON and just not use RBI mode in various shot configuration)
* '''Advanced:''' advanced features if avalaible
** '''Do One Cleaning Image After Raw Readoutmode Change:''' used to remove with/black block of data in the image after a readoutmode switch, this will ad extra time to the shot
* '''Camera Info:''' general info about the camera read directly from it
** '''Device Model:''' Name and Sigla of model
** '''Serial Number:''' serial number attribuited to camera from vendor
** '''Firmware Vesion:''' firmware version
** '''HW Revision:''' hardware version
** '''SDK Version:''' version of SDK DLL library used by Voyager to manage the Camera and the Filter Wheel
* '''Default:''' press this button to restore setting to the default
* '''Cancel:''' to exit form without saving changes
* '''OK:''' to save the changes to settings

The FLI Filter Wheel configuration form:

[[File:97831a541208ddbdcd01187517132e49bee4f8b0.png]]

* '''Filter Wheel Chooser:''' Choose the filter wheel from the drop-down list, the filter wheel must be connected to open the settings form
* '''Rescan:''' to read again the list of FLI filter wheel connected to the PC
* '''Cancel:''' to exit form without saving changes
*'''OK:''' to save the changes to settings

{{Note|If you use different camera control or software for your FLI data collect, please verify your previous calibration files work fine. We suggest to redo a set of calibration files dedicated in Voyager.}}

==QHY CMOS Native Driver==
If you choose QHY CMOS Camera or QHY CMOS Camera BETA from the Camera drop-down list, Voyager will connect directly to your QHY CMOS camera (not via ASCOM).

{{Note|Difference between the two QHY Native driver:

- QHY CMOS Camera (QHY SDK frozen for old CMOS cameras until 2020). Use with old CMOS camera.

- QHY CMOS Camera BETA [starting from Voyager Release 2.3.0] (for camera need SDK equal or greater than 2020, you can update manually this driver if needed) . Suggested for QHY600,294,268,533,461 and newest.}}

Click the Camera Advanced Config button to bring up the QHY CMOS Camera Setup dialog:

[[File:QHYCMOSSetupcmd.png]]

The QHY CMOS Camera Setup dialog is very similar to the QHY ASCOM dialog:

[[File:QHYSetupForm.png]] 
 {{Note|You set default values for Gain, Offset and USB Limit in this dialog. You can override these values when you define a Sequence or Research and Survey definition on a per-element (group of exposures for a given filter) basis}}

{{Note|If you using the direct driver in Voyager and your QHY filter wheel is setting up to use I2C you must use the dedicated Voyager driver for the filter wheel (Voyager to QHYCMOS filter wheel) because the direct driver isn't ASCOM and work on SDK so you cannot mix things with I2C that is managed from SDK.
 If you want to use the QHY filter wheel with USB please install and select the QHY ASCOM USB driver for serial. In case of use of I2C mode or USB mode.. be sure the hardware switch in the filter wheel is positioned in the right mode, you must look at flashing and color when you start the filter wheel (default mode usually is in I2C mode). Refer to the QHY documentations.}}

{{Note|Changing manually driver in the platform folder of Voyager is an operation to your entire risk and can introduce misconfiguration or issues. To go back simply reinstall Voyager. If you install a new version of Voyager or a Daily Build the SDK will be restored by installation in any case.}}

 

*'''Camera Chooser:''' Choose the camera from the drop-down list
*'''Bin Mode''': list of the allowed binning mode for the choosed camera (selection not made any change in camera settings)
*'''Preset:''' Choose a preset from the drop-down list and the preset's values will be applied to the settings for Gain, Offset and USB Limit
**Choose one of the User presets (User 1, User 2, etc.) to create a custom preset for Gain, Offset and USB Limit
**Click the '''Edit Name''' button to change the preset name from User X to a name of your choosing:
**[[File:Asi-preset-editname.jpg]]

*'''CMOS Reset Voyager Preset Setting:''' Click to reset any custom (User 1, User 2, etc) presets you created in this profile. This button appears in the top-level Camera Setup dialog if you choose QHYCMOS Camera

*[[File:Asi-reset-preset.jpg]]

*'''Gain, Offset and USB Limit Sliders:''' Click and drag these sliders with your mouse, or click on the slider and use the up and down or left and right arrows to change the values. If you change the values this way, the Preset drop-down list changes to Manal
**[[File:QHYGaincontrol.png]]
***
*'''Gain:''' Move the slider to set the gain value. See your camera's manual for an explanation of how your choice here affects your image
*'''Offset:''' Move the slider to set the offset value. See your camera's manual for an explanation of how your choice here affects your image
*'''USB Limit:''' Move the slider to set the USB limit value. This controls how fast the camera sends data to the USB port. If your download does not finish, try a higher setting. 0 value is the fastest possible.
*'''Remove Overscan Area:''' remove overscan area from data download where sensor allow this
*'''Disable 12bit ADC to enable guiding port''': Disable 12 bit ADC to enable guiding port where sensor allow this
*'''Row Noise Reduction:''' Row noise reduction where sensor allow this
*'''Speed:''' High speed or low speed in download where sensor allow this
*'''ReadMode:''' readoutmote dropdown list where to select the readout mode for the camera (cannot be changed if camera is connected). Special mode are available for QHY600 and similar cameras.
*'''Firmware Label:''' report the versione of the firmware inside the camera selected
*'''SDK Version Label:''' report the SDK version inside the Voyager Release / Daily Build you are using. You can update SDK copying the dll of a new SDK from QHY directly inside the Voyager installation directory. We suggest to you use the ones released with Voyager distributions
*'''Cancel:''' Discard changes and exit this dialog
*'''OK:''' Save changes and exit this dialog

 {{Note|The QHYCMOS Camera native driver is the only way to control the Gain and Offset values of a QHY CMOS camera from Voyager. You cannot control them from Voyager if you use the ASCOM driver to connect to your QHY CMOS camera}}

==Filters==

If your camera is connected via MaximDL or TheSkyX Camera Add On, filters must be configured in those applications and imported to Voyager using the GET button, as described below. When you choose Maxim DL or TheSkyX Camera Add On, no filter wheel selection will be presented because the filter wheel is not connected to Voyager, it is connected to Maxim DL or TheSkyX.

For ASCOM and QSI camera, you must configure a Filter Wheel from the Filter Wheel drop-down list:

[[File:Select-filter-wheel.jpg]]

For an ASCOM filter wheel, click the ASCOM button to display the ASCOM chooser and select the filter wheel for this configuration.

Once a Camera and optionally a filter wheel have been selected, next populate the Filters window with the list of available filters.

'''With Voyager disconnected to external devices''', click the GET button to retrieve a list of filters and label names from the filter device or third party application.

[[File:Filter-list.jpg]]

{{Note|For DSLR's and One Shot Color cameras (OSC), a filter named ** Bayer Matrix ** will be shown.}}{{Note|For monochrome cameras with no filter wheel, click the Clear button and the filter ** Clear ** will be created.}}

 

==Filter Setup==
Some filter wheel drivers or applications cannot return a list of filters. For those cases, click the EDIT button and manually enter the filter list:

[[File:Filter-setup-1.jpg]]

{{Note|If entering filters manually and using a third party application such as MaximDL or TheSkyX Camera Add-on, make sure the filter Name and Number match those defined in the third party software. It is preferable to use the GET button to ensure a match.}}{{Note|Max number of filters managed by Voyager is 12}}{{Note|Magnitude usable interval start from 0 to 7}} 
===RoboStar Configuration for Filters===
Set the minimum (Mag End) and maximum (Mag Start) stellar magnitudes for Voyager's RoboStar autofocus routine on a per-filter basis.

Click the "Set Broadband" or "Set NarrowBand" buttons to use the default magnitudes for these respective filter types.
 

===RoboStar LocalField Configuration for Filters===
Set the Exposure Time in seconds and Binning for the RoboStar LocalField (multiple-star) autofocus routine on a per-filter basis.

Check the box "Not Use LocalField in Sequence" if you do not want to use LocalField autofocus while a sequence is executing.

 

==Resolution Imager==
This is where the image scale of your telescope and camera is defined.
 {{Note|For correct operation of Voyager these settings are mandatory}}

[[File:Resolution-imager.jpg]]
 

*'''Telescope Focal Length''': The focal length of the primary telescope in millimeters (mm)
*'''Pixel Size''': The size of the main camera's pixels in microns

After entering these two values, Voyager will automatically calculate the image scale for binning 1x1. This value is computed in arc-seconds/pixel and appears in the Unbinned Image Scale field

*'''Camera P.A.''': The position angle of Camera updated to the last valid solving PA retrieved by Voyager during overall operations. This value will be passed to the Virtual Field of View facility in Web Dashboard to drawing your FOV over the Aladin map. The update of this value will be done at Voyager application closing.
*'''Camera Pixel''' : The size in pixel in horizontal and vertical of your camera in bin1.This value will be passed to the Virtual Field of View facility in Web Dashboard to drawing your FOV over the Aladin map. This is a readonly field. 
{{Note|Failure to define the image scale could lead to
malfunction of the Plate Solving system and the loss of image alignment}} {{Note|From Voyager 2.0.13a, Voyager will force Maxim DL to use the focal length set in Voyager}}
 
==Sensor Type==
[[File:Sensor-type.jpg]]

In this panel, select the type of camera sensor:

*'''Monochrome''': Mono cameras with or without a filter wheel
*'''Color''': Color cameras with a Bayer Matrix (OSC or One Shot Color cameras)
*'''DSLR''': Commercial cameras, modified or not

 {{Note|If you use a third party application such as MaximDL or TheSkyX to manage your camera, all cameras defined in that application can be managed in Voyager}}
 
{{Note|If you want to use a filter wheel with a color camera, please choose Monochrome like camera type. This will enable the filter wheel control where you can configure control and filters.}} 

==Cooling System==
If the camera has a cooling system (usually a Peltier cooler), Voyager can manage it using these settings:

[[File:Cooling-system.jpg]]

*'''On Connect Set Cooler''': When Voyager connects to the camera, turn the cooling system Off, On, or leave it unchanged. If you connect to your system a long time before use, you may want to leave this "Off" or "Unchanged" and then turn the cooler on using the sequence settings or a DragScript command. If you are planning to disconnect and reconnect Camera so many thank during setting up Voyager use the "Unchanged" to avoid camera cooling to be stressed.
*'''Timeout Settling Temp''': The time in minutes after which the cooling action is considered failed if the desired temperature is not reached
*'''Deviation Max under''': The absolute temperature difference in °C allowed from the desired temperature before the cooling action is considered successful. This temperature must be maintained for the amount of time indicated in the next field, "... for time span of"
*'''... for time span of''': The amount of time that the temperature must be within the "Deviation Max under" described above for a cooling action to be considered successful
*'''Default WarmUp Time''': The time in minutes after which the warmup action is considered failed if the desired temperature is not reached
*'''Default Temp. Cooling''': The desired temperature in °C for a cooling operation
*'''Default Cool Down time''': The desired time in minutes used to reach the desired cooled temperature, to avoid cooling too fast which in some cases can cause frost to form
*'''No CoolDown for Delta''': The maximum difference in °C below which the camera's native firmware cooling system is used instead of the Cool Down parameters specified here. In other words, if the camera's sensor is currently at -25 °C and you request a change to -30 °C, if the "No CoolDown for Delta" value is 10 °C, Voyager will just command the camera to cool to -30 °C without any management of cool down ramp time.
*'''Default Temp. WarmUp''': The desired temperature in °C for a WarmUp operation. Note that if this is set too high, the WarmUp operation may fail. However, in most cases this does not cause any problems.
*'''Temperature Control Allowed by Camera:''' remove flag if camera doesn't allow temperature control or not have it

These settings are used for all operations relating to setting the camera's sensor temperature. To find out how they work in detail read see the [[OnTheFly]] section.
 
{{Note|The fields "Default Cool Down Time," "Timeout Settling Temp" and "... for time span of" are closely
linked. The "Timeout Settling Temp." should be larger than the "Default Cool Down Time" plus the "...for the span of" time, or the cooling action would always result in a timeout error}}{{Note|You can use the cooling system's native firmware factory settings in the Cooling panel of the Sequence Configuration dialog}}

{{Note|The Sequence Configuration dialog's Cooling panel supports auto setpoint scaling. If the camera cannot reach the desired temperature within a defined time, it will try to reach a designated warmer temperature}} 
==Readout Mode==
Some cameras have settings to control readout speed vs. readout noise. The Readout Mode section of the Setup workspace lets you configure these settings:

[[File:Readout-mode.jpg]]
 

*'''GET''': Click this button to retrieve the list of available modes, if any. '''Voyager must be disconnected from the control systems for this to work'''
*'''Light/Dark/Bias''': Recommended setting is to have the highest quality - lowest noise, regardless of speed. But this is optional - you can choose any setting
*'''Focus''': Recommended setting is fastest speed, regardless of noise, so autofocus operations happen quickly
*'''Plate Solve''': Recommended setting is fastest speed that still results in successful plate solves. If you are not sure, set for highest quality.

 
==Speed==
Some cameras have settings to control gain in order to improve dynamic range. The Speed section of the Setup workspace lets you configure these settings in order to accelerate some Voyager features:

[[File:Camera-speed.jpg]]

*'''GET''': Click this button to retrieve the list of available modes, if any. '''Voyager must be disconnected from the control systems for this to work'''
*'''Binning 1x1''': Choose the gain to be used when taking exposures with binning 1x1
*'''Binning 2x2''': Choose the gain to be used when taking exposures with binning 2x2
*'''Other Binning''': Choose the gain to be used when taking exposures with binning other than 1x1 and 2x2

 

==TheSkyX Camera Add On Setting==
Settings for TheSkyX Camera Add On can be configured in this panel of the Camera setup workspace:

[[File:Theskyx-camera-settings.jpg]]
 

Due to a lack of commands in TheSkyX's DCOM interface (the interface used by external applications to manage TheSkyX operations), Voyager is unable to determine the current filter selected in the filter wheel. To ensure the correct filter is used, Voyager takes a very short "dummy exposure" and sets the filter to the desired value. The "dummy image" is not saved. The default values here should be good for most setups. The goal is to make this a very short exposure with a fast download, so if you know of better settings for your camera, you can set them here.

*'''Dummy Exposure Bin''': Binning level to be used when taking dummy exposures
*'''Dummy Exposure ROI''': Region Of Interest size to be used when taking dummy exposures
*'''Dummy Exposure Time:''' Exposure time to be used when taking dummy exposures

 
{{Note|Be sure your dummy exposure time is not under the minimum value accepted from the camera. This could be thrown an error in the camera driver}}
 

==Maxim DL==
Settings dedicated to Maxim DL Camera additional features:

[[File:Immaginefr3fwf.png]]

* '''Quit Camera Connection on Voyager Setup Disconnect:''' disconnect camera in Maxim DL when disconnect setup from Voyager

==Various==
Miscellaneous settings are contained in the Various panel of the Camera setup workspace:

[[File:Camera-various.jpg]]

*'''Download Save Timeout''': Time in seconds after which the download of an image from the camera times out (fails)
*'''ASCOM ImageReady Slow Polling''': Delay before polling the ASCOM driver to see if the image is ready to download. This is used if the camera's firmware is slow and needs some time between ImageReady queries (see [https://forum.starkeeper.it/t/camera-communication-speed-adjustment/276/4 discussion] in the Voyager forum)
*'''ASCOM Polling De-Throttle''': Controls the amount of delay between requests to the ASCOM camera driver to avoid overflowing a slow camera's command buffer.
*'''Use Canopus FIT fix''': [http://www.minorplanetobserver.com/MPOSoftware/MPOCanopus.htm MPO Canopus] is an astrometry and photometry application usually used in Astronomical Research . This flag fix a ''OBJCTDEC'' key in saved FIT Header adding a + for a positive value. Without this flag Canopus cannot handle correctly the FIT made by Voyager (or others FIT generator)
*'''Not Manage AIRMASS in FIT''': Voyager will not write AIRMASS calculated value in the FIT Header, if camera control in Voyager is an external application, this application will be delegated to write the AIRMASS header (like Maxim or TSX Camera add on)
*'''Additional Safe Time after Filter Wheel filter change:''' add an extra time wait of x seconds after the driver of the filter wheel report changing of filter is finished. This to avoid that filter wheel that report wheel have finished to move but is not true might affect the next image in shot
*'''Hide Personal Info in FITS Header''': remove personal data from FIT Headers (SITELAT, SITELONG, OWNER, SWOWNER, OBSERVER)
*'''Leave FILTER FIT Header content blank:''' regardless of the filter used to trigger the FIT, no text will be inserted in the headers for the FILTER header 

==FIT Headers Custom==
Various FIT Headers that can be written with the values in the settings:

[[File:Immaginevbdfvdf.png]]

* '''BAYERPAT''': bayern pattern of the color sensor
* '''XBAYROFF''': offset of the bayer pattern in X
* '''YBAYROFF''': offset of the bayer pattern in Y
* '''ROWORDER''': This keyword is <code>ROWORDER</code> of type <code>TSTRING</code>. It can take two values: <code>BOTTOM-UP</code> and <code>TOP-DOWN</code>.

==Other Setup Pages==
<categorytree mode="pages" depth="1">Setup</categorytree>

[[Category:Setup]]
[[Category:All]]
[[Category:Manual|Ha]]

File:Setup-camera-216c.jpg

2025-10-23T08:44:04Z

Leonardo: Leonardo uploaded a new version of File:Setup-camera-216c.jpg

== Summary ==
importing from old wiki

File:Camera-setup-217d.jpg

2025-10-23T08:40:28Z

Leonardo: Leonardo uploaded a new version of File:Camera-setup-217d.jpg

== Summary ==
importing from old wiki

Auto Flat

2025-10-23T08:34:27Z

Leonardo: /* Auto Flat Options and Operations */

==Auto Flat Configuration==
The Auto Flat configuration window of the [[OnTheFly]] workspace is where you configure sequences to take flat images.

[[File:Session-onthefly.jpg]]

To bring up the Auto Flat configuration window, click the gear icon next to the Auto Flat button in the Session panel of the OnTheFly workspace.

Voyager will automatically scale your exposure time to reach your Target ADU within the Max Err%, between the Min Exp. and Max Exp. times you specify.

Voyager will take multiple flats ("Repeat" number of flats) with each filter.

Once configured, you can run the Auto Flat sequence by clicking the Auto Flat button with the green triangle, or by calling the Flat operation in a [[DragScript]].

As of Voyager 2.0.14e (daily build) or 2.1.0 (stable), you can choose the profile assigned to an Auto Flat sequence and edit sequences defined with profiles other than the currently active one. Values such as the filters, camera speed and readout mode are derived from the profile. Also, as of these Voyager releases, you no longer need to be connected to your equipment to create or edit an Auto Flat sequence. You only need to have a profile loaded, or choose one with the Change Profile to This Sequence button. You can also edit your Auto Flat sequences while actions are running.

{{Note|If Voyager can't find an acceptable exposure length for your Auto Flats, increase the ROI and/or increase the error tolerance. The ADU of a small ROI can vary quite a lot with a sensor with many pixels.}}

By default, the profile currently loaded and active in Voyager is used.

[[File:Autoflat-sequence-216d.jpg]]
 

*[[File:Change-profile-sequence.png]] '''Change Profile to This Sequence''': Brings up a dialog window from which you can change the profile assigned to this sequence. See [[Sequence Configuration#Change%20Sequence%20Profile|Change Sequence Profile]] section below for discussion of the migration process
*[[File:Reset-sequence-data.png|link=https://voyager.tourstar.net/File:Reset-sequence-data.png]] '''Reset Sequence Data''': Caution! Clicking this button resets all information in the Auto Flat sequence. If you have not saved it, your Auto Flat sequence data will be lost and you will have to start over
*[[File:Load-file.png|link=https://voyager.tourstar.net/File:Load-file.png]] '''Open Sequence File''': Click this file to load the data from a saved Auto Flat sequence file into the Auto Flat configuration window
*[[File:Save-file.png|link=https://voyager.tourstar.net/File:Save-file.png]] '''Save Sequence File''': Click this file to save the data from the Auto Flat Configuration window to the file of your choice
*[[File:Cancel-config.png|link=https://voyager.tourstar.net/File:Cancel-config.png]] '''Cancel Changes and Close Window''': Click this button to close the Auto Flat Configuration window and discard any changes made since it was opened
*
*'''OK''': Click the OK button to save your changes and close the Auto Flat Configuration window

==Flat Elements==
The Flat Elements panel of the Auto Flat configuration window is where you specify the filters, exposure goals in ADU, and number of flat images to take for each filter:

[[File:Autoflat-elements-216d.jpg]]

In this example, 10 flats will be taken for filters L, R, G and B, with Voyager adjusting exposure times to reach a target ADU (average brightness) of 32768, plus or minus 5%.

*'''Slot''': Click the number to "activate" the slot. A gray number means the slot will not be run. A green number means the slot will run.
*'''Filter''': Choose the filter to use for this slot from the drop-down list
*'''Suffix''': Optionally enter a character string to include in the flat file name. In this example, the filter name is specified and will be included in each flat file name.
*'''Min Exp'''.: Minimum exposure length in seconds
*'''Max Exp'''.: Maximum exposure length in seconds
*'''Init Exp'''.: Initial exposure length in seconds. Voyager will try to achieve the Target ADU, within the Max Err percentage, by varying the exposure time, starting with this value, but staying between the Min Exp. and Max Exp.
*'''Init Bright''': Initial panel brightness setting for your flat device
*'''Target ADU''': Desired ADU value for your flat file - a measure of brightness. Generally around half your sensor's maximum ADU is considered a reasonable value here
*'''Max Err%''': Maximum deviation percentage from the Target ADU, plus or minus, for a successful flat exposure to be taken
*'''Calc. ROI''': Choose a Region of Interest (ROI) from the drop-down list or use the default. If "No" is chosen, use the entire frame to calculate ADU (this slows down finding the proper exposure time) . If a number is chosen, calculate the frame's ADU mean value by looking at this Region Of Interest. The larger your sensor or the more light curvature in your optics, the larger your ROI must be to avoid larger fluctuations in the calculated exposure times
*'''Bin''': Binning level to use for this flat exposure. Should match the binning used for your light frames
*'''Speed''': Choose from the drop-down list. Allowed values are Auto Profile and ISO numbers. Auto Profile uses the [[Camera Setup#Speed|speed set in Camera Setup]] for the flat frame exposures
*'''Readout Mode''': Choose from the drop-down list. A list will be shown if your CCD driver allows Voyager to retrieve this information from your camera
*'''Gain:''' If you are using the [[Camera Setup#ASI%20Native%20Driver|ASI Camera native driver]] supplied by Voyager ('''not''' the ASI ASCOM driver), you can enter the Gain for this sequence element. This will be grayed out if you are not using Voyager's ASI Camera native driver.
*'''Offset:''' If you are using the [[Camera Setup#ASI%20Native%20Driver|ASI Camera native driver]] supplied by Voyager ('''not''' the ASI ASCOM driver), you can enter the Offset for this sequence element. This will be grayed out if you are not using Voyager's ASI Camera native driver.
*{{Note|If you are using a sequence with the ASI Camera native driver that was first defined with a different camera, all Gain and Offset values will be initially set to 0/0. Make sure you change these to the desired settings and save the sequence before running.}}
* Click the magnifying glass icon to select the Gain and Offset from the presets defined in the [[Camera Setup#ASI%20Native%20Driver|ASI Camera native driver setup]]. 
*'''Repeat''': The number of flat frames to take
*[[File:Sequence-elements-move.png|link=https://voyager.tourstar.net/File:Sequence-elements-move.png]]: Up arrow moves this row up one position; Down arrow moves this row down one position; X clears the information from this row
*The scroll bars on the right can be used to scroll the window up and down if you have more rows than show in the main window

 

==Auto Flat Options and Operations==
The lower portion of the Auto Flat configuration window contains other options for the flat sequence. Depending on the Flat Type you select, the options will change slightly.

Here is the way the options look if you choose either '''Flat Device''' or '''Manual Panel''':

[[File:Autoflat-options-211e.jpg]]

*'''Flat Base Name''': This text will be used as the first part of the flat file names. It will be appended with the Filter name, flat number and timestamp
*'''Flat Base''' '''Directory''': Folder for saving your flat files. Enter the directory name, or click the Select button to browse to it
*'''Flat Sub Foldering / File Naming:''' selection of the sub foldering and file naming method
**'''Use FILE PATTERN:''' flag this checkbox to activate sub foldering and file naming with File Pattern method (please configure the file pattern in the File Pattern Manager)
**'''Override FILE PATTERN:''' flag this chheckbox to activate sub foldering and file naming with File Pattern method, insert in the big text field near the flag the string to override of the file pattern to use instead of the one configured in the File Pattern Manager. This will affect only the actual sequence and do not change the main File Patterm Manager configuration. This is for example mandatory in case of join of the OpenSkyGems network and sharing of the observatory setup.
**'''User Voyager STANDARD:''' flag this checkbox (this choice is the default for a new sequence) to use the original sub foldering and file naming system adopted by Voyager from the beginning
***'''Create Logical Data Subfolder Inside Flat Base Directory''': If checked, Voyager will automatically create a subfolder based on the date inside the specified Flat Base Directory. Flats taken between midnight and 8AM local time will be stored in the same directory as yesterday's subfolder. If you are taking both dusk and dawn flats, all flats will be in the same subfolder.
*'''Flat Type''': Choose the type of flat from the drop-down list
**'''Manual Panel''': A light panel that is not controllable by Voyager. It is either fixed on the wall and you point your scope at it by using the Move telescope to this ALT/AZ Coordinates field, or is placed on top of the scope before you run your flats
**'''Flat Device''': A light source configured in [[Flat Device Setup]]. If you choose Flat Device as your Flat Type, a drop-down list appears from which you can select Flat Device #1 or Flat Device #2. Choose the Flat Device you want to use for this Auto Flat sequence. See [[Flat Device Setup]] for more info on configuring one or two Flat Devices.

[[File:Flat-device-2.11e.jpg]]

**'''Sky Dawn''': Take flat frames using the morning sky at dawn. See the [[Auto Flat#Sky Flats|Sky Flats]] section below
**'''Sky Dusk''': Take flat frames using the evening sky at dusk. See the [[Auto Flat#Sky Flats|Sky Flats]] section below
*'''Move telescope on START''': Specify how Voyager should treat the mount at the start of the auto flat sequence
**'''Don't Care:''' Don't change anything, if the mount was parked, it stays parked. If it was tracking, it will continue tracking. If not tracking, it stays not tracking
**'''Park on Start''': Park the mount at the start of the auto flat sequence
**'''Move to Alt/Az Coordinates:''' Slew the mount to the specified Altitude and Azimuth coordinates at the start of the auto flat sequence. One reason to use this is to point the scope to a fixed light source, normally a flat panel attached to the observatory wall
**'''AutoSlew for Sky Flat''': If you choose Dawn or Dusk sky flats as your Flat Type, the option to Autoslew for SkyFlat will appear. This is the default choice - and the recommended choice - for sky flats. Voyager will slew to the most appropriate spot in the sky to take your sky flats
*'''Mount Settling:''' manage the mount settling time after a movement
**'''Do Not Use:''' time settling configured for mount in general mount settings tabs of Voyager will be not used
**'''Use Default Time:''' time settling configured for mount in general mount settings tabs of Voyager will be used before proceede with auto flat
*'''Move telescope During FLAT:''' Choose how Voyager should move the mount - or not - during the auto flat sequence
**'''Don't Care''': Don't change anything, if the mount was parked, it stays parked. If it was tracking, it will continue tracking. If not tracking, it stays not tracking
**'''Stop Tracking:''' Stop the mount from tracking at the start of the auto flat sequence
**'''Dithering:''' If you choose Dawn or Dusk sky flats as your Flat Type, the option for Dithering will appear. If selected, Voyager will dither the scope while taking sky flats. If any stars are out while you are taking flats, dithering will help your processing software to remove the stars when stacking your flat frames
*'''Move Telescope On END''': Specify how Voyager should treat the mount at the end of the auto flat sequence
**'''Don't Care''': Don't change anything, if the mount was parked, it stays parked. If it was tracking, it will continue tracking. If not tracking, it stays not tracking
**'''Park on END''': Park the mount at the end of the auto flat sequence
*'''Run this Program/Script On START:''' Click the box with "..." to bring up the [[OnTheFly#Utilities|Run External Program / Script]] window to browse to a program or script to run at the start of the Auto Flat sequence. Click the X box to clear the field so no program or script is run. One example of how this field may be used is to run an external program that turns on your flat panel if it cannot be configured as a Flat Device.
*'''Stop Tracking During Flat''': If checked, command the mount to stop tracking while taking flats
*'''Exposure Error Action''': If checked, retry the specified number of times in case of an error
*'''Park On''' '''END''': Park the mount at the end of the Auto Flat sequence
*'''Run This Program/Script on END''': Click the box with "..." to bring up the [[OnTheFly#Utilities|Run External Program / Script]] window to browse to a program or script to run at the end of the Auto Flat sequence. Click the X box to clear the field so no program or script is run. One example of how this field may be used is to run an external program that turns off your flat panel if it cannot be configured as a Flat Device.
*'''Use SubFrame''': If checked, use a centered subframe of the size selected from the drop-down list: Full Frame, 1/2 size, 1/4 size, 1/8 size, 1/16 size or CUSTOM size.
**'''CUSTOM Size''': If you choose custom size from the drop-down, a counter appears from which you can choose any percentage value for your subframe size
*'''Rotator Manage:''' if checked Voyager will manage the rotator at beginning of action, rotating it to the PA choosen
**'''PA:''' PA to use for Rotator during Auto Flat action execution. No Plate solving and adjust or sync. Just simple rotation to the PA

 
==Fixed Length Flats - Dark Flat Matching==
If you would prefer to take fixed exposure length flats, e.g. if you are using a CMOS camera and calibrate your flats with matching length flat darks, you can do this with Auto Flat by:

*Determine the exposure length for your flats
*Set the Min Exp = Max Exp = Init Exp = desired exposure length
*Set the Max Err% to 100
*Set Target ADU to half your camera's max ADU, e.g. 32767 if your max ADU is 65535 (16 bit)

Set everything else as you would for variable length flats, and run the Auto Flat sequence.

And if you have a software adjustable brightness light panel you can set the flat duration and Voyager will adjust the brightness of the panel until you get the right flat. Very useful to be able to match duration of flat darks to the flats. 

For taking autoscaled dark library based on time you can also use the DagScript you will found here:

https://forum.starkeeper.it/t/collect-calibration-fits-in-one-session/2666/1

==Sky Flats==
As of Voyager 2.1.1a, sky flats are supported. Sky flats are taken at dusk and/or at dawn, pointing the telescope at about 75 degrees elevation and azimuth roughly opposite the sun.

Choose the type of flats, Sky Dawn or Sky Dusk, from the Flat Type drop-down box:

[[File:Choose-flat-type.jpg]]

You can configure the solar elevation at which dawn and dusk commence in the [[Flat Device Setup#Sky Flat|SkyFlat section of Flat Device Setup]]. The defaults should work well.

For dawn flats, the sky is getting brighter as time goes on, so you need to shoot your flats using your filters in order of decreasing transparency to sky light. You are taking pictures of a blue sky, so a likely order is L - B - G - R and if you have narrowband, O - H - S.

For dusk flats, the sky is getting darker as time goes on, so you need to shoot your flats using your filters in order of increasing transparency to sky light. The likely order is the opposite of dawn - first narrowband if you need those flats, S - H - O, then broadband R - G - B - L.

Your combination of telescope, camera and perhaps filters will determine the appropriate settings for minimum, maximum and initial exposure, as well as Target ADU, Maximum Error% and ROI (Region of Interest).

See the [[Auto Flat#Flat Elements|Auto Flat Elements]] section above for definition of these settings.

You need to experiment to determine what works best for your setup, but some considerations:

*The sky's brightness is changing rapidly at dawn and dusk, so shorter exposures are more likely to lie within your specified ADU error range
*For flats, your ADU value just needs to be somewhere in the linear response range of your sensor. In most cases, the middle of the range with a 10% error will work.
*If your camera has a lot of pixels, increasing the ROI from the default will help Voyager find the right exposure length. The average brightness over a small ROI changes more from frame to frame than a larger ROI
*The number of flats you can take for each filter will depend on your exposure length and your camera's download speeds. If your sequences are not finishing for one or more filters, consider taking fewer flats for those filters, or changing their order in the sequence so you can use a shorter exposure length
*You may need to take both dawn and dusk flats to get enough flats for each filter
*
*

Here is an example Auto Flat sequence for dawn flats: [[File:Dawn-flat-211e.jpg]]

*'''Move telescope on START:''' AutoSlew for SkyFlat is recommended - Voyager will slew the telescope to a good position for taking sky flats
*'''Move telescope During Flat:''' Dithering is a good choice here - if there are any stars bright enough to show up in your flats, they will appear in different positions so they can be eliminated when you stack your flats for processing
*'''Slew @ Each Flat''': Voyager will make a small move between flats to keep the scope pointed at a position in the sky that will reduce gradients
*'''Slew Only @ Filter Change''': Voyager will only slew between filters. Staying pointed at the same part of the sky may produce more gradients in your flats, so use this with caution. It may help if you have trouble getting enough sky flats during the available twilight

 {{Note|Auto Flat with Sky Flats will wait up to 6 hours for dawn or dusk to begin. If you need to wait longer than 6 hours, use the Wait Dusk or Wait Dawn action in a DragScript}} 
[[Category:All]]
[[Category:Manual|Jb]]

File:Autoflat-options-211e.jpg

2025-10-23T08:31:21Z

Leonardo: Leonardo uploaded a new version of File:Autoflat-options-211e.jpg

== Summary ==
importing from old wiki

File:Autoflat-sequence-216d.jpg

2025-10-23T08:29:29Z

Leonardo: Leonardo uploaded a new version of File:Autoflat-sequence-216d.jpg

== Summary ==
importing from old wiki

Version

2025-10-23T08:23:52Z

Leonardo: /* Voyager Version */

==Voyager Version==
The version of Voyager documented by this Wiki is: 2.3.13 -> (Daily Build 2025-09-28) -> 32 and 64 bit version

Voyager Release information is here: https://forum.starkeeper.it/c/releases

MediaWiki:Sidebar

2025-10-23T08:22:39Z

Leonardo:

Camera Setup

2025-09-25T16:58:09Z

Leonardo: /* QHY CMOS Native Driver */

==Camera Setup Workspace==
Click the Camera button in the Setup workspace to display the Camera setup window:

[[File:Camera-setup-217d.jpg]]
 {{Note|Camera selection must be filled out - this is mandatory for proper operation of Voyager}} 

==Color Coding==
Throughout the Setup workspace, Voyager uses color to indicate the following:

*'''Black''': A normal setting
*Gold or Yellow: Use caution when changing as things may not work well or as expected
*Red: Use extreme care when changing this setting - the wrong value can damage your equipment or the imaging session may fail

==Camera Choice==
Voyager supports the following ways to connect to a camera:

[[File:Setup-camera-216c.jpg]]

*ASCOM Camera
*ASI Camera (with ASI SDK frozen to 1.16.0 version)
*ASI Camera V2 [starting from Voyager Daily Build 2.2.16h] (for cameras need SDK equal or greater than 1.16.3 and/or using FPGA binning mode like ASI294MM Pro)
*CAM8S Camera
*CMOS ASCOM Camera V2 [starting from Voyager Daily Build 2.3.4j] (ONLY for CMOS cameras using ASCOM Camera Interface V2 and having numeric Gain managed in driver - Like all MORAVIAN CMOS)
*FLI CCD Camera
*Maxim DL
*QHY CMOS Camera
*QHY CMOS Camera BETA [starting from Voyager 2.3.0] (for using your QHY camera whit the last Beta SDK released from QHY, Beta version embedded in Voyager depend on relase or daily build creation)
*QSI Camera
*SX ASCOM Camera
*TheSkyX Camera Add On
*TheSky64 Camera Add On

Visit the [[Installation#Prerequisites|Installation Prerequisites]] section to see which versions of these third party applications are supported by Voyager.

Depending on the Camera selection, different configuration options are available, so make this selection first.

For ASCOM connected cameras, the Camera Advanced Config button brings up the ASCOM Properties dialog. The ASCOM button brings up the ASCOM chooser dialog - use this to select the specific ASCOM camera for this configuration.

== CMOS ASCOM Camera V2 ==
Choose CMOS ASCOM Camera V2 if you have a CMOS camera without native support in Voyager and you want to use the numeric Gain configurable in Sequence slots. The camera must have ASCOM driver implements ICamera V2 interface. You can ask to support if your camera are in the list of suitable for this kind of drivers. Usually all the cameras with ASCOM 5.x and newer.

The difference between normal ASCOM driver choice in Voyager is the possibility to use Gain in Sequence slots to define custom gain value for each shot.

The default Gain for plate solve and focus shot are defined in the Camera Setup tab:

[[File:Immagine2dwfwef.png]]

==TheSkyX Camera Add On==
If you choose TheSkyX Camera Add On from the Camera drop-down list, Voyager will connect directly to TSX configured Camera and Filter Wheel. {{Note|Please remove the AutoSave flag in TheSkyX Camera Add On to prevents CFITSIO error during Voyager FIT data management. Voyager will save for you all the data needed.}}

==Info about Camera Driver / SDK / ASCOM Driver ==
Some clarification about level of drivers, especially for CMOS cameras:

* Camera Driver (low level file needed by Camera to work with your OS, usually contains also the firmware will be loaded on camera for some brand/models) this must be installed in anycase and usually are not included in SDK and ASCOM driver
* SDK (mid level file for allow application to talk with the camera driver, can be used to direct access to camera) this not include camera driver usually depends on camera brands
* ASCOM Driver (ASCOM platform file allow all application compatible with ASCOM to work with camera, use SDK to access to camera driver) not include camera driver but usually include SDK, location of the SDK usually is not the right one for the application use only SDK … this is the reason if you install newer ASCOM driver not mean automatically you will have your application with updated SDK.

SDK with direct access is the most performant usually especially for CMOS with big size sensor.

Voyager have direct driver using SDK for some CMOS / CCD cameras, brands usually have a Beta Release of driver for the new cameras or just released on market. So if you want to use beta driver and upate ones used in Voyager in the wiki is described how to do or in the page of each single brand. (basically download SDK file and copy on Voyager SDK Platform folder). See [https://wiki.starkeeper.it/index.php/Installation#SDK_Platform_Folder Voyager SDK Platform folder]. Some brand like ASI and QHY have double camera control in voyager to use stable or beta version of SDK.

In any case, we will not be responsible for any malfunctions or strange behaviors.

If you have problems with these drivers, first open a support ticket at your CMOS support service.

'''A last thing, like wrote in wiki, if you will update Voyager installation with a new daily build or release we will install back the choosed driver by Voyager.'''

==QSI Native Driver==
If you choose QSI Camera from the Camera drop-down list, Voyager will connect directly to your QSI camera using the COM object released with the their SDK (not via ASCOM).

Usually until 6.x version of the CD installation software of QSI this will be included in the main installation of CD, now ATIK (owner of QSI) seems to have removed it and trust only on ASCOM driver.

How to allow Voyager work with QSI SDK driver ?

'''You can use the legacy driver installation (instead of the last version):'''

https://qsimaging.com/drivers-software/#cd-and-drivers

''<code>"Our legacy installer includes our old ASCOM driver '''QSI Installer''' (.zip) 30.9MB v1.0.0.3"</code>''

'''You can download from here the SDK:'''

https://qsimaging.com/drivers-software/#custom

Open the QSI folder inside and install it like for instructions in the readme.txt:

''<code>"Installation of QSICamera.dll requires the use of regsvr32 to register the dll in the Windows Registry.</code>''

''<code>We recommend placing QSICamera.dll in C:\Windows\System32 and then calling regsvr32 from powershell run as an administrator.</code>''

''<code> PS C:\WINDOWS\system32> regsvr32 .\QSICamera.dll</code>''

''<code>Note: On a 64 bit machine</code>''

''<code> QSICamera.dll from the x64 folder should be placed in C:\Windows\System32</code>''

''<code> QSICamera.dll from the x32 folder should be placed in C:\Windows\SysWOW64</code>''

''<code>To unregister you will need to call regsvr32 with the /u argument.</code>''

''<code> PS C:\WINDOWS\system32> regsvr32 /u .\QSICamera.dll"</code>''

We do not put this on Voyager installation to avoid retro compatibility problem with camera having 5.x and 6.x version of firmware, we are not sure all working fine with the 7.x SDK.

'''If you have a 5.x or 6.x installation CD the SDK will be installed automatically with the main installation menù.'''

If you want direct support please contact us for remote checking.

==ASI Native Driver / ASI Native Driver V2==
If you choose ASI Camera or ASI Camera V2 from the Camera drop-down list, Voyager will connect directly to your ZWO ASI camera (not via ASCOM).

{{Note|Difference between the two ASI Native driver:

- ASI Camera (with ASI SDK frozen to 1.16.0 version)

- ASI Camera V2 [starting from Voyager Daily Build 2.2.16h] (for camera need SDK equal or greater than 1.16.3 and/or using FPGA binning mode like ASI294MM Pro)}}

Click the Camera Advanced Config button to bring up the ASI Camera Setup dialog:

[[File:Zwo-camera-advanced.jpg]]

The ASI Camera Setup dialog is very similar to the ZWO ASI ASCOM dialog:

[[File:Zwo-asi-native-driver.jpg]]

 {{Note|You set default values for Gain, Offset and USB Limit in this dialog. You can override these values when you define a Sequence or Research and Survey definition on a per-element (group of exposures for a given filter) basis}} 

*'''Connected Cameras:''' Choose the camera from the drop-down list
**'''Edit:''' Click the Edit button if you would like to use a different name for the camera selected from the drop-down list
**'''USB Type:''' Displays the type of USB connection, USB3 or USB2
**'''Bayer Pattern:''' Displays the Bayer Matrix pattern If the '''Connected Camera''' has a color sensor
**'''Temperature:''' Displays the sensor temperature returned by the camera
**'''MonoBin:''' If checked and If the connected camera has a color sensor, the pixels from the color sensor are binned by the camera and a monochrome image is returned
**

*'''Preset:''' Choose a preset from the drop-down list and the preset's values will be applied to the settings for Gain, Offset and USB Limit
**[[File:Asi-preset-custom.jpg]]
**Choose one of the User presets (User 1, User 2, etc.) to create a custom preset for Gain, Offset and USB Limit
**Click the '''Edit Name''' button to change the preset name from User X to a name of your choosing:
**[[File:Asi-preset-editname.jpg]]
*'''ASI Reset Voyager Preset Setting:''' Click to reset any custom (User 1, User 2, etc) presets you created in this profile. This button appears in the top-level Camera Setup dialog if you choose ASI Camera
**[[File:Asi-reset-preset.jpg]]
*'''Gain, Offset and USB Limit Sliders:''' Click and drag these sliders with your mouse, or click on the slider and use the up and down or left and right arrows to change the values. If you change the values this way, the Preset drop-down list changes to Manual
**[[File:Asi-gain-sliders.jpg]]
*'''Gain:''' Move the slider to set the gain value. See your camera's manual for an explanation of how your choice here affects your image
*'''Offset:''' Move the slider to set the offset value. See your camera's manual for an explanation of how your choice here affects your image
*'''USB Limit:''' Move the slider to set the USB limit value. This controls how fast the camera sends data to the USB port. If your download does not finish, try a lower setting.
*'''Remove Gain Limit Management:''' (Starting from Voyager 2.2.14b version) ASI Camera driver (like for ASI specific) limit the maximum gain for DSO use, calculus is automatically done. If you want to use gain up to raw max gain, check this flag and reopen the form. If you use high gain level for this cameras you can shrink in a bad way the full well capacity and increase drammatically the noise. '''Use at your risk !'''
*'''Cancel:''' Discard changes and exit this dialog
*'''OK:''' Save changes and exit this dialog 
{{Note|The ASI Camera native driver is the only way to control the Gain and Offset values of a ZWO ASI camera from Voyager. You cannot control them from Voyager if you use the ASCOM driver to connect to your ASI camera}}

==ASI Camera Name Match==
Tells Voyager to check the ASI Camera name on connection if you are using the ASI Camera (not ASCOM) driver.

[[File:Asi-camera-name-217d.jpg]]

*'''Raise Error On Camera Connect in Startup if Name Not Match:''' If checked and the ASI Camera camera type has been selected, Voyager will raise an error when connecting to the camera if the camera name specified in setup does not match the camera name returned by the driver.

 

==FLI CCD Native Driver==
If you choose FLI CCD Camera from the Camera drop-down list, Voyager will connect directly to your FLI CCD camera (not via ASCOM) and if you want directly also to your FLI Filter Wheel.

Click the Camera Advanced Config button to bring up the FLI CCD Camera Setup dialog:

[[File:FLICameraChoose.png]]

The FLI CCD Camera Setup dialog is this one:

[[File:FLISettingForm.png]]

* '''Camera Chooser:''' Choose the camera from the drop-down list, the camera must be connected to open the settings form
* '''Rescan:''' to read again the list of FLI CCD Camera connected to the PC
* '''RBI Preflood:''' to avoid ghost issue on the KAF CCD Sensor RBI can be use to remove and mitigate the effect. More info on website of vendor. This will add extra time to the shot
**'''Flood Time:''' time of exposure in milliseconds with flooding of sensor with IR internal leds
** '''Flushes:''' number of cleaning cicle after flooding (dark mode an background flush will used if avalaible from firmware)
** '''RBI Bin Factor:''' factor to use in binning for the flooding
** '''RBI Enabled:''' switch to off if you dont want to use the RBI at all and dont want to retrieve the Readout Mode dedicated to RBI (advice is to leave ON and just not use RBI mode in various shot configuration)
* '''Advanced:''' advanced features if avalaible
** '''Do One Cleaning Image After Raw Readoutmode Change:''' used to remove with/black block of data in the image after a readoutmode switch, this will ad extra time to the shot
* '''Camera Info:''' general info about the camera read directly from it
** '''Device Model:''' Name and Sigla of model
** '''Serial Number:''' serial number attribuited to camera from vendor
** '''Firmware Vesion:''' firmware version
** '''HW Revision:''' hardware version
** '''SDK Version:''' version of SDK DLL library used by Voyager to manage the Camera and the Filter Wheel
* '''Default:''' press this button to restore setting to the default
* '''Cancel:''' to exit form without saving changes
* '''OK:''' to save the changes to settings

The FLI Filter Wheel configuration form:

[[File:97831a541208ddbdcd01187517132e49bee4f8b0.png]]

* '''Filter Wheel Chooser:''' Choose the filter wheel from the drop-down list, the filter wheel must be connected to open the settings form
* '''Rescan:''' to read again the list of FLI filter wheel connected to the PC
* '''Cancel:''' to exit form without saving changes
*'''OK:''' to save the changes to settings

{{Note|If you use different camera control or software for your FLI data collect, please verify your previous calibration files work fine. We suggest to redo a set of calibration files dedicated in Voyager.}}

==QHY CMOS Native Driver==
If you choose QHY CMOS Camera or QHY CMOS Camera BETA from the Camera drop-down list, Voyager will connect directly to your QHY CMOS camera (not via ASCOM).

{{Note|Difference between the two QHY Native driver:

- QHY CMOS Camera (QHY SDK frozen for old CMOS cameras until 2020). Use with old CMOS camera.

- QHY CMOS Camera BETA [starting from Voyager Release 2.3.0] (for camera need SDK equal or greater than 2020, you can update manually this driver if needed) . Suggested for QHY600,294,268,533,461 and newest.}}

Click the Camera Advanced Config button to bring up the QHY CMOS Camera Setup dialog:

[[File:QHYCMOSSetupcmd.png]]

The QHY CMOS Camera Setup dialog is very similar to the QHY ASCOM dialog:

[[File:QHYSetupForm.png]] 
 {{Note|You set default values for Gain, Offset and USB Limit in this dialog. You can override these values when you define a Sequence or Research and Survey definition on a per-element (group of exposures for a given filter) basis}}

{{Note|If you using the direct driver in Voyager and your QHY filter wheel is setting up to use I2C you must use the dedicated Voyager driver for the filter wheel (Voyager to QHYCMOS filter wheel) because the direct driver isn't ASCOM and work on SDK so you cannot mix things with I2C that is managed from SDK.
 If you want to use the QHY filter wheel with USB please install and select the QHY ASCOM USB driver for serial. In case of use of I2C mode or USB mode.. be sure the hardware switch in the filter wheel is positioned in the right mode, you must look at flashing and color when you start the filter wheel (default mode usually is in I2C mode). Refer to the QHY documentations.}}

{{Note|Changing manually driver in the platform folder of Voyager is an operation to your entire risk and can introduce misconfiguration or issues. To go back simply reinstall Voyager. If you install a new version of Voyager or a Daily Build the SDK will be restored by installation in any case.}}

 

*'''Camera Chooser:''' Choose the camera from the drop-down list
*'''Bin Mode''': list of the allowed binning mode for the choosed camera (selection not made any change in camera settings)
*'''Preset:''' Choose a preset from the drop-down list and the preset's values will be applied to the settings for Gain, Offset and USB Limit
**Choose one of the User presets (User 1, User 2, etc.) to create a custom preset for Gain, Offset and USB Limit
**Click the '''Edit Name''' button to change the preset name from User X to a name of your choosing:
**[[File:Asi-preset-editname.jpg]]

*'''CMOS Reset Voyager Preset Setting:''' Click to reset any custom (User 1, User 2, etc) presets you created in this profile. This button appears in the top-level Camera Setup dialog if you choose QHYCMOS Camera

*[[File:Asi-reset-preset.jpg]]

*'''Gain, Offset and USB Limit Sliders:''' Click and drag these sliders with your mouse, or click on the slider and use the up and down or left and right arrows to change the values. If you change the values this way, the Preset drop-down list changes to Manal
**[[File:QHYGaincontrol.png]]
***
*'''Gain:''' Move the slider to set the gain value. See your camera's manual for an explanation of how your choice here affects your image
*'''Offset:''' Move the slider to set the offset value. See your camera's manual for an explanation of how your choice here affects your image
*'''USB Limit:''' Move the slider to set the USB limit value. This controls how fast the camera sends data to the USB port. If your download does not finish, try a higher setting. 0 value is the fastest possible.
*'''Remove Overscan Area:''' remove overscan area from data download where sensor allow this
*'''Disable 12bit ADC to enable guiding port''': Disable 12 bit ADC to enable guiding port where sensor allow this
*'''Row Noise Reduction:''' Row noise reduction where sensor allow this
*'''Speed:''' High speed or low speed in download where sensor allow this
*'''ReadMode:''' readoutmote dropdown list where to select the readout mode for the camera (cannot be changed if camera is connected). Special mode are available for QHY600 and similar cameras.
*'''Firmware Label:''' report the versione of the firmware inside the camera selected
*'''SDK Version Label:''' report the SDK version inside the Voyager Release / Daily Build you are using. You can update SDK copying the dll of a new SDK from QHY directly inside the Voyager installation directory. We suggest to you use the ones released with Voyager distributions
*'''Cancel:''' Discard changes and exit this dialog
*'''OK:''' Save changes and exit this dialog

 {{Note|The QHYCMOS Camera native driver is the only way to control the Gain and Offset values of a QHY CMOS camera from Voyager. You cannot control them from Voyager if you use the ASCOM driver to connect to your QHY CMOS camera}}

==Filters==

If your camera is connected via MaximDL or TheSkyX Camera Add On, filters must be configured in those applications and imported to Voyager using the GET button, as described below. When you choose Maxim DL or TheSkyX Camera Add On, no filter wheel selection will be presented because the filter wheel is not connected to Voyager, it is connected to Maxim DL or TheSkyX.

For ASCOM and QSI camera, you must configure a Filter Wheel from the Filter Wheel drop-down list:

[[File:Select-filter-wheel.jpg]]

For an ASCOM filter wheel, click the ASCOM button to display the ASCOM chooser and select the filter wheel for this configuration.

Once a Camera and optionally a filter wheel have been selected, next populate the Filters window with the list of available filters.

'''With Voyager disconnected to external devices''', click the GET button to retrieve a list of filters and label names from the filter device or third party application.

[[File:Filter-list.jpg]]

{{Note|For DSLR's and One Shot Color cameras (OSC), a filter named ** Bayer Matrix ** will be shown.}}{{Note|For monochrome cameras with no filter wheel, click the Clear button and the filter ** Clear ** will be created.}}

 

==Filter Setup==
Some filter wheel drivers or applications cannot return a list of filters. For those cases, click the EDIT button and manually enter the filter list:

[[File:Filter-setup-1.jpg]]

{{Note|If entering filters manually and using a third party application such as MaximDL or TheSkyX Camera Add-on, make sure the filter Name and Number match those defined in the third party software. It is preferable to use the GET button to ensure a match.}}{{Note|Max number of filters managed by Voyager is 12}}{{Note|Magnitude usable interval start from 0 to 7}} 
===RoboStar Configuration for Filters===
Set the minimum (Mag End) and maximum (Mag Start) stellar magnitudes for Voyager's RoboStar autofocus routine on a per-filter basis.

Click the "Set Broadband" or "Set NarrowBand" buttons to use the default magnitudes for these respective filter types.
 

===RoboStar LocalField Configuration for Filters===
Set the Exposure Time in seconds and Binning for the RoboStar LocalField (multiple-star) autofocus routine on a per-filter basis.

Check the box "Not Use LocalField in Sequence" if you do not want to use LocalField autofocus while a sequence is executing.

 

==Resolution Imager==
This is where the image scale of your telescope and camera is defined.
 {{Note|For correct operation of Voyager these settings are mandatory}}

[[File:Resolution-imager.jpg]]
 

*'''Telescope Focal Length''': The focal length of the primary telescope in millimeters (mm)
*'''Pixel Size''': The size of the main camera's pixels in microns

After entering these two values, Voyager will automatically calculate the image scale for binning 1x1. This value is computed in arc-seconds/pixel and appears in the Unbinned Image Scale field

*'''Camera P.A.''': The position angle of Camera updated to the last valid solving PA retrieved by Voyager during overall operations. This value will be passed to the Virtual Field of View facility in Web Dashboard to drawing your FOV over the Aladin map. The update of this value will be done at Voyager application closing.
*'''Camera Pixel''' : The size in pixel in horizontal and vertical of your camera in bin1.This value will be passed to the Virtual Field of View facility in Web Dashboard to drawing your FOV over the Aladin map. This is a readonly field. 
{{Note|Failure to define the image scale could lead to
malfunction of the Plate Solving system and the loss of image alignment}} {{Note|From Voyager 2.0.13a, Voyager will force Maxim DL to use the focal length set in Voyager}}
 
==Sensor Type==
[[File:Sensor-type.jpg]]

In this panel, select the type of camera sensor:

*'''Monochrome''': Mono cameras with or without a filter wheel
*'''Color''': Color cameras with a Bayer Matrix (OSC or One Shot Color cameras)
*'''DSLR''': Commercial cameras, modified or not

 {{Note|If you use a third party application such as MaximDL or TheSkyX to manage your camera, all cameras defined in that application can be managed in Voyager}}
 
{{Note|If you want to use a filter wheel with a color camera, please choose Monochrome like camera type. This will enable the filter wheel control where you can configure control and filters.}} 

==Cooling System==
If the camera has a cooling system (usually a Peltier cooler), Voyager can manage it using these settings:

[[File:Cooling-system.jpg]]

*'''On Connect Set Cooler''': When Voyager connects to the camera, turn the cooling system Off, On, or leave it unchanged. If you connect to your system a long time before use, you may want to leave this "Off" or "Unchanged" and then turn the cooler on using the sequence settings or a DragScript command. If you are planning to disconnect and reconnect Camera so many thank during setting up Voyager use the "Unchanged" to avoid camera cooling to be stressed.
*'''Timeout Settling Temp''': The time in minutes after which the cooling action is considered failed if the desired temperature is not reached
*'''Deviation Max under''': The absolute temperature difference in °C allowed from the desired temperature before the cooling action is considered successful. This temperature must be maintained for the amount of time indicated in the next field, "... for time span of"
*'''... for time span of''': The amount of time that the temperature must be within the "Deviation Max under" described above for a cooling action to be considered successful
*'''Default WarmUp Time''': The time in minutes after which the warmup action is considered failed if the desired temperature is not reached
*'''Default Temp. Cooling''': The desired temperature in °C for a cooling operation
*'''Default Cool Down time''': The desired time in minutes used to reach the desired cooled temperature, to avoid cooling too fast which in some cases can cause frost to form
*'''No CoolDown for Delta''': The maximum difference in °C below which the camera's native firmware cooling system is used instead of the Cool Down parameters specified here. In other words, if the camera's sensor is currently at -25 °C and you request a change to -30 °C, if the "No CoolDown for Delta" value is 10 °C, Voyager will just command the camera to cool to -30 °C without any management of cool down ramp time.
*'''Default Temp. WarmUp''': The desired temperature in °C for a WarmUp operation. Note that if this is set too high, the WarmUp operation may fail. However, in most cases this does not cause any problems.
*'''Temperature Control Allowed by Camera:''' remove flag if camera doesn't allow temperature control or not have it

These settings are used for all operations relating to setting the camera's sensor temperature. To find out how they work in detail read see the [[OnTheFly]] section.
 
{{Note|The fields "Default Cool Down Time," "Timeout Settling Temp" and "... for time span of" are closely
linked. The "Timeout Settling Temp." should be larger than the "Default Cool Down Time" plus the "...for the span of" time, or the cooling action would always result in a timeout error}}{{Note|You can use the cooling system's native firmware factory settings in the Cooling panel of the Sequence Configuration dialog}}

{{Note|The Sequence Configuration dialog's Cooling panel supports auto setpoint scaling. If the camera cannot reach the desired temperature within a defined time, it will try to reach a designated warmer temperature}} 
==Readout Mode==
Some cameras have settings to control readout speed vs. readout noise. The Readout Mode section of the Setup workspace lets you configure these settings:

[[File:Readout-mode.jpg]]
 

*'''GET''': Click this button to retrieve the list of available modes, if any. '''Voyager must be disconnected from the control systems for this to work'''
*'''Light/Dark/Bias''': Recommended setting is to have the highest quality - lowest noise, regardless of speed. But this is optional - you can choose any setting
*'''Focus''': Recommended setting is fastest speed, regardless of noise, so autofocus operations happen quickly
*'''Plate Solve''': Recommended setting is fastest speed that still results in successful plate solves. If you are not sure, set for highest quality.

 
==Speed==
Some cameras have settings to control gain in order to improve dynamic range. The Speed section of the Setup workspace lets you configure these settings in order to accelerate some Voyager features:

[[File:Camera-speed.jpg]]

*'''GET''': Click this button to retrieve the list of available modes, if any. '''Voyager must be disconnected from the control systems for this to work'''
*'''Binning 1x1''': Choose the gain to be used when taking exposures with binning 1x1
*'''Binning 2x2''': Choose the gain to be used when taking exposures with binning 2x2
*'''Other Binning''': Choose the gain to be used when taking exposures with binning other than 1x1 and 2x2

 

==TheSkyX Camera Add On Setting==
Settings for TheSkyX Camera Add On can be configured in this panel of the Camera setup workspace:

[[File:Theskyx-camera-settings.jpg]]
 

Due to a lack of commands in TheSkyX's DCOM interface (the interface used by external applications to manage TheSkyX operations), Voyager is unable to determine the current filter selected in the filter wheel. To ensure the correct filter is used, Voyager takes a very short "dummy exposure" and sets the filter to the desired value. The "dummy image" is not saved. The default values here should be good for most setups. The goal is to make this a very short exposure with a fast download, so if you know of better settings for your camera, you can set them here.

*'''Dummy Exposure Bin''': Binning level to be used when taking dummy exposures
*'''Dummy Exposure ROI''': Region Of Interest size to be used when taking dummy exposures
*'''Dummy Exposure Time:''' Exposure time to be used when taking dummy exposures

 
{{Note|Be sure your dummy exposure time is not under the minimum value accepted from the camera. This could be thrown an error in the camera driver}}
 

==Maxim DL==
Settings dedicated to Maxim DL Camera additional features:

[[File:Immaginefr3fwf.png]]

* '''Quit Camera Connection on Voyager Setup Disconnect:''' disconnect camera in Maxim DL when disconnect setup from Voyager

==Various==
Miscellaneous settings are contained in the Various panel of the Camera setup workspace:

[[File:Camera-various.jpg]]

*'''Download Save Timeout''': Time in seconds after which the download of an image from the camera times out (fails)
*'''ASCOM ImageReady Slow Polling''': Delay before polling the ASCOM driver to see if the image is ready to download. This is used if the camera's firmware is slow and needs some time between ImageReady queries (see [https://forum.starkeeper.it/t/camera-communication-speed-adjustment/276/4 discussion] in the Voyager forum)
*'''ASCOM Polling De-Throttle''': Controls the amount of delay between requests to the ASCOM camera driver to avoid overflowing a slow camera's command buffer.
*'''Use Canopus FIT fix''': [http://www.minorplanetobserver.com/MPOSoftware/MPOCanopus.htm MPO Canopus] is an astrometry and photometry application usually used in Astronomical Research . This flag fix a ''OBJCTDEC'' key in saved FIT Header adding a + for a positive value. Without this flag Canopus cannot handle correctly the FIT made by Voyager (or others FIT generator)
*'''Not Manage AIRMASS in FIT''': Voyager will not write AIRMASS calculated value in the FIT Header, if camera control in Voyager is an external application, this application will be delegated to write the AIRMASS header (like Maxim or TSX Camera add on)
*'''Additional Safe Time after Filter Wheel filter change:''' add an extra time wait of x seconds after the driver of the filter wheel report changing of filter is finished. This to avoid that filter wheel that report wheel have finished to move but is not true might affect the next image in shot
*'''Hide Personal Info in FITS Header''': remove personal data from FIT Headers (SITELAT, SITELONG, OWNER, SWOWNER, OBSERVER)
*'''Leave FILTER FIT Header content blank:''' regardless of the filter used to trigger the FIT, no text will be inserted in the headers for the FILTER header 

==FIT Headers Custom==
Various FIT Headers that can be written with the values in the settings:

[[File:Immaginevbdfvdf.png]]

* '''BAYERPAT''': bayern pattern of the color sensor
* '''XBAYROFF''': offset of the bayer pattern in X
* '''YBAYROFF''': offset of the bayer pattern in Y
* '''ROWORDER''': This keyword is <code>ROWORDER</code> of type <code>TSTRING</code>. It can take two values: <code>BOTTOM-UP</code> and <code>TOP-DOWN</code>.

==Other Setup Pages==
<categorytree mode="pages" depth="1">Setup</categorytree>

[[Category:Setup]]
[[Category:All]]
[[Category:Manual|Ha]]

AutoFocus Setup

2025-03-17T08:36:14Z

Leonardo: /* RoboFire Configuration Center */

==AutoFocus Setup Video==
There is a video on setting up AutoFocus on the Voyager Astro Imaging YouTube Channel

<youtube>https://www.youtube.com/watch?v=VkWxrhRN_ns&t=2s</youtube>

==AutoFocus Setup Workspace==
The AutoFocus Setup workspace is where you store settings for Voyager's autofocus operations:

[[File:Autofocus-setup-2.12e.png]]

 

==Color Coding==
Throughout the Setup workspace, Voyager uses color to indicate the following:

*'''Black''': A normal setting
*Gold or Yellow: Use caution when changing as things may not work well or as expected
*Red: Use extreme care when changing this setting - the wrong value can damage your equipment or the imaging session may fail

==Avoid different Thickness Filter Set==
Using filter with different thickness is something to avoid. This cause focus shift between set of filters and can cause autofocus failure.

If unfortunately you are in this situation you can mitigate this in Voyager by:

* create and use a dedicated profile for narrow band filter without broadband filters
* in the sequence override the plate solve fitler with one narrow filter and increase binning and exposure time for solving (https://wiki.starkeeper.it/index.php/Sequence_Configuration#Plate_Solving_Tab)
* change the '''Near Focus''' setting of RoboFire increasing for how much is needed to recognize the HFD value when you switch to narrow filter and for sure not using LocalField autofocus (https://wiki.starkeeper.it/index.php/AutoFocus_Setup#VCurve_Mode_Tab). At start of focus an HFD lower than Near Focus parameter will abort the focus process.

==AutoFocus Choice==
Select the AutoFocus program you want to use at the top of the AutoFocus Setup workspace:

[[File:Autofocus-choice.jpg]]

*AutoFocus: Select the autofocus program from the options in the drop-down list

[[File:Autofocus-selections.jpg]]

*Available selections include None, FocusMax, TheSkyX @Focus2, Maxim DL, RoboFire, and TheSkyX @Focus3

*FocusMax is a product of CCDWare: http://www.ccdware.com/products/focusmax/
*TheSkyX has two autofocus routines: @Focus2 and @Focus3. TheSkyX is a product of Software Bisque: http://www.bisque.com/sc/pages/TheSkyX-Editions.aspx
*Maxim DL is a product of Diffraction Limited: http://diffractionlimited.com/product/maxim-dl/
*RoboFire is Voyager's proprietary autofocus function, and has two options: RoboFire VCurve mode (focusing on a single star), and RoboFire LocalField (multi-star focus)

{{Note|RoboFire Autofocus doesn't allow use of focuser with relative driver movements mode ... only absolute ASCOM driver}}

{{Note|RoboFire Autofocus is not compatible (at now) with Baader SteelDrive focusers}}

==Focuser Choice==
If you choose RoboFire for autofocus, you must select ASCOM Focuser from the Focuser drop-down, and then click the ASCOM button to select the focuser. Click the Config button to modify the ASCOM focuser's settings:

[[File:Autofocus-choice.jpg]]

If you use any of the other autofocus options, you must set up the focuser in those programs, not in Voyager.

==Focus Result Watchdog==
The Focus Result Watchdog panel in the AutoFocus Setup workspace has several parameters controlling whether an autofocus operation is considered successful:

[[File:Focus-result-watchdog.jpg]]

*'''Max HFD Value Allowed (or Zero detect)''': If checked, specify the maximum HFD (Half Flux Diameter) value in pixels beyond which the autofocus operation is considered to have failed
*'''Retry Focus For Watchdog''': The number of times an autofocus routine will be tried before giving up
*'''HFD Variation Mobile Mean Sample Frame Width''': The number of HFD values obtained from the autofocus action to be used for the calculation of the moving average. The value of the moving average will be used by the HFD watchdog during the Sequence at the end of each autofocus to validate the result obtained in percent.

 
==Work Around==
The Work Around panel in the AutoFocus Setup workspace contains a parameter to prevent focuser motion from stopping after a HALT ALL command:

[[File:Autofocus-workaround-2.12e.png]]

*'''Don't Halt Focuser on HALT ALL Command''': If checked, when a HALT ALL command is issued, which normally stops all motion, do not stop the focuser if it is moving. This is needed because sending HALT to some focuser drivers cause them to move the drawtube to the zero position.
*'''Use Slow Polling for ASCOM HUB or Not Multi Thread Driver''': If checked, adds a delay between requests to the ASCOM focuser HUB driver. This may help for autofocus drivers that are not multi-threaded or have trouble responding quickly enough to Voyager's requests. Leave off unless needed.
*'''Focuser Position Check Tolerance [-/+]''': If non-zero, when Voyager commands the focuser to move to a position, the move will be considered successful if the ending step value is within this many steps plus or minus from the commanded value. I.e., if a tolerance of 5 is specified, a focuser goto 1000 command will succeed if the ending position is any value between 995 and 1005. By default, this is zero and focuser commands will return an error is the ending value is different from the commanded value. It is recommended to use a value of 0 here unless your focuser has difficulty going to the commanded position, which is unusual but has been seen in some focusers. Less than optimal focus may be obtained if this value is non-zero

 
==RoboStar General Setting==
The RoboStar General Setting panel in the AutoFocus Setup workspace contains parameters for Voyager's RoboStar operation, which automatically selects a focus star:

[[File:Robostar-general-setting.jpg]]

 

*'''MIN Altitude for Candidate Focus Star''': Minimum altitude allowed for the focus star when chosen by RoboStar for a VCurve AutoFocus. A star lower than this value will not be considered.
*'''MAX Altitude for Candidate Focus Star''': Maximum altitude allowed for the focus star when chosen by RoboStar for a VCurve AutoFocus. A star higher than this value will not be considered.
*'''Wrong Focus Stars Manager''': Click this button to bring up the RoboStar Wrong Focus Stars Black List Manager. Add stars to this list that you do not want used as focus stars. For example, a double star may not work as a focus star and could be listed here. To add a star to the list, type its name in the Name field, click the Add button, and click OK. Just add the name, and if that name exists, Voyager will add the star to the black list and also display the data for any other blacklisted stars
{{Note|As of Voyager 2.1.1e, you can bring up the Wrong Focus Stars manager at any time, even when a sequence is running, by clicking the Wrong Focus Stars button on the Tools and Editor ribbon}}

[[File:Wrong-star-manager.jpg]]

*'''Star Magnitude Interval / Exp for Filter Autofocus''': Click the Edit Filters Magnitude / Exposure button to bring up the [[Camera Setup#Filter Setup|'''Filter Setup''']] dialog where you can specify the dimmest and brightest stars to be used by the RoboStar routine when searching for a focus star. You can also specify the exposure time and binning for each filter, as well as whether or not to use each filter during a RoboFire LocalField autofocus operation during a sequence.

[[File:Filter-setup-1.jpg]]

*Documentation for the Filter Setup dialog is here: [[Camera Setup#Filter Setup|'''Filter Setup''']]
*'''DEFAULT Star Magnitude Interval for Autofocus''': Specify the magnitude range to be used for focus stars, from the brightest (Mag Start) to the dimmest (Mag End). Click the Reset button to restore the default magnitudes.

==TheSkyX @Focus3 Setting==
The TheSkyX @Focus3 Setting panel in the AutoFocus Setup workspace contains parameters for TheSkyX @Focus3

[[File:Theskyx-atfocus3.jpg]]

*'''Starting Focus Exposure Time''': Exposure length in seconds to be used by TheSkyX's @Focus3 autofocus routine
*'''Sample Averaging Number''': The number of exposures to take at each focuser position by TheSkyX's @Focus3 autofocus routine

==AutoFocus Temperature Trigger Mode==
Contains options for selecting the temperature data source to select for generating the autofocus trigger

[[File:TempTrigger231.png]]

* '''Focuser Sensor''': this is the default option. Data about temperature for generate the trigger for AutoFocus will be readed from focuser temperature sensor
* '''Observing Conditions Control [TEMPERATURE]:''' with this option the data about temperature for generate the trigger for AutoFocus will be readed from the observing conditions control configured in Voyager, and exactly reading the TEMPERATURE variable in the data set
* '''SQM Control [TEMPERATURE]:''' with this option the data about temperature for generate the trigger for AutoFocus will be readed from the SQM control configured in Voyager. Be sure your SQM driver are of tupe observing conditions or reports this features.

{{Note|In case of absence or failure of the Observing Conditions Control or SQM Control, Voyager will switch automatically to the focuser sensor for generating the trigger.}}

==RoboFire General Setting==
The RoboFire General Setting panel in the AutoFocus Setup workspace contains important RoboFire autofocus settings and controls, including RoboFire configuration, VCurve First Light Wizard and management, and a live action to find the closest focus star using RoboStar:

[[File:Robofire-setting.jpg]]

*RoboFire Configuration Center: Click this button to bring up the RoboFire Configuration Center tabbed dialog, described below in the [[AutoFocus Setup#RoboFire Configuration Center|RoboFire Configuration Center]] documentation

==RoboFire VCurve vs. LocalField: Which to Use When?==
Voyager has two different autofocus methods: VCurve (single-star) and LocalField (multiple-star).

*VCurve: VCurve autofocus is done on a single star at the center of the field of view. VCurve works best when your optics are flat - the focal point is the same across the field - or when the region of interest is in the center of the field in a portion that is flat or close to flat (same focus). For example, this is a good choice for small galaxies and planetary nebulae.
*LocalField: LocalField autofocus optimizes the average focus (HFD: Half Flux Diameter) of multiple stars across the entire field. If your optics are not flat - there is some variation across the field - and your region of interest spans the field, LocalField will give you the best focus across the entire image. For example, this is a good choice for large nebulae or star clusters taking up the entire field.

 

{{Note|If you decide to use LocalField focus evaluate to activate also the Realign to target flag in the Sequence Guide and Dithering tab, This to avoid drift of image if your mount are not perfect aligned. This is true especially for highr res setup}}

==RoboFire Configuration Center==
Voyager's RoboFire autofocus function is configured from the RoboFire Configuration Center panel of the AutoFocus Setup workspace. Click the RoboFire Configuration Center button to bring up the tabbed dialog box.

===Focuser Tab===
[[File:Robofire-config-focuser.jpg]]

*'''Focuser Control Facility Step Size CMD''': Number of focuser steps to move for each click of the "<" and ">" small move buttons in the [[Command Window#Focuser|RoboFire Focuser command widget]] . The Large Move buttons "<<IN" and ">>OUT" move this number of steps x5.
*'''Limits:'''
**'''IN Limit''': The minimum position (furthest in) of the Focuser in steps
**'''OUT Limit''': The maximum position (furthest out) of the Focuser in steps
*'''Backlash Compensation''':
**'''Enable''': Check this box to enable backlash compensation. Some focusers have "backlash," which is what happens when you reverse focuser direction and the focuser doesn't move for a number of steps because the mechanism has a bit of "play" when changing direction
**'''IN/OUT''': If the Enable box is checked, the IN/OUT radio buttons control when backlash compensation is applied, either when moving IN or OUT. IN means backlash compensation will be done when the focuser receives a command to move IN (a compensation value will be added to the requested value in the IN direction and after the IN move is finished a move OUT will be done by the same compensation value)
**'''Steps''': Set the number of focuser steps of backlash compensation to apply. If the Enable box is checked, RoboFire autofocus will command the focuser to move this many steps when reversing focuser direction to compensate for backlash
*'''Advanced:'''
**'''Reverse Focuser Direction''': If checked, Voyager will treat the focuser position as reversed from normal, i.e. a smaller position number is further out, and larger numbers are further in. Please only check this setting if you are sure, as it could cause damage to your equipment if set incorrectly.
**'''Focus Final Offset +/- Steps''': If checked, Voyager adds / subtracts this value of steps when an autofocus operation is terminated with success. This option allows you to manage optics with a zonal defect or a collimation problem that cannot be fixed
**'''Use Focus Final Offset only for Single Star Focus Mode''': if checked and Focus Final Offset +/+ Steps option is checked the offset will be added if the current focus running is a single star type
*'''Workaround:'''
**'''Wait Time After Focuser Movements:''' if check a delay after the focuser movements will be applied. Expressed in seconds.

===VCurve Mode Tab===
Voyager's RoboFire single star autofocus works by creating a "V Curve" representing HFD (a star's Half Flux Diameter or "size") vs. focuser position. You should run the VCurve First Light Wizard to create an initial VCurve, and the Add New VCurve operation to run additional VCurves. Running multiple VCurves can improve autofocus accuracy. The buttons you click to run these VCurve functions are in the AutoFocus Setup workspace.

VCurve from a RoboFire autofocus run
[[File:VCurveRun.png|none|thumb|745x745px]]

Continuing with the RoboFire Configuration dialog, the second tab is the VCurve Mode Tab, filled out with some values from running the VCurve First Light Wizard on an actual system. The values you see will look different.

[[File:Focuser-vcurve-1.jpg]]

*'''Actual VCurve Parameters (Compatible with FocusMax):''' If you have values from running VCurves with CCDWare's FocusMax product using the same focuser and optical system, you can manually enter them here.
**'''Slope Left''': The slope of the left portion of the VCurve
**'''PID''': (Position Intercept Difference): The number of focuser steps between the X-axis intercept points (where the Half Flux Diameter is zero) of the left and right VCurve lines. The smaller this value, the steeper the V Curve lines.
**'''Step Inc''': The number of focuser steps between each measured point on the VCurve
**'''Slope Right''': The slope of the right portion of the VCurve

Click the Edit or Manage button in the Actual VCurve Parameters panel to bring up the RoboFire VCurve Data Manager. The Data Manager shows the current VCurve parameters being used by RoboFire autofocus and the values from runs of the VCurve First Light Wizard and any runs of the Add New VCurve function.

[[File:Vcurve-data-1.jpg]] 

*'''Actual VCurve Parameters (Compatible with FocusMax)''': If you have computed a VCurve with Voyager, the VCurve parameters are shown here. If you have values from CCDWare's FocusMax using the same focuser and optical system, you can type them in here.
*'''Calculate from VCurve Data in Table''': Click this button to calculate VCurve parameter values based on the rows in the Data Manager table below the button. Only rows with a "Yes" value in the "Use" column are included in the computation.
*'''Suggest Step Increment''': The Step Increment is the number of focuser position steps moved between VCurve measurements. If you have data entered in the Actual VCurve Parameters table and are not sure of the proper step increment, click this button for a recommendation. Type the recommended value into the Step Inc. field to use it in RoboFire autofocus operations.
*'''Validate Manual Values''': Click this button to verify that the values you entered in the Actual VCurve Parameters fields make sense. This doesn't guarantee proper autofocus results; it only checks the values for mathematical or logical inconsistencies.
*'''Use/Delete Buttons''': Click the button in the Use column of the VCurve Data table to toggle between "Yes" and "No." Only rows with "Yes" in this column are used when you click "Calculate from VCurve Data in Table.
*'''Comment''': The Comments field is populated when you run Voyager's VCurve operations. Click the Comment button in the VCurve data table row to edit the comment.

Returning to the RoboFire Configuration dialog, VCurve Mode tab:
[[File:Focuser-vcurve-1.jpg|none|frame]]

*'''COMMON Parameters''':
**'''Focuser Direction for VCurve and Autofocus''': IN / OUT: Click this radio button to define the direction the focuser should move when performing a VCurve autofocus operation.
*'''HFD Parameters''': HFD is the Half Flux Diameter of the focus star
**'''Near Focus''': HFD value to use when running the Near Focus part of the autofocus routine. During the Near Focus routine, multiple measurements are taken of the focus star to establish its HFD, which is then used to determine where the focuser is on the VCurve. Once this position is established, the number of steps needed to reach the middle of the VCurve (in focus) can be determined.
**'''Start Focus''': The HFD of the focus star at which to start the autofocus operation
**'''VCurve Limit''': The HFD value at the beginning and end of the VCurve
*'''Star Flux Parameters''':
**'''MIN Flux''': Minimum (dimmest) flux of the focus star. The number entered is multiplied by 1000 to determine the minimum star flux
**'''MAX Flux''': Maximum (brightest) flux of the focus star. The number entered is multiplied by 1000 to determine the maximum star flux
*'''First Light Advanced Settings:'''
**'''Focuser Progression:''' RoboFire Automata use a logaritmic search of position in power of 2 (1,2,4,8,16,32... focuser steps). If you focuser resolution is Low change the resolution of Progression from Default up to Low and Very Low Resolution. Lower is the resolution selected smaller will be the increment during the slope search in the First Light Wizard. Use it if you experience too big change in interval used by RoboFire with fast override of max HFD value in VCurve Limit Parameter. RoboFire need to find at least 3 point between the HFD Parameters selected inside the interval defined between Near Focus and VCurve Limit to allow slope calculation. Otherwise an error will be raise for few points usable for slope calculation.
*'''Camera Parameters''':
**'''Bit/Pixel''': BIts per pixel of the data coming from the driver of the imaging camera's driver. Usually is 16bit.
**'''Frame Width''': Width in pixels of the autofocus frame - the focus star must stay in this frame during the autofocus operation. Maximum size is 1024 pixels
**'''Central Region''': The percentage of the overall camera frame used as the central region. Focus stars must be within this region
**'''Target Star Bin''': The binning used for the exposures taken to find the target star when RoboStar is used to find a suitable focus star
**'''Focus Bin''': The binning used for exposures taken during autofocus
**'''Filter for VCurve''': Filter used for exposures taken while building a VCurve
*'''Exposure Parameters''':
**'''MIN Time''': The shortest allowed exposure time, in seconds, for autofocus. The RoboFire autofocus routine will adjust the exposure time between the MIN and MAX to try to find a time that achieves the desired star flux parameters
**'''Default Time''': This is the exposure time, in seconds, used for the initial image taken by the RoboFire autofocus routine
**'''MAX Time''': The longest allowed exposure time, in seconds, for autofocus. The RoboFire autofocus routine will adjust the exposure time between the MIN and MAX to try to find a time that achieves the desired star flux parameters
*'''Max HFD Error for Algorithm to find Top, Start and Near Focus''':
**RoboFire autofocus will take successive exposures and compare the resulting HFD's, looking for the values to converge within the specified error amount (either Absolute Diff or Percentage)
**Click one of the radio buttons - either the one before Absolute Diff or the one before Percentage - to select how the Max HFD (Half Flux Diameter) Error is determined
**'''Absolute Diff''': If the radio button for this choice is selected, the maximum HFD error allowed is this number expressed in pixels
**'''Percentage''': If the radio button for this choice is selected, the maximum HFD error allowed during autofocus is this percentage

 

===LocalField Mode Tab===
The LocalField Mode tab of the RoboFire Configuration dialog of the AutoFocus setup workspace contains parameters used by RoboFire's LocalField autofocus operation. LocalField autofocus is a multiple star focusing routine which finds the focuser position that minimizes the average HFD (Half Flux Diameter) of multiple stars in the autofocus exposures.

Prior to Voyager 2.1.1e, the LocalField tab looked like this: (see below for the new one)

[[File:Localfield-mode.jpg]]

*'''Camera and Exposure Parameters'''
**'''Focus Bin''': The binning used for LocalField autofocus exposures
**'''Default Time''': The exposure length in seconds of LocalField autofocus exposures. For the individual filter exposure times, use the [[Camera Setup#Filter Setup|Filters Setup Dialog]]
**'''Central Region''': The percent of the image's central region used by the LocalField autofocus operation
*'''LocalField AI Engine''':
**'''Focuser Step x Sample''':
***'''From VCurve Mode Wizard''': Choose this radio button to use the step size from the RoboFire VCurve settings. The step size is the number of steps to move the focuser between autofocus exposures
***'''Manual''': Choose this radio button to enter the step size manually
**'''Sample''': The number of exposures to take during the LocalField autofocus operation. One sample is taken at each focuser position
**'''Minimum Stars Number''': LocalField autofocus will require at least this number of stars in each exposure to be successful
*'''Advanced Settings''':
**'''Min HFD Gap''': a minimum pixel gap from the minimum value of HFD and maximum value of HFD found during the LocalFIeld sampling
**'''Min Confidence''': The minimum statistical confidence percentage to consider autofocus successful
**'''Focus Window Size''': The percentage of the image (Central Region of CCD) used during the autofocus routine
**'''Fit Order''': Curve FIT order in AI analysis of results
*'''Reset to Default''': Reset all LocalField Mode settings to Voyager's defaults

As of Voyager 2.1.1e, the labels in the LocalField setup tab have been changed to make them easier to understand:

[[File:Localfield-setup-211e.jpg]] 

*'''Camera and Exposure Parameters'''
**'''Central Region''': The percent of the image's central region used by the LocalField autofocus operation. '''Reduce this percentage if you are getting out of memory errors during LocalField autofocus'''
**'''Focus Bin for DSLR/OSC/No Filter Camera''': The binning used for LocalField autofocus exposures IF you are using a DSLR, One Shot Color or any camera without filters
**'''Default Time DSLR/OSC/No Filter Camera''': The exposure length in seconds of LocalField autofocus exposures IF you are using a DSLR, One Shot Color or any camera without filters
**'''Manage Focus Bin and Time for CCD with Filters:''' If you are using a mono camera with a filter wheel, click this button to use the [[Camera Setup#Filter Setup|Filters Setup Dialog]] where you can specify binning and default exposure time for each filter
*'''LocalField AI Engine''':
**'''Focuser Step x Sample''':
***'''From VCurve Mode Wizard''': Choose this radio button to use the step size from the RoboFire VCurve settings. The step size is the number of steps to move the focuser between autofocus exposures
***'''Manual''': Choose this radio button to enter the step size manually
**'''Sample''': The number of exposures to take during the LocalField autofocus operation. One sample is taken at each focuser position
**'''Minimum Stars Number''': LocalField autofocus will require at least this number of stars in each exposure to be successful
*'''Advanced Settings''':
**'''Min HFD Gap''': a minimum pixel gap from the minimum value of HFD and maximum value of HFD found during the LocalFIeld sampling
**'''Min Confidence''': The minimum statistical confidence percentage to consider autofocus successful
**'''Focus Window Size''': The percentage of the image (Central Region of CCD) used during the autofocus routine
**'''Fit Order''': Curve FIT order in AI analysis of results
*'''Reset to Default''': Reset all LocalField Mode settings to Voyager's defaults

===Various Tab===
The final tab of the RoboFire Configuration dialog contains some miscellaneous parameters:

[[File:Robofire-various.jpg]]

*'''Dashboard''':
**'''Show Dashboard During RoboFire Actions''': If checked, the RoboFire dashboard appears while the autofocus operations are in progress
**'''Dashboard on Top''': If checked, keep the RoboFire Dashboard on top of other windows while it is active
**'''When Action Finished Auto-Close Dashboard After''': If the RoboFire dashboard is displayed during the autofocus operation, this is the number of seconds to wait after autofocus completes before automatically closing the dashboard window
*'''Workaround'''
**'''Remove AI Diffuse Filter on Star Recognition for setup with deeply undersampled resolution, big sensor area and narrow band filters with lower nanometers''': to avoid empty star recognition process for situation descripted in the label. Use only if are inside the cases written in label. THis flag is red, if you aren't sure of what to do please referring to the Voyager suppor

* '''FIT'''
**'''Add FOcuser Position to FIT File name during Sequence''': flag this to add position of focuser (if available) to the name of FIT file will be saved

==Point Closest Focus Star with RoboStar==
[[File:Point-focus-star.jpg]]

This button starts a RoboStar operation to find a suitable nearby focus star.

{{Note|Pointing will be done with a simple goto, not a precise pointing. This because you may not have a good focus and solve may fail. Porpouse of this goto is to have a star in the field for the first light wizard or for adding new vcurve. Precise pointing isn't necessary. You will receive a warning about plate solve disabled ... is not an error (is yellow so its a warning). Just Voyager remember to you about performing a simple goto.}} 

==VCurve First Light Wizard==
[[File:Vcurve-first-light.jpg]]

Click this button to start the VCurve First Light Wizard, which walks you through all the steps needed to calculate a VCurve with your system.

The first panel of the wizard lists '''important actions you must take''' before running the wizard. Please read and follow all these steps to avoid damage to your equipment. This information will not be repeated here - read and follow the steps in the wizard.

[[File:Vcurve-wizard.jpg]]

When you have read and followed all the steps in this panel, click the OK button to immediately run the VCurve First Light Wizard

TODO: Run the wizard and capture screen shots

{{Note|VCurves are optics-specific. If you change the optics of your scope, e.g. add a Focal Reducer or Field Flattener, you should run a new VCurve}}

{{Note|VCurve results are saved in the current profile. Create a profile for each set of optics and run a new VCurve when the optics change}} 
==Add New VCurve==
[[File:Add-new-vcurve.jpg]]

Click this button to run an immediate operation to take exposures as specified in the RoboFire Configuration Center to calculate a VCurve.
{{Note|You must run the VCurve First Light Wizard before running the Add New VCurve operation}}

The new VCurve is stored in the [[AutoFocus Setup#VCurve Mode Tab|VCurve data table]] where it can be used to refine the RoboFire autofocus VCurve. Taking several VCurves can help your autofocus results.

TODO: Run this command and capture screen shots

 
==Test AutoFocus VCurve==
[[File:Test-autofocus-vcurve.jpg]] Click this button to run a RoboFire autofocus operation to test the VCurve parameters with a real life autofocus

TODO: Run and capture screen shot
 
==Other Setup Pages==
<categorytree mode="pages" depth="1">Setup</categorytree>

[[Category:Setup]]
[[Category:All]]
[[Category:Manual|Hf]]

Voyager Setup

2025-01-21T08:44:23Z

Leonardo: /* External PROCESS Starting */

==Color Coding==
Throughout the Setup workspace, Voyager uses color to indicate the following:

*'''Black''': A normal setting
*Gold or Yellow: Use caution when changing as things may not work well or as expected
*Red: Use extreme care when changing this setting - the wrong value can damage your equipment or the imaging session may fail

 
==Voyager Setup Workspace==
Click the Voyager button in the Setup workspace to display the Voyager settings window, which contains miscellaneous settings about Voyager's operation:

[[File:Setup-voyager-221.jpg]] 
==CCD Graph==
The CCD Graph panel of the Voyager setup workspace contains parameters for the [[Status Window#CCD|CCD Widget]] displayed in the [[Status Window]]

[[File:Ccd-graph.jpg]]

*'''Default Scale Temp. Top (°C)''': Default value for the top of the temperature scale, in °C
*'''Default Scale Temp. Bottom (°C)''': Default value for the bottom of the temperature scale, in °C
*'''Timer Interval in Graph''': Total time represented by the X axis of the graph in seconds
*'''Show Min/Max Temperature Axis Label''': If checked, display the white boxes with the values represented by the top and bottom of the Y axis (temperature) of the [[Status Window#CCD|CCD Widget]] displayed in the [[Status Window]]
*'''Show Temperature Label relative to Mouse''': If checked, hovering the mouse shows the temperature of the point under the mouse cursor in the [[Status Window#CCD|CCD Widget]] displayed in the [[Status Window]]
*'''AutoScale Temperature Axis''': If checked, automatically scale the values of the top and bottom of the Y axis (temperature) of the [[Status Window#CCD|CCD Widget]] displayed in the [[Status Window]] so the displayed values fit in the widget

 

==Guide Box==
The Guide Box panel of the Voyager setup workspace contains parameters for the [[Status Window#Guide|Guide Widget]] displayed in the [[Status Window]]:

[[File:Guide-box.jpg]]

*'''Default Pixel Scale''': The number selected from the drop-down box represents the number of pixels, +/-, represented by the Y axis scale of the [[Status Window#Guide|Guide Widget]] displayed in the [[Status Window]]. For example, a value of 1 here means the top of the graph represents a guide error of +1 pixels, and the bottom of the graph represents a guide error of -1 pixels
*'''Default Frame Scale''': The number of guiding frames (exposures) represented by the X axis of the graph
*'''Show Scale Label''': If checked, the values of Default Pixel Scale and Default Frame Scale are displayed in white boxes at the top and bottom respectively of the [[Status Window#Guide|Guide Widget]] displayed in the [[Status Window]]
*'''Show Temperature Label relative to Mouse''': If checked, when the mouse is hovered over the [[Status Window#Guide|Guide Widget]] displayed in the [[Status Window]], a white box pops up over the graph and shows the temperature represented by the mouse pointer location
*'''Show StarMass Mobile Mean Value''': If checked, the moving average of the StarMass value is displayed in the [[Status Window#Guide|Guide Widget]] displayed in the [[Status Window]]
*'''Show Sub RMS Value''': If checked, the RMS value of the current guide exposure is displayed in the [[Status Window#Guide|Guide Widget]] displayed in the [[Status Window]] 

 
==TARGET Graph==
The TARGET Graph panel of the Voyager setup workspace contains parameters for the [[Status Window#Target|Target Widget]] displayed in the [[Status Window]] [[File:Target-graph.jpg]]

*'''Show Min/Max Altitude Axis Label''': If checked, label the Y axis (altitude) of the [[Status Window#Target|Target Widget]] displayed in the [[Status Window]] with the values of the bottom and top lines of the graph
*'''Show Time Label relative to Mouse''': If checked, hovering the mouse over the [[Status Window#Target|Target Widget]] displayed in the [[Status Window]] pops up a box with the value corresponding to the X axis (time) value of the mouse pointer position

 
==ECHO Box==
The ECHO Box panel of the Voyager Setup workspace contains settings for the [[Main Window#Monitor Window|Monitor Window]], formerly known as the Echo box.

[[File:Echo-box.jpg]]

*'''Use Big Font Size in Echo Windows''': If checked, use large fonts in the [[Main Window#Monitor Window|Monitor Window]], which is the window where status messages appear for running actions

 

==External PROCESS Starting==
The External PROCESS Starting panel of the Voyager Setup workspace contains information relative to starting processes external to Voyager:

[[File:Voyager-external-process-2.1.7s.jpg]]

*'''Wait Process Starting for''': Number of seconds to wait after starting a process external to Voyager, e.g. PHD2 guiding software, TheSkyX planetarium or Maxim DL camera control
*'''Force Starting TSX (32 bit) by Voyager:''' If you have trouble with Voyager starting TheSkyX by its normal method (Windows 10/11 DCOM), try checking this box and Voyager will use an alternate method to start TheSkyX. This work only if the application is installed on the default installation folder.
*'''Force Starting TSX (64 bit) by Voyager:''' If you have trouble with Voyager starting TheSky64 by its normal method (Windows 10/11 DCOM), try checking this box and Voyager will use an alternate method to start TheSky64. This work only if the application is installed on the default installation folder.

 
==Logging==
The Logging panel of the Voyager Setup workspace contains settings that control what is saved in the Voyager log file, and for how long:

[[File:Logging-settings.jpg]]

*'''Logs age maximum''': The length of time to store information in Voyager logs in days, after the selected time the oldest log file will be deleted from disk
*'''ASCOM Extend info''': If checked, extended information from ASCOM devices is stored in the log
*'''CCD Peltier Data''': If checked, CCD sensor cooling data is stored in the log
*'''CCD Cooling Deviation''': If checked, CCD sensor deviation from the desired value is stored in the log
*'''PHD2 Debug''': If checked, PHD2 guiding software debug information is stored in the log
*'''GUIDE Data Stream''': If checked, the stream of information received from the guiding software is stored in the log
*'''BROADCAST Msg Send Log''': If checked, broadcast messages are stored in the log . Broadcast message are internal messages between controls that manage the setup
*'''SEQUENCE Abort Expose Screenshot''': If checked, when a sequence is aborted, a screenshot is taken and stored in the log . The screenshot will be stored in the screenshot directory with the other directories of Voyager like the log directory. A reference to the name of the saved screenshot will be added also to the actual log file 

 
==Window and Sound==
The Window and Sound panels of the Voyager Setup workspace contain settings for Voyager's window transparency and sounds:

[[File:Window-and-sound.jpg]]

*'''Window''':
**'''Transparency''': A number between 0 and 30 controlling the transparency of Voyager's Main Windows
*'''Sound''':
**'''On/Off/Only Critical Event''': Controls whether Voyager plays a sound through the PC's sound card - On = always, Off= never, Only Critical Event = only when critical events occur. Critical events are all the events reported in red in the [[Main Window|Monitor]] window

 
==DEBUG==
The DEBUG panel of the Voyager Setup workspace has settings to help with debugging:

[[File:Debug-setup.jpg]]

*'''Emulate Precise Pointing for Simulator''': If checked, Voyager will skip [[Plate Solve Setup#Precision Pointing|precision pointing]] actions and do only the normal goto (slew) actions. This is useful when testing a sequence with a simulator, as most simulators cannot perform plate solves 

 
==ASK BEFORE==
The ASK BEFORE panel of the Voyager Setup workspace has settings controlling whether Voyager confirms various actions before performing them:

[[File:Ask-before.jpg]]

*'''Confirm for OnTheFly GOTO Action''': If checked, Voyager will ask confirmation before performing a goto action from the OnTheFly workspace
*'''Confirm for OnTheFly SEQUENCE Action''': If checked, Voyager will ask confirmation before running a Sequence from the OnTheFly workspace
*'''Confirm for OnTheFly SYNC Action''': If checked, Voyager will ask confirmation before running a Sync action from the OnTheFly workspace
*'''Confirm for Close Voyager Application''': If checked, Voyager will ask confirmation closing down

 
==PATH & FILE==
The PATH panel of the Voyager Setup workspace instructs Voyager where to save images

[[File:Sequence-path.jpg]]

*'''Sequence Path''':
**'''Default''': Voyager saves images in the default location, which will be in your Windows Documents folder: \Documents\Voyager\Sequence\<target name>
**'''Specific''': Click the second radio button and click the folder icon. Browse to the path where you want images saved
**'''Manual Apply''': edit manually or with copy and paste and press Manual Apply button
*'''Sequence File Pattern:'''
**'''Manage:''' press this button to open the FILE PATTERN manager window where you can define rules for sub foldering and file naming of the various kind of sequences in Voyager (not test shot or dragscript FIT file)

== File Pattern Manager ==
Form version 2.2.14j of Voyager users can change the file naming and subfoldering logic of all the kind of Sequences usable in Voyager (Sequence, Mosaic Research & Survey, Array Sequence). Setting about are stored on the profile, different profile can handle different sub foldering and file naming. To open the manager you can press the manage button in the [https://wiki.starkeeper.it/index.php/Voyager_Setup#PATH_.26_FILE FILE & PATH box] of Voyager Setup, tab Voyager.

[[File:FilePatternManager.png]]

Special string starting and ending with $$ chars indicated a key tag (pattern) to be replaced with the related information, more info about each syngle key tag in the pattern list. You can arrange a list of this pattern and combine them with normal chars to obtain a result in file namig reported in the preview.

You can manage also the sub foldering using the / or \ char to separate file naming pattern to a dir pattern, for sure you can add more than one level of sub foldering adding more \ chars. You can use pattern for foldering and/or fixed text.

The are some special commands to allow you to obtain a defaults set of patterns to use, default is something really similar to what Voyager do with the default naming.

{{Note|You cannot apply file pattern rules to the FIT file obtained with Test Shot, plate solving and DragScript Shot.}} {{Note|Default naming is Voyager is the default for each sequence, you must chose the option in each single sequence configuration to enable the file pattern naming}} {{Note|If you use File Pattern sub foldering and naming in a sequence the automation usually done by Voyager to create a folder with the target name will be not more utilized. YOU WILL MUST PROVIDE foldering for Target in your pattern !!}} 
=== Data ===

* '''Sequence File Pattern''': This is the pattern file string saved in the profile, you can edit the string directly writing the $$ tag or text or / char to one or more subfolder. You can also double click on one tag on the Pattern List to add text in the end of Sequence File Pattern field
* '''Pattern Preview:''' this is readonly field where Voyager report the equivalent sub foldering and file naming relative to the file pattern field and a demo data simulated inside the manager. The › char indicates a folder separation

=== Pattern List ===
This grid will contains alphabetical ordered all the $$ tag usable for create a File Pattern, double click on the needed row to copy the Pattern Name to the Sequence File Pattern field.
*'''Pattern Name:''' $$ tag string can be used for compose the File Pattern, case sensitive
* '''Description:''' short description about what kind of data will be replaced to the tag if avalaible

=== Commands ===

* '''Reset to Default CMOS''': replace the actual Sequence File Pattern field with a default pattern specialized to CMOS camera really similar to the sub foldering and file naming used by original Voyager sequence action logic,
* '''Reset to Default CCD''': replace the actual Sequence File Pattern field with a default pattern specialized to CCD/DSLR camera really similar to the sub foldering and file naming used by original Voyager sequence action logic,
* '''Reset to Default CMOS''' '''Advanced''': replace the actual Sequence File Pattern field with a default pattern specialized to CMOS camera really similar to the sub foldering and file naming used by original Voyager sequence action logic, more sub foldering will be added and managed instead of the default CMOS pattern
* '''Reset to Default CCD Advanced''': replace the actual Sequence File Pattern field with a default pattern specialized to CCD/DSLR camera really similar to the sub foldering and file naming used by original Voyager sequence action logic, more sub foldering will be added and managed instead of the default CCD/DSLR pattern
* '''Cancel:''' restore the Sequence File Pattern field to the previuos version before edit begin
* '''Apply:''' apply change saving the Sequence File Pattern field in the actual profile

* '''Exit Manager:''' If you want to exit from the Manager press the X button on the top right corner of the window.

=== Example ===
For a pattern file like this:

<code>'''$$TARGETNAME$$'''\'''$$VOYDATEFOLDER08$$'''\'''$$FILTER$$'''\$$TARGETNAME$$_$$IMAGETYPE$$_$$FILTER$$_$$LABEL$$_</code>

<code>$$EXPOSURETIME$$s_BIN$$BINNING$$_$$SENSORTEMP$$C_A$$ARRAYNODE$$_$$FRAMENR$$_$$VOYDATETIME$$_$$READOUTMODE$$</code>

<code>_$$SPEED$$_RPA$$ROTATORPA$$_$$PIERSIDE$$_F$$ROBOFIREFOCUSERPOS$$</code>

You will obtain a sub foldering and file naming system like this:

<code>'''M31''' › '''2020-12-06''' › '''L''' › M31_LIGHT_L_LABEL_0.0001s_BIN1_-24.9C_A1_0023_20201206_203246_023_8MHZ_HighGain_RPA123.45_W_F30187</code>

where the bolded text is a subfolders. When some tag cannot be replaced with the related data Voyager will put a null space or a "Unknow" text string.

 

==Profiles Auto Backup==
Voyager auto save a backup copy of Profiles Folder in a special Folder called ProfileBackup. See for more info the Voyager Folders structure

[[File:AutobackupProfiles.png]]

*'''Profile Backups age maximum [days]:''' age of old backup max allowed in terms of day
Voyager backup automatically the Profiles folder at each startup and when an update online from Voyager will be started.

Voyager remove the oldest out of agebackup at the startup after a fresh backup of actual profile folder.

==Startup Option==
As of Voyager 2.1.4a, you can choose to hide personal info from the startup form.

[[File:Setup-voyager-startup-221.jpg]]

*'''Hide Personal Info in Startup Form''': If checked, the startup form (splash screen) shown when Voyager starts up will not contain your name or the Voyager serial number - it will look similar to this:
*[[File:Startup-form-no-personal-info.png]]

==Colorblind - Help for Alarm Text==
Allows customization of colors used in Alarm notifications - the normally red text that indicates an error has occurred

[[File:Voyager-colorblind-217c.jpg]]

*Personalized BackColor Monitor (*): Click the Pick Color button and choose a color to use for the background color of the [[Main Window#Monitor Window|Monitor window]].
*Personalized BackColor Settings (*): Click the Pick Color button and choose a color to use for the background color of Alarm (error) text in Setup
*Personalized ForeColor (*): Click the Pick Color button and choose a color to use for the foreground color of Alarm (error) text in both Setup and the Monitor window
*Default Colors: Click to return to the Default Color scheme
{{Note|Changes to any of these color settings requires a Voyager restart to take effect}}

== Moon Avoidance Lorentzian ==
Define a mode to avoid moon based on Lorentzian distribution formula using Distance between moon and object and width of Lorentzian period (default half of the moon period aka 14days).
The distance calculated will be used by RoboTarget Scheduler to define if a target is elegible.

[[File:Immagineergr.png]]

* '''Avoidance Profiles:''' There are 3 profile of distance: broadband for LRGB filters, narrow band and free (low consideration of moon distance). Each of this profile can be edited in terms of parameters of Lorentzian distribution or in terms of altitude for each single Moon Phase.
* '''Manage(*)''': opening the Avoidance windows manager. Be patient, opening take a while (2s to 10s) depends on your PC resources

[[File:Immaginey4y.png]]

* '''A''': profile for Broad Band Filters (LRGB)
* '''B''': profile forNarrow Band Filters
* '''C''': profile Free with very low impact of moon distance
* '''Distance:''' one of the two parameters of the Lorentzian Distribution. Means the distance max used by formula at maximum phase of moon
* '''Width:''' softness of curve far from the 100% moon phase, more is short the width more there will be an accentuated peak with flatness data before the 100% of moon phase. Start using 14 that is also the half of the moon period
* '''Generate table:''' Create automatically the list of moon phase <-> altitude tuple from 0 to 100%
* '''Data Table:''' the list of moon phase <-> altitude tuple from 0 to 100%. You can manual edit the value one by one if you have patience
* '''Chart:''' chart drawing tih the moon phase on the x axis and the minimum distance allowed between target and moon
* '''Reset All:''' By default the value are like in image perfect and balanced for the porpouse of creation (values validated by more than one advanced users). Click here to report all the profiles to the default values
* '''Apply:''' save the changing on Voyager profile file on disk
* '''Close:''' close the windows manager
{{Note|This features is reserved to Voyager Advanced and Full version}}

{{Note|Do not change the default valued if you do not understand what Lorentzian distribution is}}

 
==Other Setup Pages==
<categorytree mode="pages" depth="1">Setup</categorytree>

[[Category:Setup]]
[[Category:All]]
[[Category:Manual|Hn]]

WEB Dashboard Setup

2025-01-04T10:56:08Z

Leonardo: /* Access to Web Dashboard from Internet */

[[File:WdashDemo.jpg|frameless|837x837px]]

 

==Color Coding==
Throughout the Setup workspace, Voyager uses color to indicate the following:

*'''Black''': A normal setting
*Gold or Yellow: Use caution when changing as things may not work well or as expected
*Red: Use extreme care when changing this setting - the wrong value can damage your equipment or the imaging session may fail

==Preliminary Operations to allow Web Dashboard use==
In order to use the Voyager WEB Dashboard it is necessary to proceed with the following configurations:

*Activate the [[Voyager Setup#Application Server|Application Server]] on Voyager
*Always in Voyager [[Voyager Setup#Application Server|Application Server]] flag the voice "Allow Dashboard Service"
*Restart Voyager to apply the changes
*Allow Voyager in OS firewall at prompt first time
*Besure to have configured you firewall (also manually if needed) to forwarding the service to internal/external network

{{Note|Web Dashboard isn't available in DEMO mode.}}
==Access to Web Dashboard from Internet==
You can access to Voyager Web Dashboard using the internet link hosted in Voyager Starkeeper.it official website [http://www.starkeeper.it/wdashinfo/ here] or using the IP address or hostname of the remote PC with Voyager Application Server running if you have activated the [[Voyager Setup#Web Server|Voyager Internal Web Server]]

To allow external access your IP (where Voyager running) must be public , or static with a DynamicDNS system activated. If your IP isdinamyc and under NAT you cannot reach the Web Dashboard, you must change IP policy with your Internet Provider or use a VPN system like OpenVPN, IPVanish or similar.

==Access to Web Dashboard from Internet using Zerotier==
If you need to accesso from Internet to a remote Voyager Application Server, a Voyager Web Server or Voyager Web Dashboard and do not have a public IP you can use the zerotier approach.

Zerotier is a free service for creating distribuited private network over Internet, we have this and work wonderfully, we recommend it. We asked to 2 our users to write a paper about how to configure zerotier from zero to reach a remote observatory:

* [http://www.starkeeper.it/voyager/zerotier2.pdf http://www.starkeeper.it/voyager/zerotier.pdf]
* http://www.starkeeper.it/voyager/zerotier2.pdf 
==Access to Web Dashboard from Internet==
You can access to Voyager Web Dashboard using the internet link hosted in Voyager Starkeeper.it official website [http://www.starkeeper.it/wdashinfo/ here] or using the IP address or hostname of the remote PC with Voyager Application Server running if you have activated the [[Voyager Setup#Web Server|Voyager Internal Web Server]]

==Access to Web Dashboard from local network==
If you are in a private LAN you can access to Voyager Web Dashboard using the internet link hosted in Voyager Starkeeper.it official website [http://www.starkeeper.it/wdashinfo/ here]if Internet is disponible.

If you dont have Internet you must activate the [[Voyager Setup#Web Server|Voyager Internal Web Server]] , restart Voyager, open you browser (Chrome, FireFox, etc) and insert the IP address of the PC hosting the Voyager Application Server.

==How to choose the IP to insert in the Web Dashboard page to connect in==
Some tips on how to choose the IP for connection to dashboard:

*if you are on the same PC where is the Voyager Application Server please just press enter without input anything on IP field (some firewall can exclude this to work, jump to the next point and using IP)
*if you are on the same LAN of the PC Hosting the Voyager Application Server please use the IP listed in the [[Main Window#Application Server|Application Server Monitor Window]] , after starting Voyager you will see a list of IP addresses like in image. The right one depends on which LAN your client PC are (use from start button in windows the execute function, type cmd and press enter, type ipconfig and then press enter, a list of your PC IP will be showed, choose the class of IP matching the Voyager Application Server IP in the list)
**[[File:ASMonitorWIP.png|frameless|575x575px]]
**If for example your PC client have IP 192.168.1.108 please insert in the web dashboard IP field the IP 192.168.1.106
**you can also use the name of the Voyager Application Server PC if this is allowed from your network router protocol

==Secure the Communications between Voyager and Web Dashboard==
Actually the communication protocol is in clear, please using a VPN connection if you want to secure access and data exchange.

This is highly recommended if you use for a remote observatory. More about security will be deployed when Web Dashboard will exit from beta period.

==Beta Running and Disclaimer==
Also if Web Dashboard is released some months ago and are really stable we are decide to running in beta version.

For each questions and issues please contact us using the official website at [https://software.starkeeper.it Starkeeper.it].

Do not sharing whit everyone data access information and IP address.

== User Manual ==
https://www.starkeeper.it/wdash/doc/WDashb_Doc_1_0_14_def.pdf
 

==Other Setup Pages==
<categorytree mode="pages" depth="1">Setup</categorytree>
[[Category:Setup]]
[[Category:All]]
[[Category:Manual|Hk]]

DragScript Flow of Control

2024-12-01T20:21:59Z

Leonardo: /* Action Results: */

These DragScript elements control the flow of execution through your script. You can use the [[DragScript#DragScript Simulator|DragScript Simulator]] to test how control will flow when the DragScript actions complete with OK, ERROR or TIMEOUT status, and when Emergency Suspend, Resume and Exit events happen.

==Variables==
DragScript has several variable types: counters (integers), string variables and decimal numbers. They must be declared with the Counter, String or Decimal Number actions before they can be used. You can set and change their values, and then make decisions to execute DragScript actions based on their value. For example, you may build a script that runs from zero to ten sequences based on the value of a counter variable you set at the start of the script.

[[File:Dragscript-variables1.png]]

==='''Type'''===

*'''Counter''': Declare a counter (integer) variable and give it an initial value. You must declare a variable before using it

[[File:Dragscript-counter.png]]

*'''Label''': The name for this counter variable. There are no restrictions on length or legal characters, so just use something that makes sense for your control flow
*'''Init Value''': Initial value for the counter. Must be an integer between -2,000,000,000 and +2,000,000,000
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 

*'''String''': Declare a string variable and give it an initial value. You must declare a variable before using it

[[File:Dragscript-string.png]]

*'''Label''': The name for this string variable
*'''Init Value''': Initial value for the string
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 

*'''Decimal Number''': Declare a decimal number variable and give it an initial value. You must declare a variable before using it

[[File:Decimal-number.png]]

*'''Label''': The name for this decimal number variable
*'''Init Value''': Initial value for the decimal number - must be between the limits shown in the dialog box
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 

===Manage===

*'''Update''' '''Counter''': Update the value of a counter variable:

[[File:Dragscript-update-counter.png]]

*'''Counter''': Select the counter to update from the drop-down list. Counter variables must be declared with a Counter DragScript action before they can be updated
*'''Update Type''':
**'''Set to''': If selected, set the counter variable to the value in the Update Value field
**'''Offset by''': If selected, add the value in the Update Value field to the counter. The Update Value field can be negative or positive.
*'''Update Value''': A negative or positive integer value to either set the counter variable to or offset the counter variable by
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Update String''': Update the value of a string variable:

[[File:Dragscript-update-string.png]]

*'''String''': Select the string variable to update from the drop-down list
*'''Update Value''': Enter the new value for the string variable
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Update Decimal Number''': Update the value of a decimal number

[[File:Update-decimal-number.png]]

*'''Decimal Number''': Select the decimal number variable to update from the drop-down list
*'''Update Type''':
**'''Set to''': Set the decimal number value to the number in the Update Value field
**'''Offset by''': Add the +/- number in the Update Value field to the current value of the decimal number
*'''Update Value''': Enter the new value for the decimal number variable
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

* '''Update Decimal Number from Camera Temperature:''' Set the value of a decimal number from the temperature reported from Camera Driver:
* [[File:UpdateCameraTemp.png]]

* '''Decimal Number''': Select the decimal number variable to update from the drop-down list
* '''OK''': Save changes and close the window
* '''Cancel''': Discard changes and close the window 

*'''Update Decimal Number from Observing Conditions:''' Set the value of a decimal number from the observing conditions returned from I/O cards via Viking or from an ASCOM Observing Conditions driver:

[[File:Update-decimal-from-condx.png]]

*'''Decimal Number''': Select the decimal number variable to update from the drop-down list
*'''Observing Condition''': Select the observing condition whose value should be placed into the decimal number. These values come from [[Viking Setup|Viking]], a companion product from Starkeeper.it or from an ASCOM Observing Conditions driver
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''Update Decimal from Unix TimeStamp GMT:''' Set the value of a decimal number from the UNIX TimeStamp GMT based (seconds from 1/1/1970 UTC 0:0:0

[[File:Immaginergbrbrb.png]]

*'''Decimal Number''': Select the decimal number variable to update from the drop-down list
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Update Decimal Number from Focuser Temperature''': Set the value of a decimal number from the temperature returned by the focuser or auto-focus system

[[File:Update-decimal-from-focus-temp.png]]

*'''Decimal Number''': Select the decimal number variable to update from the drop-down list
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Update Decimal Number with Autofocus HFD''': Set the value of a decimal number with the final HFD (Half Flux Diameter) value from the last autofocus operation

[[File:Update-decimal-hfd.png]]

*'''Decimal Number''': Select the decimal number variable to update from the drop-down list
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window {{Note|At this time only RoboFire LocalField, RoboStar, and FocusMax return the HFD value - if you use a different autofocus routine, the HFD is not available}}

 

*'''Update Decimal from Focuser Position''': Set the value of a decimal number from the actual position returned by the RoboFire focuser

[[File:Update-decimal-from-focus-temp.png]]

*'''Decimal Number''': Select the decimal number variable to update from the drop-down list
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Update Decimal from Solved PA''': Set the value of a decimal number from the last solved PA returned by a Plate or Blind Solving action

[[File:UpdataFromPA.png]]

*'''Decimal Number''': Select the decimal number variable to update from the drop-down list
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''Update Decimal from Rotator PA''': Set the value of a decimal number from the Rotator PA returned by Rotator driver

[[File:UpdateRotPA.png]]

*'''Decimal Number''': Select the decimal number variable to update from the drop-down list
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Multiply Decimal Number''': Multiply a decimal number variable for the value in another variable of type counter or decimal or by direct value, the result will be stored in replace of actual value

[[File:DSMultiplyDecNum.png]]

*'''Decimal Number:''' Select the decimal number variable to multiply and update
*'''Multiply by Decimal Variable:''' Select the decimal number variable to use for multiply
*'''Multiply by Counter Variable:''' Select the counter variable to use for multiply
*'''Multiply by Value:''' Select the direct value to use for multipy
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

* '''Divide Decimal Number''': Divide a decimal number variable for the value in another variable of type counter or decimal or by direct value, the result will be stored in replace of actual value[[File:Immagineerfegwegwewegweg.png]]
** '''Decimal Number:''' Select the decimal number variable to divide and update
**'''Divide by Decimal Variable:''' Select the decimal number variable to use for divide
**'''Divide by Counter Variable:''' Select the counter variable to use for divide
**'''Divide by Value:''' Select the direct value to use for divide
**'''OK''': Save changes and close the window
**'''Cancel''': Discard changes and close the window

*'''Add to Decimal Number''': Add a decimal number variable for the value in another variable of type counter or decimal or by direct value, the result will be stored in replace of actual value[[File:Immaginevpomebmob.png]]
** '''Decimal Number:''' Select the decimal number variable to add and update
**'''Add by Decimal Variable:''' Select the decimal number variable to use for add
**'''Add by Counter Variable:''' Select the counter variable to use for add
**'''Add by Value:''' Select the direct value to use for add
**'''OK''': Save changes and close the window
**'''Cancel''': Discard changes and close the window

* '''Subtract to Decimal Number''': Subtract a decimal number variable for the value in another variable of type counter or decimal or by direct value, the result will be stored in replace of actual value[[File:Immagineiloiliolio.png]]
** '''Decimal Number:''' Select the decimal number variable to subtract and update
**'''Subtract by Decimal Variable:''' Select the decimal number variable to use for subtract
**'''Subtract by Counter Variable:''' Select the counter variable to use for subtract
**'''Subtract by Value:''' Select the direct value to use for subtract
**'''OK''': Save changes and close the window
**'''Cancel''': Discard changes and close the window

* '''Add to Counter''': Add a counter variable for the value in another variable of type counter or decimal or by direct value, the result will be stored in replace of actual value[[File:Immaginetntynty.png]]
** '''Counter:''' Select the counter variable to add and update
**'''Add Decimal Variable:''' Select the decimal number variable to use for add
**'''Add Counter Variable:''' Select the counter variable to use for add
**'''Add Value:''' Select the direct value to use for add
**'''OK''': Save changes and close the window
**'''Cancel''': Discard changes and close the window

*'''Subtract to Counter''': Subtract a counter variable for the value in another variable of type counter or decimal or by direct value, the result will be stored in replace of actual value[[File:Immaginedfdfbdf.png]]
** '''Counter:''' Select the counter variable to subtract and update
**'''Subtract Decimal Variable:''' Select the decimal number variable to use for subtract
**'''Subtract Counter Variable:''' Select the counter variable to use for subtract
**'''Subtract Value:''' Select the direct value to use for subtract
**'''OK''': Save changes and close the window
**'''Cancel''': Discard changes and close the window

==Jumps==
Jumps are used to goto a specified block of the DragScript. You can jump to the Start, End or a named Block.

[[File:Dragscript-jumps.png]]

*'''Goto Start''': Jump to the Start block of the script
*'''Goto Block''': Jump to a named block in the script

[[File:Dragscript-block-goto.png]]

*'''Block''': Select the named from the drop-down list, or type in the name of a block
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Goto End''': Jump to the End block of the script

==Repeats==
Repeats are used to execute a DragScript block a specified number of times, or until a specific time, or until astronomical night ends.

Repeats must be placed inside a block (note: Script: is a special block that contains the entire script.

If the result of evaluating a Repeat is to repeat the block, control returns to the block statement that contains the repeat.

[[File:Dragscript-repeats.png]]

*'''Repeat Block for n Times''': Repeat the containing block a specified number of times

[[File:Dragscript-repeat-block.png]]

*'''Times''': Number of times to repeat this block
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 

*'''Repeat Current Block Until Time''': Repeat the contained block until the specified time:

[[File:Dragscript-until-time.png]]

*'''Time''': Repeat the current block until this time
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 

*'''Repeat Block Until Astronomical/Nautical/Civil Night End''':

[[File:Dragscript-repeat-until-night-end.png]]

*'''Get Latitude and Longitude from Mount''': Retrieve the current latitude and longitude from the connected mount, which must support this command. This location is used, along with the current date, to determine the time that astronomical/nautical/civil night ends
*'''Use the Latitude and Longitude indicated below''': Specify your current latitude and longitude in the fields below. This location is used, along with the current date, to determine the time that astronomical/nautical/civil night ends
*'''Offset''': Time in HH MM SS
**'''Offset Before''': If selected, repeat the block until this amount of time before astronomical/nautical/civil night ends
**'''Offset After''': If selected, repeat the block this amount of time after astronomical/nautical/civil night ends
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 
**

{{Note|The time will be considered to have been reached if it is within 12 hours of the current time when the check is performed. E.g., if we set a repeat until 05:00, if it is 23:30 the repeat will be done since 23:30 is more than 12 hours in the future and less than 12 hours in the past, relative to 05:00. If it is 11:00, the repeat will be skipped, since 11:00 is later than 05:00 and more than 12 hours in the past.}} 
==Decisions==
Decisions control the flow of your DragScript based on the results of an action (OK, ERROR, TIMEOUT), operating conditions (current time, date or target altitude), or the value of a variable.

{{Note|A Decision element will create a new indent level in your DragScript. Drag new elements and drop them on the Decision element, or copy and paste them to it, to have their execution controlled by the result of the Decision}}

[[File:Dragscript-decisions-2.1.7s.jpg]]

==='''Action Results''':===
Do the actions at the indent level created by the Decision block based on the results of the action preceding the decision

**'''IF OK''': Do the actions following this statement if the result of the previous action was OK - meaning the action was successful
**'''IF ERROR''': Do the actions following this statement if the result of the previous action was ERROR - meaning the action failed
**'''IF TIMEOUT''': Do the actions following this statement if the result of the previous action was a TIMEOUT - meaning the action reached a specified timeout value without succeeding
**'''IF SKIPPED:''' Do the actions following this statement if the skipped status of the previuos action was SKIPPED - meaning the action not generate ERROR or finish OK just is SKIPPED because some constraints isnìt possible to match. At now only the Sequence Action use the SKIPPED status if time wait or time end or one of the constraints in azimuth, hour agle, alitute was thrown 

==='''Operating Conditions:'''===
Do the actions at the indent level created by the Decision block based on the time, date or target altitude

*'''DO IF ALTITUDE''': Do the actions if a target specified by RA and DEC coordinates has risen above or set below a specified altitude:

[[File:Dragscript-do-if-altitude.png]]

*'''RA Target J2000''': RA coordinates of the object you want to reach the Reference Altitude in HH MM SS or HH MM SS.sss
*'''DEC Target J2000''': DEC coordinates of the object you want to reach the Reference Altitude in DD MM SS or DD MM SS.sss
*'''Reference Altitude''': Altitude to reach in degrees
*'''Do If Actual Altitude GREATER than or EQUAL (>=) to reference''': Do the actions if the target has reached or risen above the reference altitude
*'''Do If Actual Altitude LOWER than or EQUAL (>=) to reference''': Do the actions if the target has reached or set below the reference altitude
*'''RoboClip:''' load RA and DEC from RoboClip catalog
*'''Coords From Sequence:''' load RA and DEC from a sequence file
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''DO IF ALTITUDE DYNAMIC TARGET''': Do the actions if a Dynamic Target has risen above or set below a specified altitude (RA/DEC will be calculated in realtime using RoboOrbits):

[[File:Immaginettg.png]]

* '''Comet :''' open the Comet Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
* '''Asteroid :''' open the Asteroid Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
* '''Planet:''' open the Planet Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
* '''Object Name :''' Read-only name of the Dynamic Target, coming from the search
* '''Object Key :''' Read-only key (code/number) of the Dynamic Target, coming from the search
* '''Object Dynamic Type :''' Read-only type of the Dynamic Target, coming from the search
*'''Reference Altitude''': Altitude to reach in degrees
*'''Do If Actual Altitude GREATER than or EQUAL (>=) to reference''': Do the actions if the target has reached or risen above the reference altitude
*'''Do If Actual Altitude LOWER than or EQUAL (>=) to reference''': Do the actions if the target has reached or set below the reference altitude
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''DO IF ALTITUDE BETWEEN:''' Do the actions if the altitude of a target specified by RA and DEC coordinates is between the '''Start''' and '''End''' values

[[File:Do-if-altitude-between.jpg]]

*'''RA Target J2000''': RA coordinates of the object you want to reach the Reference Altitude in HH MM SS or HH MM SS.sss
*'''DEC Target J2000''': DEC coordinates of the object you want to reach the Reference Altitude in DD MM SS or DD MM SS.sss
*'''Start and End:''' Do the actions if the specified target's altitude is greater than or equal to the '''Start''' value and less than or equal to the '''End''' value in decimal degrees
*'''RoboClip:''' load RA and DEC from RoboClip catalog
*'''Coords From Sequence:''' load RA and DEC from a sequence file
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''DO IF ALTITUDE BETWEEN DYNAMIC TARGET :''' Do the actions if the altitude of a Dynamic Target is between the '''Start''' and '''End''' values (RA/DEC will be calculated in realtime using RoboOrbits):

[[File:Immagineefe.png]]

*'''Comet :''' open the Comet Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
*'''Asteroid :''' open the Asteroid Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
*'''Planet:''' open the Planet Finder in RoboOrbits, see more here
*'''Object Name :''' Read-only name of the Dynamic Target, coming from the search
*'''Object Key :''' Read-only key (code/number) of the Dynamic Target, coming from the search
*'''Object Dynamic Type :''' Read-only type of the Dynamic Target, coming from the search
*'''Start and End:''' Do the actions if the specified target's altitude is greater than or equal to the '''Start''' value and less than or equal to the '''End''' value in decimal degrees
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''DO IF AZIMUTH BETWEEN:''' Do the actions if the azimuth of a target specified by RA and DEC coordinates is between the '''Start''' and '''End''' values and the Altitude of the Target is above the minimum Altitude for slew set up in Voyager Mount setting (default is 0°)

[[File:Immagineyjtyj.png]]

*'''RA Target J2000''': RA coordinates of the object you want to reach the Reference Altitude in HH MM SS or HH MM SS.sss
*'''DEC Target J2000''': DEC coordinates of the object you want to reach the Reference Altitude in DD MM SS or DD MM SS.sss
*'''Start and End:''' Do the actions if the specified target's azimuth is greater than or equal to the '''Start''' value and less than or equal to the '''End''' value in decimal degrees. Also the Altitude of the target must be above the minimum for a slew like set tup in Voyager Mount setting (default is 0°)
*'''RoboClip:''' load RA and DEC from RoboClip catalog
*'''Coords From Sequence:''' load RA and DEC from a sequence file
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

{{Note|Remember that a Target can be in the right azimuth interval but can be upside down wiht negtive altitude. DO IF will be not executed if altitude of target are under the minimum altitude value accepted for a slew in Voyager mount setting}}

 
*'''DO IF AZIMUTH BETWEEN DYNAMIC TARGET :''' Do the actions if the azimuth of a Dynamic Target is between the '''Start''' and '''End''' values and the Altitude of the Target is above the minimum Altitude for slew set up in Voyager Mount setting (default is 0°) (RA/DEC will be calculated in realtime using RoboOrbits):

[[File:DSDoIfAzimuth.png]]

*'''Comet :''' open the Comet Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
*'''Asteroid :''' open the Asteroid Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
*'''Planet:''' open the Planet Finder in RoboOrbits, see more here
*'''Object Name :''' Read-only name of the Dynamic Target, coming from the search
*'''Object Key :''' Read-only key (code/number) of the Dynamic Target, coming from the search
*'''Object Dynamic Type :''' Read-only type of the Dynamic Target, coming from the search
*'''Start and End:''' Do the actions if the specified target's azimuth is greater than or equal to the '''Start''' value and less than or equal to the '''End''' value in decimal degrees. Also the Altitude of the target must be above the minimum for a slew like set tup in Voyager Mount setting (default is 0°)
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''DO IF HA BETWEEN:''' Do the actions if the hour angle of the target (hours difference from the meridian) is between the specified start and end amounts [[File:Dragscript-doifha-2.1.7s.jpg]]
*'''RA Target J2000''': RA coordinates of the object whose hour angle we are testing, in HH MM SS or HH MM SS.sss
*'''DEC Target J2000''': DEC coordinates of the object whose hour angle we are testing, in DD MM SS or DD MM SS.sss
*'''Start and End:''' Do the actions if the specified target's HA (hour angle) is greater than or equal to the '''Start''' value and less than or equal to the '''End''' value in decimal hours. Note the values can be positive (after the meridian) or negative (before the meridian). The start to end can be both negative, both positive, or the start can be negative and the end can be positive. '''In all cases, the value must increase from start to end.'''
*'''RoboClip:''' load RA and DEC from RoboClip catalog
*'''Coords From Sequence:''' load RA and DEC from a sequence file
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 

*'''DO IF HA BETWEEN DYNAMIC TARGET :''' Do the actions if the hour angle of the Dynamic target (hours difference from the meridian) is between the specified start and end amounts (RA/DEC will be calculated in realtime using RoboOrbits):
*[[File:Immaginesf.png]]
*'''Comet :''' open the Comet Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
*'''Asteroid :''' open the Asteroid Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
*'''Object Name :''' Read-only name of the Dynamic Target, coming from the search
*'''Object Key :''' Read-only key (code/number) of the Dynamic Target, coming from the search
*'''Object Dynamic Type :''' Read-only type of the Dynamic Target, coming from the search
*'''Start and End:''' Do the actions if the specified target's HA (hour angle) is greater than or equal to the '''Start''' value and less than or equal to the '''End''' value in decimal hours. Note the values can be positive (after the meridian) or negative (before the meridian). The start to end can be both negative, both positive, or the start can be negative and the end can be positive. '''In all cases, the value must increase from start to end.'''
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''DO IF TIME BETWEEN''': Do the actions if the time is between the specified start and end times

[[File:Dragscript-do-if-time.png]]

*'''Start''': Beginning time of interval within which to do the following actions
*'''End''': End time of interval within which to do the following actions
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''DO IF DATE BETWEEN''': Do the actions at the indent level created by the DO statement if the date is between the start and end dates:

[[File:Dragscript-do-if-date.png]]

*'''Start''': Start date of the interval
*'''End''': End date of the interval
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''DO IF SQM''': Do the actions at the indent level created by the DO statement if the SQM value readed from control or Observing conditions is between the start and end dates:

[[File:DOIFSQM.png]]

*'''Reference Sky Quality''': reference value of Sky Quality to check
*'''Do If Actual value GREATER than or EQUAL [>=] to reference''': execute what is inside DO IF if the actual value >= that the reference value
*'''Do If Actual value LOWER than or EQUAL [<=] to reference''': execute what is inside DO IF if the actual value <= that the reference value
*'''Default''': use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''DO IF FOCAL LENGTH''': Do the actions at the indent level created by the DO statement if the FOCAL LENGTH readed from actual profile (Setup->Camera) is >=, <= or equal to reference value:

[[File:DoIfFocalLengthBlock.jpg]]

*'''Reference Focal Length''': reference value of Telescope Focal Length to check
*'''Do If Focal Length GREATER than or EQUAL [>=] to reference''': execute what is inside DO IF if the actual value >= that the reference value
*'''Do If Focal Length LOWER than or EQUAL [<=] to reference''': execute what is inside DO IF if the actual value <= that the reference value
*'''Do If Focal Length EQUAL [=] to reference''': execute what is inside DO IF if the actual value = that the reference value
*'''Default''': use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''DO IF DOME/ROOF OPEN''': Do the actions at the indent level created by the DO statement if the DOME/ROOF is opened
*'''DO IF DOME/ROOF CLOSED''': Do the actions at the indent level created by the DO statement if the DOME/ROOF is closed

{{Note|Status of DOME/ROOF will be read from the DOME Control configured in Voyager. This control is not absolutely reliable at 100%. Voyager cannot responding in anycase and any mode on damage derived from use of this conditional blocks. Please instead use the I/O card system with Viking management and physycal sensors to check the real status of your dome/roof.}}
*'''DO IF DISTRIBUITED SAFE END''': Wait the end of the night like defined in the Distribuited Safe block configuration. this is a features of the [https://software.starkeeper.it/voyager-plugins/ Distribuited Emergency plugin] dedicated to multi telscope in a single dome sharing emergency events
*'''DO IF EVEN DAY''': Decision block, true if the day of the month is an even number. Useful for example to do flat/calibration fit in different sets.
*'''DO IF ODD DAY:''' Decision block, true if the day of the month is an odd number. Useful for example to do flat/calibration fit in different sets.
*'''DO IF DAY OF WEEK:''' Decision block, true if the day of the week is one of those indicated in configuration (one or more day can be selected). Useful for example to do flat/calibration fit in different sets. Or doing some special task for copy file or etc etc
**[[File:Immaginewerwr.png]]

* '''DO IF PIER SIDE:''' Decision block, true if the pier side of the mount (what is reported by the connected driver) is equal to the parameter selected
**[[File:Immagineevveerv.png]]
** Pier West: mount before the meridian (or meridian passed but flip do not done)
** Pier East: mount after the meridian(meridian crossed and flip done)
* '''DO IF MOON PHASE:''' Decision Block, true if the moon phase >= or <=, depends on the selected filter to apply, of the value edited. To calculate the moon phase the mount must be connect or you must select manual data and input the LAT and LONG
** [[File:Immagineefefwefwevvwev.png]]
** '''Moon Phase:''' percentage value for reference
** '''Do If Actual value is GREATER than or EQUAL [>=] to reference :''' itself explained
** '''Do If Actual value is LOWERthan or EQUAL [<=] to reference :''' itself explained
** '''Get Latitude and Longitude from Mount (the Setup must be connected''' : itself explained
** '''Use Latitude and Longitude indicated below'''
*** '''Latitude''': Latitude to use
*** '''Longitude:''' Longitude to use
*** '''Default :''' restore default settings
*** '''Cancel:''' close the window without doing anything, data change will be lost
*** '''OK:''' accept data and save in block configuration
**{{Note|This block is only available and usable only if you have installed a Voyager Advanced License or a Voyager Full License. Other an error will be generate during the DragScript Execution}}
==='''Voyager Environment:'''===
Do the actions at the indent level created by the Decision block based on the Voyager internal status

*'''DO IF SETUP CONNECTED''': Do the actions if Voyager Setup is connected (from Startup menù or by DragScript connect block)
*'''DO IF SETUP DISCONNECTED''': Do the actions if Voyager Setup is not connected (from Startup menù or by DragScript disconnect block)

==='''Variable Check'''===
Do the actions at the indent level created by the DO IF statement based on the value of a variable. Variables must be declared before they can be tested in a DO IF statement

[[File:Decisions-variable-check.png]]
 

*'''DO IF COUNTER VALUE''': Check the value of a counter (integer) variable and do the following actions if the value of the counter meets the specified criteria:

[[File:Dragscript-do-if-counter.png]]

*'''Label''': Choose the counter variable to test from the drop-down list
*'''is Lower than''': Do the following actions if the selected counter value is less than the number in the counter field
*'''is Lower than or Equal to''': Do the following actions if the selected counter value is less than or equal to the number in the counter field
*'''is Equal to''': Do the following actions if the selected counter value is equal to the number in the counter field
*'''is Greater or Equal to:''' Do the following actions if the selected counter value is greater than or equal to the number in the counter field
*'''is Greater than:''' Do the following actions if the selected counter value is greater than the number in the counter field
*'''is Between:''' Do the following actions if the selected counter value is between the values in the two counter fields (greater than or equal to the left value AND less than or equal to the right field)
*'''is Not Equal''' to: Do the following actions if the selected counter value is not equal to the number in the counter field
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

**'''DO IF STRING VALUE''': Do the actions at the indent level created by the DO IF statement if a string variable is equal to, not equal to, or contains a specified string:

[[File:Dragscript-do-if-string.png]]

*'''Label''': Choose the string variable to test from the drop-down list
*'''is Equal to''': Do the following actions if the selected string value is equal to the specified string
*'''is Not Equal to''': Do the following actions if the selected string value is not equal to the specified string
*'''Contains''': Do the following actions if the selected string value contains the specified string
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 {{Note|String comparisons are case sensitive, i.e. TargetName is not equal to targetname}} 

*'''DO IF DECIMAL VALUE''': Do the actions at the indent level created by the DO IF statement if the value of the decimal number meets the specified criteria:

[[File:Do-if-decimal-value.png]]

*'''Label''': Choose the counter variable to test from the drop-down list
*'''is Lower than''': Do the following actions if the selected decimal number value is less than the number in the decimal number field
*'''is Lower than or Equal to''': Do the following actions if the selected decimal number value is less than or equal to the number in the decimal number field
*'''is Equal to''': Do the following actions if the selected decimal number value is equal to the number in the counter field
*'''is Greater or Equal to:''' Do the following actions if the selected decimal number value is greater than or equal to the number in the decimal number field
*'''is Greater than:''' Do the following actions if the selected decimal number value is greater than the number in the decimal number field
*'''is Between:''' Do the following actions if the selected decimal number value is between the values in the two decimal number fields (greater than or equal to the left value AND less than or equal to the right field)
*'''is Not Equal''' to: Do the following actions if the selected decimal number value is not equal to the number in the decimal number field
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

* '''DO IF COUNTER VALUE (Extended)''': Check the value of a counter (integer) variable and do the following actions if the value of the counter meets the specified criteria extended to a value, counter or decimal value:
** [[File:Immagineerfer.png]]
*** '''Counter''': Choose the counter variable to test from the drop-down list
***'''is Lower than''': Do the following actions if the selected counter value is less than the number in the counter field
***'''is Lower than or Equal to''': Do the following actions if the selected counter value is less than or equal to the number in the value field , counter variable or decimal variable
***'''is Equal to''': Do the following actions if the selected counter value is equal to the number in the value field , counter variable or decimal variable
***'''is Greater or Equal to:''' Do the following actions if the selected counter value is greater than or equal to the number in the value field , counter variable or decimal variable
***'''is Greater than:''' Do the following actions if the selected counter value is greater than the number in the value field , counter variable or decimal variable
***'''is Between:''' Do the following actions if the selected counter value is between the values in the value field , counter variable or decimal variable (greater than or equal to the left value AND less than or equal to the right field)
***'''is Not Equal''' to: Do the following actions if the selected counter value is not equal to the number in the value field , counter variable or decimal variable
***'''OK''': Save changes and close the window
***'''Cancel''': Discard changes and close the window 

'''DO IF DECIMAL VALUE (Extended)''': Check the value of a counter (integer) variable and do the following actions if the value of the counter meets the specified criteria extended to a value, counter or decimal value:
* [[File:Immaginee3fer.png]]
**'''Decimal Number''': Choose the decimal variable to test from the drop-down list
**'''is Lower than''': Do the following actions if the selected decimal value is less than the number in the counter field
**'''is Lower than or Equal to''': Do the following actions if the selected decimal value is less than or equal to the number in the value field , counter variable or decimal variable
**'''is Equal to''': Do the following actions if the selected decimal value is equal to the number in the value field , counter variable or decimal variable
**'''is Greater or Equal to:''' Do the following actions if the selected decimal value is greater than or equal to the number in the value field , counter variable or decimal variable
**'''is Greater than:''' Do the following actions if the selected decimal value is greater than the number in the value field , counter variable or decimal variable
**'''is Between:''' Do the following actions if the selected decimal value is between the values in the value field , counter variable or decimal variable (greater than or equal to the left value AND less than or equal to the right field)
**'''is Not Equal''' to: Do the following actions if the selected decimal value is not equal to the number in the value field , counter variable or decimal variable
**'''OK''': Save changes and close the window
**'''Cancel''': Discard changes and close the window

==Events==
DragScript execution can be suspended, terminated (exited) and resumed based on the occurrence of Emergency Exit, Emergency Suspend and Emergency Resume events.

The most common use of Events is together with a weather monitoring system, as configured in [[Weather Setup]]. You can specify at a detailed level which events should cause DragScript execution to SUSPEND (such as overcast clouds), EXIT (such as rain), or RESUME (such as clouds moving out so it becomes clear again).

In addition to weather events, you can raise Emergency Exit, Emergency Suspend and Emergency Resume events at any point in your DragScript.

When an Event is raised, control flow goes immediately to the appropriate block (Exit, Suspend or Resume) in the Events block of your DragScript. Create those blocks by dragging elements from the Events: Manage list.

[[File:Dragscript-events.png]]

==='''Manage'''===
See the [[DragScript Examples#Emergency Exit|DragScript Examples]] section to see how these blocks work in a DragScript.

*'''Emergency Exit''': Drag this element to the Events block of your DragScript. Then drag the actions you wish to take place when an Emergency Exit event is raised. For example, stop tracking, stop guiding, park your mount, and close the observatory roof
*'''Emergency Suspend''': Drag this element to the Events block of your DragScript. Then drag the actions you wish to take place when an Emergency Suspend event is raised. For example, stop tracking and stop guiding

[[File:Dragscript-suspend-2.png]]

*'''Wait Resume until absolute time''': If the time specified in HH MM SS is reached without an Emergency Resume event being raised, perform the action selected from the radio buttons in this dialog window
*'''Wait Resume for a time interval of:''' If the time period specified in HH MM SS elapses without an Emergency Resume event being raised, perform the action selected from the radio buttons in this dialog window
*'''Wait Resume until end of Astronomical Night''': If the end of Astronomical Night arrives without an Emergency Resume event being raised, perform the action selected from the radio buttons in this dialog window
*'''Wait Resume until end of Nautical Night''' : If the end of Nautical Night arrives without an Emergency Resume event being raised, perform the action selected from the radio buttons in this dialog window
*'''Wait Resume until end of Civil Night''': If the end of Civil Night arrives without an Emergency Resume event being raised, perform the action selected from the radio buttons in this dialog window
*{{Note|the various Wait Resume until end of xxxx Nights needed the specification on how to retrieve the data for the night (from Mount or by manual latitude and longitude) . }}
** '''Get Latitude and Longitude from Mount''': Retrieve the current latitude and longitude from the connected mount, which must support this command. This location is used, along with the current date, to determine the time that astronomical night begins and end. SETUP MUST BE CONNECTED TO WORK !
** '''Use the Latitude and Longitude indicated below''': Specify your current latitude and longitude in the fields below. This location is used, along with the current date, to determine the time that astronomical night begins and end
**
*'''Wait Resume Until Distribuited SAFE End [Distribuited Emergency Plugin Needed]:''' if selected Voyager will wait for resume according the SAFE END procedure of the Distribuited Emergency Plugin. A dedicated plugin for multi pier in a single building is needed https://software.starkeeper.it/voyager-plugins/
*'''On Resume Timeout End DragScript''': If the time specified above is reached without an Emergency Resume event occurring, end the DragScript
*'''On Resume Timeout Exec Emergency Exit Event''': If the time specified above is reached without an Emergency Resume event occurring, raise an Emergency Exit event
*'''On Resume Timeout Restart DragScript''': If the time specified above is reached without an Emergency Resume event occurring, Voyager will restart the DragScript form beginneng like a new running
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''Emergency Resume''': Execute these actions when an Emergency Resume event is raised. For example, start tracking and start guiding 

==='''Raise'''===
Raise an Emergency Exit, Suspend or Resume event

*'''Raise Emergency Exit Event''': Raise the Emergency Exit event. Execution of the DragScript will go immediately to the Emergency Exit block in the Events block
*'''Raise Emergency Suspend Event''': Raise the Emergency Suspend event. Execution of the DragScript will go immediately to the Emergency Suspend block in the Events block
*'''Raise Emergency Resume Event''': Raise the Emergency Resume event. Execution of the DragScript will go immediately to the Emergency Resume block in the Events block

==='''Remote'''===
Block for management of Distributed [https://wiki.starkeeper.it/index.php/Distributed_Emergency Distributed Emergency]

*'''Set Distributed Emergency Status''': Update overriding the internal Distributed Emergency Status for the Voyager Client connected to the selected value
**[[File:Des1.png]]
*'''Distributed Safe''': Distributed Safe wait the night like configured and in the night wait to have a Safe condition from the Emergency Event System (in Voyager is Weather, Safety Monitor, Viking I/O). If night is recognized and safe condition is true DragScript will exit from this block with OK result. If timeout is reached waiting DragScript will exit from this block with a TIMEOUT result. In case of error during waiting DragScript will exit with ERROR result. Checking the exit of block user can decide if inform all the client of a SAFE condition using the SET DISTRIBUTED EMERGENCY STATUS or restart the Master DragScript to wait for better conditions (same night or next night is automatically decided from DragScript). This block is usually associated and work only if you using the [https://wiki.starkeeper.it/index.php/Distributed_Emergency Distributed Emergency] plugin. Right and only place where to use is the Voyager MASTER of plugin where information is processed and emergency events checked.
**'''Important Note!''' Distributed Safe Cannot be used inside the Event Manager (Exit, Suspend, Resume)
***[[File:DES2.png]]
***'''NIGHT Configuration:''' data necessary to calculate the start and end interval of the actual night
****'''Night DATA:''' data about location of observatory
*****Latitude: Latitude of the Mount
*****Longitude: Longitude of the Mount
****'''Night TYPE:''' type of night to calculate. Astronomical, Nautical or Civil
****'''Night START OFFSET:''' apply an offset to the time start of the night
*****Offset Before: offset before the start in hours, minutes and seconds
*****Offset After: offset after the start in hours, minutes and seconds
****'''Night END OFFSET:''' apply an offset to the time end of the night
*****Offset Before: offset before the end in hours, minutes and seconds
*****Offset After: offset after the end in hours, minutes and seconds
****'''EVENT CHECK options:''' with this option you can decide to remove from processing status of SAFE some kind of events that will be ignored (event in any case are disable during the wait safe action)
*****'''Check Emergency Exit Status in SAFE status calculation:''' if unchecked the condition that throw an Emergency Status will be ignored in calculation of SAFE Staus . ATTENTION !! this is a way really dangerous for your setup .. use only if you want to wait safe in particular condition , particular timing and for particular tasks
*****'''Check Emergency SUSPEND Status in SAFE status calculation:''' if unchecked the condition that throw an Emergency Status will be ignored in calculation of SAFE Staus . ATTENTION !! this could be a way really dangerous for your setup .. use only if you want to wait safe in particular condition , particular timing and for particular tasks.
****'''LIGHT CONDITIONS options:''' with this option you can decide to remove from processing status of SAFE the LIGHT Conditions status
*****'''Remove Weather LIGHT Conditions Status From Calculation of All Emergency Status:''' if unchecked the LIGHT conditions from Weather system will be not used to calculate the SAFE Status. Usefull if you want to open the dome with the light approaching the night time and do skyflat. For the Dawn flat you can decide to disable the LIGHT event using dedicated block
****'''Default''': Use the default settings
****'''OK''': Save changes and close the window
****'''Cancel''': Discard changes and close the window

==='''Various'''===

*'''Resume from Block''': Resume execution starting with the specified block. This can only be placed in the Emergency Resume block in the Events block

[[File:Dragscript-resume-from-block.png]]

*'''Block''': Choose the block where execution should resume from the drop-down list
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Disable Events''': Disable event processing. Emergency Exit, Suspend and Resume events will be ignored

*'''Enable Events''': Enable event processing. Emergency Exit, Suspend and Resume events will be recognized and handled
*'''Disable Exit Event:''' Disable event processing. Emergency Exit only event will be ignored
*'''Enable Exit Event:''' Enable event processing. Emergency Exit event will be recognized and handled
*'''Disable Suspend Event:''' Disable event processing. Emergency Suspend and Resume only events will be ignored
*'''Enable Suspend Event:''' Enable event processing. Emergency Suspend and Resume only events will be recognized and handled
*'''Disable Weather Light Event:''' Disable event processing of Light conditions coming from Weather System. Status of Light will be not used to processing the Emergency Exit and/or Emergency Suspend or Emergency Resume events (Work only if you have a weather system configured in Voyager)
*'''Enable Weather Light Event:''' Enable event processing of Light conditions coming from Weather System. Status of Light will be used to processing the Emergency Exit and/or Emergency Suspend or Emergency Resume events (Work only if you have a weather system configured in Voyager)

{{Note|Enable and disable Events is a really powerful features !!! Please use with complete understand that if you forget to re-enable the events your setup can be damaged from weather conditions. }} 

{{Note|Enable and disable Light Conditions from emergency status calculation can be useful for do SkyFlat or generally other kind of tasks at dawn and dusk or for daylight operations and testing.}}

== Events Robotarget ==
If you are running a Voyager Advanced or Full version you can intercept the thrown events generated by RoboTarget Action during. This event can be annotations or errors. Data about are saved in the environment variables of DragScript and can be used in the signal block of DragScript. What is inside the Events RoboTarget Management will executed in seld contained DragScript ineriths by the actual DragScript eliminating all except what is in the events handle you have created.

To select the event handle and create it you must use the Operating Conditions blocks.

[[File:Immagineergerherherh.png]]

=== '''Operating Conditions''' ===
There is only one operating conditions block to handle a RoboTarget Event. The DO IF ROBOTARGER EVENT. You can use one or more of this block.

* '''DO IF ROBOTARGER EVENT''': Handle one or more events related to RoboTarget Action executing in a self contained ineriths dragscript the block inside the condition
* [[File:Immaginergerwerhgwrh.png]]

* '''Even(s) Selected''': select one or more RoboTarget events to handle
* '''Reset''': Uncheck all the events selected and remove from handling
* '''Cancel''': exit from configuration without save anything
* '''OK''': Save changes and close the window

==Block==
The Block element creates a new block in your DragScript. Drag and Drop it on a DragScript element that creates a new indent level, e.g. Script, DO IF, IF, Emergency Exit, Emergency Suspend, or Emergency Resume.

[[File:Dragscript-block.png]]

*'''Label''': Give your block a name. This name can be referenced by other script elements such as jumps and resumes
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

==Remark==
The Remark element adds a non-executable comment to your script for documentation purposes

[[File:Dragscript-remark.png]]

*'''Remark''': Enter a comment that will appear in your script
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 
==Flow==
Flow Control are useful for changin flow of execution during DragScript

[[File:DSFlowRestart.png]] 

* '''Exit Block:''' exit the current block container and execute the first following useful instruction
** must be used inside a BLOCK container
** cannot be used directly under the SCRIPT default block or EVENTS default block
** if nested inside more than one BLOCK container DragScript Engine will exit from the first BLOCK container parent
* '''Restart DragScript:''' The Restart DragScript element allow script to be restart from beginning, all the variable and status will be resetted

[[Category:DragScript]]
[[Category:All]]
[[Category:Manual|Ld]]

File:Immagineefefwefwevvwev.png

2024-12-01T20:16:09Z

Leonardo:

egeg

File:Dragscript-decisions-2.1.7s.jpg

2024-12-01T20:12:07Z

Leonardo: Leonardo uploaded a new version of File:Dragscript-decisions-2.1.7s.jpg

== Summary ==
importing from old wiki

Version

2024-12-01T20:08:07Z

Leonardo:

==Voyager Version==
The version of Voyager documented by this Wiki is: 2.3.11d -> (Daily Build 2024-12-01) -> 32 and 64 bit version

Voyager Release information is here: https://forum.starkeeper.it/c/releases

MediaWiki:Sidebar

2024-12-01T20:07:21Z

Leonardo:

Viking

2024-10-27T15:10:16Z

Leonardo: /* List of Supported I/O Cards and Automation Protocols */

Voyager's companion product, Viking, provides I/O status and control for domotics (control devices used for home automation) and your observatory's I/O devices.

Actual release version is 1.0.34

Viking can be used standalone from its GUI and also integrated with Voyager to check the status and set the values of:

*Relay Cards: read status and set on/off Digital (on/off)
*Analog Input status
*Digital Input status
*PWM (Pulse-Width-Modulation) device: read status and set value
*DAC (Digital to Analog Conversion) device: read status and set value

Viking contains an application server for both local and LAN-based programmatic control

==List of Supported I/O Cards and Automation Protocols==

This is actually list of I/O cards and automation protocols (more are coming or may be requested at license purchase):

*AMS
*ARDUINO - Box Relay Ethernet 8 Relay
*DENKOVI - DAEnetIP3 Ethernet 12 Relay I/O Module
*DENKOVI - Internet/Ethernet Relay Board 12 Channel with DAEnetIP4 - I/O, SNMP, Web
*DENKOVI - SmartDEN-IP16R IoT Internet / Ethernet 16 Relay Module - DIN Rail BOX
*DENKOVI - SmartDEN-IPMAXI - DIN Rail BOX
*DENKOVI - SmartDEN-IP-PLC
*Digital Loggers - Web Power Switch Pro (Using REST API with firmware >= 1.8.0.20)
*Digital Loggers - Web Power Switch Pro (Using HTML API)
*Digital Loggers - Web Power Switch 7 (Using HTML API)
*DragonFly ASCOM from Lunatico
*DragonFly COM from Lunatico
*FireFly ASCOM from Lunatico
*FireFly COM in EXP Port from Lunatico
*GCE - IPX-800 V2 - 8 relay board internet controller
*GCE - IPX-800 V3 - 8 relay board internet controller
*GCE - IPX-800 V3 + (1) X-880 - 16 relay board internet controller
*GIOD - Viking Compatible Generic I/O Device Protocol
*KMTronic - LAN Ethernet IP 4 channels UDP Relay board
*KMTronic - LAN Ethernet IP 8 channels UDP Relay board
*KMTronic - LAN Ethernet IP 8 channels WEB Relay board
*MyHome - Open Protocol for Electric Networks (BTicino)
*PegasusAstro - Pocket PowerBox [OLD ASCOM]
*PegasusAstro - Ultimate PowerBox [OLD ASCOM]
*PegasusAstro - Umtilate PowerBox 2 [OLD ASCOM]
*PegasusAstro - USB Control HUB [OLD ASCOM]
*PegasusAstro - Pocket PowerBox Advance - Unity REST/API
*PegasusAstro - Pocket PowerBox Micro- Unity REST/API
*PegasusAstro - Ultimate PowerBox 2 - Unity REST/API
*PegasusAstro - Ultimate PowerBox 3 - Unity REST/API
*PegasusAstro - Prodigy Micro Focuser - Unity REST/API
*PegasusAstro - USB Control HUB - Unity REST/API
*PrimaLuceLab - Eagle 2/3
*PrimaLuceLab - Eagle 4
*PrimaLuceLab - Eagle 5
*Robot Electronics - ETH8020
*Robot Electronics - ETH008
*ScopeDome Arduino ASCOM Switch [Using Driver >= 5.5.5.19]
*Simulator
*TecnoSky - TecnoShelter I/O Card
*Velleman P8055
*Velleman VM140
*West Mountain Radio - RIGRunner 4005i

==Installation==

Download the free trial version of Viking, then locate the downloaded Viking_Setup_X.Y.Z.exe file and double-click to start installation:

[[File:Viking download.png]]

If you get a Windows User Account Control warning message asking if you want to install this application from an unknown publisher, click Yes to continue.

[[File:Viking-select-language.png]]

Select the language for installation and click OK

[[File:Viking-license-accept.png]]

Click the radio button to Accept the agreement and click Next to continue

[[File:Viking-select-directory.png]]

Choose your installation directory or just accept the default and click Next to continue

[[File:Viking-start-menu.png]]

Select your Start Menu folder or accept the default and click Next to continue

[[File:Viking-shortcut.png]]

Check the box to create a desktop shortcut (recommended) and click Next to continue

[[File:Viking-confirm-settings-install.png]]

Confirm your settings and click Install to perform the installation, or Back to make changes

[[File:Viking-install-done.png]]

Click Finish to exit Setup

 

==Licensing==
Double click the desktop Viking icon, or type Viking in the Windows menu to find and start the application.

[[File:Viking-desktop-icon.png]]

Viking will start in Demo mode and show the License Manager splash screen

[[File:Viking-license-manager-screen.png]]

In Demo Mode, the number of I/O devices is limited and the application server is not available.

You can use Demo Mode indefinitely to learn the Viking software and work with the included Simulator.
 

===Trial License===
When you are ready to start your 45 day free trial, click the Attiva TRIAL button (Activate Trial). If you are connected to the Internet, your trial license will be automatically activated.

If you are not connected to the Internet, follow the instructions under "How to Obtain a Trial License" in the splash screen. You will have to copy and paste the serial number - in the example above it is the set of eight four-digit blocks of letters and numbers - into an email and send it to the email address shown in the message. You will receive a license file within 24-48 hours by email.
 

===Commercial License===
Click the Acquista Licenza button (Buy License) to obtain a commercial license. You will have to copy and paste the serial number - in the example above it is the set of eight four-digit blocks of letters and numbers - into the order form when you buy the license. You will receive a license file within 24-48 hours by email.
 

===Installing Your License===
Click the Installa Licenza (Install License) button to install your license file.

[[File:Viking-install-license.png]]

Click the Seleziona (Select) button to browse to the license file attached to the email you received.

Click IMPORTA (Import) to import the license file and activate it. Click Annulla (Cancel) to cancel the operation and exit the window.

You can now start Viking and use it with your newly installed license.

==Setup==
You can setup your I/O controller card on the I/O Card Setting tab of the Viking GUI.

One instance of Viking can control one I/O card.

[[File:Viking1 0 14.png]]

*'''I/O Card''': Choose your I/O card from the drop-down list of supported devices.

Depending on the I/O card you select, different fields will be displayed directly below the I/O card selection drop-down.

These fields tell Viking how to address the I/O card. Fill them out as appropriate for your card.

In this example, the KMTronic UDP Relay card is selected, and it requires an IP Address and UDP/IP Port number.

[[File:Viking-io-card-address.png]]

Most cards use an IP address and port number, but some have ASCOM drivers or other means of connecting.

Depending on the capabilities of the card you select, one or more of the tabs in the lower half of the screen will have relevant settings for the selected card.

===Relays Setup Tab===
The number of relays shown on this tab should match the number on the I/O card selected from the drop-down on this tab.

[[File:Viking-relay-setting.png]]

*'''Relay X - Description''': Provide a meaningful name for the relay. The name you provide here will appear on Viking's Relay control tab 

===Digital Inputs Setup Tab===
[[File:Viking-digital-inputs-setup.png]]

*'''In X - Description''': Provide a meaningful name for the digital input. The name you provide here will appear on Viking's Input control tab 

===Analog Inputs Setup Tab===
[[File:Viking-analog-inputs-setup.png]]

*'''In X - Description''': Provide a meaningful name for the analog input. The name you provide here will appear on Viking's Input control tab

===PWM Setup Tab===
[[File:Viking-pwm-setup.png]]

*'''PWM X - Description''': Provide a meaningful name for the PWM device. The name you provide here will appear on Viking's PWM control tab

===DAC Setup Tab===
[[File:Viking-dac-setup.png]]

*'''DAC X - Description''': Provide a meaningful name for the DAC device. The name you provide here will appear on Viking's DAC control tab

===Uscite Automazione Setup Tab===
Note: "Automations" are unique to the MyHome automation device. You can use Voyager's DragScript to automate reading and setting any I/O device controlled by Viking.

[[File:Viking-automation-setup.png]]

*'''Automation X - Description''': Provide a meaningful name for the Automation device. The name you provide here will appear on Viking's Out Automation control tab

==Additional Info for some I/O Cards:==
Below is specific information for some I/O Cards regarding their use:

{{Note|Read carefully below if you have connection and use problems and you are using one of the cards listed below }}
* '''Digital Logger:'''
** In order to use this cards its necessary to use firmware version 1.8.0.20 or newest, activate the flag for REST API for admin and not admin user, choose also legacy clear login allow flag (or Allow legacy plaintext login methods) using web setup. Viking use REST API to communicate with this Card.
* '''DragonFly e FireFly from Lunatico (COM and ASCOM):'''
** Use Viking (Or Voyager if you manage Vikign from Voyager) to connect first time the hardware, in this way the user environment is the one correct to be used with Viking. Other you will not be able to connect the board
** If you have used another program (not VIking and Voyager) you must kill the DragonFly /FireFly application or better restart the PC to use with Voyager
* '''PrimaLuceLab Eagle 2/3/4/5 using Manager X version:'''
** Manager X lock the hostname/IP address to use, please use always ''localhost'' or the connection will be not accept. This is a limitation of the Manager X developers. Please , '''if you need to connect Viking from another PC open a ticket to the PrimaLuceLab Support.'''

==Descriptions and Connection Test==
After naming your I/O card's individual controls, you can save the descriptions to a file, reset the descriptions to the default, and test your connection.

The buttons below the descriptions provide these functions:

[[File:Viking-io-card-descriptions.png]]

*'''Reset Objects Description:''' Sets the descriptions back to the default values, e.g. Relay 1, Relay 2, etc. Be sure this is what you want so you don't accidentally lose all your meaningful names
*'''Save Objects Description:''' Saves the descriptions (meaningful names)
*'''Connection Test:''' After selecting your I/O card and configuring its address, click Connection Test to make sure Viking can communicate with your I/O card

==Connecting and Status==
At the bottom of the Viking GUI you will always find the Connect button and some additional status information.

[[File:Viking-connect-status.png]]

*'''Connect:''' Click to connect to your I/O card. After successfully connecting, the button reads Disconnect. Click to disconnect from your I/O card

Connection status information appears at the bottom of the Viking window:

[[File:Viking-status-bar-2.png]]

#The type of I/O control card selected. The LED is black if not connected, green if connected
#Viking's Application Server port number. In this example, the application server is on port 4434
#Number of clients connected to Viking's application server
#License type

==Relay Devices==

The Out Relays panel shows the current status of connected Relay devices and provides buttons to set individual or all relays on or off.

[[File:Viking-relay-2.png]]

*'''Get Status''': Click to refresh relay status
*'''ALL OFF''': Click and then click OK on the confirmation popup window to set all relays to the OFF position
*'''ALL ON''': Click and then click OK on the confirmation popup window to set all relays to the ON position
*'''OFF''': Click the OFF button to the left of the relay description to turn an individual relay OFF
*'''ON:''' Click the ON button to the left of the relay description to turn an individual relay ON
*'''LED's''': The LED's to the left of the descriptions are black if the device is OFF, and red if it is ON

 

==Input Devices==

The Input panel shows the current status of connected digital and analog input devices

[[File:Viking-input-2.png]]

*'''Get Status''': Click to refresh device status
*'''LED's''': The LED's to the left of the descriptions are black if the device is OFF, and red if it is ON
*'''Analog:''' The value of the Analog input is displayed in the box to the left of the description

 

==Pulse Width Modulation (PWM) Devices==

The PWM panel shows the current status of connected PWM devices and provides buttons to set individual or all PWM devices to a specified value or off.

[[File:Viking-pwm-2.png]]

*'''Get Status''': Click to refresh PWM device status
*'''ALL OFF''': Click and then click OK on the confirmation popup window to set all PWM devices OFF
*'''OFF''': Click the OFF button to the left of the relay description to turn an individual PWM device OFF
*'''SET:''' Sets the PWM device to the value specified by the counter field
*'''Value''': The field to the right of the PWM description label shows the current value of the PWM device

 

==Digital to Analog Conversion (DAC) Devices==

The DAC panel shows the current status of connected DAC devices and provides buttons to set individual or all DAC devices to a specified value or off.

[[File:Viking-dac-2.png]]

*'''Get Status''': Click to refresh DAC device status
*'''ALL OFF''': Click and then click OK on the confirmation popup window to set all DAC devices OFF
*'''OFF''': Click the OFF button to the left of the relay description to turn an individual DAC device OFF
*'''SET:''' Sets the DAC device to the value specified by the counter field
*'''Value''': The field to the right of the DAC description label shows the current value of the DAC device

 

==Home Automation Devices==

The Out Automation panel shows the current status of connected Bticino MyHome devices and provides buttons to Open, Close or Stop a MyHome automation

[[File:Viking-automation-2.png]]

*'''Get Status''': Click to refresh device status
*'''OPEN:''' Open the MyHome automation
*'''CLOSE''': Close the MyHome automation
*'''Stop:''' Stop the MyHome automation
*'''LED''': The LED's to the right of the button are black until the button is clicked, then red to indicate the MyHome automation status for that button is active

 

==Viking Settings: Common and Application Server==
The Viking Setting tab is where configuration information about Viking itself (not the I/O cards) is stored.

[[File:Viking-setting-2.png]]

*'''Common:'''
**'''Language:''' Choose the interface language, English or Italian
*'''Application Server:''' Settings for the application server contained in Viking
**'''Actual Server IP:''' IP address for the Viking program's application server. This is the IP address of the machine where this instance of Viking is running
***'''Update:''' Click this button to read the IP address of the machine if it has changed since the last setting
**'''TCP/IP Port Number from License:''' Port number of Viking's application server. This is read from your Viking license file.
**'''Start Server Automatically''': If checked, Viking's application server will start when Viking starts
**'''Remote Commands Execution Timeout:''' How long to wait in seconds before considering a remote command to have timed out
***

== Multi Instance ==
Starting from release 1.0.24 Viking allow multi instance running correctly in on PC. This tab allow you to start the 2nd instance or create a shortcut icon on the Desktop to start the 2nd instance.

[[File:Multiinstance.png]]

 

* '''Start Instance #2:''' click the button to open a second instance of Viking
* '''Create Start Instance #2 Icon on Desktop:''' create a shortcut icon on the Desktop to start the 2nd instance

{{Note|To activate the Multi Instance you must purchase a second license of Viking for the same serial. You will receive a dedicated license file to unlock the features.}}

{{Note|You can run a max of 2 instances of Viking in one PC}}

{{Note|With 2 instances running you can manage 2 different I/O cards. Voyager, starting from version 2.2.16j, have a second Viking client ready to be configured and used.}}

{{Note|If your tab for multi instance is disabled this means: you dont have license enabled for multi instance, you are in demo mode, your instance is the #2}}

==Application Server Monitor Window==
The Application Server tab contains a running log of timestamped application server commands and responses:

[[File:Viking-application-server-window.png]]

*'''Text Zoom:''' Move the slider to change the font size for the text in the monitor window
*'''Clear Monitor:''' remove all text in the monitor log of application server
*'''Start:''' start the application server
*'''Stop:''' stop the application server

 

==Viking ASCOM Switch driver for 3rd part Automation Software Integration==
We have developed [Thanks to Michael Poelzl] an ASCOM Switch Driver for VIking that allow other automation software, that support ASCOM Switch Client, to use Viking for interface to all the I/O cards managed by Viking. Starting from Viking 1.0.26 we support the ASCOM interaction with this driver. You can download it on our website at download section https://software.starkeeper.it

Prerequisites are:

* Viking 1.0.26 ore newer Installed and configured
* ASCOM Platform 6.4 or newer installed
* Microsoft Dot.Net Framework 4.6 installed

How to install

* check the prerequisites above
* download the Viking ASCOM Switch Driver Installer from our website
* start the installation
* follow instructions at video during installation
* Open your Automation Software (SGP,NINA...)
* Select in the ASCOM Switch section of your software the driver choosing the "ASCOM Switch Driver for Starkeeper Viking Application"
* Open the ASCOM configuration form
** [[File:ASCOmViking.png]]
** '''Viking IP Address:''' insert the IP of the PC where Viking is installed. Insert 127.0.0.1 if your Viking is installed on the same PC of your automation software.
** '''Viking Port Number:''' default port is 4434 for istance 1, 4435 for instance 2
** '''Start VIking on Connect:''' allow ASCOM driver to start Viking Application at connection if not already start. To work with this feature Viking must start like admin (use compatibility tab of Viking link icon to enable the admini mode)
*** I'''nstance 1 or 2:''' choose the istance you wan to start
** '''Viking App Path:''' select the path were Viking is installed (usually c:\Program Files (x86)\Viking...
** '''Logging:''' enable the logging on file of the driver activities
*** '''Write ASCOM Log:''' writing in ASCOM log default folder the ASCOM activities
*** '''Log TCP Messages:''' add to log also the protocol messages exchanged between Viking and the ASCOM driver

* Connect and test it, your automation software will retrieve all the configuration data from Viking and will show what is provided by the I/O card configured in Viking
* Follow the instructions of your automation software on how use the Switch facilities

[[Category:All]
[[Category:Manual|Mm]]

Viking

2024-10-27T15:07:38Z

Leonardo:

Voyager's companion product, Viking, provides I/O status and control for domotics (control devices used for home automation) and your observatory's I/O devices.

Actual release version is 1.0.34

Viking can be used standalone from its GUI and also integrated with Voyager to check the status and set the values of:

*Relay Cards: read status and set on/off Digital (on/off)
*Analog Input status
*Digital Input status
*PWM (Pulse-Width-Modulation) device: read status and set value
*DAC (Digital to Analog Conversion) device: read status and set value

Viking contains an application server for both local and LAN-based programmatic control

==List of Supported I/O Cards and Automation Protocols==

This is actually list of I/O cards and automation protocols (more are coming or may be requested at license purchase):

*AMS
*ARDUINO - Box Relay Ethernet 8 Relay
*DENKOVI - DAEnetIP3 Ethernet 12 Relay I/O Module
*DENKOVI - Internet/Ethernet Relay Board 12 Channel with DAEnetIP4 - I/O, SNMP, Web
*DENKOVI - SmartDEN-IP16R IoT Internet / Ethernet 16 Relay Module - DIN Rail BOX
*DENKOVI - SmartDEN-IPMAXI - DIN Rail BOX
*Digital Loggers - Web Power Switch Pro (Using REST API with firmware >= 1.8.0.20)
*Digital Loggers - Web Power Switch Pro (Using HTML API)
*Digital Loggers - Web Power Switch 7 (Using HTML API)
*DragonFly ASCOM from Lunatico
*DragonFly COM from Lunatico
*FireFly ASCOM from Lunatico
*FireFly COM in EXP Port from Lunatico
*GCE - IPX-800 V2 - 8 relay board internet controller
*GCE - IPX-800 V3 - 8 relay board internet controller
*GCE - IPX-800 V3 + (1) X-880 - 16 relay board internet controller
*GIOD - Viking Compatible Generic I/O Device Protocol
*KMTronic - LAN Ethernet IP 4 channels UDP Relay board
*KMTronic - LAN Ethernet IP 8 channels UDP Relay board
*KMTronic - LAN Ethernet IP 8 channels WEB Relay board
*MyHome - Open Protocol for Electric Networks (BTicino)
*PegasusAstro - Pocket PowerBox [OLD ASCOM]
*PegasusAstro - Ultimate PowerBox [OLD ASCOM]
*PegasusAstro - Umtilate PowerBox 2 [OLD ASCOM]
*PegasusAstro - USB Control HUB [OLD ASCOM]
*PegasusAstro - Pocket PowerBox Advance - Unity REST/API
*PegasusAstro - Pocket PowerBox Micro- Unity REST/API
*PegasusAstro - Ultimate PowerBox 2 - Unity REST/API
*PegasusAstro - Prodigy Micro Focuser - Unity REST/API
*PegasusAstro - USB Control HUB - Unity REST/API
*PrimaLuceLab - Eagle 2/3
*PrimaLuceLab - Eagle 4
*PrimaLuceLab - Eagle 5
*Robot Electronics - ETH8020
*Robot Electronics - ETH008
*ScopeDome Arduino ASCOM Switch [Using Driver >= 5.5.5.19]
*Simulator
*TecnoSky - TecnoShelter I/O Card
*Velleman P8055
*Velleman VM140
*West Mountain Radio - RIGRunner 4005i

==Installation==

Download the free trial version of Viking, then locate the downloaded Viking_Setup_X.Y.Z.exe file and double-click to start installation:

[[File:Viking download.png]]

If you get a Windows User Account Control warning message asking if you want to install this application from an unknown publisher, click Yes to continue.

[[File:Viking-select-language.png]]

Select the language for installation and click OK

[[File:Viking-license-accept.png]]

Click the radio button to Accept the agreement and click Next to continue

[[File:Viking-select-directory.png]]

Choose your installation directory or just accept the default and click Next to continue

[[File:Viking-start-menu.png]]

Select your Start Menu folder or accept the default and click Next to continue

[[File:Viking-shortcut.png]]

Check the box to create a desktop shortcut (recommended) and click Next to continue

[[File:Viking-confirm-settings-install.png]]

Confirm your settings and click Install to perform the installation, or Back to make changes

[[File:Viking-install-done.png]]

Click Finish to exit Setup

 

==Licensing==
Double click the desktop Viking icon, or type Viking in the Windows menu to find and start the application.

[[File:Viking-desktop-icon.png]]

Viking will start in Demo mode and show the License Manager splash screen

[[File:Viking-license-manager-screen.png]]

In Demo Mode, the number of I/O devices is limited and the application server is not available.

You can use Demo Mode indefinitely to learn the Viking software and work with the included Simulator.
 

===Trial License===
When you are ready to start your 45 day free trial, click the Attiva TRIAL button (Activate Trial). If you are connected to the Internet, your trial license will be automatically activated.

If you are not connected to the Internet, follow the instructions under "How to Obtain a Trial License" in the splash screen. You will have to copy and paste the serial number - in the example above it is the set of eight four-digit blocks of letters and numbers - into an email and send it to the email address shown in the message. You will receive a license file within 24-48 hours by email.
 

===Commercial License===
Click the Acquista Licenza button (Buy License) to obtain a commercial license. You will have to copy and paste the serial number - in the example above it is the set of eight four-digit blocks of letters and numbers - into the order form when you buy the license. You will receive a license file within 24-48 hours by email.
 

===Installing Your License===
Click the Installa Licenza (Install License) button to install your license file.

[[File:Viking-install-license.png]]

Click the Seleziona (Select) button to browse to the license file attached to the email you received.

Click IMPORTA (Import) to import the license file and activate it. Click Annulla (Cancel) to cancel the operation and exit the window.

You can now start Viking and use it with your newly installed license.

==Setup==
You can setup your I/O controller card on the I/O Card Setting tab of the Viking GUI.

One instance of Viking can control one I/O card.

[[File:Viking1 0 14.png]]

*'''I/O Card''': Choose your I/O card from the drop-down list of supported devices.

Depending on the I/O card you select, different fields will be displayed directly below the I/O card selection drop-down.

These fields tell Viking how to address the I/O card. Fill them out as appropriate for your card.

In this example, the KMTronic UDP Relay card is selected, and it requires an IP Address and UDP/IP Port number.

[[File:Viking-io-card-address.png]]

Most cards use an IP address and port number, but some have ASCOM drivers or other means of connecting.

Depending on the capabilities of the card you select, one or more of the tabs in the lower half of the screen will have relevant settings for the selected card.

===Relays Setup Tab===
The number of relays shown on this tab should match the number on the I/O card selected from the drop-down on this tab.

[[File:Viking-relay-setting.png]]

*'''Relay X - Description''': Provide a meaningful name for the relay. The name you provide here will appear on Viking's Relay control tab 

===Digital Inputs Setup Tab===
[[File:Viking-digital-inputs-setup.png]]

*'''In X - Description''': Provide a meaningful name for the digital input. The name you provide here will appear on Viking's Input control tab 

===Analog Inputs Setup Tab===
[[File:Viking-analog-inputs-setup.png]]

*'''In X - Description''': Provide a meaningful name for the analog input. The name you provide here will appear on Viking's Input control tab

===PWM Setup Tab===
[[File:Viking-pwm-setup.png]]

*'''PWM X - Description''': Provide a meaningful name for the PWM device. The name you provide here will appear on Viking's PWM control tab

===DAC Setup Tab===
[[File:Viking-dac-setup.png]]

*'''DAC X - Description''': Provide a meaningful name for the DAC device. The name you provide here will appear on Viking's DAC control tab

===Uscite Automazione Setup Tab===
Note: "Automations" are unique to the MyHome automation device. You can use Voyager's DragScript to automate reading and setting any I/O device controlled by Viking.

[[File:Viking-automation-setup.png]]

*'''Automation X - Description''': Provide a meaningful name for the Automation device. The name you provide here will appear on Viking's Out Automation control tab

==Additional Info for some I/O Cards:==
Below is specific information for some I/O Cards regarding their use:

{{Note|Read carefully below if you have connection and use problems and you are using one of the cards listed below }}
* '''Digital Logger:'''
** In order to use this cards its necessary to use firmware version 1.8.0.20 or newest, activate the flag for REST API for admin and not admin user, choose also legacy clear login allow flag (or Allow legacy plaintext login methods) using web setup. Viking use REST API to communicate with this Card.
* '''DragonFly e FireFly from Lunatico (COM and ASCOM):'''
** Use Viking (Or Voyager if you manage Vikign from Voyager) to connect first time the hardware, in this way the user environment is the one correct to be used with Viking. Other you will not be able to connect the board
** If you have used another program (not VIking and Voyager) you must kill the DragonFly /FireFly application or better restart the PC to use with Voyager
* '''PrimaLuceLab Eagle 2/3/4/5 using Manager X version:'''
** Manager X lock the hostname/IP address to use, please use always ''localhost'' or the connection will be not accept. This is a limitation of the Manager X developers. Please , '''if you need to connect Viking from another PC open a ticket to the PrimaLuceLab Support.'''

==Descriptions and Connection Test==
After naming your I/O card's individual controls, you can save the descriptions to a file, reset the descriptions to the default, and test your connection.

The buttons below the descriptions provide these functions:

[[File:Viking-io-card-descriptions.png]]

*'''Reset Objects Description:''' Sets the descriptions back to the default values, e.g. Relay 1, Relay 2, etc. Be sure this is what you want so you don't accidentally lose all your meaningful names
*'''Save Objects Description:''' Saves the descriptions (meaningful names)
*'''Connection Test:''' After selecting your I/O card and configuring its address, click Connection Test to make sure Viking can communicate with your I/O card

==Connecting and Status==
At the bottom of the Viking GUI you will always find the Connect button and some additional status information.

[[File:Viking-connect-status.png]]

*'''Connect:''' Click to connect to your I/O card. After successfully connecting, the button reads Disconnect. Click to disconnect from your I/O card

Connection status information appears at the bottom of the Viking window:

[[File:Viking-status-bar-2.png]]

#The type of I/O control card selected. The LED is black if not connected, green if connected
#Viking's Application Server port number. In this example, the application server is on port 4434
#Number of clients connected to Viking's application server
#License type

==Relay Devices==

The Out Relays panel shows the current status of connected Relay devices and provides buttons to set individual or all relays on or off.

[[File:Viking-relay-2.png]]

*'''Get Status''': Click to refresh relay status
*'''ALL OFF''': Click and then click OK on the confirmation popup window to set all relays to the OFF position
*'''ALL ON''': Click and then click OK on the confirmation popup window to set all relays to the ON position
*'''OFF''': Click the OFF button to the left of the relay description to turn an individual relay OFF
*'''ON:''' Click the ON button to the left of the relay description to turn an individual relay ON
*'''LED's''': The LED's to the left of the descriptions are black if the device is OFF, and red if it is ON

 

==Input Devices==

The Input panel shows the current status of connected digital and analog input devices

[[File:Viking-input-2.png]]

*'''Get Status''': Click to refresh device status
*'''LED's''': The LED's to the left of the descriptions are black if the device is OFF, and red if it is ON
*'''Analog:''' The value of the Analog input is displayed in the box to the left of the description

 

==Pulse Width Modulation (PWM) Devices==

The PWM panel shows the current status of connected PWM devices and provides buttons to set individual or all PWM devices to a specified value or off.

[[File:Viking-pwm-2.png]]

*'''Get Status''': Click to refresh PWM device status
*'''ALL OFF''': Click and then click OK on the confirmation popup window to set all PWM devices OFF
*'''OFF''': Click the OFF button to the left of the relay description to turn an individual PWM device OFF
*'''SET:''' Sets the PWM device to the value specified by the counter field
*'''Value''': The field to the right of the PWM description label shows the current value of the PWM device

 

==Digital to Analog Conversion (DAC) Devices==

The DAC panel shows the current status of connected DAC devices and provides buttons to set individual or all DAC devices to a specified value or off.

[[File:Viking-dac-2.png]]

*'''Get Status''': Click to refresh DAC device status
*'''ALL OFF''': Click and then click OK on the confirmation popup window to set all DAC devices OFF
*'''OFF''': Click the OFF button to the left of the relay description to turn an individual DAC device OFF
*'''SET:''' Sets the DAC device to the value specified by the counter field
*'''Value''': The field to the right of the DAC description label shows the current value of the DAC device

 

==Home Automation Devices==

The Out Automation panel shows the current status of connected Bticino MyHome devices and provides buttons to Open, Close or Stop a MyHome automation

[[File:Viking-automation-2.png]]

*'''Get Status''': Click to refresh device status
*'''OPEN:''' Open the MyHome automation
*'''CLOSE''': Close the MyHome automation
*'''Stop:''' Stop the MyHome automation
*'''LED''': The LED's to the right of the button are black until the button is clicked, then red to indicate the MyHome automation status for that button is active

 

==Viking Settings: Common and Application Server==
The Viking Setting tab is where configuration information about Viking itself (not the I/O cards) is stored.

[[File:Viking-setting-2.png]]

*'''Common:'''
**'''Language:''' Choose the interface language, English or Italian
*'''Application Server:''' Settings for the application server contained in Viking
**'''Actual Server IP:''' IP address for the Viking program's application server. This is the IP address of the machine where this instance of Viking is running
***'''Update:''' Click this button to read the IP address of the machine if it has changed since the last setting
**'''TCP/IP Port Number from License:''' Port number of Viking's application server. This is read from your Viking license file.
**'''Start Server Automatically''': If checked, Viking's application server will start when Viking starts
**'''Remote Commands Execution Timeout:''' How long to wait in seconds before considering a remote command to have timed out
***

== Multi Instance ==
Starting from release 1.0.24 Viking allow multi instance running correctly in on PC. This tab allow you to start the 2nd instance or create a shortcut icon on the Desktop to start the 2nd instance.

[[File:Multiinstance.png]]

 

* '''Start Instance #2:''' click the button to open a second instance of Viking
* '''Create Start Instance #2 Icon on Desktop:''' create a shortcut icon on the Desktop to start the 2nd instance

{{Note|To activate the Multi Instance you must purchase a second license of Viking for the same serial. You will receive a dedicated license file to unlock the features.}}

{{Note|You can run a max of 2 instances of Viking in one PC}}

{{Note|With 2 instances running you can manage 2 different I/O cards. Voyager, starting from version 2.2.16j, have a second Viking client ready to be configured and used.}}

{{Note|If your tab for multi instance is disabled this means: you dont have license enabled for multi instance, you are in demo mode, your instance is the #2}}

==Application Server Monitor Window==
The Application Server tab contains a running log of timestamped application server commands and responses:

[[File:Viking-application-server-window.png]]

*'''Text Zoom:''' Move the slider to change the font size for the text in the monitor window
*'''Clear Monitor:''' remove all text in the monitor log of application server
*'''Start:''' start the application server
*'''Stop:''' stop the application server

 

==Viking ASCOM Switch driver for 3rd part Automation Software Integration==
We have developed [Thanks to Michael Poelzl] an ASCOM Switch Driver for VIking that allow other automation software, that support ASCOM Switch Client, to use Viking for interface to all the I/O cards managed by Viking. Starting from Viking 1.0.26 we support the ASCOM interaction with this driver. You can download it on our website at download section https://software.starkeeper.it

Prerequisites are:

* Viking 1.0.26 ore newer Installed and configured
* ASCOM Platform 6.4 or newer installed
* Microsoft Dot.Net Framework 4.6 installed

How to install

* check the prerequisites above
* download the Viking ASCOM Switch Driver Installer from our website
* start the installation
* follow instructions at video during installation
* Open your Automation Software (SGP,NINA...)
* Select in the ASCOM Switch section of your software the driver choosing the "ASCOM Switch Driver for Starkeeper Viking Application"
* Open the ASCOM configuration form
** [[File:ASCOmViking.png]]
** '''Viking IP Address:''' insert the IP of the PC where Viking is installed. Insert 127.0.0.1 if your Viking is installed on the same PC of your automation software.
** '''Viking Port Number:''' default port is 4434 for istance 1, 4435 for instance 2
** '''Start VIking on Connect:''' allow ASCOM driver to start Viking Application at connection if not already start. To work with this feature Viking must start like admin (use compatibility tab of Viking link icon to enable the admini mode)
*** I'''nstance 1 or 2:''' choose the istance you wan to start
** '''Viking App Path:''' select the path were Viking is installed (usually c:\Program Files (x86)\Viking...
** '''Logging:''' enable the logging on file of the driver activities
*** '''Write ASCOM Log:''' writing in ASCOM log default folder the ASCOM activities
*** '''Log TCP Messages:''' add to log also the protocol messages exchanged between Viking and the ASCOM driver

* Connect and test it, your automation software will retrieve all the configuration data from Viking and will show what is provided by the I/O card configured in Viking
* Follow the instructions of your automation software on how use the Switch facilities

[[Category:All]
[[Category:Manual|Mm]]

MediaWiki:Sidebar

2024-10-27T15:07:24Z

Leonardo:

MediaWiki:Sidebar

2024-10-27T15:06:45Z

Leonardo:

Version

2024-10-27T15:06:21Z

Leonardo: /* Voyager Version */

==Voyager Version==
The version of Voyager documented by this Wiki is: 2.3.11c -> (Daily Build 2024-10-27) -> 32 and 64 bit version

Voyager Release information is here: https://forum.starkeeper.it/c/releases

Sequence Configuration

2024-06-29T14:10:15Z

Leonardo: /* Sequence Configuration Dialog */

__TOC__

A Sequence is a set of exposures of a single target. It can include repeated exposures using multiple filters and exposure lengths.

In addition to specifying the number and type of exposures to take, you can specify many additional actions and settings, including

*Sequence start delays
*Cooling settings
*Pointing retries
*Plate solving on or off
*Tracking stops and starts
*Meridian flip management
*Guiding and dithering settings
*Exposure delays and subframe size
*Autofocus actions
*Error and sequence end actions

One or more sequences can be included in a [[DragScript]] to completely automate an imaging session.

Sequences are stored by default in the ConfigSequence folder of your [[Installation#Voyager Folders|Voyager directory]], but you are free to store them anywhere.

You can edit sequences while actions are running. You can invoke the sequence and flat sequence editor from the [[Main Window#Tools and Editor|Tools and Editor]] menu to do this.

A running sequence will use the sequence that was defined at the time it started running. You can edit a sequence while it is running, but the changes will not take effect until you stop and restart the sequence.{{Note|You must have a profile defined and loaded to configure a sequence. }} 

==Defining a Sequence==
Sequences are defined by clicking the gear [[File:Gear-icon.jpg]] icon next to the Sequence button in the Session panel of the [[OnTheFly]] workspace:

[[File:Session-onthefly.jpg]]

Sequences are run by clicking the Sequence button with the green triangle next to it. [[File:Sequence-green-triangle.png]]

Sequences start-up options can be specified by clicking the button with two blue triangles [[File:Double-blue-arrow.jpg]]

 
==Sequence Configuration Dialog==

The sequence configuration dialog comes up after you click the gear [[File:Gear-icon.jpg]] icon next to the Sequence button:

[[File:Sequence-config-window-2.11f.jpg]]

*'''Target Name''': Enter the name of the object you want to image and click Fast Find. Voyager will look up the J2000 coordinates in the connected [[Planetarium Setup|Planetarium]] software and if found, enter them in the RA and DEC fields at the top right of this dialog window.
*'''RA''' and '''DEC''': The Right Ascension and Declination coordinates for the sequence target. Populated automatically by the Fast Find / Object Finder / SIMBAD controls, or entered manually.
*'''COPY and PASTE:''' copy the RA and DEC data from fields to the clipboard, paste the RA and DEC data in clipboard into the rispective field in sequence configurator
*'''Rotation Angle:''' an arbitrary angle that can be a Rotator PA or Sky PA, depends on rotator tab setting. Always put the PA needed before the meridian .{{Note|Always put the PA needed before the meridian}}
*'''Target Type :''' define the type of target used by the sequence. Default is normal target. For a Default target you must edit the RA and DEC field about the target coordinates. Comet, Asteroid, Planet, DynaSearch types arereserved for Dynamic Target (a target wher Voyager will calculate the actual coordinates during the sequence in a dynamic way). For using dynamic target you must select the target using the Comets,Asteroids, Planets buttons. More info about RoboOrbits and Dynamic Target [[Introduction to RoboOrbits|here]]. If you are using a Dynamic Target the RA and DEC field will be hide and the Target Key Field will be valorized with the code/number of the target object selected. Using other finders like Fast Find, Sesame, Find and RoboClip will reset the Target Type to Default (static target). The DynaSearch dynamic target you must use the search text used in Planetarium control to find the object you want like target (example Ganymede for Ganymede luna of Jupiter)
*{{Note|If you are using a Dynamic Target remember to select the pointing tab of the sequence configuration the Dynamic Target Pointing mode more appropriate to your neededs. Se the pointing tab explanation. Default is Calculate RA/DEC only at Sequence begin}}
*'''Fast Find''': Click the Fast Find button to do a quick lookup of the target name entered in the Target Name field
*'''Find:''' Click this icon to bring up the Object Finder. The Object Finder is documented in the [[OnTheFly#Target Coordinates J2000|Target Coordinates J2000]] section. Coordinates found with the Object Finder can be entered into the RA and DEC fields for the Sequence
*'''SESAME''': Enter a target in the Target Name field and click this button to do a SESAME search for the object. If found, a pop-up window displays object information returned from SESAME
*'''ROBOCLIP''': Open RoboClip Windows Manager to retrieve customized targets on shared database
*'''Target Key :''' This is a read-only field. if you are using a Dynamic Target (Comet, Asteroid) this field contains the code/number of the dynamic target you have selected with the RoboOrbits Finders, more info about RoboOrbits [[Introduction to RoboOrbits|here]]. If you are using a static (normal) target the fields is empty or will be not used by the Sequence action.
*'''Profile:''' The equipment profile associated with this sequence. A new sequence will default to using the currently active profile. You can create and edit sequences for non-active profiles by clicking the '''Change Profile to This Sequence''' button in the title bar of this window
*[[File:Change-profile-sequence.png]] '''Change Profile To This Sequence''': Brings up a dialog window from which you can associate sequences with a profile. See [[Sequence Configuration#Change Sequence Profile|Change Sequence Profile]] section below for discussion of this process
*[[File:Reset-sequence-data.png]] '''Reset Sequence Data''': Caution! Clicking this button resets all information in the sequence. If you have not saved it, your sequence data will be lost and you will have to start over
*[[File:Load-file.png]] '''Open Sequence File''': Click this file to load the data from a saved sequence into the Sequence Configuration window
*[[File:Save-file.png]] '''Save Sequence File''': Click this file to save the data from the Sequence Configuration window to the file of your choice
*[[File:Cancel-config.png]] '''Cancel and Discard Changes''': Click this button to close the Sequence Configuration window and discard any changes made since it was opened
*
*'''Refresh Filter Synoptic''': Refresh the visual representation of the filters used in order by this sequence - this information appears in the space below the sequence elements and above the sequence configuration tabbed windows
*'''OK''': Click the OK button to save your changes and close the Sequence Configuration window
*

{{Note|If you wish to set the Position Angle of your sequence target, you need use either the MoveTo command button in the Rotator widget or the RotatorMoveTo command in a DragScript }} 

==Change Sequence Profile==

As of Voyager 2.0.14e (daily build) or 2.1.0 (stable build), you can create and edit sequences with the profile of your choice.

'''''If you only edit or create sequences for the active profile, there is no need to use this dialog window. The active profile is used, and the filename of the active profile will be stored with the sequence when you save it.'''''

By default, a new sequence will be created using the currently active profile, which is displayed on the right at the top of the Voyager main window.

'''References to the "Actual" profile mean the currently active profile in Voyager.'''

If you want to create or edit a sequence using a different profile from the currently active one, click the '''Change Profile to This Sequence''' button in the Sequence Configuration title bar to bring up this dialog:

[[File:Sequence-profile-migration-tool.png]]

 {{Note|If you are editing a sequence created with Voyager prior to version 2.0.14e, the profile is not stored with the sequence so Voyager doesn't know which profile was used to create it. If you want to use the active profile, you can just cancel from the dialog and continue editing the sequence. The profile name will be stored in the sequence the next time you save it to disk.}} 

*'''Data''':
**'''Sequence''': The sequence file currently being worked on. If you have created a new sequence and it has not yet been saved, this field will be blank
**'''Original Profile''': The profile stored with the sequence file
**'''Actual Profile''': The profile currently loaded and active in Voyager
*'''APPLY Actual Profile''': Ignore the profile stored in the sequence file and use the currently active profile in Voyager. If settings such as filters are different between the two profiles, carefully review your sequence elements and make sure you are using the desired filters, speed and readout mode
*'''USE Original Profile''': Use the profile stored in the sequence file for things like filters, camera gain and readout. This is useful if you want to edit a sequence for a different profile than the currently active one.
*'''SELECT MANUALLY Profile''': Opens a file browsing dialog and you can select any profile. The selected profile will be used to supply information such as filters, camera readout and gain settings when editing this sequence, and the selected profile will be stored in the sequence file when you save it
*'''CANCEL''': Abort and close this window without saving changes

==Sequence Elements==
The Sequence Elements panel of the Sequence Configuration dialog tells Voyager about the exposures you want to take of your target:

[[File:Sequence-elements-gain-offset.jpg]]

*'''Slot''': Click the gray buttons in the Slot column and they turn green indicating that slot is active - the information in that row (slot) of the Sequence Elements table will be used when you run the sequence
*'''Type''': Exposure type: Light, Bias or Dark
*'''Filter''': Filter for this exposure. Available filters come from the connected profile in the [[Camera Setup#Filters|Camera Setup]] area
*'''Suffix''': Enter any text you would like to include in the image filename.
*'''Exposure''': Length of the exposure in seconds
*'''Bin''': Binning level for this exposure. Available binning levels come from the connected profile in the [[Camera Setup#Filters|Camera Setup]] area
*'''Speed''': ISO for DSLR's
*'''Readout Mode''': Select a Readout Mode from the drop-down list. Readout Modes are retrieved from your camera if your camera driver provides them. The [[Camera Setup#Readout Mode|Readout Mode section of the Camera Setup]] page explains how to retrieve them
*'''Gain:''' If you are using the [[Camera Setup#ASI Native Driver|ASI Camera native driver]] supplied by Voyager ('''not''' the ASI ASCOM driver), you can enter the Gain for this sequence element. This will be grayed out if you are not using Voyager's ASI Camera native driver.
*'''Offset:''' If you are using the [[Camera Setup#ASI Native Driver|ASI Camera native driver]] supplied by Voyager ('''not''' the ASI ASCOM driver), you can enter the Offset for this sequence element. This will be grayed out if you are not using Voyager's ASI Camera native driver.
*{{Note|If you are using a sequence with the ASI Camera native driver that was first defined with a different camera, all Gain and Offset values will be initially set to 0/0. Make sure you change these to the desired settings and save the sequence before running.}} 
*[[File:Lens.jpg]]: Click the magnifying glass icon to select the Gain and Offset from the presets defined in the [[Camera Setup#ASI Native Driver|ASI Camera native driver setup]].
*'''Repeat''': Number of exposures to take
*[[File:Sequence-element-copy-paste.jpg]]:
**Up arrow moves this row up one position; Down arrow moves this row down one position; X clears the information from this row
**'''Copy Button''': Click Copy to copy the sequence element information from the row containing the Copy button
**'''Paste Button''': After clicking Copy on a row, click Paste on a new row to paste the sequence element information to the row containing the Paste button
**Use copy and paste to quickly set up the sequence elements for a number of rows that only differ in a couple of values, such as the filter choice
*The scroll bars on the right can be used to scroll the window up and down if you have more rows than show in the main window 

The colored bar under the Sequence Elements is called the Filter Synoptic. It represents the filters used when the sequence runs, in the order they will be used. The length of each color bar is proportional to the length of exposures taken with that filter.

[[File:Filter-synoptic.png]]

In this example, we take five 30 second images with the L filter - which corresponds to the white part of the bar. Then five each of red, green and blue, 60 seconds each. This is how our sequence will use filters when the "Group By Slot" option is chosen as the Sequence Mode in the [[Sequence Configuration#Sequence Tab|Sequence Tab]]. If we chose "cyclic Round" instead, the sequence will take one image with each filter and then move on to the next, like this:

[[File:Filter-synoptic-cycle.png]]
 {{Note|Image filenames by default include: Target Name, Type, Exposure, Binning, Sensor Temperature (cooling), sequence number, filter, date and time, position angle, and pier side. If using a driver that supports Gain and Offset, they are also included in the file name. Use the Suffix field in the Sequence Elements to add other information }} {{Note|You cannot set any values in a row unless you click the gray Slot number at the start of the row first. It turns green indicating the slot is active, and then you can enter values in that row}}

Once you have set up your Target Name and Sequence Elements, click through the tabs at the bottom of the dialog to specify the way Voyager should handle other elements such as Cooling, Guiding, etc. during the execution of this sequence.

==Sequence Image Filenames==
Starting from version 2.2.14j Voyager have also a [https://wiki.starkeeper.it/index.php/Voyager_Setup#File_Pattern_Manager File Pattern way] to define sub foldering and file naming.

Here explaned the default folder and naming system.

The image filenames are generated automatically by Voyager. The number of fields can vary depending on your connected equipment - e.g. if you don't have a rotator configured, you won't have the Position Angle field.

Here's an example filename with a description of the fields.

[[File:Filename-spec-216c.jpg]]

#Target name
#Type of exposure: Light, Dark, or Bias
#Filter Name: Filter Name for cameras with filter wheels - blank if the contents of the Suffix field equals one of your filter names
#Suffix: Whatever you type in the suffix field of the Sequence element; example here is G139 to represent Gain of 139
#Exposure length
#Binning level
#Sensor temperature or "No_Cooling" if Voyager is not managing cooling during the Sequence
#Sequence number: a sequential number generated automatically when Voyager takes a new image
#Date: YYYYMMDD
#Time: HHMMSS
#MS: millisecond portion of the time the image was taken
#Gain: Gain value if you are using Voyager's ASI Camera native driver
#Offset: Offset value if you are using Voyager's ASI Camera native driver
#Position Angle if a rotator is defined in Setup
#Position relative to Meridian: E = East or W = West
#File type: FIT for a FITS file

==Sequence Tab==
The Sequence tab of the Sequence Configuration window tells Voyager how to cycle through your exposures, where to store images, and other sequence constraints:

[[File:Sequence-definition-tab-2.1.7s.jpg]]

*'''Sequence Mode''': Choose Cyclic Round or Group By Slot from the drop-down list
**'''Cyclic Round''': Voyager will take one exposure using the parameters of a slot, then move to the next slot and take one exposure, etc. E.g. if you have one slot for each filter of L, R, G and B, Voyager would take one L exposure, then one R, then G, then B, then cycle back around to L and repeat until the total number of exposures specified in the Repeat box are taken.
**'''Group By Slot''': Voyager will take the number of exposures specified in the Repeat column for each slot before moving on to the next slot
**'''Repeat''': If checked, Voyager will loop back and run the sequence again. It will be run the number of times specified in the Repeat counter field
*'''Sequence Directory''': Where to save images taken during this sequence
**'''Auto / Manual''': Choose Auto and Voyager will automatically create a sequence directory using the base folder specified in [[Voyager Setup#PATH|Voyager Setup]] and the Target Name. Choose Manual and you can type in any folder for your images, or click the Select button and browse to a directory to choose that one
**'''Create Logical Data Subfolder Inside Sequence Directory (all between 00:00 to 08:00 AM are from yesterday)''': Check this box to create a subfolder, named with the date of the start of the sequence. All images from this sequence are stored in the subfolder, including any taken after midnight until 8AM local time
**'''Create Data SubFolder for Filter Name:''' Check this box to create subfolders named with the filters used for this sequence. Images taken by this sequence are stored in the subfolder with the name matching the filter used for the image. New as of Voyager 2.1.2e

* '''Sequence Sub Foldering / File Naming:''' selection of the sub foldering and file naming method
**'''Use FILE PATTERN:''' flag this checkbox to activate sub foldering and file naming with File Pattern method (please configure the file pattern in the [https://wiki.starkeeper.it/index.php/Voyager_Setup#File_Pattern_Manager File Pattern Manager])
**'''Override FILE PATTERN:''' flag this chheckbox to activate sub foldering and file naming with File Pattern method, insert in the big text field near the flag the string to override of the file pattern to use instead of the one configured in the [https://wiki.starkeeper.it/index.php/Voyager_Setup#File_Pattern_Manager File Pattern Manager]. This will affect only the actual sequence and do not change the main File Patterm Manager configuration. This is for example mandatory in case of join of the OpenSkyGems network and sharing of the observatory setup.
**'''Use Voyager STANDARD:''' flag this checkbox (this choice is the default for a new sequence) to use the original sub foldering and file naming system adopted by Voyager from the beginning
***'''Create Logical Data Subfolder Insside Sequence Directory (all between 00:00 to 08:00 AM are from yesterday) :''' Check this box to create a subfolder, named with the date of the start of the sequence. All images from this sequence are stored in the subfolder, including any taken after midnight until 8AM local time
*** '''Create Data Subfolder for Filter Name:''' create a sub folder with the target name

{{Note|The Cyclic Round setting is best if you have to get as many images as possible from each filter in a single Sequence run. For example, you have traveled to a dark site and just want to get as much data as possible in one night. The Group By Slot setting is the most time efficient as no time is spent changing filters between each exposure. However, if clouds move in or you run out of time, you may not get data from all filters in a single session with this setting}} {{Note|Use Group By Slot with Repeat to have some of the advantages of both modes (Cyclic Round and Group By Slot). For example, set the sequence to take 5 images with each filter, select Group By Slot, and Repeat to as many times as you want. Now you will get some images with each filter, but you won't spend as much time changing filters over the course of the sequence.}}
 
==Constraints Tab==
The Sequence tab of the Sequence Configuration window tells Voyager how to cycle through your exposures, where to store images, and other sequence constraints:

[[File:ConstraintsSequence2214j.jpg]]

*'''Sequence Constraints''':
**'''Exit sequence if Target is below this Altitude''': If checked, automatically end the sequence if target drops below the given altitude in degrees. If the sequence is running in a [[DragScript]], return to DragScript with an OK result (no error, successful sequence termination,skipped status will be set)
**'''Exit sequence if Target is above this Altitude''': If checked, automatically end the sequence if target rises above the given altitude in degrees. If the sequence is running in a [[DragScript]], return to DragScript with an OK result (no error, successful sequence termination,skipped status will be set)
**'''Exit sequence if Target is before this HourAngle:''' If checked, automatically end the sequence if target is before the hour angle (hours from the meridian) specified in the spinner control. If the sequence is running in a [[DragScript]], return to DragScript with an OK result (no error, successful sequence termination,skipped status will be set)
**'''Exit sequence if Target is above this HourAngle''': If checked, automatically end the sequence if target is after the hour angle (hours from the meridian) specified in the spinner control. If the sequence is running in a [[DragScript]], return to DragScript with an OK result (no error, successful sequence termination,skipped status will be set)
**'''Exit sequence if Target is before this Azimuth:''' If checked, automatically end the sequence if target is before the azimuth angle specified in the spinner control. If the sequence is running in a [[DragScript]], return to DragScript with an OK result (no error, successful sequence termination,skipped status will be set)
**'''Exit sequence if Target is after his Azimuth:''' If checked, automatically end the sequence if target is after the azimuth angle specified in the spinner control. If the sequence is running in a [[DragScript]], return to DragScript with an OK result (no error, successful sequence termination,skipped status will be set)
**'''Use External Interval Angle:''' if each the azimuth constraints will be cheched you can decide with this flag to use external angle instead of internal angle between before and after azimuth. Example if you choose 70° before and 150° after with out external flag this mean sequence run if angle is between 70 and 150°, if you chec it and invert to external sequence will be terminate if azimuth is between 70 and 150°

{{Note|The hour angles can be negative or positive. The ending hour angle must be greater than the starting hour angle.}}

==On Start Tab==
The On Start tab of the Sequence Configuration window is where you can specify things to do before starting the sequence:

[[File:On-start-tab.png]]

*'''Run this Program/Script BEFORE Time Wait''': Click the box with "..." to bring up the [[OnTheFly#Utilities|Run External Program / Script]] window to browse to a program or script to run before the "Time Wait on Start" interval. '''Note:''' this field is used to run an external Windows program or script, not a Voyager DragScript. Run your Sequence from the DragScript, not the other way around.
*'''Time Wait On Start''': Specify if Voyager should delay before starting the sequence
**'''NOTE:''' The first checkbox, the one after '''Time Wait On Start''' and before '''Interval''', must be checked if you want Voyager to wait either an Interval OR until an Absolute time. This checkbox is linked to "Time Wait on Start" and the default is to wait for an Interval
***'''Interval''': Check the box before '''Interval''' and enter the amount of time to wait in HH:MM:SS in the three scrolling fields. Voyager will wait this amount of time before starting the sequence
***'''Absolute''': Check the box before '''Interval''' AND check the box before '''Absolute'''. Enter the actual time in HH:MM:SS at which Voyager should start running the sequence
*'''Run this Program/Script AFTER Time Wait''': Click the box with "..." to bring up the [[OnTheFly#Utilities|Run External Program / Script]] window to browse to a program or script to run after the "Time Wait on Start" interval. '''Note:''' this field is used to run an external Windows program or script, not a Voyager DragScript. Run your Sequence from the DragScript, not the other way around.
*'''Point Target On Start''': Check to perform a [[Plate Solve Setup#Precision Pointing|precision pointing]] operation at sequence start
*'''Inject Focus on Start''': Check to perform an autofocus operation at sequence start
*'''Open Flat Device Cover''': Check to open the flat device at sequence start
**'''On Start''': Open the flat device cover as soon as the sequence is executed - do not wait if there is a "Time Wait On Start" specified
**'''After Time Wait on Start''': Open the flat device cover after the Time Wait On Start interval has elapsed
*'''Calibrate DONUTS:''' Check to perform a calibration operation in Donuts Process (an algorithm suite and application for advanced research https://pypi.org/project/donuts/). Douts suite must installaled, configured and ready to work.
**'''On ALT/AZ Coords:''' perform the Donuts calibration pointing the telescope to the ALT/AZ coordinates defined by user
***'''ALT :''' Altitude coordinate in format DD MM SS or DD MM SS.sss
***'''AZ :''' Azimuth coordinate in format DD MM SS or DD MM SS.sss
**'''On Place:''' perform the Donuts calibration pointing where is actually pointed the telescope 
{{Note|If the sequence is run from a DragScript, only the Point Target on Start field is used. The other fields must be specified with DragScript actions}} 
==Cooling Tab==
The Cooling tab of the Sequence Configuration window is where you specify CCD cooling (Peltier) for the sequence:

[[File:Cooling-tab.png]]

*'''Cooling''': Check this box to manage cooling via this Sequence. If you don't check this box and have cooling set before running the sequence, no changes to cooling will be made
*'''SetPoint''': Enter the desired sensor temperature (SetPoint) for your CCD cooler
**'''Use CCD Firmware Cooldown''': If checked, just command the desired temperature to the CCD cooler and let the cooler's firmware decide how quickly to ramp to that temperature
**'''Power ON After Time Wait On Start''': If checked, send a command to turn CCD cooler power on after the [[Sequence Configuration#On Start Tab|Time Wait On Start]] interval has elapsed
**'''Auto Scale SetPoint if CCD can't cooling at initial desired request''': If checked, if the CCD cooler fails to reach the desired temperature within the time specified in [[Camera Setup#Cooling System|Camera Setup]], or within the power usage constraints listed below, try again with successively warmer temperatures as specified below
***'''Or if Cooler Power Mobile Mean is >=''': Begin the auto scaling operation if the moving average of the cooler power in use was greater than or equal to the specified percentage for the "in the last" number of seconds
***'''And use in order this SetPoint in °C''': Use these temperatures in the order specified for auto scaling. The temperatures should be progressively warmer (higher numbers) from left to right

 {{Note|If you see "NoCooling" in the file name created by Voyager, it means the "Cooling" checkbox in the Cooling tab of the Sequence is unchecked. This means you have cooling on in the camera but the Voyager Sequence is not managing it.

If an error has been returned from the camera's cooling system, you would see UNK text instead of NoCooling.}}

 

==Pointing Tab==
The Pointing tab of the Sequence Configuration window is where you specify additional parameters for any Pointing operations performed during the sequence:

[[File:Pointing-tab.png]]

*'''On Driver Goto Error''': If the mount driver returns an error when Voyager commands a Goto (slew) operation, retry the operation up to a maximum of 3 times
*'''Meridian Flip Watchdog:''' if checked, in case of Meridian flip do not recognized after the Voyager meridian change routine (pier contine to remain on west) Voyager will retry for 3 times and then will abort the Sequence with an error. if not flagged Voyager will retry forever until the end of interval of time dedicated to the sequence. {{Note|If you experience this problem you must check you driver/mount settings and fix it to avoid the problem.}}
*'''Dynamic Target Pointing (Only for Comets and Asteroids Target Type) :''' only if you are using a Dynamic Target (comet or asteroid) Voyager allow you to select when calculating the RA/DEC coordinates od the Dynamic Target. Default for a Dynamic Target is the Calculate RA/DEC only at Sequence Begin
**'''Calculate RA/DEC Only at Sequence Begin :''' Voyager will calculate the RA/DEC of the Dynamic Target only whe the Sequence action will start and will use this RA/DEC for all duration of the Sequence action. If the Sequence will be restarted anothe day or some hours after or generally will be restarted VOyager will calculate again the RA/DEC coordinates. But not in the same Sequence run.
**'''Calculate RA/DEC at Each Precise Goto :''' Voyager will calculate the RA/DEC of the Dynamic Target at each precise pointing goto inside the Sequence Run included at the begin of Sequence
**'''Calculate RA/DEC Every X seconds :''' Voyager will calculate the RA/DEC of the Dynamic Target at the beginning of the Sequence and each X seconds like edited in the dedicated field. if the X interval is expired and Voyager is in exposure camera mode, will wait the end of exposure to calculate the new coordinates. A realign goto will not be requested if the next flag is not checked.
***'''And Realign Target :''' if checked Voyager will force a realign with a Precise pointing to the new RA/DEC of the Dynamic Target
***'''Without Using Plate Solving :''' if checked Voyager will avoid the precise pointing with plate solving for the realign and will use a simple goto without solving

==Rotator Tab==
The Rotator tab of the Sequence Configuration window is where you specify additional parameters for your rotator's actions during the sequence:

[[File:RotatorTab2213c.jpg]]

* '''Rotator Manage:''' if check rotator's action will be managed during the sequence framing the target with the PA specified and other all the others flag available
* '''Rotator Type:''' define if the rotation angle is the rotator angle (rotator PA) reported from the driver (and with offset if asked to Voyager in Sync) or the Sky angle (Sky PA) chosen with web dashboard VirtualFOV or planetarium or another system. If you select Sky PA Voyager will use the Plate solve PA result to rotate the rotator to the right angle. If you select the Rotator PA Voyager will just rotating rotator using drive angle at desidered value, no correction using the plate solved PA will be done
* '''PA Tollerance +/-:''' specified the tollerance in degree about the PA accepted like ok (example 180° +/-3° will accept 177° to 183°)
* '''Rotator & Meridian Flip:''' "Mantain the Same Image Orientation After the Meridian" if checked force Voyager to shot the target with same orientation in the images taken before anf after meridian.Use of this flag is useful also to use the same guide star in case of use of OAG with high focal lenght.
* '''Rotator & Fork Mount:''' if enabled force Voyager to check rotator tolleranze after each Target realign, useful for fork mount with derotator system

{{Note|Rotator management will be done only done in this two points of the sequence:

- at first precise pointing, so flag the “Point target on start” in the start tab of the sequence configurator

- at meridian change
}} {{Note|In sequence always put the PA needed before the meridian

SKY PA:

the solving of the SKY PA changes by 180 ° if the mount is after the meridian and has made the flip even if the rotator has not made any rotation

if you ask to keep the orientation of the Voyager image according to the meridian in which the mount is located, it behaves like this:

before the meridian it maintains the same SKY PA set in the sequence (net of fine adjustments)
after the meridian it maintains the same SKY PA set in the sequence, this means that the plate solving of the image shows a PA offset by 180 ° from the request and therefore the rotator is flipped

if you do NOT request to keep the orientation of the Voyager image based on the meridian in which the mount is located, it behaves like this :

before the meridian it maintains the same SKY PA set in the sequence
after the meridian the requested SKY PA will be flipped by 180 °, this means that the plate solving of the image shows an already corrected PA so the rotator does not move (net of precision adjustments)

ROTATOR PA:

SKY PA is not taken into consideration at all, therefore plate solving does not affect the rotator

if you ask to keep the orientation of the Voyager image according to the meridian in which the mount is located, it behaves like this:

before the meridian it maintains the same ROTATOR PA set in the sequence
after the meridian the required ROTATOR PA will be flipped by 180 ° in order to have the image not rotated and the rotator will then be rotated by 180 °

if you do NOT request to keep the orientation of the Voyager image based on the meridian in which the mount is located, it behaves like this:

before the meridian it maintains the same ROTATOR PA set in the sequence
after the meridian it keeps the same ROTATOR PA set in the sequence, the image will be flipped but the rotator will not be flipped

}}
 

==Tracking Tab==
The Tracking tab of the Sequence Configuration window is where you specify additional parameters for your mount's tracking actions during the sequence:

[[File:Tracking-tab.png]]

*'''Tracking Stop Watchdog''': If checked, if tracking stops during the sequence, attempt to restart tracking the specified number of times
*'''Tracking Start''': If checked, stop tracking when the sequence is started, and start tracking only after the [[Sequence Configuration#On Start Tab|Time Wait On Start]] interval has elapsed

 
==Plate Solving Tab==
The Tracking tab of the Sequence Configuration window is where you specify additional parameters for plate solving during the sequence:

[[File:Plate-solving-tab.png]]

*'''Disable Plate Solving''': If checked, do not perform plate solving during the sequence. If this is checked, precision pointing can not be done, only unverified goto's of the mount
*'''Bypass DEFAULT Setting and use Actual Filter for Plate Solving''': If checked, the filter in use for image exposures will be used for plate solving, regardless of the settings specified in [[Plate Solve Setup#Plate Solving DEFAULT Setting|Plate Solve setup]]
*'''Bypass DEFAULT Setting and use this OVERRIDE Setting for Plate Solving:''' if checked, the filter used for plate solving will be the one in Plate Solving OVERRIDE Setting Box. Usefull when you use a 2 subset of filter narrow / broadbrand of different tichkness, this mean different focus. Remember to enlarge time or increase (or do togheter) binning in case of use of narrow band filter. 
{{Note|Using a narrow band filter may cause plate solving to fail, as the resulting image may be too dim to have stars that the plate solving routine can locate in the image}}

==Meridian Flip Tab==
The Meridian Flip tab of the Sequence Configuration window is where you specify additional parameters for meridian flip management during the sequence:

[[File:Sequence-meridian-flip-211j.jpg]]

*'''Meridian Flip Mode''': Choose Do Not Manage, Halt on Flip Time or Manage from the drop-down list
**'''Do Not Manage''': Voyager will not perform any meridian flip management during the sequence - it will not monitor mount position near the meridian while the mount is tracking
**'''Halt on Flip Time''': When Voyager determines it is time to flip the mount, the sequence will be halted. If you have [[Mount Setup#Safety|tracking safety stop]] enabled in Voyager the mount will be halted. Otherwise, set a limit in your mount configuration settings to stop tracking
**'''Manage''': Voyager will monitor the mount position relative to the meridian and perform a meridian flip as needed, as specified in [[Mount Setup#GEM Meridian Flip Manager|Mount Setup]]
*'''Inject Focus On Meridian Flip''': If checked, perform an autofocus after the meridian flip completes
*'''Force Meridian Flip Procedure with Exposure Abort After Meridian Crossing''': If checked, Voyager will abort any exposure in progress and force a meridian flip after the Wait Max Time number of minutes has elapsed past the meridian. This time should be greater than the "Do Flip After Mount Crossing Meridian By" number of minutes you set the [[Mount Setup#GEM Meridian Flip Manager|GEM Meridian Flip manager in Mount Setup]]. This could be used as a safety value to make sure your mount never tracks further than this amount of time past the meridian.
*'''ABORT Exposure if Meridian Flip occurs outside Voyager and FORCE EXECUTE Meridian Flip Operations''': If checked, Voyager will notice if a meridian flip has occurred external to Voyager (not initiated by Voyager) and perform the meridian flip operations. This option only works if:
**[[Mount Setup#Mount Selection|Mount control in Voyager]] is via ASCOM
**[[Mount Setup#GEM Meridian Flip Manager|ASCOM Pier Mode setting]] in Voyager is either ASCOM Normal or ASCOM Inverted
**Meridian Flip Mode setting on this tab is Manage
*'''Run this Program/Script BEFORE Meridian Flip''': Click the box with "..." to bring up the Run External Program / Script window to browse to a program or script to run before the "Meridian Flip" action '''Note:''' this field is used to run an external Windows program or script, not a Voyager DragScript. Run your Sequence from the DragScript, not the other way around. '''Avoid use of long time running script/executable to prevent pier crash and damage to your setup.'''
*'''Run this Program/Script AFTER Meridian Flip''': Click the box with "..." to bring up the Run External Program / Script window to browse to a program or script to run after the "Meridian Flip" action '''Note:''' this field is used to run an external Windows program or script, not a Voyager DragScript. Run your Sequence from the DragScript, not the other way around.

 {{Note|If you choose Do Not Manage, please be sure your mount's firmware and/or driver software handles meridian flips automatically and prevents equipment damaging pier crashes}}{{Note|If you choose Force Meridian Flip with Exposure Abort..., make sure your mount can track the specified Max Wait Time number of minutes past the meridian without an equipment damaging pier crash}} {{Note|As of Voyager 2.1.4a, Sequences contain a new Watchdog for the control of meridian flip repetitions. After a certain number of attempts by Voyager to change the meridian, the Sequence stops. If this occurs when the Sequence is running in a DragScript, the Sequence ends with an ERROR}}
 
==Guide/Dithering Tab==
The Guide/Dithering tab of the Sequence Configuration window is where you specify additional parameters for guiding and dithering management during the sequence. The settings in [[Guiding Setup]] are used unless these settings override them.

[[File:Sequence-config-dither-every-x.png]]

*'''Guide Star Selection Method''': Choose how the guide star should be selected
**'''Voyager RoboGuide''': Voyager's own RoboGuide algorithm, as specified in [[Guiding Setup#RoboGuide Advanced|Guiding Setup]], will be used to select a guide star. If RoboGuide cannot find a suitable guide star, Voyager will retry with the guiding software's own guide star selection process if it has one
**'''Native Guide Control''': Use the guiding software's own star selection method
*'''Calibrate Guide''': If checked, perform a Guiding Calibration step at the start of the sequence. Use the exposure time in the spinner control in seconds and binning level for the guide software's calibration routine
**'''Recalibrate Every X Minute:''' if activate will force Voyager to recalibrate guiding at interval defined in minutes in the min fields, useful for fork mount with also derotating system
*'''Guiding''': If checked, enable Guiding for this sequence. Use the exposure time in the spinner control in seconds and binning level for the guide software's guiding exposures. Enter zero for the exposure time if you want to use your guide software's automatic mode, if it has one
**'''AO Centering''': Choose None, Every Exposure or Every X Exposure from the drop-down list. This setting only works if you have an AO (Adaptive Optics) guide unit connected and your AO supports mirror homing
***'''None''': Never perform AO Centering
***'''Every Exposure''': Perform AO Centering after every exposure
***'''Every X Exposure''': Specify X = number of exposures between AO Centering operations
*'''Star Lost Detection''': If checked, the maximum allowed percentage of time that the guide star can be lost without considering guiding to have failed
*'''Dithering''': If checked, specify the max number of pixels to move during a dithering operation. Note: this works with or without guiding enabled.
**'''Max Deviation:''' value in pixel of max ditherinng allowed, dithering pixel are randomly choosed according a spiral virtual path
**'''Every X Exposure''': If Dithering is checked, dither every X exposures, where X is the value of the counter field
**'''Use Maxim MultiStar Dithering:''' if your guide control in Voyager is Maxim DL 6.x and newest and you have MultiStar option activated in Maxim Guide setting (track box) Voyager will manage for you a different way to do dithering for using multistar algorithm of Maxim. Movement of mount will be done without using GuideStarMove method and a new full image of guide sensor will be acquired.
*'''Realign to Target''': If checked, perform a precision pointing operation after this number of minutes has elapsed. This is useful if you are doing unguided exposures and want to re-center your target every so often
*'''Donuts Recenter:''' if checked instead of normal realign to target the Donuts process will be used to realign the referenced frame
**'''Every X Exposure''': If Donuts Recenter is checked, recenter every X exposures with Donuts , where X is the value of the counter field

 
{{Note|If the Guiding checkbox is not checked, the sequence runs without Guiding.}}{{Note|Dithering will use the guiding software's routine if guiding is enabled and dithering is available from the guiding software. If guiding is not enabled, dithering will be performed by Voyager}} 
{{Note|As of Voyager 2.1.1g, lack of calibration performed via Voyager is signaled as a Warning and does not cause the Sequence to end with an Error.

To use the previously saved guider calibration in PHD2, OPEN PHD2 APPLICATION !, go to advanced setup, select tab Guiding and check the box “Auto Restore Calibration”.

For the automatic management of the guide vector at meridian change, the mount must also be connected to PHD2 and must provide Meridian Side data. Follow the instructions in PHD2. In this mode Voyager cannot guarantee the correct functioning guiding after a meridian change.}}

==Shot Tab==
The Shot tab of the Sequence Configuration window is where you specify additional parameters for image exposures:

[[File:Shot-tab.png]]

*'''Wait Between Shot''': If checked, wait the specified number of seconds after each exposure before beginning the next. May be useful for some cameras that need a pause before the next command is sent to take an exposure
*'''On Exposure Error - Redo Sub (Max 3 times):''' If checked, if an exposure results in an error, try to re-take the exposure up to 3 times
*'''On Exposure Error - Abort Immediatly Sequence in Case of Camera Shot Error:''' if checked in case of sequence error of type Camera Shor Error (any error occurred during the Camera Exposure action) the sequence will be aborted immediatly. Useful if you have a camera with some hardware/driver problem that cannot be solved by the brand support or is under solution/investigation. In DragScript you can for example intercept the error and decide to disconnect the setup, power cycle the camera and restart all without exit from Voyager.
*'''On Exposure Error - Abort Sequence After Consecutive Error:''' if checked Voyager will count the consecutive error during exposure in a row and if passing the edited value (default 5) the Sequence will be aborted. A good ended exposure will reset the counter to 0. Useful when you want to be sure to intercept temporary failure of the camera hardware/driver and do not lost the night time. In DragScript you can for example intercept the error and decide to disconnect the setup, power cycle the camera and restart all without exit from Voyager.
*'''On Exposure Error - Try Restart Camera and FilterWheel Connection in Case of CameraShot Error for :''' if checked Voyager will count the consecutive error during exposure in a row and if passing the edited value (default 3) will try to restart the camera and filterwheel connection in Voyager. Restart meaning a disconnect and reconnect of the hardware in Voyager (and not in OS that is not possible or a powering down). This features is in a Beta status, is not certified to work at 100%, solving the camera problem is the best solution ... ever!!!
*'''Use SubFrame''': If checked, use a centered subframe of the size selected from the drop-down list: Full Frame, 1/2 size, 1/4 size, 1/8 size, 1/16 size or CUSTOM size.
**'''CUSTOM Size''': If you choose custom size from the drop-down, a counter appears from which you can choose any percentage value for your subframe size

 

==Focus Tab==
The Focus tab of the Sequence Configuration window is where you specify additional parameters for autofocus operations. The settings in [[AutoFocus Setup|AutoFocus setup]] are used unless these settings override them.

The Focus Tab was revised in Voyager 2.3.8b to make room for additional Focus Triggers, reflected here:

[[File:Sequence-autofocus-2.11f.jpg]]

*'''Focus Method''': Choose the autofocus method to use during the sequence
**'''Voyager RoboStar''': Use [[AutoFocus Setup#RoboStar General Setting|Voyager's RoboStar]] method to select the star for autofocus operation. If you are using TheSkyX @Focus2, @Focus3, or FocusMax, make sure they are not configured to also move to a focus star.
**'''Voyager LocalField''': Use Voyager's LocalField multiple-star autofocus operation
**'''Focus Star''': Use the focus star specified by the Focus Star panel below and use Voyager's VCurve single-star autofocus operation
**'''FocusMax AcquireStar''': Use FocusMax for autofocus and request that it use its own AcquireStar method to select a star for autofocus
**'''Focus On Place''': Autofocus using a suitable star, if one can be found, in the current field of view
*'''Use Low Precision Pointing for Pointing Focus Star''': If checked, relax the [[Mount Setup#Management|error tolerance for precision pointing]] to the focus star.
**'''Multiple Max Allowed Error by''': If Use Low Precision Pointing is checked, multiply the error tolerance specified in [[Mount Setup#Management|Mount Setup]] by the number of times specified in the counter. E.g., if you specified an error tolerance of 10 arc-secs in Mount Setup, and a "5" here, the focus star precision pointing operation would stop when the error was less than 50 arc-secs.
*'''Use a Simple Goto for Pointing Focus Star instead of Precise Pointing''': If checked, the focus star will be pointed only with a simple goto without using plate solving in closed loop
*'''Max HFD Variation Percentage Allowed''': If checked, the maximum percent variation of the focus star's HFD (Half Flux Diameter) at final focus between the current and previous autofocus action. Larger values are considered an autofocus failure and will raise an ERROR. If '''Retry Focus for Watchdog''' is checked in Autofocus Setup, the autofocus will be retried the up to the number of times specified in that setup field
*'''Force RoboStar''' on First Focus: If checked, use the RoboStar operation on first autofocus to find a suitable focus star and perform a VCurve autofocus operation
*'''On LocalField Focus Error use RoboStar''': If checked, if a LocalField autofocus operation fails, try RoboStar to find a suitable focus star and perform a VCurve autofocus operation
*'''Focus Star Setting''': Specify a star to use for autofocus before the meridian, after the meridian, or at all times.
**If only the left column - '''Before Meridian''' - is filled out, that star is used for the entire sequence.
**If both columns are filled out, the coordinates on the left are used before the meridian and the star on the right is used after the meridian
***[[File:Object-finder.jpg]]: Click this icon to bring up the [[OnTheFly#Target Coordinates J2000|Object Finder]] and search for your focus star by name. The [[OnTheFly#Target Coordinates J2000|Object Finder]] will populate the RA, DEC and NAME fields from the search result
*'''Focus Filter''':
**'''Use Actual Filter''': Autofocus using the filter for the currently running slot of the sequence
**'''Use Default Filter''': Choose the default filter to use for autofocus operations. If nothing else overrides this selection, use the filter selected from the drop-down list.
*'''Focus Trigger''': Check one or more boxes to determine the condition(s) that trigger an autofocus
**'''Focus By Slot''': If checked, and if the sequence mode is '''Group By Slot''', autofocus at the start of every new sequence slot.
**'''Focus Each X Exposure''': If checked, focus every X exposures, where X is the counter value.
**'''Focus Each X Minutes''': If checked, focus every X minutes, where X is the counter value. This can be especially useful if your sequence mixes slots with very different exposure lengths.
**'''Focus Each X Delta °C or Delta ADU:''' If checked, focus every X degrees °'''C''' change of temperature or change of ADU value reported by the focuser chosen in Setup. Check your focuser documentation to see whether it reports temperature or a value of ADU that is related to temperature. Then choose the counter value based on how much the number returned by the focuser changes when you need to rerun autofocus.
**'''Focus Each X Delta Degrees of Altitude''': If checked, focus every time the target's altitude changes by the specified number of degrees

As of Voyager 2.1.1f, new Monitor Window information lines have been added at the start of each exposure explaining the autofocus criteria currently in effect along with current status of each criterion:[[File:New-autofocus-monitor-info-2.11f.jpg]]

{{Note|If you check more than one Focus Trigger box, autofocus will be performed whenever any of the checked criteria are met. E.g., you could focus both every 30 minutes and every filter change and every 2 degrees temperature change.}} 

{{Note|If no Focus Trigger boxes are checked, autofocus will only be performed at times specified in other areas, such as in the On Start and Meridian Flip tabs. If none of those boxes are checked, no autofocus will be performed during the Sequence run}} 

{{Note|Both Voyager's RoboStar and FocusMax's AcquireStar methods may move the mount to the focus star, perform the autofocus, and move back to the target. These operations can provide a better autofocus by choosing a more suitable star than any in the current field of view. However, they will spend more time to move the mount to the focus star and back compared to focusing on the best star in the field of view}} 

{{Note|Low Precision Pointing can save considerable time during your sequence and in many cases there is no need for high precision pointing to goto a focus star}} 

==On Error Tab==
The On Error tab of the Sequence Configuration window is where you specify actions Voyager should take if an error is raised during a sequence:

[[File:On-error-tab.png]]

*'''Do this on ERROR''':
**'''Nothing''' - if this radio button is checked, Voyager will not take any action when an error happens
**'''Good Night''': if this radio button is checked, Voyager will perform the following shutdown actions:
***'''Run this Program/Script BEFORE''': Click the "..." button to [[OnTheFly#Utilities|choose an external program]] or script to run at the start of the Good Night operation. Click the X button to clear this field. '''Note:''' this field is used to run an external Windows program or script, not a Voyager DragScript. Run your Sequence from the DragScript, not the other way around.
***'''Move CCD to Filter''': If checked, move the filter wheel to the filter selected from the drop-down list
***'''Async Warmup''': If checked, send a command to the CCD cooler to warm the sensor, and do not wait for the warmup operation to complete
***'''Sync Warmup''': If checked, send a command to the CCD cooler to warm the sensor, and wait for the warmup operation to complete
***'''Park''': If checked, park the mount
***'''Run this Program/Script AFTER''': Click the "..." button to [[OnTheFly#Utilities|choose an external program]] or script to run at the end of the Good Night operation. Click the X button to clear this field. '''Note:''' this field is used to run an external Windows program or script, not a Voyager DragScript. Run your Sequence from the DragScript, not the other way around.

 {{Note|If the sequence is run from a DragScript, the information in the On Error tab is not used. Instead, the DragScript instructions for managing the Error condition are used}}

==On End Tab==
The On End tab of the Sequence Configuration window is where you specify actions Voyager should take at the end of a sequence:

[[File:On-end-2.11f.jpg]]

*'''Force Sequence End Timer''': If checked, end the sequence after the time Interval specified has elapsed (HH:MM:SS)
**'''Absolute''': If checked, end the sequence at the absolute time indicated in the counter fields (HH:MM:SS)
**'''Finish Running Exposure''': If checked, finish any exposure in progress when the Force Sequence End Timer is triggered
*'''Do this at END''':
**'''Nothing''': If this radio button is selected, do nothing at the end of the sequence
**'''Warmup''': If this radio button is selected, warmup the CCD cooler at the end of the sequence
***'''Sync Warmup''': If checked, wait for the warmup to finish. If not checked, send the warmup command to the cooler and don't wait
*'''Good Night''': if this radio button is checked, Voyager will perform the following shutdown actions at the end of the sequence:
**'''Run this Program/Script BEFORE''': Click the "..." button to [[OnTheFly#Utilities|choose an external program]] or script to run at the start of the Good Night operation. Click the X button to clear this field. '''Note:''' this field is used to run an external Windows program or script, not a Voyager DragScript. Run your Sequence from the DragScript, not the other way around.
**'''Move CCD to Filter''': If checked, move the filter wheel to the filter selected from the drop-down list
**'''Async Warmup''': If checked, send a command to the CCD cooler to warm the sensor, and do not wait for the warmup operation to complete
**'''Sync Warmup''': If checked, send a command to the CCD cooler to warm the sensor, and wait for the warmup operation to complete
**'''Park''': If checked, park the mount
**'''Close Flat Device Cover''': If checked, close the specified flat device cover
**'''Run this Program/Script AFTER''': Click the "..." button to [[OnTheFly#Utilities|choose an external program]] or script to run at the end of the Good Night operation. Click the X button to clear this field. '''Note:''' this field is used to run an external Windows program or script, not a Voyager DragScript. Run your Sequence from the DragScript, not the other way around. 
***
{{Note|If the sequence is run from a DragScript, the On End tab information is not used. The DragScript instructions for end time and what to do after the sequence ends are followed instead}}

[[Category:All]]
[[Category:Manual|Ja]]

File:Sequence-config-window-2.11f.jpg

2024-06-29T14:07:16Z

Leonardo: Leonardo uploaded a new version of File:Sequence-config-window-2.11f.jpg

== Summary ==
importing from old wiki

MediaWiki:Sidebar

2024-06-29T14:06:34Z

Leonardo:

Version

2024-06-29T14:06:13Z

Leonardo:

==Voyager Version==
The version of Voyager documented by this Wiki is: 2.3.11b -> (Daily Build 2024-05-29) -> 32 and 64 bit version

Voyager Release information is here: https://forum.starkeeper.it/c/releases

DragScript Elements

2024-06-29T14:05:15Z

Leonardo: /* Voyager */

__TOC__

The DragScript "language" is composed of blocks that are dragged from the list on the right side of the DragScript editor to the script being created or edited on the left.

Each category of element is organized in list that can be expanded or contracted by clicking the "+" or "-" next to the element category name:

[[File:Dragscript-editor-elements.png]]

E.g., if you click the + in front of Actions, the list expands like this:

[[File:List-expanded.png]]

As you can see in the case of Actions, there are further subcategories of actions, and clicking the + in front of one of them expands it again:

[[File:Subcategory-expanded.png]]

Here, the list of Setup actions is fully expanded and we see three choices that we can drag to the active script: Connect Setup, Connect Setup with Timeout, and Disconnect Setup

For the remainder of this page, we will describe the available DragScript elements. New elements are added periodically and will be documented in the release notes and here.

Press Sort button to listing all the categories and blocks in alphabetical order.

==DragScript Actions==

===Operating System===
The Operating System actions control the PC running Voyager:

[[File:DSopOs.png]]

*'''Shutdown PC''': Shutdown the PC running Voyager
*'''Restart PC''': Restart (reboot) the PC running Voyager
*'''Hybernate PC:''' Hybernate the PC running Voyager (only in OS that support it)
*'''Suspend PC:''' Susend the PC running Voyager (only in OS that support it)
*'''Kill Process''': Kill a process on the PC running Voyager. Either type in the Process name or click one of the buttons to use a preconfigured process name.

[[File:Kill-process.png]]

*'''Serial Port STRING Transmit''': Send a text string with a terminator (if necessary) to an RS232 Serial Port

[[File:SerPortTx.png]]

*'''Configuration'''
**'''Serial Port Config''': insert the string used to configure and open the serial port (portname,portspeed,databit,parity,datastopbit) for parity use N=None O=Odd E=Even (Example COM1,9600,8,N,1)
**'''Text to Send''': input the text to send to the serial port
**'''Use Terminator''': indicate if you want to use a terminator or not. CR = carriage return, LF=Line feed
*'''Serial Port BINARY Transmit''': Send Binary data string to an RS232 Serial Port

[[File:SerPortBin.png]]

*'''Configuration'''
**'''Serial Port Config''': insert the string used to configure and open the serial port (portname,portspeed,databit,parity,datastopbit) for parity use N=None O=Odd E=Even (Example COM1,9600,8,N,1)
**'''Binary Data To Send(*):''' input the binary data to send to the serial port. Binary Data must be entered ad a string in hexadecimal format separated (Example 0A 0B 0C A1 A2 A3)
*'''UDP IP/Port STRING Transmit''': Send a text string with a terminator (if necessary) to an UDP Port
[[File:Txudpstring.png]]

* '''Configuration'''
**'''IP/Hostname''': IP or hostname of PC where to send data
**'''Port:''' UDP port number to use for transmission
**'''Text to Send''': input the text to send to the UDP Port
**'''Use Terminator''': indicate if you want to use a terminator or not. CR = carriage return, LF=Line feed
*'''UDP IP/Port BINARY Transmit''': Send Binary data string to an RS232 Serial Port
*[[File:UDPIPBinaryTX.png]]
* '''Configuration'''
** '''IP/Hostname''': IP or hostname of PC where to send data
**'''Port:''' UDP port number to use for transmission
** '''Binary Data To Send(*):''' input the binary data to send to the serial port. Binary Data must be entered ad a string in hexadecimal format separated (Example 0A 0B 0C A1 A2 A3)

==Setup==
Setup actions control connecting and disconnecting to your equipment and software:

[[File:Dragscript-setup-2.14c.png]]

*'''Connect Setup''': Commands Voyager to connect to the equipment and software in the currently selected [[Setup#Profile Management|Profile]]
*'''Connect Setup with Timeout''': Command Voyager to connect to the equipment in the currently selected [[Setup#Profile Management|Profile]]. Voyager will timeout if connection does not complete within the specified number of seconds:

[[File:Setup-timeout.png]]

*'''Disconnect Setup''': Command Voyager to disconnect from the equipment and software in the currently selected [[Setup#Profile Management|Profile]]
*'''Force Disconnect Setup''': Command Voyager to forcefully disconnect the Seup without checking if the previous connection was actually successful (all setup checks connected regularly)
*'''Connect Safety Monitor Control''': Connect only the Safety Monitor control. This is useful for monitoring conditions prior to connecting all your equipment
*'''Disconnect Safety Monitor Control''': Disconnect only the Safety Monitor control
*'''Connect Flat Device #1 / #2 Control''': Connect only the Flat Device #1/#2. This is useful for switch on the flat device only when needed
*'''Disconnect Flat Device #1 / #2 Control''': Disconnect only the Flat Device #1/#2 control

 

==Voyager==
Interaction with Voyager Application:

[[File:Immagine 2021-04-05 193048.png]]

* '''Change Voyager Profile''': will allow changing of profile from DragScript. Voyager must have the setup not connect or action will failed.
** [[File:Immaginefefefr.png]]
*** '''Profile:''' Profile select, and list of all profile if retrieved from Voyager
*** '''Get Voyager Profiles List:''' listg of profiles will be retrieved directly from Voyager using the Application Server. Male sure that the Application Server in Voyager is active
*** '''OK''': Click to save your changes and close the window
***'''Cancel''': Click to discard your changes and close the window
* '''Empty Voyager Temporary Folders''': will remove all file from the temporary folders of Voyager (for example the FIT folder where is the temporary Shot for platesolving or pointing)

==Session==
Session actions run sequences to acquire images, flat frames, and shutdown ("Good Night") your system:

[[File:Session-script.png]]

*'''RoboTarget''': Robotic Scheduler Available only in [https://software.starkeeper.it/voyager-advanced/ Voyager Advanced version]
*'''Sequence''': Run a [[Sequence Configuration|Sequence]] with options:

[[File:Dragscript-sequence-211g.jpg]] 

*'''Configuration Panel''':
**Click the folder icon [[File:Folder-icon.png]] to select the Sequence file to run. [[Sequence Configuration|Create your Sequence files]] in Voyager's OnTheFly workspace
**'''Start/TimeSpan''': Click one of the radio buttons to use that option to tell when to start and end the sequence. This is one way to have Voyager image this target until a specific time is reached, or an interval has elapsed. It is a good idea to specify an ending time here, or a minimum altitude in the Sequence definition or the Options field below, so Voyager will not continue trying to take images after the object has set
***'''Start and End from Sequence:''' Use the start and end times specified in the sequence definition file. The start time comes from the [[Sequence Configuration#On Start Tab|On Start tab]] and the end time comes from the [[Sequence Configuration#On End Tab|On End tab]]
***'''Immediately Start and Finish After Interval''': Start the sequence immediately and end it after the HH:MM:SS amount of time specified with the Time Span: counter fields
***'''Start and End at Absolute Time''': Voyager should wait until the specified Start: time and end the sequence at the specified End: time.
***'''Immediately Start and End at Absolute Time''': Start the sequence immediately and end it at the time specified in the counter fields
***'''Immediately Start and Finish With Astronomical Night''': Start the sequence immediately and finish it at Astronomical Night's end, offset +/- by the number of minutes set in the Offset: counter field
*'''Calculated Time Span''': Voyager will show how much time this sequence will take with the chosen Start/TimeSpan option if you choose Start and End at Absolute time. It is not possible to calculate this if you choose one of the "Immediately Start" options
**
**

 {{Note|Enter time in 24 hour format using local time - or the time zone on the computer running Voyager. That's the time that will be used in doing these calculations. Midnight is 00:00:00. 10 pm local time is 22:00:00. 3 AM is 03:00:00.}} {{Note|Note: If the Start: time is more than 12 hours in the future, Voyager will start the sequence, assuming that the start time has passed already in the current night. For example, if you specify a start time of 20:00:00 and it is now 20:15:00, Voyager will start the sequence}} {{Note|If the End time is more than 12 hours in the future, Voyager will assume the End time has already passed for the night and end the sequence. For example, if a sequence has a Start time of 20:00:00 and an End time of 21:00:00 and the current time is 22:00:00, Voyager will end the sequence}} {{Note|Times entered here will override any start or end times defined in the Sequence file. The times you define when you create the sequence are used for OnTheFly running of the Sequence, not for DragScript execution}} {{Note|The Start and End times are checked at the beginning of running a sequence and the sequence exits with status OK if the current time is outside the Start and End time window}}

**'''Options''': Check the boxes to select any of these options (Remember to scrool the panel to find more options in the configuration form):
***'''Overrides Target Coords J2000''': If checked, the RA and DEC coordinates are used instead of those in the sequence file. RA coordinates are in HH MM SS and DEC coordinates are HH MM SS.sss
***'''Overrides Target Name with this''': If checked, the name entered in the field will be used as the target name, which is part of the file name
***'''Force Dynamic Target Comet :''' if checked force the Sequence to use a Comet Dynamic Target type, you MUST select the Comet using the Comet Finder button near the check. If you check the flag and do not select a Comet the Sequence will generate an Error at starting. Target Name and Target key will be populated after the search and the overrides target name will be used with the name of the Dynamic Target. You can for sure change it.
***'''Force Dynamic Target Asteroid :''' if checked force the Sequence to use an Asteroid Dynamic Target type, you MUST select the Asteroid using the Asteroid Finder button near the check. If you check the flag and do not select an Asteroid the Sequence will generate an Error at starting. Target Name and Target key will be populated after the search and the overrides target name will be used with the name of the Dynamic Target. You can for sure change it.
***'''Force Dynamic Target Planet:''' if checked force the Sequence to use an PlanetDynamic Target type, you MUST select the Planet using the Planet Finder button near the check. If you check the flag and do not select a Planet the Sequence will generate an Error at starting. Target Name and Target key will be populated after the search and the overrides target name will be used with the name of the Dynamic Target. You can for sure change it.
***'''Force Dynamic Target DynaSearch:''' if checked force the Sequence to use an Planetarium Text Dynamic Target type, you MUST select the text using the Planetarium Control (your planetarium). If you check the flag and do not select an existent target text in Planetarium objects the Sequence will generate an Error at starting. Target Name and Target key will be populated after the search and the overrides target name will be used with the name of the Dynamic Target. You can for sure change it.
***'''Override Dynamic Target Pointing Type :''' if checked and only if you are using a Dynamic Target (comet or asteroid) Voyager allow you to select when calculating the RA/DEC coordinates od the Dynamic Target. Default for a Dynamic Target is the Calculate RA/DEC only at Sequence Begin
****'''Calculate RA/DEC Only at Sequence Begin :''' Voyager will calculate the RA/DEC of the Dynamic Target only whe the Sequence action will start and will use this RA/DEC for all duration of the Sequence action. If the Sequence will be restarted anothe day or some hours after or generally will be restarted VOyager will calculate again the RA/DEC coordinates. But not in the same Sequence run.
****'''Calculate RA/DEC at Each Precise Goto :''' Voyager will calculate the RA/DEC of the Dynamic Target at each precise pointing goto inside the Sequence Run included at the begin of Sequence
****'''Calculate RA/DEC Every X Seconds :''' Voyager will calculate the RA/DEC of the Dynamic Target at the beginning of the Sequence and each X seconds like edited in the dedicated field. if the X interval is expired and Voyager is in exposure camera mode, will wait the end of exposure to calculate the new coordinates. A realign goto will not be requested if the next flag is not checked.
*****'''And Realign Target :''' if checked Voyager will force a realign with a Precise pointing to the new RA/DEC of the Dynamic Target
*****'''Without Using Plate Solving :''' if checked Voyager will avoid the precise pointing with plate solving for the realign and will use a simple goto without solving
***'''Override Angle Rotation of Target with PA of°:''' if checked , if in the sequence the rotator is managed, this flag force the Rotation Angle to the value selected. The other rotator settings in sequence will not be changed.
***'''Finish Running Exposure in case of elapsed time for Sequence Execution''': If checked, an exposure in progress will be allowed to finish if it starts before the sequence end time but finishes after the sequence end time
***'''Override Lower Altitude value under which Exit from Sequence''': If checked, if the sequence target sets below the altitude given here, the sequence will end. This value will override the minimum altitude value chosen in the sequence file
***'''Override Higher Altitude value above which Exit from Sequence''': If checked, if the sequence target rises above the altitude given here, the sequence will end. This value will override the maximum altitude value chosen in the sequence file
***'''Override Lower HourAngle value under which Exit from Sequence:''' If checked, if the sequence target HourAngle are lower the value given here, the sequence will end. This value will override the Lower HourAngle value chosen in the sequence file
***'''Override Higher HourAngle value over which Exit from Sequence:''' If checked, if the sequence target HourAngle are higher the value given here, the sequence will end. This value will override the Higher HourAngle value chosen in the sequence file
***'''Override Camera Cooling Temperature with Decimal Variable:''' if checked for colling temperature will be used the value inside the decimal variable selected in the drop-box combo box control
***'''Override Lower Azimuth value under which Exit from Sequence:''' If checked, if the sequence target Azimuth are lower the value given here, the sequence will end. This value will override the Lower Azimuth value chosen in the sequence file
***'''Override Higher Azimuth value over which Exit from Sequence:''' If checked, if the sequence target Azimuth are higher the value given here, the sequence will end. This value will override the Higher Azimuth value chosen in the sequence file
***'''Use External Interval Angle:''' if each the azimuth constraints will be cheched you can decide with this flag to use external angle instead of internal angle between before and after azimuth. Example if you choose 70° before and 150° after with out external flag this mean sequence run if angle is between 70 and 150°, if you chec it and invert to external sequence will be terminate if azimuth is between 70 and 150°
**'''Default''': Click this button to populate this window with the default options
**'''OK''': Click to save your changes and close the window
**'''Cancel''': Click to discard your changes and close the window 
**'''Override FILE PATTERN:''' flag this chheckbox to activate sub foldering and file naming with File Pattern method, insert in the big text field near the flag the string to override of the file pattern to use instead of the one configured in the File Pattern Manager. This will affect only the actual sequence and do not change the main File Patterm Manager configuration. This is for example mandatory in case of join of the OpenSkyGems network and sharing of the observatory setup.
*'''Research & Survey''': Run a [[Research Survey|Research & Survey]] sequence with options

[[File:Research-survey-dragscript.png]]

*'''Configuration Panel''':
**Click the folder icon [[File:Folder-icon.png]] to select the Research & Survey sequence file to run. Create your sequence files in Voyager's [[Research Survey|Research & Survey workspace]]
**TYPO: Star/TimeSpan should be Start/TimeSpan
**'''Start/TimeSpan''': Click one of the radio buttons to use that option to tell when to start and end the Research & Survey sequence. This is one way to have Voyager image this target until a specific time is reached, or an interval has elapsed. It is a good idea to specify an ending time here, or a minimum altitude in the Research & Survey sequence definition or the Options field below, so Voyager will not continue trying to take images after the object has set
***'''Immediately Start and Finish After Interval''': Start the sequence immediately and end it after the HH:MM:SS amount of time specified with the Time Span: counter fields
***'''Start and End at Absolute Time''': Voyager should wait until the specified Start: time and end the sequence at the specified End: time.
***'''Immediately Start and End at Absolute Time''': Start the sequence immediately and end it at the time specified in the counter fields
***'''Immediately Start and Finish With Astronomical Night''': Start the sequence immediately and finish it at Astronomical Night's end, offset +/- by the number of minutes set in the Offset: counter field
**'''Calculated Time Span''': Voyager will show how much time this sequence will take with the chosen Start/TimeSpan option if you choose Start and End at Absolute time. It is not possible to calculate this if you choose one of the "Immediately Start" options
*'''Options''':
**'''Finish Running Exposure in case of elapsed time for Sequence Execution''': If checked, an exposure in progress will be allowed to finish if it starts before the sequence end time but finishes after the sequence end time
**'''Default''': Click this button to populate this window with the default options
**'''OK''': Click to save your changes and close the window
**'''Cancel''': Click to discard your changes and close the window 

 {{Note|See the Important Notes above in the Sequence discussion to understand how Voyager treats the values in the time fields when they have already passed in tonight's session or if they are also specified in the Research & Survey sequence definition file}}

*'''Flat''': Run an Auto Flat sequence. [[Auto Flat|Configure the Auto Flat sequence files]] in the OnTheFly workspace

[[File:Flat-sequence-dragscript.png]]

*Click the folder icon [[File:Folder-icon.png]] and choose the Auto Flat sequence file to run. [[Auto Flat|Configure the Auto Flat sequence files]] in the OnTheFly workspace
*TYPO: Configuration dialog says "Good Night" but should be Auto Flat
*'''Default''': Click this button to populate this window with the default options (blanks out the Flat Sequence File field)
*'''OK''': Click to save your changes and close the window
*'''Cancel''': Click to discard your changes and close the window

 

*'''Good Night''': Run a series of one or more shutdown actions:

[[File:Dragscript-good-night.png]]

*'''CCD Filter Select''': Moves the filter wheel to the filter chosen from the drop-down box on the right
*'''Sync Warmup''': Send the CCD cooler a warmup command and wait until it finishes
*'''Async Warmup''': Send the CCD cooler a warmup command and continue execution without waiting for it to finish
*'''Parking''': Park the mount as specified in [[Mount Setup#Park.2FUnpark|Mount Setup]]

 

==Plate Solving==
Plate Solving actions perform a plate solving action as defined in the [[Plate Solve Setup|Plate Solving setup]] of the active profile:

[[File:Dragscript-plate-solving.png]]

 

*'''Plate Solving''' : Perform a plate solve action at the current scope location using the Plate Solve software defined in the [[Plate Solve Setup|Plate Solving setup]] of the active profile. ''Mount will not be synched''
*'''Plate Solving with Mount Sync:''' Perform a plate solve action at the current scope location using the Plate Solve software defined in the [[Plate Solve Setup|Plate Solving setup]] of the active profile. ''Send a Sync command to the mount unless you have chosen to not send a Sync command to your mount in [[Mount Setup#Management|Mount Setup]]. You may lost pointing model if you have one and your driver not allow additional and external sync''

==Blind Solving==
Blind Solving actions perform a plate solving action as defined in the [[Plate Solve Setup|Plate Solving setup]] of the active profile:

[[File:BlindSolveBlocks.png]]

 

*'''Blind Solving with Mount Sync:''' Perform a blind solve action at the current scope location using the Plate Solve software defined in the [[Plate Solve Setup|Plate Solving setup]] of the active profile. ''Send a Sync command to the mount unless you have chosen to not send a Sync command to your mount in [[Mount Setup#Management|Mount Setup]]. You may lost pointing model if you have one and your driver not allow additional and external sync''

 

==WEB Solving==
Plate Solving actions perform a plate solving action as defined in the [[Plate Solve Setup|Plate Solving setup]] of the active profile:

[[File:WebSolvingBlocks.png]]

 

*'''Web Solving with''' '''Sync''': Perform a web blind solve action at the current scope location using the nova.astrometry.net site. An active Internet connection is required. Send a Sync command to the mount unless you have chosen to not send a Sync command to your mount in [[Mount Setup#Management|Mount Setup]]
**[[File:Web-solving-with-sync.png]]
***'''Timeout''': Specify the number of minutes Voyager should wait after initiating the Web Solve before timing out. Use an IF TIMEOUT decision action to define what to do if the web solve times out

==Guiding==
Guiding actions send commands to the guide software:

[[File:Dragscript-guiding-dithering.png]]

*'''Calibrate Guide''': Command the guide software to perform a calibration action. It is recommended to include a Calibrate Guide action at the start of your sequence unless you are sure that your guider is calibrated from a previous session. Double click to bring up the configuration window:

[[File:Dragscript-calibrate-guide.png]]

*'''Time''': Exposure time for Calibration exposures by the guiding software
*'''Binning''': Binning level for Calibration exposures by the guiding software
*'''Use RoboGuide Star Selection''': If selected, use Voyager's RoboGuide process to choose a guide star for the Calibration action. This is mandatory at this time since some guiding software cannot select a guide star.
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Acquiring Guide Star''': Commands the guiding software to select a guide star. Double click to bring up the configuration window:

[[File:Dragscript-acquire-guide-star.png]]

*'''Time''': Exposure time for guide star acquisition exposures by the guiding software
*'''Binning''': Binning level for guide star acquisition exposures by the guiding software
*'''Use RoboGuide Star Selection''': If selected, use Voyager's RoboGuide process to choose a guide star. This is mandatory at this time since some guiding software cannot select a guide star.
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''Guide Start''': Commands the guiding software to begin guiding. Double click to bring up the configuration window:

[[File:Dragscript-guide-start.png]]

*'''Time''': Exposure time for guiding exposures by the guiding software
*'''Binning''': Binning level for guiding exposures by the guiding software
*'''Use RoboGuide Star Selection''': If selected, use Voyager's RoboGuide process to choose a guide star. This is mandatory at this time since some guiding software cannot select a guide star.
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Guide Stop''': Command the guiding software to stop guiding

 

*'''Guide Dithering''': Command the guiding software to perform a dithering action. Dithering is used to move the mount a tiny random amount in a random direction - usually only a couple of pixels. This prevents hot or cold pixels in your sensor from showing up in the same position in all of your images, making it easier to remove hot or cold pixels when stacking your images. Double click to bring up the configuration window:

[[File:Dragscript-guide-dithering.png]]

*'''Max Pixel''': Specify the maximum number of pixels that a dithering operation can move the mount
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 

*'''Unguided Dithering''': Perform a dithering action directly, vs. Guide Dithering which sends a dithering command to the guide software. Dithering is used to move the mount a tiny random amount in a random direction - usually only a couple of pixels. This prevents hot or cold pixels in your sensor from showing up in the same position in all of your images, making it easier to remove hot or cold pixels when stacking your images.

[[File:Unguided-dither-3.png]]

*'''Max Pixel''': Specify the maximum number of pixels that a dithering operation can move the mount
*'''From Actual Position''': This is the safest and default choice - it sends a command to move the mount up to the specified number of pixels from the current position. This should be a small movement, as the recommended number of pixels to dither is 3
*'''From Last Goto Action Position''': Send a command to move the mount a random number of pixels up to '''Max Pixel''' in a random direction relative to the position of the last Goto action. This should only be used following a successful Goto action in your DragScript. You can damage your mount if you use this without a successful Goto action preceding it.
*'''From Last Precision Pointing Action Position''': Send a command to move the mount a random number of pixels up to '''Max Pixel''' in a random direction relative to the position of the last Precision Pointing action. This should only be used following a successful Precision Pointing action in your DragScript. You can damage your mount if you use this without a successful Precision Pointing action preceding it.
*'''Use Actual Position on Empty/Fail condition''': If checked, if the position reported by the Last Goto Action or Last Precision Pointing Action is empty, or if the Last Goto Action or Last Precision Pointing Action ended with an error, use the Actual Position of the mount as the starting point for dithering. In other words, don't attempt to dither based on the Last Goto action position or the Last Precision Pointing action position if either of those positions is empty, as this would send a command to the mount that could cause a pier crash and/or damage to your equipment. '''Highly recommend leaving this checked.'''
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 
==Mount==
Mount actions send commands to the mount defined in the [[Mount Setup|Mount setup]] of the active profile:

[[File:Dragscript-mount.png]]

*'''Stop Tracking''': Command the mount to stop tracking
*'''Start Tracking''': Command the mount to start tracking
*'''Parking''': Command the mount to slew to the Park position
*'''Unparking''': Command the mount to Unpark
*'''Sync on Park''': Command the mount to save the current position as the Park position
*'''Homing''': Command the mount to move to the Home position (depends on the driver if the command will work, not all drivers have this command implemented !)
*'''Goto RA/DEC''': Command the mount to move to the specified RA and DEC coordinates (J2000)

[[File:Dragscript-gotoradec.png]]

*'''RA J2000''': Enter the RA coordinates in HH MM SS or HH MM SS.sss
*'''DEC J2000''': Enter the RA coordinates in DD MM SS or DD MM SS.sss
*'''Default''': Use the default settings: clears the RA and DEC fields
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Goto ALT/AZ''': Command the mount to move to the specified Altitude and Azimuth coordinates

[[File:Goto-altaz.png]]

*'''ALT:''' Enter the Altitude coordinates in DD MM SS or DD MM SS.sss
*'''AZ''': Enter the Azimuth coordinates in DD MM SS or DD MM SS.sss
*'''Force Use of Normal RA/DEC Slew With Conversion''': If checked, convert the requested ALT and AZ values to RA and DEC values and send a goto RA/DEC command to the mount
*'''Default''': Use the default settings: clears the AZ and ALT fields
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Goto Near Zenith''': Command the mount to move to a point close to the current Zenith (directly overhead). 
{{Note|Goto Near Zenith followed by a Blind Solving with Sync action is a good way to initialize your mount's pointing model at the start of a session. It is only a single point, but if your mount is accurately polar aligned, doing this before the first Precise Pointing operation may helps the Precise Pointing to succeed}}

*

*'''Goto By Name''': Command the mount to move to an object by name with an optional RA and DEC offset. This action requires Voyager to be connected to the [[Planetarium Setup|Planetarium software]] defined in the current profile. The Object Name must match a name that can be successfully searched in the connected Planetarium software.

[[File:Dragscript-gotoname.png]]

*'''Object Name''': Name of the object to goto. Must be a name that can be successfully searched in the connected Planetarium software
*'''Offset RA (optional)''': An optional +/- offset in HH MM SS or HH MM SS.sss to be added or subtracted from the RA coordinates returned by the Planetarium software
*'''Offset DEC (optional)''': An optional +/- offset in DD MM SS or DD MM SS.sss to be added or subtracted from the DEC coordinates returned by the Planetarium software
*'''Goto Dynamic Target''': Command the mount to move to a RA/DEC of a Dynamic Target calculating with RoboOrbits the coordinates at now [[File:Immaginedd.png]]
**'''Comet :''' open the Comet Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
**'''Asteroid :''' open the Asteroid Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
**'''Planet:''' open the Planet Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
**'''Object Name :''' Read-only name of the Dynamic Target, coming from the search
**'''Object Key :''' Read-only key (code/number) of the Dynamic Target, coming from the search
**'''Object Dynamic Type :''' Read-only type of the Dynamic Target, coming from the search
**'''Offset RA (optional)''': An optional +/- offset in HH MM SS or HH MM SS.sss to be added or subtracted from the RA coordinates calculated
**'''Offset DEC (optional)''': An optional +/- offset in DD MM SS or DD MM SS.sss to be added or subtracted from the DEC coordinates calculated

*'''Goto By Offset''': Command the mount to move from actual position by an RA and DEC offset.

[[File:Immagineerferf.png]]

*'''Offset RA''' : +/- offset in HH MM SS or HH MM SS.sss to be added or subtracted from the actual RA coordinates
*'''Offset DEC''' : +/- offset in DD MM SS or DD MM SS.sss to be added or subtracted from the actual DEC coordinates

 

*'''Precise Pointing''': Command the mount to perform a [[Plate Solve Setup#Precision Pointing|precise pointing]] operation to the specified RA/DEC coordinates - slew to the object, plate solve to get actual coordinates, re-slew to correct pointing error:

[[File:Dragscript-precisepointing.png]]

*'''RA J2000''': Enter the RA coordinates in HH MM SS or HH MM SS.sss
*'''DEC J2000''': Enter the DEC coordinates in DD MM SS or DD MM SS.sss
*'''Max Error using Multiple of Profile Error by''': If selected, multiply the maximum allowed pointing error by the number specified in the counter field. E.g., if the [[Mount Setup#Management|Precision Pointing Max Allowed Error]] specified in Mount Setup is 50 arc-seconds, a value of 2 in the counter field here would change the maximum pointing error to 100 arc-seconds. Precise pointing returns an OK (success) result when the error is less than the Max Error.
*'''Max Error is''': If selected, use the value specified in the counter field as the maximum pointing error in arc-seconds. Precise pointing returns an OK (success) result when the error is less than the Max Error.
*'''RoboClip:''' open RoboClip manager windowd and allow to select a target,
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Precise Pointing by Name''': Command the mount to perform a [[Plate Solve Setup#Precision Pointing|precise pointing]] operation to the specified named object - slew to the object, plate solve to get actual coordinates, re-slew to correct pointing error. This action requires Voyager to be connected to the [[Planetarium Setup|Planetarium software]] defined in the current profile. The Object Name must match a name that can be successfully searched in the connected Planetarium software.

*[[File:Dragscript-precisepointing-name.png]]
**'''Object Name''': Name of the object to goto. Must be a name that can be successfully searched in the connected Planetarium software
**'''Offset RA (optional)''': An optional +/- offset in HH MM SS or HH MM SS.sss to be added or subtracted from the RA coordinates returned by the Planetarium software
**'''Offset DEC (optional)''': An optional +/- offset in DD MM SS or DD MM SS.sss to be added or subtracted from the DEC coordinates returned by the Planetarium software
**'''Max Error using Multiple of Profile Error by''': If selected, multiply the maximum allowed pointing error by the number specified in the counter field. E.g., if the [[Mount Setup#Management|Precision Pointing Max Allowed Error]] specified in Mount Setup is 50 arc-seconds, a value of 2 in the counter field here would change the maximum pointing error to 100 arc-seconds. Precise pointing returns an OK (success) result when the error is less than the Max Error.
**'''Max Error is''': If selected, use the value specified in the counter field as the maximum pointing error in arc-seconds. Precise pointing returns an OK (success) result when the error is less than the Max Error.
**'''Default''': Use the default settings
**'''OK''': Save changes and close the window
**'''Cancel''': Discard changes and close the window

*'''Precise Pointing Dynamic Target''': Command the mount to perform a [[Plate Solve Setup#Precision Pointing|precise pointing]] operation to the specified Dynamic Target. RA/DEC will be calculated in real-tim using the RoboOrbits, more info [[Introduction to RoboOrbits|here]].

*[[File:Immaginenn.png]]
**'''Comet :''' open the Comet Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
**'''Asteroid :''' open the Asteroid Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
**'''Asteroid :''' open the Asteroid Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
**'''Object Name :''' Read-only name of the Dynamic Target, coming from the search
**'''Object Key :''' Read-only key (code/number) of the Dynamic Target, coming from the search
**'''Object Dynamic Type :''' Read-only type of the Dynamic Target, coming from the search
**'''Offset RA (optional)''': An optional +/- offset in HH MM SS or HH MM SS.sss to be added or subtracted from the RA coordinates returned by the Planetarium software
**'''Offset DEC (optional)''': An optional +/- offset in DD MM SS or DD MM SS.sss to be added or subtracted from the DEC coordinates returned by the Planetarium software
**'''Max Error using Multiple of Profile Error by''': If selected, multiply the maximum allowed pointing error by the number specified in the counter field. E.g., if the [[Mount Setup#Management|Precision Pointing Max Allowed Error]] specified in Mount Setup is 50 arc-seconds, a value of 2 in the counter field here would change the maximum pointing error to 100 arc-seconds. Precise pointing returns an OK (success) result when the error is less than the Max Error.
**'''Max Error is''': If selected, use the value specified in the counter field as the maximum pointing error in arc-seconds. Precise pointing returns an OK (success) result when the error is less than the Max Error.
**'''Default''': Use the default settings
**'''OK''': Save changes and close the window
**'''Cancel''': Discard changes and close the window

 

*'''Precise Pointing Mount & Rotator''': Command the mount to perform a [[Plate Solve Setup#Precision Pointing|precise pointing]] operation to the specified named object - slew to the object, plate solve to get actual coordinates, re-slew to correct pointing error, rotating the rotator and align to the requested PA within the specified tollerance.

*[[File:PrecisePointingMountRotator.png]]
**'''RA J2000''': Enter the RA coordinates in HH MM SS or HH MM SS.sss
**'''DEC J2000''': Enter the DEC coordinates in DD MM SS or DD MM SS.sss
**'''Max Error using Multiple of Profile Error by''': If selected, multiply the maximum allowed pointing error by the number specified in the counter field. E.g., if the [[Mount Setup#Management|Precision Pointing Max Allowed Error]] specified in Mount Setup is 50 arc-seconds, a value of 2 in the counter field here would change the maximum pointing error to 100 arc-seconds. Precise pointing returns an OK (success) result when the error is less than the Max Error.
**'''Max Error is''': If selected, use the value specified in the counter field as the maximum pointing error in arc-seconds. Precise pointing returns an OK (success) result when the error is less than the Max Error.
** '''Rotation Angle:''' an arbitrary angle that can be a Rotator PA or Sky PA, depends on following setting.
** '''Rotation Type:''' define if the rotation angle is the rotator angle (rotator PA) reported from the driver (and with offset if asked to Voyager in Sync) or the Sky angle (Sky PA) chosen with web dashboard VirtualFOV or planetarium or another system. If you select Sky PA Voyager will use the Plate solve PA result to rotate the rotator to the right angle. If you select the Rotator PA Voyager will just rotating rotator using drive angle at desidered value, no correction using the plate solved PA will be done
** '''PA Tollerance +/-:''' if the PA of rotator is inside the interval given the position will be declared ok and rotator will not be rotate.
** '''Rotator & Meridian Flip:''' "Mantain the Same Image Orientation After the Meridian" if checked force Voyager to shot the target with same orientation in the images taken before anf after meridian. In this case if you have chosen Rotator PA like Rotation type the rotator will be flipped if the mount is after the meridian, if you chosen Sky PA the PA will retained also after the meridian triggering a rotator flip.Use this flag is useful also to use always the same guide star in case of use of OAG or system with high focal lenght.
**'''RoboClip:''' open RoboClip manager windowd and allow to select a target, with RA and DEC will be also acquired the PA
***'''Default''': Use the default settings
***'''OK''': Save changes and close the window
***'''Cancel''': Discard changes and close the window

 

*'''Stop Tracking (Only FS2 Mount)''': Command an FS2 mount to stop tracking
*'''Start Tracking (Only FS2 Mount)''': Command an FS2 mount to start tracking
*'''FS2 Meridian Flip WEST''': Command an FS2 mount to perform a meridian flip to the West
*'''FS2 Meridian Flip EAST''': Command an FS2 mount to perform a meridian flip to the East
*'''Connect Maxim Telescope''': Connect the Telescope/Mount defined in Maxim DL configuration (you must have camera configured in Voyager like Maxim DL)
*'''Disconnect Maxim Telescope''': Disconnect the Telescope/Mount defined in Maxim DL configuration (you must have camera configured in Voyager like Maxim DL) {{Note|The FS2 Mount commands should only be used if your mount is controlled by the Astro Electronic FS2 motor control system. Using these commands with other mounts may fail and cause damage to the mount and other equipment}}

==Dome==
Dome actions send commands to the dome defined in the [[Dome Setup]] area of the active profile:

[[File:Dragscript-dome-217d.jpg]]

*'''Open Shutter''': Command the dome's shutter or the observatory's roll-off roof to open
*'''Close Shutter''': Command the dome's shutter or the observatory's roll-off roof to close
*'''Dome Slave ON''': Send a command to the dome software to "Slave" to the mount. The dome's azimuth position will track with the mount's movements in azimuth
*'''Dome Slave OFF''': Send a command to the dome software to turn off "Slave" to the mount. The dome's azimuth position will stop tracking the mount's azimuth movements
*'''Dome Goto Azimuth''': Command the Dome to rotate to the specified Azimuth

[[File:Dragscript-dome-az.png]]

*'''Azimuth''': Azimuth position the mount should move to in degrees
*'''Cancel''': Discard changes and close the window
*'''OK''': Save changes and close the window

 

*'''Dome Find Home''': Command the dome to find its Home position. If your dome supports the Find Home command, the dome moves to a known position
*'''Dome Park''': Send a Park command to the dome.
*'''Dome Unpark:''' Send an Unpark command to the dome

 
==Camera==
Camera actions can control the camera's cooling system and take exposures

[[File:Dragscript-camera.png]]

*'''Cool Down''': Command the camera's cooling system to cool down to a desired temperature:

[[File:Dragscript-cooldown.png]]

*'''Final Temperature''': Desired sensor temperature in °C
*'''Use Variable:''' check this flag if you want to set the cooling temperature reading the value inside the variable selectable in the drop-down combo instead to use a fixed value
*'''Async Cooling''': If checked, command the cooling system to go to the Final Temperature and do not wait for the cooling system to report that it has reached the desired temperature
*'''Use CCD Firmware Cooldown''': If selected, let the CCD's cooling system manage the speed of the cooldown process
*'''Use Voyager Ramp Mode Cooldown''': If selected, let Voyager's cooldown process manage the speed of the cooldown process. Voyager's process is defined in [[Camera Setup#Cooling System|Camera Setup]]
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Warmup''': Command the camera's cooling system to warmup

[[File:Dragscript-warmup.png]]

*'''Async Cooling''': If checked, command the camera's cooling system to warmup and do not wait for the warmup operation to finish
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Expose''': Take an exposure

[[File:Dragscript-expose-216d.jpg]]

*'''Exposure Type''': Choose Light, Bias, Dark or Flat from the drop-down list
*'''Filter Index''': Choose the filter for the exposure from the drop-down list
*'''Expose''': Enter the exposure length in seconds in the counter field
*'''Use Variable:''' select if you want to get the exposure time from the decimal variable selected in the near list control
*'''Binning''': Select the binning level for the exposure from the counter field
*'''SubFrame''': Select the frame size from the drop-down list: Full Frame, 1/2, 1/4, 1/8, 1/16 or CUSTOM. If you select CUSTOM subframe size, enter the desired subframe size in percent in the counter field that appears
*'''Gain:''' Set the camera's Gain value to the number in the spinner control. Works only if you are using the ASI Camera native driver.
*'''Offset:''' Set the camera's Offset value to the number in the spinner control. Works only if you are using the ASI Camera native driver.
*'''File Directory''': Click the folder icon to select the folder where Voyager should save the image resulting from this exposure
*'''File Name''': Enter the file name to use when saving the image resulting from this exposure
*'''Make Unique File Name''': If checked, add a suffix to the file name if needed to avoid overwriting an existing file
*'''FIT Object Name''': The name to use to populate the OBJECT field in the FITS header
*'''FIT Airmass calculation''': Compute the current airmass value and add to the FITS file header. Airmass is the amount of atmosphere you are imaging through. It is one when imaging directly overhead, and increases as you image closer to the horizon.
*'''Focuser Position Add to FIT Name:''' add the focuser position to the FIT name, only if you are using RoboFire like Autofocus control in Voyager
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

* '''TheSkyX/64 Camera FW Reconnect''': Reconnect camera and filterwheel if the control used for camera in Voyager is TheSkyX or TheSky64

{{Note|Dragscript editor doesn’t have access to profile configuration, for this reason you dont find setting about readout mode and speed in exposure block. Exposure block use auto mode of readout mode and default speed mode. This mean chooses are based on shot type and binning. It retrieve automatically the correct values you set up on Voyager camera setting tab.}} 

{{Note|Filter labels are shown in this dialog if the DragScript editor is opened from Voyager and filter labels are defined in the current profile. Otherwise only filter indexes are shown. The first filter is index zero (0)}}

{{Note|If you check the use variable flag the exposure time used for the exposure will be added to the name of FIT file}} 

==AutoFocus==
These DragScript commands perform Voyager's autofocus operations:

[[File:Dragscript-autofocus.png]]

*'''AutoFocus with RoboStar''': perform an autofocus operation using Voyager's RoboStar method to choose the focus star:

[[File:Dragscript-autofocus-robostar.png]]

*'''Monochromatic Camera''': Select if a monochrome camera is connected. Select a filter to use for the autofocus operation from the drop-down list
*'''DSLR/Color Camera''': Select if a DSLR or Color (OSC) camera is connected
*'''No Filter''': Select if a monochrome camera is connected without filters
*'''Use Low Precision Pointing''': If checked, Voyager's RoboStar operation will slew to the focus star with a more relaxed precision pointing operation. Specify the multiple for the maximum allowed precision pointing error in the counter field. E.g., if the precision pointing max allowed error configured in [[Mount Setup#Management|Mount Setup]] is 50 arc-seconds, a "Multiple Max Allowed Error by" setting of two would relax the maximum allowed pointing error to 100 arc-seconds
*'''AutoFocus OnPlace''': Perform the autofocus operation at the current scope location. Do not use RoboStar to select a focus star
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Simple Goto RoboStar Star''': Perform a simple goto operation to move the mount to the focus star selected by RoboStar:

[[File:DSSimpleGotoRoboStar.png]]

*'''Monochromatic Camera''': Select if a monochrome camera is connected. Select a filter to use for the precise pointing operation from the drop-down list
*'''DSLR/Color Camera''': Select if a DSLR or Color (OSC) camera is connected
*'''No Filter''': Select if a monochrome camera is connected without filters
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Precise Pointing RoboStar Star''': Perform a precise pointing operation to move the mount to the focus star selected by RoboStar:

[[File:Dragscript-precisepointing-robostar.png]]

*'''Monochromatic Camera''': Select if a monochrome camera is connected. Select a filter to use for the precise pointing operation from the drop-down list
*'''DSLR/Color Camera''': Select if a DSLR or Color (OSC) camera is connected
*'''No Filter''': Select if a monochrome camera is connected without filters
*'''Use Low Precision Pointing''': If checked, Voyager will slew to the focus star with a more relaxed precision pointing operation. Specify the multiple for the maximum allowed precision pointing error in the counter field. E.g., if the precision pointing max allowed error configured in [[Mount Setup#Management|Mount Setup]] is 50 arc-seconds, a "Multiple Max Allowed Error by" setting of two would relax the maximum allowed pointing error to 100 arc-seconds
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''RoboFire Focuser Move To''': Move the focuser to a specified absolute or relative position:

[[File:Dragscript-robomove.png]]

*'''Position''': Desired focuser position in steps
*'''Mode''': Choose absolute or relative
**'''Absolute''': Command the focuser to move to the specified position. Your focuser must support absolute positioning.
**'''Relative''': Command the focuser to move in or out by the specified number of steps. Negative numbers move the focuser IN and positive move it out, unless you specify "Reverse Focuser Direction" in [[AutoFocus Setup#RoboFire Configuration Center|Autofocus Setup]]
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''RoboFire Focuser Move From Variable''': Move the focuser to an absolute or relative position stored in a variable:

[[File:Dragscript-robomove-variable.png]]

*'''Get Position From Variable''': select the variable that contains the position
*'''Mode''': Choose absolute or relative
**'''Absolute''': Command the focuser to move to the specified position. Your focuser must support absolute positioning.
**'''Relative''': Command the focuser to move in or out by the specified number of steps. Negative numbers move the focuser IN and positive move it out, unless you specify "Reverse Focuser Direction" in [[AutoFocus Setup#RoboFire Configuration Center|Autofocus Setup]]
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

{{Note|Be sure to select the right Variable and that the variable is valorized before using this block or you can lost focus. Be sure also to have inserted limits on RoboFIre configuration to avoid damage to your focuser.}}

*'''AutoFocus with RoboFire LocalField''': Perform Voyager's LocalField (multiple star) autofocus routine

[[File:Dragscript-localfield.png]]

*'''Monochromatic Camera''': Select if a monochrome camera is connected. Select a filter to use for the precise pointing operation from the drop-down list
*'''DSLR/Color Camera''': Select if a DSLR or Color (OSC) camera is connected
*'''No Filter''': Select if a monochrome camera is connected without filters
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 
==Rotator==
Rotator actions can move the rotator to a specified Position Angle or flip the rotator 180 degrees:

[[File:Dragscript-rotator.png]]

 

*'''Rotator Move To''': Move the rotator to the specified position angle in degree
**[[File:Dragscript-rotatormove.png]]
***'''PA''': Move the rotator to this Position Angle in degrees
***'''OK''': Save changes and close the window
***'''Cancel''': Discard changes and close the window

*
*'''Rotator 180° Flip''': Move the rotator to a position 180 degrees opposite its current position
*'''Rotator Sync''': Synchronize the mechanical position to the submitted position (create an offset to the mechanical position)
**[[File:RotatorSyncBlockConf.png]]
***'''Rotator Sync To:''' with this option Voyager will sync the rotator PA to the PA in the next field
***'''PA:''' Position Angle to use for sync
***'''Use Variable:''' get PA value from the selected variable
***'''Reset Rotator Sync:''' with this option Voyager will reset the Sync (remove the offset applied to the mechanical position of rotator)
***'''Default:''' reset all parameters in the form to the default values
***'''Cancel:''' exit from the configuration form without saving anything
***'''OK:''' accept the inserted value and store data

* '''Precise Rotate SkyPA''': Move the rotator to the specified SkyPA position
** [[File:PRSKYPADS.png]]
*** '''Rotation Angle''': SKY PA in degree to use for positioning the rotator
*** '''PA Tollerance +/-''': max allowed difference in degree between solved PA and requested PA
*** '''Save Final Rotator PA to this DragScript Decimal:''' if flagged save the Rotator PA degree of pointing (if positioned ok) to the decimal variable selected in the combobox
*** '''OK''': Save changes and close the window
*** '''Cancel''': Discard changes and close the window

==Flat Device==
Flat Device commands can open and close the flat device cover:

[[File:Dragscript-flat-device.jpg]]

*'''Open Flat Device Cover''': Command the flat device to open
*'''Close Flat Device Cover''': Command the flat device to close
*'''Switch On Light Flat Device''': Turn the light on for the specified Flat Device

[[File:Dragscript-switch-on-flat-device.jpg]]

*'''Device ID''': Choose the Flat Device number to control with this command. See [[Flat Device Setup]] for more information on flat devices.

 

*'''Switch Off Light Flat Device''': Turn the light off for the specified Flat Device

[[File:Dragscript-switch-off-flat-device.jpg]]

*'''Device ID''': Choose the Flat Device number to control with this command. See [[Flat Device Setup]] for more information on flat devices.

 

*'''Select Brightness Flat Device''': Set the brightness level for the specified Flat Device.

[[File:Dragscript-select-brightness.jpg]]

*'''Device ID''': Choose the Flat Device number to control with this command. See [[Flat Device Setup]] for more information on flat devices.
*'''Brightness''': Brightness level for the specified Flat Device. 
{{Note|If you have a flat device that can open and close, don't forget to issue an Open Flat Device command in your DragScript before taking exposures including plate solving and autofocus!}}

==Script==
The Script action can run an external script or program:

[[File:Dragscript-script-external.png]]

[[File:External-script-1.png]]

*'''File Program/Script''': Click the folder icon to select the program or script to run
*'''Arguments''': Command line arguments to be passed to the program or script when invoking it
* '''JOLLY Strings''':there are some special strings called jolly that can be used in argument line will be replaced with some data from Voyager environment or DragScript variables
** '''Internal IPs:''' ##INTERNAL-IP## write a list of all internal IPs avalaible in the system
** '''External IP''': ##EXTERNAL-IP## write a list of external IP assigned to your PC(router) if you have internet connection up
** '''NOW''': ##NOW## write the actual date and time
** '''Mount Altitude''': ##MOUNT-ALT## write the actual altitude of Telescope Mount if connected
** '''Mount Azimuth''': ##MOUNT-AZ## write the actual azimuth of Telescope Mount if connected
** '''Variable''': ##VAR-name## where you must replace the ''name'' with the real name of your variable (case sensitive) , write the actual value of you variable (decimal, string or counter)
*'''Wait For Program/Script''': If checked, wait for the program or script to return before continuing (synchronous execution)
*'''On Timeout Kill Program/Script''': If checked, and the "Wait for Program/Script" option is checked, and the "Wait / Timeout" time period has elapsed, terminate the external program or script
*'''Return OK to DragScript Engine only if Script return this''': If checked, the script or program must return the value specified in the text field in order for this action to be considered a success and return OK
*'''Save External Script output to this DragScript String''': If checked, store the value that the external script or program returns in STDOUT to the DragScript string variable chosen from the drop-down list
*'''Save External Script output to this DragScript Decimal''': If checked, store the value that the external script or program returns in STDOUT to the DragScript decimal number variable chosen from the drop-down list
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 
{{Note|Voyager will only terminate the specified program or script when the timeout period expires. If the called program calls other programs, they will not be terminated by Voyager}}{{Note|Use of Jolly String and DragScript Variables in arguments line is reserved to who have purchased and activated the Voyager Developer Plugin}}
{{Note|If the value returned from STDOUT is stored in a DragScript decimal number, be sure that the number returned uses a period as the decimal point separator}}

'''Example of Use'''

In this example, we call a Python script located in the directory d:\VScheduler\Scheduler.py, and wait up to 10 seconds for the script to complete.

The Python script writes a value to STDOUT with this code:<blockquote>import sys</blockquote><blockquote>sys.stdout.write('RUN')</blockquote><blockquote>sys.stdout.flush()</blockquote>We store that value in the SchedulerResult DragScript string variable. We can then make decisions in the DragScript using the DO IF STRING VALUE statement.

[[File:Script-scheduler-example.jpg]]

 
==Timing==
Timing actions inform DragScript to wait before performing an action. You can wait for a time interval, an absolute time to be reached, astronomical night with an offset, or for an object to reach a desired altitude:
 [[File:Dragscript-timing-211a.jpg]]

*'''Wait Time''': Wait for a specified time to arrive or to elapse

[[File:Dragscript-waittime.png]]

*'''Interval/Time''': Enter a time in HH MM SS.
*'''Wait Type''': Chose Absolute or Relative
**'''Absolute''': Wait until this absolute time is reached. If the time specified is more than 12 hours in the future, Voyager will assume this time has passed and will not wait. For example, if the specified time is 20:00:00 and this action is executed at 20:15:00, Voyager will not wait because that would cause a wait until tomorrow night, which is probably not what you intended
**'''Relative''': Wait for this amount of time to elapse
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 

 

*'''Wait Altitude''': Wait until the object at the given RA and DEC coordinates reaches the specified altitude, either rising or setting:

[[File:Dragscript-wait-altitude.png]]

*'''RA Target J2000''': RA coordinates of the object you want to reach the Reference Altitude in HH MM SS or HH MM SS.sss
*'''DEC Target J2000''': DEC coordinates of the object you want to reach the Reference Altitude in DD MM SS or DD MM SS.sss
*'''Reference Altitude''': Altitude to reach in degrees
*'''Exit Wait if Actual Altitude GREATER than or EQUAL (>=) to reference''': Wait until the target rises above the reference altitude
*'''Exit Wait if Actual Altitude LOWER than or EQUAL (>=) to reference''': Wait until the target sets below the reference altitude
*'''Wait Altitude until absolute time''': The Wait Altitude operation will terminate when this time is reached, whether or not the target has reached the reference altitude. This is usually done to end the wait with morning light
*'''Activate Antiglitch Altitude Reading System:''' set the flag if you want to activate an AntiGlitch system to avoid glitchy readings of values from mount drivers that have undeclared bugs (3 continuous readings are done to get the OK). Sometime happens in buggy drivers a single reading is damaged and trigger the OK to wait altitude status. I fyou have this problem activate the flag but report the problem to the mount driver developer.
* '''RoboClip:''' load RA and DEC from RoboClip catalog
* '''Coords From Sequence:''' load RA and DEC from a sequence file
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''Wait Altitude Dynamic Target''': Wait until the object at the calculated RA and DEC coordinates of a Dynamic Target reaches the specified altitude, either rising or setting:

[[File:Immagineddd.png]]

*'''Comet :''' open the Comet Finder in RoboOrbits, see more [https://wiki.starkeeper.it/index.php/RoboOrbits_Finders here]
*'''Asteroid :''' open the Asteroid Finder in RoboOrbits, see more [https://wiki.starkeeper.it/index.php/RoboOrbits_Finders here]
*'''Object Name :''' Read-only name of the Dynamic Target, coming from the search
*'''Object Key :''' Read-only key (code/number) of the Dynamic Target, coming from the search
*'''Object Dynamic Type :''' Read-only type of the Dynamic Target, coming from the search
*'''Reference Altitude''': Altitude to reach in degrees
*'''Exit Wait if Actual Altitude GREATER than or EQUAL (>=) to reference''': Wait until the target rises above the reference altitude
*'''Exit Wait if Actual Altitude LOWER than or EQUAL (>=) to reference''': Wait until the target sets below the reference altitude
*'''Wait Altitude until absolute time''': The Wait Altitude operation will terminate when this time is reached, whether or not the target has reached the reference altitude. This is usually done to end the wait with morning light
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*

*'''Wait Astronomical/Nautical/Civil Night''': Wait until astronomical/nautical/civil night, with an optional offset:

[[File:Dragscript-wait-night.png]]

*'''Get Latitude and Longitude from Mount''': Retrieve the current latitude and longitude from the connected mount, which must support this command. This location is used, along with the current date, to determine the time that night begins
*'''Use the Latitude and Longitude indicated below''': Specify your current latitude and longitude in the fields below. This location is used, along with the current date, to determine the time that night begins
*'''Offset''': Time in HH MM SS
**'''Offset Before''': If selected, exit the wait this amount of time before night
**'''Offset After''': If selected, exit the wait this amount of time after night
*'''Exit with ERROR if Wait Time is Greater than:''' if this option is flag the DragScript will exit with Error if the time wait for the begin of the next astronomical night is greater than the value in hour expressed in the numeric edit. Useful if you want to detect that the actual night is already finished and the dragscript can exit otherwise without this flag the next astrnomical night will be waited
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window
*
*
*'''Wait Dusk''' [[File:Dragscript-wait-dusk.jpg]]

*'''Get Latitude and Longitude from Mount''': Retrieve the current latitude and longitude from the connected mount, which must support this command. This location is used, along with the current date, to determine the time that dusk begins
*'''Use the Latitude and Longitude indicated below''': Specify your current latitude and longitude in the fields below. This location is used, along with the current date, to determine the time that dusk begins
*'''Offset''': Time in HH MM SS
**'''Offset Before''': If selected, exit the wait this amount of time before dusk
**'''Offset After''': If selected, exit the wait this amount of time after dusk
*'''Save Time to Event (minutes) in Decimal''': Save the computed time until Dusk in a decimal variable. See the DragScript example below for one way to use this.
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

You can configure the time at which dusk begins in the [[Flat Device Setup#Sky Flat|SkyFlat section of Flat Device]] Setup. {{Note|If dusk (plus or minus the offset if one is specified) has already passed, Wait Dusk returns OK if it has been less than 12 hours since dusk, else it returns ERROR if has been more than 12 hours}}

*'''Wait Dawn'''

[[File:Wait-dawn-2.jpg]]

*'''Get Latitude and Longitude from Mount''': Retrieve the current latitude and longitude from the connected mount, which must support this command. This location is used, along with the current date, to determine the time that dawn begins
*'''Use the Latitude and Longitude indicated below''': Specify your current latitude and longitude in the fields below. This location is used, along with the current date, to determine the time that dawn begins
*'''Offset''': Time in HH MM SS
**'''Offset Before''': If selected, exit the wait this amount of time before dawn
**'''Offset After''': If selected, exit the wait this amount of time after dawn
*'''Save Time to Event (minutes) in Decimal''': Save the computed time until dawn in a decimal variable. See the DragScript example below for one way to use this.
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

You can configure the time at which dawn begins in the [[Flat Device Setup#Sky Flat|SkyFlat section of Flat Device]] Setup.
 {{Note|If dawn (plus or minus the offset if one is specified) has already passed, Wait Dawn returns OK if it has been less than 12 hours, else ERROR if more than 12 hours}}

*

*'''Wait Safe''': Wait Safe Condition wait the safe condition before allow dragscript to execute net instruction. During the wait the events like Emergency Exit and Emergency suspend will be disabled and not managed. Just to remember you emergency events can coming from Viking I/O, Safe Monitor control, Weather Condition control. Like said this action will forcing event disable until exit for timeout or for safe. So be sure to have the observatory on the right configuration to avoid weather damage (closed and all parked). This action allow Voyager to run forever DragScript in case of no emergency exit. Can wait a time or an interval or the presence of astronomical/nautical/civil night, with an optional offset. Usually this is the first action in a script, its a good thing to put the Start node in Event disabled mode when you are manage the events in your DragScript. Also remember that the event at exit of this action will be restored to the original status, if they are disabled they will be leave disable or viceversa. We suggest also generally in dragscript to disable events during an atomic tasks like the opening observatory and connect setup to avoid interruption not really needed with impredictable results. If the action finish for wait will produce a status of TIMEOUT to the DragScript, if the action finish for one of the exit options will produce a status of ERROR to the DragScript, if the action found a SAFE status inside the wait option will produce a status of OK to the DragScript. You can decide if repeat the the action in a never ending loop (if you use night this mean to wait for the next night if you not check the exit ERROR options) or simple end the DragScript if you start DragScript night by Night. Rember that an Emergency Exit in any case will exit the DragScript.

{{Note|Wait SAFE Cannot be used inside the Event Manager (Exit, Suspend, Resume)}}

[[File:DSWaitSafe.png]]

*'''Wait SAFE until finish Night''': this option wait SAFE status until on eof specified kind of Nights is finished
**'''Get Latitude and Longitude from Mount''': Retrieve the current latitude and longitude from the connected mount, which must support this command. This location is used, along with the current date, to determine the time that astronomical night begins and end
**'''Use the Latitude and Longitude indicated below''': Specify your current latitude and longitude in the fields below. This location is used, along with the current date, to determine the time that astronomical night begins and end
**'''Night TYPE:''' the night to wait between Astronomical (Astrophotographers dark night -18° sun) , Nautical (-12° sun), Civil (-6° sun)
**'''Offset''': Time in HH MM SS
***'''Offset Before''': If selected, exit the wait this amount of time before astronomical night
***'''Offset After''': If selected, exit the wait this amount of time after astronomical night
*'''Wait SAFE until absolute time''': this option wait SAFE status until the absolute time you put inside the hh mm ss field
*'''Wait SAFE for a time interval of:''' this option wait SAFE status until the amount of time in the interval will be elapsed
*'''EXIT Options:''' with this options you can decide to exit with ERROR it the conditions inside is true
**'''Exit with ERROR if the Astronomical Night has ended less than:''' if this option is flag the DragScript will exit with Error if the astronomical night is ended by the time in hh field. This work and be active only if you use Wais SAFE with astronomical night. This flag enabled prevento to wait for the next night if the night is finished and you want to shutdown all without wait the next night.
**'''Exit with ERROR if Wait Time is greater than:''' if this option is flag the DragScript will exit with EORR if the time to wait is greater than the value in the hh field. This option is active only if you choose the Wait SAFE until absolute time. Useful if you dont wait over a certain time span.
*'''EVENT CHECK options:''' with this option you can decide to remove from processing status of SAFE some kind of events that will be ignored (event in any case are disable during the wait safe action)
**'''Check Emergency Exit Status in SAFE status calculation:''' if unchecked the condition that throw an Emergency Status will be ignored in calculation of SAFE Staus . ATTENTION !! this is a way really dangerous for your setup .. use only if you want to wait safe in particular condition , particular timing and for particular tasks
**'''Check Emergency SUSPEND Status in SAFE status calculation:''' if unchecked the condition that throw an Emergency Status will be ignored in calculation of SAFE Staus . ATTENTION !! this could be a way really dangerous for your setup .. use only if you want to wait safe in particular condition , particular timing and for particular tasks.
*'''LIGHT CONDITIONS options:''' with this option you can decide to remove from processing status of SAFE the LIGHT Conditions status
**'''Remove Weather LIGHT Conditions Status From Calculation of All Emergency Status:''' if unchecked the LIGHT conditions from Weather system will be not used to calculate the SAFE Status. Usefull if you want to open the dome with the light approaching the night time and do skyflat. For the Dawn flat you can decide to disable the LIGHT event using dedicated block
*'''MOON PHASE Options''' (Only for ADVANCED and FULL License Voyager versions): useful to ignore Safe status if the Moon Phase is over certains value
**'''Unsafe if Moon Phase equal or greater than:''' if checked Voyager will check the Moon Phase and if the value is equal or greater than the one indicated will return Unsafe to Emergency Events system
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

==Using the Time to Event Value in a DragScript==
Here's an example of using the '''Save Time to Event (minutes)''' value in a DragScript.

The basic idea is that you can decide whether or not to execute any actions based on how many minutes there are until or after dawn or dusk.

[[File:Dragscript-wait-dawn-2.jpg]]

The decimal variable "'''Minutes Before Event'''" is initialized to 0.

The '''Wait Dawn: Data from connected Setup - Offset (Before) 00:15:00 [hh:mm:ss]>>Minutes Before Event''' action waits until 15 minutes before dawn, and then puts the value 15 into the variable '''Minutes Before Event'''

The '''DO IF DECIMAL VALUE''' block will execute if the '''Minutes Before Event''' variable is between 0 and 15. If not, control passes to the End block.

The '''Goto Block: DAWN FLAT''' statement sends control back to that block, and the minutes before or after dawn are computed again and stored in the '''Minutes Before Event''' variable.

If it is after dawn when the '''Wait Dawn''' action runs, the value stored in '''Minutes Before Event''' will be negative, and the '''DO IF DECIMAL VALUE''' statement will not run.

 

==Signals==
Signals actions let you send notifications via email, Skype or SMS:

[[File:Dragscript-signals.png]]

{{Note|As of Voyager 2.1.4a, you can use the Save without Personal Info button to save a copy of your DragScript with all personal info (email addresses, email account logins, phone numbers, etc.) deleted. Use this save mode before posting a script online or sharing with others.}}

[[File:Dragscript-editor-toolbar-3.png]]

Use button 5 to save your DragScript with the personal info deleted for any of the actions in this group (Signals).

 

*Send Email using Voyager Account: Send an email using Voyager's email account. You must have an active [[Licensing|support and update Voyager license]] to use this option and an Internet connection

[[File:Dragscript-send-email.png]]

*'''Mail to''': Email address to send to
*'''Object''': Subject line of email TYPO: Should be Subject instead of Object
*'''Text''': Body of email
*'''Cancel''': Discard changes and close the window
*'''OK''': Save changes and close the window
*'''JOLLY Strings''':there are some special strings called jolly that can be used in mail text and will be replaced with some data from Voyager environment or DragScript variables
**'''Internal IPs:''' ##INTERNAL-IP## write a list of all internal IPs avalaible in the system
**'''External IP''': ##EXTERNAL-IP## write a list of external IP assigned to your PC(router) if you have internet connection up
**'''NOW''': ##NOW## write the actual date and time
**'''Mount Altitude''': ##MOUNT-ALT## write the actual altitude of Telescope Mount if connected
**'''Mount Azimuth''': ##MOUNT-AZ## write the actual azimuth of Telescope Mount if connected
**'''Variable''': ##VAR-name## where you must replace the ''name'' with the real name of your variable (case sensitive) , write the actual value of you variable (decimal, string or counter)

 

*'''Send Email''': Send an email notification using a specified email server and account. Requires an Internet connection

[[File:Dragscript-sendemail.png]]

*'''Mail From''': Email address this message is from
*'''Mail to''': Email address to send to
*'''Object''': Subject line of email TYPO: Should be Subject instead of Object
*'''Text''': Body of email
*'''SMTP User''': Username to login to SMTP (mail) server. Check with your local ISP or network administrator if you don't know how to login to your SMTP server to send email
*'''SMTP Password''': Password to login to your SMTP (mail) server
*'''SMTP Server''': Hostname or IP address of your SMTP (mail) server
*'''SMTP Port''': Port number of your SMTP (mail) server
*'''Use SSL''': If checked, use an SSL (secure) connection to your mail server
*'''GMAIL''': Click this button to use the SMTP server and port information for Google Gmail
*'''HOTMAIL''': Click this button to use the SMTP server and port information for Microsoft Hotmail
*'''Cancel''': Discard changes and close the window
*'''OK''': Save changes and close the window

*'''JOLLY Strings''':there are some special strings called jolly that can be used in mail text and will be replaced with some data from Voyager environment or DragScript variables
**'''Internal IPs:''' ##INTERNAL-IP## write a list of all internal IPs avalaible in the system
**'''External IP''': ##EXTERNAL-IP## write a list of external IP assigned to your PC(router) if you have internet connection up
**'''NOW''': ##NOW## write the actual date and time
**'''Mount Altitude''': ##MOUNT-ALT## write the actual altitude of Telescope Mount if connected
**'''Mount Azimuth''': ##MOUNT-AZ## write the actual azimuth of Telescope Mount if connected
**'''Variable''': ##VAR-name## where you must replace the ''name'' with the real name of your variable (case sensitive) , write the actual value of you variable (decimal, string or counter)

 

*'''Start Skype Call''': Start a Skype call from the computer running Voyager. Requires an Internet connection

[[File:Dragscript-skype.png]]

*'''Phone Number to Call''': Phone number or Skype name to call using Skype
*'''After Command Wait''': Time in seconds to wait after sending the command before timing out if no response from Skype
*'''After leave ringing for''': Time in seconds to wait after Skype places the call and the remote phone starts to ring
*'''Skype Exe Directory''': Location of Skype program on this computer
*'''Find Skype''': Look for Skype program on this computer and fill out the Skype Exe Directory if found
*'''Test''': Try to make a Skype call using the information in this dialog window
*'''Cancel''': Discard changes and close the window
*'''OK''': Save changes and close the window

 

*'''Send SMS with Nexmo'''
**Send an SMS (text message) using the Nexmo service: https://www.nexmo.com/ Requires an Internet connection.

[[File:Dragscript-nexmo.png]]

*'''Source Number or Name''': Phone number of sender, or name of sender. For country like USA this is a constraint to use (phone number) to avoid error in transmission (from Voyager version 2.2.1d)
*'''To Telephone Number''': Phone number to send SMS message to
*'''Text''': Body of SMS messages
*'''API Key''': API Key for Nexmo service - you must sign up at https://www.nexmo.com/ to get an API key and secret
*'''API Secret''': API Secret for Nexmo service
*'''Cancel''': Discard changes and close the window
*'''OK''': Save changes and close the window

*'''JOLLY Strings''':there are some special strings called jolly that can be used in mail text and will be replaced with some data from Voyager environment or DragScript variables
**'''Internal IPs:''' ##INTERNAL-IP## write a list of all internal IPs avalaible in the system
**'''External IP''': ##EXTERNAL-IP## write a list of external IP assigned to your PC(router) if you have internet connection up
**'''NOW''': ##NOW## write the actual date and time
**'''Mount Altitude''': ##MOUNT-ALT## write the actual altitude of Telescope Mount if connected
**'''Mount Azimuth''': ##MOUNT-AZ## write the actual azimuth of Telescope Mount if connected
**'''Variable''': ##VAR-name## where you must replace the ''name'' with the real name of your variable (case sensitive) , write the actual value of you variable (decimal, string or counter)

 
{{Note|Nexmo is an online service that offers voice and data communication. To use Nexmo from Voyager you must register at their site at https://www.nexmo.com}}

 

* '''Send Telegram'''
** Send an message using Telegram service chatbot: https://www.telgram.org/ Requires an Internet connection.
** [[File:SaveTelegramBlock.png]]

* '''Text''': message
* '''API ID''': API ID (token create during the chatbot) of your Telegram user
* '''Chat ID''': ID number assigned to chatbot created, you can get opening the link [https://api.telegram.org/bot<your https://api.telegram.org/bot<YOUR_TOKEN>/getUpdates]
* '''Cancel''': Discard changes and close the window
* '''OK''': Save changes and close the window

* '''JOLLY Strings''':there are some special strings called jolly that can be used in mail text and will be replaced with some data from Voyager environment or DragScript variables
**'''Internal IPs:''' ##INTERNAL-IP## write a list of all internal IPs avalaible in the system
** '''External IP''': ##EXTERNAL-IP## write a list of external IP assigned to your PC(router) if you have internet connection up
** '''NOW''': ##NOW## write the actual date and time
** '''Mount Altitude''': ##MOUNT-ALT## write the actual altitude of Telescope Mount if connected
**'''Mount Azimuth''': ##MOUNT-AZ## write the actual azimuth of Telescope Mount if connected
**'''Variable''': ##VAR-name## where you must replace the ''name'' with the real name of your variable (case sensitive) , write the actual value of you variable (decimal, string or counter)
'''Guide to obtain API ID and Chat ID''' :

# Download the Telegram APP on your mobile phone and register
# Open a chat with @BotFather and type /newbot to create a new private bot
# You will be asked for a friendly name - choose whatever you like, e.g. VoyagerMessages
# You will be given an "API Token" - save this somewhere - it is what you will enter as the API ID in your DragScript action, as shown above
# In your browser (can be on a desktop, doesn't have to be on your phone) open the link <nowiki>https://api.telegram.org/botYOUR-TOKEN/getUpdates</nowiki> replacing YOUR-TOKEN with the API Token
# You will get a short message that starts with {"ok":true. It won't have the Chat ID yet - this is OK
# Go back to Telegram and find the last message from @BotFather that starts with "Congratulations on your new bot. You will find it at ..." Click on that link and a new message room will open in Telegram, talking to your bot
# Type at least one message - a simple "hello" will do
# Go back to the browser page you opened in step 5 and hit reload - now you should see more characters including a long number after "from":{"id": That number is the Chat ID, which you use in your DragScript Send Telegram action as shown above
# If you don't see the Chat ID, try sending a couple more messages to your bot in Telegram and then quickly reload your browser until you get the ID
# That's it - you can now use the API ID and Chat ID to send Telegram messages from your DragScript

==User Manual Input==
User manual input actions allow interactions between Voyager and the user:

[[File:DragScriptUserInter.png]]

 

*'''Wait User OK''': Ask to the user with a windows prompt to press a button on the screen to continue or to abort and also its possible to activate a timeout during waiting of the user interaction
*[[File:DragScriptWaitUser.png]]
*'''Wait Mode''': how the wait will be work
*'''Use Timeout of:''' with this option the wait will finish in anycase after the seconds selected
*'''In case of timeout exit with:''' if the Use timeout of option will be used then exit can be selected between TIMEOUT or OK action result, this result will be usable in the DragScript using the IF condition related to actions
*'''No Timeout:''' with this option the wait will be for ever until physically user press the button on the screen
*'''Message:''' show a text message inside window prompt to the user
*'''Show Variable Value:''' show a text rappresentation of the variable selected inside window prompt to the user
*'''Wait User DATA''': Ask to the user with a windows prompt to input data (DECIMAL,STRING, COUNTER depends on type of variable used for storage) to continue or to abort and also its possible to activate a timeout during waiting of the user interaction. The inpout data will be stored in the selected variable.
*[[File:Immaginewefwef.png]]
*'''Wait Mode''': how the wait will be work
*'''Use Timeout of:''' with this option the wait will finish in anycase after the seconds selected
*'''In case of timeout exit with:''' if the Use timeout of option will be used then exit can be selected between TIMEOUT or OK action result, this result will be usable in the DragScript using the IF condition related to actions
*'''No Timeout:''' with this option the wait will be for ever until physically user press the button on the screen
*'''Message:''' show a text message inside window prompt to the user
*'''Show Variable Value:''' show a text rappresentation of the variable selected inside window prompt to the user
*'''Insert Data in Variable:''' the data in input from the user will be stored in the selected DragScript variable (variable must be declared before use it in DragScript). Based on type of DragScript Variable the edit mask of input field will be adapted. 
{{Note|if you using No Timeout option you must be really to be present in front of your PC to continue}}

==Optec Perseus==
Optec Perseus actions allow to interact with the hardware [https://optecinc.com/astronomy/catalog/perseus/default.htm Port Instrument Selector from Optec] :

[[File:OptecPer1.png]]

 

*'''Optec Perseus Read Device Info''': ask information about device and save it in environment variables of DragScript
*'''Optec Perseus Read Device Status''': ask status of device and save it in environment variables of DragScript
*'''Optec Perseus Homing''': command to device to Homing
*'''Optec Perseus Set Port:''' rotate device to select the port selected index
**[[File:OptecPer2.png]]
**'''Port:''' port index to select

 
{{Note|ASCOM Switch driver of Optec Perseus must be installed in order to allow working the DragScript Blocks}}

== Donuts ==
Donuts actions allow to interact with the software Donuts developed by Kames MacCormac, used for advanced research pointing, code here https://github.com/jmccormac01/Donuts :

[[File:DonutsSection.png]]

*'''Donuts Calibration''': ask to Donuts process to performe a Calibration using camera and mount

[[Category:DragScript]]
[[Category:All]]
[[Category:Manual|Lb]]

File:Dragscript-sequence-211g.jpg

2024-06-29T14:01:21Z

Leonardo: Leonardo uploaded a new version of File:Dragscript-sequence-211g.jpg

== Summary ==
importing from old wiki

DragScript Elements

2024-06-29T14:00:03Z

Leonardo: /* Mount */

__TOC__

The DragScript "language" is composed of blocks that are dragged from the list on the right side of the DragScript editor to the script being created or edited on the left.

Each category of element is organized in list that can be expanded or contracted by clicking the "+" or "-" next to the element category name:

[[File:Dragscript-editor-elements.png]]

E.g., if you click the + in front of Actions, the list expands like this:

[[File:List-expanded.png]]

As you can see in the case of Actions, there are further subcategories of actions, and clicking the + in front of one of them expands it again:

[[File:Subcategory-expanded.png]]

Here, the list of Setup actions is fully expanded and we see three choices that we can drag to the active script: Connect Setup, Connect Setup with Timeout, and Disconnect Setup

For the remainder of this page, we will describe the available DragScript elements. New elements are added periodically and will be documented in the release notes and here.

Press Sort button to listing all the categories and blocks in alphabetical order.

==DragScript Actions==

===Operating System===
The Operating System actions control the PC running Voyager:

[[File:DSopOs.png]]

*'''Shutdown PC''': Shutdown the PC running Voyager
*'''Restart PC''': Restart (reboot) the PC running Voyager
*'''Hybernate PC:''' Hybernate the PC running Voyager (only in OS that support it)
*'''Suspend PC:''' Susend the PC running Voyager (only in OS that support it)
*'''Kill Process''': Kill a process on the PC running Voyager. Either type in the Process name or click one of the buttons to use a preconfigured process name.

[[File:Kill-process.png]]

*'''Serial Port STRING Transmit''': Send a text string with a terminator (if necessary) to an RS232 Serial Port

[[File:SerPortTx.png]]

*'''Configuration'''
**'''Serial Port Config''': insert the string used to configure and open the serial port (portname,portspeed,databit,parity,datastopbit) for parity use N=None O=Odd E=Even (Example COM1,9600,8,N,1)
**'''Text to Send''': input the text to send to the serial port
**'''Use Terminator''': indicate if you want to use a terminator or not. CR = carriage return, LF=Line feed
*'''Serial Port BINARY Transmit''': Send Binary data string to an RS232 Serial Port

[[File:SerPortBin.png]]

*'''Configuration'''
**'''Serial Port Config''': insert the string used to configure and open the serial port (portname,portspeed,databit,parity,datastopbit) for parity use N=None O=Odd E=Even (Example COM1,9600,8,N,1)
**'''Binary Data To Send(*):''' input the binary data to send to the serial port. Binary Data must be entered ad a string in hexadecimal format separated (Example 0A 0B 0C A1 A2 A3)
*'''UDP IP/Port STRING Transmit''': Send a text string with a terminator (if necessary) to an UDP Port
[[File:Txudpstring.png]]

* '''Configuration'''
**'''IP/Hostname''': IP or hostname of PC where to send data
**'''Port:''' UDP port number to use for transmission
**'''Text to Send''': input the text to send to the UDP Port
**'''Use Terminator''': indicate if you want to use a terminator or not. CR = carriage return, LF=Line feed
*'''UDP IP/Port BINARY Transmit''': Send Binary data string to an RS232 Serial Port
*[[File:UDPIPBinaryTX.png]]
* '''Configuration'''
** '''IP/Hostname''': IP or hostname of PC where to send data
**'''Port:''' UDP port number to use for transmission
** '''Binary Data To Send(*):''' input the binary data to send to the serial port. Binary Data must be entered ad a string in hexadecimal format separated (Example 0A 0B 0C A1 A2 A3)

==Setup==
Setup actions control connecting and disconnecting to your equipment and software:

[[File:Dragscript-setup-2.14c.png]]

*'''Connect Setup''': Commands Voyager to connect to the equipment and software in the currently selected [[Setup#Profile Management|Profile]]
*'''Connect Setup with Timeout''': Command Voyager to connect to the equipment in the currently selected [[Setup#Profile Management|Profile]]. Voyager will timeout if connection does not complete within the specified number of seconds:

[[File:Setup-timeout.png]]

*'''Disconnect Setup''': Command Voyager to disconnect from the equipment and software in the currently selected [[Setup#Profile Management|Profile]]
*'''Force Disconnect Setup''': Command Voyager to forcefully disconnect the Seup without checking if the previous connection was actually successful (all setup checks connected regularly)
*'''Connect Safety Monitor Control''': Connect only the Safety Monitor control. This is useful for monitoring conditions prior to connecting all your equipment
*'''Disconnect Safety Monitor Control''': Disconnect only the Safety Monitor control
*'''Connect Flat Device #1 / #2 Control''': Connect only the Flat Device #1/#2. This is useful for switch on the flat device only when needed
*'''Disconnect Flat Device #1 / #2 Control''': Disconnect only the Flat Device #1/#2 control

 

==Voyager==
Interaction with Voyager Application:

[[File:Immagine 2021-04-05 193048.png]]

* '''Change Voyager Profile''': will allow changing of profile from DragScript. Voyager must have the setup not connect or action will failed.
** [[File:Immaginefefefr.png]]
*** '''Profile:''' Profile select, and list of all profile if retrieved from Voyager
*** '''Get Voyager Profiles List:''' listg of profiles will be retrieved directly from Voyager using the Application Server. Male sure that the Application Server in Voyager is active
*** '''OK''': Click to save your changes and close the window
***'''Cancel''': Click to discard your changes and close the window
* '''Empty Voyager Temporary Folders''': will remove all file from the temporary folders of Voyager (for example the FIT folder where is the temporary Shot for platesolving or pointing)

==Session==
Session actions run sequences to acquire images, flat frames, and shutdown ("Good Night") your system:

[[File:Session-script.png]]

*'''RoboTarget''': Robotic Scheduler Available only in [https://software.starkeeper.it/voyager-advanced/ Voyager Advanced version]
*'''Sequence''': Run a [[Sequence Configuration|Sequence]] with options:

[[File:Dragscript-sequence-211g.jpg]] 

*'''Configuration Panel''':
**Click the folder icon [[File:Folder-icon.png]] to select the Sequence file to run. [[Sequence Configuration|Create your Sequence files]] in Voyager's OnTheFly workspace
**'''Start/TimeSpan''': Click one of the radio buttons to use that option to tell when to start and end the sequence. This is one way to have Voyager image this target until a specific time is reached, or an interval has elapsed. It is a good idea to specify an ending time here, or a minimum altitude in the Sequence definition or the Options field below, so Voyager will not continue trying to take images after the object has set
***'''Start and End from Sequence:''' Use the start and end times specified in the sequence definition file. The start time comes from the [[Sequence Configuration#On Start Tab|On Start tab]] and the end time comes from the [[Sequence Configuration#On End Tab|On End tab]]
***'''Immediately Start and Finish After Interval''': Start the sequence immediately and end it after the HH:MM:SS amount of time specified with the Time Span: counter fields
***'''Start and End at Absolute Time''': Voyager should wait until the specified Start: time and end the sequence at the specified End: time.
***'''Immediately Start and End at Absolute Time''': Start the sequence immediately and end it at the time specified in the counter fields
***'''Immediately Start and Finish With Astronomical Night''': Start the sequence immediately and finish it at Astronomical Night's end, offset +/- by the number of minutes set in the Offset: counter field
*'''Calculated Time Span''': Voyager will show how much time this sequence will take with the chosen Start/TimeSpan option if you choose Start and End at Absolute time. It is not possible to calculate this if you choose one of the "Immediately Start" options
**
**

 {{Note|Enter time in 24 hour format using local time - or the time zone on the computer running Voyager. That's the time that will be used in doing these calculations. Midnight is 00:00:00. 10 pm local time is 22:00:00. 3 AM is 03:00:00.}} {{Note|Note: If the Start: time is more than 12 hours in the future, Voyager will start the sequence, assuming that the start time has passed already in the current night. For example, if you specify a start time of 20:00:00 and it is now 20:15:00, Voyager will start the sequence}} {{Note|If the End time is more than 12 hours in the future, Voyager will assume the End time has already passed for the night and end the sequence. For example, if a sequence has a Start time of 20:00:00 and an End time of 21:00:00 and the current time is 22:00:00, Voyager will end the sequence}} {{Note|Times entered here will override any start or end times defined in the Sequence file. The times you define when you create the sequence are used for OnTheFly running of the Sequence, not for DragScript execution}} {{Note|The Start and End times are checked at the beginning of running a sequence and the sequence exits with status OK if the current time is outside the Start and End time window}}

**'''Options''': Check the boxes to select any of these options (Remember to scrool the panel to find more options in the configuration form):
***'''Overrides Target Coords J2000''': If checked, the RA and DEC coordinates are used instead of those in the sequence file. RA coordinates are in HH MM SS and DEC coordinates are HH MM SS.sss
***'''Overrides Target Name with this''': If checked, the name entered in the field will be used as the target name, which is part of the file name
***'''Force Dynamic Target Comet :''' if checked force the Sequence to use a Comet Dynamic Target type, you MUST select the Comet using the Comet Finder button near the check. If you check the flag and do not select a Comet the Sequence will generate an Error at starting. Target Name and Target key will be populated after the search and the overrides target name will be used with the name of the Dynamic Target. You can for sure change it.
***'''Force Dynamic Target Asteroid :''' if checked force the Sequence to use an Asteroid Dynamic Target type, you MUST select the Asteroid using the Asteroid Finder button near the check. If you check the flag and do not select an Asteroid the Sequence will generate an Error at starting. Target Name and Target key will be populated after the search and the overrides target name will be used with the name of the Dynamic Target. You can for sure change it.
***'''Override Dynamic Target Pointing Type :''' if checked and only if you are using a Dynamic Target (comet or asteroid) Voyager allow you to select when calculating the RA/DEC coordinates od the Dynamic Target. Default for a Dynamic Target is the Calculate RA/DEC only at Sequence Begin
****'''Calculate RA/DEC Only at Sequence Begin :''' Voyager will calculate the RA/DEC of the Dynamic Target only whe the Sequence action will start and will use this RA/DEC for all duration of the Sequence action. If the Sequence will be restarted anothe day or some hours after or generally will be restarted VOyager will calculate again the RA/DEC coordinates. But not in the same Sequence run.
****'''Calculate RA/DEC at Each Precise Goto :''' Voyager will calculate the RA/DEC of the Dynamic Target at each precise pointing goto inside the Sequence Run included at the begin of Sequence
****'''Calculate RA/DEC Every X Seconds :''' Voyager will calculate the RA/DEC of the Dynamic Target at the beginning of the Sequence and each X seconds like edited in the dedicated field. if the X interval is expired and Voyager is in exposure camera mode, will wait the end of exposure to calculate the new coordinates. A realign goto will not be requested if the next flag is not checked.
*****'''And Realign Target :''' if checked Voyager will force a realign with a Precise pointing to the new RA/DEC of the Dynamic Target
*****'''Without Using Plate Solving :''' if checked Voyager will avoid the precise pointing with plate solving for the realign and will use a simple goto without solving
***'''Override Angle Rotation of Target with PA of°:''' if checked , if in the sequence the rotator is managed, this flag force the Rotation Angle to the value selected. The other rotator settings in sequence will not be changed.
***'''Finish Running Exposure in case of elapsed time for Sequence Execution''': If checked, an exposure in progress will be allowed to finish if it starts before the sequence end time but finishes after the sequence end time
***'''Override Lower Altitude value under which Exit from Sequence''': If checked, if the sequence target sets below the altitude given here, the sequence will end. This value will override the minimum altitude value chosen in the sequence file
***'''Override Higher Altitude value above which Exit from Sequence''': If checked, if the sequence target rises above the altitude given here, the sequence will end. This value will override the maximum altitude value chosen in the sequence file
***'''Override Lower HourAngle value under which Exit from Sequence:''' If checked, if the sequence target HourAngle are lower the value given here, the sequence will end. This value will override the Lower HourAngle value chosen in the sequence file
***'''Override Higher HourAngle value over which Exit from Sequence:''' If checked, if the sequence target HourAngle are higher the value given here, the sequence will end. This value will override the Higher HourAngle value chosen in the sequence file
***'''Override Camera Cooling Temperature with Decimal Variable:''' if checked for colling temperature will be used the value inside the decimal variable selected in the drop-box combo box control
***'''Override Lower Azimuth value under which Exit from Sequence:''' If checked, if the sequence target Azimuth are lower the value given here, the sequence will end. This value will override the Lower Azimuth value chosen in the sequence file
***'''Override Higher Azimuth value over which Exit from Sequence:''' If checked, if the sequence target Azimuth are higher the value given here, the sequence will end. This value will override the Higher Azimuth value chosen in the sequence file
***'''Use External Interval Angle:''' if each the azimuth constraints will be cheched you can decide with this flag to use external angle instead of internal angle between before and after azimuth. Example if you choose 70° before and 150° after with out external flag this mean sequence run if angle is between 70 and 150°, if you chec it and invert to external sequence will be terminate if azimuth is between 70 and 150°
**'''Default''': Click this button to populate this window with the default options
**'''OK''': Click to save your changes and close the window
**'''Cancel''': Click to discard your changes and close the window 
**'''Override FILE PATTERN:''' flag this chheckbox to activate sub foldering and file naming with File Pattern method, insert in the big text field near the flag the string to override of the file pattern to use instead of the one configured in the File Pattern Manager. This will affect only the actual sequence and do not change the main File Patterm Manager configuration. This is for example mandatory in case of join of the OpenSkyGems network and sharing of the observatory setup.
*'''Research & Survey''': Run a [[Research Survey|Research & Survey]] sequence with options

[[File:Research-survey-dragscript.png]]

*'''Configuration Panel''':
**Click the folder icon [[File:Folder-icon.png]] to select the Research & Survey sequence file to run. Create your sequence files in Voyager's [[Research Survey|Research & Survey workspace]]
**TYPO: Star/TimeSpan should be Start/TimeSpan
**'''Start/TimeSpan''': Click one of the radio buttons to use that option to tell when to start and end the Research & Survey sequence. This is one way to have Voyager image this target until a specific time is reached, or an interval has elapsed. It is a good idea to specify an ending time here, or a minimum altitude in the Research & Survey sequence definition or the Options field below, so Voyager will not continue trying to take images after the object has set
***'''Immediately Start and Finish After Interval''': Start the sequence immediately and end it after the HH:MM:SS amount of time specified with the Time Span: counter fields
***'''Start and End at Absolute Time''': Voyager should wait until the specified Start: time and end the sequence at the specified End: time.
***'''Immediately Start and End at Absolute Time''': Start the sequence immediately and end it at the time specified in the counter fields
***'''Immediately Start and Finish With Astronomical Night''': Start the sequence immediately and finish it at Astronomical Night's end, offset +/- by the number of minutes set in the Offset: counter field
**'''Calculated Time Span''': Voyager will show how much time this sequence will take with the chosen Start/TimeSpan option if you choose Start and End at Absolute time. It is not possible to calculate this if you choose one of the "Immediately Start" options
*'''Options''':
**'''Finish Running Exposure in case of elapsed time for Sequence Execution''': If checked, an exposure in progress will be allowed to finish if it starts before the sequence end time but finishes after the sequence end time
**'''Default''': Click this button to populate this window with the default options
**'''OK''': Click to save your changes and close the window
**'''Cancel''': Click to discard your changes and close the window 

 {{Note|See the Important Notes above in the Sequence discussion to understand how Voyager treats the values in the time fields when they have already passed in tonight's session or if they are also specified in the Research & Survey sequence definition file}}

*'''Flat''': Run an Auto Flat sequence. [[Auto Flat|Configure the Auto Flat sequence files]] in the OnTheFly workspace

[[File:Flat-sequence-dragscript.png]]

*Click the folder icon [[File:Folder-icon.png]] and choose the Auto Flat sequence file to run. [[Auto Flat|Configure the Auto Flat sequence files]] in the OnTheFly workspace
*TYPO: Configuration dialog says "Good Night" but should be Auto Flat
*'''Default''': Click this button to populate this window with the default options (blanks out the Flat Sequence File field)
*'''OK''': Click to save your changes and close the window
*'''Cancel''': Click to discard your changes and close the window

 

*'''Good Night''': Run a series of one or more shutdown actions:

[[File:Dragscript-good-night.png]]

*'''CCD Filter Select''': Moves the filter wheel to the filter chosen from the drop-down box on the right
*'''Sync Warmup''': Send the CCD cooler a warmup command and wait until it finishes
*'''Async Warmup''': Send the CCD cooler a warmup command and continue execution without waiting for it to finish
*'''Parking''': Park the mount as specified in [[Mount Setup#Park.2FUnpark|Mount Setup]]

 

==Plate Solving==
Plate Solving actions perform a plate solving action as defined in the [[Plate Solve Setup|Plate Solving setup]] of the active profile:

[[File:Dragscript-plate-solving.png]]

 

*'''Plate Solving''' : Perform a plate solve action at the current scope location using the Plate Solve software defined in the [[Plate Solve Setup|Plate Solving setup]] of the active profile. ''Mount will not be synched''
*'''Plate Solving with Mount Sync:''' Perform a plate solve action at the current scope location using the Plate Solve software defined in the [[Plate Solve Setup|Plate Solving setup]] of the active profile. ''Send a Sync command to the mount unless you have chosen to not send a Sync command to your mount in [[Mount Setup#Management|Mount Setup]]. You may lost pointing model if you have one and your driver not allow additional and external sync''

==Blind Solving==
Blind Solving actions perform a plate solving action as defined in the [[Plate Solve Setup|Plate Solving setup]] of the active profile:

[[File:BlindSolveBlocks.png]]

 

*'''Blind Solving with Mount Sync:''' Perform a blind solve action at the current scope location using the Plate Solve software defined in the [[Plate Solve Setup|Plate Solving setup]] of the active profile. ''Send a Sync command to the mount unless you have chosen to not send a Sync command to your mount in [[Mount Setup#Management|Mount Setup]]. You may lost pointing model if you have one and your driver not allow additional and external sync''

 

==WEB Solving==
Plate Solving actions perform a plate solving action as defined in the [[Plate Solve Setup|Plate Solving setup]] of the active profile:

[[File:WebSolvingBlocks.png]]

 

*'''Web Solving with''' '''Sync''': Perform a web blind solve action at the current scope location using the nova.astrometry.net site. An active Internet connection is required. Send a Sync command to the mount unless you have chosen to not send a Sync command to your mount in [[Mount Setup#Management|Mount Setup]]
**[[File:Web-solving-with-sync.png]]
***'''Timeout''': Specify the number of minutes Voyager should wait after initiating the Web Solve before timing out. Use an IF TIMEOUT decision action to define what to do if the web solve times out

==Guiding==
Guiding actions send commands to the guide software:

[[File:Dragscript-guiding-dithering.png]]

*'''Calibrate Guide''': Command the guide software to perform a calibration action. It is recommended to include a Calibrate Guide action at the start of your sequence unless you are sure that your guider is calibrated from a previous session. Double click to bring up the configuration window:

[[File:Dragscript-calibrate-guide.png]]

*'''Time''': Exposure time for Calibration exposures by the guiding software
*'''Binning''': Binning level for Calibration exposures by the guiding software
*'''Use RoboGuide Star Selection''': If selected, use Voyager's RoboGuide process to choose a guide star for the Calibration action. This is mandatory at this time since some guiding software cannot select a guide star.
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Acquiring Guide Star''': Commands the guiding software to select a guide star. Double click to bring up the configuration window:

[[File:Dragscript-acquire-guide-star.png]]

*'''Time''': Exposure time for guide star acquisition exposures by the guiding software
*'''Binning''': Binning level for guide star acquisition exposures by the guiding software
*'''Use RoboGuide Star Selection''': If selected, use Voyager's RoboGuide process to choose a guide star. This is mandatory at this time since some guiding software cannot select a guide star.
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''Guide Start''': Commands the guiding software to begin guiding. Double click to bring up the configuration window:

[[File:Dragscript-guide-start.png]]

*'''Time''': Exposure time for guiding exposures by the guiding software
*'''Binning''': Binning level for guiding exposures by the guiding software
*'''Use RoboGuide Star Selection''': If selected, use Voyager's RoboGuide process to choose a guide star. This is mandatory at this time since some guiding software cannot select a guide star.
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Guide Stop''': Command the guiding software to stop guiding

 

*'''Guide Dithering''': Command the guiding software to perform a dithering action. Dithering is used to move the mount a tiny random amount in a random direction - usually only a couple of pixels. This prevents hot or cold pixels in your sensor from showing up in the same position in all of your images, making it easier to remove hot or cold pixels when stacking your images. Double click to bring up the configuration window:

[[File:Dragscript-guide-dithering.png]]

*'''Max Pixel''': Specify the maximum number of pixels that a dithering operation can move the mount
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 

*'''Unguided Dithering''': Perform a dithering action directly, vs. Guide Dithering which sends a dithering command to the guide software. Dithering is used to move the mount a tiny random amount in a random direction - usually only a couple of pixels. This prevents hot or cold pixels in your sensor from showing up in the same position in all of your images, making it easier to remove hot or cold pixels when stacking your images.

[[File:Unguided-dither-3.png]]

*'''Max Pixel''': Specify the maximum number of pixels that a dithering operation can move the mount
*'''From Actual Position''': This is the safest and default choice - it sends a command to move the mount up to the specified number of pixels from the current position. This should be a small movement, as the recommended number of pixels to dither is 3
*'''From Last Goto Action Position''': Send a command to move the mount a random number of pixels up to '''Max Pixel''' in a random direction relative to the position of the last Goto action. This should only be used following a successful Goto action in your DragScript. You can damage your mount if you use this without a successful Goto action preceding it.
*'''From Last Precision Pointing Action Position''': Send a command to move the mount a random number of pixels up to '''Max Pixel''' in a random direction relative to the position of the last Precision Pointing action. This should only be used following a successful Precision Pointing action in your DragScript. You can damage your mount if you use this without a successful Precision Pointing action preceding it.
*'''Use Actual Position on Empty/Fail condition''': If checked, if the position reported by the Last Goto Action or Last Precision Pointing Action is empty, or if the Last Goto Action or Last Precision Pointing Action ended with an error, use the Actual Position of the mount as the starting point for dithering. In other words, don't attempt to dither based on the Last Goto action position or the Last Precision Pointing action position if either of those positions is empty, as this would send a command to the mount that could cause a pier crash and/or damage to your equipment. '''Highly recommend leaving this checked.'''
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 
==Mount==
Mount actions send commands to the mount defined in the [[Mount Setup|Mount setup]] of the active profile:

[[File:Dragscript-mount.png]]

*'''Stop Tracking''': Command the mount to stop tracking
*'''Start Tracking''': Command the mount to start tracking
*'''Parking''': Command the mount to slew to the Park position
*'''Unparking''': Command the mount to Unpark
*'''Sync on Park''': Command the mount to save the current position as the Park position
*'''Homing''': Command the mount to move to the Home position (depends on the driver if the command will work, not all drivers have this command implemented !)
*'''Goto RA/DEC''': Command the mount to move to the specified RA and DEC coordinates (J2000)

[[File:Dragscript-gotoradec.png]]

*'''RA J2000''': Enter the RA coordinates in HH MM SS or HH MM SS.sss
*'''DEC J2000''': Enter the RA coordinates in DD MM SS or DD MM SS.sss
*'''Default''': Use the default settings: clears the RA and DEC fields
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Goto ALT/AZ''': Command the mount to move to the specified Altitude and Azimuth coordinates

[[File:Goto-altaz.png]]

*'''ALT:''' Enter the Altitude coordinates in DD MM SS or DD MM SS.sss
*'''AZ''': Enter the Azimuth coordinates in DD MM SS or DD MM SS.sss
*'''Force Use of Normal RA/DEC Slew With Conversion''': If checked, convert the requested ALT and AZ values to RA and DEC values and send a goto RA/DEC command to the mount
*'''Default''': Use the default settings: clears the AZ and ALT fields
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Goto Near Zenith''': Command the mount to move to a point close to the current Zenith (directly overhead). 
{{Note|Goto Near Zenith followed by a Blind Solving with Sync action is a good way to initialize your mount's pointing model at the start of a session. It is only a single point, but if your mount is accurately polar aligned, doing this before the first Precise Pointing operation may helps the Precise Pointing to succeed}}

*

*'''Goto By Name''': Command the mount to move to an object by name with an optional RA and DEC offset. This action requires Voyager to be connected to the [[Planetarium Setup|Planetarium software]] defined in the current profile. The Object Name must match a name that can be successfully searched in the connected Planetarium software.

[[File:Dragscript-gotoname.png]]

*'''Object Name''': Name of the object to goto. Must be a name that can be successfully searched in the connected Planetarium software
*'''Offset RA (optional)''': An optional +/- offset in HH MM SS or HH MM SS.sss to be added or subtracted from the RA coordinates returned by the Planetarium software
*'''Offset DEC (optional)''': An optional +/- offset in DD MM SS or DD MM SS.sss to be added or subtracted from the DEC coordinates returned by the Planetarium software
*'''Goto Dynamic Target''': Command the mount to move to a RA/DEC of a Dynamic Target calculating with RoboOrbits the coordinates at now [[File:Immaginedd.png]]
**'''Comet :''' open the Comet Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
**'''Asteroid :''' open the Asteroid Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
**'''Planet:''' open the Planet Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
**'''Object Name :''' Read-only name of the Dynamic Target, coming from the search
**'''Object Key :''' Read-only key (code/number) of the Dynamic Target, coming from the search
**'''Object Dynamic Type :''' Read-only type of the Dynamic Target, coming from the search
**'''Offset RA (optional)''': An optional +/- offset in HH MM SS or HH MM SS.sss to be added or subtracted from the RA coordinates calculated
**'''Offset DEC (optional)''': An optional +/- offset in DD MM SS or DD MM SS.sss to be added or subtracted from the DEC coordinates calculated

*'''Goto By Offset''': Command the mount to move from actual position by an RA and DEC offset.

[[File:Immagineerferf.png]]

*'''Offset RA''' : +/- offset in HH MM SS or HH MM SS.sss to be added or subtracted from the actual RA coordinates
*'''Offset DEC''' : +/- offset in DD MM SS or DD MM SS.sss to be added or subtracted from the actual DEC coordinates

 

*'''Precise Pointing''': Command the mount to perform a [[Plate Solve Setup#Precision Pointing|precise pointing]] operation to the specified RA/DEC coordinates - slew to the object, plate solve to get actual coordinates, re-slew to correct pointing error:

[[File:Dragscript-precisepointing.png]]

*'''RA J2000''': Enter the RA coordinates in HH MM SS or HH MM SS.sss
*'''DEC J2000''': Enter the DEC coordinates in DD MM SS or DD MM SS.sss
*'''Max Error using Multiple of Profile Error by''': If selected, multiply the maximum allowed pointing error by the number specified in the counter field. E.g., if the [[Mount Setup#Management|Precision Pointing Max Allowed Error]] specified in Mount Setup is 50 arc-seconds, a value of 2 in the counter field here would change the maximum pointing error to 100 arc-seconds. Precise pointing returns an OK (success) result when the error is less than the Max Error.
*'''Max Error is''': If selected, use the value specified in the counter field as the maximum pointing error in arc-seconds. Precise pointing returns an OK (success) result when the error is less than the Max Error.
*'''RoboClip:''' open RoboClip manager windowd and allow to select a target,
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Precise Pointing by Name''': Command the mount to perform a [[Plate Solve Setup#Precision Pointing|precise pointing]] operation to the specified named object - slew to the object, plate solve to get actual coordinates, re-slew to correct pointing error. This action requires Voyager to be connected to the [[Planetarium Setup|Planetarium software]] defined in the current profile. The Object Name must match a name that can be successfully searched in the connected Planetarium software.

*[[File:Dragscript-precisepointing-name.png]]
**'''Object Name''': Name of the object to goto. Must be a name that can be successfully searched in the connected Planetarium software
**'''Offset RA (optional)''': An optional +/- offset in HH MM SS or HH MM SS.sss to be added or subtracted from the RA coordinates returned by the Planetarium software
**'''Offset DEC (optional)''': An optional +/- offset in DD MM SS or DD MM SS.sss to be added or subtracted from the DEC coordinates returned by the Planetarium software
**'''Max Error using Multiple of Profile Error by''': If selected, multiply the maximum allowed pointing error by the number specified in the counter field. E.g., if the [[Mount Setup#Management|Precision Pointing Max Allowed Error]] specified in Mount Setup is 50 arc-seconds, a value of 2 in the counter field here would change the maximum pointing error to 100 arc-seconds. Precise pointing returns an OK (success) result when the error is less than the Max Error.
**'''Max Error is''': If selected, use the value specified in the counter field as the maximum pointing error in arc-seconds. Precise pointing returns an OK (success) result when the error is less than the Max Error.
**'''Default''': Use the default settings
**'''OK''': Save changes and close the window
**'''Cancel''': Discard changes and close the window

*'''Precise Pointing Dynamic Target''': Command the mount to perform a [[Plate Solve Setup#Precision Pointing|precise pointing]] operation to the specified Dynamic Target. RA/DEC will be calculated in real-tim using the RoboOrbits, more info [[Introduction to RoboOrbits|here]].

*[[File:Immaginenn.png]]
**'''Comet :''' open the Comet Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
**'''Asteroid :''' open the Asteroid Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
**'''Asteroid :''' open the Asteroid Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
**'''Object Name :''' Read-only name of the Dynamic Target, coming from the search
**'''Object Key :''' Read-only key (code/number) of the Dynamic Target, coming from the search
**'''Object Dynamic Type :''' Read-only type of the Dynamic Target, coming from the search
**'''Offset RA (optional)''': An optional +/- offset in HH MM SS or HH MM SS.sss to be added or subtracted from the RA coordinates returned by the Planetarium software
**'''Offset DEC (optional)''': An optional +/- offset in DD MM SS or DD MM SS.sss to be added or subtracted from the DEC coordinates returned by the Planetarium software
**'''Max Error using Multiple of Profile Error by''': If selected, multiply the maximum allowed pointing error by the number specified in the counter field. E.g., if the [[Mount Setup#Management|Precision Pointing Max Allowed Error]] specified in Mount Setup is 50 arc-seconds, a value of 2 in the counter field here would change the maximum pointing error to 100 arc-seconds. Precise pointing returns an OK (success) result when the error is less than the Max Error.
**'''Max Error is''': If selected, use the value specified in the counter field as the maximum pointing error in arc-seconds. Precise pointing returns an OK (success) result when the error is less than the Max Error.
**'''Default''': Use the default settings
**'''OK''': Save changes and close the window
**'''Cancel''': Discard changes and close the window

 

*'''Precise Pointing Mount & Rotator''': Command the mount to perform a [[Plate Solve Setup#Precision Pointing|precise pointing]] operation to the specified named object - slew to the object, plate solve to get actual coordinates, re-slew to correct pointing error, rotating the rotator and align to the requested PA within the specified tollerance.

*[[File:PrecisePointingMountRotator.png]]
**'''RA J2000''': Enter the RA coordinates in HH MM SS or HH MM SS.sss
**'''DEC J2000''': Enter the DEC coordinates in DD MM SS or DD MM SS.sss
**'''Max Error using Multiple of Profile Error by''': If selected, multiply the maximum allowed pointing error by the number specified in the counter field. E.g., if the [[Mount Setup#Management|Precision Pointing Max Allowed Error]] specified in Mount Setup is 50 arc-seconds, a value of 2 in the counter field here would change the maximum pointing error to 100 arc-seconds. Precise pointing returns an OK (success) result when the error is less than the Max Error.
**'''Max Error is''': If selected, use the value specified in the counter field as the maximum pointing error in arc-seconds. Precise pointing returns an OK (success) result when the error is less than the Max Error.
** '''Rotation Angle:''' an arbitrary angle that can be a Rotator PA or Sky PA, depends on following setting.
** '''Rotation Type:''' define if the rotation angle is the rotator angle (rotator PA) reported from the driver (and with offset if asked to Voyager in Sync) or the Sky angle (Sky PA) chosen with web dashboard VirtualFOV or planetarium or another system. If you select Sky PA Voyager will use the Plate solve PA result to rotate the rotator to the right angle. If you select the Rotator PA Voyager will just rotating rotator using drive angle at desidered value, no correction using the plate solved PA will be done
** '''PA Tollerance +/-:''' if the PA of rotator is inside the interval given the position will be declared ok and rotator will not be rotate.
** '''Rotator & Meridian Flip:''' "Mantain the Same Image Orientation After the Meridian" if checked force Voyager to shot the target with same orientation in the images taken before anf after meridian. In this case if you have chosen Rotator PA like Rotation type the rotator will be flipped if the mount is after the meridian, if you chosen Sky PA the PA will retained also after the meridian triggering a rotator flip.Use this flag is useful also to use always the same guide star in case of use of OAG or system with high focal lenght.
**'''RoboClip:''' open RoboClip manager windowd and allow to select a target, with RA and DEC will be also acquired the PA
***'''Default''': Use the default settings
***'''OK''': Save changes and close the window
***'''Cancel''': Discard changes and close the window

 

*'''Stop Tracking (Only FS2 Mount)''': Command an FS2 mount to stop tracking
*'''Start Tracking (Only FS2 Mount)''': Command an FS2 mount to start tracking
*'''FS2 Meridian Flip WEST''': Command an FS2 mount to perform a meridian flip to the West
*'''FS2 Meridian Flip EAST''': Command an FS2 mount to perform a meridian flip to the East
*'''Connect Maxim Telescope''': Connect the Telescope/Mount defined in Maxim DL configuration (you must have camera configured in Voyager like Maxim DL)
*'''Disconnect Maxim Telescope''': Disconnect the Telescope/Mount defined in Maxim DL configuration (you must have camera configured in Voyager like Maxim DL) {{Note|The FS2 Mount commands should only be used if your mount is controlled by the Astro Electronic FS2 motor control system. Using these commands with other mounts may fail and cause damage to the mount and other equipment}}

==Dome==
Dome actions send commands to the dome defined in the [[Dome Setup]] area of the active profile:

[[File:Dragscript-dome-217d.jpg]]

*'''Open Shutter''': Command the dome's shutter or the observatory's roll-off roof to open
*'''Close Shutter''': Command the dome's shutter or the observatory's roll-off roof to close
*'''Dome Slave ON''': Send a command to the dome software to "Slave" to the mount. The dome's azimuth position will track with the mount's movements in azimuth
*'''Dome Slave OFF''': Send a command to the dome software to turn off "Slave" to the mount. The dome's azimuth position will stop tracking the mount's azimuth movements
*'''Dome Goto Azimuth''': Command the Dome to rotate to the specified Azimuth

[[File:Dragscript-dome-az.png]]

*'''Azimuth''': Azimuth position the mount should move to in degrees
*'''Cancel''': Discard changes and close the window
*'''OK''': Save changes and close the window

 

*'''Dome Find Home''': Command the dome to find its Home position. If your dome supports the Find Home command, the dome moves to a known position
*'''Dome Park''': Send a Park command to the dome.
*'''Dome Unpark:''' Send an Unpark command to the dome

 
==Camera==
Camera actions can control the camera's cooling system and take exposures

[[File:Dragscript-camera.png]]

*'''Cool Down''': Command the camera's cooling system to cool down to a desired temperature:

[[File:Dragscript-cooldown.png]]

*'''Final Temperature''': Desired sensor temperature in °C
*'''Use Variable:''' check this flag if you want to set the cooling temperature reading the value inside the variable selectable in the drop-down combo instead to use a fixed value
*'''Async Cooling''': If checked, command the cooling system to go to the Final Temperature and do not wait for the cooling system to report that it has reached the desired temperature
*'''Use CCD Firmware Cooldown''': If selected, let the CCD's cooling system manage the speed of the cooldown process
*'''Use Voyager Ramp Mode Cooldown''': If selected, let Voyager's cooldown process manage the speed of the cooldown process. Voyager's process is defined in [[Camera Setup#Cooling System|Camera Setup]]
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Warmup''': Command the camera's cooling system to warmup

[[File:Dragscript-warmup.png]]

*'''Async Cooling''': If checked, command the camera's cooling system to warmup and do not wait for the warmup operation to finish
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Expose''': Take an exposure

[[File:Dragscript-expose-216d.jpg]]

*'''Exposure Type''': Choose Light, Bias, Dark or Flat from the drop-down list
*'''Filter Index''': Choose the filter for the exposure from the drop-down list
*'''Expose''': Enter the exposure length in seconds in the counter field
*'''Use Variable:''' select if you want to get the exposure time from the decimal variable selected in the near list control
*'''Binning''': Select the binning level for the exposure from the counter field
*'''SubFrame''': Select the frame size from the drop-down list: Full Frame, 1/2, 1/4, 1/8, 1/16 or CUSTOM. If you select CUSTOM subframe size, enter the desired subframe size in percent in the counter field that appears
*'''Gain:''' Set the camera's Gain value to the number in the spinner control. Works only if you are using the ASI Camera native driver.
*'''Offset:''' Set the camera's Offset value to the number in the spinner control. Works only if you are using the ASI Camera native driver.
*'''File Directory''': Click the folder icon to select the folder where Voyager should save the image resulting from this exposure
*'''File Name''': Enter the file name to use when saving the image resulting from this exposure
*'''Make Unique File Name''': If checked, add a suffix to the file name if needed to avoid overwriting an existing file
*'''FIT Object Name''': The name to use to populate the OBJECT field in the FITS header
*'''FIT Airmass calculation''': Compute the current airmass value and add to the FITS file header. Airmass is the amount of atmosphere you are imaging through. It is one when imaging directly overhead, and increases as you image closer to the horizon.
*'''Focuser Position Add to FIT Name:''' add the focuser position to the FIT name, only if you are using RoboFire like Autofocus control in Voyager
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

* '''TheSkyX/64 Camera FW Reconnect''': Reconnect camera and filterwheel if the control used for camera in Voyager is TheSkyX or TheSky64

{{Note|Dragscript editor doesn’t have access to profile configuration, for this reason you dont find setting about readout mode and speed in exposure block. Exposure block use auto mode of readout mode and default speed mode. This mean chooses are based on shot type and binning. It retrieve automatically the correct values you set up on Voyager camera setting tab.}} 

{{Note|Filter labels are shown in this dialog if the DragScript editor is opened from Voyager and filter labels are defined in the current profile. Otherwise only filter indexes are shown. The first filter is index zero (0)}}

{{Note|If you check the use variable flag the exposure time used for the exposure will be added to the name of FIT file}} 

==AutoFocus==
These DragScript commands perform Voyager's autofocus operations:

[[File:Dragscript-autofocus.png]]

*'''AutoFocus with RoboStar''': perform an autofocus operation using Voyager's RoboStar method to choose the focus star:

[[File:Dragscript-autofocus-robostar.png]]

*'''Monochromatic Camera''': Select if a monochrome camera is connected. Select a filter to use for the autofocus operation from the drop-down list
*'''DSLR/Color Camera''': Select if a DSLR or Color (OSC) camera is connected
*'''No Filter''': Select if a monochrome camera is connected without filters
*'''Use Low Precision Pointing''': If checked, Voyager's RoboStar operation will slew to the focus star with a more relaxed precision pointing operation. Specify the multiple for the maximum allowed precision pointing error in the counter field. E.g., if the precision pointing max allowed error configured in [[Mount Setup#Management|Mount Setup]] is 50 arc-seconds, a "Multiple Max Allowed Error by" setting of two would relax the maximum allowed pointing error to 100 arc-seconds
*'''AutoFocus OnPlace''': Perform the autofocus operation at the current scope location. Do not use RoboStar to select a focus star
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Simple Goto RoboStar Star''': Perform a simple goto operation to move the mount to the focus star selected by RoboStar:

[[File:DSSimpleGotoRoboStar.png]]

*'''Monochromatic Camera''': Select if a monochrome camera is connected. Select a filter to use for the precise pointing operation from the drop-down list
*'''DSLR/Color Camera''': Select if a DSLR or Color (OSC) camera is connected
*'''No Filter''': Select if a monochrome camera is connected without filters
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Precise Pointing RoboStar Star''': Perform a precise pointing operation to move the mount to the focus star selected by RoboStar:

[[File:Dragscript-precisepointing-robostar.png]]

*'''Monochromatic Camera''': Select if a monochrome camera is connected. Select a filter to use for the precise pointing operation from the drop-down list
*'''DSLR/Color Camera''': Select if a DSLR or Color (OSC) camera is connected
*'''No Filter''': Select if a monochrome camera is connected without filters
*'''Use Low Precision Pointing''': If checked, Voyager will slew to the focus star with a more relaxed precision pointing operation. Specify the multiple for the maximum allowed precision pointing error in the counter field. E.g., if the precision pointing max allowed error configured in [[Mount Setup#Management|Mount Setup]] is 50 arc-seconds, a "Multiple Max Allowed Error by" setting of two would relax the maximum allowed pointing error to 100 arc-seconds
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''RoboFire Focuser Move To''': Move the focuser to a specified absolute or relative position:

[[File:Dragscript-robomove.png]]

*'''Position''': Desired focuser position in steps
*'''Mode''': Choose absolute or relative
**'''Absolute''': Command the focuser to move to the specified position. Your focuser must support absolute positioning.
**'''Relative''': Command the focuser to move in or out by the specified number of steps. Negative numbers move the focuser IN and positive move it out, unless you specify "Reverse Focuser Direction" in [[AutoFocus Setup#RoboFire Configuration Center|Autofocus Setup]]
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''RoboFire Focuser Move From Variable''': Move the focuser to an absolute or relative position stored in a variable:

[[File:Dragscript-robomove-variable.png]]

*'''Get Position From Variable''': select the variable that contains the position
*'''Mode''': Choose absolute or relative
**'''Absolute''': Command the focuser to move to the specified position. Your focuser must support absolute positioning.
**'''Relative''': Command the focuser to move in or out by the specified number of steps. Negative numbers move the focuser IN and positive move it out, unless you specify "Reverse Focuser Direction" in [[AutoFocus Setup#RoboFire Configuration Center|Autofocus Setup]]
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

{{Note|Be sure to select the right Variable and that the variable is valorized before using this block or you can lost focus. Be sure also to have inserted limits on RoboFIre configuration to avoid damage to your focuser.}}

*'''AutoFocus with RoboFire LocalField''': Perform Voyager's LocalField (multiple star) autofocus routine

[[File:Dragscript-localfield.png]]

*'''Monochromatic Camera''': Select if a monochrome camera is connected. Select a filter to use for the precise pointing operation from the drop-down list
*'''DSLR/Color Camera''': Select if a DSLR or Color (OSC) camera is connected
*'''No Filter''': Select if a monochrome camera is connected without filters
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 
==Rotator==
Rotator actions can move the rotator to a specified Position Angle or flip the rotator 180 degrees:

[[File:Dragscript-rotator.png]]

 

*'''Rotator Move To''': Move the rotator to the specified position angle in degree
**[[File:Dragscript-rotatormove.png]]
***'''PA''': Move the rotator to this Position Angle in degrees
***'''OK''': Save changes and close the window
***'''Cancel''': Discard changes and close the window

*
*'''Rotator 180° Flip''': Move the rotator to a position 180 degrees opposite its current position
*'''Rotator Sync''': Synchronize the mechanical position to the submitted position (create an offset to the mechanical position)
**[[File:RotatorSyncBlockConf.png]]
***'''Rotator Sync To:''' with this option Voyager will sync the rotator PA to the PA in the next field
***'''PA:''' Position Angle to use for sync
***'''Use Variable:''' get PA value from the selected variable
***'''Reset Rotator Sync:''' with this option Voyager will reset the Sync (remove the offset applied to the mechanical position of rotator)
***'''Default:''' reset all parameters in the form to the default values
***'''Cancel:''' exit from the configuration form without saving anything
***'''OK:''' accept the inserted value and store data

* '''Precise Rotate SkyPA''': Move the rotator to the specified SkyPA position
** [[File:PRSKYPADS.png]]
*** '''Rotation Angle''': SKY PA in degree to use for positioning the rotator
*** '''PA Tollerance +/-''': max allowed difference in degree between solved PA and requested PA
*** '''Save Final Rotator PA to this DragScript Decimal:''' if flagged save the Rotator PA degree of pointing (if positioned ok) to the decimal variable selected in the combobox
*** '''OK''': Save changes and close the window
*** '''Cancel''': Discard changes and close the window

==Flat Device==
Flat Device commands can open and close the flat device cover:

[[File:Dragscript-flat-device.jpg]]

*'''Open Flat Device Cover''': Command the flat device to open
*'''Close Flat Device Cover''': Command the flat device to close
*'''Switch On Light Flat Device''': Turn the light on for the specified Flat Device

[[File:Dragscript-switch-on-flat-device.jpg]]

*'''Device ID''': Choose the Flat Device number to control with this command. See [[Flat Device Setup]] for more information on flat devices.

 

*'''Switch Off Light Flat Device''': Turn the light off for the specified Flat Device

[[File:Dragscript-switch-off-flat-device.jpg]]

*'''Device ID''': Choose the Flat Device number to control with this command. See [[Flat Device Setup]] for more information on flat devices.

 

*'''Select Brightness Flat Device''': Set the brightness level for the specified Flat Device.

[[File:Dragscript-select-brightness.jpg]]

*'''Device ID''': Choose the Flat Device number to control with this command. See [[Flat Device Setup]] for more information on flat devices.
*'''Brightness''': Brightness level for the specified Flat Device. 
{{Note|If you have a flat device that can open and close, don't forget to issue an Open Flat Device command in your DragScript before taking exposures including plate solving and autofocus!}}

==Script==
The Script action can run an external script or program:

[[File:Dragscript-script-external.png]]

[[File:External-script-1.png]]

*'''File Program/Script''': Click the folder icon to select the program or script to run
*'''Arguments''': Command line arguments to be passed to the program or script when invoking it
* '''JOLLY Strings''':there are some special strings called jolly that can be used in argument line will be replaced with some data from Voyager environment or DragScript variables
** '''Internal IPs:''' ##INTERNAL-IP## write a list of all internal IPs avalaible in the system
** '''External IP''': ##EXTERNAL-IP## write a list of external IP assigned to your PC(router) if you have internet connection up
** '''NOW''': ##NOW## write the actual date and time
** '''Mount Altitude''': ##MOUNT-ALT## write the actual altitude of Telescope Mount if connected
** '''Mount Azimuth''': ##MOUNT-AZ## write the actual azimuth of Telescope Mount if connected
** '''Variable''': ##VAR-name## where you must replace the ''name'' with the real name of your variable (case sensitive) , write the actual value of you variable (decimal, string or counter)
*'''Wait For Program/Script''': If checked, wait for the program or script to return before continuing (synchronous execution)
*'''On Timeout Kill Program/Script''': If checked, and the "Wait for Program/Script" option is checked, and the "Wait / Timeout" time period has elapsed, terminate the external program or script
*'''Return OK to DragScript Engine only if Script return this''': If checked, the script or program must return the value specified in the text field in order for this action to be considered a success and return OK
*'''Save External Script output to this DragScript String''': If checked, store the value that the external script or program returns in STDOUT to the DragScript string variable chosen from the drop-down list
*'''Save External Script output to this DragScript Decimal''': If checked, store the value that the external script or program returns in STDOUT to the DragScript decimal number variable chosen from the drop-down list
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 
{{Note|Voyager will only terminate the specified program or script when the timeout period expires. If the called program calls other programs, they will not be terminated by Voyager}}{{Note|Use of Jolly String and DragScript Variables in arguments line is reserved to who have purchased and activated the Voyager Developer Plugin}}
{{Note|If the value returned from STDOUT is stored in a DragScript decimal number, be sure that the number returned uses a period as the decimal point separator}}

'''Example of Use'''

In this example, we call a Python script located in the directory d:\VScheduler\Scheduler.py, and wait up to 10 seconds for the script to complete.

The Python script writes a value to STDOUT with this code:<blockquote>import sys</blockquote><blockquote>sys.stdout.write('RUN')</blockquote><blockquote>sys.stdout.flush()</blockquote>We store that value in the SchedulerResult DragScript string variable. We can then make decisions in the DragScript using the DO IF STRING VALUE statement.

[[File:Script-scheduler-example.jpg]]

 
==Timing==
Timing actions inform DragScript to wait before performing an action. You can wait for a time interval, an absolute time to be reached, astronomical night with an offset, or for an object to reach a desired altitude:
 [[File:Dragscript-timing-211a.jpg]]

*'''Wait Time''': Wait for a specified time to arrive or to elapse

[[File:Dragscript-waittime.png]]

*'''Interval/Time''': Enter a time in HH MM SS.
*'''Wait Type''': Chose Absolute or Relative
**'''Absolute''': Wait until this absolute time is reached. If the time specified is more than 12 hours in the future, Voyager will assume this time has passed and will not wait. For example, if the specified time is 20:00:00 and this action is executed at 20:15:00, Voyager will not wait because that would cause a wait until tomorrow night, which is probably not what you intended
**'''Relative''': Wait for this amount of time to elapse
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 

 

*'''Wait Altitude''': Wait until the object at the given RA and DEC coordinates reaches the specified altitude, either rising or setting:

[[File:Dragscript-wait-altitude.png]]

*'''RA Target J2000''': RA coordinates of the object you want to reach the Reference Altitude in HH MM SS or HH MM SS.sss
*'''DEC Target J2000''': DEC coordinates of the object you want to reach the Reference Altitude in DD MM SS or DD MM SS.sss
*'''Reference Altitude''': Altitude to reach in degrees
*'''Exit Wait if Actual Altitude GREATER than or EQUAL (>=) to reference''': Wait until the target rises above the reference altitude
*'''Exit Wait if Actual Altitude LOWER than or EQUAL (>=) to reference''': Wait until the target sets below the reference altitude
*'''Wait Altitude until absolute time''': The Wait Altitude operation will terminate when this time is reached, whether or not the target has reached the reference altitude. This is usually done to end the wait with morning light
*'''Activate Antiglitch Altitude Reading System:''' set the flag if you want to activate an AntiGlitch system to avoid glitchy readings of values from mount drivers that have undeclared bugs (3 continuous readings are done to get the OK). Sometime happens in buggy drivers a single reading is damaged and trigger the OK to wait altitude status. I fyou have this problem activate the flag but report the problem to the mount driver developer.
* '''RoboClip:''' load RA and DEC from RoboClip catalog
* '''Coords From Sequence:''' load RA and DEC from a sequence file
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''Wait Altitude Dynamic Target''': Wait until the object at the calculated RA and DEC coordinates of a Dynamic Target reaches the specified altitude, either rising or setting:

[[File:Immagineddd.png]]

*'''Comet :''' open the Comet Finder in RoboOrbits, see more [https://wiki.starkeeper.it/index.php/RoboOrbits_Finders here]
*'''Asteroid :''' open the Asteroid Finder in RoboOrbits, see more [https://wiki.starkeeper.it/index.php/RoboOrbits_Finders here]
*'''Object Name :''' Read-only name of the Dynamic Target, coming from the search
*'''Object Key :''' Read-only key (code/number) of the Dynamic Target, coming from the search
*'''Object Dynamic Type :''' Read-only type of the Dynamic Target, coming from the search
*'''Reference Altitude''': Altitude to reach in degrees
*'''Exit Wait if Actual Altitude GREATER than or EQUAL (>=) to reference''': Wait until the target rises above the reference altitude
*'''Exit Wait if Actual Altitude LOWER than or EQUAL (>=) to reference''': Wait until the target sets below the reference altitude
*'''Wait Altitude until absolute time''': The Wait Altitude operation will terminate when this time is reached, whether or not the target has reached the reference altitude. This is usually done to end the wait with morning light
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*

*'''Wait Astronomical/Nautical/Civil Night''': Wait until astronomical/nautical/civil night, with an optional offset:

[[File:Dragscript-wait-night.png]]

*'''Get Latitude and Longitude from Mount''': Retrieve the current latitude and longitude from the connected mount, which must support this command. This location is used, along with the current date, to determine the time that night begins
*'''Use the Latitude and Longitude indicated below''': Specify your current latitude and longitude in the fields below. This location is used, along with the current date, to determine the time that night begins
*'''Offset''': Time in HH MM SS
**'''Offset Before''': If selected, exit the wait this amount of time before night
**'''Offset After''': If selected, exit the wait this amount of time after night
*'''Exit with ERROR if Wait Time is Greater than:''' if this option is flag the DragScript will exit with Error if the time wait for the begin of the next astronomical night is greater than the value in hour expressed in the numeric edit. Useful if you want to detect that the actual night is already finished and the dragscript can exit otherwise without this flag the next astrnomical night will be waited
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window
*
*
*'''Wait Dusk''' [[File:Dragscript-wait-dusk.jpg]]

*'''Get Latitude and Longitude from Mount''': Retrieve the current latitude and longitude from the connected mount, which must support this command. This location is used, along with the current date, to determine the time that dusk begins
*'''Use the Latitude and Longitude indicated below''': Specify your current latitude and longitude in the fields below. This location is used, along with the current date, to determine the time that dusk begins
*'''Offset''': Time in HH MM SS
**'''Offset Before''': If selected, exit the wait this amount of time before dusk
**'''Offset After''': If selected, exit the wait this amount of time after dusk
*'''Save Time to Event (minutes) in Decimal''': Save the computed time until Dusk in a decimal variable. See the DragScript example below for one way to use this.
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

You can configure the time at which dusk begins in the [[Flat Device Setup#Sky Flat|SkyFlat section of Flat Device]] Setup. {{Note|If dusk (plus or minus the offset if one is specified) has already passed, Wait Dusk returns OK if it has been less than 12 hours since dusk, else it returns ERROR if has been more than 12 hours}}

*'''Wait Dawn'''

[[File:Wait-dawn-2.jpg]]

*'''Get Latitude and Longitude from Mount''': Retrieve the current latitude and longitude from the connected mount, which must support this command. This location is used, along with the current date, to determine the time that dawn begins
*'''Use the Latitude and Longitude indicated below''': Specify your current latitude and longitude in the fields below. This location is used, along with the current date, to determine the time that dawn begins
*'''Offset''': Time in HH MM SS
**'''Offset Before''': If selected, exit the wait this amount of time before dawn
**'''Offset After''': If selected, exit the wait this amount of time after dawn
*'''Save Time to Event (minutes) in Decimal''': Save the computed time until dawn in a decimal variable. See the DragScript example below for one way to use this.
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

You can configure the time at which dawn begins in the [[Flat Device Setup#Sky Flat|SkyFlat section of Flat Device]] Setup.
 {{Note|If dawn (plus or minus the offset if one is specified) has already passed, Wait Dawn returns OK if it has been less than 12 hours, else ERROR if more than 12 hours}}

*

*'''Wait Safe''': Wait Safe Condition wait the safe condition before allow dragscript to execute net instruction. During the wait the events like Emergency Exit and Emergency suspend will be disabled and not managed. Just to remember you emergency events can coming from Viking I/O, Safe Monitor control, Weather Condition control. Like said this action will forcing event disable until exit for timeout or for safe. So be sure to have the observatory on the right configuration to avoid weather damage (closed and all parked). This action allow Voyager to run forever DragScript in case of no emergency exit. Can wait a time or an interval or the presence of astronomical/nautical/civil night, with an optional offset. Usually this is the first action in a script, its a good thing to put the Start node in Event disabled mode when you are manage the events in your DragScript. Also remember that the event at exit of this action will be restored to the original status, if they are disabled they will be leave disable or viceversa. We suggest also generally in dragscript to disable events during an atomic tasks like the opening observatory and connect setup to avoid interruption not really needed with impredictable results. If the action finish for wait will produce a status of TIMEOUT to the DragScript, if the action finish for one of the exit options will produce a status of ERROR to the DragScript, if the action found a SAFE status inside the wait option will produce a status of OK to the DragScript. You can decide if repeat the the action in a never ending loop (if you use night this mean to wait for the next night if you not check the exit ERROR options) or simple end the DragScript if you start DragScript night by Night. Rember that an Emergency Exit in any case will exit the DragScript.

{{Note|Wait SAFE Cannot be used inside the Event Manager (Exit, Suspend, Resume)}}

[[File:DSWaitSafe.png]]

*'''Wait SAFE until finish Night''': this option wait SAFE status until on eof specified kind of Nights is finished
**'''Get Latitude and Longitude from Mount''': Retrieve the current latitude and longitude from the connected mount, which must support this command. This location is used, along with the current date, to determine the time that astronomical night begins and end
**'''Use the Latitude and Longitude indicated below''': Specify your current latitude and longitude in the fields below. This location is used, along with the current date, to determine the time that astronomical night begins and end
**'''Night TYPE:''' the night to wait between Astronomical (Astrophotographers dark night -18° sun) , Nautical (-12° sun), Civil (-6° sun)
**'''Offset''': Time in HH MM SS
***'''Offset Before''': If selected, exit the wait this amount of time before astronomical night
***'''Offset After''': If selected, exit the wait this amount of time after astronomical night
*'''Wait SAFE until absolute time''': this option wait SAFE status until the absolute time you put inside the hh mm ss field
*'''Wait SAFE for a time interval of:''' this option wait SAFE status until the amount of time in the interval will be elapsed
*'''EXIT Options:''' with this options you can decide to exit with ERROR it the conditions inside is true
**'''Exit with ERROR if the Astronomical Night has ended less than:''' if this option is flag the DragScript will exit with Error if the astronomical night is ended by the time in hh field. This work and be active only if you use Wais SAFE with astronomical night. This flag enabled prevento to wait for the next night if the night is finished and you want to shutdown all without wait the next night.
**'''Exit with ERROR if Wait Time is greater than:''' if this option is flag the DragScript will exit with EORR if the time to wait is greater than the value in the hh field. This option is active only if you choose the Wait SAFE until absolute time. Useful if you dont wait over a certain time span.
*'''EVENT CHECK options:''' with this option you can decide to remove from processing status of SAFE some kind of events that will be ignored (event in any case are disable during the wait safe action)
**'''Check Emergency Exit Status in SAFE status calculation:''' if unchecked the condition that throw an Emergency Status will be ignored in calculation of SAFE Staus . ATTENTION !! this is a way really dangerous for your setup .. use only if you want to wait safe in particular condition , particular timing and for particular tasks
**'''Check Emergency SUSPEND Status in SAFE status calculation:''' if unchecked the condition that throw an Emergency Status will be ignored in calculation of SAFE Staus . ATTENTION !! this could be a way really dangerous for your setup .. use only if you want to wait safe in particular condition , particular timing and for particular tasks.
*'''LIGHT CONDITIONS options:''' with this option you can decide to remove from processing status of SAFE the LIGHT Conditions status
**'''Remove Weather LIGHT Conditions Status From Calculation of All Emergency Status:''' if unchecked the LIGHT conditions from Weather system will be not used to calculate the SAFE Status. Usefull if you want to open the dome with the light approaching the night time and do skyflat. For the Dawn flat you can decide to disable the LIGHT event using dedicated block
*'''MOON PHASE Options''' (Only for ADVANCED and FULL License Voyager versions): useful to ignore Safe status if the Moon Phase is over certains value
**'''Unsafe if Moon Phase equal or greater than:''' if checked Voyager will check the Moon Phase and if the value is equal or greater than the one indicated will return Unsafe to Emergency Events system
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

==Using the Time to Event Value in a DragScript==
Here's an example of using the '''Save Time to Event (minutes)''' value in a DragScript.

The basic idea is that you can decide whether or not to execute any actions based on how many minutes there are until or after dawn or dusk.

[[File:Dragscript-wait-dawn-2.jpg]]

The decimal variable "'''Minutes Before Event'''" is initialized to 0.

The '''Wait Dawn: Data from connected Setup - Offset (Before) 00:15:00 [hh:mm:ss]>>Minutes Before Event''' action waits until 15 minutes before dawn, and then puts the value 15 into the variable '''Minutes Before Event'''

The '''DO IF DECIMAL VALUE''' block will execute if the '''Minutes Before Event''' variable is between 0 and 15. If not, control passes to the End block.

The '''Goto Block: DAWN FLAT''' statement sends control back to that block, and the minutes before or after dawn are computed again and stored in the '''Minutes Before Event''' variable.

If it is after dawn when the '''Wait Dawn''' action runs, the value stored in '''Minutes Before Event''' will be negative, and the '''DO IF DECIMAL VALUE''' statement will not run.

 

==Signals==
Signals actions let you send notifications via email, Skype or SMS:

[[File:Dragscript-signals.png]]

{{Note|As of Voyager 2.1.4a, you can use the Save without Personal Info button to save a copy of your DragScript with all personal info (email addresses, email account logins, phone numbers, etc.) deleted. Use this save mode before posting a script online or sharing with others.}}

[[File:Dragscript-editor-toolbar-3.png]]

Use button 5 to save your DragScript with the personal info deleted for any of the actions in this group (Signals).

 

*Send Email using Voyager Account: Send an email using Voyager's email account. You must have an active [[Licensing|support and update Voyager license]] to use this option and an Internet connection

[[File:Dragscript-send-email.png]]

*'''Mail to''': Email address to send to
*'''Object''': Subject line of email TYPO: Should be Subject instead of Object
*'''Text''': Body of email
*'''Cancel''': Discard changes and close the window
*'''OK''': Save changes and close the window
*'''JOLLY Strings''':there are some special strings called jolly that can be used in mail text and will be replaced with some data from Voyager environment or DragScript variables
**'''Internal IPs:''' ##INTERNAL-IP## write a list of all internal IPs avalaible in the system
**'''External IP''': ##EXTERNAL-IP## write a list of external IP assigned to your PC(router) if you have internet connection up
**'''NOW''': ##NOW## write the actual date and time
**'''Mount Altitude''': ##MOUNT-ALT## write the actual altitude of Telescope Mount if connected
**'''Mount Azimuth''': ##MOUNT-AZ## write the actual azimuth of Telescope Mount if connected
**'''Variable''': ##VAR-name## where you must replace the ''name'' with the real name of your variable (case sensitive) , write the actual value of you variable (decimal, string or counter)

 

*'''Send Email''': Send an email notification using a specified email server and account. Requires an Internet connection

[[File:Dragscript-sendemail.png]]

*'''Mail From''': Email address this message is from
*'''Mail to''': Email address to send to
*'''Object''': Subject line of email TYPO: Should be Subject instead of Object
*'''Text''': Body of email
*'''SMTP User''': Username to login to SMTP (mail) server. Check with your local ISP or network administrator if you don't know how to login to your SMTP server to send email
*'''SMTP Password''': Password to login to your SMTP (mail) server
*'''SMTP Server''': Hostname or IP address of your SMTP (mail) server
*'''SMTP Port''': Port number of your SMTP (mail) server
*'''Use SSL''': If checked, use an SSL (secure) connection to your mail server
*'''GMAIL''': Click this button to use the SMTP server and port information for Google Gmail
*'''HOTMAIL''': Click this button to use the SMTP server and port information for Microsoft Hotmail
*'''Cancel''': Discard changes and close the window
*'''OK''': Save changes and close the window

*'''JOLLY Strings''':there are some special strings called jolly that can be used in mail text and will be replaced with some data from Voyager environment or DragScript variables
**'''Internal IPs:''' ##INTERNAL-IP## write a list of all internal IPs avalaible in the system
**'''External IP''': ##EXTERNAL-IP## write a list of external IP assigned to your PC(router) if you have internet connection up
**'''NOW''': ##NOW## write the actual date and time
**'''Mount Altitude''': ##MOUNT-ALT## write the actual altitude of Telescope Mount if connected
**'''Mount Azimuth''': ##MOUNT-AZ## write the actual azimuth of Telescope Mount if connected
**'''Variable''': ##VAR-name## where you must replace the ''name'' with the real name of your variable (case sensitive) , write the actual value of you variable (decimal, string or counter)

 

*'''Start Skype Call''': Start a Skype call from the computer running Voyager. Requires an Internet connection

[[File:Dragscript-skype.png]]

*'''Phone Number to Call''': Phone number or Skype name to call using Skype
*'''After Command Wait''': Time in seconds to wait after sending the command before timing out if no response from Skype
*'''After leave ringing for''': Time in seconds to wait after Skype places the call and the remote phone starts to ring
*'''Skype Exe Directory''': Location of Skype program on this computer
*'''Find Skype''': Look for Skype program on this computer and fill out the Skype Exe Directory if found
*'''Test''': Try to make a Skype call using the information in this dialog window
*'''Cancel''': Discard changes and close the window
*'''OK''': Save changes and close the window

 

*'''Send SMS with Nexmo'''
**Send an SMS (text message) using the Nexmo service: https://www.nexmo.com/ Requires an Internet connection.

[[File:Dragscript-nexmo.png]]

*'''Source Number or Name''': Phone number of sender, or name of sender. For country like USA this is a constraint to use (phone number) to avoid error in transmission (from Voyager version 2.2.1d)
*'''To Telephone Number''': Phone number to send SMS message to
*'''Text''': Body of SMS messages
*'''API Key''': API Key for Nexmo service - you must sign up at https://www.nexmo.com/ to get an API key and secret
*'''API Secret''': API Secret for Nexmo service
*'''Cancel''': Discard changes and close the window
*'''OK''': Save changes and close the window

*'''JOLLY Strings''':there are some special strings called jolly that can be used in mail text and will be replaced with some data from Voyager environment or DragScript variables
**'''Internal IPs:''' ##INTERNAL-IP## write a list of all internal IPs avalaible in the system
**'''External IP''': ##EXTERNAL-IP## write a list of external IP assigned to your PC(router) if you have internet connection up
**'''NOW''': ##NOW## write the actual date and time
**'''Mount Altitude''': ##MOUNT-ALT## write the actual altitude of Telescope Mount if connected
**'''Mount Azimuth''': ##MOUNT-AZ## write the actual azimuth of Telescope Mount if connected
**'''Variable''': ##VAR-name## where you must replace the ''name'' with the real name of your variable (case sensitive) , write the actual value of you variable (decimal, string or counter)

 
{{Note|Nexmo is an online service that offers voice and data communication. To use Nexmo from Voyager you must register at their site at https://www.nexmo.com}}

 

* '''Send Telegram'''
** Send an message using Telegram service chatbot: https://www.telgram.org/ Requires an Internet connection.
** [[File:SaveTelegramBlock.png]]

* '''Text''': message
* '''API ID''': API ID (token create during the chatbot) of your Telegram user
* '''Chat ID''': ID number assigned to chatbot created, you can get opening the link [https://api.telegram.org/bot<your https://api.telegram.org/bot<YOUR_TOKEN>/getUpdates]
* '''Cancel''': Discard changes and close the window
* '''OK''': Save changes and close the window

* '''JOLLY Strings''':there are some special strings called jolly that can be used in mail text and will be replaced with some data from Voyager environment or DragScript variables
**'''Internal IPs:''' ##INTERNAL-IP## write a list of all internal IPs avalaible in the system
** '''External IP''': ##EXTERNAL-IP## write a list of external IP assigned to your PC(router) if you have internet connection up
** '''NOW''': ##NOW## write the actual date and time
** '''Mount Altitude''': ##MOUNT-ALT## write the actual altitude of Telescope Mount if connected
**'''Mount Azimuth''': ##MOUNT-AZ## write the actual azimuth of Telescope Mount if connected
**'''Variable''': ##VAR-name## where you must replace the ''name'' with the real name of your variable (case sensitive) , write the actual value of you variable (decimal, string or counter)
'''Guide to obtain API ID and Chat ID''' :

# Download the Telegram APP on your mobile phone and register
# Open a chat with @BotFather and type /newbot to create a new private bot
# You will be asked for a friendly name - choose whatever you like, e.g. VoyagerMessages
# You will be given an "API Token" - save this somewhere - it is what you will enter as the API ID in your DragScript action, as shown above
# In your browser (can be on a desktop, doesn't have to be on your phone) open the link <nowiki>https://api.telegram.org/botYOUR-TOKEN/getUpdates</nowiki> replacing YOUR-TOKEN with the API Token
# You will get a short message that starts with {"ok":true. It won't have the Chat ID yet - this is OK
# Go back to Telegram and find the last message from @BotFather that starts with "Congratulations on your new bot. You will find it at ..." Click on that link and a new message room will open in Telegram, talking to your bot
# Type at least one message - a simple "hello" will do
# Go back to the browser page you opened in step 5 and hit reload - now you should see more characters including a long number after "from":{"id": That number is the Chat ID, which you use in your DragScript Send Telegram action as shown above
# If you don't see the Chat ID, try sending a couple more messages to your bot in Telegram and then quickly reload your browser until you get the ID
# That's it - you can now use the API ID and Chat ID to send Telegram messages from your DragScript

==User Manual Input==
User manual input actions allow interactions between Voyager and the user:

[[File:DragScriptUserInter.png]]

 

*'''Wait User OK''': Ask to the user with a windows prompt to press a button on the screen to continue or to abort and also its possible to activate a timeout during waiting of the user interaction
*[[File:DragScriptWaitUser.png]]
*'''Wait Mode''': how the wait will be work
*'''Use Timeout of:''' with this option the wait will finish in anycase after the seconds selected
*'''In case of timeout exit with:''' if the Use timeout of option will be used then exit can be selected between TIMEOUT or OK action result, this result will be usable in the DragScript using the IF condition related to actions
*'''No Timeout:''' with this option the wait will be for ever until physically user press the button on the screen
*'''Message:''' show a text message inside window prompt to the user
*'''Show Variable Value:''' show a text rappresentation of the variable selected inside window prompt to the user
*'''Wait User DATA''': Ask to the user with a windows prompt to input data (DECIMAL,STRING, COUNTER depends on type of variable used for storage) to continue or to abort and also its possible to activate a timeout during waiting of the user interaction. The inpout data will be stored in the selected variable.
*[[File:Immaginewefwef.png]]
*'''Wait Mode''': how the wait will be work
*'''Use Timeout of:''' with this option the wait will finish in anycase after the seconds selected
*'''In case of timeout exit with:''' if the Use timeout of option will be used then exit can be selected between TIMEOUT or OK action result, this result will be usable in the DragScript using the IF condition related to actions
*'''No Timeout:''' with this option the wait will be for ever until physically user press the button on the screen
*'''Message:''' show a text message inside window prompt to the user
*'''Show Variable Value:''' show a text rappresentation of the variable selected inside window prompt to the user
*'''Insert Data in Variable:''' the data in input from the user will be stored in the selected DragScript variable (variable must be declared before use it in DragScript). Based on type of DragScript Variable the edit mask of input field will be adapted. 
{{Note|if you using No Timeout option you must be really to be present in front of your PC to continue}}

==Optec Perseus==
Optec Perseus actions allow to interact with the hardware [https://optecinc.com/astronomy/catalog/perseus/default.htm Port Instrument Selector from Optec] :

[[File:OptecPer1.png]]

 

*'''Optec Perseus Read Device Info''': ask information about device and save it in environment variables of DragScript
*'''Optec Perseus Read Device Status''': ask status of device and save it in environment variables of DragScript
*'''Optec Perseus Homing''': command to device to Homing
*'''Optec Perseus Set Port:''' rotate device to select the port selected index
**[[File:OptecPer2.png]]
**'''Port:''' port index to select

 
{{Note|ASCOM Switch driver of Optec Perseus must be installed in order to allow working the DragScript Blocks}}

== Donuts ==
Donuts actions allow to interact with the software Donuts developed by Kames MacCormac, used for advanced research pointing, code here https://github.com/jmccormac01/Donuts :

[[File:DonutsSection.png]]

*'''Donuts Calibration''': ask to Donuts process to performe a Calibration using camera and mount

[[Category:DragScript]]
[[Category:All]]
[[Category:Manual|Lb]]

File:Immaginenn.png

2024-06-29T13:58:47Z

Leonardo: Leonardo uploaded a new version of File:Immaginenn.png

DragScript Elements

2024-06-29T13:57:55Z

Leonardo: /* Guiding */

__TOC__

The DragScript "language" is composed of blocks that are dragged from the list on the right side of the DragScript editor to the script being created or edited on the left.

Each category of element is organized in list that can be expanded or contracted by clicking the "+" or "-" next to the element category name:

[[File:Dragscript-editor-elements.png]]

E.g., if you click the + in front of Actions, the list expands like this:

[[File:List-expanded.png]]

As you can see in the case of Actions, there are further subcategories of actions, and clicking the + in front of one of them expands it again:

[[File:Subcategory-expanded.png]]

Here, the list of Setup actions is fully expanded and we see three choices that we can drag to the active script: Connect Setup, Connect Setup with Timeout, and Disconnect Setup

For the remainder of this page, we will describe the available DragScript elements. New elements are added periodically and will be documented in the release notes and here.

Press Sort button to listing all the categories and blocks in alphabetical order.

==DragScript Actions==

===Operating System===
The Operating System actions control the PC running Voyager:

[[File:DSopOs.png]]

*'''Shutdown PC''': Shutdown the PC running Voyager
*'''Restart PC''': Restart (reboot) the PC running Voyager
*'''Hybernate PC:''' Hybernate the PC running Voyager (only in OS that support it)
*'''Suspend PC:''' Susend the PC running Voyager (only in OS that support it)
*'''Kill Process''': Kill a process on the PC running Voyager. Either type in the Process name or click one of the buttons to use a preconfigured process name.

[[File:Kill-process.png]]

*'''Serial Port STRING Transmit''': Send a text string with a terminator (if necessary) to an RS232 Serial Port

[[File:SerPortTx.png]]

*'''Configuration'''
**'''Serial Port Config''': insert the string used to configure and open the serial port (portname,portspeed,databit,parity,datastopbit) for parity use N=None O=Odd E=Even (Example COM1,9600,8,N,1)
**'''Text to Send''': input the text to send to the serial port
**'''Use Terminator''': indicate if you want to use a terminator or not. CR = carriage return, LF=Line feed
*'''Serial Port BINARY Transmit''': Send Binary data string to an RS232 Serial Port

[[File:SerPortBin.png]]

*'''Configuration'''
**'''Serial Port Config''': insert the string used to configure and open the serial port (portname,portspeed,databit,parity,datastopbit) for parity use N=None O=Odd E=Even (Example COM1,9600,8,N,1)
**'''Binary Data To Send(*):''' input the binary data to send to the serial port. Binary Data must be entered ad a string in hexadecimal format separated (Example 0A 0B 0C A1 A2 A3)
*'''UDP IP/Port STRING Transmit''': Send a text string with a terminator (if necessary) to an UDP Port
[[File:Txudpstring.png]]

* '''Configuration'''
**'''IP/Hostname''': IP or hostname of PC where to send data
**'''Port:''' UDP port number to use for transmission
**'''Text to Send''': input the text to send to the UDP Port
**'''Use Terminator''': indicate if you want to use a terminator or not. CR = carriage return, LF=Line feed
*'''UDP IP/Port BINARY Transmit''': Send Binary data string to an RS232 Serial Port
*[[File:UDPIPBinaryTX.png]]
* '''Configuration'''
** '''IP/Hostname''': IP or hostname of PC where to send data
**'''Port:''' UDP port number to use for transmission
** '''Binary Data To Send(*):''' input the binary data to send to the serial port. Binary Data must be entered ad a string in hexadecimal format separated (Example 0A 0B 0C A1 A2 A3)

==Setup==
Setup actions control connecting and disconnecting to your equipment and software:

[[File:Dragscript-setup-2.14c.png]]

*'''Connect Setup''': Commands Voyager to connect to the equipment and software in the currently selected [[Setup#Profile Management|Profile]]
*'''Connect Setup with Timeout''': Command Voyager to connect to the equipment in the currently selected [[Setup#Profile Management|Profile]]. Voyager will timeout if connection does not complete within the specified number of seconds:

[[File:Setup-timeout.png]]

*'''Disconnect Setup''': Command Voyager to disconnect from the equipment and software in the currently selected [[Setup#Profile Management|Profile]]
*'''Force Disconnect Setup''': Command Voyager to forcefully disconnect the Seup without checking if the previous connection was actually successful (all setup checks connected regularly)
*'''Connect Safety Monitor Control''': Connect only the Safety Monitor control. This is useful for monitoring conditions prior to connecting all your equipment
*'''Disconnect Safety Monitor Control''': Disconnect only the Safety Monitor control
*'''Connect Flat Device #1 / #2 Control''': Connect only the Flat Device #1/#2. This is useful for switch on the flat device only when needed
*'''Disconnect Flat Device #1 / #2 Control''': Disconnect only the Flat Device #1/#2 control

 

==Voyager==
Interaction with Voyager Application:

[[File:Immagine 2021-04-05 193048.png]]

* '''Change Voyager Profile''': will allow changing of profile from DragScript. Voyager must have the setup not connect or action will failed.
** [[File:Immaginefefefr.png]]
*** '''Profile:''' Profile select, and list of all profile if retrieved from Voyager
*** '''Get Voyager Profiles List:''' listg of profiles will be retrieved directly from Voyager using the Application Server. Male sure that the Application Server in Voyager is active
*** '''OK''': Click to save your changes and close the window
***'''Cancel''': Click to discard your changes and close the window
* '''Empty Voyager Temporary Folders''': will remove all file from the temporary folders of Voyager (for example the FIT folder where is the temporary Shot for platesolving or pointing)

==Session==
Session actions run sequences to acquire images, flat frames, and shutdown ("Good Night") your system:

[[File:Session-script.png]]

*'''RoboTarget''': Robotic Scheduler Available only in [https://software.starkeeper.it/voyager-advanced/ Voyager Advanced version]
*'''Sequence''': Run a [[Sequence Configuration|Sequence]] with options:

[[File:Dragscript-sequence-211g.jpg]] 

*'''Configuration Panel''':
**Click the folder icon [[File:Folder-icon.png]] to select the Sequence file to run. [[Sequence Configuration|Create your Sequence files]] in Voyager's OnTheFly workspace
**'''Start/TimeSpan''': Click one of the radio buttons to use that option to tell when to start and end the sequence. This is one way to have Voyager image this target until a specific time is reached, or an interval has elapsed. It is a good idea to specify an ending time here, or a minimum altitude in the Sequence definition or the Options field below, so Voyager will not continue trying to take images after the object has set
***'''Start and End from Sequence:''' Use the start and end times specified in the sequence definition file. The start time comes from the [[Sequence Configuration#On Start Tab|On Start tab]] and the end time comes from the [[Sequence Configuration#On End Tab|On End tab]]
***'''Immediately Start and Finish After Interval''': Start the sequence immediately and end it after the HH:MM:SS amount of time specified with the Time Span: counter fields
***'''Start and End at Absolute Time''': Voyager should wait until the specified Start: time and end the sequence at the specified End: time.
***'''Immediately Start and End at Absolute Time''': Start the sequence immediately and end it at the time specified in the counter fields
***'''Immediately Start and Finish With Astronomical Night''': Start the sequence immediately and finish it at Astronomical Night's end, offset +/- by the number of minutes set in the Offset: counter field
*'''Calculated Time Span''': Voyager will show how much time this sequence will take with the chosen Start/TimeSpan option if you choose Start and End at Absolute time. It is not possible to calculate this if you choose one of the "Immediately Start" options
**
**

 {{Note|Enter time in 24 hour format using local time - or the time zone on the computer running Voyager. That's the time that will be used in doing these calculations. Midnight is 00:00:00. 10 pm local time is 22:00:00. 3 AM is 03:00:00.}} {{Note|Note: If the Start: time is more than 12 hours in the future, Voyager will start the sequence, assuming that the start time has passed already in the current night. For example, if you specify a start time of 20:00:00 and it is now 20:15:00, Voyager will start the sequence}} {{Note|If the End time is more than 12 hours in the future, Voyager will assume the End time has already passed for the night and end the sequence. For example, if a sequence has a Start time of 20:00:00 and an End time of 21:00:00 and the current time is 22:00:00, Voyager will end the sequence}} {{Note|Times entered here will override any start or end times defined in the Sequence file. The times you define when you create the sequence are used for OnTheFly running of the Sequence, not for DragScript execution}} {{Note|The Start and End times are checked at the beginning of running a sequence and the sequence exits with status OK if the current time is outside the Start and End time window}}

**'''Options''': Check the boxes to select any of these options (Remember to scrool the panel to find more options in the configuration form):
***'''Overrides Target Coords J2000''': If checked, the RA and DEC coordinates are used instead of those in the sequence file. RA coordinates are in HH MM SS and DEC coordinates are HH MM SS.sss
***'''Overrides Target Name with this''': If checked, the name entered in the field will be used as the target name, which is part of the file name
***'''Force Dynamic Target Comet :''' if checked force the Sequence to use a Comet Dynamic Target type, you MUST select the Comet using the Comet Finder button near the check. If you check the flag and do not select a Comet the Sequence will generate an Error at starting. Target Name and Target key will be populated after the search and the overrides target name will be used with the name of the Dynamic Target. You can for sure change it.
***'''Force Dynamic Target Asteroid :''' if checked force the Sequence to use an Asteroid Dynamic Target type, you MUST select the Asteroid using the Asteroid Finder button near the check. If you check the flag and do not select an Asteroid the Sequence will generate an Error at starting. Target Name and Target key will be populated after the search and the overrides target name will be used with the name of the Dynamic Target. You can for sure change it.
***'''Override Dynamic Target Pointing Type :''' if checked and only if you are using a Dynamic Target (comet or asteroid) Voyager allow you to select when calculating the RA/DEC coordinates od the Dynamic Target. Default for a Dynamic Target is the Calculate RA/DEC only at Sequence Begin
****'''Calculate RA/DEC Only at Sequence Begin :''' Voyager will calculate the RA/DEC of the Dynamic Target only whe the Sequence action will start and will use this RA/DEC for all duration of the Sequence action. If the Sequence will be restarted anothe day or some hours after or generally will be restarted VOyager will calculate again the RA/DEC coordinates. But not in the same Sequence run.
****'''Calculate RA/DEC at Each Precise Goto :''' Voyager will calculate the RA/DEC of the Dynamic Target at each precise pointing goto inside the Sequence Run included at the begin of Sequence
****'''Calculate RA/DEC Every X Seconds :''' Voyager will calculate the RA/DEC of the Dynamic Target at the beginning of the Sequence and each X seconds like edited in the dedicated field. if the X interval is expired and Voyager is in exposure camera mode, will wait the end of exposure to calculate the new coordinates. A realign goto will not be requested if the next flag is not checked.
*****'''And Realign Target :''' if checked Voyager will force a realign with a Precise pointing to the new RA/DEC of the Dynamic Target
*****'''Without Using Plate Solving :''' if checked Voyager will avoid the precise pointing with plate solving for the realign and will use a simple goto without solving
***'''Override Angle Rotation of Target with PA of°:''' if checked , if in the sequence the rotator is managed, this flag force the Rotation Angle to the value selected. The other rotator settings in sequence will not be changed.
***'''Finish Running Exposure in case of elapsed time for Sequence Execution''': If checked, an exposure in progress will be allowed to finish if it starts before the sequence end time but finishes after the sequence end time
***'''Override Lower Altitude value under which Exit from Sequence''': If checked, if the sequence target sets below the altitude given here, the sequence will end. This value will override the minimum altitude value chosen in the sequence file
***'''Override Higher Altitude value above which Exit from Sequence''': If checked, if the sequence target rises above the altitude given here, the sequence will end. This value will override the maximum altitude value chosen in the sequence file
***'''Override Lower HourAngle value under which Exit from Sequence:''' If checked, if the sequence target HourAngle are lower the value given here, the sequence will end. This value will override the Lower HourAngle value chosen in the sequence file
***'''Override Higher HourAngle value over which Exit from Sequence:''' If checked, if the sequence target HourAngle are higher the value given here, the sequence will end. This value will override the Higher HourAngle value chosen in the sequence file
***'''Override Camera Cooling Temperature with Decimal Variable:''' if checked for colling temperature will be used the value inside the decimal variable selected in the drop-box combo box control
***'''Override Lower Azimuth value under which Exit from Sequence:''' If checked, if the sequence target Azimuth are lower the value given here, the sequence will end. This value will override the Lower Azimuth value chosen in the sequence file
***'''Override Higher Azimuth value over which Exit from Sequence:''' If checked, if the sequence target Azimuth are higher the value given here, the sequence will end. This value will override the Higher Azimuth value chosen in the sequence file
***'''Use External Interval Angle:''' if each the azimuth constraints will be cheched you can decide with this flag to use external angle instead of internal angle between before and after azimuth. Example if you choose 70° before and 150° after with out external flag this mean sequence run if angle is between 70 and 150°, if you chec it and invert to external sequence will be terminate if azimuth is between 70 and 150°
**'''Default''': Click this button to populate this window with the default options
**'''OK''': Click to save your changes and close the window
**'''Cancel''': Click to discard your changes and close the window 
**'''Override FILE PATTERN:''' flag this chheckbox to activate sub foldering and file naming with File Pattern method, insert in the big text field near the flag the string to override of the file pattern to use instead of the one configured in the File Pattern Manager. This will affect only the actual sequence and do not change the main File Patterm Manager configuration. This is for example mandatory in case of join of the OpenSkyGems network and sharing of the observatory setup.
*'''Research & Survey''': Run a [[Research Survey|Research & Survey]] sequence with options

[[File:Research-survey-dragscript.png]]

*'''Configuration Panel''':
**Click the folder icon [[File:Folder-icon.png]] to select the Research & Survey sequence file to run. Create your sequence files in Voyager's [[Research Survey|Research & Survey workspace]]
**TYPO: Star/TimeSpan should be Start/TimeSpan
**'''Start/TimeSpan''': Click one of the radio buttons to use that option to tell when to start and end the Research & Survey sequence. This is one way to have Voyager image this target until a specific time is reached, or an interval has elapsed. It is a good idea to specify an ending time here, or a minimum altitude in the Research & Survey sequence definition or the Options field below, so Voyager will not continue trying to take images after the object has set
***'''Immediately Start and Finish After Interval''': Start the sequence immediately and end it after the HH:MM:SS amount of time specified with the Time Span: counter fields
***'''Start and End at Absolute Time''': Voyager should wait until the specified Start: time and end the sequence at the specified End: time.
***'''Immediately Start and End at Absolute Time''': Start the sequence immediately and end it at the time specified in the counter fields
***'''Immediately Start and Finish With Astronomical Night''': Start the sequence immediately and finish it at Astronomical Night's end, offset +/- by the number of minutes set in the Offset: counter field
**'''Calculated Time Span''': Voyager will show how much time this sequence will take with the chosen Start/TimeSpan option if you choose Start and End at Absolute time. It is not possible to calculate this if you choose one of the "Immediately Start" options
*'''Options''':
**'''Finish Running Exposure in case of elapsed time for Sequence Execution''': If checked, an exposure in progress will be allowed to finish if it starts before the sequence end time but finishes after the sequence end time
**'''Default''': Click this button to populate this window with the default options
**'''OK''': Click to save your changes and close the window
**'''Cancel''': Click to discard your changes and close the window 

 {{Note|See the Important Notes above in the Sequence discussion to understand how Voyager treats the values in the time fields when they have already passed in tonight's session or if they are also specified in the Research & Survey sequence definition file}}

*'''Flat''': Run an Auto Flat sequence. [[Auto Flat|Configure the Auto Flat sequence files]] in the OnTheFly workspace

[[File:Flat-sequence-dragscript.png]]

*Click the folder icon [[File:Folder-icon.png]] and choose the Auto Flat sequence file to run. [[Auto Flat|Configure the Auto Flat sequence files]] in the OnTheFly workspace
*TYPO: Configuration dialog says "Good Night" but should be Auto Flat
*'''Default''': Click this button to populate this window with the default options (blanks out the Flat Sequence File field)
*'''OK''': Click to save your changes and close the window
*'''Cancel''': Click to discard your changes and close the window

 

*'''Good Night''': Run a series of one or more shutdown actions:

[[File:Dragscript-good-night.png]]

*'''CCD Filter Select''': Moves the filter wheel to the filter chosen from the drop-down box on the right
*'''Sync Warmup''': Send the CCD cooler a warmup command and wait until it finishes
*'''Async Warmup''': Send the CCD cooler a warmup command and continue execution without waiting for it to finish
*'''Parking''': Park the mount as specified in [[Mount Setup#Park.2FUnpark|Mount Setup]]

 

==Plate Solving==
Plate Solving actions perform a plate solving action as defined in the [[Plate Solve Setup|Plate Solving setup]] of the active profile:

[[File:Dragscript-plate-solving.png]]

 

*'''Plate Solving''' : Perform a plate solve action at the current scope location using the Plate Solve software defined in the [[Plate Solve Setup|Plate Solving setup]] of the active profile. ''Mount will not be synched''
*'''Plate Solving with Mount Sync:''' Perform a plate solve action at the current scope location using the Plate Solve software defined in the [[Plate Solve Setup|Plate Solving setup]] of the active profile. ''Send a Sync command to the mount unless you have chosen to not send a Sync command to your mount in [[Mount Setup#Management|Mount Setup]]. You may lost pointing model if you have one and your driver not allow additional and external sync''

==Blind Solving==
Blind Solving actions perform a plate solving action as defined in the [[Plate Solve Setup|Plate Solving setup]] of the active profile:

[[File:BlindSolveBlocks.png]]

 

*'''Blind Solving with Mount Sync:''' Perform a blind solve action at the current scope location using the Plate Solve software defined in the [[Plate Solve Setup|Plate Solving setup]] of the active profile. ''Send a Sync command to the mount unless you have chosen to not send a Sync command to your mount in [[Mount Setup#Management|Mount Setup]]. You may lost pointing model if you have one and your driver not allow additional and external sync''

 

==WEB Solving==
Plate Solving actions perform a plate solving action as defined in the [[Plate Solve Setup|Plate Solving setup]] of the active profile:

[[File:WebSolvingBlocks.png]]

 

*'''Web Solving with''' '''Sync''': Perform a web blind solve action at the current scope location using the nova.astrometry.net site. An active Internet connection is required. Send a Sync command to the mount unless you have chosen to not send a Sync command to your mount in [[Mount Setup#Management|Mount Setup]]
**[[File:Web-solving-with-sync.png]]
***'''Timeout''': Specify the number of minutes Voyager should wait after initiating the Web Solve before timing out. Use an IF TIMEOUT decision action to define what to do if the web solve times out

==Guiding==
Guiding actions send commands to the guide software:

[[File:Dragscript-guiding-dithering.png]]

*'''Calibrate Guide''': Command the guide software to perform a calibration action. It is recommended to include a Calibrate Guide action at the start of your sequence unless you are sure that your guider is calibrated from a previous session. Double click to bring up the configuration window:

[[File:Dragscript-calibrate-guide.png]]

*'''Time''': Exposure time for Calibration exposures by the guiding software
*'''Binning''': Binning level for Calibration exposures by the guiding software
*'''Use RoboGuide Star Selection''': If selected, use Voyager's RoboGuide process to choose a guide star for the Calibration action. This is mandatory at this time since some guiding software cannot select a guide star.
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Acquiring Guide Star''': Commands the guiding software to select a guide star. Double click to bring up the configuration window:

[[File:Dragscript-acquire-guide-star.png]]

*'''Time''': Exposure time for guide star acquisition exposures by the guiding software
*'''Binning''': Binning level for guide star acquisition exposures by the guiding software
*'''Use RoboGuide Star Selection''': If selected, use Voyager's RoboGuide process to choose a guide star. This is mandatory at this time since some guiding software cannot select a guide star.
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''Guide Start''': Commands the guiding software to begin guiding. Double click to bring up the configuration window:

[[File:Dragscript-guide-start.png]]

*'''Time''': Exposure time for guiding exposures by the guiding software
*'''Binning''': Binning level for guiding exposures by the guiding software
*'''Use RoboGuide Star Selection''': If selected, use Voyager's RoboGuide process to choose a guide star. This is mandatory at this time since some guiding software cannot select a guide star.
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Guide Stop''': Command the guiding software to stop guiding

 

*'''Guide Dithering''': Command the guiding software to perform a dithering action. Dithering is used to move the mount a tiny random amount in a random direction - usually only a couple of pixels. This prevents hot or cold pixels in your sensor from showing up in the same position in all of your images, making it easier to remove hot or cold pixels when stacking your images. Double click to bring up the configuration window:

[[File:Dragscript-guide-dithering.png]]

*'''Max Pixel''': Specify the maximum number of pixels that a dithering operation can move the mount
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 

*'''Unguided Dithering''': Perform a dithering action directly, vs. Guide Dithering which sends a dithering command to the guide software. Dithering is used to move the mount a tiny random amount in a random direction - usually only a couple of pixels. This prevents hot or cold pixels in your sensor from showing up in the same position in all of your images, making it easier to remove hot or cold pixels when stacking your images.

[[File:Unguided-dither-3.png]]

*'''Max Pixel''': Specify the maximum number of pixels that a dithering operation can move the mount
*'''From Actual Position''': This is the safest and default choice - it sends a command to move the mount up to the specified number of pixels from the current position. This should be a small movement, as the recommended number of pixels to dither is 3
*'''From Last Goto Action Position''': Send a command to move the mount a random number of pixels up to '''Max Pixel''' in a random direction relative to the position of the last Goto action. This should only be used following a successful Goto action in your DragScript. You can damage your mount if you use this without a successful Goto action preceding it.
*'''From Last Precision Pointing Action Position''': Send a command to move the mount a random number of pixels up to '''Max Pixel''' in a random direction relative to the position of the last Precision Pointing action. This should only be used following a successful Precision Pointing action in your DragScript. You can damage your mount if you use this without a successful Precision Pointing action preceding it.
*'''Use Actual Position on Empty/Fail condition''': If checked, if the position reported by the Last Goto Action or Last Precision Pointing Action is empty, or if the Last Goto Action or Last Precision Pointing Action ended with an error, use the Actual Position of the mount as the starting point for dithering. In other words, don't attempt to dither based on the Last Goto action position or the Last Precision Pointing action position if either of those positions is empty, as this would send a command to the mount that could cause a pier crash and/or damage to your equipment. '''Highly recommend leaving this checked.'''
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 
==Mount==
Mount actions send commands to the mount defined in the [[Mount Setup|Mount setup]] of the active profile:

[[File:Dragscript-mount.png]]

*'''Stop Tracking''': Command the mount to stop tracking
*'''Start Tracking''': Command the mount to start tracking
*'''Parking''': Command the mount to slew to the Park position
*'''Unparking''': Command the mount to Unpark
*'''Sync on Park''': Command the mount to save the current position as the Park position
*'''Homing''': Command the mount to move to the Home position (depends on the driver if the command will work, not all drivers have this command implemented !)
*'''Goto RA/DEC''': Command the mount to move to the specified RA and DEC coordinates (J2000)

[[File:Dragscript-gotoradec.png]]

*'''RA J2000''': Enter the RA coordinates in HH MM SS or HH MM SS.sss
*'''DEC J2000''': Enter the RA coordinates in DD MM SS or DD MM SS.sss
*'''Default''': Use the default settings: clears the RA and DEC fields
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Goto ALT/AZ''': Command the mount to move to the specified Altitude and Azimuth coordinates

[[File:Goto-altaz.png]]

*'''ALT:''' Enter the Altitude coordinates in DD MM SS or DD MM SS.sss
*'''AZ''': Enter the Azimuth coordinates in DD MM SS or DD MM SS.sss
*'''Force Use of Normal RA/DEC Slew With Conversion''': If checked, convert the requested ALT and AZ values to RA and DEC values and send a goto RA/DEC command to the mount
*'''Default''': Use the default settings: clears the AZ and ALT fields
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Goto Near Zenith''': Command the mount to move to a point close to the current Zenith (directly overhead). 
{{Note|Goto Near Zenith followed by a Blind Solving with Sync action is a good way to initialize your mount's pointing model at the start of a session. It is only a single point, but if your mount is accurately polar aligned, doing this before the first Precise Pointing operation may helps the Precise Pointing to succeed}}

*

*'''Goto By Name''': Command the mount to move to an object by name with an optional RA and DEC offset. This action requires Voyager to be connected to the [[Planetarium Setup|Planetarium software]] defined in the current profile. The Object Name must match a name that can be successfully searched in the connected Planetarium software.

[[File:Dragscript-gotoname.png]]

*'''Object Name''': Name of the object to goto. Must be a name that can be successfully searched in the connected Planetarium software
*'''Offset RA (optional)''': An optional +/- offset in HH MM SS or HH MM SS.sss to be added or subtracted from the RA coordinates returned by the Planetarium software
*'''Offset DEC (optional)''': An optional +/- offset in DD MM SS or DD MM SS.sss to be added or subtracted from the DEC coordinates returned by the Planetarium software
*'''Goto Dynamic Target''': Command the mount to move to a RA/DEC of a Dynamic Target calculating with RoboOrbits the coordinates at now [[File:Immaginedd.png]]
**'''Comet :''' open the Comet Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
**'''Asteroid :''' open the Asteroid Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
**'''Planet:''' open the Planet Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
**'''Object Name :''' Read-only name of the Dynamic Target, coming from the search
**'''Object Key :''' Read-only key (code/number) of the Dynamic Target, coming from the search
**'''Object Dynamic Type :''' Read-only type of the Dynamic Target, coming from the search
**'''Offset RA (optional)''': An optional +/- offset in HH MM SS or HH MM SS.sss to be added or subtracted from the RA coordinates calculated
**'''Offset DEC (optional)''': An optional +/- offset in DD MM SS or DD MM SS.sss to be added or subtracted from the DEC coordinates calculated

*'''Goto By Offset''': Command the mount to move from actual position by an RA and DEC offset.

[[File:Immagineerferf.png]]

*'''Offset RA''' : +/- offset in HH MM SS or HH MM SS.sss to be added or subtracted from the actual RA coordinates
*'''Offset DEC''' : +/- offset in DD MM SS or DD MM SS.sss to be added or subtracted from the actual DEC coordinates

 

*'''Precise Pointing''': Command the mount to perform a [[Plate Solve Setup#Precision Pointing|precise pointing]] operation to the specified RA/DEC coordinates - slew to the object, plate solve to get actual coordinates, re-slew to correct pointing error:

[[File:Dragscript-precisepointing.png]]

*'''RA J2000''': Enter the RA coordinates in HH MM SS or HH MM SS.sss
*'''DEC J2000''': Enter the DEC coordinates in DD MM SS or DD MM SS.sss
*'''Max Error using Multiple of Profile Error by''': If selected, multiply the maximum allowed pointing error by the number specified in the counter field. E.g., if the [[Mount Setup#Management|Precision Pointing Max Allowed Error]] specified in Mount Setup is 50 arc-seconds, a value of 2 in the counter field here would change the maximum pointing error to 100 arc-seconds. Precise pointing returns an OK (success) result when the error is less than the Max Error.
*'''Max Error is''': If selected, use the value specified in the counter field as the maximum pointing error in arc-seconds. Precise pointing returns an OK (success) result when the error is less than the Max Error.
*'''RoboClip:''' open RoboClip manager windowd and allow to select a target,
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Precise Pointing by Name''': Command the mount to perform a [[Plate Solve Setup#Precision Pointing|precise pointing]] operation to the specified named object - slew to the object, plate solve to get actual coordinates, re-slew to correct pointing error. This action requires Voyager to be connected to the [[Planetarium Setup|Planetarium software]] defined in the current profile. The Object Name must match a name that can be successfully searched in the connected Planetarium software.

*[[File:Dragscript-precisepointing-name.png]]
**'''Object Name''': Name of the object to goto. Must be a name that can be successfully searched in the connected Planetarium software
**'''Offset RA (optional)''': An optional +/- offset in HH MM SS or HH MM SS.sss to be added or subtracted from the RA coordinates returned by the Planetarium software
**'''Offset DEC (optional)''': An optional +/- offset in DD MM SS or DD MM SS.sss to be added or subtracted from the DEC coordinates returned by the Planetarium software
**'''Max Error using Multiple of Profile Error by''': If selected, multiply the maximum allowed pointing error by the number specified in the counter field. E.g., if the [[Mount Setup#Management|Precision Pointing Max Allowed Error]] specified in Mount Setup is 50 arc-seconds, a value of 2 in the counter field here would change the maximum pointing error to 100 arc-seconds. Precise pointing returns an OK (success) result when the error is less than the Max Error.
**'''Max Error is''': If selected, use the value specified in the counter field as the maximum pointing error in arc-seconds. Precise pointing returns an OK (success) result when the error is less than the Max Error.
**'''Default''': Use the default settings
**'''OK''': Save changes and close the window
**'''Cancel''': Discard changes and close the window

*'''Precise Pointing Dynamic Target''': Command the mount to perform a [[Plate Solve Setup#Precision Pointing|precise pointing]] operation to the specified Dynamic Target. RA/DEC will be calculated in real-tim using the RoboOrbits, more info [[Introduction to RoboOrbits|here]].

*[[File:Immaginenn.png]]
**'''Comet :''' open the Comet Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
**'''Asteroid :''' open the Asteroid Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
**'''Object Name :''' Read-only name of the Dynamic Target, coming from the search
**'''Object Key :''' Read-only key (code/number) of the Dynamic Target, coming from the search
**'''Object Dynamic Type :''' Read-only type of the Dynamic Target, coming from the search
**'''Offset RA (optional)''': An optional +/- offset in HH MM SS or HH MM SS.sss to be added or subtracted from the RA coordinates returned by the Planetarium software
**'''Offset DEC (optional)''': An optional +/- offset in DD MM SS or DD MM SS.sss to be added or subtracted from the DEC coordinates returned by the Planetarium software
**'''Max Error using Multiple of Profile Error by''': If selected, multiply the maximum allowed pointing error by the number specified in the counter field. E.g., if the [[Mount Setup#Management|Precision Pointing Max Allowed Error]] specified in Mount Setup is 50 arc-seconds, a value of 2 in the counter field here would change the maximum pointing error to 100 arc-seconds. Precise pointing returns an OK (success) result when the error is less than the Max Error.
**'''Max Error is''': If selected, use the value specified in the counter field as the maximum pointing error in arc-seconds. Precise pointing returns an OK (success) result when the error is less than the Max Error.
**'''Default''': Use the default settings
**'''OK''': Save changes and close the window
**'''Cancel''': Discard changes and close the window

 

*'''Precise Pointing Mount & Rotator''': Command the mount to perform a [[Plate Solve Setup#Precision Pointing|precise pointing]] operation to the specified named object - slew to the object, plate solve to get actual coordinates, re-slew to correct pointing error, rotating the rotator and align to the requested PA within the specified tollerance.

*[[File:PrecisePointingMountRotator.png]]
**'''RA J2000''': Enter the RA coordinates in HH MM SS or HH MM SS.sss
**'''DEC J2000''': Enter the DEC coordinates in DD MM SS or DD MM SS.sss
**'''Max Error using Multiple of Profile Error by''': If selected, multiply the maximum allowed pointing error by the number specified in the counter field. E.g., if the [[Mount Setup#Management|Precision Pointing Max Allowed Error]] specified in Mount Setup is 50 arc-seconds, a value of 2 in the counter field here would change the maximum pointing error to 100 arc-seconds. Precise pointing returns an OK (success) result when the error is less than the Max Error.
**'''Max Error is''': If selected, use the value specified in the counter field as the maximum pointing error in arc-seconds. Precise pointing returns an OK (success) result when the error is less than the Max Error.
** '''Rotation Angle:''' an arbitrary angle that can be a Rotator PA or Sky PA, depends on following setting.
** '''Rotation Type:''' define if the rotation angle is the rotator angle (rotator PA) reported from the driver (and with offset if asked to Voyager in Sync) or the Sky angle (Sky PA) chosen with web dashboard VirtualFOV or planetarium or another system. If you select Sky PA Voyager will use the Plate solve PA result to rotate the rotator to the right angle. If you select the Rotator PA Voyager will just rotating rotator using drive angle at desidered value, no correction using the plate solved PA will be done
** '''PA Tollerance +/-:''' if the PA of rotator is inside the interval given the position will be declared ok and rotator will not be rotate.
** '''Rotator & Meridian Flip:''' "Mantain the Same Image Orientation After the Meridian" if checked force Voyager to shot the target with same orientation in the images taken before anf after meridian. In this case if you have chosen Rotator PA like Rotation type the rotator will be flipped if the mount is after the meridian, if you chosen Sky PA the PA will retained also after the meridian triggering a rotator flip.Use this flag is useful also to use always the same guide star in case of use of OAG or system with high focal lenght.
**'''RoboClip:''' open RoboClip manager windowd and allow to select a target, with RA and DEC will be also acquired the PA
***'''Default''': Use the default settings
***'''OK''': Save changes and close the window
***'''Cancel''': Discard changes and close the window

 

*'''Stop Tracking (Only FS2 Mount)''': Command an FS2 mount to stop tracking
*'''Start Tracking (Only FS2 Mount)''': Command an FS2 mount to start tracking
*'''FS2 Meridian Flip WEST''': Command an FS2 mount to perform a meridian flip to the West
*'''FS2 Meridian Flip EAST''': Command an FS2 mount to perform a meridian flip to the East
*'''Connect Maxim Telescope''': Connect the Telescope/Mount defined in Maxim DL configuration (you must have camera configured in Voyager like Maxim DL)
*'''Disconnect Maxim Telescope''': Disconnect the Telescope/Mount defined in Maxim DL configuration (you must have camera configured in Voyager like Maxim DL) {{Note|The FS2 Mount commands should only be used if your mount is controlled by the Astro Electronic FS2 motor control system. Using these commands with other mounts may fail and cause damage to the mount and other equipment}}

==Dome==
Dome actions send commands to the dome defined in the [[Dome Setup]] area of the active profile:

[[File:Dragscript-dome-217d.jpg]]

*'''Open Shutter''': Command the dome's shutter or the observatory's roll-off roof to open
*'''Close Shutter''': Command the dome's shutter or the observatory's roll-off roof to close
*'''Dome Slave ON''': Send a command to the dome software to "Slave" to the mount. The dome's azimuth position will track with the mount's movements in azimuth
*'''Dome Slave OFF''': Send a command to the dome software to turn off "Slave" to the mount. The dome's azimuth position will stop tracking the mount's azimuth movements
*'''Dome Goto Azimuth''': Command the Dome to rotate to the specified Azimuth

[[File:Dragscript-dome-az.png]]

*'''Azimuth''': Azimuth position the mount should move to in degrees
*'''Cancel''': Discard changes and close the window
*'''OK''': Save changes and close the window

 

*'''Dome Find Home''': Command the dome to find its Home position. If your dome supports the Find Home command, the dome moves to a known position
*'''Dome Park''': Send a Park command to the dome.
*'''Dome Unpark:''' Send an Unpark command to the dome

 
==Camera==
Camera actions can control the camera's cooling system and take exposures

[[File:Dragscript-camera.png]]

*'''Cool Down''': Command the camera's cooling system to cool down to a desired temperature:

[[File:Dragscript-cooldown.png]]

*'''Final Temperature''': Desired sensor temperature in °C
*'''Use Variable:''' check this flag if you want to set the cooling temperature reading the value inside the variable selectable in the drop-down combo instead to use a fixed value
*'''Async Cooling''': If checked, command the cooling system to go to the Final Temperature and do not wait for the cooling system to report that it has reached the desired temperature
*'''Use CCD Firmware Cooldown''': If selected, let the CCD's cooling system manage the speed of the cooldown process
*'''Use Voyager Ramp Mode Cooldown''': If selected, let Voyager's cooldown process manage the speed of the cooldown process. Voyager's process is defined in [[Camera Setup#Cooling System|Camera Setup]]
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Warmup''': Command the camera's cooling system to warmup

[[File:Dragscript-warmup.png]]

*'''Async Cooling''': If checked, command the camera's cooling system to warmup and do not wait for the warmup operation to finish
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Expose''': Take an exposure

[[File:Dragscript-expose-216d.jpg]]

*'''Exposure Type''': Choose Light, Bias, Dark or Flat from the drop-down list
*'''Filter Index''': Choose the filter for the exposure from the drop-down list
*'''Expose''': Enter the exposure length in seconds in the counter field
*'''Use Variable:''' select if you want to get the exposure time from the decimal variable selected in the near list control
*'''Binning''': Select the binning level for the exposure from the counter field
*'''SubFrame''': Select the frame size from the drop-down list: Full Frame, 1/2, 1/4, 1/8, 1/16 or CUSTOM. If you select CUSTOM subframe size, enter the desired subframe size in percent in the counter field that appears
*'''Gain:''' Set the camera's Gain value to the number in the spinner control. Works only if you are using the ASI Camera native driver.
*'''Offset:''' Set the camera's Offset value to the number in the spinner control. Works only if you are using the ASI Camera native driver.
*'''File Directory''': Click the folder icon to select the folder where Voyager should save the image resulting from this exposure
*'''File Name''': Enter the file name to use when saving the image resulting from this exposure
*'''Make Unique File Name''': If checked, add a suffix to the file name if needed to avoid overwriting an existing file
*'''FIT Object Name''': The name to use to populate the OBJECT field in the FITS header
*'''FIT Airmass calculation''': Compute the current airmass value and add to the FITS file header. Airmass is the amount of atmosphere you are imaging through. It is one when imaging directly overhead, and increases as you image closer to the horizon.
*'''Focuser Position Add to FIT Name:''' add the focuser position to the FIT name, only if you are using RoboFire like Autofocus control in Voyager
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

* '''TheSkyX/64 Camera FW Reconnect''': Reconnect camera and filterwheel if the control used for camera in Voyager is TheSkyX or TheSky64

{{Note|Dragscript editor doesn’t have access to profile configuration, for this reason you dont find setting about readout mode and speed in exposure block. Exposure block use auto mode of readout mode and default speed mode. This mean chooses are based on shot type and binning. It retrieve automatically the correct values you set up on Voyager camera setting tab.}} 

{{Note|Filter labels are shown in this dialog if the DragScript editor is opened from Voyager and filter labels are defined in the current profile. Otherwise only filter indexes are shown. The first filter is index zero (0)}}

{{Note|If you check the use variable flag the exposure time used for the exposure will be added to the name of FIT file}} 

==AutoFocus==
These DragScript commands perform Voyager's autofocus operations:

[[File:Dragscript-autofocus.png]]

*'''AutoFocus with RoboStar''': perform an autofocus operation using Voyager's RoboStar method to choose the focus star:

[[File:Dragscript-autofocus-robostar.png]]

*'''Monochromatic Camera''': Select if a monochrome camera is connected. Select a filter to use for the autofocus operation from the drop-down list
*'''DSLR/Color Camera''': Select if a DSLR or Color (OSC) camera is connected
*'''No Filter''': Select if a monochrome camera is connected without filters
*'''Use Low Precision Pointing''': If checked, Voyager's RoboStar operation will slew to the focus star with a more relaxed precision pointing operation. Specify the multiple for the maximum allowed precision pointing error in the counter field. E.g., if the precision pointing max allowed error configured in [[Mount Setup#Management|Mount Setup]] is 50 arc-seconds, a "Multiple Max Allowed Error by" setting of two would relax the maximum allowed pointing error to 100 arc-seconds
*'''AutoFocus OnPlace''': Perform the autofocus operation at the current scope location. Do not use RoboStar to select a focus star
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Simple Goto RoboStar Star''': Perform a simple goto operation to move the mount to the focus star selected by RoboStar:

[[File:DSSimpleGotoRoboStar.png]]

*'''Monochromatic Camera''': Select if a monochrome camera is connected. Select a filter to use for the precise pointing operation from the drop-down list
*'''DSLR/Color Camera''': Select if a DSLR or Color (OSC) camera is connected
*'''No Filter''': Select if a monochrome camera is connected without filters
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Precise Pointing RoboStar Star''': Perform a precise pointing operation to move the mount to the focus star selected by RoboStar:

[[File:Dragscript-precisepointing-robostar.png]]

*'''Monochromatic Camera''': Select if a monochrome camera is connected. Select a filter to use for the precise pointing operation from the drop-down list
*'''DSLR/Color Camera''': Select if a DSLR or Color (OSC) camera is connected
*'''No Filter''': Select if a monochrome camera is connected without filters
*'''Use Low Precision Pointing''': If checked, Voyager will slew to the focus star with a more relaxed precision pointing operation. Specify the multiple for the maximum allowed precision pointing error in the counter field. E.g., if the precision pointing max allowed error configured in [[Mount Setup#Management|Mount Setup]] is 50 arc-seconds, a "Multiple Max Allowed Error by" setting of two would relax the maximum allowed pointing error to 100 arc-seconds
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''RoboFire Focuser Move To''': Move the focuser to a specified absolute or relative position:

[[File:Dragscript-robomove.png]]

*'''Position''': Desired focuser position in steps
*'''Mode''': Choose absolute or relative
**'''Absolute''': Command the focuser to move to the specified position. Your focuser must support absolute positioning.
**'''Relative''': Command the focuser to move in or out by the specified number of steps. Negative numbers move the focuser IN and positive move it out, unless you specify "Reverse Focuser Direction" in [[AutoFocus Setup#RoboFire Configuration Center|Autofocus Setup]]
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''RoboFire Focuser Move From Variable''': Move the focuser to an absolute or relative position stored in a variable:

[[File:Dragscript-robomove-variable.png]]

*'''Get Position From Variable''': select the variable that contains the position
*'''Mode''': Choose absolute or relative
**'''Absolute''': Command the focuser to move to the specified position. Your focuser must support absolute positioning.
**'''Relative''': Command the focuser to move in or out by the specified number of steps. Negative numbers move the focuser IN and positive move it out, unless you specify "Reverse Focuser Direction" in [[AutoFocus Setup#RoboFire Configuration Center|Autofocus Setup]]
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

{{Note|Be sure to select the right Variable and that the variable is valorized before using this block or you can lost focus. Be sure also to have inserted limits on RoboFIre configuration to avoid damage to your focuser.}}

*'''AutoFocus with RoboFire LocalField''': Perform Voyager's LocalField (multiple star) autofocus routine

[[File:Dragscript-localfield.png]]

*'''Monochromatic Camera''': Select if a monochrome camera is connected. Select a filter to use for the precise pointing operation from the drop-down list
*'''DSLR/Color Camera''': Select if a DSLR or Color (OSC) camera is connected
*'''No Filter''': Select if a monochrome camera is connected without filters
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 
==Rotator==
Rotator actions can move the rotator to a specified Position Angle or flip the rotator 180 degrees:

[[File:Dragscript-rotator.png]]

 

*'''Rotator Move To''': Move the rotator to the specified position angle in degree
**[[File:Dragscript-rotatormove.png]]
***'''PA''': Move the rotator to this Position Angle in degrees
***'''OK''': Save changes and close the window
***'''Cancel''': Discard changes and close the window

*
*'''Rotator 180° Flip''': Move the rotator to a position 180 degrees opposite its current position
*'''Rotator Sync''': Synchronize the mechanical position to the submitted position (create an offset to the mechanical position)
**[[File:RotatorSyncBlockConf.png]]
***'''Rotator Sync To:''' with this option Voyager will sync the rotator PA to the PA in the next field
***'''PA:''' Position Angle to use for sync
***'''Use Variable:''' get PA value from the selected variable
***'''Reset Rotator Sync:''' with this option Voyager will reset the Sync (remove the offset applied to the mechanical position of rotator)
***'''Default:''' reset all parameters in the form to the default values
***'''Cancel:''' exit from the configuration form without saving anything
***'''OK:''' accept the inserted value and store data

* '''Precise Rotate SkyPA''': Move the rotator to the specified SkyPA position
** [[File:PRSKYPADS.png]]
*** '''Rotation Angle''': SKY PA in degree to use for positioning the rotator
*** '''PA Tollerance +/-''': max allowed difference in degree between solved PA and requested PA
*** '''Save Final Rotator PA to this DragScript Decimal:''' if flagged save the Rotator PA degree of pointing (if positioned ok) to the decimal variable selected in the combobox
*** '''OK''': Save changes and close the window
*** '''Cancel''': Discard changes and close the window

==Flat Device==
Flat Device commands can open and close the flat device cover:

[[File:Dragscript-flat-device.jpg]]

*'''Open Flat Device Cover''': Command the flat device to open
*'''Close Flat Device Cover''': Command the flat device to close
*'''Switch On Light Flat Device''': Turn the light on for the specified Flat Device

[[File:Dragscript-switch-on-flat-device.jpg]]

*'''Device ID''': Choose the Flat Device number to control with this command. See [[Flat Device Setup]] for more information on flat devices.

 

*'''Switch Off Light Flat Device''': Turn the light off for the specified Flat Device

[[File:Dragscript-switch-off-flat-device.jpg]]

*'''Device ID''': Choose the Flat Device number to control with this command. See [[Flat Device Setup]] for more information on flat devices.

 

*'''Select Brightness Flat Device''': Set the brightness level for the specified Flat Device.

[[File:Dragscript-select-brightness.jpg]]

*'''Device ID''': Choose the Flat Device number to control with this command. See [[Flat Device Setup]] for more information on flat devices.
*'''Brightness''': Brightness level for the specified Flat Device. 
{{Note|If you have a flat device that can open and close, don't forget to issue an Open Flat Device command in your DragScript before taking exposures including plate solving and autofocus!}}

==Script==
The Script action can run an external script or program:

[[File:Dragscript-script-external.png]]

[[File:External-script-1.png]]

*'''File Program/Script''': Click the folder icon to select the program or script to run
*'''Arguments''': Command line arguments to be passed to the program or script when invoking it
* '''JOLLY Strings''':there are some special strings called jolly that can be used in argument line will be replaced with some data from Voyager environment or DragScript variables
** '''Internal IPs:''' ##INTERNAL-IP## write a list of all internal IPs avalaible in the system
** '''External IP''': ##EXTERNAL-IP## write a list of external IP assigned to your PC(router) if you have internet connection up
** '''NOW''': ##NOW## write the actual date and time
** '''Mount Altitude''': ##MOUNT-ALT## write the actual altitude of Telescope Mount if connected
** '''Mount Azimuth''': ##MOUNT-AZ## write the actual azimuth of Telescope Mount if connected
** '''Variable''': ##VAR-name## where you must replace the ''name'' with the real name of your variable (case sensitive) , write the actual value of you variable (decimal, string or counter)
*'''Wait For Program/Script''': If checked, wait for the program or script to return before continuing (synchronous execution)
*'''On Timeout Kill Program/Script''': If checked, and the "Wait for Program/Script" option is checked, and the "Wait / Timeout" time period has elapsed, terminate the external program or script
*'''Return OK to DragScript Engine only if Script return this''': If checked, the script or program must return the value specified in the text field in order for this action to be considered a success and return OK
*'''Save External Script output to this DragScript String''': If checked, store the value that the external script or program returns in STDOUT to the DragScript string variable chosen from the drop-down list
*'''Save External Script output to this DragScript Decimal''': If checked, store the value that the external script or program returns in STDOUT to the DragScript decimal number variable chosen from the drop-down list
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 
{{Note|Voyager will only terminate the specified program or script when the timeout period expires. If the called program calls other programs, they will not be terminated by Voyager}}{{Note|Use of Jolly String and DragScript Variables in arguments line is reserved to who have purchased and activated the Voyager Developer Plugin}}
{{Note|If the value returned from STDOUT is stored in a DragScript decimal number, be sure that the number returned uses a period as the decimal point separator}}

'''Example of Use'''

In this example, we call a Python script located in the directory d:\VScheduler\Scheduler.py, and wait up to 10 seconds for the script to complete.

The Python script writes a value to STDOUT with this code:<blockquote>import sys</blockquote><blockquote>sys.stdout.write('RUN')</blockquote><blockquote>sys.stdout.flush()</blockquote>We store that value in the SchedulerResult DragScript string variable. We can then make decisions in the DragScript using the DO IF STRING VALUE statement.

[[File:Script-scheduler-example.jpg]]

 
==Timing==
Timing actions inform DragScript to wait before performing an action. You can wait for a time interval, an absolute time to be reached, astronomical night with an offset, or for an object to reach a desired altitude:
 [[File:Dragscript-timing-211a.jpg]]

*'''Wait Time''': Wait for a specified time to arrive or to elapse

[[File:Dragscript-waittime.png]]

*'''Interval/Time''': Enter a time in HH MM SS.
*'''Wait Type''': Chose Absolute or Relative
**'''Absolute''': Wait until this absolute time is reached. If the time specified is more than 12 hours in the future, Voyager will assume this time has passed and will not wait. For example, if the specified time is 20:00:00 and this action is executed at 20:15:00, Voyager will not wait because that would cause a wait until tomorrow night, which is probably not what you intended
**'''Relative''': Wait for this amount of time to elapse
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 

 

*'''Wait Altitude''': Wait until the object at the given RA and DEC coordinates reaches the specified altitude, either rising or setting:

[[File:Dragscript-wait-altitude.png]]

*'''RA Target J2000''': RA coordinates of the object you want to reach the Reference Altitude in HH MM SS or HH MM SS.sss
*'''DEC Target J2000''': DEC coordinates of the object you want to reach the Reference Altitude in DD MM SS or DD MM SS.sss
*'''Reference Altitude''': Altitude to reach in degrees
*'''Exit Wait if Actual Altitude GREATER than or EQUAL (>=) to reference''': Wait until the target rises above the reference altitude
*'''Exit Wait if Actual Altitude LOWER than or EQUAL (>=) to reference''': Wait until the target sets below the reference altitude
*'''Wait Altitude until absolute time''': The Wait Altitude operation will terminate when this time is reached, whether or not the target has reached the reference altitude. This is usually done to end the wait with morning light
*'''Activate Antiglitch Altitude Reading System:''' set the flag if you want to activate an AntiGlitch system to avoid glitchy readings of values from mount drivers that have undeclared bugs (3 continuous readings are done to get the OK). Sometime happens in buggy drivers a single reading is damaged and trigger the OK to wait altitude status. I fyou have this problem activate the flag but report the problem to the mount driver developer.
* '''RoboClip:''' load RA and DEC from RoboClip catalog
* '''Coords From Sequence:''' load RA and DEC from a sequence file
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''Wait Altitude Dynamic Target''': Wait until the object at the calculated RA and DEC coordinates of a Dynamic Target reaches the specified altitude, either rising or setting:

[[File:Immagineddd.png]]

*'''Comet :''' open the Comet Finder in RoboOrbits, see more [https://wiki.starkeeper.it/index.php/RoboOrbits_Finders here]
*'''Asteroid :''' open the Asteroid Finder in RoboOrbits, see more [https://wiki.starkeeper.it/index.php/RoboOrbits_Finders here]
*'''Object Name :''' Read-only name of the Dynamic Target, coming from the search
*'''Object Key :''' Read-only key (code/number) of the Dynamic Target, coming from the search
*'''Object Dynamic Type :''' Read-only type of the Dynamic Target, coming from the search
*'''Reference Altitude''': Altitude to reach in degrees
*'''Exit Wait if Actual Altitude GREATER than or EQUAL (>=) to reference''': Wait until the target rises above the reference altitude
*'''Exit Wait if Actual Altitude LOWER than or EQUAL (>=) to reference''': Wait until the target sets below the reference altitude
*'''Wait Altitude until absolute time''': The Wait Altitude operation will terminate when this time is reached, whether or not the target has reached the reference altitude. This is usually done to end the wait with morning light
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*

*'''Wait Astronomical/Nautical/Civil Night''': Wait until astronomical/nautical/civil night, with an optional offset:

[[File:Dragscript-wait-night.png]]

*'''Get Latitude and Longitude from Mount''': Retrieve the current latitude and longitude from the connected mount, which must support this command. This location is used, along with the current date, to determine the time that night begins
*'''Use the Latitude and Longitude indicated below''': Specify your current latitude and longitude in the fields below. This location is used, along with the current date, to determine the time that night begins
*'''Offset''': Time in HH MM SS
**'''Offset Before''': If selected, exit the wait this amount of time before night
**'''Offset After''': If selected, exit the wait this amount of time after night
*'''Exit with ERROR if Wait Time is Greater than:''' if this option is flag the DragScript will exit with Error if the time wait for the begin of the next astronomical night is greater than the value in hour expressed in the numeric edit. Useful if you want to detect that the actual night is already finished and the dragscript can exit otherwise without this flag the next astrnomical night will be waited
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window
*
*
*'''Wait Dusk''' [[File:Dragscript-wait-dusk.jpg]]

*'''Get Latitude and Longitude from Mount''': Retrieve the current latitude and longitude from the connected mount, which must support this command. This location is used, along with the current date, to determine the time that dusk begins
*'''Use the Latitude and Longitude indicated below''': Specify your current latitude and longitude in the fields below. This location is used, along with the current date, to determine the time that dusk begins
*'''Offset''': Time in HH MM SS
**'''Offset Before''': If selected, exit the wait this amount of time before dusk
**'''Offset After''': If selected, exit the wait this amount of time after dusk
*'''Save Time to Event (minutes) in Decimal''': Save the computed time until Dusk in a decimal variable. See the DragScript example below for one way to use this.
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

You can configure the time at which dusk begins in the [[Flat Device Setup#Sky Flat|SkyFlat section of Flat Device]] Setup. {{Note|If dusk (plus or minus the offset if one is specified) has already passed, Wait Dusk returns OK if it has been less than 12 hours since dusk, else it returns ERROR if has been more than 12 hours}}

*'''Wait Dawn'''

[[File:Wait-dawn-2.jpg]]

*'''Get Latitude and Longitude from Mount''': Retrieve the current latitude and longitude from the connected mount, which must support this command. This location is used, along with the current date, to determine the time that dawn begins
*'''Use the Latitude and Longitude indicated below''': Specify your current latitude and longitude in the fields below. This location is used, along with the current date, to determine the time that dawn begins
*'''Offset''': Time in HH MM SS
**'''Offset Before''': If selected, exit the wait this amount of time before dawn
**'''Offset After''': If selected, exit the wait this amount of time after dawn
*'''Save Time to Event (minutes) in Decimal''': Save the computed time until dawn in a decimal variable. See the DragScript example below for one way to use this.
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

You can configure the time at which dawn begins in the [[Flat Device Setup#Sky Flat|SkyFlat section of Flat Device]] Setup.
 {{Note|If dawn (plus or minus the offset if one is specified) has already passed, Wait Dawn returns OK if it has been less than 12 hours, else ERROR if more than 12 hours}}

*

*'''Wait Safe''': Wait Safe Condition wait the safe condition before allow dragscript to execute net instruction. During the wait the events like Emergency Exit and Emergency suspend will be disabled and not managed. Just to remember you emergency events can coming from Viking I/O, Safe Monitor control, Weather Condition control. Like said this action will forcing event disable until exit for timeout or for safe. So be sure to have the observatory on the right configuration to avoid weather damage (closed and all parked). This action allow Voyager to run forever DragScript in case of no emergency exit. Can wait a time or an interval or the presence of astronomical/nautical/civil night, with an optional offset. Usually this is the first action in a script, its a good thing to put the Start node in Event disabled mode when you are manage the events in your DragScript. Also remember that the event at exit of this action will be restored to the original status, if they are disabled they will be leave disable or viceversa. We suggest also generally in dragscript to disable events during an atomic tasks like the opening observatory and connect setup to avoid interruption not really needed with impredictable results. If the action finish for wait will produce a status of TIMEOUT to the DragScript, if the action finish for one of the exit options will produce a status of ERROR to the DragScript, if the action found a SAFE status inside the wait option will produce a status of OK to the DragScript. You can decide if repeat the the action in a never ending loop (if you use night this mean to wait for the next night if you not check the exit ERROR options) or simple end the DragScript if you start DragScript night by Night. Rember that an Emergency Exit in any case will exit the DragScript.

{{Note|Wait SAFE Cannot be used inside the Event Manager (Exit, Suspend, Resume)}}

[[File:DSWaitSafe.png]]

*'''Wait SAFE until finish Night''': this option wait SAFE status until on eof specified kind of Nights is finished
**'''Get Latitude and Longitude from Mount''': Retrieve the current latitude and longitude from the connected mount, which must support this command. This location is used, along with the current date, to determine the time that astronomical night begins and end
**'''Use the Latitude and Longitude indicated below''': Specify your current latitude and longitude in the fields below. This location is used, along with the current date, to determine the time that astronomical night begins and end
**'''Night TYPE:''' the night to wait between Astronomical (Astrophotographers dark night -18° sun) , Nautical (-12° sun), Civil (-6° sun)
**'''Offset''': Time in HH MM SS
***'''Offset Before''': If selected, exit the wait this amount of time before astronomical night
***'''Offset After''': If selected, exit the wait this amount of time after astronomical night
*'''Wait SAFE until absolute time''': this option wait SAFE status until the absolute time you put inside the hh mm ss field
*'''Wait SAFE for a time interval of:''' this option wait SAFE status until the amount of time in the interval will be elapsed
*'''EXIT Options:''' with this options you can decide to exit with ERROR it the conditions inside is true
**'''Exit with ERROR if the Astronomical Night has ended less than:''' if this option is flag the DragScript will exit with Error if the astronomical night is ended by the time in hh field. This work and be active only if you use Wais SAFE with astronomical night. This flag enabled prevento to wait for the next night if the night is finished and you want to shutdown all without wait the next night.
**'''Exit with ERROR if Wait Time is greater than:''' if this option is flag the DragScript will exit with EORR if the time to wait is greater than the value in the hh field. This option is active only if you choose the Wait SAFE until absolute time. Useful if you dont wait over a certain time span.
*'''EVENT CHECK options:''' with this option you can decide to remove from processing status of SAFE some kind of events that will be ignored (event in any case are disable during the wait safe action)
**'''Check Emergency Exit Status in SAFE status calculation:''' if unchecked the condition that throw an Emergency Status will be ignored in calculation of SAFE Staus . ATTENTION !! this is a way really dangerous for your setup .. use only if you want to wait safe in particular condition , particular timing and for particular tasks
**'''Check Emergency SUSPEND Status in SAFE status calculation:''' if unchecked the condition that throw an Emergency Status will be ignored in calculation of SAFE Staus . ATTENTION !! this could be a way really dangerous for your setup .. use only if you want to wait safe in particular condition , particular timing and for particular tasks.
*'''LIGHT CONDITIONS options:''' with this option you can decide to remove from processing status of SAFE the LIGHT Conditions status
**'''Remove Weather LIGHT Conditions Status From Calculation of All Emergency Status:''' if unchecked the LIGHT conditions from Weather system will be not used to calculate the SAFE Status. Usefull if you want to open the dome with the light approaching the night time and do skyflat. For the Dawn flat you can decide to disable the LIGHT event using dedicated block
*'''MOON PHASE Options''' (Only for ADVANCED and FULL License Voyager versions): useful to ignore Safe status if the Moon Phase is over certains value
**'''Unsafe if Moon Phase equal or greater than:''' if checked Voyager will check the Moon Phase and if the value is equal or greater than the one indicated will return Unsafe to Emergency Events system
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

==Using the Time to Event Value in a DragScript==
Here's an example of using the '''Save Time to Event (minutes)''' value in a DragScript.

The basic idea is that you can decide whether or not to execute any actions based on how many minutes there are until or after dawn or dusk.

[[File:Dragscript-wait-dawn-2.jpg]]

The decimal variable "'''Minutes Before Event'''" is initialized to 0.

The '''Wait Dawn: Data from connected Setup - Offset (Before) 00:15:00 [hh:mm:ss]>>Minutes Before Event''' action waits until 15 minutes before dawn, and then puts the value 15 into the variable '''Minutes Before Event'''

The '''DO IF DECIMAL VALUE''' block will execute if the '''Minutes Before Event''' variable is between 0 and 15. If not, control passes to the End block.

The '''Goto Block: DAWN FLAT''' statement sends control back to that block, and the minutes before or after dawn are computed again and stored in the '''Minutes Before Event''' variable.

If it is after dawn when the '''Wait Dawn''' action runs, the value stored in '''Minutes Before Event''' will be negative, and the '''DO IF DECIMAL VALUE''' statement will not run.

 

==Signals==
Signals actions let you send notifications via email, Skype or SMS:

[[File:Dragscript-signals.png]]

{{Note|As of Voyager 2.1.4a, you can use the Save without Personal Info button to save a copy of your DragScript with all personal info (email addresses, email account logins, phone numbers, etc.) deleted. Use this save mode before posting a script online or sharing with others.}}

[[File:Dragscript-editor-toolbar-3.png]]

Use button 5 to save your DragScript with the personal info deleted for any of the actions in this group (Signals).

 

*Send Email using Voyager Account: Send an email using Voyager's email account. You must have an active [[Licensing|support and update Voyager license]] to use this option and an Internet connection

[[File:Dragscript-send-email.png]]

*'''Mail to''': Email address to send to
*'''Object''': Subject line of email TYPO: Should be Subject instead of Object
*'''Text''': Body of email
*'''Cancel''': Discard changes and close the window
*'''OK''': Save changes and close the window
*'''JOLLY Strings''':there are some special strings called jolly that can be used in mail text and will be replaced with some data from Voyager environment or DragScript variables
**'''Internal IPs:''' ##INTERNAL-IP## write a list of all internal IPs avalaible in the system
**'''External IP''': ##EXTERNAL-IP## write a list of external IP assigned to your PC(router) if you have internet connection up
**'''NOW''': ##NOW## write the actual date and time
**'''Mount Altitude''': ##MOUNT-ALT## write the actual altitude of Telescope Mount if connected
**'''Mount Azimuth''': ##MOUNT-AZ## write the actual azimuth of Telescope Mount if connected
**'''Variable''': ##VAR-name## where you must replace the ''name'' with the real name of your variable (case sensitive) , write the actual value of you variable (decimal, string or counter)

 

*'''Send Email''': Send an email notification using a specified email server and account. Requires an Internet connection

[[File:Dragscript-sendemail.png]]

*'''Mail From''': Email address this message is from
*'''Mail to''': Email address to send to
*'''Object''': Subject line of email TYPO: Should be Subject instead of Object
*'''Text''': Body of email
*'''SMTP User''': Username to login to SMTP (mail) server. Check with your local ISP or network administrator if you don't know how to login to your SMTP server to send email
*'''SMTP Password''': Password to login to your SMTP (mail) server
*'''SMTP Server''': Hostname or IP address of your SMTP (mail) server
*'''SMTP Port''': Port number of your SMTP (mail) server
*'''Use SSL''': If checked, use an SSL (secure) connection to your mail server
*'''GMAIL''': Click this button to use the SMTP server and port information for Google Gmail
*'''HOTMAIL''': Click this button to use the SMTP server and port information for Microsoft Hotmail
*'''Cancel''': Discard changes and close the window
*'''OK''': Save changes and close the window

*'''JOLLY Strings''':there are some special strings called jolly that can be used in mail text and will be replaced with some data from Voyager environment or DragScript variables
**'''Internal IPs:''' ##INTERNAL-IP## write a list of all internal IPs avalaible in the system
**'''External IP''': ##EXTERNAL-IP## write a list of external IP assigned to your PC(router) if you have internet connection up
**'''NOW''': ##NOW## write the actual date and time
**'''Mount Altitude''': ##MOUNT-ALT## write the actual altitude of Telescope Mount if connected
**'''Mount Azimuth''': ##MOUNT-AZ## write the actual azimuth of Telescope Mount if connected
**'''Variable''': ##VAR-name## where you must replace the ''name'' with the real name of your variable (case sensitive) , write the actual value of you variable (decimal, string or counter)

 

*'''Start Skype Call''': Start a Skype call from the computer running Voyager. Requires an Internet connection

[[File:Dragscript-skype.png]]

*'''Phone Number to Call''': Phone number or Skype name to call using Skype
*'''After Command Wait''': Time in seconds to wait after sending the command before timing out if no response from Skype
*'''After leave ringing for''': Time in seconds to wait after Skype places the call and the remote phone starts to ring
*'''Skype Exe Directory''': Location of Skype program on this computer
*'''Find Skype''': Look for Skype program on this computer and fill out the Skype Exe Directory if found
*'''Test''': Try to make a Skype call using the information in this dialog window
*'''Cancel''': Discard changes and close the window
*'''OK''': Save changes and close the window

 

*'''Send SMS with Nexmo'''
**Send an SMS (text message) using the Nexmo service: https://www.nexmo.com/ Requires an Internet connection.

[[File:Dragscript-nexmo.png]]

*'''Source Number or Name''': Phone number of sender, or name of sender. For country like USA this is a constraint to use (phone number) to avoid error in transmission (from Voyager version 2.2.1d)
*'''To Telephone Number''': Phone number to send SMS message to
*'''Text''': Body of SMS messages
*'''API Key''': API Key for Nexmo service - you must sign up at https://www.nexmo.com/ to get an API key and secret
*'''API Secret''': API Secret for Nexmo service
*'''Cancel''': Discard changes and close the window
*'''OK''': Save changes and close the window

*'''JOLLY Strings''':there are some special strings called jolly that can be used in mail text and will be replaced with some data from Voyager environment or DragScript variables
**'''Internal IPs:''' ##INTERNAL-IP## write a list of all internal IPs avalaible in the system
**'''External IP''': ##EXTERNAL-IP## write a list of external IP assigned to your PC(router) if you have internet connection up
**'''NOW''': ##NOW## write the actual date and time
**'''Mount Altitude''': ##MOUNT-ALT## write the actual altitude of Telescope Mount if connected
**'''Mount Azimuth''': ##MOUNT-AZ## write the actual azimuth of Telescope Mount if connected
**'''Variable''': ##VAR-name## where you must replace the ''name'' with the real name of your variable (case sensitive) , write the actual value of you variable (decimal, string or counter)

 
{{Note|Nexmo is an online service that offers voice and data communication. To use Nexmo from Voyager you must register at their site at https://www.nexmo.com}}

 

* '''Send Telegram'''
** Send an message using Telegram service chatbot: https://www.telgram.org/ Requires an Internet connection.
** [[File:SaveTelegramBlock.png]]

* '''Text''': message
* '''API ID''': API ID (token create during the chatbot) of your Telegram user
* '''Chat ID''': ID number assigned to chatbot created, you can get opening the link [https://api.telegram.org/bot<your https://api.telegram.org/bot<YOUR_TOKEN>/getUpdates]
* '''Cancel''': Discard changes and close the window
* '''OK''': Save changes and close the window

* '''JOLLY Strings''':there are some special strings called jolly that can be used in mail text and will be replaced with some data from Voyager environment or DragScript variables
**'''Internal IPs:''' ##INTERNAL-IP## write a list of all internal IPs avalaible in the system
** '''External IP''': ##EXTERNAL-IP## write a list of external IP assigned to your PC(router) if you have internet connection up
** '''NOW''': ##NOW## write the actual date and time
** '''Mount Altitude''': ##MOUNT-ALT## write the actual altitude of Telescope Mount if connected
**'''Mount Azimuth''': ##MOUNT-AZ## write the actual azimuth of Telescope Mount if connected
**'''Variable''': ##VAR-name## where you must replace the ''name'' with the real name of your variable (case sensitive) , write the actual value of you variable (decimal, string or counter)
'''Guide to obtain API ID and Chat ID''' :

# Download the Telegram APP on your mobile phone and register
# Open a chat with @BotFather and type /newbot to create a new private bot
# You will be asked for a friendly name - choose whatever you like, e.g. VoyagerMessages
# You will be given an "API Token" - save this somewhere - it is what you will enter as the API ID in your DragScript action, as shown above
# In your browser (can be on a desktop, doesn't have to be on your phone) open the link <nowiki>https://api.telegram.org/botYOUR-TOKEN/getUpdates</nowiki> replacing YOUR-TOKEN with the API Token
# You will get a short message that starts with {"ok":true. It won't have the Chat ID yet - this is OK
# Go back to Telegram and find the last message from @BotFather that starts with "Congratulations on your new bot. You will find it at ..." Click on that link and a new message room will open in Telegram, talking to your bot
# Type at least one message - a simple "hello" will do
# Go back to the browser page you opened in step 5 and hit reload - now you should see more characters including a long number after "from":{"id": That number is the Chat ID, which you use in your DragScript Send Telegram action as shown above
# If you don't see the Chat ID, try sending a couple more messages to your bot in Telegram and then quickly reload your browser until you get the ID
# That's it - you can now use the API ID and Chat ID to send Telegram messages from your DragScript

==User Manual Input==
User manual input actions allow interactions between Voyager and the user:

[[File:DragScriptUserInter.png]]

 

*'''Wait User OK''': Ask to the user with a windows prompt to press a button on the screen to continue or to abort and also its possible to activate a timeout during waiting of the user interaction
*[[File:DragScriptWaitUser.png]]
*'''Wait Mode''': how the wait will be work
*'''Use Timeout of:''' with this option the wait will finish in anycase after the seconds selected
*'''In case of timeout exit with:''' if the Use timeout of option will be used then exit can be selected between TIMEOUT or OK action result, this result will be usable in the DragScript using the IF condition related to actions
*'''No Timeout:''' with this option the wait will be for ever until physically user press the button on the screen
*'''Message:''' show a text message inside window prompt to the user
*'''Show Variable Value:''' show a text rappresentation of the variable selected inside window prompt to the user
*'''Wait User DATA''': Ask to the user with a windows prompt to input data (DECIMAL,STRING, COUNTER depends on type of variable used for storage) to continue or to abort and also its possible to activate a timeout during waiting of the user interaction. The inpout data will be stored in the selected variable.
*[[File:Immaginewefwef.png]]
*'''Wait Mode''': how the wait will be work
*'''Use Timeout of:''' with this option the wait will finish in anycase after the seconds selected
*'''In case of timeout exit with:''' if the Use timeout of option will be used then exit can be selected between TIMEOUT or OK action result, this result will be usable in the DragScript using the IF condition related to actions
*'''No Timeout:''' with this option the wait will be for ever until physically user press the button on the screen
*'''Message:''' show a text message inside window prompt to the user
*'''Show Variable Value:''' show a text rappresentation of the variable selected inside window prompt to the user
*'''Insert Data in Variable:''' the data in input from the user will be stored in the selected DragScript variable (variable must be declared before use it in DragScript). Based on type of DragScript Variable the edit mask of input field will be adapted. 
{{Note|if you using No Timeout option you must be really to be present in front of your PC to continue}}

==Optec Perseus==
Optec Perseus actions allow to interact with the hardware [https://optecinc.com/astronomy/catalog/perseus/default.htm Port Instrument Selector from Optec] :

[[File:OptecPer1.png]]

 

*'''Optec Perseus Read Device Info''': ask information about device and save it in environment variables of DragScript
*'''Optec Perseus Read Device Status''': ask status of device and save it in environment variables of DragScript
*'''Optec Perseus Homing''': command to device to Homing
*'''Optec Perseus Set Port:''' rotate device to select the port selected index
**[[File:OptecPer2.png]]
**'''Port:''' port index to select

 
{{Note|ASCOM Switch driver of Optec Perseus must be installed in order to allow working the DragScript Blocks}}

== Donuts ==
Donuts actions allow to interact with the software Donuts developed by Kames MacCormac, used for advanced research pointing, code here https://github.com/jmccormac01/Donuts :

[[File:DonutsSection.png]]

*'''Donuts Calibration''': ask to Donuts process to performe a Calibration using camera and mount

[[Category:DragScript]]
[[Category:All]]
[[Category:Manual|Lb]]

File:Immaginedd.png

2024-06-29T13:55:19Z

Leonardo: Leonardo uploaded a new version of File:Immaginedd.png

DragScript Flow of Control

2024-06-29T13:53:38Z

Leonardo: /* Decisions */

These DragScript elements control the flow of execution through your script. You can use the [[DragScript#DragScript Simulator|DragScript Simulator]] to test how control will flow when the DragScript actions complete with OK, ERROR or TIMEOUT status, and when Emergency Suspend, Resume and Exit events happen.

==Variables==
DragScript has several variable types: counters (integers), string variables and decimal numbers. They must be declared with the Counter, String or Decimal Number actions before they can be used. You can set and change their values, and then make decisions to execute DragScript actions based on their value. For example, you may build a script that runs from zero to ten sequences based on the value of a counter variable you set at the start of the script.

[[File:Dragscript-variables1.png]]

==='''Type'''===

*'''Counter''': Declare a counter (integer) variable and give it an initial value. You must declare a variable before using it

[[File:Dragscript-counter.png]]

*'''Label''': The name for this counter variable. There are no restrictions on length or legal characters, so just use something that makes sense for your control flow
*'''Init Value''': Initial value for the counter. Must be an integer between -2,000,000,000 and +2,000,000,000
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 

*'''String''': Declare a string variable and give it an initial value. You must declare a variable before using it

[[File:Dragscript-string.png]]

*'''Label''': The name for this string variable
*'''Init Value''': Initial value for the string
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 

*'''Decimal Number''': Declare a decimal number variable and give it an initial value. You must declare a variable before using it

[[File:Decimal-number.png]]

*'''Label''': The name for this decimal number variable
*'''Init Value''': Initial value for the decimal number - must be between the limits shown in the dialog box
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 

===Manage===

*'''Update''' '''Counter''': Update the value of a counter variable:

[[File:Dragscript-update-counter.png]]

*'''Counter''': Select the counter to update from the drop-down list. Counter variables must be declared with a Counter DragScript action before they can be updated
*'''Update Type''':
**'''Set to''': If selected, set the counter variable to the value in the Update Value field
**'''Offset by''': If selected, add the value in the Update Value field to the counter. The Update Value field can be negative or positive.
*'''Update Value''': A negative or positive integer value to either set the counter variable to or offset the counter variable by
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Update String''': Update the value of a string variable:

[[File:Dragscript-update-string.png]]

*'''String''': Select the string variable to update from the drop-down list
*'''Update Value''': Enter the new value for the string variable
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Update Decimal Number''': Update the value of a decimal number

[[File:Update-decimal-number.png]]

*'''Decimal Number''': Select the decimal number variable to update from the drop-down list
*'''Update Type''':
**'''Set to''': Set the decimal number value to the number in the Update Value field
**'''Offset by''': Add the +/- number in the Update Value field to the current value of the decimal number
*'''Update Value''': Enter the new value for the decimal number variable
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

* '''Update Decimal Number from Camera Temperature:''' Set the value of a decimal number from the temperature reported from Camera Driver:
* [[File:UpdateCameraTemp.png]]

* '''Decimal Number''': Select the decimal number variable to update from the drop-down list
* '''OK''': Save changes and close the window
* '''Cancel''': Discard changes and close the window 

*'''Update Decimal Number from Observing Conditions:''' Set the value of a decimal number from the observing conditions returned from I/O cards via Viking or from an ASCOM Observing Conditions driver:

[[File:Update-decimal-from-condx.png]]

*'''Decimal Number''': Select the decimal number variable to update from the drop-down list
*'''Observing Condition''': Select the observing condition whose value should be placed into the decimal number. These values come from [[Viking Setup|Viking]], a companion product from Starkeeper.it or from an ASCOM Observing Conditions driver
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''Update Decimal from Unix TimeStamp GMT:''' Set the value of a decimal number from the UNIX TimeStamp GMT based (seconds from 1/1/1970 UTC 0:0:0

[[File:Immaginergbrbrb.png]]

*'''Decimal Number''': Select the decimal number variable to update from the drop-down list
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Update Decimal Number from Focuser Temperature''': Set the value of a decimal number from the temperature returned by the focuser or auto-focus system

[[File:Update-decimal-from-focus-temp.png]]

*'''Decimal Number''': Select the decimal number variable to update from the drop-down list
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Update Decimal Number with Autofocus HFD''': Set the value of a decimal number with the final HFD (Half Flux Diameter) value from the last autofocus operation

[[File:Update-decimal-hfd.png]]

*'''Decimal Number''': Select the decimal number variable to update from the drop-down list
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window {{Note|At this time only RoboFire LocalField, RoboStar, and FocusMax return the HFD value - if you use a different autofocus routine, the HFD is not available}}

 

*'''Update Decimal from Focuser Position''': Set the value of a decimal number from the actual position returned by the RoboFire focuser

[[File:Update-decimal-from-focus-temp.png]]

*'''Decimal Number''': Select the decimal number variable to update from the drop-down list
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Update Decimal from Solved PA''': Set the value of a decimal number from the last solved PA returned by a Plate or Blind Solving action

[[File:UpdataFromPA.png]]

*'''Decimal Number''': Select the decimal number variable to update from the drop-down list
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''Update Decimal from Rotator PA''': Set the value of a decimal number from the Rotator PA returned by Rotator driver

[[File:UpdateRotPA.png]]

*'''Decimal Number''': Select the decimal number variable to update from the drop-down list
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Multiply Decimal Number''': Multiply a decimal number variable for the value in another variable of type counter or decimal or by direct value, the result will be stored in replace of actual value

[[File:DSMultiplyDecNum.png]]

*'''Decimal Number:''' Select the decimal number variable to multiply and update
*'''Multiply by Decimal Variable:''' Select the decimal number variable to use for multiply
*'''Multiply by Counter Variable:''' Select the counter variable to use for multiply
*'''Multiply by Value:''' Select the direct value to use for multipy
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

* '''Divide Decimal Number''': Divide a decimal number variable for the value in another variable of type counter or decimal or by direct value, the result will be stored in replace of actual value[[File:Immagineerfegwegwewegweg.png]]
** '''Decimal Number:''' Select the decimal number variable to divide and update
**'''Divide by Decimal Variable:''' Select the decimal number variable to use for divide
**'''Divide by Counter Variable:''' Select the counter variable to use for divide
**'''Divide by Value:''' Select the direct value to use for divide
**'''OK''': Save changes and close the window
**'''Cancel''': Discard changes and close the window

*'''Add to Decimal Number''': Add a decimal number variable for the value in another variable of type counter or decimal or by direct value, the result will be stored in replace of actual value[[File:Immaginevpomebmob.png]]
** '''Decimal Number:''' Select the decimal number variable to add and update
**'''Add by Decimal Variable:''' Select the decimal number variable to use for add
**'''Add by Counter Variable:''' Select the counter variable to use for add
**'''Add by Value:''' Select the direct value to use for add
**'''OK''': Save changes and close the window
**'''Cancel''': Discard changes and close the window

* '''Subtract to Decimal Number''': Subtract a decimal number variable for the value in another variable of type counter or decimal or by direct value, the result will be stored in replace of actual value[[File:Immagineiloiliolio.png]]
** '''Decimal Number:''' Select the decimal number variable to subtract and update
**'''Subtract by Decimal Variable:''' Select the decimal number variable to use for subtract
**'''Subtract by Counter Variable:''' Select the counter variable to use for subtract
**'''Subtract by Value:''' Select the direct value to use for subtract
**'''OK''': Save changes and close the window
**'''Cancel''': Discard changes and close the window

* '''Add to Counter''': Add a counter variable for the value in another variable of type counter or decimal or by direct value, the result will be stored in replace of actual value[[File:Immaginetntynty.png]]
** '''Counter:''' Select the counter variable to add and update
**'''Add Decimal Variable:''' Select the decimal number variable to use for add
**'''Add Counter Variable:''' Select the counter variable to use for add
**'''Add Value:''' Select the direct value to use for add
**'''OK''': Save changes and close the window
**'''Cancel''': Discard changes and close the window

*'''Subtract to Counter''': Subtract a counter variable for the value in another variable of type counter or decimal or by direct value, the result will be stored in replace of actual value[[File:Immaginedfdfbdf.png]]
** '''Counter:''' Select the counter variable to subtract and update
**'''Subtract Decimal Variable:''' Select the decimal number variable to use for subtract
**'''Subtract Counter Variable:''' Select the counter variable to use for subtract
**'''Subtract Value:''' Select the direct value to use for subtract
**'''OK''': Save changes and close the window
**'''Cancel''': Discard changes and close the window

==Jumps==
Jumps are used to goto a specified block of the DragScript. You can jump to the Start, End or a named Block.

[[File:Dragscript-jumps.png]]

*'''Goto Start''': Jump to the Start block of the script
*'''Goto Block''': Jump to a named block in the script

[[File:Dragscript-block-goto.png]]

*'''Block''': Select the named from the drop-down list, or type in the name of a block
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Goto End''': Jump to the End block of the script

==Repeats==
Repeats are used to execute a DragScript block a specified number of times, or until a specific time, or until astronomical night ends.

Repeats must be placed inside a block (note: Script: is a special block that contains the entire script.

If the result of evaluating a Repeat is to repeat the block, control returns to the block statement that contains the repeat.

[[File:Dragscript-repeats.png]]

*'''Repeat Block for n Times''': Repeat the containing block a specified number of times

[[File:Dragscript-repeat-block.png]]

*'''Times''': Number of times to repeat this block
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 

*'''Repeat Current Block Until Time''': Repeat the contained block until the specified time:

[[File:Dragscript-until-time.png]]

*'''Time''': Repeat the current block until this time
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 

*'''Repeat Block Until Astronomical/Nautical/Civil Night End''':

[[File:Dragscript-repeat-until-night-end.png]]

*'''Get Latitude and Longitude from Mount''': Retrieve the current latitude and longitude from the connected mount, which must support this command. This location is used, along with the current date, to determine the time that astronomical/nautical/civil night ends
*'''Use the Latitude and Longitude indicated below''': Specify your current latitude and longitude in the fields below. This location is used, along with the current date, to determine the time that astronomical/nautical/civil night ends
*'''Offset''': Time in HH MM SS
**'''Offset Before''': If selected, repeat the block until this amount of time before astronomical/nautical/civil night ends
**'''Offset After''': If selected, repeat the block this amount of time after astronomical/nautical/civil night ends
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 
**

{{Note|The time will be considered to have been reached if it is within 12 hours of the current time when the check is performed. E.g., if we set a repeat until 05:00, if it is 23:30 the repeat will be done since 23:30 is more than 12 hours in the future and less than 12 hours in the past, relative to 05:00. If it is 11:00, the repeat will be skipped, since 11:00 is later than 05:00 and more than 12 hours in the past.}} 
==Decisions==
Decisions control the flow of your DragScript based on the results of an action (OK, ERROR, TIMEOUT), operating conditions (current time, date or target altitude), or the value of a variable.

{{Note|A Decision element will create a new indent level in your DragScript. Drag new elements and drop them on the Decision element, or copy and paste them to it, to have their execution controlled by the result of the Decision}}

[[File:Dragscript-decisions-2.1.7s.jpg]]

==='''Action Results''':===
Do the actions at the indent level created by the Decision block based on the results of the action preceding the decision

**'''IF OK''': Do the actions following this statement if the result of the previous action was OK - meaning the action was successful
**'''IF ERROR''': Do the actions following this statement if the result of the previous action was ERROR - meaning the action failed
**'''IF TIMEOUT''': Do the actions following this statement if the result of the previous action was a TIMEOUT - meaning the action reached a specified timeout value without succeeding
**'''IF SKIPPED:''' Do the actions following this statement if the skipped status of the previuos action was SKIPPED - meaning the action not generate ERROR or finish OK just is SKIPPED because some constraints isnìt possible to match. At now only the Sequence Action use the SKIPPED status if time wait or time end or one of the constraints in azimuth, hour agle, alitute was thrown 

==='''Operating Conditions:'''===
Do the actions at the indent level created by the Decision block based on the time, date or target altitude

*'''DO IF ALTITUDE''': Do the actions if a target specified by RA and DEC coordinates has risen above or set below a specified altitude:

[[File:Dragscript-do-if-altitude.png]]

*'''RA Target J2000''': RA coordinates of the object you want to reach the Reference Altitude in HH MM SS or HH MM SS.sss
*'''DEC Target J2000''': DEC coordinates of the object you want to reach the Reference Altitude in DD MM SS or DD MM SS.sss
*'''Reference Altitude''': Altitude to reach in degrees
*'''Do If Actual Altitude GREATER than or EQUAL (>=) to reference''': Do the actions if the target has reached or risen above the reference altitude
*'''Do If Actual Altitude LOWER than or EQUAL (>=) to reference''': Do the actions if the target has reached or set below the reference altitude
*'''RoboClip:''' load RA and DEC from RoboClip catalog
*'''Coords From Sequence:''' load RA and DEC from a sequence file
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''DO IF ALTITUDE DYNAMIC TARGET''': Do the actions if a Dynamic Target has risen above or set below a specified altitude (RA/DEC will be calculated in realtime using RoboOrbits):

[[File:Immaginettg.png]]

* '''Comet :''' open the Comet Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
* '''Asteroid :''' open the Asteroid Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
* '''Planet:''' open the Planet Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
* '''Object Name :''' Read-only name of the Dynamic Target, coming from the search
* '''Object Key :''' Read-only key (code/number) of the Dynamic Target, coming from the search
* '''Object Dynamic Type :''' Read-only type of the Dynamic Target, coming from the search
*'''Reference Altitude''': Altitude to reach in degrees
*'''Do If Actual Altitude GREATER than or EQUAL (>=) to reference''': Do the actions if the target has reached or risen above the reference altitude
*'''Do If Actual Altitude LOWER than or EQUAL (>=) to reference''': Do the actions if the target has reached or set below the reference altitude
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''DO IF ALTITUDE BETWEEN:''' Do the actions if the altitude of a target specified by RA and DEC coordinates is between the '''Start''' and '''End''' values

[[File:Do-if-altitude-between.jpg]]

*'''RA Target J2000''': RA coordinates of the object you want to reach the Reference Altitude in HH MM SS or HH MM SS.sss
*'''DEC Target J2000''': DEC coordinates of the object you want to reach the Reference Altitude in DD MM SS or DD MM SS.sss
*'''Start and End:''' Do the actions if the specified target's altitude is greater than or equal to the '''Start''' value and less than or equal to the '''End''' value in decimal degrees
*'''RoboClip:''' load RA and DEC from RoboClip catalog
*'''Coords From Sequence:''' load RA and DEC from a sequence file
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''DO IF ALTITUDE BETWEEN DYNAMIC TARGET :''' Do the actions if the altitude of a Dynamic Target is between the '''Start''' and '''End''' values (RA/DEC will be calculated in realtime using RoboOrbits):

[[File:Immagineefe.png]]

*'''Comet :''' open the Comet Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
*'''Asteroid :''' open the Asteroid Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
*'''Planet:''' open the Planet Finder in RoboOrbits, see more here
*'''Object Name :''' Read-only name of the Dynamic Target, coming from the search
*'''Object Key :''' Read-only key (code/number) of the Dynamic Target, coming from the search
*'''Object Dynamic Type :''' Read-only type of the Dynamic Target, coming from the search
*'''Start and End:''' Do the actions if the specified target's altitude is greater than or equal to the '''Start''' value and less than or equal to the '''End''' value in decimal degrees
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''DO IF AZIMUTH BETWEEN:''' Do the actions if the azimuth of a target specified by RA and DEC coordinates is between the '''Start''' and '''End''' values and the Altitude of the Target is above the minimum Altitude for slew set up in Voyager Mount setting (default is 0°)

[[File:Immagineyjtyj.png]]

*'''RA Target J2000''': RA coordinates of the object you want to reach the Reference Altitude in HH MM SS or HH MM SS.sss
*'''DEC Target J2000''': DEC coordinates of the object you want to reach the Reference Altitude in DD MM SS or DD MM SS.sss
*'''Start and End:''' Do the actions if the specified target's azimuth is greater than or equal to the '''Start''' value and less than or equal to the '''End''' value in decimal degrees. Also the Altitude of the target must be above the minimum for a slew like set tup in Voyager Mount setting (default is 0°)
*'''RoboClip:''' load RA and DEC from RoboClip catalog
*'''Coords From Sequence:''' load RA and DEC from a sequence file
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

{{Note|Remember that a Target can be in the right azimuth interval but can be upside down wiht negtive altitude. DO IF will be not executed if altitude of target are under the minimum altitude value accepted for a slew in Voyager mount setting}}

 
*'''DO IF AZIMUTH BETWEEN DYNAMIC TARGET :''' Do the actions if the azimuth of a Dynamic Target is between the '''Start''' and '''End''' values and the Altitude of the Target is above the minimum Altitude for slew set up in Voyager Mount setting (default is 0°) (RA/DEC will be calculated in realtime using RoboOrbits):

[[File:DSDoIfAzimuth.png]]

*'''Comet :''' open the Comet Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
*'''Asteroid :''' open the Asteroid Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
*'''Planet:''' open the Planet Finder in RoboOrbits, see more here
*'''Object Name :''' Read-only name of the Dynamic Target, coming from the search
*'''Object Key :''' Read-only key (code/number) of the Dynamic Target, coming from the search
*'''Object Dynamic Type :''' Read-only type of the Dynamic Target, coming from the search
*'''Start and End:''' Do the actions if the specified target's azimuth is greater than or equal to the '''Start''' value and less than or equal to the '''End''' value in decimal degrees. Also the Altitude of the target must be above the minimum for a slew like set tup in Voyager Mount setting (default is 0°)
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''DO IF HA BETWEEN:''' Do the actions if the hour angle of the target (hours difference from the meridian) is between the specified start and end amounts [[File:Dragscript-doifha-2.1.7s.jpg]]
*'''RA Target J2000''': RA coordinates of the object whose hour angle we are testing, in HH MM SS or HH MM SS.sss
*'''DEC Target J2000''': DEC coordinates of the object whose hour angle we are testing, in DD MM SS or DD MM SS.sss
*'''Start and End:''' Do the actions if the specified target's HA (hour angle) is greater than or equal to the '''Start''' value and less than or equal to the '''End''' value in decimal hours. Note the values can be positive (after the meridian) or negative (before the meridian). The start to end can be both negative, both positive, or the start can be negative and the end can be positive. '''In all cases, the value must increase from start to end.'''
*'''RoboClip:''' load RA and DEC from RoboClip catalog
*'''Coords From Sequence:''' load RA and DEC from a sequence file
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 

*'''DO IF HA BETWEEN DYNAMIC TARGET :''' Do the actions if the hour angle of the Dynamic target (hours difference from the meridian) is between the specified start and end amounts (RA/DEC will be calculated in realtime using RoboOrbits):
*[[File:Immaginesf.png]]
*'''Comet :''' open the Comet Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
*'''Asteroid :''' open the Asteroid Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
*'''Object Name :''' Read-only name of the Dynamic Target, coming from the search
*'''Object Key :''' Read-only key (code/number) of the Dynamic Target, coming from the search
*'''Object Dynamic Type :''' Read-only type of the Dynamic Target, coming from the search
*'''Start and End:''' Do the actions if the specified target's HA (hour angle) is greater than or equal to the '''Start''' value and less than or equal to the '''End''' value in decimal hours. Note the values can be positive (after the meridian) or negative (before the meridian). The start to end can be both negative, both positive, or the start can be negative and the end can be positive. '''In all cases, the value must increase from start to end.'''
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''DO IF TIME BETWEEN''': Do the actions if the time is between the specified start and end times

[[File:Dragscript-do-if-time.png]]

*'''Start''': Beginning time of interval within which to do the following actions
*'''End''': End time of interval within which to do the following actions
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''DO IF DATE BETWEEN''': Do the actions at the indent level created by the DO statement if the date is between the start and end dates:

[[File:Dragscript-do-if-date.png]]

*'''Start''': Start date of the interval
*'''End''': End date of the interval
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''DO IF SQM''': Do the actions at the indent level created by the DO statement if the SQM value readed from control or Observing conditions is between the start and end dates:

[[File:DOIFSQM.png]]

*'''Reference Sky Quality''': reference value of Sky Quality to check
*'''Do If Actual value GREATER than or EQUAL [>=] to reference''': execute what is inside DO IF if the actual value >= that the reference value
*'''Do If Actual value LOWER than or EQUAL [<=] to reference''': execute what is inside DO IF if the actual value <= that the reference value
*'''Default''': use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''DO IF FOCAL LENGTH''': Do the actions at the indent level created by the DO statement if the FOCAL LENGTH readed from actual profile (Setup->Camera) is >=, <= or equal to reference value:

[[File:DoIfFocalLengthBlock.jpg]]

*'''Reference Focal Length''': reference value of Telescope Focal Length to check
*'''Do If Focal Length GREATER than or EQUAL [>=] to reference''': execute what is inside DO IF if the actual value >= that the reference value
*'''Do If Focal Length LOWER than or EQUAL [<=] to reference''': execute what is inside DO IF if the actual value <= that the reference value
*'''Do If Focal Length EQUAL [=] to reference''': execute what is inside DO IF if the actual value = that the reference value
*'''Default''': use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''DO IF DOME/ROOF OPEN''': Do the actions at the indent level created by the DO statement if the DOME/ROOF is opened
*'''DO IF DOME/ROOF CLOSED''': Do the actions at the indent level created by the DO statement if the DOME/ROOF is closed

{{Note|Status of DOME/ROOF will be read from the DOME Control configured in Voyager. This control is not absolutely reliable at 100%. Voyager cannot responding in anycase and any mode on damage derived from use of this conditional blocks. Please instead use the I/O card system with Viking management and physycal sensors to check the real status of your dome/roof.}}
*'''DO IF DISTRIBUITED SAFE END''': Wait the end of the night like defined in the Distribuited Safe block configuration. this is a features of the [https://software.starkeeper.it/voyager-plugins/ Distribuited Emergency plugin] dedicated to multi telscope in a single dome sharing emergency events
*'''DO IF EVEN DAY''': Decision block, true if the day of the month is an even number. Useful for example to do flat/calibration fit in different sets.
*'''DO IF ODD DAY:''' Decision block, true if the day of the month is an odd number. Useful for example to do flat/calibration fit in different sets.
*'''DO IF DAY OF WEEK:''' Decision block, true if the day of the week is one of those indicated in configuration (one or more day can be selected). Useful for example to do flat/calibration fit in different sets. Or doing some special task for copy file or etc etc
**[[File:Immaginewerwr.png]]

* '''DO IF PIER SIDE:''' Decision block, true if the pier side of the mount (what is reported by the connected driver) is equal to the parameter selected
**[[File:Immagineevveerv.png]]
** Pier West: mount before the meridian (or meridian passed but flip do not done)
** Pier East: mount after the meridian(meridian crossed and flip done) 
==='''Voyager Environment:'''===
Do the actions at the indent level created by the Decision block based on the Voyager internal status

*'''DO IF SETUP CONNECTED''': Do the actions if Voyager Setup is connected (from Startup menù or by DragScript connect block)
*'''DO IF SETUP DISCONNECTED''': Do the actions if Voyager Setup is not connected (from Startup menù or by DragScript disconnect block)

==='''Variable Check'''===
Do the actions at the indent level created by the DO IF statement based on the value of a variable. Variables must be declared before they can be tested in a DO IF statement

[[File:Decisions-variable-check.png]]
 

*'''DO IF COUNTER VALUE''': Check the value of a counter (integer) variable and do the following actions if the value of the counter meets the specified criteria:

[[File:Dragscript-do-if-counter.png]]

*'''Label''': Choose the counter variable to test from the drop-down list
*'''is Lower than''': Do the following actions if the selected counter value is less than the number in the counter field
*'''is Lower than or Equal to''': Do the following actions if the selected counter value is less than or equal to the number in the counter field
*'''is Equal to''': Do the following actions if the selected counter value is equal to the number in the counter field
*'''is Greater or Equal to:''' Do the following actions if the selected counter value is greater than or equal to the number in the counter field
*'''is Greater than:''' Do the following actions if the selected counter value is greater than the number in the counter field
*'''is Between:''' Do the following actions if the selected counter value is between the values in the two counter fields (greater than or equal to the left value AND less than or equal to the right field)
*'''is Not Equal''' to: Do the following actions if the selected counter value is not equal to the number in the counter field
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

**'''DO IF STRING VALUE''': Do the actions at the indent level created by the DO IF statement if a string variable is equal to, not equal to, or contains a specified string:

[[File:Dragscript-do-if-string.png]]

*'''Label''': Choose the string variable to test from the drop-down list
*'''is Equal to''': Do the following actions if the selected string value is equal to the specified string
*'''is Not Equal to''': Do the following actions if the selected string value is not equal to the specified string
*'''Contains''': Do the following actions if the selected string value contains the specified string
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 {{Note|String comparisons are case sensitive, i.e. TargetName is not equal to targetname}} 

*'''DO IF DECIMAL VALUE''': Do the actions at the indent level created by the DO IF statement if the value of the decimal number meets the specified criteria:

[[File:Do-if-decimal-value.png]]

*'''Label''': Choose the counter variable to test from the drop-down list
*'''is Lower than''': Do the following actions if the selected decimal number value is less than the number in the decimal number field
*'''is Lower than or Equal to''': Do the following actions if the selected decimal number value is less than or equal to the number in the decimal number field
*'''is Equal to''': Do the following actions if the selected decimal number value is equal to the number in the counter field
*'''is Greater or Equal to:''' Do the following actions if the selected decimal number value is greater than or equal to the number in the decimal number field
*'''is Greater than:''' Do the following actions if the selected decimal number value is greater than the number in the decimal number field
*'''is Between:''' Do the following actions if the selected decimal number value is between the values in the two decimal number fields (greater than or equal to the left value AND less than or equal to the right field)
*'''is Not Equal''' to: Do the following actions if the selected decimal number value is not equal to the number in the decimal number field
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

* '''DO IF COUNTER VALUE (Extended)''': Check the value of a counter (integer) variable and do the following actions if the value of the counter meets the specified criteria extended to a value, counter or decimal value:
** [[File:Immagineerfer.png]]
*** '''Counter''': Choose the counter variable to test from the drop-down list
***'''is Lower than''': Do the following actions if the selected counter value is less than the number in the counter field
***'''is Lower than or Equal to''': Do the following actions if the selected counter value is less than or equal to the number in the value field , counter variable or decimal variable
***'''is Equal to''': Do the following actions if the selected counter value is equal to the number in the value field , counter variable or decimal variable
***'''is Greater or Equal to:''' Do the following actions if the selected counter value is greater than or equal to the number in the value field , counter variable or decimal variable
***'''is Greater than:''' Do the following actions if the selected counter value is greater than the number in the value field , counter variable or decimal variable
***'''is Between:''' Do the following actions if the selected counter value is between the values in the value field , counter variable or decimal variable (greater than or equal to the left value AND less than or equal to the right field)
***'''is Not Equal''' to: Do the following actions if the selected counter value is not equal to the number in the value field , counter variable or decimal variable
***'''OK''': Save changes and close the window
***'''Cancel''': Discard changes and close the window 

'''DO IF DECIMAL VALUE (Extended)''': Check the value of a counter (integer) variable and do the following actions if the value of the counter meets the specified criteria extended to a value, counter or decimal value:
* [[File:Immaginee3fer.png]]
**'''Decimal Number''': Choose the decimal variable to test from the drop-down list
**'''is Lower than''': Do the following actions if the selected decimal value is less than the number in the counter field
**'''is Lower than or Equal to''': Do the following actions if the selected decimal value is less than or equal to the number in the value field , counter variable or decimal variable
**'''is Equal to''': Do the following actions if the selected decimal value is equal to the number in the value field , counter variable or decimal variable
**'''is Greater or Equal to:''' Do the following actions if the selected decimal value is greater than or equal to the number in the value field , counter variable or decimal variable
**'''is Greater than:''' Do the following actions if the selected decimal value is greater than the number in the value field , counter variable or decimal variable
**'''is Between:''' Do the following actions if the selected decimal value is between the values in the value field , counter variable or decimal variable (greater than or equal to the left value AND less than or equal to the right field)
**'''is Not Equal''' to: Do the following actions if the selected decimal value is not equal to the number in the value field , counter variable or decimal variable
**'''OK''': Save changes and close the window
**'''Cancel''': Discard changes and close the window

==Events==
DragScript execution can be suspended, terminated (exited) and resumed based on the occurrence of Emergency Exit, Emergency Suspend and Emergency Resume events.

The most common use of Events is together with a weather monitoring system, as configured in [[Weather Setup]]. You can specify at a detailed level which events should cause DragScript execution to SUSPEND (such as overcast clouds), EXIT (such as rain), or RESUME (such as clouds moving out so it becomes clear again).

In addition to weather events, you can raise Emergency Exit, Emergency Suspend and Emergency Resume events at any point in your DragScript.

When an Event is raised, control flow goes immediately to the appropriate block (Exit, Suspend or Resume) in the Events block of your DragScript. Create those blocks by dragging elements from the Events: Manage list.

[[File:Dragscript-events.png]]

==='''Manage'''===
See the [[DragScript Examples#Emergency Exit|DragScript Examples]] section to see how these blocks work in a DragScript.

*'''Emergency Exit''': Drag this element to the Events block of your DragScript. Then drag the actions you wish to take place when an Emergency Exit event is raised. For example, stop tracking, stop guiding, park your mount, and close the observatory roof
*'''Emergency Suspend''': Drag this element to the Events block of your DragScript. Then drag the actions you wish to take place when an Emergency Suspend event is raised. For example, stop tracking and stop guiding

[[File:Dragscript-suspend-2.png]]

*'''Wait Resume until absolute time''': If the time specified in HH MM SS is reached without an Emergency Resume event being raised, perform the action selected from the radio buttons in this dialog window
*'''Wait Resume for a time interval of:''' If the time period specified in HH MM SS elapses without an Emergency Resume event being raised, perform the action selected from the radio buttons in this dialog window
*'''Wait Resume until end of Astronomical Night''': If the end of Astronomical Night arrives without an Emergency Resume event being raised, perform the action selected from the radio buttons in this dialog window
*'''Wait Resume until end of Nautical Night''' : If the end of Nautical Night arrives without an Emergency Resume event being raised, perform the action selected from the radio buttons in this dialog window
*'''Wait Resume until end of Civil Night''': If the end of Civil Night arrives without an Emergency Resume event being raised, perform the action selected from the radio buttons in this dialog window
*{{Note|the various Wait Resume until end of xxxx Nights needed the specification on how to retrieve the data for the night (from Mount or by manual latitude and longitude) . }}
** '''Get Latitude and Longitude from Mount''': Retrieve the current latitude and longitude from the connected mount, which must support this command. This location is used, along with the current date, to determine the time that astronomical night begins and end. SETUP MUST BE CONNECTED TO WORK !
** '''Use the Latitude and Longitude indicated below''': Specify your current latitude and longitude in the fields below. This location is used, along with the current date, to determine the time that astronomical night begins and end
**
*'''Wait Resume Until Distribuited SAFE End [Distribuited Emergency Plugin Needed]:''' if selected Voyager will wait for resume according the SAFE END procedure of the Distribuited Emergency Plugin. A dedicated plugin for multi pier in a single building is needed https://software.starkeeper.it/voyager-plugins/
*'''On Resume Timeout End DragScript''': If the time specified above is reached without an Emergency Resume event occurring, end the DragScript
*'''On Resume Timeout Exec Emergency Exit Event''': If the time specified above is reached without an Emergency Resume event occurring, raise an Emergency Exit event
*'''On Resume Timeout Restart DragScript''': If the time specified above is reached without an Emergency Resume event occurring, Voyager will restart the DragScript form beginneng like a new running
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''Emergency Resume''': Execute these actions when an Emergency Resume event is raised. For example, start tracking and start guiding 

==='''Raise'''===
Raise an Emergency Exit, Suspend or Resume event

*'''Raise Emergency Exit Event''': Raise the Emergency Exit event. Execution of the DragScript will go immediately to the Emergency Exit block in the Events block
*'''Raise Emergency Suspend Event''': Raise the Emergency Suspend event. Execution of the DragScript will go immediately to the Emergency Suspend block in the Events block
*'''Raise Emergency Resume Event''': Raise the Emergency Resume event. Execution of the DragScript will go immediately to the Emergency Resume block in the Events block

==='''Remote'''===
Block for management of Distributed [https://wiki.starkeeper.it/index.php/Distributed_Emergency Distributed Emergency]

*'''Set Distributed Emergency Status''': Update overriding the internal Distributed Emergency Status for the Voyager Client connected to the selected value
**[[File:Des1.png]]
*'''Distributed Safe''': Distributed Safe wait the night like configured and in the night wait to have a Safe condition from the Emergency Event System (in Voyager is Weather, Safety Monitor, Viking I/O). If night is recognized and safe condition is true DragScript will exit from this block with OK result. If timeout is reached waiting DragScript will exit from this block with a TIMEOUT result. In case of error during waiting DragScript will exit with ERROR result. Checking the exit of block user can decide if inform all the client of a SAFE condition using the SET DISTRIBUTED EMERGENCY STATUS or restart the Master DragScript to wait for better conditions (same night or next night is automatically decided from DragScript). This block is usually associated and work only if you using the [https://wiki.starkeeper.it/index.php/Distributed_Emergency Distributed Emergency] plugin. Right and only place where to use is the Voyager MASTER of plugin where information is processed and emergency events checked.
**'''Important Note!''' Distributed Safe Cannot be used inside the Event Manager (Exit, Suspend, Resume)
***[[File:DES2.png]]
***'''NIGHT Configuration:''' data necessary to calculate the start and end interval of the actual night
****'''Night DATA:''' data about location of observatory
*****Latitude: Latitude of the Mount
*****Longitude: Longitude of the Mount
****'''Night TYPE:''' type of night to calculate. Astronomical, Nautical or Civil
****'''Night START OFFSET:''' apply an offset to the time start of the night
*****Offset Before: offset before the start in hours, minutes and seconds
*****Offset After: offset after the start in hours, minutes and seconds
****'''Night END OFFSET:''' apply an offset to the time end of the night
*****Offset Before: offset before the end in hours, minutes and seconds
*****Offset After: offset after the end in hours, minutes and seconds
****'''EVENT CHECK options:''' with this option you can decide to remove from processing status of SAFE some kind of events that will be ignored (event in any case are disable during the wait safe action)
*****'''Check Emergency Exit Status in SAFE status calculation:''' if unchecked the condition that throw an Emergency Status will be ignored in calculation of SAFE Staus . ATTENTION !! this is a way really dangerous for your setup .. use only if you want to wait safe in particular condition , particular timing and for particular tasks
*****'''Check Emergency SUSPEND Status in SAFE status calculation:''' if unchecked the condition that throw an Emergency Status will be ignored in calculation of SAFE Staus . ATTENTION !! this could be a way really dangerous for your setup .. use only if you want to wait safe in particular condition , particular timing and for particular tasks.
****'''LIGHT CONDITIONS options:''' with this option you can decide to remove from processing status of SAFE the LIGHT Conditions status
*****'''Remove Weather LIGHT Conditions Status From Calculation of All Emergency Status:''' if unchecked the LIGHT conditions from Weather system will be not used to calculate the SAFE Status. Usefull if you want to open the dome with the light approaching the night time and do skyflat. For the Dawn flat you can decide to disable the LIGHT event using dedicated block
****'''Default''': Use the default settings
****'''OK''': Save changes and close the window
****'''Cancel''': Discard changes and close the window

==='''Various'''===

*'''Resume from Block''': Resume execution starting with the specified block. This can only be placed in the Emergency Resume block in the Events block

[[File:Dragscript-resume-from-block.png]]

*'''Block''': Choose the block where execution should resume from the drop-down list
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Disable Events''': Disable event processing. Emergency Exit, Suspend and Resume events will be ignored

*'''Enable Events''': Enable event processing. Emergency Exit, Suspend and Resume events will be recognized and handled
*'''Disable Exit Event:''' Disable event processing. Emergency Exit only event will be ignored
*'''Enable Exit Event:''' Enable event processing. Emergency Exit event will be recognized and handled
*'''Disable Suspend Event:''' Disable event processing. Emergency Suspend and Resume only events will be ignored
*'''Enable Suspend Event:''' Enable event processing. Emergency Suspend and Resume only events will be recognized and handled
*'''Disable Weather Light Event:''' Disable event processing of Light conditions coming from Weather System. Status of Light will be not used to processing the Emergency Exit and/or Emergency Suspend or Emergency Resume events (Work only if you have a weather system configured in Voyager)
*'''Enable Weather Light Event:''' Enable event processing of Light conditions coming from Weather System. Status of Light will be used to processing the Emergency Exit and/or Emergency Suspend or Emergency Resume events (Work only if you have a weather system configured in Voyager)

{{Note|Enable and disable Events is a really powerful features !!! Please use with complete understand that if you forget to re-enable the events your setup can be damaged from weather conditions. }} 

{{Note|Enable and disable Light Conditions from emergency status calculation can be useful for do SkyFlat or generally other kind of tasks at dawn and dusk or for daylight operations and testing.}}

== Events Robotarget ==
If you are running a Voyager Advanced or Full version you can intercept the thrown events generated by RoboTarget Action during. This event can be annotations or errors. Data about are saved in the environment variables of DragScript and can be used in the signal block of DragScript. What is inside the Events RoboTarget Management will executed in seld contained DragScript ineriths by the actual DragScript eliminating all except what is in the events handle you have created.

To select the event handle and create it you must use the Operating Conditions blocks.

[[File:Immagineergerherherh.png]]

=== '''Operating Conditions''' ===
There is only one operating conditions block to handle a RoboTarget Event. The DO IF ROBOTARGER EVENT. You can use one or more of this block.

* '''DO IF ROBOTARGER EVENT''': Handle one or more events related to RoboTarget Action executing in a self contained ineriths dragscript the block inside the condition
* [[File:Immaginergerwerhgwrh.png]]

* '''Even(s) Selected''': select one or more RoboTarget events to handle
* '''Reset''': Uncheck all the events selected and remove from handling
* '''Cancel''': exit from configuration without save anything
* '''OK''': Save changes and close the window

==Block==
The Block element creates a new block in your DragScript. Drag and Drop it on a DragScript element that creates a new indent level, e.g. Script, DO IF, IF, Emergency Exit, Emergency Suspend, or Emergency Resume.

[[File:Dragscript-block.png]]

*'''Label''': Give your block a name. This name can be referenced by other script elements such as jumps and resumes
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

==Remark==
The Remark element adds a non-executable comment to your script for documentation purposes

[[File:Dragscript-remark.png]]

*'''Remark''': Enter a comment that will appear in your script
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 
==Flow==
Flow Control are useful for changin flow of execution during DragScript

[[File:DSFlowRestart.png]] 

* '''Exit Block:''' exit the current block container and execute the first following useful instruction
** must be used inside a BLOCK container
** cannot be used directly under the SCRIPT default block or EVENTS default block
** if nested inside more than one BLOCK container DragScript Engine will exit from the first BLOCK container parent
* '''Restart DragScript:''' The Restart DragScript element allow script to be restart from beginning, all the variable and status will be resetted

[[Category:DragScript]]
[[Category:All]]
[[Category:Manual|Ld]]

File:Immagineyjtyj.png

2024-06-29T13:53:12Z

Leonardo:

tjrjt

File:DSDoIfAzimuth.png

2024-06-29T13:51:18Z

Leonardo: Leonardo uploaded a new version of File:DSDoIfAzimuth.png

== Summary ==
importing from old wiki

DragScript Flow of Control

2024-06-29T13:51:05Z

Leonardo: /* Operating Conditions: */

These DragScript elements control the flow of execution through your script. You can use the [[DragScript#DragScript Simulator|DragScript Simulator]] to test how control will flow when the DragScript actions complete with OK, ERROR or TIMEOUT status, and when Emergency Suspend, Resume and Exit events happen.

==Variables==
DragScript has several variable types: counters (integers), string variables and decimal numbers. They must be declared with the Counter, String or Decimal Number actions before they can be used. You can set and change their values, and then make decisions to execute DragScript actions based on their value. For example, you may build a script that runs from zero to ten sequences based on the value of a counter variable you set at the start of the script.

[[File:Dragscript-variables1.png]]

==='''Type'''===

*'''Counter''': Declare a counter (integer) variable and give it an initial value. You must declare a variable before using it

[[File:Dragscript-counter.png]]

*'''Label''': The name for this counter variable. There are no restrictions on length or legal characters, so just use something that makes sense for your control flow
*'''Init Value''': Initial value for the counter. Must be an integer between -2,000,000,000 and +2,000,000,000
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 

*'''String''': Declare a string variable and give it an initial value. You must declare a variable before using it

[[File:Dragscript-string.png]]

*'''Label''': The name for this string variable
*'''Init Value''': Initial value for the string
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 

*'''Decimal Number''': Declare a decimal number variable and give it an initial value. You must declare a variable before using it

[[File:Decimal-number.png]]

*'''Label''': The name for this decimal number variable
*'''Init Value''': Initial value for the decimal number - must be between the limits shown in the dialog box
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 

===Manage===

*'''Update''' '''Counter''': Update the value of a counter variable:

[[File:Dragscript-update-counter.png]]

*'''Counter''': Select the counter to update from the drop-down list. Counter variables must be declared with a Counter DragScript action before they can be updated
*'''Update Type''':
**'''Set to''': If selected, set the counter variable to the value in the Update Value field
**'''Offset by''': If selected, add the value in the Update Value field to the counter. The Update Value field can be negative or positive.
*'''Update Value''': A negative or positive integer value to either set the counter variable to or offset the counter variable by
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Update String''': Update the value of a string variable:

[[File:Dragscript-update-string.png]]

*'''String''': Select the string variable to update from the drop-down list
*'''Update Value''': Enter the new value for the string variable
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Update Decimal Number''': Update the value of a decimal number

[[File:Update-decimal-number.png]]

*'''Decimal Number''': Select the decimal number variable to update from the drop-down list
*'''Update Type''':
**'''Set to''': Set the decimal number value to the number in the Update Value field
**'''Offset by''': Add the +/- number in the Update Value field to the current value of the decimal number
*'''Update Value''': Enter the new value for the decimal number variable
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

* '''Update Decimal Number from Camera Temperature:''' Set the value of a decimal number from the temperature reported from Camera Driver:
* [[File:UpdateCameraTemp.png]]

* '''Decimal Number''': Select the decimal number variable to update from the drop-down list
* '''OK''': Save changes and close the window
* '''Cancel''': Discard changes and close the window 

*'''Update Decimal Number from Observing Conditions:''' Set the value of a decimal number from the observing conditions returned from I/O cards via Viking or from an ASCOM Observing Conditions driver:

[[File:Update-decimal-from-condx.png]]

*'''Decimal Number''': Select the decimal number variable to update from the drop-down list
*'''Observing Condition''': Select the observing condition whose value should be placed into the decimal number. These values come from [[Viking Setup|Viking]], a companion product from Starkeeper.it or from an ASCOM Observing Conditions driver
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''Update Decimal from Unix TimeStamp GMT:''' Set the value of a decimal number from the UNIX TimeStamp GMT based (seconds from 1/1/1970 UTC 0:0:0

[[File:Immaginergbrbrb.png]]

*'''Decimal Number''': Select the decimal number variable to update from the drop-down list
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Update Decimal Number from Focuser Temperature''': Set the value of a decimal number from the temperature returned by the focuser or auto-focus system

[[File:Update-decimal-from-focus-temp.png]]

*'''Decimal Number''': Select the decimal number variable to update from the drop-down list
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Update Decimal Number with Autofocus HFD''': Set the value of a decimal number with the final HFD (Half Flux Diameter) value from the last autofocus operation

[[File:Update-decimal-hfd.png]]

*'''Decimal Number''': Select the decimal number variable to update from the drop-down list
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window {{Note|At this time only RoboFire LocalField, RoboStar, and FocusMax return the HFD value - if you use a different autofocus routine, the HFD is not available}}

 

*'''Update Decimal from Focuser Position''': Set the value of a decimal number from the actual position returned by the RoboFire focuser

[[File:Update-decimal-from-focus-temp.png]]

*'''Decimal Number''': Select the decimal number variable to update from the drop-down list
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Update Decimal from Solved PA''': Set the value of a decimal number from the last solved PA returned by a Plate or Blind Solving action

[[File:UpdataFromPA.png]]

*'''Decimal Number''': Select the decimal number variable to update from the drop-down list
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''Update Decimal from Rotator PA''': Set the value of a decimal number from the Rotator PA returned by Rotator driver

[[File:UpdateRotPA.png]]

*'''Decimal Number''': Select the decimal number variable to update from the drop-down list
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Multiply Decimal Number''': Multiply a decimal number variable for the value in another variable of type counter or decimal or by direct value, the result will be stored in replace of actual value

[[File:DSMultiplyDecNum.png]]

*'''Decimal Number:''' Select the decimal number variable to multiply and update
*'''Multiply by Decimal Variable:''' Select the decimal number variable to use for multiply
*'''Multiply by Counter Variable:''' Select the counter variable to use for multiply
*'''Multiply by Value:''' Select the direct value to use for multipy
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

* '''Divide Decimal Number''': Divide a decimal number variable for the value in another variable of type counter or decimal or by direct value, the result will be stored in replace of actual value[[File:Immagineerfegwegwewegweg.png]]
** '''Decimal Number:''' Select the decimal number variable to divide and update
**'''Divide by Decimal Variable:''' Select the decimal number variable to use for divide
**'''Divide by Counter Variable:''' Select the counter variable to use for divide
**'''Divide by Value:''' Select the direct value to use for divide
**'''OK''': Save changes and close the window
**'''Cancel''': Discard changes and close the window

*'''Add to Decimal Number''': Add a decimal number variable for the value in another variable of type counter or decimal or by direct value, the result will be stored in replace of actual value[[File:Immaginevpomebmob.png]]
** '''Decimal Number:''' Select the decimal number variable to add and update
**'''Add by Decimal Variable:''' Select the decimal number variable to use for add
**'''Add by Counter Variable:''' Select the counter variable to use for add
**'''Add by Value:''' Select the direct value to use for add
**'''OK''': Save changes and close the window
**'''Cancel''': Discard changes and close the window

* '''Subtract to Decimal Number''': Subtract a decimal number variable for the value in another variable of type counter or decimal or by direct value, the result will be stored in replace of actual value[[File:Immagineiloiliolio.png]]
** '''Decimal Number:''' Select the decimal number variable to subtract and update
**'''Subtract by Decimal Variable:''' Select the decimal number variable to use for subtract
**'''Subtract by Counter Variable:''' Select the counter variable to use for subtract
**'''Subtract by Value:''' Select the direct value to use for subtract
**'''OK''': Save changes and close the window
**'''Cancel''': Discard changes and close the window

* '''Add to Counter''': Add a counter variable for the value in another variable of type counter or decimal or by direct value, the result will be stored in replace of actual value[[File:Immaginetntynty.png]]
** '''Counter:''' Select the counter variable to add and update
**'''Add Decimal Variable:''' Select the decimal number variable to use for add
**'''Add Counter Variable:''' Select the counter variable to use for add
**'''Add Value:''' Select the direct value to use for add
**'''OK''': Save changes and close the window
**'''Cancel''': Discard changes and close the window

*'''Subtract to Counter''': Subtract a counter variable for the value in another variable of type counter or decimal or by direct value, the result will be stored in replace of actual value[[File:Immaginedfdfbdf.png]]
** '''Counter:''' Select the counter variable to subtract and update
**'''Subtract Decimal Variable:''' Select the decimal number variable to use for subtract
**'''Subtract Counter Variable:''' Select the counter variable to use for subtract
**'''Subtract Value:''' Select the direct value to use for subtract
**'''OK''': Save changes and close the window
**'''Cancel''': Discard changes and close the window

==Jumps==
Jumps are used to goto a specified block of the DragScript. You can jump to the Start, End or a named Block.

[[File:Dragscript-jumps.png]]

*'''Goto Start''': Jump to the Start block of the script
*'''Goto Block''': Jump to a named block in the script

[[File:Dragscript-block-goto.png]]

*'''Block''': Select the named from the drop-down list, or type in the name of a block
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Goto End''': Jump to the End block of the script

==Repeats==
Repeats are used to execute a DragScript block a specified number of times, or until a specific time, or until astronomical night ends.

Repeats must be placed inside a block (note: Script: is a special block that contains the entire script.

If the result of evaluating a Repeat is to repeat the block, control returns to the block statement that contains the repeat.

[[File:Dragscript-repeats.png]]

*'''Repeat Block for n Times''': Repeat the containing block a specified number of times

[[File:Dragscript-repeat-block.png]]

*'''Times''': Number of times to repeat this block
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 

*'''Repeat Current Block Until Time''': Repeat the contained block until the specified time:

[[File:Dragscript-until-time.png]]

*'''Time''': Repeat the current block until this time
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 

*'''Repeat Block Until Astronomical/Nautical/Civil Night End''':

[[File:Dragscript-repeat-until-night-end.png]]

*'''Get Latitude and Longitude from Mount''': Retrieve the current latitude and longitude from the connected mount, which must support this command. This location is used, along with the current date, to determine the time that astronomical/nautical/civil night ends
*'''Use the Latitude and Longitude indicated below''': Specify your current latitude and longitude in the fields below. This location is used, along with the current date, to determine the time that astronomical/nautical/civil night ends
*'''Offset''': Time in HH MM SS
**'''Offset Before''': If selected, repeat the block until this amount of time before astronomical/nautical/civil night ends
**'''Offset After''': If selected, repeat the block this amount of time after astronomical/nautical/civil night ends
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 
**

{{Note|The time will be considered to have been reached if it is within 12 hours of the current time when the check is performed. E.g., if we set a repeat until 05:00, if it is 23:30 the repeat will be done since 23:30 is more than 12 hours in the future and less than 12 hours in the past, relative to 05:00. If it is 11:00, the repeat will be skipped, since 11:00 is later than 05:00 and more than 12 hours in the past.}} 
==Decisions==
Decisions control the flow of your DragScript based on the results of an action (OK, ERROR, TIMEOUT), operating conditions (current time, date or target altitude), or the value of a variable.

{{Note|A Decision element will create a new indent level in your DragScript. Drag new elements and drop them on the Decision element, or copy and paste them to it, to have their execution controlled by the result of the Decision}}

[[File:Dragscript-decisions-2.1.7s.jpg]]

==='''Action Results''':===
Do the actions at the indent level created by the Decision block based on the results of the action preceding the decision

**'''IF OK''': Do the actions following this statement if the result of the previous action was OK - meaning the action was successful
**'''IF ERROR''': Do the actions following this statement if the result of the previous action was ERROR - meaning the action failed
**'''IF TIMEOUT''': Do the actions following this statement if the result of the previous action was a TIMEOUT - meaning the action reached a specified timeout value without succeeding
**'''IF SKIPPED:''' Do the actions following this statement if the skipped status of the previuos action was SKIPPED - meaning the action not generate ERROR or finish OK just is SKIPPED because some constraints isnìt possible to match. At now only the Sequence Action use the SKIPPED status if time wait or time end or one of the constraints in azimuth, hour agle, alitute was thrown 

==='''Operating Conditions:'''===
Do the actions at the indent level created by the Decision block based on the time, date or target altitude

*'''DO IF ALTITUDE''': Do the actions if a target specified by RA and DEC coordinates has risen above or set below a specified altitude:

[[File:Dragscript-do-if-altitude.png]]

*'''RA Target J2000''': RA coordinates of the object you want to reach the Reference Altitude in HH MM SS or HH MM SS.sss
*'''DEC Target J2000''': DEC coordinates of the object you want to reach the Reference Altitude in DD MM SS or DD MM SS.sss
*'''Reference Altitude''': Altitude to reach in degrees
*'''Do If Actual Altitude GREATER than or EQUAL (>=) to reference''': Do the actions if the target has reached or risen above the reference altitude
*'''Do If Actual Altitude LOWER than or EQUAL (>=) to reference''': Do the actions if the target has reached or set below the reference altitude
*'''RoboClip:''' load RA and DEC from RoboClip catalog
*'''Coords From Sequence:''' load RA and DEC from a sequence file
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''DO IF ALTITUDE DYNAMIC TARGET''': Do the actions if a Dynamic Target has risen above or set below a specified altitude (RA/DEC will be calculated in realtime using RoboOrbits):

[[File:Immaginettg.png]]

* '''Comet :''' open the Comet Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
* '''Asteroid :''' open the Asteroid Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
* '''Planet:''' open the Planet Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
* '''Object Name :''' Read-only name of the Dynamic Target, coming from the search
* '''Object Key :''' Read-only key (code/number) of the Dynamic Target, coming from the search
* '''Object Dynamic Type :''' Read-only type of the Dynamic Target, coming from the search
*'''Reference Altitude''': Altitude to reach in degrees
*'''Do If Actual Altitude GREATER than or EQUAL (>=) to reference''': Do the actions if the target has reached or risen above the reference altitude
*'''Do If Actual Altitude LOWER than or EQUAL (>=) to reference''': Do the actions if the target has reached or set below the reference altitude
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''DO IF ALTITUDE BETWEEN:''' Do the actions if the altitude of a target specified by RA and DEC coordinates is between the '''Start''' and '''End''' values

[[File:Do-if-altitude-between.jpg]]

*'''RA Target J2000''': RA coordinates of the object you want to reach the Reference Altitude in HH MM SS or HH MM SS.sss
*'''DEC Target J2000''': DEC coordinates of the object you want to reach the Reference Altitude in DD MM SS or DD MM SS.sss
*'''Start and End:''' Do the actions if the specified target's altitude is greater than or equal to the '''Start''' value and less than or equal to the '''End''' value in decimal degrees
*'''RoboClip:''' load RA and DEC from RoboClip catalog
*'''Coords From Sequence:''' load RA and DEC from a sequence file
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''DO IF ALTITUDE BETWEEN DYNAMIC TARGET :''' Do the actions if the altitude of a Dynamic Target is between the '''Start''' and '''End''' values (RA/DEC will be calculated in realtime using RoboOrbits):

[[File:Immagineefe.png]]

*'''Comet :''' open the Comet Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
*'''Asteroid :''' open the Asteroid Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
*'''Planet:''' open the Planet Finder in RoboOrbits, see more here
*'''Object Name :''' Read-only name of the Dynamic Target, coming from the search
*'''Object Key :''' Read-only key (code/number) of the Dynamic Target, coming from the search
*'''Object Dynamic Type :''' Read-only type of the Dynamic Target, coming from the search
*'''Start and End:''' Do the actions if the specified target's altitude is greater than or equal to the '''Start''' value and less than or equal to the '''End''' value in decimal degrees
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''DO IF AZIMUTH BETWEEN:''' Do the actions if the azimuth of a target specified by RA and DEC coordinates is between the '''Start''' and '''End''' values and the Altitude of the Target is above the minimum Altitude for slew set up in Voyager Mount setting (default is 0°)

[[File:DSDoIfAzimuth.png]]

*'''RA Target J2000''': RA coordinates of the object you want to reach the Reference Altitude in HH MM SS or HH MM SS.sss
*'''DEC Target J2000''': DEC coordinates of the object you want to reach the Reference Altitude in DD MM SS or DD MM SS.sss
*'''Start and End:''' Do the actions if the specified target's azimuth is greater than or equal to the '''Start''' value and less than or equal to the '''End''' value in decimal degrees. Also the Altitude of the target must be above the minimum for a slew like set tup in Voyager Mount setting (default is 0°)
*'''RoboClip:''' load RA and DEC from RoboClip catalog
*'''Coords From Sequence:''' load RA and DEC from a sequence file
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

{{Note|Remember that a Target can be in the right azimuth interval but can be upside down wiht negtive altitude. DO IF will be not executed if altitude of target are under the minimum altitude value accepted for a slew in Voyager mount setting}}

 
*'''DO IF AZIMUTH BETWEEN DYNAMIC TARGET :''' Do the actions if the azimuth of a Dynamic Target is between the '''Start''' and '''End''' values and the Altitude of the Target is above the minimum Altitude for slew set up in Voyager Mount setting (default is 0°) (RA/DEC will be calculated in realtime using RoboOrbits):

[[File:Immaginehh.png]]

*'''Comet :''' open the Comet Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
*'''Asteroid :''' open the Asteroid Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
*'''Planet:''' open the Planet Finder in RoboOrbits, see more here
*'''Object Name :''' Read-only name of the Dynamic Target, coming from the search
*'''Object Key :''' Read-only key (code/number) of the Dynamic Target, coming from the search
*'''Object Dynamic Type :''' Read-only type of the Dynamic Target, coming from the search
*'''Start and End:''' Do the actions if the specified target's azimuth is greater than or equal to the '''Start''' value and less than or equal to the '''End''' value in decimal degrees. Also the Altitude of the target must be above the minimum for a slew like set tup in Voyager Mount setting (default is 0°)
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''DO IF HA BETWEEN:''' Do the actions if the hour angle of the target (hours difference from the meridian) is between the specified start and end amounts [[File:Dragscript-doifha-2.1.7s.jpg]]
*'''RA Target J2000''': RA coordinates of the object whose hour angle we are testing, in HH MM SS or HH MM SS.sss
*'''DEC Target J2000''': DEC coordinates of the object whose hour angle we are testing, in DD MM SS or DD MM SS.sss
*'''Start and End:''' Do the actions if the specified target's HA (hour angle) is greater than or equal to the '''Start''' value and less than or equal to the '''End''' value in decimal hours. Note the values can be positive (after the meridian) or negative (before the meridian). The start to end can be both negative, both positive, or the start can be negative and the end can be positive. '''In all cases, the value must increase from start to end.'''
*'''RoboClip:''' load RA and DEC from RoboClip catalog
*'''Coords From Sequence:''' load RA and DEC from a sequence file
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 

*'''DO IF HA BETWEEN DYNAMIC TARGET :''' Do the actions if the hour angle of the Dynamic target (hours difference from the meridian) is between the specified start and end amounts (RA/DEC will be calculated in realtime using RoboOrbits):
*[[File:Immaginesf.png]]
*'''Comet :''' open the Comet Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
*'''Asteroid :''' open the Asteroid Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
*'''Object Name :''' Read-only name of the Dynamic Target, coming from the search
*'''Object Key :''' Read-only key (code/number) of the Dynamic Target, coming from the search
*'''Object Dynamic Type :''' Read-only type of the Dynamic Target, coming from the search
*'''Start and End:''' Do the actions if the specified target's HA (hour angle) is greater than or equal to the '''Start''' value and less than or equal to the '''End''' value in decimal hours. Note the values can be positive (after the meridian) or negative (before the meridian). The start to end can be both negative, both positive, or the start can be negative and the end can be positive. '''In all cases, the value must increase from start to end.'''
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''DO IF TIME BETWEEN''': Do the actions if the time is between the specified start and end times

[[File:Dragscript-do-if-time.png]]

*'''Start''': Beginning time of interval within which to do the following actions
*'''End''': End time of interval within which to do the following actions
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''DO IF DATE BETWEEN''': Do the actions at the indent level created by the DO statement if the date is between the start and end dates:

[[File:Dragscript-do-if-date.png]]

*'''Start''': Start date of the interval
*'''End''': End date of the interval
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''DO IF SQM''': Do the actions at the indent level created by the DO statement if the SQM value readed from control or Observing conditions is between the start and end dates:

[[File:DOIFSQM.png]]

*'''Reference Sky Quality''': reference value of Sky Quality to check
*'''Do If Actual value GREATER than or EQUAL [>=] to reference''': execute what is inside DO IF if the actual value >= that the reference value
*'''Do If Actual value LOWER than or EQUAL [<=] to reference''': execute what is inside DO IF if the actual value <= that the reference value
*'''Default''': use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''DO IF FOCAL LENGTH''': Do the actions at the indent level created by the DO statement if the FOCAL LENGTH readed from actual profile (Setup->Camera) is >=, <= or equal to reference value:

[[File:DoIfFocalLengthBlock.jpg]]

*'''Reference Focal Length''': reference value of Telescope Focal Length to check
*'''Do If Focal Length GREATER than or EQUAL [>=] to reference''': execute what is inside DO IF if the actual value >= that the reference value
*'''Do If Focal Length LOWER than or EQUAL [<=] to reference''': execute what is inside DO IF if the actual value <= that the reference value
*'''Do If Focal Length EQUAL [=] to reference''': execute what is inside DO IF if the actual value = that the reference value
*'''Default''': use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''DO IF DOME/ROOF OPEN''': Do the actions at the indent level created by the DO statement if the DOME/ROOF is opened
*'''DO IF DOME/ROOF CLOSED''': Do the actions at the indent level created by the DO statement if the DOME/ROOF is closed

{{Note|Status of DOME/ROOF will be read from the DOME Control configured in Voyager. This control is not absolutely reliable at 100%. Voyager cannot responding in anycase and any mode on damage derived from use of this conditional blocks. Please instead use the I/O card system with Viking management and physycal sensors to check the real status of your dome/roof.}}
*'''DO IF DISTRIBUITED SAFE END''': Wait the end of the night like defined in the Distribuited Safe block configuration. this is a features of the [https://software.starkeeper.it/voyager-plugins/ Distribuited Emergency plugin] dedicated to multi telscope in a single dome sharing emergency events
*'''DO IF EVEN DAY''': Decision block, true if the day of the month is an even number. Useful for example to do flat/calibration fit in different sets.
*'''DO IF ODD DAY:''' Decision block, true if the day of the month is an odd number. Useful for example to do flat/calibration fit in different sets.
*'''DO IF DAY OF WEEK:''' Decision block, true if the day of the week is one of those indicated in configuration (one or more day can be selected). Useful for example to do flat/calibration fit in different sets. Or doing some special task for copy file or etc etc
**[[File:Immaginewerwr.png]]

* '''DO IF PIER SIDE:''' Decision block, true if the pier side of the mount (what is reported by the connected driver) is equal to the parameter selected
**[[File:Immagineevveerv.png]]
** Pier West: mount before the meridian (or meridian passed but flip do not done)
** Pier East: mount after the meridian(meridian crossed and flip done) 
==='''Voyager Environment:'''===
Do the actions at the indent level created by the Decision block based on the Voyager internal status

*'''DO IF SETUP CONNECTED''': Do the actions if Voyager Setup is connected (from Startup menù or by DragScript connect block)
*'''DO IF SETUP DISCONNECTED''': Do the actions if Voyager Setup is not connected (from Startup menù or by DragScript disconnect block)

==='''Variable Check'''===
Do the actions at the indent level created by the DO IF statement based on the value of a variable. Variables must be declared before they can be tested in a DO IF statement

[[File:Decisions-variable-check.png]]
 

*'''DO IF COUNTER VALUE''': Check the value of a counter (integer) variable and do the following actions if the value of the counter meets the specified criteria:

[[File:Dragscript-do-if-counter.png]]

*'''Label''': Choose the counter variable to test from the drop-down list
*'''is Lower than''': Do the following actions if the selected counter value is less than the number in the counter field
*'''is Lower than or Equal to''': Do the following actions if the selected counter value is less than or equal to the number in the counter field
*'''is Equal to''': Do the following actions if the selected counter value is equal to the number in the counter field
*'''is Greater or Equal to:''' Do the following actions if the selected counter value is greater than or equal to the number in the counter field
*'''is Greater than:''' Do the following actions if the selected counter value is greater than the number in the counter field
*'''is Between:''' Do the following actions if the selected counter value is between the values in the two counter fields (greater than or equal to the left value AND less than or equal to the right field)
*'''is Not Equal''' to: Do the following actions if the selected counter value is not equal to the number in the counter field
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

**'''DO IF STRING VALUE''': Do the actions at the indent level created by the DO IF statement if a string variable is equal to, not equal to, or contains a specified string:

[[File:Dragscript-do-if-string.png]]

*'''Label''': Choose the string variable to test from the drop-down list
*'''is Equal to''': Do the following actions if the selected string value is equal to the specified string
*'''is Not Equal to''': Do the following actions if the selected string value is not equal to the specified string
*'''Contains''': Do the following actions if the selected string value contains the specified string
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 {{Note|String comparisons are case sensitive, i.e. TargetName is not equal to targetname}} 

*'''DO IF DECIMAL VALUE''': Do the actions at the indent level created by the DO IF statement if the value of the decimal number meets the specified criteria:

[[File:Do-if-decimal-value.png]]

*'''Label''': Choose the counter variable to test from the drop-down list
*'''is Lower than''': Do the following actions if the selected decimal number value is less than the number in the decimal number field
*'''is Lower than or Equal to''': Do the following actions if the selected decimal number value is less than or equal to the number in the decimal number field
*'''is Equal to''': Do the following actions if the selected decimal number value is equal to the number in the counter field
*'''is Greater or Equal to:''' Do the following actions if the selected decimal number value is greater than or equal to the number in the decimal number field
*'''is Greater than:''' Do the following actions if the selected decimal number value is greater than the number in the decimal number field
*'''is Between:''' Do the following actions if the selected decimal number value is between the values in the two decimal number fields (greater than or equal to the left value AND less than or equal to the right field)
*'''is Not Equal''' to: Do the following actions if the selected decimal number value is not equal to the number in the decimal number field
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

* '''DO IF COUNTER VALUE (Extended)''': Check the value of a counter (integer) variable and do the following actions if the value of the counter meets the specified criteria extended to a value, counter or decimal value:
** [[File:Immagineerfer.png]]
*** '''Counter''': Choose the counter variable to test from the drop-down list
***'''is Lower than''': Do the following actions if the selected counter value is less than the number in the counter field
***'''is Lower than or Equal to''': Do the following actions if the selected counter value is less than or equal to the number in the value field , counter variable or decimal variable
***'''is Equal to''': Do the following actions if the selected counter value is equal to the number in the value field , counter variable or decimal variable
***'''is Greater or Equal to:''' Do the following actions if the selected counter value is greater than or equal to the number in the value field , counter variable or decimal variable
***'''is Greater than:''' Do the following actions if the selected counter value is greater than the number in the value field , counter variable or decimal variable
***'''is Between:''' Do the following actions if the selected counter value is between the values in the value field , counter variable or decimal variable (greater than or equal to the left value AND less than or equal to the right field)
***'''is Not Equal''' to: Do the following actions if the selected counter value is not equal to the number in the value field , counter variable or decimal variable
***'''OK''': Save changes and close the window
***'''Cancel''': Discard changes and close the window 

'''DO IF DECIMAL VALUE (Extended)''': Check the value of a counter (integer) variable and do the following actions if the value of the counter meets the specified criteria extended to a value, counter or decimal value:
* [[File:Immaginee3fer.png]]
**'''Decimal Number''': Choose the decimal variable to test from the drop-down list
**'''is Lower than''': Do the following actions if the selected decimal value is less than the number in the counter field
**'''is Lower than or Equal to''': Do the following actions if the selected decimal value is less than or equal to the number in the value field , counter variable or decimal variable
**'''is Equal to''': Do the following actions if the selected decimal value is equal to the number in the value field , counter variable or decimal variable
**'''is Greater or Equal to:''' Do the following actions if the selected decimal value is greater than or equal to the number in the value field , counter variable or decimal variable
**'''is Greater than:''' Do the following actions if the selected decimal value is greater than the number in the value field , counter variable or decimal variable
**'''is Between:''' Do the following actions if the selected decimal value is between the values in the value field , counter variable or decimal variable (greater than or equal to the left value AND less than or equal to the right field)
**'''is Not Equal''' to: Do the following actions if the selected decimal value is not equal to the number in the value field , counter variable or decimal variable
**'''OK''': Save changes and close the window
**'''Cancel''': Discard changes and close the window

==Events==
DragScript execution can be suspended, terminated (exited) and resumed based on the occurrence of Emergency Exit, Emergency Suspend and Emergency Resume events.

The most common use of Events is together with a weather monitoring system, as configured in [[Weather Setup]]. You can specify at a detailed level which events should cause DragScript execution to SUSPEND (such as overcast clouds), EXIT (such as rain), or RESUME (such as clouds moving out so it becomes clear again).

In addition to weather events, you can raise Emergency Exit, Emergency Suspend and Emergency Resume events at any point in your DragScript.

When an Event is raised, control flow goes immediately to the appropriate block (Exit, Suspend or Resume) in the Events block of your DragScript. Create those blocks by dragging elements from the Events: Manage list.

[[File:Dragscript-events.png]]

==='''Manage'''===
See the [[DragScript Examples#Emergency Exit|DragScript Examples]] section to see how these blocks work in a DragScript.

*'''Emergency Exit''': Drag this element to the Events block of your DragScript. Then drag the actions you wish to take place when an Emergency Exit event is raised. For example, stop tracking, stop guiding, park your mount, and close the observatory roof
*'''Emergency Suspend''': Drag this element to the Events block of your DragScript. Then drag the actions you wish to take place when an Emergency Suspend event is raised. For example, stop tracking and stop guiding

[[File:Dragscript-suspend-2.png]]

*'''Wait Resume until absolute time''': If the time specified in HH MM SS is reached without an Emergency Resume event being raised, perform the action selected from the radio buttons in this dialog window
*'''Wait Resume for a time interval of:''' If the time period specified in HH MM SS elapses without an Emergency Resume event being raised, perform the action selected from the radio buttons in this dialog window
*'''Wait Resume until end of Astronomical Night''': If the end of Astronomical Night arrives without an Emergency Resume event being raised, perform the action selected from the radio buttons in this dialog window
*'''Wait Resume until end of Nautical Night''' : If the end of Nautical Night arrives without an Emergency Resume event being raised, perform the action selected from the radio buttons in this dialog window
*'''Wait Resume until end of Civil Night''': If the end of Civil Night arrives without an Emergency Resume event being raised, perform the action selected from the radio buttons in this dialog window
*{{Note|the various Wait Resume until end of xxxx Nights needed the specification on how to retrieve the data for the night (from Mount or by manual latitude and longitude) . }}
** '''Get Latitude and Longitude from Mount''': Retrieve the current latitude and longitude from the connected mount, which must support this command. This location is used, along with the current date, to determine the time that astronomical night begins and end. SETUP MUST BE CONNECTED TO WORK !
** '''Use the Latitude and Longitude indicated below''': Specify your current latitude and longitude in the fields below. This location is used, along with the current date, to determine the time that astronomical night begins and end
**
*'''Wait Resume Until Distribuited SAFE End [Distribuited Emergency Plugin Needed]:''' if selected Voyager will wait for resume according the SAFE END procedure of the Distribuited Emergency Plugin. A dedicated plugin for multi pier in a single building is needed https://software.starkeeper.it/voyager-plugins/
*'''On Resume Timeout End DragScript''': If the time specified above is reached without an Emergency Resume event occurring, end the DragScript
*'''On Resume Timeout Exec Emergency Exit Event''': If the time specified above is reached without an Emergency Resume event occurring, raise an Emergency Exit event
*'''On Resume Timeout Restart DragScript''': If the time specified above is reached without an Emergency Resume event occurring, Voyager will restart the DragScript form beginneng like a new running
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''Emergency Resume''': Execute these actions when an Emergency Resume event is raised. For example, start tracking and start guiding 

==='''Raise'''===
Raise an Emergency Exit, Suspend or Resume event

*'''Raise Emergency Exit Event''': Raise the Emergency Exit event. Execution of the DragScript will go immediately to the Emergency Exit block in the Events block
*'''Raise Emergency Suspend Event''': Raise the Emergency Suspend event. Execution of the DragScript will go immediately to the Emergency Suspend block in the Events block
*'''Raise Emergency Resume Event''': Raise the Emergency Resume event. Execution of the DragScript will go immediately to the Emergency Resume block in the Events block

==='''Remote'''===
Block for management of Distributed [https://wiki.starkeeper.it/index.php/Distributed_Emergency Distributed Emergency]

*'''Set Distributed Emergency Status''': Update overriding the internal Distributed Emergency Status for the Voyager Client connected to the selected value
**[[File:Des1.png]]
*'''Distributed Safe''': Distributed Safe wait the night like configured and in the night wait to have a Safe condition from the Emergency Event System (in Voyager is Weather, Safety Monitor, Viking I/O). If night is recognized and safe condition is true DragScript will exit from this block with OK result. If timeout is reached waiting DragScript will exit from this block with a TIMEOUT result. In case of error during waiting DragScript will exit with ERROR result. Checking the exit of block user can decide if inform all the client of a SAFE condition using the SET DISTRIBUTED EMERGENCY STATUS or restart the Master DragScript to wait for better conditions (same night or next night is automatically decided from DragScript). This block is usually associated and work only if you using the [https://wiki.starkeeper.it/index.php/Distributed_Emergency Distributed Emergency] plugin. Right and only place where to use is the Voyager MASTER of plugin where information is processed and emergency events checked.
**'''Important Note!''' Distributed Safe Cannot be used inside the Event Manager (Exit, Suspend, Resume)
***[[File:DES2.png]]
***'''NIGHT Configuration:''' data necessary to calculate the start and end interval of the actual night
****'''Night DATA:''' data about location of observatory
*****Latitude: Latitude of the Mount
*****Longitude: Longitude of the Mount
****'''Night TYPE:''' type of night to calculate. Astronomical, Nautical or Civil
****'''Night START OFFSET:''' apply an offset to the time start of the night
*****Offset Before: offset before the start in hours, minutes and seconds
*****Offset After: offset after the start in hours, minutes and seconds
****'''Night END OFFSET:''' apply an offset to the time end of the night
*****Offset Before: offset before the end in hours, minutes and seconds
*****Offset After: offset after the end in hours, minutes and seconds
****'''EVENT CHECK options:''' with this option you can decide to remove from processing status of SAFE some kind of events that will be ignored (event in any case are disable during the wait safe action)
*****'''Check Emergency Exit Status in SAFE status calculation:''' if unchecked the condition that throw an Emergency Status will be ignored in calculation of SAFE Staus . ATTENTION !! this is a way really dangerous for your setup .. use only if you want to wait safe in particular condition , particular timing and for particular tasks
*****'''Check Emergency SUSPEND Status in SAFE status calculation:''' if unchecked the condition that throw an Emergency Status will be ignored in calculation of SAFE Staus . ATTENTION !! this could be a way really dangerous for your setup .. use only if you want to wait safe in particular condition , particular timing and for particular tasks.
****'''LIGHT CONDITIONS options:''' with this option you can decide to remove from processing status of SAFE the LIGHT Conditions status
*****'''Remove Weather LIGHT Conditions Status From Calculation of All Emergency Status:''' if unchecked the LIGHT conditions from Weather system will be not used to calculate the SAFE Status. Usefull if you want to open the dome with the light approaching the night time and do skyflat. For the Dawn flat you can decide to disable the LIGHT event using dedicated block
****'''Default''': Use the default settings
****'''OK''': Save changes and close the window
****'''Cancel''': Discard changes and close the window

==='''Various'''===

*'''Resume from Block''': Resume execution starting with the specified block. This can only be placed in the Emergency Resume block in the Events block

[[File:Dragscript-resume-from-block.png]]

*'''Block''': Choose the block where execution should resume from the drop-down list
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Disable Events''': Disable event processing. Emergency Exit, Suspend and Resume events will be ignored

*'''Enable Events''': Enable event processing. Emergency Exit, Suspend and Resume events will be recognized and handled
*'''Disable Exit Event:''' Disable event processing. Emergency Exit only event will be ignored
*'''Enable Exit Event:''' Enable event processing. Emergency Exit event will be recognized and handled
*'''Disable Suspend Event:''' Disable event processing. Emergency Suspend and Resume only events will be ignored
*'''Enable Suspend Event:''' Enable event processing. Emergency Suspend and Resume only events will be recognized and handled
*'''Disable Weather Light Event:''' Disable event processing of Light conditions coming from Weather System. Status of Light will be not used to processing the Emergency Exit and/or Emergency Suspend or Emergency Resume events (Work only if you have a weather system configured in Voyager)
*'''Enable Weather Light Event:''' Enable event processing of Light conditions coming from Weather System. Status of Light will be used to processing the Emergency Exit and/or Emergency Suspend or Emergency Resume events (Work only if you have a weather system configured in Voyager)

{{Note|Enable and disable Events is a really powerful features !!! Please use with complete understand that if you forget to re-enable the events your setup can be damaged from weather conditions. }} 

{{Note|Enable and disable Light Conditions from emergency status calculation can be useful for do SkyFlat or generally other kind of tasks at dawn and dusk or for daylight operations and testing.}}

== Events Robotarget ==
If you are running a Voyager Advanced or Full version you can intercept the thrown events generated by RoboTarget Action during. This event can be annotations or errors. Data about are saved in the environment variables of DragScript and can be used in the signal block of DragScript. What is inside the Events RoboTarget Management will executed in seld contained DragScript ineriths by the actual DragScript eliminating all except what is in the events handle you have created.

To select the event handle and create it you must use the Operating Conditions blocks.

[[File:Immagineergerherherh.png]]

=== '''Operating Conditions''' ===
There is only one operating conditions block to handle a RoboTarget Event. The DO IF ROBOTARGER EVENT. You can use one or more of this block.

* '''DO IF ROBOTARGER EVENT''': Handle one or more events related to RoboTarget Action executing in a self contained ineriths dragscript the block inside the condition
* [[File:Immaginergerwerhgwrh.png]]

* '''Even(s) Selected''': select one or more RoboTarget events to handle
* '''Reset''': Uncheck all the events selected and remove from handling
* '''Cancel''': exit from configuration without save anything
* '''OK''': Save changes and close the window

==Block==
The Block element creates a new block in your DragScript. Drag and Drop it on a DragScript element that creates a new indent level, e.g. Script, DO IF, IF, Emergency Exit, Emergency Suspend, or Emergency Resume.

[[File:Dragscript-block.png]]

*'''Label''': Give your block a name. This name can be referenced by other script elements such as jumps and resumes
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

==Remark==
The Remark element adds a non-executable comment to your script for documentation purposes

[[File:Dragscript-remark.png]]

*'''Remark''': Enter a comment that will appear in your script
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 
==Flow==
Flow Control are useful for changin flow of execution during DragScript

[[File:DSFlowRestart.png]] 

* '''Exit Block:''' exit the current block container and execute the first following useful instruction
** must be used inside a BLOCK container
** cannot be used directly under the SCRIPT default block or EVENTS default block
** if nested inside more than one BLOCK container DragScript Engine will exit from the first BLOCK container parent
* '''Restart DragScript:''' The Restart DragScript element allow script to be restart from beginning, all the variable and status will be resetted

[[Category:DragScript]]
[[Category:All]]
[[Category:Manual|Ld]]

File:Immagineefe.png

2024-06-29T13:48:26Z

Leonardo: Leonardo uploaded a new version of File:Immagineefe.png

File:Immagineefe.png

2024-06-29T13:47:07Z

Leonardo: Leonardo uploaded a new version of File:Immagineefe.png

DragScript Flow of Control

2024-06-29T13:46:22Z

Leonardo: /* Operating Conditions: */

These DragScript elements control the flow of execution through your script. You can use the [[DragScript#DragScript Simulator|DragScript Simulator]] to test how control will flow when the DragScript actions complete with OK, ERROR or TIMEOUT status, and when Emergency Suspend, Resume and Exit events happen.

==Variables==
DragScript has several variable types: counters (integers), string variables and decimal numbers. They must be declared with the Counter, String or Decimal Number actions before they can be used. You can set and change their values, and then make decisions to execute DragScript actions based on their value. For example, you may build a script that runs from zero to ten sequences based on the value of a counter variable you set at the start of the script.

[[File:Dragscript-variables1.png]]

==='''Type'''===

*'''Counter''': Declare a counter (integer) variable and give it an initial value. You must declare a variable before using it

[[File:Dragscript-counter.png]]

*'''Label''': The name for this counter variable. There are no restrictions on length or legal characters, so just use something that makes sense for your control flow
*'''Init Value''': Initial value for the counter. Must be an integer between -2,000,000,000 and +2,000,000,000
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 

*'''String''': Declare a string variable and give it an initial value. You must declare a variable before using it

[[File:Dragscript-string.png]]

*'''Label''': The name for this string variable
*'''Init Value''': Initial value for the string
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 

*'''Decimal Number''': Declare a decimal number variable and give it an initial value. You must declare a variable before using it

[[File:Decimal-number.png]]

*'''Label''': The name for this decimal number variable
*'''Init Value''': Initial value for the decimal number - must be between the limits shown in the dialog box
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 

===Manage===

*'''Update''' '''Counter''': Update the value of a counter variable:

[[File:Dragscript-update-counter.png]]

*'''Counter''': Select the counter to update from the drop-down list. Counter variables must be declared with a Counter DragScript action before they can be updated
*'''Update Type''':
**'''Set to''': If selected, set the counter variable to the value in the Update Value field
**'''Offset by''': If selected, add the value in the Update Value field to the counter. The Update Value field can be negative or positive.
*'''Update Value''': A negative or positive integer value to either set the counter variable to or offset the counter variable by
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Update String''': Update the value of a string variable:

[[File:Dragscript-update-string.png]]

*'''String''': Select the string variable to update from the drop-down list
*'''Update Value''': Enter the new value for the string variable
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Update Decimal Number''': Update the value of a decimal number

[[File:Update-decimal-number.png]]

*'''Decimal Number''': Select the decimal number variable to update from the drop-down list
*'''Update Type''':
**'''Set to''': Set the decimal number value to the number in the Update Value field
**'''Offset by''': Add the +/- number in the Update Value field to the current value of the decimal number
*'''Update Value''': Enter the new value for the decimal number variable
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

* '''Update Decimal Number from Camera Temperature:''' Set the value of a decimal number from the temperature reported from Camera Driver:
* [[File:UpdateCameraTemp.png]]

* '''Decimal Number''': Select the decimal number variable to update from the drop-down list
* '''OK''': Save changes and close the window
* '''Cancel''': Discard changes and close the window 

*'''Update Decimal Number from Observing Conditions:''' Set the value of a decimal number from the observing conditions returned from I/O cards via Viking or from an ASCOM Observing Conditions driver:

[[File:Update-decimal-from-condx.png]]

*'''Decimal Number''': Select the decimal number variable to update from the drop-down list
*'''Observing Condition''': Select the observing condition whose value should be placed into the decimal number. These values come from [[Viking Setup|Viking]], a companion product from Starkeeper.it or from an ASCOM Observing Conditions driver
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''Update Decimal from Unix TimeStamp GMT:''' Set the value of a decimal number from the UNIX TimeStamp GMT based (seconds from 1/1/1970 UTC 0:0:0

[[File:Immaginergbrbrb.png]]

*'''Decimal Number''': Select the decimal number variable to update from the drop-down list
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Update Decimal Number from Focuser Temperature''': Set the value of a decimal number from the temperature returned by the focuser or auto-focus system

[[File:Update-decimal-from-focus-temp.png]]

*'''Decimal Number''': Select the decimal number variable to update from the drop-down list
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Update Decimal Number with Autofocus HFD''': Set the value of a decimal number with the final HFD (Half Flux Diameter) value from the last autofocus operation

[[File:Update-decimal-hfd.png]]

*'''Decimal Number''': Select the decimal number variable to update from the drop-down list
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window {{Note|At this time only RoboFire LocalField, RoboStar, and FocusMax return the HFD value - if you use a different autofocus routine, the HFD is not available}}

 

*'''Update Decimal from Focuser Position''': Set the value of a decimal number from the actual position returned by the RoboFire focuser

[[File:Update-decimal-from-focus-temp.png]]

*'''Decimal Number''': Select the decimal number variable to update from the drop-down list
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Update Decimal from Solved PA''': Set the value of a decimal number from the last solved PA returned by a Plate or Blind Solving action

[[File:UpdataFromPA.png]]

*'''Decimal Number''': Select the decimal number variable to update from the drop-down list
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''Update Decimal from Rotator PA''': Set the value of a decimal number from the Rotator PA returned by Rotator driver

[[File:UpdateRotPA.png]]

*'''Decimal Number''': Select the decimal number variable to update from the drop-down list
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Multiply Decimal Number''': Multiply a decimal number variable for the value in another variable of type counter or decimal or by direct value, the result will be stored in replace of actual value

[[File:DSMultiplyDecNum.png]]

*'''Decimal Number:''' Select the decimal number variable to multiply and update
*'''Multiply by Decimal Variable:''' Select the decimal number variable to use for multiply
*'''Multiply by Counter Variable:''' Select the counter variable to use for multiply
*'''Multiply by Value:''' Select the direct value to use for multipy
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

* '''Divide Decimal Number''': Divide a decimal number variable for the value in another variable of type counter or decimal or by direct value, the result will be stored in replace of actual value[[File:Immagineerfegwegwewegweg.png]]
** '''Decimal Number:''' Select the decimal number variable to divide and update
**'''Divide by Decimal Variable:''' Select the decimal number variable to use for divide
**'''Divide by Counter Variable:''' Select the counter variable to use for divide
**'''Divide by Value:''' Select the direct value to use for divide
**'''OK''': Save changes and close the window
**'''Cancel''': Discard changes and close the window

*'''Add to Decimal Number''': Add a decimal number variable for the value in another variable of type counter or decimal or by direct value, the result will be stored in replace of actual value[[File:Immaginevpomebmob.png]]
** '''Decimal Number:''' Select the decimal number variable to add and update
**'''Add by Decimal Variable:''' Select the decimal number variable to use for add
**'''Add by Counter Variable:''' Select the counter variable to use for add
**'''Add by Value:''' Select the direct value to use for add
**'''OK''': Save changes and close the window
**'''Cancel''': Discard changes and close the window

* '''Subtract to Decimal Number''': Subtract a decimal number variable for the value in another variable of type counter or decimal or by direct value, the result will be stored in replace of actual value[[File:Immagineiloiliolio.png]]
** '''Decimal Number:''' Select the decimal number variable to subtract and update
**'''Subtract by Decimal Variable:''' Select the decimal number variable to use for subtract
**'''Subtract by Counter Variable:''' Select the counter variable to use for subtract
**'''Subtract by Value:''' Select the direct value to use for subtract
**'''OK''': Save changes and close the window
**'''Cancel''': Discard changes and close the window

* '''Add to Counter''': Add a counter variable for the value in another variable of type counter or decimal or by direct value, the result will be stored in replace of actual value[[File:Immaginetntynty.png]]
** '''Counter:''' Select the counter variable to add and update
**'''Add Decimal Variable:''' Select the decimal number variable to use for add
**'''Add Counter Variable:''' Select the counter variable to use for add
**'''Add Value:''' Select the direct value to use for add
**'''OK''': Save changes and close the window
**'''Cancel''': Discard changes and close the window

*'''Subtract to Counter''': Subtract a counter variable for the value in another variable of type counter or decimal or by direct value, the result will be stored in replace of actual value[[File:Immaginedfdfbdf.png]]
** '''Counter:''' Select the counter variable to subtract and update
**'''Subtract Decimal Variable:''' Select the decimal number variable to use for subtract
**'''Subtract Counter Variable:''' Select the counter variable to use for subtract
**'''Subtract Value:''' Select the direct value to use for subtract
**'''OK''': Save changes and close the window
**'''Cancel''': Discard changes and close the window

==Jumps==
Jumps are used to goto a specified block of the DragScript. You can jump to the Start, End or a named Block.

[[File:Dragscript-jumps.png]]

*'''Goto Start''': Jump to the Start block of the script
*'''Goto Block''': Jump to a named block in the script

[[File:Dragscript-block-goto.png]]

*'''Block''': Select the named from the drop-down list, or type in the name of a block
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Goto End''': Jump to the End block of the script

==Repeats==
Repeats are used to execute a DragScript block a specified number of times, or until a specific time, or until astronomical night ends.

Repeats must be placed inside a block (note: Script: is a special block that contains the entire script.

If the result of evaluating a Repeat is to repeat the block, control returns to the block statement that contains the repeat.

[[File:Dragscript-repeats.png]]

*'''Repeat Block for n Times''': Repeat the containing block a specified number of times

[[File:Dragscript-repeat-block.png]]

*'''Times''': Number of times to repeat this block
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 

*'''Repeat Current Block Until Time''': Repeat the contained block until the specified time:

[[File:Dragscript-until-time.png]]

*'''Time''': Repeat the current block until this time
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 

*'''Repeat Block Until Astronomical/Nautical/Civil Night End''':

[[File:Dragscript-repeat-until-night-end.png]]

*'''Get Latitude and Longitude from Mount''': Retrieve the current latitude and longitude from the connected mount, which must support this command. This location is used, along with the current date, to determine the time that astronomical/nautical/civil night ends
*'''Use the Latitude and Longitude indicated below''': Specify your current latitude and longitude in the fields below. This location is used, along with the current date, to determine the time that astronomical/nautical/civil night ends
*'''Offset''': Time in HH MM SS
**'''Offset Before''': If selected, repeat the block until this amount of time before astronomical/nautical/civil night ends
**'''Offset After''': If selected, repeat the block this amount of time after astronomical/nautical/civil night ends
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 
**

{{Note|The time will be considered to have been reached if it is within 12 hours of the current time when the check is performed. E.g., if we set a repeat until 05:00, if it is 23:30 the repeat will be done since 23:30 is more than 12 hours in the future and less than 12 hours in the past, relative to 05:00. If it is 11:00, the repeat will be skipped, since 11:00 is later than 05:00 and more than 12 hours in the past.}} 
==Decisions==
Decisions control the flow of your DragScript based on the results of an action (OK, ERROR, TIMEOUT), operating conditions (current time, date or target altitude), or the value of a variable.

{{Note|A Decision element will create a new indent level in your DragScript. Drag new elements and drop them on the Decision element, or copy and paste them to it, to have their execution controlled by the result of the Decision}}

[[File:Dragscript-decisions-2.1.7s.jpg]]

==='''Action Results''':===
Do the actions at the indent level created by the Decision block based on the results of the action preceding the decision

**'''IF OK''': Do the actions following this statement if the result of the previous action was OK - meaning the action was successful
**'''IF ERROR''': Do the actions following this statement if the result of the previous action was ERROR - meaning the action failed
**'''IF TIMEOUT''': Do the actions following this statement if the result of the previous action was a TIMEOUT - meaning the action reached a specified timeout value without succeeding
**'''IF SKIPPED:''' Do the actions following this statement if the skipped status of the previuos action was SKIPPED - meaning the action not generate ERROR or finish OK just is SKIPPED because some constraints isnìt possible to match. At now only the Sequence Action use the SKIPPED status if time wait or time end or one of the constraints in azimuth, hour agle, alitute was thrown 

==='''Operating Conditions:'''===
Do the actions at the indent level created by the Decision block based on the time, date or target altitude

*'''DO IF ALTITUDE''': Do the actions if a target specified by RA and DEC coordinates has risen above or set below a specified altitude:

[[File:Dragscript-do-if-altitude.png]]

*'''RA Target J2000''': RA coordinates of the object you want to reach the Reference Altitude in HH MM SS or HH MM SS.sss
*'''DEC Target J2000''': DEC coordinates of the object you want to reach the Reference Altitude in DD MM SS or DD MM SS.sss
*'''Reference Altitude''': Altitude to reach in degrees
*'''Do If Actual Altitude GREATER than or EQUAL (>=) to reference''': Do the actions if the target has reached or risen above the reference altitude
*'''Do If Actual Altitude LOWER than or EQUAL (>=) to reference''': Do the actions if the target has reached or set below the reference altitude
*'''RoboClip:''' load RA and DEC from RoboClip catalog
*'''Coords From Sequence:''' load RA and DEC from a sequence file
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''DO IF ALTITUDE DYNAMIC TARGET''': Do the actions if a Dynamic Target has risen above or set below a specified altitude (RA/DEC will be calculated in realtime using RoboOrbits):

[[File:Immaginettg.png]]

* '''Comet :''' open the Comet Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
* '''Asteroid :''' open the Asteroid Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
* '''Planet:''' open the Planet Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
* '''Object Name :''' Read-only name of the Dynamic Target, coming from the search
* '''Object Key :''' Read-only key (code/number) of the Dynamic Target, coming from the search
* '''Object Dynamic Type :''' Read-only type of the Dynamic Target, coming from the search
*'''Reference Altitude''': Altitude to reach in degrees
*'''Do If Actual Altitude GREATER than or EQUAL (>=) to reference''': Do the actions if the target has reached or risen above the reference altitude
*'''Do If Actual Altitude LOWER than or EQUAL (>=) to reference''': Do the actions if the target has reached or set below the reference altitude
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''DO IF ALTITUDE BETWEEN:''' Do the actions if the altitude of a target specified by RA and DEC coordinates is between the '''Start''' and '''End''' values

[[File:Do-if-altitude-between.jpg]]

*'''RA Target J2000''': RA coordinates of the object you want to reach the Reference Altitude in HH MM SS or HH MM SS.sss
*'''DEC Target J2000''': DEC coordinates of the object you want to reach the Reference Altitude in DD MM SS or DD MM SS.sss
*'''Start and End:''' Do the actions if the specified target's altitude is greater than or equal to the '''Start''' value and less than or equal to the '''End''' value in decimal degrees
*'''RoboClip:''' load RA and DEC from RoboClip catalog
*'''Coords From Sequence:''' load RA and DEC from a sequence file
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''DO IF ALTITUDE BETWEEN DYNAMIC TARGET :''' Do the actions if the altitude of a Dynamic Target is between the '''Start''' and '''End''' values (RA/DEC will be calculated in realtime using RoboOrbits):

[[File:Immagineefe.png]]

*'''Comet :''' open the Comet Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
*'''Asteroid :''' open the Asteroid Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
*'''Object Name :''' Read-only name of the Dynamic Target, coming from the search
*'''Object Key :''' Read-only key (code/number) of the Dynamic Target, coming from the search
*'''Object Dynamic Type :''' Read-only type of the Dynamic Target, coming from the search
*'''Start and End:''' Do the actions if the specified target's altitude is greater than or equal to the '''Start''' value and less than or equal to the '''End''' value in decimal degrees
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''DO IF AZIMUTH BETWEEN:''' Do the actions if the azimuth of a target specified by RA and DEC coordinates is between the '''Start''' and '''End''' values and the Altitude of the Target is above the minimum Altitude for slew set up in Voyager Mount setting (default is 0°)

[[File:DSDoIfAzimuth.png]]

*'''RA Target J2000''': RA coordinates of the object you want to reach the Reference Altitude in HH MM SS or HH MM SS.sss
*'''DEC Target J2000''': DEC coordinates of the object you want to reach the Reference Altitude in DD MM SS or DD MM SS.sss
*'''Start and End:''' Do the actions if the specified target's azimuth is greater than or equal to the '''Start''' value and less than or equal to the '''End''' value in decimal degrees. Also the Altitude of the target must be above the minimum for a slew like set tup in Voyager Mount setting (default is 0°)
*'''RoboClip:''' load RA and DEC from RoboClip catalog
*'''Coords From Sequence:''' load RA and DEC from a sequence file
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

{{Note|Remember that a Target can be in the right azimuth interval but can be upside down wiht negtive altitude. DO IF will be not executed if altitude of target are under the minimum altitude value accepted for a slew in Voyager mount setting}}

 
*'''DO IF AZIMUTH BETWEEN DYNAMIC TARGET :''' Do the actions if the azimuth of a Dynamic Target is between the '''Start''' and '''End''' values and the Altitude of the Target is above the minimum Altitude for slew set up in Voyager Mount setting (default is 0°) (RA/DEC will be calculated in realtime using RoboOrbits):

[[File:Immaginehh.png]]

*'''Comet :''' open the Comet Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
*'''Asteroid :''' open the Asteroid Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
*'''Object Name :''' Read-only name of the Dynamic Target, coming from the search
*'''Object Key :''' Read-only key (code/number) of the Dynamic Target, coming from the search
*'''Object Dynamic Type :''' Read-only type of the Dynamic Target, coming from the search
*'''Start and End:''' Do the actions if the specified target's azimuth is greater than or equal to the '''Start''' value and less than or equal to the '''End''' value in decimal degrees. Also the Altitude of the target must be above the minimum for a slew like set tup in Voyager Mount setting (default is 0°)
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''DO IF HA BETWEEN:''' Do the actions if the hour angle of the target (hours difference from the meridian) is between the specified start and end amounts [[File:Dragscript-doifha-2.1.7s.jpg]]
*'''RA Target J2000''': RA coordinates of the object whose hour angle we are testing, in HH MM SS or HH MM SS.sss
*'''DEC Target J2000''': DEC coordinates of the object whose hour angle we are testing, in DD MM SS or DD MM SS.sss
*'''Start and End:''' Do the actions if the specified target's HA (hour angle) is greater than or equal to the '''Start''' value and less than or equal to the '''End''' value in decimal hours. Note the values can be positive (after the meridian) or negative (before the meridian). The start to end can be both negative, both positive, or the start can be negative and the end can be positive. '''In all cases, the value must increase from start to end.'''
*'''RoboClip:''' load RA and DEC from RoboClip catalog
*'''Coords From Sequence:''' load RA and DEC from a sequence file
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window 

*'''DO IF HA BETWEEN DYNAMIC TARGET :''' Do the actions if the hour angle of the Dynamic target (hours difference from the meridian) is between the specified start and end amounts (RA/DEC will be calculated in realtime using RoboOrbits):
*[[File:Immaginesf.png]]
*'''Comet :''' open the Comet Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
*'''Asteroid :''' open the Asteroid Finder in RoboOrbits, see more [[RoboOrbits Finders|here]]
*'''Object Name :''' Read-only name of the Dynamic Target, coming from the search
*'''Object Key :''' Read-only key (code/number) of the Dynamic Target, coming from the search
*'''Object Dynamic Type :''' Read-only type of the Dynamic Target, coming from the search
*'''Start and End:''' Do the actions if the specified target's HA (hour angle) is greater than or equal to the '''Start''' value and less than or equal to the '''End''' value in decimal hours. Note the values can be positive (after the meridian) or negative (before the meridian). The start to end can be both negative, both positive, or the start can be negative and the end can be positive. '''In all cases, the value must increase from start to end.'''
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''DO IF TIME BETWEEN''': Do the actions if the time is between the specified start and end times

[[File:Dragscript-do-if-time.png]]

*'''Start''': Beginning time of interval within which to do the following actions
*'''End''': End time of interval within which to do the following actions
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''DO IF DATE BETWEEN''': Do the actions at the indent level created by the DO statement if the date is between the start and end dates:

[[File:Dragscript-do-if-date.png]]

*'''Start''': Start date of the interval
*'''End''': End date of the interval
*'''Default''': Use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''DO IF SQM''': Do the actions at the indent level created by the DO statement if the SQM value readed from control or Observing conditions is between the start and end dates:

[[File:DOIFSQM.png]]

*'''Reference Sky Quality''': reference value of Sky Quality to check
*'''Do If Actual value GREATER than or EQUAL [>=] to reference''': execute what is inside DO IF if the actual value >= that the reference value
*'''Do If Actual value LOWER than or EQUAL [<=] to reference''': execute what is inside DO IF if the actual value <= that the reference value
*'''Default''': use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''DO IF FOCAL LENGTH''': Do the actions at the indent level created by the DO statement if the FOCAL LENGTH readed from actual profile (Setup->Camera) is >=, <= or equal to reference value:

[[File:DoIfFocalLengthBlock.jpg]]

*'''Reference Focal Length''': reference value of Telescope Focal Length to check
*'''Do If Focal Length GREATER than or EQUAL [>=] to reference''': execute what is inside DO IF if the actual value >= that the reference value
*'''Do If Focal Length LOWER than or EQUAL [<=] to reference''': execute what is inside DO IF if the actual value <= that the reference value
*'''Do If Focal Length EQUAL [=] to reference''': execute what is inside DO IF if the actual value = that the reference value
*'''Default''': use the default settings
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''DO IF DOME/ROOF OPEN''': Do the actions at the indent level created by the DO statement if the DOME/ROOF is opened
*'''DO IF DOME/ROOF CLOSED''': Do the actions at the indent level created by the DO statement if the DOME/ROOF is closed

{{Note|Status of DOME/ROOF will be read from the DOME Control configured in Voyager. This control is not absolutely reliable at 100%. Voyager cannot responding in anycase and any mode on damage derived from use of this conditional blocks. Please instead use the I/O card system with Viking management and physycal sensors to check the real status of your dome/roof.}}
*'''DO IF DISTRIBUITED SAFE END''': Wait the end of the night like defined in the Distribuited Safe block configuration. this is a features of the [https://software.starkeeper.it/voyager-plugins/ Distribuited Emergency plugin] dedicated to multi telscope in a single dome sharing emergency events
*'''DO IF EVEN DAY''': Decision block, true if the day of the month is an even number. Useful for example to do flat/calibration fit in different sets.
*'''DO IF ODD DAY:''' Decision block, true if the day of the month is an odd number. Useful for example to do flat/calibration fit in different sets.
*'''DO IF DAY OF WEEK:''' Decision block, true if the day of the week is one of those indicated in configuration (one or more day can be selected). Useful for example to do flat/calibration fit in different sets. Or doing some special task for copy file or etc etc
**[[File:Immaginewerwr.png]]

* '''DO IF PIER SIDE:''' Decision block, true if the pier side of the mount (what is reported by the connected driver) is equal to the parameter selected
**[[File:Immagineevveerv.png]]
** Pier West: mount before the meridian (or meridian passed but flip do not done)
** Pier East: mount after the meridian(meridian crossed and flip done) 
==='''Voyager Environment:'''===
Do the actions at the indent level created by the Decision block based on the Voyager internal status

*'''DO IF SETUP CONNECTED''': Do the actions if Voyager Setup is connected (from Startup menù or by DragScript connect block)
*'''DO IF SETUP DISCONNECTED''': Do the actions if Voyager Setup is not connected (from Startup menù or by DragScript disconnect block)

==='''Variable Check'''===
Do the actions at the indent level created by the DO IF statement based on the value of a variable. Variables must be declared before they can be tested in a DO IF statement

[[File:Decisions-variable-check.png]]
 

*'''DO IF COUNTER VALUE''': Check the value of a counter (integer) variable and do the following actions if the value of the counter meets the specified criteria:

[[File:Dragscript-do-if-counter.png]]

*'''Label''': Choose the counter variable to test from the drop-down list
*'''is Lower than''': Do the following actions if the selected counter value is less than the number in the counter field
*'''is Lower than or Equal to''': Do the following actions if the selected counter value is less than or equal to the number in the counter field
*'''is Equal to''': Do the following actions if the selected counter value is equal to the number in the counter field
*'''is Greater or Equal to:''' Do the following actions if the selected counter value is greater than or equal to the number in the counter field
*'''is Greater than:''' Do the following actions if the selected counter value is greater than the number in the counter field
*'''is Between:''' Do the following actions if the selected counter value is between the values in the two counter fields (greater than or equal to the left value AND less than or equal to the right field)
*'''is Not Equal''' to: Do the following actions if the selected counter value is not equal to the number in the counter field
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

**'''DO IF STRING VALUE''': Do the actions at the indent level created by the DO IF statement if a string variable is equal to, not equal to, or contains a specified string:

[[File:Dragscript-do-if-string.png]]

*'''Label''': Choose the string variable to test from the drop-down list
*'''is Equal to''': Do the following actions if the selected string value is equal to the specified string
*'''is Not Equal to''': Do the following actions if the selected string value is not equal to the specified string
*'''Contains''': Do the following actions if the selected string value contains the specified string
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 {{Note|String comparisons are case sensitive, i.e. TargetName is not equal to targetname}} 

*'''DO IF DECIMAL VALUE''': Do the actions at the indent level created by the DO IF statement if the value of the decimal number meets the specified criteria:

[[File:Do-if-decimal-value.png]]

*'''Label''': Choose the counter variable to test from the drop-down list
*'''is Lower than''': Do the following actions if the selected decimal number value is less than the number in the decimal number field
*'''is Lower than or Equal to''': Do the following actions if the selected decimal number value is less than or equal to the number in the decimal number field
*'''is Equal to''': Do the following actions if the selected decimal number value is equal to the number in the counter field
*'''is Greater or Equal to:''' Do the following actions if the selected decimal number value is greater than or equal to the number in the decimal number field
*'''is Greater than:''' Do the following actions if the selected decimal number value is greater than the number in the decimal number field
*'''is Between:''' Do the following actions if the selected decimal number value is between the values in the two decimal number fields (greater than or equal to the left value AND less than or equal to the right field)
*'''is Not Equal''' to: Do the following actions if the selected decimal number value is not equal to the number in the decimal number field
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

* '''DO IF COUNTER VALUE (Extended)''': Check the value of a counter (integer) variable and do the following actions if the value of the counter meets the specified criteria extended to a value, counter or decimal value:
** [[File:Immagineerfer.png]]
*** '''Counter''': Choose the counter variable to test from the drop-down list
***'''is Lower than''': Do the following actions if the selected counter value is less than the number in the counter field
***'''is Lower than or Equal to''': Do the following actions if the selected counter value is less than or equal to the number in the value field , counter variable or decimal variable
***'''is Equal to''': Do the following actions if the selected counter value is equal to the number in the value field , counter variable or decimal variable
***'''is Greater or Equal to:''' Do the following actions if the selected counter value is greater than or equal to the number in the value field , counter variable or decimal variable
***'''is Greater than:''' Do the following actions if the selected counter value is greater than the number in the value field , counter variable or decimal variable
***'''is Between:''' Do the following actions if the selected counter value is between the values in the value field , counter variable or decimal variable (greater than or equal to the left value AND less than or equal to the right field)
***'''is Not Equal''' to: Do the following actions if the selected counter value is not equal to the number in the value field , counter variable or decimal variable
***'''OK''': Save changes and close the window
***'''Cancel''': Discard changes and close the window 

'''DO IF DECIMAL VALUE (Extended)''': Check the value of a counter (integer) variable and do the following actions if the value of the counter meets the specified criteria extended to a value, counter or decimal value:
* [[File:Immaginee3fer.png]]
**'''Decimal Number''': Choose the decimal variable to test from the drop-down list
**'''is Lower than''': Do the following actions if the selected decimal value is less than the number in the counter field
**'''is Lower than or Equal to''': Do the following actions if the selected decimal value is less than or equal to the number in the value field , counter variable or decimal variable
**'''is Equal to''': Do the following actions if the selected decimal value is equal to the number in the value field , counter variable or decimal variable
**'''is Greater or Equal to:''' Do the following actions if the selected decimal value is greater than or equal to the number in the value field , counter variable or decimal variable
**'''is Greater than:''' Do the following actions if the selected decimal value is greater than the number in the value field , counter variable or decimal variable
**'''is Between:''' Do the following actions if the selected decimal value is between the values in the value field , counter variable or decimal variable (greater than or equal to the left value AND less than or equal to the right field)
**'''is Not Equal''' to: Do the following actions if the selected decimal value is not equal to the number in the value field , counter variable or decimal variable
**'''OK''': Save changes and close the window
**'''Cancel''': Discard changes and close the window

==Events==
DragScript execution can be suspended, terminated (exited) and resumed based on the occurrence of Emergency Exit, Emergency Suspend and Emergency Resume events.

The most common use of Events is together with a weather monitoring system, as configured in [[Weather Setup]]. You can specify at a detailed level which events should cause DragScript execution to SUSPEND (such as overcast clouds), EXIT (such as rain), or RESUME (such as clouds moving out so it becomes clear again).

In addition to weather events, you can raise Emergency Exit, Emergency Suspend and Emergency Resume events at any point in your DragScript.

When an Event is raised, control flow goes immediately to the appropriate block (Exit, Suspend or Resume) in the Events block of your DragScript. Create those blocks by dragging elements from the Events: Manage list.

[[File:Dragscript-events.png]]

==='''Manage'''===
See the [[DragScript Examples#Emergency Exit|DragScript Examples]] section to see how these blocks work in a DragScript.

*'''Emergency Exit''': Drag this element to the Events block of your DragScript. Then drag the actions you wish to take place when an Emergency Exit event is raised. For example, stop tracking, stop guiding, park your mount, and close the observatory roof
*'''Emergency Suspend''': Drag this element to the Events block of your DragScript. Then drag the actions you wish to take place when an Emergency Suspend event is raised. For example, stop tracking and stop guiding

[[File:Dragscript-suspend-2.png]]

*'''Wait Resume until absolute time''': If the time specified in HH MM SS is reached without an Emergency Resume event being raised, perform the action selected from the radio buttons in this dialog window
*'''Wait Resume for a time interval of:''' If the time period specified in HH MM SS elapses without an Emergency Resume event being raised, perform the action selected from the radio buttons in this dialog window
*'''Wait Resume until end of Astronomical Night''': If the end of Astronomical Night arrives without an Emergency Resume event being raised, perform the action selected from the radio buttons in this dialog window
*'''Wait Resume until end of Nautical Night''' : If the end of Nautical Night arrives without an Emergency Resume event being raised, perform the action selected from the radio buttons in this dialog window
*'''Wait Resume until end of Civil Night''': If the end of Civil Night arrives without an Emergency Resume event being raised, perform the action selected from the radio buttons in this dialog window
*{{Note|the various Wait Resume until end of xxxx Nights needed the specification on how to retrieve the data for the night (from Mount or by manual latitude and longitude) . }}
** '''Get Latitude and Longitude from Mount''': Retrieve the current latitude and longitude from the connected mount, which must support this command. This location is used, along with the current date, to determine the time that astronomical night begins and end. SETUP MUST BE CONNECTED TO WORK !
** '''Use the Latitude and Longitude indicated below''': Specify your current latitude and longitude in the fields below. This location is used, along with the current date, to determine the time that astronomical night begins and end
**
*'''Wait Resume Until Distribuited SAFE End [Distribuited Emergency Plugin Needed]:''' if selected Voyager will wait for resume according the SAFE END procedure of the Distribuited Emergency Plugin. A dedicated plugin for multi pier in a single building is needed https://software.starkeeper.it/voyager-plugins/
*'''On Resume Timeout End DragScript''': If the time specified above is reached without an Emergency Resume event occurring, end the DragScript
*'''On Resume Timeout Exec Emergency Exit Event''': If the time specified above is reached without an Emergency Resume event occurring, raise an Emergency Exit event
*'''On Resume Timeout Restart DragScript''': If the time specified above is reached without an Emergency Resume event occurring, Voyager will restart the DragScript form beginneng like a new running
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

*'''Emergency Resume''': Execute these actions when an Emergency Resume event is raised. For example, start tracking and start guiding 

==='''Raise'''===
Raise an Emergency Exit, Suspend or Resume event

*'''Raise Emergency Exit Event''': Raise the Emergency Exit event. Execution of the DragScript will go immediately to the Emergency Exit block in the Events block
*'''Raise Emergency Suspend Event''': Raise the Emergency Suspend event. Execution of the DragScript will go immediately to the Emergency Suspend block in the Events block
*'''Raise Emergency Resume Event''': Raise the Emergency Resume event. Execution of the DragScript will go immediately to the Emergency Resume block in the Events block

==='''Remote'''===
Block for management of Distributed [https://wiki.starkeeper.it/index.php/Distributed_Emergency Distributed Emergency]

*'''Set Distributed Emergency Status''': Update overriding the internal Distributed Emergency Status for the Voyager Client connected to the selected value
**[[File:Des1.png]]
*'''Distributed Safe''': Distributed Safe wait the night like configured and in the night wait to have a Safe condition from the Emergency Event System (in Voyager is Weather, Safety Monitor, Viking I/O). If night is recognized and safe condition is true DragScript will exit from this block with OK result. If timeout is reached waiting DragScript will exit from this block with a TIMEOUT result. In case of error during waiting DragScript will exit with ERROR result. Checking the exit of block user can decide if inform all the client of a SAFE condition using the SET DISTRIBUTED EMERGENCY STATUS or restart the Master DragScript to wait for better conditions (same night or next night is automatically decided from DragScript). This block is usually associated and work only if you using the [https://wiki.starkeeper.it/index.php/Distributed_Emergency Distributed Emergency] plugin. Right and only place where to use is the Voyager MASTER of plugin where information is processed and emergency events checked.
**'''Important Note!''' Distributed Safe Cannot be used inside the Event Manager (Exit, Suspend, Resume)
***[[File:DES2.png]]
***'''NIGHT Configuration:''' data necessary to calculate the start and end interval of the actual night
****'''Night DATA:''' data about location of observatory
*****Latitude: Latitude of the Mount
*****Longitude: Longitude of the Mount
****'''Night TYPE:''' type of night to calculate. Astronomical, Nautical or Civil
****'''Night START OFFSET:''' apply an offset to the time start of the night
*****Offset Before: offset before the start in hours, minutes and seconds
*****Offset After: offset after the start in hours, minutes and seconds
****'''Night END OFFSET:''' apply an offset to the time end of the night
*****Offset Before: offset before the end in hours, minutes and seconds
*****Offset After: offset after the end in hours, minutes and seconds
****'''EVENT CHECK options:''' with this option you can decide to remove from processing status of SAFE some kind of events that will be ignored (event in any case are disable during the wait safe action)
*****'''Check Emergency Exit Status in SAFE status calculation:''' if unchecked the condition that throw an Emergency Status will be ignored in calculation of SAFE Staus . ATTENTION !! this is a way really dangerous for your setup .. use only if you want to wait safe in particular condition , particular timing and for particular tasks
*****'''Check Emergency SUSPEND Status in SAFE status calculation:''' if unchecked the condition that throw an Emergency Status will be ignored in calculation of SAFE Staus . ATTENTION !! this could be a way really dangerous for your setup .. use only if you want to wait safe in particular condition , particular timing and for particular tasks.
****'''LIGHT CONDITIONS options:''' with this option you can decide to remove from processing status of SAFE the LIGHT Conditions status
*****'''Remove Weather LIGHT Conditions Status From Calculation of All Emergency Status:''' if unchecked the LIGHT conditions from Weather system will be not used to calculate the SAFE Status. Usefull if you want to open the dome with the light approaching the night time and do skyflat. For the Dawn flat you can decide to disable the LIGHT event using dedicated block
****'''Default''': Use the default settings
****'''OK''': Save changes and close the window
****'''Cancel''': Discard changes and close the window

==='''Various'''===

*'''Resume from Block''': Resume execution starting with the specified block. This can only be placed in the Emergency Resume block in the Events block

[[File:Dragscript-resume-from-block.png]]

*'''Block''': Choose the block where execution should resume from the drop-down list
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 

*'''Disable Events''': Disable event processing. Emergency Exit, Suspend and Resume events will be ignored

*'''Enable Events''': Enable event processing. Emergency Exit, Suspend and Resume events will be recognized and handled
*'''Disable Exit Event:''' Disable event processing. Emergency Exit only event will be ignored
*'''Enable Exit Event:''' Enable event processing. Emergency Exit event will be recognized and handled
*'''Disable Suspend Event:''' Disable event processing. Emergency Suspend and Resume only events will be ignored
*'''Enable Suspend Event:''' Enable event processing. Emergency Suspend and Resume only events will be recognized and handled
*'''Disable Weather Light Event:''' Disable event processing of Light conditions coming from Weather System. Status of Light will be not used to processing the Emergency Exit and/or Emergency Suspend or Emergency Resume events (Work only if you have a weather system configured in Voyager)
*'''Enable Weather Light Event:''' Enable event processing of Light conditions coming from Weather System. Status of Light will be used to processing the Emergency Exit and/or Emergency Suspend or Emergency Resume events (Work only if you have a weather system configured in Voyager)

{{Note|Enable and disable Events is a really powerful features !!! Please use with complete understand that if you forget to re-enable the events your setup can be damaged from weather conditions. }} 

{{Note|Enable and disable Light Conditions from emergency status calculation can be useful for do SkyFlat or generally other kind of tasks at dawn and dusk or for daylight operations and testing.}}

== Events Robotarget ==
If you are running a Voyager Advanced or Full version you can intercept the thrown events generated by RoboTarget Action during. This event can be annotations or errors. Data about are saved in the environment variables of DragScript and can be used in the signal block of DragScript. What is inside the Events RoboTarget Management will executed in seld contained DragScript ineriths by the actual DragScript eliminating all except what is in the events handle you have created.

To select the event handle and create it you must use the Operating Conditions blocks.

[[File:Immagineergerherherh.png]]

=== '''Operating Conditions''' ===
There is only one operating conditions block to handle a RoboTarget Event. The DO IF ROBOTARGER EVENT. You can use one or more of this block.

* '''DO IF ROBOTARGER EVENT''': Handle one or more events related to RoboTarget Action executing in a self contained ineriths dragscript the block inside the condition
* [[File:Immaginergerwerhgwrh.png]]

* '''Even(s) Selected''': select one or more RoboTarget events to handle
* '''Reset''': Uncheck all the events selected and remove from handling
* '''Cancel''': exit from configuration without save anything
* '''OK''': Save changes and close the window

==Block==
The Block element creates a new block in your DragScript. Drag and Drop it on a DragScript element that creates a new indent level, e.g. Script, DO IF, IF, Emergency Exit, Emergency Suspend, or Emergency Resume.

[[File:Dragscript-block.png]]

*'''Label''': Give your block a name. This name can be referenced by other script elements such as jumps and resumes
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

==Remark==
The Remark element adds a non-executable comment to your script for documentation purposes

[[File:Dragscript-remark.png]]

*'''Remark''': Enter a comment that will appear in your script
*'''OK''': Save changes and close the window
*'''Cancel''': Discard changes and close the window

 
==Flow==
Flow Control are useful for changin flow of execution during DragScript

[[File:DSFlowRestart.png]] 

* '''Exit Block:''' exit the current block container and execute the first following useful instruction
** must be used inside a BLOCK container
** cannot be used directly under the SCRIPT default block or EVENTS default block
** if nested inside more than one BLOCK container DragScript Engine will exit from the first BLOCK container parent
* '''Restart DragScript:''' The Restart DragScript element allow script to be restart from beginning, all the variable and status will be resetted

[[Category:DragScript]]
[[Category:All]]
[[Category:Manual|Ld]]

File:Immaginettg.png

2024-06-29T13:45:07Z

Leonardo: Leonardo uploaded a new version of File:Immaginettg.png

RoboOrbits Finders

2024-06-29T13:42:38Z

Leonardo: /* Planets Finder */

==What is RoboOrbits Finders==
Finders are forms for searching data related to Dynamic Targets in the RoboOrbits database.

There is a finder for each type of Dynamic Target, from a finder you don't have access to the data of other types of Dynamic Target.

For opening the Finder, where possible, there are dedicated buttons with text that recalls the type of Dynamic Target that can be searched.

[[File:Immaginecc.png]]

Thanks to the Finder it will be possible to carry out more or less in-depth searches in the RoboOrbits database, calculate the current position of the Target and view its orbital data including transit data.

{{note|In order to calculate the position of the Dynamic Target in real time it is necessary that Voyager has access to the data of the location of the mount through the mount or through the fixed parameters in the setup of Voyager or thanks to the use of the new system of cache of the Location introduced with the Voyager version 2.3.8b. Without latitude, longitude and elevation data it will only be possible to view the orbital parameters and a few other information.}}Please configure Location source [[Mount Setup#Latitude .2F Longitude .2FElevation -.3E Source|here]] . More info about Voyager Location Cache [https://wiki.starkeeper.it/index.php/Mount_Setup#Voyager_Location_Cache_Manager here]. {{note|Finders will not work until you download and import the data into RoboOrbits. The RoboOrbits database is in fact empty upon first installation. The data is not included in Voyager.}}
==Comets Finder==
Comets Finder allow user to search for comets object in the RoboOrbits database. Search will be done in what is actually stored and not online. If you want you can update before the Comets database from online data.

[[File:Immagineww.png]]

* '''Find Comets :''' entering the text to search
**'''Find :''' run the search. Will be found comets which designation name or number start, contains or match with the text.
**'''Red X Button :''' will reset the search fields and the search results and data
* '''Search Results :''' where is showed the list of object found with the target number/code and the Designation Name order in alfabetical order. Double click on the interest row to select the object and to close the Finder and report the calculated coordinates to the caller. Single click on the interest row to show the orbital data and the processed data
* '''Data About Selected Object - NOW :''' contains all the data about the selected row with calculation about actual location and transit info if the Voyager Location cache is valorized and valid (see [https://wiki.starkeeper.it/index.php/Mount_Setup#Voyager_Location_Cache_Manager here]). All the calculation and processing is done on the actual date time , time zone and latitude, longitude and elevation reported onthe little status bar on bottom of the finder
* '''Copy RA/DEC :''' copy to the clipboard the infor about actual RA/DEC of the target selected, you can paste in other Voyager forms where you have the Paste RA/DEC buttons
* '''Use this Object :''' click on this button to close the Finder and report the calculated coordinates to the caller.

A red background on the Transit Time field in the Processed data means the object will never be visible:

[[File:Immaginegg.png]]

{{note|If the Voyager Location Cache is empty transit / actual location and others data field will be blank. Connect at least one time the mount or use fidex value configuration to obtain the dynamic informations about the selected object.}}

==Asteroids Finder==
Asteroids Finder allow user to search for asteroids object in the RoboOrbits database. Search will be done in what is actually stored and not online. If you want you can update before the Asteroids database from online data.

[[File:Immagineoo.png]]

* '''Find Asteroids :''' entering the text to search
**'''Fast Find :''' run the search. Will be found asteroids which designation name or number start or match with the text. This is a fast search.
**'''Deep Find :''' run the serarch. Will be found asteroids which designation name or number start, contains or match with the text. This is a deep search and the time needed depends on your CPU power.
**'''Red X Button :''' will reset the search fields and the search results and data
*'''Search Results :''' where is showed the list of object found with the target number/code and the Designation Name order in alfabetical order. Double click on the interest row to select the object and to close the Finder and report the calculated coordinates to the caller. Single click on the interest row to show the orbital data and the processed data
*'''Data About Selected Object - NOW :''' contains all the data about the selected row with calculation about actual location and transit info if the Voyager Location cache is valorized and valid (see [https://wiki.starkeeper.it/index.php/Mount_Setup#Voyager_Location_Cache_Manager here]). All the calculation and processing is done on the actual date time , time zone and latitude, longitude and elevation reported onthe little status bar on bottom of the finder
*'''Copy RA/DEC :''' copy to the clipboard the infor about actual RA/DEC of the target selected, you can paste in other Voyager forms where you have the Paste RA/DEC buttons
*'''Use this Object :''' click on this button to close the Finder and report the calculated coordinates to the caller.

A red background on the Transit Time field in the Processed data means the object will never be visible:

[[File:Immaginegg.png|link=https://wiki.starkeeper.it/index.php/File:Immaginegg.png]]

{{note|If the Voyager Location Cache is empty the transit / actual location and others data field will be blank. Connect at least one time the mount or use fidex value configuration to obtain the dynamic informations about the selected object.}}

==Planets Finder==
PlanetsFinder allow user to search for planet object in the RoboOrbits database. Search will be done in what is actually stored and not online. It is not needed to update the data about because the planets data are embedded in Voyager application

[[File:Immaginexcv.png]]

*'''Planets List:''' Double click to select the planet and calculate the actual position
*'''Data About Selected Planet - NOW :''' contains all the data about the selected row with calculation about actual location and transit info if the Voyager Location cache is valorized and valid (see [https://wiki.starkeeper.it/index.php/Mount_Setup#Voyager_Location_Cache_Manager here]). All the calculation and processing is done on the actual date time , time zone and latitude, longitude and elevation reported onthe little status bar on bottom of the finder
*'''Copy RA/DEC :''' copy to the clipboard the infor about actual RA/DEC of the target selected, you can paste in other Voyager forms where you have the Paste RA/DEC buttons
*'''Use this Object :''' click on this button to close the Finder and report the calculated coordinates to the caller.

A red background on the Transit Time field in the Processed data means the object will never be visible:

[[File:Immaginegg.png|link=https://wiki.starkeeper.it/index.php/File:Immaginegg.png]]

{{note|Ephemeris Calculation are accurated only fort the actual position, for future time the values can be affected by a various arcmin errors}}
[[Category:RoboOrbits]]
[[Category:All]]
[[Category:Manual|Ro]]

RoboOrbits Finders

2024-06-29T13:41:20Z

Leonardo: /* Asteroids Finder */

==What is RoboOrbits Finders==
Finders are forms for searching data related to Dynamic Targets in the RoboOrbits database.

There is a finder for each type of Dynamic Target, from a finder you don't have access to the data of other types of Dynamic Target.

For opening the Finder, where possible, there are dedicated buttons with text that recalls the type of Dynamic Target that can be searched.

[[File:Immaginecc.png]]

Thanks to the Finder it will be possible to carry out more or less in-depth searches in the RoboOrbits database, calculate the current position of the Target and view its orbital data including transit data.

{{note|In order to calculate the position of the Dynamic Target in real time it is necessary that Voyager has access to the data of the location of the mount through the mount or through the fixed parameters in the setup of Voyager or thanks to the use of the new system of cache of the Location introduced with the Voyager version 2.3.8b. Without latitude, longitude and elevation data it will only be possible to view the orbital parameters and a few other information.}}Please configure Location source [[Mount Setup#Latitude .2F Longitude .2FElevation -.3E Source|here]] . More info about Voyager Location Cache [https://wiki.starkeeper.it/index.php/Mount_Setup#Voyager_Location_Cache_Manager here]. {{note|Finders will not work until you download and import the data into RoboOrbits. The RoboOrbits database is in fact empty upon first installation. The data is not included in Voyager.}}
==Comets Finder==
Comets Finder allow user to search for comets object in the RoboOrbits database. Search will be done in what is actually stored and not online. If you want you can update before the Comets database from online data.

[[File:Immagineww.png]]

* '''Find Comets :''' entering the text to search
**'''Find :''' run the search. Will be found comets which designation name or number start, contains or match with the text.
**'''Red X Button :''' will reset the search fields and the search results and data
* '''Search Results :''' where is showed the list of object found with the target number/code and the Designation Name order in alfabetical order. Double click on the interest row to select the object and to close the Finder and report the calculated coordinates to the caller. Single click on the interest row to show the orbital data and the processed data
* '''Data About Selected Object - NOW :''' contains all the data about the selected row with calculation about actual location and transit info if the Voyager Location cache is valorized and valid (see [https://wiki.starkeeper.it/index.php/Mount_Setup#Voyager_Location_Cache_Manager here]). All the calculation and processing is done on the actual date time , time zone and latitude, longitude and elevation reported onthe little status bar on bottom of the finder
* '''Copy RA/DEC :''' copy to the clipboard the infor about actual RA/DEC of the target selected, you can paste in other Voyager forms where you have the Paste RA/DEC buttons
* '''Use this Object :''' click on this button to close the Finder and report the calculated coordinates to the caller.

A red background on the Transit Time field in the Processed data means the object will never be visible:

[[File:Immaginegg.png]]

{{note|If the Voyager Location Cache is empty transit / actual location and others data field will be blank. Connect at least one time the mount or use fidex value configuration to obtain the dynamic informations about the selected object.}}

==Asteroids Finder==
Asteroids Finder allow user to search for asteroids object in the RoboOrbits database. Search will be done in what is actually stored and not online. If you want you can update before the Asteroids database from online data.

[[File:Immagineoo.png]]

* '''Find Asteroids :''' entering the text to search
**'''Fast Find :''' run the search. Will be found asteroids which designation name or number start or match with the text. This is a fast search.
**'''Deep Find :''' run the serarch. Will be found asteroids which designation name or number start, contains or match with the text. This is a deep search and the time needed depends on your CPU power.
**'''Red X Button :''' will reset the search fields and the search results and data
*'''Search Results :''' where is showed the list of object found with the target number/code and the Designation Name order in alfabetical order. Double click on the interest row to select the object and to close the Finder and report the calculated coordinates to the caller. Single click on the interest row to show the orbital data and the processed data
*'''Data About Selected Object - NOW :''' contains all the data about the selected row with calculation about actual location and transit info if the Voyager Location cache is valorized and valid (see [https://wiki.starkeeper.it/index.php/Mount_Setup#Voyager_Location_Cache_Manager here]). All the calculation and processing is done on the actual date time , time zone and latitude, longitude and elevation reported onthe little status bar on bottom of the finder
*'''Copy RA/DEC :''' copy to the clipboard the infor about actual RA/DEC of the target selected, you can paste in other Voyager forms where you have the Paste RA/DEC buttons
*'''Use this Object :''' click on this button to close the Finder and report the calculated coordinates to the caller.

A red background on the Transit Time field in the Processed data means the object will never be visible:

[[File:Immaginegg.png|link=https://wiki.starkeeper.it/index.php/File:Immaginegg.png]]

{{note|If the Voyager Location Cache is empty the transit / actual location and others data field will be blank. Connect at least one time the mount or use fidex value configuration to obtain the dynamic informations about the selected object.}}

==Planets Finder==
PlanetsFinder allow user to search for planet object in the RoboOrbits database. Search will be done in what is actually stored and not online. It is not needed to update the data about because the planets data are embedded in Voyager application

[[File:Immaginexcv.png]]

*'''Planets List:''' Double click to select the planet and calculate the actual position
*'''Data About Selected Planet - NOW :''' contains all the data about the selected row with calculation about actual location and transit info if the Voyager Location cache is valorized and valid (see [https://wiki.starkeeper.it/index.php/Mount_Setup#Voyager_Location_Cache_Manager here]). All the calculation and processing is done on the actual date time , time zone and latitude, longitude and elevation reported onthe little status bar on bottom of the finder
*'''Copy RA/DEC :''' copy to the clipboard the infor about actual RA/DEC of the target selected, you can paste in other Voyager forms where you have the Paste RA/DEC buttons
*'''Use this Object :''' click on this button to close the Finder and report the calculated coordinates to the caller.

A red background on the Transit Time field in the Processed data means the object will never be visible:

[[File:Immaginegg.png|link=https://wiki.starkeeper.it/index.php/File:Immaginegg.png]]
[[Category:RoboOrbits]]
[[Category:All]]
[[Category:Manual|Ro]]

File:Immaginexcv.png

2024-06-29T13:38:46Z

Leonardo:

xcv