C 2.01: why is the throttle trim behaviour different ?

[SR71]

Busy in OpenTx 2.0 conversion process, I noticed a weird difference.

In an old model, in order to achieve a trim range between 0 -50, I created the following mix (C 1.52):

Code: Select all

 CH10 TrmT Weight(+25%) Offset(100%)

that returns a 0 - 50 output on the whole trim range.

Loading the same file in C2.0.1 the Mix becomes:

Code: Select all

CH10 TrmT Weight(+25%) Offset(25%)

that always returns a 0 - 50 output on the whole trim range.

Now, put aside that, looking at it harder, it seems that after all the behavior more correct is the second one, why is this happening ?

[MikeB]

I believe the offset is now applied AFTER the weight, where before it was applied BEFORE the weight.
So in 1.52 the offset of 100% was then modified by the weight of 25% giving an actual offset of 25%.
Now, the offset is not modified.

The original method was in er9x/openTx for a long time. It is arguable that it should always have been done the new way.
I added an option to er9x/ersky9x a year ago to choose between these two methods, so existing mixes still worked, but you could choose this later (better) method.

Mike.