PROFINET - Industrial Ethernet for Real-Time Automation

PROFINET is the Industrial Ethernet protocol strongly associated with Siemens automation, though it is an open standard maintained by PI (PROFIBUS and PROFINET International). It is used for PLCs, distributed I/O, drives, HMIs, safety devices, and motion systems.

The important idea is that PROFINET uses Ethernet, but it is not just "normal office Ethernet with PLC tags." It adds device descriptions, cyclic real-time I/O, diagnostics, topology awareness, and engineering integration.

Learning Objectives

By the end of this lesson, you should be able to:

Explain the difference between standard Ethernet traffic and PROFINET real-time traffic.
Identify IO controller, IO device, and IO supervisor roles.
Understand cyclic process data and acyclic engineering data.
Recognize GSDML files and device names.
Compare PROFINET with PROFIBUS and EtherNet/IP.
Troubleshoot common commissioning problems.

PROFINET Roles

flowchart LR classDef ctrl fill:#dbeafe,stroke:#2563eb,color:#1e3a5f classDef dev fill:#dcfce7,stroke:#16a34a,color:#14532d classDef sup fill:#fef9c3,stroke:#ca8a04,color:#713f12 classDef net fill:#fee2e2,stroke:#dc2626,color:#7f1d1d PLC["IO Controller\nPLC"]:::ctrl SW["Industrial Ethernet switch"]:::net RIO["IO Device\nRemote I/O"]:::dev VFD["IO Device\nDrive"]:::dev HMI["IO Supervisor\nEngineering / HMI"]:::sup PLC <--> SW SW <--> RIO SW <--> VFD HMI <--> SW

Role	Meaning
IO Controller	PLC that owns cyclic I/O exchange
IO Device	Remote I/O, drive, valve island, scanner, or module
IO Supervisor	Engineering station or diagnostic tool

Cyclic and Acyclic Data

PROFINET separates fast process data from slower configuration and diagnostic data.

Data type	Purpose	Example
Cyclic I/O	Repeated real-time process exchange	16 input bytes from remote I/O every 4 ms
Acyclic data	Parameters, diagnostics, records	Read drive fault code or set parameter
Alarms	Event notification	Module removed, short circuit, device fault

sequenceDiagram participant PLC as IO Controller participant IO as IO Device loop Every update cycle PLC->>IO: Output process data IO-->>PLC: Input process data end PLC->>IO: Acyclic read record - diagnostics IO-->>PLC: Fault record and status

Real-Time Classes

PROFINET supports several communication styles:

Class	Use	Notes
TCP/IP	Engineering and non-real-time services	Uses normal IP stack
RT	Real-time cyclic I/O	Common factory automation
IRT	Isochronous real-time	Motion control with tight timing

Most machine I/O uses PROFINET RT. High-end coordinated motion may use IRT with special network planning and capable switches/devices.

Device Names, IP Addresses, and GSDML

PROFINET commissioning depends on three things:

Item	Purpose
Device name	Logical identity assigned by engineering tool
IP address	Network address, often assigned during commissioning
GSDML file	XML device description containing modules, slots, subslots, and diagnostics

A common beginner mistake is setting the IP address correctly but leaving the PROFINET device name wrong. The PLC configuration expects a specific name; if the physical device has a different name, it will not connect as the intended IO device.

Startup and Discovery

During commissioning, an engineering tool normally discovers devices with PROFINET discovery services, assigns each device name, and then downloads the expected hardware configuration to the PLC. At runtime, the IO controller looks for configured device names and establishes application relationships with matching IO devices.

sequenceDiagram participant ENG as Engineering Tool participant DEV as IO Device participant PLC as IO Controller ENG->>DEV: Discover device on Ethernet ENG->>DEV: Assign PROFINET device name ENG->>PLC: Download hardware configuration PLC->>DEV: Connect using expected name DEV-->>PLC: Cyclic I/O ready or diagnostic fault

This explains why "I can ping it" is not enough. IP reachability proves Layer 3 connectivity; PROFINET operation also needs the configured name, module layout, subslot identity, and real-time communication setup to match.

Worked Example - Remote I/O Update Time

A PLC reads 32 digital inputs and writes 16 digital outputs through a PROFINET remote I/O station every 4 ms.

Input process data  = 32 bits = 4 bytes
Output process data = 16 bits = 2 bytes
Update time         = 4 ms
Updates per second  = 1 / 0.004 = 250 updates/s

The payload is small, but the real requirement is not bandwidth. It is predictable update timing and clear diagnostics when the station or module fails.

Engineering Rule - Update Time vs PLC Load

The fastest possible update time is not always the best choice. A practical estimate starts with the number of devices and their update periods.

Total cyclic exchanges per second = sum(1 / update_time for each device)

If a cell has 20 devices at 4 ms:

Exchanges per second = 20 x (1 / 0.004 s) = 5000 exchanges/s

That may still be reasonable on a capable controller, but it is a controller-load and switch-design question, not just an Ethernet bandwidth question. Slower sensors should not be configured with motion-class update rates.

PROFINET vs PROFIBUS

Feature	PROFINET	PROFIBUS DP
Physical layer	Ethernet	RS-485 fieldbus
Topology	Star, line, ring with switches	Bus line
Speed	100 Mbit/s typical	Up to 12 Mbit/s
Device description	GSDML	GSD
Diagnostics	Rich, topology-aware	Strong but bus-oriented
Best for	Modern Ethernet automation	Legacy and robust fieldbus systems

Practical Checks

Confirm the device name exactly matches the PLC hardware configuration.
Install the correct GSDML file for the device revision.
Check switch support for LLDP, VLAN/QoS, MRP, and IRT if required.
Keep office IT traffic away from time-critical machine networks.
Verify update times against device and PLC capability.
Use diagnostics to identify slot, subslot, and module faults.
Confirm the configured module order matches the physical station exactly.
Keep a record of device names before replacing hardware.

Common Mistakes

Treating PROFINET as just TCP/IP polling.
Setting only the IP address and forgetting the PROFINET device name.
Using unmanaged office switches in a time-critical cell.
Mixing firmware/device revisions without the correct GSDML file.
Choosing very fast update times without checking PLC load.
Ignoring shield bonding and industrial Ethernet cabling quality.
Replacing a device and assigning only the old IP address, not the old PROFINET name.

Summary

PROFINET brings Ethernet into real-time industrial control. It keeps normal IP services where useful, but adds cyclic I/O, device descriptions, engineering integration, alarms, diagnostics, and optional isochronous timing. For technicians, the most common commissioning checks are device name, IP address, GSDML file, update time, and network topology.

Mind Map

mindmap root((PROFINET)) Core concept Industrial Ethernet Cyclic real-time I/O Device diagnostics Applications PLC remote I/O Drives Motion Safety systems Calculations Update time ms Updates/s = 1/T Total cycles = sum 1/T I/O bytes per cycle Design rules Match device name Use correct GSDML Plan switches Match modules Practical checks IP and name Slot diagnostics Update load Common mistakes Office switch misuse Wrong GSDML Too-fast cycle