nx4 post processor mt11060 .pdf

8/10/2019 nx4 post processor mt11060 .pdf

1/254

Post Building Techniques

Student GuideJuly 2006

MT11060 Post Builder 3.5

Publication Number

mt11060_g NX 4


2/254

Manual History

ManualRevision

UnigraphicsVersion

PublicationDate

Version 17.0 February 2001

Version 18.0 May 2002

Unigraphics NX February 2003

Unigraphics NX 2 March 2004

NX 3 May 2005NX 4 July 2006

This edition obsoletes all previous editions.

Proprietary & Restricted Rights Notice

This software and related documentation are proprietary to UGS Corp.

2006 UGS Corp. All Rights Reserved.

All trademarks belong to their respective holders.

2006 UGS Corp.

All Rights Reserved.

Produced in the United States of America.

2 Post Building Techniques Student Guide mt11060_g NX 4


3/254

Contents

The NX/Post Post Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Post Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Building a Post Processor with Post Builder . . . . . . . . . . . . . . . . . . 2-1

Post Builder Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Activity Preparation for using the Post Builder . . . . . . . . . . . . . . . 2-4Post Builder Menu and Tool Bars . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6Using the Post Builder to Create a New Post Processor . . . . . . . . . . . 2-9

Activity Introduction to Post Builder . . . . . . . . . . . . . . . . . . . . . . 2-11NX/Post Builder Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16Machine Tool Parameter Selections . . . . . . . . . . . . . . . . . . . . . . . . . 2-18Program And Tool Path Property Page . . . . . . . . . . . . . . . . . . . . . . 2-20

Activity Word Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22Program and Tool Path Property Page (continuation) . . . . . . . . . . . . 2-29

About the interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30Activity Program and Tool Path Parameters . . . . . . . . . . . . . . . . 2-35

NC Data Definitions Property Page . . . . . . . . . . . . . . . . . . . . . . . . . 2-42Activity NX Data Definition . . . . . . . . . . . . . . . . . . . . . . . . . 2-45Creating New M or G code groups . . . . . . . . . . . . . . . . . . . . . . . . . . 2-54

Activity Creating a New M-Code Group . . . . . . . . . . . . . . . . . . . 2-55Output Settings Property Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57

Activity Output Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-61Post Files Preview Property Page . . . . . . . . . . . . . . . . . . . . . . . . . . 2-63Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-64

Post Builder for Wire EDM Applications . . . . . . . . . . . . . . . . . . . . . 3-1

Using Post Builder to create 2-axis and 4-axis Wire EDM PostProcessors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Activity Creating a 2axis Wire EDM Post . . . . . . . . . . . . . . . . . . 3-5Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

Post Builder for 5-Axis Mill Applications . . . . . . . . . . . . . . . . . . . . . 4-1

Using Post Builder to create 5-axis Mill Post Processors . . . . . . . . . . 4-2Activity Creating a 5Axis Mill Post with Post Builder . . . . . . . . . . 4-8Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

UGS Corp., All Rights Reserved Post Building Techniques Student Guide 3


4/254

Contents

Post Builder for Lathe Applications . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Using Post Builder to create Lathe Post Processors . . . . . . . . . . . . . . 5-2Activity Creating a Lathe Post with Post Builder . . . . . . . . . . . . . . 5-5Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Creating Mill-Turn Post Processors . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Mill-Turn Centers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2Mill-Turn and the Post Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3Heads for Mill-turn centers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4Creating a Mill-Turn Post Processor . . . . . . . . . . . . . . . . . . . . . . . . . 6-55 Axis Mill-Turn Centers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-115-Axis Mill-Turns and the Post Builder . . . . . . . . . . . . . . . . . . . . . . 6-13

Activity Creating a 5Axis Multi-Link Mill-Turn Post . . . . . . . . . 6-14Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-28

Tcl Basics for Post Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Tcl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2Tcl Command Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3Tcl Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4Tcl Control of Word Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5Tcl Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6Tcl Mathematical Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7

Variable Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8Tcl Variable Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9

Variable Substitution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10Variable Substitution Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11Activity Tcl Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12Tcl Procedures and Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14Tcl I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16Tcl Special Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17Constructing a Simple Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18Tcl Flow Control Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-21

Activity Tcl Flow Constructs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-24Tcl Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27Tcl and Unigraphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28

Tcl Reference Manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-29Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-30

Customizing a Post Processor with Post Builder . . . . . . . . . . . . . . . 8-1

Activity Custom Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17

User Defined Events (UDEs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

User Defined Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

4 Post Building Techniques Student Guide UGS Corp., All Rights Reserved mt11060_g NX 4


5/254

Contents

User Defined Event Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3Activity Creating User Defined Events . . . . . . . . . . . . . . . . . . . . . 9-6Activity Modify the Coolant UDE for Thru-Spindle . . . . . . . . . . . 9-11Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15

Virtual NC Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Integrated Simulation and Verification Overview . . . . . . . . . . . . . . 10-2Machine Tool Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3

Activity Using Post Builder to crate a VNC . . . . . . . . . . . . . . . . . 10-5Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7

A Guide to Best Practices of Building a Post Processor . . . . . . . . 11-1

Custom Command Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Advanced Post Building Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Guide to modifying and customizing existing post processors . . . . . . B-2Activity Modifying an Event Handler . . . . . . . . . . . . . . . . . . . . . B-4Definition File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-6

Activity Modifying a Definition file . . . . . . . . . . . . . . . . . . . . . . . B-7Machine Kinematics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-11Circles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-12

Advanced Kinematics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-13Rotary Axes Designations . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-144th Axis Center Offsets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-15

5th Axis Center Offsets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-16Axis Rotation (Standard or Reverse) . . . . . . . . . . . . . . . . . . . . B-17Zero Position Offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-20Pivot Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-22Dual Table Kinematics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-24Special Case 5-Axis Dual Table . . . . . . . . . . . . . . . . . . . . . . . . B-26UG/Post Postprocessing using Runugpost . . . . . . . . . . . . . . . . B-28

Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-29

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1

UGS Corp., All Rights Reserved Post Building Techniques Student Guide 5


6/254


7/254

Lesson

1 The NX/Post Post Processor

Purpose

This lesson describes the post processing function of NX and the variouscomponents of aNX/Postpost processor. An overview of the Post Buildermodule is also presented.

Objective

Upon completion of this lesson, you will be able to:

Understand the terminology and interrelationships of the variouscomponents ofNX/Post.

Understand the use of thePost Builderas a tool to build post processors.

UGS Corp., All Rights Reserved Post Building Techniques Student Guide 1-1


8/254

The NX/Post Post Processor

Post Processing

You use the Manufacturing applications of NX to generate tool paths. Thetool path consists of GOTO points and other information that controls the

movement of the tool. This tool path usually cannot be used for machiningsince each machinetool/controller combination has different requirements,tool change requirements, and software characteristics, such as the sequenceof G codes which are permitted on a line of output.

The tool path must be formatted to match the unique characteristics of themachine tool/controller combination. The procedure of modifying this generictool path to a form that can be understood and used by the machine toolcontroller is called post processing.

Two elements arerequired for post processing. They are:

Tool path - A NX internal tool path.

Note: Pre V16 legacy data must be imported into the current version of NX inorder to be post processed usingNX/Post.

Post processor - this is a computer program that reads, converts andreformats tool path information for a particular machine tool/controllercombination.

NX/Post Execute

NX provides a post processor, NX/Post, which utilizes NX tool path data

as input, and outputs machine controller readable NC/CNC code. PostProcessors for NX/Post are customizable through the use of user createdEvent Handler and Definition files. These files, in conjunction withNX/Post,are used to generate output for the simplest to the very complex of machinetool/controller combinations.

TheNX/Postprocessor can be used to generate output for simple millingmachines and lathes to ultra complex multi-axis (4+ axis) machining andproduction centers (a production center is considered to be a milling/turningtype machine). The extensibility ofNX/Postpost processors is achievedthrough the scripting languageTcland the use of the NX concept of Definition

files.The followingflowchart illustrates the steps required to process (post process)tool path data in an acceptable format for a machine tool/controller usingthe NX/Postpost processor:

1-2 Post Building Techniques Student Guide UGS Corp., All Rights Reserved mt11060_g NX 4


9/254


TheNX/Postexecute module consists of the following components:

Event Generator - sends Events and variables to NX/Postwhen youpost process. An Event is a collection of data which is processed by

NX/Post, creating data which causes a specific action(s) by the machine

tool/controller.

Event Handler -is a file containing a specific set of instructions, writtenin the Tcl scripting language, dictating how each event type is to beprocessed. This file is created when using Post Builder.

Definition file -is a file containing specific information about machinetool/controller format. Thisfile is also created when using Post Builder.

Outputfile -is a machine tool readable file generate byNX/Post, passedto the machine tool/controller, that executes specific machine toolinstructions.

The Event Generator, Event Handler, and the Definition file areinterdependent and together convert the internal tool path into a setof instructions that can be read and executed by the specific machinetool/controller combination.



10/254


Manufacturing Output Manager (MOM)

The Manufacturing Output Manager, referred to as MOM, is a utility programused byNX/Postforgenerating output based upon data that is stored within

the internal tool path. NX/Postuses the MOM to start, add data and specifyfunctions to the interpreter, and to load Event Handlers and Definition files.

Post Builder

TheNX/Postmechanism uses Tcl (Tool Command Language) scripts and filesfor post processing. These files extract information from the part file, processthis information according to defined rules, formats the information for outputand then outputs the data to a file which is later used by the machine controlfor machining a part. These files are highly customizable, and if manuallyedited, require the working knowledge of the Tcl scripting language.

Post Builder provides a graphical User Interface for building posts. Thedesign intent of thePost Builderis to create all the necessary files needed forpost processing without detailed knowledge of the file structure or Tcl.

Post Builderis very flexible and allows for the definition of various types ofoutput blocks and word addresses. Sequence of output in the NC outputfile is very easy to control for blocks involving the start of program, start ofoperation, end of operation, end of program, tool changes and canned cycles.

Post Builder currently configures post processors for the following:

3-axis milling machines

3-axis mill-turn centers (XZC)

multi-axismill-turn centers

4-axis milling machines with a rotary table or a rotary head

5-axis milling machines with dual rotary heads or rotary tables

5-axis milling machines with rotary head and rotary table

2-axis lathes

2 and 4-axis Wire EDM machines



11/254


The followingflowchart illustrates the process of building a post processorusing the Post Builder:



12/254


Summary

In this lesson you were introduced to:

The post processing function ofNX/Post.

Interrelationships and functionality of the variousNX/Postcomponents.



13/254

Lesson

2 Building a Post Processorwith Post Builder

Purpose

This lesson describes the procedures of building post processors throughthe use of the Post Builder.

Objective


Understand the various components ofPost Builder.

Use thePost Builderto build a 3-axis mill post processor.



14/254

2

Building a Post Processor with Post Builder



15/254


Post Builder Overview

Post Builderprovides an easy to use interface for creating and modifying postprocessors. Drag and drop functions allows the creation of formats, addresses,

sequences and blocks. ThePost Buildercreates the defi

nition of outputblocks, formats for addresses and controls the sequence of output for the startand end of program, start and end of operation and tool path Events.

ThePost Builderworks in conjunction with three files.

TheDefinition file, with .def extension, contains information about themachine tool/controller functionality and format requirements.

TheEvent Handler, with .tcl extension, contains instructions of how eachEvent type is to be processed.

ThePost Builder parameterfile, with .pui extension, contains theparameters that are used byPost Builderfor an individual post. Thisfile is referenced whenever you would edit or customize a post processorusing thePost Builder..

An existing library of post processors is provided by UGS athttp://ftp.ugs.com/unigraphics/pb_posts/post_index.htm.

Machine tools and machine controllers in industry vary greatly, you shouldbe aware that postprocessors made available on this ftp site should beconsidered as example postprocessors only and considerable adjustment of

these postprocessors may be required to suit the specifi

c machine tool.The activities, in this lesson, will use a copy of the main CAM mach\resourcedirectory. The logic behind this concept is that you can experiment with

various ideas and techniques without the worry of corrupting any system filesthat would normally be used by NX/Postor Post Builder.

You will assume that the CAM Mach\resource directory has not been copiedto your home directory (unless instructed otherwise by your instructor).

The following activity will take you through the process of creating a copy ofthe mach\resource directory structure to your home directory.



16/254

2


Activity Preparation for using the Post Builder

In this activity you will make a copy of the MACH/RESOURCE directorystructure in the home directory and modify the directories for read/write

access.Step 1: Copy the mach\resource directory.

Start NX.

On the NX Main Menu Bar, select Help NX Log File toverify themach\resourcedirectory being used. Search for theenvironment variableUGII_CAM_RESOURCE_DIR.

Open an XP Explorer window and locate the directory fromthe previous action item.

Highlight themach\resourcedirectory, right click onmach\resourcedirectory and select Copy.

Highlight your home directory, right click on your homedirectory and select Paste.

Step 2: Copy the environmentfile, ugii_env.dat to your home directory.

From the XP Explorer window locate theugii_env.dat file in the\NXxx0\UGIIdirectory (note: xx represents current version).

Highlight theugii_env.dat file, right click on the ugii_env.datfile and select Copy.

Highlight your home directory, right click on your homedirectory and select Paste.

Step 3: Edit the ugii_env.dat file to redefine your mach\resource directorylocation.

Highlight theugii_env.dat file from your home directory, rightclick on the ugii_env.dat file and selectOpen with Wordpad

(note: prior to editing thisfi

le, you may have to associate thefile with either Wordpad or Notepad).

Scroll down the file until you find the following line:UGII_CAM_RESOURCE_DIR=${UGII_CAM_BASE_DIR}resource\and change the line toUGII_CAM_RESOURCE_DIR=${HOMEDRIVE}${HOMEPATH}\resowhere HOMEDRIVE is the letter designator of thedisk drive where your home directory is located andHOMEPATHis the directory structure.



17/254


Savethe file and exit from the editor.

Step 4: Change protection on the resource directory that was created.

Navigate to your home directory, highlight the resourcedirectory, right click, select properties, select the security tab,highlight the user nameEveryonein the upper dialog, on thelower dialog, check on Full Control.

ChooseOK until you return to the main Explorer dialog.

Step 5: Restart NX.

Log off NX and then log back on.

On the NX Main Menu bar, selectHelpNX Log Fileto verify

the updated\mach\resourcedirectory is being used.

This completes this activity.



18/254

2


Post Builder Menu and Tool Bars

Post Builderis started by choosing from the desktop menu bar,StartAllPrograms NX Post ToolsPost Builder.

When you initially enter thePost Builderyou will see thePost Builder MenuBar. The Menu Bar contains a Cue Lineand twoTool Bars.

TheCue line displays prompt messages on expected input by the currentoption. These messages indicate the next action which you need to take.

ThePost Filing toolbar contains three command buttons associated withcreatingnew, openingand savingpost processors.

Create Newoption allows for creation of a new post processor.

Open Existingoption allows for modification or editing of an existing postprocessor.

Saveoption allows for saving the post processor currently being worked upon.

TheHelp tool barcontains command buttons associated with help options.



19/254


Balloon Tipoption, when turned on, displays a message balloon that containsdescriptions concerning the functionality of the widget, whenever the cursorstops at a widget on the dialog.

Context Helpoption when turned on, changes the pointer into a questionmark. You can then click on an icon or item on the display that you are inquestion about and will see an explanation of the function of the icon or item.Click on the explanation window to close.

Users Manualis a complete online manual on the Post Builder. TheUsersManualalso contains MOM events and variables.

Pull Down menus are also available forFile, Options, Utilitiesand Help.

TheFilepull down menu allows for the creation, opening, saving and closingof post processor files. It also allows you to access a list of the most recentlyopened posts as well as exiting from the Post Builderprogram.

The Options pull down menu allows for the validation of the syntax,addresses, blocks and formats used in Custom Commands as well as thenumber of backup files created.

TheUtilitiespull down menu allows for modification of theTemplate_post.datdata file and the addition of MOM variables.



20/254

2


TheHelppull down menu allows for the activation ofBalloon Tips,ContextSensitive Help, access to the Users Manual, Release Notes and specificinformation concerning the version of thePost Builderbeing utilized.



21/254


Using the Post Builder to Create a New Post Processor

To create a new post processor, theNew option (or Create New commandbutton from the Post Filing Tool Bar) from the File pull down menu is

selected. TheCreate New Post Processormenu is displayed which allowsfor post processor naming and description, output units and machine tooland controller type.

ThePost Name field is the name of the post processor being created. Spacesare not allowed.

The Description field allows for text describing machine tool/controllercharacteristics and any other miscellaneous information.

Post Output Unitsselection buttons allow for inch or metric output.



22/254

2


Machine Toolallows the selection of various milling (multi-axis) machine,lathe configurations and Wire EDM type machines.

Controllerallows the selection ofgeneric, library or Users machinecontrollers.

Genericcontroller contains defaults for a generic control

Libraryallows theselection of controller from a NX supplied list

Usersallows the selection of post processors by browsing for specificpost processors

NOTE: You can select a previously created post processor.

TheMachine Tooland Controllerselections determine base files used to

create the post processor which contains various Events, commands andprocedures.

TheOk button enables acceptance of specifications for the machine tool andcontroller and advances you to the main editor portion of the user interface.

TheCancelbutton will dismiss the current menu, terminates the process ofcreating a new post processor and returns you to the Post Buildermenu bar.

When you create a new post processor, you can add the name of the postto thetemplate_post.dat file. This file contains a list of post processors forNX/Post to use. It defines a list of post processors that are available in the

Post Process dialog. The name of the post processor can be added by using theUtilitiespull down menu from the main tool bar.

The following activity will introduce you to the basic concepts and use of thePost Buildermodule.



23/254


Activity Introduction to Post Builder

Step 1: Start thePost Builder.

On the menu bar, choose Start All Programs Post ToolsPost Builder.

Select theNew option in theFilemenu and in thePost Namefield, name the post processor***_my_post, where***standsfor your initials.

Note: Use lower case characters only and no spaces.

Step 2: Select various initial options.

ForPost Output Unit you will accept the default ofinches.

ForMachine Tool you will accept the default ofMill.

Notice the 3-axis button bar.

Select the 3-axis button bar and notice the choices available.

You will accept the default for 3-axis.

Dismiss the 3-axis.

ForControlleryou will accept the default ofGeneric. Somecommon controllers are already provided. If you were to select the

Libraryoption, a list of available controllers would be available forselection as a template in building your post.

Select OK.

TheMain Editorproperty page (tab) is displayed.



24/254

2


Step 3: Save your newly created post processor to your home directory.

SelectFilefrom the menu bar and then select Save As.

Filter to your home post processor directory.

Visually check theFile name box, if the file name shown isthe same asthe file name of your post processor, select OK,

otherwise type in the correct name and then select OK.

When you save your file, three files are actually saved. The fileshave the extension .pui, .tcl, and.def.

In order for your newly created post processor to be includedin the NX Post Processing window by default, you must savethe post to your home post processing directory and modify thetemplate_post.dat file to include the new post processor. This fileis also located in the home post processor directory. This file isadded to the template_post.dat file by using the Utilitiesfunctionfrom the main menu bar.



25/254


Step 4: Add your newly created post processor to the template_post.datfile.

Choose theUtilitiesoption and then chooseEdit TemplatePosts Data Filefrom the pull down menu.

The Install Posts dialog is displayed.Browse to your post processor directory, then select thetemplate_post.dat file and choose OK.

Highlight theTOOL LISTline as shown below, then select theNEWbutton.

The Open dialog is displayed.

Navigate to your home directory and select the post processorwhich you previously saved.

Choose the Open button.



26/254

2


The path and name of the file are inserted into theTemplate_post.datfile.

Choose theOK button at the bottom of the dialog.

The Save As dialog appears.

If necessary, select the file nametemplate_post.dat.

Choose the Savebutton.

ChooseYesto the Save Aswarning message to replace thetemplate_post.dat file.

Step 5: Verify the post processor has been added to the Post Process dialog.

Return toa NX session and retrieve the part filemill_testfromyourstudent_home\partsdirectory.

Verify the post processor by entering the Manufacturing

Application in NX and selecting the post processing icon.

You will see your post processor,***_ my_post, under Available Machineson the Post Process dialog.



27/254


Choose Cancel.

Return to thePost Buildermain dialog.

This concludes the activity.



28/254

2


NX/Post Builder Parameters

As you proceed to build a post processor using thePost Builder, the userinterface takes on the appearance of a tabbed notebook. There are five major

tabs (also referred to as property pages) which are displayed. They are:Machine Tool, Program and Tool Path, NC Data Definition, Output SettingsandPost Files Preview. When a major property page is selected, menus andor sub property pages are displayed which allows for the setting of variousparameters used in creation of your post processor.

Machine Tool Property Page

TheMachine Tool property page allows the selection of output to includeCircular Records or to output linear motion only. You can also specifyLinearAxis Travel Limits,Home Position,Linear Motion Step Size and TraversalFeed Rate, Axis Multipliersand vectors representing theInitial Spindle Axis.



29/254


TheDisplay Machine Toolbutton gives a simple, generic, representation ofthe motions of the machine tool being configured.

TheDefaultbutton returns you to the state when the post was last saved forthe current "screen".

TheRestorebutton returns you to the state when you entered the current"screen".



30/254

2


Machine Tool Parameter Selections

In this activity you will examine and modify some of the various MachineTool Parameters located within the Machine Tool selection of the Post Builder

and will then restore them to their original state.Step 1: Examine the various Machine Tool Parameters.

Select Display Machine Tool.



31/254


Notice the display of a simple 3-axis mill.

Clear the display of the machine tool by selecting the Closebutton on the Machine Tool title bar.

Set the linear travel limits to the following: X=60, Y=50andZ=40.

Select theRestorebutton.

Notice that the X, Y and Z axis limits are returned to their originalsettings.

This concludes the activity.



32/254

2


Program And Tool Path Property Page

TheProgram and Tool Pathproperty page allows for creation, modificationand customization of the Event Handlers for all Events which occur by theuse of multiple function property pages. These functions, presented in thetab format, are:

Program allows the addition, modification and customization of ProgramStart Sequences, Operation Start Sequences, Tool Path Events includingMachine Control Events, Motion Events, Canned Cycles Events, OperationEnd Sequences and Program End Sequences.

G Codes property page will allow you to specify default G-codes used

throughout the post processor. Changing any of the G-codes in this list willupdate the G-codes globally.

M Codesproperty page will allow you to specify default M-codes usedthroughout the post processor. Changing any of the M codes in this list, willupdate the M-codes globally.

Word Summaryproperty page provides a summary of all addresses and allowsthe individual modification of the various elements used in data definition ofthe address. This property page allows the modification of groups of wordsthat use the same format and also allows modification of the format itself. If



33/254


you want to specify a different format for only one of the words, you would go tothe Format section of NC Data Definitions property page to make the change.The following parameters are available in Word Summary:

Word is the same that you will find in the word section of the NC DataDefinitions section.

Leader/Code - allows you to modify the leader for any word. The leader isthe character that precedes the numeric information. For example, if theword is X20.0000, then the leader is X. You can either enter a new leaderor right click on the existing leader and choose from the list.

Data Type - can beeither numeric or text. Specify text when the codeneeded cannot be formatted from a number directly into a word addressand a value. If, for example, you need a G84.1 for tapping and G81

(without a decimal) for drilling, you would make the G-motion word textand change all of the G codes to G81 instead of 81 with a leader of G.You may also go to the format property page in NC Data Definitions tochange only the G-motion word to text.

Plus (+) - allows a plus sign for all positive numbers. If set tono the (+)sign is not generated. A minus sign (-) is generated for all numeric data ifthe value isnegative.,

Lead Zero - will allow the output of leading zeroes.

Integer - controls number of digits output to the left of the decimal point.An error isgenerated if the numeric data exceeds the format specified.

Decimal (.) - controls whether or not numeric data has a decimal point.An error is generated if the decimal is suppressed and leading or trailingzeroes are not output.

Fraction - determines how many digits are output to the right of thedecimal point.

Trail Zero - will allow the output of trailing zeroes.

To change how the post processor will output a value of zero for coordinatedata, select either thezero_int or zero_realoption for formats in the NCData Definitions section under the Format property page. This will outputa zero in front of the decimal point.



34/254

2


Activity Word Summary

In this activity you will modify some of the various word formats and changethe sequence number. You will find these items in the Program and Tool Path

andWord Summary section of the Post Builder.

Step 1: Enter the Word Summary subsection of the Program and Tool Pathsection ofPost Builder.

Select theProgram and Tool Pathproperty page from thePostBuilderselection menu.

Select theWord Summaryproperty page.

Step 2: Change the X, Y, and Z-axis word format to 3.3.

Scroll down theWordcolumn until you reach the X address.

In the row of the X address, locate the integercolumn and

change the value from 4 to 3.



35/254


In the row of theX address, locate the fractioncolumn andchange the value from 4 to 3.

Notice that changing the X address word format also changesall other axis word formats.

Step 3: Change the F address format to 3.1.

Scroll down theWordcolumn until you reach theF address.

In the row of the Faddress, locate theintegercolumn andchange the value from 7 to 3. Thefractioncolumn is set to2,change the value to1.

Step 4: Change the S address format to 4.

In the row of the S address, locate the integercolumn andchange the value from 5 to 4. Thefractioncolumn is set to 0and does not need to be changed.

Step 5: Allow for maximum tool offset of 999 by changing the D addressto 3.0.



36/254

2


Scroll down theWordcolumn until you reach the address.

Notice that the range for the offset is from 0 to 99. The maximumnumber allowable since the format for the word is Digit_2.By changing the format toDigit_4, you can then allow for themaximum desired tool offset of 999.

Click on the word, under the Wordcolumn heading.

The Word D: property page is displayed.



37/254


Change the format from 2 to 4 by selectingthe drop down arrow and selecting Digit_4.

Change the number of available offsets from 99 to999 bychanging theMaximum valueparameter from99 to 999.

Choose OK.

Step 6: Change the sequence number to start at 5 and increment by 5

for each block afterwards.

SelectOther Data Elementsfrom theWord Summarypropertypage.

The Other Data Elements property page is displayed.



38/254

2


Change theSequence Number Startfrom10 to 5, then changetheSequence NumberIncrementfrom10 to 5.

Choose OK.

Step 7: Save the post and run it against the test part, mill_test.

If necessary, enter theManufacturing Applicationin NX.

Using the Operation Navigation Tool, expand theT12345-Aparent andselect the FACE_MILLINGoperation.

Select thepost processing icon.

Highlight your post processor which you have modified and selectOK.



39/254


The default directory is write protected, you will need to change the outputdirectory to your home directory.

Change the default for Output File to your home directory and then selectOK.

Verify the output.

Your output will be similar to the following:



40/254

2


Return to the Post Builder.

This completes the activity.



41/254


Program and Tool Path Property Page (continuation)

Word Sequencingallows the customization of the order of output of wordscomprising a block of NC data. The sequence order of the words will prevail

throughout the post processor. If for example, the X and Y words werereversed, it will be reflected in all of the blocks generated by all Events. Youcan also suppress or make any word active. IfBalloon Helpis active, eachword will display the context of that word. By default, a representative code isused to display that word, for example, the G17 word can also be G18 or G19.In other cases a D or T represents the adjust register or tool number register.

Custom Commandallows the addition of user created custom commands.These are Tcl procedures that are executed by an Event. When creating acustom command, thePost Builderwill place all of the correct syntax aroundthe body of the procedure that you are creating. The first line of the CustomCommand will be: proc PB_CMD_name_of_proc {} { and the last line willbe }.

TheCustom Commandprocedure will be processed in the sequence where itwas placed. ThePost Builderwill check the validity of the syntax of CustomCommands. Numerous Custom Commands, designed for common "specialapplications", are supplied with every release of the Post Builder..

Linked Postsallows you to specify posts that can be linked to your currentpost. Linked Posts would be applicable in situations where separate postshave been developed for special machine options such as right angle millingheads, specialized mill-turn centers, machining centers having more than two

rotary axis or any application that requires multiple post processors.



42/254

2


About the interface

Under the Program property page, you will see two distinct windowsdisplayed. The left most window, also referred to as theComponent Window,

contains a list of components that make up a program, displayed in a treeformat. When a component is selected, the parameters associated with thecomponent is displayed in the right most window, also referred to as theParameter Window.

A detailed explanation of the above numbered components follows:

The Program contains the following sequences;



43/254


An NC program has a beginning and an end with a number of operations orsteps in between. Collectively, the program is considered to be composed ofa sequential order of Events. Due to the way that tool paths are createdwithin NX, certain Events, such as Tool Change, Spindle Start or Approach

Motion Events canoccur at the start and end of an NC program and for eachoperation. At themarkers(designated as yellow rectangular blocks) of thesepre-determined Events, you can force certain instruction blocks to be output.This is referredto as a sequence. Understanding the sequences and theevents that trigger them allow you to properly place custom commands andblocks to obtain the desired output.

Three types of components can be attached to the markersof the varioussequences. They are identified by the following icons:

Cube: a normal block

Hand: a custom or MOM command

Page: an operator message

When a rectangular block appears light-blue in color, it designates thecomponent as being used by more than one marker. Changing one instancewill affect all instances of that component.

When a rectangular block appears white in color, it designates the componentas being used only once.



44/254

2


From the post processors view, an NC program consists offive sequences anda collection of Events that can occur in each operation. They are as follows:

Program Start Sequencewhich determines which blocks are output whenthis particular Event occurs before the tool path is read. This Eventoccurs before any other Event is processed.

Operation Start Sequencecontains Events and actions that will occurfrom the start of an operation to the first cut motion. Every operation willhave a first tool change, automatic tool change, manual tool change orno tool change.

Tool Path Sequenceconsist of Events and actions that pertain to machinecontrol, motion control and canned cycles.

Machine Controloptions control items such as coolant, spindle, tailstocksand clamps. They can also be used to change modes such as incrementalor absolute, inverse time, feed per minute/per revolution and constantsurface speed. Information can be passed to a post processor by parameterdata which is available at the Start of Operation. This includes feedsand speeds and any cutting parameters such as stepover and tolerances.Information can also be passed by way of User Defined Events-UDEs-(sometimes referred to as post commands). UDEs specified as Startof Post come out after the Start of Operation in the order specified byOperation Markers (a marker indicates Events that may occur). UDEsassociated with the tool, program, method, or any other parent group are

output before the Start of Operation Event. The recommended method ofoutput for the Start of Operation NC code is to organize all of the data(spindle speed, spindle direction, coolant status, length compensation,tool number) and then output this data as part of the Operation StartSequence.

Motionoptions describe how the post processor will process GOTOrecords in the tool path. All motion generated with a feed rate of zero isprocessed by the Rapid Move Event. If any motion types have a non-zerofeed rate, the Linear Move Event will be used. Motion types included inthis Event type are cut, engage, first cut, stepover and side cut. Circular

motion is handled by the Circle Move Event. An Event type for Nurbsis currently handled by the Post Builderfor Fanuc 6M, Siemens andHeidenhain controls.

Canned Cycleoptions describe how the post processor will handle cannedcycles. You can define and or modify the G-code, associated parameters,and output blocks that will be used with pre-defined cycles.

Operation End Sequencecontains Events and actions that occur fromthe final retract motion to the end of the operation. These are items like



45/254


returning to a home position or turning off the spindle and or coolant. Ifthe same End of Operation function is always going to be performed atthe end of every operation you can enter it into this sequence instead ofprogramming UDEs.

Program End Sequencecontains Events and actions that occur from theend of the last operation to the end of the program.

By activating the Add Block button, you can drag and drop a blockcomponentinto the location desired. The block component can be placedabove, below or next to an existing block component. Block components whichare available are listed in theAdd Block component available option menu.

Activating theDisplay Combined N/C Code Blocks toggle button will displayall block components in the form of NC codes. By default, block componentsare displayed in terms of their descriptions.

The Add Blockcomponent option menu describes the blocks which areavailable. You can create a new block component and apply it to a sequence.

You may also select one of the pre-defined block components.

TheTrashbin is used to delete any unwanted block component by draggingthe block component to the trash bin icon.

You can also delete the component by right clicking on the component andselecting delete from the drop down menu.

TheOperation Startsequence is one of the sequences which can occur witheach operation (one of the five sequences,Program Start, Operation Start,Tool Path, Operation End and Program End). Yellow colored blocks alwaysrepresent the sequence blocks (also referred to as markers).



46/254

2


You can neither add or delete Event blocks.

A block component can be placed above, below or next to an existing block.

If you right click on the block component, a pop-up menu appears which allowsyou toCut, Copy As or Deletea custom command block. If a block containsNC data, your options are Edit,Force Output,Cut,Copy Asor Delete.



47/254


Activity Program and Tool Path Parameters

In this activity youwill examine and modify Program and Tool PathParameters.

Step 1: Enter the Program and Tool Path section ofPost Builder.

Select theProgram and Tool Pathproperty page from thePostBuilderselection menu.

If necessary select the Programproperty page.

Step 2: Create a Program Start Sequence with a Rewind Stop Code of (#).

Select the Program Start Sequence from the ComponentWindow.

Double-click theblock componentcontaining the% from theSequence Window.

Prior to selecting this particular component, notice the light-bluecolor of the block component. This indicates that this particularblock is used again in either the same or another sequence. In thisparticular example, this block component appears again in theProgram Endsequence.



48/254

2


The Block: rewind_stop_codeproperty page is displayed.

Highlight the selection box containing the "%", usingMB3,selectChange Element, then selectUser Defined Expression.

The Expression Entry text box is displayed.

Change the "%" to "#".



49/254


ChooseOK from the Expression Entrytext box.

ChooseOK from theBlock: rewind_stop_codeproperty page.

As mentioned earlier in this activity, this block component alsoappears in theProgram Endsequence. A change to one blockcomponent will change all like components, regardless of theirlocation.

Step 3: Create a Program Start sequence with a G70G90G40G17G94block by modifying the Word sequence (NOTE: list the G codes inthe order shown).

Select theWord Sequencingproperty page from the menu.

Select the "G" block withMB1 and "drag" it to the beginningof the line.



50/254

2


Select the "G90" block withMB1 and "drag" it between the "G"and "G40" block.

Select the "G01" block and position it between the "G17" and"G43" block.

Step 4: Suppress the output of selected words.

Position the mouse over the "G97" block and click once tosuppress the "G97" output (turns from pink to blue).

Repeat the previous action and suppress the following: "G99",the three "P" words and the "E" word.

Step 5: Change the order of the "D" and "H" words.

Move the "D" word behind the "H" word.



51/254


Step 6: Change the tool parameter number to a maximum of 999 andminimum of 1.

Position the mouse over the "T" block and withMB3 selectEdit.

Change the maximum value from 99 to 999.

Change the minimum value from 0to 1.

Change the Tcode output format by selecting Edit underFormat and change the output field from2 to 3.

Choose,OKtwice.

Savethe post processor.


If necessary, enter theManufacturing application.



52/254

2


Using the Operation Navigation Tool, expand the T12345-Aparent and select the FACE_MILLINGoperation.

Select the post processing icon.

Highlight your post processor which you have modified andselect OK.

Accept the default forOutput Fileand then select OK.

Verify the output.

Your output should be similar to the following:



53/254






54/254

2


NC Data Definitions Property Page

TheNC Data Definitionsproperty page allows the definition of output formatsfor NC data.

Data definitions are broken down into four sub classifications, alsorepresented in tabular format. These sub classes are:

Blockdefines the format sequence of the instruction data that appearsas output. Blocks are made up of word elements, each being defined byan address and variable. There are two methods used to create a block.From the sequence or event property page you may drag a blank blockand drop it into a sequence or event. You can also edit any existing block

with the sequence, event or NC Data Defi

nitions block property page. Youmay then edit or build your block of data.

Worddefines the address, output format and the structure of the wordsthat comprise the instructions. Parameters associated with addressare format, maximum and minimum values, modality and leading andtrailing characters. A word is composed of an address leader, a number ortext and a trailer. An address leader may be any character. The addressleader is usually a single character such as G, M, X, Y, Z, etc. The traileris usually a blank character. You can specify the format for current words



55/254


from an existing list of formats or edit one of the existing formats. You canalso create a new format from the Format section of this property page.

Formatfor data output can be defined asreal, integeror character string.

Parameters for Formatvary according to the data type selected. Realnumbers are generally used for co-ordinate values; integersare used forregisters andcharacter stringsare used for commentary messages andspecial output.

Other Data Elementsallow for the control of sequence number output, theuse of special characters for word separation, end of block and messagestart and end codes.

You have probably noticed that block word address icons have symbolsassociated with them. These various icon symbols are switchedon when you

pass the mouse over the word address icon and select the pull down menuwithMB3. ChoosingOptional, No Word Separator, Force Output or anycombination of the three from the pull down menu will turn the varioussymbols on.

A checkmark before the option is an indicator of the option being turned on.

Force Outputforces the selected code for output within the current blockonly. This is useful, for example, to force out a T or some other code foreach tool change. By default all words are modal and will output only ifthe value changes from one block to the next. Force Outputcan only bespecified within the context of an Event or sequence.

No Word Separatorresults in the separator character being suppressedfollowing the word on output. This is used mainly for CLS output.



56/254

2


Optionalwill test to see if the address has a variable defined, if defined, itwill be used; if the variable is not defined, the address will be suppressed.Note that this option takes priority over the "Force Output" option.



57/254


Activity NX Data Definition

In this activity youwill modify a word address to force a G91 code and thenmodify the existing G84 tapping code to produce a G84.1 rigid tapping

cycle.Step 1: Enter NC Data Definition section of the Post Builder.

Select theNC Data Definitionfrom thePost Builderselectionmenu.

If necessary, choose theBlockproperty page.

Step 2: Change the incremental mode block address variable to force out a

G91 code.



58/254

2


Right click theincremental_modevariable and then selectForce Output .

Notice the white bar, indicatingForce Output, that appears onthe block address icon.

Step 3: Create a G84.1 Rigid tapping sequence.

You will now modify the existingG code that will be output for atapping cycle. You will change the standard G84 code toG84.1used in a rigid tapping sequence.

If necessary choose theN/C Data Definitionproperty page.

Choose theWordproperty page.

Highlight theG block, usingMB3, selectCreate.

The G_1 block is created.



59/254


The standard tapcode isG84 which represents a two digit integer. You will becreating a new tap code,G84.1, which represents a three digit, real number.

You will now create a new format to represent the new tapping code ofG84.1.

ChooseNewunder Format.

TheFormat: user_fmtproperty page is displayed.

EnterDigit_2_1in theFormat Nametext box.



60/254

2


Select theNumericradio button under Data Type.

TheFormat: user_fmtproperty page displayed is expanded.

Change the output to two places to the left of the decimal and one placeto the right.



61/254


Check the Output Decimal Point box.

Choose OK.

You have just completed setting the format for the G84.1code. You must nowset the parameters to allow customization of the tapping code.

Choose theProgram and Tool Pathproperty page.

If necessary, choose the Program Propertypage.

HighlightCanned Cyclesand then click onCommon Parameters.

TheEvent: Cycle Parameters property page is displayed.



62/254

2


Under theG Codeand Customizationsection, scroll down toCustomizeTapand check the box.

Choose OK.

You must now discard the previous tapping word block and create a tappingword block that allows for the G84.1word.

Choose theN/C Data Definitionsproperty page.

Choose theBlockproperty page.

Highlight cycle_tap.



63/254


Drag theG84block to the trash bin.

ChooseG_1 from the Add Wordpull down menu, then chooseG-UserDefined Expression.



64/254

2


Choose theAdd Wordbutton and drag the block to the beginning of theline.

TheExpression Entrydialog box is displayed.

Key in84.1into theExpression Entrybox.

Choose OK.

Save the post and run it against the test part, mill_test.

If necessary, enter theManufacturing applicationin NX.

Using the Operation Navigation Tool, expand theT12345-Aparent andselect the TAP_.5_13UNCoperation.



65/254



Highlight your post processor which you have modified and selectOK.

Accept the default forOutput Fileand then selectOK.

Verify the output.

Your output should be similar to the following:





66/254

2


Creating New M or G code groups

M and G codes are normally classified into logical groups. One such group istheMotiongroup. This group consists of the words G00 for rapid, G01 for

linear feed, G02 for circular interpolation CW, G03 for circular interpolationCCW and G80 thru G89 codes that represent drill cycles. Only one word fromthis group can be active at any given time, i.e. it is illogical for a machine tobe moving in the G00 mode (rapid) while making a G01 move (linear feed)simultaneously.

As a general rule,Post Buildersupports all common M and G code groups.In some instances however, certain machine tool/controller combinationssupport functions that are unique and require custom M or G codes. PostBuilderallows you to create these new M or G code groups as will be shown inthe following activity.



67/254


Activity Creating a New M-Code Group

In this activity, you will create a new M-code group to support a machine toolfeature of coolant through the tool. In a later activity, you will modify the

coolant UDE (User Defi

ned Event) to support this function within NX.Step 1: Continue using***_my_postin Post Builder.

If necessary open***_my_postusing thePost Builder.

Step 2: Create the new M-code word group.

Choose theNC Data Definitionsproperty page.

Choose theWordproperty page.

You will now create the new M-code word group by copying an

existing group. It is recommended, as a best practice, to copy agroup that is as similar as possible to the desired group. This willutilize the existing settings of the formats and word characteristics.

Step 3: Scroll down and then highlight theM_coolantword.

Step 4: Choose theCreatebutton.

TheM_coolant _1word is created.

Step 5: Change the name of the new word group.

Highlight theM_coolant_1word.

Change the name to M_coolant_thru.



68/254

2


Save the post processor.


In support of the creation of the new wordM_coolant_thru, you will need tobuild a UDE to turn on the coolant through the tool, create a custom commandto detect and interpret the coolant-through the tool UDE and then output theappropriate M-code. These steps will be performed in future activities.



69/254


Output Settings Property Page

The Output Settingsproperty page allows the generation and control ofoutput used in a listingfile. Items for output are X, Y and Z co-ordinates, 4th

and 5th-axis angle, and feeds and speeds. You can also specifyfi

le extensionsfor listing and NC output. Tabs are present forListing File control and forOther Options.

Under Other Options, the Output Control Elements section, GenerateGroup Outputallows the definition of how the post processor will processGroups. Operations may be organized into groups in order to create morethan one NC program in a part file. Each group is considered to be a separate

program. The default setting for this option is OFF. This option shouldonly be used when you want to post process more than one NC program ata time. Selecting more than one Group with this option turned ON willresult in one file containing all the Groups which have been selected. Thefile naming convention will be the name of your file with the name of thegroup appended. For example, if the base file name is "1234" and the groupis called "finish_mill", then the name of the file will be 1234_finish_mill.ptp.When Group output is set to ON, you should not mix operations in groupswith operations outside of groups. This will result in unpredictable output.When the group output setting is OFF, you will only get a single NC output



70/254

2


file called 1234.ptp. All operations in any selected group will be output in asingle file. Any group organization will be ignored.

The name of the group or program in NX can be used as the programname in theStart of Program Event. This will be passed as the variablenamemom_group_name. By changing the name of thePROGRAMin theOperation Navigator, and by creating a custom command, you can create theequivalence of a PARTNO statement.

Output Warning Messageswill result in warnings generated to a logfile.

Display Verbose Error Messages will result in detailed error messages beingdisplayed as your job is being post processed.

Activate Review Toolinitiates theReview Toolwhich aides in the debuggingof a post processor.

TheReview Toolconsists of three list boxes, each having horizontal andvertical scroll bars to assist in viewing the information.



71/254


The left most list box displays all the MOM events in sequential order thathave been created during the post processing cycle. Each MOM event isdisplayed with the appropriate MOM event number. Selection of an event

in this box will highlight the corresponding generated output code in theright list box.

The middle list box displays the MOM generated variables and addressesassociated with a particular Event in alphabetical order.

The right list box displays the output generated by the post processor.

Note: Extensions defined inside ofPost Builderwill be superseded by theoutput file name displayed in the post processor dialog. Default extensions forlisting output are.lpt, for machine output, the default is .ptp.

UnderUser Tcl Source, theSource Users Tcl file option allows the useof anexisting Tcl source program.



72/254

2


TheGenerate Virtual NC Controller (VNC) option, when checked, createsa Virtual NC Controller which is used by the Integrated Simulation and

Verification (IS&V) module of NX.



73/254


Activity Output Settings

In this activity youwill modify the data which is selected for output to alistingfile.

Step 1: Enter the Output Settings section ofPost Builder.

Select theOutput SettingsListing File.

Check theGenerateListing Filebox.

Uncheck the4th and 5th axis angle box.


If necessary, enter the Manufacturing application in NX.

Using the Operation Navigation Tool, expand the T12345-Aparent and select the FACE_MILLINGoperation.


Highlight your post processor which you have modified andselect OK.

Accept the default forOutput Fileand then select OK.

Verify the listingfile. The listingfile will be located in yourhome directory and will have a .lptextension. Open the filewith the Notepad editor and examine the contents.

The contents of the listingfile should be similar to the following:



74/254

2






75/254


Post Files Preview Property Page

ThePost Files Preview property page allows you to examine the Definitionfile (.def) and the Event Handlers (.tcl) before output generation. Newly

defi

ned code appears in the top window while the original code is displayedin the bottom window.



76/254

2


Summary

ThePost Builderis an efficient and robust tool that can be used to build themajority of the post processors that are required in todays manufacturing

environment. The following functions were used in conjunction of building apost processor with thePost Builder:

Created a directory structure for testing post processors developed withthe Post Builder.

Creation, modification and customization of Event handlers with theProgram and Tool path function.

Defined output formats.

Modified listing and output options.

Verified the output of your post processor using the PostReview Tool.



77/254

Lesson

3 Post Builder for Wire EDMApplications

Purpose

This lesson describes the procedures for building post processors for WireEDM applications through the use of the Post Builder.

Objective


Use thePost Builderto build 2 or 4-axis Wire EDM post processors.



78/254

3

Post Builder for Wire EDM Applications

Using Post Builder to create 2-axis and 4-axis Wire EDM PostProcessors

There are two different selections, available in the Post Builderfor creating

Wire EDM post processors. They are: 2-axis

4-axis

Once you make the selection of a 2-axis or 4-axis Wire EDM, you will thenneed to select the type of controller. Your choices available are:

Generic

Library

Users



79/254


Genericcontroller defaults to a generic template that uses generic featurescommon to most machine tool controllers.

Librarycontroller allows the selection of templates for Agie, Charmilles andMitsubishi (the main Wire EDM manufactures). These custom templatescontain the basic codes required for the most common Wire EDM functionssuch as threading, start and end of cut and power settings required by the

various controllers.

Userscontroller allows the selection, as a template, of a previous post thatyou have created. Selection is accomplished by choosing the Browsebuttonand then selecting the previously created post processor from a specificdirectory.

When youchoose the option for the controller that you will be using as atemplate, choosingOK will display the Machine Tool property page. Thisallows you to choose various parameters from the component window thatare necessary for your post processor.



80/254

3


Selection of theDisplay Machine Tool button, displays a generic view of themachine tool that corresponds to the type of machine selected.

The majority of the options/parameters available are self-explanatory.

The following activity will familiarize you with the functions and parametersthat are available when creating a Wire EDM post processor.



81/254


Activity Creating a 2axis Wire EDM Post

Step 1: If necessary, start the Post Builder.

On the Windows desktop menu bar, choose Start All

Programs NX Post Tools Post Builder.

Step 2: Create a new 2-axis Wire EDM post.

Select theNew option in theFilepull down menu and in theName field, name the post processor ***_wire_edm_post,where***stands for your initials.


UnderMachine Tool, selectWire EDMand accept the defaultof 2-axis.



82/254

3


UnderController, selectLibrary.

Select the down arrow and then select Charmillesfrom thepull down menu.

Select OK.

You will accept all defaults to create the post, however, before yousave your post, explore the various options available.

Save the post to your home post processing directory byselectingFile,Save Asand then specifying your postprocessorlocation.

Step 3: You will open a part file and browse for the post processor.

Return to a NX session and retrieve the part filewedm_2_4_axisfrom yourstudent_home\partsdirectory.

Step 4: Run the post against the test part, wedm_2_4_axis.

From theProgram Viewof the Operation Navigator, select thePROGRAMparent.

Select the Post Process icon from the Manufacturing

Operations tool bar.



83/254


ChooseBrowseand select the***_wire_edm_post.

Choose OK.

ChooseOK on the Postprocess dialog.

This completes this activity and the lesson.



84/254

3


Summary

The flexibility and robustness of the Post Builder allows you to easilygenerate post processors for 2 and 4 axis Wire EDM machines. In this lesson

you were introduced to: Creating a 2-axis Wire EDM post processor using the Post Builder tool.



85/254

Lesson

4 Post Builder for 5-Axis MillApplications

Purpose

This lesson describes the procedures for building post processors for 5-axismills through the use of the Post Builder.

Objective


Use thePost Builderto build 5-axis mill post processors.



86/254

4

Post Builder for 5-Axis Mill Applications

Using Post Builder to create 5-axis Mill Post Processors

There are currently, five different selections, available in the Post Builder forcreating 4 and 5-axis post processors. They are:

4-Axis with rotary table

4-Axis with rotary head

5-Axis with dual rotary heads

5-Axis with dual rotary tables

5-Axis with rotary head and table

Once you makethe selection of the type of multi-axis machine, the MachineToolproperty page is displayed, allowing you to choose General,Fourth AxisandFifth Axisparameters from the component window of the property page.



87/254


Selectionof theDisplay Machine Tool button, displays a generic view of themachine tool that corresponds to the type of machine selected.



88/254

4




89/254


Selecting the 4th or 5th axis from the component window of the MachineToolproperty page results in a rotary axis configuration property page beingdisplayed. This property page allows you to configure the various parametersfor each axis of rotary motion.



90/254

4


Parameters in this dialog are:

Rotary Axis- selection of the configure button results in the Rotary AxisConfiguration dialog displayed. This dialog allows the selection of plane ofrotation, axis word address designation, default linearization tolerance andthe method of handling Axis Limit violations.

Machine Zero to Rotary Axis Center- allows the definition of the center of

the 4th and or 5th axis in relation to the machine zero.

Rotary Motion Resolution- allows the specification of accuracy of rotation indegrees.

Maximum Feed Rate - allows the specification of the maximum degrees ofrotation per minute.

Pivot Distance- specifies the distance from the head or table rotation pivotpoint to the spindle gage point. This option is not valid for dual rotary typemachine tools.

Angular Offset- this offset adjusts the rotary angle motion and is generally

used when the tool axis of 0,0,1 does not result in angular positions of 0 forthe fourth and or fifth axis.

Axis Rotation- specifies the rotation of the 4th and or 5th axis according tothe right-hand rule.

Axis Direction- determines clockwise or counterclockwise direction of rotarymotion. Two options are available to determine axis direction. The firstoption, Magnitude Determines Direction, determines that the sign is usedto determine the angular position. B-90 and B90 are different positions



91/254


and are 180 degrees apart. Rotation to a larger angle is always clockwise,to a smaller angle, counterclockwise. The second option,Sign DeterminesDirection, signifies that the sign only is used for direction. B-90 and B90are the same position on the rotary table. B-90 designates that the table

will rotate counterclockwise to B90. The reverse is true for B90 to B-90, thetable will rotate clockwise.

Axis Limits- allows for control of the minimum and maximum angles thatcan be programmed for the fourth and or fifth axis. If the range of travel islimited to less than 360 degrees, the travel is measured clockwise. If thereis no range of travel limits, there are two possible choices for minimum andmaximum angles. If sign determines direction, 0 degrees is the minimum and360 is the maximum. If magnitude determines direction, the minimum is-359.999 and the maximum is 359.999.

Rotary Axis Can be Incremental- this check box allows rotary output to be

incremental with respect to the previous rotation.



92/254

4


Activity Creating a 5Axis Mill Post with Post Builder

Step 1: If necessary, start the Post Builder.

On the Windows desktop menu bar, choose Start

AllPrograms NX Post Tools Post Builder.

Step 2: Create a new 5-axis mill post with dual rotary tables.

Select theNew option in theFilepull down menu and in theName field, name the post processor ***_5_axis, where***stands for your initials.


Set thePost Output Unit to Inch.

Set theMachine Toolto Mill.

UnderMachine Tool, select the blue button and then select5-axis with dual rotary tables.

Set theControllerto Generic.

Choose OK.

The Property Pages dialog is displayed.



93/254


Select theMachine Toolproperty page.

You will accept all defaults to create the post, however, before yousave your post, explore the various options available under 4th and5th axis located in the Component Window.

Save the post by selectingFileSave.

Step 3: Run the post against the test

Documents

nx4 post processor mt11060 .pdf