Skip to content
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

Why the translation results of y and z axis between IMU and camera are reverse with RealSenseD435i? #7865

Closed
opendvd opened this issue Nov 27, 2020 · 10 comments

Comments

@opendvd
Copy link

opendvd commented Nov 27, 2020

I use Kailbr to calibrate the RealSenseD435i, especially the external parameters between IMU and camera. But the external parameters of translation between IMU and camera confused me. The Kalibr's results are different with ideal value.
The ideal value is:
t_IC0 = [-0.006 0.005 0.012]T;
t_IC1 = [0.044 0.005 0.012]T;
But kalibr result is:
t_IC0 = [-0.00510796 0.01859231 0.00576145]T;
t_IC1 = [0.04383316 0.01886102 0.00574488]T;
So why the results of y and z axis are reverse?
Kalibr's result is here: results-imucam-imu_cameras_calibration.txt

@MartyG-RealSense
Copy link
Collaborator

Hi @opendvd If you are seeking to understand the transformation matrices between the IMU and the D435i's other camera sensors then the information in the link below may be helpful to you.

IntelRealSense/realsense-ros#1449

@opendvd
Copy link
Author

opendvd commented Nov 29, 2020

Hi @opendvd If you are seeking to understand the transformation matrices between the IMU and the D435i's other camera sensors then the information in the link below may be helpful to you.

IntelRealSense/realsense-ros#1449

Thank you. I checked this hyperlink that you provided, but did not find the answer I wanted. I want to know what caused the result of translation to be reverse?
I disassembled the realsenseD435i and used a ruler to measure, the result is very close to the ideal value:
t_IC0 = [-0.006 0.005 0.012]T;
t_IC1 = [0.044 0.005 0.012]T;
(The ideal value is got by realsense2_description ROS wrapper. I run the launch file: view_d435i_model.launch in ROS. )
But when I use kalibr to get the calibration results, the results is reverse. I also use kalibr to calibration the MYNTEYE camera, its calibration is right, so I think Kalibr is correct. The problem is in realsense.

@opendvd
Copy link
Author

opendvd commented Nov 29, 2020

The transformation about the RealsenseD435i is show in rviz.
图片

@MartyG-RealSense
Copy link
Collaborator

MartyG-RealSense commented Nov 29, 2020

Is Kalibr taking account of how the left infrared imager is on the right side of the camera when viewed from a front-on perspective?

#3662

@opendvd
Copy link
Author

opendvd commented Nov 30, 2020

Is Kalibr taking account of how the left infrared imager is on the right side of the camera when viewed from a front-on perspective?

#3662

  1. Thank you for your reply. The Kalibr only focus on camera's ros topic: /camera/infra1/image_rect_raw&/camera/infra2/image_rect_raw.
  2. I think it has nothing to do with Kalibr, because I use Kalibr to calibrate my MYNTEYE camera is normal.
  3. Could you please calibrate D435i with Kalibr? (The transformation between IMU and two camera) You will understand my problem.

@MartyG-RealSense
Copy link
Collaborator

MartyG-RealSense commented Nov 30, 2020

I am not able to make use of Kalibr.

It has already been established in another case that there can be large differences in Kalibr's calibration results with RealSense and with Mynteye.

#7103

Bearing that in mind, I do not think that there is anything else that I can add that will be helpful, unfortunately. I would always recommend using RealSense's own IMU calibration tool.

https://github.com/IntelRealSense/librealsense/tree/master/tools/rs-imu-calibration

@opendvd
Copy link
Author

opendvd commented Dec 1, 2020

I am not able to make use of Kalibr.

It has already been established in another case that there can be large differences in Kalibr's calibration results with RealSense and with Mynteye.

#7103

Bearing that in mind, I do not think that there is anything else that I can add that will be helpful, unfortunately. I would always recommend using RealSense's own IMU calibration tool.

https://github.com/IntelRealSense/librealsense/tree/master/tools/rs-imu-calibration

Thanks for your reply. I will continue to explore the cause of this problem.

@MartyG-RealSense
Copy link
Collaborator

Hi @opendvd Do you have an update that you can provide, please? Thanks!

@MartyG-RealSense
Copy link
Collaborator

Hi @opendvd Do you require further assistance with this case, please? Thanks!

@MartyG-RealSense
Copy link
Collaborator

Case closed due to no further comments received.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants