turtlebot3 VS navigation2

You could try downloading the package: https://github.com/ROBOTIS-GIT/turtlebot3/tree/humble-devel and just build / run in your iron workspace.

git clone https://github.com/ROBOTIS-GIT/turtlebot3.git -b foxy-devel

To give more context, I am using ROS2 (robot operating system) to build a small mobile robot for hobby/learning. To learn by ready other code, I am looking at a very popular ROS project called Turtlebot3.

You can copy and modify the (turtlebot3)[https://github.com/ROBOTIS-GIT/turtlebot3] repo as basis. They have different robot models for gazibo simulation and starting point for ros navigation.

- if you want to later make a more complicated robot (that uses cameras, has robotic arm etc.) you'd want to look into ROS (robot operating system). If you are in/going to university I highly recommend you join an engineering design team. For an example project you can refer to https://github.com/ROBOTIS-GIT/turtlebot3

The tutorial I was using (which comes straight from nav2) says to run ros2 launch nav2_bringup navigation_launch.py . However, when I went to tune Turtlebot3 via the .param file, it did no change whatsoever. This is because, by default, the file uses up this param file that is significantly different than burger.yaml; After changing it the costmap looks completely different. After reading the source code for the .launch file of the Turtlebot3 nav package for galactic and nav2, I've found out that running ros2 launch nav2_bringup navigation_launch.py params_file:=[PATH_TO_BURGER_YAML] works and completely fixes this issue.

If you're looking for an example of setting the local planner then the turtlebot3 (which I've seen you're using in your delivery_robot_sample package) has an example here: https://github.com/ROBOTIS-GIT/turtlebot3/blob/master/turtlebot3_navigation/launch/move_base.launch

This line might be your issue according to this github issues post (comment at the very bottom: https://github.com/ros-planning/navigation2/issues/2283)

I recently stumbled upon system tests for Nav2, I didn't dive into details but README says that among other things they test robots in sandbox environment, might be useful.

The tutorial I was using (which comes straight from nav2) says to run ros2 launch nav2_bringup navigation_launch.py . However, when I went to tune Turtlebot3 via the .param file, it did no change whatsoever. This is because, by default, the file uses up this param file that is significantly different than burger.yaml; After changing it the costmap looks completely different. After reading the source code for the .launch file of the Turtlebot3 nav package for galactic and nav2, I've found out that running ros2 launch nav2_bringup navigation_launch.py params_file:=[PATH_TO_BURGER_YAML] works and completely fixes this issue.

I am using the nav2_bringup example (https://github.com/ros-planning/navigation2/blob/main/nav2_bringup/launch/multi_tb3_simulation_launch.py) to launch multiple robots, it works fine. This file launches a file for single robots in different namespaces. This file for single robots is also able to switch from localization to mapping, simply by launching the file with argument slam:=True. I added slam as a launch argument for tb3_simulation_launch.py when launched from multi_tb3_simulation_launch.py and when i start the multirobot file with slam:=True it seems to work partially. ROS topics with the name /robot1/slam_toolbox/feedback,/robot1/slam_toolbox/update and /robot2/slam_toolbox/feedback ,/robot2/slam_toolbox/update get created, but /slam_toolbox/graph_visualization and /slam_toolbox/scan_visualization are only there once and not for every robot. In RVIZ there is no sign of SLAM working.

Hey, I am not sure if you can or even want but you could have a look into the C++ DWB planner plugin which is used in the nav2 stack.

I have tried all different kinds of headers in the python script (for instance, I have tried a header format like this), and it still complains about copyright linting. I have tried to remove every reference to linting in my package.xml and CMakeLists.txt but colcon/ament just keeps complaining about linting errors.