The power of editing your own post is that you eliminate manual G-code editing. No more sitting at the control typing in G10 L2 P1... because the post forgot it. No more "find and replace" for coolant commands.
Find the fs2 (Format Statement 2) definitions.
Change 0.4 0.3 to 0.3 0.3 for three decimal places. The Problem: You have 100 fixtures. Mastercam gives you G54, G55, G56. You need G54.1 P1. The Fix: This is intermediate-level logic. You need to edit the pwcs block. mastercam post processor editing
The best post processor is invisible. You generate the code, press cycle start, and walk away. If you have to touch the G-code, you need to edit your post.
If you want to keep them but control the start number, find seqno$ and seqinc$ . The Problem: Mastercam outputs M8 for mist, but your machine uses M7 for mist. The Fix: Locate the pcool$ post block. It looks something like this: The power of editing your own post is
Start small. Back up your files. Change the coolant command. Test it on a piece of foam. Then move on to work offsets. Eventually, you will realize that the post processor is not a "black box," but a powerful, programmable tool that customizes Mastercam to fit your machines perfectly.
Look for:
A Mastercam Post Processor is a text-based file that acts as a middleman. It takes the file—which contains the generic motion data (X, Y, Z, I, J, K) and operation flags—and reformats it into machine-specific G-code.