The Offline CNC Program Folder: How to Run a Drip‑Feed from a Network Share and Never Lose a Program Again
Every CNC shop has experienced the USB stick shuffle. A corrupted thumb drive, an operator grabbing the wrong revision, or a monitor-side sticky note with a hand‑edited G‑code line. It costs hours of scrapped material and machine downtime. The fix is not a $5,000 DNC suite. It is a properly configured network share, a free drip‑feed utility, and a naming convention that makes overwriting a proven program impossible. This guide walks you through the exact steps to set up an offline CNC program folder that feeds directly to your machine via RS‑232 — and never loses a program again.
The Bootleg USB Problem
USB sticks are convenient, but they are a single‑point‑of‑failure for CNC programs. A technician plugs in a stick, finds a file named BRACKET_FINAL.nc, loads it, and runs. The trouble starts when someone else has a stick labelled BRACKET_FINAL2.nc that is actually the older revision. By the end of a shift, no one knows which file is current. Worse, a corrupted FAT32 table can wipe a batch of programs in seconds. In one documented case, a Canadian job shop lost an entire afternoon shift because a corrupted USB stick required three hours to find the latest revision across four machine operators' personal drives.
The solution is a central network share — a folder on a file server or a dedicated shop PC — with controlled access and a strict naming system. Combine that with a free DNC program that feeds G‑code over RS‑232, and you eliminate both the physical media and the version chaos.
Drip‑Feed: Why and How
Drip‑feeding (also called DNC operation or remote run) sends G‑code line by line from a host PC to a CNC controller over a serial cable. It is the standard method for large programs that exceed the controller's memory. The host PC sits on the network, so the program file lives on the central share. No USB involved. The machine runs directly from the network folder.
To pull this off reliably, you need three things: a physically correct RS‑232 cable, proper handshaking, and a DNC utility that can read from a mapped network drive. We cover all three below.
RS‑232 Drip‑Feed: The Hard Details
RS‑232 is the oldest reliable link between PCs and CNCs. Many modern controllers still use a 9‑pin D‑sub connector. The critical parameters for drip‑feed:
Baud Rate
Most Fanuc, Haas, and Mazak controls accept baud rates up to 19,200 or 38,400. For drip‑feed, 19,200 baud is the sweet spot between speed and stability. Some older controls top out at 9,600. Set the PC's COM port and the CNC parameter to the same rate. Common values: 9600, 19200. Do not exceed 38,400 unless you have tested the cable length and shielding; longer runs above 10 m need lower baud.
Handshaking: RTS/CTS
Flow control prevents data overrun. The dominant standard for CNC drip‑feed is hardware handshaking using RTS (Request To Send) and CTS (Clear To Send) lines. Both the PC and the CNC must be configured for RTS/CTS flow control. XON/XOFF (software handshake) is slower and less reliable because it introduces extra characters into the data stream. Set your DNC software to Hardware (RTS/CTS). On the CNC, look for parameters like I/O Channel = 0 and Handshake = Hardware.
Pinout for the Classic 9‑pin to 25‑pin Cable
The most common setup is a PC with a 9‑pin DB9 male, and the CNC with a 25‑pin DB25 female. The correct null‑modem wiring for drip‑feed with hardware handshake:
| DB9 (PC) | DB25 (CNC) | Signal |
|---|---|---|
| 2 | 2 | TX → RX |
| 3 | 3 | RX ← TX |
| 5 | 7 | Signal Ground |
| 7 | 4 | RTS → CTS |
| 8 | 5 | CTS ← RTS |
Note: Many CNC vendors (Haas, Fanuc) require a null‑modem crossover. Always test continuity with a multimeter before production use. Pin 1 (DCD) and pin 6 (DSR) can be looped on the DB9 side if the DNC software needs them.
The Naming Convention: PART_REV_CAM_VER.nc
Version control lives or dies by file names. The best convention for a CNC program folder is:
[PART NUMBER]_[REVISION]_[CAM SOURCE]_[VERSION].nc
Example: HG‑1126_B_MASTERCAM_003.nc
- PART NUMBER – The engineering drawing number.
- REVISION – A single letter (A, B, C…).
- CAM SOURCE – Short code for the CAM system (MASTERCAM, FUSION, ESPRIT).
- VERSION – A three‑digit sequential number starting at 001. No skipping.
When a new revision of the part comes in, the letter increments. Programmers increment the version number only for toolpath changes within the same revision. This convention prevents accidental overwrites because the file name itself encodes the history. Any operator can look at the folder and see immediately which file is the newest—sort by the version suffix descending.
Network Share Permissions
Security is essential to stop operators from editing or deleting programs accidentally. Set up two security groups on your file server:
- CNC_Operators – Read‑only access to the share. They can browse, open for drip‑feed, and copy to local, but cannot modify or delete.
- CNC_Programmers – Read/write access. They can add new files, edit, and rename. Only programmers should be able to write to the share.
Map the share as a drive letter (e.g., Z:\) on each shop PC. The DNC software reads from this drive. Operators authenticate with their domain or local credentials. No anonymous access. No guest accounts. This simple permission layer eliminates the risk of a wrong click wiping yesterday's proven program.
Comparison: Drip‑Feed Methods
| Method | Medium | Handshaking | Max Baud | Version Control | Cost |
|---|---|---|---|---|---|
| USB Stick | FAT32 drive | N/A | N/A | None | $5 |
| RS‑232 Drip‑Feed (share) | Network folder + serial | RTS/CTS hardware | 19,200 | Via naming convention | Free DNC sw |
| Ethernet DNC | TCP/IP | Protocol‑based | 100 Mb | Server DB | $1k+ |
The RS‑232 drip‑feed method is the best cost/benefit balance for small to medium shops. It requires no license fees, no network switch reprogramming, and it uses the RS‑232 port that is already on the machine.
Setting Up the Folder Structure
On the server (or a dedicated shop PC with file sharing enabled), create the following hierarchy:
\\CNC-Shop\Programs(shared folder)\_Released– Only programmers can write. Contains final approved files for production.\_Archive– Read‑only for everyone. Older versions moved here manually.\_Incoming– Write access for programmers, drop location for CAM post‑processed files.
Operators are pointed to _Released. They never see the other folders. This forces discipline: a file is only released when it passes simulation and prove‑out. No one runs a half‑baked program.
Free DNC Software Options
You do not need expensive DNC servers. Reliable, free utilities include:
- CIMCO DNC – Free version handles up to one machine. Features: file drip, editing, compare. Supports RTS/CTS.
- DNC4U by Predator – Lightweight free version for single machine. Works well with mapped drives.
- NCDNC – Command‑line tool that can be scripted. Good for advanced automation.
Configure the software to watch the _Released folder. The operator selects a file from the list, clicks "Send," and the machine receives the program line by line. Because the file path points to the network share, the version in the folder is always the current one.
Troubleshooting Common Drip‑Feed Failures
Even with a perfect setup, serial links can be finicky. Here are the top five issues and their fixes:
- No data received – Check the null‑modem crossover. Measure continuity on pins 2, 3, and 5. Re‑crimp if necessary.
- Garbled characters – Baud rate mismatch. Ensure both PC and CNC match exactly (e.g., 19200, not 19200 vs 19200.2).
- Drip stops after a few lines – Handshake issue. Verify RTS/CTS is enabled on both ends. XON/XOFF will cause pauses.
- File not appearing – Permission problem. Operator's mapped drive has read‑only access but the DNC software may try to write a temporary lock file. Check share permissions.
- "Memory full" error – The controller's buffer is too small for the baud rate. Lower the baud to 9600 or increase the buffer size parameter (if available).
Why This Beats Commercial DNC
Commercial DNC solutions often include features like remote monitoring, program compare, and audit logs. For a job shop with a handful of machines, the cost ($1,500–$5,000 per seat plus annual maintenance) is hard to justify. The network share + free DNC approach gives you the core function: reliable, version‑controlled program delivery. The missing audit trail and program history can be supplemented with a simple text log or a lightweight document management tool. The risk of a lost program is virtually zero if the naming convention is followed.
Automating Your SOP with Visual Documentation
Setting up the folder and naming convention is just the first half. The second half is making sure every operator and programmer follows it. That is where visual SOPs come in. A single laminated sheet at each machine showing the naming convention, the mapped drive path, and a screenshot of the DNC software interface eliminates verbal instructions and sticky‑note workarounds. Better yet, digitize that sheet into a searchable document that lives on the same network share.
This is where the Ryxen ecosystem intersects. Tools like ShopDocs (visual SOP software) allow you to embed diagrams, cable pinouts, and step‑by‑step checklists directly into a live document. When you update the naming convention or change the COM port, you edit one file and it propagates instantly. The network share becomes both the program repository and the operations manual. No more chasing down the latest version of the SOP — it updates alongside the G‑code.
By automating your SOP with digital documentation, you lock in the ROI of the drip‑feed system. Operators who can see the process — the exact cable diagram, the correct baud setting, the required file name — make fewer errors. The time spent troubleshooting drops, and the confidence in running any program from the share becomes absolute.
Final Checklist for a Bulletproof Drip‑Feed System
- [ ] Correct RS‑232 cable with null‑modem and hardware handshake pins.
- [ ] CNC parameters: Baud 19200, 7 data bits, 2 stop bits, even parity (Fanuc default), RTS/CTS.
- [ ] PC COM port: same settings, hardware flow control.
- [ ] Free DNC software installed and pointing to
Z:\_Released. - [ ] Share permissions: CNC_Operators read‑only, CNC_Programmers read/write.
- [ ] Naming convention written and posted at every machine.
- [ ] Visual SOP for cable connection and software usage published.
This system has been proven in shops with Haas, Mazak, and Fanuc controls. It costs under $50 for a good serial cable and zero for the software. The USB sticks can be relegated to emergency backup only. Your programs are safe, versioned, and served directly from the network — exactly where they belong.