ROS 2

What it means

ROS 2 is a robotics software framework for building communicating components. A node is a participant in its graph and typically performs one logical function. Nodes can publish or subscribe to topics, offer or request services, and use actions for long-running work. The official documentation describes communication within a process, across processes or between machines. [1]

Despite its name, ROS 2 should be understood through those software roles rather than assumed to replace the computer's general-purpose operating system. A robot project still has to implement its sensing, planning and control components and connect them appropriately. [1]

How it applies to humanoids

A humanoid project can separate camera processing, joint-state handling, task requests and other functions into components that communicate through this framework. ROS 2's node model provides the interfaces; the implementation determines what each component actually does. A robot using ROS 2 therefore has a development architecture, not a complete capability description. [1]

Reachy 2 provides a documented product example. Pollen's page states that it runs ROS 2 Humble and offers a Python SDK and VR teleoperation. These are separate interface descriptions, and the robot record cites the product page for this development environment. [4]

Terminology and timing traps

Message delivery requires suitable quality-of-service settings. ROS 2's Jazzy documentation distinguishes best-effort and reliable delivery, as well as history and durability choices. Publisher and subscription profiles must be compatible to establish a connection. Selecting reliability is a communication decision; it does not prove that a complete humanoid application meets every timing requirement. [2]

Real-time means correct computation within a deadline, not merely a high average frame rate. The ROS 2 real-time background article distinguishes hard, soft and firm deadlines. It also discusses why system behavior and software design matter when building time-sensitive applications. [3]

A ROS 2 label does not identify one fixed product stack. Pollen specifies Humble for Reachy 2, while the cited node documentation is from Jazzy. These references explain concepts, but users should follow their robot's supported distribution and packages rather than assume all instructions are interchangeable. [1, 4]

How to read it on humanoidversus.com

Read compute and developer documentation for the disclosed environment. The public-SDK flag and open-source hub identify access described in the record; they do not establish that every component, firmware layer or hardware design has an open license.

Reachy 2 is linked because its official source names ROS 2 explicitly. This entry has no live table: named ai_stack values are not a ROS 2 adoption ranking. Check the robot's SDK, supported distribution and actual control interfaces before attributing a software feature to its whole system. [4]

Further reading

The ROS 2 node documentation explains component communication. Its quality-of-service and real-time design articles explain delivery and timing assumptions. Pollen's Reachy 2 page shows a manufacturer-specific deployment of these developer interfaces. [1–4]