G-code & post-processors

Export is the last step: toolpaths become G-code through a post-processor that speaks your controller’s dialect.

Supported controllers

ChantoCNC ships posts for GRBL, LinuxCNC, Mach3, Marlin, and Masso. Posts are configuration, not code — headers, footers, and dialect quirks live in editable post definitions, so covering another controller is usually a small tweak away. If yours isn’t listed, email us.

Where the numbers come from

G-code is measured from the setup:

• Origin corner — the stock corner you’ll zero X and Y on. The export measures from that physical corner regardless of which way the canvas showed the job.
• Z zero — stock top or machine bed, matching how you touch off.

Zero the machine the way the setup says, and the cut lands where the canvas showed it.

Files and tool changes

Export an operation at a time, or a whole job. Multi-bit jobs can emit tool-change commands for controllers that handle them, or split the program into one file per bit so you can re-zero between tools — the practical choice on most hobby-class machines.

Feeds, speeds, headers

Feeds and speeds come from the bit definitions used by each operation; the post writes them into the program along with a header identifying the job, operation, and bit — so the file on your controller’s screen tells you what it is six months from now.