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

About Livox lidar instead of velodyne #19

Open
MA-xiaowen opened this issue Mar 19, 2024 · 1 comment
Open

About Livox lidar instead of velodyne #19

MA-xiaowen opened this issue Mar 19, 2024 · 1 comment

Comments

@MA-xiaowen
Copy link

First of all, thank you very much for your outstanding contribution, which brought me into contact with this excellent project fusion lidar and cameras. About the lidar we use, it is a solid-state lidar rather than a mechanical lidar like velodyne. So I would like to ask, is there anything that needs to be paid attention to when replacing velodyne with solid-state lidar? By changing the lidar topic and image topic, I can currently display the original image and point cloud, but cannot display the fused image and point cloud, I hope you can give me your comments on this part. Thank you so much.

@EPVelasco
Copy link
Owner

Hi. You should take into account the type of message in the point cloud. The current project works with topics with PontiCloud2 message type. I think Livox has its own message type (see livox_ros_driver).
Make sure to convert the livox message to PointCloud2.
You can see the official livox mapping repository. There is a node there that converts the message type to PointCloud2.

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

2 participants