-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Resetting Kalman filter with invalid quaternion results in crash #453
Comments
Hi! Interesting that this happens. Could you tell a bit more how you set this? Through the parameters or hard coded in the firmware? |
Through the parameters. Initially I thought it has something to do with the convergence of the filter (see #402), but then I noticed I am actually setting a malformed quaternion (all terms set to 0). Everything is fine when the quaternion is set to [0, 0, 0, 1]. |
Hmm okay. Did you make your own parameters for the initial quaternions? It doesn't exist in the current master, and it is set starting from this line:
Just making sure what is changed in your version before we try to recreate your problem. |
Seems like we are on a pretty old version indeed. Sorry for this. We will try to merge from the upstream and see if we have any related issues. Thanks |
This is fixing the client in python 3.9. When vispy releases its next version, the special handling for python 3.9 can be removed.
Fixes running client on Python 3.9
Setting initial quaternion (
kalman/initialQ[x,y,z,w]
) to zero and resetting the filter (kalman/resetEstimation = 1
), results in immediate firmware crash. CF spits out a part of the regular boot log, but then freezes and does not respond to commands anymore.The text was updated successfully, but these errors were encountered: