Siemens SIMATIC ET 200SP Manual page 58

Assigning parameters / Setting the address space
6.4 Data records for diagnostics
Data record 92 contains device-specific messages and information on the device function
states of the F-CM AS-i Safety ST module.
For some events, the F-CM AS-i Safety ST module generates a diagnostic alarm.
The following applies for diagnostic alarms of the F-CM AS-i Safety ST module with firmware
V1.0.0:
● The "Error code" column in the table below indicates which events are relevant here. If
the associated bit changes in the data record, a diagnostic alarm with the indicated error
code is generated (incoming alarm when bit changes to value "1" and outgoing alarm
when bit changes to value "0").
● The text inside parentheses after the error code corresponds to the error text that is
specified for the given error code according to the PROFIBUS Standard. Several error
codes can be output. If no error code is specified ("-"), a diagnostic alarm is not
generated.
● The diagnostic alarms in firmware V1.0.1 or higher are described in Section "DS 206
Diagnostic Data Record (Page 69)".
Table 6- 8 DS 92 device-specific diagnostics
Byte.Bit Description
0.0 ... 0.7 Reserved
1.0 ... 1.7 Reserved
2.0 ... 2.7 Reserved
3.0 ... 3.7 Reserved
4.0 ... 4.7 Reserved
5.0 ... 5.7 Reserved
6.0 ... 6.7 Reserved
7.0 ... 7.7 Reserved
8.0 ... 8.7 Reserved
9.0 ... 9.7 Reserved
10.0 ... 10.7 Reserved
11.0 ... 11.7 Reserved
12.0 Serious device fault
12.1 Group error
12.2 AS-i communication error
12.3 Group_Message_Device
12.4 Group_Message_Application
58
Only with firmware V1.0.0:
Error code (decimal) in the
diagnostic alarm
-
-
-
-
-
-
-
-
-
-
-
-
9 ("Error")
24 ("Switch-off")
19 ("Communication error")
-
-
Fail-safe Module F‑CM AS‑i Safety ST (3RK7136‑6SC00‑0BC1)
Manual, 03/2017, A5E03957059020A/RS-AB/002
Remark
-
-
-
-
-
-
-
-
-
-
-
-
See Section Error statuses
(Page 17)
At least one error is present.
Failure of an AS-i slave configured
in the F-CM AS-i Safety ST module
or code sequence error
At least one message about the
device state is present, e.g.,
configuration missing.
At least one message about the
application state is present, e.g.,
startup test necessary, safety
sensor tripped (Emergency Stop,
protective door, etc.).