Tool changes are a program’s chapter breaks, and finding the next one is a navigation skill every machinist uses constantly, to jump around a long program, to pick a safe place to restart, to stay oriented during a run. It is also fast and specific once you know the signature, which turns a wall of code into a sequence of clearly marked sections.
A worked glimpse of the shape
A tool-change block in a real program reads like a small stanza: a line carrying T05, an M06 to swap it in, then G43 H05 to pick up tool five’s length, S2400 M03 to start the spindle, G54 confirming the work offset, and a G00 rapid to the first hole. Six or seven lines, the same shape every time, only the numbers changing. Once that stanza is a single recognized object to your eye, scanning a program for tool changes is like flipping through a book for its chapter headings, you are not reading the words, you are spotting the format, and the format is what the search below targets.
The signature to search for
A tool change has a recognizable shape: the T word and M06 mark the boundary (T stages the tool in the magazine, M06 executes the physical exchange), and a short preamble after it re-establishes the new tool’s context. Search for the boundary, then read the preamble.
| Element | What it looks like | What it tells you |
|---|---|---|
| The boundary | T-word with M06 | A tool change happens here |
| Length offset | G43 H-number | Which offset register this tool uses |
| Spindle | S-word with M03/M04 | The new tool is spinning up |
| Context | Work offset, first rapid | Where the new tool starts cutting |
That preamble is the fingerprint: when G43 H, a spindle start, and an approach move cluster together, you are reading the opening of a tool’s section, the same recognizable shape on every Fanuc-shaped control, documented in the standard reference. Use the control’s program search for T or M06 rather than scrolling, search lands exactly on the boundary, scrolling drifts past it.
The three jobs it serves
Navigation. A long program is a sequence of tool sections, and jumping between tool changes is how you move through it, to the roughing tool, the finish tool, the drill. The chapter-break model makes a forty-tool program legible: each change is a heading, each section a chapter.
Restart safety. Tool changes are the gold-standard restart points because they freshly re-establish the tool, the offset, the spindle, and often the work offset within a few lines, which shrinks the state you must reconstruct to almost nothing. Finding the next (or previous) tool change is the first move in any safe mid-program restart, and the reason a skipped tool change contaminates everything downstream, every section after it inherited the wrong tool.
Orientation. Knowing which tool’s section you are in tells you what the surrounding code is doing, a deep plunge in the drill section reads differently from the same move in the finish section. During a run, glancing to the next tool change tells you what is coming.
Reading it like a chapter, not a line
The skill is recognizing the signature as one shape rather than decoding it word by word. The T-and-M06 pair, the G43 H, the spindle start, the approach, become a single recognized pattern once the vocabulary is automatic, so your eye jumps to tool changes the way a reader’s eye finds paragraph breaks. That recognition is recall, drilled free in the 60-second rounds on the G-code practice page, and it compounds with the broader reading-for-errors discipline: fluent readers navigate by tool change, scan each section for its species of error, and never lose their place in a long program. Narrating a few real programs, calling out each tool change aloud as you reach it, turns the recognition into a reflex within a week.
Sources
Frequently asked questions
How do you find the next tool change in a G-code program?
Search forward for the signature: a T word with M06, where T stages the tool and M06 executes the change. Use program search rather than scrolling, then read the few lines after it, the G43 H call, spindle start, work offset, first approach, that re-establish the new tool.
What does a tool change look like in the code?
A T word naming the tool, an M06 to execute it, then a preamble: G43 with an H number, an S word and M03 for the spindle, often the work offset and a rapid to the first position. That preamble cluster is the fingerprint.
Why is finding tool changes useful?
Navigation (they are a program’s chapter breaks), restart safety (the gold-standard re-entry points, since they re-establish tool, offset, and spindle), and orientation (knowing which tool’s section you are in).
What is the fastest way to get good at spotting tool changes?
Recognize the signature on sight through recall practice: the T-and-M06 pair plus the preamble become one recognized shape. The free G-Code Sprint app drills the core, and narrating real programs turns it into a reflex.