Most machinists learn G-code.
Few understand how the CNC controller actually thinks.

CNC machines do not execute isolated commands. They operate as state-driven control systems. Every movement is the result of layered logic: modal memory, coordinate transformations, compensation stacks, feed mode states, and safety interlocks.

Understanding the CNC Operating System is the difference between running programs and controlling machines.

────────────────────────────────────────
SECTION 1 — CNC MACHINES RUN STATES, NOT LINES
────────────────────────────────────────

A CNC controller is a state machine.

Each block of code modifies machine state.

Example:

G90
G17
G54
G43 H12

After these lines execute, the machine is no longer “neutral.” It now holds:

• Absolute positioning
• XY plane active
• Work offset G54
• Tool length compensation applied

The next motion command uses this stored state.

Most crashes occur because programmers forget the machine remembers previous states.

────────────────────────────────────────
SECTION 2 — EXECUTION ORDER: WHAT REALLY HAPPENS INSIDE
────────────────────────────────────────

When a block is read, the controller processes commands in a defined internal order:

1. Mode changes (G90/G91)
2. Plane selection
3. Compensation activation
4. Coordinate transformation
5. Motion execution

Example block:

G01 G41 X50. F400

The controller:

• Confirms motion mode
• Applies cutter compensation
• Calculates adjusted path
• Executes feed move

If compensation is active before safe entry, lateral jump occurs instantly.

Controllers do not “interpret like humans.”
They compute geometry first, then move.

────────────────────────────────────────
SECTION 3 — MODAL MEMORY STACK
────────────────────────────────────────

Modal groups prevent conflicting commands but remain active until changed.

Active groups typically include:

• Motion (G00/G01/G02/G03)
• Plane (G17/G18/G19)
• Positioning (G90/G91)
• Feed mode (G94/G95)
• Compensation (G40/G41/G42)
• Canned cycles (G80/G81/G83)
• Work offsets (G54–G59)

The controller maintains these in memory simultaneously.

Unexpected motion happens when one forgotten state remains active.

Example:

G91 left active → new program assumes G90 → rapid collision.

The machine did not fail.
The operator misunderstood the stored state.

────────────────────────────────────────
SECTION 4 — OFFSET LAYERS (THE INVISIBLE STACK)
────────────────────────────────────────

CNC positioning is not single-layer.

Actual position =

Machine Zero

• Work Offset
• Tool Length Offset
• Cutter Radius Offset
• Local Shift (G52)
• Rotation (G68)

Each layer modifies final motion.

Example:

Wrong G54 + active G52 = double shift.

Result: correct geometry, wrong location.

Controllers compute the entire transformation stack before movement.

────────────────────────────────────────
SECTION 5 — FEED MODE AND SPINDLE RELATIONSHIP
────────────────────────────────────────

Feed mode changes motion behavior completely.

G94 → Feed per minute
G95 → Feed per revolution

If G95 remains active and spindle speed changes:

Feedrate changes instantly.

Tool overload occurs without warning.

Controllers do exactly what mode defines — not what programmer assumes.

────────────────────────────────────────
SECTION 6 — LOOK-AHEAD AND TRAJECTORY PLANNING
────────────────────────────────────────

Modern controllers read multiple blocks ahead.

They:

• Smooth acceleration
• Adjust jerk limits
• Blend corners

High-speed machining depends on internal look-ahead buffers.

If short blocks exist, machine may decelerate unexpectedly.

This explains surface finish variation not visible in code alone.

────────────────────────────────────────
SECTION 7 — MACRO VARIABLES: CONTROLLER INTELLIGENCE
────────────────────────────────────────

Macro variables allow controller self-awareness.

Example:

4120 → active tool

4003 → positioning mode

5023 → Z machine position

Example safety logic:

IF[#4003 NE 90] THEN #3000=1 (SET ABSOLUTE MODE)

The controller stops itself.

At this point, the machine becomes partially autonomous.

────────────────────────────────────────
SECTION 8 — ALARM LOGIC AND INTERLOCK SYSTEMS
────────────────────────────────────────

Alarms are not random.

They trigger when:

• axis limit exceeded
• compensation invalid
• servo load exceeds threshold
• illegal modal combination occurs

Controllers monitor motion continuously.

Overtravel alarm example:

Axis position > software limit
→ immediate stop
→ servo disable

The controller protects hardware through internal checks.

────────────────────────────────────────
SECTION 9 — RESTART FAILURE: STATE DESYNCHRONIZATION
────────────────────────────────────────

Mid-program restart skips previous state changes.

If G43, G54, or G90 were activated earlier:

Restart may use wrong assumptions.

Professional rebuild:

G90 G17 G40 G49 G80
G94
G54

This reinitializes machine logic.

Safe restart equals state reconstruction.

────────────────────────────────────────
SECTION 10 — THERMAL AND MECHANICAL REALITY
────────────────────────────────────────

Controllers assume rigid structure.

Reality:

• spindles expand
• ballscrews heat
• columns drift

Compensation systems attempt correction, but state logic does not include physics unless measured.

Probe feedback loops help reduce drift.

Machines think digitally; physics behaves analog.

────────────────────────────────────────
SECTION 11 — WHY SIMULATION DIFFERS FROM REALITY
────────────────────────────────────────

CAM simulation shows geometry.

It does not simulate:

• servo acceleration
• modal inheritance
• probe contamination
• offset stacking

Simulation verifies path.

Controller executes state.

These are not identical processes.

────────────────────────────────────────
SECTION 12 — HOW PROFESSIONAL SHOPS CONTROL THE SYSTEM
────────────────────────────────────────

Elite shops enforce:

• mandatory modal rebuild blocks
• machine coordinate retract for tool change
• probe verification cycles
• restart protocol checklists
• macro verification alarms

They do not trust memory.

They control state intentionally.

────────────────────────────────────────
FINAL UNDERSTANDING
────────────────────────────────────────

CNC machines do not “run programs.”

They execute a continuously evolving control state defined by modal memory, offsets, compensation layers, feed modes, and transformation stacks.

Most machinists learn commands.

Master machinists learn controller behavior.

Understanding the CNC Operating System transforms unpredictable machines into controlled production systems.