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

<html>

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

<head>

<title>The MOM Postprocessor</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=2465>
<meta name=layout-width content=655>
<meta name=date content="03 25, 2004 2:15:57 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=ChapName>The MOM (Manufacturing Output Manager) Postprocessor</h1>

<h1>Postprocessing with MOM</h1>

<p CLASS=Paragraph>NX also provides the MOM postprocessor that <span style="font-style: italic;">can</span> 
 properly format tool paths for specific types of machine/controller combinations. 
 The MOM postprocessor, like GPM, also requires several elements:</p>

<ul>
	
	<li class=kadov-p-CListBullet><p CLASS=ListBullet>the <span style="font-weight: bold;">Event 
 Generator</span> - is the core module that will cycle through the events 
 in the part file.</p></li>
	
	<li class=kadov-p-CListBullet><p CLASS=ListBullet>the <span style="font-weight: bold;">Event 
 Handler</span> - is a file containing a set of instructions dictating 
 how each event type is to be processed.</p></li>
	
	<li class=kadov-p-CListBullet><p CLASS=ListBullet>the <span style="font-weight: bold;">Definition 
 File</span> - is a file containing static information related a particular 
 machine tool/controller combination.</p></li>
	
	<li class=kadov-p-CListBullet><p CLASS=ListBullet>the <span style="font-weight: bold;">Output 
 File</span> - is the file where the postprocessor puts the postprocessed 
 NC instructions that will be read and executed by the machine tool.</p></li>
</ul>

<p CLASS=Paragraph>The Event Generator, the Event Handler, and the Definition 
 File are dependent upon each other. Together they transform the tool path 
 data contained in the part file into a set of formatted instructions that 
 they can be read and executed by a specific machine tool/controller combination.</p>

<p CLASS=Paragraph>The MOM postrocessor:</p>

<ol>
	
	<li class=kadov-p-CListNum><p CLASS=ListNum>Uses the Event Generator 
 to read the events (tool path data) in the part file.</p></li>
	
	<li class=kadov-p-CListNum><p CLASS=ListNum>Each event is processed 
 according to the instructions contained in the Event Handler.</p></li>
	
	<li class=kadov-p-CListNum><p CLASS=ListNum>The resulting instructions 
 are format according to the information contained in the Definition File.</p></li>
	
	<li class=kadov-p-CListNum><p CLASS=ListNum>The postprocessed machine 
 control instructions are written to the Output File.</p></li>
</ol>

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

<p CLASS=Paragraph
	style="margin-left: 40px;"><span style="font-weight: bold;">Figure 
 1-5</span> The tool path data is postprocessed according to the instructions 
 in the Event Generator and the formats in the Definition File.</p>

<p CLASS=Paragraph>The following section describes the processing steps 
 required to postprocess a tool path. An illustration summarizes these 
 steps.</p>

<h1>&nbsp;</h1>

<h1>MOM Postprocesssing Steps</h1>

<p CLASS=Paragraph>This section describes the several requirements for 
 postprocessing using the MOM postprocessor. To simplify the description 
 of the process, the requirements are presented as sequential steps in 
 the following order:</p>

<ul>
	
	<li class=kadov-p-CListBullet><p CLASS=ListBullet>Create an Event Handler</p></li>
	
	<li class=kadov-p-CListBullet><p CLASS=ListBullet>Create a Definition 
 File</p></li>
	
	<li class=kadov-p-CListBullet><p CLASS=ListBullet>Create the tool path 
 in NX</p></li>
	
	<li class=kadov-p-CListBullet><p CLASS=ListBullet>Create a Postprocessed 
 File</p></li>
</ul>

<h5>&nbsp;</h5>

<h5>Create an Event Handler</h5>

<p CLASS=Paragraph>Prior to postprocessing tool path data, you must create 
 an Event Handler (with the extension .tcl) for the type of machine/controller 
 you plan to use to cut the part. The Event Handler contains a detailed 
 set of instructions for processing each event type.</p>

<h5>&nbsp;</h5>

<h5>Create a Definition File</h5>

<p CLASS=Paragraph>Prior to postprocessing tool path data, you must also 
 create a Definition File (with the extension .def) for the type of machine/controller 
 you plan to use to cut the part. The Definition File contains instructions 
 about:</p>

<ul>
	
	<li class=kadov-p-CListBullet><p CLASS=ListBullet>General machine attributes.</p></li>
	
	<li class=kadov-p-CListBullet><p CLASS=ListBullet>The addresses that 
 are supported for the particular machine.</p></li>
	
	<li class=kadov-p-CListBullet><p CLASS=ListBullet>The attributes of 
 each address (format, minimum value, maximum value, etc.)</p></li>
	
	<li class=kadov-p-CListBullet><p CLASS=ListBullet>A set of block templates 
 that describe how the addresses fit together to perform the desired action 
 at the machine tool.</p></li>
</ul>

<h5>&nbsp;</h5>

<h5>Create the Tool Path</h5>

<p CLASS=Paragraph>Create the desired tool paths using the Manufacturing 
 application. For detailed information on the use of this application , 
 refer to the <span style="font-style: italic;">NX Manufacturing Online 
 Help</span>.</p>

<h5>&nbsp;</h5>

<h5>Create a Postprocessed Tool Path</h5>

<p CLASS=Paragraph>As described previously, the MOM postprocessor is a 
 program that reads the tool path data and converts it, according to the 
 instructions in the Event Handler and the formats in the Definition File, 
 into machine-readable commands that are compatible with the particular 
 machine/controller combination that you will use to cut the part.</p>

<p CLASS=Paragraph>You can postprocess with the GPM by invoking the POSTPROCESS 
 option in the Operation Manager.</p>

<p CLASS=Paragraph>You are require to select the name of the machine tool 
 that you are postprocessing for from the list box and specify the name 
 of the Output File (with the extension .ptp) in the text field.</p>

<h5>&nbsp;</h5>

<h5>Load</h5>

<p CLASS=Paragraph>Finally, you can load the tool path information into 
 the machine tool controller and machine the part.</p>

<p CLASS=Paragraph>Refer to Figure 1-4 for an illustrative summary of these 
 steps in postprocessing.</p>

<p><img src="../graphics/ch1fi02.gif"
		x-maintain-ratio=true
		style="border-style: none;
				margin-top: 0px;
				margin-bottom: 0px;
				margin-left: 0px;
				margin-right: 0px;
				width: 502px;
				height: 652px;
				float: none;"
		width=502
		height=652
		border=0></p>

<p CLASS=Paragraph
	style="margin-left: 40px; margin-bottom: 0;"><span style="font-weight: bold;">Figure 
 1-6</span> The above illustrates the stages of MOM Postprocessing a tool 
 path in order to operate a particular machine. </p>

</body>

</html>
