Programming instructions

7-6
NC Events NC Programming 17VRS
DOK-MTC200-NC**PRO*V17-ANW1-EN-P
Branch on NC Event to NC Subroutine (Interrupt) ‘BEV’
The BEV command branch on NC NC-event to NC subroutine (interrupt)
is used to activate monitoring of the NC-event specified in the command
parameter. If the NC-event assumes the status "1", processing branches
to the subroutine which is parameterized in the branch label of the BEV
command. A change of the status of low-parity NC-events or of the trig-
gering NC-event is ignored until the end of the subroutine. However, the
program may be interrupted by higher-priority NC-events.
BEV <Branch label> <Event number[0..7]>
BEV .LABEL 4
After the branch from the subroutine, block preparation is resumed at the
beginning of the interrupted NC-block so that this block is now completely
processed to insure that all the functions of the interrupted block are per-
formed. This can lead to unexpected results with incremental program-
ming and incremental variable programming (@01=@01+3).
•
The portion of the NC-program which is processed as a subroutine
must be terminated upon the branch back from the subroutine. Moni-
toring of the triggering NC-event and lower-priority NC-events is re-
sumed automatically.
•
Repeating the assignment of a branch label to an NC-event using the
BEV command overwrites the previous assignment as well as any
different branching behavior defined using the command JEV Jump on
NC NC-event.
•
NC-events can also be changed by the SPS program. Therefore
please refer to the machine builder's information since the builder may
have used various NC-events for synchronization purposes.
Jump on NC Event (Interrupt) ‘JEV’
The JEV command jump on NC NC-event (interrupt)is used to activate
monitoring of the NC-event specified in the command parameter. If the
NC-event assumes the status "1", processing branches to the point in the
NC-program which is parameterized in the jump label of the JEV com-
mand. A change of the status of low-parity NC-events or of the triggering
NC-event is ignored. However, the program may be interrupted by higher-
priority NC-events.
JEV <Branch label> <Event number[0..7]>
JEV .LABEL 4
After the interruption is triggered by the NC-event, the program is contin-
ued at a defined location and it cannot be reset, as is for the case with the
BEV command, by a jump back from a subroutine (RTS) into the inter-
rupted NC-block.
Repeating the assignment of a jump label to an NC-event using the JEV
command overwrites the previous assignment as well as any different
branching behavior defined using the command BEV branch on NC-event
to NC-subroutine (interrupt).
NC-events can also be changed by the SPS program. Therefore please
refer to the machine builder's information since the builder may have used
various NC-events for synchronization purposes.
Syntax
Syntax