Siemens SINUMERIK 840D sl Function Manual page 514

Diagnostics
10.2 NCK safety alarms for SINUMERIK 840D sl
27097
Explanation
Response
Remedy
Program
continuation
27099
Parameter
Explanation
Response
Remedy
Program
continuation
10-514
SINUMERIK 840D sl/SINAMICS S120 SINUMERIK Safety Integrated (FBSI sl) – 05.2008 Edition
SPL not started
After the time defined in MD SAFE_SPL_START_TIMEOUT expired,
the SPL had not started. Please note MDs 13310:
$MN_SAFE_SPL_START_TIMEOUT and 10096 $MN_SAFE_DIAG-
NOSIS_MASK, bit 1.
Alarm display
Find the reason why SPL did not start. Possible causes could be:
– There is either an NC or drive fault (e.g. after replacing an encoder,
Emergency Stop, PROFIsafe alarms)
– There is a syntax error in the SPL itself
– A safety alarm is present (e.g. "safe end position exceeded")
– At PROG_EVENT start, the name or path of the SPL was not
correctly written to; observe upper and lower case letters
– Simultaneous start of an ASUB and PROG_EVENT, parameterizing
MD 11602 (stop reasons, read–in inhibit)
– Problems when calling FB4/FC9
Clear the alarm with the reset key. Restart the part program
Double allocation in the SPL assignment MD %1[%2] – MD %3[%4]
%1 = $MN_PROFISAFE_IN_ASSIGN
%2 = Machine data index
%3 = $MN_PROFISAFE_IN_ASSIGN
%4 = Machine data
SPL inputs ($A_INSE) have been assigned twice in the displayed
machine data by various applications. This can be:
– PROFIsafe communication
Mode group not ready
Channel not ready
NC start inhibit in this channel
Interface signals are set
Alarm display
Correct the displayed MD
Switch control system OFF and ON again.
© Siemens AG 2008 All Rights Reserved
05.08