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

Imu Message #14

Open
Morgantiz opened this issue Feb 15, 2023 · 0 comments
Open

Imu Message #14

Morgantiz opened this issue Feb 15, 2023 · 0 comments

Comments

@Morgantiz
Copy link

Morgantiz commented Feb 15, 2023

I'm using the Concert platform odometry, on topic "/concert_odometry/base_link/odom", to localize the robot with respect to its starting position. The x and y coordinates seem to work quite well, but the orientation angle on the navigation plane does not seem to be accurate in the same way.
Unfortunately, small errors on the orientation angle create more visible problems in localization that can only be compensated for through the use of sensors (checking the differences between the environment with the given map).
I have noticed that a common solution is to use the orientation component of an Imu, which is already on the Concert platform (e.g. Neobotix settings here, or even the turtlebot3, from what i have seen here). The meaning of the robot_localization node settings used by Neobotix are explained here.
For these reasons It would also be useful to have an /imu topic with a standard Imu Message sensor_msgs/Imu, as defined here, so i can test whether this improves the localization performance of the navigation stack.
Thank you!

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

No branches or pull requests

1 participant