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

Using official rslidar sdk to capture point cloud for LIO-SAM #134

Open
TZECHIN6 opened this issue Oct 5, 2023 · 4 comments
Open

Using official rslidar sdk to capture point cloud for LIO-SAM #134

TZECHIN6 opened this issue Oct 5, 2023 · 4 comments

Comments

@TZECHIN6
Copy link

TZECHIN6 commented Oct 5, 2023

As rslidar sdk now can publish XYZIRT pointcloud directly, has anyone tried to use it with LIO-SAM directly?

Do we still need to use rs_to_velodyne to post processing the pointcloud before inputting to LIO-SAM node?

Great thanks!

@pvela2017
Copy link

Hello,
I'm new in this field, is there a difference between [robosense XYZIRT] and [velodyne XYZIRT] information?

@TZECHIN6
Copy link
Author

TZECHIN6 commented Nov 7, 2023

I believe at least the naming of it is different, e.g. timestamp and ts. For the actual data representation, I am not so sure, thus I have asked this question in here.

@pvela2017
Copy link

I see, it happens I have a robosense lidar and velodyne lidar. I could test both but I need some guidance on what to look for

@pvela2017
Copy link

pvela2017 commented Nov 16, 2023

Hi,
I tried the optimized-sc-f-loam with the robosense lidar compiled using XYZIRT and got the following error:
[pcl::PCDWriter::writeBinary] Input point cloud has no data!
Then tried it with the rs_to_velodyne package and got the same error.

Now, Im testing the velodyne one.

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