You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Using the same pcap file, the velodyne_packets and velodyne_pointcloud output from ros1 and ros2 are different, leading the visualization in rviz show different. ros2 pipeline shows multiple reflection of the same objects at wront location. (like a ghost image)
See rviz output video below:
ROS1:
ROS1.mp4
ROS2:
ROS2.mp4
I exam the velodyne_driver output, (topic velodyne_packets), for the first output frame (using rostopic echo -n 1 for ros1 or ros2 topic echo --once in ros2), ros1 has more packets (151 packets) than ros2(128 packets). (The actual data for the 128 packets from ros2 are the same as those in ros1 output, just missing the rest packets). I wonder what make the velodyne driver treat the same pcap file differently?
The text was updated successfully, but these errors were encountered:
I found this issue is has nothing to do with the driver, but related to the pointcloud calibration file. If I change all the rot_correction to 0.0, I would be normal again.
@JWhitleyWork
Do you know how the calibration file/rot_crrection works?
Please complete the following information:
ROS1:
ROS2:
Describe the bug
Using the same pcap file, the velodyne_packets and velodyne_pointcloud output from ros1 and ros2 are different, leading the visualization in rviz show different. ros2 pipeline shows multiple reflection of the same objects at wront location. (like a ghost image)
See rviz output video below:
ROS1:
ROS1.mp4
ROS2:
ROS2.mp4
I exam the velodyne_driver output, (topic velodyne_packets), for the first output frame (using
rostopic echo -n 1
for ros1 orros2 topic echo --once
in ros2), ros1 has more packets (151 packets) than ros2(128 packets). (The actual data for the 128 packets from ros2 are the same as those in ros1 output, just missing the rest packets). I wonder what make the velodyne driver treat the same pcap file differently?The text was updated successfully, but these errors were encountered: