MAVLink messages update Wed Oct 29 23:10:01 UTC 2025

Author: PX4BuildBot

en/messages/common.md

@@ -4663,7 +4663,7 @@ Value | Name | Description
 --- | --- | ---
 <a id='MAV_RESULT_ACCEPTED'></a>0 | [MAV_RESULT_ACCEPTED](#MAV_RESULT_ACCEPTED) | Command is valid (is supported and has valid parameters), and was executed. 
 <a id='MAV_RESULT_TEMPORARILY_REJECTED'></a>1 | [MAV_RESULT_TEMPORARILY_REJECTED](#MAV_RESULT_TEMPORARILY_REJECTED) | Command is valid, but cannot be executed at this time. This is used to indicate a problem that should be fixed just by waiting (e.g. a state machine is busy, can't arm because have not got GPS lock, etc.). Retrying later should work. 
-<a id='MAV_RESULT_DENIED'></a>2 | [MAV_RESULT_DENIED](#MAV_RESULT_DENIED) | Command is invalid (is supported but has invalid parameters). Retrying same command and parameters will not work. 
+<a id='MAV_RESULT_DENIED'></a>2 | [MAV_RESULT_DENIED](#MAV_RESULT_DENIED) | Command is invalid; it is supported but one or more parameter values are invalid (i.e. parameter reserved, value allowed by spec but not supported by flight stack, and so on). Retrying the same command and parameters will not work. 
 <a id='MAV_RESULT_UNSUPPORTED'></a>3 | [MAV_RESULT_UNSUPPORTED](#MAV_RESULT_UNSUPPORTED) | Command is not supported (unknown). 
 <a id='MAV_RESULT_FAILED'></a>4 | [MAV_RESULT_FAILED](#MAV_RESULT_FAILED) | Command is valid, but execution has failed. This is used to indicate any non-temporary or unexpected problem, i.e. any problem that must be fixed before the command can succeed/be retried. For example, attempting to write a file when out of memory, attempting to arm when sensors are not calibrated, etc. 
 <a id='MAV_RESULT_IN_PROGRESS'></a>5 | [MAV_RESULT_IN_PROGRESS](#MAV_RESULT_IN_PROGRESS) | Command is valid and is being executed. This will be followed by further progress updates, i.e. the component may send further [COMMAND_ACK](#COMMAND_ACK) messages with result [MAV_RESULT_IN_PROGRESS](#MAV_RESULT_IN_PROGRESS) (at a rate decided by the implementation), and must terminate by sending a [COMMAND_ACK](#COMMAND_ACK) message with final result of the operation. The [COMMAND_ACK](#COMMAND_ACK).progress field can be used to indicate the progress of the operation.