<!doctype HTML public "-//W3C//DTD HTML 4.0 Frameset//EN">

<html>

<!--(==============================================================)-->
<!--(Document created with RoboEditor. )============================-->
<!--(==============================================================)-->

<head>

<title>User Defined Events</title>

<!--(Meta)==========================================================-->

<meta name=generator content="RoboHELP by eHelp Corporation - www.ehelp.com">
<meta name=generator-major-version content=0.1>
<meta name=generator-minor-version content=1>
<meta name=filetype content=kadov>
<meta name=filetype-version content=1>
<meta name=page-count content=1>
<meta name=layout-height content=1439>
<meta name=layout-width content=644>
<meta name=date content="09 1, 2005 1:56:45 PM">


<!--(Links)=========================================================-->

<link rel="StyleSheet" href="../../css/main_styles.css">



<!--(Style Sheet)===================================================-->

<style>
<!--
body {background-color: #ffffff;}
-->
</style>


</head>

<!--(Body)==========================================================-->


<body class="bodydocs" onLoad="top.pageLoader()" bgcolor="#FFFFFF">


<h1 CLASS=Section>User Defined Events</h1>

<h1>Machine Control Events</h1>

<p CLASS=Paragraph>Machine Control Events are used to convey to the Machine 
 Tool information about the physical state of the Machine Tool. This may 
 include turning on the spindle at a specific speed and direction, turning 
 on the coolant or clamping the work piece. There is a set of standard 
 machine control events that cover most of the common functions that occur 
 on machine tools. However, there are a great variety of functions on machine 
 tools that are not addressed by the standard set of Machine Control Events. 
 There is a mechanism for you to define your own set of Machine Control 
 Events, User Defined Events. <span style="font-style: normal;">The architecture 
 that underlies Machine Control Events, is the same architecture that underlies 
 User Defined Events. Therefore, all Machine Control Events are defined 
 as User Defined Events.</span> This gives you the ability to modify existing 
 Machine Control Events as well as creating your own.</p>

<h1>User Defined Events</h1>

<p CLASS=Paragraph>User Defined Events (UDEs) provide a general mechanism 
 by which the structure of Machine Control Events can become user definable. 
 Once UDE's are created they are then treated like Machine Control Events. 
 They are presented during the specification of the <span style="font-style: italic;">Start 
 of Path</span>, <span style="font-style: italic;">End of Path,</span> 
 and <span style="font-style: italic;">In Path</span> Machine Control Event 
 sets.</p>

<h2>How They Are Stored</h2>

<p CLASS=Paragraph>The description of the Event structure and the data 
 associated with the Events is stored and is output during postprocessing. 
 All UDE's are defined in a file called ude.cdl in the <span style="font-style: italic;">$UGII_BASE_DIR/mach/resource/user_def_event/ude.cdl. 
 </span><span style="font-style: normal;">The ude.cdl file defines events 
 and is referenced by the configuration file.</span></p>

<p CLASS=Paragraph><span style="font-style: normal;">Parameters that are 
 set in the UDE are converted to MOM variables.</span></p>

<h2>How They Are Output</h2>

<p CLASS=Paragraph>All of the standard Machine Control Events are output 
 by Post as events and parameters. Postbuilder will create postprocessors 
 that use these events and parameters. When a non-standard UDE is output 
 by Post during postprocessing a MOM variable is created for each parameter 
 defined in the UDE. It is up to the user to process the non-standard UDE 
 variables. The standard UDE variables are described in the <span style="font-weight: bold;">Machine 
 Control Events section</span>.</p>

<p CLASS=Paragraph>The order of output of events to either Post or to the 
 CLS is determined by the order of output on the Machine Control dialog. 
 For more information on the order go to the section titled <a HREF="../concepts/concepts.html#ordrofevnts"><span 
 style="font-weight: bold;">Order Of Events</span></a>.</p>

<p CLASS=Paragraph>Each UDE will be denoted by an EVENT. The text following 
 the UI_LABEL <!--kadov_tag{{<spaces>}}-->&nbsp;<!--kadov_tag{{</spaces>}}-->is 
 shown in the UDE dialog. The example below is a part of the ude.cdl file 
 that describes the format of the Spindle command. Note that the dialog 
 is created from the contents of the ude.cdl file.</p>

<p CLASS=Image><img src="../graphics/ude_cdl.gif"
					x-maintain-ratio=true
					style="border-style: none;
							margin-top: 0px;
							margin-bottom: 0px;
							margin-left: 0px;
							margin-right: 0px;
							width: 624px;
							height: 202px;
							float: none;"
					width=624
					height=202
					border=0></p>

<p CLASS=Paragraph>&nbsp;</p>

<p CLASS=Image><img src="../graphics/ude_dialogs.gif"
					x-maintain-ratio=true
					style="border-style: none;
							margin-top: 0px;
							margin-bottom: 0px;
							margin-left: 0px;
							margin-right: 0px;
							width: 260px;
							height: 306px;
							float: none;"
					width=260
					height=306
					border=0></p>

<p>&nbsp;</p>

<p style="margin-bottom: 0;">&nbsp; </p>

</body>

</html>
