Fieldbuses

What are fieldbuses?

A fieldbus is a digital industrial communication network that lets field equipment such as sensors, actuators, I/O modules and drives exchange data deterministically over a single shared cable with a controller such as a PLC or DCS. From the late 1980s onwards, fieldbuses replaced conventional point-to-point wiring, in which every signal had its own pair of wires running back to the control cabinet. That saves cable and cabinet space, enables remote diagnostics and forms the lowest communication layer (levels 0–1) of the Purdue Model and the automation pyramid. Well-known examples are Profibus, Modbus RTU, CAN, Foundation Fieldbus and AS-Interface.

🧠 What does a fieldbus do?

A fieldbus has four core tasks:

• Cyclic process data - measured values and commands are exchanged in a fixed cycle (typically 1–100 ms), so the controller can act deterministically
• Acyclic data - parameterisation, configuration and device diagnostics on request, without disturbing the cyclic traffic
• Diagnostics and alarms - devices report wire breaks, short circuits or internal faults themselves, whereas an analogue signal only shows “no value”
• Less wiring - dozens of devices on one cable instead of one wire pair per signal, often via O close to the machine

Most fieldbuses follow a master/slave or controller/device principle: one controller polls the devices in a fixed sequence or shares bus access by passing a token, as Profibus does between multiple masters. CAN is the well-known exception: every node may transmit, and when two nodes transmit at once the message with the highest priority (the lowest identifier) wins without any data being lost. Either way the response time is predictable, which is essential for real-time control.

🕰️ How did fieldbuses come about?

Until the 1980s, every signal ran to the control cabinet as a 4-20 mA loop or a 24 V contact. As microprocessors found their way into field devices, competing digital buses appeared:

The “fieldbus wars” of the 1990s were fought over which protocol would become the international standard. The compromise was that IEC 61158 describes multiple protocol types and IEC 61784-1 groups them into communication profile families (CPFs). So there never was a single fieldbus, only a recognised family.

📦 Which fieldbus protocols are most widely used?

Alongside these classic fieldbuses there are protocols for specific domains:

• Buildings - BACnet (including over RS-485), KNX, LON (LonWorks) and DALI for building automation, HVAC and lighting
• Metering - M-Bus for reading energy, water and gas meters
• Energy and utilities - DNP3 and IEC 60870-5-104 between RTUs and a control centre
• Point-to-point - IO-Link (IEC 61131-9) is not a bus; it connects one smart sensor to a master over at most 20 metres, and the master itself sits on a fieldbus or Ethernet

🔄 What is the difference between a fieldbus and industrial Ethernet?

Industrial Ethernet protocols such as ProfiNET, IP (managed by ODVA and based on CIP), EtherCAT, POWERLINK and SERCOS III are often called “Ethernet fieldbuses”. They do the same job, but over standard Ethernet hardware.

The market figures come from HMS Networks’ annual study: the share of classic fieldbuses fell from 22% in 2024 to 17% in 2025. Profibus is still the largest classic fieldbus, but ProfiNET (27%), EtherNet/IP (23%) and EtherCAT (17%) dominate new installations. In existing plants (brownfield), fieldbuses will remain in service for decades.

A common misconception: ProfiNET is not Profibus over Ethernet, but a separate protocol from the same organisation (PROFIBUS & PROFINET International). You connect Profibus devices to ProfiNET through a proxy or gateway.

🔧 How do you design a fieldbus network?

A fieldbus is more sensitive to installation errors than Ethernet. Incorrect termination and poor shielding are among the most common causes of faults. A proven approach:

1. Match the protocol to the controller and the process - Siemens environments often use Profibus/ProfiNET, Rockwell environments DeviceNet/EtherNet/IP; process plants with explosion hazards use Profibus PA or Foundation Fieldbus
2. Calculate your segments - stay within the limits in the table below, with spare capacity for expansion
3. Terminate each segment at both ends - with exactly two active terminating resistors, no more and no fewer
4. Earth and shield correctly - earth the cable shield according to the protocol’s installation guideline and route fieldbus cables away from power cables of variable frequency drives (EMC)
5. Record addresses and configuration - bus addresses, GSD/EDS files and firmware versions belong in your asset inventory and configuration management
6. Test and document - measure signal quality at handover (FAT/SAT) so you have a baseline for later troubleshooting

In the process industry, attention is shifting to Ethernet-APL: two-wire Ethernet at 10 Mbit/s (10BASE-T1L) with power over the same cable, a trunk of up to 1000 m and spurs of up to 200 m, suitable for intrinsically safe applications. It combines fieldbus-style cabling with the speed and IP addressing of Ethernet.

🔐 How secure are fieldbuses?

Classic fieldbuses were designed for availability, not for confidentiality or integrity. Profibus, Modbus RTU, CAN and Foundation Fieldbus H1 have no authentication and no encryption: anyone with physical access, or access through a gateway, can read the traffic and send commands. The old assumption that “it is on a separate cable, so it is safe” no longer holds once a fieldbus can be reached through a gateway, an engineering station or remote access.

• Treat each fieldbus segment as a zone in the zones and conduits model of IEC 62443; gateways to Ethernet are conduits
• Restrict physical access to cabinets, connectors and diagnostic ports
• Secure the layer above - network segmentation and hardening of engineering stations are often more effective than measures on the bus itself
• Monitor where you can - at Ethernet level with network monitoring; on the fieldbus with protocol analysers or Wireshark via a suitable interface
• Choose protocols with security options for new builds, such as CIP Security for EtherNet/IP or the ProfiNET security classes

Functional safety is a different subject: safety profiles such as PROFIsafe and CIP Safety (defined in IEC 61784-3) protect against transmission errors for functional safety, not against attackers. For organisations covered by the Dutch Cybersecurity Act (Cyberbeveiligingswet), fieldbuses and their gateways simply belong in the risk assessment of the OT environment.

🏭 Where are fieldbuses used?

• Discrete manufacturing - PLC to remote I/O, drives and valve terminals on production lines and packaging machines
• Process industry - chemicals, oil and gas, food and pharma with Profibus PA, Foundation Fieldbus and HART, often connected to a DCS
• Water - pumping stations and treatment plants of Dutch water boards and drinking water companies, where Profibus and Modbus are still common alongside ProfiNET
• Machine building - motion control and servo drives via CANopen, EtherCAT or SERCOS
• Buildings and energy - BACnet, KNX and M-Bus in building automation, access control and metering systems

❓ Frequently asked questions

Is Modbus a fieldbus?

Modbus RTU is a classic fieldbus: a serial protocol over RS-485 in which one master polls up to 247 slaves. Modbus TCP uses the same message format over Ethernet and therefore counts as industrial Ethernet. Neither variant has authentication or encryption by default.

What is the difference between Profibus DP and Profibus PA?

Profibus DP is fast (up to 12 Mbit/s) and runs over RS-485 in factory automation. Profibus PA runs at 31.25 kbit/s over a two-wire cable that also powers the devices and is suitable for hazardous areas. A segment coupler connects PA segments to a DP network.

Are fieldbuses obsolete?

Fieldbuses are not obsolete, but they are losing ground: in 2025, 17% of newly installed industrial network nodes were still classic fieldbus. In existing plants, fieldbuses often stay in service for twenty years or more. For new builds, most designers choose industrial Ethernet or Ethernet-APL.

Why does a fieldbus need terminating resistors?

A fieldbus running on RS-485 (such as Profibus DP or Modbus RTU) or on CAN is a transmission line on which signals reflect at the end of the cable. Terminating resistors at both ends of a segment absorb those reflections. Missing or extra terminations are among the most common causes of fieldbus faults.

Which standard describes fieldbuses?

The international standard for fieldbuses is IEC 61158, which describes the protocol types, together with IEC 61784-1 for the communication profiles. IEC 61784-3 covers functionally safe fieldbus profiles and IEC 61784-5 covers installation. In addition, most fieldbuses have a user organisation that manages specifications and certification.

Can a fieldbus be hacked?

A fieldbus can be abused, because classic protocols such as Profibus and Modbus RTU have no authentication or encryption. An attacker does need physical access or a compromised system connected to the bus, such as an engineering station or gateway. The best protection therefore lies in segmentation, physical security and securing those upstream systems.

📌 In summary

A fieldbus connects sensors, actuators and drives to the controller over a single shared, deterministic cable and forms the lowest communication layer of industrial automation. Profibus, Modbus RTU, CAN and Foundation Fieldbus still run in countless plants, but new builds are moving to industrial Ethernet and Ethernet-APL. Because classic fieldbuses have no built-in security, you protect them through zones, physical access control and well-secured gateways and engineering stations.