CNC Automatic Tool Change Programming: Writing ATC Routines That Do Not Crash Your Machine

Automatic tool change (ATC) sounds like a simple convenience. The machine swaps tools, the program keeps running, and you walk away. In practice, ATC programming is where more shops lose time than almost any other operation. A badly written tool change can crash the spindle, damage the turret, break a tool, or — worst of all — run without crashing but produce a part that is off by 0.1 mm because the tool length compensation never updated correctly.

The tool change itself takes maybe two seconds. The programming around it takes twenty minutes if you do it right, or two hours if you find out at 3 AM that the tool hit the vise jaw because you forgot to account for the tool holder height.

How ATC Actually Works Inside the Controller

When the program calls a new tool with T and M06, the controller does a sequence of things in a specific order. First, it decelerates the spindle. Then it indexes the turret or carousel to the correct tool position. Then it accelerates the spindle back up. Only after all of that does it apply the new tool length offset.

The problem: most programmers assume the offset is applied instantly. It is not. There is a delay — sometimes 0.5 seconds, sometimes 2 seconds — between the turret lock and the moment the controller actually reads the new H value. If you program a Z move immediately after M06, the controller might still be using the old tool length. The tool drops too far, smashes into the part, and your morning just got worse.

The M06 and T Command Relationship

T selects the tool. M06 executes the change. They are two separate commands and they must appear in the correct order. T first, then M06. If you put M06 before T, the controller does not know which tool to grab, and on some machines it will just index to the last used position — which might be the wrong tool entirely.

The standard sequence is: T[tool number] M06. Some controllers also accept M06 T[tool number] — both work, but be consistent. Pick one format and use it everywhere in the program. Mixing formats in the same program is a good way to get a surprise tool change on a machine that interprets the commands differently.

After M06, you should always call the tool length compensation with G43 H[offset number]. This tells the controller to apply the new tool’s length value to the Z axis. Without G43, the machine does not know how long the new tool is, and every Z move after the change will be wrong by the difference in tool length.

Setting Up Tool Length Offsets: The Part Nobody Wants to Do

Tool length offsets are the foundation of ATC programming. If they are wrong, nothing else matters. The program can be perfect, the tool paths can be flawless, but if H03 is off by 0.05 mm, every operation using tool three will be off by 0.05 mm in Z.

Measuring Tool Lengths Correctly

Do not trust the tool list from the tool crib. Tools wear, shrink, and get re-ground. A tool that measured 75.00 mm last week might be 74.85 mm today after a regrind.

Measure every tool on the machine, every time you load it. Use the tool setter or a probe cycle to measure the Z position of the tool tip relative to a known datum — usually the top of the part or a precision block on the fixture plate.

The measurement should include the tool holder, not just the cutting tool. A 10 mm end mill in a CAT40 holder has a different effective length than the same end mill in an HSK63 holder. Measure the complete assembly. Write the value down. Enter it into the offset table. Do this for every tool in the magazine.

One trick that saves time: measure all tools before you start the program, not during. If you stop the program midway to measure a tool, you lose the machine’s rhythm and you are more likely to make a mistake entering the offset.

Using the Same Datum for Every Tool

All tool length offsets must reference the same Z datum. If tool one is measured from the top of the part and tool two is measured from the vise jaw, the two offsets are not compatible. The controller will apply them correctly individually, but the relative positioning between tools will be wrong.

Pick one datum — usually the top surface of the part or the fixture plate — and measure every tool from that same surface. This way, when the controller switches from tool one to tool two, the Z axis knows exactly where the new tool tip is relative to the old one. No guesswork, no cumulative error.

Programming the Tool Change Move Itself

The tool change is not just T and M06. There is a move before it and a move after it, and both need to be programmed with care.

Where to Position the Tool Before the Change

Before you call M06, the tool needs to be in a safe position. This means: clear of the part, clear of the fixture, and at a height where the turret can rotate without hitting anything.

The standard practice: retract the tool to a safe Z height (usually 50 to 100 mm above the part), then move to a tool change position — a fixed X, Y location that is clear of all clamps and fixtures. Many shops program a dedicated tool change point at X0 Y0 or at a corner of the fixture where there is nothing to hit.

Do not skip this move. If the tool is still over the part when M06 executes, the turret has to rotate around the tool, and on some machines the turret will swing into the vise. The result is a bent turret arm and a stopped machine.

The move to the tool change position should be at rapid speed (G00). Do not feed slowly to the change position. You want the tool out of the way as fast as possible.

What Happens Right After M06

The moment after M06 is the most dangerous moment in the entire program. The turret has locked, the spindle is accelerating, but the controller has not yet applied the new tool length offset if you did not program G43.

The safe sequence after M06:

G43 H[new offset] — apply tool length
G00 Z[safe height] — retract to a known clear position
G01 Z[next cut depth] — approach the part at feed rate

The G00 Z[safe height] after G43 is critical. It gives the controller time to settle on the new offset value before the tool moves toward the part. If you go straight from G43 to G01 Z[cut depth], the controller might still be calculating the offset and the tool will plunge to the wrong depth.

Some programmers add a dwell (G04 P0.5) after G43 to give the controller half a second to lock in the new offset. This is not required on most modern controllers, but it does not hurt. On older controls, it can prevent a crash.

Tool Change Positioning on Multi-Tool Programs

When you have ten or fifteen tools in a program, the tool change position becomes a traffic management problem. Every tool has to go to the same change point, and if the change point is poorly chosen, the rapid moves between the cut area and the change point eat up cycle time.

Minimizing Travel Distance to the Change Point

The tool change position should be as close as possible to the cutting area, but far enough from the fixture to be safe. A good rule: place the change point at the corner of the part’s bounding box, offset by at least 20 mm from any clamp or fixture element.

If the part is 100 mm by 80 mm, put the change point at X120 Y100. The tool travels 20 mm from the edge of the part to the change point — short enough to keep cycle time low, long enough to clear everything.

For programs with many tools, consider using multiple change points. One change point for the roughing tools (large end mills, face mills) and a different one for the finishing tools (small ball end mills, deburring tools). This keeps the travel moves short for each group and avoids having a tiny finishing tool travel all the way across a large part to reach a distant change point.

Grouping Tools by Operation Type

Do not call tools in the order they appear in the tool list. Call them in the order of operations. If the first five operations are all roughing passes with the same 20 mm face mill, do not change tools after each pass. Keep the same tool in the spindle for all five passes, then change to the next tool.

This sounds obvious, but it is amazing how many programs have T1 M06, then two lines of cutting, then T2 M06, then two more lines, then T3 M06. That is four tool changes for a job that could run with two.

Group the operations: all drilling with tool one, all roughing with tool two, all finishing with tool three. The program runs faster, the turret lasts longer, and there are fewer chances for a crash during a tool change.

Common ATC Programming Mistakes That Cause Crashes

Forgetting G43 After M06

This is the number one ATC mistake. The programmer writes T5 M06 and then immediately goes to G01 Z-5.0. The controller changes the tool but does not apply the length offset. The tool drops to Z-5.0 based on the previous tool’s length, which might be 10 mm longer or shorter than tool five. The result: the tool either smashes into the part or stops 10 mm above it and cuts air.

Always, without exception, program G43 H[offset] immediately after M06. Make it a habit. Type it before you type anything else after the tool change.

Not Accounting for Tool Holder Interference

On machines with a close-coupled turret, the tool holder on the next position might be physically close to the current tool. When the turret rotates, the holders can collide. This is called tool holder interference, and it happens more often than people admit.

Check the turret layout in the machine’s manual. Some controllers let you define which tools can be adjacent to each other. If tool one and tool five cannot be next to each other in the turret, the controller will skip over tool five and go to tool six instead. If you did not program for this, the machine will grab the wrong tool.

The fix: know your turret map. Program tool changes in an order that respects the turret’s physical layout. If the manual says tool one and tool three cannot be adjacent, never program T1 M06 followed immediately by T3 M06. Insert a different tool between them.

Ignoring Spindle Orientation on Asymmetric Tools

Some tools have an orientation requirement — a flat on the tool holder that must align with a specific angle on the turret. A tool with a flat will not seat properly if the turret rotates to the wrong angle. The tool drops into the spindle but sits crooked, and the next cut is off by the runout amount.

For tools with orientation flats, use the M19 command (spindle orient) if your controller supports it. M19 rotates the spindle to a specific angle before the tool changes. This ensures the flat always seats in the same position.

If your controller does not support M19, you have to manually account for the angular offset. Measure the angle between the tool’s flat and the cutting edge. Program the tool change so the turret always indexes to the same angular position for that tool. This is tedious but necessary for tools with flats or keyed holders.

Advanced ATC Techniques for High-Volume Work

Using Macro Variables for Dynamic Tool Changes

On controllers that support macro programming, you can write a subprogram that handles the tool change automatically. The main program calls the subprogram with the tool number as a variable, and the subprogram handles the retract, the change, the G43, and the return to cutting height.

This eliminates the chance of forgetting G43 or putting the safe Z in the wrong place. The subprogram is written once, tested thoroughly, and then called from every tool change in the program. If you need to update the tool change logic, you change it in one place instead of hunting through hundreds of lines of code.

Pre-Positioning the Next Tool

Some advanced controllers allow you to pre-position the next tool in the turret while the current tool is still cutting. This is called next-tool preview or advance turret positioning. The controller rotates the turret to the next tool position during the last few seconds of the current cut, so when M06 executes, the tool is already in place.

This shaves 0.5 to 1 second off each tool change. On a program with 20 tool changes, that is 10 to 20 seconds saved per cycle. For high-volume production, that adds up to hours per week.

Not every machine supports this. Check your controller’s documentation. If it is available, enable it and program the look-ahead moves accordingly. The controller will tell you which block to put the next-tool call in — usually the block before the actual M06.