Diagnosis and behavior in case of error
The PROFIBUS module provides detailed diagnosis information about the status of the connected device, its own status and
the status of the PROFIBUS connection. Diagnosis information is shown with the locally available lamps and via the standard
PROFIBUS services.
Local Diagnosis PDP32
Diagnosis information is locally shown with LEDs (Light Emitting Diodes) Bus and DD located on the front side of the
PROFIBUS module. The meaning of the LED status is as follows:
LED Bus (red, green)
LED DD (red, green)
Meaning
Off
Off
Power Supply missing
Green flashing
- Connection to master missing
- Bus address of UMC different form the one configured in the
master
- I/O size mismatch between device and master
Red flashing
Parameter mismatch between device and master
Red
Communication lost, supervision timeout time exceeded
Green
OK, normal data exchange
Amber flashing
Amber flashing
Initializing
Green flashing
Waiting for communication from UMC
Green
OK, normal data exchange
Red flashing
Connection to UMC lost
Red
Internal fault. Replace communication interface.
PROFIBUS Diagnosis
•
Standard Diagnosis: The format of the standard diagnosis data is defined within the PROFIBUS standards (IEC 61158). It
consists of 6 octets that cannot be influenced by the field device manufacturer. The diagnosis information is related to the
communication layer and covers run-up diagnosis scenarios such as the device identification, communication mode infor-
mation (FREEZE, SYNC), readiness, availabilities, watchdogs, parameterization and configuration faults.
For details, see IEC 61158-6, 6.2.3.1 to 6.2.3.5. Bit 7 in octet 3 (the “Ext_Diag_Overfl ow” flag) is used by the PROFIBUS com-
munication interface to indicate more diagnosis information then fits into the actual diagnosis message length.
•
Extended Diagnosis: PROFIBUS module offers extended diagnosis to make the diagnosis data of the connected devices
available to the PROFIBUS master. Depending on the selected diagnosis format DP-V1 or DP-V0, the content of the diagno-
sis is slightly different. The extended diagnosis telegram has the following format:
Byte in the extended
diagnosis telegram
Meaning DP-V0
Meaning DP-V1
0
Block length: 10 = 10 Bytes
Block length: 13 = 13 Bytes
1
Communication status communication
interface - UMC:
Value(0) ="Communication OK"
Value(1) ="Lost Communication to UMC100"
Status type (always 0x81 = Status Mode)
2
Diagnosis Byte 0 UMC (see UMC manual)
Slot number (always zero)
3
Diagnosis Byte 1 UMC (see UMC manual)
Status specifi er (always zero)
4
Diagnosis Byte 2 UMC (see UMC manual)
Communication status communication interface - UMC:
Value(0) ="Communication OK"
Value(1) ="Lost Communication to UMC100"
5
Diagnosis Byte 3 UMC (see UMC manual)
Diagnosis Byte 0 UMC (see UMC manual)
6
Diagnosis Byte 4 UMC (see UMC manual)
Diagnosis Byte 1 UMC (see UMC manual)
7
Diagnosis Byte 5 UMC (see UMC manual)
Diagnosis Byte 2 UMC (see UMC manual)
8
Diagnosis Byte 6 UMC (see UMC manual)
Diagnosis Byte 3 UMC (see UMC manual)
9
Diagnosis Byte 7 UMC (see UMC manual)
Diagnosis Byte 4 UMC (see UMC manual)
10
-
Diagnosis Byte 5 UMC (see UMC manual)
11
-
Diagnosis Byte 6 UMC (see UMC manual)
12
-
Diagnosis Byte 7 UMC (see UMC manual)
—
Diagnosis
12
P D P 3 2 .0 M A N UA L
