Open Source RoboticsRobots, software & learning

Nav2

Software

ROS 2 navigation framework with configurable bringup, localization and behavior-tree navigation; robot and distribution matching are essential. [1]

Installation & first result →Official websiteGetting started

For
ROS 2 developers integrating mobile-robot navigation [1]
Source rights
Some licenses are unresolved. Review licenses
Unknowns
operating system, compute requirements not fully established. Review gaps

Source researched · Not tested by us
Sources checked · Research details

Licenses & related hardware
License
not fully assessed for software, documentation · Details by part

Requirements · Research details and dates

On this page

Overview

Nav2 supplies a ROS 2 navigation framework. This profile preserves repository release 1.5.2 and separately checks the current Rolling documentation. Those are different snapshots: use the documentation and packages for the ROS distribution you intend to run, rather than treating the preserved tag as the current Rolling installation. [1] [2] [6] [7]

Is this for you?

Workflows
  • Launch simulated TurtleBot navigation
  • Set an initial pose and send a navigation goal through RViz
  • Adapt bringup and parameters for a particular robot

[5] [7]

Known limitations
  • The preserved 1.5.2 repository and current Rolling documentation are separate evidence snapshots
  • Example bringup must be adapted to the actual robot, map and hardware
  • Rolling quickstart warns that a source build is needed
  • No navigation, localization or obstacle-avoidance performance measured

Source comparison and scope of this review.

[5] [6] [7] · Editorial assessment

What you need

Dependencies
  • ROS 2 environment matched to the selected branch/packages
  • Robot-specific navigation configuration
  • Gazebo and RViz for the documented TurtleBot simulation

[5] [7] [9]

Installation & first result

Open the upstream getting-started guide [7] · Project documentation [7]

  • Choose matching ROS/Nav2 documentation and packages
  • Launch the documented simulation bringup
  • Set the initial pose in RViz
  • Send a navigation goal and exercise cancellation
  • Create robot-specific configuration before attempting physical navigation

Editorial progression from the documented simulation example; not tested here.

[5] [7] · Editorial assessment

Installation

Choose a supported ROS distribution and follow its documentation. Current Rolling quickstart explicitly says Rolling binaries are not released and requires a source build, despite showing a generic apt example.

[7] [9]

Hardware, models & data

File formats
  • ROS 2 YAML configuration
  • Robot URDF in the simulation bringup

[5] [7]

Project notes

Start with the simulation bringup

The current quickstart launches a TurtleBot simulation with Nav2, AMCL localization, robot-state transforms, Gazebo and RViz. After launch, the user supplies an approximate initial pose in RViz, then sends a navigation goal. The initial pose completes the transform setup needed for that example; starting the processes alone is not the whole setup. The RViz plugin also provides cancellation and reset controls. None of these operations were executed in this source review. [7]

The Rolling page explicitly warns that Rolling binaries are not currently released and directs users to build from source. It also shows generic package-install commands, so that command block should not be read as proof of Rolling binary availability. Follow the selected distribution's installation route. [7] [9]

Treat the example as a starting configuration

The pinned nav2_bringup README expects a robot-specific navigation package adapted for its maps, robot, hardware and world. It describes optional composition, enabled by default in that example, which groups Nav2 nodes into one process; it can be disabled through the launch configuration. This is a deployment choice to evaluate for the actual system, not a measured performance advantage established here. [5]

A successful TurtleBot example does not validate another robot's localization, sensing, motion behavior or obstacle response. The useful next step is to make that robot's configuration explicit and test its navigation behavior in the chosen environment. No hardware trial or navigation benchmark is claimed by this profile. [5] [7]

Keep the source and documentation trail

The pinned README contains unversioned documentation links, while the separately retrieved quickstart belongs to the current Rolling documentation tree. Both source snapshots are retained so readers can distinguish the release evidence from the current instructions. [1] [7]

The bringup package declares Apache-2.0, but the repository is mixed-license: its root notice lists LGPL-2.1-or-later, Apache-2.0, BSD-3-Clause and combined terms, directing readers to each package.xml and file notice. Otherwise unmarked files default to Apache-2.0. Check the specific packages and files being reused; external dependencies, independently acquired maps and website imagery require separate checks. [3] [6]

What we checked

Source research only; no installation, physical build or performance test performed. No affiliate links added.

Not yet established

  • Requirements: operating system, host computer
  • Version-specific hardware compatibility (ecosystem tags alone do not establish it)

Updates

Upstream last updated
Sep 16, 2026 [2]
Latest release
Sep 16, 2026 [2]
Profile updated
Oct 4, 2026
Sources last checked
Sep 30, 2026
Next review
Oct 30, 2026
Reviewed revision
7b9be248a652224a19305469fd5e854d50512341 (release 1.5.2) · software repository

Source files and licenses

Available project sources support research coverage; complete build and commercial qualification remain separate.

LayerAvailability / license
softwareavailable · License not fully assessed
Mixed-license repository: LGPL-2.1-or-later, Apache-2.0, BSD-3-Clause and combined terms. Check each package.xml and file notice. nav2_bringup specifically declares Apache-2.0. [3] [6]
documentationavailable · License not fully assessed
Repository uses package/file-specific terms; unmarked files default Apache-2.0. External website separately captured as evidence; no images reused or website-wide license inferred. [3] [5]

Navigation framework profile does not select a trained policy or training dataset.

References

Each source links to the exact revision we read. “Used for” shows where this page relies on it.

Project sources

Videos

Correction guidance · Discussion is not enabled · Profile format 0.6.0-draft.1

Change history

2026-10-04 — Added 3 YouTube reference(s) (S010, S011, S012): official channel or videos linked from the pinned upstream sources. Existing claims, source-check dates and evidence are unchanged.