Anda di halaman 1dari 72

Go to CGTech Help Library

Automating VERICUT
Batch VERICUT
Batch Script Files

Multiple VERICUT batch sessions can be run via a single executable command by
including VERICUT batch commands in an executable script file. The script file is then
submitted to the operating system for processing. After each batch execution terminates,
the operating system then executes the next command in the script file.
Batch files for different operating systems differ slightly in format. Details will follow
later in this document. In general, each batch command in the script file appears as it
would when entered by itself on the command line. Other operating system commands,
such as those that delete or rename files can also be included in the script file.
Tip: VERICUT batch files can be easily created using VERICUT's Batch Wizard.

Windows batch script files


A batch file to be run on Windows is named with a ".bat" extension, for example
"batchfile.bat". Windows NT batch execution lines in the script file are "called" via the
"call" command to return control to the script file after each VERICUT execution. The
examples that follow show two sample script files.
Windows XP batch script file examples:
Example 1 executes two batch sessions, each processing a part unrelated to the other.

call vericut batch "vcp=part1.VcProject"


call vericut batch "vcp=part2.VcProject"

Example 2 represents a part machined in two setups: the first is configured to


automatically save an In-process file named "setup1.ai" via the AutoSave function.
The second uses the ip=<ipfile> option to load the "setup1.ai" In-process file so
cutting can be continued with the session configuration saved in the
"setup2.VcProject" project file.

call vericut batch "vcp=setup1.VcProject"


call vericut batch "vcp=setup2.VcProject" "ip=setup1.ai"
UNIX batch script files
A batch script file to be executed in UNIX must have "executable" permissions. Use the
"chmod" command to give the file executable permissions, for example the following
command makes a file named "batchfile" executable by all users: chmod 777 batchfile
The "batchfile" file is executed via typing the file name on the command line, for
example type: batchfile The examples that follow show two sample script files.

UNIX batch script file examples:


Example 1 executes two batch sessions, each processing a part unrelated to the other.

vericut batch vcp=part1.VcProject


vericut batch vcp=part2.VcProject

Example 2 represents a part machined in two setups: the first is configured to


automatically save an In-process file named "setup1.ai" via the AutoSave function.
The second uses the ip=<ipfile> option to load the "setup1.ai" In-process file so
cutting can be continued with the session configuration saved in the
"setup2VcProject" project file.

vericut batch vcp=setup1.VcProject


vericut batch vcp=setup2.VcProject ip=setup1.ai
Batch Processing

Running VERICUT in batch automates the verification process by loading requested


VERICUT files, processing the NC program file, and exiting VERICUT-all without
opening the VERICUT window. Other command line options are commonly used to
specify the VERICUT Project file(s) and/or IP file(s) needed for the simulation, perform
VERICUT functions, and change VERICUT variable values. See "Command line
options" for more information.
VERICUT is run in batch mode (unattended in the background) by including the "batch"
command line option, or via the Batch Wizard. Another form of batch processing,
"batchp", pops open the VERICUT window when finished to reveal the cut workpiece.
You can run other applications, or perform other tasks while VERICUT is processing in
batch mode.
The same CGTech security and computer resources are required to run VERICUT in
batch as required during interactive processing. Logging out after initiating a batch
session has no affect on the process, as long as the computer remains active.
The following simple examples run VERICUT as configured by the previously created
"part.VcProject" project file:

vericut batch vcp=part.VcProject (UNIX)

vericut batch “vcp=part.VcProject” (Windows)

The values stored in the Project file provide information about the stock model to
machine, tool path file(s) to process, orientations of the models and tool paths, type of
machining to simulate, etc. In this above example the following actions occur:
1. VERICUT is executed.
2. Load the "part.VcProject" project file.
3. Press Play to start the simulation. (Also writes a Log file containing errors and
other information about the simulation.)
4. When finished, exit VERICUT.
For greater automation, multiple batch execution commands can be compiled in an
executable batch script file, as described by the sections that follow.
Batch Wizard

The Batch Wizard graphically guides you through setting up and running Batch Session
Files (.vcs), also called Batch Script Files. Batch mode runs CGTech products
unattended in the background. Command line options and configuration files control the
batch process without opening the VERICUT window. This enables you to run other
applications, or perform other tasks while CGTech products are being productive.
Batch session files created by the Batch Wizard are computer independent, and can be
run on any computer that is capable of running VERICUT.

Accessing the Batch Wizard


Accessing the Batch Wizard is different, depending on the environment in which it is
operated.

• Access the Batch Wizard on a Windows computer — From the Taskbar, click
Start > All Programs > CGTech VERICUT 6.x > Utilities > Batch Wizard
where "6.x" is the desired VERICUT version number.
• Access the Batch Wizard on a UNIX computer — Type "bwizard". If the
command is not found, include the full path, e.g. "/<cgtech6x>/<computer
type>/commands/bwizard" where <cgtech6x> represents the directory path to
where CGTech products were installed, and <computer type> is the type of
computer on which VERICUT is being operated, for example: hp, rs, sgi, or
solaris.
Sample Batch Wizard window:

Batch Wizard Main window


The features on the Batch Wizard main window enable you to create a new batch session
file, modify, and/or run an existing batch session file. Batch session files created by the
Batch Wizard are computer independent, and can be run on any computer that is capable
of running VERICUT.

Main Menu

The menu located across the top of the Batch Session Wizard window provides easy
access to major Batch Wizard functions. Each menu contains groups of related functions.
Left-click on any menu name to display the list of functions in that menu. Click on the
function in the menu that you want to use.

File
Open — Displays a file selection window enabling you to select an existing
Batch Session File (ref. Batch Script Files in the VERICUT Help section, in the
CGTech Help Library)
Save — Use to save the current Batch Session file.
Save As — Save the current Batch Session file under a different name.
Working Directory — Opens the Working Directory selection window enabling
you to specify a working directory.
Run Messages — Opens the Batch Session Wizard Run Messages window. This
window contains the same information as the Batch Session Run Status area of
the Batch Wizard main window, described below, but enables you to see large
numbers of status messages at the same time.
Exit — Use to exit, and close, the Batch Wizard window.

Operations
Run — Use to run the current Batch Session file. This provides the same
functionality as the Run button described below.
Edit — Opens the Batch Session Wizard Editor window enabling you to add,
modify, or delete operations from an existing Batch Session file, or to add
operations to create a new Batch Session file. This provides the same
functionality as the Edit button, described below.

Help
On Automating VERICUT — Opens the Automating VERICUT section of the
CGTech Help Library.
Current Batch Session File

The /path/filename of the current Batch Session file, as well as a list of the operations
contained in it, are displayed in this part of the Batch Wizard main window.

Run — Use to run the current Batch Session file. This provides the same functionality as
the Operations > Run feature in the main menu, described above.
Edit — Opens the Batch Session Wizard Editor window enabling you to add, modify, or
delete operations from an existing Batch Session file, or to add operations to create a new
Batch Session file. This provides the same functionality as the Operations > Edit feature
in the main menu, described above.

Batch Session Run Status

The bottom portion of the main window shows the status of the of the Batch Session file
that is running. Information like which operations have finished executing, errors related
to those operations, which operation is currently executing, as well as notification when
the Batch Session file is finished running.
Tip: You can change the size of the Current Batch Session File list area and the Batch
Session Run Status listing area by lecft-clicking on the divider between these two areas
and dragging up or down. Dragging the divider up makes the Batch Session Run Status
area larger and the Current Batch Session File area smaller. Dragging the divider down
has the opposite effect.

Batch Session Editor window


Accessed using the Edit button on the Batch Wizard Main window, the features on this
window are used to add, modify, or delete batch operations in the current Batch Session
file.
In general, press Next to go to the next window, Back returns to the previous window.
When the batch session setup is complete, you return to the Batch Wizard Main window
where you can save, and then run the batch session file.
The following describe that Batch Wizard windows that guide you through the process of
setting up a batch session file.

Main window
Add — Opens the CGTech Product window enabling you to start adding a new operation
to the current Batch Session file. The new operation is added at the end of the operation
list. You can then use Move Up feature, described below, to change its position in the
Operation list.
Modify — Opens the CGTech Product window enabling you to modify an existing
operation. Select the operation that you want to modify so that it becomes highlighted,
then select Modify open the CGTech Product window.

Operations are performed in order that they appear in the Operation list. Use the Move
Up / Move Down buttons to change an operation's position in the list.
Move Up — Each time you click on the Move Up button, the highlighted operation
moves one position higher in the Operation list.
Move Down — Each time you click on the Move Down button, the highlighted
operation moves one position lower in the Operation list.
Delete — Use to delete the highlighted operation from the Operation list.
Delete All — Use to delete all operations from the Operation list.

OK — Use OK to accept all of the changes that you made while in the Batch Session
Wizard Editor, close the Batch Session Wizard Editor window, and return to the Batch
Wizard Main window where you can save the Batch Session file, and then run it.
NOTE: Using OK adds the changes you made in the editor to the active copy of the
current Batch Session file. The changes are not permanently saved until you use Save or
Save As in the File menu in the Batch Wizard Main window.
Cancel — Close the Batch Session Wizard Editor window without adding any changes to
the active copy of the current Batch Session file, and returns to the Batch Wizard Main
window.
CGTech Product window
This screen is used to specify which CGTech product will be run in the batch operation.
The choices include VERICUT, VERICUT Converters, or Operating System Commands.

Name of the current operation — Use the text field to enter name for a new operation,
or edit the name of an existing operation. Operations can be named anything you like.
Product — Select one of the products from the list to be run in the batch operation.
Vericut — Use VERICUT for the batch operation.
Iges2v — Use the IGES Converter (ref. IGES Converter, in the VERICUT
Converters and CAD/CAM Interfaces section, in the CGTech Help Library) for the
batch operation.
Bincl2v — Use the Binary CL Converter (ref. Binary CL Converter, in the
VERICUT Converters and CAD/CAM Interfaces section, in the CGTech Help
Library) for the batch operation.
PolyFix — Use the PolyFix Converter (ref. PolyFix Converter, in the VERICUT
Converters and CAD/CAM Interfaces section, in the CGTech Help Library) for the
batch operation.
Sur2stk — Use the Surface to Solid Converter (ref. Surface to Solid Converter, in
the VERICUT Converters and CAD/CAM Interfaces section, in the CGTech Help
Library) for the batch operation.
VDA — Use the VDAFS Converter (ref. VDASF Converter, in the VERICUT
Converters and CAD/CAM Interfaces section, in the CGTech Help Library) for the
batch operation.
BWizard — Use Batch Wizard to run the batch operation.
O.S.Commands — Use an operating system command to assist with batch
processing.
Command used to execute the product — Use the text field to enter the command to
start the selected product.

Back — Returns to the Batch Session Wizard Editor Main window without making any
changes.
Next — The Next button will behave differently depending on the product that has been
selected (highlighted) for the batch operation.
If O.S.Commands is highlighted, the Next button will display the Operating System
Command Options window enabling you to specify operating system commands to
assist with batch processing, such as: copy, move, append, rename, and set
environment variables.
If any product other than O.S.Commands is highlighted, the Next button will display
the Command Line Options window, with the command line options that are
appropriate for the highlighted product display in the Available Options list of the
window.
For information on specific command line options, refer to Command Line Options
for VERICUT, and Command Line Options for CGTech Converters, also in the
Automating VERICUT section of the CGTech Help Library.
Command Line Options window
Accessed by selecting the Next button in the CGTech Products window when any
product other than O.S.Commands is highlighted, the Command Line Options window is
used to choose one, or more, command line options for the product being run in batch.
The command line options in the Options Available list are specific to the product that
was highlighted in the CGTech Product window.

Options Available list — The command line options that appear in the Options
Available list are specific to the CGTech product that is specified to run this operation.
Selecting an item in the list causes it to become highlighted. If the selected item requires
a file to be specified, it will display in the text field below the Options Available list so
that you can enter the /path/filename of the required file. You can also click on (File
Selection) to display a file selection window and use it to specify the /path/filename.
Click on (Add) to add the highlighted command line option to the Options Selected
list.
(Move Up) — Use to change the order of the items in the Options Selected list.
Each time you click on the button, the highlighted option moves one position higher in
the list.

(Move Down) — Use to change the order of the items in the Options Selected list.
Each time you click on the button, the highlighted option moves one position lower in the
list.

(Add) — Adds the option highlighted in the Available Options list to the Options
Selected list.

(Remove) — Removes the option highlighted in the Options Selected list from the
list.

(File Selection) — Displays a File Selection window enabling you select the
/path/filename for command line options requiring a file to be specified.

Options Selected list — The command line options that appear in the Options Selected
list are the command line options that will be executed for the operation when you run the
Batch Session file. Be sure to include one of the batch options (batch or batchp) to run
the CGTech product in batch mode.

Back — Returns to the CGTech Product window without making any changes.
Next — Accepts the operation values as you defined them, closes the Command Line
Options window and returns to the Batch Session Wizard Editor window.

For information on specific command line options, refer to Command Line Options for
VERICUT, and Command Line Options for CGTech Converters, also in the Automating
VERICUT section of the CGTech Help Library.
Operating System Command Options window
Accessed by selecting the Next button in the CGTech Products window when
O.S.Commands is highlighted, the Operating System Command Options window is used
to add operating system commands to the batch session file to assist with batch
processing.

When you select one of the operating system command types in the upper part of the
window, the lower part of the window will change to help guide you through specifying
the information necessary for the selected operating system command.
As you will see in the following examples you can use simple inputs, as well as use
wildcards (*.log, *.*, etc.), "relative" directory paths, and environment variables to define
the operating system commands.

In all cases, you can use (File Selection) to display a file selection window to assist
you in specifying the required /path/filename(s).
Copy file(s) — Enables you to copy one, or more, file(s) from one directory to another.
Enter the /path/filename(s) of the file(s) to be copied in the From text field, or use the file
selection icon to open a file selection window and use it to assist you in specifying the
/path/filename(s). Similarly, use the To text field to specify the new /path/filename(s) of
the new location.

Delete File(s) — Enables you to delete one, or more, file(s). Enter the /path/filename(s)
of the file(s) to be deleted in the text field, or use the file selection icon to open a file
selection window and use it to assist you in specifying the /path/filename(s).

Move File(s) — Enables you to move one, or more, file(s) from one directory to another.
Enter the /path/filename(s) of the file(s) to be moved in the From text field, or use the
file selection icon to open a file selection window and use it to assist you in specifying
the /path/filename(s). Similarly, use the To text field to specify the new /path/filename(s)
of the new location.

Rename File(s) — Enables you to rename one, or more, file(s). Enter the
/path/filename(s) of the file(s) to be renamed in the From text field, or use the file
selection icon to open a file selection window and use it to assist you in specifying the
/path/filename(s). Similarly, use the To text field to specify the new file names.
Append one file to another — Enables you to append the contents of one file to the end
of another file. Enter the /path/filename(s) of the file containing the data that you want to
append in the From text field, or use the file selection icon to open a file selection
window and use it to assist you in specifying the /path/filename. Similarly, use the To
text field to specify the /path/filename of the file that you want the data appended to.

Set Environment Variable — Enables you to set the value of an environment variable.
Enter the name of the environment variable to be set in the Environment Variable text
field. Enter the value of the environment variable in the To text field. Use the file
selection icon to open a file selection window and use it to assist you in specifying the
value of the environment variable if appropriate.

Other — Enables you to define a generic operating system command. Enter any
command that your operating system will understand in the text field. Use the file
selection icon to open a file selection window and use it to assist you in specifying the
operating system command if appropriate.

Back — Returns to the CGTech Product window without making any changes.
Next — Accepts the operating system commands as you defined them, closes the
Operating System Command Options window, and returns to the Batch Session Wizard
Editor window.
Configuring for Batch Process Output

Output from running VERICUT in batch always includes a Log file. VERICUT can also
be configured to automatically perform many operations, or output many different types
of files. The following sections describe how to configure VERICUT for batch process
output.
See the VERICUT Help section, in the CGTech Help Library, for additional information
on any of the VERICUT windows, or files, referred to in the following examples.

To batch save IP or View Capture files:


1. Configure VERICUT for processing the desired Project file (models, NC
Programs, tools, etc.)
2. Click File menu > AutoSave to display the AutoSave window.
3. Click on either the In Process tab (if configuring to automatically save IP files),
or the View Capture tab (if configuring to automatically save View Capture
image files). If saving View Capture image files, then click on Properties on the
View Capture tab to display the View Capture window and use its features to
configure the desired image file format.
4. In either case, use the Auto Save features select the event(s) and enter supporting
data that will cause VERICUT to automatically save the file. Type the name to be
used for the file in the text field, or click on Browse and use the window that
displays to specify the /path/filename for the file.
5. Use the Auto Error features to have VERICUT automatically save the file when
an error is encountered. Toggle the "On" checkbox on and type the name to be
used for the file in the text field, or click on Browse and use the window that
displays to specify the /path/filename for the file.
NOTE: If using both Auto Save and Auto Error, be sure to use different file
names for each to avoid overwriting.
6. Press OK.
7. Save a Project file (or IP file) to be used during the batch process, for example
"test.VcProject"
8. Exit VERICUT
9. To start batch processing use the Batch Wizard, or execute VERICUT with
vcp=<file> and batch (or batchp) command line options, for example:

vericut batch vcp=test.VcProject


To batch record VERICUT Image files:
1. Configure VERICUT for processing the desired project file (models, tool path,
tools, etc.)
2. Click File menu > Images > Record Movie to display the Image Record
window.
3. Configure the window as desired to record snapshot or animation images.
4. Press Record, then Stop, to retain Image Record window changes.
5. Close the Image Record window.
6. Save a Project file (or IP file) to use during the batch process, for example
"test.VcProject"
7. Exit VERICUT
8. To start batch processing use the Batch Wizard, or execute VERICUT with
vcp=<file>, record, and batch (or batchp) command line options, for example:
vericut batch vcp=test.VcProject record

To append to an existing Image file, include the "IMRCAPDT=on" option, for


example:
vericut batch vcp=test.VcProject record IMRCAPDT=on

To batch compare design models using AUTO-DIFF:


1. Configure VERICUT for processing the desired project file (models, tool path,
tools, etc.)
2. Depending on the AUTO-DIFF comparison method to be used, ensure a Design
Solid, Surface or Point model is loaded (ref. Modeling Window in the VERICUT
Help section).
3. Click Analysis menu > AUTO-DIFF to display the AUTO-DIFF window.
4. Configure the AUTO-DIFF features as required to compare with the design model
and show gouge, and/or excess conditions.
5. Press Apply, and then close the AUTO-DIFF window.
6. Save a Project file (or IP file) to use during the batch process, for example
"test.VcProject"
7. Exit VERICUT
8. To start batch processing use the Batch Wizard, or execute VERICUT with
vcp=<file>, auto-diff=<reportfilename>, and batch (or batchp) command line
options, for example:
vericut batch vcp=test.VcProject auto-diff=test.rpt
To batch optimize tool path files using OptiPath:
1. Configure VERICUT for processing the desired project file (models, tool path,
tools, etc.), and optimizing the desired tools.
The following steps assuming an OptiPath Library file exists containing the desired
optimization data, and that VERICUT has already been configured to optimize tool paths.
If the library does not exist or does not contain all of the desired optimization data, use
the OptiPath window to create this file. Use the Tool Manager window, the OptiPath
window, and the OptiPath Control window features to configure VERICUT for
optimization.

1. Click OptiPath menu > Control to display the OptiPath Control window.
2. Ensure the window is configured as required (OptiPath Library file name,
Material, Machine, etc.) to optimize the desired tools. Do not turn optimization
On in this window to start tool path optimization, as this will be done via the
"optimize" command line option.
3. Press OK.
4. Save a Project file (or IP file) to use during the batch process, for example
"test.VcProject"
5. Exit VERICUT
6. To start batch processing use the Batch Wizard, or execute VERICUT with
vcp=<file>, optimize, and batch (or batchp) command line options, for example:

vericut batch vcp=test.VcProject optimize


Command Line Options
Command Line Options for VERICUT

Command line options configure and control VERICUT upon execution. Command line
options are particularly useful in customizing the user interface for specific site use, or
during batch processing as described in "Batch Processing".
See the VERICUT Help section, in the CGTech Help Library, for additional information
on any of the VERICUT windows, or files, referred to in the following section.
Available command line options are listed in alphabetical order in the following table.
Each is described in detail below. Options can be arranged on the command line in any
order.

Command line option: General description:

Sets a user variable (value in the user


<uservariablename>=<uservalue>
interface)

append_log Open Log file in append mode

Perform an AUTO-DIFF model comparison


auto-diff=<reportfilename>
and write results to a file

Runs VERICUT in the background, without


batch
opening the user interface

Similar to batch, except "pops open" the


batchp
VERICUT window when finished

Processes the "Burn" function in a Die


burn
Sinking Simulation

Reads the specified CSYS File and creates a


csys_file=<filename>
VERICUT coordinate system.

Imports DXF 2D geometry and creates a


dxf2sweep
"sweep" solid model

dxf2sor Imports DXF 2D geometry and creates a


"solid of revolution" solid model

export Exports the VERICUT cut model

fitall Fits all open views

hres=<value> Sets the horizontal screen display resolution

Appends recorded images to an existing


IMRCAPDT=on
Image file

ip=<ipfile> Loads an In Process file

LGFILNAM=<logfilename> Set the Log file name

ops=</path/filename> Creates an Operations file

optimize Turns OptiPath on

record Records VERICUT images to an Image file

report=<filename> Creates a VERICUT report file

Specifies the VERICUT report template file


report_template=<filename>
to use for creating a VERICUT report.

reset_cutcolor Resets cut colors of all machine cuts

reset_log Reset the Log file

reverse Reverses the active view

Open a stand-alone Tool Manager window


toolman.bat
Upgrade an old tool library file in batch

usr=<usrfile> Loads a User file

vcp=<file> Loads a Project file

Plays back the specified VERICUT image


VericutPlayer
file.
vres=<value> Sets the vertical screen display resolution

Zooms out approximately 20% for each


zoom_out[=<value>]
"zoom_out"

NOTE: If the option you are looking is not listed above, see "Obsolete command line
options" at the end of this section.
WINDOWS NOTE: Command line options containing an assignment ("=") must be
surrounded with double quotes, for example: vericut "usr=part.usr"
Command Line Option Details

<uservariablename>=<uservalue>
Use to specify a user variable, and corresponding value, to be set in the user interface.
Also known as a "user variable override", user variables and values entered on the
command line are not case sensitive. However, some operating systems use case
sensitivity when reading directory paths and file names. Consult your operating system
guide to determine if case sensitivity applies.
Windows example:
vericut "FASTFEED=500"

UNIX example:
vericut FASTFEED=500

When combined with other command line options that affect project values, the options
are processed in the order listed below. Processing order is the same regardless of the
order in which they are listed on the command line.
The order in which command line options affecting project values are processed:
1. ip=<ipfile> — load VERICUT model
2. usr=<usrfile> — load complete set of user values
3. vcp=<file> — load complete set of project values
4. <uservariablename>=<uservalue> — load individual user values

NOTES:
1. Specific spelling and formats apply. To see a list of VERICUT user variable
names/values, view any Project file saved from the current version of VERICUT.
The middle column lists user variables, while the right column indicates the saved
user values for corresponding user variables.
2. When specifying multiple word user values join the words with an underscore
("_").
append_log
When VERICUT is run and an existing Log file is detected, the Log file is opened in
"append" mode. Additional log messages are appear at the end of the file.
Also see: reset_log and LGFILNAM=<logfilename>.

auto-diff=<reportfilename>
Performs an AUTO-DIFF model comparison and writes results to the specified AUTO-
DIFF Report file. The comparison method and tolerances used are controlled via the
AUTO-DIFF window. The comparison is performed when tool path processing has
finished. Immediately afterwards, VERICUT automatically restores the model to its "as
machined" state, as it was prior to differencing.
This option is commonly used during batch processing to automatically inspect the part
after machining.

batch
Runs VERICUT in the background, without opening the user interface. In this mode,
VERICUT loads specified IP, User, or Project files (in listed order), processes the tool
path file(s), and exits-without user interaction. The "batch" option can appear anywhere
on the command line. Examples follow.
Windows examples:
vericut batch "vcp=part.VcProject"
vericut "vcpr=C:\ncparts\part.VcProject" batch

UNIX examples:
vericut batch vcp=part.VcProject
vericut vcp=/ncparts/part.VcProject batch

For step-by-step examples of how to accomplish popular tasks via batch processing, see
"Batch processing".

NOTES:
1. The same CGTech security and computer resources are required to run VERICUT
in batch mode as required during interactive processing.
2. Logging out after initiating a batch session has no affect on the process, as long as
the computer remains active.
3. Another form of batch processing, batchp, "pops open" the VERICUT window
when finished to reveal the cut workpiece.
4. A "Batch Wizard" provides a guided, graphical method of creating and running
CGTech products in batch mode.
See "Batch processing" for details.

batchp
Similar to batch, except when finished the VERICUT window "pops open" to reveal the
cut workpiece. The model can then be analyzed or saved for later use.
See "Batch processing" for details.

BKGNCLR
Use to specify the Background color.
"BKGNCLR=0 0 255 Blue" where "0 0 25 Blue" represents the color identifier
from the Color window Color List.
See Color window: Define tab, Color List in the VERICUT Help section, in the
CGTech Help Library, for more information.

burn
Executes the processing of the "Burn" feature of a Die Sinking Simulation. The burn
operation is performed when NC program processing has finished.

csys_file=<filename>
Reads the specified CSYS File and creates one or more VERICUT coordinate systems. If
this command line argument is used, then VERICUT does not create CSYS's when
processing the NC program file. This command provides the same functionality as the
CSYS from File feature in the Coordinate System window.
dxf2sor [argument list]
Enables you to import two dimensional geometry from files which comply with a de
facto CAD system standard, the Data eXchange Format (DXF) to define a "closed" 2-D
profile that can be "revolved" about the Z-axis to create solid model.
Arguments:
"input=<dxf_filename>" (Required)
(dxf_filename is a fully qualified filename, including the directory path, of a DXF file
containing at least one closed profile)

["output=<sor_filename>"] (Optional)
(sor_filename is a fully qualified filename, including the directory path, of the output
SOR file)
NOTE: If "output" is not specified, the resulting output file will default to the name
of the DXF file, without the extension, with a ".sor" extension added
(dxf_filename.sor). If the output file already exists, it is overwritten.

["layer=<layerame>"] (Optional)
(layername is a fully qualified filename, including the directory path, of the output
SOR file)
NOTE: IF "layer" is specified, only entities on the specified layer will be
converted. If "layer" is not specified, entities on all layers will be converted

["Help"] (Optional)
Prints out the valid arguments.

NOTE: This functionality is also available as a stand-alone utility on Windows.


Execute dxf2sor.bat, located in the "commands" directory of your VERICUT
installation, with the appropriate arguments.

dxf2sweep [argument list]


Enables you to import two dimensional geometry from files which comply with a de
facto CAD system standard, the Data eXchange Format (DXF) to define a "closed" 2-D
profile that can be "swept" a specified thickness along an axis to create solid model. The
program that takes a DXF profile, sweeps it along the positive Z-axis the specified
distance, and then outputs it to a VERICUT sweep file.

Arguments:
"input=<dxf_filename>" (Required)
(dxf_filename is a fully qualified filename, including the directory path, of a DXF file
containing at least one closed profile)

"length=(sweep model thickness)" (Required)


(sweep model thickness is the distance to sweep the 2D DXF profile along the positive Z
axis)

["output=<sweep_filename>"] (Optional)
(sweep_filename is a fully qualified filename, including the directory path, of the output
SWEEP file )
NOTE: If "output" not specified, the resulting output file will default to the name
of the DXF file, without the extension, with a ".swp" extension added. If the output file
already exists, it is overwritten.

["layer=<lay1_name, lay2_name, ...>"] (Optional)


(lay1_name, lay2_name, ... is the name of the layer containing the DXF entities )
NOTE: IF "layer" is specified, only entities on the specified layer(s) will be converted.
If "layer is not specified, all entities will be converted

It is possible to have multiple closed profiles that represent holes in the interior of the
model. If multiple profiles exist, they must conform to the following:
1. cannot intersect other profiles
2. cannot self-intersect
3. inner profiles must be completely contained by the outer profile
4. cannot be contained by any other profile
5. all entities of a closed profile must have same layer name

NOTE: This functionality is also available as a stand-alone utility on Windows.


Execute dxf2sweep.bat, located in the "commands" directory of your VERICUT
installation, with the appropriate arguments.
export
Exports the VERICUT cut model. The method and tolerances used are controlled via the
File menu > Save Cut Stock > CAD Model window configuration. The export
operation is performed when NC program processing has finished.

fitall
Fits all open views. Use this option to ensure models of the workpiece, holding fixtures,
and NC machine are fit completely within all open views.

FLATBG
Sets all View backgrounds to the "Flat Background Color".

hres=<value>
Sets the screen display resolution in the horizontal direction. The value entered is in
pixels.
Also see: vres=<value>.

IMRCAPDT=on
Actually a user variable override, this option is used with the "record" option to append
images recorded via the File menu > Images > Record Movie function to an existing
Image file.

ip=<ipfile>
Loads an existing In-process file into VERICUT. The full directory path can be included
with the file name. The examples that follow assume an In-process file named "part.ip"
has been saved.
Windows examples:
vericut "ip=part.ip"
vericut "ip=C:\ncparts\part.ip"
UNIX examples:
vericut ip=part.ip
vericut ip=/ncparts/part.ip

When combined with other command line options that affect user values, the options are
processed in the order listed below. Processing order is the same regardless of the order
in which they are listed on the command line.
The order in which command line options affecting user values are processed:
1. ip=<ipfile> — load VERICUT model
2. usr=<usrfile> — load complete set of user values\
3. vcp=<file> — load complete set of project values
4. <uservariablename>=<uservalue> — load individual user values

LGFILNAM=<logfilename>
Actually a user variable override, this option sets the name of the Log file to receive
error, warning, and informational messages resulting from processing a tool path in
VERICUT.
Also see: append_log and reset_log.

ops=</path/filename>
An Operations File, or Ops File, can be used to assemble a project with multiple setups
from several VERICUT project files, which typically have the extension ".VcProject".
This assembly process can only be triggered from the command line that invokes
VERICUT. The necessary command line syntax is;

For Windows ... "ops=D:\My\Path\MyOperationsFile.VcTmp" ...

For UNIX ... "ops=/My/Path/MyOperationsFile.VcTmp" ...

Any extension can be used in the file name, but by convention ".VcTmp" denotes a
temporary file.
optimize
Turns OptiPath on for optimizing tool path feed rates and/or spindle speeds. Cutting tools
optimized and optimization values used are controlled via the Project menu > NC
Programs and OptiPath menu > Control window configurations.

record
Records VERICUT session images to an Image file, as specified by the File menu >
Images > Record Movie window configuration. When record is used with the
IMRCAPDT=on option, images are appended to the end of the file.

report
Use to generate a VERICUT report in "batch". Using the command line option "report",
the VERICUT report file name and report template file stored in the VERICUT Project
file is used. Use the command line option "report_template", described below, to specify
a different report template file.
Use the command line option "report=<filename>", to specify using a different report
file than the one stored in the VERICUT Project file. The report format (text, HTML,
PDF) is defined by the report file extension (.txt, .html, .pdf) of report file name. Default
format is HTML. Use the command line option "report_template", described below, to
specify using a different report template file than the one stored in the VERICUT Project
file.
See Introduction to VERICUT Reports in the VERICUT Help section, in the CGTech
Help Library, for more information.

report_template
Use the command line option, "report_template=<filename>", to specify the report
template file to be used for generating a VERICUT report.

reset_cutcolor
Resets the cut colors of all machine cuts to be one color: the Reset Cut color. Cut colors
are reset prior to cutting.
reset_log
When VERICUT is run and an existing Log file is detected, the Log file is reset (cleared)
prior to writing new log messages.
Also see: append_log and LGFILNAM=<logfilename>.

reverse
Reverse the active view prior to cutting. This option is useful when recording images and
tool motion occurs on the opposite side of the model.
See "Reverse" in the View menu > Orient window for more information.

toolman.bat [argument list]


Enables you to open a stand-alone Tool Manager window with a specied VERICUT tool
library (.tls) file. You can also use it to upgrade an old tool library (.tls) file to the current
version in batch mode.

Arguments:
"filename"
(filename is a fully qualified filename, including the directory path, of a VERICUT tool
library file (.tls) )

"tls=oldlibname"
(oldlibname is a fully qualified filename, including the directory path, of an existing
VERICUT tool library file (.tls) )
This argument is optional and only valid when there is an "oplib" defined.

"oplib=oldoplibname"
(oldoplibname is a fully qualified filename, including the directory path, of an existing
OptiPath library file(.olb) )
This argument is optional. If specified, the OptiPath information will be merged into the
upgraded tool library file.

"upgrade"
"output=newlibname"
(newlibname is a fully qualified filename, including the directory path, for the upgraded
VERICUT tool library file)
This argument is optional. If not specified the upgraded tool library name will default to
oldlibname_[current version].tls

Example 1:
Open a stand-alone Tool Manager window with a specified VERICUT Tool Library file.
Syntax:
toolman.bat filename
Sample command:
C:\cgtech62\windows\commands\toolman.bat C:\test\new_op_aero.tls

Example 2:
Upgrade an old tool library (.tls) file to the current version in batch mode.
Syntax:
toolman.bat "tls=oldlibname" "oplib=oldoplibname" upgrade "output=newlibname"
Sample command:
C:\cgtech62\windows\commands\toolman.bat
"tls=C:\cgtech545\samples\op_aero.tls" "oplib=C:\cgtech545\samples\op_aero.olb"
upgrade "output=C:\test\new_op_aero.tls"

usr=<usrfile>
Loads an existing user file into VERICUT. The full directory path can be included with
the file name. The examples that follow assume a User file named "part.usr" has been
saved.
Windows examples:
vericut "usr=part.usr"
vericut "usr=C:\ncparts\part.usr"

UNIX examples:
vericut usr=part.usr
vericut usr=/ncparts/part.usr
When combined with other command line options that affect user values, the options are
processed in the order listed below. Processing order is the same regardless of the order
in which they are listed on the command line.
The order in which command line options affecting user values are processed:
1. ip=<ipfile> — load VERICUT model
2. usr=<usrfile> — load complete set of user values
3. vcp=<file> — load complete set of project values
4. <uservariablename>=<uservalue> — load individual user values

vcp=<file>
Loads an existing Project file into VERICUT. The full directory path can be included
with the file name. The examples that follow assume a Project file named
"part.VcProject" has been saved.
Windows examples:
vericut "vcp=part.VcProject"
vericut "vcp=C:\ncparts\part.VcProject"

UNIX examples:
vericut vcp=part.VcProject
vericut vcp=/ncparts/part.VcProject

When combined with other command line options that affect user values, the options are
processed in the order listed below. Processing order is the same regardless of the order
in which they are listed on the command line.
The order in which command line options affecting user values are processed:
1. ip=<ipfile> — load VERICUT model
2. vcp=<file> — load complete set of project values
3. <uservariablename>=<uservalue> — load individual user values

VericutPlayer [argument list]


Enables you to open a "VERICUT Player" window and play back an Image file recorded
using the File menu > Images > Record function or the record command line option.
Arguments:
"filename"
(filename is a fully qualified filename, including the directory path, of a VERICUT
Image file)

"impbfil=(filename)"
(filename is a fully qualified filename, including the directory path, of a second
VERICUT Image file to play both Image files simultaneously)

"impbspdp=(value)"
(value, entered as a percent, controls how fast images are played back )

"impberrt=value)"
(value is either "on" or "off"; when value=on, playback stops when an error is
detected by VERICUT )

"impbchgt=value)"
(value is either "on" or "off"; when value=on, playback stops when the cutter
changes)

"impbnevt=value)"
(value is either "on" or "off"; when value=on, playback stops every "N" events
(frames). Use "impbneve=value" to specify "N")

"impbeoft=value)"
(value is either "on" or "off"; when value=on, causes playback to stop when the end
of an NC program file has been reached )

"impbneve=value)"
(value is the number used to specify the number of events (frames) that causes
playback to stop when "impbnevt=on)" as described above)

"impbstop=value)"
(value is either "on" or "off"; when value=on, playback stops at an "inserted stop")
"impbloop=value)"
(value is either "on" or "off"; when value=on, causes playback to loop continuously
until interactively stopped by pressing the Escape key <Esc> )

"impbssd=value)"
(value is the number of seconds to pause after displaying a snapshot)

NOTE: This functionality is also available as a stand-alone utility on Windows.


Execute player.bat, located in the "commands" directory of your VERICUT installation,
with the appropriate arguments.

vres=<value>
Sets the screen display resolution in the vertical direction. The value entered is in pixels.
Also see: hres=<value>.

zoom_out[=<value>]
Zooms out, or decreases the viewing size of uncut stock models by approximately 20%
for each "zoom_out" listed. For example, "zoom_out" zooms out one step, while
"zoom_out=2" zooms out twice.
See "Zoom Out" in the View menu > Orient window for more information.
Obsolete command line options
The command line options listed below are obsolete in this version of VERICUT.
Recommended alternate command line options are recommended where possible.
autodemo = <imgfile> — Not supported.
batcht — "True batch", obsolete- use "batch" instead.
OpenGL — Not supported.
pbappend — Obsolete- use "IMRCAPDT=on" instead.
pseudocolor — No longer applies.
results — No longer applies.
slice — Not supported in this release.
statdisp = <computername> — Not supported.
truecolor — No longer applies.
Command Line Options for CGTech Converters

CGTech converter products provide a way to translate a wide variety of CAD/CAM data,
primarily for use in VERICUT. All converters can be run interactively, or in batch mode.
When run in batch, command line options are used to configure the converters without
the use of the user interface.
The sections that follow describe command line options available for CGTech converter
products. See the appropriate section for details.

WINDOWS NOTE: Command line options containing an assignment ("=") must be


surrounded with double quotes, for example: iges2v "input=inputfile.igs"

Binary CL Converter command line options


Syntax: bincl2v [argument list]
Command line options available for the Binary CL Converter are described in the table
below.

Option Description Default

batch Execute without user interface

batcht (obsolete) Same as "batch"

input=input-file Binary CL Input File

output=output-file Output File (ASCII APT)

aptwords.tbl
table=table-file APT Table File
(CGTech library)

Input File Type:


cltype={1|2|3|4} 1
1=IBM,2=IBMWS,3=CATWS,4=VAXWS

circles={YES|NO} Output Circles Yes

height=value Minimum Cutter Height 0


NOTE: This functionality is available as a stand-alone utility on Windows. Execute
bincl2v.bat, located in the "commands" directory of your VERICUT installation, with
the appropriate arguments.

See Binary CL Converter, in the Converters and CAD/CAM Interfaces section of the
CGTech Help Library for additional information.
CAD Converter command line options
Syntax: cad2v [argument list]
Command line options available for the CAD Model Converter are described in the table
below.

Option Description Default

Execute without user


batch
interface

input=input-file CAD Input File

output=output-file Output File

dtol=value Deviation Tolerance 0.05

format={ASCII|BINARY} Output File Format BINARY

type={VERICUT|STL} Output File Type STL

dir={INWARD|OUTWARD} Normal Direction OUTWARD

NOTE: This functionality is also available as a stand-alone utility on Windows.


Execute cad2v.bat, located in the "commands" directory of your VERICUT installation,
with the appropriate arguments.

See CAD Model Converter, in the Converters and CAD/CAM Interfaces section of the
CGTech Help Library for additional information.
IGES Converter command line options
Syntax: iges2v [argument list]
Command line options available for the IGES Converter are described in the table below.

Option Description Default

Execute without user


batch
interface

batcht (obsolete) Same as "batch"

input=input-file IGES Input File

output=output-file Output File

0.05 for in. model, 1.27


dtol=value Deviation Tolerance
for mm model

format={ASCII|BINARY} Output File Format BINARY

type={VERICUT|STL} Output File Type STL

mode={TRIMMED|BASE|ALL} Surface Input Mode ALL

dir={INWARD|OUTWARD|GUESS} Normal Direction OUTWARD

Summary of input file


summary
contents

NOTE: This functionality is also available as a stand-alone utility on Windows.


Execute iges2v.bat, located in the "commands" directory of your VERICUT installation,
with the appropriate arguments.

See IGES Converter, in the Converters and CAD/CAM Interfaces section of the CGTech
Help Library for additional information.
PolyFix Converter command line options

Syntax: polyfix [argument list]


Command line options available for the IGES Converter are described in the table below.

Option Description Default

Execute without user


batch
interface

batcht (obsolete) Same as "batch"

input=input-file Input File

intype={VERICUT|STL} Input File Type STL

output=output-file Output File

outformat={ASCII|BINARY} Output File Format BINARY

outtype={VERICUT|STL} Output File Type STL

NOTE: This functionality is also available as a stand-alone utility on Windows.


Execute polyfix.bat, located in the "commands" directory of your VERICUT installation,
with the appropriate arguments.

See Polyfix Converter, in the Converters and CAD/CAM Interfaces section of the
CGTech Help Library for additional information.
Surface to Solid Converter command line options
Syntax: sur2stk [argument list]
The command line options available for the Surface to Solid Converter are described in
the table below.

Option Description Default

Execute without user


batch
interface

batcht (obsolete) Same as "batch"

input=input-file IGES Input File

output=output-file Output File

tol=value Tolerance

intype={VERICUT|STL} Input File Type

outtype={VERICUT|STL} Output File Type

format={ASCII|BINARY} format={ASCII|BINARY} BINARY

matrix=matrix-string Transformation Matrix Identity matrix

offset=value surface Offset 0

base=value Base Location 0

rectangle={NO|YES} Project Rectangle NO

NOTE: This functionality is also available as a stand-alone utility on Windows.


Execute sur2stk.bat, located in the "commands" directory of your VERICUT
installation, with the appropriate arguments.

See Surface to Solid Converter, in the Converters and CAD/CAM Interfaces section, in
the CGTech Help Library for additional information.
VDA Converter command line options

Syntax: vda [argument list]


Command line options available for the VDA Converter are described in the table below.

Option Description Default

Execute without user


batch
interface

batcht (obsolete) Same as "batch"

input=input-file VDA Input File

output=output-file Output File

0.05 for in. model, 1.27


dtol=value Deviation Tolerance
for mm model

format={ASCII|BINARY} Output File Format BINARY

type={VERICUT|STL|POINT} Output File Type STL

dir={INWARD|OUTWARD|GUESS} Normal Direction OUTWARD

NOTE: This functionality is also available as a stand-alone utility on Windows.


Execute vda.bat, located in the "commands" directory of your VERICUT installation,
with the appropriate arguments.

See VDA Converter, in the Converters and CAD/CAM Interfaces section, in the CGTech
Help Library for additional information.
Controlling VERICUT with Comment Records

Comment records, for example "PPRINT/COMMENT TEXT" in APT or CLS tool paths,
or "(COMMENT TEXT)" in G-Code tool paths, typically have no affect on tool motion
simulated by VERICUT. However, special "VERICUT comment" records are available
to help control the tool path simulation in VERICUT. For example, VERICUT comments
can be used to change cut colors, set VERICUT user interface values, or cause VERICUT
to perform certain actions, such as: AUTO-DIFF model comparisons, reversing the view,
etc.
Note that for G-Code NC programs, the NC control must be configured to interpret the
comment record format for that control, for example "begin comment" word, "end
comment" word (if present), etc. Some simple examples follow.

Examples of VERICUT comment records that reverse the model view:

APT or CLS tool path:


PPRINT/VERICUT-COMMAND reverse

G-Code tool paths:


Fanuc control configured with "(" begin comment word, and ")" end comment
word —
(VERICUT-COMMAND reverse)

Cincinnati Acramatic control configured with "(MSG," begin comment word, and
")" end comment word —
(MSG,VERICUT-COMMAND reverse)

Heidenhain control configured with ":" begin comment word (no end comment
word) —
:VERICUT-COMMAND reverse
The available VERICUT comment records with specific formats and examples are
described in the sections

VERICUT-BEGINTABLE record
VERICUT-COMMAND records
VERICUT-CUTCOLOR record
VERICUT-ENDTABLE record
VERICUT-MATRIX record
VERICUT-MODAL record
VERICUT-MOTION record
VERICUT-OPTIPATH record
VERICUT-TC record
VERICUT-TOOLID record
VERICUT-USERTAG record
VERICUT-VARTAG record
VERICUT-BEGINTABLE Record

Special comment record that, when used with VERICUT-ENDTABLE record, enables
specifying the contents of a table, for use in a VERICUT report, from PPRINT statements
within the toolpath file. The general format is PPRINT/VERICUT-BEGINTABLE
"tagname", for APT or CLS tool paths, or (VERICUT-BEGINTABLE "tagname") for G-
code tool paths.

Example of use:
Use to specify the contents for a "Table" type User-Defined Tag:

(VERICUT-BEGINTABLE "setup_info")
( 1ST OP, METALDYNE PUNCH SLEEVE BODY )
( PART #,H0070-0243 )
( REV.,"A" )
( NC Program File,L1H0070-0243.TXT)
( DATE ORIGINALLY PROGRAMMED,10/24/03 )
( PROGAMMED BY,CHARLIE WILSON )
( STOCK,6-1/2" H-13 CUT +.150 )
(- ,CHUCK ON STOCK DIA. 3.00" DEEP )
(- ,WITH FULL CHUCK PRESSURE )
(- ,UNDERCUT YOUR JAWS FOR A GOOD GRIP )
(VERICUT-ENDTABLE)

where setup_info is the User-Defined Tag name, and the remaining statements represent
the content of the table, with the exception if the VERICUT-ENDTABLE statement
which indicates the end of the table data. Each comment record represents a row in the
table and the "," character is used to separate the column entries.
NOTE: See VERICUT-USERTAG record for information on populating a table in a
VERICUT report using a text file.
VERICUT-COMMAND Record

Special comment records that perform VERICUT commands or operations. The


commands available via comment records are listed below with examples of use.
Note that for G-Code NC programs, the NC control must be configured to interpret the
comment record format for that control, for example "begin comment" word, "end
comment" word (if present), etc. See "Controlling VERICUT with comment records" for
some examples.

auto-diff
Performs an AUTO-DIFF comparison, then restores the cut model.
Examples of use:
APT/CLS — PPRINT/VERICUT-COMMAND auto-diff
G-Code (Fanuc) — (VERICUT-COMMAND auto-diff)

display
Updates the display of a FastMill cut model with current cuts.
Examples of use:
APT/CLS — PPRINT/VERICUT-COMMAND display
G-Code (Fanuc) — (VERICUT-COMMAND display)

display_fixtures
Displays all defined fixture models. (See also "remove_fixtures".)
Examples of use:
APT/CLS — PPRINT/VERICUT-COMMAND display_fixtures
G-Code (Fanuc) — (VERICUT-COMMAND display_fixtures)

FIT
Does a "fit" of the active view. (See also "FIT_ALL".)
Example of use:
PPRINT/VERICUT-COMMAND,FIT

FIT_ALL
Does a "fit" of all views. (See also "FIT".)
Example of use:
PPRINT/VERICUT-COMMAND,FIT_ALL

load_model_by_name "<component name>"


Makes a pre-defined model(s), referenced by its component name, "visible" in the
VERICUT display. (See also "remove_model_by_name")
Examples of use:
Display the model(s) referenced by the component named "Fixture" in the Project (or
Component) Tree:
APT/CLS — PPRINT/VERICUT-COMMAND load_model_by_name "Fixture"
G-Code (Fanuc) — (VERICUT-COMMAND load_model_by_name "Fixture")

Notice that before processing the command, the "Fixture" icon is displayed as not
visible.

Before After
Notice that after processing the command, the "Fixture" icon is now displayed as
visible.

load_fixture_by_seq <n>
Displays in the VERICUT display the model(s) associated with the fixture component,
referenced by the sequential order in which the fixture components appear in the Project
(or Component) Tree. (See also "remove_fixture_by_seq")

Examples of use:
Display the model(s) referenced by the second fixture component (Fixture B) in the
Project (or Component) Tree:

APT/CLS — PPRINT/VERICUT-COMMAND load_fixture_by_seq 2


G-Code (Fanuc) — (VERICUT-COMMAND load_fixture_by_seq 2)

Notice that before processing the command, the "Fixture B" icon is displayed as not
visible.

Before After
Notice that after processing the command, the "Fixture B" icon is now displayed as
visible.

pause n
Adds "n" seconds of delay to an Image file being recorded. (See Record Movie in the
VERICUT Help section, in the CGTech Help Library, for additional information.)
Examples of use:
Add 5 seconds of pause:
APT/CLS — PPRINT/VERICUT-COMMAND pause 5
G-Code (Fanuc) — (VERICUT-COMMAND pause 5)

repaint
Repaints solid objects with colors assigned via the Edit menu > Colors: Assign tab. See
the VERICUT Help section, in the CGTech Help Library, for additional information.
Examples of use:
APT/CLS — PPRINT/VERICUT-COMMAND repaint
G-Code (Fanuc) — (VERICUT-COMMAND repaint)
reset_cutcolor
Resets all model colors to the "Reset Cut Color" color. (Ref. Edit menu > Colors:
Assign tab in the VERICUT Help section, in the CGTech Help Library.)

Examples of use:
APT/CLS — PPRINT/VERICUT-COMMAND reset_cutcolor
G-Code (Fanuc) — (VERICUT-COMMAND reset_cutcolor)

reverse
Reverses the view of the VERICUT model. (Ref. View menu > Orient: Reverse in the
VERICUT Help section, in the CGTech Help Library. )
Examples of use:
APT/CLS — PPRINT/VERICUT-COMMAND reverse
G-Code (Fanuc) — (VERICUT-COMMAND reverse)

remove_fixtures
Removes all displayed fixture models. (See also "display_fixtures".)

Examples of use:
APT/CLS — PPRINT/VERICUT-COMMAND remove_fixtures
G-Code (Fanuc) — (VERICUT-COMMAND remove_fixtures)

remove_model_by_name "<component name>"


Removes a pre-defined model(s), referenced by its component name, "not visible" in the
VERICUT display. (See also "load_model_by_name")

Examples of use:
Remove the model(s) referenced by the component named "Fixture", in the Project (or
Component) Tree, from the VERICUT display:

APT/CLS — PPRINT/VERICUT-COMMAND remove_model_by_name “Fixture”


G-Code (Fanuc) — (VERICUT-COMMAND remove_model_by_name “Fixture ”)
Notice processing the command, that the "Fixture" icon is displayed as visible.

Before After
Notice that after processing command, the "Fixture" icon is now displayed as not
visible.

remove_fixture_by_seq <n>
Removes from the VERICUT display, the model(s) associated with the fixture
component, referenced by the sequential order in which the fixture components appear in
the Project (or Component) Tree. (See also "load_model_by_seq")

Examples of use:
REMOVE the model(s) referenced by the second fixture component (Fixture B) in the
Project (or Component) Tree:

APT/CLS — PPRINT/VERICUT-COMMAND remove_fixture_by_seq 2


G-Code (Fanuc) — (VERICUT-COMMAND remove_fixture_by_seq 2)
Notice that before processing the command, the "Fixture B" icon is displayed as visible.

Before After
Notice that after processing the command, the "Fixture B" icon is now displayed as not
visible.

SAVE_IP,filename
Saves an In-Process file, named "filename" to the current working directory. ".ip" is
appended if no extension is specified.
Examples of use:
Saves an IP file named setup1.ip to the current working directory.

PPRINT/VERICUT-COMMAND,SAVE_IP,setup1

See in In-Process File in the Getting Started with VERICUT section of VERICUT Help,
in the CGTech Help Library, for additional information on In-Process files.

SAVE_VCT,filename,FEATURES,YES (or NO)


SAVE_VCT,filename,stockname
Saves a VERICUT Solid file, named "filename" to the current working directory. ".vct" is
appended if no extension is specified.
NOTE: If "filename" contains spaces or a drive letter, include double quotes in the
command. See examples below.
FEATURES, YES indicates that the VERICUT Solid file is to be saved with features.
FEATURES, NO indicates that the VERICUT Solid file is to be saved without features.
Use "stockname" to specify which stock is to be saved when more than one stock
component is present.

Examples of use:
Save a VERICUT Solid file named stock1.vct, using the first stock component, to the
current working directory. Save the file with features.

PPRINT/VERICUT-COMMAND,SAVE_VCT,stock1
or
PPRINT/VERICUT-COMMAND,SAVE_VCT,stock1,FEATURES,YES

Save a VERICUT Solid file named stock1.vct, using the first stock component, to the
current working directory. Save the file without features.

PPRINT/VERICUT-COMMAND,SAVE_VCT,stock1,FEATURES,NO

Save a VERICUT Solid file named "stock2.vct", using the stock component named
"Cut_Stock2", to the current working directory. Save the file with features.

PPRINT/VERICUT-COMMAND,SAVE_VCT,stock2,Cut_Stock2
or
PPRINT/VERICUT-COMMAND,SAVE_VCT,stock2,FEATURES,YES,Cut_Stock2

Save a VERICUT Solid file named "stock2.vct", using the stock component named
"Cut_Stock2", to the current working directory. Save the file without features.

PPRINT/VERICUT-COMMAND,SAVE_VCT,stock2,FEATURES,NO,Cut_Stock2

Save a VERICUT Solid file named "my stock1.vct", using the first stock component, to
the "n:\my files\" directory.

PPRINT/VERICUT-COMMAND,SAVE_VCT,"n:\my files\my stock1"


or
(VERICUT-COMMAND,SAVE_VCT,"n:\my files\my stock1")
Save a VERICUT Solid file with features named "my stock1.vct", using the first stock
component, to the "n:\my files\" directory.

PPRINT/VERICUT-COMMAND,SAVE_VCT,"n:\my files\my stock1",


FEATURES,YES
or
(VERICUT-COMMAND,SAVE_VCT,"n:\my files\my stock1",FEATURES,YES)

See VERICUT Solid File, in the Getting Started with VERICUT section of VERICUT
Help, in the CGTech Help Library, for additional information on VERICUT Solid files.

ZOOM_OUT
Zooms out in the active view.
Example of use:
PPRINT/VERICUT-COMMAND,ZOOM_OUT

VERICUT-CUTCOLOR Record

Special comment records that assign the cut color for the active tool. Cut colors are
referenced via an index corresponding to the colors defined for use via the "Shade Color
list" on the Edit menu > Colors: Define tab (See the VERICUT Help section, in the
CGTech Help Library for additional information). Color index numbers range from 0-n
where "0" refers to the first color in the list-typically assigned to be the Error color. "1"
refers to the second listed color, and so on. The index number is always 1 less than the
index seen in the user interface. Examples follow.
Note that for G-code tool paths, the NC control must be configured to interpret the
comment record format for that control, for example "begin comment" word, "end
comment" word (if present), etc. See "Controlling VERICUT with comment records" for
simple examples.

Examples of use:
Set the cut color to "Light Steel Blue", as referenced in the sample Color window below:
APT/CLS — PPRINT/VERICUT-CUTCOLOR 2
G-Code (Fanuc) — (VERICUT-CUTCOLOR 2)
VERICUT-ENDTABLE Record

Special comment record that, when used with VERICUT-BEGINTABLE record, enables
specifying the contents of a table, for use in a VERICUT report, from PPRINT statements
within the toolpath file. The general format is PPRINT/VERICUT-ENDTABLE, for APT
or CLS tool paths, or (VERICUT-ENDTABLE) for G-code tool paths.

Example of use:
Use to specify the contents for a "Table" type User-Defined Tag:
(VERICUT-BEGINTABLE "setup_info")
( 1ST OP, METALDYNE PUNCH SLEEVE BODY )
( PART #,H0070-0243 )
( REV.,"A" )
( NC Program File,L1H0070-0243.TXT)
( DATE ORIGINALLY PROGRAMMED,10/24/03 )
( PROGAMMED BY,CHARLIE WILSON )
( STOCK,6-1/2" H-13 CUT +.150 )
(- ,CHUCK ON STOCK DIA. 3.00" DEEP )
(- ,WITH FULL CHUCK PRESSURE )
(- ,UNDERCUT YOUR JAWS FOR A GOOD GRIP )
(VERICUT-ENDTABLE)

where the VERICUT-BEGINTABLE statement indicates the start of the table data,
setup_info is the User-Defined Tag name, the remaining statements represent the content
of the table, and the VERICUT-ENDTABLE statement indicates the end of the table
data. Each comment record represents a row in the table and the "," character is used to
separate the column entries.

NOTE: See VERICUT-USERTAG record for information on populating a table in a


VERICUT report using a text file.
VERICUT-MATRIX Record

Special comment records that specify a twelve parameter tool path transformation matrix:
i1,j1,k1,d1,i2,j2,k2,d2,i3,j3,k3,d3. This record is processed regardless of the Process
Matrix setting in the Apt Settings window: Motion tab (See the VERICUT Help
section, in the CGTech Help Library, for more information). The transformation matrix is
similar to the matrix used in programming APT tool paths. Its twelve parameters reveal
the geometrical attributes of the local (transformed) coordinate system in terms of the
workpiece origin.
The format of the matrix is as follows:

i j k d

X i1 j1 k1 d1

Y i2 j2 k2 d2

Z i3 j3 k3 d3

The first three columns represent the axes of the local system: i1, i2, i3 as the positive X-
axis vector; j1, j2, j3 as the positive Y-axis vector; and k1, k2, k3 as the positive Z-axis
vector. The fourth column d1, d2, d3 is the origin point of the local system. The active
matrix is reset to an identity matrix (no rotation or translation) each time a new tool path
file is processed.
Note that for G-code tool paths, the NC control must be configured to interpret the
comment record format for that control, for example "begin comment" word, "end
comment" word (if present), etc. See "Controlling VERICUT with comment records" for
simple examples.

Examples of use:
Translate the tool path 2 units in X, 3 in Y, and -1 in Z.
APT/CLS — PPRINT/VERICUT-MATRIX 1,0,0,2,0,1,0,3,0,0,1,-1
G-Code (Fanuc) — (VERICUT-MATRIX 1,0,0,2,0,1,0,3,0,0,1,-1)

As above, except in APT/CLS multi-line record format using the "$" continuation:
PPRINT/VERICUT-MATRIX 1,0,0,2,$
PPRINT/VERICUT-MATRIX 0,1,0,3,$
PPRINT/VERICUT-MATRIX 0,0,1,-1
Rotate the tool path 180 degrees about the Y axis:
APT/CLS — PPRINT/VERICUT-MATRIX -1,0,0,0,0,1,0,0,0,0,-1,0
G-Code (Fanuc) — (VERICUT-MATRIX -1,0,0,0,0,1,0,0,0,0,-1,0)
VERICUT-MODAL Record

Special comment records that specify a user interface value, such as a data field entry or
an option choice. One user variable/value can be set per record. Most user variables
found in a Project file can be set or modified in this way.
Note that for G-code tool paths, the NC control must be configured to interpret the
comment record format for that control, for example "begin comment" word, "end
comment" word (if present), etc. See "Controlling VERICUT with comment records" for
simple examples.

Examples of use:
Set the Fast Feed data field value to "100":
APT/CLS — PPRINT/VERICUT-MODAL FASTFEED=100
G-Code (Fanuc) — (VERICUT-MODAL FASTFEED=100)

Choosing the Machining Type option for simulation of milling or turning operations:
APT/CLS milling mode — PPRINT/VERICUT-MODAL MACHTYPE=milling
APT/CLS turning mode — PPRINT/VERICUT-MODAL MACHTYPE=turning
G-Code (Fanuc) milling mode — (VERICUT-MODAL MACHTYPE=milling)
G-Code (Fanuc) turning mode — (VERICUT-MODAL MACHTYPE=turning)
VERICUT-MOTION record

Special comment records that control when tool motions and cutting are simulated. When
off, motion commands and tool positions are processed, but simulation, cutting, collision
detection, and axis overtravel detection are suspended (ignored) during subsequent
moves. When motion is turned on, the tool and/or NC machine "jumps" to its current
position. The motion "on" condition is automatically set when a reset is done.
Note that for G-code tool paths, the NC control must be configured to interpret the
comment record format for that control, for example "begin comment" word, "end
comment" word (if present), etc. See "Controlling VERICUT with comment records" for
simple examples.

Examples of use:
Turn motion off:
APT/CLS — PPRINT/VERICUT-MOTION off
G-Code (Fanuc) — (VERICUT-MOTION off)

Turn motion on:


APT/CLS — PPRINT/VERICUT-MOTION on
G-Code (Fanuc) — (VERICUT-MOTION on)
VERICUT-OPTIPATH record

Special comment records that control when tool motions are optimized via the OptiPath.
When off, optimization is suspended (ignored) during subsequent moves-tool path
records are written to the Optimized file as they were programmed. Optimization remains
off until the next OptiPath "On" record is encountered. Optimization must be turned on
prior to the next tool change. A format also exists for specifying which OptiPath library
record to use:
VERICUT-OPTIPATH DESC="my_optipath_tool_description" TEETH=<n>
where "my_optipath_tool_description" is an optimization record description which could
contain any characters, including delimiters. The description must be enclosed in double
quotes. "N" is the number of cutting teeth. This record specifies two of the four values
needed to identify which optimization record to use. The other two values come from
Material and Machine on the OptiPath Control window. If an optimization record
matching the four values is not found, VERICUT continues to write un-optimized tool
path records to the optimized tool path file.
See the VERICUT Help section, in the CGTech Help Library, for additional information
on OptiPath and the OptiPath Control window.
Note that for G-Code NC programs, the NC control must be configured to interpret the
comment record format for that control, for example "begin comment" word, "end
comment" word (if present), etc. See "Controlling VERICUT with comment records" for
simple examples.

Examples of use:
Turn optimization off:
APT/CLS — PPRINT/VERICUT-OPTIPATH off
G-Code (Fanuc) — (VERICUT-OPTIPATH off)

NOTE: "OPTIPATH off" turns off OptiPath until the next "OPTIPATH on" is
encountered.

Turn optimization on:


APT/CLS — PPRINT/VERICUT-OPTIPATH on
G-Code (Fanuc) — (VERICUT-OPTIPATH on)
Specify an OptiPath library record for use with the current tool:
APT/CLS — PPRINT/VERICUT-OPTIPATH DESC=".5 Dia Ball EM, Carbide"
TEETH=4
G-Code (Fanuc) — (VERICUT-OPTIPATH DESC=".5 Dia Ball EM, Carbide"
TEETH=4)
VERICUT-TC record

Special comment records that define the shapes of cutters, shanks or holders in a tool
assembly. Interpreted like a CUTTER record, anything allowed to follow "CUTTER/" is
also allowed to follow "VERICUT-TC". Like "CUTTER", this record is processed by
default via Tool Change By in the NC Programs window set to: "Cutter Desc." or
"VERICUT TC". See the VERICUT Help section, in the CGTech Help Library, for
additional information.
Note that for G-code tool paths, the NC control must be configured to interpret the
comment record format for that control, for example "begin comment" word, "end
comment" word (if present), etc. See "Controlling VERICUT with comment records" for
simple examples.

Examples of use:
Defines an APT-type seven parameter cutter shape- 1.0 diameter x .125 corner radius x
3.0 height:
APT/CLS — PPRINT/VERICUT-TC 1.0,.125,0,0,0,0,3.0
G-Code (Fanuc) — (VERICUT-TC 1.0,.125,0,0,0,0,3.0)

Defines a profile cutter shape:


APT/CLS — PPRINT/VERICUT-TC XCUT,PTS,0,0,.5,0,ARC,1,0,.5,PTS,1,.5,1,1
G-Code (Fanuc) — (VERICUT-TC XCUT,PTS,0,0,.5,0,ARC,1,0,.5,PTS,1,.5,1,1)

As above, except in APT/CLS multi-line record format using the "$" continuation:
PPRINT/VERICUT-TC XCUT,PTS,0,0,.5,0,$
PPRINT/VERICUT-TC ARC,1,0,.5,PTS,1,.5,$
PPRINT/VERICUT-TC 1,1

Defines a profile shank shape:


APT/CLS — PPRINT/VERICUT-TC SHANK,PTS,0,0,.5,0,.5,1,0,1
G-Code (Fanuc) — (VERICUT-TC SHANK,PTS,0,0,.5,0,.5,1,0,1)

Defines a profile holder shape:


APT/CLS — PPRINT/VERICUT-TC HOLDER,PTS,0,0,1,0,1.5,.5,1.5,3,0,3
G-Code (Fanuc) — (VERICUT-TC HOLDER,PTS,0,0,1,0,1.5,.5,1.5,3,0,3)
Incorrect examples:
Continuation record missing "VERICUT-TC":
PPRINT/VERICUT-TC XCUT,PTS,0,0,.5,0,ARC,$
PPRINT/1,0,.5,PTS,1,.5,1,1,0,1

The word "ARC" split between lines:


PPRINT/VERICUT-TC XCUT,PTS,0,0,.5,0,AR$
PPRINT/VERICUT-TC C,1,0,.5,PTS,1,.5,1,1,0,1

Continuation record does not have the same keyword "TC":


PPRINT/VERICUT-TC XCUT,PTS,0,0,.5,0,1,.5,1,1 $
PPRINT/VERICUT-COMMAND reverse
VERICUT-TOOLID record

Special comment records that specify the ID of a tool to use from a VERICUT Tool
Library file. This record is acted on only when VERICUT is configured to retrieve tools
from a Tool Library, for example: Tool Change By in the NC Programs window set to:
"Tool Number". See the VERICUT Help section, in the CGTech Help Library, for
additional information.
Note that for G-Code tool paths, the NC control must be configured to interpret the
comment record format for that control, for example "begin comment" word, "end
comment" word (if present), etc. See "Controlling VERICUT with comment records" for
simple examples.

Example of use:
Use tool in the library having ID #100002:
APT/CLS — PPRINT/VERICUT-TOOLID 100002
G-Code (Fanuc) — (VERICUT-TOOLID 100002)

NOTE: This feature is intended to be used only for Verification. Using it with Machine
Simulation will result in an incorrectly positioned tool being displayed only in a
Workpiece view.
VERICUT-USERTAG record

A special comment record that enables specifying User-Defined Tag values, for use in a
VERICUT report, from within the NC program file. The general format is
PPRINT/VERICUT-USERTAG "tagname"="tagvalue", for APT or CLS tool paths, or
(VERICUT-USERTAG "tagname"="tagvalue") for G-code tool paths.

Examples of use:
Use to specify the value for a "Text" type User-Defined Tag:
PPRINT/VERICUT-USERTAG "text_entry"="This is the text that will appear in the
VERICUT report.")
(VERICUT-USERTAG "text_entry"="This is the text that will appear in the
VERICUT report.")
where text_entry is the User-Defined Tag name, and "This is the text that will appear in
the VERICUT report.", is what will be written out in the report.
Use to specify the value for a "Table" type User-Defined Tag:
PPRINT/VERICUT-USERTAG "table_name"="/path/filename")
(VERICUT-USERTAG "table_name"="/path/filename")
where table_name is the User-Defined Tag name, and /path/filename represents the path
and file name of the text file containing the data for the table.

NOTE: See VERICUT-BEGINTABLE record and VERICUT-ENDTABLE record for


information on populating a table in a VERICUT report using the PPRINT statements in
the NC program file.
Use to specify the value for a "Picture From File" type User-Defined Tag:
PPRINT/VERICUT-USERTAG "picture"="/path/filename")
(VERICUT-USERTAG "picture"="/path/filename")
where picture is the User-Defined Tag name, and /path/filename represents the path and
file name of the image file containing picture for the report.
User-defined tags defined using a VERICUT-USERTAG record can be used within a
"Toolpath Loop", or a "Tool Change Loop" in a VERICUT report. See Report Template
window, Page Layout tab in the VERICUT Help section, in the CGTech Help Library
for additional information.
VERICUT-VARTAG record

A special comment record that enables assigning the value of an NC variable to a User-
Defined Tag, from within the NC program file, for use in a VERICUT report. The
general format is PPRINT/VERICUT-VARTAG "user-defined tag name"="NC variable
name", for APT, or CLS, NC programs, or (VERICUT-VARTAG "user-defined tag
name"="NC variable name") for G-Code NC programs.
Note that for G-Code NC programs, the NC control must be configured to interpret the
comment record format for that control, for example "begin comment" word, "end
comment" word (if present), etc. See "Controlling VERICUT with comment records" for
simple examples.
The user-defined tag value will be the NC variable's value at the time the comment
statement is processed. If you have multiple comment statements, defining the same user-
defined tag, with the same tool and NC program, the user-defined tag value will be NC
variable's value at the time that the last comment statement is processed.

Example of use:
Assign the value of NC variable 5043 to user-defined tag Tool Tip Z :
APT/CLS — PPRINT/VERICUT-VARTAG "Tool Tip Z"="5043"
G-Code (Fanuc) — (VERICUT-VARTAG "Tool Tip Z"="5043")

NOTES:
1. NC variable name is the name of the NC variable as long as the variable is not an
array variable. If the variable is an array variable, NC variable name must be a
single array element, like text[0, 1], or frame[1, X, TR]. See Variables window
in the VERICUT Help section, in the CGTech Help Library for additional
information on NC Variables.
2. User-defined tags defined using a VERICUT-VARTAG record can be used
within a "Toolpath Loop", or a "Tool Change Loop" in a VERICUT report. See
Report Template window, Page Layout tab in the VERICUT Help section, in
the CGTech Help Library for additional information.