ROS 2
SoftwareLibraries and tools for robot applications, reviewed through a Humble release manifest and version-matched documentation for installation and node communication. [5] [6] [12]
Installation & first result →Official websiteGetting started
- For
- Robot software developers who need middleware, tools and a package ecosystem [1]
- Source rights
- Some licenses are unresolved. Review licenses
- Unknowns
- compute requirements not fully established. Review gaps
Source researched · Not tested by us
Sources checked · Research details
Licenses & related hardware
- Robots
- da Vinci Research Kit (dVRK), Maker's Pet Loki, Maker's Pet Snoopy, OpenAMRobot mobile base (OpenAMR), OpenMANIPULATOR-X, Reachy 2 and 3 moreTagged in our catalog; tags do not establish tested compatibility.
- License
- CC-BY-4.0 · license not fully assessed for software · Details by part
Overview
ROS 2 is a collection of libraries and tools for building robot applications from communicating components. This review uses the release-humble-20260914 source manifest and separately preserved Humble documentation. Humble is the selected evidence scope, not a claim that it is the newest ROS distribution or the right choice for every robot. Check the target robot's drivers and tutorial requirements before choosing a distribution. [2] [5] [12]
Is this for you?
- Workflows
- Compose a graph of nodes
- Exchange data through topics
- Request computations through services or actions
- Develop packages against a selected ROS distribution
- Known limitations
- The ros2 repository is a release/source manifest, not a monolithic archive of all ROS packages
- A successful talker/listener demo does not validate a robot driver or complete control system
- Licenses and supported distributions must be checked per package
Manifest scope and demo limits are editorial qualifications of the inspected sources.
What you need
- Operating system
- Ubuntu 22.04 amd64/arm64 for the Humble deb route selected here
Scoped entry route; not an exhaustive list of ROS distributions or source-build platforms.
- Languages / runtimes
- C++
- Python
Demonstrated client API examples, not an exhaustive language list.
- Dependencies
- Distribution-matched ROS packages and Ubuntu repository setup
- Middleware implementation; Humble documentation defaults to Fast DDS
Installation & first result
Open the upstream getting-started guide [6] · Project documentation [1] [5]
- Match the target robot or tutorial to a ROS distribution and host platform
- Follow the full Humble repository and system-update prerequisites
- Install desktop for the documented demo route
- Source the environment in both terminals and run the talker/listener examples
- Check each added driver or algorithm package for distribution support
Editorial starting sequence; no installation or hardware integration performed.
- Installation
Use the Humble Ubuntu 22.04 deb instructions, choose desktop or ros-base, and source the setup file for the current shell in each terminal.
Editorial scoped installation route; not executed.
[6] · Editorial assessment
Hardware, models & data
Project notes
The repository is a map of the software
The ros2/ros2 repository contains a ros2.repos manifest naming separate repositories and their selected versions. Preserving this archive preserves that map; it does not preserve every component's source, binary or dependency. A reproducible source build needs the referenced repositories as well. For users who want to begin with the framework, the documentation offers prebuilt packages rather than requiring a source build. [11] [12]
The Humble deb instructions target Ubuntu 22.04 on amd64 or arm64. The desktop installation includes RViz, demos and tutorials; ros-base provides communication libraries, messages and command-line tools without GUI tools. Follow the complete upstream locale, repository and system-update prerequisites before installing either. The guide specifically warns about updating systemd/udev-related packages on early Ubuntu 22.04 installations. These steps were inspected, not executed here. [6]
Use the demo to check communication, then add the robot
For the documented desktop route, source the Humble setup script in each terminal, using the extension for the current shell. The guide then runs demo_nodes_cpp talker in one terminal and demo_nodes_py listener in the other through ros2 run. Receiving the published messages checks that this example can communicate through the C++ and Python APIs. It does not establish that a motor driver, navigation system or physical robot is correctly configured. [6]
Nodes participate in a graph and can run in the same process, in separate processes or on different machines. They publish and subscribe to topics, provide services, accept actions and expose runtime parameters. Actions add feedback and cancellation or preemption for longer-running work, such as requesting travel to a waypoint; a short request can use a service instead. Choosing those interfaces is part of designing the application, rather than something the framework decides for the robot. [7] [8]
The Humble documentation names Fast DDS as the default middleware and describes alternatives through the RMW layer. Keep the selected middleware and package versions with the experiment's configuration. Before adding a driver or algorithm, use its package documentation and ROS Index entry to check supported distributions and dependencies. ROS ecosystem membership alone does not establish that two packages work together in the selected release. [5] [6]
What we checked
Source research only; no installation, physical build or performance test performed. No affiliate links added.
Not yet established
- Requirements: host computer
- Version-specific hardware compatibility (ecosystem tags alone do not establish it)
Updates
Source files and licenses
Documented open robotics framework; release manifest and documentation preserved, component-level source and license review remains configuration-specific.
| Layer | Availability / license |
|---|---|
| software | available · License not fully assessed Multi-repository manifest. Developer policy expects package LICENSE files, typically Apache-2.0, with existing permissive exceptions such as BSD-3-Clause. No single distribution-wide license assigned and component archives not all preserved here. [9] [12] |
| documentation | available · CC-BY-4.0 License of the separately preserved Humble documentation repository. [5] [10] |
Framework profile selects no learned weights or dataset.
Licensing follows the packages
The ROS 2 developer guide requires package license files, typically Apache-2.0, while allowing existing permissive licenses such as RViz's three-clause BSD. That is a package policy, not one license covering an entire robot stack. Inspect the actual selected components and dependencies before redistributing them. The separately preserved documentation repository has a CC-BY-4.0 license. [9] [10]
This profile establishes a documented starting route and the scope of the saved release manifest. No ROS installation, network test, robot-driver integration or control-system validation was performed.
References
Each source links to the exact revision we read. “Used for” shows where this page relies on it.
- S001 ros2/ros2: README.md
Revision, date & where cited
github.com · revision
7fdc394· Accessed Oct 1, 2026
Used for: Installation & first result - S002 ros2/ros2: commit 7fdc394
- S004 ros2/ros2: files
Revision, date & where cited
github.com · revision
7fdc394· archive file inventory · Accessed Oct 1, 2026 - S005 ROS 2 Humble documentation: source/index.rst
Revision, date & where cited
github.com · revision
35b00f1· Accessed Oct 1, 2026
Used for: Overview, Is this for you?, Installation & first result, Use the demo to check communication, then add the robot and 1 more - S006 ROS 2 Humble documentation: source/Installation/Ubuntu-Install-Debs.rst
Revision, date & where cited
github.com · revision
35b00f1· Accessed Oct 1, 2026
Used for: Is this for you?, What you need, Installation & first result, Hardware, models & data and 2 more - S007 ROS 2 Humble documentation: source/Concepts/Basic/About-Nodes.rst
Revision, date & where cited
github.com · revision
35b00f1· Accessed Oct 1, 2026
Used for: Is this for you?, Hardware, models & data, Use the demo to check communication, then add the robot - S008 ROS 2 Humble documentation: source/Concepts/Basic/About-Actions.rst
Revision, date & where cited
github.com · revision
35b00f1· Accessed Oct 1, 2026
Used for: Is this for you?, Hardware, models & data, Use the demo to check communication, then add the robot - S009 ROS 2 Humble documentation: source/The-ROS2-Project/Contributing/Developer-Guide.rst
Revision, date & where cited
github.com · revision
35b00f1· Accessed Oct 1, 2026
Used for: Is this for you?, Source files and licenses - S010 ROS 2 Humble documentation: LICENSE
Revision, date & where cited
github.com · revision
35b00f1· Accessed Oct 1, 2026
Used for: Source files and licenses - S011 ROS 2 Humble documentation: source/Installation.rst
Revision, date & where cited
github.com · revision
35b00f1· Accessed Oct 1, 2026
Used for: The repository is a map of the software - S012 Humble source repository manifest
Revision, date & where cited
github.com · revision
7fdc394· Accessed Oct 1, 2026
Used for: Overview, Is this for you?, The repository is a map of the software, Source files and licenses
Correction guidance · Discussion is not enabled · Profile format 0.6.0-draft.1