3DEXPERIENCE-to-Vericut Interface (3dxml)
3DEXPERIENCE-to-Vericut Interface (3dxml)¶
Overview CATV6_3dx is an interface that facilitates the transfer of Fixture, Stock, Design, and 3D tool representations from the 3DEXPERIENCE manufacturing process to Vericut.
Available Interfaces: Vericut provides two interfaces for 3DEXPERIENCE:
CATV6_3dx: Standard interface for direct data transfer
CATV6_3dxml: Alternative interface for 3DXML-based data transfer
Software Requirements: CATV6_3dxml Interface¶
Licensing Requirements
CGTech Licensing:
CATIA V6 Interface
Installation & Configuration: CATV6_3dxml Interface¶
User Configuration
No manual configuration required
The interface is pre-configured for seamless operation.
Installation Path
The interface installation files are located at:
C:\Program Files\CGTech\Vericut x.x.x\windows64\CATV6_3dxml
To access version details, use:
C:\Program Files\CGTech\Vericut x.x.x\windows64\commands\catv6_3dxml_version.bat
Environment variables: CATV6_3dxml Interface
¶
To enable the 3DEXPERIENCE 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
CATV_LANGUAGE (Optional)
Purpose: Allows the interface to use a localized language file instead of US English.
Note: The application also provides the option to change the language directly from within the user interface but the path to the language local files must be set when using any other language then English.
Available Languages: French, German, Italian, Portuguese, Chinese, Japanese.
Example For Vericut 9.7, set to:
C:\Program Files\CGTech\Vericut 9.7\windows64\CATV6_3dx\CatvFrench.local
How to add an icon to the 3DEXPERIENCE Toolbar:
CATV6_3dxml Interface¶
1. Copy the icon file from the Vericut installation path to where 3DEXPERIENCE expects to find it. The paths depend on where you have 3DEXPERIENCE installed, but typically you will find a large folder under:
C:\Program Files\Dassault Systemes\B424_Cloud\win_b64\resources\graphic\icons
Copy from:
2. Get 3DEXPERIENCE running.
3. Open a Manufacturing file
4. Pick Tools > Macro 
5. In the Macros dialog, pick Macro Libraries.
6. In the Macro Libraries dialog, set the Library type to PLM Directories.
7. Pick Create new library from files and select the folder containing the CATV6.CATScript file. (For example, C:\Program Files\CGTech\Vericut xxx\windows64\catv6_3dx).
8. Close the Macro Libraries dialog.
9. Close the Macros dialog.
10. Pick Tools > Action Bar Customization, then right click in the Menu Bar and pick Add Commands…
11. In the Customize dialog, ensure the Commands tab is to the front.
12. Select Macros from the left-hand list of Categories.
13. Pick CATV.CATScript from the right-hand list of Commands.
14. Click on the Show Properties... button.
15. Pick the ... button to the right of the Icon: label.
16. In the Icon Browser dialog, set the filter to i_catv, then pick Vericut Icon 
and Close the Icon Browser.
17. Back on the Customize dialog, position the mouse cursor over the name of the macro, CATV6.CATScript, in the right-hand list, depress the left mouse button, and drag the cursor to the toolbar where you want the icon to appear. It's counterintuitive, but you drag the macro name, not the icon! Repeat this step if you want the icon to appear on more than one toolbar.
18. Close the Customize dialog.
19. From the toolbar, right click and pick Exit Customize Mode
Microsoft Redistributables: CATV6_3dxml Interface¶
The 3DEXPERIENCE-to-Vericut Interface (CATV6_3dxml) 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 3DEXPERIENCE 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: CATV6_3dxml Interface¶
Overview: The CATV6_3dxml interface exports manufacturing data from 3DEXPERIENCE 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 3DEXPERIENCE-to-Vericut Interface¶
To connect 3DEXPERIENCE with Vericut, follow these steps:
1. Alternately, Run the CATV6_3dxml batch file - Navigate to: C:\Program Files\CGTech\Vericut x.x.x\windows64\commands\catv6_3dxml_20xx.bat - Execute the file to initiate the interface.
2. Alternately, you can use the Vericut Icon - Click on the Vericut icon to launch the interface.
Important Note: The CATV6_3dxml interface requires an active NC Manufacturing file to function properly with Vericut. If the CATV6_3dxml Interface is launched and 3DEXPERIENCE is not running, The CATV6_3dxml Interface will ask if you wish to start 3DEXPERIENCE.
When you trigger CATV6_3dxml, you should see a window similar to this:
Note: The Interface Checks Out a license when the Interface is opened and then the Interface Checks In the license when the Interface is closed
Project Settings¶
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.
The files generated by CATV6_3dxml are intended to be "add-ons" for existing Vericut projects that contain much more detail than is present in a PPR context. For example, you may have a machine and control fully specified in a project file, and simply wish to place the PPR 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.
If you wish to append the part operations from a PPR context to the setups that are already defined in your project template, you can click on the Append to existing setups in project template check-box under the template field. Otherwise, and more typically, the imported part operations will be the only setups in the generated project.
Operations¶
This list contains the names of all the part Operations found in the PPR context. Typically, you would leave each Operation active so that they will all be simulated, but you could cause any of them to be skipped by un-checking their Active check box. When you select an Operation, most of the other elements of the interface will change to reflect the choices made for that Operation.
Setup Template¶
If all part operations in the PPR context use the same machine, and that machine is defined in the project template file, then the setup template field blank 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.
Models¶
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. For each attach component, a set of models can be specified via a 3DXML/CGR file. Also, for each attach component an Attach CSYS, Stock CSYS, Fixture Name, Stock Name and Design Name can be specified.
A 3DXML/CGR file can be exported from DELMIA 3DEXPERIECE. Type the 3DXML/CGR file, or use the \"Browse\" button to display a file selection window to select the 3DXML/CGR file. After specifying the 3DXML/CGR file, press the Load button to read the 3DXML/CGR file and display the 3DXML/CGR file hierarchy in the tree view. The user can set a tree item to a stock 
, fixture
, design 
, tool 
, holder 
, or undefined 
by selecting it from the right mouse button popup menu.
This will also set all its descendants to the same type. During the load process, CATV6_3DXML will attempt to identify the items in the tree view with the tools used in the 3DEXPERIENCE > Activities Process Tree. If tool is identified, then the tree item icon is changed from undefined item to a tool item . CATV6_3DXML will only process items from the tree that are set to stock, fixture, design, tool, and holder. In order for a tool's holder 
to be processed, its tool item must also be set.
By identifying the tool in the tree view allows CATV6_3DXML to correlate it with the tool in the 3DEXPERIENCE Activities Process Tree.
By setting a tree view item to undefined will tell CATV6_3DXML not to process that tree item. Tree view items that have 3D model data associated with are displayed in blue.
Attach CSYS is the CATIA/DELMIA coordinate system that is associated with the Vericut Attach Component. If Stock CSYS is specified, then the relationship between the Attach CSYS and the Stock CSYS is used for transitioning between Vericut setups, else the relationship between the current Attach CSYS and the Attach CSYS from the first operation is used. 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.
Tooling¶
Select one of the following options from the pull-down list:
Generate Tools from CATIA/DELMIA information — Choose this option to have CATIA/DELMIA create a tool library using the tool data in CATIA/DELMIA.
• Use Selected Tool Library — Choose this option to specify a specific tool library to use. Enter the \path\filename of the tool library file in the text field or use the Browse button to display a file selection window and use it to specify the \path\filename of the tool library file.
• Use Tools from the Setup Template — Choose this option to use the tool library file stored in the Setup Template instead of one created by CATV6_3DXML.
• Merge Tools into Setup Template Tool Library — Choose this option to merge the tool library created by CATV6_3DXML, with the tool library file stored in the Setup Template, and use the "merged" tool library rather than one created by CATV6_3DXML.
If Use Selected Tool Library is selected, then type the tool library name in the text field or use the "Browse" button to display a file selection window to select the tool library file.
NC Programs¶
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.
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.
Coordinate Systems¶
The Coordinate Systems list allows for the definition of a coordinate system that defines the relationship between an Attach Axis System and the NC Program Origin. Use the Add button to create a new coordinate system. A default coordinate system Name is assigned when created and can be changed and must be unique. The Attach Component is the Vericut component in which the coordinate system will be attached to. The Attach Axis System and the NC Program Origin are 3DEXPERIENCE/DELMIA Axis Systems of the current PPR. Use the Delete button to delete a coordinate system.
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. The ‘From’ Component is a Vericut component. The ‘To’ CSYS is a coordinate system defined in the Coordinate Systems list.
Format Settings¶
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 Tool ID Method to define how the tool IDs are generated. Typically, Number and Name are used for milling and Assembly Name is used for turning.
Generate buttons¶
CATV6_3dxml is not aware when you switch between PPR contexts. The Update button forces CATV6_3dxml to refresh the interface content from the currently active PPR. If a PPR context does not exist in the current session of 3DEXPERIENCE/DELMIA, then the program will display a warning message.
When you have provided CATV6_3dxml with all the information it needs, you can perform the transfer of data to, and triggering of, Vericut. Click on the "Generate files" button to create the tool libraries, models and NC programs without triggering Vericut. Once you have all the files needed, you can fire up Vericut with the "Run Vericut" button. You can perform both of these steps at once with the "Generate and run" button. The "Exit" button terminates the program.
Preferences
¶
Also known as 'prefs' file, stores all user specified 'global' settings for interface operation. The settings stored are called 'global' because they are responsible for overall look & feel and operational behavior of the interface. They are not tied to any specific 3dx project. By default, 'Preferences' file is generated at C:\Users\username\catv6_3dxml_user.prefs
Custom Data
¶
CATV6 uses a custom data file to store all user settings. The name of the custom data file is the active 3DEXPERIENCE/DELMIA PPR name with the extension ".CatvCustomData.".
The custom data file is written to the directory:
C:\Users\username\AppData\Roaming\CGTech\catv6_3dxml_version.
The custom data file is read when CATV6_3dxml is launched and written when CATV6_3dxml is exited.