Siemens SINUMERIK 840D Series Diagnostics Manual page 246

1 Alarms
Definitions:
Reactions:
Remedy:
Program Continuation:
16939
Parameters:
Definitions:
Reactions:
Remedy:
Program Continuation:
16940
Parameters:
Definitions:
Reactions:
Remedy:
Program Continuation:
16941
Parameters:
Definitions:
Reactions:
Remedy:
1-246
Reorganization events are, among others, subprogram abort, delete distance-to-go and
interrupts, axis replacement, exiting the correction state. These events wait for the end of
a gear change. However, the maximum waiting period has elapsed.
- Alarm display.
- Interface signals are set.
- NC Start disable in this channel.
- NC Stop on alarm.
Program must be aborted with Reset and, if necessary, GEAR_CHANGE_WAIT_TIME
must be increased.
Clear alarm with the RESET key. Restart part program
Channel %1 action %2 rejected due to active gear change
%1 = Channel ID
%2 = Action number/action name
Reorganization events that are possible in Stop state, e.g mode change, are waiting for
the end of the gear change. However, the maximum waiting period has elapsed.
- Alarm display.
- Interface signals are set.
Repeat action or increase MD GEAR_CHANGE_WAIT_TIME.
Clear alarm with the Delete key or NC START.
Channel %1 action %2<ALNX> wait for gear change
%1 = Channel ID
%2 = Action number/action name
Reorganization events are waiting for the end of a gear change. The alarm is displayed
during the waiting period.
- Alarm display.
- Warning display.
Alarm is suppressed by means of ENABLE_ALARM_MASK bit 1 == 0.
Alarm display showing cause of alarm disappears. No further operator action
Channel %1 action %2<ALNX> rejected because no program event has been exe-
cuted yet
%1 = Channel ID
%2 = Action number/action name
The setting of the machine data $MC_PROG_EVENT_MASK forces an asynchronous
subprogram to be triggered automatically on RESET or PowerOn. The implicitly triggered
asynchronous subprograms are normally called "Event-triggered program call" or "Pro-
gram event".
In the alarm situation, this asynchronous subprogram could not yet be activated; that is
why the action (normally start of part program) must be rejected.
Reasons for the fact that the asynchronous subprogram could not be triggered:
1. The asynchronous subprogram does not exist (/_N_CMA_DIR/
_N_PROG_EVENT_SPF)
2. The asynchronous subprogram is allowed to start in the referenced state only (see
$MN_ASUP_START_MASK)
3. READY is missing (because of alarm)
- Alarm display.
• Load program
• Check $MN_ASUP_START_MASK
• Acknowledge alarm
SINUMERIK 840D/840Di/810D Diagnostics Guide (DA) – 11.02 Edition
 Siemens AG, 2002. All rights reserved
11.02