Skip to content

slapos
slapos
Commit 1877bde4 authored by Léo-Paul Géneau's avatar Léo-Paul Géneau 👾
Browse files
Options

component/mavsdk: update common.xml

parent d3d9e767
Hide whitespace changes
Inline Side-by-side
Showing with 53 additions and 704 deletions
component/mavsdk/buildout.hash.cfg
View file @ 1877bde4
......@@ -14,4 +14,4 @@
# not need these here).
[message-definition]
filename = common.xml
md5sum = 741068d99c27594d9b655caf125169f3
md5sum = 0ea1924febf283cb065b328874cb16fa
component/mavsdk/common.xml
View file @ 1877bde4
<?xml version="1.0"?>
<mavlink>
<include>minimal.xml</include>
<version>3</version>
<dialect>0</dialect>
<enums>
<enum name="MAV_AUTOPILOT">
<description>Micro air vehicle / autopilot classes. This identifies the individual model.</description>
<entry value="0" name="MAV_AUTOPILOT_GENERIC">
<description>Generic autopilot, full support for everything</description>
</entry>
<entry value="1" name="MAV_AUTOPILOT_RESERVED">
<description>Reserved for future use.</description>
</entry>
<entry value="2" name="MAV_AUTOPILOT_SLUGS">
<description>SLUGS autopilot, http://slugsuav.soe.ucsc.edu</description>
</entry>
<entry value="3" name="MAV_AUTOPILOT_ARDUPILOTMEGA">
<description>ArduPilot - Plane/Copter/Rover/Sub/Tracker, https://ardupilot.org</description>
</entry>
<entry value="4" name="MAV_AUTOPILOT_OPENPILOT">
<description>OpenPilot, http://openpilot.org</description>
</entry>
<entry value="5" name="MAV_AUTOPILOT_GENERIC_WAYPOINTS_ONLY">
<description>Generic autopilot only supporting simple waypoints</description>
</entry>
<entry value="6" name="MAV_AUTOPILOT_GENERIC_WAYPOINTS_AND_SIMPLE_NAVIGATION_ONLY">
<description>Generic autopilot supporting waypoints and other simple navigation commands</description>
</entry>
<entry value="7" name="MAV_AUTOPILOT_GENERIC_MISSION_FULL">
<description>Generic autopilot supporting the full mission command set</description>
</entry>
<entry value="8" name="MAV_AUTOPILOT_INVALID">
<description>No valid autopilot, e.g. a GCS or other MAVLink component</description>
</entry>
<entry value="9" name="MAV_AUTOPILOT_PPZ">
<description>PPZ UAV - http://nongnu.org/paparazzi</description>
</entry>
<entry value="10" name="MAV_AUTOPILOT_UDB">
<description>UAV Dev Board</description>
</entry>
<entry value="11" name="MAV_AUTOPILOT_FP">
<description>FlexiPilot</description>
</entry>
<entry value="12" name="MAV_AUTOPILOT_PX4">
<description>PX4 Autopilot - http://px4.io/</description>
</entry>
<entry value="13" name="MAV_AUTOPILOT_SMACCMPILOT">
<description>SMACCMPilot - http://smaccmpilot.org</description>
</entry>
<entry value="14" name="MAV_AUTOPILOT_AUTOQUAD">
<description>AutoQuad -- http://autoquad.org</description>
</entry>
<entry value="15" name="MAV_AUTOPILOT_ARMAZILA">
<description>Armazila -- http://armazila.com</description>
</entry>
<entry value="16" name="MAV_AUTOPILOT_AEROB">
<description>Aerob -- http://aerob.ru</description>
</entry>
<entry value="17" name="MAV_AUTOPILOT_ASLUAV">
<description>ASLUAV autopilot -- http://www.asl.ethz.ch</description>
</entry>
<entry value="18" name="MAV_AUTOPILOT_SMARTAP">
<description>SmartAP Autopilot - http://sky-drones.com</description>
</entry>
<entry value="19" name="MAV_AUTOPILOT_AIRRAILS">
<description>AirRails - http://uaventure.com</description>
</entry>
</enum>
<enum name="MAV_TYPE">
<description>MAVLINK component type reported in HEARTBEAT message. Flight controllers must report the type of the vehicle on which they are mounted (e.g. MAV_TYPE_OCTOROTOR). All other components must report a value appropriate for their type (e.g. a camera must use MAV_TYPE_CAMERA).</description>
<entry value="0" name="MAV_TYPE_GENERIC">
<description>Generic micro air vehicle</description>
</entry>
<entry value="1" name="MAV_TYPE_FIXED_WING">
<description>Fixed wing aircraft.</description>
</entry>
<entry value="2" name="MAV_TYPE_QUADROTOR">
<description>Quadrotor</description>
</entry>
<entry value="3" name="MAV_TYPE_COAXIAL">
<description>Coaxial helicopter</description>
</entry>
<entry value="4" name="MAV_TYPE_HELICOPTER">
<description>Normal helicopter with tail rotor.</description>
</entry>
<entry value="5" name="MAV_TYPE_ANTENNA_TRACKER">
<description>Ground installation</description>
</entry>
<entry value="6" name="MAV_TYPE_GCS">
<description>Operator control unit / ground control station</description>
</entry>
<entry value="7" name="MAV_TYPE_AIRSHIP">
<description>Airship, controlled</description>
</entry>
<entry value="8" name="MAV_TYPE_FREE_BALLOON">
<description>Free balloon, uncontrolled</description>
</entry>
<entry value="9" name="MAV_TYPE_ROCKET">
<description>Rocket</description>
</entry>
<entry value="10" name="MAV_TYPE_GROUND_ROVER">
<description>Ground rover</description>
</entry>
<entry value="11" name="MAV_TYPE_SURFACE_BOAT">
<description>Surface vessel, boat, ship</description>
</entry>
<entry value="12" name="MAV_TYPE_SUBMARINE">
<description>Submarine</description>
</entry>
<entry value="13" name="MAV_TYPE_HEXAROTOR">
<description>Hexarotor</description>
</entry>
<entry value="14" name="MAV_TYPE_OCTOROTOR">
<description>Octorotor</description>
</entry>
<entry value="15" name="MAV_TYPE_TRICOPTER">
<description>Tricopter</description>
</entry>
<entry value="16" name="MAV_TYPE_FLAPPING_WING">
<description>Flapping wing</description>
</entry>
<entry value="17" name="MAV_TYPE_KITE">
<description>Kite</description>
</entry>
<entry value="18" name="MAV_TYPE_ONBOARD_CONTROLLER">
<description>Onboard companion controller</description>
</entry>
<entry value="19" name="MAV_TYPE_VTOL_TAILSITTER_DUOROTOR">
<description>Two-rotor Tailsitter VTOL that additionally uses control surfaces in vertical operation. Note, value previously named MAV_TYPE_VTOL_DUOROTOR.</description>
</entry>
<entry value="20" name="MAV_TYPE_VTOL_TAILSITTER_QUADROTOR">
<description>Quad-rotor Tailsitter VTOL using a V-shaped quad config in vertical operation. Note: value previously named MAV_TYPE_VTOL_QUADROTOR.</description>
</entry>
<entry value="21" name="MAV_TYPE_VTOL_TILTROTOR">
<description>Tiltrotor VTOL</description>
</entry>
<entry value="22" name="MAV_TYPE_VTOL_FIXEDROTOR">
<description>VTOL with separate fixed rotors for hover and cruise flight. Fuselage and wings stay (nominally) horizontal in all flight phases.</description>
</entry>
<entry value="23" name="MAV_TYPE_VTOL_TAILSITTER">
<description>Tailsitter VTOL. Fuselage and wings orientation changes depending on flight phase: vertical for hover, horizontal for cruise. Use more specific VTOL MAV_TYPE_VTOL_DUOROTOR or MAV_TYPE_VTOL_QUADROTOR if appropriate.</description>
</entry>
<!-- Entries up to 25 reserved for other VTOL airframes -->
<entry value="24" name="MAV_TYPE_VTOL_RESERVED4">
<description>VTOL reserved 4</description>
</entry>
<entry value="25" name="MAV_TYPE_VTOL_RESERVED5">
<description>VTOL reserved 5</description>
</entry>
<entry value="26" name="MAV_TYPE_GIMBAL">
<description>Gimbal</description>
</entry>
<entry value="27" name="MAV_TYPE_ADSB">
<description>ADSB system</description>
</entry>
<entry value="28" name="MAV_TYPE_PARAFOIL">
<description>Steerable, nonrigid airfoil</description>
</entry>
<entry value="29" name="MAV_TYPE_DODECAROTOR">
<description>Dodecarotor</description>
</entry>
<entry value="30" name="MAV_TYPE_CAMERA">
<description>Camera</description>
</entry>
<entry value="31" name="MAV_TYPE_CHARGING_STATION">
<description>Charging station</description>
</entry>
<entry value="32" name="MAV_TYPE_FLARM">
<description>FLARM collision avoidance system</description>
</entry>
<entry value="33" name="MAV_TYPE_SERVO">
<description>Servo</description>
</entry>
<entry value="34" name="MAV_TYPE_ODID">
<description>Open Drone ID. See https://mavlink.io/en/services/opendroneid.html.</description>
</entry>
<entry value="35" name="MAV_TYPE_DECAROTOR">
<description>Decarotor</description>
</entry>
<entry value="36" name="MAV_TYPE_BATTERY">
<description>Battery</description>
</entry>
</enum>
<enum name="MAV_MODE_FLAG" bitmask="true">
<description>These flags encode the MAV mode.</description>
<entry value="128" name="MAV_MODE_FLAG_SAFETY_ARMED">
<description>0b10000000 MAV safety set to armed. Motors are enabled / running / can start. Ready to fly. Additional note: this flag is to be ignore when sent in the command MAV_CMD_DO_SET_MODE and MAV_CMD_COMPONENT_ARM_DISARM shall be used instead. The flag can still be used to report the armed state.</description>
</entry>
<entry value="64" name="MAV_MODE_FLAG_MANUAL_INPUT_ENABLED">
<description>0b01000000 remote control input is enabled.</description>
</entry>
<entry value="32" name="MAV_MODE_FLAG_HIL_ENABLED">
<description>0b00100000 hardware in the loop simulation. All motors / actuators are blocked, but internal software is full operational.</description>
</entry>
<entry value="16" name="MAV_MODE_FLAG_STABILIZE_ENABLED">
<description>0b00010000 system stabilizes electronically its attitude (and optionally position). It needs however further control inputs to move around.</description>
</entry>
<entry value="8" name="MAV_MODE_FLAG_GUIDED_ENABLED">
<description>0b00001000 guided mode enabled, system flies waypoints / mission items.</description>
</entry>
<entry value="4" name="MAV_MODE_FLAG_AUTO_ENABLED">
<description>0b00000100 autonomous mode enabled, system finds its own goal positions. Guided flag can be set or not, depends on the actual implementation.</description>
</entry>
<entry value="2" name="MAV_MODE_FLAG_TEST_ENABLED">
<description>0b00000010 system has a test mode enabled. This flag is intended for temporary system tests and should not be used for stable implementations.</description>
</entry>
<entry value="1" name="MAV_MODE_FLAG_CUSTOM_MODE_ENABLED">
<description>0b00000001 Reserved for future use.</description>
</entry>
</enum>
<enum name="MAV_MODE_FLAG_DECODE_POSITION" bitmask="true">
<description>These values encode the bit positions of the decode position. These values can be used to read the value of a flag bit by combining the base_mode variable with AND with the flag position value. The result will be either 0 or 1, depending on if the flag is set or not.</description>
<entry value="128" name="MAV_MODE_FLAG_DECODE_POSITION_SAFETY">
<description>First bit: 10000000</description>
</entry>
<entry value="64" name="MAV_MODE_FLAG_DECODE_POSITION_MANUAL">
<description>Second bit: 01000000</description>
</entry>
<entry value="32" name="MAV_MODE_FLAG_DECODE_POSITION_HIL">
<description>Third bit: 00100000</description>
</entry>
<entry value="16" name="MAV_MODE_FLAG_DECODE_POSITION_STABILIZE">
<description>Fourth bit: 00010000</description>
</entry>
<entry value="8" name="MAV_MODE_FLAG_DECODE_POSITION_GUIDED">
<description>Fifth bit: 00001000</description>
</entry>
<entry value="4" name="MAV_MODE_FLAG_DECODE_POSITION_AUTO">
<description>Sixth bit: 00000100</description>
</entry>
<entry value="2" name="MAV_MODE_FLAG_DECODE_POSITION_TEST">
<description>Seventh bit: 00000010</description>
</entry>
<entry value="1" name="MAV_MODE_FLAG_DECODE_POSITION_CUSTOM_MODE">
<description>Eighth bit: 00000001</description>
</entry>
</enum>
<enum name="MAV_STATE">
<entry value="0" name="MAV_STATE_UNINIT">
<description>Uninitialized system, state is unknown.</description>
</entry>
<entry value="1" name="MAV_STATE_BOOT">
<description>System is booting up.</description>
</entry>
<entry value="2" name="MAV_STATE_CALIBRATING">
<description>System is calibrating and not flight-ready.</description>
</entry>
<entry value="3" name="MAV_STATE_STANDBY">
<description>System is grounded and on standby. It can be launched any time.</description>
</entry>
<entry value="4" name="MAV_STATE_ACTIVE">
<description>System is active and might be already airborne. Motors are engaged.</description>
</entry>
<entry value="5" name="MAV_STATE_CRITICAL">
<description>System is in a non-normal flight mode. It can however still navigate.</description>
</entry>
<entry value="6" name="MAV_STATE_EMERGENCY">
<description>System is in a non-normal flight mode. It lost control over parts or over the whole airframe. It is in mayday and going down.</description>
</entry>
<entry value="7" name="MAV_STATE_POWEROFF">
<description>System just initialized its power-down sequence, will shut down now.</description>
</entry>
<entry value="8" name="MAV_STATE_FLIGHT_TERMINATION">
<description>System is terminating itself.</description>
</entry>
</enum>
<enum name="MAV_COMPONENT">
<description>Component ids (values) for the different types and instances of onboard hardware/software that might make up a MAVLink system (autopilot, cameras, servos, GPS systems, avoidance systems etc.).
Components must use the appropriate ID in their source address when sending messages. Components can also use IDs to determine if they are the intended recipient of an incoming message. The MAV_COMP_ID_ALL value is used to indicate messages that must be processed by all components.
When creating new entries, components that can have multiple instances (e.g. cameras, servos etc.) should be allocated sequential values. An appropriate number of values should be left free after these components to allow the number of instances to be expanded.</description>
<entry value="0" name="MAV_COMP_ID_ALL">
<description>Target id (target_component) used to broadcast messages to all components of the receiving system. Components should attempt to process messages with this component ID and forward to components on any other interfaces. Note: This is not a valid *source* component id for a message.</description>
</entry>
<entry value="1" name="MAV_COMP_ID_AUTOPILOT1">
<description>System flight controller component ("autopilot"). Only one autopilot is expected in a particular system.</description>
</entry>
<!-- Component ids from 25-99 are reserved for private OEM component definitions (and may be incompatible with other private components). Note that if this range is later reduced, higher ids will be reallocated first. -->
<entry value="25" name="MAV_COMP_ID_USER1">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="26" name="MAV_COMP_ID_USER2">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="27" name="MAV_COMP_ID_USER3">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="28" name="MAV_COMP_ID_USER4">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="29" name="MAV_COMP_ID_USER5">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="30" name="MAV_COMP_ID_USER6">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="31" name="MAV_COMP_ID_USER7">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="32" name="MAV_COMP_ID_USER8">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="33" name="MAV_COMP_ID_USER9">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="34" name="MAV_COMP_ID_USER10">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="35" name="MAV_COMP_ID_USER11">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="36" name="MAV_COMP_ID_USER12">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="37" name="MAV_COMP_ID_USER13">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="38" name="MAV_COMP_ID_USER14">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="39" name="MAV_COMP_ID_USER15">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="40" name="MAV_COMP_ID_USER16">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="41" name="MAV_COMP_ID_USER17">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="42" name="MAV_COMP_ID_USER18">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="43" name="MAV_COMP_ID_USER19">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="44" name="MAV_COMP_ID_USER20">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="45" name="MAV_COMP_ID_USER21">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="46" name="MAV_COMP_ID_USER22">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="47" name="MAV_COMP_ID_USER23">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="48" name="MAV_COMP_ID_USER24">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="49" name="MAV_COMP_ID_USER25">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="50" name="MAV_COMP_ID_USER26">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="51" name="MAV_COMP_ID_USER27">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="52" name="MAV_COMP_ID_USER28">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="53" name="MAV_COMP_ID_USER29">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="54" name="MAV_COMP_ID_USER30">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="55" name="MAV_COMP_ID_USER31">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="56" name="MAV_COMP_ID_USER32">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="57" name="MAV_COMP_ID_USER33">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="58" name="MAV_COMP_ID_USER34">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="59" name="MAV_COMP_ID_USER35">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="60" name="MAV_COMP_ID_USER36">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="61" name="MAV_COMP_ID_USER37">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="62" name="MAV_COMP_ID_USER38">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="63" name="MAV_COMP_ID_USER39">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="64" name="MAV_COMP_ID_USER40">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="65" name="MAV_COMP_ID_USER41">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="66" name="MAV_COMP_ID_USER42">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="67" name="MAV_COMP_ID_USER43">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="68" name="MAV_COMP_ID_TELEMETRY_RADIO">
<description>Telemetry radio (e.g. SiK radio, or other component that emits RADIO_STATUS messages).</description>
</entry>
<entry value="69" name="MAV_COMP_ID_USER45">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="70" name="MAV_COMP_ID_USER46">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="71" name="MAV_COMP_ID_USER47">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="72" name="MAV_COMP_ID_USER48">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="73" name="MAV_COMP_ID_USER49">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="74" name="MAV_COMP_ID_USER50">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="75" name="MAV_COMP_ID_USER51">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="76" name="MAV_COMP_ID_USER52">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="77" name="MAV_COMP_ID_USER53">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="78" name="MAV_COMP_ID_USER54">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="79" name="MAV_COMP_ID_USER55">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="80" name="MAV_COMP_ID_USER56">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="81" name="MAV_COMP_ID_USER57">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="82" name="MAV_COMP_ID_USER58">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="83" name="MAV_COMP_ID_USER59">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="84" name="MAV_COMP_ID_USER60">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="85" name="MAV_COMP_ID_USER61">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="86" name="MAV_COMP_ID_USER62">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="87" name="MAV_COMP_ID_USER63">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="88" name="MAV_COMP_ID_USER64">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="89" name="MAV_COMP_ID_USER65">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="90" name="MAV_COMP_ID_USER66">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="91" name="MAV_COMP_ID_USER67">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="92" name="MAV_COMP_ID_USER68">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="93" name="MAV_COMP_ID_USER69">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="94" name="MAV_COMP_ID_USER70">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="95" name="MAV_COMP_ID_USER71">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="96" name="MAV_COMP_ID_USER72">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="97" name="MAV_COMP_ID_USER73">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="98" name="MAV_COMP_ID_USER74">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="99" name="MAV_COMP_ID_USER75">
<description>Id for a component on privately managed MAVLink network. Can be used for any purpose but may not be published by components outside of the private network.</description>
</entry>
<entry value="100" name="MAV_COMP_ID_CAMERA">
<description>Camera #1.</description>
</entry>
<entry value="101" name="MAV_COMP_ID_CAMERA2">
<description>Camera #2.</description>
</entry>
<entry value="102" name="MAV_COMP_ID_CAMERA3">
<description>Camera #3.</description>
</entry>
<entry value="103" name="MAV_COMP_ID_CAMERA4">
<description>Camera #4.</description>
</entry>
<entry value="104" name="MAV_COMP_ID_CAMERA5">
<description>Camera #5.</description>
</entry>
<entry value="105" name="MAV_COMP_ID_CAMERA6">
<description>Camera #6.</description>
</entry>
<entry value="140" name="MAV_COMP_ID_SERVO1">
<description>Servo #1.</description>
</entry>
<entry value="141" name="MAV_COMP_ID_SERVO2">
<description>Servo #2.</description>
</entry>
<entry value="142" name="MAV_COMP_ID_SERVO3">
<description>Servo #3.</description>
</entry>
<entry value="143" name="MAV_COMP_ID_SERVO4">
<description>Servo #4.</description>
</entry>
<entry value="144" name="MAV_COMP_ID_SERVO5">
<description>Servo #5.</description>
</entry>
<entry value="145" name="MAV_COMP_ID_SERVO6">
<description>Servo #6.</description>
</entry>
<entry value="146" name="MAV_COMP_ID_SERVO7">
<description>Servo #7.</description>
</entry>
<entry value="147" name="MAV_COMP_ID_SERVO8">
<description>Servo #8.</description>
</entry>
<entry value="148" name="MAV_COMP_ID_SERVO9">
<description>Servo #9.</description>
</entry>
<entry value="149" name="MAV_COMP_ID_SERVO10">
<description>Servo #10.</description>
</entry>
<entry value="150" name="MAV_COMP_ID_SERVO11">
<description>Servo #11.</description>
</entry>
<entry value="151" name="MAV_COMP_ID_SERVO12">
<description>Servo #12.</description>
</entry>
<entry value="152" name="MAV_COMP_ID_SERVO13">
<description>Servo #13.</description>
</entry>
<entry value="153" name="MAV_COMP_ID_SERVO14">
<description>Servo #14.</description>
</entry>
<entry value="154" name="MAV_COMP_ID_GIMBAL">
<description>Gimbal #1.</description>
</entry>
<entry value="155" name="MAV_COMP_ID_LOG">
<description>Logging component.</description>
</entry>
<entry value="156" name="MAV_COMP_ID_ADSB">
<description>Automatic Dependent Surveillance-Broadcast (ADS-B) component.</description>
</entry>
<entry value="157" name="MAV_COMP_ID_OSD">
<description>On Screen Display (OSD) devices for video links.</description>
</entry>
<entry value="158" name="MAV_COMP_ID_PERIPHERAL">
<description>Generic autopilot peripheral component ID. Meant for devices that do not implement the parameter microservice.</description>
</entry>
<entry value="159" name="MAV_COMP_ID_QX1_GIMBAL">
<deprecated since="2018-11" replaced_by="MAV_COMP_ID_GIMBAL">All gimbals should use MAV_COMP_ID_GIMBAL.</deprecated>
<description>Gimbal ID for QX1.</description>
</entry>
<entry value="160" name="MAV_COMP_ID_FLARM">
<description>FLARM collision alert component.</description>
</entry>
<entry value="171" name="MAV_COMP_ID_GIMBAL2">
<description>Gimbal #2.</description>
</entry>
<entry value="172" name="MAV_COMP_ID_GIMBAL3">
<description>Gimbal #3.</description>
</entry>
<entry value="173" name="MAV_COMP_ID_GIMBAL4">
<description>Gimbal #4</description>
</entry>
<entry value="174" name="MAV_COMP_ID_GIMBAL5">
<description>Gimbal #5.</description>
</entry>
<entry value="175" name="MAV_COMP_ID_GIMBAL6">
<description>Gimbal #6.</description>
</entry>
<entry value="180" name="MAV_COMP_ID_BATTERY">
<description>Battery #1.</description>
</entry>
<entry value="181" name="MAV_COMP_ID_BATTERY2">
<description>Battery #2.</description>
</entry>
<entry value="190" name="MAV_COMP_ID_MISSIONPLANNER">
<description>Component that can generate/supply a mission flight plan (e.g. GCS or developer API).</description>
</entry>
<entry value="191" name="MAV_COMP_ID_ONBOARD_COMPUTER">
<description>Component that lives on the onboard computer (companion computer) and has some generic functionalities, such as settings system parameters and monitoring the status of some processes that don't directly speak mavlink and so on.</description>
</entry>
<!-- Component ids from 192-194 are reserved for any future mavlink components related to the mission computer. -->
<entry value="195" name="MAV_COMP_ID_PATHPLANNER">
<description>Component that finds an optimal path between points based on a certain constraint (e.g. minimum snap, shortest path, cost, etc.).</description>
</entry>
<entry value="196" name="MAV_COMP_ID_OBSTACLE_AVOIDANCE">
<description>Component that plans a collision free path between two points.</description>
</entry>
<entry value="197" name="MAV_COMP_ID_VISUAL_INERTIAL_ODOMETRY">
<description>Component that provides position estimates using VIO techniques.</description>
</entry>
<entry value="198" name="MAV_COMP_ID_PAIRING_MANAGER">
<description>Component that manages pairing of vehicle and GCS.</description>
</entry>
<entry value="200" name="MAV_COMP_ID_IMU">
<description>Inertial Measurement Unit (IMU) #1.</description>
</entry>
<entry value="201" name="MAV_COMP_ID_IMU_2">
<description>Inertial Measurement Unit (IMU) #2.</description>
</entry>
<entry value="202" name="MAV_COMP_ID_IMU_3">
<description>Inertial Measurement Unit (IMU) #3.</description>
</entry>
<entry value="220" name="MAV_COMP_ID_GPS">
<description>GPS #1.</description>
</entry>
<entry value="221" name="MAV_COMP_ID_GPS2">
<description>GPS #2.</description>
</entry>
<entry value="236" name="MAV_COMP_ID_ODID_TXRX_1">
<description>Open Drone ID transmitter/receiver (Bluetooth/WiFi/Internet).</description>
</entry>
<entry value="237" name="MAV_COMP_ID_ODID_TXRX_2">
<description>Open Drone ID transmitter/receiver (Bluetooth/WiFi/Internet).</description>
</entry>
<entry value="238" name="MAV_COMP_ID_ODID_TXRX_3">
<description>Open Drone ID transmitter/receiver (Bluetooth/WiFi/Internet).</description>
</entry>
<entry value="240" name="MAV_COMP_ID_UDP_BRIDGE">
<description>Component to bridge MAVLink to UDP (i.e. from a UART).</description>
</entry>
<entry value="241" name="MAV_COMP_ID_UART_BRIDGE">
<description>Component to bridge to UART (i.e. from UDP).</description>
</entry>
<entry value="242" name="MAV_COMP_ID_TUNNEL_NODE">
<description>Component handling TUNNEL messages (e.g. vendor specific GUI of a component).</description>
</entry>
<entry value="250" name="MAV_COMP_ID_SYSTEM_CONTROL">
<deprecated since="2018-11" replaced_by="MAV_COMP_ID_ALL">System control does not require a separate component ID.</deprecated>
<description>Component for handling system messages (e.g. to ARM, takeoff, etc.).</description>
</entry>
</enum>
<enum name="FIRMWARE_VERSION_TYPE">
<description>These values define the type of firmware release. These values indicate the first version or release of this type. For example the first alpha release would be 64, the second would be 65.</description>
<entry value="0" name="FIRMWARE_VERSION_TYPE_DEV">
......@@ -1425,21 +769,21 @@
</entry>
</enum>
<enum name="COMP_METADATA_TYPE">
<description>Possible values for COMPONENT_INFORMATION.comp_metadata_type.</description>
<description>Supported component metadata types. These are used in the "general" metadata file returned by COMPONENT_INFORMATION to provide information about supported metadata types. The types are not used directly in MAVLink messages.</description>
<entry value="0" name="COMP_METADATA_TYPE_GENERAL">
<description>General information which also includes information on other optional supported COMP_METADATA_TYPE's. Must be supported. Only downloadable from vehicle.</description>
<description>General information about the component. General metadata includes information about other COMP_METADATA_TYPEs supported by the component. This type must be supported and must be downloadable from vehicle.</description>
</entry>
<entry value="1" name="COMP_METADATA_TYPE_PARAMETER">
<description>Parameter meta data.</description>
</entry>
<entry value="2" name="COMP_METADATA_TYPE_COMMANDS">
<description>Meta data which specifies the commands the vehicle supports. (WIP)</description>
<description>Meta data that specifies which commands and command parameters the vehicle supports. (WIP)</description>
</entry>
<entry value="3" name="COMP_METADATA_TYPE_PERIPHERALS">
<description>Meta data which specifies potential external peripherals that do not talk MAVLink</description>
<description>Meta data that specifies external non-MAVLink peripherals.</description>
</entry>
<entry value="4" name="COMP_METADATA_TYPE_EVENTS">
<description>Meta data for events interface</description>
<description>Meta data for the events interface.</description>
</entry>
</enum>
<enum name="PARAM_TRANSACTION_TRANSPORT">
......@@ -1664,7 +1008,7 @@
</entry>
<entry value="85" name="MAV_CMD_NAV_VTOL_LAND" hasLocation="true" isDestination="true">
<description>Land using VTOL mode</description>
<param index="1">Empty</param>
<param index="1" label="Land Options" enum="NAV_VTOL_LAND_OPTIONS">Landing behaviour.</param>
<param index="2">Empty</param>
<param index="3" label="Approach Altitude" units="m">Approach altitude (with the same reference as the Altitude field). NaN if unspecified.</param>
<param index="4" label="Yaw" units="deg">Yaw angle. NaN to use the current system yaw heading mode (e.g. yaw towards next waypoint, yaw to home, etc.).</param>
......@@ -4980,6 +4324,19 @@
<description>Unit is sometimes working, sometimes not.</description>
</entry>
</enum>
<enum name="NAV_VTOL_LAND_OPTIONS">
<entry value="0" name="NAV_VTOL_LAND_OPTIONS_DEFAULT">
<description>Default autopilot landing behaviour.</description>
</entry>
<entry value="1" name="NAV_VTOL_LAND_OPTIONS_FW_DESCENT">
<description>Descend in fixed wing mode, transitioning to multicopter mode for vertical landing when close to the ground.
The fixed wing descent pattern is at the discretion of the vehicle (e.g. transition altitude, loiter direction, radius, and speed, etc.).
</description>
</entry>
<entry value="2" name="NAV_VTOL_LAND_OPTIONS_HOVER_DESCENT">
<description>Land in multicopter mode on reaching the landing co-ordinates (the whole landing is by "hover descent").</description>
</entry>
</enum>
<enum name="MAV_WINCH_STATUS_FLAG" bitmask="true">
<description>Winch status flags used in WINCH_STATUS</description>
<entry value="1" name="MAV_WINCH_STATUS_HEALTHY">
......@@ -5019,25 +4376,6 @@
</enum>
</enums>
<messages>
<message id="0" name="HEARTBEAT">
<description>The heartbeat message shows that a system or component is present and responding. The type and autopilot fields (along with the message component id), allow the receiving system to treat further messages from this system appropriately (e.g. by laying out the user interface based on the autopilot). This microservice is documented at https://mavlink.io/en/services/heartbeat.html</description>
<field type="uint8_t" name="type" enum="MAV_TYPE">Vehicle or component type. For a flight controller component the vehicle type (quadrotor, helicopter, etc.). For other components the component type (e.g. camera, gimbal, etc.). This should be used in preference to component id for identifying the component type.</field>
<field type="uint8_t" name="autopilot" enum="MAV_AUTOPILOT">Autopilot type / class. Use MAV_AUTOPILOT_INVALID for components that are not flight controllers.</field>
<field type="uint8_t" name="base_mode" enum="MAV_MODE_FLAG" display="bitmask">System mode bitmap.</field>
<field type="uint32_t" name="custom_mode">A bitfield for use for autopilot-specific flags</field>
<field type="uint8_t" name="system_status" enum="MAV_STATE">System status flag.</field>
<field type="uint8_t_mavlink_version" name="mavlink_version">MAVLink version, not writable by user, gets added by protocol because of magic data type: uint8_t_mavlink_version</field>
</message>
<message id="300" name="PROTOCOL_VERSION">
<wip/>
<!-- This message is work-in-progress and it can therefore change. It should NOT be used in stable production environments. -->
<description>Version and capability of protocol version. This message can be requested with MAV_CMD_REQUEST_MESSAGE and is used as part of the handshaking to establish which MAVLink version should be used on the network. Every node should respond to a request for PROTOCOL_VERSION to enable the handshaking. Library implementers should consider adding this into the default decoding state machine to allow the protocol core to respond directly.</description>
<field type="uint16_t" name="version">Currently active MAVLink version number * 100: v1.0 is 100, v2.0 is 200, etc.</field>
<field type="uint16_t" name="min_version">Minimum MAVLink version supported</field>
<field type="uint16_t" name="max_version">Maximum MAVLink version supported (set to the same value as version by default)</field>
<field type="uint8_t[8]" name="spec_version_hash">The first 8 bytes (not characters printed in hex!) of the git hash.</field>
<field type="uint8_t[8]" name="library_version_hash">The first 8 bytes (not characters printed in hex!) of the git hash.</field>
</message>
<message id="1" name="SYS_STATUS">
<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 whether the system is currently active or not and if an emergency occurred. During the CRITICAL and EMERGENCY states the MAV is still considered to be active, but should start emergency procedures autonomously. After a failure occurred it should first move from active to critical to allow manual intervention and then move to emergency after a certain timeout.</description>
<field type="uint32_t" name="onboard_control_sensors_present" enum="MAV_SYS_STATUS_SENSOR" display="bitmask" print_format="0x%04x">Bitmap showing which onboard controllers and sensors are present. Value of 0: not present. Value of 1: present.</field>
......@@ -5053,10 +4391,6 @@
<field type="uint16_t" name="errors_count2">Autopilot-specific errors</field>
<field type="uint16_t" name="errors_count3">Autopilot-specific errors</field>
<field type="uint16_t" name="errors_count4">Autopilot-specific errors</field>
<extensions/>
<field type="uint32_t" name="onboard_control_sensors_present_extended" enum="MAV_SYS_STATUS_SENSOR_EXTENDED" display="bitmask" print_format="0x%04x">Bitmap showing which onboard controllers and sensors are present. Value of 0: not present. Value of 1: present.</field>
<field type="uint32_t" name="onboard_control_sensors_enabled_extended" enum="MAV_SYS_STATUS_SENSOR_EXTENDED" display="bitmask" print_format="0x%04x">Bitmap showing which onboard controllers and sensors are enabled: Value of 0: not enabled. Value of 1: enabled.</field>
<field type="uint32_t" name="onboard_control_sensors_health_extended" enum="MAV_SYS_STATUS_SENSOR_EXTENDED" display="bitmask" print_format="0x%04x">Bitmap showing which onboard controllers and sensors have an error (or are operational). Value of 0: error. Value of 1: healthy.</field>
</message>
<message id="2" name="SYSTEM_TIME">
<description>The system time is the time of the master clock, typically the computer clock of the main onboard computer.</description>
......@@ -5498,7 +4832,7 @@
<field type="float[9]" name="covariance" invalid="[NaN,]">Row-major representation of a 3x3 attitude covariance matrix (states: roll, pitch, yaw; first three entries are the first ROW, next three entries are the second row, etc.). If unknown, assign NaN value to first element in the array.</field>
</message>
<message id="62" name="NAV_CONTROLLER_OUTPUT">
<description>The state of the fixed wing navigation and position controller.</description>
<description>The state of the navigation and position controller.</description>
<field type="float" name="nav_roll" units="deg">Current desired roll</field>
<field type="float" name="nav_pitch" units="deg">Current desired pitch</field>
<field type="int16_t" name="nav_bearing" units="deg">Current desired heading</field>
......@@ -5577,18 +4911,13 @@
<field type="uint8_t" name="on_off">1 stream is enabled, 0 stream is stopped.</field>
</message>
<message id="69" name="MANUAL_CONTROL">
<description>This message provides an API for manually controlling the vehicle using standard joystick axes nomenclature, along with a joystick-like input device. Unused axes can be disabled and buttons states are transmitted as individual on/off bits of a bitmask</description>
<description>This message provides an API for manually controlling the vehicle using standard joystick axes nomenclature, along with a joystick-like input device. Unused axes can be disabled an buttons are also transmit as boolean values of their </description>
<field type="uint8_t" name="target">The system to be controlled.</field>
<field type="int16_t" name="x" invalid="INT16_MAX">X-axis, normalized to the range [-1000,1000]. A value of INT16_MAX indicates that this axis is invalid. Generally corresponds to forward(1000)-backward(-1000) movement on a joystick and the pitch of a vehicle.</field>
<field type="int16_t" name="y" invalid="INT16_MAX">Y-axis, normalized to the range [-1000,1000]. A value of INT16_MAX indicates that this axis is invalid. Generally corresponds to left(-1000)-right(1000) movement on a joystick and the roll of a vehicle.</field>
<field type="int16_t" name="z" invalid="INT16_MAX">Z-axis, normalized to the range [-1000,1000]. A value of INT16_MAX indicates that this axis is invalid. Generally corresponds to a separate slider movement with maximum being 1000 and minimum being -1000 on a joystick and the thrust of a vehicle. Positive values are positive thrust, negative values are negative thrust.</field>
<field type="int16_t" name="r" invalid="INT16_MAX">R-axis, normalized to the range [-1000,1000]. A value of INT16_MAX indicates that this axis is invalid. Generally corresponds to a twisting of the joystick, with counter-clockwise being 1000 and clockwise being -1000, and the yaw of a vehicle.</field>
<field type="uint16_t" name="buttons">A bitfield corresponding to the joystick buttons' 0-15 current state, 1 for pressed, 0 for released. The lowest bit corresponds to Button 1.</field>
<extensions/>
<field type="uint16_t" name="buttons2">A bitfield corresponding to the joystick buttons' 16-31 current state, 1 for pressed, 0 for released. The lowest bit corresponds to Button 16.</field>
<field type="uint8_t" name="enabled_extensions">Set bits to 1 to indicate which of the following extension fields contain valid data: bit 0: pitch, bit 1: roll.</field>
<field type="int16_t" name="s">Pitch-only-axis, normalized to the range [-1000,1000]. Generally corresponds to pitch on vehicles with additional degrees of freedom. Valid if bit 0 of enabled_extensions field is set. Set to 0 if invalid.</field>
<field type="int16_t" name="t">Roll-only-axis, normalized to the range [-1000,1000]. Generally corresponds to roll on vehicles with additional degrees of freedom. Valid if bit 1 of enabled_extensions field is set. Set to 0 if invalid.</field>
<field type="uint16_t" name="buttons">A bitfield corresponding to the joystick buttons' current state, 1 for pressed, 0 for released. The lowest bit corresponds to Button 1.</field>
</message>
<message id="70" name="RC_CHANNELS_OVERRIDE">
<description>The RAW values of the RC channels sent to the MAV to override info received from the RC radio. The standard PPM modulation is as follows: 1000 microseconds: 0%, 2000 microseconds: 100%. Individual receivers/transmitters might violate this specification. Note carefully the semantic differences between the first 8 channels and the subsequent channels</description>
......@@ -6185,9 +5514,6 @@
<field type="uint32_t" name="baudrate" units="bits/s">Baudrate of transfer. Zero means no change.</field>
<field type="uint8_t" name="count" units="bytes">how many bytes in this transfer</field>
<field type="uint8_t[70]" name="data">serial data</field>
<extensions/>
<field type="uint8_t" name="target_system">System ID</field>
<field type="uint8_t" name="target_component">Component ID</field>
</message>
<message id="127" name="GPS_RTK">
<description>RTK GPS data. Gives information on the relative baseline calculation the GPS is reporting</description>
......@@ -6694,7 +6020,7 @@
<field type="uint8_t" name="target_system">System ID (0 for broadcast)</field>
<field type="uint8_t" name="target_component">Component ID (0 for broadcast)</field>
<field type="uint16_t" name="message_type">A code that identifies the software component that understands this message (analogous to USB device classes or mime type strings). If this code is less than 32768, it is considered a 'registered' protocol extension and the corresponding entry should be added to https://github.com/mavlink/mavlink/definition_files/extension_message_ids.xml. Software creators can register blocks of message IDs as needed (useful for GCS specific metadata, etc...). Message_types greater than 32767 are considered local experiments and should not be checked in to any widely distributed codebase.</field>
<field type="uint8_t[2]" name="payload">Variable length payload. The length must be encoded in the payload as part of the message_type protocol, e.g. by including the length as payload data, or by terminating the payload data with a non-zero marker. This is required in order to reconstruct zero-terminated payloads that are (or otherwise would be) trimmed by MAVLink 2 empty-byte truncation. The entire content of the payload block is opaque unless you understand the encoding message_type. The particular encoding used can be extension specific and might not always be documented as part of the MAVLink specification.</field>
<field type="uint8_t[249]" name="payload">Variable length payload. The length must be encoded in the payload as part of the message_type protocol, e.g. by including the length as payload data, or by terminating the payload data with a non-zero marker. This is required in order to reconstruct zero-terminated payloads that are (or otherwise would be) trimmed by MAVLink 2 empty-byte truncation. The entire content of the payload block is opaque unless you understand the encoding message_type. The particular encoding used can be extension specific and might not always be documented as part of the MAVLink specification.</field>
</message>
<message id="249" name="MEMORY_VECT">
<description>Send raw controller memory. The use of this message is discouraged for normal packets, but a quite efficient way for testing new messages and getting experimental debug output.</description>
......@@ -7606,9 +6932,9 @@
<field type="float" name="loiter_radius">Current loiter radius</field>
<field type="float" name="time_to_home">Time to home in seconds</field>
<field type="float" name="max_distance_from_home">Max distance from home in meters</field>
<field type="float" name="reserved2">reserved2</field>
<field type="float" name="reserved3">reserved3</field>
<field type="float" name="reserved4">reserved4</field>
<field type="float" name="time_to_rally">Time to rally in seconds</field>
<field type="float" name="max_distance_from_rally">Max distance from rally in meters</field>
<field type="uint8_t" name="return_destination">Selected destination in return mode. 0:NOT_ACTIVE, 1:HOME, 2:RALLY, 3:MISSION_LAND</field>
<field type="float" name="reserved5">reserved5</field>
</message>
<message id="15001" name="SERIAL_PASSTHROUGH">
......@@ -7640,7 +6966,7 @@
<field type="uint8_t" name="target_component">Component which should execute the command, 0 for all components</field>
<field type="int16_t" name="terrain_elevation">Terrain elevation</field>
</message>
<message id="15005" name="MISSION_ITEM_INT_CAP">
<message id="15005" name="MISSION_ITEM_INT_CAP">
<description>Message encoding a mission item. This message is emitted to announce
the presence of a mission item and to set a mission item on the system. The mission item can be either in x, y, z meters (type: LOCAL) or x:lat, y:lon, z:altitude. Local frame is Z-down, right handed (NED), global frame is Z-up, right handed (ENU). NaN or INT32_MAX may be used in float/integer params (respectively) to indicate optional/default values (e.g. to use the component's current latitude, yaw rather than a specific value). See also https://mavlink.io/en/services/mission.html.</description>
<field type="uint8_t" name="target_system">System ID</field>
......@@ -7663,6 +6989,7 @@
<field type="float" name="length">Length between circles</field>
<field type="float" name="bearing">Bearing of the pattern</field>
<field type="float" name="speed">Desired speed in waypoint</field>
<field type="uint8_t" name="silent_mode">0: Disabled, 1: Enabled. If enabled, will start flying in silent mode when waypoint reached</field>
</message>
<message id="15006" name="MISSION_REQUEST_INT_CAP">
<description>Request the information of the mission item with the sequence number seq. The response of the system to this message should be a MISSION_ITEM_INT message. https://mavlink.io/en/services/mission.html</description>
......@@ -7675,7 +7002,7 @@
<description>Properties of the CAP system that need to be reported more frequently then CAP_STATUS.</description>
<field type="uint64_t" name="utc_time">UTC time reported by the GPS.</field>
</message>
<message id="15008" name="MISSION_COUNT_CAP">
<message id="15008" name="MISSION_COUNT_CAP">
<description>This message is emitted as response to MISSION_REQUEST_LIST by the MAV and to initiate a write transaction. The GCS can then request the individual mission item based on the knowledge of the total number of waypoints.</description>
<field type="uint8_t" name="target_system">System ID</field>
<field type="uint8_t" name="target_component">Component ID</field>
......@@ -7690,5 +7017,27 @@
<extensions/>
<field type="uint8_t" name="mission_type" enum="MAV_MISSION_TYPE">Mission type.</field>
</message>
<message id="15010" name="SAFE_ALTITUDE_TO_DESTINATION">
<description>Highest point on the path to destination.</description>
<field type="uint8_t" name="target_system">System ID</field>
<field type="uint8_t" name="target_component">Component ID</field>
<field type="float" name="home">Safe altitude to home in meters</field>
<field type="float" name="rally">Safe altitude to rally in meters</field>
</message>
<message id="15011" name="UBLOX_SATELLITE_INFO">
<description>uBlox satellite information for each constellation. GNSS identifiers are the same as uBlox GNSS identifiers. Look at "u-blox M9 SPG 4.04" pdf specification</description>
<field type="uint8_t" name="target_system">System ID</field>
<field type="uint8_t" name="target_component">Component ID</field>
<field type="uint8_t[7]" name="visible">Visible satellites in each constellation. 0:GPS, 1:SBAS, 2:Galileo, 3:BeiDou, 4:IMES, 5:QZSS, 6:GLONASS</field>
<field type="uint8_t[7]" name="used">Used satellites in each constellation. 0:GPS, 1:SBAS, 2:Galileo, 3:BeiDou, 4:IMES, 5:QZSS, 6:GLONASS</field>
</message>
<message id="15012" name="SILENT_MODE">
<description>Silent Mode is flying without radio signal transmission. This mode powers off the radio.</description>
<field type="uint8_t" name="target_system">System ID</field>
<field type="uint8_t" name="target_component">Component ID</field>
<field type="uint8_t" name="state">Current silent mode state. 0:STATE_OFF_INTERNAL, 1:STATE_ON_INTERNAL, 2:STATE_OFF_EXTERNAL, 3:STATE_ON_EXTERNAL </field>
<field type="uint8_t" name="command">Command used to set silent mode state. 0:COMMAND_NONE_EXTERNAL (set by autopilot!), 1:COMMAND_OFF_EXTERNAL, 2:COMMAND_ON_EXTERNAL</field>
<field type="uint32_t" name="timeout">Current silent mode set timeout time in seconds</field>
</message>
</messages>
</mavlink>
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7