Custom G-Code Output from Fusion
Make Fusion's G-code look and behave exactly the way your shop wants: program structure, headers, safe start blocks, modal codes, arcs, number formats, macros and special G-codes, all matched to your standard and your control.
Your G-code, your standard
Most shops have a standard for how programs should look: a header with part number, revision and setup notes, a safe start line, specific modal codes at each tool change, arcs as I/J/K or R, a certain number of decimal places, and special G-codes for features their control supports. When Fusion's output does not match, operators edit every program by hand, and mistakes creep in.
ENGIMANDI customises Fusion posts to produce G-code to your standard. We shape program start and end blocks, headers and comments, modal code output, arc and helical formats, feed and speed formatting, safe start and restart blocks, and special G-codes such as high-speed modes, smoothing, tilted planes and probing. We compare output against a reference program you approve.
Read custom G-code for different CNC controllers and why CAM posts produce incorrect G-code.
What you get
- Program header & comments
- Safe start blocks
- Modal code control
- Arc & helix format
- Number formats & decimals
- Special G-codes
- Restart-friendly blocks
- Matched to a reference program
G-code we customise
Every line of the program.
Program Structure
Start, end, sequence numbers and program number format.
Safe Start
G17/G40/G49/G80/G90-style safety lines at start and each tool.
Arcs & Helix
I/J/K or R, plane selection and arc splitting rules.
High-Speed Codes
Smoothing and look-ahead codes set per operation.
Macros & Variables
Macro calls, variables and custom subprograms.
Restart Blocks
Full modal state at each tool so operators can restart safely.
G-code customisation stack
Post engine tools.
Typical projects
- Shop-standard header with setup sheet data
- Safe restart at every tool change
- Arcs as R for an older control
- High-speed mode per operation type
- Macro calls for in-process checks
- Removing unnecessary output lines
How we customise G-code
Reference
Your ideal program.
Compare
Current output vs reference.
Customise
Post changes and options.
Test
Output diff and machine run.
Handover
Notes and options guide.
Custom G-code questions
Can the post add our part number and revision?
Yes, from Fusion document, setup or program properties.
Can we switch features on and off?
Yes, as post properties programmers set at post time.
What about M-codes?
See custom M-code output.
Will output still work on our control?
Yes. We check every change against your control's supported codes.
Is this customisation or modification?
Mostly customisation of output. Logic changes fall under modification.