JT Catiav5 Help

SIEMENS
JT Bi-Directional
Translator for Catia
V5 13.0
User Assistance
Contents
JT Bi-directional translator for CATIA V5 13.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Using the translator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Translating Catia V5 files to JT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Translate CATIA V5 files to JT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Modifying Catia V5 to JT translator specific options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Modifying Catia V5 to JT general setup options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Modifying filter options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
Modifying level of detail options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25
Modifying metadata options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30
Translate CATIA V5 to JT files from the command prompt . . . . . . . . . . . . . . . . . . . . . . . 2-32
Sample configuration file – CATIA V5 to JT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33
Locate configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35
Translating JT files to Catia V5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35
Translate JT files to CATIA V5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35
Modifying JT to Catia translator specific options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36
Translate JT to CATIA V5 files from the command prompt . . . . . . . . . . . . . . . . . . . . . . . 2-40
Sample configuration file – JT to CATIA V5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41
Internationalized content in configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42
Using the interface to configure file translations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42
Using the interface to configure file translations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42
Working with the CATIA JT Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43
Working with operating system interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-51
Mapping entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60
Entity mapping for CATIA V5 to JT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60
Entity mapping for JT to CATIA V5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-62
Understanding the ASCII text file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-63
Understanding JT files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-65
Select a JT file version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-66
Customize text messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-67
Global Technical Access Center (GTAC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
JT Bi-Directional Translator for Catia V5 13.0 3

Chapter 1: JT Bi-directional translator for CATIA V5 13.0
JT Bi-directional translator for CATIA V5 13.0

You can use the JT Bi-directional Translator for CATIA V5 to translate CATIA V5 files to JT files
and JT files to CATIA V5 files.
You can convert CATProduct, CATParts, CGR, and CATShape files created in CATIA V5
worksessions to JT files by using the interface which is installed in CATIA V5, by using an interface
through the operating system, or by using command prompt options. To begin translating files you
can use the values set in the default configuration file or you edit the parameters. You can also set
parameter values from the command prompt.
You can also translate JT to CATIA V5 CATProduct and CATPart files by using command prompt
options. To begin translating these files you can use the values set in the default configuration
file or you can edit the parameters.
It is not mandatory to install CATIA CAD software to translate CATIA V5 parts and assemblies or JT
files. However, you do need a license for JT Bi-directional Translator for CATIA V5. For information
about obtaining licenses, contact your Siemens PLM Software distributor.
JT Import for CATIA V5
You can use JT Import for CATIA V5 to interactively import JT files into your CATIA V5 session. JT
Import for CATIA V5 features are supported only from the interface that is installed in CATIA V5.
You can insert JT files as CGR files into an existing CATProduct, and JT Import for CATIA V5 supports
tessellated data. If you also install the JT Bi-directional Translator for CATIA V5 application, you
extend the use of JT Import for CATIA V5 to insert or open JT files as CATProducts and CATParts. JT
Import then supports precise b-rep and assembly data.
Both JT Bi-directional Translator for CATIA V5 and JT Import for CATIA V5 are licensed separately by
Siemens PLM.
JT Bi-Directional Translator for Catia V5 13.0 1-1

Chapter 2: Using the translator
Translating Catia V5 files to JT
Translate CATIA V5 files to JT

The CATIA V5 to JT configuration file contains preferences and options that determine how you can
translate CATIA V5 files to JT files.
You can begin translating CATIA V5 CATProducts and CATParts to JT files by using the default
configuration file that is provided during installation. Or, you can edit this standard configuration file
and change any default value associated with parameters used to translate files.
You can also use command line options to modify how files are translated.
• CATIA V5 to JT configuration file
• Translating CATIA V5 files from the command prompt
• Locate the configuration file
Modifying Catia V5 to JT translator specific options
Edit translator specific options
You can edit the options listed in this section to change how you translate CATIA V5 files to JT.
1. Open an existing configuration file with a text editor.
2. Edit the configuration file options.
Option Keyword or value Example

catiaConfig catiaConfig { catiaConfig {
collapsetopart PartHierarchy =
PartHierarchy
showopenbodies "collapsetopart"
part_and_asm
part_only appendCADExtension =
appendCADExtension
conflict_only "none"
none
true
Translate_Bodies Translate_Bodies = true
false

Chapter
Chapter 2: 2: UsingUsing the translator
the translator
"all"
Translate_OpenBodies "none" Translate_OpenBodies = "all"
"<OpenBody1, OpenBody2>"
true
Translate_Curves Translate_Curves = true
false
true
Translate_Surfaces Translate_Surfaces = true
false
true
Translate_Points Translate_Points = true
false
true Translate_PointCloudData =
Translate_PointCloudData
false true
true Translate_InactiveLayerEntities
Translate_InactiveLayerEntities
false = true
true Translate_NoShowEntities =
Translate_NoShowEntities
false false
none
Translate_Textures embed Translate_Textures = "embed"
external
"D:\CATIA_V5\win_b64\startup
TextureImageSearchPath "String"
\materials”
AssySearchCriteria =
"InternalLink;CurrentWorking
AssySearchCriteria "String"
Directory;RelativeFolder;
AssySearchPath”
AssySearchPath "String" AssySearchPath = ""
true
OptimizeBrep OptimizeBrep = false
false
"all"
"none"
"{error, warning, info}"
LogReporting Note LogReporting = "error"

You can use a
comma separated
list with any of these
values.
2-2 JT Bi-Directional Translator for Catia V5 13.0

Using the translator
"cat_file, cat_ext, user, pid,

LogFileName LogFileName = "cat_file, pid"
time"
"all"
"none"
ConsoleReporting Note ConsoleReporting = "error"

You can use a
comma separated
values.
true
XTbrep XTbrep = true
false
true
SimplifyGeom SimplifyGeom = false
false
CATTPS_CATNls_File=”
CATTPS_CATNls_File “<location_of_the_file>”
<location_of_the_file>”
close brace } }
"high"
TransparencyQuality TransparencyQuality = "high"
"low"
true
EnableEquipmentRuns EnableEquipmentRuns = false
false
3. Save the configuration file with a .config extension.
Note
If you edit an option be sure to include a space both before and after the equal sign.
catiaConfig
Purpose
You can use this option in a configuration file to mark the beginning of CATIA translation options.
Syntax
catiaConfig {

Chapter
the translator
PartHierarchy
Purpose
You can use this option to specify how your JT translation appears in the Assembly Tree of the
Teamcenter viewer. This option sets the product structure of resulting translated JT files.
Syntax
PartHierarchy = "collapsetopart"
Arguments
Use this option To do this
Display one node for each CATPart.
Note
collapsetopart
You can use this option when you
want all entities within a part to be
written into just one node.
Display one node for each geometrical set.
Note
showopenbodies
The CATIA V5 name convention is
duplicated for each geometrical set.
Note
Supporting geometry visibility in a Capture will cause additional leaf structure to be translated to
the JT file - for "collapsetopart" as well as "showopenbodies" setting.
appendCADExtension
Purpose
You can use this option to add an extension to the names of the JT files. You use this option to
more precisely identify your part or assembly nodes by choosing from the following.
Syntax
appendCADExtension = "none"
Arguments
Add _CATPart or _CATProduct to the JT file
part_and_asm
name.
Add _CATPart to the JT part name.
part_only Note
JT assembly files are not changed.

Add _CATPart to JT part files if there is an

assembly node with that name.
Note
conflict_only
This prevents conflicts with
embedded parts if you use the full
shatter option.
none Prevent changes to the names of the nodes.
Translate_Bodies
Purpose
You can use this option to activate processing CATIA V5 solid bodies.
Syntax
Translate_Bodies = true
Translate_OpenBodies
Purpose
You can use this option to specify if you want to translate CATIA V5 open bodies. Open bodies
are named containers for CATIA geometry. Use the following additional options to specify how
you want CATIA V5 open bodies translated.
Syntax
Translate_Openbodies = "all"
Arguments
"all" Translate all open bodies.
"none" Disable translating open bodies.
Specify the exact open bodies you want to
"<comma-separated list>"
process.
Notes
• When your CATProduct or CATPart contains nested open bodies, this option only applies to
the top level open body.
• You can use PartHierarchy to control how the translated open bodies are displayed in the
viewer.
• Supporting geometry visibility in a Capture will require some open bodies to be translated.
Translate_OpenBodies setting will be overridden in such cases.

Chapter
the translator
Translate_Curves
Purpose
You can use this option to activate processing CATIA V5 curves as wire frames.
Syntax
Translate_Curves = true
Translate_Surfaces
Purpose
You can use this option to activate processing CATIA V5 free-form surfaces.
Syntax
Translate_Surfaces = true
Translate_Points
Purpose
You can use this option to activate processing CATIA V5 points.
Syntax
Translate_Points = true
Translate_PointCloudData
Purpose
You can use this option to activate processing CATIA V5 point cloud data such as points,
scans, grids and meshes.
Syntax
Translate_PointCloudData = true
Translate_InactiveLayerEntities
Purpose
You can use this option to activate processing CATIA V5 entities that are not on the active layer.
Syntax
Translate_InactiveLayerEntities = true
Translate_NoShowEntities
Purpose
You can use this option to activate processing CATIA V5 entities when CATIA modeling has
set them not to show.
Syntax
Translate_NoShowEntities = false

Note
When geometry visibility in a Capture is enabled by setting the
CAPTURE_GEOMETRY_VISIBILITY environment variable to TRUE, geometry will be translated,
regardless of its Show / Hide status, if it is referenced by a Capture.
Translate_Textures
Purpose
You can use this option to specify if you want to translate CATIA V5 material textures to JT.
Use the following additional options to specify how you want CATIA V5 material textures to
translated to JT.
Syntax
Translate_Textures = "embed"
Arguments
"none" Disable translation of textures of JT.
Texture image will be embedded inside the JT
"embed"
file.
JT file will have a reference to an external
texture image file. Texture image will be copied
to the folder specified by 'outputDirectory'
"external" option.
Updating the image file will cause the JT
visualization to be updated automatically to
reflect the new image file.
Note
For non-cubic texture mapping types, the texture display in JT may not match that of
CATIA V5. It is recommended that the user either change the mapping type to cubic
in CATIA V5 and re-translate or adjust the display using the ‘Render’ functionality in
TC Visualization and re-save the JT file.
Texture definition is stored in the tessellation container. Deleting ‘all’ the LODs and
re-tessellating will cause the texture definition to be lost.
TextureImageSearchPath
Purpose
Use this option to locate the texture images referenced by the CATProducts/CATParts.
Syntax
TextureImageSearchPath = "<path_to_texture_image_files>"
Notes
• You can use this option to search in several directories. You must separate or delimit each
directory with a semicolon.

Chapter
the translator
• If no directories are specified in this option, the translator will look for the texture image in the
absolute location stored internally in the file. It will also search in the directory that contains
the input CATProduct/CATPart.
Example
TextureImageSearchPath = "D:\CATIA_V5\win_b64\startup\materials"
TextureImageSearchPath = "D:\CATIA_V5\win_b64\startup\materials;
D:\CATIA_V5\win_b64\startup\materials\textures"
AssySearchCriteria
Purpose
Use this option to specify the search criteria to use for locating components referenced by the
CATProducts you want translated.
Syntax
AssySearchCriteria = "InternalLink;CurrentWorkingDirectory;RelativeFolder;AssySearchPath"
Notes
• You can use this option to specify the combination of InternalLink, CurrentWorkingDirectory,
RelativeFolder and AssySearchPath to be used for locating components.
• When AssySearchCriteria includes AssySearchPath, ensure that AssySearchPath option

is set appropriately.
Example
AssySearchCriteria = "CurrentWorkingDirectory;Relative Folder"
AssySearchPath
Purpose
Use this option to locate components referenced by the CATProducts you want translated. When
you translate a CATProduct by specifying the path, the directory and subdirectories listed in
AssySearchPath are searched.
Syntax
AssySearchPath = "<path_to_CATProduct>"
Notes
• You can use this option to search in several directories and their subdirectories. You must
separate or delimit each directory with a semicolon.
• You must also set AssySearchCriteria to contain AssySearchPath.
Example
AssySearchPath = "D:\CATIA_V5\test_data\F123456"; AssySearchPath =
"D:\CATIA_V5\test_data;D:\CATIA_V5\more_test_data"

OptimizeBrep
Purpose
You can use this option to optimize the model for better downstream usability.
Syntax
OptimizeBrep = false
Notes
• You must also set the XTbrep option to true.
• This option attempts to repair tolerant geometry by recalculating edge and vertex geometry
to Parasolid precision wherever possible and ensures that edges that were designed to be
tangent are tangent to within Parasolid tolerance.
• This option attempts to remove redundant topology. For example, it attempts to merge two
half-cylinder faces into one cylindrical face.
• This option removes any duplicate underlying curve and surface geometry by attempting to
share geometry within a sheet or solid body. Duplicate curves or surfaces are those that are
of the same curve or surface type and are spatially and parametrically exactly the same.
• A tolerance of 1.0e-6 meters will be used for optimizing the Brep.
LogReporting
Purpose
You can use this option to control error reporting details. You can choose from the various options
to determine how you want error messages written to the log file.
Syntax
LogReporting = "none"
Arguments
"all" Write all error messages to the log file.
"none" Disable error messaging.
Select a combination of error message types
to write to the log file.
{"error" "warning" "info"} Note

These options must be in the form of
a comma separated list.
LogFileName
Purpose
You can use this option to specify the name of your error message log file. And, you can add
other supported information that may be useful to organizing log files.

Chapter
the translator
Syntax
LogFileName = "cat_file"
Arguments
Display the input file name as part of the log
"cat_file"
file name.
Display the input file extension in the log file
"cat_ext"
name.
"user" Display the system user in the log file name.
Display the system process ID in the log file
"pid"
name.
"time" Display the system time in the log file name.
Notes
• The log file is saved to the location you specified in outputDirectory.
• You can use any combination of these options for the name of the log file by surrounding a
list of comma separated options with quotation marks.
Example
This example translates XYZ.CATProduct as root user and creates the log file name –
XYZ_root.log.
LogFileName = "cat_file, user"
This next example translates XYZ.CATProduct and creates the log file name –
XYZ_CATProduct_root.log.
LogFileName = "cat_file, cat_ext, user"
ConsoleReporting
Purpose
to determine how you want error messages written to the console.
Syntax
ConsoleReporting = "error"
Arguments
"all" Send all error messages to the console.
Disable sending any error message to the
"none"
console.


to send to the console.

XTbrep
Purpose
You can use this option to activate the use of XT B-rep when translating models and parts. Use
this feature to generate Parasolid XT B-rep, the common strategy for sharing XT data across
B-rep processing geometry, as an alternative JT B-rep for precise geometry.
Syntax
XTbrep = true
SimplifyGeom
Purpose
You can use this option to activate an attempt to recover analytic representations of the geometry
from B–Spline geometry.
Syntax
SimplifyGeom = false
Notes
• You must also set the XTbrep option to true.
• This option will convert Rational B-Curves and B-Surfaces to Non rational B-Curves and
B-Surfaces.
• A tolerance of 1.0e-6 meters will be used for simplifying the geometry.
CATTPS_CATNls_File
Purpose
Use this option to specify the path to a file that defines localized PMI labels.
Syntax
CATTPS_CATNls_File = “<location_of_the_file>”
Notes
• The specified path may be absolute or relative to the working directory.
• Make sure the specified file is in the same format as <

CATIA_V5_install>\resources\msgcatalog\<language>\CATTPS.CATNls.

Chapter
the translator
Example
CATTPS_CATNls_File = "P:\parts\catiav5\CAD_Data\PMI\Localization
\French_CATTPS.CATNls"
CATTPS_CATNls_File = ".\German_CATTPS.CATNls”
close brace
Purpose
You can use the right brace (}) to indicate the end of a section in the configuration file.
TransparencyQuality
Purpose
You can use this option to mimic the transparency display in CATIA V5.
Syntax
TransparencyQuality= “high”
Notes
• When TransparencyQuality = “high”, the transparency value is faithfully translated to JT
• When TransparencyQuality = “low”, all non-zero transparency values in CATIA V5 will be

mapped to 50% transparency in JT.
Example
TransparencyQuality = "low"
EnableEquipmentRuns
Purpose
You can use this option to create a place holder node in the JT assembly for a CATIA V5 Run
node.
Syntax
EnableEquipmentRuns = false
Modifying Catia V5 to JT general setup options
Edit general setup options

You can edit options in the Setup section of the configuration file to specify general conditions and
features that are common for all JT translators.
1. Open an existing configuration file in a text editor.
2. Edit one or more of the following options in the Setup section of the configuration file.
Option Keywords Example

EAITranslator EAITranslator { EAITranslator {
OutputDirectory "path to directory" OutputDirectory = "./"

chordalOption "RELATIVE" "ABSOLUTE" chordalOption = "RELATIVE"

"PER_PART" "MONOLITHIC" structureOption =
structureOption
"FULL_SHATTER" "MIMIC" "PER_PART"
"JTASCII" "JTPARTS"
writeWhichFiles =
writeWhichFiles "JTASSEMBLY" “PLMXML”
“JTPARTS,JTASSEMBLY”
“AP242XML”
"NONE" "PART_AND_ASM" pmiOption =
pmiOption
"ASM_ONLY" "PART_ONLY" "PART_AND_ASM"
“9”
JtFileFormat “10”
“10”
true
triStripOpt triStripOpt = true
false
true
seamSewing seamSewing = false
false
seamSewingTol any integer seamSewingTol = 0.001
true
includeBrep includeBrep = true
false
true
autoNameSanitize autoNameSanitize = true
false
true updateChangedPartsOnly =
updateChangedPartsOnly
false false
true
writeAsciiAssembly writeAsciiAssembly = false
false
true
singlePartsNoAssem singlePartsNoAssem = true
false
true
smartLODgeneration smartLODgeneration = false
false
true autoLowLODgeneration =
autoLowLODgeneration
false false
numLODs any integer numLODs = 3
Note
If you edit an option make sure to include a space both before and after the equal sign.

Chapter
the translator
EAITranslator
Purpose
You can use the left brace ({) to mark the beginning section of the configuration file.
OutputDirectory
Purpose
You can use this option to specify the directory name and path for saved JT files.
Example
The default value is
OutputDirectory = "./"
chordalOption
Purpose
You can use this option to specify how you want the Level of Detail (LOD) chordal value set
during the translation. You set this option to an absolute value in model units or as a percentage
of the part size.
Arguments
Use one of these arguments.
Use this argument To

Interpret the tessellation value as a strict
"ABSOLUTE"
number of units that are applied to all parts.
Interpret the tessellation value of all parts
"RELATIVE" relative to size and with the same surface
quality.
Example
• If you specify RELATIVE, a bolt is tessellated to the same degree as a larger part, and both
have the same surface quality. This is the optimum setting.
• If you specify ABSOLUTE, and have a chordal value of 1, that value is used to tessellate a
part that is one unit across, and for a part that is 100 units across. This process results in
larger parts being more tessellated than smaller parts.

chordalOption = "RELATIVE"
structureOption
Purpose
You can use this option to define and specify how you want to display the JT file.
Arguments
Use one of these arguments.

Use this argument To

Display an assembly JT file and directory of
structureOption="PER_PART"
part JT files derived from the original CAD data.
Display a single JT file containing the entire
structureOption="MONOLITHIC"
CAD data.
Display a JT file for each node in the JT
structureOption="FULL_SHATTER"
assembly.
Display one output file per original CAD file
structureOption="MIMIC" with corresponding contents to mimic the CAD
file structure.

Chapter
the translator
Example
Use the following product structure to see how the various structureOption arguments affect how
the JT files are displayed.
Option Resulting JT
MONOLITHIC A.JT
A.JT
A/P1.JT
PER_PART A/P2.JT
A/P3.JT
A/P4.JT
A.JT
B.JT
C.JT
FULL_SHATTER P1.JT
P2.JT
P3.JT
P4.JT
When you display product structure using the MIMIC argument, the results will vary depending on
the your JT translator. Use MIMIC to produce one-to-one JT file output for your specific CAD
input. For example, if the original data in the product structure example contained three CAD
assembly files, A.model, B.model, and C.model, the following table shows the results.
Option Resulting JT files

A.JT
MIMIC B.JT
C.JT

Note
The MONOLITHIC and MIMIC arguments may produce hybrid JT files containing both assembly
and part product structure. This may result in non-intuitive translations if the writeWhichFiles
option is not set to "JTPARTS,JTASSEMBLY."
writeWhichFiles
Purpose
You can use this option to filter how you want JT files translated.
Arguments
Choose one of these arguments.
Use this argument To do this

Export a text file that contains a listing of the
hierarchy for the model.
Note
• Install JT Utilities in order to
run the jttoascii utility from the
command-line in the same
translator environment.
"JTASCII"
• The new file will have an .ajt
extension together with the
name of the assembly.
• For some translators, choose

theWrite Assembly Text File
menu on the interface.
"JTPARTS" Export data translated as parts.

"JTASSEMBLY" Export data translated as assemblies.
Export data translated as PLMXML.
Note
• To explore or examine your
PLMXML file use a utility like
Jumpstart (included in the
"PLMXML" PLMXML SDK).
• Enabling both PLMXML

and pmiOption significantly
increases the file size. If you do
not need PMI, you can turn off
pmiOption.

Chapter
the translator
Export Assembly structure as STEP AP242

Business Object Model ( BOM ) XML.
Note
“AP242XML”
The most common usage of
this setting will take the shape
writeWhichFiles=”JTPARTS,AP242XML”
Note
Your configuration file may include a deprecated option, writeWhichFiles =
"PARTS_ONLY,ASSEMBLY_ONLY". The software will automatically change the option to
writeWhichFiles = "JTPARTS,JTASSEMBLY".
Example
The default is
writeWhichFiles = "JTPARTS,JTASSEMBLY"
pmiOption
Purpose
You can use this option to specify which product manufacturing information (PMI) data, if any, you
want to make available during the translation. Once pmiOption is set, you will need to enable
specific PMI entities for the specific JT translator you use.
Arguments
Choose one of the following arguments.
Use this option To export

"NONE" No PMI data
"PART_ONLY" Part PMI data
"ASM_ONLY" Assembly PMI data
"PART_AND_ASM" Part and assembly PMI data
Example
pmiOption = "PART_AND_ASM"
Notes
• The user needs to install TcVis V10.0.0.3 or higher for geometry visibility in captures to
work correctly.
JtFileFormat
Purpose
You can use this option to specify the most appropriate JT file format supported by your
environment.

Syntax
JtFileFormat = "10"
Arguments
Use this value To do this
Translate geometry content as losslessly or
lossily; all other content is translated with
losslessy compression.
Note
"8"
This setting is supported by the
following software:
• Teamcenter Visualization 4.0
and later.
Translate geometry content as losslessly or

lossily; all other content is translated with
losslessy compression.
JT V9.X is the recommended version for
multi-CAD workflows. This JT version
writes tessellation in a Topomesh format
which increases operations performed when
tessellated JT data is imported into NX and
"9" CATIA V5.
Note
following software:
• Teamcenter Visualization 2007
and later.
V10 JTs offer the following advantages:

• True Unicode PMI
• Advanced compression (10% - 30%

smaller than V9 JTs)
"10"
Note
following software:
• Teamcenter Visualization 10.1
and later.

Chapter
the translator
Notes
• For JT V9 and later, do not use Simplification in the first LOD level; this would remove
Topomesh data.
For more information about JT formats, see Select a JT file version.
triStripOpt
Purpose
You can use this option to enable or disable an additional optimization on the tessellated geometry
data in each JT part file. Use this option to reduce the number of triangles in the tristrips, without
reducing the quality of the displayed geometry. The process increases visualization quality, but
it also increases translation time.
Example
triStripOpt = true
seamSewing
Purpose
You can use this option to enable or disable creating shared edges in NURB data. Creating
shared edges is useful for face-modeled data.
Note
When you make seamSewing available, use seamSewingTol to set specific tolerance values.
Example
seamSewing = false
seamSewingTol
Purpose
You can use this option to specify tolerance for two vertices in a seam selected to be sewn. The
value you set is a floating point that represents a percentage of the bounding box.
Example
seamSewingTol = 0.001
includeBrep
Purpose
You can use this option to enable or disable precise model geometry in translated part files.
Notes
• When you make includeBrep available, the size of the JT file will increase because you are
including precise measurement and analysis work.

• For many JT translators, you can use the Include Precise Geometry menu on the translator
interface.
Example
includeBrep = true
autoNameSanitize
Purpose
You can use this option to enable or disable various Filter options.
Example
autoNameSanitize = true
updateChangedPartsOnly
Purpose
You can use this option to enable or disable a review of existing JT files to determine if the original
part changed. When you set updateChangedPartsOnly to true, only updated parts are translated.
Note
For this JT translator, if the geometry of the JT file was modified by Assembly Features (Holes,
Cuts, Grooves), the JT part file is not updated.
Example
updateChangedPartsOnly = false
writeAsciiAssembly
Purpose
You can use this option to enable or disable creating a text file containing the hierarchy for the
model. The text file uses an .alt extension and is named according to the assembly file name.
The text file also has an .ajt extension.
Notes
• Make sure that you have installed JT Utilities so that jttoascii runs correctly.
• For some translators, this option corresponds to the Write Assembly Text File menu on the
interface.
Example
writeAsciiAssembly = false
singlePartsNoAssem
Purpose
Use this option to activate or make unavailable creating a JT assembly structure when a JT
model is being translated with structureOption set to PER_PART. If the JT file consists only of an

Chapter
the translator
assembly and single part, the entire model is replaced with a single part. The software names the
part the name of the original assembly node. You can then translate one-part models without
creating a JT assembly file.
Note
If you set singlePartsNoAssem to true and writeWhichFiles was set to JTASSEMBLY, this
option will be overridden.
Example
singlePartsNoAssem = true
smartLODgeneration
Purpose
You can use this option to enable or disable creating of more levels of detail (LODs) than the
number specified in numLODs if the last LOD contains more than 200 polygons.
Example
smartLODgeneration = false
autoLowLODgeneration
Purpose
You can use this option to enable or disable the translator to automatically analyze and create
two simplified default levels of detail: a convex hull and a bounding box.
Example
autoLowLODgeneration = false
numLODs
Purpose
You can use this option to specify the number of levels of detail (LODs) for the translated file.
Each LOD can have separate tessellation options and these options are specified in the LOD
section of the configuration file.
Note
It is possible to declare up to ten LODs, but for the best translation performance consider using
three or less
Example
numLODs = 3
close brace
Purpose

Modifying filter options
Edit filter options
You can edit the Filter section of the configuration file to specify how filenames are sanitized and to
specify how metadata keys are filtered.
2. Edit one or more of the following Filter options.

Filter Filter { Filter {
FilenameSanitizeSet "string of characters" FilenameSanitizeSet = "abc123."
FilenameSanitizeSetAdd "string of characters" FilenameSanitizeSetAdd = "4l"
FilenameSanitizeSetDelete "string of characters" FilenameSanitizeSetDelete = "c"
MetadataKey = "metadata key to
MetadataKey "string of characters"
exclude"
MetadataFilter = "EXCLUDE" or
MetadataFilter "string of characters"
"INCLUDE"
close brace } }
3. Make sure the autoNameSanitize option is set to true.
Note
Filter
Purpose
You can use the left brace ({) to mark the beginning of the Filter section in the configuration file.
FilenameSanitizeSet
Purpose
You can use this Filter option to modify the file names created by the translator. You may have
source files that include naming conventions that are not supported by your environment. Use this
option to specify a set of characters in file names that are to be replaced with an underscore ("_").
Notes
• You can specify alphabetic letters and numbers, and you can also sanitize the following
symbols from file names:`~!@#$%^&*()-+=\"\\':;,./<>?|[]{}
• If you update or write a new set of characters, your existing set or default set is overwritten.

Chapter
the translator
Example
You have unsupported file names that begin with 1a. To change all “1's” and “a's” to underscores,
in Filter section of your configuration file enter:
FilenameSanitizeSet = "1a".
FilenameSanitizeSetAdd
Purpose
You can use this Filter option to add one or more characters to the file name sanitize string
specified by FilenameSanitizeSet .
Example
You want to add 2b to your existing file name sanitize set. To replace “2's” and “b's” with
underscores, in the Filter section of your configuration file type:
FilenameSanitizeSetAdd = "2b"
FilenameSanitizeSetDelete
Purpose
You can use this Filter option to delete previously set sanitized file name characters. You can
ignore one or more characters from the sanitize string set from FilenameSanitizeSet. This option
is useful if you do not want to sanitize specific characters
Example
You want to include periods in your file names, but periods are include in your sanitize set. To
include periods in your file names, in the Filter section of your configuration file type:
FilenameSanitizeSetDelete = "."
MetadataKey
Purpose
You can use this Filter option to specify that all keys in “MetadataKey” are to be removed from JT
files (EXCLUDE), or to specify that all keys except those in “Metadatakey” are to be removed
from JT files (INCLUDE).
Example
MetadataKey = <metadata key to include or exclude>
MetadataFilter
Purpose
Controls if specified metadata keys are removed from JT files (EXCLUDE) or if all other keys
other than those specified are removed from JT files (INCLUDE).
Example
MetadataKeyFilter = "EXCLUDE"

close brace
Purpose
Modifying level of detail options
Edit level of detail options

You can edit the Level of Detail (LOD) section of the configuration file to change how the translation
is tessellated and to set the level of simplification for the translation. By editing options in this
section you can increase or decrease the details of each defined LOD. Use numLODs to specify
how many LODs you want.
2. Edit one or more of the following Level of Detail options.

LOD LOD "lod number" { LOD "1" {
Level any integer Level = 1
Label <label_name> Label = Manufacturing
Chordal any number Chordal = 0.001
Angular any number Angular = 26
Length any number Length = 0.0
FeatureSuppression any integer FeatureSuppression = 0
Simplify any number Simplify = 0.60
advCompressionLevel any value between 0.0 and 1.0 advCompressionLevel = 0.5
close brace } }
Tip
You will achieve the best translation and viewing performance if you define three or fewer
LODs. Each new LOD requires time and adds size to the translated JT file.
LOD
Purpose
You can use this Level of Detail option to indicate the beginning section of the configuration file
that sets details of your LODs. The syntax includes the keyword (LOD) indicating the beginning
of this section, a number that indicates the number of LODs you want, and a left brace ({).
Example

Chapter
the translator
LOD "1" {
Level
Purpose
You can use this Level of Detail (LOD) option to specify how many levels of detail you want set
for each translation. If there are three levels of detail, this line is repeated three times, each
with a different level of detail.
Example
Level = 1
Label
Purpose
You can use this Level of Detail (LOD) option to assign labels to one or more LODs. To create a
label for each LOD, in the LOD section of the configuration file, enter Label = <label_name>
Example
• Label = Manufacturing
•
LOD "1" {
Level = 1
Label = Manufacturing
Chordal = 0.001
Angular = 20.0
Length = 0.0
FeatureSuppression = 0.0
Simplify = 1.0
AdvCompressionLevel = 0.0
• The benefit of using LOD labels is they help improve loading LODs in Teamcenter's lifecycle
visualization. If the JT file has several unlabeled LODs, each one will be loaded. When
you define one or more LODs, you can then use Teamcenter's lifecycle visualization
features to load specifically labeled LODs. For example, you can label an LOD containing
specified details (Chordals, Angulars, etc.) as Manufacturing, and the Teamcenter's lifecycle
visualization user can then open this LOD only, or any other LOD they want to open.
• Refer to Teamcenter's lifecycle visualization documentation for LOD details.
• When you assign labels to LODs, smartLODgeneration and autoLowLODgeneration are

unavailable.

Chordal
Purpose
You can use this Level of Detail option to define the maximum absolute distance that a line
segment may deviate from the smooth curve it is approximating. The value you set for this option
produces the levels of detail representing each part and it specifies polygonal approximations of
models defined with curved surfaces.
Example
• Chordal = 0.001
• Refer to Angular for additional details.
Angular
Purpose
You can use this Level of Detail (LOD) option to limit the absolute maximum angle between two
adjacent line segments in a curve approximation. The value you set produces the levels of
detail representing each part and it specifies polygonal approximations of models defined with
curved surfaces.
Example
• Angular = 25
Tip
For best results, use both chordal and angular parameters. The chordal value
affects larger features of the model, while the angular value affects smaller
features.

Chapter
the translator
• The round object has a small hole through the center of it. If the translator tessellates the
object with only the angular parameter, the polygons that define the hole follow the surface
much better than the polygons that define the perimeter. If the translator tessellates the
object with only the chordal parameter, the polygons along the perimeter of the object follow
the curves much better than the polygons that define the hole.
Tip
For best results, use both chordal and angular parameters. The chordal value affects
larger features of the model, while the angular value affects smaller features.
Length
Purpose
A line segment in the tessellation of a curve has a certain length. This parameter specifies
the exact length allowed.
Example
Length = 0.0

FeatureSuppression
Purpose
You can use this Level of Detail option to suppress holes and arcs smaller than the specified
number.
Example
FeatureSuppression = 0
Simplify
Purpose
You can use this Level of Detail (LOD) option to specify a minimum level of simplification for the
model, relative to the first level of detail. The value is expressed as a percentage of the first
level of detail.
Example
• Simplify = 0.60
• Assume that a model contains 100,000 polygons for the first level of detail. You decide to set
the second level of detail to 60% of the first level. Enter the following in the configuration file:
Simplify = 0.60.
The software checks the translated JT file to see if the second LOD has 60,000 or fewer
polygons. If there are more than 60,000 polygons, the translator continues to simplify the
model until the number of polygons meets 60%.
Notes
• Make sure the first LOD is set to 1.0 (one hundred percent) because it should have the
highest level of detail.
• For best results, it is recommended that you set smartLODgeneration to false.
advCompressionLevel
Purpose
Use this option to specify the level of advanced compression for each Level of Detail (LOD) you
set when translating JT files. A value of 0.0 specifies lossless compression, while a value of
1.0 specifies lossy compression. Set the value of this option as a floating point in the range of
0.0 to 1.0.
Set the advanced compression level to 0.0 for the finest LOD. This setting is required for
exchanging JT files in multi-CAD environments.
Notes
Compression methods include lossless and lossy standards.
lossless A compression method where original data is not lost after compressing
files. The size of the file is larger than from using lossy compression.

Chapter
the translator
lossy A compression method where original, usually repeating, data is deleted

from the file. Lossy compressed files are smaller than lossless files.
Generally speaking, you will notice that measurement accuracy begins to be affected at
compression level values of 0.2 or 0.3. And visual accuracy begins to be affected at values of
0.4 or 0.6.
Compression value Effect on geometry

Lossless compression with no effect on the
0.0 measurement accuracy and appearance of
geometry.
Minimal lossy compression with little effect on
0.1 the measurement accuracy and appearance of
geometry.
Moderate lossy compression with a noticeable
0.5 effect on the measurement accuracy and
appearance of geometry.
Aggressive lossy compression with an obvious
1.0 effect on the measurement accuracy and
appearance of geometry.
Example
advCompressionLevel = 0.5
close brace
Purpose
Modifying metadata options
Edit metadata options
You can edit the Metadata section of the configuration file to modify how metadata is displayed
in your translated JT files.
2. Edit one or more of the following options.

Metadata Metadata { Metadata {
AddToParts = "<metadata
AddToParts "string of characters" key>" AddToParts =
"<metadata value>"
AddToAssemblies =
"<metadata key>"
AddToAssemblies "string of characters"
AddToAssemblies =
"<metadata value>"

AddToAllNodes = "<metadata
AddToAllNodes "string of characters" key>" AddToAllNodes =
"<metadata value>"
close brace } }
Note
Enter these options in pairs. The first line of text defines the metadata key and the second
line defines the metadata value.
Metadata
Purpose
You can use the left brace ({) to mark the beginning of the Metadata section of the configuration
file.
AddToParts
Purpose
You can use this Metadata option to add common metadata properties to all model part nodes.
Example
Enter pair values in the Metadata section of the configuration file; one line defines the metadata
key and the other line defines the metadata value.
AddToParts = "Creator"
AddToParts = "Mr. Smith"
AddToAssemblies
Purpose
You can use this Metadata option to add common metadata properties to all model assembly
nodes.
Example
AddToAssemblies = "Creator"
AddToAssemblies = "Mr. Smith"
AddToAllNodes
Purpose
You can use this metadata option to add common metadata properties to all model part and
assembly nodes.

Chapter
the translator
Example
AddToAllNodes = "Creator"
AddToAllNodes = "Mr. Smith"
close brace
Purpose
Translate CATIA V5 to JT files from the command prompt

You can save time by translating files from the command prompt.
To use the command prompt
• At the command prompt, type
jt_catiav5 <path_to_Catia5_file> <configuration_file>
Note
If you do not include a reference to your specific configuration file, the default
configuration file is used.
• Enter command-line options, as desired

In the selected directory, translate all JT files to
–dir=<directory>
CATIA V5 and all CATIA V5 files to JT.
Look in the specified directory or directories for
–AssySearchPath=<directory>
associated CATParts and CATProducts.
-AssySearchCriteria=Internal Use the specified search criteria to locate
link;CurrentWorkingDirectory;RelativeFolder components referenced by the CATProducts
;AssySearchPath you want to translate.
Specify the directory where translated JT files
–outputDirectory=<directory>
are saved.
–PartHierarchy=<collapsetopart/showopen Specify how your JT translation appears in the
bodies> Assembly Tree of the viewer.
–Translate_Bodies=<true/false> Enable or disable processing solid bodies.
Specify how the translator processes open
–Translate_OpenBodies=<OpenBody1,OpenBody2>
bodies.
Enable or disable processing free-form
–Translate_Surfaces=<true/false>
surfaces.
Enable or disable translating curves as
–Translate_Curves=<true/false>
wireframe entities.
–Translate_Points=<true/false> Enable or disable processing CATIA V5 points.

Enable or disable translating entities that were

–Translate_NoShowEntities=<true/false>
set to no show in CATIA V5.
-Translate_Textures = "none" or "embed" or Specify how CATIA V5 material textures should
"external" be translated to JT.
Look in the specified directory or directories
-TextureImageSearchPath = <directory”
for Texture image files.
–Translate_InactiveLayerEntities= Enable or disable translating entities that are
<true/false> not on the active layer.
–LogReporting=<all> | <none> | Control the error reporting details you want
<error,warning,info> written to your error log file.
–LogFileName=<cat_file,cat_ext,user, Specify the name of your error message log
pid,time> file.
–ConsoleReporting=<all> | <none> | Control the error reporting details you want
<error,warning,info> written to the console.
–appendCADExtension=<part_and_asm> | Add an extension to the names of the JT files
<part_only> | <conflict_only> | <none> to identify part or assembly nodes.
Select translating PLMXML to JT or to CATIA
-mode=<PLMXMLtoJT> | <PLMXMLtoCATIAV5>
V5.
–CATTPS_CATNls_File=<location_of_ Use the specified CATTPS.CATNls file to read
catnls_file> the localized labels for PMI.
Enable or disable adding a place holder node
-Enable_Equipment_Runs=<true/false>
in the JT assembly.
Example
jt_catiav5 Part1.CATPart catiatojt.config
jt_catiav5 –LogReporting="error,warning" –LogFileName="cat_file,user"

–PartHierarchy=collapsetopart Part1.CATPart catiatojt.config
jt_catiav5 -dir="d:\scratch" —
AssySearchCriteria="CurrentWorkingDirectory;AssySearchPath" —
AssySearchPath=d:\scratch\;c:\scratch" catiatojt.config
Get information and help from the command prompt.
Sample configuration file – CATIA V5 to JT

version "EAITranslator" 1.0.0 "EAITranslator"
EAITranslator {
chordalOption = "RELATIVE"
structureOption = "PER_PART"
writeWhichFiles = "JTPARTS,JTASSEMBLY"
pmiOption = "PART_AND_ASM"
partMonitor = false

Chapter
the translator
JtFileFormat = “9”
triStripOpt = true
seamSewing = false
seamSewingTol = 0.001
includeBrep = true
autoNameSanitize = true
updateChangedPartsOnly = false
writeAsciiAssembly = false
singlePartsNoAssem = false
autoLowLODgeneration = true
smartLODgeneration = false
numLODs = 3
verboseReporting = false
}
Filter {
MetadataKey = ""
MetadataFilter = "EXCLUDE"
FilenameSanitizeSet = ""
FilenameSanitizeSetAdd = ""
FilenameSanitizeSetDelete = ""
}
Metadata {
AddToParts = ""
AddToAssemblies = ""
AddToAllNodes = ""
}
LOD "1" {
Level = 1
Chordal = 0.001
Angular = 20.0
Length = 0.0
}
LOD "2" {
Level = 2
Chordal = 0.002
Angular = 0.0
Length = 0.0
Simplify = 0.4
}
LOD "3" {
Level = 3
Chordal = 0.009
Angular = 0.0
Length = 0.0
Simplify = 0.1
}
catiaConfig {
PartHierarchy = "collapsetopart"
Translate_OpenBodies = "all"

Translate_Surfaces = true
Translate_PointCloudData = false
Translate_NoShowEntities = false
Translate_InactiveLayerEntities = true
Translate_Textures = "none"
TextureImageSearchPath = “”
AssySearchCriteria =
"InternalLink;CurrentWorkingDirectory;RelativeFolder;AssySearchPath"
AssySearchPath = ""
FontsSearchPath = ""
LogReporting = "error"
XTbrep = true
SimplifyGeom = false
OptimizeBrep = false
appendCADExtension = "none"
CATTPS_CATNls_File = ""
TransparencyQuality = "high"
}
Locate configuration files
The translator locates configuration files in the following order:
1. When you use the configuration file from the command prompt to enter the path and file name
of the file.
2. When you do not use the command prompt, or if you use the GUI, the translator looks for a
configuration file in the current working directory.
Note
If the current working directory does not have the required file permissions, then the
.config file will be written to the directory defined on Windows by the environment
variable %USERPROFILE% and on UNIX by the environment variable $HOME.
3. When you do not have a configuration file saved in the current working directory, the translator
reads the default file located in the <translator_installation_directory>/etc directory.
Translating JT files to Catia V5
Translate JT files to CATIA V5
The JT to CATIA V5 configuration file contains preferences and options that determine how you
can translate JT files to the CATIA V5 format.

Chapter
the translator
You can begin translating JT files to CATIA V5 files by using the default configuration file that is
provided during installation. Or, you can edit this standard configuration file and change any default
value associated with parameters used to translate files.
• You can also use command line options to modify how files are translated.
• Edit translator specific options
• Translate JT to CATIA V5 files from the command prompt
• Sample configuration file – JT to CATIA V5
• Locate the configuration file
Modifying JT to Catia translator specific options
Edit translator specific options
You can edit the options listed in this section to change how you translate JT files to CATIA V5.
2. Edit the configuration file options.
Option Keyword or value Example

catiaConfig catiaConfig { catiaConfig {
true
Translate_Bodies Translate_Bodies = true
false
true
Translate_Curves Translate_Curves = true
false
true
Translate_Points Translate_Points = true
false
true
EnableHybridDesign EnableHybridDesign = true
false
"R19"
CatiaV5FileFormat CatiaV5FileFormat = "R19"
"R14"

"all"
"none"
LogReporting Note LogReporting = "error"

You can use a
comma separated
values.
"cat_file, cat_ext, user, pid,

LogFileName LogFileName = "cat_file, pid"
time"
"all"
"none"
ConsoleReporting Note ConsoleReporting = "error"

You can use a
comma separated
values.
close brace } }
Note
If you edit an option be sure to include a space both before and after the equal sign.
catiaConfig
Purpose
You can use this option in a configuration file to mark the beginning of CATIA translation options.
Syntax
catiaConfig {
Translate_Bodies
Purpose
You can use this option to activate processing CATIA V5 solid bodies.

Chapter
the translator
Syntax
Translate_Curves
Purpose
You can use this option to activate processing CATIA V5 curves as wire frames.
Syntax
Translate_Points
Purpose
You can use this option to activate processing CATIA V5 points.
Syntax
EnableHybridDesign
Purpose
You can use this option to either enable or disable hybrid design inside Part Bodies and Bodies
created from a JT to CATIA V5 translation.
Example
EnableHybridDesign = true
CatiaV5FileFormat
Purpose
You can use this option to specify the version of CATIA V5 files that are to be produced from a
JT to CATIA V5 translation.
Syntax
CatiaV5FileFormat = "R14"
Notes
"R14" Write CATIA V5R14 files.
"R19" Write CATIA V5R19 files.
LogReporting
Purpose
to determine how you want error messages written to the log file.
Syntax
LogReporting = "none"

Arguments
"all" Write all error messages to the log file.
"none" Disable error messaging.
to write to the log file.

LogFileName
Purpose
You can use this option to specify the name of your error message log file. And, you can add
other supported information that may be useful to organizing log files.
Syntax
Arguments
Display the input file name as part of the log
"cat_file"
file name.
Display the input file extension in the log file
"cat_ext"
name.
"user" Display the system user in the log file name.
Display the system process ID in the log file
"pid"
name.
"time" Display the system time in the log file name.
Notes
• The log file is saved to the location you specified in outputDirectory.
• You can use any combination of these options for the name of the log file by surrounding a
list of comma separated options with quotation marks.
Example
This example translates XYZ.CATProduct as root user and creates the log file name –
XYZ_root.log.
LogFileName = "cat_file, user"
This next example translates XYZ.CATProduct and creates the log file name –
XYZ_CATProduct_root.log.
LogFileName = "cat_file, cat_ext, user"

Chapter
the translator
ConsoleReporting
Purpose
to determine how you want error messages written to the console.
Syntax
Arguments
"all" Send all error messages to the console.
Disable sending any error message to the
"none"
console.
to send to the console.

close brace
Purpose
Translate JT to CATIA V5 files from the command prompt

You can save time by translating files from the command prompt.
To use the command prompt
• At the command prompt, type
jt_catiav5 <path_to_JT_file> <configuration_file>
Note
If you do not include a reference to your specific configuration file, the default
configuration file is used.
• Enter command-line options, as desired

In the selected directory, translate all JT files to
–dir=<directory>
CATIA V5 and all CATIA V5 files to JT.
Specify the directory where translated files are
–outputDirectory=<directory>
saved.

–Translate_Bodies=<true/false> Enable or disable processing solid bodies.

Enable or disable translating curves as
–Translate_Curves=<true/false>
wireframe entities.
–Translate_Points=<true/false> Enable or disable processing JT points.
–LogReporting=<all> | <none> | Control the error reporting details you want
<error,warning,info> written to your error log file.
Specify the name of your error message log
–LogFileName=<cat_file,cat_ext,user,pid,time>
file.
–ConsoleReporting=<all> | <none> | Control the error reporting details you want
<error,warning,info> written to the console.
Enable or disable hybrid design inside Part
–EnableHybridDesign=<true/false>
Bodies and Bodies.
–CatiaV5FileFormat=<”R14”/”R19”> Specify the version of CATIA V5 files.
Example
jt_catiav5 file1.jt jttocatia.config
jt_catiav5 –LogReporting="error,warning" –LogFileName="cat_file,user" –file1.jt

jttocatia.config
jt_catiav5 -dir="d:\scratch" jttocatia.config
jt_catiav5 -EnableHybridDesign=true Part1.jt
jt_catiav5 -CatiaV5FileFormat="R19" Part1.jt
Get information and help from the command prompt.
Sample configuration file – JT to CATIA V5

version "EAITranslator" 1.0.0 "EAITranslator"
EAITranslator {
}
catiaConfig {
EnableHybridDesign = true
CatiaV5FileFormat = "R14"
LogReporting = "error"
}

Chapter
the translator
Internationalized content in configuration files

The translator supports internationalized content in configuration files. Configuration options that
accept string values such as "OutputDirectory" and "AssySearchPath" now support internationalized
characters. Configuration files containing internationalized characters are required to be saved as
"UTF-8 without Byte Order Mark (BOM) ". Applications such as Notepad++ and Visual Studio allow
for editing and saving the configuration files in this manner.
In order for the translator to read UTF-8 encoded configuration files on UNIX, the operating system
should be configured to run a UTF-8 locale such as en_US.UTF8. UNIX operating system can be
configured to work in a particular language by setting the LANG environment variable. Consult the
operating system documentation for full details on setting LANG. In addition to the LANG environment
variable, two other environment variables will need to be set. JT_UCM_PATH should set to
$EAI_INSTALL/etc and JT_CODE_PAGE should be set to UTF8.
Using the interface to configure file translations

Using the interface to configure file translations
You can open a Graphical User Interface (GUI) either from a CATIA V5 session or from your operating
system. The interface may simplify how you edit translation parameters by using graphical options
and menus. Use the interface to configure preferences for exporting or importing CGR files and
CATPart or CATProduct files to JT file types.
Note
To import files into a CATIA V5 session you must purchase a license for JT Import for
CATIA V5. This application is a separate, independent software program.
You can use the interface that is embedded in CATIA V5 to:

• Specify frequently used configuration settings and JT preferences.
Note
o See Locate configuration files for a description of how the translator locates the
configuration file for populating the JT Preferences dialog.
o Configuring settings using the JT Preferences interface will not modify the
configuration files located in the “etc” folder of the translator install. If the translator
locates the configuration file in the “etc” folder, a configuration file with the changed
settings will be written to the current working directory. If the current working
directory does not have the required file permissions, the configuration file will
be written to the directory defined on Windows by the environment variable
%USERPROFILE% and on UNIX by the environment variable $HOME.
• Import JT files.
• Insert a JT file in a selected node. The inserted file can be a CGR, CATPart, or CATProduct file.

• Save a currently opened CATPart or CATProduct file as a JT file.
You can use the interface from your operating system to:
• Specify frequently used configuration settings.
Note
o See Locate configuration files for a description of how the translator locates the
configuration file for populating the JT Preferences dialog.
o Configuring settings using the JT Preferences interface will not modify the
configuration files located in the “etc” folder of the translator install. If the translator
locates the configuration file in the “etc” folder, a configuration file with the changed
settings will be written to the current working directory. If the current working
directory does not have the required file permissions, the configuration file will
be written to the directory defined on Windows by the environment variable
%USERPROFILE% and on UNIX by the environment variable $HOME.
• Convert a JT file to CATPart or CATProduct files.
• Convert a CGR file to a JT file.
• Convert a CATPart or CATProduct file to a JT file.
Note
Converting JT to CGR is not supported using the operating system interface.
Working with the CATIA JT Toolbar

Working with the operating system interface
Use the JT Toolbar to set export and import preferences, to convert JT files to CATPart, CATProduct,
and CGR file types, to insert JT files into a CATIA V5 node, and to save CATPart, CATProducts, and
CGR files as JT files.
The CATIA JT toolbar is a Windows only feature.

Specify preferences for
JT Preferences
exporting or importing files.

Chapter
the translator
Convert JT files to CATPart and

Open a JT file CATProduct files and open them
in the active CATIA session.
Insert a JT file in a CATIA V5
CATProduct node.
Insert a JT file
You can insert the file as a CGR,
CATPart, or CATProduct file.
Save a CATPart, CATProduct,
Save As a JT file or CGR in an active CATIA
session as a JT file.
You can:
• Specify translation preferences.
• Convert JT files to CATIA files.
• Insert JT files as CGR and CATIA files.
• Save CATIA files as JT files.
Specify translation preferences

You can configure common export and import translation parameters by opening a CATIA V5 session
and then using the JT Toolbar to access various options.
1. Open export options by doing the following:
a. From the JT Toolbar, click the JT Preferences icon .
b. From the JT Preferences dialog box, click the Export JT tab, and then choose from the
available preferences.


Chapter
the translator
In this section Choose this option To do this

Select or clear exporting
CATParts and CATProducts
Write JT for to the JT file format.
The default value is on for
both CATIA file formats.
Set the translation of Open
Bodies.
Valid settings include
Geometrical Sets
All, None, or a
<comma-separated list>.
Choose CATIA Entities
The default value is All.
Bodies Select or clear translating
Surfaces these CATIA objects.
Curves
Points The default value for each
PMI object is on.
Select or clear translating
entities when CATIA V5
No Show configured them to not show.
The default setting is off.
Select how you want output
files displayed.
Choose one of the following
options from the list:
Use this
To do this
option
Translate
CATIA data
Single JT into an
Assembly Assembly JT
Select JT Contents File Structure file and to a
and
subfolder JT part file
of JT parts directory.
This setting
is the default.
Translate
CATIA data
All JT in a and display
single file a single file
containing all
of the data.

Translate
CATIA data
Mimic
and display
CATIA files
a JT file for
in a single
each node
folder
in the JT
Assembly.
Translate
CATIA data
Mimic and display
CATIA one output
files and file per
use CATIA original CAD
folders file to mimic
the CAD file
structure.
Select or clear precise model
geometry in translated JT
Include Precise Geometry files.
The default setting is
selected.
Select to display one node
for each geometrical set or
Separate JT node for each one node for each CATPart.
Geometrical Set The default is to clear this
option; that is, to display one
node for each CATPart.
Select to activate an
attempt to recover analytic
Simplify Curves and Surfaces representations of the
to Analytics B-Spline geometry.
See SimplifyGeom option for
further details
Select this option to
optimize the model for
Optimize Model for better downstream usability.
Advanced Settings Downstream Usability
See OptimizeBrep option for
further details.
Specify how parts will be
tessellated.
Relative – Interpret the
Chordal option tessellation value of all parts
relative to the size of the file
and with the same surface
quality.

Chapter
the translator
Absolute – Interpret the

tessellation value as a strict
number of units that are
applied to all parts. The
default value is millimeters.
Specify the number of level
of details for the translation.
Note
While you can
Number of levels select up to ten
levels, three
levels of detail
provide translated
details for most
translations.
Specify level of detail settings

LOD “1” for translated JT files.
For details, see the Note.
Select or clear the translator
to automatically analyze and
Additional LODs for Smooth create two simplified default
Visual Translation levels of detail – a convex
hull and a bounding box.
The default value is on.

Note
The following table represents LOD options and their possible values:
Chordal option = Chordal option =

Relative Absolute
Define the
maximum absolute
distance that a
0(inclusive) to Any value greater
Chordal deviation line segment may
100(inclusive) than 0
deviate from the
smooth curve it is
approximating.
Limit the absolute
maximum angle
between two 0(inclusive) to 0(inclusive) to
Segment angle
adjacent line 180(inclusive) 180(inclusive)
segments in a curve
approximation.
Specify the absolute
0(inclusive) to Any value greater
Segment length length of tessellated
100(inclusive) than 0
chords.
Suppress holes
and arcs smaller 0(inclusive) to Any value greater
Feature removal
than the specified 100(inclusive) than 0
number.
Specify a
minimum level of
simplification for the
model, using the
0(inclusive) to 0(inclusive) to
Triangle reduction first level of detail
100(inclusive) 100(inclusive)
as the starting point.
The setting is a
percentage of the
first level of detail.
Add labels to one or
Name <any_string> <any_string>
more LODs.
2. Open import preferences by doing the following:
a. From the JT Toolbar, click the JT Preferences icon .
b. From the JT Preferences dialog box, click the Import JT tab, and then choose from the
available preferences.

Chapter
the translator
3. Click OK to save the catiatojt.config and jttocatia.config files in the current working directory.
4. Click Cancel to end the JT preferences session without saving the settings.
5. Click Help to open the online Help for JT Bi-directional translator for CATIA V5.
Convert JT files to CATIA
1. From the JT Toolbar, click Open JT file .
2. In the Open JT File dialog box, select the JT file or files you want to convert to CATIA files,
and then click Open.
3. Select your output directory and click OK.
Note
When the conversion is successful, press any key to close the translation window and the
translated files will appear in the CATIA session.
Insert JT files as CGR or CATIA files

1. Choose to insert a CGR or CATIA file by doing the following:

a. From the JT Toolbar, click JT Preferences .
b. Click the Import JT tab and from the Insert JT section, select As CGR or As
CATProducts/CATParts.
2. From an active CATIA V5 session containing an open CATProduct, highlight the CATProduct
node to insert the JT file.
3. From the JT Toolbar, click Insert a JT file .
4. In the Select JT File to Insert dialog box, choose the JT file, and then click Open.
5. Press any key to close the translation window and the translated files will appear in the CATIA
session.
Save CATIA files as JT files
From an active CATIA session, you can save CATPart, CATProduct, and CGR files to JT using options
from the JT Toolbar. You can specify how CATIA files are translated by setting export preferences.
1. Choose how you want the JT file translated by doing the following:
a. From JT Toolbar, click JT Preferences .
b. Click the Export JT tab and make your selections.
2. Open the CATPart or CATProduct that you want to translate and save as a JT file.
3. From the JT Toolbar, click Save As JT file .
4. In the Select Directory for JT Files window, select an output directory and then click OK.
5. Press any key to close the translation window.
Working with operating system interface
Modify with the operating system interface
Using the operating system interface, you can:

• Select files to translation
• Specify the output file directory
• Specify preferences for exporting files
• Specify preferences for importing files

Chapter
the translator
Specify files to translate
1. Open the interface in one of these ways:

• (Windows) Navigate to <translator_installation_directory> and run OS_GUI.bat.
• (UNIX) Navigate to <default_installation_directory> and run OS_GUI.
The JT Bi-directional Translator for CATIA V5 dialog box appears.
2. You can drag JT, CATProduct, CATPart, CATShape, CGR files and drop them onto the list section
of the JT Bi-directional Translator for CATIA V5 dialog box.
3. Alternatively, in the JT Bi-directional Translator for CATIA V5 dialog box, in the Select file(s)
section, click Browse.
4. From Files of Type, select the type of file you want to translate.

5. Select one or more files and click Open.

Your selected files are displayed in the list section of the JT Bi-directional Translator for CATIA
V5 dialog box.
6. (Optional) To remove one or more files from the list, right-click the specific file and then click
Remove graphic.
7. When finished, do one of the following:

• Click OK to launch jt_catiaV5 and end the interface session.
• Click Apply to launch jt_catiaV5, but keep the interface session open.
• Click Cancel to end the interface session.
• Click Help to open the online Help for the JT Bi-directional Translator for CATIA V5.
Specify the output file directory

2. In the JT Bi-directional Translator for CATIA V5 dialog box, select Change Output Folders.
3. If you click Browse, you can use the graphic tools to navigate to the directory of your choice,
and click Open.
If you select Same As Input Directory, the output files are written in the same location as that of
the input files. If the location of the input directory is read-only, then a message box appears.
Click Continue to overwrite the existing files.
Click Cancel to adjust your file selection or output folder choices.

Chapter
the translator
Specify preferences for exporting files

2. In the JT Bi-directional Translator for CATIA V5 dialog box, click JT Preferences.
3. Select the Export JT tab, and then choose from the available preferences.


Chapter
the translator

Select or clear exporting
CATParts and CATProducts
Write JT for to the JT file formats.
The default value is on for
both CATIA file formats.
Set the translation of Open
Bodies.
Valid settings include
Geometrical Sets
All, None, or a
<comma-separated list>.
Choose CATIA Entities
The default value is All.
Bodies Select or clear translating
Surfaces these CATIA objects.
Curves
Points The default value for each
PMI object is on.
Select or clear translating
entities when CATIA V5
No Show configured them to not show.
The default setting is off.
Select how you want output
files displayed.
Choose one of the following
options from the list:
Use this
To do this
option
Translate
CATIA data
Single JT into an
Assembly Assembly JT
Select JT Contents File Structure file and to a
and
subfolder JT part file
of JT parts directory.
This setting
is the default.
Translate
CATIA data
All JT in a and display
single file a single file
containing all
of the data.

Translate
CATIA data
Mimic
and display
CATIA files
a JT file for
in a single
each node
folder
in the JT
Assembly.
Translate
CATIA data
Mimic and display
CATIA one output
files and file per
use CATIA original CAD
folders file to mimic
the CAD file
structure.
Select or clear precise model
geometry in translated JT
Include Precise Geometry files.
The default setting is
selected.
Select to display one node
for each geometrical set or
Separate JT node for each one node for each CATPart.
Geometrical Set The default is to clear this
option; that is, to display one
node for each CATPart.
Select to activate an
attempt to recover analytic
Simplify Curves and Surfaces representations of the
to Analytics B-Spline geometry.
See SimplifyGeom option for
further details
Select this option to
optimize the model for
Optimize Model for better downstream usability.
Advanced Settings Downstream Usability
See OptimizeBrep option for
further details.
Specify how parts will be
tessellated.
Relative – Interpret the
Chordal option tessellation value of all parts
relative to the size of the file
and with the same surface
quality.

Chapter
the translator
Absolute – Interpret the

tessellation value as a strict
number of units that are
applied to all parts. The
default value is millimeters.
Specify the number of level
of details for the translation.
Note
While you can
Number of levels select up to ten
levels, three
levels of detail
provide translated
details for most
translations.

Select or clear the translator
to automatically analyze and
Additional LODs for Smooth create two simplified default
Visual Translation levels of detail – a convex
hull and a bounding box.
The default value is on.
The following table represents LOD options and their possible values:
Chordal option = Chordal option =

Relative Absolute
Define the maximum
absolute distance
that a line segment 0(inclusive) to Any value greater than
Chordal deviation
may deviate from the 100(inclusive) 0
smooth curve it is
approximating.

Limit the absolute

maximum angle
0(inclusive) to 0(inclusive) to
Segment angle between two adjacent
180(inclusive) 180(inclusive)
line segments in a
curve approximation.
Specify the absolute
0(inclusive) to Any value greater than
Segment length length of tessellated
100(inclusive) 0
chords.
Suppress holes and
0(inclusive) to Any value greater than
Feature removal arcs smaller than the
100(inclusive) 0
specified number.
Specify a minimum
level of simplification
for the model, using
the first level of detail 0(inclusive) to 0(inclusive) to
Triangle reduction
as the starting point. 100(inclusive) 100(inclusive)
The setting is a
percentage of the
first level of detail.
Add labels to one or
Name <any_string> <any_string>
more LODs.
Specify preferences for importing files
At this time, the operating system interface supports importing CATProduct and CATPart files.
2. In the JT Bi-directional Translator for CATIA V5 dialog box, click JT Preferences.
3. Select the Import JT tab, and then choose from the available preferences.

Chapter
the translator

Select or clear processing
Bodies CATIA V5 solid bodies.
The default is on.
CATIA V5 curves as wire
CATPart Import Settings Curves frames.
The default is on.
Points CATIA V5 points.
The default is on.
Mapping entities
Entity mapping for CATIA V5 to JT
It may be useful to understand how the translators map various CATIA entities during processing.
Refer to the entity mapping tables for mapping CATIA V5 to JT below.

Data type: wireframe
CATIA V5 JT with XT B-Rep JT with JT B-Rep

Point Point Point
Line Line B-Curve
Circle Circle Arc B-Curve
Ellipse Ellipse B-Curve
Parabola B-Curve B-Curve
Hyperbola B-Curve B-Curve
B-Curve B-Curve B-Curve
Data type: surface geometry
CATIA V5 JT with XT B-Rep JT with JT B-Rep

Open body Sheet body Open body
Facetted
JT Tristripsets optimized by face colors JT Tristripsets optimized by face colors
Body/CGR
Cone Cone B-Surface
Cylinder Cylinder B-Surface
Plane Plane B-Surface
Sphere Sphere B-Surface
Torus Torus B-Surface
Extrusion Swept B-Surface
Offset Offset B-Surface
B-Surface if curve is circle or ellipse;
Revolution B-Surface
otherwise Spun Surface
Other Surface
B-Surface B-Surface
Types
Data type: Supplemental Geometry
CATIA V5 JT
Axis System Coordinate System PMI
Axis Reference Line PMI
Data type: product structure
JT with JT with
CATIA V5
PartHierarchy=CollapseToPart PartHierarchy=ShowOpenBodies
CATProduct JT Assembly JT Assembly
CGR JT Part JT Part
CATPart JT Part JT Assembly
Contents of Geometrical Sets are JT Part for the top level Geometrical
Geometrical Set
transferred to the B-rep Set

Chapter
the translator
Data type: PMI
CATIA V5 JT
Capture Model View
3D Note 3D Notes
Note Object Attribute User Defined Symbol
Datum Datum Feature Symbol
Datum Target Datum Target
Geometrical Tolerance Feature Control Frame
Dimension Dimension
Roughness Surface Finish
Data type: attributes
CATIA V5 JT
Product Properties (Part
Number, Revision, Definition
JT Property
Nomenclature, Source,
Description)
User added properties JT Property
Mass Properties (Density,
Mass, Center of Gravity, JT Property
Moment of Inertia)
CATIA V5 User Parameters
such as Standard Notes,
JT Property
Annotation Notes, Part
Notes
Entity mapping for JT to CATIA V5

It may be useful to understand how the translators map various CATIA entities during processing.
Refer to the entity mapping tables for mapping JT to CATIA V5 below.
Data type: wireframe
JT CATIA V5
Point Point
Line Line
Circle Circle Arc
Ellipse Ellipse
B-spline B-Curve
Data type: surface geometry
JT CATIA V5
Cone Cone

Cylinder Cylinder
Plane Plane
Sphere Sphere
Torus Torus
Swept B-Surface
Offset B-Surface
Revolution B-Surface
Blending B-Surface
B-Surface B-Surface
Other Surface Types B-Surface
Data type: supplemental geometry
JT CATIA V5
Coordinate System Axis System
Reference Line PMI Axis
Data type: product structure
JT CATIA V5
JT Assembly CATProduct (CGR with JT→CGR)
JT Part CATPart (CGR with JT→CGR)
Data type: attribute
JT CATIA V5
JT Property User added property
Understanding the ASCII text file

The ASCII file format consists of a hierarchy of assembly nodes and partition nodes. The format lets
transformation and attribute information be attached to each node.
Indenture Level
When you specify either an assembly node or a partition node, the first column contains the indenture
level of the node. The indenture level indicates the depth of the node in the assembly tree.
Note
The root assembly node always resides at level 0 and the direct children of the root node
reside at level 1. Lines that specify transforms or attributes do not indicate the indenture
level. These properties are attached to the previous assembly or partition node.

Chapter
the translator
Assembly Nodes
Assembly nodes are specified by the keyword ASM followed by the node name contained in double
quotes.
0 ASM "Node name"
Partition Nodes
Partition nodes are specified using two lines. The first line contains the keyword PRT followed by
the node name contained in double quotes. The second line contains the keyword FILE followed by
the file path in double quotes. Either a relative or absolute path may be used. A partition node may
refer to an assembly file or a part file.
1 PRT "Partition name"
File "./pathtopart/part.jt"
Transforms
Transformations may be added to a node using the keyword MATRIX followed by a 4x4 transformation
matrix. The following entry translates -5 units in the X direction, 2 units in the Y direction, and 4
units in the Z direction.
MATRIX [ 1 0 0 0 ] [ 0 1 0 0 ] [ 0 0 1 0 ] [-5 2 4 1 ]
Note
If a matrix is not specified then the identity matrix is assumed.
Attributes
Two types of attributes can be added to a node: regular attributes and hidden attributes. Use the
keyword ATTR to specify a regular attribute and ATTR_H to specify a hidden attribute. Both regular
and hidden attributes require three fields: a type, a key, and a value. The type of field indicates
whether the value is a string, an integer, a floating point number, or a date (keywords: STRING, INT,
FLOAT, DATE). The key identifies the attribute and is associated with a value. The key appears on
the left side of the "attribute" window and the value appears on the right. The following lines specify
four attributes.
ATTR Type="STRING" Key="My String Key" Value="test value"
ATTR Type="INT" Key="My Int Key" Value="3"
ATTR Type="FLOAT" Key="My Float Key" Value="2.1234"
ATTR Type="DATE" Key="Translated" Value="12 31 1998 11 45 30"
Specifications
• The extension on all ASCII Direct Model files is .ajt.
• A node is indicated by placing the indenture level of the node in column 0 followed by the node
type and the node name in double quotes.
• The first node always starts at level 0. It is the only node to reside at level 0.

• The indenture level may only increase by one level at a time when increasing.
• There are no limits on the node level step size when decreasing.
• There are currently only two types of nodes: assemblies and partitions. Assemblies are identified
by the keyword ASM and partitions by the key word PRT. The name of each node immediately
follows each key word and is contained in double quotes.
• Partition nodes must have a file path associated with them. Preceding each file path is the key
word FILE. If a relative path is used, the path must be relative to the output JT file.
• Matrices are indicated with the keyword MATRIX. The matrices are set at 4 x 4 dimensions. If
a matrix is not specified then the identity matrix is assumed.
• Comments may be included by placing a # character in column 0.
• The keywords are case insensitive.
Example file
An example of the ASCII format is given in fishing_reel.ajt. The assembly tree created by this file
is shown below.
Understanding JT files
When you export model files, the translator creates a JT assembly file containing hierarchy, offset,
and other information necessary to assemble the part files of your model. The translator also creates

Chapter
the translator
a subdirectory with the same name as the JT assembly file, and it writes each part of your model to
an individual JT part file that contains all the levels of detail in the subdirectory.
The translator supports part-instancing in the JT assembly files. When you export an instanced
model, the translator writes only one copy of the part geometry to a JT part file, even though the part
may repeat several times throughout the model.
The translator automatically names the JT assembly file according to the name of the model file
that you load in the interface.
Example
When you load a file named formula_car into the translator, it creates a JT assembly
file named formula_car.jt in the specified directory, then creates a subdirectory named
formula_car, for which the part files for the model are written.
Select a JT file version

You can use the JtFileFormat configuration parameter to set the JT version generated by the
Translator. By default, the application sets the current recommended version of JT generated by the
Translator. However, you can also select earlier versions, if necessary.
The following table lists which JT version was introduced for a specific Teamcenter's lifecycle
visualization release.
JT version Teamcenter's lifecycle visualization

8.0 VisMockup 5.0
8.1 Teamcenter's lifecycle visualization 2005
8.2 Teamcenter's lifecycle visualization 2005 SR1
9.0 Teamcenter's lifecycle visualization 2007.2

Note
• JT-based applications are backward-compatible with all earlier JT versions. For
example, Teamcenter's lifecycle visualization 8.1, which introduced JT 10.0, also reads
all 9.x and 8.x JT files.
• JT-based applications are also forward-compatible, provided that all JT versions are
within the same major JT file version. For example, Teamcenter's lifecycle visualization
2007.2, which introduced JT 9.0, also reads JT 9.1, 10.0, 10.0, and 10.0 files, plus
all future minor versions of JT 9.0. However, newer JT file versions may contain data
that is not understood by older viewers. In this case, the non-understood data is not
displayed in the viewer.
Customize text messages

You may find it useful to customize or localize CATIA V5 text messages that are generated during the
translation. You can use the jt_catiav5_messages.txt file to review and customize messages, as
desired. This file is located on the CATIA V5 CD.
Note
• Do not modify the MessageCode syntax because it is alphanumeric and unique to
the code.
• You can modify and customize the MessageString syntax. Be sure to keep format
descriptors within the text in the order they are used. Format descriptors are
programming references such as %s and %d.

Chapter 3: Global Technical Access Center (GTAC)
To report any serious problems about this translator or for help obtaining a license, please contact
the Global Technical Access Center.
Phone:
• USA and Canada: (800) 955-0000 or (714) 952-5444
• Outside the United States and Canada: Contact your local support office.
Website:
You can also log and view existing resolutions for incident reports on the Web at
http://www.siemens.com/plm/support

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.

JT Catiav5 Help

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

JT Catiav5 Help

Uploaded by

Copyright:

Available Formats

SIEMENS

JT Bi-directional translator for CATIA V5 13.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Using the translator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Global Technical Access Center (GTAC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

JT Bi-Directional Translator for Catia V5 13.0 3

JT Bi-directional translator for CATIA V5 13.0

JT Bi-Directional Translator for Catia V5 13.0 1-1

Translating Catia V5 files to JT

Translate CATIA V5 files to JT

• Translating CATIA V5 files from the command prompt

• Locate the configuration file

Modifying Catia V5 to JT translator specific options

Edit translator specific options

2. Edit the configuration file options.

Option Keyword or value Example

JT Bi-Directional Translator for Catia V5 13.0 2-1

LogReporting Note LogReporting = "error"

2-2 JT Bi-Directional Translator for Catia V5 13.0

"cat_file, cat_ext, user, pid,

ConsoleReporting Note ConsoleReporting = "error"

3. Save the configuration file with a .config extension.

JT Bi-Directional Translator for Catia V5 13.0 2-3

Display one node for each geometrical set.

2-4 JT Bi-Directional Translator for Catia V5 13.0

Add _CATPart to JT part files if there is an

none Prevent changes to the names of the nodes.

JT Bi-Directional Translator for Catia V5 13.0 2-5

2-6 JT Bi-Directional Translator for Catia V5 13.0

JT Bi-Directional Translator for Catia V5 13.0 2-7

• When AssySearchCriteria includes AssySearchPath, ensure that AssySearchPath option

• You must also set AssySearchCriteria to contain AssySearchPath.

2-8 JT Bi-Directional Translator for Catia V5 13.0

• A tolerance of 1.0e-6 meters will be used for optimizing the Brep.

{"error" "warning" "info"} Note

JT Bi-Directional Translator for Catia V5 13.0 2-9

2-10 JT Bi-Directional Translator for Catia V5 13.0

Select a combination of error message types

{"error" "warning" "info"} Note

• A tolerance of 1.0e-6 meters will be used for simplifying the geometry.

• Make sure the specified file is in the same format as <

JT Bi-Directional Translator for Catia V5 13.0 2-11

• When TransparencyQuality = “low”, all non-zero transparency values in CATIA V5 will be

Modifying Catia V5 to JT general setup options

Edit general setup options

Option Keywords Example

2-12 JT Bi-Directional Translator for Catia V5 13.0

chordalOption "RELATIVE" "ABSOLUTE" chordalOption = "RELATIVE"

3. Save the configuration file with a .config extension.

JT Bi-Directional Translator for Catia V5 13.0 2-13

Use this argument To

The default value is

2-14 JT Bi-Directional Translator for Catia V5 13.0

Use this argument To

JT Bi-Directional Translator for Catia V5 13.0 2-15

Option Resulting JT files

2-16 JT Bi-Directional Translator for Catia V5 13.0

Use this argument To do this

• For some translators, choose

"JTPARTS" Export data translated as parts.

• Enabling both PLMXML

JT Bi-Directional Translator for Catia V5 13.0 2-17

Export Assembly structure as STEP AP242

Use this option To export