The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
As you see, the velodyne_driver publishes /velodyne_packets, a device-dependent data stream that rviz does not understand.
As @dornhege said, you need to run one of the velodyne_pointcloud nodes or nodelets. They will convert the raw Velodyne packets into sensor_msgs/PointCloud2, which rviz can display. That wiki page gives some launch file examples you may find helpful.
| | 2 | give launch example |
As you see, the velodyne_driver publishes /velodyne_packets, a device-dependent data stream that rviz does not understand.
As @dornhege said, you need to run one of the velodyne_pointcloud nodes or nodelets. They will convert the raw Velodyne packets into sensor_msgs/PointCloud2, which rviz can display. That wiki page gives some launch file examples you may find helpful.
UPDATE: The 32e_points.launch file will be released shortly. Meanwhile, just start the driver as you did before, and also run the cloud nodelet in a separate terminal:
$ roslaunch velodyne_pointcloud cloud_nodelet.launch calibration:=$(rospack find velodyne_pointcloud)/params/32db.yaml
| | 3 | correct error in example |
As you see, the velodyne_driver publishes /velodyne_packets, a device-dependent data stream that rviz does not understand.
As @dornhege said, you need to run one of the velodyne_pointcloud nodes or nodelets. They will convert the raw Velodyne packets into sensor_msgs/PointCloud2, which rviz can display. That wiki page gives some launch file examples you may find helpful.
UPDATE: The version 0.9.1 with the 32e_points.launch file will be released shortly. Meanwhile, just start You can either check out the driver as you did before, new version and also run build it from source, or wait for the cloud nodelet in Debian packages to be updated (probably a separate terminal:few days).
$ roslaunch velodyne_pointcloud cloud_nodelet.launch calibration:=$(rospack find velodyne_pointcloud)/params/32db.yaml
| | 4 | No.4 Revision |
As you see, the velodyne_driver publishes /velodyne_packets, a device-dependent data stream that rviz does not understand.
As @dornhege said, you need to run one of the velodyne_pointcloud nodes or nodelets. They will convert the raw Velodyne packets into sensor_msgs/PointCloud2, which rviz can display. That wiki page gives some launch file examples you may find helpful.
UPDATE: version 0.9.1 with the 32e_points.launch file will be released shortly. has just been released. You can either check out the new version and build it from source, or wait for the Debian packages to be updated (probably a few days).
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.