Skip to content

Commit 7c1b058

Browse files
Davidsastresashamishwilleejulianoes
authored
gimbal_v2.md: Add clarification about gimbal yaw frame (#531)
* gimbal_v2.md: Add clarification about gimbal yaw frame * Subedit * Update en/services/gimbal_v2.md Co-authored-by: Julian Oes <julian@oes.ch> --------- Co-authored-by: Hamish Willee <hamishwillee@gmail.com> Co-authored-by: Julian Oes <julian@oes.ch>
1 parent b40e3a5 commit 7c1b058

File tree

1 file changed

+13
-0
lines changed

1 file changed

+13
-0
lines changed

en/services/gimbal_v2.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -255,6 +255,19 @@ This signals that the gimbal manager also is also acting as the gimbal device.
255255

256256
Also see [how to address non-MAVLink gimbal devices](#non_mavlink_gimbal_device_addressing).
257257

258+
#### How to interpret `GIMBAL_DEVICE_ATTITUDE_STATUS` yaw gimbal angle
259+
260+
The [GIMBAL_DEVICE_ATTITUDE_STATUS.flags](#GIMBAL_DEVICE_ATTITUDE_STATUS) field must report the frame used for reported yaw values as **either**:
261+
262+
- `GIMBAL_DEVICE_FLAGS_YAW_IN_VEHICLE_FRAME`: Yaw is relative to vehicle.
263+
- `GIMBAL_DEVICE_FLAGS_YAW_IN_EARTH_FRAME`: Yaw is relative to north.
264+
265+
For older devices, if neither of the flags above are set, the yaw frame must be inferred from the `GIMBAL_DEVICE_FLAGS_YAW_LOCK`.
266+
If it is set, the yaw is relative to North, otherwise to the front of the vehicle.
267+
268+
> **Note** Manufacturers working on new gimbal devices should set either `GIMBAL_DEVICE_FLAGS_YAW_IN_VEHICLE_FRAME` or `GIMBAL_DEVICE_FLAGS_YAW_IN_EARTH_FRAME`.
269+
> Components recieving the message should also handle `GIMBAL_DEVICE_FLAGS_YAW_LOCK` for backwards compatibility with older devices.
270+
258271
## Message/Command/Enum Summary
259272

260273
### Gimbal Manager Messages

0 commit comments

Comments
 (0)