W
ith Serial to Ethernet Connector you can share up to 255 serial devices over network turning your computer into a terminal server. With this serial over network solution any device connected to a COM port can be accessed and used from any spot on the globe as if it were physically connected to the local machine. The data sent by serial port device is transmitted over a TCP/IP network. This is achieved thanks to our virtual serial port technology that emulates standard COM ports behavior and Windows OS treats the virtual ports as the real ones. Although the ports are treated as physical you are not limited to the quantity of physical COM ports and can create COM port connections without occupying real serial ports.
With Serial to Ethernet Connector you can: share serial port for incoming connections, connect the port to remote host, or share port using UDP connection.
Starting from version 7.0 Serial to Ethernet Connector got absolutely new user interface for even easier creation and management of connections with latter conveniently visualized and more.
Requirements
Minimum IE 6 installed, Processor: Pentium II class at least 200 MHz; RAM: 64 MB; Disk Space: 20 MB
Changes: 7.0
Added: a redesigned interface; the ability to export/import the connections configuration (from the GUI as well as the command line); the ability to set the size of the buffer or disable buffering altogether. Improved: performance when creating multiple virtual COM ports at a time, conditional data sending: you can now specify multiple conditions; the “Send data when received char with code” condition now accepts characters with ASCII codes above 127; on removing a connection, the virtual COM port is now deleted even when opened. Fixed: an issue where the GUI failed to connect to the service after reopening; incorrect behavior of strict baud rate emulation; some activation issues; a crash of the service on attempt to create a virtual COM port with a long name; a condition where a client connection set to communicate with a large number of servers could disappear after a reboot; a crash of the GUI on attempt to send a mirror request; a condition where a server would sometimes start listening for connections when not supposed to (i.e. when configured to start listening only when the COM port is opened, and the port was closed); the service could become unresponsive on startup on some older processors; with delayed sending enabled, the data could get split across multiple network packets; the “Break connection if no activity” option was not functional; a break signal from a device was not transmitted when using the Telnet protocol; a few minor bugs related to flow control negotiation.
Languages supported
English
