<!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>Translating NX Assemblies</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_topic2" id="xps10_pagetitle">Translating NX Assemblies</div>
      <hr noshade="true">
      <div class="title_division">Native NX Assemblies</div>
      <p class="para_division">Translated JT files are stored in the same location as the NX assembly they represent. They are named the same as the NX part with the addition of &quot;_[refsetname]&quot; to the end of the name and the JT suffix.</p>
      <p class="para_division">You can use the -force_output_dir option to send the resulting JT files to a specific directory.</p>
      <p class="para_division">When using the -generate_assy_jt option and the -force_output_dir option together, the component JT files and assembly.jt file are output to the same location. Normally, the -generate_assy_jt option outputs the assembly.jt file to the current working directory or to the location specified by the -generate_assy_jt={location} option. Used together, the -generate_assy_jt option assumes the location specified in the -force_output_dir option for the assembly.jt file.</p>
      <p class="para_division">Once the files are written to a specific location, you should not move or rename them. Their location and naming is important information that is used by the interoperation function and the translator to locate existing JT files for a particular NX component.</p>
      <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">You will require write access to the directory containing the NX assembly being translated.</p>
               </div>
            </td>
         </tr>
      </table>
      <div class="title_division">Teamcenter Integration for NX Assemblies</div>
      <p class="para_division">Parts that are already stored in Teamcenter Engineering can be translated. They are identified using the syntax &quot;@DB/Item/Rev.&quot;</p>
      <p class="para_division">For example, &quot;@DB/123456/B&quot; translates revision B of the NX master associated with the 123456 item, and &quot;@DB/123456/B/spec/DWG 1&quot; translates the NX part &quot;DWG 1&quot; attached using the specification relation to revision B of item 123456.</p>
      <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 View3D button in Teamcenter Engineering-Web does not correctly process assembly JT datasets for non-master NX datasets.</p>
               </div>
            </td>
         </tr>
      </table>
      <p class="para_division">The JT files generated by the translation are automatically stored in Teamcenter Engineering inside a DirectModel dataset. This dataset is associated by a rendering relation to the NX dataset that generated it. The name of the JT file produced is the name of the reference set that was translated.</p>
      <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">In a standard Teamcenter Engineering installation it is possible to add a rendering relation to a released dataset or item revision, thereby allowing assemblies that have already been released, to be translated.</p>
               </div>
            </td>
         </tr>
      </table>
      <p class="para_division">If the model reference set is being translated, a &quot;$&quot; designation is added to the JT file. This allows Teamcenter Engineering to make an informed decision about which JT file to download, in case there are multiple files associated with a particular NX part and the request for the JT file is unclear.</p>
      <div class="title_division">Store Translated JT Files Outside Teamcenter Engineering</div>
      <p class="para_division">The translator provides a -save_outside_iman option that enables a Teamcenter Engineering part or assembly to be translated, with the resulting JT files stored outside Teamcenter Engineering. Here, the JT files are created in the current directory or the directory specified if the -force_output_dir option is used. The files produced are named according to the item revision, NX dataset name, and reference set.</p>
      <div class="title_division">Naming files outside Teamcenter Engineering</div>
      <p class="para_division">The ugtopv translator supports translating a NX assembly that is stored in Teamcenter Engineering while saving the component jt files (and the generated bookmark or assembly jt file) in the file system (outside of Teamcenter Engineering).</p>
      <p class="para_division">To do this, the jt files are constructed by:</p>
      <p class="para_division">[ITEM ID]_[ITEM REV]_[UGDATASET_TYPE]_[DATASET NAME]_[REFSET NAME].jt</p>
      <p class="para_division">For example:</p>
      <p class="para_division">123456_A_alt_a_PART.jt</p>
      <p class="para_division">The jt files created by this method are stored in the current directory.</p>
      <p class="para_division">If a bookmark or assembly jt is being generated, the bookmark or assembly jt refers to these jt files. This provides a way of having a representation of the whole assembly outside Teamcenter Engineering.</p>
      <p class="para_division">You can leave some of these values blank. For example, when translating the UGMaster dataset, you can use:</p>
      <p class="para_division">123456_A___PART.jt</p>
   </body>
</html>