Channel reorder testing

yes but how do you deal with all those uncommon use cases just now? do it manually of course, and i think it's not an unreasonable expectation to have to reprogram/change settings for a model if doing something like changing protocols.

as i said before if the channel/protocol mapping works at the outset of programming a model i think that should cover the expectation of new users to deviation, as this is what i see posted about in regards to the channel/protocol mapping.

Wait a minute, why would I want the bargraphs reordered, if I put channel 3 in the third spot and Channel 1 in the first spot, I don't think I want them to change because I changed protocols. The channels don't actually change, it just what the receiver controls that changes.

Leaving it as is would add a visual indicator that the correct channel is moving when I move the stick now assigned to the throttle function.

In reality I don't think the page config should be changed at all if you are using the Advanced Mixer GUI. Much easier to see if something is set wrong if you leave it as is.

The bars were one of the unsolved questions earlier. Personally I would not expect them to change. For me they are only a small picture of the channel monitor placed on the main screen.
On the other side I just expect the bar to move when I move the sticks. I can not perceive the expo applied, but dr limits and the effect of throttle hold. So effectively for me it's not really important where which channel is shown.

This is of course completely different for boxes and toggles, as stated above.

I would not like the BARS to change - having spend a quite bit of time switching between Helis between Devo and Spektrum (DSM2) receivers I need channel 1 to be the first bar irrespective what it represents in the current protocol.

A further point against re-arranging the channels bars based on protocol - many receivers are marked ch1-6 (or 8,...) irrespective of what commands that channel carries to the model. To maintain at least some consistency between aliases and channel orders and ch sequences and receivers, keeping them in fixed 1...x sequence is the best option.

Maybe this is overly simplistic but I always looked at it like this.

• Mode is physical, tell me which stick is ratcheted and which are spring loaded.
• Channels are channels, like on a radio dial, even a station that simply changes call letters would still be at the same location on the dial.
• Protocols are what those channels control, aliased for human consumption (sometimes).

Testing devo7e-v4.0.1-6a63c8e

6 Channel Orange Rcvr
DSM2
Mode 2 Devo 7e
Mixers for Elevons
Mixers for CAR
Tx output at default (10 mW)

Manual says it must be 150 mW for 7e.

In real model tests, range was only 20 feet.

Reset to 150 mW. Range was then as expected.

Current models/default.ini shows:

[radio]
protocol=DEVO
num_channels=8
fixed_id=123456
tx_power=10mW


Question -- can default be 150 mW?

I had thought the default was 150 mW in the released version but misremembered. it always was 10 mw. Guess I had changed it manually before.