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
Yeah, I would run with linear.
Most all of the RSSI outputs I have seen from my equipment are jumpy and erratic like that, particularly the spread spectrum frequency hoppers.
Maybe run a 5 second floating average to smooth it up a bit?
Hmmm... George, it's kinda to much jumpy, but looks like it's "linear".
Not actually sure Sandro. If it helps, here is a video which displays raw RSSI voltage levels from a Dragonlink system from launch, out to about 5.7km. On the turn around it gets a bit erratic as electronics and battery get between Rx antenna an me. It may help you see how its scaled in the Rx.
https://vimeo.com/40007622
@Eugene, MinimOSD hardware v1.0 is full firmware compatible with the old version. It just has a revised power circuitry with a switching regulator for improved cooling.
@George, about the ChainlLink... I hope so. I need to finish my install. If it's just a matter of read that ~0.9 to ~3.3v... I would just want to know if it's linear already.
Got it... I'm worried on to know if it is linear or not. I mean, it would be nice if the RSSI voltage scale reflects a logarithmic based scale (dB) which would solve the problem of the non-linearity on the loss of power through the air.
Thanks by those infos on the 9X. And the microwave oven is a fantastic idea... =)
Hi Sandro, glad to see you're getting better, I get RSSI from my Turnigy 9x receiver as describe here RSSI from TGY 9x and I also made a simple rssi buffer.
About what just said George, it could be nice to have something in mission planner to calibrate RSSI, as we do for our radio, with for exemple max value (1m from receiver), min value (in microwave oven) and switch off value.
Also, looking at your Chainlink, to obtain an RSSI voltage should just be a case of looking at the voltage between the middle pin and grd pin of the connector next to the 'Com port' connector (labelled as "SPPM VRSSI GND" in the manual). You should just see a voltage range between about ~0.9v and ~3.3v?
Sandro, Just a note for scaling, nearly all radios will be different with respect to RSSI voltage values (from my experience) so maybe a tab in the set up page of mission planner requiring user to have radio on near plane for full signal sample, then switch Tx off for low signal sample. APM planner can then auto scale 0 - 100% giving the user an option to enter a margin value to their taste. ie A 10% margin value has the displayed RSSI reading 0% at 10% above Tx 'switched off' sample. Just thoughts anyway, glad your better too mate.
Does it support MiminOSD 1.0 hardware?