<!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>Exporting NX models to ECAD</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_topic3" id="xps10_pagetitle">Exporting NX models to ECAD</div>
      <hr noshade="true">
      <p class="para_topic">There are two ways to export an NX model to ECAD:</p>
      <ul>
         <li>
            <p class="para_item">In NX, select the PCB.xchange toolbar icon Export ECAD Model. </p>
         </li>
         <li>
            <p class="para_item">In the PCB.xchange window, choose <b class="uiTerm">Read NX Model</b> to import the PCB assembly, then choose <b class="uiTerm">Write ECAD Model</b>. 
            </p>
         </li>
      </ul>
      <p class="para_topic">The first method is simpler, while the second provides more functionality.</p>
      <div class="title_division"> Exporting with the PCB.xchange Toolbar</div>
      <p class="para_division">Start with the model open in NX. The NX model must be an assembly that matches the requirements for ECAD translation. Models that are created by choosing <b class="uiTerm">PBC.xchange</b>&rarr;<b class="uiTerm">Import ECAD Model</b> in NX, or <b class="uiTerm">File</b>&rarr;<b class="uiTerm">Write</b>&rarr;<b class="uiTerm">Write NX Model</b> in PBC.xchange generally satisfy these requirements. For models created from scratch in NX, certain requirements must be met; these are discussed in the PCB.xchange toolbar article <a class="links" href="javascript:void(0)" onclick="top.openFile('pcb/02topic_3.html');return(false);">Defining a PCB Assembly</a>. Before exporting, it is good practice to validate the assembly by selecting <b class="uiTerm">Info/Validate PCB Assembly</b> on the PCB.xchange toolbar, and correct any errors.
      </p>
      <p class="para_division">Once the NX model is checked for errors, select <b class="uiTerm">PCB.xchange</b>&rarr;<b class="uiTerm">Export ECAD Model</b>. After entering the IDF board file name and path, specify whether you want to include the whole assembly or only the board. Select the IDF format and units, and specify the entity filter if any. If you want to view the log file when the write operation is complete select  <b class="uiTerm">Show Log</b>. This file is stored in the scratch directory defined on the File Settings dialog box.
      </p>
      <p class="para_division">Select Use Entity Filter check box, and scroll the list box to select the entity filter name(s) you wish to apply to the ECAD Write operation. You can also create your own filters which will appear on the list the next time you start PCB.xchange; see <a class="links" href="javascript:void(0)" onclick="top.openFile('pcb/xu_filter.html');return(false);">Working with Entity Filters</a> for details.
      </p>
      <div class="title_division"> Exporting from the PCB.xchange window</div>
      <div class="title_division"> Reading an NX Model into the PCB.xchange window </div>
      <p class="para_division">To open NX models of PC boards or PCB assemblies in preparation for translation to ECAD, select <b class="uiTerm">File</b>&rarr;<b class="uiTerm">Read</b>&rarr;<b class="uiTerm">Read NX Model</b>. When the Read command is executed, the board geometry, drilled holes and restriction areas, as well as component footprint, placement and orientation are loaded into PCB.xchange and checked for modeling errors and ECAD compatibility. The PCB Assembly appears in the graphics window. 
      </p>
      <p class="para_division">The NX model must be an assembly that matches the requirements for ECAD translation. Models that are created by the PCB.xchange command Write NX Model generally satisfy these requirements. For models created from scratch in NX certain requirements must be met; these are discussed in the PCB.xchange toolbar article  <a class="links" href="javascript:void(0)" onclick="top.openFile('pcb/02topic_3.html');return(false);">Defining a PCB Assembly</a>.
      </p>
      <p class="para_division">While the file is in PCB.xchange, you can control the display in different ways to facilitate visual inspection. You can also automatically generate and view an information file that summarizes and validates the PCB Assembly for ECAD compliance and reports any errors in format. You can also generate a report that compares the assembly to previous or subsequent versions, or use PCB.xchange to automatically update an obsolete version of the assembly based on the currently loaded version (see Managing Assembly Updates).</p>
      <div class="title_division"> Writing an ECAD file from the PCB.xchange window</div>
      <p class="para_division">Once the NX model is checked for errors, writing an ECAD file is an automated procedure. After entering the ECAD board file name and path, specify whether you want to include the whole assembly or only the board. Select the IDF format and units, and specify the entity filter, if any. When the write operation is complete, a completion message appears and any errors are listed. </p>
      <p class="para_division">Select the <b class="uiTerm">Use Entity Filter</b> check box and click the <b class="uiTerm">Filters List</b> button. Scroll the list to select the entity filter name(s) you wish to apply to the ECAD Write operation. You can also create your own filters which will appear on the list the next time you start PCB.xchange; see  <a class="links" href="javascript:void(0)" onclick="top.openFile('pcb/xu_filter.html');return(false);">Working with Entity Filters</a> for details.
      </p>
      <div class="title_division"> Setting the default filter(s)</div>
      <p class="para_division">Some filters may be previously selected by default; you may wish to change these defaults. To save the default selection of filter(s) as well as the default setting for  <b class="uiTerm">Use Entity Filter</b> you must copy the file %MAYA_PCB_DIR%/pcbx_ug.ini ($MAYA_PCB_DIR/pcbx_ug.ini on UNIX), and place the copy in the working directory or your home directory. Then, choose <b class="uiTerm">File</b>&rarr;<b class="uiTerm">Settings</b> and click the <b class="uiTerm">Save Settings</b> button. The current settings in the Write ECAD Model dialog box is saved into the <i class="fileName">pcbx_ug.ini</i> file you duplicated, and PCB.xchange reproduces the settings by reading the<i class="fileName"> pcbx_ug.ini</i> file during startup.
      </p>
      <p class="para_division">When you click  <b class="uiTerm">Save Settings</b> in the File Settings dialog box, PCB.xchange first looks for the file <i class="fileName">pcbx_ug.ini</i> in the working directory. If the file is not there, it looks in the user's home directory. If it is not there, it uses the file in the PCB.xchange installation.
      </p>
      <p class="para_division">The working directory is defined as the directory from which PCB.xchange is launched, typically the same directory from which NX is launched. The home directory is an environment variable typically defined by a system administrator for a specific user.</p>
      <div class="title_division"> Transferring component geometry with PCB.xchange</div>
      <p class="para_division">In IDF, there are two files that contain data being transferred between ECAD and MCAD, a Board file and a Library file (also called a Profile file).</p>
      <p class="para_division">In addition to the component name, number and reference designator, the Board file contains information defining:</p>
      <ul>
         <li>
            <p class="para_item">Which side of the board the component is placed on</p>
         </li>
         <li>
            <p class="para_item">X-Y distance from the board origin to the component origin (placement)</p>
         </li>
         <li>
            <p class="para_item">Component rotation in degrees</p>
         </li>
         <li>
            <p class="para_item">Z-distance from the board surface to the component origin (mounting offset) </p>
         </li>
      </ul>
      <p class="para_division">The Library file contains information defining the characteristics of each component package, including:</p>
      <ul>
         <li>
            <p class="para_item">Component footprint </p>
         </li>
         <li>
            <p class="para_item">Component height </p>
         </li>
      </ul>
      <p class="para_division">Typically, the data in the Library file is not needed when transferring a PCB assembly from NX to ECAD. The ECAD application uses the component name and number to reference a part in the ECAD libraries. Therefore, only the information in the Profile file need be written to ECAD. </p>
      <p class="para_division">For this reason, the default option for writing files is <b class="uiTerm">Board File + Components</b>. This option writes all the data for the Board file, but omits the Library file. 
      </p>
      <p class="para_division">If you have created parts in NX that do not exist in the ECAD libraries, you may wish to choose the Board File and Component Library File. This writes both the Board file and the Library file. Bear in mind however, that PCB.xchange uses a simple rectangular bounding box to represent the component footprint, not its actual shape.</p>
      <p class="para_division">If you have modified only the PC Board, you can choose  <b class="uiTerm">Board File, No Components</b>. No component placement data is written to the Board file.
      </p>
      <p class="para_division">When PCB.xchange reads a PCB assembly from NX it uses the 3D bounding box (X-Y in the plane of the PC board and Z for the height) to create the component footprint and height. This is used if you read a model from NX and write it to an ECAD file to create a IDF library file. This may not be the same as the footprint and height in the ECAD library. Generally when transferring a PCB assembly from NX to ECAD the IDF library file is not needed since the ECAD system uses its own library to identify the component details.</p>
      <p class="para_division">For more information, see:</p>
      <ul>
         <li>
            <p class="para_item"><a class="links" href="javascript:void(0)" onclick="top.openFile('pcb/02topic_3.html');return(false);"> Defining a PCB Assembly</a> 
            </p>
         </li>
         <li>
            <p class="para_item"><a class="links" href="javascript:void(0)" onclick="top.openFile('pcb/xu_filter.html');return(false);">Working with Entity Filters</a> 
            </p>
         </li>
         <li>
            <p class="para_item"><a class="links" href="javascript:void(0)" onclick="top.openFile('pcb/xu_manage_updates.html');return(false);">Managing Assembly Updates</a> 
            </p>
         </li>
      </ul>
   </body>
</html>