The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
Provided you can provide a detailed bug report (preferably with some instructions for reproduction), it would make sense to open a ticket on the Gazebo Bitbucket issue tracker.
I didn't notice this problem so far. I noticed other issues with Sensors in newer Gazebo versions as described here however (probably not related, but maybe).
It sounds a lot like your issue is related to Gazebo internals, so properly solving it would require some changes in source code. A quick hack for fixing it could be moving the sensor and collision geometry a bit further apart from each other. As sonar sensors are quite noisy and partly unreliable in the real world, you could also consider the erroneous data a feature :D.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
