NX CAM Postprocessor: The Short Version
An NX CAM postprocessor turns a toolpath into the codes your control will run. inteliScience treats the post as the CAM product, not Generate. NX for Manufacturing 2606 (June 2026) loads Post Hub machine kits, ships a Post Builder to Post Configurator convert tool, and lets TCL snippets in CAM Notes drive NC output. Conversion is not a buy-off on the machine.
| Layer | What it is | Who owns it |
|---|---|---|
| Toolpath | Operations, MCS, tools | Programmer |
| Post | Events, cycles, addresses | Methods + the control |
| Kit | Kinematics + CSE + post | Machine + NX |
The Problem: Pretty Paths, Generic Fanuc
If you picked GENERIC and the machine moved, you got lucky. Heidenhain cycles, Fanuc macros, Sinumerik CYCLE832, probe and tool-setter blocks: none of that lives in Face Milling. It lives in the post.
This is not a tutorial on operations. Face mill, MCS, and Make Machining Suggestion are the programmer’s side of the job. Here the question is: which file talks to the control, and who is allowed to change it.
Designcenter Student Edition can generate and verify toolpaths. Siemens’ student terms say CAM data is not available for post-processing. Treat school paths as throwaway.
Post Builder vs Post Configurator: what actually differs
Both write TCL underneath. The structure is not the same.
Post Builder is the older tool: one post, one set of files, every event handler edited in place. Siemens has kept it in maintenance since NX 1980, so it gets critical fixes and no new features. Every house post older than a few years is a Post Builder post.
Post Configurator is the current tool. It is layered: a Siemens-maintained base for the control family, a machine layer, and your customization on top. Enhancements only arrive here. Updating a Configurator post on the next release means re-applying your layer, not diffing a monolithic TCL file.
Post Hub is the library of ready-made machine kits (kinematics, simulation, post) that you pull into the NX palette. If a kit exists for your control and head, start there.
The convert tool takes a Post Builder post into Post Configurator. Siemens’ wording is that it preserves existing customizations. The Community threads on failed conversions are where the real list of edge cases lives.
2606: more automation in the post, not a free lunch
NX for Manufacturing 2606 shipped on 19 June 2026. Three items on the release list concern the post directly:
- Tool-setting and probing cycles from Blum-Novotest and Renishaw are built in, for laser and contact probes: initial length and diameter measurement, wear compensation, breakage checks between operations. The output rides the postprocessor layers and is reachable through Post Hub. Siemens lists Fanuc, Sinumerik, Heidenhain, Mazak, Okuma, Makino, Brother, Fagor, and Mitsubishi.
- TCL logic in CAM Notes can now drive adaptive NC output through the postprocessor layer: calculations and conditionals at post time.
- Make Machining Suggestion got a history-free generative option. That is toolpath, not post. Do not mix it into this article.
Read “preserving customizations” as a Siemens claim. Your Heidenhain pocket cycle, your 5-axis TCP call, your OEM tool-change subprogram: prove them with a buy-off program on the machine.
TCL in CAM Notes is power and an audit problem at the same time. Who may put logic in a note that ships G-code? If the answer is “anyone with a CAM seat,” you have just moved post authoring into the operation dialog.
We advise against running the converter on Friday and cutting metal on Monday without a signed checklist.
# After Manufacturing is open: confirm a CAM setup exists (NXOpen, NX 2606).
import NXOpen
session = NXOpen.Session.GetSession()
work = session.Parts.Work
cam = work.CAMSetup
print("CAM setup:", cam is not None)None means you never entered Manufacturing. You cannot post a CAD part.
A shop post in practice
- Name the control and the NC format (mm/inch, absolute/incremental, which work offset).
- Get a kit from Post Hub if one exists for that machine. Load it. Do not start from a blank Fanuc and “make it like the old Heidenhain.”
- If you are still on Post Builder, plan the conversion as a project: convert, diff the NC against the old post, cut air.
- Map tool numbers, adjust, cutcom to the magazine you actually have.
- One probe cycle or one rigid tap through the post. That is the first real test, not a 200-operation demo.
- Lock who edits the post. Version it with the NX release.
Simultaneous 5-axis needs TCP or polar output that matches the head or table. That is a kinematics question the kit has to answer before the post can. Mill-turn channels are another article again.
This runs as a POC. What’s missing for production: A kit that is your kinematics, cycles the OEM actually documented, a buy-off on the machine, and a rule for who edits the post after 2606. Siemens NX consulting is that work, including NXOpen gates around it.
The buy-off checklist
Before a converted or new post touches production:
- Program start and end. Safe-start block, work offset, coolant and spindle states, program end and rewind exactly as the control manual says.
- Tool change. Tool number, length offset, pre-select of the next tool, the OEM subprogram if there is one.
- One of each cycle you use. Drill, tap, bore, one probe cycle, one tool-setter call. Compare the NC line by line with a known-good program.
- Cutter compensation and adjust. On, off, the plane, the register.
- Rotary output. Angles, direction, clamp and unclamp, TCP on and off, for every rotary axis the kit claims.
- Air cut, then a soft material. Only then the first real part.
- Sign it. Post version, NX release, kit version, date, who tested. Store it next to the post.
What we recommend
Use Post Hub when the kit is close. Convert Builder posts instead of rewriting them from memory. Then treat every customization as code: review, test, sign.
Our clear recommendation: one post per machine configuration, not one “almost” post for the hall. Templates plus posts beat a weekend of Generate.
Do not buy a course that posts to GENERIC and calls it done. Designcenter Copilot and CAM chat will find the Post dialog. They will not author your CYCLE.
Frequently Asked Questions
What is an NX CAM postprocessor?
The layer that turns NX operations into NC for a named control: addresses, cycles, tool change, start/end of program. Without it you have a viewer.
Post Builder vs Post Configurator?
Builder is the older authoring tool, in maintenance since NX 1980. Configurator is the current, layered one and the only one that receives new features. Siemens ships a convert tool. The buy-off stays on the shop floor either way.
How much does an NX CAM postprocessor cost?
A Post Hub kit can be “already there” and still need days of events. A stubborn mill-turn or a house cycle is a project, often more than the CAM seat. Siemens quotes the license. We quote the remaining events.
Can I post from NX Student Edition?
Generate and verify, yes. Siemens says student CAM data is not available for post-processing. Do not promise a shop post from a student seat.
NX CAM postprocessor vs machine simulation?
The post writes the file. ISV/CSE simulation reads kinematics and, if you set it up, that file. A green Verify window is not a post.
Next Step
Want NC that matches your control, not GENERIC? Book a free 60-minute strategy call. Book a strategy call about the NX CAM postprocessor