Reference Manual

05-4446A01, Rev. E Mercury Reference Manual 83
IP-to-Serial Application Example
You must choose UDP or TCP to establish communications. This
depends on the type of device you are communicating with at the other
end of the IP network. In this example, we will use TCP to illustrate its
use.
In TCP mode, the transceiver remains in a passive mode, offering a
socket for connection. Once a request is received, data received at the
serial port is sent through the IP socket and vice versa, until the connec-
tion is closed or the link is interrupted. In this mode, the transceiver
behaves the same, whether it is an Access Point or a Remote.
(See
Figure 3-47 and Table 3-4)
NOTE: The TCP session has a timeout of 10 minutes (600 seconds). If
inactive for that time, the session is closed. The transceiver
offers the port again for connection after this time expires.
Establishing a
Connection
From the PC, establish a TCP connection to the IP address of the
Remote transceiver and to the IP port as configured above (30010). Use
a Telnet client application to establish this connection. Data can now be
sent between the PC and the RTU or other connected device.
Invisible place holder
Figure 3-47. IP-to-Serial Application Diagram
Point-to-Point Serial-to-Serial Application Example
Once you have configured the transceivers, they begin processing data
presented at the COM ports. Data presented at the Access Point’s COM
port is packetized and sent via UDP to the Remote. Upon receiving the
Ethernet
Crosssover
RTU
EIA-232
Computer
or Network
192.168.0.10 192.168.0.1 192.168.0.2
LA
N
COM
1
COM
2
PW
R
LIN
K
Remote
Access Point
Table 3-4. Serial Port Application Configuration
IP-to-Serial Connection
Transceiver
Location
Menu Item Setting
Access Point None is required None is required
Remote Unit IP Address 192.168.0.2
Status Enabled
IP Protocol TCP
Baud Rate 9,600 (Example)
Flow Control None
Local IP Port 30010