// Docs

Learn a post

If your controller is not in the list — or you want MillPath to write exactly like your current CAM — let it learn the post.

Export options → Check this post → Learn a post from your files…

What to add

• G-code that runs right on your machine, from VCarve, Fusion, Carbide Create or another CAM. Several files are better: one with a tool change, one with holes.
• Your Vectric post (.pp), if you use VCarve or Aspire.

Fusion (.cps) and SheetCAM posts are programs and are not run in MillPath: add a G-code file they wrote instead.

What MillPath learns

Comments, line numbers, decimals, the file extension, the tool change (T1 M6, M6 T1 or a pause), tool lengths (G43), the dwell unit (seconds or milliseconds), arcs, drilling cycles, coolant words, and the start and end lines.

It uses only what your files show: no drilling cycles in your files means holes are written as moves. What the files cannot show is listed, and taken from the closest built-in post. Moves to machine coordinates (G28, G53) are not copied. Files that disagree — one waits in seconds, another in milliseconds — are flagged.

Save the post, then run the controller check with it before the first real job.