Master CNC G Code: What Every Engineer Should Read Before Cutting Metal

• 1
  What G code actually is, and what it is not
• 2
  Modal states: why one line can change everything after it
• 3
  Work offsets and the difference between machine and part coordinates
• 4
  Cutter compensation, tool length, and the offsets that keep dimensions in tolerance
• 5
  Safety lines, dry runs, and when G code is the wrong tool for the job
• 6
  Common G codes and what they change

G code is a text instruction set standardized under ISO 6983. Each line, called a block, carries one or more words: a letter address plus a number. G01 X25.4 Y0 F200 tells the controller to move in a straight line to that coordinate at 200 mm/min. The controller reads blocks in order and executes each one before reading the next.

It is not a design file. The geometry lives in the CAM output or the drawing. G code only describes motion, feed, speed, tool changes, and machine state. When a part comes out wrong, the cause is often upstream in the CAM strategy or the workholding, not in the G code itself.

Different controllers share the core word set but diverge on the edges. Fanuc, Siemens, Haas, and Mitsubishi controls all accept G00, G01, G02, and G03, but canned cycles, macro syntax, and high-speed look-ahead differ. A program that runs clean on one control may need edits on another.

For an engineer reviewing a program, the useful question is not whether the code is elegant. It is whether the setup is safe, the coordinates match the fixture, and the toolpath matches the drawing. That is where most scrapped parts come from.

Most G codes are modal. Once you call G01, every following block with coordinates stays in G01 until another motion code appears. This is efficient, and it is also the most common source of crashes. A single missing G00 before a rapid move, or a leftover G41 from a previous operation, carries forward into everything below it.

The three motion codes you will see in almost every program are G00 for rapid positioning, G01 for linear feed, and G02 or G03 for clockwise and counterclockwise arcs. G00 moves at the machine's maximum rapid rate and is never used for cutting. G01 moves at the programmed feed rate F. Arcs need I, J, K offsets or an R value, depending on the control.

Modal state also applies to units, plane selection, and feed mode. G20 selects inches, G21 selects millimeters. G17, G18, and G19 set the active plane for arcs and cutter compensation. G94 sets feed per minute, G95 sets feed per revolution. A program that mixes these without resetting them will produce wrong dimensions that look correct on screen.

The practical rule: at the start of every tool, reset the states you depend on. Do not assume the previous tool left the controller in a known condition. A short safety block at the top of each operation costs nothing and prevents most of the errors that reach the spindle.

Machine coordinates are fixed to the machine. Part coordinates are set by the work offset, usually G54 through G59. The controller adds the offset to the programmed coordinate to find the physical position. If the offset is wrong, every dimension shifts by the same amount, and the error is easy to spot because it is uniform.

Setting G54 means touching off the part or fixture and storing that position in the offset table. On a vise setup, the X and Y zero is often the corner of the stock, and Z zero is the top face. On a tombstone or a 5-axis trunnion, the offset may reference a rotary center point instead. The choice changes how the CAM posts the program.

A common failure is a mismatch between the CAM setup and the physical offset. The programmer assumes Z zero is the top of the stock; the operator set it to the top of the vise jaw. The tool plunges into the jaw or cuts air. Both the setup sheet and the program header should state the zero reference explicitly.

For parts held in soft jaws or custom fixtures, record the offset values in the setup documentation. When the job runs again six months later, the second setup is faster and the risk of a wrong zero drops sharply. This is a documentation habit, not a machining skill, and it pays off more often.

Cutter compensation, G41 for left and G42 for right, shifts the toolpath by the tool radius so the programmed path describes the finished part edge, not the tool center. The controller reads the radius from the offset table. If the operator updates the radius after a wear measurement, the part dimension changes without editing the program.

This is why cutter comp matters for tolerance control. On a feature held to ±0.005 mm, the operator can adjust the offset in small increments and re-cut. Editing the program coordinates instead would be slower and riskier. Most production shops run comp on all profile cuts for exactly this reason.

Tool length offsets work the same way. Each tool has a stored length; the controller applies it when the tool is called. A wrong length offset means the tool either crashes into the part or cuts air above it. After a tool change or a new insert, the length should be re-measured or verified with a touch-off.

G43 applies the length offset, usually with an H number that matches the tool. G49 cancels it. A safe block before any cutting move is G43 H01 Z50.0, which applies the offset and positions Z at a safe height. Skipping the safe height is one of the few errors that damages both the part and the machine.

A safe start line resets the states that matter: G21 for millimeters, G17 for the XY plane, G90 for absolute positioning, G94 for feed per minute, and G40 to cancel any active cutter compensation. It also cancels any active canned cycle with G80. This block is not optional on a machine that runs more than one programmer's work.

A dry run with the tool retracted, or a single-block run at reduced feed, catches most collisions before they happen. On a new program, run the first tool with rapid override down and watch the distance-to-go display. If the remaining travel looks wrong, stop. The display tells you more than the screen preview does.

G code is a poor fit when the geometry is complex and the batch is small. A 5-axis contoured surface with hundreds of small moves is better posted from CAM with look-ahead enabled. Hand-editing that path risks gouges that are hard to see in simulation. Use the code as a review artifact, not a writing exercise.

It is also the wrong tool for a one-off hole pattern that a manual mill can drill in ten minutes. Programming, setup, and proving a CNC program has a fixed cost. Below a certain part count or complexity, that cost does not pay back. Knowing when to stop is part of the skill.