-
Notifications
You must be signed in to change notification settings - Fork 2
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
OAK-D-LR imuExtrinsics not merged #86
Comments
@dylan-gonzalez its WIP, we are working on adding the spec extrinsics directly to FW, with this branch supplementing it from "at calibration time".
These two IMUs differ only in FW version. BNO086 should be same as BNO085 with updated FW. We update the FW, so should be treated as BNO086 |
Do you have covariance values for the BNO086? When I run the |
@Serafadam do we have those available? |
Hi, unfortunately currently those values are not provided in the datasheets and firmware, though they should be added after the IMU calibration process updates. |
When will that be? |
So is it safe to use these extrinsics (which are for the BNO084) for the BNO086 in the OAK-D-LR? |
@Serafadam do you mind verifying? Also is OAK-D-LR now also included? |
How come the
adding_IMU_tmp
branch hasn't been merged? It has the commit that adds the imuExtrinsics, which I need to use to define the tf camera_link -> imu_link for the oak-d-lr here. Just curious as to why it hasn't been merged.Also, how do I know what IMU my OAK-D-LR has? In the depthai hardware docs, it says that it has a BNO085, but on the shop page it says it has a BNO086.
The text was updated successfully, but these errors were encountered: