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]

Recovery Behaviors as they are usually implemented take full control of the robot and of move_base. Basically move_base turns to the recovery behavior and waits until it is complete. It is not interleaved or continuously called or watched from move_base. Essentially you've created a dead-lock where you wait for move_base and move_base waits for you to complete.

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.