CHIPBY KINETIC CARVING
CNC · Hobbyist · Information · Platform
Return to Kinetic Carving
Software · Outputintermediate~2 min read

Post processors

Short answer

The post processor writes your toolpaths as G-code in the exact dialect your controller expects. Pick the one that matches your controller, not your machine brand. Symptoms of the wrong post look like machine faults but are not.

What it does

CAM knows the geometry: where the tool goes, how fast, how deep. The post processor knows your machine: what commands it accepts, how it wants a tool change expressed, whether it supports arcs, what it needs at the start and end of a file, and which units.

Same toolpaths, different post, completely different text file.

Symptoms of the wrong post

What happensUsual post cause
Everything is 25.4 times too big or too smallPost outputs the wrong units for the controller
The machine ignores tool changes and keeps cuttingTool change command the controller does not understand
The spindle does not start, or does not stopSpindle commands in a form the controller does not accept
The tool plunges at rapid speedPlunge expressed as a rapid rather than a feed move
Circles come out facetedArc fitting off, so arcs are output as line segments
The controller throws an error on a specific lineA command the controller does not support
The file does not load at allWrong file extension or format for the controller

All of these look like machine problems. They are not. If a machine behaved normally and then started doing one of these after a software change, check the post first.

Choosing the right one

Match the controller, not the brand
Machines from the same manufacturer can ship with different controllers across model years and product lines. Find out what is actually running your machine, and pick the post for that. See controllers and ecosystems.

The order to look:

  1. Your machine manufacturer's own documentation or downloads.
  2. The CAM package's bundled post list, which usually covers common controllers.
  3. Your machine's user community, which often maintains a refined version.

Testing a new post safely

  1. Post a small, simple job.
  2. Open the file in a text editor and read the first twenty lines. Check the units command, the spindle command and the coordinate system.
  3. Load it and run it in the air, well above the material, watching what the machine does.
  4. Then run it in scrap.
  5. Only then use it on real material.

When to edit a post

Rarely, and only with a specific reason: adding a pause at tool changes, changing the spindle warm-up delay, adjusting how the file ends. Post files are plain text and editable, and a broken post produces G-code that can drive your machine into something. Keep a copy of the original before you change anything.