OpenHD
OSD Enhancements
Just trying to stay organised
-FPV boresight (locked) option....................................................................................................done -inav home arrow broken.....................................................................fix committed....needs testing -No difference between ground and air pi icons..........................................................................done -upper and lower bar behavior in response to arm and user selection........................................done -rc control input indicator......................................................................................version 2........ done -vibration widget..........................................................................................................................done -3d wireframe model.....................................................................................................................wip -total distance flown.....................................................................................................................done -total mah flown...........................................................................................................................done -mah widget default placement...................................................................................................done -total distance default placement................................................................................................done -control input display default placement......................................................................................done -warning when armed and no homeposition.................................................................................done -some widgets missing glow.........................................................................................................done -controls display inputs that are bound by square rather than depicted circle............................ignore -vertical speed gauge....................................................................................................................done -Ladders-speed-alt-compass-attitude...........................................................................................done -attitude pitch lines....................................................................................................................... done -"range" options in speed alt heading ladders..............................................................................done -battery show volt amps...............................................................................................................done -experiment with high wind detection (maybe also download wind)... initial support ..................done -wind in km or mph......................................................................................................................done -wind for planes...........................................................................................................................done -rssi breakout requested...............................................................................................................done -imperial/metric broken in many places........................................................................................done -ahi size........................................................................................................................................done -controls- reverse options.............................................................................................................done -single control- square for one stick..............................................................................................done -fix home position........................................................................................................................done -rssi for regular rc.......................................................................................................................done -temperature v1...........................................................................................................................done -bank angle indicator......................................................................................................................done -home distance has "..." after digits........was bug caused by lat lon 0,0........................................done -resize option on more widgets..................................................................................................done -Color request for 55,155,255 (blue)...did basic blue.................................................................done -vibration widget sensitivity -flight path vector conformal and non-conformal modes -horizon ladder needs clipping/mask...maybe....maybe not.. kinda like the current look -info/tooltips for osd widgets -telemetry/osd animation tweening -battery popup missing horizontal line -battery volts show one more decimal point -wind rolling average -wind accuracy estimate -rolling average for card stats -post flight report -declutter options -warning, caution, normal, color themes -determine vehicle type from telemetry (then osd can configure for special cases) -change glyph by flight mode per vehicle type -horizon ladder needs more size option
Map Specific -trails on past drone movement.....................................................................................................................................done -mini map doesnt display settings popup......................................................................................................................done -wind map integration -large map settings popup can only be closed by clicking "x" which closes that map -maps keep defaulting to streets rather than satelite or last map -display mission waypoints -mini map detail popup appears on top of map -map goes out of position on app resize of window (desktop) -decrease mini map to just an icon
Looked at issue for "home distance has "..." after digits" . its tied to conversion of the number to a qt local regional string right in the widget form qml file .. So it might be different depending on your regional install of qt
Edit: this turned out to be a bug from intial home being 0,0
Future ideas for ladders:
-range can be easily broken out into the popups on all ladders.......................................................................................done -speed popup can have aircraft setting to show the squares at a desired min speed (like a stall point)......................... done -compass ladder is a bit bare. could use numbers or ese, ene, wsw, etc..........................................................................done -glow is not implimented on ladders...................................................................................................................................done
-predictive trend arrows can be another popup option for speed and alt
ADS-B improvements -traffic limited by number of markers displayed- 20 is default right now...........................................................................done -api request frequency- 15 seconds currently...................................................................................................................done -ring for effective display area...........................................................................................................................................done -off/on adsb master control...............................................................................................................................................done -setting for max markers...................................................................................................................................................done -alert for traffic within x distance and y alt... similar to tcas.. thinking yellow ring then red ring....................................... done -map rotation and aircraft marker direction.......................................................................................................................done -adsb status indicator light"...............................................................................................................................................done -need handleing for onstart coordinates. they dont populate until map moves................................................................done -audible "traffic “ -ring doesnt disappear when adsb is disabled -ring not consitent looking between map providers.... wip... it’s better now.... -markers dont position exactly (evident upon zoom) -markers get drawn then rotated.. problem is visible when map is NOT oriented north
A new class of model data that we just call "blackbox"
It will keep appending blackbox objects to the model- -once every second -object has lat lon.......................................................................................................done -heading......................................................................................................................done -altitude.......................................................................................................................done -speed.........................................................................................................................done -battery data................................................................................................................done -pi loads/temps............................................................................................................done -rssi down/up...............................................................................................................done
will add more params... -home arrow................................................................................................................done -home distance...........................................................................................................done -home lat lon...............................................................................................................done -mah...........................................................................................................................done -msl alt -airspeed....................................................................................................................done -throttle.......................................................................................................................done -rc inputs....................................................................................................................done
With this data we can draw the trails very easily (just a polyline that keeps getting appended), postflight report, and find my drone functions...
-play button .............................................................................................................done -slider needs to get model rows to define ................................................................done -indicate which blackbox model ...............................................................................done -button to un pause telemetry and restart blackbox after viewing ...........................done -make model persist/saveable -add different playback speed buttons -prevent blackbox playback while armed=true
Battery/energy consumption
This will be my next big push after knocking out some other stuff.. Just trying to put some ideas on "paper"
-more configuration options are needed for battery- available mah and minimum safe voltage. This should allow support for batteries with different chemestry. Also options to base battery warnings on volts or mah (need to look into... might not be good idea) Or some hybrid of both. Battery sag is a real issue
-live efficiency display- distance traveled/mah consumed x time - this can be interesting to determine max endurance, most efficient speed, etc
-calculate a zero wind point of no return based on energy consumption
-integrate point of no return onto map- first will be zero wind and a simple circle. Later wind can be added and to a method to plot it on map will have to be found. Perhaps spokes from drone position with length being estimated max range. The ends of the spokes can be connected with a polyline which with wind should generate and oval type of shape for the estimated range of the drone...
-To do all this some calculations will need to be done and data gathered (good basis below to calculate energy needed) -Read parameters for RTL altitudes, climb rates, descent rates, and cruise speeds -Read new parameters for climb MAH, cruise MAH, descent MAH. and desired % remaining on landing -Calculate distance, time, and MAH required to climb up to RTL altitude (skip if FS is land only) -Calculate distance, time, and MAH required to cruise home (skip if FS is land only) -Calculate distance, time, and MAH required to descend to a landing -Sum total MAH required to RTL + % Battery remaining on landing = new live battery failsafe MAH point.
Parameters to make this all work (copied elsewhere) BATT_FS_RESERVE is the % remaining the copter will have when it lands, or at least close to it anyway. BATT_FS_CURR_CLM is the MAH rate used in a climb BATT_FS_CURR_DES is the MAH rate used in a descent BATT_FS_CURR_CRS is the MAH rare used in cruise
-battery alarms
-battery popup missing horizontal line
-battery volts show one more decimal point