LibrePilot Forum
Users => Applications - FPV => Topic started by: vgwit on August 13, 2018, 08:13:39 am
-
Have upgraded from CC3D to Revo and GPS. Is there a way to have altitude in OSD from barometer? I've found Settings -> OsdSettings -> AltitudeSource that is set by default to GPS. Changed it to Baro but it seems not working. Is there another way?
Thanks.
-
The right way to configure the MinOPOSD is using the config tool, like described in Wiki page (https://librepilot.atlassian.net/wiki/spaces/LPDOC/pages/7274504/MinOPOSD+setup#MinOPOSDsetup-Panelsetup).
The OsdSettings UAVO refers to another OSD hardware, never released.
-
Thanks.
I use the config tool and want to see Home Altitude from telemetry via Flex-IO port on Revo. The question is which data I'll see? From GPS or barometer? Is it configurable?
-
Value is the same as the one displayed in PFD equal to the PositionState.Down UAVO.
Without GPS this value comes from baro
With GPS, the result is a mix between GPS and baro and give altitude above HomeLocation.
-
What I see is Home Altitide in miniOPOSD shows altitude above home location. But reads only GPS, not barometer (it isn't present at all until GPS lock) while PFD and PositionState.Down UAVO relies on baro. I'd prefer to see Home Altitide from barometer. How to get it?
-
Seems you are using the generic "All boards" MinOPOSD firmware.
Since you use a Revo you may need to flash one "Revo only" MinOPOSD firmware (https://librepilot.atlassian.net/wiki/spaces/LPDOC/pages/7274504/MinOPOSD+setup#MinOPOSDsetup-Downloadsdownloads) for Altitude based on PositionState.Down.
"Revo only" MinOPOSD firmware add also more warning alarms and travel distance.
-
Thank you. I'm flashed
LP_MicroKvteam_CC3D_analog_inputs300718.hex.
Will try
LP_All_From_Revo300718+AnalogRSSI_pin1.hex
and LP_All_From_Revo300718.hex
tonight.
-
Have tried other Revo firmware.
Some questions left:
- All_From_Revo300718 shows RSSI always 100% no matter what it is reality. I guess Revo get it from receiver. I use iA6b receiver and iBus on Flexi port. What I need to see real RSSI?
- All_From_Revo300718+AnalogRSSI_pin1 says about pin1. It is of what?
- Both firmware shows a parameter E XX.XX which I couldn't find in config tool. What is it?
-
shows RSSI always 100% no matter what it is reality.
Link quality, not related to RSSI (Received Signal Strength Indication) not send by receiver except if you are able to redirect the Rssi value to one receiver output in PPM/PWM : See last entry in Input tab.
AnalogRSSI_pin1
Pin1 in OSD (https://code.google.com/archive/p/minoposd/wikis/AnalogRSSI.wiki) pcb connected to the receiver output analog RSSI voltage, if any.
https://librepilot.atlassian.net/wiki/spaces/LPDOC/pages/7274504/MinOPOSD+setup#MinOPOSDsetup-Rssisetup
E XX.XX
Related to the remaining energy. Assumes you configure a Voltage/Current sensor connected to the Revo. (https://librepilot.atlassian.net/wiki/x/BQB2)
-
Thank you f5soh,
my receiver outputs analog RSSI and passes it to RSSI input of my micro minimOSD module. With firmware LP_MicroKvteam_CC3D_analog_inputs300718 I see it correctly. But with both Revo firmwares I do not see it, it shows either 0 or 100%. How can I solve this?
-
Download the archive from this post (https://forum.librepilot.org/index.php?topic=4369.msg29769#msg29769) and flash the LP_All_From_Revo300718+AnalogRSSI_MicroKvteam_pin3.hex
I didn't upload the right file to the wiki with latest update.
-
Thank you f5soh,
I'll try it tonight.
Not quite understand about RSSI from Revo:
Link quality, not related to RSSI
Manual says for All_From_Revo300718:
"RSSI information comes from link quality UAVO"
Why with this firmware I see in OSD 100% Link quality instead of RSSI? Is it possible to see RSSI?
-
Modern 2.4g receivers have Link Quality instead of RSSI. It doesn't do you any good to see a high RSSI when flying a long way away, just because you are flying over someone's wifi. You would need to know how high the RSSI of your packets is when compared to background noise.
You use Link Quality as if it were RSSI except that it will be close to 100% most of the time. When it is below 100% most of the time you should turn around, because you are probably at 90% of maximum distance. You can test to see if it changes by turning off the transmitter and it will drop to 0% if configured correctly.
-
Thank you Cliff,
it is clear now about difference. The only thing not clear in my case is what does it mean when OSD RSSI with All_From_Revo300718 firmware shows 100% with transmitter switched off.
-
This means receiver still sending a valid signal to the FC.
-
Thanks you guys,
at last got what I wanted except this one:
E XX.XX
Related to the remaining energy. Assumes you configure a Voltage/Current sensor connected to the Revo. (https://librepilot.atlassian.net/wiki/x/BQB2)
I's appeared in latest firmwares. I don't use current sensor and would like to hide this energy parameter. But it isn't present in Config tool. How to get rid of it?
-
Since you do not use a current sensor you should remove the "Battery percent" from OSD panel ?
-
Sorry, The E0.00 is linked with "Time" and shows the estimated remaining flight time.
Download and flash latest firmware from Wiki page (https://librepilot.atlassian.net/wiki/spaces/LPDOC/pages/7274504/MinOPOSD+setup#MinOPOSDsetup-Downloadsdownloads) and tell me if the "E0.00" issue is fixed.
-
Have tried both Revo160818. Same problem. E 0.00 is placed where battery voltage should be.
And it appears after switching from ComBridge to Telemetry.
-
Do you talk about the "E0:00" one line bellow the Time value ?
-
yes. Have attached a frame.
-
Maybe the battery module is running into the Revo, even if no sensor connected connected.
Look at PFD: if you see voltage/current, the battery module is enabled and estimated time computed.
-
Yes, I want to use Battery module and particularly Battery Current input. But not for current but for measuring other parameter (camera tilt angle). If I disable BatteryCurrent on ADC0 (or set it to Generic or any other setting) E0:00 goes away. But I'd like to use ADC0 for my purpose.
-
Sorry, i cannot support this special usage of current input for tilt angle in OSD...
If you define Adc as current input, this input is used by battery module.
You could at least use the Airspeed analog but Airspeed is not implemented in OSD.
-
OSD firmware (170818) will support AirSpeed now.
-
Sorry but with 170818 FW AirSpeed doesn't work. And RSSI stopped working in ...pin3 FW.
-
Strange...
I added more info about the config on boot screen and refreshed firmware files in Wiki.
I do not have hardware for analog Rssi but here the Rssi shows a floating input pin and airspeed works fine.
A small video (with some glitches...) showing the airspeed config
https://www.youtube.com/watch?v=iiAFkz37lyA
-
Finally got the positiv result :)
Have updated with your refreshed file (it appeared to be slightly bigger) and managed to get it working as expected.
Thank you very much.