ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
Firstly, I'd try with the baseline TB3 in our little demo world with your launch files / scripts. This way we can tell what issues are in the navigation configuration and which may be caused by your specific environment model or robot models.
Secondly, there may be a serious issue if you see any AMCL particle clouds. AMCL is the localization engine but you've explicitly said you want to be doing SLAM, so you should not expect to see anything from AMCL because it shouldn't even be running.
Thirdly, I'd try slam_toolbox rather than cartographer (for debugging, you're welcome to move back to it later) to see if the changing of SLAM vendors makes it work. Basically, my advice boils down to start with something we know works (like the tutorial) and change 1 thing at a time until it breaks
2 | No.2 Revision |
Firstly, I'd try with the baseline TB3 in our little demo world with your launch files / scripts. This way we can tell what issues are in the navigation configuration and which may be caused by your specific environment model or robot models.
Secondly, there may be a serious issue if you see any AMCL particle clouds. AMCL is the localization engine but you've explicitly said you want to be doing SLAM, so you should not expect to see anything from AMCL because it shouldn't even be running.
Thirdly, I'd try slam_toolbox rather than cartographer (for debugging, you're welcome to move back to it later) to see if the changing of SLAM vendors makes it work. Basically, my advice boils down to start with something we know works (like the tutorial) and change 1 thing at a time until it breaksbreaks. Once it breaks, you have a good idea where the issue lies and then you can ask a follow up question on a more targeted issue.
(assort order around as you like)