Skip to main content

ROS 2: The Robotic Nervous System

Introduction to ROS 2​

Robot Operating System 2 (ROS 2) serves as the "nervous system" of modern robotic systems, providing the communication infrastructure that enables different components to work together seamlessly. Unlike its predecessor, ROS 2 is designed for production environments with improved security, real-time capabilities, and better architecture.

Architecture Overview​

DDS-Based Communication​

ROS 2 uses Data Distribution Service (DDS) as its underlying communication middleware, providing:

  • Decentralized communication: No central master node
  • Quality of Service (QoS) policies: Configurable reliability and performance
  • Language independence: Support for C++, Python, Rust, and more
  • Platform compatibility: Runs on various operating systems

Nodes and Processes​

In ROS 2:

  • Each process runs as a separate node
  • Nodes communicate through topics, services, and actions
  • No single point of failure as in ROS 1
  • Better process isolation and security

Core Communication Patterns​

Topics (Publish/Subscribe)​

  • Asynchronous, one-to-many communication
  • Used for streaming data like sensor readings
  • Example: Camera images, laser scans, joint states
import rclpy
from rclpy.node import Node
from sensor_msgs.msg import Image

class ImageSubscriber(Node):
    def __init__(self):
        super().__init__('image_subscriber')
        self.subscription = self.create_subscription(
            Image,
            'camera/image_raw',
            self.listener_callback,
            10)

    def listener_callback(self, msg):
        self.get_logger().info('Received image')

Services (Request/Response)​

  • Synchronous, one-to-one communication
  • Used for actions that return a result
  • Example: Navigation goals, calibration procedures

Actions (Goal/Feedback/Result)​

  • Asynchronous, long-running operations
  • Provides feedback during execution
  • Example: Navigation to goal, trajectory execution

Quality of Service (QoS) Settings​

ROS 2 provides configurable QoS policies:

  • Reliability: Best effort vs. reliable delivery
  • Durability: Volatile vs. transient local
  • History: Keep last N messages vs. all messages
  • Deadline: Maximum time between publications

Security Features​

ROS 2 includes built-in security:

  • Authentication: Verify node identity
  • Encryption: Protect message contents
  • Access control: Control who can communicate
  • Signing: Ensure message integrity

Real-Time Capabilities​

ROS 2 supports real-time systems:

  • Real-time scheduling: Configurable priority levels
  • Memory pre-allocation: Avoid dynamic allocation in critical paths
  • Deterministic communication: Predictable timing behavior
  • Lock-free data structures: Reduce contention

Migration from ROS 1​

Key differences from ROS 1:

  • No central master
  • Built-in security
  • Real-time support
  • Better cross-compilation
  • Improved testing infrastructure

Best Practices​

Node Design​

  • Keep nodes focused on single responsibilities
  • Use parameters for configuration
  • Implement proper cleanup
  • Follow naming conventions

Communication Design​

  • Choose appropriate QoS settings
  • Use appropriate message types
  • Consider bandwidth and latency
  • Implement proper error handling

Testing and Validation​

  • Unit test individual components
  • Integration test communication
  • Validate message schemas
  • Test under various network conditions

ROS 2 Ecosystem​

Core Packages​

  • rclpy/rclcpp: Client libraries
  • ros2cli: Command-line tools
  • rviz2: Visualization tool
  • rosbag2: Data recording/playback

Common Tools​

  • ros2 run: Execute nodes
  • ros2 topic: Monitor topics
  • ros2 service: Call services
  • ros2 param: Manage parameters

ROS 2 provides the foundational communication infrastructure that enables complex robotic systems to function as cohesive, integrated entities. Understanding its architecture and capabilities is essential for developing sophisticated robotic applications.