ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange

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]

Take a look at costmap2d parameters. The navigation stack has given you the warning and told you why the robot is not moving:

[/move_base]:Sensor data is out of date, we're not going to allow commanding of the base for safety

You might want to increase your laser scan publish rate (if possible), or tweak some of the parameters in costmap_common_params.yaml Perhaps higher transform tolerance? Or change the expected update rate of the laser scan?

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.

Powered by Askbot version 0.10.2