<description>Emit an encrypted signature / key identifying this system. PLEASE NOTE: This protocol has been kept simple, so transmitting the key requires an encrypted channel for true safety.</description>
<fieldname="key"type="char[32]">key</field>
</message>
<messagename="ACTION_ACK"id="9">
<description>This message acknowledges an action. IMPORTANT: The acknowledgement can be also negative, e.g. the MAV rejects a reset message because it is in-flight. The action ids are defined in ENUM MAV_ACTION in mavlink/include/mavlink_types.h</description>
@@ -463,14 +468,23 @@ NOT the global position estimate of the sytem, but rather a RAW sensor value. Se
</message>
<messagename="RAW_PRESSURE"id="29">
<description>The RAW pressure readings for the typical setup of one absolute pressure and one differential pressure sensor. The sensor values should be the raw, unscaled ADC values.</description>
<description>The RAW pressure readings for the typical setup of one absolute pressure and one differential pressure sensor. The sensor values should be the raw, UNSCALED ADC values.</description>
<fieldname="usec"type="uint64_t">Timestamp (microseconds since UNIX epoch or microseconds since system boot)</field>
<fieldname="temperature"type="int16_t">Raw Temperature measurement (raw)</field>
</message>
<messagename="SCALED_PRESSURE"id="38">
<description>The pressure readings for the typical setup of one absolute and differential pressure sensor. The units are as specified in each field.</description>
<fieldname="usec"type="uint64_t">Timestamp (microseconds since UNIX epoch or microseconds since system boot)</field>
<description>The attitude in the aeronautical frame (right-handed, Z-down, X-front, Y-right).</description>
<fieldname="usec"type="uint64_t">Timestamp (microseconds since UNIX epoch or microseconds since system boot)</field>
...
...
@@ -493,6 +507,7 @@ NOT the global position estimate of the sytem, but rather a RAW sensor value. Se
<fieldname="vz"type="float">Z Speed</field>
</message>
<messagename="GLOBAL_POSITION"id="33">
<description>The filtered global position (e.g. fused GPS and accelerometers). Coordinate frame is right-handed, Z-axis up (GPS frame)</description>
<fieldname="usec"type="uint64_t">Timestamp (microseconds since unix epoch)</field>
...
...
@@ -640,9 +655,9 @@ NOT the global position estimate of the sytem, but rather a RAW sensor value. Se
<description>As local waypoints exist, the global waypoint reference allows to transform between the local coordinate frame and the global (GPS) coordinate frame. This can be necessary when e.g. in- and outdoor settings are connected and the MAV should move from in- to outdoor.</description>
<description>The heartbeat message shows that a system is present and responding. The type of the MAV and Autopilot hardware allow the receiving system to treat further messages from this system appropriate (e.g. by laying out the user interface based on the autopilot).</description>
<fieldname="type"type="uint8_t">Type of the MAV (quadrotor, helicopter, etc., up to 15 types, defined in MAV_TYPE ENUM)</field>
<fieldname="autopilot"type="uint8_t">Type of the Autopilot: 0: Generic, 1: PIXHAWK, 2: SLUGS, 3: Ardupilot (up to 15 types), defined in MAV_AUTOPILOT_TYPE ENUM</field>
</message>
<messagename="BOOT"id="1">
<description>The boot message indicates that a system is starting. The onboard software version allows to keep track of onboard soft/firmware revisions.</description>
<description>The system time is the time of the master clock, typically the computer clock of the main onboard computer.</description>
<fieldname="time_usec"type="uint64_t">Timestamp of the master clock in microseconds since UNIX epoch.</field>
</message>
<messagename="PING"id="3">
<description>A ping message either requesting or responding to a ping. This allows to measure the system latencies, including serial port, radio modem and UDP connections.</description>
<fieldname="target_system"type="uint8_t">0: request ping from all receiving systems, if greater than 0: message is a ping response and number is the system id of the requesting system</field>
<fieldname="target_component"type="uint8_t">0: request ping from all receiving components, if greater than 0: message is a ping response and number is the system id of the requesting system</field>
<fieldname="time"type="uint64_t">Unix timestamp in microseconds</field>
</message>
<messagename="ACTION"id="10">
<description>An action message allows to execute a certain onboard action. These include liftoff, land, storing parameters too EEPROM, shutddown, etc. The action ids are defined in ENUM MAV_ACTION in mavlink/include/mavlink_types.h</description>
<fieldname="target"type="uint8_t">The system executing the action</field>
<fieldname="target_component"type="uint8_t">The component executing the action</field>
<description>This message acknowledges an action. IMPORTANT: The acknowledgement can be also negative, e.g. the MAV rejects a reset message because it is in-flight. The action ids are defined in ENUM MAV_ACTION in mavlink/include/mavlink_types.h</description>
<description>Set the system mode, as defined by enum MAV_MODE in mavlink/include/mavlink_types.h. There is no target component id as the mode is by definition for the overall aircraft, not only for one component.</description>
<fieldname="target"type="uint8_t">The system setting the mode</field>
<fieldname="mode"type="uint8_t">The new mode</field>
</message>
<messagename="SET_NAV_MODE"id="12">
<description>Set the system navigation mode, as defined by enum MAV_NAV_MODE in mavlink/include/mavlink_types.h. The navigation mode applies to the whole aircraft and thus all components.</description>
<fieldname="target"type="uint8_t">The system setting the mode</field>
<fieldname="nav_mode"type="uint8_t">The new navigation mode</field>
</message>
<messagename="RAW_IMU"id="28">
<description>The RAW IMU readings for the usual 9DOF sensor setup. This message should always contain the true raw values without any scaling to allow data capture and system debugging.</description>
<fieldname="usec"type="uint64_t">Timestamp (microseconds since UNIX epoch)</field>
<fieldname="xgyro"type="int16_t">Angular speed around X axis (adc units)</field>
<fieldname="ygyro"type="int16_t">Angular speed around Y axis (adc units)</field>
<fieldname="zgyro"type="int16_t">Angular speed around Z axis (adc units)</field>
<fieldname="xmag"type="int16_t">X Magnetic field (milli tesla)</field>
<fieldname="ymag"type="int16_t">Y Magnetic field (milli tesla)</field>
<fieldname="zmag"type="int16_t">Z Magnetic field (milli tesla)</field>
</message>
<messagename="RAW_PRESSURE"id="29">
<description>The RAW pressure readings for the typical setup of one absolute pressure and one differential pressure sensor. The sensor values should be the raw, unscaled ADC values.</description>
<fieldname="usec"type="uint64_t">Timestamp (microseconds since UNIX epoch)</field>
<description>The filtered local position (e.g. fused computer vision and accelerometers).</description>
<fieldname="usec"type="uint64_t">Timestamp (microseconds since unix epoch)</field>
<fieldname="x"type="float">X Position</field>
<fieldname="y"type="float">Y Position</field>
<fieldname="z"type="float">Z Position</field>
<fieldname="vx"type="float">X Speed</field>
<fieldname="vy"type="float">Y Speed</field>
<fieldname="vz"type="float">Z Speed</field>
</message>
<messagename="GPS_RAW"id="32">
<description>The global position, as returned by the Global Positioning System (GPS). This is
NOT the global position estimate of the sytem, but rather a RAW sensor value. See message GLOBAL_POSITION for the global position estimate.</description>
<fieldname="usec"type="uint64_t">Timestamp (microseconds since unix epoch)</field>
<fieldname="fix_type"type="uint8_t">0-1: no fix, 2: 2D fix, 3: 3D fix</field>
<fieldname="lat"type="float">X Position</field>
<fieldname="lon"type="float">Y Position</field>
<fieldname="alt"type="float">Z Position in meters</field>
<fieldname="eph"type="float">Uncertainty in meters of latitude</field>
<fieldname="epv"type="float">Uncertainty in meters of longitude</field>
<fieldname="v"type="float">Overall speed</field>
<fieldname="hdg"type="float">Heading, in FIXME</field>
</message>
<messagename="GPS_STATUS"id="27">
<description>The global position, as returned by the Global Positioning System (GPS). This is
NOT the global position estimate of the sytem, but rather a RAW sensor value. See message GLOBAL_POSITION for the global position estimate. This message can contain information for up to 20 satellites.</description>
<fieldname="satellites_visible"type="uint8_t">Number of satellites visible</field>
<fieldname="satellite_used"type="array[20]">0: Satellite not used, 1: used for localization</field>
<fieldname="satellite_elevation"type="array[20]">Elevation (0: right on top of receiver, 90: on the horizon) of satellite</field>
<fieldname="satellite_azimuth"type="array[20]">Direction of satellite, 0: 0 deg, 255: 360 deg.</field>
<fieldname="satellite_snr"type="array[20]">Signal to noise ratio of satellite</field>
</message>
<messagename="SYS_STATUS"id="34">
<description>The general system state. If the system is following the MAVLink standard, the system state is mainly defined by three orthogonal states/modes: The system mode, which is either LOCKED (motors shut down and locked), MANUAL (system under RC control), GUIDED (system with autonomous position control, position setpoint controlled manually) or AUTO (system guided by path/waypoint planner). The NAV_MODE defined the current flight state: LIFTOFF (often an open-loop maneuver), LANDING, WAYPOINTS or VECTOR. This represents the internal navigation state machine. The system status shows wether the system is currently active or not and if an emergency occured. During the CRITICAL and EMERGENCY states the MAV is still considered to be active, but should start emergency procedures autonomously. After a failure occured it should first move from active to critical to allow manual intervention and then move to emergency after a certain timeout.</description>
<fieldname="mode"type="uint8_t">System mode, see MAV_MODE ENUM in mavlink/include/mavlink_types.h</field>
<fieldname="nav_mode"type="uint8_t">Navigation mode, see MAV_NAV_MODE ENUM</field>
<fieldname="status"type="uint8_t">System status flag, see MAV_STATUS ENUM</field>
<fieldname="vbat"type="uint16_t">Battery voltage, in millivolts (1 = 1 millivolt)</field>
<fieldname="motor_block"type="uint8_t">Motor block status flag, 0: Motors can be switched on (and could be either off or on), 1: Mechanical motor block switch is on, motors cannot be switched on (and are definitely off)</field>
<fieldname="packet_drop"type="uint16_t">Dropped packets (packets that were corrupted on reception on the MAV)</field>
</message>
<messagename="WAYPOINT"id="39">
<description>Message encoding a waypoint. This message is emitted to announce
the presence of a waypoint. It cannot be used to set a waypoint, use WAYPOINT_SET for this purpose. The waypoint can be either in x, y, z meters (type: LOCAL) or x:lat, y:lon. The global and body frame are related as: positive Z-down, positive X(front looking north, positive Y(body:right) looking east. Therefore y encodes in global mode the latitude, whereas x encodes the longitude and z the GPS altitude (WGS84).</description>
<fieldname="type"type="uint8_t">0: global (GPS), 1: local, 2: global orbit, 3: local orbit</field>
<fieldname="orbit"type="float">Orbit to circle around the waypoint, in meters. Set to 0 to fly straight through the waypoint</field>
<fieldname="orbit_direction"type="uint8_t">Direction of the orbit circling: 0: clockwise, 1: counter-clockwise</field>
<fieldname="param1"type="float">For waypoints of type 0 and 1: Radius in which the waypoint is accepted as reached, in meters</field>
<fieldname="param2"type="float">For waypoints of type 0 and 1: Time that the MAV should stay inside the orbit before advancing, in milliseconds</field>
<fieldname="yaw"type="float">yaw orientation in radians, 0 = NORTH</field>
<fieldname="autocontinue"type="uint8_t">autocontinue to next wp</field>
</message>
<messagename="WAYPOINT_REQUEST"id="40">
<description>Request the information of the waypoint with the sequence number seq. The response of the system to this message should be a WAYPOINT message.</description>
<description>Set the waypoint with sequence number seq as current waypoint. This means that the MAV will continue to this waypoint on the shortest path (not following the waypoints in-between).</description>
<description>Message that announces the sequence number of the current active waypoint. The MAV will fly towards this waypoint.</description>
<fieldname="seq"type="uint16_t">Sequence</field>
</message>
<messagename="WAYPOINT_COUNT"id="44">
<description>This message is emitted as response to WAYPOINT_REQUEST_LIST by the MAV. The GCS can then request the individual waypoints based on the knowledge of the total number of waypoints.</description>
<description>A certain waypoint has been reached. The system will either hold this position (or circle on the orbit) or (if the autocontinue on the WP was set) continue to the next waypoint.</description>
<fieldname="seq"type="uint16_t">Sequence</field>
</message>
<messagename="WAYPOINT_ACK"id="47">
<description>Ack message during waypoint handling. The type field states if this message is a positive ack (type=0) or if an error happened (type=non-zero).</description>
<description>As local waypoints exist, the global waypoint reference allows to transform between the local coordinate frame and the global (GPS) coordinate frame. This can be necessary when e.g. in- and outdoor settings are connected and the MAV should move from in- to outdoor.</description>
<fieldname="global_x"type="float">global x position</field>
<fieldname="global_y"type="float">global y position</field>
<fieldname="global_z"type="float">global z position</field>
<fieldname="global_yaw"type="float">global yaw orientation in radians, 0 = NORTH</field>
<fieldname="local_x"type="float">local x position that matches the global x position</field>
<fieldname="local_y"type="float">local y position that matches the global y position</field>
<fieldname="local_z"type="float">local z position that matches the global z position</field>
<fieldname="local_yaw"type="float">local yaw that matches the global yaw orientation</field>
</message>
<!-- MESSAGE IDs 80 - 250: Space for custom messages in individual projectname_messages.xml files -->
<messagename="STATUSTEXT"id="254">
<description>Status text message. These messages are printed in yellow in the COMM console of QGroundControl. WARNING: They consume quite some bandwidth, so use only for important status and error messages. If implemented wisely, these messages are buffered on the MCU and sent only at a limited rate (e.g. 10 Hz).</description>
<fieldname="severity"type="uint8_t">Severity of status, 0 = info message, 255 = critical fault</field>
<fieldname="text"type="array[50]">Status text message, without null termination character</field>
</message>
<messagename="DEBUG"id="255">
<description>Send a debug value. The index is used to discriminate between values. These values show up in the plot of QGroundControl as DEBUG N.</description>
<fieldname="ind"type="uint8_t">index of debug variable</field>
The heartbeat message just shows that a system is present.
<fieldname="type"type="uint8_t">Type of the MAV (quadrotor, helicopter, etc., up to 15 types, defined in MAV_TYPE ENUM)</field>
<fieldname="autopilot"type="uint8_t">Type of the Autopilot: 0: Generic, 1: PIXHAWK, 2: SLUGS, 3: Ardupilot (up to 15 types), defined in MAV_AUTOPILOT_TYPE ENUM</field>
</message>
<messagename="PING"id="1">
A ping message either requesting or responding to a ping.
<fieldname="target_system"type="uint8_t">0: request ping from all receiving systems, if greater than 0: message is a ping response and number is the system id of the requesting system</field>
<fieldname="target_component"type="uint8_t">0: request ping from all receiving components, if greater than 0: message is a ping response and number is the system id of the requesting system</field>
<fieldname="time"type="uint64_t">Unix timestamp in microseconds</field>
Trim values to scale the RAW RC channel values. The standard PPM modulation is as follows: 1000 microseconds: 0%, 2000 microseconds: 100%. Individual receivers/transmitters might violate this specification.
<fieldname="chan_function"type="uint8_t">RC channel function, as defined in ENUM MAVLINK_RC_CHAN_MAPPING in mavlink/include/mavlink_types.h</field>
</message>
<messagename="WAYPOINT_SET"id="16">
Message setting a waypoint. The waypoint can be either in x, y, z meters (type: LOCAL) or x:lat, y:lon. The global and body frame are related as: positive Z-down, positive X(front looking north, positive Y(body:right) looking east. Therefore x encodes in global mode the latitude, whereas y encodes the longitude and z the altitude over ground.
<fieldname="param_subset_id"type="uint8_t">0: All parameters, else report a subset of parameters as defined in MAVLIN_SUBSET_PARAM enum</field>
</message>
<messagename="PID"id="34">
Report PID controller values.
<fieldname="pid_id"type="uint8_t">PID ID</field>
<fieldname="k_p"type="float">P</field>
<fieldname="k_i"type="float">I</field>
<fieldname="k_d"type="float">D</field>
</message>
<messagename="RC_CHANNELS_TRIM"id="35">
Report trim values to scale the RAW RC channel values. The standard PPM modulation is as follows: 1000 microseconds: 0%, 2000 microseconds: 100%. Individual receivers/transmitters might violate this specification.
<fieldname="chan_function"type="uint8_t">RC channel function, as defined in ENUM MAVLINK_RC_CHAN_MAPPING in mavlink/include/mavlink_types.h</field>
</message>
<messagename="WAYPOINT"id="37">
Message encoding a waypoint. This message is emitted to announce
the presence of a waypoint. It cannot be used to set a waypoint, use WAYPOINT_SET for this purpose. The waypoint can be either in x, y, z meters (type: LOCAL) or x:lat, y:lon. The global and body frame are related as: positive Z-down, positive X(front looking north, positive Y(body:right) looking east. Therefore x encodes in global mode the latitude, whereas y encodes the longitude and z the altitude over ground.
The RAW values of the RC channels received. The standard PPM modulation is as follows: 1000 microseconds: 0%, 2000 microseconds: 100%. Individual receivers/transmitters might violate this specification.
<fieldname="chan1"type="uint16_t">RC channel 1 value, in microseconds</field>
<fieldname="chan2"type="uint16_t">RC channel 2 value, in microseconds</field>
<fieldname="chan3"type="uint16_t">RC channel 3 value, in microseconds</field>
<fieldname="chan4"type="uint16_t">RC channel 3 value, in microseconds</field>
<fieldname="chan5"type="uint16_t">RC channel 3 value, in microseconds</field>
</message>
<!-- MESSAGE IDs 70 - 240: Space for custom messages in individual projectname_messages.xml files -->
<messagename="STATUSTEXT"id="240">
<fieldname="severity"type="uint8_t">Severity of status, 0 = info message, 255 = critical fault</field>
<fieldname="text"type="array[50]">Status text message, without null termination character</field>
</message>
<messagename="DEBUG"id="241">
<fieldname="ind"type="uint8_t">index of debug variable</field>
<fieldname="fl_6"type="float">Log value 6 </field>
</message>
<messagename="FILTERED_DATA"id="178">
Measured value from the IMU in units after sensor calibration and temperature compensation. Note that this IS NOT the output of the attitude filter, for that see messages 30 and 33.
<fieldname="aX"type="float">Accelerometer X value (m/s^2) </field>
<fieldname="aY"type="float">Accelerometer Y value (m/s^2)</field>
<fieldname="aZ"type="float">Accelerometer Z value (m/s^2)</field>
<fieldname="gX"type="float">Gyro X value (rad/s) </field>
<fieldname="gY"type="float">Gyro Y value (rad/s)</field>
<fieldname="gZ"type="float">Gyro Z value (rad/s)</field>
<fieldname="mX"type="float">Magnetometer X (normalized to 1) </field>
<fieldname="mY"type="float">Magnetometer Y (normalized to 1) </field>
<fieldname="mZ"type="float">Magnetometer Z (normalized to 1) </field>
</message>
<messagename="GPS_DATE_TIME"id="179">
Pilot console PWM messges.
<fieldname="year"type="uint8_t">Year reported by Gps </field>
...
...
@@ -166,14 +130,6 @@ This message configures the Selective Passthrough mode. it allows to select whic
<fieldname="bitfieldPt"type="uint16_t">Bitfield containing the PT configuration</field>
</message>
<messagename="PID"id="182">
Configure a PID loop.
<fieldname="target"type="uint8_t">The system setting the PID values</field>
Configurable data log probes to be used inside Simulink
<fieldname="fl_1"type="float">Log value 1 </field>
<fieldname="fl_2"type="float">Log value 2 </field>
<fieldname="fl_3"type="float">Log value 3 </field>
<fieldname="fl_4"type="float">Log value 4 </field>
<fieldname="fl_5"type="float">Log value 5 </field>
<fieldname="fl_6"type="float">Log value 6 </field>
</message>
<messagename="FILTERED_DATA"id="178">
Measured value from the IMU in units after sensor calibration and temperature compensation. Note that this IS NOT the output of the attitude filter, for that see messages 30 and 33.
<fieldname="aX"type="float">Accelerometer X value (m/s^2) </field>
<fieldname="aY"type="float">Accelerometer Y value (m/s^2)</field>
<fieldname="aZ"type="float">Accelerometer Z value (m/s^2)</field>
<fieldname="gX"type="float">Gyro X value (rad/s) </field>
<fieldname="gY"type="float">Gyro Y value (rad/s)</field>
<fieldname="gZ"type="float">Gyro Z value (rad/s)</field>
<fieldname="mX"type="float">Magnetometer X (normalized to 1) </field>
<fieldname="mY"type="float">Magnetometer Y (normalized to 1) </field>
<fieldname="mZ"type="float">Magnetometer Z (normalized to 1) </field>
</message>
<messagename="GPS_DATE_TIME"id="179">
Pilot console PWM messges.
<fieldname="year"type="uint8_t">Year reported by Gps </field>
<fieldname="month"type="uint8_t">Month reported by Gps </field>
<fieldname="day"type="uint8_t">Day reported by Gps </field>
<fieldname="hour"type="uint8_t">Hour reported by Gps </field>
<fieldname="min"type="uint8_t">Min reported by Gps </field>
<fieldname="sec"type="uint8_t">Sec reported by Gps </field>
<fieldname="visSat"type="uint8_t">Visible sattelites reported by Gps </field>
</message>
<messagename="MID_LVL_CMDS"id="180">
Mid Level commands sent from the GS to the autopilot. These are only sent when being opperated in mid-level commands mode from the ground; for periodic report of these commands generated from the autopilot see message XXXX.
<fieldname="target"type="uint8_t">The system setting the commands</field>
<fieldname="uCommand"type="float">Log value 2 </field>
<fieldname="rCommand"type="float">Log value 3 </field>
</message>
<messagename="CTRL_SRFC_PT"id="181">
This message configures the Selective Passthrough mode. it allows to select which control surfaces the Pilot can control from his console. It is implemented as a bitfield as follows:
Position Bit Code
=================================
15-8 Reserved
7 dt_pass 128
6 dla_pass 64
5 dra_pass 32
4 dr_pass 16
3 dle_pass 8
2 dre_pass 4
1 dlf_pass 2
0 drf_pass 1
Where Bit 15 is the MSb. 0 = AP has control of the surface; 1 = Pilot Console has control of the surface.
<fieldname="target"type="uint8_t">The system setting the commands</field>
<fieldname="bitfieldPt"type="uint16_t">Bitfield containing the PT configuration</field>
</message>
<messagename="PID"id="182">
Configure a PID loop.
<fieldname="target"type="uint8_t">The system setting the PID values</field>