Closed villanuevab closed 6 years ago
The lidar driver I have does not publish ring information. I think this is the issue.
hi, i have the same issue with you , i comment some code . and the package can work , but in cloud window , it is wrong . it seems like the package didn't detect the edge in cloudpoints
I use the lidar of robosense. Only neet to modify some codes.
Hi everyone! did you manage to use other LiDARS like robosense with this package? @oaix could you please how did you manage to use robosense LiDAR? I am getting an error saying
Failed to find match for field 'ring'. terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc
and after that the process dies and generates this output:
[find_transform-2] process has died [pid 31697, exit code -6, cmd /home/pedram/catkin-ws/devel/lib/lidar_camera_calibration/find_transform __name:=find_transform > __log:=/home/pedram/.ros/log/75cc0b6e-2d4a-11e9-8464-90b11c970001/find_transform-2.log]. log file: /home/pedram/.ros/log/75cc0b6e-2d4a-11e9-8464-90b11c970001/find_transform-2*.log
Can anyone help?
I write a ros package to convert robosense point cloud into velodyne_cloud.See here
Hi, do you have any idea about how to use this calibration tool with Ouster LiDAR 128line?
Do you have any idea about how can I modify the code in the calibration tool to adapt to my Ouster LiDAR? Thx
I use the lidar of robosense. Only neet to modify some codes.
Hi, I used the Ouster LiDAR with 64 channels. How can I manage to change the code to make this calibration tool to work with my LiDAR, thx!
Hi, I have the same question. Have you had a solution now?
Is there a common used calibration tool to calibrate Ouster Lidar?
I tried using another lidar device and updated the velodyne topic in
lidar_camera_calibration
https://github.com/ankitdhall/lidar_camera_calibration/blob/master/conf/lidar_camera_calibration.yaml#L4 . I am getting the following error:I am able to calibrate when using a Velodyne lidar. The only difference that I made to cause this error is use a different lidar and different topic name. Both use PointCloud2.msg.