<!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>Splice definition</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">Splice definition</div>
      <hr noshade="true">
      <p class="para_topic">A splice is any means by which two or more wires connect along a path in a harness design. The connection may be made by a physical device, or the wires may be attached to each other directly (soldered, twisted, and so forth). A wire involved in a splice may end at the splice or it may pass through the splice.</p>
      <p class="para_topic">The following instructions describe how splices are included in a harness design using Routing Electrical.</p>
      <div class="title_division">Splice component qualification</div>
      <p class="para_division">Create a splice component, which is required to represent the splice whether physical or virtual. A virtual device carries information necessary to support the electrical relationships of the splice, but has no solid body. A physical device has similar electrical information but also carries a solid body.</p>
      <p class="para_division">Use <b class="uiTerm">Qualify Part</b> to add to a <b class="uiTerm">Fixture Port</b> to a splice component. The <b class="uiTerm">Fixture Port</b> allows you to position the component along a path. Create a number of <b class="uiTerm">Connection Ports</b> to the component, as many as the number of wires that the splice component may expect to connect. Alternatively, create a Multi&ndash;Port with as many <b class="uiTerm">Virtual Ports</b>.
      </p><br><div class="figure">
         <p align="center"><img align="bottom" src="graphics/virtual_splice1.gif"></p>
      </div>
      <div class="title_figure">Virtual splice component with 2 connection ports</div>
      <div class="figure">
         <p align="center"><img align="bottom" src="graphics/virtual_splice2.gif"></p>
      </div>
      <div class="title_figure">Virtual splice component using a multiport</div>
      <div class="title_division">Component List (.cmp) content</div>
      <p class="para_division">Include entries in the component list for the splice component. Define the splice component as a connector rather than a device.</p>
      <div class="title_division">Connection List (.hrn) content</div>
      <p class="para_division">Each wire that terminates at the splice has an entry in the Connection List with either the <em>from connector</em> or the <em>to connector</em> having the value of the splice component's unique identifier (as provided by the <b class="uiTerm">Component Navigator</b>).
      </p>
      <p class="para_division">An entry in the Connection List for a wire that passes through the splice, but does not terminate there, has no reference to the splice. Define this wire as if it had nothing to do with the splice.</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">In the 3D model, it is not possible to determine which wires in the bundle, if any, pass through a splice.</p>
               </div>
            </td>
         </tr>
      </table>
      <p align="center"><img align="bottom" src="graphics/splice2.gif"></p>
      <p class="para_division">Wires A, B and C are defined in the connection list as being from C1 to C2. Wire D is defined as being from C1 to S1. The model does not contain the information that Wire C passes through S1 (a splice).</p>
      <div class="title_division">Splice component placement</div>
      <p class="para_division">Determine where you want to place the splice in the harness by whatever design criteria applies. Subdivide the path segments at that location, which creates an RCP along the path. Place the <b class="uiTerm">Splice Component</b> on the RCP, using the <b class="uiTerm">Fixture Port</b> of the <b class="uiTerm">Splice Component</b> as the placement object.
      </p>
      <div class="figure">
         <p align="center"><img align="bottom" src="graphics/splice_comp.gif"></p>
      </div>
      <div class="title_figure">Splice component placed on path</div>
      <p class="para_division">The fixture port disappears when you place the component. If the splice has no solid body then there is no display indicating that the component is present. This does not pose a problem when assigning components however, since the <b class="uiTerm">Fixture Port</b> becomes visible as the cursor drags over the component (or you can select it from the ANT).
      </p>
      <div class="title_division">Routing the wires</div>
      <p class="para_division">A wire that terminates at a splice routes the same way other wires are routed, using either <b class="uiTerm">Auto Route</b> or <b class="uiTerm">Manual Route</b>. Typically, the bundle diameter on one side of the splice is larger than the bundle diameter on the other side, since one or more wires stop at the splice.
      </p>
      <div class="title_division">Formboard</div>
      <p class="para_division">The splice component carries to the formboard model. If a virtual splice component is used, you should place a note at the splice location to indicate to the builder where the splice occurs. If a physical splice component is used, the component appears on the formboard drawing, which should annotate accordingly.</p>
   </body>
</html>