A field guide to industrial Ethernet

Nearly every new field installation speaks some flavor of Ethernet, but "industrial Ethernet" is a family of incompatible protocols with different timing models, topologies, and vendor ecosystems. Here is how to keep the big four straight.

PROFINET

From PROFIBUS & PROFINET International (PI), dominant in process and factory automation, especially where Siemens controllers anchor the architecture. PROFINET RT carries real-time frames over standard Ethernet (prioritized, typically sub-10 ms cycles); PROFINET IRT adds scheduled, hardware-assisted communication for sub-millisecond, jitter-free motion. Conformance classes (A through D) describe which features a device supports — from basic RT over standard switches up to IRT with media redundancy and isochronous cycles. Strengths: enormous installed base, deep device profiles (PROFIdrive, PROFIenergy, PROFIsafe for functional safety), and seamless integration with the Siemens/TIA world. Note it is not routable IP traffic at the RT level — plan your network segmentation accordingly.

EtherNet/IP

From ODVA, built on the Common Industrial Protocol (CIP), dominant in North American discrete manufacturing and anywhere Rockwell/Allen-Bradley controllers lead. Standard Ethernet/IP traffic is ordinary TCP/UDP; implicit (I/O) messaging uses UDP with a producer/consumer model over standard switches. Device Level Ring (DLR) provides fast ring redundancy, and CIP Safety handles safety-rated communication. Strengths: uses standard Ethernet infrastructure and IP addressing throughout, huge multi-vendor catalog, and CIP's object model gives devices a consistent application layer. For hard-motion determinism it historically leaned on hardware and topology rather than schedule-based Ethernet — which is why CIP Motion and the move toward TSN matter.

EtherCAT

From Beckhoff, managed by the EtherCAT Technology Group, dominant in high-performance motion: packaging, robotics, semiconductor equipment, test rigs. Its trick is on-the-fly processing — a single Ethernet frame traverses every node, each reading and writing its data as the frame passes, with distributed clocks keeping axes synchronized to tens of nanoseconds. Cycle times down to tens of microseconds on ordinary Ethernet hardware (master needs a capable NIC; slaves need dedicated controller chips). Topology is flexible — line, ring, star via branch devices — and diagnostics are excellent. Trade-off: slaves require EtherCAT silicon, and the master is typically a soft controller (PC-based) or dedicated hardware rather than a traditional PLC rack, though many PLC vendors now offer EtherCAT masters.

TSN: the convergence layer

Time-Sensitive Networking is not a competitor but a set of IEEE 802.1 standards (time sync, scheduled traffic, frame preemption, stream reservation, redundancy) that bring determinism to standard Ethernet. The pitch: one converged network carrying control traffic, safety, and best-effort IT traffic with guarantees. All three protocols above have TSN strategies — PROFINET over TSN, EtherNet/IP with TSN (as part of the ODVA/OPC connectivity push), and EtherCAT's coexistence story — and OPC UA FX (Field eXchange) aims to be the vendor-neutral application layer on top. TSN adoption is real but uneven: silicon, switches, and end devices are shipping, while multi-vendor schedule configuration (the hard part) is still maturing.

How to choose

• Match your controller ecosystem first: Siemens → PROFINET, Rockwell → EtherNet/IP, Beckhoff/soft-control → EtherCAT. Fighting the ecosystem costs more than any protocol advantage.
• Match cycle-time needs second: millisecond class → any of them; sub-millisecond multi-axis motion → EtherCAT or PROFINET IRT; converged IT/OT backbone → TSN-based design.
• Design for the next owner: document topologies, use managed switches with diagnostics, and keep safety (PROFIsafe, CIP Safety, Safety over EtherCAT) in the plan from day one rather than bolting it on.

The honest summary: the protocol wars are mostly over at the field level — each incumbent won its territory — and the interesting engineering has moved up a layer, to TSN convergence and to getting data off all of these networks into software that can use it.