<!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>Tips for use</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">Tips for use</div>
      <hr noshade="true">
      <table cellspacing="4" align="center">
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td"><a class="links" href="javascript:void(0)" onclick="top.openFile('routingtools/frmbrd_over.html');return(false);">Overview</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_frmbrd_create.html');return(false);">Options</a></p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td">Related Topics</p>
            </td>
         </tr>
      </table><br><p class="para_topic">This topic contains shortcuts, best practices, and tips to use with the <b class="uiTerm">Formboard</b> functionality.
      </p>
      <div class="title_division">Preview/Creation</div>
      <ul>
         <li>
            <p class="para_item">When qualifying backshells or clips which are not going to be in the component list; make sure to use fixture ports and ensure that the fixture port attaches to an RCP when the backshell or clip is placed in the assembly.</p>
         </li>
         <li>
            <p class="para_item">Devices are not included in the formboard assembly. Instead, for each device only connection, a proxy is placed in the formboard so that the wire routing remains intact. For wires that contain a device connection, a dummy connector will be created in the formboard. The formboard component list will append and a new connector will be added as necessary for each device. The <b class="uiTerm">Formboard Connection Navigator</b> alters to change the wires from connecting to devices to connecting to the new proxy connectors. The new connector name is: &lt;Device Name&gt;_PROXY. The pin information remains consistent between the device and the new formboard connector. The geometrical representation of a new connector is a single multiport in a dynamically created <b class="uiTerm">Formboard</b> specific component: &lt;Device name&gt;_proxy.prt.
            </p>
            <p class="para_item">If a device has more than one multi&ndash;port, and the harness has wires connected to them, multiple proxy connectors create. These are named using the following convention: &lt;Device_Name&gt;_PROXY_&lt;Multi&ndash;port Name&gt;.</p>
         </li>
      </ul>
      <div class="title_division">Bundle/Component arrangement</div>
      <ul>
         <li>
            <p class="para_item">When using <b class="uiTerm">Formboard Modify Path</b>, turning on a Grid and the <b class="uiTerm">Snap to Grid</b> option from <b class="uiTerm">Preferences&rarr;Work Plane</b>, will assist in easier orientation of bundles and components.
            </p>
         </li>
         <li>
            <p class="para_item">After synchronization, or any other operation that might have changed the initial number of RCPs or segments in a formboard part, the branch angle value in <b class="uiTerm">Orient Bundles</b> may be inaccurate.
            </p>
         </li>
      </ul>
      <div class="title_division">Annotation/Reports</div>
      <ul>
         <li>
            <p class="para_item">It is highly recommended that you use tabular notes for large associative annotations, because tabular notes/labels have poor performance with attributes.</p>
         </li>
         <li>
            <p class="para_item">If you specify the column titles as either blank or all spaces, then the column line is not inserted into the annotation. Always use a non&ndash;blank column title.</p>
         </li>
         <li>
            <p class="para_item">If you specify 0 for a column width, then no formatting applies. The resulting string is not padded with spaces nor will it be truncated. We recommend using 0 (zero) for column width when creating tabular notes.</p>
         </li>
         <li>
            <p class="para_item">The <b class="uiTerm">Nodal Report</b> will generate a note containing the pairs of consecutive nodes. Consecutive nodes are nodes that do not have any other nodes along the path between them. Since there are two possible ways of generating the annotation of each pair (both N1&rarr;N2, and N2&rarr;N1), both methods are put into the annotation. You should choose your preferred method and then remove the unwanted values by hand.
            </p>
         </li>
         <li>
            <p class="para_item">The <b class="uiTerm">Clock Annotation</b> and <b class="uiTerm">Auto Clock Report</b> generates a symbol that indicates clocking information. The symbol consists of a circle with tick marks indicating angle increments. You can specify the angle increments for the ticks, the length of the tick marks, and the radius of generated circles. A small triangle and possibly a line are created. The triangle represents the connector master keyway. The line indicates the rotation vector of the port that the backshell uses to attach to the connector. The circle itself represents the orthographic projection of the face of the connector (that attaches to the backshell) to the XY plane.
            </p>
         </li>
         <li>
            <p class="para_item">The <b class="uiTerm">Component CGM Annotation</b> and <b class="uiTerm">Auto Component CGM</b> reports use a characteristic value (CGM_FILE) that is on the component. You can specify this characteristic in the part table or define it manually by assigning an attribute titled CGM_FILE to the component in the context of the harness. The CGM files should be in UGII_FMBD_CGM_DIR, or in UGII_ROUTE_ELEC_PART_PATH.
            </p>
         </li>
         <li>
            <p class="para_item">The <b class="uiTerm">Component Pattern Annotation</b> and <b class="uiTerm">Auto Component Pattern Report</b> use the PATTERN_FILE characteristic for determining the pattern part file to use. The pattern part files should be in UGII_FMBD_PATTERN_DIR or in the UGII_WIRING_PART_PATH.
            </p>
         </li>
         <li>
            <p class="para_item">For the Auto Component, Connector, Clock, Component CGM, and Component Pattern reports, finding the bounding box of each component and offsetting the annotation by the values specified in the <b class="uiTerm">Specify Offset</b> dialog box determines the origin of each annotation. The <b class="uiTerm">Base Point</b> in <b class="uiTerm">Specify Offset</b> indicates the point in the bounding box to use as the origin. The top left base point is the point on the bounding box of the component that is at the minimum X value, and maximum Y value, and the Bottom Right is the point at the maximum X value, and minimum Y value, etc. The X offset and Y offsets will then apply to the base point.
            </p>
         </li>
         <li>
            <p class="para_item">When CGM annotation/reports are created, the imported geometry is inserted into a group. The geometry can then be selected for repositioning.</p>
         </li>
      </ul>
      <div class="title_division">Synchronization</div>
      <ul>
         <li>
            <p class="para_item">If discrepancies are deactivated, they are not fixed. This may prevent other discrepancies from being fixed. For example, specifying a segment length discrepancy to be deactivated will cause one or more wire length discrepancies from being fixed.</p>
         </li>
         <li>
            <p class="para_item">Updated annotations will lose most or all of the user added formatting.</p>
         </li>
         <li>
            <p class="para_item">Re&ndash;flatten branches will re&ndash;clock the components. This may cause all of the components in the formboard part to flip, but they will all have the same relative clocking as in the master.</p>
         </li>
         <li>
            <p class="para_item">Branch angle support does not implement in Unigraphics V18 synchronization; because of this the segments created from missing component and missing segment discrepancies may not have the correct relative branch angle.</p>
         </li>
      </ul>
      <div class="title_division">Interpreting synchronization results</div>
      <p class="para_division">You can find segment discrepancies, as well as clip discrepancies, by mapping the RCPs in the formboard part to the RCPs in the master part. This mapping method makes a best guess attempt at determining the mapping between the formboard and master parts. The current mapping method makes a best guess attempt determining the mapping between the formboard and master parts. This guess will result in accurate results, however they are not minimal.</p>
      <div class="title_division">Example:</div>
      <p class="para_division">A master part consists of a wire following one segment. The formboard generated from this master part also consists of a wire following one segment. If this segment becomes subdivided in the master part, a segment discrepancy between the two parts exists. Intuitively, there should be an extra segment discrepancy and a segment length discrepancy (as the segment is half of its original length). However, the mapping algorithm finds three discrepancies, two extra segments, and one missing segment. These three discrepancies, when fixed, will result in the correct segment creation.</p>
   </body>
</html>