Communication Protocols

13.5 IEC 60870-5-104

13.5 IEC 60870-5-104

13.5.1 Introduction

The IEC 60870-5-104 protocol is a standardized transmission protocol (TCP/IP) for communication with remote
stations in the network (LAN, WAN).

For CP-8050, the following protocol firmware for IEC60870-5-104 is available:

Firmware System Standard and function
ETI4 CP-8050 IEC 60870-5-104 for master station (controlling station)
ETI4 CP-8050 IEC 60870-5-104 for remote station (controlled station)
FWI4 CP-8050 IEC 60870-5-104 for master station (controlling station)
with Application Layer Firewall (TCP/IP Stack separation)
FWI4 CP-8050 IEC 60870-5-104 for remote station (controlled station)
with Application Layer Firewall (TCP/IP Stack separation)

The IEC 60870-5-104 protocol is a transmission protocol on OSI-layer 5-7 for the communication between
control systems or between master stations and remote terminal units. For OSI-layer 3+4 the TCP/IP protocol is
implemented.
The protocol is especially suitable for SCADA applications.
In contrast to the IEC 60870-5-101 protocol, which establishes connections over serial interfaces, the IEC
60870-5-104 interface enables the communication over networks (Local Area Network "LAN" and Wide Area
Network "WAN"). Thereby common network components such as switches and routers can be used.
The IEC 60870-5-104 protocol uses a signal-orientated data model. Every message represents one data point,
such as e.g. one measured value, setpoint value, command or alarm. This message is thereby defined by an
address and a data type. The address then determines which signal is concerned, i.e. transmitter and receiver
must know the meaning of the address.
For the transmission of data, a "TCP-Connection" is established between 2 participating stations. One station
can establish an independent connection to several different stations.
Each station has equal access and can spontaneously perform a data transmission.

Application Layer Firewall (TCP/IP Stack separation)

The firmware FWI4 uses in contrast to the firmware ETI4 its own embedded TCP/IP stack.

SICAM A8000 Series, CP-8050, Manual 865

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

When using both firmwares in CP-8050 - ETI4 with Linux TCP/IP Stack and FWI4 with Embedded TCP/IP Stack - a
separation of the networks through the Application Layer Firewall (realized via "TCP/IP Stack Separation") is
achieved.

Schematic representation:

Example:

• ETI4 firmware: assigned LAN connector on CP-8050 [X2]

• FWI4 firmware: assigned LAN connector on CI-8520 [X1, X2]

13.5.2 Functions

Function ETI4 FWI4

■ IEC 60870-5-104 X X
– Controlling station X X
– Controlled station X X
– max. Connections 100 100
– max. Connections without TLS (recommended) 50 50

866 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

Function ETI4 FWI4

– max. Connections with TLS (recommended) 25 -
– Port number (TCP) 2404 X
– Port number (TCP) parameter-settable (1024 – 65535) X -
– Application Layer Firewall (TCP/IP-Stack separation) - X

■ Interoperability
– IEC 60870-5-104 Ed.2 X X
– Interoperability according to 13.5.10 Interoperability IEC 60870-5-104 (ETI4, X X
FWI4)

■ License
– License required to use the firmware in CP-8050 - X
– License management with Siemens ALM "Automation License Manager" - X
– Engineering: Import license from ALM - X

■ Ethernet Interface (Features)

– Ethernet Interface (13.1.4.6 Ethernet Interface - Module properties) X X
– TCP/IP optimization parameter X X
– TCP/IP Keep Alive X X

■ IEC 60870-5-104 Functions

– Acquisition of events (transmission of data ready to be sent) X X
– General Interrogation X X
– Clock synchronization according to IEC 60870-5-104 X X
(time synchronization via NTP is recommended)
– Command transmission X X
– Supervision of maximum transport delay in control direction X X
– Set control location X X
– Check control location X X
– Transmission of integrated totals X X
– File transfer X X

■ Protocol Element Control and Return Information

● Protocol element control messages
– Interface “enable, disable” X X
– Send (general) interrogation command X X
– Set control location X X
– Remote operation “enable, disable” - -

● Protocol element return information

– PRE return information 0 “Status DATA TRANSFER (BSE)” X X
– PRE return information 1 “Status DATA TRANSFER (104)” X X
– protocol specific return information 2 “Remote operation enable/disable” - -

■ Redundancy (functions for the support of redundant communication routes)

● 104 redundancy according to IEC 60870-5-104 Edition 2
– 104 redundancy “Controlling Station” X X

SICAM A8000 Series, CP-8050, Manual 867

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

Function ETI4 FWI4

– 104 redundancy “Controlled Station (with 1 Ethernet interface)” X X
– 104 redundancy “Controlled Station (with 2 Ethernet interfaces)” X X
● PRE-Redundancy X X
● PSI-Redundancy (Synchronous Connections) X X
● Port-Redundancy
– Deactivation of interface (with protocol element control message) X X
– Deactivation of interface (with redundancy control message) X X
● Device Redundancy X X
– Device Redundancy with the same PRE-Parameter X X
– Device Redundancy with different PRE-Parameter (“A/B-Parameter”) X X
– Device Redundancy with different PRE-Parameter (“A/B-Parameter”) for signals - -

■ Special functions
● WhiteList-Filter X X
● WhiteList-Filter “TI-Filter” X X
● Data Throughput Limitation X X
● Time stamp (IV=1) in Messages in Transmit Direction X X
● Originator address = 0 for all messages in transmit direction X X
● Summer time bit (SU) = 0 for all messages in transmit direction (time tag) X X
● Day of week (DOW) = 0 for all messages in transmit direction (time tag) X X
● Special functions DBAG
– Breaker delay in transmit direction (<TI=150>) X X
– Send originator address with settable value X X
● Special functions RWE
– Bit by bit marking of the field X X
– Cyclic measured values X X
– Address of the return information for selection command 2 X X
– NT-Bit, IV-Bit according to RWE requirements X X
● Suppress error in case of connection failure X X
● Error handling for connection with “failure = suppress”
– NT-Bit simulation after connection failure X X
– General interrogation after connection is OK X X

■ Security
● TLS (IEC 62351-3 “Transport Layer Security”)
– max. Connections with TLS 25 -
– Mixture of connections with/without TLS X -
– Portnumber (TCP) for TLS 19998 -
– Port number (TCP) for TLS parameter-settable (1024 – 65535) X -
– PKI Certificate-Management X -
● Whitelist-Filter
– WhiteList-Filter (predefined for all TI’s + COT‘s) X X
– WhiteList-Filter “TI-Filter” (type identification pass-through filter - parameter- X X
settable)
● Data throughput limit
– Data Throughput Limitation in Receive Direction X X
– Data Throughput Limitation in transmit direction X X

868 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

Function ETI4 FWI4

■ Webserver (PRE specific WEB-Pages) X X

■ Engineering
● SICAM Device Manager X X
● SICAM TOOLBOX II X X
● Remote operation
– Remote operation with SICAM TOOLBOX II based on http/https X 128 X 128
– Remote operation via control message “enable/disable” X 128 X 128
– Warning for “remote operation active” X 128 X 128

13.5.3 Modes of Operation

Standard Operation Mode Optional equipment Interface signals (X2, X3)

Electrical ethernet-interface - TXD+, TXD-, RXD+, RXD-
(twisted pair)
Optical interface e.g.: Siemens SCALANCE Type:
X101-1 or Phoenix FO converter
Type: FL MC 2000E LC

NOTE

i
13.5.4 Communication

For the stations to communicate with each other, suitable transmission facilities and/or network components
may be needed in addition.

Own Station (Central Station or Substation)

System System element Protocol Element Remarks

SICAM A8000 Series CP-8050/CPCI85 ETI4, FWI4

Remote Station (Substation or Central Station)

System System element Protocol Element Remarks

SICAM A8000 Series CP-8050/CPCI85 ETI4, FWI4
SICAM A8000 Series CP-8000/CPC80 ET84
CP-8021/CPC80
CP-8022/CPC80
SICAM AK3 CP-2016/CPCX26 SM-2558/ETA4
CP-2019/PCCX26 ET24
Legacy systems CP-20xx SM-2556/ETA2
(SICAM AK, SICAM TM, CP-50xx SM-2557/ETA2
SICAM EMIC, SICAM MIC, CP-60xx SM-2558/ETA4
SICAM BC) ETT0

128 This function is implemented on the basic system element!

SICAM A8000 Series, CP-8050, Manual 869

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

System System element Protocol Element Remarks

Siemens devices – – according to
13.5.10 Interoperability
IEC 60870-5-104 (ETI4,
FWI4)
Third-party system – – according to
13.5.10 Interoperability
IEC 60870-5-104 (ETI4,
FWI4)

13.5.5 LAN/WAN communication according to IEC 60870-5-104

13.5.5.1 Ethernet interface

The Ethernet Interface is implemented on the basis system element.

The interface is selected in 2 steps (see 13.1.4.4 Selection of the Ethernet interface for communication proto-
cols) :

• Selection of a LAN interface on the PRE

• Assignment of the LAN interface to the connector on BSE

13.5.5.2 Definition of the Connections

IP Addresses
Every device which is connected to a TCP/IP network has an unambiguous IP address.
The protocol firmware supports only IP addresses in the format IPv4 (=32 Bit). With that 232, therefore
4,294,967,296 addresses can be represented. The IP address is mostly represented in the dotted decimal nota-
tion.
Example: 192,168,122,195
The IP address of the own station is to be parameterized with the parameter [BSE] System settings |
Network settings | Interface | IPV4 address .
With CP-8050, a separate IP address can be parameterized for each Ethernet interface.

The IP address(es) of the remote station(s) is(are) to be parameterized for each connection in the system-tech-
nical parameters with parameter [PRE] Station definition (Connection definition) .

870 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

Port Numbers
Every IP connection is defined by the IP address of the own station and the remote station and the port
number. The port numbers are determined by the IANA (Internet Assigned Numbers Authority).
Port numbers used in the LAN/WAN protocol firmware:
Port Number Protocol Standard
2404 IEC 60870-5-104 IEC 60870-5-104 Edition 2.0

Default Router (Default Gateway) 129

If one’s own network is connected by means of a router, then the IP address of the Default Router is to be set
with the parameter [BSE] System settings | Network settings | Interface | IPV4
default gateway .

Subnet Mask 129

The subnet mask is a bit mask, that separates an IP address into a network- and a device part (Host part). It is
used in IP networks to make routing decisions.
The subnet mask is to be set with the parameter [BSE] System settings | Network settings |
Interface | IPV4 subnet mask .
The subnet mask is exactly as long as the IP address, to which it is applied (therefore 32 Bit for IPv4). All bits of
the network part are set to "1" and all bits of the device part are set to "0".
In most cases the notation of a network mask is not carried out binary, rather (as with IP address also)
frequently in decimal notation (dotted decimal notation).
Therefore the IPv4 network mask for a 27 bit network part reads 255.255.255.224.
The usable address space of a network is defined by the subnet mask. For a 27 bit network the first 27 places
of the IP address of the network part and for all hosts of the network are identical. In all practical cases of
application the network part is continuous (without zeros in between).

A network mask with 27 set bits produces a network part of 192.168.122.192. 5 bits and therefore 32
addresses are left over for the device part.

129 Function integrated on the basic system element

SICAM A8000 Series, CP-8050, Manual 871

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

In the above example the smallest host address ends with 11000000 (decimal: 192), the greatest possible
host address with the octet 11011111 (decimal: 223). The address range for the subnet in the example is
therefore 192.168.122.192 to 192.168.122.223.
The greatest address is by definition reserved for the IP Broadcast and the smallest address describes the
network itself. They are therefore not included in the freely usable addresses.
In practice the Default Gateway is often assigned to the smallest (binary in the example: 11000001, decimal:
193) or largest (binary in the example: 11011110, decimal: 222) usable IP address in the network.

Connection-specific parameters
In the master station and in the remote terminal unit(s), the required settings are to be carried out in the
parameters of the Station definition (Connection definition) .
The following parameters can be set for each connection:

• Station number (internal)

The station number is used SICAM A8000 internal for the routing of the data, diagnostic treatment and
failure management. The station number is the SICAM A8000 internal reference for the connection that
is assigned to an IP address. During the data transmission, only the IP address assigned to the station
number is transmitted, the station number is not transmitted.
During the data flow routing the data are routed for transmission to a "station number" (=Connection
number = destination station number).
The station number is to be entered in the parameter [PRE] Station definition (Connection
definition) | Station definition | Station number (internal) for each connection.

• Connection
A parameterized connection can be activated/deactivated with the parameter [PRE] Station defi-
nition (Connection definition) | Connection definition | Connection ; e.g. this
way connections can be prepared, which are activated at a later time by means of parameterization.

• Data Flow Control, Controlling/Controlled

Through the plant configuration, it is determined for every connection whether a station according to IEC
60870-5-104 is a "Controlling Station" or a "Controlled Station". Therefore for every connection one party
is to be parameterized either as "Controlling Station" or as "Controlled Station". The IEC 60870-5-104 data
flow is started/stopped by the "Controlling Station". With the parameter [PRE] Station definition
(Connection definition) | Station definition | Controlling/Controlled the role
of the own station is to be parameterized for every connection.

• IP-address
For every connection the IP address of the remote station is to be parameterized.
The IP address (Internet-Protocol) is a number, which permits the addressing of parties in LAN/WAN IP
networks. This address must always be unambiguous in a network.
The IP address is to be parameterized as follows (example): 192,168,122,195. The IP address of the
remote station is to be parameterized for every connection with the parameters [PRE] Station
definition (Connection definition) | Station definition | IP address .

• Redundancy
For every connection, its redundancy function is to be determined for the selected redundancy control:
– No redundancy [Default]
– Real connection
– Virtual connection
– Connection has IEC 60870-5-104 Controlling functionality - i.e. no redundancy
For further details refer to section "Functions for the support of redundant communication routes".
With the parameter [PRE] Station definition (Connection definition) | Station
definition | Redundancy the function of the own station is to be parameterized for every connec-
tion.

872 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

• RedGroup
When using the redundancy according to IEC 60870-5-104, every connection can be assigned to one of
several redundancy groups.
For further details refer to section "Functions for the support of redundant communication routes".
With the parameter [PRE] Station definition (Connection definition) | Station
definition | RedGroup the redundancy group number is parameterized for the connection.

• Stop behavior
If the own station is parameterized as "Controlled Station" and the IEC 60870-5-104 data transfer has
been stopped by the "Controlling Station" with "STOP DataTransfer activation", with the parameter [PRE]
Station definition (Connection definition) | Station definition | Stop behav-
iour it can be selected, if in state “STOP” all messages in transmit direction (including End of Init) will be
saved or discarded.
Note: With “stop behavior = discard” a buffer overflow is avoided in the state “STOP”

• Network connection
Optimized IEC 60870-5-104 parameters for network connection:
– LAN (IEC 104 default)
– WAN
– LAN (fast dropout detection)
– GPRS
– Satellite
– free definable 1
– free definable 2
– free definable 3

• Station failure
For certain redundancy configurations or operating modes, for the SICAM RTUs internal diagnostics, the
failure of a connection can be suppressed with the parameter [PRE] Station definition
(Connection definition) | Station definition | Station failure .
If the failure is suppressed, the connection is never signaled in the diagnostic as failed and all messages
in transmit direction (also INIT-End) are discarded until the connection is established!
Note: With that a ring overflow is avoided with non-connected remote stations.

• Day of week
With function enabled with the parameter [PRE] Station definition (Connection defini-
tion) | Station definition | Day of week the day of week (DOW field of the time tag) is
always set to “0” by the LAN/WAN protocol element for all messages in transmit direction.

• Daylight saving time

With function enabled with the parameter [PRE] Station definition (Connection defini-
tion) | Station definition | Summertime the summer time bit (SU bit of the time tag) is
always set to “0” by the LAN/WAN protocol element for all messages in transmit direction.

• Originator address
With function enabled with the parameter [PRE] Station definition (Connection defini-
tion) | Station definition | Originator address the originator address is always set to
“0” by the LAN/WAN protocol element for all messages in transmit direction.

SICAM A8000 Series, CP-8050, Manual 873

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

• Clear Ring Buffer

At failure of connection the protocol element can read data from the ring buffer from the basic system
element (BSE) after timeout and delete data without error. This function can avoid ring buffer overflow
on basic system element (BSE).
The function can be enabled with the parameter [PRE] Station definition (Connection
definition) | Station definition | Clear ring buffer .
The delay time can be parameterized with the parameter Advanced parameters | Timeout clear
ring buffer .

• Profile (type identification check)

The selected profile defines the type identifications to be supported for communication with remote
system.
Depending on selected profile, enhanced checks for fields of IEC 60870-5-104 message will be executed.
Supported Profiles:
– SICAM RTUs - IEC104 (“SICAM RTUs “Standard“)
– IEC 60870-5-104 Ed.2 (“KEMA conformance tested”)
– WhiteList-Filter
– WhiteList-Filter for passive PRE
– WhiteList-Filter + TI-Filter
– TI-Filter
The required profile can be selected with the parameter [PRE] Station definition (Connection
definition) | Station definition | Profile (type identification check) .

• Data throughput limit in receive direction (msg/s)

• Data throughput limit in transmit direction (msg/s)

The protocol element for IEC 60870-5-104 in SICAM RTUs supports a limitation of data throughput in
transmit-/receive direction for IEC 60870-5-104 data messages.
The number of messages/second in transmit direction can be parameterized with the parameter [PRE]
Station definition (Connection definition) | Station definition | Data
throughput limit in transmit direction (msg/s) (0 = no data throughput limitation).
The number of messages/second in receive direction can be parameterized with the parameter [PRE]
Station definition (Connection definition) | Station definition | Data
throughput limit in receive direction (msg/s) (0 = no data throughput limitation).

IEC 60870-5-104 Parameter

For the coupling of different systems with the IEC 60870-5-104 protocol, the setting of the variable elements
of the message according to IEC 60870-5-104 to the following defined values is required:
IEC 60870-5-101 Parameter Description System
Element
Cause of transmission (COT) Number of octets for cause of transmission = 2 BSE
Common address of ASDU Number of octets for common address of the ASDU = 2 BSE
(CASDU)
Information object address Number of octets for the address of the information object = 3 BSE
(IOA)
Maximum message length max. 253 BSE
Time tag Number of octets for time tag = 7 BSE

NOTE

i If one parameter does not correspond to the required setting, a parameter error is reported!

874 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

IEC 60870-5-104 Parameters / TCP Parameters

The IEC 60870-5-104 specific parameters for "Definition of monitoring times" and "Maximum number of unac-
knowledged I-format frames k and acknowledgement w" are grouped into parameter groups. One of these
parameter groups (104 parameter, network connection) can be selected for every connection.

NOTE

i The modifying of the 104 specific parameters requires detailed knowledge of the IEC 60870-5-104 protocol
and should therefore only be performed by communications experts or after consultation!

Supported IEC 60870-5-104 / TCP Parameters

Network connection
LAN (fast
LAN (IEC dropout free free free
104 detec- GPR Satel- defin- defin- defin-
Parameters default) WAN tion) S lite able 1 able 2 able 3
IEC 104 Parameter
timeout connection setup 5 5 5 60 5 5 5 5
t0
Timeout transmit t1 15 60 7 250 60 15 15 15
timeout transmit acknowl- 10 10 2 10 10 10 10 10
edge t2
timeout connection check 20 20 10 250 20 20 20 20
t3
Max. no. of APDUs until 12 12 12 12 60 12 12 12
acknowledgement (k)
Number od APDUs until 8 8 8 8 8 8 8 8
acknowledge (w)
TCP-parameters *) *)

transmission optimization **) **) **) **) **) **) **) **)

initial TCP retransmission 2500 2500 100 2500 2500 2500 2500 2500
timeout
minimum TCP retransmis- 250 250 100 1000 250 250 250 250
sion timeout
maximum TCP retransmis- 5000 5000 200 1000 5000 5000 5000 5000
sion timeout 0
MSS (maximum segment 1460 1460 1460 512 1460 1460 1460 1460
size) transmit direction
TCP connection close ***) ***) ***) ***) ***) ***) ***) ***)

*) ... The settings for TCP parameters can not be changed in CP-8000/
CP-802x (ET84)
**) ... Possible settings:

• default (ack delay, no nagle)

• bandwith (ack delay, nagle)
• throughput (no ack delay, nagle)
• response time (no ack delay, no nagle)
***) ... Possible settings:

• close with FIN or RST (default)

• close with RST

SICAM A8000 Series, CP-8050, Manual 875

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

The following IEC 60870-5-104 parameters can be set per parameter group:

• Timeout connection setup t0

Timeout for connection setup.
Note:
The parameter [PRE] Interface parameter | Network connection | LAN (IEC 104
default) | IEC 104-Parameter | Timeout connection setup t0 is not evaluated by the
protocol!

• Timeout transmit t1
Timeout for transmit or test frames.
Transmitted data (Information/Transmit-/Test frames) must be acknowledged by the remote station at
the latest before expiry of the Timeout t1 with a transmit or test frame. On timeout the connection is
terminated and then re-established.
The Timeout t1 is to be parameterized with the parameter [PRE] Interface parameter |
Network connection | LAN (IEC 104 default) | IEC 104-Parameter | Timeout
transmit t1 .

• Timeout Transmission Acknowledgement t2

Timeout for acknowledgment, if no data is transmitted t2<t1.
With the simultaneous transmission of user data (I-Frames) in both directions, acknowledgments are sent
together in the user data messages. For the data transmission of user data in only one direction, an
acknowledgment (S-frame) is sent after Timeout t2 at the latest.
The Timeout t2 is to be parameterized with the parameter [PRE] Interface parameter |
Network connection | LAN (IEC 104 default) | IEC 104-Parameter | Timeout
transmit acknowledge t2 .

• Timeout Connection Check t3

Timeout for the transmission of Test-Frames, if no data traffic t3>t1.
If no data is transmitted with connection established, then a test frame (TESTFR act) is sent after t3 at the
latest. This must be replied to by the remote station, also with a Test-Frame (TESTFR con). This test proce-
dure can be performed independently by both sides of a connection. The Timeout t2 is retriggered by the
reception of Information/Transmit/Test frames.
The Timeout t3 is to be parameterized with the parameter [PRE] Interface parameter |
Network connection | LAN (IEC 104 default) | IEC 104-Parameter | Timeout
connection check t3 .

The following parameters can be set for each parameter group for "Maximum number of unacknowledged I-
format frames k and acknowledgement w":

• Maximum number of unacknowledged APDUs (k)

Greatest difference between receive sequence number and transmit status variable. User data is trans-
mitted from one station to the remote station without needing to receive an immediate acknowledge-
ment for the transmitted user data. However, if after a max. number (k) of transmitted but not yet
acknowledged ASDUs no acknowledgement has been received, no further data is sent until the reception
of the acknowledgement.
An acknowledgement must now be sent by the remote station before expiry of t1.
For IEC 60870-5-104 a sum acknowledgement is used i.e. all consecutively numbered messages received
without error up to a moment in time are acknowledged with an acknowledgement message.
The maximum number of unacknowledged APDUs (k) is to be parameterized with the parameter [PRE]
Interface parameter | Network connection | LAN (IEC 104 default) | IEC 104-
Parameter | Max. no. of APDUs until acknowledgement (k) .

876 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

• Number od APDUs until acknowledge (w)

Acknowledgement at the latest after reception of "w" I-format APDUs.
User data is transmitted from one station to the remote station without needing to receive an immediate
acknowledgement for the transmitted user data. An acknowledgement is sent after the reception of a
max. number (w) of user data messages (APDUs).
Recommendation: "w" should not exceed 2/3 of the "k"-value.
The number of APDUs until acknowledgement (w) is to be parameterized with the parameter [PRE]
Interface parameter | Network connection | LAN (IEC 104 default) | IEC 104-
Parameter | Number of APDUs until acknowledgement (w) .
The following TCP/IP parameters are supported by the protocol firmware:

• MSS (maximum segment size) transmit direction

One TCP packet typically has a maximum size of 1500 Bytes. It may only be so large, that it fits in the
transmission layer situated below, the Internet protocol IP. TCP and IP protocols each define a header of
20 Bytes size. Therefore 1460 bytes are left over for the user data in a TCP/IP packet.
With the parameter [BSE] System settings | Network setting | Interface | MSS
(Maximum Segment Size) transmit direction the maximum user data length is determined in
the TCP/IP packet (max. 1460 Bytes). The modification of the parameter "MSS (Maximum Segment Size)
transmit direction" is then definitely required, if TCP/IP is implemented in combination with transmission
systems which cannot transmit the TCP packets with the max. defined size (e.g. GPRS supports max. 500
Bytes).

• Transmission optimization
The data transmission over TCP/IP can be optimized with the parameter [PRE] Interface param-
eter | Network connection | LAN (IEC 104 default) | TCP parameter | Transmis-
sion optimization for the following requirements:
– default (ack delay, no nagle)
– bandwith (ack delay, no nagle)
– throughput (no ack delay, nagle)
– Response time (no ack delay, no nagle)
(For details see chapter "Data Transmission Procedure")

• Maximum segment size (MSS) in transmit direction

In rare cases transmission systems support only a limited Maximum Segment Size (MSS) for Ethernet
packets (MSSmax = 1460 Bytes).
e.g.: there are GPRS systems that only support a max. Segment Size of 512 Bytes.
The maximum segment size can be set with parameter Network connection | * | TCP-param-
eter | MSS (maximum segment size) transmit direction or with the parameter
Advanced parameters | TCP/IP optimizations | MSS (maximum segment size)
transmit direction .

• Maximum Segment Size in Transmission direction “MTU“ (=Maximum Transmission Unit)

In rare cases transmission systems support only a limited Maximum Segment Size (MSS) for Ethernet
packets (MSSmax = 1460 Bytes). e.g.: there are GPRS systems that only support a max. Segment Size of
512 Bytes. The maximum segment size can be set with parameter [BSE] System settings |
Network settings | Interface | * | MTU .

• Minimum TCP expected acknowledgement time

The minimum TCP expected acknowledgement time can be modified with the parameter [BSE]
System settings | Network settings | Interface | * | Minimum TCP retransmis-
sion timeout .

SICAM A8000 Series, CP-8050, Manual 877

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

• TCP connection close

The mode for the termination of a TCP/IP connection can be modified with the parameterr [PRE]
Interface parameter | Network connection | LAN (IEC 104 default) | TCP-param-
eter | TCP connection close :
– close with FIN or RST (default)
– close with RST
(for further details, see to section "Data Transmission Procedure")
By default the parameters are set so that no modification is required.

Data Transmission Procedure

The transmission of the data from the remote terminal unit to the master station as well as from the master
station to the remote terminal unit takes place spontaneously for each LAN connection. For each LAN connec-
tion, the data transmission is comparable with that between 2 stations over a virtual point-to-point connec-
tion.

Data Transmission Procedure

The prioritization and 104-blocking of the data to be sent takes place on the basic system element (BSE). The
data transmission is started after a startup or with redundancy switchover after establishment of the TCP/IP
connection and after "STARTDTact".
The data storage on the basic system element is managed individually for each LAN connection (excluded
from this are special redundancy modes such as e.g. "synchronous connections").
Data messages "to all" are already split up selectively for every LAN connection by the communications func-
tion on the basic system element (BSE).
Data messages to "prepared connections" will be requested by the protocol element but not sent and
discarded without error message. The protocol element will send a positive activation confirmation (ACTCON
+) for general interrogation command and test command to the basic system element.
The data processing of the TCP packets can be influenced by the parameter [PRE] Interface parameter
| Network connection | LAN (IEC 104 default) | TCP-parameter | Transmission
optimization – the moment for the transmission of a TCP packet is controlled by the Nagle algorithm. The
Nagle algorithm is applied with the TCP protocol and should prevent too small packets, for which the addi-
tional overhead due to header etc. is considerably larger than the actual user data.
Nagle algorithm for the transmission of TCP packets:

• If a TCP packet is full, then send immediately

• If a TCP packet is not full, then this is first sent when a TCP acknowledgement is received.
The data pick-up from the basic system element is performed in such a way, that on the one hand the blocking
per connection is optimally utilized, and on the other, one connection with a lot of data does not block others
unnecessarily long. With the data pick-up for transmission, the connections are processed in ascending order.
The communications function on the basic system element performs the prioritization of the data per connec-
tion. During the data pick-up, the highest priority data object is always offered for transmission.
Note:
For the optimum prioritization and blocking of the data with LAN/WAN communication, only 1 priority level is
to be used.
→ As a result a more favorable prioritization for LAN is achieved, since the data for transmission for each
connection (=destination station) are requested in groups (=blocked) by the LAN/WAN protocol element. In
addition, through the blocking at TCP/IP level, several messages for this connection are transmitted.
→ Due to this the processing of the connections according to the Round-Robin principle is ensured (Connec-
tions are processed in ascending order).
System data is processed with high priority by the communications function on the basic system element and
transferred to the LAN/WAN protocol element for transmission as fast as possible.

878 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

Data transmission control with Start/Stop (data flow block)

For every TCP connection, one station is either "Listener (Server)" or "Connector (Client)".
After startup, redundancy switchover or after a failure of the connection, every connection on TCP level is
established by that station defined as "Connector (Client)".
For IEC 60870-5-104 the data transfer is controlled by the Controlling-Station with the messages Start/Stop
data transfer. After establishment of a connection at TCP/IP level, the transmission of the data according to IEC
60870-5-104 is stopped.
The data transfer according to IEC 60870-5-104 is started by that station defined as "Controlling Station" with
STARTDTact (Start Data Transfer Activation).
After reception of the confirmation from the remote station (STARTDTcon = Start Data Transfer Confirmation)
the connection is ready for the transmission of the data.
According to IEC 60870-5-104 the data transmission must be started by the Controlling Station with STARTD-
Tact (Start Data Transfer ACTIVATION). The start must be confirmed by the remote station (Controlled Station)
with STARTDTcon (Start Data Transfer CONFIRMATION). If no STARTDTcon has been received within t1 after
sending STARTDTact, the connection is terminated again. User data may only be transmitted after successful
connection establishment.
The data transmission is stopped by the Controlling Station with STOPDTact (Stop Data Transfer ACTIVATION).
STOPDTact is confirmed by the remote station (Controlled Station) with STOPDTcon (Stop Data Transfer
CONFIRMATION).
After start of the IEC 60870-104 data transfer with the message STARTDTact by the controlling station, a
general interrogation command can be sent to the controlling station if required (for update of the process
data base). The function GI after "Start Data Transfer" can be enabled with the parameter [PRE]
IEC60870-5-104 | Communication functions | General interrogation | GI after
START DT for all connections of the protocol element.
With function enabled, the protocol element will send an internal system message to the basic system
element; this will initiate a sending of a general interrogation command to the controlling station.
Start-/Stop data transfer messages are transmitted with U-Frames "Unnumbered Control Functions" and are
used by the Controlling Station in order to control the data transfer from a Controlled Station. Stop Data
Transfer is used especially when several connections are established to one station but one connection (e.g.
due to redundancy) is not used. Start/Stop Data Transfer is intended to prevent a possible loss of data during
the switchover to another connection.
The duration of the stopped data transfer is not monitored!
If, as Controlling Station, one remote station blocks the data transfer for a longer period, an overflow of the
data storage (rings) on the basic system element (BSE) can occur and through this a fault in the system is
signaled. The handling of the user data with stopped "Data Transfer" can be parameterized for each connec-
tion with the parameter [PRE] Station definition (Connection definition) | Station
definitions | Stop behaviour.
Handling of the user data if the data transmission is stopped with STOPDTact:

• "Save" [Default]
The data are saved in the data storage of the communication function on the basic system element (BSE)
until they are deleted by the dwell time monitoring or can be transmitted to the remote station.
Advantage: Storage of the data with stopped data transfer
Disadvantage: Ring overflow possible

• "Discard"
All data in transmit direction are read out immediately from the basic system element (BSE) by the
protocol firmware, not transmitted and discarded without error message. As a result an overflow of the
data storage (rings) is prevented.
Advantage: Ring overflow is prevented
Disadvantage: Data loss

Connection Termination
The following possibilities for closing a TCP/IP connection are available:

SICAM A8000 Series, CP-8050, Manual 879

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

• Close with FIN or RST (default)

– 4-way handshake (FIN, ACK, FIN, ACK) for all “known IP addresses“ (configured in the parameters of
the Connection definition).
Such a termination occurs for instance if a IEC 60870-5-104timeout expires or when a IEC
60870-5-104message with an illegal frame format is received. If the remote station cannot be
reached or does not respond to the FIN, the socket will only be deleted after a TCP timeout (3
minutes). During this time the socket and its resources are occupied and this can cause resource
problems with the result that no new connections can be established. Possible reasons: Possible
reasons:
– Denial-of-service attack
– Faulty remote station
– 1-way handshake (RST) Such a termination occurs for instance if
– the IP address of the remote station is not included in the connection definition
– a connection to a remote station is already established, and the remote station tries to establish
further connection.

• Close with RST

IEC 60870-5-104 defines the termination of a connection with 4-way handshake. The closing of a
connection with 1-way handshake (RST) only can be used for the following cases:
– robust interface required (e.g. with an insecure WAN or Internet)
– downward compatible applications

Acknowledgement Procedure
For each connection, all data messages transmitted must be acknowledged by the remote station. Thereby,
not every individual IEC 60870-5-104 packet that can contain several IEC 60870-5-104 message objects must
be acknowledged, rather several consecutively numbered messages received without error up to a moment in
time can also be acknowledged in one operation with one acknowledgement message (sum acknowledge-
ment procedure)
With this sum acknowledgement procedure, user data is transmitted from a station to the remote station
without an acknowledgement needing to be received immediately for the transmitted user data. If no
acknowledgement has been received after a maximum number (k) of transmitted but not yet acknowledged
IEC 60870-5-104 packets (ASDU's), no further data is sent until reception of the acknowledgement.
The max. number (k) of messages is to be set with the parameter [PRE] Interface parameter |
Network connection | LAN (IEC 104 default) | IEC 104-Parameter | Max. no. of
APDUs until acknowledgement (k) .
An acknowledgement must now be sent by the remote station before expiry of t1. With the simultaneous
transmission of user data (I-Frames) in both directions, acknowledgments are sent together in the user data
messages. For the data transmission of user data in only one direction, an acknowledgment (S-frame) is sent
after Timeout t2 at the latest.
On reception of IEC 60870-5-104 packets (APDUs) with user data, an acknowledgement must be sent at the
latest after reception of a settable maximum number of messages. The max. number (w) of messages is to be
set with the parameter [PRE] Interface parameter | Network connection | LAN (IEC 104
default) | IEC 104-Parameter | Number of APDUs until acknowledgement (w) .
The retries are (insofar as necessary) performed automatically by the TCP/IP layer of the protocol until the
termination of the connection and can only be influenced indirectly with the parameter [BSE] System
settings | Network settings | Interface | TCP min. acknowledge time .
The data transmission at TCP level starts the data transmission with the settable initial value for the expected
acknowledgement time. Depending on the quality of the connection the expected acknowledgement time is
adapted dynamically between the parameterized minimum or maximum TCP expected acknowledgement
time.
If, with connection established, the IEC 60870-5-104 acknowledgement for transmitted data (information/
transmit/test frames) is missing for longer than the set 104 expected acknowledgement time (timeout t1), all

880 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

IEC 60870-5-104 messages already sent but not yet acknowledged are negatively acknowledged to the basic
system element (BSE), the TCP connection is terminated with RST and the remote station flagged as failed.
The connection is setup again after a fixed implemented delay time of 2 seconds.

NOTE

i The parameter [PRE] Interface parameter | Network connection | LAN (IEC 104
default) | IEC 104-Parameter | Timeout connection setup t0 is not evaluated by the
protocol!

The error message for the failed connection is reset after successfully established connection at TCP level.

Failure Monitoring
The monitoring of every established connection is carried out by the active master / remote terminal unit
either by means of (subject to acknowledgement) spontaneously transmitted user data messages or by means
of cyclic transmitted messages (Test-Frames). The failure monitoring can be carried out independently by both
participating stations of a connection.
The Test-Frames are generated by the protocol firmware itself and are not transferred to the basic system
element.
If no user data is transmitted with a connection established and activated data transfer, a Test-Frame (TESTFR
act) is sent at the latest after expiry of the time t3 (Timeout Connection Test). This Test-Frame must be replied
(acknowledged) by the remote station with a Test-Frame (TESTFR con) at the latest before expiry of the
timeout t1.
The "Test function of the link layer" (test command) also enables a cyclic message transmission and moni-
toring controlled by the basic system element. This test function can be parameterized on the basic system
element (BSE) in the IEC 60870-5-101/104 parameter block.
The timeout t3 is retriggered with the transmission of user data messages or test frames. After a message
transmission, the remote station is signaled as failed after expiry of the monitoring time t1 (Timeout) and the
TCP connection is terminated with RST or FIN. For further details, refer to section “Acknowledgement Proce-
dure”.
No further data is sent to failed remote stations until successful establishment of the connection.
The data is stored in the data storage of the communication function on the basic system element (BSE) until
these are deleted by the dwell time monitoring or can be transmitted to the re-reachable remote station.No
further data is sent to a failed remote station until successful station initialization.

Error Handling for “Failed” Connections

The failure of a connection can be suppressed with the parameter [PRE] Station definition
(Connection definition) | Station definitions | Station failure.
The error handling for faulty connections with “failure = suppress” can be set with the parameter [PRE]
Station definition (Connection definition) | Station definitions | Error
handling for connections with ”failure = suppress“ .
Error handling for faulty connection if ”failure = suppressed” – Mode-0“: (=default)

• no error in diagnostics

• no NT-Bit emulation for received data by BSE

• no general interrogation command initiated by BSE after connection error

Error handling for faulty connections if ”failure = suppressed – Mode-1“: 130

130 ETA2 supports only mode-1 (without parameter)! not supported by ETA4 with “IEC 60870-5-104 redundancy with 2 Ethernet inter-
faces”! During connection failure all data messages in transmit direction (including “End of Init”) will be discarded. With that a ring
overflow is avoided with non-connected remote stations.

SICAM A8000 Series, CP-8050, Manual 881

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

• no error in diagnostics

• NT-Bit emulation for received data by BSE

• general interrogation command initiated by BSE after connection error

Connection Failure “notify/suppress” with 104-Redundancy with 1 Ethernet Interface

Supported settings for “failure = notify/suppress“ (each redundancy group):
Failure for “virtual connection“ Failure for "real connection(s)" 131 supporte
d
notify notify ✓
notify suppress ✓
suppress notify
suppress suppress

13.5.5.3 Station Initialization

After startup, the connection is first established on the TCP/IP level. Then the Controlling Station starts the
connection on the 104-level by means of STARTDTact (Start Data Transfer Activation). Afterwards the trans-
mission of user data and other system messages to the remote station is started either immediately or only
after the transmission of the INIT-End message.

End of Initialization
The INIT-End message "<TI=70> End of Initialization" is only transmitted to the remote station for each ASDU
after startup of the component or the basic system element, if the following preconditions are fulfilled:

• Connection is established at TCP/IP level

• Connection is established at IEC 60870-5-104 level with STARTDTact

• Sending of „end of initialization" must be enabled on the basic system element in the IEC
60870-5-101/104 parameter block

• "INIT-End" has been received by the basic system

• Parameter [PRE] Station definition (Connection definition) | Station defini-

tions | Stop behaviour = "save"

• Parameter [PRE] Station definition (Connection definition) | Connection defini-

tion | Station failure = "notify"

13.5.5.4 Acquisition of Events (transmission of data ready to be sent)

The transmission of the data from the remote terminal unit to the master station as well as from the master
station to the remote terminal unit takes place spontaneously with connection established and for each
connection. The prioritization and 104-blocking of the data ready to be sent takes place on the basic system
element (BSE). The data transmission is started after a startup or, with redundancy switchover, after successful
establishment of the connection.
For further details, see to section "Data Transmission Procedure".

13.5.5.5 General interrogation, Outstation interrogation

The general interrogation (outstation interrogation) function is used to update the master station after the
internal connection initialization or after the master station has detected a loss of information. The general

131 All real connections of a redundancy group must have the same parameter settings!

882 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

interrogation function <TI:=100> of the master station requests the remote terminal unit connected over one
connection to transmit the current values of all its process variables.
A general interrogation command "to all" triggered in the system is always transferred by the communications
function on the basic system element (BSE) station-selective (per connection) to the protocol element of the
master station and transmitted by this to the remote terminal units.
A general interrogation command to a "prepared connection" will not be transmitted but positive confirmed
(ACTCON+) by the protocol element.
After start of the IEC 60870-104 data transfer with the message STARTDTact by the controlling station, a
general interrogation command can be sent to the controlling station if required (for update of the process
data base). For further details, refer to section "Data Transmission Procedure" | "Data trans-
mission control with Start/Stop (data flow block)".
If the IEC 60870-104 data transfer will be stopped by the controlling station using STOPDTact during running
general interrogation, the not sent general interrogation data stored on BSE can be discarded or continued
with sending after STARTDTact.
This function can be enabled on BSE with the parameter [PRE] Data base management | Data base
management at failure | Failure behavior for process inform (GI) . With selection
“Delete“ all process information with cause of transmission “interrogated by station interrogation“ including
ACTCON and ACTTERM will be deleted in case of communication failure or STOPDTact.
The deactivation of a general interrogation <COT:= 8> (DEACT) is not supported. If a deactivation is received,
the protocol element responds with DEACTCON- with <COT:=45> (unknown cause of transmission).

13.5.5.6 Clock Synchronization

In networks and in systems with time-critical tasks a precise time is indispensable.

The clock synchronization for IEC 60870-5-104 can be performed in the following ways:

• Clock synchronization command <TI:=103>

• Network Time Protocol (NTP) according to RFC 1305 132

For SICAM RTUs a clock synchronization using NTP is recommended!
Messages that are transmitted after a startup contain the

• current time, if the automation unit already has been synchronized previously

• relative time from startup (reference date), if the automation unit already has never been synchronized
Reference date for SICAM RTUs: 1.1.2001 1.1.2001
Reference date for Ax1703: 1.1.1997 1.1.1997
In both cases, the time tag is marked as invalid until the first reception of the synchronizing event.

Clock Synchronization Command

The clock synchronization of the remote station can be performed over the network. With SICAM RTUs the
clock synchronization command <TI:=103> is sent spontaneously at a change of time and cyclic 1x per minute
with the actual time.
The procedure for clock synchronization defined in IEC 60870-5-5 is not recommended for use with network
communication, because the transmission delay cannot be evaluated and therefore a correction of transmis-
sion delay cannot be performed properly.
However, the clock synchronization with the clock synchronization command can be implemented in configu-
rations with networks if the "maximum network delay" is less than the accuracy required for time synchroniza-
tion.
If for instance the network provider guarantees, that the maximum delay for the transmission in the network
is never greater than 400 milliseconds and the accuracy required for the time synchronization is only 1
second, then this procedure can be used for clock synchronization.
If the accuracy of clock synchronization via network is insufficient, a local time signal receiver or clock synchro-
nization via NTP must be used by the remote station.

132 Function integrated on the basic system element

SICAM A8000 Series, CP-8050, Manual 883

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

SICAM RTUs as Sender of Clock Synchronization Command

The clock synchronization command will be sent cyclic at the 30th second of minute. In SICAM RTUs the trans-
mission of the clock synchronization command is initiated by the basic system element.
Before switchover of daylight saving time the clock synchronization command will be sent (in advance) with
new time.

SICAM RTUs as Receiver of Clock Synchronization Command

With SICAM RTUs the correct setting of time is only ensured if the clock synchronization command will be
received between 10th and 50th second. In SICAM RTUs the new time will be set at next change of minute.

NOTE

i With SICAM RTUs the new time must be sent in (advance) at change of daylight saving time, otherwise the
time is not correct for up to 1 minute.

13.5.5.7 Command transmission

The master station always sends data telegrams in command direction to the remote partner spontaneously if
the connection has been established (data transmission must have been started and the number of unac-
knowledged APDUs must not have been reached yet). The prioritization and 104-blocking of the data to be
sent already takes place on the basic system element (BSE). Commands and other messages defined according
to IEC 60870-5-104 are always transmitted without 104-blocking.
For commands in transmit direction the “Control location check” function can optionally be used in the
protocol element. If the control location check has been enabled, commands will only be sent if the originator
address of the command has been enabled beforehand by control telegrams.
The <TI:=107> test command with cause of transmission <COT=6> (activation) can be sent via each connec-
tion from the base system element to check the situation.
The remote partner must respond to the test command with cause of transmission <COT=7> (confirmation of
activation) and P/N=1 (ACTCON+). The check of the correct confirmation of the test commend will be done on
the basic system element.
A test command triggered by the base system element to a prepared connection is not sent and confirmed by
the protocol element with ACTCON+.
Refer to the Data Transmission Procedure, Page 878 paragraph and 13.5.7 Message Conversion paragraph for
more detailed information.

Command Transfer Monitoring (Dwell Time Monitoring)

During the transmission of data in networks, unwanted delays can occur. So that no unwanted process
behavior is triggered due to a delayed output of commands, the LAN/WAN protocol element can monitor the
transmission time (dwell time) of the data in the network for selected process information in control direction.
This monitoring prevents the output of outdated commands.
If the command delay monitoring is activated and a command message arrives via the LAN interface, then the
time tag of the telegram is compared with the current time of the component.
If the evaluated command delay time (transmission time of the data in the network) is longer than the para-
metrized command delay monitoring the command message is discarded without an error message.
If the time of the component has not been specified yet, the [PRE] IEC60870-5-104 | Communication
functions | Command transmission | Discard command if local time not set parameter
can specify whether a received command telegram is forwarded for further processing or whether it is deleted
when command runtime monitoring is active.
The controlling station detects the failed command output through the missing of the confirmation of activa-
tion (ACTCON).
The time for the command delay monitoring is to be parameterized on the basic system element (BSE) in the
IEC 60870-5-101/104 parameters per protocol element. The command delay monitoring can also be deacti-
vated (Command delay monitoring = 0).

884 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

Error signalization To localize the error, the number of commands discarded by the command delay moni-
toring since RESET is summed and the last discarded command messages are additionally saved in a diagnostic
ring. The counters and the diagnostic ring can be read out with the SICAM TOOLBOX II (ST-Emulation).
Monitoring the command delay for the following message types (TI's):

• <TI:=58> Single command with time tag CP56Time2a

• <TI:=59> Double command with time tag CP56Time2a

• <TI:=60> Regulating step command with time tag CP56Time2a

• <TI:=61> Setpoint command, normalized value with time tag CP56Time2a

• <TI:=62> Setpoint command, scaled value with time tag CP56Time2a

• <TI:=63> Setpoint command, short floating point number value with time tag CP56Time2a

• <TI:=64> Bit pattern of 32 bit with CP56Time2a time marker

• <TI:=107> Check command with time tag CP56Time2a

NOTE

i • The message conversion in receive direction can also generate the assigned message types without
time tag. As a result, indirectly the internal type identifications <TI=45, 46, 47, 48, 59, 50, 51 and
104> are also affected.

• The command delay monitoring is only carried out for command messages with the cause of transmis-
sion ACT (Activation)!

Control location / Control location check

The “Control location” function is used to make sure that commands and setpoints are transferred from
authorized sources only. Once the function has been activated, commands/set point adjusting commands are
only transferred to the remote partner by the protocol element if the control location (originator address) has
been enabled.
If the control location is not enabled, the protocol element immediately sends back a negative acknowledg-
ment of activation (ACTCON) to the originator address (for more details on the control location, see section
13.1.4.7 Control location function for commands and setpoint values).

13.5.5.8 Transmission of integrated totals

A counter interrogation command "to all" triggered in the system is always transferred by the communications
function on the basic system element (BSE) station-selective (per connection) to the protocol element of the
master station and transmitted by this to the remote terminal units.
The functionality implemented in the System SICAM RTUs concerning integrated totals is documented in the
document "Common Functions Peripheral Elements according to IEC 60870-5-101/104."

13.5.6 Redundancy

To increase the availability central stations as well as remote terminal units can be implemented redundantly.
In this section, not the possible redundancy concepts themselves that can be realized are described, rather
only those functions supported by the protocol element (PRE) for the support of redundant systems or
communication routes.
The following redundancy modes are supported:

• 104-Redundancy

• 104-Redundancy “Controlled” with 1 Ethernet Interface

• 104-Redundancy “Controlled” with 2 Ethernet Interfaces

SICAM A8000 Series, CP-8050, Manual 885

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

• 104 redundancy „Controlling“

• PRE-Redundancy

• Port-Redundancy (deactivation of Interface)

• PSI-redundancy (synchronous connections)

• Device redundancy

NOTE

i Only 1 redundancy mode can be used per protocol element (PRE)!

13.5.6.1 104-Redundancy
The "104-Redundancy" is defined in the IEC 60870-5-104 standard.
With 104-redundancy, one or more substations (Controlled Station) are connected to one or more redundant
master stations (Controlling Stations) via several logical connections. The data transfer always takes place via
only 1 started connection per redundancy group.

Redundancy Function according to IEC 60870-5-104:

• The master station (Controlling Station) and the remote terminal unit (Controlled Station) support
multiple "logical connections"

• Multiple logical connections are grouped to form one redundancy group

• Within a redundancy group only 1 logical connection may be started

• Only the master station (Controlling Station) decides which logical connection within a redundancy
group is started

• All logical connections of a redundancy group are monitored by test frames

• One redundancy group is only supplied by one process image (data base)
There is a TCP connection for each redundant Ethernet interface of the remote station and these redundant
connections are combined into a redundancy group. Only one of the redundant connections may be started
by the controlling station and transmit data. At the NIP, the 104-redundancy group can be described like a
switch which controls the sending of data to the started connection.
The 104-redundancy with 2 Ethernet interfaces uses an additional logical switch on the BSE which selects to
which NIP the data to be sent is forwarded, and thus the redundancy group extends over both NIPs and the
BSE.

NOTE

i The 104-redundancy "Controlled with 2 Ethernet interfaces" can only be used within one basic system
element (BSE).
A distribution of 104-redundancy over several BSE's is not supported!

The controlling station switches between the redundant connections. There are two types of redundancy
switching, the "soft switchover" and the "hard switchover".
The soft switchover is applied, e.g. during tests or when a part of the controlling station is to be decommis-
sioned. First, the previously started connection is stopped with a STOPDTact. Only when STOPDTcon has been
received by the controlling station a STARTDTact will be sent from the controlling station to another connec-
tion. This then becomes the new started connection.
The hard switchover occurs primarily when the controlling station detects a connection failure (for example,
a 104 timeout). The controlling station will immediately send a STARTDTact to another connection. This then
becomes the new started connection. If the previously started connection in the controlled station is still

886 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

established at this time (because the controlled station has not yet detected a connection failure), it is immedi-
ately closed.
Several independent redundancy groups are possible. Each connection can be assigned to exactly one redun-
dancy group.
The connection parameterization, the connection state and the redundancy state can be read out from PRE in
the ST emulation with the command "idh".

13.5.6.2 104-Redundancy “Controlled” with 1 Ethernet Interface

The 104-redundancy “Controlled” with 1 Ethernet interface allows the interfacing of a remote station with
redundant Ethernet interfaces over 1 Ethernet network to redundant master stations.
Example for a remote station with redundant interfaces is e.g. one system with two Ethernet interfaces or two
systems that are operated redundantly or a combination of both.

Operating Mode of the 104-Redundancy with 1 Ethernet Interface in the Controlled Station:

• Several redundancy groups can be defined for each PRE

• Each redundancy group consists of one or more "real" connections and exactly 1 "virtual connection" for
the communication to the BSE. The connections of a redundancy group in transmit direction are handled
as one connection (=virtual connection) from the point of view of the communication function on the
BSE.

• A redundancy group may only have a max. of 4 real connections assigned

• The data is transferred from the BSE to the PRE via the "virtual connection" assigned to the redundancy
group. As a result, the connections of a 104 redundancy group for 1 Ethernet interface are supplied from
only one process image (data base).

SICAM A8000 Series, CP-8050, Manual 887

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

• The 104 data transmission is controlled by the controlling station with STARTDT / STOPDT act - only 1
Connection may be started per redundancy group.

• The data is transmitted to the remote station only over the started "real connection" of the 104-redun-
dancy group.

• All stopped connections are established at the TCP level.

• Each connection is monitored with test frames.

• Each connection (and therefore the 104 sequence numbers) is managed independently.

• In receive direction, the data of a 104-redundancy group are transmitted to the BSE with the station
number assigned to the "virtual connection".

• Connections for 104 redundancy and normal connections (without redundancy) can be mixed on the
same PRE.

Parameter settings for the 104-Redundancy with 1 Ethernet Interface in the Controlled Station:

• The parameter [PRE] Redundancy | Redundancy mode must be set to "104-Redundancy" .

• The parameters of the connection definitions [PRE] Station definition (Connection defi-
nition) | Station definition | Station enable must be set to yes .

• For all connections of the 104 redundancy group, the parameter [PRE] Station definition
(Connection definition) | Station definition | Controlling/Controlled must be
set to "controlled" .

• For each 104 redundancy group, a connection must be defined with the parameter [PRE] Station
definition (Connection definition) | Station definition | Redundancy as
"virtual Connection" .
The virtual connection is used only for internal communication with the BSE. This connection is not
present on the LAN (the IP address of the virtual connection is not relevant and will not be used).
Notes:
– "suppress station failure" must not be set for virtual connections!
– only the virtual connection must be included in the topology definition. (including a real connection
of a 104-redundancy group in topology definition will cause buffer overflow)

• All connections of the 104 redundancy groups to the remote stations must be defined with the param-
eter [PRE] Station definition (Connection definition) | Station definition |
Redundancy as "real Connection" .
For the real connections additionally all necessary parameters like IP address of the remote station, ...
must be defined in the parameters of the [PRE] Station definition (Connection defini-
tion) | Station definition .

• With 104-redundancy, a connection can be assigned to one of several redundancy groups. Each redun-
dancy group can be controlled independently of the other 104-redundancy groups. For each 104-redun-
dancy group, the data transmission can be started via 1 of the assigned connections. The redundancy
group is set with parameter [PRE] Station definition (Connection definition) |
Station definition | RedGroup .

• The Stop behavior must be set with parameter [PRE] Station definition (Connection defi-
nition) | Station definition | Stop behavior to "store".

• The function "Clear ring buffer" must be set with parameter [PRE] Station definition (Connec-
tion definition) | Station definition | Clear ring buffer to "no".

• The parameter [PRE] | Redundancy | Station number for received telegrams is not
evaluated.

• If the PRE is switched to "passive" by the redundancy control of the BSE, the transmission of the telegram
"<TI:=103> Clock synchronization command“ can be suppressed with parameter [PRE] | Redundancy
| Send time setting (TI103) if passive .

888 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

• If the PRE is switched to "passive" by the redundancy control of the BSE, the transmission of the telegram
"<TI:=107> Check command with time tag CP56Time2a“ can be suppressed with parameter [PRE] |
Redundancy | Send test command (TI107) if passive .

• The parameter [PRE] | Redundancy | Disable Ethernet-Port if passive must be set to

"no".

13.5.6.3 104-Redundancy “Controlled” with 2 Ethernet Interfaces

The 104-redundancy "Controlled" with 2 Ethernet interfaces enables the redundant interfacing of a compo-
nent as substation to remote stations with redundant Ethernet interfaces via 2 Ethernet networks. Example for
a remote station with redundant interfaces is e.g. one system with two Ethernet interfaces or two systems
that are operated redundantly or a combination of both. This type of redundancy requires two PRE’s on the
same BSE.
In addition to the two redundancy groups on the PRE's there is a "switch" on the BSE, which switches between
the two PRE redundancy groups. The two PRE redundancy groups and the BSE switch work as a single redun-
dancy group.
The CP-8050 internal redundancy control telegrams are not used in the controlled station.

Operating Mode of the 104-Redundancy “Controlled” with 2 Ethernet Interfaces” in the Controlled
Station.
Only the differences or extensions compared to the functionality of the 104-redundancy with 1 Ethernet inter-
face are described here:

SICAM A8000 Series, CP-8050, Manual 889

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

• The data transfer is started by the controlling station with the telegram STARTDTact. For each redundancy
group (which is assigned to two PRE's and the BSE) only 1 connection may be started. i.e. either a real
connection has been started on the Ethernet interface 1 or on the Ethernet interface 2. The data transfer
from the BSE to the PRE takes place only via the "virtualConnection" of the started Ethernet interface. This
supplies the connections of a redundancy group for 2 Ethernet interfaces from only one process image.

• The data transmission to the remote station is done only via the real connection with data transmission
started with STARTDTact.

Parameter settings for the 104-Redundancy “Controlled” with 2 Ethernet Interface in the Controlled
Station.
Only the differences or extensions compared to the functionality of the 104-redundancy with 1 Ethernet inter-
face are described here:

• The virtual connections must be configured identically on both PRE’s (same number of virtual connec-
tions, same assignment to station numbers, same redundancy groups).

• The number of real connections and the station numbers of the real connections may be different on
both PRE's.

• On the PRE, connections for 104-redundancy and normal connections (without redundancy) can only be
parameterized mixed on the primary protocol element.

• For the remaining parameters in 104-redundancy with 2 Ethernet interfaces the same rules apply to
parameter settings as with 104-redundancy with 1 Ethernet interface.

13.5.6.4 104 redundancy „Controlling“

The 104 redundancy "Controlling" enables the interfacing of a central station to one or more remote stations.
One PRE in the central station works as a controlling station. The number of controlling stations depends on
the redundancy configuration and the PRE's can be equipped as required (mixed configurations are also
possible):

• on one BSE

• on various BSE’s within one component

• on various BSE’s in different components

Redundancy switching is controlled by the BSE with the redundancy A/P control message (FC 159, IC 1) - the
entire PRE is switched to passive or active. With redundancy switching, all redundant connections of a PRE are
switched together with STARTDT or STOPDT. It is not possible to switch some connections as started (with
STARTDT) and other connections as stopped (with STOPDT).
The redundancy control logic (active/passive switching) controls all connections that are parameterized as
"104-redundancy controlling:

• PRE is set to “active“:

– 104 data transfer is started with STARTDTact when connection is established.
– should be confirmed by the remote station with STARTDTcon.

• PRE is set to “passive“:

– 104 data transfer is stopped with STOPDTact when connection is established.
– should be confirmed by the remote station with STOPDTcon.
When the START/STOP switchover has been acknowledged with "STARTDTcon / STOPDTcon" from all connec-
tions, a redundancy A/P control acknowledgment message (FC 159, IC 2) is returned to the BSE.

890 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

In the following cases, a connection is not taken into account during redundancy switching and the handling
of the A/P control message acknowledgment (FC 159, IC 2):

• the connection fails (remote device close the connection → IEC 104 Timeout) before a STARTDTcon /
STOPDTcon is received. The A/P control acknowledgment message will be delayed until the remote
station is detected as failed.

• The connection is established during redundancy switchover and started if necessary.

Operating Mode of the 104-Redundancy “Controlling”:

The redundancy control evaluates the criteria for a redundancy switchover and sets the controlling stations
used in the redundancy configuration to started or stopped. Depending on the redundancy group, two to four
controlling stations are possible. A maximum of one controlling station may be started.
After a redundancy switchover the redundancy control logic must wait for the A/P control acknowledgment
message from the PRE before initiating another switchover, otherwise the following behavior may occur:

• Hard switchovers and connection terminations

• Non-IEC 104 compliant behavior

The redundancy control requires additional functionality, which can be implemented as follows:

• SICAM RTUs Redundancy or

• recundancy controlled by logic (CAEx)

SICAM A8000 Series, CP-8050, Manual 891

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

Prosess data message handling between BSE and PRE depends on the redundancy and connection state.
Process data messages to the PRE are, depending on the operating state, fetched and sent, fetched up and
discarded or piled up.
PRE active/passive Connection Handling of Data Note
104-data transfer (Data BSE → PRE)
passive/STOPDT down fetched and discarded • loss of data on this
PRE
passive/STOPDT up fetched and discarded • loss of data on this
PRE

892 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

PRE active/passive Connection Handling of Data Note

104-data transfer (Data BSE → PRE)
aktive/STARTDT down piled up • ring overflow
possible (loss of
data)
• confirmation time-
outs
aktive/STARTDT up fetched and discarded

Process data messages received from the remote station are forwarded without change to the BSE.

Parameter settings for the 104-Redundancy “Controlling”

(valid for all connections with controlling functionality of the 104-redundancy)
The number of connections with controlling redundancy on one NIP is functionally unlimited, all 100 connec-
tions of one NIP can be operated with controlling redundancy (see recommendations in the function over-
view).

• The parameter [PRE] Redundancy | Redundancy mode must be set to 104-Redundancy .

• The parameters of the connection definitions [PRE] Station definition (Connection defi-
nition) | Station definition | Station enable must be set to yes .

• The IEC 60870-5-104 data flow control of the own station (Controlling / Controlled) must be set in the
parameters of the connection definitions with the parameter [PRE] Station definition
(Connection definition) | Station definition | Controlling/Controlled must be
set to controlled.

• The “redundancy“ mode must be set in the parameters of the connection definitions with the parameter
[PRE] Station definition (Connection definition) | Station definition |
Redundancy to 104-Contr-Red.

• In the parameters of the connection definitions the parameter [PRE] Station definition
(Connection definition) | Station definition | RedGroup is not relevant.

• In the parameters of the connection definitions, set the parameter [PRE] Station definition
(Connection definition) | Station definition | Stop behavior to store.

• In the parameters of the connection definitions, set the parameter [PRE] Station definition
(Connection definition) | Station definition | Station failure to notify.

• In the parameters of the connection definitions, set the parameter [PRE] Station definition
(Connection definition) | Station definition | Clear ring buffer to No.

• In addition, all required parameters such as the IP address of the remote station, ... must be parameter-
ized for the connections in the parameters of the [PRE] Station definition (Connection
definition) | Station definition .

• The parameter [PRE] | Redundancy | Station number for received telegrams is not
evaluated.

• If the PRE is switched to "passive" by the redundancy control of the BSE, the transmission of the telegram
"<TI:=103> Clock synchronization command“ can be suppressed with parameter [PRE] | Redundancy
| Send time setting (TI103) if passive .

• If the PRE is switched to "passive" by the redundancy control of the BSE, the transmission of the telegram
"<TI:=107> Check command with time tag CP56Time2a“ can be suppressed with parameter [PRE] |
Redundancy | Send test command (TI107) if passive .

• The parameter [PRE] | Redundancy | Disable Ethernet-Port if passive must be set to

"no".

SICAM A8000 Series, CP-8050, Manual 893

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

13.5.6.5 PRE-Redundancy

With PRE redundancy one remote terminal unit (Controlled Station) is connected with one or several master
stations (Controlling Stations) over several logical connections. The data transmission takes place over all
connections.
The PRE redundancy mode is selected by setting the parameter Connection definition | Redundancy
to none .
The switchover of the redundancy state ("ACTIVE" ↔ "PASSIVE") takes place system-internal through redun-
dancy control messages.

Operating mode of the redundancy control for PRE-redundancy

• There is no difference between redundancy state "ACTIVE/PASSIVE" on the IEC 60870-5-104 interface.

• The data transmission is started by the controlling station for every connection with STARTDTact but not
stopped with redundancy state "PASSIVE".

• The data transmission is carried out on all connections independent of the other connections

• All data transferred from the BSE to the PRE for transmission are transmitted to the remote station even
with the redundancy state "PASSIVE".

• The data transmission is controlled from one specific process image for each connection.

• The switchover to "PASSIVE" takes place globally per PRE and not selectively per connection.

Parameter settings PRE-Redundancy:

• The "PRE-Redundancy" is selected by setting the parameter [PRE] Station definition (Connec-
tion definition) | Station definition | Redundancy to none.

• The parameter [PRE] Redundancy | Redundancy mode must be set to "104-Redundancy" .

• The parameter [PRE] | Redundancy | Station number for received messages is not eval-
uated.

• For all connections of the 104 redundancy group, the parameter [PRE] Station definition
(Connection definition) | Station definition | Controlling/Controlled must be
set to "controlled" .

• In the redundancy state "PASSIVE", the message "<TI=107> check command with time tag CP56Time2a"
can be disabled for transmission by the PRE with the parameter [PRE] | Redundancy | Redun-
dancy | Send test command (TI107) if passive .

• In the redundancy state "PASSIVE", the message "<TI:=103> Clock synchronization command" can be disa-
bled for transmission by the PRE with the parameter [PRE] | Redundancy | Redundancy | Send
time setting (TI103) if passive .

• In the redundancy state "PASSIVE", the Ethernet interface can be deactivated with the parameter [PRE]
Redundancy | Disable Ethernet-Port if passive .

894 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

NOTE

i There is no difference between redundancy state "active / passive" on the IEC 60870-5-104 interface.
When using IEC 104 redundancy “Controlled" and "PRE Redundancy" at the same time, the following must
be observed with the following configuration:
Configuration:

• 2 telecontrol front ends (at one time one is active and one passive).
On each telecontrol front end, 104 redundancy "Controlled" is parameterized.

• 2 SCADA systems with 104 redundancy “Controlling" parameterized.

Each SCADA system has a connection to each telecontrol front end.
What is to be considered:

• In total there are two IEC 104 redundancy groups with two connections each.
For each redundancy group, a connection has been started.

• The IEC 104 redundancy control in the SCADA system must recognize which telecontrol frontend is
active.
e.g.: only the active telecontrol front end send <TI:=103> or <TI:=107> messages.
With this the SCADA system can recognize the active telecontrol frontend.
– in SICAM RTUs telecontrol frontend the sending of messages with <TI:=103> or <TI:=107> can be
disabled in redundancy state “passive”.

13.5.6.6 Port-Redundancy (deactivation of Interface)

For specific redundancy configurations the Ethernet interface can be deactivated.

Activation/deactivation of the Ethernet interface with:

• PST control message

• Redundancy control message

The activation/deactivation of the Ethernet interface with redundancy control message can be enabled with
the parameter [PRE] Redundancy | Disable Ethernet-Port if passive . If the activation/deacti-
vation of the Ethernet interface with redundancy control message is enabled the PST control message can not
be used.
After restart of the PRE the Ethernet-interface is activated per default.
Functions during "Interface DISABLE":

• Ethernet Port will be disabled

(disconnect Ethernet connection; TCP/IP connection will be released)

• no services possible (IEC 60870-5-104, WEB, NTP, remote operation)

Note: behavior is the same as with disconnected LAN cable.

• Warning: "interface DISABLED" (diagnostic message)

• all IEC 60870-5-104 connections will be released after 104 timeouts

13.5.6.7 PSI-Redundancy (Synchronous Connections)

The redundancy mode "PSI-Redundancy (synchronous connections)" is a proprietary function and is only
implemented in plants with a control system (Controlling Station) from the manufacturer "PSI".
This redundancy function is not defined in the IEC 60870-5-104 standard! This redundancy mode is selected
by setting the parameter [PRE] Redundancy | Redundancy mode to PSI-Redundancy and with that is
continuously activated.

SICAM A8000 Series, CP-8050, Manual 895

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

A switchover/control of the redundancy through system-internal redundancy control messages as well as the
redundancy functions of the Controlling Station are not supported for this redundancy mode!
Functioning method of synchronous connections:

• The data is sent over the synchronous connections with the same data content

• The data is sent over the synchronous connections in the same order

• The data is sent over the synchronous connections with the same IEC 60870-5-104 sequence number
The data to the first synchronous connection established is transmitted beginning with the sequence
number "0". The data to other synchronous connections established later is transmitted with the current
consecutive sequence number (the sequence number for received data is individual for each synchro-
nous connection)

• The data is transmitted over the synchronous connections with as little chronological offset as possible

• In receive direction, there is no specific function for synchronous connections – received data is trans-
ferred to the BSE for each synchronous connection

On the LAN/WAN-protocol element, synchronous connections for PSI redundancy and normal connections
(without redundancy) can be used mixed.
For synchronous connections, system internally only 1 virtual connection may be parameterized and at least 2
or more real connections. The synchronous connections form a group – these are handled as one connection
in transmit direction from the perspective of the communications function on the BSE.
The synchronism of the connections is controlled directly by the LAN/WAN-protocol element. The data trans-
ferred from the BSE for transmission to the synchronous connections are duplicated by the LAN/WAN-protocol
element to the assigned connections. Due to the synchronism of the connections during transmission, the
data throughput is defined by the slowest remote station. With acknowledgement required, a further trans-
mission can only then take place when all remote stations have acknowledged.
In transmit direction, on the BSE the data is only routed to the "virtual connection“ and passed on immediately
to the remote station by the LAN/WAN-protocol element without TCP/IP blocking. If the control of the data
transmission is stopped for one connection, the data for this connection are discarded.

896 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

In receive direction, the data is passed on to the BSE either with the station number of the virtual connection
or with the station number of the real connection. The selection of the station number is performed with the
parameter [PRE] | Redundancy | Station number for received telegrams .
On failure of one real connection, this is signaled as failed. On failure of all real connections, in addition the
virtual connection is signaled as failed.
Necessary parameter settings for synchronous connection on the LAN/WAN-protocol element:

• Virtual connection
A selected connection is to be defined as virtual connection in the parameters [PRE] Station defi-
nition (Connection definition) | Station definition | Redundancy .
The virtual connection is used only for internal communication with the BSE. This connection is not
present on the LAN (the IP address of the virtual connection is not relevant and will not be used).
Note:
For connections that are operated without redundancy, the parameter Connection definition |
Redundancy is to be set to "none".

• Synchronous Connections (real connections)

All connections to the connected remote stations that are to be handled as synchronous connections are
to be defined as real connections in the parameters [PRE] Station definition (Connection
definition) | Connection definition | Redundancy .
For the real connections, in addition all necessary parameters of the Connection definition (such as IP
address of the remote station,…) must be parameterized in [PRE] Station definition (Connec-
tion definition) | Connection definition .

• IEC 60870-5-104 Data Flow Control of the own station (Controlling/Controlled)

The data flow control is defined for all synchronous connections together with the parameter [PRE]
Station definition (Connection definition) | Station definition | Control-
ling/Controlled for the virtual connection!
Necessary parameter settings of the communications function/topology on the BSE for synchronous connec-
tions in transmit direction:

• Deactivation of the state compression

• All user data must be assigned to one priority level

• For the failure management, the real connections must be entered in the topology

• For the real connections the disabling of system data must be activated in the topology

• For the failure management of the data in receive direction, the parameter setting of the topology and
the source ID is required

• The virtual connection and all real connections must be parameterized as "Controlled"

• No data may be routed to a real connection

Limitations:

• A special handling for synchronous connections is only implemented in transmit direction!

• Synchronous connections to one SICAM RTUs component must not be used!

• With synchronous connections the remote station may not use Start/Stop for the control of the data
transmission!

• The formation of redundancy groups for synchronous connections is not supported!

• Data in transmit directions must not be routed "to all"!

13.5.7 Message Conversion

Data in transmit direction are transferred from the basic system element (BSE) to the protocol element (PRE) in
the SICAM RTUs internal format. These are converted by the protocol element to the IEC 60870-5-104

SICAM A8000 Series, CP-8050, Manual 897

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

message format on the line and transmitted according to the transmission procedure of the IEC 60870-5-104
protocol.
Data in receive direction are converted on the transmission line by the protocol element from IEC
60870-5-104 format to a SICAM RTUs internal format and transferred to the basic system element.

Object Numbering
All IEC 60870-5-104 message objects are transmitted with an unambiguous IEC 60870-5-104 sequence
number. In one TCP-packet several IEC 60870-5-104 message objects can be transmitted. A blocked IEC
60870-5-104 message (with several individual messages) is handled as one message object.
The sequence number is managed for each connection and is an ascending number in the range 0-32767
(modulus 32768). The sequence number is used for the acknowledgement procedure defined for IEC
60870-5-104.

13.5.7.1 Blocking

For the optimum utilization of the transmission paths, for the data transmission with IEC 608705104 protocols
the "Blocking" according to IEC 60870-5-101/104 is implemented. This function is performed on the basic
system element (BSE) according to the rules applicable for this. Data to be transmitted are thereby already
blocked on the basic system element and passed on to the protocol element for transmission.
With LAN-communication, several messages blocked according to IEC 60870-5-104 can be entered in one TCP-
packet before this is transmitted.
Received data in blocked format according to IEC 60870-5-104 are passed on from the protocol element to the
basic system element in blocked format. On the basic system element the blocked data is split up again into
individual information objects by the detailed routing function and passed on as such to the further
processing. Received messages with maximum length are transmitted SICAM RTUs internal in several blocks to
the basic system element (BSE) because of the additionally required transport information.
The parameters necessary for the blocking are to be set on the basic system element (BSE) in the IEC
60870-5-101/104 parameter block

13.5.7.2 Special Functions

For the coupling to external systems, if necessary the following special functions can be activated for the
adaptation of the message conversion:

• Summer time bit (SU)=0 for all messages in transmit direction

(summer time bit in the time tag)

• Day of week (DOW)=0 for all messages in transmit direction

(day of week in the time tag)

• Time stamp (IV=1) in Messages in Transmit Direction

• Originator address = 0 for all messages in transmit direction

• WhiteList-Filter

• Data Throughput Limitation

• Special functions DBAG

• Special functions RWE

Summer Time Bit = 0 for all Messages in Transmit Direction

With the setting of the parameter [PRE] Station definition (Connection definition) |
Station definition | Summertime to suppress, the summer time bit (SU) in the time tag is always
set to “0" by the protocol element for all messages with time tag in transmit direction.

898 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

Day of Week = 0 for all Messages in Transmit Direction

With the setting of the parameter Connection definition | Day of week to suppress, the day of
the week (DOW) in the time tag is always set to “0” by the protocol for all messages with time tag in transmit
direction.

NOTE

i This function is only active for process information messages in transmit direction.
The day of week in clock synchronization command message is not affected!

Time stamp (IV=1) in Messages in Transmit Direction

If the time synchronization of the own AU fails (i.e. after timeout of free running time or monitoring time for
sync. event), the I bit of the internal system clock will be set in SICAM RTUs. All data with time stamp from
local I/O’s will be sent with IV=1 for time tag. All data with time stamp from remote RTU’s via serial or LAN
based interface will be sent with IV-Bit for time tag from remote RTU.
With the setting of the parameter [PRE] Advanced parameters | Time stamp (IV=1) in
messages in transmit direction , and if the time synchronization of the own AU fails, the protocol
element will send all messages with <TI:=30, 31, 32, …40> in transmit direction with IV=1 for time tag.

NOTE

i In Ax 1703 the I bit of the internal system clock will not be set.
The failure of the time synchronization of the own AU must be sent in Ax 1703 with a protocol element
control message to the protocol element (user error → message conversion → protocol element control
message).

Originator Address = 0 for all Messages in Transmit Direction

With the setting of the parameter [PRE] Station definition (Connection definition) |
Station definition | Originator address to suppress, for all messages in transmit direction the
originator address is always set to “0” by the protocol element.

WhiteList-Filter
Caused by increased using of the norm protocol IEC 60870-5-101/104 in the area of the telecontrol engi-
neering/process automation this protocol is also very often used to exchange data between different providers
(net couplings).
For the protection of the own network and also not send any unwanted telegrams to the remote network, the
data traffic is reduced to the absolutely necessary minimum at such interfaces.
Only defined telegrams (selected by type identification and cause of transmission) will be sent in transmit
direction to the remote network and only defined telegrams will be taken in receive direction at WhiteList-
Filter enabled.

SICAM A8000 Series, CP-8050, Manual 899

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

The WhiteList-Filter can be enabled for each single connection with the parameter [PRE] Station defi-
nition (Connection definition) | Station definition | Profile (type identifica-
tion check) .
Following WhiteList-Filters can be selected: 133

• WhiteList-Filter
– This profile can be used on interfaces between different providers or regions within same provider.
– From the pre-defined WhiteList-Filter only selected type identifications in transmit/receive direction
are passed through (siehe Profile Definition: “WhiteList-Filter“ , Page 902).

• TI-Filter + WhiteList-Filter
– From the pre-defined WhiteList-Filter only selected type identifications are passed through by the TI-
Filter.
– The TI-Filter can be parameterized separately in transmit-/receive direction.
– IEC 60870-5-104 messages with type identifiers are already filtered out by the WhiteList-Filter
cannot be passed through by the TI-Filter.
– IEC 60870-5-104 messages with type identifiers that are filtered out by the TI-Filter are acknowl-
edged to the remote station and then discarded (ACTCON / ACTTERM will not be sent).

133 For profiles additional parameter settings (BSE + PRE) are required! (Profile definitions later in this chapter)

900 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

• TI-Filter
– Only the IEC 60870-5-104 messages with type identifiers selected in the TI-Filter will be passed in
transmit-/receive direction (the cause of transmission is not evaluated).
– The TI-Filter can be parameterized separately in transmit-/receive direction.
– IEC 60870-5-104 messages with type identifiers that are filtered out by the TI-Filter are acknowl-
edged to the remote station and then discarded (ACTCON / ACTTERM will not be sent).

• SICAM RTUs - IEC104 (“SICAM RTUs “Standard“)

– WhiteList-Filter switched off (=Default).
– This profile is typically used for interfacing SICAM RTUs systems within region of same provider.
– All supported type identifications from interoperability [OptUnresolvedLink]Manual CP-8000,
CP-802x[/OptUnresolvedLink] incl. type identifications used by SICAM RTUs in private range (remote
diagnostics, remote configuration,…) will be passed through in transmit-/receive direction.

• IEC 60870-5-104 Ed.2 (“KEMA conformance tested”)

– WhiteList-Filter disabled and data in private range are disabled. This profile will be used if interface
should be used as conformance tested according IEC 60870-5-104 by KEMA.
– Only the supported type identifications from interoperability for SICAM RTUs “Protocol Implementa-
tion Conformance Statement (PICS) - Interoperability of SICAM AK, SICAM TM according to IEC
60870-5-104 (ETA4) as Controlled Station “will be passed through in transmit-/receive irection.
– Type identifications in private range (e.g.: remote diagnostics, remote parameterization,…) will not
be supported! Spontaneous tasks are not supported.

WhiteList-Filter

• the WhiteList-Filter is not an interoperability document!

• the WhiteList-Filter has the same definition in transmit-/receive direction

• Filtered messages in transmit direction will be discarded without error 134

(message will be logged as normal in data flow test)

• Filtered messages in receive direction will be confirmed to remote station and discarded without error 134
(filtered messages cannot be logged in data flow test)

• Special functions for commands:

Command messages with originator address = “0“ will be filtered in case of “COT ≠ 6” or “COT ≠ 8”.
For commands sent with COT=ACT/DEACT, the reply for the command in receive direction with
COT=ACTCON (DEACTCON)/ACTTERM will be passed only in a time window when this command was sent
before wit COT=ACT/DEACT via this interface/connection.
For commands received with COT=ACT/DEACT, the reply for the command in transmit direction with
COT=ACTCON (DEACTCON)/ACTTERM will be passed only in a time window when this command was
received before wit COT=ACT/DEACT via this interface/connection.
The time window is set to 600 seconds and cannot be parameterized.
The WhiteList-Filter function stores for up to 200 commands running at the same time the address for the
command, direction (transmit/receive) and the interface/connection information. After termination of the
command sequence according IEC 60870-5-101/104 standard (ACT→ACTCON→ACTTERM) the stored
command information will be deleted. The stored command information is deleted at a faulty command
sequence after expiry of the time window at the latest.

134 Error will be set for messages with type identifications not supported according WhiteList-Filter definition. No Error will be set for
messages with type identifications supported according WhiteList-Filter definition but with cause of transmission not supported
according WhiteList-Filter definition.

SICAM A8000 Series, CP-8050, Manual 901

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

TI-Filter (“Type Identification Pass Filter”)

The TI-Filter (“Type identification pass filter“) will pass only IEC 60870-5-101/104 messages in transmit-/receive
direction with type identifiers selected in the TI-Filter.
The TI-Filter can be activated with the parameter [PRE] Station definition (Connection defini-
tion) | Station definition | Profile (type identification check) by selecting "TI-
Filter" or "WhiteList-Filter + TI-Filter".

The type identifiers which shall be passed through by the TI filter in the send/receive direction are set with the
parameters [PRE] IEC60870-5-104 | WhiteList-Filter | TI-Filter.

• max. 30 type identifiers can be defined in the TI-Filter. (also TI’s sent during GI and TI’s for system infor-
mation must be defined)

• Each type identifier may only be entered once in the TI-Filter

• For each type identification, you can select in TI-Filter "Type identification pass in":
– Transmit- and Receive direction
– Transmit direction
– Receive direction
.

• The TI-Filter can be parameterized separately in transmit-/receive direction.

• The TI-Filter can be used either selectively or in combination with the WhiteList-Filter.

• If the TI-Filter is used with the WhiteList-Filter, only the IEC60870-5-101/104 messages with type identi-
fiers passsed by the WhiteList-Filter and selected in the TI-Filter will be passed in transmit-/ receive direc-
tion (the cause of transmission is evaluated by the WhiteList-Filter). Not selected TI’s in TI-Filter will be
discarded.

• If the TI-Filter is used without the WhiteList-Filter, only the IEC 60870-5-101 messages with type identi-
fiers selected in the TI-Filter will be passed in transmit-/ receive direction (the cause of transmission will
not be evaluated). Not selected TI’s in TI-Filter will be discarded.

• IEC 60870-5-101 messages, with type identifiers that are filtered out by the TI-Filter in receive direction,
are acknowledged to the remote station and then discarded (ACTCON / ACTTERM will not be sent).

Profile Definition: “WhiteList-Filter“

The following table includes the profile definition for “WhiteList-Filter“ and "WhiteList-Filter for passive
PRE" .

902 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

SICAM A8000 Series, CP-8050, Manual 903

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

Table 13-2 Semantics of cause of transmission:

<0> := not used

<1> := periodic, cyclic
<2> := Background scan
<3> := spontaneous
<4> := initialized
<5> := request or requested
<6> := activation
<7> := Confirmation of activation
<8> := Abortion of activation
<9> := Confirmation of the abortion of activation
<10> := Activation termination
<11> := Return information, caused by a remote command
<12> := Return information, caused by a local command
<13> := File transfer
<14..19> := reserved for further compatible definitions (not used)
<20> := interrogated by station interrogation
<21..36> := interrogated by group 1..16 interrogation
<37> := requested by general counter request
<38..41> := requested by group 1..4 counter request
<42, 43> := reserved for further compatible definitions (not used)
<44> := unknown type identification
<45> := Unknown cause of transmission
<46> := unknown common address of ASDU

904 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

<47> := unknown information object address

<48, 63> := for special use (private range - not used)

Profile Definition "SICAM RTUs – IEC104"

The profile SICAM RTUs – IEC104 (“SICAM RTUs Standard“) defines the functionality according to [OptUnresol-
vedLink]Manual CP-8000, CP-802x[/OptUnresolvedLink]. This profile will be used as standard for interfacing
SICAM RTUs components.

SICAM A8000 Series, CP-8050, Manual 905

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

*) blank or “X“ only

+ secondary application function only
B* can be generated by the PLC
5) transparent transmission by system
6) Reception possible, thereby the blocked single-point information is deblocked and further individ-
ually processed as TI = 30 (address translation occurs algorithmic)
7) Not supported; reply sent with COT=45 „unknown cause of transmission“

Profile Definition "IEC 60870-5-104 Ed.2"

The profile IEC 60870-5-104 Ed.2 (“KEMA Conformance tested“) defines IEC 60870-5-104 Ed. 2 functionality
as conformance tested by KEMA. This profile is used at interfaces required functionality as conformance tested
according IEC 60870-5-104 Ed. 2 by KEMA.
... more details see document “Protocol Implementation Conformance Statement (PICS) - Interoperability of
SICAM AK, SICAM TM according to IEC 60870-5-104 (ETA4) as Controlled Station“

906 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

SICAM A8000 Series, CP-8050, Manual 907

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

*) blank or “X“ only

+ secondary application function only
X* can be generated by the PLC
1) transparent transmission by system

Use Cases
Following function is the same for different sample applications.
When WhiteList-Filter is enabled:

• routing of unwanted message within the system will be stopped

• unwanted messages will not be transmitted

• unwanted messages in receive direction will not be passed through

• ACTCON/ACTTERM for commands will be sent only if this command was received before via this interface

Partner Interface between SICAM RTUs Systems

Data exchange via interface (LAN, serial) between different partners (utilities) – both partners are using SICAM
RTUs systems.

908 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

[whitelist_partnerkopplung_sic_rtus, 1, en_US]

Partner Interface between SICAM RTUs System and 3rd Party System
Data exchange via interface (LAN, serial) between different partners (utilities) – one partner use SICAM RTUs
system the other partner uses a 3rd party system.

[whitelist_partnerkopplung_sic_rtus_fremdsys, 2, en_US]

Internal Segmentation between SICAM RTUs Systems

Data exchange via interface (LAN, serial) between different divisions within the same partner (utility) – both
divisions are using SICAM RTUs systems.

SICAM A8000 Series, CP-8050, Manual 909

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

[whitelist_intern_segm_sic_rtus, 1, en_US]

Internal Segmentation between SICAM RTUs Systems and 3rd Party Systems
Data exchange via interface (LAN, serial) between different divisions within the same customer – one division
uses a SICAM RTUs system the other division uses a 3rd party system.

[whitelist_intern_segm_sic_rtus_fremdsys, 2, en_US]

Redundant SICAM RTUs Automation Units

The WhiteList-Filter is only enabled on the interfaces between the redundant systems. All other interfaces are
not affected.

910 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

Redundant SICAM RTUs Basic System Elements (BSE)

• The WhiteList-Filter disables possible unwanted routing of system messages or messages in the private
range via possible communication loops in redundancy configuration for redundant BSE.
Note: A routing of data messages to redundant BSE will be suppressed per standard by passive BSE.

• The parameter "WhiteList-Filter for passive PRE" must be applied to both BSE.

• The WhiteList-Filter is only activated on “passive” BSE and deactivated on “active” BSE.

SICAM A8000 Series, CP-8050, Manual 911

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

Redundant SICAM RTUs Basic System Elements (BSE’s) – Remote Operation

• The WhiteList-Filter disables possible unwanted routing of system messages via communication loops in
this redundancy configuration

• The parameter "WhiteList-Filter for passive PRE" must be applied to both BSE.

• The WhiteList-Filter is only activated on “passive” BSE.

• The messages from SICAM TOOLBOX II will be discarded by the activated WhiteList- Filter on “passive” BSE
but passed through on “active” BSE by non active WhiteList-Filter.

912 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

Data Throughput Limitation

The protocol element for IEC 60870-5-104 in SICAM RTUs supports a limitation of data throughput in
transmit-/receive direction for IEC 60870-5-104 data messages.
The data throughput limitation is used for the limitation of the data throughput from/to partner or division
interface.
Data Throughput Limitation:

• connection specific parameters

• separate parameters for number of messages/second in transmit-/receive direction

• a message is a selective or blocked IEC 60870-5-104 message (APDU)

• no delay in communication if data throughput is below limit

• data throughput limitation in receive direction in case of exceeded limit by delay of acknowledge
message according IEC 60870-5-104

• data throughput limitation in transmit direction in case of exceeded limit by delay of transmission of IEC
60870-5-104 data messages

SICAM A8000 Series, CP-8050, Manual 913

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

NOTE

i The data throughput limitation works properly only if the IEC 60870-5-104 parameters are set to the same
values on both sides.

Data Throughput Limitation in Transmit Direction

The number of messages/second in transmit direction can be parameterized per connection with the system
technical parameters of the [PRE] Station definition (Connection definition) | Station
definition | Data throughput limit in transmit direction (msg/s) (0 = no data
throughput limitation).
If the number of messages/second for a single connection exceeds the parameterized limit then the data
transmission is stopped for this connection until next second.
A communication error “data throughput in transmit direction” is set if the data throughput has reached
permanently 90% of the parameterized limit within the last 10 minute window.
Data Throughput Limitation in Receive Direction
The number of messages/second in receive direction can be parameterized per connection with the system
technical parameters of the [PRE] Station definition (Connection definition) | Station
definition | Data throughput limit in receive direction (msg/s) (0 = no data
throughput limitation).
If the number of messages/second for a single connection reaches the parameterized limit, the transmission of
the confirmation for the received message will be delayed in a way that limit the number of received
messages in middle at the parameterized limit.
If the delay would cause in exceeding timeout t2 (e.g.: “k” parameter in the remote system is set to a very high
value in relation to parameterized limit) the data throughput limitation will be stopped to avoid connection
failure caused by delayed IEC 60870-5-104 confirmation.
Restriction:
In worst case the number of messages /second in receive direction can be higher by “k” of the remote system
(k=max. number of not confirmed messages = IEC 60870-5-104 parameter).
If the number of messages/second for a single connection exceeds the parameterized limit within a time slot
(1 second) then the number of messages/second for the next time slot(s) will be reduced by the exceeded
number of messages.
A communication error “data throughput in receive direction” is set if the data throughput has reached perma-
nently 90% of the parameterized limit within the last 10 minute window.

Special functions DBAG

For the implementation of the protocol firmware in DBAG projects the following special functions can be acti-
vated:

• Breaker delay in transmit direction

(DBAG-specific special message format <TI=150>)

• Send originator address with settable value

These special functions can be activated with the parameter [PRE] Advanced parameters | Project
specific settings | DBAG functions .
With function activated, messages in the format <TI=33> "32 Bit bit pattern" in the direction basic system
element * protocol element are converted by the protocol element to the DBAG-specific message format
<TI=150> and transmitted.
Messages received in the format <TI=150> are converted by the protocol element to the format <TI=33> "32
Bit bit pattern" and passed on to the basic system element.
In transmit direction <TI=33> "32 Bit pattern" is converted as follows:
Cause of IEC-Parameter Type Identification for Transmission to the Remote Station
Transmission
spontaneous - <TI=150> DBAG-specific format
GI with time (3 octets) <TI=4> Double-point information with time tag

914 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

Cause of IEC-Parameter Type Identification for Transmission to the Remote Station

Transmission
GI with time (7 octets) <TI=31> Double-point information with time tag CP56Time2a
GI without time <TI=3> Double-point information

In receive direction <TI=150> is converted as follows:

Cause of Time Format Type Identification for Transmission to Basic System
Transmission Element
spontaneous, with time (7 octets) <TI=33> Bitstring of 32 bits with time tag CP56Time2a
GI

NOTE

i The format <TI=150> is only defined with 7 bytes time, 3 bytes IOA, 2 bytes CASDU and 2 bytes URS! For
this format no double transmission is defined as format without time tag!

Breaker delay in transmit direction

If the delay of the circuit breaker or the time of the fault current is not available, this time can be added by the
protocol element in messages in transmit direction with the parameter [PRE] Advanced parameters |
Project specific settings | parameter settings for DBAG/PSI | Switch transfer
time in transmit direction .
Message structure <TI=150> "Railway-specific Format" (in the private range)

SICAM A8000 Series, CP-8050, Manual 915

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

Send originator address with settable value

In DBAG projects the originator address in transmit direction is always transferred with a fixed parameterized
value. The originator address is to be set with the parameter [PRE] Advanced parameters | Project
specific settings | parameter settings for DBAG/PSI | Originator address in
transmit direction .
For this function the setting of the number of octets for cause of transmission to "2 octets" is necessary (see
IEC 60870-5-101/104 Parameters on the Basic System Element).

Special Functions RWE

For the implementation of the protocol firmware in RWE projects the following special functions can be acti-
vated:

• Bit by bit marking of the field

• Cyclic measured values

• Address of the return information for selection command 2

• NT-Bit, IV-Bit according to RWE requirements

These special functions can be activated with the parameter [PRE] Advanced parameters | Project
specific settings | RWE functions and are effective for all connections of the LAN/WAN protocol
element.

Bit by bit marking of the field

For RWE switchgear projects, the configuration of the plants is divided into "voltage level", "station number"
and "field".
This structuring is represented on the 5-stage IEC 60870-5-101/104 address of the data.
The definition of which part of the address (CASDU, IOA) the field addresses is carried out in the parameters
[PRE] Advanced parameters | Project specific settings | RWE functions | Bit-
level flag of bay | *.
All set bits in the "Bit by bit marking of the field" define the range of the address of the field. All reset bits in
the mask define the range of the addresses for data points within the fields.
The assignment of the measured values to the fields is determined by the structuring of the address.
For cyclic group 0 measured values, no field-specific functions are implemented on the LAN/WAN protocol
element.
The transmission of cyclic group 2 measured values is activated by field¬-specific selection commands. On the
LAN/WAN protocol element the cyclic measured values are not activated/deactivated by the selection
command itself, rather indirectly by the return information for the selection command.
With the return information for selection command 2, those cyclic group 2 measured values whose address for
the field after masking matches the mask for "Bit by bit marking of the field“ are activated/deactivated for
transmission.
Bit by Bit marking of Address Range for Fields
the Field "Mask"
[HEX] BIN Dec [HEX]
CASDU1 FF 11111111 0-255 [00-FF]
CASDU2 FF 11111111 0-255 [00-FF]
IOA1 00 00000000 --
IOA2 00 00000000 --
IOA3 FC 11111100 252-255 [FC-FF]

916 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

NOTE

i • all bits with "1" in the mask declare the address range of the field

• all bits with "0" in the mask declare the address range of the data points within the field

• the bit by bit marking of the field is always the same for RWE projects!

Example:
Parameterized Return Bit by Bit marking of Addresses of the Return Information deter-
Information Address the Field "Mask" mined by this
[HEX] [BIN] [HEX] BIN Dec [HEX]
CASDU1 00 00000000 FF 11111111 0-255 [00-FF]
CASDU2 00 00000000 FF 11111111 0-255 [00-FF]
IOA1 21 00100001 00 00000000 21
IOA2 56 01010110 00 00000000 56
IOA3 03 00000011 FC 11111100 3,7,11,15,19,…,255 [03,07,0F,13,…,FF]

Cyclic measured values

Measured values can be transmitted cyclic to the remote station from the internal process image by the
protocol element itself. For this special function, the activation of the "RWE-specific functions" and the use of
the selective data flow in SICAM RTUs is required.
For cyclic measured values the following groups are supported:

• Group 0: cyclic measured values with a parameter-settable cycle time

(default cycle time)

• Group 2: cyclic measured values – are only transmitted for selection 2

(high priority cycle time)
Group 2 measured values (PSG measured values) are first transmitted cyclic after activation with the selection
command 2.
The selection of the measured values for the cyclic transmission and the assignment of the measured values to
the group is carried out in the process-technical parameter setting for the selective data flow in SICAM RTUs in
the field "Function group"
Function Group Group Note
0-249 --- No cyclic measured value! (measured value is transmitted spontaneous)
250 0 Cyclic measured value with a parameter-settable cycle time (default cycle time;
typically 3 sec)
251 1 Cyclic measured value – is only transmitted for activation with selection
command 1; not used with LAN/WAN protocol element!
252 2 Cyclic measured value – is only transmitted for activation with selection
command 2 (high priority cycle time; typically 0.5 sec)

NOTE

i The functional groups required for cyclic measured values must not be used for other functions!

The updating of the process image for cyclic measured values takes place during the transmission of sponta-
neous measured values or during general interrogation to the LAN/WAN protocol element – from now on
these measured values are transmitted cyclic (not spontaneous and not with GI) to the remote station.
For the transmission of the cyclic measured values, SICAM RTUs internal (between basic system element and
LAN/WAN protocol element) the message format "<TI:=35> measured value, scaled value with time tag
CP56Time2a" is used.

SICAM A8000 Series, CP-8050, Manual 917

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

Cyclic measured values are always transmitted from the LAN/WAN protocol element to the remote station
without time tag with the message format "<TI:=11> measured value, scaled value" and with the cause of
transmission "cyclic".
The cycle time for the transmission of cyclic measured values can be set with the parameter [PRE]
Advanced parameters | Project specific settings | RWE functions | Cyclic meas-
ured value | Base cycle time and the parameter [PRE] Advanced parameters | Project
specific settings | RWE functions | Cyclic measured value | High priority cycle
time .
The transmission of the cyclic measured values to the remote station takes place with maximum possible
blocking according to IEC 60870-5-104. The blocking for cyclic measured values is performed by the LAN/WAN
communications element itself. The parameters provided for the blocking on the basic system element (BSE)
in the IEC 60870-5-101/104 parameter block are not evaluated.
During the transmission of the cyclic measured values, the transmission of spontaneous data is disabled. All
cyclic measured values are prepared for transmission in one operation at the respective cycle moment.
Limitations:

• max. 2000 cyclic measured values

• Cyclic measured values are only supported in SICAM RTUs with selective data flow

• An address conversion for cyclic measured values is not supported

• Cyclic measured values are only supported for 1 connection

(only to the 1st connection in the detailed routing)

• Cyclic measured values must not be routed to a redundant connection

NOTE

i So that the process data is transmitted with the latest values as fast as possible after a going interface fault,
the function "delete ring with communication failure" is to be deactivated in the communications function
on the basic system element. This setting is therefore necessary, because the general interrogation in the
system is only triggered later and consequently, until the updating of the cyclic measured values, due to
the general interrogation, old values are transmitted to the remote station.

Group 0 measured values

With function enabled, group 0 measured values are always transmitted cyclic. The cycle time can be set with
the parameter [PRE] Advanced parameters | Project specific settings | RWE functions
| Cyclic measured value | Base cycle time .

Group 1 measured values (selection command 1)

Group 1 measured values are not supported!
Group 2 measured values (selection command 2)
Group 2 measured values (PSG measured values) are first transmitted cyclic after activation with the selection
command 2. If the transmission of the measured values is not activated with the selection command 2, these
measured values are not transmitted.
After startup, by default these measured values are not transmitted.
The activation of the group 2 measured values takes place on the LAN/WAN protocol element not directly with
the selection command 2, rather with the return information for the selection command 2.
The cycle time can be set with the parameter [PRE] Advanced parameters | Project specific
settings | RWE functions | Cyclic measured value | High priority cycle time .

Address of the Return Information for Selection Command

The activation of the group 2 measured values does not take place on the LAN/WAN protocol element with the
selection command 2 itself, rather with the return information for the selection command 2. The selection
command is processed in the function diagram of the component according to the RWE requirements and
with successful selection the return information is generated for the selection command 2.

918 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

The selection of the group 2 measured values is supported for all fields, whose address range has been deter-
mined by the "Bit by bit marking of the field".
The address of the return information for the selection command 2 is to be parameterized with the parame-
ters [PRE] Advanced parameters | Project specific settings | RWE functions |
Cyclic measured value | Address of the return information of select command 2 |
*.
As return information address, only those sections of the address are to be parameterized that are not part of
the address range for the field. Consequently, as return information address only the field-internal address is
to be parameterized. The bits of the address which identify the field in the return information address for
selection command 2 are not evaluated by the LAN/WAN protocol element.
For the return information of the selection command 2, SICAM RTUs internal only the message format
"<TI:=30> single-point information with time tag CP56Time2a" is used.
The cyclic transmission of the group 2 measured values is activated with the single-point information state
"ON" and deactivated with the state "OFF".
The selection of the group 2 measured values can be carried out either "Locally" or "Remotely". The return
information for the selection command 2 is only transmitted spontaneously to the remote station with the
cause of transmission "Return information, caused by a remote command" or "Return information, caused by a
local command".
With general interrogation, the return information for the selection command is not transmitted to the remote
station!
The assignment of the measured values to the fields is determined by the structuring of the address for RWE.
With the return information for selection command 2, those cyclic group 2 measured values whose address for
the field after masking matches the mask for "Bit by bit marking of the field“ are activated/deactivated for
transmission.
NT-Bit, IV-Bit according to RWE requirements
For projects for the customer RWE, a special handling can be activated for the NT-bit and the IV-bit of the
quality descriptor of the messages in transmit direction.
If the RWE-specific functions are not activated, the NT-bit and the IV-bit in the messages are transferred to the
remote station unchanged.
If the RWE-specific functions are activated, the special handling for the NT-bit and the IV-bit can be selected
with the parameter [PRE] Advanced parameters | Project specific settings | RWE func-
tions | Convert of the NT bits to the IV bit in transmit direction from the following
options:

• Variant a: (selection = <disabled>)

NT-bit is set to "0", IV-bit is not changed

• Variant b: (selection = <enabled>)

NT-bit is set to "0", IV-bit is set if
NT-bit (internal) or IV-bit (internal) is set

SICAM RTUs internal To Remote Station (Variant a) To Remote Station (Variant b)

NT bit IV bit NT bit IV bit NT bit IV bit
0 x 0 x 0 x
1 x 0 x 0 1
0 0 0 0 0 0
0 1 0 1 0 1
1 0 0 0 0 1
1 1 0 1 0 1

x = optional state, or state is not changed!

SICAM A8000 Series, CP-8050, Manual 919

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

13.5.8 Protocol Element Control and Return Information

This function is used for the user-specific influencing of the functions of the protocol elements.
This function contains two separate independent parts:

• Protocol element control

• Protocol element return information

The Protocol Element Control enables:

• Applicational control of the station interrogation

• Applicational control of ENABLE/DISABLE Ethernet interface

• Setting control location

The Protocol Element Return Information enables:

• Information about the station status/failure to be obtained

• Information to be obtained about the status of the data transfer

Block Diagram

13.5.8.1 Protocol Element Control

Protocol element internal functions can be controlled with protocol element control messages. On the basic
system element, IEC 60870-5-101/104 messages with process information in the control
direction are converted to protocol element control messages and transmitted to the selected protocol
element (see 13.1.4.8 Protocol element control messages).
Supported protocol element control functions: (see 13.1.4.8 Protocol element control messages)
SF Protocol element control function ETI4 FWI4
Control function_(PRE) [LAN] [LAN]
0 "Activate" interface X X
1 "Deactivate" interface X X

920 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

SF Protocol element control function ETI4 FWI4

Control function_(PRE) [LAN] [LAN]
2 Time sync, “OK“ X X
2 Time sync, “NOK“ X X
240 Send (General)-interrogation command (CASDU=All) X X
242 Set control location X X
243 Reset command - -
244 Send (General)-interrogation command (CASDU=selective) X X

Legend:
SF .. Control function_(PRE)

13.5.8.2 Protocol element return information

Protocol element return information are internal status information of the protocol elements which are trans-
mitted spontaneously and in the event of a general interrogation with internal message formats from the
protocol element to the basic system element. On the basic system element, the protocol element responses
(see 13.1.4.9 Protocol element return information) are converted to IEC 60870-5-101/104 messages with
process information in the monitoring direction.
Supported protocol element return informations: (see 13.1.4.9 Protocol element return information)
Protocol element return information Station UMPMI0 UMPSI0
Return information function_(PRE) [Master] [Slave]
• Station Failure 0 to 99 X X
protocol-specific return information 0 0 to 99 X X

• Status DATA TRANSFER (BSE) 135

<0> = data transfer from/to BSE is stopped
<1> = data transfer from/to BSE is started
protocol-specific return information 1 0 to 99 X X

• Status DATA TRANSFER (104-Connection) 136

<0> = IEC 60870-5-104 data transfer is stopped (STOPDTact)
<1> = IEC 60870-5-104 data transfer is started (STARTDTact)

13.5.9 WEB Server

A web server is integrated in the protocol firmware for internal diagnostic information. The web server is part
of basic system element – the PRE specific web pages will be provided by protocol element.
System Firmware Protocol function PRE-specific
web pages
SICAM A8000 Series ETI4 IEC 60870-5-104 ✓
SICAM A8000 CP-8050 FWI4 IEC 60870-5-104 ✓

Supported PRE specific web pages:

PRE specific web page for ETI4 FWI4
■ Overview X X
– Connections X X

135 the state of the “DATA TRANSFER (BSE)” can be changed by the parameter “Stop behavior” and “Failure"” (see connection specific
parameters) and und can be different to the state of “DATA TRANSFER (104 Connection)”.
136 Actual state of “DATA TRANSFER (104 Connection)”.

SICAM A8000 Series, CP-8050, Manual 921

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

PRE specific web page for ETI4 FWI4

– Routing transmit X X
– Routing receive X X
■ Developer Information 137

– Dataflow test 137 X X

– Ethernet capture 137 X X
– Diagnosis (IDR) 137 X X
– Statistic (IDE) 137 X X
– User diagnosis (IDU) X X

NOTE

i • The integrated web server is activated by default.

• The integrated web server should be deactivated for security reasons.

• The values displayed on the web pages indicate the current status when the web page is started. The
values of a website are updated when they change. Some websites require manual updating of the
website for certain functions (“refresh” or “reload this page” in the web browser).

• The web pages will be displayed only in English language.

Enable/disable web server

Start the web server via the SICAM Device Manager or internet browser
Refer to 13.1.4.10 Web server for PRE specific websites.

PRE-specific web page: Overview

On the web page Overview general information of the firmware is displayed.
Field Note
Firmware Name of firmware
Protocol Protocol function
SN Part number of the firmware
Revision Revision of firmwareHardware
Hardware Hardware number (system internal)
Firmware Firmware number (system internal)
Date and time actual date + time of firmware
Region number Region number (system internal)
Component number Component number (system internal)
BSE Basic system element number (system internal)
PRE Protocol element number of the firmware (internal)
Interface Selected Ethernet Interface
Physical Interface Assigned physical interface
IP address Own IP address of the assigned interface
Default gateway Default gateway of the assigned interface
Subnet mask Subnet mask of the assigned interface
MAC Address MAC address of the assigned interface

137 see 13.1.4.10 Web server for PRE specific websites.

922 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

Field Note
Redundancy state Current redundancy status of the firmware:

• Firmware active
• Firmware passive
Redundancy system Current redundancy status of the firmware:

• not used
• A
• B
Firmware state State of the firmware:

• Ready
• startup
• KILL
• not available

[ETI4_SICWEB_Overview, 1, en_US]

PRE-specific web page: Overview - Connections

On the web page Connections information about the status of the connection to the linked remote station
are displayed.
Field Note
Number of stations Number of configured connections for this protocol element
Number of stations connected Number of connections established for this protocol element
Number of stations disconnected Number of cleared connections for this protocol element
Number of prepared stations Number of prepared connections for this protocol element
Station CP-8050 internal station number for this connection
IP address IP address of the remote station for this connection

SICAM A8000 Series, CP-8050, Manual 923

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

Field Note
Port Used TCP port number for this connection.
(2404 = Standard Port Number for IEC 60870-5-104)
Communication state State of the connection:

• ok
• nok
• prepared
Station failure Communication status of this station:

• suppress
• notify
104 data transfer Status IEC 60870-5-104 data transfer:

• started
• stopped
Controlling / controlled IEC 60870-5-104 function of the own station for this connection:

• controlling
• controlled
TCP connection State of the TCP connection for this connection:

• up
• down
TLS Encryption of the connection with TLS:

• not used
• encrypted
• null chiper
Redundancy Used redundancy mode for this connection:

• not used
• real connection
• virtual connection
• 104 controlling redundancy

[ETI4_SICWEB_Connections, 1, en_US]

PRE-specific web page: Overview - Routing Transmit

On the web page Routing Transmit information is displayed for each parameterized data point for monitoring
of measured value changes and measured value adjustment in the transmit direction.

924 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

Field Note
Count Number of all parameterized data points in transmit direction
(total for all stations)
Count measured value Number of parameterized data points for "values" in transmission
direction (total for all stations)
Count error Number of faulty parameterized data points in transmit direction
(total number for all stations)
Error Error number

• ERR = 0 .. No error
• ERR = 1 .. Type identification (TI) not valid
• ERR = 2 .. SICAM RTUs sub-address (=IOA3) not valid
• ERR = 3 .. IEC-address not unique
• ERR = 4 .. Station number faulty
• ERR = 5 .. Type of SIP message address conversion not valid
• ERR = 10 .. Parameter not valid: X_0 greater or equal X_100
• ERR = 11 .. Parameter not valid: Y_0 greater or equal Y_100
• ERR = 12 .. Wrong parameters for adaptation for TI35
• ERR = 13 .. Wrong parameters for adaptation for TI34
• ERR = 14 .. Threshold not valid
• ERR = 15 .. Neither adaption nor threshold parametrized
TI IEC 60870-5-101/104 type identification of the data point
CASDU1, CASDU2 IEC 60870-5-101/104 address of the data point
IOA1, IOA2, IOA3
Station CP-8050 internal station number for this connection

Routing Transmit (text filter not used)

All parameterized data points for monitoring of measured value changes and measured value adaption in the
sending direction are displayed. An error number (Error <> 0) is displayed for incorrect data points.

[ETI4_SICWEB_Routing_Transmit, 1, en_US]

SICAM A8000 Series, CP-8050, Manual 925

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

Routing Transmit - with text filter

• The filter affects all fields of the table.

•
The filter is activated with .

• The display is updated immediately when the filter is changed.

[ETI4_SICWEB_Routing_Transmit_Filter, 1, en_US]

PRE-specific web page: Overview - Routing Receive

On the web page Routing Receive information is displayed for each parameterized data point for monitoring
of measured value changes and measured value adjustment in the receive direction.
Field Note
Count Number of all parameterized data points in receive direction
(total for all stations)
Count measured value Number of parameterized data points for "values" in receive
direction (total for all stations)
Count error Number of faulty parameterized data points in receive direction
(total number for all stations)
Error Error number

• ERR = 0 .. No error
• ERR = 1 .. Type identification (TI) not valid
• ERR = 2 .. SICAM RTUs sub-address (=IOA3) not valid
• ERR = 3 .. IEC-address not unique
• ERR = 4 .. Station number faulty
• ERR = 5 .. Type of SIP message address conversion not valid
• ERR = 10 .. Parameter not valid: X_0 greater or equal X_100
• ERR = 11 .. Parameter not valid: Y_0 greater or equal Y_100
• ERR = 12 .. Wrong parameters for adaptation for TI35
• ERR = 13 .. Wrong parameters for adaptation for TI34
• ERR = 14 .. Threshold not valid
• ERR = 15 .. Neither adaption nor threshold parametrized
TI IEC 60870-5-101/104 type identification of the data point
CASDU1, CASDU2 IEC 60870-5-101/104 address of the data point
IOA1, IOA2, IOA3
Station CP-8050 internal station number for this connection

926 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

Routing Receive (text filter not used)

All parameterized data points for monitoring of measured value changes and measured value adaption in the
receive direction are displayed. An error number (<> 0) is displayed for incorrect data points.

[ETI4_SICWEB_Routing_Receive, 1, en_US]

Routing Receive - with text filter

• The filter affects all fields of the table.

•
The filter is activated with .

• The display is updated immediately when the filter is changed.

[ETI4_SICWEB_Routing_Receive_Filter, 1, en_US]

PRE-specific web page: Developer Information – User Diagnosis (IDU)

On the web page Developer Information – User Diagnosis (IDU) PRE-internal user diagnostic information
and the status of the software test points are displayed.

SICAM A8000 Series, CP-8050, Manual 927

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

[ETI4_SICWEB_IDU, 1, en_US]

With Clear user diagnosis (manual reload necessary) the recorded user diagnostic entries are
deleted from the display (the website must be updated manually to update the display).

928 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

With Snapshot the current logged user diagnosis entries are saved internally and can be accessed

with Download on the PC and stored as a text file.

The text file can be opened with e.g. a text editor or sent by email for analysis.

[idu, 1, en_US]

13.5.10 Interoperability IEC 60870-5-104 (ETI4, FWI4)

This companion standard presents sets of parameters and alternatives from which subsets must be selected to
implement particular telecontrol systems. Certain parameter values, such as the choice of “structured“ or
“unstructured“ fields of the INFORMATION OBJECT ADDRESS of ASDUs represent mutually exclusive alterna-
tives. This means that only one value of the defined parameters is admitted per system. Other parameters,
such as the listed set of different process information in command and in monitor direction allow the specifi-
cation of the complete set or subsets, as appropriate for given applications. This clause summarizes the
parameters of the previous clauses to facilitate a suitable selection for a specific application. If a system is
composed of equipment stemming from different manufacturers it is necessary that all partners agree on the
selected parameters.

SICAM A8000 Series, CP-8050, Manual 929

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

The interoperability list is defined as in IEC 60870-5-101 and extended with parameters used in this standard.
The text descriptions of parameters which are not applicable to this companion standard are strike-through
(corresponding check box is marked black).
NOTE: In addition, the full specification of a system may require individual selection of certain parameters for
certain parts of the system, such as the individual selection of scaling factors for individually addressable
measured values.

The selected parameters should be marked in the white boxes as follows:

Function or ASDU is not used

Function or ASDU is used as standardized (default)

Function or ASDU is used in reverse mode

Function or ASDU is used in standard and reverse mode

The possible selection (blank, X, R, or B) is specified for each specific clause or parameter.
A black check box indicates that the option cannot be selected in this companion standard.

13.5.10.1 System or device function

(system-specific parameter, indicate the system’s or station’s function by marking one of the following with
"X")

System definition

Controlling Station (Master)

Controlled Station (Slave)

13.5.10.2 Network configuration

(network-specific parameter, all configurations that are used are to be marked "X")

Point-to-Point Multipoint-partyline

Multiple Point-to-Point Multipoint-star

13.5.10.3 Physical layer

(network-specific parameter, all interfaces and data rates that are used are to be marked "X")

930 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

Transmission speed (control direction)

Unbalanced Unbalanced Balanced

interchange Circuit V.24/ interchange Circuit V.24/ interchange CircuitX.24/
V.28 V.28 X.27
Standard Recommended if >1200
bit/s

100 bit/s 2 400 bit/s 2 400 bit/s 56 000 bit/s

200 bit/s 4 800 bit/s 4 800 bit/s 64 000 bit/s

300 bit/s 9 600 bit/s 9 600 bit/s

600 bit/s 19 200 bit/s

1 200 bit/s 38 400 bit/s

Transmission speed (monitor direction)

Unbalanced Unbalanced Balanced

interchange Circuit V.24/ interchange Circuit V.24/ interchange Circuit X.24/
V.28 V.28 X.27
Standard Recommended if >1200
bit/s

100 bit/s 2 400 bit/s 2 400 bit/s 56 000 bit/s

200 bit/s 4 800 bit/s 4 800 bit/s 64 000 bit/s

300 bit/s 9 600 bit/s 9 600 bit/s

600 bit/s 19 200 bit/s

1 200 bit/s 38 400 bit/s

13.5.10.4 Link Layer

(network-specific parameter, all options that are used are to be marked "X") Specify the maximum frame
length. If a non-standard assignment of class 2 messages is implemented for unbalanced transmission, indi-
cate the Type ID and COT of all messages assigned to class 2.)
Frame format FT 1.2, single character 1 and the fixed time out interval are used exclusively in this companion
standard.

Link transmission procedure Address filed of the link

Balanced transmission not present (balanced transmission only)

Unbalanced transmission 1 Octet

2 Octets

SICAM A8000 Series, CP-8050, Manual 931

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

structured

unstructured

Frame length

Maximum length L (control direction)

Maximum length L (monitor direction)

Time period in which repetitions are allowed (Trp) or number of repetitions

When using an unbalanced link layer, the following ASDU types are returned in class 2 messages (low priority)
with the indicated causes of transmission:

The standard assignment of ASDUs to class 2 messages is used as follows:

Type Identification Cause of transmission

9, 11, 13, 21 <1>

A special assignment of ASDUs to class 2 messages is used as follows:

Type identification Cause of transmission

NOTE: In response to a class 2 poll, a controlled station may respond with class 1 data when there is no class 2
data available.

13.5.10.5 Application Layer

Transmission mode for application data

Mode 1 (Least significant octet first), as defined in clause 4.10 of IEC 60870-5-4, is used exclusively in this
companion standard.

Common address of ASDU

(system-specific parameter, all configurations that are used are to be marked "X")

1 Octet 2 Octets

Address of the information object

(system-specific parameter, all configurations that are used are to be marked "X")

1 Octet structured

2 Octets unstructured

3 Octets

932 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

Cause of transmission
(system-specific parameter, all configurations that are used are to be marked "X")
2 Octets (with originator address)
1 Octet
Only originator address not used (=0) is used

Length of APDU
(system-specific parameter, specify the maximum length of the APDU per system)
The maximum length of the APDU in both transmission directions is 253. This is a fixed system parameter.
Length of APDU
Maximum length of APDU per system in control direction
Maximum length of APDU per system in monitoring direction

Selection of standard ASDUs

Process information in monitor direction

(station-specific parameter, mark each Type ID "X" if function is only used in the standard direction, "R" if only
used in the reverse direction, and "B" if used in both directions)

<1> := Single-point information M_SP_NA_1

<2> := Single-point information with time tag M_SP_TA_1

<3> := Double-point information M_DP_NA_1

<4> := Double-point information with time tag M_DP_TA_1

<5> := Step position information M_ST_NA_1

<6> := Step position information with time tag M_ST_TA_1

<7> := Bitstring of 32 bit M_BO_NA_1

<8> := Bitstring of 32 bit with time tag M_BO_TA_1

<9> := Measured value, normalized value M_ME_NA_1

<10> := Measured value, normalized value with time tag M_ME_TA_1

<11> := Measured value, scaled value M_ME_NB_1

<12> = Measured value, scaled value with time tag M_ME_TB_1

<13> := Measured value, short floating point number M_ME_NC_1

<14> := Measured value, short floating point number with time tag M_ME_TC_1

<15> := Integrated totals M_IT_NA_1

<16> := Integrated totals with time tag M_IT_TA_1

<17> := Event of protection equipment with time tag M_EP_TA_1

SICAM A8000 Series, CP-8050, Manual 933

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

<18> := Packed start events of protection equipment with time tag M_EP_TB_1

<19> := Packed output circuit information of protection equipment with time tag M_EP_TC_1

<20> := Packed single-point information with status change detection M_PS_NA_1 M_PS_NA_1

<21> := Measured value, normalized value without quality descriptor M_ME_ND_1

<30> := Single-point information with time tag CP56Time2a M_SP_TB_1

<31> := Double-point information with time tag CP56Time2a M_DP_TB_1

<32> := Step position information with time tag CP56Time2a M_ST_TB_1

<33> := Bitstring of 32 bits with time tag CP56Time2a M_BO_TB_1

<34> := Measured value, normalized value with time tag CP56Time2a M_ME_TD_1

<35> := Measured value, scaled value with time tag CP56Time2a M_ME_TE_1

<36> := Measured value, short floating point number with time tag CP56Time2a M_ME_TF_1

<37> := Integrated totals with time tag CP56Time2a M_IT_TB_1

<38> := Event of protection equipment with time tag CP56Time2a M_EP_TD_1

<39> := Packed start events of protection equipment with time tag CP56Time2a M_EP_TE_1

<40> := Packed output circuit information of protection equipment with time tag
M_EP_TF_1
CP56Time2a

In this companion standard only the use of the set <30> – <40> for ASDUs with time tag is permitted.
6) Reception possible, thereby the blocked single-point information is deblocked and further individually
processed as TI = 30 (address translation occurs algorithmic).

Process information in control direction

(station-specific parameter, mark each Type ID "X" if function is only used in the standard direction, "R" if only
used in the reverse direction, and "B" if used in both directions)

<45> := Single command C_SC_NA_1

<46> := Double command C_DC_NA_1

<47> := Regulating step command C_RC_NA_1

<48> := Set point command, normalized value C_SE_NA_1

<49> := Set point command, scaled value C_SE_NB_1

<50> := Set point command, short floating point number C_SE_NC_1

<51> := Bitstring of 32 bit C_BO_NA_1

<58> := Single command with time tag CP56Time2a C_SC_TA_1

934 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

<59> := Double command with time tag CP56Time2a C_DC_TA_1

<60> := Regulating step command with time tag CP56Time2a C_RC_TA_1

<61> := Set point command, normalized value with time tag CP56Time2a C_SE_TA_1

<62> := Set point command, scaled value with time tag CP56Time2a C_SE_TB_1

<63> := Set point command, short floating point with time tag CP56Time2a C_SE_TC_1

<64> := Bitstring of 32 bits with time tag CP56Time2a C_BO_TA_1

Either the ASDUs of the set <45> - <51> or of the set <58> - <64> are used.

System information in monitoring direction

(station-specific parameter, mark each Type ID "X" if function is only used in the standard direction, "R" if only
used in the reverse direction, and "B" if used in both directions)

<70> := End of initialization M_EI_NA_1

System information in control direction

(station-specific parameter, mark each Type ID "X" if function is only used in the standard direction, "R" if only
used in the reverse direction, and "B" if used in both directions)

<100> := Interrogation command C_IC_NA_1

<101> := Counter interrogation command C_CI_NA_1

<102> := Read command C_RD_NA_1

<103> := Clock synchronization command C_CS_NA_1

<104> := Test command C_TS_NA_1

<105> := Reset process command C_RP_NA_1

<106> := Delay acquisition command C_CD_NA_1

<107> := Test command with time tag CP56time2a C_CD_NA_1

X** … supported but not recommended (bad accuracy)

Parameter in control direction

(station-specific parameter, mark each Type ID "X" if function is only used in the standard direction, "R" if only
used in the reverse direction, and "B" if used in both directions)

<110> := Parameter of measured value, normalized value P_ME_NA_1

<111> := Parameter of measured value, scaled value P_ME_NB_1

<112> := Parameter of measured value, short floating P_ME_NC_1

<113> := Parameter activation P_AC_NA_1

4) … Not used in IEC 60870-5-104 Edition 2. No use case.

SICAM A8000 Series, CP-8050, Manual 935

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

File transfer
(station-specific parameter, mark each Type ID "X" if function is only used in the standard direction, "R" if only
used in the reverse direction, and "B" if used in both directions)

<120> := File ready F_FR_NA_1

<121> := section ready F_SR_NA_1

<122> := Call directory, select file, call file, call section F_SC_NA_1

<123> := last section, last segment F_LS_NA_1

<124> := Ack file, ack section F_AF_NA_1

<125> := Segment F_SG_NA_1

<126> := Directory {blank or X, only available in monitor (standard) direction} F_DR_TA_1

<127>:= QueryLog – Request for an archive file F_SC_NB_1

Type identifier and Cause of Transmission Assignments

(station-specific parameter)
Shaded boxes are not required.
Black boxes are not permitted in this companion standard
Blank = Function or ASDU is not used.
Mark Type Identification/Cause of transmission combinations:
"X" if only used in the standard direction,
"R" if only used in the reverse direction,
"B" if used in both directions.

936 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

[Type_Identification_1, 1, en_US]

SICAM A8000 Series, CP-8050, Manual 937

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

[Type_Identification_2, 1, en_US]

938 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

[Bedeutung_Übertragunsursachen, 1, en_US]

13.5.10.6 Basic application functions

Station Initialization
(station-specific parameter, mark "X" if function is used)

Station Initialization

Cyclic data transmission

(station-specific parameter, mark each Type ID "X" if function is only used in the standard direction, "R" if only
used in the reverse direction, and "B" if used in both directions)

Cyclic data transmission

Read procedure
(station-specific parameter, mark each Type ID "X" if function is only used in the standard direction, "R" if only
used in the reverse direction, and "B" if used in both directions)

Read procedure

Spontaneous transmission
(station-specific parameter, mark each Type ID "X" if function is only used in the standard direction, "R" if only
used in the reverse direction, and "B" if used in both directions)

Spontaneous transmission

Double transmission of information objects with cause of transmission spontaneous

(station-specific parameter, mark each information type "X" where both a Type ID without time and corre-
sponding Type ID with time are issued in response to a single spontaneous change of a monitored object)

SICAM A8000 Series, CP-8050, Manual 939

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

The following type identifications may be transmitted in succession caused by a single status change of an
information object. The particular information object addresses for which double transmission is enabled are
defined in a project-specific list.

Single-point information M_SP_NA_1, M_SP_TA_1, M_SP_TB_1 and M_PS_NA_1

Double-point information M_DP_NA_1, M_DP_TA_1 and M_DP_TB_1

Step position information M_ST_NA_1, M_ST_TA_1 and M_ST_TB_1

Bitstring of 32 bit M_BO_NA_1, M_BO_TA_1 and M_BO_TB_1 (if defined for a specific project)

Measured value, normalized value M_ME_NA_1, M_ME_TA_1, M_ME_ND_1 and M_ME_TD_1

Measured value, scaled value M_ME_NB_1, M_ME_TB_1 and M_ME_TE_1

Measured value, short floating point value M_ME_NC_1, M_ME_TC_1 and M_ME_TF_1

Station Interrogation
(station-specific parameter, mark "X" if function is only used in the standard direction, "R" if only used in the
reverse direction, and "B" if used in both directions)

Global

group 1 group 7 group 13

group 2 group 8 group 14

group 3 group 9 group 15

group 4 group 10 group 16

group 5 group 11

Information Object
group 6 group 12
Addresses assigned to each
group must be shown in a
separate table.

Clock synchronization
(station-specific parameter, mark "X" if function is only used in the standard direction, "R" if only used in the
reverse direction, and "B" if used in both directions)

Clock synchronization

Day of week used

RES1, GEN (time tag substituted/ not substituted) used

SU-bit (summertime) used

B** supported but not recommended (bad accuracy) By default time synchronization is done by NTP/SNTP

Optional, see 10.5.8.6

940 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

Command transmission
(object-specific parameter, mark "X" if function is only used in the standard direction, "R" if only used in the
reverse direction, and "B" if used in both directions)

Direct command transmission

Direct set point command transmission

"Select and execute" command

"Select and execute" set point command

C_SE ACTTERM used

No additional definition

Short pulse duration (duration determined by a system parameter in the outstation)

Long pulse duration (duration determined by a system parameter in the outstation)

Persistent output

B* can be used only when the COT is generated via a function plan application (CAEx)

Supervision of maximum delay in command direction of commands and set point commands

Maximum allowable delay of commands and set point commands

Transmission of integrated totals

(station- or object-specific parameter, mark "X" if function is only used in the standard direction, "R" if only
used in the reverse direction, and "B" if used in both directions)

Mode A: Local freeze with spontaneous transmission

Mode B: Local freeze with counter interrogation

Mode C: Freeze and transmit by counter interrogation commands

Mode D: Freeze by counter interrogation command, frozen values reported spontaneously

Counter read

counter freeze without reset

Counter freeze with reset

counter reset

General request counter

counter interrogation group 1

SICAM A8000 Series, CP-8050, Manual 941

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

counter interrogation group 2

counter interrogation group 3

counter interrogation group 4

Parameter loading 138

(object-specific parameter, mark "X" if function is only used in the standard direction, "R" if only used in the
reverse direction, and "B" if used in both directions)

Threshold value

Smoothing factor

Low limit for transmission of measured value

High limit for transmission of measured value

Parameter activation
(object-specific parameter, mark "X" if function is only used in the standard direction, "R" if only used in the
reverse direction, and "B" if used in both directions)

act/deact of persistent cyclic or periodic transmission of the addressed object

Test procedure
(station-specific parameter, mark "X" if function only used in standard direction, "R" if only used in the reverse
direction, and "B" if used in both directions)

Test procedure

file transfer
(station-specific parameter, mark "X" if function is used)

File transfer in monitor direction

Transparent file

Transmission of disturbance data of protection equipment

Transmission of sequences of events

Transmission of sequences of recorded analog values

File transfer in control direction

Transparent file

X* Data can be transparently transported by the system but not generated or evaluated. A maximum of
220 bytes of user data can be transported in a segment telegram for file transfer.

138 Not supported with "Controlled Function"

942 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020
 Communication Protocols
13.5 IEC 60870-5-104

Background scan
(station-specific parameter, mark "X" if function is only used in the standard direction, "R" if only used in the
reverse direction, and "B" if used in both directions)

Background scan

Note: used for data which are transmitted caused by a self-initiated general interrogation

Acquisition of transmission delay

(station-specific parameter, mark "X" if function is only used in the standard direction, "R" if only used in the
reverse direction, and "B" if used in both directions)

Acquisition of transmission delay

Definition of time outs

Parameters Default Value Note Selected value

t0 30 s Time-out of connection establishment
t1 15 s Time-out of send or test APDUs
t2 10 s Time-out for acknowledges in case of no
data messages t2<t1
t3 20 s Time-out for sending test frames in case of a
long idle state t3>t1

Maximum range of values t0 to t2 : 1 to 255 s, accuracy 1 s

Recommended range of values t3 : 0 s to 48 h, accuracy 1 s
Large range of values t3 are needed in special cases, where satellite or dial-up connections are used (for
example, with only daily or weekly connection setup for data transmission).

Maximum numbers of outstanding l format frames k and latest acknowledge

Parameters Default Value Note Selected value

k 12 APDUs Maximum difference receive sequence
number to send state variable
w 8 APDUs Latest acknowledge after receiving w I-
format APDUs

Maximum range of value k k: 1 to 32 767 (215 – 1) APDU, accuracy 1 APDU. 139

Maximum range of value w: 1 to 32 767 APDU, accuracy 1 APDU (Recommendation: w should not exceed 2/3
of k). 139
Port number
Parameters Value Note
Port number 2404 In all cases

Redundant Connections

Number N connections used in redundancy group

139 SICAM A8000 supports only 1 to 128 APDUs

SICAM A8000 Series, CP-8050, Manual 943

DC8-026-2, Edition 11.2020
Communication Protocols
13.5 IEC 60870-5-104

RFC 2200 suite

RFC 2200 is an official Internet Standard which describes the state of standardization of protocols used in the
Internet as determined by the Internet Architecture Board (IAB). It offers a broad spectrum of actual standards
used in the Internet. The suitable selection of documents from RFC 2200 defined in this standard for given
projects has to be chosen by the user of this standard.

Ethernet 802.3

Serial X.21 interface

Other selection from RFC 2200

List of valid documents from RFC 2200

1. ………………………………………
2. ………………………………………
3. ………………………………………
4. ………………………………………
5. ………………………………………
6. ………………………………………
7. etc.

944 SICAM A8000 Series, CP-8050, Manual

DC8-026-2, Edition 11.2020