MAVLink
How to connect to your device over MAVLink
MAVLink is a standardized protocol used frequently with drones. It works with many different flight controllers, programming languages, and links. Visit the mavlink docs for more info about how it works.
We also use a program called mavproxy that implements the mavlink protocol and includes lots of important features to make mav usable. The docs for mavproxy can be found here.
Below is a diagram of a proposed mavlink system. The below setup is how we setup our drones for testing at Theseus.

Theseus provides two ways to connect to your system over mavlink:
Connect to the edge device (for debug)
Devices running Theseus software route mav packets through mavproxy
Mavproxy has an open udp input connection (1) that you can connect to with udpout
Mavproxy on the edge device lists the flight controller (4) as the one and only master
Cyclops/mvps (3) and the external mav connection (1) are listed as outputs
Mav packets are only routed from an output to a master, or a master to all outputs
You will not be able to see mav packets from the edge device, or send mav packets to the edge device if you connect over this link
It exists solely as a pass through to allow you to connect to your flight controller through the edge device (mainly for convenience)
Direct connect to the flight controller
Use this connection method for flying
If using ardupilot, status text messages will be routed from the edge device to your ground station
Connecting with Vozilla

Use this dropdown menu in the top right corner of Vozilla to select a connection profile. However you connect to your flight controller normally is what you should use. You can also add output ports so you can connect on other applications like mission planner simultaneously.
Other MAVLink info
mvps mavlink info
MAVLinkcyclops mavlink info
MAVLinkvozilla (<2.0) mavlink page
MAVLinkLast updated
