<!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>Operation Start Sequence</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">Operation Start Sequence</div>
      <hr noshade="true">
      <p class="para_topic">This sequence defines the blocks that the system can output at the start of each operation.&nbsp;Every operation has a first tool change, automatic tool change, manual tool change or no tool change.&nbsp;See the list of scenarios below for the events output with each scenario.</p>
      <p class="para_topic">The Operation Start Sequence has the following  <a class="links" href="javascript:void(0)" onclick="top.openFile('postbuilder/prog_tool_program.html');return(false);">Markers</a>:
      </p>
      <div class="title_division">Start of Path</div>
      <p class="para_division">The system initially generates and continues to generate this event when you postprocess an operation.&nbsp;This event occurs whether or not there is a tool change.</p>
      <div class="title_division">From Move</div>
      <p class="para_division">This event only occurs if you have programmed a FROM in the operation.&nbsp;If you attach a block to this marker, the system only outputs the block if there is a FROM in the operation.</p>
      <div class="title_division">First Tool</div>
      <p class="para_division">This event only occurs for the first tool change in a program.&nbsp;It is useful if you already have a tool in the spindle and you wish to handle this event differently. If this marker has no blocks attached to it, the blocks the system outputs are the same as the automatic tool change block.</p>
      <div class="title_division">Automatic Tool Change</div>
      <p class="para_division">This event occurs only if the operation contains a tool change.&nbsp;The system triggers a tool change only when the tool is different between the current operation and the previous operation.&nbsp;Note that this event is not related to the postprocessor command LOAD/TOOL.&nbsp;This event occurs before the system outputs the postprocessor command LOAD/TOOL.&nbsp;You cannot use any of the LOAD/TOOL data with this event.</p>
      <div class="title_division">Manual Tool Change</div>
      <p class="para_division">This event will occur only if there is a manual tool change.</p>
      <div class="title_division">Initial Move</div>
      <p class="para_division">The system generates this event only if the operation has a tool change.&nbsp;It creates this event if there is no positioning move after the tool change.&nbsp;The system triggers all Start Post User Defined Events before the initial or first move in an operation. This event is the best place to handle the data triggered by operation level UDEs.</p>
      <p class="para_division">If there is a drilling operation that contains no avoidance moves after a tool change, the post creates an initial move before the cycle. This is to allow the tool length compensation to be applied on the first Z move after the tool change. &nbsp;&nbsp;</p>
      <div class="title_division">First Move</div>
      <p class="para_division">This event only occurs if there is no tool change in the operation.&nbsp;Every operation has either a first move or an initial move. These events allow you to combine blocks either before, with, or after the first motion block of the operation.&nbsp;If the program contains no motion before the canned cycle, the system creates a motion block to position the tool to the rapid clearance plane above the hole.</p>
      <div class="title_division">Approach Move</div>
      <p class="para_division">This event only occurs if the operation contains an approach move. The system only outputs events attached to this event if the operation contains an approach move. The system outputs any blocks attached to this event before the actual approach move motion block.</p>
      <div class="title_division">Engage Move</div>
      <p class="para_division">This event only occurs if the operation contains an engage move. The system only outputs events attached to this event if the operation contains an engage move.&nbsp; The system outputs any blocks attached to this event before the actual engage move motion block.</p>
      <div class="title_division">First Cut</div>
      <p class="para_division">This event occurs before the first cut move.&nbsp;The system outputs any blocks attached to this event before the actual first cut move motion block.</p>
      <div class="title_division">Start of Pass</div>
      <p class="para_division">This event occurs at the start of every roughing or finishing wire edm pass. Use this event to add information (power, offsets, flushing, etc.) that is different on each pass. </p>
      <div class="title_division">Cutcom Move</div>
      <p class="para_division">If Cutcom is active, this event occurs after the start of pass event. Use this event to specify the NC code needed to initiate cutter compensation. </p>
      <div class="title_division">Lead In Move</div>
      <p class="para_division">This event occurs only when you specify a lead in move in NX.</p>
      <p class="para_division">There are four possible scenarios for event markers that can occur at the start of an operation. For more information click the  <a class="links" href="javascript:void(0)" onclick="top.openFile('postbuilder/prog_event_pos_scen.html');return(false);">Event Markers Possible Scenarios</a> link. 
      </p>
   </body>
</html>