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

Revert " #338: Fix yawrate sign in commander_generic packets" #1456

Merged
merged 2 commits into from
Feb 19, 2025

Conversation

gemenerik
Copy link
Member

@gemenerik gemenerik commented Feb 11, 2025

This reverts commit f6c0e73.

Requires using correct yaw convention in cflib: bitcraze/crazyflie-lib-python#516

…ition

The Crazyflie now correctly handles both legacy and updated commander setpoints. It continues flipping the negated yaw for legacy packets to prevent unexpected behavior when updating only one side. Updated packets use the correct yaw sign and are taken as-is. This maintains compatibility while allowing for a phased transition. The legacy type will be deprecated in a future update.
@gemenerik
Copy link
Member Author

Latest commits to this and bitcraze/crazyflie-lib-python#516 ensure compatibility when updating either the Crazyflie or lib independently. The lib now checks the Crazyflie's CRTP version and sends either the legacy packet (with the original negated yaw) or the new packet type (with the corrected yaw sign). This allows for a smooth transition without breaking existing functionality. The legacy types will be deprecated in the future.

Copy link
Contributor

@ToveRumar ToveRumar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me.

Tested it with and without cflib change. Tested by checking the yaw in cfclient.

@ToveRumar ToveRumar merged commit 16c5630 into master Feb 19, 2025
25 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.

2 participants