I have started to add functions to MinimOsd code.
At first i did it for myself only. Added many functions i thought i need. Then opened this thread.
after a while, Pedro and later Miguel came, and things started to happen fast. :D
They have optimised the code and added even more things to it.
They have worked hard on CT, and it became a great tool!
Thank you Bough! :)
By now MinimOSD-Extra got a pretty advanced OSD.
Here it is in action:
- Changeable unit measurement (US, metric)
- Home alt
- Battery Percent
- Battery used mah
- Current Draw
- Time From Startup (cleared at takeoff to show exact flight time)
- OSD Menu
- Wind horizontal speed and direction, and also the average wind speed of the last few minutes.
- OSD on/off
- Switchable secound screen
- WP distance
- WP heading
- Crosstrack error
- Warning messages for Lost GPS fix, Stall, Overspeed, battery volt, battery Percent, RSSI
- Efficiency, glide distance & thermic notifier. 3 in one panel
- OSD Brightness
- HAM Call Sign
- After flight summary
- Trip distance
- Smoothened horizon
- Real heading
- Vertical speed
This functions can be turned on and off, and placed on different screens now, by the Config. tool.
Also RSSI, switching mode and channel and unit measurement, Stall speed warning, Overspeed warning, Battery warning volt, Battery percent warning, RSSI warning, can be set in new Config Tool.
We built in a new way of setting video standards. Now OSD does not guessing anymore :). You can set it fixed from CT. It is in "Video Mode" menu.
Here is how it looks: (This video is a bit outdated, sorry. I will make a new one soon.)
The MinimOSD-Extra project is here: Link
This project is the developing version of the official Arducam OSD located here: Link
The latest stable version is: 2.2
The latest version can be downloaded from here: MinimOSD-Extra R800
CT is included. (The FW for Plane, Copter, Character upload and the character file is in the "FW & Char" directory inside CT directory)
We are sharing it to see videos you make using it! :)
Hi Motion Man,
Sorry for not replying earlier.
There are so many posts and this is not my job, you know? ;)
We're looking at the workaround that uses less space possible in fw.
It should come in next copter version.
Ahhm, maybe some confusion here. I'm asking about weird values on minimosd startup for RSSI ?
Are we on the same page ?
I know that possibility, thanks :)
For now we're just going to keep code.google to manage the source code.
We already have a place to put everything that may be downloaded.
Just need to be well organized.
I made a LOT of progress. Lookting at some of your messages to other people about the SR1_EXT_STAT, I looked at my Pixhawk and noticed that SR2 (for Telemetry 2) does NOT have a SR2_EXT_STAT setting.
So I decided to try an experiment. I disconnected my 3DR Radio from the Telemetry 1 port on the PixHawk, and connected the MinimumOSD using the Telemetry 1 port, instead of the Telemetry 2 port. Now I'm getting output data on the Minimum OSD! It seems to be working! :)
So it appears that the changes made to generate the 'Extra' versions of the minimumOSD are not compatible with the Telemetry2 port on the PixHawk.
I probably could use a 'Y' cable between the 3DR radio and the MinimumOSD using the Extra firmware by connecting to the Telemetry1 port.
Note that unless I read the documentation wrong, on the Pixhawk, they tell you to connect the MinimumOSD to the telemetry 2 port.
Would it be possible to debug this and get the 'Extra' firmware to work with the PixHawk on the Telemetry 2 port instead of the telemetry 1 port?
Thanks for your help!
Latest plane is the one in the first post of this thread (r780)
Hi Motion Man,
I believe we are on the same page :)
RSSI weird values are because of APM reported values that are outside the min and max setted on minimOSD.
We'll be releasing a fix so if below minimum just shows 0% and above max shows 100%
Thank you very much for your feedback.
In APM the key parameter is indeed SR0_EXTRA2.
I guess Pixhawk should have that SR2_EXT_STAT at least because it is documented on AC page.
Not being able to buy a Pixhawk and test it is !"&!%#$(#$"% ...
At least you managed a way to make it work :)
Making the "extra" work on telem 2 as base minimosd fw works can't be achieved as we don't have enough space to include it (there is a lot of stuff that doesn't exists in the base fw that we made for extra).
So we need to find a way to Pixhawk automatically send that SRx_EXTRA2 data via telem 2. Could you try setting all the SRx_EXTRA2 parameters you have to 5 and check if it works?
I'm still investigating. In the Pixhawk, I can see the parameters in the Mission Planner 'terminal CLI', but i can't see them in the 'config/all parameters', so perhaps this is a mission planner bug?
I'll do some more configuration and testing and see if I can find out what's going on.
Looking further, I can't see how to set SR2_EXTRA2. It can be displayed in the CLI, but not in the MP config all parameters.
I'll try to learn how to set this.
First, sorry for the out of order posts. I can't seem to find a proper 'reply' button to allow the replies to come into the proper location in the discussion!
I looked deeper and it seems I can't find a way to set the proper SR2 parameters. I'm guessing that this is a Mission Planner BUG.
Here are my current settings:
I can't find out how to edit all the SR2_ settings, especially the SR2_EXTRA_2
I can only display these settings in the CLI. I'll try to find a way to report this to the MP or RC2 team.
I'm replying here because I'm feeling the same difficulty as you show the reply in a order that makes sense :S
There you have it! :) SR1_EXT_STAT is set to 2
I guess that's why it is working via telem 1
Do you have any of the SR2 parameters available via "Full Parameters List"?