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

Namespace Argument in ROS2 + Ignition #6

Open
D-1shu opened this issue Jul 12, 2023 · 0 comments
Open

Namespace Argument in ROS2 + Ignition #6

D-1shu opened this issue Jul 12, 2023 · 0 comments

Comments

@D-1shu
Copy link
Contributor

D-1shu commented Jul 12, 2023

Issue with Namespace Argument in ROS2 + Ignition

Description

Currently, the launch file in gz.launch.py does not include a namespace argument. Additionally, in the model spawn, the namespace is not utilized as part of the naming convention for the spawned robot, unlike the ros2 classic and ros1 . Furthermore, the joint states and other topics are hardcoded to "bcr_bot,"

Steps to Reproduce

  1. Execute the current version of gz.launch.py without the namespace argument.
  2. Observe the robot spawn behavior and the naming convention used.
  3. Monitor the topics and verify that they are hardcoded to "bcr_bot".

Expected Behavior

After implementing the proposed changes:

  1. The gz.launch.py launch file should include a namespace argument.
  2. The robot spawned using the model spawn should incorporate the namespace argument in its name.
  3. Joint states and other topics should be properly mapped to the provided namespace.
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