From d6a1b6d5a08514801086a42edfb49d14b0cff9c7 Mon Sep 17 00:00:00 2001 From: Thomas Stauber <48206725+ThomasRigi@users.noreply.github.com> Date: Mon, 1 Mar 2021 23:10:16 +0100 Subject: [PATCH] Add MAV_VTOL_STATE_QC field (#1569) --- message_definitions/v1.0/common.xml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/message_definitions/v1.0/common.xml b/message_definitions/v1.0/common.xml index b778cad67c..82db1cbce6 100644 --- a/message_definitions/v1.0/common.xml +++ b/message_definitions/v1.0/common.xml @@ -1936,7 +1936,8 @@ Request VTOL transition - The target VTOL state. Only MAV_VTOL_STATE_MC and MAV_VTOL_STATE_FW can be used. + The target VTOL state. For normal transitions, only MAV_VTOL_STATE_MC and MAV_VTOL_STATE_FW can be used. + Force immediate transition to the specified MAV_VTOL_STATE. 1: Force immediate, 0: normal transition. Can be used, for example, to trigger an emergency "Quadchute". Caution: Can be dangerous/damage vehicle, depending on autopilot implementation of this command. 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.