https://wiki.starkeeper.it/api.php?action=feedcontributions&user=Rowland&feedformat=atomVoyager Wiki - User contributions [en]2024-03-28T20:46:25ZUser contributionsMediaWiki 1.35.0https://wiki.starkeeper.it/index.php?title=Research_Survey&diff=6269Research Survey2022-01-28T20:23:43Z<p>Rowland: /* Target Tab */ Grammar</p>
<hr />
<div>==Research & Survey Mosaic Section==<br />
The Research & Survey Mosaic section lets you take a series of images of one or more targets at different times mantaining a complex constraints in a really simple way. For example, : <br />
<br />
*'''Exoplanets''' .. you may be looking for exoplanets, and want to image the same stars with known exoplanets several times a night<br />
*'''Asteroids and Comets''' .. you may also use the research and survey to look for moving objects, such as asteroids or comets<br />
*'''Supernovae Galaxies Survey''' .. or perhaps you want to take images of a number of galaxies every night, looking for supernovae.<br />
*'''Messier Marathons''' .. you may want to catch all the visible in the night Messier objects.<br />
*'''Mosaic''' .. you can also shot incredible Mosaic of Deep Sky using togheter with the Voyager VirtualFOV facilities based on [http://www.starkeeper.it/wdashinfo/ Web Dashboard]<br />
<br />
<br />
You can enter the Research & Survey Mosaic section two different ways:<br />
<br />
[[File:Command-bar-rs.png]]<br />
<br />
*From the Command Bar at the top of the Voyager window, click the icon pointed at by the red arrow<br />
<br />
<br />
[[File:Research-menu-2.png]]<br />
<br />
*From the Section menu, click the Research menu item on the ribbon<br />
<br />
<br /><br />
<br />
==Research & Survey Mosaic Workspace==<br />
<br />
Once you enter the Research & Survey Mosaic workspace, if you have some targets defined for your research survey mosaic, your workspace will look something like this:<br />
<br />
[[File:Research-survey-2.png]]<br /><br />
<br />
*'''Action Info''': This panel displays information about the Research & Survey Mosaic sequence that has been configured by clicking the gear [[File:Gear-icon.jpg]] icon.<br />
*The values shown in the first lines of this window depend on how you have configured the sequence. We will explain what the fields mean by using the field values from this screen shot:<br />
**'''Project''': The type of Survey ... for now this is a fixed value<br />
**'''TestUnguided''': The value of the Research Name field in the Research & Survey Mosaic configuration<br />
**'''C:\Users\leonardo\Documents\Voyager\ConfigSequence\TestUnguided.e2q''': If a Research & Survey Mosaic sequence file has been loaded, this is its pathname and filename. This will default to the [[Installation#Voyager Folders|values you specified]] when you installed Voyager, but it can be anywhere that you manually chose when you saved the file<br />
*'''Sequence Target Table''': This table shows the targets and progress if the sequence is running (as in this example) or has completed. <br />
**'''BLUE/GREEN ARROW ICON''': up pointing if object is rising before meridian, down if passed meridian and going to set<br />
**'''TARGET NAME''': Name from the data table in the Research & Survey Mosaic sequence configuration<br />
**'''RA J2000''': RA coordinates of the target from the data table in the Research & Survey Mosaic sequence configuration<br />
**'''DEC J2000''': DEC coordinates of the target from the data table in the Research & Survey Mosaic sequence configuration<br />
**'''PA°:''' Position Angle of the Target to use to manage the rotator position (Sky PA or Rotator PA depends on setting in the Rotator configuration Tab<br />
**'''ALT''': Altitude of the target at the time the sequence exposures were started<br />
**'''TIME START''': Starting time when the exposures of this object were taken<br />
**'''TIME END''': Time when the exposures of this object finished<br />
**'''TIME''': Elapsed time to complete the exposures<br />
**'''STATUS''': Blank if nothing has run, DONE if this step is complete, RUNNING if it is currently running, SKIPPED_ALTITUDE if step bypassed for low altitude, DONE_ERROR is completed with an error<br />
<br />
<br />{{Note|Each target will be listed once in this panel, regardless of whether you are running the exposures once or multiple times in a loop, which you can choose in the Research & Survey Mosaic configuration window. The times and status reflect the last running values, the altitudes are updated every 30 seconds.}}<br /><br />
==Research & Survey Mosaic Configuration==<br />
Most of the settings are the same as the Sequence Configuration window so this will be familiar if you have set up sequences before. <br />
<br />
As for Voyager 2.2.13f you can edit and import the Rotation of the Target (Sky PA or Rotator PA). As of Voyager 2.0.14e (daily build) or 2.1.0 (stable build), you can edit sequences associated with any profile, not just the one currently loaded and active in Voyager. The "Change Profile To This Sequence" button in the title bar of this window brings up the dialog to do this. <br />
<br />
<br />
[[File:Research-survey-gain-offset.jpg]]<br /><br />
<br />
*'''Project''': Any name you would like to use to identify your configuration<br />
*'''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<br />
*[[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 [[Research Survey#Change Sequence Profile|Change Sequence Profile]] section for discussion of the migration process<br />
*[[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 sequence. If you have not saved it, your sequence data will be lost and you will have to start over<br />
*[[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 sequence into the Research & Survey Mosaic Configuration window<br />
*[[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 Research & Survey Mosaic Configuration window to the file of your choice<br />
*[[File:Cancel-config.png|link=https://voyager.tourstar.net/File:Cancel-config.png]] '''Cancel and Close Window''': Click this button to close the Research & Survey Mosaic Configuration window and discard any changes made since it was opened<br />
*'''Refresh Filter Synoptic''': Refreshes the filter synoptic display - the color bar under the Sequence Elements table that represents the amount of time and order of shots taken by filter color<br />
*'''OK''': Click the OK button to save your changes and close the Research & Survey Mosaic Configuration window<br /><br />
<br />
<br /><br />
<br />
==Change Sequence Profile==<br />
<br />
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. <br />
<br />
'''''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.'''''<br />
<br />
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.<br />
<br />
'''References to the "Actual" profile mean the currently active profile in Voyager.'''<br />
<br />
<br />
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:<br />
<br />
[[File:Research-survey-change-profile.png]]<br />
<br />
<br />{{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.}}<br /><br />
<br />
*'''Data''':<br />
**'''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<br />
**'''Original Profile''': The profile stored with the sequence file<br />
**'''Actual Profile''': The profile currently loaded and active in Voyager<br />
*'''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<br />
*'''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.<br />
*'''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<br />
*'''CANCEL''': Abort the sequence profile changes and close this window without saving changes<br />
<br />
==Sequence Elements==<br />
The Sequence Elements panel of the Research & Survey Mosaic configuration window is where you define the exposures to take for each target:<br />
<br />
[[File:Research-survey-sequence-elements-216c.jpg]]<br />
<br />
*'''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<br />
*'''Type''': Exposure type: Light, Bias or Dark<br />
*'''Filter''': Filter for this exposure. Available filters come from the connected profile in the [[Camera Setup#Filters|Camera Setup]] area<br />
*'''Suffix''': Enter any suffix you would like to include in the image filename. The name of your filter is a good choice.<br />
*'''Exposure''': Length of the exposure in seconds<br />
*'''Bin''': Binning level for this exposure. Available binning levels come from the connected profile in the [[Camera Setup#Filters|Camera Setup]] area<br />
*'''Speed''': ISO for DSLR's<br />
*'''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%20Mode|Readout Mode section of the Camera Setup]] page explains how to retrieve them<br />
*'''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.<br />
*'''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.<br />
*{{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.}}<br /><br />
*[[File:Lens.jpg]]: 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]].<br />
*'''Repeat''': Number of exposures to take<br />
*[[File:Sequence-element-copy-paste.jpg|link=https://voyager.tourstar.net/File:Sequence-element-copy-paste.jpg]]:<br />
**Up arrow moves this row up one position; Down arrow moves this row down one position; X clears the information from this row<br />
**'''Copy Button''': Click Copy to copy the sequence element information from the row containing the Copy button<br />
**'''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<br />
**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<br />
**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<br />
*The color bar under the Sequence Elements is the "Filter Synoptic." This is a visual representation of the amount of time spent imaging each filter, in the order that the filters will be used. In this example, the red, green and blue filters are used in sequence, with an equal amount of time spent shooting each filter (60 seconds). The color bars have an equal size for each color, representing 60 seconds of red, 60 seconds of green, and 60 seconds of blue.<br />
<br />
<br /><br />
{{Note|Gain and Offset are only available when using the Voyager ASI or QHY Camera native driver. They are not available if you use the ASCOM driver}}<br />
<br />
==Target Tab==<br />
The Target Tab of the Research & Survey Mosaic configuration window contains two sub-tabs. The first one is a data table listing the names, coordinates, and order in which to run your targets:<br />[[File:Research-target-2.png]]<br />
<br />
*'''Name''': Enter the name of your target<br />
*'''RA J2000''': Enter the RA of your target<br />
*'''DEC J2000''': Enter the DEC of your target<br />
*'''Rotation °''': Enter the Rotation angle used by Voyager to positioning the rotator. Can be Sky PA or Rotator PA, depends on how you configure it in the Rotator configuration tab<br />
*'''Order''': Enter a number representing the order in which your target should be run. If no value is entered here, targets run in the order listed<br />
*'''RoboClip:''' opening the RoboClip for import a single target from the database (not a mosaic with Virtual FOV)<br />
*'''Remove:''' Remove the target from the Data panel<br />
*'''Disabled:''' If checked, the Research & Survey Mosaic Sequence will not be run for this target. The target will be skipped and reported in the dashboard area<br />
*'''Clear All''': Click this button to clear the target data table<br />
*'''Import Mosaic Panels from RoboClip Virtual FOV:''' import your targets as panels of mosaic from RoboClip in one click. The target in RoboClip must be a Mosaic created with Voyager's Virtual FOV facility<br />
*'''Import Targets from CSV file''': Import your targets from a CSV file with four columns formatted like this. The first line with column names is mandatory. You can have as many lines as you want in your CSV file.<br />
**TARGET;RA;DEC;ORDER<br />
**IC10;00 20 24.33;+59 18 06.7;1<br />
**IC166;06 27 05.37;+59 05 03.5;2<br />
**Here's a sample file with the correct import format: [http://www.starkeeper.it/voyager/log.csv log.csv] <br /><br />
*'''Verify''' '''Data''': Click this button after editing the list to apply your settings - this does not validate the data, it merely makes your changes active<br />
*'''Refresh Filter Synoptic''': Refreshes the filter synoptic display - the color bar under the Sequence Elements table that represents the amount of time and order of shots taken by filter color<br />
<br />
<br />
The second sub-tab of the Target tab is Running Options:<br />
<br />
[[File:Research-running-options.png]]<br />
<br />
*'''Min Altitude''': The minimum altitude in degrees at which exposures will be taken of the target. When the target is below this altitude, it will be skipped in the sequence<br />
*'''Force Starting from This Target''': Choose a target from the drop-down list to start the sequence with exposures of it<br />
*'''Repeat Loop Mode''': Choose a loop mode from the drop-down list<br />
**'''Just One Time''': Run the sequence once for each target in the data table<br />
**'''Repeat for X times''': Run the sequence X times, where X is the value entered in the "Repeat for X times" counter field on the right<br />
**'''Infinite Loop''': Run the sequence continuously until either all targets are below the "Min Altitude" value, or the time interval specified in the On End tab has elapsed - or the absolute end time has been reached<br />
*'''Invert Order Each Target Repeat''': If checked, when running the sequence more than once on the targets in the data table, reverse the order in which they are run for each loop. E.g., if the targets are T1, T2, T3, run them in that order on the first loop, and then T3, T2, T1 on the second, etc.<br />
*'''Not Allow Meridian Recrossing During a Loop''': If checked, if the meridian is crossed during a loop, skip any targets on the opposite side of the meridian during this loop. When the loop executes the next time, the meridian will be crossed and those targets will run.<br />
*'''Abort Action if One Element of Loop was done with error''': If checked, if an error occurs on a single target in a loop, the loop will be finished and then the sequence will abort<br />
*'''Time Wait After First Pointing to Target''': If checked, wait the number of seconds specified after initially pointing to a target. This allows the mount to settle after moving and before exposures begin<br />
<br />
<br />{{Note|Ordering your targets by RA may help with your survey if it minimizes the need to cross the meridian and do a time-consuming meridian flip}}<br /><br />
==Sequence Tab==<br />
The Sequence tab of the Research & Survey Mosaic window is where you specify how the slots should be ordered and where images should be stored:<br />
<br />
[[File:Research-sequence-tab.png]]<br />
<br />
*'''Sequence Mode''': Choose Cyclic Round or Group By Slot from the drop-down list<br />
**'''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.<br />
**'''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.<br />
*'''Sequence Directory''': Where to save images taken during this sequence<br />
**'''Auto / Manual''': Choose Auto and Voyager will automatically create a sequence directory using the base folder specified in [https://voyager.tourstar.net/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<br />
**'''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<br />
<br />
* '''Sequence Sub Foldering / File Naming:''' selection of the sub foldering and file naming method<br />
** '''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)<br />
** '''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<br />
*** '''Create Logical Data Subfolder Insside Sequence Directory (all between 00:00 to 08:00 AM are from yesterday) :''' create a subfolder under the target folder with a YYYY-MM-DD format , file within 00:00 to 08:00 wil be put in a folder from the previous day date<br />
*** '''Create Data Subfolder for Filter Name:''' create a sub folder with the target name<br />
<br />
<br /><br />
<br />
==On Start Tab==<br />
The On Start tab of the Research & Survey Mosaic configuration window is where you can specify things to do before starting the sequence:<br />
<br />
[[File:Research-on-start.png]]<br />
<br />
*'''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<br />
*'''Time Wait On Start''': Specify if Voyager should delay before starting the sequence<br />
**'''Interval''': Check this box 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<br />
**'''Absolute''': Check this box and enter the actual time in HH:MM:SS at which Voyager should start running the sequence<br />
*'''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<br />
*'''Point Target On Start''': Check to perform a [[Plate Solve Setup#Precision Pointing|precision pointing]] operation at sequence start<br />
*'''Inject Focus on Start''': Check to perform an autofocus operation at first target of sequence at start<br />
*'''Inject Focus on Start''' '''of Each Target:''' Check to perform an autofocus operation at start of each target sequence<br />
*'''Open Flat Device Cover''': Check to open the flat device at sequence start<br />
**'''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<br />
**'''After Time Wait on Start''': Open the flat device cover after the Time Wait On Start interval has elapsed<br />
<br />
<br />{{Note|If the Research & Survey Mosaic sequence is run from a DragScript, only the Point Target on Start field is used. The other fields must be specified with DragScript actions}}<br />
<br />
<br /><br />
<br />
==Cooling Tab==<br />
The Cooling tab of the Research & Survey Mosaic configuration window is where you specify CCD cooling (Peltier) for the sequence:<br />
<br />
[[File:Research-cooling-tab.png]]<br />
<br />
*'''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.<br />
*'''SetPoint''': Enter the desired sensor temperature (SetPoint) for your CCD cooler<br />
**'''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<br />
**'''Power ON After Time Wait On Start''': If checked, send a command to turn CCD cooler power on after the [https://voyager.tourstar.net/Sequence_Configuration#On_Start_Tab Time Wait On Start] interval has elapsed<br />
**'''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 [https://voyager.tourstar.net/Camera_Setup#Cooling_System Camera Setup], or within the power usage constraints listed below, try again with successively warmer temperatures as specified below<br />
***'''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<br />
***'''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<br />
<br />
<br /><br />
==Pointing Tab==<br />
The Pointing tab of the Research & Survey Mosaic configuration window is where you specify additional parameters for any Pointing operations performed during the sequence:<br />
<br />
[[File:Research-pointing.png]]<br />
<br />
*'''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<br />
*'''Meridian Flip Watchdog:''' if checkd abort the sequence of running target if Voyager try for the times indicated to do a Meridian Flip but mount report wrong side of Pier or side of pier calculated is wrong<br />
<br />
<br />
==Rotator Tab==<br />
The Rotator tab of the Sequence Configuration window is where you specify additional parameters for your rotator's actions during the sequence:<br />
<br />
[[File:RotatorTab2213c.jpg|link=https://wiki.starkeeper.it/index.php/File:RotatorTab2213c.jpg]]<br />
*'''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<br />
*'''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<br />
*'''PA Tollerance +/-:''' specified the tollerance in degree about the PA accepted like ok (example 180° +/-3° will accept 177° to 183°)<br />
*'''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.<br />
*'''Rotator & Fork Mount:''' if enabled force Voyager to check rotator tolleranze after each Target realign, useful for fork mount with derotator system<br />
{{Note|Rotator management will be done only done in this two points of the sequence:<br />
<br />
- at first precise pointing, so flag the “Point target on start” in the start tab of the sequence configurator<br />
<br />
- at meridian change<br />
}}<br />
<br />
<br />
==Tracking Tab==<br />
The Tracking tab of the Research & Survey Mosaic Configuration window is where you specify additional parameters for your mount's tracking actions during the sequence:<br />
<br />
[[File:Research-tracking.png]]<br />
<br />
*'''Tracking Stop Watchdog''': If checked, if tracking stops during the sequence, attempt to restart tracking the specified number of times<br />
*'''Tracking Start''': If checked, stop tracking when the sequence is started, and start tracking only after the [https://voyager.tourstar.net/Sequence_Configuration#On_Start_Tab Time Wait On Start] interval has elapsed<br />
<br />
<br /><br />
==Plate Solving Tab==<br />
The Plate Solving tab of the Research & Survey Mosaic Configuration window is where you specify additional parameters for plate solving during the sequence:<br />
<br />
[[File:Plate-solving-tab.png|link=https://voyager.tourstar.net/File:Plate-solving-tab.png]]<br />
<br />
*'''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<br />
*'''Bypass General 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 [https://voyager.tourstar.net/Plate_Solve_Setup#Plate_Solving_DEFAULT_Setting Plate Solve setup]<br />
<br />
<br />{{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}}<br /><br />
==Meridian Flip Tab==<br />
The Meridian Flip tab of the Research & Survey Mosaic Configuration window is where you specify additional parameters for meridian flip management during the sequence:<br />
<br />
[[File:Research-meridian-flip1.png]]<br />
<br />
*'''Meridian Flip Mode''': Choose Do Not Manage, Halt on Flip Time or Manage from the drop-down list<br />
**'''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<br />
**'''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<br />
**'''Manage''': Voyager will monitor the mount position relative to the meridian and perform a meridian flip as needed, as specified in [https://voyager.tourstar.net/Mount_Setup#GEM_Meridian_Flip_Manager Mount Setup]<br />
*'''Flip Rotator On Meridian Flip''': If checked, if a rotator is attached, flip the rotator 180 degrees after a meridian flip so the image's position angle is maintained<br />
*'''Inject Focus On Meridian Flip''': If checked, perform an autofocus after the meridian flip completes<br />
*'''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<br />
*'''ABORT Exposure if Meridian Flip occour outside Voyager and FORCE EXECUTE Meridian Flip operations:''' if checked Voyager try to recognize a change of pier outside Voyager and start the operation needed and/or asked in Voyager for the meridian flip. The flag work only if the mount control in Voyager is an ASCOM Driver, ASCOM Pier mode in Voyager is setting like ASCOM Normal or ASCOM Inverted and Meridian Flip Mode (Above) is setting like MANAGED<br />
<br />
<br />{{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}}<br /><br />
==Guide/Dithering Tab==<br />
The Guide/Dithering tab of the Research & Survey Mosaic Configuration window is where you specify additional parameters for guiding and dithering management during the sequence. The settings in [https://voyager.tourstar.net/Guiding_Setup Guiding Setup] are used unless these settings override them.<br />
<br />
[[File:Research-guide-dithering.png]]<br />
<br />
*'''Guide Star Selection Method''': Choose how the guide star should be selected<br />
**'''Voyager RoboGuide''': Voyager's own RoboGuide algorithm, as specified in [https://voyager.tourstar.net/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<br />
**'''Native Guide Control''': Use the guiding software's own star selection method<br />
*'''Calibrate Guide''': If checked, use this exposure in seconds and binning level for the guide software's calibration routine<br />
*'''Guiding''': If checked, use this exposure 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<br />
**'''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<br />
***'''None''': Never perform AO Centering<br />
***'''Every Exposure''': Perform AO Centering after every exposure<br />
***'''Every X Exposure''': Specify X = number of exposures between AO Centering operations<br />
*'''Star Lost Detection''': If checked, the maximum allowed percentage of time that the guide star can be lost without considering guiding to have failed<br />
*'''Dithering''': If checked, specify the max number of pixels to move during a dithering operation<br />
*'''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<br />
<br />
<br /><br />
<br />
==Shot Tab==<br />
The Shot tab of the Research & Survey Mosaic Configuration window is where you specify additional parameters for image exposures:<br />
<br />
[[File:Research-shot.png]]<br />
<br />
*'''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<br />
*'''On Exposure Error''': If checked, if an exposure results in an error, try to re-take the exposure up to 3 times<br />
*'''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.<br />
**'''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<br />
<br />
<br /><br />
==Focus Tab==<br />
The Focus tab of the Research & Survey Mosaic Configuration window is where you specify additional parameters for autofocus operations. <br />
<br />
The settings in [https://voyager.tourstar.net/AutoFocus_Setup AutoFocus setup] are used unless these settings override them.<br />
<br />
[[File:Research-survey-sequence-focus-2.11f.jpg]]<br />
<br />
*'''Focus Method''': Choose the autofocus method to use during the sequence<br />
**'''Voyager RoboStar''': Use [https://voyager.tourstar.net/AutoFocus_Setup#RoboStar_General_Setting Voyager's RoboStar] method to select the star for Voyager's single-star VCurve autofocus operation<br />
**'''Voyager LocalField''': Use Voyager's LocalField multiple-star autofocus operation<br />
**'''Focus Star''': Use the focus star specified by the Focus Star panel below and use Voyager's VCurve single-star autofocus operation<br />
**'''FocusMax AcquireStar''': Use FocusMax for autofocus and request that it use its own AcquireStar method to select a star for autofocus<br />
**'''Focus On Place''': Autofocus using a suitable star, if one can be found, in the current field of view<br />
*'''Use Low Precision Pointing''': If checked, relax the [https://voyager.tourstar.net/Mount_Setup#Management error tolerance for precision pointing] to the focus star.<br />
**'''Multiple Max Allowed Error by''': If Use Low Precision Pointing is checked, multiply the error tolerance specified in [https://voyager.tourstar.net/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.<br />
*'''Max HFD Variation Percentage Allowed''': Maximum amount of variation of the focus star's HFD (Half Flux Diameter) allowed. Larger values are considered an autofocus failure<br />
*'''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<br />
*'''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<br />
*'''Focus Star Setting''': Specify a star to use for autofocus before the meridian, after the meridian, or at all times.<br />
**If only the left column - '''Before Meridian''' - is filled out, that star is used for the entire sequence.<br />
**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<br />
***[[File:Object-finder.jpg|link=https://voyager.tourstar.net/File:Object-finder.jpg]]: Click this icon to bring up the [https://voyager.tourstar.net/OnTheFly#Target_Coordinates_J2000 Object Finder] and search for your focus star by name. The [https://voyager.tourstar.net/OnTheFly#Target_Coordinates_J2000 Object Finder] will populate the RA, DEC and NAME fields from the search result<br />
*'''Focus Filter''':<br />
**'''Use Actual Filter''': Autofocus using the filter for the currently running slot of the sequence<br />
**'''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.<br />
*'''Focus Trigger''': Check one or more boxes to determine the condition(s) that trigger an autofocus<br />
**'''Focus By Slot''': If checked, and if the sequence mode is '''Group By Slot''', autofocus at the start of every new sequence slot.<br />
**'''Focus Each X Exposure''': If checked, focus every X exposures, where X is the counter value.<br />
**'''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.<br />
**'''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.<br />
**'''Focus Each X Delta Degrees of Altitude''': If checked, focus every time the target's altitude changes by the specified number of degrees<br />
*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|link=https://voyager.tourstar.net/File:New-autofocus-monitor-info-2.11f.jpg]]<br />
<br />
<br />{{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.}}<br />{{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}}<br /><br />
<br />
<br />{{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}}<br />{{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}}<br />
<br />
==On End Tab==<br />
The On End tab of the Research & Survey Mosaic Configuration window is where you specify actions Voyager should take at the end of a sequence:<br />
<br />
[[File:Research-on-end.png]]<br />
<br />
*'''Force Sequence End Timer''': If checked, end the sequence after the time Interval specified has elapsed (HH:MM:SS)<br />
**'''Absolute''': If checked, end the sequence at the absolute time indicated in the counter fields (HH:MM:SS)<br />
**'''Finish Running Exposure''': If checked, finish any exposure in progress when the Force Sequence End Timer is triggered<br />
*'''Do this at END''':<br />
**'''Nothing''': If this radio button is selected, do nothing at the end of the sequence<br />
**'''Warmup''': If this radio button is selected, warmup the CCD cooler at the end of the sequence<br />
***'''Sync Warmup''': If checked, wait for the warmup to finish. If not checked, send the warmup command to the cooler and don't wait<br />
*'''Good Night''': if this radio button is checked, Voyager will perform the following shutdown actions at the end of the sequence:<br />
**'''Run this Program/Script BEFORE''': Click the "..." button to [https://voyager.tourstar.net/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<br />
**'''Move CCD to Filter''': If checked, move the filter wheel to the filter selected from the drop-down list<br />
**'''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<br />
**'''Sync Warmup''': If checked, send a command to the CCD cooler to warm the sensor, and wait for the warmup operation to complete<br />
**'''Park''': If checked, park the mount<br />
**'''Run this Program/Script AFTER''': Click the "..." button to [https://voyager.tourstar.net/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 <br /><br />
{{Note|If the Research & Survey Mosaic sequence is run from a DragScript, the On End tab information is not used. The DragScript instructions for what to do after the sequence ends are followed instead}}<br /><br />
<br />
[[Category:All]]<br />
[[Category:Manual|K]]</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=DragScript_Elements&diff=6268DragScript Elements2022-01-28T11:07:00Z<p>Rowland: /* Signals */ Updated instructions on getting API and Chat ID's from Telegram</p>
<hr />
<div>__TOC__<br />
<br />
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.<br />
<br />
Each category of element is organized in list that can be expanded or contracted by clicking the "+" or "-" next to the element category name:<br />
<br />
[[File:Dragscript-editor-elements.png]]<br />
<br />
E.g., if you click the + in front of Actions, the list expands like this:<br />
<br />
[[File:List-expanded.png]]<br />
<br />
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:<br />
<br />
[[File:Subcategory-expanded.png]]<br />
<br />
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<br />
<br />
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.<br />
<br />
Press Sort button to listing all the categories and blocks in alphabetical order.<br />
<br />
==DragScript Actions==<br />
<br />
===Operating System===<br />
The Operating System actions control the PC running Voyager:<br />
<br />
[[File:DSopOs.png]]<br />
<br />
*'''Shutdown PC''': Shutdown the PC running Voyager<br />
*'''Restart PC''': Restart (reboot) the PC running Voyager<br />
*'''Hybernate PC:''' Hybernate the PC running Voyager (only in OS that support it)<br />
*'''Suspend PC:''' Susend the PC running Voyager (only in OS that support it)<br />
*'''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.<br />
<br />
[[File:Kill-process.png]]<br />
<br />
*'''Serial Port STRING Transmit''': Send a text string with a terminator (if necessary) to an RS232 Serial Port<br />
<br />
[[File:SerPortTx.png]]<br />
<br />
*'''Configuration'''<br />
**'''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)<br />
**'''Text to Send''': input the text to send to the serial port<br />
**'''Use Terminator''': indicate if you want to use a terminator or not. CR = carriage return, LF=Line feed<br />
*'''Serial Port BINARY Transmit''': Send Binary data string to an RS232 Serial Port<br />
<br />
[[File:SerPortBin.png]]<br />
<br />
*'''Configuration'''<br />
**'''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)<br />
**'''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)<br />
*'''UDP IP/Port STRING Transmit''': Send a text string with a terminator (if necessary) to an UDP Port<br />
[[File:Txudpstring.png]]<br />
<br />
* '''Configuration'''<br />
**'''IP/Hostname''': IP or hostname of PC where to send data<br />
**'''Port:''' UDP port number to use for transmission <br />
**'''Text to Send''': input the text to send to the UDP Port<br />
**'''Use Terminator''': indicate if you want to use a terminator or not. CR = carriage return, LF=Line feed<br />
*'''UDP IP/Port BINARY Transmit''': Send Binary data string to an RS232 Serial Port<br />
*[[File:UDPIPBinaryTX.png]]<br />
* '''Configuration'''<br />
** '''IP/Hostname''': IP or hostname of PC where to send data<br />
**'''Port:''' UDP port number to use for transmission<br />
** '''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)<br />
<br />
==Setup==<br />
Setup actions control connecting and disconnecting to your equipment and software:<br />
<br />
[[File:Dragscript-setup-2.14c.png]]<br />
<br />
*'''Connect Setup''': Commands Voyager to connect to the equipment and software in the currently selected [[Setup#Profile Management|Profile]]<br />
*'''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:<br />
<br />
[[File:Setup-timeout.png]]<br />
<br />
*'''Disconnect Setup''': Command Voyager to disconnect from the equipment and software in the currently selected [[Setup#Profile Management|Profile]]<br />
*'''Connect Safety Monitor Control''': Connect only the Safety Monitor control. This is useful for monitoring conditions prior to connecting all your equipment<br />
*'''Disconnect Safety Monitor Control''': Disconnect only the Safety Monitor control<br />
*'''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<br />
*'''Disconnect Flat Device #1 / #2 Control''': Disconnect only the Flat Device #1/#2 control<br />
<br />
<br /><br />
<br />
==Voyager==<br />
Interaction with Voyager Application:<br />
<br />
[[File:Immagine 2021-04-05 193048.png]]<br />
<br />
* '''Change Voyager Profile''': will allow changing of profile from DragScript. Voyager must have the setup not connect or action will failed.<br />
** [[File:Immaginefefefr.png]]<br />
*** '''Profile:''' Profile select, and list of all profile if retrieved from Voyager<br />
*** '''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<br />
*** '''OK''': Click to save your changes and close the window<br />
***'''Cancel''': Click to discard your changes and close the window <br />
<br />
==Session==<br />
Session actions run sequences to acquire images, flat frames, and shutdown ("Good Night") your system:<br />
<br />
[[File:Session-script.png]]<br />
<br />
*'''Sequence''': Run a [[Sequence Configuration|Sequence]] with options:<br />
<br />
[[File:Dragscript-sequence-211g.jpg]]<br /><br />
<br />
*'''Configuration Panel''':<br />
**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<br />
**'''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<br />
***'''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]]<br />
***'''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<br />
***'''Start and End at Absolute Time''': Voyager should wait until the specified Start: time and end the sequence at the specified End: time.<br />
***'''Immediately Start and End at Absolute Time''': Start the sequence immediately and end it at the time specified in the counter fields<br />
***'''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<br />
*'''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<br />
**<br />
**<br />
<br />
<br />{{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.}}<br />{{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}}<br />{{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}}<br />{{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}}<br />{{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}}<br />
<br />
**'''Options''': Check the boxes to select any of these options:<br />
***'''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<br />
***'''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<br />
***'''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.<br />
***'''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<br />
***'''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<br />
***'''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<br />
***'''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<br />
***'''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<br />
***'''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<br />
***'''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<br />
***'''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<br />
***'''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°<br />
**'''Default''': Click this button to populate this window with the default options<br />
**'''OK''': Click to save your changes and close the window<br />
**'''Cancel''': Click to discard your changes and close the window <br /><br />
*'''Research & Survey''': Run a [[Research Survey|Research & Survey]] sequence with options<br />
<br />
[[File:Research-survey-dragscript.png]]<br />
<br />
*'''Configuration Panel''':<br />
**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]]<br />
**TYPO: Star/TimeSpan should be Start/TimeSpan<br />
**'''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<br />
***'''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<br />
***'''Start and End at Absolute Time''': Voyager should wait until the specified Start: time and end the sequence at the specified End: time.<br />
***'''Immediately Start and End at Absolute Time''': Start the sequence immediately and end it at the time specified in the counter fields<br />
***'''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<br />
**'''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<br />
*'''Options''':<br />
**'''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<br />
**'''Default''': Click this button to populate this window with the default options<br />
**'''OK''': Click to save your changes and close the window<br />
**'''Cancel''': Click to discard your changes and close the window <br /><br />
<br />
<br />{{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}}<br />
<br />
*'''Flat''': Run an Auto Flat sequence. [[Auto Flat|Configure the Auto Flat sequence files]] in the OnTheFly workspace<br />
<br />
[[File:Flat-sequence-dragscript.png]]<br />
<br />
*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<br />
*TYPO: Configuration dialog says "Good Night" but should be Auto Flat<br />
*'''Default''': Click this button to populate this window with the default options (blanks out the Flat Sequence File field)<br />
*'''OK''': Click to save your changes and close the window<br />
*'''Cancel''': Click to discard your changes and close the window<br />
<br />
<br /><br />
<br />
*'''Good Night''': Run a series of one or more shutdown actions:<br />
<br />
[[File:Dragscript-good-night.png]]<br />
<br />
*'''CCD Filter Select''': Moves the filter wheel to the filter chosen from the drop-down box on the right<br />
*'''Sync Warmup''': Send the CCD cooler a warmup command and wait until it finishes<br />
*'''Async Warmup''': Send the CCD cooler a warmup command and continue execution without waiting for it to finish<br />
*'''Parking''': Park the mount as specified in [[Mount Setup#Park.2FUnpark|Mount Setup]]<br />
<br />
<br /><br />
<br />
==Plate Solving==<br />
Plate Solving actions perform a plate solving action as defined in the [[Plate Solve Setup|Plate Solving setup]] of the active profile:<br />
<br />
[[File:Dragscript-plate-solving.png]]<br />
<br />
<br /><br />
<br />
*'''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. ''<u>Mount will not be synched</u>''<br />
*'''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. ''<u>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</u>''<br />
*'''Plate Solving with Rotator 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. <u>''Mount will not be synched.''</u> Also perform a Sync of the rotator to the PA solved.<br />
*'''Plate Solving with Mount & Rotator 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. <u>''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.''</u> Also perform a Sync of the rotator to the PA solved.<br />
<br />
<br /><br />
<br />
==Blind Solving==<br />
Blind Solving actions perform a plate solving action as defined in the [[Plate Solve Setup|Plate Solving setup]] of the active profile:<br />
<br />
[[File:BlindSolveBlocks.png]]<br />
<br />
<br /><br />
<br />
*'''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. ''<u>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</u>''<br />
*'''Blind Solving with Rotator 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. <u>''Mount will not be synched.''</u> Also perform a Sync of the rotator to the PA solved.<br />
*'''Blind Solving with Mount & Rotator 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. <u>''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.''</u> Also perform a Sync of the rotator to the PA solved.<br />
<br />
<br /><br />
<br />
==WEB Solving==<br />
Plate Solving actions perform a plate solving action as defined in the [[Plate Solve Setup|Plate Solving setup]] of the active profile:<br />
<br />
[[File:WebSolvingBlocks.png]]<br />
<br />
<br /><br />
<br />
*'''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]]<br />
**[[File:Web-solving-with-sync.png]]<br />
***'''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<br />
<br />
*'''Web Solving with Rotator Sync:''' Perform a web 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. ''Mount will not be synched.'' Also perform a Sync of the rotator to the PA solved.<br />
*'''Web Solving with Mount & Rotator Sync:''' Perform a web 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.'' Also perform a Sync of the rotator to the PA solved.<br />
<br />
<br /><br />
==Guiding==<br />
Guiding actions send commands to the guide software:<br />
<br />
[[File:Dragscript-guiding-dithering.png]]<br />
<br />
*'''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:<br />
<br />
[[File:Dragscript-calibrate-guide.png]]<br />
<br />
*'''Time''': Exposure time for Calibration exposures by the guiding software<br />
*'''Binning''': Binning level for Calibration exposures by the guiding software<br />
*'''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.<br />
*'''Default''': Use the default settings<br />
*'''OK''': Save changes and close the window<br />
*'''Cancel''': Discard changes and close the window<br />
<br />
<br /><br />
<br />
*'''Acquiring Guide Star''': Commands the guiding software to select a guide star. Double click to bring up the configuration window:<br />
<br />
[[File:Dragscript-acquire-guide-star.png]]<br />
<br />
*'''Time''': Exposure time for guide star acquisition exposures by the guiding software<br />
*'''Binning''': Binning level for guide star acquisition exposures by the guiding software<br />
*'''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.<br />
*'''Default''': Use the default settings<br />
*'''OK''': Save changes and close the window<br />
*'''Cancel''': Discard changes and close the window<br />
<br />
<br />
*'''Guide Start''': Commands the guiding software to begin guiding. Double click to bring up the configuration window:<br />
<br />
[[File:Dragscript-guide-start.png]]<br />
<br />
*'''Time''': Exposure time for guiding exposures by the guiding software<br />
*'''Binning''': Binning level for guiding exposures by the guiding software<br />
*'''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.<br />
*'''Default''': Use the default settings<br />
*'''OK''': Save changes and close the window<br />
*'''Cancel''': Discard changes and close the window<br />
<br />
<br /><br />
<br />
*'''Guide Stop''': Command the guiding software to stop guiding<br />
<br />
<br /><br />
<br />
*'''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:<br />
<br />
[[File:Dragscript-guide-dithering.png]]<br />
<br />
*'''Max Pixel''': Specify the maximum number of pixels that a dithering operation can move the mount<br />
*'''Default''': Use the default settings<br />
*'''OK''': Save changes and close the window<br />
*'''Cancel''': Discard changes and close the window<br /><br />
<br />
*'''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.<br />
<br />
[[File:Unguided-dither-3.png]]<br />
<br />
*'''Max Pixel''': Specify the maximum number of pixels that a dithering operation can move the mount<br />
*'''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<br />
*'''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.<br />
*'''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.<br />
*'''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.'''<br />
*'''Default''': Use the default settings<br />
*'''OK''': Save changes and close the window<br />
*'''Cancel''': Discard changes and close the window<br />
<br />
<br /><br />
==Mount==<br />
Mount actions send commands to the mount defined in the [[Mount Setup|Mount setup]] of the active profile:<br />
<br />
[[File:Dragscript-mount.png]]<br />
<br />
*'''Stop Tracking''': Command the mount to stop tracking<br />
*'''Start Tracking''': Command the mount to start tracking<br />
*'''Parking''': Command the mount to slew to the Park position<br />
*'''Unparking''': Command the mount to Unpark<br />
*'''Sync on Park''': Command the mount to save the current position as the Park position<br />
*'''Homing''': Command the mount to move to the Home position<br />
*'''Goto RA/DEC''': Command the mount to move to the specified RA and DEC coordinates (J2000)<br />
<br />
[[File:Dragscript-gotoradec.png]]<br />
<br />
*'''RA J2000''': Enter the RA coordinates in HH MM SS or HH MM SS.sss<br />
*'''DEC J2000''': Enter the RA coordinates in DD MM SS or DD MM SS.sss<br />
*'''Default''': Use the default settings: clears the RA and DEC fields<br />
*'''OK''': Save changes and close the window<br />
*'''Cancel''': Discard changes and close the window<br />
<br />
<br /><br />
<br />
*'''Goto ALT/AZ''': Command the mount to move to the specified Altitude and Azimuth coordinates<br />
<br />
[[File:Goto-altaz.png]]<br />
<br />
*'''ALT:''' Enter the Altitude coordinates in DD MM SS or DD MM SS.sss<br />
*'''AZ''': Enter the Azimuth coordinates in DD MM SS or DD MM SS.sss<br />
*'''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<br />
*'''Default''': Use the default settings: clears the AZ and ALT fields<br />
*'''OK''': Save changes and close the window<br />
*'''Cancel''': Discard changes and close the window<br />
<br />
<br /><br />
<br />
*'''Goto Near Zenith''': Command the mount to move to a point close to the current Zenith (directly overhead). <br /><br />
{{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}}<br />
<br />
*<br />
<br />
*'''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.<br />
<br />
[[File:Dragscript-gotoname.png]]<br />
<br />
*'''Object Name''': Name of the object to goto. Must be a name that can be successfully searched in the connected Planetarium software<br />
*'''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<br />
*'''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<br />
<br />
<br /><br />
<br />
*'''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:<br />
<br />
[[File:Dragscript-precisepointing.png]]<br />
<br />
*'''RA J2000''': Enter the RA coordinates in HH MM SS or HH MM SS.sss<br />
*'''DEC J2000''': Enter the DEC coordinates in DD MM SS or DD MM SS.sss<br />
*'''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.<br />
*'''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.<br />
*'''RoboClip:''' open RoboClip manager windowd and allow to select a target,<br />
*'''Default''': Use the default settings<br />
*'''OK''': Save changes and close the window<br />
*'''Cancel''': Discard changes and close the window<br />
<br />
<br /><br />
<br />
*'''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.<br />
<br />
*[[File:Dragscript-precisepointing-name.png]]<br />
**'''Object Name''': Name of the object to goto. Must be a name that can be successfully searched in the connected Planetarium software<br />
**'''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<br />
**'''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<br />
**'''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.<br />
**'''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.<br />
**'''Default''': Use the default settings<br />
**'''OK''': Save changes and close the window<br />
**'''Cancel''': Discard changes and close the window<br />
<br />
<br /><br />
<br />
*'''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.<br />
<br />
*[[File:PrecisePointingMountRotator.png]]<br />
**'''RA J2000''': Enter the RA coordinates in HH MM SS or HH MM SS.sss<br />
**'''DEC J2000''': Enter the DEC coordinates in DD MM SS or DD MM SS.sss<br />
**'''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.<br />
**'''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.<br />
** '''Rotation Angle:''' an arbitrary angle that can be a Rotator PA or Sky PA, depends on following setting.<br />
** '''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<br />
** '''PA Tollerance +/-:''' if the PA of rotator is inside the interval given the position will be declared ok and rotator will not be rotate.<br />
** '''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.<br />
**'''RoboClip:''' open RoboClip manager windowd and allow to select a target, with RA and DEC will be also acquired the PA<br />
***'''Default''': Use the default settings<br />
***'''OK''': Save changes and close the window<br />
***'''Cancel''': Discard changes and close the window<br />
<br />
<br /><br />
<br />
*'''Stop Tracking (Only FS2 Mount)''': Command an FS2 mount to stop tracking<br />
*'''Start Tracking (Only FS2 Mount)''': Command an FS2 mount to start tracking<br />
*'''FS2 Meridian Flip WEST''': Command an FS2 mount to perform a meridian flip to the West<br />
*'''FS2 Meridian Flip EAST''': Command an FS2 mount to perform a meridian flip to the East <br />{{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}}<br />
<br />
==Dome==<br />
Dome actions send commands to the dome defined in the [[Dome Setup]] area of the active profile:<br />
<br />
[[File:Dragscript-dome-217d.jpg]]<br />
<br />
*'''Open Shutter''': Command the dome's shutter or the observatory's roll-off roof to open<br />
*'''Close Shutter''': Command the dome's shutter or the observatory's roll-off roof to close<br />
*'''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<br />
*'''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<br />
*'''Dome Goto Azimuth''': Command the Dome to rotate to the specified Azimuth<br />
<br />
[[File:Dragscript-dome-az.png]]<br />
<br />
*'''Azimuth''': Azimuth position the mount should move to in degrees<br />
*'''Cancel''': Discard changes and close the window<br />
*'''OK''': Save changes and close the window<br />
<br />
<br /><br />
<br />
*'''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<br />
*'''Dome Park''': Send a Park command to the dome.<br />
*'''Dome Unpark:''' Send an Unpark command to the dome<br />
<br />
<br /><br />
==Camera==<br />
Camera actions can control the camera's cooling system and take exposures<br />
<br />
[[File:Dragscript-camera.png]]<br />
<br />
*'''Cool Down''': Command the camera's cooling system to cool down to a desired temperature:<br />
<br />
[[File:Dragscript-cooldown.png]]<br />
<br />
*'''Final Temperature''': Desired sensor temperature in °C<br />
*'''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<br />
*'''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<br />
*'''Use CCD Firmware Cooldown''': If selected, let the CCD's cooling system manage the speed of the cooldown process<br />
*'''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]]<br />
*'''Default''': Use the default settings<br />
*'''OK''': Save changes and close the window<br />
*'''Cancel''': Discard changes and close the window<br />
<br />
<br /><br />
<br />
*'''Warmup''': Command the camera's cooling system to warmup<br />
<br />
[[File:Dragscript-warmup.png]]<br />
<br />
*'''Async Cooling''': If checked, command the camera's cooling system to warmup and do not wait for the warmup operation to finish<br />
*'''Default''': Use the default settings<br />
*'''OK''': Save changes and close the window<br />
*'''Cancel''': Discard changes and close the window<br />
<br />
<br /><br />
<br />
*'''Expose''': Take an exposure<br />
<br />
[[File:Dragscript-expose-216d.jpg]]<br />
<br />
*'''Exposure Type''': Choose Light, Bias, Dark or Flat from the drop-down list<br />
*'''Filter Index''': Choose the filter for the exposure from the drop-down list<br />
*'''Expose''': Enter the exposure length in seconds in the counter field<br />
*'''Use Variable:''' select if you want to get the exposure time from the decimal variable selected in the near list control<br />
*'''Binning''': Select the binning level for the exposure from the counter field<br />
*'''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<br />
*'''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.<br />
*'''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.<br />
*'''File Directory''': Click the folder icon to select the folder where Voyager should save the image resulting from this exposure<br />
*'''File Name''': Enter the file name to use when saving the image resulting from this exposure<br />
*'''Make Unique File Name''': If checked, add a suffix to the file name if needed to avoid overwriting an existing file<br />
*'''FIT Object Name''': The name to use to populate the OBJECT field in the FITS header<br />
*'''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.<br />
*'''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<br />
*'''Default''': Use the default settings<br />
*'''OK''': Save changes and close the window<br />
*'''Cancel''': Discard changes and close the window<br />
<br />
* '''TheSkyX/64 Camera FW Reconnect''': Reconnect camera and filterwheel if the control used for camera in Voyager is TheSkyX or TheSky64<br />
<br />
<br />
{{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.}}<br /><br />
<br />
{{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)}}<br />
<br />
<br />
{{Note|If you check the use variable flag the exposure time used for the exposure will be added to the name of FIT file}}<br /><br />
<br />
==AutoFocus==<br />
These DragScript commands perform Voyager's autofocus operations:<br />
<br />
[[File:Dragscript-autofocus.png]]<br />
<br />
*'''AutoFocus with RoboStar''': perform an autofocus operation using Voyager's RoboStar method to choose the focus star:<br />
<br />
[[File:Dragscript-autofocus-robostar.png]]<br />
<br />
*'''Monochromatic Camera''': Select if a monochrome camera is connected. Select a filter to use for the autofocus operation from the drop-down list<br />
*'''DSLR/Color Camera''': Select if a DSLR or Color (OSC) camera is connected<br />
*'''No Filter''': Select if a monochrome camera is connected without filters<br />
*'''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<br />
*'''AutoFocus OnPlace''': Perform the autofocus operation at the current scope location. Do not use RoboStar to select a focus star<br />
*'''Default''': Use the default settings<br />
*'''OK''': Save changes and close the window<br />
*'''Cancel''': Discard changes and close the window<br />
<br />
<br /><br />
<br />
*'''Simple Goto RoboStar Star''': Perform a simple goto operation to move the mount to the focus star selected by RoboStar:<br />
<br />
[[File:DSSimpleGotoRoboStar.png]]<br />
<br />
*'''Monochromatic Camera''': Select if a monochrome camera is connected. Select a filter to use for the precise pointing operation from the drop-down list<br />
*'''DSLR/Color Camera''': Select if a DSLR or Color (OSC) camera is connected<br />
*'''No Filter''': Select if a monochrome camera is connected without filters<br />
*'''Default''': Use the default settings<br />
*'''OK''': Save changes and close the window<br />
*'''Cancel''': Discard changes and close the window<br />
<br />
<br /><br />
<br />
*'''Precise Pointing RoboStar Star''': Perform a precise pointing operation to move the mount to the focus star selected by RoboStar:<br />
<br />
[[File:Dragscript-precisepointing-robostar.png]]<br />
<br />
*'''Monochromatic Camera''': Select if a monochrome camera is connected. Select a filter to use for the precise pointing operation from the drop-down list<br />
*'''DSLR/Color Camera''': Select if a DSLR or Color (OSC) camera is connected<br />
*'''No Filter''': Select if a monochrome camera is connected without filters<br />
*'''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<br />
*'''Default''': Use the default settings<br />
*'''OK''': Save changes and close the window<br />
*'''Cancel''': Discard changes and close the window<br />
<br />
<br /><br />
<br />
*'''RoboFire Focuser Move To''': Move the focuser to a specified absolute or relative position:<br />
<br />
[[File:Dragscript-robomove.png]]<br />
<br />
*'''Position''': Desired focuser position in steps<br />
*'''Mode''': Choose absolute or relative<br />
**'''Absolute''': Command the focuser to move to the specified position. Your focuser must support absolute positioning.<br />
**'''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]]<br />
*'''OK''': Save changes and close the window<br />
*'''Cancel''': Discard changes and close the window<br />
<br />
<br />
*'''RoboFire Focuser Move From Variable''': Move the focuser to an absolute or relative position stored in a variable:<br />
<br />
[[File:Dragscript-robomove-variable.png]]<br />
<br />
*'''Get Position From Variable''': select the variable that contains the position<br />
*'''Mode''': Choose absolute or relative<br />
**'''Absolute''': Command the focuser to move to the specified position. Your focuser must support absolute positioning.<br />
**'''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]]<br />
*'''OK''': Save changes and close the window<br />
*'''Cancel''': Discard changes and close the window<br />
<br />
{{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.}}<br />
<br />
<br />
*'''AutoFocus with RoboFire LocalField''': Perform Voyager's LocalField (multiple star) autofocus routine<br />
<br />
[[File:Dragscript-localfield.png]]<br />
<br />
*'''Monochromatic Camera''': Select if a monochrome camera is connected. Select a filter to use for the precise pointing operation from the drop-down list<br />
*'''DSLR/Color Camera''': Select if a DSLR or Color (OSC) camera is connected<br />
*'''No Filter''': Select if a monochrome camera is connected without filters<br />
*'''Default''': Use the default settings<br />
*'''OK''': Save changes and close the window<br />
*'''Cancel''': Discard changes and close the window<br />
<br />
<br /><br />
==Rotator==<br />
Rotator actions can move the rotator to a specified Position Angle or flip the rotator 180 degrees:<br />
<br />
[[File:Dragscript-rotator.png]]<br />
<br />
<br /><br />
<br />
*'''Rotator Move To''': Move the rotator to the specified position angle in degree<br />
**[[File:Dragscript-rotatormove.png]]<br />
***'''PA''': Move the rotator to this Position Angle in degrees<br />
***'''OK''': Save changes and close the window<br />
***'''Cancel''': Discard changes and close the window<br />
<br />
*<br />
*'''Rotator 180° Flip''': Move the rotator to a position 180 degrees opposite its current position<br />
*'''Rotator Sync''': Synchronize the mechanical position to the submitted position (create an offset to the mechanical position)<br />
**[[File:RotatorSyncBlockConf.png]]<br />
***'''Rotator Sync To:''' with this option Voyager will sync the rotator PA to the PA in the next field<br />
***'''PA:''' Position Angle to use for sync<br />
***'''Use Variable:''' get PA value from the selected variable<br />
***'''Reset Rotator Sync:''' with this option Voyager will reset the Sync (remove the offset applied to the mechanical position of rotator)<br />
***'''Default:''' reset all parameters in the form to the default values<br />
***'''Cancel:''' exit from the configuration form without saving anything<br />
***'''OK:''' accept the inserted value and store data<br />
<br />
* '''Precise Rotate SkyPA''': Move the rotator to the specified SkyPA position<br />
** [[File:PRSKYPADS.png]]<br />
*** '''Rotation Angle''': SKY PA in degree to use for positioning the rotator<br />
*** '''PA Tollerance +/-''': max allowed difference in degree between solved PA and requested PA<br />
*** '''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<br />
*** '''OK''': Save changes and close the window<br />
*** '''Cancel''': Discard changes and close the window<br />
<br />
==Flat Device==<br />
Flat Device commands can open and close the flat device cover:<br />
<br />
[[File:Dragscript-flat-device.jpg]]<br />
<br />
*'''Open Flat Device Cover''': Command the flat device to open<br />
*'''Close Flat Device Cover''': Command the flat device to close<br />
*'''Switch On Light Flat Device''': Turn the light on for the specified Flat Device<br />
<br />
[[File:Dragscript-switch-on-flat-device.jpg]]<br />
<br />
*'''Device ID''': Choose the Flat Device number to control with this command. See [[Flat Device Setup]] for more information on flat devices.<br />
<br />
<br /><br />
<br />
*'''Switch Off Light Flat Device''': Turn the light off for the specified Flat Device<br />
<br />
[[File:Dragscript-switch-off-flat-device.jpg]]<br />
<br />
*'''Device ID''': Choose the Flat Device number to control with this command. See [[Flat Device Setup]] for more information on flat devices.<br />
<br />
<br /><br />
<br />
*'''Select Brightness Flat Device''': Set the brightness level for the specified Flat Device.<br />
<br />
[[File:Dragscript-select-brightness.jpg]]<br />
<br />
*'''Device ID''': Choose the Flat Device number to control with this command. See [[Flat Device Setup]] for more information on flat devices.<br />
*'''Brightness''': Brightness level for the specified Flat Device.<br /><br />
{{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!}}<br />
<br />
==Script==<br />
The Script action can run an external script or program:<br />
<br />
[[File:Dragscript-script-external.png]]<br />
<br />
[[File:External-script-1.png]]<br />
<br />
*'''File Program/Script''': Click the folder icon to select the program or script to run<br />
*'''Arguments''': Command line arguments to be passed to the program or script when invoking it<br />
*'''Wait For Program/Script''': If checked, wait for the program or script to return before continuing (synchronous execution)<br />
*'''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<br />
*'''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<br />
*'''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<br />
*'''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<br />
*'''Default''': Use the default settings<br />
*'''OK''': Save changes and close the window<br />
*'''Cancel''': Discard changes and close the window<br /><br />
{{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}}<br /><br />
{{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}}<br />
<br />
<br />
'''Example of Use'''<br />
<br />
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.<br />
<br />
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.<br />
<br />
[[File:Script-scheduler-example.jpg]]<br />
<br />
<br /><br />
==Timing==<br />
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:<br />
<br />[[File:Dragscript-timing-211a.jpg]]<br />
<br />
*'''Wait Time''': Wait for a specified time to arrive or to elapse<br />
<br />
[[File:Dragscript-waittime.png]]<br />
<br />
*'''Interval/Time''': Enter a time in HH MM SS.<br />
*'''Wait Type''': Chose Absolute or Relative<br />
**'''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<br />
**'''Relative''': Wait for this amount of time to elapse<br />
*'''OK''': Save changes and close the window<br />
*'''Cancel''': Discard changes and close the window<br /><br />
<br />
<br /><br />
<br />
*'''Wait Altitude''': Wait until the object at the given RA and DEC coordinates reaches the specified altitude, either rising or setting:<br />
<br />
[[File:Dragscript-wait-altitude.png]]<br />
<br />
*'''RA Target J2000''': RA coordinates of the object you want to reach the Reference Altitude in HH MM SS or HH MM SS.sss<br />
*'''DEC Target J2000''': DEC coordinates of the object you want to reach the Reference Altitude in DD MM SS or DD MM SS.sss<br />
*'''Reference Altitude''': Altitude to reach in degrees<br />
*'''Exit Wait if Actual Altitude GREATER than or EQUAL (>=) to reference''': Wait until the target rises above the reference altitude<br />
*'''Exit Wait if Actual Altitude LOWER than or EQUAL (>=) to reference''': Wait until the target sets below the reference altitude<br />
*'''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<br />
* '''RoboClip:''' load RA and DEC from RoboClip catalog<br />
* '''Coords From Sequence:''' load RA and DEC from a sequence file<br />
*'''Default''': Use the default settings<br />
*'''OK''': Save changes and close the window<br />
*'''Cancel''': Discard changes and close the window<br />
<br />
<br /><br />
<br />
*<br />
<br />
*'''Wait Astronomical/Nautical/Civil Night''': Wait until astronomical/nautical/civil night, with an optional offset:<br />
<br />
[[File:Dragscript-wait-night.png]]<br />
<br />
*'''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<br />
*'''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<br />
*'''Offset''': Time in HH MM SS <br />
**'''Offset Before''': If selected, exit the wait this amount of time before night<br />
**'''Offset After''': If selected, exit the wait this amount of time after night<br />
*'''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<br />
*'''Default''': Use the default settings<br />
*'''OK''': Save changes and close the window<br />
*'''Cancel''': Discard changes and close the window<br />
*<br />
*<br />
*'''Wait Dusk'''<br />[[File:Dragscript-wait-dusk.jpg]]<br />
<br />
*'''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<br />
*'''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<br />
*'''Offset''': Time in HH MM SS <br />
**'''Offset Before''': If selected, exit the wait this amount of time before dusk<br />
**'''Offset After''': If selected, exit the wait this amount of time after dusk<br />
*'''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.<br />
*'''Default''': Use the default settings<br />
*'''OK''': Save changes and close the window<br />
*'''Cancel''': Discard changes and close the window<br />
<br />
<br />
<br />
You can configure the time at which dusk begins in the [[Flat Device Setup#Sky Flat|SkyFlat section of Flat Device]] Setup.<br />{{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}}<br />
<br />
<br />
*'''Wait Dawn'''<br />
<br />
[[File:Wait-dawn-2.jpg]]<br />
<br />
*'''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<br />
*'''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<br />
*'''Offset''': Time in HH MM SS <br />
**'''Offset Before''': If selected, exit the wait this amount of time before dawn<br />
**'''Offset After''': If selected, exit the wait this amount of time after dawn<br />
*'''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.<br />
*'''Default''': Use the default settings<br />
*'''OK''': Save changes and close the window<br />
*'''Cancel''': Discard changes and close the window<br />
<br />
<br />
You can configure the time at which dawn begins in the [[Flat Device Setup#Sky Flat|SkyFlat section of Flat Device]] Setup.<br />
<br />{{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}}<br />
<br />
<br />
*<br />
<br />
*'''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.<br />
<br />
{{Note|Wait SAFE Cannot be used inside the Event Manager (Exit, Suspend, Resume)}}<br />
<br />
<br />
[[File:DSWaitSafe.png]]<br />
<br />
*'''Wait SAFE until finish Night''': this option wait SAFE status until on eof specified kind of Nights is finished <br />
**'''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<br />
**'''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<br />
**'''Night TYPE:''' the night to wait between Astronomical (Astrophotographers dark night -18° sun) , Nautical (-12° sun), Civil (-6° sun)<br />
**'''Offset''': Time in HH MM SS <br />
***'''Offset Before''': If selected, exit the wait this amount of time before astronomical night<br />
***'''Offset After''': If selected, exit the wait this amount of time after astronomical night<br />
*'''Wait SAFE until absolute time''': this option wait SAFE status until the absolute time you put inside the hh mm ss field<br />
*'''Wait SAFE for a time interval of:''' this option wait SAFE status until the amount of time in the interval will be elapsed<br />
*'''EXIT Options:''' with this options you can decide to exit with ERROR it the conditions inside is true<br />
**'''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.<br />
**'''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.<br />
*'''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)<br />
**'''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<br />
**'''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.<br />
*'''LIGHT CONDITIONS options:''' with this option you can decide to remove from processing status of SAFE the LIGHT Conditions status<br />
**'''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<br />
*'''Default''': Use the default settings<br />
*'''OK''': Save changes and close the window<br />
*'''Cancel''': Discard changes and close the window<br />
<br />
<br />
==Using the Time to Event Value in a DragScript==<br />
Here's an example of using the '''Save Time to Event (minutes)''' value in a DragScript.<br />
<br />
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.<br />
<br />
[[File:Dragscript-wait-dawn-2.jpg]]<br />
<br />
The decimal variable "'''Minutes Before Event'''" is initialized to 0.<br />
<br />
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'''<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
<br /><br /><br />
<br />
==Signals==<br />
Signals actions let you send notifications via email, Skype or SMS:<br />
<br />
<br />
[[File:Dragscript-signals.png]]<br />
<br />
{{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.}}<br />
<br />
[[File:Dragscript-editor-toolbar-3.png]]<br />
<br />
Use button 5 to save your DragScript with the personal info deleted for any of the actions in this group (Signals).<br />
<br />
<br /><br />
<br />
*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<br />
<br />
[[File:Dragscript-send-email.png]]<br />
<br />
*'''Mail to''': Email address to send to<br />
*'''Object''': Subject line of email TYPO: Should be Subject instead of Object<br />
*'''Text''': Body of email<br />
*'''Cancel''': Discard changes and close the window<br />
*'''OK''': Save changes and close the window<br />
*'''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<br />
**'''Internal IPs:''' ##INTERNAL-IP## write a list of all internal IPs avalaible in the system<br />
**'''External IP''': ##EXTERNAL-IP## write a list of external IP assigned to your PC(router) if you have internet connection up<br />
**'''NOW''': ##NOW## write the actual date and time<br />
**'''Mount Altitude''': ##MOUNT-ALT## write the actual altitude of Telescope Mount if connected<br />
**'''Mount Azimuth''': ##MOUNT-AZ## write the actual azimuth of Telescope Mount if connected<br />
**'''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)<br />
<br />
<br /><br />
<br />
*'''Send Email''': Send an email notification using a specified email server and account. Requires an Internet connection<br />
<br />
[[File:Dragscript-sendemail.png]]<br />
<br />
*'''Mail From''': Email address this message is from<br />
*'''Mail to''': Email address to send to<br />
*'''Object''': Subject line of email TYPO: Should be Subject instead of Object<br />
*'''Text''': Body of email<br />
*'''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<br />
*'''SMTP Password''': Password to login to your SMTP (mail) server<br />
*'''SMTP Server''': Hostname or IP address of your SMTP (mail) server<br />
*'''SMTP Port''': Port number of your SMTP (mail) server<br />
*'''Use SSL''': If checked, use an SSL (secure) connection to your mail server<br />
*'''GMAIL''': Click this button to use the SMTP server and port information for Google Gmail<br />
*'''HOTMAIL''': Click this button to use the SMTP server and port information for Microsoft Hotmail<br />
*'''Cancel''': Discard changes and close the window<br />
*'''OK''': Save changes and close the window<br />
<br />
*'''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<br />
**'''Internal IPs:''' ##INTERNAL-IP## write a list of all internal IPs avalaible in the system<br />
**'''External IP''': ##EXTERNAL-IP## write a list of external IP assigned to your PC(router) if you have internet connection up<br />
**'''NOW''': ##NOW## write the actual date and time<br />
**'''Mount Altitude''': ##MOUNT-ALT## write the actual altitude of Telescope Mount if connected<br />
**'''Mount Azimuth''': ##MOUNT-AZ## write the actual azimuth of Telescope Mount if connected<br />
**'''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)<br />
<br />
<br /><br />
<br />
*'''Start Skype Call''': Start a Skype call from the computer running Voyager. Requires an Internet connection<br />
<br />
[[File:Dragscript-skype.png]]<br />
<br />
*'''Phone Number to Call''': Phone number or Skype name to call using Skype<br />
*'''After Command Wait''': Time in seconds to wait after sending the command before timing out if no response from Skype<br />
*'''After leave ringing for''': Time in seconds to wait after Skype places the call and the remote phone starts to ring<br />
*'''Skype Exe Directory''': Location of Skype program on this computer<br />
*'''Find Skype''': Look for Skype program on this computer and fill out the Skype Exe Directory if found<br />
*'''Test''': Try to make a Skype call using the information in this dialog window<br />
*'''Cancel''': Discard changes and close the window<br />
*'''OK''': Save changes and close the window<br />
<br />
<br /><br />
<br />
*'''Send SMS with Nexmo'''<br />
**Send an SMS (text message) using the Nexmo service: https://www.nexmo.com/ Requires an Internet connection.<br />
<br />
[[File:Dragscript-nexmo.png]]<br />
<br />
*'''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)<br />
*'''To Telephone Number''': Phone number to send SMS message to<br />
*'''Text''': Body of SMS messages<br />
*'''API Key''': API Key for Nexmo service - you must sign up at https://www.nexmo.com/ to get an API key and secret<br />
*'''API Secret''': API Secret for Nexmo service<br />
*'''Cancel''': Discard changes and close the window<br />
*'''OK''': Save changes and close the window<br />
<br />
*'''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<br />
**'''Internal IPs:''' ##INTERNAL-IP## write a list of all internal IPs avalaible in the system<br />
**'''External IP''': ##EXTERNAL-IP## write a list of external IP assigned to your PC(router) if you have internet connection up<br />
**'''NOW''': ##NOW## write the actual date and time<br />
**'''Mount Altitude''': ##MOUNT-ALT## write the actual altitude of Telescope Mount if connected<br />
**'''Mount Azimuth''': ##MOUNT-AZ## write the actual azimuth of Telescope Mount if connected<br />
**'''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)<br />
<br />
<br /><br />
{{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}}<br />
<br />
<br /><br />
<br />
* '''Send Telegram'''<br />
** Send an message using Telegram service chatbot: https://www.telgram.org/ Requires an Internet connection.<br />
** [[File:SaveTelegramBlock.png]]<br />
<br />
* '''Text''': message<br />
* '''API ID''': API ID (token create during the chatbot) of your Telegram user<br />
* '''Chat ID''': ID number assigned to chatbot created, you can get opening the link [https://api.telegram.org/bot&#x3C;your https://api.telegram.org/bot<YOUR_TOKEN>/getUpdates]<br />
* '''Cancel''': Discard changes and close the window<br />
* '''OK''': Save changes and close the window<br />
<br />
* '''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<br />
**'''Internal IPs:''' ##INTERNAL-IP## write a list of all internal IPs avalaible in the system<br />
** '''External IP''': ##EXTERNAL-IP## write a list of external IP assigned to your PC(router) if you have internet connection up<br />
** '''NOW''': ##NOW## write the actual date and time<br />
** '''Mount Altitude''': ##MOUNT-ALT## write the actual altitude of Telescope Mount if connected<br />
**'''Mount Azimuth''': ##MOUNT-AZ## write the actual azimuth of Telescope Mount if connected<br />
**'''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)<br />
'''Guide to obtain API ID and Chat ID''' : <br />
<br />
# Download the Telegram APP on your mobile phone and register<br />
# Open a chat with @BotFather and type /newbot to create a new private bot<br />
# You will be asked for a friendly name - choose whatever you like, e.g. VoyagerMessages<br />
# 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<br />
# 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<br />
# You will get a short message that starts with {"ok":true. It won't have the Chat ID yet - this is OK<br />
# 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<br />
# Type at least one message - a simple "hello" will do<br />
# 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<br />
# 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<br />
# That's it - you can now use the API ID and Chat ID to send Telegram messages from your DragScript<br />
<br />
<br />
==User Manual Input==<br />
User manual input actions allow interactions between Voyager and the user:<br />
<br />
<br />
[[File:DragScriptUserInter.png]]<br />
<br />
<br /><br />
<br />
*'''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<br />
*[[File:DragScriptWaitUser.png]]<br />
*'''Wait Mode''': how the wait will be work<br />
*'''Use Timeout of:''' with this option the wait will finish in anycase after the seconds selected<br />
*'''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<br />
*'''No Timeout:''' with this option the wait will be for ever until physically user press the button on the screen<br />
*'''Message:''' show a text message inside window prompt to the user<br />
*'''Show Variable Value:''' show a text rappresentation of the variable selected inside window prompt to the user<br />
*'''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.<br />
*[[File:Immaginewefwef.png]]<br />
*'''Wait Mode''': how the wait will be work<br />
*'''Use Timeout of:''' with this option the wait will finish in anycase after the seconds selected<br />
*'''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<br />
*'''No Timeout:''' with this option the wait will be for ever until physically user press the button on the screen<br />
*'''Message:''' show a text message inside window prompt to the user<br />
*'''Show Variable Value:''' show a text rappresentation of the variable selected inside window prompt to the user<br />
*'''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.<br /><br />
{{Note|if you using No Timeout option you must be really to be present in front of your PC to continue}}<br />
<br />
==Optec Perseus==<br />
Optec Perseus actions allow to interact with the hardware [https://optecinc.com/astronomy/catalog/perseus/default.htm Port Instrument Selector from Optec] :<br />
<br />
<br />
[[File:OptecPer1.png]]<br />
<br />
<br /><br />
<br />
*'''Optec Perseus Read Device Info''': ask information about device and save it in environment variables of DragScript<br />
*'''Optec Perseus Read Device Status''': ask status of device and save it in environment variables of DragScript<br />
*'''Optec Perseus Homing''': command to device to Homing<br />
*'''Optec Perseus Set Port:''' rotate device to select the port selected index<br />
**[[File:OptecPer2.png]]<br />
**'''Port:''' port index to select<br />
<br />
<br /><br />
{{Note|ASCOM Switch driver of Optec Perseus must be installed in order to allow working the DragScript Blocks}}<br />
<br />
== Donuts ==<br />
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 :<br />
<br />
<br />
[[File:DonutsSection.png]]<br />
<br />
*'''Donuts Calibration''': ask to Donuts process to performe a Calibration using camera and mount<br />
<br />
[[Category:DragScript]]<br />
[[Category:All]]<br />
[[Category:Manual|Lb]]</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=AutoFocus_Setup&diff=5660AutoFocus Setup2020-10-14T09:57:11Z<p>Rowland: /* Other Setup Pages */</p>
<hr />
<div>==AutoFocus Setup Video==<br />
There is a video on setting up AutoFocus on the Voyager Astro Imaging YouTube Channel<br />
<br />
<youtube>https://www.youtube.com/watch?v=VkWxrhRN_ns&t=2s</youtube><br />
<br />
==AutoFocus Setup Workspace==<br />
The AutoFocus Setup workspace is where you store settings for Voyager's autofocus operations:<br />
<br />
[[File:Autofocus-setup-2.12e.png]]<br />
<br />
<br /><br />
<br />
==Color Coding==<br />
Throughout the Setup workspace, Voyager uses color to indicate the following:<br />
<br />
*'''Black''': A normal setting<br />
*<span style="color:#E7C63B;"><strong>Gold or Yellow</strong></span>: Use caution when changing as things may not work well or as expected<br />
*<span style="color:#E37D6E;"><strong>Red</strong></span>: Use extreme care when changing this setting - the wrong value can damage your equipment or the imaging session may fail<br />
<br />
==AutoFocus Choice==<br />
Select the AutoFocus program you want to use at the top of the AutoFocus Setup workspace:<br />
<br />
[[File:Autofocus-choice.jpg]]<br />
<br />
*AutoFocus: Select the autofocus program from the options in the drop-down list<br />
<br />
<br />
[[File:Autofocus-selections.jpg]]<br />
<br />
*Available selections include None, FocusMax, TheSkyX @Focus2, Maxim DL, RoboFire, and TheSkyX @Focus3<br />
<br />
*FocusMax is a product of CCDWare: http://www.ccdware.com/products/focusmax/<br />
*TheSkyX has two autofocus routines: @Focus2 and @Focus3. TheSkyX is a product of Software Bisque: http://www.bisque.com/sc/pages/TheSkyX-Editions.aspx<br />
*Maxim DL is a product of Diffraction Limited: http://diffractionlimited.com/product/maxim-dl/<br />
*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)<br />
<br />
{{Note|RoboFire Autofocus doesn't allow use of focuser with relative driver movements mode ... only absolute ASCOM driver}}<br />
<br />
{{Note|RoboFire Autofocus is not compatible (at now) with Baader SteelDrive focusers}}<br />
<br />
==Focuser Choice==<br />
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:<br />
<br />
[[File:Autofocus-choice.jpg]]<br />
<br />
<br />
If you use any of the other autofocus options, you must set up the focuser in those programs, not in Voyager.<br />
<br />
==Focus Result Watchdog==<br />
The Focus Result Watchdog panel in the AutoFocus Setup workspace has several parameters controlling whether an autofocus operation is considered successful:<br />
<br />
[[File:Focus-result-watchdog.jpg]]<br />
<br />
*'''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<br />
*'''Retry Focus For Watchdog''': The number of times an autofocus routine will be tried before giving up<br />
*'''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.<br />
<br />
<br /><br />
==Work Around==<br />
The Work Around panel in the AutoFocus Setup workspace contains a parameter to prevent focuser motion from stopping after a HALT ALL command:<br />
<br />
[[File:Autofocus-workaround-2.12e.png]]<br />
<br />
*'''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.<br />
*'''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.<br />
*'''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<br />
<br />
<br /><br />
==RoboStar General Setting==<br />
The RoboStar General Setting panel in the AutoFocus Setup workspace contains parameters for Voyager's RoboStar operation, which automatically selects a focus star:<br />
<br />
[[File:Robostar-general-setting.jpg]]<br />
<br />
<br /><br />
<br />
*'''Degree''': 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.<br />
*'''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<br />
{{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}}<br />
<br />
<br />
<br />
[[File:Wrong-star-manager.jpg]]<br />
<br />
*'''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.<br />
<br />
[[File:Filter-setup-1.jpg]]<br />
<br />
*Documentation for the Filter Setup dialog is here: [[Camera Setup#Filter Setup|'''Filter Setup''']]<br />
*'''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.<br />
<br />
==TheSkyX @Focus3 Setting==<br />
The TheSkyX @Focus3 Setting panel in the AutoFocus Setup workspace contains parameters for TheSkyX @Focus3<br />
<br />
[[File:Theskyx-atfocus3.jpg]]<br />
<br />
*'''Starting Focus Exposure Time''': Exposure length in seconds to be used by TheSkyX's @Focus3 autofocus routine<br />
*'''Sample Averaging Number''': The number of exposures to take at each focuser position by TheSkyX's @Focus3 autofocus routine<br />
<br />
==RoboFire General Setting==<br />
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:<br />
<br />
[[File:Robofire-setting.jpg]]<br />
<br />
*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<br />
<br />
==RoboFire VCurve vs. LocalField: Which to Use When?==<br />
Voyager has two different autofocus methods: VCurve (single-star) and LocalField (multiple-star). <br />
<br />
*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.<br />
*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.<br />
<br />
<br /><br />
<br />
{{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}}<br />
<br />
==RoboFire Configuration Center==<br />
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. <br />
<br />
===Focuser Tab===<br />
[[File:Robofire-config-focuser.jpg]]<br />
<br />
*'''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.<br />
*'''Limits:''' <br />
**'''IN Limit''': The minimum position (furthest in) of the Focuser in steps<br />
**'''OUT Limit''': The maximum position (furthest out) of the Focuser in steps<br />
*'''Backlash Compensation''': <br />
**'''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<br />
**'''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)<br />
**'''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<br />
*'''Advanced:''' <br />
**'''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.<br />
**'''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<br />
**'''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<br />
<br />
===VCurve Mode Tab===<br />
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.<br />
<br />
<br />
VCurve from a RoboFire autofocus run<br />
[[File:VCurveRun.png|none|thumb|745x745px]]<br />
<br />
<br />
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.<br />
<br />
[[File:Focuser-vcurve-1.jpg]]<br />
<br />
*'''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. <br />
**'''Slope Left''': The slope of the left portion of the VCurve<br />
**'''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.<br />
**'''Step Inc''': The number of focuser steps between each measured point on the VCurve<br />
**'''Slope Right''': The slope of the right portion of the VCurve<br />
<br />
<br />
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. <br />
<br />
[[File:Vcurve-data-1.jpg]]<br /><br />
<br />
*'''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.<br />
*'''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.<br />
*'''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.<br />
*'''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.<br />
*'''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.<br />
*'''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.<br />
<br />
<br />
Returning to the RoboFire Configuration dialog, VCurve Mode tab:<br />
[[File:Focuser-vcurve-1.jpg|none|frame]]<br />
<br />
*'''COMMON Parameters''':<br />
**'''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.<br />
*'''HFD Parameters''': HFD is the Half Flux Diameter of the focus star<br />
**'''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.<br />
**'''Start Focus''': The HFD of the focus star at which to start the autofocus operation<br />
**'''VCurve Limit''': The HFD value at the beginning and end of the VCurve<br />
*'''Star Flux Parameters''':<br />
**'''MIN Flux''': Minimum (dimmest) flux of the focus star. The number entered is multiplied by 1000 to determine the minimum star flux<br />
**'''MAX Flux''': Maximum (brightest) flux of the focus star. The number entered is multiplied by 1000 to determine the maximum star flux<br />
*'''Camera Parameters''':<br />
**'''Bit/Pixel''': BIts per pixel of the imaging camera's sensor<br />
**'''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<br />
**'''Central Region''': The percentage of the overall camera frame used as the central region. Focus stars must be within this region<br />
**'''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<br />
**'''Focus Bin''': The binning used for exposures taken during autofocus<br />
**'''Filter for VCurve''': Filter used for exposures taken while building a VCurve<br />
*'''Exposure Parameters''':<br />
**'''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<br />
**'''Default Time''': This is the exposure time, in seconds, used for the initial image taken by the RoboFire autofocus routine<br />
**'''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<br />
*'''Max HFD Error for Algorithm to find Top, Start and Near Focus''':<br />
**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)<br />
**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<br />
**'''Absolute Diff''': If the radio button for this choice is selected, the maximum HFD error allowed is this number expressed in pixels<br />
**'''Percentage''': If the radio button for this choice is selected, the maximum HFD error allowed during autofocus is this percentage<br />
<br />
<br /><br />
<br />
===LocalField Mode Tab===<br />
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.<br />
<br />
Prior to Voyager 2.1.1e, the LocalField tab looked like this: (see below for the new one)<br />
<br />
[[File:Localfield-mode.jpg]]<br />
<br />
*'''Camera and Exposure Parameters'''<br />
**'''Focus Bin''': The binning used for LocalField autofocus exposures<br />
**'''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]]<br />
**'''Central Region''': The percent of the image's central region used by the LocalField autofocus operation<br />
*'''LocalField AI Engine''':<br />
**'''Focuser Step x Sample''': <br />
***'''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<br />
***'''Manual''': Choose this radio button to enter the step size manually<br />
**'''Sample''': The number of exposures to take during the LocalField autofocus operation. One sample is taken at each focuser position<br />
**'''Minimum Stars Number''': LocalField autofocus will require at least this number of stars in each exposure to be successful<br />
*'''Advanced Settings''':<br />
**'''Min HFD Gap''': a minimum pixel gap from the minimum value of HFD and maximum value of HFD found during the LocalFIeld sampling<br />
**'''Min Confidence''': The minimum statistical confidence percentage to consider autofocus successful<br />
**'''Focus Window Size''': The percentage of the image (Central Region of CCD) used during the autofocus routine<br />
**'''Fit Order''': Curve FIT order in AI analysis of results<br />
*'''Reset to Default''': Reset all LocalField Mode settings to Voyager's defaults<br />
<br />
<br />
As of Voyager 2.1.1e, the labels in the LocalField setup tab have been changed to make them easier to understand:<br />
<br />
[[File:Localfield-setup-211e.jpg]]<br /><br />
<br />
*'''Camera and Exposure Parameters'''<br />
**'''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'''<br />
**'''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<br />
**'''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<br />
**'''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<br />
*'''LocalField AI Engine''':<br />
**'''Focuser Step x Sample''': <br />
***'''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<br />
***'''Manual''': Choose this radio button to enter the step size manually<br />
**'''Sample''': The number of exposures to take during the LocalField autofocus operation. One sample is taken at each focuser position<br />
**'''Minimum Stars Number''': LocalField autofocus will require at least this number of stars in each exposure to be successful<br />
*'''Advanced Settings''':<br />
**'''Min HFD Gap''': a minimum pixel gap from the minimum value of HFD and maximum value of HFD found during the LocalFIeld sampling<br />
**'''Min Confidence''': The minimum statistical confidence percentage to consider autofocus successful<br />
**'''Focus Window Size''': The percentage of the image (Central Region of CCD) used during the autofocus routine<br />
**'''Fit Order''': Curve FIT order in AI analysis of results<br />
*'''Reset to Default''': Reset all LocalField Mode settings to Voyager's defaults<br />
<br />
===Various Tab===<br />
The final tab of the RoboFire Configuration dialog contains some miscellaneous parameters:<br />
<br />
[[File:Robofire-various.jpg]]<br />
<br />
*'''Dashboard''': <br />
**'''Show Dashboard During RoboFire Actions''': If checked, the RoboFire dashboard appears while the autofocus operations are in progress<br />
**'''Dashboard on Top''': If checked, keep the RoboFire Dashboard on top of other windows while it is active<br />
**'''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<br />
*'''Workaround'''<br />
**'''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<br />
<br />
* '''FIT'''<br />
**'''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<br />
<br />
==Point Closest Focus Star with RoboStar==<br />
[[File:Point-focus-star.jpg]]<br />
<br />
This button starts a RoboStar operation to find a suitable nearby focus star. <br />
<br />
{{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.}}<br /><br />
<br />
==VCurve First Light Wizard==<br />
[[File:Vcurve-first-light.jpg]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
[[File:Vcurve-wizard.jpg]]<br />
<br />
When you have read and followed all the steps in this panel, click the OK button to immediately run the VCurve First Light Wizard<br />
<br />
<br />
TODO: Run the wizard and capture screen shots<br />
<br />
{{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}}<br />
<br />
{{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}}<br /><br />
==Add New VCurve==<br />
[[File:Add-new-vcurve.jpg]]<br />
<br />
Click this button to run an immediate operation to take exposures as specified in the RoboFire Configuration Center to calculate a VCurve.<br />
{{Note|You must run the VCurve First Light Wizard before running the Add New VCurve operation}}<br />
<br />
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. <br />
<br />
TODO: Run this command and capture screen shots<br />
<br />
<br /><br />
==Test AutoFocus VCurve==<br />
[[File:Test-autofocus-vcurve.jpg]]<br />Click this button to run a RoboFire autofocus operation to test the VCurve parameters with a real life autofocus<br />
<br />
<br />
TODO: Run and capture screen shot<br />
<br /><br />
==Other Setup Pages==<br />
<categorytree mode="pages" depth="1">Setup</categorytree><br />
<br />
[[Category:Setup]]<br />
[[Category:All]]<br />
[[Category:Manual|Hf]]</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=Rotator_Setup&diff=5659Rotator Setup2020-10-14T09:56:07Z<p>Rowland: /* Other Setup Pages */</p>
<hr />
<div>==Color Coding==<br />
Throughout the Setup workspace, Voyager uses color to indicate the following:<br />
<br />
*'''Black''': A normal setting<br />
*<span style="color:#E7C63B;"><strong>Gold or Yellow</strong></span>: Use caution when changing as things may not work well or as expected<br />
*<span style="color:#E37D6E;"><strong>Red</strong></span>: Use extreme care when changing this setting - the wrong value can damage your equipment or the imaging session may fail<br />
<br />
==Rotator Setup Workspace==<br />
Click the Rotator button in the Setup workspace to display the Rotator Setup window:<br />
<br />
[[File:Rotator-setup.jpg]]<br />
<br />
<br /><br />
<br />
==Rotator Choice==<br />
Select your rotator from the drop-down list at the top of the Rotator Setup window:<br />
<br />
[[File:Rotator-choice-1.jpg]]<br />
<br />
*The options are None for no rotator and ASCOM Rotator for a rotator controlled via an ASCOM driver.<br />
*Click the ASCOM button to choose the ASCOM driver for your rotator<br />
<br />
<br /><br />
<br />
==Sync Management==<br />
For sync we talk about synchronize the position angle of the rotator to the position angle of the sky. Voyager can manage Rotator Sync based on the driver capabilities:<br />
<br />
- (A) Driver without Sync (like ones with ASCOM Interface V2)<br />
<br />
- (B) Driver with Sync (like ones with ASCOM Interface V3)<br />
<br />
The value of offset for Sync can be managed using the Sync button in Rotator Command Widget in Voyager GUI column Command.<br />
<br />
You will input manually the angle to sync.<br />
<br />
If you have driver type (A) Voyager will calculate automatically for you the Offset and value will be stored in actual Voyager Profile. You might have more Voyager profiles with different offset if you sharing the same driver and rotator.<br />
<br />
If you have driver type (B) ASCOM Driver will calculate automatically for you the Offset and value will be stored in ASCOM driver settings permanently. Value stored will be equal for all Voyager setup profiles in case of driver and rotator sharing.<br />
<br />
<br /><br />
<br />
==Rotator Workaround==<br />
The Rotator Workaround panel of the Rotator Setup workspace contains a workaround for rotators that require a delay after finishing the move and before resuming exposures:<br />
<br />
[[File:Rotator-workaround.jpg]]<br />
<br />
*Wait Time After Rotator FInished Move: Check the box and enter the delay time in seconds if your rotator requires Voyager to delay the next action after the rotator move finishes. This can be helpful if your rotator returns from the "Move" command before it actually finishes the rotation, or if a delay is required after the move completes to allow vibrations to settle down. Some rotator drivers report rotation is finished before the rotator has actually stopped. This can cause elongated stars if the next exposure starts immediately<br />
<br />
<br /><br />
==Other Setup Pages==<br />
<categorytree mode="pages" depth="1">Setup</categorytree><br />
<br />
[[Category:Setup]]<br />
[[Category:All]]<br />
[[Category:Manual|Hg]]</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=Rotator_Setup&diff=5658Rotator Setup2020-10-14T09:51:49Z<p>Rowland: /* Other Setup Pages */</p>
<hr />
<div>==Color Coding==<br />
Throughout the Setup workspace, Voyager uses color to indicate the following:<br />
<br />
*'''Black''': A normal setting<br />
*<span style="color:#E7C63B;"><strong>Gold or Yellow</strong></span>: Use caution when changing as things may not work well or as expected<br />
*<span style="color:#E37D6E;"><strong>Red</strong></span>: Use extreme care when changing this setting - the wrong value can damage your equipment or the imaging session may fail<br />
<br />
==Rotator Setup Workspace==<br />
Click the Rotator button in the Setup workspace to display the Rotator Setup window:<br />
<br />
[[File:Rotator-setup.jpg]]<br />
<br />
<br /><br />
<br />
==Rotator Choice==<br />
Select your rotator from the drop-down list at the top of the Rotator Setup window:<br />
<br />
[[File:Rotator-choice-1.jpg]]<br />
<br />
*The options are None for no rotator and ASCOM Rotator for a rotator controlled via an ASCOM driver.<br />
*Click the ASCOM button to choose the ASCOM driver for your rotator<br />
<br />
<br /><br />
<br />
==Sync Management==<br />
For sync we talk about synchronize the position angle of the rotator to the position angle of the sky. Voyager can manage Rotator Sync based on the driver capabilities:<br />
<br />
- (A) Driver without Sync (like ones with ASCOM Interface V2)<br />
<br />
- (B) Driver with Sync (like ones with ASCOM Interface V3)<br />
<br />
The value of offset for Sync can be managed using the Sync button in Rotator Command Widget in Voyager GUI column Command.<br />
<br />
You will input manually the angle to sync.<br />
<br />
If you have driver type (A) Voyager will calculate automatically for you the Offset and value will be stored in actual Voyager Profile. You might have more Voyager profiles with different offset if you sharing the same driver and rotator.<br />
<br />
If you have driver type (B) ASCOM Driver will calculate automatically for you the Offset and value will be stored in ASCOM driver settings permanently. Value stored will be equal for all Voyager setup profiles in case of driver and rotator sharing.<br />
<br />
<br /><br />
<br />
==Rotator Workaround==<br />
The Rotator Workaround panel of the Rotator Setup workspace contains a workaround for rotators that require a delay after finishing the move and before resuming exposures:<br />
<br />
[[File:Rotator-workaround.jpg]]<br />
<br />
*Wait Time After Rotator FInished Move: Check the box and enter the delay time in seconds if your rotator requires Voyager to delay the next action after the rotator move finishes. This can be helpful if your rotator returns from the "Move" command before it actually finishes the rotation, or if a delay is required after the move completes to allow vibrations to settle down. Some rotator drivers report rotation is finished before the rotator has actually stopped. This can cause elongated stars if the next exposure starts immediately<br />
<br />
<br /><br />
==Other Setup Pages==<br />
<categorytree mode="pages" depth="1">Setup</categorytree><br />
{{#categorytree:Setup|mode="pages"}}<br />
[[Category:Setup]]<br />
[[Category:All]]<br />
[[Category:Manual|Hg]]</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=AutoFocus_Setup&diff=5657AutoFocus Setup2020-10-14T09:49:39Z<p>Rowland: /* Other Setup Pages */</p>
<hr />
<div>==AutoFocus Setup Video==<br />
There is a video on setting up AutoFocus on the Voyager Astro Imaging YouTube Channel<br />
<br />
<youtube>https://www.youtube.com/watch?v=VkWxrhRN_ns&t=2s</youtube><br />
<br />
==AutoFocus Setup Workspace==<br />
The AutoFocus Setup workspace is where you store settings for Voyager's autofocus operations:<br />
<br />
[[File:Autofocus-setup-2.12e.png]]<br />
<br />
<br /><br />
<br />
==Color Coding==<br />
Throughout the Setup workspace, Voyager uses color to indicate the following:<br />
<br />
*'''Black''': A normal setting<br />
*<span style="color:#E7C63B;"><strong>Gold or Yellow</strong></span>: Use caution when changing as things may not work well or as expected<br />
*<span style="color:#E37D6E;"><strong>Red</strong></span>: Use extreme care when changing this setting - the wrong value can damage your equipment or the imaging session may fail<br />
<br />
==AutoFocus Choice==<br />
Select the AutoFocus program you want to use at the top of the AutoFocus Setup workspace:<br />
<br />
[[File:Autofocus-choice.jpg]]<br />
<br />
*AutoFocus: Select the autofocus program from the options in the drop-down list<br />
<br />
<br />
[[File:Autofocus-selections.jpg]]<br />
<br />
*Available selections include None, FocusMax, TheSkyX @Focus2, Maxim DL, RoboFire, and TheSkyX @Focus3<br />
<br />
*FocusMax is a product of CCDWare: http://www.ccdware.com/products/focusmax/<br />
*TheSkyX has two autofocus routines: @Focus2 and @Focus3. TheSkyX is a product of Software Bisque: http://www.bisque.com/sc/pages/TheSkyX-Editions.aspx<br />
*Maxim DL is a product of Diffraction Limited: http://diffractionlimited.com/product/maxim-dl/<br />
*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)<br />
<br />
{{Note|RoboFire Autofocus doesn't allow use of focuser with relative driver movements mode ... only absolute ASCOM driver}}<br />
<br />
{{Note|RoboFire Autofocus is not compatible (at now) with Baader SteelDrive focusers}}<br />
<br />
==Focuser Choice==<br />
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:<br />
<br />
[[File:Autofocus-choice.jpg]]<br />
<br />
<br />
If you use any of the other autofocus options, you must set up the focuser in those programs, not in Voyager.<br />
<br />
==Focus Result Watchdog==<br />
The Focus Result Watchdog panel in the AutoFocus Setup workspace has several parameters controlling whether an autofocus operation is considered successful:<br />
<br />
[[File:Focus-result-watchdog.jpg]]<br />
<br />
*'''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<br />
*'''Retry Focus For Watchdog''': The number of times an autofocus routine will be tried before giving up<br />
*'''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.<br />
<br />
<br /><br />
==Work Around==<br />
The Work Around panel in the AutoFocus Setup workspace contains a parameter to prevent focuser motion from stopping after a HALT ALL command:<br />
<br />
[[File:Autofocus-workaround-2.12e.png]]<br />
<br />
*'''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.<br />
*'''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.<br />
*'''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<br />
<br />
<br /><br />
==RoboStar General Setting==<br />
The RoboStar General Setting panel in the AutoFocus Setup workspace contains parameters for Voyager's RoboStar operation, which automatically selects a focus star:<br />
<br />
[[File:Robostar-general-setting.jpg]]<br />
<br />
<br /><br />
<br />
*'''Degree''': 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.<br />
*'''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<br />
{{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}}<br />
<br />
<br />
<br />
[[File:Wrong-star-manager.jpg]]<br />
<br />
*'''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.<br />
<br />
[[File:Filter-setup-1.jpg]]<br />
<br />
*Documentation for the Filter Setup dialog is here: [[Camera Setup#Filter Setup|'''Filter Setup''']]<br />
*'''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.<br />
<br />
==TheSkyX @Focus3 Setting==<br />
The TheSkyX @Focus3 Setting panel in the AutoFocus Setup workspace contains parameters for TheSkyX @Focus3<br />
<br />
[[File:Theskyx-atfocus3.jpg]]<br />
<br />
*'''Starting Focus Exposure Time''': Exposure length in seconds to be used by TheSkyX's @Focus3 autofocus routine<br />
*'''Sample Averaging Number''': The number of exposures to take at each focuser position by TheSkyX's @Focus3 autofocus routine<br />
<br />
==RoboFire General Setting==<br />
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:<br />
<br />
[[File:Robofire-setting.jpg]]<br />
<br />
*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<br />
<br />
==RoboFire VCurve vs. LocalField: Which to Use When?==<br />
Voyager has two different autofocus methods: VCurve (single-star) and LocalField (multiple-star). <br />
<br />
*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.<br />
*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.<br />
<br />
<br /><br />
<br />
{{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}}<br />
<br />
==RoboFire Configuration Center==<br />
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. <br />
<br />
===Focuser Tab===<br />
[[File:Robofire-config-focuser.jpg]]<br />
<br />
*'''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.<br />
*'''Limits:''' <br />
**'''IN Limit''': The minimum position (furthest in) of the Focuser in steps<br />
**'''OUT Limit''': The maximum position (furthest out) of the Focuser in steps<br />
*'''Backlash Compensation''': <br />
**'''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<br />
**'''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)<br />
**'''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<br />
*'''Advanced:''' <br />
**'''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.<br />
**'''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<br />
**'''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<br />
<br />
===VCurve Mode Tab===<br />
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.<br />
<br />
<br />
VCurve from a RoboFire autofocus run<br />
[[File:VCurveRun.png|none|thumb|745x745px]]<br />
<br />
<br />
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.<br />
<br />
[[File:Focuser-vcurve-1.jpg]]<br />
<br />
*'''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. <br />
**'''Slope Left''': The slope of the left portion of the VCurve<br />
**'''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.<br />
**'''Step Inc''': The number of focuser steps between each measured point on the VCurve<br />
**'''Slope Right''': The slope of the right portion of the VCurve<br />
<br />
<br />
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. <br />
<br />
[[File:Vcurve-data-1.jpg]]<br /><br />
<br />
*'''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.<br />
*'''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.<br />
*'''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.<br />
*'''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.<br />
*'''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.<br />
*'''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.<br />
<br />
<br />
Returning to the RoboFire Configuration dialog, VCurve Mode tab:<br />
[[File:Focuser-vcurve-1.jpg|none|frame]]<br />
<br />
*'''COMMON Parameters''':<br />
**'''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.<br />
*'''HFD Parameters''': HFD is the Half Flux Diameter of the focus star<br />
**'''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.<br />
**'''Start Focus''': The HFD of the focus star at which to start the autofocus operation<br />
**'''VCurve Limit''': The HFD value at the beginning and end of the VCurve<br />
*'''Star Flux Parameters''':<br />
**'''MIN Flux''': Minimum (dimmest) flux of the focus star. The number entered is multiplied by 1000 to determine the minimum star flux<br />
**'''MAX Flux''': Maximum (brightest) flux of the focus star. The number entered is multiplied by 1000 to determine the maximum star flux<br />
*'''Camera Parameters''':<br />
**'''Bit/Pixel''': BIts per pixel of the imaging camera's sensor<br />
**'''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<br />
**'''Central Region''': The percentage of the overall camera frame used as the central region. Focus stars must be within this region<br />
**'''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<br />
**'''Focus Bin''': The binning used for exposures taken during autofocus<br />
**'''Filter for VCurve''': Filter used for exposures taken while building a VCurve<br />
*'''Exposure Parameters''':<br />
**'''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<br />
**'''Default Time''': This is the exposure time, in seconds, used for the initial image taken by the RoboFire autofocus routine<br />
**'''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<br />
*'''Max HFD Error for Algorithm to find Top, Start and Near Focus''':<br />
**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)<br />
**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<br />
**'''Absolute Diff''': If the radio button for this choice is selected, the maximum HFD error allowed is this number expressed in pixels<br />
**'''Percentage''': If the radio button for this choice is selected, the maximum HFD error allowed during autofocus is this percentage<br />
<br />
<br /><br />
<br />
===LocalField Mode Tab===<br />
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.<br />
<br />
Prior to Voyager 2.1.1e, the LocalField tab looked like this: (see below for the new one)<br />
<br />
[[File:Localfield-mode.jpg]]<br />
<br />
*'''Camera and Exposure Parameters'''<br />
**'''Focus Bin''': The binning used for LocalField autofocus exposures<br />
**'''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]]<br />
**'''Central Region''': The percent of the image's central region used by the LocalField autofocus operation<br />
*'''LocalField AI Engine''':<br />
**'''Focuser Step x Sample''': <br />
***'''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<br />
***'''Manual''': Choose this radio button to enter the step size manually<br />
**'''Sample''': The number of exposures to take during the LocalField autofocus operation. One sample is taken at each focuser position<br />
**'''Minimum Stars Number''': LocalField autofocus will require at least this number of stars in each exposure to be successful<br />
*'''Advanced Settings''':<br />
**'''Min HFD Gap''': a minimum pixel gap from the minimum value of HFD and maximum value of HFD found during the LocalFIeld sampling<br />
**'''Min Confidence''': The minimum statistical confidence percentage to consider autofocus successful<br />
**'''Focus Window Size''': The percentage of the image (Central Region of CCD) used during the autofocus routine<br />
**'''Fit Order''': Curve FIT order in AI analysis of results<br />
*'''Reset to Default''': Reset all LocalField Mode settings to Voyager's defaults<br />
<br />
<br />
As of Voyager 2.1.1e, the labels in the LocalField setup tab have been changed to make them easier to understand:<br />
<br />
[[File:Localfield-setup-211e.jpg]]<br /><br />
<br />
*'''Camera and Exposure Parameters'''<br />
**'''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'''<br />
**'''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<br />
**'''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<br />
**'''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<br />
*'''LocalField AI Engine''':<br />
**'''Focuser Step x Sample''': <br />
***'''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<br />
***'''Manual''': Choose this radio button to enter the step size manually<br />
**'''Sample''': The number of exposures to take during the LocalField autofocus operation. One sample is taken at each focuser position<br />
**'''Minimum Stars Number''': LocalField autofocus will require at least this number of stars in each exposure to be successful<br />
*'''Advanced Settings''':<br />
**'''Min HFD Gap''': a minimum pixel gap from the minimum value of HFD and maximum value of HFD found during the LocalFIeld sampling<br />
**'''Min Confidence''': The minimum statistical confidence percentage to consider autofocus successful<br />
**'''Focus Window Size''': The percentage of the image (Central Region of CCD) used during the autofocus routine<br />
**'''Fit Order''': Curve FIT order in AI analysis of results<br />
*'''Reset to Default''': Reset all LocalField Mode settings to Voyager's defaults<br />
<br />
===Various Tab===<br />
The final tab of the RoboFire Configuration dialog contains some miscellaneous parameters:<br />
<br />
[[File:Robofire-various.jpg]]<br />
<br />
*'''Dashboard''': <br />
**'''Show Dashboard During RoboFire Actions''': If checked, the RoboFire dashboard appears while the autofocus operations are in progress<br />
**'''Dashboard on Top''': If checked, keep the RoboFire Dashboard on top of other windows while it is active<br />
**'''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<br />
*'''Workaround'''<br />
**'''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<br />
<br />
* '''FIT'''<br />
**'''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<br />
<br />
==Point Closest Focus Star with RoboStar==<br />
[[File:Point-focus-star.jpg]]<br />
<br />
This button starts a RoboStar operation to find a suitable nearby focus star. <br />
<br />
{{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.}}<br /><br />
<br />
==VCurve First Light Wizard==<br />
[[File:Vcurve-first-light.jpg]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
[[File:Vcurve-wizard.jpg]]<br />
<br />
When you have read and followed all the steps in this panel, click the OK button to immediately run the VCurve First Light Wizard<br />
<br />
<br />
TODO: Run the wizard and capture screen shots<br />
<br />
{{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}}<br />
<br />
{{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}}<br /><br />
==Add New VCurve==<br />
[[File:Add-new-vcurve.jpg]]<br />
<br />
Click this button to run an immediate operation to take exposures as specified in the RoboFire Configuration Center to calculate a VCurve.<br />
{{Note|You must run the VCurve First Light Wizard before running the Add New VCurve operation}}<br />
<br />
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. <br />
<br />
TODO: Run this command and capture screen shots<br />
<br />
<br /><br />
==Test AutoFocus VCurve==<br />
[[File:Test-autofocus-vcurve.jpg]]<br />Click this button to run a RoboFire autofocus operation to test the VCurve parameters with a real life autofocus<br />
<br />
<br />
TODO: Run and capture screen shot<br />
<br /><br />
==Other Setup Pages==<br />
{{#categorytree:Setup|mode="pages"}}<br />
<br />
[[Category:Setup]]<br />
[[Category:All]]<br />
[[Category:Manual|Hf]]</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=Rotator_Setup&diff=5656Rotator Setup2020-10-14T09:49:13Z<p>Rowland: /* Other Setup Pages */</p>
<hr />
<div>==Color Coding==<br />
Throughout the Setup workspace, Voyager uses color to indicate the following:<br />
<br />
*'''Black''': A normal setting<br />
*<span style="color:#E7C63B;"><strong>Gold or Yellow</strong></span>: Use caution when changing as things may not work well or as expected<br />
*<span style="color:#E37D6E;"><strong>Red</strong></span>: Use extreme care when changing this setting - the wrong value can damage your equipment or the imaging session may fail<br />
<br />
==Rotator Setup Workspace==<br />
Click the Rotator button in the Setup workspace to display the Rotator Setup window:<br />
<br />
[[File:Rotator-setup.jpg]]<br />
<br />
<br /><br />
<br />
==Rotator Choice==<br />
Select your rotator from the drop-down list at the top of the Rotator Setup window:<br />
<br />
[[File:Rotator-choice-1.jpg]]<br />
<br />
*The options are None for no rotator and ASCOM Rotator for a rotator controlled via an ASCOM driver.<br />
*Click the ASCOM button to choose the ASCOM driver for your rotator<br />
<br />
<br /><br />
<br />
==Sync Management==<br />
For sync we talk about synchronize the position angle of the rotator to the position angle of the sky. Voyager can manage Rotator Sync based on the driver capabilities:<br />
<br />
- (A) Driver without Sync (like ones with ASCOM Interface V2)<br />
<br />
- (B) Driver with Sync (like ones with ASCOM Interface V3)<br />
<br />
The value of offset for Sync can be managed using the Sync button in Rotator Command Widget in Voyager GUI column Command.<br />
<br />
You will input manually the angle to sync.<br />
<br />
If you have driver type (A) Voyager will calculate automatically for you the Offset and value will be stored in actual Voyager Profile. You might have more Voyager profiles with different offset if you sharing the same driver and rotator.<br />
<br />
If you have driver type (B) ASCOM Driver will calculate automatically for you the Offset and value will be stored in ASCOM driver settings permanently. Value stored will be equal for all Voyager setup profiles in case of driver and rotator sharing.<br />
<br />
<br /><br />
<br />
==Rotator Workaround==<br />
The Rotator Workaround panel of the Rotator Setup workspace contains a workaround for rotators that require a delay after finishing the move and before resuming exposures:<br />
<br />
[[File:Rotator-workaround.jpg]]<br />
<br />
*Wait Time After Rotator FInished Move: Check the box and enter the delay time in seconds if your rotator requires Voyager to delay the next action after the rotator move finishes. This can be helpful if your rotator returns from the "Move" command before it actually finishes the rotation, or if a delay is required after the move completes to allow vibrations to settle down. Some rotator drivers report rotation is finished before the rotator has actually stopped. This can cause elongated stars if the next exposure starts immediately<br />
<br />
<br /><br />
==Other Setup Pages==<br />
{{#categorytree:Setup|mode="pages"}}<br />
[[Category:Setup]]<br />
[[Category:All]]<br />
[[Category:Manual|Hg]]</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=Rotator_Setup&diff=5655Rotator Setup2020-10-14T09:34:54Z<p>Rowland: /* Other Setup Pages */</p>
<hr />
<div>==Color Coding==<br />
Throughout the Setup workspace, Voyager uses color to indicate the following:<br />
<br />
*'''Black''': A normal setting<br />
*<span style="color:#E7C63B;"><strong>Gold or Yellow</strong></span>: Use caution when changing as things may not work well or as expected<br />
*<span style="color:#E37D6E;"><strong>Red</strong></span>: Use extreme care when changing this setting - the wrong value can damage your equipment or the imaging session may fail<br />
<br />
==Rotator Setup Workspace==<br />
Click the Rotator button in the Setup workspace to display the Rotator Setup window:<br />
<br />
[[File:Rotator-setup.jpg]]<br />
<br />
<br /><br />
<br />
==Rotator Choice==<br />
Select your rotator from the drop-down list at the top of the Rotator Setup window:<br />
<br />
[[File:Rotator-choice-1.jpg]]<br />
<br />
*The options are None for no rotator and ASCOM Rotator for a rotator controlled via an ASCOM driver.<br />
*Click the ASCOM button to choose the ASCOM driver for your rotator<br />
<br />
<br /><br />
<br />
==Sync Management==<br />
For sync we talk about synchronize the position angle of the rotator to the position angle of the sky. Voyager can manage Rotator Sync based on the driver capabilities:<br />
<br />
- (A) Driver without Sync (like ones with ASCOM Interface V2)<br />
<br />
- (B) Driver with Sync (like ones with ASCOM Interface V3)<br />
<br />
The value of offset for Sync can be managed using the Sync button in Rotator Command Widget in Voyager GUI column Command.<br />
<br />
You will input manually the angle to sync.<br />
<br />
If you have driver type (A) Voyager will calculate automatically for you the Offset and value will be stored in actual Voyager Profile. You might have more Voyager profiles with different offset if you sharing the same driver and rotator.<br />
<br />
If you have driver type (B) ASCOM Driver will calculate automatically for you the Offset and value will be stored in ASCOM driver settings permanently. Value stored will be equal for all Voyager setup profiles in case of driver and rotator sharing.<br />
<br />
<br /><br />
<br />
==Rotator Workaround==<br />
The Rotator Workaround panel of the Rotator Setup workspace contains a workaround for rotators that require a delay after finishing the move and before resuming exposures:<br />
<br />
[[File:Rotator-workaround.jpg]]<br />
<br />
*Wait Time After Rotator FInished Move: Check the box and enter the delay time in seconds if your rotator requires Voyager to delay the next action after the rotator move finishes. This can be helpful if your rotator returns from the "Move" command before it actually finishes the rotation, or if a delay is required after the move completes to allow vibrations to settle down. Some rotator drivers report rotation is finished before the rotator has actually stopped. This can cause elongated stars if the next exposure starts immediately<br />
<br />
<br /><br />
==Other Setup Pages==<br />
<categorytree mode="pages" depth="1">Setup</categorytree><br />
{{#categorytree:Setup|mode="pages"}}<br />
[[Category:Setup]]<br />
[[Category:All]]<br />
[[Category:Manual|Hg]]</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=Manual_Title_Page&diff=5642Manual Title Page2020-10-12T12:14:48Z<p>Rowland: /* Voyager */</p>
<hr />
<div><br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
=== '''Voyager''' ===<br />
Image Acquisition Software<br />
<br />
by Starkeeper.it<br />
<br />
<!-- PAGE BREAK --></div>Rowlandhttps://wiki.starkeeper.it/index.php?title=Manual_Title_Page&diff=5641Manual Title Page2020-10-12T11:37:28Z<p>Rowland: </p>
<hr />
<div><br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
=== '''Voyager''' ===<br />
Image Acquisition Software<br />
<br />
by Starkeeper.it<br />
<br />
<!-- PAGE BREAK --><br />
<br />
<br />
[[Category:Manual|AA]]<br />
[[Category:All]]</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=Manual_Title_Page&diff=5640Manual Title Page2020-10-12T11:35:50Z<p>Rowland: </p>
<hr />
<div><br />
<br />
<br />
[[File:Horsehead Nebula.jpg|thumb]]<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
=== '''Voyager''' ===<br />
Image Acquisition Software<br />
<br />
by Starkeeper.it<br />
<br />
<!-- PAGE BREAK --><br />
<br />
<br />
[[Category:Manual|AA]]<br />
[[Category:All]]</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=File:Horsehead_Nebula.jpg&diff=5639File:Horsehead Nebula.jpg2020-10-12T11:35:08Z<p>Rowland: </p>
<hr />
<div>Horsehead</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=MediaWiki:Sidebar&diff=5638MediaWiki:Sidebar2020-10-12T11:21:27Z<p>Rowland: </p>
<hr />
<div>* Home<br />
** mainpage|mainpage-description<br />
<br />
*VERSION<br />
*** Version| Voyager 2.2.13a1<br />
<br />
*PDF Version<br />
** https://wiki.starkeeper.it/images/voyager.pdf | PDF Manual<br />
<br />
*Videos<br />
** https://software.starkeeper.it/voyager-video-list | Videos<br />
<br />
*FAQ<br />
<br />
* Documentation<br />
*** Introduction | 1. Introduction<br />
*** Installation|2. Installation<br />
*** Licensing|3. Licensing<br />
*** Main Window|4. Main Window<br />
*** Status Window|5. Status Window<br />
*** Command Window|6. Command Window<br />
*** Setup|7. Setup<br />
*** Startup|8. Startup<br />
*** OnTheFly|9. OnTheFly<br />
****Sequence Configuration|9.1 Sequences<br />
****Auto Flat|9.2 Auto Flats<br />
***Research Survey|10. Research Survey<br />
*** FIT Viewer|11. FIT Viewer<br />
*** Application Server API|12. Application Server<br />
*** Array|13. Custom Array Observatory<br />
*** http://www.starkeeper.it/wdashinfo/ |14. Web Dashboard<br />
*** Voyager Multi Instance|15. Voyager Multi Instance<br />
<br />
* Setup<br />
*** Setup|Overview<br />
*** AutoFocus Setup|1. AutoFocus<br />
*** Camera Setup|2. Camera<br />
*** Dome Setup|3. Dome<br />
*** Flat Device Setup|4. Flat Device<br />
*** Guiding Setup|5. Guiding<br />
*** Mount Setup|6. Mount<br />
*** Observing Conditions Setup|7. Observing Conditions<br />
*** Planetarium Setup|8. Planetarium<br />
*** Plate Solve Setup|9. Plate Solve<br />
*** Rotator Setup|10. Rotator<br />
*** SQM Setup|11. SQM<br />
*** Safety Monitor Setup|12. Safety Monitor<br />
*** Viking Setup|13. Viking<br />
*** Voyager Setup|14. Voyager<br />
*** Weather Setup|15. Weather<br />
*** WEB Dashboard Setup|16. Web Dashboard<br />
<br />
* Custom Setup<br />
*** Array|Array Observatory<br />
<br />
* DragScript<br />
*** DragScript|1. Editor<br />
*** DragScript Elements|2. Elements<br />
*** DragScript Other Elements|3. Viking and Arrays<br />
*** DragScript Flow of Control|4. Variables and Control Flow<br />
*** DragScript Examples|5. DragScript Examples<br />
<br />
* RoboClip<br />
***Introduction to RoboClip|1. Introduction to RoboClip<br />
***Manager Window|2. RoboClip Manager Window<br />
<br />
* Tutorials<br />
*** Quick Start|1. Quick Start<br />
*** DragScript Examples|2. DragScript Examples<br />
*** Extending Voyager|3. Extending Voyager<br />
*** Command Line|4. Voyager Command Line Arguments<br />
<br />
* FAQ<br />
*** FAQ|FAQ<br />
<br />
* Viking<br />
*** Viking|Viking 1.0.22<br />
<br />
* Categories<br />
*** Category:All|All<br />
*** Category:Setup|Setup<br />
*** Category:DragScript|DragScript<br />
*** Category:Tutorials|Tutorials<br />
*** Category:Manual|Manual<br />
<br />
* Other info<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=Extending_Voyager&diff=5637Extending Voyager2020-10-12T11:17:14Z<p>Rowland: </p>
<hr />
<div>This page contains examples of extending Voyager with its built-in tools such as DragScript.<br />
<br />
==HitecAstro Mount Hub Pro Management==<br />
''Thanks to Nicolas Kizilian for this contribution and write-up (<nowiki>https://forum.voyagerastro.com/t/hitecastro-mount-hub-pro-management-with-scripts/681</nowiki>)''<br />
<br />
'''Editor: While this is an example of how to support a specific piece of hardware, the technique used - calling external programs from a DragScript - can be used for many other things.'''<br />
<br />
<br />
For my setup I’m using an HitecAstro MountHubPro (MHP) for managing my power outputs and dew heaters.<br />
<br />
Although it isn’t supported (yet?) by Viking, you can automate it with DragScript.<br />
<br />
*First you’ll need a tool developed by Darren Jehan from CN called TANOS MHP. This tool lets you activate/deactivage any output, manage the dew heaters output and the focuser controller on your MHP with simple command lines. You can download this tool [https://drive.google.com/file/d/1UPkLINHihEWyrzW45gFaO7VKP2Qp0ptY/view?usp=sharing from my GDrive here]<br />
*Install TANOS MHP The usage of TANOS is pretty simple<br />
**[[File:Mhp-1.png]]<br />
<br />
**In DragScript, inject a Script block calling TANOS MHP to activate or deactivate the outputs: <br />
***[[File:Mhp-2.png]]<br />
<br />
<br /><br />
[[File:Mhp-3.jpg]]<br />
<br />
Very easy isn’t it ? <br />
<br />
Another idea would be to get the data from your weather sensors and activate/deactivate/manage your dew heaters depending on the temperature and the dew point automatically. <br />
<br />
I hope that’ll help ! Nicolas <br /><br />
<br />
<br /><br />
[[Category:Tutorials]]<br />
[[Category:All]]<br />
[[Category:Manual|Mg]]</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=Extending_Voyager&diff=5636Extending Voyager2020-10-12T11:14:13Z<p>Rowland: </p>
<hr />
<div>This page contains examples of extending Voyager with its built-in tools such as DragScript.<br />
<br />
==HitecAstro Mount Hub Pro Management==<br />
''Thanks to Nicolas Kizilian for this contribution and write-up (<nowiki>https://forum.voyagerastro.com/t/hitecastro-mount-hub-pro-management-with-scripts/681</nowiki>)''<br />
<br />
'''Editor: While this is an example of how to support a specific piece of hardware, the technique used - calling external programs from a DragScript - can be used for many other things.'''<br />
<br />
<br />
For my setup I’m using an HitecAstro MountHubPro (MHP) for managing my power outputs and dew heaters.<br />
<br />
Although it isn’t supported (yet?) by Viking, you can automate it with DragScript.<br />
<br />
*First you’ll need a tool developed by Darren Jehan from CN called TANOS MHP. This tool lets you activate/deactivage any output, manage the dew heaters output and the focuser controller on your MHP with simple command lines. You can download this tool [https://drive.google.com/file/d/1UPkLINHihEWyrzW45gFaO7VKP2Qp0ptY/view?usp=sharing from my GDrive here]<br />
*Install TANOS MHP The usage of TANOS is pretty simple<br />
**[[File:Mhp-1.png]]<br />
<br />
**In DragScript, inject a Script block calling TANOS MHP to activate or deactivate the outputs: <br />
***[[File:Mhp-2.png]]<br />
<br />
<br /><br />
[[File:Mhp-3.jpg]]<br />
<br />
Very easy isn’t it ? <br />
<br />
Another idea would be to get the data from your weather sensors and activate/deactivate/manage your dew heaters depending on the temperature and the dew point automatically. <br />
<br />
I hope that’ll help ! Nicolas <br /><br />
<br />
<br /><br />
[[Category:Tutorials]]<br />
[[Category:All]]<br />
[[Category:Manual|Mg]]<br />
[{{fullurl:{{FULLPAGENAME}}|action=pdfbook}} download this selection of articles as a PDF book]</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=FAQ&diff=5635FAQ2020-10-12T11:09:11Z<p>Rowland: </p>
<hr />
<div>Post your questions in the Voyager Forum at https://forum.starkeeper.it We monitor that forum and will add the answers here if appropriate.<br />
<br />
<br />
==4K Monitor Resolution from Local or Remote Desktop==<br />
'''I have some font size problem on 4K monitor resolution, font is scaled to small and cannot show correctly Voyager Windows?'''<br />
<br />
*There is a compatibility tab in the windows properties for the Voyager application. On this tab is a button labelled “Change high DPI settings”. I then checked the box for “Use this setting to fix scaling problems for this program instead of the one in settings” and for “Use the DPI that’s set for my main display when:” I selected “I signed into Windows”. I think that means if I sign in locally on the observatory PC with a 1920x1080 monitor it uses this DPI and if I sign in remotely with my laptop and 4K display it uses this DPI.[[File:4kA.png|600x600px]][[File:4KB.png|452x452px]]<br />
<br />
<br /><br />
==Artificial Intelligence (AI) in Voyager==<br />
<br />
*'''What is the benefit to users of the AI automata inside of Voyager?'''<br />
**Voyager uses AI technology to improve focus, star recognition , equation calculation for VCurve, statistical calculations, and decisions for how to handle exceptions generated by the watchdog timers. Watchdogs are timers that oversee all requests to external hardware and software and recover from soft errors. The bottom line is that the advanced AI technology inside of Voyager contributes significantly to Voyager's exceptional reliability.<br />
<br />
==AstroPhysics Mounts and APCC==<br />
<br />
*'''What is the best way to connect to APCC from Voyager?'''<br />
**Short answer courtesy of Voyager user Bill Long: ''I run Voyager in admin mode.'' ''I just open APCC first in admin mode, connect the ASCOM driver to APCC, then connect via Voyager. Works fine.''<br />
*'''I tried this but still having problems connecting to APCC from Voyager'''<br />
**In setup for APCC, in the lower-left corner, you’ll need to uncheck the two boxes in the AP V2 Driver section labeled “auto connect” and “auto config”. This will allow Voyager to start the driver first without APCC interfering with other startup functions.<br />
<br />
<br /><br />
==AutoFocus==<br />
<br />
*'''LocalField autofocus fails with an out-of-memory error [For version older than 2.2.1b]'''<br />
**'''This problem was solved in Voyager version 2.2.1c and newer'''<br />
**Try using a smaller ROI or binning 2x2 instead of 1x1. The image is managed in memory using a Microsoft memory object that does not do garbage collection, so depending on what other programs are running and possibly using this memory, you may run out if your camera creates large images with each shot. NOTE: Be sure to set the binning for LocalField autofocus in the correct spot for your camera:<br />
***If your camera does '''not''' have filters, use the Focus Bin setting - it's in Setup -> AutoFocus -> Robofire Configuration -> LocalField Mode:<br />
***[[File:Localfield-focus-bin.jpg|514x514px]]<br />
***If your camera does have filters, its in the per-filter settings dialog, which is in Setup -> Camera, then click the EDIT button in the Filters panel:<br />
***[[File:Localfield-per-filter-bin.png]] <br /><br />
<br />
**'''How do I request an autofocus while a sequence or DragScript is running?'''<br />
***Click the Monitor tab, then click AutoFocus. Choose the filter for autofocus. The current exposure will finish, then an autofocus will be performed, and then the sequence or DragScript will resume.<br />
***[[File:Inject-autofocus.png]]<br />
<br />
<br /><br />
<br />
*'''TheSkyX @Focus2 slews to a Focus Star but doesn't return to my target.''' <br />
**Choose Voyager RoboStar in your Sequence setup, Focus tab. Voyager will choose a focus star, call TheSkyX @Focus2 which does the autofocus, and then Voyager will slew back to your target<br />
**Be sure to uncheck "Automatically slew telescope to the nearest appropriate focus star" in TheSkyX @Focus2<br />
**[[File:Theskyx-atfocus2-nofocusstar.jpg]] <br /><br />
*'''Does Voyager implement Temperature Compensation (move the focuser a predetermined amount based on ambient temperature)?'''<br />
**No, Voyager does not implement temperature compensation. Even the author of FocusMax says that temperature compensation gives inconsistent results and he decided not to use it. We want your images to have sharp focus. Voyager's goal is reliable imaging automation and unfortunately temperature compensation is unreliable. If you still want to use temperature compensation, you can find some focuser drivers that implement it for you in the driver software.<br /><br />
<br />
==Cameras==<br />
<br />
*'''Can Voyager use my FLI Camera?'''<br />
**You can connect to an FLI camera using TheSkyX, Maxim DL, or the ASCOM driver written by Hartmut Bornemann in the Yahoo! FLI Imaging Systems group at:https://groups.yahoo.com/neo/groups/FLI_Imaging_Systems/files/Hartmut%20Bornemann/<br />
**There is a checkbox in his driver labelled “Can Fast Readout." This must be unchecked. If it is checked, Voyager will not be able to consistently change the readout mode. (thanks to Bill Long for the tip)<br />
<br />
[[File:FLI Driver Image.png]]<br /><br />
<br />
*'''Can Voyager use my SBIG camera?'''<br />
**You can connect to your SBIG camera using TheSkyX or Maxim DL. There is no native support in Voyager for SBIG cameras as of Voyager 2.1.4. We need access to a camera to test a native driver. This may happen in the future but we don't have any firm as of this writing (June 2019)<br />
<br />
*'''I get an Out of Memory Error when trying to take exposures with my Camera using the ASCOM driver'''<br />
**Voyager runs as a 32-bit application so has access to 4GB no matter how much RAM is installed on your PC. Reboot your PC and only run the other applications you need.<br />
*'''Downloads from my camera are hanging'''<br />
**Check your USB cable lengths. The maximum length specified for USB3 is 3 meters - longer than that and you may have problems.<br />
**For ASI cameras, try reducing the download speed in the ASCOM driver<br />
<br />
*'''Can Voyager support Gain and Offset for my ZWO ASI CMOS camera?'''<br />
**As of Voyager 2.1.6b, an [[Camera Setup#ASI Native Driver|ASI Camera native driver]] is available as a choice in Camera setup. Use this driver and you can set Gain and Offset individually for each [[Sequence Configuration#Sequence Elements|Sequence Element]].<br />
**You '''cannot''' set Gain or Offset using the ASI ASCOM driver, you must use the ASI Camera native driver.<br />
*'''Does Voyager add GAIN and OFFSET keywords to my image file FITS headers?'''<br />
**As of Voyager 2.1.6b, if you use the [[Camera Setup#ASI Native Driver|ASI Camera native driver]], the GAIN and OFFSET keywords will be set in the image file FITS headers.<br /><br />
<br />
==Cooling==<br />
<br />
*'''Why did Voyager put "NoCooling" in the file name saved by my Sequence?'''<br />
*This happens when the Sequence's “Cooling” checkbox on the Cooling tab is unchecked. This means you have cooling on in your camera but Voyager's Sequence is not managing it. You may have started cooling from the Voyager command box or from the camera control, extrernal to Voyager. It is thus possible that the camera has been cooled, but it will say NoCooling because Voyager is not managing the temperature. If there’s an error in cooling you might see the text "UNK" in your file name.<br />
<br />
==Connection / Startup==<br />
<br />
*'''I get a red error message when I click Connect in the Startup workspace - Voyager can't connect to third party software such as TheSkyX, Maxim DL, PHD2, etc.'''<br />
**Ensure Voyager is [[Installation|running as administrator]]. Start Voyager before all other programs. Let Voyager start the other programs it needs. They will inherit the proper mode from Windows when Voyager starts them.<br />
**If you still have an error, check your antivirus software to make sure it is not preventing Voyager from communicating with other programs.<br />
**If the inter-program communication is via TCP/IP ports, check that Voyager and the third party program are allowed to access ports in the Windows firewall, or any other firewall you may be running<br />
*'''I get a red error message when I click Connect in the Startup workspace - Voyager can't connect to my hardware'''<br />
**Ensure Voyager is [[Installation|running as administrator]]. Check that your hardware is powered up and configured properly in Voyager and any driver software used to connect to it.<br />
**Ensure the COM port has not changed - sometimes Windows assigns a different COM port and your hardware driver will not be able to connect to your gear.<br />
**For camera connection problems, try applying the [[Camera Setup#Various|Slow Polling flag]] in Camera Setup. Some camera drivers can't handle requests spaced too closely together<br />
**For mount connection problems, try applying the [[Mount Setup#Data Polling|Slow Polling flag]] in Mount Setup. Some mount drivers can't handle requests spaced too closely together<br />
*'''Voyager closes after trying to connect to other software or hardware'''<br />
**Voyager will only close if a driver had a critical failure at the Windows kernel level that cannot be handled. Please activate the ASCOM log and report to the driver developers.<br />
*'''Voyager has problems connecting to my ASCOM device'''<br />
**See above suggestions<br />
**Make sure the version of ASCOM you have installed is the correct one for your driver<br />
**If your driver accepts only one connection (a serial error when you try to connect from Voyager would indicate this) you can connect only one app. If you want connect more than one app you must use an ASCOM hub.<br />
<br />
Voyager implements standard ASCOM. <br />
<br />
==Dome==<br />
<br />
*'''I have the HiTec Roll-Off-Roof controller. I am getting "The requested operation is not permitted at this time" errors. What should I do?'''<br />
**These errors have been seen when using the ASCOM driver as standard. Try the ASCOM Dome ConnectionLess Interface, which seems to eliminate these errors<br />
*'''Voyager started taking images before the dome had finished rotating'''<br />
**Voyager will slave to the dome when starting a sequence only if you check the box '''Slave on Sequence Start''' in Setup -> Dome:<br />
**[[File:Dome-slave-on-seq-start.jpg]]<br />
**If you don't do a specific command to slave the dome in Voyager, you'll see the message "Slave is unlock from user" in the monitor window<br />
**This is because some drivers don't report slave status to Voyager<br />
**If you create a DragScript to manage all night imaging remember to put a slave on block in the script if you do other mount operations before starting a sequence.<br />
**Also remember to slave off and park the dome at the end of the script<br />
*'''I use VIking to control my Dome (or Roll-Off Roof). How do I connect it to Voyager's Dome controls?'''<br />
**Voyager's Dome controls are only for ASCOM drivers. To use Viking from Voyager, build a DragScript and use the Viking actions to read and write to Viking's relays, switches and controls.<br />
**This video explains how to do this: <nowiki>https://vimeo.com/331171731</nowiki><br />
*'''How do I make sure Voyager doesn't move my scope if I have a Roll Off Roof and the roof is closed?'''<br />
**Go to SetupForm/Dome and you will see a tick box: “Abort GoTo actions if Dome mode is Roll off Roof and the Shutter is closed” A tick there will stop any clash between scope and roof. (Courtesy of Graham on our forum)<br />
*'''How can I get slaving to work with my MaxDome ASCOM driver?'''<br />
**Use Voyager RoboSync to slave the dome.<br /><br />
<br />
==DSLR Support==<br />
<br />
*'''Can I use my DSLR camera (Canon, Nikon) with Voyager?'''<br />
**Voyager supports camera connection via ASCOM drivers, Maxim DL, or TheSkyX<br />
**We strongly recommend using Maxim DL or TheSkyX with DSLR's as their camera support has been widely used<br />
**There is an [https://github.com/vtorkalo/ASCOM.DSLR open source ASCOM.DSLR driver] that may work for you. It can connect via the Canon or Nikon SDK's, or for Canon cameras, it can also connect via [https://www.otelescope.com/ O'telescope's Backyard EOS].<br />
**We cannot help you if this doesn't work, but if you want to try using the ASCOM.DSLR driver, we wrote a [[ASCOM.DSLR|Wiki page on how to set it up]]<br />
<br />
<br /><br />
==Editing a DragScript==<br />
<br />
*'''I can't get Drag and Drop to work in the DragScript Editor (perhaps with a remote desktop connection such as VNC, TeamViewer, etc)'''<br />
**You can only drop DragScript elements where the mouse pointer shape changes to an arrow with a little rectangle attached when you hover over the desired drop location.<br />
**On Windows 10, the mouse pointer will not change shape if there is no mouse connected to the remote PC. To enable the mouse pointer shape changing with no mouse connected:<br />
***Right click the Windows button on the remote PC's desktop (not on your local PC)<br />
***Click Settings<br />
***Type "Mouse Keys" in the search box and select "Turn Mouse Keys On or Off"<br />
***Turn Mouse Keys on <br /><br />
<br />
[[File:Filename-spec.jpg]]<br />
<br />
#Target name<br />
#Type of exposure: Light, Dark, or Bias<br />
#Suffix: whatever you type in the "Suffix" field. Filter names are used here.<br />
#Exposure length<br />
#Binning level<br />
#Sensor temperature<br />
#Sequence number: a sequential number generated automatically when Voyager takes a new image<br />
#Date: YYYYMMDD<br />
#Time: HHMMSS<br />
#MS: millisecond portion of the time the image was taken<br />
#Position Angle<br />
#Position relative to Meridian: E = East or W = West<br />
#File type: FIT for a FITS file<br />
<br />
==Filenames==<br />
<br />
*'''Can I use my own filenames for images taken with Voyager?'''<br />
**'''Sequences''': You can add something to the image filenames created by a sequence by typing it into the Suffix field - in this example, the filter name is used[[File:Sequence-elements.png]]<br />
**'''Other:''' With the Camera -> Expose action in a DragScript, you can specify the filename however you like<br />
*'''What do the fields mean in the default image filenames saved by Sequences?'''<br />
<br />
==Filters==<br />
<br />
*'''How can I have Voyager use Filter Offsets (automatically change focus position when switching filters with a filter wheel)?'''<br />
**Set this up in the ASCOM driver for your filter wheel, or in TheSkyX or Maxim DL if you use them for your Camera control<br />
<br />
<br /><br />
==Flats==<br />
<br />
*'''How can I take flats without the variable exposure feature of Auto Flats?'''<br />
**There are at least two ways to do this. Use the Camera -> Expose option in a DragScript. You can enter your desired exposure length and choose Flat as your exposure type. Or, enter your desired exposure length in Auto Flats for the minimum, maximum, and initial exposure times. Set the desired ADU to your mid-range (usually 32767) and 100% as your error tolerance.<br />
*'''My Auto Flats never finish, they keep looping trying to find the proper exposure time but it is always outside the allowed error tolerance'''<br />
**Try using a larger ROI - with a camera with a large number of pixels, the mean ADU of the default small ROI can change quite a bit. Also, look at the deviation in percent reported in the Monitor window. Increase your allowed error tolerance if necessary. You can also change the ROI to "no" and Voyager will determine exposure length based on the entire image, but this takes a little longer.<br />
<br />
==Guiding==<br />
<br />
*'''What's the difference between RoboGuide and Native Guide controls?'''<br />
**If you use RoboGuide, Voyager will choose a guide star using the parameters you set in RoboGuide Advanced<br />
**[[File:Roboguide-advanced.jpg]]<br />
**If you use Native Guide Control, Voyager will let your guiding software (PHD2, Maxim DL, TheSkyX) choose the guide star<br />
*'''Why does RoboGuide choose saturated guide stars?'''<br />
**This happens if you check '''Force Use Saturated Stars''' in the RoboGuide Advanced section of Guiding setup. This can be useful at long focal lengths where only a few guide stars are available. Sometimes a saturated star is the best choice for guiding.<br />
**If you use a CMOS camera, check with a viewer to see what ADU value returned for a saturated star. Put this value in the '''Override Guide Star Saturation ADU Value''' box and uncheck '''Force Use Saturated Stars''' and Voyager's AI will choose guide stars below this value<br />
**[[File:Roboguide-setup-211e.jpg]]<br />
**You can read the ADU value of a guide star inside of PHD2 if you use that for guiding<br />
**[[File:PHD2-ADU-Readout.png]]<br />
<br />
==Licensing==<br />
<br />
*'''What's the difference between "Demo" and "Trial" modes?'''<br />
**The Voyager download installs in Demo mode. This is a perpetual, full functionality version of Voyager that times out after 60 minutes. Trial mode is full functionality with no session time limit, but limited to 45 days from the time you start the trial (which can be a later date than installation).<br />
*'''How do I get a license for my second or third PC's?'''<br />
**Install the download on your second or third PC. Copy the serial number, which is unique to that PC, and email it to Leo or use the form at https://voyagerastro.com/contact-us/<br />
*'''Can I install the Free Trial download on multiple computers?'''<br />
**Yes. It will install in "Demo" mode which is full functionality with a 60 minute session timeout. You can start the 45 day free trial at any time by clicking the Activate Trial button on the startup splash screen.<br />
*'''Do I need to install Voyager to get a serial number before buying a license?'''<br />
**Yes. Each installation of Voyager has a unique serial number that is generated when you install it. Find your serial number by running Voyager, clicking the Resource menu, then the License option<br />
<br />
[[File:License-resource.jpg]]<br />
<br />
**Copy the serial number from the License window and enter it in the Serial Number field of the license purchase form<br />
<br />
<br /><br />
<br />
==Meridian Flips==<br />
<br />
*'''How do I set up Voyager to manage meridian flips?'''<br />
**Determine how far past the meridian your scope can slew without a pier crash. Let's say this is 30 minutes. Choose a value less than this, default is 10 minutes, and put that number in the "[[Mount Setup#GEM Meridian Flip Manager|Do Flip after Mount Passing Meridian By]]" field in Mount Setup. If you want Voyager to finish the current exposure before doing the flip, allow enough time for your longest exposures to complete. E.g. if your longest exposure is 10 minutes in this example, Voyager would do the meridian flip no later than 20 minutes past the meridian, which would be OK with a 30 minute max for your equipment.<br />
**We don't recommend using zero (0) for the Do Flip after Mount Passing Meridian By" number, because this requires precise synchronization of the time settings in your PC and mount and the lat/long position of your site, and you must choose the "'''ASCOM - Read LST from Driver'''" in Mount Setup<br />
**Make sure your mount driver does not also do an automatic meridian flip when it is just tracking past the meridian<br />
**Choose Manage from Meridian Flip Mode in the [[Sequence Configuration#Meridian Flip Tab|Meridian Flip tab of the Sequence]] definition.<br />
**Run your sequences. When your scope crosses the meridian plus the number of minutes you specified in "Do Flip after Mount Passing Meridian By" minutes, Voyager will wait until the current exposure finishes, then perform the meridian flip before starting the next one.<br />
**For a more thorough explanation, read the [[Mount Setup#GEM Meridian Flip Manager|GEM Meridian Flip Manager]] section of mount setup, the [[Sequence Configuration#Meridian Flip Tab|Meridian Flip tab]] of the Sequence documentation, and the [[Status Window#Meridian Flip Status LED|Meridian Flip Status LED]] explanation in the Status Window section<br />
*'''Why does Voyager start another exposure when the Orange status indicator is flashing indicating a meridian flip is needed?'''<br />
**The [[Status Window#Meridian Flip Status LED|orange status indicator]] means the meridian has been crossed. The meridian flip won't happen until the "[[Mount Setup#GEM Meridian Flip Manager|Do Flip after Mount Passing Meridian By]]" minutes have passed and the exposure underway ''at that time'' has finished.<br />
*'''My time zone is a partial hour different from UTC (like Australian Central Time which is UTC+9:30) and my meridian flips are happening 30 minutes late (or early).''' <br />
**This has been fixed in Voyager 2.1.7m and later, please upgrade<br />
<br />
<br /><br />
<br />
==Mosaics==<br />
<br />
*'''Does Voyager have a Framing and Mosaic Manager?'''<br />
**Not as of June 2019, although one is being worked on: https://forum.voyagerastro.com/t/framing-mosaic-maker-manager/419<br />
<br />
*'''How can I make a Mosaic with Voyager without a Framing and Mosaic Manager?'''<br />
**A mosaic is just a set of adjacent images. There are many free and paid tools that will let you plan a Mosaic, including the one that will be integrated with Voyager:<br />
***<nowiki>http://www.skycrumbles.net/mosaic-maker/</nowiki><br />
**Just run the tool to plan your mosaic and then copy and paste the coordinates for each panel into a Sequence in Voyager. You can use a Research & Survey sequence to shoot multiple targets with a single sequence.<br />
<br />
<br /><br />
<br />
==PHD2==<br />
<br />
*'''I am new to PHD2, how should I get started?'''<br />
**There are many online tutorials on using PHD2 so we won’t try to recreate them here, but here’s one approach when setting up a new system with PHD2. Create an equipment profile for the connected gear. Start with the PHD2 defaults, then click the Brain icon and make sure your camera’s Pixel Size (on the Camera tab) and Focal Length (on the Guiding tab) are correct. Start taking guide images with PHD2. Hold Shift and click the Guide button to start a calibration run. If you haven’t already created a dark library, you will be prompted to do it. Follow the instructions and PHD2 will create a dark library. Once you have a successful calibration, PHD2 should start guiding automatically. Go to the Tools menu and select the Guiding Assistant. Follow the instructions to run it. It says to let it run at least 2 minutes, until the RMS values settle down. On the PHD2 Yahoo! group, they usually advise to run it for 15 to 20 minutes. However long you run it, when you stop it, it will give you suggestions to improve your guiding algorithm parameters. Accept them. Nine times out of ten, you will have “good enough” guiding at this point to take images.<br />
<br />
<br /><br />
==Plate Solving==<br />
<br />
*'''What happens during a sequence if, after autofocus, plate solving on return to target fails, e.g. due to clouds?'''<br />
**Voyager will try focusing three times with three different stars if you use RoboStar, or on the same field if you use LocalField. If plate solving to position to the focus star fails, Voyager will try blind solving if a blind solver is configured. Otherwise, the focus is aborted and an emergency fast goto is done back to the target.<br />
**If you use guiding and it failed due to clouds, Voyager will try to calibrate the guider three times and for each calibration re-try, it will try to acquire a guide star three times. (note - Voyager does not use stored calibration values)<br />
**If all guide calibration tries fail, the sequence is aborted with an Error status and the actions set in the "On Error" tab are taken.<br />
**If you don't use guiding, the sequence will continue with the normal goto used to position to the target - meaning goto without plate solving, not precision pointing.<br />
**Autofocus will be tried again when scheduled, and also plate solving will be tried three times to goto the focus star.<br />
**After three failed tries to goto a focus star, plate solving to find the focus star is disabled until the first good autofocus. All failure counters are reset if autofocus is successful.<br />
**Voyager's goal is to not stop any time - just not use guiding if it is not available due to clouds.<br />
**If you have a cloud sensor, you can manage the actions taken on cloudiness using DragScript Emergency Suspend, Resume and Exit events<br />
<br />
<br /><br />
<br />
==Session==<br />
<br />
*'''What is the relationship between the Target Coordinates in the OnTheFly workspace and the Sequence defined on that page?'''<br />
**The target coordinates in the OnTheFly panel are used by by the Actions - the things outlined in yellow below. The Actions are simple things like autofocus or precision pointing (slew, plate solve, correct). If you previously defined coordinates with the Target Coordinates search box, the Solved Coordinates plate solve box, or the Solving Referenced FIT box, you will be asked if you want to use those coordinates when you create a new sequence. But if you create a sequence first, without coordinates, then go back to OnTheFly, new coordinates entered, searched or solved do not change the sequence coordinates. The assumption is that you might want to do something "On The Fly" with different coordinates, and you don't want to change your sequence coordinates.<br />
<br />
[[File:Target-coord-onthefly.jpg]]<br />
<br />
==Slewing and Meridian Flips==<br />
<br />
*'''Why does Voyager sometimes stop my mount from slewing when both Voyager and an external program are connected and I initiate a slew from the external program (e.g., Cartes du Ciel)'''<br />
**Voyager has a safety system to stop your mount if it will pass the meridian and Voyager is not doing anything at that time. There's a flag in the Mount Setup tab, under Safety, that controls this behavior. Please read [[Mount Setup#Safety|that section of the Wiki]] for more information<br />
<br />
*'''Note on TheSkyX Conversion Between J2000 and JNow'''<br />
**As of Voyager 2.1.2b, Voyager will double check Conversion between J2000> JNow and JNow> J2000 in case there is a glitch in the telescope data received from TheSkyX. Calculation will automatically switch from conversion by TSX to conversion by ASCOM / Voyager internals if needed<br />
<br />
<br /><br />
<br />
==Starting Third Party Programs==<br />
<br />
*I am unable to start a third party program from Voyager (e.g. PHD2, Cartes du Ciel, TheSkyX)<br />
**Make sure the checkbox allowing Voyager to start the third party program is checked in Setup (e.g. "Try Start Exe On Connect")<br />
**Make sure exceptions are added to any firewall / antivirus / antimalware software you are running to allow Voyager and the third party program to connect<br />
**If Voyager is successfully starting the third party program but you are getting an error, you may need to increase the delay time in Setup on the Voyager tab, under the External PROCESS Starting box. Try a larger number and see if that gives the third party program enough time to start so Voyager can connect.<br />
<br />
==Startup Problems==<br />
<br />
*'''When I try to start Voyager, the startup splash screen is stuck on the message "Sound Preload"'''<br />
*This is rare but it can happen if Voyager was closed abruptly at the OS level, corrupting information about the layout and position of controls and windows in Voyager. <br />
**Navigate to these folders in File Explorer - substitute your OS Login username for <username>. <br />
***C:\Users\<username>\AppData\Local\Leonardo_Orazi<br />
***C:\Users\<username>\AppData\Roaming\Leonardo_Orazi<br />
***Look in the Leonardo_Orazi folders and you should find one or more directories with names like "VOyager2.exe.xxxxxxxxxxxxxxxxxxxxxxxxxx" or similar name where the long string of "x's" are other characters. You may only find the Leonardo_Orazi folder in one of these parent directories.<br />
***Remove all the directories inside the Leonardo_Orazi folders and restart Voyager.<br />
***If you are not comfortable doing this please allow us to help you with a Teamviewer session - email or use the support link on top page at https://software.starkeeper.it/<br /><br />
<br />
<br /><br />
==TheSkyX and Voyager==<br />
<br />
*'''Why do I get "The Index is Out of Range: Error 733" when connecting to TheSkyX?'''<br />
*[[File:Theskyx-error-733.png]]<br />
**Voyager and TheSkyX cannot communicate. The most likely problem is that TheSkyX and Voyager are running in different modes (administrator or user). Let Voyager start TheSkyX - it will do so when you click Connect in Voyager and TheSkyX will inherit the correct mode. Or, if you start TheSkyX manually, make sure it is running in the same mode as Voyager. We recommend and only support administrator mode because connection problems can happen with some software and drivers if Voyager runs in User mode.<br />
**This sequence should work:<br />
<br />
1) Check that Voyager will run as Administrator. (Right click the Voyager icon or Voyager2.exe file, click Properties, click Compatibility tab, make sure Run this program as an Administrator box is checked, click OK)<br />
<br />
[[File:Voyager-run-as-admin2.png]]<br />
<br />
2) Check that TheSkyX can connect to a mount. In TheSkyX (not Voyager), click Connect to Telescope. We want to make sure that independently of Voyager, TheSkyX can connect to the telescope. It could be a Simulator, we just want it to be able to connect successfully.<br />
<br />
3) Close programs and reboot your PC so we are sure there are no TheSkyX processes running<br />
<br />
4) Start Voyager<br />
<br />
5) In Voyager Setup -> Mount tab, choose TheSkyX from the Mount drop-down (we want to try connecting natively to TheSkyX, not via ASCOM)<br />
<br />
6) In Voyager Startup, click Connect <br />
<br />
If there are errors connecting to TheSkyX and the mount, it might be a firewall or antivirus preventing the programs from talking. But let's see if this basic sequence works.<br />
<br />
*'''Why do I get a Connect Error -> SiteLongitude and "Your ASCoM driver can't give the Site Longitude info. Meridian Flip can't be managed from Voyager !!" error when connecting to Paramount's ASCOM driver for TheSkyX?'''<br />
*[[File:Theskyx-longitude-error.png|987x987px]]<br />
**This is a symptom of the same problem as the previous one - Voyager and TheSkyX can't communicate.<br />
**The most likely problem is that TheSkyX and Voyager are running in different modes (administrator or user). Let Voyager start TheSkyX - it will do so when you click Connect in Voyager and TheSkyX will inherit the correct mode. Or, if you start TheSkyX manually, make sure it is running in the same mode as Voyager. We recommend and only support administrator mode because connection problems can happen with some software and drivers if Voyager runs in User mode.<br />
**To run a program as administrator, right click the .exe file and select Properties. From the Compatibility tab of the Properties dialog, check the Run as Administrator box.<br />
**It is also possible that your firewall or anti-virus software is preventing Voyager from connecting. Check your firewall and anti-virus and make sure it is not blocking this connection.<br />
<br />
<br /><br />
==Setting up Application Server and Internal Web Server==<br />
<br />
*'''How can I set up the Application server and Internal Web Server in Voyager ?'''<br />
<br />
*[[File:Application and WebServer settings.png]]<br />
<br />
*Box Application Server<br />
**flag on "Activate it on start"<br />
**flag on "Not logging heartbeat"<br />
**flag on "Allow dashboard service"<br />
**select the image quality for dashboard (more quality mean more bigger data to transfer on the internet/network) default is medium<br />
*Box Web Server<br />
**flag on "Activate it on start"<br />
**use default 80 port if you don't have another web server or service using port 80, change port to 8080 or similar free port if this is not true<br />
*Close Voyager<br />
*Restart Voyager<br />
*Say yes on private and public network flag when Operating System asks for your firewall allowance (don't say no or close it or web server and application server cannot work) and you must do it manually from control panel<br />
*to know at which IP address your PC could answer you need to check in the Application server monitor, you’ll found a list of IP address if application server is turned on, see the attached image.f you have switch on also the Web Server please contact one of this IP with the browser: <nowiki>http://localhost</nowiki> (if you are on the same pc) <nowiki>http://localhost:pppp/</nowiki> (if you are on the same pc and use different port than 80) <nowiki>http://xxx.xxx.xxx.xxx</nowiki> (if you are on the network) <nowiki>http://xxx.xxx.xxx.xxx:pppp</nowiki> (if you are on the network and use different port than 80) Which IP dependes on your networking, someone can be only local, someone can be closed by your firewall/router, someone can change if you are on local olnly or in DHCP environment. If your pc have a hostname use it, better solution: <nowiki>http://hostname</nowiki> (if you are on the same pc) <nowiki>http://hostname:pppp/</nowiki> (if you are on the same pc and use different port than 80)<br />
<br />
<br /><br />
==Copy Voyager Data between different PC==<br />
<br />
*'''How can I move voyager data between two different PC ?'''<br />
<br />
Its possible to move data information about Voyager (profiles, sequences,autofocus setting, FIT Data) between two PC without lost any data. Just copy the folder "Voyager" that you can found in "Documents" folder of your PC. Paste it in a USB pen drive or in LAN shared folder. In the new PC install Voyager (if not was done), open at least 1 time, close it, copy the "Voyager" folder in USB inside the "Documents" folder of the new PC. Open Voyager in new PC. Thats all.<br />
==Using DragScript to create Parametric Dark (or DarkFlat)==<br />
<br />
*'''How can I realize autoamtically Dark with different time also for DarkFlat ?'''<br />
<br />
Its possible to use the DragScript and the exposure block in conjunction with the decimal variables feature in Voyager to create a simple DragScript that create parametric Dark (in terms of exposure time) really fast. Look at this script:<br />
<br />
[[File:DSParametricDark.png]]<br />
<br />
This DragScript take a series of 10 dark starting from 0 to 2 seconds with increment between dark of 0.2 second.<br />
<br />
10 dark at 0s<br />
<br />
10 dark at 0.2s<br />
<br />
10 dark at 0.4s<br />
<br />
10 dark at 0.6s<br />
<br />
…<br />
<br />
…<br />
<br />
10 dark at 1.8s<br />
<br />
10 dark at 2s<br />
<br />
Editing the repeat times and the initial value of ''darktime'' variable and the DO IF control value you are able to create your own parametric dark …<br />
[[Category:Manual|Z]]<br />
[[Category:FAQ]]<br />
[[Category:All]]</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=FAQ&diff=5634FAQ2020-10-12T11:08:09Z<p>Rowland: </p>
<hr />
<div>Post your questions in the Voyager Forum at https://forum.starkeeper.it We monitor that forum and will add the answers here if appropriate.<br />
<br />
<br />
==4K Monitor Resolution from Local or Remote Desktop==<br />
'''I have some font size problem on 4K monitor resolution, font is scaled to small and cannot show correctly Voyager Windows?'''<br />
<br />
*There is a compatibility tab in the windows properties for the Voyager application. On this tab is a button labelled “Change high DPI settings”. I then checked the box for “Use this setting to fix scaling problems for this program instead of the one in settings” and for “Use the DPI that’s set for my main display when:” I selected “I signed into Windows”. I think that means if I sign in locally on the observatory PC with a 1920x1080 monitor it uses this DPI and if I sign in remotely with my laptop and 4K display it uses this DPI.[[File:4kA.png|600x600px]][[File:4KB.png|452x452px]]<br />
<br />
<br /><br />
==Artificial Intelligence (AI) in Voyager==<br />
<br />
*'''What is the benefit to users of the AI automata inside of Voyager?'''<br />
**Voyager uses AI technology to improve focus, star recognition , equation calculation for VCurve, statistical calculations, and decisions for how to handle exceptions generated by the watchdog timers. Watchdogs are timers that oversee all requests to external hardware and software and recover from soft errors. The bottom line is that the advanced AI technology inside of Voyager contributes significantly to Voyager's exceptional reliability!<br />
<br />
==AstroPhysics Mounts and APCC==<br />
<br />
*'''What is the best way to connect to APCC from Voyager?'''<br />
**Short answer courtesy of Voyager user Bill Long: ''I run Voyager in admin mode.'' ''I just open APCC first in admin mode, connect the ASCOM driver to APCC, then connect via Voyager. Works fine.''<br />
*'''I tried this but still having problems connecting to APCC from Voyager'''<br />
**In setup for APCC, in the lower-left corner, you’ll need to uncheck the two boxes in the AP V2 Driver section labeled “auto connect” and “auto config”. This will allow Voyager to start the driver first without APCC interfering with other startup functions.<br />
<br />
<br /><br />
==AutoFocus==<br />
<br />
*'''LocalField autofocus fails with an out-of-memory error [For version older than 2.2.1b]'''<br />
**'''This problem was solved in Voyager version 2.2.1c and newer'''<br />
**Try using a smaller ROI or binning 2x2 instead of 1x1. The image is managed in memory using a Microsoft memory object that does not do garbage collection, so depending on what other programs are running and possibly using this memory, you may run out if your camera creates large images with each shot. NOTE: Be sure to set the binning for LocalField autofocus in the correct spot for your camera:<br />
***If your camera does '''not''' have filters, use the Focus Bin setting - it's in Setup -> AutoFocus -> Robofire Configuration -> LocalField Mode:<br />
***[[File:Localfield-focus-bin.jpg|514x514px]]<br />
***If your camera does have filters, its in the per-filter settings dialog, which is in Setup -> Camera, then click the EDIT button in the Filters panel:<br />
***[[File:Localfield-per-filter-bin.png]] <br /><br />
<br />
**'''How do I request an autofocus while a sequence or DragScript is running?'''<br />
***Click the Monitor tab, then click AutoFocus. Choose the filter for autofocus. The current exposure will finish, then an autofocus will be performed, and then the sequence or DragScript will resume.<br />
***[[File:Inject-autofocus.png]]<br />
<br />
<br /><br />
<br />
*'''TheSkyX @Focus2 slews to a Focus Star but doesn't return to my target.''' <br />
**Choose Voyager RoboStar in your Sequence setup, Focus tab. Voyager will choose a focus star, call TheSkyX @Focus2 which does the autofocus, and then Voyager will slew back to your target<br />
**Be sure to uncheck "Automatically slew telescope to the nearest appropriate focus star" in TheSkyX @Focus2<br />
**[[File:Theskyx-atfocus2-nofocusstar.jpg]] <br /><br />
*'''Does Voyager implement Temperature Compensation (move the focuser a predetermined amount based on ambient temperature)?'''<br />
**No, Voyager does not implement temperature compensation. Even the author of FocusMax says that temperature compensation gives inconsistent results and he decided not to use it. We want your images to have sharp focus. Voyager's goal is reliable imaging automation and unfortunately temperature compensation is unreliable. If you still want to use temperature compensation, you can find some focuser drivers that implement it for you in the driver software.<br /><br />
<br />
==Cameras==<br />
<br />
*'''Can Voyager use my FLI Camera?'''<br />
**You can connect to an FLI camera using TheSkyX, Maxim DL, or the ASCOM driver written by Hartmut Bornemann in the Yahoo! FLI Imaging Systems group at:https://groups.yahoo.com/neo/groups/FLI_Imaging_Systems/files/Hartmut%20Bornemann/<br />
**There is a checkbox in his driver labelled “Can Fast Readout." This must be unchecked. If it is checked, Voyager will not be able to consistently change the readout mode. (thanks to Bill Long for the tip)<br />
<br />
[[File:FLI Driver Image.png]]<br /><br />
<br />
*'''Can Voyager use my SBIG camera?'''<br />
**You can connect to your SBIG camera using TheSkyX or Maxim DL. There is no native support in Voyager for SBIG cameras as of Voyager 2.1.4. We need access to a camera to test a native driver. This may happen in the future but we don't have any firm as of this writing (June 2019)<br />
<br />
*'''I get an Out of Memory Error when trying to take exposures with my Camera using the ASCOM driver'''<br />
**Voyager runs as a 32-bit application so has access to 4GB no matter how much RAM is installed on your PC. Reboot your PC and only run the other applications you need.<br />
*'''Downloads from my camera are hanging'''<br />
**Check your USB cable lengths. The maximum length specified for USB3 is 3 meters - longer than that and you may have problems.<br />
**For ASI cameras, try reducing the download speed in the ASCOM driver<br />
<br />
*'''Can Voyager support Gain and Offset for my ZWO ASI CMOS camera?'''<br />
**As of Voyager 2.1.6b, an [[Camera Setup#ASI Native Driver|ASI Camera native driver]] is available as a choice in Camera setup. Use this driver and you can set Gain and Offset individually for each [[Sequence Configuration#Sequence Elements|Sequence Element]].<br />
**You '''cannot''' set Gain or Offset using the ASI ASCOM driver, you must use the ASI Camera native driver.<br />
*'''Does Voyager add GAIN and OFFSET keywords to my image file FITS headers?'''<br />
**As of Voyager 2.1.6b, if you use the [[Camera Setup#ASI Native Driver|ASI Camera native driver]], the GAIN and OFFSET keywords will be set in the image file FITS headers.<br /><br />
<br />
==Cooling==<br />
<br />
*'''Why did Voyager put "NoCooling" in the file name saved by my Sequence?'''<br />
*This happens when the Sequence's “Cooling” checkbox on the Cooling tab is unchecked. This means you have cooling on in your camera but Voyager's Sequence is not managing it. You may have started cooling from the Voyager command box or from the camera control, extrernal to Voyager. It is thus possible that the camera has been cooled, but it will say NoCooling because Voyager is not managing the temperature. If there’s an error in cooling you might see the text "UNK" in your file name.<br />
<br />
==Connection / Startup==<br />
<br />
*'''I get a red error message when I click Connect in the Startup workspace - Voyager can't connect to third party software such as TheSkyX, Maxim DL, PHD2, etc.'''<br />
**Ensure Voyager is [[Installation|running as administrator]]. Start Voyager before all other programs. Let Voyager start the other programs it needs. They will inherit the proper mode from Windows when Voyager starts them.<br />
**If you still have an error, check your antivirus software to make sure it is not preventing Voyager from communicating with other programs.<br />
**If the inter-program communication is via TCP/IP ports, check that Voyager and the third party program are allowed to access ports in the Windows firewall, or any other firewall you may be running<br />
*'''I get a red error message when I click Connect in the Startup workspace - Voyager can't connect to my hardware'''<br />
**Ensure Voyager is [[Installation|running as administrator]]. Check that your hardware is powered up and configured properly in Voyager and any driver software used to connect to it.<br />
**Ensure the COM port has not changed - sometimes Windows assigns a different COM port and your hardware driver will not be able to connect to your gear.<br />
**For camera connection problems, try applying the [[Camera Setup#Various|Slow Polling flag]] in Camera Setup. Some camera drivers can't handle requests spaced too closely together<br />
**For mount connection problems, try applying the [[Mount Setup#Data Polling|Slow Polling flag]] in Mount Setup. Some mount drivers can't handle requests spaced too closely together<br />
*'''Voyager closes after trying to connect to other software or hardware'''<br />
**Voyager will only close if a driver had a critical failure at the Windows kernel level that cannot be handled. Please activate the ASCOM log and report to the driver developers.<br />
*'''Voyager has problems connecting to my ASCOM device'''<br />
**See above suggestions<br />
**Make sure the version of ASCOM you have installed is the correct one for your driver<br />
**If your driver accepts only one connection (a serial error when you try to connect from Voyager would indicate this) you can connect only one app. If you want connect more than one app you must use an ASCOM hub.<br />
<br />
Voyager implements standard ASCOM. <br />
<br />
==Dome==<br />
<br />
*'''I have the HiTec Roll-Off-Roof controller. I am getting "The requested operation is not permitted at this time" errors. What should I do?'''<br />
**These errors have been seen when using the ASCOM driver as standard. Try the ASCOM Dome ConnectionLess Interface, which seems to eliminate these errors<br />
*'''Voyager started taking images before the dome had finished rotating'''<br />
**Voyager will slave to the dome when starting a sequence only if you check the box '''Slave on Sequence Start''' in Setup -> Dome:<br />
**[[File:Dome-slave-on-seq-start.jpg]]<br />
**If you don't do a specific command to slave the dome in Voyager, you'll see the message "Slave is unlock from user" in the monitor window<br />
**This is because some drivers don't report slave status to Voyager<br />
**If you create a DragScript to manage all night imaging remember to put a slave on block in the script if you do other mount operations before starting a sequence.<br />
**Also remember to slave off and park the dome at the end of the script<br />
*'''I use VIking to control my Dome (or Roll-Off Roof). How do I connect it to Voyager's Dome controls?'''<br />
**Voyager's Dome controls are only for ASCOM drivers. To use Viking from Voyager, build a DragScript and use the Viking actions to read and write to Viking's relays, switches and controls.<br />
**This video explains how to do this: <nowiki>https://vimeo.com/331171731</nowiki><br />
*'''How do I make sure Voyager doesn't move my scope if I have a Roll Off Roof and the roof is closed?'''<br />
**Go to SetupForm/Dome and you will see a tick box: “Abort GoTo actions if Dome mode is Roll off Roof and the Shutter is closed” A tick there will stop any clash between scope and roof. (Courtesy of Graham on our forum)<br />
*'''How can I get slaving to work with my MaxDome ASCOM driver?'''<br />
**Use Voyager RoboSync to slave the dome.<br /><br />
<br />
==DSLR Support==<br />
<br />
*'''Can I use my DSLR camera (Canon, Nikon) with Voyager?'''<br />
**Voyager supports camera connection via ASCOM drivers, Maxim DL, or TheSkyX<br />
**We strongly recommend using Maxim DL or TheSkyX with DSLR's as their camera support has been widely used<br />
**There is an [https://github.com/vtorkalo/ASCOM.DSLR open source ASCOM.DSLR driver] that may work for you. It can connect via the Canon or Nikon SDK's, or for Canon cameras, it can also connect via [https://www.otelescope.com/ O'telescope's Backyard EOS].<br />
**We cannot help you if this doesn't work, but if you want to try using the ASCOM.DSLR driver, we wrote a [[ASCOM.DSLR|Wiki page on how to set it up]]<br />
<br />
<br /><br />
==Editing a DragScript==<br />
<br />
*'''I can't get Drag and Drop to work in the DragScript Editor (perhaps with a remote desktop connection such as VNC, TeamViewer, etc)'''<br />
**You can only drop DragScript elements where the mouse pointer shape changes to an arrow with a little rectangle attached when you hover over the desired drop location.<br />
**On Windows 10, the mouse pointer will not change shape if there is no mouse connected to the remote PC. To enable the mouse pointer shape changing with no mouse connected:<br />
***Right click the Windows button on the remote PC's desktop (not on your local PC)<br />
***Click Settings<br />
***Type "Mouse Keys" in the search box and select "Turn Mouse Keys On or Off"<br />
***Turn Mouse Keys on <br /><br />
<br />
[[File:Filename-spec.jpg]]<br />
<br />
#Target name<br />
#Type of exposure: Light, Dark, or Bias<br />
#Suffix: whatever you type in the "Suffix" field. Filter names are used here.<br />
#Exposure length<br />
#Binning level<br />
#Sensor temperature<br />
#Sequence number: a sequential number generated automatically when Voyager takes a new image<br />
#Date: YYYYMMDD<br />
#Time: HHMMSS<br />
#MS: millisecond portion of the time the image was taken<br />
#Position Angle<br />
#Position relative to Meridian: E = East or W = West<br />
#File type: FIT for a FITS file<br />
<br />
==Filenames==<br />
<br />
*'''Can I use my own filenames for images taken with Voyager?'''<br />
**'''Sequences''': You can add something to the image filenames created by a sequence by typing it into the Suffix field - in this example, the filter name is used[[File:Sequence-elements.png]]<br />
**'''Other:''' With the Camera -> Expose action in a DragScript, you can specify the filename however you like<br />
*'''What do the fields mean in the default image filenames saved by Sequences?'''<br />
<br />
==Filters==<br />
<br />
*'''How can I have Voyager use Filter Offsets (automatically change focus position when switching filters with a filter wheel)?'''<br />
**Set this up in the ASCOM driver for your filter wheel, or in TheSkyX or Maxim DL if you use them for your Camera control<br />
<br />
<br /><br />
==Flats==<br />
<br />
*'''How can I take flats without the variable exposure feature of Auto Flats?'''<br />
**There are at least two ways to do this. Use the Camera -> Expose option in a DragScript. You can enter your desired exposure length and choose Flat as your exposure type. Or, enter your desired exposure length in Auto Flats for the minimum, maximum, and initial exposure times. Set the desired ADU to your mid-range (usually 32767) and 100% as your error tolerance.<br />
*'''My Auto Flats never finish, they keep looping trying to find the proper exposure time but it is always outside the allowed error tolerance'''<br />
**Try using a larger ROI - with a camera with a large number of pixels, the mean ADU of the default small ROI can change quite a bit. Also, look at the deviation in percent reported in the Monitor window. Increase your allowed error tolerance if necessary. You can also change the ROI to "no" and Voyager will determine exposure length based on the entire image, but this takes a little longer.<br />
<br />
==Guiding==<br />
<br />
*'''What's the difference between RoboGuide and Native Guide controls?'''<br />
**If you use RoboGuide, Voyager will choose a guide star using the parameters you set in RoboGuide Advanced<br />
**[[File:Roboguide-advanced.jpg]]<br />
**If you use Native Guide Control, Voyager will let your guiding software (PHD2, Maxim DL, TheSkyX) choose the guide star<br />
*'''Why does RoboGuide choose saturated guide stars?'''<br />
**This happens if you check '''Force Use Saturated Stars''' in the RoboGuide Advanced section of Guiding setup. This can be useful at long focal lengths where only a few guide stars are available. Sometimes a saturated star is the best choice for guiding.<br />
**If you use a CMOS camera, check with a viewer to see what ADU value returned for a saturated star. Put this value in the '''Override Guide Star Saturation ADU Value''' box and uncheck '''Force Use Saturated Stars''' and Voyager's AI will choose guide stars below this value<br />
**[[File:Roboguide-setup-211e.jpg]]<br />
**You can read the ADU value of a guide star inside of PHD2 if you use that for guiding<br />
**[[File:PHD2-ADU-Readout.png]]<br />
<br />
==Licensing==<br />
<br />
*'''What's the difference between "Demo" and "Trial" modes?'''<br />
**The Voyager download installs in Demo mode. This is a perpetual, full functionality version of Voyager that times out after 60 minutes. Trial mode is full functionality with no session time limit, but limited to 45 days from the time you start the trial (which can be a later date than installation).<br />
*'''How do I get a license for my second or third PC's?'''<br />
**Install the download on your second or third PC. Copy the serial number, which is unique to that PC, and email it to Leo or use the form at https://voyagerastro.com/contact-us/<br />
*'''Can I install the Free Trial download on multiple computers?'''<br />
**Yes. It will install in "Demo" mode which is full functionality with a 60 minute session timeout. You can start the 45 day free trial at any time by clicking the Activate Trial button on the startup splash screen.<br />
*'''Do I need to install Voyager to get a serial number before buying a license?'''<br />
**Yes. Each installation of Voyager has a unique serial number that is generated when you install it. Find your serial number by running Voyager, clicking the Resource menu, then the License option<br />
<br />
[[File:License-resource.jpg]]<br />
<br />
**Copy the serial number from the License window and enter it in the Serial Number field of the license purchase form<br />
<br />
<br /><br />
<br />
==Meridian Flips==<br />
<br />
*'''How do I set up Voyager to manage meridian flips?'''<br />
**Determine how far past the meridian your scope can slew without a pier crash. Let's say this is 30 minutes. Choose a value less than this, default is 10 minutes, and put that number in the "[[Mount Setup#GEM Meridian Flip Manager|Do Flip after Mount Passing Meridian By]]" field in Mount Setup. If you want Voyager to finish the current exposure before doing the flip, allow enough time for your longest exposures to complete. E.g. if your longest exposure is 10 minutes in this example, Voyager would do the meridian flip no later than 20 minutes past the meridian, which would be OK with a 30 minute max for your equipment.<br />
**We don't recommend using zero (0) for the Do Flip after Mount Passing Meridian By" number, because this requires precise synchronization of the time settings in your PC and mount and the lat/long position of your site, and you must choose the "'''ASCOM - Read LST from Driver'''" in Mount Setup<br />
**Make sure your mount driver does not also do an automatic meridian flip when it is just tracking past the meridian<br />
**Choose Manage from Meridian Flip Mode in the [[Sequence Configuration#Meridian Flip Tab|Meridian Flip tab of the Sequence]] definition.<br />
**Run your sequences. When your scope crosses the meridian plus the number of minutes you specified in "Do Flip after Mount Passing Meridian By" minutes, Voyager will wait until the current exposure finishes, then perform the meridian flip before starting the next one.<br />
**For a more thorough explanation, read the [[Mount Setup#GEM Meridian Flip Manager|GEM Meridian Flip Manager]] section of mount setup, the [[Sequence Configuration#Meridian Flip Tab|Meridian Flip tab]] of the Sequence documentation, and the [[Status Window#Meridian Flip Status LED|Meridian Flip Status LED]] explanation in the Status Window section<br />
*'''Why does Voyager start another exposure when the Orange status indicator is flashing indicating a meridian flip is needed?'''<br />
**The [[Status Window#Meridian Flip Status LED|orange status indicator]] means the meridian has been crossed. The meridian flip won't happen until the "[[Mount Setup#GEM Meridian Flip Manager|Do Flip after Mount Passing Meridian By]]" minutes have passed and the exposure underway ''at that time'' has finished.<br />
*'''My time zone is a partial hour different from UTC (like Australian Central Time which is UTC+9:30) and my meridian flips are happening 30 minutes late (or early).''' <br />
**This has been fixed in Voyager 2.1.7m and later, please upgrade<br />
<br />
<br /><br />
<br />
==Mosaics==<br />
<br />
*'''Does Voyager have a Framing and Mosaic Manager?'''<br />
**Not as of June 2019, although one is being worked on: https://forum.voyagerastro.com/t/framing-mosaic-maker-manager/419<br />
<br />
*'''How can I make a Mosaic with Voyager without a Framing and Mosaic Manager?'''<br />
**A mosaic is just a set of adjacent images. There are many free and paid tools that will let you plan a Mosaic, including the one that will be integrated with Voyager:<br />
***<nowiki>http://www.skycrumbles.net/mosaic-maker/</nowiki><br />
**Just run the tool to plan your mosaic and then copy and paste the coordinates for each panel into a Sequence in Voyager. You can use a Research & Survey sequence to shoot multiple targets with a single sequence.<br />
<br />
<br /><br />
<br />
==PHD2==<br />
<br />
*'''I am new to PHD2, how should I get started?'''<br />
**There are many online tutorials on using PHD2 so we won’t try to recreate them here, but here’s one approach when setting up a new system with PHD2. Create an equipment profile for the connected gear. Start with the PHD2 defaults, then click the Brain icon and make sure your camera’s Pixel Size (on the Camera tab) and Focal Length (on the Guiding tab) are correct. Start taking guide images with PHD2. Hold Shift and click the Guide button to start a calibration run. If you haven’t already created a dark library, you will be prompted to do it. Follow the instructions and PHD2 will create a dark library. Once you have a successful calibration, PHD2 should start guiding automatically. Go to the Tools menu and select the Guiding Assistant. Follow the instructions to run it. It says to let it run at least 2 minutes, until the RMS values settle down. On the PHD2 Yahoo! group, they usually advise to run it for 15 to 20 minutes. However long you run it, when you stop it, it will give you suggestions to improve your guiding algorithm parameters. Accept them. Nine times out of ten, you will have “good enough” guiding at this point to take images.<br />
<br />
<br /><br />
==Plate Solving==<br />
<br />
*'''What happens during a sequence if, after autofocus, plate solving on return to target fails, e.g. due to clouds?'''<br />
**Voyager will try focusing three times with three different stars if you use RoboStar, or on the same field if you use LocalField. If plate solving to position to the focus star fails, Voyager will try blind solving if a blind solver is configured. Otherwise, the focus is aborted and an emergency fast goto is done back to the target.<br />
**If you use guiding and it failed due to clouds, Voyager will try to calibrate the guider three times and for each calibration re-try, it will try to acquire a guide star three times. (note - Voyager does not use stored calibration values)<br />
**If all guide calibration tries fail, the sequence is aborted with an Error status and the actions set in the "On Error" tab are taken.<br />
**If you don't use guiding, the sequence will continue with the normal goto used to position to the target - meaning goto without plate solving, not precision pointing.<br />
**Autofocus will be tried again when scheduled, and also plate solving will be tried three times to goto the focus star.<br />
**After three failed tries to goto a focus star, plate solving to find the focus star is disabled until the first good autofocus. All failure counters are reset if autofocus is successful.<br />
**Voyager's goal is to not stop any time - just not use guiding if it is not available due to clouds.<br />
**If you have a cloud sensor, you can manage the actions taken on cloudiness using DragScript Emergency Suspend, Resume and Exit events<br />
<br />
<br /><br />
<br />
==Session==<br />
<br />
*'''What is the relationship between the Target Coordinates in the OnTheFly workspace and the Sequence defined on that page?'''<br />
**The target coordinates in the OnTheFly panel are used by by the Actions - the things outlined in yellow below. The Actions are simple things like autofocus or precision pointing (slew, plate solve, correct). If you previously defined coordinates with the Target Coordinates search box, the Solved Coordinates plate solve box, or the Solving Referenced FIT box, you will be asked if you want to use those coordinates when you create a new sequence. But if you create a sequence first, without coordinates, then go back to OnTheFly, new coordinates entered, searched or solved do not change the sequence coordinates. The assumption is that you might want to do something "On The Fly" with different coordinates, and you don't want to change your sequence coordinates.<br />
<br />
[[File:Target-coord-onthefly.jpg]]<br />
<br />
==Slewing and Meridian Flips==<br />
<br />
*'''Why does Voyager sometimes stop my mount from slewing when both Voyager and an external program are connected and I initiate a slew from the external program (e.g., Cartes du Ciel)'''<br />
**Voyager has a safety system to stop your mount if it will pass the meridian and Voyager is not doing anything at that time. There's a flag in the Mount Setup tab, under Safety, that controls this behavior. Please read [[Mount Setup#Safety|that section of the Wiki]] for more information<br />
<br />
*'''Note on TheSkyX Conversion Between J2000 and JNow'''<br />
**As of Voyager 2.1.2b, Voyager will double check Conversion between J2000> JNow and JNow> J2000 in case there is a glitch in the telescope data received from TheSkyX. Calculation will automatically switch from conversion by TSX to conversion by ASCOM / Voyager internals if needed<br />
<br />
<br /><br />
<br />
==Starting Third Party Programs==<br />
<br />
*I am unable to start a third party program from Voyager (e.g. PHD2, Cartes du Ciel, TheSkyX)<br />
**Make sure the checkbox allowing Voyager to start the third party program is checked in Setup (e.g. "Try Start Exe On Connect")<br />
**Make sure exceptions are added to any firewall / antivirus / antimalware software you are running to allow Voyager and the third party program to connect<br />
**If Voyager is successfully starting the third party program but you are getting an error, you may need to increase the delay time in Setup on the Voyager tab, under the External PROCESS Starting box. Try a larger number and see if that gives the third party program enough time to start so Voyager can connect.<br />
<br />
==Startup Problems==<br />
<br />
*'''When I try to start Voyager, the startup splash screen is stuck on the message "Sound Preload"'''<br />
*This is rare but it can happen if Voyager was closed abruptly at the OS level, corrupting information about the layout and position of controls and windows in Voyager. <br />
**Navigate to these folders in File Explorer - substitute your OS Login username for <username>. <br />
***C:\Users\<username>\AppData\Local\Leonardo_Orazi<br />
***C:\Users\<username>\AppData\Roaming\Leonardo_Orazi<br />
***Look in the Leonardo_Orazi folders and you should find one or more directories with names like "VOyager2.exe.xxxxxxxxxxxxxxxxxxxxxxxxxx" or similar name where the long string of "x's" are other characters. You may only find the Leonardo_Orazi folder in one of these parent directories.<br />
***Remove all the directories inside the Leonardo_Orazi folders and restart Voyager.<br />
***If you are not comfortable doing this please allow us to help you with a Teamviewer session - email or use the support link on top page at https://software.starkeeper.it/<br /><br />
<br />
<br /><br />
==TheSkyX and Voyager==<br />
<br />
*'''Why do I get "The Index is Out of Range: Error 733" when connecting to TheSkyX?'''<br />
*[[File:Theskyx-error-733.png]]<br />
**Voyager and TheSkyX cannot communicate. The most likely problem is that TheSkyX and Voyager are running in different modes (administrator or user). Let Voyager start TheSkyX - it will do so when you click Connect in Voyager and TheSkyX will inherit the correct mode. Or, if you start TheSkyX manually, make sure it is running in the same mode as Voyager. We recommend and only support administrator mode because connection problems can happen with some software and drivers if Voyager runs in User mode.<br />
**This sequence should work:<br />
<br />
1) Check that Voyager will run as Administrator. (Right click the Voyager icon or Voyager2.exe file, click Properties, click Compatibility tab, make sure Run this program as an Administrator box is checked, click OK)<br />
<br />
[[File:Voyager-run-as-admin2.png]]<br />
<br />
2) Check that TheSkyX can connect to a mount. In TheSkyX (not Voyager), click Connect to Telescope. We want to make sure that independently of Voyager, TheSkyX can connect to the telescope. It could be a Simulator, we just want it to be able to connect successfully.<br />
<br />
3) Close programs and reboot your PC so we are sure there are no TheSkyX processes running<br />
<br />
4) Start Voyager<br />
<br />
5) In Voyager Setup -> Mount tab, choose TheSkyX from the Mount drop-down (we want to try connecting natively to TheSkyX, not via ASCOM)<br />
<br />
6) In Voyager Startup, click Connect <br />
<br />
If there are errors connecting to TheSkyX and the mount, it might be a firewall or antivirus preventing the programs from talking. But let's see if this basic sequence works.<br />
<br />
*'''Why do I get a Connect Error -> SiteLongitude and "Your ASCoM driver can't give the Site Longitude info. Meridian Flip can't be managed from Voyager !!" error when connecting to Paramount's ASCOM driver for TheSkyX?'''<br />
*[[File:Theskyx-longitude-error.png|987x987px]]<br />
**This is a symptom of the same problem as the previous one - Voyager and TheSkyX can't communicate.<br />
**The most likely problem is that TheSkyX and Voyager are running in different modes (administrator or user). Let Voyager start TheSkyX - it will do so when you click Connect in Voyager and TheSkyX will inherit the correct mode. Or, if you start TheSkyX manually, make sure it is running in the same mode as Voyager. We recommend and only support administrator mode because connection problems can happen with some software and drivers if Voyager runs in User mode.<br />
**To run a program as administrator, right click the .exe file and select Properties. From the Compatibility tab of the Properties dialog, check the Run as Administrator box.<br />
**It is also possible that your firewall or anti-virus software is preventing Voyager from connecting. Check your firewall and anti-virus and make sure it is not blocking this connection.<br />
<br />
<br /><br />
==Setting up Application Server and Internal Web Server==<br />
<br />
*'''How can I set up the Application server and Internal Web Server in Voyager ?'''<br />
<br />
*[[File:Application and WebServer settings.png]]<br />
<br />
*Box Application Server<br />
**flag on "Activate it on start"<br />
**flag on "Not logging heartbeat"<br />
**flag on "Allow dashboard service"<br />
**select the image quality for dashboard (more quality mean more bigger data to transfer on the internet/network) default is medium<br />
*Box Web Server<br />
**flag on "Activate it on start"<br />
**use default 80 port if you don't have another web server or service using port 80, change port to 8080 or similar free port if this is not true<br />
*Close Voyager<br />
*Restart Voyager<br />
*Say yes on private and public network flag when Operating System asks for your firewall allowance (don't say no or close it or web server and application server cannot work) and you must do it manually from control panel<br />
*to know at which IP address your PC could answer you need to check in the Application server monitor, you’ll found a list of IP address if application server is turned on, see the attached image.f you have switch on also the Web Server please contact one of this IP with the browser: <nowiki>http://localhost</nowiki> (if you are on the same pc) <nowiki>http://localhost:pppp/</nowiki> (if you are on the same pc and use different port than 80) <nowiki>http://xxx.xxx.xxx.xxx</nowiki> (if you are on the network) <nowiki>http://xxx.xxx.xxx.xxx:pppp</nowiki> (if you are on the network and use different port than 80) Which IP dependes on your networking, someone can be only local, someone can be closed by your firewall/router, someone can change if you are on local olnly or in DHCP environment. If your pc have a hostname use it, better solution: <nowiki>http://hostname</nowiki> (if you are on the same pc) <nowiki>http://hostname:pppp/</nowiki> (if you are on the same pc and use different port than 80)<br />
<br />
<br /><br />
==Copy Voyager Data between different PC==<br />
<br />
*'''How can I move voyager data between two different PC ?'''<br />
<br />
Its possible to move data information about Voyager (profiles, sequences,autofocus setting, FIT Data) between two PC without lost any data. Just copy the folder "Voyager" that you can found in "Documents" folder of your PC. Paste it in a USB pen drive or in LAN shared folder. In the new PC install Voyager (if not was done), open at least 1 time, close it, copy the "Voyager" folder in USB inside the "Documents" folder of the new PC. Open Voyager in new PC. Thats all.<br />
==Using DragScript to create Parametric Dark (or DarkFlat)==<br />
<br />
*'''How can I realize autoamtically Dark with different time also for DarkFlat ?'''<br />
<br />
Its possible to use the DragScript and the exposure block in conjunction with the decimal variables feature in Voyager to create a simple DragScript that create parametric Dark (in terms of exposure time) really fast. Look at this script:<br />
<br />
[[File:DSParametricDark.png]]<br />
<br />
This DragScript take a series of 10 dark starting from 0 to 2 seconds with increment between dark of 0.2 second.<br />
<br />
10 dark at 0s<br />
<br />
10 dark at 0.2s<br />
<br />
10 dark at 0.4s<br />
<br />
10 dark at 0.6s<br />
<br />
…<br />
<br />
…<br />
<br />
10 dark at 1.8s<br />
<br />
10 dark at 2s<br />
<br />
Editing the repeat times and the initial value of ''darktime'' variable and the DO IF control value you are able to create your own parametric dark …<br />
[[Category:Manual|Z]]<br />
[[Category:FAQ]]<br />
[[Category:All]]</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=Main_Page&diff=5633Main Page2020-10-12T10:55:04Z<p>Rowland: </p>
<hr />
<div>==Welcome==<br />
<br />
Welcome to the Official English language Wiki for the Voyager astrophotography automation software. <br />
<br />
Voyager is commercial software written and sold by Leonardo Orazi. The official website is [https://software.starkeeper.it Starkeeper.it].<br />
<br />
This Wiki's purpose is to provide an English documentation, and to allow other Voyager users to contribute to the English language documentation.<br />
<br />
Enjoy!<br />
<br />
<br /><br />
<br />
==Downloadable PDF Manual==<br />
A downloadable PDF version of the contents of this Wiki is available here: https://wiki.starkeeper.it/images/voyager.pdf<br />
<br /><br />
==Contents==<br />
<br />
#[[Introduction]]<br />
#[[Installation]]<br />
#[[Licensing]]<br />
#[[Main Window]]<br />
#[[Status Window]]<br />
#[[Command Window]]<br />
#[[Setup]]<br />
#[[Startup]]<br />
#[[OnTheFly]]<br />
##[[OnTheFly#Sequences|Sequences]]<br />
##[[OnTheFly#Auto Flats|Auto Flats]]<br />
##[[OnTheFly#Research Survey|Research Survey]]<br />
#DragScript<br />
##[[DragScript|Editor]]<br />
##[[DragScript Elements|Actions]]<br />
##[[DragScript Other Elements|Other Elements]]<br />
##[[DragScript#Variables and Control Flow|Variables and Control Flow]]<br />
##[[DragScript Examples|Examples]]<br />
#Tutorials<br />
##[[Quick Start]]<br />
##[[DragScript Examples]]<br />
<br />
==Disclaimer==<br />
While the authors of this Wiki have worked hard to make the information useful, we cannot guarantee it is correct.<br />
<br />
This is a volunteer effort to help the community, and there are no warranties expressed or implied. <br />
<br />
<br />
'''USE AT YOUR OWN RISK!'''<br />
<br />
<br />
'''Please use care and caution and watch your equipment closely while running it with Voyager or any automation software, especially when trying something out for the first time.'''<br />
<br />
<br />
'''By using the information in this Wiki, you acknowledge that you are doing so at your own risk.''' <br />
<br />
<br />
'''The authors of this Wiki assume no liability for any loss or damage to your data or equipment resulting from your use of information in this Wiki.'''<br />
<br /><br />
[[Category:All]]<br />
[[Category:Manual|Ab]]</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=Main_Page&diff=5632Main Page2020-10-12T10:54:23Z<p>Rowland: </p>
<hr />
<div>==Welcome==<br />
<br />
Welcome to the Official English language Wiki for the Voyager astrophotography automation software. <br />
<br />
Voyager is commercial software written and sold by Leonardo Orazi. The official website is [https://software.starkeeper.it Starkeeper.it].<br />
<br />
This Wiki's purpose is to provide an English documentation, and to allow other Voyager users to contribute to the English language documentation.<br />
<br />
Enjoy!<br />
<br />
<br /><br />
<br />
==Downloadable PDF Manual==<br />
A downloadable PDF version of the contents of this Wiki is available here: https://wiki.starkeeper.it/images/voyager.pdf<br />
<br /><br />
==Contents==<br />
<br />
#[[Introduction]]<br />
#[[Installation]]<br />
#[[Licensing]]<br />
#[[Main Window]]<br />
#[[Status Window]]<br />
#[[Command Window]]<br />
#[[Setup]]<br />
#[[Startup]]<br />
#[[OnTheFly]]<br />
##[[OnTheFly#Sequences|Sequences]]<br />
##[[OnTheFly#Auto Flats|Auto Flats]]<br />
##[[OnTheFly#Research Survey|Research Survey]]<br />
#DragScript<br />
##[[DragScript|Editor]]<br />
##[[DragScript Elements|Actions]]<br />
##[[DragScript Other Elements|Other Elements]]<br />
##[[DragScript#Variables and Control Flow|Variables and Control Flow]]<br />
##[[DragScript Examples|Examples]]<br />
#Tutorials<br />
##[[Quick Start]]<br />
##[[DragScript Examples]]<br />
<br />
==Disclaimer==<br />
While the authors of this Wiki have worked hard to make the information useful, we cannot guarantee it is correct.<br />
<br />
This is a volunteer effort to help the community, and there are no warranties expressed or implied. <br />
<br />
<br />
'''USE AT YOUR OWN RISK!'''<br />
<br />
<br />
'''Please use care and caution and watch your equipment closely while running it with Voyager or any automation software, especially when trying something out for the first time.'''<br />
<br />
<br />
'''By using the information in this Wiki, you acknowledge that you are doing so at your own risk.''' <br />
<br />
<br />
'''The authors of this Wiki assume no liability for any loss or damage to your data or equipment resulting from your use of information in this Wiki.'''<br />
<br /><br />
[[Category:All]]<br />
[[Category:Manual|A1]]</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=Manual_Title_Page&diff=5631Manual Title Page2020-10-12T10:54:02Z<p>Rowland: /* Voyager */</p>
<hr />
<div><br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
=== '''Voyager''' ===<br />
Image Acquisition Software<br />
<br />
by Starkeeper.it<br />
<br />
<!-- PAGE BREAK --><br />
<br />
<br />
[[Category:Manual|AA]]<br />
[[Category:All]]</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=Manual_Title_Page&diff=5630Manual Title Page2020-10-12T10:53:23Z<p>Rowland: </p>
<hr />
<div><br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
=== '''Voyager''' ===<br />
Image Acquisition Software<br />
<br />
by Starkeeper.it<br />
<br />
<!-- PAGE BREAK --><br />
<br />
<br />
[[Category:Manual|aa]]<br />
[[Category:All]]</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=Manual_Title_Page&diff=5629Manual Title Page2020-10-12T10:52:25Z<p>Rowland: Create title page for manual</p>
<hr />
<div><br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
=== '''Voyager''' ===<br />
Image Acquisition Software<br />
<br />
by Starkeeper.it<br />
<br />
<!-- PAGE BREAK --></div>Rowlandhttps://wiki.starkeeper.it/index.php?title=Manual_Title_Page&diff=5628Manual Title Page2020-10-12T10:45:50Z<p>Rowland: Created page with " Voyager Image Acquisition Software by Starkeeper.it"</p>
<hr />
<div><br />
Voyager<br />
<br />
Image Acquisition Software<br />
by Starkeeper.it</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=Main_Page&diff=5627Main Page2020-10-12T09:45:53Z<p>Rowland: </p>
<hr />
<div>==Welcome==<br />
<br />
Welcome to the Official English language Wiki for the Voyager astrophotography automation software. <br />
<br />
Voyager is commercial software written and sold by Leonardo Orazi. The official website is [https://software.starkeeper.it Starkeeper.it].<br />
<br />
This Wiki's purpose is to provide an English documentation, and to allow other Voyager users to contribute to the English language documentation.<br />
<br />
Enjoy!<br />
<br />
<br /><br />
<br />
==Downloadable PDF Manual==<br />
A downloadable PDF version of the contents of this Wiki is available here: https://wiki.starkeeper.it/images/voyager.pdf<br />
<br /><br />
==Contents==<br />
<br />
#[[Introduction]]<br />
#[[Installation]]<br />
#[[Licensing]]<br />
#[[Main Window]]<br />
#[[Status Window]]<br />
#[[Command Window]]<br />
#[[Setup]]<br />
#[[Startup]]<br />
#[[OnTheFly]]<br />
##[[OnTheFly#Sequences|Sequences]]<br />
##[[OnTheFly#Auto Flats|Auto Flats]]<br />
##[[OnTheFly#Research Survey|Research Survey]]<br />
#DragScript<br />
##[[DragScript|Editor]]<br />
##[[DragScript Elements|Actions]]<br />
##[[DragScript Other Elements|Other Elements]]<br />
##[[DragScript#Variables and Control Flow|Variables and Control Flow]]<br />
##[[DragScript Examples|Examples]]<br />
#Tutorials<br />
##[[Quick Start]]<br />
##[[DragScript Examples]]<br />
<br />
==Disclaimer==<br />
While the authors of this Wiki have worked hard to make the information useful, we cannot guarantee it is correct.<br />
<br />
This is a volunteer effort to help the community, and there are no warranties expressed or implied. <br />
<br />
<br />
'''USE AT YOUR OWN RISK!'''<br />
<br />
<br />
'''Please use care and caution and watch your equipment closely while running it with Voyager or any automation software, especially when trying something out for the first time.'''<br />
<br />
<br />
'''By using the information in this Wiki, you acknowledge that you are doing so at your own risk.''' <br />
<br />
<br />
'''The authors of this Wiki assume no liability for any loss or damage to your data or equipment resulting from your use of information in this Wiki.'''<br />
<br /><br />
[[Category:All]]<br />
[[Category:Manual|A]]</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=MediaWiki:Mainpage&diff=5626MediaWiki:Mainpage2020-10-12T09:43:57Z<p>Rowland: Created page with "Main Page"</p>
<hr />
<div>Main Page</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=File:Onthefly-utilities-2.11h.jpg&diff=5625File:Onthefly-utilities-2.11h.jpg2020-10-11T18:40:26Z<p>Rowland: </p>
<hr />
<div>== Summary ==<br />
importing from old wiki</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=File:Dragscript-goto-zenity.png&diff=5624File:Dragscript-goto-zenity.png2020-10-11T18:40:26Z<p>Rowland: </p>
<hr />
<div>== Summary ==<br />
importing from old wiki</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=File:Filter-list.jpg&diff=5623File:Filter-list.jpg2020-10-11T18:40:26Z<p>Rowland: </p>
<hr />
<div>== Summary ==<br />
importing from old wiki</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=File:DSArrayDisconnect.png&diff=5622File:DSArrayDisconnect.png2020-10-11T18:40:26Z<p>Rowland: </p>
<hr />
<div>== Summary ==<br />
importing from old wiki</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=File:Vcurve-first-light.jpg&diff=5621File:Vcurve-first-light.jpg2020-10-11T18:40:26Z<p>Rowland: </p>
<hr />
<div>== Summary ==<br />
importing from old wiki</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=File:Test1.png&diff=5620File:Test1.png2020-10-11T18:40:26Z<p>Rowland: </p>
<hr />
<div>== Summary ==<br />
importing from old wiki</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=File:Dragscript-viking.png&diff=5619File:Dragscript-viking.png2020-10-11T18:40:26Z<p>Rowland: </p>
<hr />
<div>== Summary ==<br />
importing from old wiki</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=File:ASMonitorWIP.png&diff=5618File:ASMonitorWIP.png2020-10-11T18:40:25Z<p>Rowland: </p>
<hr />
<div>== Summary ==<br />
importing from old wiki</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=File:Dragscript-simulator1.png&diff=5617File:Dragscript-simulator1.png2020-10-11T18:40:25Z<p>Rowland: </p>
<hr />
<div>== Summary ==<br />
importing from old wiki</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=File:Asi-gain-sliders.jpg&diff=5616File:Asi-gain-sliders.jpg2020-10-11T18:40:25Z<p>Rowland: </p>
<hr />
<div>== Summary ==<br />
importing from old wiki</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=File:On-end-tab.png&diff=5615File:On-end-tab.png2020-10-11T18:40:25Z<p>Rowland: </p>
<hr />
<div>== Summary ==<br />
importing from old wiki</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=File:Voyager-shortcut-properties.jpg&diff=5614File:Voyager-shortcut-properties.jpg2020-10-11T18:40:25Z<p>Rowland: </p>
<hr />
<div>== Summary ==<br />
importing from old wiki</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=File:Viking-select-language.png&diff=5613File:Viking-select-language.png2020-10-11T18:40:25Z<p>Rowland: </p>
<hr />
<div>== Summary ==<br />
importing from old wiki</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=File:Sts-section-8.png&diff=5612File:Sts-section-8.png2020-10-11T18:40:25Z<p>Rowland: </p>
<hr />
<div>== Summary ==<br />
importing from old wiki</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=File:Research-plate-solving.png&diff=5611File:Research-plate-solving.png2020-10-11T18:40:24Z<p>Rowland: </p>
<hr />
<div>== Summary ==<br />
importing from old wiki</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=File:Research-sequence-elements.png&diff=5610File:Research-sequence-elements.png2020-10-11T18:40:24Z<p>Rowland: </p>
<hr />
<div>== Summary ==<br />
importing from old wiki</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=File:Mount-setup.jpg&diff=5609File:Mount-setup.jpg2020-10-11T18:40:24Z<p>Rowland: </p>
<hr />
<div>== Summary ==<br />
importing from old wiki</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=File:Status-window-obs-condx.png&diff=5608File:Status-window-obs-condx.png2020-10-11T18:40:24Z<p>Rowland: </p>
<hr />
<div>== Summary ==<br />
importing from old wiki</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=File:Menu-setup.jpg&diff=5607File:Menu-setup.jpg2020-10-11T18:40:24Z<p>Rowland: </p>
<hr />
<div>== Summary ==<br />
importing from old wiki</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=File:Flat-device-artesky.jpg&diff=5606File:Flat-device-artesky.jpg2020-10-11T18:40:24Z<p>Rowland: </p>
<hr />
<div>== Summary ==<br />
importing from old wiki</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=File:Dragscript-sendemail.png&diff=5605File:Dragscript-sendemail.png2020-10-11T18:40:24Z<p>Rowland: </p>
<hr />
<div>== Summary ==<br />
importing from old wiki</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=File:Dragscript-simulator4.png&diff=5604File:Dragscript-simulator4.png2020-10-11T18:40:24Z<p>Rowland: </p>
<hr />
<div>== Summary ==<br />
importing from old wiki</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=File:Dragscript-warmup.png&diff=5603File:Dragscript-warmup.png2020-10-11T18:40:23Z<p>Rowland: </p>
<hr />
<div>== Summary ==<br />
importing from old wiki</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=File:Run-dslr-setup.jpg&diff=5602File:Run-dslr-setup.jpg2020-10-11T18:40:23Z<p>Rowland: </p>
<hr />
<div>== Summary ==<br />
importing from old wiki</div>Rowlandhttps://wiki.starkeeper.it/index.php?title=File:Reset-scale.jpg&diff=5601File:Reset-scale.jpg2020-10-11T18:40:23Z<p>Rowland: </p>
<hr />
<div>== Summary ==<br />
importing from old wiki</div>Rowland