Autopilot updates:

Flight director can now be switched off (it however will be on if internal autopilot is engaged).
Flight director color is magenta if autopilot is not engaged, white if autopilot has control (internal autopilot).
Major work on autopilot system:
Easy setup for both bank and pitch. Only one setting affecting sensitivity with a three step selection of bank or pitch "force".
Bank servo magnitude setting scaled down to match settings of pitch servo magnitude. Expect a Bank servo magnitude setting of "10" if you where using a "30" previously.
Split autopilot inner loop into seperate algorithms for MGL and Trio servos to allow best possible match to either servo.
If using a Trio servo, expect Pitch servo magnitude settings in the region of "6" to "15" depending on pitch sensitivity of aircraft.
Automatic setting of servo deadband for Trio servos.
No more "running" of Trio servos when AP not engaged.
Addition of autopilot remote control via IOX (download version 2.0 of IOX script editor to add functions):
Remote engage of altitude hold, VSI hold and 180 degree turn modes as well as disengage.
Single button "engage/disengage".

Instructions for updating your Odyssey instrument:

Download the file "Odyssey.bin" which contains your Odyssey flightops operating system and Odyssey application program.
Copy this file onto a SD or MMC card (Root folder, not a "subdirectory"), insert into Odyssey and switch on. 
Odyssey will then reprogram itself if another version of software has been installed.
Please note: Depending on your currently installed version, the screen may go dark for between 30 seconds and 60 seconds as the backlight is switched off which is required for some updates. Do not remove power, wait until the update has completed. Your Odyssey will report itself for duty after the update has been completed. The Odyssey.bin file does not need to remain on the SD card. You can remove it once the update has been completed.

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 Odyssey.bin file as Odyssey.emb and copy to your SD card. In this case your SD card should also contain all data files (waypoints, 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 Odyssey.bin file as Odyssey.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 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 Compact Flash disk to your system).

If your system does not start due to a disk issue:
Rename your Odyssey.bin file to Odyssey.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 Odyssey.emb from your SD card and replace with Odyssey.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 Compact Flash 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 done this) or else you can use the file here which contains the factory setup we use to program your system for the first time (with the sound file removed): NoSound.esl

You now have a system that is equivalent to a new factory system.
Should you have changed your Compact Flash card, please be aware that some cards may not work correctly. There appears to be a lot of confusion amongst card manufacturers regarding many of the interface aspects resulting in some cards not being compatible with the TrueIDE mode we use. Most cards appear to work fine. You can currently use cards up to 4GByte in size, allthough you are unlikely to need a card larger than 1GByte. Cards must be able to operate in at least PIO Mode 4. The bootloader will check to see if your card can do this. If it cannot, the bootloader will abort with a "serious" error message. Cards that are confirmed to work with our systems are:

Lexar Premium 1GByte 80X
APacer Photo Steno III 150X
SanDisk Ultra II 1GByte
SanDisk Ultra II 2GByte

Please be aware of "pirate" copies of these cards, in particular SanDisk - they look nearly identical to the real thing. They may work but no guarantees. Use Google to find more information on pirate compact flash cards.

22 January 2008 New bootloader release 1.0.0.2

The new bootloader increases checks on FlightOps and Application code integrity and adds retry to disk system loading. If you get messages like "RAM corrupt" or similar after startup but a restart works fine, then please update your system to this bootloader.
This bootloader also extends support to SanDisk CF drives which take longer to start up.
Use Odyssey versions 0.1.0.6 or higher to program new bootloader.

Download new bootloader file here (Bootload.odb, about 40KBytes)

If your browser attempts to open the file or saves it with an extention other than ".odb", right-click on the above link, choose "save as". From the drop down list choose "Any files" or "All files" then edit the filename so it shows "Bootload.odb". This should now save the file to your disk correctly.

Instructions for programming new bootloader:

Download file Bootload.odb and place on SD card. Ensure that your Odyssey has been updated to at least version 0.1.0.6.
Insert SD card and switch Odyssey on. Go to Menu level 2, then System setup menu, then System Initialization then select "Replace bootloader".
You will be guided through a number of prompts and after some checks the new boot loader will be programmed and verified. This takes about 2 seconds. During this time your instruments power MUST NOT FAIL.
Updating the bootloader is a critical operation. If this fails you may be left with a non-functional boot loader. In this case your instrument needs to be sent to your MGL Avionics distributor if he has the ability to program a new bootloader (please check) or it needs to be returned to us to perform this operation.