Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correct MAVLINK_MSG_ID_SET_ATTITUDE_TARGET anglular rate input frame #24568

Merged
merged 2 commits into from
Jun 26, 2024

Conversation

lthall
Copy link
Contributor

@lthall lthall commented Aug 10, 2023

This PR fixes a problem where the angular rate inputs to MAVLINK_MSG_ID_SET_ATTITUDE_TARGET were not in the body frame if both attitude and rate are specified. It also checks to make sure each of the three rotation rate axis are specified.

This fixes the bug where when only rates are specified they are in body frame but when using quaternion attitude and rates the rates were in earth frame.

The message clearly specifies the rates are in body frame.

@lthall lthall force-pushed the 20230630_PR_GuidedAngleFrameFix branch from 76de937 to 752ee4e Compare August 21, 2023 23:38
@lthall lthall force-pushed the 20230630_PR_GuidedAngleFrameFix branch from 752ee4e to 37e50c3 Compare August 28, 2023 15:14
@lthall lthall force-pushed the 20230630_PR_GuidedAngleFrameFix branch from a99a2c9 to c908522 Compare June 20, 2024 23:21
@lthall
Copy link
Contributor Author

lthall commented Jun 20, 2024

I would love to get a quick explanation of the change to const Vector3f &ang_vel_body

@lthall lthall force-pushed the 20230630_PR_GuidedAngleFrameFix branch 2 times, most recently from 507af93 to e7485a2 Compare June 21, 2024 00:29
@lthall lthall force-pushed the 20230630_PR_GuidedAngleFrameFix branch from e7485a2 to c527131 Compare June 24, 2024 23:25
@peterbarker peterbarker merged commit b45b07d into ArduPilot:master Jun 26, 2024
92 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants