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

motion commander, start_linear_motion reverse yaw #389

Open
knmcguire opened this issue Mar 28, 2023 · 2 comments · May be fixed by #516
Open

motion commander, start_linear_motion reverse yaw #389

knmcguire opened this issue Mar 28, 2023 · 2 comments · May be fixed by #516
Assignees

Comments

@knmcguire
Copy link
Contributor

If somebody uses the start_linear_motion function from the motioncommander, and add a yaw_rate, you'll see that the resulting yaw rate on the crazyflie itself is reversed, compared to the coordinate system that we have given in our documentation: https://www.bitcraze.io/documentation/system/platform/cf2-coordinate-system/

This was originally introduced with this PR: bitcraze/crazyflie-firmware#338 and implemented in all packets there forth. The problem is that the coordinate system is consistent with the state estimate but not consistent with the control input...

@knmcguire
Copy link
Contributor Author

Also related a bit to this bigger picture conversation of the crazyflie-firmware: bitcraze/crazyflie-firmware#396

@knmcguire
Copy link
Contributor Author

this needs to be investigated as it is being negated in multiple places, and eventually again in the firmware...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants