Siemens 828d Post Processor For Mastercam May 2026

To understand the value, consider two common user profiles:

The Job Shop (5-axis mill): "We used a generic Fanuc post modified for Siemens. Every program needed an hour of hand-editing for CYCLE800. Now with a dedicated Mastercam post, we click 'Post' and go straight to the machine. Our setup time dropped by 70%."

The Production Turning Center: "The 828D on our lathe wants ShopTurn cycles. Our old post output long G-code. The new post outputs CYCLE95 for stock removal and CYCLE93 for grooves. The machine runs smoother, and the control screen shows graphical previews of each cycle. It’s a game-changer for our operators."

The crown jewel of the 828D is CYCLE800 for swivel head or rotary table machining. A generic post will output multiple G17/G18/G19 planes and lengthy coordinates. A dedicated 828D post outputs a single CYCLE800() line with the swivel angle, allowing the control to handle the kinematic transformation internally. This reduces program size by 90% and eliminates calculation errors.

The turning center was meant for complex contours. In Mastercam, I used "Turning" cycles to rough out a shape. Siemens has a powerful command called CYCLE 95 (Turning Cycle), but it demands data in a very specific order. siemens 828d post processor for mastercam

The standard Mastercam post wanted to output line-by-line G1 moves (point-to-point machining). While this works, it creates massive files and ignores the Siemens controller's ability to optimize feed rates on the fly. I wanted to use the controller's native cycles.

This required modifying the "Custom Cycles" section of the post. I had to map the Mastercam parameters—stock remaining, cutting depth, retract distance—into the Siemens format.

I remember staring at the logic: CYCLE95( "Contour_Name", DP, DPP, ...)

Mastercam didn't naturally name contours. I had to write a script in the post processor that would define the contour sub-routine before the cycle call. After three hours of debugging bracket errors and misplaced commas, the controller finally accepted the cycle. The machine roared to life, cutting steel in a smooth, rhythmic motion that looked just like the simulation. To understand the value, consider two common user

Companies like In-House Solutions, Postability, or independent MP gurus can build a custom post. Expect to pay $2,000–$5,000 USD, but you will get:

Using a hacked or generic post for the 828D often leads to:

Unlike Fanuc’s more basic macro structure, the Siemens 828D operates on a Sinumerik Operate interface, which supports advanced cycles (CYCLE83, CYCLE800), high-level language features, and axis substitution. A generic Fanuc-style post will fail on an 828D for several key reasons:

A properly built Mastercam post processes these nuances automatically, saving operators from manual editing. Unlike Fanuc’s more basic macro structure, the Siemens

Just when I thought I was winning, the machine crashed. Not a physical crash, but a logical one.

I was running a drilling cycle. Mastercam outputted a standard G81 drilling cycle. However, the Siemens 828D modal logic is strict. If a previous G-code grouping was left active, the drill cycle wouldn't execute correctly.

The drill was retracting too slowly. The issue was the G98/G99 modal states (Retract to Initial Point vs. Retract to R-point). Mastercam assumed one default; the Siemens controller assumed another. The drill nearly bottomed out because the R-plane logic was inverted.

I went back into the post processor’s pwdrill section. I added a force-feed of the G-group before every drilling cycle.

G0 G90 G94 ; Force absolute positioning and feed-per-minute
G17 ; Force XY plane (even for lathes, the logic must be clean)

This was the turning point. The post stopped being a generic file and started becoming a "Siemens Citizen."