Open rajrajsahil opened 5 years ago
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 build it and run the node with
<param name="publish_filtered_imu" value="true" type="bool" />
Then when you run the node, run a rosservice call /gx5/gyro_bias_capture
while the IMU is stationary. After this visualize orientation in Rviz using /gx5/filtered/imu/data
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.
Any new updates on this thread?
@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.