ROS 2 (Robot Operating System)

Overview

Open-source middleware framework for robotics built on a DDS-based publish/subscribe transport. Provides component lifecycle, parameters, services, actions, and a vast ecosystem of perception, navigation, and manipulation packages. micro-ROS extends the same component model down to MCUs running Zephyr, FreeRTOS, or NuttX, so a robot can run one consistent framework from sensor microcontroller to compute module.

Benefits

• Mature ecosystem of perception, planning, and simulation packages (Gazebo, RViz, MoveIt, Nav2)
• DDS transport is well-suited to real-time and distributed embedded systems
• Same component and message model spans MCU through workstation via micro-ROS
• Strong tooling for record-and-replay (rosbag2) and remote introspection

Limitations & Risks

• Steep learning curve, especially around DDS QoS and discovery
• Default DDS implementations are heavyweight for resource-constrained MCUs (use micro-ROS for those)
• Safety-certified ROS 2 distributions exist but are still maturing
• Cross-network DDS configuration in production is genuinely tricky

Recommended Actions

Pilot ROS 2 (Humble or later) for any project that combines perception, motion, or multi-component coordination. Prototype micro-ROS on a Zephyr-based MCU node to learn the cross-environment story. Standardize on a single DDS implementation per program (Cyclone DDS or Fast DDS) and tune QoS deliberately rather than running with defaults.

Additional Notes

ROS 2's middleware model pairs naturally with the Component-Based / Message-Driven Architecture practice (#9). micro-ROS gives ROS 2 real reach into MCU territory that ROS 1 never had.

References & Links

• https://docs.ros.org/
• https://micro.ros.org/
• https://www.ros.org/