Remzibi's OSD Configuration Tool v2
User Manual and Frequently Asked Questions
HappyKillmore - 2/24/2009



NOTE to NTSC Users: When you first plug in your OSD it will be in PAL mode by default!
To change to NTSC mode, hold down the button for ONE second (with a battery plugged in to the Vvid port) and release.
This will switch modes and will stop the display from blinking.

Remzibi's OSD Configuration Tool (Windows PC software) can be downloaded here: Setup.exe



Basic Questions

What is Remzibi's OSD?
What do I get with Remzibi's OSD?
Where can I get one?
What are the features of this OSD?
Who uses Remzibi's OSD?

Getting Started

Wiring up Remzibi's OSD board
USB Serial Software
Determining your COM port
Installing Remzibi's OSD Configuration Tool PC Software
Starting the software for the first time

New BIN File Defaults

BIN Files/Font Files and HEX Files
Preferences
Options
Video Modes

GPS Setup

NMEA Sentences
Hertz
Other Commands
Specific PMTK commands
GPS Datum

Main Screen

Configuring your OSD's Layout
Available Displays
Parameters

Font Editor

Editing Font Files
Show Dual Characters
Save Character / Save Font Set
Basic Tools

Hex Editor

Manual Tweaking of BIN Files

Updating Firmware

Updating the OSD's Operating System
Using the MegaLOAD software

Serial Communications

Serial Communications Overview
Upload Program & Font
ADC Configuration (Basic)
ADC Configuration (Advanced)

GPS Emulator

Flying your imaginary plane
Sample Output from GPS Emulator
GPS Fix Values

Language Editor

Creating a new language file
Editing Author's Information
Sharing your new language file
Key Code assignment
Auto-Update Remzibi OSD option
Finding other language files

FAQ

What number should I use for Satellites for Auto Home?
Why does it take so long to acquire satellites?
How can I change the default BIN file when I click File, New BIN File?
Why can't I get the BIN file to upload?
Why do I need to run an ADC calibration?
How do I get into the programming mode of the OSD?
I lost my plane, how can I use the GPS coordinates to find it?
What is a GPS Datum?
Is there anything better than ULEAD VideoStudio to use for video out testing?
How does the automatic update work and how can I turn it off?
Who the heck are you HappyKillmore and how are you involved with this project?

Troubleshooting

OSD with GPS connected



Basic QuestionsBack to Table of Contents
Q: What is Remzibi's OSD?
A: Remzibi's OSD is an On-Screen-Display unit that is used along with a video transmitter and video receiver on First-Person-View setups for Remote Control planes.

First-Person-View gives you a view from inside the cockpit of the R/C plane. If you connect video goggles or a monitor/TV to the output of the Video Receiver, you can actually see as if you were sitting inside the plane.

Here's where Remzibi's OSD comes into play. The OSD is connected between the video camera and the video transmitter and adds information using a video overlay processor on to the video image. It's somewhat similar to watching CNN where they have the text scrolling along the bottom of the screen... or any network show you watch will frequently have their station logo at the bottom right. This is an overlay. It's adding information to the picture displayed by the camera.

Remzibi's OSD board uses a GPS module to capture information like heading, speed, altitude and lat/long coordinates. In addition, it uses an ATMEL processor to capture information like battery voltage (video and main/motor) and other functions like Variometer which shows up and down changes in altitude. All of this information is updated in real-time and placed over the camera's picture and fed into the Video Transmitter, sent back to the ground where it is captured by the Video Receiver and then output to goggles or a monitor where you (the R/C pilot) sees the camera video with the overlayed data.

To read about the development of the OSD, check this thread on RCGroups

Here's a pretty cool sample video of the OSD in use:




Q: What do I get with Remzibi's OSD?
A: You can order items individually by contacting Remzibi, but typically, you'll receive the OSD PCB Board, GPS Module and USB to Serial Cable to program and update your OSD. These components give the ability to show Battery Voltage, Speed, Altitude, Direction Home and many other advanced displays.



Q: Where can I get one?
A: Contact Remzibi on RCGroups.com




Q: What are the features of this OSD?
A: Technical Data:
- Supply power requirement: 7V-14V (ie: 2S or 3S Lipo)
- Video voltage measurment range 0-15V
- Engine(ENG) voltage measurment range 0-30V
- General purpose ADC measurment - Build your own or use off the shelf components for many advanced readings - ie. Temperature, Amps, Air Speed, Prop Speed, RSSI, etc.
- Video signals - standard PAL or NTSC
- GPS - any GPS 5V supply with NMEA protocol with TLL standard TX RX signals (however best results and advantages are with dedicated GPS module working 5Hz update position)
- Weight : 16 gram (OSD + dedicated GPS)
- Printed OSD board size 20mmx45mm (0.78"x1.77")

Functionality:
- PC connection for configuration/calibration purposes using dedicated PC program
- No need for a free channel on your receiver for OSD to function
- GPS detection and configuration automaticaly
- Home autosave function configurable based on number of satelites - button "save home" works independently
- Metric(km/h) or feet(MPH) units - configurable
- Zero altitude to airfield level - configurable
- Fully configurable screen layout (no more cropped off data around the screen border like some other OSD's)
- Graphical symbols and fonts configurable (Font editor for creating your own symbols and characters)
- Voltages calibration function and all ADC inputs including alarms
- Frequency calibration for Hz or RPM (gain definable)
- PC configuration software includes GPS emulator for testing and setup purposes.
- Language Editor - Currently available in English, Polish and French. Simple to use langauge editor can be used to translate to any other language.

Button function:
- Save home position (short click)
- Video mode change (NTSC or PAL) press and hold button for about 1 second
- Programming mode (pressed when conecting to power) for PC communication

Information currently available on the OSD (additional hardware may be required):
- Latitude (format DDMM.MMMM or DD.DDDDDD can be choosen)
- Longitude (format DDMM.MMMM or DD.DDDDDD can be choosen)
- Speed (k/m or miles/h can be choosen)
- Altitude (meters or feet)
- Direction home arrow (animated arrow or user definable)
- Distance home (meters or feet)
- Satelite quantity (GPS signal quality)
- Heading (0º to 359º)
- Video battery voltage (individually scaled and calibrated)
- Main (Engine) battery voltage (individually scaled and calibrated)
- Virtual ADC which keeps a running total for use with battery MAH consumption
- Flight timer
- Variometer (meters/s or feet/s)
- UTC Time - UTC Date - Alarms for distance, ADC, atitude, battery voltages (individually scaled and calibrated)
- 32 static displayed independent graphical-character symbols, configurable
- Summary screen - after detection 0 speed for configurable X seconds, shows max values for altitude, distance, speed (function can be disabled)
- 6 ADC channels to use with any additional sensors, each can be individually calibrated and have an alarm set, cooperates with any additional sensors (optionaly scaled by opamp or resistor dividers) with analog output (RSSI, air pressure, current sensor, temperature or anything else with an analog output) - display format as 123 or 123.4 can be chosen
- Frequency meter (RCl input resistor need 220-515ohm or T0 in new board) - can be scaled for any units by gain as Hz or RPM, cooperate with magnetic(halotron) or optical sensor - or can be used as frames counter when connected to RX output directly

All displayed information can be placed anywhere on the screen, can be visible or invisible. Each object can have a definiable leading character(picture) and ending character(picture).
All configuration is done by the PC configuration program written by HappyKillmore.




Q: Who uses Remzibi's OSD?
A: People from all over the globe are using Remzibi's OSD. Take a look at the list of countries!



Getting StartedBack to Table of Contents
Wiring up Remzibi's OSD board

Photo of v.1 style board


Two battery (v.1 style board - 2 video grounds)


Photo of v1.1 style board


Two battery (v1.1 style board - 1 video ground)

To get your OSD board up and running, you will need the following:
1) R/C Plane well suited for FPV (ie Brushless EasyStar).
2) Video Transmitter and Receiver (ie 900Mhz 500mw system).
3) Video camera (ie KX-131, KX-171 or KX-191).
4) Video goggles or DVR for viewing/recording (ie FatShark or R-Vision Goggles).
5) Remzibi's OSD!!!

The OSD board is placed between the video camera and the video transmitter on the R/C plane. There are typically 3 wires that connect these two components. A red wire (power either 5V or 12V), a black wire which is ground and a white wire which is the video signal. You will need to make a custom cable to go from the video camera to the OSD and out of the OSD into the Video transmitter (VTx).

I have found the best solution is to use three servo extensions (labeled wrong here, should show it's female because it's the metal, not the platic that determines male or female). Take two of the extensions (we'll call them Camera and VTx) and solder and tape their red wires together. This will be the pass through for the 5V or 12V to power the camera. Next take the black wires on VTx and camera and and solder and tape them together with the red wire on the OSD extension. This will be the ground for the OSD, VTx and camera. Finally, connect the remaining yellow/white wire from the camera to the yellow/white wire on the OSD's extension and the remaining yellow/white wire from the VTx to the black wire on the OSD's extension. This might not make much sense, but we're not following the color coding shown on the servo extension for the OSD's connection cable. It should be Black = Video Out, Red = Ground, Yellow/White = Video In.

Once that cable's made, you're ready for testing. The GPS gets plugged in as shown above. You'll need at least one battery plugged into the Vvid connection to power the OSD. It can handle from 7V to 14V. If you only have a single battery to power both your video equipment and motor for the plane, then only connect the battery to Vvid. If you have two seperate packs one for video, one for the plane, then conenct the video pack to Vvid and the main plane pack to Veng.

If you are using
NTSC video equipment, you need to hold down the button for one second and release to change from PAL (default video mode) to NTSC.

Here is an example video of an OSD board in the wrong mode (make sure you watch at 0:13): http://www.vimeo.com/3343287



USB Serial Software
There are currently 4 cables that have been tested to work with Remzibi's OSD. The OTI cable and Prolific are the two cables that shipped with Remzibi's OSD. Take a look though the plastic case to see which you have received (see photo to the right).

OTI Cable
XP Users: OTi6858driver.zip
Vista Users: Read this guide to help you install these drivers.

Prolific Cable
XP Users: PL2303_Driver_XP2K_v204012.zip
Vista Users: vista-prolific-chip-driver-for-serial-adapters.zip

FTDI Cable - DIYDrones.com
This cable does not require any special software to use. You will, however, need to make a converter cable using the pinouts below. I purchased my crimper and parts from HansenHobbies.com.
This FTDI cable can be purchased DIYDrones.com.



FTDI Cable - SparkFun.com
This cable does not require any special software to use. You will, however, need to make a converter cable using the pinouts below. I purchased my crimper and parts from HansenHobbies.com. Please note that the 3.3V version will also work but you should not use the red wire shown as VCC below to power the OSD. It requires 5V and will not operate at 3.3V.
This FTDI cable can be purchased SparkFun.com.




Determining your COM port
On Windows XP, once you've installed the USB to Serial (Win2k) driver, and you've plugged in the device for the first time; click Start, Control Panel, System, Hardware, Device Manager and Expand the Ports (COM and LPT) branch. There you should find an item labeled "OTI USB-to-Serial Comm Port (COM##)" which will tell you which COM port you should select in the OSD Configuration Software.

The latest versions of the Configuration Tool attempt to locate the COM port automatically.




Installing Remzibi's OSD Configuration Tool PC Software
The full Setup can be found here http://www.happykillmore.com/Software/RemzibiOSD/Setup/Setup.exe

Please note that the minimum screen resolution for the software is 1024X768.

During the software install you will be asked to select a Video Mode (PAL or NTSC) and Units of Measure (Meters or Feet). These selections are defaults for the software and can be changed any time by clicking File, Preferences from the main screen.

By default, the software will look for new version online every time the program starts. If you wish to disable this feature, simply click Help and uncheck Auto Check for Updates on the main screen of the software.



Starting the software for the first time
When you first start the OSD Configuration Tool you will be prompted that there is a new version of the firmware, do you wish to update? Answer "Yes" to this question. When the update firmware screen appears, select the correct COM Port and click connect. Then connect the Blue/White portion of the USB to Serial cable and then the Red/Black wires. The screen should automatically start showing pages have been successfully sent. When it's completed, you're ready to start configuring your layout.

When you're ready to upload the layout to the OSD, click Tools, Serial Communication. Please refer to Uploading BIN and Font Files for instructions.



New BIN File DefaultsBack to Table of Contents
BIN Files/Font Files and HEX Files
BIN files - Short for "Binary Files" are simply data files that hold the configuration information for the OSD. They are transmitted to the OSD using Tools, Serial Communications.

Font Files - These files are used by the MAX7456 video chip to upload the font available on the OSD. They can be edited by clicking Tools, Font Editor and can be uploaded using Tools, Serial Communications.

HEX Files - Firmware files for the OSD board. These get uploaded to the bootstrap on the ATM microcontroller and contain the programming for the OSD. These files can be uploaded by clicking Tools, Update Firmware.



Preferences
Clicking File, Preferences will allow you to specify some defaults when creating a new BIN file. These settings only apply when clicking File, New BIN File.

For an explanation of what each option means, please see Options and GPS Datum



Options
Video Mode - NTSC or PAL. With PAL systems, you have 16X30 characters in the display grid. With NTSC, you have 13X30 characters.
Meters/Feet - Meters will set the OSD to use KM/H for speed and meters for altitude and distance to home. Feet will set the OSD to use MPH for speed and feet for altitude and distance to home.
Use home as Zero Altitude - Checked will zero the GPS' altitude after pushing the button on the OSD board making the ground 0. Unchecked will use the GPS' calculated altitude above sea level as the starting altitude.
Set auto home on bootup - Checked will wait for the specified satellites to be located and will automatically set the home position (same as pushing the button). Unchecked will require the user to push the button to set the home location.
Satellites for Auto Home - Specifies the number of satellites required to automatically set the home position (requires Set auto home on bootup to be checked).
NOTE: This value is actually "more than or equal to. So if you select 6, it will auto-home when more than or equal to 6 satellites are found.
More info can be found in this FAQ question.
Position Format - There are two different formats for GPS lat & long coodinates. Google Maps uses DD.DDDDDD by default.
Summary Display - After this number of seconds at zero speed, the OSD will display a summary screen with max values for Altitude, Distance from home and Speed. If this value is set to 0 it will not show the summary screen.



Video Modes
There are two video modes used in the world today. This defines the number of rows available to print graphics as well as the refresh speed of the video output (which is why it flashes when you view a PAL device on an NTSC screen). NTSC has 13 rows and PAL has 16 rows.

The OSD, by default, is set to use the PAL video mode. If you find that the display is blinking when you first connect/wire it up, you will need to hold down the button for one second and release it to change video modes.

NTSC - Used in U.S.A, Canada, Chile, Costa Rica, Cuba, Dominican Republic, Ecuador, Japan, Mexico, Nicaragua, Panama, Peru, Philippines, Puerto Rico, South Korea, Taiwan

PAL - Used in Afghanistan, Algeria, Argentina (N), Austria, Australia, Bangladesh, Belgium, Brazil (M), China, Denmark, Finland, Germany, Hong Kong, Iceland, India, Indonesia, Iraq, Ireland, Israel, Italy, Jordan, Kenya, Kuwait, Liberia, Malaysia, Netherlands, Nigeria, Norway, New Guinea, Pakistan, Poland, Singapore, South Africa, South W. Africa, Sudan, Sweden, Switzerland, Thailand, Turkey, Uganda, United Kingdom, United Arab Emirates, Yugoslavia, Zambia



GPS SetupBack to Table of Contents
NMEA Sentences
NMEA based GPS units have the ability to send multiple packets of data called NMEA sentences. Each of these sentences can be enabled or disabled along with the frequency of the sentence by changing the value in the combobox. If you specify "0" then this sentence if disabled. If "1" is specified, then one sentence is sent every so many milliseconds which is configured through the Hertz setting.

For example, If RMC is set to 3 and Hertz is set to 5, then every 200ms (1 sec / 5) the GPS will send it's sentences. Since RMC is set to 3, the RMC sentence will get sent every 3rd cycle or every 200ms X 3 = 600ms.

For Remzibi's OSD to function correctly, RMC and GGA should be set to at least a value of "1" (not "0"). All other sentences will be ignored by the OSD. However, if you are using the output of the GPS for another device along with the OSD, you may want to turn other sentences on.

By turning on additional sentences, you are using up more "bandwidth" on the GPS serial channel. If you turn on too many sentences and the baud rate is too slow, you will "swamp" the serial port and the GPS will be attempting to send more messages than is physically possible at that baud rate. Please pay attention to the bandwidth value for your GPS' baud rate.

For specific information about NMEA sentences, please check out this website

NOTE: Configuring NMEA sentences is only available in firmware 1.63 and newer.



Hertz
The Hertz of the GPS is the speed in which NMEA sentences are sent. By specifying 1Hz, 1 message will be sent per second. At 5Hz, that's 5 messages per second or 200ms. The recommended Hertz setting is 5. On the OSD there is little benefit to going above that and you do run the risk of causing problems (especially at 10Hz) on the serial port if there is static or interference.

NOTE: Configuring GPS Hertz is only available in firmware 1.63 and newer.



Other Commands
The OSD can be configured with your own PMTK commands or other GPS commands. You will need to use ALT+Enter after each line. The software will convert this from a CRLF to a CHR(0) as is required by the OSD firmware. If the command requires a checksum that too must be manually calculated and entered in the Other Commands field.

There are exactly 128 characters available in the BIN file for PMTK commands. By turning off other defaults (like NMEA sentence setup, SBAS, etc) you can free up as much as 128 characters for the "Other Commands."

NOTE: Configuring "Other Commands" is only available in firmware 1.63 and newer.



Specific PMTK commands
The software sends the following commands as defaults:
$PMTK314,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0*28 - NMEA Setup
$PMTK313,1*2E - SBAS Enable
$PMTK301,2*2E - DGPS Mode
$PMTK220,200*2C - Hertz
$PMTK330,220*2E - Datum

$PMTK251,38400*27 - Baud Rate (NOTE: Only sent on firmware older than 1.63 but not actually used)



GPS Datum
At the time this was written, there were 24 GPS satellites orbiting the earth. The GPS unit has 222 different regions that can be used as an offset for these GPS satellites. By selecting the right datum, you will be able to increase the accuracy of your lat and long positions when referring to a map. A datum is essentially an offset value for disagreements in a "zero point" that have occurred over the years. If all map makers agreed about where the zero point was located, it would be easy enough to say, "start at the zero point and go West this far and North this far." The trouble is, the powers that be have changed the starting point a few times over the years (the prime meridian once ran through Paris France instead of Greenwich England, for example).

Selecting the wrong Datum will not have any ill effects on your OSD, it will just have an offset of up to 200 meters if you plug your lat & longs values into Google Earth (for example). Google Earth uses WGS84 (Datum #220 on your OSD). So if you plan on plugging in your OSD lat & long coordinates into Google Earth, I suggest you use the 220 Datum on your OSD.

Here are some good sites that explain datums and why you need them:
Datums Explained: http://www.alpharubicon.com/prepinfo/mapdatumwmerrin.htm
Datum Offset: http://earth-info.nga.mil/GandG/coordsys/onlinedatum/indexmap.html
Satellite locations: http://www.nstb.tc.faa.gov/Full_WaasSatelliteStatus.htm



Main ScreenBack to Table of Contents
Configuring your OSD's Layout
The software's main screen has a series of display objects that can all be configured individually. Each object has a visible, row and column selections as well as other parameters that are specific for that object.

There is a grid available from the menu: ... View ... Show Grid. This grid may be toggled on or off as desired.

Objects can be selected from the list of available displays on the left or simply by clicking on the item you would like to edit. The selected object will be shown in yellow. Objects can also be dragged and dropped anywhere in the visible area.

Most objects (with the exception of the graphic objects) have a slider bar shown in the parameters area. This slider is simply for testing purposes and will not have any effect on the saved BIN file.

You can select as many or as few display objects as you'd like. One thing to keep in mind is that each television will display a different number of rows so it might take some adjustment towards the center of the screen to make everything visible on your TV or monitor. If you're using a software video capture adapter (ie EasyCAP) then all columns and rows will be visible.

Once you have adjusted the display objects to your liking, click File, Save BIN File As... and give it a logical name.

Your next step is to upload your new configuration file (BIN File) to the OSD hardware. Click Tools, Serial Communications to upload the BIN file.



Available Displays
The available display object list allows selection of individual items that can be configured. Some items like "Title Screen Text" only appear during the initial bootup of the OSD.

The X Graphic objects are simply static graphics on the screen. They could be letters to show text or perhaps a sight to show the center of the display.

All other displays show some aspect of real time data. Many have the ability to select different graphics that are shown before the real time data (ie: Speed and Distance Home). Others only show the data itself (ie: Latitude and Longitude). Simply click on one of the available displays in the list and you can tweak the parameters to your liking.

The following displays are currently available:
Altitude (GPS): Optional Header Symbol, Data (from GPS in meters or feet selected in options), Optional Footer Symbol
Azimuth (Angle from Base Station): Optional Header Symbol, Data in degrees (NOTE: This is the location of the plane in the sky from the perspective of the base station), Optional Footer Symbol
Direction Home: Graphical arrow indication which way is home (Arrow positions depends upon font file - H50 thru H6F)
Distance Home: Optional Header Symbol, Data (meters or feet selected in options), Optional Footer Symbol
Frequency Counter (Hall effect sensor): Optional Header Symbol, Data (whole number RPM's from external sensor), Optional Footer Symbol
Heading (GPS): Optional Header Symbol, Data in degrees (from GPS, not magnetic), Optional Footer Symbol
Latitude: Latitude GPS position (format DDMM.MMMM D=Degrees, M=Minutes)
Longitude: Longitude GPS position (format DDDMM.MMMM D=Degrees, M=Minutes)
Run Time: Optional Header Symbol, Data (Minutes:Seconds), Optional Footer Symbol
Satellites: Optional Header Symbol, Data (Number of satellites located), Optional Footer Symbol
Speed (Ground): Optional Header Symbol, Data (from GPS in MPH or KM/H selected in options - indicates ground speed not air speed), Optional Footer Symbol
Title Screen: Text Shown on Boot-up of OSD
UTC Date: Optional Header Symbol, Data (Universal Date (GMT) format ddmmyy), Optional Footer Symbol
UTC Time: Optional Header Symbol, Data (Universal Time(GMT) format hhmmss), Optional Footer Symbol
Variometer (Rate-of-climb inidcator): Indicator for up or down changes in altitude. The number shown is feet/s or meters/s based on the meters or feet option selection. (NOTE: This does NOT require additional hardware and is based solely on changes detected by the GPS)
Voltage - Motor: Optional Header Symbol, Data (Voltage on secondary ADC input), Optional Footer Symbol
Voltage - Video: Optional Header Symbol, Data (Voltage on primary ADC input), Optional Footer Symbol
X ADC2 - X ADC6: Optional Header Symbol, Data (Configurable via min and gain values), Optional Footer Symbol
X ADC7 Virtual (mAh Counter for ADC6): Optional Header Symbol, Data (Running MAH count based on current sensor on ADC6), Optional Footer Symbol
X Graphic 01 - X Graphic 32: Static graphic (2 characters)



Parameters
Parameters allow individual display objects to be adjusted to the user's liking.
Visible - Checked will display object, unchecked will hide object
Column - Column number. This can also be set by dragging & dropping the object.
Row - Row number. This can also be set by dragging & dropping the object.
Text Size - Small or large. There are two font sizes used by the OSD in the font file.
Header - Symbol will show a graphic before the object's data, Label allows for text before the data.
Label - This defines what text will appear before the data.
Symbol - Click on the picture box to select the symbol from the font list.
Alarm Type - "Less than" or "Greater than". If set to "less than", any time the output value drops below the alarm value setting, the header symbol will flash. If set to "Greater Than", any time the output value goes above the alarm value setting, the header symbol will flash.
Alarm Value - Altitude, Distance from Home, Voltage - Video and Voltage - Motor all have alarms. In the case of Altitude and Distance, if the data value goes higher than the alarm value, the symbol will flash every second. With voltage, the symbol will flash when the data value drops below the alarm value.
Format - "0" or "0.0". If you want a decimal place on your ADC output, select "0.0" or for whole numbers only, select "0".
Arrow Positions - The direction home object shows an arrow graphic that points the way home. Different font files may have a different number of steps for the arrow graphic. These appear in the Font File from H50 to H6F. Typically, there will be 12 or 16 arrow positions. To determine how many arrow positions there are, count the number of arrow graphic pairs are present on the font file (Tools, Font Editor) between H50 and H6F.
Note: As of v2.1.0 of the Configuration Software, the arrow positions value is fixed at 16.




Font EditorBack to Table of Contents
Editing Font Files
Remzibi's OSD board makes use of a MAX7456 chip which allows users to define their own font files. Each font file is made up of 256 characters which are 12X18 pixels each. Remzibi makes use of two different size fonts which are set at a fixed location.

Large Fonts begin at character h01(#2) and end at h24(#37).
Small Fonts begin at character h81(#130) and end at hA4(#156).

All other characters can be redefined. One thing to note is that Variometer and Direction Home make use of a series of images in a specific order. So it is important to pay attention to the characters following the selected character.

Only white and black pixels are actually displayed on the screen through the OSD board. All transparent pixels will show the input video image.



Show Dual Characters
X Graphic objects and Direction Home symbols have two characters shown next to each other when displayed. Checking the Show Dual Characters check box will make it easier to edit the pair of characters.



Save Character / Save Font Set
Clicking save character will only store the pixel changes made to one specific character in memory. To save the font file to disk, either click Save Font Set which will save over the existing font file or click Save As... and enter a different name for the font file.



Basic Tools
Set All Black/White/Transparent - Clears contents of character and set all pixels to selected color.

Inverse Colors - Will set all white characters black and all black characters white.

Flip Vertically/Horizontally - Reverses or flips character upside-down.

Nudge Up/Down/Left/Right - Bumps the character one pixel up, down, left or right. This same function can be accomplished with the arrow keys.

Copy/Paste Character - Entire characters can be moved to other locations or copied, pasted and edited to create a new character.



Hex EditorBack to Table of Contents
Manual Tweaking of BIN Files
Power users may wish to tweak some characters of the BIN file. If you're using a different manufacturer of GPS you can edit h00E0 through h014F to include GPS setting strings. You can also change the text displayed for Units when the OSD initializes by editing h00D0 - h00D8 for Feet and h00D9 - h00DF for Meters. Double clicking on a string will automatically open the text editor.

NOTE: Editing this file manually may cause unexpected results so please do not edit the BIN file using the HEX editor unless you know what you're doing!



Updating FirmwareBack to Table of Contents
Updating the OSD's Operating System
The OSD's operating system is called the Firmware. When new updates are posted, the update script will prompt you upon starting the program that there is a new version of the firmware. It is highly recommended that you load this new version.

NOTE: The update routine is VERY flaky and does not like to be interrupted. Is it suggested that you do NOT click away from the update firmware screen during the udpate process. If the process fails, no harm has been done, you'll just need to start it over again.

Using the Firmware Update Routine
Step 1) Select COM Port and Click Connect
Step 2) Select Source Firmware File (latest version will be automatically selected)
Step 3) Connect USB Serial cable to OSD board (Blue, White and Black Wires)
Step 4) Connect a battery to the Vvid (+Power-) connection.

The update process should start automatically. If you get a failure, please disconnect the battery and reconnect it. If it continues to fail, please follow the directions below to use the MegaLOAD software.




Using the MegaLOAD software
Using the MegaLOAD Software
Some users have reported serious trouble getting the Firmware Update routine to work from the OSD software. So to get around this issue, the OSD software includes a copy of the MegaLOAD software from MicroSyl.com who is the author of the Bootloader (a small piece of code pre-loaded on the OSD board to allow these firmware updates to work).

To open the MegaLOAD software, click Tools, MegaLOAD from the Main Menu. By clicking this, your layout/configuration information will automatically be converted into a HEX format that the MegaLOAD software can read (Called "File to be programmed in the EEPROM"). It will also automatically set the COM port to the same one specified in the OSD software.

To begin the firmware update, simply connect a battery (without holding down the red button). The firmware update and program upload should happen immediately.

Please Note: MegaLOAD does not replace the OSD software, it is a tool for those who are having trouble getting the firmware update routine to function.



Serial CommunicationsBack to Table of Contents
Serial Communications Overview
Opening the Serial Communications screen
The serial cable communications screen can be accessed three ways.
1) Click Tools, Serial Communication from the main screen
2) Click "F6" from the main screen
3) Press the "Serial Communications" button on the main screen

The serial communications screen has several functions. It can test the USB to serial port to verify that communications are working. It can upload your layout (BIN) information and fonts to the OSD. It can download from the OSD. Finally, it can calibrate the ADC's, which will be explained further into this manual.

The first step to using your OSD is to run a test to make sure the cable is able to communicate with the OSD correctly. When you run the software for the first time, it will prompt you to run this test. It is not necessary to run the test routine every time you program your OSD, only the first time or any time you are having problems communicating with the OSD.

Normal/Programming Modes
Your OSD has two modes. "Normal" mode and "Programming" mode. If you connect power to the OSD without holding down the red button, you will boot in Normal mode. This is how you connect using the GPS or GPS emulator or to update the firmware. If you connect the power with the red button pressed, you will enter Programming mode which is used for uploading, downloading and ADC calibration.

Connecting OSD in programming mode
Step 1) Connect your USB cable to your computer.
Step 2) Connect your USB cable to the OSD (NOTE: Red wire may not exist on your USB cable) but please note the location of the blue, white and black wires.
Step 3) Connect a battery to the +Power- (also known as Vvid) connection while holding down the red button on the OSD.
Step 4) Release the red button on the OSD.
Step 5) Open the Serial Communications screen on the PC software.
Step 6) Click the magnifying glass button (to find the COM port with the cable connected) and click Connect (or select the COM port manually and click conect).
Step 7) From the "Serial Cable Setup" tab, click "Start Test."

If everything worked as expected, you should see "Status: Passed (Firmware v#.##)" If not, you'll need to figure out if the operating system has a problem with the cable or if the wrong COM port has been selected.

Troubleshooting your USB to serial driver
To troubleshoot a bad connection, you'll need to open the "Device Manager" and expand the "Ports (COM & LPT)" branch and find the "OTI USB-to-serial Comm Port (COM##)" and make sure the OSD sofware is using the right COM port. If it's missing from the device manager screen, you may need to reinstall the drivers which can be found in the C:\program files\Remzibi OSD\USB Programmer\1.12.35 folder on your computer. Try running Setup6858.1.12.35.exe again and disconnect and reconnect your USB to serial cable. That should add the driver to the Device Manager screen. If that doesn't work, you might want to try a different USB port or you may have something wrong with your USB cable or operating system.

Show/Hide Communcations Log
By clicking Show or Hide at the bottom left you can open or close the communications log. Generally, you will not need to see the specific commands being sent or received by the OSD. However, in specific cases, you can use this function to send commands directly to the OSD. If you click the Show button and enter "VER" (no quotes) and hit Send, the OSD should respond with the verision number in the box on the right.



Upload Program & Font
Uploading Program (BIN Files) & Fonts
Step 1) Connect the OSD in programming mode (red button down while connecting power).
Step 2) Check one or more of the following options
  • Upload BIN (Program) Data - This will send your layout information to the OSD
  • Upload ADC Data (Gain & Min) - By selecting this you will overwrite your existing gain and min information from your previous calibrations. Generally, you do not want to select this option.
  • Upload Selected Font - If you have made a change to the font file or have a new font file on your computer you'd like to use, select this option.
    Step 3) Click Upload to OSD.

    Uploading the BIN (Program) Data will take about 30 seconds. Uploading the Font file will take about 4 1/2 minutes. Remember, you only need to upload the font files if you've made a change or want to upload a different font.

    Downloading Program (BIN Files)
    Step 1) Connect the OSD in programming mode (red button down while connecting power).
    Step 2) Click "Download from OSD"

    This process will grab the BIN file data from the OSD and overwrite what's in memory on the PC. When you click Exit on the Serial Communications Screen, the layout will refresh and show you how things are configured on the OSD. Please be careful. If you've opened a file and have made changes, downloading from the OSD will overwrite what's in memory and if you hit save, it will overwrite the file.




  • ADC Configuration (Basic)
    ADC stands for "Analog to Digital Converter" and is a built-in process on Microcontrollers (like the Atmel chip on this OSD). It's purpose is to convert an analog voltage into a digital number so that a math function can be completed on it. The value of the digital number is not really important, but it is important to tell the microcontroller what that value means so it can display the correct value on the output. So an input of 12.0V on the analog input of the ADC may convert into 746 as a digital readout. That value is then scaled using a "Gain" value and adjusted using a "Min" value.

    On the Basic ADC Setup, you don't have to worry about what the gain values or min values are, you only have to worry about the input voltage.

    Each ADC has an alarm value which will cause the header symbol in front of the ADC's value to flash. By default the Voltage-Motor (ADC0) and Voltage-Video (ADC1) are set to the "Less Than" alarm type meaning when the voltage drops below the alarm value, the symbol will flash.

    Using the Basic ADC Setup
    Step 1) Connect the OSD in programming mode (red button down while connecting power).
    Step 2) Using a Multi-meter (preferrably NOT a Watt-meter), measure the voltage on two battery packs.
    Step 3) Connect the battery packs to the OSD.
    Step 4) Open the Serial Communications screen and select Basic ADC Setup.
    Step 5) Click "Start Polling" (This will start asking the OSD for the current ADC values for both Vvid and Veng batteries).
    Step 6) Highlight "Voltage-Motor" and type the battery's votage (ie 12.0) in the current voltage field and an alarm value (ie 9.0) in the alarm value field.
    Step 7) Highlight "Voltage-Video" and type the battery's votage (ie 12.0) in the current voltage field and an alarm value (ie 9.0) in the alarm value field.
    Step 8) Click "Program OSD"



    ADC Configuration (Advanced)
    For those users who wish to attach other devices to the OSD, the Advanced ADC is for you. Temperature sensors, current sensors, RSSI (RX signal strength) or any other sensor (with the exception of Frequency Counter - which has it's own dedicated object on the OSD) can be connected as long as it puts out an analog voltage based on it's measurement. You'll need to include a resistor and possibly a capacitor between the sensor and the OSD board to protect the OSD's microcontroller. For more information, please read the Poor Man's OSD thread on RCGroups.com.

    You are going to need be able to make the sensor function while using the Advanced ADC setup in the OSD's software. The two critical items are the "min" value which means "what is the zero value" and be able to make the sensor function as close to the max as possible to adjust the "gain" value.

    Using the Advanced ADC Setup
    Step 1) Connect the OSD in programming mode (red button down while connecting power).
    Step 2) Open the Serial Communications screen and select Advanced ADC Setup.
    Step 3) Click "Start Polling"
    Step 4) Put the sensor in it's zero state. Read the "Current ADC" value and try this into the "Min Value" field.
    Step 5) Put the sensor in it's max state.
    Step 6) Click the "Desired Output" field and enter what you'd like to be shown when the sensor is at it's max (ie 100).
    Step 7) Enter an alarm value.
    Step 8) Click "Program OSD"

    Positive Gain
    Above, we assumed that the max ADC value is greater than the min ADC value. This means we have a positive gain. If the max ADC is less than the min but you'd like to view it as 0-100 where 100 is the max, see the Negative Gain section below.

    In the steps listed above, the Gain value was automatcially calculated when the "Desired Output" field was modified. It doesn't have to be done this way. Here is another way: Let's say a temperature sensor puts out a digital value of 129 when it's at 0°C and a digital value of 563 at 100°C. We could enter 129 for the "Min Value." To calculate the Gain, we take Output / (ADC - Min) = Gain = 100 / (563 - 129) = 0.23041.

    So as an example, if the ADC reads 412 then the output = (ADC - Min) X Gain = (412 - 129) X 0.23041 = 65.2°C.

    Negative Gain
    Let's say you're trying to use the RSSI (Received signal strength indication) output from your RX and the peak/max ADC value is 322 and the min ADC value is 840. But you'd like to show 0 when there is no signal and 100 when there is peak signal. You need to use a negative gain in this situation.
    In this situation, you'll need to enter the min ADC value (ie 840) in the "Min Value" field.
    Then you'll need to calculate the gain. Gain = Output / (ADC - Min) = 100 / (322 - 840) = -0.19305.

    So in the example above:
    If the ADC reads 711, Output = (ADC - Min) X Gain = (711 - 840) X -0.19305 = 24.9% (This would be a low signal strength)
    If the ADC reads 405, Output = (ADC - Min) X Gain = (405 - 840) X -0.19305 = 84.0% (This would be a high signal strength)

    Frequency Counter
    The frequency counter does not use the Serial Communications window. It is configured directly from the main screen by highlighting the "Frequency Counter" object and entering a gain value in the gain field. Typically, this will be 1 / {Number of detectors}. So if you've got a detector on each of your 3 blades on a propellor, your gain will be 1 / 3 = 0.33333 so for every revolution, the sensor will trigger 3 times X gain of 0.33333 = Actual RPM.




    GPS EmulatorBack to Table of Contents
    Flying your imaginary plane

    For testing purposes, instead of connecting your GPS module (which may be embedded in your plane) you can run the GPS Emulator. This will send test signals through the USB serial cable to your OSD board so you can test your BIN file's configurations with dummy data. The first commands sent to the OSD board after clicking Start are 38400 baud EXIT commands to reboot the OSD board automatically. When the board comes online it will operate at 9600 baud and start talking to the GPS emulator.

    NOTE: If you wish to go back and upload a new BIN file please remember to disconnect the GPS emulator and put the board back in programming mode before trying to use the Serial Communications screen.

    Start Latitude/Longitude - Specifies your starting location (this can be helpful to show the actual numbers you will see when you fly locally).
    Satellites - You can use this to test the Auto Home function (please note the auto home routine only updates every 60 seconds).
    Pitch/Yaw/Speed - Determine the speed and direction of the imaginary plane.
    Level Off - This will return the pitch and yaw to to a 0 change situation. It will not change the heading of the plane to 0 degrees.
    Lock on Top - When checked, the GPS Emulator will stay the top most form so it is easy to get to when using EasyCAP or other video capture software programs.

    The GPS Emulator can emulate several NMEA sentences. Remzibi's OSD currently only uses two of these sentences; GPRMC and GPGGA.



    Sample Output from GPS Emulator
    The GPS Emulator was designed to provide the minimum output to make the OSD function. It does pass the "locked" bit in the GPGGA string so it may be able to function for other purposes.

    For more information on GPS NMEA sentences, please take a look at http://aprs.gids.nl/nmea

    Sample Output
    $GPGLL,5000.0100,N,02000.0000,W,151456.300,A,*21
    $GPRMC,151456.300,A,5000.0100,N,02000.0000,W,40,0,290609,003.1,W,*5D
    $GPGGA,151456.300.000,5000.0100,N,02000.0000,W,1,9,0.0,300,M,1.2,M,,*6C



    GPS Fix Values
    For the use of simulating output for the OSD, changing this value doesn't do much. If you change it to 0, that's the "invalid" or "no fix" setting. The OSD's satellite object will show the eyes going back and forth searching for satellites. Anything other than 0 is considered a "fix" for the OSD and it will show the number of satellites found.

    For more reading on GPGGA sentences, look here: http://www.gpsinformation.org/dale/nmea.htm#GGA



    Language EditorBack to Table of Contents
    Creating a new language file
    From the main screen, either click F11 or Click View, Languages, Language Editor. This will pop-up an application called "Remzibi OSD Language Converter." It is included with the setup.exe and allows anyone to create their own language file and upload it for others to use.

    From the Language Converter application, simply click File, New Language.

    Enter the name of the language you wish to create.
    NOTE: Please use the native word for your language (ie Español instead of the English version of the word - Spanish). You do not need to check the box labeled "Create from another language" unless your new language is a "flavor" of another langauge. This will create a clone of the existing language you have selected.
    Click "Create File"

    Now you're ready to start converting. Click the first record in the translation column and start typing. In some cases, the text will be very long and it might be helpful to use the "Long translation" box at the bottom to give you more room to work. You can also resize the conversion tool and adjust the column width to make it easier.


    Special Characters:
    • Items containing a single “&” sign will create a shortcut (shown as an underline in the software) i.e. &File = File and would mean if the user hits ALT+F then the file menu would be selected. You don’t have to use these shortcuts, but some users like to use them.
    • Items containing a double “&&” sign will just show the “&” sign once. i.e. "This && That" = "This & That"
    • Items containing a “^” symbol will insert a carriage return (line break) wherever this is located. Please note that not every field is designed to handle more than one line, so I do not recommend adding a carriage return where there isn’t already one. It is ok to add as many carriage returns as you’d like to popup message boxes because they will automatically size correctly.
    • Items containing &1, &2, etc symbols will have that value replaced with something coded in the software. A good example is in the update section.

    &1 Update^Version &2 is available.^Do you wish to download now?

    Becomes

    Rembizi’s OSD Software Update
    Version 2.0.15 is available.
    Do you wish to download now?

    Where “Remzibi’s OSD Software” and “2.0.15” were replaced by the software.

    Special Fields:
    ID #0 = IDS_GLOBAL_MISSING_VALUE contains the text that will be shown anywhere the language file is missing a translation (marked as yellow).
    ID #2 = IDS_HELP_FILE_URL contains the URL the software should use when the user clicks F1 or Help, Online Help. This can contain a link to a webpage or a link to a document (ie Word Doc or PDF <-Recommended).

    Please remember to SAVE OFTEN! I have had a few crashes on the language translation software that I have not yet been able to track down.



    Editing Author's Information
    The purpose of the Author's Information screen (Edit, Edit Author Info) is to show who did the translation. I ask that people include their name and email so that I can get in touch with them if they need to make a change or addition to the file.

    The "Available to Public" check box determines if the language file is available to everyone to download. If it's unchecked, it will not appear in the Available Languages screen from the OSD software.

    The version number will increment automatically each time you save your language file.



    Sharing your new language file
    Once you've completed your new language file translation, click File, Upload Language File from the Language Converter Application. This will add your new file to the online database which can be downloaded by anyone (assuming you have checked the box "Available to Public" in the Author's Information screen). See the section on Finding other language files for details on downloading.

    Clicking "Save" in the language conversion application will not automatically upload your file, so please remember to click File, Upload Language File to share your changes!



    Key Code assignment
    The upload process assigns a "Key Code" to each language file to keep users from overwriting each other's work. If someone has already created a file called "Español" another user cannot upload another file by the same name. They can, however, work together if necessary by sharing the Key Code with each other. The first time a file is uploaded, it will be assigned the code automatically (shown at the top of the language conversion screen) and can be entered on another computer by clicking File, Enter Key Code.

    NOTE: You should only give the key code to someone you trust to maintain or help you do your conversion.



    Auto-Update Remzibi OSD option
    In some cases, it may be difficult to determine if your new translation will fit in the space provided (pay partiticular attemtion to the "Options" translations - ID# 2001 - 2007). To help with testing, if you check "Auto-Update Remizibi OSD" in the Edit menu of the language converter, it will create a "link" to the OSD software. When you click Save in the Language converter, it will send a message to the OSD software to reload the language file. This may make it easier to "tweak" the length of some translations.



    Finding other language files
    To check the online database for other language files that are not currently installed on your computer, click View, Languages, Download New Language file.

    Any language files you have not already downloaded will appear in the list. If you have already downloaded a non-standard langauge file, the OSD software will automatically keep your language file up-to-date.



    FAQBack to Table of Contents
    Q: What number should I use for Satellites for Auto Home?
    A: The miniGPS Software shows a "Fix Type" of "3D SPS" when 7 satellites are located. In the OSD Config Tool, selecting 7 would be the smallest number recommended. The auto home routine also only runs once every 60 seconds. This means that even though you may show more than the selected number of satellites, it will not trigger the auto home routine until the next full minute of run time. This is by design.



    Q: Why does it take so long to acquire satellites?
    A: The software routine on the OSD hardware updates the display when searching for satellites once per minute. This is by design. It takes several minutes to ensure good communications with the satellites.



    Q: How can I change the default BIN file when I click File, New BIN File?
    A: It is currently not possible to change the default BIN file. With every update, the default BIN file gets overwritten to make sure that the latest features are enabled correctly.



    Q: Why can't I get the BIN file to upload?
    A: If you're in the Serial Communication screen and you've click Connect and nothing appears in the "Inbound Messages" window if you Type R in the outbound message box and click send, then more than likely you have either specified the wrong COM Port or you are not in the programming mode of the OSD.



    Q: Why do I need to run an ADC calibration?
    A: The microcontroller contains an ADC (Analog to Digital Converter) which outputs a number that represents the voltage measured. Generally, there is no need to calibrate the device but if you notice that your displayed voltage does not match your measured (with a Digital Multi-Meter) voltage, then you can use the calibration routine to make the microcontroller show a number much closer to the actual voltage.

    For some very technical reading, see Amtel's Website



    Q: How do I get into the programming mode of the OSD?
    A: There are two modes for the OSD board: the run mode (just plug in the battery and GPS), and the programming mode (for uploading BIN files and Font Files). To get into the programming mode, follow these directions: (Note: OSD2 refers to the newer board with a 4 pin, 3 wire USB connector - no red wire.)

    1) Connect the "USB to Serial cable" to your PC.

    2) Start the Configuration Tool's Serial Communications Screen.

    3) Select the right COM Port and Click Connect.

    4) For the original OSD board: Connect the Blue&White wire connector of the "USB to Serial cable" to your OSD board ... while holding down the OSD button connect the USB's Red&Black wire connector to the OSD (right beside the Blue&White connector location).

    ... For OSD2: Connect the USB 4pin connector (with no red wire) to your OSD board ... while holding down the OSD button connect a 2S/3S battery to the OSD POWER connector.

    5) Release the button.

    In the Inbound Messages window of the Serial Communications screen, you should see "€€REMZIBI OSD" followed by the current firmware version of the OSD.



    Q: I lost my plane, how can I use the GPS coordinates to find it?
    A: Google Earth is a good tool to try. The latitude and longitude numbers on Remzibi's OSD are represented as degrees (dd), minutes (mm) and seconds(ssss), but in the format where Latitude is ddmm.mmmm and logitude is dddmm.mmmm.

    Once you have installed Google Earth and you have written down your last latitude and longitude (from your video recorder's playback), open Google Earth and click the "Fly To" tab on the left side of the main screen. From here, you can enter the coordinates from your OSD in the form of dd mm.mmmm [N/S],ddd mm.mmmm [E/W] (ie 36 00.9658 N,114 44.2698 W).

    Google Earth also shows Lat and Long in another format (dd°mm'ss.ss). You can convert from one to the other by multiplying or dividing by 60. From the format on Remzibi's OSD, if you take the fractional minutes (.mmmm) * 60 = ss.ss.

    For Example:
    3600.9658N = 36°00' + .9658 X 60 = 36°00'57.95N
    11444.2698W = 114°44' + .2698W X 60 = 114°44'16.19W

    Please note that if you have not selected Datum #220 (WGS 1984 Global Definition) then your location shown on Google Earth may be off by as much as 200 meters.



    Q: What is a GPS Datum?
    A: Take a look here.



    Q: Is there anything better than ULEAD VideoStudio to use for video out testing?
    A: Yes! Try AMCAP, it's lightweight (no installer, just a 48KB executable) and QUICK! Just make sure to change Options, Video Input to Video Composite.



    Q: How does the automatic update work and how can I turn it off?
    A: The automatic update routine opens a website when the OSD PC software launches. It sends a few bytes of data including the product ID and the update type it's looking for. The webpage looks in a database on HappyKillmore.com for the current version number available on the website and returns that information back to the PC software. The PC software then compares the webpage's version number with the current version number of the PC software. If the PC software is older, then it prompts you about a new version.

    If you click Yes to download, then some additional info is uploaded to the webpage including your current PC software version, your computer's name, your IP address, your firmware version, your OS language and regional settings and a few other items. This data is only seen by Remzibi and myself (HappyKillmore) and helps us figure out what countries users are located in so we can develop new language files as needed. It also helps me see if any users have already downloaded a version I posted too soon. If they did, then I need to change the version number again and post another update (which is why I have several updates per day sometimes).

    Once this data is uploaded to the webpage, it responds with a link to the update executable. This information is retrieved by the PC software and it's passed to a program called HttpSrv.exe (which was written by me) and then the OSD PC software is closed.

    The purpose of HttpSrv.exe is to download the update executable and launch the update without any input needed from the user. With Internet Explorer it would have required several confirmations from the user to run the program so I created HttpSrv.exe to get around that issue and download and launch with no questions asked.

    The update.exe is then launched. It's a WISE installer that overwrites any files that are out of date and again, doesn't ask any questions. Once it's completed, HttpSrv.exe and update.exe are both closed automatically and the new Remzibi OSD.exe is launched. So now you're up to date!

    If you'd like to disable the automatic updates, you can click Help and uncheck "Auto Check for Updates" and the software will no longer automatically check that webpage when the program starts. You can still do it manually by clicking Help, "Check for Update."



    Q: Who the heck are you HappyKillmore and how are you involved with this project?
    A: Good question! Last October (or November or December 2008, I can't remember exactly) I was looking into buying my first FPV setup. As I looked around the FPV forum on RCG and found Remzibi's Poor Man's OSD thread. I really liked the idea. At the time, Charles Beener (who is also from Ohio, USA) had been working with Remzibi to do the configuration software. I posted a message saying I am a VB6 programmer and I'd like to help.

    Charles was nice enough to send me his source code (also written in VB6) and I was off and running. By the end of January 2009, Remzibi had sent me the OSD board and I released my first version of the PC software. Over the last 6 months, lots of features have been added to the OSD hardware, firmware and PC software. So far, I've posted 82 updates (as of 6/24/09)... and there's no end in sight.



    TroubleshootingBack to Table of Contents
    OSD with GPS connected
    1) Connect the GPS, battery and VTx as shown here Wiring.jpg
    2) Make sure the GPS unit is as far away from the VTx as possible (13 inches is recommended but may not be possible). Do this outside, if you're in a basement or a building with concrete walls you may not get a signal inside.
    3) Wait 2-3 minutes. It can take that long to get the signal after plugging the battery in.