Quick Guide to UC 500

ASID12000059, Rev. 1.0, March 12

 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 - Quick Guide to UC 500, N. ASID12000059, Rev. 1.0, March 12

Manual Revisions

Revision Date Changes

1.0 2012-03-23 Version corresponding to Automation Studio 2.6 or later.

- Quick Guide to UC 500, N. ASID12000059, Rev. 1.0, March 12 iii

INDEX

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

1.1 SCOPE AND AUDIENCE ................................................................................................................................ 1-3
1.2 REFERENCES.............................................................................................................................................. 1-4
1.3 SUPPORT CONTACTS ................................................................................................................................... 1-5
2 UC 500 ............................................................................................................................................. 2-1
2.1 INTRODUCTION .......................................................................................................................................... 2-2
3 ADD DEVICE TO PROJECT ................................................................................................................. 3-1
3.1 ADDING A DEVICE ....................................................................................................................................... 3-3
4 DEVICE MODULES ............................................................................................................................ 4-1
4.1 DEVICE MODULES ....................................................................................................................................... 4-3
5 CONFIGURATION WALKTHROUGH ................................................................................................... 5-1
5.1 EXAMPLE CONFIGURATION WALKTHROUGH .................................................................................................... 5-3
6 DEVICE INTERACTION ....................................................................................................................... 6-2
6.1 DEVICE INTERACTION .................................................................................................................................. 6-4

iv - Quick Guide to UC 500, N. ASID12000059, Rev. 1.0, March 12

 1
Chapter

INTRODUCTION

Provide initial guidance for creating, building and deploying configurations to Efacec UC 500.
 Chapter 1 - Introduction

INDEX
1
1.1 SCOPE AND AUDIENCE ................................................................................................................................ 1-3
1.2 REFERENCES.............................................................................................................................................. 1-4
1.3 SUPPORT CONTACTS ................................................................................................................................... 1-5

Total pages of the chapter 5

1-2 - Quick Guide to UC 500, N. ASID12000059, Rev. 1.0, March 12

 1.1- Scope and Audience

1.1 SCOPE AND AUDIENCE

1
This guide targets the UC 500 device family and Automation Studio Engineer Edition 2.6 or Designer Edition
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.

- Quick Guide to UC 500, N. ASID12000059, Rev. 1.0, March 12 1-3

 Chapter 1 - Introduction

1.2 REFERENCES
1
[Ref.] Title Date Rev. Source Number
1. Automation Studio User Manual latest latest EFACEC latest
2. Automation Studio User Manual - Efacec
Devices latest latest EFACEC latest

3. Automation Studio User Manual - IEC

61131-3 latest latest EFACEC latest

4. Automation Studio User Manual - Mimic

Editor latest latest EFACEC latest

5. Automation Studio User Manual - IEC

61850 and Third-Party Devices latest latest EFACEC latest

6. Automation Studio User Manual - UC 500 latest latest EFACEC latest

1-4 - Quick Guide to UC 500, N. ASID12000059, Rev. 1.0, March 12

 1.3- Support Contacts

1.3 SUPPORT CONTACTS

1
When interacting with Efacec please refer your product serial number.

Contacts
Automation Studio Licensing E-mail: as_licenses@efacec.com
Automation Studio Customer Support E-mail: as_support@efacec.com
EFACEC Engenharia e Sistemas, S.A.
Rua Engº Frederico Ulrich, Apt. 3078
4471-907, Moreira da Maia
PORTUGAL
General
Tel: +351 229 402 000
Fax: +351 229 485 428
Web: www.efacec.com
E-mail: ase.eng@efacec.com

- Quick Guide to UC 500, N. ASID12000059, Rev. 1.0, March 12 1-5

 Chapter 2 - UC 500

2
Chapter

UC 500
 Chapter 2 - UC 500

INDEX

2.1 INTRODUCTION .......................................................................................................................................... 2-2

Total pages of the chapter 2

2

2-2 - Quick Guide to UC 500, N. ASID12000059, Rev. 1.0, March 12

 2.1- Introduction

2.1 INTRODUCTION

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, 2
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, mimics and event
logs.
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, analogs, 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 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).
System or user interface process that runs on the device to provide a
Process
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 Center 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 implementations allow
the user to define more than one RTU for a given channel thereby
Emulated RTU / IED
emulating several physical RTUs. Each communication module will
provide protocol-specific parameters.
Table 2.1 Overview of some UC 500 object types

Please note that this guide does not cover the advanced configuration of the Efacec UC 500. To do this, read
the Automation Studio User Manual - UC 500 [6] for better understanding of all information available.

- Quick Guide to UC 500, N. ASID12000059, Rev. 1.0, March 12 2-3

 3
Chapter

ADD DEVICE TO PROJECT

 Chapter 3 - Add device to Project

INDEX

3.1 ADDING A DEVICE ....................................................................................................................................... 3-3

Total pages of the chapter 3

3-2 - Quick Guide to UC 500, N. ASID12000059, Rev. 1.0, March 12

 3.1- Adding a device

3.1 ADDING A DEVICE

To add UC 500 devices to a device project can choose between two options: add a new device or
add an existing device.

Option How-to
 Select the project you want to add device;
 Choose “New Device…” command from
project context menu or on main menu
“Device”;
 Select device template from UC 500
templates;
 Change device name and connection address
parameters;
Add a new device
 Enter device order code;
 Select common device application;
 Select active modules;
 Press Finish to create device configuration.
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.
 Select the project you want to add an
6
existing device;
 Choose “Add Existing Device” command
from project context menu or on main menu
“Device”;
Add an existing device  Select UC 500 device driver;
 Enter connection parameters;
 Press Finish and insert login;
The newly created device will extract the current
available configuration on the live device to the
project.

Table 3.1 Available options to add UC 500 devices

Read the Automation Studio User Manual - UC 500 [6] for advanced alternatives to add UC 500 devices in
project.

- Quick Guide to UC 500, N. ASID12000059, Rev. 1.0, March 12 3-3

 4
Chapter

DEVICE MODULES
 Chapter 4 - Device Modules

INDEX

4.1 DEVICE MODULES ....................................................................................................................................... 4-3

Total pages of the chapter 5

4-2 - Quick Guide to UC 500, N. ASID12000059, Rev. 1.0, March 12

 4.1- Device modules

4.1 DEVICE MODULES

Device modules are organized by functional scope: user interface, automation, local networking, control
center communications and RTU/IDE communications.

Module Description
The events log keeps information on entities state
changes, control execution, alarm generation and
user actions like alarm acceptance and beginning and
EventLog
ending of sessions. This log, depending on the
configuration, can be directed to database and/or
printer.

Trends keep historical information of the entities

evolution (digitals, analogs and counters). The trends
Trends
record is generated either on-event (upon status
entity changed) and also periodically (cyclic).

This module allows users to create synoptics to

Mimics
the HMI.

Alarms can be generated by controls execution failure

Alarms or entities state changes to states considered as
alarm.

All the information of trends and event logs is kept in 6

a database for which periodical automatic
Database Maintenance maintenance may be setup. Database maintenance
parameter involve: the time and period, directory and
data backup.

The lists printing is based in layout models named

print-forms. A print-form is a text file written in an
interpreted language (script). This language allows
Print Forms 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

Table 4.1 User Interface modules

Module Description
Full programmability in IEC 61131-3 languages that
Automation allows users to create algorithms and advanced
applications according to the needs of each project.

Table 4.2 Automation modules

- Quick Guide to UC 500, N. ASID12000059, Rev. 1.0, March 12 4-3

 Chapter 4 - Device Modules

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

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.
IEC 61850-8-1 Client
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.

SNMP manager is a communications process that

SNMP Manager
implements the SNMP communications protocol.

Table 4.3 Local networking modules

Module Description
IEC 60870-5-101/104 Controlled The IEC 60870-5-101 controlling station implements
Station the unbalanced (master-slave) protocol option.
6
This protocol can be defined as the synchronization
DNP 3.0 Control Center
master.

Table 4.4 CC Communications modules

.Module Description
The DNP Master Station provides exchange data with
DNP 3.0 Master Station
devices communicating via the DNP protocol.

IEC 60870-5-101/104 Controlling The IEC 60870-5-101 controlling station implements

Station the unbalanced (master-slave) protocol option.

This protocol is a master-slave protocol, this means

IEC 60870-5-103 Master
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.

Modbus is a master-slave protocol, which implements

the telemetry of digitals, analogs and counters,
ModBus Master allowing controls execution of type digital or analog.
The protocol mode can be ASCII or RTU, via serial
port.

4-4 - Quick Guide to UC 500, N. ASID12000059, Rev. 1.0, March 12

 4.1- Device modules

.Module Description
The UC 500 Modbus driver shall connect to a RTU
ModBus/TCP Client through a TCP/IP socket, so for each RTU it will exist a
TCP/IP connection to the RTU.

The JBus scanner may work in two distinct modes,

Events and Digitals.
JBus Master The scanner allows to program the entities requests
that the user want to obtain from an IED. Those
requests are distributed by blocks.

This scanner allows the use of 32 serial ports, being

SPABUS Master possible to collect data of 48 ABB modules for each
serial port.

Table 4.5 RTU/IED Communications modules

- Quick Guide to UC 500, N. ASID12000059, Rev. 1.0, March 12 4-5

 5
Chapter

CONFIGURATION WALKTHROUGH
 Chapter 5 - Configuration Walkthrough

INDEX

5.1 EXAMPLE CONFIGURATION WALKTHROUGH .................................................................................................... 5-3

Total pages of the chapter 6

5-2 - Quick Guide to UC 500, N. ASID12000059, Rev. 1.0, March 12

 5.1- Example Configuration Walkthrough

5.1 EXAMPLE CONFIGURATION WALKTHROUGH

The following presents the steps to configure the modules “IEC 61850-8-1 Client” and “IEC 60870-5-101/104
Controlled Station” in the UC 500 Device.

Step How-to
 On the start page click “New Solution”;

Create a new solution

 Select the new solution location and give it a name;

 Press “Finish” button;
 On the start page click “New Project”;

Create a new device project 6

 Select “Automation Studio Device Project” and press “Next”

button;
 Give a name to project and press “Finish” button;
 Select device project and chose “New Device…” command
from project context menu;
 Select “Empty” template from UC 500 templates and press
“Next” button;

Create a new UC 500 Device

 Change device name and connection address parameters;

 Press “Next” button;
 Select “UC 500” on the model and press “Next” button;

- Quick Guide to UC 500, N. ASID12000059, Rev. 1.0, March 12 5-3

 Chapter 5 - Configuration Walkthrough

Step How-to
 Select “Gateway” and press “Next” button;
 Press “Finish” button;
 Expand device tree and double-click on “Configuration
Settings” node;

 Expand “Configuration Settings” and “Networking” nodes and

double-click on “IEC 61850-8-1 Client”;

Configure IEC 61850-8-1

Client

 Press “IEC 61850 Wizard…” on toolbar;

6 
1
Select an SCL file and press “Next” button;
 Select data object and/or data attributes to import and press
“Next” button;
 Press “Finish” button;
 Expand “CC Communications” node and double-click on “IEC
60870-5-101/104 Controlled Station”;

Configure IEC 60870-5-

101/104 Controlled Station

 Select “IEC 60870-5-101/104 Controlled Station” node and

chose “Add-> IEC 60870-5-101 Control Center” command from
context menu;

 Chose “Add IEC 60870-5-101Emulated RTU” command from

context menu;

1
Substation Configuration Language (SCL) is the language and representation format specified by IEC
61850 for the configuration of substation devices.

5-4 - Quick Guide to UC 500, N. ASID12000059, Rev. 1.0, March 12

 5.1- Example Configuration Walkthrough

Step How-to

 Chose “Add Logical Remote Unit” command from context

menu;

 Click “Add Digital Object” on toolbar;

 Expand “Networking” node and select “IEC 61850-8-1 Client”;

 Change type to “All” and press “Select All” button;

 Press “OK” button;

 Select “Optimize Address Space…” command from context
menu of the LRU;
 On Solution Explorer select “Serial Ports” command from
context menu of the Configuration Settings node.

 Click “Add Serial Port” on toolbar;

 Click on tab “Control Center IEC 60870-5-101/104”;
 Select “CC1” node and change on Properties pad the property
“Serial Port” to the value COM1;

- Quick Guide to UC 500, N. ASID12000059, Rev. 1.0, March 12 5-5

 Chapter 5 - Configuration Walkthrough

Step How-to
Note: If Properties pad is not visible, click on “View” menu on principal
toolbar and click on“Properties”;
 In the Solution Explorer open the context menu from
“Configuration Settings” node and select “Tools->Validate…”
Validate configuration menu;
 Make sure there are no errors and warnings in the Output
pad;

Table 5.1 Steps to create example UC 500 configuration

5-6 - Quick Guide to UC 500, N. ASID12000059, Rev. 1.0, March 12

 6
Chapter

DEVICE INTERACTION
INDEX

6.1 DEVICE INTERACTION .................................................................................................................................. 6-4

Total pages of the chapter 3

 6.1- Device interaction

6.1 DEVICE INTERACTION

The following presents the commands available to communicate with the device.

Step How-to
The deploy command deploys the device configuration to the device
Deploy Configuration Settings
using the address defined in the default connection.

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

The get system log command gets the system logs from the device to
Get System Log
the selected device.

Table 6.1 Commands to communicate with UC 500 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.

- Quick Guide to UC 500, N. ASID12000059, Rev. 1.0, March 12 6-3