Engineering workflow

How to Send Files to CNC Machine: 6 Steps From Model to Spindle

A practical walkthrough of how to send files to cnc machine controllers on the shop floor. Written for design engineers and buyers who need to know which formats travel well, which transfer route to pick, and where uploads usually fail.

Get Instant Quote Talk to an Engineer

STEP / IGES / DXFUSB, DNC, networkG-code offsets checkISO 27001 uploads

On this page

Key takeaways

The machine never sees your CADA CAM post processor turns the model into G-code; only that text file reaches the controller.

Send the native CAD plus one neutral copyKeep the source file and add STEP AP214 or Parasolid so nothing depends on one kernel.

USB is fine for one-offs, DNC for long programsSmall files load from a stick; programs over a few MB are usually drip-fed.

Two things break uploadsA wrong post processor and a mismatched extension, not a bad cable.

Every upload needs a first-article checkConfirm work offsets and tool numbers before the first cutting pass.

File preparation

Which Files to Send to CNC Machine Before G-Code

The controller never reads a solid model. It reads a text program of coordinates, feed rates, spindle speeds and canned cycles. Between your model and that text sits CAM software and a post processor written for the specific machine. If you send a file to CNC machine without knowing which controller will run it, the CAM engineer has to guess, and guesses turn into rework.

For most milling jobs, one neutral format is enough to start. STEP AP214 carries solid geometry and assembly structure, and nearly every CAM package reads it. IGES still shows up in older aerospace workflows, but it transmits surfaces rather than solids, so gaps and duplicated faces are common. Parasolid and native SolidWorks or NX files are useful when the geometry is complex and you want no translation loss.

2D work is different. Laser cutting, waterjet and simple profiling run from DXF or DWG. Keep DXF in model space, at 1:1, with no dimensions, title block or hidden layers. A single leftover construction line becomes a cut path, and the part is scrapped.

Send the native file and one neutral copy together. If a face translates badly in STEP, the CAM engineer can measure the original and rebuild that patch instead of asking you for a second upload. It costs you one extra attachment and saves a day.

1
Always includeNative CAD plus STEP AP214, both at final revision.
2
2D cuttingDXF in model space, 1:1 scale, geometry only.
3
AvoidSTL for prismatic parts; it is a mesh, not a solid.
4
Label revisionsPut the revision in the file name, not inside the folder.

Tolerances and setup

What the Model Must Carry Before Transfer

A file that opens cleanly can still be unmanufacturable. Before you send files to CNC machine workflows, check that the model defines what the machinist cannot infer. Critical dimensions need tolerances. A general note like ISO 2768-m is acceptable for non-critical features, but a bearing bore at Ø25 mm needs an explicit fit, for example Ø25 H7.

Thread callouts are a frequent gap. A hole drawn at Ø6.8 mm with no note leaves the CAM engineer guessing between M8 tapping and a clearance hole. Write the thread, the class and the depth. For deep bores, add a note when the depth-to-diameter ratio exceeds 4:1, because tool deflection and chip evacuation change the process.

Surface finish matters on sealing faces, sliding surfaces and optical mounts. Ra 0.8–1.6 μm is a normal machined finish for aluminum and steel. Ra 0.2–0.8 μm needs a finer step-over or a finishing pass, and that changes cycle time. Mark the faces that need it instead of applying it to the whole part.

Tell us the material and the quantity in the same message. Aluminum 6061-T6, 316L stainless and Ti-6Al-4V cut very differently, and a 10-piece order may be machined from bar while 10,000 pieces justify a fixture. The file alone does not carry that context.

1
Tolerance calloutsH7, h6 or explicit limits on every mating feature.
2
Thread notesM8 × 1.25, class 6H, depth 18 mm.
3
Finish zonesRa 0.2–0.8 μm only where it is functional.
4
ContextMaterial grade and quantity in the same message.

Transfer routes

Three Ways the Program Reaches the Controller

Once the CAM engineer posts the program, the file has to reach the machine. The route depends on program size, controller age and how the shop is wired. None of the three methods below is better in every case.

USB is the simplest. Copy the .nc or .tap file to a FAT32 stick, plug it into the pendant, and load it from the controller directory. It works on almost every Fanuc, Siemens and Heidenhain control, including machines with no network. The risk is version control. It is easy to run yesterday's program because the stick was never refreshed.

DNC, or drip feeding, streams the program line by line over RS-232 or Ethernet while the machine cuts. Use it when the program exceeds the controller memory, which happens on mold work and long 5-axis toolpaths. Typical settings are 9600 to 115200 baud, 7 data bits, even parity and 1 stop bit for RS-232. Wrong parity produces garbled blocks or an alarm partway through a cut.

Network transfer is the cleanest option on newer machines. The controller mounts a shared folder and reads the program straight from it. On a 4,000 mm travel machine running a large aerospace part, this removes the manual step entirely. Access still needs to be restricted so only released programs are visible to the operator.

1
USBBest for one-offs and short programs under a few MB.
2
DNCRequired when the program is larger than controller memory.
3
NetworkBest for repeat production and controlled revision access.
4
Common faultParity or baud mismatch on RS-232 links.

Procedure

How to Send Files to CNC Machine: 6 Steps

Follow in order. Skipping step 5 is the most common cause of a scrapped first part.

1
1. Freeze the revisionRename the file with part number and revision, for example 4471-bracket-revC.step. Export STEP AP214 at 1:1 with no construction geometry. Confirm the units are millimeters, not inches; a mixed-unit export scales the part by 25.4 and the error is only caught at the machine.
2
2. Send the packageAttach native CAD, the neutral copy and a 2D PDF with tolerances. Add material grade, quantity and any finish requirement in the message body. Uploads go through an encrypted transfer; ISO 27001:2022 processes cover the handling, and an NDA is available on request.
3
3. CAM review and DFMThe CAM engineer checks wall thickness, tool reach and fixturing before posting. Thin floors under 1 mm deflect on aluminum, and deep pockets may need a smaller tool with a longer reach. Expect a quotation and free DFM analysis within 12 hours. Fix geometry issues at this stage, not after the first cut.
4
4. Post the programSelect the post processor that matches the controller and machine kinematics. A 5-axis post for a trunnion table is not interchangeable with one for a 3-axis mill. Use the same tool numbering as the shop's preset list, otherwise the operator has to renumber every tool by hand.
5
5. Verify before transferRun the toolpath simulation and check for gouges, rapid collisions and holder interference. Confirm the program zero matches the drawing datum. Check the posted file size against controller memory; if it exceeds the limit, switch to DNC rather than splitting the program mid-toolpath.
6
6. Transfer and prove outLoad from USB, drip feed or the network folder, then dry run with the spindle at a safe height and rapid override reduced. Set work offsets from the drawing datum, touch off tools, and cut a first article. Measure the critical features and compare against the model before releasing the run.

Choose the route

Transfer Method Comparison

Match the method to program size, controller age and production volume.

Method	Best for	Typical limit	Main risk
USB stick	One-off parts and short programs	Programs under a few MB	Operator runs the wrong revision
RS-232 DNC	Long toolpaths and older controls	Streams any length	Baud or parity mismatch garbles blocks
Ethernet DNC	Mold work and large 5-axis parts	Streams any length	Network drop mid-cut
Network folder	Repeat production runs	Controller memory size	Unreleased program visible to operator
Manual entry	Small edits at the machine	A few blocks only	Typing errors in coordinates

FAQs

Frequently Asked Questions

Can I send an STL file to a CNC machine?

You can send it, but a CAM system has to convert the mesh into surfaces before it can cut. STL triangles carry no arcs or planes, so a flat face becomes thousands of small facets.

For prismatic parts, STEP or Parasolid gives cleaner toolpaths and fewer tolerance problems. STL is acceptable for organic shapes that started as a mesh, such as a scanned surface or a 3D-printed form.

Does the file format change the achievable tolerance?

Not directly. Tolerance comes from the machine, the tooling and the setup. GreatLight holds ±0.005 mm (±0.0002 in) on qualified features.

Format matters indirectly. A poorly translated model may have gaps or shifted faces, and CAM then programs to the wrong geometry. A clean STEP export avoids that class of error.

How do I know the program is safe to run?

Simulate the toolpath first, then dry run on the machine with rapids reduced and the spindle clear of the stock. Watch the tool change positions and the retract height.

After the dry run, set work offsets and touch off each tool. Cut a first article and measure before releasing the rest of the batch.

What if the program is larger than controller memory?

Switch to DNC and drip feed the program instead of splitting it. Splitting a toolpath mid-cut leaves witness marks and often breaks the tool at the restart point.

Set the link to 9600–115200 baud, 7 data bits, even parity, 1 stop bit, and test the link with a short program before running the real one.

Can you start production the same day I send files?

Production can start within 24 hours once the file set is complete and the DFM points are closed. Missing tolerances, thread notes or material grade are the usual causes of delay.

Parts ship in 3–5 days for standard work. The historical late-delivery probability is below 2%.

Is my design file kept confidential?

Uploads are secure and confidential, and an NDA is available on request. GreatLight holds ISO 27001:2022 for information security.

We do not share customer files or use them as public examples without written permission.