Siemens Sinumerik 840D sl Function Manual page 703

Sinumerik safety integrated
Hide thumbs Also See for Sinumerik 840D sl:
Table of Contents

Advertisement

10/15
Remedy
Program
r
continuation
27098
Explanation
Response
Remedy
r
Program
continuation
27099
Parameter
Explanation
© Siemens AG 2015 All Rights Reserved
SINUMERIK 840D sl/SINAMICS S120 SINUMERIK Safety Integrated (FBSI sl) - - 10.2015 Edition
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
Switch--off – switch--on the control
SPL commissioning phase completed
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.
Alarm display
Carry out a power on for the control.
Check and monitor the changes of the logic in the SPL using an
acceptance test.
Clear the alarm with the RESET key. Restart the part program.
Double assignment in the SPL assignment MD %1[%2] - -
MD %3[%4]
%1 = MD name 1
%2 = MD field index for MD name 1
%3 = MD name 2
%4 = MD field index for MD name 2
SPL inputs ($A_INSE) have been assigned twice by various applica-
tions in the displayed machine data. These can be:
-- PROFIsafe communication
-- F_DP communication
10.2NCK safety alarms for Sinumerik 840D sl
Diagnostics
10-703

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

Sinamics s120

Table of Contents