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

Use xacro file to plumb namespace into gz topics #10

Merged
merged 2 commits into from
Jun 19, 2024

Conversation

azeey
Copy link
Contributor

@azeey azeey commented Jun 19, 2024

It's not currently possible to set the namespace of gz-transport topics when a model is spawned. So the best option I could think of is to turn gz_waffle.sdf into a xacro file and pass in the namespace argument.

This also updates the max_step_size to 3ms to improve performance.

cc @SteveMacenski

Signed-off-by: Addisu Z. Taddese <[email protected]>
@SteveMacenski
Copy link
Member

Ah... that is not an expected result, thanks! So it looks like I figured out the bridge part, but didn't get the model part. I thought that there was a way to apply the node that spawned it namespace (or a launch flag) that would throw all the topics if not prepended with / into a namespace in GZ - since that would be really helpful and a common need I would imagine :-)

But this works just as well, if only slightly more manual.

@SteveMacenski SteveMacenski merged commit 9320bce into ros-navigation:multirobot Jun 19, 2024
7 checks passed
SteveMacenski added a commit that referenced this pull request Jun 21, 2024
* Attempts for multirobot namespacing in GZ

* expanding gazebo names

* Use xacro file to plumb namespace into gz topics (#10)

* Use xacro file to plumb namespace into gz topics

Signed-off-by: Addisu Z. Taddese <[email protected]>

* Fix linter

Signed-off-by: Addisu Z. Taddese <[email protected]>

---------

Signed-off-by: Addisu Z. Taddese <[email protected]>

---------

Signed-off-by: Addisu Z. Taddese <[email protected]>
Co-authored-by: Addisu Z. Taddese <[email protected]>
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

Successfully merging this pull request may close these issues.

2 participants