Multiple profile support

[fujin]

I have ships (quadcopters) that are both 3S, 4S, sometimes with a variety of props on a given day.

I'd like to be able to autotune the powertrains individually and store them in banks as well as have a way to switch between them. Ideally this would extend to battery monitoring and stuff too.

[tracernz]

Yes. Auto-detect would be ideal.

[jpahka]

+1 on profiles, although I'd like to be able to change manually also, e.g. depending on if gimbal is onboard or not

[jhitesma]

My #1 wish is for profiles. But definitely with manual change. One my builds with profiles I like to setup one "tame" profile I can let noobs try, one with my preferred setup, and sometimes a third if I want to try something different but don't feel like lugging a laptop or a USB-OTG cable with me.

Personally I like stick commands for switching since I tend to bump switches accidentally, but I know some people would prefer switches.

[tracernz]

Ideally we could specify conditions for each profile, which could include stick pos, stick command, LiPo cells etc. The first profile matched would be selected, or a default one if none match? Stick command would be the odd case in that list, but I know plenty of people would desire that so it's probably worth special casing it.

[mlyle]

I think the first thing we need is just the ability to store multiple sets of configuration information. That is, valid multi-instance object serialization to flash. Then we can teach subsystems to use them.

[mluessi]

Yes, what we need is multi-instance settings UAVOs. Relevant TL issue: https://github.com/TauLabs/TauLabs/issues/614

[Malcurin]

I would love this on a acessory switch, Or even the auto detect muyself :)

[lolorc]

+1 I'm always the one with special use cases, atm I use mwrate as a way to have two rate profiles : rate and mwrate. mwrate has been removed from next iirc