NC Dialects

How a controller program becomes motion. A machine's NC is not one language but a family of dialects that disagree about almost everything except the axis letters, so HiNC parses a program against the brand it was written for and reports what it could not honour rather than guessing.

Ordered from the engine that reads every dialect to the two reader-facing pages that say what each brand's vocabulary actually does.

• NC Parsing Engine — The interpreter pipeline, the brand-by-brand support matrix, and how a machine's own vocabulary is added without changing HiNC
• ISO / General NC — What Fanuc, Syntec, Mazak and Siemens SINUMERIK code HiNC honours, recognises without acting on, or refuses
• Heidenhain — Klartext and Heidenhain DIN/ISO: the block format, Q parameters, tilted planes and the cycles that are read

See Also

• NC Optimization — what rewrites the program this engine reads
• Setup — the setup tasks these dialects are configured from
• Program Zero Alignment — the setup task that decides which work offset the code in these pages resolves against
• Controller — picking the brand a project reads its programs with, and the tables that brand grows