It turns out that mavproxy’s context for rcbind is rcbind <dsmmode>. Since DSM mode would be Param #2, it appears that mavproxy is only interpreting one argument. so I dug into the source for MAVproxy and found this:
As suspected, rcbind's one and only argument is being interpreted as MAV_CMD_START_RX_PAIR’s param #2 via the float(args[0]) placed in the second parameter position.
So I downloaded the source and edited mavproxy_misc.py to read:
def cmd_rcbind(self, args):
'''start RC bind'''
if len(args) < 1:
print("Usage: rcbind <dsmmode>")
return
self.master.mav.command_long_send(self.settings.target_system,
self.settings.target_component,
mavutil.mavlink.MAV_CMD_START_RX_PAIR,
1,
float(args[0]), 0, 0, 0, 0, 0, 0)
…And re-ran rcbind 0 to force MAV_CMD_START_RX_PAIR’s Param #1 == 1 (via hardcoded as above) and param #2 == 0 (via the default <dsmmode> argument in MAVproxy)
The light on the RX turns off for a second, but then picks up blinking the same as before. So It is getting the message, but it still doesnt seem to be going into bind mode. I am looking for a solid light to indicate that the RX is in bind mode.
Work in progress…
Anyone have any pointers? Im just talking to myself here.