Commit d0fb5b84 authored by PX4BuildBot's avatar PX4BuildBot

autogenerated headers for rev...

autogenerated headers for rev https://github.com/mavlink/mavlink/tree/1ba233efffb54a7ed634160cd11855b3f5021b74
parent 2c4b0e9f
......@@ -7,7 +7,7 @@
#ifndef MAVLINK_VERSION_H
#define MAVLINK_VERSION_H
#define MAVLINK_BUILD_DATE "Thu Aug 02 2018"
#define MAVLINK_BUILD_DATE "Fri Aug 03 2018"
#define MAVLINK_WIRE_PROTOCOL_VERSION "2.0"
#define MAVLINK_MAX_DIALECT_PAYLOAD_SIZE 255
......
......@@ -7,7 +7,7 @@
#ifndef MAVLINK_VERSION_H
#define MAVLINK_VERSION_H
#define MAVLINK_BUILD_DATE "Thu Aug 02 2018"
#define MAVLINK_BUILD_DATE "Fri Aug 03 2018"
#define MAVLINK_WIRE_PROTOCOL_VERSION "2.0"
#define MAVLINK_MAX_DIALECT_PAYLOAD_SIZE 255
......
......@@ -7,7 +7,7 @@
#ifndef MAVLINK_VERSION_H
#define MAVLINK_VERSION_H
#define MAVLINK_BUILD_DATE "Thu Aug 02 2018"
#define MAVLINK_BUILD_DATE "Fri Aug 03 2018"
#define MAVLINK_WIRE_PROTOCOL_VERSION "2.0"
#define MAVLINK_MAX_DIALECT_PAYLOAD_SIZE 255
......
......@@ -1145,6 +1145,17 @@ typedef enum GPS_FIX_TYPE
} GPS_FIX_TYPE;
#endif
/** @brief RTK GPS baseline coordinate system, used for RTK corrections */
#ifndef HAVE_ENUM_RTK_BASELINE_COORDINATE_SYSTEM
#define HAVE_ENUM_RTK_BASELINE_COORDINATE_SYSTEM
typedef enum RTK_BASELINE_COORDINATE_SYSTEM
{
RTK_BASELINE_COORDINATE_SYSTEM_ECEF=0, /* Earth-centered, Earth-fixed | */
RTK_BASELINE_COORDINATE_SYSTEM_NED=1, /* North, East, Down | */
RTK_BASELINE_COORDINATE_SYSTEM_ENUM_END=2, /* | */
} RTK_BASELINE_COORDINATE_SYSTEM;
#endif
/** @brief Type of landing target */
#ifndef HAVE_ENUM_LANDING_TARGET_TYPE
#define HAVE_ENUM_LANDING_TARGET_TYPE
......@@ -1227,17 +1238,6 @@ typedef enum MAV_ARM_AUTH_DENIED_REASON
} MAV_ARM_AUTH_DENIED_REASON;
#endif
/** @brief RTK GPS baseline coordinate system, used for RTK corrections */
#ifndef HAVE_ENUM_RTK_BASELINE_COORDINATE_SYSTEM
#define HAVE_ENUM_RTK_BASELINE_COORDINATE_SYSTEM
typedef enum RTK_BASELINE_COORDINATE_SYSTEM
{
RTK_BASELINE_COORDINATE_SYSTEM_ECEF=0, /* Earth-centered, Earth-fixed | */
RTK_BASELINE_COORDINATE_SYSTEM_NED=1, /* North, East, Down | */
RTK_BASELINE_COORDINATE_SYSTEM_ENUM_END=2, /* | */
} RTK_BASELINE_COORDINATE_SYSTEM;
#endif
/** @brief RC type */
#ifndef HAVE_ENUM_RC_TYPE
#define HAVE_ENUM_RC_TYPE
......
......@@ -7,7 +7,7 @@
#ifndef MAVLINK_VERSION_H
#define MAVLINK_VERSION_H
#define MAVLINK_BUILD_DATE "Thu Aug 02 2018"
#define MAVLINK_BUILD_DATE "Fri Aug 03 2018"
#define MAVLINK_WIRE_PROTOCOL_VERSION "2.0"
#define MAVLINK_MAX_DIALECT_PAYLOAD_SIZE 255
......
......@@ -7,7 +7,7 @@
#ifndef MAVLINK_VERSION_H
#define MAVLINK_VERSION_H
#define MAVLINK_BUILD_DATE "Thu Aug 02 2018"
#define MAVLINK_BUILD_DATE "Fri Aug 03 2018"
#define MAVLINK_WIRE_PROTOCOL_VERSION "2.0"
#define MAVLINK_MAX_DIALECT_PAYLOAD_SIZE 255
......
......@@ -7,7 +7,7 @@
#ifndef MAVLINK_VERSION_H
#define MAVLINK_VERSION_H
#define MAVLINK_BUILD_DATE "Thu Aug 02 2018"
#define MAVLINK_BUILD_DATE "Fri Aug 03 2018"
#define MAVLINK_WIRE_PROTOCOL_VERSION "2.0"
#define MAVLINK_MAX_DIALECT_PAYLOAD_SIZE 255
......
......@@ -1701,6 +1701,11 @@
<description>Request VTOL transition</description>
<param index="1">The target VTOL state, as defined by ENUM MAV_VTOL_STATE. Only MAV_VTOL_STATE_MC and MAV_VTOL_STATE_FW can be used.</param>
</entry>
<entry value="3001" name="MAV_CMD_ARM_AUTHORIZATION_REQUEST">
<description>Request authorization to arm the vehicle to a external entity, the arm authorizer is responsible to request all data that is needs from the vehicle before authorize or deny the request. If approved the progress of command_ack message should be set with period of time that this authorization is valid in seconds or in case it was denied it should be set with one of the reasons in ARM_AUTH_DENIED_REASON.
</description>
<param index="1">Vehicle system id, this way ground station can request arm authorization on behalf of any vehicle</param>
</entry>
<entry value="4000" name="MAV_CMD_SET_GUIDED_SUBMODE_STANDARD">
<description>This command sets the submode to standard guided when vehicle is in guided mode. The vehicle holds position and altitude and the user can input the desired velocites along all three axes.
</description>
......@@ -1727,11 +1732,6 @@
<param index="6">Longitude</param>
<param index="7">Altitude</param>
</entry>
<entry value="3001" name="MAV_CMD_ARM_AUTHORIZATION_REQUEST">
<description>Request authorization to arm the vehicle to a external entity, the arm authorizer is responsible to request all data that is needs from the vehicle before authorize or deny the request. If approved the progress of command_ack message should be set with period of time that this authorization is valid in seconds or in case it was denied it should be set with one of the reasons in ARM_AUTH_DENIED_REASON.
</description>
<param index="1">Vehicle system id, this way ground station can request arm authorization on behalf of any vehicle</param>
</entry>
<entry value="5000" name="MAV_CMD_NAV_FENCE_RETURN_POINT">
<description>Fence return point. There can only be one fence return point.
</description>
......@@ -2840,6 +2840,15 @@
<description>PPP, 3D position.</description>
</entry>
</enum>
<enum name="RTK_BASELINE_COORDINATE_SYSTEM">
<description>RTK GPS baseline coordinate system, used for RTK corrections</description>
<entry value="0" name="RTK_BASELINE_COORDINATE_SYSTEM_ECEF">
<description>Earth-centered, Earth-fixed</description>
</entry>
<entry value="1" name="RTK_BASELINE_COORDINATE_SYSTEM_NED">
<description>North, East, Down</description>
</entry>
</enum>
<enum name="LANDING_TARGET_TYPE">
<description>Type of landing target</description>
<entry value="0" name="LANDING_TARGET_TYPE_LIGHT_BEACON">
......@@ -2941,15 +2950,6 @@
<description>Weather is not good to fly</description>
</entry>
</enum>
<enum name="RTK_BASELINE_COORDINATE_SYSTEM">
<description>RTK GPS baseline coordinate system, used for RTK corrections</description>
<entry value="0" name="RTK_BASELINE_COORDINATE_SYSTEM_ECEF">
<description>Earth-centered, Earth-fixed</description>
</entry>
<entry value="1" name="RTK_BASELINE_COORDINATE_SYSTEM_NED">
<description>North, East, Down</description>
</entry>
</enum>
<enum name="RC_TYPE">
<description>RC type</description>
<entry value="0" name="RC_TYPE_SPEKTRUM_DSM2">
......
......@@ -7,7 +7,7 @@
#ifndef MAVLINK_VERSION_H
#define MAVLINK_VERSION_H
#define MAVLINK_BUILD_DATE "Thu Aug 02 2018"
#define MAVLINK_BUILD_DATE "Fri Aug 03 2018"
#define MAVLINK_WIRE_PROTOCOL_VERSION "2.0"
#define MAVLINK_MAX_DIALECT_PAYLOAD_SIZE 9
......
......@@ -7,7 +7,7 @@
#ifndef MAVLINK_VERSION_H
#define MAVLINK_VERSION_H
#define MAVLINK_BUILD_DATE "Thu Aug 02 2018"
#define MAVLINK_BUILD_DATE "Fri Aug 03 2018"
#define MAVLINK_WIRE_PROTOCOL_VERSION "2.0"
#define MAVLINK_MAX_DIALECT_PAYLOAD_SIZE 255
......
......@@ -7,7 +7,7 @@
#ifndef MAVLINK_VERSION_H
#define MAVLINK_VERSION_H
#define MAVLINK_BUILD_DATE "Thu Aug 02 2018"
#define MAVLINK_BUILD_DATE "Fri Aug 03 2018"
#define MAVLINK_WIRE_PROTOCOL_VERSION "2.0"
#define MAVLINK_MAX_DIALECT_PAYLOAD_SIZE 255
......
......@@ -7,7 +7,7 @@
#ifndef MAVLINK_VERSION_H
#define MAVLINK_VERSION_H
#define MAVLINK_BUILD_DATE "Thu Aug 02 2018"
#define MAVLINK_BUILD_DATE "Fri Aug 03 2018"
#define MAVLINK_WIRE_PROTOCOL_VERSION "2.0"
#define MAVLINK_MAX_DIALECT_PAYLOAD_SIZE 179
......
......@@ -7,7 +7,7 @@
#ifndef MAVLINK_VERSION_H
#define MAVLINK_VERSION_H
#define MAVLINK_BUILD_DATE "Thu Aug 02 2018"
#define MAVLINK_BUILD_DATE "Fri Aug 03 2018"
#define MAVLINK_WIRE_PROTOCOL_VERSION "2.0"
#define MAVLINK_MAX_DIALECT_PAYLOAD_SIZE 255
......
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