Siemens SINUMERIK 840D - Page 326

6 Alarms 11.03
6.1 Alarms for SINUMERIK 840digital
© Siemens AG 2003 All Rights Reserved
6-326 SINUMERIK 840D/SIMODRIVE 611 digital SINUMERIK Safety Integrated (FBSI) - Edition 11.03
27090
Error in data NCK-PLC %1 [%2], NCK: %3; %4<ALSI>
Parameter %1 = name of the system variable in which error was detected
%2 = supplementary info, system variables – field index
%3 = supplementary information, comparison value NCK
%4 = supplementary information, crosswise data comparison – field index
Explanation For the cyclic crosswise data comparison between NCK and PLC, differences
have occurred in the compared data.. Parameter %1 specifies the incorrect
system variable ($A_INSI, $A_OUTSI, $A_INSE, $A_OUTSE or
$A_MARKERSI) with field index %2.
Special cases:
- Display "Error for crosswise data comparison NCK-PLC,
$MN_PREVENT_SYNACT_LOCK[0], ..." means that the SPL
commissioning status is set differently in the NCK and PLC.
- Display "Error for crosswise data comparison NCK-PLC,
$MN_SPL_STOP_MODE[0], ..." means that the SPL
stop response (Stop D or E) is set differently in the NCK and PLC.
- Display "error for crosswise data comparison NCK-PLC, TIMEOUT[0],
NCK: 0" means that there is a major communications error between
the NCK and PLC and no crosswise data comparison can be
carried-out.
For crosswise data comparison errors on the system variables $A_INSE, the
system variable involved is specified in alarm parameter %1 and the hardware
assignment parameterized in MD $MN_SAFE_IN_HW_ASSIGN[0...7] is
displayed, so that the hardware connection involved can be directly seen from
the data in the alarm line.
Example: Error for crosswise data comparison, NCK-PLC, DMP 04.03 bit
01=$A_INSE[2], NCK: 1;
The information in the example (04.03) corresponds to the entries made in the
machine data $MN_SAFE_IN_HW_ASSIGN[0...7] about the system variables.
They specify:
DMP 04.xx The drive number of the terminal block involved (value range =
01...21)
Module number of the input module (value range = 01...08)
The specified numbers are in the hexadecimal notation the same as in MD
$MN_SAFE_IN_HW_ASSIGN[0...7].
The bit number is specified starting just like the numbering of the inputs on the
DMP modules with the value 0 (value range = 00...15)
When assigning the SPL inputs to the NC onboard inputs, the expanded alarm
text looks like this:
Error for the crosswise data comparison, NCK-PLC, NC-Onboard-In
01=$A:INSE[1], NCK: 1;2
A specific alarm message can be configured on the HMI for each of the listed
system variables using parameter %4:
%4 = 0: Error SPL commissioning status
($MN_PREVENT_SYNACT_LOCK[0,1] - DB18.DBX36.0)
or different stop response ($MN_SAFE_SPL_STOP_MODE - DB18.DBX36.1)
%4 = 1.... 64: Error in system variables $A_INSE[1...64]
%4 = 65...128: Error in system variables $A_OUTSE[1...64]
%4 = 129...192: Error in system variables $A_INSI[1...64]
%4 = 193..256: Error in system variables $A_OUTSI[1...64]
%4 = 257…320: Error in system variables $A_MARKERSI[1...64]
In order to parameterize Alarm 27090, file ALSI_xx.com must be incorporated
in the data management and communicated to the HMI via MBDDE.INI in
section [IndexTextFiles] ALNX=f:\dh\mb.dir\alsi_. The machinery construction
OEM can re-define this file in order to incorporate sensible expanded texts in
the alarm for his particular machine/system. If the file is to be re-defined, the
new file to be created must be made known to the system via MBDDE.INI.