A complete CAD CAM CNC workflow has four distinct outputs: CAD or vector geometry defines the part; CAM defines manufacturing operations; a post-processor creates controller-suitable instructions; and a sender or machine interface transfers and manages the job. Preserve each source file so errors can be corrected at the stage that created them.
This step sits within CNC Router Terms Beginners Need Before Their First Setup; continue with The Real Switching Costs of VCarve, Easel, Fusion, and Carveco and When Paid CNC Software Saves Time on Posts, File Ownership, and Rework when the project reaches the neighboring decision.
This CAD CAM CNC workflow guide answers the specific reader task expressed in CAD, CAM, and CNC Sender Software: The Complete Workflow.
One Project, Four Digital Stages
The stages answer different questions: what is the shape, how will it be cut, how must the controller read it, and how will the machine receive it?
Combining the stages in one software interface does not remove those logical boundaries.
A traceable workflow names the output of each stage and prevents an SVG, CAM project and G-code file from being treated as interchangeable.
For repeated work, One Project, Four Digital Stages should be converted into a standard setup note with named tools, references, inspection points and change controls.
CAD Produces Intent and Geometry
CAD may create dimensioned solids and sketches; vector tools may create lines and curves for signs or profiles.
Geometry must have correct units, scale, closed boundaries where required and a clear intended origin.
Manufacturing information such as cutter diameter and depth does not automatically exist in the drawing.
Keeping those evidence types separate makes CAD Produces Intent and Geometry easier to explain without turning one result into a universal promise.
| Stage | Typical source | Output | Correct errors here |
|---|---|---|---|
| Design | CAD or vector editor | Geometry file | Dimensions, shape, scale |
| Manufacturing plan | CAM | CAM project and toolpaths | Tool, depth, stock, strategy |
| Translation | Post-processor | Controller-suitable code | Dialect and supported commands |
| Execution | Sender or machine UI | Running job and log | Connection, offsets, job control |
For current model and support information relevant to CAD Produces Intent and Geometry, continue with the TwoTrees official wiki.
CAM Converts Geometry Into Toolpaths
CAM selects stock, setup orientation, tools, feeds, speeds, depths, entry moves and strategies such as profile, pocket or drilling.
Simulation should show expected material removal and collisions within its modeled limits.
If the design changes, regenerate dependent toolpaths rather than assuming old paths remain valid.
Sketch its stock, accessible cut boundary, holding hardware and tool approach, then apply CAM Converts Geometry Into Toolpaths to that drawing.
Post-Processing Creates Machine Instructions
A post-processor translates calculated toolpaths into the syntax and conventions expected by a controller.
Controller family, units, arcs, spindle commands and other supported features must agree with the exact machine.
File extension alone cannot prove compatibility; .nc and .gcode can contain different instructions.
The Sender Manages the Job
A sender connects to the controller, displays status, transfers or streams code and provides controls supported by that combination.
Connection settings, work offsets and modal state can affect interpretation even when the file is unchanged.
Preview, establish the setup, keep stop access and follow the current machine procedure before motion.
When two options appear equal on The Sender Manages the Job, compare the assumptions behind the tie.
A Traceable File-Naming System
Use a project code, part, revision, setup, tool or operation and post target without making names impossibly long.
Example: tray-r03-top-6mm-grbl.nc clearly separates revision, setup, tool and controller target.
Archive the CAD, CAM, posted file and setup sheet together; never overwrite the only known-good revision.
Review A Traceable File-Naming System at three moments: before purchase, before the first run and after the first controlled result.
Traceability drill: take one finished part and work backward. The posted file should identify its controller target and setup; the CAM project should show the tool, stock, origin, operations, and simulation; the design should carry the approved dimensions and revision; the job sheet should identify the physical tool and fixture used. If any link cannot be reconstructed, add that information before calling the workflow repeatable. Avoid names such as final-final2.nc, which communicate chronology without meaning. A useful name can include project, revision, side or setup, tool or operation, and post target. Preserve the native design and CAM sources because G-code is a manufacturing output, not a complete editable project archive.
Questions About From CAD to CAM to the CNC Sender: How the File Actually Moves
Is CAD the same as CAM?
No. CAD defines geometry; CAM defines how tools manufacture it.
What does a post-processor do?
It translates CAM toolpaths into instructions suited to a controller and configuration.
Is a sender required for every TwoTrees CNC?
The transfer path varies by model; use the current manual and listed interfaces.
Can I edit G-code instead of changing CAM?
Recognizing simple state is useful, but geometry or strategy changes are safer to regenerate at the source.
Why keep old revisions?
They preserve traceability and allow a known-good setup to be recovered or compared.
References
- Autodesk Fusion Manufacture Overview (official source; reviewed August 22, 2026).
- Grbl Official Documentation (official source; reviewed August 22, 2026).
