Common causes of PROFINET problems

Contents

First establish what is actually being lost

Loss of an input/output (I/O) station can result from the network connection, but also from a device power failure or incorrect configuration. Record the event time, plant operating conditions and affected area: one module, all devices downstream of a port, or the entire network. Compare the PLC diagnostic buffer, device alarms and switch events. A message on the operator panel (HMI) alone does not identify the cause.

A ping response establishes only IP reachability at the time of the test. PROFINET real-time (RT) cyclic communication uses Ethernet frames directly, bypassing TCP/IP. IP services can remain available while I/O data exchange is interrupted or unstable.

Device name, IP address and configuration need separate checks

The PROFINET device name, or NameOfStation, must match the project. The controller uses it to identify the device and can assign the configured IP address. Check duplicate names and addresses, the subnet mask and assignment to the correct IO Controller. Setting an IP address alone does not replace assigning the correct device name.

DCP provides device discovery and basic configuration within the local Layer 2 network; it is not IP-routable. Before writing a name or address, confirm the device identity, for example using its MAC address and cabinet designation. Visibility in a tool does not establish that settings can safely be changed during production.

Also verify the device type, supported GSDML device description file version, module and submodule configuration, and firmware compatibility with the project. After replacing a device, do not assume that identical connectors imply an identical configuration.

Port and topology diagnostics

  • Compare the actual port-to-port connections with the documentation and configured topology. Include switches integrated into devices as well as separate switches.
  • Read link-loss events, negotiated speed and duplex mode, and the available frame checksum error (CRC/FCS) and discarded-frame counters. Evaluate increases over a defined period rather than totals since startup.
  • Correlate the results with cable movement, drive operation, network load and device power status. A counter is a diagnostic clue, not proof of a particular fault on its own.
  • Check cables and connectors using an appropriate measurement method. An illuminated link LED does not establish the quality of the complete transmission path.

LLDP describes neighbouring devices and ports. It does not replace cable testing. An incomplete map may result from an intermediate device lacking LLDP support. Automatic device naming after replacement also depends on support for that function and agreement between the actual and configured topology.

Assess shielding and equipotential bonding together

Check shield termination in connectors, cable routing relative to power circuits, and the plant's equipotential bonding. A data cable shield does not replace an equipotential bonding conductor. Disconnecting a shield as a temporary response to errors can reduce interference immunity.

There is no single separation distance from motor cables or earthing modification suitable for every installation. The solution depends on cable types, shielding, routing and equipment instructions. Changes to protective earthing and equipotential bonding require assessment by appropriately qualified personnel.

Communication timing and confirmation of the repair

Compare the I/O update time and communication monitoring settings with the project, topology and process requirements. Increasing the monitoring time can mask data loss but will not repair a cable or an overloaded port. Parameter changes require assessment of the effects on machine responses and safety functions.

Also check peak network load and discarded frames at relevant points. Collect data over representative production cycles, including traffic other than PROFINET. After the repair, compare alarms and counter increases under the same operating conditions.

For recurring failures, industrial network diagnostics should identify the section examined, evidence collected, cause and test result after the change. Coordinate cable reconnections, tests requiring disconnection and configuration changes with maintenance; not every task can be performed while the line is running.

Technical documentation

The basis is PI's PROFINET Commissioning Guideline, version 1.53 and PROFINET Assembling Guideline, version 2.12. The communication channels are explained in the PI PROFINET Technology Description. The manuals for the installed devices determine the available diagnostics and permissible settings.

All articles

Contact ETOPA

Need technical support?

Tell us about the issue or the upgrade you are planning. Discuss the scope of work with our team.

Contact our teamor call+48 725 998 471
Discuss the work +48 725 998 471