<!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>What is the RCS</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">What is the RCS</div>
      <hr noshade="true">
      <table cellspacing="3" align="center">
         <tr valign="top">
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1">
               <p class="para_td"> <a class="links" href="javascript:void(0)" onclick="top.openFile('mfggeneral/parent_geom_mcs_over.html');return(false);">Overview</a></p>
            </td>
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1">
               <p class="para_td"> <a class="links" href="javascript:void(0)" onclick="top.openFile('mfggeneral/07topic_9.html');return(false);">How To</a></p>
            </td>
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1">
               <p class="para_td"> <a class="links" href="javascript:void(0)" onclick="top.openFile('mfggeneral/parent_group_mcs.html');return(false);">Options</a></p>
            </td>
         </tr>
      </table><br><p class="para_topic">The Reference Coordinate System (RCS) is used to relocate non-modeled geometric parameters (i.e. tool axis vectors, clearance planes, etc.) when an operation has moved from one section of a part to another. This occurs when you move an operation from one orient group to another, or transform, or create it from a template. This eliminates respecification of such parameters by allowing the retrieval and mapping of stored parameters.</p>
      <p class="para_topic">Every orient group has an RCS. When you create, edit, paste or transform an operation; the system uses the RCS of the geometry parent to determine the orientation of many parameters. This eliminates respecification of such parameters as engage vectors, clearance planes, etc., by allowing the retrieval and mapping of stored parameters. During subsequent operations, these parameters are repositioned to the current (moved) RCS.</p>
      <p class="para_topic">When a mill_orient (MCS) group is first created from the default templates, there is no RCS created with it, so the default RCS is the Absolute Coordinate System. &nbsp;When you edit or display this group, you will see that XM, YM, and ZM are displayed, but not XR, YR, and ZR. If operations are created or transformed under this group, there is no destination RCS, so the mapping is based on the absolute CSYS. &nbsp;The first time you select the Link MCS/RCS check box, or define the RCS in the group, the RCS is initialized and displayed. From then on, it is used for the mapping shown below.</p>
      <div class="title_division">Using the RCS </div>
      <p class="para_division">Creating new operations from a template, and transforming operations, both make use of the RCS, as follows: Non-modeled geometric parameters can be defined using associative (smart) or non-associative points, vectors, and planes. The associative point, vector or planes are defined in relation to geometry present in the part. Associative and non-associative parameters behave differently when, transforming an operation, and creating a new operation from a template as illustrated below.</p>
      <table cellspacing="3" align="center">
         <tr valign="top">
            <th bgcolor="#c0c0c0" colspan="1" rowspan="1"></th>
            <th bgcolor="#c0c0c0" colspan="1" rowspan="1">
               <p class="para_th">&nbsp;Transformation of Operations</p>
               <p class="para_th">(RCS Mapping)</p>
            </th>
            <th bgcolor="#c0c0c0" colspan="1" rowspan="1">
               <p class="para_th">Create New Operation from Template</p>
            </th>
         </tr>
         <tr valign="top">
            <th bgcolor="#c0c0c0" colspan="1" rowspan="1">
               <p class="para_th">Smart Objects</p>
               <p class="para_th">(associative)</p>
            </th>
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1">
               <p class="para_td">not mapped</p>
               <p class="para_td">(not translated with operation)</p>
            </td>
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1">
               <p class="para_td">become dumb, then mapped to RCS in new operation</p>
            </td>
         </tr>
         <tr valign="top">
            <th bgcolor="#c0c0c0" colspan="1" rowspan="1">
               <p class="para_th">Non-associative</p>
            </th>
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1">
               <p class="para_td">mapped</p>
               <p class="para_td">(translated with operation)</p>
            </td>
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1">
               <p class="para_td">mapped to RCS in new operation</p>
            </td>
         </tr>
         <tr valign="top">
            <th bgcolor="#c0c0c0" colspan="1" rowspan="1">
               <p class="para_th">Smart From and GoHome Pts.</p>
            </th>
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1">
               <p class="para_td">&nbsp;not mapped</p>
               <p class="para_td">(not translated with operation)</p>
            </td>
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1">
               <p class="para_td">become dumb, not mapped to RCS, maintain same relationship to ACS</p>
            </td>
         </tr>
         <tr valign="top">
            <th bgcolor="#c0c0c0" colspan="1" rowspan="1">
               <p class="para_th">Dumb From and GoHome Pts.</p>
            </th>
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1">
               <p class="para_td">not mapped</p>
               <p class="para_td">(not translated with operation)</p>
            </td>
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1">
               <p class="para_td">&nbsp;not mapped to RCS, maintain same relationship to ACS</p>
            </td>
         </tr>
      </table><br><p class="para_division">Notice that From and GoHome points (whether smart or dumb) are never mapped (translated) with a transformed operation or when creating a new operation from a template. This is because From and GoHome points are associated with the machine tool and not the operation. When an operation is transformed, From and GoHome points do not move. When creating a new operation from a template, From and GoHome points maintain the same spatial relationship with the Absolute Coordinate system in the new operation as in the template.</p>
      <p class="para_division">When creating a new operation from a template, you are essentially merging in an operation, but leaving the geometry behind. Because smart objects (other than From and GoHome points) are associated with geometry in the template, they must be disassociated with the geometry (made dumb) and then mapped to the RCS in the new operation. In other words, they maintain the same spatial relationship with the RCS in the new operation as in the template.</p>
   </body>
</html>