In some rare cases it's possible that a transmitter produces exactly 1100 as
the minimum and 1900 as the maximum in which case the regular rc calibration
will not make the warning go away. One work around is to manually change the
Ah, actually, my reading is that we don't use these values to determine
whether your (e.g.) ROLL is configured.
Here'e the call we make to see if the channel is configured:
Here's the definition of that call:
And here are the AP_Param objects that's calling methods on:
"configured" on an AP_Int16:
And I'm sure we really don't want to go digging deeper into AP_Param, for
there be dragons. Suffice to say that AP_Param doesn't know anything
about magic PWM values
RC1_MIN to 1101 and RC1_MAX to 1901. You should only do this though if you
see that the RC1_MIN is 1100 and RC1_MAX is exactly 1900. If it's not then
there is a different problem.
So when you explicity set those to a value that's different to the default
value it will result in a write to storage, meaning "configured" will
return true, fixing the problem.
However - why is MP not getting that same effect from its calibration
screen? Perhaps it isn't sending through a param-set if the value hasn't