Siemens Sinumerik 840D sl Diagnostic Manual page 426

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

Advertisement

Overview of Alarms
NCK alarms
27073
Checksum error S7 PROFIsafe configuration. Confirmation and
acceptance test required!
Definitions:
The F parameters required for PROFIsafe communication are protected by a checksum. The alarm
indicates that the current checksum no longer corresponds to the stored checksum, this means that
an MD has either been changed without authorization or is faulty.
Reaction:
Mode group not ready.
Channel not ready.
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy:
Check the PROFIsafe configuration on the S7 side. Have the checksum recalculated. Re-accept
safety functions (PROFIsafe I/Os).
Program Con-
Switch control OFF - ON.
tinuation:
27090
Error in data cross check NCK-PLC, %1[%2], NCK: %3; %4<ALSI>
Parameters:
%1 = Name of system variable in which the error was detected
%2 = System variable array index extension
%3 = NCK comparison value extension
%4 = Cross-check array index extension
Definitions:
Differences in the compared data have occured in a cyclic data cross-check between NCK and PLC.
Parameter %1 specifies the incorrect system variable ($A_INSI, $A_OUTSI, $A_INSE, $A_OUTSE
or $A_MARKERSI) with array index %2.
Special cases:
- Display "Error in NCK-PLC data cross-check, $MN_PREVENT_SYNACT_LOCK[0], ..." means that
the SPL commissioning status has been set differently in the NCK and PLC.
- Display "Error in NCK-PLC data cross-check, $MN_SPL_STOP_MODE[0], ..." means that the SPL
stop reaction (Stop D or E) has been set differently in the NCK and PLC.
- Display "Error in NCK-PLC data cross-check, $MN_SAFE_SPL_USER_DATA[n], ..." means that dif-
ferent user data have been set in NCK and PLC.
- Display "Error in NCK-PLC data cross-check, TIMEOUT[0], NCK: 0" means that the communication
between NCK and PLC is generally disturbed and that a data cross-check can no longer be per-
formed.
- Display "Error in NCK-PLC data cross-check, $A_FSDP_ERR_REAC[n], $A_FRDP_SUBS[n],
$A_FRDP_ERR_REAC[n]..." means that different system variables have been specified in NCK and
PLC.
With data cross-check errors on system variables $A_INSE, the hardware assignment parameterized
in MD $MN_SAFE_IN_HW_ASSIGN[0...7] is displayed in addition to the affected system variables in
alarm parameter %1, so that the affected hardware connection is shown directly by the specifications
in the alarm line.
Example: Error in NCK-PLC data cross-check, DMP 04.03 bit 01=$A_INSE[2], NCK: 1;
The specifications in the example (04.03) correspond to the entries made in the machine data
$MN_SAFE_IN_HW_ASSIGN[0...7] for the stated system variable.
They specify:
DMP 04.xx The drive number of the affected terminal block (value range = 01...21).
DMP xx.03 Module number of the input module (value range = 01...08).
The stated numbers are shown as hexadecimal numbers as in MD
$MN_SAFE_IN_HW_ASSIGN[0...7].
The specification of the bit numbers begins with the value 0 (value range = 00...15), the same as the
numbering of the inputs on the DMP modules.
When assigning the SPL inputs to the NC onboard inputs, the extended alarm text is as follows:
Error in NCK-PLC data cross-check, NC-Onboard-In 01=$A:INSE[1], NCK: 1; 2.
With parameter %4, a specific alarm message can be configured on HMI for all listed system vari-
ables:
%4 =
DBX36.0)
%4 =
%4 =
2-426
0: Error SPL commissioning status ($MN_PREVENT_SYNACT_LOCK[0,1] - DB18
0: Error SPL stop reaction ($MN_SAFE_SPL_STOP_MODE - DB18 DBX36.1).
0: Error SPL user data ($MN_SAFE_SPL_USER_DATA - DB18 DBD256,260,264,268)
SINUMERIK 840D sl, 840Di sl, SINAMICS, Diagnostics Manual (DAsl), 03/2009
© Siemens AG, 2009. All Rights Reserved
03/2009

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents