Mazatrol Restart, Single Process, and Reform: Resuming a Program Without Scrapping the Part

The insert gives up halfway through a finish pass, or the power blips, or somebody hits feed hold and then reset out of habit — and now there's a half-machined part in the chuck and a program that starts at the beginning. On a Mazatrol lathe you almost never have to start over, and you almost never have to scrap the part. The control gives you three different tools for this, and half the trouble I see comes from using the wrong one, or using the right one without checking the state of the machine first.

I spent 19 years at Mazak Corporation as an Applications Engineer and have done the same work independently since. Restarting programs safely is one of those skills that separates people who run Mazatrol from people who were shown Mazatrol.

The three functions are not the same thing

Restart resumes a Mazatrol program from a chosen point — typically the start of a unit — rather than from the top. The control re-establishes its position in the program and continues machining from there. This is the tool for "the cycle stopped in the middle; pick it up where it left off."

Single process runs just one unit or process of the program — one operation — by itself. This is the tool for proving out a single operation, re-running one feature, or machining one step of a multi-step part without executing the whole program around it.

Reform is the thread specialist. Thread reform (refinish) re-synchronizes the threading pass with an existing thread — used when you have to re-cut, deepen, or clean up a thread that's already partly or fully formed, so the tool follows the existing helix instead of cutting a second one beside it. Without reform-style synchronization, re-running a threading unit on an existing thread is how you get a double thread and a scrapped part.

The generations present these differently — the T-Plus and T-32 era handles restart through its TPS (Tool Path Store) style functions and menu paths that differ from Matrix and Smooth — so the button sequence from a forum post for a different control will not map one-to-one onto yours. The concepts, and the cautions below, carry across all of them.

When each one is right

Broken insert mid-cycle: Stop, change the insert (same geometry — see the caution below), back the tool clear, and restart from the beginning of the unit that was cutting, or the unit before it if the tool left a witness you need to blend over. Restarting from the start of a unit matters: the control's approach moves and in-cycle state are built around unit boundaries.

Proving out one operation on a new program: Single process. Run the new grooving unit alone, check the result, then run the program whole. This is also the honest way to re-run one feature that measured out of tolerance while the rest of the part is good — adjust the offset, single-process that unit, re-measure.

Thread repair and re-cutting: Reform. A shaft comes back with a damaged thread, or a thread needs to go a few thousandths deeper to hit a gage. Reform lets the threading tool pick up the existing helix. It is also the answer to "the thread cycle got interrupted halfway" — reform re-syncs rather than assuming the part is still in original stock condition.

A partway feature that isn't a thread: Restart from that unit, after verifying the part hasn't moved and the stock state matches what the unit expects. If material the unit planned to rough is already gone, an aggressive restart can air-cut harmlessly or dig in where a previous pass changed the profile — which is why the next section exists.

The cautions that keep a restart from becoming a crash

• The tool in the turret must be the tool the program expects at that point. If you changed the insert, it must be the same geometry and the tool description data must still describe reality. Restart logic assumes the tooling state the program was built on.
• Offsets and WPC are program state too. If anyone touched offsets, the work offset, or tool data while the machine was stopped — and somebody always wants to — the restart inherits those changes. Know what state you're restarting into.
• Never restart into the middle of a cut blind. Restart to a unit boundary, approach in single block with reduced rapid and feed override in hand, and watch the first moves. The control resumes confidently whether or not its assumptions are true.
• A moved part invalidates everything. If the part slipped in the chuck, was unclamped, or the machine lost absolute position while stopped (a battery or position event — see the parameter backup and battery guide), do not restart. Re-establish the setup, then decide.
• Threading restarts are reform restarts. Treat any return to an existing thread as a reform job, full stop.

Done right, these functions are the difference between a five-minute recovery and a scrapped part plus a re-run from bar stock. They are also, not coincidentally, one of the topics where training time pays for itself fastest — an operator who restarts confidently saves a part a month.

When something on a Mazak lathe isn't working

I do this for a living. If you have operators who start programs over from the top because nobody taught them restart, or threads getting scrapped on re-cuts, send me the part, the machine, and the control version. I'll tell you what's possible.

Thank you, Tom Herzog