<!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>Motion</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_topic5" id="xps10_pagetitle">Motion</div>
      <hr noshade="true">
      <p class="para_topic">The Motion dialogs describe how your postprocessor handle the&nbsp; </p><a name="prog_toolpth_prog_motion_goto_records"></a><p class="para_topic">GOTO records in the tool path.&nbsp; The system generates more types of motion generated than most machine controls can output. The Rapid move event handles all the motion the system generates that contains a feed rate of zero. This includes retract, approach, departure, return, rapid, and traversal.&nbsp;If any of these&nbsp; </p><a name="prog_toolpth_prog_motion_motion_types"></a><p class="para_topic">motion types have a non-zero feed rate, then the system uses the Linear Move event. The system uses the Linear Move event for all the&nbsp; </p><a name="prog_toolpth_prog_motion_cutting_motion"></a><p class="para_topic">cutting motion types.&nbsp;These include cut, engage, first cut, stepover, and side cut.&nbsp; All circular motion is handled by the Circle Move event.&nbsp;Note that a threading pass usually consists of a Linear Move (infeed), the threading motion itself (Lathe Thread Move), the pullout move (linear or rapid depending on the feed rate) and the traversal move (linear or rapid depending on the feed rate).&nbsp;Several user defined events ( </p><a name="prog_toolpth_prog_motion_gohome"></a><p class="para_topic">GOHOME and&nbsp;</p><a name="prog_toolpth_prog_motion_retract"></a><p class="para_topic">RETRCT) also generate motion. They use the Rapid Move event to output.&nbsp;The Nurbs event will be handled in a future release of Post Builder.</p>
      <p class="para_topic">The motion dialogs contain codes such as S, M03, M08, G41, G17, and D.&nbsp;This way the system outputs these codes with motion.&nbsp;The system outputs these codes only if the data changes or they are being forced out with alignment. The user defined event (COOLNT/FLOOD) defines the data for turning the coolant on.&nbsp;This event occurs either before the Start of Operation or in its sequence in the Start Post commands, depending on how the event was specified.&nbsp;Output the coolant in the first G01 block before you start cutting.&nbsp;This is the most reliable method. See the  <a class="links" href="javascript:void(0)" onclick="top.openFile('postbuilder/prog_mach_control.html');return(false);">Machine Control</a> section for more information on the recommended methods of outputting machine control information.
      </p>
      <p class="para_topic"><img align="bottom" src="graphics/pb_image6jo.gif" border="0"></p>
      <p class="para_topic">The motion dialog shows you a summary of the output for each of the lathe motion types. You can click any one of the blue buttons and edit that motion event.</p>
   </body>
</html>