The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
move_base is part of the ros navigation stack, which enables 2d navigation. You can use move_base and its global and local planners and costmaps. link You could start here, its a tutorial for the turtlebot, but all the files are on github and you can look them up. Should be mostly remapping topics and tuning the planners (specially the local planner, in the launchfiles and maybe some yaml file). Its made for indoor use though. I would serve the planners a projection gridmap (rtabmap publishes this, I dont have the exact name handy), this is due to the fact that the navigation stack is 2d navigation. To take any kind of obstacle or robot height into consideration you have to "compress"/project the 3d data into the 2d gridmap, but as I said rtabmap delivers this cabability out of the box, rtabmap can also provide localization to correct odometry, just has to be put in localization mode (done in the launchfile). Also I only have seen rtabmap and navigation stack work with a prebuild database. SLAM with navigation stack and some sort of exploration algorithm/package I would only try in a second stage after the navigation with a prebuild database works, and might involve some coding.
| | 2 | No.2 Revision |
move_base is part of the ros navigation stack, which enables 2d navigation. You can use move_base and its global and local planners and costmaps. link You could start here, its a tutorial for the turtlebot, but all the files are on github and you can look them up. Should be mostly remapping topics and tuning the planners (specially the local planner, in the launchfiles and maybe some yaml file). Its made for indoor use though. I would serve the planners global planner a projection gridmap (rtabmap publishes this, I dont have the exact name handy), this is due to the fact that the navigation stack is 2d navigation. To take any kind of obstacle or robot height into consideration you have to "compress"/project the 3d data into the 2d gridmap, but as I said rtabmap delivers this cabability out of the box, rtabmap can also provide localization to correct odometry, just has to be put in localization mode (done in the launchfile). Also I only have seen rtabmap and navigation stack work with a prebuild database. SLAM with navigation stack and some sort of exploration algorithm/package I would only try in a second stage after the navigation with a prebuild database works, and this might involve some coding. coding.
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.
