Industrial IoT and Business Operations · Study deck

Industrial Protocols: Families and Timing

This first route distinguishes industrial communication duties, then traces legacy and Ethernet families through timing, bandwidth, and cycle-time evidence.

Ada is your guide for this deck.

iiotindustrialprotocols

Ada, the module guide, in a scene from this chapter.

After studying this chapter

Learning objectives

You will be able to:

Compare industrial protocols (Modbus, PROFINET, EtherCAT, OPC-UA) by latency, throughput, and use case
Evaluate protocol requirements for different industrial applications based on ISA-95 levels
Justify protocol selection based on latency, determinism, and security constraints
Distinguish between legacy serial protocols and modern industrial Ethernet protocols

Major section

Overview · Start With the Story

A protocol is a shared set of rules for how two machines exchange data.

The rule set must fit the job and the harm caused by delay or loss.
A status report for next week's maintenance plan can arrive later.
No industrial protocol is best for every loop.
The two messages share a factory, but they do not share the same time limit or failure cost.

Major section

Protocols Need Timing Fit

EtherCAT may be needed for tightly synchronized motion.

A conveyor status light, a servo axis, a safety interlock, and an ERP production report should not all use the same communication pattern.
The right question is what happens if a message is late, duplicated, stale, missing, or accepted by the wrong system.
Industrial protocol decisions also have long memory.

Major section

Protocols Need Timing Fit (continued)

The first distinction is between monitoring, automation, motion, safety, and integration.

Modbus TCP may be acceptable for simple register reads.
PROFINET IO or EtherNet/IP may fit distributed I/O and drives.
OPC UA may be the right layer for semantic IT/OT integration once the real-time control boundary is protected.

Major section

Protocols Need Timing Fit (continued)

An industrial protocol is not selected because it is newer or more fashionable.

MQTT Sparkplug B may help publish normalized telemetry upward, but it should not be confused with a deterministic fieldbus for closed-loop control.
Plants may run equipment for 20 or 30 years, with spare parts, electrician skills, PLC programming tools, vendor support contracts, cable trays, and downtime windows already fixed.
A greenfield packaging line can optimize around a modern motion network.

Major section

Match Protocol to Control Loop

A 100 ms tank-level trend can tolerate retry and buffering.

A 1 ms drive loop cannot wait for a broker, VPN, or cloud API.
A brownfield Modbus RTU segment may be left in place and bridged, while a new motion cell may justify EtherCAT or PROFINET IRT.
Beckhoff and many motion-control systems use EtherCAT.

Major section

Match Protocol to Control Loop (continued)

The same plant can therefore use several protocols at once, each with a different responsibility.

Rockwell/Allen-Bradley plants often use EtherNet/IP with CIP objects and Studio 5000.
Legacy panels may expose Modbus RTU over RS-485 or Modbus TCP.
Integration layers may use OPC UA, MQTT Sparkplug B, or historian connectors.

The protocol family changes the communication pattern: polling registers, cyclic I/O, frame-through-device processing, and semantic client-server integration solve different problems.

Major section

Match Protocol to Control Loop (continued)

Maintenance teams must be able to diagnose the chosen stack at 2 a.m., not only during a vendor demo.

A temperature trend might move from a Modbus RTU transmitter to a gateway, then to OPC UA, then to a historian and dashboard.
A robot-axis command might stay inside EtherCAT or PROFINET IRT and never cross the enterprise boundary.
A plant KPI might be aggregated by an edge node and published through MQTT after quality checks.

Major section

Determinism Needs Scheduling

Industrial Ethernet does not automatically make a network deterministic.

These details explain why two protocols with similar cable connectors can behave very differently under load.
Legacy protocols have different tradeoffs.
Modbus RTU over RS-485 is simple and widely deployed, but it is request-response, usually single-master, and carries registers rather than rich semantics.

EtherCAT network architecture showing master-slave topology: the EtherCAT master sends a single frame through each slave in sequence, and each device reads or writes its own data as the frame passes.

Major section

Determinism Needs Scheduling (continued)

PROFIBUS DP and DeviceNet solved many fieldbus needs before Ethernet became common.

IO-Link often connects smart sensors and actuators to a master that then speaks PROFINET, EtherNet/IP, or another higher-level protocol.
These protocols can still be correct when downtime, replacement cost, or certification risk makes wholesale migration unattractive.
Testing should match the consequence.

Major section

Determinism Needs Scheduling (continued)

A motion cell needs cycle-time and jitter tests under worst-case load.

A drive network may stay on EtherCAT, an I/O island may use PROFINET, a gateway may expose an OPC UA server, and a DMZ broker may publish Sparkplug B topics to analytics systems.
IEC 62443 zones and conduits help decide which messages can cross from cell, area, site operations, and enterprise networks.
The selected protocol is only credible when those evidence paths are defined.

Major section

Robot Factory Visit · Protocol Requirements

Temperature Terry is amazed!

The factory has 50 robots all working together to build cars.
Nobody can hear anything!
Robots have the same problem -- they all need to send messages, but the messages MUST arrive on time, or a robot arm might bump into something!

Major section

Key Concepts · Consumer vs Industrial IoT

A tank-level trend sampled every hundred milliseconds and a drive loop that runs every millisecond can share a plant, a network and a vendor, yet only the first can be retried or buffered.

The table then keeps them in separate columns through six rows, from timing and reliability to safety, security and lifecycle.

Consumer IoT paths can often retry or defer updates, while Industrial IoT paths must separate best-effort monitoring from bounded control and safety-related communication.

Major section

Industrial Protocol Evolution

The middle block moves onto Ethernet without giving up determinism, which is why 2003 produces two different answers in one year, one dividing time into slots and one passing a single frame through every device.

The last entry changes the question again, because: OPC-UA is not competing on speed.

Industrial protocol families evolved from simple polling buses toward fieldbus, industrial Ethernet, and structured IT/OT integration layers.

Major section

Legacy Industrial Protocols

The master sends a request, a single device answers, and the numbered sequence beneath shows the cycle repeating around the bus.

Nothing on the lower row can speak on its own, so a sensor with urgent news waits its turn, and that is the cost of the design.
The benefit is in the same picture.

Modbus keeps the communication model simple: one master polls register data from slave devices, which makes it easy to bridge but limited for rich semantics and native security.

Major section

Modern Industrial Ethernet · Putting Numbers to It

Standard PROFINET RT gives cyclic I/O priority over ordinary traffic.

Configuration, diagnostics, and IT-style exchanges remain in the non-real-time layer on the same backbone.
Standard TCP/IP: Uses unmodified Ethernet.
Figure: EtherCAT network architecture showing master-slave topology answers how EtherCAT reaches such short cycles on ordinary Ethernet hardware.

PROFINET separates deterministic cyclic I/O traffic from non-real-time configuration, diagnostics, and IT-style traffic.

Major section

EtherCAT Cycle Time

The evidence ledger must preserve sensor calibration, sample time, command, alarm state, and operator ownership, because a fast protocol cannot repair an untrustworthy measurement or an unsafe fallback.

The PLC compares the measured 0.68 mg/L with the 0.5–1.0 mg/L target band; the decision remains hold unless a bounded adjustment is justified.

Deck summary

Key takeaways

A protocol is a shared set of rules for how two machines exchange data.

EtherCAT may be needed for tightly synchronized motion.
The first distinction is between monitoring, automation, motion, safety, and integration.
An industrial protocol is not selected because it is newer or more fashionable.
A 100 ms tank-level trend can tolerate retry and buffering.

Retrieval practice

Recall check 1 of 3

Ada says: answer from memory, then check your reasoning.

Q1A plant compares a motion loop with a historian feed. What should guide protocol choice?

AUse the same cloud messaging path for both

BPick the fastest headline rate for both paths

CCompare timing, determinism, safety and security per path.

DChoose only from the newest vendor catalogue

Show answer

Answer: C Each path has different duties that must be made explicit.

Retrieval practice

Recall check 2 of 3

Ada says: answer from memory, then check your reasoning.

Q2A factory has 200 legacy Modbus RTU sensors on RS-485 serial networks. The plant manager wants to integrate this data into a new cloud-based analytics platform without replacing the sensors. What is the most practical approach?

AReplace all 200 working sensors with EtherCAT devices before integration

BAdd individual Wi-Fi adapters to every serial sensor and manage 200 wireless links

CInstall PROFINET across the plant and replace sensors as each segment migrates

DUse Modbus-to-OPC-UA gateways on RS-485 segments, then connect OPC-UA upstream

Show answer

Answer: D Gateways can map Modbus registers into an OPC UA information model and carry the data to an upstream analytics path without replacing sensors.

Retrieval practice

Recall check 3 of 3

Ada says: answer from memory, then check your reasoning.

Q3What makes EtherCAT uniquely fast compared to other industrial Ethernet protocols like PROFINET or EtherNet/IP?

AIt uses proprietary fiber links that are faster than standard copper Ethernet

BSlaves process one passing Ethernet frame on the fly, avoiding per-device frame overhead

CIt compresses all process data into smaller packets before each control cycle

DIt runs every device at 10 Gbps instead of standard industrial Ethernet speeds

Show answer

Answer: B EtherCAT's 'processing on the fly' architecture sends a single Ethernet frame that passes through all slaves sequentially.

Print reference

Answers

Answer key.

C · Each path has different duties that must be made explicit.
D · Gateways can map Modbus registers into an OPC UA information model and carry the data to an upstream analytics path without replacing sensors.
B · EtherCAT's 'processing on the fly' architecture sends a single Ethernet frame that passes through all slaves sequentially.