Robots Atlas>ROBOTS ATLAS

ROS / ROS 2 · Middleware

ROS 2 Lyrical Luth

Lyrical Luth Initial Release·Open Robotics

Active Open source Real-time capable API available
CATEGORYROS / ROS 2 · Middleware
READINESSTRL 9
ADOPTION SCALEGrowing Community
LICENSESApache-2.0
FIRST RELEASE2026

**ROS 2 Lyrical Luth** is the twelfth ROS 2 distribution and another Long Term Support (LTS) release. It was published on May 22, 2026 by Open Robotics with a 5-year support cycle until May 2031, making Lyrical a primary ROS 2 production platform alongside Jazzy Jalisco.

**Base platform**: Ubuntu 26.04 LTS 'Resolute Raccoon' (Tier 1, amd64 and arm64). Additionally supported: RHEL 10 (amd64) and Windows 11 (built with Visual Studio Build Tools 2022, amd64). The default middleware (RMW) is eProsima Fast DDS; alternatives include Eclipse Cyclone DDS, RTI Connext DDS, GurumNetworks GurumDDS, and the Zenoh-based rmw_zenoh (non-DDS).

**Key new features**: (1) Callback Group Events executor — a new executor reducing CPU usage by ~10–15% compared to single- and multi-threaded executors. (2) AsyncNode (rclpy) — native asyncio integration with ROS callbacks and timers. (3) rosidl::Buffer — zero-copy data publishing, e.g. directly from GPU memory. (4) URDF 1.2 — support for quaternions, capsule geometry, and acceleration/deceleration limits. (5) rosbag2 — remote recording control, programmatic Python APIs, circular recording with file limits, and message-loss observability. (6) Native fish shell support via setup.fish and expanded ros2 param/service/topic commands.

**Lifecycle**: initial release May 22, 2026, planned end of life (EOL) in May 2031 (5 years, per the ROS 2 LTS policy for even years). Lyrical Luth is the twelfth ROS 2 release (after Kilted Kaiju from 2025) and the first LTS based on Ubuntu 26.04.

**Standards and distribution**: code in C++17 and Python 3 (the version shipped with Ubuntu 26.04). ROS 2 is fully open source under the Apache 2.0 license, with packages distributed via apt (Debians), Docker images, RPM (RHEL 10), a Windows installer, and building from source (colcon).

Type & Roles
Software types
Middleware

Middleware is a software layer that mediates between applications, services, sensors, drivers, and execution layers. In robotics, middleware is typically responsible for inter-process communication, message passing, hardware abstraction, and module integration within a single system. The most widely used robotics middleware is ROS (Robot Operating System), which provides a publish-subscribe message bus, service calls, and a rich ecosystem of packages.

Runtime

A Runtime is the environment or execution layer used to run code, load libraries, manage dependencies, and operate applications or services — either in real time or during normal system operation. In robotics this includes real-time operating system (RTOS) runtimes, ROS 2 executor runtimes, containerised execution environments (Docker, podman), and embedded C++ runtimes on microcontrollers.

SDK

An SDK (Software Development Kit) is a curated set of libraries, interfaces, tools, sample code, and documentation intended for building applications and integrating with a specific hardware device, platform, or service. In robotics, an SDK typically exposes device control, telemetry, sensor access, configuration, and execution functions, significantly reducing the time-to-first-integration for developers targeting a specific robot or platform.

API Library

An API Library is a software package that exposes programmatic interfaces for communicating with a device, service, or system. In robotics it typically forms a lightweight integration layer built on top of the manufacturer's official API or an open-source project, abstracting low-level protocol details and providing language-native bindings (Python, C++, Java, etc.).

Developer Tool

A Developer Tool is software designed to support the development workflow, including configuration, debugging, testing, monitoring, validation, and integration of robotic and embedded systems. Examples include IDE plugins, visual debuggers, log analysers, hardware-in-the-loop (HIL) test harnesses, and code-generation utilities specific to robotics platforms.

Select an item to see its description.
Main category
MiddlewareRuntime & InfrastructureSDKsDeveloper Tools
Roles in robotics ecosystem
PerceptionDeveloper EnablementAPI AccessVisualizationMotion PlanningDiagnostics & Monitoring
Robot Control

Robot Control denotes the role of software responsible for motion control, command execution, coordination of actuating elements and the direct operational logic of the robot.

Select an item to see its description.
Software family
Family
ROS 2 Ecosystem
Maturity & Adoption
9 / 9
Proven in operational conditions
ResearchPrototypeProduction
Adoption scaleGrowing Community
Maintenance statusActively Maintained – LTS
First release2026
Last update22 September 2026
Integrates with
R2
ROS 2
Open-source framework for building robot software. The successor to ROS 1, built on DDS with native support for distributed, real-time and multi-platform systems. The de facto standard in research and commercial robotics.
→
GH
Gazebo Harmonic (gz-sim)
An LTS release of the new-generation Gazebo (gz-sim), released in September 2023 — the successor to Gazebo Classic. Modular architecture, integrated with ROS 2 Humble/Iron/Jazzy, supported until September 2028.
→
M2
MoveIt 2
Open-source motion planning, manipulation, and kinematics framework for ROS 2 (Foxy → Jazzy). Stewarded by PickNik Robotics. The de facto standard for manipulators in the ROS ecosystem.
→
NI
NVIDIA Isaac ROS
NVIDIA Isaac ROS — collection of GPU-accelerated GEM packages for ROS 2: stereo depth, AprilTags, pose estimation, cuVSLAM, object detection on Jetson and x86 CUDA. Foundation of the NVIDIA robot perception stack.
→
EF
eProsima Fast DDS
eProsima's implementation of the OMG DDS standard — the default communication layer in ROS 2 since the Foxy distribution. High performance, deterministic QoS, DDS-XRCE support for microcontrollers (Micro XRCE-DDS).
→
M
micro-ROS
A ROS 2 port for microcontrollers (Cortex-M, ESP32, RISC-V). Lets nodes running on MCUs talk to the rest of the ROS 2 graph via a Micro XRCE-DDS agent — a DDS protocol optimized for embedded.
→
C
colcon
colcon (collective construction) — the official meta-build tool for ROS 2 and beyond, the successor to catkin_make and ament_tools. Builds multi-package CMake/Python workspaces with dependency resolution.
→
R
rosdep
rosdep — the official ROS / ROS 2 tool for resolving external system dependencies (apt, brew, yum, pip) via the `rosdep/base.yaml` map. Standard since ROS Hydro (2013).
→
B
bloom
bloom — the ROS release / packaging tool, generates .deb and RPM packages from `package.xml` and ships them to the ROS buildfarm. Essential for every package maintainer in ros/rosdistro.
→
Target robotic platforms
Humanoid
Quadruped
Mobile Robot
Robotic Arm
Industrial Robot
Service Robot
Research Robot
Drone / UAV
ROS supportCompatibility with ROS / ROS 2 ecosystem
Official ROS 2 PackagePakiet dostępny w oficjalnym rejestrze ROS 2 przez rosdep / apt (packages.ros.org)
System capabilities
⊙
Open source
Source code is publicly available under an open-source license — enables security audits, custom modifications, and integration without licensing barriers.
✓
⚡
Real-time capable
Designed with timing-determinism guarantees — meets the requirements of control loops, safety systems, and tasks demanding low, predictable latency.
✓
⟨/⟩
API available
The software exposes a programmable interface (REST, gRPC, SDK, or language bindings) that enables automation and integration with other systems.
✓
📦
Pre-built / binary
Distributed as ready-to-use binary packages, container images, or installers — no need to build from source.
✓
Programming languages
C++PythonC
Operating systems
Windows
Ubuntu 26.04

Ubuntu 26.04 LTS 'Resolute Raccoon' — released April 2026, 5-year standard support (until 2031, extended to 2036 with Ubuntu Pro). Tier 1 host platform for ROS 2 Lyrical Luth and ROS 2 Rolling.

Select an item to see its description.
Minimum hardware requirements
Minimum hardware requirements
CPUMinimum: 2-core x86-64 ≥ 2 GHz or ARMv8 64-bit (Cortex-A78, Apple M-series, Snapdragon 8 Gen 2+). Recommended: 4–8 cores ≥ 2.5 GHz for production systems.
RAM (GB)4
GPUNot required for core ROS 2. RViz2: dGPU or iGPU for smooth point-cloud rendering. GPU-accelerated nodes (Isaac ROS, CUDA perception): NVIDIA RTX 3060+ / Jetson Orin NX 16 GB+.
Disk (GB)20

Installation: `sudo apt install ros-lyrical-desktop` (Ubuntu 26.04) or Docker `osrf/ros:lyrical-desktop`. Full desktop ~15 GB; minimal ros-base ~2.5 GB. Requires Ubuntu 26.04 LTS (Tier 1) or Docker on other systems.

Packaging & distribution
Package managers
apt / debDocker / Docker HubSource – CMake / ament_cmakerosdep / bloomGitHub Releases / GitHub Actions Artifactsconda / mamba.rpm Package (RHEL/Fedora)EXE Installer (Windows)
CPU architectures
x86_64 (AMD64)ARM64 / AArch64NVIDIA Jetson – AArch64 (JetPack)Apple Silicon – AArch64 (macOS)Raspberry Pi – AArch64 (BCM)
Installation difficulty
LevelModerate
Protocols and interfaces
Communication protocols
DDS (Data Distribution Service)Fast DDS (eProsima)CycloneDDSZenohRTPS (Real-Time Publish-Subscribe)ROS 2 TopicsROS 2 ServicesROS 2 ActionsRosbridge (rosbridge_suite)Shared Memory (POSIX / mmap)
Hardware interfaces
Ethernet 1000BASE-T (Gigabit Ethernet)Ethernet 10GBASE-T (10 Gigabit Ethernet)Ethernet 2.5GBASE-TUSB 3.0 / 3.1 Gen 1PCIe 4.0PCIe 5.0CAN 2.0A / 2.0BCAN FD (Flexible Data-Rate)UART / RS-232EtherCAT (Slave Interface)
Latency classes
Hard Real-Time (1–5 ms)Hard Real-Time (5–20 ms)Soft Real-Time (20–100 ms)
Deployment types
Local WorkstationEdgeContainerizedOn RobotCloudHybrid
Supported simulators
NVIDIA Isaac Sim
NVIDIA Isaac Lab
Webots
MuJoCo
Gazebo Harmonic
Drake
Genesis (generative physics simulator)
PyBullet / Bullet3
Licenses
Apache-2.0Apache License 2.0v2.0

License family: Permissive

ModificationDistributionCommercial useSublicensingPrivate useROS-compatibleOSI approvedFSF Free/LibreRequires attributionPatent grant
Version history
Lyrical Luth Initial ReleaseMay 2026

First stable release — Ubuntu 26.04 baseline, default Fast DDS, new Callback Group Events executor (~10–15% less CPU), rclpy AsyncNode (asyncio), zero-copy rosidl::Buffer, URDF 1.2, expanded rosbag2, and fish shell support.