PROFINET RT, PROFINET IRT or EtherCAT for a machine with servo axes: how do they differ?

PROFINET RT uses standard Ethernet hardware. Cyclic I/O data is sent as layer 2 frames (EtherType 0x8892) that bypass the TCP/IP stack, with a VLAN priority tag so that switches forward them ahead of ordinary traffic. Each device has its own cyclic exchange with the controller, and update times are configured per device, typically from 1 ms up to several hundred milliseconds.

Standard switches work, and normal TCP/IP traffic such as web pages or diagnostics shares the same cable. Timing depends on the switches and the load, so the jitter is good enough for I/O and inverters but is not guaranteed at the microsecond level.

PROFINET IRT adds a time-slotted schedule. Every cycle is divided into a reserved interval for isochronous frames and an open interval for everything else, and all devices synchronise their clocks. That gives cycle times well below 1 ms with jitter under a microsecond, which is what tightly coordinated servo axes need. The price is hardware: every device and switch in the IRT path must contain IRT-capable switching hardware, and the topology has to be engineered in the project.

EtherCAT gets similar determinism differently: one frame passes through all slaves and is processed on the fly, and distributed clocks in the slaves synchronise the axes to well under a microsecond. The master is a normal Ethernet port, but every slave needs an EtherCAT slave controller.

Where the motion control runs changes the requirement. If the axes are coordinated by the PLC or motion controller with position setpoints sent every cycle (electronic gearing, cams, interpolation), the network must be isochronous: PROFINET IRT or EtherCAT with distributed clocks, with cycle times of around 1 to 4 ms being common for packaging axes.

If each drive performs its own positioning and only receives start commands and targets, PROFINET RT at a few milliseconds is sufficient and the hardware is simpler. So ask both suppliers how the six axes will be coordinated before comparing bus data sheets.

In practice the controller platform decides more than the fieldbus. Each PLC family has one network it supports natively, and its engineering tools, diagnostics and safety protocol (PROFIsafe on PROFINET, FSoE on EtherCAT) are built around that network. Mixing is possible through gateways or couplers, but each gateway adds a configuration tool, a delay and a diagnostic boundary.

For six axes and 60 I/O points either technology has ample performance, so choose the controller platform your team and your customer can maintain, and take the network that belongs to it.

Some installation differences affect the design. PROFINET RT lets you use stars, lines and standard managed switches, with ring redundancy through MRP. EtherCAT is usually wired as a line from device to device without switches, branches need junction modules, and the order of the devices is part of the configuration. Both use 100 Mbit/s copper with up to 100 m between devices.

Whichever you pick, confirm that every component on the list, including the inverters and any valve islands, is available with that interface. A single device that needs a gateway tends to cost more time than the rest of the network.