Easiest cellular telemetry link?

anparkinson · January 16, 2022, 7:30pm

I’d like a cellular telemetry link between my plane and Mission Planner on my laptop.

Is this possible? What’s the easiest way?

geofrancis · January 16, 2022, 11:08pm

kiwiPaul · January 21, 2022, 9:54am

`Thanks Geofrancis.
I downloaded andruav on a couple of phones and used the webapp today - this sw is excellent!!
I’ve yet to run it on our boat - but playing around at home via 4G its looking pretty magical. Thanks dev team.

geofrancis · January 21, 2022, 2:11pm

there was a mavlink 2 bug that shows up when trying to use the web plugin, basically ardupilot doesnt send mavlink 2 unless its requested but andruav wont work unless it detects mavlink 2. This is fixed in 4.2dev, you can get around it in earlier versions but you have to initialize the telemetry port you want to use directly with mission planner first using a mavlink 2 radio or USB so it works in mavlink 2 mode.

github.com/ArduPilot/ardupilot

GCS_MAVLink: Don't start with MAVLink1 messages on a MAVLink2 connection

ArduPilot:master ← stephendade:mav20new

opened 01:24AM - 13 Dec 21 UTC

stephendade

+1 -12

Currently, ArduPilot will default to MAVLink1 messages on a ``SERIALn_PROTOCOL=2…``, until a valid MAVLink2 message is received from the GCS. Then AP will switch to sending MAVLink2 messages. Note that if MAVLink signing is enabled, ArduPilot will send MAVLink2 messages from the beginning anyway. This PR makes this behaviour more consistent, so ArduPilot will in all cases (where ``SERIALn_PROTOCOL=2``) send MAVLink2 messages from the beginning. Looking at the comments around the code, it seems this came from the time period where MAVLink2 was new, and provided a fallback to ensure a GCS could always communicate with ArduPilot. Given how long we've been using MAVLink2 without issues, I suspect this is no longer an issue. I recently encountered this whilst troubleshooting a custom GCS, where the GCS would auto-detect the MAVLink version by looking at the incoming protocol markers. So the GCS always auto-detected MAVLink1, despite ``SERIALn_PROTOCOL=2``. This will also be an issue for any GCS links over high-latency/low-bandwidth connections, where the GCS may not be sending packets often. I've tested this PR against MAVProxy, QGC and Mission Planner with no problems. I note this is a change to how ArduPilot interacts with GCS's and related systems, so I'd be interested in any cases where this breaks any existing functionality _and_ it's not fixable via setting ``SERIALn_PROTOCOL=1``.