コード 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-chec k 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-che ck, $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 different 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 performed. - 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 sy stem 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 c onnection 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) co rrespond 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 affect ed 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 numbe rs 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 i nputs, 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 variables: %4 = 0: Error SPL commissioning status ($MN_PREVENT_SYNACT_LOCK[0,1] - DB18 DBX36.0) %4 = 0: Error SPL stop reaction ($MN_SAFE_SPL_STOP_MODE - DB18 DBX36.1). %4 = 0: Error SPL user data ($MN_SAFE_SPL_USER_DATA - DB18 DBD256,260,264,268) %4 = 0: Error FSENDDP error re action ($A_FSDP_ERR_REAC[n] - DB18 DBW190, DBW210, DBW220) %4 = 0: Error FRECVDP error r eaction ($A_FRDP_ERR_REAC[n] - DB18 DBW222, DBW234, DBW246) %4 = 0: Error FRECVDP replacement values ($A_FRDP_SUBS[n] - DB18 DBW220, DBW232, DBW244) %4 = 1.... 64: Error in system variable $A_INSE[1...64] %4 = 65...128: Error in system variable $A_OUTSE[1...64] %4 = 129...192: Error in system variable $A_INSI[1...64] %4 = 193...256: Error in system variable $A_OUTSI[1...64] %4 = 257...320: Error in system variable $A_MARKERSI[1...64] In order to parameterize alarm 27090, file ALSI_xx.com must be incorporated in the data management and declared in HMI via MBDDE.INI in the section[IndexTextFiles] ALSI=f:\dh\mb.dir\alsi_. The machine manufacturer can redefine this file, in orde r to incorporate additional text passages in the alarm that make sense for their system. If the file is redefined, the newly created file has to be declared in the system via MBDDE.INI. The display of alarm 27090 can be modified via MD $MN_SAFE_ALARM_SUPPRESS_LEVEL: MD $MN_SAFE_ALARM_SUPPRESS_LEVEL = 2: Alarm 27090 will now only displayed for the first data difference found. Reaction: Alarm display. Trigger a STOP D/E (settable via MD $MN_SPL_STOP_ MODE) on all axes with safety functionality, as soon as the SPL start-up phase (MD $MN_PREVENT_SYNACT_LOCK[0,1] unequal to 0) is completed. Remedy: Analyze the value displayed and evaluate DB18: SPL_DELTA on the PLC side. Find the difference between the moni toring channels. Possible causes: - Incorrect wiring - Incorrect SPL - Incorrect assignment of the axial SG Es to internal interface $A_OUTSI - Incorrect assignment of the axial SGAs to internal interface $A_INSI - Incorrect assignment of the SPL SGEs to external interface $A_INSE - Incorrect assignment of the SPL SGAs to external interface $A_OUTSE - Different SPL startup status set in NCK and PLC - Different SPL stop reaction set in NCK and PLC Program Continuation: Clear alarm with the RESET key. Restart part program