industrial//industrial communication//industrial Ethernet

Industrial Ethernet is the family of Ethernet variants that give control networks the properties office Ethernet never prioritized: low latency, low jitter, determinism, synchronization, robustness, redundancy. Office Ethernet sells throughput per euro; industrial Ethernet sells a bound on when the frame arrives: same connector and same frames at the bottom, with a scheduler, a clock and a recovery mechanism on top that the office never needed. From about 2000, Ethernet became dominant in automation as well, and each vendor ecosystem solved those needs its own way, which produced a family of incompatible industrial Ethernets and the fragmentation that still exists.

Industrial Ethernet is the family of Ethernet variants that give control networks the properties office Ethernet never prioritized: low latency, low jitter, determinism, synchronization, robustness, redundancy. Office Ethernet sells throughput per euro; industrial Ethernet sells a bound on when the frame arrives: same connector and same frames at the bottom, with a scheduler, a clock and a recovery mechanism on top that the office never needed. From about 2000, Ethernet became dominant in automation as well, and each vendor ecosystem solved those needs its own way, which produced a family of incompatible industrial Ethernets and the fragmentation that still exists.

The members, roughly in order of ambition: Modbus TCP (plain TCP/IP, simple and interoperable, no real-time machinery), EtherNet/IP (Rockwell's world, the CIP object model), PROFINET (Siemens's world, an expressive control network with real-time classes), EtherCAT (Beckhoff's world, hyper-deterministic, built for motion), plus POWERLINK and CC-Link IE in their own ecosystems.

The family is the third rung of industrial communication. The hardware follows: an industrial switch is chosen for recovery time and synchronization, not for throughput (determinism).

What all of them share with the serial fieldbuses is that they carry a control vocabulary; what none of them carries is the semantics a data layer needs, which is why OPC UA and MQTT sit above them rather than replace them (data).