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

Clarification for the ENU frame #82

Open
ghost opened this issue Jul 26, 2018 · 5 comments
Open

Clarification for the ENU frame #82

ghost opened this issue Jul 26, 2018 · 5 comments
Labels

Comments

@ghost
Copy link

ghost commented Jul 26, 2018

Hi, I understand that this driver uses the East-North-Up definition as per REP-103. I wanted to be sure I understand what this means. See below for a simple URDF I had created which shows the imu_base_link in the standard forward-left-up frame & the imu link which is in the East-North-Up frame.
Am I interpreting this correctly?

xsens_mti_enu_frame_labels

Thanks in advance.

@fcolas fcolas added the question label Aug 1, 2018
@fcolas
Copy link
Contributor

fcolas commented Aug 1, 2018

You might want to check again section 5.2 of the user manual (MT0605P).
ENU is used in the local earth-fixed reference frame typically for the orientation and velocity messages.

@ghost
Copy link
Author

ghost commented Aug 1, 2018

Would you be interested in a simple URDF to include with the driver? I have created one for the MTi which could be modified for other models.

@fcolas
Copy link
Contributor

fcolas commented Aug 2, 2018

Why not, as in #50 I'd be happy to accept a pull request.
However, please make sure that the dimensions and the IMU origin are as accurate as possible. And the same if you include (which is a good idea) the cable sockets.
Thanks.

@fcolas
Copy link
Contributor

fcolas commented Aug 2, 2018

Actually, thanks to your question, I realized that I was doing too many frame changes. I fixed that in the code.

@ghost ghost mentioned this issue Aug 3, 2018
@ghost
Copy link
Author

ghost commented Aug 3, 2018

@fcolas check out the request. see if this is the way you want to handle this.

Cheers,
Vik

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

No branches or pull requests

1 participant