Go to CGTech Help Library

Converters and Interfaces

 VERICUT Converters and Interfaces

VERICUT Converters

Select from the following:

CAD Model Converter
IGES Converter
PolyFix Converter
Surface to Solid Converter
VDA Converter
Binary CL Converter

1
 VERICUT Converters and Interfaces

CAD Model Converter

Location: File menu > Convert > CAD Model

The CAD Model Converter converts (translates) CAD models in various formats to
Stereolithography (STL) or VERICUT Polygon model files. This converter is used to
import complex castings, clamps, fixtures, and other 3-D design models into VERICUT.
Converted data can also be used with AUTO-DIFF to verify the machined part is as
expected.
The following CAD model formats are currently supported:
CATIA V4 R14
CATIA V5 R14
STEP
SAT
CAD model data can be converted interactively in VERICUT (File menu > Convert >
CAD Model), via batch processing, or as a stand-alone utility outside of VERICUT by
running the CAD Model Converter "cad2v" command file located in the "commands"
directory of your VERICUT installation.

2
 VERICUT Converters and Interfaces

Input File — Name of the file containing the CAD data to convert (CATIA V4, CATIA
V5, STEP, SAT). Enter the /path/filename in the Input File text field or click on the
(Browse) icon to display the Select Input File file selection window and use it to specify
the /path/filename.
Output File — Name of the file to receive converted geometry. Enter the /path/filename
in the Output File text field or click on the (Browse) icon to display the Select
Output File file selection window and use it to specify the /path/filename.
Output File Type — Type of output file to create. Options are: VERICUT or STL.
Output File Format — Format of the output file. Options are: BINARY or ASCII.
Normal Direction — The direction in which surface normal vectors point, as viewed in
the CAD system. Feature only applicable to VERICUT output file types. Options:
OUTWARDor INWARD.
Tolerance — Specifies the amount of chordal deviation allowed in 3-D space from the
CAD data when creating the converted surface. The converted surface is approximated
using "facets", or triangles.

Process — Processes (converts) the CAD data according to the current window settings.
Close — Closes the CAD Model Converter window.
Help — Displays this Help page. (You can also use the F1 key to display this Help page.)

3
 VERICUT Converters and Interfaces

Converting CAD Model Data

Use the CAD Model Converter and the procedure below to convert CAD model data to
VERICUT or STL model files. Supported CAD model formats include: CATIA V4 R14,
CATIA V5 R14, STEP, and SAT.
NOTE: CAD model data can also be converted via batch processing.

To convert CAD model data to VERICUT or STL model files:

1. Access the CAD Model Converter window: in VERICUT select File menu >
Convert > CAD Model.
You can also run this converter outside of VERICUT via the "cad2v" command
file located in the CGTech "commands" directory, under the directory
representing your computer type.
2. Type the /path /filename in the text field, or use the Browse button and use the
file selection window that displays to select the Input File containing the CAD
model data to convert.
3. Type the /path /filename in the text field, or use the Browse button and use the
file selection window that displays to select the Output File to receive converted
geometry.
4. Choose the Output File Type and Output Format Type in which to write the
converted geometry.
5. If the Output File Type = VERICUT, choose the Normal Direction in which
surface normal vectors point, as viewed in the CAD system.
6. Click Process.

Tip: When expecting to use CAD model data for models in VERICUT, ensure that
surface normals point uni-directionally outwards in the CAD model prior to outputting
the model data.

4
 VERICUT Converters and Interfaces

IGES Converter

Introduction to the IGES Converter

The IGES Converter converts (translates) geometry conforming to the IGES (Initial
Graphics Exchange Specification) 5.0 specification to Stereolithography or VERICUT
Polygon model files. This converter lets you make the most of your existing CAD data by
enabling you to import complex castings, clamps, fixtures, and other 3-D design models
into VERICUT. IGES data can also be used with AUTO-DIFF to verify the machined
part is as expected. IGES data can be converted interactively in VERICUT, via batch
processing, or outside of VERICUT by running the "iges2v" command file.

IGES data and version support

CGTech's IGES Converter converts the IGES data types listed below. The IGES
Converter does not convert 2-D geometry data, however, this geometry is used to
determine boundaries and trimming curves. Only 3-D surfaces, solids, and their
supporting geometry is converted.

100: Circular arc

102: Composite curve
104: Conic arc (parabola, ellipse, hyperbola)
106: Copious data
108: Plane (bounded)
110: Line
112: Parametric spline curve
114: Parametric spline surface
116: Point
118: Ruled surface
120: Surface of revolution
122: Tabulated cylinder
124: Transformation Matrix
126: Rational B-spline curve
128: Rational B-spline surface

5
 VERICUT Converters and Interfaces

130: Offset curve

140: Offset surface
142: Curve on parametric surface
144: Trimmed parametric surface
150: Block
152: Right angular wedge
154: Right circular cylinder
156: Right circular cone frustum
158: Sphere
160: Torus
162: Solid of revolution
164: Solid of linear extrusion
168: Ellipsoid

6
 VERICUT Converters and Interfaces

IGES Converter window

Location: File menu > Convert > IGES

The IGES Converter converts (translates) IGES solid and surface geometry to
Stereolithography or VERICUT Polygon model files. This converter is used to import
complex castings, clamps, fixtures, and other 3-D design models into VERICUT. IGES
data can also be used with AUTO-DIFF to verify the machined part is as expected.
IGES data can be converted interactively in VERICUT, via batch processing, or as a
stand- alone utility outside of VERICUT by running the IGES Converter "iges2v"
command file located in the "commands" directory of your VERICUT installation.
Tips:
1. When expecting to use IGES data for solid models in VERICUT, ensure that
surface normals point unidirectionally outwards in the CAD model prior to
outputting the IGES data.
2. The Stock Consistency Check option is recommended for use with converted
IGES models used to represent a stock workpiece.

7
 VERICUT Converters and Interfaces

Input File — Name of the file containing the IGES data to convert. Enter the
/path/filename in the Input File text field or click on the (Browse) icon to display
the Select Input File file selection window and use it to specify the /path/filename.
Output File — Name of the file to receive converted geometry. Enter the /path/filename
in the Output File text field or click on the (Browse) icon to display the Select
Output File file selection window and use it to specify the /path/filename.
Output File Type — Type of output file to create. Options are: VERICUT or STL.
Output File Format — Format of the output file. Options are: BINARY or ASCII.
Normal Direction — The direction in which surface normal vectors point, as viewed in
the CAD system. Feature only applicable to VERICUT output file types. Options:
OUTWARD or INWARD.
Surface Input Mode — Controls which IGES surfaces to convert. Options:
ALL — Convert all surfaces. With this mode, base surfaces associated with trimmed
surfaces are only converted as trimmed surfaces; not in addition to trimmed surfaces.
BASE — Convert base surfaces only.
TRIMMED — Convert trimmed surfaces only.

8
 VERICUT Converters and Interfaces

Tolerance — Specifies the amount of chordal deviation allowed in 3-D space from the
IGES surface when creating the converted surface. The converted surface is
approximated using "facets", or triangles.

Process — Processes (converts) the IGES data according to the current window settings.
Converted geometry is written to the Output file. Error and informational messages from
the process are sent to the IGES Converter window message area, and to a log file named
"iges2v.log" created in the working directory.
Summary — Prints a summary of the Input file contents to the IGES Converter window
message area.
Clear — Clears the IGES Converter window message area.
Close — Closes the IGES Converter window.
Help — Displays this Help page. (You can also use the F1 key to display this Help page.)

9
 VERICUT Converters and Interfaces

Converting IGES Data

Use the IGES Converter and the procedure below to interactively convert IGES data to
VERICUT or STL model files.
NOTE: IGES data can also be converted via batch processing.

To convert IGES data to VERICUT or STL model files:

1. Access the IGES Converter window: in VERICUT select File menu > Convert
> IGES.
You can also run this converter outside of VERICUT via the "iges2v" command
file located in the CGTech "commands" directory, under the directory
representing your computer type.
2. Type the /path /filename in the text field, or use the Browse button and use the
file selection window that displays to select the Input File containing the IGES
data to convert.
3. Type the /path /filename in the text field, or use the Browse button and use the
file selection window that displays to select the Output File to receive converted
geometry.
4. Choose the Output File Type and Output Format Type in which to write the
converted geometry.
5. If the Output File Type = VERICUT, choose the Normal Direction in which
surface normal vectors point, as viewed in the CAD system. If unknown choose
INCONSISTENT
6. Choose the desired Surface Input Mode (ALL—all surfaces, BASE—base
surfaces only, TRIMMED—trimmed surfaces only)
7. Enter the Tolerance allowed from the IGES surface for surface approximation.
8. Click Process.

Error and informational messages from the process are sent to the IGES Converter
window message area, and to a log file named "iges2v.log" created in the working
directory.

10
 VERICUT Converters and Interfaces

Tips:
1. The IGES Converter does not convert 2-D geometry data, since this data is
useless in VERICUT. Only 3-D surfaces and solids, and their supporting
geometry is converted.
2. When expecting to use IGES data as solid models in VERICUT, ensure that
surface normals point uni-directionally outwards in the CAD model prior to
outputting the IGES data.

11
 VERICUT Converters and Interfaces

PolyFix Converter

Introduction to the PolyFix Converter

The PolyFix Converter ensures the surface normals of Stereolithography (STL) and
VERICUT Polygon Model files point uniformly outward from the model surface. Model
files with inconsistent normals often appear okay in VERICUT - until the solid model
database is established, such as occurs when cutting is started or the model analyzed. It is
a one time effort to repair an inconsistent polygon model file. After repair, the model data
will be processed much faster and more reliably. Model files can be repaired interactively
in VERICUT, via batch processing, or outside of VERICUT by running the "polyfix"
command file.

12
 VERICUT Converters and Interfaces

PolyFix Converter window

Location: File menu > Convert > PolyFix

The PolyFix Converter ensures the surface normals of Stereolithography (STL) and
VERICUT Polygon Model files point uniformly outward from the model surface. Model
files with inconsistent normals often appear OK in VERICUT until the solid model
database is established, such as occurs when cutting is started or the model analyzed. It is
a one time effort to repair an inconsistent polygon model file. After repair, the model data
will be processed much faster and more reliably. Model files can be repaired interactively
in VERICUT, via batch processing, or as a stand-alone utility outside of VERICUT by
running the "polyfix" command file located in the "commands" director of your
VERICUT installation.

Input File — Name of the file containing the surface normals to repair. Enter the
/path/filename in the Input File text field or click on the (Browse) icon to display
the Select Input File file selection window and use it to specify the /path/filename.

13
 VERICUT Converters and Interfaces

Output File — Name of the file to receive repaired geometry data. Enter the
/path/filename in the Output File text field or click on the (Browse) icon to display
the Select Output File file selection window and use it to specify the /path/filename.
When a model file containing multiple solids is processed, multiple output files are
created-one per solid. Each file output has the base file name specified by the Output File
field, with a unique number appended to it incremented by 1.
Input File Type — Type of input file to read. Options are: VERICUT or STL.
Output File Type — Same as Input File Type, except is applicable to the output file.
Output File Format — Format of the output file. Options are: BINARY or ASCII.
Process — Processes (repairs) the model file data according to the current window
settings. Repaired geometry is written to the Output File. Error and informational
messages from the process are sent to the PolyFix Converter window message area, and
to a log file named "polyfix.log" created in the working directory.
Clear — Clears the PolyFix Converter window message area.
Close — Closes the PolyFix Converter window.
Help — Displays this Help page. (You can also use the F1 key to display this Help page.)

14
 VERICUT Converters and Interfaces

Repairing STL or VERICUT Model File Normals

Use the PolyFix Converter and the procedure below to repair surface normals of STL
and VERICUT model files. PolyFix repairs the normals to ensure they point uniformly
outward from the model surface.
NOTE: Normals can also be repaired via batch processing.

To repair STL/VERICUT model file normals:

1. Access the PolyFix Converter window: in VERICUT select File menu >
Convert > PolyFix.
You can also run this converter outside of VERICUT via the "polyfix" command
file located in the CGTech "commands" directory, under the directory
representing your computer type.
2. Type the /path /filename in the text field, or use the Browse button and use the
file selection window that displays to select the Input File containing the normals
to repair.
3. Type the /path /filename in the text field, or use the Browse button and use the
file selection window that displays to select the Output File to receive converted
geometry.
4. Choose the Input File Type appropriate for the model being repaired.
5. Choose the Output File Type and Output Format Type in which to write the
repaired geometry.
6. Click Process.
Error and informational messages from the process are sent to the PolyFix window
message area, and to a log file named "polyfix.log" created in the working directory.
Tips:
1. PolyFix-corrected model files can be used in VERICUT as solid stock, fixture,
design, or NC machine shapes. It is a one time effort to repair an inconsistent
model file.
2. After repair, use the "Outward" normals option when referring to the repaired
model file in VERICUT.

15
 VERICUT Converters and Interfaces

Surface to Solid Converter

Introduction to the Surface to Solid Converter

The Surface to Solid Converter creates solid models from open surface STL and
VERICUT Polygon Model files. Parent surface(s) can be offset, and then projected to a
plane to create a solid model. This converter is particularly useful to create
casting/forging stock models from design surface data. The Surface to Solid Converter
has the ability to output data as VERICUT or STL model files, in ASCII or binary file
format. Solid model files can be created from surfaces interactively in VERICUT, via
batch processing, or outside of VERICUT by running the "sur2stk" command file.

16
 VERICUT Converters and Interfaces

Surface to Solid Converter window

Location: File menu > Convert > Surface To Solid

The Surface to Solid Converter creates solid models from open surface STL and
VERICUT Polygon Model files. Parent surface(s) can be offset, and then projected to a
plane to create a solid model. This converter is particularly useful to create
casting/forging stock models from design surface data. The Surface to Solid Converter
has the ability to output data as VERICUT or STL model files, in ASCII or binary file
format. Solid model files can be created from surfaces interactively in VERICUT, via
batch processing, or as a stand-alone utility outside of VERICUT by running the
"sur2stk" command file located in the "commands" directory of your VERICUT
installation.

17
 VERICUT Converters and Interfaces

Input File — Name of the file containing the surface data to create a solid from. Enter
the /path/filename in the Input File text field or click on the (Browse) icon to
display the Select Input File file selection window and use it to specify the
/path/filename.
Output File — Name of the file to receive converted geometry. Enter the /path/filename
in the Output File text field or click on the (Browse) icon to display the Select
Output File file selection window and use it to specify the /path/filename.
Input File Type — Type of input file to read. Options are: VERICUT or STL.
Output File Type — Same as Input File Type, except applicable to the output file.
Output File Format — Format of the output file. Options are: BINARY or ASCII.
Tolerance — Specifies the tolerance used when offsetting and projecting the surface(s)
to create a solid model.
Offset — Distance and direction in which to offset the design surface, as applied in the Z
direction. For example: ".100" applies an offset of .100 to the surface in the Z+ direction.
A value like "-.100" applies the offset in the Z- direction, effectively "shrinking" the
model.
Base Location — Specifies the Z value of the plane to become the base of the solid
model. The surface is projected along the Z-axis to this plane.
Project Rectangle — When active, expands surface edges to create a rectangular base.
The size of the rectangular base is determined by the X-Y bounding region of the surface
data.

Transformation Matrix — Transforms the solid model. Use this feature is used when
Offset and Base Location values were entered with respect to a tool path coordinate
system instead of the model coordinate system. Matrix values correspond to MSYS
record values that appear in a NX CLS file: dx,dy,dz,Ivx,Jvx,Kvx,Ivy,Jvy,Kvy where
"dx,dy,dz" specify the distance to the local coordinate system origin, and "Ivx,Jvx,Kvx,
Ivy,Jvy,Kvy" specify the orientation of the local coordinate system X and Y axis vectors
with respect to the surface model coordinate system.
Process — Processes (converts) the surface data according to the current window
settings. Converted geometry is written to the Output File. Error and informational

18
 VERICUT Converters and Interfaces

messages from the process are sent to the Surface to Solid Converter window message
area.
Clear — Clears the Surface to Solid Converter window message area.
Close — Closes the Surface to Solid Converter window.
Help — Displays this Help page. (You can also use the F1 key to display this Help page.

19
 VERICUT Converters and Interfaces

Converting Surface Data to Solid Models

Use the Surface to Solid Converter and the procedure below to create solid models from
open surface VERICUT or STL model files. This converter is particularly useful to create
casting/forging stock models from design surface data.
NOTE: Surface data can also be converted to solid models via batch processing.

To convert surface data to a solid model file:

1. Access the Surface to Solid Converter window: in VERICUT select File menu
> Convert > Surface to Solid.
You can also run this converter outside of VERICUT via the "sur2stk" command
file located in the CGTech "commands" directory, under the directory
representing your computer type.
2. Type the /path /filename in the text field, or use the Browse button and use the
file selection window that displays to select the Input File containing the IGES
data to convert.
3. Type the /path /filename in the text field, or use the Browse button and use the
file selection window that displays to select the Output File to receive converted
geometry.
4. Choose the Input File Type appropriate for the surface model being converted to
a solid.
5. Choose the Output File Type and Output Format Type in which to write the
solid model geometry.
6. Enter the Tolerance for offsetting and projecting the surface to create the solid.
7. Enter any Offset amount to apply to the surface, for example to add stock for
machining on the converted solid model.
8. Enter the Base Location - Z value of the plane to project the surface to.
9. To expand the surface edges to create a rectangular base, click Project
Rectangle.
10. To transform the solid model, enter 9 values separated by spaces in the
Transformation Matrix field. Format: dx,dy,dz,Ivx,Jvx,Kvx,Ivy,Jvy,Kvy where
"dx,dy,dz" specify the distance to the local coordinate system origin, and
"Ivx,Jvx,Kvx, Ivy,Jvy,Kvy" specify the orientation of the local coordinate system
X and Y axis vectors with respect to the surface model coordinate system.
Tip: Matrix values correspond to MSYS record values that appear in a NX CLS
file.
11. Click Process.

20
 VERICUT Converters and Interfaces

Error and informational messages from the process are sent to the Surface to Solid
Converter window message area.

21
 VERICUT Converters and Interfaces

VDA Converter

Introduction to the VDA Converter

The VDA Converter converts (translates) geometry conforming to the VDA (Verband
der Automobilindustrie Surface Interface) 2.0 specification to Stereolithography or
VERICUT Polygon model files. This converter lets you make the most of your existing
CAD data by enabling you to import complex castings, clamps, fixtures, and other design
models into VERICUT, as well as generate design point data for use by the AUTO-DIFF
function in VERICUT. VDA data can be converted interactively in VERICUT, via batch
processing, or outside of VERICUT by running the "vda" command file.

VDA data and version support

CGTech's VDASF Converter can convert the VDA data elements listed below. The
elements that are actually converted depend on the type of output file being generated by
the converter.
POINT
PSET (point set)
MDI (set of point/vectors)
SURF (base surface)
FACE (trimmed surface)

22
 VERICUT Converters and Interfaces

VDA Converter window

Location: File menu > Convert > VDASF

The VDA Converter converts (translates) VDA geometry to Stereolithography or

VERICUT Polygon model files. This converter is used to import complex castings,
clamps, fixtures, and other design models into VERICUT, as well as generate design
point data for use by the AUTO-DIFF function in VERICUT. VDA data can be
converted interactively in VERICUT, via batch processing, or as a stand-alone utility
outside of VERICUT by running the "vda" command file located in the "commands"
directory of your VERICUT installation.
Tip: When expecting to use VDA data for solid models in VERICUT, ensure that
surface normals all point outwards in the CAD model prior to outputting the VDA data.

Input File — Name of the file containing the VDA data to convert. Enter the
/path/filename in the Input File text field or click on the (Browse) icon to display
the Select Input File file selection window and use it to specify the /path/filename.

23
 VERICUT Converters and Interfaces

Output File — Name of the file to receive converted geometry. Enter the /path/filename
in the Output File text field or click on the (Browse) icon to display the Select
Output File file selection window and use it to specify the /path/filename.
Output File Type — Type of output file to create. Options are: VERICUT, STL or
POINT (Design Points file). The VDA data elements that are converted depend on the
type of file being generated.
Output File Format — Format of the output file. Options are: BINARY or ASCII.
Option not applicable to Point output file types.
Normal Direction — The direction in which surface normal vectors point, as viewed in
the CAD system. Feature only applicable to VERICUT output file types. Options:
OUTWARD or INWARD.
Tolerance — Specifies the amount of chordal deviation allowed in 3-D space from the
VDA surface when creating the converted surface. The converted surface is
approximated using "facets", or triangles. This option not applicable to POINT Output
File Type.
Process — Processes (converts) the VDA data according to the current window settings.
Converted geometry is written to the Output File. Error and informational messages
from the process are sent to the VDA Converter window message area, and to a log file
named "vda.log" created in the working directory.
Clear — Clears the VDA Converter window message area.
Close — Closes the VDA Converter window.
Help — Displays this Help page. (You can also use the F1 key to display this Help page.)

24
 VERICUT Converters and Interfaces

Converting VDA Data

Use the VDA Converter and the procedure below to convert VDA data to VERICUT or
STL model files, or Design Points files for use by the AUTO-DIFF function.
NOTE: VDA data can also be converted via batch processing.

To convert VDA data to VERICUT or STL model files, or Design Points files:
1. Access the VDA Converter window: in VERICUT select File menu > Convert
> VDAFS.
You can also run this converter outside of VERICUT via the "vda" command file
located in the CGTech "commands" directory, under the directory representing
your computer type.
2. Type the /path /filename in the text field, or use the Browse button and use the
file selection window that displays to select the Input File containing the VDA
data to convert.
3. Type the /path /filename in the text field, or use the Browse button and use the
file selection window that displays to select the Output File to receive converted
geometry.
4. Choose the Output File Type and Output Format Type in which to write the
converted geometry.
5. If the Output File Type= VERICUT, choose the Normal Direction in which
surface normal vectors point, as viewed in the CAD system. If unknown choose
INCONSISTENT.
6. Enter the Tolerance allowed from the VDA surface for surface approximation.
7. Click Process.
Error and informational messages from the process are sent to the VDA Converter
window message area, and to a log file named "vda.log" created in the working directory.
Tip: When expecting to use VDA data for solid models in VERICUT, ensure that
surface normals point unidirectionally outwards in the CAD model prior to outputting the
VDA data.

25
 VERICUT Converters and Interfaces

Binary CL Converter

Binary to ASCII CL Converter window

Location: File menu > Convert > Binary CL

The Binary CL Converter converts binary APT CL data into ASCII low level APT tool
path files. Binary CL data is the pre-processed NC data typically sent to a post-processor.
Binary CL data files can be converted interactively in VERICUT, via batch processing,
or as a stand-alone utility outside of VERICUT by running the "bincl2v" command file
located in the "commands" directory of your VERICUT installation.

26
 VERICUT Converters and Interfaces

Input File — Name of the file containing the binary CL data to convert. Enter the
/path/filename in the Input File text field or click on the (Browse) icon to display
the Select Input File file selection window and use it to specify the /path/filename.
Output File — Name of the file to receive converted APT tool path records. Enter the
/path/filename in the Output File text field or click on the (Browse) icon to display
the Select Output File file selection window and use it to specify the /path/filename.
APT Table File — Name of the APT Table file containing information for converting
binary APT data into ASCII APT NC program records. Enter the /path/filename in the
APT Table File text field or click on the (Browse) icon to display the Select APT
Table File file selection window and use it to specify the /path/filename.
Input File Type — Type of binary input file to read.
Options are:
IBM Mainframe APT (APT/360, APT/370, APT/AC, or MDCAPT)
Workstation IBM APT
Workstation CATIA APT
VAX APT
Minimum Cutter Height — Default height used when cutter height is not defined in the
binary APT data.
Output Circles — When active, outputs CIRCLE records for circular motion. Clearing
this check box causes chordal GOTO points to be output representing each circle.
Process — Processes (converts) the binary CL data according to the current window
settings. Converted tool path records are written to the Output File. Error and
informational messages from the process are sent to the Binary CL Converter window
message area.
Clear — Clears the Binary CL Converter window message area.
Close — Closes the Binary CL Converter window.
Help — Displays this Help page. (You can also use the F1 key to display this Help page.)

27
 VERICUT Converters and Interfaces

Converting Binary APT Data

Use the Binary CL Converter and the procedure below to convert binary APT CL data
into ASCII low level APT tool path files.
NOTE: Binary APT data can also be converted via batch processing.

To convert binary CL data to ASCII APT tool path files:

1. Access the Binary CL Converter window: in VERICUT select File menu >
Convert > Binary CL.
You can also run this converter outside of VERICUT via the "bincl2v" command
file located in the CGTech "commands" directory, under the directory
representing your computer type.
2. Type the /path /filename in the text field, or use the Browse button and use the
file selection window that displays to select the Input File containing the binary
CL data to convert.
3. Type the /path /filename in the text field, or use the Browse button and use the
file selection window that displays to select the Output File to receive converted
APT tool path records.
4. If required, Type the /path /filename in the text field, or use the Browse button
and use the file selection window that displays to select the APT Table File
containing the desired blocking factor and binary data to APT word table.
5. Choose the Input File Type that best describes the source of the binary CL data.
6. If cutter height is not specified in the binary CL data, enter a Minimum Cutter
Height value.
7. By default, circular motions will be output as CIRCLE records. To output GOTOs
instead of CIRCLEs, clear the Output Circles checkbox.
8. Click Process.
Error and informational messages from the process are sent to the Binary CL Converter
window message area. The APT CL-record number (not ISN) is placed in columns 73
through 80 on each output record of the tool path. This number can be useful when using
the History function to identify tool path records responsible for errors and other machine
cuts. (Ref. Analysis menu > X-Caliper in the VERICUT Help section, in the CGTech
Help Library)
Tips:
1. If the output APT tool path file contains incorrect, little, or no APT record data,
verify that the blocking factor is correct for the binary data. Typical blocking
factors are: 512, 3228, 4628, 15476.

28
 VERICUT Converters and Interfaces

2. If the output APT tool path file has major or minor words other than expected, try
editing the APT Table file to change the "Word" output for a specific APT
class/subclass.

29
 VERICUT Converters and Interfaces

Post Processor

Post Setup window

Location: File menu > Convert > Post Processor

The features in the Post Setup window enable you to select and view a VERICUT
VCPost post processor file and select, generate, and view the posted output file.

30
 VERICUT Converters and Interfaces

(Close Window) — Use this icon to close the Post Setup window.

SubSystem ID — Use to specify ID of the machine subsystem for which you are
generating posted output for. Select from the pull-down list of subsystems defined for the
current machine.

Post Commands — The Post Commands list contains a list of the subroutines used in
the post processor.

Post Processor File — Name of the VCPost post processor to use. Click on the
(Browse for post-processor) icon to display the Open Robot Post file selection window
and use it to specify the /path/filename.

(Edit Post-Processor) — Opens the post processor file in a text editor window (ref.
Text File in the Edit menu section of VERICUT Help for a complete description of the
text editor's features) enabling you to edit the post processor.

Post Output File — Name of the file to receive the posted output data. Enter the
/path/filename in the Post Output File text field or click on the (Browse for Post
Output file) icon to display the NC Program file selection window and use it to specify
the /path/filename.

(Edit Post Output File) — Opens the Post Output File in a text editor window (ref.
NC Program Editor in the Project Tree section of VERICUT Help for a complete
description of the text editor's features) enabling you to edit the posted NC program file.

PostOutLog — Name of the file to receive the post log data. Enter the /path/filename in
the PostOutLog text field or click on the (PostLogBrowse) icon to display the
PostLogFile file selection window and use it to specify the /path/filename.

(PostEditLog) — Opens the post log file in a text editor window (ref. NC Program
Editor in the Project Tree section of VERICUT Help for a complete description of the
text editor's features) enabling you to view and/or edit the post log file.

31
 VERICUT Converters and Interfaces

Run Post while simulating — When toggled "on" (checked), the Post Output File is
generated during the NC program simulation. Note that you can start the simulation, stop
the simulation and then continue the simulation at any time during the post processing
cycle as long as you do not toggle "off" (unchecked) the Run Post while simulating
feature, marking the end of the generating posted output cycle.

32
 VERICUT Converters and Interfaces

CAD/CAM Interfaces

Select from the following:

CATIA V5-to-VERICUT Interface (CATV)
Edgecam-to-VERICUT Interface
GibbsCam-to-VERICUT Interface (GibbsV)
Mastercam-to-VERICUT Interface (MCAMV)
NX-to-VERICUT Interface (NXV)
Pro/E-to-VERICUT Interface (PROEV)

33
 VERICUT Converters and Interfaces

CATIA V5-to-VERICUT Interface

34
 VERICUT Converters and Interfaces

Using the CATIA V5-to-VERICUT Interface

For complete details on installing and configuring the CATIA V5-to-VERICUT
Interface, see Configuring the CATIA V5-to-VERICUT Interface, in the Configuring
CAD/CAM to VERICUT Interfaces section of Installing CGTech Products, located in the
CGTech Help Library.

When you trigger CATV, either with the toolbar icon ( ) or from the operating system
level, you should see a window similar to the one shown on the following page.

35
 VERICUT Converters and Interfaces

CATV5 Main Window

The remainder of this document explains each element of the interface.

36
 VERICUT Converters and Interfaces

CATIA can have more than one CATProcess file open at once. CATV is not aware when
you switch between files in CATIA. The "Update" button forces the program to refresh
the interface content from the currently active CATProcess file. If the active CATIA file
is not a CATProcess (it could be a CATPart for example) the program will display a
warning message.

CATV will generate several files to pass CATIA information to VERICUT. For
verification or simulation of one CATProcess file, the following can be created;

• Several temporary files (with the ".VcTmp" extension)

• tool libraries (with the ".tls" extension)
• model files (in STL or VRML format)
• NC programs (in APT or G-Code)

All these files will be placed in a single folder. If you have defined the
CGTECH_CATV_FOLDER environment variable, the folder it references will appear
in the upper text field of this pair. If not, the location of the CATProcess file will be
presented so that you can keep all the related files in one place. In either case you can
override the suggested folder, by entering a different location, or by browsing ( ) for
one.

The names of created tool libraries, model files and NC programs depend on the names of
the corresponding CATIA objects (CATParts, and Part Operations). But the temporary
files, the final VERICUT project, and its log file are given the same name, which is
provided by the lower text field of this pair. By default it will be filled in with the
CATProcess name, but you can override it if you wish.

37
 VERICUT Converters and Interfaces

The files generated by CATV are intended to be "add-ons" for existing VERICUT
projects that contain much more detail than is present in a CATProcess file. For example,
you may have a machine and control fully specified in a project file, and simply wish to
place the CATProcess stock and fixtures on this machine before verifying the new NC
programs. In this field you can specify a template file for the project. Normally such a file
has the extension ".VcProject". Note that you can also specify a different template for
each CATIA part operation (called a "Setup" in VERICUT). If you do not specify a
project template, either "init.VcProject" or "initm.VcProject" will be used, depending on
whether CATIA has the unit of length set to "inch" or "millimeter".

If you wish to append the part operations from a CATProcess file to the setups that are
already defined in your project template, you can click on the Append to existing setups
in project template check-box under the template field. Otherwise, and more typically,
the imported part operations will be the only setups in the generated project.

This list contains the names of all the part operations found in the CATProcess file.
Typically you would leave each setup "checked" so that they will all be simulated, but
you could cause any of them to be skipped by un-checking their names. When you select
a setup name, most of the other elements of the interface will change to reflect the
choices made for that setup. Items with blue labels are "project wide" and do not change.

38
 VERICUT Converters and Interfaces

If all part operations in the CATProcess use the same machine, and that machine is
defined in the project template file, you could leave the setup template field blank. If
there are several machines involved, you will need to have a VERICUT project file for
each one, and will specify which file each setup should use in this field.

CATV can generate a single VERICUT view for each setup, with the stock in the same
orientation as it appears in CATIA. Alternatively, if you wish to see the view (or views)
already established in the setup (or project) template file, you can click on the Use view
or views defined in setup check-box.

Typically you would have CATV generate tool libraries (with the ".tls" extension) from
the tool data in the CATProcess file for each setup. Alternatively, if you choose to create
a single tool library for all setups, click on the Generate one tool library for all setups
check-box. In either case, select Generate tool library from CATIA information from
the pull-down list.

You can also elect, on a setup by setup basis, to merge the generated tools into the library
which is referenced by your setup (or project) template file, to use that referenced library
"as is", use an existing tool library by selecting it, or use a tool list from a TDM database
by specifying its name. Using any of these last three options implies that you are sure that
the tool geometry present in the CATProcess file is accurately represented in the
referenced library, selected library or specified TDM list. Select the desired option from
the pull-down list.

Within the CATProcess file you can define the cutting geometry of a wide variety of tool
types, and for milling tools define their holders as a stack of up to five cylinders and
cones. If this is not adequate, you can define a milling tool's cutter and holder with a
CATPart or CATProduct. A CATPart would contain two sketches, with names "CUT"
and "NOCUT" to define the half cross-section which is rotated around the tool's axis.
Typically the part can have shafts defined by the rotated sketches, but this is not essential.

39
 VERICUT Converters and Interfaces

A CATProduct can reference multiple CATParts, each with a named attribute,

"CuttingType". Values of these attributes can be "CUTTER", "SHANK" or "HOLDER"
and each CATPart should contain a sketch to define the half cross-section which is
rotated around the tool's axis. Shafts can be defined by the rotated sketches, but this is not
a requirement.

To make CATV aware of these custom milling tool profiles, click on the "Custom Tools"
button, which is blue to reflect the fact that the connections that you make between tool
names and CATParts or CATProducts will be "project wide". If the same tool is used in
more than one setup, it is only necessary to specify once the CATPart or CATProduct
containing its sketches. When you click on the "Custom Tools" button, the Custom Tool
Geometry window is displayed.

40
 VERICUT Converters and Interfaces

CATProcess files with multiple part operations seem to exhibit two different operator
styles. In the first style, the stock is represented just once and each setup contains a
different set of fixtures, some of which will typically be instances of the same
CATProduct or CATPart. The second style may or may not use a common set of fixtures,
but will have multiple instances of the stock, probably in different orientations and
locations. In VERICUT, we need to know what happens to the stock between setups.

You need to pick an axis system in each setup which has the same relationship to the
stock. Thus if the stock needs to be flipped over between setup one and two, you would
pick an axis system for both, but two of the axes will probably be reversed in the second
one. Typically the same axis system in the two instances of the stock model is adequate.
To graphically select an axis system, click on the button, then pick a machining axis
system or an axis system on a part. Use CATIA's "Edit" > "Undo" option to exit
selection mode without making a choice. Note that you can reverse the selection
sequence by picking an axis system first, then clicking the button. The name of the
selected axis system will appear in the Stock axis system field.

If the Attach axis system field is left blank the setup's machining axis system will be
placed on one of the VERICUT machine's "attach" components. Note that a setup's
machining axis system is the last such system encountered in CATIA's process tree
before the setup's first active tool change. This is not always the axis system of the
CATIA machine. If the setup's machining axis system does not coincide with one of the
VERICUT "attach" components, you can pick a different axis system for the setup.

To graphically select an axis system, click on the button, then pick a machining axis
system or an axis system on a part. Use CATIA's "Edit" > "Undo" option to exit
selection mode without making a choice. Note that you can reverse the selection
sequence by picking an axis system first, then clicking the button. The name of the
selected axis system will appear in the Attach axis system field.

41
 VERICUT Converters and Interfaces

In the Attach component name field you can specify the name of the corresponding
"attach" component. If left blank, the default name "Attach" will be used.

This field will only be enabled when you elect to generate G-Code programs. It should
specify the post-processor to be used to convert APT to G-Code. Posts from three
vendors are supported by CATIA; Cenit, IMS and ICAM. Their location is dependent on
where CATIA was installed, but will typically be in folders under "C:\Program
Files\Dassault Systemes\B16\intel_a\startup\Manufacturing". Cenit posts have the
extension ".pp", IMS uses ".lib" and ICAM's have ".dmp". You can paste a post-
processor's full path and filename into the Post-processor field, or browse ( ) for it.

For each setup you should specify which of the CATParts represent the design, the stock
and the fixtures. Normally it is only necessary to have a stock model for the first setup, as
it will get passed to subsequent ones in VERICUT. Likewise you will probably only
nominate a design model in the last setup, to be used with AUTODIFF. But fixturing will
often be different in each setup.

If design, stock or fixture models have been specified in CATIA for its video
"simulation" capability, you can use the corresponding button to wipe out any parts
currently in the displayed list, and replace them with the parts used for CATIA's video.

Otherwise you can graphically select design, stock or fixture models, click on the
corresponding button. Then you can pick a product from any level in CATIA's product
list tree, or from the picture of the models. Note that the product must be within the major
branch of the tree that is referenced by the setup's part operation. All instance names of
all CATParts under the selected product in the tree will be placed in CATV's list for this
setup. Use CATIA's "Edit" > "Undo" option to exit selection mode without making a
choice. Note that you can reverse the selection sequence by picking a product first, then
clicking the button.

42
 VERICUT Converters and Interfaces

If a CATPart selected for a Fixture, Stock or Design ...

1) contains just one body, which
2) contains just one shape, and
3) that shape is a shaft, which
4) is spun through 360 degrees, and
5) the spin axis is one of the 2 sketch axes, and
6) the profile contains only lines and circular arcs,
... then CATV will generate an SOR file instead of an STL or VRML.
Coordinate systems associated with a CATPart that gets converted to a VERICUT model
are handled according to the following:
1) Any non-hidden axis system, within a CATPart that gets converted to a VERICUT
model, is placed in the setup(s) that reference that part.
2) Axis systems are attached to the component that contains the part, be it a fixture,
stock or design.
3) Axis system names have 2 elements separated by a backslash ...
"part_name\axis_name".
4) Left-hand systems in CATIA come thru as right-hand systems. The Z axis gets
flipped.

If you decide that you don't want all the detailed parts, such as bolts, transferred to
VERICUT, you can remove names from any of the three lists by selecting them and
clicking on the appropriate button. The "Shift" and "Ctrl" keys can be used in the
normal way to select multiple names from the list so they can be removed together.

The 32 bit version of VERICUT can accept part models in a variety of formats,
including STL, VRML and native CATPart files.

You can adjust the precision of STL and VRML model types by performing the
following procedure in CATIA. This only needs to be done once.

1. Pick "Tools" > "Options ..." from the CATIA menus.

2. In the "Options" dialog, expand the "General" branch of the tree.
3. Pick the "Display" sub-branch.
4. Bring the "Performances" tab to the front.

43
 VERICUT Converters and Interfaces

5. Under "3D Accuracy" pick "Proportional", and move the corresponding slider to
the extreme left. The displayed value will then be "0.01".
6. Click on the "OK" button.

The ability to generate VRML files is license dependent in CATIA, so if your site does
not have the feature, elect to use STL or CATPart files. STL models are handled faster
than VRML models by both CATIA and VERICUT, but VRML models can give
superior graphics provided the following procedure has been performed once in CATIA;

1. Pick "Tools" > "Options ..." from the CATIA menus.

2. In the "Options" dialog, expand the "General" branch of the tree.
3. Pick the "Compatibility" sub-branch.
4. Bring the "VRML" tab to the front (it is on the extreme right of the tabs).

44
 VERICUT Converters and Interfaces

5. Select the "VRML 97" export version.

6. Select the "Save Normals" export option.
7. Click on the "OK" button.

Using CATParts is the fastest choice for CATV because the files are simply referenced,
but there is a performance penalty when VERICUT has to first access these files.
Because some models may be used in several setups, this is a "project wide" parameter,
so that we avoid having more than one version of the same model.

Specify whether the NC programs to be passed to VERICUT are APT or G-Code. APT
programs can be generated more quickly, since the post-processing step is not required,
and are fine for initial program verification. G-Code is one of the prerequisites for
machine simulation.

45
 VERICUT Converters and Interfaces

Determination of the fast feedrate, which will be set in the VERICUT project file, is
dependent on this choice. For APT programs, the first 5000 lines of the first program are
scanned, and the fastest of the encountered feedrates is used, with the addition of a small
increment (0.05 when the linear unit is "inch", 1.0 when it is "millimeter"). For G-Code
programs, all the active machines in the CATProcess file are scanned, and the largest of
their maximum fast feedrates is used.

CATV can cause CATIA to generate the NC programs defined in the CATProcess file.
Alternatively you can choose to select NC programs that have already been created. G-
Code programs produced by a post-processor that is not accessible within CATIA would
be a good example.

Specify here whether the NC programs to be generated by CATIA, or those selected,

have the tip of the tool as the driven point, or a point on the tool axis inset from the tip by
the corner radius. The third choice "Ball Center" will use the center of any ball-end
cutters, and the tip for any other style.

Pressing the "Options" button displays the Options window whose features enable you to
specify a model chordal deviation, a VERICUT G-Code table, and the Source of G-Code
tool identifiers.

46
 VERICUT Converters and Interfaces

If you choose to have CATV and CATIA generate the NC programs, they will be listed
here as they are created. Alternatively you can browse ( ) for existing programs. If you
do so, it is important to ensure that the list is in the order of cutting. You can erase ( )
programs from the list, or re-arrange ( or ) them.

If you have G-Code programs that reference subroutines, you can browse ( ) to select
the existing subroutine files. You can also erase ( ) subroutines from the list.

When you have provided CATV with all the information it needs, you can perform the
transfer of data to, and triggering of, VERICUT. Click on the "Generate files" button to
create the tool libraries, models and NC programs without triggering VERICUT. Once
you have all the files needed, you can fire up VERICUT with the "Run VERICUT"
button. You can perform both of these steps at once with the "Generate and run" button.
Data transfer, particularly if you are generating and post-processing large NC programs,
can be time consuming, so a dialog is presented which provides a simple indication of
progress. The "Exit CATV" button terminates the program.

47
 VERICUT Converters and Interfaces

CATV5 Custom Tool Geometry Window

If your site uses one or more CATIA tool catalogs, which most likely started life as Excel
spreadsheets, and you have the ".csv" versions of those catalogs, then you can use them
to populate the two lists in the "Custom Tool Geometry" dialog shown below. Use the
upper button to browse for a ".csv" catalog. When you click on the "Read" button, the
catalog is scanned for any of the tool identifiers in the left-hand list. When a tool is
found, the reference to the CATPart or CATProduct that defines the tool geometry is
copied from the tool's catalog entry to the right-hand list. You can repeat this process for
each relevant catalog, assuming that if a tool appears in more than one catalog then its
referenced CATPart or CATProduct will be the same in each.

To make the connection between a tool and its CATPart or CATProduct, select the tool's
name in the list on the left, then click on the icon. You will be offered the usual file
selection dialog to pick a CATPart or CATProduct, and the file's name will then be
displayed in the list on the right.

Repeat this sequence for all the tools that have corresponding CATParts or CATProducts.
If you wish to break a connection, and revert to using the CATProcess file's definition of
a tool's geometry, you can select the tool in the list and click on the icon. When you
have all the pairings established, click on the "OK" button and the dialog will disappear.

48
 VERICUT Converters and Interfaces

CATV5 Options Window

49
 VERICUT Converters and Interfaces

By default the precision of the created STL or VRML files is controlled by settings
within CATIA, and will be the same for all design, stock and fixture models.
Alternatively, you can use the Model chordal deviation features to specify a different
chordal deviation for any or all of the three types of model, by "checking" types and
providing maximum deviation distances. These options pertain to all setups.

For each CATIA part operation, the machining axis system defines the origin of the
coordinates in the NC programs. Typically this origin will be used to define the content
of the "Program Zero" table in VERICUT. But you can use the VERICUT G-Code
table features to define other VERICUT tables that you could use to locate the NC
programs relative to the machine axes.

For example, you may wish to use a "Work Offsets" table for register 54. Select the table
from the Table name pull-down list, or enter a different name if necessary. Use the Sub-
system and Register number text fields to enter additional information related to the
table. If you click on the button, the list of table names will be populated by scanning
the template for the setup or project. The first table encountered that has an associated
sub-system, register number and "from" component will become the selected one.
You can also use the "From" component feature to associate the machining axis system
to a different component of the machine, such as a head or turret.

When CATIA uses a post-processor to generate the NC programs, the tool identifiers
within the G-Code can be extracted from several of the tool, or tool assembly's
parameters. Typically the tool number (for a milling tool), or the assembly number (for a
turning tool), are used. But a post-processor could access names or comment fields too.

Use the Tool (milling) or assembly (turning) parameter features to specify which field
contains the tool identifiers. Use the last five features in the Source of G-Code tool
identifiers section to specify how identifiers are to be extracted from the chosen field.

The "Defaults" button can be used to revert to the "Program Zero" table and using the
entire number field as the source of tool identifiers.

Press the "OK" button when you have defined the table parameters and/or the source of
the G-Code tool identifiers, and the extra "Options" window will disappear.

50
 VERICUT Converters and Interfaces

Edgecam-to-VERICUT Interface

51
 VERICUT Converters and Interfaces

Using the Edgecam-to-VERICUT Interface

The following information applies to Edgecam versions 10, 11, 11.75, 12, 12.5, 2009 R1,
2009 R2 and 2011. It assumes that you have already installed the Edgecam-to-VERICUT
Interface.
For complete details on installing and configuring the Edgecam-to-VERICUT Interface,
see Configuring the Edgecam-to-VERICUT Interface, in the Configuring CAD/CAM
to VERICUT Interfaces section of Installing CGTech Products, located in the CGTech
Help Library.
Starting with Edgecam Version 10 and VERICUT Version 6.0, this interface transfers
multiple Edgecam Machining Sequences to corresponding VERICUT Setups.
The Edgecam-to-VERICUT Interface is divided into two steps. The first step, VERICUT
Setup, collects and saves data for each Machining Sequence. The second step, Run
VERICUT, transfers the data and executes VERICUT.

Vericut Setup Options window

In the Edgecam main menu bar select Options > Manufacture, or click on the
(Switch to Manufacture Mode) icon to switch to manufacturing mode. Once in
manufacturing mode, select Custom menu > Extras > Vericut Setup Options, or
Vericut menu > Vericut Setup Options if you added this feature to the Edgecam menu
bar, to display the following menu:

52
 VERICUT Converters and Interfaces

VERICUT Setup Options window: General tab

Enter or modify the features on the General tab to define options and where the working
files are located. This data is retained as an attribute associated with the Edgecam
machining sequence name and saved in the Edgecam part file. The last values entered
will be recalled when the Edgecam-to-VERICUT Interface is reused.

Active — When toggled "On" (checked), this machining sequence will be transferred
to VERICUT. When toggled "Off" the machining sequence is skipped, but the data is
saved.
FastMill Cut Mode — When toggled "On" (checked), VERICUT runs in "FastMill"
cut mode where all MC program records are processed as quickly as possible without
displaying animated cutting, until the final machined workpiece is displayed.
Create Tool Library — When toggled "On" (checked), the interface creates a
VERICUT tool library. Otherwise, the tool library associated with the VERICUT
Project File Template is used.
Use Tool Description — When toggled "On" (checked), VERICUT uses the
Edgecam ToolStore value as the VERICUT Tool ID. When toggled "Off",
VERICUT uses the Position value as the VERICUT Tool ID. See the example below:
Consider the following Edgecam tool dialog. It uses the tool number (Position integer
value) to effect the tool change and uses tool description (ToolStore text value) as a
comment.

53
 VERICUT Converters and Interfaces

With the Use Tool Description box unchecked, VERICUT will create a tool library file
(.tls) that looks like the following:

But with Use Tool Description toggled “On” (checked), VERICUT will create a tool
library file (.tls) that looks like the following:

NOTE: This feature was not available prior to Edgecam Version 12.5.

54
 VERICUT Converters and Interfaces

Output VcProject File — Enter the directory path, or use Browse to specify the
location where the VERICUT .VcProject file, the tool library file, and any other
associated files should be written. The file name entered will be used for the project
file, the tool library file, and any stock files created. The default is the current
Edgecam part name.
NOTE: Early versions of the Edgecam-to-VERICUT Interface called this feature
Output User File.
ToolPath File — Enter the directory path and filename of the NC program file being
simulated. The default is the last file post-processed by Edgecam.
Vericut Template — Enter the directory path and filename of a VERICUT
.VcProject file containing the correct machine and control to be simulated. This
template file must also define the "Input Program Zero" table from component "Tool"
to CSYS "Prog_Zero".

The Edgecam dialog text entries are limited to a fixed width. You can scroll to enter a
long path name or use the Browse button.

VERICUT Setup Options window: Offsets tab

The Offsets tab enables the Edgecam stock (also fixtures and the design model) to be
translated from the component attach point on the VERICUT machine. The default
"Apply to Program Zero" relationship with the values allows the program zero to
follow the XYZ offset values. The Edgecam stock can be attached at the center of
rotation for multi-axis programs or at the initial CPL defined with Edgecam's machining
sequence for most 3-axis programs.

55
 VERICUT Converters and Interfaces

Attach Stock at Center of Rotation — When toggled "On" (checked), stock is

attached at the center of rotation.
Apply to Program Zero — When toggled "On" (checked), the XYZ offset values
are applied to the Program Zero.
X-Shift (Stock and Program Zero) — Use to specify the X offset value.
Y-Shift — Use to specify the Y offset value.
Z-Shift — Use to specify the Z offset value.

Click OK when entries on all tabs are complete to save the information. Repeat this step
to define or modify options associated with each Edgecam machining sequence.

Run VERICUT
In the Edgecam main menu bar select Options > Manufacture to switch to
manufacturing mode. Once in manufacturing mode, select Custom menu > Extras >
Run Vericut Setup, or Vericut menu > Vericut Setup Options, if you added this
feature to the Edgecam menu bar, to display the following window:

Batch Mode — When toggled "On" (checked), VERICUT runs unattended in the
background. When the VERICUT window opens, the NC program verification
process is complete and the part is displayed in its processed state.

Click OK will display the following window:

56
 VERICUT Converters and Interfaces

Click OK to start the transfer of data and start a VERICUT session.

Click Cancel to cancel the transfer of data and the VERICUT session and return to the
Edgecam session.

57
 VERICUT Converters and Interfaces

GibbsCAM-to-VERICUT Interface (GibbsV)

58
 VERICUT Converters and Interfaces

Introduction to the GibbsCAM-to-VERICUT Interface

(GibbsV)

The GibbsCAM-to-VERICUT Interface, or "GibbsV", is a licensed software program

that provides a fully integrated GibbsCAM-to-VERICUT Interface. The interface
streamlines the verification and optimization of GibbsCAM generated tool paths.
Stock, fixture, and design models are automatically transferred to VERICUT, along with
tool path and tooling information.
VERICUT runs independently from GibbsCAM, so you can work in GibbsCAM while
verifying a tool path.
VERICUT has the ability to display and analyze geometric models as well as simulate
cutter motion and the material removal of an NC tool path. It also verifies the quality and
correctness of the tool path. Programming errors or inefficient motion are visually
detected during the simulation process, which aids the NC programmer in correcting the
tool path. Measurement tools are used at any time during the simulation process to verify
or compute the volume, distances and locations, as well as to compare various stages of
the "cut" part with other stages or with the "design" part.

Flow of information through GibbsV:

59
 VERICUT Converters and Interfaces

Using the GibbsCam-to-VERICUT Interface (GibbsV)

For complete details on installing and configuring the GibbsCam-to-VERICUT Interface,
see Configuring the GibbsCAM-to-VERICUT Interface (GibbsV), in the Configuring
CAD/CAM to VERICUT Interfaces section of Installing CGTech Products, located in the
CGTech Help Library.

Overview of Using GibbsV

The following overview describes how GibbsV is used with VERICUT and GibbsCAM
to simulate the cutting action of GibbsCAM-generated tool paths. Exact user actions in
GibbsCAM may vary, depending on the GibbsCAM version being used.

1. Prepare GibbsCAM model/tool path data.

In GibbsCAM, create the necessary model geometry and NC programs to simulate in
VERICUT.

2. Start the GibbsCAM-to-VERICUT Interface.

In the GibbsCAM main menu, click File > Open.
Browse and select GibbsCAM part file.
In the GibbsCAM main menu, click Plug-Ins > VERICUT to launch the
GibbsCAM-to-VERICUT Interface.
The GibbsV VERICUT Interface window opens.

3. Specify the location and base name for the VERICUT files.
In the Output Directory text field, Enter the /path/ to the directory where you want
the VERICUT files output ( .VcTemp, .tls, .ops, .ncf, .ply, .stl) in the text field, or
click on the Browse button, and use the file selection window that displays to specify
the /path/.
In the File Name text field, enter the "base" name for the VERICUT files that will be
created.
If desired, specify a Project Template file. Enter the /path/filename of the "template"
.VcProject file that you want loaded in the text field, or click on the Browse button,
and use the file selection window that displays to specify the /path/filename.
A project template (.VcProject) file is a previously defined VERICUT project file.

60
 VERICUT Converters and Interfaces

4. Tool Library Override.

If an override tool library is specified, then it is used instead of generating a new tool
library. If the tool library override field is left blank, then a new tool library is
generated.

5. Append setup option.

If you wish to append the part operations to the setups that are already defined in your
project template, you can click on the check-box under the tool library override field.
Otherwise, and more typically, the imported part operations will be the only setups in
the generated project.

6. Select attach component.

Select the corresponding "attach" component.

7. Select the NC program files to be simulated in VERICUT.

Click on the Select NC Program tab. Specify the NC Program type by selecting
either APT or G-Code. Then click on the Add button, to display a file selection
window and use it to select the NC program files.
You can use Delete to remove NC programs from the NC programs file list.
Click on the Generate NC Program tab. Enter /path/filename of the postprocessor
file in the Post-processor File text field or click on the Browse button, to display a
file selection window and use it to select the postprocessor file.

8. Attach Axis System and NC Program Zero.

For each workpiece in the Workpiece pull-down list, select an Attach Axis System
from the pull-down list, and then select an NC Program Origin from the pull-down
list

9. Select NC Subroutine Files.

If you have G-Code programs that reference subroutines, you can use Add to display
a file selection window and use it to select existing subroutine files to be added to the
NC Subroutine File list.
You can use Delete to remove subroutines from the NC Subroutine File list.

61
 VERICUT Converters and Interfaces

10. Generate Files and Run VERICUT.

Select Generate Files to output all files, for the GibbsCAM part file, including
project file, tool library file, NC program file, model files and the "operations" file
that assembles all of this information into a VERICUT "project" file.
Select Run VERICUT to start VERICUT with the files created by Generate Files.
NOTE: The values that you set in any of the GibbsV windows are saved as part
custom data in the GibbsCAM part file. When you re-open the GibbsCAM part file,
the GibbsV settings are recalled as they where when you saved the file.

62
 VERICUT Converters and Interfaces

Models

Stock, fixture and design models are associated by the GibbsCAM part file workpiece
name.
The fixture component is attached to the currently specified component in the "Attach
Component" list defined in the interface. If there are no components in "Attach
Component" list, then the fixture is attached to a component with the name of the
GibbsCAM part file workpiece. If there is no GibbsCAM part file work piece, then the
fixture is attached to the component called "Attach".
The stock component is attached to the fixture component that has the same GibbsCAM
part file work piece name. If no fixture component is found with the same GibbsCAM
part file work piece name, then the stock component is attached to the currently specified
component in the "Attach Component" list defined in the interface. If there are no
components in "Attach Component" list, then the stock is attached to a component with
the name of the GibbsCAM part file work piece. If there is no GibbsCAM part file work
piece, then the stock is attached to the component called "Attach".
The design component is attached to the stock component that has the same GibbsCAM
part file work piece name. If no stock component is found with the same GibbsCAM part
file work piece name, then the design component is attached to the fixture component
that has the same GibbsCAM part file work piece name. If no fixture component is found
with the same GibbsCAM part file work piece name, then the design component is
attached to the currently specified component in the "Attach Component" list defined in
the interface. If there are no components in "Attach Component" list, then the design is
attached to a component with the name of the GibbsCAM part file work piece. If there is
no GibbsCAM part file work piece, then the design is attached to the component called
"Attach".

63
 VERICUT Converters and Interfaces

GibbsV VERICUT Interface Window

Features in this window are used to select or generate a tool path and set options for
VERICUT simulation, and then run VERICUT.
To start the GibbsCAM to VERICUT Interface from within GibbsCAM, click Plug-Ins
in the GibbsCam main menu, then select VERICUT from the pull-down list to display the
VERICUT Interface window.
NOTE: The values that you set in any of the GibbsV windows are saved as part custom
data in the GibbsCAM part file. When you re-open the GibbsCAM part file, the GibbsV
settings are recalled as they where when you saved the file.
Sample VERICUT Interface window:

64
 VERICUT Converters and Interfaces

Output Directory — Enter the /path/ to the directory where you want the VERICUT
files output ( .VcTemp, .tls, .ops, .ncf, .ply, .stl) in the text field, or use the "Browse"
button to display a file selection window and use it to specify the /path/.
File Name — Enter the "base" name for VERICUT files that will be created.
Project Template — Enter the /path/filename of the "template" .VcProject file that you
want loaded in the text field, or use the "Browse" button to display a file selection
window and use it to specify the /path/filename.
A project template (.VcProject) file is a previously defined VERICUT project file.
Tool Library Override — If an override tool library is specified, then it is used instead
of generating a new tool library. If the tool library override field is left blank, then a new
tool library is generated.
Append to existing setups in Project Template — When toggled "On", GibbsV will
append the operations in the GibbsCAM part file, to the setups that are already defined in
your Project Template file, and setups from both files will be contained in the generated
project file. Otherwise, and more typically, the imported GibbsCAM part file will be the
only setups in the generated project file.
Attach component — Select the corresponding "attach" component.

(Select NC Program) — Use the features on this tab to select existing .ncf files.

Select APT or G-Code to specify the type of NC program.

Add — Click on the Add button and use the file selection window that displays to
select the required NC pogram files.
Delete — Use to delete the highlighted NC program files from NC programs file list.

65
 VERICUT Converters and Interfaces

(Generate NC Program) — Use the feature on this tab to create new .ncf files
from the GibbsCAM part file using a specified postprocessor.

Specify the /path/filename of the post-processor that you want to use in the Post-
processor File text field, or use click on the Browse button and use the file
selection window that displays to specify the post-processor file.

Workpiece — This list displays the names of all Workpieces in the GibbsCAM part file.
When you select a workpiece from the pull-down list, the Attach Axis System and NC
Program Origin selection apply to the currently selected workpiece.
Attach Axis System — This list displays the names of all coordinate systems in the
GibbsCAM part file. When you select a coordinate system from the pull-down list, it
becomes the Attach Axis System for the currently selected workpiece.
NC Program Origin choice list — This list displays the names of all coordinate systems
in the GibbsCAM part file. When you select a coordinate system from the pull-down list,
it becomes the NC Program Origin for all workpieces.
NOTE: There is only one NC Program Origin per GibbsCAM part file.
Initial Stock Only — When toggled "on" (checked), GibbsV will only transfer the initial
stock and the fixture and design models associated with it. All other models will be
ignored.

NC Subroutine Files — If you have G-Code programs that reference subroutines, Use
this feature to specify the subroutine files.
Add — Click on the Add button and use the file selection window that displays to
select the required NC Subroutine files.
Delete — Use to delete the highlighted subroutines from NC Subroutines File list.

Options — Displays the VERICUT Interface Options window.

66
 VERICUT Converters and Interfaces

Generate Files — Outputs all files, for the GibbsCAM part file, including project file,
tool library file, tool path file, model files and the "operations" file that assembles all of
this information into a VERICUT "project" file.
Run VERICUT — Launches VERICUT using the files created by Generate Files.
Generate and Run — Generates the files and then launches VERICUT in a single step.

Close — Saves values that you set in the GibbsCAM-to-VERICUT Interface as part
custom data in the GibbsCAM part file, and closes the GibbsV VERICUT Interface
window.

67
 VERICUT Converters and Interfaces

GibbsV-to-VERICUT Interface Options Window

Use the features of the GibbsV VERICUT Options window to pass information specific
to the model files (Stock, Fixture and Design), and machine settings, to VERICUT.
NOTE: The values that you set in any of the GibbsV windows are saved as part custom
data in the GibbsCAM part file. When you re-open the GibbsCAM part file, the GibbsV
settings are recalled as they where when you saved the file.

68
 VERICUT Converters and Interfaces

Output Model File Type — Use to specify the type of model files that are being passed
to VERICUT. Choose either VERICUT Model (VERICUT polygon file) or STL
(Stereolithography model file).
Output Model File Format — Use to specify the file format of the model files. Choose
either ASCII or Binary.
NOTE: "Binary" VERICUT polygon files are platform specific.
Output Model Tolerance — Specify tolerance values for Stock, Fixture, and Design
models in the corresponding text field.
Machine Settings —
Table Name – Select the name of a pre-defined table. If no table, then select
‘None.’ The default table name is ‘None.’
Register Number – Enter the register number. The default register number is 54.
‘From’ Component — Select the name of the component that represents the
"from" point for determining the offset. VERICUT will use the origin of the
specified component.
‘To’ CSYS — Select the name of a CSYS to represent the "to" point for
determining the offset. VERICUT will use the origin of the specified CSYS.

OK — Updates the GibbsCam part file with the current settings and closes the GibbsV
VERICUT Interface Options window and returns to the GibbsV VERICUT Interface
window.
Cancel — Closes the GibbsV VERICUT Interface Options window and returns to the
GibbsV VERICUT Interface window without updating the settings in the GibbsCAM
part file.

69
 VERICUT Converters and Interfaces

The gibbsv_user.prefs File

GibbsV uses a preference file to save/restore default settings. The preference file is
named gibbsv_user.prefs. The file will be saved on the HOMEDRIVE in the
HOMEPATH. The preference file is read when the GibbsV window opened and written
when the GibbsV window is closed. In GibbsV, the File Selection Box (FSB) filter is not
user modifiable via the interface. The file filters are stored in the preference file and can
be modified by the user. Here is a list of all tags that are supported:

GibbsVProjectTemplate
Corresponds to the Project Template feature on the GibbsV window.
Format: GibbsVProjectTemplate,/path/filename

GibbsVAppendSetups
Corresponds to the Append to existing setups in project template feature on the
GibbsV window.
Format: GibbsVAppendSetups,value
0 = OFF
1 = ON

GibbsVModelFileType
Corresponds to the Output Model File Type feature on the GibbsV Options window.
Format: GibbsVModelFileType,value
0 = VERICUT Model
1 = STL

GibbsVModelFileFormat
Corresponds to the Output Model File Format feature on the GibbsV Options window.
Format: GibbsVModelFileFormat,value
0 = ASCII
1 = Binary

GibbsVStockTol
Corresponds to the Output Model Tolerance: Stock feature on the GibbsV Options
window.
Format: GibbsVStockTol,tolerance value

70
 VERICUT Converters and Interfaces

GibbsVFixtureTol
Corresponds to the Output Model Tolerance: Fixture feature on the GibbsV Options
window.
Format: GibbsVFixtureTol,tolerance value

GibbsVDesignTol
Corresponds to the Output Model Tolerance: Design feature on the GibbsV Options
window.
Format: GibbsVDesignTol,tolerance value

GibbsVToolLibOverride
Corresponds to the Tool Library Override feature on the GibbsV window.
Format: GibbsVToolLibOverride,/path/filename

GibbsVTpType
Corresponds to the Select NC Program tab type features on the GibbsV window.
Format: GibbsVTpType,value
0 = APT
1 = G-Code

GibbsVTableName
Corresponds to the Machine Settings: Table Name feature on the GibbsV Options
window.
Format: GibbsVTableName,table name
Base Work Offset
Cutter Compensation
Gage Offset
Initial Machine Location
Input Program Zero (Special Z)
Machine Reference Location
Machine Zero
None
Probe Offset
Program Zero
RPCP Pivot Offset
RTCP Pivot Offset
Tool Change Location
Tool Change Retraction
Tool Length Compensation

71
 VERICUT Converters and Interfaces

Tool Nose Compensation

Turret Rotations
Work Offsets

GibbsVRegisterNumber
Corresponds to the Machine Settings: Register Number feature on the GibbsV Options
window.
Format: GibbsVRegisterNumber,value

GibbsVFromName
Corresponds to the Machine Settings: 'From' Component feature on the GibbsV
Options window.
Format: GibbsVFromName,component name

GibbsVToName
Corresponds to the Machine Settings: 'To' Component feature on the GibbsV Options
window.
Format: GibbsVToName,component name

GibbsVProjectFilter,*.VcProject

GibbsVTLibOverrideFilter,*.tls

GibbsVTpFilter,*.ncf

GibbsVPostFilter,*.pst

GibbsVSubFilter,*.sub

72
 VERICUT Converters and Interfaces

Mastercam-to-VERICUT Interface (MCAMV)

73
 VERICUT Converters and Interfaces

Introduction to the Mastercam-to-VERICUT Interface

(MCAMV)

The Mastercam-to-VERICUT Interface, or "MCAMV", is a licensed software program

that provides a fully integrated Mastercam-to-VERICUT interface. The interface
streamlines the verification and optimization of Mastercam-generated tool paths.
Verify individual paths, a series of selected paths, or a complete sequence of operations.
Stock models are automatically transferred to VERICUT, along with tool path and
tooling information.
VERICUT runs independently from Mastercam, so you can work in Mastercam while
verifying a tool path.
VERICUT has the ability to display and analyze geometric models as well as simulate
cutter motion and the material removal of an NC tool path. It also verifies the quality and
correctness of the tool path. Programming errors or inefficient motion are visually
detected during the simulation process, which aids the NC programmer in correcting the
tool path. Measurement tools are used at any time during the simulation process to verify
or compute the volume, distances and locations, as well as to compare various stages of
the "cut" part with other stages or with the "design" part.
Flow of information through MCAMV:

74
 VERICUT Converters and Interfaces

The Mastercam-to-VERICUT Interface is a Mastercam C-Hook application. It can be

invoked while running Mastercam, transfers internal Mastercam data to files recognized
by VERICUT, and fires up VERICUT ready to perform verification of the tool paths.
You can opt to verify Mastercam's Intermediate NC data (NCI) or the G-code files
produced by Mastercam's post-processors.

75
 VERICUT Converters and Interfaces

Accessing and Using the Mastercam-to-VERICUT

Interface (MCAMV - Versions 8 & 9)

Preparation
Mastercam V8 does not carry as much information about units in an ".MC8" file as
version 9 does in its ".MC9" files. Before using the VERICUT C-Hook with a Mastercam
V8 file, you need to ensure that it will be able interpret the units correctly. Having
retrieved an ".MC8" file with "File > Get", use "Screen > Configure" to bring up the
"System Configuration" dialog. In the low-left corner you will see a choice box labeled
"Current Configuration File" and each choice has "(English)" or "(Metric)" after the file
name. You need to ensure that the selected file has the same units as the job's stock. For
example, if you are using "Mill 9", you could select "Mill9.cfg (English)" or "Mill9M.cfg
(Metric)" depending on whether the job's units are inches or millimeters.

For complete details on installing and configuring the Mastercam-to-VERICUT Interface,

see Configuring Mastercam-to-VERICUT Interface, in the Configuring CAD/CAM to
VERICUT Interfaces section of Installing CGTech Products, located in the CGTech Help
Library.

Access
To trigger the C-Hook while in Mastercam, hold down the Alt key and click the C key
(referred to as Alt-C). You will see a file selection dialog offering all the installed C-
Hooks. Pick VERICUT.dll and click on the Open button.
Alternatively, you can add a reference to the C-Hook in Mastercam's menu structure,
either in an empty space, or by replacing a choice that you are unlikely to exercise.
Mastercam's documentation covers this process, but you would potentially need to edit
three files (mill9.txt, lathe9.txt and wire9.txt) if you intend to trigger VERICUT from all
three Mastercam applications. These files are located in Mastercam's installation folder
(for example C:\Mcam9).
To place a C-Hook in an empty menu location, between the double quotes enter the name
of the C-Hook, followed by an asterisk. So for this C-Hook it could read "VERICUT*".
Keep in mind that a menu cannot have more than ten choices. If you wish to use a key-
stroke to pick a menu item, you can precede the trigger letter with an ampersand, after
first checking that no other item in the menu uses the same letter. So if V is available, you
could enter "&VERICUT*".

76
 VERICUT Converters and Interfaces

Use
When you invoke the C-Hook the following dialog will display:

To verify NCI data, all you need to do is click the OK button. By default the files that are
needed by VERICUT will be generated in the same folder as the currently accessed
Mastercam file. You can nominate a different folder in the "Working Directory" section
of the dialog. If you wish to use a single folder for all the files generated by the interface,
regardless of the location of the Mastercam files, you can define an environment variable
to specify the folder. For example;

Environment Variable Name Variable Value

CGTECH_MCAM_FOLDER C:\Temp

77
 VERICUT Converters and Interfaces

If you wish to verify G-code data previously generated by one of Mastercam's post-
processors, select the "Verify G-Code" option. This will enable the last five input fields
in the dialog, for the specification of the G-code files and location of the stock on the
machine.
In Mastercam's "Operation Manager" you can select multiple operations, by clicking on
their names while holding the shift or control key down. The operations' icons will be
tagged with blue ticks. You can use this mechanism, and the C-Hook's "Selected
Operations" choice to restrict verification to a set of operations.
You can also specify a template user file (.usr) or in-process (.ip) file that the output of
the interface will be merged with in VERICUT. If you do not specify such a file, the
library copy of "init.usr" or "initm.usr" will be used, depending on the units of the
Mastercam data. If you specify a template file, you can also opt to use the tool library
which it references, instead of having the interface generate one.
If you elected to verify G-code files you can specify one or two by entering their paths
and names, or by browsing for them. The template user file or in-process file will need to
contain a machine and control definition. To assist you in placing the stock at the correct
location on the VERICUT machine, the delta X, Y and Z values can be specified and will
be applied to the stock.
Regardless of whether you are verifying NCI or G-Code data, you can nominate an STL
file to be used in VERICUT for the stock, instead of the block or cylinder which would
otherwise be derived from the Mastercam job setup information.

Restrictions
1. Custom tool geometry is not supported.
2. Direct 4-axis wire EDM toolpaths are not supported for NCI verification, but their G-
codes can be verified if a suitable control and machine are defined.
3. When performing roll-die toolpath verification, you will probably find it desirable to
adjust the size and shape of the stock in VERICUT.

78
 VERICUT Converters and Interfaces

Accessing and Using the Mastercam-to-VERICUT

Interface (MCAMV - Version X, X2, X3 &X4)

For complete details on installing and configuring the Mastercam-to-VERICUT Interface,

see Configuring Mastercam-to-VERICUT Interface, in the Configuring CAD/CAM to
VERICUT Interfaces section of Installing CGTech Products, located in the CGTech Help
Library.

Access
To trigger the Net-Hook while in Mastercam X, hold down the Alt key and click the C
key (referred to as Alt-C). Alternatively, you could select Settings -> Run User
Application. You will see a file selection dialog offering all the installed C-Hooks. Pick
VERICUT.dll and click on the Open button.
Another option to start MCAMV is to create an icon. You can do this as follows (You
may need Adminstrator privileges):
In Mastercam, select Settings, then Customize.
In the Customize window, select NETHook in the Customize list
Drag and drop the VERICUT icon onto the main Mastercam window
In the Toolbars list in the Customize window, double click the New toolbar entry and
rename it VERICUT
Click on the OK icon (Green check mark)
You can then position the new toolbar as desired and click on the VERICUT icon to start
MCAMV

Use
When you invoke the Net-Hook the following dialog will display:

79
VERICUT Converters and Interfaces

80
 VERICUT Converters and Interfaces

To verify NCI data, all you need to do is click the OK button. By default, the files needed
by VERICUT will be generated in the same folder as the currently accessed Mastercam
file. You can nominate a different folder in the "Working Directory" section of the
dialog. If you wish to use a single folder for all the files generated by the interface,
regardless of the location of the Mastercam files, you can define an environment variable
to specify the folder.
For example,

Environment Variable Name Variable Value

CGTECH_MCAM_FOLDER C:\Temp

If you wish to verify G-code data previously generated by one of Mastercam's post-
processors, select the "Verify G-Code" option. This will enable five additional input
fields in the dialog, for the specification of the G-code files and location of the stock on
the machine.
In Mastercam's "Operation Manager" you can select multiple operations, by clicking on
their names while holding the shift or control key down. The operations' icons will be
tagged with blue check marks. You can use this mechanism, and the C-Hook's "Selected
Operations" choice to restrict verification to a set of operations.
You can also specify a template user file (.usr) or in-process (.ip) file that the output of
the interface will be merged with in VERICUT. If you do not specify such a file, the
library copy of "init.usr" or "initm.usr" will be used, depending on the units of the
Mastercam data. If you specify a template file, you can also opt to use the tool library
which it references, instead of having the interface generate one.
If you elected to verify G-code files you can specify one or two by entering their paths
and names, or by browsing for them. The template user file or in-process file will need to
contain a machine and control definition. To assist you in placing the stock at the correct
location on the VERICUT machine, the delta X, Y and Z values can be specified and will
be applied to the stock.
Regardless of whether you are verifying NCI or G-Code data, you can nominate an STL
file to be used in VERICUT for the stock, instead of the block or cylinder which would
otherwise be derived from the Mastercam job setup information.
The data on the dialog is saved in the Mastercam part file as blanked notes on a specified
level so that when you save the part and later load it again, the values in the VERICUT
dialog will be restored. By default, this level is 3987 but you can change it by setting the
environment variable CGTECH_MCAM_NOTE_LEVEL.

81
 VERICUT Converters and Interfaces

For example,

Environment Variable Name Variable Value

CGTECH_MCAM_NOTE_LEVEL 42

Restrictions
1. Custom tool geometry is not supported.
2. Direct 4 axis wire EDM toolpaths are not supported for NCI verification, but their G-
codes can be verified if a suitable control and machine are defined.
3. When performing roll-die toolpath verification, you will probably find it desirable to
adjust the size and shape of the stock in VERICUT.

82
 VERICUT Converters and Interfaces

MCAMV VERICUT Window

83
 VERICUT Converters and Interfaces

Working Directory — Enter the /path/ to the directory where you want the VERICUT
files output, or use the “Browse” button to display a directory selection window and use
it to specify the path ( .VcProject, .tls. CGTPart.stk, CGTStock.stk)
File Name — Enter the "base" name for VERICUT files that will be created. By default
the name of the Mastercam .MCX file is used.
Project Template — Enter the /path/filename of the "template" .VcProject file that you
want loaded in the text field, or use the "Browse" button to display a file selection
window and use it to specify the /path/filename. A "template" .VcProject file is a
previously defined VERICUT project file.
Retain Setups — When toggled "On", MCAMV will append the operations in the
MasterCAM part file, to the setups that are already defined in your Project Template file,
and setups from both files will be contained in the generated project file. Otherwise, and
more typically, the imported NX part operations will be the only setups in the generated
project file.
Operations — All of the program groups shown in the Operations Manager are
available in this list. Use the list to select the operation that you want selected settings to
pertain to. When an operation is selected from the list, the Settings for Operation field is
updated so you can see at a glance which operation you are selecting settings for.
If you wish to transfer only some of the MasterCAM operations to VERICUT, choose
“Selected Operations” in the Options windows and highlight the operations you want in
this list (using the Control and Shift keys) immediately before choosing “Output Files”.
Options — Displays the MCAMV Options window enabling you to set parameters
related to the models that are passed to VERICUT and to set parameters related to
VERICUT processing.

The following features are specific to the operation specified by Settings for Operation
opname, where opname is the name of the operations that the settings apply to.
Setup Template — Enter the /path/filename of the Setup "template" file that you want
loaded in the text field, or use the "Browse" button to display a file selection window and
use it to specify the /path/filename. A setup "template" is a previously defined VERICUT
.VcProject file that containing files and settings required for VERICUT simulation.
Use Tools from the Setup Template — When toggled "On", VERICUT will use the
tool library file stored in the Setup Template rather than one created by MCAMV.
Use Views from the Setup Template — When toggled "On", VERICUT will use the
views stored in the Setup Template rather than the views created by MCAMV.
Stock STL File — Enter the /path/filename in the Stock STL File text field, or use the
"Browse" button to display a file selection window and use it to specify the
/path/filename of the STL file to be used in VERICUT for the stock, instead of the block
or cylinder which would otherwise be derived from the Mastercam job setup information.

84
 VERICUT Converters and Interfaces

Part STL File — Enter the /path/filename in the Part STL File text field, or use the
"Browse" button to display a file selection window and use it to specify the
/path/filename of the STL file to be used in VERICUT for the part.
Fixture STL File — Enter the /path/filename in the Fixture STL File text field, or use
the "Browse" button to display a file selection window and use it to specify the
/path/filename of the STL file to be used in VERICUT for the fixture.
Model Csys – Use the “Browse” button to select a Mastercam coordinate system through
which the Stock, Part and Fixture STL models will be exported. The name of the
currently selected Coordinate System will be displayed after the Model Csys label or
“None” will be displayed if there is no currently selected Coordinate System. Use the
“Clear” button to unselect a previously selected Coordinate System.
Stock Csys – Use the “Browse” button to select a Mastercam coordinate system that
describes how the Cutstock is to be oriented when transferred from one VERICUT setup
to the next. The name of the currently selected Coordinate System will be displayed after
the Model Csys label or “None” will be displayed if there is no currently selected
Coordinate System. Use the “Clear” button to unselect a previously selected Coordinate
System.
Stock Deltas — Use to position the stock at the correct location on the VERICUT
machine. Enter the offset values in the X, Y and Z text fields. The values specified will
be applied to the stock in addition to any selected Coordinate System.
Attach Component Name — Enter the name of the VERICUT attach component that is
to be used for the current operation or select from the drop down list.
VERICUT GCode Table — The four fields in the GCode Table frame are used to orient
the NC program to the part.
Table Name — Choose from None, Program Zero, Work Offsets or Base Work
Offset from the drop down list.
Register — If Work Offsets was chosen, choose the work offset register for this
setup (typically 54, 55, 56, etc.)
Program Zero From — Enter the name of the component that represents the "from"
point for determining the program zero offset or choose a component from the drop
down list. VERICUT will use the origin of the specified component. The default
"From Component" is "tool".
Program Zero To — Enter the name of a CSYS to represent the "to" point for
determining the program zero offset or choose a component from the drop down list.
VERICUT will use the origin of the specified CSYS. The default "To CSYS" is a
CSYS named "Program_Zero".
NC Program Type — Use to specify the NC program type. Select either NCI or
GCode.
NC Program File(s) — Displays a list of NC Program files that will be passed to
VERICUT.
Add — Use to add tool path files to the NC Program File(s) list.

85
 VERICUT Converters and Interfaces

Remove — Use to remove the highlighted tool path(s) from the NC Program
File(s) list.
Run VERICUT — launches VERICUT with the files created by Output Files.
Output Files — outputs all files, for all operations, including the selected models, tool
library files, updated project and setup files, and the "operations" file that assembles all of
this information into a VERICUT "project" file.
Output and Run — Use Output and Run to output the files needed by VERICUT and
then launch VERICUT in the same step.

OK — Saves values that you set in the MCAMV windows as attributes the Mastercam
part file and closes the MCAMV VERICUT window.
Apply — Saves values that you set in the MCAMV windows as attributes the Mastercam
part file and leaves the MCAMV VERICUT window open to enable you to continue.
Cancel — Closes the MCAMV VERICUT window without saving any of the settings in
the Mastercam part file.

86
 VERICUT Converters and Interfaces

MCAMV Options Window

Process — Controls the processing mode in which VERICUT is run.

Interactive — Opens the VERICUT window for access to all VERICUT functions
and capabilities. When the VERICUT window opens, all of the required VERICUT
files are loaded and ready for processing. The stock is displayed in its unprocessed
state and you need to need to press the "Play to End" icon, , in VERICUT to start
the verification process.
Batch — Runs VERICUT unattended in the background. When the VERICUT
window opens, the toolpath verification process is complete and the part is displayed
in its processed state.
NOTE: In either case, both application windows (VERICUT and Mastercam) are
available to work in at the same time.

87
 VERICUT Converters and Interfaces

Cut Mode — Controls the cut mode in which VERICUT is run (ref. Project menu >
Processing Options > Motion: Fastmill option in the VERICUT Help section, in the
CGTech Help Library for more information).
Standard — Runs VERICUT in the "Standard" cut mode where each cut made by
each tool motion is seen (full cutting animation).
FastMill — Runs VERICUT in the "FastMill" cut mode where all tool path records
are processed as quickly as possible without displaying animated cutting, and then the
final machined workpiece is displayed.
Put operations into a single VERICUT setup — If this box is checked, MCAMV will
combine all the MasterCAM operations into a single VERICUT setup. If the “Selected
Operations” box below is checked, only the operations selected in the main MCAMV
window will be used.
Operations — Use to specify the operations to process.
All Operations — Process all operations in the Operations list in the MCAMV
VERICUT window.
Selected Operations — Process only selected operations in the Operations list in the
MCAMV VERICUT window.

OK — Updates the Mastercam part file with the current settings and closes the MCAMV
Options window and returns to the MCAMV VERICUT window.
Apply — Updates the Mastercam part file with the current settings and leaves the
MCAMV Options window open for further setting changes.
Cancel — Closes the MCAMV Options window and returns to the MCAMV VERICUT
window without updating the settings in the Mastercam part file.

88
 VERICUT Converters and Interfaces

NX-to-VERICUT Interface (NXV)

89
 VERICUT Converters and Interfaces

Introduction to the NX-to-VERICUT Interface (NXV)

The NX-to-VERICUT Interface, or "NXV", is a licensed software program that provides

a fully integrated NX-to-VERICUT interface. The interface streamlines the verification
and optimization of NX-generated tool paths.
Verify individual paths, a series of selected paths, or a complete sequence of operations.
Stock, fixture, and design models are automatically transferred to VERICUT, along with
tool path and tooling information.
VERICUT runs independently from NX, so you can work in NX while verifying a tool
path.
VERICUT has the ability to display and analyze geometric models as well as simulate
cutter motion and the material removal of an NC program. It also verifies the quality and
correctness of the NC program. Programming errors or inefficient motion are visually
detected during the simulation process, which aids the NC programmer in correcting the
NC Program. Measurement tools are used at any time during the simulation process to
verify or compute the volume, distances and locations, as well as to compare various
stages of the "cut" part with other stages or with the "design" part.

Flow of information through NXV:

90
 VERICUT Converters and Interfaces

For complete details on installing and configuring the NX-to-VERICUT Interface, see
Configuring NX-to-VERICUT Interface (NXV), in the Configuring CAD/CAM to
VERICUT Interfaces section of Installing CGTech Products, located in the CGTech Help
Library.

Starting NX with NXV

The NXV command file ...<computertype>/commands/nxv/(NXx.bat, where x is the NX
version number, for windows) sets the environment for CGTech's NX-to-VERICUT
interface, then runs NX. When integrated into your normal NX start-up environment as
described under Installing the NX-to-VERICUT Interface (NXV), NXV is automatically
included when you run NX. See Installing the NX-to-VERICUT Interface (NXV) in
the Installing CGTech Products section, in the CGTech Help Library, for additional
information.
Depending on the version of NX in use, NXV is accessed differently. See "Overview of
using NXV" for details. NXV's "Run VERICUT" window is used to select the geometry
and tool path(s) used in the simulation, then run VERICUT. Options are available to run
VERICUT interactively or in batch mode (unattended in the background). When
VERICUT is run interactively, all that's left to do is press Play to End ( ) to start the
simulation.

91
 VERICUT Converters and Interfaces

Overview of Using NXV

The following overview describes how NXV is used with VERICUT and NX to simulate
the cutting action of NX-generated tool paths. Exact user actions in NX may vary,
depending on the NX version being used.

NX2, NX3, NX4, NX5 & NX6 overview

1. Prepare NX model/tool path data.

In NX, create the necessary model geometry and tool paths to simulate in VERICUT.

2. Start the NX-to-VERICUT Interface (NXV).

NX2 & NX3
A. Click Application menu > Manufacturing.
B. Click on any program group in the NX Operations Navigator to activate the
VERICUT icon.

C. Click the VERICUT icon ( ) on the NX Toolbar, or click Tools

>VERICUT (or Ctrl + Alt + V).

NX4, NX5, NX6 & NX7

A. Click Start > Manufacturing.
B. Click on any program group in the NX Operations Navigator to activate the
VERICUT icon.

C. Click the VERICUT icon ( ) on the NX Toolbar, or click Tools

>VERICUT (or Ctrl + Alt + V).

The NXV VERICUT window opens. (See window features)

3. Specify the location and base name for the VERICUT files.
A. In the Output Directory text field, enter the /path/ to the directory where you
want the VERICUT files ( .VcProject, .tls. CGTPart.stk, CGTStock.stk, etc.)
output. By default, the output directory is the "start in" directory of the session.

92
 VERICUT Converters and Interfaces

B. In the File Name text field, enter the "base" name for the VERICUT files that will
be created. By default the base name of the NX .prt file is used.
C. If desired, specify a Project Template file. Enter the /path/filename of the
"template" .VcProject file that you want loaded, in the text field, or use the
Browse button to display a file selection window and use it to specify the
/path/filename. A "template" .VcProject file is a previously defined VERICUT
project file.
D. Select the name of the program group, from the Program Group(s) list, that you
want to specify settings for. The "Settings For Program Group: program group
name" will update to confirm your selection. Any settings that you make will
apply to this program group until another program group is selected.

4. Provide NXV with information related to the model files that will be passed to
VERICUT.
A. Select Options to display the NXV Options window.
B. Specify the Output Model File Type. Choose VERICUT Model or STL.
C. Specify the Output Model File Format. Choose ASCII or Binary.
D. Specify the Output Model Tolerances. Enter the desired tolerance values in the
Part, Blank and Fixture text fields.
E. Specify the coordinate system that the model files are output relative to. Choose
Absolute or MCS/Coordinate System.
F. Specify the VERICUT program attributes.
G. Specify the Process mode in which VERICUT is to run. Choose Interactive or
Batch.
H. If NC Program Type will be set to G-Code, select the Machine Type, from the
pull-down list, that NXV is to use for creating G-Code files from the NX internal
toolpath files. This list is the same as the Available Machines list in the NX Post
Process window. This feature is used in conjunction with the Automatically
Output NC Program feature on the NXV VERICUT window.
I. Specify the Cut Mode in which VERICUT is to run. Choose Standard or
FastMill.
J. Specify the type of NC program files that are to be passed VERICUT. Choose
either CLSF or G-Code. This feature is used in conjunction with the
Automatically Output NC Program feature on the NXV VERICUT window.
K. Select OK to apply the settings and return to the VERICUT window.

93
 VERICUT Converters and Interfaces

5. If necessary, select NX geometry to transfer to VERICUT.

By default, NXV automatically creates a "stock" block enclosing the bounds of the
operation's part model. However, you can use the Geometry options to select alternate
geometry to use in the simulation.
A. NXV will automatically position the Part, Stock and Fixture models from MCS
origin of Program Group to VERICUT ATTACH component. If you wish to
output Part, Stock and Fixture models relative to a different coordinate system

(WCS), click ( Model Location ), then select the coordinate system

(WCS) representing the orientation of the of the stock on the machine in
VERICUT. You must have previously set Output Model Relative To, on the
Options window, to MCS/Coordinate System. All models will be output relative
to the selected coordinate system.

B. Click (Part), and then select geometry to represent the design model, or
theoretical finished part. (Only applicable if using AUTO-DIFF in VERICUT.)

C. Click (Stock/Blank), and then select geometry to represent the raw stock
workpiece to be machined.

D. Click (Fixture/Check), and then select geometry to represent the fixture

used to hold the stock for machining.

6. Provide VERICUT with information related to this setup.

A. If desired, enter the /path/filename of the Setup Template file that you want
loaded, in the text field, or use the Browse button to display a file selection
window and use it to specify the /path/filename. A setup "template" is a
previously defined VERICUT .VcProject file that containing files and settings
required for VERICUT simulation.
B. Toggle "On" Use Tools from the Setup Template if you want VERICUT to use
the tool library file stored in the Setup Template rather than one created by
NXV.
C. Toggle "On" Merge Tools into Setup Template Tool Library if you want
VERICUT to merge the tool library created by NXV, with the tool library file
stored in the Setup Template, and use the "merged" tool library rather than one
created by NXV.

94
 VERICUT Converters and Interfaces

D. Toggle "On" Use Views from the Setup Template if you want VERICUT to use
the views stored in the Setup Template rather than the views created by NXV.

7. Create or Select the NC program files to be simulated in VERICUT.

To create a new NC program file to add to the NC Program File(s) list, select
Automatically Output NC Program, and then Add. NXV will automatically create
a new .cls, or .ptp, file containing the operations related to the selected selected
operations.
If either the Program Group is selected, or no selection is made in the Operation
Navigator (ONT), NC code will be output for all operations. Otherwise, NC code will
be output only for the operation(s) selected.
NXV uses the settings in the Options window to determine whether a .cls file, or a
.ptp file, is created for simulation.
To add an existing NC program file(s) to the NC Program File(s) list, select Existing
NC Program, and then Add. NXV displays a standard file selection window
enabling you to select existing .cls or .ptp files.

8. Select settings for any additional program groups that you want VERICUT to
simulate.
Select another program group from the Program Group(s) list and repeat the above
steps to specify setting changes for this new setup. Continue for each program group
(setup) that you want VERICUT to simulate.

9. Output files and start VERICUT.

A. Select Output Files to output all files, for all Program Groups, including the
selected models, tool library files, updated project and setup files, and the
"operations" file that assembles all of this information into a VERICUT "project"
file.
B. Select Run VERICUT to dismiss the NXV VERICUT window and start
VERICUT.

When VERICUT is run from NX, both application windows are available to work in at
the same time.
NOTE: The values that you set in any of the NXV windows are saved as attributes in
the NX part file for each Program Name. Use Apply at any time to save your settings in
the NX part file. When you re-open the NX part file, the NXV settings are recalled as
they where when you saved the file.

95
 VERICUT Converters and Interfaces

NXV VERICUT Window

Features in this window are used to select the geometry and tool path(s) to simulate, and
then run VERICUT. In NX3-NX6 this window is opened via clicking the VERICUT icon
( ) on the NX Toolbar, Tools menu > Operation Navigator > Toolpath > VERICUT
or Tools menu > VERICUT.
NOTE: The values that you set in any of the NXV windows are saved as attributes
when you save the NX part file. When you re-open the NX part file, the NXV settings are
recalled as they where when you saved the file.

96
 VERICUT Converters and Interfaces

Sample VERICUT window:

97
 VERICUT Converters and Interfaces

File Name — Enter the "base" name for VERICUT files that will be created. By default
the base name of the NX .prt file is used.

Output Directory — Enter the /path/ to the directory where you want the VERICUT
files output ( .usr, .tls. CGTPart.stk, CGTStock.stk)

Project Template — Enter the /path/filename of the "template" .VcProject file that you
want loaded in the text field, or use the "Browse" button to display a file selection
window and use it to specify the /path/filename. A "template" .VcProject file is a
previously defined VERICUT project file.

Retain Setups in Project Template — When toggled "On", NXV will append the
operations in the NX part file, to the setups that are already defined in your Project
Template file, and setups from both files will be contained in the generated project file.
Otherwise, and more typically, the imported NX part operations will be the only setups in
the generated project file.

Active Program Group(s) — All of the program groups shown in the Operations
Navigator are available in this list. Use the list to select the program group that you want
selected settings to pertain to. When a program group is selected from the list, the
Settings for Program Group field is updated so you can see at a glance which program
group you are selecting settings for.

Remove/Restore and Switch Buttons — If there are some program groups that you do
not wish to transfer to VERICUT, select them on the Active Program Group(s) list and
use the Remove button to move them to the Deleted Program Group(s) list. Click the
Switch button to switch between displaying the Active Program Group(s) list and the
Deleted Program Group(s) list. To restore previously deleted program groups to the
Active Program Group(s) list, select them in the Deleted Program Group(s) list and
click the Restore button.

Options — Displays the NXV Options window enabling you to set parameters related to
the models that are passed to VERICUT and to set parameters related to VERICUT
processing.

Geometry — By default, NXV automatically selects models associated with your NC

operations. However, the following options can be used to select alternate geometry to
use in the simulation:

(Part) — Click this option to select geometry to represent the design

model, or theoretical finished part. Design models are used by VERICUT's
AUTO-DIFF function to detect gouges and excess material conditions. Geometry
for use as a "Design Surface" model does not have to be solid or watertight.

98
 VERICUT Converters and Interfaces

(Stock/Blank) — Click this option to select geometry to represent the raw

stock workpiece to be machined.

(Fixture/Check) — Click this option to select geometry to represent the

fixture used to hold the stock for machining.

About selecting geometry:

In general, click the desired Geometry icon, then click Select and select the
corresponding NX geometry. A window also display containing standard NX "Class
Selection" tools to assist you in selecting geometry. Geometry items can be selected in
any order, for example: stock-fixture-part, fixture-stock-part, etc. NX highlights selected
geometry. Selections for each of the geometry options can be re-selected or cleared by
selecting the corresponding geometry option, then clicking Reselect or Remove,
respectively. Reselect and Remove are only available when geometry was previously
selected.

NOTES:
A. Non-solid models composed of surfaces, faces, etc. must form a watertight skin to
be useful as solid models in VERICUT. If gaps or overlaps exist in NX geometry,
the resulting solid may have holes, or portions (possible all) of the model may
fail.

B. If a stock blank is not defined or selected via the Stock/Blank option, then
VERICUT automatically creates a stock block based on the bounds of the Part in
NX.

C. For Multiple Setup Cut Stock Transition, the NXV Interface automatically creates
the necessary ***STOCK*** csys in each Setup required to transition the Cut
Stock from Setup to Setup. No need to select a "Stock Coordinate System" as the
NXV always uses the Absolute CSYS.

(Model Location) — Click this option to select a coordinate system representing

the orientation of the stock on the machine. You can either enter the name of the
appropriate coordinate system in the window that displays or select the coordinate system
in the NX graphics area.

NOTE: When selecting a coordinate system from the NX session, an MCS cannot
currently be selected.

Also see Attach Component Name in the NX Options window section, also in Converters
and CAD/CAM Interfaces.

99
 VERICUT Converters and Interfaces

Pick Lines and Circles for SOR Profile — When toggled "On", enables you to select
connected lines and circles in NX which will be transferred into VERICUT as a Solid of
Revolution (SOR). The lines and circles must lie in the XY plane of the TURN_ORIENT
csys. They will be rotated around the Y axis of the TURN_ORIENT csys to create a
Solid of Revolution (SOR).

Setup Template — Enter the /path/filename of the Setup "template" file that you want
loaded in the text field, or use the "Browse" button to display a file selection window and
use it to specify the /path/filename. A setup "template" is a previously defined VERICUT
.VcProject file that containing files and settings required for VERICUT simulation.

Use Views from the Setup Template — When toggled "On", VERICUT will use the
views stored in the Setup Template rather than the views created by NXV.

Select one of the following options from the pull-down list:

Generate Tools from NX information — Choose this option to have NXV create a
tool library using the tool data in NX.

Use Selected Tool Library — Choose this option to specify a specific tool library to
use. Enter the \path\filename of the tool library file in the text field or use the Browse
button to display a file selection window and use it to specify the \path\filename of
the tool library file.

Use Tools from the Setup Template — Choose this option to use the tool library file
stored in the Setup Template instead of one created by NXV.

Merge Tools into Setup Template Tool Library — Choose this option to merge the
tool library created by NXV, with the tool library file stored in the Setup Template,
and use the "merged" tool library rather than one created by NXV.

Automatically Output NC Program — Use this feature to create new .cls or .ptp files
from the selected NX operations. If either the Program Group is selected, or no selection
is made in the Operation Navigator (ONT), NC code will be output for all operations.
Otherwise, NC code will be output only for the operation(s) selected.
NOTE: The Add button needs to be pressed to output the NC program(s).
Select Existing NC Program — Use this feature to select existing .cls or .ptp files.

NC Program File(s) — Displays a list of NC Program files that will be passed to

VERICUT.

Add — Use to add NC program files to the NC Program File(s) list.

When Select Existing NC Program is selected, NXV displays a standard file selection
window enabling you to select existing files.

100
 VERICUT Converters and Interfaces

When Automatically Output NC Program is selected, the configured NC code is

output and added to the list.

Remove — Use to remove the highlighted NC sub program file(s) from the NC Sub
Program File(s) list.

NC Sub Program File(s) — Displays a list of NC Sub Program (subroutine) files that
will be passed to VERICUT.

Add — Use to add an existing NC sub program (subroutine) file to the NC Sub Program
File(s) list. Selecting Add will display a file selection window enabling you to specify the
NC Sub Program file to be added to the NC Sub Program File(s) list.

Remove — Use to remove the highlighted NC sub program file(s) from the NC Sub
Program File(s) list.

Run VERICUT — launches VERICUT with the files created by Output Files.

Output Files — outputs all files, for all Program Groups, including the selected
models, tool library files, updated project and setup files, and the "operations" file that
assembles all of this information into a VERICUT "project" file.
Output and Run — Use Output and Run to output the files needed by VERICUT and
then launch VERICUT in the same step.

OK — Saves values that you set in the NXV windows as attributes the NX part file and
closes the NXV VERICUT window.

Apply — Saves values that you set in the NXV windows as attributes the NX part file
and leaves the NXV VERICUT window open to enable you to continue.

Cancel — Closes the NXV VERICUT window without saving any of the settings in the
NX part file.

101
 VERICUT Converters and Interfaces

NXV Options Window

Use the features of the NXV Options window to pass information specific to the model
files (Part, Blank, and Fixture) to VERICUT.
NOTE: The values that you set in any of the NXV windows are saved as attributes
when you save the NX part file. When you re-open the NX part file, the NXV settings are
recalled as they where when you saved the file.

102
 VERICUT Converters and Interfaces

Output Model File Type — Use to specify the type of model files that are being passed
to VERICUT. Choose either VERICUT Model (VERICUT polygon file) or STL
(Stereolithography model file).

Output Model File Format — Use to specify the file format of the model files. Choose
either ASCII or Binary.

NOTE: "Binary" VERICUT polygon files are platform specific.

Model Output Tolerance — Use to specify tolerance values for Part, Blank and
Fixture models.

Transfer All Coordinate Systems — When toggled "on" (checked), NXV transfers all
NX coordinate systems to VERICUT.

Output Model Relative To — Use to specify the coordinate system that model files are
output relative to. Choose either Absolute or MCS/Coordinate System.

Absolute — This choice is typically used for CLSF files because the CL file MSYS
record takes care of tool point location transformation. If Absolute is selected, the
following is output in the setup file for this program group:

Models are output relative to absolute.

VERICUT Process Matrix is turned-on.
VERICUT CSYS's are created for each MCS in each Program Group, attached to
the stock component.

MCS/Coordinate System — The MCS/Coordinate System choice outputs the

models relative to the MCS of the first operation in the program group, or relative to
the selected coordinate system (new), if one exists. This choice is typically used for
G-Code processing since there is no MSYS equivalent in the G-Code data. It is
sometimes used by CLSF users when they only have one setup, and want the models
located relative to the MCS, rather than absolute. If MCS/Coordinate System is
selected, the following is output in the setup file for this program group:

Models are output relative to the selected Program Group's MCS, or …

Models are output relative to the selected coordinate system.
VERICUT Process Matrix is turned-off
VERICUT CSYS's are created for each MCS in each Program Group, attached to
the stock component.

MCS/Coordinate System output is sometimes used for a single-position CLSF where

the user wants the models in the same coordinates as the MCS.

103
 VERICUT Converters and Interfaces

Process — Controls the processing mode in which VERICUT is run.

Interactive — Opens the VERICUT window for access to all VERICUT functions
and capabilities. When the VERICUT window opens, all of the required VERICUT
files are loaded and ready for processing. The stock is displayed in its unprocessed
state and you need to press the "Play to End" icon, , in VERICUT to start the
verification process.

Batch — Runs VERICUT unattended in the background. When the VERICUT

window opens, the toolpath verification process is complete and the part is displayed
in its processed state.

NOTE: In either case, both application windows (VERICUT and NX) are available to
work in at the same time.

Machine Type — Enables you to select the machine type that NXV is to use for creating
G-Code files from the NX internal toolpath files.

NC Program Type — Use to specify the type of NC program files that are to be passed
VERICUT. Choose either CLSF or G-Code. This feature is used in conjunction with the
Create for selected operations feature on the NXV VERICUT window.

Assembly Arrangement List — The Assembly Arrangement List feature displays a list
of all NX Assembly Arrangements available in the current part file. Select the desired
Assembly Arrangement from the pull-down list. If no Assembly Arrangements exist in
the current NX part file, the pull-down list displays "None".

Output Tools By — Use to specify whether to output tool by the NX Object Name
(Default) or by Tool Number. Choose NX Object Name if you want the tool to have the
NX object name as the Tool ID in VERICUT. Choose Tool Number if you want the tool
to have the NX tool number as the Tool ID in VERICUT.

Translate Holder As Library Reference — When toggled "on" (checked), NXV

enables "referenced" tool holders to be passed to VERICUT. To use the option you need
to set the UGII_CAM_LIBRARY_TOOL_GRAPHICS_PATH environment variable to
point to the location where the "referenced" tool files are stored.
Translate Holder As — Enables you to specify whether to transfer an NX holder
definition as individual SORs for each step or as a single SOR representing the complete
holder.
Steps — Each Step in the NX holder defintion is tranferred as a separate SOR.
Single SOR — The NX holder defintion is tranferred as a single SOR.

Attach Component Name — Enter the name of the VERICUT attach component that is
to be used for the current program group or select it from the Attach Component List
pull-down list.

104
 VERICUT Converters and Interfaces

Also see Model Location in the NX VERICUT window section, also in Converters and
CAD/CAM Interfaces.

Table Name — Enter the G-Code table name or select it from the Table List pull-down
list.

Register Number— If Work Offsets was selected as the Table Name, enter the work
offset register, for example 54, 55, 56, etc.

'From' Component — Enter the name of the component that represents the "from" point
for determining the program zero offset or select it from the 'From' List pull-down list.
VERICUT will use the origin of the specified component. The default "From
Component" is "tool".

'To' Csys — Enter the name of a CSYS to represent the "to" point for determining the
program zero offset in the text field or select the CSYS name from the 'To' List pull-
down list.

VERICUT will use the origin of the specified CSYS. The default "To Csys" is a CSYS
named "Program_Zero".

OK — Updates the NX part file with the current settings and closes the NXV Options
window and returns to the NXV VERICUT window.

Apply — Updates the NX part file with the current settings and leaves the NXV Options
window open for further setting changes.

Cancel — Closes the NXV Options window and returns to the NXV VERICUT window
discarding any changes made.

105
 VERICUT Converters and Interfaces

The nxv_xxx_user.prefs File

The following describes the information stored in the nxv_xxx_user.prefs file (where xxx
represents the NX version).

CGTFileType
Corresponds to the Output Model File Type feature on the NXV Options window.
Format: CGTFileType,value
0 = VERICUT Model
1 = STL

CGTFileFormat
Corresponds to the Output Model File Format feature on the NXV Options window.
Format: CGTFileFormat,value
0 = ASCII
1 = Binary

CGTOutputAllCsys
Corresponds to the Transfer All Coordinate Systems feature on the NXV Options
window.
Format: CGTOutputAllCsys,value
0 = Transfer only required coordinate systems
1 = Transfer all coordinate systems

CGTFileCoordinate
Corresponds to the Output Model Relative to feature on the NXV Options window.
Format: CGTFileCoordinate,value
0 = Absolute
1 = MCS/Coordinate System

106
 VERICUT Converters and Interfaces

CGTProcessMode
Corresponds to the Process feature on the NXV Options window.
Format: CGTProcessMode,value
0 = Interactive
1 = Batch

CGTProcessCutMode
Corresponds to the Cut Mode feature on the NXV Options window.
Format: CGTProcessCutMode,value
0 = Standard
1 = Fastmill

CGTProcessToolpathType
Corresponds to the NC Program Type feature on the NXV Options window.
Format: CGTProcessToolpathType,value
0 = CLSF
1 = G-Code

CGTProcessMachineType
Corresponds to the Machine Type feature on the NXV Options window.
The posts that appear in the list come directly from NX, therefore the exact values will be
different from one NX installation to the next.
Format: CGTProcessMachineType,value
0 = 1st post in the list
1 = 2nd post in the list
2 = 3rd post in the list, and so on.

CGTFilePartTol
Corresponds to the Model Output Tolerance: Part feature on the NXV Options window.
Format: CGTFilePartTol,tolerance value

107
 VERICUT Converters and Interfaces

CGTFileBlankTol
Corresponds to the Model Output Tolerance: Blank feature on the NXV Options
window.
Format: CGTFileBlankTol,tolerance value

CGTFileFixtureTol
Corresponds to the Model Output Tolerance: Fixture feature on the NXV Options
window.
Format: CGTFileFixtureTol,tolerance value

CGTAttachName
Corresponds to the Attach Component Name feature on the NXV Options window.
Format: CGTAttachName,component name

CGTTableName
Corresponds to the Table Name feature on the NXV Options window.
Format: CGTTableName,table name

CGTRegisterNumber
Corresponds to the Register Number feature on the NXV Options window.
Format: CGTRegisterNumber, register number

CGTProgramZeroFrom
Corresponds to the Program Zero From Component feature on the NXV Options
window.
Format: CGTProgramZeroFrom,component

108
 VERICUT Converters and Interfaces

CGTProgramZeroTo
Corresponds to the Program Zero to CSYS feature on the NXV Options window.
Format: CGTProgramZeroTo,csys name

CGTUseTlsTemplate
Corresponds to the Use Tools from Setup Template feature on NXV VERICUT
window.
Format: CGTUseTlsTemplate,value
0 = OFF
1 = ON

CGTMergeTlsTemplate
Corresponds to the Merge Tools from Setup Template feature on the NXV VERICUT
window.
Format: CGTMergeTlsTemplate,value
0 = OFF
1 = ON

CGTGLobalProjectFile
Corresponds to the Project Template feature on the NXV VERICUT window.
Format: CGTGLobalProjectFile,/path/filename

CGTOutputDir
Corresponds to the Output Directory feature on the NXV VERICUT window.
Format: CGTOutputDir,/path/filename

CGTProjectFile
Corresponds to the Setup Template feature on the NXV VERICUT window.
Format: CGTProjectFile,/path/filename

109
 VERICUT Converters and Interfaces

CGTNcProgramMode
Corresponds to the Automatically Output NC Program and Select Existing NC
Program features on the NXV VERICUT window.
Format: CGTNcProgramMode,value
0 = Automatically Output NC Program
1= Select Existing NC Program

CGTNcProgramExt1
This is the file extension that appears in the Files of type filter in the Enter Toolpath
filename window (NXV VERICUT window > Add) when the NC Program Type feature
on the NXV Options window is set to CLSF (CGTProcessToolpathType,0).
Format: CGTNcProgramExt1,extension (for example .cls)

CGTNcProgramExt2
This is the file extension that appears in the Files of type filter in the Enter Toolpath
filename window (NXV VERICUT window > Add) when the NC Program Type feature
on the NXV Options window is set to G-Code (CGTProcessToolpathType,1).
Format: CGTNcProgramExt2,extension (for example .ptp)

CGTNcSubProgramExt
This is the file extension that appears in the Files of type filter in the Enter Sub Program
filename window (NXV VERICUT window > Add)
Format: CGTNcSubProgramExt,extension (for example .ptp)

CGTAppendSetups
Corresponds to the Retain Setups in Project Template feature on NXV VERICUT
window.
Format: CGTAppendSetups,value
0 = OFF
1 = ON

110
 VERICUT Converters and Interfaces

CGTUseViews
Corresponds to the Use Views from Setup Template feature on the NXV VERICUT
window.
Format: CGTUseViews,value
0 = OFF
1 = ON

CGTSorProfile
Corresponds to the Pick Lines and Circles for SOR Profile feature on the NXV
VERICUT window.
Format: CGTSorProfile,value
0 = OFF
1 = ON

111
 VERICUT Converters and Interfaces

Pro/E-to-VERICUT Interface (PROEV)

112
 VERICUT Converters and Interfaces

Introduction to the Pro/E-to-VERICUT Interface

(PROEV)

The Pro/E-to-VERICUT Interface, or "PROEV", is a licensed software program that

provides a fully integrated Pro/E-to-VERICUT Interface. The interface streamlines the
verification and optimization of Pro/E-generated NC programs.
Stock, fixture, and design models are automatically transferred to VERICUT, along with
NC program and tooling information.
VERICUT runs independently from Pro/E, so you can work in Pro/E while verifying an
NC program in VERICUT.
VERICUT has the ability to display and analyze geometric models as well as simulate
cutter motion and the material removal of an NC program. It also verifies the quality and
correctness of the NC program. Programming errors or inefficient motions are visually
detected during the simulation process, which aids the NC programmer in correcting the
NC program. Measurement tools can be used at any time during the simulation process to
verify or compute the volume, distances and locations, as well as to compare various
stages of the "cut" part with other stages or with the "design" part.

Flow of information through PROEV:

113
 VERICUT Converters and Interfaces

The machine file, specified in the template file, is used to extract all components on the
machine. The machine file is opened as it is defined in the template file. If it is not found,
then the machine file is searched for in the same directory as the template file. If it does
not exist in the same directory as the template file, then the machine file is searched for in
the directories specified by the CGTECH_LIBRARY environment variable.
The "PROEV" data is stored in the Pro/E model via External Data. There are three
classes dedicated for storing "PROEV" External Data. They are "proev_version,"
"proev_project" and "proev_setup".

For complete details on installing and configuring the Pro/E-to-VERICUT Interface, see
Configuring the Pro/E-to-VERICUT Interface (PROEV), in the Configuring
CAD/CAM to VERICUT Interfaces section of Installing CGTech Products, located in the
CGTech Help Library.

Accessing the Pro/E-to-VERICUT Interface

To start the Pro/E-to-VERICUT Interface from within Pro/ENGINEER, click on
Applications in the Pro/ENGINEERING main menu, then select VERICUT from the
pull-down list as shown in the picture below. Holding the cursor over the VERICUT
option will display the tip shown in the yellow text box below.

114
 VERICUT Converters and Interfaces

If errors occur, visit the VERICUT Users' Forum or contact CGTech technical support
via our website, just click on the support link.
You should now be ready to start using the Pro/E-to-VERICUT Interface. See "Overview
of using PROEV" for details.

NOTE: Make sure that you do not delete the proe.text file, or the protk.dat file (if it is
located in the "Start in" directory), when deleting Pro/ENGINEER "trail.txt" files from
the "Start in" directory. Deleting these files will result in the ProENGINEER-to-
VERICUT Interface to stop working.

115
 VERICUT Converters and Interfaces

Overview of Using PROEV

The following overview describes how "PROEV" is used with Pro/ENGINEER and
VERICUT to simulate the cutting action of Pro/ENGINEER generated NC programs.
The following user actions are based on using Pro/ENGINEER Wildfire 4.0.

1. Prepare Pro/E model/tool path data.

In Pro/ENGINEER, create the necessary model geometry and NC programs to
simulate in VERICUT.

2. Start the Pro/E-to-VERICUT Interface.

A. In the Pro/ENGINEER main menu bar, click File > Open.
B. Browse and select a Pro/ENGINEER manufacturing part file (*.mfg).
C. In the Pro/ENGINEER main menu bar, click Applications > VERICUT to
launch the Pro/E-to-VERICUT Interface. The "VERICUT Interface" dashboard
panel should now display as shown below.

D. Click to close the VERICUT dashboard.

3. Specify the location and base name for the VERICUT files.
Click on the VERICUT Interface dashboard's File tab to open the File panel shown
below.

116
 VERICUT Converters and Interfaces

A. In the File panel, enter the /path/ to the directory where you want the VERICUT
files output (.VcTemp, .tls, .ops, .ncl, .ply, .stl) in the Output Directory text
field, or use the Browse button to display a file selection window and use it to
specify the /path/.
B. In the File Name text field, enter the "base" name for the VERICUT files that will
be created.
C. If desired, specify a Project Template file. Enter the /path/filename of the
"template".VcProject file that you want loaded in the Project Template text field,
or use the Browse button to display a file selection window and use it to specify
the /path/filename.
A "template".VcProject file is a previously defined VERICUT project file.
D. If you wish to append the part operations to the setups that are already defined in
your project template, you can click on the Append to existing setups in project
template check-box located under the Project Template text field so that the
check is displayed. Otherwise, and more typically, the imported part operations
will be the only setups in the generated project.

4. Select the current operation from the Operations List

Click on the VERICUT Interface dashboard's Operations tab to open the Operations
panel as shown below.

A. In the Operations list, select the operation that you want the subsequent settings
to apply to. Use the Remove button to remove an operation from the list, or the

117
 VERICUT Converters and Interfaces

Search button to populate the list with all of the operations contained in the Pro/E
manufacturing model.
B. If desired, specify a Setup Template file. Enter the /path/filename of the
"template" .VcProject file that you want loaded in the Setup Template text field,
or use the "Browse" button to display a file selection window and use it to specify
the /path/filename. A setup "template" is a previously defined VERICUT
.VcProject file that containing files and settings required for VERICUT
simulation.

5. Select the Stock Model

Click on the VERICUT Interface dashboard's Stock tab to open the Stock panel
enabling you to select the stock model(s) for the current operation.

Select the attach component for stock models from the Attach Component pull-
down list. Use the Pick button to graphically pick the models using the mouse. Use
the Remove button to remove models from the list. Use the Search button to
populate the list with Fixture models contained in the manufacturing model.
See the Stock Panel section below for additional information. Also see the Models
section below for additional information about PROEV models.

6. Select the Fixture Models

Click on the VERICUT Interface dashboard's Fixture tab to open the Fixture panel
enabling you to select the fixture models. The Fixture panel is shown below.

118
 VERICUT Converters and Interfaces

Select the attach component for fixture models from the Attach Component pull-
down list. Use the Pick button to graphically pick the models using the mouse. Use
the Remove button to remove models from the list. Use the Search button to
populate the list with Fixture models contained in the manufacturing model.
See the Fixture Panel section below for additional information. Also see the Models
section below for additional information about PROEV models.

7. Select the Design Model

Click on the VERICUT Interface dashboard's Design tab to open the Design panel
enabling you to select the design models. The Design panel is shown below.

Select the attach component for design models from the Attach Component pull-
down list. Use the Pick button to graphically pick the models using the mouse. Use
the Remove button to remove models from the list. Use the Search button to
populate the list with Design models contained in the manufacturing model.
See the Design Panel section below for additional information. Also see the Models
section below for additional information about PROEV models.

119
 VERICUT Converters and Interfaces

8. Specify options required to simulate the current operation

Click on the VERICUT Interface dashboard's Options tab to open the Options panel
enabling you to specify options required by VERICUT to simulate the current
operation.

A. Associate a Pro/E coordinate system for each attach component.

B. Specify the type of tool ID.
Use the Use Tool ID feature to specify how you want to identify tools. When
toggled on (checked), the Tool ID is used directly. When toggled off (not
checked), a Tool List is used. See the Options Panel section below for
additional information.
C. Specify subsystem ID for head 1.
D. Specify subsystem ID for head 2.
E. Specify the Tool Library.
If you want to use an existing Tool Library instead of generating a new one,
enter the /path/filename of the existing Tool Library file in the Tool Library

120
 VERICUT Converters and Interfaces

Override text field, or use the Browse button to display a file selection
window and use it to specify the /path/filename.
If the Tool Library Override text field is left blank, then a new tool library is
generated.

F. Specify the NC program type by select either APT or G-Code.

G. Select the NC program file(s) to be simulated in VERICUT.
Enter /path/filename of the NC program file in the NC Program text field or
use the Browse button to display a file selection window and use it to specify
the /path/filename.
H. Specify any NC Subroutine Files used by the current operation.
If you have G-Code NC programs that reference subroutines, use the Add
button to display a file selection window and use it to select existing
subroutine files to be added to the NC Subroutine Files list. Use the Delete
button to remove subroutine files from the NC Subroutine Files list.
I. Create one, or more, coordinate sytems.
Specify a coordinate system name in the Name text field.
Select an attach component from the Attach Component pull-down list.
Select an attach axis system from the Attach Axis System pull-down list.
Select the NC Program Origin from the NC Program Origin pull-down list.
Repeat the above steps for each coordinate system tha you want to create.
Use the Add button to add the csys to the list. Use the Delete button to
remove the csys from the list. Use the Modify button to modify an existing
csys.

J. Specify Machine Settings.

Specify the Table Name, the Register Number, the From component/csys
and the To component/csys.
See the Options Panel section below for additional information.

9. Click on the VERICUT Interface dashboard's Settings tab to open the Settings panel
enabling you to specify settings related to the Output Model File.

121
 VERICUT Converters and Interfaces

A. Select Output Model File Type, choose VERICUT Model or STL.

B. Select Output Model File Format, choose ASCII or Binary.
C. Specify Output Model Tolerances for stock, fixture and design.

10. Process the VERICUT Simulation.

Click on the VERICUT Interface dashboard's Process tab to open the Process panel
enabling you to generate the VERICUT files and start the VERICUT session.

A. Select the VERICUT mode of operation.

If you choose to run the embedded version of VERICUT, click on the Use
Embedded VERICUT check box so that the check is displayed. The
environment variable, VERICUT_FEATURE_NAME, must also be set to
EMBEDDED.
B. Generate Files and Run VERICUT.
Once you have provided PROEV with all the information it needs, you can
perform the transfer of data to, and start VERICUT.
a. Click on the Generate Files button to output all files, for the Pro/ENGINEER
manufacturing model, including project file, tool library file, NC program file,
model files and the "operations" file that assembles all of this information into
a VERICUT "project" file without starting VERICUT.

122
 VERICUT Converters and Interfaces

b. Once you have all the files needed, you can start up VERICUT with the Run
VERICUT button.
c. You can perform both of the above steps at once by clicking on the Generate
and Run button.

11. Close the Pro/E-to-VERICUT Interface.

Click on the in the VERICUT Interface dashboard to terminate the Pro/E-to-

VERICUT Interface program and close the VERICUT Interface dashboard.

NOTE: The values that you set in any of the PROEV windows are saved as external
data in the Pro/ENGINEER manufacturing model. When you re-open the
Pro/ENGINEER manufacturing model, the PROEV window settings are recalled just as
they where when you saved the file.

123
 VERICUT Converters and Interfaces

VERICUT Interface Dashboard

Features on VERICUT Interface dashboard are used to select, or generate, NC programs

and set options for VERICUT simulation, and then run VERICUT.
In Pro/E Wildfire 4.0, the VERICUT Interface dashboard is opened by clicking on
VERICUT in the Applications menu found on the main menu bar.
NOTE: The values that you set in any of the PROEV windows are saved as external
data in the Pro/ENGINEER manufacturing model. When you re-open the
Pro/ENGINEER manufacturing model, the PROEV window settings are recalled as they
where when you saved the file.

Click on the in the VERICUT Interface dashboard to terminate the Pro/E-to-

VERICUT Interface program and close the VERICUT Interface dashboard.

File tab — Opens the File panel enabling you to information related to the VERICUT
files to be created (output directory, file name, template file, etc.).
Operations tab — Opens the Operations panel enabling you to specify the operation that
you want the subsequent settings to apply to.
Stock tab — Opens the Stock panel enabling you to specify a stock model for the current
operation.
Fixture tab — Opens the Fixture panel enabling you to specify Fixture model(s) for the
current operation.
Design tab — Opens the Design panel specify a Design model for the current operation.
Options tab — Opens the Options panel enabling you to specify options (tool library,
NC programs, machine settings, etc.) required for VERICUT to simulate the current
operation.
Settings tab — Opens the Settings panel enabling you to specify file type, file format
and tolerances for the model files output to VERICUT.
Process tab —Opens the Process panel enabling you to generate the VERICUT files and
start the VERICUT session.

124
 VERICUT Converters and Interfaces

File Panel
The features on the File panel enable you to specify information related to the VERICUT
files to be created (output directory, file name, template file, etc.).

Output Directory — Enter the /path/ to the directory where you want the VERICUT
files output (.VcTemp, .tls, .ops, .ncf, .ply, .stl) in the Output Directory text field, or use
the Browse button to display a file selection window and use it to specify the /path/.
File Name — Enter the "base" name for VERICUT files that will be created.
Project Template — Enter the /path/filename of the "template" .VcProject file that you
want loaded in the Project Template text field, or use the Browse button to display a file
selection window and use it to specify the /path/filename.
A "template" .VcProject file is a previously defined VERICUT project file.Append to
existing setups in project template — When toggled "on", PROEV will append the
operations in the Pro/ENGINEER manufacturing file, to the setups that are already
defined in your Project Template file, and setups from both files will be contained in the
generated project file.
Otherwise, and more typically, the imported Pro/E manufacturing file will be the only
contain the setups in the generated project file.

125
 VERICUT Converters and Interfaces

Operations Panel
The features on the Operations panel enable you to specify the operation that you want
the subsequent settings to apply to.

Operations List — The Operations list displays all operations in the Pro/ENGINEER
manufacturing model. The currently highlighted operation is the active operation to
which all settings will apply.
Remove — Use to remove the highlighted operation from the Operations list.
Search — Use the Search button to populate the Operations list with all operations
contained in the Pro/ENGINEER manufacturing model.
Setup Template — Enter the /path/filename of the "template" .VcProject file that
you want loaded in the Setup Template text field, or use the "Browse" button to
display a file selection window and use it to specify the /path/filename. A setup
"template" is a previously defined VERICUT .VcProject file that containing files and
settings required for VERICUT simulation.

126
 VERICUT Converters and Interfaces

Models
Stock, fixture and design models are defined uniquely by their name and internal feature
ID. For each operation, only one stock, fixture and design component exist. Each
component can have multiple models.

The fixture component is attached to the currently specified component in the "Attach
Component" list defined in the interface. If there are no components in "Attach
Component" list, then the fixture is attached to the component called "Attach".

The stock component is attached to the fixture component. If no fixture component is

defined, then the stock component is attached to the currently specified component in the
"Attach Component" list defined in the interface. If there are no components in "Attach
Component" list, then the stock is attached to the component called "Attach".

The design component is attached to the stock component. If no stock component is

defined, then the design component is attached to the fixture component. If no fixture
component is defined, then the design component is attached to the currently specified
component in the "Attach Component" list defined in the interface. If there are no
components in "Attach Component" list, then the design is attached to the component
called "Attach".
The Stock, Fixture and Design panels, described below, are used to specify models.

127
 VERICUT Converters and Interfaces

Stock Panel
The features on the Stock panel enable you to specify a Stock model for the current
operation.

Attach Component — By default, if multiple Attach Components exist, the first one in
the tree will always be displayed when this panel is opened. Select the attach component
to be used for the stock models from the pull-down list. If multiple Attach Components
exist, models can be picked and/or removed for each one.
Stock Model List — List of all models associated with the stock.
Pick — Use the Pick button to enable picking part and/or assembly models in either the
Pro/E main window or in the Pro/E Navigation Area.
Remove — Use to remove the currently selected (highlighted) model from the list.
Search — Use to search the manufacturing model for the default stock models and add
them to the list.

128
 VERICUT Converters and Interfaces

Fixture Panel
The features on the Fixture panel enable you to specify Fixture model(s) for the current
operation.

Attach Component — By default, if multiple Attach Components exist, the first one in
the tree will always be displayed when this panel is opened. Select the attach component
to be used for the fixture models from the pull-down list. If multiple Attach Components
exist, models can be picked and/or removed for each one.
Fixture Model List — List of all models associated with the fixture.
Pick — Use the Pick button to enable picking part and/or assembly models in either the
Pro/E main window or in the Pro/E Navigation Area.
Remove — Use to remove the currently selected (highlighted) model from the list.
Search — Use to search the manufacturing model for the default fixture models and add
them to the list.

129
 VERICUT Converters and Interfaces

Design Panel
The features on the Design panel enable you to specify a Design model for the current
operation.

Attach Component — By default, if multiple Attach Components exist, the first one in
the tree will always be displayed when this panel is opened. Select the attach component
to be used for the design models from the pull-down list. If multiple Attach Components
exist, models can be picked and/or removed for each one.
Design Model List — List of all models associated with the design.
Pick — Use the Pick button to enable picking part and/or assembly models in either the
Pro/E main window or in the Pro/E Navigation Area.
Remove — Use the Remove button to remove highlighted models from the list.
Search — Use to search the manufacturing model for the default design models and add
them to the list.

130
 VERICUT Converters and Interfaces

Options Panel
The features on the Options panel enable you to specify options (tool library, NC
programs, machine settings, etc.) required to simulate the current operation.

Attachments
Attach Component — Select the attach component from the pulldown list..
Attach CYS — Select the Pro/E CSYS to be associated with the Attach Component
from the pull-down list.

Tooling
Use Tool ID — Use the Use Tool ID feature to specify how you want to identify
tools. When toggled on (checked), the Tool ID is used directly. When toggled off (not
checked), a Tool List is used.

131
 VERICUT Converters and Interfaces

Notes about Tools and Holders

Tools
In Pro/E, tools can be defined as a parametric tool, a sketch tool, or a solid tool.
Since, VERICUT needs to create solids of revolution for its tools, PROEV only
processes the parametric parameters, or the sketch profiles, of any given Pro/E
tool. The Pro/E solid, representing the tool, is not used.
In PROEV, PRO/E tools can be referenced directly via the "Tool ID" (name) or
indirectly by "pocket number" (Tool Position) via a Tool Change List. For each
setup (operation), PROEV creates a Tool Change List which maps the "pocket
number" to the "Tool ID". In order to support dual head machines, the "pocket
number" is prefixed with "head1" or "head2" when the "Tool Change List" is
created. PROEV builds the tool list using "head1" as the default subsystem name.
If there are two heads, then the tool list will use "head2" for the second subsystem
name.
If the "Use Tool ID" feature is toggled on (checked), then VERICUT will use the
Tool ID directly. If the "Use Tool ID" feature is toggled off (not checked), then
VERICUT will use The Tool Change List to identify tools.

Holders
In Pro/E, holders can be defined as a parametric holder or a 3D solid holder. For
solid holders, it is mandatory to create a local coordinate system, called
"ATTACH", at the location of where the tool connects to the holder. Also, the
working directory must be set to the directory in which the 3D holders reside.

Head 1 Subsystem ID — Select the subsystem ID for head 1 from the pull-down list.
Head 2 Subsystem ID — Select the subsystem ID for head 2 from the pull-down list.
Tool Library Override — If an existing Tool Library is specified in the Tool
Library Override text field, then it is used instead of generating a new tool library.
Enter the /path/filename of an existing Tool Library file in the Tool Library
Override text field, or use the Browse button to display a file selection window and
use it to specify the /path/filename.
If the tool library override field is left blank, then a new tool library file is generated.

NC Programs
APT — Select to indicate that an APT NC program is to be simulated.
G-Code — Select to indicate that a G-Code NC program is to be simulated.
Add — Use the Add button to display a file selection window and use it to select NC
program files to be added to the NC NC Programs list.

132
 VERICUT Converters and Interfaces

Delete — Use the Delete button to delete an NC Program from the list.

NC Subroutine Files — If you have G-Code NC programs that reference subroutines,

use the NC Subroutine Files list to indicate the NC subroutine files used in the
operation.
Add — Use the Add button to display a file selection window and use it to select
existing NC subroutine files to be added to the NC Subroutine Files list.
Delete — Use the Delete button to remove the highlighted subroutine file from the
NC Subroutine Files list.

Coordinate Systems
Name – Use to specify the coordinate system name to be created in VERICUT.
Attach Component — Specify the attach component that the coordinate system will
be attached to.
Attach Axis System — Specify the attach axis system. The Attach Axis System
pull-down list displays the names of all coordinate systems contained in the
Pro/ENGINEER manufacturing file. When you select a coordinate system, that
coordinate system is positioned and aligned with the Attach Component in
VERICUT.
NC Program Origin — Specify the NC Program Origin axis system. The NC
Program Origin pull-down list displays the names of all coordinate systems in the
Pro/ENGINEER manufacturing file. When you select a coordinate system, then that
coordinate system will be transferred to VERICUT with the name specified above.
The relative relationship (position/orientation) between the Attach Axis System and
NC Program Origin axis system in Pro/E will be used to properly position and
orient the Csys in VERICUT.
Coordinate Systems List — This list displays the coordinates systems for each
attach component having a relationship between the Attach Axis System and the NC
Program Origin axis system.
Add — Adds the selected Attach Component, Attach Axis System and NC
Program Origin to the Coordinate System List.
Modify — Modifies the currently selected Coordinate System record with the Attach
Component, Attach Axis System and NC Program Origin.
Delete — Deletes the currently selected Coordinate System record.

Machine Settings
Table Name — Select the table name from the pull-down list.

133
 VERICUT Converters and Interfaces

Subsystem ID — Use to specify ID of the machine subsystem for which the table is
being defined. Select the subsystem ID from the pull-down list.
Register Number — Use to specify the register number that will be used by
VERICUT to access the corresponding table data. The register number may
correspond to an offset register number, or an integer value, as required by a
particular table. Enter the register number in the Register Number text field.
'From' Component — Enter the name of the component that represents the "from"
point for determining the program zero offset or choose a component from the drop
down list. VERICUT will use the origin of the specified component. The default
"From Component" is "tool".
'To' CSYS — Enter the name of a CSYS to represent the "to" point for determining
the program zero offset or choose a component from the drop down list. VERICUT
will use the origin of the specified CSYS. The default "To CSYS" is a coordinate
system named "Program_Zero".
G-Code Table List — Displays the list of G-Code Table records currently defined.
Add — Adds a G-Code Table record to the G-Code Table List based on the current
Table Name, Subsystem ID, Register Number, 'From' Component and 'To'
CSYS settings.
Modify — Modifies the G-Code Table record highlighted in the G-Code Table List
with the current Table Name, Subsystem ID, Register Number, 'From'
Component and 'To' CSYS settings.
Delete — Deletes the G-Code Table record highlighted in the G-Code Table List.

134
 VERICUT Converters and Interfaces

Settings Panel
The features on the Settings panel enable you to specify file type, file format and
tolerances for the model files output to VERICUT.

Output Model File Type — Use to specify the type of model files that are being passed
to VERICUT. Choose either VERICUT Model (VERICUT polygon file) or STL (Stereo
lithography model file).
Output Model File Format — Use to specify the file format of the model files. Choose
either ASCII or Binary.
NOTE: "Binary" VERICUT polygon files are platform specific.

Model Output Tolerance — Use to specify tolerance values for Stock, Fixture and
Design models.

135
 VERICUT Converters and Interfaces

Process Panel
The features on the Process panel enable you to generate the VERICUT files and start the
VERICUT session.

Use Embedded VERICUT — When toggled on, PROEV will use the embedded version
of VERICUT. The environment variable, VERICUT_FEATURE_NAME, must also be
set to EMBEDDED.
Generate Files — Use the Generate Files button to output all files required by
VERICUT, to simulate the Pro/ENGINEER manufacturing model, including project file,
tool library file, NC program file, model files and the "operations" file that assembles all
of this information into a VERICUT "project" file without starting VERICUT.
Run VERICUT — Once you have generated all the files needed by VERICUT, you can
start up VERICUT with the Run VERICUT button.
Generate and Run — Use Generate and Run to generate the files needed by VERICUT
and start VERICUT in the same step.

136
 VERICUT Converters and Interfaces

The proev_v70_user.prefs File

PROEV uses a preferences file to save/restore default settings. The preferences file is
named proev_v70_user.prefs. The file will be saved on the HOMEDRIVE in the
HOMEPATH. The preferences file is read during Pro/E startup and written to during
Pro/E closing. In PROEV, the File Selection Box (FSB) filter is not user modifiable via
the interface. The file filters are stored in the preferences file and can be modified by the
user.

The following describes the information stored in the proev_v70_user.prefs file.

ProevOutputDirectory
Corresponds to the Output Directory feature on the PROEV dashboard: File panel.
Format: ProevOutputDirectory,/path/filename

ProevFileName
Corresponds to the File Name feature on the PROEV dashboard: File panel.
FORMAT: ProevFileName,filename

ProevProjectTemplate
Corresponds to the Project Template feature on the PROEV dashboard: File panel.
Format: ProevProjectTemplate,/path/filename

ProevSetupTemplate
Corresponds to the Setup Template feature on the PROEV dashboard: File panel.
Format: ProevSetupTemplate,/path/filename

ProevAppendSetups
Corresponds to the Append to existing setups in project template feature on the
PROEV dashboard: File panel.
Format: ProevAppendSetups,value
0 = OFF
1 = ON

137
 VERICUT Converters and Interfaces

ProevEmbeddedVc
Corresponds to the Use Embedded VERICUT feature on the PROEV dashboard:
Process panel.
Format: ProevEmbeddedVc,value
0 = OFF
1 = ON

ProevModelFileType
Corresponds to the Output Model File Type feature on the PROEV dashboard: Settings
panel.
Format: ProevModelFileType,value
0 = VERICUT Model
1 = STL

ProevModelFileFormat
Corresponds to the Output Model File Format feature on the PROEV dashboard:
Settings panel.
Format: ProevModelFileFormat,value
0 = ASCII
1 = Binary

ProevStockTol
Corresponds to the "Stock" Output Model Tolerance feature on the PROEV
dashboard: Settings panel.
Format: ProevStockTol,tolerance value

ProevFixtureTol
Corresponds to the "Fixture" Output Model Tolerance feature on the PROEV
dashboard Settings panel.
Format: ProevFixtureTol,tolerance value

138
 VERICUT Converters and Interfaces

ProevDesignTol
Corresponds to the "Design" Output Model Tolerance feature on the PROEV
dashboard: Settings panel.
Format: ProevDesignTol,tolerance value

ProevUseToolID
Corresponds to the Use Tool ID feature on the PROEV dashboard: Options panel.
Format: ProevUseToolID,value
0 = OFF
1 = ON

ProevHead1
Corresponds to the Head 1 Subsystem ID feature on the PROEV dashboard: Options
panel.
Format: ProevHead1,head ID

ProevHead2
Corresponds to the Head 2 Subsystem ID feature on the PROEV dashboard: Options
panel.
Format: ProevHead2,head ID

ProevToolLibOverride
Corresponds to the Tool Library Override feature on the PROEV dashboard: Options
panel.
Format: ProevToolLibOverride,/path/filename

ProevAttachComp
Corresponds to the Attach Component feature on the PROEV dashboard: Options panel.
Format: ProevAttachComp,component name

139
 VERICUT Converters and Interfaces

ProevTpType
Corresponds to the NC Program Type feature on the PROEV dashboard: Options panel.
Format: ProevTpType,value
0 = APT
1 = G-Code

ProevTpName
Corresponds to the NC Program feature on the PROEV dashboard: Options panel.
Format: ProevTpName,/path/filename

ProevTableName
Corresponds to the Table Name feature on the PROEV dashboard: Options panel.
Format: ProevTableName,value

0 = None
1 = Cutter Compensation
2 = Gage Offset
2 = Probe Offset
4 = Tool Length Compensation
5 = Tool Nose Compensation
6 = Base Work Offset
7 = Initial Machine Location
8 = Machine Zero
9 = Machine Reference Location
10 = Tool Change Location
11 = Tool Change Retraction
12 = Turret Rotations
13 = Work Offsets
14 = Program Zero
15 = Input Program Zero (Special Z)
16 = RTCP Pivot Offset
17 = RPCP Pivot Offset

ProevRegisterNumber
Corresponds to the Register Number feature on the PROEV dashboard: Options panel.
Format: ProevRegisterNumber,value

140
 VERICUT Converters and Interfaces

ProevFromName
Corresponds to the 'From' Component feature on the PROEV dashboard: Options panel.
Format: ProevFromName,component name

ProevToName
Corresponds to the 'To' CSYS feature on the PROEV dashboard: Options panel.
Format: ProevToName,csys name

ProevProjectFilter
Corresponds to the Type filter on the Select Project Template file selection window
accessed using the Project Template, "Browse" button on the PROEV dashboard: File
panel.
Format: ProevProjectFilter,*. extension (for example *.VcProject)

ProevTLibOverrideFilter
Corresponds to the Type filter on the Select Tool Library file selection window accessed
using the Tool Library Override, "Browse" button on the PROEV dashboard: Options
panel.
Format: ProevTLibOverrideFilter,*. extension (for example *.tls)

ProevTpFilter
Corresponds to the Type filter on the Select Tool Library file selection window accessed
using the NC Program, "Browse" button on the PROEV dashboard: Options panel.
Format: ProevTpFilter,*. extension (for example *.ncl,*.tap)

ProevSubFilter
Corresponds to the Type filter on the Select Tool Library file selection window accessed
using the NC Subroutine Files, "Add" button on the PROEV dashboard: Options panel.
Format: ProevSubFilter, *. extension (for example *.sub)

141
 VERICUT Converters and Interfaces

Other Interfaces

Select from the following:

TDM Interface
840D Virtual NC Kernel and Interface (VNCK)

142
 VERICUT Converters and Interfaces

TDM Interface

Introduction to the TDM Interface

The VERICUT to TDM interface "pulls" information out of TDM Systems', Tool Data
Management (TDM) system, unlike all our other CAD/CAM interfaces which "push" the
information out of the CAD/CAM system. A running VERICUT session connects to the
TDM database through Oracle (version 8i is the latest version supported by TDM), then
retrieves information from TDM using a series of database "queries". TDM replaces the
VERICUT tool library, thus when using TDM there is no tool library file. TDM tool
information is loaded directly into VERICUT's memory, without intermediate files being
created or used.
VERICUT finds the desired TDM tool information using a TDM "list". The TDM "list"
is a list of tool assemblies for a specific job. The list simply contains references to tool
assemblies, which in turn contain references to the individual pieces of the tool (holders,
inserts, clamps, screws, etc.).
The tool geometry (which we are mostly interested in) is contained in a DXF file
(Drawing eXchange Format, originally invented by AutoCAD) referenced by the tool
assembly. The DXF file contains an assembly drawing, a 2D representation of the tool
assembly. VERICUT reads the DXF file, unravels the 2D information and creates a 3D
tool. This scheme requires the tool assembly information to reside on specific layers,
created in a specific way. The layers and format is loosely defined and controlled by
TDM when it is created. It is possible to ignore or avoid TDM's recommendations when
creating the tool assembly DXF drawing. This causes the DXF tool geometry to be
invalid for VERICUT.
However, assuming valid DXF arrangement and geometry, VERICUT automatically
creates tools from the DXF assembly drawings. Creation occurs on-the-fly when
VERICUT is reading the TDM tool list. VERICUT's user file only contains a reference to
the list name. Thus, each time VERICUT refreshes tool information (such as when
opening the user file), the TDM data is re-read and the tool geometry is re-created. This is
the "live" connection to the TDM database.
It is possible to save the TDM tool information as a VERICUT tool library file. Doing
this breaks the connection to TDM and the "list", and replaces it with a normal
VERICUT tool library file, referenced in the user file. It is also possible to import
individual TDM tool assemblies. This also breaks the connection to TDM, since the
connection is based on the TDM "list", not individual tools.

143
 VERICUT Converters and Interfaces

Using the TDM Interface

The TDM Interface provides access to the information stored in TDM Systems', Tool
Data Management (TDM) system database. The TDM Interface is accessed from the
VERICUT Tool Manager > File menu.

Selecting Access TDM displays of the following window.

144
 VERICUT Converters and Interfaces

The Account and Password text fields refer to your TDM account. If the TDM database is
installed on your computer the Database text field can be left blank. Otherwise enter the
name of the server where the database is located. Then click on the Connect button to log
into the account. If there are any problems, an error message will display in the text field
to the right of the Connect button. The values you supply for Account, Password and
Database are saved and automatically re-used next time you enter this dialog, so it should
not be necessary to click on the Connect button again.
Typically the TDM database will contain lists of tools that pertain to jobs or machines.
To select such a list, you can specify a filter for the list names in the Filter text field and
then click on the Load button. If you do not enter a filter, all the lists will be placed in the
table above, and there can be thousands. You can use "*" and "?" as wild cards in the
filter (in the normal VERICUT manner) or use "%" as you would with TDM. The lists
that match the filter will display in the table on the left.

Now pick the list you need from the left table, and the tools contained in the list will
display in the table on the right.

145
 VERICUT Converters and Interfaces

The column headings in this right table correspond to the TDM field names, but it is
worth noting that the content of the "Tool No." column gets used as the tool ID in
ToolManager, and the TDM "Tool ID" and "Description" fields are combined to form the
Tool Manager description.
If you click on the "OK" or "Apply" button, without changing the content of the tool table
in any way, the tool data is transferred to Tool Manager and the user file will reference
the TDM list. To indicate this, Tool Manager's title bar will display the TDM list name
instead of a VERICUT tool library name;

146
 VERICUT Converters and Interfaces

However, if you alter the tool data, by editing text, deleting tools or adding more, the
changes will not be reflected in the TDM database. A reference in the user file to a TDM
tool list is thus no longer viable. In this situation when you click on the "OK" or "Apply"
button, ToolManager's title bar will not include a list name and you will be expected to
save the tool data in a VERICUT tool library.
Even if you make no changes, you can save the tool data to a VERICUT tool library and
the link between the user file and the TDM tool list will be severed.
By turning on the "Append to Tool Library" option, you can add the tools from the
selected TDM list to those present in the currently accessed library. If there is a conflict
between tool IDs, the tools already in the library will prevail. With this option there will
be no link between the user file and the TDM list, because the set of tools accessed by the
user file is more comprehensive than the content of the list.

147
 VERICUT Converters and Interfaces

840D Virtual NC Kernel and Interface (VNCK)

Introduction 840D Virtual NC Kernel and Interface

The 840D Virtual NC Kernel (VNCK) and Interface is a VERICUT optional module
that provides an alternate control emulation method using the VNCK program developed
by Siemens Automation and Drives Motion Control Systems Division, the developers of
the 840D CNC control. When VERICUT uses the VNCK for simulation, VERICUT is
not reading the NC program and is not calculating the machine's axes positions. Rather,
the VNCK (an external process running on the Windows computer that is also running
VERICUT) reads the NC program, calculates the axes positions, and sends those
positions to VERICUT. The VNCK is only able to read and simulate NC programs
written for the Siemens 840D control.
The VNCK and Interface consists of two components: The 840D VNCK software
program developed by Siemens, and the VERICUT Interface to the VNCK program.
Using this optional module, the VERICUT simulation is controlled by the VNCK
program. The VERICUT Interface starts the VNCK and instructs it to load the control
configuration data and NC program. During simulation, the VNCK then reads the NC
program, calculates the NC motion axes positions, and sends this motion information to
VERICUT. The VNCK program contains the actual 840D control's NC kernel, providing
NC program processing and motion emulation consistent with the physical control. The
VERICUT interface handles communication between the VNCK and VERICUT, using
Microsoft's COM protocol.

Limitations:
OptiPath and CNC Machine Probing ARE NOT compatible with the VNCK. Also,
since the VNCK is directing the simulation, other standard VERICUT simulation features
may not be available or may behave differently. Additionally, the VNCK only notifies
VERICUT when motion commands, those NC lines containing axes motions, are
processed. Other NC program lines, such as variable definitions, calculations, and
miscellaneous functions, are not considered NC events and are not displayed in the
sequential processing of the NC program.

Licensing:
The VNCK program requires a separate node-locked license from Siemens. It is not
available as a network license (i.e. does not "float"), but is locked to the specific machine
where the VNCK is used. Thus a separate VNCK licensed module is needed for each
computer that will run it. The license is locked to the MAC (physical ethernet hardware)

148
 VERICUT Converters and Interfaces

address of ALL network devices detected on the computer. Thus all MAC addresses on
the target computer are required.

VERICUT Machine/Control Configuration:

A VERICUT machine and a control file are still required for a VNCK configuration.
When used with VERICUT, the VNCK program reads the NC program and passes axes
positions to VERICUT. However, only axes controlled by the NC kernel (typically the
machine's primary motion axes) are recognized. Any other commands, such as tool
change, feed rate, pallet change, coolant, and other miscellaneous NC program codes are
not recognized by the VNCK. These are typically known as "PLC" (Programmable Logic
Controller) functions, outside the realm of the NC kernel. It is VERICUT's responsibility
to emulate these PLC actions. A mechanism is available to register PLC commands with
the VNCK, so that it can notify VERICUT when one of these commands is encountered.
However, VERICUT must be configured to register each command and provide a
simulation action for the event.
Currently, only VERICUT NC macros configured in the Word Address dialogue may be
executed. It is not possible to execute a sub-program from within VERICUT when using
the VNCK control emulation.

NC "ARC" Data:
In addition to the usual VERICUT configuration requirements, CGTech must also copy
the NC "ARC" (ARChive) data file from the physical 840D control to the simulation
computer. This file must then be expanded using Siemens' ARC utility, and configured
for VNCK simulation. The ARC file is then saved in a proprietary binary format for use
with the VNCK.

Hardware:
The VNCK only works on computers running Windows 2000 and Windows XP
Professional operating systems.

149
 VERICUT Converters and Interfaces

Installation and Use of VNCK

General Description
The Siemens’ Virtual NCK (VNCK) system is used to drive a VERICUT simulation by
providing the functions of a target Sinumerik 840D control. The VNCK uses the actual
840D machine parameter (ARC) file when processing NC program (MPF) and subroutine
(SPF) files. A VNC Server works with the VNCK to control NC program execution and
obtain the processed 840D status and axis motion results. VERICUT interfaces to this
VNC Server and receives the axis positions resulting from NC commands as well as data
from the program processing within the VNCK. VERICUT uses this VNCK data to
simulate stock cutting, machine axis motions, and to keep various status displays
updated.

Siemens’ VNCK
Users should follow Siemens’ directions for installing the VNCK and obtaining the
necessary operating license. For each machine control being simulated, the user must
obtain a Sinumerik 840D ARC (archive) file. The ARC file contains machine parameter
setting, axis definitions, NC programs, subprograms, and tool definitions. Since 840D
control space is limited, all unnecessary NC programs and tool definitions should be
deleted from the 840D control before the ARC file is saved.
Considerable time is normally required to boot the VNCK from an ARC file. However,
after the VNCK is booted, the VNCKView utility can save a binary version of the
VNCK's memory and use it to quickly boot on subsequent occasions. This binary version
of the VNCK's memory is called an SRAM file and is recommended for VERICUT
applications. Note that all SRAM files should be rebuilt whenever a new version of the
VNCK is installed.

VERICUT Implementation
When the VNCK is used with VERICUT, the major difference is that VERICUT does
not read and parse the NC programs. Instead, the VNCK processes the NC programs and
provides axis positions to VERICUT. Tool change events, messages, alarms, M-codes,
and speed-feed settings are also provided to VERICUT by the VNCK. VERICUT still
requires a control file (CTL), but it is only used to process macros associated with the
tool changes, M-codes, or speeds and feeds.
The initial implementation does not support VERICUT sub-systems or control file
subroutines.
The VERICUT-VNCK system is distributed with VERICUT as a special DLL. The
"cgtvnck.dll" file should be placed in the C:\CGTechxx\windows\vericut (where xx is the
VERICUT version number) folder and the following line inserted in the vericut.bat file:

150
 VERICUT Converters and Interfaces

set CGTECH_VNCKAPI=C:\CGTechxx\windows\vericut\cgtvnck.dll
(where xx is the VERICUT version number)
A special file folder structure is also used by VERICUT-VNCK applications. The
Siemens’ 840D expects a KONFIG.DIR folder containing the machine's definition (ARC
and SRAM files) and any subroutine (SPF) files shared by multiple projects. Multiple
project folders (e.g. PROJECT_1.WPD, PROJECT_2.WPD) can be defined at the same
level as the KONFIG.DIR folder. Each Working Project Directory (WPD) contains the
main part programs and associated subprograms (MPF and SPF files).
In VERICUT, the VNCK option is selected by setting the "NC Program Type" to
"Siemens VNC 840D". The following dialog will appear if VERICUT has a license for
the VNCK interface:

NC Program Type — Type of NC program file for VERICUT to simulate.

Initial Tool — When active, VERICUT loads an initial tool from a Tool Library file.
This action occurs automatically when the Project file is loaded, the NC program is
rewound, or the model is reset. Choose the ID of desired tool using the option list next to
this feature. This feature is useful when simulating NC programs for machines that have a
tool loaded at the time tool processing is started, therefore do not have information about
the first tool.

VNCK Control File — Selects a DAT, ARC or INI file from the konfig.dir folder
associated with the machine and project being simulated. As described above, a SRAM
(.dat) file is recommended, however ARC and INI files can also be directly used.

151
 VERICUT Converters and Interfaces

Main Toolpath (MPF) — Selects the NC program being simulated. The main program
must have an "mpf" extension and should reside in the "project.wpd" folder if it is not an
external MPF.

External MPF — Indicates the MPF does not reside in the WPD folder. The 840D has
additional restrictions regarding "external files" defined in Siemens’ documentation.

Working Project Directory — Select the WPD folder for the application being
simulated. Note that this folder must have a ".wpd" appended to its name and must have
the same parent folder as the "konfig.dir" folder.

Stop VNCK — This button will kill the VNCK process. It should only be used if
communications between VERICUT and the VNCK is lost.

The VNCK is booted the first time PLAY or SINGLE-STEP is requested in VERICUT.
Normally there is a several second delay before control returns to VERICUT. The status
of the boot operation is displayed in the VERICUT logger.
The RESET operation in VERICUT initializes the system for a new simulation. During a
RESET, the VNCK is shutdown and rebooted to reset its memory to the initial state. This
typically adds several seconds to the normal VERICUT RESET operation.
VERICUT tool definitions and offset registers are passed to the VNCK during the VNCK
boot phase. This information is written to a "VericutVNCK.ini" file residing in the
"konfig.dir" folder. All tools including any compensation values (D2, D3, etc.) used in
the MPF must be defined in VERICUT's tool manager before starting a VNCK
simulation. The VNCK will generate an alarm if a tool is not defined when referenced in
the MPF. Future versions of the VNCK will allow direct interface calls to replace the
need for the VericutVNCK.ini file.
VNCK messages and alarms are displayed in the logger and written to the VERICUT log
file. In addition, interactions between VERICUT and the VNCK can be recorded in the
G-Code log file. This trace information is recorded when the "Debug Marco Arguments"
option is selected.
During simulation, a "Single Step" request in VERICUT might result in several blocks of
the NC program being processed. This is because the VNCK reports motion, tool change,
and M-code events, but does not report all program blocks being processed. Non-motion
blocks (variable assignments, conditional statements, subroutine calls, etc.) may be
combined into a single step before results are reported to VERICUT.
During a VNCK simulation the VERICUT Toolpath window shows a pointer to the
current block of the MPF being processed. When subroutines are called, the Toolpath
window will only display the SPF file if it has been declared as a subroutine in G-Code
Settings (ref. Project menu > Processing Options > G-Code > Settings > Subroutine
tab in the VERICUT Help section, in the CGTech Help Library).
Most VNCK alarms need to be resolved before simulation can be completed. The
Siemens’ diagnostic document "840d_da.pdf" provides additional problem descriptions

152
 VERICUT Converters and Interfaces

which may be helpful resolving alarms. The VNCK error identification is displayed in the
logger window and can be used with the "840d_da.pdf" to obtain the complete error
description.
During a VNCK simulation the VERICUT dialog for variables (ref. Project menu >
Processing Options > G-Code > Variables in the VERICUT Help section, in the
CGTech Help Library) will display updated values for Tracking Variables. Note that the
VNCK reports variable values when they are processed in the "Preparatory" phase. Since
the Preparatory phase may be several blocks ahead of the current motion block, the
values may change before the toolpath window indicates the block has been processed.
Also see the restriction below for variables.
The VNCK calculates the time during a simulation and this time value is used to update
the VERICUT status information.

VERICUT Control Files

The VERICUT CTL file is used to process tool change events, M-codes, and speed-feed
settings. The initial implementation does not support VERICUT sub-systems and control
file subroutines. Two special CTL words have been used to handle tool selection and tool
changes. These are "VNCK_TOOLSELECT" and "VNCK_TOOLCHANGE". The
CTL file must be modified to define these words and associate the correct macros with
them for VERICUT tool changes.

Machine File Changes

The machine tool builder chooses names for the axes defined in the 840D ARC file.
During the VNCK boot phase, the VNCK provides these configuration names to
VERICUT so they can be matched with VERICUT axes components. The VERICUT
components should be renamed to agree with the ARC file names.
If the axes names are not known, they can be located in the ARC file by searching for
definitions similar to those shown below:

N10000 $MN_AXCONF_MACHAX_NAME_TAB[0]="X1"
N10000 $MN_AXCONF_MACHAX_NAME_TAB[1]="Y1"
N10000 $MN_AXCONF_MACHAX_NAME_TAB[2]="Z1"
N10000 $MN_AXCONF_MACHAX_NAME_TAB[3]="B1"
N10000 $MN_AXCONF_MACHAX_NAME_TAB[4]="SP"

153
 VERICUT Converters and Interfaces

Restrictions

1. In-Process (IP) files are not operational with the VNCK since the VNCK can not
again be synchronized with VERICUT when the IP file is later restored. An error
message is displayed if a VNCK session attempts to save an IP file.

2. The VNCK supports turning applications, however, turning has not been
implemented in the initial VERICUT-VNCK interface.

3. The VNCK supports multiple channels, however, the relation between multiple
channels and VERICUT sub-systems has not been implemented in the initial
VERICUT-VNCK interface.

4. During the VNCK boot process, all MPF and SPF files in the WPD folder are loaded
into the VNCK's memory. Large programs may overflow the available VNCK
memory producing a "NC Memory Full" alarm and truncating the file. If this occurs,
move the files to a separate folder and check the "External MPF" box on the Toolpath
dialog.

5. During simulation, VERICUT and the VNCK exchange asynchronous messages.

Errors have occurred causing the VERICUT to lose its connection with the VNC
Server. VERICUT will wait for 30 seconds before admitting a failure. Report this
problem and restart your job.

6. OptiPath and Curve Fit are not supported in the VERICUT-VNCK system. These
options require the original tool path file which is not being read and parsed by
VERICUT when the VNCK is active.

7. The number of variables being watched is limited to 5 with VNCK version 1.40.10.0.
This limitation should be removed in future versions of the VNCK.

154