Frequently Asked Questions

Serial Data Transfer Over an IP Network

Serial Device Server

Device servers allow non-network devices to communicate across a network. A hardware adapter connects to the device to be networked, in this case an RFC-1/B with an RS-232 data adapter, and a software driver that installs on the remote computer with which the newly networked device will communicate. The software driver creates a "virtual" COM port that translates the data stream from the network back to the original format, in this case RS-232 data.

If the transmitter site has broadband internet service then it is possible to connect the RFC-1/B to the network using a network device server. The network effectively becomes a very long serial cable through which the RFC-1/B can transfer data.

Connecting the RFC-1/B to a network does not give the RFC-1/B new features–it simply enhances existing capabilities. This kind of device server does not give the RFC-1/B a web interface. It extends the serial connection so that, for instance, data can be logged from the RFC-1/B with terminal software from the studio site or anywhere a broadband connection is available.

For example, an RFC-1/B is setup to print readings to a local printer at certain intervals. The network device server captures the data stream and transmits it over the network to a specified address. That address is assigned to a PC running appropriate capture software.

The computer receives the data and the software driver converts the network data back to RS-232 data. The capture software (such as HyperTerminal) receives the data and logs it to the display, a file or a printer just as if it came through a COM port. The network device server does all the extra work. The RFC-1/B is unaware that anything happened other than it printed a set of readings.