PROFINET diagnostic code

Available from firmware 2019.6

How to

Tutorial video

Note: These videos are based on the firmware release 2021.0 LTS. From release 2022.0 LTS, the PROFINET diagnostic features in the Web-based Management (WBM) are extended as described in the Diagnostics - PROFINET topic.

Note: Tutorial videos are embedded from the Phoenix Contact Technical Support YouTube channel. With playing an embedded YouTube video in this platform, you accept the YouTube Terms & Conditions.
Even showing the video previews on this page depends on your personal settings in the Cookie consent dialog. To watch YouTube videos, you have to allow cookies for marketing purposes which will remain on your device. The data gained through these cookies will be used by YouTube to provide video suggestions and advertisements based on your browsing habits, and may be made available to other parties.

Check and change your cookie consent

03m:33s

HDTV 720p

English

03m:35s

HDTV 720p

Deutsch

‒

Reference

The PROFINET page in the WBM Diagnostics area of your controller is used to view information about the controller and the connected PROFINET devices, as well as information about their Axioline F local bus devices. The displayed diagnostic code consists of several bits that are evaluated individually.

The diagnostic state (OK, warning, error) as well as the corresponding diagnostic text are based on an evaluation of the diagnostic bits. The following section is an excerpt from the AutomationRuntimePlatform/Source/Arp/Io/ProfinetStack/Controller/Services/DiagnosticInfo.hpp firmware file. It contains the bit description of the diagnostic code:

/// <summary>
/// Special status of this AR, bitwise coded.
/// - Bit 0: set if not connected
/// - Bit 1: set if data invalid
/// - Bit 2: set if diagnosis is available
/// - Bit 3: set if module difference is available in case of configuration difference
/// - Bit 4: set if AR is deactivated
/// - Bit 5: set if neighborhood information is not available
/// - Bit 6: neighborhood information not unique
/// - Bit 7 - Identify.cnf on alias received, but name of the device is already configured in another AR
/// - Bit 8: Maintenance Required Information is available
/// - Bit 9: Maintenance Demanded Information is available
/// - Bit 10: Channel or Manufacturer Specific Diagnosis Information are available
/// - Bit 11..15: reserved (shall be 0)
/// </summary>

The controller may show the error as a hexadecimal code which you need to convert to a binary and read the set bits from there.

Show how to convert hex codes into bitsShow how to convert hex codes into bits

Convert each hex digit into 4 binary digits and write them down one after the other.

For example, hex code 0x24 converts to binary 0010|0100. Leading zeros at the binary can be omitted, so go with 100100.

Hex 0 1 2 3 4 5 6 7 8 9 A B C D E F

Binary 0000 0001 0010 0011 0100 0101 0110 0111 1000 1001 1010 1011 1100 1101 1110 1111

Look up the bit for each binary value 1 (starting from the right), meaning that bit is set.

In our example with hex code 0x24 equalling to binary 100100, this means bits 2 and 5 are set.

Binary	`0`	`0`	`0`	`0`	`0`	`1`	`0`	`0`	`1`	`0`	`0`
Bit	`Bit 10`	`Bit 9`	`Bit 8`	`Bit 7`	`Bit 6`	`Bit 5`	`Bit 4`	`Bit 3`	`Bit 2`	`Bit 1`	`Bit 0`

Meanings and recommendations for action

Bit	Meaning and recommendation for action
`Bit 0: set if not connected`	The PROFINET controller could not establish a connection with the PROFINET device or the Application Relation (AR) was deactivated. Please check the Ethernet connection and the PROFINET device name (e.g. with PLCnext Engineer PROFINET Online Devices) In addition, check if the AR has been deactivated in the PROFINET device settings.
`Bit 1: set if data invalid`	The PROFINET device is connected to the PROFINET controller, but the device has marked the process data as invalid due to a fault. The process data are not transferred to the process image. Please check the diagnostics of the PROFINET device and contact the manufacturer of the PROFINET device if necessary.
`Bit 2: set if diagnosis is available`	The PROFINET device reports a diagnosis. Please check the diagnostics of the PROFINET device and contact the manufacturer of the PROFINET device if necessary.
`Bit 3: set if module difference is available in case of configuration difference`	During the initialization of the PROFINET connection, a deviation between the target and actual configuration was detected. Please check the configuration of the PROFINET device. In the default setting of PLCnext Engineer, the connection remains established in the event of a difference in configuration.
`Bit 4: set if AR is deactivated`	The PROFINET device is configured in the project, but the AR (Application Relation) has been deactivated. Check the Profinet device settings and activate the AR.
`Bit 5: set if neighborhood information is not available`	No neighborhood information is available in the network used. This is usually due to the use of components that are not at least PROFINET Conformance Class-B (CC-B) compatible. For a stable PROFINET network, Phoenix Contact only recommends using CC-B or CC-C compliant PROFINET devices.
`Bit 6: neighborhood information not unique`	In the network used, neighbourhood information is available but not unique. This means that more than two PROFINET devices can be detected on one port of at least one switch. This is not permitted and may result in the automatic device exchange not functioning reliably. This is usually due to the use of components that are not at least PROFINET Conformance Class-B (CC-B) compatible (e.g. unmanaged switches).
`Bit 7 - Identify.cnf on alias received, but name of the device is already - configured in another AR`	A DCP Identify (Alias) Request was sent to the network. However, the alias name of a device being searched is already in use by an AR. This information is only an indication that the control program is probably trying to establish a connection with a device although a connection is still active.
`Bit 8: Maintenance Required Information is available`	The PROFINET device has transmitted a maintenance request (maintenance alarm). Please check the diagnostics of the PROFINET device and contact the manufacturer of the PROFINET device if necessary.
`Bit 9: Maintenance Demanded Information is available`	The PROFINET device has transmitted an urgent maintenance request (maintenance alarm). Please check the diagnostics of the PROFINET device and contact the manufacturer of the PROFINET device if necessary.
`Bit 10: Channel or Manufacturer Specific Diagnosis Information are available`	Optional and manufacturer-specific information is available. Please check the diagnostics of the PROFINET device and contact the manufacturer of the PROFINET device if necessary.