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

Feature/robobus:Configure multiple lidar multiple frame_id in the configuration file,No need to install livox_SDK2 manually: #85

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

zymouse
Copy link

@zymouse zymouse commented Nov 6, 2023

settled

  • mid360*2 and had*1 multiple LIDAR test passes
  • livox_ros_driver2 Fork latest commit:852c1475b386f107298082d0a540e304f30c6d14

Functions realized

  • Configure multiple lidar multiple frame_id in the configuration file
    image

  • No need to install livox_SDK2 manually:Livox-SDK2 modified to ros2 functional package
    image

@zymouse zymouse changed the title Feature/robobus: Feature/robobus:Configure multiple lidar multiple frame_id in the configuration file,No need to install livox_SDK2 manually: Nov 6, 2023
@trishmapow
Copy link

Hi, are there any updates on whether this will be merged? It would be very useful to be able to differentiate multiple lidars.

Comment on lines +1 to +4
set(VERSION_ROS2 "ROS2" )
set(VERSION_HUMBLE "humble" )
set(ROS_EDITION ${VERSION_ROS2} )
set(HUMBLE_ROS ${ROS_HUMBLE} )

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This part probably wasn't meant to be hardcoded - but otherwise it all seems to work well.

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