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:
Added:
- Changeable unit measurement (US, metric)
- Airspeed
- Home alt
- Battery Percent
- Battery used mah
- Current Draw
- Time From Startup (cleared at takeoff to show exact flight time)
- OSD Menu
- Variometer
- 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
- Temperature
- Smoothened horizon
- Real heading
- RSSI
- 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
Username: MinimOSD_Extra
Password: Top_Secret
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! :)
Enjoy
Replies
Guys, can i use my old 2.4 customized chartset with the latest firmware?
Hi Zubair,
Differences between 2.4.0.0 and 2.4.0.1 charsets are only for plane version.
Those are chars 0xb0 and 0xb1 that are now being used in plane version (tune panel) to show sign before altitude error and air speed error reported by APM nav controller.
I'm planning to include this in copter in next pre-release.
The rest of the chars are the same.
Miguel
Ok. I am using a plane version so i have to use the 2.4.0.1? Or i can still use 2.4.0.0?
Hi Zubair,
If you are using Tune panel then you should move to charset 2.4.0.1 (just to show those 2 signs correctly).
If not you may keep using 2.4.0.0
Miguel
Hey Miguel,
I may have missed it, apologies... can you detail what the Tune panel is doing for me?
I find it very useful, especially on today's mission with a large number of altitude changes in mountainous terrain. I wish I could separate the two items so airspeed error can be near the airspeed and the alt error would be by the altitude. Actually I would just turn the airspeed part off. Copter doesn't need that anyway.
Gabor & Miguel, can we do that?
Ah, that makes sense, thanks Iam!
Gladly Miguel antd thank you again!!!!
Hi guys,
First of all, THANK YOU for keep adding extra functionality to the ArduCAM FW.
I got my minimOSD board last week (new guy to FPV!) and in a search for "the best FW" for the board I came across the minimosd-extra.
I truly appreciate all the work everyone has done on it although I have a small number of constructive critics (please take them as ideas that could help make things even better).
First, why SVN? Git is much better! It's like choosing between a rock and an hammer to hit nails.
Then the SVN organization: a bit messy! There are 4 different "base releases" (?) and then 3 "alternative" ones. The features of each one are not clear (at least for me) except the obvious ones (...copter...beta) and (...plane...beta).
The Tools folder is also a little unorganized with the CT Tool scattered in at least 2 or 3 different places.
Also, I don't think that it was a good idea to split plane/copter in two different folders with 90% of the same code... in my opinion it could be better handled with a simple #define statement and enclose plane/copter dependent code in #ifdef's.
In summary: It works, its cool and I hope I can contribute to improve the great job already done!
Anyway... my hobby during this last weekend was to get your latest SVN and work on my "alternate" minimOSD firmware. I got things a little cleanup (to my taste) and I plan to keep improving it (already done some of the stuff I suggested above). Feel free to get any of the ideas or code I modified (its GPL3 anyway...).
I placed "my" minimOSD at: https://github.com/ljalves/minimosd-ng
For other people willing to contribute to it, pull requests are welcome!
Again, thanks for all the hard work done so far and I hope to see it getting better!
:D
One weekend?
it took us like 2 years.... :D
It is nice to have a professional coder here!
Thx,
Gábor
-
66
-
67
-
68
-
69
-
70
of 163 Next