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 came, and things started to happen fast. :D
He optimised the code and added even more things to it.
He worked hard on CT, and it became a great tool!
Thank you Pedro! :)
Also Burt & Eddie came.
They also worked on it and added many smart things to our firmware.
By now MinimOSD-Extra got a pretty advanced OSD.
Here it is in action:
- Changeable unit measurement (US, metric)
- Home alt
- Battery Percent
- Current Draw
- Time From Startup (Will be cleared at takeoff to show exact flight time in the next release)
- OSD Menu
- Wind horizontal speed and direction, and also vertical wind speed (Vertical wind speed will be in next release)
- OSD on/off
- Switchable secound screen
- WP distance
- WP heading
- Warning messages for Lost GPS fix, Stall, Overspeed, battery volt, battery Percent, RSSI
- Efficiency, glide distance & thermic notifier. 3 in one panel (Will be in next release)
- OSD Brightness (Will be in next release)
- HAM Call Sign (Will be in next release)
- After flight summary (Will be in next release)
- Trip distance (Will be in next release)
- Temperature (Will be in next release)
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.)
About the menu:
I made a menu inside OSD. You can enter this menu only after boot, the same way as screen switching works.
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! :)
Can't wait to see your todays video! ;)
Today flight video with ArduPlane v.2.70 and firmware r462 MinimOSD extra.
Please, don't make me give up on quadcopters! :P
Great videos, thks.
YW. I tried to chase the train which went there, that it is why I tried to fly fast (around 102 km/h ground speed) with 80% throttle. I never was that far yet. 1,2 km far from home. So still discovering, I'm learning and tunning new things every day to get this system more reliable. It was from one village to other near city. Recently exchanged HK Orange Open LRS RX antenna with own created "sander style". It helped, it never triggered fail safe during the flight even flew farer and faster in comparison with stock HK RX antenna. I'm still tunning APM, stabilization does not work for me somehow so well. I need to learn what to do. Looks to me that first I need to tune the flying wing without use of APM. And then to try to tune APM. I am still somewhere in middle in this. Will read more and will try. Still working on better reliability of RC link and will tune RSSI with filter at least or maybe op-amp and will find out what will work best. And also going to select right UHF carrier RC control frequency for optimal performance and longer range reliability. Also will try "turn style" antenna on RX in the future. I like pan and tilt camera possibility, but with 5.8 ghz antenna on head it is not optimal. Since every time you turn with head, it could break video. But it is fun anyway. Doing things step by step. Aslo needed is to tune layout of components and embed them inside into the flying wing. Eg. to put batteries inside. Also to select optimal positions for VTX, RX, GPS and embed cables into the flying wing. But I just take time to find out and to tune things.
"I tried to chase the train" - Wow! I didn't realised that it was the same place from the previous video. There was much more white color before than now :) Nice train persuit! (102Km/h FPV ... wow)
"Looks to me that first I need to tune the flying wing without use of APM" - I agree with you. That's what I make allways. My RC instructor used to say: "If it doesn't fly well, don't use trims or radio mixs, tune the mechanics" For example, if a servo travels more than it should I change servo/control horn hole position. If elevator is not visually centered, I rotate the clevis to reduce/increase link length. Also tune CG in all 3 axis. Only then, I trim with radio.
This way, planes almost fly with any input (UAV without controller? Free flight airplane? :P ).
"I like pan and tilt camera possibility, but with 5.8 ghz antenna on head it is not optimal." -
I use a camera tripod, and connect the googles to tripod by wire (I use a toroid on the wire to reduce interferece). Pan and tilt improves our position and altitude awareness, so it is great.
Wish you a nice tunning process!
Saturday I was able to test MinimOSD Extra 2.1.5 Copter Pre Release Version r479.
To keep my notebook inside my car, I had my video receiver antenna near my car (<1m).
Worst decision ever: I thought I knew what multipath interference was...
( please don't look at the video too much time :S )
So, temperature is ok.
Vertical Landing Aid seems to be ok.
Efficiency has to have a little more copter custom work.
The line at center screen looks like home position from radar view. I think it could be also useful function for planes.
That line is a "Vertical Landing Aid". It only shows the ground height relative to the copter (center of screen).
It's intended to be a copter aid for smooth landings.
Radar would be cool, but IMHO it would consume extreme memory (code and charset) to be implement with a minimum acceptable resolution.
Anyway thank you very much for the tip.
Why do you think it should take extreme memory?
Not sure if I understand all aspects, but from my point of view it should be about calculation of the position on screen and to display some character there. Am I missing something here? It could be nice to see there also way points. It would be really great for navigation.
The problem is that we can't send/write "pixel position". We only can send/write "character position". So, if you want to have pixel resolution in a "radar panel" you'll need to have 120 custom characters in charset memmory (if my own memmory isn't failing :) a character os 10x12 pixels. It is a big resources taken.If anyone has a good workaround for this it will be much appreciated.
I think it does not need to be pixel precise position, although it could be better, just rought way where to go displayed radar way could be useful or nice.
What do you think would be a good range for the radar?
What heading should it point (north, curren heading...)?
I will add it to my "wish list" ;)
First I need to improve the code memory usage to fit new features.