What a post can generate besides G-code
- Setup sheets in HTML or PDF with tools, offsets and images.
- Tool lists in CSV or XML for presetters and tool cribs.
- Job data (cycle time, tools, material) for MES or ERP.
- Log files recording who posted what and when.
An automated flow
| Step | Automated by |
|---|---|
| Name program from part number, revision and operation | Post processor |
| Write NC file to the machine's DNC folder | Post processor or script |
| Export tool list to presetter | Post processor |
| Publish setup sheet to shop-floor screen | Post processor + web app |
| Update job status in MES | API call after posting |
Example: tool list export
tool,description,diameter,stickout,holder
1,Endmill 16 rougher,16.0,45,BT40-ER32
4,Drill 8.5 carbide,8.5,60,BT40-HYD12
7,Tap M10x1.5,10.0,55,BT40-TAPZero-edit programs
The foundation of automation is that posted programs run without editing. Only then can they flow directly to machines, presetters and MES without someone opening and changing them.
Keep it controlled
- Send programs only to approved folders; never overwrite running programs.
- Keep NC file revisions linked to CAM file revisions.
- Log every post and transfer for traceability.
A good post processor finishes programming; a great one starts production.
Automate your CAM-to-CNC flow
See our CNC post processor development and CAD-CAM integration services.