<!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>NX Cabling</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">NX Cabling</div>
      <hr noshade="true">
      <ol type="1" start="1">
         <li>
            <p class="para_item">In the legacy Connection List, <em>all</em> rows in the .hrn file are wires.
            </p>
         </li>
         <li>
            <p class="para_item">Using the legacy lists, there can be no hierarchy for wires within cables within cables.</p>
         </li>
         <li>
            <p class="para_item">Part Library View Modification.</p>
            <p class="para_item">The PLV must contain a wires node that contains a node for a wires.ptb file and a node for a cables.ptb file. (The .ptb files for wires and cables can be named whatever you want to name them as long as the names are unique.) This allows NX to find the cable's information for sweeping a solid.</p>
            <table border="0">
               <tr>
                  <td valign="top" align="left"><img align="left" src="../graphics/note.gif" alt="Note" title="Note"></td>
                  <td valign="bottom" align="left" width="100%">
                     <div class="para_note">
                        <p class="para_note_body">The order of the subnodes is import and if the same information is in multiple .ptbs, the information from the first .ptb is used. For example, a .plv file has the following:</p><pre class="indent">NODE WIRES</pre><ul class="hangingList">
                           <li><pre class="indent">NAME     Wires</pre><br><pre class="indent">WIRES_NODE  CABLE_NODE</pre></li>
                        </ul><br><pre class="indent">END_NODE</pre><br><br><pre class="indent">NODE_WIRES_NODE</pre><ul class="hangingList">
                           <li><pre class="indent">NAME Wires_node</pre><br><pre class="indent">TABLE wires.ptb</pre></li>
                        </ul><pre class="indent">END_OF_NODE</pre><br><br><pre class="indent">NODE CABLES_NODE</pre><ul class="hangingList">
                           <li><pre class="indent">NAME Cables_node</pre><br><pre class="indent">TABLE cables.ptb</pre></li>
                        </ul><pre class="indent">END_OF_NODE</pre></div>
                  </td>
               </tr>
            </table>
            <p class="para_item">In a custom installation, the names of the nodes and the part table files may differ. The wire.ptb will be searched first to find the information for OD for the swept solid as the WIRES_NODE is the first subnode of WIRES. If the information is found in the wires.ptb part table, the cables.ptb is not searched.</p>
         </li>
         <li>
            <p class="para_item">Cable_id in the import / export format and within the .hrn file specifies the cable name into which the wires are placed/ For example, <br><code>! unique_id, from_dev, from_conn, from_pin, to_dev, to_conn, to_pin, cable_id</code><br><code>w1, Dev1, Conn1, P1, Dev2, Conn2, P1, cable01</code><br>specifies that the wire w1 is in cable01. If cable_id is left blank fro a particular view, then the system assumes that the wire is not part of a cable.
            </p>
            <div class="figure">
               <p align="center"><img align="bottom" src="graphics/list_input.gif"></p>
            </div>
            <div class="title_figure">Connection list after import</div>
         </li>
         <li>
            <p class="para_item">Cable_type within the import / export format and within the .hrn file specifies the type of cable to be used when the connection (s) are routed. The cable_type field does not have to be used, PART_NAME or some other field may be used instead. However, if cable_type is not used, the swept solid is based upon the wire bundle. If cable_type is specified, the cable_type is copied up from the wire row in the Connection List Navigator to the cable row in the navigator and cable_type is used as a parameter in the search of the wires node within the part library structure. For a solid to be swept, values for the connection <em>must</em> match a single row in the cable.ptb file with an OD in order to determine the OD of the swept solid. For example:
            </p><br><pre class="indent">! unique_id, from_dev, from_conn, from_pin, to_dev, to_conn, to_pin, cable_id, cable_type</pre><br><pre class="indent">w1, Dev1, Conn1, P1, Dev 2, Conn2, P1, cableo1, C64</pre><p class="para_item">matches the cable .ptb file.</p><br><table border="" cellpadding="2" cellspacing="1" align="center">
               <colgroup span="1">
                  <col span="1">
                  <col span="1">
                  <col span="1">
                  <col span="1">
                  <col span="1">
               </colgroup>
               <tbody>
                  <tr>
                     <td colspan="1" rowspan="1">
                        <p class="para_td"><code>!MEMBER_NAME</code></p>
                     </td>
                     <td colspan="1" rowspan="1">
                        <p class="para_td"><code>PART_NUMBER</code></p>
                     </td>
                     <td colspan="1" rowspan="1">
                        <p class="para_td"><code>OD</code></p>
                     </td>
                     <td colspan="1" rowspan="1">
                        <p class="para_td"><code>NUMBER_OF_WIRES</code></p>
                     </td>
                     <td colspan="1" rowspan="1">
                        <p class="para_td"><code>CABLE_TYPE</code></p>
                     </td>
                  </tr>
                  <tr>
                     <td colspan="1" rowspan="1">
                        <p class="para_td"><code>&ldquo;A1&rdquo;</code></p>
                     </td>
                     <td colspan="1" rowspan="1">
                        <p class="para_td">12345678</p>
                     </td>
                     <td colspan="1" rowspan="1">
                        <p class="para_td"><code>3</code></p>
                     </td>
                     <td colspan="1" rowspan="1">
                        <p class="para_td"><code>4</code></p>
                     </td>
                     <td colspan="1" rowspan="1">
                        <p class="para_td"><code>&ldquo;C64&rdquo;</code></p>
                     </td>
                  </tr>
               </tbody>
            </table><br><p class="para_item">When w1 is routed, the swept solid has an OD of 3 units, the OD of the cable. If there are other wires within this cable that are routed, the OD of the swept solid for the common portions of the path remains 3 units, the OD of the cable.</p>
         </li>
         <li>
            <p class="para_item">If the cable_type field is used, uniqueness of the cable_type field in the .ptb file (although not necessary) helps NX determine the correct cable by retrieving corresponding data. See the default cir_cable.prb (CT is the cable type in this .ptb file). If more than one row in the part table matched, the first row is used. This is true for any of the fields in the part tables.</p>
         </li>
         <li>
            <p class="para_item">If wire information is desired within the file (OD, or sufficient information to obtain an OD), you create a part with the desired information within it (specify the connection information in the part), places that part file in with the other inch/metric parts for the part library, and specifies that part in the .ptb file. For example,</p>
            <table border="0" cellpadding="2" cellspacing="1" align="center">
               <colgroup span="1">
                  <col span="1">
                  <col span="1">
                  <col span="1">
                  <col span="1">
                  <col span="1">
               </colgroup>
               <tbody>
                  <tr>
                     <td colspan="1" rowspan="1">
                        <p class="para_td"><code>!OD</code></p>
                     </td>
                     <td colspan="1" rowspan="1">
                        <p class="para_td"><code>CT</code></p>
                     </td>
                     <td colspan="1" rowspan="1">
                        <p class="para_td"><code>TYPE</code></p>
                     </td>
                     <td colspan="1" rowspan="1">
                        <p class="para_td"><code>PART_NUMBER</code></p>
                     </td>
                     <td colspan="1" rowspan="1">
                        <p class="para_td"><code>PART_NAME!</code></p>
                     </td>
                  </tr>
                  <tr>
                     <td colspan="1" rowspan="1">
                        <p class="para_td"><code>0.1</code></p>
                     </td>
                     <td colspan="1" rowspan="1">
                        <p class="para_td"><code>0.01</code></p>
                     </td>
                     <td colspan="1" rowspan="1">
                        <p class="para_td"><code>0</code></p>
                     </td>
                     <td colspan="1" rowspan="1">
                        <p class="para_td"><code>&ldquo;C-01&rdquo;</code></p>
                     </td>
                     <td colspan="1" rowspan="1">
                        <p class="para_td"><code>&ldquo; &ldquo;</code></p>
                     </td>
                  </tr>
                  <tr>
                     <td colspan="1" rowspan="1">
                        <p class="para_td"><code>0.5</code></p>
                     </td>
                     <td colspan="1" rowspan="1">
                        <p class="para_td"><code>0.0</code></p>
                     </td>
                     <td colspan="1" rowspan="1">
                        <p class="para_td"><code>0</code></p>
                     </td>
                     <td colspan="1" rowspan="1">
                        <p class="para_td"><code>&ldquo;C-02&rdquo;</code></p>
                     </td>
                     <td colspan="1" rowspan="1">
                        <p class="para_td"><code>&ldquo;cable_wires.prt&rdquo;</code></p>
                     </td>
                  </tr>
               </tbody>
            </table><br><p class="para_item">(This is from the default inch cir_cables.ptb) In this case, if the wires of the cable are split out and go to different connectors, the common path has an OD of the cable and the paths that have wires on them has the OD of the bundle of those wires, or the wire ODs if the wire is on the path alone.)</p>
            <p class="para_item">For example, using the default electrical installation, place five (5) connectors and create a path from one to the other four (4) connectors as seen in Figure 2. Assign the connectors and then create a cable connection using the connection list wizard and select the cable stock to be C-05. This stock is a cable containing a shield containing four (4) wires. The red connector on the left is conn1 and the connectors on the right from top to bottom as conn2, conn3, conn4, and conn5, respectively. The cable OD is used for the left most sweep (See Figure 3) as this is the portion of the path that the cable covers with no break outs.</p>
            <div class="figure">
               <p align="center"><img align="bottom" src="graphics/cable_conn.gif"></p>
            </div>
            <div class="title_figure">Figure 2: Cable connections using connection information from a part file specified in a part table</div>
            <div class="figure">
               <p align="center"><img align="bottom" src="graphics/close_up.gif"></p>
            </div>
            <div class="title_figure">Figure 3: Close up of branches of the sweeps from Figure 2</div>
         </li>
      </ol>
   </body>
</html>