<!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>Introduction</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">Introduction</div>
      <hr noshade="true">
      <table cellspacing="4" align="center">
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td">Overview</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td"><a class="links" href="javascript:void(0)" onclick="top.openFile('dataexchange/get_started.html');return(false);">How To</a></p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td"><a class="links" href="javascript:void(0)" onclick="top.openFile('dataexchange/main_dialog.html');return(false);">Options</a></p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td"><a class="links" href="javascript:void(0)" onclick="top.openFile('dataexchange/how_do.html');return(false);">Related Topics</a></p>
            </td>
         </tr>
      </table><br><p class="para_topic">Welcome to the NX Data Exchange product suite documentation. </p>
      <p class="para_topic">Although each NX Data Exchange product &ndash; IGES, STEP, DXF/DWG, CATIA V4, CATIA V5, or Pro/E to NX &ndash; has a separate user interface, they all have many common concepts and dialog boxes.</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 translators are constructed in such a way to maximize your ability to have multiple translations going on, each with their own special control parameters. We can achieve this capability by creating independent tools that can pass information via temporary or permanent files.</p>
               </div>
            </td>
         </tr>
      </table>
      <p class="para_topic">The user interface for each translator is a collector of information needed to run the translator. This information contains what files to translate, how to control the translation process, how to map/interpret information during the translation, how to filter information, and what tolerances to use. You can save these settings to permanent files for use in subsequent translation activities. However, each time the user interface starts a translation, it will write the current settings to a temporary file, and pass the name of this temporary file to the translator process it starts.</p>
      <p class="para_topic">The actual translation process &ndash; runs as separate process from the user interface process. This means you can start a translation (processing multiple files) and not have to wait for it to complete before initiating a second translation.</p>
      <div class="title_division">Base NX parts</div>
      <p class="para_division">When importing data into NX, some translators use a base part to which imported data is added during translation. The base part has part-specific preferences and options defined so that the resulting part will have the same characteristics as NX parts created natively.</p>
      <p class="para_division">NX supplies a base part for both Metric and English for each translator in each translator's installation directory. These parts are automatically used when a translation is started. You can change the settings and options in these parts, but be aware that all future translations (by any user) will use the modified base part. You can modify a base part for yourself or for a local group by following the instructions in <a class="links" href="javascript:void(0)" onclick="top.openFile('dataexchange/how_do.html');return(false);">How Do I?</a></p>
      <div class="title_division">Translator messages</div>
      <p class="para_division">When the translators execute, they will write information to a log file. The name of the log file displays on the main dialog box. It creates in the directory where the translated files are created. It is named similar to the first file in the list of files to translate, but with a &lt;.log&gt; extension.</p>
      <p class="para_division">Log file information consists of a summary of the entities processes as well as any warnings or problems encountered in the translation. Each file (in a list of files) that was translated will have its own section in the log file. Normally, you will not have to review this file, but it is there for investigation when needed.</p>
      <div class="title_division">Additional Help</div>
      <p class="para_division">There is a <a class="links" href="javascript:void(0)" onclick="top.openFile('dataexchange/how_do.html');return(false);">How Do I?</a> topic in this Help. However the most recent Tips &amp; Techniques, as well as updates on any problems found are documented on line at <a class="links" href="javascript:void(0)" onclick="top.openFileURL('http://www.ugs.com');return(false);">UGS</a>.
      </p>
   </body>
</html>