Revision history [back]

It's probably not a bug.

Changing min_range works for me. Note that the minimum supported in hardware is 0.9 meters.

It's probably not a bug.

Changing Setting min_range works for me. Note that the minimum supported in hardware is 0.9 meters.

$ rosparam set /cloud_nodelet/min_range 10.0

$ roslaunch velodyne_driver nodelet_manager.launch model:=32E
$ roslaunch velodyne_pointcloud cloud_nodelet.launch min_range:=0.9

It's probably not a bug.

Setting min_range works for me. Note that the minimum supported in hardware is 0.9 meters.

Update: From your screenshot, it appears that you changed the parameter after the driver was running using a command like:

$ rosparam set /cloud_nodelet/min_range 10.0

The currently-released driver does not re-read parameters once it is running. So, you need to set the desired value while launching the driver. In two separate terminals try this:

$ roslaunch velodyne_driver nodelet_manager.launch model:=32E
$ roslaunch velodyne_pointcloud cloud_nodelet.launch min_range:=0.9

The reason it requires two roslaunch commands is because the 32e_points.launch script does not provide the for min_range and max_range arguments. They could easily be added. If that was the root cause of your confusion, please make a comment, and I will add them in some future version, probably for ROS Indigo.

The latest not-yet-released sources support dynamic reconfigure. If you know how to build a catkin workspace, check out the code, and build it, you are welcome to try that version. It should work on Hydro and probably Groovy. Indigo is not supported yet, but should be soon.

It's probably not a bug.

Setting min_range works for me. Note that the minimum supported in hardware is 0.9 meters.

Update: From your screenshot, it appears that you changed the parameter after the driver was running using a command like:

$ rosparam set /cloud_nodelet/min_range 10.0

The currently-released driver does not re-read parameters once it is running. So, you need to set the desired value while launching the driver. In two separate terminals try this:

$ roslaunch velodyne_driver nodelet_manager.launch model:=32E
$ roslaunch velodyne_pointcloud cloud_nodelet.launch min_range:=0.9

The reason it requires two roslaunch commands is because the 32e_points.launch script does not provide the for min_range and max_range arguments. They could easily be added. If that was the root cause of your confusion, please make a comment, and I will add them in some future version, probably for ROS Indigo.

The latest not-yet-released sources support dynamic reconfigure. If you know how to build create a catkin workspace, check out the code, and build it, you are welcome to try that version. It should work on Hydro and probably Groovy. Indigo is not supported yet, but should be soon.

It's probably not a bug.

Setting min_range works for me. Note that the minimum supported in hardware is 0.9 meters.

Update: From your screenshot, it appears that you changed the parameter after the driver was running using a command like:

$ rosparam set /cloud_nodelet/min_range 10.0

The currently-released driver does not re-read parameters once it is running. So, you need to set the desired value while launching the driver. In two separate terminals try this:

$ roslaunch velodyne_driver nodelet_manager.launch model:=32E
$ roslaunch velodyne_pointcloud cloud_nodelet.launch min_range:=0.9

The reason it requires two roslaunch commands is because the 32e_points.launch script does not provide the for min_range and max_range arguments. They could easily be added. If that was the root cause of your confusion, please make a comment, and I will add them in some future version, probably for ROS Indigo.

The latest not-yet-released sources support dynamic reconfigure. If you know how to create a catkin workspace, check out the code, and build it, you are welcome to try that version. It should work on Hydro and probably Groovy. Indigo is not supported yet, but should be soon.