The MAVLink message set.
Each message set has its own module with corresponding data types, including a
that represents all possible messages in that message set. The
Message trait is used to
represent messages in an abstract way, and each
MavMessage enum implements this trait (for
ardupilotmega::MavMessage). This is then monomorphized to the specific message
set you are using in your application at compile-time via type parameters. If you expect
ArduPilotMega-flavored messages, then you will need a
and you will receive
ardupilotmega::MavMessages from it.
Some message sets include others. For example, all message sets except
common include the
common message set. This is represented with extra values in the
MavMessage enum: a message
in the common message set received on an ArduPilotMega connection will be an
Please note that if you want to enable a given message set, you must also enable the
feature for the message sets that it includes. For example, you cannot use the
feature without also using the
Encapsulation of the Mavlink message and the header, important to preserve information about the sender system and component id
Metadata from a MAVLink packet header
Versions of the Mavlink protocol that we support
Connect to a MAVLink node by address string.
Read a MAVLink v1 message from a Read stream.
Read a MAVLink v2 message from a Read stream.
Write a MAVLink v1 message to a Write stream.
Write a MAVLink v2 message to a Write stream.
Write a message using the given mavlink version