<!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>Electrical connection navigator 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">Electrical connection navigator overview</div>
      <hr noshade="true">
      <table cellspacing="4" align="center">
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td"> 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/wiring_wire_import_data.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/wire_con_list_view.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/wiring_wire_connect_list_func.html');return(false);">Related Topics</a></p>
            </td>
         </tr>
      </table><br><p align="left"><img align="bottom" src="graphics/ico_t_elec_nav.gif"></p>
      <p class="para_topic">The purpose of the <b class="uiTerm">Electrical Connection Navigator</b> is to provide the means for importing, editing and exporting connection and component list files and to keep track of routing status information from session to session.
      </p>
      <p class="para_topic">The connection list information is necessary to assign wires and cables to paths in the assembly. The <b class="uiTerm">Connection Navigator</b> maintains one entry for each wire (or conductor) in the work part. Each component (device or connector) referenced by a connection must have an entry in the component list and a <b class="uiTerm">Unique ID</b> assigned to it to enable the routing of the connection. Various information is required to perform specific tasks in the Routing Electrical program. Routing Electrical uses the connection and component lists to identify a route for each connection and stores its connection and routing status information in the work part.
      </p>
      <div class="title_division">Smart fields</div>
      <p class="para_division">The <b class="uiTerm">Connection Navigator</b> automatically keeps track of special smart fields that contain specific information. Smart fields exist for every connection list in addition to any fields specified in the file format. These fields are required to utilize the functionality of the connection list. 
      </p>
      <p class="para_division">The smart fields for the connection list are: </p>
      <ul>
         <li>
            <p class="para_item">unique_id &ndash; the wire UD.</p>
         </li>
         <li>
            <p class="para_item">from_comp &ndash; the device ID from which the wire connects</p>
         </li>
         <li>
            <p class="para_item">from_conn &ndash; the connector ID from which the wire connects.</p>
         </li>
         <li>
            <p class="para_item">from_port &ndash; the port ID (or pin ID) from which the wire connects.</p>
         </li>
         <li>
            <p class="para_item">to_comp &ndash; the device ID to which the wire connects.</p>
         </li>
         <li>
            <p class="para_item">to_conn &ndash; the connector ID to which the wire connects.</p>
         </li>
         <li>
            <p class="para_item">to_port &ndash; the port ID to which the wire connects.</p>
         </li>
         <li>
            <p class="para_item">length &ndash; the length of the wire as modeled.</p>
         </li>
         <li>
            <p class="para_item">multiplier &ndash; a factor use to determine the cut length from the length.</p>
         </li>
         <li>
            <p class="para_item">offset &ndash; a factor used to determine the cut length from the length.</p>
         </li>
         <li>
            <p class="para_item">cut_length &ndash; a value derived from the length by applying the multiplier and the offset.</p>
         </li>
         <li>
            <p class="para_item">fabrication &ndash; the name of the fabrication (also known as harness name).</p>
         </li>
         <li>
            <p class="para_item">stock &ndash; the name of the wire stock.</p>
         </li>
         <li>
            <p class="para_item">routed &ndash; indicates that the wire is routed (system assigned).</p>
         </li>
      </ul>
      <p class="para_division">The required boxes for different functions are given in the table below.</p>
      <table bgcolor="#F0F0F0" cellpadding="2" cellspacing="4" width="95%" align="center">
         <tr valign="top">
            <th bgcolor="#c0c0c0" colspan="1" rowspan="1" valign="top">
               <p class="para_th">Functionality</p>
            </th>
            <th bgcolor="#c0c0c0" colspan="1" rowspan="1" valign="top">
               <p class="para_th">Required Smart Fields</p>
            </th>
         </tr>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Importing</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">No specific boxes are required. Any boxes defined must match types with boxes created in the route list. For example, if you specified a dumb field description in the first <b class="uiTerm">Connection List File Format</b> (and <b class="uiTerm">Connection Navigator</b>) section as a string, any other file format used for import with a description box would have to define it as a string also.
               </p>
            </td>
         </tr>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td"><b class="uiTerm">Display Logical Connectivity</b></p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">From_comp, from_conn, from_port, to_comp, to_conn, to_port. If connectors are not being used, from_conn and to_conn are not required. Unique_id is also required to label the connections.</p>
            </td>
         </tr>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td"><b class="uiTerm">Auto Route</b> (calculate length)
               </p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">From_comp, from_conn, from_port, to_comp, to_conn, to_port, and other smart fields required to determine the outer diameter in the connection list are required to obtain an accurate length calculation. In the component list, boxes used to assign components are also required. Record lengths will not be calculated accurately (if miter corners exist, which is highly unlikely), if the outer diameter cannot be determined from the connection list. The system will internally use the length, multiplier, offset, cut_length, route, fabrication and routed smart fields in the connection list. The comp, routed and occur smart fields are used internally in the component list.</p>
            </td>
         </tr>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td"><b class="uiTerm">Auto Route</b> (assign stock)
               </p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Once the length is determined in <b class="uiTerm">Auto Route</b>, additional boxes are required to determine which stock to assign. These boxes depend on how the part family tables are set up for Routing Electrical. Potentially, they would consist of gauge, type, w_spec and color. Internally, the system will use the stock smart field in the connection list.
               </p>
            </td>
         </tr>
      </table><br></body>
</html>