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

Correctly hande header.frame_id #45

Closed
rsiryani opened this issue Aug 20, 2021 · 1 comment
Closed

Correctly hande header.frame_id #45

rsiryani opened this issue Aug 20, 2021 · 1 comment
Assignees
Labels
Milestone

Comments

@rsiryani
Copy link
Contributor

The frame_id is used to define in 3D where a measurement is located.
It shouldn't be used to indicate time system.
Also the user should be able to configure the frame_id name as node parameter.

We consider here a simple case where all INS / IMU measurements should come from the same frame.
The user should make sure he has correctly setup his INS to output all measurements at the Bare IMU ref point.

@rsiryani rsiryani added this to the Rework Time milestone Aug 20, 2021
@rsiryani rsiryani added this to To do in Revamped ROS driver via automation Aug 20, 2021
@rsiryani rsiryani added the bug label Aug 20, 2021
@rsiryani
Copy link
Contributor Author

Please check https://www.ros.org/reps/rep-0145.html
The IMU frame_id should be imu_link or imu_link_ned or overiden by the user

mzembsbg added a commit that referenced this issue Aug 24, 2021
- Add a new parameter to allow user to specify driver.frameId parameter.
- Move parameter output.frequency to driver.frequency

According to REP 145, the default frame ID is "imu_link_ned".
@rsiryani rsiryani moved this from To do to In Progress in Revamped ROS driver Aug 25, 2021
@bsaussay bsaussay moved this from In Progress to Done in Revamped ROS driver Aug 27, 2021
@bsaussay bsaussay linked a pull request Aug 27, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

Successfully merging a pull request may close this issue.

2 participants