UC 500

ASID12000063, Rev. 7.1, May 16

 The content of this manual has been carefully revised, however, the full compliance of its
content with the technical and functional characteristics of the product it is referred to
cannot be assured, as typing or other errors cannot be completely ruled out. The
information given is regularly reviewed and any necessary correction or additional
explanation will be included in future revisions of this document.
Due to continuous development, the content of this manual can be changed without
notice.
We appreciate any correction or improvement suggestion.

ii - UC 500, N. ASID12000063, Rev. 7.1, May 16

Manual Revisions

Revision Date Changes

1.9 2012-03-08 Vers ion corresponding to Automation Studio 2.6 or l a ter.

2.0 2012-07-02 Incl uded mimics s cripting related i nformation.
Vers ion corresponding to Automation Studio 2.6 Rev.1 or l ater.
2.1 2012-10-04 Incl uded Automation Objects information.
Incl uded i nformation in Communicating with the device chapter.
Vers ion corresponding to Automation Studio 2.6 Rev.2 or l ater.

2.2 2013-02-06 Added information regarding deployi ng redundant configurations in UC 500

vers i ons previous to 7.2.0.

2.3 2013-05-03 Incl uded more information in the Automation Module chapter.
2.4 2013-07-10 Incl uded Areas of Responsibility chapter
2.5 2013-07-24 Incl uded new features of UC 500 vers ion 8.0.0 or a bove: changes i n Areas of
Res ponsibility a nd in Get System Log.
3.0 2013-08-08 Vers ion corresponding to Automation Studio 2.6 Rev.4 or l ater.

3.1 2013-12-26 Revi ewed Templating options descriptions.

6.1 2014-10-02 Added chapters about IEC 61850 model
6.2 2014-10-03 Added information about Import CC 101/104 Emul a ted RTU
6.4 2014-10-10 Added information about the Network Topology Module configuration

7.1 2014-10-13 Vers ion corresponding to Automation Studio 3 or l a ter.

- UC 500, N. ASID12000063, Rev. 7.1, May 16 iii

INDEX

1 INTRODUCTION ...................................................................................................................................................... 1-1

1.1 PURPOSE ................................................................................................................................................................... 1-3
1.2 SCOPE AND AUDIENCE ................................................................................................................................................ 1-4
1.3 REFERENCES ............................................................................................................................................................... 1-5
1.4 I NTRODUCTION .......................................................................................................................................................... 1-6
1.5 HOW TO GET STARTED ? .............................................................................................................................................. 1-7
2 INTRODUCIN G THE UC 500 OBJECT MODEL AND TOOL USER INTERFACE................................................. 2-1
2.1 UC 500 DEVICE FEATURES AND APPLICATIONS............................................................................................................ 2-3
2.2 PRINCIPLES OF O BJECT-ORIENTED CONFIGURATION ..................................................................................................... 2-4
2.3 UNDERSTANDING UC 500 O BJECTS............................................................................................................................ 2-5
2.4 O BJECTS ON THE USER I NTERFACE ............................................................................................................................... 2-6
2.5 ABOUT MODULES ...................................................................................................................................................... 2-7
2.6 MODULE EDITORS ...................................................................................................................................................... 2-8
2.7 ENTITY TYPES EXPLAINED............................................................................................................................................ 2-9
2.8 SELECTING REFERENCES TO ENTITIES .........................................................................................................................2-10
2.9 DEFAULT VALUES .....................................................................................................................................................2-11
3 ADOPTING A CONFIGURATION PROCESS.......................................................................................................... 3-1
3.1 PROCESS GUIDANCE.................................................................................................................................................... 3-3
3.2 I TERATIVE CONFIGURATION AND MODIFICATION ......................................................................................................... 3-5
3.3 MANAGING CONFIGURATION VERSIONS...................................................................................................................... 3-6
4 ADDIN G DEVICES TO PROJECTS........................................................................................................................... 4-1
4.1 NEW DEVICES ............................................................................................................................................................ 4-3
4.2 EXISTING DEVICES ...................................................................................................................................................... 4-4
5 SETTING-UP SOFTWARE AND HARDWARE MODULES ................................................................................... 5-1
5.1 DEVICE MODULE AND ORDER CODE ............................................................................................................................. 5-3
5.2 LOCAL AREA NETWORK I NTERFACES............................................................................................................................ 5-4
5.3 SERIAL PORTS............................................................................................................................................................. 5-5
5.4 SELECTING SOFTWARE MODULES................................................................................................................................ 5-8
5.5 SETTING UP THE MAIN MENU AND TOOLBAR.............................................................................................................. 5-9
5.6 W ATCHDOG.............................................................................................................................................................5-10
5.7 LOCAL CLOCK SYNCHRONIZATION O PTIONS...............................................................................................................5-11
6 CONFIGURING THE DATA MODEL ....................................................................................................................... 6-1
6.1 THE HIERARCHY VIEW ................................................................................................................................................. 6-3
6.2 HIERARCHY LEVELS ..................................................................................................................................................... 6-4
6.3 ENGINEERING UNITS................................................................................................................................................... 6-5
6.4 AREAS OF RESPONSIBILITY........................................................................................................................................... 6-6
6.5 IEC 61850 MODEL ................................................................................................................................................... 6-9
7 CONFIGURING THE SCADA MODUL ES ............................................................................................................... 7-1
7.1 USER INTERFACE APPLICATIONS AND LAYOUT CONFIGURATION ..................................................................................... 7-3
7.2 EVENT-LOG ................................................................................................................................................................ 7-4
7.3 ALARMS ..................................................................................................................................................................... 7-5
7.4 TRENDS...................................................................................................................................................................... 7-6
7.5 MIMICS ..................................................................................................................................................................... 7-7
7.6 NETWORK TOPOLOGY...............................................................................................................................................7-10
7.7 PRINT-FORMS ..........................................................................................................................................................7-16
7.8 SETTING-UP AUTOMATIC MAINTENANCE OF LOCAL DATABASES .................................................................................7-17
8 AUTOMATION WITH IEC 61131-3 ....................................................................................................................... 8-1

iv - UC 500, N. ASID12000063, Rev. 7.1, May 16

 8.1 AUTOMATION WITH IEC 61131-3 .............................................................................................................................8-3
9 RTU/ IED COMMUN ICATION ................................................................................................................................ 9-1
9.1 IEC 60870-5-101 CONTROLLING STATION.................................................................................................................9-3
9.2 IEC 60870-5-104 CONTROLLING STATION ................................................................................................................9-5
9.3 DNP 3 .0 MASTER ......................................................................................................................................................9-8
9.4 PROCOME MASTER .................................................................................................................................................9-9
9.5 MODBUS MASTER ................................................................................................................................................... 9-10
9.6 IEC 60870-5-103 MASTER.................................................................................................................................... 9-11
9.7 MODBUS/TCP CLIENT ............................................................................................................................................ 9-12
9.8 SPABUS MASTER .................................................................................................................................................... 9-13
9.9 JBUS M ASTER ......................................................................................................................................................... 9-14
10 CONTROL CEN TRE COMMUNICATION .............................................................................................................10-1
10.1 CONTROL CENTER COMMUNICATION ...................................................................................................................... 10-3
10.2 IEC 60870-5-101 CONTROLLED STATION ............................................................................................................ 10-4
10.3 IEC 60870-5-104 CONTROLLED STATION ............................................................................................................ 10-5
10.4 DNP 3.0 SLAVE .................................................................................................................................................... 10-6
11 LOCAL AREA NETWORKING AN D DISTRIBUTED AUTOMATION .................................................................11-1
11.1 NTP CLIENT .......................................................................................................................................................... 11-3
11.2 IEC 61850-8-1 CLIENT......................................................................................................................................... 11-4
11.3 SNMP MANAGER ................................................................................................................................................. 11-7
12 SAVING, BUILDING AN D VALIDATIN G YOUR CONFIGURATION .................................................................12-1
12.1 SAVE PROCESS ...................................................................................................................................................... 12-3
12.2 VALIDATE PROCESS................................................................................................................................................ 12-4
12.3 BUILD PROCESS..................................................................................................................................................... 12-5
13 COMMUNICATING WITH THE DEV ICE ..............................................................................................................13-1
13.1 CONFIGURATION SETTINGS .................................................................................................................................... 13-3
13.2 SYSTEM LOG ......................................................................................................................................................... 13-4
14 PRODUCTIVITY AND REFACTORIN G TOOLS ....................................................................................................14-1
14.1 PRODUCTIVITY AND REFACTORING TOOLS............................................................................................................... 14-3
14.2 SAFE MODIFICATION OF ENTITY I DENTIFIERS........................................................................................................... 14-5
14.3 HANDLING DESCRIPTIVE DATA ............................................................................................................................... 14-6
14.4 CONFIGURATION COMPARISON TOOL..................................................................................................................... 14-7
14.5 AUTOMATION O BJECTS.......................................................................................................................................... 14-8
15 USING EXTERNAL TOOLS .....................................................................................................................................15-1
15.1 DATA MAP TOOL .................................................................................................................................................. 15-3
16 ANNEXES.................................................................................................................................................................16-1
16.1 PRINT FORM DEFINITION MINI-LANGUAGE SAMPLE ............................................................................................... 16-3
16.2 CONTROL I NHIBITION MINI-LANGUAGE DEFINITION................................................................................................ 16-6
16.3 CONTROL FINAL -STATE MINI-LANGUAGE DEFINITION.............................................................................................. 16-7
16.4 CONVERSION FUNCTION MINI-LANGUAGE DEFINITION ........................................................................................... 16-8
16.5 ADVANCED USAGE OF THE IEC 61850 SCL I MPORT W IZARD ................................................................................. 16-9
16.6 IDE O PTIONS ...................................................................................................................................................... 16-13
16.7 PRIVATE EXTENSIONS........................................................................................................................................... 16-14

- UC 500, N. ASID12000063, Rev. 7.1, May 16 v

LIST OF FIGURES

Figure 2.1 Examples of object icons ............................................................................................................................. 2-5

Figure 2.2 Identifying objects in the IDE...................................................................................................................... 2-6
Figure 2.3 Example of a typical grid-based module editor ...................................................................................... 2-8
Figure 2.4 Entity selector .............................................................................................................................................2-10
Figure 2.5 Default values..............................................................................................................................................2-11
Figure 3.1 Standard configuration activity workflow................................................................................................ 3-3
Figure 3.2 Iterative activity cycle .................................................................................................................................. 3-5
Figure 4.1 IED 500 Device Structure Sample .............................................................................................................. 4-3
Figure 5.1 Serial port editor........................................................................................................................................... 5-5
Figure 5.2 Configurations using Modem physical medium (standard modem, direct cable, integrated
radio/modem, PLC modem, etc.) ................................................................................................................................. 5-5
Figure 5.3 Configurations using Radio physical medium (standard modem with external radio).................... 5-6
Figure 5.4 Configurations using Telephone physical medium (switched network, GSM, etc.) .......................... 5-6
Figure 5.5 Module browser at the Solution Explorer ................................................................................................ 5-8
Figure 6.1 Hierarchy view............................................................................................................................................... 6-3
Figure 6.2 Hierarchy levels definition .......................................................................................................................... 6-4
Figure 6.3 Hierarchy levels selector ............................................................................................................................. 6-4
Figure 6.4 Engineering unit selector ............................................................................................................................ 6-5
Figure 6.5 Opening Areas of Responsibility ................................................................................................................ 6-6
Figure 6.6 Areas of Responsibility view ....................................................................................................................... 6-7
Figure 6.7 Areas of Responsibility selector ................................................................................................................. 6-8
Figure 7.1 GUI advanced settings ................................................................................................................................. 7-3
Figure 7.2 Event log confirmation ................................................................................................................................ 7-4
Figure 7.3 Alarms configuration.................................................................................................................................... 7-5
Figure 7.4 Trends configuration .................................................................................................................................... 7-6
Figure 7.5 Mimics application ....................................................................................................................................... 7-7
Figure 7.6 Mimics module activation........................................................................................................................... 7-7
Figure 7.7 Accessing the HMI 500 actions available. ................................................................................................ 7-9
Figure 7.8 Network Topology module activation. ...................................................................................................7-10
Figure 7.9 Static topology colors configuration. ......................................................................................................7-10
Figure 7.10 Object type definition..............................................................................................................................7-11
Figure 7.10 Example of specific network topology properties..............................................................................7-11
Figure 7.10 Network Topology System Library. .......................................................................................................7-12
Figure 7.7 Database maintenance configuration.....................................................................................................7-17
Figure 8.1 Automation module ..................................................................................................................................... 8-3
Figure 9.1 Wizard to select UC500 device to import ................................................................................................ 9-3

vi - UC 500, N. ASID12000063, Rev. 7.1, May 16

Figure 9.2 Selection of emulated RTU to import ........................................................................................................9-4
Figure 9.3 Wizard to select device to import..............................................................................................................9-5
Figure 9.4 Selection of emul ated RTU/IED to import ................................................................................................9-6
Figure 9.5 Wizard to define ID generation rules ........................................................................................................9-7
Figure 10.1 Control center communication configuration .................................................................................... 10-3
Figure 11.1 Object selection step............................................................................................................................... 11-4
Figure 11.2 Review options step ................................................................................................................................ 11-5
Figure 11.3 Data Flow configuration example......................................................................................................... 11-6
Figure 14.1 Configuration settings tools................................................................................................................... 14-3
Figure 14.2 Refactoring window ................................................................................................................................ 14-4
Figure 14.3 Refactoring options ................................................................................................................................. 14-4
Figure 14.4 Id replacer wizard .................................................................................................................................... 14-5
Figure 14.5 UC 500 Selector Form ............................................................................................................................. 14-8
Figure 14.6 Automation Object associated to a symbol ........................................................................................ 14-9
Figure 15.1 Export data map wizard.......................................................................................................................... 15-3
Figure 15.2 Config tab .................................................................................................................................................. 15-4
Figure 15.3 Import data map wizard ......................................................................................................................... 15-6
Figure 16.1 SCL import tool architecture and workflow........................................................................................ 16-9
Figure 16.2 SCL object selection window ............................................................................................................... 16-11
Figure 16.3 UC 500 options ....................................................................................................................................... 16-13
Figure 16.4 UC 500 Private Extensions ................................................................................................................... 16-14

- UC 500, N. ASID12000063, Rev. 7.1, May 16 vii

LIST OF TABLES

Table 2.1 Overview of some UC 500 object types ..................................................................................................... 2-5

Table 2.2 UC 500 entity types (see 6 for details on the configuration of each entity type) .............................. 2-9
Table 2.3 UC 500 entity sources ................................................................................................................................... 2-9
Table 3.1 Tasks and engineering skill sets................................................................................................................... 3-4
Table 4.1 Available options to add existing UC 500 devices .................................................................................... 4-4
Table 5.1 Options for duplex channel operation ....................................................................................................... 5-6
Table 7.1 Scripting properties ....................................................................................................................................... 7-9
Table 7.2 Scripting actions ............................................................................................................................................. 7-9
Table 7.3 Types. .............................................................................................................................................................7-12
Table 7.3 States description and coloration value. .................................................................................................7-13
Table 7.2 Print forms names........................................................................................................................................7-16
Table 14.1 Productivity tools .......................................................................................................................................14-3
Table 14.2 Templating options....................................................................................................................................14-8
Table 15.1 Hierarchy levels definition .......................................................................................................................15-4
Table 15.2 Entity identification ...................................................................................................................................15-4
Table 15.3 Entity type ...................................................................................................................................................15-4
Table 15.4 Description ..................................................................................................................................................15-5
Table 15.5 HMI ...............................................................................................................................................................15-5
Table 15.6 Control center ............................................................................................................................................15-5
Table 15.7 Source ..........................................................................................................................................................15-6
Table 16.1 Overview of some possible mappings from IEC 61850 data objects to UC 500 entities ........... 16-10
Table 16.2 Available keywords (example for SCL object IED\LD\Q50XCBR1.PhV.phsA\a.b.c)..................... 16-12

viii - UC 500, N. ASID12000063, Rev. 7.1, May 16

 1
Chapter

INTRODUCTION
 Chapter 1 - Introduction

INDEX
1
1.1 PURPOSE ................................................................................................................................................................... 1-3
1.2 SCOPE AND AUDIENCE ................................................................................................................................................ 1-4
1.3 REFERENCES ............................................................................................................................................................... 1-5
1.4 I NTRODUCTION .......................................................................................................................................................... 1-6
1.5 HOW TO GET STARTED ? .............................................................................................................................................. 1-7

Total pages of the chapter 7

1-2 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 1.1- Purpose

1.1 PURPOSE

To help Automation Studio users configure and manage UC 500 devices. For device hardware and software
installation and maintenance procedures other documentation is need, please refer to the specific UC 500
product documentation.

- UC 500, N. ASID12000063, Rev. 7.1, May 16 1-3

 Chapter 1 - Introduction

1.2 SCOPE AND AUDIENCE

1
This guide targets the UC 500 device family and Automation Studio Designer 2.6.
The reader of this document and user of the tool is an automation engineer who has basic knowledge of
automation and industrial communications.

1-4 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 1.3- References

1.3 REFERENCES

[Ref.] Title Date Rev. Source Number

1. Automation Studio– IEC 61131-3
latest latest EFACEC latest
Programmers Guide
2. Automation Studio - Mimic Editor Guide latest latest EFACEC latest
3. Automation Studio – UC 500 Upgrade Guide latest latest EFACEC latest
4. Automation Studio – IDE Guide latest latest EFACEC latest

- UC 500, N. ASID12000063, Rev. 7.1, May 16 1-5

 Chapter 1 - Introduction

1.4 INTRODUCTION
1
The UC 500 Configuration Editor is an Automation Studio IDE module designed specifically for managing and
editing the configuration of UC 500 devices. It includes several editors, productivity tools, a device builder
and a communications driver.
This document describes user features and provides hints on how to use them in a productive way. Please
note however that this guide does not cover IDE-wide features such as windowing, device management,
loading, saving and backing up device configurations , project and build system, etc. Before going through
this guide the user is advised to read the IDE Guide 4.

1-6 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 1.5- How to get started?

1.5 HOW TO GET STARTED?

For the experienced engineer the tool is intuitive and provides built-in descriptions of all configuration
parameters so that minimum documentation reference is required during use.
An automation engineer which is inexperienced with this device model will, in most scenarios, need to read
this document1 to get started and be able to handle most configuration activities. If you already know how
to use the IDE you can skip the IDE Guide 4 and go directly to chapter 2 and 3.
In chapter 2 the UC 500 configuration model and the common IDE configuration features are introduced.
In chapter 3 the configuration process is described from a general perspective. From there the user is
directed to specific chapters for guidance on each step or on how to properly handle the configuratio n of
each module. In each specific chapter the reader will find the information which is required but not easily
perceived from the configuration editors and built-in descriptions.
Several annexes are included at the last chapter providing additional insight on specific issues.

1 This document is comprehensive but note that reading referenced documentation may also be necessary.
This document as well as any other required product documentation is included with the tool and
accessible via Start Page or Help menu.

- UC 500, N. ASID12000063, Rev. 7.1, May 16 1-7

 2
Chapter

INTRODUCING THE UC 500 OBJECT

MODEL AND TOOL USER
INTERFACE
 Chapter 2 - Introducing the UC 500 Object Model and Tool User Interface

INDEX
1
2.1 UC 500 DEVICE FEATURES AND APPLICATIONS............................................................................................................ 2-3
2.2 PRINCIPLES OF O BJECT-ORIENTED CONFIGURATION ..................................................................................................... 2-4
2.3 UNDERSTANDING UC 500 O BJECTS............................................................................................................................ 2-5
2.4 O BJECTS ON THE USER I NTERFACE ............................................................................................................................... 2-6
2.5 ABOUT MODULES ...................................................................................................................................................... 2-7
2.6 MODULE EDITORS ...................................................................................................................................................... 2-8
2.7 ENTITY TYPES EXPLAINED............................................................................................................................................ 2-9
2.8 SELECTING REFERENCES TO ENTITIES .........................................................................................................................2-10
2.9 DEFAULT VALUES .....................................................................................................................................................2-11

Total pages of the chapter 11

2-2 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 2.1- UC 500 Device features and Applications

2.1 UC 500 DEVICE FEATURES AND APPLICATIONS

UC 500 device is a communications gateway between remote units or IEDs and control centers. It also
executes functions of communications network management, local automation or soft PLC, communication
with IEDs and SCADA HMI.
The general configuration of the UC 500 device includes the configuration of: data points, controls,
synchronism module, watchdog, redundancy and generic device parameters, as well as the HMI and the
several communications protocols. The HMI includes alarms and trends management, mimi cs and event
logs

- UC 500, N. ASID12000063, Rev. 7.1, May 16 2-3

 Chapter 2 - Introducing the UC 500 Object Model and Tool User Interface

2.2 PRINCIPLES OF OBJECT-ORIENTED

1
CONFIGURATION

Object-oriented configuration introduces many benefits over the conventional table/form-based approach
of configuring devices. Previous device or SCADA engineering tools provide number of forms and tables,
usually a GUI front-end to a database matching its internal characteristics quite closely.
Although this device tool does not make use of automation objects, an object-oriented model of the device
configuration is employed. This model provides views based on configuration objects, their specific
configuration parameters and relationships between the objects. Objects can be created and deleted and
cascading updates ensure configuration is always kept consistent during editing.
The major benefits of this lie on the fact that the defined object model are oriented towards the user needs
and way of thinking and not the internal database model itself, namely:
 Presented GUI views closely match the natural objects the user needs to manage
 Most unneeded or redundant configuration tasks and parameters are eliminated
 The amount of knowledge the engineer needs to have on the specific technological
implementation is reduced.
To keep it short this reduces the learning curve and enhances user productivity.

2-4 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 2.3- Understanding UC 500 Objects

2.3 UNDERSTANDING UC 500 OBJECTS

An UC 500 object model (a given device configuration) can be conceptualized as a box containing a number
of objects of different types. Objects are entities (digitals, analogues, counters and controls), engineering
units, hierarchy levels, serial ports, conversion functions, modules, control centers, emulated RTUs,
communication channels, remote units, alarms, SOE/Event-log triggers, mimic pages, etc.
Each object has a specific type (in table 3.1 the most relevant object types are described). Objects expose
different configuration parameters according to their object type (serial ports have baud rate, stop bits,
etc.) and are related to each other in natural associations (the serial port of a given control center number
is COM1). There are also objects that are similar to each other (all control center objects share some
common parameters, but DNP 3.0 slaves have specific parameters that are not available in IEC 60870 -5-101
controlled stations).

Object Type Notes

All real-time database data objects are named entities (status or
Entity
controls).

Process System or user interface process that runs on the device to provide a
given functionality.
Automation Studio Designer introduces this virtual object type to allow
Module functionally-oriented views. A module represents a set of functionality
implemented by one or more processes.
Communication channel for obtaining data and sending controls to
remote RTUs or IEDs. Each communication module will provide
Channel
protocol-specific channel parameters and expose other related object
types.
Represents a remote RTU or IEDs available at a given channel. Each
RTU / IED communication module will provide protocol -specific RTU / IED
parameters.
Represents a control center to which the UC 500 device behaves as an
Control Centre RTU or IDE. It also represents the associated communication channel.
Each communication module will provide protocol -specific parameters.
A control center emulated RTU. Most protocol implementati ons allow
Emulated RTU/ IED the user to define more than one RTU for a given channel thereby
emulating several physical RTUs. Each communication module will
provide protocol -specific parameters.
Table 2.1 Overview of some UC 500 object types
Each object type has a specific name and icon that is consistently used in the IDE so that the user
immediately knows what object type is being handled.

Figure 2.1 Examples of object icons

- UC 500, N. ASID12000063, Rev. 7.1, May 16 2-5

 Chapter 2 - Introducing the UC 500 Object Model and Tool User Interface

2.4 OBJECTS ON THE USER INTERFACE

1
Taking the simple example of the figure bellow you can straightforwardly identify which objects are being
handled as well as have an overlook of the UC 500 configuration editor windows.

Figure 2.2 Identifying objects in the IDE

When working with the tool the user repeatedly views, check, creates, deletes or modifies the selected
object or set of objects. Objects can be selected by interacting with one of several available views (any
window in the IDE is actually an object view).
In the screenshot above the user is changing the serial port of an IEC 60870 -5-101 controlled station that is
selected. The drop-down is showing all the serial ports available on the UC 500 device and the user is
actually manipulating a reference to an existing serial port that is to be used by this object to communicate
with the actual remote control center front-end.
All objects also have a specific unique identification so that they can be referenced to in any scenarios,
serial ports are referenced by their COM number and control centers are referenced by their unique
number. In fact, any object in the UC 500 model ha s a specific parameter, named Id, which corresponds to
its unique identification.

2-6 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 2.5- About Modules

2.5 ABOUT MODULES

The UC 500 device software is modular in order to adapt the unit to distinct applications. Functional
modules are organized by functional scope: user interface (chapter 6), automation (chapter 8), local
networking (chapter 11), control center communications (chapter 10) and IED/RTU communications
(chapter 9).

- UC 500, N. ASID12000063, Rev. 7.1, May 16 2-7

 Chapter 2 - Introducing the UC 500 Object Model and Tool User Interface

2.6 MODULE EDITORS

1
2
Each module-specific editor can be brought up by double-clicking the module on the Solution Explorer.
Most module editors have a common window layout, as shown in figure below.

Figure 2.3 Example of a typical grid-based module editor

On the left side of the panel, the user can find a tree view, hierarchically representing the current
configuration of the module. On the right side, there is a grid with the entities (or other objects) co ntained
within the selected object on the tree view. The user may delete, fill up/down, and copy from/to grids and
external tools such as spread sheets.
On the toolbar, the user can find several features, such as adding new objects, filtering the grid view and
hide/unhide advanced columns.
To search by entity identifier, the user has to enter a pattern. For more information about patterns and on
how to use regular expressions and wildcards, please refer to 4.

2
As with most objects in the IDE the common operations available for every module are available at the
context menu.

2-8 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 2.7- Entity Types Explained

2.7 ENTITY TYPES EXPLAINED

Type Sub-type Source Description

Single, Double, 2-bit
Enumerated, 3-bit
Digital Discrete status value.
Enumerated, 4-bit
Enumerated
Analogue n/a Analogue status value.
Remote
Counter n/a Local Floating-point counter value.
Command Diagnostic Control with Execution order issued to source
no Local control that initiates a pre-configured
Sequence parameter
Control control sequence.

Set-point Control issued to source that carries a floating-point value

as parameter.
Table 2.2 UC 500 entity types (see 6 for details on the configuration of each entity type)
Note that there is a hard limit of 32768 on the number of entities for each type in given UC 500 device.

Source Entity Type Description

Digital
Entity that is used to monitor unit or module
Analogue
operation/ behavior.
Diagnostic Counter
Command
Controls that modify module behavior.
Set-point
Sequence n/a
Digital
Remote Data obtained from a remote RTU/ IED via a given
Analogue
communication channel.
(see 9 and 11 for the Counter
configuration of Command Controls issued to a remote RTU/ IED via a given
communication protocol - communication channel.
Set-point
specific parameters)
Sequence n/a
Digital
Derived entities (i) written by local controls, (ii) used
Analogue for control inhibition purposes or (iii) written by local
Counter automation functions (see 8).

Either (i) an internal command that that sets the

value of a given derived digital, analogue or counter
Command
Local to a pre-configured value or (ii) a control issued to
local automation functions (see 8).
Set-point that (i) modifies the value of a given
Set-point derived analogue or counter or (ii) is issued to local
automation functions (see see 8).

Sequence The only source which is applicable to sequences.

Table 2.3 UC 500 entity sources

- UC 500, N. ASID12000063, Rev. 7.1, May 16 2-9

 Chapter 2 - Introducing the UC 500 Object Model and Tool User Interface

2.8 SELECTING REFERENCES TO ENTITIES

1

Figure 2.4 Entity selector

In this dialog box, the user may select existing entities to refer in other modules. The user may search by
entity identifier, choose the type of entity, choose by module or hierarchy and may select several entities at
the same time. For more information about Hierarchy Level, please check chapter 7.
The user may also filter by modules or hierarchy l evels, and they will appear in the tree view.

2-10 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 2.9- Default Values

2.9 DEFAULT VALUES

The user has the possibility to set default values for almost every parameters of all kind of objects. These
values are kept for each existent kind of object and per device configuration.

Figure 2.5 Default values

As shown in the figure above, in each parameter, there are several options:

 Reset Value: sets the parameter with the default value.

 Reset All Values: sets all parameters with the corresponding default value.
 Set As Default Value: the current value in the selected parameter will be set as default.
 Set All As Default Value: the current values in all parameters of the selected object will be set as
default.
 Remove Default Value: removes the definition of default value of the selected parameter.
 Remove All Default Values: removes the definition of default values from all parameters.

The user may also manage those values manually through the file defaults.def, in the configuration folder.

- UC 500, N. ASID12000063, Rev. 7.1, May 16 2-11

 3
Chapter

ADOPTING A CONFIGURATION
PROCESS
 Chapter 3 - Adopting a configuration Process

INDEX
1
3.1 PROCESS GUIDANCE.................................................................................................................................................... 3-3
3.2 I TERATIVE CONFIGURATION AND MODIFICATION ......................................................................................................... 3-5
3.3 MANAGING CONFIGURATION VERSIONS...................................................................................................................... 3-6

Total pages of the chapter 6

3-2 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 3.1- Process guidance

3.1 PROCESS GUIDANCE

User Interface Requirements System Requirements System Arquitecture

Add Device To Project

Device Setup
Review Hardware Configuration

Select Required Software Modules

User Interface

Design Mimics
Configuration

Data Model Configuration

Add Units and Hierachy Levels

Alarms, SOE, Printers, Trends

Add Channels and IEDs / RTUs

Point List
Add Entities
Automation

Programming
Communications

Debugging and Testing

Add Control Centers

Communication Settings

UC 500 Configuration

Integration and Validation

Figure 3.1 Standard configuration activity workflow

The recommended activity workflow to be employed during the configuration phase of the project is
summarized above. This workflow identifies the major steps to undertake as well as general activity
precedence. Please note that this is not a strict process to follow but a general guideline.

- UC 500, N. ASID12000063, Rev. 7.1, May 16 3-3

 Chapter 3 - Adopting a configuration Process

The decision to employ a given process must consider the actual team characteristics, project constraints
and project type (new system or system expansion).
Regarding whole system configuration you can adopt a bottom-up approach (remote devices configured
1 first and UC 500 after) or a top-down approach (configure UC 500 first and remote units after), the tool
supports both. A bottom-up approach is usually recommended when IEDs are used and a top-down
approach, the more conventional approach, when remote units are simple RTUs or I/O modules. More
frequently than not, the adopted approach is a mixed approach3.
Four major configuration tasks (in terms of workload and differentiating engineering skills) are identified: (i)
core configuration (device setup, data model configuration and user interface), (ii) mimics design, (iii)
automation logic programming and (iv) communications setup. These major tasks ca n be performed
sequentially or in parallel, by the same or different engineers. Adequate tool support for any of these
strategies is included.
4
Major Tasks User Profile Reference
Core configuration Database engineer Chapters 4, 5 and 6
Mimics design Graphic designer Chapter 7.5
Automation logic Automation or control engineer Chapter 8
programming
Communications setup Communications engineer Chapters 9, 10 and 11
Table 3.1 Tasks and engineering skill sets
Independently of the adopted approach, particularly if a multi -disciplinary team is working cooperative on
the configuration phase, an integration and validation task should be foreseen prior to the FAT phase.

3 Note that some productivity features such as the IEC 61850 SCL import wizard will yield better results if a
bottom-up approach is used.
4
Remaining chapters 2, 12, 13 and 14 are applicable to all user profiles.

3-4 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 3.2- Iterative Configuration and Modification

3.2 ITERATIVE CONFIGURATION AND MODIFICATION

Actual configuration performed by the user is frequently performed iteratively, in small consecutive steps,
leading to an incremental process. Although editing, validating and testing are distinct activities for each
user profile and different features or tools of the IDE are employed, the activity cycle is quite similar (see
figure below).

Figure 3.2 Iterative activity cycle

Productive teams or engineers will make use of the reuse features provided, namely copy/paste, libraries
and templates, as described in the IDE Guide 4 and elsewhere in this document.

- UC 500, N. ASID12000063, Rev. 7.1, May 16 3-5

 Chapter 3 - Adopting a configuration Process

3.3 MANAGING CONFIGURATION VERSIONS

1
Regarding configuration version the tool allows the user to set the UC 500 configuration version (parameter
of the loaded Configuration Settings object) but, optionally, also provides the service of updating the
configuration version automatically when changes are made. The user is strongly recommended to enable
5
this feature particularly if an iterative process is used.

5
Note that in the current tool release modifying the Mimics or the Automation modules does not auto-
update the configuration version. In such cases the user must ensure it is manually updated.

3-6 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 4
Chapter

ADDING DEVICES TO PROJECTS

 Chapter 4 - Adding Devices to Projects

INDEX
1
4.1 NEW DEVICES ............................................................................................................................................................ 4-3
4.2 EXISTING DEVICES ...................................................................................................................................................... 4-4

Total pages of the chapter 4

4-2 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 4.1- New Devices

4.1 NEW DEVICES

To add new UC 500 devices to a device project the usual IDE template-based approach is employed (see 4
for details on adding devices to device projects). After selecting the UC 500 device model and desired
template the user is prompted to enter template parameters as well as the device order code. The newly
created device configuration is based on the selected template and some model and order-code related
parameters (see 5.1), such as available serial ports for UC 500 E devices, are automatically setup for you.

Figure 4.1 IED 500 Device Structure Sample

After creating a new device all basic device configuration is ensured by the tool and you can perform any
additional configuration and/or deployment at once.

- UC 500, N. ASID12000063, Rev. 7.1, May 16 4-3

 Chapter 4 - Adding Devices to Projects

4.2 EXISTING DEVICES

1
To add existing UC 500 devices to a project all the IDE mechanisms are supported:

Source How-to
Choose Add Existing Device command from Solution
Live device on the network Explorer context menu, select UC 500 device model
(previously configured by and enter connection parameters. The newly created
Automation Studio Designer) device will extract the current available configuration
on the live device to the project.

Device on the current project or in

Use copy/paste from within the tool.
another project.

Choose Import / Device Package command from the

Device package
File menu.

Choose Import commands from the File menu (see 4

Unmanaged configuration for more information on migrating UC 500
configurations).

Table 4.1 Available options to add existing UC 500 devices

4-4 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 5
Chapter

SETTING-UP SOFTWARE AND

HARDWARE MODULES

The most common step to take after adding a new UC 500 device to a project is to setup hardware-specific
configuration and select software modules to run. This is usually a quick and simple select task because the
tool sets up the correct configuration in most scenarios.
 Chapter 5 - Setting-up Software and Hardware Modules

INDEX
1
5.1 DEVICE MODULE AND ORDER CODE ............................................................................................................................. 5-3
5.2 LOCAL AREA NETWORK I NTERFACES............................................................................................................................ 5-4
5.3 SERIAL PORTS............................................................................................................................................................. 5-5
5.4 SELECTING SOFTWARE MODULES................................................................................................................................ 5-8
5.5 SETTING UP THE MAIN MENU AND TOOLBAR.............................................................................................................. 5-9
5.6 W ATCHDOG.............................................................................................................................................................5-10
5.7 LOCAL CLOCK SYNCHRONIZATION O PTIONS...............................................................................................................5-11

Total pages of the chapter 11

5-2 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 5.1- Device module and order code

5.1 DEVICE MODULE AND ORDER CODE

UC 500 devices may have different hardware options such as platform (generic or embedded PC), number
of serial ports, availability of hardware watchdog, redundant or single configuration, etc. Depending on
these options different software configuration options must, may or may not be setup or enabled.
By selecting the correct order code when you add a new device the tool sets up all hardware-dependent
required settings for you. You may later change the device order code at the Properties Window of a loaded
Configuration Settings.

5.1.1 ADVANCED SETTINGS

Available on the Advanced Settings command of the Configuration Settings context menu (Processes tab) is
the list of system processes that run once the device is started.
Note that these are advanced options that do not require modification in all but very specific cases. The tool
modifies these options automatically according to other settings chosen by the user. Any incorrect editing
of these parameters may disrupt device operation.
Additional UC 500 E specific advanced settings (available on the Advanced Settings command Configuration
Settings context menu, Files tab) allow the user to fine tune flash disk access. When you create a new UC
500 E device these settings are already setup for you targeting the most commonly used scenario.

- UC 500, N. ASID12000063, Rev. 7.1, May 16 5-3

 Chapter 5 - Setting-up Software and Hardware Modules

5.2 LOCAL AREA NETWORK INTERFACES

1
An UC 500 device may provide any number of IP network interfaces, typically (but not restricted to)
Ethernet interfaces. The current version of the tool does not allow configuration or validation of IP
addressing. To properly configure some of the modules the user must set this configuration locally at the
device.

5-4 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 5.3- Serial Ports

5.3 SERIAL PORTS

Depending on device hardware you may need to manually add all required serial ports (as available on the
6
device ). UC 500 device may contain a maximum of 64 serial ports. If you create a new UC 500 E device all
available serial ports are created automatically for you.
Serial ports may be used by communication modules or by local printers and have specific configuration
parameters such as baud rate, stop bits, number of bits per byte, parity or hardware handshaking. For serial
port configuration please select Serial Ports on the device Configuration Settings context menu.

Figure 5.1 Serial port editor

5.3.1 PHYSICAL MEDIUM

To a given serial port you may attach a generic modem, a modem with external radio or a telephonic
modem (if direct cable links are used Modem physical medium should be selected).

Direct cable connection

UC 500 COM COM IED

Serial cable External

UC 500 COM COM
modem

Figure 5.2 Configurations using Modem physical medium (standard modem, direct cable, integrated
radio/modem, PLC modem, etc.)

6
Note that the COM number must correspond to the installed serial port on device.

- UC 500, N. ASID12000063, Rev. 7.1, May 16 5-5

 Chapter 5 - Setting-up Software and Hardware Modules

Serial cable Analog signal

1 UC 500
COM COM
External Radio
I/O modem

PTT/RTS radio control signals

Figure 5.3 Configurations using Radio physical medium (standard modem with external radio)

Serial cable
External
UC 500 COM COM
modem
Phone network

Figure 5.4 Configurations using Telephone physical medium (switched network, GSM, etc.)
The required settings for each physi cal medium type are made available to the user at the serial port editor
by manipulating the toolbar filter or at the Properties Window. As physical mediums may not be supported
by every protocol the configuration validator will detect invalid options.

5.3.2 DUPLEX SERIAL PORT CHANNEL OPERATION

Depending on which module is using the serial port a redundant serial port may also be defined. In such
scenarios the communication channel is physically duplicated (protocol stack is unaware of physical
medium duplication). Several redundancy options exist and may or not be applicable to a given protocol
(read the protocol specific chapter for more information). The configuration validator is capable of
detecting invalid options.
Redundancy options available are:

Option Notes
When set to accept incoming messages on both channels any message received
Receive Mode on either channel is processed. When set to accept messages on active only any
message received on the inactive channel is discarded.
When set to send messages on both channels any message to be sent is
duplicated and sent simultaneously on both channels. When set to send
Sending Mode
messages on active only messages are not duplicated and sent on the active
channel only.
If set the active port is controlled manually by the user (via local user interface or
Manual Mode control). If unset the automatic failure detection mechanisms are employed to
decide which channel should be active at a given moment.
Sets which events are considered to detect channel failure (only used in
Failure detection
automatic switch mode).

Switch Mode Sets when the active port is switched after failure detection (immediately or after
receiving a valid message).
Table 5.1 Options for duplex channel operation

5-6 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 5.3- Serial Ports

5.3.3 ABOUT NETWORKING MODEMS

If your attached modem is used as a networking modem and not as a serial device the interface will not be
available as a COM port but as an IP network interface and would be used like any local area network
interface.

- UC 500, N. ASID12000063, Rev. 7.1, May 16 5-7

 Chapter 5 - Setting-up Software and Hardware Modules

5.4 SELECTING SOFTWARE MODULES

1
The UC 500 software modules can be active or disabled. Modules may be disabled for diagnosis purposes
and should be disabled if not required in a given project.
When a new empty device is created all avail able modules are disabled by default, hence all required
modules should be manually activated. When browsing the loaded Configuration Settings within the
Solution Explorer the user will find all the available software modules. Each module can be activated or
7
disabled in the Properties Window .

Figure 5.5 Module browser at the Solution Explorer

7
Other module configuration parameters are also available at the Properties Window.

5-8 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 5.5- Setting Up the Main Menu and Toolbar

5.5 SETTING UP THE MAIN MENU AND TOOLBAR

Even if you are setting up a gateway or controller configuration without a SCADA user interface please be
sure to check 7.1 on choosing the user interface applications available to the user and the layout of the
main menu toolbar (this is a required step for any configuration).

- UC 500, N. ASID12000063, Rev. 7.1, May 16 5-9

 Chapter 5 - Setting-up Software and Hardware Modules

5.6 WATCHDOG
1
Local software watchdog is used to monitor the operation of each module, thus allowing automatic
recovery procedures to be employed after failure detection. To configure watchdog options for a given
module check the Properties Window when the object is sel ected. The default watchdog options for newly
created devices provide default protection (no changes required in most scenarios). Other common
protection features such as real -time database backup and restart limit are available as parameters of the
loaded Configuration Settings object.
Please note that not all modules support all watchdog options, the configuration validator will issue errors
in such cases.

5-10 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 5.7- Local Clock Synchronization Options

5.7 LOCAL CLOCK SYNCHRONIZATION OPTIONS

After setting up the software modules the user should select the clock synchronization source by simply
setting the corresponding parameter at the Configuration Settings object (only modules that may provide
clock synchronization are shown on the list). If you select no synchronization source the local PC clock will
be used as time source.

- UC 500, N. ASID12000063, Rev. 7.1, May 16 5-11

 6
Chapter

CONFIGURING THE DATA MODEL

The UC 500 data model comprises the setup of all the entities (see 2.7 for an overview of UC 500 entity
types) that are to be available on the device real -time database, as well as the general structuring of the
data model.
Entities are created according to source (see 2.7 for an overview of UC 500 entity sources). Local entities are
created in the Hierarchy View (6.1). Remote entities are created in the corresponding RTU/IED module
editor (9 and 11). Diagnostic entities are handled automatically by the tool when the user creates, deletes
or modifies any configuration object that may contain diagnostic entities.
In case of remote entities a communication structure is employed to organize the entity set: RTU/IED
module, Channel, RTU/IED, etc.8. This is the module structure that is mainly used by the automation
engineer to handle configurations.
Entities may also be structured in a hierarchy of user-defined folders, known as hierarchy levels (6.2). This
structuring of the entity set is usually employed to structure the data model according to system or user
specific rules or functional levels. This structure is usually process related and is used on the unit’s user
interface for filtering or other operator interface purposes. It is therefore focused on the system operator
needs and part of the unit’s configuration.
The data model may also be grouped into areas of responsibility. The system engineer divides the data
model into areas of influence that each system operator manages.

8 The lower levels of this structure depend on the data model of each protocol
 Chapter 6 - Configuring the Data Model

INDEX
1
6.1 THE HIERARCHY VIEW ................................................................................................................................................. 6-3
6.2 HIERARCHY LEVELS ..................................................................................................................................................... 6-4
6.3 ENGINEERING UNITS................................................................................................................................................... 6-5
6.4 AREAS OF RESPONSIBILITY........................................................................................................................................... 6-6
6.5 IEC 61850 MODEL ................................................................................................................................................... 6-9

Total pages of the chapter 9

6-2 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 6.1- The hierarchy view

6.1 THE HIERARCHY VIEW

In the Hierarchy View, the user may see all the entities defined for the selected device. Filtering can be
done by kind of source, type, Id, as well as by hierarchy level. It is an editor where all entities can be edited,
independently of the source.

Figure 6.1 Hierarchy view

- UC 500, N. ASID12000063, Rev. 7.1, May 16 6-3

 Chapter 6 - Configuring the Data Model

6.2 HIERARCHY LEVELS

1
Hierarchy levels are created at the Hierarchy View where the user may create an up to four level deep
folder structure. The hierarchy levels are created and shown in a tree view and the user needs only to
define the name of each level. Hierarchy levels have a unique id for references that is created automatically
9
by the tool but that may also be changed by the user .

Figure 6.2 Hierarchy levels definition

The association of any entity with a given hierarchy level is show in the tool as one of the entity
configuration parameters (the unique hierarchy level id is used as reference). The user may also bring up
the hierarchy level selector from the Properties Window or editor grid to change this entity parameter.

Figure 6.3 Hierarchy levels selector

9
If the hierarchy level id is terminated with a $ character the level is considered to be a system hierarchy
level and is show in different color to the tool user. Such levels usually contain diagnostic entities or
supporting entities (entities that are typically not of interest for presentation on the unit’s operator
interface).

6-4 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 6.3- Engineering Units

6.3 ENGINEERING UNITS

Engineering units can be associated to analogues and counters. After creating those units in the engineering
units view, the user can associate them to an entity through the engineering unit selector.

Figure 6.4 Engineering unit selector

- UC 500, N. ASID12000063, Rev. 7.1, May 16 6-5

 Chapter 6 - Configuring the Data Model

6.4 AREAS OF RESPONSIBILITY

1
The areas of responsibility allow a system engineer to divide the data model into various areas of influence
for a particular system operator, which enables a more contained monitoring and supervision.
An area of responsibility can be associated with one or more entities and/or hierarchy levels and /or mimic
pages/folders. This allows the system engineer to easily group together areas of influence within the data
model. For example, all entities within a specific hierarchy level in the same area of responsi bility.
In version 8.0.0 and above of UC500 an area of responsibility can also be associated with one or more mimic
pages/folders.
There are two ways of associating an entity, a hierarchy level or a mimic page/folder to an area of
responsibility:
1. Using the Areas of Responsibility view, where the user can select entities, hierarchy levels and
mimic pages/folders, or
2. When configuring an entity, hierarchy level or mimic page/folder the user can select the area of
responsibility it should be associated with
In order to use the Areas of Responsibility view, right-click on the loaded configuration settings – a context
menu will appear similar to the one below - and select Areas of Responsibility.

Figure 6.5 Opening Areas of Responsibility

The following view will open, and the user can start configuring Areas of Responsibility.

6-6 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 6.4- Areas of Responsibility

Figure 6.6 Areas of Responsibility view

When the Areas of Responsibility view is opened, the user will be able to add new areas using the add Area
of Responsibility button . Please note the number of areas that can be added
may be limited.
The number of entities, hierarchy levels and mimic pages/folders which can be associated with an area is
10
not limited , and an Area of Responsibility can be associated to many hierarchy level s, entities and mimic
pages/folders at the same time.

Just select an area of responsibility, and press either the Hierarchy Levels button or the
Entities button or the Mimics button .This will enable the user to choose what to
associate with the selected area of responsibility.
As mentioned previously, there’s a different way of associating objects to areas of responsibility and that is
when configuring entities, hierarchy levels or mimic pages/folders. Each entity, hierarchy level or mimic
page/folder has a property named Areas of Responsibility which allows the user to define which areas the
entity, hierarchy level or mimic page/folder is associated with. By editing this property the user is presented
with an Area of Responsibility selector as seen below.

10
Earlier versions of UC500 might limit the number of entities and/or hi erarchy levels

- UC 500, N. ASID12000063, Rev. 7.1, May 16 6-7

 Chapter 6 - Configuring the Data Model

Figure 6.7 Areas of Responsibility selector

An entity, hierarchy level or mimic page/folder can be associated with multiple areas of responsibility.

6-8 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 6.5- IEC 61850 Model

6.5 IEC 61850 MODEL

Automation Studio 3.0 includes an IEC 61850 model on UC 500 devices that are IEC 61850 -8-1 clients. The
SCL model does not have any servers, therefore all logical nodes are under th e access points.
When the configuration is loaded, Automation Studio detects if the UC 500 device has any IEC 61850 -8-1
configuration and it creates the SCL model based on the current configuration. The structure is as follows:
 IED (UC 500 device)
o Access Point (at least one, but each IP configuration will represent an Access Point)
 Logical Node (related to Hierarchy Levels)
By default, for each Hierarchy Level there will be a Telemonitoring Interface Logical Node. However, the
user is able to customize this and determine whether or not the Hierarchy Level should have a
representation on the IEC 61850 model. The user can also modify the type of Logical Node the Hierarchy
Level is represented on the IEC 61850 model (e.g. Telecontrol interface, Human machine interface, user-
specific).
The user can also create specific logical nodes and later assign a Hierarchy Level to that logic al node.
If a logical node is associated with a Hierarchy Level, then whenever there’s a new mapping, the created
entities will be associated with that Hierarchy Level.

- UC 500, N. ASID12000063, Rev. 7.1, May 16 6-9

 7
Chapter

CONFIGURING THE SCADA

MODULES
 Chapter 7 - Configuring the SCADA Modules

INDEX
1
7.1 USER INTERFACE APPLICATIONS AND LAYOUT CONFIGURATION ..................................................................................... 7-3
7.2 EVENT-LOG ................................................................................................................................................................ 7-4
7.3 ALARMS ..................................................................................................................................................................... 7-5
7.4 TRENDS...................................................................................................................................................................... 7-6
7.5 MIMICS ..................................................................................................................................................................... 7-7
7.6 NETWORK TOPOLOGY...............................................................................................................................................7-10
7.7 PRINT-FORMS ..........................................................................................................................................................7-16
7.8 SETTING-UP AUTOMATIC MAINTENANCE OF LOCAL DATABASES .................................................................................7-17

Total pages of the chapter 17

7-2 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 7.1- User interface applications and layout configuration

7.1 USER INTERFACE APPLICATIONS AND LAYOUT

CONFIGURATION

Figure 7.1 GUI advanced settings

Different colors, as defined in the Colors tab, are used to represent multiple objects or object states or
conditions throughout the UC 500 user-interface, such as alarms or entities status or background viewers
based on lists. There are pre-defined color patterns, such as UC 500/ScateX, for a color pattern similar to
initial ScateX applications, Windows, to use the colors of the typical windows of Windows interfaces, or
others.
The descriptive texts available in the Descriptions tab represent static elements of text used throughout the
user-interface and also for logging/alarming purposes.
The user can add and remove buttons from the UC 500 main toolbar, and associate a specific image to them
in the Toolbar tab.
In the Printers tab, the user may define printers (maximum number is 4). Any viewer bas ed in lists can be
printed.
The user can define the descriptions of user bits in the User Bits tab. User bits are additional user setup
status bits available for status entities (in addition to offscan, invalid or overflow status bits).
The user-interface processes (either external tools or HMI processes) to use in a given configuration can be
configured by the user in the Processes tab. Note that user-interface processes can be started upon unit
start-up or are available to start-up at user request and none of them is guarded by the watchdog process.

- UC 500, N. ASID12000063, Rev. 7.1, May 16 7-3

 Chapter 7 - Configuring the SCADA Modules

7.2 EVENT-LOG
1
The events log keeps information on entities state changes, control execution, alarm generation and user
actions like alarm acceptance and beginning and ending of sessions. This log, depending on the
configuration, can be directed to database and/or printer.
The user can add entities to the event log, mapping existing entities.

Figure 7.2 Event log confirmation

7-4 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 7.3- Alarms

7.3 ALARMS

Alarms can be generated by controls execution failure or entities state changes to states considered as
alarm. A control execution failure occurs when a control (or controls sequence) can’t be executed because
of unavailable resources in the central unit, final states failure, interlocking or failed on sending to the
executor process. The alarms generation is configurable individually by possible entity state e by control,
and it can be performed immediately or deferred.
An alarm has individual existence (independently of the entity or contr ol that led to its generation) and a
limited life time. There may be multiple active or inactive, accepted or not accepted alarms for each entity
or control. Alarms keep active during the period on which the entity keeps the state that generated the
alarm. If the entity changes it state to any other, the alarm goes to inactive. The active state of an alarm is
not applicable to alarms generated by failure of controls execution.
The alarms generated by controls execution failure are immediately removed from the alarms database
when accepted by the user. The other alarms can be removed from the database immediately when
crossing to the inactive state or just when they are in the inactive state and accepted. The central unit can
also be configured to keep just the last alarm of each entity.
The alarms have 5 main attributes: priority, description, value, local date and origin date. Priority is a
number between 1 and 255, which indicates the severity of the event that caused the alarm. The
description is a text that identifies the alarm and the value, when available, is the entity value after the
event that caused the alarm. The local date is the date assigned by the central unit on the event detection
that caused the alarm. The origin date, when available, is the date of the event occurrence assigned by the
acquisition unit.
The alarms generator is responsible to insert in the database the generated alarms in the unit and manage
the database.
To create an alarm, the user has to associate it to an entity.

Figure 7.3 Alarms configuration

- UC 500, N. ASID12000063, Rev. 7.1, May 16 7-5

 Chapter 7 - Configuring the SCADA Modules

7.4 TRENDS
1
Trends keep historical information of the entities evolution (digitals, analogues and counters). The trends
record is generated either on-event (upon status entity changed) and also periodically (cyclic).
The user can add entities to trends, mapping existing entities.

Figure 7.4 Trends configuration

7-6 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 7.5- Mimics

7.5 MIMICS

Mimics application can be found within the User Interface configuration .

Figure 7.5 Mimics application

To activate this module on the UC500 configuration go to the Advanced Settings (the configuration must be
loaded) of the Configuration Settings and - if it does not exist already - add an entry with the well-known
WEBSERVER process, after accepting the changes the module should appear as shown on the previous
figure.

Figure 7.6 Mimics module activation

- UC 500, N. ASID12000063, Rev. 7.1, May 16 7-7

 Chapter 7 - Configuring the SCADA Modules

For more information about mimic display configuration, please refer to 2.

1 The mimic display engine in UC 500 devices supports the full mimic object model except for the following
restrictions:
 Fill animation unsupported;
 Write variable actions are not supported;
 Only one navigation action per element is supported;
 Text wrapping is not supported;
 Definition of quality status on mimic animations is unsupported. Onl y values are allowed;
 Different start and end caps are not allowed;
 Standard animations on multistate symbols and numerics are not allowed;
 If a style animation is applied to a text, and its length changes, its background color size doesn't
change with it;
 Silent execution controls are only supported on the version 6.2 or higher.
 Execute control actions do not support the value with expressions.

Note that when a multistate state is introduced as a scripting expression that expression will be rounded to
an integer, for example, if the expression returns 3.3 then the value that the state will hav e will be 3,
because the HMI500 only support integers for the states value.
In the multistate definition users can associate to a state a tagged value with the key UC500_StateDesc and
set the value with a string that should correspond to the description of that same state value in the
database entity configuration. A state can have multiple UC500_StateDesc to support multiple descriptions
for a given state.
The build compiler of the mimic’s will give a warning when it finds an entity that animates a multistate with
a state with a description that is note found in the tagged values of the state, this validation will only occur
when there is at least one Tagged Value with the key UC500_StateDesc ( Case Insensitive).

Starting in the 7.3.1 version of the UC500, the user has the possibility to check the properties of a given
entity of the RTU. The following table describe each properties of the entities can be query in the mimics
configuration.

7-8 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 7.5- Mimics

Property Name Description

Entities

Gets the entity level, in terms of value ranges , values don’t make sense for digital
entity type,
Level
For the analog entity type (0-very low, 1-low, 2-normal, 3-high to 4-very high,
etc.); counter entity type doesn’t have the very low nor low concept.

Gets if the entity is in an alarm state

InAlarm
NOTE: when alarm is inhibited this returns false

IsInvalid Gets if entity value in invalid (usually determined by the equipment).

IsImposed Gets if the entity value is imposed (value forced, usually by an operator).
IsManualOffscan Gets if the entity is in manual offscan (usually performed by an operator)
IsAutoOffscan Gets if the entity is in automatic offscan (usually determined by the equipment)
Gets if the entity value has overflown (usually determined by the equipment)
InOverflow
This attribute only applies to analog and counter entity types.
IsAlarmUnaccepted Gets if the entity alarm state was not acknowledged yet
Controls
IsUnderControl Gets if the control is currently being controlled by an operator.
Table 7.1 Scripting properties

Starting in the 8.3 version of the UC500, the user has the possibility to execute some actions of the HMI500
on a given element of the mimics configuration. The following table describe each action available.

Action Description
Execute Script

acceptActiveAlarmsInPage() Accepts all alarms on the containing page.

Table 7.2 Scripting actions

Note that the scripting properties or the actions available for the device are presented in code snippets in
the editor.

Figure 7.7 Accessing the HMI 500 actions available.

- UC 500, N. ASID12000063, Rev. 7.1, May 16 7-9

 Chapter 7 - Configuring the SCADA Modules

7.6 NETWORK TOPOLOGY

1
The network topology is present on the UC 500 starting from the 8.1 version, to make the module available
the well-known System Process NETTOPOLOGY must be added on the Configuration Settings  Advanced
Settings.

Figure 7.8 Network Topology module activation.

The configuration for the static colors of the topology is made on the User Interface  Advanced Settings
on the Network Topology tab (this is only visible when the module is activated).

Figure 7.9 Static topology colors configuration.

By default, the template of the UC already contains definitions for the static colors , but it is given the
possibility for the user to remove a given color definition.

7-10 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 7.6- Network Topology

To configure the network topology objects on the mimics model just select a given graphic object or a
symbol definition and go to the Property Pad and set the property Type that is under the Network Topology
category (as shown on the Figure 7.10).

Figure 7.10 Object type definition.

After defining the network topology type of the object, the configuration tool will display the specific
property for the chosen type of equipment.

Figure 7.11 Example of specific network topology properties.

As stated before the type of the network topology equipment can be defined also on the symbol definition,
this will state that all instances of that symbol are from the type defined, any properties of the topology
object that are defined on the symbol definition cannot be defined override on the symbol instances. If the
value of the properties are left undefined then they can be set on each instance.
To create connections between the different equipment’s of the topology the connectivity model of mimics
should be used. To learn more about the connectivity model and tools please refer to 2.

7.6.1 NETWORK TOPOLOGY MODEL

On the network topology model all objects that are a part of the topology have a

- UC 500, N. ASID12000063, Rev. 7.1, May 16 7-11

 Chapter 7 - Configuring the SCADA Modules

Type Description
None Object does not belong to the network topology model.
1 Source Cha rge or l oad of the network, element that make the network live or
energized.
Li ne Connectivity nodes that are colored, the elements ca n received a signal from the
Bus Bar IED tha t states if the equipment i s energized or not.
Tra ns former Connectivity node.
Ci rcui t Breaker
Equi pment that will switch the state of the connection. Ca n contain more than 2
Ci rcui t Switch termi nals.
Ea rthi ng Switch
Ea rth Equi pment that will give the s tate Earthed to the network.
Ca pa citor Ba nk
Connectivity node.
Feeder

Ba y
Provi des a means of grouping pieces of equipment together to represent
Sub Network el ectrical containment.
Compound
Object tha t belongs to the network topology but it does not feat on any of the
Other a va ilable types. It is not colored.
Provi des the representation of the electrical device that converts alternating
11
Recti fier current (AC), whi ch periodically reverses direction, to direct current (DC), which
fl ows in only one direction.
Table 7.3 Network Topology types.

A system library containing symbol definitions samples for almost all equipment types described on the
Table 7.3 can be found in the Automation Studio tool.

Figure 7.12 Network Topology System Library.

11
Only available on the UC 8.3 or higher.

7-12 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 7.6- Network Topology

12
State Description Value
Not live Not Energized 0
Live Energized 1
Earthed Earthed 2
Live & Earthed Energized and earthed (abnormal danger situation) 3
Loop Closed path between connectivity nodes 4
Loop & Live Same as the loop state but energized 5
Loop & Earthed Same as the loop state but earthed 6
Loop & Live & Earthed Same as the loop state but energized and earthed 7
Invalid If any of the entities of connectivity nodes have invalid values >= 8
Table 7.4 States description and coloration value.

7.6.2 CONNECTIVITY GRAPH VISUALIZATION (BETA)

It is possible as a Beta functionality, to generate the network topology graph. To enable this feature go to
the IDE options on the Automation Studio.

Figure 7.13 Network Topology generation graph ide option.

If the network topology compiler does not detect any errors, then a file DeviceName.gv will be generated
on the Output mimics folder.

12
These are the values written by the topology engine on the status variables of the lines or busbars.

- UC 500, N. ASID12000063, Rev. 7.1, May 16 7-13

 Chapter 7 - Configuring the SCADA Modules

Figure 7.14 Graphviz model file

13
To export the file generated to a visible image you need to install the GraphViz .
Execute the following command on a Command Prompt to generate the visualization, replacing the
14
parameters that are in italic.

"%programfiles(x86)%\Graphviz2.36\bin\sfdp.exe" -Gsize=200! -Gsplines=true -Goverlap=false -Tpng

source.gv > dest.png

To enable text search in the graph view, export to SVG (scalable vector graphics) using the command , to
view the SVG use a browser (Internet Explorer, Chrome, Opera or Firefox..).

"%programfiles(x86)%\Graphviz2.36\bin\sfdp.exe" -Gsize=60! -Gsplines=true -Goverlap=false -Tsvg

source.gv > dest.svg

This feature allows a fast detection of errors that were not detected by the network topology compiler and
an entire overview of the network topology model.

13
http://www.graphviz.org/, this program is a third party that does not ship with the tool.
14
The Graphviz program path and version depends on the user personal options on the installation, in here
it is used the default options.

7-14 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 7.6- Network Topology

Figure 7.15 Sample of Graphviz output for the Network Topology sample.

- UC 500, N. ASID12000063, Rev. 7.1, May 16 7-15

 Chapter 7 - Configuring the SCADA Modules

7.7 PRINT-FORMS
1
The lists printing is based in layout models named print-forms. A print-form is a text file written i n an
interpreted language (script). This language allows the definition of several kinds of objects, like drawing
objects (lines, rectangles, ellipses with and without text associated, images and regions); one object of list
definition and one object of margins definition. Each UC 500 list viewer based in list will use its own print-
form, it should be named as <process name>.pfr. If this file doesn’t exist, the viewer will use the default
print-form. If neither of them exists, the printing features are inhi bited.
For language definition, please refer to 16.2.

Application Print Form Name

Entities UR5UIEntViewer.pfr
System Log UR5UISysLogViewer.pfr
Alarms UR5UIAlrViewer.pfr
Event Log UR5UIEvtlogViewer.pfr
Trends UR5UIArcViewer.pfr
Table 7.5 Print forms names

7-16 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 7.8- Setting-up Automatic Maintenance of Local Databases

7.8 SETTING-UP AUTOMATIC MAINTENANCE OF

LOCAL DATABASES

All the information of trends and event logs is kept in a database for which periodical automatic
maintenance may be setup. Database maintenance parameter involve: the time and period, directory and
data backup.
After each maintenance action, the database is compacted and repaired, to effectively remove the occupied
disk space.
Note that a maintenance action implies that all runtime processes that access to the database turn off
temporarily, which means that the visualization and generation processes will have no access to the
database while the maintenance is occurring.

Figure 7.16 Database maintenance configuration

- UC 500, N. ASID12000063, Rev. 7.1, May 16 7-17

 8
Chapter

AUTOMATION WITH IEC 61131-3

 Chapter 8 - Automation with IEC 61131-3

INDEX

8.1 AUTOMATION WITH IEC 61131-3 ............................................................................................................................. 8-3

Total pages of the chapter 4

8-2 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 8.1- Automation with IEC 61131-3

8.1 AUTOMATION WITH IEC 61131-3

Automation Module

Figure 8.1 Automation module

For more information about automation configuration, please refer to 1.

The Automation module in UC 500 devices has the following restriction:
 Function SET_ACTIVE_GROUP, of the System library, is not supported.
 Function RESET, of the System library, is not supported.

Programs have two important tools to be referred: “Add Device Variables” and “Create Missing Device
Variables”.
In the “Add Device Variables” tool, the user can select one or more entities from the database and will
create a program variable for each UC 500 entity. By default, this tool will map entity status therefore, in
the “DeviceId” property will appear the entity name with the suffix .stVal. If a control entity is selected it
will be mapped to a control variable in Automation module and no suffix is needed.
In the next table you will find the default mapping from UC 500 entities to Automation variables.

- UC 500, N. ASID12000063, Rev. 7.1, May 16 8-3

 Chapter 8 - Automation with IEC 61131-3

15
Type Sub-type Source Status Mapping
Single Must be mapped to Boolean type from System Library.
By default mapped to the Dbpos enumeration type but can
Double
be other integer type from System Library.
Digital
2-bit Enumerated
3-bit Enumerated Remote By default mapped to an Int32 type but can be other integer
type from System Library.
4-bit Enumerated Local
Diagnostic
Analogue n/a By default mapped to a Float32 type but can be Float64 type
Automation
Counter n/a either.
Command
Control Sequence Must be mapped to a VariableId type from System Library.
Set-point

In entities source is Automation, variables can be input or output in Automation Module. Otherwise,
variable must be input. For control entities, if source is Automation, you can process the control execution
inside the Automation module.

If it is intended to map quality or timestamp from an UC 500 entity, instead of the status, it is necessary to
write in the “DeviceId” property the entity name with the suffix .q or .t respectively instead of the .stVal
suffix.

The “Create Missing Device Variables ” tool will create an entity, with Automation source if kind output and
Local source if kind input, for each input and output variable that refers an entity that does not exist in the
database. Only variables mapped to controls or status will be created in the database.

15
Changing the default mapping of UC 500 entities may result in problems when simulating the entire
device.

8-4 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 9
Chapter

RTU/ IED COMMUNICATION

In all RTU/IED communication protocols configuration, the user is required to create channel objects within
which RTU/LRU or IED objects are to be placed (actual object structure depends on specific protocol
characteristics). RTU/LRU or IED objects are entity containers and represent actual physical devices from
which remote entity values are obtained and controls executed.
Note that there is a hard limit of 255 on the number of channels in given UC 500 device and of 256
RTU/IEDs (of all protocols combined). Other limits on the number of objects may also be in place depending
on protocol or protocol options.
 Chapter 9 - RTU/ IED communication

INDEX

9.1 IEC 60870-5-101 CONTROLLING STATION ................................................................................................................ 9-3

9.2 IEC 60870-5-104 CONTROLLING STATION................................................................................................................ 9-5
9.3 DNP 3 .0 MASTER...................................................................................................................................................... 9-8
9.4 PROCOME MASTER ................................................................................................................................................. 9-9
9.5 MODBUS MASTER ....................................................................................................................................................9-10
9.6 IEC 60870-5-103 MASTER ....................................................................................................................................9-11
9.7 MODBUS/TCP CLIENT .............................................................................................................................................9-12
9.8 SPABUS MASTER .....................................................................................................................................................9-13
9.9 JBUS M ASTER ..........................................................................................................................................................9-14

Total pages of the chapter 14

9-2 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 9.1- IEC 60870-5-101 Controlling station

9.1 IEC 60870-5-101 CONTROLLING STATION

The IEC 60870-5-101 controlling station implements the unbalanced (master -slave) protocol option.
In this protocol, the maximum number of channels that can be configured is 255 and the maximum number
of RTUs is 256. Note that there is only one logical remote unit (LRU) (that corresponding to one common
address of IEC application layer) for each RTU of link layer.
The process communicates via serial port, supporting every physical medium with half or full duplex
operation. It is not possible to establish, for a given channel, distinct baud rates for sending and receiving.
Each serial port can have, as an option, a redundant serial port.

9.1.1 IMPORT CC 101 E MULATED RTU

It is possible to import CC 101 Emulated RTU from another UC 500 into a scanner RTU.
In the first step of the wizard user can chose a device from any project of the current solution.

Figure 9.1 Wizard to select UC500 device to import

- UC 500, N. ASID12000063, Rev. 7.1, May 16 9-3

 Chapter 9 - RTU/ IED communication

In the next step user can select the RTU and define import options :

Figure 9.2 Selection of emulated RTU to import

Configuration will be imported according to options defined previously.

Please note that option Delete Entities should be checked if you want to remove entities present in the
current configuration that does not exist in the RTU to be imported.

9-4 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 9.2- IEC 60870-5-104 Controlling Station

9.2 IEC 60870-5-104 CONTROLLING STATION

In this protocol, the maximum number of channels that can be configured is 255 and the maximum number
of RTUs is 256. Note that there is only one logical remote unit (LRU) (that corresponding to one common
address of IEC application layer) for each RTU of link layer.

9.2.1 IMPORT CC 104 E MULATED RTU

It is possible to import CC 104 Emulated RTU from another UC 500 or from Efacec Devices into a scanner
RTU.
In the first step of the wizard user can chose a device from any project of the current solution.

Figure 9.3 Wizard to select device to import

- UC 500, N. ASID12000063, Rev. 7.1, May 16 9-5

 Chapter 9 - RTU/ IED communication

In the next step user can select the RTU/IED and define import options :

Figure 9.4 Selection of emulated RTU/IED to import

Configuration will be imported according to options defined previously.

Please note that option Delete Entities should be checked if you want to remove entities present in the
current configuration that does not exist in the RTU/IED to be imported.

9-6 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 9.2- IEC 60870-5-104 Controlling Station

The next step is only available in case of selection of Efacec Devices. In this step user can define the rules
that will be applied in ID generation.

Figure 9.5 Wizard to define ID generation rules

Please note that the previously rules may lead to repeated Ids. In order to create all entities and
automatically give the next available Id, the option Resolve Id Conflicts of the step before this should be
checked.

- UC 500, N. ASID12000063, Rev. 7.1, May 16 9-7

 Chapter 9 - RTU/ IED communication

9.3 DNP 3.0 MASTER

In this protocol, the maximum number of channels that can be configured is 255 and the maximum number
of RTUs is 256.
The process can communicate via serial port, supporting modem and radio as physical medium, with half or
full duplex operation. It is not possible to establish, for a given channel, distinct baud rates to both ways.
Each serial port can have, as an option, a redundant serial port.

9-8 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 9.4- PROCOME Master

9.4 PROCOME MASTER

In this protocol, the maximum number of channels that can be configured is 255 and the maximum num ber
of RTUs is 256.
The process can communicate via serial port. It is not possible to establish, for a given channel, distinct
baud rates to both ways. Each serial port can have, as an option, a redundant serial port.

- UC 500, N. ASID12000063, Rev. 7.1, May 16 9-9

 Chapter 9 - RTU/ IED communication

9.5 MODBUS MASTER

Modbus is a master-slave protocol, which implements the telemetry of digitals, analogues and counters,
allowing controls execution of type digital or analogue. The protocol mode can be ASCII or RTU, via serial
port.
Modbus defines 4 memory zones, where IO can be found to be read or changed. Those zones are: Output
Status (from 1 to 10000), Input Status (from 10001 to 30000), Input Register (from 30001 to 40000) and
Hold Register (from 40001 to 48000).
The process polling works configuring the polling time of digitals, analogues and counters. The process will
try to request the memory zones assigned to each one.
The process communicates via serial port, supporting only Modem as physical medium and he doesn’t
support alternative serial port.

9-10 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 9.6- IEC 60870-5-103 Master

9.6 IEC 60870-5-103 MASTER

This protocol is a master-slave protocol, this means the protections will only send data if they are asked to
do so.
This protocol communicates with the protections through a serial port, supporting only Modem as physical
medium and supports alternative serial port. Its main task is to update entities with real time values
obtained from the protections, such as communication status, internal digitals, measures, digital indications
and events.
The process starts automatically and it will initialize all protections, detect communication failures,
synchronize protections, get events, status and analogues, allow remote setting from the command center
and send requested commands to the protections.
The protocol accepts requests from the command center to the protections, and sends them to the
protection channel. It will wait for the protection response and sends that response back to the command
center. This allows communications with all the protections without having to stop the protocol.
There are two types of channels: norma l and bypass. To a normal channel there are protections associated
to it. The protocol will scan all protections in all channels, asking for their status and/or values and then
updating those values in entities. So, for the communications with the protecti ons, a time scanning for each
channel must be defined. A bypass channel will communicate with a command center. The protocol will
“listen” this serial port for messages, send those messages to the channel (normal channel), waits for the
response which will send back to the command center. To this channel, a bypass timeout is defined. The
protocol will wait this time (after a command center has sent a message) for another message from that
command center. If it doesn’t appear, the protocol will proceed with its normal polling to the protections.
After a Bypass Channel ends its polling, the protocol will initialize again the protection.
The protocol knows to which channel it must send the message checking the address of the message sent
by the bypass channel, and finding where is the protection with that address. So, if bypass channels are
used, it’s necessary that all protections have different addresses.

- UC 500, N. ASID12000063, Rev. 7.1, May 16 9-11

 Chapter 9 - RTU/ IED communication

9.7 MODBUS/TCP CLIENT

The UC 500 Modbus driver shall connect to a RTU through a TCP/IP socket, so for each RTU it will exist a
TCP/IP connection to the RTU.
The connection between the UC 500 and the RTU´s are invisible to the UC 500, but some network delays
shall be considered:
• Typical transport delay is about 700ms for few packets transfer
• Typical transport delay after a new open TCP/IP channel is about 1500ms to 5000ms. But in some
cases it can be 60000ms. This time will be configured in the UC 500 database.
The connection management cannot be done in the UC 500, since it cannot access to GPRS modem, so
every time a GPRS connection falls down, the RTU shall initiate the procedure for login in the GPRS network.
Every time the UC 500 ModBus driver try’s to initiate a ModBus transaction like input status polling, and has
no answer, it shall repeat the message after the described transport time timeout. After a maximum retry
number, it shall give the RTU as failed and shall request messages to do general interrogation, since all data
of RTU will be invalidated.
User can define polling maps. A polling map defines a sequence of readings, using two kinds of trigger
methods:
hour scan or cyclic scan.
The hour scan defines that the scanner shall poll the defined zone at the defined hour.
The cyclic scan defines that the scanner shall poll the defined zone in a periodic way.
The check coil is for Pollar only where, before reading the map zone, the scanner shall set that bit and then
reset.

9-12 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 9.8- SPABus Master

9.8 SPABUS MASTER

This scanner allows the use of 32 serial ports, being possible to collect data of 48 ABB modules for each
serial port.
The events, analogues and digitals scan intervals are programmable, becoming possible to optimize the
scanner operation, depending on the number of protections and entities requested to them.
An entity that does not have complementary events associated, on event entity, can be reported only with
timetag information, simply by specifying in its definition that it is pretended to obtain only timetag
information.
Controls can be added to allow the writing in the protections records. To check if the control was
successfully executed, it is possible to associate an analogue to it, which is refreshed with value read from
the record, after the control execution.
The scanner supports several device types already defined, but the user can create more, by choosing the
submenu Device Types in the scanner node.

- UC 500, N. ASID12000063, Rev. 7.1, May 16 9-13

 Chapter 9 - RTU/ IED communication

9.9 JBUS MASTER

The JBus scanner may work in two distinct modes, Events and Digitals.
The scanner allows to program the entities requests that the user want to obtain from an IED. Those
requests are distributed by blocks.
The requests are always executed in words, even if the user only pretends to obtain the value of one bit.
The words attributes must be with the Reg Status enabled, to be seen by the CC.
The channel is going to be associated to a serial port, and in general this is connected to an RS -485
converter, which allows to have several IEDs in the same channel. It should not be mixed IEDs of different
brands in the same channel. In the particular case of SEPAM, synchronism should be activated at the
channel level, to achieve a bigger precision. The “Write Enable” parameter is used to condition the writings
relative to the SEPAM parameterizations.
The device function mode, in the particular case of SEPAM, is usually Events, and the “Read Events”
parameter limits the number of requests of consecutive events made to a SEPAM, if it has many events to
report, thereby limiting the time spent with that SEPAM.
To other IEDs, the function mode should be Digitals, except for EMS SAINCO and SEPAM, which should work
in Events mode.
The “Device Type” parameter should be correctly filled, depending on the IED to use. If the IED type is not
within the available types, the GENERIC type should be chosen.
Counter entities are only used in SEPAM devices.

9.9.1 WORDS

The words to ask an IED can be distributed by 8 blocks. Each of these blocks may have more than one
application set of words. The scan period of each block is defined by the parameter “Scan Block”.
Special blocks:
Block 1/ Fast: This block works like a normal block if the scanner is operating in the Events mode. But if it is
in Digitals mode, then the entities that are in this block are requested with a time scan different than the
other blocks.
General Block: In this block all entities are placed, specially the digital entities that are requested when a
general interrogation is executed.
All Blocks: Entities are requested in all blocks.
8 Odd Blocks Only: Entities are requested only in the odd blocks.
Even Blocks Only: Entities are requested only in the even blocks.

9.9.2 SAINCO LOOP CONFIGURATION

This configuration is only used if the device type is EMS SAINCO.

This is where the user associates the UC 500 digital entities to the entities requested to the SAINCO. Notice
that this device works in the Events mode.
The representation of an invalid loop is via the bit 0 status, which corresponds to the Normal Circuit ID.

9-14 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 Chapter

CONTROL CENTRE
10
COMMUNICATION
 Chapter 10 - Control Centre Communication

INDEX

10.1 CONTROL CENTER COMMUNICATION.......................................................................................................................10-3

10.2 IEC 60870-5-101 CONTROLLED STATION .............................................................................................................10-4
10.3 IEC 60870-5-104 CONTROLLED STATION .............................................................................................................10-5
10.4 DNP 3.0 SLAVE .....................................................................................................................................................10-6

Total pages of the chapter 6

10-2 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 10.1- Control center communication

10.1 CONTROL CENTER COMMUNICATION

Control center communication is setup by creating control center objects (locally representing the actual
remote control center and also the physical or logical communication channel). Control centers contain
emulated RTUs. The UC 500 device is capable of emulating one or more physical RTUs on each channel. UC
500 may contain a maximum of 8 control centers and each of them can only communicate through just one
protocol.
An entity in the UC 500 configuration may be mapped to a given emulated RTU (by selecting it using the
entity selector). Such entity maps include protocol specific options such as data type or protocol data object
address16.

Figure 10.1 Control center communication configuration

16
Please note that if multiple control objects are added in a single operation, the tool automatically verifies
if they should have the same object address, but with different values. In such cases, controls are mapped,
being assigned the same object address hence easily solving the control multiplexing engineering issue
common with most modern protocols.

- UC 500, N. ASID12000063, Rev. 7.1, May 16 10-3

 Chapter 10 - Control Centre Communication

10.2 IEC 60870-5-101 CONTROLLED STATION

This protocol can be defined as the synchronization master, which means that if so, it synchronizes the unit
real-time clock.
This protocol can be a master-master and a master slave protocol (either balanced or unbalanced protocol
options are supported).
The process can emulate, for each control center, several remote units, either on logical layer (RTU) either
on application layer (LRU). This ability allows a flexible and powerful data structuring, important benefit for
applying UC 500 as protocol converter unit or data concentrator. Each emulated RTU of logical layer is
composed by a distinct logical layer entity. The emulated RTUs of application layer associated to an
emulated RTU of logical layer are grouped in one application layer entity. It is possible to have a maximum
of 128 emulated RTUs of logical layer. However, regarding emulated RTUs of application layer, it is possible
to have as many as the addressing space of the protocol allows.
The process can communicate via serial port, supporting every physical medium with half or full dup lex
operation. It is not possible to establish, for a given channel, distinct baud rates to both ways. Each serial
port can have, optionally, a redundant serial port.
UDP support, known as Ethernet, is available for balanced and unbalanced logical layers. This
implementation is limited to proprietary UDP unicast.
There is an application entity (LRU) for each emulated RTU of logical layer. All the emulated RTUs of
application layer share the same application entity that contains 8 transmission queues for pri ority
handling.
Each IEC file (identified by a unique logical address) is mapped uniquely in a file of the files system of the
operative system. A single file can’t be in a state of upload and download at the same time, but several files
can be transferred simultaneously.
For a better performance, the objects addresses for the same kind of object to place in the same queue
17
should be contiguous and in the same range of addresses .

17
Please note that there is a feature that optimizes address space. It is enabled in any object within the
module, except for entities.

10-4 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 10.3- IEC 60870-5-104 Controlled Station

10.3 IEC 60870-5-104 CONTROLLED STATION

This protocol can be defined as the synchronization master.

The process can emulate, for each control center, several remote units, either on logical layer (RTU) either
on application layer (LRU). This ability allows a flexible and powerful data structuring, important benefit for
applying UC 500 as protocol converter unit or data concentrator. Each emulated RTU of logical layer is
composed by a distinct logical layer entity. The emulated RTUs of application layer associated to an
emulated RTU of logical layer are grouped in one application layer entity. It is possible to have a maximum
of 128 emulated RTUs of logical layer. However, regarding emulated RTUs of application layer, it is possible
to have as many as the addressing space of the protocol allows.
There is an application entity (LRU) for each emulated RTU of logical layer. All the emulated RTUs of
application layer share the same application entity that contains 8 transmission queues for priority
handling.
Each IEC file (identified by a unique logical address) is mapped uniquely in a file of the files system of the
operative system. A single file can’t be in a state of upload and download at the same time, but several files
can be transferred simultaneously.
For a better performance, the objects addresses for the same kind of object to place in the same queue
17
should be contiguous and in the same range of addresses .

- UC 500, N. ASID12000063, Rev. 7.1, May 16 10-5

 Chapter 10 - Control Centre Communication

10.4 DNP 3.0 SLAVE

This protocol can be defined as the synchronization master.

The process can emulate, for each control center, several remote units. It is possible to have a maximum of
128 emulated RTUs.
The process can communicate via serial port, supporting every physical medium with half or full duplex
operation. It is not possible to establish, for a given channel, distinct baud rates to both ways. Each serial
port can have, optionally, a redundant serial port.

10-6 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 Chapter

11
LOCAL AREA NETWORKING AND
DISTRIBUTED AUTOMATION
 Chapter 11 - Local Area Networking and Distributed Automation

INDEX

11.1 NTP CLIENT...........................................................................................................................................................11-3

11.2 IEC 61850-8-1 CLIENT .........................................................................................................................................11-4
11.3 SNMP MANAGER .................................................................................................................................................11-7

Total pages of the chapter 7

11-2 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 11.1- NTP Client

11.1 NTP CLIENT

NTP client can be defined as the synchronism master. The user can define several local interfaces and NTP
servers as well.
NTP process is an NTPv3 client, limited to unicast mode, which allows the central unit synchronization to
take as synchronism source one or more NTP servers.

- UC 500, N. ASID12000063, Rev. 7.1, May 16 11-3

 Chapter 11 - Local Area Networking and Distributed Automation

11.2 IEC 61850-8-1 CLIENT

This protocol uses a mapping of entities in MMS format and not in IEC 61850, this is due to the fact that a
MMS stack is used and the requests are done in MMS. The difference between those two formats relates to
the inclusion of the Functional Constraint in the string that identifies the entity. The Functional Constraint
characterizes the services that are allowed on a certain Data Attribute.
IEC 61850 allows mapping IEC entities in UC 500 entities. IEC 61850 may work with cyclic requests of
entities and Reports Control Block or just one of them.

11.2.1 SCL IMPORT WIZARD

All IEC 61850 compliant devices have a corresponding SCL file containing the description of the device
database (this file can alternatively be generated by the device tool). Such files are produced according to
the IEC 61850-6 XML format that may be imported by this tool to automatically generate the IEC 61850
entities and protocol -specific configuration. The wizard can be found on the toolbar of the IEC 61850 -8-1
configuration window.
To use the wizard the first step is to select and open the SCL file to import (the wizard is capable of reading
any SCL file type (CID, ICD, SSD, SCD, etc.).
In the second step the user selects required data objects from the SCL file (any set of complex data objects
or simple data attributes may be selected).

Figure 11.1 Object selection step

The third and last step is to review generating options. Several options are available that let you have
control of what gets generated (entity identifier, types, reports, etc.).

11-4 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 11.2- IEC 61850-8-1 client

Figure 11.2 Review options step

After pressing the finish button the wizard generates all the necessary entities for the selected IEC 61850
18
data objects, as well as any required configuration elements (device, logical device and report control
blocks with all required parameters, descriptions, engineering units and initial values). Please refer to 16.6
for additional information on using this wizard.
By using the SCL import wizard the user is able to quickly and interactively setup the IEC 61850 client
module by simply selecting the required data objects according to the system specificati on.

11.2.2 SCL E DITOR

As of version 3.0 of Automation Studio, the configuration of IEC 618850 -8-1 in UC 500 can also be carried
out using the SCL editor. For more information about the SCL editor please read IEC 61850 and Third-Party
Devices manual.
In UC 500, the SCL editor is client-based which means datasets and control blocks cannot be created. The
user is able to configure the data flow of Reports in much the same way as with the SCL Import Wizard.
Please read chapter 6.5 to learn how to build the SCL model and how it relates to the hierarchy level.
The following example shows the data flow configuration of a UC 500 device, with multiple inputs being
received by report. Each circle represents one or more associations. The user can double-click on an
association and it will expand to the first association found.

18
Depending on this information being available on the input SCL file.

- UC 500, N. ASID12000063, Rev. 7.1, May 16 11-5

 Chapter 11 - Local Area Networking and Distributed Automation

Figure 11.3 Data Flow configuration example

The columns represent the access points available in the UC 500 model, followed by logical nodes and
finally external references. Each external reference represents an association between an input and an
entity.

By pressing the button the user can control how the entities are named when mapping the new input.
A wizard similar to the one mentioned above in Figure 11.2 is shown.
The user is able to configure multiple inputs more easily and inspect the flow of information quite rapidly
using this editor.

11-6 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 11.3- SNMP Manager

11.3 SNMP MANAGER

SNMP manager is a communications process that implements the SNMP communications protocol.
In this process, the maximum number of channels that can be configured is 255 and the maximum number
of RTUs is 256.
The process can emulate, for each communication channel, several agents. Each agent has a community
key, which is the community identifier where the SNMP Manager is going to get connected to the agent.
This process supports SNMPv1 and SNMPv2 versions of the protocol.
SNMP supports the needed functionalities for an implementation of a Network Management Station. The
supported services are reading, writing and event reception (traps).

- UC 500, N. ASID12000063, Rev. 7.1, May 16 11-7

 Chapter

SAVING, BUILDING AND

12
VALIDATING YOUR
CONFIGURATION
 Chapter 12 - Saving, Building and Validating your configuration

INDEX

12.1 SAVE PROCESS .......................................................................................................................................................12-3

12.2 VALIDATE PROCESS ................................................................................................................................................12-4
12.3 BUILD PROCESS......................................................................................................................................................12-5

Total pages of the chapter 5

12-2 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 12.1- Save Process

12.1 SAVE PROCESS

When the user loads a configuration, a copy of the database is created and all the changes the user makes
are kept in that copy. When the user saves the configuration, those changes are copied to the main
database, and it is compacted.

- UC 500, N. ASID12000063, Rev. 7.1, May 16 12-3

 Chapter 12 - Saving, Building and Validating your configuration

12.2 VALIDATE PROCESS

The validate process can be full or partial. The user may validate the entire device, or one module that
belongs to it. The validate process is enabled in UC 500 devices and in all its modules and objects.

12-4 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 12.3- Build Process

12.3 BUILD PROCESS

The build process can be full or partial. The user may build the entire device or one module that belongs to
it. The build process is enabled in a few modules of the UC 500 device.

- UC 500, N. ASID12000063, Rev. 7.1, May 16 12-5

 Chapter

14
COMMUNICATING WITH THE
DEVICE
 Chapter 13 - Communicating with the device

INDEX

13.1 CONFIGURATION SETTINGS.....................................................................................................................................13-3

13.2 SYSTEM LOG ..........................................................................................................................................................13-4

Total pages of the chapter 4

13-2 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 13.1- Configuration Settings

13.1 CONFIGURATION SETTINGS

For handling the device configuration, the following commands are available:

 Deploy Configuration: The deploy command deploys the device configuration to the device using
the address defined in the default connection.

 Get Configuration: The get command gets the configuration from the device using the address
defined in the default connection, to the selected device.

 Reset Defaults: Restores the factory configuration on the connected device. This does not affect
your current configuration and requires the user to perform a “Get Configuration” command to
update the local configuration.

 Restore Previous Configuration: Restores the device to the configuration before the last one that
was sent by the user. This does not affect your current configuration and requires the user to
perform a “Get Configuration” command to update the local configuration.

These commands allow the user to communicate with the device. They all need a defined connection, and
the user will be asked to give a user name and a password, so the user must be authorized to access the
device. This commands run externally. The user can follow the process in the Task Manager pad, and check
for any errors that may occur in the Output Window pad.
In versions of UC 500 under 6.1.0 a first deploy may fail if file “device.manifest” is missing in the device. If
this problem occurs user can simply copy manually this file located in folder “Configuration” of local device
to folder “Config$” shared in remote UC 500. This operation only need to be done one time, and only if the
this error occurs.
In versions of UC 500 previous to 7.2.0, in redundant configurations, the “Deploy Configuration” action of
configurations must be done twice, one for each unit. If the CLP500.ini file is also included in the action, it
must be modified before each deploy to ensure that the configuration of main and backup unit are
maintained.

- UC 500, N. ASID12000063, Rev. 7.1, May 16 13-3

 Chapter 13 - Communicating with the device

13.2 SYSTEM LOG

For handling the system log, the following command are available:

 Get System Log: Retrieves the system logs available on the device, overriding any previous file that
may have already been retrieved before.

In device with firmware version up to 6.1.2 the following files are retrieved:
 Error.log: Provides information about errors that may have occurred during device operation.

 Process.log: Provides information on processes/modules that are running on the device.

 Wdog.log: Provides information on the device watchdog behavior.

After that version until version 8.0.0, the following file is also available

 CfgSrvLog.log: Provides information regarding device interaction done through the management
interface.

In version 8.0.0 and above UC500 has a System Reporting Tool .

This tool configuration is in file “srt.conf”, located in device folder, and that can be edited manually.
This file is sent to the device when Getting System Log and the files generated by the System Reporting Tool
are retrieved.

13-4 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 Chapter

14
PRODUCTIVITY AND REFACTORING
TOOLS
 Chapter 14 - Productivity and Refactoring Tools

INDEX

14.1 PRODUCTIVITY AND REFACTORING TOOLS ...............................................................................................................14-3

14.2 SAFE MODIFICATION OF ENTITY I DENTIFIERS ...........................................................................................................14-5
14.3 HANDLING DESCRIPTIVE DATA ................................................................................................................................14-6
14.4 CONFIGURATION COMPARISON TOOL .....................................................................................................................14-7
14.5 AUTOMATION O BJECTS ..........................................................................................................................................14-8

Total pages of the chapter 9

14-2 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 14.1- Productivity and Refactoring Tools

14.1 PRODUCTIVITY AND REFACTORING TOOLS

Tool Description

Copy-paste The user may copy and paste any UC 500 device and most objects on it, between
devices and between IEDs, spread sheets, etc…Please refer to 4.
The user may import and export device packages and import an UC 500 database.
Import/Export To be sure that the imported database is consistent within UC 500 features, refer
to 3.
19
Id replacer The user may replace entity identifiers of several objects within the device.
19
Translator The user may translate descriptions of several objects within the device.
19
Comparer The user may compare databases.
Optimize database The user may optimize the database of the selected device.
Statistics The user may see statistics about objects within the device
Table 14.1 Productivity tools
Most of these tools are at the Tools item in the context menu of the Configuration Settings, note that the
majority of the features described here are only available in the Designer Edition.

Figure 14.1 Configuration settings tools

19
Only available on Designer Edition.

- UC 500, N. ASID12000063, Rev. 7.1, May 16 14-3

 Chapter 14 - Productivity and Refactoring Tools

The refactoring tool is very useful. When the user modifies an entity identifier, he will be asked if he wants
to apply changes to Final State Equations, Inhibition Conditions, Automation and Mimics modules, note that
this functionality is only available in the Designer Edition.

Figure 14.2 Refactoring window

If the user selects to not be asked again, there is the possibility to change that at any time, in the Options of
the Tools menu.

8
Figure 14.3 Refactoring options
The same applies to Control Centers identifiers.

14-4 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 14.2- Safe Modification of Entity Identifiers

14.2 SAFE MODIFICATION OF ENTITY IDENTIFIERS

To safely modify entity identifiers, the user should choose all the options at the refactoring window options
or in the item Options of the Tools menu. For a more comprehensive replacement, the user may use the
wizard to replace entities identifiers.

Figure 14.4 Id replacer wizard

If the first option is selected, all the entities ids will be extracted to a CSV file. In the second option, the user
may choose a CSV file on which the second column will replace the id that is in the first column. The third
option allows the user to choose a pattern and replace by a string. To learn more about patterns, refer to 4.

- UC 500, N. ASID12000063, Rev. 7.1, May 16 14-5

 Chapter 14 - Productivity and Refactoring Tools

14.3 HANDLING DESCRIPTIVE DATA

If the user wants to translate several descriptions, the better way is to use the Translate tool. It works
exactly like the id replacer wizard but performs integrated replacement on descriptive texts.

14-6 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 14.4- Configuration Comparison Tool

14.4 CONFIGURATION COMPARISON TOOL

The user can compare the selected device database with another da tabase, including Mimics also.

- UC 500, N. ASID12000063, Rev. 7.1, May 16 14-7

 Chapter 14 - Productivity and Refactoring Tools

14.5 AUTOMATION OBJECTS

An Automation Object is a reusable element that contains a set of pre-configured device-specific

configurations.
The creation of Automation Objects is available in menu Tools in Configuration Setti ngs node and in Mimics
Symbols.
User can choose what objects of the current configuration wants to include in the Automation Object.

Figure 14.5 UC 500 Selector Form

Tools Options

If true, missing entities of checked entity maps in Control Centers will

Include Entities
be included.

Remember Include Entities If false, the user will be asked whether or not to include missing
Decision entities of checked entity maps in Control Centers .
8 If true, missing maps of selected entities in checked Control Centers
Include Missing Maps
communication objects will be included.

If false, the user will be asked whether or not to include missing

Remember Include Maps Decision
entity maps.

Define which properties are included when creating Automation

Object:
Export Properties - All
- Only different from default values
- Only different from default values defined by user

If true, Create UC 500 Model command will update existing objects

Update Existing Objects
with templates values.

Table 14.2 Templating options

14-8 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 14.5- Automation Objects

14.5.1 AUTOMATION OBJECTS IN S YMBOLS

If Automation Object was created in a Symbol, a new file will appear next to the symbol, with the extension
“.uc500.src”.

Figure 14.6 Automation Object associated to a symbol

User can edit this file, replacing fields by the keywords defined in the symbol.
For example, if symbol has defined a keyword “panelNr”, user needs to replace in the file the fields for
“$panelNr$”.
When inserting the symbol in a Page, a form will appear to define the values that the keywords will be
replaced. Then, by right clicking in the symbol inserted, user can access in Tools to menu “Create UC 500
Model”. This action will update the current configuration with the information contained in Automation
Object file.

14.5.2 AUTOMATION OBJECTS IN DEVICE TEMPLATES

Other option to use Automation Objects is when adding new device. In this case the device will be created
according to the template chosen and with the configuration defined in the Automation Object (this file has
to be included manually in the template folder by the user).
If Automation Object was created in “Configuration Settings” node, a new file with the extension
“.uc500.src” will be saved in a location chosen by user.
This file can be included in Device Templates, in folder Configuration. Can be included more than one file,
they will be processed by alphabetic order.
As explained before, this file can be edit. In this case the keywords will be the ones defined in device
template creation, and will be replaced when creating a new device.
More information about Device Templates and keywords can be found in Automation Studio User Manual:
chapter 5.9.

- UC 500, N. ASID12000063, Rev. 7.1, May 16 14-9

 Chapter

USING EXTERNAL TOOLS 15

It is also possible, although not recommended, for advanced users to perform direct database editing with
external tools via SQL or ODBC interfaces. Please refer to 3 for rules, procedures and advice on performing
external database editing.
 Chapter 15 - Using External Tools

INDEX

15.1 DATA MAP TOOL ...................................................................................................................................................15-3

Total pages of the chapter 6

15-2 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 15.1- Data Map Tool

15.1 DATA MAP TOOL

It is possible to import and export data maps using an excel spreadsheet with the entities configuration.
The user can access this tool using the File menu or the Tools menu of the Configuration Settings.

 Export Data Map

Figure 15.1 Export data map wizard

The user chooses the file where he wants to save the data map. The allowed formats are Excel 97 -2003 or
2007.
There are two actions available: Device Data Map, that generates a data map with all available entities; and
Empty Data Map, that generates an empty data map template that can be used to define entities and
import them using the import data map command.

 Define Data Map

Using the template that can be exported, the user may define entities to later import them.
In the Hierarchy Map tab, the user may define the hierarchy level s. But there is one restriction. It
must start with the parent, followed by its children, like the example below:

Hierachy Levels
Name Parent
HLName HLParent

SE
220kV SE

- UC 500, N. ASID12000063, Rev. 7.1, May 16 15-3

 Chapter 15 - Using External Tools

65kV SE
P601 65kV
P602 65kV
P700 220kV
Table 15.1 Hierarchy levels definition
In the Config tab, the user may define which parts will be used to define the entity identifiers, and which
limits and codes can be used, so the generated identifiers can be valid and structured.

Figure 15.2 Config tab

In the Data Map tab there are all the parameters that can be set to generate correctly the entities.

Part 1-16 Full Identifier

8 .Custom

The user may fill this This columns use the definitions Represents the full entity
column if he wants to created on the Config tab to allow the identifier, concatenating
define the entity user to define entity identifiers based all existent parts.
identifier. on the rules specified.
Table 15.2 Entity identification

Type
The user may choose the type of entity. If entity is a local control or set-point, this value is
ignored because the control type is defined by the type of entity associated with it.
Table 15.3 Entity type

15-4 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 15.1- Data Map Tool

Hierarchy Level Unit State Description

User
Description
The user may The user may choose the The user may define The user may define
define the hierarchy level defined, or the unit to which descriptions for each
entity write the tree path to the analogue entity state.
description. achieve the wanted level, in will be associated. If
case of equal descriptions. the unit does not
E.g.: SE\220kV\P700. exist, it will be
created.
Table 15.4 Description

SOE Printer
Alarm
The user may define if an The user may define if an The user may define if the
alarm will be generated for event log will be generated output will be a printer. If so, it
the entity. for the entity. will be associated to Printer 1.
Table 15.5 HMI

CC 1-8
The user may map the entity to a control center. In this case, the control center must exist in
the configuration to where the data map will be imported. If there is at least one rtu/lru
defined, the entity will be mapped to the first one. Otherwise, an rtu/lru will be created. The
user may write the object address to use for the map, or ‘X’ to generate automatically an
address.
Table 15.6 Control center
The user must choose the module to which associate the entity.

Channel RTU/IED LRU/LD Function Data/Object Value

Module
Address
IEC 61850 Doesn’t IED LD MMS tag, separated by If entity is a
exist. identifier. identifier. ‘$’. control, is the
IEC 60870- Channel RTU Doesn’t Object address, value to use
5-101 identifier. identifier. exist. separated by ‘.’. when control
IEC 60870- Channel RTU Doesn’t Object address, is executed.
5-104 identifier. identifier. exist. separated by ‘.’. Otherwise, it
Channel RTU Doesn’t Function Information is the initial
IEC 60870- value of the
5-103 identifier. identifier. exist. type. number.
entity.
ModBus Channel ModBus Doesn’t If entity is Memory
identifier. device exist. digital or address.
identifier. control, it
represents
the index.
DNP 3.0 Channel RTU Doesn’t Doesn’t Logical
identifier. identifier. exist. exist. address.
SNMP Channel SNMP Doesn’t OID, separated by ‘.’.
identifier. agent. exist.
Diagnostic Not supported.
Local Ignored. If entity is a If control is a
control, it command, it
represents represents
the entity to the value to
which it is be written in
associated. the

- UC 500, N. ASID12000063, Rev. 7.1, May 16 15-5

 Chapter 15 - Using External Tools

associated
entity.
Automation Ignored.
Table 15.7 Source
 Import Data Map

Figure 15.3 Import data map wizard

The user chooses the data map file to import.
In the Entities box, there are three available options: the Add option will add the entities that don’t exist;
the Update option will update the entities that already exist in the configuration; the Remove option will
remove the entities from the configuration that don’t exist in the data map.
In the Update box, there are five available options: the Entities Type will update the type of entity; the
Descriptions will update all entity descriptions; the HMI will update alarms, event logs and printers; Control
Centre will update the control center to which the entity will be mapped; and the Source Definition will
update the module, channel, RTU/IED, LRU/IED, function, data/object address and value.

8 For all parameters, except control centers, if they don’t exist, they will be created during the import
operation.
In the Import box, there are two available options: Entities will add/update/remove entities to/from th e
configuration and H. Levels will add/update/remove hierarchy levels from the configuration, accordingly to
the options specified in the Entities box.

15-6 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 Chapter

ANNEXES
16
 Chapter 16 - Annexes

INDEX

16.1 PRINT FORM DEFINITION MINI-LANGUAGE SAMPLE ................................................................................................16-3

16.2 CONTROL I NHIBITION MINI-LANGUAGE DEFINITION.................................................................................................16-6
16.3 CONTROL FINAL -STATE MINI-LANGUAGE DEFINITION ..............................................................................................16-7
16.4 CONVERSION FUNCTION MINI-LANGUAGE DEFINITION............................................................................................16-8
16.5 ADVANCED USAGE OF THE IEC 61850 SCL I MPORT W IZARD..................................................................................16-9
16.6 IDE O PTIONS...................................................................................................................................................... 16-13
16.7 PRIVATE EXTENSIONS .......................................................................................................................................... 16-14

Total pages of the chapter 14

16-2 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 16.1- Print Form Definition Mini-Language Sample

16.1 PRINT FORM DEFINITION MINI-LANGUAGE

SAMPLE

#
# SIMPLE
#
# This is a very simple example for a print form. It contains no images
# and has no text references to any particular list.
#
# Top and bottom page margins are one centimeter wide.
# Left and right page margins are two centimeters wide.
#
MARGINS(20,10,20,10);

#
# The header contains the list title only
#
RECTANGLE(0,0,100%,8) {
PEN(NoNe);
BRUSH(NONE);
TEXT(" <title>");
FONT("Arial",12, BOLD, NO, NO, NO, RGB(0,0,0));
}

#
# The footer contains the page number, the page count and the project name
#
REGION(0,-5B,100%,100%) {
LINE(0,0,100%,0) {
pen(solid, 0.1, RGB(0,0,0) );
}
RECTANGLE(0,0,50%,100%) {
PEN(NoNe);
BRUSH(NONE);
TEXT("<project name>", LEFT, BOTTOM, NO, 0, 0);
FONT("Arial",8, NORMAL, NO, NO, NO, RGB(0,0,0));
}
RECTANGLE(50%,0,100%,100%) {
PEN(NoNe);
BRUSH(NONE);
TEXT("Page <page number> of <number of pages>", RIGHT, BOTTOM, NO, 0, 0);
FONT("Arial",8, NORMAL, NO, NO, NO, RGB(0,0,0));
}
}

- UC 500, N. ASID12000063, Rev. 7.1, May 16 16-3

 Chapter 16 - Annexes

#
# On top of the list are the line numbers of the current page
#
RECTANGLE(0,10,100%,15) {
PEN(NoNe);
BRUSH(NONE);
TEXT("Lines <first line> to <last line>",RIGHT, MIDDLE, NO, 0, 0);
FONT("Arial",10, BOLD, NO, NO, NO, RGB(0,0,0));
}

#
# The list...
#
LIST (0, 15, 100%, -7B) {
#
# The list head prints general information regarding the report (printed on first
# page only):
# 1) the source application,
# 2) the user who printed the list, and
# 3) the date the list was printed.
#
LISTHEAD (18) {
#
# First draw the information description (bold font)...
#
RECT(0,0,100%,5) {
pen(NONE); BRUSH(NONE);
TEXT("Source:", LEFT, MIDDLE, YES, 0, 0);
FONT("Arial",10, BOLD, NO, NO, NO, RGB(0,0,0));
}
RECT(0,5,100%,10) {
pen(NONE); BRUSH(NONE);
TEXT("User:", LEFT, MIDDLE, YES, 0, 0);
FONT("Arial",10, BOLD, NO, NO, NO, RGB(0,0,0));
8 }
RECT(0,10,100%,15) {
pen(NONE); BRUSH(NONE);
TEXT("Date:", LEFT, MIDDLE, YES, 0, 0);
FONT("Arial",10, BOLD, NO, NO, NO, RGB(0,0,0));
}
#
# ...then draw the information (normal font)
#
RECT(16,0,100%,5) {
pen(NONE); BRUSH(NONE);
TEXT("<application>", LEFT, MIDDLE, YES, 0, 0);
FONT("Arial",10, NORMAL, NO, NO, NO, RGB(0,0,0));
}

16-4 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 16.1- Print Form Definition Mini-Language Sample

RECT(16,5,100%,10) {
pen(NONE); BRUSH(NONE);
TEXT("<user name> (<user full name>)", LEFT, MIDDLE, YES, 0, 0);
FONT("Arial",10, NORMAL, NO, NO, NO, RGB(0,0,0));
}
RECT(16,10,100%,15) {
pen(NONE); BRUSH(NONE);
TEXT("<date and time>", LEFT, MIDDLE, YES, 0, 0);
FONT("Arial",10, NORMAL, NO, NO, NO, RGB(0,0,0));
}
}
#
# The list header has black background and white text
#
LISTHEADER (5) {
pen(solid, 0.01, RGB(0,0,0) );
BRUSH(RGB(0,0,0));
FONT("Arial",10, BOLD, NO, NO, NO, RGB(255,255,255));
TEXT("", LEFT, MIDDLE, NO, 1, 0);
}
#
# The list lines have white background and black text
#
LISTLINES (5) {
pen(solid, 0.01, RGB(80,80,80) );
BRUSH(NONE);
FONT("Arial",8, NORMAL, NO, NO, NO, RGB(0,0,0));
TEXT(LEFT, MIDDLE, NO, 1, 0);
}
#
# There is no list tail
#
LISTTAIL (0);
}

- UC 500, N. ASID12000063, Rev. 7.1, May 16 16-5

 Chapter 16 - Annexes

16.2 CONTROL INHIBITION MINI-LANGUAGE

DEFINITION

Syntax: <cond> [<op> <cond>] [... <op> <cond>]

Where:
<cond>:
| NOT <cond> Logical Negation
| <ent> = <int> Value (digitals only and any source)
| VAL(<ent>,<int>,<src>) Value (digitals only)
| <fun>(<ent>,<src>) Function
<op>
| AND|OR|XOR|NAND|NOR|NXOR
<fun>:
|I Invalid
| L, LL Low levels (analogues)
| N, H, HH High Levels(analogues and counters)
<ent>:
| ENTITYID Allowed characters only
| [ENTITYID] Any characters
<src>:
|<empty> Any source
| CC1, CC2 ... CC8 Specific CC
| CC Any CC
| AUT Automation
| USR User interface
| SEQ Sequence

16-6 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 16.3- Control Final-state Mini-language Definition

16.3 CONTROL FINAL-STATE MINI-LANGUAGE

DEFINITION

Syntax: <cond> [AND <cond>] [... AND <cond>]

Where:
<cond>:
| <ent> = <int> Value (digitals only)
| <ent> = <float> Value (analogues or counters)
| (<ent> >= <float> AND <ent> <= <float>) Value Range (analogues or counters)
<ent>:
| ENTITYID Allowed characters only
| [ENTITYID] Any characters

- UC 500, N. ASID12000063, Rev. 7.1, May 16 16-7

 Chapter 16 - Annexes

16.4 CONVERSION FUNCTION MINI-LANGUAGE

DEFINITION

Direct Linear Polynomial Piecewise Linear

Syntax f(x) = x f(x) = mx+b f(x) = anxn + an-1xn-1 + ... + f(x) = [P1x;P1y][P2x;P2y]
a1x1 + a0
Example x Slope:2; Coefficient:2; Exponent:3 P1(0,2)
Offset:3 2x
3 P2 (3,4)
2x+3 [0;2][3;4]

Note that in piecewise linear, you may have a maximum of 4 points and the minimum is 2 points; x and y
are the point coordinates.

16-8 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 16.5- Advanced Usage of the IEC 61850 SCL Import Wizard

16.5 ADVANCED USAGE OF THE IEC 61850 SCL

IMPORT WIZARD

The starting point and most relevant input is the source SCL file. The tool supports any SCL file type to be
imported but please ensure that you select a CID or SCD file after device configuration is complete in order
to have more information to start with. The wizard will not be able to automatically generate all required
information if required elements are missing in the SCL input file.

16.5.1 WORKFLOW

The next figure summarizes tool usage workflow.

Figure 16.1 SCL import tool architecture and workflow

To overcome limitations in the input source files the tool combines information obtained from the user -
provided file with the installed domain models in order to build a complete image of all objects available at
20
the IED(s). This includes names, structure as well as descriptions and type information . The standard
domain models for IEC 61850 Ed. 1 and the EFACEC-specific models for the x420 device series are installed
with the tool. Other domain models can be added by the user or tool updates.
This merged information, together with the data object selection list, is used as input to the generator that
adds to the existing UC 500 configuration.

16.5.2 GENERATION RULES

When the wizard is finished the tool generates all the module structure elements and entities required to
map the selected IEC 61850 data objects to the device configuration.
The user may (and should in most cases) select top-level data objects on each logical node. For each
selected data object the type and number of entities that should be generated are determined based on the
Common Data Class (CDC) of the source object and the descriptive potential of the UC 500 data model. The

20
Note that information on the source SCL file takes precedence over information from the domain models
(the domain models are used to fill in the gaps).

- UC 500, N. ASID12000063, Rev. 7.1, May 16 16-9

 Chapter 16 - Annexes

algorithm works with any CDC, even if not known, yielding the best possible results. For an overview of
some result mappings check the table below:

CDC Typical Number and Type of Entities Generated

SPS 1 Single Digital

SPC 1 Single Digital and 2 Commands (open / close)

MV 1 or more Analogues

BCR 1 Counter (and possibly other supporting entities)

CMV 1 or more Analogues

INS 1 Enumerated (or Analogue, depending on object data type)

1 Enumerated (or Analogue) and 2 or more Commands

INC
(depending on object data type)

Table 16.1 Overview of some possible mappings from IEC 61850 data objects to UC 500 entit ies
The generator also provides the possibility of selecting data attributes. You should use this option only if
you want to fine tune the entity set that gets generated. The tool will generate only one entity for each IEC
61850 leaf attribute of the most suitable type (except for commands where usually more than one control
is required).

16.5.3 CONTROLLING GENERATOR OUTPUT THROUGH IMPORT OPTIONS

The generator not only creates the appropriate entity set but also all the container objects required with all
the correct parameters, namely devices, logical devices and addressing configuration.
For each entity in the created set the generator also sets some of the parameters automatically (if
available):
 Description of the entity (and applicable states for digital da ta points)
 Engineering units (for analogue and counter data points, creating new units if non-existent)
 Entity identifier (according to a given pattern)
 Initial value (cold start value) for data entities
 Hierarchy level (user provided hierarchy level)
The wizard provides options to enable or modify all of the parameters described above as well as the option
to generate controls, status data entities or both. If you decide to generate report control blocks a report
control block object is also added if any of the created entities are available at the control block's dataset (if
8 non-existent).

16.5.4 STEP-BY-STEP OR ITERATIVE CONFIGURATION

All of the import and select wizard options are kept between each call of the wizard (including the input
source file) so creating the database step-by-step is as simple as repeating a click-select-go process until you
have all your required database setup.

16-10 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 16.5- Advanced Usage of the IEC 61850 SCL Import Wizard

Figure 16.2 SCL object selection window

The selection window is compos ed of a toolbar and a resizable tree/list view much in the Windows Explorer
style. The tree view lets you navigate through the SCL objects (SCL File, Device, Server, Logical Device,
Logical Node, Data Object and/or Sub-Data Object). As you navigate through the object model all the
contained data objects are show in the list on the right.
The list lets you select, unselect or see what is selected and also provides a local filter (in the beige area
above the list). This lets you filter the objects on the list by name, type or functional constraint and also lets
you clear or select all the visible items. The list filter additionally lets you see only data included in reports
or the option to show or hide the data attributes. As you navigate through the model yo u also get
metaphoric icons and the description of the object you are selecting (decision aids). Also note the Clear All
Selected button that lets you clear all the objects currently selected independently of your current filter.
If you want to check what was generated at each step you need only to look at the generator output trace.

16.5.5 HOW TO GENERATE THE ENTITY IDENTIFIERS

The entity identifiers that are generated are based on the IEC 61850 naming scheme and you can setup the
name generation pattern. This pattern is basically a string of characters that is copied verbatim to the entity
identifier except for context specific keyword replacement (followed by automatic limits checking and
solving of collisions to ensure uniqueness of identifiers). Available keywords are as follows:

Keyword Usage Example

$iedName$ Name of IED IED

$ldName$ Name of logical device LD

$lnClass$ Logical node class XCBR

$lnInst$ Logical node instance number 1

$lnPrefix$ Logical node prefix Q50

$lnName$ Logical node name Q50.XCBR.1

- UC 500, N. ASID12000063, Rev. 7.1, May 16 16-11

 Chapter 16 - Annexes

Keyword Usage Example

$doName$ Data object name PhV.phsA

$daName$ Data attribute name a.b.c

Discrete control value, empty string if n/a (always numeric and applicable to
$value$
digital controls only)
21
Table 16.2 Available keywords (example for SCL object IED\LD\Q50XCBR1.PhV.phsA\a.b.c)

21
If you need to limit the length of each keyword replacement text you can write $<keyword name>:<max
len>$, for example $iedName:4$.

16-12 - UC 500, N. ASID12000063, Rev. 7.1, May 16

 16.6- IDE Options

16.6 IDE OPTIONS

Each user has the possibility to customize some IDE options referred to UC 500 configurations. They are
kept between sessions and can be restored to their default val ues at any time. Those options can be found
on the Tools menu, at the UC 500 item.

Figure 16.3 UC 500 options

- UC 500, N. ASID12000063, Rev. 7.1, May 16 16-13

 Chapter 16 - Annexes

16.7 PRIVATE EXTENSIONS

All UC 500 model elements may include a set of user defined private extensions, visible within the
Automation Studio as a Tagged Value. These extensions do not have a direct impact on the configuration
model but are kept as part of it.

Figure 16.4 UC 500 Private Extensions

These private extensions can be used for inclusion of specific project information, external tools
22
interaction configuration or any other type of information that may be useful to preserve alongside the
configuration but is not directly included in it.

22
It’s not recommended to modify private extensions that were not created by the user directly. This
modifications may cause external tools to behave differently than expected.

16-14 - UC 500, N. ASID12000063, Rev. 7.1, May 16