Automating Vericut

8/19/2019 Automating Vericut

1/49

Automating VERICUT

1

Go to CGTech Help Library

Automating VERICUT

Batch VERICUT

Batch Script Files

Multiple VERICUT batch sessions can be run via a single executable command byincluding VERICUT batch commands in an executable script file. The script file is thensubmitted to the operating system for processing. After each batch execution terminates,the operating system then executes the next command in the script file.

Batch files for different operating systems differ slightly in format. Details will followlater in this document. In general, each batch command in the script file appears as itwould when entered by itself on the command line. Other operating system commands,such as those that delete or rename files can also be included in the script file.

Tip: VERICUT batch files can be easily created using VERICUT's Batch Wizard .

Windows batch script files

A batch file to be run on Windows is named with a ".bat" extension, for example"batchfile.bat". Windows NT batch execution lines in the script file are "called" via the

"call" command to return control to the script file after each VERICUT execution. Theexamples that follow show two sample script files.

Windows XP batch script file examples:

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

call vericut batch "vcp=part1.VcProject"

call vericut batch "vcp=part2.VcProject"

Example 2 represents a part machined in two setups: the first is configured toautomatically save an In-process file named "setup1.ai" via the AutoSave function.The second uses the ip= option to load the "setup1.ai" In-process file socutting can be continued with the session configuration saved in the"setup2.VcProject" project file.

call vericut batch "vcp=setup1.VcProject"


2/49

Automating VERICUT

2

call vericut batch "vcp=setup2.VcProject" "ip=setup1.ai"

UNIX batch script files

A batch script file to be executed in UNIX must have "executable" permissions. Use the

"chmod" command to give the file executable permissions, for example the followingcommand makes a file named "batchfile" executable by all users: chmod 777 batchfile

The "batchfile" file is executed via typing the file name on the command line, forexample type: batchfile The examples that follow show two sample script files.

UNIX batch script file examples:

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

vericut batch vcp=part1.VcProjectvericut batch vcp=part2.VcProject

Example 2 represents a part machined in two setups: the first is configured toautomatically save an In-process file named "setup1.ai" via the AutoSave function.The second uses the ip= option to load the "setup1.ai" In-process file socutting can be continued with the session configuration saved in the"setup2VcProject" project file.

vericut batch vcp=setup1.VcProjectvericut batch vcp=setup2.VcProject ip=setup1.ai


3/49

Automating VERICUT

3

Batch Processing

Running VERICUT in batch automates the verification process by loading requestedVERICUT files, processing the NC program file, and exiting VERICUT-all withoutopening the VERICUT window. Other command line options are commonly used tospecify the VERICUT Project file(s) and/or IP file(s) needed for the simulation, performVERICUT functions, and change VERICUT variable values. See "Command lineoptions" for more information.

VERICUT is run in batch mode (unattended in the background) by including the "batch"command line option, or via the Batch Wizard . Another form of batch processing,"batchp", pops open the VERICUT window when finished to reveal the cut workpiece.You can run other applications, or perform other tasks while VERICUT is processing in batch mode.

The same CGTech security and computer resources are required to run VERICUT in

batch as required during interactive processing. Logging out after initiating a batchsession has no affect on the process, as long as the computer remains active.

The following simple examples run VERICUT as configured by the previously created"part.VcProject" project file:

vericut batch vcp=part.VcProject (UNIX)

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

The values stored in the Project file provide information about the stock model tomachine, tool path file(s) to process, orientations of the models and tool paths, type ofmachining to simulate, etc. In this above example the following actions occur:

1. VERICUT is executed.

2. Load the "part.VcProject" project file.

3. Press Play to start the simulation. (Also writes a Log file containing errors andother information about the simulation.)

4. When finished, exit VERICUT.

For greater automation, multiple batch execution commands can be compiled in anexecutable batch script file, as described by the sections that follow.


4/49

Automating VERICUT

4

Batch Wizard

The Batch Wizard graphically guides you through setting up and running CGTech products in batch mode. Batch mode runs CGTech products unattended in the background. Command line options and configuration files control the batch processwithout opening the VERICUT window. This allows you to run other applications, or perform other tasks while CGTech products are being productive.

Accessing the Batch Wizard

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

• Access the Batch Wizard on a Windows computer — From the Taskbar, clickStart > All Programs > CGTech VERICUT 6.x > Utilities > Batch Wizard where "6.x" is the desired VERICUT version number.

• Access the Batch Wizard on a UNIX computer — Type "bwizard". If thecommand is not found, include the full path, e.g."///commands/bwizard" where representsthe directory path to where CGTech products were installed, and is the type of computer on which VERICUT is being operated, for example:hp700, rs, sgi, or solaris.

Sample Batch wizard window:


5/49

Automating VERICUT

5

In general, follow the prompts-press Next to go to the next screen, Back returns to the previous screen. Finish indicates batch session setup is complete and opens a window tospecify the name of the batch session file to save. Following are general descriptions ofBatch Wizard screens that guide you through setting up a batch session file.

Main screen — Also known as the "Welcome screen", this screen welcomes you to the

Batch Wizard. You can start a new batch session, modify an existing session, or run anexisting session.

Operation screen — This screen is used to add, modify, or delete batch operations.Operations can be named as desired, and are performed in listed order. Use Move Up /Move Down to change the order in the list.

CGTech product screen — This screen is used to specify which CGTech product will be run in the batch operation. Choose O.S.Command to use an operating systemcommand to assist with batch processing, such as: copy, move, append, rename, and setenvironment variables.

CGTech product screen — This screen is used to specify which CGTech product will be run in the batch operation. Choose O.S.Command to use an operating systemcommand to assist with batch processing, such as: copy, move, append, rename, and setenvironment variables.

Command line option screen — This screen is used to choose one or more command

line options for the product being run in batch. Press the right arrow to include theoption in the batch session being configured. Use the left arrow to remove an unwanted

option. Use the file selection button to specify files to use. Be sure to include one ofthe batch options (batch or batchp) to run the CGTech product in batch mode.

After setup is finished, choose Run an existing session from the main screen to run the batch session. Batch session files created by the Batch Wizard are computer independent,and can be run on any computer that is capable of running VERICUT.


6/49

Automating VERICUT

6

Configuring for Batch Process Output

Output from running VERICUT in batch always includes a Log file. VERICUT can also be configured to automatically perform many operations, or output many different typesof files. The following sections describe how to configure VERICUT for batch processoutput.

See the VERICUT Help section, in the CGTech Help Library, for additional informationon any of the VERICUT windows, or files, referred to in the following examples.

To batch save IP or View Capture files:

1. Configure VERICUT for processing the desired Project file (models, NCPrograms, tools, etc.)

2. Click File menu > AutoSave to display the AutoSave window.3. Click on either the In Process tab (if configuring to automatically save IP files),

or the View Capture tab (if configuring to automatically save View Captureimage files). If saving View Capture image files, then click on Properties on theView Capture tab to display the View Capture window and use its features toconfigure the desired image file format.

4. In either case, use the Auto Save features select the event(s) and enter supportingdata that will cause VERICUT to automatically save the file. Type the name to beused for the file in the text field, or click on Browse and use the window thatdisplays to specify the /path/filename for the file.

5. Use the Auto Error features to have VERICUT automatically save the file whenan error is encountered. Toggle the "On" checkbox on and type the name to beused for the file in the text field, or click on Browse and use the window thatdisplays to specify the /path/filename for the file.

NOTE: If using both Auto Save and Auto Error, be sure to use different filenames for each to avoid overwriting.

6. Press OK.

7. Save a Project file (or IP file) to be used during the batch process, for example"test.VcProject"

8. Exit VERICUT9. To start batch processing use the Batch Wizard, or execute VERICUT with

vcp= and batch (or batchp) command line options, for example:

vericut batch vcp=test.VcProject


7/49

Automating VERICUT

7

To batch record VERICUT Image files:

1. Configure VERICUT for processing the desired project file (models, tool path,tools, etc.)

2. Click File menu > Images > Record Movie to display the Image Record

window.3. Configure the window as desired to record snapshot or animation images.

4. Press Record, then Stop, to retain Image Record window changes.

5. Close the Image Record window.

6. Save a Project file (or IP file) to use during the batch process, for example"test.VcProject"

7. Exit VERICUT

8. To start batch processing use the Batch Wizard, or execute VERICUT withvcp=, record, and batch (or batchp) command line options, for example:

vericut batch vcp=test.VcProject record

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

vericut batch vcp=test.VcProject record IMRCAPDT=on

To batch compare design models using AUTO-DIFF:

1. Configure VERICUT for processing the desired project file (models, tool path,tools, etc.)

2. Depending on the AUTO-DIFF comparison method to be used, ensure a DesignSolid, Surface or Point model is loaded (ref. Modeling Window in the VERICUT Help section).

3. Click Analysis menu > AUTO-DIFF to display the AUTO-DIFF window.

4. Configure the AUTO-DIFF features as required to compare with the design modeland show gouge, and/or excess conditions.

5. Press Apply, and then close the AUTO-DIFF window.


7. Exit VERICUT

8. To start batch processing use the Batch Wizard, or execute VERICUT withvcp=, auto-diff=, and batch (or batchp) command lineoptions, for example:

vericut batch vcp=test.VcProject auto-diff=test.rpt


8/49

Automating VERICUT

8

To batch optimize tool path files using OptiPath:

1. Configure VERICUT for processing the desired project file (models, tool path,tools, etc.), and optimizing the desired tools.

The following steps assuming an OptiPath Library file exists containing the desiredoptimization data, and that VERICUT has already been configured to optimize tool paths.If the library does not exist or does not contain all of the desired optimization data, usethe OptiPath window to create this file. Use the Tool Manager window, the OptiPathwindow, and the OptiPath Control window features to configure VERICUT foroptimization.

See "About optimizing NC programs" in the Using VERICUT section, in the CGTech Help Library, for additional information.

2. Click OptiPath menu > Control to display the OptiPath Control window.

3. Ensure the window is configured as required (OptiPath Library file name,Material, Machine, etc.) to optimize the desired tools. Do not turn optimizationOn in this window to start tool path optimization, as this will be done via the"optimize" command line option.

4. Press OK.


6. Exit VERICUT

7. To start batch processing use the Batch Wizard, or execute VERICUT withvcp=, optimize, and batch (or batchp) command line options, for example:

vericut batch vcp=test.VcProject optimize


9/49

Automating VERICUT

9

Command Line Options

Command Line Options for VERICUT

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

See the VERICUT Help section, in the CGTech Help Library, for additional informationon 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 anyorder.

Command line option: General description:

= Sets a user variable (value in the userinterface)

append_log Open Log file in append mode

auto-diff= Perform an AUTO-DIFF model comparisonand write results to a file

batch Runs VERICUT in the background, withoutopening the user interface

batchp Similar to batch, except "pops open" theVERICUT window when finished

burn Processes the "Burn" function in a DieSinking Simulation

csys_file= Reads the specified CSYS File and creates aVERICUT coordinate system.

dxf2sweep Imports DXF 2D geometry and creates a"sweep" solid model

dxf2sor Imports DXF 2D geometry and creates a


10/49

Automating VERICUT

10

"solid of revolution" solid model

export Exports the VERICUT cut model

fitall Fits all open views

hres= Sets the horizontal screen display resolution

IMRCAPDT=on Appends recorded images to an existingImage file

ip= Loads an In Process file

LGFILNAM= Set the Log file name

ops= Creates an Operations file

optimize Turns OptiPath on

record Records VERICUT images to an Image file

report= Creates a VERICUT report file

report_template= Specifies the VERICUT report template fileto use for creating a VERICUT report.

reset_cutcolor Resets cut colors of all machine cuts

reset_log Reset the Log file

reverse Reverses the active view

vcp= Loads a Project file

usr= Loads a User file

VericutPlayer Plays back the specified VERICUT imagefile.

vres= Sets the vertical screen display resolution


11/49

Automating VERICUT

11

zoom_out[=] Zooms out approximately 20% for each"zoom_out"

NOTE: If the option you are looking is not listed above, see "Obsolete command line

options" at the end of this section.WINDOWS NOTE: Command line options containing an assignment ("=") must besurrounded with double quotes, for example: vericut "usr=part.usr"


12/49

Automating VERICUT

12

Command Line Option Details

=

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 thecommand line are not case sensitive. However, some operating systems use casesensitivity when reading directory paths and file names. Consult your operating systemguide to determine if case sensitivity applies.

Windows example:

vericut "FASTFEED=500"

UNIX example:

vericut FASTFEED=500

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

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

1. ip= — load VERICUT model

2. usr= — load complete set of user values

3. vcp= — load complete set of project values

4. = — load individual user values

NOTES:

1. Specific spelling and formats apply. To see a list of VERICUT user variablenames/values, view any Project file saved from the current version of VERICUT.The middle column lists user variables, while the right column indicates the saveduser 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.

http://command_line_options_for_vericut.htm/http://command_line_options_for_vericut.htm/http://command_line_options_for_vericut.htm/http://command_line_options_for_vericut.htm/http://command_line_options_for_vericut.htm/http://command_line_options_for_vericut.htm/http://command_line_options_for_vericut.htm/http://command_line_options_for_vericut.htm/


13/49

Automating VERICUT

13

Also see: reset_log and LGFILNAM=.

auto-diff=

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 theAUTO-DIFF window. The comparison is performed when tool path processing hasfinished. Immediately afterwards, VERICUT automatically restores the model to its "asmachined" state, as it was prior to differencing.

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

batch

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

Windows examples:

vericut batch "vcp=part.VcProject"

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

UNIX examples:vericut batch vcp=part.VcProject

vericut vcp=/ncparts/part.VcProject batch

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

NOTES:

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

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

3. Another form of batch processing, batchp, "pops open" the VERICUT windowwhen finished to reveal the cut workpiece.


14/49

Automating VERICUT

14

4. A "Batch Wizard " provides a guided, graphical method of creating and runningCGTech products in batch mode.

See "Batch processing" for details.

batchp

Similar to batch, except when finished the VERICUT window "pops open" to reveal thecut workpiece. The model can then be analyzed or saved for later use.

See "Batch processing" for details.

BKGNCLRUse to specify the Background color.

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

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

burn

Executes the processing of the "Burn" feature of a Die Sinking Simulation. The exportoperation is performed when tool path processing has finished.

csys_file=

Reads the specified CSYS File and creates one or more VERICUT coordinate systems. Ifthis 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 theCSYS from File feature in the Coordinate System window.

dxf2sor[argument list]Enables you to import two dimensional geometry from files which comply with a defacto 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=" (Required)


15/49

Automating VERICUT

15

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

["output="] (Optional)

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

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

["layer="] (Optional)

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

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

["Help"] (Optional)

Prints out the valid arguments.

dxf2sweep[argument list]

Enables you to import two dimensional geometry from files which comply with a defacto 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 specifieddistance, and then outputs it to a VERICUT sweep file.

Arguments:

"input=" (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 Zaxis)


16/49

Automating VERICUT

16

["output="] (Optional)

(sweep_filename is a fully qualified filename, including the directory path, of the outputSWEEP 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 filealready exists, it is overwritten.

["layer="] (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 themodel. 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 theFile menu > Save Cut Stock > CAD Model window configuration. The exportoperation is performed when tool path processing has finished.

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


17/49


18/49

Automating VERICUT

18


LGFILNAM=

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

Also see: append_log and reset_log.

ops=

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

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

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

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

optimize

Turns OptiPath on for optimizing tool path feed rates and/or spindle speeds. Cutting toolsoptimized and optimization values used are controlled via the Project menu > NCPrograms and OptiPath menu > Control window configurations.

record

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

http://log_file.htm/http://command_line_options_for_vericut.htm/http://command_line_options_for_vericut.htm/http://log_file.htm/


19/49

Automating VERICUT

19

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 Projectfile is used. Use the command line option "report_template", described below, to specify

a different report template file.Use the command line option "report=", to specify using a different reportfile 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. Defaultformat is HTML. Use the command line option "report_template", described below, tospecify using a different report template file than the one stored in the VERICUT Projectfile.

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

report_template

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

See Create a Report Using a Template in the Using VERICUT section, in the CGTech Help Library, for more information.

reset_cutcolor

Resets the cut colors of all machine cuts to be one color: the Reset Cut color. Cut colorsare 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=.

reverse

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

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


20/49

Automating VERICUT

20

usr=

Loads an existing user file into VERICUT. The full directory path can be included withthe file name. The examples that follow assume a User file named "part.usr" has beensaved.

Windows examples:

vericut "usr=part.usr"

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


21/49

Automating VERICUT

21

UNIX examples:

vericut usr=part.usr

vericut usr=/ncparts/part.usr

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

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

1. ip= — load VERICUT model

2. usr= —- load complete set of user values



vcp=

Loads an existing Project file into VERICUT. The full directory path can be includedwith the file name. The examples that follow assume a Project file named"part.VcProject" has been saved.

Windows examples:

vericut "vcp=part.VcProject"

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

UNIX examples:

vericut vcp=part.VcProject

vericut vcp=/ncparts/part.VcProject

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

The order in which command line options affecting user values are processed:1. ip= — load VERICUT model




22/49

Automating VERICUT

22

VericutPlayer[argument list]

Enables you to open a "VERICUT Player" window and play back an Image file recordedusing the File menu > Images > Record function or the record command line option.

Arguments:

" filename"

( filename is a fully qualified filename, including the directory path, of a VERICUTImage file)

"impbfil=( filename)"

( filename is a fully qualified filename, including the directory path, of a secondVERICUT Image file to play both Image files simultaneously)

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

"impberrt=value)"

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

"impbchgt=value)"

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

"impbnevt=value)"

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

"impbeoft=value)"

(value

is either "on" or "off"; whenvalue

=on, causes playback to stop when the endof an NC program file has been reached )

"impbneve=value)"

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


23/49

Automating VERICUT

23

"impbstop=value)"

(value is either "on" or "off"; when value=on, playback stops at an "inserted stop")

"impbloop=value)"

(value is either "on" or "off"; when value=on, causes playback to loop continuouslyuntil interactively stopped by pressing the Escape key )

"impbssd=value)"

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

vres=

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

zoom_out[=]

Zooms out, or decreases the viewing size of uncut stock models by approximately 20%for each "zoom_out" listed. For example, "zoom_out" zooms out one step, while"zoom_out=2" zooms out twice.

See "Zoom Out" in the View menu > Orient window for more information.

Obsolete command line options

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

autodemo = — Not supported.

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

OpenGL — Not supported.

pbappend — Obsolete- use "IMRCAPDT=on" instead.

pseudocolor — No longer applies.

results — No longer applies.

slice — Not supported in this release.

statdisp = — Not supported.

truecolor — No longer applies.


24/49

Automating VERICUT

24

Command Line Options for CGTech Converters

CGTech converter products provide a way to translate a wide variety of CAD/CAM data, primarily for use in VERICUT. All converters can be run interactively, or in batch mode.

When run in batch, command line options are used to configure the converters withoutthe use of the user interface.

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

WINDOWS NOTE: Command line options containing an assignment ("=") must besurrounded with double quotes, for example: iges2v "input=inputfile.igs"

Binary CL Converter command line options

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

Option Description Default

batch Execute without user interface

batcht (obsolete) Same as "batch"

input=input-file Binary CL Input File

output=output-file Output File (ASCII APT)

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

cltype={1|2|3|4}Input File Type:

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

circles={YES|NO} Output Circles Yes

height=value Minimum Cutter Height 0


25/49

Automating VERICUT

25

CAD Converter command line options

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


batchExecute without userinterface

input=input-file CAD Input File

output=output-file Output File

dtol=value Deviation Tolerance 0.05

format={ASCII|BINARY} Output File Format BINARY

type={VERICUT|STL} Output File Type STL

dir={INWARD|OUTWARD} Normal Direction OUTWARD


26/49

Automating VERICUT

26

IGES Converter command line options

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




input=input-file IGES Input File


dtol=value Deviation Tolerance0.05 for in. model, 1.27for mm model


type={VERICUT|STL} Output File Type STL

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

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

summarySummary of input filecontents


27/49

Automating VERICUT

27

PolyFix Converter command line options

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




input=input-file Input File

intype={VERICUT|STL} Input File Type STL


outformat={ASCII|BINARY} Output File Format BINARY

outtype={VERICUT|STL} Output File Type STL


28/49

Automating VERICUT

28

Surface to Solid Converter command line options

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




input=input-file IGES Input File


tol=value Tolerance

intype={VERICUT|STL} Input File Type

outtype={VERICUT|STL} Output File Type

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

matrix=matrix-string Transformation Matrix Identity matrix

offset=value surface Offset 0

base=value Base Location 0

rectangle={NO|YES} Project Rectangle NO


29/49

Automating VERICUT

29

VDA Converter command line options

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




input=input-file VDA Input File


dtol=value Deviation Tolerance0.05 for in. model, 1.27for mm model


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

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


30/49

Automating VERICUT

30

Controlling VERICUT with Comment Records

Comment records, for example "PPRINT/COMMENT TEXT" in APT or CLS tool paths,or "(COMMENT TEXT)" in G-code tool paths, typically have no affect on tool motion

simulated by VERICUT. However, special "VERICUT comment" records are availableto help control the tool path simulation in VERICUT. For example, VERICUT commentscan be used to change cut colors, set VERICUT user interface values, or cause VERICUTto perform certain actions, such as: AUTO-DIFF model comparisons, reversing the view,etc.

Note that for G-Code NC programs, the NC control must be configured to interpret thecomment record format for that control, for example "begin comment" word, "endcomment" word (if present), etc. Some simple examples follow.

Examples of VERICUT comment records that reverse the model view:

APT or CLS tool path:

PPRINT/VERICUT-COMMAND reverse

G-Code tool paths:

Fanuc control configured with "(" begin comment word, and ")" end commentword —

(VERICUT-COMMAND reverse)

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

(MSG,VERICUT-COMMAND reverse)

Heidenhain control configured with ":" begin comment word (no end commentword) —

:VERICUT-COMMAND reverse


31/49

Automating VERICUT

31

The available VERICUT comment records with specific formats and examples aredescribed in the sections

VERICUT-BEGINTABLE record

VERICUT-COMMAND records VERICUT-CUTCOLOR record

VERICUT-ENDTABLE record

VERICUT-MATRIX record

VERICUT-MODAL record

VERICUT-MOTION record

VERICUT-OPTIPATH record

VERICUT-TC record

VERICUT-TOOLID record

VERICUT-USERTAG record


32/49


33/49

Automating VERICUT

33

VERICUT-COMMAND Record

Special comment records that perform VERICUT commands or operations. Thecommands available via comment records are listed below with examples of use.

Note that for G-code tool paths, the NC control must be configured to interpret thecomment record format for that control, for example "begin comment" word, "endcomment" word (if present), etc. See "Controlling VERICUT with comment records" forsome examples.

auto-diff

Performs an AUTO-DIFF comparison, then restores the cut model.

Examples of use:

APT/CLS — PPRINT/VERICUT-COMMAND auto-diff

G-code (Fanuc) — (VERICUT-COMMAND auto-diff)

display

Updates the display of a FastMill cut model with current cuts.

Examples of use:

APT/CLS — PPRINT/VERICUT-COMMAND display

G-Code (Fanuc) — (VERICUT-COMMAND display)

display_fixtures

Displays all defined fixture models. (See also "remove_fixtures".)

Examples of use:

APT/CLS — PPRINT/VERICUT-COMMAND display_fixtures

G-code (Fanuc) — (VERICUT-COMMAND display_fixtures)


34/49

Automating VERICUT

34

load_model_by_name ""

Loads a model referenced by its name. (See also "remove_model_by_name")

Examples of use:

Load the model named "Model 2" from the sample models list:

Model Definition List

---------------------

Model 1 (Stock)

Model 2 (Fixture)

Model 3 (Design Solid)

APT/CLS — PPRINT/VERICUT-COMMAND load_model_by_name "Model 2"

G-code (Fanuc) — (VERICUT-COMMAND load_model_by_name "Model 2")

load_fixture_by_seq

Loads the fixture referenced in the sequential order of defined fixtures. (See also"remove_fixture_by_seq ")

Examples of use:

Load the second fixture model (Model 3) in the sample models list:

Model Definition List

---------------------Model 1 (Stock)

Model 2 (Fixture)

Model 3 (Fixture)

APT/CLS — PPRINT/VERICUT-COMMAND load_model_by_seq 2

G-code (Fanuc) — (VERICUT-COMMAND load_model_by_seq 2)

pause n

Adds "n" seconds of delay to an Image file being recorded. (See Record Movie in theVERICUT Help section, in the CGTech Help Library, for additional information.)

Examples of use:

Add 5 seconds of pause:

APT/CLS — PPRINT/VERICUT-COMMAND pause 5

G-code (Fanuc) — (VERICUT-COMMAND pause 5)


35/49


36/49

Automating VERICUT

36

remove_model_by_name ""

Removes a model referenced by its name. (See also "load_model_by_name")

Examples of use:

Remove the model named "Model 2":

APT/CLS — PPRINT/VERICUT-COMMAND remove_model_by_name“Model 2”

G-code (Fanuc) — (VERICUT-COMMAND remove_model_by_name “Model2”)

remove_fixture_by_seq

Removes the fixture referenced in the sequential order of defined fixtures. (See also"load_model_by_seq ")

Examples of use:Remove the second fixture model in the models list:

APT/CLS — PPRINT/VERICUT-COMMAND remove_model_by_seq 2

G-code (Fanuc) — (VERICUT-COMMAND remove_model_by_seq 2)


37/49

Automating VERICUT

37

VERICUT-CUTCOLOR Record

Special comment records that assign the cut color for the active tool. Cut colors arereferenced via an index corresponding to the colors defined for use via the "Shade Colorlist" on the Edit menu > Colors: Define tab (See the VERICUT Help section, in theCGTech Help Library for additional information). Color index numbers range from 0-nwhere “0” refers to the first color in the list-typically assigned to be the Error color. "1"refers to the second listed color, and so on. The index number is always 1 less than theindex seen in the user interface. Examples follow.

Note that for G-code tool paths, the NC control must be configured to interpret thecomment record format for that control, for example "begin comment" word, "endcomment" word (if present), etc. See "Controlling VERICUT with comment records" forsimple examples.

Examples of use:

Set the cut color to "Light Steel Blue", as referenced in the sample Color window below:

APT/CLS — PPRINT/VERICUT-CUTCOLOR 2

G-code (Fanuc) — (VERICUT-CUTCOLOR 2)


38/49

Automating VERICUT

38

VERICUT-ENDTABLE Record

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

Example of use:

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

(VERICUT-BEGINTABLE "setup_info")

( 1ST OP, METALDYNE PUNCH SLEEVE BODY )

( PART #,H0070-0243 )

( REV.,"A" )

( NC Program File,L1H0070-0243.TXT)

( DATE ORIGINALLY PROGRAMMED,10/24/03 )

( PROGAMMED BY,CHARLIE WILSON )

( STOCK,6-1/2" H-13 CUT +.150 )

(- ,CHUCK ON STOCK DIA. 3.00" DEEP )

(- ,WITH FULL CHUCK PRESSURE )

(- ,UNDERCUT YOUR JAWS FOR A GOOD GRIP )

(VERICUT-ENDTABLE)

where the VERICUT-BEGINTABLE statement indicates the start of the table data,setup_info is the User-Defined Tag name, the remaining statements represent the contentof the table, and the VERICUT-ENDTABLE statement indicates the end of the tabledata. Each comment record represents a row in the table and the "," character is used toseparate the column entries. (see Using PPRINT info from an NC program in a report in the Using VERICUT section, in the CGTech Help Library, for additional information)

NOTE: See VERICUT-USERTAG record for information on populating a table in aVERICUT report using a text file.


39/49

Automating VERICUT

39

VERICUT-MATRIX Record

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

The format of the matrix is as follows:

i j k d

X i1 j1 k1 d1

Y i2 j2 k2 d2

Z i3 j3 k3 d3

The first three columns represent the axes of the local system: i1, i2, i3 as the positive X-axis vector; j1, j2, j3 as the positive Y-axis vector; and k1, k2, k3 as the positive Z-axisvector. The fourth column d1, d2, d3 is the origin point of the local system. The activematrix is reset to an identity matrix (no rotation or translation) each time a new tool pathfile is processed.


Examples of use:

Translate the tool path 2 units in X, 3 in Y, and -1 in Z.

APT/CLS — PPRINT/VERICUT-MATRIX 1,0,0,2,0,1,0,3,0,0,1,-1

G-code (Fanuc) — (VERICUT-MATRIX 1,0,0,2,0,1,0,3,0,0,1,-1)

As above, except in APT/CLS multi-line record format using the "$" continuation:

PPRINT/VERICUT-MATRIX 1,0,0,2,$

PPRINT/VERICUT-MATRIX 0,1,0,3,$

PPRINT/VERICUT-MATRIX 0,0,1,-1


40/49

Automating VERICUT

40

Rotate the tool path 180 degrees about the Y axis:

APT/CLS — PPRINT/VERICUT-MATRIX -1,0,0,0,0,1,0,0,0,0,-1,0

G-code (Fanuc) — (VERICUT-MATRIX -1,0,0,0,0,1,0,0,0,0,-1,0)


41/49

Automating VERICUT

41

VERICUT-MODAL Record

Special comment records that specify a user interface value, such as a data field entry oran option choice. One user variable/value can be set per record. Most user variablesfound in a Project file can be set or modified in this way.


Examples of use:

Set the Fast Feed data field value to "100":

APT/CLS — PPRINT/VERICUT-MODAL FASTFEED=100G-code (Fanuc) — (VERICUT-MODAL FASTFEED=100)

Choosing the Machining Type option for simulation of milling or turning operations:

APT/CLS milling mode — PPRINT/VERICUT-MODAL MACHTYPE=milling

APT/CLS turning mode — PPRINT/VERICUT-MODAL MACHTYPE=turning

G-code (Fanuc) milling mode — (VERICUT-MODAL MACHTYPE=milling)

G-code (Fanuc) turning mode — (VERICUT-MODAL MACHTYPE=turning)


42/49

Automating VERICUT

42

VERICUT-MOTION record

Special comment records that control when tool motions and cutting are simulated. Whenoff, motion commands and tool positions are processed, but simulation, cutting, collisiondetection, and axis overtravel detection are suspended (ignored) during subsequentmoves. When motion is turned on, the tool and/or NC machine "jumps" to its current position. The motion "on" condition is automatically set when a reset is done.


Examples of use:

Turn motion off:

APT/CLS — PPRINT/VERICUT-MOTION off

G-code (Fanuc) — (VERICUT-MOTION off)

Turn motion on:

APT/CLS — PPRINT/VERICUT-MOTION on

G-code (Fanuc) — (VERICUT-MOTION on)


43/49

Automating VERICUT

43

VERICUT-OPTIPATH record

Special comment records that control when tool motions are optimized via the OptiPath.When off, optimization is suspended (ignored) during subsequent moves-tool pathrecords are written to the Optimized file as they were programmed. Optimization remainsoff until the next OptiPath "On" record is encountered. Optimization must be turned on prior to the next tool change. A format also exists for specifying which OptiPath libraryrecord to use:

VERICUT-OPTIPATH DESC="my_optipath_tool_description" TEETH=

where "my_optipath_tool_description" is an optimization record description which couldcontain any characters, including delimiters. The description must be enclosed in doublequotes. "N" is the number of cutting teeth. This record specifies two of the four valuesneeded to identify which optimization record to use. The other two values come fromMaterial and Machine on the OptiPath Control window. If an optimization record

matching the four values is not found, VERICUT continues to write un-optimized tool path records to the optimized tool path file.

See the VERICUT Help section, in the CGTech Help Library, for additional informationon OptiPath and the OptiPath Control window.


Examples of use:

Turn optimization off:

APT/CLS — PPRINT/VERICUT-OPTIPATH off

G-code (Fanuc) — (VERICUT-OPTIPATH off)

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

Turn optimization on:

APT/CLS — PPRINT/VERICUT-OPTIPATH on

G-code (Fanuc) — (VERICUT-OPTIPATH on)


44/49

Automating VERICUT

44

Specify an OptiPath library record for use with the current tool:

APT/CLS — PPRINT/VERICUT-OPTIPATH DESC=".5 Dia Ball EM, Carbide"TEETH=4

G-code (Fanuc) — (VERICUT-OPTIPATH DESC=".5 Dia Ball EM, Carbide"

TEETH=4)


45/49

Automating VERICUT

45

VERICUT-TC record

Special comment records that define the shapes of cutters, shanks or holders in a toolassembly. Interpreted like a CUTTER record, anything allowed to follow "CUTTER/" isalso allowed to follow "VERICUT-TC". Like "CUTTER", this record is processed bydefault via Tool Change By in the NC Programs window set to: "Cutter Desc." or"VERICUT TC". See the VERICUT Help section, in the CGTech Help Library, foradditional information.


Examples of use:Defines an APT-type seven parameter cutter shape- 1.0 diameter x .125 corner radius x3.0 height:

APT/CLS — PPRINT/VERICUT-TC 1.0,.125,0,0,0,0,3.0

G-code (Fanuc) — (VERICUT-TC 1.0,.125,0,0,0,0,3.0)

Defines a profile cutter shape:

APT/CLS — PPRINT/VERICUT-TC XCUT,PTS,0,0,.5,0,ARC,1,0,.5,PTS,1,.5,1,1

G-code (Fanuc) — (VERICUT-TC XCUT,PTS,0,0,.5,0,ARC,1,0,.5,PTS,1,.5,1,1)

As above, except in APT/CLS multi-line record format using the "$" continuation:

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

PPRINT/VERICUT-TC ARC,1,0,.5,PTS,1,.5,$

PPRINT/VERICUT-TC 1,1

Defines a profile shank shape:

APT/CLS — PPRINT/VERICUT-TC SHANK,PTS,0,0,.5,0,.5,1,0,1

G-code (Fanuc) — (VERICUT-TC SHANK,PTS,0,0,.5,0,.5,1,0,1)

Defines a profile holder shape:

APT/CLS — PPRINT/VERICUT-TC HOLDER,PTS,0,0,1,0,1.5,.5,1.5,3,0,3

G-code (Fanuc) — (VERICUT-TC HOLDER,PTS,0,0,1,0,1.5,.5,1.5,3,0,3)


46/49

Automating VERICUT

46

Incorrect examples:

Continuation record missing "VERICUT-TC":

PPRINT/VERICUT-TC XCUT,PTS,0,0,.5,0,ARC,$

PPRINT/1,0,.5,PTS,1,.5,1,1,0,1

The word "ARC" split between lines:

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

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

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

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

PPRINT/VERICUT-COMMAND reverse


47/49

Automating VERICUT

47

VERICUT-TOOLID record

Special comment records that specify the ID of a tool to use from a VERICUT ToolLibrary file. This record is acted on only when VERICUT is configured to retrieve toolsfrom a Tool Library, for example: Tool Change By in the NC Programs window set to:"Tool Number". See the VERICUT Help section, in the CGTech Help Library, foradditional information.


Examples of use:

Use tool in the library having ID #100002:

APT/CLS — PPRINT/VERICUT-TOOLID 100002

G-code (Fanuc) — (VERICUT-TOOLID 100002)


48/49

Automating VERICUT

48

VERICUT-USERTAG record

Special comment record that enables specifying User-Defined Tag values, for use in aVERICUT report, from within the toolpath file. The general format isPPRINT/VERICUT-USERTAG "tagname"="tagvalue", for APT or CLS tool paths, or(VERICUT-USERTAG "tagname"="tagvalue") for G-code tool paths. For additionalinformation on User-Defined Tag values and VERICUT reports, see the VERICUT Help section in the CGTech Help Library.

Examples of use:

Use to specify the value for a "Text" type User-Defined Tag:

PPRINT/VERICUT-USERTAG "text_entry"="This is the text that will appear in theVERICUT report.")

(VERICUT-USERTAG "text_entry"="This is the text that will appear in theVERICUT report.")

where text_entry is the User-Defined Tag name, and "This is the text that will appear inthe VERICUT report.", is what will be written out in the report. (see Using PPRINT infofrom an NC program in a report, in the Using VERICUT section, in the CGTech Help Library, for additional information)

Use to specify the value for a "Table" type User-Defined Tag:

PPRINT/VERICUT-USERTAG "table_name"=" /path/filename")

(VERICUT-USERTAG "table_name"=" /path/filename")

where table_name is the User-Defined Tag name, and /path/filename represents the pathand file name of the text file containing the data for the table.

See Using data from a file in a report, in the Using VERICUT section, in the CGTech Help Library, for additional information.

NOTE: See VERICUT-BEGINTABLE record and VERICUT-ENDTABLE record forinformation on populating a table in a VERICUT report using the PPRINT statements inthe toolpath file.

Use to specify the value for a "Picture From File" type User-Defined Tag:

PPRINT/VERICUT-USERTAG " picture"=" /path/filename")

(VERICUT-USERTAG " picture"=" /path/filename")

where picture is the User-Defined Tag name, and /path/filename represents the path andfile name of the image file containing picture for the report.


49/49

Automating VERICUT

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

Automating Vericut

Documents

Transcript of Automating Vericut