1MRS751886-MEN
Issued:
15.03.2002
Version:
A
Program revision: 4.0.4
We reserve the right to change data without prior notice.
LIB 510 Configuration
Configuration Guide
LIB 510
Notice 1
The information in this document is subject to change without notice and should not
be construed as a commitment by ABB. ABB assumes no responsibility for any error
that may occur in this document.
Notice 2
This document complies with the program revision 4.0.4.
Notice 3
Additional information such as Release Notes and Last Minute Remarks can be
found on the program distribution media.
Trademarks
Microsoft is a registered trademark of Microsoft Corporation.
Windows NT is a trademark of Microsoft Corporation.
L
ON
W
ORKS
is a registered trademark of Echelon Corporation.
Other brand or product names are trademarks or registered trademarks of their respective holders.
All Microsoft products referenced in this document are either trademarks or registered trademarks of Microsoft
Corporation.
MicroSCADA Technology Manuals
SYS 500 manuals
COM 500 manuals
Application Objects
1MRS751848-MEN
Introduction to MicroSCADA Technology
1MRS751852-MUM
JAVA-API for MicroSCADA
1MRS751851-MEN
Programming Language SCIL
1MRS751849-MEN
SCIL-API for MicroSCADA
1MRS752199-MEN
Status Codes
1MRS751850-MEN
System Configuration
1MRS751846-MEN
System Objects
1MRS751847-MEN
Configuring MicroSCADA for OPC DA Client
1MRS752246-MEN
Installation
1MRS751853-MEN
Picture Editing
1MRS751854-MEN
System Management
1MRS751857-MEN
Visual SCIL Objects
1MRS751856-MEN
Visual SCIL User Interface Design
1MRS751855-MEN
COM 500 Engineering
1MRS751858-MEN
Connecting LONWORKS Devices to MicroSCADA
1MRS751845-MEN
Communication Programming Interface (CPI)
1MRS751859-MEN
Configuring MicroSCADA for DNP V3.00 Master Protocol
1MRS751860-MEN
Configuring MicroSCADA for DNP V3.00 Slave Protocol
1MRS751861-MEN
Configuring MicroSCADA for IEC 60870-5-101 Master Protocol
1MRS751862-MEN
Configuring MicroSCADA for IEC 60870-5-101 Slave Protocol
1MRS751863-MEN
Configuring MicroSCADA for IEC 60870-5-103 Master Protocol
1MRS752012-MEN
Configuring MicroSCADA for IEC 60870-5-104 Master Protocol
1MRS751964-MEN
Configuring MicroSCADA for IEC 60870-5-104 Slave Protocol
1MRS751965-MEN
Configuring MicroSCADA for Modbus Master Protocol
1MRS752242-MEN
Configuring MicroSCADA for Modbus Slave Protocol
1MRS751864-MEN
LIB 510
LIB 510 Configuration Manual
Configuration Guide
1MRS751886-MEN
LIB 500 manuals
LIB 510 manuals
SMS 510 manuals
CAP 505 manuals
Common manual for LIB, CAP and SMS
LIB 500 Configuration Manual
1MRS751880-MEN
LIB 500 Operator’s Manual
1MRS751885-MUM
LIB 510 Configuration
1MRS751886-MEN
LIB 510 MV Process Configuration
1MRS751887-MEN
LIB 510 MV Process Operator’s Manual
1MRS751891-MUM
LIB 510 Operator’s Manual
1MRS751888-MUM
SMS 510 Installation and Commissioning
1MRS751897-MEN
SMS 510 Operator’s Manual
1MRS751898-MUM
CAP 505 Installation and Commissioning
1MRS751901-MEN
CAP 505 Operator’s Manual
1MRS751902-MUM
Relay Configuration Tool Tutorial
1MRS751903-MEN
Relay Mimic Editor Configuration
1MRS751904-MEN
Relay Configuration Tool Quick Start Reference
1MRS751905-MEN
SPTO Configuration Tool
1MRS751906-MEN
Protocol Editing Tool
1MRS751982-MUM
Tools for Relays and Terminals
1MRS752008-MUM
1MRS751886-MEN
LIB 510 Configuration Manual
LIB 510
Configuration Guide
1
2
3
4
5
6
7
1
2
3
4
5
6
Guideline for substation engineering with LIB 510
7
Fault Report Function in LIB 510
LIB 510
LIB 510 Configuration Manual
Configuration Guide
1MRS751886-MEN
LIB 510
Contents
Configuration Guide
Contents:
1. Introduction ............................................................................... 1
1.1.1. Preferences........................................................................ 1
1.1.2. Abbreviations and Definitions ............................................ 1
1.1.3. Font conventions................................................................ 2
1.2. Fundamental concepts.................................................................. 2
2. Installation of LIB 510 ............................................................... 5
2.1. System requirements .................................................................... 5
2.1.1. MicroSCADA PC ................................................................ 5
2.1.1.1. The LIB 510 product package .............................. 5
2.1.2. Installation .......................................................................... 5
2.1.2.1. Installation of MicroSCADA software ................... 5
2.1.2.2. Installation of the LIB 510 Product Package ........ 6
2.1.3. Location of the LIB 510 software packages ..................... 11
3. Overview of Event Editor........................................................ 13
3.1.1. Main menu ....................................................................... 14
3.1.2. Toolbar ............................................................................. 15
3.1.3. Event notebook ................................................................ 15
3.1.4. Status bar......................................................................... 16
3.2. Start-up ....................................................................................... 16
3.3. Functions..................................................................................... 17
3.3.1. Process object handling................................................... 17
3.3.1.1. Editing event texts.............................................. 17
3.3.1.2. Creating process objects.................................... 17
3.3.1.3. Deleting process objects .................................... 18
3.3.1.4. Sending mask .................................................... 18
3.3.2. Template management .................................................... 19
3.3.2.1. Event templates ................................................. 19
3.3.3. Printout............................................................................. 20
3.3.4. Selecting event filter......................................................... 22
4. Trend ........................................................................................ 25
4.1. Trend report setups..................................................................... 26
4.2. Preparing trend picture preconfigurations ................................... 27
4.3. Making a menu item of a trend preconfiguration......................... 28
5. Measurement reports 2........................................................... 33
1MRS751886-MEN
LIB 510 Configuration
1MRS751886-MEN
LIB 510 Configuration
LIB 510
Contents
Configuration Guide
5.1. Overview and description ........................................................... 33
5.1.1. Features/options .............................................................. 33
5.2. General description of reports .................................................... 35
5.3. Report preparations .................................................................... 36
5.3.2.1. Defining process objects.................................... 36
5.3.2.2. Defining network printer..................................... 37
5.3.2.3. Application specific definitions (reports) ............ 38
5.3.3. Report configuration ........................................................ 39
5.3.3.1. Report object settings ........................................ 39
5.3.3.2. Execution delays................................................ 50
5.3.3.3. User-defined groups and procedures ................ 50
5.3.3.4. Call-back procedure for sampling cycle............. 50
5.3.3.5. Call-back procedure for period cycle ................. 50
5.4. Picture function installation ......................................................... 50
5.4.1. General ............................................................................ 50
5.4.2. Report picture configuration ............................................ 52
5.4.2.1. Hourly report base picture function.................... 52
5.4.2.2. Daily report base picture function ...................... 55
5.4.2.3. Weekly report base picture function .................. 57
5.4.2.4. Monthly report base picture function.................. 59
5.4.2.5. Yearly report base picture function .................... 61
5.4.3. Report column configuration............................................ 63
5.4.3.1. Report column settings ...................................... 63
5.4.3.2. An example of the report column settings ......... 66
5.5. Miscellaneous ............................................................................. 68
5.5.1. Summer time - normal time ............................................. 68
5.5.2. Troubleshooting ............................................................... 69
5.5.3. General data reading and writing procedures.................. 70
5.5.3.1. Data reading and writing procedures................. 70
5.5.3.2. Procedures ........................................................ 71
5.5.3.3. Interface for sampled values.............................. 71
5.5.3.4. Interface for period values ................................. 72
5.6. Application engineering information............................................ 73
5.6.1. Picture modifications ....................................................... 73
5.6.2. Colour definitions ............................................................. 73
5.6.3. Picture setup.................................................................... 73
5.6.4. Menu configuration for reports......................................... 74
5.6.5. Quick report picture configuration.................................... 74
1MRS751886-MEN
LIB 510
Contents
LIB 510 Configuration
Configuration Guide
5.6.6. Automatic report printing .................................................. 75
5.6.7. Files in the measurement reports 2 ................................. 76
5.6.7.1. Pictures .............................................................. 76
5.6.7.2. Other files........................................................... 76
5.6.7.3. Language text files ............................................. 78
5.6.7.4. Help text files...................................................... 79
5.6.7.5. Configuration files .............................................. 80
5.6.7.6. The process objects ........................................... 81
5.6.7.7. Command procedures........................................ 81
6. Guideline for the substation engineering with LIB 510 ....... 85
6.1. Installation of picture functions.................................................... 87
6.1.1. Main principles ................................................................. 87
6.1.2. Installation procedure....................................................... 88
6.1.3. Static picture background editing ..................................... 92
6.2. Configuration............................................................................... 92
6.2.1. Preliminary work .............................................................. 93
6.2.1.1. The object identification in the database............ 93
6.2.1.2. The object identification in the application ......... 95
6.2.1.3. The naming convention of the database ............ 95
6.2.1.4. Application language.......................................... 96
6.2.3.1. Starting standard configuration tool ................... 96
6.2.4. Representation tool .......................................................... 98
6.2.5. Process object tool........................................................... 98
6.2.6. Installing and configuring SPACOM relay picture functions..
99
6.2.6.1. Installing relay picture functions ......................... 99
6.2.6.2. Relay picture function configuration ................. 100
6.2.6.3. Standard configuration tool functions............... 101
6.2.6.4. Relay parametrisation ...................................... 104
6.2.7. Installing and configuring REx terminal picture functions 104
6.2.7.1. Installing terminal picture functions .................. 105
6.2.7.2. Terminal picture function configuration ............ 105
6.2.7.3. Standard configuration tool functions............... 106
6.2.7.4. Terminal parametrisation ................................. 110
6.2.8. Single line editing ........................................................... 110
6.2.9. Menu configuration ........................................................ 113
6.2.10.Control authority............................................................. 115
6.3. Example of standard function configurations ............................ 116
6.3.1. General .......................................................................... 116
1MRS751886-MEN
LIB 510 Configuration
LIB 510
Contents
Configuration Guide
6.3.1.1. Base................................................................. 116
6.3.1.2. Station.............................................................. 116
6.3.1.3. Bay................................................................... 117
6.3.1.4. Switching Device ............................................. 117
6.3.1.5. Transformer ..................................................... 118
6.3.1.6. Transformer measurements ............................ 119
6.3.1.7. Measurements ................................................. 119
6.3.1.8. Trip tag............................................................. 121
6.3.1.9. Auto reclose tag............................................... 122
6.3.1.10.Alarm indicator................................................. 122
6.3.1.11.SPACOM relay ................................................ 123
7. Fault Report Function in LIB 510 ........................................ 125
7.1. General description................................................................... 125
7.2.1. Files and directories ...................................................... 125
7.2.2. Tools .............................................................................. 127
7.2.3. Objects .......................................................................... 127
7.2.4. Pictures.......................................................................... 127
7.3. Fault reports generation............................................................ 128
7.4. Relay specific parameter files ................................................... 129
7.4.1. File syntax ..................................................................... 130
7.4.2. Translatable texts .......................................................... 132
7.5. Configuring signals for report generation.................................. 133
1MRS751886-MEN
LIB 510
1
LIB 510 Configuration
Configuration Guide
1. Introduction
1
1. Introduction
1.1.
Preface
Welcome to the LIB 510 Introduction Configuration Manual. This document gives
you information on how to install, configure, modify and use the different parts in
the LIB 510 product package.
Previous experience of MicroSCADA and LIB 5xx is an advantage when studying
this document.
1.1.1.
Preferences
The following documents are related to this document and the operation of the LIB
510 functions:
• Introduction to MicroSCADA Technology
• Programming Language SCIL
• MicroSCADA Application Objects
You can find information on the SM/RED and SM/SPACOM packages in the Tools
for Relays and Terminals manual.
1.1.2.
Abbreviations and Definitions
Table 1.1.2-1
Abbreviations and definitions
Base picture
Background picture (the base on which standard
functions are installed)
BBONE
Backbone
CMOD
CHPAU modules
DMOD
DEUTA modules
FMOD
FISUB modules
HDB
History Database
HV
High voltage
LAN
Local Area Network
LEC
Local engineering center
LIB 500
Application Library 500, the common platform (Base) for ABB
application engineering within MicroSCADA
LIB 510
Product including FISUB functions
LIB 520
Product including SEAPR functions
LIB 530
Product including CHPAU functions
LON
Local Operating Network
MicroLIBRARY
Application Library, previous to LIB 500
MV
Medium voltage
PC
Production center
Process symbol
Graphical presentation of a standard function in run-time
RMU
Ring Main Unit
1MRS751886-MEN
2
1MRS751886-MEN
LIB 510 Configuration
LIB 510
1. Introduction
Configuration Guide
1.1.3.
Font conventions
Normal text is written with this font and size.
SCIL CODE, SCIL PROGRAMS AND FILE NAMES ARE WRITTEN WITH THIS FONT AND SIZE.
1.2.
Fundamental concepts
1.2.1.
Application engineering
The application engineering is performed by composing LIB 510 standard functions
(see below) to pictures. The objects connected to various functions are created
automatically as the standard functions are included in the pictures.
1.2.2.
Standard functions
The LIB 510 standard functions are standard elements used for the design of
different types of application pictures. A standard function is an ordinary picture
created with the Picture Editor. It may contain almost all picture elements, such as
background, start, update and exit programs, function keys and windows. The only
technical restriction is that a standard function cannot contain picture functions. The
background may be of any size.
In LIB 510, the standard functions are grouped and organised in a menu structure
according to their purpose, (see Fig. 1.2.3.-1).
1.2.3.
Picture functions
The picture functions are functional elements that the application pictures are
composed of (also other picture elements may be included). When a LIB 510
standard function is installed into an application picture, it becomes a picture
function.
A picture function is a part of the application picture although it has its own picture
elements, such as picture background, start, update and exit programs, function keys
and windows. Each picture function is equipped with a name that must be unique
SCT
Standard Configuration Tool
SG
LIB 500 Style Guide
IT
Installation Tool
SLIB
Component library for development of application specific
functions
SMOD
SEAPR modules
SDD
System Design Description
SCS
Substation Control System (a system for monitoring and
controlling a complete substation); in this document
MicroSCADA
TCP/IP
Transmission Control Protocol/Internet Protocol
XMOD
Other LEC specific modules, new modified modules
Base picture
Background picture (the base on which standard
functions are installed)
1MRS751886-MEN
LIB 510
3
LIB 510 Configuration
Configuration Guide
1. Introduction
1
within the picture. A picture function may be repositioned. All elements of a picture
function can be viewed.
)LJ
7KH/,%VWDQGDUGIXQFWLRQPHQXKLHUDUFK\
When a picture is produced on screen, e.g. with the !NEW_PIC command, the start
program of the main picture is executed first, then the start programs of the picture
functions are run in the installation order.
1MRS751886-MEN
LIB 510
5
LIB 510 Configuration
Configuration Guide
2. Installation of LIB 510
2
2.
Installation of LIB 510
Before using the product package LIB 510, the software has to be installed on the
hard disk of the MicroSCADA computer.
2.1.
System requirements
In order to operate, the product package LIB 510 sets the following requirements to
its environment.
2.1.1.
MicroSCADA PC
Base system requirements:
• Personal computer with Intel Pentium
TM
(or higher) processor
• Microsoft Windows NT
TM
Workstation version 4.0
• 64 MB of memory (128 MB recommended)
• Hard-disk space: 500 MB minimum
Display requirement:
• VGA, minimum resolution 1024x768
• Minimum 256 colors
• Minimum refresh frequency 70 Hz
2.1.2.
The LIB 510 product package
• A full installation about 70 MB disk space. Add another 100 MB when installing
the demo application.
2.1.3.
Installation
The installation of LIB 510 consists of two parts:
1) Installing the software:
The installation of the LIB 510 product package means copying files from the
diskette to the hard disk.
2) Installing the Application Library functions:
The installation of the Application Library Standard Function means installation of
objects like a breaker into a process picture, e.g. a single line diagram, using the
MicroSCADA Picture Editor.
Important note:
In order to avoid problems, it is recommended not to have MicroSCADA active
during the installation.
2.1.3.1.
Installation of MicroSCADA software
Before the installation of LIB 510 product package can take place, the user must
make sure that MicroSCADA 8.4.3 and LIB 500 Base software are already installed
on the PC.
1MRS751886-MEN
6
1MRS751886-MEN
LIB 510 Configuration
LIB 510
2. Installation of LIB 510
Configuration Guide
2.1.3.2.
Installation of the LIB 510 Product Package
To install the LIB 510 package from a CD drive to the hard disk, please follow the
steps below. It is assumed that you use some kind of Windows file manager:
Close MicroSCADA if it is active
On the CD, the installation for LIB 510 is found in ..\PROG\LIB_510\
Double click the file with the extension EXE
Follow the instructions on the screen.
The selected LIB 510 software packages are installed on the hard disk of the PC.
Start MicroSCADA
It is also possible to install LIB 510 from the RUN menu by typing the file name and
path:
)LJ ([DPSOHZKHQLQVWDOOLQJ/,%IURPWKH581PHQX
For latest information about name and path for actual release, please refer to the
release notes.
LIB 510 Installation Wizard
This Wizard will guide you through the installation of the LIB 510 4.0.3 Product
package. The installation is started when all selections are made and ‘Start’ is
pressed.
Welcome
A 'Welcome!' dialog is displayed with a short description of the product that you are
about to Install.
1MRS751886-MEN
LIB 510
7
LIB 510 Configuration
Configuration Guide
2. Installation of LIB 510
2
)LJ 7KH:HOFRPHGLDORJRIWKH/,%,QVWDOODWLRQ
System information
If a previous version of LIB 510 has been installed on the computer, a dialog with
system information about the Installed version will be opened. It is now possible to
choose ’Next>>’ to continue the installation or ’Exit’ to stop the installation session.
8
1MRS751886-MEN
LIB 510 Configuration
LIB 510
2. Installation of LIB 510
Configuration Guide
)LJ 7KH/,%LQVWDOODWLRQV\VWHPLQIRUPDWLRQ
Select Functions to be Installed
If you select the Next button, the main dialog of the installation routine, ’LIB 510
Product Installation’, is displayed (see Fig. 2.1.3.2.-3). This dialog gives the
following information:
• All available LIB 510 software packages that can be installed
• Disk space required for each software package separately
• The total disk space required for the installation
• Available disk space on the selected destination drive
• The selected destination drive and a valid destination directory
• A general description of important information.
The selected software packages are installed to the selected destination directory
when 'Start' is pressed. By selecting 'Exit' the 'Exit Dialog' is opened. From this
dialog it is still possible to return to the main installation dialog.
1MRS751886-MEN
LIB 510
9
LIB 510 Configuration
Configuration Guide
2. Installation of LIB 510
2
)LJ 6HOHFWLRQRI/,%VRIWZDUHSDFNDJHVIRULQVWDOODWLRQ
Start installation
The whole installation is started when the ‘Start' button is clicked. At this stage the
copying of selected functions to the destination will be started. The Installation will
also upgrade the 'Product Info' presented in the 'Application Setting' tool of LIB 510.
The product info can also be viewed from the LIB 510 4.0.3 Product Info tool in
Backbone by typing <drive>/lib4/base/bbone/use/lib510r.exe. With this tool the
revisions of the installed LIB 510 software packages can be viewed or saved to a text
file.
The progress bar dialog shows the progress with a percentage value and a graphic
bar. A label text informing what type of product and what files that are copied is
presented above the graphic bar. Pressing the 'Cancel' button will open the 'Exit
installation' dialog with the possibility to stop the copying before it is finished. The
files that already have been copied must be deleted manually.
10
1MRS751886-MEN
LIB 510 Configuration
LIB 510
2. Installation of LIB 510
Configuration Guide
)LJ 7KH/,%LQVWDOODWLRQLVUXQQLQJ
Installation Ready
The installation is complete!
)LJ /,%LQVWDOODWLRQLVUHDG\
The software packages are installed in the following directories:
MV Process
(drive) :/sc/lib4/fmod/mvprocess/inst
(drive) :/sc/lib4/fmod/mvprocess/lang0
(drive) :/sc/lib4/fmod/mvprocess/use
SPA Relay Tool
(drive) :/sc/lib4/fmod/spa_tool/inst
(drive) :/sc/lib4/fmod/spa_tool /lang0
(drive) :/sc/lib4/fmod/spa_tool/use
(drive) :/sc/lib4/fmod/spa_tool/spammi
SM/SPACOM
(drive) :/sc/lib4/fmod/sm_spacom/inst
(drive) :/sc/lib4/fmod/sm_spacom/lang0
(drive) :/sc/lib4/fmod/sm_spacom/use
(drive) :/sc/lib4/fmod/sm_spacom/spacom
(drive) :/sc/lib4/fmod/sm_spacom/spacom/inst
(drive) :/sc/lib4/fmod/sm_spacom/spacom/lang0
1MRS751886-MEN
LIB 510
11
LIB 510 Configuration
Configuration Guide
2. Installation of LIB 510
2
(drive) :/sc/lib4/fmod/sm_spacom/spacom/use
Trend Reports
(drive) :/sc/lib4/fmod/trends/inst
(drive) :/sc/lib4/fmod/trends/lang0
(drive) :/sc/lib4/fmod/trends/use
Measurement Reports2
(drive) :/sc/lib4/fmod/reports2/inst
(drive) :/sc/lib4/fmod/reports2/lang0
(drive) :/sc/lib4/fmod/reports2/use
DR-Collector Tool
(drive) :/sc/lib4/fmod/drct
(drive) :/sc/lib4/fmod/ drct
(drive) :/sc/lib4/fmod/drct
RED Relay Tool
(drive) :/sc/lib4/fmod/red_tool/evtedit
(drive) :/sc/lib4/fmod/red_tool/remmi
(drive) :/sc/lib4/fmod/red_tool/sost
SM/RED
(drive) :/sc/lib4/fmod/sm_red/inst
(drive) :/sc/lib4/fmod/sm_red/rec52x
(drive) :/sc/lib4/fmod/sm_red/ref54x
(drive) :/sc/lib4/fmod/sm_red/rem54x
(drive) :/sc/lib4/fmod/sm_red/rej5xx
(drive) :/sc/lib4/fmod/sm_red/reu5xx
(drive) :/sc/lib4/fmod/sm_red/use
DEMO for LIB 510 4.0.3:
(drive) :/sc/apl/510_403_1
After the installation of LIB 510, you should have a structure as described in the
following chapter.
2.1.4.
Location of the LIB 510 software packages
The LIB 510 software packages are stored on hard disk in the following way:
12
1MRS751886-MEN
LIB 510 Configuration
LIB 510
2. Installation of LIB 510
Configuration Guide
)LJ
/,%GLUHFWRU\VWUXFWXUH
*) The standard directory structure (inst, use, lang0) is available for all functions in
FMOD.
SC
LIB4
BAS E
MV PROCESS
INST
FMOD
SPA_TOOL
SM_SPACOM
DR_TOOL
TRENDS
REPORTS 2
RED TOOL
USE
LANG0
500_403_1
APL
SM_RE D
*
*
*
*
*
DireStru.CNV
1MRS751886-MEN
LIB 510
13
LIB 510 Configuration
Configuration Guide
3. Overview of Event Edi-
tor
3
3.
Overview of Event Editor
Event Editor is a tool used for creating event handling for the relays of SPACOM
and RED 500 series. The main functions of the tool are that:
• The user can edit the event texts shown on the event and alarm lists.
• The user can edit event masks of the relay.
• The user can define which process objects are created for event handling.
• Event masks can be configured separately for each function block or SPACOM
module.
To configure SPA and REF relays, please see SM/SPACOM Configuration and
SM/RED Configuration in the “Tools for relays and Terminals” Manual.
The Event Editor can be started from the Standard Configuration Tool by selecting
Tools/Event Editor and by clicking Open in the dialog box.
)LJ 6WDUWLQJ(YHQW(GLWRUIURPWKH6WDQGDUG&RQILJXUDWLRQ7RRO
3.1.
HSI
The Event Editor is shown in Fig. 3.1.-1 below.
1MRS751886-MEN
14
1MRS751886-MEN
LIB 510 Configuration
LIB 510
3. Overview of Event Edi-
tor
Configuration Guide
)LJ 7KH(YHQW(GLWRU
3.1.1.
Main menu
The following functions can be activated from the main menu:
Table 3.1.1-1
Functions that can be activated from the main menu
Menu
Function
File
Open Template...
Save As Template...
Delete Template…
Send Mask...
Create Process Objects
Delete Process Objects
Page Setup…
Print Setup…
Print…
Exit
Settings
Select Event Filter
Help
About Event Editor
1MRS751886-MEN
LIB 510
15
LIB 510 Configuration
Configuration Guide
3. Overview of Event Edi-
tor
3
3.1.2.
Toolbar
The Toolbar consists of the following buttons:
Table 3.1.2-1
Toolbar buttons
3.1.3.
Event notebook
The function blocks included in the SW configuration of the relay are displayed as
notebook tabs in the Event Editor. Each tab represents the events of the function
block. The events belonging to one process object are combined in one container.
The title of the tab indicates which function block or SPACOM module is chosen
(Fig. 3.1.3.-1). In case of SPACOM, the number of order of the module in object
configuration can be seen in the title.
)LJ
(YHQW1RWHERRNWDEV
The tab layout consists of the following fields:
Button
Functionality
Exit
Open Template
Save As Template
Create Process Objects
Delete Process Objects
Send Mask
16
1MRS751886-MEN
LIB 510 Configuration
LIB 510
3. Overview of Event Edi-
tor
Configuration Guide
Table 3.1.3-1
Fields in the tab layout
3.1.4.
Status bar
The status bar contains fields displaying information about the currently selected
function block (see Fig. 3.1.-1).
Table 3.1.4-1
Fields in the status bar
3.2.
Start-up
On the start-up of the Event Editor, the tool reads the event filter value from the EF
attribute of the STA object created for the relay. The event filter defines which mask
parameters are used for event masking. According to this information, the Event
Editor reads the actual values for mask parameters.
If the relay has already been parametrized with the Relay Setting Tool, the Event
Editor gets the values for the event masks from the file produced by the Relay
Setting Tool. If the relay has not been parametrized yet, the Event Editor uses the
default values for the mask parameters.
E-Code
Displays the E-Code of the event. If several events have the
same event text/meaning, the E-Codes of all these events are
shown in this field.
Static Text (OX)
Displays the text which is written into the OX attribute of the
process object. This text will also be shown on the event and
alarm lists. The text is editable.
Dynamic Text
Displays the dynamic parts of the event texts. On the front of the
editable part of the field, there is a condition when the dynamic
text is used. The condition may be for example Object value or
Alarm Zone.
No
When this option is selected, the process object will not be cre-
ated. The events belonging to the process object will be excluded
from the event handling.
Event
The process object will be created and the events belonging to
the object will be included in the event handling.
Event & Alarm
The process object will be created and the events belonging to
the object will be included both in the event and in alarm han-
dling.
Alarm Class
When Event & Alarm option is selected, the alarm class can be
set.
Use in Mask
By using this selection the user can either prevent or allow the
changes in the event mask.
Name of Template
Indicates the name of the template.
Event Filter
Indicates which event filter is used.
Channel
Shows the channel of the function block
Mask A and Mask B
The title shows the names of the mask parameters e.g. "V101".
The value of the parameter is shown in the field.
1MRS751886-MEN
LIB 510
17
LIB 510 Configuration
Configuration Guide
3. Overview of Event Edi-
tor
3
If the process objects have already been created for the events the Event Editor reads
the mask value from the process objects.
In case you want to use another mask value than the value the tool has defined, you
can select which event filter the Event Editor uses. Notice that the selection of the
event filter does not affect the event filter value in STA:SEF attribute.
By using the mask parameter values the Event Editor has received, it represents the
selection buttons for process object creation. If the event is masked in the mask
parameter, the tool suggests not to create process object for it. The mask can be
changed by selecting the process object to be created or not to be created.
If the event filter has not been defined in STA:SEF, the Event Editor uses the filter
value 0 and will create process objects for all events as default. This means that all
events will be passed to MicroSCADA. However, this may cause an unnecessary
load to the system in some cases. Therefore, it is recommended to select only the
events that are wanted to be included in the event reporting before creating the
process objects.
This applies only to RED relays using LON protocol.
The Event Editor represents the events that logically belong to the one process object
as one group. If you include (or exclude) the events of one group in the event
reporting, it will change the mask for all of the events within the group.
3.3.
Functions
3.3.1.
Process object handling
3.3.1.1.
Editing event texts
The event texts of a process object are divided in a static and a dynamic part. The
static part of the event text is written into the OX attribute of the process object. The
dynamic part is written into the format text file. When the event printout is activated,
the format picture reads the texts from the OX attribute and from the format text file.
The Event Editor represents both texts in fields of their own. Each process object
may have only one Static text. Instead of that there may be several dynamic texts
according to the number of possible states of the process object. On the field of
dynamic texts, the Event Editor represents the condition that corresponds to the
dynamic text.
3.3.1.2.
Creating process objects
The process objects are created according to what has been defined in the Event
Editor.
While creating the process objects, the static event text is stored into OX attribute.
The RI attribute of the process object defines which dynamic texts are to be used.
The Event Editor automatically appends the dynamic texts into the format text file
and creates a cross-reference between process object and dynamic texts by using the
RI attribute.
The logical names of the process objects are formed by using the configurable
attribute LIB_OBJECT_NAME as a base of the logical name. Event Editor adds an
indexing letter to the end of the name. Thus, the LN will be:
LIB_OBJECT_NAME + ’index’, where index = character (A..Z, 1..)
)LJ 6NLSGLDORJ
It is possible that some process objects have already been created by some other
function than the Event Editor. For example, the process objects for the
measurements or position indications are usually created by LIB510 MV process
functions. If the Event Editor detects this kind of overlap it will not allow the user
to create such overlapping process object and suggests the user to select one of the
following options:
• Skip. The tool continues the operation with the next process object.
• Retry. The tool tries to create the same object again. The overlapping object has
to be deleted before the process object can be created.
• Cancel. Cancels the whole operation. The objects that have been created before
cancelling will remain in the process database.
3.3.1.3.
Deleting process objects
Process objects can be deleted by the Delete Process Objects function, which is
available in the File menu and also as a button on the Toolbar. After clicking the
Delete Process Objects option in the File menu or the corresponding button, the
following dialog box (Fig. 3.3.1.3.-1) requesting a confirmation before deleting
objects appears on the screen.
)LJ 'LDORJUHTXHVWLQJFRQILUPDWLRQEHIRUHGHOHWLQJREMHFWV
3.3.1.4.
Sending mask
It may be reasonable to send the mask values to the relay. In this way it is possible
to ensure that only necessary events are coming from the relay. Sending the mask to
the relay can be done with the Relay Setting Tool. The Send Mask dialog is shown
in Fig. 3.3.1.4.-1.
)LJ 6HQG0DVNGLDORJ
3.3.2.
Template management
3.3.2.1.
Event templates
The edited event texts and mask values can be saved as a template and later be used
as a blueprint for new process objects.
When the template is saved, a name has to be given for the template. The data of the
function blocks that are edited before creating the template are added to the
template.
When the template is opened, the data is read for those function blocks that are
defined in the relay configuration. If the configuration contains function blocks that
do not have any data defined in the template, the default values are to be used.
It is possible to add new function blocks to the existing template. While saving the
template, give the name of the template to where the data of the new function blocks
should be added. In that way the new data is appended to the template.
Please note that if there is new data for the function blocks that already exist in the
template, the old data will be overwritten!
Open template...
Opens the dialog where a template can be selected and opened. The dialog is shown
in Fig. 3.3.2.1.-1.
)LJ 2SHQ7HPSODWHGLDORJ
Save as template
Saves current configurations as a template. The name of the template will be entered
in the Save As Template dialog shown in the following figure.
20
1MRS751886-MEN
LIB 510 Configuration
LIB 510
3. Overview of Event Edi-
tor
Configuration Guide
)LJ 6DYH$V7HPSODWHGLDORJ
Delete template
The data structure that holds the data of the selected template is removed. The user
has to select the template he wants to delete and confirm the deletion.
)LJ 'HOHWH7HPSODWHGLDORJ
3.3.3.
Printout
The event configuration created in a tool can be printed to a printer selected by the
user. In the printed document the signals are described from the process database
point of view. The following information is included in the document.
• Date and time of printing
• Identification of the object
• Object type and revision
• Identification of the units/function blocks
• Event mask values for the units/function blocks
• Identification of the process objects
• Address of the process objects (if any)
• Signal texts
• Status texts of the signals
• Identification of the events belonging to the signal in question
• Alarm groups of the signals
In addition the printout function has the following subfunctions.
• Page Setup. Possible to setup the page margins (Top, Left, Bottom, Right)
1MRS751886-MEN
LIB 510
21
LIB 510 Configuration
Configuration Guide
3. Overview of Event Edi-
tor
3
)LJ
3DJH6HWXSGLDORJ
• Print Setup. Setup for the paper as well as for the printer can be defined.
)LJ
3ULQW6HWXSGLDORJ
There are two kinds of printouts available. One is a description of signals and the
other is a summary of the values of the Event Masks (see the following tables).
Table 3.3.3-1
Printout with description of signals
Signals
LN
IX
Object text
Status
text
E-Code
OA
AC
Mask
EAS_Q1_R1A
1
START signal from Io> ->
Reset
EO
6000
1
V101
EAS_Q1_R1A
1
START signal from Io> ->
Activated
E1
6000
1
V101
EAS_Q1_R1A
2
TRIP signal from
Reset
E2
6001
1
V101
EAS_Q1_R1A
2
TRIP signal from Io> ->
Activated
E3
6001
1
V101
EAS_Q1_R1A
3
CBFP signal from Io> ->
Reset
E4
6002
1
V101
EAS_Q1_R1A
3
CBFP signal from Io> ->
Activated
E5
6002
1
V101
22
1MRS751886-MEN
LIB 510 Configuration
LIB 510
3. Overview of Event Edi-
tor
Configuration Guide
Table 3.3.3-2
Printout with a descriptive summary of the values of the Event
Masks
3.3.4.
Selecting event filter
Some relays may contain a number of event masks, out of which one at a time can
be used in MicroSCADA. During the initialisation the tool defines the event mask it
is using. The user can select another event mask later if the relay has multiple event
mask parameters and the protocol makes it possible to select the event mask.
EAS_Q1_R1A
4
BS1 signal of Io> ->
Reset
E6
6003
1
V101
EAS_Q1_R1A
4
BS1 signal of Io> ->
Activated
E7
6003
1
V101
EAS_Q1_R1A
5
BS2 signal of Io> ->
Reset
E8
6004
1
V101
EAS_Q1_R1A
5
BS2 signal of Io> ->
Activated
E9
6004
1
V101
EAS_Q1_R1A
6
Test mode of Io> ->
Off
E10
6005
1
V101
EAS_Q1_R1A
6
Test mode of Io> ->
On
E11
6005
1
V101
Object
EAS_Q1_R1
Object Type
REF54x ver. 1.3.2
Function / Module
DEF2LOW
Application
TUTOR
Printed
99-05-03 09:13:27
Page
1 (43)
Signals
LN
IX
Object text
Status
text
E-Code
OA
AC
Mask
Values of the Event Masks
Function / Module
Mask
Value
DEF2LOW
V101
4095
AR5FUNC_80
V101
4294967295
AR5FUNC_80
V102
4231806975
AR5FUNC_81
V101
127
AR5FUNC_82
V101
127
AR5FUNC_83
V101
127
AR5FUNC_84
V101
127
AR5FUNC_85
V101
127
AR5FUNC_86
V101
31
NOC3LOW
V101
4095
DEF2HIGH
V101
4095
NOC3HIGH
V101
16383
NOC3INST
V101
16383
Object
EAS_Q1_R1
Object Type
REF54x ver. 1.3.2
Application
TUTOR
Printed
99-05-03 09:13:27
Page
1 (1)
1MRS751886-MEN
LIB 510
23
LIB 510 Configuration
Configuration Guide
3. Overview of Event Edi-
tor
3
The event filter is defined with the help of the mask.
The Event Filter is changed by first selecting the Select Event Filter command in the
Settings Menu, and the entering the number of the Event Filter in the Select Event
Filter dialog box (Fig. 3.3.4.-1). Confirm by clicking OK.
)LJ
6HOHFW(YHQW)LOWHUGLDORJER[
It might also be possible not to use any of the event masks which means that all
events are received by MicroSCADA.The following table describes the
combinations of the object type and protocol when the event mask can be selected
by the user.
Table 3.3.4-1
Different combinations of the object type and protocol
Object Type
Protocol
LON
REC52x
x
REF54x
x
REM54x
x
REX52x
x
REA5xx
REJ5xx
REU5xx
SPACOM
1MRS751886-MEN
LIB 510
25
LIB 510 Configuration
Configuration Guide
4. Trend
4
4. Trend
A trend is a time-related follow-up of process data. All types of process objects, i.e.
in and out data, binary, analog and digital data, can be illustrated as trends. The
trends can be presented in graphical form (as full-graphic curves) or in tabular form.
The Trend basket is the link between the station pictures including the process data
and the trend picture. In the station picture the user can select process data to be
presented in the trend picture by opening the basket dialog from the menu and
selecting the symbol (picture function) of the process data. This is described in detail
in the trend basket help. It must be noted that logging of the selected process data
starts when the trend basket is closed with the OK button in the station picture.
When the trend picture is shown, the user can select the data to be displayed in it
using the trend basket. When the trend basket is closed, the selected trends (see the
trend basket help for details) are brought to the trend picture and the parameters of
the coordinate system are set according to the parameters of the trends.
)LJ 7KHWUHQGJUDSKLFDOIRUP
1MRS751886-MEN
26
1MRS751886-MEN
LIB 510 Configuration
LIB 510
4. Trend
Configuration Guide
4.1.
Trend report setups
LIB 510 Trend Reports has a set of parameters, such as the number of datalogs and
the maximum length of datalogs that can be changed if required. These parameters
are stored into the text file /LIB4/FMOD/TRENDS/USE/FTU_SETUP.TXT which
can be edited by using the SCIL Editor of the MicroSCADA Base Tools. The
parameters are stored as attributes of a SCIL variable object which means that when
editing the file, it must be ensured that the syntax of the file is correct. This can be
done e.g. by using the Check Syntax option of the SCIL Editor.
The number and maximum length of the datalogs used by the LIB 510 Trend
Reports are application specific parameters and 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.
When changing one of the following parameters:
• Number of datalogs
• Max length of datalogs
• Default time channel
• Default log function
The existing datalogs FTU_TRD*:D must be deleted and either the Trend picture or
the Trend Basket must be opened in order for the changes to take effect.
The attributes are explained in the following table:
FTU SETUP.TXT
Table 4.1.-1 Attributes and their explanations
Attribute
Explanation
Number_of_Datalogs
The number of data logs created for the trends, i.e. 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, i.e.
the maximum number of history values stored for one
process object. The maximum value of this attribute is
65535.
Default_time_channel
This attribute is the name of a Trend Reports time channel
and defines the default sampling interval. Possible values
are "FTU_TRT30" (sampling interval 30 seconds),
"FTU_TRT60" (60 seconds), "FTU_TRT120" (2 minutes),
"FTU_TRT300" (5 minutes) and "FTU_TRT600" (10
minutes).
Default_log_function
The default operation performed when a value is stored.
Possible values 0 (direct), 1 (sum), 2 (mean), 4 (difference)
List_separator
The ASCII text string used for separating items in the lists of
the Trend Basket.
ASCII_column_separator
The ASCII character used for separating columns when
trends are saved to a file.
ASCII_file_Extension
The default extension of a file to which a trend is saved.
1MRS751886-MEN
LIB 510
27
LIB 510 Configuration
Configuration Guide
4. Trend
4
4.2.
Preparing trend picture preconfigurations
With this dialog the user can save the current trend picture set-up as a named
preconfiguration, which can be opened from the basket dialog or from the LIB 500
standard menu. The following parameters are saved: the current set of trends (logged
process objects), the trend curve line parameters (line style, line color and line
width), the X-axis and Y-axis parameters and the background color.
Existing preconfigurations can be deleted and renamed with the Delete and Rename
buttons on the right side of the list.
)LJ 7KH6DYH7UHQG3UHFRQILJXUDWLRQVGLDORJ
The existing preconfigurations are shown on the list. The name of the configuration
(max. 15 characters) must be entered into the field above the list before the
preconfiguration can be saved. When the preconfiguration is opened, its name is set
as the trend picture title.
To delete a preconfiguration, select a preconfiguration from the list and click the
Delete button. To rename a preconfiguration, select one from the list and click the
Rename button. This opens a new dialog where the new preconfiguration name can
be entered.
Number_of_decimals
The number of decimals used when trends are presented in
tabular form.
Max_length_of_status_text
The maximum number of characters of the status text used
when trends are saved to a file.
Attribute
Explanation
28
1MRS751886-MEN
LIB 510 Configuration
LIB 510
4. Trend
Configuration Guide
To open the preconfiguration, the included process objects must be logged, i.e. they
must remain in the trend basket.
The OK button saves the preconfiguration, Cancel withdraws all changes. Saving a
preconfiguration requires at least Engineering (2) level user authorization.
4.3.
Making a menu item of a trend preconfiguration
A preconfigured filter (which was given a name in the Trend preconfigurations
dialog, see Fig. 4.2.-1) can be added to the Trend menu as described in this section.
The menu item is then available in REPORTS/Trends/Preconfiguration x.
Changing a menu item in Preconfiguration x is performed in the following way:
Open the Picture Editor by opening the Engineering menu and by selecting the
Tool Manager.
)LJ 6HOHFWLQJWKH0LFUR6&$'$7RRO0DQDJHUIURPWKH(QJLQHHULQJPHQX
To be able to access the Tool Manager, the user needs to have authority level 2 or
higher for authority group Tools.
Start the Picture Editor in the User Interface folder by double-clicking the icon.
)LJ 'RXEOHFOLFNWKH3LFWXUH(GLWRULFRQWRVWDUWLW
Open the base picture by selecting it in the File menu either by clicking first
Open and then By File Chooser or By Name. Another possibility is to select the
name of the picture on the list in the File menu.
Click the Picture Functions button
Select the picture by clicking it with the mouse so that handles appear in the
corners of the picture
1MRS751886-MEN
LIB 510
29
LIB 510 Configuration
Configuration Guide
4. Trend
4
Click the Configure Function button
After clicking the above-mentioned button, the Standard Configuration Tool
dialog box appears.
)LJ 6WDQGDUG&RQILJXUDWLRQ7RRO
Select the Tools tab by clicking the tab, select the Menu Configuration tool on the
list, and click the Open button under the list. The Menu Configuration Tool dialog
box (Fig. 4.3.-4) appears.
30
1MRS751886-MEN
LIB 510 Configuration
LIB 510
4. Trend
Configuration Guide
)LJ 0HQX&RQILJXUDWLRQ7RRO
By clicking the + sign in front of the file named Reports (the + sign changes into -
sign after it has been clicked) in the list box, several alternatives become available.
The various preconfiguration alternatives can be found by clicking the + sign in front
of the Trends folder. The alternatives No preconfiguration, Preconfiguration 1,
Preconfiguration 2, Preconfiguration 3 are available. Select the desired alternative
and press the Edit button, after which the dialog shown below appears.
1MRS751886-MEN
LIB 510
31
LIB 510 Configuration
Configuration Guide
4. Trend
4
)LJ (GLW0HQX,WHPGLDORJ
By selecting the Advanced option in the Menu action definitions field and by
clicking the Advanced button, the Item action programis opened, see Fig. 4.3.-6. The
title of the filter is shown in the Title: field when the alternative Enabled is selected
in the Menu action definitions field.
)LJ ,WHPDFWLRQSURJUDP
The name is shown in brackets on the second row of the code. Change the name
(title) to the name that was given earlier in the Trend preconfiguration dialog and
update the Item action program by selecting the option Update in the File menu.
1MRS751886-MEN
LIB 510
33
LIB 510 Configuration
Configuration Guide
5. Measurement reports 2
5
5.
Measurement reports 2
5.1.
Overview and description
The Measurement Reports 2 is used within LIB 500 Applications for various types
of time related reports, such as hourly, daily, weekly, monthly and yearly reports.
The Measurement Reports 2 can be used for:
• Reporting of energy (active, reactive)
• Reporting of current (e.g. bay level)
• Reporting of voltage (e.g. bay level)
• Reporting of frequency
• Reporting of temperature
• Reporting of district heating
Generally, the reports are time-related follow-ups of process, metered, entered or
calculated data. All types of data can be illustrated as reports. All data for the reports
are calculated and stored in real time. Report data is collected and calculated either
cyclically or triggered by events. The most common method is to collect raw data
from the process, and thereafter to refine it and store it in the report database.
The collection and calculation of report data can be initiated in the following ways:
• at predefined time intervals
• when a predefined event occurs
• as a result of a calculation
• based on a condition
• on the operator's request
5.1.1.
Features/options
The Measurement Reports 2 is based on a divided system structure and it consists of
Report HSI, Report Base and Report Tool. Each component is independent from the
others and provides a set of functions for installing, configuring, defining, and
monitoring the user specific reports. The divided structure and independent
components allow a dynamic and a wide variety of the use of reports.
The Measurement Reports 2 supports the following time related reports:
• Hourly report (time resolution: 3 minutes)
• Daily report (time resolution: 15 minutes)
• Daily report (time resolution: 30 minutes)
• Daily report (time resolution: 60 minutes)
• Weekly report (time resolution: 1 day)
• Monthly report (time resolution: 1 day)
• Yearly report (time resolution: 1 month)
• Quick report on daily bases (time resolution: according to a period cycle)
Each report picture is composed of a report base picture function and a number of
report columns. The report base picture function includes all common
functionalities (e.g. report header, type and unit) which are usable within the report
1MRS751886-MEN
34
1MRS751886-MEN
LIB 510 Configuration
LIB 510
5. Measurement reports 2
Configuration Guide
pictures. The report columns constitute different types of data, e.g. points of time,
measured, metered, manually entered or calculated values. All data values within the
report can be presented either in a tabular (numerical) or in a graphical form as full-
graphic curves. In maximum, a report picture can contain 11 columns per report
page, including the time column.
Report Base includes a set of functions (e.g. database, data collection, calculation
and storing methods) which provide an interface between the real time process and
the report pictures. Within these functions the real time data from the process is
collected, calculated and stored into the report database and then displayed in the
report pictures with unequivocal means.
Report Tool includes a set of functions, which provide report specific tools for
installing and configuring the Report Base (e.g. the configuration of report object,
calculation and database settings) and the Report HSI (the configuration of the
report picture columns) when defining the user specific reports.
General features and options of the LIB 510 Measurement Reports 2 are:
• Improved architecture; Report HSI, Report Base and Report Tool
• Report presentations in a tabular (numerical) and in a graphical form
• Several report pages can be displayed within one report picture
• Special days supported through the Calendar Tool
• Configurable report objects
• Dynamic report object handling
• All types of process objects can be illustrated as reports
• Dynamic calculation operations enabled
• User specific definitions enabled
• Base period interval configurable: 15, 30 or 60 minutes
• History length for sampled and period values configurable
• Forecast period area on daily basis enabled
• Begin of day and begin of week configurable
• Application specific definitions enabled
1MRS751886-MEN
LIB 510
35
LIB 510 Configuration
Configuration Guide
5. Measurement reports 2
5
5.2.
General description of reports
5.2.1.
Overview and description
)LJ
([DPSOHRI'DLO\5HSRUWSLFWXUH
Report HSI provides an user-friendly interface for data analysis and for showing
values in a tabular (numerical) and in a graphical form. It can be used for example
for monitoring measured, metered, entered or calculated values, showing the history
of values, predicted future values, entering/correcting values etc.
5.2.2.
Features and options
• Report header *
• Report type *
• Report unit *
• Report scale *
• Time column
• Report columns *
• Summary columns *
36
1MRS751886-MEN
LIB 510 Configuration
LIB 510
5. Measurement reports 2
Configuration Guide
• Tabular presentation
• Graphical presentation
• Selecting a specific time from the history and future (if forecast period area
enabled)
• Scrolling backward and forward in history and in future (if forecast period area
enabled)
• Editing of period values *
• Tagging of manually entered values *
• Tracing of edited values via log file *
• Marking of values with status "unreliable", "manually entered" or "Error", in case
of an erroneous status
• Note dialog
• Scaleable axis (in a graphical form)
• Scrolling in X and Y direction (in a graphical form)
• On/off switching of each curve (in a graphical form)
• On/off switching of grid (in a graphical form)
• Load-duration curves (in a graphical form)
• Report data saving to a file (ASCII and .CSV format)
• Printout option
• Multiple report pages *
• Report specific menu *
• Authorization support *
• Help files
• Quick reporting with preconfigurations (only within the Quick report)
The ones marked with * are options within the report picture configurable attributes
by the user. (Please see 5.3.2. for details.)
5.3.
Report preparations
5.3.1.
Environmental requirements
In order to operate, the product package LIB 510 Measurement Reports 2 sets the
following requirements to its environment:
• The number of parallel queues used in MicroSCADA application has to be at
least 3
• LIB 500 Backbone version has to be 1.5 or higher
• Other requirements according to MicroSCADA Base System and the product
package LIB 510
5.3.2.
Preliminary work
5.3.2.1.
Defining process objects
The process objects must exist before they can be connected to the reports.
1MRS751886-MEN
LIB 510
37
LIB 510 Configuration
Configuration Guide
5. Measurement reports 2
5
Please note that if pulse counters are used with a SRIO type of station, the value of
the pulse counter is sent as an analogous input. Regardless of this the process object
could and must be defined as a pulse counter. It is also good to remember that when
defining report objects for this kind of process objects, the value of the pulse counter
is multiplied by 1000 (default) when the value is transferred from a SRIO type of
station.
5.3.2.2.
Defining network printer
If the printer is not connected locally to the SYS computer, a network printer must
be defined before it is possible to print measurement reports. LIB 510 Measurement
Reports 2 uses a VS Printer object, and so the network printer must be PostScript
compatible when using a remote monitor.
Definitions must be done with NT’s Printer Wizard. In order to define a network
printer, the following steps need to be taken:
Open the Printers folder in the NT’s Control Panel.
Double-click the Add Printer icon, and the Add Printer Wizard opens.
Select My Computer and press the Next button.
Press the Add Port... button, and the Printer Ports dialog opens.
Select Local Port from the list, and press the New Port... button.
Enter a port name in the format \\<name of the printer server>\<name of the
printer> and press OK.
Close the port dialog.
Select the inserted port, and press the Next button.
Select the manufacturer and model of your printer and press the Next button.
Follow the orders of the Printer Wizard, until it asks if you want your Windows-
based programs to use this printer as the default printer. Select “Yes” and press
the next button.
Follow the orders of the Printer Wizard until the installation is completed.
Configure the size and the orientation of the paper correct through the Printers
folder (A4, Landscape).
Please note that if the printer is not connected locally to the SYS computer, the
printer is accessible to MicroSCADA only if the printer is accessible from the SYS
computer and the MicroSCADA user has proper access rights to the printer. That is
why, the MicroSCADA user and user password on the computer sharing the printer
has to exist and be identical with the user and user password on the SYS computer.
The password should be the same because at run-time the MicroSCADA system
cannot prompt the user for a new password.
38
1MRS751886-MEN
LIB 510 Configuration
LIB 510
5. Measurement reports 2
Configuration Guide
Please note that when a remote monitor to MicroSCADA is opened, the printer port
which will be used has to be defined, too. Fig. 5.3.2.2.-1 presents an example of
opening a remote monitor with VS Printer definitions. In case there are difficulties
with the printer installation and configuration, please consult your PC support.
)LJ 'HILQLQJWKHXVHGSULQWHUZKHQXVLQJDUHPRWHPRQLWRU
5.3.2.3.
Application specific definitions (reports)
Before defining the reports, the following definitions should be settled from the
Application Settings (See LIB 500 4.0.3 Operator’s Manual, Backbone, chapter 5
for details):
• Period cycle * : 15, 30 or 60 minutes (Default: 60 minutes)
• The length of the period values history *: 1 - 5 years (Default: 2 years)
• The length of the forecast period area: 0 - 15 days (Default: 0 days)
• The beginning of the report day in hours after midnight *: 0 - 23 (Default: 0)
• The beginning of the report week Monday - Sunday (Default: Monday)
• Sampling cycle *: 3 minutes (Default: 3 minutes, reserved for future use)
• The length of the sampled values history *: 0 - 15 days (Default: 8 days)
!
These definitions are valid for the entire application and changes to these definitions
(The ones marked with *) afterwards will cause lost of all existing history data.
Fig. 5.3.2.3.-1 presents the Report Settings dialog which can be opened from the
Application Settings and where the application specific definitions can be defined.
1MRS751886-MEN
LIB 510
39
LIB 510 Configuration
Configuration Guide
5. Measurement reports 2
5
)LJ ([DPSOHRI5HSRUW6HWWLQJVGLDORJ
5.3.3.
Report configuration
In order to open any of the tools in the Report Configuration Tool, one of the report
base picture function must be installed to the Picture Editor. Please see Section 5.4.
for details.
Please note that there is a locking mechanism connected to the Report Object
Configuration Tool, Execution Delays and User-defined Definitions in order to take
care of concurrency when editing the report configuration data. In another words,
these tools cannot be used simultaneously by different users without breaking the
locking mechanism.
If one of these tools is already in use by one user, and another user tries to open the
same tool, a notice dialog will be displayed (please see Fig. 5.3.3.-1). Please note
that breaking the lock may cause corruption of the report configuration data.
)LJ
([DPSOHRIQRWLFHGLDORJZKHQWKHWRROLVORFNHG
5.3.3.1.
Report object settings
Before it is possible to create and configure report pictures, report objects have to be
defined and created. The report objects are shown in the report HSI in a numerical
40
1MRS751886-MEN
LIB 510 Configuration
LIB 510
5. Measurement reports 2
Configuration Guide
or in a graphical form. It is possible to connect them e.g. to a process object or to a
calculation operation. With the Report Object Configuration Tool the user is able to:
• configure and create report objects
• connect process objects to data objects
• create data objects for every report object
• create an update procedure for non-spontaneous process objects
• create time channels for report updating cycles
• create command procedures for calculated report objects
• define a calculation order of calculated report objects
The report objects are common for an application, so there is no need to configure
them every time a report picture is added, if needed report objects already exist.
Before report objects are created or configured, it is very important to make a
decision about the application specific report settings, because if these settings are
changed afterwards, all the existing report data will be lost. Please see Section
5.3.2.2. The main steps of defining the report objects are:
Open the Report Configuration Tool.
Insert new report objects.
Edit existing report objects.
Save the report objects configuration data or create all needed data objects,
command procedures and time channels by updating the configuration data to
the report database.
The report database is an union of data objects, command procedures and time
channels, which are used by the report system.
Report object configuration tool
The Report Object Configuration Tool is opened from the Standard Configuration
Tool (SCT). In order to open this tool, the following steps need to be taken:
Open the Report Configuration Tool in the Tools menu of the SCT.
Select the Report Object Settings item and open the selection.
When the Report Object Configuration Tool is opened, the user is able to insert new
report objects and to modify existing ones. Fig. 5.3.3.1.-1 presents an open Report
Object Configuration Tool. In this figure, there are two configured report objects,
which are not yet updated to the report database.
1MRS751886-MEN
LIB 510
41
LIB 510 Configuration
Configuration Guide
5. Measurement reports 2
5
)LJ 7KH5HSRUW2EMHFW&RQILJXUDWLRQ7RRO5HSRUW2EMHFWOLVWV
Table 5.3.3.1-1
The Report Object Configuration Tool dialog contains four
notebook pages
Note book page
Explanation
In Database
The page In Database contains report objects which are
updated to the database. In other words, the page In Database
always contains the setup of the present reports.
Inserted
This page contains all inserted report objects which are not yet
updated to the database. These report objects are not taken
into account in the present reports.
Deleted
When a report object on the In Database page is deleted, it is
not actually deleted but marked as a deleted object. When data
concerning this object can be found on the page Deleted, it
indicates that the object is to be deleted, and that it will be
removed when modifications will be updated to the database.
Deletion mark functions like an On/Off button. The user can
remove the deletion mark by pressing the Delete button on the
Deleted page. These report objects are taken into account in
the present reports.
Modified
When a report object is edited, the modifications are not
transferred straight to the database, but they are stored in the
Modified page. When modifications are updated to the database
by pressing the Modify DB button, the configuration of the report
object on this page replaces the configuration of the object with
the same logical name on the In Database page, and the
database is also configured according to new configurations.
These configurations are not taken into account in the present
reports.
42
1MRS751886-MEN
LIB 510 Configuration
LIB 510
5. Measurement reports 2
Configuration Guide
Dialog buttons
Table 5.3.3.1-2
The functionality of the buttons in the Report Object
Configuration Tool
Inserting a new report object
New report objects are inserted from the Report Object Configuration Tool. In order
to insert a new report object, the following steps need to be taken:
Open the Report Configuration Tool in the Tools menu of the SCT.
Button
Explanation
Edit
The Edit button opens the Report Object Editor dialog regarding the
selected object. The user is able to edit all attributes except for the
logical name of the report object.
NOTE! If the group id is changed, all data objects in the report
database for this report object will be deleted and recreated when
modifications are updated to the database.
Insert
The Insert button opens an empty Report Object Editor dialog. The
user is able to create a new report object and to configure all
attributes.
Delete
The function of the Delete button depends on which notebook page is
selected. If the In Database page is selected, the deleted object is
only marked as deleted and it will be permanently removed from the
database during the following database update. Thus it is possible to
undo deletion. Information about the marked object is also added to
the page Deleted.
If the Inserted page is selected, the selected report object is
immediately and permanently removed from the configuration data,
and the undo operation is impossible.
When the Deleted page is selected, it is possible to remove the delete
mark from the selected report object by pressing the Delete button,
and the report object will not be removed during the following
database update.
If the Modified page is selected, modifications of the selected report
object are immediately and permanently removed from the
configuration data, and the undo operation is impossible.
Advanced
The Advanced button opens the selected report object in the tree
views. With this tool the user is able to examine all configuration
attributes of one report object.
Modify DB
This button updates all modifications to the report database. This
button must be pressed before configurations will come into
operation.
OK
The OK button saves all configuration data and closes the Report
Object Configuration Tool dialog. Configuration data is saved, but the
report database is not updated.
Cancel
The Cancel button discards all changes and closes the Report Object
Configuration Tool dialog.
Apply
This button saves all configuration data. Configuration data is saved,
but the report database is not updated. See also the Modify DB
button.
Help
Opens a help text dialog.
1MRS751886-MEN
LIB 510
43
LIB 510 Configuration
Configuration Guide
5. Measurement reports 2
5
Select the Report Object Settings item and open the selection.
Open the Report Object Editor by pressing the Insert button in the Report
Configuration Tool.
Make configurations for the report object. The fields are described in detail in
the previous chapter.
Save the object by pressing the OK button (closes also the dialog) or by pressing
the Add button (leaves configuration data ready for the following report object).
Insert as many report objects as needed.
When the report object is inserted, it will appear in the Inserted page of the Report
Configuration Tool, as presented in the Fig. 5.3.3.-1.
Configuring a report object with the report object editor tool
With the Report Object Editor dialog the user is able to configure report objects. If
this dialog is opened by pressing the Insert button in the Report Object
Configuration Tool, the dialog is in insertion mode, which means that the user is able
to define the logical name for report object. If the dialog is opened with the Edit
button, it is in edit mode, and the user cannot change the Logical name field any
more. Fig. 5.3.3.1.-2 presents an opened Report Object Editor in edit mode.
)LJ 7KH5HSRUW2EMHFW(GLWRU
The Report Object Editor dialog includes at least one notebook page (General
Settings), and two pages (General Settings and Additional Settings) at the most. The
page Additional Settings is visible for measured and calculated report objects. When
the user tries to save the edited object, the Report Object Editor checks all required
information in the dialog. If some information is invalid, a message box is opened.
44
1MRS751886-MEN
LIB 510 Configuration
LIB 510
5. Measurement reports 2
Configuration Guide
Dialog buttons
Table 5.3.3.1-3
The functionality of the buttons in the Report Object Editor
dialog
General settings of a report object
The fields on the General Settings page are the same for every report object type.
The Logical name and Group ID fields are obligatory.
Table 5.3.3.1-4
Configurable attributes and fields
Measured report objects are connected to some process objects. Measured report
object types are MS (sum calculated), MM (mean calculated), MN (min value), MX
(max value) and MP (period value).
Button
Explanation
OK
When the OK button is pressed, this report object is saved on a
proper report object list and the dialog is closed. If some
configurations are unacceptable, an error message appears.
Add
The Add button saves current configurations to a proper report
object list and leaves the current configuration as a base for the
following insertion. This is handy e.g. when the same process
object is used in many report objects.
Clear
Clears all fields.
Cancel
The Cancel button discards all changes and closes the Report
Object Editor dialog.
Help
Opens a help text dialog.
Logical name (LN)
The Logical name field defines the name of this report object. It also
defines the names of the data objects, which will be created when
insertions are updated to the report database. The name of the
report object may be composed of max. 9 characters. Allowed
characters are the letters A - Z, all digits and the underscore (_).
The object name must begin with a letter or a digit.
Please note that it is not recommended to use a digit as the last
character, because the data objects for period values for a certain
year are named with an additional digit on the end of the logical
name. For this reason there is a risk of a malfunction in case there
are e.g. two report objects, ENERGY and ENERGY1. When the
length of the period history is e.g. 2 years, the names of the data
objects to be created for the ENERGY report objects are ENERGY
(which is the data object for the sampling values), and ENERGY0,
ENERGY1 and ENERGY2 (which are the year data objects of the
period values). Vice versa, the names of data objects to be created
for the ENERGY1 report objects are ENERGY1 (which is the data
object for the sampling values), and ENERGY10, ENERGY11 and
ENERGY12. Now the data object called ENERGY1 is used both as
a sampling as well as a period data object, which is impossible.
Comment (CM)
This text will be shown on the report object list and in the CM
attribute of data objects.
Unit (ST)
An informative field which is shown only on the report object list.
Group ID (ID)
The type of this report object. Possible main categories are
measured, calculated, entered, user defined and gauged.
1MRS751886-MEN
LIB 510
45
LIB 510 Configuration
Configuration Guide
5. Measurement reports 2
5
Table 5.3.3.1-5
The different types function in the following way
The values of calculated report objects are evaluated according to the definitions of
input parameters and calculation orders. Calculated report object types are CS
(sampled value), CP (period value) and CB (sampled and period values).
Table 5.3.3.1-6
The different types function in the following way
When the user defines an entered or a gauge report object only data objects are
created in the report database. No automatic configurations or value samplings are
done. The identification for an entered report object is EN and GA is for a gauge
(meter) report object.
With user-defined types the user is able to build an own reporting functionality.
When the user defines own user groups with the User Defined Groups and
Procedures tool, the groups appear onto this combo popdown list. Using user-
defined groups requires profound knowledge about reports, and therefore, this
feature should only be used when it is impossible to implement the wanted
functionality otherwise.
Additional settings for the measured report object types
This notebook page is shown only when a measured type of the Group ID is selected.
Only the Update instructions needed field is not obligatory.
Function
Explanation
MS
Sum. Data objects are created in the report database for both sampled
and period values. A period value is the sum of sampled values within
that period.
MM
Average. Data objects are created in the report database for both
sampled and period values. A period value is the average value of
sampled values within that period.
MN
Minimum. Data objects are created in the report database for both
sampled and period values. A period value is the smallest value of
sampled values within this period.
MX
Maximum. Data objects are created in the report database for both
sampled and period values. A period value is the largest of sampled
values within this period.
MP
Period. Data objects are created in the report database for both
sampled and period values, but the length of sampled object is 1, and
values are read only once within a period cycle. A period value is read
from a process object.
Function
Explanation
CS
Data object is created only for sampled values. Defined calculation is
made once a sampling cycle (e.g. once every 3 min) and the value of
this calculation are stored in the report database.
CP
Data object is created only for period values. Defined calculations are
made once a period cycle (e.g. once every 15 min, 30 min or 1 hour)
and the value of this calculation are stored in the report database.
CB
Data objects are created for both sampled and period values. Defined
calculations are made in accordance with the sampling and period
cycles, and the results are stored in the report database.
46
1MRS751886-MEN
LIB 510 Configuration
LIB 510
5. Measurement reports 2
Configuration Guide
)LJ 7KH$GGLWLRQDO6HWWLQJVSDJHIRUPHDVXUHGUHSRUWREMHFWW\SH
If you click Browse in the above dialog, the Process Object Browser (see Fig.
5.3.3.1.-4) will appear on the screen.
)LJ 7KH3URFHVV2EMHFW%URZVHU
The Process Object Browser searches for signals from the process database type of
analog input (AI), digital input (DI) and pulse counter (PC).
If the size of the process database exceeds 10 000 signals, the next/previous 10 000
signals buttons at the bottom of the dialog will be activated.
After the signal is selected and OK button is clicked, the fields in the Report Object
Editor dialog are automatically filled (see Fig. 5.3.3.1.-3). The result will be the
same, if you double-click the signal in question.
1MRS751886-MEN
LIB 510
47
LIB 510 Configuration
Configuration Guide
5. Measurement reports 2
5
Table 5.3.3.1-7
Configurable attributes and fields
Attribute
Field
Application of the process object
(P_APL)
The application of the process object where this report object
is connected. 0 is current application.
Logical name of the process
object (P_LN)
The Logical name of the process object where this report
object is connected. 0 is current application. The user is able
to write the name in the field, or the name can be selected
from the list by using the Browse button, as in Fig. 5.3.3.1.-3.
Index of the process object
(P_IX)
The index of the process object to which this report object is
connected. When the Browse button is used, this field is also
updated.
Type of the process object
(P_PT)
The type of the process object to which this report object is
connected. This value comes straight from the process
database. Possible values are AI (analog input), PC (pulse
counter) and DI (digital input).
Data acquisition unit (P_RX)
The data acquisition unit. This value comes straight from the
process database.
Max value of the pulse counter
(P_PS)
If the type of the process object is PC, a maximum value of
pulse counter is needed. If the counter counts pulses
repetitiously, this value must be 0 (zero). Please note that the
maximum value of the pulse counter has to be divided by the
linear scale of the process object (please see below) and the
result should be placed into the field of the Max value of the
pulse counter (P_PS) if needed.
Examples of the maximum values of the pulse counters:
SPACOM *
- SPTO 1D2, 1D5, 1D6, 6D3
1 000 (0V8-0V15)
1 000 000 000 (0V5)
- SPOC 110C, 111C, 112C
30 000 (13 .. 16V5)
RTU 200/210
- within RP570
PROCOL
2^Bit Count
2 147 483 648 (2^31)
65 536
NOTE! If pulse counters are used with a SRIO type of station,
the value of the pulse counter is multiplied by 1000 (default)
when the value is transferred from a SRIO type of station. Also
note that parameter V5 (SPTO) cannot be used, if pulse
counters are used with a SRIO type of station.
Linear scale of the process
object (P_SC)
The linear scale of the process object. This scale is a
multiplier, which is used when values from the process
database are stored into the report database.
Update instructions needed
(P_ACT)
If the process object does not update spontaneously, the
update instruction has to be defined by the user. If this kind of
instruction is needed, this check box has to be selected, and
the Instr. button has to be used to write the instruction.
48
1MRS751886-MEN
LIB 510 Configuration
LIB 510
5. Measurement reports 2
Configuration Guide
)LJ 7KH$GGLWLRQDO6HWWLQJVSDJHIRUFDOFXODWHGUHSRUWREMHFWW\SH
Additional settings for the calculated report object types
This notebook page is shown only when a calculated type of the group id is selected.
Configurable things are:
,QSXWSDUDPHWHUVIRUFDOFXODWLRQ'$7$,1
If the calculation operation of this object uses values of some other report objects as
input parameters, all the parameter objects have to be introduced here. The logical
names of the parameter report objects have to be written one by one, with every
name on a separate line. Fig. 5.3.3.1.-6 presents an example of input parameters for
the calculation operation.
&DOFXODWLRQRSHUDWLRQ23(5
The calculation operation may be an one line calculation, or a multi-line SCIL
program with the #RETURN command. The input parameters could be referenced
with variables %OBJ1..%OBJn, where %OBJ1 is the first report object on the input
parameter list, and the %OBJn variable is correspondingly the last one. A special
case is when there is only one input parameter; when the reference to the input
parameter is done with the %OBJ variable without any index number. The result
type of the calculation operation may be INTEGER or REAL, or a vector of the
types. Fig. 5.3.3.1.-7 presents an example of an one line calculation operation. Fig.
5.3.3.1.-8 presents another example with multi-line calculation.
Note that %OBJn is of type VECTOR. See Section 4.3.1 for more information.
&DOFXODWLRQRUGHUVRIVDPSOHGDQGSHULRGYDOXHV
The Calculation order of sampled values group is enabled when the group
identification is CS or CB. The Calculation order for period values group is enabled
when the group identification is CP or CB. If the logical name of the report object is
not on the calculation order list, the Add button is enabled, and the Up and Down
1MRS751886-MEN
LIB 510
49
LIB 510 Configuration
Configuration Guide
5. Measurement reports 2
5
buttons are disabled. If the logical name is already on the calculation order list, the
Add button is disabled, and the Up and Down buttons are enabled. By pressing the
Add button, this report object is added to the calculation order list, and by pressing
the Up and Down buttons, the user is able to move the current report object up and
down on the calculation order list. The calculation order goes from top to down.
Please note that some logical names can be mentioned twice on the calculation order
list. In that case there is an original and a modified place in the calculation order. The
calculation order place after modifications is marked with the character "(M)".
When inserting a new object, there is "(I)" after the logical name of the inserted but
not after the updated report object.
The calculation order must be defined every time a new calculated objects is inserted
or some existing calculated object is modified.
)LJ $QH[DPSOHRILQSXWSDUDPHWHUVIRUFDOFXODWLRQ
)LJ $QH[DPSOHRIDVLQJOHOLQHFDOFXODWLRQRSHUDWLRQ
)LJ $QH[DPSOHRIDPXOWLOLQHFDOFXODWLRQRSHUDWLRQ
50
1MRS751886-MEN
LIB 510 Configuration
LIB 510
5. Measurement reports 2
Configuration Guide
5.3.3.2.
Execution delays
With this tool the user can define execution delays for period cycles and for
sampling cycles. Execution delays must be used when process objects are not
spontaneous and need an update command to be used before current value is
available in the process database. An execution delay defines for how long the
program waits after time channels are triggered, before the evaluation of values will
start. When update commands are used, they are sent right after the time channels
are triggered, and the program reads the value from the process database after the
execution delay.
5.3.3.3.
User-defined groups and procedures
It is possible for the user to create own report object types. With this tool the user
can write methods for different cases, i.e. what should be done when the system
starts up or when the period cycle is full. This requires profound knowledge about
reports, and therefore, this feature should be used only when it is impossible to
implement the wanted functionality otherwise.
5.3.3.4.
Call-back procedure for sampling cycle
Call-back procedure for the sampling cycle is executed when all other sampling
cycle routines have been executed. Therefore, it is possible to execute programs
defined by the user every time sampling routines have been executed.
5.3.3.5.
Call-back procedure for period cycle
Call-back procedure for the period cycle is executed when all other period cycle
routines have been executed. Therefore, it is possible to execute programs defined
by the user every time period routines have been executed.
5.4.
Picture function installation
5.4.1.
General
This chapter describes the installation of the picture function for the Measurement
Reports 2 report base picture functions. The picture functions for the reports are
found in the directory /LIB4/FMOD/REPORTS2/INST and they should be installed
by using the LIB4 installation procedures (LIB4-LIB 510-Reports2). The
configuration of these picture functions will be performed using the Standard
Configuration Tool.
1MRS751886-MEN
LIB 510
51
LIB 510 Configuration
Configuration Guide
5. Measurement reports 2
5
)LJ
([DPSOHRIDQLQVWDOODWLRQRIDSLFWXUHIXQFWLRQIRUWKH
0HDVXUHPHQW5HSRUWVUHSRUWEDVHSLFWXUHIXQFWLRQV
5.4.1.1.
Environmental requirements
In order for the reports to operate, the following report items need to be defined:
1. Application Specific Definitions (Report Settings)
2. Report Objects
3. Execution Delays
5.4.1.2.
Installation
The installation of standard functions is divided into two main parts: installation and
configuration.
The tools, i.e. the Installation Tool and the Standard Configuration Tool, are shortly
described in the LIB 500 Base 4.0.3 Configuration Manual, Introduction.
There are report base picture functions of the following types. (Please note that each
of the report base picture function can now be installed with the header function
included in the previous revision and with the new Visual SCIL header.)
• Report Base (Hour)
• Report Base (Day, 1h)
• Report Base (Day, 30 min)
• Report Base (Day, 15 min)
• Report Base (Week)
• Report Base (Month)
• Report Base (Year)
52
1MRS751886-MEN
LIB 510 Configuration
LIB 510
5. Measurement reports 2
Configuration Guide
Table 5.4.1.2-1
During installation the following information has to be given
The name of the picture function (ID) should be unique within the same picture, and
it is recommended to use an identification that is universal, i.e. the identification
does not refer to any particular report.
Allowed characters are the letters A-Z, all digits and the underscore (_). However,
the name of the picture function cannot begin with a digit or the underscore.
The installation of application specific picture function is described in the LIB 510
4.0.3 Configuration Manual, Component Library.
5.4.2.
Report picture configuration
Hourly report base picture function
The report base picture function has the following attributes to configure with the
Standard Configuration Tool
Table 5.4.2-1
Configurable attributes
Attribute
Meaning
Default
ID
Name/Identification of the picture function within a picture
-
Attribute
Meaning
Default
PICTURE_HEADER
The title of the picture
-
REPORT_TYPE
The type of the report
-
REPORT_UNIT
The unit of the report
-
REPORT_SCALE
The general unit scale factor of the report 1
SUMMARY_INFO_1
States the summary information to be
shown on the first row of the summary
information bar
MEAN
SUMMARY_INFO_2
States the summary information to be
shown on the second row of the summary
information bar
MIN
SUMMARY_INFO_3
States the summary information to be
shown on the third row of the summary
information bar
MAX
COLUMN_CONFIG_DA
TA_FILE
The name of the column configuration file PICT/
REPORTS_H.TXT
ENABLE_MULTIPLE_P
AGES
States whether there are several report
pages within the same report picture
enabled or not
TRUE
AUTHORIZATION_GR
OUP
The name of the authorization group
REPORTS
STANDARD_MENU_PA
RT
The place of the standard menu part
B_LANG/
BGU_H1STMN.TXT
SPECIFIC_MENU_PAR
T
The place of the specific menu part
F_LANG/
FMU_H1SPMN.TXT
HELP_MENU_PART
The place of the help menu part
B_LANG/
BGU_H1HLMN.TXT
1MRS751886-MEN
LIB 510
53
LIB 510 Configuration
Configuration Guide
5. Measurement reports 2
5
Table 5.4.2-2
Attribute details
STANDARD_MENU_A
CTION
The place of the standard menu action
B_USE/BGU_
H1STAC.TXT
SPECIFIC_MENU_ACT
ION
The place of the specific menu action
F_USE/FMU_
H1SPAC.TXT
HELP_MENU_ACTION The place of the help menu action
B_USE/BGU_
H1HLAC.TXT
Attribute
Meaning
Default
PICTURE_HEADER
The title of the picture. The title is shown on the headerbar of
the picture.
REPORT_TYPE
The type of the report. The report type is shown on the top of
the report page. It can also be edited by the user or be left
undefined.
REPORT_UNIT
The unit of the report. The report unit is shown on the top right
corner of the report page. It can also be edited by the user or
be left undefined.
REPORT_SCALE
The general unit scale factor of the report. The report scale is
used for scaling of database values of the same unit scale. All
the values within the report are multiplied with the report scale.
Examples:
All the energy values in the database are stored with the unit
scale of MWh and the user would like to show values with the
unit scale of kWh instead of MWh. In this case the report scale
should be equal to 1000.
SUMMARY_INFO_1
States the summary information to be shown on the first row
of the summary information bar. The summary information is
shown for each column.
Examples:
SUM - the sum of the values is shown
MEAN - the mean of the values is shown
MIN - the minimum of the values is shown
MAX - the maximum of the values is shown
None - the summary value is not shown
SUMMARY_INFO_2
See above.
SUMMARY_INFO_3
See above.
COLUMN_CONFIG_
DATA_FILE
States the name of the configuration file where all the
configuration information of each report column is stored.
ENABLE_MULTIPLE_PAG
ES
States whether there are several report pages within the same
report picture to be shown or not.
AUTHORIZATION_GROUP States the authorization group to be used within the report. If
the specific authorization group is not defined, the
authorization group GENERAL will be used instead. (NOTE!
The name may not be composed of two letters followed by a
number)
54
1MRS751886-MEN
LIB 510 Configuration
LIB 510
5. Measurement reports 2
Configuration Guide
presents an example of the report base picture function configuration
with the Standard Configuration Tool.
STANDARD_MENU_PART States from where the standard menu part is fetched. It can be
a text file or a named program.
Syntax: ’logical path’/’file name’ or .my_named_program
Examples:
B_LANG/STAN_MN.TXT
.DEFINE_ST_MENU_BAR
SPECIFIC_MENU_PART
States from where the specific menu part is fetched. It can be
a text file or a named program. Please see examples above.
HELP_MENU_PART
States from where the help menu part is fetched. It can be a
text file or a named program. Please see examples above.
STANDARD_MENU_ACTI
ON
States from where the standard menu part program is fetched.
It can be a text file or a named program. Please see examples
above.
SPECIFIC_MENU_ACTION States from where the specific menu part program is fetched.
It can be a text file or a named program. Please see examples
above.
HELP_MENU_ACTION
States from where the help menu part is program fetched. It
can be a text file or a named program. Please see examples
above.
1MRS751886-MEN
LIB 510
55
LIB 510 Configuration
Configuration Guide
5. Measurement reports 2
5
)LJ
([DPSOHRI+RXUO\UHSRUWEDVHIXQFWLRQFRQILJXUDWLRQ
5.4.2.1.
Daily report base picture function
The report base picture function has the following attributes to configure with the
Standard Configuration Tool:
Table 5.4.2.1-1
Configurable attributes
Attribute
Meaning
Default
PICTURE_HEADER
The title of the picture
-
REPORT_TYPE
The type of the report
-
REPORT_UNIT
The unit of the report
-
REPORT_SCALE
The general unit scale factor of the report
1
SUMMARY_INFO_1
States the summary information to be shown on the
first row of the summary information bar
SUM
56
1MRS751886-MEN
LIB 510 Configuration
LIB 510
5. Measurement reports 2
Configuration Guide
Table 5.4.2.1-2
Attributes to configure with the Standard Configuration Tool
Table 5.4.2.1-3
Attribute details
SUMMARY_INFO_2
States the summary information to be shown on the
second row of the summary information bar
MEAN
SUMMARY_INFO_3
States the summary information to be shown on the
third row of the summary information bar
MIN
SUMMARY_INFO_4
States the summary information to be shown on the
fourth row of the summary information bar
MAX
Attribute
Meaning
Default
COLUMN_CONFIG_
DATA_FILE
The name of the column configuration
file
PICT/
REPORTS_D.TXT
ENABLE_MULTIPLE_PA
GES
States whether there are several report
pages within the same report picture
enabled or not
TRUE
FORECAST_AREA_
ENABLED
States whether the forecast area is to be
used within the report or not.
FALSE
AUTHORIZATION_GROU
P
The name of the authorization group
REPORTS
STANDARD_MENU_PAR
T
The place of the standard menu part
B_LANG/
BGU_H1STMN.TXT
SPECIFIC_MENU_PART
The place of the specific menu part
F_LANG/
FMU_D1SPMN.TXT
HELP_MENU_PART
The place of the help menu part
B_LANG/
BGU_H1HLMN.TXT
STANDARD_MENU_ACTI
ON
The place of the standard menu action
B_USE/BGU_
H1STAC.TXT
SPECIFIC_MENU_ACTIO
N
The place of the specific menu action
F_USE/FMU_
D1SPAC.TXT
HELP_MENU_ACTION
The place of the help menu action
B_USE/BGU_
H1HLAC.TXT
PICTURE_HEADER
The title of the picture. The title is shown on the headerbar of
the picture.
REPORT_TYPE
The type of the report. The report type is shown on the top of
the report page. It can also be edited by the user or be left
undefined.
REPORT_UNIT
The unit of the report. The report unit is shown on the top right
corner of the report page. It can also be edited by the user or be
left undefined.
REPORT_SCALE
The general unit scale factor of the report. The report scale is
used for scaling database values of the same unit scale. All the
values within the report are multiplied with the report scale.
Examples:
All the energy values in the database are stored with the unit
scale of MWh and the user would like to show values with the
unit scale of kWh instead of MWh. In this case, the report scale
should be equal to 1000.
1MRS751886-MEN
LIB 510
57
LIB 510 Configuration
Configuration Guide
5. Measurement reports 2
5
5.4.2.2.
Weekly report base picture function
The report base picture function has the following attributes to configure with the
Standard Configuration Tool:
SUMMARY_INFO_1
States the summary information to be shown on the first row of
the summary information bar. The summary information is
shown for each column.
Examples:
Day - the sum of the day energy (from the Calendar Tool)
Night - the sum of the night energy (from the Calendar Tool)
SUM- the sum of the values is shown
MEAN - the mean of the values is shown
MIN - the minimum of the values is shown
MAX - the maximum of the values is shown
None - the summary value is not shown
Note! Other in-day periods defined in the Calendar Tool can
also be stated as the summary information. (Please see LIB 500
Base Configuration Manual, Backbone Configuration Manual,
for details)
SUMMARY_INFO_2
Please see above.
SUMMARY_INFO_3
Please see above.
SUMMARY_INFO_4
Please see above.
COLUMN_CONFIG_
DATA_FILE
States the name of the configuration file where all the
configuration information of each report column is stored.
ENABLE_MULTIPLE_PA
GES
States whether there are several report pages within the same
report picture to be shown or not.
FORECAST_AREA_
ENABLED
States whether the forecast area is to be used within the report
or not.
AUTHORIZATION_GROU
P
States the authorization group to be used within the report. If the
specific authorization group is not defined, the authorization
group GENERAL will be used instead. (NOTE! The name may
not be composed of two letters followed by a number)
STANDARD_MENU_PAR
T
States from where the standard menu part is fetched. It can be
a text file or a named program.
Syntax: ’logical path’/’file name’ or .my_named_program
Examples:
B_LANG/STAN_MN.TXT
.DEFINE_ST_MENU_BAR
SPECIFIC_MENU_PART States from where the specific menu part is fetched. It can be a
text file or a named program. Please see examples above.
HELP_MENU_PART
States from where the help menu part is fetched. It can be a text
file or a named program. Please see examples above.
STANDARD_MENU_ACT
ION
States from where the standard menu part program is fetched. It
can be a text file or a named program. Please see examples
above.
SPECIFIC_MENU_ACTI
ON
States from where the specific menu part program is fetched. It
can be a text file or a named program. Please see examples
above.
HELP_MENU_ACTION
States from where the help menu part program is fetched. It can
be a text file or a named program. Please see examples above.
58
1MRS751886-MEN
LIB 510 Configuration
LIB 510
5. Measurement reports 2
Configuration Guide
Table 5.4.2.2-1
Configurable attributes
Table 5.4.2.2-2
Attribute details
Attribute
Meaning
Default
PICTURE_HEADER
The title of the picture
-
REPORT_TYPE
The type of the report
-
REPORT_UNIT
The unit of the report
-
REPORT_SCALE
The general unit scale factor of the report
1
SUMMARY_INFO
States the summary information to be
shown in the summary information bar
SUM
COLUMN_CONFIG_
DATA_FILE
The name of the column configuration file
PICT/
REPORTS_W.TXT
ENABLE_MULTIPLE_P
AGES
States whether there are several report
pages within the same report picture
enabled or not
TRUE
AUTHORIZATION_GRO
UP
The name of the authorization group
REPORTS
STANDARD_MENU_PA
RT
The place of the standard menu part
B_LANG/
BGU_H1STMN.TXT
SPECIFIC_MENU_PAR
T
The place of the specific menu part
F_LANG/
FMU_W1SPMN.TX
T
HELP_MENU_PART
The place of the help menu part
B_LANG/
BGU_H1HLMN.TXT
STANDARD_MENU_AC
TION
The place of the standard menu action
B_USE/BGU_
H1STAC.TXT
SPECIFIC_MENU_ACTI
ON
The place of the specific menu action
F_USE/FMU_
W1SPAC.TXT
HELP_MENU_ACTION
The place of the help menu action
B_USE/BGU_
H1HLAC.TXT
PICTURE_HEADER
The title of the picture. The title is shown on the headerbar of the
picture.
REPORT_TYPE
The type of the report. The report type is shown on the top of the
report page. It can also be edited by the user or be left undefined.
REPORT_UNIT
The general unit scale factor of the report.
REPORT_SCALE
The report scale is used for scaling database values of the same
unit scale. All the values within the report are multiplied with the
report scale.
Examples:
All the energy values in the database are stored with the unit
scale of MWh and the user would like to show values with the unit
scale of kWh instead of MWh. In this case the report scale should
be equal to 1000.
1MRS751886-MEN
LIB 510
59
LIB 510 Configuration
Configuration Guide
5. Measurement reports 2
5
5.4.2.3.
Monthly report base picture function
The report base picture function has the following attributes to configure with the
Standard Configuration Tool:
Table 5.4.2.3-1
Configurable attributes
SUMMARY_INFO
States the summary information to be shown in the summary
information bar. The summary information is shown for each
column.
Examples:
SUM - the sum of the values is shown
MEAN - the mean of the values is shown
MIN - the minimum of the values is shown
MAX - the maximum of the values is shown
None - the summary value is not shown
COLUMN_CONFIG_
DATA_FILE
States the name of the configuration file where all the
configuration information of each report column is stored.
ENABLE_MULTIPLE_P
AGES
States whether there are several report pages are to be shown
within the same report picture or not.
AUTHORIZATION_GRO
UP
States the authorization group to be used within the report. If the
specific authorization group is not defined, the authorization
group GENERAL will be used instead. (NOTE! The name may
not be composed of two letters followed by a number).
STANDARD_MENU_PA
RT
States from where the standard menu part is fetched. It can be a
text file or a named program.
Syntax: ’logical path’/’file name’ or .my_named_program
Examples:
B_LANG/STAN_MN.TXT
.DEFINE_ST_MENU_BAR
SPECIFIC_MENU_PAR
T
States from where the specific menu part is fetched. It can be a
text file or a named program. Please see examples above.
HELP_MENU_PART
States from where the help menu part is fetched. It can be a text
file or a named program. See examples above.
STANDARD_MENU_AC
TION
States from where the standard menu part program is fetched. It
can be a text file or a named program. Please see examples
above.
SPECIFIC_MENU_ACTI
ON
States from where the specific menu part program is fetched. It
can be a text file or a named program. Please see examples
above.
HELP_MENU_ACTION
States from where the help menu part is program fetched. It can
be a text file or a named program. Please see examples above.
Attribute
Meaning
Default
PICTURE_HEADER
The title of the picture
-
REPORT_TYPE
The type of the report
-
REPORT_UNIT
The unit of the report
-
REPORT_SCALE
The general unit scale factor of the report
1
60
1MRS751886-MEN
LIB 510 Configuration
LIB 510
5. Measurement reports 2
Configuration Guide
Table 5.4.2.3-2
Attribute details
SUMMARY_INFO
States the summary information to be
shown in the summary information bar
SUM
COLUMN_CONFIG_
DATA_FILE
The name of the column configuration file
PICT/
REPORTS_M.TXT
ENABLE_MULTIPLE_
PAGES
Is the several report pages within the same
report picture enabled or not
TRUE
AUTHORIZATION_GR
OUP
The name of the authorization group
REPORTS
STANDARD_MENU_P
ART
The place of the standard menu part
B_LANG/
BGU_H1STMN.TXT
SPECIFIC_MENU_PA
RT
The place of the specific menu part
F_LANG/
FMU_M1SPMN.TXT
HELP_MENU_PART
The place of the help menu part
B_LANG/
BGU_H1HLMN.TXT
STANDARD_MENU_A
CTION
The place of the standard menu action
B_USE/BGU_
H1STAC.TXT
SPECIFIC_MENU_AC
TION
The place of the specific menu action
F_USE/FMU_
M1SPAC.TXT
HELP_MENU_ACTION The place of the help menu action
B_USE/BGU_
H1HLAC.TXT
Attribute
Meaning
Default
PICTURE_HEADER
The title of the picture. The title is shown on the headerbar of the
picture.
REPORT_TYPE
The type of the report. The report type is shown on the top of the
report page. It can also be edited by the user or be left undefined.
REPORT_UNIT
The unit of the report. The report unit is shown on the top right
corner of the report page. It can also be edited by the user or be
left undefined.
REPORT_SCALE
The general unit scale factor of the report. The report scale is used
for scaling database values of the same unit scale. All the values
within the report are multiplied with the report scale.
Examples:
All the energy values in the database are stored with the unit scale
of MWh and the user would like to show values with the unit scale
of kWh instead of MWh. In this case the report scale should be
equal to 1000.
SUMMARY_INFO
States the summary information to be shown in the summary
information bar. The summary information is shown for each
column.
Examples:
SUM - the sum of the values is shown
MEAN - the mean of the values is shown
MIN - the minimum of the values is shown
MAX - the maximum of the values is shown
None - the summary value is not shown
1MRS751886-MEN
LIB 510
61
LIB 510 Configuration
Configuration Guide
5. Measurement reports 2
5
5.4.2.4.
Yearly report base picture function
The report base picture function has the following attributes to configure with the
Standard Configuration Tool:
Table 5.4.2.4-1
Configurable attributes
COLUMN_CONFIG_
DATA_FILE
States the name of the configuration file where all the configuration
information of each report column is stored.
ENABLE_MULTIPLE_P
AGES
States whether several report pages within the same report picture
are to be shown or not.
AUTHORIZATION_GR
OUP
States the authorization group to be used within the report. If the
specific authorization group is not defined, the authorization group
GENERAL will be used instead. (NOTE! The name may not
consist of two letters followed by a number)
STANDARD_MENU_P
ART
States from where the standard menu part is fetched. It can be a
text file or a named program.
Syntax: ’logical path’/’file name’ or .my_named_program
Examples:
B_LANG/STAN_MN.TXT
.DEFINE_ST_MENU_BAR
SPECIFIC_MENU_PA
RT
States from where the specific menu part is fetched. It can be a
text file or a named program. Please see examples above.
HELP_MENU_PART
States from where the help menu part is fetched. It can be a text
file or a named program. Please see examples above.
STANDARD_MENU_A
CTION
States from where the standard menu part program is fetched. It
can be a text file or a named program. Please see examples
above.
SPECIFIC_MENU_AC
TION
States from where the specific menu part program is fetched. It
can be a text file or a named program. Please see examples
above.
HELP_MENU_ACTION States from where the help menu part is program fetched. It can
be a text file or a named program. Please see examples above.
Attribute
Meaning
Default
PICTURE_HEADER
The title of the picture
-
REPORT_TYPE
The type of the report
-
REPORT_UNIT
The unit of the report
-
REPORT_SCALE
The general unit scale factor of the report
1
SUMMARY_INFO
States the summary information to be shown
on the summary information bar
SUM
COLUMN_CONFIG_
DATA_FILE
The name of the column configuration file
PICT/
REPORTS_Y.TXT
ENABLE_MULTIPLE_
PAGES
Is the several report pages within the same
report picture enabled or not
TRUE
AUTHORIZATION_GR
OUP
The name of the authorization group
REPORTS
62
1MRS751886-MEN
LIB 510 Configuration
LIB 510
5. Measurement reports 2
Configuration Guide
Table 5.4.2.4-2
Attribute details
STANDARD_MENU_P
ART
The place of the standard menu part
B_LANG/BGU_
H1STMN.TXT
SPECIFIC_MENU_PA
RT
The place of the specific menu part
F_LANG/FMU_
Y1SPMN.TXT
HELP_MENU_PART
The place of the help menu part
B_LANG/BGU_
H1HLMN.TXT
STANDARD_MENU_A
CTION
The place of the standard menu action
B_USE/BGU_
H1STAC.TXT
SPECIFIC_MENU_AC
TION
The place of the specific menu action
F_USE/FMU_
Y1SPAC.TXT
HELP_MENU_ACTION The place of the help menu action
B_USE/BGU_
H1HLAC.TXT
Attribute
Meaning
Default
PICTURE_HEADER
The title of the picture. The title is shown on the headerbar of the
picture.
REPORT_TYPE
The type of the report. The report type is shown on the top of the
report page. It can also be edited by the user or be left undefined.
REPORT_UNIT
The unit of the report. The report unit is shown on the top right
corner of the report page. It can also be edited by the user or be
left undefined.
REPORT_SCALE
The general unit scale factor of the report. The report scale is used
for scaling database values of the same unit scale. All the values
within the report are multiplied with the report scale.
Examples:
All the energy values in the database are stored with the unit scale
of MWh and the user would like to show values with the unit scale
of kWh instead of MWh. In this case the report scale should be
equal to 1000.
SUMMARY_INFO
States the summary information to be shown in the summary infor-
mation bar. The summary information is shown for each column.
Examples:
SUM - the sum of the values is shown
MEAN - the mean of the values is shown
MIN - the minimum of the values is shown
MAX - the maximum of the values is shown
None - the summary value is not shown
COLUMN_CONFIG_
DATA_FILE
States the name of the configuration file where all the configuration
information of each report column is stored.
ENABLE_MULTIPLE_
PAGES
States whether several report pages within the same report picture
are to be shown or not.
AUTHORIZATION_GR
OUP
States the authorization group to be used within the report. If the
specific authorization group is not defined, the authorization group
GENERAL will be used instead. (NOTE! The name may not be
composed of two letters followed by a number
1MRS751886-MEN
LIB 510
63
LIB 510 Configuration
Configuration Guide
5. Measurement reports 2
5
5.4.3.
Report column configuration
5.4.3.1.
Report column settings
Configurations to the report picture apply to the report picture itself but it does not
take any side for report objects that are considered to be shown within this report
picture. That is why configuration of report columns must take place for every report
picture.
In order to configure the report columns, the following steps need to be taken:
Open the Report Configuration Tool in the Tools menu (SCT-Tools).
Select Report Column Settings item and open the selection.
Configure attributes explained below.
Add a new report page, if necessary, with the Copy-Paste function
Save the current configuration (File - Update) and exit from the Program Editor
(File - Exit)
Table 5.4.3.1-1
Every report column has the following attributes to
configure: (’C’ - The column number)
STANDARD_MENU_P
ART
States from where the standard menu part is fetched. It can be a
text file or a named program.
Syntax: ’logical path’/’file name’ or .my_named_program
Examples:
B_LANG/STAN_MN.TXT
.DEFINE_ST_MENU_BAR
SPECIFIC_MENU_PA
RT
States from where the specific menu part is fetched. It can be a
text file or a named program. Please see examples above.
HELP_MENU_PART
States from where the help menu part is fetched. It can be a text
file or a named program. Please see examples above.
STANDARD_MENU_A
CTION
States from where the standard menu part program is fetched. It
can be a text file or a named program. Please see examples
above.
SPECIFIC_MENU_AC
TION
States from where the specific menu part program is fetched. It
can be a text file or a named program. Please see examples
above.
HELP_MENU_ACTION States from where the help menu part is program fetched. It can
be a text file or a named program. Please see examples above.
Attribute
Meaning
Default
TITLE’C’
The report column title
""
DATAS’C’
The name(s) of the report objects
""
DESIM’C’
The number of decimals
2
64
1MRS751886-MEN
LIB 510 Configuration
LIB 510
5. Measurement reports 2
Configuration Guide
Table 5.4.3.1-2
Attribute details
Every report page, too, has the following additional attributes to configure:
Table 5.4.3.1-3
Configurable report page attributes
!
When adding new report pages to the column configuration file, make sure that
every report page starts with the notation ##BEGIN_OF_REPORT_PAGE and ends
with the notation ##END_OF_REPORT_PAGE.
The operation to be calculated within the report column works as follows:
EDIT’C’
Enable/Disable Edit
FALSE
MMAN’C’
Enable/Disable Manual Tagging
FALSE
OPER’C’
The operation to be calculated
""
Attribute
Meaning
Default
TITLE’C’
The report column title. The title of the column will be shown on top of
the column.
Data type: Vector, max. 8 characters per vector element
DATAS’C’
The name(s) of the report objects to be shown within the report
column.
Data type: Text, if there is only one report object to be shown, and text
vector, if there are more than one report object to be shown
DESIM’C’
The number of decimals to be shown within the report column.
Data type: Integer
EDIT’C’
States if report object values can be edited or not.
Data type: Boolean
Note! As a basic rule, when only one report object is shown within the
report column, and the report object is not calculated from other report
objects, this attribute can be set to true
MMAN’C’
States if edited values will be tagged as "manually entered".
Data type: Boolean
Note! This attribute is active only if EDIT’C’ attribute is set to true. If
the attribute is set to true, the tracing of edited values is also activated.
OPER’C’
The operation to be calculated within the report column.
Data type: Text string or vector with the #RETURN statement
Note! If operation method is not defined and there is more than one
report object defined within the report column, the sum of the values
will be calculated as default.
Note! If the report is defined in weekly … yearly basis, the sum of the
period values of the day will be calculated as in day value by default
regardless of number of report objects defined within the report
column. Thus, if the defined report is used e.g. as in current report
(mean values calculated), the operation to be calculated within the
report column has to be defined (e.g.
"MEAN(%OBJ)
)
Attribute
Meaning
Default
PAGE_TITLE
The report page title
""
COLUMNS
The number of columns in use
10
1MRS751886-MEN
LIB 510
65
LIB 510 Configuration
Configuration Guide
5. Measurement reports 2
5
All the arithmetical functions supported by SCIL can be used. In the table below, all
the common arithmetical functions are shortly described.
Table 5.4.3.1-4
Arithmetical functions and their explanations
• If only one report object is defined to be shown within the report column, it can
be referenced with the variable %OBJ. The variable includes the measured values
of the row in question. (If one hour is shown on the row of the report picture and
base period cycle within the report application is 15 min, the variable holds 4
values. If a day is shown in the row of the report picture, the variable holds 96
values etc.) The data type of the variable: Vector
• If several report objects are defined to be shown within the report column, a
single object can be referenced with the variable %OBJ’vector element
index’
. The data type of the variable: Vector
• The column object can be referenced with the variable %COL’column
number’
. Column object has to be calculated before making a quotation to it.
The data type of the argument: Vector
• When the calculation procedure is defined by SCIL programming, the variable
type (@OPER’C’) must be a text vector containing a #RETURN statement. The
result type of the calculation operation may be integer, real or a vector of the
types.
Example:
@DATAS’C’ = "BAY1_EN"
@OPER’C’ = ("@RES = SUM(%OBJ)",-
"#IF %RES(1) > 10 #THEN #RETURN 1",-
"#ELSE #RETURN 0")
!
If the report in question is defined in weekly … yearly basis, the sum of the period
values of the day will be calculated as in day value by default. Thus, if the defined
report is used e.g. as in current report (mean values calculated), the operation to be
calculated within the report column has to be defined, e.g. "MEAN(%OBJ)"
Arithmetical Functions
Explanation
ABS(arg)
The absolute value of the argument
SUM(vector)
The sum of all the elements in a vector
MEAN(vector)
The mean value of all the elements in a vector
HIGH(vector)
The largest element in a vector
LOW(vector)
The smallest element in a vector
MIN(arg1,arg2,...)
The smallest value in the argument list
MAX(arg1,arg2,...)
The largest value in the argument list
66
1MRS751886-MEN
LIB 510 Configuration
LIB 510
5. Measurement reports 2
Configuration Guide
5.4.3.2.
An example of the report column settings
Code
Remarks
##BEGIN_OF_REPORT_PAGE
Start of the first report page
@PAGE_TITLE = "My Station"
Title text for the report page (shown in combo box
on the right corner of the report picture)
@COLUMNS = 10
Number of the columns in use (max. 10)
@C 1
The column number
@TITLE’C’ = ("Bay","HA1")
The title of the column
@DATAS’C’ = "BAY1_EN"
The name of the report object
@DESIM’C’ = 2
The number of decimals
@EDIT’C’ = TRUE
Editing of period values enabled
@MMAN’C’ = TRUE
Tracing of edited values is enabled
@OPER’C’ = ""
Operation to be calculated, none (the object
values are shown)
@C 2
The column number
@TITLE’C’ = ("Bay","HA2")
The title of the column
@DATAS’C’ = "BAY2_EN"
The name of the report object
@DESIM’C’ = 2
The number of decimals
@EDIT’C’ = FALSE
Editing of period values disabled
@MMAN’C’ = FALSE
Tracing of edited values is disabled
@OPER’C’ = ""
Operation to be calculated, none (the object
values are shown)
@C 3
The column number
@TITLE’C’ = ("Bay", "HA3")
The title of the column
@DATAS’C’ = ("BAY3_EN1","BAY3_EN2")
The names of the report objects
@DESIM’C’ = 2
The number of decimals
@EDIT’C’ = FALSE
Editing of period values disabled (because of the
several report objects defined to be shown within
the report column)
@MMAN’C’ = FALSE
Tracing of edited values is disabled
@OPER’C’ = ""
Operation to be calculated, none (sum of the
objects is calculated as default)
@C 4
The column number
@TITLE’C’ = ("Bay","HA4")
The title of the column
@DATAS’C’ = ("BAY4_EN1","BAY4_EN2")
The name of the report objects
@DESIM’C’ = 2
The number of decimals
@EDIT’C’ = FALSE
Editing of period values disabled (because of the
several report objects defined to be shown within
the report column)
1MRS751886-MEN
LIB 510
67
LIB 510 Configuration
Configuration Guide
5. Measurement reports 2
5
@MMAN’C’ = FALSE
Tracing of edited values is disabled
@OPER’C’ = "%OBJ1-%OBJ2"
Operation to be calculated, difference of the
objects is calculated
@C 5
The column number
@TITLE’C’ = ("Total","Energy")
The title of the column
@DATAS’C’ = ""
The names of the report objects
@DESIM’C’ = 2
The number of decimals
@EDIT’C’ = FALSE
Editing of period values disabled
@MMAN’C’ = FALSE
Tracing of edited values is disabled
@OPER’C’ = "%COL1+%COL2+%COL3+%COL4"
Operation to be calculated, sum of the columns 1
- 4 is calculated.
Note! No report object defined within the column
@C 6
The column number
@TITLE’C’ = ("Peak","value")
The title of the column
@DATAS’C’ = ""
The name of the report object
@DESIM’C’ = 2
The number of decimals
@EDIT’C’ = FALSE
Editing of period values disabled
@MMAN’C’ = FALSE
Tracing of edited values is disabled
@OPER’C’ =
"MAX(%COL1,%COL2,%COL3,%COL4)"
Operation to be calculated, the largest value is
calculated
Note! No report object defined within the column
@C 7
The column number
@TITLE’C’ = ("Mean of","Bay HA1")
The title of the column
@DATAS’C’ = "BAY1_EN"
The name of the report object
@DESIM’C’ = 2
The number of decimals
@EDIT’C’ = FALSE
Editing of period values disabled
@MMAN’C’ = FALSE
Tracing of edited values is disabled
@OPER’C’ = "MEAN(%OBJ)"
Operation to be calculated, the mean value is
calculated
Note! To be used e.g. with current reports, if the
defined report is done in weekly … yearly basis
@C 8
The column number
@TITLE’C’ = ("Max of","Bay HA1")
The title of the column
@DATAS’C’ = "BAY1_EN"
The name of the report object
@DESIM’C’ = 2
The number of decimals
@EDIT’C’ = FALSE
Editing of period values disabled
@MMAN’C’ = FALSE
Tracing of edited values is disabled
@OPER’C’ = "HIGH(%OBJ)"
Operation to be calculated, the maximum value
is calculated
Note! To be used e.g. with current reports, if the
defined report is done in weekly … yearly basis
Code
Remarks
68
1MRS751886-MEN
LIB 510 Configuration
LIB 510
5. Measurement reports 2
Configuration Guide
5.5.
Miscellaneous
5.5.1.
Summer time - normal time
If Daylight saving from the Application Settings is set in use, the system time will
be automatically changed from normal time to summer time and vice versa. The
change of time is taken into account in the LIB 510 Measurement Reports as
follows:
• In the autumn, the report values of the extra hour are automatically moved to the
highest index or indexes (dependent on the base period) of the data object. The
extra hour is taken into account when e.g. the day sums are calculated.
• In the Daily reports the daylight saving note will be shown in the information bar
in that specific day when the daylight saving time has been activated. The extra
hour values can also be seen and corrected in that specific day by selecting the
Show Leap Hour option in the Tools menu.
In the spring, the values of the hour in question will be unlogged.
@C 9
The column number
@TITLE’C’ = ("Min of","Bay HA1")
The title of the column
@DATAS’C’ = "BAY1_EN"
The name of the report object
@DESIM’C’ = 2
The number of decimals
@EDIT’C’ = FALSE
Editing of period values disabled
@MMAN’C’ = FALSE
Tracing of edited values is disabled
@OPER’C’ = "LOW(%OBJ)"
Operation to be calculated, the minimum value is
calculated
Note! To be used e.g. with current reports, if the
defined report is done in weekly … yearly basis
@C 10
The column number
@TITLE’C’ = ("","")
The title of the column
@DATAS’C’ = ""
The name of the report object
@DESIM’C’ = 2
The number of decimals (default: 2)
@EDIT’C’ = FALSE
Editing of period values disabled (default)
@MMAN’C’ = FALSE
Tracing of edited values is disabled (default)
@OPER’C’ = ""
Operation to be calculated, none (default)
##END_OF_REPORT_PAGE
End of the first report page
##BEGIN_OF_REPORT_PAGE
Start of the second report page
##END_OF_REPORT_PAGE
End of the second report page
Code
Remarks
1MRS751886-MEN
LIB 510
69
LIB 510 Configuration
Configuration Guide
5. Measurement reports 2
5
!
When using the reports, it is recommended to define the point of time change to a
few minutes past an even hour (i.e. execution delay time for period values is
exceeded) in order to enable calculation update for period values before the time
settings. It is also recommended that the time settings will take place before the next
period cycle routines have been executed.
5.5.2.
Troubleshooting
In case of an error in the Report Column Settings, the following error messages will
be shown:
• If the report page start notation ##BEGIN_OF_REPORT_PAGE or end notation
##END_OF_REPORT_PAGE
is missing, an information dialog is shown and an
erroneous page is discarded.
• If collecting report object values fails because the current report object does not
exist or because there is some error in the calculation, the erroneous status is
shown in the current column and erroneous lines are shown in the System
Message dialog. In case of an error in the sampling of process data or in data
calculation, please see the MicroSCADA Notification Window.
70
1MRS751886-MEN
LIB 510 Configuration
LIB 510
5. Measurement reports 2
Configuration Guide
)LJ
([DPSOHRIWKHHUURULQWKH5HSRUW&ROXPQVHWWLQJV
5.5.3.
General data reading and writing procedures
In case that User-defined Groups and Procedures are used within the report
application, it is recommended to use general data reading and writing procedures
within the user-defined procedures when reading or writing values into the report
database.
5.5.3.1.
Data reading and writing procedures
Procedures consist of reading, index calculation and writing components.
Components will be distinct for a period and for sampled values. Database structure
and time intervals for sampled and period values are dependent on the application
specific definitions which are configured by the user. (Please see Section 5.3.2.2. for
details.)
General reading and writing components are called with specific arguments and they
return a specific value.
1MRS751886-MEN
LIB 510
71
LIB 510 Configuration
Configuration Guide
5. Measurement reports 2
5
5.5.3.2.
Procedures
The following procedures apply for sampled values:
• BGU_READSF:C for reading values from the database
• BGU_WRITSF:C for writing values to the database
• BGU_INDSF:C for index calculation, used by the reading and writing procedures
The following procedures apply for period values:
• BGU_READPF:C for reading values from the DB
• BGU_WRITPF:C for writing values to the DB
• BGU_INDPF:C for index calculation, used by the reading and writing procedures
5.5.3.3.
Interface for sampled values
Data object values are time related in such a way that every time period has an index
of its own in the database. The index is not fixed, but depends on the history length
and time.
The following arguments and return values will be used within the reading and
writing procedures:
Procedure BGU_READSF:C
Table 5.5.3.3-1
Arguments
Table 5.5.3.3-2
Return value: list DATA:V with the following attribute
Procedure BGU_WRITSF:C
Table 5.5.3.3-3
Arguments
Name
Description
Data type
DATA_ID
Data object name (= LN attribute)
text
T1
Start time (has to be within the desired time period)
time
T2
End time (has to be within the desired time period)
time
Name
Description
Data type
OV
Object data
real vector
OS
Object status codes
integer vector
RT
Object registration times
time vector
IX
Object indexes of the returned values in the data object
integer vector
LE
Number of elements in the result vectors above
integer
Name
Description
Data type
DATA_ID
Data object name (= LN attribute)
text
T1
Start time (has to be within the desired time period)
time
T2
End time (has to be within the desired time period)
time
OV
Data object values within status information
vector
72
1MRS751886-MEN
LIB 510 Configuration
LIB 510
5. Measurement reports 2
Configuration Guide
Table 5.5.3.3-4
Return value
!
When using the writing procedures, make sure NOT to override any meaningful data
used by other LIB 5xx software. The storing of new values may cause an application
malfunction.
5.5.3.4.
Interface for period values
Data object values are time related in such a way that every time period has an index
of its own in the database e.g. when the selected base period frequency is one hour,
the first hour of the year has an index 1, the second hour has the index 2 etc.
The following input and output parameters will be used within the reading and
writing procedure:
Procedure BGU_READPF:C
Table 5.5.3.4-1
Arguments
Table 5.5.3.4-2
Return value: list DATA:V with the following attributes
Procedure BGU_WRITPF:C
Table 5.5.3.4-3
Arguments
Name
Description
Data type
S
Status code of the operation
real vector
Name
Description
Data type
DATA_ID
Data object name (= LN attribute)
text
T1
Start time (has to be within the desired time period)
time
T2
End time (has to be within the desired time period)
time
Name
Description
Data type
OV
Object data
real vector
OS
Object status codes
integer vector
RT
Object registration times
time vector
IX
Object indexes of the returned values in the data
object
integer vector
LE
number of elements in the result vectors above
integer
Name
Description
Data type
DATA_ID
Data object name (= LN attribute)
text
T1
Start time (has to be within the desired time period)
time
T2
End time (has to be within the desired time period)
time
OV
Data object values within status information
vector
1MRS751886-MEN
LIB 510
73
LIB 510 Configuration
Configuration Guide
5. Measurement reports 2
5
Table 5.5.3.4-4
Return value
!
When using the writing procedures, make sure NOT to override any meaningful data
used by other LIB 5xx software. The storing of new values may cause an application
malfunction.
5.6.
Application engineering information
5.6.1.
Picture modifications
If the application specific modifications to the report components are needed, copy
the due report component to the directory /APLMOD4 and do the modifications
there. Report components are always searched first from the /APLMOD4, when
pictures are run.
5.6.2.
Colour definitions
In the tabular form of the report picture, the column values are presented by different
colours. The colour of the value gives additional information on the value.
Table 5.6.2-1
The value colour gives additional information on the value.
The following colours also apply for status symbols:
Table 5.6.2-2
Following colours apply for status symbols.
5.6.3.
Picture setup
The Measurement Reports 2 includes a setup file where the following settings are
defined:
• Default directory for the reports
• Extension for ASCII files
• Extension for CSV files
• Column separator in CSV files
• Name of the note dialog
Name
Description
Data type
S
Status code of the operation
real vector
Colour
Status
Colour definition
Black
Historical data
("M",14)
White
Predicted data
("M",15)
Brown
Column selected for editing
("M",28)
White, background
Value selected for editing
("M",27)
Colour
Status
Colour definition
Magenta
Uncertain or obsolete
("M",30)
Cyan
Manually entered
("M",29)
74
1MRS751886-MEN
LIB 510 Configuration
LIB 510
5. Measurement reports 2
Configuration Guide
• Name of the edit dialog
• Default line width for trend curves in the graphical form
• Default background colour for graphical window in the graphical form
• Default colours for trend curves in the graphical form
If application specific modifications are needed, copy the setup file (lib4/fmod/
reports2/use/fmu_setup.txt) to the directory /APLMOD4 and do the modifications
there.
5.6.4.
Menu configuration for reports
In order to add defined report pictures to the standard menu part, please use the
Menu Configuration Tool. Please note that when adding the Quick report picture to
the menu part (if it does not already exist), the picture name F_USE/FMU_QUICKA
has to be used.
5.6.5.
Quick report picture configuration
If application specific modifications to the Quick report base picture function are
needed (fmu_quicka.pic), the Quick report base picture function has the following
attributes to configure with the Standard Configuration Tool:
Table 5.6.5-1
Configurable attributes
Attribute
Meaning
Default
PICTURE_HEADER
The title of the picture
Quick Report
REPORT_TYPE
The type of the report
-
REPORT_UNIT
The unit of the report
-
REPORT_SCALE
The general unit scale factor of the report 1
SUMMARY_INFO_1
States the summary information to be
shown on the first row of the summary
information bar
SUM
SUMMARY_INFO_2
States the summary information to be
shown on the second row of the summary
information bar
MEAN
SUMMARY_INFO_3
States the summary information to be
shown on the third row of the summary
information bar
MIN
SUMMARY_INFO_4
States the summary information to be
shown on the fourth row of the summary
information bar
MAX
EDITABLE_ID_TYPES States the report object types that can be
edited in the Quick report
"MS","MM","MN","MX","
MP", "EN","GA"
MARKABLE_ID_TYPE
S
States the report object types that are
tagged as "manually entered" when
values are edited in the Quick report
"MS","MM","MN","MX","
MP", "GA"
FORECAST_AREA_E
NABLED
States whether the forecast area is to be
used within the report or not.
TRUE
AUTHORIZATION_GR
OUP
The name of the authorization group
REPORTS
1MRS751886-MEN
LIB 510
75
LIB 510 Configuration
Configuration Guide
5. Measurement reports 2
5
5.6.6.
Automatic report printing
Because the Measurement Reports 2 uses a VS Printer object, automatic report
printing cannot be done by conventional means. That is why it is not supported by
the Measurement Reports 2.
If automatic report printing is needed despite of that, the following steps must be
applied:
Create command procedures for automatic report printing and for printer
configuration
Table 5.6.6-1
Command procedures for automatic report printing and for
printer configuration
Instruction files are located in the LIB4/FMOD/REPORTS2/USE directory.
Define variables in the setup procedure for automatic report printing
Define printer setup (printer port and PCL printer commands, please see printer
manual for further details)
STANDARD_MENU_P
ART
The place of the standard menu part
B_LANG/
BGU_H1STMN.TXT
SPECIFIC_MENU_PA
RT
The place of the specific menu part
F_LANG/FMU_
D1SPMN.TXT
HELP_MENU_PART
The place of the help menu part
B_LANG/BGU_
H1HLMN.TXT
STANDARD_MENU_A
CTION
The place of the standard menu action
B_USE/BGU_
H1STAC.TXT
SPECIFIC_MENU_AC
TION
The place of the specific menu action
F_USE/FMU_
D1SPAC.TXT
HELP_MENU_ACTIO
N
The place of the help menu action
B_USE/BGU_
H1HLAC.TXT
Attribute
Meaning
Default
Object
Instruction file
Object
FMU_APR
FMU_APR.CIN
Setup procedure for automatic report printing
FMU_APRH
FMU_APRH.CIN
Automatic report printing of hour reports
FMU_APRD
FMU_APRD.CIN
Automatic report printing of day reports
FMU_APRW
FMU_APRW.CIN
Automatic report printing of week reports
FMU_APRM
FMU_APRM.CIN
Automatic report printing of month reports
FMU_APRY
FMU_APRY.CIN
Automatic report printing of year reports
FMU_APRF1
FMU_APRF1.CIN
Fetch values from the report database (Part 1)
FMU_APRF2
FMU_APRF2.CIN
Fetch values from the report database (Part 2)
FMU_PRN1
FMU_PRN1.CIN
Print reports to a net printer (Part 1), printer setup
FMU_PRN2
FMU_PRN2.CIN
Print reports to a net printer (Part 2), convert
characters
76
1MRS751886-MEN
LIB 510 Configuration
LIB 510
5. Measurement reports 2
Configuration Guide
Create time channels for report printing.
5.6.7.
Files in the measurement reports 2
5.6.7.1.
Pictures
The following pictures are located in the LIB4/FMOD/REPORTS2/USE directory:
Table 5.6.7.1-1
Pictures and their functionalities
5.6.7.2.
Other files
The following text files are located in the LIB4/FMOD/REPORTS2/USE directory:
Picture
Functionality
FMU_BASKA.PIC
Report Basket dialog
FMU_CMTXTA.PIC
Comment Text dialog
FMU_DSELA.PIC
Select Day dialog
FMU_DTABA.PIC
Tabular form picture for daily report, time resolution: 1 hour
FMU_DTABB.PIC
Tabular form picture for daily report, time resolution: 30 min
FMU_DTABC.PIC
Tabular form picture for daily report, time resolution: 15 min
FMU_EDITA.PIC
Edit Value dialog (Copy-Paste functionality included)
FMU_EDITB.PIC
Edit Value dialog (Copy-Paste functionality not included)
FMU_EDITYA.PIC
Edit Y-axis Parameters dialog
FMU_GRAPHA.PIC
Graphical form picture for reports
FMU_GRAPHB.PIC
Graphical form picture for reports
FMU_GRAPHC.PIC
Graphical form picture for reports
FMU_HSELA.PIC
Select Hour dialog
FMU_HTABA.PIC
Tabular form picture for daily report
FMU_LEAPHA.PIC
Show Leap Hour dialog
FMU_LISTA.PIC
Standard list picture function
FMU_MRKA.PIC
Note dialog
FMU_MSELA.PIC
Select Month dialog
FMU_MTABA.PIC
Tabular form picture for daily report
FMU_PRCFGA.PIC
Save Preconfiguration dialog
FMU_PRCFGB.PIC
Save Preconfiguration dialog
FMU_QUICKA.PIC
Report base picture function for quick report (Base for 4.0.2)
FMU_QUICKB.PIC
Tabular form picture for quick report
FMU_QUICKC.PIC
Report base picture function for quick report (Base for 4.0.3)
FMU_SAVEA.PIC
Save Report Page to File dialog
FMU_WSELA.PIC
Select Week dialog
FMU_WTABA.PIC
Tabular form picture for weekly report
FMU_YSELA.PIC
Select Year dialog
FMU_YTABA.PIC
Tabular form picture for yearly report
FORM4FMBI1.PIC
Format picture for report alarm object
1MRS751886-MEN
LIB 510
77
LIB 510 Configuration
Configuration Guide
5. Measurement reports 2
5
(The use of the files marked with * is not supported by the Measurement Reports 2)
Table 5.6.7.2-1
Text files and their functionalities
Text file
Functionality
FMU_CONFA.CFG
Report configuration file
FMU_CONFB.CFG
Report configuration file
FMU_CONFC.CFG
Report configuration file
FMU_APR.CIN *
Report instruction file for the command procedure
FMU_APRD.CIN *
Report instruction file for the command procedure
FMU_APRF1.CIN *
Report instruction file for the command procedure
FMU_APRF2.CIN *
Report instruction file for the command procedure
FMU_APRH.CIN *
Report instruction file for the command procedure
FMU_APRM.CIN *
Report instruction file for the command procedure
FMU_APRW.CIN *
Report instruction file for the command procedure
FMU_APRY.CIN *
Report instruction file for the command procedure
FMU_DOCUM.CIN
Report instruction file for the command procedure
FMU_GLOBAL.CIN
Report instruction file for the command procedure
FMU_MMAN.CIN
Report instruction file for the command procedure
FMU_PFCAL1.CIN
Report instruction file for the command procedure
FMU_PFCAL2.CIN
Report instruction file for the command procedure
FMU_PFCAL3.CIN
Report instruction file for the command procedure
FMU_PFCLBK.CIN
Report instruction file for the command procedure
FMU_PFCLN.CIN
Report instruction file for the command procedure
FMU_PFIND.CIN
Report instruction file for the command procedure
FMU_PFREAD.CIN
Report instruction file for the command procedure
FMU_PFSRT.CIN
Report instruction file for the command procedure
FMU_PFSUM1.CIN
Report instruction file for the command procedure
FMU_PFSUM2.CIN
Report instruction file for the command procedure
FMU_PFUCLN.CIN
Report instruction file for the command procedure
FMU_PFUDEF.CIN
Report instruction file for the command procedure
FMU_PFUPD.CIN
Report instruction file for the command procedure
FMU_PFWRT.CIN
Report instruction file for the command procedure
FMU_PRN1.CIN *
Report instruction file for the command procedure
FMU_PRN2.CIN *
Report instruction file for the command procedure
FMU_SFCAL1.CIN
Report instruction file for the command procedure
FMU_SFCAL2.CIN
Report instruction file for the command procedure
FMU_SFCLBK.CIN
Report instruction file for the command procedure
FMU_SFCLN.CIN
Report instruction file for the command procedure
FMU_SFIND.CIN
Report instruction file for the command procedure
FMU_SFREAD.CIN
Report instruction file for the command procedure
FMU_SFSRT.CIN
Report instruction file for the command procedure
78
1MRS751886-MEN
LIB 510 Configuration
LIB 510
5. Measurement reports 2
Configuration Guide
5.6.7.3.
Language text files
The following text files are located in the LIB4/FMOD/REPORTS2/LANG0
directory:
FMU_SFSUM.CIN
Report instruction file for the command procedure
FMU_SFUCLN.CIN
Report instruction file for the command procedure
FMU_SFUDEF.CIN
Report instruction file for the command procedure
FMU_SFUPD.CIN
Report instruction file for the command procedure
FMU_SFWRT.CIN
Report instruction file for the command procedure
FMU_STUPF.CIN
Report instruction file for the command procedure
FMU_STUSF.CIN
Report instruction file for the command procedure
FMU_STUPD1.CIN
Report instruction file for the command procedure
FMU_STUPD2.CIN
Report instruction file for the command procedure
FMU_STUPD3.CIN
Report instruction file for the command procedure
FMU_STUPD4.CIN
Report instruction file for the command procedure
FMU_SUMMER.CIN
Report instruction file for the command procedure
FMU_WINTER.CIN
Report instruction file for the command procedure
FMU_D1SPAC.TXT
Text file for daily report Tools menu action (Base for 4.02)
FMU_D1SPMN.MNU
Text file for daily report Tools menu action (Base for 4.03)
FMU_DBCHK.TXT
Text file for the report database check action
FMU_H1SPAC.TXT
Text file for hourly report Tools menu action (Base for 4.0.2)
FMU_H1SPMN.MNU
Text file for hourly report Tools menu action (Base for 4.0.3)
FMU_INIT.TXT
Text file for system start-up action
FMU_INIT_1.TXT
Text file for system start-up action
FMU_INIT_2.TXT
Text file for system start-up action
FMU_M1SPAC.TXT
Text file for monthly report Tools menu action (Base for 4.0.2)
FMU_M1SPMN.MNU
Text file for monthly report Tools menu action (Base for 4.0.3)
FMU_PRCFG.TXT
Text file for preconfigurations
FMU_Q1SPAC.TXT
Text file for quick report Tools menu action (Base for 4.0.2)
FMU_Q1SPMN.MNU
Text file for quick report Tools menu action (Base for 4.0.3)
FMU_RECONS.TXT
Text file for the report database reconstruct action
FMU_SETUP.TXT
Text file for report picture setup
FMU_VERSION.TXT
Text file for report version info
FMU_W1SPAC.TXT
Text file for weekly report Tools menu action (Base for 4.0.2)
FMU_W1SPMN.MNU
Text file for weekly report Tools menu action (Base for 4.0.3)
FMU_Y1SPAC.TXT
Text file for yearly report Tools menu action (Base for 4.0.2)
FMU_Y1SPMN.MNU
Text file for yearly report Tools menu action (Base for 4.0.3)
PATH4_F9.TXT
Path file
UPDA4_F9.TXT
Update file
Text file
Functionality
1MRS751886-MEN
LIB 510
79
LIB 510 Configuration
Configuration Guide
5. Measurement reports 2
5
Table 5.6.7.3-1
Language text files and their functionalities
5.6.7.4.
Help text files
The following help files are located in the LIB4/FMOD/REPORTS2/LANG0
directory:
Table 5.6.7.4-1
Help text files and their functionalities
Text file
Functionality
FMI_TEXTS.TXT
Text file for report base picture function installation
FMU_D1SPMN.TXT
Text file for daily report Tools menu
FMU_H1SPMN.TXT
Text file for hourly report Tools menu
FMU_INFO.TXT
Text file for report info texts
FMU_M1SPMN.TXT
Text file for monthly report Tools menu
FMU_TEXTS.TXT
Text file for report HSI pictures
FMU_W1SPMN.TXT
Text file for weekly report Tools menu
FMU_Q1SPMN.TXT
Text file for quick report Tools menu
FMU_Y1SPMN.TXT
Text file for yearly report Tools menu
FORM4FMBI1.TXT
Text file for report alarm object format picture
Help file
Functionality
FMI_DBASE.HLP
Help file for daily report base picture function
FMI_HBASE.HLP
Help file for hourly report base picture function
FMI_MBASE.HLP
Help file for monthly report base picture function
FMI_QBASE.HLP
Help file for quick report base picture function
FMI_TOOLAA.HLP
Help file for Report Configuration Tool
FMI_TOOLAB.HLP
Help file for Report Configuration Tool
FMI_TOOLAC.HLP
Help file for Report Configuration Tool
FMI_TOOLC.HLP
Help file for Report Configuration Tool
FMI_WBASE.HLP
Help file for weekly report base picture function
FMI_YBASE.HLP
Help file for yearly report base picture function
FMU_BASKA.HLP
Help file for report basket dialog
FMU_DSELA.HLP
Help file for select day dialog
FMU_DTAB.HLP
Help file for daily report
FMU_EDITA.HLP
Help file for edit values dialog
FMU_EDITY.HLP
Help file for edit y-axis parameters dialog
FMU_HSELA.HLP
Help file for select hour dialog
FMU_HTAB.HLP
Help file for hourly report
FMU_MRKA.HLP
Help file for note dialog
FMU_MSELA.HLP
Help file for select month dialog
FMU_MTAB.HLP
Help file for monthly report
FMU_PRCFG.HLP
Help file for save preconfiguration dialog
FMU_QUICK.HLP
Help file for quick report
80
1MRS751886-MEN
LIB 510 Configuration
LIB 510
5. Measurement reports 2
Configuration Guide
5.6.7.5.
Configuration files
The following configuration files are located in the LIB4/ FMOD/REPORTS2/
INST directory:
Table 5.6.7.5-1
Configuration files and their functionalities
FMU_SAVEA.HLP
Help file for save report page to file dialog
FMU_WSELA.HLP
Help file for select week dialog
FMU_WTAB.HLP
Help file for weekly report
FMU_YSELA.HLP
Help file for select year dialog
FMU_YTAB.HLP
Help file for yearly report
Help file
Functionality
Configuration file
Functionality
FMI_COLUMNS.TXT
Report Column Setting file
FMI_CREATE.TXT
Report configuration file for creating time channels, command
procedures, alarm points and interconnections.
FMI_DBASE.DAT
Report configuration file for daily report base picture function
FMI_DBASE.TXT
Report configuration file for daily report base picture function
FMI_DBASEA.PIC
Report base picture function for daily report, time resolution: 1
hour (Base for 4.0.2)
FMI_DBASEB.PIC
Report base picture function for daily report, time resolution: 30
min (Base for 4.0.2)
FMI_DBASEC.PIC
Report base picture function for daily report, time resolution: 15
min (Base for 4.0.2)
FMI_DBASED.PIC
Report base picture function for daily report, time resolution: 1
hour (Base for 4.0.3)
FMI_DBASEE.PIC
Report base picture function for daily report, time resolution: 30
min (Base for 4.0.3)
FMI_DBASEF.PIC
Report base picture function for daily report, time resolution: 15
min (Base for 4.0.3)
FMI_HBASE.DAT
Report configuration file for hourly report base picture function
FMI_HBASE.PIC
Report base picture function for hourly report (Base for 4.0.2)
FMI_HBASE2.PIC
Report base picture function for hourly report (Base for 4.0.3)
FMI_MBASE.DAT
Report configuration file for monthly report base picture
function
FMI_MBASE.PIC
Report base picture function for monthly report (Base for 4.0.2)
FMI_MBASE.PIC
Report base picture function for monthly report (Base for 4.0.2)
FMI_QBASE.DAT
Report configuration file for quick report base picture function
FMI_QBASE.TXT
Report configuration file for quick report base picture function
FMI_QBASE.PIC
Report base picture function for quick report (Base for 4.0.2)
FMI_QBASE2.PIC
Report base picture function for quick report (Base for 4.0.3)
FMI_WBASE.DAT
Report configuration file for weekly report base picture function
FMI_WBASE.PIC
Report base picture function for weekly report (Base for 4.0.2)
1MRS751886-MEN
LIB 510
81
LIB 510 Configuration
Configuration Guide
5. Measurement reports 2
5
5.6.7.6.
The process objects
Table 5.6.7.6-1
Process objects
5.6.7.7.
Command procedures
Table 5.6.7.7-1
Command procedures
FMI_WBASE2.PIC
Report base picture function for weekly report (Base for 4.0.3)
FMI_YBASE.DAT
Report configuration file for yearly report base picture function
FMI_YBASE.PIC
Report base picture function for yearly report (Base for 4.0.2)
FMI_YBASE2.PIC
Report base picture function for yearly report (Base for 4.0.3)
FMI_TOOLA.VSO
Report Configuration Tool file
FMI_TOOLB.VSO
Report Configuration Tool file
FMI_TOOLC.VSO
Report Configuration Tool file
INDEX4_F9.TXT
Installation menu file
Configuration file
Functionality
Object Index
Object
FMU_ALARM
10
Report alarm object
Object
Functionality
FMU_DOCUM
Documents all the report command procedures to a file (pict/
fmu_docum.txt)
FMU_GLOBAL
Defines the global variables used within the reports. The global
variables are defined by the end-user from the Application Settings.
FMU_MMAN
Writes edited data to a log file, if tracing of edited values is enabled
FMU_PFACT
Activated at the end of period cycle by FMU_PFSRT:C. Updates the
process object values (update ones).
FMU_PFCAL1
Activated at the end of period cycle by FMU_PFSRT:C (Part 1).
Procedure reads the report object list and updates the current object
values to the report database.
FMU_PFCAL2
Activated at the end of period cycle by FMU_PFSRT:C (Part 2).
Procedure updates all the calculated object values.
FMU_PFCAL3
Activated at the end of period cycle by FMU_PFSRT:C (Part 3).
Procedure updates all the measured values, if sampled values are
stored in the report database within history. Period values are
counted from the sampled values.
FMU_PFCLBK
Call-back method for period values.
FMU_PFCLN
Activated at the end of period cycle by FMU_PFCAL1:C (once a
day). Resets ’old’ period values in the report database.
FMU_PFIND
Index calculations for period values.
FMU_PFREAD
Read period values from the report database with given inputs.
FMU_PFSRT
Activated at the end of period cycle by the time channel FMU_PF:T.
Starts the updating of process values and the updating of report
object values to the report database after execution delay is expired.
82
1MRS751886-MEN
LIB 510 Configuration
LIB 510
5. Measurement reports 2
Configuration Guide
FMU_PFSUM1
Activated by the the report HSI (Part 1). Procedure finds all the
calculated objects in which a given input parameter is included.
FMU_PFSUM2
Activated at the end of period cycle by FMU_PFCAL2:C or the report
HSI (Part 2). Procedure calculates the calculated object values with
given input parameters.
FMU_PFUCLN
Activated at the end of period cycle by FMU_PFCLN:C. If the user-
defined groups are defined, the procedure is executed when the ’old’
period values are reset.
FMU_PFUDEF
Activated at the end of period cycle by FMU_PFSRT:C. If the user
defined groups are defined, the procedure is executed before the
calculated values are updated.
FMU_PFUPD
Activated at the end of period cycle by FMU_PFCAL1. Updates the
object values to the report database with given input parameters.
FMU_PFWRT
Write period values to the report database with given input
parameters.
FMU_SFACT
Activated at the end of sampling cycle by FMU_SFSRT:C. Updates
the process object values (update ones).
FMU_SFCAL1
Activated at the end of sampling cycle by FMU_SFSRT:C (Part 1).
The procedure reads from the report object list all the measured and
calculated objects and updates the current object values to the
report database.
FMU_SFCAL2
Activated at the end of sampling cycle by FMU_SFSRT:C (Part 2).
The procedure updates all the calculated object values (which are
calculated within the sampling period).
FMU_SFCLBK
Call-back method for sampled values.
FMU_SFCLN
Activated at the end of sampling cycle by FMU_SFCAL1:C (once in
an hour). Resets ’old’ sampled values in the report database.
FMU_SFIND
Index calculations for sampled values.
FMU_SFREAD
Read sampled values from the report database with given input
parameters.
FMU_SFSRT
Activated at the end of sampling cycle by the time channel
FMU_SF:T. Starts the updating of process values and the updating
of the measured and calculated report object values to the report
database after execution delay is expired.
FMU_SFSUM
Activated at the end of sampling cycle by FMU_SFCAL2:C. The
procedure calculates the calculated object values with given input
parameters.
FMU_SFUCLN
Activated at the end of sampling cycle by FMU_SFCLN:C. If the
user-defined groups are defined, the procedure is executed when
the ’old’ sampled values are reset.
FMU_SFUDEF
Activated at the end of the sampling cycle by FMU_SFSRT:C. If the
user-defined groups are defined, procedure is executed before the
calculated values are updated.
FMU_SFUPD
Activated at the end of sampling cycle by FMU_SFCAL1. Updates
the object values to the report database with given input parameters.
FMU_SFWRT
Write sampled values to the report database with given input
parameters.
Object
Functionality
1MRS751886-MEN
LIB 510
83
LIB 510 Configuration
Configuration Guide
5. Measurement reports 2
5
FMU_STUPF
Activated at system start-up by FMU_STUPD1:C. If the user-defined
groups are defined, the procedure is executed at system start-up
when a period cycle time is exceeded (Period Groups).
FMU_STUSF
Activated at system start-up by FMU_STUPD1:C. If the user-defined
groups are defined, the procedure is executed at system start-up
when a sampling cycle time is exceeded (Sampled Groups).
FMU_STUPD1
Update the report object data at system start-up (Part 1)
FMU_STUPD2
Update the report object data at system start-up (Part 2)
FMU_STUPD3
Update the report object data at system start-up (Part 3)
FMU_STUPD4
Update the report object data at system start-up (Part 4)
FMU_SUMMER
Update the report objects when daylight saving time has been set
from normal time to summer time.
FMU_WINTER
Update the report objects when daylight saving time has been set
from summer time to normal time.
Object
Functionality
1MRS751886-MEN
LIB 510
85
LIB 510 Configuration
Configuration Guide
6. Guideline for the substa-
tion engineering with LIB
6
6.
Guideline for the substation engineering with
LIB 510
This document describes the guidelines for the MV-substation engineering with LIB
510. This document is just a guideline for installation, not a complete installation
manual. For specific information of an individual standard function installation refer
to the Users Guide of the corresponding standard function.
This document is only valid for LIB 510 revision 4.0.4, and it should be considered
partly as a obsolete with older or newer versions of LIB 510.
The Substation engineering with LIB 510 can be divided into two or three subtasks
depending on weather the Busbar Coloring is used or not:
1. Installation (standard function installation and static picture background editing)
2. Configuration (picture function configuration and database creation)
3. Single line editing (Busbar Coloring)
The two process picture examples used in this configuration manual look like Fig.
6.-1 and Fig. 6.-2 when they are configured and in use. Both are made with bus bar
coloring based on a single line diagram
1MRS751886-MEN
86
1MRS751886-MEN
LIB 510 Configuration
LIB 510
6. Guideline for the sub-
station engineering with
Configuration Guide
)LJ (DVWZLFNVWDWLRQRYHUYLHZDQGN9KRUL]RQWDOEXVEDU
1MRS751886-MEN
LIB 510
87
LIB 510 Configuration
Configuration Guide
6. Guideline for the substa-
tion engineering with LIB
6
)LJ (DVWZLFNN9YHUWLFDOEXVEDU
6.1.
Installation of picture functions
The engineering of the substation single line diagram can be started either by reusing
the existing single line diagram (done by LIB 510 revision 4.0.4) or from the scratch.
For the sake of the reliable functionality it is not recommended to reuse single line
diagram that has been done by other version than the current LIB 510.
When the existing single line diagram is reused, there is nothing more to do than to
relocate existing picture function as a new single line diagram, delete needless ones
and finally install the picture functions that are still missing.
6.1.1.
Main principles
The maximum number of picture functions per picture is 65000. This limitation has
to be observed with large substation single line diagram. The best way to get around
with this limitation is to make several single line diagrams for the substation e.g. a
simplified overview of the substation, a detailed picture of HV busbar, a detailed
picture of MV busbar and substation protection.
88
1MRS751886-MEN
LIB 510 Configuration
LIB 510
6. Guideline for the sub-
station engineering with
Configuration Guide
To simplify a substation single line diagram it is possible to neglect the installation
of the station and bay picture functions as long as those picture functions have
already been installed into another picture of the substation. In the simplified single
line diagram, the Busbar Coloring can be reduced just for indication of the line
potential (line indicator) if the complete installation of the Busbar Coloring has been
done in a another picture(s) i.e. at more detailed single line diagram(s).
The minimum requirement for the substation single line diagram to work properly
is to install the following standard functions:
Table 6.1.1-1
Install at least these standard functions for the substation
single line diagram to work properly
*) Optional, can be hard coded into U_OTHER_OBJECTS
6.1.2. Installation
procedure
With the exception of the BASE-standard function, the installation order is not
critical. When the single line diagram is shown on the monitor, the picture functions
will be updated in the same order as the installation has been done. Therefore it is
advisable to install the most important standard functions first.The proposed
installation order of MV Process and Protection (SPACOM & RED) standard
functions is as follows:
Table 6.1.2-1
The proposed installation order of MV Process and Protection
standard functions
BASE
Background for other standard functions; includes menus,
alarm row, path definitions etc. It should be installed FIRST to
every picture containing LIB 5xx picture functions.
STATION*)
Station standard function; includes station local/remote-switch,
authorization mechanism, station blocking, etc. It should be
installed at least for one of the single line diagrams for every
substation.
BAY*)
Bay standard function for every bay; includes bay local/
remote-switch, interlocking control, bay blocking, etc. It should
be installed for every bay at least for one of the single line
diagrams.
1.
BASE
2.
STATION
3.
BAY
4.
SWITCHING DEVICE
5.
TRANSFORMER
6.
MEASUREMENT
7.
PROTECTION DEVICE
8.
TRIP TAG
9.
AUTO-RECLOSE TAG
10.
LINE SEGMENT, LINE INDICATOR, OTHER PF’S FOR BUSBAR COLORING
11.
ALARM INDICATOR
1MRS751886-MEN
LIB 510
89
LIB 510 Configuration
Configuration Guide
6. Guideline for the substa-
tion engineering with LIB
6
Before starting the picture function installation it is necessary to decide in which
direction the busbar(s) is drawn. By using vertically drawn busbars it is possible to
fit in more feeders to the single line diagram.
If the Busbar Coloring is used, it is necessary to observe the following rules during
installation :
• The picture function with power supply capability should be installed to the
substation i.e. the picture function of generator or line indicator.
• All electrical circuits with possibility to have their own potential should have
corresponding line segment picture function. Typically there is a need for an own
line segment between two or more switching devices or between the switching
device and the active symbol like generator, line indicator, motor, reactor,
capacitor, etc.
• The connection to the ground should be symbolized by installing the picture
function of the earth symbol.
Table 6.1.2-2
During the installation the following information has to be
given
The name of the picture function (ID) should be unique within the same picture, and
it is advisable to use such an identification that is universal, i.e. there is no
identification of any particular substation. This makes sense when copying the
single line diagram (*.PIC) to another name, and then reusing it again for other
projects.
Allowed characters are the letters A-Z, all digits and underscore (_). However the
name of the picture function can not begin with digit or underscore.
In Fig. 6.1.2.-1 the general procedure for installing picture functions to the base
picture is shown.
Attribute
Meaning
Default
PICTURE FUNCTION NAME
(ID)
Name/Identification of the
picture function within picture
-
90
1MRS751886-MEN
LIB 510 Configuration
LIB 510
6. Guideline for the sub-
station engineering with
Configuration Guide
)LJ
6XFFHVVIXOLQVWDOODWLRQRIWKH6ZLWFKLQJ'HYLFHSLFWXUHIXQFWLRQFDOOHG6:WRWKHEDVHSLFWXUH
YLVLEOHLQWKHXSSHUOHIWFRUQHU
After installation, any of the picture functions can be set to a lower or higher drawing
level depending on the respective positioning of each others and static picture
background.
Fig. 6.1.2.-2 presents a substation single line diagram with horizontal busbar after
picture function installation, but the single line editing is not done yet.
1MRS751886-MEN
LIB 510
91
LIB 510 Configuration
Configuration Guide
6. Guideline for the substa-
tion engineering with LIB
6
)LJ
$VLQJOHOLQHGLDJUDPZLWKKRUL]RQWDOEXVEDUDIWHUSLFWXUHIXQFWLRQLQVWDOODWLRQ
Fig. 6.1.2.-3 presents a substation single line diagram with vertical busbar after
picture function installation.
92
1MRS751886-MEN
LIB 510 Configuration
LIB 510
6. Guideline for the sub-
station engineering with
Configuration Guide
)LJ
VLQJOHOLQHGLDJUDPZLWKYHUWLFDOEXVEDUDIWHUSLFWXUHIXQFWLRQLQVWDOODWLRQ
6.1.3.
Static picture background editing
If the Busbar Coloring is not used it is advisable to continue the single line
engineering by drawing the static background i.e. busbar(s), connections between
picture functions, device labels, etc. This is performed by using the ordinary Picture
Editor.
6.2.
Configuration
The configuration of the picture function is necessary to adapt to the standard picture
function for the real process device with proper identification, functionality and
database.
Depending on whether the existing single line diagram is reused or not, the
recommended way of configuring the picture functions may vary a little. If the
engineering has been started from scratch it is recommended to configure the
1MRS751886-MEN
LIB 510
93
LIB 510 Configuration
Configuration Guide
6. Guideline for the substa-
tion engineering with LIB
6
complete station by copying and pasting attributes. When the existing single line
diagram is reused and both substations have almost the same functionality, it might
be easier to modify just the single attributes that are needed to be modified. To avoid
misspelling, especially with station and bay name, it is advisable to copy and paste
attributes as often as possible.
The configuration of the picture function shall be performed by using standard
configuration tools such as:
1. Standard Configuration Tool
2. Representation Tool
3. Process Object Tool
Relays and Terminal picture functions are also configured with the Standard
Configuration Tool concerning attributes. Some additional tools are not available to
other picture functions. For Relays and Terminals the Process Object Tool is not
used. Configuration of Relays and Terminals picture functions is described shortly
in own sections in this manual.
6.2.1.
Preliminary work
Before the configuration of the picture functions can start there are some "configure-
only-once"-type of work to do. The usage of object identification (OI) -attribute has
to be fixed, the naming convention of the process object has to be decided and the
translation of the signal texts to local language has to be performed.
6.2.1.1.
The object identification in the database
Because of the object oriented approach of the MV Process it is very important that
there is a proper way of coding object identification to the database. This has been
achieved by using a new OI-attribute as a storage of the substation, bay and device
identification.
LIB5xx 4.0.3 supports partitioning of the OI-attribute into five (5) identification
fields. If less than five fields will be used, the unused fields has to be the last ones
i.e. the fifth field, fourth field, and so on. As a default only three fields will be used:
Table 6.2.1.1-1
OI-attributes identification fields
The sum of the field lengths should be equal or less than 30 characters.
If utilization of the OI-attribute needs to be modified due to different customer
requirements, the OI-attribute has to be changed before starting the creation of the
application database. This means there should be no process objects in the process
Field
Default length
Range
Station name
10 characters (9 characters + 1 space)
2 .. 28
Bay name
15 characters (14 characters + 1 space)
2 .. 28
Device/apparatus
name
5 characters
0, 2 .. 26 (0 = not in use)
Not specified
0
0, 2 .. 24 (0 = not in use)
Not specified
0
0 .. 22 (0 = not in use)
94
1MRS751886-MEN
LIB 510 Configuration
LIB 510
6. Guideline for the sub-
station engineering with
Configuration Guide
object database. The configuration can be done in SYS_BASCON.COM-file by
APL:BSV15.
MV Process will require substation and bay field to work properly and therefore
field identifier "STA" and "BAY" has been reserved to identify substation and bay
field. Optional device/apparatus field will be identified by "DEV" field identifier.
The following APL:BSV15 definition is a suggestion for the default configuration.
APL:BSV15=LIST(-
PROCESS_OBJECTS=LIST(-
OI=LIST(-
Title1=VECTOR("Substation"),-
Title2=VECTOR("Bay"),-
Title3=VECTOR("Device"),-
Title4=VECTOR(""),-
Title5=VECTOR(""),-
Length1=10,-
Length2=15,-
Length3=5,-
Length4=0,-
Length5=0,-
Field1=VECTOR("STA"),-
Field2=VECTOR("BAY"),-
Field3=VECTOR("DEV"),-
Field4=VECTOR(""),-
Field5=VECTOR("")),-
OX=LIST(-
Title1=VECTOR("Object text"),-
Length1=30)))
The hierarchical structure always has to be maintained while reconfiguring OI-
attribute. The first field defines the biggest group, the second field is a subgroup of
the biggest group and so on. MV Process will require substation and bay field to
work properly.
If the customer needs one additional field for e.g. utility name and region, the
configuration of OI-attribute can be done as it is shown in the following example.
Table 6.2.1.1-2
OI-attributes configuration according to the customer needs
The following APL:BSV15 definition is based on the previous example.
Field
Default length
Example
Utility abbreviation
4 characters (3 characters + 1 space)
ABB
Region abbreviation
2 characters (1 characters + 1 space)
N
Station name
9 characters (8 characters + 1 space)
Eastwick
Bay name
13 characters (12 characters + 1 space)
Incoming HV
Device/apparatus name
2 characters
Q0
1MRS751886-MEN
LIB 510
95
LIB 510 Configuration
Configuration Guide
6. Guideline for the substa-
tion engineering with LIB
6
APL:BSV15=LIST(-
PROCESS_OBJECTS=LIST(-
OI=LIST(-
Title1=VECTOR("Utility"),-
Title2=VECTOR("Region"),-
Title3=VECTOR("Substation"),-
Title4=VECTOR("Bay"),-
Title5=VECTOR("Device"),-
Length1=4,-
Length2=2,-
Length3=9,-
Length4=13,-
Length5=2,-
Field1=VECTOR(""),-
Field2=VECTOR(""),-
Field3=VECTOR("STA"),-
Field4=VECTOR("BAY"),-
Field5=VECTOR("DEV")),-
OX=LIST(-
Title1=VECTOR("Object text"),-
Length1=30)))
6.2.1.2.
The object identification in the application
Because of the obligatory substation and bay identification field in the database,
there is a setting tool which defines how the OI-attribute will be shown in printouts,
event list, alarm list, dialogs, etc.
The configuration of OI-attribute visibility is global, i.e. all function done by LIB
5xx 4.0.3 follows the same definition. The fields starting from the beginning and/or
end of OI-attribute can be defined not visible but not from the middle of OI-attribute.
That is because of the performance requirements.
The setting tool "Show Object Identification" for setting OI-attribute visibility in the
application can be found under "Tools"-menu in "Application Settings".
6.2.1.3.
The naming convention of the database
The naming convention of the process objects should be checked carefully so that
there won’t be any conflicts in the database during installation. As a well proven
naming convention three characters of the substation name, four characters of bay
and two characters of device or apparatus have been used. With proper naming
convention it is easy to navigate in the process object database, and it makes it easier
to copy process objects (related to certain substation) between different applications.
A logical name for process object may contain max. 9 or 10 characters depending on
the standard function. Allowed characters are the letters A-Z, all digits and
underscore (_). However, the name can not begin with digit or underscore.
96
1MRS751886-MEN
LIB 510 Configuration
LIB 510
6. Guideline for the sub-
station engineering with
Configuration Guide
6.2.1.4.
If another language than English is used as a monitor language i.e. as a language for
signal texts in the database, it is necessary to define this local language at least for
the user who is doing the application engineering. It is also very important that the
translation of all database texts has already been done by a Language Converter or
by other means.
6.2.2.
Configuring picture functions
For specific information of a particular picture function configuration please refer to
the installation on-line help or LIB 5xx documentation of the corresponding
standard picture function.
Configuration of the MV Process picture functions shall be performed by using
Standard Configuration Tool (SCT), Representation Tool (RT) and Process Object
Tool (POT) while Relays and Terminal picture functions also use other tools, started
within Standard Configuration Tool. The Standard Configuration Tool is opened by
selecting the picture function to configure and then clicking the short cut key for
Tools in the Picture Editor.
Because of the object oriented approach of MV Process it is very important that the
configurable attributes STATION_NAME, BAY_NAME, DEVICE_NAME and
SPECIAL_IDENTIFIER_x has been defined correctly. All picture functions
belonging to the same substation should have the same text in the configurable
attribute STATION_NAME. Also within one bay the configurable attribute
BAY_NAME should be self-same for all picture functions. The configurable
attribute DEVICE_NAME is not so critical because it is not obligatory. It is
advisable though to use it to identify different switching devices. Please note that the
configurable attributes STATION_NAME, BAY_NAME, DEVICE_NAME and
SPECIAL_ IDENTIFIER_x are all case sensitive i.e. texts ABB, abb and Abb
represent different identifiers for these attributes.
6.2.3.
Standard configuration tool
The Standard Configuration Tool has been assigned for the "normal" configuration
of the attributes. Most of the configurable attributes in MV Process will be defined
by this tool.
The Standard Configuration Tool supports copy and paste functions between all
kinds of picture functions. The copy function will copy all attributes and their values
from the selected picture function and the paste function will restore only the
relevant attributes and their values to the selected picture function. It is practical
(and recommended) to configure one bay first and then just distribute this
configuration by using copy and paste. This speeds up the configuration work since
normally there are only a few configurable attributes which has to be altered from
the first bay configuration compared to keying all data in again and again.
6.2.3.1.
Starting standard configuration tool
The Standard Configuration Tool is started from the Picture Editor, by first selecting
the object to configure, then by clicking the appropriate button. Starting can also be
done from the menu. See example in Fig. 6.2.3.1.-1 for how to start SCT. Fig.
1MRS751886-MEN
LIB 510
97
LIB 510 Configuration
Configuration Guide
6. Guideline for the substa-
tion engineering with LIB
6
6.2.3.1.-1 presents a typical Standard Configuration Tool with attributes of a Circuit
Breaker with Picture Function Name SW3.
)LJ 3URFHGXUHIRUVWDUWLQJWKH6WDQGDUG&RQILJXUDWLRQ7RRO
The Standard Configuration Tool can be resized and moved on the screen. Another
picture function is loaded into the SCT just by clicking on another picture function.
Thereby it is not necessary to exit the SCT before loading another picture function.
The meaning of the configurable attributes can be checked by selecting the
Installation Help from the Standard Configuration Tool.
Other configuration tools which are available for particular picture function can be
opened from the notebook page Tools.
For further information about the Standard Configuration Tool please refer to the
Picture Editing Manual.
98
1MRS751886-MEN
LIB 510 Configuration
LIB 510
6. Guideline for the sub-
station engineering with
Configuration Guide
6.2.4.
Representation tool
The Representation Tool is designed for selecting a proper symbol set(s) for the
graphical display of the picture function.
If there is no appropriate symbol set, it is possible to make and use your own
representation set. In that case you can copy one of the existing representation sets
to an application specific representation file ../APLMOD4/USE/APLMOD4.PIR
under the application and modify each symbol as needed. If object specific
representations are needed, you can rename the representation set (under the
application) and write the name of the representation to the selector with the logical
path.
As a preview of selected representation the Representation Tool shows the symbol
with selector value -1. Therefore it is important to have selector -1 even if it is not
necessary otherwise.
Fig. 6.2.4.-1 presents the Representation Tool with a set of representations for the
circuit breaker.
)LJ
7KH5HSUHVHQWDWLRQ&RQILJXUDWLRQ7RRO
6.2.5.
Process object tool
The Process Object Tool creates/deletes the process object database related to the
selected picture function. The existing process objects for the standard function has
to be deleted and then reinstalled every time when any of the attributes configured
by the Standard Configuration Tool has been modified.
The Process Object Tool has a direct link to the Setting Tool of the Process Objects.
This allows modifications of all configurable attributes of the process object before
creating the database. Usually this link is used to fill in the station number, address
and proper switching state for the process objects. To access to the Setting Tool of
the Process Objects select the process object from the list and press Edit.
(see Fig. 6.2.5.-1) shows the Process Object Tool with a set of process objects for
the circuit breaker. Double clicking the attribute values is the same as clicking the
Edit button.
1MRS751886-MEN
LIB 510
99
LIB 510 Configuration
Configuration Guide
6. Guideline for the substa-
tion engineering with LIB
6
)LJ
7KH3URFHVV2EMHFW7RRO
6.2.6.
Installing and configuring SPACOM relay picture functions
The following steps and tools are required for a SPACOM relay picture function in
MicroSCADA:
1. Installation of the relay picture function. (Installation Tool)
2. Configuration of the relay picture function. (Standard Configuration Tool)
• Attributes
• Rack configuration (Object Configuration Tool)
• Communication settings (Cconfig Tool)
• Event handling (Event Editor)
• Picture function object (Representation Tool)
3. Relay parametrisation (SPA Relay Tool)
Steps one and two are shortly described in the following sections, but relay
parametrisation is beyond the scope of this manual, please see Tools for Relays and
Terminals manual, SPA Relay Tool.
6.2.6.1.
Installing relay picture functions
The document LIB 500 Configuration Manual, Introduction gives a general
description of the principles for installing and configuring picture functions in LIB.
For every relay terminal a separate picture function is added to the process picture.
Please see relevant relay manuals for further information.
When installing a picture function, choose LIB4/LIB 510/PROTECTION/
SPACOM in the Standard Installation Tool. Select SPACOM. After the standard
100
1MRS751886-MEN
LIB 510 Configuration
LIB 510
6. Guideline for the sub-
station engineering with
Configuration Guide
function SPACOM has been highlighted, enter a Picture Function Name for the
function and click the Install button. Place the function anywhere in the base picture.
)LJ 7KHSURFHGXUHIRULQVWDOOLQJDUHOD\SLFWXUHIXQFWLRQUHOD\SLFWXUHIXQFWLRQ63$ZDV
VXFFHVVIXOO\LQVWDOOHGYLVLEOHLQWKHXSSHUOHIWFRUQHU
6.2.6.2.
Relay picture function configuration
The following flowchart shows the procedure of the relay configuration:
1MRS751886-MEN
LIB 510
101
LIB 510 Configuration
Configuration Guide
6. Guideline for the substa-
tion engineering with LIB
6
)LJ 7KHSURFHGXUHRIWKHUHOD\FRQILJXUDWLRQ
The Object Configuration tool is opened from the Tools menu in the Standard
Configuration Tool. The configuration of the relay can be divided into three phases.
1. Rack and module configuration
2. Storing relay specific data to the database
3. Storing picture function data
Phases 1 and 2 are done within the Object Configuration Tool.
Phase 3, storing picture function data, is done using the Standard Configuration Tool
by selecting Apply or Save.
Before starting the configuration, please ensure that the base system objects
concerning the stations and nodes are correctly configured.
6.2.6.3.
Standard configuration tool functions
Select the relay picture function and start the Standard Configuration Tool to alter
the configurable attributes and to start the Object Configuration Tool, see similar
example in (see Fig. 6.2.3.1.-1) on how to start SCT.
The tabs Attributes and Tools are described in this section. The Representation Tool
in the Tools menu is not described.
102
1MRS751886-MEN
LIB 510 Configuration
LIB 510
6. Guideline for the sub-
station engineering with
Configuration Guide
Attributes tab
)LJ 6WDQGDUG&RQILJXUDWLRQ7RROGLDORJZLWKIRFXVRQ$WWULEXWHVWDE
The following attributes can be configured in the Standard Configuration Tool.
Table 6.2.6.3-1
Configurable attributes in the Standard Configuration Tool
Configurable
Choices
STATION_NAME
The name of the substation. As a default the maximum
length of the text is 9 characters. This text will be used as a
substation identifier of the relay objects on event list, alarm
list, printout, database query, etc. It is very important that
this text is similar to all objects within the same substation.
BAY_NAME
The name of the bay/feeder. As a default the maximum
length of the text is 14 characters. This text will be used as a
bay/feeder identifier of the relay objects on event list, alarm
list, printout, database query, etc. It is very important that
this text is similar to all objects within the same bay/feeder.
DEVICE_NAME
The name (identifier) of the relay. As a default the maximum
length of the text is 5 characters. This text will be used as an
identifier of the relay on event list, alarm list, printout,
database query, etc.
1MRS751886-MEN
LIB 510
103
LIB 510 Configuration
Configuration Guide
6. Guideline for the substa-
tion engineering with LIB
6
Saving relay data to the picture function
After the relay has been configured using the relay configuration tools, the data has
to be saved to the picture function, too. This is done by using the Standard
Configuration Tool commands Save attributes or Apply attributes.
Copying picture function data
To copy picture function data and to paste it into another picture function, use the
commands Copy attributes and Paste attributes of the Standard Configuration Tool.
After you have copied the picture function data, open the Object Configuration Tool
and make the necessary definitions (addresses etc.).
Deleting picture function
To delete a picture function, select the option Delete in the Standard Configuration
Tool.
Remember to save the picture function data before you exit the Standard
Configuration Tool.
Tools tab
The following tools can be started from the Tools tab in the Standard Configuration
Tool (Fig. 6.2.6.3.-2):
• Object Configuration Tool for rack configuration (Function described in Tools
for Relays and Terminals Manual)
• Cconfig Tool for communication settings (Function described in Tools for Relays
and Terminals Manual)
• Event Editor for event handling (Function described in LIB 510 4.0.3
Configuration Manual, Event Editor)
• Representation Tool for picture function symbol used for the relay object
AUTHORIZATION GROUP
The authorization group used for the object.
VISIBLE
Visibility of the object.
LIB_OBJECT_NAME
Identifies the relay object. Name should be unique within
the application. The logical names of event process objects
will be created by using this name:LN =
LIB_OBJECT_NAME + GT specific character. (GT specific
character is defined by LIB500 installation tools.) Max.
length of attribute: 9 characters.
Configurable
Choices
104
1MRS751886-MEN
LIB 510 Configuration
LIB 510
6. Guideline for the sub-
station engineering with
Configuration Guide
)LJ 7KH6WDQGDUG&RQILJXUDWLRQ7RROGLDORJER[7RROVWDE
For detailed information about using the Standard Configuration Tool on SPACOM
units, please see Tools for Relays and Terminals Manual.
Relay parametrisation
After configuration of the Relay picture function, the relay module parameters are
set by means of the SPA Relay Tool. For more information, see Tools for Relays and
Terminals Manual, SPA Relay Tool.
6.2.7.
Installing and configuring REx terminal picture functions
Following steps and tools are required for a REx terminal picture function in
MicroSCADA:
1. Installation of the terminal picture function (Installation Tool)
2. Configuration of the terminal picture function (Standard Configuration Tool)
• Attributes
• REx Configuration (Object Configuration Tool)
• Communication settings (Cconfig Tool)
• Event handling (Event Editor)
• Picture function object (Representation Tool)
3. Terminal parametrisation (RED Relay Tool)
Steps one and two are shortly described in the following sections, but relay
parametrisation is beyond the scope of this manual, please see Tools for Relays and
Terminals Manual, RED Relay Tool.
1MRS751886-MEN
LIB 510
105
LIB 510 Configuration
Configuration Guide
6. Guideline for the substa-
tion engineering with LIB
6
Steps 1 and 2 above are accessed from Tool Manager/Picture Editor. The document
LIB 500 Base Configuration Manual Introduction, gives a general description of the
principles for installing and configuring picture functions. For every terminal a
separate picture function is added to the process picture. Please also see the
Operator’s Manual and the Technical Reference Manual of the relevant terminal for
further information.
6.2.7.1.
Installing terminal picture functions
In the installation tool, choose LIB4/LIB 510/PROTECTION & CONTROL. Select
an appropriate object type, e.g. REF54x. After the RED standard function has been
highlighted, enter a Picture Function Name for the function and click the Install
button. Place the function anywhere in the base picture.
)LJ 7KHSURFHGXUHIRULQVWDOOLQJDWHUPLQDOSLFWXUHIXQFWLRQWHUPLQDOSLFWXUHIXQFWLRQ5()ZDV
VXFFHVVIXOO\LQVWDOOHGYLVLEOHLQWKHXSSHUOHIWFRUQHU
6.2.7.2.
Terminal picture function configuration
The following flowchart shows the procedure of adding and preparing relay
terminals for the process picture.
106
1MRS751886-MEN
LIB 510 Configuration
LIB 510
6. Guideline for the sub-
station engineering with
Configuration Guide
)LJ 7KHSURFHGXUHRIWKHWHUPLQDOFRQILJXUDWLRQ
The Object Configuration Tool is opened from the Tools menu of the Standard
Configuration Tool. The configuration of the relay can be divided into four phases.
1. Relay terminal object type selection and configuration, SW library and APL
library (Object Configuration Tool)
2. Storing terminal specific data (e.g. communication type in Cconfig tool),
(Function described in Tools for Relays and Terminals Manual, SM/RED,
section Configuring Communication Settings)
3. Event configuration (Event Editor). (Function described in LIB 510 4.0.3
Configuration Manual, Event Editor)
4. Storing terminal picture function data is done by the Standard Configuration
Tool by selecting Apply or OK.
Before starting the configuration, please ensure that the base system objects
concerning the stations and nodes are correctly configured.
6.2.7.3.
Standard configuration tool functions
Select the terminal picture function and start the Standard Configuration Tool to
change the configurable attributes and to start the REx Configuration Tool, see
similar example in Fig. 6.2.3.1.-1 on how to start SCT.
The tabs Attributes and Tools are described in this section. The Representation Tool
in the Tools menu is not described.
1MRS751886-MEN
LIB 510
107
LIB 510 Configuration
Configuration Guide
6. Guideline for the substa-
tion engineering with LIB
6
Attributes tab
The following configurable attributes are possible to change for the installed object.
A description of the meaning of the configurables and the different choices follow
below.
)LJ 6WDQGDUG&RQILJXUDWLRQ7RRO$WWULEXWHVWDE
Table 6.2.7.3-1
Configurable attributes that can be changed for the installed
object.
Configurable
Choices
STATION_NAME
The name of the substation. As a default the maximum
length of the text is 9 characters. This text will be used
as a substation identifier of the relay objects on event
list, alarm list, printout, database query, etc. It is very
important that this text is similar to all objects within the
same substation.
BAY_NAME
The name of the bay/feeder. As a default the maximum
length of the text is 14 characters. This text will be used
as a bay/feeder identifier of the relay objects on event
list, alarm list, printout, database query, etc. It is very
important that this text is similar to all objects within the
same bay/feeder.
DEVICE_NAME
The name (identifier) of the relay. As a default the
maximum length of the text is 5 characters. This text will
be used as an identifier of the relay on event list, alarm
list, printout, database query, etc.
108
1MRS751886-MEN
LIB 510 Configuration
LIB 510
6. Guideline for the sub-
station engineering with
Configuration Guide
Saving relay data to the picture function
After the relay terminal has been configured using the configuration tools, the data
has to be saved to the picture function. This is done by using the Standard
Configuration Tool commands Save attributes or Apply attributes.
Copying picture function data
To copy picture function data and to paste it into another picture function, use the
commands Copy attributes and Paste attributes of the Standard Configuration Tool.
After you have copied the picture function data, open the Object Configuration Tool
and make the necessary definitions (addresses etc.).
Deleting picture function
To delete the picture function, select the option Delete in the Standard Configuration
Tool
Remember to save the picture function data before you exit the Standard
Configuration Tool.
AUTHORIZATION GROUP
The authorization group used for the object.
VISIBLE
Visibility of the relay unit object button in the process
picture.
LIB_OBJECT_NAME
Identifies the relay object. The name should be unique
within the application. The logical names of event
process objects will be created by using this name:
LN = LIB_OBJECT_NAME + Index (A-Z, 1..). (A
specific character is defined by the Event Editor)
Max. length of attribute: 9 characters.
Configurable
Choices
1MRS751886-MEN
LIB 510
109
LIB 510 Configuration
Configuration Guide
6. Guideline for the substa-
tion engineering with LIB
6
Tools Tab
)LJ 7KH6WDQGDUG&RQILJXUDWLRQ7RROGLDORJ
The following tools can be started from the Tools tab in the Standard Configuration
Tool:
• Object Configuration Tool for selection of type of terminal and application
library selection (Function described in Tools for Relays and Terminals Manual)
• Cconfig Tool for communication settings (Function described in Tools for Relays
and Terminals Manual)
• Event Editor for event handling (Function described in LIB 510 4.0.3
Configuration Manual, Event Editor)
• Representation Tool for picture function symbol used for the terminal object
Object configuration tool
• The standard function parameters for the relay unit are configured via the Object
Configuration Tool. The tool main function is to configure the relay terminal.
The Object Configuration Tool is started from the Standard Configuration Tool by
selecting Tools/Object Configuration Tool.
The data for the units is read from the
5()[REMHFWW\SHOLEUDU\. These
descriptions are stored in the directory
OLEIPRGVPBUHG
The following example concerns the REF 54x relay.
110
1MRS751886-MEN
LIB 510 Configuration
LIB 510
6. Guideline for the sub-
station engineering with
Configuration Guide
)LJ 7KHGLDORJDSSHDULQJZKHQ5()[&RQILJXUDWLRQLVVHOHFWHG
6.2.7.4.
Terminal parametrisation
After the terminal picture function configuration, the terminals are parametrised by
the RED Relay Tool, please see Tools for Relays and Terminals manual.
6.2.8.
Single line editing
If the Busbar Coloring is used, it is necessary to complete the single line diagram by
drawing all dynamic lines i.e. busbar(s) and connections between picture functions
with the Single Line Editor.
The Single Line Editor is a subset of the Picture Editor and it is saving the drawing
into the selected line segment. The Single Line Editor shall be used one by one for
every line segment to complete the connections between the picture functions.
For the selected line segment the Single Line Editor is being opened from the Tools
folder of the Standard Configuration Tool. The Single Line Editor is very
straightforward to use. You only define the line width and the type of end points as
well as setting for the grid and snap. It is recommended to keep the grid set to 8/10
1MRS751886-MEN
LIB 510
111
LIB 510 Configuration
Configuration Guide
6. Guideline for the substa-
tion engineering with LIB
6
and snap ON since the co-ordinates of line segment and connection points of
switching device have to match. The grid can be taken out of use from Picture
Editor, not in the Single Line Editor.
For typical setting of grid and snap see Fig. 6.2.8.-1 and Fig. 6.2.8.-2.
)LJ
7KHW\SLFDOJULGDQGVQDSVHWWLQJRIWKH3LFWXUH(GLWRUZLWKWKH6LQJOH/LQH(GLWRU
112
1MRS751886-MEN
LIB 510 Configuration
LIB 510
6. Guideline for the sub-
station engineering with
Configuration Guide
)LJ
7KHUHFRPPHQGHGJULGDQGVQDSVHWWLQJRIWKH6LQJOH/LQH(GLWRU
Before the Busbar Coloring is being started it is necessary to generate topology files
with the Topology Generator. The Topology Generator is found from the pull down
menu called Library in the Picture Editor. The picture function handling has to be
active to gain access to the Topology Generator.
The Topology Generator will generate a set of files required by the Busbar Coloring
to the application directory .../PICT/TOPOLOGY. If these files need to be
regenerated it is necessary to remove existing files first since the Topology
Generator will append data to the existing files. Automatic appending is very useful
if the substation single line diagram has been divided into several sub-pictures and
the Busbar Coloring should be generated for the complete station.
The topology name will be used as an identification of the substation for topology
files. When entering the topology name it is very important to use maximum 8
characters and press <ENTER> after writing. If required it is possible to create a
loadfile for transferring the single line diagram to the Network Topology. Option
Create debug file is recommended to select to see if the topology generating was
successful or not.
Please refer to Fig. 6.2.8.-3 as a example of the settings for the Topology Generator.
)LJ
7KH7RSRORJ\*HQHUDWRU
1MRS751886-MEN
LIB 510
113
LIB 510 Configuration
Configuration Guide
6. Guideline for the substa-
tion engineering with LIB
6
Depending on the complexity of the single line diagram and the speed of the
computer it takes about 1-5 minutes to complete the file generating. As an output
there is 6 to 9 files named after the Topology Name.
The Busbar Coloring can be configured to start either manually or automatically
during the system start-up. The configuration is done in runtime by Topology
Monitor which is opened from Busbar Coloring selection under the pull down menu
called Engineering.
Fig. 6.2.8.-4 shows the Topology Monitor with generated files running.
)LJ
7KH7RSRORJ\0RQLWRU
Automatic Topology Start has only effect if there is a following entry in the
APL_INIT_1 or APL_INIT_2-command procedure:
#DO BCU_TPSTRT:C ;check for automatically starting Busbar Coloring
programs
6.2.9.
Menu configuration
Typically the single line diagram is added to the menu structure under Stations. This
is done by the Menu Configuration Tool in the Picture Editor. The menus are
configurable through the base picture function. Select the base picture function of
your picture and open The Standard Configuration Tool. From the Standard
Configuration Tool you are able to open the Menu Configuration Tool by which the
menus can easily be configured.
The menus are configurable in three parts. As default The Common Part and the
Help part are common for all pictures within an application. The Picture Specific
Part is holding items used in that picture only. The sources, where the menu
definitions are fetched, are configured in each pictures base picture function.
114
1MRS751886-MEN
LIB 510 Configuration
LIB 510
6. Guideline for the sub-
station engineering with
Configuration Guide
)LJ
7KH0HQX&RQILJXUDWLRQ7RRO
Fig. 6.2.9.-2 shows the Menu Configuration Tool with the view of menu item
adding/editing.
1MRS751886-MEN
LIB 510
115
LIB 510 Configuration
Configuration Guide
6. Guideline for the substa-
tion engineering with LIB
6
)LJ
7KH0HQX&RQILJXUDWLRQ7RROZLWKWKHYLHZRIPHQXLWHPDGGLQJ
HGLWLQJ
For detailed information about the Menu Configuration Tool, see LIB 500 4.0.3
Configuration Manual, LIB 500 4.0.3 Backbone Configuration Manual.
6.2.10.
Control authority
There are some settings to do before the single line diagram is fully operable.
6.2.10.1.
System location
The system location defines whether the system is a local control system (SCS) or a
remote control system (NCC). The setting of the system location between the
Substation Control System and the Network Control System has meaning with the
station local/remote-switch. The Substation Control System has rights to control the
station only if the station local/remote-switch is in the station position whereas the
switch has to be in remote position with the Network Control System to gain the
control authority.
The System Location setting is found from the Application Settings under the pull
down menu called Options.
6.2.10.2.
Control authority of the control centers
The Control Authority of Control Centers is for defining the control centers i.e.
applications within the entire MicroSCADA system having the control authority of
the station.
116
1MRS751886-MEN
LIB 510 Configuration
LIB 510
6. Guideline for the sub-
station engineering with
Configuration Guide
The command sources found in the system are shown in the "Control centers" list.
The currently authorized centers are shown in the "Authorized centers" list.
Command sources can be added to the "Control centers" list by writing to the "New
center" field. This might be needed in case of control applications, where there are
multiple base systems. Please note that the insertion of "New centers" is case
sensitive.
6.3.
Example of standard function configurations
6.3.1.
General
As a general rule the logical name of the process objects should be unique for all
standard functions. As an exception for this rule the logical name can or has to be
same in the following cases:
Table 6.3.1-1
General rules for the logical process object names
Following tables present examples of the MV Process and SPACOM configuration.
6.3.1.1.
Base
An example of the configuration of the Base picture function:
Table 6.3.1.1-1
Configuration of the Base picture function
6.3.1.2.
Station
An example of the configuration of the Station picture function:.
Case
Logical name
Switching device with truck
Same or different
Three-state switch
Same on both switching sections
Measurements within the bay
Same or different
DTU 4
Same for all switches within the same DTU
REC 501
Same for all switches within the same REC 501
Attribute
Value
PICTURE FUNCTION NAME
EASTWICK
PICTURE_HEADER
Eastwick 110/20kV
PICTURE_HEADER_FILE
B_USE/BGU_HEAD2A.PIC
SHOW_ALARMROW
When alarms
STANDARD_MENU_PART
B_USE/BGU_H2STAND.MNU
SPECIFIC_MENU_PART
PICT/CHANGE_NAME_INTO_PIC_NAME.MNU
HELP_MENU_PART
B_USE/BGU_H2HELP.MNU
1MRS751886-MEN
LIB 510
117
LIB 510 Configuration
Configuration Guide
6. Guideline for the substa-
tion engineering with LIB
6
Table 6.3.1.2-1
Configuration of the Station picture function.
6.3.1.3.
Bay
An example of the configuration of the bay picture function:
Table 6.3.1.3-1
Configuration of the bay picture function
6.3.1.4.
Switching Device
The switching device is the common designation for Circuit breaker, Truck,
Disconnector, 3-State Switch and earth switch.
Attribute
Value
PICTURE FUNCTION NAME
STATION
STATION_NAME
Eastwick
SPECIAL_IDENTIFIER_x
N/A
PICTURE_FUNCTION_VISIBLE
Yes
STATION_LABEL
Station
P_OBJECT_LN
ESTSTA
STATION_TYPE
SPACOM /SPANET (SPA)
CMD_PARAMETER
N/A
OUTPUT_STATUS
N/A
DATA_ACQUISITION_UNIT
SPTO12D4
AUTHORIZATION_GROUP
MV_CONTROL
STATION_LR_IN_USE
Yes
LR_REMOTELY_CONTROLLABLE
Yes
EVENT_RECORDING
N/A
Attribute
Value
PICTURE FUNCTION NAME
BAY1
STATION_NAME
Eastwick
BAY_NAME
Incoming 110kV
SPECIAL_IDENTIFIER_x
N/A
BAY_LABEL
H1
P_OBJECT_LN
ESTH01_BAY
STATION_TYPE
RED 500 / REX (LON)
CMD_PARAMETER
N/A
OUTPUT_STATUS
N/A
DATA_ACQUISITION_UNIT
REF54x
AUTHORIZATION_GROUP
MV_CONTROL
BAY_LR_IN_USE
Yes
IND_DOUBLE_BINARY
Yes
LR_REMOTELY_CONTROLLABLE
No
EVENT_RECORDING
N/A
118
1MRS751886-MEN
LIB 510 Configuration
LIB 510
6. Guideline for the sub-
station engineering with
Configuration Guide
The configuration of a switching device as a circuit breaker can be given as an
example:
Table 6.3.1.4-1
Configuration of a switching device as a circuit breaker
6.3.1.5.
Transformer
As an example, the configuration of the transformer (SPAU 341):
Attribute
Value
PICTURE FUNCTION NAME
SW3
STATION_NAME
Eastwick
BAY_NAME
Incoming 110kV
DEVICE_NAME
Q0
SPECIAL_IDENTIFIER_x
N/A
P_OBJECT_LN
ESTH01_Q0
SWITCHING_DEVICE_TYPE
Circuit breaker
SWITCHING_DEVICE_PURPOSE
Circuit breaker
SWITCH_SECTION
N/A
STATION_TYPE
RED 500 / REX (LON)
INDICATION_TYPE
Double indication (DB)
MOTORIZED
Yes
CMD_PARAMETER
N/A
CONTROL_TYPE
Secured control with 4 BOs
OUTPUT_STATUS
N/A
CONTROL_PULSE_LENGTH
N/A
CONTROL_BITS
N/A
DATA_ACQUISITION_UNIT
REF54x
FUNCTION_BLOCK
COCB1-A
CHANNEL_NUMBER
N/A
AUTHORIZATION_GROUP
MV_CONTROL
SUFFIX_POSITION
None
SYMBOL_WITH_BUTTON
Yes
AUXILIARY_PLUG
No
EVENT_RECORDING
N/A
COMPACT_INSTALLATION
N/A
U_INTERLOCKING
-
U_OTHER_OBJECTS
-
REPRESENTATION
F_REPR/F_BREAK2 (vertical link)
1MRS751886-MEN
LIB 510
119
LIB 510 Configuration
Configuration Guide
6. Guideline for the substa-
tion engineering with LIB
6
Table 6.3.1.5-1
Configuration of the transformer (SPAU 341)
6.3.1.6.
Transformer measurements
The measurement for the transformer is linked to the transformer picture function,
As an example, the configuration of Transformer measurement:
Table 6.3.1.6-1
Configuration of Transformer measurement
6.3.1.7.
Measurements
As an example, the configuration of measurements:
Attribute
Value
PICTURE FUNCTION NAME
T1
STATION_NAME
Eastwick
BAY_NAME
Transformer 1
DEVICE_NAME
TR1
SPECIAL_IDENTIFIER_x
N/A
NOMINAL_VOLTAGE
20
MIN_POSIT
1
MAX_POSIT
19
P_OBJECT_LN
ESTH03_T1
STATION_TYPE
SPACOM / SPANET (SPA)
CONTROL_DIALOG_WINDOW
MNOPER
AUTHORIZATION_GROUP
MV_CONTROL
TRANSFORMER_TYPE
2-winding
SYMBOL_WITH_BUTTON
Yes
HARDWIRED
No
TOPO_OBJECT_COLOR_SPLIT
SPLIT
TOPO_OBJECT_COLOR1_NR
9
TOPO_OBJECT_COLOR2_NR
10
TOPO_OBJECT_COLOR3_NR
- (Not in use, two winding transformer)
U_INTERLOCKING
-
U_OTHER_OBJECTS
-
REPRESENTATION
F_REPR/F_TRANS3
(vertical link (3*3))
Attribute
Value
PICTURE FUNCTION NAME
T1_M
CONNECT_TO_OBJECT T1
VOLTAGE_INDICATION
Yes
AUTO_MANUAL_INDICATION
Yes
TAP_POSITION_INDICATION
Yes
PARALLEL_INDICATION
No
120
1MRS751886-MEN
LIB 510 Configuration
LIB 510
6. Guideline for the sub-
station engineering with
Configuration Guide
Table 6.3.1.7-1
Configuration of measurements
Attribute
Value
PICTURE FUNCTION NAME
BAY1_CT
STATION_NAME
Eastwick
BAY_NAME
Incoming 110kV
DEVICE_NAME
-
SPECIAL_IDENTIFIER_x
N/A
P_OBJECT_LN
ESTH01_MEC
STATION_TYPE
RED 500 / REX (LON)
TYPE_MEAS_1
(10) Current L1
FOLDER_1_TITLE
IL1
MEAS_1_DECIMALS
0
SHOW_MEAS_1
N/A
SHOW_MEAS_1_AS_BAR
N/A
SHOW_MEAS_1_UNIT
N/A
DATA_ACQUISITION_UNIT_1
REF54x
FUNCTION_BLOCK_1
-
TYPE_MEAS_2
(20) Active power P
FOLDER_2_TITLE
P
MEAS_2_DECIMALS
1
SHOW_MEAS_2
N/A
SHOW_MEAS_2_AS_BAR
N/A
SHOW_MEAS_2_UNIT
N/A
DATA_ACQUISITION_UNIT_2
REF54x
FUNCTION_BLOCK_2
-
TYPE_MEAS_3
(21) Reactive power Q
FOLDER_3_TITLE
Q
MEAS_3_DECIMALS
1
SHOW_MEAS_3
N/A
SHOW_MEAS_3_AS_BAR
N/A
SHOW_MEAS_3_UNIT
N/A
DATA_ACQUISITION_UNIT_3
REF54x
FUNCTION_BLOCK_3
-
TYPE_MEAS_4
None
FOLDER_4_TITLE
N/A
MEAS_4_DECIMALS
N/A
SHOW_MEAS_4
N/A
SHOW_MEAS_4_AS_BAR
N/A
SHOW_MEAS_4_UNIT
N/A
DATA_ACQUISITION_UNIT_4
N/A
FUNCTION_BLOCK_4
N/A
1MRS751886-MEN
LIB 510
121
LIB 510 Configuration
Configuration Guide
6. Guideline for the substa-
tion engineering with LIB
6
6.3.1.8.
Trip tag
The reason why several attributes are left empty is that there are two ways of
configuring the trip tag; either by 1) manually giving the attribute values to these
fields and then by creating the process objects in the POT tool or 2) creating the
process object in the Event Editor and then create links to these, which is the case in
this example.
Table 6.3.1.8-1
Configuration of the trip tag
AUTHORIZATION_GROUP
MV_CONTROL
SYMBOL_WITH_BUTTON
Yes
EVENT_RECORDING
N/A
U_OTHER_OBJECTS
-
REPRESENTATION
F_REPR/F_MEASM12 (vertical CT)
Attribute
Value
Attribute
Value
PICTURE FUNCTION NAME
BAY1_TRP
STATION_NAME
-
BAY_NAME
-
DEVICE_NAME
-
SPECIAL_IDENTIFIER_x
P_OBJECT_LN
-
STATION_TYPE
N/A
OUTPUT_STATUS
N/A
DATA_ACQUISITION_UNIT
N/A
FUNCTION_BLOCK
N/A
EVENT_RECORDING
N/A
LINK_TRIP_TAG_TO_LN_1
ESTH01_R1A
LINK_TRIP_TAG_TO_MODULE_1
("REF 543","","F_REPR/
F_LATCH1","2","F_REPR/F_
TRIP11")
LINK_TRIP_TAG_TO_LN_2
ESTH01_R1C LINK_TRIP_TAG_TO_MODULE_2
("REF 543","","F_REPR/
F_LATCH1","130","F_REPR/F_
TRIP3")
LINK_TRIP_TAG_TO_LN_3
ESTH01_R1D
LINK_TRIP_TAG_TO_MODULE_3
("REF 543","","F_REPR/
F_LATCH1","2","F_REPR/
F_TRIP12","66","F_REPR/
F_TRIP5","130","F_REPR/F_TRIP5")
LINK_TRIP_TAG_TO_LN_4
-
LINK_TRIP_TAG_TO_MODULE_4
No linking
122
1MRS751886-MEN
LIB 510 Configuration
LIB 510
6. Guideline for the sub-
station engineering with
Configuration Guide
6.3.1.9.
Auto reclose tag
The reason why several attributes are left empty is that there are two ways of
configuring the Auto Reclose Tag; either by 1) manually giving the attribute values
to these fields and then by creating the process objects in the POT tool or 2) creating
the process object in the Event Editor and then create links to these, which is the case
in this example.
Table 6.3.1.9-1
Process objects created in the Event Editor
6.3.1.10.
Alarm indicator
As an example, the configuration of the Alarm indicator is provided below: Note
only the three first sets of signals are shown, 4-8 are omitted from the table, since 4-
8 are almost similar to 1-3, and therefore not bringing any new information.
Table 6.3.1.10-1 Configuration of the Alarm indicator
LINK_TRIP_TAG_TO_LN_5
-
LINK_TRIP_TAG_TO_MODULE_5
No linking
REPRESENTATION
F_REPR/F_TRIP1
Attribute
Value
Attribute
Value
PICTURE FUNCTION NAME
BAY7_AR
STATION_NAME
-
BAY_NAME
-
DEVICE_NAME
-
SPECIAL_IDENTIFIER_x
N/A
P_OBJECT_LN
-
STATION_TYPE
N/A
OUTPUT_STATUS
N/A
DATA_ACQUISITION_UNIT
N/A
FUNCTION_BLOCK
N/A
AR_WITH_MULTIPLE_CYCLES
N/A
SHOW_AR_IN_USE
N/A
SHOW_AR_NOT_IN_USE
N/A
EVENT_RECORDING
N/A
LINK_AR_TAG_TO_LN
ESTHA2_R1D
LINK_AR_TAG_TO_MODULE
SPTO 6D3
REPRESENTATION
F_REPR/F_ARRUN1
Attribute
Value
PICTURE FUNCTION NAME
BAY5_AI
STATION_NAME
Eastwick
BAY_NAME
Outgoing HA5
1MRS751886-MEN
LIB 510
123
LIB 510 Configuration
Configuration Guide
6. Guideline for the substa-
tion engineering with LIB
6
6.3.1.11.
SPACOM relay
As an example, the configuration of a SPACOM relay is provided below.
Table 6.3.1.11-1 Configuration of a SPACOM relay
The rest of the relay configuration is done by e.g. Cconfig Tool, Event editor, SPA
Relay Tool.
DEVICE_NAME
-
P_OBJECT_LN
ESTHA1_ALA
STATION_TYPE
SPACOM / SPANET (SPA)
DATA_ACQUISITION_UNIT
SPTO1D6
TYPE_OF_SIGNAL1
Binary Input (BI)
SIGNAL1_TEXT
Spring uncharged
ALARMING_STATE_OF_SIGNAL1
(1)
LINK_SIGNAL1_TO_LN
N/A
LINK_SIGNAL1_TO_IX
N/A
TYPE_OF_SIGNAL2
Not Defined
SIGNAL2_TEXT
N/A
ALARMING_STATE_OF_SIGNAL2
N/A
LINK_SIGNAL2_TO_LN
N/A
LINK_SIGNAL2_TO_IX
N/A
TYPE_OF_SIGNAL3
Not Defined
SIGNAL3_TEXT
SSF6 Low Pressure
ALARMING_STATE_OF_SIGNAL3
(1)
LINK_SIGNAL3_TO_LN
N/A
LINK_SIGNAL3_TO_IX
N/A
AUTHORIZATION_GROUP
MV_CONTROL
SYMBOL_WITH_BUTTON
Yes
EVENT_RECORDING
N/A
REPRESENTATION
F_REPR/F_ALIND2 (led)
Attribute
Value
Attribute
Value
PICTURE FUNCTION NAME
Station name
Eastwick
Bay name
Incoming 20 kV
Device name
AUTHORIZATION_GROUP
SPACOM_RELAYS
1MRS751886-MEN
LIB 510
125
LIB 510 Configuration
Configuration Guide
7. Fault Report Function in
LIB 510
7
7.
Fault Report Function in LIB 510
7.1. General
description
7.1.1.
Purpose
The Fault Report Function provides automatic generation of reports after a final trip
event comes from a relay. The reports include constant data associated with the relay
and with the type of the event, as well as dynamic data that is read from the relay
just after the fault occurs. Dynamic data contains measured values and other details
specific for the situation (earth fault, short circuit etc.).
7.1.2.
Environment
The Fault Report Function is a part of LIB 500/LIB 510. It works together with
Windows NT 4.0, SYS 500 8.4.3., LIB 5xx greater than 4.0.3 and OPERA 3.2. The
user interface is made with Visual SCIL and therefore cannot be displayed in X-
monitors. The function has been implemented as a system module in LIB 510 and it
complies with LIB 500 System Design Description and Style Guide. Enabling the
fault events to activate the Fault Report Functions, the corresponding picture
functions should be installed and signals should be configured using the Event
Editor.
7.2.
Installation
7.2.1.
Files and directories
The Fault Report function files are placed in the following directory under
MicroSCADA root: ..\LIB4\FMOD\FREP. It has two subdirectories: USE and
LANGx. The first one contains all the programming components (VSO files,
pictures, text files – sources of command procedures), initialization files for VS
tools, cross-reference and relay parameter files. The second directory contains text
files with translatable texts and text files used in form pictures.
1MRS751886-MEN
126
1MRS751886-MEN
LIB 510 Configuration
LIB 510
7. Fault Report Function
in LIB 510
Configuration Guide
Full list of files is shown below:
There are three files that are not present after installing the Fault Report function but
which can be created while making settings with the Fault Report Configuration
tool. The files are
))8B)5(3LQL, ))8B;%/.LQL and FFU_CRREF.INI, being
placed in the application parameters directory. The first of them contains report
generation options that define whether reports are to be sent to a file, printer, event
list and Opera. The printer number and root directory for report files are also saved
in this file. The second file contains cross-reference table used for the function
blocks that can generate TRIP events but actual data should be read from another
function block. Usually this is the case in auto-reclosing modules. The third file is
used to set “t_Source_Ln” (Breakers Scadacode) variable defined for Opera. This
cross-reference is used only if neither breaker indication nor station L/R process
object is found for the tripping object.
In order to the fault report directories to be visible, path definitions must be
defined. File
3DWKBIW[W should be created in the ..LIB4\BASE\BBONE\USE\
directory with contents:
;Path definitions for Fault Report function in LIB500
#PATH F_USE +NO_CREATE, /LIB4/FMOD/FREP/USE
#PATH F_LANG +NO_CREATE, /LIB4/FMOD/FREP/LANG’L’
After restarting the base system, Fault Report directories will be added to “F_USE/
” and “F_LANG/” logical paths.
..\LIB4\FMOD\FREP\USE
directory
FFU_Fault.cin – source file for FFU_Fault:C command
procedure used to send values to OPERA.
FFU_Start.cin - source file for FFU_Start:C command
procedure that starts report generation.
ffu_cfg.vso – Fault Report Configuration (FRC) tool VSO
file used to configure Fault Report Function options,
adding and deleting report generation to signals.
ffu_brws.vso – Fault Report Browser (FRB) tool VSO file
used for browsing, editing and printing of the generated
report files.
ffu_fault.vso - Fault Report Generator VSO file that is
executed in an invisible monitor and that fulfills all the
work of report creation.
FFU_brws.ini – initialization file for FRB tool.
FFU_cfg.ini – initialization file for FRC tool.
FREP.ini - initialization file for Fault Report Generator.
FFU_XPAR.ini – file containing cross-reference between
module (function block) names and parameter file names.
form4ffrev.pic – form picture used for generation of
events to the LIB 500 event list.
form4ffrpr.pic – form picture used by the Fault Report
Generator to print reports.
Relay specific parameter files used in report generation
are also placed here.
..\LIB4\FMOD\FREP\LANGx
directory
form4ffrev.txt – text file used by form4ffrev.pic form
picture.
Files with translatable texts referenced from relay
parameter files can be placed here.
1MRS751886-MEN
LIB 510
127
LIB 510 Configuration
Configuration Guide
7. Fault Report Function in
LIB 510
7
7.2.2.
Tools
The Fault Report Configuration tool and Fault Report Browser can be opened from
the LIB 500 menus
µ2SWLRQV)DXOW5HSRUW«&RQILJXUDWLRQ7RRO«¶ and µ2SWLRQV
)DXOW5HSRUW«)DXOW5HSRUW%URZVHU«¶ from the Header in a VS monitor or
optionally from the Tool Manager. To open the tools from the Tool Manager they
should be registered in the
WRROVLQL file in the ?67RRO?0LVF? or
?/,%?%$6(?%%21(?86(? directories. The Fault Report Generator is an
invisible tool that starts in an invisible monitor by the FFU_Start:C command
procedure. It must be registered in the
?/,%?%$6(?%%21(?86(? directory.
Thus, it is better that all the three tools are registered in the
?/,%?%$6(?%%21(?86(?WRROVLQLfile:
[FFU_CFG]
Tool_Dir_ = \sc\LIB4\FMOD\FREP\use
[FFU_BRWS]
Tool_Dir_ = \sc\LIB4\FMOD\FREP\use
[FREP]
Tool_Dir_ = \sc\LIB4\FMOD\FREP\use
Detailed description of using the Fault Report Configuration tool and Fault Report
Browser is given in the Operator’s Manual.
7.2.3.
Objects
The Fault Report function includes the following application objects that take part
in the report generation:
•
))8B6WDUW$ – event channel which is activated from process objects whose
value is changed after the final trip event comes.
•
))8B6WDUW& – command procedure activated from the event channel
FFU_Start:A. In some cases it can be activated from another event channel as a
secondary object.
•
))8B)DXOW& – command procedure activated from the FR generator invisible
VS tool for sending data to OPERA.
•
))8B6WDUW3 – process object used for data exchanging between ))8B6WDUW&
and the invisible VS tool.
•
))8B(YHQW3 – process object used for adding of the Fault Report events to the
LIB 500 Event list.
All these objects are installed automatically when the Fault Report Configuration
tool is started.
7.2.4.
Pictures
Two form pictures are used by the FR generator:
•
IRUPIIUHYSLF is activated by ))8B(YHQW3 process object; it is used for
adding Fault Report events to the LIB 500 Event list.
•
IRUPIIUSUSLF – form picture used by the Fault Report Generator for printing
fault reports to a transparent printer.
128
1MRS751886-MEN
LIB 510 Configuration
LIB 510
7. Fault Report Function
in LIB 510
Configuration Guide
7.3.
Fault reports generation
7.3.1.
Report generation sequence
A final TRIP event is associated with a process object (usually of Binary Input type)
in the application. An attribute of the object points to the
))8B6WDUW$ event
channel, which starts the report generation by activating the
))8B6WDUW&
command procedure. This procedure raises the invisible VS tool that fulfills all the
work of the report generation. In some cases
))8B6WDUW& is activated, not from the
))8B6WDUW$ event channel, but is configured as a secondary object of another
event channel that was associated with the process object for other purposes. During
report generation common options are read from file FFU_FREP.ini in the
application parameters directory. The function block name is determined from the
RX attribute of the process object. The parameter file name is then determined from
the cross-reference list between the function block names and parameter file names
stored in the FFU_XPAR.ini file. Finally, the relay specific part of the report is
created in accordance with the relay parameter file. FR generator uses a Project
Manager object corresponding to the function block for reading data from the relay
with Communication Manager service. This object name is determined from the
process object LN attribute by cutting the last character.
Parameter files for the most common used function blocks are distributed with the
Fault Report function package.
Sometimes the TRIP event comes not from the function block in which the fault has
really occured but from another (auto-reclosing) module. In this case there is no
cross-reference between the first module name and the parameter file, and FR
generator tries to determine the actual module (function block) name from file
FFU_XBLK.ini in the application parameters directory. This file contains a cross-
reference list between pairs of LN and IX of the process object and “actual object”
and “actual block” names. When a cross-reference line with corresponding LN and
IX is found, “actual block” is used to determine the parameter file name and “actual
object” is used as a Project Manager object.
7.3.2.
Printing
Generated reports can be sent to a printer, if the corresponding option is set. The
printer number defined in the FRC tool is the number of a PRI object in the base
system. It should be “LINE” printer configured as “transparent” and connected
directly to the base system PC or to another PC in the network. SD (device name) of
the PRI object should point to the local Windows NT port that is connected directly
to a local printer or mapped to some network printer path.
7.3.3.
Interface to OPERA
FR generator initializes data sending it to OPERA by calling
%'8B)DXOW&
command procedure that is not part of the FR function.
There is a list of variables that can be sent to OPERA:
• e_Event_time
• i_Event_ms
• t_Source_ln
• t_Type"
1MRS751886-MEN
LIB 510
129
LIB 510 Configuration
Configuration Guide
7. Fault Report Function in
LIB 510
7
• t_Trigger
• t_Notation
• t_Phase
• v_I_Msr
• r_I_Load
• r_I0_Msr
• r_U0_Msr
• r_X_Msr
• r_Z_Msr
• v_Transformer_LN
• v_P_Msr
• v_Q_Msr
“e_Event_time” and "t_Source_ln" variables are always present, others can be
missing. Which optional parameters are sent to OPERA is defined in the relay
parameter file.
All the variables that are to be sent to OPERA are initialized in the VSO part of the
report generator and put into the context of the
))8B)DXOW& command procedure.
This procedure does originally nothing with the data and simply calls
%'8B)DXOW&
so that all the variables from the context of
))8B)DXOW& are passed to
%'8B)DXOW& Project engineers can implement any modifications with the data
inside
))8B)DXOW& before calling %'8B)DXOW&.
7.4.
Relay specific parameter files
The parameter file contains a description of the parameters that are to be included
into the relay-specific part of the report, as well as correlation between the relay
parameters and the OPERA input variables. Usually parameter files are named as
"module_name".par and stored in the SC\LIB4\FMOD\FREP\USE directory. This
naming convention is not obligatory and is only a convenient template.
Real correspondence between the parameter file and the relay functional block is
defined in the FFU_XPAR.INI file. The module name is written on the left, the name
of the corresponding parameter file on the right.
130
1MRS751886-MEN
LIB 510 Configuration
LIB 510
7. Fault Report Function
in LIB 510
Configuration Guide
7.4.1.
File syntax
Two list variables should be defined in parameter file:
7KH5HOD\B3DUDPHWHUV list defines relay specific part of the generated report.
This part consists of as many lines as the number of
5HOD\B3DUDPHWHUV9SDU elements. Some of them, for which
5HOD\B3DUDPHWHUV9SDUL ´´ are header lines containing only
corresponding titles, other lines consist of three parts:
1. SPA parameter name
2. parameter value or communication error message
3. parameter title
Optional Multipliers list can be defined in the file. It contains the following
vector attributes:
•
3$5 – vector of the library object parameters, which must be obtained by Project
Manager calls for the object. Usually such parameters are Obj_Nominal_In,
Obj_Nominal_Un. Some actual values uploaded from the relay must be
multiplied by these values, which is pointed in the Relay_Parameters:vUnit
vector. For example, if “Unit” is “A:2” then the uploaded value (in amperes) must
be multiplied by Multipliers:vPar(2) object parameter (usually Obj_Nominal_In).
Variables
Description
@Relay_Parameters = list(-
PAR = vector(...),-
UNIT
TITLE = vector(...),-
IS_SETTING = vector(...),-
VAR_NAME = vector(...))
3$5
- Relay parameters SPA names or “” for
header lines.
UNIT – measurement unit of the parameter in text
form, e.g. “A”. It is possible to insert here an index
to “Multipliers” list vectors (see below), which
instructs the program how to modify the uploaded
value. Example:
UNIT =
vector(“”,“A:1”,“V:2”,“s”)
7,7/(
- Parameter descriptions and report
headers.
,6B6(77,1*
– Boolean “Is setting” flag. Marks
lines to be included into report only if “Include
Setting Values” is checked in the “Report
Generation Options” dialog.
9$5B1$0(
– Name of the OPERA variable in SCIL
list attribute format, e.g
“
Opera_Parameters:Vt_Phase
” or
“
Opera_Parameters:V
v_I_Msr(2)”.
@Opera_Parameters = list(-
<var_name_1>=<default_text>,-
<var_name_2>=<default_text>,-
...)
YDUBQDPHB[!
- OPERA variable names, e.g.
t_Type
GHIDXOWBWH[W!
- value of the OPERA variable.
If
<var_name_x>
is present in the
Relay_Parameters:Vvar_name
vector, this
value is replaced by the value that is read from the
relay. Full list of the OPERA variables includes
three parts:
mandatory parameters - “e_Event_time” and
"t_Source_ln";
variables that are non-empty elements of
Relay_Parameters:Vvar_name
vector;
components of
Opera_Parameters
list.
1MRS751886-MEN
LIB 510
131
LIB 510 Configuration
Configuration Guide
7. Fault Report Function in
LIB 510
7
•
'() - If the object parameter is not available, default text is added to the output,
e.g. “*In”. This text is taken from this vector component. For the previous
example, it is Multipliers:vDef(2).
•
.2() – This is an optional vector containing additional coefficients to multiply
the uploaded values by. This is useful, for example, if the value is a percentage of
the nominal. In this case “0.01” coefficient can be used to modify the uploaded
value before it is printed.
Here is an example taken from the SPCS4D11 parameter file:
@Multipliers = LIST(-
PAR = vector("Obj_Nominal_Un","Obj_Nominal_In","Obj_Nominal_In"),-
KOEF=vector(0.01, 1.0, 0.01),-
DEF=vector("*Un","*In","*In") )
In some cases it is desirable to exclude historical values from the report, e.g. for the
SPCJ4D24 module. For this purpose a template code can be introduced into the
parameter file just after the Relay_Parameters list definition. This code, if
uncommented, will remove some parameters from the list. Here is an example from
the SPCJ4D24.par file:
@v_not_needed = vector()
;
; Use following to exclude historical data
;
@v_not_needed = vector(-
17,18,19,20,21, -
22,23,24,25,26, -
27,28,29,30,31, -
32,33,34,35,36 -
)
#set Relay_Parameters:Vpar = DELETE_ELEMENT(Relay_Parameters:Vpar,
%v_not_needed)
#set Relay_Parameters:Vunit = DELETE_ELEMENT(Relay_Parameters:Vunit,
%v_not_needed)
#set Relay_Parameters:Vtitle = DELETE_ELEMENT(Relay_Parameters:Vtitle,
%v_not_needed)
#set Relay_Parameters:Vis_setting =
DELETE_ELEMENT(Relay_Parameters:Vis_setting, %v_not_needed)
#set Relay_Parameters:Vvar_name = DELETE_ELEMENT(Relay_Parameters:Vvar_name,
%v_not_needed)
It is possible to insert a SCIL code into the parameter file, which is executed after
all the parameters are loaded. This code should be stored after defining the two lists
above in the [POST_LOAD_CODE] section.
The purpose of this SCIL code is to make some value conversions of the loaded
values, e.g. if it is needed to print some human readable text instead of numeric
values, which have been loaded. Another possibility is to remove some parameters
from the output, if the value of another parameter has a certain meaning. It is also
possible to change the order of the parameters in the output. Since it is unknown for
the parameter file creator what variable names are used in the Fault Report
Generator for the uploaded values, the following rule is accepted. The Fault Report
Generator parses the text vector and replaces each occurrence of a string
“[par_name]”, where PAR_NAME is one of the parameter names in the
5HOD\B3DUDPHWHUV list, to the actual internal variable, which contains the
parameter value. For example, if the parameter V7 is present in the
5HOD\B3DUDPHWHUVlist, the following code should work:
[POST_LOAD_CODE]
132
1MRS751886-MEN
LIB 510 Configuration
LIB 510
7. Fault Report Function
in LIB 510
Configuration Guide
#if %[V7] == “1” #then @[V7] = “One”
#if %[V7] == “2” #then @[V7] = “Two”
#else @[V7] = “Many”
)
In other words, “V7” variable in this example can be presented in two forms: %[V7]
and @[V7]. In a more complicated case, it is necessary to remove some parameters
from the report under a certain conditions. Setting the status of the parameter to
nonzero can do this:
[POST_LOAD_CODE]
@i_dec = DEC_SCAN(vector(%[V7]))
#if get_status(%i_dec(1)) <> 0 #then #return
@i_dec = TRUNC(0.0 + %i_dec(1))
#if BIT_AND(%i_dec,15) > 0 #then #block
@[V7] = SET_STATUS(%[V7], 10)
@[S001] = SET_STATUS(%[S001], 10)
@[S002] = SET_STATUS(%[S002], 10)
#block_end
It is possible to change the order of the output. A new variable should be created for
this purpose: V_PARS_ORDER. It is the vector of the same length as the parameter
vectors in the Relay_Parameters list. This vector should contain indexes of the
parameters in new the order, e.g.
[POST_LOAD_CODE]
#if %[V6]==”0” #then @v_pars_order = vector(1,2,3,4,7,8,5,6,9,10)
It is not recommended to mix this technique with using of the V_NOT_NEEDED
vector (see above). In any case, the length of the Relay Parameters list components
must be the same as the length of the V_PARS_ORDER vector.
The Fault Report Generator compiles the SCIL code stored in the
[POST_LOAD_CODE] section. If an error occures, the error description will be put
into the report text. It is not recommended to use “#error ignore” and “#error stop”
commands in this SCIL code.
The POST_LOAD_CODE section is executed
EHIRUH all the value modifications are
done according to the Multipliers list.
7.4.2.
Translatable texts
1
Parameter titles in the
5HOD\B3DUDPHWHUV9WLWOH vector can be defined
as translatable texts. In this case they are written in SCIL expansion form, e.g.
“’TITLE_MAX_CURRENT’”
. Variable @TITLE_MAX_CURRENT should be
defined at the beginning of the file from a text file placed in
?/,%?)02'?)5(3?/$1*[ directory, e.g.:
File
12&/2:SDU
@TITLE_MAX_CURRENT = “MAX_CURRENT”
@TITLE_PHASE_DATA = “PHASE_DATA”
@L = 0
@TMP=APL:BSV(11)
1. This part of the specification is not stable and may be changed in the future.
1MRS751886-MEN
LIB 510
133
LIB 510 Configuration
Configuration Guide
7. Fault Report Function in
LIB 510
7
#IF DATA_TYPE(TMP:VB_APPLICATION_LANGUAGE)=="INTEGER" #THEN –
@L = TMP:VB_APPLICATION_LANGUAGE
#error ignore
@a = DO(read_text(“/LIB4/FMOD/FREP/LANG’L’/NOC3LOW.txt”))
#error stop
@Relay_Parameters = list(-
PAR = vector(“111V200”, “111V300”,...),-
TITLE = vector(“’TITLE_MAX_CURRENT’”, “’TITLE_PHASE_DATA’”,...),-
...
File
12&/2:W[W
@TITLE_MAX_CURRENT = “Maximum current”
@TITLE_PHASE_DATA = “Phase data”
...
7.5.
Configuring signals for report generation
Signals associated with final trip events are created and configured with the Event
Editor tool, see “Event Editor Configuration Manual in LIB 510”. At first, Project
Manager objects are created in a picture function (LIB_OBJECT_NAME) with the
Standard Configuration tool. Then the signals are configured and process objects
can be created by using the Event Editor. Process objects used to generate fault
reports are usually of Binary Input type. In addition, these process objects have a
special keyword in the RX attribute: RX(26...30) is “ITRIP” or RX(26...29) is
“ITRP”. This condition is used as a default filter in the Fault Report Configuration
tool while browsing the process objects. This default filter can be changed by the
user with authorization level Engineering(2) of MV_CONTROL group .
Breaker indication or station L/R process objects should be set for the tripping
object. One of these objects, if found, is used as “t_Source_Ln” Opera parameter. At
first, Breaker indication object is searched by the Fault Report Generator. If it is not
found, station L/R is searched. If it is also not found, the FFU_CRREF.TXT cross-
reference file will be read to find the corresponding object.
Breaker indication object is searched by using the following criteria: its OI attribute
must contain “station name” and “bay name” in the places pointed by APL:BSV(15)
fields. Additionally its RX attribute must be in form:
"%%%%%%%%%%%%%%%%%%%%%%QB%%IPOS".
Station L/R object is searched by using the following criteria: its OI attribute must
contain “station name” in the place pointed by APL:BSV(15) fields. Additionally,
its RX attribute must be in form:
"%%%%%%%%%%%%%%%%%%%%%%%STAILRS".
LIB 510
Index
Configuration Guide
Index
Page
6\PEROV
*
$
Additional Settings
Additional Settings for the Calculated Report Object Types
........................................ 48
Additional Settings for the Measured Report Object Types
.......................................... 45
AI
Alarm Class
ALARM INDICATOR
Alarm list menu
ALARMING_STATE_OF_SIGNAL1
........................................................................ 123
Analog input
APL
%69
Application of the process object (P_APL)
................................................................... 47
Application picture
Application specific modifications
................................................................................ 74
Application specific picture function
............................................................................ 52
AR_WITH_MULTIPLE_CYCLES
............................................................................ 122
Arguments
Arithmetical functions
ASCII_column_separator
.............................................................................................. 26
ASCII_file_Extension
Attributes
Attributes tab
Authority level
AUTHORIZATION GROUP
..............................................................................103
AUTHORIZATION_GROUP
............................................. 74
AUTO_MANUAL_INDICATION
............................................................................. 119
AUTO-RECLOSE TAG
................................................................................................ 88
AUXILIARY_PLUG
%
Background color
BASE
Base system objects
Base system requirements
............................................................................................... 5
BAY
Bay name
BAY_LABEL
BAY_LR_IN_USE
BAY_NAME
.....................................................102
BDU_Fault:C
BGU_INDPF:C
BGU_INDSF:C
BGU_READPF:C
BGU_READSF:C
BGU_WRITPF:C
BGU_WRITSF:C
Breaker indication
1MRS751886-MEN
LIB 510 Configuration
1MRS751886-MEN
LIB 510 Configuration
LIB 510
Index
Configuration Guide
&
Calculation of report data
.............................................................................................. 33
Calculation operation (OPER)
...................................................................................... 48
Calculation order list
Calculation orders
Calculation orders of sampled and period values
......................................................... 48
CB
Channel
CHANNEL_NUMBER
.............................................................................................. 118
CMD_PARAMETER
.......................................................................................... 117
Collection of report data
............................................................................................... 33
Column object
Comment (CM)
COMPACT_INSTALLATION
................................................................................... 118
Components
Configuration of the station picture function
...................................................... 116
Configuration of the switching device
........................................................................ 118
Configuration of the transformer
........................................................................ 118
Configure Function button
............................................................................................ 29
Configuring a Report Object with the Report Object Editor Tool
................................ 43
CONNECT_TO_OBJECT
.......................................................................................... 119
CONTROL_BITS
CONTROL_DIALOG_WINDOW
............................................................................. 119
CONTROL_PULSE_LENGTH
.................................................................................. 118
CONTROL_TYPE
CP
Create Process Objects
CS
Current set of trends
'
Daily report
Data acquisition unit (P_RX)
........................................................................................ 47
Data object values
DATA_ACQUISITION_UNIT
.................................................. 117
DATA_ACQUISITION_UNIT_1
............................................................................... 120
DATA_ACQUISITION_UNIT_2
............................................................................... 120
DATA_ACQUISITION_UNIT_3
............................................................................... 120
DATA_ACQUISITION_UNIT_4
............................................................................... 120
Database structure
Datalogs
Daylight saving
DEF
Default log function
Default time channel
Default_log_function
Default_time_channel
Delete Process Objects
Deleted
Device name
Device/apparatus name
........................................................................................... 93
DEVICE_NAME
..............................................102
DI
Dialog Buttons
.............................................................................................................. 44
1MRS751886-MEN
LIB 510
Index
LIB 510 Configuration
Configuration Guide
Digital input
Directories
Directory structure
Display requirement
DTU 4
Dynamic part
Dynamic text
(
E-Code
Edit Menu Item dialog
EDITABLE_ID_TYPES
............................................................................................... 74
EF attribute
End notation
Engineering menu
Erroneous status
Error messages
Event
Event & Alarm
Event Editor
Event filter
Event filter value
Event handling
Event mask
Event printout
Event reporting
Event texts
EVENT_RECORDING
...................................................................... 117
Execution Delays
Exit
)
Fault Report Browser
Fault Report Configuration tool
.................................................................................. 127
Fault Report Function
FFU_Fault:C
FFU_Start:A
FFU_Start:C
Filter value
FOLDER_1_TITLE
FOLDER_2_TITLE
FOLDER_3_TITLE
FOLDER_4_TITLE
Forecast period area
Format picture
Format text file
Function block
............................................................................................13
FUNCTION_BLOCK
................................................................................ 118
FUNCTION_BLOCK_1
............................................................................................. 120
FUNCTION_BLOCK_2
............................................................................................. 120
FUNCTION_BLOCK_3
............................................................................................. 120
FUNCTION_BLOCK_4
............................................................................................. 120
1MRS751886-MEN
LIB 510 Configuration
LIB 510
Index
Configuration Guide
*
General features
General options
General Settings
General Settings of a Report Object
............................................................................. 44
Group ID (ID)
+
HARDWIRED
Help files
HELP_MENU_ACTION
.............................................................................................. 75
HELP_MENU_PART
........................................................................................... 75
Hourly report
,
ID
ID fields
In Database
IND_DOUBLE_BINARY
.......................................................................................... 117
Index
Index of the process object (P_IX)
............................................................................... 47
INDICATION_TYPE
Input parameter
Input parameters for calculation (DATAIN)
................................................................. 48
Inserted
Inserting a New Report Object
...................................................................................... 42
Installation Tool
INTEGER
Item action program
.
KOEF
/
l Multipliers list
Label text
LIB_OBJECT_NAME
..................................................................................18
Linear scale of the process object (P_SC)
.................................................................... 47
LINK_AR_TAG_TO_
................................................................................................ 122
LINK_AR_TAG_TO_MODULE
............................................................................... 122
LINK_TRIP_TAG_TO_LN_x
............................................................................ 121
LINK_TRIP_TAG_TO_MODULE_x
................................................................ 121
List_separator
LN
Locking mechanism
Logical name
Logical name of the process object (P_LN)
.................................................................. 47
Logical names of the process objects
............................................................................ 18
LR_REMOTELY_CONTROLLABLE
...................................................................... 117
0
MARKABLE_ID_TYPES
............................................................................................ 74
Mask A and Mask B
1MRS751886-MEN
LIB 510
Index
LIB 510 Configuration
Configuration Guide
Mask parameter
Mask value
Max length of datalogs
Max value of the pulse counter (P_PS)
......................................................................... 47
Max_Length_of_Datalogs
............................................................................................. 26
Max_length_of_status_text
........................................................................................... 27
MAX_POSIT
MEAS_1_DECIMALS
............................................................................................... 120
MEAS_2_DECIMALS
............................................................................................... 120
MEAS_3_DECIMALS
............................................................................................... 120
MEAS_4_DECIMALS
............................................................................................... 120
Measured report objects
................................................................................................ 44
MEASUREMENT
Measurements within the bay
...................................................................................... 116
Menu action definitions
................................................................................................. 31
Menu Configuration tool
............................................................................................... 29
Menu structure
MIN_POSIT
MM
MMI
MN
Modified
Monthly report
MOTORIZED
MS
Multipliers list
1
Name
No
NOMINAL_VOLTAGE
.............................................................................................. 119
Number of datalogs
Number_of_Datalogs
Number_of_decimals
2
Object
Object identification attributes
.................................................................................... 102
OI
Open Template
OUTPUT_STATUS
.....................................................................................117
OX attribute
3
P_OBJECT_LN
......................................................... 117
Page layout
Page Setup
PAR
PARALLEL_INDICATION
........................................................................................ 119
Parameter report objects
................................................................................................ 48
Parameters
PC
Period cycle
Period values
................................................................................................................. 71
1MRS751886-MEN
LIB 510 Configuration
LIB 510
Index
Configuration Guide
Period values history
Picture Editor
Picture element
PICTURE FUNCTION NAME
................................................... 89
Picture Function Name
................................................................................117
Picture Functions button
............................................................................................... 28
PICTURE_FUNCTION_VISIBLE
............................................................................ 117
PICTURE_HEADER
............................................................................................ 74
PICTURE_HEADER_FILE
....................................................................................... 116
Point of time change
Preconfiguration
Preconfigured filter
Print Setup
Process object
Process Object Browser
................................................................................................ 46
Progress bar dialog
PROTECTION DEVICE
.............................................................................................. 88
Pulse counter
4
Quick report on daily bases
........................................................................................... 33
5
Rack and module configuration
.................................................................................. 101
REAL
REC 501
Region abbreviation
Relay_Parameters list
.......................................................................................... 130
Report Base
Report base picture functions
........................................................................................ 51
Report components
Report data
Report database
Report day in hours after midnight
............................................................................... 38
Report object
Report Object Configuration Tool
.......................................................................... 39
Report picture
Report Settings dialog
Report Tool
Report week
REPORT_SCALE
REPORT_TYPE
REPORT_UNIT
REPRESENTATION
.......................................................................... 118
Return values
RI attribute
RX
6
Sampled values
Sampled values history
................................................................................................. 38
Sampling cycle
Save As Template
1MRS751886-MEN
LIB 510
Index
LIB 510 Configuration
Configuration Guide
Saving the current trend picture set-up
.......................................................................... 27
Selecting Functions to be Installed
.................................................................................. 8
Send Mask
Settings
Setup
SHOW_ALARMROW
............................................................................................... 116
SHOW_AR_IN_USE
SHOW_AR_NOT_IN_USE
........................................................................................ 122
SHOW_MEAS_2
SHOW_MEAS_2_AS_BAR
....................................................................................... 120
SHOW_MEAS_2_UNIT
............................................................................................. 120
SHOW_MEAS_3
SHOW_MEAS_3_AS_BAR
....................................................................................... 120
SHOW_MEAS_3_UNIT
............................................................................................. 120
SHOW_MEAS_4
SHOW_MEAS_4_AS_BAR
....................................................................................... 120
SHOW_MEAS_4_UNIT
............................................................................................. 120
SIGNAL1_TEXT
Signals
SPECIAL_IDENTIFIER_’number’
.....................................................................121
SPECIAL_IDENTIFIER_x
................................................................ 117
SPECIFIC_MENU_ACTION
....................................................................................... 75
SPECIFIC_MENU_PART
.....................................................................................75
STA object
STA:SEF
Standard Configuration Tool
...................................................................................29
Standard Configuration Tool dialog
.............................................................................. 29
Standard elements
Standard function parameters
...................................................................................... 109
STANDARD_MENU_ACTION
................................................................................... 75
STANDARD_MENU_PART
...................................................................................... 116
Start notation
Start program
Starting Installation
Static event text
Static part
Static Text (OX)
STATION
Station L/R process object
........................................................................................... 133
Station name
STATION_LABEL
STATION_LR_IN_USE
.............................................................................................. 117
STATION_NAME
.............................................102
STATION_TYPE
....................................................... 117
Status bar
Storing picture function data
....................................................................................... 101
Storing relay specific data to the database
.................................................................. 101
SUMMARY_INFO_1
SUMMARY_INFO_2
SUMMARY_INFO_3
SUMMARY_INFO_4
SWITCH_SECTION
SWITCHING DEVICE
................................................................................................. 88
Switching device with truck
........................................................................................ 116
1MRS751886-MEN
LIB 510 Configuration
LIB 510
Index
Configuration Guide
SWITCHING_DEVICE_PURPOSE
.......................................................................... 118
SWITCHING_DEVICE_TYPE
.................................................................................. 118
SYMBOL_WITH_BUTTON
............................................................ 118
Syntax
System Information
7
TAP_POSITION_INDICATION
................................................................................ 119
Text files
Three-state switch
Time intervals
Time related reports
Tool Manager
Tools tab
TOPO_OBJECT_COLOR_NR
................................................................................... 119
TOPO_OBJECT1_COLOR_NR
................................................................................. 119
TOPO_OBJECT2_COLOR_NR
................................................................................. 119
TRANSFORMER
TRANSFORMER_TYPE
........................................................................................... 119
Trend basket
Trend curve line parameters
.......................................................................................... 27
TRIP TAG
Type of the process object (P_PT)
................................................................................ 47
TYPE_MEAS_1
TYPE_MEAS_2
TYPE_MEAS_3
TYPE_MEAS_4
TYPE_OF_SIGNAL1
8
U_INTERLOCKING
.......................................................................................... 118
U_OTHER_OBJECTS
......................................................................... 88
Unit (ST)
Update instructions needed
........................................................................................... 45
Update instructions needed (P_ACT)
........................................................................... 47
Use in Mask
User authorization
User Interface folder
User-defined Definitions
............................................................................................... 39
User-defined groups
User-defined Groups and Procedures
............................................................................ 70
User-defined types
Utility abbreviation
9
Variable
Vector attributes
VISIBLE
VOLTAGE_INDICATION
......................................................................................... 119
:
Weekly report
Welcome! dialog
............................................................................................................. 6
1MRS751886-MEN
LIB 510
Index
LIB 510 Configuration
Configuration Guide
;
X-axis
<
Y-axis
Yearly report
Document Outline
- Introduction
- Installation of LIB 510
- Overview of Event Editor
- Trend
- Measurement reports 2
- Guideline for the substation engineering with LIB 510
- Installation of picture functions
- Configuration
- Example of standard function configurations
- Fault Report Function in LIB 510
Wyszukiwarka
Podobne podstrony:
LIB 500 Configuration Manual
LIB 510 Operator s Manual
LIB 510 MV Process Configuration
LIB 510 MV Process Operator s Manual
LIB 500 Operator s Manual
Brother Fax 510 Plus Home Fax Parts Manual
Manuale configurazione router ( Sitecom PPPoE ) (1)
PANsound manual
als manual RZ5IUSXZX237ENPGWFIN Nieznany
hplj 5p 6p service manual vhnlwmi5rxab6ao6bivsrdhllvztpnnomgxi2ma vhnlwmi5rxab6ao6bivsrdhllvztpnnomg
BSAVA Manual of Rabbit Surgery Dentistry and Imaging
Okidata Okipage 14e Parts Manual
Bmw 01 94 Business Mid Radio Owners Manual
Manual Acer TravelMate 2430 US EN
CISCO how to configure VLAN
manual mechanika 2 2 id 279133 Nieznany
4 Steyr Operation and Maintenance Manual 8th edition Feb 08
więcej podobnych podstron