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.1
We are sharing it to see videos you make using it! :)
A delay call inside the mavlink timer is not good, because it slow down the update of the screen. Andke has already reported a crash because I use a delay (on one of my first attempts to slow down the process).
the code you saw with the switch was in the pre-release. When I commit the code I will be changing the code to exactly what you proposed.
A delay call just won't work, the serial input stops working.
However I just did a form of the case, just gave it a few more times out of the loop, started with 10 and was too long. I'm still wating for the video to process so you csn see the results.
It seems like the code could be made to be a subroutine, so all 4 cases could use it and save memory, but wanted to test it first.
The Rssi is working good, so when it is released in the apm firmware everyone can enjoy it.
If a few brave souls want it I can supply the HEX file for both the apm2 and apm1.
The switch was only a test method. The implementation with the "if" is already in the stable release and is working good.
With all the information people wish (I see requests for WP and RSSI), we must admit that the MAX7456 is not good enough in the long run - the more you display, the more cluttered the screen gets - and - we are completely missing analog indicators, and the increased readability they provide.
For really cool graphics, and audio warnings - take a look at this project;
Fortunately it's open source too - it would be sweet to make that read mavlink...
the openpilot osd is super great!
In the mean time, to resolve cluttered data, selectable panels will be added. So, the user can switch between different panel layouts for the different fligth phases. At least it will be possible to select 3 different panels.
I combined Burt's and my changes to the setup panel last night and also rewrote the warnings panel this afternoon. I've put the changes in the pre-release files. Can someone check them out and have a play to make sure they are user friendly.
The project came alive!
I think that i will just sit back and listen a bit. :)
All the committers have really good ideas, it is good to see them working on this.
Can't wait to see the result! :)
I think this little team will make MinimOSD the best OSD! :)
I think the same :)
For some reason I still can't get into the OSD menu.
I had the problem with 1.28 but I think Gabor found a bug and fixed it, but I have also tried 1.29.1 and 1.29.2 and still no menu appears.
I am switching between Manual and Stab modes, but I have also tried Stab and FBWA modes. I have also tried OSD reset, but this makes no difference. I am trying within 60 secs of APM boot.
Did anything change in the way you access the setup menu?
The only thing I can think of different on my MimimOSD to most is that I am powering both sides of the unit (logic and video) from the APM 5v input, but I can't see how this would affect the software logic?
Despite this I think the Minim-Extra software is a great piece of work and despite the lack of menu, if I turn warnings off in the config I can still use it, and it is a great improvement over the original software.
Thanks to all of you who are putting in the hard work.
-no recent change in method.
-power source cannot influence this.
- Do you see the indicated flight mode change on OSD ? (do you see the text change ?)
- it is important that OSD actually shows f.eks manu-stab-manu - if you switch too quickly, it won't "get" the change. it needs to see 1-2-1 - the whole sequence.
-finally : its not 60 sec after apm boot, but osd boot - reset osd, then toggle mode once it displays data.
Thanks for your help.
I've just tried it all again with 1.29.1 installed. I do see the mode text on the OSD change and I've tried switching (MANU->STAB->MANU) as quickly as the OSD can recognise, but still no success.
I've tried as soon as the OSD starts to show mode information, but also tried leaving it longer in case there was some functions still booting.
I need to head to bed, but tomorrow I'll try a few roll-back versions of the firmware and see if any of them let me get into the menu successfully.