-
Notifications
You must be signed in to change notification settings - Fork 63
float accuracy values for other quantities than quaternions #66
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
Comments
Hi JR, |
I agree with you, I cannot find much. I wonder if it is possible that the datasheet is not very complete.
The thing that makes me think such data may be available is that:
No idea if / how this could be accessed though, but probably the manufacturer of the firmware could say something more (?). I just got good hopes due to the Quaternion uncertainty data being available. |
Hi JR,
and we do already extract The "accuracy" or "status" byte for the accel, gyro and mag is: There does not appear to be an equivalent 16-bit value for those. Sorry - that's the best we can do! |
Ok, thanks :) . Maybe I could take contact with Hillcrest Labs directly and ask them if there is more than what is in the datasheet. Do you have a contact address that you would recommend that I use? I could put you in copy if you want :) . |
I like very much that the quaternion data can produce a detailed accuracy value in addition to the quality flag:
byte quat_accuracy = bno080_imu.getQuatAccuracy(); float quat_radian_accuracry = bno080_imu.getQuatRadianAccuracy();
I only find documented the quality flag, not detailed float value, for the other components (acceleration, gyro, magnetometer). Any way to access detailed float value uncertainties on these too / if not, is this something that can be added, or is it just not produced by the IMU?
The text was updated successfully, but these errors were encountered: