-
Notifications
You must be signed in to change notification settings - Fork 250
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
Slowly getting to the correct orientation #43
Comments
You have shown that the 3D model initially only rotates half the expected angle. This will be due to an incorrect gyroscope sensitivity or I suggest that you start with a simple implementation and gradually increase complexity. I suggest that you implement each of the following systems and only progress to the next once the current system is working without issue.
|
@xioTechnologies Thanks again. I will close the issue. |
Dear xioTechnologies,
Thanks to the X-IMU3 GUI, I was able to visualize the orientation of my 9DOF IMU (Acclerometer, magnetometer and gyro).
I am using the default parameters for the algorithm's initialization:
However, as I rotated the IMU, the measured orientation slowly approached the correct orientation but not exactly right. Usually the measured orientation became correct after a reinitialization triggered by the timeout.
I also tried disabling the magnetic rejection but had similar observations. I demonstrated this issue in a short video.
https://youtu.be/yuEquhkZYPk
My guess is that the rejection parameters need to be tuned, or maybe disabled? The application I'm working on involves constant rotation of the imu, not much accleration though. I wonder what I should do to obtain accurate orientation measurements, for example like in the video https://youtu.be/BXsGWoOMtmU
Many thanks for your insight.
Finally my hardware info, thought I don't think it matters:
Microcontroller used: SONY SPRESENSE. It has 6 ARM® Cortex®-M4F cores running at 156 MHz
IDE: Arduino
Gyroscope : FXAS21002C
Accelerometer and Magnetometer : FXOS8700
The text was updated successfully, but these errors were encountered: