PROFINET Protocol

Industrial Ethernet protocol for real-time automation, motion control, and factory-floor communication over standard Ethernet infrastructure.

Type

Industrial Ethernet

Layer

2 (RT/IRT) / 3-4 (NRT)

Cycle Time

< 1 ms (IRT)

Standard

IEC 61158 / IEC 61784

What is PROFINET?

PROFINET (Process Field Net) is an industrial Ethernet protocol developed by PROFIBUS International (PI) in collaboration with Siemens. Introduced in 2004, it was designed to bring real-time communication to standard Ethernet networks in factory automation, process control, and motion applications.

PROFINET is the most widely used industrial Ethernet protocol in Europe and one of the leading protocols worldwide, with over 50 million installed nodes. It is standardized under IEC 61158 and IEC 61784, ensuring interoperability across vendors and device types.

Unlike proprietary fieldbus systems, PROFINET runs on standard Ethernet hardware and cabling (100 Mbps, Cat 5e or higher). It supports real-time (RT) and isochronous real-time (IRT) communication alongside standard TCP/IP traffic on the same physical network. This allows automation data, diagnostics, and IT traffic to coexist without requiring separate cabling.

PROFINET builds on the legacy of PROFIBUS, the dominant serial fieldbus in Europe for decades. While PROFIBUS uses RS-485 serial communication, PROFINET replaces the physical layer with Ethernet while preserving familiar concepts like device descriptions and cyclic IO exchange. Migration paths exist through PROFINET/PROFIBUS proxies that allow mixed networks during transitions.

PROFINET IO Architecture

PROFINET IO defines three device roles that work together to manage cyclic data exchange on the network. Every device on a PROFINET network fills one of these roles.

The IO Controller is typically a PLC or automation controller that manages the process. It sends output data (commands) to field devices and receives input data (measurements, status) in return. A single IO Controller can manage hundreds of IO Devices on one network.

An IO Device is any field device that exchanges process data with the IO Controller. Examples include variable frequency drives, remote IO modules, sensors, valves, and motor starters. Each IO Device is assigned a unique device name and IP address during commissioning.

The IO Supervisor is an engineering or monitoring station used for configuration, diagnostics, and commissioning. It does not participate in cyclic data exchange but can read diagnostic information, configure device parameters, and perform network analysis. Tools like Siemens TIA Portal or third-party engineering software fill this role.

Cyclic data exchange between the IO Controller and IO Devices is the core of PROFINET IO. The Controller sends outputs and receives inputs at a fixed cycle rate, typically between 1 ms and 512 ms depending on the application. This provider-consumer model ensures deterministic data delivery for time-critical control loops.

PROFINET IO ArchitectureIO Controller(PLC)Industrial Ethernet SwitchDriveIO DeviceRobotIO DeviceSensor ModuleIO DeviceValve TerminalIO DeviceIO Supervisor(Engineering Station)Real-time IO DataDiagnostics / Config
PROFINET IO architecture: the IO Controller exchanges real-time cyclic data with IO Devices over industrial Ethernet, while the IO Supervisor handles diagnostics and configuration.

PROFINET Communication Channels

One of PROFINET's key strengths is its ability to carry three distinct communication channels on the same Ethernet wire. Each channel serves a different purpose and operates at a different priority level.

RT (Real-Time) is the standard communication channel for cyclic IO data exchange. RT frames bypass the TCP/IP stack entirely, using Layer 2 Ethernet frames with a dedicated EtherType (0x8892). This achieves cycle times of 1 to 10 ms, which is sufficient for the vast majority of factory automation tasks such as reading sensors, controlling valves, and monitoring discrete IO points.

IRT (Isochronous Real-Time) provides deterministic communication with cycle times below 1 ms, down to 31.25 microseconds. IRT reserves dedicated time slots within each Ethernet cycle using time-division multiplexing. This guarantees ultra-low jitter (less than 1 microsecond), making IRT essential for synchronized motion control, multi-axis coordination, and high-speed printing or packaging machines. IRT requires special hardware support in the network switches.

NRT (Non-Real-Time) carries standard TCP/IP and UDP traffic for non-time-critical tasks. This includes device configuration, firmware updates, web-based diagnostics, SNMP network management, and general IT communication. NRT traffic uses standard IP protocols and can be routed across subnets just like any other Ethernet traffic.

PROFINET Communication ChannelsRT (Real-Time)Cyclic IO DataPROFINET RTEthernet Layer 2< 10 ms cycleIRT (Isochronous Real-Time)Motion ControlPROFINET IRTEthernet Layer 2 (reserved bandwidth)< 1 ms cycleNRT (Non-Real-Time)Diagnostics, Config, ITTCP/IP, UDP/IPEthernet Layer 2Best effortStandard Ethernet Infrastructure (100 Mbit/s or 1 Gbit/s)
PROFINET supports three communication channels on the same Ethernet network: RT for standard IO, IRT for high-precision motion control, and NRT for IT traffic and diagnostics.

PROFINET RT vs IRT

Choosing between RT and IRT depends on the application's timing requirements. Most PROFINET installations use RT exclusively. IRT is reserved for applications that demand synchronized, sub-millisecond communication.

FeatureRT (Real-Time)IRT (Isochronous RT)
Cycle Time1-10 ms< 1 ms (down to 31.25 us)
JitterLowUltra-low (< 1 us)
Use CaseStandard IO (sensors, valves)Motion control, synchronized drives
Ethernet LayerLayer 2, prioritizedLayer 2, reserved time slots
HardwareStandard switchesIRT-capable switches required
Bandwidth ReservationNoYes (time-division)

GSD Files and Device Configuration

Every PROFINET device is described by a GSD file (General Station Description). GSD files use XML format (specifically GSDML, the GSD Markup Language) and contain all the information an engineering tool needs to configure a device on the network.

A GSD file defines the device's identity (vendor name, device name, order number), its available modules and submodules, IO data structure, supported parameters, and diagnostic capabilities. When an engineer adds a device to a PROFINET project, the engineering tool reads the GSD file to present configuration options and validate the setup.

Engineering tools such as Siemens TIA Portal, STEP 7, and third-party tools like CODESYS or Phoenix Contact PLCnext Engineer import GSD files to build the network configuration. The tool assigns device names, IP addresses, and maps IO data to PLC variables. This configuration is then downloaded to the IO Controller, which uses it to establish communication with each IO Device at startup.

Device manufacturers are required to provide a GSD file for every PROFINET device they produce. These files are typically available for download from the manufacturer's website or from the PI (PROFIBUS International) GSD library.

PROFINET vs Other Industrial Protocols

PROFINET competes with several other industrial Ethernet protocols. The choice often depends on regional preferences, PLC vendor ecosystem, and specific application requirements.

FeaturePROFINETEtherNet/IPModbus TCP
DeveloperPI / SiemensODVA / RockwellModbus Organization
Real-TimeRT + IRTCIP Motion (implicit UDP)None
Min Cycle Time31.25 us (IRT)~1 ms~10 ms (polling)
TransportLayer 2 (RT/IRT) + TCP/IPTCP/UDP/IPTCP/IP
DiagnosticsBuilt-in, detailedCIP diagnosticsLimited
MarketDominant in EuropeDominant in North AmericaUniversal, simple

Common Use Cases

PROFINET is used across a wide range of industries and applications, from discrete manufacturing to process automation.

  • Automotive manufacturing: robot control, synchronized conveyor systems, and body-in-white welding lines where precise timing between stations is critical.
  • Packaging machines: high-speed filling, labeling, and sealing systems that require coordinated motion across multiple axes.
  • Printing presses: register control and color synchronization across print heads, demanding sub-millisecond accuracy with IRT.
  • CNC machine tools: spindle control, tool changers, and axis interpolation where deterministic communication ensures machining precision.
  • Process automation: chemical plants, water treatment, and food/beverage production, often combined with PROFIsafe for safety-critical functions like emergency stops and safety interlocks.
  • Motion control applications: multi-axis servo systems, flying shears, and electronic gearing where IRT provides the jitter-free synchronization that mechanical linkages once delivered.

Frequently Asked Questions About PROFINET

What is the difference between PROFINET and PROFIBUS?

PROFIBUS is a serial fieldbus protocol that runs over RS-485 wiring at speeds up to 12 Mbps. PROFINET is its Ethernet-based successor, running at 100 Mbps or faster over standard Ethernet cabling. PROFINET supports simultaneous real-time and IT communication on the same wire, offers faster cycle times, and integrates natively with TCP/IP networks. Many facilities run both protocols side by side using PROFINET/PROFIBUS proxies during migration.

Does PROFINET work with standard Ethernet switches?

For RT (Real-Time) communication, yes. PROFINET RT uses prioritized Layer 2 Ethernet frames that work with any managed switch supporting IEEE 802.1Q VLAN tagging and priority queuing. However, IRT (Isochronous Real-Time) requires special IRT-capable switches with hardware support for time-slot scheduling. Standard unmanaged switches are not recommended for any PROFINET deployment because they cannot prioritize real-time traffic.

What is PROFINET IRT used for?

IRT is used for applications requiring deterministic, sub-millisecond communication with ultra-low jitter. Typical use cases include synchronized multi-axis motion control (servo drives, robotics), high-speed packaging machines, printing presses with register control, and any application where precise timing between devices is essential. If your application only needs cycle times of 1 ms or longer, standard RT is usually sufficient.

Can PROFINET and IT traffic share the same network?

Yes, this is one of PROFINET's core design principles. RT and IRT frames coexist with standard TCP/IP traffic on the same physical network. Real-time frames are prioritized at Layer 2, so they are delivered before lower-priority IT traffic. In IRT networks, reserved time slots ensure that real-time data is never delayed by other traffic. Proper network design with managed switches and VLAN segmentation is recommended to maintain performance.

Is PROFINET only for Siemens PLCs?

No. While Siemens was a primary developer of PROFINET and it is the native protocol for Siemens S7-1200 and S7-1500 PLCs, PROFINET is an open standard managed by PROFIBUS International (PI). Over 60 vendors produce PROFINET-compatible devices, including ABB, Phoenix Contact, Beckhoff, Turck, Weidmuller, and many others. Any certified PROFINET device can communicate with any certified IO Controller regardless of vendor.

What is PROFIsafe?

PROFIsafe is a safety communication profile that runs on top of PROFINET (and PROFIBUS). It enables safety-related communication up to SIL 3 (IEC 61508) and Performance Level e (ISO 13849) using the same network infrastructure as standard automation data. PROFIsafe adds a safety layer with CRC checks, sequence numbers, and watchdog timers to detect communication errors. This eliminates the need for dedicated safety wiring, reducing cost and complexity in machines with emergency stops, light curtains, and safety interlocks.

Related Protocols

  • EtherNet/IP: industrial Ethernet protocol based on CIP, dominant in North American automation.
  • Modbus TCP: simple, widely supported industrial Ethernet protocol for register-based communication.
  • Modbus RTU: serial fieldbus protocol for RS-485 industrial networks.
  • TCP: the reliable transport protocol underlying PROFINET's NRT communication channel.