Why library posts need customising
- Library posts target a controller family, not your exact machine.
- Machine builder M-codes (clamps, chip conveyor, air blast, through-spindle coolant) differ.
- Tool change positions and safe retract methods vary.
- Your shop has its own header, tool list and restart standards.
Project steps
| Step | Output |
|---|---|
| Machine questionnaire | Controller, options, travels, M-codes, sample programs |
| Select library base post | Closest Autodesk post for the controller |
| Customise | Header, M-codes, retracts, cycles, properties |
| Machine definition | Kinematics and limits in Fusion for simulation |
| Test and simulate | Test set posted and checked |
| Prove on machine | Approved post version |
Example: machine-specific M-codes in a Fusion post
function onSection() {
// ...
if (tool.coolant == COOLANT_THROUGH_TOOL) {
writeBlock(mFormat.format(88)); // through-spindle coolant on this machine
}
if (getProperty("useChipConveyor")) {
writeBlock(mFormat.format(31)); // conveyor on (machine builder code)
}
}Codes like these come from the machine builder's M-code list; they are not universal, which is exactly why customisation is needed.
Fusion machine simulation
With a machine definition, Fusion can simulate the machine, checking axis limits and collisions. We match the machine definition to the post configuration so simulation and output agree.
Machines we commonly configure
VMCs and HMCs, 4-axis rotary tables, trunnion 5-axis machines, head-head 5-axis machines, CNC lathes and mill-turn centres, on controllers such as FANUC, Haas, Siemens, Heidenhain, Mitsubishi and Okuma.
A Fusion post built for your exact machine removes the guesswork from every program.
Get a Fusion post for your machine
See our Fusion 360 customisation and CNC post processor development services, or read the Fusion post system overview.