I can't believe I missed that!
expects cmdToSend1 to be a single, but the MAVlink command looks to be sending UInt16s. Is the correct way to proceed to generate several singles with bits that are equivalent to 2 uint16s, and set param1,param2, etc?
I investigated two other routes of sending the command:
RC = MAVLink.mavlink_rc_channels_override_t()
RC.chan1_raw = x
MAV.sendPacket(RC, RC.target_system, RC.target_component )
yields a warning:
warning: RuntimeWarning: Setting field chan1_raw on value type mavlink_rc_channels_override_t may result in updating a copy. Use mavlink_rc_channels_override_t.chan1_raw.SetValue(instance, value) if this is safe. For more information help(mavlink_rc_channels_override_t.chan1_raw.SetValue).
and has no effect.
, but I am not sure of what to use for instance. MAVID seems not to work.
I also found that, in SITL with XPlane, when using Script.SendRC(), stopping the script results in MissionPlanner keeping the RC override last sent when the script was aborted. I worry about this from an FMEA perspective. Have I misconfigured something, or is this just the way things are? Would unplugging the ground-station give control back to actual RC transmitters? Is there a way in MissionPlanner to return all RC control to the physical RC transmitters?
Thanks again for all your help!