TL;DR:

  • EtherCAT (Ethernet for Control Automation Technology) is a real-time industrial Ethernet protocol developed by Beckhoff, now managed by the EtherCAT Technology Group as an open standard (IEC 61158)
  • It achieves cycle times under 100 microseconds by processing Ethernet frames on the fly at each node rather than buffering and forwarding them
  • Used extensively in servo drives, motion controllers, robotics, and high-precision CNC systems where hard real-time communication is required

Standard Ethernet wasn’t designed for industrial control. The TCP/IP stack introduces variable latency, collisions require retransmission, and there’s no guaranteed worst-case delivery time. For sending data between a PC and a printer or a web server, this is fine. For coordinating 16 servo axes in a CNC machine at microsecond precision, it isn’t.

EtherCAT solves this by treating the Ethernet frame differently. Rather than each node receiving a frame, processing it, and sending it on, EtherCAT nodes process frames on the fly — reading their data and inserting their response as the frame passes through, without buffering the entire frame first. The frame makes one loop around the network and returns to the master with all node data included.

How EtherCAT Works

An EtherCAT network has a master — typically an industrial PC running TwinCAT, CODESYS, or similar automation software — and up to 65,535 slaves connected in a line or ring topology using standard Cat5e or Cat6 cable with RJ45 connectors.

When the master sends a frame, it contains data addressed to each slave. Each slave reads its incoming data, performs its action (updates encoder feedback, accepts a velocity setpoint, reads a sensor), and inserts its response data into the same frame as it passes through. The frame arrives back at the master roughly 300 nanoseconds per node later — at 100Mbps Ethernet speed, this is the propagation delay through the hardware.

This “processing on the fly” architecture is what makes EtherCAT fast. A network with 100 slaves achieves a cycle time of around 100 microseconds for a 100-byte frame — approximately 10,000 synchronised update cycles per second. Compare this to PROFIBUS at 12Mbps with cycle times in the low milliseconds, or even PROFINET IRT (which achieves 250 microseconds with careful configuration).

Distributed Clocks

Sub-microsecond synchronisation between nodes is handled by EtherCAT’s distributed clock mechanism. The master broadcasts a reference time, and each slave adjusts its local clock to match, accounting for the propagation delay from master to each slave. Slaves can then trigger actions (an encoder latch, a digital output, an ADC sample) at exactly the right moment in the network cycle, synchronised to within 100 nanoseconds across the entire network.

This level of synchronisation is what allows multi-axis motion control — a six-axis robot arm, a five-axis machining centre — where multiple drives need to execute coordinated moves that are tight in time as well as space.

Physical Layer

EtherCAT runs on standard Ethernet hardware. You don’t need specialised cables or switches — standard Cat5e patch cables and standard RJ45 connectors work fine. What you do need is EtherCAT-capable interface hardware on the master (a standard Ethernet NIC running a real-time OS, or a dedicated EtherCAT master card) and EtherCAT slave controllers on each device.

The slave controller is the key hardware component — it’s a dedicated chip that implements the on-the-fly frame processing. Beckhoff’s ET1100 and similar chips are widely used. Many servo drive and I/O module manufacturers integrate EtherCAT slave controllers directly into their products.

The network topology is flexible. EtherCAT supports line, ring, tree, and star topologies using standard Ethernet switches at junction points. Ring topology provides redundancy — if the ring is broken, traffic routes the other way.

EtherCAT in Robotics and CNC

EtherCAT has become the dominant choice for:

Servo systems: Delta, Kollmorgen, Beckhoff, Schneider Electric, Yaskawa, and most other servo drive manufacturers offer EtherCAT interfaces. The fast cycle time means tight torque, velocity, and position loops that allow responsive and precise control.

CNC machining: Beckhoff’s TwinCAT with EtherCAT is widely deployed in CNC controllers. FANUC and Mitsubishi Electric have their own proprietary protocols (FSSB and SSCNET III respectively), but EtherCAT is the open-standard alternative with comparable performance.

Industrial robots: Many collaborative robot manufacturers have adopted EtherCAT for internal axis communication. KUKA’s KRC5 controllers use EtherCAT internally. Universal Robots exposes EtherCAT for integration with external systems.

Machine vision synchronisation: A camera trigger, a strobe light, and a conveyor encoder can all be synchronised via EtherCAT distributed clocks, ensuring the camera fires at exactly the right conveyor position for repeatable inspection.

When to Choose EtherCAT vs Alternatives

EtherCAT is the right choice when:

  • You need cycle times below 1 millisecond
  • You’re coordinating multiple axes or synchronised I/O
  • You want a standard protocol with broad device support
  • You’re building new equipment and can specify the protocol from scratch

PROFINET IRT achieves similar performance but is more common in Siemens-centric environments. EtherNet/IP is a strong alternative for Rockwell Automation systems and US manufacturing environments but doesn’t achieve EtherCAT’s cycle times. Sercos III targets similar motion control applications and has a strong installed base in grinding and injection moulding.

For systems that don’t need sub-millisecond performance — general I/O monitoring, condition monitoring, data aggregation — EtherCAT is overkill and standard PROFINET, EtherNet/IP, or Modbus TCP will do the job more simply.

EtherCAT Technology Group and Conformance

The EtherCAT Technology Group (ETG) manages the standard, certification, and device conformance testing. Over 7,000 member companies and thousands of certified devices make EtherCAT one of the better-supported industrial protocols. Conformance testing through an ETG-approved test lab is required for EtherCAT logo certification, which gives you reasonable confidence that certified devices from different manufacturers will interoperate.

The standard is published as IEC 61158 (fieldbus standard, type 12) and IEC 61784 (communication profile families), which is relevant for machinery directive compliance in European markets.

If you’re specifying a new motion control system and performance matters, EtherCAT deserves to be at the top of your shortlist.