How to Send a NC File to a CNC Machine

• 1
  Key takeaways
• 2
  What a nc file to a cnc machine actually contains
• 3
  Choosing a path to send a nc file to a cnc machine
• 4
  Loading and checking the program at the machine
• 5
  Sending a nc file to a cnc machine at an outside shop
• 6
  Step by step: send a nc file to a cnc machine
• 7
  Which transfer path fits your job

An NC file is plain ASCII text. It holds a sequence of G-codes and M-codes that move the machine: spindle speed, feed rate, tool changes, coolant, and every toolpath coordinate. The CAM software writes it after post-processing, so the same toolpath becomes different text for a Fanuc, a Siemens or a Heidenhain control.

That post-processor step matters. A file posted for a Haas mill will not run cleanly on a Siemens 840D without editing. Check the header for the control name and the unit system before anything else. G20 is inches, G21 is millimeters. Mixing them is one of the most common reasons a first article comes out at the wrong scale.

File size drives the transfer method. A simple 2.5D pocket program is often under 50 KB and fits any control. A 5-axis surfacing program for a large mold can pass 20 MB, which is far beyond the memory of an older mill. Know the size before you choose the port.

• 1
  Check the header firstControl type, units, work offset number, and program number.
• 2
  Strip what the control rejectsComments with unsupported characters, stale tool lists, CAM notes.
• 3
  Keep one revision rulePart number, operation number, date. Nothing else in the file name.

USB is the fastest path on any control built after about 2005. Copy the file to a FAT32 stick, insert it, and load from the memory card screen. Keep the stick dedicated to the shop. A stick that also carries office files is how a control picks up a folder structure it cannot read.

Ethernet is the cleanest option when the machine sits on the shop network. Map a folder on the machine to a folder on the CAM workstation, then drag the file across. Set a fixed IP for the control. DHCP leases that change overnight break the mapped drive, and the operator finds out at 6 a.m.

RS-232 remains common on older lathes and mills. It is slow but reliable. Use a short shielded cable, set the baud rate to match the control (9600 or 19200 is typical), and turn off hardware handshaking only if the control requires it. A wrong parity bit gives you a garbled first line and nothing else.

Drip feed, also called DNC, streams the program from the PC line by line while the machine cuts. Use it when the file is larger than control memory. The trade-off is real: if the PC sleeps, the cable is bumped, or the network drops, the cut stops mid-path. Never drip feed a finishing pass on a part you cannot remake.

• 1
  USBFast, offline, best for files under ~100 MB on modern controls.
• 2
  EthernetBest for repeat jobs and shops with a stable network.
• 3
  RS-232Slow but dependable on pre-2005 controls.
• 4
  Drip feedOnly when memory is the limit, and only on roughing or non-critical passes.

Once the file is on the control, the work is not done. Read the first 20 lines on the screen and the last 20. The first block should set the work offset and the safe Z height. The last block should cancel cutter compensation, retract, and stop the spindle. If either end looks wrong, stop there.

Run a dry run with the tool clear of the stock. Most controls offer a dry run or machine lock mode that moves the axes without cutting. Watch the distance-to-go display. Feed hold is your friend on the first pass. A single rapid into a vise costs more than the whole setup.

Single block through the first tool change, then let it run. On a 5-axis job, slow the rotary feed override to 50 percent for the first few degrees of tilt. Collisions on rotary axes happen in the first second, not the tenth minute.

• 1
  Read both ends of the fileFirst block safe, last block clean.
• 2
  Dry run with clearanceConfirm the toolpath envelope before metal is cut.
• 3
  Single block the first toolThen release the override once the path is proven.

When you hand a job to a machining partner, the file is only half the handoff. The other half is the setup sheet: work offset origin, stock size, tool list, and the revision you expect back. Without it, the shop guesses, and guesses show up as a part that matches the model but not the drawing.

Agree on the transfer channel up front. Email attachments are fine for a 200 KB lathe program and useless for a 40 MB mold program. Most shops prefer a secure upload link for anything over a few megabytes, and that link should sit behind an NDA when the geometry is sensitive.

Version control is the part that fails quietly. Name files with part number, operation, and date. If a shop has two revisions of the same program open on two machines, someone will run the old one. A one-line email confirming the revision prevents most of these errors.

For regulated work in aerospace, medical devices or automotive, the program travels with records. Traceability means the shop can show which revision ran on which machine on which date. Keep the file name stable across that chain so the records match.

• 1
  Send a setup sheet with the fileOrigin, stock, tools, revision expected.
• 2
  Match the channel to the sizeEmail for small text files, secure upload for large ones.
• 3
  Confirm the revision in writingOne line by email, not a phone call.