-
Notifications
You must be signed in to change notification settings - Fork 16.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
Sudden height change in ALT HOLD - dangerous #1989
Comments
Hi Victor, I'm having a look at it. So you're using 3.3-dev, appears to be recent, but not the latest. I believe it's using the new IMU filtering scheme as you have INS_GYRO_FILTER and INS_ACCEL_FILTER parameters. But you also still have AHRS_EKF_USE which I think has been deprecated? BTW, this was not 1, so I believe you were using DCM rather than EKF. You should probably be using EKF. I do see a permanent, and remarkably consistent offset between the Baro height, and the inertial height estimate. It actually begins before the motors start. Normally this sort of problem is caused by vibrations, but that doesn't seem to be the case here. The vibration levels look good, and as I said, the divergence between INAV altitude and baro altitude begins before the motors even start. I do notice that your IMU is registering only 8 m/s/s acceleration downward while sitting still. The system basically thinks it is accelerating downward. This is probably the reason for the offset. I think something went wrong during your accelerometer calibration. |
@R-Lefebvre thanks a lot for taking a looking that up. Just saw what you mean. I'll leave a capture here in case someone experiences something similar. |
Some conclusions posted here. in a nutshell, it seems to us that these misbehaviors are due to a bad set of parameters (we are using these ones). For completion, falling back to DCM (forcing it in the code) fixes this sudden changes. |
@victor, |
those voices in my head... please make them stop! |
Thanks @rmackay9 for your answer. We also noticed that while armed, we can't change to GPS-enabled modes (e.g.: we can't change from |
@vmayoral, it's all guesswork without a log file. |
@rmackay9 rebased the code including latest commits from @priseborough and redid the tests. Looks much better. We can now change modes (we were previous getting We'll keep looking into it to make sure issues have been fixed. |
ok great. let's close this issue then and we can re-open if it reappears. |
@rmackay9 and @tridge,
We'd appreciate if you could take a look at this log.
@imuguruza and @ahcorde noticed today (it seems it happened several times) that when taking off in
ALT HOLD
the copter suddenly gets height really aggressively:Changing to STABILIZE allowed us to land the copter Has someone else experienced this?
The text was updated successfully, but these errors were encountered: