The safe_base_controller only moves/turns the base if movement/turning in this direction is allowed. It subscribes to the command_limits topic where max and min velocities greater than zero must be published in order for the controller to allow movement.
- Author: Sebastian Haug, Sachin Chita, John Hsu, Melonee Wise
- License: BSD
- Repository: bosch-ros-pkg
- Source: svn http://svn.code.sf.net/p/bosch-ros-pkg/code/tags/stacks/bosch_skin/bosch_skin-0.3.0
Safe Base Controller
The safe_base_controller is a modified base_controller for the PR2. It subscribes to a topic where velocity limits for the base can be specified (implemented in a deadman manner, limits greater than zero have to be periodically granted otherwise the limit will timeout and the base stop).
To use this controller the robot has to be started with the safe_base_controller in the package path. This can be either achieved by checking out and compiling the package as the ros user or by starting the robot with sudo robot start -e. See controller_manager help for more info.
Once the robot has been started and the controller is visible (rosrun pr2_controller_manager pr2_controller_manager list-types) you can start the safe_base_controller with the provided launch file.
safe_base_controllerThe safe_base_controller "node" is started by the controller manager as a realtime controller. Below only new parameters are listed, the ones already included in the original base_controller are omitted.
Subscribed Topicscommand (geometry_msgs/Twist)
- Message which contains the requested velocities with which the base should drive.
- Specifies the maximum velocities the base is allowed to drive. Needs to be send constantly otherwise base will not be allowed to move.
- When the last command_limits message is older than timeout, the base is stopped. (Similar to the parameter timeout which stops the base if no new command message arrives.)