Industrial Networks & Fieldbus

Industrial Networks & Fieldbus: Engineering Guide

Industrial networks and fieldbus systems are the communication backbone of modern automation. They connect PLCs, remote I/O, drives, safety devices, HMIs, SCADA gateways, analyzers, and smart instruments over deterministic or near-deterministic links so that control, diagnostics, and asset data can move reliably across the plant. In practice, “fieldbus” often refers to device-level industrial communication such as PROFIBUS, Modbus RTU, CANopen, DeviceNet, AS-Interface, FOUNDATION Fieldbus, and HART, while “industrial Ethernet” covers PROFINET, EtherNet/IP, EtherCAT, Modbus TCP, POWERLINK, and similar protocols.

What it is and how it works

An industrial network replaces point-to-point hardwiring for signals that can be multiplexed digitally. Instead of running a separate pair for every analog or discrete point, devices share a common medium and exchange framed data according to a protocol. Architecturally, the network usually has three layers:

• Physical layer: copper, fiber, wireless, connectors, shielding, and signaling.
• Data link / protocol layer: addressing, arbitration, retries, cyclic I/O, and diagnostics.
• Application layer: process data objects, device parameters, alarms, time sync, and safety data.

In cyclic control traffic, the PLC or controller polls devices or exchanges scheduled frames at fixed intervals. For example, PROFINET RT, EtherNet/IP implicit messaging, and EtherCAT all support fast cyclic data exchange. Determinism matters because the control loop must meet a bounded update time. For a remote I/O island with 32 digital inputs and 16 outputs, a 10 ms update can be more than adequate; for servo motion, sub-millisecond performance may be required.

Main vendor families engineers should know

Engineers should be familiar with both protocol ecosystems and the product families that dominate real projects.

Vendor	Product families / examples	Typical use
Siemens	SIMATIC S7-1200/1500, ET 200SP, SCALANCE X switches, SINAMICS drives, CM/CP communication modules	PROFINET, PROFIBUS, industrial Ethernet, distributed I/O
Rockwell Automation	ControlLogix, CompactLogix, POINT I/O, FLEX 5000, Stratix switches, PowerFlex drives	EtherNet/IP, DeviceNet legacy, CIP Safety
Beckhoff	CX controllers, EK/EJ EtherCAT couplers, EL terminal series, TwinSAFE	EtherCAT, distributed I/O, high-speed motion
Schneider Electric	Modicon M340/M580, Advantys, Altivar drives, ConneXium switches	Modbus TCP, EtherNet/IP, legacy Modbus RTU
WAGO	750/753 I/O, PFC controllers, industrial edge gateways	Modbus TCP, PROFINET, EtherNet/IP, field wiring density
HMS Networks	Anybus gateways, IXXAT interfaces, Ewon remote access	Protocol conversion, remote connectivity, legacy integration
Phoenix Contact	Axioline, PLCnext, FL SWITCH, mGuard	Open automation, segmentation, cybersecurity, remote I/O
Endress+Hauser / Emerson / Yokogawa	Field instruments with HART, FOUNDATION Fieldbus, PROFIBUS PA, Ethernet-APL offerings	Process instrumentation and asset diagnostics

Selection criteria and concrete sizing rules

Selection starts with the control problem, not the protocol brand. Key criteria are update time, device count, topology, distance, EMC environment, safety needs, vendor lock-in, and lifecycle support.

Rule 1: Size bandwidth from payload and update rate

Estimate cyclic data load using:

$$B \approx \frac{N \cdot (D_{in}+D_{out}) \cdot 8}{T_u}$$

where $N$ is the number of devices, $D_{in}$ and $D_{out}$ are bytes per device per cycle, and $T_u$ is update time in seconds.

Example: 24 remote I/O nodes each exchange 12 bytes in and 8 bytes out every 10 ms.

$$B \approx \frac{24 \cdot (12+8)\cdot 8}{0.01} = 384{,}000\ \text{bit/s} \approx 0.384\ \text{Mbit/s}$$

This is only the cyclic payload. In real systems, protocol overhead, retries, diagnostics, and bursts can multiply the requirement by 3 to 10. A practical engineering margin is to keep average network loading below 30% to 40% of nominal capacity for Ethernet-based control networks and below 20% for legacy serial fieldbus.

Rule 2: Size cable length from topology and speed

For 100BASE-TX industrial Ethernet, a copper segment is typically limited to 100 m per ISO/IEC 11801 and TIA-style structured cabling practice. For RS-485 fieldbus, the allowable distance depends on baud rate, cable type, and termination. A common engineering approximation for PROFIBUS DP is that higher baud rates require shorter segments; always confirm with the vendor’s cable table and the actual repeater count.

Example: A skid has a PLC, one managed switch, and six devices spread over 80 m. Use copper Ethernet if the environment allows it; if the skid is in a high-EMI area or crosses buildings, fiber is preferred for galvanic isolation and lightning immunity.

Rule 3: For analog process buses, calculate segment current

FOUNDATION Fieldbus H1 and PROFIBUS PA are powered fieldbuses. A segment must supply all device currents while keeping voltage above the minimum device requirement.

$$I_{seg} = \sum I_i + I_{margin}$$

Example: Eight transmitters draw 14 mA each and the segment coupler provides 20 mA margin.

$$I_{seg} = 8 \cdot 14 + 20 = 132\ \text{mA}$$

If the power conditioner is rated for 500 mA, current is acceptable, but voltage drop along trunk and spurs must still be checked. In practice, segment design tools from vendors are used to verify spur length, trunk length, and intrinsic safety barriers where applicable.

Rule 4: Reserve headroom for growth

For new projects, specify at least 20% spare device capacity, 25% spare bandwidth, and 1 unused switch port per cabinet section or field junction point. For SCADA integration, reserve an extra protocol gateway or spare virtual machine capacity if the plant will later expose data to MES, historians, or cloud platforms.

Where it fits in automation, panels, SCADA, and contracting

Industrial networks sit between field devices and control layers. In a panel, they reduce terminal count, simplify marshalling, and enable diagnostics. In PLC and SCADA projects, they carry process data, alarms, timestamps, and asset status to controllers, historians, and operator stations. In EPC and contracting work, the network scope includes cable schedules, cabinet layout, switch selection, IP plan, grounding, EMC measures, FAT/SAT test cases, and cybersecurity zoning.

For system integrators, the network architecture often determines commissioning effort. A well-designed remote I/O network can cut cabinet wiring significantly, but a poorly designed one can create difficult faults, hidden latency, and vendor-dependent troubleshooting.

Applicable standards and clauses

• IEC 61158: Industrial communication networks – Fieldbus specifications; protocol families and communication profiles.
• IEC 61784-1: Communication profile families; defines CPF mappings and conformance concepts.
• IEC 61784-2: Additional profiles for real-time Ethernet and fieldbus use cases.
• IEC 61784-3: Functional safety communication profiles; relevant for PROFIsafe, CIP Safety, FSoE.
• IEC 62443-3-2: Risk assessment and security zoning for industrial automation and control systems.
• IEC 60204-1, clause 13: Control equipment wiring practices and conductor identification.
• IEC 61000-6-2 and IEC 61000-6-4: Immunity and emission requirements for industrial environments.
• EN 50170: Historic fieldbus framework widely referenced for PROFIBUS installations.
• NFPA 79, section 12: Industrial machinery wiring methods and communication circuits in North American projects.
• ANSI/TIA-568: Structured cabling practices where Ethernet infrastructure is used.

For CE-marked machinery, network design is not isolated from the overall conformity assessment. Under the Machinery Directive practice and the newer EU Machinery Regulation transition, communication systems that affect safety functions, diagnostics, or remote access should be included in the technical file and risk assessment. Cybersecurity is increasingly relevant under EU NIS2 expectations for essential and important entities.

Installation considerations: wiring, EMC, segregation, thermal

Wiring and topology

• Use the protocol-approved cable type and connector system.
• Terminate RS-485 and similar buses correctly at both ends only.
• Do not create star topologies on protocols that require line or ring discipline unless the vendor explicitly supports it.
• Label device addresses, port numbers, and cable IDs consistently with the loop drawings.

EMC and segregation

• Separate data cables from VFD output cables, contactor circuits, and transformer primaries.
• Cross power and data at 90 degrees where unavoidable.
• Bond shield terminations according to the vendor’s EMC scheme; for high-frequency industrial Ethernet, 360-degree shield termination at the connector is usually preferred.
• Use fiber where lightning, long distances, or severe ground potential differences exist.

Thermal and cabinet layout

Managed switches, gateways, and industrial firewalls dissipate heat. A compact cabinet with multiple PoE switches can exceed thermal limits quickly. Estimate heat load as the sum of device losses:

$$P_{total} = \sum P_i$$

If four devices each dissipate 8 W, then:

$$P_{total} = 4 \cdot 8 = 32\ \text{W}$$

Ensure the enclosure ventilation and ambient temperature rating can handle the load with margin. Place active network gear away from the hottest zone near drives and transformer compartments.

Copy-ready project specifications table

Item	Specification
Protocol	PROFINET / EtherNet/IP / Modbus TCP / EtherCAT / PROFIBUS DP / FOUNDATION Fieldbus H1
Topology	Line, star via managed switch, ring with redundancy, or segment-based fieldbus as approved by vendor
Update time	Target cyclic I/O update < 10 ms for standard discrete control; < 1 ms for motion where required
Bandwidth margin	Average load ≤ 40% of link capacity; design spare capacity ≥ 25%
Cable	Industrial-rated Cat5e/Cat6 or protocol-approved shielded pair; fiber for long distance/high EMI
EMC	Comply with IEC 61000-6-2 immunity and IEC 61000-6-4 emissions for industrial installations
Segregation	Separate from VFD output cables; maintain physical segregation per panel wiring practice
Grounding/shielding	Single-point or multi-point shield strategy per protocol and EMC design; 360-degree termination for Ethernet connectors
Cybersecurity	Network zoning, firewalling, remote access control, least privilege, asset inventory per IEC 62443-3-2
Documentation	IP plan, node list, cable schedule, topology drawing, FAT/SAT test plan, backup and restore procedure

Industrial networks are not just “communications”; they are a design discipline that affects control performance, maintainability, compliance, and lifecycle cost. The best projects treat them as an engineered subsystem with clear protocol choice, quantified sizing, EMC-aware installation, and standards-based documentation from the start.