ACU-RITE MILLPWR 2 Axes - Manual (Page 65)

PROGRAMMING
MILLPWR ®
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 prece-
dence:
Messages
Tool Change
Spindle Control
Coolant Control
Dwell
Motion
Stop
• When a Z-axis move is required, the program will pause and you will be prompted to
position the Z-axis. Once the Z-axis is in position, pressing
GO will resume program
execution.
• 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
generate 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 mes-
sage.
• 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 interven-
- tion or acknowledgement.
• All tool diameter compensation must be made in CAD/CAM, however, the tool length
offset 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.
Operation Manual 3-36
• Because your MILLPWR is a 2-axis control, G-code pro-
grams must be created for 2-axis operations. All Z-axis info.
must be independent (on a separate line) from X- and Y-axis
information. Arcs can only be performed in the X-Y plane. An
arc or linear move in the X-Z, or Y-Z plane will generate a
RUN TIME ERROR during program execution.