SYS600 Application Design

MicroSCADA Pro
SYS 600 *9.1

Application Design
Configuration Manual
1MRS755387 MicroSCADA Pro SYS 600 *9.1
Issued: 30.06.2004 Application Design
Version: C/25.02.2005
1. About this manual ...................................................................11

1.1. Copyrights ...................................................................................11
1.2. Trademarks .................................................................................11
1.3. General .......................................................................................11
1.4. Use of symbols ............................................................................12
1.5. Document conventions ................................................................12
1.6. Terminology ................................................................................13
1.7. Related documents .....................................................................14
1.8. Document revisions .....................................................................14
2. Migrating an existing MicroSCADA application in the
new process graphics 15
2.1. Introduction to migration tools .....................................................15
2.2. Exporting information from pictures to data files .........................16
2.2.1. Configuration Data Export Tool ........................................17
2.2.1.1. Starting Configuration Data Export Tool ............17
2.2.1.2. Options ...............................................................18
2.2.1.3. Exporting picture data ........................................19
2.3. Event conversion .........................................................................19
2.3.1. Event Conversion Tool .....................................................20
2.3.1.1. Starting Event Conversion Tool .........................20
2.3.1.2. Making conversion .............................................21
3. Creating new MicroSCADA Pro application with new
process graphics ....................................................................23
3.1. List Based Engineering tool ........................................................24
3.1.1. System Requirements ......................................................25
3.1.2. Using the tool ...................................................................25
3.1.3. Create sheet ....................................................................26
3.1.3.1. Columns .............................................................27
3.1.3.2. User interface components ................................28
3.1.3.3. Tips for using Create sheet ................................29
3.1.3.4. Exception handling in Create sheet ...................29
3.1.4. Symbols, Mappings and Data Source sheets ..................32
3.1.4.1. Columns .............................................................33
3.1.4.2. User interface components ................................35
3.1.5. Defaults sheet ..................................................................36
3.1.6. Clipboard sheet ................................................................37
3.2. Object Navigator engineering ......................................................37
3.2.1. Installing standard functions ............................................37
3.2.1.1. Standard Functions of LIB 5xx and SA-LIB ........38
©Copyright 2005 ABB Oy, Substation Automation Products, Vaasa, FINLAND 3

SYS 600 *9.1 MicroSCADA Pro 1MRS755387
Application Design
3.2.1.2. Installation and configuration of standard

functions ............................................................ 38
3.2.1.3. Connecting standard function to existing
process objects .................................................. 41
3.2.2. Connecting standard functions to display ........................ 42
3.3. Connectivity package support ..................................................... 43
3.4. Using Input Objects .................................................................... 44
4. Standard functions of SA-LIB ............................................... 47
4.1. Preliminary work ......................................................................... 47
4.2. Communication support .............................................................. 47
4.3. Station ......................................................................................... 47
4.3.1. Standard function installation .......................................... 47
4.3.1.1. Symbol installation ............................................. 47
4.3.2. Standard function configuration ....................................... 48
4.3.2.1. Configuration with a tool .................................... 48
4.3.2.2. Configuration with the Process Object Tool ....... 48
4.3.2.3. Example of a station configuration ..................... 50
4.3.3. Application engineering information ................................. 50
4.3.3.1. Structure of the station standard function .......... 50
4.3.3.2. Files ................................................................... 50
4.3.3.3. Language text file .............................................. 50
4.3.3.4. Help text file ....................................................... 50
4.3.3.5. Configuration files .............................................. 51
4.3.3.6. Other text files .................................................... 51
4.3.3.7. Process objects ................................................. 51
4.3.3.8. Scale objects ..................................................... 52
4.3.3.9. Command procedures ....................................... 52
4.3.3.10.Event channels .................................................. 52
4.4. Bay .............................................................................................. 52
4.4.2.1. Configuration with tools ..................................... 53
4.4.2.2. Configuration of process objects ....................... 53
4.4.2.3. Example of a bay configuration ......................... 55
4.4.3.1. Structure of the bay standard function ............... 55
4.4.3.2. Files ................................................................... 56
4.4.3.4. Help text file ....................................................... 56
4
Application Design
4.4.3.6. Other text files ....................................................56

4.4.3.7. Command procedures ........................................57
4.4.3.8. Process objects ..................................................57
4.4.3.9. Scale objects ......................................................58
4.4.3.10.Event channels ..................................................58
4.5. Switching device .........................................................................59
4.5.1. Standard function installation ...........................................59
4.5.1.1. Symbol installation .............................................59
4.5.2. Standard function configuration .......................................60
4.5.2.1. Configuration with tools ......................................60
4.5.2.2. Configuration of process objects ........................61
4.5.2.3. Example of a switching device configuration .....62
4.5.3. Application engineering information .................................63
4.5.3.1. Structure of the switching device standard
function ...............................................................63
4.5.3.2. Files ....................................................................63
4.5.3.3. Language text file ...............................................63
4.5.3.4. Help text file .......................................................63
4.5.3.5. Configuration files ..............................................64
4.5.3.6. Other text files ....................................................64
4.5.3.8. Process objects ..................................................65
4.5.3.9. Scale objects ......................................................71
4.6. Tap changer ................................................................................71
4.6.0.1. Standard function installation .............................71
4.6.0.2. Symbol installation .............................................71
4.6.1. Standard function configuration .......................................72
4.6.1.1. Configuration with tools ......................................72
4.6.1.2. Configuration of process objects ........................73
4.6.2. Example of a tap changer configuration ..........................74
4.6.3. Application engineering information .................................74
4.6.3.1. Structure of the tap changer standard function ..74
4.6.3.2. Files ....................................................................74
4.6.3.3. Language text files .............................................75
4.6.3.4. Help text file .......................................................75
4.6.3.5. Configuration files ..............................................75
4.6.3.6. Other text file ......................................................76
4.6.3.8. Process objects ..................................................77
4.6.3.9. Scale objects ......................................................78
4.7. Measurement ..............................................................................78
5
Application Design

4.7.2.3. Example of measurement configuration ............ 82
4.7.3.1. Structure of the measurement standard function 83
4.7.3.2. Files ................................................................... 83
4.7.3.4. Help text file ....................................................... 83
4.7.3.6. Other text files .................................................... 84
4.7.3.7. Command procedures ....................................... 84
4.7.3.8. Process objects ................................................. 85
4.7.3.9. Scale objects ..................................................... 86
4.8. Alarm indicator ............................................................................ 87
4.8.2. Example of alarm indicator configuration ......................... 89
4.8.3.1. Structure of the alarm indicator standard
function .............................................................. 89
4.8.3.2. Files ................................................................... 89
4.8.3.4. Help text file ....................................................... 90
4.9. Auto Reclose .............................................................................. 90
4.9.2.1. Structure of the Auto Reclose standard function 92
4.9.2.2. Files ................................................................... 92
4.9.2.4. Help text file ....................................................... 93
4.9.2.6. Process objects ................................................. 93
6
Application Design
4.9.2.7. Scale objects ......................................................94

4.10.Trip Signal ..................................................................................94
4.10.1.Standard function installation ...........................................94
4.10.1.1.Symbol installation .............................................94
4.10.1.2.Configuration with tools ......................................95
4.10.1.3.Configuration of process objects ........................95
4.10.2.Application engineering information .................................96
4.10.2.1.Structure of the Trip Signal standard function ....96
4.10.2.2.Files ...................................................................96
4.10.2.3.Language text file ...............................................96
4.10.2.4.Help text file .......................................................96
4.10.2.5.Configuration files ..............................................97
4.10.2.6.Process objects ..................................................97
4.10.2.7.Scale objects ......................................................97
4.11.Generator ...................................................................................97
4.11.1.Standard function installation ...........................................97
4.11.2.Symbol installation ...........................................................98
4.11.3.Configuration with tools ....................................................98
4.11.4.Configuration of process object .......................................98
4.11.5.Application engineering information .................................98
4.11.5.1.Structure of the generator standard function .....98
4.11.5.2.Files ...................................................................99
4.11.5.3.Language text file ...............................................99
4.11.5.4.Help text file .......................................................99
4.11.5.5.Configuration files ..............................................99
4.11.5.6.Process object ...................................................99
4.11.5.7.Scale object .......................................................99
4.12.Line Indicator ............................................................................100
4.12.1.Standard function installation .........................................100
4.12.2.Symbol installation .........................................................100
4.12.3.Configuration with tools ..................................................100
4.12.4.Configuration of process objects ....................................101
4.12.5.Application engineering information ...............................101
4.12.5.1.Structure of the line indicator standard function 101
4.12.5.2.Files .................................................................101
4.12.5.3.Language text file .............................................101
4.12.5.4.Help text file .....................................................102
4.12.5.5.Configuration files ............................................102
4.12.5.6.Command procedures .....................................102
4.12.5.7.Process objects ................................................102
4.12.5.8.Scale object .....................................................102
7
Application Design
4.13.Descriptions to the configurable attributes ............................... 103

5. Creating single-line diagram ............................................... 123
5.1. Connecting signals ................................................................... 124
5.2. Busbar coloring ......................................................................... 126
5.3. Launching external application from process displays ............. 129
5.4. USE CASE - Building an electric network from several
substations ................................................................................ 132
5.4.1. Description ..................................................................... 132
5.4.2. Scenario 1: Using external color handling ..................... 132
5.4.3. Scenario 2: Use of an additional circuit breaker and an
earthing switch ............................................................... 133
5.4.4. Scenario 3: Building stations to the same picture .......... 133
6. Adaptations to application window .................................... 135
6.1. Customizing application window ............................................... 135
6.1.1. Customizing application layout (GUI) ............................ 135
6.1.2. Customization dialog ..................................................... 135
6.1.2.1. Toolbars tab ..................................................... 137
6.1.2.2. Commands tab ................................................ 140
6.1.2.3. Options tab ...................................................... 141
6.1.3. Resetting layout ............................................................. 141
6.1.4. Object specific custom menus ....................................... 141
7. Event List .............................................................................. 145
7.1. Introduction to Event List .......................................................... 145
7.2. Customizing the column layout ................................................. 146
7.2.1. Defining event coloring .................................................. 148
7.2.2. Event coloring example ................................................. 148
7.3. Preconfiguring events with advanced conditions ...................... 149
7.3.1. Advanced condition example ......................................... 149
8. Alarm List .............................................................................. 151
8.1. Introduction to Alarm List .......................................................... 151
8.2. Customizing column layout ....................................................... 152
8.3. Preconfiguring alarm buffer with advanced conditions ............. 154
8.3.1. Advanced condition, example 1 ..................................... 154
8.3.2. Advanced condition, example 2 ..................................... 155
9. Blocking List ......................................................................... 157
9.1. Introduction to Blocking List ...................................................... 157
9.2. Customizing blocking settings .................................................. 158
10.Trends ................................................................................... 159
10.1.Introduction to trends ............................................................... 160
10.2.Copying the trends ................................................................... 160
8
Application Design
10.3.Exporting trends to the .csv or .txt file ......................................160

10.4.Trend Display parameters ........................................................161
10.5.Application objects ....................................................................161
10.6.Data objects ..............................................................................161
10.7.Time channels ..........................................................................162
11.Localization of application ..................................................163
11.1.Language identifiers .................................................................163
11.2.Text Translation Tool ................................................................163
11.3.Text databases .........................................................................163
11.4.Monitor Pro, tools and components ..........................................164
11.5.Basic workflow of localization ...................................................164
11.6.Basic work flow in translating Monitor Pro, tools and
components ...............................................................................167
11.7.Using new language in Monitor Pro ..........................................172
12.Index ......................................................................................173
9
Application Design
1. About this manual
1.1. Copyrights
The information in this document is subject to change without notice and should not
be construed as a commitment by ABB Oy. ABB Oy assumes no responsibility for
any errors that may appear in this document.
In no event shall ABB Oy be liable for direct, indirect, special, incidental or
consequential damages of any nature or kind arising from the use of this document,
nor shall ABB Oy be liable for incidental or consequential damages arising from use
of any software or hardware described in this document.
This document and parts thereof must not be reproduced or copied without written
permission from ABB Oy, and the contents thereof must not be imparted to a third
party nor used for any unauthorized purpose.
The software or hardware described in this document is furnished under a license
and may be used, copied, or disclosed only in accordance with the terms of such
license.
Copyright © 2005 ABB Oy
All rights reserved.
1.2. Trademarks
ABB is a registered trademark of ABB Group. All other brand or product names
mentioned in this document may be trademarks or registered trademarks of their
respective holders.
1.3. General
This manual provides information for application engineers, who build up the
MicroSCADA applications for the new MicroSCADA Pro Monitor type.
The steps for application engineering are:
• A totally new MicroSCADA application is constructed by using the
engineering tools with new process graphics
• Constructing process displays with Display Builder
• Mapping the graphical symbols of process displays to process MicroSCADA
application’s database by dragging and dropping complete objects
• Customizing the automatically configured dynamic busbar coloring
• Adjusting the new list and trend display
• Customizing the menus and toolbars of the application window of
MicroSCADA Pro Monitor
• Localizing the application texts by using engineering tools
11
Application Design
1.4. Use of symbols

This publication includes warning, caution, and information icons that point out
safety related conditions or other important information. It also includes tip icons to
point out useful information to the reader. The corresponding icons should be
interpreted as follows:
The warning icon indicates the presence of a hazard which could

result in personal injury.
The caution icon indicates important information or warning related

to the concept discussed in the text. It might indicate the presence of
a hazard which could result in corruption of software or damage to
equipment or property.
The information icon alerts the reader to relevant facts and

conditions.
Although warning hazards are related to personal injury, and caution hazards are
associated with equipment or property damage, it should be understood that
operation of damaged equipment could, under certain operational conditions, result
in degraded process performance leading to personal injury or death. Therefore,
comply fully with all warning and caution notices.
1.5. Document conventions

The following conventions are used for the presentation of material:
• The words in names of screen elements (for example, the title in the title bar of a
dialog, the label for a field of a dialog box) are initially capitalized.
• Capital letters are used for the name of a keyboard key if it is labeled on the
keyboard. For example, press the CTRL key. Enter key is an exception, e.g. press
Enter.
• Lowercase letters are used for the name of a keyboard key that is not labeled on
the keyboard. For example, the space bar, comma key and so on.
• Press CTRL+C indicates that you must hold down the CTRL key while pressing
the C key (to copy a selected object in this case).
• Press ESC E C indicates that you press and release each key in sequence (to copy
a selected object in this case).
• The names of push and toggle buttons are boldfaced. For example, click OK.
• The names of menus and menu items are boldfaced. For example, the File menu.
• The following convention is used for menu operations: Menu Name > Menu
Item > Cascaded Menu Item. For example: select File > Open > New
Project.
• The Start menu name always refers to the Start menu on the Windows Task
Bar.
12
Application Design
• System prompts/messages and user responses/input are shown in the Courier

font. For example, if you enter a value out of range, the following message is
displayed:
Entered value is not valid. The value must be 0 to
30.
You may be told to enter the string MIF349 in a field. The string is shown as follows
in the procedure:
MIF349
• Variables are shown using lowercase letters:
sequence name
1.6. Terminology
Action tool; tool Used to perform an action within the application. It can be a menu item
or a toolbar tool. A tool can be any of the following types: button, drop-
down button, textbox, combo box, label, separator.
Band Action tool container which can be menu, toolbar, status bar, or pop-up
menu.
Context menu Pop-up menu which is displayed by clicking the right mouse button.
Detatchable band Submenu or subband that can be torn off by using the detach grab
handle to make it float on the screen.
Docking area Monitor Pro defines four docking areas on the top, bottom, right and left
edges of the control's dialog. It also defines an area for free position
(floating).
Docking line Each docking area can have multiple docking lines where the bands
are positioned.
Floating band Band that can be positioned anywhere on the screen while the
application has focus.
Pop-up menu Pop-up menu is displayed as a submenu for an another tool.
13
Application Design
1.7. Related documents
Name of the manual MRS number

MicroSCADA Pro SYS 600 Operation Manual 1MRS755307
MicroSCADA Pro SYS 600 Process Display Design 1MRS755379
MicroSCADA Pro SYS 600 Installation and Administration Manual 1MRS755409
MicroSCADA Pro SYS 600 System Objects 1MRS751847-MEN
MicroSCADA Pro SYS 600 Application Objects 1MRS751848-MEN
1.8. Document revisions
Version Revision number Date History

A 9.0 30.06.2004 Document created
B 9.0 15.11.2004 Additions and error corrections in chapters 3, 4
and 6
C 9.1 25.02.2005 -Localization tool additions
-Trend display extentions
-SA-LIB extentions
-Connectivity support added
-Using input objects added
14
Application Design
2. Migrating an existing MicroSCADA application

in the new process graphics
2.1. Introduction to migration tools

This section provides information on the migration tools needed during the
application design, when the existing pictures are migrated to use MicroSCADA Pro
Monitor’s new process graphics.
Usually, an existing MicroSCADA application contains a set of pictures and their
related process database built with LIB 5xx application library. MicroSCADA Pro
Control System SYS 600 contains the engineering tools to migrate these
applications in a straightforward way. During the migration, the information from
the existing pictures is exported to a set of data files. These data files are then used
by the faceplates of MicroSCADA Pro Monitor. The connection between the
existing process objects of the migrated application and graphical symbols of the
new process displays is made by dragging and dropping the complete objects during
the single line diagram engineering with SYS 600 Display Builder.
LIB 5xx application MicroSCADA Pro

application
Connect to
process
objects
PDB
Read
Export configuration
configuration of the objects
Data files
CDE
Fig. 2.1.-1 Migrating process

Another migration tool is needed for the new event handling concept introduced in
the SYS 600 MicroSCADA Pro Control System. In this concept, the new Event
Objects are displayed in the application’s process database. Another event
architecture has been used with the existing application, which database has been
built with LIB5xx application library and contains the LIB 500 Event List. To
provide a continuum from the existing LIB 500 Event List to the new SYS 600 Event
15
Application Design
List, the migration tool to migrate the existing application to the new event handling
concept is introduced. The following figure describes both the event handling
processes and the role of migration tool.
A040355
Fig. 2.1.-2 Event conversion process

LIB 500 Event List concept:
1. The value of the process object is updated
2. Format picture is activated
3. Format picture reads the text related to the event from the text file and shows it
in the Event List
Event Conversion Tool:
4. Reads all the format pictures and related text files found from the application
5. Puts texts to text database, creates Event Objects, connects Process Objects to
Event Objects
MicroSCADA Pro Event List concept:
6. The value of the process object is updated
7. Event object is activated. Event Object contains the reference to text database,
from where the textual presentation of event is fetched
2.2. Exporting information from pictures to data files

In a LIB5xx based picture, the parameters describing the object and its behaviour is
stored in the picture. When the new process displays are used with an existing
process database, these parameters need to be extracted from the pictures and made
available for the new faceplates.
16
Application Design
The new Configuration Data Export Tool is used for this purpose. It extracts the
needed information from the pictures and stores it in separate files available for the
new process displays.
2.2.1. Configuration Data Export Tool

The Configuration Data Export Tool offers the means to reuse the pictures and
process database built with LIB 5xx application library, when an application is
upgraded to the MicroSCADA Pro environment.Configuration Data Export Tool
can separate the configuration of the picture functions from the SCIL picture.
When the configuration data files are exported, they can be connected to the single
line diagram built with SA graphics symbols. For more information on the picture
engineering, refer to SYS 600 Process Display Design manual.
By default, SA control dialogs can connect to the configuration made with LIB 510
MV Process. However, it is possible to export data from any picture function that is
designed according to LIB 5xx design rules.
2.2.1.1. Starting Configuration Data Export Tool

Configuration Data Export Tool can be started by clicking the DAT Export button
in the Tool Manager dialog, Miscellaneous tab.
CDE_Icon
Fig. 2.2.1.1.-1 Configuration Data Export Tool icon
17
Application Design
Main view
CDE_Tool
Fig. 2.2.1.1.-2 Main view of the tool

The Source directory shows where the SCIL pictures are located. The Destination
directory shows where the data files are exported when the exporting is made. In
practice, this always has to be /POBJCONF directory under the application. When
the Override existing configuration files option is checked, the configuration file is
recreated, if there already is a file with the same name in the destination directory.
The SCIL pictures found from the source directory are listed in the Pictures tab.
2.2.1.2. Options
The purpose of the Export Options is to filter out the picture functions that are not
related to the process graphics. These kind of functions are, for example,
components that were used for building the busbar coloring into the LIB 500 single
line diagrams.
In this way, the amount of the data files can be reduced. Also, by having this kind of
filter, the creation of unnecessary data files will be prevented.
18
Application Design
Exp_Opt
Fig. 2.2.1.2.-1 Export Options
2.2.1.3. Exporting picture data

To export configuration data from picture do as follows:
1. Select the picture(s) in the Pictures list from which you want to export data.
2. Select filter from the Options dialog.
3. Click the Export button.
For more information on how to finalize the picture engineering, refer to SYS 600
Process Display Design manual.
2.3. Event conversion

In LIB 500 Event List, the format pictures are used for showing the dynamic part of
the event text. However, the event text presentation in SYS 600 Event List is based
on the Event Objects. When SYS 600 Event List on MicroSCADA Pro Monitor is
used with an existing process database, the format picture mechanism must be
integrated into the new event handling concept.
The new Event Conversion Tool offers the means to convert the used format picture
concept into a new event handling concept. In practice, this means that each process
object that has a known LIB 5xx format picture, is connected to a comparable Event
Object. When the event conversion is done, the same event texts are shown in the
SYS 600 Event List and in the LIB 500 Event List.
19
Application Design
2.3.1. Event Conversion Tool

The purpose of Event Conversion Tool is:
• To locate the used, known LIB 5xx format pictures from the process objects of
the application.
• To create the related Event Objects that the new event handling concept needs.
• To separate event texts from the text files, and write them to a text database file
(APL_TEXT.SDB) of the running application.
• To connect the created Event Objects to the text identifiers that are located from
the text database file.
• To connect process objects to event objects.
Format pictures are still needed to print the events to the Event
Printer. Due to this, the format picture information in process
database is not modified during the conversion.
2.3.1.1. Starting Event Conversion Tool

The Event Conversion Tool is started from the Tool Manager dialog in the
Miscellaneous tab. Click the Event Conversion button to start the Event Conversion
Tool.
EC_icon
Fig. 2.3.1.1.-1 Icon for opening Event Conversion Tool
EC_Tool
Fig. 2.3.1.1.-2 Main view of Event Conversion Tool
20
Application Design
The Event Conversion Tool contains three tabs: Found Event Text Conventions, Not
Resolved and Modified Process Objects.
Found Event Text Conventions tab shows all the supported format picture
conventions found from the application. The conventions within the application can
be examined by clicking Search.
The Format picture field shows the name of the format picture (PF attribute of
process object). The Text file field shows the language text file related to the format
picture. Sometimes the event text does not come from the text file, but the value of
the process data is shown directly in the Event List (OV-attribute). In this kind of
cases a text *Value based form* is shown in the field. The Event object field shows
the name of the event object or objects where the process object is connected.
When the modification of the process database is done, the Not resolved tab shows
all process objects that are not connected to the event object. Possible reasons for the
process objects to not connect are:
• Not supported software package. The process objects are not recognized, if they
are made by using the LIB4 application library. Supported libraries are LIB 500,
LIB 520, LIB 530, LIB 542 and LIB 580.
• Not supported form convention. Some format pictures have internal logic that is
not possible to write open by the Event Conversion Tool.
• Language text file not found. It is not possible to read the language text file.
• Event text could not be resolved. Event Conversion Tool does not recognize the
text file format and therefore cannot resolve the text.
Modified Process Objects tab shows the list of all process objects that are
successfully connected to event objects.
2.3.1.2. Making conversion

The conversion can be done by clicking the Search button, which looks for the
known conventions within the application. Clickin the Modify DB button makes the
changes to the process database. If you do not want to examine the event
conventions beforehand, you can click the Modify DB button directly.
When the conversion is ready, the result can be saved to a log file. The log file
contains all the data found from three tabs in the Event Conversion Tool.
It is recommended to take a backup from the application (process

database) before making the event conversion.
21
Application Design
3. Creating new MicroSCADA Pro application with

new process graphics
With the LIB based pictures, a lot of engineering tasks were made in the Picture
Editor, for example drawing pictures, creating the process database, and so on. In the
MicroSCADA Pro Control System SYS 600 the engineering tasks during
application design are changed. The new engineering can be divided in two different
approaches: list based engineering and Object Navigator engineering.
From the two different engineering approaches, the Object

Navigator engineering is preferred.
List based engineering

A new Microsoft Excel based engineering tool is introduced by means of which the
creation of objects (stations, bays, devices, measurements, and so on) is done
efficiently. Also the new process displays can be configured with this tool. As this
tool is based on Microsoft Excel, the handling of large amounts of data is quite
efficient. The following figure describes the list based engineering approach.
A050006
Fig. 3.-1 List based engineering approach
23
Application Design
Object Navigator engineering

Complete objects, for example switching devices, transformers, measurements, as
well as LIB standard functions, can now be installed and configured directly in the
Object Navigator. Installing such an object means that the corresponding process
objects are created and object parameters are stored in the application, but no
process display elements are built.
These objects are installed during the single line diagram engineering in the process
displays by the drag and drop operation. In this operation, all the connections
between the display elements and process database are automatically configured.
The following figure describes the Object Navigator engineering approach.
A040354
Fig. 3.-2 Object Navigator engineering approach
3.1. List Based Engineering tool

List Based Engineering tool (LBE) is an efficient way to create process objects from
a scratch in SYS 600/LIB applications.
Creating and configuring the process objects with LBE tool requires:
• Knowledge on LIB engineering.
• Information on how the attribute values are stored in the MicroSCADA Pro
configuration data files.
• Information on how the process displays are created with Display Builder.
Technically, the tool is a Microsoft Excel document that contains:
• A sheet to specify naming convention and per-bay amounts of each supported
process object type.
24
Application Design
• One sheet for each supported process object type to fill in the process object
configuration data.
• A sheet to create, edit and delete graphical objects (symbols) in process
displays.
• A sheet to define mappings between subdrawing data variables and display
data variables.
• A sheet to create, edit and delete data variables in data sources of process
displays.
• A sheet that contains default values and settings.
• A Clipboard sheet for the user to store temporary data.
The user interface components are provided to execute Visual BASIC for
Applications (VBA) macros that generate default names and configurations to the
LIB object sheets, perform write operations to the MicroSCADA Pro process
database, provide informative exception handling and operate with graphical objects
in process displays.
3.1.1. System Requirements

In addition to MicroSCADA Pro Control System SYS 600 software requirements
(see the Installation and Administration Manual), LBE tool has the following
requirements:
• Microsoft Excel 2000 or later
• Existing empty or non-empty LIB application in HOT state to perform
operations to the MicroSCADA Pro process database
• Dual-display video card and two display devices are recommended to enable
more information to be visible at one time
3.1.2. Using the tool

Before opening the tool, start Microsoft Excel and verify that macro security level
is set to "Medium" by selecting Tools>Macro>Security>Security Level.
LBE tool is installed in \sc\sa_lib\tools\LBE.xls. When the document is
opened, click Enable Macros to enable all the functionality built in the sheets. If
you click Disable Macros, the contents will still be visible, but the functionality will
not be available.
The following sheets are included into this tool:
• Create
• Switch
• Measurement
• Alarm
• Transformer
• Bay LR
• Station LR
• Line Indicator
• Generator
25
Application Design
• AR
• Trip
• Symbols
• Mappings
• Data Source
• Defaults
• Clipboard
General notes:
• Keyboard shortcuts CTRL+PAGE UP and CTRL+PAGE DOWN can be used
to quickly move between the sheets.
• Excel's AutoFilter functionality is enabled by default in Symbols, Mappings and
Data Source sheets. To enable AutoFilter in other sheets, select Data>Filter>
AutoFilter.
• LBE uses Excel's data validation functionality in several columns of the sheets. If
a range is copied from column to another, the data validation (and also cell
formatting) in the target range will be overwritten. To prevent this, it is
recommended to use Edit>Paste Special>Values when copying data between
columns.
• Most of the macros and event handlers clear Excel's undo stack, so undo will not
always be available. This applies especially to the event based sheets ie. Symbols,
Mappings and Data Source sheets.
• Column headings and some of the columns of the sheets are read-only. If their
contents are changed, the changes are canceled programmatically by calling
Excel's undo function.
• LBE tool does not use the locking mechanism that for example Display Builder
uses when opening a process display file.
• Adding the graphical objects to busbar coloring topology and building the
topology can be done only in Display Builder.
The following sections describe the functionality of these different sheets in the List
Based Engineering tool.
3.1.3. Create sheet

This sheet is used to specify the naming convention for process objects (contents of
Logical Name attribute) and amounts of each supported process object type per bay.
An example in Chapter Fig. 3.1.3.-1 contains 4 bays (B1, B2, B3 and B4) defined
for one station (S1). Each bay to be engineered contains multiple object types.
26
Application Design
CreateCheet
Fig. 3.1.3.-1 Create sheet
3.1.3.1. Columns
The Create sheet contains columns, which identify used naming convention and
types of objects. The following tables contain the names and purposes for both of
these categories.
• The columns from LN Prefix to LN Suffix are used together with the marker (see
Defaults sheet) to form naming convention for process object logical names. The
name is formed as follows: LN Prefix + Station Name + Station Suffix + Bay
Name + Bay Suffix + Device Prefix + Device Name + LN Suffix. The Device
Name is formed as follows: Device Marker + a running number starting from 1.
27
Application Design
• The columns from Breakers to Tripping Tags contain per-bay amounts of each
supported process object type. Only whole numbers greater than 0 are accepted.
Table 3.1.3.1-1 Naming convention columns

Column Purpose
LN Prefix Prefix of Logical Name
Station Name Station name of Logical Name
Station Suffix Station suffix of Logical Name
Bay Name Bay name of Logical Name
Bay Suffix Bay suffix of Logical Name
Device Prefix Device prefix of Logical Name
LN Suffix Suffix of Logical Name
Table 3.1.3.1-2 Object type columns

Column Purpose
Breakers Amount of breaker objects
Disconnectors Amount of disconnector objects
Measurements Amount of measurement objects
Alarm Symbols Amount of alarm objects
2-W Transformers Amount of 2-winding transformer objects
3-W Transformers Amount of 3-winding transformer objects
Bay LRs Amount of bay local/remote objects
Station LRs Amount of station local/remote objects
Line Indicators Amount of line indicator objects
Generators Amount of generator objects
AR Symbols Amount of auto reclose objects
Tripping Tags Amount of tripping tag objects
3.1.3.2. User interface components

The buttons in this sheet are used to activate the macros that have influence on the
object names in the LIB object sheets. They can also create the process objects in the
MicroSCADA Pro application with the related process display information. All this
is done in an efficient way to increase the productivity of engineering. The following
table contains the button names and functions.
Table 3.1.3.2-1 Buttons in Create sheet

Button Function
Create Names Creates the names for the process objects in LIB object sheets according
to the specified naming convention. This button also creates the process
object type specific attribute names and default values. The default values
can be overridden by entering new name-value-pairs to the Default sheet.
Add Symbols Creates a predefined subdrawing and data variable mappings for each
process object in LIB object sheets and adds them to the active process
display file. The active process display file must contain at least one
MicroSCADA data source. If more than one MicroSCADA data sources
are found, the first one is used.
28
Application Design
Table 3.1.3.2-1 Buttons in Create sheet

Write Data Writes the configuration data files in the MicroSCADA Pro application
based on the information found from the LIB object sheets. The
destination folder for these files is the POBJCONF directory of the
application. In this directory, each file is recognized by the process object
logical name with a .dat extension, for example
\sc\apl\applicationname\POBJCONF\S1_STA1.dat. This button also
creates the process objects in the MicroSCADA Pro process database.
Clear Sheets Clears the contents of all LIB object sheets without prompting for
confirmation
3.1.3.3. Tips for using Create sheet

In the following list, you can find useful tips when using Create sheet buttons during
the LBE engineering.
• It is not mandatory to use the Create Names button; all names and configuration
data can also be entered manually in the LIB object sheets.
• If LIB object sheets are not empty, the new process object information will be
added after the existing information in the sheet.
• Both breakers and disconnectors are created in the Switching Device sheet.
• Both 2-winding transformers and 3-winding transformers are created in the
transformer sheet.
• Bay LR's, Station LR's and Line Indicators do not have Device Name.
• Station LR's do not have Bay Name.
• The rows are processed until a row, where both Station Name and Bay Name are
empty is found.
• The rows of LIB object sheets are processed until a row with empty Process
Object Logical Name is found.
• Each row is processed starting from left to right until an empty value is found.
• If the Symbols sheet is not empty, the new symbol information will be added after
the existing information in the sheet.
• When Add Symbols button creates the subdrawings, their coordinates are set in
such a way that symbols of each bay are piled on top of each other. Bay and
Station LR's are piled above the bay. Bays of the same station are aligned next to
each other, and if process display contains more than one station, they are aligned
one below the other.
• If the breaker and disconnector markers are equal, LBE tool has no possibility to
decide whether to use the breaker or the disconnector subdrawing and the
disconnector is used for both.
• If 2-winding and 3-winding transformer markers are equal, LBE tool has no
possibility to decide whether to use the 2-winding or the 3-winding subdrawing,
and 2-winding is used for both.
3.1.3.4. Exception handling in Create sheet

The following exceptions may occur, when the buttons in the Create sheet are used
during the LBE engineering.
29
Application Design
Creating names
If a connection to MicroSCADA OPC Server cannot be established from LBE tool,
the following message is displayed:
A050247
Fig. 3.1.3.4.-1 Cannot connect to OPC server

LBE tool uses a MicroSCADA command procedure named BGU_CREATEDB. If
it cannot be created, the following message is displayed:
A050211
Fig. 3.1.3.4.-2 Cannot create command procedure

If the attribute names and default values cannot be fetched from MicroSCADA, the
following message is displayed:
A050212
Fig. 3.1.3.4.-3 Cannot get attributes

If the object type specific CONFIG_DATA_FILE, which is specified in the Default
sheet, is not recognized as a SA-LIB file, the following message is displayed:
A050213
Fig. 3.1.3.4.-4 Config data file is not recognized as a SA-LIB file
30
Application Design
If Station is specified, but Bay is empty or vice versa, the following message is
displayed:
A050248
Fig. 3.1.3.4.-5 No bay designation
Writing data
If the directory path corresponding to the current application name, which is
specified in Defaults sheet, cannot be found, the following message is displayed:
A050214
Fig. 3.1.3.4.-6 Cannot find application path

If writing to a configuration data file is not possible from LBE tool, the following
message, where S1_STA1.dat is the name of the configuration file, is displayed:
A050242
Fig. 3.1.3.4.-7 Cannot write file

If the process object creation fails in the MicroSCADA Pro process database, the
31
Application Design
A050215
Fig. 3.1.3.4.-8 Cannot create process object

If one or more SCIL error status codes are received by LBE as a result of the process
object creation in the MicroSCADA Pro process database, the following message is
displayed:
A050216
Fig. 3.1.3.4.-9 Errors when creating process object

Creating the object may have totally or partially failed because of the error.
Adding Symbols
If the active process display file contains no MicroSCADA data sources, the
A050217
Fig. 3.1.3.4.-10 Cannot add symbols
3.1.4. Symbols, Mappings and Data Source sheets

These three sheets are used for list based editing of process displays. The sheets are
event based, which means that all changes in cell contents take effect immediately
in the loaded process display. If no process display is loaded, LBE uses the template
display file specified in Defaults sheet, and the changes are applied to it.
32
Application Design
3.1.4.1. Columns
Symbols sheet
The columns of Symbols sheet have the following purposes:
• Object # contains the number of the graphical object. The column is read-only.
• Subdrawing File contains the file name of the used subdrawing. Entering a valid
file name to an empty cell creates a new graphical object (and also writes initial
default values to the editable attribute cells of the row, if they are not already
specified). Entering a valid file name to a non-empty cell changes the used
subdrawing file. Deleting cell contents, or entering an empty string, deletes the
graphical object (but not the values of the editable attribute cells of the row).
• Object Name contains the name of the graphical object. It is not recommended to
have several graphical objects with equal object name in one process display.
• ToolTip contains the text that is displayed as a tooltip for the graphical object.
• Visibility Priority contains the visibility priority level of the graphical object.
Valid values can be seen and changed from the data validation in-cell dropdown.
• X Coord and Y Coord columns contain the coordinates of the graphical object.
Only whole numbers between -16 383 and 16 383 are accepted.
• X Scale and Y Scale columns contain the scale factors of the subdrawing. Only
decimal numbers between -16 383 and 16 383 are accepted.
• SA Object Type contains the value of SAObjectType custom attribute key of the
subdrawing. The column is read-only.
• SA Object Name contains the value of SAObjectName custom attribute key of
the graphical object. The column is read-only.
• Message column contains the result and time of the last operation related to the
subdrawing file. The column is read-only.
Mappings sheet
The columns of Mappings sheet have the following purposes:
• Object # contains the number of the graphical object. The column is read-only.
• Object Name contains the name of the graphical object. The column is read-only.
• Subdrawing Data Var Name contains the name of the subdrawing data variable.
The column is read-only.
• Data Var Type contains the data type of the subdrawing data variable. The same
type is required for the mapped display data variable or constant value. The
column is read-only.
• Data Source # contains the number of the data source that contains the mapped
display data variable. The column is read-only.
• Data Var # contains the number of the mapped display data variable. The column
is read-only.
• Data Source Name contains the name of the data source that contains the mapped
display data variable. Entering a valid data source name to an empty cell enables
the user to enter also a display data variable name. If more than one data sources
are found with equal name, the first one will be used. Entering a valid data source
33
Application Design
name to non-empty cell removes an existing data variable mapping. Deleting cell
contents, or entering an empty string, deletes an existing data variable mapping.
• Display Data Var Name contains the name of the mapped display data variable.
Before entering a data variable name, data source name must always be specified
first. Entering a valid data variable name to an empty cell maps the subdrawing
data variable to the display data variable (and deletes existing constant mapping).
If more than one data variables are found with equal name, the first one will be
used. Entering a valid data variable name to non-empty cell changes the data
variable mapping. Deleting cell contents, or entering an empty string, deletes an
existing data variable mapping (but leaves the data source name as is).
• Constant Value contains the value of the mapped constant. Entering a valid value
to a cell maps the subdrawing data variable to the constant (and deletes existing
data variable mapping). Entering a valid value to non-empty cell changes the
constant mapping. Deleting cell contents, or entering an empty string, deletes an
existing constant mapping.
• Message column contains the result and time of the last mapping operation. The
column is read-only.
Data Source sheet

The columns of Data Source sheet have the following purposes:
• Data Var # contains the number of the data variable. The column is read-only.
• Data Var Name contains the name of the data variable. Entering a non-empty
string to an empty cell creates a new data variable. Entering a non-empty string to
a non-empty cell renames the data variable. Deleting cell contents, or entering an
empty string, deletes the data variable (but not the values of the editable attribute
cells of the row). It is not recommended to have several data variables with equal
name in one data source.
• Data Var Type contains the type of the data variable. The valid types can be seen
and changed from the data validation in-cell dropdown. If text type is selected,
length of the data variable is set to 16 characters.
• Public indicates the scope of the data variable. If the scope is public, the cell
contains "x". If the scope is private, the cell is empty. Setting the scope to public
is done by entering any non-empty string to the cell, and setting the scope to
private is done by deleting the cell contents or entering an empty string.
• MicroSCADA Object Reference contains the process object logical name + ":P"
(+ possible attribute name) + index. The column applies only to MicroSCADA
data sources.
• MicroSCADA Variable Type contains the type of the MicroSCADA variable.
The valid types can be seen and changed from the data validation in-cell
dropdown. The column applies only to MicroSCADA data sources.
• "Swap Values 0 and 1" and "Swap Values 1 and 2" columns contain the value
swapping information for state indication variables. Enabled swapping type is
indicated with "x". Entering any non-empty string to the cell enables the
swapping type. Deleting cell contents, or entering an empty string, sets the
swapping type to none. Both swapping types cannot be enabled simultaneously
34
Application Design
for one MicroSCADA data variable. The columns apply only to MicroSCADA
data sources.
• OPC Item ID contains the MicroSCADA object reference in complete format ie.
"\\APL\" + application number + "\P\" + process object logical name + "\" +
index (+ ":" + possible attribute name). The column is read-only and applies only
to MicroSCADA data sources.
• Mapping Count contains the sum of subdrawing data variables and other object
dynamics that are mapped to the display data variable. A data variable with one
or more mappings cannot be deleted. The column is read-only.
• Message column contains the result and time of the last operation related to the
data variable name. The column is read-only.
3.1.4.2. User interface components
Symbols sheet
The user interface components of Symbols sheet have the following purposes:
Table 3.1.4.2-1 Buttons in Symbols sheet

Button Function
Open Opens a file selection dialog and reads the contents of the selected
process display file to memory and to Symbols, Mappings and Data
Source sheets. Only the attributes of subdrawing objects are displayed in
Symbols sheet, other graphical object types are ignored (but not deleted
from memory). Previous contents of the sheets are cleared without further
notice.
Save As Opens a file selection dialog and writes the contents of the active process
display to the selected file.
Show Preview Shows the current process display file in a preview window. Right mouse
button enlarges and left mouse button reduces the window size. SHIFT +
any mouse button shows the Zoom Control. If Symbols or Mappings sheet
is active, a rectangle is drawn around the graphical object that is being
edited (the rectangle does is not drawn if multiple rows are selected).
Clear Sheets Clears the contents of Symbols, Mappings and Data Source sheets, and
opens the template display file, without prompting for confirmation.
Mapping sheet
The user interface components of Mappings sheet have following purposes:
Write Object Details to Each Row check box
• Defines whether or not LBE writes object numbers and names to each row. When
this option is not checked, the Mappings sheet is usually more readable, but the
object details are needed in each row sometimes when AutoFilters are applied.
Data Source sheet

The user interface components of Data Source sheet have the following purposes:
Data Source text box, spin button and list box
• Active data source can be changed by entering a valid data source number to the
text box, changing the data source number with the spin button, or selecting the
35
Application Design
data source from the list box. Entering a string to the list box renames the active
data source. It is not recommended to have empty data source names, or several
data sources with equal name in one process display.
Application text box and spin button
• Application number of the data source can be changed by entering a valid number
to the text box or changing the number with the spin button. The controls are
enabled only when a MicroSCADA data source is active.
Blink Period text box and spin button
• Blink period of blinking status colors can be changed by entering a valid
millisecond value to the text box or changing the value with the spin button. The
controls are enabled only when a MicroSCADA data source is active.
3.1.5. Defaults sheet

Defaults sheet contains settings, attribute names and default values that are essential
to the functionality of other sheets, macros and event handlers.
General section of Defaults sheet contains the following settings:
• Number and name of the application where process objects are created to
• OPC Server ProgID
• Path to the root directory of MicroSCADA Pro
Process Display section contains the following settings:
• Path and file name of the process display that is used as a template when the
contents of Symbols, Mappings and Data Source sheets is cleared
• X and Y coordinates of the first symbol of the first bay of the first station in
process display when Add Symbols button is clicked
• Y-offset of symbols in a bay when Add Symbols button is clicked
• X-offset of bays next to each other when Add Symbols button is clicked
• Y-offset of stations, if symbols are created to more than one station when Add
Symbols button is clicked
• Default visibility priority for new graphical objects
• Default X and Y coordinates for new graphical objects
• Default X and Y scale factors for new graphical objects
Default Mappings section contains the following settings that are used when
Add Symbols button is clicked:
• Subdrawing data variable names that are mapped to data variables that are
created to the first MicroSCADA data source of the active process display
• Possible attribute name + index that are used for creating the object reference of
each MicroSCADA data variable
• Variable type of each MicroSCADA data variable
• Swapping type of each MicroSCADA data variable, used only if variable type is
"State Indication"
• Subdrawing data variable names that are mapped to constant values
36
Application Design
• The values for each subdrawing data variable that is specified to be mapped to
constant
LIB Object Attributes and Default Values section contains the following
settings for each supported process object type:
• Marker that is used in device name and process object logical name when Create
Names button is clicked.
• Subdrawing file name that is used when graphical object (symbol) is added to the
Symbols sheet with Add Symbols button.
• Process object attribute names and default values that are copied to LIB object
sheets when Create Names button is clicked
Note the following:
• The attribute names and default values are copied starting from left to right
until an empty cell occurs.
• Both breakers and disconnectors are created in the Switching Device sheet and
therefore they have common attribute names.
• Both 2-winding and 3-winding transformers are created in the Transformer
sheet, so they have common attribute names.
3.1.6. Clipboard sheet

This sheet is not used by LBE tool macros at all. It can be used freely as a workspace
and for storing cell contents copied or cut from other sheets. By default, its first
column contains the file names of all SA symbols, so that they can be copied and
pasted instead of manually typing to Subdrawing File column in the Symbols sheet
and in the Defaults sheet.
3.2. Object Navigator engineering

The function of an application is to fulfil the requirements to monitor and control the
process devices related to certain application area. The application area may be an
electricity distribution, a heat distribution or an other related application.
The application requires its own connections to the process equipment in the form
of system and application objects. System objects describe how the system is
configured. Application objects are more related to the signal flow, when indications
are received in the application database or process devices, which are controlled in
the application. For more information, refer to the Application Objects and System
Objects manuals.
3.2.1. Installing standard functions

Object Navigator is capable to create application objects or standard functions. In
the case of standard functions, a set of application objects is created during the
standard function installation. Object Navigator can be used for the objects’
application engineering with regard to the following operations: add, delete, modify,
export, import or document.
37
Application Design
The functionality of the Object Navigator to create and engineer certain types of
application objects is described more detailed in the Application Objects manual.
The following section describes how Object Navigator can be used for creating and
engineering the standard functions.
3.2.1.1. Standard Functions of LIB 5xx and SA-LIB

The Substation Automation Library (SA-LIB) is included in MicroSCADA Pro.
This library contains the most generic Substation Automation library functions.
These functions can be used during the application engineering to model the
application related process. Each standard function contains a set of configurable
attributes, which specify how the signal flow is passed between the process devices
and the application database.
The following application process related standard functions are included in the SA-
LIB:
• Station
• Bay
• Switching Device
• Tap Changer
• Measurement
• Alarm Indicator
• Auto Reclose
• Trip Signal
• Generator
• Indicator
If the MicroSCADA Pro system also contains Standard Application Library LIB 5xx
products, they are included in the list of standard functions as well.
For more information on the symbols, refer to Chapter 4.
3.2.1.2. Installation and configuration of standard functions

In the Object Navigator, installing of standard functions is possible when Object >
Install Standard Function is selected from the menu bar. The Install Standard
Function dialog is then opened, see Chapter Fig. 3.2.1.2.-1.
38
Application Design
A050245
Fig. 3.2.1.2.-1 Install Standard Function

Expand the SA_LIB Process node, select a standard function, then click Install or
press Enter. The Standard Function Tool is now opened, see Chapter Fig. 3.2.1.2.-2.
A050246
Fig. 3.2.1.2.-2 Standard Function Tool
39
Application Design
In Standard Function Tool, the standard function related configurable attributes are
displayed. When Standard Function Tool is opened, the default values are assigned
in the attribute list. During the application engineering, these attributes are
engineered to the values required by the application in question. When Apply is
clicked, the configuration file for these attributes is created. When this is done, the
Apply button is dimmed. The next step is to start the Process Object Tool from the
Tools tab. This can be done either by double-clicking the Process Object Tool in the
list or selecting the Process Object Tool and clicking Open. When this is done, the
Process Object Tool is opened, see Chapter Fig. 3.2.1.2.-3.
Process Object Tool
Fig. 3.2.1.2.-3 Process Object Tool

In the Process Object Tool, there are three tabs:
• New
• Existing
• Other
On the New tab, the standard function related process objects can be created one by
one or in small groups with the Create button located on the bottom row of the tool.
The Create All button creates all the process objects on the New tab. After the
process objects have been created, they appear on the Existing tab.
The Existing tab of the Process Object Tool includes functionality to directly edit
the process object attribute values usually modified in the Process Object Form of
Object Navigator. The editable process object attributes are:
IU = In Use
SS = Switch State
40
Application Design
UN = Unit Number
OA = Object Address
OB = Object Bit Address
The OA and OB attributes are displayed and handled as process object type
dependent encoded values, like in the Process Object Form of Object Navigator,
thus they are not necessarily the same values as stored in the SYS 600 process
database. The titles for OA and OB fields are surrounded with brackets to indicate
this encoding and slight address naming inaccuracy. Both the OA and OB attributes
are displayed as decimal numbers, ignoring the Output Type attribute definition.
A separate edit area (bottom of the Existing tab) is used for editing purposes in this
tab. Read-only columns for the attributes are also shown in the process object list of
the Existing tab.
When a existing process object is selected in the Process Object Tool, the current
attribute values for IU, SS, UN, OA and OB are displayed in the edit area together
with their corresponding dialog items. When multiple process objects are selected,
the attribute values of the first selected object are shown in edit area, and if an
attribute value is modified, this has effect on the attribute value for all the selected
process objects.
However, if multiple process objects are selected, then the OA and OB attribute
fields are disabled; the UN attribute is the only address attribute, which can be
changed alone. If the OA or OB attribute is changed, all the three/two address
attributes must be defined before applying the change. If all address attributes UN,
OA and OB have their initial values (UN=0, OA=0 and OB=16), they are shown as
empty fields.
The change in IU or SS attribute value is executed immediately after modifying the
value of the edit control, except for multiple selected objects. After this, a
confirmation prompt appears. The UN, OA and OB attribute changes are executed
only after the user clicks the Enter button, on the right hand-side of the attribute edit
areas, or after the user presses the Enter key on the keyboard.
The Other tab shows indexes that are not recognized by a standard function. This
happens when the user creates new indexes for an existing process object group in
the Object Navigator. For more information on the Object Navigator, refer to the
Application Objects manual.
3.2.1.3. Connecting standard function to existing process objects

A standard function can be connected to the process objects of the running
application. In the Attributes tab of the Standard Function Tool, the name of the
Process Object Group should be typed in the P_OBJECT_LN field.
This feature is normally used when connecting several standard functions of the
same type to the same Process Objects. Select the Tools tab of the Standard Function
Tool, then select the Existing tab of the Process Object Tool. Existing process
objects are listed and the Connect All button is enabled. Click Connect All and then
Close.
41
Application Design
3.2.2. Connecting standard functions to display

The Object Browser can be used for creating display symbols based on existing
process objects in the MicroSCADA Pro process database. The browser contains the
insertable objects structured in tree view. Object Browser is opened by selecting the
command Object Browser in the Actions menu of Display Builder.
A040053
Fig. 3.2.2.-1 View of the Object Browser

Object Browser is able to display symbols from all the applications. An application
can be selected from the drop-down list in the upper part of the dialog. Select an
application from the list and click the Select button to update the view.
The symbols can be inserted in the display by dragging them to the drawing area.
Station and bay symbols are dragged from the corresponding node. As an example,
dragging an “Incoming 110kV” object in Chapter Fig. 3.2.2.-1 creates a bay symbol
in the display. Dragging an Eastwick object creates a station symbol.
The Object Browser contains only those objects that have a process
database connection. Symbols that do not have a process connection
can also be used in single-line diagrams. They can be inserted from
the Palette window.
42
Application Design
3.3. Connectivity package support

With SCL import function you can import new objects with configurations from an
existing scl file. This function can be used with IEC 61850 Protocol. The SCL
Importer tool is opened from the Tool Manager’s Application Objects tab.
Using SCL Importer

1. Open the tool from the Tool Manager by clicking its icon.
Fig. 3.3.-1 SCL Importer icon
A050017
Fig. 3.3.-2 SCL Import dialog
2. In the SCL Import dialog, browse the scl file you want to import, see
Chapter Fig. 3.3.-2.
3. Select the application and language from the drop-down list if needed.
4. Click Import.
43
Application Design
5. You can see the created process objects and their indexes by clicking the View
Log, which activates after importing.
A050018
Fig. 3.3.-3 Viewing Log File
3.4. Using Input Objects

Input Object is an object responding to the user’s action, for example a mouse click.
It writes data to the MicroSCADA process database and can have several
appearances, such as a button or a slider.
When the data is written from the Input Object to the process database, it is done in
two phases, which are always required in order to write data to the process database:
1. First, the Input Object sets the data variable to a certain value, for example,
when the mouse moves above the Input Object slider. The data variable value is
changed accordingly, but the value is not yet written to the process database.
You can define the data variable for the set operation by selecting the data
variable in the Input Object Properties dialog.
2. The data variable is written to the data source (MicroSCADA OPC server). This
happens when the user clicks on the object. You can define the data variable for
writing in the Input Object Properties dialog’s Rules tab, see Chapter Fig. 3.4.-4.
There are two ways to create an Input Object and connect it to the process database:
• You can set a data variable to a certain value and write the value to a data
source in the same object, as described in the example below.
• You can also do it in separate objects. For example, there can be two buttons;
the first button sets a variable1 to value x, and the other button writes the value
of variable1 (x) to the variable2.
Creating an Input Object and connecting it to process database:

1. Click the Input Object icon on the Objects toolbar of Display Builder, see
Chapter Fig. 3.4.-1.
Fig. 3.4.-1 Input Object button
44
Application Design
2. Select the location for the Input Object by dragging a rectangle on the drawing
area. Now you can see the Input Object on the drawing area, see Chapter Fig.
3.4.-2.
Fig. 3.4.-2 Input Object on the drawing area

3. Right-click the Input Object and select Input Object Properties to open the
Input Object Properties dialog. The data variable that is mapped to the object is
displayed in the Variables list box, see Chapter Fig. 3.4.-3.
A050179
Fig. 3.4.-3 Mapped data variable

4. To change the mapped data variable, click the Change button and select the data
variable.
5. Click OK.
6. Right-click the Input Object and select Properties.
7. Click the Create a new rule button on the Rules tab, see Chapter Fig. 3.4.-4.
45
Application Design
A050177
Fig. 3.4.-4 Rules tab of the Input Object dialog

8. Select Write Data Var to Data Var from the drop-down list in the Action
column to open the Data selection for the Writable Vars dialog.
9. Select the data varible you want to write to. You can select the same variable
that was defined in the Input Object Properties dialog.
10.The Data selection dialog is displayed. Select the variable from where the data
is read in this dialog. This can be the same data variable that was used as the
target data variable.
As default, Input Object is shown as a slider. To change its layout, right-click the
Input Object and select the Types tab in the Input Object Properties dialog and select
another layout.
The different types of Input Objects may require a different count of

mapped data variables.
46
Application Design
4. Standard functions of SA-LIB
4.1. Preliminary work

Before the configuration of the standard functions can start, some preparatory
configurations are required (that is, configurations that are required only once). The
usage of the object identification (OI) attribute has to be settled, the naming
convention of the process object has to be decided and the translation of the signal
texts into the local language has to be performed.
Some of the symbols in this chapter have different presentations, for

example the vertical and horizontal presentation. For more
information on the different presentations, refer to the Process
Display Design manual.
4.2. Communication support

The following protocols are supported in SA-LIB:
• SPA
• ANSI
• LON
• RP-570
• RP-570 with FTABs
• IEC 60870-5-101
• IEC 60870-5-103
• IEC 61850-8
• DNP 3.0
• MODBUS RTU
• PROCOL
4.3. Station
4.3.1. Standard function installation

This chapter describes the installation of station standard function from the SA-LIB.
The standard function for the station is found in the directory /SA_LIB/BASE/
BBONE/INST and it should be installed by using the SA-LIB installation
procedures (SA_LIB/Process/Station). This standard function is configured by
using configuration tools such as:
1. Object Navigator
2. List-Based Engineering Tool
4.3.1.1. Symbol installation

The SA symbol for station standard function is installed by using Display Builder
functions:
47
Application Design
1. LIB 5xx Object Browser

2. Palette
For more information, please refer to the Process Display Design manual.
Table 4.3.1.1-1 SA symbol for station standard function

File name Symbol
Station.sd
4.3.2. Standard function configuration
4.3.2.1. Configuration with a tool

The station standard function has the following attributes to be configured with the
Standard Function Tool:
Table 4.3.2.1-1 Configurable attributes

Attribute Meaning Default
STATION_NAME Name of the substation -
P_OBJECT_LN Logical name of database process objects -
STATION_TYPE The type of control device & protocol LON
CMD_PARAMETER The type of control command for IEC 60870-5- N/A
101 or DNP 3.0 protocol
OUTPUT_STATUS Process objects for output status with DNP 3.0 N/A
protocol
AUTHORIZATION_ The name of the authorization group MV_CONTROL
GROUP
STATION_LR_IN_USE Station local/remote switch used for control Yes
authority checking
IND_DOUBLE_BINARY Indication type double binary/single binary Double binary
LR_REMOTELY_ Station local/remote switch remotely Yes
CONTROLLABLE controllable/ manually operated
EVENT_RECORDING Process objects for event recording with RP-570 No process
objects
OPC_ITEM_PREFIX Specifies the OPC Item Prefix used as an IEC “IEC61850
61850 instance information Subnetwork.IE
D1.LD1"
OPC_LN_INSTANCES Specifies the OPC Logical Node names used as VECTOR("LLN
IEC 61850 instance information 0")
For more detailed description on the configurable attributes, see Section 4.13.
Configuration with the Process Object Tool

Depending on the configuration of the station standard function, the Process Object
Tool creates a certain set of the process objects into the database. Those process
objects which are going be linked to the actual process should be edited to have a
station number, an address and a proper switching state. Otherwise, by default, all
other attributes should have suitable values for normal operation.
48
Application Design
The Process Object Tool creates process objects based on the following list:
Table 4.3.2.1-2 Process objects created by the Process Object Tool

Index Explanation Purpose
10 Station local/remote switch The station local/remote switch is used to
indication determine whether the control to the station objects
is allowed from the panel (local), from the
substation control system, from the remote control
system or station authority checking is out of use.
11 Station local/remote switch to The station local/remote switch to Local-command
Local-command or Station/ object is an output object which is designed to set
Remote command the station control to local (panel) when the
attribute IND_DOUBLE_BINARY is checked.
If IND_DOUBLE_BINARY is not checked, output
object is used for setting the switch either to Station
or Remote.
12 Station local/remote switch to The station local/remote switch to Station-
Station-command command object is an output object, which is
designed to set the station control to substation
control system (station).
13 Station local/remote switch to The station local/remote switch to Remote-
Remote-command command object is an output object, which is
designed to set the station control to network
control system (remote).
14 Station local/remote switch to The station local/remote switch to Out of use-
Out of use-command command object is an output object, which is
designed to set the station authority checking out
of use.
15 Station blockings The indication for station blockings is an internal
object, which is meant for generating events and
(optional) printouts of the station blockings.
16 Station selected on monitor The indication for station selected on monitor is an
internal object and it is used to inform other users
(optional) that the station dialog has been opened by another
user(s).
110 Station local/remote-switch Created only for ANSI and RTU type stations. For
indication ANSI it is used for converting the indication from
analog value to double binary value. For RTU it is
used as an event recording object.
111-114 Indication for command Indicates with IEC 60870-5-101 and -103 whether
termination the issued command was successful or not.
(optional)
49
Application Design
4.3.2.2. Example of a station configuration

Table 4.3.2.2-1 Example of a station standard function configuration
Attribute Value
STATION_NAME Eastwick
P_OBJECT_LN EST
STATION_TYPE LON
AUTHORIZATION_GROUP MV_CONTROL
STATION_LR_IN_USE Yes
IND_DOUBLE_BINARY Yes
LR_REMOTELY_CONTROLLABLE No
EVENT_RECORDING N/A
4.3.3. Application engineering information
4.3.3.1. Structure of the station standard function

This section describes the structure of the station standard function. All sub-drawing
files form pictures, help and other text files as well as database objects are included.
The station is a part of the standard functions of SA-LIB and has the directory
/SA_LIB/BASE/BBONE and the standard SA-LIB subdirectories INST, LANG0
and USE.
4.3.3.2. Files
Below is the list of all the station standard function related files and their
functionality.
Table 4.3.3.2-1 Station standard function related files

File Functionality Path
Station.sd SA symbol for station standard /PROG/GRAPHICSENGINE/
function PALETTE/04-SA_Indication
FORM5SAGR1.PIC Generic format picture for printing /SA_LIB/BASE/BBONE/USE
4.3.3.3. Language text file

The following Text Translation Tool compatible text files are used by the station
standard function. The path is /SA_LIB/BASE/BBONE/LANG0.
Table 4.3.3.3-1 Text Translation Tool compatible text files

File Functionality
SAI_STA2.TXT Text file for the database creation of the standard function
4.3.3.4. Help text file

The path to the station help text file is /SA_LIB/BASE/BBONE/LANG0.
Table 4.3.3.4-1 Station help text file

File Functionality
SAI_STA2.HLP Standard function installation help file
50
Application Design
4.3.3.5. Configuration files

The following configuration files are used by the station standard function. The path
is /SA_LIB/BASE/BBONE/INST.
Table 4.3.3.5-1 Configuration files used by the station standard function

File Functionality
SAI_STA2.DAT Contains the configuration data for station when it is created, modified or
deleted by the configuration tools
SAI_STA2.POT Contains the process object definitions for the Process Object Tool and
the List-Based Engineering Tool
SAI_DAU.TXT Contains the list of data acquisition units
INDEX5_B1.TXT Selection list of SA-LIB standard functions for the installation tool
4.3.3.6. Other text files

The following text file is used by the station. The path is /SA_LIB/BASE/BBONE/
USE.
Table 4.3.3.6-1 Another text file used by the station

File Functionality
BGU_AUTH.TXT Contains the SCIL code for the station authority check. The code is
executed by the dialog for the station.
4.3.3.7. Process objects

The following process objects are created depending on the configuration of the
station.
Table 4.3.3.7-1 Process objects created by manually operated station local/remote switch
Index Obj. type Process object Remarks Group identifier
10 DB/BI Station local/remote switch ind. - FPASTAILRS
15 AI Blockings Internal FPASTAXBLK
Optional
16 AI Station selected on monitor Internal FPASTAXMEV
Optional
110 EVREC Station local/remote switch ind. RP-570 only FPASTAELRS
Optional
110 AI Station local/remote switch ind. ANSI only FPASTAELRS
Table 4.3.3.7-2 Process objects created by remotely controllable station local/remote switch
10 DB/BI Station local/remote switch ind. - FPASTAILRS
11 BO L/R-sw. to Local -command or Station Remote command - FPASTACLRS
12 BO L/R-sw. to Station -command - FPASTACLRS
13 BO L/R-sw. to Remote -command - FPASTACLRS
14 BO L/R-sw. to Out of use -command - FPASTACLRS
15 AI Blockings Internal FPASTAXBLK
Optional
16 AI Station selected on monitor Internal FPASTAXMEV
Optional
51
Application Design
Table 4.3.3.7-2 Process objects created by remotely controllable station local/remote switch
110 EVREC Station local/remote switch ind. RP-570 only. FPASTAELRS
Optional
110 AI Station local/remote switch ind. ANSI only FPASTAELRS
111-114 TERM Command termination indication for output signals IEC 60870- FPASTATOBC
5-101 and -
103 only.
Optional
4.3.3.8. Scale objects

At the first installation the station creates the scale 1_1 (linear 1:1 scale). For
SPACOM / SRIO (ANSI) type of station, the installation will also create the scale
FPU_1_1000 (linear 1:1000 scale).
4.3.3.9. Command procedures

At the first installation, the station creates the command procedure BGU_UPDATE,
which updates process objects when they are update-deblocked. This feature is
similar to the SYS 600 Blocking List function. It is also used by the Update process
data dialog.
For SPACOM / SRIO (ANSI) type of station, the installation creates the command
procedure BGU_AI2DB, which updates the station level local/remote switch
indication double binary from an analog input.
4.3.3.10. Event channels

For SPACOM / SRIO (ANSI) type of station, the installation creates the event
channel BGU_AI2DB, which is set to activate the command procedure
BGU_AI2DB.
4.4. Bay

This section describes the installation of the bay standard function in SA-LIB. The
standard function for the bay is found in the directory /SA_LIB/BASE/BBONE/
INST and it should be installed by using the SA-LIB installation procedures
(SA_LIB/Process/Bay). This standard function is configured by using configuration
tools such as:
1. Object Navigator

The SA symbol for the bay standard function is installed by using the Display
Builder functions:
2. Palette
52
Application Design
For more information, please refer to the SYS 600 Process Display Design manual.
Table 4.4.1.1-1 Bay Switch Indication

File name Symbol
Bay.sd
4.4.2.1. Configuration with tools

The bay standard function has the following attributes to be configured with the
Object Navigator or with the List-Based Engineering Tool:

BAY_NAME Name of the bay -
P_OBJECT_LN Logical name of database process -
objects
CMD_PARAMETER Parameter for control method for IEC N/A
60870-5-101 and DNP 3.0 protocol
OUTPUT_STATUS Process objects for output status with N/A
DNP 3.0 protocol
AUTHORIZATION_GROUP The name of the authorization group MV_CONTROL
BAY_LR_IN_USE Physical L/R-switch exists/not Bay L/R-switch exists
available
BAY_LR_POLARITY Polarity of the bay L/R switch L1
IND_DOUBLE_BINARY Indication type double binary/single Double binary
binary
LR_REMOTELY_CONTROLL Bay L/R-switch remotely controllable/ Manually operated
ABLE manually operated
EVENT_RECORDING Process objects for event recording No process objects
with RP-570
OPC_ITEM_PREFIX Specifies the OPC Item Prefix used “IEC61850
as IEC 61850 instance information Subnetwork.IED1
.LD1"
OPC_LN_INSTANCES Specifies the OPC Logical Node VECTOR("LLN0")
names used as IEC 61850 instance
information
4.4.2.2. Configuration of process objects

Depending on the configuration of the bay standard function, the tools create a
certain set of process objects in the database. Those process objects which are going
to be linked to the actual process should be edited to have a station number, an
address and a proper switching state. Otherwise, by default, all other attributes
should have suitable values for normal operation.
53
Application Design
The tools create process objects based on the following list:
Table 4.4.2.2-1 Process objects created for the bay

10 Bay local/remote switch The bay (disabled)/local/remote switch is used to
indication determine whether the control to the bay objects
is completely inhibited, or it is allowed locally or
remotely.
11 Bay local/remote switch to The bay local/remote switch to Disabled -
Disabled -command, or bay command object is an output object which is
local/remote command designed to set the bay control to disabled (no
control locally or remotely).
If IND_DOUBLE_BINARY is not checked and
STATION_TYPE is IEC 61850-8, this output
object is used for setting bay L/R switch either to
local or remote.
12 Bay local/remote switch to The bay local/remote switch to Local -command
Local -command object is an output object, which is designed to set
the bay control to the local (panel).
13 Bay local/remote switch to The bay local/remote switch to Remote -
Remote -command command object is an output object, which is
designed to set the bay control to substation or
network control system (remote).
14 Bay local/remote switch to The bay local/remote switch to Reserved -
Reserved -command command object is an output object, which is
designed to set the bay control to reserved. The
reserved position can be used for special
purposes.
15 External interlocking ON/OFF The external interlocking in use/out of use (HW) -
(HW) -indication ind. is meant as an ON/OFF type of indication for
the hardware switch of the interlocking function.
(optional)
16 External interlocking ON/OFF The external interlocking in use/out of use (SW) -
(SW) -indication ind. is meant as an ON/OFF type of indication for
the software switch of the interlocking function.
(optional)
17 External interlocking ON/OFF The external interlocking in use/out of use -
-command command is an output object, which can be used
to remotely enable/disable interlocking function of
(optional) the field device.
18 Internal interlocking ON/OFF The internal interlocking in use/out of use -

-indication indication is meant as an ON/OFF type of
indication of the internal interlocking functions. By
(optional) disabling internal interlocking, there will not be
any interlocking checking in the control dialogs
during operation.
19 Internal interlocking ON/OFF The internal interlocking in use/out of use -
-command command is an object, which is defined to
internally control the state of the internal
(optional) interlocking in use/out of use -indication.
54
Application Design
Table 4.4.2.2-1 Process objects created for the bay

20 Bay blockings The bay blockings -indication is an internal object,
which is meant for generating events and
(optional) printouts of the bay blockings.
21 Bay selected on monitor The bay selected on monitor -indication is an

internal object and it is used to inform other users
(optional) that the bay dialog has been opened by another
user(s).
110 Bay local/remote switch Created only for ANSI and RTU type stations. For
indication ANSI it is used for converting the indication from
analog value to double binary value. For RTU it is
used as an event recording object.
111-114, Indication for command Indicates with IEC 60870-5-101 and -103 whether
117 termination the issued command was successful or not.
(optional) Output status object with DNP 3.0 type of

stations.
115 External interlocking ON/OFF Event recording object (for accurate time stamp)
(HW) with RTU 2xx/RP-570 type of stations.
(optional)
116 External interlocking ON/OFF Event recording object (for accurate time stamp)
(SW) with RTU 2xx/RP-570 type of stations.
(optional)
4.4.2.3. Example of a bay configuration

Table 4.4.2.3-1 Example configuration of the bay standard function
Attribute Value
BAY_NAME Outgoing HA2
P_OBJECT_LN ESTHA02BAY
STATION_TYPE LON
CMD_PARAMETER N/A
OUTPUT_STATUS N/A
BAY_LR_IN_USE Yes
BAY_LR_POLARITY L1
IND_DOUBLE_BINARY Yes
LR_REMOTELY_CONTROLLABLE No
EVENT_RECORDING N/A
4.4.3.1. Structure of the bay standard function

This section describes the structure of the bay standard function. All sub-drawing
files, form pictures, help and other text files, as well as database objects are included.
The bay is a part of the standard functions of the SA-LIB and has the directory
and USE.
55
Application Design
4.4.3.2. Files
Below there is a list of all bay standard function related files and their functionality..
Table 4.4.3.2-1 Bay standard function related files

Bay.sd SA symbol for the bay standard /PROG/GRAPHICSENGINE/
function PALETTE/04-SA_Indication

The following Text Translation Tool compatible text files are used by the bay

File Functionality
SAI_BAY2.TXT Text file for the database creation of the standard function

The path to the bay help text file is /SA_LIB/BASE/BBONE/LANG0.
Table 4.4.3.4-1 Bay help text file

File Functionality
SAI_BAY2.HLP Standard function installation help file

The following configuration files are used by the bay standard function. The path is
/SA_LIB/BASE/BBONE/INST.
Table 4.4.3.5-1 Configuration files used by the bay standard function

File Functionality
SAI_BAY2.DAT Contains the configuration data for the bay when it is created, modified
or deleted by the configuration tools
SAI_BAY2.POT Contains the process object definitions for the Object Navigator and
the List-Based Engineering Tool
INDEX5_B1.TXT Selection list of SA-LIB standard functions for the installation tool

The following text file is used by the bay. The path is /SA_LIB/BASE/BBONE/
USE.
Table 4.4.3.6-1 Another text file used by the bay

File Functionality
executed by the dialog of the bay.
56
Application Design

At the first installation, the bay creates the command procedure BGU_UPDATE,
similar to the SYS 600 Blocking List function. It is also used by the Update process
data dialog.
Table 4.4.3.7-1 Command procedures used by bay

File Functionality
BGU_CONTROL Performs the actual control operations

The following process objects are created depending on the configuration of the bay.
Table 4.4.3.8-1 Process objects created by manually operated bay local/remote switch
10 DB/BI Bay local/remote switch ind. - FPABAYILRS
15 BI Interl. in use/out of use (SW) Hardware sw. (MFU) FPABAYIINH
Optional
16 BI Interl. in use/out of use (HW) Software sw. (MFU) FPABAYIINH
Optional
17 BO Interl. in use/out of use -cmd Command to MFU FPABAYCINH
Optional
18 BI Interl. in use/out of use Internal FPABAYIINH
Optional
19 BO Interl. in use/out of use -cmd Internal FPABAYCINH
Optional
20 AI Blockings Internal FPABAYXBLK
Optional
21 AI Bay selected on monitor Internal FPABAYXMEV
Optional
110 EVREC Bay local/remote switch ind. RP-570 only FPABAYELRS
Optional
110 AI Bay local/remote switch ind. ANSI only FPABAYELRS
115 EVREC Interl. in use/out of use (SW) RP-570 only FPABAYEINH
Optional
116 EVREC Interl. in use/out of use (HW) RP-570 only FPABAYEINH
Optional
117, TERM Command termination indication for IEC 60870-5-101 and -103 only FPASTATINH
119 output signals Optional
Table 4.4.3.8-2 Process objects created by remotely controllable bay local/remote switch
10 DB/BI Bay local/remote switch ind. - FPABAYILRS
11 BO L/R-sw. to Local -command or Local Remote Local Remote command if FPABAYCLRS
command station type is IEC 61850-8
12 BO L/R-sw. to Local -command - FPABAYCLRS
13 BO L/R-sw. to Remote -command - FPABAYCLRS
14 BO L/R-sw. to Reserved -command Only if ind. type DB FPABAYCLRS
57
Application Design
Table 4.4.3.8-2 Process objects created by remotely controllable bay local/remote switch
15 BI Interl. in use/out of use (HW) Hardware sw. (MFU) FPABAYIINH
Optional
16 BI Interl. in use/out of use (SW) Software sw. (MFU) FPABAYIINH
Optional
17 BO Interl. in use/out of use -cmd Command to MFU FPABAYCINH
Optional
18 BI Interl. in use/out of use -ind. Internal FPABAYIINH
Optional
19 BO Interl. in use/out of use -cmd Internal FPABAYCINH
Optional
20 AI Blockings Internal FPABAYXBLK
Optional
21 AI Bay selected on monitor Internal FPABAYXMEV
Optional
110 EVREC Bay local/remote switch ind. RP-570 only FPABAYELRS
Optional
110 AI Bay local/remote switch ind. ANSI only FPABAYELRS
111-114 TERM/OS Command termination indication for output IEC 60870-5-101 and -103 FPASTATOBC
signals only
Output status object Optional
Output status object when
station type is DNP 3.0,
optional
115 EVREC Interl. in use/out of use (HW) RP-570 only FPABAYEINH
Optional
116 EVREC Interl. in use/out of use (SW)-ind. Only RP-570 only FPABAYEINH
Optional
117, TERM Command termination indication for output IEC 60870-5-101 and -103 FPASTATINH
119 signals only
Optional

At the first installation the bay creates the scale 1_1 (linear 1:1 scale). For
SPACOM/SRIO (ANSI) type of station. The installation also creates the scale
FPU_1_1000 (linear 1:1000 scale).
4.4.3.10. Event channels

For SPACOM/SRIO (ANSI) type of station, the installation creates the event
channel BGU_AI2DB, which is set to activate the command procedure
BGU_AI2DB.
58
Application Design
4.5. Switching device

This section describes the installation of the switching device standard function from
the SA-LIB. The standard function for the switching device is found in the directory
/SA_LIB/BASE/BBONE/INST and it should be installed by using the SA-LIB
installation procedures (SA_LIB/Process/Switching Device). This standard function
is configured by using configuration tools such as:
1. Object Navigator

The SA symbol for the switching device standard function is installed by using the
following Display Builder functions:
2. Palette
For more information, refer to the SYS 600 Process Display Design manual.
Table 4.5.1.1-1 SA Symbol for switching device standard function

File name Representation Symbol
Breaker.sd ANSI
Disconnector.sd ANSI
Truck.sd ANSI, IEC
Breaker.sd IEC
Contactor.sd IEC
Disconnector.sd IEC
Load Breaker.sd IEC
Earth.sd ANSI, IEC
59
Application Design

The switching device standard function has the following attributes to be configured
with the Object Navigator or with the List-Based Engineering Tool:l

DEVICE_NAME Name of the device -
objects
SWITCHING_DEVICE_TYPE Type of switching device Circuit breaker
SWITCHING_DEVICE_ Usage of the selected switching device Circuit breaker
PURPOSE type
SWITCH_SECTION Switch section of the truck or 3-state Truck: first section
switch 3-state switch:
disconnector
STATION_TYPE Type of control device & protocol LON
INDICATION_TYPE Type of position indication process Double binary
object
MOTORIZED Selection of motorized or manually Motorized
operated
CMD_PARAMETER Parameter for control method for IEC N/A
60870-5-101 and DNP 3.0 protocol
CONTROL_TYPE Type of control process object(s) Secured control
with 4 binary
outputs
DNP 3.0 protocol
CONTROL_PULSE_LENGTH Length of control pulse 0
CONTROL_BITS Bits to be used to send a control Empty vector
command
AUTHORIZATION_GROUP Name of the authorization group MV_CONTROL
BAY_LR_POLARITY Polarity of bay L/R switch L1
AUXILIARY_PLUG Selection if the switching device is Stand-alone
mounted in the truck switch
EVENT_RECORDING Process objects for event recording No process
with RP-570 objects
INTERLOCKING_BYPASS Specifies whether the interlocking FALSE
bypass function is used or not
SYNCHROCHECK_BYPASS Specifies whether the synchrocheck FALSE
bypass function is used or not
OPC_ITEM_PREFIX Specifies the OPC Item Prefix used as "IEC61850
IEC 61850 Instance information Subnetwork.IED1.
LD1"
OPC_LN_INSTANCES Specifies the OPC Logical Node VECTOR("CSWI1
names used as IEC 61850 Instance ","CILO1")
information
60
Application Design

QUALIFIERS Qualifier is the value written to the QL Minimum length is
attribute of process object when writing 0 (default) and
the control command. Qualifiers are maximum length 5
given as a vector of integers.

Depending on the configuration of the switching device standard function, the tools
create a certain set of process objects in the database. Those process objects which
are going to be linked to the actual process should be edited to have a station number,
an address and a proper switching state. Otherwise, by default, all other attributes
The tools create process objects based on the following list:.
Table 4.5.2.2-1 Process objects created for switching device

10 Position indication Used for position indication of the switching device state
open/closed/ intermediate/faulty
11 Open select or open Depending on the defined control type it is used for
execute sending Open select or Open execute to the control
unit.
12 Close select or close Depending on the defined control type it is used for
execute sending Close select or Close execute to the control
unit.
13 Execute selected or Depending on the defined control type it is used for
select open/close and sending Execute or Select open/close and Execute/
execute/cancel or Cancel to the control unit.
execute open
14 Cancel command or Used for sending Cancel command or Execute close
execute close command command to the control unit.
15 External control blocking Receives a control blocking signal from the control unit
(optional) and prevents the control actions in the single line
diagram.
16 Open interlocked Receives a control blocking signal for Open command
(optional) from the control unit and prevents the Open command
in the single line diagram.
17 Close interlocked Receives a control blocking signal for Close command
(optional) from the control unit and prevents the Close command
in the single line diagram.
18 Interlocking cause Receives an interlocking cause, that is, an integer value
(optional) that represents a reason for an unsuccessful control
action.
19 Selected on monitor An internal tag that shows if the switching device is
(optional) selected on different picture(s) or monitor(s).
20 Command event An internal or external tag that shows if the switching
(optional) device is right under the command sequence.
21 Auxiliary plug state An internal or external tag to indicate if the switching
(optional) device is fully racked out from the cubicle and therefore,
it should not be shown in the single line diagram.
61
Application Design
Table 4.5.2.2-1 Process objects created for switching device

25 Cancel command Used for sending a Cancel command to the control unit.
(108) Position indication other Receives position indication as a single indication (110),
110 type than double analog input (110) or two single indications (110-open,
indication 108-close)
111-114 Indication for command Indicates with IEC 60870-5-101 and -103 whether the
termination or indication issued command was successful or not.
for output status With DNP 3.0 indicates the status of output object.
(optional)
115 External control blocking Event recording object (for accurate time stamp) with
(optional) RTU 2xx/RP-570 type of stations.
116 Open interlocked Event recording object (for accurate time stamp) with
117 Close interlocked Event recording object (for accurate time stamp) with
120 Command event Event recording object (for accurate time stamp) with
121 Auxiliary plug state Event recording object (for accurate time stamp) with
(208) Position indication other Event recording object (for accurate time stamp) with
210 type than double RTU 2xx/RP-570 type of stations.
indication
4.5.2.3. Example of a switching device configuration

The configuration of a switching device as a circuit breaker can be given as an
example:
Table 4.5.2.3-1 Configuration of the switching device as a circuit breaker

Attribute Value
DEVICE_NAME Q0
P_OBJECT_LN ESTHA02Q0
SWITCHING_DEVICE_TYPE Circuit breaker
SWITCHING_DEVICE_PURPOSE Main busbar circuit breaker
SWITCH_SECTION N/A
STATION_TYPE LON
INDICATION_TYPE Double binary
MOTORIZED Yes
CMD_PARAMETER N/A
CONTROL_TYPE Secured control with 4 binary outputs
OUTPUT_STATUS N/A
CONTROL_PULSE_LENGTH N/A
CONTROL_BITS N/A
BAY_LR_POLARITY L1
AUXILIARY_PLUG No
EVENT_RECORDING N/A
62
Application Design
4.5.3.1. Structure of the switching device standard function

This section describes the structure of the switching device standard function. All
sub-drawing files, form pictures, help and other text files, as well as database objects
are included. The switching device is a part of the standard functions of the SA-LIB
and has the directory
and USE.
4.5.3.2. Files
Below there is a list of all switching device standard function related files and their
functionality.
Table 4.5.3.2-1 Switching device standard function related files
Breaker.sd SA ANSI symbol for breaker /PROG/GRAPHICSENGINE/PALETTE/03 - SA_ANSI
Disconnector.sd SA ANSI symbol for disconnector /PROG/GRAPHICSENGINE/PALETTE/03 - SA_ANSI
Truck.sd SA Common symbol for truck /PROG/GRAPHICSENGINE/PALETTE/01 - SA_Common
Breaker.sd SA IEC symbol for breaker /PROG/GRAPHICSENGINE/PALETTE/02 - SA_IEC
Contactor.sd SA IEC symbol for contactor /PROG/GRAPHICSENGINE/PALETTE/02 - SA_IEC
Disconnector.sd SA IEC symbol for disconnector /PROG/GRAPHICSENGINE/PALETTE/02 - SA_IEC
Load Breaker.sd SA IEC symbol for load breaker /PROG/GRAPHICSENGINE/PALETTE/02 - SA_IEC
Earth.sd SA Common symbol for earth /PROG/GRAPHICSENGINE/PALETTE/01 - SA_Common

The following Text Translation Tool compatible text files are used by the switching
device standard function. The path is /SA_LIB/BASE/BBONE/LANG0.

File Functionality
SAI_SSW.TXT Text file for the database creation of the standard function

The path to the switching device help text file is /SA_LIB/BASE/BBONE/LANG0.
Table 4.5.3.4-1 Switching device help text file

File Functionality
SAI_SSW.HLP Standard function installation help file
63
Application Design

The following configuration files are used by the switching device standard
function. The path is /SA_LIB/BASE/BBONE/INST.
Table 4.5.3.5-1 Configuration files used by the switching device standard

function
File Functionality
SAI_SSW.DAT Contains the configuration data for the switching device when it is
created, modified or deleted by the configuration tools
SAI_SSW.POT Contains the process object definitions for the Object Navigator and the
List-Based Engineering Tool
INDEX5_B1.TXT Selection list of the SA-LIB standard functions for the installation tool

The following text file is used by the switching device. The path is
/SA_LIB/BASE/BBONE/USE.
Table 4.5.3.6-1 Another text file used by the switching device

File Functionality
executed by the dialog of the switching device.

At the first installation, the bay creates the command procedure BGU_UPDATE,
similar to the SYS 600 Blocking List function.
For the indication type of single indication (BI), the installation will create the
command procedure BGU_BI2DB, which updates the position indication double
binary from the binary input.
For the indication type of an analog input (AI), the installation will create the
command procedure BGU_AI2DB, which updates the position indication double
binary from the analog input.
For the indication type of two single indication (2xBI), the installation creates the
command procedures BGU_2BI2DB and BGU_SETDB, which are used to update
the position indication double binary from two binary inputs.
Table 4.5.3.7-1 Command procedures used by the switching device

File Functionality
OBJECT_INFO Get configuration of the standard function
SELECT_ON_MONITOR Set standard function to selected on monitor -state
OPEN_SELECT Perform open select command on standard function.Uses text file /sa_lib/base/bbone/use/
BGU_SW_SEL.TXT
UNSELECT_ON_MONITOR Remove selected on monitor -state from standard function
CLOSE_SELECT Perform close select command on standard function.Uses text file /sa_lib/base/bbone/use/
BGU_SW_SEL.TXT
64
Application Design
Table 4.5.3.7-1 Command procedures used by the switching device

OPEN_EXECUTE Perform open execute command on standard function.Uses text file /sa_lib/base/bbone/use/
BGU_SW_EXE.TXT
CLOSE_EXECUTE Perform close execute command on standard function.Uses text file /sa_lib/base/bbone/
use/BGU_SW_EXE.TXT
CANCEL Perform cancel command on standard function. Uses text file
SEARCH_OBJECTS Search for objects that belong to standard function.
CHECK_AUTHORITY Check if the user is authorized to control the station.
INTERRUPT_AR_SEQUENCE Interrupt running auto-reclosure sequence.
SET_SIMULATION Set simulation state for objects that belong to standard function.
GET_SIMULATION Get simulation state of objects that belong to standard function.
GET_ALARMS Get alarms of standard function
ACKNOWLEDGE_ALARM Acknoledge single alarm of standard function
GET_OFFSETS Get index offsets for indexes that are used for selected on monitor indication, command
event indication and control block setting.
BGU_BLOCK Performs the blocking operations

Function Description
GET_BLOCKING_STATE Get blocking state for objects that belong to the standard function.
SET_BLOCKING_STATE Set blocking state for the objects that belong to the standard function. If standard function is
a bay, applies to all objects that belong to the bay. If standard function is a station, applies to
all objects that belong to the station.

switching device.
Table 4.5.3.8-1 Manually operated circuit breaker, disconnector or earth

switch. The process objects to be created with the tools.
10 DB Position indication FPQxxxIPOS
19 AI Object selected on Optional FPQxxxXMEV
monitor
21 BI Auxiliary plug indication Optional FPQxxxIAUX
108 BI Close position indication Indication type 2xBI FPQxxxEPOS
110 BI or AI Position indication or Ind. type AI, BI or 2xBI FPQxxxEPOS
open position indication
110 EVREC Event recording for Indication type DB FPQxxxEPOS
DB position indication RP-570 only
Optional
121 EVREC Event recording for RP-570 only FPQxxxEAUX
BI auxiliary plug indication Optional
208 EVREC Event recording for close Indication type 2xBI FPQxxxEPOS
BI position indication RP-570 only
Optional
210 EVREC Event recording for Ind. type AI, BI or 2xBI FPQxxxEPOS
BI or AI position indication or RP-570 only
open position indication Optional
65
Application Design
Three characters (xxx) in the group identifier are replaced by other

characters based on the selection made with configurable attributes
SWITCHING_DEVICE_TYPE and
SWITCHING_DEVICE_PURPOSE.
Table 4.5.3.8-2 Motorized circuit breaker, disconnector or earth switch. The

process objects to be created with the tools.
10 DB Position indication FPQxxxIPOS
11 BO Open command or Open Sec. control with FPQxxxCOBC
execute 4xBO, 2xBO or 2xDO
12 BO Close command or Sec. control with FPQxxxCOBC
Close execute 4xBO, 2xBO or 2xDO
13 BO Execute command or Sec. control with FPQxxxCOBC
Open/Close select and 4xBO, or 5xBO
Execute/Cancel
command or Open
execute command
14 BO Cancel command or Sec. control with 4xBO FPQxxxCOBC
close execute command or 5xBO
15 BI/AI External control blocking AI when the selected FPQxxxIBLK
station type is
IEC 61850-8
16 BI External interlock for Optional FPQxxxIINH
open cmd
17 BI External interlock for Optional FPQxxxIINH
close cmd
18 AI External interlocking Optional FPQxxxIINH
cause
19 AI Object selected on Optional FPQxxxXMEV
monitor
20 BI Object command event Optional FPQxxxICEV
21 BI Auxiliary plug indication Optional FPQxxxIAUX
25 BO Cancel command 5xBO FPQxxxCOBC
108 BI Close position indication Indication type 2xBI FPQxxxEPOS
110 BI or AI Position indication or Ind. type AI, BI or 2xBI FPQxxxEPOS
110 EVREC Event recording for Indication type DB FPQxxxEPOS
Optional
111-114 TERM/OS Command termination IEC 60870-5-101 and - FPQxxxTOBC
indication for output 103 only
signals Optional
115 EVREC Event recording for Only RP-570 FPQxxxEBLK
BI external control blocking Optional
116 EVREC Event recording for Only RP-570 FPQxxxEINH

BI external interlock for Optional
open cmd
117 EVREC Event recording for Only RP-570 FPQxxxEINH
close cmd
66
Application Design
Table 4.5.3.8-2 Motorized circuit breaker, disconnector or earth switch. The

process objects to be created with the tools.
120 EVREC Event recording for RP-570 only FPQxxxECEV
BI object command event Optional
121 EVREC Event recording for RP-570 only FPQxxxEAUX
BI auxiliary plug indication Optional
208 EVREC Event recording for close Indication type 2xBI FPQxxxEPOS
Optional
210 EVREC Event recording for Ind. type AI, BI or 2xBI FPQxxxEPOS
BI or AI position indication or RP-570 only Optional
252 AI Calculated interlocking Optional FPQxxxIINH
cause
Three characters (xxx) in the group identifier are replaced by other

characters based on the selection made with configurable attributes
SWITCHING_DEVICE_TYPE and
SWITCHING_DEVICE_PURPOSE.
Table 4.5.3.8-3 Manually operated truck. The process objects to be created

with the tools.
30 DB Position indication FPQT01IPOS
39 AI Object selected on Optional FPQT01XMEV
monitor
128 BI Close position indication Indication type 2xBI FPQT01EPOS
130 BI or AI Position indication or Ind. type AI, BI or 2xBI FPQT01EPOS
130 EVREC Event recording for Indication type DB FPQT01EPOS
Optional
228 EVREC Event recording for close Indication type 2xBI FPQT01EPOS
Optional
230 EVREC Event recording for Ind. type AI, BI or 2xBI FPQT01EPOS
Table 4.5.3.8-4 Motorized truck . The process objects to be created with the
tools.
30 DB Position indication FPQT01IPOS
31 BO Open command or Open Sec. control with FPQT01COBC
32 BO Close command or Sec. control with FPQT01COBC
67
Application Design
Table 4.5.3.8-4 Motorized truck . The process objects to be created with the
tools.
33 BO Execute command or Sec. control with FPQT01COBC
Open/Close select and 4xBO or 5xBO
Execute/Cancel
command or Open
execute command
34 BO Cancel command or Sec. control with 4xBO FPQT01COBC
Close execute command or 5xBO
35 BI/AI External control blocking AI when the selected FPQT01IBLK
station type is
IEC 61850-8
36 BI External interlock for Optional FPQT01IINH
open cmd
37 BI External interlock for Optional FPQT01IINH
close cmd
38 AI External interlocking Optional FPQT01IINH
cause
39 AI Object selected on Optional FPQT01XMEV
monitor
40 BI Object command event Optional FPQT01ICEV
45 BO Cancel command 5xBO FPQT01COBC
128 BI Close position indication Indication type 2xBI FPQT01EPOS
130 BI or AI Position indication or Ind. type AI, BI or 2xBI FPQT01EPOS
130 EVREC Event recording for Indication type DB FPQT01EPOS
Optional
131-134 TERM Command termination IEC 60870-5-101 and FPQxxxTOBC
indication for output -103 only
signals Optional
135 EVREC Event recording for Only RP-570 FPQT01EBLK
136 EVREC Event recording for Only RP-570 FPQT01EINH
open cmd
137 EVREC Event recording for Only RP-570 FPQT01EINH
close cmd
140 EVREC Event recording for RP-570 only FPQT01ECEV
228 EVREC Event recording for close Indication type 2xBI FPQT01EPOS
Optional
230 EVREC Event recording for Ind. type AI, BI or 2xBI FPQT01EPOS
251 AI Calculated interlocking Optional FPQT01IINH
cause
68
Application Design
Table 4.5.3.8-5 Manually operated three-state switch. The process objects

to be created with the tools.
10 DB Position indication Disconnector section FPQ301IPOS
11 DB Position indication Earth switch section FPQ301IPOS
25 AI Object selected on Optional FPQ301XMEV
monitor
108 BI Close position indication Indication type 2xBI FPQ301EPOS
Disconnector section
109 BI Earth position indication Indication type 2xBI FPQ301EPOS
Earth switch section
110 BI or AI Position indication or Ind. type AI, BI or 2xBI FPQ301EPOS
open position indication Disconnector section
free position indication Earth switch section
110 EVREC Event recording for Indication type DB FPQ301EPOS
Optional
Optional
208 EVREC Event recording for Indication type 2xBI FPQ301EPOS
BI close position indication RP-570 only
Optional
209 EVREC Event recording for earth Indication type 2xBI FPQ301EPOS
Optional
210 EVREC Event recording for Ind. type AI, BI or 2xBI FPQ301EPOS
free position indication Optional
Table 4.5.3.8-6 Motorized three-state switch. The process objects to be

created with the tools.
10 DB Position indication Disconnector section FPQ301IPOS
11 DB Position indication Earth switch section FPQ301IPOS
12 BO Open command or Sec. control with FPQ301COBC
Open execute 4xBO, 2xBO or 2xDO
13 BO Close command or Sec. control with FPQ301COBC
14 BO Free command or Free Sec. control with FPQ301COBC
15 BO Earth command or Earth Sec. control with FPQ301COBC
16 BO Execute command or Sec. control with FPQ301COBC
open/close select and 4xBO, BO or AO
execute/ cancel cmd Direct control with BO
17 BO Cancel command or Sec. control with FPQ301COBC
free/earth select and 4xBO, BO or AO
execute/cancel cmd Direct control with BO
69
Application Design

18 BI External control blocking Optional FPQ301IBLK
19 BI External interlock for Optional FPQ301IINH
open cmd
close cmd
free cmd
earth cmd
23 AI External inter-locking Optional FPQ301IINH
cause
24 AI External interlocking Optional FPQ301IINH
cause
25 AI Object selected on Optional FPQ301XMEV
monitor
26 BI Object command event Optional FPQ301ICEV
108 BI Close position indication Indication type 2xBI FPQ301EPOS
109 BI Earth position indication Indication type 2xBI FPQ301EPOS
free position indication
Optional
Optional
112-117 TERM Command termination IEC 60870-5-101 and FPQxxxTOBC
indication for output -103 only
signals Optional
118 EVREC Event recording for RP-570 only FPQ301EBLK
119 EVREC Event recording for RP-570 only FPQ301EINH
open cmd
close cmd
free cmd
earth cmd
126 EVREC Event recording for RP-570 only FPQ301ECEV
BI close position indication RP-570 only
Optional
70
Application Design

BI earth position indication RP-570 only
Optional
free position indication Optional
251 AI Calculated interlocking Optional FPQ301IINH
cause
252 AI Calculated interlocking Optional FPQ301IINH
cause

At the first installation the switching device creates the scale 1_1 (linear 1:1 scale).
For indication type of analog input, the installation will also create the scale
BGU_1_1000 (linear 1:1000 scale).
4.6. Tap changer

This chapter describes the installation of the tap changer standard function from the
SA-LIB. The standard function for the tap changer is found in the directory
installation procedures (SA_LIB/Process/Tap Changer). This standard function is
configured by using configuration tools such as:
1. Object Navigator

The SA symbol for the tap changer standard function is installed by using the
2. Palette
For further information, please refer to the Process Display Design manual.
71
Application Design
Table 4.6.1.1-1 SA symbol for tap changer standard function

File name Representation Symbol
Transformer2w.sd ANSI, IEC
Transformer3w.sd ANSI, IEC

The tap changer standard function has the following attributes to be configured with
the Object Navigator or with the List-Based Engineering Tool:
Table 4.6.2.1-1 Tap changer attributes configured with the tools

MIN_POSITION Minimum position of tap changer 1
MAX_POSITION Minimum position of tap changer 19
P_OBJECT_LN Logical name of database process object -
STATION_TYPE The type of control device & protocol ANSI
CMD_PARAMETER A selector for selecting of control method. N/A
This attribute has meaning only if IEC
60870-5-101 or DNP 3.0 protocol is
selected, otherwise this attribute is
disabled.
DNP 3.0 protocol.
AUTO_MANUAL_IND_TYP The type of the auto/manual signal 01=manual,
E 10=auto (DB)
AUTHORIZATION_GROUP The name of the authorization group MV_CONTROL
TRANSFORMER_TYPE The number of windings 2-winding
OPC_ITEM_PREFIX Specifies the OPC Item Prefix to as IEC "IEC61850
61850 instance information Subnetwork.IED1.
LD1"
OPC_LN_INSTANCES Specifies the OPC Logical Node names VECTOR
used as IEC 61850 Instance information ("ATCC1")
72
Application Design

Depending on the configuration of the tap changer standard function, the tools create
a certain set of process objects into the database. Those process objects which are
going be linked to the actual process should be edited to have a station number, an
When process objects are created, default scales are assigned to the analog input
signals meant to be connected to the process (indices 24,25 and 26).
Table 4.6.2.2-1 Process objects created for tap changer

Index Explanation Purposes
10 Tap position indication Used for indication of the tap changer
position.
11 Tap ch. auto/manual ind. Used for indication of the transformer auto
manual state.
12 Tap ch. single/parallel ind. Used for indication of the transformer single /
parallel state.
13 Tap ch. master/slave ind. Used for sending “close select” command of
the disconnector section to the control unit.
14 Tap ch. manual cmd Used for sending "manual" command to the
control unit.
15 Tap ch. auto cmd Used for sending "auto" command to the
control unit.
16 Tap ch. raise cmd Used for sending "raise" command to the
control unit.
17 Tap ch. lower cmd Used for sending "lower" command to the
control unit.
18 Tap ch. single/parallel cmd Used for sending "single" or “parallel”
command to the control unit.
19 Tap ch. master/slave command Used for sending a "master" or “slave”
command to the control unit.
20 Transformer ext. blocking Used for indication of the transformer
blocking signal.
21 Undervoltage blocking Used for indication of the transformer
undervoltage blocking signal.
22 Overcurrent blocking Used for indication of the transformer
overcurrent blocking signal.
23 Main/second settings ind. Used for indication of the active settings.
24 Voltage Used for indication of the voltage.
25 Ref. voltage ind. Used for indication of the reference voltage.
26 Ref. voltage setpoint Used for sending the reference voltage to the
control unit (Main settings).
27 Ref. voltage setpoint Used for sending the reference voltage to the
control unit (Second settings).
28 Checksum of SGF1 Used for indication of value of switch group
SGF1.
29 Tap changer operation counter In internal use, used for counting the number
of tap changer step changes.
30 Selected on monitor In internal use, tags the selection of the
object made in different pictures or monitors.
249 Transformer routing prim. info For busbar coloring purposes.
73
Application Design
Table 4.6.2.2-1 Process objects created for tap changer

Index Explanation Purposes
250 Transformer predefined color For busbar coloring purposes.
253 Transformer fict. pos. ind. For busbar coloring purposes.
255 Transformer predefined color For busbar coloring purposes.
4.6.2.3. Example of a tap changer configuration

Table 4.6.2.3-1 Example configuration of a tap changer
Attributes Value
BAY_NAME Transformer 1
DEVICE_NAME TR1
MIN_POSIT 1
MAX_POSIT 19
P_OBJECT_LN ESTH03_T1
STATION_TYPE SPA
TRANSFORMER_TYPE 2-winding
4.6.3.1. Structure of the tap changer standard function

This section describes the structure of the tap changer standard function. All sub-
drawing files, form pictures, help and other text files, as well as database objects are
included. The tap changer is a part of the standard functions of SA-LIB and has the
directory /SA_LIB/BASE/BBONE and the standard SA-LIB subdirectories INST,
LANG0 and USE.
4.6.3.2. Files
Below there is a list of all tap changer standard function related files and their
functionality.
Table 4.6.3.2-1 Tap changer standard function related files

Transformer2w.sd SA ANSI symbol for two winding /PROG/GRAPHICSENGINE/
transformer PALETTE/03 - SA_ANSI
Transformer3w.sd SA ANSI symbol for three winding /PROG/GRAPHICSENGINE/
transformer PALETTE/03 - SA_ANSI
Transformer2w.sd SA IEC symbol for two winding /PROG/GRAPHICSENGINE/
transformer PALETTE/03 - SA_IEC
Transformer3w.sd SA IEC symbol for three winding /PROG/GRAPHICSENGINE/
transformer PALETTE/02 - SA_IEC
74
Application Design
4.6.3.3. Language text files

The following Text Translation Tool compatible text files are used by the tap
changer standard function. The path is /SA_LIB/BASE/BBONE/LANG0.
Table 4.6.3.3-1 Text Translation Tool compatible text files used by the tap
changer standard function
File Functionality
SAI_TR2R.TXT Text file for the database creation of the standard function
SAI_TR2S.TXT Text file for the database creation of the standard function
SAI_HVT2.TXT Text file for the database creation of the standard function busbar
coloring
SAI_HVT3.TXT Text file for the database creation of the standard function busbar
coloring

The path to the tap changer help text file is /SA_LIB/BASE/BBONE/LANG0.
Table 4.6.3.4-1 Tap changer help text file

File Functionality
SAI_TR2.HLP Standard function installation help file

The following configuration files are used by the tap changer standard function. The
path is /SA_LIB/BASE/BBONE/INST.
Table 4.6.3.5-1 Configuration files used by the tap changer standard

function
File Functionality
SAI_TRI_2.DAT Contains the configuration data for tap changer when it is created
modified or deleted by configuration tools
SAI_TRI_2.POT Contains the process object definitions for the Object Navigator and
SAI_HVT23.POT Contains the process object busbar coloring definitions for the
Object Navigator and List-Based Engineering Tool
SAI_TRAIDX.TXT Contains the process object busbar coloring definitions for the
Object Navigator and List-Based Engineering Tool
SAI_HVT2.TPL Contains the process object busbar coloring template definitions for
the Object Navigator and List-Based Engineering Tool
SAI_HVT3.TPL Contains the process object busbar coloring template definitions for
the Object Navigator and List-Based Engineering Tool
INDEX5_B1.TXT Selection list of SA-LIB standard functions for installation tool.
75
Application Design
4.6.3.6. Other text file

The following text file is used by the tap changer. The path is /SA_LIB/BASE/
BBONE/USE.
Table 4.6.3.6-1 Text file used by the tap changer

File Functionality
BGU_AUTH.TXT Contains the SCIL code for station authority check. The code is
executed by the dialog of the tap changer.

At the first installation, the tap changer creates the command procedure
BGU_UPDATE, which updates process objects when they are update-deblocked.
This feature is similar to the SYS 600 Blocking List function.
For ANSI type of station, the command procedure BGU_AI2DB will be created
while installing. The command procedure BGU_AI2DB updates the position
indication double binary from the analog input. The command procecure
BGU_TCCO is created for updating the operation counter object.
Table 4.6.3.7-1 Command procedures used by the tap changer

BGU_TRAFO Performs the control operations
AUTOMATIC_SELECT Performs select operation for automatic command on transformer standard function.
Uses text file /SA_LIB/BASE/BBONE/USE/BGU_SW_SEL.TXT
AUTOMATIC_EXECUTE Performs execute operation for automatic command on transformer standard function.
Uses text file /SA_LIB/BASE/BBONE/USE/BGU_SW_EXE.TXT
AUTOMATIC_CANCEL Performs cancel operation for automatic command on transformer standard function.
Uses text file /SA_LIB/BASE/BBONE/USE/BGU_SW_CAN.TXT
LOWER_SELECT Performs select operation for lower command on transformer standard function.
LOWER_EXECUTE Performs execute operation for lower command on transformer standard function.
LOWER_CANCEL Performs cancel operation for lower command on transformer standard function.
MANUAL_SELECT Performs select operation for manual command on transformer standard function.
MANUAL_EXECUTE Performs execute operation for manual command on transformer standard function.
MANUAL_CANCEL Performs cancel operation for manual command on transformer standard function.
PARALLEL_SELECT Performs select operation for parallel command on transformer standard function.
PARALLEL_EXECUTE Performs execute operation for parallel command on transformer standard function.
PARALLEL_CANCEL Performs cancel operation for parallel command on transformer standard function.
RAISE_SELECT Performs select operation for raise command on transformer standard function.
RAISE_EXECUTE Performs execute operation for raise command on transformer standard function.
76
Application Design
Table 4.6.3.7-1 Command procedures used by the tap changer

BGU_TRAFO Performs the control operations
RAISE_CANCEL Performs cancel operation for raise command on transformer standard function.
SINGLE_SELECT Performs select operation for single command on transformer standard function.
SINGLE_EXECUTE Performs execute operation for single command on transformer standard function.
SINGLE_CANCEL Performs cancel operation for single command on transformer standard function.
SELECT_ON_MONITOR Set transformer standard function to selected on monitor -state
UNSELECT_ON_MONITOR Remove selected on monitor -state from transformer standard function
OBJECT_CONF Get object configuration for transformer standard function
GET_STATES Get process object states of transformer standard function
GET_MESSAGES Get object messages of transformer standard function
BGU_BLOCK Performs the blocking operations

GET_BLOCKING_STATE Get blocking state for objects that belong to standard function.
SET_BLOCKING_STATE Set blocking state for objects that belong to standard function. If standard function is bay,
applies to all objects that belong to bay. If standard function is station, applies all objects that
belong to station.

The following process objects will be created depending on the configuration of the
tap changer.
Table 4.6.3.8-1 Process objects for Generic tap changer

Object Meaning of Process
Index Remarks Group identifier
type object
10 AI Tap changer position - FPTAVRIPOS
11 BI/DB Tap changer manual/ - FPTAVRIMAN
auto -ind.
12 BI/DB Tap changer single/ DB with IEC 61850-8 FPTAVRISGL
parallel -ind.
13 BI/AO Tap changer master/ AO with IEC 61850-8 FPTAVRIMST or
slave -ind. or FPTAVRCPOS
Raise/Lower cmd
14 BO Tap changer Manual - FPTAVRCMAN
cmd or
Auto/Manual cmd
15 BO Tap changer Auto cmd - FPTAVRCMAN or
or Parallel select cmd FPTAVRCSGL
16 BO Tap changer Raise cmd - FPTAVRCPOS or
or tap changer Raise/ FPTAVRCSGL
Lower cmd or
Single select cmd
17 BO Tap changer Lower cmd - FPTAVRCPOS or
or Parallel execute cmd FPTAVRCSGL
77
Application Design
Table 4.6.3.8-1 Process objects for Generic tap changer

Object Meaning of Process
Index Remarks Group identifier
type object
18 BO Single execute cmd Only IEC 61850-8 FPTAVRCSGL
19 BO Single/Parallel cancel Only IEC 61850-8 FPTAVRCSGL
cmd
20 BI/AI Tap changer external AI with IEC 61850-8 FPTAVRIBLK
blocking
24 AI Voltage - FPTAVRMVOL
29 AI Tap changer operation - FPTAVRICNR
counter
30 AI Tap changer selected on - FPTAVRXMEV
monitor
Table 4.6.3.8-2 Process objects for busbar coloring purposes
Object
Index Meaning of process object Remarks
type
240 BI Transformer switch1 -
243 BI Transformer switch4 3-winding
246 AI Transformer passive node1 -
247 AI Transformer passive node2 -
248 AI Transformer passive node3 3-winding
250 AI Transformer active color1 -
251 AI Transformer active color2 -
252 AI Transformer active color3 3-winding

At the first installation, the tap changer creates the scale 1_1 (linear 1:1 scale). For
ANSI type of station, the installation creates also the scale BGU_1_1000 (linear
1:1000 scale).
4.7. Measurement

This chapter describes the installation of measurement standard function from the
SA-LIB. The standard function for the measurement is found in the directory
installation procedures (SA_LIB/Process/Measurement). This standard function is
configured by using the configuration tools such as:
1. Object Navigator
78
Application Design

The SA symbol for the measurement standard function is installed by using the
Display Builder functions:
2. Palette
For further information, refer to the SYS Process Display Design manual.
Table 4.7.1.1-1 SA symbols for measurement standard function

File Name Symbol
Bar Graph.sd
Line Graph.sd
Value.sd
Circle.sd
Current Transducer ANSI.sd
Current Transducer IEC.sd
Voltage Transducer ANSI.sd
Voltage Transducer IEC.sd

The measurement standard function has the following attributes to be configured
with the Object Navigator or the List-Based Engineering Tool:
Table 4.7.2.1-1 Configurable measurement picture function attributes

79
Application Design
Table 4.7.2.1-1 Configurable measurement picture function attributes

TYPE_MEAS_’number’ The type of the measurement None
FOLDER_’number_TITL Abbreviation of the measurement -
E
MEAS_’number_DECIM Decimals used for presenting the value 0
ALS
AUTHORIZATION_GRO The name of the authorization group MV_CONTROL
UP
EVENT_RECORDING Process objects for event recording with No process objects
RP-570
OPC_ITEM_PREFIX Specifies the OPC Item Prefix used as IEC "IEC61850
61850 Instance information Subnetwork.IED1
.LD1"
OPC_LN_INSTANCE_1 Specifies the OPC Logical Node names VECTOR("MMXU1")
used as IEC 61850 Instance information for
the measurement type 1

Depending on the measurement standard function configuration, the tools create a
certain set of process objects in the database. Those process objects which are going
to be linked to the actual process should be edited to have a station number, an
Table 4.7.2.2-1 Process objects created for measurement

10 Current L1 Current measurement on phase L1
13 Neutral current I0 Neutral current measurement
14 Directional neutral current Ij Directional neutral current measurement
15 Maximum demand I15min Current measurement of 15 minutes maximum
demand
16 Voltage U12 Phase to phase voltage measurement on
phases L1-L2
80
Application Design

phases L2-L3
phases L3-L1
19 Residual voltage U0 Residual voltage measurement
20 Active power P Active power measurement
21 Reactive power Q Reactive power measurement
22 Apparent power S Apparent power measurement
23 Power factor Cosj Power factor measurement
24 Frequency f Frequency measurement
25 Harmonic distortion Harmonic distortion measurement
26 Temperature Temperature measurement
27-32 User-defined measurement Any analog input (AI) type of user-defined
measurement
33-37 User-defined pulse counter Any pulse counter (PC) type of user-defined
measurement
38 Active energy (kWh) Active energy counter for kWh
39 Active energy (MWh) Active energy counter for MWh
40 Active energy (GWh) Active energy counter for GWh
41 Reversed active energy (kWh) Reversed active energy counter for kWh
42 Reversed active energy (MWh) Reversed active energy counter for MWh
43 Reversed active energy (GWh) Reversed active energy counter for GWh
44 Reactive energy (kvarh) Reactive energy counter for kvarh
45 Reactive energy (Mvarh) Reactive energy counter for Mvarh
46 Reactive energy (Gvarh) Reactive energy counter for Gvarh
47 Reversed reactive energy (kvarh) Reversed reactive energy counter for kvarh
48 Reversed reactive energy (Mvarh) Reversed reactive energy counter for Mvarh
49 Reversed reactive energy (Gvarh) Reversed reactive energy counter for Gvarh
110 Current L1 Event recording object (for accurate time
(optional) stamp) with RTU 2xx/RP-570 type of stations.
113 Neutral current I0 Event recording object (for accurate time
114 Directional neutral current Ij Event recording object (for accurate time
115 Maximum demand I15min Event recording object (for accurate time
116 Voltage U12 Event recording object (for accurate time
119 Residual voltage U0 Event recording object (for accurate time
81
Application Design

120 Active power P Event recording object (for accurate time
121 Reactive power Q Event recording object (for accurate time
122 Apparent power S Event recording object (for accurate time
123 Power factor Cosj Event recording object (for accurate time
124 Frequency f Event recording object (for accurate time
125 Harmonic distortion Event recording object (for accurate time
126 Temperature Event recording object (for accurate time
127- User-defined measurement Event recording object (for accurate time
132 (optional) stamp) with RTU 2xx/RP-570 type of stations.
4.7.2.3. Example of measurement configuration

The configuration of the measurement with a horizontal field can be given as an
example:
Table 4.7.2.3-1 Measurement configuration

Attribute Value
DEVICE_NAME CT
P_OBJECT_LN ESTHA02CT
STATION_TYPE LON
TYPE_MEAS_1 Current L1
FOLDER_1_TITLE IL1
MEAS_1_DECIMALS 0
TYPE_MEAS_2 Active power P
FOLDER_2_TITLE P
MEAS_2_DECIMALS 1
TYPE_MEAS_3 Reactive power Q
FOLDER_3_TITLE Q
MEAS_3_DECIMALS 1
TYPE_MEAS_4 None
FOLDER_4_TITLE N/A
MEAS_4_DECIMALS N/A
EVENT_RECORDING N/A
82
Application Design
4.7.3.1. Structure of the measurement standard function

This section describes the structure of the measurement standard function. All sub-
included. The measurement is a part of the standard functions of SA-LIB and has a
directory /SA_LIB/BASE/BBONE, and the standard SA-LIB subdirectories INST,
LANG0 and USE.
4.7.3.2. Files
Below there is a list of all measurement standard function related files and their
functionality.
Table 4.7.3.2-1 Measurement standard function files

Bar Graph.sd Measurement bar graph /PROG/GRAPHICSENGINE/PALETTE/05
symbol - SA_Measurement
Line Graph.sd Measurement line graph /PROG/GRAPHICSENGINE/PALETTE/05
Value.sd Measurement value /PROG/GRAPHICSENGINE/PALETTE/05
Circle.sd Measurement circle /PROG/GRAPHICSENGINE/PALETTE/05
Current Transducer SA ANSI symbol for /PROG/GRAPHICSENGINE/PALETTE/05
ANSI.sd current transducer - SA_Measurement
Current Transducer SA IEC symbol for current /PROG/GRAPHICSENGINE/PALETTE/05
IEC.sd transducer - SA_Measurement
Voltage Transducer SA ANSI symbol for /PROG/GRAPHICSENGINE/PALETTE/05
ANSI.sd voltage transducer - SA_Measurement
Voltage Transducer SA IEC symbol for /PROG/GRAPHICSENGINE/PALETTE/05
IEC.sd voltage transducer - SA_Measurement
FORM5SAGR1.PIC Generic format picture for /SA_LIB/BASE/BBONE/USE
printing

The following Text Translation Tool compatible text file is used by the
measurement standard function. The path is /SA_LIB/BASE/BBONE/LANG0.
Table 4.7.3.3-1 Language text file

File Functionality
SAI_ME.TXT Text file for the database creation of the standard function

The path to the measurement help text file is /SA_LIB/BASE/BBONE/LANG0.
Table 4.7.3.4-1 Help text file

File Functionality
SAI_ME1.HLP Standard function installation help file
83
Application Design

The following configuration files are used by the measurement standard function.
The path is /SA_LIB/BASE/BBONE/INST.
Table 4.7.3.5-1 Configuration files used by the measurement standard

function
File Functionality
SAI_ME1.DAT Contains the configuration data for measurement when it is
created modified or deleted by configuration tools
SAI_ME1.POT Contains the process object definitions for the Object
Navigator and List-Based Engineering Tool
INDEX5_B1.TXT Selection list of SA-LIB standard functions for installation tool.

The following text file is used by the measurement. The path is /SA_LIB/BASE/
BBONE/USE.
Table 4.7.3.6-1 Text file used by the measurement

File Functionality
BGU_AUTH.TXT Contains the SCIL code for station authority check. The code
is executed by the dialog of the measurement.

At the first installation the measurement creates the command procedure
BGU_UPDATE, which updates process objects when they are update-deblocked.
This feature is similar to the SYS 600 Blocking List function.
Table 4.7.3.7-1 Command procedures used by the measurement

BGU_CONTROL Performs the control operations
OBJECT_INFO Get configuration of the standard function
SELECT_ON_MONITOR Set standard function to selected on monitor -state
OPEN_SELECT Perform open select command on standard function.
Uses text file
/sa_lib/base/bbone/use/BGU_SW_SEL.TXT
UNSELECT_ON_MONITOR Remove selected on monitor -state from standard function
CLOSE_SELECT Perform close select command on standard function.
Uses text file
/sa_lib/base/bbone/use/BGU_SW_SEL.TXT
OPEN_EXECUTE Perform open execute command on standard function.
Uses text file
/sa_lib/base/bbone/use/BGU_SW_EXE.TXT
CLOSE_EXECUTE Perform close execute command on standard function.
Uses text file
/sa_lib/base/bbone/use/BGU_SW_EXE.TXT
CANCEL Perform cancel command on standard function.
Uses text file
/sa_lib/base/bbone/use/BGU_SW_CAN.TXT
SEARCH_OBJECTS Search for objects that belong to standard function.
84
Application Design
Table 4.7.3.7-1 Command procedures used by the measurement

BGU_CONTROL Performs the control operations
CHECK_AUTHORITY Check if the user is authorized to control the station.
INTERRUPT_AR_ Interrupt running auto-reclosure sequence.
SEQUENCE
SET_SIMULATION Set simulation state for objects that belong to standard
function.
GET_SIMULATION Get simulation state of objects that belong to standard
function.
GET_ALARMS Get alarms of standard function
ACKNOWLEDGE_ALARM Acknoledge single alarm of standard function
GET_OFFSETS Get index offsets for indexes that are used for selected on
monitor indication, command event indication and control
block setting.

measurement.
Table 4.7.3.8-1 Measurement process objects

10 AI Current L1 - FPPMEAMCUR
13 AI Neutral current I0 - FPPMEAMNCU
14 AI Directional neutral current Ij - FPPMEAMDNC
15 AI Maximum demand I15min - FPPMEAMMDC
16 AI Voltage U12 - FPPMEAMVOL
19 AI Residual voltage U0 - FPPMEAMRVL
20 AI Active power P - FPPMEAMAPW
21 AI Reactive power Q - FPPMEAMRPW
22 AI Apparent power S - FPPMEAMAPP
23 AI Power factor Cosj - FPPMEAMCOS
24 AI Frequency f - FPPMEAMFRQ
25 AI Harmonic distortion - FPPMEAMHDS
26 AI Temperature - FPPMEAMTMP
27-32 AI User defined measurement - FPPMEAMXXX
33-37 PC User defined pulse counter - FPPMEAMXXX
38 PC Active energy E (kWh) - FPPMEAMAEN
39 PC Active energy E (MWh) - FPPMEAMAEN
40 PC Active energy E (GWh) - FPPMEAMAEN
41 PC Reverse active energy E (kWh) - FPPMEAMAEN
42 PC Reverse active energy E (MWh) - FPPMEAMAEN
43 PC Reverse active energy E (GWh) - FPPMEAMAEN
44 PC Reactive energy E (kvarh) - FPPMEAMREN
45 PC Reactive energy E (Mvarh) - FPPMEAMREN
85
Application Design
Table 4.7.3.8-1 Measurement process objects

46 PC Reactive energy E (Gvarh) - FPPMEAMREN
47 PC Reverse reactive energy E (kvarh) - FPPMEAMREN
48 PC Reverse reactive energy E (Mvarh) - FPPMEAMREN
49 PC Reverse reactive energy E (Gvarh) - FPPMEAMREN
110 EVREC Current L1 Only RP-570; FPPMEAECUR
optional
optional
optional
113 EVREC Neutral current I0 Only RP-570; FPPMEAENCU
optional
114 EVREC Directional neutral current Ij Only RP-570; FPPMEAEDNC
optional
115 EVREC Maximum demand I15min Only RP-570; FPPMEAEMDC
optional
116 EVREC Voltage U12 Only RP-570; FPPMEAEVOL
optional
optional
optional
119 EVREC Residual voltage U0 Only RP-570; FPPMEAERVL
optional
120 EVREC Active power P Only RP-570; FPPMEAEAPW
optional
121 EVREC Reactive power Q Only RP-570; FPPMEAERPW
optional
122 EVREC Apparent power S Only RP-570; FPPMEAEAPP
optional
123 EVREC Power factor Cosj Only RP-570; FPPMEAECOS
optional
124 EVREC Frequency f Only RP-570; FPPMEAEFRQ
optional
125 EVREC Harmonic distortion Only RP-570; FPPMEAEHDS
optional
126 EVREC Temperature Only RP-570; FPPMEAETMP
optional
127-132 EVREC User defined measurement Only RP-570; FPPMEAEXXX
optional

At the first installation, the measurement creates the scale 1_1 (linear 1:1 scale). For
ANSI type of station, the scale BGU_1_1000 (linear 1:1000 scale) is also created at
the installation.
86
Application Design
4.8. Alarm indicator

This chapter describes the installation of alarm indicator standard function from the
SA-LIB. The standard function for the alarm indicator is found in the directory
installation procedures (SA_LIB/Process/Alarm Indicator). This standard function
is configured by using configuration tools such as:
1. Object Navigator

The SA symbol for alarm indicator standard function is installed by using the
2. Palette
For further information, refer to the SYS 600 Process Display Design manual.
Table 4.8.1.1-1 SA symbol for the alarm indicator standard function

File Name Symbol
Alarm A.sd
Alarm Bell.sd
Alarm Led.sd
Alarm Star.sd

The alarm indicator standard function has the following attributes to be configured
Table 4.8.1.2-1 Alarm indication attributes to be configured with the tools

object
87
Application Design
Table 4.8.1.2-1 Alarm indication attributes to be configured with the tools

STATION_TYPE The type of control device & protocol. LON
TYPE_OF_SIGNAL’x’ The type of the input signal. -
SIGNAL’x’_TEXT Identification for signal shown in event Not available
lists, alarm list and so on
ALARMING_STATE_OF_SIG The state of the signal when an alarm Not available
NAL’x’ (warning) is activated.
LINK_SIGNAL’x’_LN The logical name of the process Not available
object to which the signal is linked.
LINK_SIGNAL’x’_IX The index of the process object to Not available
which the signal is linked.
AUTHORIZATION_GROUP The name of the authorization group. MV_CONTROL
EVENT_RECORDING Selection whether the event recording Not available
process objects are created when the
RP-570 protocol is used.

Depending on the configuration of the alarm indicator standard function, the tools
will create a certain set of process objects in the database. Those process objects
which are going to be linked to the actual process should be edited to have a station
number, an address and a proper switching state. Otherwise, by default, all other
attributes should have suitable values for normal operation.
If the value of the attribute TYPE_OF_SIGNAL’nr’ is linked, the process object is
not created by the tools, but the name and the index of the signal is given to the
attributes LINK_SIGNAL’nr’_TO_LN and LINK_SIGNAL’nr’_TO_IX.
Table 4.8.1.3-1 Process objects created for the alarm indicator

10...17 Alarm indication Used for indication of the alarming state of the signal
88
Application Design
4.8.1.4. Example of alarm indicator configuration

Table 4.8.1.4-1 Alarm indicator configuration
Attribute Value
DEVICE_NAME AI
P_OBJECT_LN EST_HA5AI
STATION_TYPE LON
TYPE_OF_SIGNAL1 Binary Input (BI)
SIGNAL1_TEXT SF6 low pressure
ALARMING_STATE_OF_SIGNAL1 (1)
4.8.2.1. Structure of the alarm indicator standard function

This section describes the structure of the alarm indicator standard function. All sub-
included. The alarm indicator is a part of the standard functions of SA-LIB and has
a directory /SA_LIB/BASE/BBONE, and the standard SA-LIB subdirectories
INST, LANG0 and USE.
4.8.2.2. Files
Below there is a list of all alarm indicator standard function related files and their
functionality.
Table 4.8.2.2-1 Alarm indicator standard function related files

Alarm A.sd SA symbol for alarming A /PROG/GRAPHICSENGINE/PALETTE/04
- SA_Indication
Alarm Bell.sd SA symbol for alarming /PROG/GRAPHICSENGINE/PALETTE/04
bell - SA_Indication
Alarm Led.sd SA symbol for alarming /PROG/GRAPHICSENGINE/PALETTE/04
led - SA_Indication
Alarm Star.sd SA symbol for alarming /PROG/GRAPHICSENGINE/PALETTE/04
star - SA_Indication
printing

The following Text Translation Tool compatible text files are used by the alarm
indicator standard function. The path is /SA_LIB/BASE/BBONE/LANG0.
Table 4.8.2.3-1 Text Translation Tool compatible text file used by the alarm
indicator
File Functionality
SAI_AI.TXT Text file for the database creation of the standard function
89
Application Design

The path to the alarm indicator help text file is /SA_LIB/BASE/BBONE/LANG0.
Table 4.8.2.4-1 Alarm indicator help text file

File Functionality
SAI_AI.HLP Standard function installation help file

The following configuration files are used by the alarm indicator standard function.
Table 4.8.2.5-1 Configuration files used by the alarm indicator

File Functionality
SAI_AI.DAT Contains the configuration data for alarm indicator when it is created
SAI_AI.POT Contains the process object definitions for the Object Navigator and
NDEX5_B1.TXT Selection list of SA-LIB standard functions for installation tool.
4.9. Auto Reclose

This chapter describes the installation of Auto Reclose standard function from the
SA-LIB. The standard function for the Auto Reclose is found in the directory /
SA_LIB/BASE/BBONE/INST and it should be installed by using the SA-LIB
installation procedures (SA_LIB/Process/Auto Reclose). This standard function is
configured by using configuration tools such as:
1. Object Navigator

The SA symbol for Auto Reclose standard function is installed by using the Display
Builder functions:
2. Palette
For further information, refer to the SYS 600 Process Display Design manual.
Table 4.9.1.1-1 SA symbol for Auto Reclose standard function

File Name Symbol
Auto-Reclosing.sd
90
Application Design

The Auto Reclose standard function has the following attributes to be configured
Table 4.9.1.2-1 Auto Reclose standard function configurable attributes

P_OBJECT_LN Logical name of database -
process objects
STATION_TYPE The type of control device & LON
protocol
OUTPUT_STATUS Process objects for output status N/A
with DNP 3.0 protocol
AR_WITH_MULTIPLE_CYCLE Select object type to indicate No
S auto-reclosure in progress
SHOW_AR_IN_USE Show tag during auto-reclosure Show tag
SHOW_AR_NOT_IN_USE Show tag also when no auto- Do not show tag
reclosing is in progress
EVENT_RECORDING Process objects for event No process objects
recording with RP-570
LINK_AR_TAG_TO_LN Create link between existing -
auto-reclosing objects from other
LIB 5xx functions
LINK_AR_TAG_TO_MODULE Select type designation of the No linking
auto-reclosing module
OPC_ITEM_PREFIX Specifies the OPC Item Prefix "IEC61850
used as IEC 61850 Instance Subnetwork.IED1.LD1"
information
OPC_LN_INSTANCES Specifies the OPC Logical Node VECTOR("RREC1")
names used as IEC 61850
Instance information

Depending on the configuration of the Auto Reclose standard function, the tools
create a certain set of process objects in the database. The process objects which are
going to be linked to an actual process should be edited to have a station number, an
Table 4.9.1.3-1 Process objects created for Auto Reclose

10 Auto-reclosing in use/out of use Indicates if the auto-reclose is in use
indication (optional) (software switch of the auto-reclosing unit).
11 Auto-reclosing in use/out of use Indicates if the auto-reclose is in use
indication (optional) (hardware switch of the auto-reclosing
unit).
91
Application Design
Table 4.9.1.3-1 Process objects created for Auto Reclose

12 Auto-reclosing in progress/not in Indicates if there is an auto-reclosing
progress ind. (optional) sequence running.
13 Auto-reclosing interrupt command Interrupts the auto-reclosing sequence.
(optional)
14 Auto-reclosing in use/out of use Enables/disables the auto-reclosure.
command (optional)
110 Auto-reclosing in use/out of use Event recording object (for accurate time
indication (optional) stamp) with RTU 2xx/RP-570 type of
stations.
111 Auto-reclosing in use/out of use Event recording object (for accurate time
indication (optional) stamp) with RTU 2xx/RP-570 type of
stations.
112 Auto-reclosing in progress/not in Event recording object (for accurate time
progress ind. (optional) stamp) with RTU 2xx/RP-570 type of
stations.
113 Auto-reclosing interrupt command Command termination object with IEC
(optional) 60870-5-101 and -103 type of stations.
Output status object with DNP 3.0 type of
stations.
114 Auto-reclosing in use/out of use Command termination object with IEC
command (optional) 60870-5-101 and -103 type of stations.
Output status object with DNP 3.0 type of
stations.
4.9.2.1. Structure of the Auto Reclose standard function

This section describes the structure of the Auto Reclose standard function. All sub-
included. The Auto Reclose is a part of the standard functions of SA-LIB and has a
LANG0 and USE.
4.9.2.2. Files
Below there is a list of all Auto Reclose standard function related files and their
functionality.
Table 4.9.2.2-1 Auto Reclose standard function related files

Auto-Reclosing.sd SA symbol for Auto Reclose /PROG/GRAPHICSENGINE/
PALETTE/04 - SA_Indication
printing
92
Application Design

The following Text Translation Tool compatible text files are used by the Auto
Reclose standard function. The path is /SA_LIB/BASE/BBONE/LANG0.
Table 4.9.2.3-1 Text Translation Tool compatible text file used by the Auto
Reclose standard function
File Functionality
SAI_ARC2.TXT Text file for the database creation of the standard function

The path to the Auto Reclose help text file is /SA_LIB/BASE/BBONE/LANG0.
Table 4.9.2.4-1 Auto Reclose help text file

File Functionality
SAI_ARC2.HLP Standard function installation help file

The following configuration files are used by the Auto Reclose standard function.
Table 4.9.2.5-1 Configuration files used by the Auto Reclose stardard

function
File Functionality
SAI_ARC2.DAT Contains the configuration data for the Auto Reclose when it is created,
SAI_ARC2.POT Contains the process object definitions for the Object Navigator and List-
Based Engineering Tool
NDEX5_B1.TXT Selection list of SA-LIB standard functions for installation tool

The following process objects are created for the Auto Reclose standard function.
Table 4.9.2.6-1 Process objects created for the Auto Reclose standard
function
Index Obj. type Process object Remarks Group ident.
10 BI Auto-reclosing in use Software switch FPFARCISCE
Optional
11 BI Auto-reclosing in use Hardware switch FPFARCISCE
Optional
12 BI or AI Auto-reclosing in Optional FPFARCIARC
progress
13 BO Auto-reclosing Optional FPFARCCINR
interruption
14 BO AR in use/ out of use - Optional FPFARCCSCE
cmd
110 EVREC Event recording for Only RP-570 FPFARCESCE
auto-reclosing in use Optional
93
Application Design
Table 4.9.2.6-1 Process objects created for the Auto Reclose standard
function
111 EVREC Event recording for Only RP-570 FPFARCESCE
auto-reclosing in use Optional
112 EVREC Event recording for Only RP-570 FPFARCEARC
auto-reclosing in Optional
progress
113 TERM / OS Command termination Only IEC 60870-5-101 FPFARCTINR
of auto-reclosing and -103; Optional
interruption
Output status object Output status object

when station type is
DNP 3.0, Optional
114 TERM / OS Command termination Only IEC 60870-5-101 FPFARCTSCE
of auto-reclosing in use/ and -103; Optional
out of use –cmd
Output status object Output status object

when station type is
DNP 3.0, Optional

At the first installation the Auto Reclose creates the scale 1_1 (linear 1:1 scale). For
multiple shots with ANSI type of station the installation creates also the scale
BGU_1_1000 (linear 1:1000 scale).
4.10. Trip Signal

This chapter describes the installation of Trip Signal standard function from the SA-
LIB. The standard function for the Trip Signal is found in the directory /SA_LIB/
BASE/BBONE/INST and it should be installed by using the SA-LIB installation
procedures (SA_LIB/Process/Trip Signal). This standard function is configured by
using the configuration tools, such as:
1. Object Navigator

The SA symbol for Trip Signal standard function is installed by using the Display
Builder functions:
2. Palette
94
Application Design
For further information, refer to the SYS 600 Process Display Design manual..
Table 4.10.1.1-1 SA symbol for the Trip Signal standard function

File Name Symbol
Tripping.sd

The Trip Signal standard function has the following attributes to be configured with
the Object Navigator or the List-Based Engineering Tool:
Table 4.10.1.2-1 Configurable Attributes

objects
DNP 3.0 protocol
EVENT_RECORDING Process objects for event recording No process objects
with RP-570
LINK_TRIP_TAG_TO_LN_x The logical name of the database -
process objects to which this trip tag
is linked.
LINK_TRIP_TAG_TO_ The module to which this trip tag is No linking
MODULE_x linked.

Depending on the configuration of the Trip Signal standard function, the tools create
a certain set of process objects in the database. Those process objects which are
going be linked to actual process should be edited to have a station number, an
address and a proper switching state. All other attributes should have suitable values
for normal operation by default.
Table 4.10.1.3-1 Process objects created for Trip Signal

10 General protection trip The general protection trip indication can be used as
indication (optional) ON/OFF type indication of any protection trip within
the bay.
11 General trip relay latched The general trip relay latched indication can be used
indication (optional) as ON/OFF type indication of any latched protection
trip relay within the bay.
95
Application Design
Table 4.10.1.3-1 Process objects created for Trip Signal

12- General trip relay reset The general trip relay reset command object is an
17 command (optional) output object which can be used to reset latched
output relays, trip indicators and memorised
parameters.
110 General protection trip Event recording object (for accurate time stamp) with
indication (optional) RTU 2xx/RP-570 type of stations.
111 General trip relay latched Event recording object (for accurate time stamp) with
indication (optional) RTU 2xx/RP-570 type of stations.
112- Indication for command Indicates with IEC 60870-5-101 and -103 whether the
117 termination (optional) issued command was successful or not.
4.10.2.1. Structure of the Trip Signal standard function

This section describes the structure of the Trip Signal standard function. All sub-
included. The Trip Signal is a part of the standard functions of SA-LIB and has the
LANG0 and USE.
4.10.2.2. Files
Below there is a list of all Trip Signal standard function related files and their
functionality.
Table 4.10.2.2-1 Trip Signal stardard function related files

Tripping.sd SA symbol for Trip Signal PROG/GRAPHICSENGINE/PALETTE/04
- SA_Indication
FORM5SAGR1.PIC Generic format picture for SA_LIB/BASE/BBONE/USE
printing

The following Text Translation Tool compatible text file is used by the Trip Signal
Table 4.10.2.3-1 Text Translation Tool compatible text file used by the Trip
Signal standard function
File Functionality
SAI_TRIP2.TXT Text file for the database creation of the standard function

The path to the Trip Signal help text file is /SA_LIB/BASE/BBONE/LANG0.
Table 4.10.2.4-1 Help text file used by the Trip Signal

File Functionality
SAI_TRIP2.HLP Standard function installation help file
96
Application Design

The following configuration files are used by the Trip Signal standard function. The
Table 4.10.2.5-1 Configuration files used by the Trip Signal standard

function
File Functionality
SAI_TRIP2.DAT Contains the configuration data for Trip Signal when it is created
SAI_TRIP2.POT Contains the process object definitions for the Object Navigator and
NDEX5_B1.TXT Selection list of SA-LIB standard functions for installation tool.

The following process objects are created for the Trip Signal standard function.
Table 4.10.2.6-1 Process objects created for the Trip Signal

10 BI Protection trip Optional FPFTRPITRP
11 BI Trip relay latched Optional FPFTRPITRL
12- BO Latched trip relay reset Optional FPFTRPCTRL
17
110 EVREC Protection trip Only RP-570 FPFTRPETRP
Optional
111 EVREC Trip relay latched Only RP-570 FPFTRPETRL
Optional
112- TERM Command termination of Only IEC 60870-5- FPFTRPTTRL
117 latched trip relay reset 101 and -103;
Optional

At the first installation the Trip Signal creates the scale 1_1 (linear 1:1 scale).
4.11. Generator

This chapter describes the installation of generator standard function from the SA-
LIB. You can find the standard function for generator in the /SA_LIB/BASE/
BBONE/INST directory and install it by using the SA-LIB installation procedures
(SA_LIB/Process/Generator). To configure this standard function, you can use the
following tools:
1. Object Navigator
97
Application Design
4.11.2. Symbol installation

You can install the SA symbol for the generator standard function by using the
1. Object Browser
2. Palette
For further information, refer to the Process Display Design manual.
Table 4.11.2-1 SA symbol for the generator standard function

File Name Symbol
Generator.sd
4.11.3. Configuration with tools

You can configure the following generator standard function attributes with the
Object Navigator or the List-Based Engineering Tool:
Table 4.11.3-1 Generator standard function configurable attributes

4.11.4. Configuration of process object

The generator’s configuration creates one process object in the database.
Table 4.11.4-1 Process object created for the generator

255 Generator color Used for generator coloring object by DMS 600
4.11.5.1. Structure of the generator standard function

This section describes the structure of the generator standard function. All the sub-
included in it. The generator is a part of the standard functions of SA-LIB and has
the directory /SA_LIB/BASE/BBONE and the standard SA-LIB subdirectories
98
Application Design
4.11.5.2. Files
Below, there is a list of all the generator standard function related files and their
functionality.
Table 4.11.5.2-1 Generator standard function related files

Generator.sd SA symbol for the generator PROG/GRAPHICSENGINE/PALETTE/
01 - SA_Common

The following Text Translation Tool compatible text file is used by the generator
Table 4.11.5.3-1 Text Translation Tool compatible text file used by the
generator standard function
File Functionality
SAI_GEN.TXT Text file for the database creation of the standard function

The path to the generator help text file is /SA_LIB/BASE/BBONE/LANG0.
Table 4.11.5.4-1 Help text file used by the generator

File Functionality
SAI_GEN.DAT Contains the configuration data and process object definitions for the
generator when it is created, modified or deleted by configuration tools

The following configuration files are used by the generator standard function. The
Table 4.11.5.5-1 Configuration files used by the generator standard function

File Functionality
SAI_GEN.DAT Contains the configuration data and process object definitions for the
generator when it is created, modified or deleted by configuration tools
INDEX5_B1.TXT Selection list of SA-LIB standard functions for the Installation tool
4.11.5.6. Process object

The following process object is created for the generator standard function.
Table 4.11.5.6-1 Process object created for the generator

Index Obj. type Process object Remarks Group ident
255 AI Generator color - BCHTCIXPCD
4.11.5.7. Scale object

At the first installation the generator creates the scale 1_1 (linear 1:1 scale).
99
Application Design
4.12. Line Indicator

This chapter describes the installation of line indicator standard function from SA-
LIB. You can find the standard function for the line indicator in the /SA_LIB/BASE/
BBONE/INST directory and install it by using the SA-LIB installation procedures
(SA_LIB/Process/Line Indicator). To configure this standard function, you can use
the following configuration tools:
1. Object Navigator
4.12.2. Symbol installation

You can install the SA symbol for the line indicator standard function by using the
1. Object Browser
2. Palette
For further information, refer to the Process Display Design manual.
Table 4.12.2-1 SA symbol for the generator standard function

File Name Symbol
Line Indicator.sd
Line Indicator H.sd
4.12.3. Configuration with tools

The line indicator standard function has the following attributes to be configured
Table 4.12.3-1 Line indicator standard function configurable attributes

P_OBJECT_LN Logical name of the database process -
objects
LINE_INDICATOR_ Specifies which product or function is DMS 600
COLORED_BY used for the coloring
100
Application Design
4.12.4. Configuration of process objects

Configuration of the line indicator creates a certain set of process objects in the
database.
Table 4.12.4-1 Process objects created for the line indicator

10 DMS 600 color number Used for line indicator coloring object by DMS
600
253 Virtual switch for Topol. Col. Virtual switch for Topological Busbar Coloring
254 Ext. ground ind. For Topol. Col. External ground indicator for Topological
Busbar Coloring
255 Infeed color for Topol. Col. Infeed color for Topological Busbar Coloring
4.12.5.1. Structure of the line indicator standard function

This section describes the structure of the line indicator standard function. All the
sub-drawing files, form pictures, help and other text files, as well as database objects
are included. The line indicator is a part of the standard functions of SA-LIB and has
the directory /SA_LIB/BASE/BBONE, and the standard SA-LIB subdirectories
4.12.5.2. Files
Below, there is a list of all the line indicator standard function related files and their
functionality.
Table 4.12.5.2-1 Line indicator standard function related files

Line Indicator.sd Vertical SA symbol for Line PROG/GRAPHICSENGINE/PALETTE/
Indicator 01 - SA_Common
Line Indicator H.sd Horizontal SA symbol for PROG/GRAPHICSENGINE/PALETTE/
Line Indicator 01 - SA_Common
FORM5SAGR1.PIC Generic format picture for SA_LIB/BASE/BBONE/USE
printing

The following Text Translation Tool compatible text file is used by the line indicator
Table 4.12.5.3-1 Text Translation Tool compatible text file used by the line
indicator standard function
File Functionality
SAI_LIND.TXT Text file for the database creation of the standard function
101
Application Design

The path to the line indicator help text file is /SA_LIB/BASE/BBONE/LANG0.
Table 4.12.5.4-1 Help text file used by the line indicator

File Functionality
SAI_LIND.HLP Standard function installation help file

The following configuration files are used by the line indicator standard function.
Table 4.12.5.5-1 Configuration files used by the line indicator

File Functionality
SAI_LIND.DAT Contains the configuration data and process object definitions for the
line indicator when it is created, modified or deleted by configuration
tools
INDEX5_B1.TXT Selection list of SA-LIB standard functions for the Installation tool

At first installation, the line indicator creates the command procedure SAI_MTSTS,
which updates the status of the line indicator color.
For the indication type of an analog input (AI), the installation creates the command
procedure SAI_MT2TC, which updates the fictitious power indicator, grounding
indicator and active voltage color.

The following process objects are created for the line indicator standard function.
Table 4.12.5.7-1 Process objects created for the line indicator

Obj.
Index Process object Remarks Group ident.
type
10 AI DMS 600 color number - BCHMTCXFCD
253 BI Virtual switch for Topol. Col. - BCHTCIXFPI
254 AI Ext. ground ind. for Topol. Col. - BCHTCIXCCD
255 AI Infeed color for Topol. Col - BCHTCIXPCD
4.12.5.8. Scale object

At first installation, the line indicator creates the scale 1_1 (linear 1:1 scale).
102
Application Design
4.13. Descriptions to the configurable attributes
STATION_NAME A selector type of an editable combo box to select or enter the

name of the substation. By default, the maximum length of the
text is 9 characters. The selection list shows up to ten latest
entries.
The configurable attribute is read directly from the process

object database, if there is any process object linked to the
selected station picture function. Therefore, the configurable
attribute within a picture function has only meaning when the
process objects have not been created.
This text is used as a substation identifier of the common station

objects on event list, alarm list, printout, database query, and so
on. It is very important that this text is similar to all objects within
the same substation.
P_OBJECT_LN The logical name of the database process objects. The

maximum length of the text is 10 characters. Allowed characters
are letters A-Z, all digits and the underscore (_).
The logical names of process objects have to be unique

throughout the entire system, that is, different objects cannot
have the same logical name. Therefore, it is very important to
have a proper naming convention for the process object
database.
Certain naming convention is also required to speed up the

opening time of the main dialogs. With the predefined naming
convention it is possible to collect all station and bay related
database objects without searching through the complete
database. Therefore, it is advised to use the following naming
convention:
• The first three characters identify the substation

• The following four characters identify the bay
• The last three characters can be freely used to
identify the source of the signal, that is, device, unit,
and so on.
The following list is presented as an example of the proper

naming convention within one bay. The station name is Green
Bay and the bay name is HA12 Downtown:
103
Application Design
- GRB, station
- GRBHA12BAY, bay
- GRBHA12Q0, circuit breaker Q0
- GRBHA12Q1, truck Q1
- GRBHA12Q9, earth switch Q9
- GRBHA12CT, measurements/current transformer
- GRBHA12VT, measurements/voltage transformer
- GRBHA12ALA, alarm indicator
- GRBHA12AR, auto-reclosing tag
- GRBHA12TRP, tripping tag
- GRBHA12R1, feeder terminal or protection unit 1
- GRBHA12R2, feeder terminal or protection unit 1
- GRBHA12LS1, line segment 1 of busbar coloring
- GRBHA12LI, line indicator of busbar coloring
If some other naming convention than 3+4 is used, it usually

takes a longer time to open the main control dialogs.
STATION_TYPE A selector type of a combo box to select the station type of the
objects.
The database process objects are created for the station type
defined here. The list of supported protocols is as follows:
- SPA
- ANSI
- LON
- RP-570
- RP-570 with FTABs
- IEC 60870-5-101
- IEC 60870-5-103
- IEC 61850-8
- DNP 3.0
- Modbus RTU
- PROCOL
CMD_PARAMETER A selector type of a combo box to select a command parameter

for the control method. This attribute has meaning only if IEC
60870-5-101 or DNP 3.0 protocol is selected, otherwise this
attribute is disabled.
The supported control parameters for the IEC 60870-5-101

protocol are:
- Double command (TY = 46)

- Single command (TY = 45)
and for DNP 3.0 protocol:
- Direct
- Direct - No ack.
104
Application Design
OUTPUT_STATUS An ON/OFF type of a toggle button to select whether there is

need for output status process objects with the DNP 3.0
protocol. If STATION_TYPE is other than DNP 3.0, the
configurable attribute is disabled, and the value has no meaning.
AUTHORIZATION_ A selector type of an editable combo box to select the

GROUP authorization group for the object. The maximum length of the
text is 63 characters. The given text has to be usable as a SCIL
list attribute name (see Programming Language SCIL manual).
The contents of the selection list is taken from the existing
authorization groups.
The name may not be composed of two letters followed by a

number.
The attribute needs to be defined, if the object is wanted to be

included in some authorization group. The authorization level of
each user in this group can be defined afterwards by the system
manager with User Management pictures.
STATION_LR_IN_USE An ON/OFF type of a toggle button to select if the station local/

remote switch is in use, that is, a physical switch exists.
By default, the station local/remote switch is in use.
If this selection is set OFF, the control authority is given to

everyone whose personal authorization level is high enough for
the control actions. This is gained by setting the state (value) of
the station local/remote switch permanently out of use.
The process object for station local/remote switch is created

regardless of the selection. If the station local/remote switch is
NOT in use, the process object should be left as it is created,
that is, switching state (SS) to manual and value (DB) as 3 (out
of use).
IND_DOUBLE_BINARY An ON/OFF type of toggle button to select whether the station/

remote switch indication type is double binary or single binary.
This selection is disabled and it has no meaning if the station/
remote switch is not in use, that is, STATION_LR_IN_USE is not
set.
Depending on the actual field device or communication protocol,

the indication of the local/remote switch is sent either as a single
binary (0/1) or as a double binary (0/1/2/3) format.
Binary input:
0 = Remote
1 = Station
Double binary input:

0 = Local
1 = Station
2 = Remote
3 = Out of use
105
Application Design
LR_REMOTELY_ An ON/OFF type of a toggle button for the selection, whether the
CONTROLLABLE station local/remote switch can be controlled remotely by SCS or
MicroSCADA, or not.
By default, the station local/remote switch is defined as manually

controllable only.
Typically, if there is a remote control for the station local/remote

switch, switching election between the station and remote can
be done remotely, whereas switching election to or from local
has to be performed locally.
Switching to and from local:

This can be achieved by setting the attribute SS (switching
state) of the local command -process object to OFF (0). Setting
the SS-attribute to 0 will make the relevant radio-button in the
dialog insensitive for selections.
EVENT_RECORDING An ON/OFF type of a toggle button to select whether there is

need for event recording process objects with the RP-570
protocol. If STATION_TYPE is other than RTU 2xx or RTU 2xx/
FTABs, the configurable attribute is disabled and the value has
no meaning.
With the RP-570 the time stamp from process device comes into
the event recording process object. If no accurate time stamp is
needed or available, or the device is emulating the RP-570
without an event recording possibility, do not set this attribute
ON.
OPC_ITEM_PREFIX Specifies the OPC Item Prefix used as an IEC 61850 instance
information. The default is “IEC61850 Subnetwork.IED1.LD1".
OPC_LN_INSTANCES Specifies the OPC Logical Node names used as IEC 61850
instance information. The dafult is VECTOR("LLN0").
BAY_NAME A selector type of an editable combo box to select or enter the

name of the bay (feeder). By default, the maximum length of the
text is 14 characters. The selection list shows up to ten latest
entries.

selected bay picture function. Therefore, the configurable
attribute within a picture function has meaning only when the
process objects have not been created.
This text will be used as a bay (feeder) identifier of the common

bay objects on event list, alarm list, printout, database query,
and so on. It is very important that this text is similar to all
objects within the same bay (feeder).
106
Application Design
BAY_LR_IN_USE An ON/OFF type of a toggle button to select if the bay local/

remote switch is in use, that is, a physical switch exists.
By default, the bay local/remote switch is in use.
It is typical that if RTU 200 or RTU 210 is used as a remote

terminal unit, there is no bay local/remote switches at bay level.
The control authority of a single bay is determined by using
station local/remote switch only.
The process object for bay local/remote switch is created

regardless of the selection. If the bay local/remote switch is NOT
in use, the process object should be left as it is created, that is,
switching state (SS) to manual and value (DB) as 2 (remote).
BAY_LR_POLARITY The polarity of the bay local/remote-switch input signal.
LR_REMOTELY_ An ON/OFF type of a toggle button to select if the bay local/

CONTROLLABLE remote switch can be controlled remotely by SCS/MicroSCADA.
This selection is disabled and it has no meaning if the bay local/
remote switch in not in use, that is, BAY_LR_IN_USE is not set.
By default, bay local/remote switch is defined as manually

controllable only.
It is typical that if there is a remote control for bay local/remote

switch, shift to local can be done remotely, whereas shift from
local to remote has to be performed locally. This can be
achieved by setting the attribute SS (switching state) of the local
command process object to OFF (0). By setting the SS-attribute
to 0, the relevant radio-button on dialog becomes insensitive for
shifting.
DEVICE_NAME A selector type of an editable combo box to select or enter the

name (identifier) of the switching device. By default, the
maximum length of the text is 5 characters. The selection list
shows up to ten latest entries.

selected switching device.
Therefore, the configurable attribute within a picture function has

meaning only when the process objects have not been created.
This text will be used as an identifier of the switching device on

event list, alarm list, printout, database query, and so on.
107
Application Design
SWICHING_DEVICE A selector type of a combo box to select the type of the

_TYPE switching device. By default, the type is a circuit breaker.
The configurable attribute has a great effect since it defines the

index range for process objects, the texts within database and
dialogs, the functionality and methods on dialogs, and so on. It is
also used by the event and alarm list when filtering certain types
of switching devices.
Circuit breakers:
• Circuit breaker
• Circuit breaker with synchro-check
• Circuit breaker-disconnector (no full breaking capacity)
Disconnectors:
• Disconnector
• Fuse switch
• Load breaking switch
Earth switch
Fault-making switch
Truck
Three-state switch
(needs to be set up by installing two picture functions)
SWICHING_DEVICE_ A selector type of a combo box to select the purpose of the

PURPOSE switching device.
The configurable attribute has just an informative purpose since

by the default it is not used by any function within LIB 5xx. The
attribute is stored into process object database (the 25th or the
26th character of the RX attribute) for user-defined purposes, for
example, for special search condition on the alarm or event list.
Circuit breakers:
• Circuit breaker
• Main busbar circuit breaker
• Main busbar A circuit breaker
• Main busbar B circuit breaker
• Reserve busbar circuit breaker
• By-pass circuit breaker
• Bus-section circuit breaker
• Bus-coupler circuit breaker
Disconnectors:
• Disconnector
• Main busbar disconnector
• Main busbar A disconnector
• Main busbar B disconnector
• Reserve busbar disconnector
108
Application Design
• By-pass disconnector
• Line disconnector
• Line disconnector A
• Line disconnector B
• Bus-section disconnector
• Bus-section A disconnector
• Bus-section B disconnector
• Bus-section C disconnector
• Bus-coupler disconnector
Earth switches:
• Earth switch
• Main busbar earth switch
• Main busbar A earth switch
• Main busbar B earth switch
• Reserve busbar earth switch
• By-pass earth switch
• Line earth switch
• Line earth switch A
• Line earth switch B
• CT-section earth switch
Fault-making switch
Truck
Three-state switch
SWITCH_SECTION A selector type of a combo box to select the switch section for
the truck and the three-state switch. If
SWITCHING_DEVICE_TYPE is some other than truck or three-
state switch, the configurable attribute is disabled, and the value
has no meaning.
When the type of the switching device is truck, this configurable

attribute is needed to combine two picture functions as one
physical truck for Busbar Coloring. If there is a circuit breaker
with two truck picture functions, this attribute should have a
different value for both truck picture functions. In that way the
Busbar Coloring calculation algorithm knows that the other
picture function is not a duplicate but a part of the other one.
Any of the two picture functions can be selected as the first

section, as long as the other picture function is selected as the
second section of the truck. If only one picture function will be
used (that is, one sided installation), the attribute can be left by
default.
As far as the three-state switch is concerned, this selection will

be used to identify whether the picture function is for the
disconnector section or for the earth switch section of the three-
state switch.
109
Application Design
INDICATION_TYPE A selector type of a combo box to select the type of the position
indication process object(s). By default, the process object type
is defined as a double indication (DB).
The purpose of this configurable attribute is to support other

data type than double indication as the position indication of the
switching device. The supported data types are:
Double indication (DB)

Single indication (BI)
2 x Single indications (2 x BI)
Analog input (AI)
The interface between the picture function and the process

object database is always with double indication object, that is,
there is an additional process object(s) receiving information and
then passing it to double indication.
MOTORIZED An ON/OFF type of a toggle button to select if the switching

device is motorized and remotely controllable by SCS/
MicroSCADA. By default, the switching device is defined as a
motorized object.
By selecting Motorized option, the Process Object Tool (POT)

will create a set of process objects for control purpose and all
configurable attributes related to control are being enabled.
110
Application Design
CONTROL_TYPE A selector type of a combo box to select the control method and
the type of the control process object(s). If the configurable
attribute MOTORIZED is not selected, this attribute is disabled,
and the value has no meaning.
The purpose of this configurable attribute is to support other

control methods and process object types than the conventional
one. The conventional control method depends very much on
the configurable attribute STATION_TYPE since there is a
certain default method for each protocol to control the switching
device. The supported control methods are:
• Secured command with four binary outputs

(open select, close select, execute, cancel)
• Secured command with two binary outputs
(open execute, close execute)
• Secured command with two digital outputs
(open execute, close execute; pulse length configurable)
• Secured command with a single binary output (*)
(open select/close select/execute/cancel)
• Secured command with a single analog output
(open select, close select, execute, cancel or open execute/
close execute)
• Secured command with five binary outputs
(open select, close select, open execute, close
execute,cancel)
• Direct command with a single binary output
(open execute/close execute)
(*) Control method not supported with SPA and ANSI protocols
Normally, A RTU 2xx with RP-570 uses secured command with

a single binary output.
CONTROL_PULSE An input field for integer value to set the pulse length of the
_LENGTH control pulses. The configurable attribute is enabled, if the
attribute MOTORIZED is set and CONTROL_TYPE is secured
control with two digital outputs.
111
Application Design
CONTROL_BITS A vector type of an input field for integer values to specify the
bits to be used to send a control command to the switching
device. The configurable attribute is enabled if the attribute
MOTORIZED is set and CONTROL_TYPE is a secured control
with an analog output.
There is a need to specify two or four elements for that vector. If

two elements are specified, the first element represents the bit
for Open execute while the second element is for Close execute.
When four elements are used, the first represents the bit for
Open select, the second represents Close select, the third
represents Execute and the fourth represents Cancel.
When five elements are used, the first represents the bit for
Open select, the second represents Close select, the third
represents Open execute, the fourth represents Close execute
and the fifth represents Cancel.
The bit vector shall be given to the SCT in the following way:
(0,1) or (9,10,11,8) or (0,0,1,2,3).
AUXILIARY_PLUG An ON/OFF type of a toggle button to select whether the device

utilizes an auxiliary plug or not. If the
SWITCHING_DEVICE_TYPE is truck or three-state switch, the
configurable attribute is disabled, and the value has no meaning.
The process object for an auxiliary plug informs if the control

cable from the switching device to the cubicle has been
disconnected, that is, if the switching device is fully racked out
from the cubicle. In that case, no switching device symbol is
shown in the single line diagram.
The process object can also be used as an internal tag without

the process connection. In that case, the control dialog asks the
auxiliary plug state when the object state is intermediate.
INTERLOCKING Specifies whether the interlocking bypass function is used or not.

_BYPASS The default is FALSE.
SYNCHROCHECK Specifies whether the synchrocheck bypass function is used or

_BYPASS not. The default is FALSE.
112
Application Design
QUALIFIERS Qualifier is a value that is written to the QL attribute of process

object when writing the control command. The qualifiers are
given as a vector of integers. Minimum length is 0 (default) and
maximum length 5. The vector items have the following
meanings:
Item Meaning
1= Qualifier for open select
2= Qualifier for close select
3= Qualifier for open execute
4= Qualifier for close execute
5= Qualifier for cancel
For example, (1,2,3) defines qualifier 1 for open select, qualifier

2 for close select and qualifier 3 for open execute.
It is not possible to give "empty" items e.g. (,,,,3), but all the
values must be given, e.g. (0,0,0,0,3).
NOMINAL_VOLTAGE The nominal voltage of the voltage regulator.
MIN_POSITION The minimum position of the tap changer.
MAX_POSITION The maximum position of the tap changer.
TRANSFORMER_TYPE Selection for the 2-winding or 3-winding transformer.
HARD_WIRED The connection type between different SPAU modules when

parallel operation is used. Hardwired means that different SPAU
modules have a physical wiring between them. This is used
when master/slave operation mode is wanted.
AUTO_MANUAL_ID The type and polarity of the auto/manual indication object for
_TYPE Generic tap changer.
TYPE_MEAS_’number’ The type of the measurement. The type identifies the

measurement for the creation of database (indexes, object texts,
units...). In case no suitable alternative can be found, the
indexes 27...37 can be used. The indexes 27 ... 32 are for user-
defined analog (AI) objects, and the indexes 33 ... 37 are for
user-defined pulse counter (PC) objects.
The database objects are not created until the Process Object
Tool has been used to create them.
FOLDER_’number’ The name of the measurement to be shown in the measurement

_TITLE dialog. Attribute is optional, if it is not given, the measurement is
referred to as "Meas. 'number'" in the dialog.
If the configurable attribute TYPE_MEAS_'number' is not

configured, this attribute is disabled, and the value has no
meaning.
113
Application Design
MEAS_’number The number of decimals used when presenting the

’_DECIMALS measurement value in the dialog.
If the configurable attribute TYPE_MEAS_'number' is not

configured, this attribute is disabled, and the value has no
meaning.
OPC_LN_INSTANCE_1 Specifies the OPC Logical Node names used as IEC 61850
Instance information for the measurement type 1. The default is
VECTOR("MMXU1").
Instance information for the measurement type 2.
The default is VECTOR("MMXU1").
TYPE_OF_SIGNAL’nr’ A selector type of a combo box to select the type of the signal.
The list of supported input signals is as follows:
• Binary Input (BI)

• Double Binary (DB)
• Analog Input (AI)
• Linked
If any of the first three choices is selected, the process objects

are created by using the Process Object Tool. When Linked is
selected, the logical name and the index of the process object
where the signal is connected to has to be given. When an
empty string is selected, it means that the signal is discarded by
the alarm indicator.
SIGNAL’nr’_TEXT This text is used as an identifier of the signal on event list, alarm
list, printouts, and so on.
ALARMING_STATE_OF_ The alarming state of the signal is defined by this attribute. The
SIGNAL’nr’ value of the attribute is related to the type of the signal. The
following examples clarify how this attribute should be defined:
- Type of signal is BI, alarming state is 1

value to be set: (1)
- Type of signal is DB, alarming states are 0 and 3
values to be set: (1,0,0,1)
- Type of signal is AI, high alarm = 12, high warning
= 10, low warning = 8, low alarm = 6
values to be set: (12,10,8,6)
LINK_SIGNAL’nr’_TO_LN The logical name of the process object to which the signal is
linked.
114
Application Design
LINK_SIGNAL’nr’_TO_IX The index of the process object to which the signal is linked.
AR_WITH_MULTIPLE_ An ON/OFF type of a toggle button to select the object type for
CYCLES the indication auto-reclosing in progress. The configurable
attribute is enabled, if the attribute P_OBJECT_LN has been
configured. The database process objects will be created either
as a binary input or as an analog input depending on the
selection.
SHOW_AR_IN_USE An ON/OFF type of a toggle button to select if the tag is shown

when the auto-reclosing is in use. The configurable attribute is
enabled, if the attribute P_OBJECT_LN has been configured.
By default no tag is shown. This is useful when the auto-

reclosure is normally OFF and a warning should be produced if
the auto-reclosing is in use.
SHOW_AR_NOT_IN_US An ON/OFF type of a toggle button to select if the tag is shown

E when the auto-reclosing is not in use. The configurable attribute
is enabled, if the attribute P_OBJECT_LN has been configured.
By default, no tag is shown. This is useful when the auto-

reclosure is normally ON and the warning should be produced if
the auto-reclosing is not in use.
LINK_AR_TAG_TO_LN The logical name of the database process objects of the auto-
reclosing module. The maximum length of the text is 10
characters.
Allowed characters are the letters A-Z, all digits and the
underscore (_). However, an object name cannot begin with a
digit or an underscore.
The configurable attributes LINK_AR_TAG_TO_LN and

LINK_AR_TAG_TO_MODULE are utilized to create a link
between existing auto-reclosing objects from the other LIB 5xx
function (for example. auto-reclosing module) and the auto-
reclosing tag. It even supports linking of user-defined process
objects as LINK_AR_TAG_TO_MODULE is an editable selector.
115
Application Design
LINK_AR_TAG_TO An editable selector type of a combo box to select the type

_MODULE designation of the auto-reclosing module. The configurable
attribute is enabled, if the attribute LINK_AR_TAG_TO_LN has
been configured.
By default, all auto-reclosing modules from SPACOM family

have been implemented for the users to choose from. The
supported modules are:
SPCT 2C5
SPCT 2C17
SPCT 2D38
SPCT 2D46
SPCT 5D54
SPTO 6D3
SPCT 2D38
index 70 HSAR started/reset (E1/E2)
index 74 SSAR started/reset (E6/E7)
index 78 delayed SSAR started/reset (E11/E12)
SPCT 2D46
index 91 HSAR forward started/reset (E1/E2)
index 95 SSAR started/reset (E6/E7)
index 109 auto-reclosing interrupted (E25)
During the relay installation and configuration, the following
indexes have to be created and SPACOM events have to be
enabled as a minimum requirement for the auto-reclosing tag by
using the SPACOM Relay Configuration Tool:
SPCT 2C5
index 65 auto-reclosing started/reset (E1/E2)
SPCT 2C17
index 151 auto-reclosing started/reset (E1/E2)
SPCT 5D54
index 32 auto-reclosing interrupted by ARINH (E30)
index 33 auto-reclosing interrupted manually (E31)
index 34 auto-reclosing interrupted by open cmd (E32)
index 40 shot 1 started/reset (channel 1 - E1/E2)
SPTO 6D3
index 16 auto-reclosing interrupted (E7)
index 17 auto-reclosing interrupted by open cmd (E8)
index 18 auto-reclosing interrupted by ARINH (E9)
index 20 shot 1 started/reset (E11/E12)
116
Application Design
If there is no appropriate auto-reclosing module to choose, or if

freely defined process objects are going to be used, it is possible
to link those objects by using the following syntax:
"IDENT","INDX1","REPR1","INDX2","REPR2", ...
IDENT = module ID - (used only as a comment)
INDX1 = DB index of "AR in progress" -object 1
REPR1 = representation (symbol set) for object 1
INDX2 = DB index of "AR in progress" -object 2
REPR2 = representation (symbol set) for object 2
As an example, the auto-reclosing module SPCT 2D46:

"SPCT
2D46","91","F_REPR/F_ARRUN4","95","F_REPR/
ARRUN5"
The type designation of the auto-reclosing module is not

necessary; it is just additional information for users.
LINK_TRIP_TAG_TO The logical name of the database process objects of the

_LN_x protection module x (x=1..5). The maximum length of the text is
10 characters. Allowed characters are the letters A-Z, all digits
and the underscore (_).
The configurable attributes LINK_TRIP_TAG_TO_LN_x and

LINK_TRIP_TAG_TO_MODULE_x are utilized to create a link
between the existing protection tripping indication objects from
the other picture function (for example protection module) and
the trip indication tag. It even supports linking of user-defined
process objects as LINK_TRIP_TAG_TO_MODULE_x, which is
an editable selector.
117
Application Design
LINK_TRIP_TAG_TO_ An editable selector type of a combo box to select the type

MODULE_x designation of the protection module x (x=1..5). The
configurable attribute is enabled, if the attribute
LINK_TRIP_TAG_TO_LN_x has been configured.
By default, all protection modules from the SPACOM family have

been implemented for the users to choose from. The supported
modules are:
SPAM 05x
SPCD 2D55
SPCD 3C21
SPCD 3C22
SPCD 3C23
SPCD 3D53
SPCJ 1C7
SPCJ 1C8
SPCJ 2C30
SPCJ 3C3
SPCJ 3C48
SPCJ 3D35
SPCJ 4D24
SPCJ 4D28
SPCJ 4D29
SPCJ 4D34
SPCJ 4D36
SPCJ 4D40
SPCJ 4D44
SPCJ 4D61
SPCP 3C2
SPCS 2D26
SPCS 2D32
SPCS 2D37
SPCS 3C4
SPCS 4D11
SPCS 4D12
SPCS 4D13
SPCU 1C1
SPCU 1C6
SPCU 1D39
SPCU 1D47
SPCU 3C14
SPCU 3C15
SPEF 3A2
The minimum requirement for the tripping tag to function is that

the following indexes have been created and SPACOM events
have been enabled by using the Relay Configuration Tool:
SPAM 05x
index 122 thermal trip (E5/E6)
index 125 dI> trip (E11/E12)
index 126 Is> trip (E13/E14)
index 128 I0> trip (E17/E18)
index 129 I> trip (E19/E20)
118
Application Design
SPCD 2D55
index 26 TS2 (E31/E32) note!
index 12 dI01> (E3/E4)
index 15 dI02> (E9/E10)
SPCD 3C21
index 32 dI> L1 (E3/E4)
SPCD 3C22
SPCD 3C23
SPCD 3D53
index 31 3dI> trip (E1/E2)
index 32 3dI>> trip (E3/E4)
index 49 3dI> trip/L1 (1E1/1E2)
index 50 3dI>> trip/L1 (1E3/1E4)
SPCJ 1C7
index 14 I0>> trip (E7/E8)
SPCJ 1C8
SPCJ 2C30
index 23 dI0> trip (E1/E2)
SPCJ 3C3
index 22 I>> trip (E7/E8)
SPCJ 3C48
SPCJ 3D35
SPCJ 4D24
index 44 TS2 (E25/E26)
SPCJ 4D28
index 70 I>>> trip (E11/E12)
119
Application Design
SPCJ 4D29
SPCJ 4D34
index 60 thermal alarm trip (E5/E6)
index 61 thermal overload trip (E7/E8)
index 63 Is> trip (E11/E12)
index 71 I< trip (E27/E28)
SPCJ 4D36
SPCJ 4D40
index 80 Ib> trip (E3/E4)
index 82 Ia> trip (E7/E8)
index 84 I< trip (E11/E12)
SPCJ 4D44
index 108 TS2 (E25/E26)
SPCJ 4D61
SPCP 3C2
index 62 U>, U>> trip (E3/E4)
index 64 reverse power trip (E7/E8)
SPCS 2D26
index 87 U0b> trip (E3/E4)
SPCS 2D32
index 99 U02> trip (E9/E10)
index 103 Itr> trip (E17/E18)
120
Application Design
SPCS 2D37
index 12 I01> first trip (E3/E4)
index 14 I01> second trip (E7/E8)
SPCS 3C4
SPCS 4D11
index 121 TS2 (E25/
E26)
SPCS 4D12
index 134 TS2 (E25/E26)
SPCS 4D13
index 147 TS2 (E25/E26)
SPCU 1C1
index 12 U> trip (E3/E4)
index 14 U< trip (E7/E8)
SPCU 1C6
index 18 U0>> trip (E7/E8)
SPCU 1D39
SPCU 1D47
SPCU 3C14
SPCU 3C15
index 22 3U<< trip (E7/E8)
SPEF 3A2
index 101 I> alarm (E3/E4)
index 103 I0> alarm (E7/E8)
index 105 dI> alarm (E11/E12)
As a presumption, these modules are using TS2 as the indicator

of latched output.
If there is no appropriate protection module to pick or if freely

defined process objects are going to be used, it is possible to
link those objects by using the following syntax:
"ID","I1","R1","I2","R2","I3","R3", ...
121
Application Design
ID = module ID - (used only as a comment)

I1 = DB index of latch indication object
R1 = representation (symbol set) for latch indication
I2 = DB index of trip indication object 1
R2 = representation (symbol set) for object 1
I3 = DB index of trip indication object 2
R3 = representation (symbol set) for object 2
If the module does not support sending of an event of a latched

output relay, the vector element I1 has been left as an empty
element, that is, " ".
As an example, non-directional overcurrent and neutral earth-

fault of REF 54x feeder terminal:
"REF54x","","F_REPR/F_LATCH1","1","F_REPR/F_TRIP3",-
”60","F_REPR/F_TRIP11"
The type designation of the protection module x (x=1..5) is not

necessary, if there is no logical name for the protection module
in question.
LINE_INDICATOR_ A selector type of combo box to select the color of line indicator.
COLORED_BY
The line indicator can get its color either from DMS 600, Busbar
Coloring or by manual setting.
122
Application Design
5. Creating single-line diagram

The MicrosSCADA Pro Display Builder is an editor that lets you create complete
graphical interfaces. It is the primary tool that is used when process displays are
created. You can draw the displays and map the signals before or after process
objects have been created to the MicroSCADA process database, except that the
Object Browser requires an existing and running application.
Symbols representing the process objects can be created to an empty display from
the palette, and the signal mappings can be done manually. Alternatively, the LBE
tool can be used to create basic symbol layout and ready signal mappings for the
display, or the symbols and mappings can also be created with the Object Browser.
After adding the symbols for process objects and busbars to the display, the busbar
coloring topology can be built manually or by using the Display Builder's automatic
functions. For more information on the Display Builder, refer to SYS 600 Process
Display Design manual.
A040030
Fig. 5.-1 Main window of Display Builder
123
Application Design
5.1. Connecting signals

The data variable properties can be edited by selecting Edit >Data Variables (see
Fig. 5.1.-1 ). Usually, the Object Browser tool generates automatically the data
variables for those symbols that are dragged to the display from the object browser
tree, and connects the symbol to the variables. Sometimes it is necessary to edit these
settings manually.
In the data source settings, the MicroSCADA application number can be set to all
data variables that exist in the data source. This makes it possible to create more than
one data source in the same picture and define the application for them separately.
A050043
Fig. 5.1.-1 Creating MicroSCADA data source in Data Selection dialog

To create a MicroSCADA data source manually:
1. Select Edit > Data Variables to open the Data Variables dialog.
2. Select MicroSCADA from the New Data Source drop-down menu and click the
Add New Data Source button.
3. Under the MicroSCADA Data Source Settings field, select the application
number from the Application drop-down menu and click Apply. This
application number is applied to all data variables that are created under this
data source.
124
Application Design
The data variable properties contain settings for the data variable name, type and
scope. Type Float can be used for all signal types. The scope should normally be
private. The public scope can be used if the edited view is used as a subdrawing in
other displays, and the variable value has to be accessed in the parent display.
A050042
Fig. 5.1.-2 Creating MicroSCADA data variables

To create MicroSCADA data variables manually:
1. Select the MicroSCADA data source from the data source hierarchy and click
the New variable button.
2. Define the data variable settings under the Data Variable field. These settings
are related to a so called view data variable that is visible to view. Set the type to
Float and scope to Private.
To connect the data variable to the MicroSCADA process database:
1. Under the MicroSCADA Data Variable Settings field, type the process object
reference in the Object Reference text field. The format is <process object
logical name>:P<process object attribute><process object index>. For example,
ESTH01_Q0:POV10. Note that the object reference must be typed in upper case
letters.
2. Select the Type of Variable, refer to MicroSCADA data variable types on
page 126.
125
Application Design
3. Click the Validate button to check that the name was typed correctly and the
process object exists (Fig. 5.1.-3).
ResultOfValid
Fig. 5.1.-3 Validation notice for existing process object

4. Click Apply to save the settings.
MicroSCADA data variable types

The type of the MicroSCADA data variable is selected from the Type of Variable
drop-down menu. Three types are available:
• State indication
• Status color
• Generic signal
The state indication is used for integer state values. There is a possibility to swap
values 1 and 2. If the signal value read from the process object is for example 1, it
can be changed to 2 and written to the view data variable.
The status color is used when the data variable should represent the status color
value for the symbol. Internally this is done by subscribing several process objects’
attribute values from the MicroSCADA OPC Server, and the status color is
calculated based on the attribute values. Some attribute values are also subscribed
from other process indexes, such as values for command event, selected on monitor
status and control blocked signal. These values are subscribed from indexes <current
index> + 10, <current index> + 9,<current index> + 3, respectively.
When the Generic signal is used, no type conversion is done when moving data from
the MicroSCADA OPC Server to the data variable. This variable type can be used
with measurement values and other floating point data types, or text values.
5.2. Busbar coloring

Busbar coloring in the SYS 600 Monitor Pro can be used to indicate the status of the
busbar sections in several different ways. It can indicate which busbar sections are
powered, unpowered or in certain other states, or more accurately, which voltage
level each busbar section has. Alternatively, each voltage source or voltage source
type can have a color that is used for the sections they are connected to. Busbar
coloring may also be used to indicate situations where two or more voltage sources
form a loop.
126
Application Design
A040066
Fig. 5.2.-1 Station with busbar coloring
A040065
Fig. 5.2.-2 Station without busbar coloring

To enable busbar coloring in Monitor Pro, the following information must be saved
in the display file.
Voltage level information must be specified for all line indicators, transformers and
generators in the display. Supported voltage levels are listed in the MicroSCADA
Pro SYS 900 Process Display Design manual. The levels are given by mapping the
following data variables to constant kilovolt values:
• Line indicators: Voltage Level (kV)
• 2-Winding transformers: Primary Voltage Level (kV) and Secondary Voltage
Level (kV)
• 3-Winding transformers: Primary Voltage Level (kV), Secondary Voltage Level
(kV) and Tertiary Voltage Level (kV)
• Generators: Voltage Level (kV)
127
Application Design
Mapping is done by activating a symbol and then selecting Object > Properties.
Select the Subdrawing tab from the appearing dialog. Set Mapping Type to Map to
Constant, and enter the value to the Is Mapped To column.
A040068
Fig. 5.2.-3 Mapping voltage level of line indicator to 110 kilovolts

All graphical objects that are part of the busbar coloring topology must have a
unique identifier and information on which objects they are connected to. When an
object that can be part of the topology is created, the identifier is given automatically
and stored in the value of the object specific custom attribute key SAObjectName.
By default, all graphical objects that can be part of the topology are also given
custom attribute keys to store in the information on the connections. These keys are
named NextObject1, NextObject2, etc.depending on how many connections each
symbol can have. If the keys do not exist, create them by selecting Actions > Add
Selected Objects to Topology. The values for the keys can be specified manually
or generated automatically by selecting Actions > Build Topology. Each value
contains an SAObjectName, colon, and number of the location (Hotspot) which the
object is connected to. If the exact location cannot be given, 0 is used.
Topology details can be viewed one by one by activating an object, selecting Object
> Properties and selecting the Custom tab, or all in one by selecting Actions >
Topology Information.
128
Application Design
A040069
Fig. 5.2.-4 Topology information of SA symbols in bay

All dynamic objects that are part of the topology must have an ID of the
MicroSCADA data source item, because they are mapped to the stored in value of
the custom attribute key OPCItemID. The keys and values are generated
automatically from the data variable mappings when the display file is saved.
Check that the primary winding of a transformer is connected to the

primary side of the topology. In addition, be careful when
connecting sections to the main and reserve busbars from the bay.
Verify that sections "jump" to the correct busbar.
The loop indication is displayed better, if the main and reserve

busbars are built by using several sections instead of a long one.
For more information on preparing process displays for busbar coloring, refer to the
Process Display Design manual.
5.3. Launching external application from process displays

There is a possibility to open external programs, like relay tools from the process
displays of the SYS 600 Monitor Pro. Below there is an example of how to launch
the REF542plus tool by right-clicking a relay symbol.
To create a rule for opening external tools:
1. Open the properties for the selected object and select the Rules tab from the
appearing dialog.
2. Create a new rule as defined in Fig. 5.3.-1.
129
Application Design
A050172
Fig. 5.3.-1 Creating new rule

3. Connect to a correct script file by clicking the Create or Select a Rules Script
File button. Browse the file \sc\prog\graphicsengine\etc\execute.bas.
4. When the script file’s path is showing under the Script File Name, click Close.
A050173
Fig. 5.3.-2 Connecting to specific script file

5. Select Execute from the Action drop-down menu.
130
Application Design
A050174
Fig. 5.3.-3 Creating action

6. Select the Custom tab.
7. Add two custom attributes for the object (Executable and Arguments) by
clicking the Create New Custom Attribute button. Assign proprietary strings
for them. Note that if there are spaces in the strings, you have to use quotation
marks as in the Fig. 5.3.-4.
131
Application Design
A050175
Fig. 5.3.-4 Adding custom attributes

8. Click Close in the Object Properties dialog. When running the process display,
right-clicking the mouse opens the external tool.
5.4. USE CASE - Building an electric network from several

substations
5.4.1. Description
An outgoing line indicator in station A (A:LIOUT) has a connection to an incoming
line indicator of station B (B:LIIN). The color of A:LIOUT has to propagate to
B:LIIN. This means that, if a circuit breaker in station A is opened and A:LIOUT is
colored with unpowered color, B:LIIN must be colored with the same color.
Possible scenarios to solve this problem:
• Use external color handling provided by DMS 600
• Use of an additional circuit breaker and an earthing switch
• Building stations to the same picture
5.4.2. Scenario 1: Using external color handling

This scenario is applicable in systems where DMS 600 is installed. In the SYS 600
Monitor Pro, choose Tools > System tools > Busbar Coloring…. Select Coloring
modes page and select External handling for voltage source colors and then press
OK.
132
Application Design
5.4.3. Scenario 2: Use of an additional circuit breaker and an earthing

switch
An additional circuit breaker and an earthing switch can be used after an incoming
line indicator. The devices can be virtual or real. In this scenario, virtual devices are
created. These two switches simulate the state of the upper level network enabling
to simulate all the states that a feeding line may have, except the state looped.
1. Open MicroSCADA Tool Manager > Object Navigator.
2. Select Object > Install standard function
3. Browse for Standard Functions/SA_LIB/Process/Switching Device and click
Install.
4. Fill in STATION_NAME, BAY_NAME, DEVICE_NAME and
P_OBJECT_NAME. Click Apply.
5. Select Tools tab page, open Process Object Tool and click Create All.
6. Repeat steps 3-5 to create more virtual circuit breakers.
7. Use LIB 5xx Object Browser in Display Builder to create symbols to the station
picture. It is encouraged to clearly separate virtual circuit breakers from the
station picture.
The following figure gives an example of an earthed upper level network (Rivendell
110 kV).
UpperLevelProblem_SeveralStations.tif
Fig. 5.4.-1 Example of an earthed upper level network
5.4.1. Scenario 3: Building stations to the same picture

This scenario is applicable for relatively small networks (maximum of three stations
due to performance).
133
Application Design
1 Build every station separately in Display Builder ( one station to each .v file).
2 Open an empty station picture.
3 Merge and scale each station to the empty picture.
Select File > Merge > Data Source Name and open the first station.
Select Object > Scale > Shrink until the space is enough for stations still left.
Move the station to an appropriate place in the picture.
4 After merging stations, connect stations with Horizontal and Vertical Busbars.
5 Select Actions > Build Topology and see Actions > Topology Information to
see unconnected objects. Fix the topology if needed.
6 Select File > Save.
UpperLevelProblem_SeveralStations.tif
Fig. 5.4.-2 Several stations in the same picture
134
Application Design
6. Adaptations to application window
6.1. Customizing application window
6.1.1. Customizing application layout (GUI)

Monitor Pro supports almost all the Office 2000 features. With Monitor Pro you can:
• Add custom toolbars
• Rename custom toolbars
• Delete custom toolbars
• Rename menu items
• Delete menu items
• Copy or move menu items from one place to another
• Rename toolbar buttons
• Delete toolbar buttons
• Copy or move toolbar buttons from one place to another
However, some menu items and toolbars are generated programmatically. Therefore
they cannot be customized, for example the menu items in the picture specific menu
and the buttons in the application-specific toolbar.
In addition, you cannot add new menus, menu items or toolbar buttons, but you can
copy and move the existing ones. Furthermore, pre-defined toolbars cannot be
deleted, but you can hide or show them.
The Monitor Pro layouts are user-specific. The default layout is loaded when the
user logs into the application for the first time.You can start the Monitor Pro
customization in three different ways:
1. By double-clicking any empty area of the band.
2. By right-clicking the mouse to open the customization pop-up menu. From this
menu, select the Menu Customize menu item.
3. By selecting Tools - Customize.
6.1.2. Customization dialog

In the Customization dialog you can:
• Add, rename and delete custom toolbars (that is, user-defined toolbars)1
• Delete and rename menu items1
• Change the caption and style of the tool context menu
• Get an action tool categorized listing
• Drag and drop to any band, menu or submenu
• Access full keyboard shortcut customization dialog
1. Some menu items (for example the menu items in picture specific menu) and some
toolbars (for example the buttons in application specific toolbar) are not
customizable because they are generated programmatically.
135
Application Design
The tool context menu, see Fig. 6.1.2.-1, is another pop-up menu that you can use
for customization. The context menu can be displayed while the Customization
dialog is open. It can be opened by right-clicking the toolbar button. The styles for
this tool are the following:
• Default style: includes both the text and icon, if available
• Text only: only the text (caption of the tool) is shown
• Image only: only the icon is displayed, if available
• Image and text: includes both the text and icon, if available
CustomizeToolContextMenu
Fig. 6.1.2.-1 Tool context menu, selecting style

When the Customization dialog is open, you can move toolbar buttons and menu
items around. You can create a copy of the tool by pressing down the CTRL key
while moving the tool.
If you are allowed to customize the toolbar, a More tools button is displayed (see
Fig. 6.1.2.-2). This quick customization pop-up menu allows you to show or hide
tools from the toolbar without needing to open the Customization dialog. However,
menu items must be customized by using the Customization dialog.
You can move or delete tools from the bands (toolbars) without opening the
Customization dialog: hold the ALT key down and drag with the mouse the tools
between bands (toolbars) to move them, or away from the band to delete them. If
you hold the ALT+CTRL keys down while moving the tool, a copy of the tool is
made.
136
Application Design
CustomizeMoreTools
Fig. 6.1.2.-2 More tools button
6.1.2.1. Toolbars tab
A040049
Fig. 6.1.2.1.-1 Customization dialog’s Toolbars tab

You can configure the visibility of the toolbars and menus. For customization you
can use either the Customization dialog’s Toolbars tab or by right-clicking on the
area of bands and selecting or deselecting toolbars.
Toolbar visibility is view specific. For process graphics view, alarm list view, event
list view, blocking list view, trends view and full screen view, there are different
configurations on which toolbars are shown. Change the visibility of the toolbar in
a view by selecting the view and changing the visibility of toolbars. The
configuration is automatically saved when some other view is selected.
137
Application Design
CustomizeBands
Fig. 6.1.2.1.-2 Selecting/deselecting toolbars by right-clicking on the bands area
CustomizeFullScreen
Fig. 6.1.2.1.-3 Toolbar menu in full screen mode

You can create a new toolbar by clicking the New button in the Toolbars tab. After
this, a dialog for naming the new toolbar is displayed.
138
Application Design
CustomizeNewToolbar
Fig. 6.1.2.1.-4 New toolbar

When the created toolbar is selected, the Rename and Delete buttons become active
and you can rename or delete the toolbar. By clicking the Undo button in the
Toolbars tab, you can load the last saved layout.By clicking the Keyboard button in
the Toolbars tab, a new dialog is displayed, see Fig. 6.1.2.1.-5 below.
CustomizeKeyboard
Fig. 6.1.2.1.-5 Keyboard shortcuts customization

In the Categories section, you can add a new keyboard shortcut to the menu items
and toolbars. The Categories list contains:
• Built-in Menus: all top-level menus
• Start with characters mi: all menus that have sub bands (sub menu items)
• Start with characters tb: all toolbars (except user-defined toolbars, that is, created
by using the Customization dialog)
The Commands list contains:
• Sub menu items and buttons of selected category
139
Application Design
To give a new value for a tool (menu item or button in the toolbar) take the following
steps:
1. In the Categories list, select the category in which the menu item or toolbar
buttons are located.
2. In the Commands list, select the tool (menu item or toolbar buttons).
3. Type the new shortcut key combination in the text box Press new shortcut key.
4. Click the Assign button and the shortcut key appears in the Current keys field.
With the Remove button, the selected shortcut key in Current keys section can be
removed.You can reset the shortcut keys by clicking the Reset All button.
6.1.2.2. Commands tab
CustomizeCommandsSheet
Fig. 6.1.2.2.-1 Customization dialog’s Commands tab

The Categories and Commands functions are the same as in assigning new keyboard
shortcut keys, described earlier in Section 6.1.2.1. Toolbars tab.The tools can be
moved around as described in the beginning of the Section 6.1.2. Customization
dialog. When you click the Modify selection button, a same kind of pop-up menu
appears as when a toolbar button or menu item is right-clicked while the
Customization dialog is open. The Modify selection button becomes active when
you select a tool either from the menu or the toolbar.
140
Application Design
6.1.2.3. Options tab
CustomizeOptionsSheet
Fig. 6.1.2.3.-1 Customization dialog’s Options tab

You can take the personalized menus into use via the Options tab. Only the most
recently used menus are visible.
The data of menu usage is saved when the application is exited, and loaded again
when the application is started (or the user logs into some application, and user-
specific layout loading actions are done). Also logging into application loads the
menu usage data (in addition to the user-specific layout file). Correspondingly when
logging out, the menu usage data is saved (in addition to the user specific layout
file).
In Options tab, you can select to use menu animations and large icons.You can clear
the menu usage data by clicking the Reset Menu Usage Data button.
6.1.3. Resetting layout

You can access this function from the Tools menu in the application window. The
function resets the layout, that is, old layout files are deleted and new ones localized
and taken into use.
6.1.4. Object specific custom menus

An object specific custom menu opens when a symbol is clicked with the right
mouse button in the process display that is presented in the application window.
Menu structure is familiar from the Windows Start menu. The menu items are
folders and files in a file system. Therefore, no special tool is needed to configure
the menu. The configuration is done by organizing the files (programs, documents
or shortcuts) and the directories in a file system. A menu item can be a file, a
directory, a link or a shortcut to a file or to a directory, or an Internet shortcut.
141
Application Design
Process objects have separate directories, where files such as technical

documentation, Internet shortcuts or control commands (SCIL or VB scripts) exist.
There is also a folder for the common menu items.
Pop-up menu
Pop-up menu items can be added, modified or removed. This is done by using
Windows Explorer to copy the correct files below the Process object directory. It is
also possible for a component using the File System menu to add default or new
items to the menu.
Language support
The menu items have a national language support (NLS). Changing the language of
the application window in run time affects the menu items. However, this is not the
case with the files, because the file name determines the name of the menu item.
Thus, for each culture (country or language), there should be a folder where
language specific files are located. Language specific menus can be built in these
directories.
Title
A title is used to give the operator additional information about the process object,
whose popup menu was opened. For example, the title may be "Erador 20kV
Station, Weathertop, Breaker 1". The title can be horizontally or vertically aligned,
and it can be enabled or disabled. In addition, the title can have an icon or there can
be an icon representing the selected process object.
Icon
An icon and a caption of a menu item is in fact an icon that is associated to a file
type. A caption is a file name without the file extension (.doc for example ). It is
configurable even if it does not have an icon.
Menu items
Disabled menu items are grayed. The menu does not support check boxes, radio
buttons, or shortcut keys.
A file or a folder is an input for a menu item. Changing the name or the icon of the
file changes the appearance of the menu item. If a file or a folder is hidden, it is not
shown or the menu item is disabled. If a target of a link does not exist, the menu item
is disabled.
The icon, name, and the file or folder attributes are read and a menu item is shown
accordingly. If the file or the folder is a link or a shortcut, its’ icon and name are
used. Thus, the target of the link does not affect to the menu item appearance.
The operator receives additional information about a process object by opening a
context-sensitive pop-up menu. It contains the menu items common to all process
objects; menu items that are process object specific and a transformer. There can be
menu items that are shown only for a certain process object instance, such as a log,
a figure, a video clip or a maintenance record.
When a menu item is clicked, a file is opened (using the application that is associated
to it in the operating system). A menu item may also be executable or a script. It is
possible to give arguments to the executables or scripts with the File System menu.
142
Application Design
Each application has its own directory in the file system where the menu structure is
constructed. The directory contains subdirectories, which determine menu items for:
• All process objects
• Process object types, for example breaker and transformer
• Process object instances
Below these directories, there may be language specific folders.
MENUS directory
MENUS directory consists of directories such as all, objecttypes and instances.
• Menu items, which are to be shown in each pop-up menu, should be stored under
the directory all.
• The directory objecttypes consists of all object types that a station overview
might have. Menu items that each object type might have are located here.
• It is also possible that an instance of a breaker might have some menu items that
are instance specific, such as a figure of a breaker, online video stream,
maintenance log or a web link to the manufacturer’s home page. In that case, the
menu items are stored below the instances\<unique object id>.
• The menu for all objects can be found in <apl>\MENUS\all.
Table 6.1.4-1 Menu item descriptions

Name Description Path
<apl> Path of the application E.g. C:\sc\apl\510_403_1
<object type> Type of an object <apl>\MENUS\objecttypes\<object type>

See table "Object types" (common menu for an object type)
<display name> Name of the display file
(without extension .v)
<SaObjectName> SA-name of the object <apl>\MENUS\instances\<display
(instance name) name>\<SaObjectName>\
Menu structures are not shadowed. If HSB system is used,

menus have to be manually copied between Hot/Stand-by -
computer after modifications has been done. Otherwise, the
directories are deleted during the switch-over.
Error handling
Table 6.1.4-2 Possible errors with context-sensitive pop-up menus

Error Handling
There are no items in the menu directory, Only a title of a menu is shown. There might
i.e. menu is empty. also be a message such as "No items" or an
icon presenting that.
A file type of menu item is unknown and an Open With... -dialog will be shown.
icon presenting that is shown.
143
Application Design
Table 6.1.4-2 Possible errors with context-sensitive pop-up menus

Error Handling
A sub menu item is empty The sub menu item is shown and it can be
browsed. However, when browsed, it can be
seen that the sub menu item has no menu
items.
User has no authorization to execute menu The menu item is disabled.
item.
A link target does not exist The menu item is disabled.
Object types
The possible object types are:
• Arc suppression coil
• Branch
• Breaker
• Busbar
• Capacitor
• Condensator
• Current transformer
• Disconnector
• Earth disconnector
• Fault indicator
• Fuse
• Generator
• Line indicator
• Motor
• Primary transformer
• Serial reactor
• Shunt reactor
• Transformer2w
• Transformer3w
• Voltage transformer
• Zero current transformer
When object specific custom menus are created in Hot-Stand-By

systems, the same file structure must be copied manually into both
computers.
At the moment, the object specific custom menus do not support the
localization issues.
144
Application Design
7. Event List
7.1. Introduction to Event List

The SYS 600 Event List provides information on events occuring in the system.
Thus, you can make the right decisions and verify that the taken measures are
successfully performed.
It is also possible to receive information on activities carried out by other users,
operations of objects, acknowledging of alarms, editing of limit values, logging in,
etc.
The Event List presents the data in a structured way for the user's convenience.
Each event is normally presented by displaying an event text line, which describes
the cause of the event in the process. Event text lines usually have an event row
number, a time stamp, an object identification, a signal text, a text indicating the
state and event (see Fig. 7.1.-1). For more information on SYS 600 Event List
functions, see the SYS 600 Operation Manual.
event_list
Fig. 7.1.-1 Event List, main view
145
Application Design
In this chapter, you learn how to configure the SYS 600 Event List, that is, how to
customize column layouts, event coloring and advanced condition in the
preconfiguration.
7.2. Customizing the column layout

The Event List can be configured to have column layouts, which are application or
user specific. If the user specific column layout file is not located in the system, the
default column layout template for the application is used.
The default column layout template for the application contains the following
columns:
• Event row number
• Status columns with symbols for Alarm, Comment, Status
• Date
• Time
• Station
• Bay
• Device
• Object Text
• State Text
• Event Text
elist_layout
Fig. 7.2.-1 Default column layout for Event List

You can find the column layout template for the application in the following folder:
\sc\apl\<application name>\par\apl\event. User specific column
layout templates are located in the following folder: \sc\apl\<application
name>\par\<user name>\event. The column layout files always use the file
name layout.ini.
You can manage the contents of these layout files by using the Layout Settings
dialog of the Event List.
146
Application Design
It is possible to add the following columns of the MicroSCADA system to the Event
List, see Table 7.2.-1. Mainly, the information source for the supported columns is
either from the MicroSCADA process database or from the history database.
Table 7.2.-1 Supported columns for Event List

Column Information Source
AB Alarm Blocking (AB) attribute
AC Alarm Class (AC) attribute
AG Alarm Generation (AG) attribute
AH Action on History (AH) attribute
AL Alarm (AL) attribute
AR Alarm Receipt (AR) attribute
AS Alarm State (AS) attribute
AZ Alarm Zone (AZ) attribute
BC Bit Count (BC) attribute
BL Blocked (BL) attribute
CA Changed Attribute (CA) attribute of history database
CE Counter Enable (CE) attribute
CL Counter Limit (CL) attribute
CO Counter Overflow (CO) attribute
CT Cause of Transmission (CT) attribute
CV Counter Value (CV) attribute
DATE Date of event from Event Time (ET) attribute of history database
ED Event Daylight Saving (ED) attribute of history database
EVENT Message Text (MX) attribute
EX Event Comment Text (EX) attribute of history database
GT Group Type (GT) attribute
HA History Activation (HA) attribute
HB History Blocking (HB) attribute
HD History Logging Daylight Saving (HD) attribute of history database
HH History on History (HH) attribute of history database
HI Higher Input (HI) attribute
HM History logging time Milliseconds (HT) attribute of history database
HO Higher Output (HO) attribute
HT History logging Time (HT) attribute of history database
HW Higher Warning (HW) attribute
IU In Use (IU) attribute
IN Item Name (IN) attribute
IX Index (IX) attribute
LA Alarm Activation (LA) attribute
LI Lower Input (LI) attribute
LN Logical Name (LN) attribute
LO Lower Output (LO) attribute
LW Lower Warning (LW) attribute
NV Normal Value (NV) attribute
OA Object Address (OA) attribute
OB Object Bit Address (OB) attribute
OF Overflow (OF) attribute
OI Object Identifier (OI) attribute
147
Application Design
Table 7.2.-1 Supported columns for Event List (Continued)

Column Information Source
OI1 The 1st level of Object Identifier (OI) attribute
OI2 The 2nd level of Object Identifier (OI) attribute
OI3 The 3rd level of Object Identifier (OI) attribute
OI4 The 4th level of Object Identifier (OI) attribute
OR Out of Range (OR) attribute
OS Object Status (OS) attribute
OT Output Type (OT) attribute
OV Object Value (OV) attribute
OX Object Text (OX) attribute
PF Physical Format (PF) attribute
PH Printout on History (PH) attribute
PT Process Object Type (PT) attribute
RA Reserved A (RA) attribute
RB Reserved B (RB) attribute
RC Receipt (RC) attribute
RI Reserved Integer (RI) attribute
RM Registration Milliseconds (RM) attribute
RT Registration Time (RT) attribute
RX Reserved Text (RX) attribute
SB Substituted (SB) attribute
SE Selection (SE) attribute
SP Stop Execution (SP) attribute
SS Switch State (SS) attribute
ST Sort Type (ST) attribute
STATUS Status columns with symbols for Alarm, Comment, Status
SZ SCADA Zone Supervision (SZ) attribute
SX State Text (SX) attribute
TIME Time of event from Event Time (ET) and Event Milliseconds (EM)
attributes of history database
UB Update Blocking (UB) attribute
UN Unit Number (UN) attribute
XB Activation Blocking (XB) attribute
ZD Zero Deadband (ZD) attribute
ZE Zero deadband supervision Enabled (ZE) attribute
7.3. Defining event coloring

Event coloring displays the most important events in a way that they are easily
located from the Event List. The SYS 600 Event List can be configured to use
different colors for events, which fulfill the defined conditions in the Event Color
Settings dialog. By using this functionality, the Event List can be adapted to display
the events according to the convention required by the application.
7.3.1. Event coloring example

The following is an example of event coloring in an application and the steps of how
it has been defined in the Event Color Settings dialog.
148
Application Design
1. Open the Event Color Settings by selecting Event List > Color Settings.
2. Click the Add button. The new event coloring condition row is now displayed.
3. Double-click the the first column of the Attribute column. Select the HI - Higher
Input attribute from the drop-down list.
4. Double-click the first row of the Condition column. Select Condition < (smaller
than) from the drop-down list.
5. Double-click the first row of the Value column. Enter the value 10 in the Value
field.
6. Double-click the first row of the Color column. Select the color Red from the
drop-down list.
7. Repeat the conditions for the rows 2, 3, 4, 5, 6 and 7 according to the following
Fig. 7.3.1.-1 Event coloring example.
8. Click OK to accept the defined settings. The Event List now displays the events
according to the defined conditions.
elist_color
Fig. 7.3.1.-1 Event coloring example.
7.4. Preconfiguring events with advanced conditions

You can configure the Event List to use advanced condition when defining
preconfigurations for displayed events. You can access the Advanced Condition
dialog by clicking the More button in the Filter dialog and by selecting the
Advanced Condition option.
An example of advanced condition, which you can use in your application is
presented in the following section.
7.4.1. Advanced condition example

When an event occurs in the MicroSCADA system, the information on the event is
stored in the history database. Several attributes are stored in the application as event
history attributes.
149
Application Design
The attribute for the daylight saving (HD - History logging time Daylight saving) is
stored in the history database together with these attributes. Fig. 7.4.1.-1 presents an
example of how to configure an advanced condition, which specifies that only the
events that occurred when daylight saving time was in use, are displayed in the
Event List.
ad_event_cond
Fig. 7.4.1.-1 Advanced condition example
150
Application Design
8. Alarm List
8.1. Introduction to Alarm List

SYS 600 Alarm List displays a summary of the present alarm situation of the
supervised process. Each alarm is normally presented as an alarm text line (see Fig.
8.1.-1) describing the cause of the alarm in the process. An alarm text line consists
of:
• Alarm row number
• Time stamp
• Object identification
• Object text
• Text indicating alarm status
• Number indicating alarm class (range 1...7)
You can find a more detailed description of the Alarm List functions in
SYS 600 Operation Manual.
In this chapter you learn how to configure SYS 600 Alarm List, that is, how to
customize column layout and define advanced conditions in the preconfigurations.
Alarm_list1
Fig. 8.1.-1 SYS 600 Alarm List
151
Application Design
8.2. Customizing column layout

Alarm List can be configured to have column layouts, which are application or user-
specific. For each user, the default column layout template for application is used if
a user-specific column layout file is not located from the system.
A default column layout template for an application contains the following columns:
• Alarm row number
• Date
• Time
• Station
• Bay
• Device
• Object Text
• Status
• Class
AlarmListColumns
Fig. 8.2.-1 Default column layout for Alarm List

You can find the column layout template for application in folder
\sc\apl\<application name>\par\apl\alarm. User-specific column
layout templates are located in folder \sc\apl\<application
name>\par\<user name>\alarm. The column layout files are always using
the file name layout.ini.
You can edit the contents of these layout files by using a normal text editor
application of Windows operating system (for example Notepad). The format of this
file is Windows Initialization (INI) file, which is used typically to describe the
configuration settings in Windows operating system applications, see Fig. 8.2.-2.
152
Application Design
AlarmListAplLayout
Fig. 8.2.-2 Describing configuration settings in layout.ini file

Each column of Alarm List is described by its own section name, for example
[Column1]. The column order is defined by the number in the end of the section
name.
153
Application Design
The key names for each column are presented in the table below.
Table 8.2.-1 Column key names and their contents

Key name Contents
Label Identifies the column name in the Alarm List (for example Date)
Attribute Identifies the information which the Alarm List application reads
from the MicroSCADA Pro system, see Table 8.2.-2.
Length Identifies the length of the column
Table 8.2.-2 Supported attribute keywords

Keyword Source
DATE Date of alarm
TIME Time of alarm
OI Object Identifier (OI) attribute
OI1 The 1st level of Object Identifier (OI) attribute
OI2 The 2nd level of Object Identifier (OI) attribute
OI3 The 3rd level of Object Identifier (OI) attribute
OX Object Text (OX) attribute
STATUS_TEXT Status
AC Alarm Class (AC) attribute
AZ Alarm Zone (AZ) attribute
OS Object Status (OS) attribute
PT Process Object Type (PT) attribute
LN Logical Name (LN) attribute
IX Index (IX) attribute
8.3. Preconfiguring alarm buffer with advanced conditions

You can configure the Alarm List to use advanced conditions when defining
preconfigurations for displayed alarms. You can access the Advanced Condition
dialog in both Alarm List Templates by clicking the More button in the Filter dialog
and by selecting the option Advanced Condition.
Two examples of advanced conditions, which you can use in your application are
presented in the following section.
8.3.1. Advanced condition, example 1

Typically, the alarms of the system are categorized into several alarm classes. This
categorization is used to indicate the functional purpose and importance of alarm
classes. The result of this work depends on the application area in question.
Fig. 8.3.1.-1 presents an example of how to configure an advanced condition, which
specifies that only the alarms belonging to classes 1, 2 and 3 are displayed in the
Alarm List.
154
Application Design
AdvancedAlarmCondition1
Fig. 8.3.1.-1 Configuring advanced conditions for alarms, example 1
8.3.2. Advanced condition, example 2

For the signals of type analog input, the alarming process objects contain
information about limit value supervision, that is, about the reason why the alarm
limit has been violated.
The four different reasons for alarm limit violation can be:
1. Low alarm, the value received from the process is equal or smaller than Low
Alarm (LI) attribute in the limit value configuration
2. High alarm, the value received from the process is equal or greater than High
Alarm (HI) attribute in the limit value configuration
3. Low warning, the value received from the process is equal or smaller than Low
Warning (LW) attribute in the limit value configuration
4. High warning, the value received from the process is equal or greater than High
Warning (HW) attribute in the limit value configuration
155
Application Design
Fig. 8.3.2.-1 presents an example of how to configure an advanced condition in

such a way that only the alarms from analog input’s process objects violating the
low alarm or high alarm are displayed in the Alarm List.
AdvancedAlarmCondition2
Fig. 8.3.2.-1 Configuring advanced conditions for alarm limit violation,

example 2
156
Application Design
9. Blocking List
9.1. Introduction to Blocking List

SYS 600 Blocking List displays a summary of the present signal blocking situation
of the supervised process. Each signal is presented as a signal text line, describing
the signal in the process, see Fig. 9.1.-1. A signal text line consists of:
• Blocked signal row number
• Signal text
• Check boxes indicating blocking state
You can find a more detailed description of the Blocking List functions in
SYS 600 Operation Manual.
In this chapter, you learn how to customize the SYS 600 Blocking List blocking
settings.
BlockListExp
Fig. 9.1.-1 Blocking List main view
Table 9.1.-1 Explanations to Fig. 9.1.-1

Number Explanation
1 Tool menu for Blocking List
2 Toolbar buttons
3 Check boxes indicating the blocking state of the signal
4 Current page and the total amount of pages
5 Signal text
6 Scroll box
7 Arrows for scrolling the page up or down
8 Fields presenting sum of signals for each blocking type
157
Application Design
9.2. Customizing blocking settings

You can configure application or user-specific settings for Blocking List. If a user-
specific blocking settings file can not be located from the system, a default blocking
settings template for application is used for each user.
A default blocking settings template contains the following settings:
• Show Update Blockings
• Show Control Blockings
• Show Alarm Blockings
• Show Event Blockings
• Show Printout Blockings
• Show Action Blockings
• Enable event on block/deblock (Off)
• Enable printout (Off)
BlockingListSettings
Fig. 9.2.-1 Default blocking settings for Blocking List

You can find the default blocking settings template in folder
\sc\apl\<application name>\par\apl\blocking. The templates for
user-specific blocking settings are located in folder \sc\apl\<application
name>\par\<user name>\blocking. Blocking settings files always use the
file name blocking_settings.ini.
You can manage the contents of these layout files in the Blocking Settings dialog of
the Blocking List.
158
Application Design
10. Trends
Trend Display is a component included in the MicroSCADA Monitor Pro
application. Trend Display functionality is similar to one of the Trend Reports
picture in LIB 510.
Trend Display is used for trend analyses and for showing measured values in curve
or table form.
A050171
Fig. 10.-1 Trend Display
159
Application Design
10.1. Introduction to trends

A trend is a time-related follow-up of process data. All types of process objects, like
in and out data, binary, analogue and digital data can be illustrated as trends. When
a trend picture is shown, you can select the data to be displayed in the picture by
using a trend basket. When the trend basket is closed, the selected trends are
displayed in the trend picture.
The trend display configuration includes a set of parameters (colors, fonts and so
on), which are called the trend preconfigurations. You can create, delete or apply an
existing preconfiguration to the trend picture shown.
10.2. Copying the trends

In Trend Display, you can copy the selected trend items from the tabular or graphical
view to the clipboard of the operating system. In the graphical view, there are
usually several trend items that are included in the selection to be copied. When you
paste the selection to the clipboard, the data is divided into several sections, where
each section has a header and contents of each selected trend item.
10.3. Exporting trends to the .csv or .txt file

In Trend Display, you can export the selected trend item from the tabular or
graphical view to a .csv or .txt file. You can choose the file name and folder in the
Save As dialog.
When you select a rectangular region in the graphical view, the graph is zoomed
automatically. To enable other selection mechanisms than zooming in the graphical
view, you need to change the modes of the graphical view. The following modes and
submodes are available:
Table 10.3.-1 Modes and submodes of Trend Display

Mode Sub-mode Functionality
Panning No Trend data in the graphical view is panned according to
the mouse movements.
Selection Auto-zooming Trend data in the graphical view is zoomed
enabled automatically according to the mouse selection.
Selection Auto-zooming Trend data in the graphical view is selected according to
disabled the mouse selection. There is no automatic zooming,
instead the selection is indicated to be either copied to
the clipboard or exported to a file.
You can zoom or pan easily by using the keyboard and mouse:
Panning: ALT + left-click the mouse + move the mouse

Zoom selection: CTRL + left-click the mouse + drag the mouse to the selected area
Zooming in: CTRL + left-click the mouse
Zooming out: CTRL + SHIFT + left-click the mouse
The selection mode policy, whether the auto-zooming is enabled or disabled is
defined in the toggle toolbar button. It is enabled by default.
160
Application Design
10.4. Trend Display parameters

The Trend Display has a set of parameters, such as the number of data logs and the
maximum length of data logs that can be changed if required. These parameters are
stored in the text file:
\sc\sa_lib\base\bbone\use\bgu_ta_setup.txt.
You can edit the file by using the SCIL Editor of the MicroSCADA Base Tools. The
parameters are stored as SCIL variables. Therefore, ensure that the file syntax is
correct when editing a file. The syntax can be checked, for example, by using the
Check Syntax option of the SCIL Editor.
The parameters are described in the following table:
Table 10.4.-1 Parameter descriptions

Parameter Description
Number of Datalog The number of data logs created for the trends, that is, the
maximum number of process objects that can be logged at the
same time. The maximum value of this attribute depends on
the size of the system and the hardware used, and it should be
found out experimentally.
Max Length of Datalogs The maximum number of registrations in one data log, that is,
the maximum number of history values stored for one process
object. The maximum value of this attribute is 65535.
The number and maximum length of the data logs used in the Trend Display are
application-specific parameters. Their effect on the system performance should
always be measured by using the actual hardware. Too large values of these
parameters may cause poor system performance.
After changing one of the parameters, restart the Trend Display and delete the
existing data logs. After this, the changes take effect.
The following two data log ASCII files are used in the Trend Display:
• \sa_lib\base\bbone\use\bgu_ta_setup.txt
• \sc\sa_lib\base\bbone\Lang<*>\bgu_ta_objec.txt
Both files are used in the Trend Display to create and initialize necessary application
objects. Marking <*> refers to the current application language number.
10.5. Application objects

Trend Display in the MicroSCADA Monitor Pro application uses the same
application objects as LIB 510 Trend Picture. The objects include a set of Data
Objects and Time Channels. All the needed application objects are created when the
Trend Display is started for the first time. If the full set of needed objects exist before
the first Trend Display start-up, the objects are not updated. To reinitialize the
objects completely, delete the old objects and restart the Trend Display.
10.5.1. Data objects

Trend Display uses data objects named FTU_TRD*, where * means 1 to the
maximum number of trends. The default trend number is 20
(NUMBER_OF_DATALOGS parameter of the bgu_ta_setup.txt file).
161
Application Design
10.5.2. Time channels

Trend Display uses the following time channels:
• FTU_TRT30 (time channel for 30 seconds time interval)
• FTU_TRT60 (time channel for 1 minute time interval)
• FTU_TRT120 (time channel for 2 minutes time interval)
162
Application Design
11. Localization of application

Texts’ translantions are included in the SYS 600 Visual SCIL Objects Manual, for
example the button labels and menu texts are normally defined by using the Dialog
Editor and stored in the same objects. For more information on using language
dependent texts, refer to the SYS 600 Visual SCIL Application Design Manual.
Other application texts’ translations, for example texts describing process objects
and their states, are stored in the text databases. The texts are translated explicitly by
the TRANSLATION function, or usually implicitly by referencing the object’s
language sensitive attribute. These texts are translated by the Text Translation Tool.
To save the translation, you can use a Windows based localization tool, such as
RCWinTrans, Multilizer or Lingobit Localizer. For example, the Lingobit Localizer
can be downloaded from http://www.lingobit.com/.
11.1. Language identifiers

It is recommended, but not required, that the two letter language identifiers, which
are used in the applications, are defined by the ISO standard 639.
When ISO 639 language identifiers are used, the system is able to map the Windows
language ID's, which are derived from the Windows locale ID's, to the language
identifiers of the MicroSCADA applications. Consequently, the OPC clients
connected to the MicroSCADA OPC Data Access Server may define their language
by the means specified in the OPC standard. The MicroSCADA base system
automatically converts the Windows language ID’s to the ISO 639 language
identifiers. For more information on using language functions, refer to the SYS 600
Programming Language SCIL Manual.
11.2. Text Translation Tool

In the MicroSCADA application, there is a large amount of language dependent text,
which has to be translated. The Text Translation Tool can be used to translate the
MicroSCADA system’s different file formats. For more information on using Text
Translation Tool, refer to the SYS 600 System Administration Manual.
11.3. Text databases

The translations of application texts are stored in data files called the text databases.
The databases have three different scopes for different needs of software
components using translated texts:
1. The application text database, APL_TEXT.sdb, is designed to contain the site
specific texts of the application.
2. The text databases listed by the application attribute, APL:BTD, are used by
various software products, such as LIBxxx products and their localizations.
3. The system text database, SYS_TEXT.sdb, is delivered with the MicroSCADA
Pro based software and should not be modified.
163
Application Design
The databases are searched in the scope order, APL_TEXT.sdb first and
SYS_TEXT.sdb last.
It is not allowed to modify SYS_TEXT.sdb by any tool or SCIL

programming language. A later version of SYS 600 always overrides
this file.
11.4. Monitor Pro, tools and components

Monitor Pro and some other SYS 600 components use the satellite resource
Dynamic Linking Libraries (.dll) to store resources. In this method, each supported
language has its resources in a separate dll. Each dll uses the same resource
identifiers, but also contains strings in the appropriate language.
Each dll’s name and directory indicates the language of its resources. For example,
Monitor Pro has executable \sc\prog\sa_lib\FrameWindow.exe, which loads its EN
resources from \sc\prog\sa_lib\EN\FrameWindow_EN.dll. These language dlls can
be translated by using a third party software.
Table 11.4.-1 The dlls that can be translated

Dll name (default installation path
Description
c:\sc\prog\sa_lib\en)
Alarmctl_en.dll Resources for the alarm list
Basket_texts.dll Resources for the trend basket1
Blockingctl_en.dll Resources for the blocking list
BusbarColoring_en.dll Resources for the busbar coloring
ControlDialog_en.dll Resources for the control dialogs
Eventctl_en.dll Resources for the event list
FrameWindow_en.dll Resources for the Monitor Pro
LIB510RelayTools_en.dll Resources for the LIB 510 relay tool launcher
MSCGraph_texts.dll Resources for the graph control1
Options_en.dll Resources for the option dialog
TrendApp_texts.dll Resources for the trend display1
1. These dll files do not need the language id as part of their name.
11.5. Basic workflow of localization

All the separate tasks listed below are not needed, but they are recommended to get
the whole Operator user interface translated for the selected MicroSCADA Pro
based application.
• SYS 600 system tools’ translation. All SYS 600 tools (\sc\stool\), which Operator
uses daily, need to be translated either by using Visual SCIL Editor or Text
Translation Tool.
• If the application is LIB 500 based, the LIB 500 and other needed LIBxxx based
applications needs to be translated by using Text Translation Tool.
• Translate Monitor Pro, tools and its components.
164
Application Design
Translating the SYS 600 System Texts:
1. Shutdown MicroSCADA Pro.

2. Copy the \sc\sys\active\sys_\sys_text.sdb to your application folder, for example
C:\sc\apl\tutor\apl_ and give it some meaningful name such as SYST_DE.sdb.
3. Define the new language database file for the application object. Modify the
application creation routine C: \sc\sys\active\sys_\sys_bascon.com, in a way
that it includes the definition for the new added text database file.
For more detailed information about attribute text databases, refer to SYS 600
System Object Manual.
The following example shows how the application creation code could look like:
#CREATE APL:V = LIST(-
TT = "LOCAL",- ;Translation Type
NA = "TUTOR",- ;Name of application directory
AS = "HOT",- ;Application state (COLD,WARM,HOT)
PH = %l_Global_Paths,-
TD = VECTOR("APL_/SYST_TEXT_DE.SDB","APL_/SYST_TEXT_FI.SDB"),-
; Text databases
-; PQ = 15,- ;Number of parallel queues/ Needed in COM500 Applications
-; QD = (1,1,0,0,0,0,1,1,1,1,1,1,1,1,1),-
;Parallel queue dedication/ Needed in COM500 Applications
SV = %SV,- ;System variable (RESERVED)
CP = "SHARED",- ;Color Allocation Policy
-; RC = VECTOR("FILE_FUNCTIONS_CREATE_DIRECTORIES"),-
;Revision compatibility
HP = "DATABASE",- ;History Logging Policy ("DATABASE", "EVENT_LOG", "NONE")
EE = 1,- ;System Events & Operating System Events (1=Enabled, 0=Disabled)
AA = 1,- ;Number of APL-APL servers
MO = %MON_MAP,- ;Monitor mapping
PR = (1,2,3)) ;Printer mapping
#CREATE APL1:B = %APL
4. Start up the MicroSCADA Pro and open the Visual SCIL monitor.
5. Open the Text Tool by using the Tool Manager and open the defined APL_/
SYST_DE.sdb.
The APL_/SYS_TEXT_DE.SDB can be opened by selecting File > Open and
navigating to correct object in the appearing dialog, see Fig. 11.5.-1.
165
Application Design
TextTool_Browsing
Fig. 11.5.-1 File Navigator dialog

For more information on how to use Text Tool, refer to the System Administration
Manual.
6. Close the MicroSCADA Pro and modify the application language:
#CREATE APL:V = LIST(-
TT = "LOCAL",- ;Translation Type
NA = "TUTOR",- ;Name of application directory
AS = "HOT",- ;Application state (COLD,WARM,HOT)
PH = %l_Global_Paths,-
TD = VECTOR("APL_/SYST_TEXT_DE.SDB","APL_/SYST_TEXT_FI.SDB"),-
; Text databases
LA = "DE",-
-; PQ = 15,- ;Number of parallel queues/ Needed in COM500 Applications
-; QD = (1,1,0,0,0,0,1,1,1,1,1,1,1,1,1),-
;Parallel queue dedication/ Needed in COM500 Applications
SV = %SV,- ;System variable (RESERVED)
CP = "SHARED",- ;Color Allocation Policy
-; RC = VECTOR("FILE_FUNCTIONS_CREATE_DIRECTORIES"),-
;Revision compatibility
HP = "DATABASE",- ;History Logging Policy ("DATABASE", "EVENT_LOG", "NONE")
EE = 1,- ;System Events & Operating System Events (1=Enabled, 0=Disabled)
AA = 1,- ;Number of APL-APL servers
MO = %MON_MAP,- ;Monitor mapping
PR = (1,2,3)) ;Printer mapping
#CREATE APL1:B = %APL
If the system tools are translated by using Visual SCIL Editor, all
changes are lost when installing a later version of SYS 600.
166
Application Design
11.6. Basic work flow in translating Monitor Pro, tools and

components
Here is an example on how to use the Lingobit Localizer in translation. When you
start the Lingobit Localizer, it creates a new project or loads an existing project
automatically. The c:\data project location is used in the example below.
1. Fill in the Name field with the project name and click Browse to find the project
location, see Fig. 11.6.-1.
A050016
Fig. 11.6.-1 Main window of the Localizer and the Project Wizard dialog
2. Click Next to open the list of dll files, see Fig. 11.6.-2.
3. Click Add if you want to add more files, and Remove if there are unnecessary
files on the list.
A050007
Fig. 11.6.-2 List of dll files to be translated
167
Application Design
4. Click Next to open the dialog for selecting the languages, see Fig. 11.6.-3.
5. Select the original language from the drop-down list and click Add to select the
target language.
A050008
Fig. 11.6.-3 Selecting the original and target languages

6. Click Next to open the list of dll files in the application window. The list is
shown on the left side of the window, see Fig. 11.6.-4.
A050009
Fig. 11.6.-4 List of dll files in the application window

7. Click the dll files to see the strings to be translated. The resources are collected
to a string table, and all the strings in each table should be translated, see
Fig. 11.6.-5.
168
Application Design
A050010
Fig. 11.6.-5 String table in the application window

8. Click the string you want to translate and type in the translation in the language
column. The strings that are not translated use the original language, see Fig.
11.6.-6.
169
Application Design
A050011
Fig. 11.6.-6 EN translation in the application window

9. When you have done the translations, save them by selecting Edit >Save.
10.To generate the dll files, open the Language to export dialog by selecting
Project > Create Localized Files, see Fig. 11.6.-7.
11. Select the language to which the dll files are generated to and click OK.
170
Application Design
A050014
Fig. 11.6.-7 Generating the translation

12.You can find the translated dll files where the project was created, which is
c:\data\SYS600 in this example, see Fig. 11.6.-8. Depending on your project
setup and the generated languages, there is a directory for each language. As
only Finnish language was generated in this example, there is only one
subdirectory in the project structure c:\data\SYS600\Finnish-Finland.
A050015
Fig. 11.6.-8 Contents of the localized files

13. When you have generated the files, they should be copied from the project
directory to c:\sc\prog\sa_lib\FI and renamed according to the following table.
171
Application Design
Table 11.6.-1 Renamed dll files

DLL name (default installation path New name, if translated to "Finnish-
c:\sc\prog\sa_lib\en) Finland"
Alarmctl_en.dll Alarmctl_fi.dll
Basket_texts.dll Basket_texts.dll1
Blockingctl_en.dll Blockingctl_fi.dll
BusbarColoring_en.dll BusbarColoring_fi.dll
ControlDialog_en.dll ControlDialog_fi.dll
Eventctl_en.dll Eventctl_fi.dll
FrameWindow_en.dll FrameWindow_fi.dll
LIB510RelayTools_en.dll LIB510RelayTools_fi.dll
MSCGraph_texts.dll MSCGraph_texts.dll1
Options_en.dll Options_fi.dll
TrendApp_texts.dll TrendApp_texts.dll1
1. These dll files do not require the language id as part of they name.
It is not allowed to modify anything else but the strings in the

resource dll files.
11.7. Using new language in Monitor Pro
LIB 500 based application

In Monitor Pro, the operator language is based on the current user language. The user
language can be changed from the User Management Tool and taken into use in the
next login.
SYS 600 based application

If there is no user management in the application, the current user language is the
same as the application language. This needs to be set in SYS_BASCON.com, refer
to the code example in Section 11.5. Basic workflow of localization.
172
Application Design
12. Index
A
Action Blockings .................................................................................... 158
Advanced Condition ............................................................................... 149
Advanced Condition dialog .................................................................... 154
Alarm Blockings ..................................................................................... 158
alarm buffer preconfiguration ................................................................. 154
alarm limit violation ............................................................................... 155
Alarm List
alarm classes ..................................................................................... 154
attribute keywords ............................................................................ 154
column key names ............................................................................ 154
column layout template .................................................................... 152
customizing columns ........................................................................ 152
layout.ini file ..................................................................................... 153
limit value supervision ..................................................................... 155
alarm text line ......................................................................................... 151
ALARMING_STATE_OF_ SIGNAL’nr’ ............................................. 114
ALARMING_STATE_OF_SIGNAL’x’ .................................................. 88
ALARMING_STATE_OF_SIGNAL1 .................................................... 89
APL_TEXT.SDB .................................................................................... 163
application objects .................................................................................... 37
AR_WITH_MULTIPLE_ CYCLES ...................................................... 115
Attributes .............................................................. 48, 53, 61, 66, 67, 73, 91
AUTHORIZATION_GROUP 48, 50, 53, 55, 60, 62, 72, 74, 80, 82, 88, 89,
105
AUTO_MANUAL_ID_TYPE ............................................................... 113
AUTO_MANUAL_IND_TYPE .............................................................. 72
AUXILIARY_PLUG ................................................................. 60, 62, 112
B
BAY_LR_IN_USE ..................................................................... 53, 55, 107
BAY_LR_POLARITY ........................................................................... 107
BAY_NAME .............................. 53, 55, 60, 62, 72, 74, 79, 82, 87, 89, 106
Binary Input (BI) ...................................................................................... 89
Blocked signal row number .................................................................... 157
C
CMD_PARAMETER ....................................................................... 72, 104
column layout template .......................................................................... 146
Configuration
Of the station picture function ............................................................ 50
Of the switching device ...................................................................... 62
Configuration Data Export Tool ............................................................... 17
configuring complete objects ................................................................... 24
173
Application Design
Control Blockings .................................................................................. 158

CONTROL_BITS ...................................................................... 60, 62, 112
CONTROL_PULSE_LENGTH ................................................. 60, 62, 111
CONTROL_TYPE ..................................................................... 60, 62, 111
creating configuration file ........................................................................ 40
creating display symbols .......................................................................... 42
creating graphical interfaces ................................................................... 123
creating process displays ........................................................................ 123
Customization dialog ............................................................................. 135
Commands tab .................................................................................. 140
Options tab ....................................................................................... 141
Toolbars tab ...................................................................................... 137
D
Data Objects ........................................................................................... 161
daylight saving ....................................................................................... 150
DEVICE_NAME ................................... 60, 62, 72, 74, 80, 82, 87, 89, 107
Dialog Editor .......................................................................................... 163
Display Builder ...................................................................................... 123
DLL ........................................................................................................ 164
Dynamic Linking Libraries .................................................................... 164
E
engineering tools ...................................................................................... 15
Event Blockings ..................................................................................... 158
Event coloring ........................................................................................ 148
Event Conversion Tool ............................................................................ 20
EVENT_RECORDING ................... 48, 50, 53, 55, 60, 62, 80, 82, 88, 106
Export Options ......................................................................................... 18
F
FOLDER_’number_TITLE ...................................................................... 80
FOLDER_’number’_TITLE .................................................................. 113
FOLDER_1_TITLE ................................................................................. 82
FOLDER_2_TITLE ................................................................................. 82
FOLDER_3_TITLE ................................................................................. 82
FOLDER_4_TITLE ................................................................................. 82
G
generator standard function ...................................................................... 97
Generator.sd ............................................................................................. 98
H
HARD_WIRED ..................................................................................... 113
HD - History logging time Daylight saving ........................................... 150
I
IND_DOUBLE_BINARY ......................................................... 53, 55, 105
174
Application Design
INDICATION_TYPE ................................................................. 60, 62, 110

Install Standard Function dialog ............................................................... 38
installing complete objects ....................................................................... 24
installing standard functions ..................................................................... 38
INTERLOCKING_BYPASS ........................................................... 60, 112
IU .............................................................................................................. 40
L
Language identifiers ............................................................................... 163
LBE ........................................................................................................... 24
LIB 5xx application library ...................................................................... 15
Line Indicator H.sd ................................................................................. 100
line indicator standard function .............................................................. 100
Line Indicator.sd ..................................................................................... 100
LINE_INDICATOR_COLORED_BY ................................................... 122
LINK_AR_TAG_TO_LN ...................................................................... 115
LINK_AR_TAG_TO_MODULE .......................................................... 116
LINK_SIGNAL’nr’_TO_IX ............................................................ 88, 115
LINK_SIGNAL’nr’_TO_LN ........................................................... 88, 114
LINK_SIGNAL’x’_IX ............................................................................. 88
LINK_SIGNAL’x’_LN ............................................................................ 88
LINK_TRIP_TAG_TO_ MODULE_x .................................................. 118
LINK_TRIP_TAG_TO_LN_x ............................................................... 117
List Based Engineering ............................................................................. 23
sheets .................................................................................................. 25
List Based Engineering tool ..................................................................... 24
loading last saved layout ........................................................................ 139
LR_REMOTELY_ CONRTOLLABLE ................................................ 107
LR_REMOTELY_CONTROLLABLE ......................... 48, 50, 53, 55, 106
M
MAX_POSIT ............................................................................................ 74
MAX_POSITION ............................................................................. 72, 113
MEAS_’number_DECIMALS ................................................................. 80
MEAS_’number’_DECIMALS .............................................................. 114
MEAS_1_DECIMALS ............................................................................. 82
MEAS_2_DECIMALS ............................................................................. 82
MEAS_3_DECIMALS ............................................................................. 82
MEAS_4_DECIMALS ............................................................................. 82
menu configuration ................................................................................. 137
MicrosSCADA Pro Display Builder ...................................................... 123
MIN_POSIT ............................................................................................. 74
MIN_POSITION .............................................................................. 72, 113
Monitor Pro ............................................................................................ 135
customization .................................................................................... 135
features ............................................................................................. 135
175
Application Design
layout ................................................................................................ 135

MOTORIZED ............................................................................ 60, 62, 110
N
naming convention ................................................................................... 28
NOMINAL_VOLTAGE ........................................................................ 113
O
OA ............................................................................................................ 41
OB ............................................................................................................ 41
object browser .......................................................................................... 42
Object Navigator ...................................................................................... 37
Object Navigator Engineering .................................................................. 24
Object type ............................................................................................... 28
OPC_ITEM_PREFIX ...................................................................... 48, 106
OPC_LN_INSTANCE_1 ................................................................. 80, 114
OPC_LN_INSTANCE_2 ................................................................. 80, 114
OPC_LN_INSTANCE_3 ................................................................. 80, 114
OPC_LN_INSTANCE_4 ................................................................. 80, 114
OPC_LN_INSTANCES ................................................................... 48, 106
Other tab ................................................................................................... 41
OUTPUT_STATUS ............................................................................... 105
P
P_OBJECT_LN .............. 48, 50, 53, 55, 60, 62, 72, 74, 80, 82, 87, 89, 103
Palette window ......................................................................................... 42
Printout Blockings .................................................................................. 158
process object attributes ........................................................................... 40
Process Object Tool ................................................................................. 48
Existing tab ................................................................................... 40, 41
New tab .............................................................................................. 40
starting ................................................................................................ 40
Process objects ......................................................................................... 80
Q
QUALIFIERS ........................................................................................ 113
R
resetting layout ....................................................................................... 141
RX attribute ............................................................................................ 108
S
SA-LIB ..................................................................................................... 38
SCIL Editor ............................................................................................ 161
SCIL variables ........................................................................................ 161
SCL import function ................................................................................ 43
SCL Importer tool .................................................................................... 43
SHOW_AR_IN_USE ............................................................................. 115
176
Application Design
SHOW_AR_NOT_IN_USE ................................................................... 115

Signal text ............................................................................................... 157
signal text line ......................................................................................... 157
SIGNAL’nr’_TEXT ............................................................................... 114
SIGNAL’x’_TEXT ................................................................................... 88
SIGNAL1_TEXT ..................................................................................... 89
Source directory ........................................................................................ 18
SS .............................................................................................................. 40
Standard Configuration Tool ........................................................ 48, 53, 79
Standard Function Tool ............................................................................ 40
attributes ............................................................................................. 40
Attributes tab ...................................................................................... 41
Tools tab ............................................................................................. 41
standard functions ..................................................................................... 38
STATION_LR_IN_USE ............................................................ 48, 50, 105
STATION_NAME ......... 48, 50, 53, 55, 60, 62, 72, 74, 79, 82, 87, 89, 103
STATION_TYPE ........... 48, 50, 53, 55, 60, 62, 72, 74, 80, 82, 88, 89, 104
Substation Automation library ................................................................. 38
SWICHING_DEVICE_ PURPOSE ....................................................... 108
SWICHING_DEVICE_TYPE ............................................................... 108
SWITCH_SECTION .................................................................. 60, 62, 109
Switching state (SS) ....................................................................... 106, 107
SWITCHING_DEVICE_PURPOSE ................................................. 60, 62
SWITCHING_DEVICE_TYPE ......................................................... 60, 62
SYNCHROCHECK_BYPASS ........................................................ 60, 112
SYS 600 Event List ............................................................................ 15, 19
SYS_TEXT.SDB .................................................................................... 163
system objects ........................................................................................... 37
T
Text databases ........................................................................................ 163
Text Translation Tool ............................................................................. 163
Time Channels ........................................................................................ 161
toolbar configuration .............................................................................. 137
Toolbars tab
changing visibility ............................................................................ 137
creating new toolbar ......................................................................... 138
naming new toolbar .......................................................................... 138
renaming and deleting new toolbar .................................................. 139
TRANSFORMER_TYPE ........................................................... 72, 74, 113
TRANSLATION function ...................................................................... 163
Trend Application ................................................................................... 159
trend basket ............................................................................................. 160
Trend Display ......................................................................................... 159
Trend display configuration ................................................................... 160
trend picture ............................................................................................ 160
177
Application Design
trend preconfiguration ............................................................................ 160

Trend Reports ......................................................................................... 159
TYPE_MEAS_’number’ .................................................................. 80, 113
TYPE_MEAS_1 ....................................................................................... 82
TYPE_MEAS_2 ....................................................................................... 82
TYPE_MEAS_3 ....................................................................................... 82
TYPE_MEAS_4 ....................................................................................... 82
TYPE_OF_SIGNAL’nr’ .................................................................. 88, 114
TYPE_OF_SIGNAL’x’ ........................................................................... 88
TYPE_OF_SIGNAL1 .............................................................................. 89
U
UN ............................................................................................................ 41
Update Blockings ................................................................................... 158
V
VBA ......................................................................................................... 25
Visual BASIC for Applications ............................................................... 25
178
1MRS755387 EN 02.2005
ABB Oy
Substation Automation Products
P.O. Box 699
FI-65101 Vaasa
FINLAND
Tel. +358 10 22 11
Fax. +358 10 224 1094
www.abb.com/substationautomation

SYS600 Application Design

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

SYS600 Application Design

Caricato da

Copyright:

Formati disponibili

MicroSCADA Pro

SYS 600 *9.1

1. About this manual ...................................................................11

©Copyright 2005 ABB Oy, Substation Automation Products, Vaasa, FINLAND 3

3.2.1.2. Installation and configuration of standard

4.4.3.6. Other text files ....................................................56

4.7.1. Standard function installation .......................................... 78

4.9.2.7. Scale objects ......................................................94

4.13.Descriptions to the configurable attributes ............................... 103

10.3.Exporting trends to the .csv or .txt file ......................................160

1. About this manual

1.4. Use of symbols

The warning icon indicates the presence of a hazard which could

The caution icon indicates important information or warning related

The information icon alerts the reader to relevant facts and

1.5. Document conventions

• System prompts/messages and user responses/input are shown in the Courier

1.7. Related documents

Name of the manual MRS number

1.8. Document revisions

Version Revision number Date History

2. Migrating an existing MicroSCADA application

2.1. Introduction to migration tools

LIB 5xx application MicroSCADA Pro

Fig. 2.1.-1 Migrating process

Fig. 2.1.-2 Event conversion process

2.2. Exporting information from pictures to data files

2.2.1. Configuration Data Export Tool

2.2.1.1. Starting Configuration Data Export Tool

Fig. 2.2.1.1.-1 Configuration Data Export Tool icon

Fig. 2.2.1.1.-2 Main view of the tool

Fig. 2.2.1.2.-1 Export Options

2.2.1.3. Exporting picture data

2.3. Event conversion

2.3.1. Event Conversion Tool

2.3.1.1. Starting Event Conversion Tool

Fig. 2.3.1.1.-1 Icon for opening Event Conversion Tool

Fig. 2.3.1.1.-2 Main view of Event Conversion Tool

2.3.1.2. Making conversion

It is recommended to take a backup from the application (process

3. Creating new MicroSCADA Pro application with

From the two different engineering approaches, the Object

List based engineering

Fig. 3.-1 List based engineering approach

Object Navigator engineering

Fig. 3.-2 Object Navigator engineering approach

3.1. List Based Engineering tool

3.1.1. System Requirements

3.1.2. Using the tool

3.1.3. Create sheet

Fig. 3.1.3.-1 Create sheet

Table 3.1.3.1-1 Naming convention columns

Table 3.1.3.1-2 Object type columns

3.1.3.2. User interface components

Table 3.1.3.2-1 Buttons in Create sheet

Table 3.1.3.2-1 Buttons in Create sheet

3.1.3.3. Tips for using Create sheet

3.1.3.4. Exception handling in Create sheet

Fig. 3.1.3.4.-1 Cannot connect to OPC server

Fig. 3.1.3.4.-2 Cannot create command procedure

Fig. 3.1.3.4.-3 Cannot get attributes

Fig. 3.1.3.4.-4 Config data file is not recognized as a SA-LIB file

Fig. 3.1.3.4.-5 No bay designation

Fig. 3.1.3.4.-6 Cannot find application path