-
Notifications
You must be signed in to change notification settings - Fork 115
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
data is not steady when when imu is in rest position #24
Comments
Has anyone understood what is causing this? I am seeing a very similar problem. When using the MIPs software provided by Lord Sensing, the sensor is very responsive. When using this driver the orientation is not very responsive or it responds very delayed as above. If I rotate the sensor around 180* about Z and stop the orientation keeps moving. |
Try this, not sure if it will fix it but it seems to do something. @rajrajsahil I think it has to do with Gyro Bias I am pretty sure. It also appears that Gyro bias calculation only appears to affect the KF filtered data? Pull from my master branch at: https://github.com/samkys/microstrain_mips/commits/master
Then when you run the node, run a This worked for me as of now! |
@samkys Thanks for your detailed steps. Unluckily for me it didn't solve the problem. The Yaw drifts randomly in positive or negative directions while moving along a straight line. I repeated the same experiment with another manufacturer IMU and I did not observe this drift. In the attached snapshot red is ground truth and blue is IMU yaw based odometry. |
@samkys Update! Looks like your fix is working, please ignore my previous post. The IMU Yaw is much more stable now! Thanks for the help! |
Glad to hear! Good luck, and if anything changes let me know. |
Imu is on the robot. When the robot is rotating IMU(3DM-GX5-25) give value close to accurate but when we stop the robot for some time IMU output(yaw) keep increasing. I checked the output of the IMU with MIP Monitor as mention in the datasheet without using this package and it was working very good.
The text was updated successfully, but these errors were encountered: