| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
Is it possible to implement the navigation stack only allowing forward motion on a differential drive robot?
The reason being that gmapping is sending reverse commands and I only have sensors on the front of the robot, therefore sometimes it reverses into things. Im using frontier exploration if that information is needed.
Also I suppose would frontier exploration need backwards motion?
Hi Miguel,
I'll try to shed some light on this.
Obviously, you can implement the desired behaviour yourself. This would mean implementing a local planner following the 'nav_core::BaseLocalPlanner' interface (see the nav_core documentation).
gmapping is actually "just" doing map building, thus, it does not send any commands. frontier_exploration also just sends goals in terms of geometry_msgs::PoseStamped using the move_base_msgs/MoveBaseAction interface to the move_basenode. move_base is actually the one creating the movement commands.
Thus, you would need to adapt the parameters of you local planner (and probably of you global planner) to achieve the respective behaviour.
Check out the move_base documentation and especially the one for the dwa_local_planner.
I guess you can achieve what you want by setting the parameter ~<name>/min_vel_x for the dwa_local_planner, if you have configured it as local planner in the move_basenode. (I'm not sure, if this works for base_local_planner as well)
This actually depends on the robot you have. move_base has a geometry_msgs::Twist interface. It just sends velocities with respect to the base_link (usually). Thus, if it sends the command to turn, i.e. only rotational velocity, it depends of the controller of your robot what it actually does.
Asked: 2015-07-20 05:31:48 -0500
Seen: 800 times
Last updated: Jul 20 '15
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.
