Detailed description
2.7 Program operation mode
Basic logic functions: Mode group, channel, program operation, reset response (K1)
126 Function Manual, 11/2006, 6FC5397-0BP10-2BA0
Stop event
• A stop event can be triggered by the following
Event Classification
VDI interface signals from the PLC "Hard" stop event
Alarms with NOREADY response "Hard" stop event
Stop key "Soft" stop event
Read-in disable "Soft" stop event
Single block "Soft" stop event
Note
Some NCK events are stopped for a short time, in order to perform a switching operation,
and restarted immediately. These include e.g., the ASUB that stops the contour briefly in
order to then start the ASUB program immediately. These events are also allowed in the
stop delay area, however they are pushed back to its end and are thus considered "soft stop
events".
Boundary conditions
The following exceptions apply while a stop delay area is being processed:
• A change in the feed is ignored while in the stop delay area. A feed disable is thus not
effective until the program area has been exited, and is stopped.
• None of the main run axes, such as command axes and positioning axes, which are
traversed with POSA, is stopped.
• Part program command G4 is permitted in the stop delay area. Other part program
commands that cause a stop in the meantime (e.g., WAITM) are not permitted and trigger
"Alarm 16954".
• If a STOP DELAY AREA with an override of 0% is entered, the STOP DELAY AREA will
not be accepted!
Table 2-10 Summary of NCK events, which stop at least for short time
NCK events Response Stop criteria
Reset and mode group RESET immediate IS: DB21, ... DBX7.7 and DB11, ... DBX20.7
PROG_END Alarm 16954 NC prog.: M30
Interrupt delayed IS: "FC-9" and ASUP DB10, ... DBB1
DELDISTOGO_SYNC immediate IS: "Delete distance-to-go" DB21, ... DBX6.2 and axial
PROGRESETREPEAT delayed IS: "Clear number of subprogram passes" DB21, ...
DBX6.3
PROGCANCELSUB delayed IS: "Program level abort" DB21, ... DBX6.4
To Next Page
Loading...
Need help?
General
