Nav2 in ROS 2 overview

Introduction

Nav2 helps robots move safely and smartly in places. It plans paths and avoids obstacles so robots reach their goals.

When you want a robot to move from one spot to another inside a building.

When a robot needs to avoid obstacles while moving around.

When you want to control robot navigation using ROS 2 tools.

When you need a flexible system to add custom behaviors to robot movement.

When testing robot navigation in simulation before real-world use.

Syntax

ROS

ros2 launch nav2_bringup navigation_launch.py

This command starts the Nav2 system using a launch file.

You can customize the launch file to fit your robot and environment.

Examples

Starts Nav2 using simulation time, useful when running in a simulator like Gazebo.

ROS

ros2 launch nav2_bringup navigation_launch.py use_sim_time:=true

Runs a simple program to send navigation goals to Nav2.

ROS

ros2 run nav2_simple_commander simple_commander

Sample Program

This program creates a ROS 2 node that sends a navigation goal to Nav2 once. The robot will try to move to position (1.0, 1.0) on the map.

ROS

# This is a simple Python example to send a navigation goal using Nav2 in ROS 2
import rclpy
from rclpy.node import Node
from geometry_msgs.msg import PoseStamped

class SimpleNav(Node):
    def __init__(self):
        super().__init__('simple_nav')
        self.publisher = self.create_publisher(PoseStamped, 'goal_pose', 10)
        self.timer = self.create_timer(2.0, self.send_goal)
        self.sent = False

    def send_goal(self):
        if not self.sent:
            goal = PoseStamped()
            goal.header.frame_id = 'map'
            goal.pose.position.x = 1.0
            goal.pose.position.y = 1.0
            goal.pose.orientation.w = 1.0
            self.publisher.publish(goal)
            self.get_logger().info('Goal sent to Nav2')
            self.sent = True


def main(args=None):
    rclpy.init(args=args)
    node = SimpleNav()
    rclpy.spin(node)
    node.destroy_node()
    rclpy.shutdown()

if __name__ == '__main__':
    main()

Important Notes

Nav2 uses many parts like map servers, planners, and controllers working together.

You can test Nav2 in simulators before using real robots.

Make sure your robot's sensors and odometry data are correctly set up for good navigation.

Summary

Nav2 helps robots plan and move safely in ROS 2 environments.

It is used for real and simulated robot navigation tasks.

You send goals to Nav2, and it handles path planning and obstacle avoidance.

Practice

1. What is the primary purpose of Nav2 in ROS 2?

easy

A. To process sensor data for object recognition

B. To control robot arm movements

C. To manage robot battery levels

D. To help robots plan paths and navigate safely

Solution

1. Step 1: Understand Nav2's role in ROS 2

   Nav2 is designed to help robots move safely by planning paths and avoiding obstacles.

2. Step 2: Compare options with Nav2's function

   Only To help robots plan paths and navigate safely describes path planning and safe navigation, which matches Nav2's purpose.

3. Final Answer:

   To help robots plan paths and navigate safely -> Option D

4. Quick Check:

   Nav2 = path planning and navigation [OK]

Hint: Nav2 is about robot movement and path planning [OK]

Common Mistakes:

• Confusing Nav2 with sensor processing
• Thinking Nav2 controls robot arms
• Assuming Nav2 manages hardware like batteries

2. Which of the following is the correct way to send a navigation goal to Nav2 in ROS 2?

easy

A. ros2 service call /start_navigation std_srvs/Empty '{}'

B. ros2 topic pub /cmd_vel geometry_msgs/Twist '{linear: {x: 1.0}}'

C. ros2 action send_goal /navigate_to_pose nav2_msgs/action/NavigateToPose '{pose: {position: {x: 1.0, y: 2.0}}}'

D. ros2 param set /nav2_controller speed 1.0

Solution

1. Step 1: Identify the command to send a navigation goal

   The correct command uses ros2 action send_goal with the NavigateToPose action and a pose message.

2. Step 2: Check other options for correctness

   ros2 topic pub /cmd_vel geometry_msgs/Twist '{linear: {x: 1.0}}' publishes velocity commands, not goals. ros2 service call /start_navigation std_srvs/Empty '{}' calls a service unrelated to sending goals. ros2 param set /nav2_controller speed 1.0 sets parameters, not goals.

3. Final Answer:

   ros2 action send_goal /navigate_to_pose nav2_msgs/action/NavigateToPose '{pose: {position: {x: 1.0, y: 2.0}}}' -> Option C

4. Quick Check:

   Send goal = ros2 action send_goal [OK]

Hint: Use ros2 action send_goal for Nav2 goals [OK]

Common Mistakes:

• Using topic publish instead of action send_goal
• Calling unrelated services
• Setting parameters instead of sending goals

3. Given the following Nav2 action client code snippet in ROS 2, what will be the output if the robot successfully reaches the goal?

client.send_goal(goal_msg)
result = client.get_result()
print(result.status)

medium

A. An integer status code indicating success

B. A string message describing the error

C. A boolean True if goal reached, False otherwise

D. No output, the code will raise an exception

Solution

1. Step 1: Understand Nav2 action client result

   The get_result() method returns a result object with a status code as an integer.

2. Step 2: Interpret the printed status

   Printing result.status outputs an integer code representing success or failure, not a string or boolean.

3. Final Answer:

   An integer status code indicating success -> Option A

4. Quick Check:

   result.status = integer code [OK]

Hint: Nav2 action results use integer status codes [OK]

Common Mistakes:

• Expecting a string message instead of code
• Thinking result.status is boolean
• Assuming code raises exception on success

4. You wrote a Nav2 client node but it never moves the robot after sending a goal. Which of the following is the most likely cause?

medium

A. The robot's wheels are physically blocked

B. The Nav2 stack is not running or not properly launched

C. The robot's battery is low

D. The goal message has an incorrect frame_id

Solution

1. Step 1: Check common Nav2 goal issues

   If the Nav2 stack is not running or not properly launched, the robot will not move because the navigation system is inactive.

2. Step 2: Evaluate other options

   While an incorrect frame_id can cause issues, the most common cause when the robot never moves after sending a goal is that the Nav2 stack is not running. Hardware issues like blocked wheels or low battery are less likely in software debugging context.

3. Final Answer:

   The Nav2 stack is not running or not properly launched -> Option B

4. Quick Check:

   Nav2 stack running = robot moves [OK]

Hint: Ensure Nav2 stack is running if robot doesn't move [OK]

Common Mistakes:

• Assuming Nav2 stack is always running
• Ignoring coordinate frame mismatches
• Blaming hardware before software checks

5. You want your robot to navigate through a dynamic environment using Nav2 in ROS 2. Which combination of Nav2 components should you configure to ensure the robot replans paths when obstacles move?

hard

A. Use the planner_server with a global planner and enable the controller_server with obstacle avoidance

B. Use only the behavior_tree without planners or controllers

C. Disable the controller_server and rely on manual velocity commands

D. Use the map_server alone to update the robot's position

Solution

1. Step 1: Identify components for path planning and obstacle avoidance

   The planner_server creates global paths, and the controller_server handles local obstacle avoidance and path following.

2. Step 2: Understand dynamic replanning needs

   Enabling both planner and controller servers allows Nav2 to replan paths when obstacles move, ensuring safe navigation.

3. Final Answer:

   Use the planner_server with a global planner and enable the controller_server with obstacle avoidance -> Option A

4. Quick Check:

   Planner + Controller = dynamic replanning [OK]

Hint: Planner and controller servers enable dynamic path replanning [OK]

Common Mistakes:

• Ignoring controller_server role in obstacle avoidance
• Thinking behavior_tree alone handles planning
• Relying only on map_server for navigation