Haas Automation VF Series, Книга управления

Страница: 43 / 127

36
January 2004
MEM
ORY MODE
MEM
Selects the Memory mode on machine for running programs.
SINGLE BLOCK
Turns single block on so that when the cycle start button is pressed, only one block of the program running is
executed for each press of the cycle start button.
DRY RUN
The DRY RUN function is used to check a program quickly without actually cutting parts. DRY RUN is selected
by pressing the DRY RUN button while in MEM or MDI mode. When in DRY RUN, all rapids and feeds are run
at the DRY RUN speed selected on the JOG speed buttons 100., 10., 1.0 or 0.1 inches per minute. The bottom
of the screen will display the DRY RUN rate that is selected.
DRY RUN cannot be turned on while a program is running. It can only be turned on or off when a program
stopped in a reset condition. The first push of the DRY RUN button turns on this function and the second push
will turn it off. DRY RUN will still make all of the requested tool changes and X, Y, and Z axis moves. The speed
used in DRY RUN can be changed at any time and the operator can then check that the motions that are
programmed are exactly what were intended. Note that Graphics mode is just as useful and may be even safer
since it does not begin moving the machine before the program is checked.
OPT STOP
Turns on optional stops. If an M01 code is encountered in the program and the OPT STOP is selected, a
program stop is executed. Depending on the look-ahead function, it may not stop immediately. If the program
has been interpreted many blocks ahead, and OPT STOP is pressed, then the nearest M01 may not be
commanded. See G103.
1. OPT STOP will take effect on the line after highlighted line, when pressed.
2. M01 is not allowed during cutter compensation. Alarm 349 will be generated in this case, as is M02,
M30, and M00.
BLOCK DELETE
Blocks with a slash (“/”) as the first item are ignored or not executed when this key is enabled. If a slash is in
the middle of a block, address codes after the slash will be ignored, if this key is enabled.
1. When not in cutter compensation, block delete will take effect two lines after BLOCK DELETE is pressed.
2. When in cutter compensation, blocks must be processed earlier. Therefore, block delete will not take
effect until at least four lines after the highlighted line when BLOCK DELETE is pressed.
3. If BLOCK DELETE changes state during the processing of the first block of a chamfering/rounding pair,
and at least one of the pair is block-deleted, the behavior is undefined.
4. Processing will slow down for paths containing block deletes during high-speed machining, because
the look-ahead queue will be emptied as processing approaches the block-deleted line(s). This limits
the speed at which the previous blocks can run.