velodyne icon indicating copy to clipboard operation
velodyne copied to clipboard

ROS support for Velodyne 3D LIDARs

Results 112 velodyne issues
Sort by recently updated
recently updated
newest added

Right now on the dashing-devel branch, you can set different parameters during startup. Changing them after startup (via `ros2 param set`, for instance) appears to work, but doesn't actually change...

enhancement

Currently the integration tests across all packages are disabled in the ROS 2 port, but it would be great to re-enable them and make sure they pass.

enhancement

The current ROS 2 Dashing code disables some of the logging because it wasn't clear the best way to pass the necessary logging pointer to where it is needed. https://github.com/ros-drivers/velodyne/blob/dashing-devel/velodyne_pointcloud/src/lib/rawdata.cc#L101...

enhancement

Dear: when I use the launch file in velodyne_pointcloud to read pcap files, I can not read a complete revolution. The results in rviz is shown as following: ![2019-06-05 16-39-49屏幕截图](https://user-images.githubusercontent.com/36224780/58942609-a85a6100-87b0-11e9-809c-cd87d774ae07.png)...

question

**Is your feature request related to a problem? Please describe.** Within the driver the packet message is published using the timestamp of the last packet. This means that the published...

enhancement
help wanted

http://wiki.ros.org/velodyne is somewhat dated and needs to include additional data about new sensors and this driver's support of them. The README is also very sparse. It should include, at the...

enhancement

I tried converting some existing code I had to use the `velodyne_pointcloud::PointXYZIR` type provided in this repository, but it wouldn't build due to uses of `pcl::KdTreeFLANN`, `pcl::PCLBase` and `pcl::Passthrough`. From...

Hey, I was wondering why no one ever added in the GPS and IMU data. I am going to be working on this, and might ask for a merger later.

enhancement

For the case where first non zero minIntensity_ value appears in the middle of the list, it will be errornously placed as the minIntensity of the first laser in the...

bug

if I use a db.XML which defines No.0 and No.3 laser's minIntensity are '1' instead of '0'. I got an incorrect yaml file: lasers: - {dist_correction: 0.0, dist_correction_x: 0.0, dist_correction_y:...

bug
duplicate