V5 JT Doc
V5 JT Doc
Contents
USER GUIDE
Version 24.0
Revision: 1.0
Issued: 19/04/2021
Contents
Overview of TRANSLATE ............................................................................................................ 3
Save As JT............................................................................................................................. 26
Open JT Data........................................................................................................................ 27
Appendix A – CATIA V5 Configuration ..................................................................................... 28
Introduction ......................................................................................................................... 28
Conventions ......................................................................................................................... 28
CATIA V5 Installation Directory ........................................................................................... 28
CATIA V5 Environment DIRENV & ENV................................................................................ 29
Checking the CATIA V5 Environment .................................................................................. 30
Checking the Theorem Shared Library ................................................................................ 30
Appendix B – JT Configuration File .......................................................................................... 30
Introduction ......................................................................................................................... 30
The Setup Section ................................................................................................................ 31
The Level of Detail Section .................................................................................................. 33
The Filter Section ................................................................................................................. 34
The Metadata section.......................................................................................................... 35
The Special Section .............................................................................................................. 36
Overview of TRANSLATE
About Theorem
We are proud that the vast majority of the world's leading Automotive, Aerospace, Defense,
Power Generation and Transportation companies and their Supply chains use our products
and services daily. Working closely with our customers, to both fully understand their
requirements and feed their input into our development processes has significantly
contributed to our technology and industry knowledge.
TRANSLATE
PUBLISH
VISUALIZE
Visualization for Augmented (AR), Mixed (MR) and Virtual (VR) Reality
applications
The CATIA V5-JT Translator is a bi-directional direct database converter between the
Dassault Systèmes CATIA V5 Modelling Application and the JT file format, used by the
Siemens Teamcenter Visualization products.
It enables the user to convert all forms of 3D Mechanical Design Geometry and Assembly
data, together with system defined attribute information, colour information, between
these two systems. This product is designed for companies using CATIA V5 who have
selected JT to be their main method of collaboration and communication between OEMs
and their customers or suppliers.
It is also a major method of visualization and therefore companies using JT based solutions
need to translate their CATIA V5 data into the JT format.
The translator can be invoked in either an interactive or batch mode with the command line
interface allowing the conversion process to be integrated into any process oriented
operation. Alternatively from Theorem R18 the conversion process may be operated by
using the new Theorem Unified Interface.
• The conversion process can be run Interactively, Batch Mode or using the new
Unified Interface
• Uses the CATIA V5 API and Siemens JTOpen API to read and write data.
• Reduce costs due to processing time and increase overall conversion success levels
by filtering input data and focusing the conversion to only those elements required.
• Reduce costs and risks associated to accessing the wrong version of data by
integrating the conversion process into a related business processes.
• With over 20 years of industrial use Theorem translation products robustness and
quality is well proven, reducing your business risk.
This document will focus specifically on guidance for the use of the Visualize 3D for CATIA V5
– JT product. For information regarding any of Theorem’s product ranges please contact
[email protected]
Getting Started
Documentation & Installation Media
The latest copy of the User Guide documentation can be found on our web site at:
http://www.theorem.com/Documentation
Each product has a specific link that provides user documentation in the form of PDF and
Tutorials.
The latest copy of Theorem software can be found via the link above and by searching for
the specific product. Each product has a specific link to the Product Release Document,
which contains a link to the download location of the installation CD.
Alternatively, you can request a copy of the software to be shipped on a physical CD.
Installation
The installation is run from the .msi file download provided. For full details of the installation
process, visit www.theorem.com/documentation and select UI from the product selection
list.
License Configuration
To run any product a valid license file is required. The Flex License Manager is run from the
.msi file download provided. For full details of the installation process, visit
www.theorem.com/documentation
Alternatively, the Unified Interface can be run via a Windows Explorer selection in:
<UI_installation_directory>\bin\Unified_Interface.cmd
The default layout is split into 4 primary areas, which can be altered to the users prefer:
Translation Active
Activity Configurations
Output File
Logs Browser
On completion, the Unified Interface will display the activity information and details from
the log file created during the translation, if requested, in the Translation Activity and
Output Log panes, respectively.
The generated output data can be located by selecting the translation from the Activity pane
and opening the output folder:
The format of the command is as follows when translating from JT to CATIA V5:
(Note! Replace the [XX] seen in the example with the version of CATIA V5 you are using. E.g.
for CATIA V5 R31, change to CATIA531):
The example above will translate a CATIA V5 sample file provided within the installation and
finish with the following screen output when successful:
C:\Temp\pump_assy.jt
Translator Customization
The Theorem translator allows the information that is read from the source system and
written to the target system to be tailored via a set of user specified arguments. Commonly
used arguments are supported via the Unified Interface, with Advanced Arguments being
described within this document for use in the Unified Interface or via the Command Line
invocation.
• CATIA V5 Read – Those arguments that affect how data is read from CATIA V5
• JT Write – Those arguments that affect how the data is written to JT
• Entity Mask – Those arguments that allow specific read entities to be masked
• General – Those arguments that are common to ALL Publishing activities
regardless of source data
The image below shows the CATIA V5 Read arguments that are available, with their default
settings:
Read A secondary argument to ‘Read PMI’ and allows the control over whether
Captures captures are read as part of the process. Default is ON when ‘Read PMI’ is
marked as ON.
o Command Line Syntax:
read_captures
dont_read_captures – to turn off
JT Write Arguments
The image below shows the Write JT arguments that are available, with their default
settings:
Option Description
Option Description
Mask File Specifies the Mask File to be written to, that can be
referenced by future translations. A Mask file MUST be
specified if masking is required. The first line in this file is
OFF ALL ENT:
o Command Line Syntax:
Mask <filename>
Entity Types Translated Specifies a selection list from which to select which entity
types are to be processed. The following types are
available: "POI","CUR",”SKI”,"SOL",”ISO”,"TEX","AXI"
o Command Line Syntax:
Add any of the above to the
specified mask file, one entry per
line prefixed by the word ON, e.g.:
ON POI
to ensure they are considered in the
translation
Layers Translated Specifies a selection list from which to select which layers
are to be processed.
o Command Line Syntax:
A single entry of ON ALL LAY must
precede any Layer Mask command.
Add a list or range of numbers
representing layer to be processed
Option Description
Picture showing typical CATIA V5 3D Dimensions and Annotations. Note, in the upper
dimension the dimensions values 5.000 +- .008 are created using a filled text font. The
characters “ST” in the frame are created using an unfilled stick font.
Picture showing the reorientation of the model with the text also reoriented. Note the text
characters have been rotated 180 degrees and are now readable with filled character
representation.
To recreate the JT filled text using simple polygons, rather than JT text glyph
representations, use the options pmi_glyphs_off pmi_polygons together. The output
representation will appear filled and look correct when viewed in the authored orientation.
However, filled text created with simple polygons, will not display correctly if the data is
reoriented and the text switching in JT is selected. The picture below shows an example of
Picture showing JT PMI with filled text rendered in outline only. Note the option
pmi_glyphs_off also removes the filled arrowhead rendering.
If you would prefer to maintain filled arrowheads and only impact the characters to be
recreated in outline mode, then use the option dont_fill_pmi_text instead of the option
pmi_glyphs_off. The resultant output is shown in the picture below with the text drawn in
outline and the arrowheads filled.
JT Read Arguments
The image below shows the JT Read arguments that are available, with their default settings:
Option Description
Option Description
The image below shows the General arguments that are available, with their default
settings:
Option Description
read_geometry_edges CATIA V5 allows the display of shaded surfaces and edges. This
option allows the translator to mimic this for FTA construction
geometry by promoting the edge curves to standalone
wireframe.
JT Advanced Arguments
Argument Description
This requires an additional software download and is documented within that download.
Please contact [email protected] for more information.
In order to translate from within CATIA V5, the CATIA V5 application must be started from
within a Theorem environment, so that the appropriate CATIA V5 menus are loaded.
<installation_directory>\bin\catia5r[version]_start.cmd
(where [version] should be substituted for the version of CATIA V5 that you have installed –
e.g. 28, 29, 30, 31):
Save As JT
Once CATIA V5 has been started it is possible for a model to be saved to JT. To do this, the
user selects the File -> Save As Menu Option. From the file browser window that opens,
change the ‘Save as type’ option to be jt (*.jt).
To add a user defined configuration to the process (created from the Theorem UI), this can
be selected from the Tools>Options>Infrastructure>Theorem>CAA Export JT menu. The
process will then use this defined configuration to create the JT data as required.
Open JT Data
Once CATIA V5 has been started it is possible for a model to be imported from JT using the
File -> Open menu. Once selected, find the JT data you wish to import into CATIA V5 and
select it from the file browser. When ready, press the ‘Open’ button from the menu to
import.
To add a user defined configuration to the process (created from the Theorem UI), this can
be selected from the Tools>Options>Infrastructure>Theorem>CAA Import JT menu. The
process will then use this defined configuration to create the JT data as required.
Conventions
Release of CATIA V5
To indicate a release of CATIA V5 the notation <XX> shall be used. This needs to be replaced
with the specific release to be used i.e. 28, 29, 30, 31.
Having selected the CATIA V5 installation directory via the browse button, the installation
process will record the location of the CATIA V5 installation directory in the ts_env.bat file.
This file is located in the Theorem translator installation directory. If the location of CATIA V5
subsequently changes, the translator can be guided to the changed location by modifying
this file using a text editor to modify the ts_env.bat that is located in the translator
installation directory.
If no entry is included for DSLICENSING a warning dialog will be displayed which warns of the
empty field. Selecting Yes to continue will allow the installation to continue.
<Translator_Installation_Directory>\bin\catia5r<XX>_start.cmd
Once CATIA has been run the Translator can run as described in the relevant product User
Guide.
Windows 10:
C:\ProgramData\DassaultSystemes\CATEnv
Or
%APPDATA%\CATEnv
%CATIAV5_INST%\<OSDS>\code\bin\setcatenv -h
If when installing CATIA V5 the default environment file location was replaced with another
location then this location needs to be indicated to the Translator by defining in the
ts_env.bat the environment variable CATIAV5_DIRENV:
set CATIAV5_DIRENV=/some/directory
If the Theorem installation is needed to support multiple releases of CATIA. Then the user
can define release specific locations using:
set CATIAV5R<XX>_DIRENV=/some/directory
The Theorem translator will attempts to create its own environment file called
TheoremCatia5R<XX>.txt. The user must therefore have write permission to the CATEnv
directory. If this is not possible an existing environment file can be specified using the
variable CATIAV5_ENV. e.g.
set CATIAV5_ENV=CATIA.V5R31.B31
Note. the extension .txt is not required. The user can specify a release specific name using
CATIAV5R<XX>_ENV e.g.
set CATIAV5R31_ENV=CATIA.V5R31.B31
%TS_INST%\bin\checkcatia5r<XX>env.cmd
%TS_INST%\bin\checkcatia5r<XX>cadverter.cmd
A successful output is an indication that the location for CATIA V5 has been specified to the
Theorem translator correctly and that the correct version of the Theorem CATIA V5
translator products have been installed.
The JT configuration file contains various sections, each containing different settings based
on the section.
"FULL_SHATTER"
WriteWhichFiles "ALL" WriteWhichFiles = "ALL"
"ASSEMBLY_ONLY"
"PARTS_ONLY"
compression true compression = true
false
FALSE
triStripOpt true triStripOpt = false
TRUE
false
FALSE
seamSewing true seamSewing = true
FALSE
seamSewingTol any integer seamSewingTol = 0.001
includeBrep true includeBrep = false
TRUE
false
FALSE
brepPrecision "SINGLE" brepPrecision = "SINGLE"
"DOUBLE"
autoNameSanitize true autoNameSanitize = true
TRUE
false
FALSE
updateChangedPartsOnly true updateChangedPartsOnly =
false
TRUE
false
FALSE
verboseReporting true verboseReporting = false
TRUE
FALSE
writeAsciiAssembly true writeAsciiAssembly =
false
TRUE
false
FALSE
singlePartsNoAssem true singlePartsNoAssem =
false
TRUE
false
FALSE
smartLODgeneration true smartLODgeneration = true
TRUE
false
FALSE
autoLowLODgeneration true autoLowLODgeneration =
true
TRUE
false
FALSE
numLODs any integer numLODs = 3
close brace } }
This section consists of several sets of level of detail (LOD) information, and the number of
these sets depends on the number you specified on the numLODs line in the configuration
file.
Note: Be sure to add these options to the configuration file in pairs: one line to define the
metadata key and one line to define the metadata value.
AddToAssemblies = "<metadata
value>"
AddToAllNodes "string of AddToAllNodes = "<metadata
characters" key>"
AddToAllNodes = "<metadata
value>"
close brace } }
false
FALSE
false
FALSE
false
FALSE
false
FALSE
false
FALSE
cm
centimetres
metre
metres
inches
feet
yards
inputUnits
false
FALSE
read_pmi_1
read_pmi_3
false
false
FALSE
SOLtoDetail
toSets
toPart
SURandFACtoD
etail
toPartOptimi
zed
false
FALSE
Windows example
useExeInAssemblyScript =
X:\users\translation\exena
me.exe
Windows example
useLogDirInAssemblyScript
=
X:\users\translation\logDir
Windows example
zPart =
X:\users\translation\tessPar
t.config
structureOutputType JT structureOutputType JT
= JT
PLMXML
PLMXMLJT
brepType JT brepType = XT JT
XT
XTJT
false
FALSE
false
FALSE
false
FALSE
false
FALSE
false
FALSE
false
FALSE
false
FALSE
false
FALSE
false
FALSE
false
FALSE
TRUE
false -
process
wireframe as
tessellation
false
FALSE
false
FALSE
false
FALSE
false
FALSE
false
FALSE
false
FALSE
false
FALSE
false
FALSE
false
FALSE
false
FALSE
false
FALSE
false
FALSE
false
FALSE
Structure
All
false
false
FALSE
false
FALSE
false
FALSE
false
FALSE
Spheres
All
false
FALSE
false
FALSE
false
FALSE
false
FALSE
false
FALSE
false
FALSE
false
FALSE
false
FALSE
false
FALSE
false
false
FALSE
false
FALSE
false
FALSE
false
FALSE
FALSE
false
FALSE
false
FALSE
close brace } }