<!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>Bend radius tables 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_topic2" id="xps10_pagetitle">Bend radius tables overview</div>
      <hr noshade="true">
      <p class="para_topic">Bend corner radii may be determined by bend radius tables for any Routing application. A bend table specifies a radius to use given a stock diameter. This allows nonlinear relationships between the stock diameter and bend radius to be specified. For example, a stock diameter of 10.0 may always have a bend radius of 2.0 assigned, whereas a stock diameter of 20.0 may have a bend radius of 3.0 assigned.</p>
      <p class="para_topic">In order to set up the use of Bend Radius Tables, four things must be done;</p>
      <ol type="1" start="1">
         <li>
            <p class="para_item">The environment variable that defines the directory in which Routing should look for the bend tables must be defined (<code>UGII_ROUTING_BEND_TABLES_PATH</code>).
            </p>
         </li>
         <li>
            <p class="para_item">The Routing application's Application View File (.apv) must define the bend table file list.</p>
         </li>
         <li>
            <p class="para_item">The bend table file list must be created and exist in the directory pointed to by the environment variable <code>UGII_ROUTING_BEND_TABLES_PATH</code>.
            </p>
         </li>
         <li>
            <p class="para_item">The bend table files listed in the bend table file list must exist in the directory pointed to by the environment variable <code>UGII_ROUTING_BEND_TABLES_PATH</code>.
            </p>
         </li>
      </ol>
      <p class="para_topic">Each of these tasks is described below.</p>
      <div class="title_division">Environment variable</div>
      <p class="para_division">The environment variable <code>UGII_ROUTING_BEND_TABLES_PATH</code> must be defined and point to a list of valid directories (there may be just one). These are the directories that hold the files that define the bend radius table values. In the default ugii_env file, this variable is provided with a default definition. If the variable is to be defined using the ugii_env file, then this line needs to be modified to point to the correct directories (unless the default is to be used).
      </p>
      <div class="title_division">Application View File entry</div>
      <p class="para_division">Each Routing application is driven by an application view file. For example, Routing Mechanical has the default .apv file named ugroute_mech.xml. To use bend radius tables, the file which lists the available tables must be specified in the application view file.</p>
      <p class="para_division">The Bend Table Files element in the APV file appears as follows:</p><pre class="indent">&lt;BEND_RADIUS_TABLE_FILES&gt;
			&lt;File_Name&gt;
					routing_bend_table.txt
			&lt;/File_Name&gt;
&lt;/Bend_Radius_Table_Files&gt;</pre><div class="title_division">Bend Table File List</div>
      <p class="para_division">The file specified in the apv file (above) must contain a list of one or more file names. These are the names of the actual bend radius table files (described below). Here is an example of a Bend Table File List (which would be named routing_bend table.txt according to the example apv entry above.</p>
      <p class="para_division">bend_table1.txt</p>
      <p class="para_division">bend_table2.txt</p>
      <p class="para_division">bend_table3.txt</p>
      <p class="para_division">This is a very simple text file, listing a file name in each line of the file.</p>
      <div class="title_division">Bend Table Files</div>
      <p class="para_division">A bend table file associates a bend radius with a stock diameter. There may be any number of associations made. The general syntax of a bend radius table is the following:</p><pre class="indent">TABLE &lt;table name&gt;
&lt;stock diameter&gt;		&lt;bend radius&gt;
&lt;stock diameter&gt;		&lt;bend radius&gt;
.
.
.
END_OF_TABLE</pre><p class="para_division">Comment lines may be inserted anywhere in the file by beginning the comment line with an exclamation point (!).</p>
      <p class="para_division">The following is an example of the contents of a bend radius table file:</p><pre class="indent">!
1	Bend Table 1
!
! 1st column == Stock diameter
! 2nd column =- Bend Radius
!
TABLE Standard Bend Radius Table
0.25 1
-.50 1
0.75 1
1.00 1
1.25 2
1.50 2
1.75 2
2.00 2
2.25 4
2.50 4
3.00 4
END_OF_TABLE</pre><div class="title_division">User interaction</div>
      <p class="para_division">You can make use of Bend Radius Tables through the <b class="uiTerm">Assign Corner</b> dialog box of Routing. Please refer to the<a class="links" href="javascript:void(0)" onclick="top.popUpPage('routingtools/index.html?goto=routingtools/title_page.html&vars=-aux,-home','linkInter','menubar=yes,status=yes,resizable=yes,toolbar=yes,scrollbars=yes,location=no,directories=no');return(false);"> Routing Tools Help</a> &ndash; Assign Corner topic for further information.
      </p>
   </body>
</html>
