support for multiple velodynes

No known models are currently known to return closer measurements.

NOTE: There is still some other problem keeping that from working.

…s#63)

I think that `dsr` was unused. See line 317: 

for (int dsr=0; ...

Remove unused variable

Correct important data type error for VLP-16

Fix output of calibration data onto console

Documentation tools create this folder that shall not be uploaded to git.

Previously, transform_node has neither read parameters other than frame_id from the command line nor has it exposed these parameters via dynamic reconfigure. As parameters like max_range and view_width have been initialized to zero, the inconfigurable transform_node has returned an empty point cloud.

Now, transform_node launches an reconfigure server just as cloud_node. In contrast to cloud_node, transform node exposes another parameter for dynamic reconfiguration: frame_id, i.e. the frame of reference the incoming Velodyne points are transformed to.

allow floats in min/max_intensity and make horiz_offset_correction optional

Fix pr 80; adding travis CI tests.

Sign inversion in some equations

…rs#84)

This fixes a regression in the 32e and VLP-16 calibrations which do not contain
intensity values. There is still a problem with the 64e_s2.1 calibration.

This currently fails on 64e_s2.1-sztaki.yaml and on issue_84_float_intensities.yaml.

)

…r/velodyne

Use tf2_ros static_transform_publisher for more consistent timing (ros-drivers#2)

…ros-drivers#78

…rivers#78)

The value of time_offset is added to the calculated time stamp in live mode for each packet.

Add dynamic latency configuration to velodyne_driver

update velodyne_driver package description to include all models

address build warning for strict-aliasing.

velodyne/velodyne_pointcloud/src/conversions/colors.cc:84:58:
 error: dereferencing type-punned pointer will break strict-aliasing rules [-Werror=strict-aliasing]
         p.rgb = *reinterpret_cast<float*>(&rainbow[color]);
                                                          ^

that last_azimuth_diff variable may be used uninitialized.  Variable
is now initialized to 0 at creation.

velodyne/velodyne_pointcloud/src/lib/rawdata.cc:328:57: error: ‘last_azimuth_diff’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
           azimuth_corrected_f = azimuth + (azimuth_diff * ((dsr*VLP16_DSR_TOFFSET) + (firing*VLP16_FIRING_TOFFSET)) / VLP16_BLOCK_TDURATION);

GCC Build Warnings

velodyne_driver: use port number for PCAP data (ros-drivers#46, ros-drivers#66)

Also verified with sensor. It reduced overlap in the pointcloud

updated VLP-16 packet rate from user manual.

Fix for device_ip filter in InputSocket: initialization of devip_ for correct ip filtering in InputSocket::getPacket.

intensity and VPoint::intensity are both of type float.

- rpm, device_ip, port, read_once, read_fast, repeat_delay

Fix misleading typecasts.

DISTANCE_MAX and DISTANCE_MAX_UNITS are not used anywhere in the code.

Furthermore, using them would lead to errors as both VLP-64 manuals state that returns above 120 m should not be used. The VLP-32 manual allows 70 m as the maximum valid sensor range.

Add more options in launch files.

Remove unused constants.

velodyne_driver/src/lib/input.cc : fix for device_ip filter

…ed calibration file. This method is useful when processing data offline from a bag file, without starting any ros master

Added an interface to set up raw data processing offline

…ros-drivers#93)

This eliminates a CMake warning when building on Xenial.

Fixed bug. Laserscans now cover full 360 degrees.

…_support

Add VLP16 Puck Hi-Res config file

Modern pluginlib macro

Added velodyne_laserscan package

…olkandre/velodyne into cut_at_specified_angle_feature

…here: ros-drivers#126 (comment)