« previous next »
Pages: 1 [2]
*

vgwit

  • **
  • 96
Re: minOPOSD altitude setting
« Reply #15 on: August 16, 2018, 12:20:58 pm »
Thanks you guys,

at last got what I wanted except this one:

Quote from: f5soh on August 14, 2018, 08:52:46 pm
Quote
E XX.XX
Related to the remaining energy. Assumes you configure a Voltage/Current sensor connected to the Revo.

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?
Logged
*

f5soh

  • *****
  • 4572
    • LibrePilot
Re: minOPOSD altitude setting
« Reply #16 on: August 16, 2018, 12:28:12 pm »
Since you do not use a current sensor you should remove the "Battery percent" from OSD panel ?
Logged
*

f5soh

  • *****
  • 4572
    • LibrePilot
Re: minOPOSD altitude setting
« Reply #17 on: August 16, 2018, 01:05:30 pm »
Sorry, The E0.00 is linked with "Time" and shows the estimated remaining flight time.
Download and flash latest firmware from Wiki page and tell me if the "E0.00" issue is fixed.
Logged
*

vgwit

  • **
  • 96
Re: minOPOSD altitude setting
« Reply #18 on: August 16, 2018, 06:06:40 pm »
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.
« Last Edit: August 16, 2018, 06:52:03 pm by vgwit »
Logged
*

f5soh

  • *****
  • 4572
    • LibrePilot
Re: minOPOSD altitude setting
« Reply #19 on: August 16, 2018, 06:48:17 pm »
Do you talk about the "E0:00" one line bellow the Time value ?
Logged
*

vgwit

  • **
  • 96
Re: minOPOSD altitude setting
« Reply #20 on: August 16, 2018, 07:04:20 pm »
yes. Have attached a frame.
« Last Edit: August 16, 2018, 07:08:47 pm by vgwit »
Logged
*

f5soh

  • *****
  • 4572
    • LibrePilot
Re: minOPOSD altitude setting
« Reply #21 on: August 16, 2018, 07:45:07 pm »
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.
Logged
*

vgwit

  • **
  • 96
Re: minOPOSD altitude setting
« Reply #22 on: August 16, 2018, 08:20:53 pm »
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.
Logged
*

f5soh

  • *****
  • 4572
    • LibrePilot
Re: minOPOSD altitude setting
« Reply #23 on: August 16, 2018, 08:59:29 pm »
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.
Logged
*

f5soh

  • *****
  • 4572
    • LibrePilot
Re: minOPOSD altitude setting
« Reply #24 on: August 17, 2018, 12:09:35 am »
OSD firmware (170818) will support AirSpeed now.
Logged
*

vgwit

  • **
  • 96
Re: minOPOSD altitude setting
« Reply #25 on: August 17, 2018, 06:06:46 pm »
Sorry but with 170818 FW AirSpeed doesn't work. And RSSI stopped working in ...pin3 FW.
Logged
*

f5soh

  • *****
  • 4572
    • LibrePilot
Re: minOPOSD altitude setting
« Reply #26 on: August 17, 2018, 08:17:48 pm »
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

Logged
*

vgwit

  • **
  • 96
Re: minOPOSD altitude setting
« Reply #27 on: August 17, 2018, 08:47:25 pm »
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.
Logged
Pages: 1 [2]
« previous next »