Open knmcguire opened 1 year ago
Also related a bit to this bigger picture conversation of the crazyflie-firmware: https://github.com/bitcraze/crazyflie-firmware/issues/396
this needs to be investigated as it is being negated in multiple places, and eventually again in the firmware...
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: https://github.com/bitcraze/crazyflie-firmware/pull/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...