You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the RC transmitter is turned on after the flight controller has already initialized then RC will not be used for control setpoints. It seems that this issue was introduced between 1.5.5 and 1.6.0rc1.
I think that it is because there are two instances of the manual_control_setpoint topic being published, one for RC and one for SOURCE_MAVLINK_3. If the RC transmitter is on during startup then it's manual_control_setpoint topic will be instance 0, but If it is turned on after startup then the mavlink instance will be instance 0 and the RC instance will be instance 1.
The text was updated successfully, but these errors were encountered:
This was actually a short term "feature" to prevent them from conflicting. Ideally we'd want some hand off mechanism to move between RC and gamepad input, but it needs to be safe.
If the RC transmitter is turned on after the flight controller has already initialized then RC will not be used for control setpoints. It seems that this issue was introduced between 1.5.5 and 1.6.0rc1.
I think that it is because there are two instances of the manual_control_setpoint topic being published, one for RC and one for SOURCE_MAVLINK_3. If the RC transmitter is on during startup then it's manual_control_setpoint topic will be instance 0, but If it is turned on after startup then the mavlink instance will be instance 0 and the RC instance will be instance 1.
The text was updated successfully, but these errors were encountered: