CNC Programming and Prove-Out
Follow the CAD-to-CAM-to-post chain and use graphics, dry run, single block and overrides to check a program against its setup.
CAD describes the shape; CAM plans how to cut it
CAD describes the shape; CAM plans how to cut it
CAD supplies design geometry and drawings. CAM uses geometry plus the programmer's stock, tool, workholding, operation and cutting-data choices to calculate toolpaths. Depending on the operation, CAM may work from 2D profiles or a 3D model; a solid model is not always required.
A post-processor translates CAM output into the syntax and conventions for a particular machine/control combination. Selecting the wrong post can change tool calls, arc format, offsets or startup behavior. Review the posted code as well as the CAM preview.
Other ways to create a program
A short program can be written directly in a text editor. Conversational programming asks for feature dimensions at the control. Manual data input (MDI) lets the operator enter commands at the control, often for immediate execution. These routes still require correct modes, geometry and setup data; they do not bypass prove-out. Tormach's post-processor guidelines identify control-specific requirements.
Each prove-out aid answers a different question
Each prove-out aid answers a different question
Prove-out compares the intended operation, posted code and actual setup. Follow Equipment Operating Procedure and Machine Hazards and Housekeeping for safety requirements; this page explains program-checking concepts, not a machine operating procedure.
| Aid | Useful for | Limit |
|---|---|---|
| Graphics or simulation | Inspecting path shape, endpoints, sequence and modeled interference. | A missing clamp, wrong tool model or incorrect offset can make the preview disagree with the machine. |
| Dry run | Observing a trial cycle under the control's defined test conditions. | It may substitute feed rates; the name does not guarantee no motion or no contact. Use the manual's procedure. |
| Single block | Advancing through blocks while comparing position and active modes with expectations. | One canned-cycle block may contain several motions. Not every internal action stops separately. |
| Feed override | Adjusting eligible feed motions during observation. | It need not affect rapids, tool changes or synchronized operations. Rapid override may be a separate control. |
Review the program against the setup before a supervised trial; Checklist
Review the program against the setup before a supervised trial
- Match the posted file and revision to the intended part, machine and post-processor.
- Identify the active units, plane, distance mode and feed mode at each operation.
- Compare work offsets, tool numbers and offset registers with the documented setup.
- Trace the first approach, tool changes, cycle returns and final retract against the modeled stock and fixtures.
- Check that the actual setup matches what the preview includes; resolve any discrepancy with the instructor before proceeding.
- Identify the manual's dry-run, single-block and override behavior before using those functions in a supervised trial.
- After an edit, repeat the affected checks; compare the first part's measured features with the drawing.
Practise interpretation with G-code and Toolpaths and explore the existing 3D/WebGL milling lab in Milling Operations. A successful simulation only establishes behavior within that model. It does not approve a program for a real machine.