ROS2 DDS (Data Distribution Service)
The communication backbone that powers modern AGV fleets. DDS replaces the centralized master of legacy systems with a decentralized, real-time data bus capable of handling the rigorous demands of industrial automation and mobile robotics.
_hero.png)
Core Concepts
Decentralization
Unlike ROS1, there is no master node. Every robot and sensor acts as an independent node, eliminating single points of failure in your AGV fleet.
Real-Time QoS
Quality of Service (QoS) policies allow you to tune communication for reliability (TCP-like) or speed (UDP-like) depending on navigation needs.
Discovery
Nodes automatically discover each other on the network using multicast. Add a new AGV to the warehouse floor, and it instantly syncs with the fleet manager.
Security (DDS-Security)
Native support for authentication, access control, and encryption ensures that your industrial robot data remains safe from unauthorized access.
Interoperability
DDS is a standard managed by OMG. This means different hardware vendors and middleware implementations can communicate seamlessly.
Data-Centricity
The network cares about the data, not the nodes. Components subscribe to topics like "LidarScan" without needing to know which sensor produced it.
How ROS2 DDS Works
At the heart of ROS2 is the abstract middleware interface (rmw). This layer allows ROS2 to sit on top of various DDS implementations like eProsima Fast DDS, Eclipse Cyclone DDS, or RTI Connext without changing your application code.
In a typical AGV scenario, the DDS layer handles the complex serialization of messages. When your navigation stack publishes a velocity command, DDS ensures it reaches the motor controllers within a guaranteed timeframe, using the UDP transport protocol for efficiency.
Crucially, for processes running on the same onboard computer, many DDS implementations utilize "Shared Memory" (Zero-Copy). This bypasses the network stack entirely, allowing massive data streams—like raw 4K camera feeds—to be processed with near-zero latency and minimal CPU overhead.
_diagram.png)
Real-World Applications
High-Density Warehousing
In environments with hundreds of AGVs, DDS traffic isolation ensures that fleet management commands take priority over diagnostic logging, preventing network congestion.
Outdoor Agriculture AMRs
Using DDS "Best Effort" QoS, agricultural robots can continue operating on lossy, long-range Wi-Fi networks where occasional packet loss is expected and acceptable.
Swarm Robotics
Because DDS is decentralized, a swarm of robots can dynamically form a mesh network, sharing map data and coordinate tasks without a central server.
Hospital Logistics
DDS Security plugins are essential here, ensuring that robots delivering sensitive medical supplies cannot be hijacked or monitored by unauthorized devices.
Frequently Asked Questions
What is the main advantage of DDS over ROS1's TCPROS?
The primary advantage is the removal of the single point of failure (the ROS Master). Additionally, DDS uses UDP by default which is faster and supports multicast, whereas TCPROS is connection-oriented and can struggle with intermittent connectivity typical in mobile robotics.
Which DDS implementation works best for AGVs?
It depends on the hardware. Eclipse Cyclone DDS is often favored for its low CPU usage and ease of configuration out of the box. eProsima Fast DDS provides extensive configuration options for complex networks. Both are excellent choices for modern AGVs.
Why can't my robots see each other on the Wi-Fi network?
This is usually a Multicast issue. DDS relies on UDP Multicast for discovery. Many industrial Wi-Fi routers block multicast traffic to save bandwidth. You may need to enable IGMP snooping on your router or configure a Discovery Server.
What is a ROS2 Discovery Server?
A Discovery Server is a centralized registry used in scenarios where multicast is not available (like over the internet or restrictive Wi-Fi). Nodes query the server to find peers instead of broadcasting to the whole network.
How does QoS "Reliability" impact latency?
Setting QoS to "Reliable" guarantees message delivery by acknowledging receipt and retransmitting lost packets. This increases network traffic and latency compared to "Best Effort," which sends data 'fire-and-forget' style.
Can I mix different DDS vendors in one fleet?
Yes, because they all adhere to the OMG DDS standard, they are interoperable on the wire. However, mixing vendors can sometimes lead to minor performance quirks regarding discovery times or QoS interpretation, so sticking to one vendor per fleet is best practice.
What is "Zero-Copy" transport?
Zero-Copy allows nodes on the same computer to exchange messages by passing pointers to shared memory locations rather than copying the data itself. This is critical for high-bandwidth sensors like LiDARs and cameras to prevent CPU saturation.
How do I secure my ROS2 DDS traffic?
You can use SROS2 (Secure ROS2), which leverages the DDS-Security spec. It involves generating certificates and keys for each node, enabling encryption, authentication, and access control policies.
Does DDS introduce significant CPU overhead?
DDS is heavier than raw TCP sockets due to the serialization and discovery mechanics. However, on modern embedded processors (like Jetson or Raspberry Pi 4), the overhead is negligible for typical AGV workloads, especially when tuned correctly.
What is the ROS_DOMAIN_ID?
The `ROS_DOMAIN_ID` is an environment variable (integer 0-101) that isolates ROS2 networks. Robots on ID 0 cannot communicate with robots on ID 1. This is essential for running multiple simulations or separating production fleets on the same physical network.
How do I debug DDS connection issues?
Tools like `ros2 doctor` provide initial health checks. For deeper analysis, Wireshark works well (with RTPS dissectors), or vendor-specific tools like the Fast DDS Monitor allow you to visualize the discovery graph and traffic flow.