Acknowledging A Communication Error With Channel_1 Reset; F_Dp Communication For A System Error - Siemens SINUMERIK 840D sl Function Manual

Connecting sensors and actuators
8.4 Safety-related CPU-CPU communication (F_DP communication)
FRDP[1...3] or FRDP_HF[4..16].ERR_REAC = $MN_SAFE_RDP_ERR_REAC
8.4.11

Acknowledging a communication error with channel_1 reset

If, due to a communication error, an alarm with NCK responses and possibly a STOP D/E
initiated, then the user acknowledgment must be realized using a channel_1 reset in order that
the alarms are cleared and the alarm responses reset. If the channel_1 reset is initiated before
setting the request for the user acknowledgment $A_FRDP_ACK_REQ, then the NCK
responses are reset within the scope of the reset processing. As a result of the communication
error that is still present, the alarm is again initiated in the next F_DP clock cycle and the NCK
responses are reactivated.
If the error response (STOP D/E), programmed when a communication error occurs, prevents
e.g. moving plant/systems into a suitable position required to continue operation in a production
plant or system, then the error response must be re-programmed
NCK responses using a channel_1 reset.
Example
1. The currently programmed error response is $A_FRDP_ERR_REAC = 0 (Alarm 27350 +
STOP D/E).
2. A communication error is identified and the responses Alarm 27350 + STOP D/E initiated.
3. In order that the plant or system can continue to produce, the component involved should
be manually moved into a suitable position. To do this, error response
$A_FRDP_ERR_REAC must be set to 3 (no Alarm) in the user program and then a
channel_1 reset must be initiated. The alarms are then cleared and the NCK responses
reset.
4. The error response is initiated again as the communication error is still present after the
channel_1 reset. Due to the fact that the error response was re-programmed, an alarm is
not initiated and no NCK interlocks due to STOP D/E are effective. This means that the
plant or system components can be moved.
8.4.12

F_DP communication for a system error

There is a system error, if incorrect behavior (inappropriate response) is detected, which is not
caused by a communication error described in the F_DP protocol, but was only the result of
incorrect behavior (malfunction) of the system software or hardware.
Driver-specific system errors:
● Asynchronous fault state (StateFault)
The NCK or PLC-F_DP driver is in the fault/error state while the F_DP of the 2nd channel
is not in a fault/error state.
⇒ Alarm 27355
● Sign-of-life monitoring (LifeSign)
The NCK or PLC-F_DP driver has not updated its sign-of-life.
⇒ Alarm 27355
252
before acknowledging the
Function Manual, 12/2017, 6FC5397-4BP40-6BA1
Safety Integrated