Skip to content
Tutorials Center
My learning

Topics

Lesson 26 of 37 ยท Communication Protocols

Fieldbus and Industrial Networks Overview

A map of industrial communication for PLCs: serial buses, fieldbuses, industrial Ethernet, the automation pyramid, determinism, topologies and a runnable C frame and CRC model.

A PLC rarely works alone. It reads remote I/O racks, talks to drives and robots, sends data to a SCADA server and may exchange messages with another PLC across the plant. All of that rides on industrial networks. Standard office networking is not enough, because a control network must be predictable, robust against electrical noise, and often fast enough to close a control loop in a few milliseconds.

No real PLC network is available here. The lesson explains concepts with diagrams and read-only frame formats, and uses C stand-ins to show framing and error checking.

The automation pyramid

Networks are layered by what they carry:

flowchart TB
    A["Enterprise: ERP, MES<br/>(office Ethernet, databases)"]
    B["Supervisory: SCADA, HMI<br/>(OPC UA, Modbus TCP, Ethernet)"]
    C["Control: PLC to PLC<br/>(PROFINET, EtherNet/IP)"]
    D["Field: sensors, valves, drives<br/>(IO-Link, PROFIBUS, Modbus RTU)"]
    A --> B --> C --> D

Lower levels need speed and determinism; upper levels need volume and openness.

At the field level, simple devices exchange a few bytes quickly. At the enterprise level, large data sets travel with no hard timing.

From wiring to fieldbus

Early automation connected each sensor to the PLC with its own two wires. A plant with thousands of points needed kilometers of cable. A fieldbus replaces point-to-point wiring with a shared digital bus: one cable connects many devices, each with an address. Benefits: less wiring, rich diagnostics, and configurable devices.

Well-known families:

Family Medium Notes
Modbus RTU RS-485 serial Simple, universal; see Modbus
PROFIBUS DP RS-485 Common in older Siemens plants
CANopen / DeviceNet CAN bus Motion, machinery, vehicles
IO-Link 3-wire point-to-point Sensor-level digital link
PROFINET, EtherNet/IP, EtherCAT Ethernet Modern, fast; see industrial Ethernet
Modbus TCP, OPC UA, MQTT TCP/IP Supervisory and IT/OT links; see OPC UA and MQTT

Key concepts

  • Master/slave (client/server). One device starts every exchange and the others answer. Modbus works like this.
  • Producer/consumer. A device publishes data and any interested device consumes it; EtherNet/IP uses this model.
  • Cyclic versus acyclic data. Cyclic data (process values) is exchanged at a fixed rate; acyclic data (configuration, diagnostics) is sent on demand.
  • Determinism. The guarantee that data arrives within a bounded time. Standard Ethernet with collisions or heavy traffic cannot promise it, so industrial variants add scheduling, priorities or special hardware.
  • Topology. Line (daisy chain), star (switch), ring (with redundancy). Rings let traffic reroute if a cable breaks.
  • Physical layer. RS-485 uses differential signalling over twisted pair, resisting noise over up to about 1200 m, with termination resistors at both ends of the line.

Frames and error checking

Data is sent in frames: a header with address and function, a payload, and a check value so receivers can detect corruption. A common check is a CRC (cyclic redundancy check). Modbus RTU uses CRC-16.

This C program builds a small Modbus-style request frame and computes the CRC-16 (polynomial 0xA001, initial value 0xFFFF, as in Modbus RTU). It is a stand-in showing the idea, not a driver.

C C stand-in: build a serial frame with CRC-16

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with scanf or fgets), it gets the next line from this box.

The CRC lets the receiver reject a frame that picked up electrical noise, instead of acting on a wrong value.

Polling a bus: a timing model

On a master/slave bus the master asks each slave in turn, so the update time grows with the number of devices. This model computes the cycle time for a serial bus.

C C stand-in: update time of a polled serial bus

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with scanf or fgets), it gets the next line from this box.

Twice the devices means twice the time. That is why large plants favor Ethernet-based protocols with higher speed and parallelism.

Choosing a network

Consider: speed and determinism required, number and type of devices, distance, noise environment, vendor ecosystem, diagnostics, and cost. Also plan security: segment the control network, restrict access, and never connect it to the internet directly (see safety and security basics).

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does a fieldbus mainly replace?

    A fieldbus connects many devices on one cable and carries digital values plus diagnostics.
  2. 2. Why does an industrial control network care about determinism?

    A control loop that receives data late can become unstable; deterministic networks bound the delay.
  3. 3. What is the purpose of the CRC in a frame?

    The receiver recomputes the CRC; a mismatch means the frame was damaged and must be discarded.
  4. 4. On a master/slave serial bus, what happens to update time when slaves are added?

    The master polls sequentially, so the full cycle is roughly the sum of every slave's exchange.

Summary

  • Industrial networks are layered in the automation pyramid, from field devices up to enterprise systems.
  • Fieldbuses replaced individual wires; Ethernet-based protocols now dominate for speed and openness.
  • Know master/slave versus producer/consumer, cyclic versus acyclic data, determinism and topology.
  • Frames carry address, data and a check value such as CRC-16.
  • The C programs are stand-ins illustrating framing and timing.

Next: Modbus RTU and TCP