Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

Revision history [back]

We found out that the prohibition areas plugin were consuming too much of our robot, removing them stopped that problem. (Prohibition areas made our Raspberry CPU go to 100%, while without it it wont go past 25%..). Probably sometimes it would freeze and not compute its odometry correctly, therefore thinking that it was seeing a wall when it wasn't.

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.