Serial to Ethernet Connector allows creating several types of connection for three main purposes: share serial port for incoming connections (server), connect serial port to the remote host (client) and share serial port using UDP.

Let’s review some possible scenarios:

  1. Say, you have a serial port device connected to your PC. You want to share the device over network and for this purpose you install Serial to Ethernet Connector. Now, all the client computers can connect and communicate with your device as if it were connected directly to those PCs.Thus, with the help of SEC, you can turn your PC into home server with multiple clients, with or without SEC installed. This connection type is convenient when you need to pass the data from/to your serial device.
    home server

    RAW server <–> RAW multi clients

  2. Let’s imagine, you have serial port device, connected to real serial port on your local PC, and you want to operate this device using some application, which is installed on the target PC. For this purpose, both computers have SEC installed. Now, once virtual serial port is created on the target PC and the application is connected to it, this application can communicate with the remote serial device. As Telnet underlay protocol is selected, your application can manage all real serial port settings as if the device were connected directly to the server PC.

    remote serial device

    Telnet server (real serial port) <–> Telnet client (virtual serial port)

  3. Say, you have two applications, which are installed on different PCs, but you are not able to connect these PCs directly using null-modem cable. But these PCs are connected to the Internet or local network. With the help of SEC you can create virtual serial ports on both PCs and thus connect one application to another via LAN or the Internet.The applications will communicate just the same way as if they were connected directly via null-modem cable.

    using null-modem cable

    Telnet client (virtual) <–> Telnet server (virtual)

  4. You have a device, which supports Telnet (RFC 2217) protocol and which is located far from your local PC, but you want to work with it locally. For this purpose you install SEC on your local PC; and now, you can connect to the remote device and communicate with it as if it were connected locally.

    RFC 2217

    Telnet client (virtual) <–> serial device 

  5. It’s possible that you have a serial device connected to your local machine (server PC), but the application, which is supposed to communicate with this serial device, does not support OS of the server PC. On the other hand, you have virtual machine installed on this PC, which runs the needed OS.To solve this problem you can share COM port on the server machine (host OS), to which the device is attached.Then, on the virtual machine (guest OS), which will become client in this case, create virtual port using SEC. Now, specify the server’s IP address (or network name) and TCP port to connect to.Once connection is established, all data sent from the serial device, attached to the server machine, will be redirected to the virtual serial port on the client (your virtual machine), where it can be further processed by your application.

    virtual machine

    Telnet server <–> Telnet client (virtual)


          Electronic Team Licensing Policy:

  1. Single License allows you to install Serial to Ethernet Connector on one computer. To ensure client-server architecture, Serial to Ethernet Connector should be installed on two sides.
  2. If you know the exact number of computers to be equipped with Serial to Ethernet Connector, consider obtaining Limited Site License – up to 50 copies of Serial to Ethernet Connector can be installed within your Company’s offices nationwide.
  3. Other license types for Serial to Ethernet Connector include: SDK License (embed Serial to Ethernet Connector into your own software/hardware products) and Source Code License (get extensively commented source code). Find more details at our web site.