<!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>IGES export advanced settings</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">IGES export advanced settings</div>
      <hr noshade="true">
      <table cellspacing="4" align="center">
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td"><a class="links" href="javascript:void(0)" onclick="top.openFile('dataexchange/iges_settings.html');return(false);">Overview</a></p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td">Options</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><div class="title_division">Map tabulated cylinder to b-surface</div>
      <p class="para_division">When you turn this option on, NX entities that would normally become IGES <b class="uiTerm">Tabulated Cylinder</b> become IGES b-surface entities instead.
      </p>
      <div class="title_division">Map crosshatch to</div>
      <p class="para_division">When exporting NX crosshatch information, you can represent it as IGES <b class="uiTerm">Section Area</b> data (the most common representation) or as <b class="uiTerm">Copious Data</b>. You would only use <b class="uiTerm">Copious Data</b> if the receiving system has previously proven unable to handle <b class="uiTerm">Section Area</b> information appropriately (which should be very rare).
      </p>
      <p class="para_division">The default is to export crosshatch information as <b class="uiTerm">Section Area</b> data.
      </p>
      <div class="title_division">Revolve faces to</div>
      <p class="para_division">The IGES translator can export revolved faces such as cones, spheres, tori, etc., as either IGES Surface of Revolution entities or IGES B&ndash;surface entities.</p>
      <div class="title_division">Output Solids As</div>
      <p class="para_division">Solids can be output as Surfaces or just as their edge outline (<b class="uiTerm">Edges Only</b>). The correct choice is dependent on what the expected use of the data will be in the receiving system. If the main purpose is to create drawings in the receiving system, the <b class="uiTerm">Edges Only</b> is most appropriate. If you use the geometry representation, (in addition to drawing information), then select Surfaces to ensure a proper geometric representation.
      </p>
      <p class="para_division">NX IGES does not create the IGES solid entity at this time.</p>
      <p class="para_division">The default is to export solid information as trimmed surfaces.</p>
      <div class="title_division">Approximation tolerance</div>
      <p class="para_division">This is the tolerance the IGES translator uses when it needs to approximate an NX surface object when there is no direct IGES entity to represent the information and an IGES B&ndash;surface has to create. At this point, these are mainly offset surfaces and variable radius blend surfaces within NX.</p>
      <p class="para_division">The entered value must be between .000001mm and .01mm. The smaller the value the more accurate the approximation will be but the translation will take longer and a larger IGES file will result.</p>
      <p class="para_division">It is reasonable to set this to an order of magnitude smaller than the receiving system's machining tolerance if you know it. However .01 will generally be appropriate for most systems.</p>
      <p class="para_division">The default value is .01mm.</p>
      <div class="title_division">JAMA option</div>
      <p class="para_division">If you are required to export IGES data that meets the JAMA (Japanese Automotive Manufacturers Association) specifications, you should check this option. Visit <a class="links" href="javascript:void(0)" onclick="top.openFileURL('http://www.jama.org');return(false);">http://www.jama.org</a> for details on JAMA.
      </p>
      <p class="para_division">Note that you must purchase a separate license for this option to actually create the JAMA specific information.</p>
      <p class="para_division">The default is not to create a JAMA compliant IGES file.</p>
      <div class="title_division">Model space maximum</div>
      <p class="para_division">The IGES format allows the sending system to specify the maximum space used by the model. In many cases this is the bounding box that surrounds the model. If you select <b class="uiTerm">System Defined</b>, these values write to the IGES file.
      </p>
      <p class="para_division">There are systems that use the value in the IGES file to determine the relative accuracy they will use for modeling operations. If you want to decrease the bounding box values you can check the <b class="uiTerm">User Specified</b> option and enter the desired value.
      </p>
      <p class="para_division">CATIA requires all components to have the same MODEL DIMENSION value, which CATIA determines from this value in the IGES file. If the IGES file adds to an existing assembly structure within CATIA, this option lets the sender set the value to ensure the component will be usable.</p>
      <p class="para_division">The default is to use the NX generated maximum model space values.</p>
      <div class="title_division">Coincident point resolution</div>
      <p class="para_division">The IGES format allows the sending system (NX) to specify the value it uses to decide if two points are coincident. NX uses .00001mm for this resolution. This value is usually acceptable to most systems. However you can enter a different if the receiving system requires a less accurate resolution.</p>
      <p class="para_division">The default is to use the <b class="uiTerm">Coincident Point Resolution</b>.
      </p>
      <div class="title_division">Configuration information</div>
      <p class="para_division">The <b class="uiTerm">Author</b>, <b class="uiTerm">Company</b>, <b class="uiTerm">ID For Receiver</b>, and <b class="uiTerm">Start Section</b> items are dynamic input boxes. This data is copied as entered to the appropriate boxes within the IGES file. Configuration information can be used to help manage data that is being exchanged, but it is does not have to be provided. In most systems &ndash; including NX &ndash; if the data is in the IGES file, it is assigned to general text attributes for the created part.
      </p>
      <p class="para_division">There is no default text entry for <b class="uiTerm">Author</b>, <b class="uiTerm">Company</b>, <b class="uiTerm">ID For Receiver</b>, or <b class="uiTerm">Start Section</b>.
      </p>
   </body>
</html>