RTUtil560 Users Guide R8

RTU560
Remote Terminal Unit
RTUtil560 User's Guide Release 8

Preliminary Version
Revision
Document identity: 1KGT 150 451 V005 1
Revision: 0 Date: May 2000

Basic document
Revision: 1 Date: October 2000
Excel import and PLC
Revision: 2 Date: March 2001
PLC functions
Revision: 3 Date: Mai 2001
Installation, Directory structure,
Initialization Excel, interface wizard
Revision: 4–5 <skipped>
Revision: 6 Date: December 2004
Document updated according to FW Release 6
New chapter ‘Data Interface Excel Export’ added
Revision: 7 Date: March 2006
Document updated according to FW Release 6/7
Chapter ‘Data Interface Excel Export’ extended
Revision: 8 Date: April 2006
Document updated according to FW Release 8
New chapter ‘IEC61850 Engineering’ added
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 © 2006 ABB AG Mannheim/Germany
ABB AG 1KGT 150 451 V008 1 Preliminary Version I

RTU560 RTUtil560 User’s Guide Contents
Contents
Revision ..................................................................................................... I
Getting started...........................................................................................1
RTUtil560 ........................................................................................................................... 1
System requirements ........................................................................................................... 1
Installation........................................................................................................................... 2
Getting Help on RTUtil560................................................................................................. 2
General Overview......................................................................................3
RTUtil560 Structure............................................................................................................ 3
General Data Structuring and View .................................................................................... 4
General Tree Structure ........................................................................................................ 5
Data Engineering Concept .......................................................................7
The Tree Functionalities ...........................................................................9

The Trees............................................................................................................................. 9
Network Tree ...................................................................................................................... 9
Engineering Functions in Network Tree ............................................................... 9
Network Tree Structure....................................................................................... 10
Actions in Network Tree..................................................................................... 10
Links and Link Actions in Network Tree ........................................................... 10
Signal Tree ........................................................................................................................ 11
Engineering Functions in Signal Tree................................................................. 11
Signal Tree Structure .......................................................................................... 11
Actions in Signal Tree ........................................................................................ 11
Links and Link actions in Signal Tree ................................................................ 12
Hardware Tree................................................................................................................... 12
Engineering Functions in Hardware Tree ........................................................... 12
Hardware Tree Structure..................................................................................... 12
Actions in Hardware Tree................................................................................... 12
Links and Link Actions in Hardware Tree.......................................................... 13
Parameter in Hardware Tree ............................................................................... 13
User Interface ..........................................................................................15

RTUtil560 User Interface.................................................................................................. 15
RTUtil560 Workspace ...................................................................................................... 16
Data Presentation Windows .............................................................................................. 17
Tree Window ...................................................................................................... 17
Tree View ........................................................................................................... 17
Parameter View................................................................................................... 19
Data Point View.................................................................................................. 20
ABB AG 1KGT 150 451 V008 1 Preliminary Version I

Contents RTU560 RTUtil560 User's Guide
Moving in Trees, Selecting Items .......................................................... 21
Edit Functions......................................................................................... 23
Add - Delete - Copy - Link Actions ..................................................................................23
Add Item............................................................................................................................23
Delete Item (Branch) .........................................................................................................24
Copy/Paste Item (Branch) .................................................................................................25
Link Item ...........................................................................................................................26
Link Item ...........................................................................................................................26
Project Functions ................................................................................... 27

Project Settings..................................................................................................................27
Check Plausibility..............................................................................................................28
Build the RTU Files ..........................................................................................................30
File Generating Steps ..........................................................................................30
The RTU-Files ....................................................................................................31
Extra Functions ...................................................................................... 33

Extract the RTU files.........................................................................................................33
Data Interface - Excel Import ............................................................................................34
Data Interface – Excel Export ...........................................................................................38
Data Interface – MULTIPROG wt Export ........................................................................41
Extra – Open MULTIPROG wt.........................................................................................43
Extra – Start MS_DOS batch file ......................................................................................43
Extra – SCD Import...........................................................................................................43
Extra – Language...............................................................................................................44
Extra - Options ..................................................................................................................44
Excel Interface ........................................................................................ 45

Excel Import Introduction .................................................................................................45
Excel Import Overview .....................................................................................................45
RTUtil560 Project Pattern File ..........................................................................................47
Excel files and sheets.........................................................................................................47
Contents of Excel File and Sheets.......................................................................47
Excel Sheet Types ...............................................................................................51
General Hints for Columns and Rows.................................................................52
Excel Sheet Functions .........................................................................................53
Excel sheet structure ...........................................................................................55
Excel interface initialization wizard ..................................................................................61
Steps of the initialization wizard.........................................................................61
Start the Excel Interface initialization wizard .....................................................62
Select the Excel file of the RTU (Step 1/5).........................................................63
Assign the RTU's Excel sheets (Step 2/5) ...........................................................64
Assign Address Parameter (Step 3/5)..................................................................65
Assign the Process Object Identification (Step 4/5)............................................67
Check the General and PDP Parameters (Step 5/5).............................................68
Performing the Excel Import .............................................................................................69
Excel Import Error Handling...............................................................................69
List of Errors and Warnings during Excel Import...............................................70
Invariant Excel Column Names.........................................................................................72
II 1KGT 150 451 V008 1 Preliminary Version ABB AG

RTU560 RTUtil560 User’s Guide Contents
IEC61850 Engineering ............................................................................75

RTU560 in an IEC61850 system ...................................................................................... 75
Engineering Process .......................................................................................................... 76
Network and Hardware tree .............................................................................................. 78
Excel Import File............................................................................................................... 79
SCD File Import................................................................................................................ 81
User Interface .................................................................................................................... 83
Directory Structure .................................................................................85

Relative Directory ............................................................................................................. 85
Sub Directories.................................................................................................................. 85
Engineering Example..............................................................................87
Process Control System..................................................................................................... 87
RTU Configuration ........................................................................................................... 88
Initialize Project.................................................................................................. 88
Initialize Signal Tree........................................................................................... 89
Build the Network Tree ...................................................................................... 90
Build the Signal Tree .......................................................................................... 90
Build the Hardware Tree..................................................................................... 91
Configuration Files ............................................................................................. 93
Configfile Download .......................................................................................... 93
ABB AG 1KGT 150 451 V008 1 Preliminary Version III

RTU560 RTUtil560 User's Guide Getting started
Getting started
RTUtil560
The basic topics of RTUtil560 are:
• Configuration and data engineering tool for RTU560 projects
• The principles of user interface structuring according to IEC 1346-1
• MS Windows 2000 / XP Professional
• The User Interface of RTUtil560 is an application based on the
Microsoft standard presentation format
• Documentation of all project steps
• External data interface concept
• Multilingual tool (user interface and help files)
• Delivery version with setup, installation and uninstallation program on
CD-ROM
System requirements
The performance requirements for the data engineering tool RTUtil560, particularly
the free disc space depends on the project size. Basic requirements are:
• Operating system: MS Windows 2000 / XP Professional
• Memory: 64 MB RAM
• Processor: Pentium class
• Hard disc: > 200MB free disc space
• Hard lock: dongle (parallel or USB port) for MULTIPROG wt export
ABB AG 1KGT 150 451 V008 1 Preliminary Version 1

Getting started RTU560 RTUtil560 User's Guide
Installation
RTUtil560 is distributed as CD-ROM version and is developed for the Windows
NT 4.0 operating system. Next to the RTUtil560 setup program there are additional
software components on the CD. For installation of the complete RTU engineering
platform (containing also the communication between PC and RTU) see also the
documentation "RTU560 Web Server User's Guide".
Usually the configuration menu starts automatically after insert the CD to the drive.
To start this menu manually, insert the CD to the drive, select the root directory and
start „RTUtil.exe“.
To install only RTUtil560 manually, call the setup program from the distributed
media. If CD drive is „D:\“, the directory to start „setup.exe“ is
„D:\Program\RTUtil560“.
After starting the setup program follow the steps of the installation dialogs:
1. Acknowledge welcome page

2. Select the program path, where the files should be installed
3. Select the program group of RTUtil560
4. Start copying of the files to the local hard disc
The setup program will copy all the files needed from CD to your local disc. Also
all required registry entries are done by the setup program.
To use all features of RTUtil560 a dongle is needed.
Getting Help on RTUtil560

Applications written for Windows usually provide context sensitive Help, allowing
the user to get help on a particular window, dialog box, command or toolbar button.
RTUtil560 provides this help for the user as text messages shown in the status bar
and tool tips. Tool tips are the tiny popup windows that present short descriptions of
a toolbar button’s purpose when the user positions the mouse on a button for some
time. RTUtil560 provides all these features in the language chosen by the user.
Example of a Tool Tip
2 1KGT 150 451 V008 1 Preliminary Version ABB AG

RTU560 RTUtil560 User's Guide General Overview
General Overview
RTUtil560 Structure
RTUtil560 enables the user to control the whole engineering process of an RTU
based system. All configuration data is managed from RTUtil560. To do so several
functional concepts for data storage, structuring and presentation are needed.
To meet the requirements the internal software structure of RTUtil560 is split up
into different function parts as shown in the figure below.
RTUtil 560
User Plausibility Excel Excel PLC

Interface Check Import Export Interface
(UI) (PC) (EI) (EE) (PI)
Database (DB)
Overview RTUtil560 Components

General Overview RTU560 RTUtil560 User's Guide
General Data Structuring and View

The general view of the user to the engineering data is implemented on the basis of
international Standard IEC 1346-1. This Standard describes the structuring
principles and reference designations for industrial systems, installations and
equipment.
In the user interface this standard is presented in trees showing the RTU from
different points of view. To describe the whole process the view is split up into
three trees. IEC 1346-1 defines how to split up a system (function-, product- and
location-oriented structure).
The user interface structure offers three trees to describe the system structure
usually used for an RTU.
• Network Tree
The Network Tree shows the lines and protocols for routing the data
points through the network.
• Signal Tree
In the Signal Tree the location and designation of signals is shown.
The signal location describes the place of the data points in the
primary process.
• Hardware Tree
The Hardware Tree present 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.

RTU560 RTUtil560 User's Guide General Overview
General Tree Structure

The following example shows the implementation of structuring principles
according to IEC 1346-1. In the picture Network - RTU - Process the project views
down to the RTU internal configuration are shown. This is only a small example of
an RTU network. RTU 01 is the concentrator station in this network. The right side
of the picture presents the electrical process (one bay in a station, with the double
point indication Q0). This scenario will be built up in the three trees: Network Tree,
Signal Tree and Hardware Tree.
04 Plant Ladenburg 110kV

CS 1 CS 2
Line 2 Line 2
Line 1
Line 1
Rack TP 1, Segment 1 Rack TP 2, Segmen
RTU 01 Com Subrack 560CSR01
23 NG 23 560SLI01 560SLI01
Tx Rx C E Tx Rx C E
5V 1 1
Line 3 Line 4 24V 2
A
MMI
1
2
A2
MMI
1
2
UP BA BA
Q0
On
B B
O ff
RTU 11 RTU 21 Peripherie Bus Line, Segment 1

Rack TP 1, Segment 2 Rack TP 2, Segment 2
Line 3
SPAx 1 Line 4
RTU 12
Line 5
Peripherie Bus Line, Segment 2
SPAx 2
SPAx 2 21.03 MW
Network - RTU - Process
The root node of a tree is similar to the tree type (e. g. Signal Tree, Hardware Tree).
The Network Tree is the representation of the network structure. The concentrator
RTU 01 is chosen as root node in the Network Tree, because the concentrator RTU
is normally a unique starting point in an RTU station network. The hosts (central
systems) are represented below the root RTU.
In Signal Tree the structuring of the electrical process and the naming of the single
point indication is made. The name for every data point is derived from the structure
of the electrical process.
Some nodes have different presentation locations (references) in several trees.
These nodes are the line and station nodes from the Network Tree and the data point
nodes from the Signal Tree. The line and station nodes have references in the
Hardware Tree and in the Network Tree. The data point nodes have references in
the Hardware Tree and in the Signal Tree.
The Hardware Tree describes the internal structure of the station nodes (e. g. RTU
01). The RTU and Line node types in Hardware Tree are linked nodes from the
Network Tree. The double point indication Q0 in the electrical process is linked
from the Signal Tree to a binary input board in the Hardware Tree.

RTU560 RTUtil560 User's Guide Data Engineering Concept
Data Engineering Concept
The engineering of RTU560 data contains several dependency steps, that demand a
sequence in the data engineering process. To understand the engineering steps see
also chapter "Engineering Example".
The basic data engineering steps are:
1. Project configuration (start)
Set the project environment data.
Before building the trees the Signal Tree structure has to be defined
(number of levels and naming of these levels).
2. Build up the tree structures
Build up the station network topology in the Network Tree. Choose
the lines and the communication protocols between the stations. The
Network Tree is needed 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 (ObjID) for every 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 with cabinet, racks and boards. To build
up the Hardware Tree the standard data entry functions or data
import functionality could be used.
The link steps in the Hardware Tree build up the relations between the
trees.
Link data definition sources (e. g. RTU stations and IEDs) and Line
nodes from the Network Tree to the Hardware Tree.
Link all the data points (e. g. single and double indications) from
Signal Tree to the IO-boards of the Hardware Tree. To speed up data
point linking more than one data point can be linked to a board in one
step
While adding or linking new data points to 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.

Data Engineering Concept RTU560 RTUtil560 User's Guide
3. Set parameters, addresses

Set the addresses for the process data points
Set single parameters for several tree objects.
4. Start the plausibility check.
5. Build the RTU-files for each RTU.
During the whole engineering process RTUtil560 supports the user to avoid data
inconsistencies. The basic functions that support the user during the engineering
process are:
• Avoiding to build up a wrong tree
• Check ranges for each parameter
• Check dependencies between the tree nodes
• Check dependencies between parameters
• Check the complete plausibility of a project before generating the RTU-files

RTU560 RTUtil560 User's Guide The Tree Functionalities
The Tree Functionalities
The Trees
The special concepts for the different trees are based on the general presentation
format and the general functions like add, copy, link and delete items.
The presentation of the engineering data in different tree structures results in a
complete new engineering process concept. General rules as described in the data
engineering concept are required to build up a project and use the powerful
functionality of the trees.
Network Tree
The Network Tree enables the user to build up the whole RTU station network
topology and to handle the connectivity data, the protocol parameters, and the filter
functionality of a project. To do so several functionalities are required. The user has
to be supported by a set of functions and dialogs to entry the data for build up the
Network Tree.
The Network Tree gives no information about the RTU's internal network. The
station network, which is build up with the Network Tree, is clearly distinguished
from the RTU's internal network, which is described in Hardware Tree. The
Network Tree gives an overview of a complete station network. The internal
structure of an RTU is built up in the Hardware Tree. All information about the
connection between racks, the I/O bus network and the system bus configuration is
part of the Hardware Tree.
Engineering Functions in Network Tree

• Build up station network topology
• Set protocols to line objects
• Route data points through the station network (this function can be
launched from several engineering steps, see detailed actions
description)
• Set filter functions for the data points

The Tree Functionalities RTU560 RTUtil560 User's Guide
Network Tree Structure

The two standard tree node types to build up the Network Tree are the station and
the line nodes. E. g. station nodes are like RTU stations, network control center
(NCC) or IEDs (e. g. SPA). From the users point of view some of the station nodes
are only data sources (like IEDs), others are data consumers like the network
control center and some could be both data sources and hosts.
With these two element types the complete station network topology could built up
in the Network Tree. The starting point for the Network Tree is the "node RTU" in a
station network. The node RTU is the root node for the station network. More than
one node RTU is possible but not common.
Via the host interface of an RTU several central systems could be connected. The
assignment of board interface and line will be done in the Hardware Tree. The
Network Tree only represents the general topology and connection of stations.
The sub interface allows connecting sub stations and IEDs. The hardware board
with the interface also depends on the RTU type. The assignment will also be done
in the Hardware Tree.
Actions in Network Tree

The Network Tree data entry is performed by the general functions (add, copy, link
and delete nodes). In addition to this functions special views to the data points are
needed, to select filter functionalities for data points.
To add the station and line nodes in the Network Tree the Add Item... function is
normally used. It is also possible to link an existing station from Hardware Tree to
the Network Tree. By adding several stations and connecting them with lines, the
station network topology is build up.
To choose a protocol for a line element, select the line object. Next to the tree
window the parameter window (parameter pane) for the line object appears. Choose
the protocol type for the line selected in this window.
To launch automatic protocol routing take the following steps. Add a new data point
to an RTU in Hardware Tree. Add a new line to an RTU in Network Tree. Then the
protocol routing for all data points of this line is carried out.
Links and Link Actions in Network Tree

Links in the Network Tree are made to the Hardware Tree, when the hardware
configuration data of an RTU is entered. The usual way is to build up the network
topology in the Network Tree and link the nodes to the Hardware Tree.
See the Network Tree as an overview of the complete station network and the
Hardware Tree as a list of data sources for this network. All tree nodes except the
Central System node have to be linked to the Hardware Tree.
First link all data sources (RTUs and IEDs) to the Hardware Tree. Afterwards the
hardware structure has to be built, to link the lines to the RTUs communication
interface boards (e. g. serial line interface). To assist the user in these link actions
RTUtil560 gives information in the Link Item... dialog, which elements from the
Network Tree have to be linked to the Hardware Tree.
The user can get this information from the Link Item... dialog. In the Link Item...
dialog a list of nodes that can be linked to the selected node and aren't linked to that
node yet is presented. So, if the user selects the Hardware Tree root node and calls
the link node dialog, he will get information about the not linked station nodes from
Network Tree.

Signal Tree
The Signal Tree is built up to guarantee a unique object identifier for each data
point in a system. The structure of the Signal Tree depends on the project. The
specific signal structure is defined at the beginning of a project. The Signal Tree
gives an overview of the amount of IO-data in a RTUtil560 project.
Engineering Functions in Signal Tree

• Build up the process structure. Set the number of levels and their
naming.
• Give an unique identifier to every data point in the system.
Signal Tree Structure

The Signal Tree structure is project dependent. The Signal Tree mirrors the location
of the data points in the process. The user has to build up the structure, dependent
on his own process structure, of the Signal Tree at the beginning of a project. At the
beginning of a project the user determines the number of levels in this tree and their
meaning. This settings cannot be changed during the project any more.
The length of the data point name is configurable between 1 and 128 character. The
maximum length of the unique object identifier is 32 character, and may start with a
configurable position within the character string.
The goal of the Signal Tree is to get a unique object identifier for every data point in
a system. For an electrical distribution process the structure could be as shown here.
Level Description Number of Identifier

Characters (example)
1. Area 3 E2_
2. Station 6 MANNH_
3. Bay 6 TRAN10
4. ./. 17 Q0
Actions in Signal Tree

When building up a user dependent structure of the Signal Tree the user is assisted
by a dialog, where the number of levels for the Signal Tree can be selected and the
types of these levels can be specified. With this dialog the project dependent
process structure is built up. The dialog to build up the Signal Tree structure is part
of the "Project Wizard", which appears when launching a new project.
To insert the tree levels and the data points to the Signal Tree, the common action
functions like Add Item... and Link Item... are used.
An other common way to build up the Signal Tree structure is to import all the data
from given lists. In this case the data has to be available in a common format like
Excel sheets and the Signal Tree structure has to be adapted to the data structure.

The Tree Functionalities RTU560 RTUtil560 User's Guide
Links and Link actions in Signal Tree

The function of the Signal Tree is to provide a unique object ID for a data point.
Having obtained this object ID the user links the data points from Signal Tree to the
appropriate board in the Hardware Tree (e. g. a single point indication to a binary
input board).
The linking of data points from Signal Tree to Hardware Tree connects a data point
to its data source (RTU, IED, etc.). During this process and with a correctly built of
the Network Tree the automatic protocol routing action is triggered by the linking of
a data point.
To support the user RTUtil560 gives information which elements from the Signal
Tree have to be linked to the Hardware Tree and which boards are required to link
the data.
Hardware Tree
The structure of the RTU hardware is built up in the Hardware Tree. This tree gives
information about the internal structure of an RTU. The communication structure of
an RTU and the IO-hardware needed for the data points shall be distinguished.
The structuring gives the user the possibility to get an overview of the whole RTU
and enables the user to locate every data point in the station. All configuration data
which is needed for a single RTU is presented in the Hardware Tree.
Engineering Functions in Hardware Tree

• Build up RTU's internal hardware structure.
• Build up the RTU's communication structure: internal RTU network
with communication boards, I/O bus, system bus, ...
• Build up IO-hardware: add data points (DPs) to the RTU or link them
from Signal Tree.
Hardware Tree Structure

The Hardware Tree structure is the hierarchical structure of the RTU. It starts with
the RTU as one unit and includes the levels: cabinet, rack, board, interfaces and data
points. Next to the tree nodes the parameter panes have the specific data entry
controls needed to parameterize the nodes.
Actions in Hardware Tree

The general actions Link Item... and Add Item... are used to build up the
Hardware Tree. The Hardware Tree can be built up separated (stand alone) from the
Network Tree and Signal Tree. For small projects with only one RTU and less data
points no Signal Tree is needed.
To use the functionality of Network Tree and Signal Tree (automatic signal routing
and unique object-ID) it is recommended to build these trees first, and link their
data to the Hardware Tree.

Links and Link Actions in Hardware Tree

The Signal Tree and the Network Tree are the data sources to build up the Hardware
Tree. The Network Tree determines the dependencies of the communication. The
Signal Tree defines the IO-data. The following engineering steps shall be
distinguished: the communication data is built up first and then the IO-data.
The RTUs and lines are linked from Network Tree to Hardware Tree. The other
direction is in some cases possible too. It is important to use the same station in the
Network Tree and the Hardware Tree.
The links from Network Tree have to be performed before linking the IO-data to the
Hardware Tree, because the automatic signal routing goes through the station
network. Automatic signal routing will be successful only if the communication
hardware is complete.
Linking data points from Signal Tree to Hardware Tree will start the automatic
signal routing, if the communication structure for an RTU is complete. The data
points get the unique object ID from the Signal Tree. To speed up data point linking
from Signal Tree to Hardware Tree a special link mechanism to link more than one
data point is available.
Parameter in Hardware Tree

There is a parameter concept for every tree node . In the Hardware Tree for several
nodes there is an extended parameter concept.
RTU Segment (only RTU560):
The segment is an internal RTU structuring principle. For the RTU560 it is possible
to set up 1-4 segments, each including 1-6 extension racks.
To build several segments for one RTU, different I/O bus lines have to be connected
to a Serial Line Interface board (SLI) or to an Ethernet Adapter board (ETH). An
interface of one of these communication boards shall be assigned to one segment.
There may be up to four segments. The I/O bus is able to connect six extension
racks to one segment.

RTU560 RTUtil560 User's Guide User Interface
User Interface
RTUtil560 User Interface

The new tool for the RTU is a standard Windows application (Win32 application).
The mainframe window includes all the views to the project data. Look and feel of
the application's mainframe are known from other Win32 applications. Standard
windows control mechanisms are used whenever it was feasible and useful, so that
the user needs less time to start projects with the new tool.
The context help functionality is based on Tool Tips and allows context sensitive
help support.
The general data view and structuring supports the common engineering sequence.
A user interface that contains all functionalities is the basis for the RTU
configuration and the whole engineering process. The user interface includes the
presentation objects and views for structured data presentation according to IEC
1346-1.
This chapter gives an overview to the User Interface presentation format. The main
windows of RTUtil560 and the general tree structures will be shown in this chapter.
Also an overview to the menus in RTUtil560 will be given.

User Interface RTU560 RTUtil560 User's Guide
RTUtil560 Workspace
The RTUtil560 workspace is a frame for a standard windows application. Where it
is feasible common windows controls are used. The functionality will be completed
by special functions required to configure an RTU.
The figure RTUtil560 Workspace gives an overview about the general construction of
the User Interface of RTUtil560. The several parts and their structure will be part of
the following chapters.
The Menu of the RTUtil560 User Interface enables the user to select all functions,
which are needed to configure an RTU. A shorter way to activate the same
functions, which are available in the menus, is to select them directly with a
Toolbar button.
The Tree Windows allows the view to the several trees of an RTU project. There
is a view to the Network Tree, to the Hardware Tree and to the Signal Tree
available. Several tree windows may be open at the same time.
Main window Menu bar Tool bar Tree window
Statusbar Tree view pane Parameter view pane
RTUtil560 Workspace

Data Presentation Windows

The general structure of data presentation format following IEC 1346-1 is
implemented in the different tree views. They are used building up the structure to
configure RTUs, their signals, the station network up to the central system and the
automation functions. The data in these structures is in hierarchical order, so that it
is easy to present the items in a tree. The different views are: Signal Tree,
Hardware Tree and Network Tree.
Next to the general tree windows there are list windows to support data entry
functions. For data input and presentation there are different mechanisms to realize.
Tree Window
The views in an RTUtil560 project mirrors the two general engineering steps. The
first step is to build up the general data structure, the second is to parameterize the
data. Between these two steps there are some automatisms from RTUtil560. By this
general separation the working window is split into two parts called panes. These
two panes supports the common engineering steps:
1. Build up the structure of project data in trees - Tree View (left side)
2. Enter the properties and parameter to the nodes - Parameter View
(right side)
Tree Window
Tree View
In the left pane of a tree presentation window one of the tree views is shown. The
user is able to open several windows with the same tree view or with different tree
views. This functionality enables the user to show links between trees, copy item
groups and find nodes.
The presentation style for every tree node gives the basic information that a user
needs to identify the node. The structure of the general node presentation is:

• Image for node type

• Local Type (alternatively)
• Item Type
• Item Name
Image:
Is an icon for the node type, e. g. an icon showing a „board“ or „rack“. Icons are
used for easy identification of elements, so that the localization of a tree node is no
problem.
Local Type:
The local type can be seen as predefinition for a node and gives information about
the location of a node. It is used to limit the kind of types and number of nodes that
can be added as children to an existing node. E. g. a „560CSR01“ node have a local
type „Slot 10_P1“ where only the „Power supply unit board - 560PSU01“ node can
be added.
The local type is a tree dependent part of the node presentation. This means, that
there can be different local types for one node. This behavior is only important for
the linked node types like data points and line nodes. The data points normally have
an local type in the Hardware Tree presentation. E. g. a single indication in
Hardware Tree have a local type which describes if the data point is an input or an
output. In the Signal Tree the local type of the Hardware Tree is not part of the
presentation format for the same node.
Item Type:
The node type specify the behavior of a tree node. The node type is normally hard
coded with an internal type ID. The user only sees the short description for a node
type in the tree view. E. g. "SPI" for a single indication.
For some items that don’t have a specific behavior and only are structuring help
nodes, like the items in Signal Tree, it is possible to change the node type text. E. g.
the default text of the level nodes ("Area", "Plant") in Signal Tree will be defined at
the beginning of a new project.
Item Name:
The item name is an identifier for the tree items. Not all items in a tree could have a
name. Names can be given to several node types.
For data points the name could be a structured object identifier that is used in an
external interface. To support structured naming special functionality is added in
Signal Tree. The name for data point items can divided in an auto naming part and
a freely chosen part. The auto naming part is given from the Signal Tree structure
and cannot be influenced directly. The path of the Signal Tree gives the identifier
for a the tree node, e. g. a single indication have a unique identifier from Signal
Tree path, like „E_1_110KV_0101“. The free part is a name for the tree item
chosen by the user. Both name parts together have to be a unique identifier for a
data point.

Parameter View
The right pane is in the Tree Window is the Parameter View. The general data entry
forms give information about the properties and actual parameters of a node.
Dependent on item type and its localization in the tree, the dialog changes the
presentation form. For easy node parameter handling, the dialog has a common
structure for every node.
General page for a tree node
The presentation form is a property sheet. The first site for every tree item shows
General properties, like icon, item type and name. So there is a general view to get
information of every item.
The other property pages actually available for the user depend on the parameters
of an item. Normally there is one page for a group of parameters (e. g. process
parameters PDP, protocol parameters Line... , etc.).

Data Point View

The view over all data points is available for one of the RTUs, IEDs and Lines
selected in the Network Tree. An other way is to select one of the RTUs or IEDs in
the Network Tree and listen the data points from this view.
The Data Point List will be presented with the following dialogs:
1. by menu, View/Data Point List
2. by tool bar, click the symbol

RTU560 RTUtil560 User's Guide Moving in Trees, Selecting Items
Moving in Trees, Selecting Items
To build up the data in trees there are rules how to move in the trees, input new
nodes and change their parameters.
There are two fundamental differences in user control regarding the selection of an
item in the tree. There is a very easy way with standard mouse control for users
working the first time with RTUtil560. And there is control over all functions and
moves with the keyboard, so that a person who is familiar with RTUtil560 can work
very efficiently. Every function can be executed either with the mouse or the
keyboard. In the following table the controls to move in the tree, select an item and
switching between the two panes of working window are described.
Action Mouse Keyboard

Open branch • double click the item • arrow key right
• click the „+“ in front of
the item
Close branch • double click the item • arrow key left
• click the „-“ in front of
the item
select item • click item • move to the next item
in the tree with the
arrow keys up and
down
• use page up and down
for a faster move

RTU560 RTUtil560 User's Guide Edit Functions
Edit Functions
Add - Delete - Copy - Link Actions

The tree actions are the basic functionality's to build up every tree structure. The
general functions are Add, Delete , Copy & Paste and Link an Item. These
functionalities can be launched by several mechanisms described in the following
chapters.
Add Item
To add items to a tree, the user has to select an item in one of the tree view panes.
Then he can choose the start level for data entry. After this the Add Item... dialog
for the selected node can be launched. There are four common ways, known from
windows standard applications to get the dialog.
1. by menu, Edit/Add Item...
2. by tool bar, click

3. by shortcut keys CTRL+A
4. with the right mouse button Pop Up Menu, with the mouse click the
right button, a pop up menu appears, select Add Item...
In the dialog the user can enter all the data one level below the selected tree node.
The selected node is the parent node for the new entries. The add node dialog
presents a list of possible child node types. The list of child node types depends on
the parent node type and the actual structure.
After entering one item there is the chance to add the same node by clicking the
Add button with the mouse or push the return key. The written item will be inserted
in the tree structure. The dialog stay active at the selected hierarchical level. To stop
data entry push the Done button. The dialog will cancel and the control return to
the tree.
While the Add Item... dialog is open the user is able to move in the Tree View
pane of the Tree Window. The dialog will change the format dependent on the
selected node in the Tree View pane.

Edit Functions RTU560 RTUtil560 User's Guide
Add Item dialog
Delete Item (Branch)

To Delete a node or a branch the user has to select a tree node or a group of tree
nodes and call the delete item mechanism by one of the following ways:
1. by menu, Edit/Delete Item...
2. by tool bar,
3. by Shortcut key DEL
4. by Pop Up Menu, with the mouse click the right button, a pop up
menu appears, select Delete Item...
After selecting an item and calling the Delete Node function, a popup window
appears and the user will be asked, if he is sure he wants to delete the selected item.
If he presses the Yes button the item will be deleted. If the selected tree node has
child items a second popup window appears and asks for confirmation to delete the
whole Branch.

RTU560 RTUtil560 User's Guide Edit Functions
Copy/Paste Item (Branch)

Copying nodes, branches and groups of items is an essential function to save time
by doing same things only once. The copy concept of RTUtil560 gives the user a
powerful function for data engineering. A basic rule is that the user is supported by
indications from RTUtil560 during copying.
While copying a node only data is copied (no links will copy). There are no hidden
functionalities and no automatisms are triggered, like it is the case when linking
nodes between the trees.
If the node has child nodes, the complete branch will be copied.
The Copy/Paste action could be launched in several ways:
1. by menu, first Copy the item to the clipboard, than Paste it to the
target, Edit/Copy Item, Edit/Paste
2. by tool bar, first Copy the item to the clipboard, than Paste it to the
target,
3. by Shortcut keys, first Copy the item to the clipboard, than Paste it to
the target, CTRL+C, CTRL+V
4. by Pop Up Menu, select item, with the mouse click the right button, a
pop up menu appears, select Copy Item to copy the item to the
clipboard, than Paste it to the target
5. by Drag & Drop, select the node with the mouse, keep left mouse
button pressed, drag the item to the target, release the mouse button to
drop the item. This is the Drag & Drop method.
The drag & drop functionality is the same as in standard Windows tools like the file
Explorer.
If the node is copied via drag & drop functionality, only the Drop dialog appears,
if the detailed position of the node is required (if a local type has to be chosen).

Edit Functions RTU560 RTUtil560 User's Guide
Link Item
Link Items in different trees in several places is one of the basics of structuring the
configuration following IEC 1346-1. So this function has to be used in every
project. Some nodes of the project have to be inserted several times in different
trees. These nodes are the station nodes (RTUs and IEDs), the line nodes and all
data point nodes.
After the given engineering example the station and line nodes will be linked from
the Network Tree to the Hardware Tree. The data point nodes will have to be linked
from the Signal Tree to the Hardware Tree.
The Link Action could be launched in several ways:
1. by menu, Edit/Link Item...
2. by tool bar,
3. by shortcut keys, CTRL+L
4. by Pop Up Menu, select item, with the mouse click the right button, a
pop up menu appears, select Link Item...
5. by Drag & Drop, select the node with the mouse, keep left mouse
button pressed, drag the item to the target, press STRG + SHIFT to
force link item, drop the item on the target
The selected item is the target node of the link action. To select the node that should
be linked to the target node, the Link Item... dialog appears. In the drop down list
of the edit control all the nodes that can be linked to the selected target node appear.
The user has to choose a node of this list. To link the chosen node to the selected
node target press the Link button.
If the node will be linked via drag & drop functionality, the Link Item dialog only
appears, if the detailed position of the node is required (if a local type is there).
Link item dialog
After linking an item a small yellow circle on the icon of the item informs the user
that the item is already linked.
Line icon before linking
Line icon after linking, marked with a red circle

RTU560 RTUtil560 User's Guide Project Functions
Project Functions
Project Settings
The Project Settings dialog presents with the tab for "Initialize Project" the
general information of the project. With the tab "Initialize Signal Tree" the defined
data point structure for the project will be reported.
To get the Project Settings dialog by menu, select Project/Settings...
Project Settings Dialog

Project Functions RTU560 RTUtil560 User's Guide
Check Plausibility
Before starting the generation of the loadable files, a plausibility check of the
data is recommended.
Start plausibility check:
1. by menu, Project/Check Plausibility...
Concern Check E W I
All Object ID number (OBJ IDNR) has to be unequivocal.
objects No duplicate entries allowed. X
All Object ID string (OBJ ID) has to be unequivocal. No
objects duplicate entries allowed. X
All References has to be unequal to zero. X
objects
Rack Address (RACK ADDRESS and RACK PLACE) has
to be unequivocal. No duplicate entries allowed. X
Com- Address (SLOT ADDRESS and RACK ADDRESS)
board has to be unequivocal. No duplicate entries allowed. X
If a comboard is configured as ACTIVE within
redundancy mode, a comboard of the same board type X
has to be configured as STANDBY and vice versa.
(same number of same board types with same
redundancy mode within an redundant system).
Only one master is allowed within an redundant
system. (one master STANDBY and one master X
ACTIVE).
If a comboard is configured as NON REDUNDANT
and MASTER, no other comboard as MASTER
within the RTU is allowed. Further no comboard X
configured as ACTIVE or STANDBY is allowed.
At least one master has to be available. X
Supply- Address (SEGMENT ADDRESS, RACK ADDRESS X
board and SLOT ADDRESS) has to be unequivocal. No
duplicate entries allowed.
Activity HOSTACTIVITY NUMBER has to be unequivocal.
- HOST No duplicate entries allowed. X
- SUB SUBACTIVITY NUMBER has to be unequivocal. No
duplicate entries allowed. X
Interface IP ADDRESS has to be unequal to zero. X
- ETH
Line SEGMENT ADDRESS has to be unequivocal. No
- PB duplicate entries allowed. X
At the moment COM A is only allowed to be linked to
I/O bus 1 and 3 and COM B is only allowed to be X
linked to I/O bus 2 and 4.
Each configured I/O bus has to be linked to a rack. X
IOBoard Address (SEGMENT ADDRESS, RACK ADDRESS
and SLOT ADDRESS) has to be unequivocal. No X
duplicate entries allowed.
- BA22 Maximum 16 BA22 allowed. X
- BA20/22 BA20 and BA22 has to be handled by the same PDV X
activity.
- BA20/22 An RCO command is not allowed to be switched by a

channel, which is supervised by means of a check X

circuit.
- BA20/22 An SCO persistent command is not allowed to be
switched by a channel, which is supervised by means X
of a check circuit.
Datapoint Address (SEGMENT ADDRESS, RACK ADDRESS,
SLOT ADDRESS and CHANNEL) has to be X
unequivocal. No duplicate entries allowed.
Information Object Address has to be unequivocal.
(within an info type and one ASDU address). Only for X
101 and 104.
Information Object Address for a data point has to be
equal for different lines (e.g. 101 and 104 host lines) X
Protocol DNP3: After the address of an DPI one X
address must not be occupied.
- SCO Persistent output only with BA20 1 pole allowed. X
- DCO Persistent output only with BA20 1 pole allowed. X
- CSC Check circuit number (CSC NUMBER) has to be
unequivocal. No duplicate entries allowed. X
- CSC The value for high resistance of the relay coil has to be
greater than the value for the low resistance. X
- CSC BA20 1 pole and 2 pole are not allowed to be handled X
within one check circuit.
E = Error
W = Warning
I = Information

Project Functions RTU560 RTUtil560 User's Guide
Build the RTU Files

Start the generation of the RTU files:
1. by menu, Project/Build RTU file...
File Generating Steps

1. On the first page select the RTU from the project.
First page of the Build RTU file dialog
2. Choose a file name for the RTU files. Give the name for the IOD file,
but all files will be generated (gcd, ios and oad). If the option Save
information into.... is ON, the whole project is saved ( I/O data with
all project information, see chapter ‘Extract the RTU files’). If the
option is OFF only the I/O data will be stored in the I/O file.
3. Click on Next button

Second page of the Build RTU file dialog
4. To start generation of RTU files immediately click the option Check

Plausibility... to Off. The text of the Next button will be changed to
Generate File. Click this button to start file generation.
Note: The Check Plausibility is recommended before starting file
generation. This function can also started independent from the Build
RTU file dialog. Therefore see the chapter Check Plausibility.
5. Acknowledge the indication that the files have been generated and
abort the dialog with Cancel.
The RTU-Files
The GCD-File (General Configuration Data) contains all the information to
establish the communication. The items of the GCD-File are:
• Project information
• The RTU node with parameters and offset address of the system event
block
• Cabinet nodes
• Rack nodes with address and I/O bus connection
• Supply boards
• Communication boards with all parameter entries for the interfaces
• Line nodes with protocol specific parameters
• Sub- and Host station I/O devices with offset address of the system
event block
The IOD-File (Input Output Data) contains the complete information about the data
points and their parameters:
• I/O devices of type I/O board
• Process data points with all parameters (PDP, protocol addresses)

RTU560 RTUtil560 User's Guide Extra Functions
Extra Functions
Extract the RTU files

RTUtil560 is able to read a RTU file *.IOD from the subdirectory ...\rtufile or
any other user defined directory. RTUtil560 separates the project information
from this file, if the switch ‘Save information into RTU file for extracting a
whole project’ was enabled. The project information will be stored on the
subdirectory ...\proj with the original file name or with a new name defined by
the user.
Start Extract RTU file...:
1. by menu, Extra/Extract RTU file.....
The standard dialog asks the user for subdirectory name and file name.

Extra Functions RTU560 RTUtil560 User's Guide
Data Interface - Excel Import

The RTUtil560 Excel data interface enables the user to use Excel sheets to
manage RTU data. The interface imports data points to a given hardware
template (pattern file).
To do so, in a first step the hardware of the RTU is built up with the RTUtil560
and saved in the pattern directory. This project can be seen as a pattern project
for several Excel import files. The Excel import defines the process data points
for the given hardware.
Start Excel Import:
1. by menu, Extra/Excel Import.....

Steps of RTUtil560 Excel Import:
1. Start RTUtil560 Excel Import function from the menu or with the
toolbar button.
2. Select a pattern file and click on the Next button
Select Pattern

3. Select an RTU from the pattern file and click on the Next button
Select RTU
4. Select the Excel import file and click on the Next button, to
select the Excel import files.
Select Export File
5. Select the sheets of the Excel file, that shall be imported

Select Excel sheets
Before the import is started, the previous selections are displayed. Click on
Start button.
Summary
6. After Excel import is done the last page with a success indication
occurs. Chose file name and check if the project should be opened
by finishing the dialog.

Save Project
For a detailed error detection see the directory of the Excel file.
There are two files:
• The error report file (*.log), which contains written information
about errors occurred during the import.
• The extension file (*.err) is an Excel file. For an easy error location
the fields where the errors occurred are marked red.

Data Interface – Excel Export

Parameters included in the Pattern-File of a configuration (global data) and all
process data parameters can be exported to Excel Worksheets by using the Excel
Export function. The Excel Export is done into predefined Excel files (pattern
files) , available in the subdirectory \patterns:
• …..\patterns\ExcelExportPD.xls for process data
• …..\patterns\ExcelExport.xls for global data
The Excel Export is started in the Dialogue Extras -> Excel Export.
The first step (1) is to define the pattern file for the process data, which is
normally fixed.
Define the path for the pattern for process data
In the next step (2) the path- and file name for the output file for process data has to be
defined. The number of row for the first entry should be at least 6.
Define the path- and file name for the output file for process data

The next step (3) is to define the RTU node to be exported.
Define the RTU node to be exported
Now repeat step 1 and 2 for the sheets for global data and start the export function.
The result of the Excel Export for global data is a file containing three
worksheets
• Station Parameter Global parameter for all RTU’s
• Line Parameter Parameter for all communication lines
• Hardware Parameter Hardware parameter of all RTU’s
It is not possible to re-import these two sheets into RTUtil560 again.
The Excel-Export worksheets for the process data parameter have the same style
as the Excel-Import worksheets, and can be re-imported again.
Example for the Excel Export of global data

Example 1 for process data
Example 2 for process data

Data Interface – MULTIPROG wt Export

The PLC information of a RTUtil560 project have to be exported in a project file
with the extension “*.mwt”.
Select the menu entry “MULTIPROG wt Export...” of the menu bar element
“Extras“ in RTUtil560. The MULTIPROG wt Export wizard starts.
MULTIPROG wt Export menu entry
You can also use the toolbar icon.
The following dialog asks for RTUtil560 project name. You can use the active
project or any other project.
Select RTUtil560 project
Select one of the options. If an other RTUtil560 project should be selected give
the path and the project name and select the project with the extension “*.rtu”.
Click the Next button.

The following dialog asks for the MULTIPROG wt project.
Select MULTIPROG wt project
You can build a new MULTIPROG wt project and export into this project or you
can select an existing project for the export. The extension of the
MULTIPROG wt project is “*.mwt“.
Now click the Start button and the export function runs and presents the
following result dialog.
Finished MULTIPROG wt export
The last dialog shows the result of the MULTIPROG wt export. The export can
be successful or maybe was aborted. If it was aborted an error description
appears. When “Open project in MULTIPROG wt“ is selected the
MUTLTIPROG wt project will be open after clicking the Finish button.

Extra – Open MULTIPROG wt

Starts RTU560's PLC programming and test tool MULTIPROG wt.
Related toolbar icon to start MULTIPROG wt:
Extra – Start MS_DOS batch file

Starts – if present in the RTUtil560 program directory path's subfolder \batch –
after reply for batch processing parameters, the DOS batch file
RTUtil560_Batch.bat.
Related toolbar icon to start the batch job:
Extra – SCD Import

This function is in RTUtil560 the starting point for the engineering of an
IEC61850 sub device communication interface. The detailed description of the
IEC61850 engineering process could be found below in the chapter “IEC61850
Engineering”.

Extra – Language
In this dialog, the language of RTUtil560's user interface is selected. The
selection takes effect after restart of RTUtil560.
RTUtil560 menu item: Extra/Language...
Language Dialog
Extra - Options
Change the saving directories for Project Files and RTU-Files. The path
where Microsoft Access is installed an the path for MULTIPROG wt projects
can be changed in this dialog, too.
Get the general options dialog from menu Extra/Options..
General options dialog

RTU560 RTUtil560 User's Guide Excel Interface
Excel Interface
Excel Import Introduction

Excel is a suitable and often used tool for the definition and documentation of
engineering data.
RTUtil560 provides an Excel interface to import the RTU relevant engineering data
from Excel sheets. To allow adaptations to specific customer or project
requirements, the structure of the Excel sheets used for data import is as free as
possible.
Following chapters describe
• the structure of the Excel files and sheets
• how to use the Excel interface initialization wizard
• steps in Performing the Excel Import
Excel Import Overview

The Excel import uses the Excel file(s) together with an RTUtil560 project pattern:
Sequence of an Excel import

Excel Interface RTU560 RTUtil560 User's Guide
The Excel file(s) contains information for

the project Signal Tree (signal names structured according to the project
settings of the project pattern)
the data object's hardware assignment to RTU I/O points resp. IEDs
the data object's processing parameters
communication protocol message addresses and parameters of each data object
for all levels of the Network Tree
The project pattern has to contain

the complete Network Tree (including all links to the Hardware Tree)
the Hardware Tree down to RTU560 board level resp. IED level (without I/O
signal definitions and assignments)
of the RTUtil560 project to which data object information shall be imported.
Steps to perform an Excel import are:

1. build the RTUtil560 project pattern
(example provided within the RTUtil560 directory path \patterns:
'Excel Import.RTU')
2. adapt the provided exemplary Excel sheet (RTUtil560 directory path
\xls_import: 'Excel Import.xls') to your project requirements
3. fill in all the information to be imported to the RTUtil560 project in the Excel
sheet
4. initialize the Excel interface (RTUtil560 tree 'Project - Settings')
- the RTUtil560 project pattern and the Excel file must exist at this point!
5. perform the Excel import (RTUtil560 tree 'Extra – Excel Import')
The initialization information is saved to the RTUtil560 pattern file and in the final
RTUtil560 project file after successfully performed Excel import.

RTUtil560 Project Pattern File

For the Excel Import, an RTUtil560 project pattern file has to exist.
The project pattern is a normal RTUtil560 project that has to contain all engineering
information, except
the data object definitions in the Hardware Tree for local I/O signals and I/O
signals of the IEDs
data object related processing parameters
communication protocol identifications / addresses and related data object
parameters
i.e. the pattern project has to contain

• the complete Network Tree
the Hardware Tree down to RTU560 board level resp. IED level (without I/O
signal assignment) including all links to the Network Tree
• all project settings and parameters not related to I/O signals
Excel files and sheets

RTUtil560 provides an exemplary Excel file 'Excel Import.xls', that should be used
as basis for project specific Excel sheets.
Contents of Excel File and Sheets

For each RTU560 of an RTUtil560 project, a separate Excel file which contains at
least one sheet has to be provided.
Sheets within the Excel file

For each subordinated IED line (a line that connects directly to IEDs, not to lower
level RTU560s), one sheet has to be added. If the RTU has two subordinated IED
lines, the excel file consists of three sheets: one sheet for the RTU's local I/O and
one for each subordinated line.
Sheet contents
Each data point with all its processing parameters and related communication
addresses on all higher level lines of the Network Tree is specified in only one sheet
of the set of Excel files and sheets belonging to a RTUtil560 project. This
specification has to take place in the relevant Excel sheet (Local I/O or IED line) of
the Excel file that belongs to the lowest level RTU560. For each higher level line of
the network tree, a protocol specific address / host parameter block has to be added
to the sheet where the data point is defined.

Example 1: CS - RTU - Sub-RTU

The following network topology needs two Excel files:
Control System
CS
IEC870-5-104
RTU 1
IEC 870-5-101
RTU 2
(sub RTU)
Network Topology with CS - RTU1 - SubRTU2
Excel files: two files RTU 1 and RTU 2:
RTU 1: one sheet with

• IEC 870-5-104 block
• local I/O data point parameter block (RTU)
RTU 2: one sheet with

• IEC 870-5-104 block
• IEC 870-5-101 block

Example 2: CS - RTU - IED

The following network topology needs one Excel file:
Control System
CS
IEC870-5-104
RTU 1
IEC 870-5-101
n* IED
Network Topology with CS - RTU1 - n*IED
Excel files: one file – RTU 1

RTU 1: two sheets
Sheet 1: with the RTU 1 local I/O data points
• IEC 870-5-104 block
Sheet 2: with the IED data points
• IEC 870-5-104 block
• IEC 870-5-101 block
• IED data point parameter block (IEC 870-5-101)

Example 3: CS1 - CS2 - RTU - Sub-RTU - IEDs

The following network topology needs two Excel files:
Control System Control System

CS 1 CS 2
IEC870-5-104 IEC870-5-101
RTU 1
IEC 870-5-103 IEC 870-5-101
n* IED RTU 2
IEC 870-5-101
IEC 870-5-103
n* IED n* IED
Network Topology with CS1,CS2 - RTU 1 - RTU2 - n*IED
Excel files: two files – RTU 1, RTU 2

RTU 1: two sheets
• IEC 870-5-104 block (CS 1)
• IEC 870-5-101 block (CS 2)
Sheet 2: with the IED data points
• IEC 870-5-104 block (CS 1)
• IEC 870-5-101 block (CS 2)
• IEC 870-5-103 block (RTU 1)
• IED data point parameter block (IEC 870-5-103)
RTU 2: three sheets
• IEC 870-5-104 block (CS 1)
• IEC 870-5-101 block (CS 2)
• IEC 870-5-101 block (RTU 1)

Sheet 2: with IED data points from the IEDs connected to the IEC 870-5-101 line
• IEC 870-5-104 block (CS 1)
• IEC 870-5-101 block (CS 2)
• IEC 870-5-101 block (RTU 1)
• IEC 870-5-101 block (RTU 2)
• IED Data point parameter block (IEC 870-5-101)
Sheet 3: with IED data points from the IEDs connected with IEC 870-5-103 line
• IEC 870-5-104 block (CS 1)
• IEC 870-5-101 block (CS 2)
• IEC 870-5-101 block (RTU 1)
• IEC 870-5-103 block (RTU 2)
• IED Data point parameter block (IEC 870-5-103)
Excel Sheet Types

To import data definitions related to an RTU's local I/O or related to subordinated
IED lines, two types of Excel sheet column structures are used.
Excel Sheet for RTUs (Local I/O)

Column blocks:
• Signal (Signal type and RTUtil560 import flag)
• Process Object Identification
• RTU hardware address
• address / host parameter blocks
• data point parameter block (type specific)
Excel Sheet for subordinated IED lines

The IED data point parameter blocks depend on the protocol of the subordinated
line the IED is connected to. Each protocol type has an individual data point
parameter block structure.
The subordinated line sheet has no hardware address block. It consists of the
following column blocks:
• Signal (Signal type and RTUtil560 import flag)
• IED-Name
• address / host parameter blocks
• IED line address / sub parameter block

General Hints for Columns and Rows
Unique Column Name

Each column from which data has to be imported to an RTUtil560 project pattern
must have a unique identifier. All identifiers of one sheet must be in the same row,
typically this is one of the first rows of a sheet (column 5 in the exemplary Excel
file, shaded in gray color). The row number of the column identifiers may differ
from sheet to sheet.
With this identifier the import is managed. Changing the identifier names is allowed
only for communication line blocks. Changing the identifier names is mandatory if
a line is duplicated. The user has to take care that all identifier names used in one
RTUtil560 project are unique.
Columns that shall not be imported into the RTUtil560 project do not need to get an
identifier name.
Rows per Data Point

Within the exemplary sheet, the number of rows provided for each local process I/O
signal depends on the signal type and accords with the number of hardware I/O
terminals occupied by the signal. The number of rows for each signal may be
adapted to project specific requirements (1 to n rows), but it must be guaranteed that
only one row of the rows belonging to one and the same signal is allowed to get the
'Y' flag set in the STIM column which flags the signals as to be imported in the
RTUtil560 project.
Default number of rows for local I/O data objects is ‘1’, and may be set according to
the data point type:
Data point Rows

AMI 2
ASO 2
BSI8 8
BSI16 16
BSO1 1
BSO2 2
BSO8 8
BSO16 16
DCO 2
DMI8 8
DMI16 16
DPI 2
DSO8 8
DSO16 16
EPI 1
ITI 1
MFI 2
RCO 2
SCO 1
SPI 1
STI 8

Extendibility of Excel Sheet

To adapt the exemplary Excel sheet to project requirements, the following changes
are allowed:
The columns can be changed in any order. Necessary address/host parameter blocks
can be added, those not used may be deleted. The data point parameter blocks of
data points, that are not used can be deleted.
To add other information, e.g. marshalling information to the Excel sheet, any
column at any position can be added.
When the Excel sheet once was initialized and columns used for import to
RTUtil560 are changed (deleted, new ones added, column identifiers renamed),
the Excel interface has to be re-initialized. This is not necessary when the order
of the columns has been changed.
Excel Sheet Functions

The exemplary Excel sheet has some functions that facilitate working with the
Excel sheet.
Drop-down List of Predefined Values

Cells with allowed values from a value list have a drop-down value list from which
a value has to be selected. For the drop-down list a basic Excel function is used.
The drop down list is defined in the first value row and has to be copied to all
following rows.
Value drop-down list

Range Supervision
Cells where a number in a defined range is expected have got a range supervision.
For this purpose a basic Excel function is used (data validation).
Like the drop down list it is defined in the first row where a data point can be
defined. To all following rows it has to be copied.
Range Supervision
Description of the Cell Meaning

Most of the cells of the exemplary Excel sheet which contain the unique column
names have a description of their meaning. The description is displayed when the
cell is active. For this feature a basic Excel function is used ('Data' – 'Validation' –
'Input Message').
Excel problem:
The description is not displayed if the unique column name cell is in the frozen pane
range of the sheet (Excel: 'Window' – 'Freeze / Unfreeze Panes').
Cell Description

The description contains the name of the column, type, range and default value of
the parameter.
Within the Excel sheets following data input types are used:
♦ value list
♦ number with specified range
♦ Yes/No selection
♦ character string of specified maximum length
Excel sheet structure
Blocks of the Excel Sheet

The information of the sheets is arranged in logical blocks:
• Signal
• RTU Hardware Address
• Address / Host parameter blocks
• Address/ Sub parameter blocks (only in subordinated line sheets)
• Data Point Parameter blocks (only in the local I/O sheet)
The address/host parameter and address/sub parameter block is specific for each
protocol type. The data point parameter block is point type specific.
Excel Sheet Block for Signal Types

Specifies the data point type and a flag which marks the data point for import to
RTUtil560.
Signal block

Excel Sheet Block for Process Object Identification

The process object identification specifies the signal name of the data point. The
length of the name is limited to 32 (128) characters. The structure of the signal
name can be defined individually per project.
Example of a Process Object Identification
In the exemplary Excel sheet the name is structured in four elements (Station /
Subnet / Bay / SCADA object) with a maximum length of eight characters for each
of them.. The name of the data point shown in the figure above which is imported to
the RTUtil560 Signal Tree is “RTUNAME LADENBG TEST007 AMI“:
A correct import of structured signal names to the RTUtil560 Signal Tree is

achieved only, if the Signal Tree structure elements defined after opening a new
RTUtil560 project (the project pattern) have exactly the same text length as the
Process Object Identification elements in the Excel import sheets.
It is strictly recommended that the object identification structure used in the
! Excel sheet is exactly the same as the Signal Tree structure defined for the
RTUtil560 project pattern.

Excel Sheet Block for RTU Hardware Address

The hardware address of a local I/O data point is specified in the RTU hardware
address block.
The hardware address consists of:
• I/O bus segment
• Rack address
• Slot address
• Channel within board
In addition, the data object qualifier "Blocked" is specified in the hardware address
block.
RTU Hardware Address

Excel Sheet Block for Line Address and Host Parameters

Each protocol type has a specific structure of the address / host parameter block.
The following blocks exist in the exemplary Excel file:
• IEC 870-5-104 Address / Host parameter

• IEC 870-5-101 Address / Host parameter
• Modbus Address / Host parameter
• RP570/71 Address / Host parameter
• DNP 3.0 Address / Host parameter
• DNP 3.0 LAN/WAN Address / Host parameter
• Indactic 33 Address / Host parameter
• Indactic 35 Address / Host parameter
• TG809 Address / Host parameter
• Sinaut 8-FW Address / Host parameter
• Conitel 300 Address / Host parameter
• Hitachi 300 Address / Host parameter
For each new protocol that is integrated in RTUtil560, an exemplary block for this
protocol is added to the exemplary Excel sheet.
Following section of an Excel sheet shows an example of an IEC 870-5-104 address

/ host parameter block. In this example, the rows contain the standard message
address elements in a 1:1 manner – i.e. the input has to take place as one number for
each standard address element.
Example of an IEC 870-5-104 Address / Host parameter block
If the message address elements of communication protocols shall be engineered in

a structured manner (possible with the IEC 60870-5-101 and –104 protocols), the
structure elements and bit sizes should be defined in an early stage of a customer
project, i.e. before creating the project pattern and the Excel sheets. The standard
protocol message address elements may be structured in a free manner on bit limits.
This means, that for example a 16 bit ASDU Address may be structured in two
elements, occupying 7 and 9 bits. The address elements are then input as two
numbers with value ranges of 0...127 resp. 0...1023 (see following example).

Note, that restrictions in the possible ranges as with following example (e.g. 1...127)
are not checked when the Excel import is performed. If those restrictions are
specified in a customer project, the user has to take care for correct data entry.
Structured IEC 870-5-104 addresses
The Excel sheet must have as many address/host parameter blocks as corresponds to
the number of communication lines a message passes from the lowest level
RTU560 up to a top level end node of the network tree (normally a Network
Control System).
Care must be taken to get unique column identifiers over all address/host parameter
blocks, see chapter General Hints for Columns and Rows. If the address/host
parameter block columns are copied from the exemplary Excel file, it is
recommended to increase the first numeric value (second character) of the column
name or to substitute the first two characters with a unique identification string of
the specific line.

Excel Sheet Block for local Data Point Parameters

Each data point type has it’s own specific parameter block.
The following data point types are available in monitoring direction:

• Single Point Input (SPI)
• Double Point Input (DPI)
• Integrated Totals Input (ITI)
• Step Position Input (STI)
• Analog Measured value Input (AMI)
• Bit String Input (BSI8 / BSI16)
• Digital Measured value Input (DMI8 / DMI16)
Data points types in command direction:

• Single Command Output (SCO)
• Double Command Output (DCO)
• Regulation step Command Output (RCO)
• Analog Setpoint Output (ASO)
• Digital Setpoint Output (DSO8 / DSO16)
• Bit String Output (BSO1 / BSO2 / BSO8 / BSO16)
As an example, the parameter block for analog measured value inputs (AMI) is
shown in following section of an Excel sheet.
Note, that the column identifiers of the data point parameter blocks must not be
changed!
Analog Measured Value Input (AMI) Parameter

Excel interface initialization wizard

With the Excel interface initialization wizard, the Excel interface can be adapted to
your project requirements. The interface must be initialized for each RTUtil560
project pattern. By this way it is possible to adapt the Excel sheet exactly to your
project requirements.
Steps of the initialization wizard
Start
Project->Settings->
Initialize Excel interface
Step 1/5
Select the Excel files of

the RTU.
Step 2/5
Assign the Excel sheets.
Step 3/5
Assign the address, host

and sub parameters
for every host/sub line

for each RTU to
be initialized Step 4/5
Assign the Process

Object Identification
Step 5/5
Check the general and

PDP parameter s
Steps of the Excel interface initialization wizard

The initialization wizard leads through the five main steps of the Excel interface
initialization. Except step three, every step is represented by one dialogue page. In
step three there are as many pages as lines are used in the import. The wizard has to
be passed through for every RTU of an RTUtil560 project.
Start the Excel Interface initialization wizard

Click in RTUtil560's menu bar on – Project - Settings
Now you are in the project settings window where you can see three folders. Chose
the folder Initialize Excel Interface:
Project settings initialize Excel Interface

The status of the active RTUtil560 project's Excel interface initialization is shown.

In the dialog all RTUs of the project have an own entry line with a colored spot at
the beginning of each RTU entry. A red spot identifies those RTUs for which the
Excel interface is not yet initialized, a green spot indicates that an RTU has the
Excel interface initialized.
If an RTU Excel interface once is initialized the spot always will remain green.
It will not change to red anymore even if the Excel file for this RTU is modified
or changed.
Select your RTU for which the Excel interface shall be initialized. Selection of
more than one RTU is possible using the Windows standard mechanisms for multi
selection (Shift resp. Ctrl key pressed + left Mouse click).
With the “Start Initialization” button the initialize wizard of the Excel interface is
started for the first of the selected RTUs.
Select the Excel file of the RTU (Step 1/5)

For each of the selected RTUs an Excel file with the import information has to
exist. In the dialog the Excel file name for the according RTU has to be specified.
The name of the RTU to be processed is displayed on top of the dialog.
Select Excel file of the RTU

As default excel file name the RTU name with the extension 'xls' is used.
Going to the next dialog the import Excel file is opened, so that you can have a look
on it during the following dialogs.

Assign the RTU's Excel sheets (Step 2/5)

In this dialog the Excel sheets of the specified Excel file are assigned to the RTU's
local I/O (presented with the RTU name) and to the IED lines connected to this
RTU in the Network Tree.
Assign Excel sheets

In the rightmost area of the window, the "Column ID row" can be changed, if the
row number of the unique column identifiers of the sheet is not the fifth row as with
the exemplary Excel file
If data points for a specific IED line defined in the project pattern shall not be
imported for this RTU, you have to select "not used" for this IED sub line.
! For this reason it is not allowed to give an Excel sheet the name "not used"!
After assignment of all Excel sheets whose data shall be imported, press Next to go
to the next dialog folder.

Assign Address Parameter (Step 3/5)

This dialog has to be stepped through for each host communication line and for
each IED line to which an Excel sheet had been assigned in the previous dialog. For
all RTUtil560 parameters that shall be imported to this RTU, the according
references for the respective unique column identifiers have to be assigned in
selecting the according identifier names from the drop down lists.
Assign host address and parameters
Each column in the Excel sheets has a unique default name, which may be used
during initialization (Set default names for Excel columns). In order to distinguish
between the different lines within a configuration, the first n character of the default
names have to be set individually.
Set default names for columns

When using structured addresses (possible with IEC 870-5-101 and –104 lines), the
order of the entries is important: The least significant structure element of an
! address has to be assigned in the first row, the most significant structure element in
the last row of consecutive rows of the dialog box.
Example:
Structured addresses – IEC 870-5-104 line parameter settings in the project pattern

Assign the Process Object Identification (Step 4/5)

If the assignment for all communication lines is finished, the window for the
assignment of the Process Object Identification elements from the Excel sheets to
signal name elements of the active project is displayed:
Process Object Identification

The references are automatically inserted. Please check the column identifiers and
string lengths for correctness and do corrections if necessary.

Check the General and PDP Parameters (Step 5/5)

Now you get a check box where you should find all items marked as 'OK'. If there
are errors listed with one or more items, go back to the corresponding dialog and
check your assignments resp. the Excel sheets' column identifiers for correctness.
Check general and PDP parameter
To finish the initialization of the Excel interface for this RTU, press the Finish
button and the dialog will go back to the Project Settings window where the
processed RTU now has got a green spot.
You may now continue with the other RTUs of your project or start the Excel
import for the RTU with the now initialized Excel interface.
If you have to do changes resp. additions in the configuration or the column
naming, the initialization of the Excel import for this RTU can be processed again
to do the relevant additions or re-definitions.

Performing the Excel Import

The Excel import is started from the RTUtil560 Extra – Excel Import menu. A
wizard guides through the dialogs and asks for the necessary settings. The wizard is
described within chapter Data Interface - Excel Import of this document.
Excel Import Error Handling

During the Excel import a log file and an Excel error file are created in the original
Excel file's directory path. These files get the same file name as the imported Excel
file, file extensions '.log' resp. '.err'.
Errors and warnings detected during the Excel import are written to the log-file.
Cells with erroneous contents are marked red (error), those ones containing values
which might be incorrect are marked yellow (warning) in the sheets of the Excel
error file. With the information from these two files, errors can be located and
corrected in a comfortable manner.
Following table lists all errors checked for during the Excel import and the
according error handling (result).
Error Result
Column for a data point parameter The corresponding data point value is set to
missing the default value for all imported data points
Protocol address missing RTUtil560 automatically assigns an address
to the concerned data object *
Process Object Identification missing The data point won’t be imported into the
Signal Tree
Process Object Identification already The existing data point with the Object
exists Identification will be deleted
RTU hardware address missing The data point won’t be imported into the
Hardware Tree
Hardware address already used The existing data point (with the hardware
address) will be deleted from the hardware
(will not be deleted in the Signal Tree)
Hardware address does not exist The data point will not be imported into the
Hardware Tree
Data point parameter entry missing The parameter will be set to the default value
Data point parameter out of range The parameter will be set to the default value
* The automatic address assignment may use addresses that are assigned to other
data objects within the Excel sheet. There is no guarantee that the automatic
address assignment will result in unique and unambiguous addresses. If this
feature is used, the user is responsible to check the overall address consistency.

List of Errors and Warnings during Excel Import
Error Error Text Error

ID Type
28000 database opening failed Err/Abo
28004 value no string where string is expected Err
28005 cannot find a defined Excel column in the Excel sheet Warn
28006 unknown type of the process data Err
28007 the Object ID is not defined Err
28008 number expected - no value defined or value not a number Err
28012 address value out of range (too high) Err
28014 cannot read the value Err
28016 process data object does not correspond to the type of I/O Err
board or to the channel I/O number
28026 no correspondence in Excel sheet '%s' and Access table Err
'%s'.
28027 this row with the unique column name in the Excel sheet is Err/Abo
not defined or the value is below 1. The entry is in the MS
Access data base table '%s'.
28031 The string for the definition of %i is missing Warn
28032 the break condition for a definition of (%i) or for a string (%s) Err
not found up to this field
28033 floating number expected; no value or value is not a floating Err
number
28034 the value is missing Warn
28035 Definition of the 'yes' value is missing. It has to be defined in Warn
the Excel sheet 'Defines'. The default value 'Yes' is used.
28036 Definition of the 'no' value is missing. It has to be defined in Warn
the Excel sheet 'Defines'. The default value 'No' is taken.
28037 an error occurred reading a yes/no value - reenter the value Err
28038 yes or no expected where the value is not yes or no Err
28039 'Object Identification' missing, data point cannot be imported Err
28040 Entry of the string '%s' in the Access database table Warn
'z_tbl_Excel_String_To_ID' missing. The string is used for
the assignment of the Excel columns to the data point
parameter entries within RTUtil560.
28041 The line '%s' defined in the MS Access assignment table Err
'z_tbl_Excel_Assignment_Line' does not exist in the project.
28043 The 'Hardware address' I/O bus %i, Rack address %i, Slot Err
address % i, Channel %i does not exist in the project
pattern. The data point is not imported to the Hardware Tree.
28044 The data point cannot be added to the project Err
28045 The value is not allowed or not defined in the Excel sheet Err
'Defines'.
28046 The value is above the allowed maximum value (allowed Err
range: %i .. %i).
28047 The value is below the allowed minimum value (allowed Err
range: %i .. %i).
28048 The given sheet type '%s' in the column '%s' of the MS Err
Access table '%s' is unknown.
28050 The IED is not present in the Hardware Tree of the project. Err
28051 The value is above the allowed maximum value (allowed Err
range: %.1f .. %.1f).
28052 The value is below the allowed minimum value (allowed Err
range: %.1f .. %.1f).
28053 There is no data point with this 'Process Object Identification' Err
28054 The data point with this 'Process Object Identification' is of Err
wrong type. Type has to be SPI or DPI
28055 'Persistent output' not allowed - 23BA20 not a one pole type Err
28056 Column with these numbers from the Excel sheet 'Defines' Err/Abo
not present in Access table 'z_tbl_Excel_Number_Of_Rows'.
28057 Column with this string from the Excel sheet 'Defines' not Err/Abo
present in Access table 'z_tbl_Excel_Number_Of_Rows'.
28058 RTU for Excel import not found in the Network Tree. Err
28059 No definition found for the general table in Access table Err
'z_tbl_excel_assignment_PDP'.

28060 No definition found for the Excel column 'RTUtil560 Import'. Err
Entry in Access table 'z_tbl_Excel_Assignment_PDP' is
missing or wrong or the column does not exist in the Excel
table.
28061 No definition found for the Excel column 'Signal Type'. Entry Err
in Access table 'z_tbl_Excel_Assignment_PDP' is missing or
wrong or the column does not exist in the Excel sheet.
28062 No definition found for the Excel column 'Intelligent Err
electronic device name (IED)'. Entry in Access table
'z_tbl_Excel_Assignment_PDP' is missing, or the entry is
wrong, or the column does not exist in the Excel sheet.
28063 No definition found for the Excel column 'PB-Segment'. Entry Err
in the Access table 'z_tbl_Excel_Assignment_PDP' is
missing, or the entry is wrong, or the column does not exist
in the Excel sheet.
28064 No definition found for Excel column 'I/O Subrack Address'. Err
Entry in the Access table 'z_tbl_Excel_Assignment_PDP' is
in the Excel sheet.
28065 No definition found for Excel column 'Slot Address'. Entry in Err
Access table 'z_tbl_Excel_Assignment_PDP' is missing, or
the entry is wrong, or the column does not exist in the Excel
sheet.
28066 No definition found for the Excel column 'Channel within Err
Board'. Entry in Access table 'z_tbl_Excel_Assignment_PDP'
is missing, or the entry is wrong, or the column does not
exist in the Excel sheet.
28067 No definition found for the column 'Process Object Err
Identification' Entry in table 'z_tbl_Excel_Assignment_Line' is
in the Excel sheet.
28068 Address in the RTUtil560 project missing for the data point in Warn
row:
28069 length of an element of the 'Process Object Identification' Err
cannot be zero or less. It i given in the Access table
'z_tbl_Excel_Assignment_Line'.
28070 The definition for the data point '%s' in the Access database Err
table 'z_tbl_Excel_String_To_ID' is missing. The string is
used for the assignment of the Excel columns to the data
point parameter entries in the RTUtil560.
28071 There is no SOC with the given name Err
28072 The Excel error file (*.err) cannot be stored on disk. Access Err
was denied.
28502 The number of rows the data point '%s' uses is not given in Warn
the Access table 'z_tbl_Excel_Number_Of_Rows'.
28504 A data point with the given 'Process Object Identification' Warn
exists. The existing data point was replaced
28505 The hardware address already exist. The existing data point Warn
was removed from the hardware.
Note:
%s – replaced by a string
%i – replaced by an integer number
%f – replaced by a float number
Err = Error
Err/Abo = Error, Excel import aborted
Warn = Warning

Invariant Excel Column Names
Parameter Unique Excel column name

General parameters
Signal type STTY
RTUtil560 import STIM
IED name (not mandatory) IEDN
PB segment (only Local I/O) RUPB
I/O subrack address RURC
Slot address RUSL
Channel within board RUCH
Blocked RUBL
AMI PDP parameter
Input signal range AMRA
Input signal type AMTY
Conversion factor AMCO
Line frequency AMFR
Smoothing AMSM
Acquisition mode AMTR
Periodic update (RTU DB) AMSC
Threshold AMTH
BSI PDP parameter
Consistency check time BSCO
Digital filter BSFI
DMI PDP parameter
Value presentation DMPR
Input signal type DMTY
Maximum value (100%) DMMA
Consistency check time DMCO
Digital filter DMFI
Invert the input value DMVI
Invert the sign of the input value DMSI
DPI PDP parameter
Supervision time for midpoint DPMI
Digital Filter DPFI
Maximum chatter frequency DPFR
Invert the input value DPIN
ITI PDP parameter
Acquisition of end of period ITEP
readings
Unit of IR cycle ITUN
Acquisition of intermediate readings ITIR
End of period wrap around counter ITWR
Reduction factor ITRE
Digital Filter ITFI
SPI PDP parameter
Digital filter SPFI
Maximum chatter frequency SPFR

Parameter Unique Excel column name

Invert the input value SPIN
STI PDP parameter
STI value presentation STPR
Consistency check time STCO
Digital filter STFI

ASO PDP parameter
Output signal range ASOU
Output signal type ASTY

Conversion factor ASCO
Strobe (SOC) ASST
DCO PDP parameter
Persistent output DCPO
Command pulse length DCPL
Select before operate only DCSE
Response indication DCRE
Command release delay time DCDE
DSO PDP parameter

DSO value presentation DSPR
Output signal type DSTY
Maximum value (100%) DSMA
Strobe (SOC) DSST
RCO PDP parameter
Command pulse length RCPL
SCO PDP parameter
Output type SCOT
Command pulse length SCPL
Select before operate only SCSE
Response indication SCRE
Command release delay time SCDE

RTU560 RTUtil560 User's Guide IEC61850 Engineering
IEC61850 Engineering
RTU560 in an IEC61850 system

The RTU560 provides as IEC61850 client NCC gateway functionality, connecting
an IEC61850 station bus with NCCs. The figure below shows the RTU560 in an
IEC61850 system.
GPS
WEB HMI IRIG-B Tele-control
Station Level
RTU
I/Os
IEC61850-8-1
Bay Level
SPA
IEC103,
DNP3.0,
Ctrl/ Ctrl/ Ctrl/ Ctrl/
Ctrl Main1 Main2 BBP DR/PQ M Modbus
Prot Prot Prot Prot
Bay Bay with legacy products

Process Level
RTU560 in an IEC61850 system
The standard functionality of the RTU560 like local I/Os and connections with
legacy protocols are available as well.

IEC61850 Engineering RTU560 RTUtil560 User's Guide
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.
[ IET ]
System
1
Configuration
. Primary objects
. Logical Nodes
SA-
2 Engineer
.SSD
3
3 [ IET ]
System 4
….
3 Configuration
. Network
. Communication
3 SA-
5 Engineer
9
.ICD .ICD .ICD .SCD .XLS .cfg
…...
7 NCC-
8 Engineer
9
10
.XLS
Generation
11 [ RTUtil ] 6
IED 1 IED n RTU
…...
Device SA-
Configuration Engineer
. RTU [ RTUtil ]
Scope of RTU61850*1
Engineering SA Engineering NCC
Engineering process
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
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.
The primary system configuration tool and the communication system configuration
tool are outside the scope of this document. These tools are not part of RTUtil560.
RTUtil560 covers the steps 6 to 11 only. The initial point for the engineering in
RTUtil560 is the completed SCD file.

Network and Hardware tree

The network defined in the SCD file must be mapped to an equivalent structure in
the RTUtil560 network tree. The following figure shows the defined mapping.
Logical Logical
TNO Line 1 TNO Line 2
Node ITCI 1 Node ITCI 2
=
IEC61850 Subnet IEC61850 Subnet
TNO IED TNO IED

IED 1 IED 2 IED 3 TNO IED 1 TNO IED 2
3a 3b
Mapping of network
The logical node ITCI (Telecontrol interface) is mapped to an IEC61850 line in

RTUtil560 and the IEDs are mapped one to one. If an IED is part of two IEC61850
networks this IED is represented by two IED in RTUtil560. An example of a
network tree is shown below.
Example network tree
The parameters of the IEC61850 line are IED name and access point where the
logical node ITCI is located. These parameters are not editable in RTUtil560 but
filled during the import of the SCD file. See next chapters for a detailed description.
In the hardware tree the IEC61850 line is linked to the Ethernet interface of a CMU.
This is shown in the figure below.
Example hardware tree

Excel Import File

In the engineering process RTUtil560 imports the SCD file, extract all data points
and write these data points to the Excel import file. As prerequisite the Excel
interface initialization must be done according chapter “Excel Interface”.
The Excel import sheet for the IEC61850 sub device communication interface
contains in one section the IEC61850 process object references and in another
section additional parameters like scaling limits. The process object references are
filled during the import of the SCD file. The user may not modify the data in this
section. The object references are for information purposes only. See figure below.
IEC61850 process object reference

The additional parameters are the scaling limits for AMI, ASO, DMI and DSO data
points. The parameters could be edit by the user. See figure below.
IEC61850 additional parameter

The extraction of data points from the SCD file could be done with an empty excel
import file or with a file filled from a previous SCD file import. In this case the
Excel import file is synchronized with latest SCD file. During synchronization three
case are considered:
• New data point: The data point is part of SCD file but not part of
Excel import file.
• Updated data point: At least one parameter of the data point is
changed in SCD File compared to the Excel import file.
• Deleted data point: The data point is part of Excel import file but
not part of SCD file.
The result of the synchronization is written to the first section of the Excel import
file. A new column called ‘Modified’ contains a character for each data point. The
meaning of the characters is:
• N New data point
• U Updated data point
• D Deleted data point
The following figure shows an example from the Excel import file.
Modified column

SCD File Import

The SCD file import and Excel import file synchronization could be started by the
user from the RTUtil560 menu. The menu item is located in ‘Extra – SCD Import’.
When selected a wizard starts that guides the user through the import and
synchronization process. The steps are:
Step 1: The user has to select the SCD file to import. The user can type the
complete path of the file or browse to the file in the file system. If
the ‘Next’ button is pressed the SCD file is imported and parsed.
After that the dialog continues with the next step.
Select SCD file
Step 2: The user has to select the Excel import file that should be
synchronized with the SCD file. The user can type the complete
path of the file or browse to the file in the file system. If the ‘Next’
button is pressed the Excel import file is read and the dialog
continues with the next step.
Select Excel import file
Step 3: In the last dialog the user specifies the mapping between the ITCI
logical nodes found in the SCD file and the sheets from the Excel

import file. Each sheet in the Excel import file represents an

IEC61850 line in RTUtil560.
ITCI logical nodes must not be mapped to Excel sheets. In this case
the data points related to the not linked ITCI logical node will not
be handled during synchronization.
The defined mapping is stored in the Excel import file. So, if the
Excel import file is used a second time the user must not specify
the mapping again.
If the ‘Finish’ button is pressed the processing starts. Result of the

synchronization process is an Excel import file synchronized with
the selected SCD file.
Select mapping between ITCI nodes and sheet names
The Excel import file generated in the synchronization is used during the normal
Excel import process described in chapter ‘Excel Interface’.

User Interface
According to other sub device communication interfaces the IEC61850 parameters
are shown in separate property pages. There are parameters for IEC61850 lines and
for IED data points. The IED itself has no IEC61850 parameters.
The IEC61850 line parameters are the IED name and the access point name. The
parameters are updated during the SCD file import described above. The shown
parameters are not editable. See figure below.
IEC61850 line parameter
Addresses and parameters of IEC61850 data points will be displayed in the

properties page of a selected data point. Two sections are grouped in this page.
a) Address group:
All information imported from the process object reference section (see chapter
'Excel Import File') are as shown in the page. All fields within this group are not
editable. The address element ‘logical node instance name’ is a concatenation of
logical node prefix, logical node class and logical node instance number. The signal
attribute is a concatenation of signal data object name and signal data object
attribute separated by a dot character.
b) Sub parameter:
Processing parameters that are configuration specific will be displayed in this
editable group. Only parameters referring to the selected data point type are shown.
If no parameter is needed for the selected data point, the group is not displayed.

IEC61850 data point parameter

RTU560 RTUtil560 User's Guide Directory Structure
Directory Structure
Relative Directory
The relative directory structure after installation is described in the following table.
The starting structure is user dependent and suggested by the installation program as
C:\Program Files\ABB\RTUtil560
Sub Directories
The following table contains the sub directories of RTUtil560, that will be build
during the installation process.
Directory Description File

extensions
RTUtil560 The RTUtil560 main directory.
RTUtil560\batch bat
RTUtil560\bin The binary file directory for exe, dll
executables and dynamic link library
files.
RTUtil560\ CSV based files from data export. csv, log
csv_export
RTUtil560\ CSV based files for data import. csv, log
csv_import
RTUtil560\db Directory for the empty database, the mdb
type database, configuration database
and help database.
RTUtil560\ Pattern project file. Basic project files rtu
patterns for start.
RTUtil560\ Pattern file of an empty MULTIPROG mwt
patterns_mwt wt project.
RTUtil560\proj Project directory for RTUtil560 rtu
projects.
RTUtil560\ The loadable files for the several gcd, iod, oad
rtufile RTUs and projects.
RTUtil560\ The tutorials of RTUtil560 in Acrobat pdf
tutorials format.
RTUtil560\ Excel Sheets for data export. xls, err, log

xls_export
RTUtil560\ Excel Sheets for data import. xls, err, log
xls_import
As default directory for MULTIPROG wt projects (*.mwt) the MULTIPROG wt

project directory is taken.

RTU560 RTUtil560 User's Guide Engineering Example
Engineering Example
Process Control System

As process control system the following busbar with a outgoing feeder bay is given:
110 kV
I
II
Q1 Q2
Q0
Q9
Q8
Q0 – circuit breaker
Q1, Q2 – busbar disconnector
Q9 – outgoing feeder disconnector
Q8 – outgoing feeder earthing switch
I, II – busbar
This bay is at two locations, in Mannheim and in Ladenburg.

Engineering Example RTU560 RTUtil560 User's Guide
RTU Configuration
Initialize Project
At the start of a new project some project information is set.
Initialize project
The project information is only for documentation.

Initialize Signal Tree

The Signal Tree structure is defined. The name and the length of the levels have to
be given.
Four levels are defined:
• Station with 10 character length
• Subnet with 6 character length
• Bay with 4 character length
• SCADA Object with 12 character length
(the last level never has a name)
Initial Signal Tree
Now the general project settings are made. With „Finish“ they are accepted.
These settings cannot be changed anymore.

Build the Network Tree

The two outgoing feeder bays are supervised by the telecontrol. The one in
Mannheim is supervised by one RTU and the one in Ladenburg by another RTU.
The RTU in Mannheim is a router RTU and connected to the control system. The
RTU in Ladenburg is a sub RTU, connected to the router RTU in Mannheim.
Networktree
Build the Signal Tree

First the outgoing feeder in Mannheim is built. The outgoing feeder in Ladenburg is
exactly the same. It can be copied. When the station Mannheim is copied to the
Signal Tree the name of the station („Mannheim“) is replaced by „COPY“ . The
only thing that has to be done is to replace „COPY“ by „Ladenburg“ and the Signal
Tree is finished.
Signal Tree

Build the Hardware Tree

Communication Part
Every RTU a configuration file should be built for has to be configured in the
Hardware Tree.
The nodes RTU, line and data point are already defined in the other trees so they
have to be linked in to the Hardware Tree. The RTUs and the lines are in the
Network Tree and the data point in the Signal Tree.
In the first step the hardware is built up to the communication rack.
The parameter „Time synchronization mode“ of the RTU, „Initial redundancy
mode“ and „Administration mode“ of the communication boards (SLI, ETH) and
the „node name“, „IP address“, „Subnet mask“, „Default gateway IP“ of the
Ethernet interface have to be set.
Parameters of the communication board (SLI, ETH)
I/O Part
Then the I/O racks and I/O boards are added. They can be added only if I/O bus is
defined.
Set SEV Address and Link Data Points

Before the data points are linked the start address of the RTU system event block
(SEV) should be set. The SEV link and ASDU address (IEC 60870-5-104 only
ASDU address) is used as default address of the data points.

RTU SEV start address
Then the data points can be linked.
Hardware Tree
Now the RTUs have been engineered with the RUTtil 560.

Configuration Files
Before the configuration files are build the project should be saved. Two download
files are build:
1. .gcd
2. .iod
Generate download file
The last part (after the last „\“) of the „Filename“ is the configuration file name.
Configfile Download
How the configuration files are downloaded is described in the documentation:
"RTU560 Web-Server User’s Guide"

RTUtil560 Users Guide R8

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

RTUtil560 Users Guide R8

Uploaded by

Copyright:

Available Formats

RTU560

Remote Terminal Unit

RTUtil560 User's Guide Release 8

Document identity: 1KGT 150 451 V005 1

Revision: 0 Date: May 2000

We reserve all rights in this document and in the information contained

ABB AG 1KGT 150 451 V008 1 Preliminary Version I

Data Engineering Concept .......................................................................7

The Tree Functionalities ...........................................................................9

User Interface ..........................................................................................15

ABB AG 1KGT 150 451 V008 1 Preliminary Version I

Moving in Trees, Selecting Items .......................................................... 21

Project Functions ................................................................................... 27

Extra Functions ...................................................................................... 33

Excel Interface ........................................................................................ 45

II 1KGT 150 451 V008 1 Preliminary Version ABB AG

IEC61850 Engineering ............................................................................75

Directory Structure .................................................................................85

ABB AG 1KGT 150 451 V008 1 Preliminary Version III

ABB AG 1KGT 150 451 V008 1 Preliminary Version 1

1. Acknowledge welcome page

Getting Help on RTUtil560

Example of a Tool Tip

2 1KGT 150 451 V008 1 Preliminary Version ABB AG

User Plausibility Excel Excel PLC

Overview RTUtil560 Components

ABB AG 1KGT 150 451 V008 1 Preliminary Version 3

General Data Structuring and View

4 1KGT 150 451 V008 1 Preliminary Version ABB AG

General Tree Structure

04 Plant Ladenburg 110kV

RTU 11 RTU 21 Peripherie Bus Line, Segment 1

Network - RTU - Process

ABB AG 1KGT 150 451 V008 1 Preliminary Version 5

Data Engineering Concept

ABB AG 1KGT 150 451 V008 1 Preliminary Version 7

3. Set parameters, addresses

8 1KGT 150 451 V008 1 Preliminary Version ABB AG

The Tree Functionalities

Engineering Functions in Network Tree

ABB AG 1KGT 150 451 V008 1 Preliminary Version 9

Network Tree Structure

Actions in Network Tree

Links and Link Actions in Network Tree

10 1KGT 150 451 V008 1 Preliminary Version ABB AG

Engineering Functions in Signal Tree

Signal Tree Structure

Level Description Number of Identifier

Actions in Signal Tree

ABB AG 1KGT 150 451 V008 1 Preliminary Version 11

Links and Link actions in Signal Tree

Engineering Functions in Hardware Tree

Hardware Tree Structure

Actions in Hardware Tree

12 1KGT 150 451 V008 1 Preliminary Version ABB AG

Links and Link Actions in Hardware Tree

Parameter in Hardware Tree

ABB AG 1KGT 150 451 V008 1 Preliminary Version 13

RTUtil560 User Interface

ABB AG 1KGT 150 451 V008 1 Preliminary Version 15

Main window Menu bar Tool bar Tree window

Statusbar Tree view pane Parameter view pane

16 1KGT 150 451 V008 1 Preliminary Version ABB AG