Fusion Canned Cycle Post Processor Customisation
Drilling, peck drilling, chip breaking, rigid tapping, boring, thread milling and probing, output as your control's native cycles with correct parameters, instead of long expanded moves. Where a cycle is not supported, we expand it safely.
Native cycles are shorter, safer and editable
Fusion's hole-making operations can be output either as canned cycles or as expanded linear moves. Native cycles give short, readable programs that operators can adjust at the machine, such as changing peck depth or dwell. But each control has its own cycle codes and parameters: G81 to G89 and G73 on FANUC-style controls, CYCLE81 to CYCLE86 on Siemens, CYCL DEF 200 series on Heidenhain, and different tapping and boring formats everywhere.
ENGIMANDI customises how your Fusion post outputs cycles. We map each Fusion cycle type to your control's native cycle, set parameters such as retract plane, peck depth, dwell, feed per revolution and orientation for back boring, enable rigid tapping codes for your machine, add thread milling and probing cycles, and fall back to safe expanded moves when the control lacks a cycle.
Read canned cycle handling in post processors.
What you get
- Native drilling cycles
- Peck & chip-break cycles
- Rigid tapping
- Boring & back boring
- Thread milling
- Probing cycles
- Correct parameter mapping
- Safe expanded fallback
Cycles we customise
Every hole-making operation.
Drilling
Spot, drill, dwell and deep peck with retract rules.
Tapping
Rigid and floating tapping, left and right hand.
Boring
Fine boring, back boring and spindle orientation.
Thread Milling
Helical thread milling output with correct arcs.
Probing
Probe cycles mapped to Renishaw, Blum or control cycles.
Lathe Cycles
Axial and radial drilling and tapping on lathes and live tools.
Cycle formats we support
Native cycles for each control.
Typical projects
- Rigid tapping instead of floating holders
- Heidenhain cycles instead of expanded moves
- Back boring with spindle orientation
- Probing cycles for in-process checks
- Chip-break drilling for deep holes
- Live tool tapping on a lathe
How we customise cycles
Review
Control cycles and options.
Map
Fusion cycles to native codes.
Build
Parameters and fallbacks.
Test
Trial holes on the machine.
Document
Cycle map for programmers.
Canned cycle questions
Why use cycles instead of expanded code?
Cycles are shorter and editable at the machine. Expanded code is useful when the control lacks a cycle or when you need full control of each move.
Can we choose per operation?
Yes. We can add a property to force expanded output when needed.
Do you support probing?
Yes, mapping Fusion probing operations to your probe and control cycles.
What about tilted plane drilling?
Cycles work in tilted planes when the post and control handle the plane correctly; we test this on your machine.
Does rigid tapping need machine options?
Often yes. We check your options and use the correct codes.