E560 FD Release 9 0 PDF

RTU560
Remote Terminal Unit
Function Description Release 9.0
This manual describes the functions provided by the

Remote Terminal Unit RTU560 Release 9.0.
Revision
Document identity: 1KGT 150 589 V000 1
Revision: 0 Date: 01/2008
We reserve all rights in this document and in the information contained therein.
Reproduction, use or disclosure to third parties without express authority is strictly
forbidden.
© Copyright 2008 ABB AG
ABB AG 1KGT 150 589 V000 1 1-1

Contents
FUNCTION DESCRIPTION RELEASE 9.0 .............................................. 1-1
1 ABOUT THE RTU560 FUNCTION DESCRIPTION ............................ 1-1
1 THE RTU560 FAMILY ........................................................................ 1-1

1.1 Overview ...........................................................................................................1-1
1.2 Hardware...........................................................................................................1-3
1.2.1 Hardware Structure............................................................................1-5
1.3 Software ..........................................................................................................1-11
1.3.1 RTU560 Software Structure.............................................................1-12
1.3.2 I/O Bus Master and RTU560 I/O Bus ..............................................1-14
1.3.3 Event Flow through RTU560 ...........................................................1-15
1.4 Tools................................................................................................................1-17
1.4.1 RTUtil560 .........................................................................................1-17
1.4.2 RTU560 Web Server .......................................................................1-19
1.4.3 MULTIPROG wt ...............................................................................1-21
2 SCADA MONITORING DIRECTION .................................................. 2-1

2.1 Indication Processing ........................................................................................2-1
2.1.1 Function Distribution ..........................................................................2-2
2.1.2 23BE23/23BE40 Functions................................................................2-2
2.1.3 PDP Functions of the CMU................................................................2-5
2.1.4 Group Information ..............................................................................2-7
2.1.5 Error Handling....................................................................................2-9
2.1.6 Indication Processing with 560MIO80 ...............................................2-9
2.2 Analog Measured Information Processing ......................................................2-10
2.2.1 Analog Measured Information (AMI) Types.....................................2-10
2.2.2 Function Distribution ........................................................................2-10
2.2.3 23AE23 Functions............................................................................2-11
2.2.4 PDP Functions of the CMU..............................................................2-16
2.2.5 Error Handling..................................................................................2-19
2.2.6 Analog Measured Value Processing with 560MIO80 ......................2-20
2.3 Digital Measured Value Processing ................................................................2-20
2.3.1 23BE23/23BE40 Functions..............................................................2-22
2.3.2 PDP Functions of the CMU..............................................................2-23
2.3.3 Error Handling..................................................................................2-24
2.3.4 Digital Measured Value Processing with 560MIO80 .......................2-24
ABB AG 1KGT 150 589 V000 1 1-1

Abbreviations Remote Terminal Unit RTU560
2.4 Bit-string Input Value Processing ................................................................... 2-25

2.4.1 Function Distribution ....................................................................... 2-25
2.4.2 23BE23/23BE40 Functions ............................................................. 2-26
2.4.3 Error Handling ................................................................................. 2-27
2.4.4 Bit-string Input Processing with 560MIO80..................................... 2-27
2.5 Integrated Total Processing ........................................................................... 2-28
2.5.1 Integrated Total Value Types .......................................................... 2-28
2.5.2 Function Distribution ....................................................................... 2-29
2.5.3 23BE23/23BE40 Functions ............................................................. 2-29
2.5.4 PDP Functions of the CMU ............................................................. 2-30
2.5.5 Error Handling ................................................................................. 2-33
2.5.6 Integrated Total Processing with 560MIO80................................... 2-33
2.6 Direct Interfacing of Current and Voltage Transformer .................................. 2-34
3 SCADA COMMAND DIRECTION ...................................................... 3-1

3.1 Output Command Types .................................................................................. 3-1
3.2 Function Distribution......................................................................................... 3-1
3.3 Object Command Output.................................................................................. 3-2
3.3.1 Object Command Output with 23BA20/23BA40 ............................... 3-2
3.3.2 Single Object Command Output ....................................................... 3-2
3.3.3 Double Object Command Output...................................................... 3-3
3.3.4 Output Procedures ............................................................................ 3-4
3.3.5 Object Command Output with 560MIO80 ....................................... 3-13
3.4 Regulation Step Command Output ................................................................ 3-14
3.5 Setpoint Command Output ............................................................................. 3-15
3.5.1 Analog Setpoint Command Output ................................................. 3-15
3.5.2 Digital Setpoint Command Output .................................................. 3-18
3.6 Bit-string Output.............................................................................................. 3-21
3.6.1 Bit-string Output with 23BA20/23BA40 ........................................... 3-21
3.6.2 Bit-string Output with 560MIO80..................................................... 3-21
3.7 Error Handling ................................................................................................ 3-22
4 REDUNDANCY .................................................................................. 4-1

4.1 Overview........................................................................................................... 4-1
4.2 RTU560A/C redundant CMU concept.............................................................. 4-1
4.3 Redundancy switchover ................................................................................... 4-4
4.4 Influence on RTU Functions............................................................................. 4-5
4.4.1 PDP and Counter Values .................................................................. 4-5
4.4.2 PLC Function .................................................................................... 4-5
4.4.3 Group Functions................................................................................ 4-5
4.4.4 Archive and Local Print, Integrated HMI ........................................... 4-6
4.4.5 Time Administration .......................................................................... 4-6
4.5 RTUtil560 Configuration ................................................................................... 4-6
4.6 Redundant Communication.............................................................................. 4-8
4.6.1 Redundant Host Communication Interfaces ..................................... 4-8
4.6.2 Redundant Subdevice Communication Interface ............................. 4-8
1-2 1KGT 150 589 V000 1 ABB AG

Remote Terminal Unit RTU560 Contents
5 HOST COMMUNICATION INTERFACE ............................................ 5-1

5.1 Overview HCI Software Structure .....................................................................5-3
5.2 Queue- and Buffer Handling .............................................................................5-4
5.2.1 Priority – Read Queues .....................................................................5-5
5.2.2 Queue Transitions and Overflow .......................................................5-6
6 SUB-DEVICE COMMUNICATION INTERFACE ................................ 6-1

6.1 Message Flow in Monitoring Direction ..............................................................6-3
6.2 Message Flow in Command Direction ..............................................................6-3
6.3 General Interrogation ........................................................................................6-4
6.4 Time Synchronization........................................................................................6-4
6.5 System Events ..................................................................................................6-5
7 IEC61850 STATION COMPUTER ...................................................... 7-1

7.1 RTU560 in an IEC61850 System ......................................................................7-1
7.2 Engineering process .........................................................................................7-2
8 INTERFACES AND NETWORK ......................................................... 8-1

8.1 Network Configuration.......................................................................................8-1
8.2 Interface Configuration......................................................................................8-2
8.2.1 The Interfaces ....................................................................................8-2
8.3 Duplex Communication .....................................................................................8-3
8.3.1 WT Link Full Duplex (no handshake) ................................................8-3
8.3.2 Direct Link (TxD / RxD only) ..............................................................8-4
8.3.3 Dial up. (external modem, DCD handshake).....................................8-4
8.4 Half Duplex Communication..............................................................................8-6
8.4.1 WT Link Half Duplex (RTS/CTS handshake) ....................................8-6
8.4.2 WT Link Half Duplex (RTS/DCD handshake)....................................8-7
8.5 Additional Communication Modes ....................................................................8-8
8.5.1 Loop Switch unit DSTC 3002.............................................................8-8
8.5.2 Link with collision avoidance (DCD handshake) ...............................8-8
8.6 Network Configuration Rules and Restrictions .................................................8-9
8.6.1 Interface Configuration Rules and Restrictions .................................8-9
9 PROGRAMMABLE LOGIC CONTROL (PLC) ................................... 9-1

9.1 PLC – SCADA Processing ................................................................................9-1
9.1.1 PLC Application and Tasks................................................................9-2
9.2 I/O Interface.......................................................................................................9-3
9.2.1 General I/O Handling .........................................................................9-3
9.3 Signal Processing .............................................................................................9-5
9.3.1 Messages and Commands ................................................................9-5
9.3.2 System Event Processing..................................................................9-6
9.3.3 System Event Messages ...................................................................9-6
9.4 Characteristic Technical Data ...........................................................................9-7
ABB AG 1KGT 150 589 V000 1 1-3

10 LOCAL PRINT AND PROCESS ARCHIVE FUNCTION.................. 10-1

10.1 Overview......................................................................................................... 10-1
10.2 Message Processing and Buffering................................................................ 10-2
10.2.1 Supported Data Types .................................................................... 10-4
10.2.2 Queue Handling .............................................................................. 10-4
10.3 Message String Generation............................................................................ 10-5
10.4 Data Archives ................................................................................................. 10-6
10.4.1 Archive Records.............................................................................. 10-6
10.4.2 Archive Files.................................................................................... 10-7
10.4.3 Archive Function Global Settings.................................................... 10-7
10.4.4 Access to Archive Data ................................................................... 10-8
10.4.5 Archive Data Import to MS Excel .................................................... 10-8
10.5 Local Print Output......................................................................................... 10-12
10.5.1 Serial Printer Interface .................................................................. 10-12
10.5.2 Local Print Global Settings............................................................ 10-13
10.5.3 Page Layout and Page Control..................................................... 10-13
10.5.4 New Day........................................................................................ 10-14
10.5.5 Printout after RTU Restart............................................................. 10-14
10.6 Data Point Configuration .............................................................................. 10-15
10.6.1 Process Data Points...................................................................... 10-16
10.6.2 Configuration of System Events.................................................... 10-16
11 DISTURBANCE DATA FILE ARCHIVE........................................... 11-1

11.1 Introduction ..................................................................................................... 11-1
11.2 The Archive Function...................................................................................... 11-2
11.3 Protection equipment supported by RTU560 ................................................. 11-3
11.4 Configuration of a disturbance data file archive ............................................. 11-3
11.5 Access to the disturbance data file archive.................................................... 11-4
11.6 Conversion properties .................................................................................... 11-5
11.6.1 Application....................................................................................... 11-5
11.6.2 Settings ........................................................................................... 11-6
11.6.3 Example .......................................................................................... 11-8
12 TRANSMISSION AND STORAGE OF METER DATA .................... 12-1

12.1 Overview......................................................................................................... 12-1
12.2 Transmission of Meter Data ........................................................................... 12-2
12.3 Transmission Procedure ................................................................................ 12-2
12.4 Conversion Properties .................................................................................... 12-3
1-4 1KGT 150 589 V000 1 ABB AG

Remote Terminal Unit RTU560 Contents
13 INTEGRATED HMI ........................................................................... 13-1

13.1 Overview .........................................................................................................13-2
13.2 Structure of the Integrated HMI.......................................................................13-3
13.3 The HMI-Editor ................................................................................................13-4
13.3.1 The Project.......................................................................................13-4
13.3.2 The Page .........................................................................................13-4
13.3.3 The Background...............................................................................13-4
13.3.4 Operation of the Editor.....................................................................13-5
13.3.5 The Components of the Integrated HMI Editor................................13-7
13.4 The Process Archives .....................................................................................13-8
13.5 The Alarm List .................................................................................................13-8
13.6 The Control Authority ......................................................................................13-9
13.7 The Component View Editor ...........................................................................13-9
14 STARTUP, CONFIGURATION, TIME MANAGEMENT ................... 14-1

14.1 Startup Procedures .........................................................................................14-1
14.1.1 RTU560 CMU Start..........................................................................14-1
14.1.2 RTU560 System Start ......................................................................14-3
14.1.3 CMU Integration...............................................................................14-3
14.1.4 CMU Removal..................................................................................14-4
14.2 RTU560 Configuration ....................................................................................14-5
14.2.1 General Requirements.....................................................................14-5
14.2.2 Configuration File Load Procedure..................................................14-5
14.3 RTU560 Time Management............................................................................14-6
14.3.1 Time Management Principle ............................................................14-6
14.3.2 RTU560 Time Slave.........................................................................14-8
14.3.3 Time Zone and Daylight Saving.......................................................14-8
14.4 Time Synchronization Modes..........................................................................14-9
14.4.1 Synchronization by CS Command from NCC..................................14-9
14.4.2 Synchronization by CS Command & External Minute Pulse .........14-10
14.4.3 Synchronization by sntp.................................................................14-10
14.4.4 Synchronization by Radio Clock ....................................................14-15
14.4.5 Redundant Time Synchronization .................................................14-16
14.5 Synchronization of Sub-RTUs.......................................................................14-17
14.5.1 Synchronization with CS Command ..............................................14-17
14.5.2 Synchronization with sntp Server ..................................................14-17
ABB AG 1KGT 150 589 V000 1 1-5

15 STATUS AND DIAGNOSTIC INFORMATION................................. 15-1

15.1 Status and Error Report to NCC..................................................................... 15-1
15.2 Web-Server Diagnosis ................................................................................... 15-1
15.2.1 System Diagnosis ........................................................................... 15-1
15.2.2 Status Information ........................................................................... 15-2
15.3 RTU Alarm and Warning ................................................................................ 15-3
15.4 Board States and LED Signaling.................................................................... 15-3
15.4.1 Communication and Data Processing Units ................................... 15-4
15.4.2 I/O Boards, Modems and Real Time Clocks................................. 15-10
15.4.3 LED indications 23OK24 ............................................................... 15-16
15.4.4 LED indications of decentralized modules.................................... 15-16
16 SYSTEM DATA INTERFACE .......................................................... 16-1

16.1 System Events................................................................................................ 16-1
16.2 System Commands ........................................................................................ 16-3
1-6 1KGT 150 589 V000 1 ABB AG

Abbreviations
AMI Analog Measured value Input
ASO Analog Setpoint command Output
BCU Bus Connection Unit
BSI Bit String Input (8, 16 bit)
CMU Communication and Data Processing Unit
CS Control System
CSC Command Supervision Channel
CS-Command Clock Synch Command
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 (1bit)
GCD General Configuration Data
HCI Host Communication Interface
IED Intelligent Electronic Device
IOC I/O Controller (Controller on I/O Board)
IOD Input Output Data
IOM I/O Bus Master (Function of SLC)
ITI Integrated Totals Input
MFI Analog Measured value Floating Input
MPU Main Processing Unit
NCC Network Control Center
PB Peripheral Bus
ABB AG 1KGT 150 589 V000 1 1-1

PBP Peripheral Bus Processor
PDP Process Data Processing
PLC Programmable Logic Control
PPP Point to Point Protocol
PSU Power Supply Unit
RCO Regulation step Command Output
RTC Real Time Clock
SBO Select before Operate
SCADA Supervision, Control and Data Acquisition
SCI Sub-Device Communication Interface
SCO Single Command Output
SEV System Events
SLC Serial Line Controller
SOC Strobe Output Channel
SPI Single Point Input
SSC System Single Command
STI Step position Input (8 bit)
TSI Time Synchronization Input
TSO Time Synchronization Output
1-2 1KGT 150 589 V000 1 ABB AG

1 About the RTU560 Function Description
Application Hints for the Use of RTU560
Read the following chapters before mounting and commissioning a RTU560 Remote
Terminal Unit.
Regulations for the installation and operation of

electrical systems
The ABB RTU560 devices are produced in compliance with the relevant regulations and
appointments.
Die RTU560 is classified according to IEC 60664-1 (DIN VDE 0110): Insulation
coordination for equipment within low-voltage systems Part 1: Principles, requirements
and tests.
• Pollution degree 2
Only non-conductive pollution occurs except that occasionally a temporary
conductivity caused by condensation is to be expected
• Over-voltage category II
is in accordance with the appointment in IEC 61131 part 2
The user has to ensure that the devices and the components belonging to them are
mounted in compliance with the current safety regulations and.
• DIN VDE 0100 Erection of power installations with nominal voltages up to

1000 V
• DIN VDE 0106 Protection against electrical shock
Part 100: Actuating members positioned close to parts
liable to shock
• EN 60204 Safety of machinery; Electrical equipment of machines
Part 1: General requirements
• EN 60950 Electronic equipment for use in electrical power
installations and their assembly into electrical power
installations
• DIN VDE 0800 Telecommunications
If the pollution degree 2 (VDE 0110) cannot be guaranteed or further protection against
direct contact is required the devices should be mounted into appropriate cubicles.
If ABB RTU560 devices are coupled with or fed by power-frequency voltage networks of
over-voltage category III qualified protective provisions have to be taken to guarantee
over-voltage category II according to VDE 0110 at the terminal connectors (e.g. surge
voltage protectors).
ABB AG 1KGT 150 589 V000 1 1-1

About the RTU560 Function Description Remote Terminal Unit RTU560
Installation and application hints
Documentation
This document contains all essential functions of the RTU560 boards for the use in the
RTU560. For more details and additional information the documents described in chapter
"Related documents" have to be used.
Qualified personnel
The RTU560 modules partly conduct dangerous contact voltages at their connectors.
Touching parts which are alive may cause serious injuries.
Therefore installation, commissioning and maintenance of such systems shall be carried

out only by technically instructed personnel. The personnel should have an adequate
knowledge of
• dealing with dangerous voltages

• using the specifications and standards. In particular EN (VDE-) and accident
prevention regulations.
Use according to the rules
The RTU560 was developed, manufactured, tested and documented while observing the
relevant standards. When the valid regulations for installation, commissioning and
maintenance are observed, the product poses no danger to health and objects in normal
case.
Use according to the rules means that the RTU560 is operating and maintained
exclusively in the form as described in the functional- and module description documents.
Especially the technical data for the process-circuits and the supply should be regarded.
Any liability for the consequences of incorrect use or after unauthorized repairs is
rejected.
1-2 1KGT 150 589 V000 1 ABB AG

Remote Terminal Unit RTU560 About the RTU560 Function Description
WARNINGS, CAUTIONS
Grounding the devices
• Before connecting any power to the device, the 6.3 mm Faston connector should
be wired to protection earth. The grounding may be removed only if it is certain that
no more power is being supplied to the device.
• Regard the grounding principles for the serial peripheral bus (direct or capacitive
grounding)
Connection of the supply voltage
• A terminal block feeding dangerous contact voltages (supply voltage, input-/output

channels) should only be plugged or withdrawn in off load state.
Protect the device from dampness, dirt and damage during transport,
storage and operation.
Do not operate device outside of the specified technical data
Operate device according to the protection degree IP 20
• Mount it into a closed cubicle or rack if the environmental conditions require that.
Do not obstruct the ventilation for cooling
• Do not cover the ventilation slots by cables or wires.

Lead signal and power lines separately
• Capacitive and inductive interference's of the power lines to signal lines should be
prevented by appropriate cable laying (distance, crossing).
Use over-voltage protection in cables to outdoor antenna
Graphic Aids in the Function Description
The following symbols are used throughout the description:

Symbol Description
An information hint which should be regarded or which helps to find an essential
point in the chapter etc.
A caution hint which is important to know if you configure the RTU560.
Which informs about a restriction etc.
A configuration hint which shows where a parameter or any other
configurable point is described.
ABB AG 1KGT 150 589 V000 1 1-3

About the RTU560 Function Description Remote Terminal Unit RTU560
Related documents
The RTU560 Function Description is part of the total documentation of the RTU560
remote terminal unit. More details and additional information can be found in the following
documents:
[1] 1 KGT 150 451 RTUtil560 Users guide Handling of all RTU560 PC-
based utilities
[2] 1KGT 150 583 Web Server Users guide Handling the RTU560
Web Server, Installation and
Configuration
[3] individual Ident RTU560 Individual Hardware Data

Hardware Data Sheets Sheets of all RTU560 boards,
units and auxiliary equipment
[4] individual Ident RTU560 Individual Connection and

Connection and Settings Settings description of all
documents RTU560 boards, units and
auxiliary equipment
[5] individual Ident RTU560 Individual description of each

Host and Sub-Device protocol implementation in
Communication Interfaces RTU560
[6] 1 KGT 150 470 MULTIPROG wt Manual Manual for RTU560's PLC
programming and test system
[7] 1 KGT 150 526 PLC Libraries Description of RTU560

specific PLC functions and
function blocks
[8] 1 KGT 150 654 Integrated HMI Engineering Engineering and configuration
Guide for the integrated HMI
interface
1-4 1KGT 150 589 V000 1 ABB AG

1 The RTU560 Family
1.1 Overview
Based on a modular multi-CPU concept, RTU560 is designed for extremely high

communication and data processing capability. Maintaining the proven I/O board family of
RTU200 and RTU232, it fulfills the requirements for high end remote terminal units:
• Modular hardware and software configuration

• Compact construction
• Low number of board types
• Up to 16 communication interfaces to NCCs
• Up to 32 communication interfaces to sub-devices
• Up to 5000 data points per RTU560
• Support of various communication protocols
• Scaleable performance
• State-of-the-art configuration tool RTUtil560 with external data interface
• Web Server based access to configuration data and application program files
• Web Server based process and system diagnosis
• Integrated Human Machine Interface (HMI) (option)
• Programmable logic control function according to IEC 61131-3 (option)
RTU560’s communication capabilities are shown in principle in Figure 1-1.
ABB AG 1KGT 150 589 V000 1 1-1

The RTU560 Family Remote Terminal Unit RTU560
Station Control Telecontrol Center(s)
IEC 60870-5-104
WAN
IEC 60870-5-104
IEC 60870-5-101 IEC 60870-5-101
DNP 3.0 DNP 3.0 IEC 60870-5-104
RTU 560
IEC 60870-5-103
IEC 60870-5-101 IEC 60870-5-101
DNP 3.0 DNP 3.0
SPABus
Modbus IED
Sub-RTU Process IED IED

Marshalling Rack Protection and
Control Units
IED
Protection and
Control Units
Figure 1-1: RTU560 communication capabilities in principle
1-2 1KGT 150 589 V000 1 ABB AG

Remote Terminal Unit RTU560 The RTU560 Family
1.2 Hardware
Each hardware board is described in detail in the hardware data sheet. Board settings
and wiring principles are explained in the unit and application descriptions. The following
tables list the boards, which are available for the RTU560 A, C and D:
Type Ident Function

560SLI02 4 Serial Line Interfaces
560ETH03 2 Serial Line Interfaces, 1 Ethernet Interface
R0001
Communication and 560CMU02 3 Serial Line Interfaces, 1 Ethernet Interface (RTU560D)
Processing Units 560CMU04 4 Serial Line Interfaces, 1 Ethernet Interface
R0001: for UART-based communication protocols
R0002: for non-UART-based communication protocols
560CMU05 4 Serial Line Interfaces, 2 Ethernet Interfaces
560BCU01 Connection Unit to extend the RTU560 system bus to a
second communication subrack 560CSR01 (RTU560A)
560BCU02 Connection Unit to provide the RTU560 system bus to a
Bus Connection pair of two CMUs within an I/O subrack 23TP22
Units (RTU560C)
560BCU03 Connection Unit to provide the RTU560 system bus to a
R0002 pair of two CMUs within an I/O subrack 23ET24
(RTU560C)
23AA20 Analog Output 2 channels / board
23AE23 Analog Input 8 channels / board
I/O Boards
23BA20 Binary Output 16 output relays / board
with IOC
23BE23 Binary Input 16 channels / board
23BA22 Command supervision 2 independent channels
Decentralized 560CVT01 I/O module for 3-phase 3*U, 3*I, calculated values
Module, systems, 3/4-wire
Rail mounted connection
23BA40 Binary Output Interposing 16 output relays / board
220 V DC
I/O Boards with IOC
23BE40 Binary Input interposing 16 channels / board
Rail mounted
110 V DC (R0001)
220/250 V DC (R0002)
General boards / 23OK24 Fiber Optic Coupler, RTU560 I/O bus,
units 2 optical channels or RS485 / RS232 C
560FOC40 Fiber Optic Coupler RTU560 I/O bus,
for 23BA40/23BE30 or RS485
560RTC01 Real time clock GPS time receiver
560RTC02 Real time clock DCF77 time receiver
560RTC03 Real time clock IRIG-B/AFNOR receiver
23WT23 Leased line modem FSK CCITT V.23 modem
23WT24 Private line modem FSK modem, 9.6 kBit/s
23WT25 Leased line modem FSK selective modem
560MPR01 I/O Subrack, RTU560D Mounting plate version,
560CMU02 and 8 I/O slots
560CSR01 Communication Subrack, For up to 8 communication
RTU560A units, clock, bus connection
unit 560BCU01
Subracks 23TP22 I/O Subrack, RTU560C Mounting plate version,
19 slots, 560BCU02
23ET24 I/O Subrack, RTU560C Hinged frame version,
19 slots, 560BCU03
ABB AG 1KGT 150 589 V000 1 1-3

Type Ident Function

560PSU01 Power Supply Unit with Input ranges:
redundancy logic, 42 W 24 ... 60 V DC (R0001)
110 ... 220 V DC (R0002)
560PSU02 Power Supply Unit with Input range 48… 220 V DC
Power supply / redundancy logic, 80 W
mains adapter 560PSU40 Power Supply Unit for Input Range:
23BA40/23BE40, 85 … 264 V AC,
560CVT01 and 560MPR01 85 … 375 V DC
23VG23 AC / DC converter 24 V DC / 2 A output
battery charging function
23VG24 AC / DC converter 24 V DC / 10 A output
Table 1-1: RTU560 A, C and D boards
The following tables list the boards, which are available for the RTU560 E.
Typ Ident Funktion

Communication and 560CMU80 CMU with 3 serial line interfaces
Processing Unit (CMU) R0001
560CMU80 CMU with 3 serial line interfaces and 1 Ethernet-Interface
R0002
I/O Boards with IOC 560MIO80 16 Binary Inputs, 4 Analog Inputs, 8 Output Relays
R0001 24 ... 60 V DC
560MIO80 16 Binary Inputs, 4 Analog Inputs, 8 Output Relays
R0002 110 ... 220 V DC
General Boards / Units 560FOC80 Fiber Optic Coupler
560MOD80 V.23 Modem
560MOD81 Dial up Modem
560MOD82 GSM Modem
Housing 560HOS80 Basic Housing for CMU and 3 I/O Units
R0001
560HOS80 Extension for 4 I/O Units
R0002
Power Supply 560PSU80 R0001: Input 24 ... 60 V DC
R0002: Input 110 ... 220 V DC
560PSU81 Input: 220 V AC
Table 1-2: RTU560 E boards
1-4 1KGT 150 589 V000 1 ABB AG

1.2.1 Hardware Structure
RTU560 in principle is built up by one or two main subracks containing the

Communication and Processing Units (CMUs) with the serial or Ethernet communication
interfaces and I/O subracks with the I/O boards. There are three types of RTU
configurations:
• RTU560A with up to 16 CMUs placed in one or two communication subracks

560CSR01, I/O boards placed within up to 224 I/O subracks 23ET24 or 23TP22.
• RTU560C with one or two CMUs placed in one of the I/O subracks 23ET24 or
23TP22 together with up to 15 I/O boards within this main subrack; further I/O
boards placed within another up to 24 I/O subracks 23ET24 or 23TP22.
• RTU560D with one CMU 560CMU02 together with up to 8 I/O boards. Further 8
I/O boards can be placed into a second subrack 560MPR01.
• RTU560E with one CMU and three I/O boards in the basic housing, or four I/O
boards in the extension housing.
Network Control Centers
CMU CMU CMU CMU
RTU560 System Bus
CMU CMU CMU CMU
I/O Boards
IED Sub-RTU IED
I/O Boards
IED Sub-RTU IED

I/O Boards
I/O Boards
Figure 1-2: RTU560 Hardware structure in principle
ABB AG 1KGT 150 589 V000 1 1-5

The CMUs communicate over the RTU560 system bus which is provided on the back-
plane of the communication subrack 560CSR01 (RTU560A) or by means of bus
connection units 560BCU02 or 560BCU03 (RTU560C).
The I/O subracks are connected to the CMU’s via serial RS485 interfaces A or B. In total
up to32 I/O bus segments may be configured (RTU560A), If one of the serial interfaces of
a CMU’s interface pair A and B is used for I/O bus connection, the pair’s other interface
may only be used for another I/O bus segment (cannot be used for other types of
communication protocols)!
Bus connection units do not only provide the system bus connection between
communication subracks (RTU560A) resp. CMUs (RTU560C), but in addition the system
signals
• local alarm (relay contact)

• local warning (relay contact)
• TSI (Time Sync Input signal)
• TSO (Time Sync Output signal)
If one of these signals has to be provided externally, e.g. if the RTU has to be
synchronized by any type of time synchronization pulse signal (including those used with
560RTC01, 560RTC02 and 560RTC03 real time clocks), one of the appropriate BCU
boards has to be configured within the RTU, although if not required for system bus
interconnection between communication subracks (RTU560A) or CMUs (RTU560C).
1.2.1.1 Configuration Type RTU560A
RTU560A is the RTU560 configuration type providing - in addition to the local I/O
connections - multiple communication interfaces to NCCs and Sub-Devices like Sub-
RTUs, Protection Equipment, Bay Control Units and IEDs (e.g. intelligent Transducers).
This configuration type has also to be used when redundant power supplies for the main
subracks are required.
Up to 8 CMUs can be configured within one communication subrack 560CSR01. Adding

a second communication subrack provides another 8 CMU slots giving a maximum
number of 16 CMUs for one RTU560. In this configuration, within both communication
subracks, a system bus connection unit 560BCU01 has to be used which provides the
system bus interconnection between the two communication subracks.
Besides PSUs, CMUs and bus connection units, the two real time clock units 560RTC01
(GPS receiver), 560RTC02 (DCF77 receiver) and 560RTC03 (IRIG-B / AFNOR receiver)
are the only boards of RTU560’s board family that can be placed within the
communication subrack. All other boards have to be placed within I/O subracks.
1-6 1KGT 150 589 V000 1 ABB AG

Communication subrack 560CSR01
560PSU01 560PSU01 560ETH01 560ETH01 560ETH01 560SLI01 560SLI01 560SLI01 560SLI01 560RT 560BCU01
5V
Tx Rx CE Tx Rx CE Tx Rx CE Tx Rx CE Tx Rx CE Tx Rx CE Tx Rx CE C02
5V
A ERR A ERR A ERR A ERR A ERR A ERR A ERR
24 V 24 V
ERR ALR
B B B B B B B S1
A C A C A C 1 1 1 1 WRN
OFF
12 3 4
E E E 2 2 2 2 FR
MMI MMI MMI MMI MMI TSI
MMI MMI LS
UE + UE +
A A A A A A A MN TSO
UE - UE -
PE PE SEB
B B B B B B B
E E E
ON ON 1 1 1 1
OFF OFF
2 2 2 2
RTU I/O bus segment

I/O subrack 23TP21
23NG24
24 V
5V
UE +
UE -
PE
ON
0FF
Max. 6 I/O subracks

per I/O bus segment
I/O subrack 23TP21
23NG24
24 V
5V
UE +
UE -
PE
ON
0FF
Figure 1-3: RTU560A (configuration example)
ABB AG 1KGT 150 589 V000 1 1-7

1.2.1.2 Configuration Type RTU560C
RTU560C is the compact RTU560 configuration type, providing - in addition to the local
I/O connections - up to 8 serial communication interfaces to NCCs or Sub-Devices like
Sub-RTUs, Protection Equipment, Bay Control Units and IEDs (e.g. intelligent
transducers).
One or two CMUs can be configured within one of the RTU’s I/O subracks, thus building
the RTU’s main subrack. In this configuration, if two CMUs are to be configured, a system
bus connection unit 560BCU02 (23TP22) or 560BCU03 (23ET24) has to be used which
provides the system bus interconnection between the two CMUs.
Besides the two (double-) slots reserved for CMUs, within RTU560C’s main subrack 15
slots remain available for I/O boards, modems, RTCs or optical couplers from the
RTU560 board family.
The I/O bus is provided by one of the CMU’s serial interface CPB, internally connected to
the I/O bus on the backplane of the main subrack. Additional I/O subracks are added to
this first I/O bus segment using the standard I/O bus interfaces provided by the I/O
subracks. Interface CPA of the CMU which provides the I/O bus interface may be used
as additional I/O bus segment only.
23NG24 23BE21 23BE21 23BE21 23BE21 23BE21 23BE21 23BE21 23BE21 23BE21 23BE21 23BE21 23BE21 23BA21 23BA21 23BA21 560SLI01 560SLI01
Tx Rx CE Tx Rx CE
A A
5V ST ST ST ST ST ST ST ST ST ST ST ST ST ST ST B B
PST PST PST 1 1
OFF
1 2 3
24 V
2 2
1 9 1 9 1 9 1 9 1 9 1 9 1 9 1 9 1 9 1 9 1 9 1 9
4
2 10 2 10 2 10 2 10 2 10 2 10 2 10 2 10 2 10 2 10 2 10 2 10 MMI MMI
A A
3 11 3 11 3 11 3 11 3 11 3 11 3 11 3 11 3 11 3 11 3 11 3 11
UE + 4 12 4 12 4 12 4 12 4 12 4 12 4 12 4 12 4 12 4 12 4 12 4 12
UE - 5 13 5 13 5 13 5 13 5 13 5 13 5 13 5 13 5 13 5 13 5 13 5 13 B B
6 14 6 14 6 14 6 14 6 14 6 14 6 14 6 14 6 14 6 14 6 14 6 14
PE 7 15 7 15 7 15 7 15 7 15 7 15 7 15 7 15 7 15 7 15 7 15 7 15
8 16 8 16 8 16 8 16 8 16 8 16 8 16 8 16 8 16 8 16 8 16 8 16 1 1
ON
CO CO CO 2 2
OFF
Figure 1-4: Main Subrack RTU560C (configuration example with 23ET24)
1.2.1.3 Configuration Type RTU560D
The RTU560D is the smallest RTU560 configuration type, providing - in addition to the
local I/O connections - up to 4 communication interfaces (3 serial and 1 Ethernet
interface) to NCCs or Sub-Devices like Sub-RTUs, Protection Equipment, Bay Control
Units and IEDs (e.g. intelligent transducers).
One CMU 560CMU02 can be configured within a dedicated slot of the mounting plate
rack 560MPR01, thus building the RTU’s main subrack. Beside this reserved slot for the
CMU, 8 slots remain available for I/O boards, modems, RTCs or optical couplers from the
RTU560 board family.
The I/O bus segment is provided by the CMU’s serial interface CPB, internally connected
to the I/O bus on the backplane of the subrack 560MPR01. One additional subrack
560MPR01 can be connected to the main subrack, with 8 slots for additional I/O boards.
1-8 1KGT 150 589 V000 1 ABB AG

Figure 1-5: RTU560D with 560CMU02 and 560MPR01
1.2.1.4 Configuration type RTU560E
Fiber-optical converter 560FCO01 Backup-Battery
Power Supply
IO Board Modules
CMU Module
Figure 1-6: RTU560E housing and modules
ABB AG 1KGT 150 589 V000 1 1-9

The RTU560E housing allows to install the RTU56E near to the process. The shielding of
the housing is sufficient to fulfill the EMC profile for electrical substations. Within the
housing is space to install a battery for backup in case of AC voltage supply. In the lower
part is space to install the optional optical interface unit 560FOC01 or other small
modules (e.g. special modems). Thus no additional part may be needed to be installed
next to the RTU560E housing for standard applications.
There are two types of housing available:
• 560HOS01 R0001 for an RTU560E with CMU module, max. 3 I/O board modules and
power supply
• 560HOS01 R0002 for an RTU560E I/O board extension with maximum 4 I/O board
modules and power supply
The RTU560E I/O-box is an advantage for substations where the I/O-signals are located
in groups spread over the station area etc.
1-10 1KGT 150 589 V000 1 ABB AG

1.3 Software
The high processing performance of the RTU560 Remote Terminal Unit is accomplished
by effective distribution of the tasks to the communication and processing units (CMU)
and the microcontrollers on the I/O boards.
Each of the input/output boards has its own input/output microcontroller (IOC) which is
used to support the basic input/output functions of the board.
The CMUs have various tasks:
• Communication with the network control center(s)

• Communication with subordinated devices
• Updating of the data base for the process signals, handling of the SCADA
functions which are not performed by the I/O-boards
The different processors of a CMU (MPU and SLC) can work independently of each other
and are de-coupled from each other via shared memories. Different CMUs can handle
different tasks independently and communicate with each other via the internal system
bus. By this means optimal execution of the individual tasks is accomplished.
The program system of the RTU560 remote terminal unit is of modular design and
consists of the following program types:
• Micro-controller programs
• Standard programs
• Application programs
The micro-controller programs of the boards are optimized to the components and for the
defined functions. They are an integral part of the boards.
The standard programs written in C programming language cover the programs for all
telecontrol functions, for system monitoring, time management and for the handling of the
process data base.
The 32 bit operating system used in RTU560 is VxWorks® (Wind River Systems). The
PLC programs for the tasks of station automation functions are cyclically executed by the
optionally installed PLC software.
Figure 1-7: Software packages of RTU560
ABB AG 1KGT 150 589 V000 1 1-11

1.3.1 RTU560 Software Structure
The RTU560 software is structured into different activities. All activities can run on one
CMU or the activities can be distributed to different CMUs (not RTU560D or E). The
number of CMUs depends on type and number of the required communication interfaces.
NCCs
HCI
Host
Communication Data Configuration PLC
Interfaces Base Files IEC1131
IC Internal Communication
SCI PDP
MMI Central System
Sub-Device Board Control Process Data
Interfaces Control and Time
Communication and Diagnosis Processing and
Administration
Interfaces IO-Board
Control
IEDs Sub-RTUs Local I/O Board
Figure 1-8 Software Structure
The different activities and the distribution to the CMUs is configured automatically within
RTUtil560. The information is available in the configuration files.
IC Internal Communication
All activities communicate with each other via the internal communication (IC). The IC is
a protocol independent communication system. Every activity can distribute messages.
Every activity receives all messages distributed. The internal communication is used to
communicate between the activities of one CMU or between the activities on different
CMUs.
RTU560 System Control

This activity is running once in the RTU560. The System Control is handling the system
startup and supervision of all CMU boards. The runtime integration of a configured CMU
board is also handled by this activity.
This activity is not fixed to a specific CMU, but floating during runtime of the system. The
CMU board with the lowest rack- and slot-address is always used as Administration
Master in the system.
Time Administration
This activity is running once in the RTU560 on the CMU configured as Time-
Administrator Mode: Master. The Time Administration for the complete RTU560 is done
by this activity.
1-12 1KGT 150 589 V000 1 ABB AG

Board Control and Diagnosis
This activity is running once on each CMU with board. Board Control and Diagnosis is
handling startup and supervision of a CMU board. The Web-Server for Diagnosis belongs
to this activity.
PDP Process Data Processing and I/O Bus Master
This activity is running on each CMU for the interfaces COMA or COMB connected to I/O
bus segments. This activity handles the process data processing and supervision and
control of the local I/O boards. The serial line controller (SLC) is loaded with the I/O bus
master (IOM) firmware. The IOM controls the I/O bus interfaces (COMA and COMB). If
COMA or COMB is used for IOM, both interfaces can’t be used for HCI or SCI anymore
HCI Host Communication Interfaces
This activity is running on each CMU with interfaces COM1, COM2, COMA, COMB or
ETH which are connected to a control center communication line. It is possible to run
multiple HCIs on one CMU. The HCI activity handles the complete communication
protocol including all individual communication queues and buffers.
If COMA or COMB is used for HCI’s, the SLC is loaded with the communication interface
firmware, and can’t be used for IOM functionality anymore.
SCI Subordinate Device Communication Interfaces
This activity is running on each CMU with interfaces CP1, CP2, CPA or CPB connected
to a sub-device communication line. It is possible to run multiple SCIs on one CMU. The
SCI activity handles the complete communication protocol including all individual
communication queues and buffers.
If CPA or CPB is used for SCI’s, the SLC is loaded with the communication interface
firmware, and can’t be used for IOM functionality anymore.
Data Base
The Data Base activity is running on each CMU board. The data base collects all process
messages and all system status messages. In the data base the actual state of this data
points and the qualifiers are stored. The Web-Server shows the actual state of the data
base of the requested CMU.
PLC IEC 61131-3
It is possible to define one PLC activity per CMU board. The activity is running on each
CMU where a PLC FUNCTION is configured with RTUtil560. The PLC function can run
on a CMU with other communication functions (HCI or SCI). In these cases the priority of
the CMU is below the communication. It is possible to run a PLC function on a CMU
without communication functions (HCI or SCI).
MMI Interface
The MMI Interface activity is running on each CMU board. Via PPP protocol the diagnosis
Web-Server can be accessed (not 560CMU02, 560CMU05).
ABB AG 1KGT 150 589 V000 1 1-13

1.3.2 I/O Bus Master and RTU560 I/O Bus
The I/O bus master IOM is the master for the I/O boards connected to the RTU560 I/O
bus. The communication protocol between IOM and I/O board is tailored to achieve a
maximum throughput. The protocol is totally independent of any communication protocol
used to communicate with the network control center.
The main processing unit (MPU) is master to the IOM. The MPU stores any output
request to an I/O board etc. in a dialog RAM. The IOM will read that part and expand it to
complete dialogs with the addressed I/O board.
The IOM stores any event or answer from I/O boards in the dialog RAM and forces an
interrupt to the MPU if there is a message from IOM.
CMU
MPU
I/O Board
Input signal state
RAM Output signal state
Relocation register IOC

for ITI
I/O
SLC Bus- I/O
FIFO Part
module Task
Parameter
register
Requests
Dialog registers
Status etc.
Figure 1-9: Dialog RAM array between SLC and IOC
The main task of the IOM is to poll all configured boards for events.
To be independent of the board type (23BE23, 23AE23 etc.), a dialog RAM array is
specified which has the same structure for all RTU560 I/O boards with an I/O controller
(IOC). Within the IOC software the "Bus module" task handles in a standardized form the
dialog with the IOM. The IOC reads and writes directly into the dedicated registers and
informs the bus module.
The bus module handles the dialog RAM for the I/O task. The I/O task is board specific.
1-14 1KGT 150 589 V000 1 ABB AG

Subrack: = 1
Read event flag of subrack
NO
Is there any event
message within subrack ?
YES
Read event flag of each configured board within

subrack.
Create list of board with event
Read one event into RAM to MPU.

Increment event list pointer
Address next board with event
More events YES

Subrack: = subrack + 1
in subrack ?
NO
NO
All subracks polled
for events ?
YES
Poll one board and read board status

Increment board pointer
NO
Board status o.k.
?
Store board status into
RAM to MPU
YES
Command output requests will be inserted if pending
Figure 1-10: Event polling by MPU
1.3.3 Event Flow through RTU560
Figure 1-11 explains and qualifies the different levels which an event has to pass before
it is transmitted to the NCC.
ABB AG 1KGT 150 589 V000 1 1-15

NCC Network Control Center
Communication
Buffer, Queues
Signal processing MPU

MPU - HCI Task < 1 ms / event
Internal Communication
IC < 1 ms / event
Signal processing MPU

< 1 ms / event MPU
MPU- SCI
- HCITask
Task MPU - PDP Task Signal processing MPU
< 1 ms / event
IED or Sub-Station RAM
SLC - IOM Task I/O bus transmission

typ. 20 .. 60 ms for a complete polling cycle
(approx. 7 ms / event)
FIFO
Process signal scanning and peprocessing

IOC time depends on signal type
Binary input: 1 ms cycle
Analog input: typ. 580 ms (at 50 Hz)
Process Signal
Figure 1-11: Event flow through RTU560
SLC – IOM Task
The transmission time from I/O board to the MPU depends on the overall situation of the
IOM.
• Number of subracks and boards

• Number of pending events within a subrack
• Output requests from MPU to I/O board
• To increase the transmission time it is possible to split the I/O boards on up to 4
I/O bus segments managed by up to four CMUs.
MPU
The transmission time through the MPU depends on the CMU configuration.
PDP and HCI may run on the same CPU or on different CPUs
1-16 1KGT 150 589 V000 1 ABB AG

1.4 Tools
The RTU560 is easy to engineer and maintain by using the utility RTUtil560 to configure
the RTU560, MULTIPROG wt to program and test the PLC functions and the RTU560
Web-Server for diagnosis and file transfer issues. There is no proprietary tool delivered
by ABB for protocol analysis issues. For further information ask your local distributor to
get a recommendation for third party protocol analysis tools.
1.4.1 RTUtil560
RTUtil560 is the configuration and engineering tool for the RTU560, contains the
following topics and features:
• Configuration and engineering tool for RTU560 networks

• Generating of files for each RTU560
• The principles of user interface structuring according to IEC 61346-1
• MS Windows 2000 / XP professional platform
• The User Interface of RTUtil560 is application based on the Microsoft standard
presentation format
• Documentation of all project steps
• External data interface
• Multilingual tool (user interface and help files)
• Delivered on CD-ROM with installation and uninstall program
1.4.1.1 RTUtil560 System Requirements
The performance requirements for the configuration and engineering tool RTUtil560,
(especially the free disc space) depends on the project size. Basic requirements are:
• Operating system: Microsoft Windows 2000 / XP professional

• Memory: 64 MB RAM
• Processor: Pentium class
• Hard disc: > 200 MB free disc space
1.4.1.2 Basic Concept
RTUtil560 is designed to engineer all types and sizes of RTU560 including interfaces to
IEDs that are used in a common station network. The process signal mapping to the
different communication protocols is one of the main tasks needed in hierarchical
communication network structures.
The general view of the user to the engineering data is implemented on the basis of
international Standard IEC 61346-1. This Standard describes the structuring principles
and reference designations for industrial systems, installations and equipment.
ABB AG 1KGT 150 589 V000 1 1-17

The user interface structure offers three trees to build up the system.
• Network Tree
The Network Tree shows the lines and protocols for routing the data points through
the network.
• Signal Tree
The location and designation of signals are shown in the Signal Tree. The signal
location describes the place of the data points in the primary process.
• Hardware Tree
The Hardware Tree presents the structure of an RTU with the levels cabinet, rack,
board and the reference to the data points defined in Signal Tree.
The structuring in trees allows a common presentation format and a general user
interface of the RTU data and the environment.
04 Plant Ladenburg 110kV

CS 1 CS 2
Line 1 Line 2 Segment 1 Segmen 2

Line 1 Line 2 Com Subrack 560CSR01 Rack TP21 Rack TP 21
RTU 01
23 NG 23560SLI01
Tx RxCE 560SLI01
Tx RxCE
Line 3 Line 4 5V
24V
1
MMI
A
2
1
1
MMI
2
1
UP B
2 B
A
2
On
Off
A
B A
B
Q0
RTU 11 RTU 21 Segment 1 Segment 2
Rack TP21 Rack TP21
SPAx1 Line 3 Line 4

RTU 12 Line 5
Peripherie Bus
SPAx2
SPAx2 21.03 MW
Figure 1-12: Network – RTU Hardware – Primary Process
1.4.1.3 Engineering Steps
The engineering of the RTU560 data consists of several steps that demand a sequence
in the data engineering process. The engineering steps could be different, if interfaces for
external data import are used (e. g. Excel import). The following steps describe the basic
engineering sequence:
• Project configuration (start)

• Set the project environment data.
• Build up the tree structures
Build up the station network topology in the Network Tree. Define the lines and the
communication protocols between the stations. The Network Tree is required for routing
the process data points through the RTU network.
Definition of data points in Signal Tree. The Result of this definition is the unique object
identifier for each data point.
Definition of all RTUs and IEDs with their data points in the Hardware Tree. The
Hardware Tree contains the full description of the RTU hardware in detail (cabinets,
racks, boards). Also link steps to build up the relations between the trees are done in the
Hardware Tree.
1-18 1KGT 150 589 V000 1 ABB AG

If a data point is added or linked to the Hardware Tree the automatic signal routing
functionality for this data point will be executed. The signal routing depends on the
topology and the communication protocols in the Network Tree.
• Set parameters, communication addresses

• Set single parameters for several tree objects.
• Check project plausibility and generate the download file for a single RTU.
• Documentation
Generate the project documentation. Choose the RTU and the configuration parts, which
have to be documented.
1.4.2 RTU560 Web Server
The RTU560 Web Server, integrated in the RTU560 firmware, presents information to a
standard browser (e. g. Microsoft Explorer) and offers the following functions:
• Loading configuration files to and from the RTU

• Loading firmware to the RTU
• System diagnosis with a chronological view to events in the RTU
• Process diagnosis that indicates the actual process status
• Display of archives
• Time administration
• Administrate different user groups
1.4.2.1 RTU560 Web-Server System Requirements
To get access to the RTU560 Web-Server pages a standard browser with Java Script
implementation is needed. There are no restrictions to the operating system that is used.
The physical connection to the RTU may be a serial connection (PPP) or an Ethernet
connection.
1.4.2.2 System Diagnosis
The system diagnosis indicates RTU560 events in a list in chronological order. The
information for each indication in this list is structured as follows:
• Date
• Time
• Indication text
ABB AG 1KGT 150 589 V000 1 1-19

1.4.2.3 Status information
The status information page shows the RTU560 hardware structure as known from the
RTUtil560 Hardware Tree. Next to the static hardware configuration following information
is provided:
• Display the actual process data states for all information in monitoring direction
• Get information about the actual state of the system event and status indications
• Get information about several parameters (e. g. TCP/IP address of the Ethernet
board)
1.4.2.4 Archive Information
This menu point will display the archived information from the CompactFlash:
• Events and Indications, Commands

• Measured Values
• Counter Values
• Files
1.4.2.5 Configuration File Transfer
The user menu allows the following operations:
• Get information about the actual used file versions

• Write of the GCD-File to the RTU (basic hardware data of the RTU)
• Write of the IOD-File to the RTU (IO data of the RTU)
• Read of the IOD-File from the RTU (to extract a complete RTUtil560 project from
the configuration file)
• Delete GCD-File file in the RTU's file system
• Delete IOD-File file in the RTU's file system
• Reset of the RTU
1.4.2.6 Firmware File Transfer
The user menu allows the following operations:
• Get information about the actual used firmware version

• Loading of the application firmware files to the RTU
• Loading of the IO-Bus Master firmware files to the RTU
• Loading of the license file to the RTU
• Reset of the RTU
1-20 1KGT 150 589 V000 1 ABB AG

1.4.2.7 Administration
The administrator point in the RTU560 Web-Server allows to restrict the access to the
different pages on the RTU.
• Modify user groups (add or delete new users)

• Change passwords for existing users
1.4.3 MULTIPROG wt
The RTU 560 PLC development system MULTIPROG wt is a standard programming and
test system for IEC 61131-3 designed PLCs. It is based on the standard IEC 61131-3.
MULTIPROG wt allows an easy programming supporting the following languages:
• FBD Function Block Diagram

• IL Instruction List
• LD Ladder Diagram
• SFC Sequential Function Chart
• ST Structured Text
The programming system offers powerful features for the different development steps of
a PLC application:
• Edit
• Compile
• Debug
• Print
The programming system is based on a modern 32 bit windows technology, providing
comfortable handling using:
• zooming scrolling
• customizable toolbars
• drag & drop operations
• a shortcut manager
• movable windows.
1.4.3.1 MULTIPROG wt System Requirements
To run the MULTIPROG wt PLC programming system, the following workstation

requirements must at least be fulfilled
• Operating system: Microsoft Windows 2000 / XP professional

• Memory: 64 MB RAM
• Processor: Pentium class (133 MHz minimum, >200 MHz Recommended)
• Hard disc: > 60MB free disc space
• Hard lock (dongle)
ABB AG 1KGT 150 589 V000 1 1-21

2 SCADA Monitoring Direction
The following SCADA functions are described for the I/O boards 23BE23/23BE40 and
23AE23 of RTU560 A/C/D. If not otherwise noticed, they are also available within
560MIO80 of the RTU560E.
2.1 Indication Processing
There are two types of indications:
• Single point input (SPI)

• Double point input (DPI)
Figure 2-1 shows the signal definition for SPI and DPI. Double indications are
represented by two sequential bits within a 23BE23/23BE40 board. The normal state of a
DPI is a non-equivalent bit combination (10 or 01). An intermediate state (00) is given
during the runtime of a unit from one position to the other (e.g. an isolator from OFF to
ON).
Signal state Double point indication (DPI) Signal state Single point indication (SPI)
ON 1
OFF 1
0 OFF 0
ON 1
0
10 00 01 11 0 1 0
OFF ON OFF ON OFF
faulty position
OFF
normal position intermediate position ON
16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 Bit position within board
DPI 8 DPI 7 DPI 6 DPI 5 DPI 4 DPI 3 DPI 2 DPI 1 DPI number within board
Figure 2-1: Indication Type Definition
The definition of the bit position for ON and OFF can be changed for the whole
configuration. If changed, this definition is also valid for DCO and RCO commands.
Parameter: Change ON and OFF connection point (RTU

Parameters)
Within an indication board SPI and DPI can be mixed. But a DPI can start on an odd bit-
position only. Within a 23BE23/23BE40 board it is possible to mix any type of binary
inputs. E.g. inputs not assigned to DPI or SPI may be configured to indications as pulse
counters, digital measured values on bit string inputs. Digital measured values and bit
string inputs must be configured starting with bit position 1 or 9.
ABB AG 1KGT 150 589 V000 1 2-1

SCADA Monitoring Direction Remote Terminal Unit RTU560
2.1.1 Function Distribution
The process data acquisition functions for indications processed by the RTU560 can be
split into functions handled by the:
• I/O controller (IOC) of the binary input board 23BE2323BE40

• Process data processing (PDP) part of the CMU
• Protocol specific communication interface part at a CMU
The data processing functions of the communication interface is described in the

documentation of the specific communication protocol.
23BE23/23BE40 functions:
- Reading input register (every millisecond)

- Digital filter (contact bouncing)
- Oscillation suppression (signal chattering)
- Signal inversion
- Time out monitoring for DPI intermediate position
- Store events in FIFO with time stamp
CMU - PDP:
- Intermediate midpoint position handling for DPI

- Command output response
- Group signals
- Transmission to internal communication
2.1.2 23BE23/23BE40 Functions
The IOC of the 23BE23/23BE40 supports the indication functions. The parameter of each
function is loaded from PDP part of the CMU at start up or if it must be initialized. Some
parameters are valid for the 16 inputs, others can be set individually per input.
The 23BE23/23BE40 reads all 16 inputs periodically every millisecond regardless of

specified data point type. The IOC handles the necessary activities for all 16 bits within
that millisecond. Reading every millisecond allows the high event resolution for
indications. Each board does this independently from each other for a block of 16 bits.
If the data point is Blocked the status is set to ‘blocked’ and no changes are reported
from the PDP.
Parameter: Blocked (SPI/DPI– PDP Parameters)
2-2 1KGT 150 589 V000 1 ABB AG

Remote Terminal Unit RTU560 SCADA Monitoring Direction
Digital Filter
The configuration parameter Digital filter specifies how many milliseconds an input must
be stable before it is accepted as a new signal state. The typical value is 10 ms. Digital
filter is used to prevent ordinary contact bouncing.
Parameter: Digital filter (SPI/DPI– PDP Parameters)
If an indication has changed its state and should be transmitted as an event to the PDP,
the time stamp of the event is the time of the last edge before the filter time elapsed.
1
input channel
0
digital filter time

counter 255
digital filter time
(e.g. 7 ms)
7
6
5
4
3
2
1
0
time
1ms (a)
event into FIFO

with
time stamp of (a)
Figure 2-2: Digital Filter for Contact Bouncing
ABB AG 1KGT 150 589 V000 1 2-3

Oscillation Suppression
Indications which change their state very often produce a higher transmission load to
NCC. To prevent a permanent transmission it is possible to specify an automatic
indication blocking if the number of events per time period exceeds a defined value.
Oscillation suppression may be activated or deactivated individually per indication. The
configuration parameter is Maximum chatter frequency
Maximum Chatter Frequency is defined to:
MAX CHA FREQ = number of changes

second
The monitoring period is calculated:
2000
Tosc = [milliseconds]
MAX CHA FREQ
Parameter: Maximum Chatter Frequency (SPI/DPI – PDP Parameters)
Tosc is the monitoring period. The maximum value is 100Hz, a typical value is 2.
The 23BE23/23BE40 is loaded with the parameter. Each leading edge of 0->1 starts the
monitoring period tosc. Within that time interval each leading edge increments the chatter
counter register of that indication. The third change within that period puts the indication
into the dynamically blocked state. The 23BE23/23BE40 informs the PDP by an internal
event. It starts a reset time period (fix to 60 seconds). Within that reset time each new
start trigger (0->1 edge) starts tosc again. If the indication state is stable for at least this
reset time period, the 23BE23/23BE40 informs PDP by again by an internal event.
Input channel
1
indication 0
60 sec
chatter counter reset time
register
3
2
1
0
tosc tosc tosc time
event into FIFO event into FIFO

with status: with status:
Input = Invalid Input = Valid
Figure 2-3: Oscillation Suppression on 23BE23/23BE40
2-4 1KGT 150 589 V000 1 ABB AG

Intermediate Position Handling for DPI
The 23BE23/23BE40 handles the two bits of the double indication. Signal state changes
of the DPI are transmitted to the PDP. Intermediate positions (00) are indicated by a
special status bit to PDP. The 23BE23/23BE40 monitors the time window for intermediate
position. The time out value is loaded as a parameter from PDP. If the DPI does not get a
new end position within the allowed time, the 23BE23/23BE40 generates an event with
the actual state and status DPI intermediate position time out.
FIFO storage on 23BE23/23BE40
To de-couple event bursts from I/O bus transmission etc., the events are stored into the
23BE23/23BE40 board FIFO. Up to 50 events can be stored within the FIFO. If the FIFO
becomes full, the 23BE23/23BE40 stops its activities until there is space. Each event has
a time stamp with a resolution of one millisecond within a minute. The absolute time is
expanded by the PDP.
2.1.3 PDP Functions of the CMU
The PDP receives all events out of the 23BE23/23BE40 FIFO. The PDP handles all other
functions specified for that indication.
Command output response
The functionality of a response indication to stop a related command output pulse is

described at command processing section of this document.
Intermediate Position suppression for DPI
This function is only valid for double indications (DPI). Figure 2-4 shows how that is
handled within the RTU560.
The configuration parameter Supervision Time for Midpoint specifies whether or not a
DPI message should be transmitted for the event when the indication changes to a mid-
position (00). PDP keeps the first signal change internal. If an abnormal situation occurs,
the message of the leading edge is sent to NCC in addition and allows a more detailed
analysis of the error situation of the unit.
The parameter Supervision time for midpoint specifies the time window where the
RTU560 should inhibit the transmission of the mid-position (00). If the new state is not
indicated to the RTU in this time the RTU generates a DPI telegram with the actual
position (normally then 00). The qualifier IV (invalid) keeps 0, because this is a valid
process information.
Parameter: Supervision time for midpoint (DPI – PDP Parameters)
If the supervision for the midpoint is enabled, the RTU560 will also inhibit the
transmission of the faulty position (11) for a fixed time of three seconds.
ABB AG 1KGT 150 589 V000 1 2-5

Supervision time for mid point = active

Supervision time
1
ON Normal signal state change
0
ON -> OFF
OFF 1
0
DPI
1
ON Abnormal state change
0
ON -> intermediate -> ON
1
OFF
0
DPI
1
ON DPI
0
Abnormal state change
1 time out
OFF
0
DPI
Supervision time for mid point = inactive

1
ON
0 Normal signal state change
OFF 1 ON -> OFF
0
DPI DPI
1
ON Abnormal state change
0
ON -> intermediate -> ON
1
OFF
0
DPI DPI
1
ON
0
Abnormal state change
1 time out
OFF
0
DPI
Figure 2-4: Mid-Position suppression for Double Point Inputs
2-6 1KGT 150 589 V000 1 ABB AG

Signal Inversion
After having a stable indication signal it is possible to define the logical state for the
signal, corresponding to the signal voltage level. This function is the signal inversion. The
inversion is defined by a configuration parameter Invert the input value.
INVERSION = NO INVERSION = YES

logical 0 = OFF 0V Process Voltage
logical 1 = ON Process Voltage 0V
Table 2-1: Definition of Inversion
All other functions are then based on the signal state given by the inversion parameter.
Parameter: Invert the input value (SPI/DPI – PDP Parameters)
2.1.4 Group Information
Group information are single point information (SPI) data objects that are calculated from
other SPI´s or System Events (SEV) by logical operations.
The RTU560 supports different group information types:
• OR groups (>=)
• AND groups (&)
• NOR groups
• Dynamic OR groups
A group information data object can be generated out of all single point information (SPI)
and System Events (SEV) processed in the RTU560. A group information can also be an
input to another group information.
The number of input signals per group information is limited to 32 signals.
The group information output is communicated as SPI event on the internal

communication. The time stamp of the event will be the time of the input signal which
forces the new event message.
OR group
The output signal of an OR group is set to 1 when at least one input signal is set to 1.
The first signal, which is set to 1, forces the transmission of the OR group signal.
The output signal of an OR group is set to 0, when all input signals are 0. The trailing
edge of the last signal which is set to 0 forces the transmission of the OR group signal.
ABB AG 1KGT 150 589 V000 1 2-7

AND group
The output signal of an AND group is set to 1 when all input signals are set to 1. The last
input signal which is set to 1 forces the transmission of the AND group signal.
The output signal of an AND group is set to 0, when at least one input signal goes to 0.
The trailing edge of this signal forces the transmission of the AND group signal.
NOR group
The output signal of a NOR group is set to 0 when at least one input signal is set to 1.
The first signal which is set to 1 forces the transmission of the NOR group signal.
The output signal of a NOR group is set to 1, when all input signal are 0. The trailing
edge of the last signal which is set to 0 forces the transmission of the NOR group signal.
Dynamic OR group
The output signal of a dynamic OR group is set to 1 every time a input signal is set to 1.
Every signal which is set to 1 forces the transmission of the OR group signal.
The output signal of a dynamic OR group is set to 0, when all input signal are 0. The
trailing edge of the last signal which is set to 0 forces the transmission of the OR group
signal.
Qualifier for group signals
A group signal qualifier represents the logical OR of the qualifiers of all input signals of
the group information. That means, that if the state of one of the inputs is not equal to
O.K., the output of the logic function is set to this state.
2-8 1KGT 150 589 V000 1 ABB AG

2.1.5 Error Handling
23BE23/23BE40 board failure
A 23BE23/23BE40 board can be set "out of service":
• the board has never been in service

(configuration error)
• the board failed during normal operation
(hardware failure, I/O bus failure etc.)
• the board has been removed or subrack power was lost.
• If a board is set out of service the qualifiers of all configured indications are set
INVALID due to board failure. The RTU560 treats all DPI and SPI messages of
that board with qualifiers IV = 1.
A 23BE23/23BE40 board can be set in service again during runtime:
• if the board is replaced

• if power is turned on again in the subrack
• if the I/O bus is O.K.
When this happens the following sequence recovers the indications:
• normalize the 23BE23/23BE40

• load all parameters for the configured indications (done by PDP)
• read all values (signal state)
• Reset qualifier IV to 0 and transmit the actual value and qualifier status to NCC.
Dynamic Qualifier Changes
An indication can change qualifier status at runtime if:
• the 23BE23/23BE40 board fails (qualifier IV = 1)

• the oscillation suppression is activated and triggered for that indication.
2.1.6 Indication Processing with 560MIO80
The Multi In-/Output Board 560MIO80 of the RTU560E has also 16 binary input channels
with the same features as the 23BE23/23BE40.
ABB AG 1KGT 150 589 V000 1 2-9

2.2 Analog Measured Information Processing
2.2.1 Analog Measured Information (AMI) Types
Each analog value is converted by the analog digital converter (ADC) of the 23AE23
board into a signed integer presentation. The presentation is shown in Figure 2-5. The
100% input signal value is represented with 12 bit plus sign.
[digits]
+ 4096
3000
e.g. -20..+20
2000 mA
1000
-20 -15 -10 -5 5 10 15 20 [e.g. mA]

-100 25 50 75 100 [%]
-2000
Input signal
-3000
- 4096
Analog Value Presentation according to IEC 870-5-101
Figure 2-5: Analog Value Presentation by ADC
The PDP converts the value to a normalized presentation.
The process data acquisition functions for analog measured information processed by the
RTU560 can be split into functions handled by:
• IOC of the analog input board 23AE23

• Protocol specific communication interface at a CMU
2-10 1KGT 150 589 V000 1 ABB AG

23AE23:
- Scan analog input cyclically

- Zero value supervision and switching detection
- Smoothing
- Threshold supervision on integrator algorithm
- Periodic update of RTU data base
- Store events into FIFO with time stamp
CMU - PDP functions:
- Unipolar and live zero conversion

- Scaling
- Threshold supervision on absolute threshold value
2.2.3 23AE23 Functions
The IOC of the 23AE23 board supports the analog measured information functions. The
parameters of each function and each AMI are loaded from PDP at start up or if the
board must be initialized during runtime.
If the data point is blocked the status is set to Blocked and no changes are reported from
the PDP.
Parameter: Blocked (AMI – PDP Parameters)
Line Frequency and Scan Cycle
Each channel is scanned by the IOC of the 23AE23 cyclically. The scan cycle is given by
the AC line frequency:
• 50 Hz: 580 milliseconds for all 8 channels

• 60 Hz: 500 milliseconds for all 8 channels
• 16.6 Hz: 1620 milliseconds for all 8 channels
The scan frequency is independent from the number of configured channels. The Line
frequency must be equal to the 23AE23 hardware setting (board wide parameter).
Parameter: Line frequency (AMI – PDP Parameter)
ABB AG 1KGT 150 589 V000 1 2-11

Zero Value Supervision and Switching Detection
A low input signal can be forced to 0 %. This allows to reject noise on the input signal
produced by the transducer etc. The zero value supervision is configurable with
RTUtil560 between ± 0.1% and ± 5%. The default value is set to ± 0.25 %.
Parameter: Zero Range (AMI – PDP Parameter)
The switching detection is a special function of the 23AE23. It is used to force a value
update to PDP if a signal changes only some few percent from/to zero. The function is
only active when threshold supervision with integration is selected. The threshold
supervision on integrator algorithm would need some cycles before the threshold is
exceeded and reported to NCC. This gives a transient situation, e.g. the 380 kV
transmission line is switched but the actual current does not change more or less
immediately.
Switching detection operates in that form that every time a signal changes to/from 0 %
from/to more than ± 2.5 % the new value is transmitted to PDP immediately. If the new
value is below ± 2.5 % an event is not forced. PDP transmits the received value to NCC
regardless of any other parameter.
Switching detection is a fixed parameter and can not be parameterized
Event transmission to UB due to

switching detection
Input Signal
[%]
+2.5
+0.25
zero value 0
zone
time
- 0.25
scan cycle
23AE21
-2.5
Figure 2-6: Zero Value Supervision and Switching Detection
2-12 1KGT 150 589 V000 1 ABB AG

Smoothing
Unstable input signals may be smoothed to prevent too many CS updates. Smoothing
can be parameterized per input by the configuration parameter Smoothing. No smoothing
can be configured. The smoothing factor is given in binary factors.
Parameter: Smoothing (AMI – PDP Parameter)
Input Signal
MW
[%]
80
70
60
50
40
30 MWngl for e.g. k=2
20
10
time
scan cycle
23AE21
Figure 2-7: Smoothing of Analog Values
The IOC calculates the new value by the formula:
MW − MWagl
MWngl = + MWagl
K
MWngl = new calculated analog measured value

MW = raw analog measured value (result of A/D conversion)
MWagl = last calculated value
k = smoothing factor (1, 2, 4, 8, 16, .. 128)
ABB AG 1KGT 150 589 V000 1 2-13

Threshold Supervision on Integrator Algorithm
Threshold supervision can be done on two different methods within RTU560. The
decision of which method is active depends on the configured parameters.
If threshold supervision with integration is selected the 23AE23 board is doing it. The IOC
calculates at each cycle the difference between the last reported analog value and the
actual value. The difference is added to the accumulated value in the threshold difference
register. If the accumulated deltas exceed the parameterized threshold value, the actual
value is stored into the FIFO and reported to the PDP. The actual value becomes the last
reported value. The threshold difference register is set to zero. The accumulation is done
in consideration of the sign of the difference.
Input Signal
[%]
60 new value
transmission
new value new value
transmission transmission
40
20
deltas (differences) to last reported value
0
time
scan cycle
23AE21
Threshold Difference-
Register exceed threshold exceed threshold exceed threshold
[% of input signal]
+ 10
+ threshold
0
- threshold time
-10
example = threshold = 10 % of input signal
Figure 2-8: Threshold Supervision with Integration
2-14 1KGT 150 589 V000 1 ABB AG

The threshold difference register is cleared if:
• the value exceeds the threshold value

• the switching detection supervision was triggered
• the value passed a monitored limit
The threshold value can be parameterized by Threshold. To be independent of the scan

cycle the threshold is calculated on a threshold integration per second. The threshold is
rescaled according to the Line frequency:
• 50 Hz: threshold base 1s = Threshold / 0.58 = 12%

• 60 Hz: threshold base 1s = Threshold / 0.5 = 10%
• 16.6 Hz: threshold base 1s = Threshold / 1.62 = 25%
Parameter: Threshold ( AMI – PDP Parameter)

Line frequency ( AMI – PDP Parameter)
Periodic update of RTU data base
If a periodic update of the RTU560 data base is required, the 23AE23 board can be
parameterized to transmit the AMI periodically. The configuration parameter Periodic
Update specifies how often the data base should be updated.
Parameter: Periodic Update ( AMI – PDP Parameter)
The periodic update is independent of threshold supervision with integration. That means
a value might be transmitted twice to PDP in a cycle:
• caused by threshold exceeding
• caused by periodic update
The periodic update time is selectable between 1, 2, 4, 8, 30 and 60 seconds.
FIFO storage of 23AE23
To de-couple event bursts from I/O bus transmission etc. the events are stored into the
23AE23 board FIFO. Up to 50 events can be stored within the FIFO. If the FIFO becomes
full and the IOC has to store events it stops its activities until there is space. Each event
has a time stamp with a resolution of one millisecond within a minute. The absolute time
is expanded by the PDP.
For each measured value written to the FIFO the IOC reads the actual time. The effective
time quality is equivalent to the scan cycle of the analog input board.
ABB AG 1KGT 150 589 V000 1 2-15

Bipolar, Unipolar and Live Zero conversion
The input signal type allows to specify unipolar input signals. That means a negative
value is not allowed. The RTU560 flags a unipolar defined input signal with the qualifier
invalid (qualifier IV = 1) if the value becomes negative (> Zero Value Supervision).
Input signals with live zero presentation (standard = 4..20 mA) are transformed to the
standard presentation of –100% respectively 0% up to 100 % by the PDP. The
conversion is done in the form that:
• 20 % of the input signal rage (standard: 4 mA) becomes –100% respectively 0% of

the normalized AMI value
• 100 % of the input signal rage (standard: 20 mA) becomes 100 % of the
normalized AMI value
Input signals below 20 % (4 mA) are set to –100% respectively 0%. For a value below
3,5 mA the AMI is indicated to be faulty (qualifier IV=1)
The configuration parameter Input signal type specifies the input is a bipolar, a unipolar
or a live zero signal. The configuration parameter ‘Input signal range’ specifies the
hardware setting of the 23AE23 board.
Parameter: Input signal range (AMI – PDP Parameter)

Input signal type (AMI – PDP Parameter)
Adjust zero value for live zero signal (AMI – PDP Parameter)
Scaling
The PDP converts the value to a normalized AMI format. The parameter Conversion
factor specifies the percentage of the maximum input signal that is defined as 100 % of
the normalized value.
Parameter: Conversion factor (AMI – PDP Parameter)
2-16 1KGT 150 589 V000 1 ABB AG

Unipolar Bipolar
1 1
-100% 100% -100% 100%
-1 -1
Figure 2-9: Example unipolar / bipolar measurement
Live Zero 4 … 40 mA
1 1
-100 20 40 60 80 100 8 16 24 32 40
[% Imax] [mA]
1 … 5 mA
2 … 10 mA
4 … 20 mA
8 … 40 mA -1 -1
Figure 2-10: Example Live Zero measurements

Conversion Factor Adjust Live Zero
1 1
-100 20 40 60 80 100 4 12 20
[%] [mA]
-1 -1
Figure 2-11: Example “Conversion Factor” and “Adjust Live Zero”
ABB AG 1KGT 150 589 V000 1 2-17

Threshold Supervision on absolute Threshold Value
Threshold supervision can be done on two different methods within RTU560. The
Threshold Supervision on absolute Threshold Value is done in the PDP.
In this mode the PDP checks each AMI received from 23AE23 against the last reported
value. If the new value exceeds the last reported value plus threshold the received AMI
will become last reported value and is transmitted to NCC.
The threshold value can be parameterized by Threshold. The threshold is monitored

every nn seconds. Therefore the 23AE23 transmits the actual value periodically. The
period is given by the configuration parameter Periodic update.
Parameter: Threshold (AMI – PDP Parameter)

Periodic update (AMI – PDP Parameter)
Input
[%]
new value
100
new value
new value
80
new value
60 threshold value
new value
40
New value transmission to CCI
20
time
periodic
update cycle (uc)
Figure 2-12: Threshold Supervision on Absolute Value
Only one method can be used for threshold supervision. Either the integration method or
nor absolute threshold.
2-18 1KGT 150 589 V000 1 ABB AG

AMV overflow and/or A/D converter errors
The 23AE23 board checks at start up and during each conversion the functionality of the
A/D converter. If an error is detected the AMIs are marked invalid. The qualifier IV is set
to 1 and transmitted to NCC with the new state.
For AMIs with live zero conversion, a value below 3,5 mA is marked as invalid.
23AE23 board failure
A 23AE23 board can be set "out of service":

• the board has been removed on-line or subrack power was lost.
If a board is set out of service all configured AMIs are set to the invalid state. The
RTU560 transmits all AMI messages of that board to the NCC with the qualifier IV = 1.
A 23AE23 board can be set in service again during runtime:

When this happens the following sequence recovers the AMIs:
• normalize the 23AE23

• load all parameters for configured channels (from PDP)
• read all values and update status
• reset qualifier IV to 0 and transmit the actual value and qualifier status to NCC.
An AMI can change qualifier status at runtime if:
• the 23AE23 board fails (qualifier IV = 1)

• the live zero supervision detects a current below 3.5 mA (qualifier IV = 1)
• the unipolar value is below –Zero Range (qualifier IV=1)
• the value has an overflow of the ADC signal input (qualifier OV = 1)
• the scaling by means of conversion factor gives a result of more than 100 %
(qualifier OV = 1)
ABB AG 1KGT 150 589 V000 1 2-19

2.2.6 Analog Measured Value Processing with 560MIO80
The Multi In-/Output Board 560MIO80 of the RTU560E has 4 analog input channels with
the same features as the 23AE23.
2.3 Digital Measured Value Processing
There are two types of digital measured values:
• Digital measured input value (DMI)

• Step position input value (STI)
The RTU560 can handle different bit pattern to read them and convert them into a digital
measured value:
• 8 bit digital measured value (DMI8)

• 16 bit digital measured value (DMI16)
• 8 bit step position value (STI)
The RTU can handle conversions for:
• binary data (BIN)

• binary coded decimals (BCD)
• Gray code (GRAY)
The maximum length of a digital measured value is the word of 16 bit

(= one 23BE23/23BE40 board). Double word values (32 bit) are not supported.
2-20 1KGT 150 589 V000 1 ABB AG

Digital measured value presentation
Each type is converted and scaled by the PDP.
16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 23BE21 Input Channel
S Scaling and/or Conversion
16 bit unsigned binary data
S 15 bit + sign binary data
S 7 bit + sign binary data
0..9 0..9 0..9 0..9 4 Decade BCD unsigned
S 0..7 0..9 0..9 0..9 4 Decade BCD signed
0..9 0..9 2 Decade BCD unsigned
S 0..7 0..9 2 Decade BCD signed
16 bit gray code
S 15 bit signed gray code
8 bit gray code
STI
S Step Position
(Value = -64 ... +63 steps)
S Signed Integer
DMI
value
two's complement
S = Sign bit
Figure 2-13: Digital Measured Value presentation
ABB AG 1KGT 150 589 V000 1 2-21

The IOC of the 23BE23/23BE40 board supports the digital measured value (DMI)
functions. The parameter of each function and each DMI is loaded from PDP at start up
or if the board must be initialized during runtime.
The 23BE23/23BE40 reads all 16 inputs periodically every millisecond regardless of the
that millisecond.
If the data point is Blocked the status is set to ‘blocked’ and no changes are reported
from the PDP.
Parameter: Blocked (DMI/STI – PDP Parameters)
Digital filter
filter are used to prevent ordinary contact bouncing.
Parameter: Digital filter (DMI/STI – PDP Parameters)
Consistency check
A DMI is a bit pattern of 8 or 16 bit length. The value is valid only if all binary channels of
the DMV are valid and stable for at least the consistency check time. This is given if no
input changed for the parameterized consistency check time. Any change on an input
channel re-triggers the settling time.
The minimum settling time is defined by the PDP parameter Consistency check time. The
minimum consistency time is 100 milliseconds.
Parameter: Consistency check time (DMI/STI – PDP Parameters)
FIFO storage of 23BE23/23BE40
If a DMI has changed and is stable for at least the consistency time, it is stored into the
FIFO and transmitted to the PDP.
2-22 1KGT 150 589 V000 1 ABB AG

The PDP receives all events out of the 23BE23/23BE40 FIFO. The PDP handles all other
functions specified for that DMI.
Signal Inversion
Inversion is only possible for DMI not for STI inputs. The PDP parameters Invert input
signal and Invert sign of input value specify a bit inversion of the digital input value. The
inversion of the sign bit can be configured independent from the inversion of the value
bits.
Parameter: Invert the input signal (DMI – PDP Parameters)

Invert the sign of input value (DMI – PDP Parameters)
DMI 8 S 7 6 5 4 3 2 1
Process Input PV 0V 0V 0V 0V 0V 0V PV
Invert the Invert the

input value sign
= NO = NO 1 0 0 0 0 0 0 1
= YES = NO 1 1 1 1 1 1 1 0
= NO = YES 0 0 0 0 0 0 0 1
= YES = YES 0 1 1 1 1 1 1 0
0V = 0V; PV = Process voltage; S = Sign bit
Figure 2-14: Example for inversion of DMI8
Scaling and format conversion
The PDP parameter DMI/STI Value presentation and Input signal type specifies which
DMI type is connected to the 23BE23/23BE40 board.
STI values are always handled as 7 bit signed integer, range -63 ... +63. For DMI inputs,
the parameter Maximum value specifies the binary value that is converted to 100 % of the
scaled DMV value. The binary value of the STI is limited to the range – 63 to +63.
Parameter: DMI/STI Value presentation (DMI/STI – PDP Parameters)

Input signal type (DMI – PDP Parameters)
Maximum value (DMI – PDP Parameters)
ABB AG 1KGT 150 589 V000 1 2-23


If a board is set out of service the configured digital measured values are to the invalid
state. All DMI/STI are set faulty. The RTU560 transmits the DMI/STI values of that board
to the NCC with the corresponding message and the qualifier IV = 1.

When this happens the following sequence recovers the DMIs:

• load all parameters for the configured DMIs/STIs (done by PDP)
• read all values
A DMV can change qualifier status at runtime if:

• if the maximum value specified for a DMI input is exceeded (qualifier 0V = 1)
• if any digit of a BCD coded DMI input has an invalid code > 9 ( Qualifier IV = 1)
2.3.4 Digital Measured Value Processing with 560MIO80
2-24 1KGT 150 589 V000 1 ABB AG

2.4 Bit-string Input Value Processing
The RTU560 can handle bit patterns to read them and convert them into a bit-string input
value (BSI):
• 8 bit bit-string (BSI8)

• 16 bit bit-string (BSI16)
The maximum length of a bit-string is the word of 16 bit (= one 23BE23/23BE40 board).
Double word values are not supported.
If an eight bit pattern is selected the residual 8 bit of the 23BE23/23BE40 board can be
used for another digital value, for pulse counter values or indications.
The data acquisition functions for digital measured values processed by the RTU560 can
be split into functions handled by:
• IOC of the binary input board 23BE23/23BE40

23BE23/23BE40 functions:

- Consistency check
- Store events in FIFO with time stamp
CMU - PDP:
ABB AG 1KGT 150 589 V000 1 2-25

The IOC of the 23BE23/23BE40 board supports the bit-string input (BSI) functions. The
parameter of each function and each BSI is loaded from PDP at start up or if the board
must be initialized during runtime.
The 23BE23/23BE40 reads all 16 inputs periodically every millisecond regardless of the
that millisecond.
If the data point is Blocked the status is set to blocked and no changes are reported from
the PDP.
Parameter: Blocked (BSI – PDP Parameters)
Digital filter
Parameter: Digital filter (BSI – PDP Parameters)
Consistency check
A BSI is a bit pattern of 8 or 16 bit length. The value is valid only if all binary channels of
the BSI are valid and stable for at least the consistency check time. This is given if no
input changed for the parameterized consistency check time. Any change on an input
channel re-triggers the settling time.
The minimum settling time is defined by the PDP parameter Consistency check time. The
minimum consistency time is 100 milliseconds.
Parameter: Consistency check time (BSI – PDP Parameters)
FIFO storage of 23BE23/23BE40
If a BSI has changed and is stable for at least the consistency time, it is stored into the
FIFO and transmitted to the PDP.
2-26 1KGT 150 589 V000 1 ABB AG


If a board is set out of service the configured digital measured values are to the invalid
state. All BSI are set faulty. The RTU560 transmits the BSI values of that board to the
NCC with the corresponding message and the qualifier IV = 1.

When this happens the following sequence recovers the BSI’s:

• load all parameters for the configured BSI’s (done by PDP)
• read all values
A BSI can change qualifier status at runtime if:
2.4.4 Bit-string Input Processing with 560MIO80
ABB AG 1KGT 150 589 V000 1 2-27

2.5 Integrated Total Processing
2.5.1 Integrated Total Value Types
There are two types of integrated total values (ITI) defined in the RTU560:
• End of period reading counters (EPR)

• Intermediate reading counters (IR)
Both types have only one source and the IR is only an intermediate value of the
corresponding EPR. That means there is one ITI which is transmitted periodically in fixed
periods.
Integrated Total Values with reset to zero at end of period

Counts The IR reading cycle must be 1/n of end of period time
e.g.: if period = 60 minutes and n = 5 the IR cycle = 12 min
Period Period Period Period time
Intermediate End of IR End of End of End of

reading Period reading Period Period Period
cycle reading reading reading reading
Figure 2-15: Integrated Total Values Definition for EPR and IR
Integrated Total Value presentation
Although the internal value representation is 32 bit signed integer the RTU560 supports
on its local inputs positive ITI values only. This allows ITI values between:
• 0 .. and...+ 2 147 483 647
2-28 1KGT 150 589 V000 1 ABB AG

The process data acquisition functions for ITIs processed by the RTU560 can be split into
functions handled by:
• IOC of the binary input board 23BE23

23BE23 functions:

- Increment integration register
- Freeze integration register into relocation register
CMU - PDP:
- Freeze and read ITIs periodically

The IOC of the 23BE23/23BE40 supports the integrated total functions. The parameter of
each function is loaded from PDP at start up or if it must be initialized. Parameters can be
set individually per input.
The 23BE23/23BE40 reads all 16 inputs each millisecond. If the channel is configured for
integrated total a signal change of 0->1 is accepted after digital filtering to be a pulse
count and increments the pulse counter register.
Whenever the PDP sent a broadcast command to freeze counter values, the
23BE23/23BE40 reads the actual integration register and stores the contents into the
relocation register. The PDP receives the frozen ITI value from the 23BE23/23BE40.
Digital filter
Parameter: Digital filter (ITI – PDP Parameters)
ABB AG 1KGT 150 589 V000 1 2-29

Integrated Total Frequency
The 23BE23/23BE40 can read ITI counter increments with a frequency of max. 120 Hz.
The default digital filter is 10 ms (necessary when normal relay contacts are used). The
ratio for the 0 and 1 state should be 1:1.
Freeze ITI value
EPR or IR readings are forced by the PDP periodically. The PDP sends a broadcast
command to all I/O boards: "freeze ITI registers".
Each 23BE23/23BE40 on which ITI's are configured stores the actual integrated total
register contents into a relocation register. This is done within the normal signal
processing, the integrated total register continues counting. The frozen values are
transmitted afterwards to the PDP.
Reading ITI counter values and update ITI status
Reading is done:
• for each configured IR cycle

• for each configured EPR period
The frozen ITI values are read from all ITIs which are configured for the actual period. It
is not necessary to have all ITIs in the same EPR periods or IR cycles.
There are some qualifier information, which inform the NCC about the quality of the ITI.
These qualifiers are updated at each ITI reading.
2-30 1KGT 150 589 V000 1 ABB AG

EPR / IR parameters
With the PDP parameter Acquisition of end of period reading ITI the transmission of EPR
readings can be switched off or the EPR period in minutes is specified. The parameter
End of period wrap around counter specifies that the ITI value is not reset after an EPR
reading.
Parameter: Acquisition of end of period reading ITI (ITI - PDP parameters)

End of period wrap around counter (ITI - PDP parameters)
With the PDP parameter Acquisition of intermediate reading ITI the transmission of IR
readings can be switched of or the IR period is specified. With Unit of IR cycle it is
possible to decide whether IR period is defined in second or minute cycles.
Parameter: Acquisition of intermediate reading ITI (ITI - PDP parameters)

Unit of IR cycle (ITI - PDP parameters)
CA = Counter was adjusted since last reading
This flag is set if the counter is:
• restarted due to RTU560 restart

• the time changed during the period / cycle
(new time synchronization)
If the RTU560 system time has changed due to a new received time base (hard
synchronization) the CA qualifier is set. CA is set if the time changed more than 5
seconds from the old system time.
The flag is set in the first telegram of an intermediate value (IR) and in the first telegram
of an end of period value (EPR). If the EPR telegram comes first the qualifier is not set in
the following IR telegram.
ABB AG 1KGT 150 589 V000 1 2-31

IV = ITI is invalid
This flag is set if the ITI value is not valid because the PDP could not receive the value
from the 23BE23/23BE40 board.
CS
RTU560
EPR ITI queue
EPR period and
IR cycle IR
values
freeze
PCV register
23BE21
relocation Integration
register Register
Puls from Metering Device
Figure 2-16: Reading ITI within the RTU560
IT = Invalid time
This flag is set in the time information element of the ITI telegram until the RTU560 has a
valid system time and is synchronized after start up.
2-32 1KGT 150 589 V000 1 ABB AG


If a board is set out of service the configured ITI´s qualifiers are set to invalid due to
board failure. The RTU560 transmits all ITI messages of that board to the NCC with an
ITI message and the qualifier IV = 1.

When this happens the following sequence recovers the pulse counter values:

• load all parameters for the configured channels (done by PDP part of CMU)
• read all values and update status
• Reset qualifiers IV for affected ITI´s
An integrated total value can change qualifier status at runtime if:
2.5.6 Integrated Total Processing with 560MIO80
with the same features as the 23BE23. The inputs E1 and E9 can be used for integrated
total information (ITI) with a frequency up to 8 kHz.
ABB AG 1KGT 150 589 V000 1 2-33

2.6 Direct Interfacing of Current and Voltage Transformer
The Current/Voltage Transformer Interface 560CVT01 is used for monitoring input

signals from three independent phases with 3 or 4 wire connections. The following
measurements are available:
Measurement Measuring Path(s)

Voltage 1-N, 2-N, 3-N, 1-2, 2-3, 3-1
Current 1, 2, 3, N
Active Power 1, 2, 3, Σ
Reactive Power Σ
Apparent Power Σ
Power Factor 1, 2, 3, Σ
Frequency Phase 1 only
Accumulated values are stored in energy registers of the 560CVT01 as long integer
values. On power up these values are reset to zero. The accumulated values are
cyclically transmitted to the RTU560:
• Active Energy 3-phase
• Reactive Energy 3-phase
• Reactive Energy (Ind.) 3-phase
• Reactive Energy (Cap.) 3-phase
The 560CVT01 provides a measure of the distortion (THD), in each phase voltage and
current waveform, as a percentage deviation from pure 50 Hz or 60 Hz sine waves by
Fast Fourier Transform algorithm (FFT):
• U1, U2, U3 % THD
• I1, I2, I3 % THD
The measurements (AMI) are transmitted by the subdevice communication interface,
using the parameter ‘rated value’ and ‘range’, by converting these values into a
normalized representation.
All measurements are representing the secondary output of the transformer.
Parameter
Secondary rated voltage (560CVT01 - parameter)
Voltage measurement range (560CVT01 - parameter)
Secondary rated current (560CVT01 - parameter)
Current measurement range (560CVT01 - parameter)
2-34 1KGT 150 589 V000 1 ABB AG

For example:
Secondary rated current = 5 Ampere (Value range: 1 … 5 Ampere)
Current measurement range = 0.5 (Value range: 0.01 … 1.20)
►100 % = 2.5 Ampere (secondary)
Example 120 V Value

Range = 1,0
Lower Limit - 120 Volt - 100 %
0 Volt 0
Upper Limit + 120 Volt + 100 %
The Frequency is detected at the phase 1 voltage signal and converted to a normalized
representation, using the parameter ‘nominal frequency’:
Parameter:
Nominal frequency (560CVT01 - parameter)
Frequency Example 50 Hz Value

Nominal frequency
‚Nominal frequency’ * 90 % 45,0 Hz - 100 %
‚Nominal frequency’ 50,0 Hz 0
‚Nominal frequency’ * 110 % 55,0 Hz + 100 %
The Power Factor (Phase 1, 2, 3 and Σ) is also a normalized value:

Power factor Value
- 1,000 - 100 %
0 0
+ 1,000 + 100 %
The Total Harmonic Distortion THD (V and C, Phase 1, 2 and 3) is transmitted in

percentage as a normalized value:
THD Value
- - 100 %
0 0
100,0 % + 100 %
All Energy Values are cyclicly requested by the RTU560 subdevice communication
interface and transmitted as Integrated Total Information (ITI):
Parameter:
IR / EPR cycle time (560CVT01 - parameter)
Wrap around, Pulse quantity (560CVT01 - parameter)
ABB AG 1KGT 150 589 V000 1 2-35

3 SCADA Command Direction
The following SCADA functions are described for the I/O board 23BA20/23BA40 of
RTU560 A/C. If not otherwise noticed, they are also available within 560MIO80 of the
RTU560E.
3.1 Output Command Types
The RTU560 knows following output command types:
• Command Output
- Single Command Output (SCO)
- Double Command Output (DCO)

• Regulation Step Command Output (RCO)
• Setpoint Command Output
- Analog Setpoint Command Output (ASO)
- Digital Setpoint Command Output (DSO)

• Bit-string Output Command (BSO)
3.2 Function Distribution
Within RTU 560 the output boards 23BA20/23BA40, 23AA20 and if requested the
command supervision board 23BA22 are responsible to do the command outputs. They
are coordinated and monitored by the PDP.
The IOC of the output boards are responsible to switch the output relays or to set the
analog output value. They supervise and monitor also the hardware. Which kind of output
is configured and wired on which channel is loaded by the PDP to the boards during
initialization in a similar form as for the input boards.
Commands (SCO, DCO), Regulation step commands (RCO) and Setpoint Commands
(ASO, DSO) may be executed in one or two step mode (Select before operate
sequence). Bit-string- Outputs (BSOxx) are handled by the RTU560 in a direct command
sequence only.
ABB AG 1KGT 150 589 V000 1 3-1

SCADA Command Direction Remote Terminal Unit RTU560
3.3 Object Command Output
3.3.1 Object Command Output with 23BA20/23BA40
Object command outputs (SCO or DCO):
• can be wired for one, 1.5 and two pole switching

• allows additional (1 out of n)-check (command supervision 23BA22)
1.5 pole and two pole switching (not 23BA40)
• allows two step commands (Select before operate SBO sequence)
• allows command termination by a response indication
• allows persistent output
3.3.2 Single Object Command Output
A single command has only one output relay. It can be configured pulse ON or OFF
command or as persistent output.
Parameter: Command type (SCO – PDP Parameters)
Single object commands can be wired with one relay contact per command
(23BA20/23BA40: 1 pole) or with two relay contacts per command (23BA20/23BA40: 2
pole).
Single Object commands are pulse outputs whereas the pulse duration is specified by the
parameter Command pulse length per command. Only the configured direction is used
for pulse output. The not configured direction is ignored. One relay is occupied within a
23BA20/23BA40 output board.
Parameter: Command pulse length (SCO – PDP Parameters)
K1
ON or OFF output
23BA20 pulse
Interposing Relays
Figure 3-1: Single Command definition: pulse output
3-2 1KGT 150 589 V000 1 ABB AG

Remote Terminal Unit RTU560 SCADA Command Direction
Single object commands are configurable as persistent output. In persistent mode an ON

command switches the relay persistent on and the OFF command switches the relay to
off.
K1
23BA20 ON-Command OFF-Command
Interposing Relays
Figure 3-2: Single Command definition: persistent output
3.3.3 Double Object Command Output
A double command has two independent output relays:
• one relay for ON direction

• one relay for OFF direction
Double object commands can be wired with one relay contact per command
(23BA20/23BA40: 1 pole) or with two relay contacts per command (23BA20/23BA40: 2
pole).
Double Object commands can be pulse outputs whereas the pulse duration is specified
by the parameter Command pulse length per command. Only one channel ON or OFF
can be active at the same time. The two relays occupie two consecutive bits within a
23BA20 output board. The ON-relay is normally on the odd channel (1, 3, 5 …) and the
OFF-relay on the even channel (2, 4, 6 …).
Parameter: Command pulse length (DCO – PDP Parameters)
k1 ON
Output
pulse
k2 OFF
23BA20 Output
Interposing Relays pulse
Figure 3-3: Double Command definition: pulse output
The definition of the bit position for ON and OFF can be changed for the whole
configuration. If changed, this definition is also valid for DPI and RCO commands.
Parameter: Change ON and OFF connection point (RTU Parameters)
ABB AG 1KGT 150 589 V000 1 3-3

3.3.4 Output Procedures
The following options are available for single and double object commands.
One Step Command / Select Before Operate Procedure
Commands for objects can be given either direct in one step or for higher security
requests in the “select before operate“ procedure. The SBO mode decreases the residual
error probability in command direction essentially.
If the parameter Select before operate only is selected always a select before operate
sequence is necessary.
Parameter: Select before operate only (SCO/DCO – PDP Parameters)
If RTU 560 receives a SELECT command it checks whether the object is available and if
no other object is already reserved. If the check is O.K. it acknowledges the reservation
with a positive confirmation. The reservation is valid for approx. 20 seconds. Within that
time window either the corresponding EXECUTE Command or a DESELECT command
should be received. If not, the RTU 560 clears the reservation.
If an EXECUTE command is received within time the object number is compared with the
number of the reserved object. If both object numbers are the same, the command is
executed. The command is finished, when the RTU 560 transmits the activation
termination for that command.
The SBO procedure depends on the protocol of the communication line.
While a command object is selected, no other command objects of the same type can be
selected (Command types are –Object Commands, -Regulation Commands, -Setpoint
Commands). If another command object of the same type will be selected, the previous
selection will be cancelled.
3-4 1KGT 150 589 V000 1 ABB AG

Termination of Command output by Response Indication
The pulse duration of an object command can be limited to the runtime of the switching
device (e.g. isolator). The run time end is recognized by the new position indication. To
prevent that the command is stopped before the new position is settled, a Command
release delay time can be specified.
The use of a response indication is specified by the parameters of the Response

indication for each object command. The response delay time can be specified by the
parameter Command release delay time. The default is 200 ms.
Parameter: Response indication (SCO/DCO – PDP Parameters)

Parameter: Command release delay time (SCO/DCO – PDP Parameters)
RTU560
Command
23BA20 DCO
Switch Gear UB CS
Response
23BE21 DPI
Pulse length without response

Pulse length
with response
Command
output
ON 1
0
Response message
OFF 1
0
Command release
DPI delay time
Message
Figure 3-4: Response Indication procedure
The response indication is a SPI or DPI message. Therefore only the end positions ( ON /
OFF) can stop the command. It is not required that the reported indication state and the
command direction ( ON / OFF ) do match.
A new command from NCC is accepted only when the command is switched off, that
means after the response delay time and the final termination of the command with
ACTTERM to NCC.
ABB AG 1KGT 150 589 V000 1 3-5

Object Command output without supervision
The 23BA20 board is doing the final output by switching the output relay(s). The
23BA20/23BA40 monitors and checks an output by:
• reading back the output bit pattern from the relay coils driver
• supervision of the 24 V DC which switches the output relays
• monitoring the output pulse time
• indicating the command state by LEDs
Figure 3-5 shows the principle wiring for object commands in one pole technique.
In two pole technique two relays per command direction are needed and will be switched
by the 23BA20/23BA40 board (e.g. k1 and k9), see Figure 3-6. In that form object
commands and regulation step commands can be mixed within a board.
k1 - k16 = output relays
23BA20
k11
k12
k15
k13
k14
k16
k10
k5
k6
k9
k3
k4
k7
k8
k1
k2
R2
R1
Interposing Relays
UD
ON ON ON ON ON ON ON ON
OFF OFF OFF OFF OFF OFF OFF OFF
Ch 1 Ch 2 Ch 3 Ch 4 Ch 5 Ch 6 Ch 7 Ch 8
SCO, DCO Commands
Figure 3-5: Process commands without supervision (1-pole)
3-6 1KGT 150 589 V000 1 ABB AG

k1 - k16 = output relays
23BA20
k11
k12
k15
k13
k14
k16
k10
k5
k6
k9
k3
k4
k7
k8
k1
k2
R2
R1
UD
Interposing Relays
OFF OFF OFF OFF

Ch 1 Ch 2 Ch 3 Ch 4
SCO, DCO Commands
Figure 3-6: Process command without supervision (2-pole)
The coordination of the output board is done by the PDP. The interaction is shown in
Figure 3-7. If a process command is received to switch the selected output channel, the
assigned 23BA20/23BA40 is requested to do the output.
Procedure:
• Check if no other output is active etc.

• Switch selected output relay
• Start output pulse timer
• Transmit a positive acknowledge (output active) to the PDP
• Switch off output relay when the pulse time has elapsed
• Transmit “output deactivated“ to PDP
The PDP monitors the output commands. If it does not receive the acknowledge
information within time, it will stop the output by forcing the 23BA20/23BA40 to stop. The
23BA20/23BA40 acknowledges output active will response the command with Activation
Confirmation to NCC.
ABB AG 1KGT 150 589 V000 1 3-7

PDP 23BA20 Comment
Receive, RTU 560 receives output command from CS.

check and It checks command on plausibility and no output
prepare active
output
command If o.k. PDP transmits command to related
23BA20 output board with pulse time parameter
Check
output cmd . 23BA20 checks received com-
switch mand and activates output
output relay
start timer channel if o.k.
23BA20 starts timer with
output pulse received pulse time length
set flag time and indicates output active
output active to PDP.
Pulse time
elapsed
swicth off
output relay 23BA20 switch off output channel when pulse time
elapsed.
23BA20 indicates output deactivated to PDP
reset flag PDP receives output deactivated and resets
output active
output active. A new command may receive.
Figure 3-7: Interaction PDP - 23BA20/23BA40, command output without command

supervision
Command output with supervision
To increase the security that only one interposing relay is switched at a time when a
command is given, object commands can be expanded with the (1 out of n)-check
function. Figure 3-8 and Figure 3-9 show the principle wiring between the 23BA20 board
and the additional required 23BA22 command supervision board.
Command output with supervision is not available with 560MIO80 and 23BA40.
3-8 1KGT 150 589 V000 1 ABB AG

- UD +
UD = Process Voltage to switch Interposing Relays
GO
(1 out of n)-check
*) = 1.5 pole is also possible if R1 or R2 is wired only.
check circuit
23BA22 the other route may be used for other Commands
P1 / P2
P2- P2+ P1- P1 +

*)
R2
R1
k1
to other 23BA20 Boards k2
with same Relay Type connected k3
k4
k5
Object Interposing Relays
k6
k7
k8
k9
k10
k11
k12
k13
k14
k15
k16
23BA20
23BA20 Relay
Test Period
Switch over from
"TEST" to "SWITCH"
Output Pulse
output pulse
given by "GO" Relay
1 out of n
test period (with positive result)
Figure 3-8: Object command output with supervision (1,5-pole)
ABB AG 1KGT 150 589 V000 1 3-9

- UD +
UD = Process Voltage to switch Interposing Relays
(1 out of n)-check GO
*) = only 2 pole Object Commands possible if wired
check circuit for (1 out of n)-check
P1 / P2 23BA22
P2- P2+ P1- P1 +
*) R2
R1
k1
to other 23BA20 Boards k2
with same Relay Type connected k3
Object Interposing Relays k4

k5
k6
k7
k8
k9
k10
k11
k12
k13
k14
k15
k16
23BA20
23BA20 Relay
Test Period
Switch over from
"TEST" to "SWITCH"
Output Pulse
output pulse
given by "GO" Relay
1 out of n
test period (with positive result)
Figure 3-9: Object command output with supervision (2-pole)
3-10 1KGT 150 589 V000 1 ABB AG

PDP 23BA20 23BA22 Comment

Receive, Command is checked on plausibility
check and and no other output active.
prepare Related 23BA20 output channel is
output
command switched on by transmitting command
to 23BA20 board with a longer pulse
length than defined for the Command
Check
output cmnd.
switch
output relay
set flag
output active
start test PDP indicates Output
circuit "n" Activeand starts
23BA22 with pulse
Run 1 out of n
check for time parameter.
circuit "n" 23BA22 runs
switch over to (1 out of n)-check
output position
and start output
by "GO" relay If Positive:
start output output and
timer timer started
set flag Output Pulse

output Time
command
running
Pulse time
elapsed
switch off
"GO" relay
23BA22 switch off
GO relay if pulse time
reset flag elapsed
output It indicates Output
running
prepare stop Deactivatedto UB
for 23BA20
relay
PDP transmits Output Stop
to 23BA20 board
switch off 23BA20 will switch off
output relay related Output Channel
reset timer 23BA20 indicates Output
Deactivatedto UB
PDP receives Output
reset flag Deactivatedand resets
output active
output active.
A new command may receive
Figure 3-10: Interaction PDP - 23BA20/23BA22, with command supervision
ABB AG 1KGT 150 589 V000 1 3-11

The coordination between the two output boards is done by the PDP. The interaction
between the three boards is shown in Figure 3-10.When a process command is received
the 23BA20 output relay is switched first with a pulse time which is longer than the
configured output pulse duration for that channel. After the 23BA20 has acknowledged
that the output relay is switched on, the 23BA22 is started to check the output circuit and
if positive to do the final output with the configured time for that channel.
The 23BA22 allows to check two different output circuits with different nominal
resistances. But only one channel can be active at the same time (P1 or P2). If the
23BA22 receives a request to test and switch a command on P1 or P2 the following
sequence is started:
• Check that no other output is active etc.

• Select P1 or P2 for checking
• Start to measure the resistance in the switched output channel (interposing relay)
• Compare the measured resistance against the parameterized upper and lower
limits
• Abort all activities and transmit a negative acknowledge if the resistance is out of
limits
• Switch the auxiliary relays from “TEST“ to “SWITCH“ position if the resistance
check is O.K.
• Start the output pulse by switching the “GO“ relays which feed the process voltage
to the selected interposing relay
• Start output pulse timer
• Transmit a positive acknowledge (command running) to PDP
• Switch off “GO“ relay when the pulse time elapsed
• Switch back to “TEST“ position
• Transmit “command stopped“ to PDP
The PDP will then stop the 23BA20 output by a stop command. The PDP part of the CPU
monitors the output commands. If it does not receive the acknowledge information within
time it will stop the output by forcing the 23BA22 to reset and the 23BA20 to stop output.
The assignment between 23BA22 and 23BA20 and the upper and lower resistance limits
has to be parameterized for each channel on the command supervision board 23BA22.
Two command supervision channels CSC (P1 / P2) can be defined on each 23BA22
board. On the 23BA20 board can be selected which command supervision channel
monitors the board. For 1.5 pole 23BA20 two channels can be selected (relays 1-8 and
relays 9-16) .The command supervision is valid for all SCO and DCO commands on this
board.
It must be regarded that channels connected to the same route (R1 / R2) must have the
same supervision channel CSC n.
Parameter: Check circuit number (CSC – General Parameters)

Low limit resistance (CSC – General Parameters)
High limit resistance (CSC – General Parameters)
3-12 1KGT 150 589 V000 1 ABB AG

23BA22 LOCAL mode
The 23BA22 board has a push-button on the front panel which allows to inhibit any active
output. This button is marked with LOC and a LED indicates if LOCAL is active or not. To
switch from remote to local and vice versa the push-button must be pressed twice within
5 seconds. The LED LOC flashes -after the push-button is pressed once- for five
seconds.
As long as LOCAL mode is active, the 23BA22 discards any command and returns
negative acknowledgements. The position of the LOCAL/REMOTE switch is sent to the
NCC with system events # 64 to #95 (see also chapter 16).
If the LOC push button is pressed twice again, the 23BA22 switches back to remote
mode and will accept and handle commands in the normal way.
3.3.5 Object Command Output with 560MIO80
The Multi In-/Output 560MIO80 of the RTU560E has eight binary outputs. The following
types of Command Output are supported by the 560MIO80:
• Single Command Output / Double Command Output
• Persistent Output
• One ore two step command (Select Before Operate Sequence)
• Termination by Response Indication
• One pole and two pole switching
1.5 pole switching and (1 out of n)-check is not supported by 560MIO80.
ABB AG 1KGT 150 589 V000 1 3-13

3.4 Regulation Step Command Output
Regulation step command output (RCO)
• can be wired for one and two pole switching 23BA20/23BA40 and 560MIO80
• allows one and two step commands (select before operate sequence)
• cannot be wired with command supervision
• cannot be terminated by a response indication
The object command pulse length is described by the parameter PULSE LENGTH. The
pulse duration for HIGHER and LOWER is the same.
Parameter: Command pulse length (RCO – PDP Parameters)
Re-trigger of regulations commands
The output pulse duration of a regulation command can be expanded if the same
command is received within the output pulse time and can be sent to the output board
before the time elapsed. 23BA20/23BA40/560MIO80 starts the timer again.
An output pulse can also be shortened by a new command with DEACTIVATION flag. If a
DEACTIVATION command is received the running regulation command is stopped
immediately.
Option Start Retrigger Retrigger Retrigger Stop Pulse duration

RCO RCO RCO RCO RCO RCO without stop
SEL ACT ACT ACT ACT DEACT
Command output relay
Nominal
pulse duration
Figure 3-11: Re-trigger / stop of a regulation command
The definition of the bit position for HIGHER and LOWER can be changed for the whole
configuration. If changed, this definition is also valid for DPI and DCO commands.
Parameter: Change ON and OFF connection point (RTU

Parameters)
3-14 1KGT 150 589 V000 1 ABB AG

3.5 Setpoint Command Output
A set point command is specified by an analog or digital set point value output. The
output can be done with or without strobe. For a strobe output the value is valid for the
receiving unit during the additional strobe pulse output. One or two step commands is
possible. The set point command types are:
• analog output value (ASO)

Analog output channel on a 23AA20 board
(current or voltage output)
• digital output value (DSO)
Digital output on 23BA20/23BA40 board
3.5.1 Analog Setpoint Command Output
3.5.1.1 Analog Setpoint Command Output with 23AA20
The analog set point command output (ASO) can be done in two ways, with strobe or
without strobe. The strobe output allows to trigger the concerned unit when a new value
is received. When this is not requested the set point command can be done without
strobe.
Bipolar, Unipolare and Live Zero conversion
The analog output value is converted to an analog output signal by the 23AA20 board.
The Output signal type allows to specify unipolar output signals. That means a negative
ASO value is set to zero.
Output signals with live zero presentation (standard = 4..20 mA) are transformed by the
PDP. The conversion is done in the form that:
• 0% of the normalized ASO value becomes 20 % of the output signal range

(Standard: 4 mA)
• 100 % of the normalized ASO value becomes 100 % of the input signal range
(Standard: 20 mA).
ABB AG 1KGT 150 589 V000 1 3-15

100 %
0%
4 mA (0%) 20 mA (100%)
Output Value
Figure 3-12: Live Zero Output Conversion by a 23AA20 board

The configuration parameter Output signal type specifies if the output is a bipolar, a
unipolar or a live zero signal. The configuration parameter Output signal range specifies
the hardware setting of the 23AA20 board.
Parameter: Output signal range (ASO – PDP Parameters)

Output signal type (ASO – PDP Parameters)
Scaling
The PDP converts the value of a normalized ASO. The configuration parameter
Conversion factor specifies the percentage of the maximum output signal that is defined
as 100 % of the normalized value.
Parameter: Conversion factor (ASO – PDP Parameter)
Normalized ASO value
[digits]
+ 100 %
e.g. conv. factor = 75 %
-20 -15 -10 -5 5 10 15 20 [e.g. mA]

-100 -75 -50 -25 25 50 75 100 [% ]
Output signal
- 100 %
Figure 3-13: Analog Value Conversion ASO
3-16 1KGT 150 589 V000 1 ABB AG

Analog Setpoint command without strobe
The analog output stays stable until a new ASO is received.
Analog Setpoint command with strobe
For analog setpoints with strobe, the corresponding Strobe output channel (SOC) should
be configured to any output channel of a 23BA20/23BA40 board. The strobe Pulse length
is configurable. The default value is 500 milliseconds. The ASO must be configured to an
analog output board 23AA20.
Parameter: Pulse length (SOC – PDP Parameters)

Strobe (SOC) (ASO – PDP Parameters)
The PDP coordinates the output of the analog output value and the strobe pulse. There is
a delay of approx. 50 ms between the output of the analog value and the strobe. This
delay allows the value to become stable. The analog output stays stable until a new ASO
is received.
Figure 3-14: Set Point Command for Analog Output
3.5.1.2 Analog Setpoint Command Output with 560MIO80
There is no analog output available on the Multi In-/Output 560MIO80 of RTU560E.
ABB AG 1KGT 150 589 V000 1 3-17

3.5.2 Digital Setpoint Command Output
3.5.2.1 Digital Setpoint Command Output with 23BA20/23BA40
A digital setpoint output (DSO) is an output of a normalized value on a 23BA20/23BA40.

The following types are possible:
• Digital Setpoint Output 8 bit (DSO8)

• Digital Setpoint Output 16 bit (DSO16)
The RTU knows conversions for:
• Binary data (BIN)

• Binary coded decimals (BCD)
• Gray code (GRAY)

(= one 23BA20/23BA40 board). Double word values are not supported.
Digital Setpoint value presentation
Each type is converted by the PDP.
3-18 1KGT 150 589 V000 1 ABB AG

16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 23BA20 Output Channel
Conversion by PDP
(a)
(b) S 15 bit + sign binary data
(c) 8 bit unsigned binary data
(d) S 7 bit + sign binary data
(e) 0..9 0..9 0..9 0..9 4 Decade BCD unsigned
(f) S 0..7 0..9 0..9 0..9 4 Decade BCD signed
(g) 0..9 0..9 2 Decade BCD unsigned
(h) S 0..7 0..9 2 Decade BCD signed
(i) 16 bit gray code

(j)
(k) 8 bit gray code
(l) S 7 bit signed gray code
S = Sign bit / Sign position
Figure 3-15: Digital Setpoint Value presentation
Scaling and format conversion
A digital setpoint output is converted from a normalized value (+/- 100%) to a bit pattern
output on 23BA20/23BA40 by the PDP. The PDP parameter DSO value presentation and
Output signal type specifies which DSO type is connected to the 23BA20/23BA40 board.
The PDP receives the bit pattern of the DMV. The PDP parameter Maximum value
specifies the binary value output for 100 % of the DSO value.
Parameter: DSO Value presentation (DSO – PDP Parameters)

Input signal type (DSO – PDP Parameters)
Maximum value (DSO – PDP Parameters)
ABB AG 1KGT 150 589 V000 1 3-19

Digital Setpoint command without strobe
The pulse length of a digital setpoint without strobe signal is fixed to 500 milliseconds
Digital Setpoint command with strobe
For digital setpoints with strobe, the corresponding Strobe output channel (SOC) should
be configured to any output channel of a 23BA20/23BA40 board. The Pulse length of the
strobe signal is configurable. The default value is 500 milliseconds. The DSO must be
configured to a binary output board 23BA20/23BA40. SOC and DSO8 can be located on
the same 23BA20/23BA40.
Parameter: Pulse length (SOC – PDP Parameters)

Strobe (SOC) (ASO – PDP Parameters)
The PDP coordinates the output of the digital output value and the strobe pulse. There is
a delay of approx. 50 ms between the output of the digital value and the strobe. This
delay allows the value to become stable. The digital outputs are switched off at the end.
Figure 3-16: Set Point Command for Digital Output
3.5.2.2 Digital Setpoint Command Output with 560MIO80
The Multi In-/Output device 560MIO80 of the RTU560E hat 8 binary output channels.
That is way only the Digital Setpoint Output 8 bit (DSO8 without strobe) is supported.
3-20 1KGT 150 589 V000 1 ABB AG

3.6 Bit-string Output
3.6.1 Bit-string Output with 23BA20/23BA40
A bit-string output (BSO) is a persistent output on a 23BA20/23BA40. The following types

are possible:
• Bit-string Output 1 bit (BSO1)

Bit-string output values are transparent mapped 23BA20/23BA40 output channels. The
output value is switched on the output board and stays stable until a new value is
received from NCC for this output channel.

(= one 23BA20/23BA40 board). Double word values are not supported.
Note for 23BA40: The number of simultaneous active relays may not exceed 2
(At heavy loads and higher temperature)
3.6.2 Bit-string Output with 560MIO80
The Multi In-/Output device 560MIO80 of the RTU560E hat 8 binary output channels. So
the 560MIO80 supports 1, 2 or 8 bit Bit-string Output (BSO).
ABB AG 1KGT 150 589 V000 1 3-21

3.7 Error Handling
Output Board Failure
An output board can be set “out of service“:

If an output board is set out of service the configured output channels are set faulty due
to board failure in the data base. The RTU560 indicates that to the NCC with diagnostic
message.
An output board can be set in service again during runtime:

If this happens the following sequence recovers the output channels:
• normalize the output board

• load all parameters for configured channels by the PDP
• clear faulty state in data base and update NCC
3-22 1KGT 150 589 V000 1 ABB AG

4 Redundancy
4.1 Overview
To keep access to a remote station can be very important for stations with critical
responsibilities in an energy transportation grid. Mainly it is capability to keep access to
station and to the important process units.
The RTU560 takes care of this requirement with a graceful degradation concept.
Especially for the central part, the CMU boards in the RTU560. The RTU560A / C
concept is designed to support redundant functionality.
The redundancy is available in steps:
• Redundant communication capabilities for RTU560A / C with

- Redundant communication lines
- Multi host connections
- Modem pool connections
• Redundant power supplies in the communication sub-rack 560CSR01 for

RTU560A
• Redundant CMU boards in the RTU560A / C
The hardware design of the RTU560 is state-of-the-art for industrial electronic products
with respect to the environment conditions for outdoor stations and EMC conditions in
electrical substations. The RTU560 modules have a high availability, proven by a low
return rate of defective boards over the past.
4.2 RTU560A/C redundant CMU concept
The main concept is to have one or more pairs of CMU boards for those communications
lines and functions, which are critical for the operation of the station. In case of an error
condition the RTU560 will switchover to the standby CMU and this CMU starts to take
over the tasks after a cold start.
One pair of communication units (CMU) of an RTU560 configuration can be defined as a

redundant communication set. In case of an error of an active CMU, the system will
switch over to the redundant stand-by CMU, which will continue processing after
performing a cold-start. Other redundant sets of communication units in the configuration
will not be affected in operation.
This new redundancy concept of the ABB AG firmware is different to former

releases of the RTU560, and will result in a better availability of the system.
For some function modules like archives and PLC it is not useful to have a redundancy
because of loss of information for the archive or loss of process control for the PLC.
These modules are only installed once in the RTU560A system and so called non
redundant modules.
ABB AG 1KGT 150 589 V000 1 4-1

Redundancy Remote Terminal Unit RTU560
The RTU560A (and RTU560C) CMU modules can be defined in three types:
• the active CMU (A), which is the active running device

• the standby CMU (B), which monitors the active CMU and is
prepared to take over as active device
• the non redundant CMU (C), which continuous operation all the time
To supervise the status of the RTU560A / C under this conditions it is necessary, that the
standby CMU and the active CMU monitors each other to be in the situation to take over
the other state or not. When for example a standby CMU fails, it is not allowed to switch
over, and it is necessary to inform the host about the failure in the standby CMU by the
active one. On the other side the standby CMU must detect, when the active CMU fails
without any alarm or warning message to take over the active state.
Figure 4-1: RTU560A configuration with redundant CMU modules
4-2 1KGT 150 589 V000 1 ABB AG

Remote Terminal Unit RTU560 Redundancy
The above picture shows an example of a redundant RTU560A. The redundant CMU’s A
and B may have the following configuration:
• NCC1 and NCC2 are communicating via a serial line protocol (e.g. DNP 3.0)
• The IO boards are organized in two PDP groups and connected to the CMU 1 of
each group.
• some IEDs (e.g. the protection relays for the main transformers) are of high
importance and therefore connected to the redundant CMU A2 and B2
The non redundant CMU’s may have the tasks:
• a third NCC
• PLC
• Process event / Disturbance file / Load profile archive
• IEDs (e.g. additional protection relays)
Master / Slave concept
In case of an RTU560A / C configuration with more then one CMU board it is necessary
to define a Time-Administration Master within the RTU560. All other configured CMU
modules are in that definition Time-Slave. RTUtil560 is used to define Master and Slave
CMUs.
The Time-Administration-Master is responsible for the time administration of the system,

and has to synchronize all Slave-CMU’s.
In addition, every RTU560 system has a System-Administration-Master for supervising

the whole system. This master-functionality is defined by the communication boards
during start-up automatically, by choosing the (running) communication board with the
lowest rack- and slot-address as master.
Master / Slave concept with redundant CMU modules
A redundant configuration has also one Time-Administration-Master and one System-

Administration-Master.
The Time-Administration-Master is defined by the user during the engineering process.

The Time-Administration-Master can run on a redundant pair of CMU’s or on a non-
redundant CMU (see also chapter 4.4.5).
The System-Administration-Master is defined by the system automatically during start-up,

by using the communication unit with the lowest rack/slot-address as a master. In case of
a failure of this master, the system will automatically switch to another master.
ABB AG 1KGT 150 589 V000 1 4-3

4.3 Redundancy switchover
A redundancy switchover will be caused by detection of system errors for one of the
active CMUs.
A redundancy switchover will not be caused by
• Failure of a communication link to a master system or to a subsystem.

• Firmware or configuration errors
• PLC alarm condition initiated by a PLC program
A redundancy switchover can also be forced by the connected NCC’s by using the
System Single Commands (SSC).
SSC (#016 … #023) Switch-over to CMU in communication-rack #0 slot x, 1 ≤ x ≤ 8

SSC (#024 … #031) Switch-over to CMU in communication-rack #1 slot x, 1 ≤ x ≤ 8
Redundancy switchover activities
When it comes to a controlled switchover between the two CMU’s, the active CMU stop
the activities and will do an internal restart. The line driver on the communication
interfaces will go to high impedance of the tri-state.
The standby CMU will continue the start procedure. From the viewpoint of the RTU560
system it is a cold start. The now active CMU starts communication on the serial lines
and will initialize the communication to their host and sub-devices. The IO boards will do
a reset. The PDP module takes over the communication on the RTU560 peripheral bus
and reads all values from the IO boards.
The actual state of all CMU’s in a (non-) redundant configuration is shown in the System
Events #149 to #164 and #224 to #239 (see also chapter 16):
SEV (149 … 156) CMU in communication-rack #0 slot x is inoperable, 1 ≤ x ≤ 8

SEV (157 … 164) CMU in communication-rack #1 slot x is inoperable, 1 ≤ x ≤ 8
SEV (224 … 231) CMU in communication-rack #0 slot x is active, 1 ≤ x ≤ 8

SEV (232 … 239) CMU in communication-rack #1 slot x is active, 1 ≤ x ≤ 8
A redundant pair of communication units will show the following states of the System
Events:
Normal operation One CMU is faulty
SEV 149 – 164 SEV 224 – 239 SEV 149 – 164 SEV 224 – 239
(inoperable) (active) (inoperable) (active)
Active No Yes No Yes

CMU
Standby No No Yes No
CMU
4-4 1KGT 150 589 V000 1 ABB AG

4.4 Influence on RTU Functions
4.4.1 PDP and Counter Values
The I/O boards will do a reset. The PDP module takes over the communication on the
RTU560 peripheral bus and reads all values from the I/O boards.
The counter values for the integrated totals (ITI) start with their reset values ‘zero’.
4.4.2 PLC Function
PLC Functions configured on a redundant CMU board
In case of redundancy switchover the PLC program on the new active CMU waits for the
complete refresh of I/O data for process data base of the PLC module. Then a cold start
of the PLC application is performed.
Note:
• The *.pro PLC configuration file has to be loaded to both redundant boards. It will not
be distributed automatically.
• After a restart of a PLC program timers and storage functions start with their initial
values.
PLC Function configured on a non redundant CMU board
This PLC program is not stopped because of a redundancy switchover. During the
switchover, the PLC will continue running, but using the last actual values. The PLC
program can read the status of the system, which allows to program the activities of the
PLC program during the switchover period. After start up of the new active CMU all data
points coming from a redundant CMU are updated. The PLC can continue with normal
operation. It is possible to mix redundant PLC tasks and not redundant PLC tasks in one
RTU560 system.
4.4.3 Group Functions
The Group function task to build summary alarms by AND and OR logic runs on every
CMU. If the Group Function is running on a redundant pair of CMU’s, calculating the
group signals will be started again after the complete switchover by the new active CMU.
ABB AG 1KGT 150 589 V000 1 4-5

4.4.4 Archive and Local Print, Integrated HMI
Archive for process data, the disturbance data archive, the load profile archive and the
local print function have to run on non redundant CMUs (C).
If process archives are used in the Integrated HMI, the Integrated HMI has to run on non
redundant CMUs (C), where the process archives are configured. If not, the Integrated
HMI can run also on redundant CMU’s.
4.4.5 Time Administration
It is possible to connect the real-time-clocks 560RTC01/02/03 to a redundant pair of

CMU’s. In this case, the user has to take care about the following rules:
RTU560C:
The serial peripheral bus (for reading the time information) has to be connected to both
(redundant) CMU’s.
RTU560A (with two communication sub-racks 560CSR01):
It is not possible to install the real-time-clock 560RTC01/02/03 into one of the

communication sub-racks 560CSR01. The clock has to be installed into an extension
sub-rack, which must be connected to both of the Time-Administration-Master.
4.5 RTUtil560 Configuration
The configuration of redundant CMUs is part of the engineering tool RTUtil560. The
definition for each board (master / slave) will be done here. RTUtil560 identifies two
configuration aspects.
• Time-Administration Mode
• Initial Redundancy Mode
Time-Administration-Mode is a functionality of a redundant or non-redundant CMU. The

Time-Administration-Master is responsible for the time-management of the whole system.
The Real-Time-Clock 560RTC01/02/03 have to be connected to the Time-Administration-
Master-CMU.
Initial Redundancy Mode defines the CMU function concerning redundancy. This mode
although defines the default redundancy function after startup of a correct working
system. The Initial Redundancy Modes are Active (A) or Standby (B).
4-6 1KGT 150 589 V000 1 ABB AG

Figure 4-2: Administration and redundancy modes
Figure 4-3: Configuration of redundant CMU’s in RTUtil560
ABB AG 1KGT 150 589 V000 1 4-7

4.6 Redundant Communication
NCC’s (Network Control Center) and IED’s (Intelligent Electronic Devices) can have
redundant communication lines to the RTU560. The availability of redundant lines
depends on the used protocol type.
4.6.1 Redundant Host Communication Interfaces
Redundant Communication Lines to NCC’s are available for the protocols IEC60870-5-
101, IEC 60870-5-104, RP570/71 and Conitel 300. For details see the protocol
descriptions.
4.6.2 Redundant Subdevice Communication Interface
Redundant Subdevice Communication Lines are available for the protocol IEC60870-5-
101 only. For details see the protocol description for this protocol.
The functionality of redundant subdevice communication lines is handled by System

Commands (SSC = System Single Command) (see chapter 0) and supervised by System
Events (SEV) (see chapter 16).
Modem Pools for Subdevice Communication Interfaces
It is possible to connect up to four dial-up modems to the four serial subdevice

communication interfaces of one CMU 560SLI02 or 560CMU04 (For 560ETH02 two
interfaces only). This pool of modems will be administrated by the RTU560. Several
devices can be connected to (one or) several modems. In addition it is possible to
configure redundant communication lines to the subordinated devices.
The modem pool functionality is handled by System Single Commands (SSC), which are
generated depending on commands from the NCC’s (see also chapter 16)
SSC ( 3 … 11 ) System Single Commands
4-8 1KGT 150 589 V000 1 ABB AG

5 Host Communication Interface
This chapter describes the general part of Host Communication Interface (HCI) of the
RTU560. The communication with multiple NCCs with different communication protocols
is one of the basic concepts for RTU560.
Station Control Network Control Center Network Control Center
IEC 60870-5-104
WAN
IEC 60870-5-104
IEC 60870-5-1010 IEC 60870-5-101
DNP 3.0 DNP 3.0 IEC 60870-5-104
RTU560 HCI HCI HCI

IC
SCI PDP SCI SCI

IEC 60870-5-101 SPABus IEC 60870-5-103
DNP 3.0 Modbus IEC 60870-5-101
IED

Marshalling Rack
Protection and
IED
Control Units
Protection and
Control Units
Figure 5-1: RTU560 Network
The RTU560 allows the communication up to 16 different NCCs by using the serial
interfaces of 560SLI02/560CMU04/560CMU05, or serial and Ethernet interfaces from the
560ETH03, 560CMU02, 560CMU04 or 560CMU05. The configuration of the interfaces as
host and communication lines with their protocols is completely done in RTUtil560. There
are no hardware switches to configure the interfaces.
ABB AG 1KGT 150 589 V000 1 5-1

Host Communication Interface Remote Terminal Unit RTU560
Dialog RTU560 – NCC
The assignment of UART host protocols to the serial interfaces is totally free. There are
no dependencies between the different protocols.
Protocols that work not UART based are restricted to the interfaces CPA and CPB on the
CMU 560SLI02 R0002 or 560CMU04 R0002.
Ethernet and TCP/IP based protocols could only be used with the Ethernet interfaces on
the 560ETH03, 560CMU02, 560CMU04, 560CMU05 or 560CMU80 R0002.
Monitoring Direction
All active NCCs get any message that is created in the RTU560. Also any message that
comes from a substation and could be translated between the protocols is sent to the
activated NCCs.
To avoid transmission of certain data points on certain HCIs, a filter can be set in the
configuration for these data points.
Command Direction
Commands to the RTU560 are accepted equal from all central systems. There is no
restriction to the number of different commands that could be handled at one time in the
RTU560.
General Interrogation
The HCI contains a database with the actual state of the process data objects and the
state of the objects from sub-stations. A general interrogation command is answered
directly from HCI with the entries of this database.
Failure of a Host-Line
The RTU560 can manage up to 16 lines to a NCC. To indicate if a communication

between RTU560 and one NCC fails there is a system event message which indicates
the number of the host interface (see also chapter 16).
SEV (101 ... 116): Host no. x online, 1 ≤ x ≤ 16
5-2 1KGT 150 589 V000 1 ABB AG

Remote Terminal Unit RTU560 Host Communication Interface
5.1 Overview HCI Software Structure
The internal software of the Host Communication Interface (HCI) is hierarchical

structured into the three parts
• Interface to the Internal Communication (IC)

• Application layer in monitoring and command direction
• Link layer
NCC
Host Communication
Interfaces (HCI)
Link Layer
Application Layer Application Layer

Monitoring Direction Command Direction
Interface to
Internal
Communication
Internal Communication (IC)
Figure 5-2: Interface IC – Application Layer – Link Layer
ABB AG 1KGT 150 589 V000 1 5-3

5.2 Queue- and Buffer Handling
The events which the HCI receive from the IC are stored into five queues to handle the
different priorities and overflow mechanism. The interface to the IC is responsible for filter
and distribution of the events to the different queues. The Link Layer handles the
transmission of the events from the different queues to the NCC.
The picture below shows the five internal queues between the interface to the internal
communication and the application layer in monitoring direction. These queues are used
independent from the communication protocol in every RTU560 HCI.
NCC
Host Communication
Interfaces (HCI) HCI- Database
Link Layer
Application Layer
Monitoring Direction
Prio 1 Prio 2 AMI AMI ITI

queue queue spont . cycl. queue Application Layer
Command Direction
transm transm
queue queue
Information Information AMI AMI Integrated
objects objects spontaneous cyclic totals
priority 1 priority 2 transmission transmission
Interface to
Internal
Communication
Figure 5-3: RTU HCI queues
Depending on the priority of the queues the application layer monitoring task reads out
the queues and sends the telegrams to the link layer.
• Interface to IC gets a telegram

• Interface to IC distributes the telegram to one of the queues
• Dependent to the priority the application layer in monitoring direction reads out the
queues
• Telegrams in the AMI cyclic transmission queue are stored in the data base.
Telegrams in the other queues are stored in the host data base and send by the
link layer.
• The link layer sends the telegram
An exception to this handling is made for the periodic transmission of analogue measured
values. For these values there is a separated queue named AMI cyclic transmission
queue. The application layer in monitoring direction reads the telegrams from this queue
with highest priority and writes them directly to the HCI-Database. Dependent on the
Background cycle time parameter that could be set for every AMI, the application layer
monitoring direction task reads out the database and writes the telegram to the link layer.
Parameter: Background cycle (AMI – Protocol Address and Parameter)
5-4 1KGT 150 589 V000 1 ABB AG

The Queues
• Priority 1 queue
The Prio1 queue contains the data types SPI, DPI, EPI, BSI, DMI, STI of priority 1
and also System Events
Queue size: 100 ... 3000 entries, default 500
Parameter: Buffer size for priority 1 data points (Interface Parameter)
• Priority 2 queue
The Prio2 queue contains the data types SPI, DPI, EPI, BSI, DMI, STI of priority 2.
Parameter: Buffer size for priority 2 data points (Interface Parameter)
• AMI spontaneous transmission queue

This queue includes analogue measurements, which are transmitted spontaneous.
Parameter: Buffer size for spontaneous transmitted AMI’s (Interface Parameter)
• AMI cyclic transmission queue

This queue includes AMI’s which are transmitted only in a fixed cycle.
Queue size: 300 entries (fix size, not configurable)

Priority: highest
• ITI queue
The ITI queue includes the end of period and intermediate reading integrated
totals. The ITI queue has a transmission priority of 1 or 2.
Parameter: Buffer size for integrated totals (ITI) (Interface Parameter)

Parameter: Priority of ITI queue (Interface Parameter)
5.2.1 Priority – Read Queues
The read access mechanism for the queues depends on the priority of the queues. The
AMI cyclic transmission queue is read out with the highest priority. The other queues
get priorities from 1 to 3
• Priority 1: Prio1 queues

• Priority 2: Prio2 queues
• Priority 3: AMI spontaneous transmission queue
ABB AG 1KGT 150 589 V000 1 5-5

5.2.2 Queue Transitions and Overflow
This topic gives information about the various states and transition conditions of the
queue control of the HCI in monitoring direction.
If the host interface starts, all queue entries are discarded until the internal system event
DB_UPDATED is received. Then the host database is updated. From this time on the
queue control works. The control mechanisms are described in detail below.
Parameter: Queue storage timeout (Interface Parameter)
START
QUEUE DISCARDED
OFFLINE NCC online
System Event
DB_UPDATED
NCC offline
QUEUE OK
QUEUE OK
read queue and send
messages
NCC online OFFLINE offline Timer
4 ONLINE 1 expired
no more marked
messages in
database NCC online
QUEUE OK or
Queue OVERFLOW
QUEUE OK NCC offline
overflow all queue entries will be
transmit marked Queue discarded, read queue
messages from overflow and write marked
database
6 messages to database
ONLINE
3 ONLINE
Queue Queue
ok overflow
QUEUE OVERFLOW QUEUE OVERFLOW offline Timer

read queue and write NCC offline read queue and write expired
marked messages to marked messages to
database NCC online database
5 ONLINE 2 ONLINE
Figure 5-4: Queue handling transition diagram

1. The host interface is ‘offline’, the queues are okay and buffer all information.
2. The host interface is offline and one or more queues have an overflow. The queue
entries are read and written into the database. The data is marked in the database for
later transmission.
3. The host is offline and the offline timer (Queue storage time out) is expired, the queue
entries are read and written into the database. All queue entries will be discarded and
the data is marked in the database for later transmission.
4. The host interface is online and the queues are okay, the queues are emptied and
messages are sent.
5. The host interface is online and one or more queues have an overflow. The queue
entries are read and written into the database. The data is marked in the database for
later transmission.
6. The host interface is online and the queues are okay, marked elements of the
database are read and messages are sent.
5-6 1KGT 150 589 V000 1 ABB AG

ITI Queue – Overflow Handling
Intermediate reading (IR) messages are not stored, when the queue is full. Only end of
period (EPR) messages are then stored in the queue, by overwriting the IR messages in
the queue. In the case that all stored IR messages are overwritten, the oldest EPR
message will be overwritten. So that the queue contains from the actual time backwards
the EPR messages. System Event #133 (for host line 1) up to System Event #148 (for
host line 16) are used to indicate the overflow of an ITI queue.
All Other Queues – Overflow Handling
To avoid an overflow in the queues, there is a queue supervision for all queues except
the ITI queue. If any of these queues has reached the high level (80% filled) the queue is
read with the highest priority, as long as the queue has reached its low level (40% filled)
again. The total number of readings for each queue remains equal.
If not guaranteed, that the in- and outflow of telegrams can be handled quickly enough,
all telegrams from the input queues are read out and will be written to the host database.
No telegrams are sent to the Link Layer. If the Link Layer works again the telegrams are
build out of the database but without timestamps. A system event message which
indicates the queue overflow is generated and filled into the Prio1 queue (see also
chapter 16).
SEV (117 … 132) for host line 1 … 16
ABB AG 1KGT 150 589 V000 1 5-7

6 Sub-Device Communication Interface
This chapter describes the general part of Sub-Device Communication Interface (SCI) of
the RTU560. The sub-device communication interface is used for communication
between RTU560 and subordinated devices. Subordinated devices are RTU560s or in
general- other intelligent electronic devices (IED).
The communication with multiple IEDs with different communication protocols is one of
the basic concepts of RTU560.
A network configuration with subordinated devices is shown in Figure 6-1.
IEC 60870-5-104
WAN
IEC 60870-5-104
IEC 60870-5-1010 IEC 60870-5-101
DNP 3.0 DNP 3.0 IEC 60870-5-104
RTU560 HCI HCI HCI
IC
SCI PDP SCI SCI

IEC 60870-5-101 SPABus IEC 60870-5-103
DNP 3.0 Modbus IEC 60870-5-101
IED

Marshalling Rack
Protection and
IED
Control Units
Protection and
Control Units
Figure 6-1: RTU560 Network
The SCI supports various communication protocols. The protocol specific configuration
parameters are described in additional documents.
The configuration of the SCI and communication lines with their protocols is completely
done in RTUtil560. There are no hardware switches to configure the interfaces.
The SCI can manage up to 32 devices per line. In a RTU560 it is possible to have up to
32 sub-lines.
ABB AG 1KGT 150 589 V000 1 6-1

Sub-Device Communication Interface Remote Terminal Unit RTU560
The assignment of UART sub protocols to the serial interfaces is totally free. There are
no dependencies between the different protocols on one CMU. The only restriction is the
number of communication protocols offered in one firmware package. Not all existing
protocols can be combined on one CMU board. Only certain combinations of protocols
are possible.
Protocols that work not UART based are restricted to the interfaces CPA and CPB on the
CMU 560SLI02 R0002 or 560CMU04 R0002
Ethernet and TCP/IP based protocols could only be used with the Ethernet interfaces on
the 560ETH003, 560CMU02, 560CMU04, 560CMU05 or 560CMU80 R0002.
The structure of the sub-device interface is independent of the protocol and shown in
Figure 6-2.
Sub-Device
Communication Interface to
Interface (SCI) Internal
Communication
Application Layer Application Layer

Monitoring Direction Command Direction
Link Layer
Sub-Device
Figure 6-2: Internal structure of the SCI
6-2 1KGT 150 589 V000 1 ABB AG

Remote Terminal Unit RTU560 Sub-Device Communication Interface
6.1 Message Flow in Monitoring Direction
The messages from a subordinated device are checked by the link layer on valid format
of the configured protocol. If the message is valid it is given to the application layer in
monitoring direction.
The application layer for the monitoring direction decodes the user data. All values, flags
and other information are mapped into the RTU560 internal format
The mapping is shown in the protocol specific description.
If the user data is valid and configured part of this SCI it is sent to the internal
communication.
The queuing between link layer and application layer is secured no messages can be
lost. The sizes of these queues are not configurable by RTUtil560.
6.2 Message Flow in Command Direction
The messages on the internal communication are all detected and checked by the
application layer for the control direction if they are configured part of this SCI.
The application layer for the control direction encodes the user data. All values, flags and
other information are mapped into the protocol specific format.
This mapping is shown in the protocol specific description.
The user data is given to the link layer where the link information is added and sent to the
subordinated line.
The queuing between application layer and link layer is secured so no messages can be
lost. The sizes of these queues are not configurable by RTUtil560.
For some specific protocols it is necessary that the application layer for the control
direction of the SCI simulates messages which are not sent by the subordinated line
protocol and sends them to the internal communication to have consistency to the
internal sequences of the RTU560.
Process commands and status check instructions (during start up) can be given in
parallel to all IED connected to a subdevice communication line.
ABB AG 1KGT 150 589 V000 1 6-3

Sub-Device Communication Interface Remote Terminal Unit RTU560
6.3 General Interrogation
The general interrogation command is done by the sub device communication interface
automatically in following situations:
• System start up
• Redundancy switchover (also when the concerning CMU board is not part of the
redundant system; to actualize the process data from subordinated devices)
• Sub device line status changed from offline to online
If the general interrogation command is not supported by the configured protocol, the SCI
simulates a general interrogation in e.g. with reading of all values or other procedures to
get the actual values of the subordinated devices.
6.4 Time Synchronization
The time synchronization of a subordinated device is autonomously managed by the SCI

and only implemented if it is supported by the configured protocol.
The time synchronization must be configured once per sub-line. It is not possible to
configure different time synchronization modes on one line.
Parameter: Time interval of clock synchronization commands (Line Parameters)
If the RTU560 is synchronized the sub-device communication interface reads the

RTU560 internal time and sends it in a configured period of time to all subordinated
devices if they are in state online.
If the RTU560 has no valid time information, the time synchronization command is
not sent to any subordinated device.
6-4 1KGT 150 589 V000 1 ABB AG

Remote Terminal Unit RTU560 Sub-Device Communication Interface
6.5 System Events
The Subdevice Communication Interface (SCI) manages and controls System Events for
each device that is connected to the line.
Two System Events are controlled by the SCI. For IEDs, these two System Events are
the only ones which are provided by the SCI whereas for RTU560 Sub-devices the SCI
manages the complete System Event Block of an RTU560 with up to 255 System Events.
System Events controlled by the SCI:
System event Address

offset
RTU is active #24
RTU is inoperable #48
• RTU is active
- influenced at RTU startup only
- set to 1, if the SCI line configuration for this IED is correct
- set to 0 if the IED cannot be configured on this line by any reason
• RTU is inoperable
- dynamic communication state of the IED
- set to 1 when communication to the IED fails
- set to 0 when communication to the IED becomes OK
- set to 1 in case of RTU is set to inactive state during RTU startup
ABB AG 1KGT 150 589 V000 1 6-5

7 IEC61850 Station Computer
7.1 RTU560 in an IEC61850 System
The RTU560 provides as IEC61850 client a NCC gateway functionality, connecting an

IEC61850 station bus with network control systems (NCC). The figure below shows the
RTU560 in an IEC61850 system.
Figure 7-1: RTU560 in an IEC61850 system
The standard functionality of the RTU560 like local I/O and connections with legacy
protocols are available as well, but must run on addition communication units (CMU) of
the RTU560 system.
The IEC61850 gateway can run on the communication units 560CMU04 and 560CMU05
only, other standard functionality is not possible on these units.
ABB AG 1KGT 150 589 V000 1 7-1

IEC61850 Station Computer Remote Terminal Unit RTU560
7.2 Engineering process
The engineering process of an IEC61850 system is defined as top-down engineering in

the IEC standard. In this process RTUtil560 is the IED configuration tool for the RTU560.
The following figure shows the different steps of the system engineering in an overview.
Figure 7-2: Engineering Process Overview
The steps in detail are:
1. The Substation Automation (SA) engineer defines in the system configuration the
primary objects, the structure of the substation and Logical Nodes of the substation.
2. The primary system configuration tool exports a System Specification Description

(SSD) file including:
- primary objects
- substation structure
- Logical nodes
7-2 1KGT 150 589 V000 1 ABB AG

Remote Terminal Unit RTU560 IEC61850 Station Computer
3. The communication system configuration tool imports following data:
- SSD-file of the primary system configuration

- ICD (IED Capability Description) files of the IEDs
- ICD-file of the RTU560 (gateway)
4. The SA-Engineer configures the IEC61850 network, the relationship between Logical
Nodes and IEDs and the communication between the IEDs and the gateway. This
configuration is done in the communication system configuration tool.
5. The communication system configuration tool exports a System Configuration

Description (SCD) file including:
- Primary objects
- Substation structure
- Logical nodes
- IEC61850 network
- Relationship between Logical Nodes and IEDs
- Communication between the IEDs and the gateway
6. The SA-Engineer configures in RTUtil560 the network and hardware tree of the
RTU560.
7. RTUtil560 imports the SCD-file.
8. RTUtil560 extracts all available data points from the SCD-file. The data points are build
from the IEC61850 data attributes. The following conditions are required for available
status data attributes:
1. The data attribute is defined as a member of a data set.

2. A Report Control Block is defined for the data set.
3. The Report Control is directed to the RTU560.
Controllable data attributes are extracted independent of the data set configuration.
RTUtil560 writes these data points into the Excel import file.
9. The SA-Engineer or NCC-Engineer defines
- which data points has to be mapped to the internal data points of the RTU560
- which data points has to be mapped to the NCC signal list
- additional information data like specific data point name
10. RTUtil560 imports the completed Excel import file. The configured IEC61850-data
points (all or a subset) are mapped to internal data and to NCC-signal list as defined.
11. The data point configuration is generated by RTUtil560 and loaded to the RTU560.
ABB AG 1KGT 150 589 V000 1 7-3

8 Interfaces and Network
8.1 Network Configuration
IEC 60870-5-104
WAN
IEC 60870-5-104
IEC 60870-5-101 IEC 60870-5-101
DNP 3.0 DNP 3.0 IEC 60870-5-104
560 560 560 560
RTU560 SLI01 SLI01 ETH01 SLI01
A A A A
B B B B
1 1 1
E
2 2 2
IEC 60870-5-101 SPABus
DNP 3.0 Modbus

IEC 60870-5-103
IEC 60870-5-101
IED
Marshalling Rack
Protection and
IED
Control Units
Protection and
Control Units
Figure 8-1: RTU Network with Interfaces
The complete station network with router RTUs, sub-RTUs and IEDs will be configured in
RTUtil560. The configuration of the station network topology will be done in the Network
Tree of RTUtil560. The start point in this tree is the router RTU in the station network. For
a detailed description how to build up the Network Tree see also the RTUtil560 User’s
Guide.
ABB AG 1KGT 150 589 V000 1 8-1

Interfaces and Network Remote Terminal Unit RTU560
8.2 Interface Configuration
8.2.1 The Interfaces
CP1, CP2
560SLI02, 560CMU02, 560CMU04, 560CMU05 & 560CMU80
Parameter: Interface Type: RS232, RS422 (560SLI02, 560CMU04)

RS232 (560CMU02, 560CMU80)
RS232, RS485 (560CMU05)
Parameter: COM Speed: 50 to 38.400 Baud
CPA, CPB
560SLI02, 560ETH03, 560CMU02, 560CMU04, 560CMU05 & 560CMU80
Parameter: Interface Type: RS232, RS485 (560SLI02, 560ETH03, 560CMU04)

RS485 (CPA: 560CMU02, 560CMU80)
RS232, RS485 (560CMU05)
Parameter: COM Speed: 50 to 38.400 Baud
Ethernet Interface(s)
560ETH03, 560CMU02, 560CMU04, 560CMU05 & 560CMU80 R0002
Parameter: IP Address
Parameter: Subnet mask
Parameter: Default Gateway IP
MMI
560SLI02 & 560ETH03 & 560CMU04 & 560CMU80
This interface of type RS232 is provides local PPP (Point to Point Protocol) access to the
RTU's Web Server at fixed communication speed of 38.400 Baud and fixed IP Address
10.0.10.50. The interface cannot be configured. But the connection partner (PC) has to
be configured (see Document RTU560 Web Server User’s Guide chapter Dial-Up,
Network and RAS).
The communication units 560CMU02 and 560CMU05 have no serial interface for the
MMI. For configuration down-load and diagnosis the Ethernet interface is used. The
default IP-address 192.168.0.1 of the board can be set temporary by an onboard jumper.
8-2 1KGT 150 589 V000 1 ABB AG

Remote Terminal Unit RTU560 Interfaces and Network
8.3 Duplex Communication
WT Duplex
4 Wire
NCC
WT
RTU560
Tx Tx
WT
Rx Rx
Figure 8-2: Duplex communication
8.3.1 WT Link Full Duplex (no handshake)
Used with 4-wire or 2 channels in WT-Modems 23WT25 and 4-wire with 23WT23.
It is the same as No HW-Handshake: a Full Duplex transmission with TxD and RxD. DTR
and RTS are set to continuous “On”. This switches the Carrier from the WT’s to on state.
DSR, DCD and CTS are ignored.
Parameter: Modem Control (Interface Parameter)

Transmit delay time (Interface Parameter)
ABB AG 1KGT 150 589 V000 1 8-3

DTR
DSR Not used

used
DCD Not used
RTS
CTS Not used
TxD
RxD
Figure 8-3: WT Full Duplex Link Transmit Control
8.3.2 Direct Link (TxD / RxD only)
Used lines are TxD / RxD in separate ⇒ Duplex Transmission
No control signals used, CTS and DCD simulated to active.

Works in RS232 and RS422 (see Figure 8-3).
RTU and communication partner are directly connected together. Communication partner
may be a PC, another RTU, a PC-Modem or a CS.
Parameter: Transmit delay time (Interface Parameter)
8.3.3 Dial up. (external modem, DCD handshake)
Used lines are TxD / RxD in separate ⇒ Duplex Transmission
Control signals DTR / DSR, RTS / CTS and DCD are used for Flow Control. Operates in
RS232 mode only.
RTU and communication partner are directly connected together. Communication partner
may be a PC, another RTU, a PC-Modem (dial up) or a CS.

8-4 1KGT 150 589 V000 1 ABB AG

DTR
DSR Not used
DCD No effect for transmit
RTS
CTS No effect for transmit
TxD
RxD
Figure 8-4: Direct / Modem Link
NCC NCC NCC
Hayes Modem Hayes Modem Hayes Modem
RTU560 RTU560 RTU560

Figure 8-5: Dial up Configuration
ABB AG 1KGT 150 589 V000 1 8-5

8.4 Half Duplex Communication
WT Half Duplex WT Half Duplex

4 Wire 2 Wire
NCC NCC
WT WT
RTU560
RTU560
Tx Tx Tx
Rx WT Rx
RTU560 WT Rx
RTU560
Tx Tx Tx
Rx WT Rx WT Rx
Figure 8-6: Half Duplex Communication
8.4.1 WT Link Half Duplex (RTS/CTS handshake)
Used in the WT-Modems 23WT23/25 with 2-wire. The Control signals control the Carrier
on the transmission line.

8-6 1KGT 150 589 V000 1 ABB AG

WT Mode, Half duplex,with CTS
DTR
DSR Not used for 23WT21 and 23WT22
DCD Maybeactive in Half Duplex
RTS Switch carrier on
CTS Carrier is on
TxD End of last stop bit
RxD
Figure 8-7: WT-Mode, Half duplex, with RTS/CTS Handshake
8.4.2 WT Link Half Duplex (RTS/DCD handshake)
Used with WT-Modems 23WT23/25 with 2-wire. The Control signals control the Carrier
on the transmission line.
Parameter: Transmit delay time (Interface Parameter)
ABB AG 1KGT 150 589 V000 1 8-7

W-Mode, Half duplex,with CSTD Carrier Setup Time Delay
DTR
DSR Not usedfor 23WT21and 23WT22
DCD Maybeactive in Half Duplex
RTS Switch carrieron
CTS CTS is not connectedor useable
intCTS CSTD CTS is simulated
TxD
RxD
Figure 8-8: WT-Mode, Half duplex, no RTS/CTS handshake
8.5 Additional Communication Modes
8.5.1 Loop Switch unit DSTC 3002
The communication loop switch unit DSTC 3002 for redundant communication lines is
supported only by the RP570/71 host communication interface.
Parameter: Loop switch unit (Interface Parameter)
8.5.2 Link with collision avoidance (DCD handshake)
Collision avoidance is supported only by the host/subdevice communication interfaces

with DNP3.0 protocol. If a collision is detected on the communication link, the interface
will about and wait a random time, before it continuous transmission.
Parameter: Fixed delay time (Interface Parameter)
Parameter: Maximum random delay (Interface Parameter)
8-8 1KGT 150 589 V000 1 ABB AG

8.6 Network Configuration Rules and Restrictions
The configuration of a sub-RTU network is limited by some definitions, physical

restrictions, address ranges etc.:
• In 2 racks, with eight 560SLI02/560CMU04/560CMU05 CMUs in each rack, there

are 64 physical serial interfaces available.
• Max. 16 host-lines
• Max. 32 sub-lines
• Max. 32 sub-stations (RTUs and IEDs) per line
• Each router RTU can be a process RTU
The practical restrictions may differ depending on the communication speed of the station
network, the used communication protocols and the amount of process data points
connected to a RTU560.
8.6.1 Interface Configuration Rules and Restrictions
The assignment of UART host protocols to the serial interfaces is totally free. There are
no dependencies between the different protocols on one CMU.
Special protocols are running only:
• On the CMU 560SLI02 R0002 or 560CMU04 R0002
• On CP1 or CP2 of the CMU 560SLI02, 560CMU02, 560CMU04 or 560CMU05
The SLC works only in one mode (IO Bus, Bit protocols or UART protocols). It is
impossible to mix the mode type. For example it is not possible that CPA works in IO Bus
mode and CPB in Bit protocol.
Ethernet and TCP/IP based protocols can only be used with the Ethernet interface on the
560ETH003, 560CMU02, 560CMU04, 560CMU05 or 560CMU80 R0002.
ABB AG 1KGT 150 589 V000 1 8-9

9 Programmable Logic Control (PLC)
This chapter describes the PLC function, the RTU560 runtime system for control
applications. It has been designed according to IEC61131-3 and is engineered with the
programming and debug system "MULTIPROG wt".
9.1 PLC – SCADA Processing
The PLC is an integrated part of the RTU560 system that exchanges data with SCADA.
from / to Network Control Center from / to MULTIPROG wt
Internal
Communication
Boot
PLC project
PLC
INPUT file
program
memory .
memory
(I) .
PLC
SCADA function
PLC PLC
OUTPUT internal
memory flag
(Q) RTU560 memory
Config-
files
.
.
from / to I/O hardware

from / to sub RTU
Figure 9-1: PLC – SCADA processing in RTU560
Figure 9-1 shows the basic elements of the PLC in interaction with SCADA. They are
described below:
PLC Function
The PLC function is a licensed software package that generally enables the CMU to run
PLC applications and to communicate with MULTIPROG wt for loading and debugging of
applications. It is started at boot time of the CMU if a PLC function is added in the
configuration.
Once started on a CMU, the PLC function is running in shared mode with low priority
compared to the SCADA software.
It is possible to design a configuration, where PLC function and SCADA activities run on
different CMUs. Since both communicate via Internal Communication the PLC function
may run on any CMU within RTU560. This provides maximum processor power for each
of the activities.
ABB AG 1KGT 150 589 V000 1 9-1

Programmable Logic Control (PLC) Remote Terminal Unit RTU560
PLC INPUT, PLC OUTPUT and internal flag memory
The PLC Function has its own memory for these data areas that are allocated at start
time. A PLC application basically reads data from the INPUT (I) memory and writes
calculation results into the OUTPUT (Q) memory. From there it is transferred to SCADA
via the Internal Communication (detailed description see chapter 9.2). Internal memory is
a freely usable memory area (M) for the PLC application.
PLC program memory
The program memory (in RAM) contains the PLC application. From here the PLC
function loads and executes it. The application includes also the entire address
information for data exchange with SCADA and INPUT / OUTPUT memory. The program
memory may be loaded by MULTIPROG wt or from the boot project.
At load time of the application the PLC function formally checks for all data points if they
are included in the RTU560 configuration. If not, a System Message [13.5.4] “Activity
Error for PLC in Rack x Slot y: START ERROR” is generated.
Retain Variable Section
Selected data of the PLC program can be stored on the CompactFlash® Card of the
RTU560. These data will be restored after system startup.
The retain variables are stored on the CompactFlash® Card every 20 seconds, but only if
the contents of the variable section has been changed. By using a special function block
within the PLC program, it is also possible to save this section manually. But the storage
cycle for this operation is also limited to 20 seconds.
Boot project file
The boot project file is a MULTIPROG wt generated file named “bootfile.pro” that
contains the PLC application. It resides non-volatile in the FLASH memory of the CMU. If
no boot project is found at boot time, the PLC function starts without an application, else
the boot project is loaded into the PLC program memory and started (Cold start).
9.1.1 PLC Application and Tasks
A PLC application is generated by MULTIPROG wt after successful compilation of a

project on the PC. From there it may be loaded into program memory (RAM) in order to
test and debug it, or into FLASH memory as a boot project that is started automatically
when the RTU is booted.
A PLC application is processed on the CMU by one or more tasks as defined in

MULTIPROG wt. A task may be defined as CYCLIC, EVENT or SYSTEM type. SYSTEM
tasks are connectable to „System Programs” (SPGs, s. PLC help) Type EVENT is not
supported. CYCLIC type tasks are activated at a specified time interval. The task cycle
time is defined by the user with MULTIPROG wt. The minimum cycle time is specified to:
10 ms.
9-2 1KGT 150 589 V000 1 ABB AG

Remote Terminal Unit RTU560 Programmable Logic Control (PLC)
The PLC cycle time can be incremented in 1 ms intervals but is rounded in each PLC
cycle to 10 millisecond values. A task cycle time should be calculated under
consideration of RTU560 signal configuration and typical event load. The real PLC cycle
time depends on the overall situation within the RTU560 software. In case of SCADA and
PLC configured on one CMU, both share the MPU and SCADA has a higher priority than
PLC. In case of a burst of signal events, SCADA needs more CPU time than in idle loop.
This may stretch the PLC cycle time. In case of high real-time requirements with the PLC
it is recommended to use an extra CMU to run the PLC.
A PLC task can be supervised by a watchdog with definable timeout. If the time needed
for processing the program is longer than the watchdog time the program stops
execution. A PLC program restart can be programmed as reaction to an elapsed
watchdog error (SPG 10) in MULTIPROG wt.
9.2 I/O Interface
9.2.1 General I/O Handling
The I/O Interface for the PLC provides data transfer from SCADA to the PLC and vice
versa.
At startup of a PLC application the corresponding tasks read their input signals directly
from the SCADA database, where the last received data resides. In running mode
however, the I/O Interface works with a queue handling as described below (see Figure
9-2).
Input queues
Command Message
queue queue
PLC core
INPUT OUTPUT
DPI memory memory
SCO SPI
DCO AMI
DPI Value0 Application AMI Value
Value1 Task(s) OV
... BL
TimeTag ...
AND
Input SCO SE TimeTag Output
PID
handler EX
OR
DCO SE handler
... ...
Value Value0
COT Value1
... COT
...
Figure 9-2: PLC I/O Interface
ABB AG 1KGT 150 589 V000 1 9-3

Input queues
The PLC relevant data is filtered from the Internal Communication and written into the
corresponding Input queue for commands or messages/System Events. The maximum
number of entries is 150 for each queue. If a queue overflow occurs, the contents will be
deleted to enable the latest data to be processed.
Input handler
At the beginning of each PLC task cycle the task executes an input handler. The input
handler evaluates the meanwhile received data point signals in the input queues. The
signals that are configured for the task are transferred into the PLC INPUT memory. If a
signal is repeatedly in the queue, the input handler transfers only the first one to the
INPUT memory and writes the rest back to the queue to be processed in the next PLC
task cycle.
If commands are received, the input handler sets the corresponding SE (select) or EX
(execute) flag of the PLC data type in the INPUT memory to TRUE for one task cycle,
dependent on the Select state of the received command (s. Table 9-1).
Received SCADA PLC “EX” state PLC “SE” state

“Select” state of
command
0 TRUE (for one cycle) FALSE
1 FALSE TRUE (for one cycle)
Table 9-1: Select and Execute states for commands in INPUT memory
PLC core
The PLC core processes PLC application in one or more tasks, reading from the INPUT
memory, and writing the calculation results to the OUTPUT memory.
Output handler
At the end of each task cycle the output handler is executed. It checks if the send
condition is fulfilled for each OUTPUT data point (s. Table 9-2). If yes it sends it to the
Internal Communication.
Data point type Data point send condition
SPI, DPI, STI, “Value” or any quality flag have changed compared to last task cycle
DMI8 DMI16, BSI8,
BSI16, ITI
AMI, MFI Any quality flag has changed compared to last task cycle or “TR" (transmit)
flag is set
SCO, DCO, RCO, “SE” (select) or “EX” (execute) flag have a FALSE -> TRUE transition
ASO, BSOx, DSOx compared to the last task cycle and “COT” (cause of transmission) is not
zero
Table 9-2: Data point "send" conditions for the PLC Output handler
9-4 1KGT 150 589 V000 1 ABB AG

9.3 Signal Processing
This chapter describes the possible signal flow between a network control center (NCC),
the PLC and the I/O processing or subordinated RTU.
9.3.1 Messages and Commands
Besides the hardware connectable process data points from the I/O hardware or sub
RTU (both abbreviated with I/O in the following text) a PLC function allows to define
virtual process data points. They are handled by a network control center (NCC) in the
same way as process data points, but are not processed by the I/O.
Network Control Center (NCC)
Virtual Virtual
Confirm. command message
Normal
command
PLC Normal
message
PLC used PLC used

command message
I/O Processing or Sub RTU

Figure 9-3: Signal flow within the system
Figure 9-3 shows in principle the logical signal flow of messages and commands between
NCC and I/O.
ABB AG 1KGT 150 589 V000 1 9-5

The following signal types are supported by the PLC:
• Virtual message
If in configuration a virtual message is added to a PLC task, the PLC may send a
message to the NCC. This message cannot be send by the I/O. Virtual messages
are represented in the OUTPUT memory of the PLC.
• Virtual command
If in configuration a virtual command is added to a PLC task, the PLC may receive
this command from the NCC and send back the confirmations. The I/O does not
know about this command and thus is not able to execute it. Virtual commands are
represented in the INPUT memory for activation/deactivation and in the OUTPUT
memory for the confirmations.
• PLC used message
If in configuration a message data point is selected to be used in PLC, besides the
normal signal flow between I/O and NCC it may be received by the PLC. PLC used
messages are represented in the INPUT memory of the PLC.
• PLC used command
If in configuration a command data point is selected to be used in PLC, besides the
normal signal flow between NCC and I/O the command and the confirmations may
be send and received by the PLC. PLC used commands are represented in the
OUTPUT memory for activation/deactivation and in the INPUT memory for the
confirmations.
If nothing PLC specific is configured with the data points, the PLC does not know about
them and thus is not able to receive or send them.
9.3.2 System Event Processing
Internal System Events (SEV) are received by the PLC. System Events of Sub RTUs are
not supported. If the SEV block in configuration is selected to be used in the PLC, the
System Events are received by the PLC comparable with messages from the I/O.
9.3.3 System Event Messages
There are two System Events available for signaling the state of the running PLC tasks
(see also chapter 16):
• System Event #046: At least one PLC function not active

• System Event #047: At least one PLC cycle time exceeded
9-6 1KGT 150 589 V000 1 ABB AG

9.4 Characteristic Technical Data
1000 Boolean instruction lines: approx. 10 ms
1000 BOOL8 and INT instruction lines: approx. 10 ms
Shortest task cycle period configurable: 10 ms
Memory capacity (program/data) absolute: ≤ 8 MByte (560CMU02/04/05 only),

configurable
Program memory consumption: approx. 10 kByte per 1000 instructions
Program memory capacity per POU: 64 kByte
I/O image capacity configurable: max. 1000 INPUT and 1000 OUTPUT
signals
Maximum number of user tasks: 15
Retain variable section: 1 kByte system flags, 1 kByte user flags
ABB AG 1KGT 150 589 V000 1 9-7

10 Local Print and Process Archive Function
10.1 Overview
The Local Print and Archive function is an option which allows to have locally:
• permanent output to a printing device connected to one of RTU560's serial interfaces

• output to a printer as backup function to the normal host communication; i.e. printing is
started only when all host connections of an RTU are in the off-line state
• output to archive files in CSV format. The archive files are stored in the Flash memory
file system of one CMU of RTU560.
Archive files can be downloaded to a PC or their contents may be displayed using the
RTU560 Web-Server functionality.
Local printout or storage to an archive file respectively is possible for following data
categories:
• Process and System events, Step Position and Bit string information in monitoring
direction, commands in command direction, Login/Logout of HMI
• Measured values (AMI)
• Integrated Totals (ITI)
The ASCII plain text elements object text, state text and one additional character as
event class identifier are assigned individually per information object by means of
RTUtil560 data entry. The object specific text is used for both functions – Archive and
Local Print – if both are activated for the respective information object.
If both functions shall be activated in an RTU560, both must be assigned to the same
CMU board! The Archive function requires that the according CMU board is equipped
with at least a 128MB CompactFlash® card.
ABB AG 1KGT 150 589 V000 1 10-1

Local Print and Process Archive Function Remote Terminal Unit RTU560
Performance Data:
• maximum number of data points to be printed/archived: 5.000
• maximum number of entries per archive file: 10.000
• maximum permanent load of messages to be archived: 50 per second
• maximum object text length [character]: 128
• maximum state text length for binary information [character]: 32
10.2 Message Processing and Buffering
Figure 10-1 shows, in principle, the archive and print related RTU internal message flow.
Events or periodically acquired information from the RTU's local I/O, from Sub-devices or
from output signals of a PLC task running in the RTU are processed by the Archive/Print
Distribution Task. Information, whether a data object message has to be archived or
printed locally, is taken from the PTX configuration file.
Messages that are configured to be printed or/and archived locally, are written to the
corresponding Entry Queue(s), which thus decouple further message processing from
the internal communication flow.
10-2 1KGT 150 589 V000 1 ABB AG

Remote Terminal Unit RTU560 Local Print and Process Archive Function
Local I/O Sub-Device Interfaces
Archive/Print
Message
Distribution
Task
archive/print?
Printer Archive
Entry Entry
Queue PTX Queue
Config
uration
File
Archive Files
Text
Text
Printout Archive File

Task Task
ASCII Printer
Figure 10-1: Message flow Local Print and Archive Function
ABB AG 1KGT 150 589 V000 1 10-3

10.2.1 Supported Data Types
Following data types are supported by the Local Print and Archive function:
SEV System Events SCO Single Command Output
SPI Single Point Information DCO Double Command Output
DPI Double Point Information RCO Regulation Command Outp.
AMI Analog Measured Input ASO Analogue Setpoint Output
DMI Digital Measured Input DSO Digital Setpoint Output
STI Step Position Input BSO Bit String Output
BSI Bitstring Input
ITI Integrated Total Input
EPI Event of Protection equipment Input
10.2.2 Queue Handling
Each of the two entry queues is able to store up to 1000 messages for local printout or
file archiving respectively. If the queues are going to become full, distinct actions take
place for the two queues:
Printer Entry Queue

When 999 messages are stored in the queue and another message shall be written to
the queue, this message is discarded and the message "Printer Queue overflow" is
written as last entry to the end of the queue; the queue input is blocked for further
messages which are discarded during the queue's blocked state.
Releasing of the queue input takes place, when 20 message entries are available again.
As first entry after the queue input, the message "Printer Queue active again" is written
to the queue.
Archive Entry Queue

As long as the maximum number of 1000 archive messages are stored in the queue,
further messages are discarded without any notification; this due to the fact, that the
RTU560 runtime system guarantees a permanent load of 50 archive entries per second.
This is a fixed limit which must not be exceeded, whereas temporary higher message
loads (peaks) are buffered in the Archive Entry Queue.
10-4 1KGT 150 589 V000 1 ABB AG

10.3 Message String Generation
The two tasks
• Printout Task
• Archive File Task
handle the further message processing. Each task is waiting on its corresponding entry
queue, reads and processes message by message as long as there are messages
stored in the queue.
A message's ASCII string is built from
- the message's time tag,

- the information object's plain text elements from the PTX configuration file and
- the data type specific value presentation
The ASCII string is then formatted according to the global settings of the corresponding
function and finally provided as complete record to the respective output handler.
Output String Elements

The output strings are built from the following elements:
1. Date and time

- one character W or S signalizing standard time (W) or summer time (S)
- date in the format yy.mm.dd (archive records only)
- time in the format hh:mm:ss,nnn nnn = 000 to 999 milliseconds
- 3 characters: 3 spaces or TIV as time invalid qualifier
2. Data Type
- 3 characters representing the RTU560 standard data type (see chapter 10.2.1)
3. Object Text
- the individual object text from the PTX configuration file, extended with spaces to the
number of characters specified within the global settings for the respective function
ABB AG 1KGT 150 589 V000 1 10-5

4. Value, object qualifier and event class

- value presentation depending on data type:
a. individual ON /OFF text from the PTX configuration file for SEV, SPI, DPI and EPI
messages
b. system immanent, data type specific representation according to Table 10-1
- 2 characters data object qualifier: 2 spaces / IV / OV (valid / invalid / overflow)

- one character event class identifier from the PTX configuration file
Data Type minimum Value maximum Value unit character qualifiers

AMI IV, OV
Depending on the scaling
DMI IV, OV
STI -63 +63 - IV
ITI 0 2,147,483,646 - IV
BSI 0000h FFFFh - IV
Table 10-1: Value presentation and ranges
10.4 Data Archives
10.4.1 Archive Records
The Archive Output Handler writes the strings as CSV records to the archive files. The
record's ASCII string elements are separated by semicolons; at the end of each record, a
<CR> (carriage return) and a <LF> (line feed) character are appended.
The first record of an archive file contains the system immanent column names of the
record elements:
S/W;Date;Time;Time Invalid;Data Type;Object Text;Value;Data Invalid;Eventclass;
All other records contain the archived process message records. Example for a process
event record:
W;02.07.04;17:27:08,352; ;DPI;DBOX E203 Q1 Disconnector ;open ; ;S;
10-6 1KGT 150 589 V000 1 ABB AG

10.4.2 Archive Files
Depending on the type of data objects to be archived locally, up to 3 archive files are
present in the Flash memory file system of the assigned CMU:
local default File Name provided Message Type Data Typ

File Name by RTU560's Web Server
arcsys.log arcEvLog.txt System events SEV
Process events SPI, DPI, EPI
Step position information STI
Bit String Input BSI
Command Output SCO, DCO
Regulation Commands RCO
Setpoint Commands ASO, DSO
Bit String Output BSO
arcval.log arcMeLog.txt Analog Measurements AMI, DMI
Digital Measurements
arccnt.log arcCoLog.txt Integrated totals ITI
Table 10-2: Archive file types
If an archive file's maximum size is reached and a new record has to be written to the
archive, the oldest record will be overwritten (FIFO principle).
10.4.3 Archive Function Global Settings
Following table shows the global parameters for the archive function of RTU560:
Parameter Range Meaning Default Value

File size 100 … 10000 maximum size 2500 Entries
arcsys.log Entries of the archive file
arcval.log Entries of the archive file
arccnt.log Entries of the archive file
Object text size 16 to 128 character maximum length 32 characters
of the object text string
Value text size 8 to 32 character maximum length 16 characters
of the state text string
Table 10-3: Archive function global settings
Marginal conditions:
• object text size and value text size parameters must get the same values for the
archive function and for the local print function if both functions are activated in the
RTU. If different values are specified, the settings for the local print function are used.
• when a new PTX-file is loaded to the CMU board where the functions are assigned to,
an RTU restart has to be performed to re-initialize the archive and printer functions!
• if the new value specified for the maximum size of an archive file is smaller than the
size of existing archive files, the existing files will be deleted and new ones created!
ABB AG 1KGT 150 589 V000 1 10-7

10.4.4 Access to Archive Data
Display and uploading of stored archive data is provided by RTU560's Web Server.
Details see [2], Users Guide to RTU560 Web Server.
The Web Browser hosting computer has to be connected
• directly to that CMU's serial MMI interface where the archive function is assigned to
• to the Network (LAN or WAN) in case of ETH CMU type. If the archive function is not
assigned to that CMU which provides the RTU's LAN interface, RTU560's internal
routing functionality has to be setup in an appropriate manner. Details see [2].
Note, that network components used in the network path to the RTU must support HTTP
protocol!
10.4.5 Archive Data Import to MS Excel
Archive data from archive files, uploaded to a PC, can be imported to MS Excel. The
following screenshots give an example of an import performed with Excel 97 under
Microsoft® Windows NT 4.0.
With Excel 2000 running under Microsoft® Windows 2000, the dialogs are nearly
identical, whereat the first step can be omitted. The comma (,) used as decimal symbol in
the imported data can be defined within step 3 of the Excel 2000 text import in pressing
the 'Further...' button provided in the 'Step 3 of 3' dialog box.
To get correct results, the import sequence has to be performed as follows:
1. before starting the import, the MS Windows regional settings of the decimal symbol
for numbers has to be checked (Control Panel – Regional settings). If the country
specific default decimal symbol is another character than the comma, e.g. the dot
character, the setting must be changed temporarily to comma (,) :
10-8 1KGT 150 589 V000 1 ABB AG

2. Start MS Excel, open the uploaded archive file – select file type 'Text Files':
3. import step 1: select 'Delimited'
ABB AG 1KGT 150 589 V000 1 10-9

4. import step 2: select 'Semicolon' as data delimiter, {none} as Text Qualifier
5. import step 3: assign the second column data format 'Date' with the sequence 'YMD',
then finish the import
6. When the import is finished, the regional settings for the decimal symbol should be
reset to the old settings (Windows Control Panel). Otherwise other application data
files could be processed or displayed in an incorrect manner!
10-10 1KGT 150 589 V000 1 ABB AG

7. To get the time tags displayed with their resolution of 1 millisecond, the cell format of
the second column has to be set to the custom specific time format 'hh:mm:ss.000'
with following result:
ABB AG 1KGT 150 589 V000 1 10-11

The Excel sheet now is ready to be used for any type of calculation or sort operation.
8. When saving the resulting Excel book, the 'MS Excel Workbook' type should be
selected instead of the 'Text (Tab delimited)' type format as suggested by Excel's
"save As" pane which – if confirmed without additional changes – would overwrite the
original text file!
10.5 Local Print Output
To prepare the ASCII string for local print output, space characters are appended to the
data object specific text elements of the output record to get constant string element
lengths according to the global element length settings. Then the string is sent on the
serial printer interface.
10.5.1 Serial Printer Interface
The serial Printer interface has following characteristics:
The serial printer port can be assigned to one of a CMU board's ports COM1, COM2,
COMA or COMB, selectable communication speed between 50 and 38.400 bit/s.
• the character format is fixed: 1 Start bit, 8 data bits, 1 Stop bit, even parity
• XON / XOFF flow control or hardware flow control is supported:
- on character level at ports COM1 and COM2

- on record level (one text line) at ports COMA and COMB
10-12 1KGT 150 589 V000 1 ABB AG

10.5.2 Local Print Global Settings
The global settings for the local print functionality contain some general parameters.
Definitions of the header and foot line and column header line.
Parameter Range Meaning Default

value
Form feed at no / yes indicates whether a new day's logs shall start on no
midnight a new page
Form feed after no / yes after the specified number of lines, a form feed yes
number of lines character is sent to the printer
Number of lines 20 to 200 number of lines per page 66
Object text size 16 to 128 maximum length 32
characters of the object text string characters
Value text size 8 to 32 maximum length 16
characters of the state text string characters
Print date in no / yes indicates whether the date has to be included in yes
header line the header line
Header line text <TEXT> text to be printed in the header line RTU name
Print column titles no / yes indicates whether the column titles shall be no
on top of page printed on top of each page
Parameter Range Meaning Default

value
Title column 1 <TEXT> text column “TIME” “Time”
Title column 2 <TEXT> text column “TIME VALIDITY” “TIV”
Title column 3 <TEXT> text column “DATA POINT TYPE” “Type”
Title column 4 <TEXT> text column “OBJECT TEXT” “Object text”
Title column 5 <TEXT> text column “STATE/VALUE” “State”
Title column 6 <TEXT> text column “DATAPOINT INVALID” “IV”
Title column 7 <TEXT> text column “EVENT CLASS” “class”
Print date in foot no / yes indicates whether the date shall be printed in yes
line the foot line
Foot line text <TEXT> text at the end of a page RTU name
Table 10-4: Local Print global settings
10.5.3 Page Layout and Page Control
Figure 10-2 shows the page layout in principle. The date is either printed in the header or
in the footer as selected when configuring the Local Print function by means of
RTUtil560. This also applies to the printing of the columns titles on each page. A 4 digit
page number is printed in each pages' foot line. It starts with 0001 after every RTU restart
and becomes 0001 again when 9999 pages are printed without any RTU restart.
ABB AG 1KGT 150 589 V000 1 10-13

date in the header Date(yy/mm/dd): 02/07/04

(if selected) Mannheim TS ABB Kaefertal
Time TIV Type Object text State IV class

header line S 17:28:55,005 DPI DBOX E203 Q5 Earthing Switch open S
S 17:28:55,073 SPI DBOX E203 Bay earthed no E
column titles S
S
17:28:59,964
17:29:01,427
DPI
DPI
DBOX E203 Q1 Disconnector
DBOX E203 Q0 Breaker
closed
closed
S
S
(if selected) S 17:30:21,675 AMI Demobox I L2 +87.28 % C
S 17:29:23,686 STI DBOX E203 TR 1 Tap position +03 T
S 17:29:32,047 STI DBOX E203 TR 1 Tap position +05 T
S 17:29:56,557 SPI DBOX E203 Bay control local B
S 17:30:20,864 DPI DBOX E203 Q0 Breaker open S
S 17:30:21,675 AMI Demobox I L2 +00.00 % C
S 17:30:25,446 DPI DBOX E203 Q1 Disconnector open S
S 17:30:37,649 DPI DBOX E203 Q5 Earthing Switch closed S
S 17:28:37,673 SPI DBOX E203 Bay earthed yes E
S 17:32:00,000 ITI Demobox Energy Input 0000270908 I
S 17:32:00,000 ITI Demobox Energy Output 0000000000 O
S 17:48:00,000 ITI Demobox Energy Output 0000000000 O
date in the foot lines S 17:49:00,000 ITI Demobox Energy Input 0000273874 I
(if selected) S 17:49:00,000 ITI Demobox Energy Output 0000000000 O
Date(yy/mm/dd): 02/07/04
foot line, RTU560 Local Print Example Page 0012
includes page number <form feed>

start of next page:
Date(yy/mm/dd): 02/07/04
Mannheim TS ABB Keafertal
Time TIV Type Object text State IV class
Figure 10-2: Local Print – Page Layout
10.5.4 New Day
At the beginning of a new day, if 'Form feed at midnight' is selected, a form feed
character followed by the header is sent to the printer. If 'Form feed at midnight' is not
enabled, each day at midnight, a text line "Midnight message" is sent to the printer.
10.5.5 Printout after RTU Restart
After restart of the RTU, an activation message is sent to the printer followed by a form
feed character and the first page header. The first page printed after an RTU restart
always gets page number 0001 printed in the foot line.
10-14 1KGT 150 589 V000 1 ABB AG

last log lines before W 17:52:00,000 ITI Demobox Energy Input 0000274398 I
the RTU was restarted W 17:52:00,000 ITI Demobox Energy Output 0000000000 O
activation message A B B - RTU560(e) Local Print Function activated

<form feed>
start of next page:
Date(yy/mm/dd): 80/01/01 RTU not synchronised yet!

header on first page Mannheim TS ABB Kaefertal
after RTU restart Time TIV Type Object text State IV class
System Events and W

W
00:00:00,270
00:00:00,328
TIV
TIV
SEV
SEV
Host 1 online
Host 2 online
No
No
Process logs after W 00:00:00,465 TIV SEV Host 3 online No
W 00:00:01,000 TIV SEV RTU is synchronized No
RTU restart before W 00:00:02,890 TIV SEV RTU is active Yes
first Time W
W
00:01:00,000
00:01:00,000
TIV
TIV
ITI
ITI
Demobox Energy Input
Demobox Energy Output
0000274913
0000000000
I
O
Synchronization W 00:00:05,585 TIV SEV Host 3 online Yes
S 17:55:10,014 SEV RTU is synchronized Yes
S 17:56:57,023 AMI Demobox UL3 +87.00 % 3
System Event and S 17:57:00,437 AMI Demobox IL2 +98.75 % 1
S 17:57:59,680 SPI DBOX E203 Overcurrent Start started P
process logs after the S 17:57:59,860 SPI DBOX E203 Overcurrent Trip tripped P
RTU is synchronized S 18:00:00,000 ITI Demobox Energy Input 0000275753 I
Figure 10-3: Printer Output after RTU Restart
10.6 Data Point Configuration
Configuration information and text information for the RTU's Archive and Print functions is
written to the '.PTX' configuration file which has to be loaded to the flash file system of
that CMU board, where the function(s) is (are) assigned to.
For each data point in monitoring and command direction following items can be
specified:
• Object text of the data point

• State text (ON and OFF – Text for events)
• Event class (one additional character per data object)
• Archive function enable
• Print function enable / Print as backup
ABB AG 1KGT 150 589 V000 1 10-15

10.6.1 Process Data Points
For each process data point in monitoring direction of the data types specified in chapter
10.2.1, archiving or local printout may be configured as follows:
Parameter Values Meaning Default value

Archive function enable no / yes archive function enable for the data point no
Print function enable no / yes print function enable for the data point no
permanently
Print as backup no / yes data point changes are only printed if all no
hosts are offline
Object text <TEXT> text for the object data point
signal name
State text ‘ON’ <TEXT> text for value ‘ON’ “ON”
State text ‘OFF’ <TEXT> text for value ‘OFF’ “OFF”
Event class 1 ASCII class of event, e. g. “A” for alarm, ... space
character
10.6.2 Configuration of System Events
If system events shall be archived or printed, this must be specified by RTUtil560 on RTU
level in general:
Parameter Values Meaning Default

value
Archive function enable no / yes archive function enable for this no
System Event
Print function enable no / yes print function enable for this no
permanently System Event
Print as backup no / yes data point changes are only printed no
if all hosts are offline
Object text <TEXT> text for the System Event System Event
name
Pos. state text <TEXT> text for the positive state “Yes”
Neg. state text <TEXT> text for negative state “No”
Event class <TEXT> class of event, e. g. “S” space
10-16 1KGT 150 589 V000 1 ABB AG

11 Disturbance Data File Archive
11.1 Introduction
Protection equipment is limited in memory and therefore only a small amount of

disturbance-record files can be stored in protection equipment memory before it is
overwritten. To simplify the analysis of disturbance faults and to reduce the time to get
information of these faults, it is necessary to collect them in a centralized archive. This
archive is provided by RTU560.
The uploaded files are stored on the RTU560 file system. To avoid that flash memory on
RTU560 file system exceeds, a file administration function is included.
To get access to the uploaded disturbance-data-files, the archive is displayed by RTU560

Web-Server, where it is also possible to upload files.
In addition it is also possible to upload disturbance data from protection equipment

connected to Sub-RTUs by using file transfer function with the communication protocols
IEC60870-5-101 or IEC60870-5-104.
The Disturbance Data File Archive function requires that the according CMU board is
equipped with a 128MB CompactFlash® card.
ABB AG 1KGT 150 589 V000 1 11-1

Disturbance Data File Archive Remote Terminal Unit RTU560
11.2 The Archive Function
The following drawing shows the structure of the RTU560 disturbance data archive and
upload function. The following functions are required:
• Protection equipment supporting upload of disturbance records
• RTU560 CMU (560SLI02, 560ETH03, 560CMU02, 560CMU04, 560CMU80) with

compact flash file system for archiving the disturbance files
• Work place PC with Web-Browser for uploading the disturbance data
Protection Work Place

with Web-Browser
for access to disturbance
data
Restriction:
PC can only be connected
NCC
NCC to the LAN segments of
PC the 560ETHxx configured
with the archive
TCP/IP Network
HTML (Web-Server)
IEC104 or for access to
DNP over LAN Disturbance Data
for process data
560PSU01 560PSU01 560SLI02 560SLI02
File Archive for
560ETH03 560ETH03
24 V 24 V
Tx Rx
A
B
ERR
Tx Rx
A
B
ERR
Tx Rx
B
C
ERR
Tx Rx
B
C
ERR Disturbance Data
OFF
1 2 3
must be configured on the

5V 5V 1 1
A L A L
2 2 E E
MMI MMI
4
MMI MMI
A A
A A
CMU the Web-Server is

UE + UE +
UE - UE - B B
B B
PE PE
1 1
accessed!
ON ON
E E
2 2
OFF OFF
SPA Bus
IEC101
Disturbance Data
REF542+ REF542+
RTU560 disturbance data
560PSU01
24 V
560PSU01
24 V A
560SLI02
Tx Rx
ERR
560SLI02
Tx Rx
A ERR
560ETH03
Tx Rx
560ETH03
Tx Rx
archive supports
- all protections devices
B ERR B ERR
B B
C C
OFF
1 2 3
5V 5V 1 1
A L A L
2 2 E E
MMI MMI
4
IEC103
MMI MMI
A A
A A
UE + UE +
supporting disturbance record

UE - UE - B B
B B
PE PE
1 1
ON ON
E E
2 2
upload via IEC103

OFF OFF
Protection Protection - REF542+ connected via

Device Device SPA-Bus
SPA Bus
REF542+ REF542+ Disturbance Data from IEDs

connected to Sub-RTUs can be
IEC103 archived in the Router-RTU
Protection Protection
Restriction:
Device Device only one Archive in the RTUtil
NT Project
Figure 11-1: The disturbance data file archive within RTU560
11-2 1KGT 150 589 V000 1 ABB AG

Remote Terminal Unit RTU560 Disturbance Data File Archive
11.3 Protection equipment supported by RTU560
The RTU560 disturbance data archive supports following protection equipment:
• all protection devices supporting disturbance record upload via IEC103
• REF542(Plus) or Rex5xx (e.g. REL531/561) connected via SPABus
The protection device can be connected via an IEC103 line to an RTU560. In addition
REF542(Plus) or Rex5xx are supported connected to a SPABUS line.
After a new disturbance record is available the device must send spontaneous a “list of
recorded disturbances” (ASDU23) to the RTU560. The upload of disturbance records
must be possible according to IEC103 section 7.4.7
After a spontaneous update of the “list of recorded disturbances” (ASDU23) from the IEC
103 device RTU560 checks for new files within the directory. The new disturbance files
are uploaded with low priority and stored in the RTU560 disturbance file archive on the
compact flash card.
For REF542(Plus) or Rex5xx with SPABus RTU560 requests cyclical the device
directory, detects new files and upload them to the disturbance file archive.
11.4 Configuration of a disturbance data file archive
The File-archive is running on any CMU.in the system, in configurations with redundant
CMU’s the File-archive must be configured on a non-redundant CMU (C) (see Figure
11-1). It is also possible to have several file archives in a system.
Figure 11-1: Configuration of file archives function
The File-transfer function is configured on a subdevice communication line. At least two

elements are necessary for this function (see Figure 11-2):
• The File transfer directory (FDR)

with the name of the directory
auf der Compactflash card
• One File transfer file (FTR)

for each disturbance record
to be transferred
Figure 11-2: Configuration of file archive function
ABB AG 1KGT 150 589 V000 1 11-3

Set the parameter for the File Archive according to Table 11-1.
Option / Parameter Range / Comments Default

File type Disturbance recorder – IEC103 -
Disturbance Recorder SPAbus REF542 (Plus)
Disturbance Recorder SPAbus Rex5xx
Max. number of Enable / Disable Enable
archived files in If enable: Number of files in a FTR [1 ... 255] 15
directory If disable: 1 file within FTR
Max. time of storage in Enable / Disable Enable
directory If enable: Delete file after number of days automatically 30 days
[1 ... 365]
If disable: Overwrite the oldest file, if archive is full.
Table 11-1: Parameters for the file archive directory
11.5 Access to the disturbance data file archive
Within RTU560 Webserver there is an own page for the disturbance data file archive.
This page shows the disturbance data files in a variable structure, configurable by the
user. This page is also used for the file transfer of the disturbance data files to the
workplace PC. After the file transfer the files are converted to the COMTRADE format.
But it is also possible to define any other conversion program.
Figure 11-2: View of the disturbance data file archive
The left hand part of the table shows all available directories within the RTU560, the right
hand part shows the directory structure of the local PC.
11-4 1KGT 150 589 V000 1 ABB AG

The menu bar on top of the table contains (from left to right) a pushbutton to open a
dialog for the conversion properties, a pushbutton to navigate in the folder, and a
pushbutton to refresh the page.
Figure 11-3: The elements of the menu bar
Figure 11-4: Detailed view of the file manager
A double click on the directory symbol opens the next level of the directory structure.
A double click on the file symbol opens the properties dialog for this file.
11.6 Conversion properties
11.6.1 Application
Different devices connected via different protocols produces different disturbance

recorder file-formats. These formats are often device specific and can not be displayed
and analyzed by conventional programs for fault analysis (e.g. ABB WinEve). Therefore it
is necessary to convert the files stored by RTU560 File Archive into a supported file-
format.
ABB AG 1KGT 150 589 V000 1 11-5

The following conversion programs are distributed within RTUtil560 installation disc:
Device type Conversion program
REF542 / REF542(Plus) smsconvert.exe
Rex5xx REx5xxConvert.exe
IEC60870-5-103 – Device iec103convert.exe
A detailed description of the conversion programs is included on this disc.
11.6.2 Settings
For each directory displayed in the Archive File Manager it is possible to configure a
target filename and a conversion call. Entered values will be saved on the local PC for
the current logged in user, if the operation system supports user accounts. Therefore the
entered values must only be entered once, even if the web-browser or the RTU560 will
be restarted.
In the field ‘Target Filename’ the resulting name of the selected file after copying to the
local PC can be entered. If no value entered, a default name will be used.
In the field ‘Conversion Call’ the call of an external conversion function can be specified,
that is located on the local PC. This function depends on the device and the protocol it is
connected with. If no value entered, no conversion will be done and the selected file will
only be copied.
Figure 11-5: Conversion Properties View
11-6 1KGT 150 589 V000 1 ABB AG

There are the following three possibilities for the conversion properties:
1. Neither Target Filename nor Conversion Call are selected:

The file name within the RTU560 file archive is used as file name within the PC
Default: FilenumberX – X means number of file, no file extension
2. Only Target Filename is configured:

The Target Filename is used as file name within the PC.
3. Target Filename and Conversion Call are configured:

The Target Filename is used as file name within the PC. Afterwards the
Conversion Call is executed on the local PC.
Both values are strings, which support wildcard usage. With the wildcards it is possible to
define a target filename or a conversion call for all files in a directory.
Wildcards starts and ends always with the percentage-sign % (e.g. %nameoffile% ).
While processing, wildcards will be replaced by the corresponding values of the selected
file.
The following wildcards are supported by the RTU560 archive manager:
Wildcard Meaning
nameoffile Name of File / Fault number of disturbance record

Range: 0 – 65535
revindex Directory entries, that can not be differed by name of file or

creation time, have different revision indices.
Revision index starts always with ‘a’ and will be incremented
cyear2 Year of creation time in format YY.

Example: Year ‘2003’ will be displayed as ‘03’
Range: 0 – 99
cmonth Month of creation time in format MM.

Example: Month ‘December’ will be displayed as ‘12’
Range: 1 – 12
cdayofmonth Day of month of creation time in format DD.

Range: 1 – 31
chourofday Hour of creation time in format HH.

Range: 0 – 24
cminute Minute of creation time in format MM.

Range: 0 – 59
csecond Second of creation time in format XX.

Range: 0 – 59
syear Year of storage time in format YY.

Range: 0 – 99
ABB AG 1KGT 150 589 V000 1 11-7

Wildcard Meaning
smonth Month of storage time in format MM.

Range: 1 – 12
sdayofmonth Day of month of storage time in format DD.

Range: 1 – 31
shourofday Hour of storage time in format HH.

Range: 0 - 24
sminute Minute of storage time in format MM.

Range: 0 – 59
ssecond Second of storage time in format XX.

Range: 0 – 59
workingdir The path of the directory selected on the local PC selected

in the right-panel.
parentdir Name of the parent directory the selected file is located in as

displayed in the header of the dialog.
targetfilename The result of the processed target filename string. That

means all wildcards are already replaced by the
corresponding values of the selected file.
Wildcards which are numbers can be extended to a fixed number of characters by adding
a ‘0’ (Zero) followed by the number of characters of the item.
11.6.3 Example
Value: Creation time 4 minutes, 2 digits with leading ‘0’, if necessary.

Wildcard: %02cminute%
Result: ’04’
Value Creation year 1998, only the last two digits

Wildcard: %cyear2%
Result: ’98’
Value: Creation date 1.12.2002, format YYYY-MM-DD.

Wildcard: %cyear4%-%02cmonth%-%02cdayofmonth%
Result: ’2002-12-01’
MyFile_%nameoffile%_%cyear2%-%02cmonth%-%02cdayofmonth%.xyz
With File number 15 and creation date June 18th, 2003 will result in the string:
MyFile_15_03-06-18.xyz
11-8 1KGT 150 589 V000 1 ABB AG

12 Transmission and Storage of Meter Data
12.1 Overview
Meter Data (Load profiles and log-files) of alpha meters, which are generated in the
devices, are transferred to the Compact Flash Card of one of the CMU’s of a RTU560
system. Using the integrated Webserver of RTU560, it is possible to download these files
to a local PC.
The file archive is running on any CMU in the system. In systems with redundant CMU’s
the file archive must be configured on a non-redundant CMU (group C).
For the storage of load profiles and log files you need at least (see Figure 12-1):
• Communication line with protocol according to IEC 62056-21

(formerly IEC 61107)
• One or more alpha meters (IED) supporting the mode C of IEC 62056-21
• The file archive function running on a non-redundant CMU of the RTU560
• At least one file transfer directory (FDR) with the name of the directory
• At least one file transfer file (FTR) for the records.
Figure 12-1: Configuration example with RTUtil NT
The contents of the transmitted files is according to EDIS (Energy Data Identification
System) ((E)DIN 43863 Part 3), including ASCII data and <CR>/<LF>.
ABB AG 1KGT 150 589 V000 1 12-1

Transmission and Storage of Meter Data Remote Terminal Unit RTU560
12.2 Transmission of Meter Data
The Meter Data is requested in Protocol Mode C according IEC 62056-21. Only some
features of this protocol mode are supported by the subdevice communication interface
(see Table 12-1). R6-command is used for reading in order to transmit the files in
separate blocks with separate checksum.
Mode C Features Support
Bi-directional data exchange Supported

Baud rate switching Not supported
Data readout Supported
Programming with enhanced security Not supported
Manufacturer-specific modes Not supported
Table 12-1: Supported features in IEC 62056-21 protocol mode C
12.3 Transmission Procedure

IEC 62056 Meter Interface
RTU560 transmit receive from meter device
/?12345!<CR><LF>
/ABB4\@V3.01 <CR><LF>
<ACK>041<CR><LF>
<SOH>P0<STX>(00002314)<ETX>d
<SOH>P1<STX>(00000000)<ETX> a
<ACK>
<SOH>R6<STX>P.01(00011150001;)<ETX> -
<STX>P.01(0001115001500)(00)(15)(4)(1.5)(kW)
(2.5)(kW)(3.5)(kvar)(4.5)(kvar)<CR><LF>
(000.000)(000.000)(000.000)(000.000)<CR><LF>
. . . . . . . . . . . . . .
(000.000)(000.000)(000.000)(000.000)<CR><LF>
<EOT>x
<ACK>
... ... ... ...
<STX>(000.000)(000.000)(000.000)(000.000)<CR><LF>
. . . . . . . . . . . . . .
(000.000)(000.000)(000.000)(000.000)<CR><LF>
<ETX>x
<SOH>B0<ETX>q
Figure 12-2: Transmission procedure of meter reading
12-2 1KGT 150 589 V000 1 ABB AG

Remote Terminal Unit RTU560 Transmission and Storage of Meter Data
12.4 Conversion Properties
For each directory displayed in the Archive File Manager it is possible to configure a
target directory and a target filename. Entered values will be saved on the local PC for
the current logged in user, if the operation system supports user accounts. Therefore the
entered values have only be entered once, even if the web-browser or the RTU560 will
be restarted.
The field ‘Target directory name’ contains the name of the target directory on a local PC.
This entry is only necessary for automatic download of meter data, initiated by the local
PC.
In the field ‘Target Filename’ the resulting name of the selected file after copying to the
local PC can be entered. If no value entered, a default name will be used.
In the field ‘Conversion Call’ is not necessary for load profiles and log files.
Figure 12-3: Conversion properties
Both values are strings, which support wildcard usage. With the wildcards it is possible to
define a target filename or a conversion call for all files in a directory.
Wildcards starts and ends always with the percentage-sign % (e.g. %nameoffile%).
While processing, wildcards will be replaced by the corresponding values of the selected
file. The following wildcards are supported by the RTU560 archive manager:
ABB AG 1KGT 150 589 V000 1 12-3

Transmission and Storage of Meter Data Remote Terminal Unit RTU560
Wildcard Meaning
nameoffile Name of File
revindex Directory entries, that can not be differed by name of file or

creation time, have different revision indices.
Revision index starts always with ‘a’ and will be incremented
cyear2 Year of creation time in format YY.

Range: 0 – 99
cmonth Month of creation time in format MM.

Range: 1 – 12
cdayofmonth Day of month of creation time in format DD.

Range: 1 – 31
chourofday Hour of creation time in format HH.

Range: 0 – 24
cminute Minute of creation time in format MM.

Range: 0 – 59
csecond Second of creation time in format XX.

Range: 0 – 59
syear Year of storage time in format YY.

Range: 0 – 99
smonth Month of storage time in format MM.

Range: 1 – 12
sdayofmonth Day of month of storage time in format DD.

Range: 1 – 31
12-4 1KGT 150 589 V000 1 ABB AG

13 Integrated HMI
The RTU560 function Integrated HMI is an easy possibility to realized small customer
specific monitoring and control applications. For this function no additional SCADA
product is required (see Figure 13-1)
Figure 13-1: Example for a single line diagram
ABB AG 1KGT 150 589 V000 1 13-1

Integrated HMI Remote Terminal Unit RTU560
13.1 Overview
The function integrated HMI consists of two parts:
• An editor for the offline configuration

• A runtime system installed on the RTU560
With the offline editor customer specific pages can be created. Therefore a library
package is provided with usable components. It is possible to connect dynamic
components to RTU560 data points. Therefore the editor reads the data point list from
the RTUtil560 configuration file. The editor generates one HMI project file per RTU560
HMI function (see Figure 13-2). This additional configuration file has to be uploaded to
RTU560.
The following options are possible for the connection between RTU560 and the PC:
• Local area network (LAN)

• Wide area network (WAN)
• Dialed line or modem connection (PPP)
• Direct serial connection (PPP)
Requirements for the local PC:
• Microsoft Windows compatible operating system

• Microsoft Internet Explorer
• Java Runtime Environment
The parameters for the integrated HMI are the TCP/IP port number and the maximum
time for local control authority.
Parameter: Port Number (HMI – Parameter)
Local Control Authority (HMI – Parameter)
Figure 13-2: Overview
13-2 1KGT 150 589 V000 1 ABB AG

Remote Terminal Unit RTU560 Integrated HMI
13.2 Structure of the Integrated HMI
The Integrated HMI function can be divided into the following parts:
• HMI Editor
• HMI Library
• User project
• HMI Server
• HMI Application
• HMI Client
The HMI Editor is used to create user projects consisting of components provided by the
HMI Library.
A user project is structured in pages where the components are inserted in. Components
can be configured with the HMI Editor by the user.
Configuration of components is component-specific. This means every component type

has its own configuration facilities. The components are described later on. The HMI
editor provides also a interface to RTU560 configuration files (*.iod, *.gcd) so that it is
possible to connect components to process data configured in RTUtil560. The selection
of process data is done by the object-name of the process data, so no separate
addressing has to be done by the user for this function. Modifications in the RTU560
configuration do not influence a made link to a process data, until the process data is
deleted.
The saved HMI Project has to be downloaded to the RTU560 CMU board where the HMI
server is configured. On this CMU board also the HMI Library has to be available.
Starting the HMI Application on client-system automatically checks, if the HMI Library and
the uploaded user project is cached locally on the client system in the correct version. If
the cached version is not up-to-date, if will be updated in the client-systems cache. Now
the application is started on the client system out of the uploaded user project.
The application contains a HMI Client, which starts automatically the communication-
session to the HMI Server on the RTU560 to retrieve dynamic information of linked
process data points.
Updates of requested process data information are sent spontaneous by HMI Server to
the HMI Client on client system side. The HMI Client distributes this information within the
HMI Application. If a HMI Application is closed, the communication-session between HMI
Server and HMI Client will be closed.
ABB AG 1KGT 150 589 V000 1 13-3

13.3 The HMI-Editor
The HMI Editor is an offline program for configuration of user specific pages. It generates
user project-files that can be uploaded to RTU560 Compact Flash file system.
13.3.1 The Project
A user project contains all configured information made by the user about a HMI
Application. The HMI Editor can create new user projects, open already existing user
projects and save them. All information of a user project are hold within one project file.
The file extension of this file is ‘jar‘.
The absolute path and the filename of an user project will be displayed in the title of the
HMI Editor frame. Before saving an user project a backup is made. This backup-file has
the file-extension ‘jar_bak‘.
User projects are structured into several entries like pages and other resources.
13.3.2 The Page
Pages are used to structure a user project. The can be added, deleted, renamed or
moved within a user project. Pages must have the extension ‘.page‘. Otherwise they will
not be identified as pages.
Open a page using the HMI Editor means to open it for editing in the editors workplace.
To close a page means to hide the selected page.
Pages can be linked between each other by using link-components. One page can be
specified as start page of the user project.
13.3.3 The Background
Images have to be imported into a user project before they can be used. It is also
possible to export any kind of entry out of the user project, e.g. to reuse them in other
projects. The following graphical formats for backgrounds are supported: ‚.gif’, ‚.jpg’.
The import of images is done in the dialogue:
Project Æ Image Æ Import
13-4 1KGT 150 589 V000 1 ABB AG

13.3.4 Operation of the Editor
The HMI-Editor has the same ‚look-and-Feel’ as other Microsoft compatible products
Using the menu button ‚File’ you can (see Figure 13-3):
• Create a New project
• Open an existing project
• Save an open project
• Save an open project with another name
• Close an open project
Figure 13-3: Pull-down menu ‚File’

The menu button ‘Page’ is activated only, if a project is open. Using this menu button the
user can:
• Create a New page
• Open an existing page
• Rename an active page
• Delete the active page
• Close the active page
• Import pages and Export the active page
• Delete the active page
Figure 13-4: Pull-down menu ‘Page’
ABB AG 1KGT 150 589 V000 1 13-5

After opening a new page, an empty worksheet is displayed (see Figure 13-) in order to
place the components on it. The layout of this worksheet can be configured with the
‚Options’ dialogue.
Figure 13-5: Empty worksheet
Using the right mouse button, the ‚Properties’ dialogue is opened, in order to manipulate
the components, like:
• Cut the selected component

• Copy the selected component
• Paste the copied component
• Delete the selected component
• Move a selected component Frontward or Backwards
• Move a selected component ‘To front’ or ‘To back’
Figure 13-6: Properties dialogue
13-6 1KGT 150 589 V000 1 ABB AG

13.3.5 The Components of the Integrated HMI Editor
The components of the integrated HMI editor can be divided into:
• Static components
• Dynamic components
• Links
• Tables
Static components will not change their properties during runtime, while dynamic
components will change their style (color, …), dependent of the actual state of the
process. All components are available in the header line of the HMI editor (see Figure
13-7).
Figure 13-7: The components of the HMI editor
13.3.5.1 Static Components
Static components are fixed during runtime. The following components are available:
• Line component variable color or thickness
• Rectangle component transparent or filled
• Ellipse component or circle, transparent or filled
• Text component Static text, variable style
• Image component Bitmap graphic (*.jpg, *.gif)
13.3.5.2 Dynamic Components
Dynamic components will change their properties during runtime. The following
components are available:
• Normalized value component Process object in monitoring direction

• Floating point value component Process object in monitoring direction
• Integrated total component Pulse counter value
• Byte value component Variable text dependant of the state
• System time component Actual time of the RTU560
ABB AG 1KGT 150 589 V000 1 13-7

13.3.5.3 Dynamic Components with Operator Dialogue
• Bit string component to operate bit string process objects
• Step position component to operate regulation step commands
• Symbol component for circuit breaker, disconnector, …
13.3.5.4 Links
• Link label Link to navigate to over pages
• Link button Push button to navigate to over pages
13.3.5.5 Tables
• History table component Dynamic change of a process object
• Process archives Events, Measurements, Integrated Totals
• Alarm list for all process objects in alarming state
13.4 The Process Archives
Process objects in monitoring and command direction may be archived on the Compact
Flash Card of the RTU560 by configuration. These archives can be displayed in tabulated
form with the integrated HMI.
In addition the following information are archived in the event list (not configurable):
• Login and logout of users of the integrated HMI
• Requests and releases of the command authority
13.5 The Alarm List
The alarm list of the integrated HMI is used to manage process objects in alarming state.
The dedicated process objects and the alarming state(s) are defined by configuration.
Fleeting alarms will disappear from the alarm list, if these alarms were acknowledged
before by the operator (configurable feature).
13-8 1KGT 150 589 V000 1 ABB AG

13.6 The Control Authority
A special user group of the integrated HMI is allowed to operate the process. These
users have to request this control authority by a special dialogue. This request of a local
user will be indicated to all host interfaces by System Event #100. Dependant on the
configuration, commands from the host interfaces will be rejected as long as a local user
with control authority is logged in.
Only one user is allowed to request the control authority at the same time.
The control authority will be released to the system if:
• the user releases the control authority by dialogue
• the user logs out
• the connection between PC and integrated HMI is closed
• a special timer for supervision times out
Parameter: Control Authority Timeout (HMI – Parameter)
13.7 The Component View Editor
Symbol components have a fixed representation within the HMI editor (see chapter
13.3.5.3). In addition it is possible to create user definable component views with a
special view editor included in the HMI editor. These representations will be included into
the Component Library of the integrated HMI.
The following properties for the two (SPI) or four (DPI) states are affected by this editor:
• Representation of the component
• Color of the representation for the different states
• Size of the representation
ABB AG 1KGT 150 589 V000 1 13-9

14 Startup, Configuration, Time Management
14.1 Startup Procedures
A RTU560 System may contain several Communication Units (CMUs, e.g. 560SLI02 or
560ETH03, 560CMU04, 560CMU05). Activities, e.g. communication protocols, I/O Bus
Interfaces or PLC functions, may be configured freely to be running on different CMUs.
RTU560 supports the following startup procedures:
• RTU560 CMU Start

Power ON or reset of a CMU
• RTU560 System Start
Power ON or reset of the RTU560
• RTU560 CMU Integration
Plug in of one CMU in a running RTU560 (only in multiple CMU systems)
• Protocol restart
Communication protocols often provide methods to restart the RTU. Since the
RTU560 may support various protocols, the restart methods are described in the
specific protocol description.
14.1.1 RTU560 CMU Start
When a CMU is started after Power ON or reset command by NCC or RTU560 Web-
Server, it does the following startup sequence:
• Initialization and hardware test (RAM, FLASH, Watchdog etc.), firmware load from
FLASH memory
• Send System Message " CMU in rack x, slot y: STARTUP "
• Check if other CMUs are present in the RTU for 10 s. If yes, the CMU compares its
own firmware and configuration with all present CMUs in the following way:
- the firmware release version no. (first digit, e.g.: 8 for a Version 8.0) must
be the same on every CMU. If not, the CMU stops further initialization and
sends System Message "Firmware-Error on CMU in rack x, slot y version
Vn.xx ". It waits for load of a new firmware and a reset.
ABB AG 1KGT 150 589 V000 1 14-1

Startup, Configuration, Time Management Remote Terminal Unit RTU560
- The .gcd configuration (General Configuration Data) must be present and

equal on every CMU. If not, the CMU stops further initialization, sends
System Message " Config-Error on CMU in rack x, slot y: GCD File date "
and waits for load of a new ".gcd" configuration and a reset.
- The .iod configuration (Input Output Data), if present, must be equal on
every CMU. If not, or if it is missing on any other CMU, the CMU does its
further initialization without ".iod" configuration and sends System Message
" Config-Error on CMU in rack x, slot y: IOD File date " or " Config-Error on
CMU in rack x, slot y: IOD File size ".
- The password configuration for the RTU560 Web-Server must be present
and equal on every CMU. If not, the CMU sends System Message " Config-
Error on CMU in rack x, slot y: Password " does its further initialization with
default password configuration.
• Check if the configuration is formally valid (CMU type, rack and slot address are
correct). If not, the CMU sends System Message " Config-Error on CMU in rack x,
slot y: WRONG RACK OR SLOT ADDRESS ", stops further initialization and waits
for load of a new “.gcd” configuration and/or replacement
• Wait for registration request by RTU560 System Control for 10 sec. If System
Control is not present, System Message " Master for CMU in rack x, slot y: Error "
is sent
• Start Activities as called by System Control (s. 14.1.2). If an Activity cannot be
started, System Message “ Activity Error for <Activity Type> in rack x, slot y:
<Activity-Error Type> ” is sent by the CMU (details s. table “System Messages” in
Chapter 8)
When All Activities are started, and System Control has started successfully, the
following System Events are generated (see also chapter 16):
• CMU in rack x, slot y: operable
• CMU in rack x, slot y: active
14-2 1KGT 150 589 V000 1 ABB AG

Remote Terminal Unit RTU560 Startup, Configuration, Time Management
14.1.2 RTU560 System Start
The RTU560 system start (Power ON or reset of the RTU560) is managed by System
Control which is running on the MASTER CMU. The system start sequence is:
• After CMU start (s. 14.1.1), System Control requests the configured boards and
waits 5 s for their registration.
• RTU560 System Control starts the configured Activities on the registered CMUs in
the following order:
- Archive and Print functions
- Host Communication Interfaces (Slave Protocols, no communication)

- Sub-Device Communication Interfaces (Master Protocols)
- I/O Bus Interfaces (PDP)
- PLC and Local Function tasks
• Sub-Device Interfaces and I/O bus request data from Sub-Devices and I/O Boards.
System Control waits until they report the database update.
• Configured host-interface(s) start(s) communication to the NCC.
• System supervision is started to enable CMU removal and integration.
14.1.3 CMU Integration
In a multiple-CMU system, a single CMU may be integrated into a running RTU560.

During the integration process, already running Activities in the RTU continue their
operation. To be able to integrate a CMU, the following condition must be fulfilled:
• The CMU must be configured in the RTU560
During integration, a CMU does a similar startup-sequence as described in 14.1.1 except

the following:
• If any configuration (.gcd, .iod or password) is not present or different to the files on
the other CMUs, the integrating CMU tries to load it from a CMU that is running.
Afterwards the integrating CMU automatically performs a reset in order to repeat
CMU start with the new configuration.
• After successful startup of the CMU, RTU560 System Control requests a data
update from I/O Bus and Sub-Devices on the CMU(s) that were already running
before the integration to actualize the integrated CMU`s database. Host interfaces
on the integrating board (if present) start communication to the NCC, when this
data update is finished.
If a former ‘active’ CMU of a redundant pair is integrated into the system again, this CMU
will become now the ‘stand-by’ CMU of the redundant pair.
ABB AG 1KGT 150 589 V000 1 14-3

The integration of a CMU is signaled by System Events (SEV) in the following way (see
also chapter 16):
• Non-redundant CMU:
SEV ‘Inoperable’ = ‘False’, SEV ‘Active’ = ‘True’
• Redundant CMU:
SEV ‘Inoperable’ = ‘False’, SEV ‘Active’ = ‘False’
14.1.4 CMU Removal
A CMU may be removed from a running RTU560. Already running Activities on other
CMUs continue their operation.
If a CMU running I/O busses or Sub-Device communication interfaces is
removed, the remaining boards in the RTU560 are triggered to stamp the related
process data invalid in their database.
The removal of a CMU is signaled by System Events (see also chapter 16):
• SEV ‘Inoperable’ = ‘True’, SEV ‘Active’ = ‘False’
If the active CMU of a redundant pair is removed from the system, the system performs a
restart of the former ‘stand-by’ CMU, to become now the active one. The state of the new
‘active’ CMU is:
• SEV ‘Inoperable’ = ‘False’, SEV ‘Active’ = ‘True’
14-4 1KGT 150 589 V000 1 ABB AG

14.2 RTU560 Configuration
14.2.1 General Requirements
The RTU560 needs valid configuration for operation. A RTU560 with multiple CMUs must
keep equal configurations in each CMU.
There are three different types of configuration files:
• General Configuration Data (GCD) configuration: hardware and protocol

information
• Input Output Data (IOD) configuration: process data point information
• Password configuration: password settings for the RTU560 Web-Server
The password configuration has a default setting in a new RTU and may be changed via
Web-Server.
The IOD and GCD configuration is provided by means of two binary files with .iod and
.gcd suffix. The files are stored non-volatile in FLASH memory and are copied into RAM
at CMU boot for read-only access.
The files are generated with the configuration tool RTUtil560 by command (See
RTUtil560 Users Guide, chapter “Generate RTU-Files”). The configuration files may be
loaded to the RTU via RTU560 Web-Server or via NCC using a file transfer service of the
communication protocol.
14.2.2 Configuration File Load Procedure
The configuration file load is done for each of the different types separately. During and
after file load the RTU continues normal operation with its present configuration in RAM.
Activation of the new configuration in FLASH memory is done after the next CMU start.
14.2.2.1 Load Configuration Files via RTU560 Web-Server
The RTU560 Web-Server enables a user to load configuration files into the FLASH
memory file system of the addressed CMU. The addressed CMU cares for distribution of
the loaded files to all CMUs in the RTU, no matter whether they are configured or not.
The user is informed about the success of the file load procedure and about the number
of boards that received the file. He may now decide about the activation of the new
configuration via reset command to the RTU.
14.2.2.2 Load Configuration Files via NCC File Transfer
The configuration file load via NCC is handled together with the host-interface running a
specific communication protocol. The relating file transfer service is documented in the
respective protocol description. The distribution process after file load is the same as in
14.2.2.1.
ABB AG 1KGT 150 589 V000 1 14-5

14.3 RTU560 Time Management
14.3.1 Time Management Principle
RTU560 provides a general time base that may be synchronized in four different modes
to be configured:
• Clock Synchronization Command (CS Command)

Synchronize by a (cyclic) time message from NCC (see 14.4.1).
• CS Command & external minute pulse
Synchronize by a cyclic message via a host communication interface
plus an external minute pulse wired to the TSI (Time Synch. Input) of
the RTU560 (see 14.4.2). Not supported within RTU560E.
• (s)ntp Server
Synchronize by a (s)ntp server via the network (see 14.4.3)
• Radio Clock
Synchronize to the GPS, IRIG-B or DCF 77 standard (middle Europe
only) (see 14.4.4). Not supported within RTU560E.
• Redundant Time Synchronization
Up to eight time server are accepted according to their priority (see
14.4.5).
Parameter: Time synchronization mode (RTU Parameter)
The RTU560 decides during startup - by reading the GCD configuration - what kind of
time synchronization is configured. One CMU synchronizes the RTU time according to
the provided synchronization mode and acts as the Time Master.
Parameter: Time-Administration Mode (CMU Parameter)
Until the RTU is synchronized, the absolute time starts with:

Year month Day hour minute second
1980 01 01 00 00 00
The Time Master CMU keeps the time information for the entire RTU. It generates a
controlled 10 kHz clock and the internal TSO minute pulse which are needed by all Time
Slaves and I/O Master. It distributes the absolute time information in time message
telegrams to Time Slaves and I/O Masters.
14-6 1KGT 150 589 V000 1 ABB AG

NCC
CS-Command
MPU sub
sub RTU
RTU
GPS
TSI input
Logic
IOM
antenna
Master CMU
560RTC
minute pulse
I/O Bus
560RTC01
DCF 77 or
transmitter 560RTC02
Minute pulse
to slow to fast
I/O board
Minute circuit
I/O Controller
Master CMU
Time regulation concept

for Master CMU and I/O Controller
Figure 14-1: Principal of time synchronization in RTU560
Differences between the internal time and the received time on the Time Master are
regulated by scaling pre-divider registers. This method allows a soft regulation of time
differences and a long time correction of crystal clock errors.
The Time Slave CMUs are hard coupled with the 10 kHz clock and the TSO generated
by the Time Master. They cyclically receive a time message by the Time Master via
Internal Communication and synchronize their time accordingly.
The I/O Master (IOM) - on every CMU - is hard coupled with the 10 kHz clock and the
TSO generated by the Time Master. It cyclically receives a time message by the MPU via
the DPRAM interface and synchronizes its time accordingly.
The IOM again transmits a time synchronization instruction (broadcast) cyclically to all I/O
Controllers (IOC) on the I/O boards via I/O bus (typically every 2 seconds). The IOCs
independently regulate deviations between their internal current time and the cyclic
synchronization instructions. All I/O boards are time synchronized by the IO with a
resolution of ± 100µs and accuracy of ± 0.3ms.
ABB AG 1KGT 150 589 V000 1 14-7

Time Time Time

Master Slave Slave
Logic Logic Logic
Time Time Time

Message Message Message
10 kHz
TSO
TSI
RTU560 Internal Communication
Figure 14-2: Time Master and Slave dependencies
14.3.2 RTU560 Time Slave
A Time Slave is running on each RTU560 CMU. Its time management is hard coupled to
the Time Master. Its time base is fed by the 10 kHz signal, synchronization is done via
TSO minute pulse, absolute time is received via time message on Internal
Communication that are provided by the Time Master.
Negative System Event [25] “RTU is not synchronized” is sent if:
• the 10 kHz signal is missed for 5 sec or

• the TSO minute pulse is missed for 10 min or
• the time message is missed for 5 min
14.3.3 Time Zone and Daylight Saving
The RTU560 provides SNTP client and server functionality for the time synchronization.
The timestamps used in the (S)NTP protocol are in coordinated universal time (UTC).
UTC is an atomic realization of Greenwich Mean Time the astronomical basis for civil
time. To convert the UTC timestamps into local time the RTU560 needs information
about the time zone and the daylight saving dates. This chapter explains the
corresponding RTU parameter.
The difference between the local time zone and the UTC time zone is configured with an
offset. The range of this offset is between –12 and +12 hours. The parameter defines the
offset between local time (normal, winter time) and UTC time. For example the Western
European Standard Time (WEDT) has an offset of +1 hour to UTC. The offsets for
several time zones could be found at:
http://www.timeanddate.com/library/abbreviations/timezones/
Parameter: Time-zone offset (RTU Parameter)
14-8 1KGT 150 589 V000 1 ABB AG

The daylight saving dates define day and hour when the time changes from winter to
summer time and vice versa. The parameters specify no exact date but a rule how to
determine the dates every year. The rule includes month, day of week, position in month
and hour. The rule must be read as “position of day in month at hour”. An example is
shown below:
Month: October, Day: Sunday, Position: Last, Hour: 3 means

”Last Sunday in October at 3 o’clock”.
In the year 2005 this leads to the date 10-29-2005, 3 o’clock.
Parameter: Daylight saving time start (RTU Parameter)
Parameter: Daylight saving time end (RTU Parameter)
Important: The difference between summer and winter time is 1 hour. The summer time
is one hour ahead of winter time (+1 hour).
14.4 Time Synchronization Modes
14.4.1 Synchronization by CS Command from NCC
The time and date of the first received CS Command from NCC after start-up is taken to
initialize all time bases on that reference. The Time Master calculates its deviation with
each received CS Command and starts to compensate the difference. The long term
accuracy to NCC is given to:
• ± 5 milliseconds
The CS Command should be sent from primary NCC approx. every 5 minutes. A
supervision time for CS Command may be defined by configuration.
Parameter: Time synchronization lost (RTU Parameter)
If no CS Command is received within the supervision time, the RTU560 Time Master
indicates by negative System Event [25] “ RTU is not synchronized ” that the
synchronization is lost. The RTU560 then runs with the accuracy of its own crystal clock.
The time within the process messages is still valid but not synchronized to NCC.
The communication line that receives the CS Command must be configured via
configuration tool. The CS Command may also be sent to a communication line on a
Time Slave.
Parameter: Time Administration (RTU Parameter)
ABB AG 1KGT 150 589 V000 1 14-9

14.4.2 Synchronization by CS Command & External Minute Pulse
This method means receiving CS Commands from NCC (s. 14.4.4) but synchronizing the
time trigger to an external minute pulse reference, wired to the TSI input. This could be
the minute pulse of a local central clock.
To get a high synchronization accuracy, no filter is allowed at input TSI. This method
should only be used if it is guaranteed that no spikes or additional minute pulses are
received from the external minute pulse source.
Each time the RTU560 receives a CS Command from NCC it calculates the received
time to the next full minute. The RTU560 waits for the external minute pulse to start
trigger (just after the first CS Command) or as reference for synchronization. By receiving
the minute pulse it regulates the time difference in the same way than for the other two
modes.
As in CS Command mode, a supervision time for CS Command and the communication

line that receives the CS Command may be defined by configuration.
Parameter: Time synchronization lost (RTU Parameter)
Parameter: Time synchronization from line (RTU Parameter)
Additionally to the time synchronization supervision timeout in CS Command mode, if the

TSI minute pulse fails for 10 minutes, the RTU560 Time Master indicates by negative
System Event [25] “RTU is not synchronized” the lost synchronization.
14.4.3 Synchronization by sntp
The Network Time Protocol (ntp) is used to synchronize computer clocks on an Ethernet
based network. The RTU560 supports the Simple Network Time Protocol (sntp) which is
a simplified access strategy for servers and clients using ntp. For example sntp doesn’t
provide encryption for the transmitted time. There are no difference in the protocol
between ntp and sntp. That means ntp servers are able to synchronize sntp clients and
the other way round.
The RTU560 supports sntp as client and server. The sntp client is used to synchronize
the clock in the RTU560 from an external source and the sntp server could be used to
synchronize Sub-RTUs or others clocks on the network. The figure below shows the
principal of the sntp time synchronization in the RTU560.
14-10 1KGT 150 589 V000 1 ABB AG

Figure 14-3: SNTP time synchronization in the RTU560
The SNTP client in the RTU560 retrieves the time from an external (s)ntp server and sets
the internal clock according this time. The external (s)ntp server could be an external
clock (e.g. Meinberg GPS LANTIME) or another RTU560. The sntp server in the RTU560
replies with the time from the internal clock on requests from (s)ntp clients in other
devices. This chapter contains all information about the sntp client. The sntp server is
explained in chapter “14.5.2 Synchronization with sntp Server”.
Important: The (s)ntp protocol uses the coordinated universal time (UTC). To get the
RTU560 synchronized in local time the daylight saving and time zone parameter must be
set. See chapter “14.3.3 Time Zone and Daylight Saving” for more information.
Important: The sntp client synchronizes the RTU560 in winter time and sets the
summer/winter time flag according the date.
The features of the sntp client in the RTU560 are:
• Support of sntp version 3 (RFC 1769)

• Operational mode unicast (Client – Server communication) or broadcast (Listen to
broadcast server)
• Request of ntp and sntp server
• Request of up to 5 (s)ntp server in unicast mode.
• Listen to 1 broadcast server in broadcast mode.
The differences between the operational mode unicast and broadcast are explained in
the next figure.
ABB AG 1KGT 150 589 V000 1 14-11

Figure 14-4: sntp operational modes
In addition to the time distribution the main difference between the operational modes
unicast and broadcast is the synchronization accuracy. For more information on time
synchronization accuracy see the section at the end of this chapter.
In the RTU560 the parameters for the sntp client are part of the Ethernet interface
configuration. A sntp client could be configured for each Ethernet interface in a RTU560.
Parameter: sntp client (Ethernet Interface Parameter)
14-12 1KGT 150 589 V000 1 ABB AG

Important: The maximum number of sntp clients per RTU560 is 2. The two clients could
be on separate CMUs or on one CMU with two Ethernet interfaces (560ETH03 Category
R0002).
Each sntp client must have a unique number. Possible numbers are 1 or 2. The client
number doesn’t define the priority of the client as time master. The priority of time
masters is defined in the RTU parameter.
Parameter: sntp client number (Ethernet Interface Parameter)
The current state of a sntp client is represented by a system event in the RTU560.
Possible values for the system event are synchronized respectively not synchronized.
The operational mode of the client must be defined in the sntp client parameter. If the
broadcast flag is set, the client works in broadcast mode. If the flag is not set the client
works in unicast mode. If two sntp clients are configured the clients could work in the
same operational mode or in different modes as well.
Parameter: Broadcast (sntp Client Parameter)
Unicast client features
In unicast mode the sntp client polls up to five sntp servers, cyclical on the network. The
IP address of each server must be configured in the sntp client parameters. If the IP
address of a server is set to 0.0.0.0 the server is not configured. All servers are equal that
means the sntp client tries to poll every server cyclical.
Parameter: sntp server X (sntp Client Parameter)
Important: If the sntp client is configured in unicast mode at least the first sntp server
must be configured (Server address unequal 0.0.0.0).
Important: All configured sntp servers must be visible on the network for the Ethernet
interface. That means the IP address and the subnet mask of the Ethernet interface must
be set according the rules of a TCP/IP network.
The following rules define the synchronization behavior of the SNTP client in unicast
mode. According the rules the internal clock of the RTU560 gets synchronized and the
system event is set accordingly:
• In each cycle the sntp client tries to request every configured server two times. If
both accesses fail the server is defined as not available.
• If more than 50% of the configured servers are not available no time will be
accepted.
• Are the received time from the available servers is significant different no time will
be accepted.
• If more than one server is available the sntp client uses for synchronization the
time from the server with the lowest transmission delay.
The polling interval is configured in the sntp client parameter and the interval applies for
all configured servers. The range of the polling interval is between 1 and 1440 minutes
(one day).
Parameter: Polling interval (sntp Client Parameter)
ABB AG 1KGT 150 589 V000 1 14-13

Broadcast client features
In broadcast mode the sntp client listen to time telegrams on a special broadcast
address. This broadcast address couldn’t be configured but depends on the IP address
and the subnet mask of the Ethernet interface. The broadcast address is calculated
according the following rule:
Figure 14-5: Calculation of broadcast address
The (s)ntp broadcast server sends the time telegram cyclical on the Ethernet network.
The RTU560 supervises the broadcast server with a timeout. If the time telegram doesn’t
arrive during the timeout the according system event is set to ‘not synchronized’. The
range for the timeout is between 1 and 1440 minutes (one day). The timeout is part of the
sntp client parameter.
Parameter: Timeout interval (sntp Client Parameter)
Important: It is not necessary to set the timeout to higher values than the actual
broadcast cycle. The RTU560 firmware makes sure that the timeout doesn’t occur in
normal operation.
The sntp client accepts the time if two complete broadcast time telegrams are received.
In this case the internal clock will be synchronized and the according system event is set
to ‘synchronized’. If the time is the same in two consecutive broadcast telegrams (server
is broken) the time is discarded.
Synchronization accuracy
The (s)ntp protocol considers in unicast mode the transmission delays between client and
server. The client corrects the received time by the transmission delays. This functionality
increases the accuracy of the time synchronization in unicast mode. In broadcast mode
(which is a one way communication) this correction is not possible. In a reference
configuration (see Figure 14-6) where the minute pulse output of an external reference
clock is connected to a binary input of the RTU560 the sntp synchronization accuracy is
defined.
14-14 1KGT 150 589 V000 1 ABB AG

Figure 14-6: Reference configuration synchronization accuracy
The following values apply for the reference configuration with a polling interval of 2
minutes respectively a broadcast interval of 2 minutes:
sntp synchronization accuracy

Unicast mode: +/- 1 msec
Broadcast mode: +/- 10 msec
Important: The specified synchronization accuracy is valid for a local Ethernet network
only. The values don’t apply for the Internet or a cooperate network.
14.4.4 Synchronization by Radio Clock
To synchronize the time via Radio Clock, a real-time-clock board (560RTC01 for GPS,
560RTC02 for DCF77 - middle Europe only, or 560RTC03 for IRIG-B/AFNOR) must be
configured and available. The minute pulse output of the RTC must be wired to the TSI
input terminal on the RTU´s Bus Connection Unit 560BCU0x.
The RTC board receives and synchronizes itself to the DCF 77 / GPS / IRIG-B time
standard. To ensure the functionality of the RTC, the alignment and position of the
antenna should be carefully checked. After power-on the RTC needs approx. 3 - 4
minutes to receive the complete information from the DCF 77 / GPS / IRIG-B transmitter.
Important: To enable time synchronization by radio clock, the Time Master must have an
I/O Bus configured at COM B!
Add I/O Bus to COM B (CMU interface in Hardware Tree)
ABB AG 1KGT 150 589 V000 1 14-15

Each minute the RTU560 Time Master reads the time of the RTC via I/O bus to compare
it with the RTU560 time. When RTU560 is synchronized via RTC it indicates this with
positive System Events [25] “RTU is synchronized” and [26] “External Clock of RTU is
operable”.
If the RTC loses the synchronization (e.g. antenna error), it runs with its internal crystal
clock with the specified accuracy for the next max. 2.5 hours.
The Time Master sends negative System Events [25] “RTU is not synchronized” and [26]
“External clock of RTU is inoperable” if:
• the RTC board fails for 5 min or

• the minute pulse of the RTC board is lost for 10 minutes or
• the RTC is not synchronized to DCF 77 / GPS / IRIG-B for more than 2.5 hours.
14.4.5 Redundant Time Synchronization
Up to eight time-master can be configured to synchronize the RTU560. The input is

accepted from the time master with its highest priority. In case of a failure of the primary
time master, the secondary time master is used. If the primary time master is available
again, he is allowed to synchronize the RTU560.
Parameter: Time Master x (RTU Parameter)
14-16 1KGT 150 589 V000 1 ABB AG

14.5 Synchronization of Sub-RTUs
14.5.1 Synchronization with CS Command
In case of sub-RTUs time synchronization may be done via CS Command. Here any
RTU560 CMU is time master for its sub-RTUs. It simulates the NCC functions by sending
CS Commands cyclically with the used communication protocol. Therefore the cycle time
must be configured. The parameter(s) is described in the specific protocols description
(Line parameters).
In case of “CS Command only” synchronization, the transmission time over the line
makes the time accuracy on the sub-RTU worse by 5 ms per sub-ordinate line (s. Figure
14-7). To keep the same accuracy for all RTUs within a network, they have to be
synchronized by an RTC each or by CS Command & ext. minute pulse.
NCC
CS-Command + 5 ms
RTU 560 + 10 ms
+ 5 ms
+ 15 ms
CS-Command
RTU 560
+ 5 ms
CS-Command
RTU 560
Figure 14-7: Time accuracy in a multi level network (CS Commands only)
14.5.2 Synchronization with sntp Server
The RTU560 supports sntp server functionality for the time synchronization of external
clocks. These clocks could be in sub-RTUs, IED or even PCs that are connected to the
same Ethernet network. The following figure shows the sntp server in the RTU560 in a
possible configuration. The figure is an example only.
ABB AG 1KGT 150 589 V000 1 14-17

Figure 14-8: RTU560 sntp server configuration
The features of the sntp server in the RTU560 are:
• Support of sntp version 3 (RFC 1769)

• Operational mode unicast (Reply to client request) and broadcast (Transmission of
broadcast time telegrams)
• Reply to ntp and sntp clients
The differences between the operational mode unicast and broadcast are explained in
Figure 14-4 (see chapter “14.4.3 Synchronization by s”). In contrast to the client the sntp
server supports both operational modes together (not exclusive like the client). The
parameters for the sntp server are part of the Ethernet interface configuration.
To configure the sntp server the flag in the configuration must be set. If the flag is set a
sntp server is started in unicast mode. In this mode the RTU560 responds to requests
from sntp clients. The time send to the clients is taken from the internal clock. The sntp
server is bound to the Ethernet interface. That means the server responds to clients that
are visible on the connected network according the interface configuration of subnet
mask and IP address.
Parameter: sntp Server (Ethernet Interface Parameter)
Important: There is no restriction on the number of sntp servers per RTU560. Each
Ethernet interface could have one sntp server. That means the maximum number of
servers per CMU is 2 on a 560ETH03 R0002.
14-18 1KGT 150 589 V000 1 ABB AG

Important: The (s)ntp protocol uses the coordinated universal time (UTC). To get the UTC
time for the sntp server from the internal local time the daylight saving and time zone
parameter must be set. See chapter “14.3.3 Time Zone and Daylight Saving” for more
information.
Additional to the unicast server a broadcast server could be configured per Ethernet
interface. In this case the RTU560 responds to client requests and sends broadcast time
telegrams cyclical. The time telegrams are send to a special broadcast address that
depends on the IP address and the subnet mask of the Ethernet interface. The broadcast
address is calculated according Figure 14-5 (see chapter “14.4.3 Synchronization by s”).
Parameter: broadcast (Ethernet Interface Parameter)
The cyclical interval for sending broadcast telegrams could be configured in the range
between 1 and 1440 minutes (one day).
Parameter: Broadcast interval (Ethernet Interface Parameter)
Unicast and broadcast server are independent from each other and don’t interact.
ABB AG 1KGT 150 589 V000 1 14-19

15 Status and Diagnostic Information
15.1 Status and Error Report to NCC
RTU560 reports the System Status and Error states to the NCC by means of System
Events (see chapter 16).
RTU internally, System Events are processed and provided as Single Point Information.
Message types and message identifications used to send System Events to a NCC
depend on the communication protocol used on the host interface.
15.2 Web-Server Diagnosis
The RTU560 Web-Server is the common maintenance and diagnosis entry to RTU560.
Within this chapter the diagnosis functions are described. Further information concerning
the Web-Server provided by RTU560, see document “RTU560 Web-Server User`s
Guide”.
15.2.1 System Diagnosis
Within the System Diagnosis page, the RTU560 Web-Server provides the RTU's System
Messages. System messages are displayed after selecting the hyperlink “System
Diagnosis” on a standard Web browser surface addressing the RTU560 Web-Server's
homepage.
The diagnosis information is shown in two different views:
• General View (Overview)
• Detailed View
The System Diagnosis page shows the list of System Messages - one line per message -
in chronological order. The general format of a System Message line is:
System Time->System Message
Where System Time is printed in the format: yy.mm.dd, hh:mm:ss
The system time and date is set to 80.01.01, 00:00:00 approximately 30 seconds after a
CMU's restart. System Messages from the first 30 seconds after CMU restart are printed
without date and time information.
Afterwards every CMU´s internal time is used. When the RTU is time synchronized, this
is indicated by System Message [9.4] “RTU is synchronized” within the list of System
Messages.
ABB AG 1KGT 150 589 V000 1 15-1

Status and Diagnostic Information Remote Terminal Unit RTU560
In Multi-CMU configurations each CMU holds and controls its own buffer for System
Messages. There is no synchronization of the System Message buffer contents between
the CMUs. This means, that the display of the System Messages using different CMU's
MMI interface may look different, especially for the first seconds after RTU restart. Every
CMU starts to listen to System Messages 15 to 20 seconds after its power-on or reset.
Example (General View):

in an RTU with two CMUs -> a ‘Initially active’ CMU in slot 3 and a ‘stand-by’ CMU
in Slot 4, the System Message display of the CMU in slot 4 might look as follows:
80.01.01, 00:00:00->CMU in rack 0, slot 4: STARTUP

80.01.01, 00:00:00->CMU in rack 0, slot 3: STARTUP
80.01.01, 00:00:42->CMU in rack 0, slot 4: Operable
80.01.01, 00:00:45->CMU in rack 0, slot 3: Operable
80.01.01, 00:00:42->CMU in rack 0, slot 4: Not active
80.01.01, 00:00:45->CMU in rack 0, slot 3: Active
07.05.08, 15:42:51->RTU is synchronized
Most of the System Messages influence the RTU Error Status (Warning / Alarm / OK) of
RTU560.
15.2.2 Status Information
The RTU560 Web-Server's Status Information pages provide information about the
hardware configuration of the RTU, state and status of any information object configured
in monitoring direction and the actual state of all System Events. This information is
displayed after choosing the hyperlink “Status Information” on a standard Web browser
surface addressing the RTU560 Web-Server.
The actual configuration is shown in a tree structure similar to that one of the hardware
tree in RTUtil560. The display of the actual state is activated by selecting the related link
items within the tree. The state information actually displayed is actualized approximately
every 5 seconds:
• the actual value of any data object configured in monitoring direction

• data objects actually having any faulty state are marked by the additional string "iv"
in red color
• if a link to an RTU560 is selected, a list of the actual state of all System Events of
this RTU is displayed – OK states in green color, faulty states in red color
• if a link to an IED sub-device is selected, the actual state of the two System Events
"active" and "inoperable" for this IED is displayed
• If a 560ETH03, 560CMU02 or 560CMU04 board is selected, the related network
settings (IP-Address, Subnet Mask and Default Gateway) are displayed.
15-2 1KGT 150 589 V000 1 ABB AG

Remote Terminal Unit RTU560 Status and Diagnostic Information
15.3 RTU Alarm and Warning
The CMU, to which MASTER administration mode is assigned, evaluates the System
Messages generated by any CMU of an RTU560 to build the RTU560 Warning and
Alarm state.
If a Bus Connection Unit Bus Connection Unit device 560BCU01/02/03 is present in the
RTU, the Warning and Alarm states are signalized by means of NC contacts of the Alarm
and Warning relays of the BCU. The hardware logic on the BCU always closes the
Warning contact in parallel if the Alarm contact is closed.
In addition the BCU boards provide a watchdog timer which is re-triggered periodically by
the MASTER CMU. If the watchdog time of about 30 seconds elapses without any re-
trigger signal, the Warning and Alarm contact is closed by the BCU's watchdog logic.
The RTU internal Alarm and Warning states additionally can be influenced resp.
controlled by a PLC program running on any of the RTU's CMUs. For this purpose,
specific PLC Function Blocks are provided in the RTU's PLC Firmware Library RTU_FW.
Details see RTU560 Documentation "PLC Libraries".
15.4 Board States and LED Signaling
All RTU560 boards have LEDs to indicate errors or operating modes. These LEDs allow
a general visual check of the overall situation of the RTU560. The following chapters
describe the LEDs for each board.
ABB AG 1KGT 150 589 V000 1 15-3

15.4.1 Communication and Data Processing Units
15.4.1.1 LEDs on 560SLI02, 560ETH03, 560CMU02 and 560CMU04
ERR = Error (red)

560SLI02 Tx = Transmitted Data (green)
Tx Rx CE Rx = Received Data (green)
A ERR CE = Communication Error (Yellow)
B A = Serial Interface A
1 B = Serial Interface B
2 1 = Serial Interface 1
2 = Serial Interface 2
Figure 15-1: LEDs on 560SLI02
ERR = Error (red)

560ETH03 Tx = Transmitted Data (green)
Tx Rx CE Rx = Received Data (green)
A ERR CE = Communication Error (Yellow)
B A = Serial Interface A
A L B = Serial Interface B
E
E = Ethernet Interface
A = Ethernet Active (green)
L = Ethernet Link (yellow)
Figure 15-2: LEDs on 560ETH03
15-4 1KGT 150 589 V000 1 ABB AG

Figure 15-3: LEDs on 560CMU02 and 560CMU05
Figure 15-4: LEDs on 560CMU04
ABB AG 1KGT 150 589 V000 1 15-5

15.4.1.2 CMU States
CMU Boot State
After Reset (Power switch ON or software reset by Web-Server / Control System) the
CMU is in Boot State, where hardware and basic hardware drivers are initialized. The
only signaling in that state is the red ERR LED.
The Boot state signaling of the CMU is:

Signal element Signal
System Diagnosis -
"ERR" LED (red) ON
Alarm relay ON
Warning relay ON
Since the application firmware of the CMU is not started yet in boot state, the System
Diagnosis via Web-Server is not available.
In case of errors during hardware initialization, the CMU stays in boot state.
If the boot state is finished successfully, the ERR LED changes to OFF for approx. one
second and afterwards goes ON again. Now the CMU changes to "Startup" state.
CMU Startup State
In "Startup" state the CMU initializes itself by evaluating the configuration files. During this
process, configured communication interfaces and internal Activities on all CMUs in the
RTU are initialized by the Administration MASTER CMU in the following sequence:
- Archive and Print functions

- Internal Database
- Logic Functions
- Host Interfaces
- Sub device Interfaces
- I/O Bus Interfaces
- PLC functions
The Startup state signaling of the CMU is:

System Diagnosis "CMU in rack x, slot y: STARTUP"
"ERR" LED (red) Flashing with approx. 2,5 Hz
Alarm relay ON
Warning relay ON
For configured communication interfaces, additional signaling is done at the serial

interfaces (see chapter 15.4.1.3) when they are initialized.
From Startup state the CMU changes to one of the states OK, Warning or Alarm,
dependent on the success of the initialization.
15-6 1KGT 150 589 V000 1 ABB AG

CMU Alarm State
Alarm state of the RTU per definition means a fatal error in the RTU as described in the
RTU560 Function Description.
The Alarm state signaling of the CMU is:

System Diagnosis s. Function Description
"ERR" LED (red) ON
Alarm relay ON
Warning relay ON
In Alarm state the Administration MASTER CPU sets the Alarm and Warning relay to
active state.
CMU Warning State
Warning state per definition means a minor error in the RTU as described in the RTU560
Function Description.
The Warning state signaling of the CMU is:

"ERR" LED (red) Flashing with 1 Hz
Alarm relay OFF
Warning relay ON
In Warning state the Administration MASTER CPU sets the Warning relay to active state.
CMU OK State
In OK state the RTU is running error free according to the active configuration.
The OK state signaling of the CMU is:

"ERR" LED (red) OFF
Alarm relay OFF
Warning relay OFF
In OK state the Administration MASTER CPU sets the Warning and Alarm relay to
inactive state.
ABB AG 1KGT 150 589 V000 1 15-7

15.4.1.3 Communication Interface States
Serial Interface states
All serial interfaces on the CMU signalize their state via LED if they are configured.
Serial Interface Boot and not configured state
This state applies to a serial interface if the CMU is in "Boot" state or the interface is not
configured.
The boot state signaling of a serial interface is:

Serial Interface "Tx" and "Rx" LED (green) according to data request
Serial Interface “CE” LED (yellow) OFF
Serial Interface Startup state
This state applies to a serial interface if the CMU is in state "Startup" and the initialization
of the serial interface via configuration files is in progress.
The startup state signaling of a serial interface is:

Serial Interface "Tx" and "Rx" LED (green) according to data transfer
Serial Interface "CE" LED (yellow) Flashing with approx. 2,5 Hz
If startup fails, a System Message "Activity Error for <Activity Type> in rack x, slot y:
<Activity-Error Type>" (s. Function Description) is generated in System Diagnosis.
Serial Interface OK
After successful startup the active communication protocol sets the OK condition. After a
communication error in running mode the state is set back to OK state with the first
correctly transmitted telegram.
The OK state signaling of a serial interface is:

Serial Interface "CE" LED (yellow) OFF
15-8 1KGT 150 589 V000 1 ABB AG

Serial Interface Error
In case of a communication error (parity error, gap supervision error, baud rate error,
etc.) or after a failed Startup a serial interface is set to Error state.
The Error state signaling of a serial interface is:

Serial Interface "CE" LED (yellow) ON
Note: The yellow “CE” LEDs are not available on the communication unit 560CMU02 and
560CMU05.
Ethernet Interface
The Ethernet Interface (560ETH03, 560CMU02, 560CMU04, 560CMU05 or 560CMU80

R0002) signaling is not influenced by the RTU560 application.
If an active Ethernet line is connected to the CMU, the signaling is as follows:

Ethernet interface "A" LED (green) according to data transfer on the
Ethernet line
Ethernet interface “L” LED (yellow) According to the state of the
Ethernet link
If no active Ethernet line is connected, the signaling is accidental. This applies for all
states.
ABB AG 1KGT 150 589 V000 1 15-9

15.4.2 I/O Boards, Modems and Real Time Clocks
15.4.2.1 LED Indications 23AA20 / 23AE23 / 23BE23
Figure 15-5: LEDs 23AA20 / 23AE23 / 23BE23
LED indication Board indication

Board runs initialization procedure
Board is doing a cold- or warm start
Board has detected a memory error (EPROM and/or RAM)
23AA20
The microcontroller / - processor has an error
23BE23 23AE23
Peripheral bus processor did not poll the board for at least two
minutes.
Time out IOM cycle
A/D converter faulty -
15.4.2.2 LED Indications 23BA20 / 23BA22
23BA22 23BA20
red Error
red Error
red Process error
red Process error
green Command output

green TM1 Test Mode circuit 2
green TM0 Test Mode circuit 1
green CO Command output
red LOC LOCAL / REMOTE

LOCAL / REMOTE
push button
Figure 15-6: LEDs 23BA20 / 23BA22
15-10 1KGT 150 589 V000 1 ABB AG

LED Status LED indications

ST ON Board runs initialization procedure.
Board is doing a cold- or warm start.
Board has detected a memory error (EPROM and/or RAM).
The microcontroller / - processor has an error.
PST ON 24 V DC for output relays failed or internal short circuit etc.
Time out IOM cycle. An active output is stopped (switched off).
TM0 / ON (1 out of n) - check active on circuit P1 (TM0) or P2 (TM1)
TM1 OFF last command output performed successfully
flashing last command output sequence stopped due to resistance violation
CO ON At least one relay is switched on. Command output active
(pulse output or persistent if a GOM output is activated).
LOC ON 23BA22 is switched to local mode. No active output possible
(GO relay disabled).
OFF Remote = normal command output
flashing LOCAL / REMOTE toggle time window
LOC pushbutton
Press key twice within 5 seconds to switch to LOCAL or back to REMOTE. If you
press it only once, it is ignored. The LOC-LED will flash during that time window.
The state of the LOCAL/REMOTE switch is sent to the NCC’s by a System Event:
System Event #64 for check circuit 1

…..
System Event #95 for check circuit 32
Object command output with (1 out of n)-check:
For an object command output with command supervision the LEDs of 23BA20 and
23BA22 must be regarded together. See also chapter: Command output with supervision
and see figures: 3-9 to 3-11 how the two boards are operating together for a command
output.
23BA20 Meaning
LED 1 2 3 4 5
Error ST
Process voltage error PST
Command output CO z z z
23BA22
Error ST
Test mode circuit 1 TM0
Test mode circuit 2 TM1 z
Command output CO z
Local LOC
= ON ≈ 2,5 Hz ≈ 1 Hz Serial data
Figure 15-7: Normal object command output
ABB AG 1KGT 150 589 V000 1 15-11

(1) Before the pulse output
(2) 23BA20 has switched the output channel
(3) 23BA22 does the (1 out of n)- check (positive) and activates GO relay for the
given pulse time
(4) 232BA20 is still active; but the output relay will be switched off by the
communication unit
(5) After the pulse output
Object command output and failure at (1 out of n)-check:

23BA20 Meaning
LED 1 2 3 4 4a 5
Error ST
Command output CO z z z z
23BA22
Error ST
Test mode circuit 1 TM0 z
Test mode circuit 2 TM1
Command output CO
Local LOC
= ON ≈ 2,5 Hz ≈ 1 Hz Serial data
Fig. 1 - 5 : Object command output and failure at (1 out of n)-check
(1) Before the pulse output
(2) 23BA20 has switched the output channel
(3) 23BA22 does the (1 out of n)-check. The result is negative.
(4) 23BA22 flashes LED PST and TMx
(5) Alternative to 3: If the result is positive the command is switched on.

If the 24 V DC fails during command output PST and CO flashes.
23BA20 relay is switched off. If failure 4 occurred The 23BA22 LEDs keeps flashing until
the next output command.
15-12 1KGT 150 589 V000 1 ABB AG

15.4.2.3 LED Indications 23WT25
Figure 15-8: LED’s 23WT25

TxD ON Transmitted data true
RxD ON Received data true
RTS ON Request to send = ON
DCD ON Data carrier detected = ON
EQZ ON Equalizer
SQL ON Signal quality level
15.4.2.4 LED Indications 23WT23/23WT24
23 WT 23
TxD = Send data (green)
RxD = Receive data (green)
TxD RxD
RTS = Request to send (yellow)
RTS DCD
DCD = Data carrier detected (yellow)
Figure 15-9: LED’s 23WT23/23WT24

TxD ON Transmitted data
RxD ON Receive data
RTS ON Request to send
DCD ON Data carrier detected
ABB AG 1KGT 150 589 V000 1 15-13

15.4.2.5 LED Indications 560RTC01
560RTC01
red Error
red FR Free running

green LS Lock status (GPS receive signal)
yellow MN Minute pulse
Figure 15-10: LED’s 560RTC01

ST ON - Antenna / converter unit is defect
- Antenna cable is defect
- Watchdog because of an error on the board
FR ON 560RTC01 is not synchronized by the GPS time standard or has lost
the synchronization
LS ON The LED indicates that at least 4 satellites are received after start up
of the board and the receiver has calculated his position
MN ON Minute pulse.
- Flashes every minute for about 1 second.
560RTC02
red Error
red FR Free running

green CD Carrier detect (DCF77 receive signal)
yellow MN Minute pulse
15-14 1KGT 150 589 V000 1 ABB AG


ST ON - Board runs initialization procedure
- Board is doing a cold- or warm start
- Board has detected a memory error (EPROM and/or RAM)
- The micro controller / - processor has an error
FR ON 560RTC02 is not synchronized by the DCF77 time standard or has lost
the synchronization
CD ON The LED indicates the receiving level of DCF77 transmitter. It allows to
adjust the antenna to the maximum receiving level.
MN ON Minute pulse.

ST ON - Board runs initialization procedure
- Board is doing a cold- or warm start
- Board has detected a memory error (EPROM and/or RAM)
- The micro controller / - processor has an error
FR ON 560RTC03 is not synchronized by IRIG-B / AFNOR time standard or has
lost the synchronization
CD ON 560RTC03 has received valid IRIG-B / AFNOR time telegram
TS ON 560RTC03 is synchronized by IRIG-B / AFNOR time telegram
MN ON Minute pulse.
ABB AG 1KGT 150 589 V000 1 15-15

15.4.3 LED indications 23OK24
Figure 15-13: LED’s 23OK24
15.4.4 LED indications of decentralized modules
15.4.4.1 LED indications 23BA40 and 23BE40
Figure 15-14: LEDs 23BA40
Figure 15-15: LEDs 23BE40
15-16 1KGT 150 589 V000 1 ABB AG

15.4.4.2 LED indications 560CVT01
Figure 15-16: LEDs 560CVT01
ABB AG 1KGT 150 589 V000 1 15-17

16 System Data Interface
16.1 System Events
Information in Web-Server.
The columns have the following meaning:
• SEV offset:
System Event offset address within the System Event Block
• System Event
Meaning of System Event list in case of positive transmission value. The default
value is “not set” ("0")
• Reason(s)
Possible reason(s) for the occurrence of the message
SEV System Event Reason(s)

offset
016 At least one indication is faulty At least one SPI or DPI or a result of the ‘Logic
Function’ is faulty or blocked
017 At least one analog value faulty At least one AMI is faulty
018 At least one digital value faulty At least one DMI, STI, BSI is faulty
019 At least one pulse counter faulty At least one ITI is faulty
020 At least one command is faulty At least one SCO or DCO is faulty
021 At least one analog output faulty At least one ASO is faulty
022 At least one digital output is faulty At least one DSO or BSO is faulty
023 RTU is faulty Error in configuration data, no configuration data
(*.gcd, *.iod) available
024 RTU is active Local RTU: Configuration data for this RTU is correct,
Subordinated device (IED): Set once after the
successful startup of the subdevice interface
025 RTU is synchronized RTU560 is synchronized by (s)ntp server, real-time-
clock or host system (NCC)
026 External clock is inoperable Real-time-clock 560RTC01/02/03 is faulty
027 Local Printer offline If ‘Local Archive/Print’ is enabled:
028 At least one indication is oscillating Set together with System Event #16, if ‘Maximum
chatter frequency’ is exceeded and process data point
is blocked for at least 60 seconds. In this case ‘System
Event’ #016 is set too.
029 System Battery low (RTU560E only) Set if the backup-battery connected to the power
supply unit 560PSU81 is low
030 AC Power Supply failed (RTI560E only) Set if the AC power for the power supply 560PSU81 is
missing, and the system is running on backup-battery
044 At least one DCE faulty Dial-up connections only: At least one dial-up
connection is faulty
045 Device connected Dial-up connections only: At least one dial-up
connection is established by a ‘System Command’
#003 (see also chapter 0)
046 At least one PLC function not running Systems with PLC only: At least one of the PLC
functions is not running
047 At least one PLC function cycle time exceeded Systems with PLC only: At least one PLC function has
exceeded the configured cycle time
ABB AG 1KGT 150 589 V000 1 16-1

System Data Interface Remote Terminal Unit RTU560
SEV System Event Reason(s)

offset
048 Device is inoperable Set/reset for subordinated devices (IED) only: Sub-
RTU or IED becomes inoperable
049 Device out of service Set if a subordinated device was set out of service by a
‘System Command’ #001 (see also chapter 0)
059 Power supply failure in RTU central subrack For redundant power supply units 560PSU01 or
560CSR01 560PSU02 in communication subracks 560CSR01:
One of the two power supply units has failed
064 - x. Cmd. supervision circuit disconnected or faulty Error in the check circuit x of a Command Supervision
095 1 ≤ x ≤ 32 Board 23BA22 (1 … 16 devices)
096 (s)ntp client 1 is synchronized The first (s)ntp client is synchronized by a server
097 (s)ntp client 2 is synchronized The second (s)ntp client is synchronized by a server
100 Command authority ‘LOCAL’ Integrated HMI has requested command authority. If
‘Interlock with local control authority’ is enabled,
commands from a NCC are rejected for this line
101-116 Host x Online, 1 ≤ x ≤ 16 NCC connection to Host 1 … 16 established
117-132 Host x: Information loss due to queue overflow, Queue overflow for host communication queue to host
1 ≤ x ≤ 16 x. Process data is stored in local data base.
133-148 Host x: Information loss due to ITI queue overflow, Queue overflow for ITI host communication queue to
1 ≤ x ≤ 16 host x. Intermediate reading values (IR) are
superseded if possible, or Process data is stored in
local data base.
149-156 Communication unit x in communication-subrack A communication unit (CMU) is inoperable.
560CSR01 #0 is inoperable. 1 ≤ x ≤ 8 For redundant communication units (CMU) only:
157-164 Communication unit x in communication-subrack The system has switched to the other communication
560CSR01 #1 is inoperable. 1 ≤ x ≤ 8 unit of the redundant pair.
174 Data base version Date and Time of actual configuration file
180-183 Device reachable on redundant line x, 1 ≤ x ≤ 4 For redundant subdevice communication lines only:
a communication line can be used for communication
184-187 Device active on redundant line x, 1 ≤ x ≤ 4 For redundant subdevice communication lines only:
a communication line is used for communication.
Set by ‘System Command’ #008 to 011
(see also chapter 16.2)
188-191 Device preferred on redundant line x, 1 ≤ x ≤ 4 For redundant subdevice communication lines only:
Line should be used as preferred line.
Set by ‘System Command’ #004 to #007
(see also chapter 0)
192-223 Network element no. x is operable. 1 ≤ x ≤ 32 For snmp (Simple Network Management Protocol)
only: Actual state of the network elements x.
224-231 Communication unit x in communication-subrack A communication unit (CMU) is active.
560CSR01 #0 is active, 1 ≤ x ≤ 8 For redundant communication units (CMU) only:
232-239 Communication unit x in communication-subrack The state of the standby-unit is shown in ‘System
560CSR01 #1 is active, 1 ≤ x ≤ 8 Event’ #149 to 164.
16-2 1KGT 150 589 V000 1 ABB AG

Remote Terminal Unit RTU560 System Data Interface
16.2 System Commands
The behavior of subordinated devices connected to a subdevice communication interface

can be influenced by System Commands
This table shows the System Commands (SSC = System Single Command).
The columns have the following meaning:
• SSC address
System Command Address
• System Command
Meaning of the System Command
SSC System Command Remark

address
001 Set device out of service (For redundant subdevice communication lines only:)
ON: Set device out of service
OFF: Set device in service
The result is reflected in ‘System Event’ #049
002 Reset device process ON: Reset subdevice
003 Connect device For dial-up subdevice connections only:
ON: Establish a dial-up connection
OFF: Disconnect the dial-up connection
The result is reflected in the ‘System Event’ #045
004 Set redundant line 1 as preferred line For redundant subdevice communication lines only:
005 Set redundant line 2 as preferred line ON: Line x is the preferred line for communication.
006 Set redundant line 3 as preferred line Another line is used only in case of a failure.
007 Set redundant line 4 as preferred line The result is reflected in the ‘System Events’ #188 to
#191 (see also chapter 16.1).
008 Set redundant line 1 as active line For redundant subdevice communication lines only:
009 Set redundant line 2 as active line ON: Line x is the active line for communication.
010 Set redundant line 3 as active line The result is reflected in the ‘System Events’ #184 to
011 Set redundant line 4 as active line #187 (see also chapter 16.1)
016 … Switch over to redundant CMU in rack #0, slot x The (redundant) communication unit in slot x of the
023 1≤x≤8 communication subrack 560CSR01 y will become the
024 … Switch over to redundant CMU in rack #1, slot x active communication unit in the configuration
031 1≤x≤8
ABB AG 1KGT 150 589 V000 1 16-3

System Data Interface Remote Terminal Unit RTU560
ABB AG
Power Technologies Division
Power Technology Systems
Kallstadter Str. 1,
D 68309 Mannheim
Phone +49 (0) 621 381 – 7592

Fax +49 (0) 621 381 – 7622
www.abb.com/pt Subject to alterations
16-4 1KGT 150 589 V000 1 ABB AG

E560 FD Release 9 0 PDF

Uploaded by

Copyright:

Available Formats

E560 FD Release 9 0 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

E560 FD Release 9 0 PDF

Uploaded by

Copyright:

Available Formats

RTU560

Remote Terminal Unit

Function Description Release 9.0

This manual describes the functions provided by the

Document identity: 1KGT 150 589 V000 1

Revision: 0 Date: 01/2008

ABB AG 1KGT 150 589 V000 1 1-1

FUNCTION DESCRIPTION RELEASE 9.0 .............................................. 1-1

1 ABOUT THE RTU560 FUNCTION DESCRIPTION ............................ 1-1

1 THE RTU560 FAMILY ........................................................................ 1-1

2 SCADA MONITORING DIRECTION .................................................. 2-1

ABB AG 1KGT 150 589 V000 1 1-1

2.4 Bit-string Input Value Processing ................................................................... 2-25

3 SCADA COMMAND DIRECTION ...................................................... 3-1

4 REDUNDANCY .................................................................................. 4-1

1-2 1KGT 150 589 V000 1 ABB AG

5 HOST COMMUNICATION INTERFACE ............................................ 5-1

6 SUB-DEVICE COMMUNICATION INTERFACE ................................ 6-1

7 IEC61850 STATION COMPUTER ...................................................... 7-1

8 INTERFACES AND NETWORK ......................................................... 8-1

9 PROGRAMMABLE LOGIC CONTROL (PLC) ................................... 9-1

ABB AG 1KGT 150 589 V000 1 1-3

10 LOCAL PRINT AND PROCESS ARCHIVE FUNCTION.................. 10-1

11 DISTURBANCE DATA FILE ARCHIVE........................................... 11-1

12 TRANSMISSION AND STORAGE OF METER DATA .................... 12-1

1-4 1KGT 150 589 V000 1 ABB AG

13 INTEGRATED HMI ........................................................................... 13-1

14 STARTUP, CONFIGURATION, TIME MANAGEMENT ................... 14-1

ABB AG 1KGT 150 589 V000 1 1-5

15 STATUS AND DIAGNOSTIC INFORMATION................................. 15-1

16 SYSTEM DATA INTERFACE .......................................................... 16-1

1-6 1KGT 150 589 V000 1 ABB AG

AMI Analog Measured value Input

ASO Analog Setpoint command Output

BCU Bus Connection Unit

BSI Bit String Input (8, 16 bit)

CMU Communication and Data Processing Unit

CSC Command Supervision Channel

CS-Command Clock Synch Command

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 (1bit)

GCD General Configuration Data

HCI Host Communication Interface

IED Intelligent Electronic Device

IOC I/O Controller (Controller on I/O Board)

IOD Input Output Data

IOM I/O Bus Master (Function of SLC)

ITI Integrated Totals Input

MFI Analog Measured value Floating Input

MPU Main Processing Unit

NCC Network Control Center

ABB AG 1KGT 150 589 V000 1 1-1

PBP Peripheral Bus Processor

PDP Process Data Processing

PLC Programmable Logic Control

PPP Point to Point Protocol