9.12.2
Activation
Setting
Each ASUB channel can be set separately with the following channel-specific machine data:
MD20194 $MC_IGNORE_NONCSTART_ASUP (ASUB start permitted despite pending alarm
response "NC Start disable" for certain user alarms)
A change of the MD setting acts only with the NEWCONF part program command or from the
user interface per softkey.
Sequence
The normal sequence for the ASUB start has the following form:
● Set machine data appropriate with MD20194 $MC_IGNORE_NONCSTART_ASUP and
activate with NEWCONF.
● Start the part program.
A user alarm from the number ranges that can be overridden appears, e.g. alarm 65500.
This can occur from a synchronized action or with a part program command.
● Despite alarm, the part program is processed to the program end M02, M30 or M17.
The Reset channel state is active.
● A started user ASUB from reset is now performed.
Note
An ASUB start from a running or stopped part program is also permitted for a pending "NC
Start disable" alarm response. It is irrelevant whether a user alarm or an NCK alarm with the
"NC Start disable" alarm response is involved.
Note
If the part program is stopped during the processing of the user ASUB, the ASUB can no longer
be continued with the NC Start key, e.g. for M0 in the ASUB or for user stop. The "NC Start
disable" alarm response is rejected with the alarm 16906. The previously generated user alarm
can be acknowledged only with reset.
9.12.3
Examples
9.12.3.1
User ASUB from reset - example 1
MD20194 is not set in the application
Basic Functions
Function Manual, 01/2015, 6FC5397-0BP40-5BA2
K1: Mode group, channel, program operation, reset response
9.12 Perform ASUB start for user alarms
575