Official Autodesk Development Partner

Fusion Heidenhain Post Processor for TNC Controls

Heidenhain TNC controls use their own Klartext (plain language) programming. We build Fusion posts that output clean Klartext or ISO for TNC 640, TNC 620, TNC 530 and TNC7, using Heidenhain cycles, PLANE functions, TCPM and tolerance settings.

Klartext that Heidenhain operators recognise

Heidenhain programs look nothing like ISO G-code. Moves are written as L and CC/C blocks, tools are called with TOOL CALL, drilling and tapping use numbered cycles such as CYCL DEF 200, 203 and 207 with Q parameters, tilted planes use PLANE SPATIAL or PLANE VECTOR, and tool centre point uses M128 or FUNCTION TCPM. Operators on Heidenhain machines expect this style, and they edit programs at the control.

ENGIMANDI builds Fusion Heidenhain posts that produce well-structured Klartext, or ISO if your shop prefers it. We output native Heidenhain cycles with correct Q parameters, PLANE functions with the right positioning behaviour (MOVE, TURN or STAY), M128/FUNCTION TCPM for simultaneous machining, Cycle 32 tolerance per operation and readable block numbering and comments.

Read Heidenhain post processor development.

What you get

  • Klartext or ISO output
  • TNC 640, 620, 530 & TNC7
  • Heidenhain drilling & tapping cycles
  • PLANE SPATIAL & PLANE VECTOR
  • M128 / FUNCTION TCPM
  • Cycle 32 tolerance
  • TOOL CALL conventions
  • Operator-friendly structure
Capabilities

Heidenhain post features

Native TNC programming from Fusion.

Klartext

L, C and CC blocks with Heidenhain formatting and block numbers.

Cycles

CYCL DEF 200, 203, 205, 207, 209 and thread milling cycles with Q parameters.

PLANE Functions

PLANE SPATIAL, VECTOR and RESET with MOVE, TURN or STAY.

TCPM

M128 or FUNCTION TCPM for simultaneous 5-axis machining.

Cycle 32

Path tolerance set per operation for speed and accuracy.

TOOL CALL

Tool calls with axis, speed and delta values in Heidenhain style.

Controls

Heidenhain controls we post for

Milling and mill-turn.

TNC7TNC 640TNC 620iTNC 530TNC 320TNC 128Klartext (.h)ISO (.i)
Use cases

Typical projects

  • Hermle C-series post with PLANE SPATIAL
  • DMG MORI DMU with Heidenhain TNC 640
  • iTNC 530 mould machining with Cycle 32
  • Simultaneous 5-axis with FUNCTION TCPM
  • TNC 620 VMC post for a job shop
  • Klartext output replacing ISO for operators
Our process

How we build Heidenhain posts

Identify

Control, software and machine.

Style

Klartext or ISO conventions.

Build

Native Heidenhain output.

Prove

Trials at the machine.

Support

Ongoing help.

FAQ

Heidenhain post questions

Klartext or ISO: which should we use?

Klartext gives full access to Heidenhain features and is easier for TNC operators to edit. ISO can suit shops that standardise on G-code across machines.

Which PLANE function is best?

PLANE SPATIAL is common for 3+2 work. We choose the function and positioning behaviour that match your machine and preferences.

Can Heidenhain cycles replace expanded drilling moves?

Yes. Native cycles make programs shorter and easier to adjust at the control.

Do you support older iTNC 530 controls?

Yes, with their specific cycle and function sets.

Can the post use Q parameters for flexibility?

Yes. Q parameters can be used for values operators need to adjust.