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

Fast-LIO not working properly with MID360 LiDAR #11

Open
ylenianistico opened this issue Aug 23, 2024 · 2 comments
Open

Fast-LIO not working properly with MID360 LiDAR #11

ylenianistico opened this issue Aug 23, 2024 · 2 comments

Comments

@ylenianistico
Copy link

ylenianistico commented Aug 23, 2024

Hello! Thank you very much for this work. I am trying to run Fast-LIO with data recorded (ros2 bag) from a LiDAR MID360.

The rosbag contains the topics

/livox/imu
/livox/lidar

To launch FAST-LIO, I'm doing

ros2 launch fast_lio mapping_mid360.launch.py

and then I play the rosbag. But when it starts reading messages from the /livox/topics I get this error:

[fastlio_mapping-1] Failed to find match for field 'reflectivity'

I think this is because Fast-LIO is expecting a field named reflectivity, but my LiDAR point cloud doesn't include this field (it only has x, y, z, intensity, tag, line, and timestamp).

I tried to modify the code here slightly, but I didn't manage to make it work.

Have you ever faced this problem?

Thanks again

@Taeyoung96
Copy link
Owner

@ylenianistico
Thanks for testing our work!
Unfortunately, I haven't tested with MID360, but I have a few questions.

What config file and launch file did you use?
If you used mid360.yaml, could you change the preprocess to the following?

preprocess:
    lidar_type: 1                # 1 for Livox serials LiDAR, 2 for Velodyne LiDAR, 3 for ouster LiDAR, 
    scan_line: 4
    blind: 0.5
    # timestamp_unit: 3

@imdsafi09
Copy link

Hi, I tried to run it with ouster-128. The algorithm seems to work with the same output as above, but in my case, it's only "ring," as shown in the screenshot. I am using the Ouster-64 configuration as follows:
preprocess:
lidar_type: 3 # 1 for Livox serials LiDAR, 2 for Velodyne LiDAR, 3 for ouster LiDAR,
scan_line: 128
blind: 2.0
timestamp_unit: 3
scan_rate: 10

image

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

3 participants