GibbsCAM-to-Vericut Interface (GibbsV)¶

Overview
GibbsV is a licensed software tool that facilitates the seamless transfer of manufacturing data from GibbsCAM to Vericut

Software Requirements for GibbsCAM Interface¶

Licensing Requirements CGTech Licensing:
GibbsCAM Interface

Installation & Configuration: GibbsCAM Interface¶

Using an Installer
¶

To install the GibbsCAM-to-Vericut Interface (GibbsV), download the latest Vericut Software Release and run the gibbscam_interface_install.exe, then follow the step-by-step prompts to complete the installation.

You can download the installer from the Vericut website:
Request Latest Vericut Software Release

Environment variables: GibbsCAM Interface
¶

To enable the GibbsCAM Interface to locate the necessary Vericut files, the following environment variables must be defined:

Environment Variables: Description & Example
CGTECH_INSTALL
Purpose: Defines the Vericut installation folder.
Example: For Vericut 9.7, set to: C:\Program Files\CGTech\Vericut 9.7

CGTECH_PRODUCTS
Purpose: Specifies the folder for the operating system running Vericut (windows64).
Example: For Vericut 9.7, set to:
C:\Program Files\CGTech\Vericut 9.7\windows64

LSHOST
Purpose: Defines the name of the license server computer.
Example: localhost

CGTECH_SINGLE_PLATFORM (Optional)
Purpose: Specifies if Vericut is running on a single platform.
Example: CGTECH_SINGLE_PLATFORM=YES

GIBBSV_LANGUAGE (Optional)
Purpose: If you want the interface to use something other than US English, the variable can specify the path and file name of localized text file. If the GIBBSV_LANGUAGE environment variable is set, then it will use that as the default language. If the user interactively changes the language in the GUI, then the newly selected language file is searched for in the same directory defined in the GIBBSV_LANGUAGE environment variable. If the GIBBSV_LANGUAGE is not defined, then the language file is searched for in the "GibbsV" subdirectory under the install directory.
Note: The application also provides the option to change the language directly from within the user interface.
Available Languages: French, German, Italian, Chinese, and Japanese.
Example For Vericut 9.7, set to:
C:\Program Files\CGTech\Vericut 9.7\windows64\GibbsV\version\GibbsvJapanese.local

GIBBSV_USE_TOOL_NUM (Optional)
Purpose: If GIBBSV_USE_TOOL_NUM=NO or not defined, then CGV will create tool ID's based on the "TGx_y" format and creates a tool list. This is the default behavior. If GIBBSV_USE_TOOL_NUM is set to YES, then CGV will create tool ID's based on the tool number and not create a tool list.
Example: GIBBSV_USE_TOOL_NUM=YES

Set up a Vericut icon: GibbsCAM Interface¶

To add an icon to the Toolbar

If you wish to add the Vericut icon to the GibbsCAM toolbar…

1. From the GibbsCAM Toolbar, right click and select Customize Toolbar & Menus
   

2. Select the Vericut command, then drag and drop it onto the GibbsCAM Toolbar.
   
   

3. Close the Customize Toolbar & Menus window

Microsoft Redistributables: GibbsCAM Interface¶

The GibbsCAM-to-Vericut Interface (GCV) may require the installation of Microsoft Redistributables, specifically the Windows C++ run-time libraries. These libraries ensure compatibility and proper functioning of the interface, allowing seamless data transfer between GibbsCAM and Vericut for manufacturing simulation.

Note: A runtime library is a collection of low-level compiler support routines and functions that are used by virtually all programs compiled with GCC (GNU Compiler Collection) and can be downloaded here.

Documentation: GibbsCAM Interface¶

Overview: The GibbsCAM interface exports manufacturing data from GibbsCAM to Vericut, ensuring a seamless transition for simulation. It automatically configures the necessary Vericut setup requirements and launches the simulation, ready to play.

Vericut Simulation Setup Requirements: To run a successful simulation in Vericut, the following steps must be completed:

1. Select a VMC (Vericut Machine Configuration) – Define the machine setup for simulation.

2. Select and Orient Stock, Fixture, and Design Models – Ensure correct positioning of components.

3. Select NC Programs & Subroutines – Load the necessary machining programs.

4. Define Cutting Tools – Specify the tools used in the machining process.

5. Define Work Offsets Tables – Configure coordinate systems for accurate machining.

Accessing the GibbsCAM-to-Vericut Interface¶

To connect GibbsCAM with Vericut, follow these steps:
The Interface is activated by clicking Vericut icon

Important Note: The GibbsCAM interface requires an active NC Manufacturing file to function properly with Vericut.

When you trigger GibbsV, you should see a window similar to this:

License Handling
- The interface checks out a license when Generate, Run, or Generate & Run is executed.
- The interface checks in the license upon completion of data export.

Project Settings¶

GibbsV will generate several files to pass GibbsCAM information to Vericut. For verification or simulation of one GibbsCAM part file, the following can be created; - Vericut template file (*.VcTmp) - Vericut Tool libraries (*.tls) - Vericut Operation file (*.ops) - Model files (*.stl and *.ply)

The Output Directory specifies the directory where you want the Vericut files to be written (.VcTemp, .tls, .ops, .ply, .stl). Type the Output Directory, or use the "Browse" button to display a file selection window to select the path. The File Name specifies the "base" name for all Vericut files that will be created. Type the File Name, or use the "Use Part Name" button to auto-fill the GibbsCAM part name.

The files generated by GibbsV are intended to be "add-ons" for existing Vericut projects that contain much more detail than is present in a GibbsCAM part file. For example, you may have a machine and control fully specified in a project file, and simply wish to place the GibbsCAM part stock and fixtures on this machine before verifying the new NC programs. In this field you can specify the Project Template file. Type the Project Template, or use the "Browse" button to display a file selection window to select the Vericut project template.

Setup Template¶

If all GibbsCAM part information use the same machine, and that machine is defined in the project template file, then the setup template field can be left 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.

Workpiece Settings¶

The attach components are read from the machine file that is specified in the project template (or from the machine file specified in the setup template if defined) and presented in a pull-down list called Attach Component. All attach components are active by default. The user can prohibit an attach component from being processed by unchecking the Active check box.

For each attach component, a workpiece, an attach axis system, component names and work groups can be specified.

The Workpiece is the GibbsCAM part that is associated with the Vericut Attach Component.

The Attach Axis System is the GibbsCAM coordinate system that is associated with the Vericut Attach Component.

By default, the fixture, stock and design components will be named "Fixture," "Stock," and "Design" in Vericut. These defaults can be overridden by specifying a fixture, stock or design Name.

The fixture, stock and design WG Override specifies the work group geometry to be used for the fixture, stock and design model respectively instead of the default definition.

If you wish to transfer only the initial stock and the fixture and design models associated with it and ignore all other models, then you can click on the Initial Stock Only check-box.

The fixture, stock and design Import toggles allows the user to import or not import models for a corresponding component.

Model Type Assignment Logic

• Fixture and Design Models: If the WG Override field is not defined, GCV will first reference the Properties window to determine the model type.
  

• Stock Models: If the WG Override field is not defined, GCV will first reference the Properties window to determine the model type.
  

• If the model type is not found in the Properties window, GCV will then check the Document Control dialog.
  

• Body Bag handeling: Models placed in the Body Bag will be excluded from output. This function is used to remove unwanted or inactive models from the export process.

Attach Axis System Requirements

• The Attach Axis System must be a GibbsCAM coordinate system that mirrors the XY Plane. You can define this using the Coordinate System Palette.
  

• In GibbsCAM, the Vericut Attach coordinate system is automatically aligned with the position of the Vericut Attach component.
  

Tool Path Settings¶

Specify whether the NC programs to be passed to Vericut are APT or G-Code. Use the "Add" button to browse for and add a tool path to the list. Use the "Delete" button to delete a tool path from the list. It is important to ensure that the list is in the order of cutting.

Use the Post-process feature to create new .ncf files from the GibbsCAM part file. Designate an optional output directory for posted G code files.

Note: Preference file includes the "*.post" to GibbsVPostFilter tag as part of the default setting.

Tooling¶

Select tool library information:

• Select Generate Tools from GibbsCAM information if you want Vericut to use the tool library file created by GibbsV.

• Select Use Selected Tool Library if you want Vericut to use an existing tool library file

• Select 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 GibbsV.

• Select Merge Tools into Setup Template Tool Library if you want Vericut to merge the tool library created by GibbsV, with the tool library file stored in the Setup Template, and use the \"merged\" tool library rather than one created by GibbsV.

For each Tool Group, you can specify the tool group type of Spindle, Turret, or Gang Tool, and you can specify the Subsystem ID. If Turret is selected, then you can select if Upper or Lower turret.

Select Tool ID information:

• Select Use Tool Group/Number if you want the tool ID to contain the tool group and tool number.

• Select Use Tool Number if you want the tool ID to contain the tool number only. A tool list will not be generated if this option is selected.

• Select Use Tool Comment if you want the tool ID to contain the tool comment only.

Note: GibbsV will use the first quoted string from the GibbsCAM Tool Comments as the Vericut Tool ID and set the Vericut Tool Change By feature to Tool Number.

Output Intermediate Tooling: If checked, then intermediate tooling will be output with the tool if it exist, else no intermediate tooling will be output with the tool.

Environment variable called GIBBSV_USE_TOOL_NUM:
If GIBBSV_USE_TOOL_NUM=NO or not defined, then CGV will create tool ID's based on the "TGx_y" format and creates a tool list. This is the default behavior.

If GIBBSV_USE_TOOL_NUM=YES, then CGV will create tool ID's based on the tool number and not create a tool list.

NC Subroutines¶

If you have G-Code programs that reference subroutines, you can use the "Add" button to browse for and add subroutine files to the list. Use the "Delete" button to delete subroutine files from the list.

Machine Settings¶

The Machine Settings list allows for the definition of work offsets which defines the relationship between the 'From' Component and the 'To' CSYS. Use the Add button to create a new work offset record.

Table name can be Program Zero, Work Offsets, or Base Work Offset. Set the appropriate Subsystem ID, Register Number and Subregister Number.

Select the 'From' Component that represents the "from" point for determining the program zero offset. Vericut will use the origin of the specified component. The default "From Component" is "tool".

Select the 'To' CSYS that represent the "to" point for determining the program zero offset. Vericut will use the origin of the specified GibbsCAM coordinate system.

Options¶

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

Use Output Model File Format to specify the file format of the model files. Choose either ASCII or Binary. NOTE: "Binary" Vericut polygon files are platform specific.

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

Gibbscam is a single setup product. If you wish to append the GibbsCAM part information 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. Otherwise, and more typically, the imported GibbsCAM part information will be the only setups in the generated project.

If you wish to transfer all GibbsCAM part coordinate systems to Vericut, then you can click on the Output All Coordinate Systems check-box.

The Application Language list allows for the selection of a native language.

CGTech Products allows you to change the directory used to launch Vericut from the interface. This directory is initialized by the CGTECH_PRODUCTS environment variable. The Product Launch allows you to select to launch the desired application, Vericut or Optimizer

Generate buttons¶

When you have provided GibbsV 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" button.

You can perform both of these steps at once with the "Generate and Run" button. The dialog can be closed by pressing the icon in the upper right hand corner of the dialog.

Preferences¶

Preferences File GibbsV uses a preference file to save/restore default settings. The preference file is named gibbsv_version_user.prefs. The file will be saved on the HOMEDRIVE in the HOMEPATH. The preference file is read during GibbsV startup and written during GibbsV closing. The File Selection Box (FSB) filters are not user modifiable via the interface. The file filter tags are stored in the preference file and can be modified by the user. By default, 'Preferences' file is generated at C:\Users\username\gibbsv_version_user.prefs

Custom Data¶

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 were when you saved the file.