Siemens SINUMERIK 840Di Diagnostic Manual page 470

Overview of Alarms
NCK alarms
27094 Write access to system variable %1 only allowed from NCK-SPL
Parameters: %1 = Name of safety system variable concerned
Definitions: Write access to a safety system variable is only allowed from the part program
/_N_CST_DIR/_N_SAFE_SPF. If this error occurs, an instruction from another part program was
detected.
Reaction: Alarm display.
Remedy: Check the part programs you are using for write accesses to safety system variables.
Program Clear alarm with the RESET key. Restart part program
Continuation:
27095 %1 SPL protection not activated
Parameters: %1 = Name of the component on which the protection is not activated (NCK or PLC)
Definitions: The protection features are not activated for the SPL. The startup phase of the SPL is not yet
complete. No stop reaction (Stop D or E) was initiated on an error in data cross-comparison between
NCK and PLC.
Reaction: Alarm display.
Remedy: - Remedy for NCK: Activate the protection features with MD $MN_PREVENT_SYNACT_LOCK[0,1].
The number range of the synchronized action IDs used in the SPL must be entered in this MD.
- Remedy for PLC: Activate the protection features by setting the appropriate data bit in DB18.
Program Clear alarm with the RESET key. Restart part program
Continuation:
27096 SPL start not allowed
Definitions: To start the SPL in protected state (MD $MN_PREVENT_SYNACT_LOCK[0,1] not equal 0) Safety
Integrated functionality must first be activated for at least one axis (via MD
$MA_SAFE_FUNCTION_ENABLE). Without this functionality it is only possible to operate SPL in
start-up state.
Reaction: Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Channel not ready.
Remedy: Start up axial Safety Integrated functionality or remove the SPL protection via MD
$MN_PREVENT_SYNACT_LOCK[0,1].
Program Switch control OFF - ON.
Continuation:
27097 SPL start not executed
Definitions: SPL start not executed after predefined timeout in MD SAFE_SPL_START_TIMEOUT.
Reaction: Alarm display.
Remedy: Find reason for not executed SPL start. Possible causes may be:
- An NC or drive error is present (e.g. after encoder replacement, EMERGENCY STOP, PROFIsafe
alarms)
- Syntax error in SPL
- Safety Integrated alarm present (e.g. "Safe limit position overrun")
- Name or path of SPL for PROG_EVENT start written incorrectly; take care of upper and lower cases
- Simultaneous start of an ASUB and PROG_EVENT, parameterization MD 11602 (stop causes e.g.
read-in disable)
- Problems when calling FB4/FC9
Program Clear alarm with the RESET key. Restart part program
Continuation:
2-470
© Siemens AG, 2006. All rights reserved
SINUMERIK, SIMODRIVE Diagnostics Manual (DA), 11/2006 Edition
11/2006