postbuilder, manual tool change, outputting a M00 at end.
Jul 23, 2014 Replied by guymalpass on topic Siemens NX Postbuilder. The machine will run at F20000 fine but I can't get the NX postprocessor to output NGC files with feedrates higher than 10000. For example I create a toolpath with a feed of 15000 but when I post process it gets reduced to 10000. What I was getting at with the m/min thing was a way of. Jul 16, 2012 Learn how to edit postprocessors in NX CAM using the graphical Post Builder user interface: +Modify the order of code output +Add a custom command to address special situations +Use User-Defined Events (UDEs) to allow NC programmers control over posted output +Add additional file information to posted output that CLS-bound postprocessors cannot. If you modify a post processor from the library, or create your own using NX Post Builder, you are encouraged to contribute it for inclusion in this library. Instructions to download Customer Postprocessor Library 1. Use your browser find function to search for a po 2. Click on the name to see the files required for eac 3.
postbuilder, manual tool change, outputting a M00 at end.
For starters,I am new to postbuilder and VERY new to tcl programming.
I am embarking on the 'learn as you go' method of making a post.
I have managed to figure everything out I need to except one simple, but important item.
The post does not output an M00 at the end of an operation that uses a tool flagged as 'manual tool change'
How can I get the post to do that??
My instinct says I need to write a custom command that querys the MOM_tool_change_type variable and outputs based on that.
Am I on the right track?
Can someone help me with the syntax to get an 'if' statement to work?
Thanks,
JAY
The Manufacturing application generates NX tool paths that are used to manufacture parts. Generally, you cannot just send an unmodified tool path file to a machine and start cutting because there are many different types of machines. Each type of machine has unique hardware capabilities and is controlled by a specific computer (also called the controller).
The controller accepts a tool path file and directs tool motion and other machine activity (for example, turning the coolant or air on and off). Just as each type of machine has unique hardware characteristics, each controller has unique software characteristics. For instance, most controllers require a particular code to turn on the coolant. Some controllers also restrict the number of M codes that are allowed in one line of output. This information is not in the initial NX tool path.
Without the correct formatting for a machine, the tool path file hits the controller’s brick wall of incompatibility.
Therefore, the tool path must be modified to suit the unique parameters of each different machine/controller combination. The modification is called postprocessing, and the result is a postprocessed tool path.
Two elements are essential for postprocessing. They are:
Tool Path Data | This is an NX tool path. |
A Postprocessor | This is a program that reads the tool path data and reformats it for use with a particular machine and its accompanying controller. |
The tool path data is reformatted by the postprocessor for the machine.
-640x360_tcm27-76744.jpg "Post")
Each postprocessor program is usually dedicated to a single type of machine/controller combination. You can modify postprocessor file parameters for functions of that particular type of machine/controller combination. However, you cannot modify the program for use with another type of machine/controller combination.
NX provides a generalized postprocessor program, Post, which inputs NX tool path data, and outputs machine readable NC code. Post is highly customizable and can be used for both very simple and very complex machine tool/controller combinations.
Post Builder is the NX product that is used to customize the postprocessor for each machine tool/controller combination.
NX provides the Post postprocessor that can properly format tool paths for specific types of machine/controller combinations. The Post postprocessor requires several elements:
Event Generator core module | Cycles through the events in a part file and communicates the data associated with each event to the Post postprocessor. An event is a collection of data, that when processed by Post, causes the NC machine to perform some specific action. This is activated by following the path Tools→Operation Navigator→Output→Post Postprocessor, or the icon. |
Event Handler (.tcl) file | Contains a set of instructions dictating how each event type is to be processed. This is created with Post Builder. |
Definition File (.def) file | Contains static information related to a particular machine tool/controller combination. This is created with Post Builder. |
Output File | Contains the postprocessed NC instructions that will be read and executed by the machine tool. |
Post User Interface file (.pui) | Used by Post Builder to edit the event handler and definition files. |
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 can be read and executed by a specific machine tool/controller combination.
The Post Postprocessor does the following:
Uses the Event Generator to read the events (tool path data) in the part file.
Each event is processed according to the instructions contained in the Event Handler.
The resulting instructions are formatted according to the information contained in the Definition File.
The postprocessed machine control instructions are written to the Output File.
The tool path data is postprocessed according to the instructions in the Event Handler and the formats in the Definition File.
Ug Nx Post Builder Manual 2019
To develop a post, you must create an event handler and a definition file. The recommened method to create these is with Post Builder. After creating a post, you will have three files: <post_name>.tcl, ~.def, and ~.pui.
Note | The Post Builder documentation is included in the Post Builder kit and accessed from within Post Builder. |
This is an example NC program for a specific controller:
This produces the output file, which must be loaded in the machine’s CNC controller. Usually this file is placed in a location on your Network or DNC (Distributed Numerical Control) system for distribution to the appropriate machine tool. Or, this file could be output on a paper tape or disk and manually loaded into the machine.
For information on creating or installing a post see the Post documentation.
Incoming search terms:
- membuka post builder nx 8