ACU-RITE MILLPWR 3 Axes - Manual (Page 72)

PROGRAMMING
MILLPWR ®
Operation Manual 3-36
Additional G-code Conventions for MILLPWR
The following lists some of the expectations and limitations of programs imported into MILLPWR .
• 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 22 characters) is displayed to the operator at run-time.
Program execution pauses until the operator acknowledges the message.
• Arcs may only be programmed by endpoint and center. Using endpoint and radius will gen-
erate a run-time error.
• Parametric programming (use of variables or algebraic operations) is not supported.
The characters (#, [,], <, or >) within a block will generate a run-time error.
• Program delimiters (“%”) are ignored. Text following the delimiter is ignored.
• Text following a programming comment character (“;”) 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.
• All tool diameter compensation must be made in CAD/CAM, however, the tool length off
set is read from
MILLPWR ’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.