<!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>Paths 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_topic3" id="xps10_pagetitle">Paths overview</div>
      <hr noshade="true">
      <table cellspacing="4" align="center">
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td">Paths Overview</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"> <a class="links" href="javascript:void(0)" onclick="top.openFile('routingtools/paths_routing.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('routingtools/parallel_offset.html');return(false);">Related Topics</a></p>
            </td>
         </tr>
      </table><br><p class="para_topic">To create a routing assembly, the design engineer must define the paths followed by stock. This topic highlights concepts and operations used to define and manipulate paths. We discuss basic terminology, fundamental operations and information associated with paths.</p>
      <div class="title_division">Routing control points (RCPs)</div>
      <p class="para_division">RCPs define positions within a routing assembly. A single RCP connects to one or more additional RCPs, as shown below. In this example, RCP A connects to one RCP and RCP D connects to three RCPs. All connected RCPs are a routing. This example contains two routings. One routing contains RCPs A, B, C, D, and E and the other routing contains RCPs, F, G, H, and I.</p>
      <div class="figure">
         <p align="center"><img align="bottom" src="graphics/image1585.gif"></p>
      </div>
      <div class="title_figure">RCPs and routings</div>
      <div class="title_division">Using existing geometry</div>
      <p class="para_division">One option when creating routings is to select existing NX geometry such as points, lines, arcs, and splines (available geometry will depend on the routing application). Routing creates RCPs at the ends of the existing geometry. The path between the two RCPs will follow the existing geometry.</p>
      <p class="para_division">During the creation of routings, RCPs are often associated with existing NX geometry. This permits attaching routings to devices or routings that need to pass through cutout holes in solids to update automatically when the associated feature moves.</p>
      <p class="para_division">The display symbol for an RCP (what appears in the graphics window) is a small circle. The marker symbol draws parallel to the screen and does not rotate or scale. Turn off the display of RCPs in <b class="uiTerm">Preferences</b>.
      </p>
      <div class="title_division">Paths and path segments</div>
      <p class="para_division">All of the RCPs and segments between any two RCPs within a routing define a path. In the figure above, RCPs and routings, the path between RCPs A and C is: A, B, D, and C. A path between I and H is: I, F, and H. There is no path between B and G. A path segment is any section between two adjacent RCPs, such as the segment between RCPs B and D. Path segments display in the center line font.</p>
   </body>
</html>