LibrePilot Forum
Users => Applications - FPV => Topic started by: Zrisst on November 25, 2015, 11:08:16 am
-
I'm waiting to receive a MinimOSD board.
Surfing the web I found some things, but... do you have a good tutorial about configuring MinimOSD for Revo?
Thank you in advance.
-
Maybe here ?
https://librepilot.atlassian.net/wiki/display/LPDOC/MinOPOSD+setup
-
Thanks a lot Laurent...
The LP documentation is excellent (I should took a look there before posting. Sorry).
:)
-
Surfing I founded various config software for programming MiniOSD with different fields.
https://code.google.com/p/minimosd-extra/downloads/list
Loos like a newer version of the one you linked
https://code.google.com/p/arducam-osd/downloads/list
Diferent one with different HUD options
May I use any of them? Is the .HEX file for tuning for Revo limited to the linked OSDConfig version?
Thanks!
-
May I use any of them? Is the .HEX file for tuning for Revo limited to the linked OSDConfig version?
Thanks!
There are for sure many variations of firmware for minimosd supporting telemetry protocol either UavTalk or Mavlink. If you pick firmware, it must talk Uavtalk to work with LibrePilot.
Also the uav objects it sends must be up to date with the current flight controller firmware, such that minimosd understands what that means and can display it.
I am not aware of other OSDs firmwares that can do UavTalk, maybe PlayUAVOSD will as they have some UavTalk code in the repo, but for my current builds I use microosd and the minimoposd from the link f5soh provided.
-
May I use any of them? Is the .HEX file for tuning for Revo limited to the linked OSDConfig version?
Thanks!
There are for sure many variations of firmware for minimosd supporting telemetry protocol either UavTalk or Mavlink. If you pick firmware, it must talk Uavtalk to work with LibrePilot.
Also the uav objects it sends must be up to date with the current flight controller firmware, such that minimosd understands what that means and can display it.
I am not aware of other OSDs firmwares that can do UavTalk, maybe PlayUAVOSD will as they have some UavTalk code in the repo, but for my current builds I use microosd and the minimoposd from the link f5soh provided.
Thanks. I'll start using the one linked by f5soh then.
-
For uavo and config tool compatibility you should use all files available in wiki page.
-
New here, first post.
I have been trying to get my OSD to read battery voltage. I have followed the instructions given in libreOSD. I can get it to work fine except the voltage, when I plug the battery in the OSD boots and the volts count down to zero. I have the battery connected to battery one or 2 on the OSD, same resulst. This is using LP_MicroKvteam_CC3D_analog_inputs2810.hex with the recommended character set. If I use the other HEX file LP_MinimOSD_CC3D_analog_inputs2810.hex then the volts count up and stop at 17.09 volts no mater what the battery voltage is. I have tried this with a regular OSD and a mini OSD board. I am using a CC3D board with OP 15.2.2. I know they are communicating with the CC3D because the horizon is working. Any help would be deeply appreciated.
Thank You Carlos
-
My OSD did the same thing " count down to zero". I had Batt 1 displayed. I connected power to Batt 2 without changing anything in screen setup and now it works. I however cannot get any data from my CC3D, like horizon,pitch angle, armed/disarmed, ect.
UPDATE: Got this function to work!! Changed CC3D port to Telemetry @ 57600 baud rate, saved and cycled power to board.
-
So are you powering both bat 1 and bat2 at the same time. I get horizon have not tried other information. will try and report back. Thanks for your comment.
-
Got horizon and battery voltage working, all I really care for. Using battery 2 connection.
-
How did you get your battery to work??
All of the telemetry from the CC3D works but the battery is like it is not connected.
I am at a loss currently.
thanks
Update: After getting all the software updated correctly and moving the battery input over to Battery 2 everything Works. So Battery 1 is the wrong input for Libre Pilot.
-
How did you get your battery to work??
All of the telemetry from the CC3D works but the battery is like it is not connected.
I am at a loss currently.
thanks
Update: After getting all the software updated correctly and moving the battery input over to Battery 2 everything Works. So Battery 1 is the wrong input for Libre Pilot.
battery 2 is the default one to use anyway. has nothing to do with libre since the battery is connected straight to the osd.
-
This Batt 1/Batt 2 issue seems to be common. Not sure if it is an error in the firmware or what. If your OSD is setup to display Batt 1 then you should connect power to Batt 2 and it will work.
-
I think it's how it was compiled as to what is where...and actually, I really didn't see an option for the fpv battery, just references to the flight pack and which pins to put it on.
in my case:
#define VOLTAGE_PIN A0
#define CURRENT_PIN A1
(http://cdn3.volusion.com/tcfyn.cheun/v/vspfiles/photos/minimOSD-4.jpg)
-
I think he was talking about Micro MinimOSD. I has a Batt 1 and a Batt 2 pin. In the setup if you want to display Batt A voltage, then connect battery voltage to Batt 1 pin on the board, the voltage counts down to zero just after boot. If you remove power from Batt 1 pin and attach it to Batt 2 pin, without changing anything in the display setup, it will display correctly. Don't know why this is, but I have read about several people having this problem.
-
HELP! I'm a MAC user. I have been trying to flash a mini OSD with firmware. Thus far I've been unable to solve the problem. Can anyone do it for me? I'm using a Revolution Mini flight board. I'm open to suggestions.