Fix: Allow node renaming in ROS2 to avoid duplicate nodes (#22) #23
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.
Fix: Allow node renaming in ROS2
This PR addresses the issue where launching multiple Hesai LiDAR sensors results in multiple nodes with the same name.
Referring to the issue https://github.com/HesaiTechnology/HesaiLidar_ROS_2.0/issues/22
🔹 Changes:
ros_node_name
in the config file to allow setting custom node names.source_drive_common.hpp
andsource_driver_ros2.hpp
driver_param.h
in the submoduledriver
to include:This is my first PR involving submodules, and I may have missed something. I apologize for any mistakes made during the process.
Please refer to the pull request for the HesaiLidarSDK: https://github.com/HesaiTechnology/HesaiLidar_SDK_2.0/pull/20