-
Notifications
You must be signed in to change notification settings - Fork 525
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
Map overlapping problem #681
Comments
Could be some issue with your tf. Triple check the laser to base link tf in your urdf. |
I am not using a URDF, only tf from the drivers' packages. I checked running: |
Nah I mean the tf needs to be correct. An incorrect TF can cause this as far as I know since I had a very similar issue. An Incorrect tf would also look completely normal on the tree. |
Okay, thank you. How do I know if my tf is correct then ? |
Hello !
-> My setup:
-> The problem:
I can successfully generate a map, but when I move the robot or when odometry data changes, I get a new scan of the map but overlapping the previous one ! (Fixed Frame is set to "map" and sometimes to "base_footprint" but still got the same behavior)
I want the map to stay put in place (static, not moving with the robot) while the robot is moving to scan the reaminning blank spaces.
I have also tried this with gmapping and got the same problem. Is there a parameter to change in order to fix that ?
Thanks in advance!
The text was updated successfully, but these errors were encountered: