I noticed I am not getting the same PWM value for the same channel between the RC and the Gamepad. For example, the following channels when RC low, mid, and high are in different values compared to the gamepad.
RC1_MAX,1901
RC1_MIN,1101
RC1_TRIM,1501
RC2_MAX,1901
RC2_MIN,1101
RC2_TRIM,1501
RC3_MAX,1901
RC3_MIN,1101
RC3_TRIM,1101
RC4_MAX,1901
RC4_MIN,1101
RC4_TRIM,1501
RC5_MAX,1901
RC5_MIN,1101
RC5_TRIM,1501
RC6_MAX,1901
RC6_MIN,1101
RC6_TRIM,1501
RC7_MAX,1901
RC7_MIN,1101
RC7_TRIM,1101
I have done the same as this user trying to explain and share his experience.
So, after Joystick detection and hitting the Enable button, the user cannot arm the copter because Throttle is not the lowest and Yaw is not the highest.
In RC, there is a calibration inside the MP. The calibration for the Joystick gamepad is outside of the MP, there seems to be no way for the RC and Joystick to have the identical PWM range.
DO NOT RC CALIBRATE THE JOYSTICK, it is not the same control mechanism as is used for RC systems. It uses MAVLink override messages.
So, let us take the RC2 channel 2 pitch for discussion, if they do not have identical ranges, what could the forward and backward experience be if the Gamepad MAX is higher than RC2_MAX? Does MAVLink override messages internally map the ranges to the RCx_MIN, RCx_Trim, and RCx_MAX? Can the user safety ignore these concerns? does it affect LUA Script RC_Channel_ud:get_aux_switch_pos(), for example?
