Skip to content

Working with Vericut Files

Introduction to Using Vericut Files

In the following discussion the term "Vericut" represents Vericut, Vericut Composite Simulation and Vericut Drill and Fastener Simulation. Any exceptions will be noted within the topic.

This section introduces you to files commonly used in Vericut, and how to work with them. For a complete list of Vericut files with detailed descriptions, see Vericut File Descriptions in the Getting Started section of Vericut Drill and Fastener Simulation Help.

Common Vericut files

The files described below are most commonly used to configure Vericut, monitor the verification session, and save session information. Familiarity with these files will enable you to work more efficiently in Vericut, and get the most from your verification system.

NC Program files — These files contain data describing cutting tool positions, machine information, and other information required to operate NC machine tools. Vericut simulates and verifies two distinct types of NC program files: ASCII APT-CLS and G-code, or machine code data. Vericut must be configured differently, depending on which NC program type you choose to process.

Project files — These files contain Vericut session settings, also known as "user configuration values" or "user values". Virtually everything changeable in the user interface can be saved in a Project file. Relatively small in size, Project files minimize effort required to configure Vericut for processing multiple setup NC jobs.

In Process files — Also known as "IP files", contain all data necessary to re-establish a Vericut session, most importantly, the 3-D Vericut model with any cuts that were machined into it. Even the Log file (see below) is restored providing error history of prior NC program files used to machine the workpiece.

Log files — These files record information about the Vericut session, such as: error, warning, and informational messages, machining times, optimization results, and more. Reviewing these files is an important step in ensuring that simulated tool paths have performed as expected.

Machine files and Control files — These files contain information required to simulate G-Code NC program files and machining on an NC machine. Machine files contain such information as: machine axes, connect order, kinematics, 3-D size/shape, etc. Control files contain the rules for how machine codes are processed, which word/addresses perform specific functions, order of processing, etc.

Configuring Vericut to start with a custom Project file

By default, Vericut starts with either the "vericut.VcProject" (inch sessions) or "vericutm.VcProject" (mm sessions) Library file. You can change the project file Vericut starts with by setting the CGTECH_VCPROJECT environment variable in the "vericut" batch file prior to the entry that executes Vericut. The command files are located in the "platform\commands" folder, where "platform" represents the computer type on which Vericut is running (e.g. "windows64\commands")

Example edited "vericut" batch file (added the CGTECH_VCPROJECT entry):

set CGTECH_VCPROJECT=C:\myfolder\myproject.vcproject

  %start_cmd% "%CGTECH_JRE%\bin\javaw" %ARG_SPLASH% -Dsun.java2d.noddraw=true -Xms128m -Xmx512m -Xss6m -classpath "%CGTECH_CLASSES%;%CGTECH_CLASSES%\Vericut.jar;%CGTECH_CLASSES%\iText.jar;%CGTECH_CLASSES%\iTextAsian.jar;%CGTECH_CLASSES%\acrobat.jar;%CGTECH_CLASSES%\MRJToolkitStubs.zip" Vericut %ARGSTR%

:end_cgtech

endlocal

Where Vericut looks for referenced files

In the following discussion the term "Vericut" represents Vericut, Vericut Composite Simulation, and Vericut Drill and Fastener Simulation.

Vericut looks in the places listed below (in listed order) when trying to find files referenced in Vericut files. An example follows.

Look in the folder specified by the path stored in the Vericut file.

  1. If not found, look in the current Working Directory.

  2. If not found, look in the parent folder (the folder where the file containing the referenced file came from).

  3. If not found, look in the Vericut Library as specified by the CGTECH_LIBRARY environment variable.

Example

Consider the following:

Vericut is run from the M:\mydirectory location.

The command file used to run Vericut defines CGTECH_LIBRARY to point to C:\Program Files\Vericut [version number]]\library.

Using File tab > Open, you navigate to D:\projectfiles and select a project file that contains a reference to a Vericut Tool Library file stored in E:\NCparts.

Vericut looks in the following locations to find the Tool Library file.

  1. E:\NCparts — specified by the path stored in the Vericut file

  2. M:\mydirectory — the current Working Directory

  3. D:\projectfiles — parent folder where the Project file came from
  4. C:\Program Files\Vericut [version number]\library — specified by the CGTECH_LIBRARY environment variable

Vericut quits looking as soon as a file is found. If all locations are checked without findinging the referenced file, an error is issued.