Siemens SINUMERIK 840D sl Function Manual page 655

27096 SPL start not allowed
Remedy SPL protection withdrawn via MD11500 $MN_PREVENT_SYNACT_LOCK[0,1] or
● Commissioning of the axis-specific Safety Integrated functionality and
● Parameterization of at least one SGE/SGA at an SPL interface and
● Activation of the associated drive object
Program con‐ Switch control system OFF and ON again.
tinuation
27097 SPL not started
Parameter
Explanation After the time defined in MD13310 SAFE_SPL_START_TIMEOUT expired, the SPL had not started.
This alarm can be suppressed using MD10096 $MN_SAFE_DIAGNOSIS_MASK, bit 1 = 1.
Response Alarm display
Remedy 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 MD11602 (stop reasons, read-in
inhibit)
● Problems when calling FB4/FC9
Program con‐ Switch control system OFF and ON again.
tinuation
27098 SPL commissioning phase completed
Parameter
Explanation The SPL commissioning phase was just ended by changing MD11500 $MN_PREVENT_SYNACT_LOCK.
The /_N_CST_DIR/_N_SAFE_SPF is, from the next power on, subject to the monitoring mechanisms defined
for the SPL (access protection, checksum calculation).
Changes to SPL can only be made in the unprotected state.
Response Alarm display
Remedy Carry out a power on for the control.
Check and monitor the changes of the logic in the SPL using an acceptance test.
Program con‐ Clear the alarm with the RESET key. Restart the part program.
tinuation
Safety Integrated
Function Manual, 12/2017, 6FC5397-4BP40-6BA1
11.2 NCK safety alarms for SINUMERIK 840D sl
Diagnostics
655