UG后处理定制命令英文解说讲解.doc

POST BUILDER CUSTOM COMMANDS In this NX A to Z article, we are going to talk about writing custom commands in Post Builder. Custom commands allow you to?get just about whatever you want in your machine code file. We all know that the graphical tools within Post Builder provide a great way to configure the standard components of a postprocessor, but what about the non-standard stuff – that is what custom commands are for.? For an introduction to Post Builder, click?here. TCL Postprocessors written for NX are written in a language called TCL (Tool Command Language). TCL is a scripting language, meaning that it is not compiled, and it’s syntax resembles C. TCL is a fairly straightforward language; however, it’s syntax can be troublesome. The link below is a very good resource for learning TCL; however, the best method for writing TCL is to copy it from an existing custom command that implements the same function you are trying to implement and then change the variables and expressions as required. For example, if you are trying to write and if…else loop, just find one in an existing custom command and change it as required to suit your desired functionality. This will help to eliminate a lot of the headaches due to syntax errors. /doc/tcl/index.html Manufacturing Output Manager (MOM) Before you write custom commands, you first need to understand how NX communicates with your postprocessor. When you postprocess a program from with NX, NX starts a program called NX Post. The primary component of NX Post is the?Manufacturing Output Manager (MOM). MOM is described in the NX Help Documentation as follows:?The Manufacturing Output Manager (MOM) is the central core of the NX Post postprocessor module. MOM converts tool paths from model files into manufacturing output (machine code) by adding the required functions and data as described below: The Event Generator reads through the tool path data, extracts events and their associated variable information, then passes the e