Firmware and Windows Client are made from a modified version of the orginal one found here : arducam-osd
Update 30 January 2013, new version include :
- Possibility to choose what parameter to tune with CH6
To enable this feature and display selectable parameter screen (screen 1) :
- motors must be disarmed
- CH7 switch is engaged
- Full throttle and full pitch
After you'll we see a check screen (screen 2) where you have to :
- Put throttle in low position
- Put pitch in middle position
- Put CH6 in middle position
Then you can select parameter (screen 3) to tune with CH6, those parameters are :
- STABILIZE_KP
- RATE_KP
- RATE_KI
- LOITER_KP
- LOITER_RATE_KP
- LOITER_RATE_KI
- NAV_KP
- NAV_KI
- Move pitch stick to move between parameter list
- Select with full throttle a parameter to be tune with CH6
- Quit screen and start tuning the selected paramter with CH7 switchin off position
After tuning a paramter, go back to screen 3, and save new parameter value with yaw stick to the left.
Compiled firmware : 20130129_ArduCAM_OSD_.rssi.time.status.climb.current.tuning.mavlink1.0.hex
Firmware sources : Arducam_osd_src.zip
Update 16 August 2012, new version include :
- Mavlink 1.0 support
- Flying time (count when throttle is above 20%)
Compiled firmware : ArduCAM_OSD_.rssi.time.status.mavlink1.0.hex
Firmware sources : Arducam_osd_src.zip
Windows client sources : OSD_IDE.zip
Update 23 May 2012, new version include :
- RSSI Display
- T° display (maybe useless :) )
- Climb rate
- Armed / Disarmed status (with Flight Mode)
- Speed in km/h
- No more "Charset update"
- Battery remaining (not tested)
"Charset update" was removed hardcoded, so to upload a new charset, you'll have to use the orginal firmware to do it and after you can use this firmware.
This new version need a new charset (MinimOSD_20.mcm) and the new client
Firmware : ArduCAM_OSD.rssi.amp.status.hex
Client : OSD_Config_RSSI_Status_Amp.exe
Charset : MinimOSD_20.mcm
Comments
Hi animamaf,
yes with the original firmware it's acting the same, with TX connected is working fine, with it disconnected all the alues are 0.
Do you have TX connected ?
sorry I don't have a clue. I suppose symptom is the same with the original firmware ?
I don't think you understood what my problem is. The MinimOSD is working ok if I have the TX wire connected, I used it for a month or two like this , with all 4 wires connected. But recently I received the 3DR Radios and I have removed the TX wire to minimOSD, as the wiki says, only connected the TX to the radio, since than the values on my OSD are not updated, only the mode (ACRO, STAB, ALTH.. etc) is changing and after I arm the APM2 also the battery voltage is displayed, but other values are all 0.
As you can see in the picture bellow, the brown wire is temporary connected to minimOSD, this way the OSD is working as it should, but if that wire is connected to my radio instead I'm having the problems I wrote above.
Any ideea ?
It's not a new firmware, it's just functionality added to the current one (MinimOSD_19_MAV10.hex)
So to make it working, you have to follow those recommandations : How_to_start_minim
I just tried it now and I have the same issue as Gabor's firmware, the OSD values are not changing if the TX is removed from MinimOSD, everything is 0, only the mode changes.
If I connect the TX wire it's all good, the values start to update ~4 seconds I power up the system, but as I read in the wiki, if I also use a telemetry radio I have to remove TX from minim.
Do you guys use both minimOSD and a Radio ?
Thank you, I will try it now. I also tryed Gabor's firmware and I can't use it well with a 3DR radio connected also. It works great if I connect the TX to MinimOSD but if I remove the TX it doesn't work.
Today update for Mavlink 1.0
ArduCAM_OSD_.rssi.time.status.mavlink1.0.hex
Arducam_osd_src.zip
And the other firmware is here :
adding-extra-functions-to-minimosd
no it does not work with mavlink 1.0 but there is another firmware here somwhere for the OSD (not the standard one) that has many features, just look for it, it can for example disable the OSD, change between US and metric symbols and something... I really recommend it
does this firmware works with curent MAVLink protocol 1.0? because I see on the screen "Waiting for mavlink heartbeats"
Things I forgot in the last message, on the APM2 it uses the pin that is labeled here
http://code.google.com/p/ardupilot-mega/wiki/APM2board
Go down about a page and a picture shows it.
On the APM1 there is a set of pins on the oil pan labeled "Expansion Ports". The signal pin of A7 is where the change above will read it.
Another note, the Manlink message only sends a byte, the Input from the APM is a 16 bit, I subtract 4 from whatever value it gets, then div by 4. This should give a value less then 255. On the OSD side values will be from 0 to 255, 0 being 0 volts and 255 being about 5 volts. On my TSLRS recevier, I get from 51 good RSSI to 25 for transmitter turned off.
Later
Burt