From Voyager Unofficial Wiki
Jump to: navigation, search

Post your questions in the Voyager Forum at https://forum.starkeeper.it We monitor that forum and will add the answers here if appropriate.


  • LocalField autofocus fails with an out-of-memory error
    • 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:
      • If your camera does not have filters, use the Focus Bin setting - it's in Setup -> AutoFocus -> Robofire Configuration -> LocalField Mode:
      • Localfield-focus-bin.jpg
      • 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:
      • Localfield-per-filter-bin.png


  • Can I use my own filenames for images taken with Voyager?
    • 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 usedSequence-elements.png
    • Other: With the Camera -> Expose action in a DragScript, you can specify the filename however you like
  • What do the fields mean in the default image filenames saved by Sequences?


  1. Target name
  2. Type of exposure: Light, Dark, or Bias
  3. Suffix: whatever you type in the "Suffix" field. Filter names are used here.
  4. Exposure length
  5. Binning level
  6. Sensor temperature
  7. Sequence number: a sequential number generated automatically when Voyager takes a new image
  8. Date: YYYYMMDD
  9. Time: HHMMSS
  10. MS: millisecond portion of the time the image was taken
  11. Position Angle
  12. Position relative to Meridian: E = East or W = West
  13. File type: FIT for a FITS file


  • Why did Voyager put "NoCooling" in the file name saved by my Sequence?
  • 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.


  • 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?
    • These errors have been seen when using the ASCOM driver as standard. Try the ASCOM Dome ConnectionLess Interface, which seems to eliminate these errors
  • Voyager started taking images before the dome had finished rotating
    • Voyager will slave to the dome when starting a sequence only if you check the box Slave on Sequence Start in Setup -> Dome:
    • Dome-slave-on-seq-start.jpg
    • 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
    • This is because some drivers don't report slave status to Voyager
    • 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.
    • Also remember to slave off and park the dome at the end of the script
  • I use VIking to control my Dome (or Roll-Off Roof). How do I connect it to Voyager's Dome controls?
    • 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.
    • This video explains how to do this: https://vimeo.com/331171731

Editing a DragScript

  • I can't get Drag and Drop to work in the DragScript Editor (perhaps with a remote desktop connection such as VNC, TeamViewer, etc)
    • 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.
    • 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:
      • Right click the Windows button on the remote PC's desktop (not on your local PC)
      • Click Settings
      • Type "Mouse Keys" in the search box and select "Turn Mouse Keys On or Off"
      • Turn Mouse Keys on


  • How can I take flats without the variable exposure feature of Auto Flats?
    • 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.
  • My Auto Flats never finish, they keep looping trying to find the proper exposure time but it is always outside the allowed error tolerance
    • 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.


  • Do I need to install Voyager to get a serial number before buying a license?
    • 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


    • Copy the serial number from the License window and enter it in the Serial Number field of the license purchase form

Plate Solving

  • What happens during a sequence if, after autofocus, plate solving on return to target fails, e.g. due to clouds?
    • 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.
    • 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)
    • 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.
    • 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.
    • Autofocus will be tried again when scheduled, and also plate solving will be tried three times to goto the focus star.
    • 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.
    • Voyager's goal is to not stop any time - just not use guiding if it is not available due to clouds.
    • If you have a cloud sensor, you can manage the actions taken on cloudiness using DragScript Emergency Suspend, Resume and Exit events


  • What is the relationship between the Target Coordinates in the OnTheFly workspace and the Sequence defined on that page?
    • 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.


Slewing and Meridian Flips

  • 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)
  • 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 that section of the Wiki for more information

if the mount stop means have passed meridian and Voyager is connected but not used (meridian passed for the data received from the mount and meridian managing mode setting in Voyager).  Voyager doesn't intercept external goto and if pass the meridian during slew stop tracking because Voyager is in IDLE. Remove the flag if he want to manage slew from external.