Command Line Options¶

Click the below options to quickly navigate to the relevant section of the page.

• Converters

• ToolMan

• Vericut

• VDAF
• Reviewer
• CAS Repair

Command Line Options for Vericut Converters¶

Vericut converter products provide a way to translate a wide variety of CAD/CAM data, primarily for use in Vericut. All converters can be run interactively, or in batch mode. When run in batch, command line options are used to configure the converters without the use of the user interface.

The sections that follow describe command line options available for Vericut converter products. See the appropriate section for details.

📝 Windows note: Command line options containing an assignment ("=") must be surrounded with double quotes, for example: iges2v "input=inputfile.igs"

Binary CL Converter command line options¶

Syntax: bincl2v [argument list]

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

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

See Binary CL Converter, in the Converters and CAD/CAM Interfaces section of the Vericut Help Library for additional information.

CAD Converter command line options¶

Syntax: cad2v [argument list]

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

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

See CAD Model Converter, in the Converters and CAD/CAM Interfaces section of the Vericut Help Library for additional information.

IGES Converter command line options¶

Syntax: iges2v [argument list]

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

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

See IGES Converter, in the Converters and CAD/CAM Interfaces section of the Vericut Help Library for additional information.

PolyFix Converter command line options¶

Syntax: polyfix [argument list]

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

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

See Polyfix Converter, in the Converters and CAD/CAM Interfaces section of the Vericut Help Library for additional information.

Surface to Solid Converter command line options¶

Syntax: sur2stk [argument list]

The command line options available for the Surface to Solid Converter are described in the table below.

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

See Surface to Solid Converter, in the Converters and CAD/CAM Interfaces section, in the Vericut Help Library for additional information.

VDA Converter command line options¶

Syntax: vda [argument list]

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

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

See VDA Converter, in the Converters and CAD/CAM Interfaces section, in the Vericut Help Library for additional information.

Post Process command line options¶

Syntax: project file (/path/filename) [argument list]

Command line options available for post processing in batch mode are described in the table below.

See Post Processor, in the Converters and Interfaces section of the Vericut Help Library for additional information.

Command Line Options for Stand-alone Tool Manager¶

toolman.bat [argument list]

This batch file enables you to open a stand-alone Tool Manager independent of Vericut. The command line options described below enable Tool Manager to be opened with a specified Vericut tool library (.tls) file, import CAD model files.

📝 NOTE: Command line options typically must be enclosed in double quotes ("") when used in a standard Windows command prompt, due to special characters in the option, such as the "=" character.

Arguments:

"filename"

filename is a fully qualified filename, including the directory path, of a Vericut tool library file (.tls). See Example 1 below to see how it is used.

"CAD_MODEL=cadfilename"

cadfilename is a fully qualified filename, including the directory path, of the CAD model file to open. The file name extension indicates the type of file: STEP (.stp or .step) or CATIA V5 (.CATPart, .CATProduct). The 'filename' of the CAD model file will be used in the description field of the tool created. The tool ID will be a number incremented to the next available tool number. Using this command line argument causes the CAD Geometry window to be opened in addition to the Tool Manager window. It sets the CAD File feature in the CAD Geometry window. See Example 3 below to see how it is used.

"CAD_TOOL_TYPE"=tooltype"

tooltype is the "type" of tool being imported in the CAD model file. Use Mill for milling tools, and Turn for turning tools. It sets the Tool Type feature in the CAD Geometry window. See Example 3 below to see how it is used.

"CAD_UNITS =units"

units represent the "units" of the tool that is to be created in Tool Manager. This is not the incoming units of the CAD model file since that is determined by reading the unit setting in the CAD file. Select either Inch, or Millimeter to set the Units feature in the CAD Geometry window. See Example 3 below to see how it is used.

"CAD_NORMALS=normals"

normals is used to specify the direction of surface normals relative to the material. Use Inward to specify that the surface normals point inward towards the material, or Outward if the surface normals point away from material. It sets the Normals feature in the CAD Geometry window. See Example 3 below to see how it is used.

"tls=filename"

filename is a fully qualified filename, including the directory path, of a Vericut tool library file (.tls).

In some cases, filename is the name of an existing Vericut tool library file. See Example 2 below to see the how it is used with an existing tool library file.

In other cases, filename is the name of a Vericut tool library file that is to be created. See Example 3 below to see how it is used to create a new tool library file.

"report=report_name"

report_name is a fully qualified filename, including the directory path, for the Tool Library Report file to be created (.pdf, .txt, or .htm). See Example 2 below to see how it is used.

📝 NOTES:

1. Report format is determined by the "report_name" file extension:
   
   A ".pdf" extension will create the report in PDF format.
   
   A ".txt" extension will create the report in text format
   
   A ".htm" extension will create the report in HTML format.

2. The report will be created using the template file stored in the user preferences file if one exists, otherwise the default template from the /library/ directory of your Vericut installation will be used.

Example 1:

Open a stand-alone Tool Manager window with a specified Vericut Tool Library file.

Syntax:

toolman.bat "filename"

where filename is the tool library file (.tls) that is to be opened in Tool Manager.

Sample command:

\windows64\commands\toolman.bat "C:\test\filename.tls"

Example 2:

Create a Tool Library Report file.

Syntax:

toolman.bat "tls= tls_name " "report=report_name"

where:tls_name is the name of the tool library file (.tls) to be used to create the report.

report_name is the name of the report that is to be created. The report_name extension determines the report format.

Sample command:

...\windows64\commands\toolman.bat

"tls=...\library\vericut_setup2.tls" "report=C:\test\tool_report.htm"

Example 3:

Open a stand-alone Tool Manager window and the CAD Geometry window to import tool insert and holder solid models from a CAD system into Vericut's Tool Manager. Currently, only STEP and CATIA V5 files are supported.

Syntax:

toolman.bat "tls= tls_name " "CAD_MODEL=cadfilename" "CAD_UNITS =units" "CAD_TOOL_TYPE=tooltype" "CAD_NORMALS=normals"

where:tls_name is the name of the tool library file (.tls) that the tool/assembly is to be imported to. If the tool library file does not currently exist, it will be created when you save it in Tool Manager.

cadfilename is the name of the CAD model file to be imported.

units represent the "units" of the tool that is to be created in Tool Manager.

tooltype is the "type" of tool being imported in the CAD model file.

normals represent the direction of the surface normals relative to the material.

Sample command:

...\windows\commands\toolman.bat

"tls=...\library\vericut_setup1.tls"

"CAD_MODEL=C:\tool_models\tool_12345.stp"

"CAD_UNITS =Inch" "CAD_TOOL_TYPE"=Turn" "CAD_NORMALS=Outward"

Tool Manager starts with the "CAD Geometry" window open, the CAD model file loaded, the Tool Type, Units and Normals settings pre-set based on the command line option settings, and the tool displayed in the Tool Manager graphics window. When you are finished in Tool Manager you can save the file, or exit and you will be prompted to save the file.

See the Arguments section above for additional information on each argument used in the examples.

See Tool Manager section of Vericut Help for additional information on the Vericut Tool Manager.

See CAD Geometry window section of Vericut Help for additional information on the CAD Geometry window.

Command Line Options for Vericut¶

Command line options configure and control Vericut upon execution. Command line options are particularly useful in customizing the user interface for specific site use, or during batch processing as described in "Batch Processing".

See the Vericut Help section, in the Vericut Help Library, for additional information on any of the Vericut windows, or files, referred to in the following section.

Available command line options are listed in alphabetical order in the following table. Each is described in detail below. Options can be arranged on the command line in any order.

📝 NOTES:

1. If the option you are looking is not listed above, see "Obsolete command line options" at the end of this section.

2. Command line options containing an assignment ("=") must be surrounded with double quotes, for example: vericut "usr=part.usr"

Command Line Option Details¶

<uservariablename>=<uservalue>

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

Example:

vericut "FASTFEED=500"

When combined with other command line options that affect project values, the options are processed in the order listed below. Processing order is the same regardless of the order in which they are listed on the command line.

The order in which command line options affecting project values are processed:

1. ip=<ipfile> — load Vericut model

2. usr=<usrfile> — load complete set of user values

3. vcp=<file> — load complete set of project values
4. <uservariablename>=<uservalue> — load individual user values

📝 NOTES:

1. Specific spelling and formats apply. To see a list of Vericut user variable names/values, view any Project file saved from the current version of Vericut. The middle column lists user variables, while the right column indicates the saved user values for corresponding user variables.

2. When specifying multiple word user values join the words with an underscore ("_").

append_log

When Vericut is run and an existing Log file is detected, the Log file is opened in "append" mode. Additional log messages are appear at the end of the file.

Also see: reset_log and LGFILNAM=<logfilename>.

auto-diff=<reportfilename>

Performs an AUTO-DIFF model comparison and writes results to the specified AUTO-DIFF Report file. The comparison method and tolerances used are controlled via the AUTO-DIFF window. The comparison is performed when tool path processing has finished. Immediately afterwards, Vericut automatically restores the model to its "as machined" state, as it was prior to differencing.

This option is commonly used during batch processing to automatically inspect the part after machining.

batch

The batch command enables you to run Vericut in the background, without opening the user interface. In this mode, Vericut loads specified IP, User, or Project files (in listed order), processes the tool path file(s), and exits-without user interaction. The "batch" option can appear anywhere on the command line. Examples follow.

Examples:

vericut batch "vcp=part.VcProject"

vericut "vcpr=C:\ncparts\part.VcProject" batch

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

📝 NOTES:

1. The same Vericut security and computer resources are required to run Vericut in batch mode as required during interactive processing.

2. Logging out after initiating a batch session has no affect on the process, as long as the computer remains active.

3. Another form of batch processing, batchp, "pops open" the Vericut window when finished to reveal the cut workpiece.
4. A "Batch Wizard" provides a guided, graphical method of creating and running Vericut products in batch mode.

See "Batch processing" for details.

batchp

"batchp" is similar to batch, except that when processing is finished, the Vericut window "pops open" to reveal the cut workpiece. The model can then be analyzed or saved for later use.

See "Batch processing" for details.

BKGNCLR

Use to specify the Background color.

"BKGNCLR=0 0 255 Blue" where "0 0 25 Blue" represents the color identifier from the Color window Color List.

See Color window: Define tab, Color List in the Vericut Help section, in the Vericut Help Library, for more information.

burn

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

csys_file=<filename>

Reads the specified CSYS File and creates one or more Vericut coordinate systems. If this command line argument is used, then Vericut does not create CSYS's when processing the NC program file. This command provides the same functionality as the CSYS from File feature in the Coordinate System window.

dxf2sor [argument list]

Enables you to import two dimensional geometry from files which comply with a de facto CAD system standard, the Data eXchange Format (DXF) to define a "closed" 2-D profile that can be "revolved" about the Z-axis to create solid model.

Arguments:

"input=<dxf_filename>" (Required)

(dxf_filename is a fully qualified filename, including the directory path, of a DXF file containing at least one closed profile)

["output=<sor_filename>"] (Optional)

(sor_filename is a fully qualified filename, including the directory path, of the output SOR file)

📝 NOTE: If "output" is not specified, the resulting output file will default to the name of the DXF file, without the extension, with a ".sor" extension added (dxf_filename.sor). If the output file already exists, it is overwritten.

["layer=<layerame>"] (Optional)

(layername is a fully qualified filename, including the directory path, of the output SOR file)

📝 NOTE: IF "layer" is specified, only entities on the specified layer will be converted. If "layer" is not specified, entities on all layers will be converted

["Help"] (Optional)

This argument prints out the valid arguments.

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

dxf2sweep [argument list]

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

Arguments:

"input=<dxf_filename>" (Required)

(dxf_filename is a fully qualified filename, including the directory path, of a DXF file containing at least one closed profile)

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

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

["output=<sweep_filename>"] (Optional)

(sweep_filename is a fully qualified filename, including the directory path, of the output SWEEP file)

📝 NOTE: If "output" not specified, the resulting output file will default to the name of the DXF file, without the extension, with a ".swp" extension added. If the output file already exists, it is overwritten.

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

(lay1_name, lay2_name, ... is the name of the layer containing the DXF entities )

📝 NOTE: IF "layer" is specified, only entities on the specified layer(s) will be converted. If "layer is not specified, all entities will be converted

It is possible to have multiple closed profiles that represent holes in the interior of the model. If multiple profiles exist, they must conform to the following:

1. cannot intersect other profiles

2. cannot self-intersect

3. inner profiles must be completely contained by the outer profile
4. cannot be contained by any other profile
5. all entities of a closed profile must have same layer name

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

export

Exports the Vericut cut model. The method and tolerances used are controlled via the File tab > Save Cut Stock > CAD Model configuration. The export operation is performed when NC program processing has finished.

fitall

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

FLATBG

The FLATBG command sets all View backgrounds to the "Flat Background Color".

hres=<value>

This command sets the screen display resolution in the horizontal direction. The value entered is in pixels.

Also see: vres=<value>.

ip=<ipfile>

This command loads an existing In-process file into Vericut. The full directory path can be included with the file name. The examples that follow assume an In-process file named "part.ip" has been saved.

Examples:

vericut "ip=part.ip"

vericut "ip=C:\ncparts\part.ip"

When combined with other command line options that affect user values, the options are processed in the order listed below. Processing order is the same regardless of the order in which they are listed on the command line.

The order in which command line options affecting user values are processed:

1. ip=<ipfile> — load Vericut model

2. usr=<usrfile> — load complete set of user values\

3. vcp=<file> — load complete set of project values
4. <uservariablename>=<uservalue> — load individual user values

LGFILNAM=<logfilename>

Actually a user variable override, this option sets the name of the Log file to receive error, warning, and informational messages resulting from processing a tool path in Vericut.

Also see: append_log and reset_log.

MinExtFile=<filename>

This command calculates the min cutter extension and saves the adjusted tools in a tool library named “filename”.

Syntax:

“MinExtFile= filename”

(filename is a fully qualified filename, including the directory path, for the Vericut tool library file that is to receive the adjusted tools.)

Sample command:

“MinExtFile=C:\tool_libs\extended_tool_lib1.tls

The optional argument "[S]" can be used in "filename" for multiple setups. For example, using the command "MinExtFile=new_tools[S].tls" with vericut.Vcproject, which has three setups, will produce the following three files:

• new_toolsS1.tls

• new_toolsS2.tls

• new_toolsS3.tls

ops=</path/filename>

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

Any extension can be used in the file name, but by convention ".VcTmp" denotes a temporary file.

optimize

Turns optimization on for optimizing tool path feed rates and/or spindle speeds. Cutting tools optimized and optimization values used are controlled via the Project tab > NC Programs and Optimize tab > Optimize Control configurations.

report

Use to generate a Vericut report in "batch". Using the command line option "report", the Vericut report file name and report template file stored in the Vericut Project file is used. Use the command line option "report_template", described below, to specify a different report template file.

Use the command line option "report=<filename>", to specify using a different report file than the one stored in the Vericut Project file. The report format (text, HTML, PDF) is defined by the report file extension (.txt, .html, .pdf) of report file name. Default format is HTML. Use the command line option "report_template", described below, to specify using a different report template file than the one stored in the Vericut Project file.

See Introduction to Vericut Reports in the Vericut Help section, in the Vericut Help Library, for more information.

report_template

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

reset_cutcolor

The reset_color command resets the cut colors of all machine cuts to be one color: the Reset Cut color. Cut colors are reset prior to cutting.

reset_log

When Vericut is run and an existing Log file is detected, the Log file is reset (cleared) prior to writing new log messages.

Also see: append_log and LGFILNAM=<logfilename>.

reverse

Reverse the active view prior to cutting. This option is useful when recording images and tool motion occurs on the opposite side of the model.

See "Reverse" in the View tab > Orient for more information.

save_vcreview=<filename>

This command line option sets a flag that causes a review file to be saved at end of processing (end of the last setup). This command line option is only applicable when running in “batch” mode.

STL_OUTPUT

This command line option turns on STL output enabling the export of an STL model of the cut stock in batch mode. If the STL output file name is not specified in command line, Vericut will use the one specified in the VCProject file. If the output file name is not specified in the VcProject file, the export will fail.

📝 NOTE: This command line option only works in "batch" mode.

The following parameters are optional:

“STLFIL=filename.stl”

  Specifies the name and location of the STL output file.

“STLSTKNM=stock”

  Specifies the stock name to use for STL output.

“STLUNIT=[-1,0,1] ”

  Specified units for STL output operation. Use -1 for No Units; 0 for Inch; and 1 for Millimeter.

“STLCSYS=[0,1] ”

  Specifies the coordinate system to use for STL output. Use 0 for Stock or 1 for Active coordinate system.

“STLFRMT=[0,1]”

  Specifies the format of the output file. Use 0 for ASCII or 1 for binary output format.

"STLTYPE=[0,1]"

  Specifies the STL output file type. Use 0 for “Vericut” Type or 1 for “STL” Type.

"STLREDUCE"

  Using this optional parameter turns on "Reduce Triangle” mode. The STL file will be created using the triangle reduction method.

STOCK_BLOCK_FROM_DESIGN_EXTENT

Creates a “Block” stock model having Length X/Width Y/Height Z size and position such that a child or sibling Design model is completely surrounded by stock material.

Sample Vericut batch command:

"C:\Program Files\CGTech\Vericut 9.7\windows64\commands\vericut" "vcp=apt_adsurf2.vcproject" STOCK_BLOCK_FROM_DESIGN_EXTENT batch

STOCK_BLOCK_OFFSET=<n>

Used with the STOCK_BLOCK_FROM_DESIGN_EXTENT to create a “Block” stock model with Length X/Width Y/Height Z size such that each side is offset “n” units larger than the Design model inside.

Sample Vericut batch command (5mm offset):

"C:\Program Files\CGTech\Vericut 9.7\windows64\commands\vericut" "vcp=apt_adsurf2.vcproject" STOCK_BLOCK_FROM_DESIGN_EXTENT "STOCK_BLOCK_OFFSET=5" batch

📝 NOTES:

• The commands can be upper case or lower case.

• Currently effective for defining a block for (1) Stock component.

• Design component can be a child or sibling to Stock component.

usr=<usrfile>

This command line option loads an existing user file into Vericut. The full directory path can be included with the file name. The examples that follow assume a User file named "part.usr" has been saved.

Examples:

vericut "usr=part.usr"

vericut "usr=C:\ncparts\part.usr"

When combined with other command line options that affect user values, the options are processed in the order listed below. Processing order is the same regardless of the order in which they are listed on the command line.

The order in which command line options affecting user values are processed:

1. ip=<ipfile> — load Vericut model

2. usr=<usrfile> — load complete set of user values

3. vcp=<file> — load complete set of project values
4. <uservariablename>=<uservalue> — load individual user values

vcp=<file>

This command loads an existing Project file into Vericut. The full directory path can be included with the file name. The examples that follow assume a Project file named "part.VcProject" has been saved.

Examples:

vericut "vcp=part.VcProject"

vericut "vcp=C:\ncparts\part.VcProject"

When combined with other command line options that affect user values, the options are processed in the order listed below. Processing order is the same regardless of the order in which they are listed on the command line.

The order in which command line options affecting user values are processed:

1. ip=<ipfile> — load Vericut model

2. vcp=<file> — load complete set of project values

3. <uservariablename>=<uservalue> — load individual user values

vres=<value>

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

Obsolete command line options¶

The command line options listed below are obsolete in this version of Vericut. Recommended alternate command line options are recommended where possible.

• autodemo = <imgfile> — Not supported.

• batcht — "True batch", obsolete- use "batch" instead.

• FORCE — Turns on Force.

• FORCE_FEED_OPTIMIZATION=0|1 — Set Force Mode: Analyze (0) or Optimize (1)

• FORCEOD = Directory — Set Output Directory

• OpenGL — Not supported.

• pbappend — Obsolete

• pseudocolor — No longer applies.

• results — No longer applies.

• slice — Not supported in this release.

• statdisp = <computername> — Not supported.

• truecolor — No longer applies.

• zoom_out[=<value>] — Obsolete

Command Line Option for Vericut Drilling and Fastening¶

The following describes commands that can be used to start the Vericut Drilling and Fastening from a command line.

C:\cgtech97\windows64\commands\vdaf.bat "C:\Program Files\temp\projectA.vdafproject"

The following describes commands that can be used to post NC program from the Vericut Drilling and Fastening from a command line.

vdaf "vcp=C:\Program Files\temp\projectA.vdafproject" "post_file=C:\Program Files\temp\projectA.vcpost" "POST_OUT= C:\Program Files\temp\program.mpf " post_run

Command Line Options for Vericut Reviewer¶

The following describes commands that can be used to start the Vericut Reviewer from a command line.

C:\cgtech97\windows64\commands\reviewer.bat "C:\Program Files\temp\3_axis_mill_fanuc.vcreview"

or

C:\cgtech97\windows64\commands\reviewer.bat review_filename="C:\Program Files\temp\3_axis_mill_fanuc.vcreview"

Notice in the above example, the "review_filename" command line option is used.

Or if spaces are in the installed path as is the default for V97, you will need double quotes on either side of the command line argument as shown below:

"C:\Program Files\cgtech`\<version number>`\windows64\commands\reviewer.bat" review_filename="C:\Program Files\temp\3_axis_mill_fanuc.vcreview"

Notice the double quotes are not used around the command line option argument like that used by Vericut.

For example:

C:\cgtech97\windows64\commands\vericut.bat "vcp=C:\Program Files\cgtech`\<version number>`\samples\3_axis_mill_fanuc.vcproject"

Using Command Line Options to save sub-window configurations

"readprefs=[filename]"

Command Line Options for CAS Repair Utility¶

Syntax: cas_repair [argument list]

The command line options available for the CAS Repair Utility are described in the table below.

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

See CAS Repair Utility, in the Custom Group section, in the CGTech Help Library for additional information.