Open jaeseok4104 opened 1 year ago
For your target frame to be odom
, there must be a valid set of transforms between the velodyne's frame (by default, velodyne
) and the odom
frame. Is this true for your setup?
how can i set odom to velodyne frame? when i use this driver, should i make odom to velodyne tf?
I didn't understand what you said. I think this driver posts point cloud in velodyne frames, and I think if I set to velodyne frames in rviz, I should be able to see point cloud data.
when i use ros-noetic i could used this driver. don't surrport melodic version?
how can i set odom to velodyne frame? when i use this driver, should i make odom to velodyne tf?
If you want to use an /odom
frame then yes, you need to publish a TF between /velodyne
(the default frame for the sensor) and /odom
. If you do not want to use /odom
then you can just change rviz
to view in /velodyne
frame.
when i use ros-noetic i could used this driver. don't surrport melodic version?
melodic
was supported until 2 weeks ago when melodic
became end-of-life. The driver was confirmed to work on melodic
by many users for a very long time. If you still want to use melodic
, you can use the melodic-devel
branch of this repository or the apt
package.
Please complete the following information:
sudo dpkg -s ros-$ROS_VERSION-velodyne
, if from source, give commit hash]Describe the bug
![image](https://github.com/ros-drivers/velodyne/assets/51950819/eb29a73f-0e69-4a27-b116-0bddbe789db7)
didn't published sensor_msgs/pointcloud2 how can i fix this error?
when i set 1.5.2 version, work for me. but I cannot use high version
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen.
Additional context Add any other context about the problem here.