Hello everyone. Recently I port the MinimOSD to the Remzibi OSD's harware, so a poor man can enjoy MinimOSD's convenience now (no need to modify APM's software anymore).
Because of the limited flash space of Atmega16, the code of OSD is slightly changed, and it is not compatible with Michael's original config tool. So I adapt the config tool as well.
The Remzibi's OSD uses Megaload bootloader, so please use the Megaload programmer to upload the firmware. (The config tool can also upload the firmware, but I have to admit that it is not quite good right now.)
Anyway, here is the firmware and config tool, and here is the source code.
Thank binzi for providing the hardware.
Comments
Fantastic, good to have you back. Is this for Mavlink 1.0?
Finally I have some time to update this work after defending my PhD thesis. Sorry for let you wait so long.
The firmware is still under alpha test, but you may try it as you wish.
Here you can download the new firmware and config tool. Please update both the firmware and charset.
http://code.google.com/p/hazys-osd/downloads/
Hi,
I tried the configuration with APM 2.5 and remzibi OSD 3DR. Hex file upload was successful and even Save to OSD was "successful" but I don`t get an OSD overlay and I can`d Read from OSD and I can`t upload firmware from the configuration tool. I assume there is no connection possible to the OSD and the save to osd was not really successful. I had no APM connected but I should anyway get an on screen message right?.
Any news hazy? I still can't get it to work with APM2, tried everything I can think of but still just get the waiting for heartbeats message, If I connect the 3DR telemetry radio to the same port the telemetry data goes through fine.
Hi everyone, sorry for my late response. I went to my home town and could not access internet there :(
To spagoziak: you may try programming the OSD using Remzibi's tool or any ISP tool. There may be something wrong in the bootloader or the connection.
To dmitry.chernov63: it is strange, I will check it later.
To Graham Dyer: are you using MAVLink 1.0 version in both APM2 and the OSD? I tested MAVLink 1.0 on APM2 and OSD, and it seemed to work properly before I left :). I will test again to check whether there is something changed.
Don't know what's changed (maybe Mavlink 0.9 > 1.0?) but this no longer works with APM2. Waits forever for heartbeats...
hazy, I hope you have some time to look at it (please:)), I really miss having my OSD.
Hello, hazy!
Thank you for great work!
One strange issue - I use "Altitude(Relative)". Before GPS lock it is zero, but after lock it "jumps" to ~60m (every time sightly different numbers). And I can't bring it to 0 by pressing Reset on APM or sending any command from Mission Planner.
In Mission Planner I see zero (if I switch to home altitude).
I use Config Tool 1.0.2.5, Firmware 1.02, APM1 with ArduPlane 2.50 (MAVLink 1.0)
How to get real relative altitude?
Please help me.
Thank you!
I also can't install firmware with OSDConfig, so I use Usbasp to program directly in chip. Most likelu something is wrong with bootloader. Configuration and fonts I can upload then with OSDConfig
Hazy,
I've tried following the instructions listed here (http://code.google.com/p/hazys-osd/wiki/Firmware) every way I can think of, but none are successful.
I am able to get OSDConfig to begin uploading for a very small moment--to 1%, then the status bar at the bottom says Program Failed.
Can you advise on what I am doing wrong?
Thank you,
spag
Ok, everything works in real life too very nice. Just made some little flight :)
-
1
-
2
-
3
-
4
-
5
of 9 Next