K1: Mode group, channel, program operation, reset response
9.9 Program operation mode
Basic Functions
584 Function Manual, 09/2011, 6FC5397-0BP40-2BA0
Bahavior for NC Stop
The behavior of the function "event-driven program call" for NC-Stop (i.e. NC/PLC interface signal
DB21,...DBX7.2, 7.3 or 7.4 is set) can be set channel-specific for the triggering event part program end,
operator panel reset and power up with the machine data:
MD20193 $MC_PROG_EVENT_IGN_STOP
In this way, an edge change of the interface signal DB21, ...DBX7.3 (NC-Stop) initiated by the user by activating
the NC Stop key in case of reset or power-up is ignored during the execution of the event-driven user program
and an undesired stop behavior at the machine is prevented.
2 • upon an activation through operator panel reset:
0 is not suppressed.
1 suppressed.
3 • upon an activation through power-up
0 is not suppressed.
1 suppressed.
Note
The system variables $AC_STAT and $AC_PROG are not affected by this function, i.e. in the
running event-driven user program $AC_STAT is set to "active" and $AC_PROG to
"running".
NC/PLC interface signals DB21, ... DBX35.0-7 ("Program status ..." and "Channel status...")
also remain unaffected.
Bit Value Description
The event-driven user program is:
1 • upon an activation through part program end
0 stopped/prevented at NC stop
1 despite NC Stop been completely processed.
2 • upon an activation through operator panel reset:
0 stopped/prevented at NC stop
1 despite NC Stop been completely processed.
3 • upon an activation through power-up
0 stopped/prevented at NC stop
1 despite NC Stop been completely processed.
Note
A programming of DELAYFSTON/ DELAYFSTOF in the event-driven user program cannot be
provided with the behavior set with MD20193, because the NC Stop can cause an
interruption before the execution of the first command DELAYFSTON.
Bit Value Description
To Next Page
Loading...
Need help?
General
