common: remove wip tag from MAV_CMD_DO_ORBIT and ORBIT_EXECUTION_STATUS (#2316)

These are in production use for 7 years now.
This commit is contained in:
Matthias Grob
2025-07-30 10:15:59 +02:00
committed by GitHub
parent e9d76096eb
commit f459afd493
-4
View File
@@ -1219,8 +1219,6 @@
<param index="7" label="Y Offset" units="m">Y offset from target</param>
</entry>
<entry value="34" name="MAV_CMD_DO_ORBIT" hasLocation="true" isDestination="true">
<wip/>
<!-- This message is work-in-progress and it can therefore change. It should NOT be used in stable production environments. -->
<description>Start orbiting on the circumference of a circle defined by the parameters. Setting values to NaN/INT32_MAX (as appropriate) results in using defaults.</description>
<param index="1" label="Radius" units="m">Radius of the circle. Positive: orbit clockwise. Negative: orbit counter-clockwise. NaN: Use vehicle default radius, or current radius if already orbiting.</param>
<param index="2" label="Velocity" units="m/s">Tangential Velocity. NaN: Use vehicle default velocity, or current velocity if already orbiting.</param>
@@ -7672,8 +7670,6 @@
<field type="float[58]" name="data">data</field>
</message>
<message id="360" name="ORBIT_EXECUTION_STATUS">
<wip/>
<!-- This message is work-in-progress it can therefore change, and should NOT be used in stable production environments -->
<description>Vehicle status report that is sent out while orbit execution is in progress (see MAV_CMD_DO_ORBIT).</description>
<field type="uint64_t" name="time_usec" units="us">Timestamp (UNIX Epoch time or time since system boot). The receiving end can infer timestamp format (since 1.1.1970 or since system boot) by checking for the magnitude of the number.</field>
<field type="float" name="radius" units="m">Radius of the orbit circle. Positive values orbit clockwise, negative values orbit counter-clockwise.</field>