50 Industrial Ethernet Protocols

In 60 Seconds

Industrial Ethernet protocols (PROFINET, EtherNet/IP, EtherCAT) extend standard Ethernet with deterministic, real-time capabilities required for machine control, where missing a 100ms deadline can cause equipment damage. Time-Sensitive Networking (TSN) is emerging as a converged IT/OT standard providing guaranteed latency on standard Ethernet hardware.

50.1 Industrial Ethernet: PROFINET, EtherCAT, and TSN

Learning Objectives

By the end of this section, you will be able to:

Compare major industrial Ethernet protocols (PROFINET, EtherNet/IP, EtherCAT) by cycle time, node capacity, and vendor ecosystem
Distinguish real-time classes (NRT, RT, IRT) and explain their deterministic networking requirements
Design EtherCAT networks for high-speed motion control using distributed clocks
Configure PROFINET for Siemens automation systems with correct device roles and Frame IDs
Evaluate Time-Sensitive Networking (TSN) standards for converged IT/OT deployments
Select the appropriate industrial Ethernet protocol for a given application by applying a structured decision matrix
Calculate position error accumulation from cycle time jitter to justify protocol selection

50.2 Prerequisites

Before diving into this chapter, you should be familiar with:

Industrial Protocols Overview: IT/OT networking context
Networking Basics: Ethernet and TCP/IP fundamentals
Wired Communication: Physical layer concepts

Key Concepts

PROFINET: Siemens-led industrial Ethernet standard for automation; supports three communication channels: TCP/IP (configuration), RT (real-time, 1-10ms cycle), IRT (isochronous real-time, <1ms cycle).
TSN (Time-Sensitive Networking): IEEE 802.1 standards extending standard Ethernet with time-bounded delivery, traffic shaping, and frame preemption for deterministic industrial Ethernet.
EtherCAT: Beckhoff’s industrial Ethernet protocol where the master broadcasts frames that each slave node reads/inserts into as the frame passes through, achieving sub-100µs cycle times.
Real-Time (RT) Communication: PROFINET RT uses standard Ethernet frames bypassing TCP/IP stack with cycle times of 1-10ms; suitable for most automation applications.
Isochronous Real-Time (IRT): PROFINET IRT uses time-synchronized frames with <1ms and microsecond-level jitter; required for motion control and drives.
GSDML File: PROFINET’s device description file (Generic Station Description Markup Language) declaring module slots, submodules, and parameters; used by engineering tools for automatic device configuration.

For Beginners: Why Industrial Ethernet?

Office Ethernet: Designed for files, emails, web browsing - “Best effort” delivery—packets arrive eventually - A 100ms delay? Nobody notices

Industrial Ethernet: Designed for machine control - Deterministic delivery—packets MUST arrive on time - A 100ms delay? Robot crashes, product ruined

The Challenge: Standard Ethernet wasn’t built for this. When you plug a printer and a robot controller into the same switch, the printer’s large print job can delay the robot’s control packets.

The Solutions:

Modified Ethernet (PROFINET IRT, EtherCAT): Change how Ethernet works
Priority Mechanisms (TSN): Add strict scheduling to standard Ethernet
Dedicated Networks: Keep industrial traffic separate

Real-World Analogy:

Standard Ethernet = Regular highway (everyone shares, traffic jams possible)
Industrial Ethernet = Emergency vehicle lane (guaranteed access for critical traffic)

Sensor Squad: The Fast Lane

“Regular Ethernet works fine for my web browsing, so why do factories need special Ethernet?” asked Sammy the Sensor.

Max the Microcontroller explained: “Imagine a highway with no speed limits and no lane rules. Most of the time, traffic flows fine. But during rush hour, you might wait 10 seconds at a bottleneck. That’s normal Ethernet – usually fast, but no guarantees. Now imagine a robot arm that MUST receive its command within 1 millisecond. A 10-second delay means a crashed robot.”

“Industrial Ethernet protocols like PROFINET, EtherCAT, and EtherNet/IP add a reserved fast lane,” said Lila the LED. “Critical control messages get priority – they ALWAYS arrive on time, even when the network is busy. It’s like an ambulance lane on a highway.”

Bella the Battery was impressed: “EtherCAT is the fastest – it can update 1,000 devices in just 30 microseconds by passing a single packet through all devices in a chain. PROFINET IRT guarantees delivery within 250 microseconds using reserved time slots. These numbers sound tiny, but in a factory making cars or chips, they’re the difference between precision and disaster!”

50.4 Industrial Ethernet Landscape

Understanding Industrial Ethernet Determinism

Core Concept: Determinism means guaranteed, predictable timing—a control command sent will arrive within a known time window with minimal variation (jitter), regardless of other network traffic.

Why It Matters: Standard Ethernet uses best-effort delivery where packets may be delayed by other traffic. For motion control (robot arms, CNC machines), a delayed command can cause collisions, product defects, or safety hazards. Industrial Ethernet protocols solve this through various mechanisms: time-slotted scheduling (PROFINET IRT), processing-on-the-fly (EtherCAT), or IEEE TSN standards (802.1Qbv time-aware shaper).

Key Takeaway: Match your cycle time requirement to the protocol: <100 microseconds requires EtherCAT or PROFINET IRT; 1-10 milliseconds works with PROFINET RT or EtherNet/IP; >10 milliseconds can use standard Ethernet with OPC-UA or MQTT.

50.4.2 Protocol Comparison

Protocol	Vendor	Cycle Time	Nodes	Primary Use
PROFINET RT	Siemens	1ms - 10ms	512	Factory automation, general I/O
PROFINET IRT	Siemens	250μs - 1ms	512	Motion control, synchronized axes
EtherNet/IP	Rockwell	1-10ms	Unlimited	Process, discrete
EtherCAT	Beckhoff	31.25μs - 100μs	65,535	High-speed motion control
CC-Link IE	Mitsubishi	125μs - 10ms	254	Asia-Pacific automation
POWERLINK	B&R	200μs - 10ms	253	CNC, packaging
SERCOS III	Bosch	31.25μs	511	Precision motion control

50.5 PROFINET

50.5.1 Architecture

PROFINET three performance tiers: NRT for configuration, RT for 10ms cycles, IRT for sub-1ms isochronous control — Figure 50.2: PROFINET performance classes from NRT to IRT

50.5.2 PROFINET Device Roles

Role	Function	Example
IO Controller	Master device, initiates communication	PLC (S7-1500)
IO Device	Slave device, responds to controller	Remote I/O, drives
IO Supervisor	Configuration and diagnostics	Engineering station

50.5.3 PROFINET Frame Structure

| Ethernet Header | VLAN Tag | Frame ID | Cyclic Data | Status | FCS |
| 14 bytes        | 4 bytes  | 2 bytes  | Variable    | 4 bytes| 4 bytes|

Quick Check: PROFINET Frame IDs

50.5.4 Network Topology

PROFINET topology with S7-1500 PLC controller connecting through switch to IO devices, drives, and HMI panel — Figure 50.3: PROFINET network topology with PLC and IO devices

50.6 EtherCAT

50.6.1 Operating Principle

EtherCAT’s key innovation: Processing on the Fly

EtherCAT processing-on-the-fly: single frame passes through slaves, each reading and writing data inline — Figure 50.4: EtherCAT processing-on-the-fly single frame sequence

50.6.2 EtherCAT Frame Structure

| Ethernet Header | EtherCAT Header | Datagram 1 | Datagram 2 | ... | FCS |
| 14 bytes        | 2 bytes         | Variable   | Variable   |     | 4 bytes|

Datagram Structure:

| Header | Address | Data | WKC |
| 10 bytes| 4 bytes | N bytes | 2 bytes|

WKC (Working Counter): Incremented by each slave that processes the datagram

50.6.3 EtherCAT Addressing Modes

Mode	Description	Use Case
Position	Sequential order in network	Simple topologies
Node	Configured node address	Large networks
Logical	FMMU-mapped logical address	Process image
Broadcast	All slaves	Configuration

50.6.4 Distributed Clocks

EtherCAT achieves sub-microsecond synchronization:

EtherCAT distributed clocks with master reference synchronizing slaves to sub-microsecond jitter — Figure 50.5: EtherCAT distributed clocks synchronization chain

50.6.5 EtherCAT Network Topology

EtherCAT daisy-chain topology with master, slaves, branch coupler, and optional redundancy return path — Figure 50.6: EtherCAT daisy-chain topology with branch support

50.7 EtherNet/IP

50.7.1 Architecture

EtherNet/IP uses the Common Industrial Protocol (CIP) over standard Ethernet:

EtherNet/IP CIP architecture stack with application objects/services over TCP explicit and UDP implicit messaging — Figure 50.7: EtherNet/IP CIP protocol architecture stack

50.7.2 CIP Connections

Type	Transport	Use Case
Explicit	TCP	Configuration, diagnostics
Implicit (I/O)	UDP multicast	Cyclic data exchange
Unconnected	UDP	One-time requests

50.8 Time-Sensitive Networking (TSN)

50.8.1 TSN Standards

TSN is a set of IEEE 802.1 standards for deterministic Ethernet:

Standard	Name	Function
802.1AS	Timing and Sync	Clock synchronization
802.1Qbv	Time-Aware Shaper	Scheduled traffic
802.1Qbu/802.3br	Frame Preemption	Interrupt low-priority
802.1Qci	Stream Filtering	Ingress policing
802.1CB	Redundancy	Frame replication
802.1Qcc	Configuration	Central management

50.8.2 TSN Traffic Scheduling

TSN time-aware shaper Gantt chart with critical, scheduled, and best-effort traffic in deterministic time slots — Figure 50.8: TSN time-aware shaper scheduling for three traffic classes

50.8.3 TSN Network Architecture

Converged TSN network carrying critical motion, scheduled I/O, and best-effort IT traffic on single infrastructure — Figure 50.9: Converged TSN network with mixed traffic types

50.8.4 OPC-UA over TSN

The emerging standard for unified industrial communication:

OPC-UA over TSN stack with information model, pub/sub messaging, and deterministic TSN Ethernet transport — Figure 50.10: OPC-UA over TSN unified communication stack

Interactive: Industrial Ethernet Cycle Time Calculator

Estimate whether your motion control requirements can be met by each protocol, based on device count and required update rate.

Show code

viewof ctDevices = Inputs.range([2, 512], {value: 32, step: 2, label: "Number of devices on network"})
viewof ctRequiredCycle = Inputs.select(["< 100 µs", "100–500 µs", "500 µs – 1 ms", "1–10 ms", "> 10 ms"], {label: "Required cycle time:"})
viewof ctApplication = Inputs.select(["CNC / Precision Machining", "Robot Motion Control", "Packaging / Assembly", "Process Control", "Building Automation"], {label: "Application type:"})

Show code

{
  // Protocol specs: [minCycle_us, maxDevices, name, color, description]
  const protocols = [
    {name: "EtherCAT", minUs: 31, maxDev: 65535, color: "#16A085",
     desc: "Processing-on-the-fly. Single frame services all nodes. Distributed Clocks for sub-µs sync."},
    {name: "PROFINET IRT", minUs: 250, maxDev: 512, color: "#3498DB",
     desc: "Isochronous Real-Time with scheduled time slots. Requires IRT-capable switches."},
    {name: "PROFINET RT", minUs: 1000, maxDev: 512, color: "#E67E22",
     desc: "Real-Time over standard Ethernet. Good for most automation tasks."},
    {name: "EtherNet/IP", minUs: 1000, maxDev: 99999, color: "#9B59B6",
     desc: "CIP over standard TCP/UDP. Implicit I/O via UDP multicast for cyclic data."},
    {name: "TSN (802.1Qbv)", minUs: 100, maxDev: 99999, color: "#2C3E50",
     desc: "Emerging standard. Time-aware shaper enables determinism on standard Ethernet."}
  ];

  const reqMap = {"< 100 µs": 100, "100–500 µs": 500, "500 µs – 1 ms": 1000, "1–10 ms": 10000, "> 10 ms": 99999};
  const reqUs = reqMap[ctRequiredCycle];

  const appRec = {
    "CNC / Precision Machining": "EtherCAT",
    "Robot Motion Control": "EtherCAT",
    "Packaging / Assembly": "PROFINET IRT",
    "Process Control": "PROFINET RT",
    "Building Automation": "EtherNet/IP"
  };

  return html`<div style="background:#f8f9fa;border:1px solid #dee2e6;border-radius:6px;padding:16px;margin-top:8px;">
    <table style="width:100%;border-collapse:collapse;font-size:0.85em;margin-bottom:10px;">
      <tr style="background:#2C3E50;color:#fff;">
        <th style="padding:6px 8px;text-align:left;">Protocol</th>
        <th style="padding:6px 8px;">Min cycle</th>
        <th style="padding:6px 8px;">Max devices</th>
        <th style="padding:6px 8px;">Meets requirement?</th>
      </tr>
      ${protocols.map(p => {
        const meetsTime = p.minUs <= reqUs;
        const meetsDev = p.maxDev >= ctDevices;
        const ok = meetsTime && meetsDev;
        const recommended = p.name === appRec[ctApplication];
        return html`<tr style="border-bottom:1px solid #dee2e6;background:${ok ? (recommended ? '#eafaf1' : '#fff') : '#fdf2f2'};">
          <td style="padding:6px 8px;font-weight:bold;color:${p.color};">${p.name}${recommended ? ' ★' : ''}</td>
          <td style="padding:6px 8px;text-align:center;">${p.minUs < 1000 ? p.minUs + ' µs' : (p.minUs/1000) + ' ms'}</td>
          <td style="padding:6px 8px;text-align:center;">${p.maxDev > 9000 ? 'Unlimited' : p.maxDev}</td>
          <td style="padding:6px 8px;text-align:center;font-weight:bold;color:${ok ? '#16A085' : '#E74C3C'};">${ok ? '✓ Yes' : (meetsTime ? '✗ Too many devices' : '✗ Too slow')}</td>
        </tr>`;
      })}
    </table>
    <div style="padding:8px;background:#fff;border-radius:4px;border:1px solid #dee2e6;font-size:0.85em;color:#2C3E50;">
      ★ Recommended for <strong>${ctApplication}</strong>: <strong style="color:${protocols.find(p=>p.name===appRec[ctApplication]).color};">${appRec[ctApplication]}</strong> —
      ${protocols.find(p=>p.name===appRec[ctApplication]).desc}
    </div>
  </div>`;
}

50.9 Protocol Selection Guide

50.9.1 Decision Matrix

Industrial Ethernet selection flowchart branching by cycle time and vendor to recommend EtherCAT, PROFINET, or TSN — Figure 50.11: Industrial Ethernet protocol selection decision flowchart

50.9.2 Application Suitability

Application	Best Protocol	Cycle Time	Why
CNC Machining	EtherCAT	100-250μs	Sub-microsecond sync
Robotics	EtherCAT, PROFINET IRT	250μs-1ms	Coordinated motion
Packaging	PROFINET RT, EtherNet/IP	1-10ms	Fast but not critical
Process Control	PROFINET RT, Modbus TCP	10-100ms	Slow processes
Building Automation	BACnet/IP, Modbus TCP	100ms-1s	Non-critical timing

Putting Numbers to It

How does cycle time affect robot arm positioning accuracy? Consider a 6-axis industrial robot welding car frames at 0.5 m/s tool speed.

EtherCAT (100 μs cycle time):

Position updates: 10,000 Hz
Distance per update: $0.5\text{ m/s} / 10{,}000 = 0.05\text{ mm}$
Jitter tolerance: ±10 μs (±0.005 mm position error)
Total accumulated error over 1-meter weld: ~10 updates late = $10 \times 0.05 = 0.5\text{ mm}$

PROFINET RT (1 ms cycle time):

Position updates: 1,000 Hz
Distance per update: $0.5\text{ m/s} / 1{,}000 = 0.5\text{ mm}$
Jitter tolerance: ±100 μs (±0.05 mm)
Accumulated error: ~10 updates late = $10 \times 0.5 = 5\text{ mm}$

Standard Ethernet (10 ms):

Position updates: 100 Hz
Distance per update: $5\text{ mm}$
Jitter: ±5 ms (±2.5 mm!)
Accumulated: $50\text{ mm}$ — unusable for precision welding

Quality impact: Automotive specification requires ±2 mm weld accuracy. EtherCAT easily meets this (0.5 mm error). Standard Ethernet fails completely (50 mm drift). This 10× cycle time improvement costs only ~$200 more per robot controller but prevents $10,000+ in scrap per misaligned frame!

50.10 Understanding Check

Knowledge Check

Scenario: You’re designing a semiconductor wafer handling system with: - 6-axis robot arm (synchronized 8 axes total) - 50+ I/O points for vacuum, sensors - Vision system for alignment - Integration with MES for recipe management - Requirement: 100μs motion synchronization

Questions:

Which industrial Ethernet would you choose for motion control?
How would you handle the vision system integration?
What about MES connectivity?
How would you ensure 100μs synchronization?

Solution

1. Motion Control: EtherCAT

100μs requirement eliminates PROFINET RT and EtherNet/IP
EtherCAT achieves 50-100μs cycles easily
Distributed Clocks for sub-microsecond synchronization
Native support in most servo drive manufacturers

2. Vision System Integration: Option A: Separate GigE Vision network (keeps determinism) Option B: EtherCAT with CoE (CAN over EtherCAT) for triggers - Vision processing done off-network - Only trigger/result over EtherCAT (~μs for signal) - Camera images via separate GigE (bulk data)

3. MES Connectivity: OPC-UA via Gateway

EtherCAT master exposes OPC-UA server
MES connects as OPC-UA client
Non-deterministic traffic isolated from motion network
Recipe download before motion, not during

4. Ensuring 100μs Synchronization:

Distributed Clocks Configuration:
- Reference clock: EtherCAT master
- DC slaves: All servo drives
- Propagation delay: Auto-measured at startup
- Sync0 signal: Triggers synchronized motion
- Jitter: <100ns (100× better than requirement)

Network topology:

Master → Drive1 → Drive2 → ... → Drive8 → I/O

Daisy-chain minimizes jitter
Total propagation: 8 × 1μs = 8μs
Plenty of margin for 100μs cycle

Auto-Gradable Quick Check

Interactive Quiz: Match Concepts

🏷️ Label the Diagram

💻 Code Challenge

📝 Order the Steps

50.11 Summary

PROFINET dominates Siemens ecosystems with RT (10ms) and IRT (<1ms) classes
EtherCAT achieves the fastest cycles (<100μs) with processing on the fly
EtherNet/IP (Rockwell) uses standard TCP/UDP with CIP application layer
TSN is the future – deterministic standard Ethernet enabling IT/OT convergence
Choose by cycle time: <100μs -> EtherCAT, <1ms -> PROFINET IRT, >1ms -> PROFINET RT/EtherNet/IP
Distributed Clocks (EtherCAT) or PTP (TSN) enable sub-microsecond synchronization
OPC-UA over TSN is emerging as the unified industrial standard
Real-world ROI: BMW achieved 18-month payback on EtherCAT migration through 75% scrap reduction and 15% throughput increase

50.12 Concept Relationships

Industrial Ethernet protocols solve the determinism challenge through different mechanisms:

Determinism = Predictable Timing: Standard Ethernet is “best effort” - packets arrive when they arrive. Industrial control requires guaranteed delivery within time window (e.g., servo motor command MUST arrive within 250 µs). Three approaches: (1) PROFINET IRT uses time-slotted scheduling, (2) EtherCAT uses processing-on-the-fly, (3) TSN uses IEEE 802.1 standards. All achieve same goal (determinism) via different physics.

Cycle Time Drives Protocol Selection: The worked example (packaging line) demonstrates decision tree: 100 µs requirement → EtherCAT (only option). 500 µs → PROFINET IRT or EtherCAT. 10 ms → PROFINET RT, EtherNet/IP, or standard Ethernet + OPC-UA. Cycle time is the PRIMARY selection criterion, not features or vendor preference.

TSN Convergence Vision: Current state = protocol silos (PROFINET for Siemens, EtherCAT for Beckhoff, EtherNet/IP for Rockwell). TSN future = unified transport layer (IEEE 802.1Qbv time-aware shaper + 802.1AS clock sync) with OPC-UA information model on top. OPC-UA over TSN eliminates protocol lock-in while preserving determinism. OPC-UA Fundamentals explains information model side.

Real-World Complexity: BMW case study shows EtherCAT migration delivered 18-month ROI through 75% scrap reduction + 15% throughput increase. BUT this wasn’t just protocol swap - it was full re-engineering (robot programs rewritten, PLC logic updated, operator training). Technology selection is 20% of project; integration is 80%.

50.13 See Also

Protocol Comparisons:

OPC-UA Fundamentals - OPC-UA provides integration layer ABOVE real-time protocols. PROFINET controls servo (1 ms cycle), OPC-UA reads status (100 ms poll). Complementary, not competitive.
Modbus Protocol - Modbus = no determinism guarantees. PROFINET RT = <10 ms deterministic. Different problem domains (Modbus for slow I/O, PROFINET for motion control).

Real-Time Fundamentals:

Time-Sensitive Networking (TSN) - IEEE 802.1 standards enabling convergence. 802.1Qbv (time-aware shaper), 802.1AS (clock sync), 802.1Qbu (frame preemption) are building blocks.
Distributed Clocks - EtherCAT achieves <100 ns synchronization. How: reference clock in first slave, each slave measures propagation delay, compensates in hardware. Nanosecond sync enables coordinated multi-axis motion.

Deployment Guides:

PROFINET Engineering - GSD files, device configuration, topology planning, redundancy (MRP ring), diagnostics.
EtherCAT Master Configuration - ESI files, PDO mapping, distributed clock setup, safe state configuration.

Advanced Topics:

TSN + 5G Integration - Wireless TSN using 5G URLLC (Ultra-Reliable Low-Latency Communication). Enables mobile robots with deterministic wireless (1 ms latency, 99.9999% reliability).
Safety Protocols - PROFIsafe (PROFINET safety layer), FSoE (EtherCAT safety), CIP Safety (EtherNet/IP). Functional safety (SIL 2/3) on top of real-time protocols.

Hands-On:

Try Industrial Ethernet Cycle Time Calculator to visualize cycle time vs number of devices for each protocol.

50.14 What’s Next

Continue exploring industrial protocols:

Chapter	Focus	Why Read It
OPC-UA Fundamentals	Semantic information model and secure Pub/Sub	Understand how OPC-UA sits above PROFINET/EtherCAT as the integration layer connecting controllers to MES and cloud
Modbus Protocol	Legacy serial and TCP-based register protocol	Compare PROFINET’s determinism against Modbus TCP’s best-effort delivery; assess migration decisions for brownfield sites
Industrial Protocols Overview	Full landscape of OT protocols from fieldbus to Industrial Ethernet	Place PROFINET and EtherCAT in the broader IT/OT context alongside HART, Foundation Fieldbus, and PROFIBUS
Networking Basics	Ethernet, TCP/IP, and switching fundamentals	Reinforce the Layer 2 mechanisms (VLAN tagging, frame priority) that PROFINET and TSN build upon
Wired Communication	Physical layer cabling, connectors, and signal integrity	Apply cable selection criteria (Cat5e vs. Cat6a) for EtherCAT daisy-chain and PROFINET star topologies