...
SerialOverUDP Device Redundant, SerialOverUDP Line Redundant, and SerialOverUDP System&Line Redundant communication lines were designed for support of "Serial to Ethernet Device Servers" of (e.g. Moxa NPort serial devices). These devices are powerful compact converters of RS232/422/485 interfaces to the TCP/IP Ethernet which support work in UDP mode. These devices transmit data, received from serial lines, to UDP packets, and send them to one or more IP addresses and ports (where the D2000 KOM process is located). Likewise, the serial device server sends data, which have been received on a specific UDP port, to a serial port.
The transmission parameters of the serial line are set in the configuration of the serial device and cannot be changed or set via configuration in the D2000 System. Data, transmitted in UDP packets between the device and D2000 KOM, contain only data of the serial communication. They contain neither the control nor the check characters (e.g. handshaking).
Note: an Both IPv4 and IPv6 protocols are supported.
Note: An RFC2217 Client line can be used to control the parameters of the serial line if the serial server supports the RFC2217 mode.
...
This line supports a redundancy of serial servers and also working works in D2000 Redundant System if used communication protocols support support redundancy of the application server.
Configuration parameters
...
IP address or hostname of a serial server. It is a UDP port that receives the data transmitted by the D2000 KOM process. The Port value must correspond to the serial server configuration (the parameter "Local Listen Port").
Note: it is possible to specify an address * or ALL (for IPv4 protocol) or [*] or [ALL] (for IPv6 protocol) that causes data to be received from any device, but sending data is disabled. This feature is useful e.g. in combination with the Generic User Protocol.
...