Lol you’re really going for it
OK a few notes, firstly on the UDP connection which you eventually worked out, I did post the solution higher up, but should have been more clear:
By default there are 6 UDP ports opened on the proxy, the first three are ‘out’ and the last three are ‘in’. If you’re connecting from an external IP you need to use the last 3 ports and connect with UDPCI. MP UDP connection is only really useful if you’re connecting to a local SITL or if you direct the central proxy to a specific external IP (which is ugly).
When you set "maverick_fc::mavlink_baud": "921600"
and then run maverick configure
, it uses that value (and others) to transform the various mavlink proxy configurations, held in ~/config/mavlink. If you’re using the default mavlink-router proxy, have a look at ~/config/mavlink/mavlink-router-fc.conf, which has been generated from the values you specify and various defaults. In there you should see ‘Baud=921600,57600,115200,921600’, which is the order it tries to connect, and when it detects a connection it sticks to it. It may be that you set the localconf value but didn’t run maverick configure
, in which case it would have been cycling through the default values which are ‘Baud=115200,57600,115200,921600’. It puts the value you specify first of all (921600, or 115200 which is the default), and then a set of fallback values to try (57600,115200,921600).
So, the next bit, dronekit failing. You’re right when you say the maverick docs say ‘As tcp endpoints can support multiple connections this does not restrict usage.’. The tcp proxy endpoint does support multiple connections - you can connect multiple GCSs for example to the same tcp endpoint, as well as dronekit etc. It’s dronekit that face-plants however - since a while back when ardpilot added mavlink routing. Read all about it here: Exception in message handler for HEARTBEAT mode 0 not available on mavlink definition · Issue #677 · dronekit/dronekit-python · GitHub. Basic answer is use something else, like ROS, if you want multiple mavlink devices on the wire. With regards dronekit, mavlink-router and udp, read here ('Normal' udp endpoint doesn't work · Issue #95 · mavlink-router/mavlink-router · GitHub). Dronekit seems to be in maintenance-only mode, no real improvements are being made to it - until (if) droncore becomes available for ardupilot, you might be better looking at ROS/Mavros.