Fix launch file to avoid launching packages for real robots during simulation #51
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed change(s)
Update
hardware_connected
tojoint_hardware_connected
to avoid launching packages for real robots during simulationUseful links (GitHub issues, forum threads, etc.)
Types of change(s)
Testing and Verification
Please describe the tests that you ran to verify your changes. Please also provide instructions and ROS packages as appropriate so we can reproduce the test environment.
colcon build --symlink-install
ros2 launch mini_pupper_gazebo gazebo.launch.py
ros2 node list
and see no lidar or servo specific nodes are launchedTest Configuration
Mini Pupper Version
Simulator
PC OS + ROS version
Ubuntu 22.04, ROS 2 Humble
Checklist
Other comments