Owner's manual

Chapter 30
Using a 9/Series Dual--processing System
3
0
-
8
Synchronization M-codes are ignored during QuickCheck execution and
during a Mid-Program Start operation.
Example 30.1
Example of Synchronization f or Tapping (see Figure 30.1)
Process 1 Comment Process 2 Comment
N10G90 S500G00 X0 Y0; Startspindle andmovetostartpoint
N1 G90 G00 X--2. Y0
S30;
Moveto startpointandstarttapping
spindle
N20 G81 X--1 Y5.5 R3 Z1; Drillinghole atX--1 Y5.5
N2M100; Waitforfirsthole to finish drilling and
clearthe positionfortapping
(process1 block N40)
N30X5.7Y0; Drilling hole atX5.7Y0
N40M100; Release process 2block N3
N3G84X--1Y5.5R3
Z1F20;
Starttapping firsthole
N50 G00 X0 Y0; Move away fromsecondhole fortapping
N4M101; Waitforsecond hole tofinish drilling and
clearthe positionfortapping
(process1 block N60)
N60M101; Release process 2block N5
N5 X5.7 Y0; Starttapping secondhole
N70M30;
N6M30;
Simple Synchronization vs Synchronization with Setup
There are two t ypes of synchronization M-codes. They are:
M100 - M149 — Simple Synchronization. These M-codes a re for
simple synchronization. When executed, this set of M-codes does not
set up any program blocks that have already been read into program
lookahead again.
M150 - M199 — Synchronization with Re-Setup. This set of M-codes
cancels a ny information already in block lookahead and sets up the
blocks again before process execution is resumed. This second setup is
only e ssential when shared information is being changed from one
process to another, as in the case of the dual-processing shared
paramacro parameters.