Open YangJunghoon opened 2 months ago
Set the model ID to VLS128
to fix the issue.
i tried that Node( package='velodyne_driver', executable='velodyne_driver_node', name='velodyne_driver', parameters=[{ 'frame_id': 'velodyne', 'model': 'VLS128' }], output='screen' ), Node( package='velodyne_pointcloud', executable='velodyne_transform_node', name='velodyne_transform', parameters=[{ 'min_range': 0.4, 'max_range': 130.0, 'calibration': 'config/VLS128.yaml', 'model': 'VLS128' }], output='screen' ) but return error [velodyne_transform_node-2] [INFO] [1727073236.440597056] [velodyne_transform]: correction angles: config/VLS128.yaml [velodyne_driver_node-1] terminate called after throwing an instance of 'std::runtime_error' [velodyne_driver_node-1] what(): Unknown Velodyne LIDAR model: VLS128 [velodyne_transform_node-2] [WARN] [1727073236.447534543] [velodyne_pointcloud]: Timings not supported for model VLS128 [velodyne_transform_node-2] [WARN] [1727073236.447553540] [velodyne_pointcloud]: NO TIMING OFFSETS CALCULATED. ARE YOU USING A SUPPORTED VELODYNE SENSOR? [ERROR] [velodyne_driver_node-1]: process has died [pid 94803, exit code -6, cmd '/opt/ros/humble/lib/velodyne_driver/velodyne_driver_node --ros-args -r __node:=velodyne_driver --params-file /tmp/launch_params_t0ly_cme'].
Ok, that's a bug in the driver then: https://github.com/ros-drivers/velodyne/blob/d8cf623a922b1f12995e8c71295924c2905bd9a3/velodyne_pointcloud/src/lib/rawdata.cpp#L188-L210
Btw, you can give https://github.com/valgur/velodyne_decoder a try. It's not a direct replacement, but the precise timing info for VLS-128 is definitely supported there, together with dual-return support and other improvements.
Please complete the following information:
Describe the bug velodyne_transform_node-2] [INFO] [1727069870.757835119] [velodyne_transform]: correction angles: config/VLS128.yaml [velodyne_driver_node-1] terminate called after throwing an instance of 'std::runtime_error' [velodyne_driver_node-1] what(): Unknown Velodyne LIDAR model: VLS-128
To Reproduce Steps to reproduce the behavior:
Expected behavior using VLS-128 driver