| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
I saw on the wiki that some of the Subscribed Topics, Published Topics, and Services of the rtabmap node were marked as Planning. I think does this mean that it is possible to use only rtabmap node to complete the robot's path planning, so that the robot can reach the predetermined target and avoid obstacles that appear on the path?
I asked the same question in the Official RTAB-Map Forum.
I didn't know it was possible until you had asked. Apparently it is supported according to a forum post here
I feel the forum post sums it up nicely:
rtabmap does topological planning with its graph. The global path would be all nodes to be traversed on the map's graph to reach the goal. The local graph is the upcoming nodes (up to RGBD/LocalRadius, default 10 meters) that should be loaded in Working Memory so that the robot can localize on the path. In this topological planning, there is no explicit obstacle detection (the grid map is not used), it is just assumed that poses on the graph are cleared from obstacle (which should be the case if the robot moved on these particular locations). Normally, rtabmap planning would be integrated on top of move_base navigation for metric planning, which will do obstacle avoidance using the grid map generated by rtabmap. rtabmap sends goals to move_base, then move_base sends velocity commands to robot controller.
So basically it is able to provide a global path towards a goal, but relies on move_base to actually get the robot to follow the path, send velocity goals to your controller module and avoid pbstacles. I assume this is not the default use case for RTAB-MAP as most people would use it to loaclize (get xyz position) and rely on move_base to plan paths and avoid obstacles. But it is definitely possible to plan paths with it, although I'm not sure of what is the benefit.
Thx for the answer. To add to benefits:
More details in this paper.
Beside the paper I mentioned that is more theorical, there is no tutorial for that. The launch used in that paper was az3_nav.launch (rtabmap and move_base connected by actionlib api). The patrol example can be done with the script patrol.py:
$ patrol.py kitchen living_room bathroom
Actually, you can try it with the turtlebot example (tested on melodic). In rviz, open Tools properties and change /move_base_simple/goal to /rtabmap/goal, and the goal will pass by rtabmap instead. You can also do:
# To go to node 20
rosservice call /rtabmap/set_goal 20 "" ""
# or label node 20 as kitchen, then move to it
rosservice call /rtabmap/set_label 20 kitchen
rosservice call /rtabmap/set_goal 0 "kitchen" ""
You can add MapGraph (/rtabmap/mapGraph) and MarkerArray (/rtabmap/labels) to RVIZ to see the graph with labels and node ids.
Asked: 2020-04-17 02:25:33 -0500
Seen: 1,039 times
Last updated: Aug 09 '21
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.