Vous êtes sur la page 1sur 49

Automating VERICUT

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"

Automating VERICUT
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

Automating VERICUT

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.

Automating VERICUT

Batch Wizard
The Batch Wizard graphically guides you through setting up and running CGTech
products in batch mode. 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 allows you to run other applications, or
perform other tasks while CGTech products are being productive.

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>/<computertype>/commands/bwizard" where <cgtech6x> represents
the directory path to where CGTech products were installed, and <computertype>
is the type of computer on which VERICUT is being operated, for example:
hp700, rs, sgi, or solaris.

Sample Batch wizard window:

Automating VERICUT
In general, follow the prompts-press Next to go to the next screen, Back returns to the
previous screen. Finish indicates batch session setup is complete and opens a window to
specify the name of the batch session file to save. Following are general descriptions of
Batch Wizard screens that guide you through setting up a batch session file.
Main screen Also known as the "Welcome screen", this screen welcomes you to the
Batch Wizard. You can start a new batch session, modify an existing session, or run an
existing session.
Operation screen This screen is used to add, modify, or delete batch operations.
Operations can be named as desired, and are performed in listed order. Use Move Up /
Move Down to change the order in the list.
CGTech product screen This screen is used to specify which CGTech product will
be run in the batch operation. Choose O.S.Command to use an operating system
command to assist with batch processing, such as: copy, move, append, rename, and set
environment variables.
CGTech product screen This screen is used to specify which CGTech product will
be run in the batch operation. Choose O.S.Command to use an operating system
command to assist with batch processing, such as: copy, move, append, rename, and set
environment variables.
Command line option screen This screen is used to choose one or more command
line options for the product being run in batch. Press the right arrow
to include the
option in the batch session being configured. Use the left arrow to remove an unwanted
option. Use the file selection button
to specify files to use. Be sure to include one of
the batch options (batch or batchp) to run the CGTech product in batch mode.
After setup is finished, choose Run an existing session from the main screen to run the
batch session. Batch session files created by the Batch Wizard are computer independent,
and can be run on any computer that is capable of running VERICUT.

Automating VERICUT

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

Automating VERICUT

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

Automating VERICUT

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.
See "About optimizing NC programs" in the Using VERICUT section, in the CGTech
Help Library, for additional information.
2. Click OptiPath menu > Control to display the OptiPath Control window.
3. 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.
4. Press OK.
5. Save a Project file (or IP file) to use during the batch process, for example
"test.VcProject"
6. Exit VERICUT
7. 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

Automating VERICUT

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:

<uservariablename>=<uservalue>

Sets a user variable (value in the user


interface)

append_log

Open Log file in append mode

auto-diff=<reportfilename>

Perform an AUTO-DIFF model comparison


and write results to a file

batch

Runs VERICUT in the background, without


opening the user interface

batchp

Similar to batch, except "pops open" the


VERICUT window when finished

burn

Processes the "Burn" function in a Die


Sinking Simulation

csys_file=<filename>

Reads the specified CSYS File and creates a


VERICUT coordinate system.

dxf2sweep

Imports DXF 2D geometry and creates a


"sweep" solid model

dxf2sor

Imports DXF 2D geometry and creates a

Automating VERICUT
"solid of revolution" solid model
export

Exports the VERICUT cut model

fitall

Fits all open views

hres=<value>

Sets the horizontal screen display resolution

IMRCAPDT=on

Appends recorded images to an existing


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

report_template=<filename>

Specifies the VERICUT report template file


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

vcp=<file>

Loads a Project file

usr=<usrfile>

Loads a User file

VericutPlayer

Plays back the specified VERICUT image


file.

vres=<value>

Sets the vertical screen display resolution

10

Automating VERICUT

zoom_out[=<value>]

Zooms out approximately 20% for each


"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"

11

Automating VERICUT

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.

12

Automating VERICUT
Also see: reset_log and LGFILNAM=<logfilename>.

auto-diff=<reportfilename>
Performs an AUTO-DIFF model comparison and writes results to the specified AUTODIFF 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.

13

Automating VERICUT
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 export
operation is performed when tool path 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)

14

Automating VERICUT
(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.

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)

15

Automating VERICUT
["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 tool path 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.

16

Automating VERICUT

FLATBG
Sets all View backgrounds to "FLAT" 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

17

Automating VERICUT
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.

18

Automating VERICUT

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.
See Create a Report Using a Template in the Using VERICUT section, in the CGTech
Help Library, for more information.

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.

19

Automating VERICUT

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"

20

Automating VERICUT
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 "vcpr=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

21

Automating VERICUT

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)

22

Automating VERICUT
"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)

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.

23

Automating VERICUT

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


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)

table=table-file

APT Table File

cltype={1|2|3|4}

Input File Type:


1
1=IBM,2=IBMWS,3=CATWS,4=VAXWS

circles={YES|NO}

Output Circles

Yes

height=value

Minimum Cutter Height

aptwords.tbl
(CGTech library)

24

Automating VERICUT

CAD Converter command line options


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

Description

Default

batch

Execute without user


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

25

OUTWARD

Automating VERICUT

IGES Converter command line options


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

Description

Default

batch

Execute without user


interface

batcht (obsolete)

Same as "batch"

input=input-file

IGES Input File

output=output-file

Output File

dtol=value

Deviation Tolerance

0.05 for in. model, 1.27


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


summary

Summary of input file


contents

26

OUTWARD

Automating VERICUT

PolyFix Converter command line options


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

Description

batch

Execute without user


interface

batcht (obsolete)

Same as "batch"

input=input-file

Input File

intype={VERICUT|STL}

Input File Type

output=output-file

Output File

Default

STL

outformat={ASCII|BINARY} Output File Format

BINARY

outtype={VERICUT|STL}

STL

Output File Type

27

Automating VERICUT

Surface to Solid Converter command line options


Command line options available for the Surface to Solid Converter are described in the
table below.
Option

Description

Default

batch

Execute without user


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

base=value

Base Location

rectangle={NO|YES}

Project Rectangle

NO

28

Automating VERICUT

VDA Converter command line options


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

Description

batch

Execute without user


interface

batcht (obsolete)

Same as "batch"

input=input-file

VDA Input File

output=output-file

Output File

dtol=value

Deviation Tolerance

0.05 for in. model, 1.27


for mm model

format={ASCII|BINARY}

Output File Format

BINARY

type={VERICUT|STL|POINT}

Output File Type

STL

dir={INWARD|OUTWARD|GUESS} Normal Direction

29

Default

OUTWARD

Automating VERICUT

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

30

Automating VERICUT
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

31

Automating VERICUT

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 Gcode 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. (See Using PPRINT
info from an NC program in a report, in the Using VERICUT section, in the CGTech
Help Library, for additional information)

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


VERICUT report using a text file.

32

Automating VERICUT

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 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
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)

33

Automating VERICUT

load_model_by_name "<modelname>"
Loads a model referenced by its name. (See also "remove_model_by_name")
Examples of use:
Load the model named "Model 2" from the sample models list:
Model Definition List
--------------------Model 1 (Stock)
Model 2 (Fixture)
Model 3 (Design Solid)
APT/CLS PPRINT/VERICUT-COMMAND load_model_by_name "Model 2"
G-code (Fanuc) (VERICUT-COMMAND load_model_by_name "Model 2")

load_fixture_by_seq <n>
Loads the fixture referenced in the sequential order of defined fixtures. (See also
"remove_fixture_by_seq")
Examples of use:
Load the second fixture model (Model 3) in the sample models list:
Model Definition List
--------------------Model 1 (Stock)
Model 2 (Fixture)
Model 3 (Fixture)
APT/CLS PPRINT/VERICUT-COMMAND load_model_by_seq 2
G-code (Fanuc) (VERICUT-COMMAND load_model_by_seq 2)

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)

34

Automating VERICUT

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: Reversein 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)

35

Automating VERICUT

remove_model_by_name "<modelname>"
Removes a model referenced by its name. (See also "load_model_by_name")
Examples of use:
Remove the model named "Model 2":
APT/CLS PPRINT/VERICUT-COMMAND remove_model_by_name
Model 2
G-code (Fanuc) (VERICUT-COMMAND remove_model_by_name Model
2)

remove_fixture_by_seq <n>
Removes the fixture referenced in the sequential order of defined fixtures. (See also
"load_model_by_seq")
Examples of use:
Remove the second fixture model in the models list:
APT/CLS PPRINT/VERICUT-COMMAND remove_model_by_seq 2
G-code (Fanuc) (VERICUT-COMMAND remove_model_by_seq 2)

36

Automating VERICUT

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)

37

Automating VERICUT

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. (see Using PPRINT info from an NC program in a report
in the Using VERICUT section, in the CGTech Help Library, for additional information)

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


VERICUT report using a text file.

38

Automating VERICUT

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

i1

j1

k1

d1

i2

j2

k2

d2

i3

j3

k3

d3

The first three columns represent the axes of the local system: i1, i2, i3 as the positive Xaxis 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

39

Automating VERICUT
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)

40

Automating VERICUT

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)

41

Automating VERICUT

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)

42

Automating VERICUT

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 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 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)

43

Automating VERICUT
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)

44

Automating VERICUT

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)
45

Automating VERICUT

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

46

Automating VERICUT

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.
Examples of use:
Use tool in the library having ID #100002:
APT/CLS PPRINT/VERICUT-TOOLID 100002
G-code (Fanuc) (VERICUT-TOOLID 100002)

47

Automating VERICUT

VERICUT-USERTAG record
Special comment record that enables specifying User-Defined Tag values, for use in a
VERICUT report, from within the toolpath 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. For additional
information on User-Defined Tag values and VERICUT reports, see the VERICUT
Help section in the CGTech Help Library.
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. (see Using PPRINT info
from an NC program in a report, in the Using VERICUT section, in the CGTech Help
Library, for additional information)
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.
See Using data from a file in a report, in the Using VERICUT section, in the CGTech
Help Library, for additional information.

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 toolpath 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.

48

Automating VERICUT
See Using PPRINT info from an NC program in a report, in the Using VERICUT
section, in the CGTech Help Library, for additional information)

49