-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please add support for showing elevation above terrain #8
Comments
It would be easier for people to understand what is being requested and motivation, if there was an explanation about it here. So, is this gonna be used to debug terrain following? |
Fair question: my plan was to use it for both
Because space is limited, I can see how I would only use 2 altitudes instead of 3: Heigh Above Takeoff Point and Height Above Terrain. I could drop absolute altitude, although if I can have all 3, even better :) |
+1, this would be excellent. Like a poor man's Radio Altimeter. Well, not really, but it can certainly help situational awareness to know your height above the ground below you. |
HI, I am wondering why we don't try the other new boards which can work with the MinimOSD extra, they have plenty of space to add tones of features. |
Hi Elios007, can you give me a hint, which boards are compatible to minimOSD but with more RAM? |
Hi Lechuck, I thought that witespy micro minimOSD has more memory, but it seems it is the same. |
Yeah there are so many out there. |
@Elios007 @LeChuck71 I was looking at this again. Of course, I cannot use any of the extra pins for direct measuring of bat and bat2. Not super useful if ardupilot will do it for me, but the point is that I'm hopeful there are boards out there that have more RAM and will allow continuing development of minimOSD instead of being stuck here due to lack of RAM. |
Another interesting board: https://github.com/Brotronics/MinimOSD_MK2 |
https://groups.google.com/forum/#!msg/drones-discuss/abJ9fhBbpV0/XUc46rdy2uwJ
Tridge says
"It would be good if the OSD also displayed
TERRAIN_REPORT.current_height, so OSD uses know their terrain
height. That value is available even if you are not following the
terrain."
The text was updated successfully, but these errors were encountered: