Using FANUC EGD for High-Speed Robot-to-Robot Communication
FANUC’s Ethernet Global Data (EGD) protocol enables fast, deterministic robot-to-robot communication in modern manufacturing cells. This article explains configuration, networking, and I/O mapping ...
Fast Data Exchange Becomes Critical in Multi-Robot Cells
Modern manufacturing cells demand tight coordination between robots operating in shared spaces. FANUC’s Ethernet Global Data (EGD) protocol addresses this need with deterministic, high-speed communication designed specifically for controller-level data exchange.
Unlike general-purpose Ethernet protocols, EGD focuses on predictable timing and low overhead. This makes it particularly effective for synchronized motion, collision avoidance, and distributed task execution across robotic systems.
Why Robot-to-Robot Communication Matters
In complex automation environments, robots rarely operate in isolation. They share tooling zones, pass workpieces, and execute sequential processes that depend on real-time feedback.
EGD enables direct data sharing between controllers without relying on higher-level systems. This reduces latency and simplifies architecture compared to PLC-mediated communication.
Figure 1. FANUC robots exchange data using EGD in a coordinated training setup, demonstrating real-time synchronization capabilities.
Understanding the Communication Architecture
Producer–Consumer Model
EGD uses a producer-consumer structure. One robot publishes data, while others subscribe to receive it. This model supports one-to-many communication without additional configuration complexity.
Each data exchange includes a defined size, update interval, and identifier. These parameters ensure consistent communication timing across all connected devices.
UDP-Based Deterministic Messaging
EGD operates over UDP, prioritizing speed over retransmission reliability. In controlled industrial networks, this tradeoff delivers predictable performance essential for motion coordination.
This design avoids delays caused by packet acknowledgment, making EGD suitable for time-sensitive automation tasks.
Physical Network Setup and Constraints
EGD runs on standard Ethernet infrastructure. Two robots can connect directly, while larger systems require an industrial Ethernet switch.
Shielded cables help maintain signal integrity in electrically noisy environments. Network isolation remains critical, as EGD traffic is not intended for enterprise-level routing.
Figure 2. Controller Ethernet ports must be correctly identified to ensure proper network configuration and communication mapping.
IP Configuration and Network Alignment
Each robot must operate within the same subnet while maintaining unique IP addresses. Configuration is handled through the teach pendant interface.
Correct port selection is essential. Misaligned port assignments often cause communication failures, even when IP settings appear valid.
Figure 3. Network parameters must align across all robots to establish reliable EGD communication.
Configuring Data Exchange Between Robots
Producer Setup
The producer defines the destination IP, data size, and transmission interval. Typical update rates range around 100 ms, balancing responsiveness and network load.
Exchange IDs link producers and consumers. These identifiers must match exactly to establish communication channels.
Figure 4. Producer configuration defines how and when data is transmitted across the network.
Consumer Setup
The consumer listens for incoming data using the same exchange ID. Timeout parameters ensure fault detection when communication is interrupted.
This mechanism provides a simple but effective way to monitor communication health without additional diagnostics layers.
Figure 5. Consumer configuration validates incoming data and ensures synchronization with the producer.
Mapping Data to Rack 88
FANUC assigns EGD communication to Rack 88 within its I/O system. Engineers map internal registers to this rack to exchange signals between robots.
Accurate mapping ensures that transmitted data aligns correctly with receiving inputs. Even minor mismatches can cause logic errors in coordinated operations.
Figure 6. Proper I/O mapping ensures consistent data interpretation between producer and consumer robots.
Application in Real Manufacturing Environments
EGD excels in applications where robots must coordinate without centralized control. Automotive assembly, palletizing lines, and welding cells all benefit from direct controller communication.
In many cases, engineers combine EGD with higher-level systems such as PLC/PAC platforms to manage supervisory logic while preserving real-time robot coordination.
Industry Perspective: A Shift Toward Distributed Control
The adoption of protocols like EGD reflects a broader trend toward distributed intelligence in automation systems. Instead of relying solely on centralized PLCs, controllers increasingly communicate directly.
This evolution aligns with the growth of industrial Ethernet technologies and specialized communication networking solutions that prioritize determinism and scalability.
Author’s View
EGD stands out not because it replaces other protocols, but because it simplifies a specific problem: fast, predictable robot-to-robot communication. Engineers who understand its limitations can deploy it effectively without overengineering the system.
In practice, the best architectures combine EGD for real-time exchange and PLC or DCS layers for supervision. This hybrid approach delivers both speed and system-wide visibility.
Daniel Reeves, Senior Industrial Systems Reporter. With 14 years of experience in FANUC robotics integration and Siemens industrial networking, he specializes in high-speed automation architectures and real-time communication systems.