CAD SetupInstallation Guide

SIEMENS
CAD Translators
Installation
Proprietary & Restricted Rights Notice
This software and related documentation are proprietary to Siemens Product Lifecycle Management
Software 2 (IL) Ltd. © 2018 Siemens Product Lifecycle Management Software 2 (IL) Ltd.
Trademarks
Siemens and the Siemens logo are registered trademarks of Siemens AG. Tecnomatix is a trademark
or registered trademark of Siemens Product Lifecycle Management Software Inc. or its subsidiaries
in the United States and in other countries. All other trademarks, registered trademarks, or service
marks belong to their respective holders.
2 CAD Translators Installation

Contents
Proprietary & Restricted Rights Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
CAD Translators Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

CAD Translators - Installation Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
CAD Setup Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Pro/E to JT Translator Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
CATIA V5 to JT Translator Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Teamcenter Visualization License Server Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Tecnomatix/Robcad Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
CAD Translators Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

CAD Translators Convertors Setup . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Versions and Releases . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
COJT Translators . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
COJT Conversion Translators . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Application Options . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
CO Translators . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
CO Conversion Translators . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
TxConvert2co . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
NX Config File . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
TxJt2co . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
TxCatia2co . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
TxCo2Catia . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25
Additional JT Conversion Capabilities . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26
JT Mirror . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26
External ID Options . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26
Attribute Mapping . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29
Defining Naming Rules . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29
Appendix A: Multiple Instances of Robfacein . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35
Appendix B: Setup Features . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35
CAD Translators Installation 3

Chapter 1: CAD Translators Installation
1.1 CAD Translators - Installation Components

The CAD Translators installation is composed of five components:
• CAD Setup installation
• Pro/E to JT translator installation
• CATIA V5 to JT Translator Installation
• Teamcenter Visualization License Server installation
• Tecnomatix / Robcad installation
1.2 Licenses
The following licenses are needed for running the translators:
Required CAD
Translator Required Tecnomatix / Siemens PLM Software License
License
Access to CATIA
V5 needed:
Works with a
CATIA V5 HD2
TxCatia2co CAT5_IN Tecnomatix 14 FlexLM configuration.
Not all of the
licenses within
this configuration
are needed
Access to CATIA
V5 needed:
Works with a
CATIA V5 HD2
TxCo2catia CAT5_IN Tecnomatix 14 FlexLM configuration.
Not all of the
licenses within
this configuration
are needed
CAD Translators Installation 1-1

Chapter
Chapter 1: 1: CAD CAD Translators
Translators Installation
Installation
Basic license
forProE;
please refer to
TxConvert2co Teamcenter
proetojt-translator TC Visualization proetojt-translator
(ProE) Visualization
install guide
for further
instructions.
TxConvert2co NX License Basic license for

(NX) Server NX
TxJt2co
NX License Basic license for

TxNX2cojt
Server NX
Basic license
for ProE;
please refer to
Teamcenter
TxProE2cojt proetojt-translator proetojt-translator
Visualization
install guide
for further
instructions.
Please refer to
catiatojt-translator
Teamcenter
TxCatia2cojt catv5tojt_sca FlexLM install guide
Visualization
for further
instructions.
TxJt2cojt
Iges Teamcenter
TxIGES2Cojt FlexLM
_file_translator Visualization
Dxf Teamcenter
TxDXF2Cojt FlexLM
_file_translator Visualization
Teamcenter
TxSTEP2Cojt step_to_jt FlexLM
Visualization
The following import interfaces: TxCatia2co, TxConvert2co [NX/ProE], TxJt2co call Robfacein
automatically.
TxCo2catia calls Robfaceout automatically.
The license required for Robfacein /Robfaceout on Robcad is PRD_ROBFACE.
The license version is the same as that of Robcad.
1-2 CAD Translators Installation

CAD Translators Installation
1.3 CAD Setup Installation

The Setup automatically identifies and, if necessary, installs the following redistributable packages
which are required for some of the translators:
• MS .NET Framework 2.0 SP1
• MS Visual J# 2.0
• Microsoft Visual C++ 2012 Update 4 Redistributable Package (x64)
1. From the CAD Translators folder, run setup.exe. The InstallShield Wizard Welcome window is
displayed:
2. Click Next. The Destination Folder window is displayed:
3. Accept the indicated destination location or click Change to select a different location to install
the CAD translator files.

Chapter
Installation
4. Click Next. The Ready to Install window is displayed:
5. Click Install. The Installing CADTranslators window is displayed indicating the progress of
the installation:
When the installation is complete, the InstallShield Wizard Completed window is displayed:

CAD Translators Installation
6. Click Finish.
1.4 Pro/E to JT Translator Installation

The Siemens Pro/E to JT translator serves as the basis for translating Pro/E data for use in
Tecnomatix/Robcad applications.
The Pro/E to JT Translator setup is located in the 'JT Translator for ProE' folder of the CAD
Translators section on the Tecnomatix installation DVD.
1.5 CATIA V5 to JT Translator Installation

The Siemens CATIA V5 to JT translator serves as the basis for translating CATIA V5 data using
TxCatia2cojt, for use in Tecnomatix applications.
The CATIA to JT Translator setup is located in the 'JT Translator for CATIA' folder of the CAD
Translators section on the Tecnomatix installation DVD.
1.6 Teamcenter Visualization License Server Installation

The Teamcenter Visualization License Server is necessary for running the various CAD to JT
translators, specifically to license the Pro/E to JT translator and CATIA V5 to JT translator. It is not
required for the CATIA .CO interface (TxCatia2co, TxCo2catia).
Note: Before you can set up the license server, you must receive a license file from Siemens PLM
Software. Please refer to the specific installation guide of the relevant CAD to JT translator that
you are installing.

Chapter
Installation
1.7 Tecnomatix/Robcad Installation

In order to work with the CAD Translators, at least either a Tecnomatix or Robcad application must
exist on the machine, since running CAD Translators requires the existence of robfacein and
robfaceout on the machine.
Refer to the relevant installation instructions to set up Tecnomatix and Robcad applications.
1.8 Troubleshooting
If for any reason TxCatia2co or TxCo2catia does not work properly after installing CAD Translators,
verify that the redistributable packages were installed by checking in Start -> Control Panel ->
Programs and Features.
In case the redistributable packages were not installed, you must install them manually in the
following order:
1. MS .NET Framework 2.0 SP1, which you can find on the Tecnomatix installation DVD at the
following location:
CADTranslatorsx64\ISSetupPrerequisites\Microsoft .NET Framework 2.0 SP1
x64\NetFx20SP1_x64.exe
2. MS Visual J# 2.0, which you can find on the Tecnomatix installation DVD at the following location:
CADTranslatorsx64\ISSetupPrerequisites\Visual JSharp .NET Redistributable Package 2.0
x64\vjredist64.exe

Chapter 2: CAD Translators Reference
2.1 CAD Translators Convertors Setup

The CAD Translators Setup contains a set of CAD converters for CO and COJT formats. It is installed
independently and can be used for both Tecnomatix and Robcad PC product lines.
• COJT Translators:
o TxNx2cojt
o TxJt2cojt
o TxCatia2cojt
o TxProE2cojt
o TxSTEP2Cojt
o TxIGES2Cojt
o TxDXF2Cojt
• CO Translators:
o TxConvert2co (NX and Pro/E via jt)
o TxJt2co
o TxCatia2co
o TxCo2Catia
• TxNamingRules – Stand-alone GUI to set naming rules.
2.2 Versions and Releases

The CAD setup supports the following Tecnomatix versions:
• Tecnomatix: 11.1 to 14.1
• Robcad: 9.1, 11.0
CAD versions supported:

• NX8.5, NX9.0 (from this version: 64bit only), NX10, NX11
• CATIA V5: R21 to V5-6 R2016

Chapter
Translators Reference
Reference
• CATIA V4
• ProE: WildFire5, Creo Parametric 1.0, Creo Parametric 2.0
• IGES: 5.3
• STEP: AP203/AP214/AP242 formats
• DXF: up to AutoCAD 2014
• JT: up to 10.2
2.3 COJT Translators
2.3.1 COJT Conversion Translators

• TxNx2cojt
• TxJt2cojt
• TxCatia2cojt
• TxProE2cojt
• TxIGES2cojt
• TxSTEP2cojt
• TxDXF2cojt
NX, CATIA, Pro/E, DXF, IGES and STEP Translators

The COJT translator applications: TxNx2cojt, TxCatia2cojt, TxProE2cojt, TxIGES2cojt, TxSTEP2cojt
and TxDXF2cojt are command line applications for converting NX, CATIA, Pro/E, IGES, STEP and
DXF data files to .COJT components. The applications perform this conversion by first converting
the source file to a *.jt file, using the Siemens PLM Software NX, CATIA and Pro/E JT converters.
The applications then create .cojt components for the generated .jt Assembly or .jt parts and create
an XML allowing the hierarchy to be imported to the eMServer.
Successful conversions also create log files in the destination folder.
To run these applications, make sure that the relevant JT converter is installed on your computer
with the appropriate license.
Refer to the relevant JT converter manual for information about its settings, configurations and
capabilities.
Refer to the CAD Translators Installation Guide for information about installing the Siemens PLM
Software converters.
JT Translator

CAD Translators Reference
The TxJt2cojt application creates .COJT components for input .JT Assembly or .JT parts and creates
an XML allowing the hierarchy to be imported to the eMServer.
2.3.2 Application Options

The applications contain flags that enable you to select the input file, the destination location and
several optional flags to customize the output according to need.
Syntax
TxNx2cojt|TxCatia2cojt|TxProE2cojt|TxJt2cojt
|TxDXF2Cojt|TxIGES2cojt|TxSTEP2cojtfile-name
[-output<output-name>]
[-f<list-file>]
[-dir<directory-path>]
[-library<prototype_output_directory>]
[-l<log-file>]
[-dest<destination-path>]
[-keep]
[-assytree]
[-hierarchyTypeoneComp|monoSubAssy]
[-accumulateMatrices]
[-noXml]
[-extIdMod<1|2|3>]
[-emsClassdefaultResource|compoundClass;prototypeClass;instanceClass]
[-equipment]
[-applyNamingRules]
[-v<F|E|W>]
[-h|-?]
Parameters
Input file - for TxNx2cojt can be NX part or

assembly. For TxCatia2cojt can be CATIA part
<fileName> or assembly. For TxProE2cojt can be Pro/E
part or assembly. For TxJt2cojt can be JT part
or assembly.
The name of the end component, can be used

[-output]
only for a single input file.
Specifies a text file with a list of files (not

[-f]
relevant for TxJt2cojt).

Chapter
Reference
Name of the directory containing the parts (not

[-dir]
relevant for TxJt2cojt).
[-library] Specifies a destination folder for the prototypes.
[-l] The name of the output log.
[-dest] The destination for the components.
Specifies not to delete intermediate .JT files.

[-keep]
Not relevant for TxJt2cojt.
TxNx2cojt only: Specifies to generate the

assembly XML file by using the Assytree
[-assytree] functionality. The XML file is generated directly
from the source assembly file and not from the
.JT assembly file.
oneComp- Create monolithic JT file for the

whole assembly.
[-hierarchyType] monoSubAssy- Create monolithic JT file for
each sub-assembly.
The default is to keep the current hierarchy.
TxJt2cojt only: Generates only hierarchy files,

[-hierarchyOnly]
pointing to the .cojt files.
If the CAD has an assembly structure

in which there are transformations in the
subassemblies, then when this option is set,
the matrices are accumulated on the leaf nodes
of the JT-assembly and removed from the
subassembly nodes.
[-noXml] Specifies not to create XML file.
[-extIdMod] Sets the method to calculate external ID.
Allows you to import the hierarchy as resources

or as custom classes.
By Default: The hierarchy nodes are imported
as PmCompoundPart, PmPartPrototype,
[-emsClass
PmPartInstance.
defaultResource|compoundClass;
prototypeClass; instanceClass] As Resource: Applied when using
the -emsClass defaultResource option.
The hierarchy nodes are imported as:
PmCompoundResource, PmToolPrototype,
PmToolInstance.

As Custom Classes: Applied when using the

-emsClass option:
CustomCompoundClass;
CustomPrototypeClass; CustomInstanceClass.
Add userdefined class names to the
customization before performing the import.
Note: You should only add classes to the
customization when using the As Custom
Classes option. The classes already exist for
the By Default and As Resource options.
Creates an EquipmentPrototype compound

hierarchy. This option must be used in
conjunction with the -emsClass option. The
compoundClass parameter must be the
PmEquipmentPrototype class or a class that
inherits from it. The prototypeClass parameter
must be the PmToolPrototype or a class that
[-equipment] inherits from it (except PmEquipmentPrototype
or inheriting classes). The instanceClass can
only be PmToolInstance.
Example:
TxJt2cojt C:\CAD_DATA\JT\Cube.jt -emsClass
PmEquipmentPrototype; PmToolPrototype;
PmToolInstance -equipment
Apply defined naming rules to prototypes,

parts and their instances. If not supplied no
-applyNamingRules
naming rules will be applied and names will be
preserved the same as in the JT file
Sets the verbosity level for system messages

to be displayed during program execution.
F; only fatal severity messages are reported.
[-v] E; error and fatal severity messages are
reported.
W; warning, error, and fatal severity messages
are reported.
[-h or -?] Displays extended usage.
The COJT translators use intermediate JT files and therefore offer Additional JT Conversion
Capabilities.

Chapter
Reference
2.4 CO Translators
2.4.1 CO Conversion Translators

• TxConvert2co (NX, Pro/E and IGES via jt)
• TxJt2co
• TxCatia2co
• TxCo2Catia
NX, CATIA, JT and Pro/E Translators
The CO translator applications: TxConvert2co, TxJt2co and TxCatia2co are command line
applications for converting NX, CATIA, Pro/E and IGES data files to .CO components.
TxCo2Catia is a command line application for converting CO components to CATIA.
In order to run TxCatia2co and TxCo2Catia, CATIA V5 must be installed with a valid license.
2.4.2 TxConvert2co
The TxConvert2co translator is a command line application for converting NX, CATIA, Pro/E and
IGES data files to Robcad component (*.co) files. TxConvert2co performs this conversion by first
converting the source file to a *.jt file, using the Siemens PLM Software NX to JT, CATIA to JT or
Pro/E to JT, IGES to JT converters. TxConvert2co then converts the intermediate *.jt file to a Robcad
*.co file. In addition to the *.co file(s), successful conversion also creates the following files in the
destination folder: jt2co.log and TxConvert2co_timeStamp.log.
To run the TxConvert2co translator, make sure that the relevant converter (NX to JT, CATIA to JT or
Pro/E to JT) is installed on your computer with the appropriate license.
NX Converter
The NX converter is part of the installation of the NX CAD system. No further installation is required.
• Set the environment variable UGII_BASE_DIR to point to the NX base installation directory.
Pro/E Converter
1. Install Pro/E.
2. Install the Pro/E to JT converter.
Troubleshooting
• Using a text editor, open one of the following batch files: proeWF3tojt.bat, proeWF2tojt.bat,
proeWFtojt.bat, proe2001tojt.bat, depending on the version of Pro/E installed on your machine.
• Make sure that the PROE_DIR variable is set to the correct Pro/E installation directory. For
example: PROE_DIR=C:\Program Files\proeWildfire.

• In the PATH environment variable, the path to the installation of the Pro/E to JT converter must
come before the path to the installation of Pro/E.
Syntax
TxConvert2cofile-name
[-output<output-name>]
[-f<list-file>]
[-dir<directory-path>]
[-filter<filterTypefiltername>]
[-l<log-file>]
[[-t<tolerance>]|[-T<tolerance>]]
[-y<layer1[-layer2]>...-y<layerN[-layerM]>]
[-excludepoint|line]
[-noExplode]
[-approx|-exact]
[-dest<destination-path>]
[-hierarchyType<cell|superComp|oneComp|monoSubAssy>]
[-keep]
[-noXml]
[-extIdMod<1|2|3>]
[-equipment]
[-v<F|E|W>]
[-h|-?]
Parameters
Converts NX, Pro/E and IGES to CO via JT

TxConvert2co
format.
Input file - can be part or assembly of Pro/E or

<fileName>
NX and IGES data files.

Chapter
Reference
Specifies the name of the output file.

The name must conform to the naming
conventions of Tecnomatix, otherwise naming
rules are applied. By default, the output name
[-output output-name] is created from the input name by applying
naming rules.
Example:
TxConvert2co.exe C:\CAD_DATA\NX\Cube.prt
-output pedals
The name of the directory containing the parts

[-dir]
to be converted.
Destination of prototypes files. Default: the JT

source directory.
[-library <prototype_output_directory>] Example:
-library c:\mylibrary
[-f] Specifies text file with a list of files.
Specifies a CAD system filter - specify the type

[-filter]
of filter and its value.
Writes conversion information to the TxJt2co

log file.
[-l logfile] Example:
-l c:\temp\log.log
[-t] The relative tolerance value.
[-T] The absolute tolerance value.
[-y] For the layers option.
Determines whether to use approximate or

[-approx | -exact]
exact geometry.
The name of the destination folder for the

[-dest]
components.

cell - Keep original hierarchy and create cell

file.
superComp- Keep original hierarchy and
[-hierarchyType < cell | create Super component.
superComp | oneComp | monoSubAssy>] oneComp- Create a single component file for
the whole assembly.
monoSubAssy- Create a cell and component
files for each sub-assembly.
Do not delete intermediate *.jt files (RF file is

[-keep]
always deleted).
F: only fatal severity messages are reported.

E: error and fatal severity messages are
[-v F|E|W] reported.
W: warning, error, and fatal severity messages
are reported.
Specifies a type to exclude from the conversion

[-exclude]
(line or point).
Converts geometry as one block instead of

exploding it to blocks.
[-noExplode] Example:
TxConvert2co C:\CAD_DATA\NX\Cube.prt
-noExplode

subassembly nodes.
[-noXml] Prevents the creation of an XML file.

Chapter
Reference
Chooses the behavior for generating Ext-Id in

the XML:
1- Standard behavior (default) - application
generates unique ID
2 - PDM configuration - defines a special
attribute inside the JT which represents the
External-Id
[-extIdMod <1 |2 |3...>]
3 - Always unique - always generates a unique
ID (which is not persistent)
Example:
TxConvert2co C:\CAD_DATA\NX\Cube.prt
-extIdMod 2
See: External ID Options.

PmPartInstance.
As Resource: Applied when using the
-emsClass defaultResource option.
PmCompoundResource, PmToolPrototype,
[-emsClass PmToolInstance.
defaultResource|compoundClass;
prototypeClass; instanceClass] As Custom Classes: Applied when using the
-emsClass option:
Add user-defined class names to the


conjunction with the -emsClassoption. The
Example:
TxConvert2coC:\CAD_DATA\NX\Cube.prt
-emsClass PmEquipmentPrototype;
PmToolPrototype; PmToolInstance -equipment
The TxConvert2co translator uses intermediate JT files and therefore offers Additional JT Conversion
Capabilities .
2.4.3 NX Config File

The NX to JT converter that is called by TxConvert2co and TxNX2cojt has a configuration file that is
stored by default in the NX installation, for example:
C:\Program Files\Siemens\NX 9.0\PVTRANS\tessUG.config
Users can specify their own version of the config file in a location different to that of tess.UG.config
file using the following methods:
1. New copy named TxUG2co.config in the current working folder.
2. New copy in C:\Program Files\Tecnomatix\CADTranslators\dat\TxUG2co.config
3. Environment variable UGII_PV_TESS_CONFIG_FILE that specifies the full path and file name of
the configuration file.
4. Modify the file in its default location: C:\Program Files\Siemens\NX 9.0\PVTRANS\tessUG.config
5. New copy of TxUG2co.config in folder specified in environment variable Home.
The location of the configuration file is searched in the above order starting from 1.
Note
For users of NX11, the support path is located in: C:\Program Files\Siemens\NX
11.0\NXBIN. For users of previous NX versions the value remains UGII_ROOT_DIR.

Chapter
Reference
Note: The paths listed above (C:\Program Files\Siemens\NX 9.0 and C:\Program
Files\Tecnomatix\CADTranslators) are given as examples. Your installations may use different paths.
2.4.4 TxJt2co
TxJt2co translator converts .jt Assembly or .jt Part to Tecnomatix/Robcad objects. For Assembly it
creates an XML allowing the hierarchy to be imported to the eMServer. Geometry files can be copied
to .COJT folder or converted to .co.
The translator contains flags that enable you to select the .jt file for conversion, the destination
location and several optional flags to customize the output according to need.
Syntax
TxJt2cojt-file
[-outputoutput-name]
[-dest<destination>]
[-flistfile]
[-llogfile]
[-vF|E|W]
[-lod[0-1]]
[-keep]
[-approx|-exact]
[-noExplode]
[-noLine]
[-noPoint]
[-norfi]
[-noGenLod]
[-hierarchyType<cell|superComp|oneComp|monoSubAssy>]
[-hierarchyOnly]
[-noXml]
[-extIdMod<1|2|3...>](seedetailsforexplanation)
[-equipment]
[-h|-?]

Parameters
jt -file Specifies the .jt file to be converted.
Specifies the name of the output file.

The name must conform to the naming
conventions of Tecnomatix, otherwise naming
[-output output-name] is created from the input name by applying
naming rules.
Example:
TxJt2co.exe C:\ADJUSTABLE_PEDALS.jt
-output pedals
Specifies the output directory for hierarchy file.

Used also for prototypes except when using the
-library flag.
[-dest <destination>] By default, it is the location of the source file.

Example:
-dest c:\dest
Destination of prototypes files. Default: the JT

source directory.
[-library <prototype_output_directory>] Example:
-library c:\mylibrary
Specifies a file containing the names of the

[-f listfile]
input components.
Writes conversion information to the TxJt2co

log file.
[-l logfile] Example:
TxJt2co.exe C:\ADJUSTABLE_PEDALS.jt -l
c:\temp\log.log
F: only fatal severity messages are reported.

E: error and fatal severity messages are
[-v F|E|W] reported.
W: warning, error, and fatal severity messages
are reported.

Chapter
Reference
Determines the required level of details, set

value between 0.0 and 1.0.
Example:
TxJt2co.exe C:\ADJUSTABLE_PEDALS.jt -lod
1
A JT file may contain several LODs. When
converting from JT to CO using the -approx
flag, the system converts only one LOD to the
CO. The system determines which LOD to use
based on the -lod flag.
[-lod [0-1] ]
Use 1.0 to take the “best” LOD (this is the
default), which results in a highly accurate CO,
but also produces a larger file with a longer
conversion time.
Use 0.0 to take the “worst” LOD which results
in a less accurate CO, but produces a smaller
file and less conversion time.
Use a fraction between 0.0 and 1.0 to take an
LOD of corresponding accuracy, e.g., in a case
of five LODs, using 0.5 takes LOD3.
RF files created during the process will not be

deleted. By default, Rf files are deleted.
[-keep] Example:
-keep
Selects -approx to create .co files that contain

information by approximation only. Select
-exact to create .co files that contain the full
geometry (converted from JT-Brep or XT-Brep
formats).
[-approx | -exact]
Example:
TxJt2co C:\ADJUSTABLE_PEDALS.jt -approx
TxJt2co C:\ADJUSTABLE_PEDALS.jt -exact
Converts geometry as one block instead of

exploding it to blocks.
[-noExplode] Example:
TxJt2co C:\ADJUSTABLE_PEDALS.jt
-noExplode

Prevents the creation of .co files with lines,

in order to improve loading and Graphics
performance.
[-noLine]
Example:
TxJt2co C:\ADJUSTABLE_PEDALS.jt -noLine
Prevents the creation of.co files with points,

in order to improve loading and Graphics
performance.
[-noPoint]
Example:
TxJt2co C:\ADJUSTABLE_PEDALS.jt -noPoint
Converts the file to rf without actually generating

the components.
[-norfi]
Example:
TxJt2co C:\ADJUSTABLE_PEDALS.jt -norfi
[-noGenLod] Prevents the creation of Level Of Details.
Choose which hierarchy files will be created

during the process:
cell- Keep original hierarchy and create cell file
- default behavior.
supercomp- Keep original hierarchy and
create Super component.
[-hierarchyType < cell | superComp |
oneComp- Create a single component file for
oneComp | monoSubAssy>]
the whole assembly.
monoSubAssy- Create a cell and component
files for each sub-assembly.
Example:
-hierarchyType oneComp
Generates only hierarchy files.

Using this option with -cojt results in the 3D
data pointing to the .cojt file.
[-hierarchyOnly]
Example:
-hierarchyOnly

Chapter
Reference

subassembly nodes.
[-noXml] Prevents the creation of an XML file.
Choose the behavior for generating Ext-Id in

the XML:
1- Standard behavior (default) - application
generates unique ID
2 - PDM configuration - defines a special
attribute inside the JT which represents the
External-Id
[-extIdMod <1 |2 |3...>]
3 - Always unique - always generates a unique
ID (which is not persistent)
Example:
-extIdMod 2
See: External ID Options.

PmPartInstance.
As Resource: Applied when using the
-emsClass defaultResource option.
[-emsClass PmCompoundResource, PmToolPrototype,
defaultResource|compoundClass; PmToolInstance.
prototypeClass; instanceClass]
As Custom Classes: Applied when using the
-emsClassoption:
Add user-defined class names to the



conjunction with the -emsClassoption. The
Example:
TxJt2co C:\Assembly.jt -emsClass
PmEquipmentPrototype; PmToolPrototype;
PmToolInstance -equipment
[-h or -?] Displays help about the usage.
The TxJt2co translator offers Additional JT Conversion Capabilities.
2.4.5 TxCatia2co
2.4.5.1 TxCatia2co Import

TxCatia2co imports CATProducts and their objects: CATParts, CATIA V4 models and CGR from
CATIA V5 to Tecnomatix/Robcad applications. It also creates the XML allowing the hierarchy to be
imported into eMServer. You are required to enter the files to import using the following syntax:
Syntax
TxCatia2cocatia_file1[...<catia_fileN>]
[-output<output_filname1>[<output_filname2>...]]
[-outdir<output_directory>]
[-approx|exact]
[-approxTolerance<tolerance_val>]
[-exactTolerance<tolerance_val>]
[-bodyName<body1>[<body2>...]]
[-explode]
[-hierarchyOnly]
[-productToComp]
[-oneComp]
[-excludesolid|surface|curve|point|line|frame]

Chapter
Reference
[-nogroups]
[-superComponents]
[-log<logFileName>]
[-vf|e|w]
[-norfi]
[-cacheon|off]
[-includeBlankEntities]
[-EntityLevel]
[-h|-?]
Parameters
A CATIA V5 CATProduct or one of its objects,

<INPUTFILE>
i.e., CATParts, CATIA V4 models, CGR
Specifies the name for the output file (Comp

/ Cell). In case there is more than one input
file you can specify more than one output
[-output <output_filname1> name. The name must conform to the naming
[<output_filname2> ...]] conventions of Tecnomatix; otherwise naming
is created from the input name by applying
naming rules.
Specifies the output directory. By default, it is

[-outdir<output_directory>]
the location of the source file.
Specifies the prototype output directory.

Hierarchy file are created in the outdir
[-library <prototype_output_directory>]
directory.The libRoot-dest must be under the
lib_root folder.
Imports the file using the exact geometry.

By default, the system performs the import
using approximations. You can convert
CAD data using either Exact geometry or by
Approximation. Both options use tolerance -
the smaller the tolerance value used, the more
[-approx|exact] accurate the results of the import. However,
smaller tolerances also increase the time it
takes to complete the conversion and cause a
dramatic increase in the size of the resulting
data. The tolerance units are set according to
the Catia unit setting and the default tolerance
is 0.001mm.

[-approxTolerance<tolerance_val>] Sets the tolerance for the approximation.
[-exactTolerance<tolerance_val>] Sets the tolerance for the exact geometry.
[-bodyName <body1>[<body2>...]] Converts all bodies that are specified (only).
Explodes solid to faces. TxCatia2co converts

solids as solids, by default. However, you
[-explode] can select the Explode Solid to Faces option,
causing each solid to be converted as a group
of faces.
By default, CATProduct conversion

encompasses the product and all its children
(CATParts). The CATIA Interface converts the
Master CATProduct as a cell (.ce) and the parts
as components (.co). If you select the Import
Hierarchy Only option, the system only converts
the CATProduct, which is useful when you only
[-hierarchyOnly]
need to import the hierarchy to the eMServer,
without CATParts. To import a CATProduct to
the eMServer, click the XML tab, and select
the Create XML file option. An XML file is
created instead of the cell (.ce), which can be
imported to the eMServer. Using TxCatia2co
automatically creates the XML file.
Converts the hierarchy into a supercomponent

[-productToComp]
instead of generating a cell.
Converts the hierarchy into a single component

[-oneComp]
instead of generating a cell.
[-exclude
Excludes specific types from the conversion.
solid|surface|curve|point|line|frame]
Allows you to import the hierarchy as

resources or as custom classes. By
Default: The hierarchy nodes are imported
PmPartInstance As Resource: Applied when
[-emsClass using the option -emsClass defaultResource.
defaultResource|compoundClass; The hierarchy nodes are imported as:
prototypeClass; instanceClass] PmCompoundResource, PmToolPrototype,
PmToolInstance. As Custom Classes: Applied
when using the option:
-emsClass CustomCompoundClass;
CustomPrototypeClass;
CustomInstanceClass. Add user-defined

Chapter
Reference
class names to the customization before

performing the import.
Allows the creation of components without

[-nogroups] generating a hierarchy of the groups they
contain. The entity tree is then flat.
Generates a super component for each

sub-tree (CATProduct) in the root hierarchy.
* Any CATProduct file in the tree becomes
a super component. If there are more than
one instances of CATProduct only one super
component is created.
* The root node becomes a CELL except when
using -productToComp
* All the *.CATParts in the tree are converted
to Prototypes.
* Attribute: UGS_TX_LEVEL=CO:
[-superComponents] 1. This attribute is relevant only when it is
defined for *.CATProduct files.
2. This attribute is only activated when
-superComponents is activated. In a regular
conversion it is ignored.
3. A node with UGS_TX_LEVEL=CO becomes
one Comp.
4. All Super Components treat the oneComp
Nodes under them as leaf nodes.
5. When a node with the special attribute points
to another node with the attribute, the second
one is ignored.
The name for the conversion output log. The

[-log <logFileName>]
default is "outputName.log".

Sets the verbosity level for system messages

displayed during program execution.
F - only fatal severity messages are reported
[-v f|e|w] E- error and fatal severity messages are
reported.
W- warning, error, and fatal severity messages
are reported.
Converts the file to rf without actually generating

[-norfi]
the components.
Overrides Catia's settings and use|avoid using

[-cache on|off]
the cache.
Convert all Catia objects including those that

[-includeBlankEntities]
are invisible.
Includes detailed representation of component

in the resulting .jt in addition to united
[-EntityLevel]
representation. (Should be used only when
Tecnomatix 9.1 and up is installed).
Multiple Releases of CATIA

If you have installed more than one release of CATIA on your machine, TxCatia2co searches for
the latest CATIA release from the supported releases. For example, if the user has CATIA R21
and R22, TxCatia2co uses R22 and not R21.
Users can set different behavior by defining the following environment variables:
• UGS_TX_CATIA_DLL_PATH - the location of the CATIA dll path (usually in "C:\Program
Files\Dassault Systemes\B22\intel_a\code\bin")
• UGS_TX_CATIA2CO_DLL_PATH - the location of the converter dlls (e.g., C:\Program

Files\Tecnomatix\CadTranslators\Cat5_R22)
Important: CATIA and the converter dlls must be from the same release.
Color Conversion
Tecnomatix/Robcad applications currently support 20 colors while CATIA supports the RGB colors
mechanism (2563 options). As a result, CATIA V5 Interface only converts an approximation of
the original colors in CATIA.
Also, while CATIA enables colors on any face inside a solid, Tecnomatix/Robcad applications only
support the same color on the entire solid. When converting a solid that consists of faces with
different colors, the CATIA V5 Interface sets the color of the converted solid to one of the colors of the
faces (the first color encountered when traversing the solid). However, you can use the “Explode
Solid to Faces” option in order to set different colors to the faces of the solid.

Chapter
Reference
Custom Naming Rules

The application provides separate naming rules behavior depending on type:
1. Component file name on the file system
2. Super-Component /cell names
3. Instances
By default, the system uses the "cad_names.opt" file for all types. The location of the *.opt files
containing the naming rules description is: <TxCatia2Co Location>\dat. Use the naming rules
command to edit and add new naming rules files.
In order to set different rules for each type, create two new naming rules files, under the "<TxCatia2Co
Location>\dat" directory, which already contains the "cad_names.opt" file.
The following lists the naming rule files names and their behavior:
1. Component -generate names using "cad_name.opt" (the default file continues to provide
component names)
2. Super-component - generate names using "TxNameRuleSuComp.opt" which is also used for
Cell names
3. Instance - generate names using "TxNameRuleInst.opt"
Notes: Only these files can be used. Users can create and edit each of these files by using
the Naming rules tool. At runtime, TxCatia2co searches for these files, and reverts to the default
"cad_names.opt" file if it fails to find them. Naming rules are applied to both valid and invalid source
names.
Log Summary Script
Users can execute the TxCatia2coVB.vbs script to run TxCatia2Co to produce a list of files and write
the final results to a summary log file. In order to run the script, users must specify the following:
Cscript.exeTxCatia2coVB.vbs-log<summary-log-name>-f<params-file>
• Cscript.exe - a Windows command to run script in batch mode
• -log - the full path of the summary log
• -f - the name of the file that contains a list of command lines to TxCatia2co. Each line in the file
contains a full command line: Inputs and Options.
Return Code
The application returns the following meaningful return codes:
ReturnCode Description
0 Full success of the conversion
1 Partial success of the conversion
-1 Unknown error occurred during the conversion
-2 No license to CAD system

-3 No Tecnomatix license
-4 Error in opening input file
-5 Error in opening output file
-6 Error in reading the input file - may be corrupted
Error while writing output - may be a

-7
write-protection problem
-8 System environment is not set properly
-9 Input file type is not supported
-10 Command line is incorrect
Unknown error occurred while calling to

-11
external application
-100 Robfacein error - general error
-200 TxCatia2CO failed to traverse geometry
-201 TxCatia2CO failed to traverse hierarchy
TxCatia2CO - usually means no Catia license

-202
available
-203 TxCatia2CO - fatal error occurred
-204 TxCatia2CO - Robfacein partial success
Troubleshooting
After installing the CATIA V5, you may experience some of the following problems:
• The translator fails to load the CATIA environment.
• The translator fails to start the CATIA session.
• The translator fails to open the CATIA document.
Use the following checklist to eliminate further significant issues:

• Verify that the PATH environment variable does not include any path to the CATIA folder. For
example, C:\Program Files\Dassault Systemes|B14\intel_a\code\bin. The system identifies the
CATIA installation as it runs, and inclusion of such a path can cause a contradiction.
• Verify that the PATH environment variable includes the path to the CAD translators folder. For
example, C:\Program Files\Tecnomatix\CadTranslators
• If you changed the PATH, try to restart your machine.

Chapter
Reference
• Make sure that you are able to run the CATIA application. If this is not possible, verify that your
CATIA license is valid and available, and that CATIA is configured using the correct license
information.
• Verify that the file you are attempting to convert, and to load into CATIA, has valid data. To do
this, open CATIA and load the file you are trying to convert, to verify that it is valid.
• Make sure that you have a valid Tecnomatix license for the V5 interface: FEA_CAD_INFACE_V5
2.4.5.2 CATIA V4 Models

TxCatia2co converts v4 models (from the command line, or embedded in the CATProduct hierarchy)
into CGR, which is converted to Tecnomatix components with approximate geometry.
The process also creates a cshell script named <product name>.v4Models.csh, which specifies the
path of the models and the expected component name for each one. You can use this script on UNIX
in order to convert the models file to a component with exact geometry.
Note: The script includes Windows paths - replace these with the correct UNIX paths using an
additional UNIX script, V4models-postprocess.csh . that is provided.
2.4.5.3 Using the V4models-postprocess.csh

V4models-postprocess.csh<DOSoriginalpathprefix><Unixreplacementpathprefix>
<.v4modelsfilename>
The script processes each line in the .v4models.csh file, line after line serially, doing the following
(for every line):
• Replaces the DOS original path prefix with the Unix replacement path prefix.
• Turns path to Unix style (replacing all '\' with '/').
• Replaces the DOS new lines with Unix new lines.
The script actually modifies the .v4Models.csh file to run on Unix platform.
Notes :
The first parameter of the script is the DOS original path prefix. Instead of every backslash ('\'),
place two backslashes ('\\').
The second parameter of the script is the Unix replacement path prefix. Write this as a regular
Unix path (with slashes).
Example
.v4models.cshfilename:parts.v4models.csh
DOSoriginalpathprefix:C:\BUGS\
Unixreplacementpathprefix:/usr/staff/local/
parts.v4models.cshcontent:
catrob"C:\BUGS\Catia\UWE\63240sjaa001h1.model""C:\BUGS\Catia\UWE\comp3.co"-mirrorzx
catrob"C:\BUGS\Catia\UWE\63142sja_a000__.model""C:\BUGS\Catia\UWE\comp1.co"

catrob"C:\BUGS\Catia\UWE\63219sda_a001h1.model""C:\BUGS\Catia\UWE\comp2.co"
Script execution:
V4models-postprocess.cshC:\\BUGS\\/usr/staff/local/parts.v4models.csh
After the execution, the parts.v4models.csh file contains the following:

catrob"/usr/staff/local/Catia/UWE/63240sjaa001h1.model""
/usr/staff/local/Catia/UWE/comp3.co"-mirrorzx
catrob"/usr/staff/local/Catia/UWE/63142sja_a000__.model""/usr
/staff/local/Catia/UWE/comp1.co"
catrob"/usr/staff/local/Catia/UWE/63219sda_a001h1.model""/usr
/staff/local/Catia/UWE/comp2.co"
2.4.6 TxCo2Catia
The TxCo2Catia translator is a command line application that converts Robcad cells or components
into CATIA V5 data files.
The exported data is an approximation; TxCo2Catia does not export exact data.
Requirements
You must install the following applications on your computer before running TxCo2Catia:
• Robcad
• CATIA V5R15 or higher (with license)
Output
The output of TxCo2Catia is composed of CATIA V5 files, (CATProduct and CGR) a log file, and
an optional robface (rf) file.
When performing a conversion, TxCo2Catia creates the *.CATProduct file, containing hierarchy
information, together with a log file and output folder and axissystems.cgr (this contains frames (axis
systems) created at the cell level but not belonging to a specific component; if there are no such
frames, the file is not created). TxCo2Catia writes all the CATIA V5 files to the output folder.
If the keep option is active, TxCo2Catia also creates a *.rf file.
By default, TxCo2Catia names the *.log, *.rf, *.CATProduct and the output file folder after the cell or
component it is converting.
Syntax
TxCo2Catia<comp/cell>
[-output<outputName>]
[-log<logfileName>]
[-dest<destinationFolder>]
[-keep]
[-h]

Chapter
Reference
Parameters
The name of the input cell or component to

[comp/cell]
convert.
[-output] Specifies the name of the output CATProduct.
[-log] Specifies the name of the logfile.
[-dest] Specify a destination folder for the output files.
[-keep] Saves the intermediate rf file.
[-h] Displays help about the usage.
Multiple Releases of CATIA

If you have installed more than one release of CATIA on your machine, TxCo2Catia searches for
the earliest CATIA release. For example, if the user has CATIA R21 and R22, TxCo2Catia uses
R21 and not R22.
Users can set different behavior by defining the following environment variables:
• UGS_TX_CATIA_DLL_PATH - the location of the CATIA dll path (usually in "C:\Program
Files\Dassault Systemes\B22\intel_a\code\bin")
• UGS_TX_CATIA2CO_DLL_PATH - the location of the converter dlls (e.g., C:\Program

Files\Tecnomatix\CadTranslators\Cat5_R22)
Important: CATIA and the converter dlls must be from the same release.
2.5 Additional JT Conversion Capabilities

2.5.1 JT Mirror
The PLMXML may have pairs of parts that point to the same .JT file, while their transformation
matrices are different, where one is defined in such a way that the geometry of the JT is mirrored
about a certain plane.
When translating JT assemblies, the translators automatically create mirrored JTs in order to allow
Process Designer to refer correctly to the mirrored parts.
JT Mirror also creates folders containing the mirrored .JT files. Both folder names and part names
include the jtmirror keyword. For example, the mirror result of adapterpalette.cojt, which contains
adapterplatte.jt, is:
adapterplattejtmirror.cojt containing adapterplattejtmirror.jt
2.5.2 External ID Options

1. standard (default behavior)
- This method always generates a valid XML that can be imported to eMServer.

- For the same hierarchy structure it always generates the same External-IDs for the same objects.
- Duplicate IDs are made unique by using an enumeration mechanism.
- When 1024 characters are exceeded, it shortens the name and makes it unique using the
same (or similar) enumeration mechanism.
- Updates only succeed only if:
• All object paths are unique
• External Id does not exceed 1024 character
a. External-ID for Prototypes

• External-ID = JT Geometry Path + file name (without .jt extension) of the geometry prototype
• e.g., "c:\Fender.jt" becomes: External-ID = "c:\Fender"
b. External-ID for Compounds

• External-ID = 'Main JT Assembly Private name' + 'object hierarchy path'.
• e.g., when the JT assembly is C:\myassembly.jt, the compound is:

"car->door->rightdoor->handle->housing"
• External-ID = "myassembly>car>door>rightdoor>handle>housing"
c. External-ID for Instances
• External-ID = 'JT Assembly Private name' + 'object hierarchy path'
• e.g., when the JT assembly is C:\myassembly.jt, the instance is:

"car->door->rightdoor->handle->housing>screw"
• External-ID = "myassembly> car>door>rightdoor>handle>housing >screw"
• For cases when such as external ID already exists: "myassembly>

car>door>rightdoor>handle>housing >screw_#number"
2. PDM configuration
• Use a special attribute: UGS_TX_EXTERNAL_ID that contains the External-ID as a string.
For example, NX users can add this attribute as follows:

Chapter
Reference
Other CAD applications offer similar means for adding the UGS_TX_EXTERNAL_ID attribute.
o Users are responsible for the value of the External-ID that converts data to JT.
o When a user sets an invalid values (duplicate IDs or IDs that exceeded 1024 characters),
the application does not change the IDs. Instead, it informs the user about the
problematic IDs in the log, and it changes the name of the xml to outputName_invalid.xml,
to alert the user that the output xml is incorrect.
JT Node Attributes
A JT attribute is actually defined as a JtKProperty object.
A JtKProperty node can contain four types of attributes:
• JtkPUBLIC_SHARED - Designates a property that is visible among all instances of a
JtkAssembly or JtkPart. This is the default for all properties.
• JtkHIDDEN_SHARED - Designates a property that is associated with, but not visible from,
all instances of a JtkAssembly or JtkPart.
• JtkPUBLIC_INSTANCE - Designates a property that is visible only from the JtkAssembly,

JtkInstance, or JtkPart on which it is placed.
• JtkHIDDEN_INSTANCE - Designates a property that is only associated with, but not visible
from, the JtkAssembly, JtkInstance, or JtkPart on which it is placed.
It is impossible to define an Instance attribute (JtkPUBLIC_INSTANCE or JtkHIDDEN_INSTANCE)

on the root node, because this node cannot be instantiated.
For this reason the method reads the Shared attribute of "UGS_TX_EXTERNAL_ID" for the root
node, while for all other nodes it reads the Instance attribute.

Although this method uses Shared attribute for the root node and Instance attribute for all other
nodes, it is necessary to define the "UGS_TX_EXTERNAL_ID" attribute as SHARED and as
INSTANCE (with the same value) for each node, for the following reasons:
• In order to use this method for a sub tree, each node must have a SHARED attribute so it
can be read as a root node.
• In order to use this method and use the root node as a sub-tree, the root node requires
an INSTANCE attribute.
3. Unique External-ID
This method generates a unique External ID for each node. While very safe, it does not allow
users to implement an update.
2.5.3 Attribute Mapping

Attributes from the JT assembly will be converted according to the cadAttr.map mapping file.
Attributes that are not listed in the mapping file are not converted.
The translator searches in four locations in the order listed below, and it uses the first cadAttr.map it
finds:
1. Current directory, from where the command was executed
2. HOME directory of the current user
3. dat directory under the CAD Translators installation (e.g., C:\Program

Files\Tecnomatix\CadTranslators\dat)
4. dat directory under the Tecnomatix installation (e.g., C:\Program Files\Tecnomatix\eMPower\dat)
The mapping file lists the name of each JT attribute, the name of the corresponding Robcad/eMServer
attribute, and YES or NO to specify whether or not to map the attribute. Each mapping occurs on a
separate line consisting of three white-space separated fields:
"CAD ATTRIBUTE" ROBCAD_ATTRIBUTE YES | NO
The quotation marks are optional; they are needed only if a CAD attribute has more than one word.
The third field is YES to use the mapping; NO has the effect of commenting out the line.
2.6 Defining Naming Rules

The Naming Rules module dialog provides a mechanism for translating the names of entities or
components that have been imported to a valid Tecnomatix name. For example, any imported
component whose name begins with a digit (such as, 123.prt) or is more than 30 characters in length
must have its name translated before it can be used by Tecnomatix/Robcad applications. Naming
rules are used to define how these translations are made. A number of predefined rules are provided,
but others can be defined as needed.
The following table lists the predefined rules that cannot be changed.

Chapter
Reference
Replace With
'[\/\+-]'
<REMOVE-EXT> AnyExtension
'[^a-zA-Z0-9_]' _(underscore)
<INVALID-FIRST> r
<FIRST-30>
<UPPER-CASE>
The following table lists the predefined rules that can be changed.
Replace With
space _(underscore)
- _(underscore)
/ _(underscore)
.prt
.model
.library
.asm

All naming rules, whether predefined or customized, must be contained in a single file, which must be
named cad_names.opt. When a CAD translator encounters a component possessing an invalid
name, it applies the rules in cad_names.opt sequentially, replacing the invalid name with a valid
name.
The cad_names.opt searches in the following order:
1. current folder
2. home directory
3. Install dir/dat
Notes:
• cad_names.opt must appear in one of the directories specified above.
• There are two separate cad_names.opt files - one under the installation of the CAD Translators
and one under the Tecnomatix applications installation. The former only applies to the
applications in the CAD Translators. All other Tecnomatix applications (for example, cadlink)
use the file under the Tecnomatix installation.
To define naming rules:

The naming rules UI is available from the command line:
• Under the installation of Tecnomatix - type NamingRules.exe.
• Under the CAD setup - type TxNamingRules.exe.

Chapter
Reference
Usage
1. Click the Browse button to the right of the Rules file field and select the location of the
cad_names.opt file, which contains the naming rules.
2. Use the following steps according to need:

• To add a new rule, enter the string to be replaced in the Replace field, and then enter the
translation in the With field. Click Add.
• To modify an existing rule, select it from the list and enter a new translation in the With
field. Click Replace.
• To delete a rule, select it from the list and click Delete. Click Delete All to remove all
naming rules.
• Use the Up and Down arrows to re-order the rules. When the system encounters an invalid
name, it processes the list of rules in order until it finds the first one that is applicable.
3. To add a special rule to the list, select it from the Special Rule dropdown list and then click
Add. Refer to Special Naming Rules below.
Special Naming Rules
The Naming Rule Settings dialog box contains a list of special naming rules you can add to the
cad_names.opt file. You select these rules from the Special Rule dropdown list. Certain special
naming rules open an additional dialog that allows you to further define the details of the rule, as
described in the table below.
Special Naming Rule Description
Converts the entire name from uppercase to

Convert uppercase to lowercase
lowercase.
Uses the first 15-30 characters of the

component name.
Use first x characters only
Uses the last 15-30 characters of the

component name.
Use last x characters only

If invalid, replaces the first character in the

component name with a user defined string.
For example, if the user defined string is ‘r’,
123.prt is converted to r23.prt.
Replace first character if invalid
If invalid, prepends a user defined string to the

first character in the component name. For
example, if the user defined string is ‘r’, 123.prt
is converted to r123.prt.
Prepend to first character if invalid
Replaces all the characters between two

positions in the name with a predefined string.
These parameters are defined in the Special
Rules dialog box after clicking Add in the
Naming Rule Settings dialog.
Replace substring from index to index
In the example above, a component with the

name this_is_my_original_string.prt
would have its name translated to
this_is_my_new_string.prt. This is
because characters 9 through 26 in the old
name are translated to the string defined in the
New string field.
Note: The length of the new string does not
need to match the number of characters being
replaced.

Chapter
Reference
Translates invalid component names according

to rules defined in a special text file. Typically,
this option is used in place of all other naming
rules.
The naming rules script must be named
Naming rule script
renamePartToComp, with a file extension
of .csh for Unix systens or .bat for Windows
systems, including robcad_pc.
Note: The path lookup order for this option is
the same as cad_names.opt.
Substitutes a predefined string for any

component name, or part of a name, that
matches the defined expression.
Regular expression match/replace rule
In the above example, all strings with lowercase

letters that start with the letter x will be replaced
with new_string.
Extracts a substring from a specified string and

inserts it into a component name at a specified
location.
Insert substring
The example above specifies that

%PARTNAME% will be extracted in its
entirety and appended to the end of the
component name.
Note: the example uses macros to define the
substring and indices to be used. You may
manually enter the substring and indices if you
wish.

Removes a specified extension from the end of

a name string. You can enter the value “Any
Extension” if you want to remove any extension
regardless of type.
Remove extension
Note: If the value is left blank the value “Any

Extension” is automatically applied.
2.7 Appendix A: Multiple Instances of Robfacein

In most installations, only one instance of Robfacein is installed on a machine. In the following
exceptional cases, a multiple installation of Robfacein may exist:
• Both Tecnomatix and Robcad are installed
• A number of versions of Robcad are installed
As Robfacein is version-dependent, using the incorrect version of Robfacein results in a different

component. The user, therefore, requires a method to determine which version of Robfacein is used.
To solve this problem, the new UGS_TX_ROBFACE_PATH environment variable is used. It stores
the path to the relevant instance of Robfacein.
• The same variable is used for both Robfacein and Robfaceout. Therefore, it must store the path
without the application name (e.g., C:\Program Files\Tecnomatix\eMPower).
• The user is able to set this variable in the current shell or as a general variable on the machine.
• The user is able to run multiple sessions of an interface using different instances of Robfacein at
the same time, by setting different values in different shells.
• A user with a standard installation of either Tecnomatix or Robcad is not required to make any
configuration changes.
• The search order of the Robfacein instances is as follows:
1. The Robfacein instance which appears in the environment variable.

2. The first instance of Robfacein in the PATH.
2.8 Appendix B: Setup Features

• The default installation path is C:\Program Files\Tecnomatix\CADTranslators.

Chapter
Reference
• CAD Setup adds the CAD installation path to the machine's PATH variable.
• CAD Setup provides uninstall functionality.
• CAD Translators includes as add-on installation of ProE to Jt translator and installation of Catia to
Jt translator. This is needed in order to translate ProE and Catia V5 data to Tecnomatix / Robcad.

Siemens Industry Software
Headquarters
Europe
Granite Park One
Stephenson House
5800 Granite Parkway
Sir William Siemens Square
Suite 600
Frimley, Camberley
Plano, TX 75024
Surrey, GU16 8QD
USA
+44 (0) 1276 413200
+1 972 987 3000
Asia-Pacific
Americas
Suites 4301-4302, 43/F
Granite Park One
AIA Kowloon Tower, Landmark East
5800 Granite Parkway
100 How Ming Street
Suite 600
Kwun Tong, Kowloon
Plano, TX 75024
Hong Kong
USA
+852 2230 3308
+1 314 264 8499
About Siemens PLM Software
© 2018 Siemens Product Lifecycle Management

Siemens PLM Software, a business unit of the Siemens
Software Inc. Siemens and the Siemens logo are
Industry Automation Division, is a leading global provider
registered trademarks of Siemens AG. D-Cubed,
of product lifecycle management (PLM) software and
Femap, Geolus, GO PLM, I-deas, Insight, JT, NX,
services with 7 million licensed seats and 71,000 customers
Parasolid, Solid Edge, Teamcenter, Tecnomatix and
worldwide. Headquartered in Plano, Texas, Siemens
Velocity Series are trademarks or registered trademarks
PLM Software works collaboratively with companies
of Siemens Product Lifecycle Management Software
to deliver open solutions that help them turn more
Inc. or its subsidiaries in the United States and in other
ideas into successful products. For more information
countries. All other trademarks, registered trademarks
on Siemens PLM Software products and services, visit
or service marks belong to their respective holders.
www.siemens.com/plm.

CAD SetupInstallation Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CAD SetupInstallation Guide

Uploaded by

Copyright:

Available Formats

SIEMENS

2 CAD Translators Installation

Proprietary & Restricted Rights Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

CAD Translators Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

CAD Translators Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

CAD Translators Installation 3

1.1 CAD Translators - Installation Components

• Pro/E to JT translator installation

• CATIA V5 to JT Translator Installation

• Teamcenter Visualization License Server installation

• Tecnomatix / Robcad installation

CAD Translators Installation 1-1

TxConvert2co NX License Basic license for

NX License Basic license for

1-2 CAD Translators Installation

1.3 CAD Setup Installation

• Microsoft Visual C++ 2012 Update 4 Redistributable Package (x64)

2. Click Next. The Destination Folder window is displayed:

CAD Translators Installation 1-3

4. Click Next. The Ready to Install window is displayed:

1-4 CAD Translators Installation

1.4 Pro/E to JT Translator Installation

1.5 CATIA V5 to JT Translator Installation

1.6 Teamcenter Visualization License Server Installation

CAD Translators Installation 1-5

1.7 Tecnomatix/Robcad Installation

1-6 CAD Translators Installation

2.1 CAD Translators Convertors Setup

• TxNamingRules – Stand-alone GUI to set naming rules.

2.2 Versions and Releases

• Robcad: 9.1, 11.0

CAD versions supported:

• CATIA V5: R21 to V5-6 R2016

CAD Translators Installation 2-1

• ProE: WildFire5, Creo Parametric 1.0, Creo Parametric 2.0

• STEP: AP203/AP214/AP242 formats

• DXF: up to AutoCAD 2014

2.3 COJT Translators

2.3.1 COJT Conversion Translators

NX, CATIA, Pro/E, DXF, IGES and STEP Translators

2-2 CAD Translators Installation

2.3.2 Application Options

Input file - for TxNx2cojt can be NX part or

The name of the end component, can be used

Specifies a text file with a list of files (not

CAD Translators Installation 2-3

Name of the directory containing the parts (not

[-library] Specifies a destination folder for the prototypes.

[-l] The name of the output log.

[-dest] The destination for the components.

Specifies not to delete intermediate .JT files.

TxNx2cojt only: Specifies to generate the

oneComp- Create monolithic JT file for the

TxJt2cojt only: Generates only hierarchy files,

If the CAD has an assembly structure

[-noXml] Specifies not to create XML file.

[-extIdMod] Sets the method to calculate external ID.

Allows you to import the hierarchy as resources

2-4 CAD Translators Installation

As Custom Classes: Applied when using the

Creates an EquipmentPrototype compound

Apply defined naming rules to prototypes,

Sets the verbosity level for system messages