Você está na página 1de 57

Automation Studio

Designer
Users Manual
Revisions

Version Date Comments Product Author


Version

1.0 2008-08-06 Initial version 1.0 Adriano Meira,


Elisabete Fonseca
Ferreira, Carlos
Fernandes

Document

Name Automation Studio Designer - Users Manual


Document Nr ASID08000220
Model Modelo para Fascculo de Manual
Model Version 1.0
Reviewed by Rogrio Dias Paulo
Approved by Rogrio Dias Paulo
Total of Pages 50

Revisions
Index

1. INTRODUCTION ............................................................................................................... 2

1.1 SCOPE.......................................................................................................................... 2
1.2 AUTOMATION STUDIO DESIGNER OVERVIEW ................................................................... 2
2. LEGEND ............................................................................................................................ 3

3. INSTALLATION ................................................................................................................ 4

3.1 SYSTEM REQUIREMENTS ............................................................................................... 4


3.2 APPLICATION INSTALLATION ........................................................................................... 4
3.2.1 License Agreement ................................................................................................ 5
3.2.2 Destination Folder .................................................................................................. 5
3.2.3 Complete Installation ............................................................................................. 6
3.2.4 Installation .............................................................................................................. 6
3.2.5 Uninstalling............................................................................................................. 7
4. USAGE .............................................................................................................................. 8

4.1 STARTING AUTOMATION STUDIO DESIGNER .................................................................... 8


4.2 LICENSING .................................................................................................................... 9
4.3 BASIC USAGE.............................................................................................................. 11
4.3.1 Creating a new Solution ....................................................................................... 11
4.3.2 Creating a new Project ......................................................................................... 11
4.3.2.1. System ..................................................................................................................... 12
4.3.2.2. Library ...................................................................................................................... 12
4.3.3 Saving a project/solution ...................................................................................... 12
4.3.4 Adding References .............................................................................................. 12
4.3.5 Adding Elements .................................................................................................. 13
4.3.6 Adding new Device .............................................................................................. 14
4.3.7 Creating Basic Function Block ............................................................................. 15
4.3.8 Creating Function Classes ................................................................................... 15
4.3.8.1. ST Program ............................................................................................................. 16
4.3.9 Instantiating Function Classes ............................................................................. 17
4.3.10 Defining Hardware ............................................................................................ 18
4.3.11 BinaryIO Application ......................................................................................... 18
4.3.11.1. Logical Input........................................................................................................... 19
4.3.11.2. Logical Output ........................................................................................................ 20
4.3.11.3. Controllable Object ................................................................................................ 20
4.3.12 Creating Internal Associations .......................................................................... 21
4.3.13 Creating Logs ................................................................................................... 22
4.3.14 Building ............................................................................................................. 22
4.3.15 Deploying .......................................................................................................... 23
4.3.16 Validating .......................................................................................................... 23
4.4 SCL ........................................................................................................................... 24
4.4.1 Validation ............................................................................................................. 24
4.4.2 Exporting .............................................................................................................. 24

Index
4.4.3 Importing .............................................................................................................. 24
4.5 IEC 61850-8-1 ........................................................................................................... 25
4.5.1 Server................................................................................................................... 25
4.5.2 Client .................................................................................................................... 26
4.6 DISPLAY ..................................................................................................................... 28
4.6.1 Display Editor ....................................................................................................... 28
4.6.2 Graphical Object Editor ........................................................................................ 29
4.7 SETTINGS ................................................................................................................... 30
4.8 DNP........................................................................................................................... 32
4.9 LOG VIEWER ............................................................................................................... 34
4.9.1 Viewing................................................................................................................. 34
4.9.2 Sorting .................................................................................................................. 34
4.9.3 Filtering ................................................................................................................ 35
4.9.4 Paging .................................................................................................................. 35
4.9.5 Showing and hiding columns ............................................................................... 35
4.9.6 Exporting .............................................................................................................. 35
4.10 DRIVER ..................................................................................................................... 37
4.11 OTHER FEATURES ..................................................................................................... 38
4.11.1 Tagged Values Editor ....................................................................................... 38
4.11.2 Reference Form ................................................................................................ 38
4.11.3 Object Browser ................................................................................................. 39
4.11.4 Properties ......................................................................................................... 39
4.11.5 Output ............................................................................................................... 40
4.11.6 Ping ................................................................................................................... 40
4.11.7 Designer Options .............................................................................................. 41
4.11.8 Browser Window ............................................................................................... 41
4.11.9 About................................................................................................................. 42
ANNEXES .......................................................................................................................... 44

A1. AUTOMATION STUDIO SERVER ..................................................................................... 44


A1.1. Adding Device .................................................................................................... 44
A1.2. Test Device......................................................................................................... 45
A1.3. IO Simulator Panel ............................................................................................. 45
A1.4. Driver .................................................................................................................. 45
A2. BCU 500 .................................................................................................................... 46
A2.1. Adding Device .................................................................................................... 46
A2.2. Creating e Editing Digital I/O .............................................................................. 46
A2.3. Analog I/O Configuration .................................................................................... 46
A2.4. AC ....................................................................................................................... 47
A2.5. DC ...................................................................................................................... 48
A2.6. Editing Time zone ............................................................................................... 48
A2.7. Driver .................................................................................................................. 49

Index
List of Figures
FIGURE 1 - FIRST WINDOW OF THE INSTALLATION..................................................................... 4

FIGURE 2 - LICENSE AGREEMENT WINDOW ................................................................................ 5

FIGURE 3 - DESTINATION FOLDER WINDOW ................................................................................ 5

FIGURE 4 - COMPLETE INSTALLATION WINDOW ......................................................................... 6

FIGURE 5 - INSTALLATION WINDOW .............................................................................................. 6

FIGURE 6 - UNINSTALL AUTOMATION STUDIO DESIGNER ......................................................... 7

FIGURE 7 - AUTOMATION STUDIO DESIGNER SPLASH-SCREEN ............................................... 8

FIGURE 8 LICENSE TYPE .............................................................................................................. 9

FIGURE 9 ACQUIRING A LICENSE ............................................................................................. 10

FIGURE 10 - NEW SOLUTION WINDOW ........................................................................................ 11

FIGURE 11 - NEW PROJECT WINDOW ......................................................................................... 11

FIGURE 12 - ADD REFERENCE(S) WINDOW ................................................................................ 13

FIGURE 13 - ADDING ELEMENT ON SOLUTION EXPLORER ...................................................... 13

FIGURE 14 - TOOL BOX .................................................................................................................. 14

FIGURE 15 - ADD DEVICE WIZARD ............................................................................................... 14

FIGURE 16 - FIRST STEP OF FUNCTION CLASS WIZARD .......................................................... 15

FIGURE 17 - SECOND STEP OF FUNCTION CLASS WIZARD ..................................................... 16

FIGURE 18 - SELECT TYPE OF THE FUNCTION .......................................................................... 16

FIGURE 19 - ST PROGRAM WINDOW ........................................................................................... 17

FIGURE 20 - BINARY IO APPLICATION WINDOW ......................................................................... 18

FIGURE 21 - BINARY IO APPLICATION WINDOW ......................................................................... 19

FIGURE 22 - LOGICAL INPUT STEP............................................................................................... 19

FIGURE 23 - LOGICAL OUTPUT STEP........................................................................................... 20

FIGURE 24 - CONTROLLABLE OBJECT STEP .............................................................................. 20

FIGURE 25 - INTERNAL ASSOCIATION WINDOW ........................................................................ 21

FIGURE 26 - LOGGER EDITOR WINDOW ...................................................................................... 22

FIGURE 27 - SCL MENU.................................................................................................................. 24

FIGURE 28 - IEC 61850-8-1 SERVER EDITOR ............................................................................... 25

FIGURE 29 - IEC61850-8-1 SERVER DATASET EDITOR .............................................................. 26

FIGURE 30 - IEC 61850-8-1 CLIENT WIZARD ................................................................................ 27

FIGURE 31 - EDIT SUBSCRIBER ELEMENT WIZARD ................................................................... 27

FIGURE 32 - DISPLAY EDITOR ...................................................................................................... 28

List of Figures
FIGURE 33 TEXT OBJECT ........................................................................................................... 29

FIGURE 34 - GRAPHICAL OBJECT EDITOR .................................................................................. 29

FIGURE 35 - SETTINGS EDITOR .................................................................................................... 30

FIGURE 36 - DNP SLAVE EDITOR.................................................................................................. 32

FIGURE 37 DATA OBJECT DNP WIZARD FIRST STEP ............................................................. 33

FIGURE 38 - EXAMPLE OF DATA OBJECT DNP WIZARD SECOND STEP ................................. 33

FIGURE 39 LOG VIEWER............................................................................................................. 34

FIGURE 40 LOG VIEWER SORT .................................................................................................. 35

FIGURE 41 LOG VIEWER FILTERS ............................................................................................. 35

FIGURE 42 - LOG VIEWER PAGINATION ...................................................................................... 35

FIGURE 43 - LOG VIEWER EXPORT TO CSV ............................................................................... 35

FIGURE 44 DRIVER CONTEXT MENU ........................................................................................ 37

FIGURE 45 - TAGGED VALUES EDITOR ....................................................................................... 38

FIGURE 46 -REFERENCE FORM ................................................................................................... 38

FIGURE 47 - OBJECT BROWSER VIEW CONTENT ...................................................................... 39

FIGURE 48 - PROPERTIES PAD ..................................................................................................... 40

FIGURE 49 - OUTPUT WINDOW ..................................................................................................... 40

FIGURE 50 - PING TASK ................................................................................................................. 40

FIGURE 51 - OPTIONS WINDOW ................................................................................................... 41

FIGURE 52 - BROWSER WINDOW ................................................................................................. 42

FIGURE 53 - ABOUT BOX ............................................................................................................... 42

FIGURE 54 - ADD DEVICE WIZARD ............................................................................................... 44

FIGURE 55 - AUTOMATION STUDIO SERVER REMOTE CONSOLE ........................................... 45

FIGURE 56 - IO SIMULATOR PANEL .............................................................................................. 45

FIGURE 57 - ADD DEVICE WIZARD ............................................................................................... 46

FIGURE 58 - AC IO POINT CONFIGURATION ............................................................................... 47

FIGURE 59 - DC IO POINT EDITOR ................................................................................................ 48

FIGURE 60 - TIMEZONE EDITOR ................................................................................................... 49

List of Figures
Summary

This document is the Automation Studio Designer users manual providing detailed
description usage procedures.

Summary
Automation Studio
Designer
Users Manual

Introduction 1 of 57
1. Introduction

1.1 Scope

Automation Studio Designer.

1.2 Automation Studio Designer Overview

Automation Studio Designer is a user-interface software tool for configuring and managing
protection, automation and control devices and systems such as substation automation
systems (SAS) or similar systems.

This tool features object oriented device configuration and management and relies heavily
on an integrated and configurable windowing environment, featuring systematic use of
copy/paste, drag-and-drop and context menus, allowing intuitive handling of definitions.

This tool also fully supports IEC 61850 object modeling and SCL import/export for easy
engineering of multivendor systems.

Introduction 2 of 57
2. Legend
In this document relevant instructions, advice or warnings will be shown using the icons
bellow:

Security Instruction failing to comply with this instruction may cause erroneous or unexpected
behaviour on the device, system or application, or/and, cause damage to equipment or system.

Operational or Security Instruction failing to comply with this instruction may cause erroneous
or unexpected behaviour on the device, system or application.

Additional Information observing this instruction may increase user productivity or the usage of
Automation Studio Designer. Not a security instruction.

Legend 3 of 57
3. Installation
This chapter describes all the procedures required for installing and uninstalling the
product.

3.1 System Requirements

The minimum requirements to run Automation Studio Designer are:

512 MB of RAM memory;

100 MB of free space on hard drive;


Windows XP or Windows Vista operating system.

The recommended requirements to run Automation Studio Designer are:

1.5 GB of RAM memory (2 GB for Windows Vista) or higher;

200 Mbytes or more of free space on hard drive;


Windows XP or Windows Vista operating system;
Internet Explorer 7.0 or higher.

3.2 Application Installation

Automation Studio Designer can be installed by executing the provided self-executable


installer.

To install Automation Studio Designer run Setup.exe.

Figure 1 - First window of the installation

Usage 4 of 50
3.2.1 License Agreement

Figure 2 - License agreement window

The user is asked to accept a license agreement applicable to the Automation Studio
Designer application and version being installed. Please read this license agreement
thoroughly.

Please select the option I accept the terms in the License Agreement and continue with
the installation. If you do not agree with the licensing terms the installation process will be
cancelled and the product will not be installed.

3.2.2 Destination Folder

Figure 3 - Destination folder Window

The next window allows the user to select a destination folder for the Automation Studio
Designer Application.

By default, the software will be installed in the Program Files folder.

Usage 5 of 50
3.2.3 Complete Installation

Figure 4 - Complete installation window

The next step is a confirmation window. The user has to click the Install button to
proceed, or Cancel to abort the installation process.

Designer may have issues with anti-virus software upon installation. Please close all other
running programs.

3.2.4 Installation

Figure 5 - Installation window

The application is then automatically installed. The user can keep track of the operation
through a status window.

Usage 6 of 50
3.2.5 Uninstalling

Figure 6 - Uninstall Automation Studio Designer

To uninstall the Automation Studio Designer Application please select Add or Remove
programs from the Control Panel (Start>Control Panel>Add or Remove Programs) and
remove the intended version of the Automation Studio Designer.

Usage 7 of 50
4. Usage

4.1 Starting Automation Studio Designer

Automation Studio Designer can be executed by clicking on the shortcut placed on the
users desktop or by following the link: Start > All Programs > Efacec > Automation Studio
> Designer [Version].

The Splash Screen of the Automation Studio Designer is shown while the program loads.

Figure 7 - Automation Studio Designer Splash-Screen

Usage 8 of 50
4.2 Licensing

Figure 8 License type

Before using Automation Studio Designer a software license must be acquired from
1
EFACEC . Available license types include:

Trial This license allows free usage of the application but limits its features

System Integrator Licensed EFACEC system integrator

End User Licensed EFACEC end-user.

Trial License is not available for Automation Studio Designer.

A license can be obtained from EFACEC by stepping through the license wizard. The first
step of the license wizard allows the user to choose the applicable license type.

1
For more information on licensing please contact EFACEC.

Usage 9 of 50
Figure 9 Acquiring a license

In the second window of the process, the user is asked to introduce required license
identification data:

Company name;

Project identification;

2
The actual license may be obtained online or offline by generating a license request file to
be sent to EFACEC.

If the license information is destroyed, changed or corrupted another licensing process will
be required.

Automation Studio licenses are for individual use and single machine only.

2
Online licensing is only available for authorized personnel.

Usage 10 of 50
4.3 Basic Usage

4.3.1 Creating a new Solution

To create a new Designer Solution, the user has the following options:

Select the New>Solution Option on File Menu;

Select New Solution option on Start Page.

Figure 10 - New solution window

After selecting the option, a window (show on the previous figure) is opened and the user
can choose the name and the location of the solution. The location can be indicated with
the full path or can be selected with a Choose Folder form clicking on the button next to
the location text box.

A folder with the solution name is created in the chosen location after clicking the OK
button and a *.asdsln file is created on the folder.

4.3.2 Creating a new Project

To create a new Designer Project, the user has the following options:

Select the New>Project Option on File Menu;

Select New Project option on Start Page.

Figure 11 - New project window

After selecting the option, a window (show on the previous figure) is opened and the user
can choose the name, the location and the type of the project.

The project will be associated with the existing Solution. If the user wants to associate the
project with a new solution, the Create New Solution option can be selected.

If no solution exists, one will be created. *.asdsln file will be created next to the file that
contains project information.

Usage 11 of 50
Two types of Designer Projects can be created:

System;

Library.

In any of these types, designer projects will have the same folder structure, with five
distinct folders:

In contains all project reference of files needed;

Out contains the compressed file with all project files located in Temp folder
(*.aslib for library projects, *.asdev for each device created on system projects);

Runtime contains all files obtained from the device;

Src contains the *.asml with the model information of the project;

Temp contains all files generated after building.

4.3.2.1. System

System projects contain the substation configuration. Each system can have multiple
devices.

4.3.2.2. Library

Library projects contain elements that can be reused on others projects.

4.3.3 Saving a project/solution

The solution can be saved by clicking the Save or Save All button in the toolbar or
selecting Save All or Save Solution in the File Menu.

Unsaved solutions are marked with a * symbol on Solution Explorer.

4.3.4 Adding References

References to libraries can be added to the project. Right-click on the references node of
the project and select Add references option.

By default, three libraries are added to the project:


System;
IEC61850;
IEC611313.
Designer is installed with other libraries included in the folder Includes of the Designer
product folder (by default, [Program Files]\EFACEC\Automation Studio\Designer\[Version]\).
User libraries can also be added.
All the libraries can be added and removed at any time.

Usage 12 of 50
Figure 12 - Add reference(s) window

After selecting this option, a windows form (shown on the previous figure) is opened and
the user can choose the library to add as project reference. A list of the system libraries
(libraries that are available on Includes folder) are shown and can be added by double-
clicking on them or clicking the Add button after selecting one or more libraries.

User libraries can also be added by clicking the Browse button and selecting the *.aslib
file of the library definition.

4.3.5 Adding Elements

Elements can be added to the project by right-clicking on the node, selecting the Add
menu item and choosing the element to add. The elements are grouped by category.

Figure 13 - Adding element on Solution Explorer

All the nodes are aware of which elements can be added, i.e. the user is only shown a list of
elements that can be added to the selected node.

Usage 13 of 50
Figure 14 - Tool box

Adding objects can also be done using the Toolbox pad. Simply click and drag the
element over the node of the Solution Explorer Tree View.

If the toolbox is not visible, the user can select Toolbox option the View menu.

4.3.6 Adding new Device

Devices are special elements. After adding one, a wizard (shown on next figure) appears
to the user and allows him to choose the type of device to add.

Figure 15 - Add device wizard

The wizard will list all the devices templates defined on the project (or on the libraries
added to the project as reference). The wizard is composed by two steps:

Usage 14 of 50
The first step allows the user to choose the type of device to be added;

In the second step the user may choose a template according to the selected
device type.

After selecting the template, a device is created and added to the selected node.

4.3.7 Creating Basic Function Block

To create a Basic Function Block object, the user will have to add an element called ST
Function Block (STFB).

The user can add variables to the STFB by selecting the Add option of the nodes
context. A Reference Form is opened and the user may select the type of the variable. To
edit the code of the STFB, the user has to double-click the node that represents it and use
the ST Editor opened in a tab.

4.3.8 Creating Function Classes

To create a new Function Class, the user will have to add an element called Function
Class (FC).

After selecting the option on the context menu of a node (or selecting the option on Edit
Menu), a wizard will appear, giving the user two options:

1. Create a totally new Function Class, defining its attributes. On the wizard, the user
will have to choose a name for the FC, give a description for it and then click on
the Finish button. The user will not have to choose a type in this case;

Figure 16 - First step of Function Class Wizard

Usage 15 of 50
Figure 17 - Second step of Function Class Wizard

2. Create a FC based on a Logical Node Template (existing on a referenced library,


or defined in the same solution).

In this case, the user will have to select the type of the FC. A reference form will
appear to allow the user to select the type of the FC. A default description is given
to the FC, but the user can change it as well as its name in the correspondent text
boxes.

Figure 18 - Select type of the function

The next step will allow modifying the attributes of the FC. A tree view appears
with all the attributes of the FC. User can change their behaviour or/and add it to
the FC.

Clicking on the Finish button creates a new FC and closes the form.

4.3.8.1. ST Program

For the created object, the user can create a ST Program that will run on the virtual

Usage 16 of 50
machine.

Figure 19 - ST Program window

The user can add a ST Program by selecting the Add/ST Program option on the Programs
Node of the FC.

The main properties of this object are:

Execution indicates the execution kind (Slow or fast);

Priority indicates the execution priority (from 1 to 32);

Scheduling indicates the program scheduling (Cyclic, OnEvent or Both);

Cycle If the selected scheduling was Cyclic or Both a cycle must be defined.

These properties can be set using the Properties Pad, the Program node must be selected
in the Solution Explorer Pad.

To edit an ST Program, the user will have to double-click on the node that represents it, or
select Edit option on the nodes context menu.

The editor that appears is a simple text editor with a few tools to simplify the programs
creation:

Codebits Clicking on the Insert codebits button, the user will access several
snippets with prewritten code: loops, comparisons, arithmetic operations, and
others;

Syntax Highlight The editor will recognize ST language and will paint the code
in different colours to improve readability;

Comments using the two buttons Comment Selected Lines and Uncomment
Selected Lines, the user can comment or uncomment parts of the code;

Indents - using the two buttons Decrease Indent and Increase Indent, the user
can indent parts of the code.

4.3.9 Instantiating Function Classes

To instantiate a Function Class, the user must select the Add option of the context menu
of a Logical Device, adding a Function object.

A Reference Form is opened to select the type of the Function.

Usage 17 of 50
All the Logical Devices are in the folder Resources of the Device.

The name given to the created Function must comply with the following name pattern:
[Prefix][Name of Function Class][Suffix]
Prefix can be freely chosen by the user;
The Name must be exactly the same of the Function Class (case-sensitive);
Suffix must be the number of the instantiation (integer, start in 0).

4.3.10 Defining Hardware

User can define the hardware (HW) of a device in the Hardware section of the IDE.

If the device was created based on an existing template (or imported), most of the HW
elements were already created. Otherwise, the user will have to define the HW by adding
boards to the slots.

Boards can be edited by double-clicking on the node that represents them, or selecting
Edit option of the nodes context menu. A view content (shown in next figure) appears,
listing all the properties of the IO Points of the board.

Figure 20 - Binary IO Application window

4.3.11 BinaryIO Application

To create Logical Objects, the user must add a BinaryIOApplication object on the Access
Points Node.

Selecting Add I/O Point Configuration option, a wizard is shown that allows creating
Logical objects associated with the I/O Points of the Boards.

Usage 18 of 50
Figure 21 - Binary IO Application window

Users have three options (described in the next parts):

1. Logical Input;

2. Logical Output;

3. Controllable Object.

4.3.11.1. Logical Input

Figure 22 - Logical input step

Selecting this option, the user must choose the board of the logical input to create.

All the available physical inputs of the board are displayed on the right of the step. On the

Usage 19 of 50
left part of the step, the user can choose the type of the input to create (simple, double, n
bits or pulse counter) and indicate the different properties of the created object.

4.3.11.2. Logical Output

Figure 23 - Logical output step

Selecting this option, the user only has to select the physical outputs that will be activated
with the created logical output and give it a name.

4.3.11.3. Controllable Object

Figure 24 - Controllable object step

Selecting this option, the user can create a controllable object:

First, creating logical inputs that can be associated with the created object. The
process is the same that for Logical Input Creation;

Finally, user can select the physical output of all the boards in the device that can
be activated with the execution of the created control.

Usage 20 of 50
User only has to indicate the level of output activation (High or Low).

The name of the created controllable object is given on the first step of the creation.

4.3.12 Creating Internal Associations

Figure 25 - Internal association window

Internal associations can be created adding a Device Application to the project. Double-
clicking on the created element (or right-clicking on it and selecting Edit option), a view
content is shown were associations between elements may be defined.

Only data objects can be associated (single points, double points, integer points, controls,
etc.). The elements to associate must be added to the editor by drag-and-drop from the
Solution Explorer to the editor.

Outputs are added on the left of the matrix editor, Inputs on the top of the view. To
associate an output with an input, the user has to click on the box that joins the two
elements.

Unalterable associations are identifiable with a grey box, and the user cant associate the two
elements. An association can only occur between two elements with compatible types.

Tooltips are shown when the mouse holds over elements, the tooltip indicates its full name.

To remove an element of the view, the user right-clicks on the column (or row) of the
element, and select the Remove Section Item option (all the associations created with
the removed element will be automatically destroyed).

Clicking on Clear All option all the associations created on this device application will
removed.

Usage 21 of 50
4.3.13 Creating Logs

Figure 26 - Logger editor window

On the Access Point Node, user can add a Log object. Properties of the created object
can be set on the Property Pad.

User must add Logger object to select the object of the configuration to log. Double-
clicking on the node that represents the object, its editor appears on a view content.

Objects to be logged can be drag-and-drop on the list view of the editor, or selected by
clicking on the button Select Elements on the top of the editor.

The Logger Editor is composed by two parts:

In the left the user can define the Logger properties (On-event, Periodic and the
period) and visualize Log properties;

In the right a list view with all the elements (Composite objects) to log and the
properties to set: Options of logging (Trigger, Data, None), or to visualize: data
type, description, namespace).

Trigger When element changes, the logger logs another entry and the element is logged.
Data The element is logged.
None - The element is not to be logged.

4.3.14 Building

Build has three levels of execution:

1. Solution Selecting Build Solution option of the context menu of the Solution
node (or selecting Build solution option of the Build Menu), all the projects of the
solutions are build. Projects are build in the same order as they are displayed;

Usage 22 of 50
2. Project Selecting Build option of the context menu of the Project node, the
project is built, building all devices existing on the project;

3. Device - Selecting Build option of the context menu of the Device node, the
device is built. All the files generated in the build operation are grouped on the
Temp folder of the project, in a folder with the same name of the device
(Temp/[Device Name]/Out).

Two other associated actions exist for solutions and projects: (i) Clean, that removes all the
files on the project folder, except the *.asml file, and (ii) Rebuild, that performs a Clean
operation followed by a Build.

4.3.15 Deploying

Deploy has two levels of execution:

1. Project - Selecting Deploy option of the context menu of the Project node, all the
devices included on the project are deployed;

2. Device - Selecting Deploy Configuration option of the context menu of the Device
node, the device configuration is deployed to the device using the address defined
in the Configure Connection defined on the device.

A Ping tool is available to test IP defined, by selecting Ping option of the Connect item on
the context menu of the device node.

4.3.16 Validating

All the elements defined on the configuration can be validated, selecting Validate option of
the context menu of the node that represents it.

To validate solutions, user can select Validate Solution of the Build Menu.

Result of the validation appears on the Output Window pad.

Usage 23 of 50
4.4 SCL

A menu SCL is available with all the SCL operations, which are described in this part.

Figure 27 - SCL menu

4.4.1 Validation

After selecting Validate SCL File option of the SCL menu the user is asked to select a
file with an SCL valid extension (*.scl, *.cid, *.icd, *.scd, *.ssd) to validate.

Result of the validation is written on the output window pad.

4.4.2 Exporting

On the Export option of the SCL Menu (with a valid device selected on the Solution
Explorer Pad) there are four choices:

Export Domain Model;

Export IED Capability Description;

Export Configured IED Description;

Export Substation Configuration Description.

After selecting a choice, the user will be asked to input the filename to be saved

4.4.3 Importing

Selecting Import option of the SCL Menu with a valid device selected, the user will have
2 options:

Import Domain Model;

Import IED Capability Description.

In any of these cases, the user will be asked to select the file to import. The imported
element is added to the model at selected position on the Solution Explorer tree view.

Usage 24 of 50
4.5 IEC 61850-8-1

First, the user has to create a IEC 61850-8-1 Server and a IEC 61850-8-1 Client
objects in the access points of the device. Some possibilities to do this:

Clicking on the Add option of the access points context menu;

Dragging from the toolbox pad;

Using the Edit > Add menu.

4.5.1 Server

To edit the IEC 61850-8-1 Server object, the user will have to double-click on the node
that represents the element, or selecting the Edit option on its context menu.

Figure 28 - IEC 61850-8-1 Server editor

IEC 61850-8-1 Server Editor appears in a new tab or if its already loaded, the
corresponding tab will be selected. To include logical nodes the user must drag&drop the
nodes from the source explorer.

Selecting the different options from the context menu, the user can create:

Report Control Block A property pad appears in the right of the editor to edit its
properties;

GSSE Control Block - A property pad appears in the right of the editor to edit its
properties;

GOOSE Control Block - A property pad appears in the right of the editor to edit
its properties;

Usage 25 of 50
Figure 29 - IEC61850-8-1 Server dataset editor

DataSet A DataSet editor appears on the right of the IEC 61850-8-1 Server
editor. The user can drag&drop the elements to include in the dataset and set a
name and a description for it.

IEC 61850-8-1 Server treeview can be filtered by element type on the Filter combo
box.

Selecting the tab Server Profile, the user can set IEC 61850-8-1 properties.

The dataset can only be edited when the Dataset edit mode is checked.

4.5.2 Client

To edit the IEC 61850-8-1 Client object, the user will have to double-click on the node
that represents the element, or selecting the Edit option on its context Menu.

Usage 26 of 50
Figure 30 - IEC 61850-8-1 Client wizard

A wizard appears to the user, allowing him to choose between two options for the source
of the Goose Server:

CID File Selecting this option, the user is asked to choose a *.cid file to open.
The model included in the file will be imported in the project.

Figure 31 - Edit subscriber element wizard

The next step of the wizard allows the user to create a GOOSE Subscriber,
choosing the different elements to include in the defined Goose Control Blocks of
the imported model.

IED in Model Selecting this option, the user must select an IED defined in the
same edited project.

The next step of the wizard will be the same of the previous figure and the Goose
subscriber will be created with the same process.

Usage 27 of 50
4.6 Display

First, the user has to create a Display object in the access points of the device. Some
possibilities to do this:

Clicking on the Add option of the access points context menu;

Dragging from the toolbox pad;

Using the Edit > Add menu.

4.6.1 Display Editor

Figure 32 - Display editor

To edit the Display object, the user will just have to double-click on the node that
represent the element, or selecting Edit option on its context Menu.

Selecting one of these options, the display editor appears in a new view.

If the Display has no pages defined, a pop-up appears to ask to the user to create a
default page on the first edition.

The display editor comes with the most common tools of graphic editors: object selection,
select area, zoom, pen tool, line tool, fill tool, eraser, ellipse tool and rectangle tool.

The user can import a background by selecting an image file. The editor supports common
formats such as BMP, JPG, GIF. Its also possible to export the display as a BMP file.

Another option is to add or remove a page (a combo box is available to navigate between
the different created pages).

Usage 28 of 50
Finally, the user can add (or remove) objects to the page:

Graphical objects Selecting this option, a reference form will appears to the
user to select the symbol object (in the same model or in referenced model) to
add to the page. Next, we will describe with more attention how to create a
graphical object;

Text objects - Selecting this option, a window form (shown on the next figure)
appears that allows him to create the text object. In the form the user can set the
displayed text, the alignment of the object in the page and the scale of it. Clicking
the OK button will add the object to the edited page.

Figure 33 Text Object

All these tools are available on the tool bar of the editor.

4.6.2 Graphical Object Editor

Figure 34 - Graphical object editor

Usage 29 of 50
To create a graphical object, the user has to add a Graphic Symbol object (selecting the
option on the context menu of a valid node, on the Edit Menu or on the tool box pad) to the
model.

To show the editor of the object, the user just has to double-click on the node that
represents it, or select Edit option on its context menu.

The graphical object editor is displayed on a new view.

The available tools to draw are the same as in the Display Editor.

To edit the Graphical object, the user has to create the four images that represent the all
the possible states: on, off, intermediate and invalid.

4.7 Settings

Figure 35 - Settings editor

To visualize the settings for a device, the user has to select the option Settings in the
nodes context menu that represents the device. If it contains setting elements and the
property Setting Group Count of the logical device that owns these elements has a value
bigger than zero, the menu item will be active.

The Settings Editor (the option Settings in the context menu) is opened in a view content.
It is composed by two components:

The tool bar composed by 5 items:

o Export Settings to File that open a SaveDialogFile form to choose the file
to save;

o Import Settings from File that open a OpenDialogFile form to choose the
file to import;

o Get Settings From Device imports settings from a specified device;

Usage 30 of 50
o Send Settings to Device exports settings to a specified device;

o Validate checks if all values comply with their limits. Results of the
validation are displayed in the Output Window.

The list view that shows hierarchically all the settings data objects, displaying its
properties (name, description) and allowing to define the different setting values in
the different Setting Groups. Finally, the user can choose the active setting group
for each Logical Device.

Settings are saved in files with the extension *.settings

Usage 31 of 50
4.8 DNP

To create DNP objects, the user must add a DNP Master element in the access points of
the Device, adding channels to it and creating associations to slaves.

Figure 36 - DNP Slave editor

Upon edition of a Slave (double-clicking the node or selecting its Edit menu item), a DNP
Slave Editor appears on a view content. This editor is composed by 2 components:

A tool bar with the buttons Add Element to create a DNP object and a Edit
Conversion Function button to edit the conversion function of the select DNP
Object;

A list view with all the created DNP objects.

When the user clicks on Add Element, a Data Object DNP wizard window is displayed to
create a DNP Object.

Usage 32 of 50
Figure 37 Data Object DNP wizard first step

In the first step of the wizard, the user must give a name, a description and a type to the
data object. Some types require the definition of the field Type of DNP object. The next
step also differs with the chosen type.

Figure 38 - Example of Data Object DNP wizard second step

DNP Slaves must be associated with a DNP Profile.

Usage 33 of 50
4.9 Log Viewer

The log viewer can be accessed through the context menu at device nodes. Possible
actions are viewing, sorting, paging, filtering and exporting the log.

Figure 39 Log Viewer

4.9.1 Viewing

The viewer automatically loads the log and displays the first and last entry time, sorting by
entry id in a descending order.

To improve usability entry ids are grouped using different background colours, cell
borders and hiding repeated information.

4.9.2 Sorting

It is possible to sort the log by the Entry, Time and Name columns. To perform this
action the user has to click on the corresponding header cell has show below. Alternating
order can be done by pressing the cell another time.

Usage 34 of 50
Figure 40 Log Viewer sort

4.9.3 Filtering

The log can be filtered through the Variable Name, Start Date and End Date fields,

wildcards may be applied using the * character.

After defining the filters press the Apply button to filter the log. Clicking the filter name
enables or disables it. Finally the panel may be hidden on the Filter button.

Figure 41 Log Viewer filters

4.9.4 Paging

Paging is done using the navigator located in the bottom. It can be used to show the first,
previous, next and last page. Furthermore if the user knows the exact page he wants to
see he can enter the page number in the textbox located in the middle of the navigator.

Figure 42 - Log Viewer pagination

4.9.5 Showing and hiding columns

Clicking the right mouse will show a context menu, in the View item a list of all available
columns are shown to toggle their visibility.

4.9.6 Exporting

The log viewer allows the user to export records into a CSV file, where the field separator
is a tab character. After pressing the export button, an export entries form shows two
choices.

Figure 43 - Log Viewer export to CSV

Filtered Items - Only filtered entries will be exported.

Usage 35 of 50
All Items - Entire log will be exported.

In any of these options sort order is maintained and only visible columns are considered.

Usage 36 of 50
4.10 Driver

Figure 44 Driver context menu

Before using driver it is necessary the connection must be configured using the Configure
Connection menu item. All driver functionalities require valid credentials.

Available options depend on the device capabilities.

Available options are:

Reset - To reset a device, the user must select Online>Reset Option on the
context menu of the node that represents the Device.

Restore Default Configuration - This functionality will restore the device with a
default configuration.

Deploy - To deploy the created configuration to a device, the user must select
Online>Deploy Configuration Option on the context menu of the node that
represents the Device.

Update Firmware - This option updates the device firmware.

Get Configuration - To get the device current configuration, the user must select
Online>Get Current Configuration option on the context menu of the node that
represents the Device.

Get System Log - To get the device log files, the user must select Online>Get
System Log Option on the context menu of the node that represents the Device.

Get Event Log - To get the device event log, the user must select Online>Get
Event Log Option on the context menu of the node that represents the Device.
If the action succeeds a log viewer is opened.

Get All Files - To get all available device files, the user must select Online>Get
All Files Option on the context menu of the node that represents the Device.

Usage 37 of 50
4.11 Other Features

4.11.1 Tagged Values Editor

Figure 45 - Tagged values editor

This editor allows the user to visualize the Tagged Values of the selected object in the
Solution Explorer Pad.

The editor is a simple list view that allows the user to set the values of select tagged
values or change their names. Buttons in the tool bar allow the user to add or remove
tagged values

By default this editor is hidden and is only displayed selecting Tagged Values option in the
View menu.

Tagged Values are elements that add semantics to model elements.

Normally, the user will not have to change any tagged values, and/or another editor is
provided to change the value.

4.11.2 Reference Form

Figure 46 - Reference form

This form is widely used across the Designer. It allows selecting objects from the model
(or referenced) in a Tree View (Folder View option) or in a List View (Flat View option)
objects.

Usage 38 of 50
All the checked objects are added to the selection.

Properties button shows a property pad in the form to visualize properties of the selected
object. Clear All removes the check from all nodes.

OK Button is activated only if the selection is valid for the operation.

4.11.3 Object Browser

Figure 47 - Object Browser view content

Object Browser Pad allows visualization of objects included in referenced libraries;

It is composed by two components: in the left, a tree view with all the library objects, in the
right, a property pad to visualize the selected object properties.

The tree view is read-only and the objects can not be edited.

4.11.4 Properties

Automation Studio Designer provides a Properties Pad, which allows the user to visualize
the properties of selected objects.

The properties can be ordered alphabetically or by category. The property description

Usage 39 of 50
panel can be hidden.

Figure 48 - Properties pad

4.11.5 Output

Figure 49 - Output window

Automation Studio Designer provides an Output Window to display all the messages to
the user on a pad.

4.11.6 Ping

Figure 50 - Ping task

Automation Studio Designer provides to the user a Ping Tool. Results are print on the

Usage 40 of 50
Output Window.

This tool is available selecting Connect>Ping option of the context menu of a Device
object.

The Ping option is only available if an IP Address is defined for the device.

4.11.7 Designer Options

Figure 51 - Options window

Automation Studio Designer has several settings that can be configured by the user.
These settings can be changed on the options window, available on the Tools menu
(Tools>Options).

4.11.8 Browser Window

The user can open a Browser Window on Automation Studio Designer clicking on New
Browser Window under the View Menu.

Usage 41 of 50
Figure 52 - Browser window

4.11.9 About

Figure 53 - About box

The About window of the Automation Studio Designer can be visualized clicking on the
About option under the Help menu.

Usage 42 of 50
It contains information about the installed version of Automation Studio Designer and its
License.

Usage 43 of 50
ANNEXES

A1. Automation Studio Server

To create an Automation Studio Server, the user must add a reference in its project to the
library AutomationStudio. This library exists in the Included libraries folder of the product.

The user must install Automation Studio Server application to simulate the behaviour of a
configured device.

A1.1. Adding Device

Figure 54 - Add device wizard

To Add an Automation Studio Server, the user can:

Select Add Device option on the Device Menu;

Select Add>System>Device option of the context menu of the node that the
device will be added to (Project node, System node, etc.);

Drag&Drop Device Object from the tool box to the Solution Explorer.

A wizard (shown in the previous figure) appears and allows the user to select the devices
template. The wizard is composed by two steps: one to select the type of Device, and the
second to select available templates of that type.

After the selection, a pre-configured Automation Studio Server (with the hardware
definition, the access points defined, etc.) is added to the project.

Usage 44 of 50
A1.2. Test Device

To test an Automation Studio Server, the user must select Test>Test Device option of
the servers context menu.

Figure 55 - Automation Studio Server remote console

The application opens Automation Studio Server and prints the results of the remote
console in the Output Window.

A1.3. IO Simulator Panel

Automation Studio Server application provides an I/O Simulator to simulate the inputs and
outputs of a server.

To run the IO simulator, the user must select Test>IO Simulator option of the servers
context menu.

Figure 56 - IO Simulator panel

The inputs and outputs of the simulator represent the IO Points defined in the servers IO
Boards.

A1.4. Driver

All driver options are available in the BCU500, except the update firmware functionality.

Usage 45 of 50
A2. BCU 500

To create a BCU 500 Device, the user must add a reference in its project to the library
Syrius. This library exists in the Included libraries folder of the product.

A2.1. Adding Device

Figure 57 - Add Device wizard

To Add a BCU 500 Device, the user can:

Select Add Device option on the Device Menu;

Select Add>System>Device option of the context menu of the node that the
device will be add to (Project node, System node, etc.);

Drag-and-drop Device Object from the tool box to the Solution Explorer.

A wizard (shown in the previous figure) appears and allows to the user selecting the
template of the device. The wizard is composed by two steps: one to select the type of
Device, and the second to select available templates of that type.

After the selection, a pre-configured BCU 500 (with the hardware definition, the access
points defined, etc.) is added to the project.

A2.2. Creating e Editing Digital I/O

See BinayIO Application for more details.

A2.3. Analog I/O Configuration

There are three kinds of Analog I/O Boards: MAP8080 (AC), MAP 8081 (DC) and MAP
8082 (AC).

Usage 46 of 50
A2.4. AC

Figure 58 - AC IO Point configuration

AC IO Points are configured in the Property Pad. For each AC input, user must define its
rated current.

The template for the BCU 500 has the correct default properties for the AC inputs. Change it
only if needed.

Usage 47 of 50
A2.5. DC

Figure 59 - DC IO Point editor

DC IO Points has an editor to define the conversion function. There are four types of
functions:

Direct;

Linear the user must set Slope and OffSet properties;

Piecewise Linear the user must indicate the number of points and variables
values;

Polynomial - the user must indicate parameter values.

The range of the DC input must be set on the property pad.

The template for the BCU 500 has the correct default properties for the AC inputs. Change it
only if needed.

A2.6. Editing Time zone

To edit the time zone of a device, the user must select the Edit timezone option on the
devices context menu.

Usage 48 of 50
Figure 60 - Timezone editor

The timezone editor is relatively simple and allows adjusting the time of the offset (relative
to GMT) and the Day Light Savings. The start and the end of the Day Light Savings can
be defined relative to the day of year or a specific day (defining the day, the week and the
month).

A2.7. Driver

All driver options are available in the BCU500. In the update firmware functionality it is
possible to select the hardware components to be updated (Master, HMI, DSP).

Usage 49 of 50
Subject to change prior notice.

This document contains general information and descriptions of available technical


options, which may not be present in individual cases. The required features should
therefore be specified in each individual contract.

If you have any questions regarding this product please contact EFACEC.

EFACEC Sistemas de Electrnica, S.A.

Rua Eng Frederico Ulrich

Apart. 3078

4471-907 Moreira Maia

PORTUGAL

Tel: +351 22 940 2000

Fax: +351 22 948 5428

Web: http://www.efacec.pt/

Email: se@efacec.pt

Usage 50 of 50