Automatic or with Manual Download at this direct link [32 bit]:
https://www.starkeeper.it/voyager/Voyager_Setup_2.3.9.zip
Automatic or with Manual Download at this direct link [64 bit]:
https://www.starkeeper.it/voyager/Voyager_Setup_2.3.9_64bit.zip
Release 2.3.9 - Built 2023-07-15 - UPDATE INFO
| ⦁ | [New] New Release available of Voyager : the 64 bit version for camera with large sensors and large FIT, for better management and use of memory and for better performance and faster operations. You must have the 64-bit drivers of the hardware controls used in your setup. Installation is different from 32 bit , the 32 bit installer do not install or update Voyager 64 bit. Follow the instruction here for the 64 bit version installation and use Voyager 64bit - Voyager Wiki |
|---|---|
| ⦁ | [New] Donuts → Added the possibility to perform an Altazimuthal goto before proceeding with the calibration of Donuts (on sequence, in OnTheFly and on DragScript) |
| ⦁ | [New] PlateSolve3 → Added PlateSolve3 as new Plate and Blind Solving control. PlateSolve 3 was written by David Rowe and is provided free of charge as a courtesy of PlaneWave Instruments, Inc. You need to download the package with executable and catalogs and configure. Follow the dedicated instructions in the wiki. Use minimum version 3.82 of PlateSolve3 |
| ⦁ | [New] Pattern File → Added $$VOYPROFILE$$ for Voyager’s current profile name to the list of Possible Patterns |
| ⦁ | [New] RoboClip → It is now possible to import TheSkyX Observing Lists if exported in CSV mode with delimiter ; The imported fields (whatever position they are) are Object Name;Object Type;RA (2000.0);Dec (2000.0);Axis Position Angle . Object Type is used for the group if during the import the group is not redefined |
| ⦁ | [New] Sequence → It is now possible to request the pointing of the fire star in the Sequence with a simple Goto without using plate solving. useful if prime focus solving may fail to center star (out of focus from previous night or previous focus filters not parafocal) |
| ⦁ | [New] RoboOrbits → Created a new Voyager automaton for the management of the data of the Orbits of Asteroids and Comets and for their calculation |
| ⦁ | [New] RoboOrbits → Added in Setup, in the COMMON section, a box dedicated to the recovery of Comet data from the MinorPlanetCenter official website https://www.minorplanetcenter.net/iau/MPCORB/CometEls.txt. Import not compatible with other data format |
| ⦁ | [New] RoboOrbits → Comet data can be loaded both from the web by downloading the file and by importing an already downloaded file. The data is compared with those present in the RoboOrbits database and possibly added or updated |
| ⦁ | [New] RoboOrbits → Added in Setup, in the COMMON section, a box dedicated to recovering Asteriod data from the official site https://ftp.lowell.edu/pub/elgb/astorb.dat in the format foreseen for this file. Import not compatible with other data format |
| ⦁ | [New] RoboOrbits → Asteroid data can be loaded both from the web by downloading the file and by importing an already downloaded file. The data is compared with those present in the RoboOrbits database and possibly added or updated. This procedure can last from a few minutes to a few hours depending on the data already present in the archive and the download speed of your connection |
| ⦁ | [New] DragScript → Added new DOWNLOAD AND UPDATE COMETS DATA block which allows you to download Comets data from the Internet and update the RoboOrbits database |
| ⦁ | [New] DragScript → Added new DOWNLOAD AND UPDATE ASTEROIDS DATA block which allows you to download Comet data from the Internet and update the RoboOrbits database |
| ⦁ | [New] Rotator → Added work around for Rotators that have ASCOM drivers with movement flag activation delay. Such drivers can cause the rotator to return from the move operation prematurely by indicating no rotation in progress even though rotation was requested. In any case, contact the driver developer to report the problem and have the malfunction corrected |
| ⦁ | [New] Dome → Some ASCOM drivers do not correctly manage the AtHome property to verify the completion of the requested Home action. Added a work around in the Dome settings Do not use AtHome property for checking FindHome Action End box Options to recognize the end of Homing using the Slewing state. Use only in case of Homing problems with your driver |
| ⦁ | [New] Mount → Added the Elevation in meters to the mount location data override |
| ⦁ | [New] Mount → Introduced an automatic self-learning caching mechanism to have the mount location data even if the setup is disconnected (active override of the location in Voyager is required or at least an error-free first connection to the mount) |
| ⦁ | [New] Sequence → Introduced Target typology: Default, Comet, Asteroid. Default is the classic one used so far, for comets and asteroids the Sequence action will be able to recalculate the position in different ways with a setting that can always be configured in sequence |
| ⦁ | [New] DragScript → Sequence Block modified to also manage overridden Dynamic targets (Asteroids and Comets) |
| ⦁ | [New] DragScript → Added new GOTO DYNAMIC TARGET block to point asteroids and comets with their name without indicating the coordinates, the coordinates are calculated in real time when goto |
| ⦁ | [New] DragScript → Added new PRECISE POINTING DYNAMIC TARGET block to precisely point asteroids and comets with their name without indicating the coordinates, the coordinates are calculated in real time when goto |
| ⦁ | [New] DragScript → Added new WAIT ALTITUDE DYNAMIC TARGET block to wait for the set altitude of asteroids and comets with their name without indicating the coordinates, the coordinates are calculated in real time when checking |
| ⦁ | [New] DragScript → Added new DO IF ALTITUDE DYNAMIC TARGET conditional block to check the set altitude of asteroids and comets with their name without indicating the coordinates, the coordinates are calculated in real time when checking |
| ⦁ | [New] DragScript → Added new DO IF ALTITUDE BETWEEN DYNAMIC TARGET conditional block to check the set altitude of asteroids and comets with their name without indicating the coordinates, the coordinates are calculated in real time when checking |
| ⦁ | [New] DragScript → Added new DO IF AZIMUTH BETWEEN DYNAMIC TARGET conditional block to verify the set azimuth of asteroids and comets with their name without indicating the coordinates, the coordinates are calculated in real time when checking |
| ⦁ | [New] DragScript → Added new DO IF HA BETWEEN DYNAMIC TARGET conditional block to check the set HA of asteroids and comets with their name without indicating the coordinates, the coordinates are calculated in real time when checking |
| ⦁ | [New] Application Server → Added new RemoteRoboOrbitsGetAsteroids API for remote search of Asteroids in RoboOrbits |
| ⦁ | [New] Application Server → Added new API RemoteRoboOrbitsGetCometsLike for remote search of Comets in RoboOrbits |
| ⦁ | [New] Application Server → Added new RemoteRoboDataGetGeoDataCache API for retrieving Observatory/mount Location data from Voyager Geo cache remotely |
| ⦁ | [New] RoboTarget → Added the ability to execute Dynamic Targets (Comets and Asteroids) in RoboTarget with automatic calculation of coordinates in real time |
| ⦁ | [New] RoboTarget Manager → Added the ability to configure Dynamic Targets (Comets and Asteroids) |
| ⦁ | [New] Application Server → Added new RemoteMountStatusGetInfo API to obtain information on the status of the mount and the meridian flip |
| ⦁ | [New] Array → Added new action (usable also from the main Array management window) to fire RoboStar on a single star of all nodes without using the default filters and the Offset but directly the final filters. It is necessary to use homogeneous filters such as all narrow or all broadband otherwise the focus could fail |
| ⦁ | [New] Array → Added new action (also usable from the main Array management window) to perform the LocalField focus on the whole field of all the nodes without using the default filters and the Offset but directly the final filters |
| ⦁ | [New] Array → Added new sequence action without any use of offsets, sequence configuration has been changed to now have this option and decide which filters to use for focus. Obviously, if the focus on a single star is used, it is necessary to use homogeneous filters for all nodes in the entire sequence, such as all narrow or all broadband, otherwise the focus could fail |
| ⦁ | [New] Safety Monitor → Added new Safety Monitor URL Text control for reading the content of remote web pages in the same way as the Text File |
| ⦁ | [New] Sequence → Added possibility to reconnect Camera and FilterWheel if present following a CameraShot type error, you can also set how many times to restart before aborting the sequence. It is absolutely not certain that this procedure can be effective for all setups and for all types of errors. The solution is always to fix the camera or its configuration |
| ⦁ | [New] RoboStar → For compatibility with the 64-bit version of Voyager, RoboStar from this version uses an in-memory database and no longer an MS Access file |
| ⦁ | [New] RoboClip → For compatibility with the 64-bit version of Voyager the RoboClip from this version uses a SQLite database and no longer an MS Access file |
| ⦁ | [New] RoboClip → ABSOLUTELY IMPORTANT TO DO !! Added new function for importing data from the old RoboClip version on MS Access (up to Voyager 2.3.8f) to the new version of RoboClip, usable and functioning only on Voyager 32bit |
| ⦁ | [New] ATTENTION !! Updated ASI Camera V2 SDK to version 1.20.0.0 of 2023.04.18 , MANDATORY Install the latest ASI Camera drivers to support this SDK - Then check the Remove Overscan Area settings if used |
| ⦁ | [New] ATTENTION !! Updated QHY Beta Camera SDK to version 23.5.29.20 of 2023.05.09 , MANDATORY Install the latest QHY Camera drivers to support this SDK - Then check the Remove Overscan Area settings if used |
| ⦁ | [New] All Applications → Voyager’s Windows Application running in 64 bit mode show a blu icon on the command bart with a 64 bit logo |
| ⦁ | [New] Dome → Added new configuration flag in the general setup of Voyager to the Dome tab for the activation of the Slow Polling in the retrieval of the Dome states |
| ⦁ | [New] OpenSkyGems Plugin → Added flag to avoid uploading personal FIT files |
| ⦁ | [Mod] Advanced NDA → RoboTargetRunningTargetEphemerisPNG event modified to receive the ephemeris image, now it also contains the data useful for drawing references on the time axis |
| ⦁ | [Mod] Advanced NDA → RemoteRoboTargetAddTarget command modified to manage Dynamic Targets |
| ⦁ | [Mod] Advanced NDA → RemoteRoboTargetGetTarget command modified to also receive the specific data of the Dynamic Targets |
| ⦁ | [Mod] Array → Last used OnTheFly configurations of all command actions dedicated to Array are now stored in profile and not in volatile memory |
| ⦁ | [Mod] Camera → Added memory optimizations for very large sensors |
| ⦁ | [Mod] Array → Added support for $$ROBOFIREFOCUSERPOS$$ in pattern file management for Sequences in Array |
| ⦁ | [Mod] Platform SDK → The folder structure of the Platform SDK has been modified for compatibility with the 64-bit version of Voyager |
| ⦁ | [Mod] DragScript → Added possibility to select also coordinates from the manual mount in the management of the Emergency SUSPEND event |
| ⦁ | [Mod] TheSkyX and TheSky64 Dome → Optimizations for TheSkyX/64 versions not able to correctly handle the IsGotoComplete property on first connection |
| ⦁ | [Bug] Array → The Sequence was aborted in case of request not to use Plate Solving |
| ⦁ | [Bug] Array → The enable/disable command buttons of the Array Management Window were not always consistent with the current state of the Array |
| ⦁ | [Bug] Array → Some array action configuration windows did not correctly disable the settings and commands of unconfigured or disabled nodes |
| ⦁ | [Bug] Array → If the start of the sequence was requested with the mount in No Goto Zone for meridian cross the sequence waited for the exit from the no goto zone even if the requested object was not |
| ⦁ | [Bug] Array → in case of use of the virtual mount on an instance in a second PC a GeoData Cache absence error was generated which interrupted the Setup connection |
| ⦁ | [Bug] RoboData → Voyager instances from the second onwards used the RoboData database of the first instance |
For who already have the 64 bit Beta version its necessary to download and install the 2.3.9 64 bit from the new installer, download it. The auto update will not work for the Beta.
…