Quick Guide for Efacec Devices

ASID12000058, 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 for Efacec Devices, N. ASID12000058, Rev. 1.0., March 12

Manual Revisions

Revision Date Changes

1.0 2012-01-20 Version corresponding to Automation Studio 2.6 or later.

- Quick Guide for Efacec Devices, N. ASID12000058, Rev. 1.0., March 12 iii
INDEX

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

1.1 INTRODUCTION .......................................................................................................................................... 1-3
1.2 SCOPE AND AUDIENCE ................................................................................................................................ 1-4
1.3 REFERENCES.............................................................................................................................................. 1-5
1.4 SUPPORT CONTACTS ................................................................................................................................... 1-6
2 ADD DEVICE TO PROJECT ................................................................................................................. 2-1
2.1 ADD A NEW DEVICE .................................................................................................................................... 2-2
2.2 ADD AN EXISTING DEVICE ............................................................................................................................ 2-3
3 CORE CONFIGURATION .................................................................................................................... 3-1
3.1 CORE CONFIGURATION ................................................................................................................................ 3-3
3.2 RESOURCES............................................................................................................................................... 3-3
3.3 HARDWARE .............................................................................................................................................. 3-4
3.4 USER INTERFACE ........................................................................................................................................ 3-5
3.5 AUTOMATION ........................................................................................................................................... 3-6
3.6 NETWORKING............................................................................................................................................ 3-7
3.7 CC COMMUNICATIONS ............................................................................................................................... 3-8
3.8 RTU/IED COMMUNICATIONS ...................................................................................................................... 3-9
4 EXAMPLE CONFIGURATION WALKTHROUGH ................................................................................... 4-1
4.1 EXAMPLE CONFIGURATION WALKTROUGH ....................................................................................................... 4-3
5 DEVICE INTERACTION ....................................................................................................................... 5-2
5.1 DEVICE INTERACTION .................................................................................................................................. 5-3

iv - Quick Guide for Efacec Devices, N. ASID12000058, Rev. 1.0., March 12

LIST OF FIGURES

Figure 2.1 IED 500 new device wizard ............................................................................................................ 2-2

Figure 3.1 Efacec Devices Configuration items ............................................................................................... 3-3

- Quick Guide for Efacec Devices, N. ASID12000058, Rev. 1.0., March 12 v

LIST OF TABLES

Table 2.1 Available options to add an existing Efacec device ......................................................................... 2-3
Table 3.1 Function type .................................................................................................................................. 3-3
Table 3.2 CC Communications Protocols ........................................................................................................ 3-8
Table 3.3 RTU/ IED Communications Protocols. ............................................................................................. 3-9
Table 4.1 Steps to create a BCU 500 configuration ........................................................................................ 4-6

vi - Quick Guide for Efacec Devices, N. ASID12000058, Rev. 1.0., March 12

 1
Chapter

INTRODUCTION
 Chapter 1 - Introduction

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

Total pages of the chapter 6

1-2 - Quick Guide for Efacec Devices, N. ASID12000058, Rev. 1.0., March 12
 1.1- Introduction

1.1 INTRODUCTION
1
The Efacec Devices Configuration Editor is an Automation Studio IDE module designed specifically for
managing and editing the configuration of Efacec devices such as BCU 500, DCU 500, TPU 220, G Remote,
and others. It includes several editors, productivity tools, a device builder and a communications driver. This
document will briefly describe all Efacec family device modules and provide a fast track guide for a general
configuration.
Please note that this guide does not cover the advanced configuration of the Efacec family devices features.
Read the Automation Studio User Manual – Efacec Devices for better understanding of all configuration
capabilities of the Efacec family devices. For IDE-wide features such as windowing, device management,
loading, saving and backing up device configurations, project and build system, etc, read the Automation
Studio User Manual.

- Quick Guide for Efacec Devices, N. ASID12000058, Rev. 1.0., March 12 1-3
 Chapter 1 - Introduction

1.2 SCOPE AND AUDIENCE

1
This guide targets the Efacec device family and Automation Studio Engineer Edition 2.6 or Designer Edition
2.6, or later versions of these editions.
The reader of this document and user of the tool is an automation engineer who has basic knowledge of the
Efacec family devices, automation and industrial communications.

1-4 - Quick Guide for Efacec Devices, N. ASID12000058, Rev. 1.0., March 12
 1.3- References

1.3 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

- Quick Guide for Efacec Devices, N. ASID12000058, Rev. 1.0., March 12 1-5
 Chapter 1 - Introduction

1.4 SUPPORT CONTACTS

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

Contacts
Automation Studio Licensing E-mail: [email protected]
Automation Studio Customer Support E-mail: [email protected]
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: [email protected]

1-6 - Quick Guide for Efacec Devices, N. ASID12000058, Rev. 1.0., March 12
 2
Chapter

ADD DEVICE TO PROJECT

 Chapter 2 - Add device to project

INDEX

2.1 ADD A NEW DEVICE .................................................................................................................................... 2-2

2.2 ADD AN EXISTING DEVICE ............................................................................................................................ 2-3

2 Total pages of the chapter 3

2-2 - Quick Guide for Efacec Devices, N. ASID12000058, Rev. 1.0., March 12
 2.1- Add a new device

2.1 ADD A NEW DEVICE

To add a new Efacec device to a device project usually IDE template-based approach is employed.
First of all select the project element (project, system, substation…) where you want to add the device and
choose the “New Device…” command from the context menu or main menu “Device”, a wizard will pop up.
In that wizard you have to choose one Efacec device family and version, for instance BCU BCU 500 version 2
2.0. Then the user is prompted to enter some template parameters (such as device name, connection ip
address, …) as well as the device order code.

Figure 2.1 IED 500 new device wizard

The newly created device configuration is based on the selected template and some model and order-code
related parameters, such as installed boards, are automatically setup for you.

- Quick Guide for Efacec Devices, N. ASID12000058, Rev. 1.0., March 12 2-3
 Chapter 2 - Add device to project

2.2 ADD AN EXISTING DEVICE

To add an Efacec device to a device project choose between two options: add an existing one or use a
device package.

2 Option How-to
Choose “Add Existing Device” command from
Solution Explorer context menu, select “Efacec
Add an existing device, live on the Device” driver and enter connection parameters.
network (previously configured by
Automation Studio) The newly created device will extract the current
available configuration from the live device to the
project.

Choose “Import / Device Package” command from

Import device package the File Menu and select the .adev file you want to
import.

Table 2.1 Available options to add an existing Efacec device

2-4 - Quick Guide for Efacec Devices, N. ASID12000058, Rev. 1.0., March 12
 3
Chapter

CORE CONFIGURATION
 Chapter 3 - Core configuration

INDEX

3.1 CORE CONFIGURATION ................................................................................................................................ 3-3

3.2 RESOURCES............................................................................................................................................... 3-3
3.3 HARDWARE .............................................................................................................................................. 3-4
3.4 USER INTERFACE ........................................................................................................................................ 3-5
3.5 AUTOMATION ........................................................................................................................................... 3-6
3.6 NETWORKING............................................................................................................................................ 3-7
3.7 CC COMMUNICATIONS ............................................................................................................................... 3-8
3.8 RTU/IED COMMUNICATIONS ...................................................................................................................... 3-9
3
Total pages of the chapter 9

3-2 - Quick Guide for Efacec Devices, N. ASID12000058, Rev. 1.0., March 12
 3.1- Core configuration

3.1 CORE CONFIGURATION

Figure 3.1 Efacec Devices Configuration items 3

The Efacec device family configuration is organized in the Automation Studio by functional scope:
resources, hardware, user interface, automation, networking, CC communications, RTU/ IED
communications.
According to the device type and/ or order code selected some of these sections may not be available.

3.2 RESOURCES
The functional blocks of the unit are organized in logical devices. Each logical device has influence in the
functions that are hierarchically bellow it (behaviour, command origin, etc). It is possible to add functions
via Logical Device context menu or via “New Function Wizard”.

Name Description
Firmware Function A firmware function is a function that is built in the Efacec device. The list of
firmware functions available depends on the Efacec device type.

User Function A user function is used to create data objects that will be updated by programs
developed in the automation module.

I/O Function An I/O Functions areis used to create data objects that give meaning to the
hardware I/O points. An I/O function can have data objects and channels for
digital I/O and analogue I/O.

Virtual I/O Function A Virtual I/O Functions areis used to create virtual objects. For instance, when an
Efacec device needs some IEC 61850 publisher it is necessary to create this
function type.

Table 3.1 Function type

- Quick Guide for Efacec Devices, N. ASID12000058, Rev. 1.0., March 12 3-3
 Chapter 3 - Core configuration

3.3 HARDWARE

By default the Efacec Device is set-up automatically when the order code is defined/ updated, but it is also
possible to add a new boards to an empty slot using the slot context menu.

3-4 - Quick Guide for Efacec Devices, N. ASID12000058, Rev. 1.0., March 12
 3.4- User Interface

3.4 USER INTERFACE

In the user interface section, it is possible to find the Event Log module and the Mimics module if the Efacec
device type has display.
Some generic Event Log properties (such as, max events, timeout, …) can be found in the property pad. In
the Mapping Editor it is possible to add entities to the log and define the trigger and the related elements.
Some Efacec devices, such as G Remote or TPU 220, doesn’t support the Mimics module. Devices that
supports this module define some restrictions, for a detailed list of mimics module restrictions see [2]. For
more information about the Mimics module configuration, please refer to [4].
3

- Quick Guide for Efacec Devices, N. ASID12000058, Rev. 1.0., March 12 3-5
 Chapter 3 - Core configuration

3.5 AUTOMATION

In the Efacec devices family it is possible to implement specific automation and supervision functions of
complementary logic through the Automation Module. Different Efacec devices types may define different
restrictions on this module, see [2] to fully understand those restrictions. For more information about the
Automation module configuration, please refer to [3].

3-6 - Quick Guide for Efacec Devices, N. ASID12000058, Rev. 1.0., March 12
 3.6- Networking

3.6 NETWORKING

In the Networking section it is possible to find Time Synchronization protocols and the IEC 61850 protocol.
At the moment, only SNTP protocol is supported for time synchronization.
For more information about the IEC 61850 module configuration, please refer to [5].

- Quick Guide for Efacec Devices, N. ASID12000058, Rev. 1.0., March 12 3-7
 Chapter 3 - Core configuration

3.7 CC COMMUNICATIONS

When creating an Efacec device through the IDE template-based approach it is possible to select CC
Communications protocols, those protocols will appear in this section. It is also possible to add and/or
remove protocols in the Advanced Settings available in the configuration Settings context menu.

Module Description
DNP 3.0 Control Center

3 Table 3.2 CC Communications Protocols

3-8 - Quick Guide for Efacec Devices, N. ASID12000058, Rev. 1.0., March 12
 3.8- RTU/ IED Communications

3.8 RTU/ IED COMMUNICATIONS

When creating an Efacec device through the IDE template-based approach it is possible to select RTU/ IED
Communications protocols, those protocols will appear in this section. It is also possible to add and/ or
remove protocols in the Advanced Settings available in the configuration Settings context menu.

Module Description
ModBus Master

Table 3.3 RTU/ IED Communications Protocols. 3

- Quick Guide for Efacec Devices, N. ASID12000058, Rev. 1.0., March 12 3-9
 4
Chapter

EXAMPLE CONFIGURATION
WALKTHROUGH
 Chapter 4 - Example Configuration Walkthrough

INDEX

4.1 EXAMPLE CONFIGURATION WALKTROUGH ....................................................................................................... 4-3

Total pages of the chapter 6

4-2 - Quick Guide for Efacec Devices, N. ASID12000058, Rev. 1.0., March 12
 4.1- Example configuration walkthrough

4.1 EXAMPLE CONFIGURATION WALKTHROUGH

In tThis section will be presented the steps to configure an example data model, the IEC 61850-8-1
Server/Client module and the DNP 3.0 Control Center module in a BCU 500 device.

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

Create a new solution

4
 Select the new solution location and give it a name;
 Press “Finish” button;
 On the start page click “New Project”;

Create a new project

 Select “Automation Studio Device Project” and press

“Next” button;
Give a name to project and press “Finish” button;
 In the solution explorer select device project and chose
“New Device…” command from project context menu;
 Select one template from BCU 500 templates (for example,
BCU500 version 2.03.000) and press “Next” button;

Add a new BCU 500 Device

 Change device name and connection address parameters;

 Choose BCU 500 Order Code;
 Press “Next”

- Quick Guide for Efacec Devices, N. ASID12000058, Rev. 1.0., March 12 4-3
 Chapter 4 - Example Configuration Walkthrough

Steps How-to

 Continuing in the previous step or select command

“Function Wizard” in Logical Device “CRTL” context menu;

Create a Function

 Select Firmware Function and press next;

 Select firmware function “CBCtrl” and press Finish.

 Expand device tree and double-click on “Configuration

Settings” node;
 Open Mapping Editor by double-clicking in Resources and
verify that firmware function is mapped to IEC 61850;
4

 Go to IEC 61850 under Networking and open it;

Configure IEC 61850 Server

 In logical node LLN0 in logical device “CTRL” create a

DataSet;
 Double-click in created dataset and via Drag&Drop add the
data object Pos from the CSWI function;
 In the same logical node add a report control block and
associate the created dataset by changing the Dataset
property in the Property Pad;

4-4 - Quick Guide for Efacec Devices, N. ASID12000058, Rev. 1.0., March 12
 4.1- Example configuration walkthrough

Steps How-to
 In the Solution Explorer open the context menu from
“Configuration Settings” node and select “Advanced
Settings” menu;

 Add “DNP 3.0 Control Center” and press “ok”;

 Expand “CC Communications” node and in the context
menu from “DNP 3.0” press “Add DNP Channel”

 In DNP Channel add an IED;

 Go back again to the “Mapping Editor” and map all data

Configure DNP 3.0 Control
Center objects from firmware function to the created IED;
4

 In the Solution Explorer open the context menu from

“Configuration Settings” node and select “Tools-
>Validate…” menu;

Validate Configuration

 Make sure there are no errors or warnings in the Output

Pad;
 If configuration settings are unsaved, press “Save
Configuration Settings” command.
 In the Solution Explorer open the context menu from the
IED 500 device and select “Build” menu;

Build Configuration
 Make sure there are no errors or warnings in the Output
Pad;
 Verify that default connection is correctly defined in the
Deploy Configuration Settings Connections folder;

- Quick Guide for Efacec Devices, N. ASID12000058, Rev. 1.0., March 12 4-5
 Chapter 4 - Example Configuration Walkthrough

Steps How-to

 In the Solution Explorer open the context menu from the

IED 500 Device and select “Deploy Configuration Settings”
menu;
 Type user name and password;
 To follow the deploy process go to Task Manager Pad and
check the Output Window Pad to check for any errors
 In the Solution Explorer open the context menu from
“Operational Settings” node and select “Edit…” option;

 Settings editor view content will appear;

4  Edit ‘ManSyncTime’ and ‘ManSyncTime’ values;
Operational Settings

 Validate settings;
 Make sure there are no errors and warnings in the Output
Pad;
 In the Operational Settings view content press “Deploy
Settings to Device” button or in the Solution Explorer open
the context menu from the IED 500 Device (or from the
Operational Settings node) and select “Deploy Operational
Settings” menu;
Deploy Operational Settings

 Type user name and password;

 To follow the deploy process go to Task Manager Pad and
check the Output Pad to check for any errors

Table 4.1 Steps to create a BCU 500 configuration

4-6 - Quick Guide for Efacec Devices, N. ASID12000058, Rev. 1.0., March 12
 5
Chapter

DEVICE INTERACTION
 Chapter 5 - Device Interaction

INDEX

5.1 DEVICE INTERACTION .................................................................................................................................. 5-3

Total pages of the chapter 3

5-2 - Quick Guide for Efacec Devices, N. ASID12000058, Rev. 1.0., March 12
 5.1- Device Interaction

5.1 DEVICE INTERACTION

In an Efacec device it is possible to build the entire device configuration or partially the Mimics or the VM
module. But partial deploy is not supported on these devices. Therefore, to deploy a configuration it is
necessary to build the device, choosing the “Build” command available in the device node context menu.
The “Deploy” command available on the device node context menu will update the physical device
configuration to the configuration made in the Automation Studio. So, to deploy a configuration it is
necessary to have a default connection in the “Connections folder” and be authorized.
If the build process succeeds a current settings file will appear in the “Operational Settings” folder. In this
section it is possible to interact with the current settings of the device:
 deploy new settings to device
 get settings from device
 change device active group
 compare local settings with device settings

- Quick Guide for Efacec Devices, N. ASID12000058, Rev. 1.0., March 12 5-3