OSD based menus for tuning, features, etc

cyber_06_wolf · April 6, 2020, 4:10pm

Hi developers, I have a question before I put in an enhancement request. In my mind the single biggest feature that makes inav attractive over ardupilot is the interactive OSD menu system. It is so convenient to be able to take off, fly a moment, land, change a setting, and take off again without having to bring out a laptop/tablet. Once a menu system is setup it would be trivial to add features to it, and with hardware with OSDs built in getting more and more popular I think it is a good path to pursue.

I think the logical way to implement this would be stick gestures, but I have read a couple times there are safety concerns with stick gestures on ardupilot since it uses throttle/yaw to arm.

I would like to work on/solicit help building an OSD menu system for ardupilot. I want to set some baseline rules and outline functionality before I post an enhancement or ask for people to help me spend time on it. If I were to start with stick gestures, is that doomed to never be implemented into master? I’ve thought about just using a dedicated RC channel to enable this menu but 90% of the time it would be a wasted channel(you couldn’t use it if the vehicle was armed).

My thought would be in the arming check file, add a parameter like “menu in use” so arming checks would fail if a menu is active, and even better arming requests aren’t even accepted while in a menu. To enter the menu there just needs to be a mutually exclusive window for throttle and entering a menu. i.e. throttle 0-15% for arm, throttle 40-60% for entering menu. If you require the throttle to always be above the arming window while menus are active, I don’t see any reason why this couldn’t be implemented in a safe manner. Of course osd menus could be disabled permanently by anyone who didn’t want them active.

Things I would definitely want in a menu system:
-PID values
-flight modes
-feature settings (smart audio vtx control in particular)

List of topics/requests for this kind of thing:

github.com/ArduPilot/ardupilot

Support SmartAudio VTX control protocol

opened 06:58AM - 21 Dec 18 UTC

closed 08:22AM - 17 Feb 21 UTC

macrokernel

Enhancement

Please implement support for the SmartAudio VTX control protocol to allow VTX po…wer level, band and channel programmatic selection. Many modern VTX models allow changing their configuration parameters via an additional wire connected to the FC TX pin. This nice feature is implemented in BetaFlight and iNav. There is a good description of how it can be used in the Oscar's blog: https://oscarliang.com/vtx-control/ I think that it would even better if the VTX power level could be changed on arming. For example, when the model is powered on, VTX is started with the minimal power level to prevent overheating. After arming the model, VTX power could be set to its maximum or another configured value. #### Platform [ ] All [ ] AntennaTracker [ * ] Copter [ * ] Plane [ * ] Rover [ * ] Submarine

github.com/ArduPilot/ardupilot

Support for quick tweaking (profiling) of some settings

opened 12:37PM - 26 Jul 17 UTC

SergeyBokhantsev

Enhancement AllVehicles

#### Issue details As many of another pilots I do have several batteries of dif…ferent capacity, weight, voltage etc. So for the one battery I want to use one settings (capacity, failsafe voltage, failsafe behavior, even PIDs) For the another one I must use different settings. Or as another example is when someone are using different props and alters them. So he must use different PIDs as well. It would be great to have a possibility to tweak some settings basing on the pre-configured profiles. Important point here is it must be doable without connecting to notebook/phone. It must be simple and quick to select the proper configuration right on a flight site. Technically one of the option could be: - have stored profiles on flash card. This could be a text file like: `{ Profile: 1, { ... settings to tweak ... } Profile: 2, { ... settings to tweak ... } }` - when vehicle is disarmed and some RC stick combination is pushed then profile 1 applied. That must be indicate by led, buzzer and mavlink message. Next time pushing that RC stick combination must apply next profile and so on. #### Platform [ x ] Copter

andyp1per · July 4, 2020, 10:12pm

vierfuffzig · July 4, 2020, 10:38pm

i‘d like to add that i‘ve been using the OSD param screen PR by @andyp1per for quite while on all my setups now, as it‘s an awesome addition i really don‘t want to miss anymore. thanks again andy, great job!