Fusion Post Processor Customisation for Your Shop Standards
Start from a proven Autodesk library post and make it yours. We tailor headers, comments, program numbering, safe lines, coolant, properties, file naming and output style so every program matches your shop's standards.
Small changes, big difference on the shop floor
For many machines, the Autodesk library post already handles the core motion correctly. What is missing is the shop's way of doing things: a header with part, material and stock details, a tool list, specific comments, a safe start line, program number rules, particular coolant or air-blast codes, a home position at the end, or file names that match the DNC system.
Customisation is the fastest and most economical route. ENGIMANDI adjusts library posts through post properties and targeted code changes, keeping the post close to Autodesk's structure so future library updates remain easy to merge. We add new user properties so programmers can switch options at post time instead of editing code.
Need deeper logic changes? See post modification. Further reading: post processor customisation in manufacturing.
What you get
- Program header & tool list
- Comment style & operator notes
- Safe start & end lines
- Program number & file naming
- Coolant & air-blast codes
- New post properties
- Home & park positions
- Close to library for updates
Common Fusion post customisations
Quick, low-risk changes with high value.
Headers
Part name, revision, programmer, date, stock, WCS and tool list at the top.
Comments
Operation names, tool descriptions and setup notes in the format operators prefer.
Safety Lines
Safe start blocks, cancel codes and end positions matched to your machine.
Coolant & Options
Flood, mist, through-spindle, air blast and chip conveyor codes mapped.
Post Properties
New switches in the post dialog for options your programmers need.
File Output
File names, extensions, line numbers and program numbers for your DNC.
Customisation tools
Library posts and the Fusion post engine.
Typical projects
- Header with stock size and tool list for setup
- Through-spindle coolant code added for new tools
- File naming matching the DNC folder structure
- Optional stop after each tool as a property
- Machine parks at the front for part unloading
- Library update merged with shop changes
How we customise posts
Collect
Current post, samples and wish list.
Agree
Expected output confirmed.
Change
Targeted edits and new properties.
Compare
Before and after output reviewed.
Deliver
Post and change notes.
Post customisation questions
What is the difference between customisation and modification?
Customisation adjusts output style and options while keeping the post logic. Modification changes how the post behaves, such as new motion, cycle or tool change logic.
Will customisation stop library updates?
No. We keep changes clearly marked and close to the original so updates can be merged.
How fast can small changes be done?
Many customisations are delivered within one to three working days.
Can programmers change options themselves?
Yes. We add post properties so options can be switched in the post dialog without editing code.
Do you need our machine?
No. Sample programs and clear requirements are usually enough, with an operator checking the first run.