SIP-2
84/145
USER GUIDE - Rev. 3 (January 2018)
5.16
DATA FLOW CONFIGURATION
The
Flow
menu basically permits the virtual ports (TCP/UDP) configuration parameters to
be established, as well as to define the connections and/or flows between any of the
available interfaces. See section 1.2 for more general information about the port
interconnection.
The
UDP
protocol is a
connectionless protocol
. The data is transmitted as
independent blocks (packets).
The
TCP
protocol is a
connection-oriented protocol
; thus, a prior establishment phase
is necessary, and with it the data is transmitted as a continuous character flow.
5.16.1
Encapsulation protocols
Each one of the ports should be configured for operation with a specific protocol, either to
operate in
transparent mode
(
raw
and
packed
), with one of the
telecontrol protocols
being hold
or with a
policy
defined by the user.
Some protocols have multiple identifiers, which not only indicate the protocol itself, but also
the
size of the link address
, when the standard requires it as a user option.
The protocols without multiple identifiers are the following:
•
pid1, dlms, gestel, sap20, twc, dnp3,
procome
and
iec103.
The protocols with multiple identifiers and values related to them are listed below:
•
iec101_1
. IEC 60870-5 101, with FT1.2 frame and a link address size of
1
byte.
•
iec101
. IEC 60870-5 101, with FT1.2 frame and a link address size of
2
byte.
•
iec102_1
. IEC 60870-5 102, with FT1.2 frame and a link address size of
1
byte.
•
iec102
. IEC 60870-5 102, with FT1.2 frame and a link address size of
2
byte.
•
modbusrtu
. Modbus protocol in RTU mode for operation in the encapsulator
connected to the remote equipment.
•
modbusrtu_cc
. Modbus protocol in RTU mode for operation in the encapsulator
connected to the controlling equipment (control center).
