PROFINET is an open industrial Ethernet standard, maintained by PROFIBUS & PROFINET International (PI), that carries real-time I/O data and normal TCP/IP traffic over the same cabling. PI reports that the installed base reached 89.2 million nodes at the end of 2025, with 10.4 million new nodes added during the year, and HMS Networks estimates it took 30% of new industrial Ethernet nodes worldwide in 2025. If you work with Siemens controllers, you will meet it on almost every machine.
What is PROFINET, in one paragraph?
PROFINET is an industrial communication standard that uses ordinary Ethernet hardware (RJ45 or M12 connectors, switches, copper or fibre) and adds the timing and diagnostic behaviour that automation needs. A controller (an IO-Controller, usually a PLC) exchanges cyclic process data with field devices (IO-Devices such as remote I/O, drives and valve terminals), while configuration, web pages and IT protocols share the same wire. PI describes it as the leading industrial Ethernet standard, supported by many vendors, which is why a drive from one manufacturer can usually be commissioned from a PLC made by another.
According to PI's annual node count for 2025, the technology is still growing: the installed base rose to 89.2 million nodes, and PI links that growth to end-to-end data communication, IO-Link integration and the move to Gigabit networks.
How fast is it? RT, IRT and TSN compared
PROFINET offers several real-time options so that a simple conveyor and a multi-axis printing press can use the same standard. The figures below are the commonly published ranges; always check the data sheet for the devices you are actually using.
| Option | Typical cycle time | Typical use | Notes |
|---|---|---|---|
| TCP/IP (non-real-time) | Not deterministic | Diagnostics, web server, engineering tools | Shares the wire with real-time traffic |
| RT (Real-Time) | About 1 to 10 ms | Most factory I/O, remote I/O, valve terminals | Runs on standard switches with prioritisation (Wikipedia) |
| IRT (Isochronous Real-Time) | Below 1 ms | Synchronised drives and motion | Needs IRT-capable devices and switches |
| PROFINET over TSN | Deterministic, sub-millisecond | Converged IT/OT networks | Specification V2.4 integrates TSN; needs TSN-capable hardware |
PI states that mechanisms added in specification V2.3 (Fast Forwarding, Dynamic Frame Packing and Fragmentation) allow cycle times down to 31.25 microseconds while standard data travels in parallel. For most machines you will never get near that; typical cyclic update times in a TIA Portal project are in the millisecond range.
PI also published PROFINET V2.5, which it describes as adding "security inside", certificate management and a transport channel for parameterisation and firmware updates, while keeping backward compatibility with existing systems.
PROFINET or PROFIBUS: what changed?
PROFINET replaces the serial PROFIBUS cable with Ethernet, so bandwidth, device count and diagnostics all improve. PROFIBUS runs at up to 12 Mbit/s over RS-485, while PROFINET devices normally connect at 100 Mbit/s, and Gigabit is now spreading. Engineering looks familiar: each device is described by a GSD file (written in the XML-based GSDML language), which the engineering tool uses to build the configuration.
PROFIBUS is not gone. PI reported about 1 million new PROFIBUS devices in 2025 and a total of 71 million, with new installations declining as Ethernet-APL takes over process plants. Expect to maintain old PROFIBUS lines for years, usually behind a gateway to PROFINET.
What are the PROFINET conformance classes?
Conformance classes (CC-A to CC-D) describe how demanding the network and devices are. According to the PROFINET article on Wikipedia, CC-A certifies the devices only, so structured cabling or wireless can be used; CC-B also requires certified network infrastructure and adds network diagnostics and topology detection; CC-C adds IRT for positioning and motion; CC-D extends this to TSN. Most general factory automation sits in CC-A or CC-B.
How do you design a reliable PROFINET network?
Good PROFINET design is mostly good Ethernet design: plan the topology, protect real-time traffic and document everything.
- Pick a topology deliberately. Line topology is cheapest because many IO-Devices have two ports, but one cable break splits the line. Star topology isolates faults. Ring topology adds resilience.
- Use a ring with Media Redundancy Protocol (MRP) where uptime matters. MRP provides a ring with a switching time below 50 ms, which is often sufficient for standard real-time communication, according to Wikipedia's PROFINET article.
- Use managed switches and industrial-grade cabling. Managed switches give you port statistics, topology information and the option of prioritisation. Use shielded cable and proper strain relief, and keep it away from drive output cables.
- Segregate networks. Keep the machine network separate from the office network and cross between them through a firewall or a controlled gateway, not a flat switch. PI's TSN pages explain the underlying reason: large standard TCP/IP packets, such as a virus scan on a PC, can delay real-time frames on a congested path.
- Plan addressing and names up front. PROFINET devices are normally identified by a device name that the controller assigns to an IP address at start-up using the Discovery and basic Configuration Protocol (DCP). A device with the wrong name will not join the system even if the IP address looks right.
- Document it. Keep a network drawing, a list of device names and IP addresses, and switch configuration backups with the project.
How do you troubleshoot a PROFINET fault?
Start with the diagnostics the system already gives you, then move to the physical layer. PI claims that the consistent diagnostics of the standard can reduce downtime by up to 50%; treat that as a vendor-association claim rather than a guarantee, but the diagnostic data really is rich.
- Check what the controller reports. In TIA Portal the online and diagnostics view shows which station has failed and why (for example a missing device name or a module mismatch).
- Device not found. Compare the device name stored in the device with the name in the project. A replaced device often comes back with a blank name.
- Intermittent dropouts. Suspect cabling first: damaged connectors, kinked cable, poor shield termination or a port negotiating at the wrong speed.
- Slow or jittery response. Look for network load from a non-PROFINET device, a broadcast storm, or an unmanaged switch added into the middle of a line.
- Still stuck? Capture traffic with Wireshark on a mirror port. It decodes PROFINET frames and shows what is actually on the wire.
You can rehearse several of these on a laptop without hardware. The free PROFINET industrial Ethernet course from EDWartens covers the fundamentals.
Is PROFINET secure?
Not automatically; security is a design task. PI says specification V2.5 adds "security inside", scalable security mechanisms and certificate management, but plants running older devices need network-level protection as well. Practical steps are the same as for any OT network: segment the machine network, restrict who can reach engineering ports, disable unused services on devices, keep device firmware current and back up configurations. HMS Networks reported that cybersecurity is now cited by nearly half of respondents as a top integration challenge, so expect questions about it in interviews and design reviews.
What should you practise first?
Work through a small project end to end. Build a controller with two or three IO-Devices in your engineering tool, import the GSD files, give each device a unique name, assign IP addresses, download, and confirm every device reports healthy. Then break things on purpose: unplug a cable, rename a device, duplicate an address, and read what the diagnostics say each time. Recognising the symptom of each fault is the quickest way to become fast at fault-finding on a live plant.
How EDWartens can help
The EDWartens UK Professional Module is a five-day live online class in Siemens TIA Portal, covering PLC hardware, ladder logic, HMI and WinCC SCADA, followed by self-paced Basic Engineering that includes industrial communication protocols. It is delivered online with simulation tools rather than a physical rig, so hands-on network work on real switches is something you would add separately. The CPD certificate (recording 80 hours of learning) is not a regulated qualification. You can also practise first in the free browser simulators and see the wider training overview. To compare protocols, read our PROFINET vs EtherNet/IP comparison.




