Industrial networking and IT/OT service

PROFINET and PROFIBUS Communication and Fault Analysis

We investigate intermittent dropouts between PLCs, remote I/O and drives using device diagnostic logs, port counters and the field topology. We assess the devices and physical connections used for PROFINET and PROFIBUS separately.

Your situation

What problem does this service solve?

Intermittent “device not found” / station faults

Remote I/O or a drive disappears for a few seconds, the line stops and then recovers on its own. Possible causes to check: the physical layer (cable, connector, grounding), network load and configuration inconsistency. We verify each one separately with port counters and device diagnostic logs.

No communication after a device replacement

In PROFINET, communication is not established if no device name has been assigned to the new module, if the GSDML version differs from the one in the project, or if the topology definition does not match. In PROFIBUS, the same check is done for the station address, GSD file and baud rate.

PROFINET traffic on the same network as office/data traffic

When control traffic shares the same links with high-volume data, camera or backup traffic, the risk of latency and loss increases; the station’s communication may be cut off.

Unclear faults in old PROFIBUS segments

Termination resistors, segment length, shielding and connector quality may have deteriorated through additions over the years. The documentation is often out of date.

Technical framework

What we cover, and within what limits

PROFINET is an industrial communication protocol defined by PI (PROFIBUS & PROFINET International) that runs on standard Ethernet infrastructure. Cyclic I/O data is carried over the real-time (RT) channel, which bypasses the TCP/IP stack. IRT (isochronous real-time) provides time-scheduled communication with devices and switches that have hardware support. TSN (Time-Sensitive Networking) based PROFINET is a separate infrastructure option that requires TSN-capable controllers, devices and switches; it is not a setting that can be switched on later in an existing PROFINET device. We do not assume RT, IRT or TSN is automatically present in every installation. Which level is needed is determined by the application’s cycle time and synchronisation requirements, and which can be used by the support of the devices on site. PROFIBUS DP, on the other hand, is an RS-485-based serial fieldbus. Its station address, GSD file, baud rate, segment and termination rules are separate from PROFINET’s device name, IP and GSDML scheme.

Technical scope

Topology and device inventory

IO controllers, IO devices, switches and port connections are mapped; the topology in the engineering project is compared one by one with the physical connections on site.

PROFINET device name, IP and GSDML consistency

Device name (NameOfStation), IP address, GSDML version and firmware are recorded; the device replacement procedure is put in writing.

Diagnostics and measurement

Dropout moments are analysed using port statistics, the PLC’s diagnostic buffer and traffic capture from a suitable point (port mirroring or TAP). Mirroring and TAP installation are planned separately.

Redundancy and network load

Redundancy configuration such as MRP and ring manager/client roles are checked; other traffic entering the control network is separated out.

PROFIBUS segment check

Station addresses, GSD files, baud rate, segment length, termination, repeaters and connectors are checked; the physical layer is examined with suitable measurement tools.

Improvement and documentation

A prioritised list of fixes, planned implementation, then a repeat of the same measurement.

PROFINET RT, IRT and TSN: what to discuss when?

The comparison is conceptual. Which communication class is used in a project is determined by the application’s requirements and the support stated in the devices’ official documentation.

Communication typeTypical usePrerequisite
PROFINET RTThe vast majority of cyclic data exchange with remote I/O, drives and HMIsPROFINET-capable devices and properly configured Ethernet infrastructure
PROFINET IRTApplications requiring isochronous and tight timing, such as multi-axis motion controlThe application’s isochronous operation requirement; IRT-capable controllers, devices and switches; time-scheduled topology configuration
PROFINET over TSNPROFINET using IEEE TSN mechanisms; not a setting that can be enabled on an existing RT or IRT deviceTSN-capable controllers, devices and switches; support must be verified in the manufacturer’s documentation
PROFIBUS DPRemote I/O and drive communication in existing plantsRS-485 physical layer rules, termination and segment length

Prerequisites: what we need to get started

We list missing information and access together in the first meeting and complete them during the survey.

  • An up-to-date copy of the PLC/engineering project (e.g. TIA Portal) or support from the project owner
  • HMI/PLC alarm logs showing fault times
  • Physical access to critical stations and permission to measure inside cabinets
  • A managed switch that supports port mirroring, or a point where a TAP can be installed
  • The automation lead available during measurements

Deliverables

Up-to-date PROFINET/PROFIBUS topology diagram

PROFINET device name, IP, GSDML and firmware; PROFIBUS station address and GSD inventory

Fault analysis report based on measurement data

Prioritised list of fixes

Device replacement and name assignment procedure

Verification measurements after the fixes

Sample scenario

Representative scenario: an ET200SP station that drops several times per shift

The line reports a “station failure” at irregular intervals during the shift. When alarm times, the counters of the port the station is connected to and a passive traffic capture are placed side by side, it may turn out that CRC errors on the same port coincide with the dropout moments. This finding makes the physical layer the first thing to check: connector, cable route, grounding. The port’s speed/duplex setting is verified in the same check. The fix is carried out during planned downtime, the counters are reset and the same measurement is repeated for a week.

This is a representative fault analysis flow; it is not a real customer case.

Service summary

Related services

Industrial Ethernet and Factory Networks

We map switches, cables and connected devices from machine cabinets to the plant backbone.

View details →

Scope limit

We do not write or modify the PLC application program. Hardware configuration changes are made with the project owner’s approval, together with the automation lead. The conditions of the official authorised service must be verified separately for the manufacturer’s warranty and support coverage.

Project approach

How do we proceed?

No step that touches production is carried out until the maintenance window, configuration backup and rollback plan are clear.

01 / STAGE

Symptom analysis

Alarm times, affected stations and the recurrence pattern are identified.

02 / STAGE

Measurement

Data is collected with port counters, diagnostic logs and traffic capture.

03 / STAGE

Root cause

The physical layer, configuration, network load and topology are separated out.

04 / STAGE

Remediation

Prioritised changes are applied in a planned window, with a rollback plan.

STAGE 05

Verification

The same measurements are repeated; the result and remaining risks are reported.

Frequently asked questions

Questions about PROFINET and PROFIBUS Communication

01

Is PROFINET the same as regular Ethernet?

No. PROFINET is a protocol that runs on Ethernet infrastructure and is designed for the real-time communication needs of industrial automation. The same cables and connectors can be used. But not every switch, topology and network load is suitable for every PROFINET application.

02

Does every PROFINET installation support IRT or TSN?

No. Most applications run on PROFINET RT. IRT and TSN require the controller, devices and switches to support these features and be configured accordingly; support is verified from the device documentation.

03

How long does it take you to find the cause of intermittent dropouts?

It depends on how often the fault occurs and on measurement access. For a frequently recurring fault, a short measurement window may be enough; for a rare fault, traffic capture may need to stay on for several days. We do not guarantee results; we apply a measurement-based method.

04

Is migrating from PROFIBUS to PROFINET mandatory?

No. A healthy PROFIBUS segment can be kept. If device support allows, existing PROFIBUS devices can be represented on the PROFINET side through a proxy, and a gradual migration can be planned. The decision is driven by spare parts availability and the line’s investment plan together.

Technical survey

Let's plan a technical survey for PROFINET and PROFIBUS communication

Briefly describe your line, your PLC and network equipment and your goal. We will respond with a written proposal covering scope, assumptions and deliverables.