Byte Bit Name and meaning Cause Measures Group
2 0 DIA_MAINTENANCE_ALARM
Maintenance alarm
To determine the cause, check in
DIAGNOSIS_EXTENSION and
DIAGNOSIS_EXTENSION_2
which diagnosis event has trig‐
gered the message.
Depends on the
triggering diagnos‐
tics event.
M
1 DIA_MAINTENANCE_DEMANDED
Maintenance demand
To determine the cause, check in
DIAGNOSIS_EXTENSION and
DIAGNOSIS_EXTENSION_2
which diagnosis event has trig‐
gered the message.
Depends on the
triggering diagnos‐
tics event.
M12, M
2 DIA_FUNCTION_CHECK
Function check
The device is in on-site operation
or the FEEDBACK_VALUE is si‐
mulated
- F
3 DIA_INV_PRO_COND
Invalid process conditions
To determine the cause, check in
DIAGNOSIS_EXTENSION and
DIAGNOSIS_EXTENSION_2
which diagnosis event has trig‐
gered the message.
Depends on the
triggering diagnos‐
tics event.
P
4
... 7
Reserved - - -
3 0
... 6
Reserved - - -
7 EXTENSION_AVAILABLE
Extension available
Further information about the trig‐
gering diagnosis event is availa‐
ble in DIAGNOSIS_EXTENSION
and DIAGNOSIS_EXTEN‐
SION_2.
- -
9.3.3.3 Definition of the status
Status byte
The status is used to provide information about the quality of the input and output values. This
information is classified into four stages. Quality stages such as "Bad", "Uncertain", "Good" and
"Good (cascade)" are accompanied with further information. In this case, it deals with the sub-
status and the limit bits. The status byte has the following structure:
Status byte structure
7 6 5 4 3 2 1 0
Quality Sub-status Limit bits
Quality 00 Bad
01 Uncertain
10 Good
11 Good (cascade)
Limit bits 00 Good
Functions/operations using PROFIBUS PA
9.3 Cyclic data transfer
SIPART PS2 with PROFIBUS PA
226 Operating Instructions, 05/2019, A5E00127926-AC
To Next Page
Loading...
Need help?
General
