Active
You may tick/untick each translation line in order to make it active/not active.
Modify
Delete and Add buttons allow to add or to delete a line. The lines can be sorted using up
and down arrows.
■
Terminal servers*
Generally a Terminal Server (also referred to as a Serial Server) enables connection of devices
with serial interface to a RipEX over the local area network (LAN). It is a virtual substitute for devices
used as serial-to-TCP(UDP) converters.
Examples of the use:
A SCADA application in the centre should be connected to the Radio network via a serial interface,
however for some reason that serial interface is not used. The operating system (e.g. Windows)
can provide a virtual serial interface to such application and converts the serial data to TCP (UDP)
datagrams, which are then received by the Terminal server in RipEX. This type of interconnection
between RipEX and application is especially advantageous when:
•
there is not any physical serial interface on the computer
•
the serial cable between the RipEX and computer would be too long (e.g. the RipEX is installed
very close to the antenna to improve radio coverage).
•
the LAN between the computer and the place of RipEX installation already exists
•
Modbus TCP is used with local TCP sessions on slave sites or when combination of Modbus
RTU and Modbus TCP is used. For more information refer to Application note Modbus TCP/RTU
This applies also to other SCADA protocol TCP versions, e.g. DNP3 TCP.
NOTE: The TCP (UDP) session operates only locally between the RipEX and the central computer,
hence it does not increase the load on Radio channel.
In some special cases, the Terminal server can be also used for reducing the network load from
applications using TCP. A TCP session can be terminated locally at the Terminal server in RipEX,
user data extracted from TCP messages and processed like it comes from a COM port. When data
reaches the destination RipEX, it can be transferred to the RTU either via a serial interface or via
TCP (UDP), using the Terminal server again.
Terminal server
List box: On, Off
Default = Off
If "On", up to 5 independent Terminal servers can be set up. Each one can be either of TCP or
UDP
Type
,
Inactivity
is the timeout in sec for which the TCP socket in RipEX is kept active
after the last data reception or transmission,
My IP
address of a Terminal server has to be always
the same as the IP address of the RipEX ETH interface,
My Port
can be set as required.
Des-
tination IP
and
Destination port
values belong to the locally connected application (e.g. a vir-
tual serial interface). In some cases, applications dynamically change the IP port with each da-
tagram. In such a case set Destination port=0. RipEX will then send replies to the port from
which the last response was received. This feature allows to extend the number of simultaneously
opened TCP connections between a RipEX and locally connected application to any value up
to 10 on each Terminal server.
Protocol
follows the same principles as a protocol on COM in-
terface. You may tick/untick each individual Terminal server in order to make it
active
/
inactive
.
2
http://www.racom.eu/eng/products/m/ripex/app/modbus.html
RipEX Radio modem & Router – © RACOM s.r.o.
138
Advanced Configuration
Summary of Contents for RipEX
Page 2: ......
