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

Fixed transformation error for centered_laser_pose_ computation #88

Open
wants to merge 1 commit into
base: melodic-devel
Choose a base branch
from

Conversation

madMAx43v3r
Copy link

fixed transformation error for centered_laser_pose_ computation in case of laser mounted upside down

tf::createQuaternionFromRPY() takes fixed angles as input such that angle_center is not affected by the 180 deg roll

…se of laser mounted upside down

tf::createQuaternionFromRPY() takes fixed angles as input such that angle_center is not affected by the 180 deg roll
Copy link
Contributor

@k-okada k-okada left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, but not 100% sure if this does not break existing users, do you have any simulation environment that we can check this ?

@madMAx43v3r
Copy link
Author

This change only affects users where angle_center != 0 and the scanner is mounted upside down. I believe we are one of the first to encounter this case.

We tested this on one of our MP-400 at Neobotix which is fitted with a new scanner for testing purposes. This scanner doesn't follow the ROS convention and thus has a angle_center of over 100 deg. When we mounted the scanner normally we could build maps no problem, but when we mounted it upside down we got major issues trying to build a map, everything was rotated and it was a big mess. However in RVIZ it looked just fine in both cases (using odom as reference), so the problem had to be in gmapping.

With this fix we can build maps just fine even when the scanner is mounted upside down.

Hope that helps.

@madMAx43v3r
Copy link
Author

Sorry, I moved that other commit to another branch now.

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

Successfully merging this pull request may close these issues.

2 participants