bg

DNC Precision

DNC for 10 to 15 Older CNC Machines through Serial-to-Ethernet Converters

Data
NC programs to Fanuc and Siemens controls, some of them loaded through a floppy emulator on the control's RS-232 port
Industry
Machine shop, 10 to 15 CNC machines of different brands
Interface
RS-232 through USR-TCP232-410s serial-to-Ethernet converters, virtual COM port drivers
Product
DNC Precision
Result
Each machine gets a virtual COM port with its own settings in DNC Precision; the handshake lines stay under the program's control; server and client mode covers the operators' PCs

The task

A shop runs 10 to 15 CNC machines of different brands, most of them older. The majority are Fanuc controls, a few are Siemens, and they load programs over RS-232, some of them through a floppy emulator that is itself connected to the control's RS-232 port. The plan was to put the machines on the network with USR-TCP232-410s serial-to-Ethernet converters, three or four machines first, and to send programs either through virtual COM ports or with DNC software. Three questions came with it: does DNC Precision work with this kind of setup, can it talk to the converters over TCP directly instead of through virtual ports, and does it have a server and a client like the DNC system the shop was comparing it with?

The answers

1. Yes, it works in this setup

Serial-to-Ethernet converters are the usual way to bring older machines onto the network without touching the control. The converter sits next to the machine, the RS-232 cable to the control stays short, and the long run is Ethernet.

2. Use the virtual COM port driver, not raw TCP

DNC Precision does not open TCP connections itself, and that is deliberate. A reliable transfer of a large program depends on the RS-232 handshake lines, RTS/CTS and DTR/DSR, and on the control's flow control. A virtual COM port driver passes those lines through to the program, so DNC Precision can stop and resume the stream exactly when the control asks for it. A raw TCP socket carries only the data bytes. The converter vendor ships the virtual COM port driver; install it on the DNC PC, map one COM port per converter, and set the same baud rate, parity, stop bits and flow control in the converter, in the driver and in DNC Precision. The RS-232 troubleshooting guide helps when a transfer stops at the end of a program.

3. Yes, there is a server and client mode

DNC Precision runs as the server on the PC that owns the COM ports. Operators request a program from the control's keyboard or from a client on their own PC, and the DNC server page and the help file describe the setup step by step.

Starting with three or four machines

  • One converter per machine, one virtual COM port per converter, named after the machine in DNC Precision.
  • Port settings per machine: the older Fanuc controls usually want 4800 or 9600 baud, 7 data bits, even parity, 2 stop bits and XON/XOFF, so each machine keeps its own profile.
  • Keep the floppy emulator path until the first machine has transferred its longest program without a stop; then move the next machine.

Try it yourself

The trial version of DNC Precision has every option described above. Configure it the same way and write to support if your device sends something different.

Product Buy Download Support Contacts Site map
Copyright © 1999 - 2026, AGG Software.
All rights reserved.. Terms of use | Privacy policy