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
@Chris Kreuzer : you mean it doesnt work with Mavlink 1.0 and AP 2.6 right?
Your firmware doesnt work.. :-(
Well there's an officiel firmware for MAVlink 1.0 here : arducam-osd
My firmware could work, but not tested :)
When I'll have some time, I'll update the firmware with actual revision of the official code.
Ohh it doesnt work...
Can I use "ArduCAM_OSD.rssi.amp.status.hex" with ArduCopter 2.6 (MAVLINK 1.0)?
Well analog port will use this : 5 volts / 1024 units or 4.88 mV per unit.
So if max signal for you is 3.3v, max value will be 676 and it 100% signal, you should do the same for min signal value, and build your own function to display a percent (0% to 100%) according to the signal you receive
@airmamaf: Thank you for replying.
Can you explain more about the Percent_RSSI part? Mine is a Rangelink. RSSI out is 3.3v max. Cheers.
Minh
@NguyenHaMinh, yes it' correct.
But be careful, PERCENT_RSSI(x) function should be specific to your receiver, the above code is just for Turnigy 9x receiver.
I used pin 7 for RSSI, because I had a problem with pin 8, but maybe it's an arducopter problem, so you should have a try with pin 8 for arduplane.
Hi guys,
Noob question: Is the following procedure correct?
1. Update charset with the original Arducam and FW
2.Update ur FW
3.Add your above code to APM_Config.h, line 21
4.Add your above code to GCS_Mavlink.pde, line 412
5.Compile with022 relax patch and upload ArduPlane( my case) to APM 2.0
RSSI feed from my Rx would have to go into port 7 of the AMP 2.0 right?. Thank you for the code!
@AIRMAMAF
Great WORK!! Thanks!!