Release Note | Voyager 2.7
Firmware Voyager 2.7
A new firmware package is available in October 2024. In this version, Voyager introduces user logging action and a faster starting/restarting time.
Run the downloaded file and follow the instructions to update your Voyager. If you have any problems, please do not hesitate to contact us or your local distributor, and we will guide you through the updating process.
What’s NEW
- The booting time for both starting and restarting the device is enhanced. The total time decreased from 1m 40s to 42s.
- Application logging functionality is introduced. Main actions during the operational state of the Voyager are logged to a *.txt file named “VoyagerLogFile-YYYY-MM-DD - HH-MM-SS-LogID”. In which YYYY-MM-DD - HH-MM-SS-LogID are respectively year, month, day, hour, minute, second and log identification number of every section.*
- Overwriting of Microflown probe calibration coefficient from already recorded *.h5 files is available in the File Manager page. **
Bug Fixes
- Snapshot functionality did not properly display the spectrum curve when the linear axis was selected. This is fixed;
- When going to Sound Quality main tab the weighting was automatically switched to dBA and returned to the main selected by the user. This is fixed.
Coming soon
- The Signal Generator feature will also be compatible with VELO.
Note(s)
- *Voyager will create one file for every session initiated, which means that starting or restarting the Voyager creates automatically a new log file inside the folder /Voyager/Logs/Application.
- *Voyager always writes to the most recent log file. Changing the name of the file will make the logging functionality not work properly.
- *The date and time used in the logging are the same ones set in the Voyager General Settings page.
- **The currently loaded calibration coefficients will be the coefficients overwriting the *.h5 file data. This feature is only possible when the coefficients from the *.h5 file and the current setup have the same amount of channel numbers, i.e., it is not possible to load a UPS type into a file that has been recorded with a PU configuration. This overwriting info is also logged in the log file.
Related products
Voyager
PU Voyager