Turtlebot3 Refuses to Move in a Straight Line

• navigation2

  9 2,473 9.6 C++

  ROS 2 Navigation Framework and System

  

  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.

• InfluxDB

  www.influxdata.com featured

  Purpose built for real-time analytics at any scale. InfluxDB Platform is powered by columnar analytics, optimized for cost-efficient storage, and built with open data standards.

  

• navigation2_tutorials

  1 184 4.7 C++

  Tutorial code referenced in https://docs.nav2.org/

  

  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.

• turtlebot3

  8 1,468 0.0 Python

  ROS packages for 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.

Suggest a related project