Power Grids

RTU500 series - Remote Terminal Units

Host Communication Interface with IEC
60870-5-101
Protocol description
Revision

Document identity: 1KGT 150 466 V024 1

Revision: Date: Changes:
0 11/2000 New document
1 02/2001 Chapter 12 added
Counter Interrogation Command added
Interoperability list actualized
2 04/2002 Chapter Dial up added
3 11/2002 Chapter File transfer updated
Chapter Transparent Data added
4 10/2003 Chapter Line Redundancy added
Chapter AI Parameter Download added
New redundant Time Synchronization Mode
Two step commands allowed for RCO and ASO/DSO
New System Events introduced
5 08/2004 New System Events introduced
New Line Parameter for SEV and Commands
Cause of Transmission one or two octets
Interoperability List extended
6 02/2005 New System Event (SEV) #100
7 04/2006 Counter Interrogation Command C_CI_NA_1 is now supporting
counter groups
Reset Process Command C_RP_NA_1 will be routed to subdevice
interfaces
New System Events (SEV)
New function: System Single Commands (SSC)
8 06/2006 New: Double transmission of information objects
Deactivate Command C_RP_NA_1 explained
9 07/2007 Chapter Request for access demand added (function available in
Release higher than 8.1)
10 08/2007 New System Events introduced
Interoperability list corrected and updated
Parameter for C_IC_NA_1 / C_CI_NA_1 corrected
Support of COT 44 to 47 for commands GI initialized by PLC pro-
gram
11 06/2009 Chapter Physical Layer modified
Transparent data channel Modbus protocol
Chapter Redundant communication lines extended
Parameter In Use introduced
Setpoint with termination message
Background cycle introduced
Interlock with local control authority
Originator address configurable (2 octets)
System events, System single commands
Max. 16 Host Interfaces
New Line Parameter New ASDU: C_SE_NC_1, P_ME_NA_1
Chapter Dial up updated
Document identity: 1KGT 150 466 V024 1
Revision: Date: Changes:
Group Interrogation introduced
<106> Delay Acquisition Command
12 10/2009 Correction Dial up Parameters
Carrier Trailing Time added in Table Communication Parameter - IEC
60870-5-101
System Events updated
13 03/2011 System Command #012 'Global process image update'

New chapter 'Force process update image'

14 07/2011 New ASDU: P_ME_NC_1
Chapter "Parameter Loading" revised
Chapter “FILE TRANSFER” extended
15 11/2011 Update chapter 7.1.2
16 12/2011 New layout
17 04/2015 New parameter: 'Allow only one interrogation running per common
address of ASDU (PR#16851)
Update file transfer to RCD configuration files (PR#20418)
More details on command qualifiers (PR#17056)
New chapter: Application layer - communication queue handling
(PR#3251)
Update: usage of orginator adress parameter (PR#11465)
Correction: value ranges of dial-up parameters (PR#21617)
Correction: qualifier of command for BSO (PR#23928)
Update chapter system events and system commands
New layout
18 11/2016 Added footnote to table 'ASDU in monotoring direction' (PR#29542)
01/2017 Update: Table 'Conversion of values' for DPI in monitoring direction
(PR#33212)
AMI/MFI 'Background cycle': added cycle time 15 min (PR#27626)
03/2017 Update: 'Redundant communication lines' in Chapter 'Link Lay-
er' (PR#32834)
19 06/2017 Update: Chapter 'Parameter Loading' and 'Interoperability
List' (PR#32754)
07/2017 Update: Chapter 'Application Layer General' Parameter 'Protocol edi-
tion' (PR#34995)
09/2017 Update chapter Link Layer - General: changed cycle time offline
supervision from "is set to off" to "120 s by default" (PR#35094)
20 08/2018 New layout
Introduced new parameter 'Put in buffer' (PR#35074)
21 01/2019 Updated document for KEMA conformance test (PR#40073, #41050)
02/2019 Introduced new system events #031 and #032 (PR#40633)
Introduced new parameter 'Unstable event filter' for DPI and SPI
(PR#40630)
22 05/2019 Renamed default value of parameter 'Protocol profile' (PR#41697)
06/2019 Set default of parameter 'Routed diagnosis support' to disabled
(PR#42528)
Document identity: 1KGT 150 466 V024 1
Revision: Date: Changes:
10/2019 Updated chapter 'Communication Queue Handling': Added descrip-
tion about new feature of 75 % buffer fill level as system event
(PR#43793)
23 02/2020 Corrected message of system event #174 (PR44658)
24 03/2020 Updated description of parameter 'Acknowledge Commands on
reception' (PR#44929)
Contents

Contents

1 Introduction............................................................................................................................. 7
1.1 Preface........................................................................................................................... 7
1.2 References..................................................................................................................... 7
1.3 Conventions................................................................................................................... 7

2 Physical Layer.........................................................................................................................9
2.1 Serial line-based communication...................................................................................9
2.2 Host interface.................................................................................................................9

3 Link Layer..............................................................................................................................11
3.1 General.........................................................................................................................11
3.2 Unbalanced Mode........................................................................................................12
3.3 Balanced mode............................................................................................................ 12
3.4 Dial-up function............................................................................................................ 13
3.4.1 General........................................................................................................ 13
3.4.2 Dial-up configuration....................................................................................13
3.4.3 Request for Access Demand...................................................................... 15
3.5 Redundant communication lines................................................................................. 16
3.5.1 Unbalanced mode........................................................................................16
3.5.2 Balanced mode............................................................................................18

4 Application Layer..................................................................................................................21
4.1 General.........................................................................................................................21
4.2 Communication Queue Handling.................................................................................22
4.3 ASDU Type identification.............................................................................................24
4.3.1 ASDU in monitoring direction...................................................................... 24
4.3.2 ASDU in control direction............................................................................ 25
4.3.3 ASDU of system information in command direction....................................25
4.3.4 ASDU for file transfer.................................................................................. 26

5 Parameters and Addressing................................................................................................27

5.1 Address elements........................................................................................................ 27
5.1.1 Restrictions for the link address..................................................................27
5.1.2 Restrictions for the Common Address........................................................ 27
5.1.3 Restrictions for the information object address........................................... 28
5.2 General data point parameters....................................................................................28

6 Data Types - Monitoring Direction......................................................................................29

6.1 AMI – Analog Measured Information...........................................................................29
6.1.1 Supported Data Types.................................................................................29
6.1.2 Additional Information.................................................................................. 29
6.1.3 Conversion of Values...................................................................................30
6.1.4 Conversion of Quality Descriptors...............................................................30
6.1.5 Conversion of Causes of Transmission.......................................................31
6.2 BSI – Bit String Information.........................................................................................31
6.2.1 Supported Data Types.................................................................................31

1KGT 150 466 V024 1 I

 Contents

6.2.2 Additional Information.................................................................................. 31

6.2.3 Conversion of values...................................................................................32
6.2.4 Conversion of Quality Descriptors...............................................................32
6.2.5 Conversion of Causes of Transmission.......................................................32
6.3 DMI – Digital Measured Information............................................................................32
6.3.1 Supported Data Types.................................................................................33
6.3.2 Additional Information.................................................................................. 33
6.3.3 Conversion of values...................................................................................33
6.3.4 Conversion of Quality Descriptors...............................................................33
6.3.5 Conversion of Causes of Transmission.......................................................34
6.4 DPI – Double Point Information.................................................................................. 34
6.4.1 Supported Data Types.................................................................................34
6.4.2 Additional Information.................................................................................. 34
6.4.3 Conversion of Values...................................................................................35
6.4.4 Conversion of Quality Descriptors...............................................................35
6.4.5 Conversion of Causes of Transmission.......................................................35
6.5 EPI – Protection Event Information............................................................................. 35
6.5.1 Supported Data Types.................................................................................35
6.5.2 Additional information.................................................................................. 36
6.5.3 Conversion of Values...................................................................................36
6.5.4 Conversion of Quality Descriptors...............................................................36
6.5.5 Conversion of Causes of Transmission.......................................................36
6.6 ITI – Integrated Totals Information.............................................................................. 37
6.6.1 Supported Data Types.................................................................................37
6.6.2 Additional Information.................................................................................. 37
6.6.3 Conversion of Values...................................................................................37
6.6.4 Conversion of Quality Descriptors...............................................................38
6.6.5 Conversion of Causes of Transmission.......................................................38
6.7 MFI – Measured Float Information.............................................................................. 38
6.7.1 Supported Data Types.................................................................................38
6.7.2 Values.......................................................................................................... 38
6.7.3 Additional Information.................................................................................. 39
6.7.4 Conversion of Values...................................................................................39
6.7.5 Conversion of Quality Descriptors...............................................................39
6.7.6 Conversion of Causes of Transmission.......................................................39
6.8 SPI – Single Point Information.................................................................................... 40
6.8.1 Supported Data Types.................................................................................40
6.8.2 Additional Information.................................................................................. 40
6.8.3 Conversion of Values...................................................................................40
6.8.4 Conversion of Quality Descriptors...............................................................41
6.8.5 Conversion of Causes of Transmission.......................................................41
6.9 STI – Step Position Information.................................................................................. 41
6.9.1 Supported Data Types.................................................................................41
6.9.2 Additional Information.................................................................................. 42
6.9.3 Conversion of Values...................................................................................42
6.9.4 Conversion of Quality Descriptors...............................................................42

II 1KGT 150 466 V024 1

Contents

6.9.5 Conversion of Causes of Transmission.......................................................42

7 Data Types - Controlling Direction..................................................................................... 45

7.1 ASO – Analog Setpoint Output................................................................................... 45
7.1.1 Supported Data Types.................................................................................45
7.1.2 Command Authority..................................................................................... 45
7.1.3 Additional Information.................................................................................. 45
7.1.4 Conversion of Values...................................................................................45
7.1.5 Conversion of Qualifier of Command.......................................................... 46
7.1.6 Conversion of Causes of Transmission.......................................................46
7.2 BSO – Bit String Output.............................................................................................. 46
7.2.1 Supported Data Types.................................................................................46
7.2.2 Command Authority..................................................................................... 46
7.2.3 Additional Information.................................................................................. 47
7.2.4 Conversion of Values...................................................................................47
7.2.5 Conversion of Qualifier of Command.......................................................... 47
7.2.6 Conversion of Causes of Transmission.......................................................47
7.3 DCO – Double Command Output............................................................................... 47
7.3.1 Supported Data Types.................................................................................48
7.3.2 Command Authority..................................................................................... 48
7.3.3 Additional Information.................................................................................. 48
7.3.4 Conversion of Values...................................................................................48
7.3.5 Conversion of Qualifier of Command.......................................................... 48
7.3.6 Conversion of Causes of Transmission.......................................................49
7.4 DSO – Digital Setpoint Output.................................................................................... 49
7.4.1 Supported Data Types.................................................................................49
7.4.2 Command Authority..................................................................................... 50
7.4.3 Additional Information.................................................................................. 50
7.4.4 Conversion of Values...................................................................................50
7.4.5 Conversion of Qualifier of Command.......................................................... 50
7.4.6 Conversion of Causes of Transmission.......................................................50
7.5 FSO – Floating Point Setpoint Output.........................................................................51
7.5.1 Supported Data Types.................................................................................51
7.5.2 Command Authority..................................................................................... 51
7.5.3 Additional Information.................................................................................. 51
7.5.4 Conversion of values...................................................................................51
7.5.5 Conversion of Qualifier of Command.......................................................... 51
7.5.6 Conversion of Causes of Transmission.......................................................52
7.6 RCO – Regulation Command Output..........................................................................52
7.6.1 Supported Data Types.................................................................................52
7.6.2 Command Authority..................................................................................... 52
7.6.3 Additional Information.................................................................................. 52
7.6.4 Conversion of Values...................................................................................53
7.6.5 Conversion of Qualifier of Command.......................................................... 53
7.6.6 Conversion of Causes of Transmission.......................................................53
7.7 SCO – Single Command Output................................................................................. 54
7.7.1 Supported Data Types.................................................................................54

1KGT 150 466 V024 1 III

 Contents

7.7.2 Command Authority..................................................................................... 54

7.7.3 Additional Information.................................................................................. 54
7.7.4 Conversion of Values...................................................................................54
7.7.5 Conversion of Qualifier of Command.......................................................... 54
7.7.6 Conversion of Causes of Transmission.......................................................55

8 Transparent Data.................................................................................................................. 57
8.1 Transparent data channel............................................................................................57
8.1.1 Command direction......................................................................................57
8.1.2 Monitoring direction..................................................................................... 58
8.1.3 Request procedure...................................................................................... 59
8.2 Encapsulated SPAbus messages................................................................................60
8.2.1 General........................................................................................................ 60
8.2.2 Request procedure...................................................................................... 61

9 File Transfer.......................................................................................................................... 63
9.1 Supported data types.................................................................................................. 63
9.2 Values...........................................................................................................................63
9.3 Command Authority..................................................................................................... 63
9.4 Additional information.................................................................................................. 64
9.5 Conversion of causes of transmission........................................................................ 64
9.6 Download..................................................................................................................... 64
9.7 Upload.......................................................................................................................... 64
9.8 Transmission of sequences of events......................................................................... 65
9.8.1 Scope of operation...................................................................................... 65
9.8.2 Engineering in RTUtil500.............................................................................65
9.8.3 Runtime procedure...................................................................................... 66
9.9 Transmission of sequences of recorded analog values.............................................. 66
9.9.1 Scope of operation...................................................................................... 66
9.9.2 Engineering in RTUtil500.............................................................................66
9.9.3 Runtime procedure...................................................................................... 67

10 Internal Functions.................................................................................................................69
10.1 General Interrogation................................................................................................... 69
10.1.1 Supported Data Types.................................................................................69
10.1.2 Values.......................................................................................................... 69
10.1.3 Command Authority..................................................................................... 69
10.1.4 Additional information.................................................................................. 69
10.1.5 Conversion of Quality Descriptors...............................................................69
10.1.6 Conversion of Causes of Transmission.......................................................70
10.2 Counter Interrogation Command................................................................................. 70
10.2.1 Supported data types.................................................................................. 70
10.2.2 Values.......................................................................................................... 70
10.2.3 Command Authority..................................................................................... 70
10.2.4 Additional information.................................................................................. 70
10.2.5 Conversion of quality descriptors................................................................ 71
10.2.6 Conversion of causes of transmission........................................................ 71

IV 1KGT 150 466 V024 1

Contents

10.3 Read Command...........................................................................................................71

10.3.1 Supported data types.................................................................................. 71
10.3.2 Values.......................................................................................................... 72
10.3.3 Command Authority..................................................................................... 72
10.3.4 Additional information.................................................................................. 72
10.3.5 Conversion of quality descriptors................................................................ 72
10.3.6 Conversion of causes of transmission........................................................ 72
10.4 Time Synchronization.................................................................................................. 72
10.4.1 Supported Data Types.................................................................................73
10.4.2 Values.......................................................................................................... 73
10.4.3 Command Authority..................................................................................... 73
10.4.4 Additional information.................................................................................. 73
10.4.5 Conversion of Causes of Transmission.......................................................73
10.5 Test Command.............................................................................................................73
10.5.1 Supported data types.................................................................................. 74
10.5.2 Values.......................................................................................................... 74
10.5.3 Command Authority..................................................................................... 74
10.5.4 Additional Information.................................................................................. 74
10.5.5 Conversion of quality descriptors................................................................ 74
10.5.6 Conversion of causes of transmission........................................................ 74
10.6 Reset Command.......................................................................................................... 74
10.6.1 Supported data types.................................................................................. 75
10.6.2 Values.......................................................................................................... 75
10.6.3 Command Authority..................................................................................... 75
10.6.4 Additional information.................................................................................. 75
10.6.5 Conversion of quality descriptors................................................................ 75
10.6.6 Conversion of causes of transmission........................................................ 75
10.7 Deactivate Command.................................................................................................. 75
10.7.1 Supported data types.................................................................................. 76
10.7.2 Values.......................................................................................................... 76
10.7.3 Command Authority..................................................................................... 76
10.7.4 Additional information.................................................................................. 76
10.7.5 Conversion of quality descriptors................................................................ 76
10.7.6 Conversion of causes of transmission........................................................ 76
10.8 Delay Acquisition Command....................................................................................... 77
10.8.1 Supported data types.................................................................................. 77
10.8.2 Values.......................................................................................................... 77
10.8.3 Command Authority..................................................................................... 77
10.8.4 Additional Information.................................................................................. 77
10.8.5 Conversion of quality descriptors................................................................ 77
10.8.6 Conversion of causes of transmission........................................................ 77
10.9 Parameter Loading...................................................................................................... 78
10.9.1 Supported data types.................................................................................. 78
10.9.2 Command Authority..................................................................................... 78
10.9.3 Additional Information.................................................................................. 78
10.9.4 Conversion of Values for Threshold............................................................ 78

1KGT 150 466 V024 1 V

 Contents

10.9.5 Conversion of values for smoothing............................................................79

10.9.6 Conversion of qualifier of parameter of measured values...........................79
10.9.7 Conversion of causes of transmission........................................................ 79
10.10 System Events............................................................................................................. 80
10.11 System commands...................................................................................................... 81
10.11.1 Reset device process.................................................................................. 82
10.11.2 Force process image update.......................................................................82
10.11.3 Request redundancy change over.............................................................. 82

11 Interoperability List.............................................................................................................. 83
11.1 System or device......................................................................................................... 83
11.2 Network configuration.................................................................................................. 83
11.3 Physical Layer..............................................................................................................83
11.3.1 Transmission speed (control direction)........................................................83
11.3.2 Transmission speed (monitor direction)...................................................... 84
11.4 Link Layer.................................................................................................................... 84
11.5 Application Layer......................................................................................................... 85
11.5.1 Transmission Mode for Application Data.....................................................85
11.5.2 Common Address of ASDU........................................................................ 85
11.5.3 Information object address.......................................................................... 85
11.5.4 Cause of transmission................................................................................. 85
11.5.5 Selection of standard ASDUs......................................................................85
11.6 Basic application functions.......................................................................................... 89
11.6.1 Station initialization...................................................................................... 89
11.6.2 Cyclic data transmission..............................................................................89
11.6.3 Read procedure........................................................................................... 89
11.6.4 Spontaneous transmission.......................................................................... 89
11.6.5 Double transmission of information objects with cause of transmission
spontaneous.................................................................................................89
11.6.6 Station interrogation.....................................................................................90
11.6.7 Clock synchronization..................................................................................90
11.6.8 Command transmission............................................................................... 90
11.6.9 Transmission of integrated totals................................................................ 90
11.6.10 Parameter loading....................................................................................... 91
11.6.11 Parameter activation....................................................................................91
11.6.12 Test procedure............................................................................................. 91
11.6.13 File transfer..................................................................................................91
11.6.14 Background scan......................................................................................... 91
11.6.15 Acquisition of transmission delay................................................................ 92

12 Glossary.................................................................................................................................93

VI 1KGT 150 466 V024 1

Introduction Preface

1 Introduction

1.1 Preface
This document describes the functions of the host communication interface in RTU500 series
according to IEC 60870-5-101.

RTU500 series fulfills the requirements of IEC 60870-5-101 Edition 2. Detailed information can be
found in the interoperability list (see Chapter 11).

1.2 References
[1] IEC 60870-5-2

Telecontrol equipment and systems - Part 5: Transmission protocols - Section 2: Link

transmission procedures

Edition 1.0 1992-04

[2] IEC 60870-5-101

Telecontrol equipment and systems – Part 5-101: Transmission protocols – Companion

standard for basic telecontrol tasks

Edition 2.1 2015-11

[3] RTU500 series Interfaces and Protocols Release 12 (1KGT 150 939)
[4] User Manual RTUtil500 Release 12 (1KGT 150 950)

1.3 Conventions
In this document function codes of data types according to IEC 60870-5-101 are marked with
brackets: <Function code>

Bold fonts with the table heading "Parameter name" are references to configuration parameters
in RTUtil500. The parameter is followed by the parameter location where to find this parameter in
RTUtil500. The first element of the parameter location defines the node in the hardware tree on the
left side (e. g. RTU, CMU, line, IED) and the second element defines selected header control tab in
the parameter window on the right side (e. g. general, interfaces, protocol).

Example:

Parameter name Default Parameter location

In use enabled data point - Line T101

If enabled, the data point is transmitted to the host communication interface.
This setting refers to data in monitoring and command direction.

The tables in the next chapters include lists of the functions, options and message types supported
according to the protocol structure given in IEC 60870-5 (EPA three layer model) for
• the physical layer
• the link layer
• the application layer
This layered model is valid for the protocol IEC 60870-5-101.

1KGT 150 466 V024 1 7

Conventions Introduction

8 1KGT 150 466 V024 1

Physical Layer Serial line-based communication

2 Physical Layer

2.1 Serial line-based communication

The protocol IEC 60870-5-101 is running on the serial communication interfaces of the CMUs. For
more details see RTU500 series Interfaces and Protocols Release 12 (1KGT 150 939).

Set the communication parameters according to the following table:

Parameter name Default Parameter location

Interface type RS232C CMU - serial interfaces

Type of physical interface.
Select from list.
Value range: RS232C, RS485 or fix if selection is not supported
Baud rate 9600 bits/sec CMU - serial interfaces
Value range: 50, 75, 100, 110, 150, 200, 300, 600, 1200, 1500, 2400, 4800, 9600, 19200, 38400 bits/sec; 50-600 bits/sec only on
selected interfaces
Modem control Direct link (TxD/RxD CMU - serial interfaces
only)

Value range:
• Direct link (TxD/RxD only)
• WT link full duplex (no handshake)
• WT link half duplex (RTS/CTS handshake)
• WT link half duplex (RTS/DCD handshake)
• Dial up (external modem DCD handshake)
• Loop switch unit (DSTC 3002), RP570/71 Host interface only
• Link with collision avoidance (DCD handshake), DNP 3 only
Usage of the controls for this interface.
Direct Link: No modem controls.
Loop Switch Unit: RP570/71 Host Interface only.
Collision Avoidance: DNP3.0 Host/Sub-Interface only
Transmit delay time disabled CMU - serial interfaces
If 'Transmit Delay Time' is enabled:
Delay time in Milliseconds. Value range: 1 to 10000 ms.
Recommended value for WT modems in half-duplex mode: 30 ms

ADVICE
The possibility to use different transmission speeds in control and in monitor direction is not
supported by RTU500 series.

2.2 Host interface

All host interfaces will be configured according to the following table.

Parameter name Default Parameter location

Host number 1 CMU - all interfaces

Logical number of this host interface. Value range: 1 to 16.
The Host Number has to be unique in a system,
and will point to the data in the system event block

1KGT 150 466 V024 1 9

Host interface Physical Layer

10 1KGT 150 466 V024 1

Link Layer General

3 Link Layer

3.1 General
A link address model is used for all RTU500 series communication interfaces. The basic procedures
for data transfer, protection against loss and duplication and flow control are described in [2, 5]. This
link address is configurable in the line folder of RTUtil500 separately for every line. The link address
must be configured only once.

Parameter name Default Parameter location

Linkaddress 1 RTU - Line T101

Link address of this process data point. The address may be unstructured or structured.
Length 0, 1 or 2 octets (0 only balanced transmission)

Communication primitives like framing of messages, parity checks or retransmissions are handled
by the telecontrol protocol. These tasks are executed in the link layer that connects RTUs and
control systems or other RTUs. The selectable parameters have to be calculated regarding the real
communication technology. All parameters preset to the default values from [2, 9.5].

Parameter name Default Parameter location

Link address structure 8 bit unstructured Line T101 - IEC 60870-5-101

Length of Link Address: 0, 8 or 16 bit
0 in balanced mode only

Structured address with underscore as delimiter

Example: 3_5_8 defines 16-bit address with 3 structure elements:
3 bit most significant
5 bit medium significant
8 bit least significant

Table 1: Line parameters link layer IEC60870-5-101: address elements

Parameter name Default Parameter location

Maximum frame length 255 Line T101 - IEC 60870-5-101

Maximum frame length.
Value range: 32 to 255 octets.

Table 2: Line parameters link layer IEC60870-5-101: telegram framing

Parameter name Default Parameter location

Timeout acknowledgement 1s Line T101 - IEC 60870-5-101

Link Layer response/confirmation time out interval in seconds.
Relevant at Master interface in balanced and unbalanced mode and
at slave interface in balanced mode only.
Value range: 0.1 to 600 sec.
Cycle time test link Enabled, 120 s Line T101 - IEC 60870-5-101
Specification whether Test Link messages shall be sent
If selected, Test Link message will be sent if within the specified time
no Application message had been sent
Relevant in balanced mode only
Time period in seconds or '-' to disable.
Cycle time offline supervision Enabled, 120 s Line T101 - IEC 60870-5-101

Table 3: Line parameters link layer IEC60870-5-101: timeouts

1KGT 150 466 V024 1 11

Unbalanced Mode Link Layer

Parameter name Default Parameter location

Specification whether offline supervision of the primary station shall take place
Relevant at slave interface and unbalanced mode only.
Time period in seconds or '-' to disable.
Gap supervision time Enabled, 1 t0 Line T101 - IEC 60870-5-101
Specification whether the receiver shall perform a check for
line idle intervals between the characters of a frame
[IEC 60870-5-1, clause 6.2.4.2: Transmission rule R3 for format FT1.2].
Maximum allowed length of line idle intervals between two characters
Specification: number of line idle bits or '-' to disable.
Communication retry Enabled, 7 Line T101 - IEC 60870-5-101
Specification whether transmission repetitions shall take place
Relevant at slave interface in balanced mode only.
Maximum number of transmission repetitions
in case of consecutive transmission disturbances
Value range: 1 to 255 or '-' to disable.

Relevant at slave interface in balanced mode only.

Table 3: Line parameters link layer IEC60870-5-101: timeouts

Parameter name Default Parameter location

Transmission mode Unbalanced Line T101 - IEC 60870-5-101

Balanced Mode: spontaneous transmission
Unbalanced Mode: polling by primary station
Single character for acknowledgements Enabled Line T101 - IEC 60870-5-101
Use Single Character 0xE5
as Link Layer Acknowledgement
Link layer user class assignment according IEC Disabled Line T101 - IEC 60870-5-101
If enabled:
Link layer user classes are assigned as defined in IEC60870-5-101.
Otherwise link layer user classes are assigned according to the data point's configuration parameter 'Priority'.
Direction bit of controlling station 0 Line T101 - IEC 60870-5-101
Specification of the direction bit DIR of the Link Layer Control Field
to be used by the transmitter
Value range: 0 or 1
Relevant in balanced mode only
[IEC 60870-5-2, clause 6.1.2]

Table 4: Line parameters link layer IEC60870-5-101: other parameters

3.2 Unbalanced Mode

• The controlling station is primary station, controlled station (RTU) is secondary station
• The controlling station uses SEND/CONFIRM or SEND/NO REPLY services for transmission of
messages to the RTU
• The controlling station uses REQUEST/RESPOND services for the polling procedure and during
establishment of the link

3.3 Balanced mode

• Controlling station and controlled station (RTU) act simultaneously as primary and secondary
stations.
• Both, controlling station and controlled station use SEND/CONFIRM services for message
exchange, controlling station may also use the SEND/NO REPLY service.
• During link establishment both, controlling station and controlled station use the REQUEST/
RESPOND service.

12 1KGT 150 466 V024 1

Link Layer Dial-up function

3.4 Dial-up function

3.4.1 General

In the dial-up mode a communication link can be established via HAYES-compatible modems
between an RTU and a higher-level system. In this case the RTU receives telephone calls and then
switches over to the data mode.

When a telephone connection has been established, but communication according to the protocol
does not take place the telephone connection will be terminated after elapse of the time defined
with the interface parameter Maximum time period until connection is established.

Additionally, the RTU may ring up the higher-level system on its own as soon as spontaneous
changes of Prio1 data points (see parameter Address) or system events have occurred or cyclical
calls from the RTU have been configured. It is always the task of the control system to terminate the
connection to the RTU.

If there is no communication with the control system for a configurable time, the RTU terminates the
telephone connection by itself. (Parameter: Time period until hanging up because of inactivity).

When the attempt to establish the telephone connection has failed dialling will be repeated several
times (interface parameter: Maximum number of dialling attempts). If the higher-level system
supports a modem pool functionality and several telephone numbers have been configured the next
telephone number will be called and establishing the telephone connection be attempted.

3.4.2 Dial-up configuration

In addition to the protocol-specific settings described in the chapters Physical Layer and Link Layer,
some settings shall be made for the dial-up mode, too.

The dial-up mode is available only, if the parameter dial-up active on the serial communication
interface (COM) of the CMU is enabled.

Parameter name Default Parameter location

Modem control: CMU - serial interfaces

Dial up (external modem DCD handshake)
Dial up enabled: enabled CMU - serial interfaces
If enabled:
This interface is using a dial-up connection
to the sub devices or the host interfaces.
Note: Not all protocols are supporting 'dial-up'.
Available only, if 'Dial up' is selected

All interface settings such as parity, baud rate, number of data bits, etc. depend on the protocol
selected and are valid for both the configuration and the data mode.

The dial-up mode parameters are available in separate dialogue windows in the network and
hardware Tree of the configuration tool RTUtil500.

3.4.2.1 Dial-up parameters at the the serial interfaces of the CMU

Parameter name Default Parameter location

Escape sequence preceding silent time 1s CMU - serial interfaces (dial up parameters)
Range: 1 … 255 s
Minimal delay time between data mode and Hayes command mode

1KGT 150 466 V024 1 13

Dial-up function Link Layer

Parameter name Default Parameter location

Configuration string for modem ATE0X3S0=1 CMU - serial interfaces (dial up parameters)
String
Configuration string initializing the modem used.
Note:The configuration string depends on the type of modem, the modem manufacturer and the modem function used.
Dial string for modem ATDT CMU - serial interfaces (dial up parameters)
String
Command Hayes to establish a modem connection
Escape string for modem +++ CMU - serial interfaces (dial up parameters)
String
Command Hayes to switch from data mode to command mode
Answer string for modem Disable CMU - serial interfaces (dial up parameters)
<no defaults>
String
Enable/Disable
If enabled: An incoming call is answered with this string.
Note: For standard HAYES modems the value S0=0 shall be set in the configuration string, if this feature is enabled (see modem
description).
Hang up string for modem ATH CMU - serial interfaces (dial up parameters)
String
String requesting the modem to terminate the telephone connection.
Connect string of modem CONNECT CMU - serial interfaces (dial up parameters)
String
String sent by the modem if a telephone connection has been established.
OK string of modem OK CMU - serial interfaces (dial up parameters)
String
String sent by the modem to acknowledge a command
Disconnect string of modem NO CARRIER CMU - serial interfaces (dial up parameters)
String
String sent by the modem if the connection is aborted
Ring string of modem RING CMU - serial interfaces (dial up parameters)
String
String sent by the modem signaling an incoming call.
Busy string of modem BUSY CMU - serial interfaces (dial up parameters)
String
With this string the modem signals that the remote terminal called is busy.
PIN configuration string for GSM modem Disable CMU - serial interfaces (dial up parameters)
String
Enable/Disable
Service configuration string for GSM modem Disable CMU - serial interfaces (dial up parameters)
String
Enable/Disable

3.4.2.2 Dial-up parameters of the RTU

The configuration of the dial-up timeout parameters can be found only in the network tree at the
RTU node (left window) and on the specific line (right window) at the tab dial up parameters.

Parameter name Default Parameter location

Maximum time till link is established 60 s Network tree only:

RTU - line

14 1KGT 150 466 V024 1

Link Layer Dial-up function

Parameter name Default Parameter location

Value range: 1 ... 255 s

Maximum time interval until the connection to a higher-level system must be established. When this time has elapsed the modem
connection will be terminated.
Maximum number of dial attempts 2 Network tree only:
RTU - line
Value range: 1 ... 255 attempts
Maximum number of times a telephone number is called. If the higher-level system supports a modem-pool function the next
telephone number will then be called.
Time between dial attempts 60 s Network tree only:
RTU - line
Value range: 1 ... 15 300 s
When an attempt has failed the number will be called again after elapse of this time.
Time between two series of dial attempts 7 800 s Network tree only:
RTU - line
Value range: 60 … 15 300 s
Waiting time between dial series with different telephone numbers (modem pool)
Inactivity hang up delay disabled Network tree only:
RTU - line
Value range: disabled, 1 ... 15 300 s
Inactivity hang up delay after commands disabled Network tree only:
RTU - line
Value range: disabled, 1 ... 15 300 s
Maximum period for one telephone connection 600 s Network tree only:
RTU - line
Value range: disabled, 10 ... 15 300 s
Cyclic calls of dial up slave disabled Network tree only:
RTU - line
Value range: disabled / enabled
If enabled: Start time of cyclic calls [hour, minutes]; Time interval between two calls [days, hours, minutes]

3.4.2.3 Dial-up parameters of the control system

This window can be found only in the network tree at the connected control system.

Parameter name Default Parameter location

Telephone number 1 <no default> Network tree only:

Control system - Telephone numbers
Value range: string (length max. 27 characters)
Telephone number under which a higher-level system can be called.
Telephone number 2 ... 16 deactivated Network tree only
Control system - Telephone numbers
Value range: deactivated, string (length max. 27 characters)
Additional telephone numbers under which a higher-level system can be called. If the higher-level system does not support the
modem-pool function the telephone numbers need not to be configured.

3.4.3 Request for Access Demand

‘Acquisition of events by quick-check procedure’ will only be supported by HCI IEC 60870-5-101
with dial-up connections.

The global request of access demand (broadcast link address, FC = ‘REQUEST for access
demand’) will only be respond with respond access demand (link address of RTU500 series RTU at
this HCI IEC 60870-5-101, FC = ‘RESPOND status of link or access demand’), if at least one user

1KGT 150 466 V024 1 15

Redundant communication lines Link Layer

data class 1 is waiting for transmission in HCI IEC 60870-5-101. Otherwise no respond will be send
by HCI IEC 60870-5-101.

3.5 Redundant communication lines

The redundant line function of RTU500 series is used to raise connection availability to the
controlling station. This function is only available for the protocol IEC 60870-5-101 and it is
implemented according to the Norwegian User Conventions.

General function:
• Both lines have the same link address
• The switching between the lines is generally initiated by the controlling station.
• After a redundancy switching a general interrogation must be sent from the controlling station
• During the switchover between the redundant lines the CMU has to secure that no data point
information get lost.
• After a disruption the connection have to establish again.

Redundancy Switch Over condition (only available in unbalanced mode):

• As default, the redundancy switching is done according to the IEC standard (Norvegian User
Convention) which switches to redundant line upon 'reset of remote link' (FC0) command.
• It is possible to change the redundancy switching: it can be configured that the switching over is
done by 'request of user data' command (FC11).
Parameter name Default Parameter location

Redundancy switch over condition IEC Standard: Reset of Line T101 - IEC 60870-5-101
remote link (Norwegian
UC) (FC0)
Value range:
- IEC Standard: Reset of remote link (Norwegian UC) (FC0)
- Request User Data (FC11)

Both the configuration of redundant lines is part of the engineering tool for the RTU500 series
RTUtil500. Both lines must be connected to the same CMU. The interfaces could be configured with
different physical parameters.

Steps in RTUtil500:

1. Add one communication line T101 to the network tree.

2. Link this communication within the hardware tree twice to the same CMU.

3.5.1 Unbalanced mode

After startup of the controlling station, the controlling station sends a Request Status of Link on both
channels, in order to determine which channel to use as the primary channel, and send a Reset
of Remote Link on the primary channel. The controlling station will continue to send a Request
Status of Link message on the backup channel cyclically (see the following figures Initialization of
controlling station, unbalanced mode and Initialization of controlled station, unbalanced mode).

16 1KGT 150 466 V024 1

Link Layer Redundant communication lines

Figure 1: Initialization of controlling station, unbalanced mode

Figure 2: Initialization of controlled station, unbalanced mode

1KGT 150 466 V024 1 17

Redundant communication lines Link Layer

If the primary channel is interrupted, the controlling station will mark the primary channel down
and send a Reset of Remote Link message to the controlled station over the backup channel. The
controlled station will respond and the controlling station then will send a poll request. Once the new
primary channel is established, the controlling station will begin sending a Request Status of Link
message on the channel which lost communication.

3.5.2 Balanced mode

After restart of the controlling station, link connection is established in both directions and on both
lines. Both links of the controlling station may by default be defined to be passive at the moment
the link layer is available after restart. An interrogation command is therefore transmitted to define
the active line (see the following figures Initialization of controlling station, balanced mode and
Initialization of controlled station, balanced mode).

Figure 3: Initialization of controlling station, balanced mode

18 1KGT 150 466 V024 1

Link Layer Redundant communication lines

Figure 4: Initialization of controlled station, balanced mode

If communication fails on the active line when the controlling station attempts to transmit user data,
a line switch will be performed, after maximum transmission retries has elapsed. A line switch will
also be performed whenever the periodic line check procedure on the active line (Test function of
link) times out after maximum transmission retries.

If communication fails on the active line when the controlled station attempts to transmit user data,
the controlled station must wait for the controlling station to detect the failure.

1KGT 150 466 V024 1 19

Redundant communication lines Link Layer

20 1KGT 150 466 V024 1

Application Layer General

4 Application Layer

4.1 General
The selectable parameters have to be calculated regarding the real communication technology. All
parameters preset to the default values from the IEC standard.

Parameter name Default Parameter location

ASDU address of station 1 RTU - Line T101

ASDU address of the station used for station specific commands,
like counter interrogation commands, reset process commands, etc.
Parameter name Default Parameter location

Setpoint command with command disabled RTU - Line T101/T104

acknowledgement
If enabled, all setpoint commands will be respond with activation termination.
Fixed originator address disabled RTU - Line T101/T104
If enabled,
a fix originator address can be configured.
This originator address is set in telegrams send by this host communication interface.
Originator address. Value range 0 to 255.
only possible to enable if special protocol profiles are selected

Table 5: RTU parameters application layer

Parameter name Default Parameter location

ASDU address structure 8 bit unstructured Line T101 - IEC 60870-5-101

Length of Common Address of ASDU: 8 or 16 bit

Structured address with underscore as delimiter

Example: 3_5_8 defines 16-bit address with 3 structure elements:
3 bit most significant
5 bit medium significant
8 bit least significan
Information object address structure 16 bit unstructured Line T101 - IEC 60870-5-101
Length of Information Object Address: 8, 16 or 24 bit

Structured address with underscore as delimiter

Example: 3_5_6_3_7 defines 24-bit address with 5 structure elements
Cause of transmission length 8 bit Line T101 - IEC 60870-5-101
Selection: 8 or 16 bit
If 16 bit is selected, the second octet (Originator Address)
is set to 0 in send frames and is ignored in received frames

Table 6: Line parameters application layer IEC 60870-5-101: telegram framing

Parameter name Default Parameter location

Protocol edition Edition 1 Line T101/104 - IEC 60870-5-101/104

Edition 1: Timer t1 is retriggered with any transmitted telegram i.e. there is only one timer t1.
Edition 2: Separate timer t1 for each sent telegram i.e. if any timer t1 expires connection is closed.
Protocol profile Standard Line T101/104 - IEC 60870-5-101/104
Selection of IEC60870-5-104 protocol profile.
Default value 'Standard' equals the IEC standard.
Other selections activate special IEC protocol profiles.
For more details see document 'Customer Profiles' which you can get from RTU technical support team.

Table 7: Line parameters application layer IEC 60870-5-101: other parameters

1KGT 150 466 V024 1 21

Communication Queue Handling Application Layer

Parameter name Default Parameter location

Transmission with full timestamp disabled Line T101 - IEC 60870-5-101

Specification of the format of time tags for process information:
- short format: CP24Time2a (minutes and milliseconds up to 59.59999)
- long format: CP56Time2a (complete date and time representation, 2 character year representation 00 to 99)
Background scan cycle disabled Line T101/104 - IEC 60870-5-101/104
If enabled:
Background scan according to IEC60870-5-101/104
will be send with the configured cycle time.
Cycle time of background scan in minutes or '-' to disable.
Acknowledge Commands on reception disabled Line T101/104 - IEC 60870-5-101/104
Specification whether Activation Confirmation shall be sent immediately after reception of a command. Necessary if the primary station
uses a fix timeout period with low tolerance.
If HCI receives an interal negative confirmation, then this is send as negative termination to primary station. An internal positive
confirmation generates no additional message to primary station. The internal positive Activation Termination is send to primary
station.
Send analog events with value 0 in GI disabled Line T101/104 - IEC 60870-5-101/104
If enabled:
For subdevice communication interfaces with IEC60870-5-103.
Selected values are transmitted with '0' during General Interrogation
Double transmission mode disabled Line T101 - IEC 60870-5-101
If enabled: (and if Transmit with Timestamp is enabled)
Information in monitoring direction will be transmitted twice:
1. With high priority, without time stamp.
2. With low priority, with time stamp.
(Pulse counter PCV are not affected)
Exclusive access to interfaces of redundant lines disabled Line T101 - IEC 60870-5-101
If enabled, the serial interfaces of a redundant
subdevice communication line will be accessed exclusive.
That means as long as one interface is accessed all other interfaces of
this redundant line are blocked.
Treat value 'no counter requested (not used)' of disabled Line T101/104 - IEC 60870-5-101/104
RQT qualifier of C_CI_NA_1 as 'general request
counter'
If enabled:
Qualifier of counter interrogation command 'no counter requested' is treated as 'general request counter'.
Event buffer overflow strategy Delete oldest event Line T101/104 - IEC 60870-5-101/104
Delete oldest event:
In case of overflow the oldest events will be removed from the concerned queue to get space for new events and put in a one-stage
image.

Delete newest event:

In case of overflow the newest events are not entered to the queue but written to a one-stage process image instead.
Parameter Loading enabled Line T101/104 - IEC 60870-5-101/104
If enabled: Parameter loading requests are supported.
If disabled: Parameter loading requests will be responded negative.
Type specific address range disabled Line T101/104 - IEC 60870-5-101/104
If enabled, IEC address of different RTU data types are independent, so data points of different type may have the same address.
Routed diagnosis support disabled Line T101/104 - IEC 60870-5-101/104
If enabled: Routed diagnosis is activated.
Allow only one general interrogation running per disabled Line T101/104 - IEC 60870-5-101/104
common address of ASDU
If enabled: Only one running general interrogation per common address of ASDU is allowed.

Table 7: Line parameters application layer IEC 60870-5-101: other parameters

4.2 Communication Queue Handling

The host interface has 7 different communication queues and an additional process image:
• Command acknowledgment queue

22 1KGT 150 466 V024 1

Application Layer Communication Queue Handling

• Priority 1 queue for monitoring data (except integrated totals and measured values)
(Priority 1 for monitoring data can be configured individual per data point)
• Priority 2 queue for monitoring data (except integrated totals and measured values)
(Priority 2 for monitoring data can be configured individual per data point)
• Integrated totals (ITI) queue
(The priority of the ITI queue can be assigned in total as Prio 1 or Prio 2)
• Spontaneous measured value queue
• Requested information queue incl. file transfer
• Sequence of event queue (SOE) queue
(The SOE queue is only used if double transmission mode is activated)
The queue priority is assigned by function/ cause of transmission (COT) or by configuration

Highest Priority:
• Command acknowledgment queue (COT=6…10)
Priority level 1:
• Priority 1 Monitoring data queue (COT=3)
• Integrated totals queue (if configured as priority 1) (COT=3)
Priority level 2:
• Priority 2 Monitoring data queue (COT=3)
• Integrated totals queue (if configured as priority 2) (COT=3)
• Spontaneous measured value queue (COT=3)
• Requested information queue incl. file transfer (COT=37..41 and COT =13)
• SOE queue (if double transmission mode is activated)
Lowest priority:
• Interrogated data, direct from process image (COT=20…36)
• Periodic/ cyclic measured values, direct from process image (COT=1)
• Background cycle, direct from process image (COT=2)
Parameter name Default Parameter location

Buffer size of priority 1 datapoints 500 entries CMU - all interfaces

Transmit buffer size for priority 1 data.
Value range: 100 to 10000 entries
Buffer size of priority 2 datapoints 500 entries CMU - all interfaces
Transmit buffer size for priority 2 data.
Value range: 100 to 10000 entries
Buffer size of Integrated Totals (ITI) 1000 entries CMU - all interfaces
Transmit buffer size for Integrated Total.
Value range: 10 to 10000 entries
Priority of ITI queue 2 CMU - all interfaces
Priority of the transmit buffer for Integrated Totals.
Value range: 1 or 2
Buffer size of spontaneous transmitted Analog 500 entries CMU - all interfaces
Measured values (AMI)
Transmit buffer size for spontaneous transmitted measurements.
Value range: 100 to 100000
Queue storage timeout aktiviert, 120 min CMU - all interfaces
Delay time, before the buffers are cleared.
Value range: disabled, 1 to 10080 minutes

It is possible to disable buffering for selected monitoring data points:

Parameter name Default Parameter location

Put in buffer Enabled data point - line T101/T104

1KGT 150 466 V024 1 23

ASDU Type identification Application Layer

Parameter name Default Parameter location

If enabled: parameter changes will be stored in buffer when host is offline.

If disabled: GI is mandatory to get current value.

A buffer filling limit of 75 % of monitoring queues is signalized as alarm system event. Signalization
is done using system events #293-308: 'Host interface x: SOE buffer alarm limit exceeded'.

These system events are generated for each host interface instance identified by its host number
independently.
Signalization system event is generated, if at least one of the following buffers exceeds 75 % of its
filling level:

• Priority 1 queue for monitoring data

• Priority 2 queue for monitoring data
• Integrated totals (ITI) queue
• Spontaneous transmitted Analog Measured Inputs
Signalization is reset, if the all buffers have a filling level less than 10 %. Signalization limits (set and
reset) are not configurable.

4.3 ASDU Type identification

Overview on type identifications for data elements of the application layer defined in [2].

The column "RTU data type" shows the type of data with must be configured in RTUtil500.

4.3.1 ASDU in monitoring direction

ASDU Description Type iden- RTU data type

tification
M_SP_NA_1Single-point information <1> SPI
M_SP_TA_1 Single-point information with time tag <2> SPI
M_SP_T- Single-point information with time tag CP56Time2a <30> SPI
B_1
M_D- Double-Point information <3> DPI
P_NA_1
M_D- Double-Point information with time tag <4> DPI
P_TA_1
M_DP_T- Double-Point information with time tag CP56Time2a <31> DPI
B_1
M_ST_NA_1Step position information <5> STI
M_ST_TA_1 Step position information with time tag <6> STI
M_ST_T- Step position information with time tag CP56Time2a <32> STI
B_1
M_BO_NA_1Bitstring of 32 bit <7> BSI8/16/321
M_BO_TA_1Bitstring of 32 bit with time tag <8> BSI8/16/321
M_BO_T- Bitstring of 32 bit with time tag CP56Time2a <33> BSI8/16/321
B_1
M_ME_NA_1Measured value, normalized value <9> AMI DMI8/16
M_ME_TA_1Measured value, normalized value with time tag <10> AMI DMI8/16
Table 8: ASDU in monitoring direction

24 1KGT 150 466 V024 1

Application Layer ASDU Type identification

ASDU Description Type iden- RTU data type

tification
M_ME_T- Measured value, normalized value with time tag <34> AMI DMI8/16
D_1 CP56Time2a
M_ME_N- Measured value, scaled value <11> AMI
B_1
M_ME_T- Measured value, scaled value with time tag <12> AMI
B_1
M_ME_TE_1Measured value, scaled value with time tag <35> AMI
CP56Time2a
M_ME_NC_1Measured value, short floating point <13> MFI
M_ME_TC_1Measured value, short floating point value with time <14> MFI
tag
M_ME_T- Measured value, short floating point value with time <36> MFI
F_1 tag CP56Time2a
M_IT_NA_1 Integrated totals <15> ITI
M_IT_TA_1 Integrated totals with time tag <16> ITI
M_IT_TB_1 Integrated totals with time tag CP56Time2a <37> ITI
M_EP_TA_1 Event of protection equipment with time tag <17> EPI
M_EP_T- Event of protection equipment with time tag <38> EPI
D_1 CP56Time2a
Table 8: ASDU in monitoring direction

1 BSI32 is not supported for local I/O.

4.3.2 ASDU in control direction

ASDU Description Type iden- RTU data type

tification
C_SC_NA_1Single command <45> SCO
C_D- Double command <46> DCO
C_NA_1
C_R- Regulation step command <47> RCO
C_NA_1
C_SE_NA_1Set point command, normalized value <48> ASO DSO8/16
C_SE_N- Set point command, scaled value <49> ASO DSO8/16
B_1
C_SE_NC_1Set point command, short floating point <50> FSO
C_BO_NA_1Bitstring of 32 bit <51> BSO1/2/8/16/32
Table 9: ASDU in control direction

4.3.3 ASDU of system information in command direction

ASDU Description Type iden-

tification
C_IC_NA_1 Interrogation Command <100>
C_CI_NA_1 Counter interrogation command <101>
Table 10: System information in command direction

1KGT 150 466 V024 1 25

ASDU Type identification Application Layer

ASDU Description Type iden-

tification
C_RD_NA_1 Read command <102>
C_CS_NA_1 Clock synchronization command <103>
C_TS_NA_1 Test command <104>
C_RP_NA_1 Reset process command <105>
C_CD_NA_1 Delay acquisition command <106>
P_ME_NA_1 Parameter of measured value, normalized <110>
P_ME_NB_1 Parameter of measured value, scaled value <111>
P_ME_NC_1 Parameter of measured value, floating point value <112>
Table 10: System information in command direction

4.3.4 ASDU for file transfer

ASDU Description Type iden-

tification
F_FR_NA_1 File ready <120>
F_SR_NA_1 Section ready <121>
F_SC_NA_1 Call directory, select file, … <122>
F_LS_NA_1 Last section, last segment <123>
F_AF_NA_1 Ack file, ack section <124>
F_SG_NA_1 Segment <125>
F_DR_TA_1 Directory <126>
Table 11: ASDU for file transfer

26 1KGT 150 466 V024 1

Parameters and Addressing Address elements

5 Parameters and Addressing

5.1 Address elements

Selection according to [2]. The sizes of the addressing fields can be configured as shown in the
following table:

Parameter name Default Parameter location

Link address structure 8 bit unstructured Line T101 - IEC 60870-5-101

Length of Link Address: 0, 8 or 16 bit
0 in balanced mode only

Structured address with underscore as delimiter

Example: 3_5_8 defines 16-bit address with 3 structure elements:
3 bit most significant
5 bit medium significant
8 bit least significant
Parameter name Default Parameter location

ASDU address structure 8 bit unstructured Line T101 - IEC 60870-5-101

Length of Common Address of ASDU: 8 or 16 bit

Structured address with underscore as delimiter

Example: 3_5_8 defines 16-bit address with 3 structure elements:
3 bit most significant
5 bit medium significant
8 bit least significan
Information object address structure 16 bit unstructured Line T101 - IEC 60870-5-101
Length of Information Object Address: 8, 16 or 24 bit

Structured address with underscore as delimiter

Example: 3_5_6_3_7 defines 24-bit address with 5 structure elements
Cause of transmission length 8 bit Line T101 - IEC 60870-5-101
Selection: 8 or 16 bit
If 16 bit is selected, the second octet (Originator Address)
is set to 0 in send frames and is ignored in received frames

Table 12: Address element configuration

5.1.1 Restrictions for the link address

The value 0 is only allowed in balanced mode.

Parameter name Default Parameter location

Linkaddress 1 RTU - Line T101

Link address of this process data point. The address may be unstructured or structured.
Length 0, 1 or 2 octets (0 only balanced transmission)

5.1.2 Restrictions for the Common Address

The value 0 is not allowed.

The highest possible address value (255 for 1 octet common address length and 65 535 for 2 octet
common address length) is reserved for broadcast calls in control direction and therefore must not
be used as station address.

1KGT 150 466 V024 1 27

Address elements Parameters and Addressing

Parameter name Default Parameter location

ASDU address of station 1 RTU - Line T101

ASDU address of the station used for station specific commands,
like counter interrogation commands, reset process commands, etc.

Parameter name Default Parameter location

ASDU address 1 data point - Line T101

Application Service Data Unit.
The address may be unstructured or structured.
Length 1 or 2 octets.

5.1.3 Restrictions for the information object address

All addresses must be unique within one station. The type of presentation (ASDU format) is not part
of the identification of an object.

The value 0 is not allowed.

Parameter name Default Parameter location

Information object 1 data point - Line T101

Address of the Information Object.
The address may be unstructured or structured.
Length 1, 2 or 3 octets

5.2 General data point parameters

Parameter name Default Parameter location

In use enabled data point - Line T101

If enabled, the data point is transmitted to the host communication interface.
This setting refers to data in monitoring and command direction.
Parameter name Default Parameter location

Group interrogation active disabled data point - Line T101/T104

If enabled:
Data point belongs to an interrogation group
Interrogation group number disabled data point - Line T101/T104/GP104
If enabled:
Data point belongs to an interrogation group.
Enter group number for group interrogation.
Value range: 1 to 16 or '-' to disable.

Table 13: General data point parameters

28 1KGT 150 466 V024 1

Data Types - Monitoring Direction AMI – Analog Measured Information

6 Data Types - Monitoring Direction

6.1 AMI – Analog Measured Information

Analog process information indicated by 16 bit used as a measured value from analog inputs in
normalized or scaled format.

6.1.1 Supported Data Types

IEC 60870-5-101 RTU

ASDU Type iden- Data type Data Parame- Parameter location
tification property type ter name
M_ME_NA_1 <9> normalized with- AMI Transmission AMI - line T101/T104/
out timestamp format: Normal- GP104
ized
M_ME_TA_1 <10> normalized AMI Transmission AMI - line T101
with timestamp format: Normal-
CP24Time2a ized
Transmit with AMI - line T101
timestamp
M_ME_NB_1 <11> scaled without AMI Transmission AMI - line T101/T104/
timestamp format: Scaled GP104
M_ME_TB_1 <12> scaled with AMI Transmission AMI - line T101
timestamp format: Scaled
CP24Time2a Transmit with AMI - line T101
timestamp
M_ME_TD_1 <34> normalized AMI Transmission AMI - line T101/T104/
with timestamp format: Normal- GP104
CP56Time2a ized
Transmission AMI - line T101/T104/
with timestamp GP104
Transmit with full Line T101 - IEC
timestamp 60870-5-101
M_ME_TE_1 <35> scaled with AMI Transmission AMI - line T101/T104/
timestamp format: Scaled GP104
CP56Time2a Transmission AMI - line T101/T104/
with timestamp GP104
Transmit with full Line T101 - IEC
timestamp 60870-5-101
Table 14: AMI - Supported data types

6.1.2 Additional Information

Parameter name Default Parameter location

Spontanous transmission enabled data point - Line T101/T104/GP104

if enabled:
Spontaneous transmission of this process data point1)

1KGT 150 466 V024 1 29

AMI – Analog Measured Information Data Types - Monitoring Direction

Parameter name Default Parameter location

Background cycle disabled data point - Line T101/T104/GP104

If enabled:
Cyclic transmission of this process data point
out of the process image of the host interface with given cycle time of the background cycle.
Value range: disabled, 1 sec, 2, 4, 5, 8, 10, 16, 30, 60 sec, 2 min, 5 min, 10 min, 15 min1)

1)It
is possible to set both parameters at the same data point. That means that the concerning data
point is directly send to the NCC on every change and additional after the configured time period.

Parameter name Default Parameter location

Put in buffer Enabled data point - line T101/T104

If enabled: value changes will be stored in buffer when host is offline.
If disabled: GI is mandatory to get current value.

6.1.3 Conversion of Values

Parameter name Default Parameter location

Transmission format Normalized AMI - line T101/104

Transmission format for this data point:
Normalized: Value range -1.0 ... +1.0
Scaled: Value range -32768.0 ... +32767.0.
Maximum value 1 (Normalized) AMI - line T101/104
32767 (Scaled)
+100 % within RTU internal communication get converted
to parameter 'Maximum value' in the external communication protocol.
Normalized: Value range -1.0 ... +1.0.
Scaled: Value range -32768.0 ... +32767.0.
Minimum value -1 (Normalized AMI - line T101/104
-32768 (Scaled)
-100 % within RTU internal communication get converted
to parameter 'Minimum value' in the external communication protocol.
Normalized: Value range -1.0 ... +1.0.
Scaled: Value range -32768.0 ... +32767.0.

Range RTU internal value IEC 60870-5-101

Range min. -100 % Minimum value
... ...
Range max. +100 % Maximum value

Table 15: AMI - Conversion of values

6.1.4 Conversion of Quality Descriptors

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
OV Overflow Overflow
BL Blocked Blocked
SB Substituted Substituted
Table 16: AMI - Conversion of quality descriptors

30 1KGT 150 466 V024 1

Data Types - Monitoring Direction AMI – Analog Measured Information

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
NT Not Topical Not Topical
IV Invalid Invalid
Table 16: AMI - Conversion of quality descriptors

6.1.5 Conversion of Causes of Transmission

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
T Test Test
P/N Positive/negative confirmation - Irrelevant -
Cause Spontaneous 3 - spontaneous
Periodic / cyclic 1 - periodic / cyclic
Background scan 2 - background scan
Requested 5 - requested
Interrogated 20, 21 ... 36 - interrogated
Table 17: AMI - Conversion of causes of transmission

6.2 BSI – Bit String Information

Binary process information is indicated by 8, 16 or 32 bit.

6.2.1 Supported Data Types

IEC 60870-5-101 RTU

ASDU Type iden- Data type Data Parame- Parameter location
tification property type ter name
M_BO_NA_1 <7> without time- BSI
stamp
M_BO_TA_1 <8> with timestamp BSI Transmit with BSI - line T101
CP24Time2a timestamp
M_BO_TB_1 <33> with timestamp BSI Transmission BSI - line T101/T104/
CP56Time2a with timestamp GP104
Transmit with full line T101- IEC
timestamp 60870-5-101
Table 18: BSI - Supported data types

6.2.2 Additional Information

Parameter name Default Parameter location

Put in buffer Enabled data point - line T101/T104

If enabled: value changes will be stored in buffer when host is offline.
If disabled: GI is mandatory to get current value.

1KGT 150 466 V024 1 31

BSI – Bit String Information Data Types - Monitoring Direction

6.2.3 Conversion of values

Range RTU internal value IEC 60870-5-101

Range min. 0 0
... ...
Range max. BSI8: Bit mask of 8 bit; 255

range ... 255

BSI16: Bit mask of 16 65 535
bit;

range ... 65 535

BSI32: Bit mask of 32 4 294 967 295
bit;

range ... 4 294 967 295

Table 19: BSI - Conversion of values

6.2.4 Conversion of Quality Descriptors

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
OV Overflow Overflow
BL Blocked Blocked
SB Substituted Substituted
NT Not Topical Not Topical
IV Invalid Invalid
Table 20: BSI - Conversion of quality descriptors

6.2.5 Conversion of Causes of Transmission

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
T Test Test
P/N Positive/negative confirmation - Irrelevant -
Cause Spontaneous 3 - spontaneous
Background scan 2 - background scan
Requested 5 - requested
Interrogated 20, 21 ... 36 - interrogated
Table 21: BSI - Conversion of causes of transmission

6.3 DMI – Digital Measured Information

Binary process information indicated by 8 or 16 bit is used as a measured value from digital inputs
in normalized format.

32 1KGT 150 466 V024 1

Data Types - Monitoring Direction DMI – Digital Measured Information

6.3.1 Supported Data Types

IEC 60870-5-101 RTU

ASDU Type iden- Data type Data Parame- Parameter location
tification property type ter name
M_ME_NA_1 <9> without time- DMI
stamp
M_ME_TA_1 <10> with timestamp DMI Transmit with DMI - line T101
CP24Time2a timestamp
M_ME_TD_1 <34> with timestamp DMI Transmission DMI - line T101/T104/
CP56Time2a with timestamp GP104
Transmit with full Line T101 - IEC
timestamp 60870-5-101
Table 22: DMI - Supported data types

6.3.2 Additional Information

Parameter name Default Parameter location

Put in buffer Enabled data point - line T101/T104

If enabled: value changes will be stored in buffer when host is offline.
If disabled: GI is mandatory to get current value.

6.3.3 Conversion of values

Range RTU internal value IEC 60870-5-101

Range min. -100 % -1
... ...
Range max. +100 % +1-2e-15
Table 23: DMI - Conversion of values

6.3.4 Conversion of Quality Descriptors

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
OV Overflow Overflow
BL Blocked Blocked
SB Substituted Substituted
NT Not Topical Not Topical
IV Invalid Invalid
Table 24: DMI - Conversion of quality descriptors

1KGT 150 466 V024 1 33

DMI – Digital Measured Information Data Types - Monitoring Direction

6.3.5 Conversion of Causes of Transmission

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
T Test Test
P/N Positive/negative confirmation - Irrelevant -
Cause Spontaneous 3 - spontaneous
Periodic / cyclic 1 - periodic / cyclic
Background scan 2 - background scan
Requested 5 - requested
Interrogated 20, 21 ... 36 - interrogated
Table 25: DMI - Conversion of causes of transmission

6.4 DPI – Double Point Information

Binary process information is indicated by two bits.

6.4.1 Supported Data Types

IEC 60870-5-101 RTU

ASDU Type iden- Data type Data Parame- Parameter location
tification property type ter name
M_DP_NA_1 <3> without time- DPI
stamp
M_DP_TA_1 <4> with timestamp DPI Transmit with DPI - line T101
CP24Time2a timestamp
M_DP_TB_1 <31> with timestamp DPI Transmission DPI - line T101/T104/
CP56Time2a with timestamp GP104
Transmit with full line T101 - IEC
timestamp 60870-5-101
Table 26: DPI - Supported data types

6.4.2 Additional Information

Parameter name Default Parameter location

Put in buffer Enabled data point - line T101/T104

If enabled: value changes will be stored in buffer when host is offline.
If disabled: GI is mandatory to get current value.

Parameter name Default Parameter location

Unstable event filter Disabled data point - line T101/T104

If enabled,
a value change is first forwarded to the connected NCC, if the value is stable for the configured time.
Value range: 1 to 300 seconds.

34 1KGT 150 466 V024 1

Data Types - Monitoring Direction DPI – Double Point Information

6.4.3 Conversion of Values

RTU internal value IEC 60870-5-101

intermediate 11
off 01
on 10
indeterminate 00
Table 27: DPI – Conversion of values

6.4.4 Conversion of Quality Descriptors

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
BL Blocked Blocked
SB Substituted Substituted
NT Not Topical Not Topical
IV Invalid Invalid
Table 28: DPI - Conversion of quality descriptors

6.4.5 Conversion of Causes of Transmission

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
T Test Test
P/N Positive/negative confirmation - Irrelevant -
Cause Spontaneous 3 - spontaneous
Background scan 2 - background scan
Requested 5 - requested
Interrogated 20, 21 ... 36 - interrogated
Table 29: DPI - Conversion of causes of transmission

6.5 EPI – Protection Event Information

Binary process information is indicated by two bits and relative timetag (used by protection relays).

6.5.1 Supported Data Types

IEC 60870-5-101 RTU

ASDU Type iden- Data type Data Parame- Parameter location
tification property type ter name
M_EP_TA_1 <17> with timestamp EPI
CP24Time2a
Table 30: EPI - Supported data types

1KGT 150 466 V024 1 35

EPI – Protection Event Information Data Types - Monitoring Direction

IEC 60870-5-101 RTU

ASDU Type iden- Data type Data Parame- Parameter location
tification property type ter name
M_EP_TD_1 <38> with timestamp EPI Transmit with full line T101- IEC
CP56Time2a timestamp 60870-5-101
Table 30: EPI - Supported data types

6.5.2 Additional information

The EPI contents a elapsed time tag of the protection event with the range of 0..59 999 ms.

Parameter name Default Parameter location

Put in buffer Enabled data point - line T101/T104

If enabled: value changes will be stored in buffer when host is offline.
If disabled: GI is mandatory to get current value.

6.5.3 Conversion of Values

RTU internal value IEC 60870-5-101

intermediate 0
off 1
on 2
indeterminate 3
Table 31: EPI - Conversion of values

6.5.4 Conversion of Quality Descriptors

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
EI Elapsed time valid Elapsed time valid
BL Blocked Blocked
SB Substituted Substituted
NT Not Topical Not Topical
IV Invalid Invalid
Table 32: EPI - Conversion of quality descriptors

6.5.5 Conversion of Causes of Transmission

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
T Test Test
P/N Positive/negative confirmation - Irrelevant -
Cause Spontaneous 3 - spontaneous
Table 33: EPI - Conversion of causes of transmission

36 1KGT 150 466 V024 1

Data Types - Monitoring Direction ITI – Integrated Totals Information

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
Background scan 2 - background scan
Table 33: EPI - Conversion of causes of transmission

6.6 ITI – Integrated Totals Information

Binary process information is indicated by 32 bits as a count value.

6.6.1 Supported Data Types

IEC 60870-5-101 RTU

ASDU Type iden- Data type Data Parame- Parameter location
tification property type ter name
M_IT_NA_1 <15> without time- ITI
stamp
M_IT_TA_1 <16> with timestamp ITI Transmit with ITI - line T101
CP24Time2a timestamp
M_IT_TB_1 <37> with timestamp ITI Transmission ITI - line T101/T104/
CP56Time2a with timestamp GP104
Transmit with full line T101 - IEC
timestamp 60870-5-101
Table 34: ITI - Supported data types

6.6.2 Additional Information

Parameter name Default Parameter location

Put in buffer Enabled data point - line T101/T104

If enabled: value changes will be stored in buffer when host is offline.
If disabled: GI is mandatory to get current value.

6.6.3 Conversion of Values

Range RTU internal value IEC 60870-5-101

Range min. - 2 147 483 648 - 2 147 483 648

0 (from local I/O) 0

... ...
Range max. 2 147 483 647 2 147 483 647
Table 35: ITI - Conversion of values

1KGT 150 466 V024 1 37

ITI – Integrated Totals Information Data Types - Monitoring Direction

6.6.4 Conversion of Quality Descriptors

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
SEQ Sequence number Sequence number
CY Carry Carry
CA Adjusted Adjusted
IV Invalid Invalid
Table 36: ITI - Conversion of quality descriptors

6.6.5 Conversion of Causes of Transmission

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
T Test Test
P/N Positive/negative confirmation - Irrelevant -
Cause Spontaneous 3 - spontaneous
Requested 5 - requested
Interrogated 37, 38 … 41 - interrogated
Table 37: ITI - Conversion of causes of transmission

6.7 MFI – Measured Float Information

32 bit analog process information is used as a measured value in float format.

6.7.1 Supported Data Types

IEC 60870-5-101 RTU

ASDU Type iden- Data type Data Parame- Parameter location
tification property type ter name
M_ME_NC_1 <13> without time- MFI
stamp
M_ME_TC_1 <14> with timestamp MFI Transmit with MFI - line T101
CP24Time2a timestamp
M_ME_TF_1 <36> with timestamp MFI Transmission MFI - line T101/T104/
CP56Time2a with timestamp GP104
Transmit with full Line T101 - IEC
timestamp 60870-5-101
Table 38: MFI - Supported data types

6.7.2 Values

R32–IEEE STD 754

38 1KGT 150 466 V024 1

Data Types - Monitoring Direction MFI – Measured Float Information

6.7.3 Additional Information

Parameter name Default Parameter location

Spontanous transmission enabled data point - Line T101/T104/GP104

if enabled:
Spontaneous transmission of this process data point1)
Background cycle disabled data point - Line T101/T104/GP104
If enabled:
Cyclic transmission of this process data point
out of the process image of the host interface with given cycle time of the background cycle.
Value range: disabled, 1 sec, 2, 4, 5, 8, 10, 16, 30, 60 sec, 2 min, 5 min, 10 min, 15 min1)

1)It
is possible to set both parameters at the same data point. That means that the concerning data
point is directly send to the NCC on every change and additional after the configured time period.

Parameter name Default Parameter location

Put in buffer Enabled data point - line T101/T104

If enabled: value changes will be stored in buffer when host is offline.
If disabled: GI is mandatory to get current value.

6.7.4 Conversion of Values

Range RTU internal value IEC 60870-5-101

Range min. -3.4 x 10e38 -3.4 x 10e38
... ...
Range max. +3.4 x 10e38 +3.4 x 10e38
Table 39: MFI - Conversion of values

6.7.5 Conversion of Quality Descriptors

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
OV Overflow Overflow
BL Blocked Blocked
SB Substituted Substituted
NT Not Topical Not Topical
IV Invalid Invalid
Table 40: MFI - Conversion of quality descriptors

6.7.6 Conversion of Causes of Transmission

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
T Test Test
P/N Positive/negative confirmation - Irrelevant -
Table 41: MFI - Conversion of causes of transmission

1KGT 150 466 V024 1 39

SPI – Single Point Information Data Types - Monitoring Direction

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
Cause Spontaneous 3 - spontaneous
Periodic / cyclic 1 - periodic / cyclic
Background scan 2 - background scan
Requested 5 - requested
Interrogated 20, 21 ... 36 - interrogated
Table 41: MFI - Conversion of causes of transmission

6.8 SPI – Single Point Information

Binary process information is indicated by one bit.

6.8.1 Supported Data Types

IEC 60870-5-101 RTU

ASDU Type iden- Data type Data Parame- Parameter location
tification property type ter name
M_SP_NA_1 <1> without time- SPI
stamp
M_SP_TA_1 <2> with timestamp SPI Transmit with SPI - line T101
CP24Time2a timestamp
M_SP_TB_1 <30> with timestamp SPI Transmission SPI - line T101/T104/
CP56Time2a with timestamp GP104
Transmit with full Line T101 - IEC
timestamp 60870-5-101
Table 42: SPI - Supported data types

6.8.2 Additional Information

Parameter name Default Parameter location

Put in buffer Enabled data point - line T101/T104

If enabled: value changes will be stored in buffer when host is offline.
If disabled: GI is mandatory to get current value.

Parameter name Default Parameter location

Unstable event filter Disabled data point - line T101/T104

If enabled,
a value change is first forwarded to the connected NCC, if the value is stable for the configured time.
Value range: 1 to 300 seconds.

6.8.3 Conversion of Values

RTU internal value IEC 60870-5-101

off 0
Table 43: SPI - Conversion of values

40 1KGT 150 466 V024 1

Data Types - Monitoring Direction SPI – Single Point Information

RTU internal value IEC 60870-5-101

on 1
Table 43: SPI - Conversion of values

6.8.4 Conversion of Quality Descriptors

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
BL Blocked Blocked
SB Substituted Substituted
NT Not Topical Not Topical
IV Invalid Invalid
Table 44: SPI - Conversion of quality descriptors

6.8.5 Conversion of Causes of Transmission

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
T Test Test
P/N Positive/negative confirmation - Irrelevant -
Cause Spontaneous 3 - spontaneous
Background scan 2 - background scan
Requested 5 - requested
Interrogated 20, 21 ... 36 - interrogated
Table 45: SPI - Conversion of causes of transmission

6.9 STI – Step Position Information

Binary process information is indicated by 8 bits.

6.9.1 Supported Data Types

IEC 60870-5-101 RTU

ASDU Type iden- Data type Data Parame- Parameter location
tification property type ter name
M_ST_NA_1 <5> without time- STI
stamp
M_ST_TA_1 <6> with timestamp STI Transmit with STI - line T101
CP24Time2a timestamp
M_ST_TB_1 <32> with timestamp STI Transmission STI - line T101/T104/
CP56Time2a with timestamp GP104

Table 46: STI - Supported data types

1KGT 150 466 V024 1 41

STI – Step Position Information Data Types - Monitoring Direction

IEC 60870-5-101 RTU

ASDU Type iden- Data type Data Parame- Parameter location
tification property type ter name
Transmit with full line T101 - IEC
timestamp 60870-5-101
Table 46: STI - Supported data types

6.9.2 Additional Information

Parameter name Default Parameter location

Put in buffer Enabled data point - line T101/T104

If enabled: value changes will be stored in buffer when host is offline.
If disabled: GI is mandatory to get current value.

6.9.3 Conversion of Values

Range RTU internal value IEC 60870-5-101

Range min. -63 -63
... ...
Range max. +63 +63
Table 47: STI - Conversion of values

6.9.4 Conversion of Quality Descriptors

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
OV Overflow Overflow
BL Blocked Blocked
SB Substituted Substituted
NT Not Topical Not Topical
IV Invalid Invalid
T Transient Bit Transient Bit
Table 48: STI - Conversion of quality descriptors

6.9.5 Conversion of Causes of Transmission

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
T Test Test
P/N Positive/negative confirmation - Irrelevant -
Cause Spontaneous 3 - spontaneous
Background scan 2 - background scan
Table 49: STI - Conversion of causes of transmission

42 1KGT 150 466 V024 1

Data Types - Monitoring Direction STI – Step Position Information

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
Requested 5 - requested
Interrogated 20, 21 ... 36 - interrogated
Table 49: STI - Conversion of causes of transmission

1KGT 150 466 V024 1 43

STI – Step Position Information Data Types - Monitoring Direction

44 1KGT 150 466 V024 1

Data Types - Controlling Direction ASO – Analog Setpoint Output

7 Data Types - Controlling Direction

7.1 ASO – Analog Setpoint Output

Analog process command (16 bit signed number).

7.1.1 Supported Data Types

IEC 60870-5-101 RTU

ASDU Type iden- Data type Data type Parame- Parameter
tification property ter name location
C_SE_NA_1 <48> normalized, with- ASO Transmission ASO - line T101/
out time tag format: Nor- T104/GP104
malized
C_SE_NB_1 <49> scaled, without ASO Transmis- ASO - line T101/
time tag sion format: T104/GP104
Scaled
Table 50: ASO - Supported data types

7.1.2 Command Authority

See also parameter Interlock with local control authority

(Table Interface parameters - IEC 60870-5-101 in chapter Physical Layer (page "2-1"))

7.1.3 Additional Information

Analog set-point output is a persistent output.

7.1.4 Conversion of Values

Range RTU internal value IEC 60870-5-101

Range min. -100 % Normalized: -1

Scaled: -32 768

... ...
Range max. +100 % Normalized: +1-2e-15

Scaled: +32 767

Table 51: ASO - Conversion of values

1KGT 150 466 V024 1 45

ASO – Analog Setpoint Output Data Types - Controlling Direction

7.1.5 Conversion of Qualifier of Command

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
SE Select / Execute Select / Execute

(1 select, 0 execute)
QL default 0 - default
Table 52: ASO - conversion of qualifier of command

ADVICE
All qualifier values are accepted for local control points.

7.1.6 Conversion of Causes of Transmission

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
T Test Ignored
P/N Positive/negative confirmation Relevant in monitor direction
only
Cause Activation 6 - Activation
Activation Confirmation 7 - Activation Confirmation
Deactivation 8 - Deactivation
Deactivation Confirmation 9 - Deactivation Confirmation
Activation Termination 10 - Activation Termination
Negative Confirmation 45 … 47 - Unknown
Table 53: ASO - Conversion of causes of transmission

7.2 BSO – Bit String Output

Binary process command (1, 2, 8, 16, 32 bit unsigned number).

7.2.1 Supported Data Types

IEC 60870-5-101 RTU

ASDU Type iden- Data type Data type Parame- Parameter
tification property ter name location
C_BO_NA_1 <51> without time tag BSO
Table 54: BSO - Supported data types

7.2.2 Command Authority

See also parameter Interlock with local control authority

46 1KGT 150 466 V024 1

Data Types - Controlling Direction BSO – Bit String Output

(Table Interface parameters - IEC 60870-5-101 in chapter Physical Layer (page "2-1"))

7.2.3 Additional Information

Always persistent output. A new command with value 0 (all bits) has to be generated.

7.2.4 Conversion of Values

Range RTU internal value IEC 60870-5-101

Range min. 0 0
... ...
Range max. 4 294 967 295 4 294 967 295
Table 55: BSO - Conversion of values

7.2.5 Conversion of Qualifier of Command

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
SE only direct execute only direct execute
Table 56: BSO - conversion of qualifier of command

7.2.6 Conversion of Causes of Transmission

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
T Test Ignored
P/N Positive/negative confirmation Relevant in monitor direction
only
Cause Activation 6 - Activation
Activation Confirmation 7 - Activation Confirmation
Activation Termination 10 - Activation Termination
Negative Confirmation 45 … 47 - Unknown
Table 57: BSO - Conversion of causes of transmission

7.3 DCO – Double Command Output

Binary process command (two bits).

1KGT 150 466 V024 1 47

DCO – Double Command Output Data Types - Controlling Direction

7.3.1 Supported Data Types

IEC 60870-5-101 RTU

ASDU Type iden- Data type Data Parame- Parameter location
tification property type ter name
C_DC_NA_1 <46> without time- DCO
stamp
Table 58: DCO - Supported data types

7.3.2 Command Authority

See also parameter Interlock with local control authority

(Table Interface parameters - IEC 60870-5-101 in chapter Physical Layer (page "2-1"))

7.3.3 Additional Information

None

7.3.4 Conversion of Values

RTU internal value IEC 60870-5-101

off 01
on 10
Table 59: DCO - Conversion of values

7.3.5 Conversion of Qualifier of Command

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
SE Select / Execute Select / Execute

(1 select, 0 execute)
QU default 0 - no additional definition
overwritten for local I/O by com- 1 - short pulse duration
mand output duration parame-
ter
overwritten for local I/O by com- 2 - long pulse duration
mand output duration parame-
ter
overwritten for local I/O by com- 3 - persistent output
mand output type parameter
Table 60: DCO - conversion of qualifier of command

48 1KGT 150 466 V024 1

Data Types - Controlling Direction DCO – Double Command Output

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
IEC61850 client: function is 9... 15 - reserved for the selec-
used to specify command check tion of other predefined functions
attributes
Table 60: DCO - conversion of qualifier of command

ADVICE
All qualifier values are accepted for local control points.

7.3.6 Conversion of Causes of Transmission

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
T Test Ignored
P/N Positive/negative confirmation Relevant in monitor direction
only
Cause Activation 6 - Activation
Activation Confirmation 7 - Activation Confirmation
Deactivation 8 - Deactivation
Deactivation Confirmation 9 - Deactivation Confirmation
Activation Termination 10 - Activation Termination
Negative Confirmation 45 … 47 - Unknown
Table 61: DCO - Conversion of causes of transmission

7.4 DSO – Digital Setpoint Output

Binary process command (8 or 16 bit signed number).

7.4.1 Supported Data Types

IEC 60870-5-101 RTU

ASDU Type iden- Data type Data type Parame- Parameter
tification property ter name location
C_SE_NA_1 <48> normalized, with- DSO Transmission DSO - line T101/
out time tag format: Nor- T104/GP104
malized
C_SE_NB_1 <49> scaled, without DSO Transmis- DSO - line T101/
time tag sion format: T104/GP104
Scaled
Table 62: DSO - Supported data types

1KGT 150 466 V024 1 49

DSO – Digital Setpoint Output Data Types - Controlling Direction

7.4.2 Command Authority

See also parameter Interlock with local control authority

(Table Interface parameters - IEC 60870-5-101 in chapter Physical Layer (page "2-1"))

7.4.3 Additional Information

Digital set-point output is a persistent output.

7.4.4 Conversion of Values

Range RTU internal value IEC 60870-5-101

Range min. -100 % -1
... ...
Range max. +100 % +1-2e-15
Table 63: DSO - Conversion of values

7.4.5 Conversion of Qualifier of Command

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
SE Select / Execute Select / Execute

(1 select, 0 execute)
QL default 0 - default
Table 64: DSO - conversion of qualifier of command

ADVICE
All qualifier values are accepted for local control points.

7.4.6 Conversion of Causes of Transmission

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
T Test Ignored
P/N Positive/negative confirmation Relevant in monitor direction
only
Cause Activation 6 - Activation
Activation Confirmation 7 - Activation Confirmation
Deactivation 8 - Deactivation
Deactivation Confirmation 9 - Deactivation Confirmation
Activation Termination 10 - Activation Termination
Table 65: DSO - Conversion of causes of transmission

50 1KGT 150 466 V024 1

Data Types - Controlling Direction FSO – Floating Point Setpoint Output

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
Negative Confirmation 45 … 47 - Unknown
Table 65: DSO - Conversion of causes of transmission

7.5 FSO – Floating Point Setpoint Output

Floating point process command (32 bit short floating point number)

7.5.1 Supported Data Types

IEC 60870-5-101 RTU

ASDU Type iden- Data type Data type Parame- Parameter
tification property ter name location
C_SE_NC_1 <50> without time tag FSO
Table 66: FSO - Supported data types

7.5.2 Command Authority

See also parameter Interlock with local control authority

(Table Interface parameters - IEC 60870-5-101 in chapter Physical Layer (page "2-1"))

7.5.3 Additional Information

None

7.5.4 Conversion of values

Range RTU internal value IEC 60870-5-101

Range min. -3.4 x 10e38 -3.4 x 10e38
... ...
Range max. +3.4 x 10e38 +3.4 x 10e38
Table 67: FSO - Conversion of values

7.5.5 Conversion of Qualifier of Command

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
SE Select / Execute Select / Execute

(1 select, 0 execute)
QL default 0 - default
Table 68: FSO - conversion of qualifier of command

1KGT 150 466 V024 1 51

FSO – Floating Point Setpoint Output Data Types - Controlling Direction

ADVICE
All qualifier values are accepted for local control points.

7.5.6 Conversion of Causes of Transmission

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
T Test Ignored
P/N Positive/negative confirmation Relevant in monitor direction
only
Cause Activation 6 - Activation
Activation Confirmation 7 - Activation Confirmation
Deactivation 8 - Deactivation
Deactivation Confirmation 9 - Deactivation Confirmation
Activation Termination 10 - Activation Termination
Negative Confirmation 45 … 47 - Unknown
Table 69: FSO - Conversion of causes of transmission

7.6 RCO – Regulation Command Output

Regulation step command (two bits).

7.6.1 Supported Data Types

IEC 60870-5-101 RTU

ASDU Type iden- Data type Data type Parame- Parameter
tification property ter name location
C_RC_NA_1 <47> without time tag RCO
Table 70: RCO - Supported data types

7.6.2 Command Authority

See also parameter Interlock with local control authority

(Table Interface parameters - IEC 60870-5-101 in chapter Physical Layer (page "2-1"))

7.6.3 Additional Information

Regulation step commands are in principle retriggerable commands.

In order to retrigger a running two step regulation command, it is not necessary to resend the
command Select.

52 1KGT 150 466 V024 1

Data Types - Controlling Direction RCO – Regulation Command Output

7.6.4 Conversion of Values

RTU internal value IEC 60870-5-101

Lower 01
Higher 10

Table 71: RCO - Conversion of values

7.6.5 Conversion of Qualifier of Command

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
SE Select / Execute Select / Execute

(1 select, 0 execute)
QU default 0 - no additional definition
overwritten for local I/O by com- 1 - short pulse duration
mand output duration parame-
ter
overwritten for local I/O by com- 2 - long pulse duration
mand output duration parame-
ter
overwritten for local I/O by com- 3 - persistent output
mand output type parameter
IEC61850 client: function is 9... 15 - reserved for the selec-
used to specify command check tion of other predefined functions
attributes
Table 72: RCO - conversion of qualifier of command

ADVICE
All qualifier values are accepted for local control points.

7.6.6 Conversion of Causes of Transmission

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
T Test Ignored
P/N Positive/negative confirmation Relevant in monitor direction
only
Cause Activation 6 - Activation
Activation Confirmation 7 - Activation Confirmation
Deactivation 8 - Deactivation
Deactivation Confirmation 9 - Deactivation Confirmation
Activation Termination 10 - Activation Termination
Table 73: RCO - Conversion of causes of transmission

1KGT 150 466 V024 1 53

SCO – Single Command Output Data Types - Controlling Direction

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
Negative Confirmation 45 … 47 - Unknown
Table 73: RCO - Conversion of causes of transmission

7.7 SCO – Single Command Output

Binary process command (one bit).

7.7.1 Supported Data Types

IEC 60870-5-101 RTU

ASDU Type iden- Data type Data Parame- Parameter location
tification property type ter name
C_SC_NA_1 <45> without time- SCO
stamp
Table 74: SCO - Supported data types

7.7.2 Command Authority

See also parameter Interlock with local control authority

(Table Interface parameters - IEC 60870-5-101 in chapter Physical Layer (page "2-1"))

7.7.3 Additional Information

Commands send with qualifier persistent output (3) are replied only with activation confirmation, no
activation termination is send.

7.7.4 Conversion of Values

RTU internal value IEC 60870-5-101

off 0
on 1
Table 75: SCO - Conversion of values

7.7.5 Conversion of Qualifier of Command

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
SE Select / Execute Select / Execute
Table 76: SCO - conversion of qualifier of command

54 1KGT 150 466 V024 1

Data Types - Controlling Direction SCO – Single Command Output

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
(1 select, 0 execute)
QU default 0 - no additional definition
overwritten for local I/O by com- 1 - short pulse duration
mand output duration parame-
ter
overwritten for local I/O by com- 2 - long pulse duration
mand output duration parame-
ter
overwritten for local I/O by com- 3 - persistent output
mand output type parameter
IEC61850 client: function is 9... 15 - reserved for the selec-
used to specify command check tion of other predefined functions
attributes
Table 76: SCO - conversion of qualifier of command

ADVICE
All qualifier values are accepted for local control points.

7.7.6 Conversion of Causes of Transmission

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
T Test Ignored
P/N Positive/negative confirmation Relevant in monitor direction
only
Cause Activation 6 - Activation
Activation Confirmation 7 - Activation Confirmation
Deactivation 8 - Deactivation
Deactivation Confirmation 9 - Deactivation Confirmation
Activation Termination 10 - Activation Termination
Negative Confirmation 45 … 47 - Unknown
Table 77: SCO - Conversion of causes of transmission

1KGT 150 466 V024 1 55

SCO – Single Command Output Data Types - Controlling Direction

56 1KGT 150 466 V024 1

Transparent Data Transparent data channel

8 Transparent Data
In automation systems may be required information that is not mapped to the IEC 60870-5-101
protocol. This information includes several device specific parameters etc.

Several type identifications of the private range have been selected to enable transparent data
transfer through the RTU500 series RTU to subordinated devices.

8.1 Transparent data channel

8.1.1 Command direction

With the Transparent Data Message C_TD_NA_1 the Controlling Station is able to request data
from subordinate devices through the RTU500 series.

The Type Ident is 145, ASDU address and the Information object address must be configured in
RTUtil500.

The Transparent Data Message C_TD_NA_1 will be answered from the RTU by sending the
message back to Controlling Station with Cause of Transmission 7 (activation confirmation).

When the message is accepted by the RTU (message can be processed by the RTU and device
answers to the request message), the RTU sends a “positive confirmation” ACTCON, otherwise
(message cannot be processed by the RTU) the RTU sends a “negative confirmation” ACTCON.

Every transparent data command is checked on ASDU address, information object address and “No
of Data Bytes in Current Segment“.

If the ASDU address or information object address does not match to the configuration in RTUtil500
or the “No of Data Bytes in Current Segment” is higher than 200, the command is confirmed
negative.

1KGT 150 466 V024 1 57

Transparent data channel Transparent Data

Figure 5: ASDU Type 145

8.1.2 Monitoring direction

With the Transparent Data Response M_TD_NA_1, the RTU is able to transmit any data as
transparent data to a Controlling Station.

The Type Ident is 146, theLink address, ASDU address and the Information object address must be
configured by RTUtil500. They are equal to the one used in command direction.

The maximum amount of segments is 255, each of them contains up to 200 data bytes.

If all data can be sent in one message (data segmentation not necessary), the contents of both
segmentation control fields are set to 1.

58 1KGT 150 466 V024 1

Transparent Data Transparent data channel

Figure 6: ASDU Type 146

8.1.3 Request procedure

Figure 7: Request procedure

1KGT 150 466 V024 1 59

Encapsulated SPAbus messages Transparent Data

8.2 Encapsulated SPAbus messages

8.2.1 General

With the Transparent Data Message C_SB_NA_1 the Controlling Station is able to request data and
execute commands of a SPAbus device connected to a subordinate device through the RTU560.

The Type Ident is 133, the ASDU address and the Information object address must be configured in
RTUtil500.

The Transparent Data Message C_SB_NA_1 will be answered from RTU by sending the message
back to Central System with Cause of Transmission 7 (activation confirmation).

When the message is accepted by the subordinate device (Device answers to the request
message), the RTU sends a "positive confirmation" ACTCON with the reply data included,
otherwise (message cannot be processed) the RTU sends a "negative confirmation" ACTCON.

Every transparent data command is checked on ASDU address, information object address and “No
of Data Bytes in Current Segment“.

If the ASDU address, information object address or “No of Data Bytes” does not match to the
configuration in RTUtil500, the command is confirmed negative.

Figure 8: ASDU Type 133

60 1KGT 150 466 V024 1

Transparent Data Encapsulated SPAbus messages

8.2.2 Request procedure

Figure 9: Request procedure

1KGT 150 466 V024 1 61

Encapsulated SPAbus messages Transparent Data

62 1KGT 150 466 V024 1

File Transfer Supported data types

9 File Transfer
The file transfer is used for exchanging files between a control center and a RTU500 series or a
subordinated device.

Before starting file transfer to an RTU, the control center can deactivate the RTU (stop periodic
measurements), in order to have highest possible bandwidth for the file transfer. If no new
configuration files are loaded into the RTU between deactivation and reset command, the RTU
restarts with the same configuration data as before.

If a file transfer is started without preceding deactivation command, the RTU will continue its normal
operation during the complete file transfer process. The downloaded configuration will become
active only after a restart of the RTU.

The file name in the protocol is fixed for the following supported file types to 1 (transparent file).

Supported file types:

• RCD configuration file

• PRO configuration file (PLC boot project file)
• Disturbance recorder of various protocols and device types. See corresponding SCI description
for details.
• UNDEF file not specified in greater detail
The name of file in the protocol for ‘Sequence of events’ is 3 and ‘Sequence of analog values’ is 4.

• Sequence of events file

• Sequence of recorded analog values file

9.1 Supported data types

IEC 60870-5-101 RTU
ASDU Type iden- Data type Data type Parame- Parameter
tification property ter name location
F_FR_NA_1 <120>
F_SR_NA_1 <121>
F_SC_NA_1 <122>
F_LS_NA_1 <123>
F_AF_NA_1 <124>
F_SG_NA_1 <125>
F_DR_TA_1 <126>
Table 78: File transfer - Supported data types

9.2 Values
None.

9.3 Command Authority

None

1KGT 150 466 V024 1 63

Additional information File Transfer

9.4 Additional information

F_DR_TA_1 cannot be generated by RTU500 series, but routed to/from subordinated devices.

9.5 Conversion of causes of transmission

RTU IEC 60870-5-101
Internal commu- Internal communication (long) Communication
nication (short)
T Test Ignored
P/N Positive/negative confirmation Relevant in monitor direction only
Cause Spontaneous 3 – spontaneous (126)
Requested 5 – requested (122, 126)
File transfer 13 - file transfer
Table 79: File transfer - Conversion of causes of transmission

9.6 Download
The download of configuration files does not trigger any restarting mechanism in the RTU500
series. For activating the new configuration file, the control center has to issue a Reset Process
Command (C_RP_NA_1, ASDU 105) after writing the files to the RTU500 series.

The RCD configuration file is distributed to every CMU board in the system concerned after
download is completed. Configuration file distribution will only be done, if the file belongs to the
RTU itself. Otherwise the file transfer will only be routed to the subordinated device it belongs to. In
this case the file transfer handling is done by the subordinated device (e.g. a RTU of the RTU500
series).

PRO configuration file is only stored local these download is completed. This means, that PLC
functions using this configuration file has to be located on the same CMU-board where the host
communication interface handling the file transfer is located.

The distribution is done between the message F_LS_NA_1 and the message F_AF_NA_1 and may
last a couple of seconds.

The message F_AF_NA_1 is only acknowledged positive, when file transfer and file distribution was
successful. If a file transfer to a RTU500 series is confirmed negative, the downloaded file was not
stored and the previous file is not deleted or overwritten.

9.7 Upload
All supported file types can also be uploaded from a RTU of the RTU500 series or an IED.

See documentation of the relevant subdevice communication interface for support of (disturbance)
file upload.

64 1KGT 150 466 V024 1

File Transfer Transmission of sequences of events

9.8 Transmission of sequences of events

9.8.1 Scope of operation

Sequences of events (SOE) (for example single point information, double point information
measured values, integrated totals) acquired in a controlled station are transmitted via the file
transfer defined in IEC 60870-5-5 and IEC 60870-5-101.ed.2 (2003) (chapter 7.4.11.3) when
onward transmission to the controlling station is required.

ASDUs with the following type identifications may be transmitted as spontaneous digital information:

<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 bit 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 value 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
Table 80: Supported ASDUs

ASDUs with the following type identifications are not supported:

<39> Packed start events of protection equipment with time tag M_EP_TE_1
CP56Time2a
<40> Packed output circuit information of protection equipment with time M_EP_TF_1
tag CP56Time2a
Table 81: Not supported ASDUs

The variable structure qualifier is set to 1, i.e. only one information object is transmitted per ASDU.

9.8.2 Engineering in RTUtil500

Recording and transmission of sequences of events are only activated, if preconfigured in

RTUtil500.

Transmission of sequences of events (spontaneous digital events) is activated by configuring one

FTR object of file type 'Sequence of events' in the Hardware Tree. It is possible to configure a single
FTR of file type 'Sequence of events' as child of an FDR object (file type 'UNDEF') but not as child
of the RTU itself. By enabling the FTR of file type 'Sequence of events' (setting 'In use') for a HCI
the FTR is activated.

The FTR object contains the parameters Max. contained ASDUs and Sections per file. The product
of both parameters defines the number of recorded events buffered including the point of time at
which they are acquired. If the predefined product is exceeded the RTU informs spontaneously the
controlling station about an available file for transfer. The parameter Max. contained ASDUs has a
value range from 1 to 5 000 and the default value is 1 000. The parameter Sections per file has a
value range from 1 to 100 and the default value is 1.

RTU objects of type SPI, DPI, STI, BSIx, AMI, DMI, MFI, ITI, EPI, SEV offer the checkbox Include in
sequence of event file. If enabled events will be recorded and transmitted to the controlling station
via file transfer.

1KGT 150 466 V024 1 65

Transmission of sequences of events File Transfer

9.8.3 Runtime procedure

The structure of the record of sequences of events in a section of a file is composed according
IEC 60870-5-101.ed.2 (2003) (chapter 7.4.11.3.1). The transmission procedures are performed
according IEC 60870-5-101.ed.2 (2003) (chapter 7.4.11.3.2).

FTR of file type 'Sequence of events' is available as volatile file / memory area, i.e. after RTU restart
the file is available for transfer after the above described buffer limit is exceeded.

FTR requests of file type 'Sequence of events' are supported only by one requester at the same
time.

9.9 Transmission of sequences of recorded analog

values
9.9.1 Scope of operation

Sequences of recorded analog values (for example, measured values, integrated totals) acquired
in a controlled station are transmitted via the file transfer defined in IEC 60870-5-5 and IEC
60870-5-101.ed.2 (2003) (chapter 7.4.11.4) when onward transmission to the controlling station is
required.

The following information elements may be transmitted as sequences of recorded analog values:

• binary counter reading (ITI)

• normalized value with quality descriptor (AMI and DMI).

9.9.2 Engineering in RTUtil500

Recording and transmission of sequences of analog values are only activated, if preconfigured in
RTUtil500.

Transmission of sequences of recorded analog values is activated by configuring one FTR object
of file type 'Sequence of recorded analog values' in the Hardware Tree. It is possible to configure
a single FTR of file type 'Sequence of recorded analog values' as child of an FDR object (file type
'UNDEF') but not as child of the RTU itself. By enabling the FTR of file type 'Sequence of recorded
analog values' (setting 'In use') for a HCI the FTR is activated.

The time interval between information elements is to be calculated as product of the factor <1..255>
and the time base in <seconds, minutes or hours>. The result of this calculation has to be converted
in seconds for configuration in RTUtil500. The FTR object contains the parameter Time interval for
setting the time interval for data recording. The resolution of parameterTime interval is seconds
and the value range is from 1 to 918 000 seconds (=255 hours). Default value of parameter Time
interval is 10 seconds.

The FTR object contains the parameter Max. contained information elements of a record identifier.
That parameter determines the number of buffered information elements. If this parameters is
exceeded the RTU informs spontaneously the controlling station about an available file for transfer.
The parameter has a value range from 1 to 3 600 and the default value is 300.

RTU objects of type AMI, DMI and ITI offer the checkbox Include in sequence of recorded analog
value file. If enabled the values will be recorded and transmitted via file transfer. Enclosed is the
parameter Record identifier defining a unique value for identifying the set of information elements
(normalized values or counter readings), i.e. the address of the complete sequence of recorded

66 1KGT 150 466 V024 1

File Transfer Transmission of sequences of recorded analog values

analog values. Value range is from 1 to 65 535. The parameter Record identifier is sensitive only, if
parameter Include in sequence of recorded analog value file is enabled.

9.9.3 Runtime procedure

The structure of data files containing sequences of recorded analog values is composed according
IEC 60870-5-101.ed.2 (2003) (chapter 7.4.11.4.1). The transmission procedures are performed
according IEC 60870-5-101.ed2003 (chapter 7.4.11.4.2).

FTR of file type 'Sequence of recorded analog values' is available as volatile file / memory area, i.e.
after RTU restart the file is available for transfer after the above described buffer limit is exceeded.

FTR requests of file type 'Sequence of recorded analog value' are supported only by one requester
at the same time.

1KGT 150 466 V024 1 67

Transmission of sequences of recorded analog values File Transfer

68 1KGT 150 466 V024 1

Internal Functions General Interrogation

10 Internal Functions

10.1 General Interrogation

The general interrogation includes single point information, double point information, step positions,
measured values, bit strings and RTU system events, whereas integrated totals are excluded. The
interrogation of a selected part of the process information by a group interrogation is supported.
The process values transmitted in the course of the interrogation are marked with the cause of
transmission 20 (General Interrogation) or 21 to 36.

When events occur during the general interrogation, the General Interrogation is interrupted, and
the events are transmitted immediately.

10.1.1 Supported Data Types

IEC 60870-5-101 RTU

ASDU Type iden- Data type Data type Parame- Parameter
tification property ter name location
C_IC_NA_1 <100>
Table 82: General Interrogation - Supported data types

10.1.2 Values

20, 21 … 36

10.1.3 Command Authority

None

10.1.4 Additional information

The general interrogation is responded from the HCI’s process image.

10.1.5 Conversion of Quality Descriptors

RTU IEC 60870-5-101

Internal commu- Internal commu- Communication
nication (short) nication (long)
QOI Qualifier of Interrogation 20 – General interrogation

21 – Interrogation Group 1

22 – Interrogation Group 2

36 – Interrogation Group 16
Table 83: General Interrogation - Conversion of quality descriptors

1KGT 150 466 V024 1 69

General Interrogation Internal Functions

10.1.6 Conversion of Causes of Transmission

RTU IEC 60870-5-101

Internal commu- Internal commu- Communication
nication (short) nication (long)
T Test Ignored
P/N Positive/negative confirma- Relevant in monitor direction only
tion
Cause Activation 6 - Activation
Activation Confirmation 7 - Activation Confirmation
Activation Termination 10 - Activation Termination
Negative Confirmation 45 … 47 - Unknown
Table 84: General Interrogation - Conversion of causes of transmission

A General Interrogation (with QOI=20) can be generated also by the Function Block GI_OUT of a
PLC program. All process data points will be transmitted to the NCC with COT=20.

10.2 Counter Interrogation Command

Process command to interrogate a binary counter

10.2.1 Supported data types

IEC 60870-5-101 RTU

ASDU Type iden- Data type Data Parame- Parameter location
tification property type ter name
C_IC_NA_1 <101>
Table 85: Counter Interrogation Command - Supported data types

10.2.2 Values

0…5

10.2.3 Command Authority

None

10.2.4 Additional information

The link address must be same as used for system events.

The ASDU address must be same. Broadcast address is not supported.

The information object address must be zero.

If link, ASDU or information object address does not match, the command is confirmed negative.

Only counter data of the local PDP is readable. The counter interrogation command for
subordinated devices is not supported.

70 1KGT 150 466 V024 1

Internal Functions Counter Interrogation Command

10.2.5 Conversion of quality descriptors

RTU IEC 60870-5-101

Internal commu- Internal commu- Communication
nication (short) nication (long)
RQT No counter requested 0 - No counter requested

request counter group 1 1 - request counter group 1

request counter group 2 2 - request counter group 2

request counter group 3 3 - request counter group 3

request counter group 4 4 - request counter group 4

general request counter 5 - general request counter

FRZ No freeze or reset 0 - No freeze or reset

counter freeze without reset 1 - counter freeze without reset

counter freeze with reset 2 - counter freeze with reset

counter reset 3 - counter reset

Table 86: Counter Interrogation Command - Conversion of quality descriptors

10.2.6 Conversion of causes of transmission

RTU IEC 60870-5-101

Internal commu- Internal commu- Communication
nication (short) nication (long)
T Test Ignored
P/N Positive/negative confirma- Relevant in monitor direction only
tion
Cause Activation 6 - Activation
Activation Confirmation 7 - Activation Confirmation
Activation Termination 10 - Activation Termination
Negative Confirmation 45 … 47 - Unknown
Table 87: Counter Interrogation Command - Conversion of causes of transmission

10.3 Read Command

Process command to read a specific data point.

10.3.1 Supported data types

IEC 60870-5-101 RTU

ASDU Type iden- Data type Data type Parame- Parameter
tification property ter name location
C_RD_NA_1 <102>
Table 88: Read Command - Supported data types

1KGT 150 466 V024 1 71

Read Command Internal Functions

10.3.2 Values

None.

10.3.3 Command Authority

None

10.3.4 Additional information

The process data point with the link, ASDU and information object address of the C_RD_NA_1
command is read and send to NCC with cause of transmission requested.

The timestamp of the process data point is the actual time of the RTU.

10.3.5 Conversion of quality descriptors

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
SE Select / Execute Only S/E = 0 (execute) supported
Table 89: Read Command - Conversion of quality descriptors

10.3.6 Conversion of causes of transmission

RTU IEC 60870-5-101

Internal commu- Internal commu- Communication
nication (short) nication (long)
T Test Ignored
P/N Positive/negative confirmation Relevant in monitor direction only
Cause Request 5 - Request
Negative Confirmation 45 … 47 - Unknown
Table 90: Read Command - Conversion of caused of transmission

10.4 Time Synchronization

The RTU500 series supports different methods of time synchronization. The time synchronization
can be done via the communication line with the protocol IEC 60870-5-101.

The eight time masters have their own priority. If a higher prior master will fail, the time master with
the lower priority will synchronize the RTU. If the higher prior time master is available again, he will
continue synchronizing.

Parameter name Default Parameter location

Time administration Not used RTU Parameters

Primary device for time synchronization. This device is always allowed to synchronize the RTU if availble. If not, the next device is
used.

72 1KGT 150 466 V024 1

Internal Functions Time Synchronization

10.4.1 Supported Data Types

IEC 60870-5-101 RTU

ASDU Type iden- Data type Data type Parame- Parameter
tification property ter name location
C_CS_NA_1 <103>
Table 91: Time Synchronization - Supported data types

10.4.2 Values

Complete time and date information in CP56Time2a format.

10.4.3 Command Authority

None

10.4.4 Additional information

Time Synchronization is configurable.

Parameter: Time interval of clock synchronization commands.

(siehe Tabelle Linienparameter - IEC 60870-5-101 in chapter " 3-1").

10.4.5 Conversion of Causes of Transmission

RTU IEC 60870-5-101

Internal commu- Internal commu- Communication
nication (short) nication (long)
T Test Ignored
P/N Positive/negative confirma- Relevant in monitor direction only
tion
Cause Activation 6 - Activation
Activation Confirmation 7 - Activation Confirmation
Spontaneous 3 - Spontaneous
Negative Confirmation 45 … 47 - Unknown
Table 92: Time synchronization - Conversion of causes of transmission

10.5 Test Command

Process command to test a HCI of RTU500 series.

1KGT 150 466 V024 1 73

Test Command Internal Functions

10.5.1 Supported data types

IEC 60870-5-101 RTU

ASDU Type iden- Data type Data type Parame- Parameter
tification property ter name location
C_TS_NA_1 <104>
Table 93: Test Command - Supported data types

10.5.2 Values

0x55AA

10.5.3 Command Authority

None

10.5.4 Additional Information

None

10.5.5 Conversion of quality descriptors

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
SE Select / Execute Only S/E = 0 (execute) supported
Table 94: Test Command - Conversion of quality descriptors

10.5.6 Conversion of causes of transmission

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
T Test Ignored
P/N Positive/negative confirma- Relevant in monitor direction
tion
Cause Activation 6 - Activation
Activation Confirmation 7 - Activation Confirmation
Negative Confirmation 45 … 47 - Unknown
Table 95: Test Command - Conversion of causes of transmission

10.6 Reset Command

Process command to reset the RTU500 series RTU.

74 1KGT 150 466 V024 1

Internal Functions Reset Command

10.6.1 Supported data types

IEC 60870-5-101 RTU

ASDU Type iden- Data type Data type Parame- Parameter
tification property ter name location
C_RP_NA_1 <105>
Table 96: Reset Command - Supported data types

10.6.2 Values

10.6.3 Command Authority

None

10.6.4 Additional information

The reset process command is not acknowledged.

The reset process command will be routed to a subdevice communication interface, if necessary.

10.6.5 Conversion of quality descriptors

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
SE Select / Execute Only S/E = 0

(execute) supported
Table 97: Reset Command - Conversion of quality descriptors

10.6.6 Conversion of causes of transmission

RTU IEC 60870-5-101

Internal Internal Communication
communication (short) communication (long)
T Test Ignored
P/N Not used Not relevant
Cause REMOTE_RESET Not relevant
Table 98: Reset Command - Conversion of causes of transmission

10.7 Deactivate Command

Process command to deactivate the host communication interface of the RTU500 series.

1KGT 150 466 V024 1 75

Deactivate Command Internal Functions

10.7.1 Supported data types

IEC 60870-5-101 RTU

ASDU Type iden- Data type Data Parame- Parameter location
tification property type ter name
C_RP_NA_1 <105>
Table 99: Deactivate Command - Supported data types

10.7.2 Values

128

10.7.3 Command Authority

None

10.7.4 Additional information

The Deactivate Command stops the transmission of periodic measurements, process commands
are negative acknowledged (ACTCON neg).

Spontaneous informations (including Integrated Totals) are still sent.

10.7.5 Conversion of quality descriptors

RTU IEC 60870-5-101

Internal commu- Internal commu- Communication
nication (short) nication (long)
SE Select / Execute Only S/E = 0 (execute) supported
Table 100: Deactivate Command - Conversion of quality descriptors

10.7.6 Conversion of causes of transmission

RTU IEC 60870-5-101

Internal commu- Internal commu- Communication
nication (short) nication (long)
T Test Ignored
P/N Not used Not relevant
Cause Activation 6 - Activation
Activation Confirmation 7 - Activation Confirmation
Negative Confirmation 45 … 47 - Unknown
Table 101: Deactivate Command - Conversion of causes of transmission

76 1KGT 150 466 V024 1

Internal Functions Delay Acquisition Command

10.8 Delay Acquisition Command

10.8.1 Supported data types

IEC 60870-5-101 RTU

ASDU Type iden- Data type Data Parame- Parameter location
tification property type ter name
C_CD_NA_1 <106>
Table 102: Delay Acquisition Command - Supported data types

10.8.2 Values

Two octet binary time CP16Time2a.

10.8.3 Command Authority

None

10.8.4 Additional Information

None

10.8.5 Conversion of quality descriptors

RTU IEC 60870-5-101

Internal commu- Internal commu- Communication
nication (short) nication (long)
SE Select / Execute Only S/E = 0 (execute) supported
Table 103: Delay Acquisition Command - Conversion of quality descriptors

10.8.6 Conversion of causes of transmission

RTU IEC 60870-5-101

Internal commu- Internal commu- Communication
nication (short) nication (long)
T Test Ignored
P/N Not used Used in monitoring direction only
Cause Spontaneous 3 - Spontaneous
Activation 6 - Activation
Activation Confirmation 7 - Activation Confirmation
Negative Confirmation 45 … 47 - Unknown
Table 104: Delay Acquisition Command - Conversion of causes of transmission

1KGT 150 466 V024 1 77

Parameter Loading Internal Functions

10.9 Parameter Loading

Parameter loading is used to change parameters of measured values, which are locally connected
to the analog input boards of the RTU500 series. A routing to subordinated devices is not supported
by RTU500 series.

Parameter loading is enabled per default. Deviating from standard in RTU500 the IOA used to carry
information in control and monitor direction are the same for the parameter types.

Parameter name Default Parameter location

Parameter Loading Enabled Line T101/104

If enabled: Parameter loading requests are supported. If disabled: Parameter loading requests will be responded negative.

To achieve full conformity with standard parameter loading can be disabled. If parameter loading is
disabled request will be responded with negative activation confirmation.

10.9.1 Supported data types

IEC 60870-5-101 RTU

ASDU Type iden- Data type Data Parame- Parameter location
tification property type ter name
P_ME_NA_1 <110> Parameter sent
as a normalized
value
P_ME_NB_1 <111> Parameter sent
as a scaled
value
P_ME_NC_1 <112> Parameter sent
as a floating
point value
Table 105: Parameter Loading - Supported data types

10.9.2 Command Authority

None

10.9.3 Additional Information

None

10.9.4 Conversion of Values for Threshold

Range RTU internal value IEC 60870-5-101 value

Range min. 1% Normalized: 328

Scaled: 10

Floating point: 1.0

... ...
Table 106: Parameter Loading - Conversion of values for threshold

78 1KGT 150 466 V024 1

Internal Functions Parameter Loading

Range RTU internal value IEC 60870-5-101 value

Range max. +12 % Normalized: 3 933

Scaled: 120

Floating point: 12.0

Table 106: Parameter Loading - Conversion of values for threshold

ADVICE
Values for Normalized type are accepted in continuous range but rounded to 0.1% of maximal
value.

10.9.5 Conversion of values for smoothing

Range RTU internal value IEC 60870-5-101 value

Range min. 1 Normalized: not available

Scaled: 1

Floating point: 1.0

... ...
Range max. 128 Normalized: not available

Scaled: 128

Floating point: 128.0

Table 107: Parameter Loading - Conversion of values for smoothing

The following values are processed: 1, 2, 4, 8, 16, 32, 64, 128

10.9.6 Conversion of qualifier of parameter of measured values

RTU IEC 60870-5-101

Internal commu- Internal communication (long) Communication
nication (short)
QPM Threshold Value 1 – Threshold value
Smoothing factor 2 – Smoothing factor
Table 108: Parameter Loading - Conversion of qualifier of parameter of measured values

10.9.7 Conversion of causes of transmission

RTU IEC 60870-5-101

Internal commu- Internal commu- Communication
nication (short) nication (long)
P/N Not used Relevant in monitor direction only
Cause Activation 6 - Activation
Activation Confirmation 7 - Activation Confirmation
Table 109: Parameter Loading - Conversion of causes of transmission

1KGT 150 466 V024 1 79

System Events Internal Functions

RTU IEC 60870-5-101

Internal commu- Internal commu- Communication
nication (short) nication (long)
Negative Confirmation 45 … 47 - Unknown
Table 109: Parameter Loading - Conversion of causes of transmission

10.10 System Events

The host interface manages internal status messages of the RTU500 series. These status
messages can be created from the host itself or other activities of the RTU500 series. The system
events of other activities are sent via internal communication and are processed by the HCI.

Parameter name Default Parameter location

Fix SEV address schema enabled SDI - line

Value range: enabled/ disabled
if enabled: a base address for the whole block of system events is defined at the SDI node
if disabled: individual addresses per SEV can be defined
In order to avoid collisions, the addresses of the system events may not be used for other process objects.
In use enabled SDI - line
Value range: enabled/ disabled
if disabled: no SEVs will be transmitted on this line

The following table shows the system events available for the host interface. System events send
spontaneous as SPI with or without timestamp and contained in a general interrogation (without
timestamp):

Description of system event Address offset

At least one indication faulty SEV#016
At least one analog value faulty SEV#017
At least one digital value faulty SEV#018
At least one integrated total faulty SEV#019
At least one object or regulation command faulty SEV#020
At least one analog output faulty SEV#021
At least one digital output faulty SEV#022
RTU is faulty SEV#023
Device/ RTU active SEV#024
RTU synchronized SEV#025
External clock inoperable SEV#026
Local printer offline SEV#027
At least one indication oscillating SEV#028
Battery voltage low (RTU560E only) SEV#029
AC power supply failure (RTU560E only) SEV#030
At least one memory card removed 1,2 SEV#031
At least one user account file is missing or corrupt SEV#032
Test mode active SEV#042
At least one data object simulated SEV#043
Table 110: Description of system events

80 1KGT 150 466 V024 1

Internal Functions System commands

Description of system event Address offset

At least one data communication equipment (DCE) faulty SEV#044
Device connected SEV#045
At least one PLC function not running SEV#046
At least one PLC function cycle time exceeded SEV#047
Device/ RTU inoperable SEV#048
Device/ RTU is out of service SEV#049
Power supply failure in RTU central sub-rack SEV#059
Command supervision circuit x disconnected or faulty, 1 ≤ x ≤ 32 SEV#064 ... #095
SNTP client 1 is synchronized SEV#096
SNTP client 2 is synchronized SEV#097
Local control authority active SEV#100
Host x Online, 1 ≤ x ≤ 16 SEV#101 ... #116
Host interface x: At least one change of information lost, 1 ≤ x ≤ 16 SEV#117 ... #132
Host interface x: At least one pulse counter lost, 1 ≤ x ≤ 16 SEV#133 ... #148
CMU x is inoperable, 1 ≤ x ≤ 16 SEV#149 … #164
Configuration date SEV#174
Device reachable on redundant line x, 1 ≤ x ≤ 4 SEV#180 … #183
Device active on redundant line x, 1 ≤ x ≤ 4 SEV#184 … #187
Device preferred on redundant line x, 1 ≤ x ≤ 4 #SEV188 … #191
Network element x is operable, 1 ≤ x ≤ 32 SEV#192 … #223
CMU x is active, 1 ≤ x ≤ 16 SEV#224 … #239
Process command collision with host x, 1 ≤ x ≤ 16 SEV#242 ... #257
Command collision with Integrated HMI SEV#258
Command collision with web server SEV#259
Command collision with PLC SEV#260
HMI Client x online,1 ≤ x ≤ 16 SEV#261 ... #276
PRP interface x: Network interface E1 link on, 1 ≤ x ≤ 8 SEV#277 ... #284
PRP interface x: Network interface E2 link on, 1 ≤ x ≤ 8 SEV#285 ... #292
Host interface x: SOE buffer filling status is not reached, 1 ≤ x ≤ 16 SEV#293 ... #308
CAM Client x online, 1 ≤ x ≤ 4 SEV#309 ... #312
RTC battery voltage low 1 SEV#313
Table 110: Description of system events

1 540CID01, 540CMD01 and 560CMR01/02

2 520CMD01
ADVICE
System event #174 "Database identity tag" is not sent spontaneous but send in a general
interrogation with timestamp

10.11 System commands

System Single Commands (SSC) are accepted by the host communication interface with protocol
IEC 60870-5-101. If the command is addressed to the RTU itself, the RTU performs the command.

1KGT 150 466 V024 1 81

System commands Internal Functions

If the command is addressed to the connected subdevice, the SSC command is sent to the
corresponding subinterface.

SSC supported Description of SSC Address offset

X Set device out of service #001
X Reset device process #002
X Connect/disconnect device #003
X Set redundant line 1 / 2 as preferred line #004, #005
Set redundant line 3 / 4 as preferred line #006, #007
X Force global process image update, i.e. force process #012
image update of all subdevices
X Request redundancy change over for the active CMU x, 1 #016 ... #031
≤ x ≤ 16
Table 111: Description of system single commands (SSC)

10.11.1 Reset device process

The SSC command performs a reset for the addressed device. If the command is addressed to the
RTU itself, the RTU performs a restart. If the command is addressed to the connected subdevice,
the SSC command is sent to the corresponding sub-device interface.

RTU internal value Status

off <Ignored>
on reset device process
Table 112: Conversion of values SSC#002

10.11.2 Force process image update

If the SSC command is addressed to the RTU itself, SSC commands "force process image update"
are delegated to all sub-device interfaces. If the SSC command is addressed to the connected sub-
device, the command is routed to the corresponding sub-device interface.

RTU internal value Status

off <Ignored>
on Force process image update
Table 113: Conversion of values SSC#012

10.11.3 Request redundancy change over

The SSC command performs a switchover to the CMU specified by the command. If the command
is addressed to the RTU itself, the RTU forces a CMU reset when the CMU is active and the
standby partner is ok. If the command is addressed to the connected subdevice, the SSC command
is sent to the corresponding subinterface.

RTU internal value Status

off <Ignored>
on Request redundancy change over
Table 114: Conversion of values SSC#016 ... #031

82 1KGT 150 466 V024 1

Interoperability List System or device

11 Interoperability List
The selected parameters are marked in the white boxes as follows:

Function or ASDU is not used

X Function or ASDU is used as standardized (default)
R Function or ASDU is used in reverse mode
B Function or ASDU is used in standard and reverse mode

11.1 System or device

(system-specific parameter)

System definition
Controlling station definition (master)
X Controlled station definition (slave)

11.2 Network configuration

(network-specific parameter)

X Point-to-point X Multipoint-party line

X Multiple point-to-point X Multipoint-star

11.3 Physical Layer

(network-specific parameter)

11.3.1 Transmission speed (control direction)

Unbalanced interchange
Circuit V.24/V.28
Standard
X 100bit/s
X 200bit/s
X 300bit/s
X 600bit/s
X 1 200bit/s

Unbalanced interchange
Circuit V.24/V.28
Recommended if >1 200 bit/s
X 2 400bit/s
X 4 800bit/s
X 9 600bit/s

Balanced interchange
Circuit X.24/X.27
X 2 400bit/s
X 4 800bit/s
X 9 600bit/s
X 19 200bit/s

1KGT 150 466 V024 1 83

Physical Layer Interoperability List

X 38 400bit/s
56 000bit/s
64 000bit/s

11.3.2 Transmission speed (monitor direction)

Unbalanced interchange
Circuit V.24/V.28
Standard
X 100bit/s
X 200bit/s
X 300bit/s
X 600bit/s
X 1 200bit/s

Unbalanced interchange
Circuit V.24/V.28
Recommended if >1 200 bit/s
X 2 400bit/s
X 4 800bit/s
X 9 600bit/s

Balanced interchange
Circuit X.24/X.27
X 2 400bit/s
X 4 800bit/s
X 9 600bit/s
X 19 200bit/s
X 38 400bit/s
56 000bit/s
64 000bit/s

11.4 Link Layer

(network-specific parameter)

Frame format FT 1.2, single character 1 and the fixed time out interval are used exclusively in this
companion standard.

Link transmission procedure

X Balanced transmission
X Unbalanced transmission

Frame length
255 Maximum length L (control direction)
255 Maximum length L (monitor direction)
≤255 Time during which repetitions are permitted (Trp) or number of repetitions

Address field of the link

X Not present (balanced transmission only)
X One octet
X Two octets
X Structured
X Unstructured

84 1KGT 150 466 V024 1

Interoperability List Application Layer

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

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

Type identification Cause of transmission

9, 11, 13, 21 <1>

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

Type identification Cause of transmission

10, 12, 14, 34, 35, 36 <1>
1, 2, 3, 4, 5, 6, 7, 8, 15, 16, 17, 30, 31, 32, 33, <3>
37, 38

11.5 Application Layer

11.5.1 Transmission Mode for Application Data

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

11.5.2 Common Address of ASDU

(system-specific parameter)

X One octet X Two octets

11.5.3 Information object address

(system-specific parameter)

X One octet X Structured

X Two octets X Unstructured
X Three octets

11.5.4 Cause of transmission

(system-specific parameter)

X One octet X Two octets

(with originator address = 0)

11.5.5 Selection of standard ASDUs

11.5.5.1 Process information in monitor direction

(station-specific parameter)

X <1> := Single-point information M_SP_NA_1

X <2> := Single-point information with time tag M_SP_TA_1
X <3> := Double-point information M_DP_NA_1
X <4> := Double-point information with time tag M_DP_TA_1

1KGT 150 466 V024 1 85

Application Layer Interoperability List

X <5> := Step position information M_ST_NA_1

X <6> := Step position information with time tag M_ST_TA_1
X <7> := Bitstring of 32 bit M_BO_NA_1
X <8> := Bitstring of 32 bit with time tag M_BO_TA_1
X <9> := Measured value, normalized value M_ME_NA_1
X <10> := Measured value, normalized value with time tag M_ME_TA_1
X <11> := Measured value, scaled value M_ME_NB_1
X <12> := Measured value, scaled value with time tag M_ME_TB_1
X <13> := Measured value, short floating point value M_ME_NC_1
X <14> := Measured value, short floating point value with time tag M_ME_TC_1
X <15> := Integrated totals M_IT_NA_1
X <16> := Integrated totals with time tag M_IT_TA_1
X <17> := Event of protection equipment with time tag M_EP_TA_1
<18> := Packed start events of protection equipment with time tag M_EP_TB_1
<19> := Packed output circuit information of protection equipment M_EP_TC_1
with time tag
<20> := Packed single-point information with status change detection M_PS_NA_1
<21> := Measured value, normalized value without quality descriptor M_ME_ND_1

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

X <31> := Double-point information with time tag CP56Time2a M_DP_TB_1
X <32> := Step position information with time tag CP56Time2a M_ST_TB_1
X <33> := Bitstring of 32 bit with time tag CP56Time2a M_BO_TB_1
X <34> := Measured value, normalized value with time tag M_ME_TD_1
CP56Time2a
X <35> := Measured value, scaled value with time tag CP56Time2a M_ME_TE_1
X <36> := Measured value, short floating point value with time tag M_ME_TF_1
CP56Time2a
X <37> := Integrated totals with time tag CP56Time2a M_IT_TB_1
X <38> := Event of protection equipment with time tag CP56Time2a M_EP_TD_1
<39> := Packed start events of protection equipment with time tag M_EP_TE_1
CP56Time2a
<40> := Packed output circuit information of protection equipment M_EP_TF_1
with time tag CP56Time2a

Either ASDUs of the set <2>, <4>, <6>, <8>, <10>, <12>, <14>, <16>, <17>, <18>, <19> or of the
set <30 –40> are used.

11.5.5.2 Process information in control direction

(station-specific parameter)

X <45> := Single command C_SC_NA_1

X <46> := Double command C_DC_NA_1
X <47> := Regulating step command C_RC_NA_1
X <48> := Set point command, normalized value C_SE_NA_1
X <49> := Set point command, scaled value C_SE_NB_1
X <50> := Set point command, short floating point value C_SE_NC_1
X <51> := Bitstring of 32 bit C_BO_NA_1

11.5.5.3 System information in monitor direction

(station-specific parameter)

X <70> := End of initialization M_EI_NA_1

86 1KGT 150 466 V024 1

Interoperability List Application Layer

11.5.5.4 System information in control direction

(station-specific parameter)

X <100> := Interrogation command C_IC_NA_1

X <101> := Counter interrogation command C_CI_NA_1
X <102> := Read command C_RD_NA_1
X <103> := Clock synchronization command C_CS_NA_1
X <104> := Test command C_TS_NA_1
X <105> := Reset process command C_RP_NA_1
X <106> := Delay acquisition command C_CD_NA_1
X <107> := Test command with time tag CP56Time2a C_TS_TA_1

11.5.5.5 Parameter in control direction

(station-specific parameter)

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

X1 <111> := Parameter of measured value, scaled value P_ME_NB_1
X1 <112> := Parameter of measured value, short floating point value P_ME_NC_1
<113> := Parameter activation P_AC_NA_1

1 Deviation from standard explained in chapter "Parameter Loading" more detailed

11.5.5.6 File transfer

(station-specific parameter)

X <120> := File ready F_FR_NA_1

X <121> := Section ready F_SR_NA_1
X <122> := Call directory, select file, call file, call section F_SC_NA_1
X <123> := Last section, last segment F_LS_NA_1
X <124> := Ack file, ack section F_AF_NA_1
X <125> := Segment F_SG_NA_1
X <126> := Directory {blank or X, only available in monitor (standard) F_DR_TA_1
direction}

11.5.5.7 Type identification and case of transmission assignments

(station-specific parameter)

Type identification Cause of transmission

1 2 3 4 5 6 7 8 9 10 11 12 13 20 37 44 45 46 47
to to
36 41
<1> M_SP_NA_1 X X X X
<2> M_SP_TA_1 X X (x) (x)
<3> M_DP_NA_1 X X X X
<4> M_DP_TA_1 X X (x) (x)
<5> M_ST_NA_1 X X X X
<6> M_ST_TA_1 X X (x) (x)
<7> M_BO_NA_1 X X X X
<8> M_BO_TA_1 X X

1KGT 150 466 V024 1 87

Application Layer Interoperability List

Type identification Cause of transmission

1 2 3 4 5 6 7 8 9 10 11 12 13 20 37 44 45 46 47
to to
36 41
<9> M_ME_NA_1 X X X X X
<10> M_ME_TA_1 X X X
<11> M_ME_NB_1 X X X X X
<12> M_ME_TB_1 X X X
<13> M_ME_NC_1 X X X X X
<14> M_ME_TC_1 X X X
<15> M_IT_NA_1 X X
<16> M_IT_TA_1 X X X
<17> M_EP_TA_1 X
<18> M_EP_TB_1
<19> M_EP_TC_1
<20> M_PS_NA_1
<21> M_ME_ND_1
<30> M_SP_TB_1 X X
<31> M_DP_TB_1 X X
<32> M_ST_TB_1 X X
<33> M_BO_TB_1 X X
<34> M_ME_TD_1 X X
<35> M_ME_TE_1 X X
<36> M_ME_TF_1 X X
<37> M_IT_TB_1 X X
<38> M_EP_TD_1 X
<39> M_EP_TE_1
<40> M_EP_TF_1
<45> C_SC_NA_1 X X X X X X X X
<46> C_DC_NA_1 X X X X X X X X
<47> C_RC_NA_1 X X X X X X X X
<48> C_SE_NA_1 X X X X X X X X
<49> C_SE_NB_1 X X X X X X X X
<50> C_SE_NC_1 X X X X X X X X
<51> C_BO_NA_1 X X X X X X
<70> M_EI_NA_1 X
<100> C_IC_NA_1 X X X X X X
<101> C_CI_NA_1 X X X X X X
<102> C_RD_NA_1 X X X X
<103> C_CS_NA_1 X X X X X X
<104> C_TS_NA_1 X X X X X
<105> C_RP_NA_1 X X X X X
<106> C_CD_NA_1 X X X X X X
<110> P_ME_NA_1 X X X X X
<111> P_ME_NB_1 X X X X X

88 1KGT 150 466 V024 1

Interoperability List Basic application functions

Type identification Cause of transmission

1 2 3 4 5 6 7 8 9 10 11 12 13 20 37 44 45 46 47
to to
36 41
<112> P_ME_NC_1 X X X X X
<113> P_AC_NA_1 X
<120> F_FR_NA_1 X X X X
<121> F_SR_NA_1 X X X X
<122> F_SC_NA_1 X X X X X
<123> F_LS_NA_1 X X X X
<124> F_AF_NA_1 X X X X
<125> F_SG_NA_1 X X X X
<126> F_DR_TA_1 1 X

1 Blank or X only.

(x) Functionality 'Local' or 'Remote' can be assigned by PLC.

11.6 Basic application functions

11.6.1 Station initialization

(station-specific parameter)

X Remote initialization

11.6.2 Cyclic data transmission

(station-specific parameter)

X Cyclic data transmission

11.6.3 Read procedure

(station-specific parameter)

X Read procedure

11.6.4 Spontaneous transmission

(station-specific parameter)

X Spontaneous transmission

11.6.5 Double transmission of information objects with cause of

transmission spontaneous

(station-specific parameter)

1KGT 150 466 V024 1 89

Basic application functions Interoperability List

The following type identifications will 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.

X Single-point information M_SP_NA_1, M_SP_TA_1, M_SP_TB_1 and M_PS_NA_1

X Double-point information M_DP_NA_1, M_DP_TA_1 and M_DP_TB_1
X Step position information M_ST_NA_1, M_ST_TA_1 and M_ST_TB_1
X Bitstring of 32 bit M_BO_NA_1, M_BO_TA_1 and M_BO_TB_1
X Measured value, normalized value M_ME_NA_1, M_ME_TA_1, M_ME_ND_1 and
M_ME_TD_1
X Measured value, scaled value M_ME_NB_1, M_ME_TB_1 and M_ME_TE_1
X Measured value, short floating point number M_ME_NC_1, M_ME_TC_1 and M_ME_TF_1

11.6.6 Station interrogation

(station-specific parameter)

X global
X group 1 X group 7 X group 13
X group 2 X group 8 X group 14
X group 3 X group 9 X group 15
X group 4 X group 10 X group 16
X group 5 X group 11
X group 6 X group 12

Information object addresses assigned to each group must be shown in a separate table.

11.6.7 Clock synchronization

(station-specific parameter)

X Clock synchronization
Day of week used
RES1, GEN (time tag substituted/ not substituted) used
X SU-bit (summertime) used

11.6.8 Command transmission

(object-specific parameter)

X Direct command transmission

X Direct set point command transmission
X Select and execute command
X Select and execute set point command
X C_SE ACTTERM used (configurable)
X No additional definition
X Short-pulse duration (duration determined by a system parameter in the controlled station)
X Long-pulse duration (duration determined by a system parameter in the controlled station)
X Persistent output

All qualifiers are supported for commands

11.6.9 Transmission of integrated totals

(station- or object-specific parameter)

90 1KGT 150 466 V024 1

Interoperability List Basic application functions

X Mode A: local freeze with spontaneous transmission

X Mode B: local freeze with counter interrogation
X Mode C: freeze and transmit by counter interrogation commands
X Mode D: freeze by counter-interrogation command, frozen values reported spontaneously
X Counter read
X Counter freeze without reset
X Counter freeze with reset
Counter reset
X General request counter
X Request counter group 1
X Request counter group 2
X Request counter group 3
X Request counter group 4

11.6.10 Parameter loading

(object-specific parameter)

X Threshold value
X Smoothing factor
Low limit for transmission of measured value
High limit for transmission of measured values value

11.6.11 Parameter activation

(object-specific parameter)

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

11.6.12 Test procedure

(station-specific parameter)

X Test procedure

11.6.13 File transfer

(station-specific parameter)

File transfer in monitor direction

X Transparent file
X Transmission of disturbance data of protection equipment
X Transmission of sequences of events
X Transmission of sequences of recorded analogue values

File transfer in control direction

X Transparent file

11.6.14 Background scan

(station-specific parameter)

X Background scan

1KGT 150 466 V024 1 91

Basic application functions Interoperability List

11.6.15 Acquisition of transmission delay

(station-specific parameter)

X Acquisition of transmission delay

92 1KGT 150 466 V024 1

Glossary

12 Glossary
AC Alternating Current

AMI Analog Measured value Input

ASDU Application Service Data Unit

ASO Analog Setpoint command Output

BSI Bit String Input

BSO Bit String Output

CA Certificate Authority

CAM Central User Account Management

CMU Communication and Data Processing Unit

DCD Data Carrier Detect

DCO Double Command Output

DMI Digital Measured value Input (8, 16 bit)

DPI Double Point Input

DSO Digital Setpoint command Output (8, 16 bit)

EPI Event of Protection equipment Input (1 bit)

FC Functional Constraint

FDR File transfer directory

FSO Floating Setpoint Command Output

FTR File transfer file

GSM Global Standard for Mobile Communications

HCI Host Communication Interface

HMI Human Maschine Interface (here Integrated HMI function of the

RTU500 series)

HTTPS Hypertext Transfer Protocol Secure

IEC International Electrotechnical Commission

IED Intelligent Electronic Device

IOA Information Object Address

ITI Integrated Totals Input

Max Maximum

MFI Analog Measured value Floating Input

ms Millisecond

NCC Network Control Center

1KGT 150 466 V024 1 93

 Glossary

PDP Process Data Processing

PIN Personal Identity Number

PLC Programmable Logic Control

PRP Parallel Redundancy Protocol

RCD RTU Configuration Data

RCO Regulation step Command Output

RTC Real Time Clock

RTU Remote Terminal Unit

SCI Sub-Device Communication Interface

SCO Single Command Output

SEV System Event

SNTP Simple Network Time Protocol (according to RFC 4330)

SOE Sequence-of-Event Queue

SPI Single Point Input or Single point information

SSC System Single Command

STI Step position Input

94 1KGT 150 466 V024 1

1KGT 150 466 V024 1 95
 Note:

The specifications, data, design or other information contained in this document (the “Brochure”)
- together: the “Information” - shall only be for information purposes and shall in no respect be
binding. The Brochure does not claim to be exhaustive. Technical data in the Information are only
approximate figures. We reserve the right at any time to make technical changes or modify the
contents of this document without prior notice. The user shall be solely responsible for the use of
any application example or information described within this document. The described examples
and solutions are examples only and do not represent any comprehensive or complete solution.
The user shall determine at its sole discretion, or as the case may be, customize, program or add
value to the ABB Power Grids Germany AG products including software by creating solutions for
the end customer and to assess whether and to what extent the products are suitable and need to
be adjusted or customized.

This product is designed to be connected to and to communicate information and data via a network
interface. It is the users sole responsibility to provide and continuously ensure a secure connection
between the product and users or end customers network or any other network (as the case may
be). The user shall establish and maintain any appropriate measures (such as but not limited to the
installation of firewalls, application of authentication measures, encryption of data, installation of
anti-virus programs, etc) to protect the product, the network, its system and the interface against
any kind of security breaches, unauthorized access, interference, intrusion, leakage and/or theft
of data or information. ABB Power Grids Germany AG is not liable for any damages and/or losses
related to such security breaches, any unauthorized access, interference, intrusion, leakage and/or
theft of data or information.

ABB Power Grids Germany AG shall be under no warranty whatsoever whether express or implied
and assumes no responsibility for the information contained in this document or for any errors that
may appear in this document. ABB Power Grids Germany AG's liability under or in connection with
this Brochure or the files included within the Brochure, irrespective of the legal ground towards any
person or entity, to which the Brochure has been made available, in view of any damages including
costs or losses shall be excluded. In particular ABB Power Grids Germany AG shall in no event
be liable for any indirect, consequential or special damages, such as – but not limited to – loss of
profit, loss of production, loss of revenue, loss of data, loss of use, loss of earnings, cost of capital
or cost connected with an interruption of business or operation, third party claims. The exclusion
of liability shall not apply in the case of intention or gross negligence. The present declaration shall
be governed by and construed in accordance with the laws of Switzerland under exclusion of its
conflict of laws rules and of the Vienna Convention on the International Sale of Goods (CISG).

ABB Power Grids Germany AG reserves all rights in particular copyrights and other intellectual
property rights. Any reproduction, disclosure to third parties or utilization of its contents - in whole or
in part - is not permitted without the prior written consent of ABB Power Grids Germany AG.

ABB is a registered trademark of ABB Asea Brown Boveri Ltd.

Manufactured by/for a Hitachi Power Grids company.

© 2021 Hitachi Power Grids.

All rights reserved.

96 1KGT 150 466 V024 1

1KGT 150 466 V024 1 97
Visit us

ABB Power Grids Germany AG

P.O. Box 10 01 64
68128 Mannheim, Germany

hitachiabb-powergrids.com/rtu

1KGT 150 466 V024 1