Difference between revisions of "Installation"
| (One intermediate revision by the same user not shown) | |||
| Line 251: | Line 251: | ||
| − | + | [[File:Immagineeberberb.png]] | |
| − | |||
| − | |||
| + | {{note|You can add folder inside for beta SDK version where to copy your file but attention, each voyager installation (also daily build) will overwrite the folders structures and file internally needed (your structures will remain untouched). For example if you change SDK from QHY in platform\qhy\64 each file with same name will replaced with original by Voyager installation !!}} | ||
| + | {{note|For ZWO ASI : ASI Camera V2 SDK DLL is just under ASI folder (64) , the ASI Camer SDL DLL is under V1 folder (64)}}{{note|For QHY Beta Driver : Voyager since release 2.3.0 have a control camera dedicated to Beta driver version. If you want to manually update or change this driver use the folder paltform\QHY\BETA\64}} | ||
==Installing Previous Versions== | ==Installing Previous Versions== | ||
Latest revision as of 11:50, 15 July 2023
Voyager is a shareware program. The demo version is free to use. The author assumes no liability resulting from improper use or bugs in the program. As an integrator of third-party applications, VOYAGER cannot know for sure the behavior of other software. Any damage arising from the use of VOYAGER is not covered by any insurance.
USE AT YOUR OWN RISK!
The latest version of the application can be downloaded here: https://software.starkeeper.it/#download_voyager_section
Prerequisites
VOYAGER runs on Microsoft Windows operating systems, both 32 and 64 bit. Basic requirements are:
- Operating Systems 32 / 64bit Windows XP with Service Pack 3, Windows Vista, Windows 7, Windows 8 and 8.1,
Windows 10, Windows 11
- Microsoft Dot Net 4.0
- ASCOM platform from version 6.5 SP1 and newest https://ascom-standards.orgImportant Note! If you are using a version 6.5 of ASCOM Platform please be sure to use at least the SP1 to avoid problem on target pointing. This is a declared ASCOM bugs solved in 6.5 SP1 !
- minimum 1024x600 screen
VOYAGER has also been tested on Mac using PARALLELS virtual environment.
Third Party Applications and Versions Supported by Voyager
Applications, with minimum versions, that can be managed by VOYAGER:
- CAMERA CCD / CMOS / DSLR
- connected via ASCOM Platform 6.x https://ascom-standards.org All cameras have ASCOM Driver
- or Maxim DL CCD version 5.x or later(All cameras supported from Maxim DL)
- or TheSkyX using Camera Add On (All cameras supported from the TheSkyX Camera Add On)
- or ASI Camera (ZWO ASI native driver direct to camera with SDK)
- or QHY Camera (QHY Native driver direct to camera with SDK)
- or FLI Camera (FLI Native driver direct to camera with LibFli.dll)
- or QSI CCD (QSI COM component released by QSI to install)
- MOUNT / TELESCOPE
- connected via ASCOM Platform 6.5 SP1 https://ascom-standards.org
- or TheSky6 Professional Edition 6.0.0.24 and later
- or TheSkyX Professional Edition 10.1.11 and later
- Array Virtual Mount (Advanced version of Voyager)
- GUIDING
- PHD2 version 2.3.0 and later
- or MaximDL 5.x and later
- or TheSkyX
- PLANETARIUM
- Cartes du Ciel
- TheSkyX
- TheSky6
- Hallo Northern Sky
- Stellarium (officially tested from version 0.21.0 using remote interface)
- PLATE SOLVING / BLIND SOLVING
- PinPoint LE version 5.x
- or PinPoint FULL version 5.x and later
- or TheSkyX ImageLink
- or PlateSolve2
- or nova.astrometry.net
- or All Sky Plate Solver
- or ASTAP
- FOCUSER
- connected via ASCOM Platform 6.5 SP1 https://ascom-standards.org
- or FocusMax 3.4.40 and later
- or MaximDL 5.x and later
- or TheSkyX @focus2 and @focus3
- FLAT DEVICE
- Gemini SnapCap
- Alnitak Flat-Fielding Device
- Tecnosky TecnoCap and MultiLevel
- Arduino Flat Device
- Artesky Flat Device
- Sky Flats
- ASCOM Cover Calibrator Device
- Geoptik Flat Device
- PegasusAstro Flat device
- All ASCOM CoverCalibrator compatible
- ROTATOR
- connected via ASCOM Platform 6.5 SP1 https://ascom-standards.org
- RCOS TCC Rotator
- DOME
- connected via ASCOM Platform 6.5 SP1 https://ascom-standards.org
- ScopeDome LS with ScopeSync
- NexDome
- WEATHER
- AAG Cloudwatcher / Solo
- Boltwood / Clarity II / SkyAlert Weather Station or compatible
- OBSERVING CONDITIONS
- connected via ASCOM Platform 6.5 SP1 https://ascom-standards.org
- using Viking Client
- SKY QUALITY MONITOR (SQM)
- connected via ASCOM Platform 6.5 SP1 https://ascom-standards.org
- SAFETY MONITOR (SQM)
- connected via ASCOM Platform 6.x5 SP1 https://ascom-standards.org
- Textfile Safety Monitor
- I/O CARDS
- Viking and all supported Cards
The availability of executable actions within Voyager depends on the number and capability of connected applications.
Installation Video
There is a video on how to install Voyager on the Voyager Astro Imaging YouTube channel:
Installation Procedure
After downloading the installation file:
1. Start by double clicking on the downloaded file:
2. Voyager is a signed application as of Voyager 2.2.1. It is signed by "Starkeeper di Orazi Leonardo."
5. Choose your installation language, English or Italiano, and click OK
6. Read the license agreement, click the I accept the agreement radio button, and click the Next button to continue installing Voyager:
7. Optionally, check the "Create a desktop shortcut" box and click Next to continue installing Voyager:
8. Finally, click the Install button to do the installation:
9. You will see a dialog box with a progress bar while files are extracted and installed. Click Finish to complete the installation:
1
Congratulations, you have installed Voyager!
Voyager Folders
When you first run VOYAGER, it will create a series of folders in your Windows user's Documents directory:
- Advanced
Reserved to Voyager Full/Advanced version
- ConfigSequence
Configuration files of the automated imaging sequences or automatic flat taking sequences
- Data
Database files for various pourpouse
- Data Backup
Database backup (backup of folder Data with age system like for Profile Backup
- FIT
FITS files (image files with metadata) created by VOYAGER actions for plate solving and test shots. These files are erased at each start of Voyager.
- GuideFIT
FITS files created by guiding actions. These are the screenshot and the jpg or fit file related to a find star problem. These files can be delete whenever you choose. However, if you need help with guiding, you will need to provide one or more files from this folder to assist in troubleshooting, so you may want to keep the last session's files at least.
- Log
Text files with the log of operations performed by Voyager. The level of information is very high. These files will be required in case of bugs to fix or anomalies to interpret.
- Orbits
Database with data related to RoboOrbits Automata
- Profile
Settings files for the various imaging system configurations you define
- ProfileBackup
AutoSaving of Profile folder with datetime naming at each start of Voyager and before an online update of Release from Voyager. You can define age of backup to retain on this folder using the Setting of VOyager, tab Voyager, Box Profile Backup
- Renting
Ticket file system access reserved to Voyager Renting Plugin
- ScreenShot
Screenshots of the program in case of watchdog events such as guiding or other failures
- Script
DragScript files used to automate imaging sessions
- Sequence
Default folder containing the FITS files generated by running sequences, the files are sorted to subfolders that are created with the name of the target. You can override this and send FITS files to a directory of your choice in the Setup section.
Log File
The Log folder contains the files Voyager creates as it executes tasks. There will be a file for each day of use, and each file will contain at most the logs from 24 hours of operation. Information in the log file is intended to help the developer trace the cause of a problem in the event of application failure or malfunction.
The developer may ask you to attach a zip file with the relevant portion of the log to help track down a problem. You can use a text editor, such as Notepad or the free third party editor Notepad++ to find the time of the problem, and then trim the log file down to the relevant lines. If there are more than a few lines of interest, save the relevant lines to a new text file and then compress them into a .zip file to attach to your email requesting help.
You may be asked to email the relevant portion of the log file with a text editor, and attach a zip file in your email They will be required as necessary to send an email. In that case it will be necessary to decrease the size of the zip file and select only the necessary period. The log file entries are timestamped, so just select the entries around the time of the problem.
SDK Platform Folder for Voyager 32 bit
ONLY FOR 32 BIT VERSION OF VOYAGER !
The SDK platform folder contains all the SDK/DLL Library used by Voyager for external Camera/Driver. It is organized by Vendor and internally by architecture bits.
This folder is not located in document folder but in Voyager installation folder, usually C:\Program Files (x86)\Voyager
SDK Platform Folder for Voyager 64 bit
ONLY FOR 64BIT VERSION OF VOYAGER !
The SDK platform folder contains all the SDK/DLL Library used by Voyager for external Camera/Driver. It is organized by Vendor and internally by architecture bits.
This folder is not located in document folder but in Voyager installation folder, usually C:\Program Files\Voyager
Installing Previous Versions
Retrieve the old version setup from the Releases Category in Voyager's forum and execute the installer.
If you can't find the version you are looking for please contact support.
Installing Daily Build Versions
The daily Builds are development versions of Voyager based on the current official release version. They contain new features or existing bug fixes.
They can be downloaded directly from the Voyager forum here. They are declared unstable as they have not been tested and their installation is on a voluntary basis.
To go back from the Daily Build versions you need to reinstall the original release version.