ACU-RITE MILLPWRG2 - Manual (Page 124)

106 6 Programming
6.2 F
o
lders
Additional G-code Conventions for MILLPWR
G2
The following lists some of the expectations and limitations of
programs ran in MILLPWR
G2
.
 Blocks may contain multiple commands and are executed with the
following precedence:
Messages
Tool Change
Spindle Control
Coolant Control
Dwell
Motion
Stop
 Operator comments should be enclosed in parentheses.
 An operator comment with “MSG” appearing within the text is
considered a message. The text following “MSG” (up to 60
characters) is displayed to the operator at run-time. Program
execution pauses until the operator acknowledges the message by
pressing GO. Format is MSG (Operator message) or MSG ("Operator
message").
 Parametric programming (use of variables or algebraic operations) is
not supported.
 Program delimiters (“%”) are ignored. Text following the delimiter
is ignored.
 White space is ignored between parameters but not within a
numeric value or message.
 If a coolant command (M7, M8 and M9) appears in the block, the
Operator Intervention Message is displayed regardless of the
current coolant setting. If AMI hardware is present, the block will
execute without the need for any operator intervention or
acknowledgement.
 Tool length off set is read from MILLPWR
G2
‘s tool library.
For example: In a G-code file, T1 will use the tool length offset from
Tool #1 in the tool library. T2 will use tool length offset from tool
library tool #2, etc.
 The skew feature does not work with G-code programs. Remove
any skew angle prior to running a G-code program.