ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
@kmhallen is right: don't run the cloud node, because VLP16-points.launch
already starts the cloud nodelet. Since they are both publishing the same information to the /velodyne_points
topic, the result will be confusing and waste cycles and bandwidth.
The recommended method is to attach the Velodyne to its own ethernet port with a statically assigned IP in the 192.168.1.x
range. We normally do it via the Ubuntu network manager like this:
192.168.1.77
255.255.255.0
192.168.1.0
Setting up a VLP-16 is very similar to this 32E tutorial.
2 | No.2 Revision |
@kmhallen is right: don't run the cloud node, because VLP16-points.launch
already starts the cloud nodelet. Since they are both publishing the same information to the /velodyne_points
topic, the result will be confusing and waste cycles and bandwidth.
The recommended method is to attach the Velodyne to its own ethernet port with a statically assigned IP in the 192.168.1.x
range. We normally do it via the Ubuntu network manager like this:
192.168.1.77
255.255.255.0
192.168.1.0
Setting up a VLP-16 is very similar to this 32E tutorial. We'd like to make a VLP-16 version of that tutorial some time soon.