Official Autodesk Development Partner

Controller-Specific Fusion Post Processors

Every CNC control reads code differently. We build Fusion posts that match your control's syntax, cycles, high-speed and 5-axis functions, program structure and file format, for FANUC, Siemens, Heidenhain, Haas, Mitsubishi, Mazak, Okuma, Fagor and many more.

Same toolpath, different languages

A FANUC control uses G43 for tool length and G05.1 for high-speed machining. Siemens uses D numbers and CYCLE832. Heidenhain uses conversational TOOL CALL, CYCL DEF and PLANE functions. Okuma selects offsets with G15 H. Each control also has its own drilling cycles, tilted plane commands, subprogram style, comment format and file naming. A generic post only covers the basics.

ENGIMANDI builds Fusion posts matched to your control model, software version and installed options. We use the control's native functions for high-speed machining, tilted planes, tool centre point and cycles, so programs run as the control's designers intended. If you run several control brands, we keep a consistent structure across all your posts so programmers get the same behaviour everywhere.

Read custom G-code for different CNC controllers and migrating a post processor between controllers.

What you get

  • Native control syntax
  • Control-specific cycles
  • High-speed functions
  • Tilted plane commands
  • TCP / RTCP functions
  • Program & file structure
  • Version & option matched
  • Consistent across brands
Also supported

More controls

If it reads G-code, we can post for it.

Brother CNC-C00DMG MORI CELOSHurco WinMax (NC)Doosan / DN SolutionsHyundai WIASyntecLNCKND & GSKMach3 / Mach4LinuxCNCCentroid
Use cases

Typical projects

  • Post for a new control on an existing machine
  • Using native cycles instead of long-hand code
  • High-speed functions set per operation
  • Retrofit from FANUC to Siemens
  • Consistent posts across a mixed shop floor
  • Post for a lesser-known Asian control
Our process

How we match your control

Identify

Control, version and options.

Study

Manuals and proven programs.

Build

Native syntax and functions.

Prove

Trials on the machine.

Support

Updates with control changes.

FAQ

Controller-specific questions

Why not use a generic FANUC post everywhere?

Many controls accept FANUC-style code, but differ in cycles, high-speed and 5-axis functions. A controller-specific post uses what your control actually supports.

Does the control software version matter?

Yes. Newer versions add functions and change some syntax, so we match your version.

What about the machine itself?

For builder codes and options, see machine-specific posts.

Can you support a control you have not used?

Yes, working from the control manual and proven programs from your machine.

Do you move posts between controls?

Yes, see post migration and upgrade.