1/ Software Update on the integration of Remzibi OSD and APM
I am just updating Blake's and binzi's Blog contents: Blake and binzi
I do not know how to make a firmware for APM Planner, so you will need to use Arduino GUI tool
Replace your ArduPilotMega folder with the ArduPilotMega folder from APM2.1.2-OSD.zip: APM2.1.2-OSD.zip
Configure the APM_Config.h to your need
//to deactivate use OSD_PROTOCOL_NONE
//#define OSD_PROTOCOL OSD_PROTOCOL_NONE
#define OSD_PROTOCOL OSD_PROTOCOL_REMZIBI
// port 3 is the telem port on the shield
#define OSD_PORT 3
// set a radio switch to activate/deactivate the OSD output :
// below 1450 will display the OSD
// above 1450 will stop displaying the OSD
#define OSD_MODE_CHANNEL 6
// choose your unit to display the disctance to waypoint in feet or meter
#define OSD_UNIT OSD_UNIT_METER
//#define OSD_UNIT OSD_UNIT_FEET
Then follow the normal process from the wiki above.
http://code.google.com/p/ardupilot-mega/wiki/Code
2/ Hardware
To connect your APM with the Remzibi OSD, you need to have a cable from Telem port to Remzibi GPS port. GND and TX (from APM) are enough.
If you do not see any OSD info at first, stop your camera feed to see if the OSD shows up anything. You might be starting in the wrong TV mode (PAL/NTSC). You just have to push the OSD button for about 1 second.
3/ Remzibi
You need to use Remzibi OSD software from Remzibi site and update your layout with APM.bin and flash the firmware using ARDU firmware (Announcement) in the same software.
Note: for metric or feet units , be carefull to use the right unit in the Remzibi OSD software. You need to change the APM_Config.h for feet/meter of the next waypoint in the status at the bottom
4/Usage
Once everything is connected, normally the APM sets HOME for the OSD once it gets a GPS_fix. If you connected your OSD after that, then you can just push the OSD button once to force the HOME location on the OSD.
The arrow and distance from home will always display home direction and distance to home direction. It won't show the next waypoint direction (too complicated yet )
5/ what's new
I have updated all the units and it should be displaying proper values now
Comments
Thanks Peter,
Can you share your APM.bin. I did not look in the flickering issue but I am happy that you solved it 8).. nice
Second issue : The video shows an old version that was not right. The one attached to the post should be working fine. I have made the mistake several time . The artificial horizon should be parrallel to the real horizon ie: if you bank to the right, the horizon should bank to the left ... unatural unless you fly 8))
As is, the code is not ready to go streamline and there is no easy way to connect the APM to the OSD and use Xbee at the same time. It needs a bit of tinckering. I might write a message to Chris to ask what should be done to integrate it. I know they are working on a DiyDrone OSD and he might want to support only one official OSD eventually.
Hi Matthias,
Very well done thanks. I did get it to work yesterday but had to make some small changes.
On the OSD I noticed that some values were flickering badly. When I looked at the APM.bin file with Remzibis software I noticed that some elements were overlapping. Rearranged the layout slightly and now the display is perfect.
The second issue was that the roll on the artificial horizon was backwards and I had to change it in the Arduino code. Now it looks great and I can't wait to test it in the air.
Not sure why I had to make these changes as it seems to work fine for others but I'm happy that it works now.
I too would like to see this integrated in the main code.
@HK : is it how it worked in ardupilot (no mega)? I understand that it makes more stuff to test and an in house osd is in the work but I could not wait and I would like my investment not to be lost.
Updated it to 2.1.2 and fixed all the wrong units.
Would be nice to see this code be integrated in main APM codebase.
@Johann: For the overlay, it might be an electrical issue (bad wiring)
I have done a debug session of the values displayed and most of them are wrong (speed, altitude, direction to waypoint). I had lat/lon non displayed but I would not be surprised that this, as well, was wrong.
I will release a new version tomorrow.