-
Notifications
You must be signed in to change notification settings - Fork 239
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
angular velocity on /imu topic broken #83
Comments
You are right. Gyro is configured as +/-2000dps and Accel is configured as +/-2g |
@OpusK, Does this software update include a workaround for this issue? |
I have just updated to 1.1.13 and it looks like the gyroscope is still reporting incorrect reading. Looking at the source code, a comment has been added next to GYRO_FACTOR definition (and the math in the comment is correct), but the value has not been changed (it's still the old 0.000133)
|
This issue has not been resolved in the 1.1.13 release. |
Hi :) @ihadzic You can watch the code is replaced. It will be updated soon. Thanks |
Hi again @ihadzic We update new firmware (version 1.2.0) :) Thank you to your contribution! |
I have recently upgraded the OpenCR firmware on my TB (I am now in the 1.1.2, before I was in 1.0.7). It looks like the units on /imu topic have been switched to radians (from raw ADC readings), but the numbers appear broken. I make the robot spin by exactly 1rad/s (verified correct by external means) and the imu/ topic reports 0.12 on z-axis angular velocity.
I believe the problem is that the calculations assume that the gyroscope range is +/-250 degrees (cf. the value of GYRO_FACTOR constant in turtlebot3_sensor.h), but the FS_SEL bits are still set to +/- 2000 range (see the register write to GYRO_CONFIG register in MPU9250.cpp)
The text was updated successfully, but these errors were encountered: