Odyssey/Voyager G2 software binary download page
G2 Beta page - if you would like to try a beta of the next release, follow this link
Current latest version release on this
page: (Uploaded 03 November 2011)
Update instructions on
the bottom of this page.
Current version numbers:
FlightOps system
G2 1.0.0.7
Odyssey application G2 A
1.0.3.1
Download update file
Odyssey2.bin (Approximately 1.5MBytes
size). For installation instructions see bottom of this page.
Download the
matching Odyssey2 simulator
(Approximately 1.5MByte size). Windows installation program.
Download the
current sound file for your EFIS here
(Sounds.esd) . Installation instructions at the bottom of this
page.
Details of current firmware upgrade:
Fixed: Related to recent changes of the CAN driver autopilot would
not engage if servos are powered up after EFIS is already running.
Fixed:
Typo in menus for servo tests.
Details of previous upgrade to version 1.0.3.0
Fixed: Issue related to autopilot disengaging after some time if multiple MGL servos are selected. This issue was introduced in version 1.0.2.9, related to new CAN bus interface programming for CAN bus support of AHRS and compass.
Details of previous upgrade to version 1.0.2.9
Added: User selection for TAS calculation: Use ambient temperature
or standard atmospheric model.
Added: First version to support new SP6/SP7
CAN communications. SP6/7 CAN units will be available in January.
Changed:
ETE will now show in minutes:seconds if less than one hour, otherwise
hours:minutes as before.
Fixed: Several minor issues related to Interactive
flightplan tool.
Fixed: Vertical fonts, normal and transparent modes:
Characters wider than 8 pixels where not drawn correctly.
Fixed: Simulator:
Vertical edged fonts where not drawn vertical.
Improved: USB Master/Slave
error recovery in case of communications interference.
Removed: HITS box size
selection in 3D setup menu. Now fixed size: 2000 ft.
Several other minor
fixes and improvements.
Details of previous upgrade to version 1.0.2.8
Added new setup item in "Operations setup" to select NTSC video sources. Currently, if a NTSC camera is connected, the bottom few lines of the image shows a repeat of the top. This is caused by the lower number of lines of the NTSC signal when compared with PAL. The new setup uses advanced vertical line interpolation scaling to stretch the image to fit without causing any noticable image artifacts. Please note that when you connect video sources, all sources must be either PAL or NTSC, you cannot mix.
Impoved: The raster map TAWS overlay could result in some ant-aliased lines being drawn "funny" depending on their position in the drawing order. This is caused by a bug in the graphics chip. This has been fixed by using a work-around.
Details of previous upgrade to version 1.0.2.7
Added: TAWS overlay on raster maps (if enabled in setup).
Previously this was only available on vector maps.
Added: G-Force setup menu
under Instruments setup. This allows setup of display limits, warning limits etc
similar to other indicators. Negative G-Forces can be displayed with SP-7
(Previous SP products give absolute, total G-Force regardless of
direction).
Added: New support for rounded rectangles (frame, filled and
frame filled types). This is a new selection in the DrawPrimitives screen
item.
Added: New AOA display component using "feather" display.
Added:
Dotted track line on raster maps.
Changed: TAWS tarrain warning on map flashing has been replaced with a steady color display if vector maps are used (using terrain data to make the terrain backdrop). In case of Raster maps the terrain will flash slowly so to allow the underlying map information not to be lost.
Improved: Rendering quality of "analog arc" screen component using subpixel rendering.
Fixed: Plates component could have problems displaying a plate due
to a racing condition between GPU and processor. This could lead to the plate
flashing briefly before being erased This affected only the plates screen
component. The plates viewer in the menu was fine.
Fixed: Previous releases
suffered from an ARINC label corruption problem. While this has impoved due to
additional measures in previous releases this could still occur on some systems.
The root cause of this has now finally been discovered and fixed in the slave
processor responsible for ARINC label processing.
Fixed: VPX Pro/Sport have
slightly different communications protocol to upgraded VPX-75 used for testing
here. This resulted in Pro and Sport units not operating
correctly.
Details of previous upgrade to version 1.0.2.6
This is the first release to officially support Navidata created
by Jeppesen JSUM download (Navidata file is created by Jeppesen based on
subscription).
Fixed: SD cards formated with FAT32 could not be used in the
system. This has now been fixed. It is however recommended that FAT (or FAT16)
be used for SD cards that are used for flight data recording as this allows
slightly faster disk operation.
Amended: VPX interface mainly with respect to
flap and trim functionality, also changed ECB current component to start at "1"
rather than "0", similar to other ECB components. Please amend your screen
designs accordingly if required.
Improved: Autopilot pitch control in
conditions where internal GPS cannot be used and static pressure is used as
backup. Also, if external GPS feed is used (such as from G430 or NMEA), internal
GPS will still be used for autopilot vertical guidance whenever
possible.
Added support for SL40 radio as VHF 2
Added secondary algorithm
to assist AP to track altitude to tighter limits in calm conditions
Added
black box flight data recorder feed (messages 1,2 and 3 supported at this
stage)
Details of previous upgrade to version 1.0.2.5
Fixed bug related to airspaces containing large number of polygon points. This can lead to a serious system lockup. This has been introduced in version 1.0.2.4 due to some changes around airspace data processing. If you have upgraded to 1.0.2.4 please change to 1.0.2.5 even if your system does not appear to be affected.
Added support for up to 8000 active airspaces within a 10x10
degree area around aircraft position (increased from 2000).
Added support for
airspaces with a large number of polygon points (previous limit was 400, now
800).
Added support for V0 and V1 V speeds for airspeed tape as well as analog airspead indicator display.
Details of previous upgrade to version 1.0.2.4
Added first release of autopilot yaw axis support using a
third servo (MGL servo only).
Updated some autopilot related interfaces to
reflect failed servos etc before engage attempt.
New HSI routines and much
improved autopilot coupling allows for smooth changes between navigation sources
without autopilot disconnect.
Complete rewrite of communications interface between ARINC
processor and main processor to elliminate any chance of corrupted ARINC labels
from making it through. Relevant mostly for G430 based
installations.
Complete overhaul of internal SPI based communications links
between various processors in order to increase performance and high level of
data rate handling mainly in support of new CAN interface based pheriperals.
Further improvements of system startup time. Typical system startup from power on now down to about 5 seconds to live display
Changes to ARINC based autopilot interface (for external autopilot
based on GPSS feed. Changed from relative to absolute steering.
Please see this document for details on operation and
setup.
Please note: The changes to the ARINC AP interface are still
experimental. Feedback is appreciated.
Added further options to synthetic
vision based heading indications. Now true or magnetic headings, major cardinal
headings (NSEW) or numeric tapes, also options on font size. Select in 3D View
setup.
Fixed a minor issue on the NMEA RMC output sentence: The ground speed was inserted incorrectly (it is good in the RMB message).
Added support for Ground proximity warning and flap position over
speed warning. See this document
for details.
New sound files to support ground proximity and flap
overspeed warnings to be found here.
Ability to import a setupody.dat file into a real EFIS (Note
the file must have been exported by a system that has the same software version
number).
Moved sound file install into "Installation tasks" menu.
System
is now able to support "Whole World" single Navidata file (as available soon
through Jeppesen subscription).
Minor work on XRX interface to improve
resynchronizing communications (The XRX protocol has no means of synchonizing a
message start making this a little tricky).
ILS from SL30 was showing wrong
direction. Fixed.
Simulator: Added ability to use any folder or disk as "SD
card". The target "SD card" is selected under the "Project" menu. This now
permits use of a real SD card similar to a real EFIS if so desired.
Added Radio stack component and default radio stacks to all built
in screen. New Radio stack setup menu (enable radio stack items).
Support for
V10 radio with full remote control of radio. Note: Please set radio to Flip-Flop
frequency selection and "Main+Standby" mode in the radio's setup using the
radios own setup menu. The V10 radio needs to be updated to version 170111.
Earlier versions of the firmware will not work. Follow this
link for the V10 update software.
Please note: Slave systems cannot
currently set frequency of radio connected to primary system. In case of a V10,
the idea is to wire each EFIS to the radio (serial ports 1 and 2) so you have a
fully redundant system.
Some changes to SL30/SL40 interface - EFIS now
shows frequency selected on these radios (RX and TX need to be
connected).
Many internal changes to navigation source selection mechanisms
partly prompted by radio stack functionality.
Improvements to COM Extender
initialization (COM extender might not initialize if plugged in after EFIS
startup or EFIS startup takes longer than usual).
Minor internal changes to
autopilot engage.
Preliminary documentation for radio stack (Text file): Follow this
link.
Alternate installations:
a) SD card system
If you are using a SD card based system and are not
using the internal solid state disk, rename the Odyssey2.bin file as
Odyssey2.emb and copy to your SD card. In this case your SD card should also
contain all data files (navidata, screen files (if you use custom screen files),
maps etc - do not use folders).
b) SD card boot
If you are operating a system where you boot from SD card
but are using data files installed on the internal solid state disk, rename the
Odyssey2.bin file as Odyssey2.exb and copy to your SD card. On startup, Odyssey
will load the file from SD card and ignore any installed Odyssey.bin file on the
internal solid state disk.
Instructions for uploading a new sound
file:
Download the file "Sounds.esd" which contains the voice/sounds
as used with the current software versions.
Copy this file onto a SD card (Root folder, not a
"subdirectory"), insert into Odyssey or Voyager and switch on.
Go
to menu level 2, then select "system setup". Once in system setup, press the
down arrow until you get to select "system initialization". Now select
"Load sound file from SD/MMC card".
The programming will take around a
minute depending on the size of your sound file. After this is finished you can
remove the "Sounds.esd" file from your SD card.
Instructions for rebuilding your solid state disk from scratch
Should you want to rebuild your internal solid state disk from scratch (perhaps your disk is corrupted or you just want to start fresh or you fitted a new SDHC Flash disk to your system).
If your system does not start due to a disk issue:
Rename your
Odyssey2.bin file to Odyssey2.emb and place on the SD card. Your system should
now boot from the SD card giving you access to the menus.
Go to Menu level 2, then "down arrow" to get to the second page. Select "File
manager". Now select "Format internal Solid state disk". Confirm the warning
prompts.
Remove power.
Remove Odyssey2.emb from your SD card and replace
with Odyssey2.bin. Insert and start up. The system will now be transfered to the
internal disk.
If you have inserted a brand new disk or have formatted your
SDHC in other system (such as Windows), FlightOps will reformat it and ask
you to restart. After this the system is copied again (since the format erased
it). Now you should have a working but completely blank system.
Execute your script library file containing your personalized system (if you have such a file).
You now have a system that is equivalent to a new factory system.
Should
you have changed your internal SDHC Flash card, please be aware that
some cards may not work correctly. The speed class of the card is of no concern
as this applies to writing the card only. We recommend 4GByte SDHC cards from
reputable sources be used. Be aware of pirate parts that may contain a well
known manufacturers brand name but are of dubious origin.