Dry Run & Prove-out

Dry run and prove-out is the discipline of verifying a CNC program before it is trusted to cut metal — the deliberate, step-by-step process of proving that the code moves the way it should, clears the fixtures and the work, and stops where it must, before the first tool makes the first chip. A new or edited program is an unproven promise; the crash that turns a machine into scrap, a tool into fragments or a fixture into a ruined part is almost always the promise broken at speed. Prove-out is how the machinist collects on the promise safely, and it is the stage of the machining job cycle that stands between the finished setup and the trusted run. It is done in layers of increasing risk: verify the code without motion, run it above the part, then cut the first piece under the operator’s full control.

Verifying without motion

Prove-out begins before the axes move, in the places where a mistake costs nothing but the moments that read it. The program is checked against what it must do: the toolpath simulated and backplotted in CAM and on the control’s graphics display, watched for the jumps, plunges and reversals that a written program hides; the code proofread for the addresses that matter — the work offset selected, the tool lengths matched to the tools in the spindle, the feeds and speeds sane, the rapids placed where they clear the part. The check is made against the program’s own meaning, block by block as this wiki describes under reading a program block, because a program that reads correctly is far more likely to run correctly. Errors found here — an offset named wrong, a rapid aimed at the fixture — are the cheapest errors of the whole job, caught by the eye instead of by the crash.

The dry run above the part

The first physical check is the dry run: the program run with the part and cutting fluid absent, the spindle idle or spinning in air, and the motions made harmless. On many controls the dry-run mode hands every move — rapids included — to the feed-rate override, so the whole program can be walked at a crawl; with the toolpath held safely above the highest point of the work, the machinist confirms the sequence of the program, the clearance of its motions, and the offsets that place its cuts. The run is made in single block, one line at a time, the machine stopping after each block so the operator can confirm the move before pressing cycle start again, and the feed hold is kept under a ready finger — the control that stops all axis motion instantly when a move looks wrong. Speeds are held low: a few tens of per cent of the programmed feed for the first passes of a new program, the overrides ramped up only as each section proves itself. What the dry run establishes is that the program, the offsets and the setup agree — that the code’s coordinates meet the part where it actually sits, above the fixture, clear of the clamps.

Each tool’s first approach

The most dangerous moment of prove-out is not the cutting but the approach: each tool’s rapid to the surface, the move that ends a fraction of a millimetre from the work or the stock. A small error in an offset or a clearance places that rapid inside the material, and a rapid does not stop politely. The practised approach makes it safe. The machinist watches the distance-to-go display, which shows how far the current move has yet to travel, and slows each approach to its last approach: single block on, feed rate override at its lowest, cycle start tapped to bring the tool to its start, then the move walked in slowly with the feed hold checking the remaining distance against the tool’s true position before the tool is allowed to reach the cut. When the approach is verified the run continues, and each tool in turn is brought to its surface the same careful way — for the first tool of a job, and for every tool whose offset or clearance has not yet been seen in metal.

Cutting the first part

With the approaches proven, the program is allowed to cut — but still under the operator’s control. The first part is machined in single block, each cutting motion stepped and watched, the overrides still low enough to react, the feed hold near at hand. Where an offset is uncertain, trial machining sets the tool to leave a little extra stock on the critical surface, the part is measured, and the offset is corrected before the finish pass takes the final size — the technique that turns an uncertain offset into a measured one without scrapping the part. As the first piece takes shape its features are verified early rather than at the end: a critical bore or diameter measured as soon as it is cut, so an error in an offset or a tool is found while the correction is still cheap. What the operator watches for is the first part’s conformity, and the outcome of the run is the job’s real gate — the program that proves itself becomes the program that makes the first article, and the process moves from cautious proof to trusted production.

Prove-out as a habit

The discipline of dry run and prove-out is strongest exactly when it seems least necessary — on the familiar job, the small edit, the quick rerun — because it is precisely there that the unnoticed change does its damage: the offset that shifted, the tool that was substituted, the fixture that moved. Every program, new or edited, earns the same layers of proof, and the layers cost only minutes when they are routine and everything when they are skipped. Read the code, simulate the moves, walk the program above the part in single block at low rates, bring each tool to its surface with the feed hold ready, and cut the first part under control — this is how a program becomes trustworthy in CNC machining, and how the machine, the tools and the part all survive the moment when a line of code is first asked to make metal from air.