Robot Operating System 2 (ROS 2): Core Concepts, Architecture, and Real-World Capabilities

The Robot Operating System 2 (ROS 2) is an open-source, middleware framework that addresses the communication and coordination challenges inherent in modern, distributed robotic systems. In this article, Pedro details how ROS 2's architectural foundations successfully address the core limitations of its predecessor, ROS 1, using real-world scenarios, and steps for setting up the ROS 2 Foxy environment on Ubuntu Linux distro, and cross-platform communication between a host PC and a Raspberry Pi module.

- By Pedro Bertoleti

The robotics field is getting more and more collective. It is rapidly moving from monolithic, single-unit systems to highly distributed, heterogeneous, and networked configurations. Modern robots, particularly those designed for complex environments such as industrial floors, public roads, or domestic usage, are seldom single entities. Instead, they function as a tightly integrated collection of specialized, communicating modules: sensors, actuators, control systems, and decision-making algorithms, often distributed across multiple microprocessors, single-board computers (SBCs), and even external computational resources.

This paradigm shift necessitates a powerful, flexible, and utterly reliable communication framework to manage the complexity of data flow, synchronization, and inter-process communication (IPC) within the robot, itself, in addition to network communication with other robots or remote control systems over the network. To fulfill these requirements, ROS 2 comes as the state-of-the-art, robust, and a reliable communication solution for robots.

ROS 2 was designed to support modern industrial requirements, including multi-robot coordination—which means two or more robots working together to achieve a common goal.

This article serves as an in-depth technical review of the ROS 2 framework [1]. I will discuss its core components, analyze its sophisticated decentralized architecture, and illustrate its capabilities in creating distributed systems where reliability and performance are paramount. The focus will be on the widely adopted Foxy “flavor,” demonstrating its usage on an Ubuntu Linux distro, including a practical example. (Note: In this context, a “flavor” is the specific installation option or package set you choose. It determines which components and tools are included in your setup, and defines the scope of the installed software.)

WHAT'S ROS 2?