-
Notifications
You must be signed in to change notification settings - Fork 13.5k
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
Pr crazyflie optflow fix #9514
Pr crazyflie optflow fix #9514
Conversation
param set MPC_Z_P 1.5 | ||
param set MPC_Z_VEL_I 0.3 | ||
param set MPC_Z_VEL_P 0.4 | ||
param set MPC_HOLD_MAX_XY 0.1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor suggestion, sorting these alphabetically and splitting roughly by group makes this a bit easier to read or change.
Does the EKF handle NANs correctly already and use the onboard gyro? |
@DanielePettenuzzo Please follow up with a 2nd PR up sorting the params. Thanks! |
This would break the EKF if you tried to use it, I think. https://github.com/PX4/Firmware/blob/master/src/modules/ekf2/ekf2_main.cpp#L895-L897 |
@mhkabir I'm currently cleaning up my pr for the ecl.. will open it tomorrow. I basically take the imu gyro data in the estimator interface when NAN is published. |
Sounds good! Also you should note that it should use the delayed IMU data from the delayed time horizon the EKF is fusing the flow data at. Not the latest one pushed in the estimator interface. |
The crazyflie optical flow deck doesn't have a gyro therefore we need to use the gyro from the crazyflie's imu. This PR sets the gyro fields in the optical_flow message equal to NAN in order to understand if there is a gyro or not (to distinguish from px4flow).
Also updated crazyflie default params after several test flights.