-
Notifications
You must be signed in to change notification settings - Fork 73
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
Livox LiDAR support #17
Comments
Unfortunately, the current version code does not support Livox. |
Can you write in more detail? Are there any hardware limitations for example livox mid 360 lidar for use with LIW-OAM without ROS (directly using with SDK\driver livox)? |
@ZikangYuan Are the following changes enough to use Livox AVIA for liw_oam?
We can execute liw_oam with Livox AVIA by converting the livox custom message (livox_ros_driver::CustomMsg) into sensor_msgs::PointCloud2 message, and the estimation result is good even in an environment where point clouds degenerate. |
@TakuOkawara Did you manage to launch LIW-OAM with the Livox AVIA lidar? |
Yes, we were able to launch LIW-OAM with the Livox AVIA lidar and wheel odometry. |
Thank you for sharing your great project with us.
We were able to run this package with the bag file obtained from your Google Drive.
We ask you whether this package supports for Livox LiDARs because we plan to cite your paper.
As seen in some codes such as kaist.yaml and lioOptimization.cpp, this package seems to support Livox LiDARs.
kaist.yaml
lioOptimization.cpp
However, cloudProcessing.cpp shows that other than Velodyne LiDARs cannot be used currently such as the following image.
cloudProcessing.cpp
Therefore, we are confused about whether we can use Livox LiDAR for this package.
If this package does not support Livox LiDAR (especially, Livox AVIA), can we use this package by Livox AVIA with some adjustments to the settings made for Velodyne?
The text was updated successfully, but these errors were encountered: