Closed jrharbin-york closed 1 year ago
I managed to fix it myself... I think it was to do with using the GPU plugin, libgazebo_ros_gpu_laser.so which was not compatible with my current AMD RX580 GPU, and therefore silently failing.
Editing pmb2_description/urdf/sensors/sick_tim571_laser.gazebo.xacro and changing the plugin filename from libgazebo_ros_gpu_laser.so to libgazebo_ros_laser.so, and the sensor type from "gpu_ray" to "ray" fixed it.
Now the lasers are shown on Gazebo and the costmaps etc shown.
Soon I will be able to test it on a new PC with an Nvidia 3060 GPU, I suspect it works without this workaround on a recent Nvidia GPU.
I don't know if you have already found and fixed this, as I know you're aware of at least one bug, but I was looking again today at the laser scans and they are all empty?
The scan topics published by gazebo e.g. /omni1/scan_rear_raw and /omni1/scan_rear_front have constant range data of -inf and intensities of 1.0.
This is probably a Gazebo error then, given that Gazebo should be the publisher of the raw laser scan data? I found the following errors in /home/jharbin/.gazebo/client-11345 related to the model files, which I don't know if they are related?