<!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>Overview</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">Overview</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('routingtools/paths_overview.html');return(false);">Paths Overview</a></p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td"><a class="links" href="javascript:void(0)" onclick="top.openFile('routingtools/paths_create_editpath.html');return(false);">How To</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('routingtools/parallel_offset.html');return(false);">Related Topics</a></p>
            </td>
         </tr>
      </table><br><p class="para_topic">An RCP never creates at the same position as an existing RCP. The system uses the existing RCP instead. The existing associativity between the RCP and the object where it creates remains. If there was no pre-existing association, however, the system makes an association to the new object, if applicable.</p>
      <p class="para_topic">A segment may follow a curve of any type (line, arc or b-curve). It may follow the entire curve or a portion of it. Two segments cannot follow the same part of a curve. A segment following a curve remains associated to that curve, so that if you modify the curve then the segment is updated accordingly.</p>
      <p class="para_topic">When you select a segment it subdivides at the point of selection. The exceptions are 1) the selection point is at one of the end RCPs of the segment. (In this case, the end RCP is added to the path); or 2) the current path end is one of the end RCPs of the selected segment. (In this case, the segment is included in the path and the other end RCP becomes the current path end.)</p>
      <div class="title_division">Routing assumptions</div>
      <p class="para_division"><b class="uiTerm">Create Path</b> uses simplifying assumptions to help define routing assemblies. For instance, if you select a closed arc or a circular edge of a face, <b class="uiTerm">Create Path</b> assumes you are trying to route to a hole or to an attachment on a device. In this case <b class="uiTerm">Create Path</b> calculates positions that will enable you to route up to the position along the axis of the arc/edge. <b class="uiTerm">Create Path</b> also associates the path's position with the center of the arc/edge. So the path's position will stay attached to the hole or device if moved. If this was not the desired behavior, you may select the same objects using <b class="uiTerm">Point Constructor</b> and <b class="uiTerm">Create Path</b> will use the selected positions without making any assumptions or object association.
      </p>
      <p class="para_division">Use these same general rules when selecting a follow curve. <b class="uiTerm">Create Path</b> assumes you are going to include the drive curve in the path and calculates a position, which enables you to approach the curve along a tangent to the end of the curve. When the drive curve is included the path is associated with the curve and will stay attached to the curve. If this was not the desired behavior, you may select curves using <b class="uiTerm">Point Constructor</b> and <b class="uiTerm">Create Path</b> will use the selected positions without making any assumptions or object association.
      </p>
      <div class="title_division">Object scopes</div>
      <p class="para_division">When you select an object, path creation behaves differently depending on where the selected object is in the assembly relative to the current work part where the path creates:</p>
      <table bgcolor="#F0F0F0" cellpadding="2" cellspacing="4" width="95%" align="center">
         <colgroup span="1">
            <col span="1" width="66*">
            <col span="1" width="133*">
         </colgroup>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Work Part Scope</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Object selected is from the current work part (note B and B' are different in this context even though they are the same part).</p>
            </td>
         </tr>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Work Part Component Scope</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Object selected is a component member from one of the component or subcomponent parts of the current work part (similarly, D and D' are different).</p>
            </td>
         </tr>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Displayed Part Scope</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">None of the above. Under normal NX settings these objects are inactive, but they are still selectable under <b class="uiTerm">Create Path</b>.
               </p>
            </td>
         </tr>
      </table><br><p align="center"><img align="bottom" src="graphics/image1594.gif"></p>
      <p class="para_division">A is the displayed part (root part); B is the current work part. Here scopes are work part (B), work part component (D), and displayed part scope (A, B, D, C)</p>
      <p class="para_division">RCPs may only be associated with objects in the work part or a work part component. If selecting a RCP, which is not in the work part, the selected RCP cannot be included in the new path. Rather, the function creates a new RCP in the work part at the selected RCP's position. The system does not subdivide selected segments not in the work part. In this case, a NX creates a new in the work part at the selected position. Drive curves will not follow in the displayed part scope. In this case, also, the system creates a new RCP in the work part at the selection position.</p>
      <div class="title_division">Paths with WAVE linked ports</div>
      <p class="para_division">Parts can have selectable ports that are WAVE linked to ports in an assembly component. WAVE linked ports create with the <b class="uiTerm">WAVE Geometry Linker</b> (<b class="uiTerm">Assemblies&rarr;WAVE Geometry Linker</b>). See  <a class="links" href="javascript:void(0)" onclick="top.openFile('routingtools/port_dis2.html');return(false);">WAVE Linked Ports</a> for further information. When creating paths, WAVE linked ports behave the same as non&ndash;linked ports in the work part.
      </p>
   </body>
</html>