EtherCAT Real-time Ethernet
EtherCAT allows Autonomous Guided Vehicles (AGVs) to achieve microsecond-level synchronization between motion controllers, safety sensors, and navigation systems. It is the industrial standard for determinism, speed, and reduced cabling complexity in mobile robotics.
Core Concepts
Processing on the Fly
Unlike standard Ethernet, EtherCAT frames are processed by slave devices as they pass through. Data is read and written instantaneously, virtually eliminating communication delays.
Distributed Clocks
A precise synchronization mechanism ensures all axes on a robot move in perfect harmony. Jitter is reduced to less than 1 µs, essential for mecanum drive kinematics.
Flexible Topology
EtherCAT supports line, tree, and star topologies without managed switches. This allows for daisy-chaining devices inside tight AGV chassis, saving weight and space.
Safety over EtherCAT (FSoE)
Safety data (E-Stop, LiDAR fields) is transmitted over the same standard Ethernet cable as control data, reducing wiring harness complexity significantly.
High Bandwidth Efficiency
EtherCAT utilizes over 90% of the available bandwidth. A single frame can update inputs and outputs for hundreds of devices, keeping bus cycle times extremely low.
Cost Efficiency
Master devices require only a standard Ethernet port (no special card). Standard CAT5e cables are used, and no expensive switches are required between nodes.
How It Works: The "Train" Analogy
Imagine a high-speed train (the Ethernet frame) that doesn't stop at stations. Instead, passengers (data) jump on and off while the train is moving at full speed. This is the fundamental principle of EtherCAT's "Processing on the Fly."
In a typical mobile robot architecture, the Industrial PC (Master) sends a single frame. This frame travels through the motor drivers, the I/O modules, and the safety scanners (Slaves). Each device reads the command addressed to it and inserts its feedback data (like motor encoder position or battery voltage) into the same frame.
The frame returns to the Master with a complete snapshot of the robot's state. This cycle happens thousands of times per second (often 1kHz to 8kHz), allowing the robot to react instantly to dynamic environments, such as a person stepping into its path.
- Single frame for all devices
- Full duplex communication
- Deterministic timing
Real-World Applications
Precision Docking & Charging
AGVs require millimeter-level accuracy to connect with charging contacts or conveyor belts. EtherCAT's high-speed feedback loop allows the navigation controller to make micro-adjustments to the wheel motors instantly, ensuring perfect alignment every time.
Holonomic Motion Control
For Mecanum or Swerve drive robots, four or more motors must coordinate perfectly to move diagonally or rotate in place. Distributed Clocks ensure every motor receives its velocity command at the exact same microsecond, preventing wheel slippage and path deviation.
Integrated Safety Zones
Using Safety over EtherCAT (FSoE), safety laser scanners communicate directly with the safety PLC and motor drives over the standard bus. If an obstacle is detected, the system can trigger Safe Torque Off (STO) immediately without needing separate hardwiring for every sensor.
Mobile Manipulation
For AMRs equipped with robotic arms, EtherCAT synchronizes the mobile base with the arm's controller. This allows for continuous motion where the base compensates for the arm's movement, expanding the workspace and increasing cycle efficiency.
Frequently Asked Questions
What distinguishes EtherCAT from standard TCP/IP Ethernet?
Standard TCP/IP is non-deterministic, meaning data packet arrival times can vary, which is acceptable for internet browsing but dangerous for robot control. EtherCAT uses the same physical cables but a different protocol that guarantees data arrival within microseconds, ensuring hard real-time control.
Does EtherCAT require special cables or switches?
No. You can use standard CAT5e or CAT6 Ethernet cables. Furthermore, EtherCAT does not use standard network switches; devices are daisy-chained (connected one to the next), which actually simplifies the BOM and reduces hardware costs for AGV manufacturers.
What is Safety over EtherCAT (FSoE) and why use it?
FSoE is a certified safety protocol that runs on the same wire as standard control data (Black Channel principle). It allows you to achieve safety levels up to SIL 3 / PLe without running separate yellow safety cables to every E-stop and scanner, saving significant weight and space inside mobile robots.
How does EtherCAT handle network topology changes?
EtherCAT supports Hot Connect, which allows sections of the network to be connected or disconnected during operation. This is useful for modular robots or AGVs that might attach to different tools or trailers with their own I/O modules dynamically.
Can I use EtherCAT with ROS or ROS 2?
Yes, there are several open-source and commercial EtherCAT masters available for Linux that integrate with ROS/ROS 2 (such as SOEM or the EtherLab master). This allows high-level navigation stacks to communicate directly with real-time hardware drivers.
What is the maximum cable length between nodes?
Like standard Ethernet, the distance between two EtherCAT nodes can be up to 100 meters (328 ft) using copper cable. For AGVs, distances are usually very short, but this range is useful for communication between the AGV and fixed infrastructure if using optical links.
What happens if a cable breaks or a device fails?
EtherCAT supports cable redundancy. By connecting the last node back to a second port on the master, a ring topology is created. If a cable breaks, the traffic is instantly rerouted, ensuring the robot can continue to operate or safely shut down.
Is EtherCAT suitable for battery-powered devices?
Yes. EtherCAT slave controllers are implemented in hardware (ASICs or FPGAs) and are generally very power efficient compared to main processors handling complex TCP/IP stacks. This helps conserve the AGV's overall battery life.
How many devices can be connected to one Master?
Ideally, EtherCAT supports up to 65,535 nodes in a single network segment. In a practical AGV scenario, you will never hit this limit, allowing you to add as many sensors, drives, and I/O slices as the chassis can physically hold.
What is the typical cycle time for an AGV application?
For mobile robotics, typical cycle times range from 1ms (1kHz) to 4ms (250Hz). This is sufficient for smooth motion control and navigation. High-performance manipulator arms on top of AGVs might run faster, around 250µs (4kHz).
Do I need a specific hardware card for the Master?
No. One of EtherCAT's biggest advantages is that the Master functionality is purely software-based and works with any standard Ethernet controller found on industrial PCs (like those from Intel or Realtek). Only the Slaves require specific EtherCAT chips.
Ready to implement EtherCAT Real-time Ethernet in your fleet?
Take your AGV performance to the next level with our compliant hardware solutions.
Explore Our Robots