Renaming inputs for Deviation

In order to support the Devo12 properly, and to better handle the Devo7e, I am about to rename all of the switches in Deviation. Basically all switches will be handled like the MIX and FMODE 3-way switches:
AIL_DR will become AIL_DR0 and AIL_DR1 (and AIL_DR2 on the Devo12)

This will also make it easier for folks who want to reverse the meaning of switches in Deviation (where 'down' is off)

I thought I had this sorted, but the more I think about it the less convinced I am, so I'd like some feedbck on the following options to enable compatibility across radios:

Should a 2-position switch's "On" position map to the middle position or far position on a radio where that same switch has 3 positions?

Example:The arrow directions are important. We need to be able to map both from devo8 to devo12 and from devo12 to devo8. (The same applies to the 6, 7e and 10 of course)

Note that I have a goal of having the same model file work in all radios, so I don't really have a good technical solution to the last option. That is because it probably implies you have a mapping table from each radio to each other radio which is not maintainable. If this option is really the best, I'll probably need to name 2-position and 3-position switches differently in the model.ini file.

If we choose (2) the names in Devo8/10 is there a concern about naming the switches in the Devo8/10 interface 'AIL_DR2' instead of 'AIL_DR1'? That would make coding easier, but maybe confusing to users who may wonder where 'AIL_DR1' went.

Anyhow, I'm open to feedback on this before I go and actually implement the change.

I agree that (1) is more easy for understanding.

At any case config for Devo 12 will be not workable at Devo 8 and will require modification. It's merely question how to translate Devo 12 config in Devo8 and that would be easy to understand and modify.

Agreed that in most cases a devo12 config will not 'just work' in a devo8. but it should preserve as much functionality as possible so that it is easy to get working on that Tx.

Regardless of solution, all switches will work like the 'FMODE' and 'MIX' switches. You can invert any switch. so you can do 'NOT AIL_DR0' which on a devo8 will be identical to 'AIL_DR1' but would mean 'AIL_DR1 or AIL_DR2' on a Devo12

One thing we could do would be to pop up a dialog whenever we detect a model that was not created for the user's Tx. At least it would give a heads up to fix the model after import. The dialog would only appear once per model (as soon as you save the model, it is now 'for your tx'

I agree with Hex, that it should be the number (1), but without the DR2 linked back.

Explanation:
The (1) is better then the (2), because if we use scheme (2), then a good working DEVO 8 config would cause an empty mid state on the DEVO 12, which is barely usable. It would be an invalid state, and you have to switch throw that to get to the other valid state. No good.

However in the scheme (1), if you assign both DR1 and DR2 to the same DR1 state, it would be again an invalid config, because there might be two contradictory state both on.

So I think it would be better to drop the DR2 state.
But how?
They should be assigned to a new constant FALSE switch.

Yep, I would like this way too...

BTW the DEVO 12 is a good example, that the model config compatibility would need some more tricks, like the virtual switch assignments, discussed in an other thread:
www.deviationtx.com/forum/3-feedback-que...es?limitstart=0#4870

That way a model config (and even more a template) could use a "virtual thottle hold switch", which everybody could assign to that real switch he want to use for that function...

I think what will be with complex mixer (3 pages) after conwersion from Devo 12 to devo8:

Devo 12
AIL_DR0 - AIL_DR1 - AIL_DR2

Devo 8
(*) AIL_DR0 - AIL_DR1 - None???
(1) AIL_DR0 - AIL_DR1 - AIL_DR1
(2) AIL_DR0 - AIL_DR1 - AIL_DR1
(3) AIL_DR0 - AIL_DR1 - None???

I think will be better replace/mark all inconvertible switches with red FALSE and value 0 ('false'). At such case pop up warning dialog in time of loading model file.