<!DOCTYPE html
  PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<!--
Copyright (c) 2006 UGS Corp.

All Rights Reserved.

This software and related documentation are proprietary to UGS Corp.
-->
<html>
   <head>
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <title>JT files in Teamcenter Engineering</title>
      <script language="javaScript">
        abridged="false";
        displayConditions=new Array();
      </script>
      <link type="text/css" href="../css/main_styles.css" rel="stylesheet">
   </head>
   <body class="bodydocs" onload="top.pageLoader()" bgcolor="#FFFFFF">
      <div class="title_topic4" id="xps10_pagetitle">JT files in Teamcenter Engineering</div>
      <hr noshade="true">
      <p class="para_topic">JT files are managed in Teamcenter Engineering in conjunction with Teamcenter Integration for NX.</p>
      <p class="para_topic">Using Teamcenter Engineering version 5.1.0.4 or later, the files generated during save from NX or by the ugtopv translator are automatically uploaded to Teamcenter Engineering.</p>
      <p class="para_topic">Each NX dataset in the ItemRevision can have a corresponding DirectModel dataset with a rendering relation between the NX dataset and the DirectModel dataset. The JT file generated is placed in the DirectModel dataset with the file named the same as the reference set (the name &quot;NONE&quot; is used if no reference set was specified and the entire geometry was tessellated). For example, if &quot;PART&quot; is the model reference set name, the JT file name in the DirectModel dataset is called PART.jt.</p>
      <p class="para_topic">If the NX dataset is a UGMASTER, then the DirectModel dataset is also attached to the ItemRevision using a rendering relation.</p>
      <div class="title_division">Model reference set</div>
      <p class="para_division">If the reference set that generated the JT file was the model reference set, the file is tagged with a &quot;$&quot; character. Taking the above example, the JT file name in the DirectModel dataset would be PART$.jt. By this method, the master JT file can be identified in the case where there is more than one JT file in the dataset.</p>
      <div class="title_division">Dataset UID</div>
      <p class="para_division">When Teamcenter Visualization accesses jt files stored in Teamcenter Engineering, the preferred method is to use the unique identifier (UID) of the rev0 (i.e., latest version) DirectModel dataset and the name of the reference set (which identifies the file requested). This is preferred because it's faster than looking up via the ItemRev - UG dataset - DirectModel dataset route.</p>
      <p class="para_division">Where possible, the dataset UID is cached in the NX part file (e.g., when generating the jt file on save). However, in cases where jt files are generated without being able to modify the NX part (e.g., when translating using the ugtopv translator), the UID is not cached in the part so the jt file is located (more slowly) by following the ItemRev - UG dataset - DirectModel dataset route.</p>
      <p class="para_division">Because the latest version of the dataset is used, it's possible to modify the component part and save a new jt file. Any saved bookmarks or saved jt assemblies will continue to reference the latest component geometry (within a specific item revision).</p>
      <div class="title_division">Multiple JT Files For a Part File</div>
      <p class="para_division">While a 1-to-1 correspondence between the NX part and the jt file is the most common situation, there are some situations in which you can get more than one jt file per part file. One case is where you have modeled the left-hand and right-hand geometry in the same part file. To support this, NX has provided the Assemblies_AdditionalModelRefSets option in the user defaults file. This feature allows the left-hand and right-hand geometry to be saved in separate jt files.</p>
      <p class="para_division">For example, for the part fender.prt, the jt files generated for NX are:</p>
      <ul>
         <li>
            <p class="para_item">fender_LEFT.jt</p>
         </li>
         <li>
            <p class="para_item">fender_RIGHT.jt</p>
         </li>
      </ul>
      <p class="para_division">If you're using Teamcenter Integration for NX, in the DirectModel dataset you would have:</p>
      <ul>
         <li>
            <p class="para_item">PART$.jt</p>
         </li>
         <li>
            <p class="para_item">LEFT.jt</p>
         </li>
         <li>
            <p class="para_item">RIGHT.jt</p>
         </li>
      </ul>
      <table border="0">
         <tr>
            <td valign="top" align="left"><img align="left" src="../graphics/note.gif" alt="Note" title="Note"></td>
            <td valign="bottom" align="left" width="100%">
               <div class="para_note">
                  <p class="para_note_body">The &quot;$&quot; character indicates the model reference set.</p>
               </div>
            </td>
         </tr>
      </table>
      <div class="title_division">Locating the JT File</div>
      <p class="para_division">When given the name of a reference set (and the dataset UID), Teamcenter Engineering provides the JT file using the following rules:</p>
      <ol type="1" start="1">
         <li>
            <p class="para_item">If a jt file matching the reference set name exists, it's returned, else</p>
         </li>
         <li>
            <p class="para_item">If a single jt file exists, it's returned, else</p>
         </li>
         <li>
            <p class="para_item">If a jt file is marked as being the master by the $ designation, it's returned, else</p>
         </li>
         <li>
            <p class="para_item">Nothing is returned.</p>
         </li>
      </ol>
      <div class="title_division">Assembly JT Files in Teamcenter Engineering</div>
      <p class="para_division">Assembly jt files are stored in Teamcenter Engineering using the same naming conventions for the datasets and the same attachments to the NX dataset and Item Revision as component jt files.</p>
      <p class="para_division">When using the ugtojt or ugtopv translator to generate the jt file, it's named TopOfAssembly.jt in the dataset.</p>
      <p class="para_division">When you select the View 3D button on a dataset, Teamcenter Visualization is launched with the jt file in that dataset. If there is more than one jt file in the dataset, it looks for a file called TopOfAssembly.jt and then follows the same rules for component jt files.</p>
      <p class="para_division">To export JT files (assemblies and components) from Teamcenter Engineering, use the ugtopv translator with the following options together to write JT files for the components to the current directory:</p>
      <ul>
         <li>
            <p class="para_item">-pim=yes</p>
         </li>
         <li>
            <p class="para_item">-save_outside_iman</p>
         </li>
      </ul>
      <p class="para_division">To specify a different location to write the files, use the following option:</p>
      <ul>
         <li>
            <p class="para_item">-force_output_dir</p>
         </li>
      </ul>
      <p class="para_division">To create a bookmark or assembly jt file in the same directory, use the following options:</p>
      <ul>
         <li>
            <p class="para_item">-generate_bookmark</p>
         </li>
         <li>
            <p class="para_item">-generate_assy_jt</p>
         </li>
      </ul>
   </body>
</html>