NX Post processors have capabilities beyond toolpath translation – they can also be used to detect and enforce programming styles. By developing custom warning messages, a user can ensure proper CAM programming. It can be tempting to put these into a programming template, but by putting the functionality right into the post, the user can more consistently keep programming mistakes from making it to your machine controller.

This video shows off several examples of how a custom post processor warning can be used to prevent machine/part/tool crashes, weed out invalid machine code, and enforce desirable programming styles. All demos were made using NX Post Builder 12.

The three examples we show are:

  • Post processor preventing spindle speed maximum from being used.
  • Post processor double checking tap feedrates against RPM and pitch.
  • Post processor confirming correct configuration of cutter compensation settings for a specific machine.

The next video of this NX post processor series covers how to identify the underlying variables in NX for enabling warnings. It will cover how to take a specific programming style preference and confirm that it can be checked by the post processor.

NX Post processors have access to a huge breadth of information provided by the NX CAM application, information that can be used to speed up programming and prevent machine crashes. Post processors have to handle and process information provided by NX in order to perform more complex or tailored tasks. But what kind of information does a post processor see? How is any of that information stored and handled?

This video explores the relationships between NX CAM, post processors, and the MOM variables that tie the two together. We demonstrate how information is stored and transferred from NX CAM to a post processor as a specific variable. As an example, we will examine a cutter compensation setting and explore the variables that capture and describe the setting. This cutter compensation setting is an example from a previous video that demonstrates how a post processor can produce custom warnings if desired settings are not used. This video explicitly covers how to find and describe the variable and values that correspond to “desirable settings.”

The next video of this NX post processor series will cover how to transfer custom warning dialogs from post processor to post processor using Post Builder. This third and final installment is reserved for our current NX support customers and will enable a skilled user to propagate custom warning messages onto all Post Builder post processors. In combination with this second video, the user should finally be able to program custom warning messages on all post processors. The first video, Putting Custom Warnings right in your NX Posts, covers potential examples and use-cases for custom warning messages.

NX Post processors are capable of a wide variety of custom behaviors, but tend to be written with very specific machines and setups in mind. What if you wanted to take a custom feature from one post and put it on another post? There are certain tools and features that can be used to easily migrate functionality between post processors built with Post Builder – this video will show you how.

This video will demonstrate how to transfer custom commands between different post processors and will use examples from the previous videos of this post processor series. We will explore how to take a custom warning message from one post processor and transfer it to a different machine’s post. We will also look at how to modify the custom warning itself.

The discussion and demonstration will be limited to behavior governed exclusively by custom commands. Though this sounds like a limitation, a remarkable amount of custom behavior can be handled entirely through Post Builder custom commands. This video will get you up to speed on how to modify and bring your favorite custom command performance to all of your Post Builder posts.

TIPS & TRICKS 01: The first video in this series, Putting Custom Warnings right in your NX Posts, covers potential examples and use-cases for custom warning messages.

TIPS & TRICKS 02: The second video in this series, Selecting MOM Variables for Custom Development, covers how to identify the underlying variables in NX for enabling warnings.