11.02
Remedy:
Program Continuation:
27034
Parameters:
Definitions:
Reactions:
Remedy:
Program Continuation:
27090
Parameters:
Definitions:
Reactions:
Siemens AG, 2002. All rights reserved
SINUMERIK 840D/840Di/810D Diagnostics Guide (DA) – 11.02 Edition
Please inform the authorized personnel/service department. Check and change the
stated MD. Allow the checksum to be recalculated. Re-accept safety functions. Parame-
terize MD $MN_SAFE_SPL_STOP_MODE to another stop mode or enable the external
Stop E in the specified axes (set bits 4 and 6 in $MA_SAFE_FUNCTION_ENABLE).
The alarm is triggered during startup. No program can be started.
Switch control OFF - ON.
Parameterization of MD %1 invalid
%1 = MD identifier
The parameterization of %1 is incorrect. This alarm occurs in the following context: an
incorrect value was entered for MD $MN_SAFE_ALARM_SUPPRESS_LEVEL.
- Mode group not ready.
- Channel not ready.
- NC Start disable in this channel.
- NC Stop on alarm.
- Alarm display.
- Interface signals are set.
Check the specified machine data.
Switch control OFF - ON.
Error in data cross check NCK-PLC, %1[%2], NCK: %3; %4<ALSI>
%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
Error in the external wiring of the SPL terminals results in the previously issued alarm with
information about the faulty system variables $A_INSE[1...64]. Via the MD
$MN_SAFE_IN_HW_ASSIGN[0...7], the machine operator has to search for the module
over which the system variable is supplied.
To simplify the diagnosis, the specification of the affected system variables in alarm
parameter %1 is extended.
In addition to the names of the affected system variables ($A_INSE), the hardware
assignment parameterized in MD $MN_SAFE_IN_HW_ASSIGN[0...7] is displayed, so
that the affected HW connection can be determined from the information in the alarm line.
This extension is only made when there is a data cross check error at the $A_INSE sys-
tem variables.
Example: Error in data cross check NCK PLC,
DMP 04.03 bit 01=$A_INSE[2], NCK: 1; 2
The information in the example (04.03) corresponds to the entries made in the MD
$MN_SAFE_IN_HW_ASSIGN[0...7] about the system variables. They state:
DMP 04.03 bit 01The drive number of the affected terminal block (value range = 01...21)
DMP 04.03 bit 01Module number of the input module (value range = 01...08)
The stated numbers are hexadecimally displayed as in the MD
$MN_SAFE_IN_HW_ASSIGN[0...7].
The bit-number specification begins, as does the numbering of the inputs on the DMP
modules, with the value 0:
DMP 04.03 bit 012nd terminal (value range = 00... 15)
When assigning the SPL inputs to the NC onboard inputs, the extended alarm text looks
like this:
Error in data cross check NCK PLC, NC onboard input 01=$A:INSE[1], NCK: 1; 2
- Alarm display.
1 Alarms
1-357