hit counter script

Siemens SINUMERIK 840D Diagnostics Manual page 397

Hide thumbs Also See for SINUMERIK 840D:
Table of Contents

Advertisement

10.04
Reactions:
Remedy:
Program Continuation:
27094
Parameters:
Definitions:
Reactions:
Remedy:
Program Continuation:
27095
Parameters:
Definitions:
Reactions:
Remedy:
Program Continuation:
27096
Definitions:
Reactions:
Remedy:
Program Continuation:
 Siemens AG, 2004. All rights reserved
SINUMERIK 840D/840Di/810D Diagnostics Guide (DA), 10.04 Edition
• %1 = FILE_LENGTH: the file length has changed.
• %1 = FILE_CONTENT: the file contents have changed.
%2 specifies the reference variable (file length, checksum of file contents), %3 specifies
the actual variable which is calculated cyclically.
- Alarm display.
Check the file and the time of the last modification to the file. Reload the original file and
start the monitoring system again with a Power On.
Switch control OFF - ON.
Write access to system variable %1 only allowed from NCK-SPL
%1 = Name of safety system variable concerned
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 pro-
gram was detected.
- Alarm display.
Check the part programs you are using for write accesses to safety system variables.
Clear alarm with the RESET key. Restart part program
%1 SPL protection not activated
%1 = Name of the component on which the protection is not activated (NCK or PLC)
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-com-
parison between NCK and PLC.
- Alarm display.
• 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.
Clear alarm with the RESET key. Restart part program
SPL start not allowed
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 oper-
ate SPL in start-up state.
- 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.
Start up axial Safety Integrated functionality or remove the SPL protection via MD
$MN_PREVENT_SYNACT_LOCK[0,1].
Switch control OFF - ON.
1 Alarms
1-397

Advertisement

Table of Contents
loading

Table of Contents

Save PDF