Skip to content

Commit 23ab73b

Browse files
committed
common.xml: remove stale reservation for MAV_CMD_PARAM_TRANSACTION
no longer in mavlink/mavlink/master
1 parent 89adb31 commit 23ab73b

1 file changed

Lines changed: 0 additions & 2 deletions

File tree

message_definitions/v1.0/common.xml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1709,7 +1709,6 @@
17091709
<param index="1" label="Tag" minValue="0" increment="1">Target tag to jump to.</param>
17101710
<param index="2" label="Repeat" minValue="0" increment="1">Repeat count.</param>
17111711
</entry>
1712-
<!-- entry value 900 reserved for MAV_CMD_PARAM_TRANSACTION (development.xml) -->
17131712
<entry value="1000" name="MAV_CMD_DO_GIMBAL_MANAGER_PITCHYAW" hasLocation="false" isDestination="false">
17141713
<description>Set gimbal manager pitch/yaw setpoints (low rate command). It is possible to set combinations of the values below. E.g. an angle as well as a desired angular rate can be used to get to this angle at a certain angular rate, or an angular rate only will result in continuous turning. NaN is to be used to signal unset. Note: only the gimbal manager will react to this command - it will be ignored by a gimbal device. Use GIMBAL_MANAGER_SET_PITCHYAW if you need to stream pitch/yaw setpoints at higher rate. </description>
17151714
<param index="1" label="Pitch angle" units="deg" minValue="-180" maxValue="180">Pitch angle (positive to pitch up, relative to vehicle for FOLLOW mode, relative to world horizon for LOCK mode).</param>
@@ -4380,7 +4379,6 @@
43804379
<field type="uint32_t" name="custom_mode">The new autopilot-specific mode. This field can be ignored by an autopilot.</field>
43814380
</message>
43824381
<!-- IDs 15-17 reserved for PARAM_VALUE_UNION and other param messages -->
4383-
<!-- IDs 19 reserved for PARAM_ACK_TRANSACTION (development.xml) -->
43844382
<message id="20" name="PARAM_REQUEST_READ">
43854383
<description>Request to read the onboard parameter with the param_id string id. Onboard parameters are stored as key[const char*] -&gt; value[float]. This allows to send a parameter to any other component (such as the GCS) without the need of previous knowledge of possible parameter names. Thus the same GCS can store different parameters for different autopilots. See also https://mavlink.io/en/services/parameter.html for a full documentation of QGroundControl and IMU code.</description>
43864384
<field type="uint8_t" name="target_system">System ID</field>

0 commit comments

Comments
 (0)