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

Timed out waiting for transform from tb3_2/base_footprint to map to become available before running costmap, tf error: Could not find a connection between 'map' and 'tb3_2/base_footprint' because they are not part of the same tree.Tf has two or more unconnected trees.. #7

Open
gege980823 opened this issue Oct 12, 2022 · 3 comments

Comments

@gege980823
Copy link

I ran into this problem when I was running multiple robots and I didn't know what to do about it. Is it useful to publish a tf static transform from odom to base_footprint? My tf tree is disconnected from odom to base_footprint.Meanwhile, there is no news on my scan topic.I just learned multi-robot slam, and there are many things I don't understand. I hope someone can give me some advice!

@sandilyasg
Copy link

@gege980823 were you able to solve it? Can you please post how you solved the issue? Thanks

@hikashi
Copy link
Owner

hikashi commented Jun 12, 2023

I believe it has something to do with the turtlebot environment setup you have and therefore this issue occurred.
Can you download the turtlebot3 library and retry again?

@Daviesss
Copy link

Daviesss commented Mar 1, 2024

I ran into this problem when I was running multiple robots and I didn't know what to do about it. Is it useful to publish a tf static transform from odom to base_footprint? My tf tree is disconnected from odom to base_footprint.Meanwhile, there is no news on my scan topic.I just learned multi-robot slam, and there are many things I don't understand. I hope someone can give me some advice!

This is as a result of tf tree not correct . There is no connected transform(tf) from map to tb_2/base_footprint , the tree has to be connected before the error is solved .

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

4 participants