MicroSCADA Pro SYS

Transcription

1 MicroSCADA Pro SYS

2

3 1MRS Issued: Version: B/ MicroSCADA Pro SYS Contents Copyrights Introduction This Manual Use of symbols Related documents Document conventions Document revisions Migrating an existing MicroSCADA application in SYS 600 and Monitor Pro Exporting information from pictures to data files Configuration Data Export tool Starting Configuration Data Export tool Options Exporting picture data Event conversion Event Conversion Tool Starting Event Conversion Tool Making conversion Creating new SYS 600 application with new process graphics List Based Engineering tool System Requirements Using the tool Create sheet Columns User interface components Tips for using Create sheet Exception handling in Create sheet Symbols, Mappings and Data Source sheets Columns User interface components Defaults sheet Clipboard sheet Object Navigator engineering Installing standard functions Standard Functions of LIB 5xx and SA-LIB Installation and configuration of standard functions 44 3

4 SYS MicroSCADA Pro 1MRS Connecting standard functions to display Connectivity package support Using Input Objects Defining application options Application settings Application Language Lockout duration Daylight settings Process control settings HD space alarm Report settings Customizing Time Formats SQL Exporter Using SQL Exporter Menu bar Toolbar Dialog selections Creating database Creating cyclical measurement recording table Creating history recording table Creating user accounts Enabling and disabling SQL logging Enabling communication between SQL database and SYS Editing command procedures Testing user accounts and databases Managing process objects Adding process object Removing process objects Selecting process objects Using database filter options Exporting list Opening list in Excel Opening list in refreshable Excel range Importing list Cleaning objects Standard functions of SA-LIB Preliminary work Procedures for use with standard functions Communication support Station

5 1MRS MicroSCADA Pro SYS Standard function installation Symbol installation Standard function configuration Configuration with a tool Configuration with the Process Object Tool Example of a station configuration Application engineering information Structure of the station standard function Files Language text file Help text file Configuration files Other text files Process objects Scale objects Command procedures Event channels Bay Standard function installation Symbol installation Standard function configuration Configuration with tools Configuration of process objects Example of a bay configuration Application engineering information Structure of the bay standard function Files Language text file Help text file Configuration files Other text files Command procedures Process objects Scale objects Event channels Switching device Standard function installation Symbol installation Standard function configuration Configuration with tools Configuration of process objects

6 SYS MicroSCADA Pro 1MRS Example of a switching device configuration Application engineering information Structure of the switching device standard function Files Language text file Help text file Configuration files Other text files Command procedures Process objects Scale objects Operation counters Tap changer Standard function installation Symbol installation Standard function configuration Configuration with tools Configuration of process objects Example of a tap changer configuration Application engineering information Structure of the tap changer standard function Files Language text files Help text file Configuration files Other text file Command procedures Process objects Scale objects Operation counters Measurement Standard function installation Symbol installation Standard function configuration Configuration with tools Configuration of process objects Example of measurement configuration Application engineering information Structure of the measurement standard function

7 1MRS MicroSCADA Pro SYS Files Language text file Help text file Configuration files Other text files Command procedures Process objects Scale objects Alarm indicator Standard function installation Symbol installation Configuration with tools Configuration of process objects Example of alarm indicator configuration Application engineering information Structure of the alarm indicator standard function Files Language text file Help text file Configuration files Auto Reclose Standard function installation Symbol installation Configuration with tools Configuration of process objects Application engineering information Structure of the Auto Reclose standard function Files Language text file Help text file Configuration files Process objects Scale objects Trip Signal Standard function installation Symbol installation Configuration with tools Configuration of process objects Application engineering information

8 SYS MicroSCADA Pro 1MRS Structure of the Trip Signal standard function Files Language text file Help text file Configuration files Process objects Scale objects Generator Standard function installation Symbol installation Configuration with tools Configuration of process object Application engineering information Structure of the generator standard function Files Language text file Help text file Configuration files Process object Scale object Line Indicator Standard function installation Symbol installation Configuration with tools Configuration of process objects Application engineering information Structure of the line indicator standard function Files Language text file Help text file Configuration files Command procedures Process objects Scale object Descriptions to the configurable attributes Creating single-line diagram Connecting signals Data variable types Customizing used process object indexes Configuring status signals Customizing Object Browser

9 1MRS MicroSCADA Pro SYS Network topology coloring Switching device Line segment Feeding point Line indicator Transformer Network topology coloring modes Used states and colors Color priorities Network topology coloring system Building network overview Removing the network overview configuration Troubleshooting Network Topology Coloring Status information Using external color handling Additional circuit breaker and earthing switch Using measurement values Measurement value quality Network topology coloring and different representations in same Process Display Alternative building of network overview Launching external application from Process Displays Modificating data variable with SCIL Event List Customizing the column layout Creating custome Event List columns Defining event coloring Event coloring example Preconfiguring events with advanced conditions Advanced condition example Locating object Alarm List Customizing column layout Preconfiguring alarm buffer with advanced conditions Advanced condition, example Advanced condition, example Locating object Blocking List Customizing blocking settings Trends

10 SYS MicroSCADA Pro 1MRS Introduction to trends Copying the trends Exporting trends to the.csv or.txt file Trend Display parameters Application objects Data objects Time channels Measurement Reports Features and options Application specific definitions (reports) Migrating existing Measurement Reports built with LIB 5xx application library Report object settings Report Object Configuration Tool Report Object Configuration Tool tabs Report Object Configuration Tool buttons Inserting new report object Configuring report object with Report Object Editor Tool Dialog buttons General Settings of report object Additional Settings for measured report object types Additional Settings for calculated report object types Execution delays User defined groups and procedures Call-back procedure for sampling cycle Call-back procedure for period cycle Customizing application window Customization dialog Toolbars tab Commands tab Options tab Adding new menus and toolbars Creating new menu Creating new menu by copying existing menu Creating new toolbar Creating new toolbar in Customize dialog Customizing menu commands Adding menu commands from Commands tab Resetting layout, toolbars or localizations Context-sensitive shortcut menus Language support

11 1MRS MicroSCADA Pro SYS Title Icon Menu commands MENUS directory Generating shortcut menus Object types Examples of creating shortcut menus for symbols Troubleshooting Process Display menu Language support Icon Picture specific menu Opening Visual SCIL tools Creating subdrawing for Visual SCIL tool Taking subdrawing into use Command Line Support Starting Monitor Pro with a delay Customizing Monitor Pro appearance User specific appearance Application specific appearance System specific appearance Defining shortcuts to Process Displays Hiding Process Displays from Process Displays Toolbar Custom commands in Monitor Pro Opening display Alarms Blockings Events Trends Measurement Reports Process graphics Current process graphics picture Renaming Process Display Running Command Line Running SCIL Opening Visual SCIL tool Selecting Visual SCIL tool from list Defining Visual SCIL tool file Setting alarm indicator Localizing application Language identifiers

12 SYS MicroSCADA Pro 1MRS Text Translation Tool Text databases Monitor Pro, tools and components Basic workflow of localization Translating the SYS 600 System Texts: Basic work flow in translating Monitor Pro, tools and components Translating user interface components Translating system and application specific toolbars Translating custom commands Removing translation Adding new language in Monitor Pro Using Asian characters Saving Customized Application Search Path and Relative Paths in Process Displays System Self Supervision Supervision Application Objects Communication Station Supervision Monitoring SA symbols Defining object dynamics location in symbol Settings object dynamics Saving supervision display Supervising base system Supervising monitor Supervising application Supervising communication PC-NET Supervising communication line PC-NET IEC OPC Server Supervising station PC-NET IEC OPC Server Supervising LON Clock Master User management Defining user interface Adding user Removing user

13 1MRS MicroSCADA Pro SYS Adding group Removing group Changing password Authorization Default authorization levels Authorization Groups Customization authorization groups Control authorization groups Configure authorization groups Integrating PCM Opening PCM 600 relay tool Controlling PCM 600 by using SCIL Terminology Abbreviations Index

14 14

15 1MRS MicroSCADA Pro SYS Copyrights The information in this document is subject to change without notice and should not be construed as a commitment by ABB Oy. ABB Oy assumes no responsibility for any errors that may appear in this document. In no event shall ABB Oy be liable for direct, indirect, special, incidental or consequential damages of any nature or kind arising from the use of this document, nor shall ABB Oy be liable for incidental or consequential damages arising from use of any software or hardware described in this document. This document and parts thereof must not be reproduced or copied without written permission from ABB Oy, and the contents thereof must not be imparted to a third party nor used for any unauthorized purpose. The software or hardware described in this document is furnished under alicense and may be used, copied, or disclosed only in accordance with the terms of such license. Copyright 2008 ABB Oy All rights reserved. Trademarks ABB is a registered trademark of ABB Group. All other brand or product names mentioned in this document may be trademarks or registered trademarks of their respective holders. Guarantee Please inquire about the terms of guarantee from your nearest ABB representative. 15

16 16

17 1MRS MicroSCADA Pro SYS Introduction 1.1. This Manual 1.2. Use of symbols This manual provides information for application engineers who build up the SYS 600 applications using the new user interface Monitor Pro. The steps for application engineering are: Creating the process database by using the Connectivity Packages, the Excel-based LBE tool or Object Navigator Building the Process Displays by dragging and dropping complete objects from Object Navigator to the Process Display Customizing the Process Display Customizing the list, trend and report displays Customizing the menus and toolbars Localizing the application texts This publication includes warning, caution, and information icons that point out safety related conditions or other important information. It also includes tip icons to point out useful information to the reader. The corresponding icons should be interpreted as follows: The caution icon indicates important information or warning related to the concept discussed in the text. It might indicate the presence of a hazard which could result in corruption of software or damage to equipment or property. The information icon alerts the reader to relevant facts and conditions. Although warning hazards are related to personal injury, and caution hazards are associated with equipment or property damage, it should be understood that operation of damaged equipment could, under certain operational conditions, result in degraded process performance leading to personal injury or death. Therefore, comply fully with all warning and caution notices. 17

18 SYS MicroSCADA Pro 1MRS Related documents Name of the manual MRS number MicroSCADA Pro SYS 600 Operation Manual 1MRS MicroSCADA Pro SYS 600 Process Display Design 1MRS MicroSCADA Pro SYS 600 Installation and Commissioning Manual 1MRS MicroSCADA Pro SYS 600 System Objects 1MRS MicroSCADA Pro SYS 600 Application Objects 1MRS MicroSCADA Pro SYS 600 Visual SCIL 1MRS MicroSCADA Pro SYS 600 Programming Language SCIL 1MRS MicroSCADA Pro SYS 600 System Configuration 1MRS PCM 600 Installation and Commissioning Manual 1MRS PCM 600 Help 1.4. Document conventions The following conventions are used for the presentation of material: The words in names of screen elements (for example, the title in the title bar of a dialog, the label for a field of a dialog box) are initially capitalized. Capital letters are used for the name of a keyboard key if it is labeled on the keyboard. For example, press the CTRL key. Enter key is an exception, e.g. press Enter. Lowercase letters are used for the name of a keyboard key that is not labeled on the keyboard. For example, the space bar, comma key and so on. Press CTRL+C indicates that you must hold down the CTRL key while pressing the C key (to copy a selected object in this case). Press ESC E C indicates that you press and release each key in sequence (to copy a selected object in this case). The names of push and toggle buttons are boldfaced. For example, click OK. The names of menus and menu commands are boldfaced. For example, the File menu. The following convention is used for menu operations: Menu Name > Menu Command > Cascaded Menu Command. For example, select File > Open > New Project. The Start menu name always refers to the Start menu on the Windows Task Bar. System prompts/messages and user responses/input are shown in the Courier font. For example, if you enter a value out of range, the following message is displayed: Entered value is not valid. The value must be 0 to 30. You may be told to enter the string MIF349 in a field. The string is shown as follows in the procedure: MIF349 Variables are shown using lowercase letters: sequence name 18

19 1MRS MicroSCADA Pro SYS Document revisions Version Revision number Date History A Document created B Document updated 19

20 20

21 1MRS MicroSCADA Pro SYS Migrating an existing MicroSCADA application in SYS 600 and Monitor Pro This chapter provides information on the migration tools needed during the application design when the existing LIB 5xx based applications are migrated to use the Monitor Pro s new Process Displays. Usually, an existing application contains a set of pictures and their related process database built with LIB 5xx application library. SYS 600 contains the engineering tools to migrate these applications in a straightforward way. During the migration, the picture configuration information from the existing pictures is copied to the process database. The Monitor Pro user interface uses the copied information. The connection between the existing process objects of the migrated application and the graphical symbols of the new Process Displays is made by dragging and dropping the complete objects during the single line diagram engineering with Display Builder. LIB 5xx application SYS 600 application PDB Fig Migrating process Export configuration Read configuration of the objects A

22 SYS MicroSCADA Pro 1MRS LIB 5xx application SYS 600 application Report database RDB Export configuration Read configuration of the objects A Fig Migrating measurement reports Another migration tool is needed for the event handling concept introduced in SYS 600. In this concept, the Event Objects are displayed in the application s process database. Another event architecture has been used with the existing application, which database has been built with LIB5xx application library and contains the LIB 500 Event List. To provide a continuum from the existing LIB 500 Event List to the SYS 600 Event List, a migration tool to migrate the existing application to the new event handling concept is introduced. The following figure describes both the event handling processes and the role of the migration tool. 22

23 1MRS MicroSCADA Pro SYS LIB 500 Event List SYS 600 Event List Data update from process PDB 3. Format pictures :P :H APL_TEXT.SDB Text files Conversion Tool Fig Event conversion process A SYS 600 Event List concept: 1. The value of the process object is updated 2. Format picture is activated 3. Format picture reads the text related to the event from the text file and shows it in the Event List Event Conversion Tool: 1. Reads all the format pictures and related text files found from the application 2. Puts texts to text database, creates Event Objects, connects Process Objects to Event Objects MicroSCADA Pro Event List concept: 1. The value of the process object is updated 2. Event object is activated. Event Object contains the reference to text database, from where the textual presentation of event is fetched By default, SA control dialogs can connect to the configuration made with LIB 510 MV Process. However, it is possible to export data from any picture function that is designed according to LIB 5xx design rules Exporting information from pictures to data files In a LIB5xx based picture, the parameters describing the object and its behaviour is stored in the picture. When the new Process Displays are used with an existing process database, these parameters need to be extracted from the pictures and made available for the new control dialogs. 23

24 SYS MicroSCADA Pro 1MRS The Configuration Data Export tool is used for this purpose. It extracts the needed information from the pictures and stores it in separate files available for the Process Displays Configuration Data Export tool The Configuration Data Export tool offers the means to reuse the pictures and process database built with LIB 5xx application library when an application is upgraded to the Monitor Pro user interface. First, Configuration Data Export can separate the configuration of the picture functions from the SCIL picture. Next, the tool copies the information to the process database. In case of Measurement Reports, tool creates the external configuration data files that are saved in apl\apl name\reports\preconf. The Process Displays and measurement report displays in Monitor Pro can utilize the exported configuration data. For more information on the picture engineering, refer to SYS 600 Process Display Design manual Starting Configuration Data Export tool To start the Configuration Data Export tool, click the DAT Export button in the Tool Manager dialog, Miscellaneous tab. Fig Configuration Data Export tool icon CDE_Icon 24

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

26 SYS MicroSCADA Pro 1MRS Fig Export Options Exp_Opt Exporting picture data To export configuration data from a picture: 1. Select the picture(s) in the Pictures list from which you want to export data. 2. Select filter from the Options dialog. 3. Click the Export button. For more information on how to finalize the picture engineering, refer to SYS 600 Process Display Design Event conversion In LIB 500 Event List, the format pictures are used for showing the dynamic part of the event text. However, the event text presentation in SYS 600 Event List is based on the Event Objects. When SYS 600 Event List is used with an existing process database, the format picture mechanism must be converted into the new event handling concept. The SYS 600 Event Conversion Tool offers the means to convert the used format picture concept into a new event handling concept. In practice, this means that each process object that has a known LIB 5xx format picture is connected to a comparable Event Object. When the event conversion is done, the same event texts are shown in the SYS 600 Event List and in the LIB 500 Event List Event Conversion Tool The purpose of Event Conversion Tool is: To locate the used, known LIB 5xx format pictures from the process objects of the application. 26

27 1MRS MicroSCADA Pro SYS To create the related Event Objects that the new event handling concept needs. To separate event texts from the text files, and write them to a text database file (APL_TEXT.SDB) of the running application. To connect the created Event Objects to the text identifiers that are located from the text database file. To connect process objects to event objects. Format pictures are still needed to print the events to the Event Printer. Due to this, the format picture information in process database is not modified during the conversion Starting Event Conversion Tool The Event Conversion Tool is started from the Tool Manager dialog in the Miscellaneous tab. Click the Event Conversion button to start the Event Conversion Tool. Fig Icon for opening Event Conversion Tool EC_icon Fig Main view of Event Conversion Tool EC_Tool The Event Conversion Tool contains three tabs: Found Event Text Conventions Not Resolved Modified Process Objects. 27

28 SYS MicroSCADA Pro 1MRS Making conversion Found Event Text Conventions tab shows all the supported format picture conventions found from the application. The conventions within the application can be examined by clicking Search. The Format picture field shows the name of the format picture (PF attribute of process object). The Text file field shows the language text file related to the format picture. Sometimes the event text does not come from the text file, but the value of the process data is shown directly in the Event List (OV-attribute). In this kind of cases a text *Value based form* is shown in the field. The Event object field shows the name of the event object or objects where the process object is connected. When the modification of the process database is done, the Not resolved tab shows all process objects that are not connected to the event object. Possible reasons for the process objects not ti connect are: Not supported software package. The process objects are not recognized because they are not compatible with LIB4. Not supported form convention. Some format pictures have internal logic that is not possible to write open by the Event Conversion Tool. Language text file not found. It is not possible to read the language text file. Event text could not be resolved. Event Conversion Tool does not recognize the text file format and therefore cannot resolve the text. Modified Process Objects tab shows the list of all process objects that are successfully connected to event objects. The conversion can be done by clicking the Search button, which looks for the known conventions within the application. Clickin the Modify DB button makes the changes to the process database. If you do not want to examine the event conventions beforehand, you can click the Modify DB button directly. When the conversion is ready, the result can be saved to a log file. The log file contains all the data found from three tabs in the Event Conversion Tool. It is recommended to take a backup from the application (process database) before making the event conversion. 28

29 1MRS MicroSCADA Pro SYS Creating new SYS 600 application with new process graphics With the LIB based pictures, a lot of engineering tasks were made in the Picture Editor, for example drawing pictures, creating the process database, and so on. In SYS 600, the engineering tasks during application design are changed. The new engineering can be divided in two different approaches: List based engineering Object Navigator engineering. From the two different engineering approaches, the Object Navigator engineering is preferred. List based engineering A new Microsoft Excel based engineering tool is introduced by means of which the creation of objects (stations, bays, devices, measurements, and so on) is done efficiently. Also the new Process Displays can be configured with this tool. As this tool is based on Microsoft Excel, the handling of large amounts of data is quite efficient. Fig describes the list based engineering approach. List Based Engineering approach Creates the process objects PDB MicroSCADA Pro application Connect to process objects Uses the display files Creates the configuration Display file templates Fig List-based engineering approach A Object Navigator engineering Complete objects, for example switching devices, transformers, measurements, as well as LIB standard functions, can now be installed and configured directly in the Object Navigator. Installing such an object means that the corresponding process objects are created and object parameters are stored in the application, but no Process Display elements are built. 29

30 SYS MicroSCADA Pro 1MRS These objects are installed during the single line diagram engineering in the Process Displays by the drag and drop operation. In this operation, all the connections between the display elements and process database are automatically configured. The following figure describes the Object Navigator engineering approach. Object Navigator Engineering approach Creates the process objects and configuration PDB MicroSCADA Pro application Uses the configuration Browse objects Connect to process objects Fig Object Navigator engineering approach A List Based Engineering tool List Based Engineering tool (LBE) is an efficient way to create process objects from a scratch in SYS 600/LIB applications. Creating and configuring the process objects with LBE tool requires: Knowledge on LIB engineering. Information on how the attribute values are stored in the SYS 600 configuration data files. Information on how the Process Displays are created with Display Builder. Technically, the tool is a Microsoft Excel document that contains: A sheet to specify naming convention and per-bay amounts of each supported process object type. One sheet for each supported process object type to fill in the process object configuration data. A sheet to create, edit and delete graphical objects (symbols) in Process Displays. A sheet to define mappings between subdrawing data variables and display data variables. A sheet to create, edit and delete data variables in data sources of Process Displays. A sheet that contains default values and settings. A Clipboard sheet for the user to store temporary data. 30

31 1MRS MicroSCADA Pro SYS System Requirements The user interface components are provided to execute Visual BASIC for Applications (VBA) macros that generate default names and configurations to the LIB object sheets, perform write operations to the process database, provide informative exception handling and operate with graphical objects in Process Displays. In addition to the SYS 600 software requirements, the LBE tool has the following requirements: Microsoft Excel 2000 or later Existing empty or non-empty LIB application in HOT state to perform operations in the process database Dual-display video card and two display devices are recommended to enable more information to be visible at one time For more information about software requirements, refer to Installation and Commissioning Manual Using the tool Before opening the tool, start Microsoft Excel and verify that macro security level is set to "Medium" by selecting Tools > Macro > Security > Security Level. LBE tool is installed in \sc\sa_lib\tools\lbe.xls. When the document is opened, click Enable Macros to enable all the functionality built in the sheets. If you click Disable Macros, the contents will still be visible, but the functionality will not be available. The following sheets are included into this tool: Create Switch Measurement Alarm Transformer Bay LR Station LR Line Indicator Generator AR Trip Symbols Mappings Data Source Defaults Clipboard 31

32 SYS MicroSCADA Pro 1MRS General notes: Keyboard shortcuts CTRL + Page Up and CTRL + Page Down can be used to quickly move between the sheets. Excel's AutoFilter functionality is enabled by default in Symbols, Mappings and Data Source sheets. To enable AutoFilter in other sheets, select Data > Filter > AutoFilter. LBE uses Excel's data validation functionality in several columns of the sheets. If a range is copied from column to another, the data validation (and also cell formatting) in the target range will be overwritten. To prevent this, it is recommended to use Edit > Paste Special > Values when copying data between columns. Most of the macros and event handlers clear Excel's undo stack, so undo will not always be available. This applies especially to the event based sheets ie. Symbols, Mappings and Data Source sheets. Column headings and some of the columns of the sheets are read-only. If their contents are changed, the changes are canceled programmatically by calling Excel's undo function. LBE tool does not use the locking mechanism that for example Display Builder uses when opening a Process Display file. Adding the graphical objects to the network topology coloring and building the topology can be done only in Display Builder. The following sections describe the functionality of these different sheets in the List Based Engineering tool Create sheet This sheet is used to specify the naming convention for process objects (contents of Logical Name attribute) and amounts of each supported process object type per bay. An example in Fig contains 4 bays (B1, B2, B3 and B4) defined for one station (S1). Each bay to be engineered contains multiple object types. 32

33 1MRS MicroSCADA Pro SYS CreateCheet Fig Create sheet Columns The Create sheet contains columns, which identify used naming convention and types of objects. The following tables contain the names and purposes for both of these categories. The columns from LN Prefix to LN Suffix are used together with the marker (see Defaults sheet) to form naming convention for process object logical names. The name is formed as follows: LN Prefix + Station Name + Station Suffix + Bay Name + Bay Suffix + Device Prefix + Device Name + LN Suffix. The Device Name is formed as follows: Device Marker + a running number starting from 1. The columns from Breakers to Tripping Tags contain per-bay amounts of each supported process object type. Only whole numbers greater than 0 are accepted. Table Column LN Prefix Station Name Naming convention columns Purpose Prefix of Logical Name Station name of Logical Name 33

34 SYS MicroSCADA Pro 1MRS Table Station Suffix Bay Name Bay Suffix Device Prefix LN Suffix Table Naming convention columns (Continued) Station suffix of Logical Name Bay name of Logical Name Bay suffix of Logical Name Device prefix of Logical Name Suffix of Logical Name Object type columns Column Purpose Breakers Amount of breaker objects Disconnectors Amount of disconnector objects Measurements Amount of measurement objects Alarm Symbols Amount of alarm objects 2-W Transformers Amount of 2-winding transformer objects 3-W Transformers Amount of 3-winding transformer objects Bay LRs Amount of bay local/remote objects Station LRs Amount of station local/remote objects Line Indicators Amount of line indicator objects Generators Amount of generator objects AR Symbols Amount of auto reclose objects Tripping Tags Amount of tripping tag objects User interface components The buttons in this sheet are used to activate the macros that have influence on the object names in the LIB object sheets. They can also create the process objects in the SYS 600 application with the related Process Display information. All this is done in an efficient way to increase the productivity of engineering. The following table contains the button names and functions. Table Button Create Names Add Symbols Write Data Clear Sheets Buttons in Create sheet Function Creates the names for the process objects in LIB object sheets according to the specified naming convention. This button also creates the process object type specific attribute names and default values. The default values can be overridden by entering new name-value-pairs to the Default sheet. Creates a predefined subdrawing and data variable mappings for each process object in LIB object sheets and adds them to the active Process Display file. The active Process Display file must contain at least one MicroSCADA data source. If more than one MicroSCADA data sources are found, the first one is used. Writes the configuration data files in the SYS 600 application based on the information found in the LIB object sheets. The destination folder for these files is the POBJCONF directory of the application. In this directory, each file is recognized by the process object logical name with a.dat extension, for example \sc\apl\applicationname\pobjconf\s1_sta1.dat. This button also creates the process objects in the process database. Clears the contents of all LIB object sheets without prompting for confirmation 34

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

36 SYS MicroSCADA Pro 1MRS Creating names If a connection to MicroSCADA OPC Server cannot be established from LBE tool, the following message is displayed: A Fig Cannot connect to OPC server LBE tool uses a MicroSCADA command procedure named BGU_CREATEDB. If it cannot be created, the following message is displayed: A Fig Cannot create command procedure If the attribute names and default values cannot be fetched from MicroSCADA, the following message is displayed: A Fig Cannot get attributes If the object type specific CONFIG_DATA_FILE, which is specified in the Default sheet, is not recognized as a SA-LIB file, the following message is displayed: Fig Config data file is not recognized as a SA-LIB file A

37 1MRS MicroSCADA Pro SYS If Station is specified, but Bay is empty or vice versa, the following message is displayed: Fig No bay designation A Writing data If the directory path corresponding to the current application name, which is specified in Defaults sheet, cannot be found, the following message is displayed: A Fig Cannot find application path If writing to a configuration data file is not possible with the LBE tool, the following message, where S1_STA1.dat is the name of the configuration file, is displayed: Fig Cannot write file A

38 SYS MicroSCADA Pro 1MRS If the process object creation fails in the process database, the following message is displayed: A Fig Cannot create process object If one or more SCIL error status codes are received by LBE as a result of the process object creation in the process database, the following message is displayed: Fig Errors when creating process object Creating the object may have totally or partially failed because of the error. A Adding Symbols If the active Process Display file contains no MicroSCADA data sources, the following message is displayed: Fig Cannot add symbols A Symbols, Mappings and Data Source sheets These three sheets are used for list based editing of Process Displays. The sheets are event based, which means that all changes in cell contents take effect immediately in the loaded Process Display. If no Process Display is loaded, LBE uses the template display file specified in Defaults sheet, and the changes are applied to it. 38

39 1MRS MicroSCADA Pro SYS Columns Symbols sheet The columns of Symbols sheet have the following purposes: Object # contains the number of the graphical object. The column is read-only. Subdrawing File contains the file name of the used subdrawing. Entering a valid file name to an empty cell creates a new graphical object (and also writes initial default values to the editable attribute cells of the row, if they are not already specified). Entering a valid file name to a non-empty cell changes the used subdrawing file. Deleting cell contents, or entering an empty string, deletes the graphical object (but not the values of the editable attribute cells of the row). Object Name contains the name of the graphical object. It is not recommended to have several graphical objects with equal object name in one Process Display. ToolTip contains the text that is displayed as a tooltip for the graphical object. Visibility Priority contains the visibility priority level of the graphical object. Valid values can be seen and changed from the data validation in-cell dropdown. X Coord and Y Coord columns contain the coordinates of the graphical object. Only whole numbers between and are accepted. X Scale and Y Scale columns contain the scale factors of the subdrawing. Only decimal numbers between and are accepted. SA Object Type contains the value of SAObjectType custom attribute key of the subdrawing. The column is read-only. SA Object Name contains the value of SAObjectName custom attribute key of the graphical object. The column is read-only. Message column contains the result and time of the last operation related to the subdrawing file. The column is read-only. Mappings sheet The columns of Mappings sheet have the following purposes: Object # contains the number of the graphical object. The column is read-only. Object Name contains the name of the graphical object. The column is read-only. Subdrawing Data Var Name contains the name of the subdrawing data variable. The column is read-only. Data Var Type contains the data type of the subdrawing data variable. The same type is required for the mapped display data variable or constant value. The column is read-only. Data Source # contains the number of the data source that contains the mapped display data variable. The column is read-only. Data Var # contains the number of the mapped display data variable. The column is read-only. Data Source Name contains the name of the data source that contains the mapped display data variable. Entering a valid data source name to an empty cell enables the user to enter also a display data variable name. If more than one data sources are found with equal name, the first one will be used. Entering a valid data source 39

40 SYS MicroSCADA Pro 1MRS name to non-empty cell removes an existing data variable mapping. Deleting cell contents, or entering an empty string, deletes an existing data variable mapping. Display Data Var Name contains the name of the mapped display data variable. Before entering a data variable name, data source name must always be specified first. Entering a valid data variable name to an empty cell maps the subdrawing data variable to the display data variable (and deletes existing constant mapping). If more than one data variables are found with equal name, the first one will be used. Entering a valid data variable name to non-empty cell changes the data variable mapping. Deleting cell contents, or entering an empty string, deletes an existing data variable mapping (but leaves the data source name as is). Constant Value contains the value of the mapped constant. Entering a valid value to a cell maps the subdrawing data variable to the constant (and deletes existing data variable mapping). Entering a valid value to non-empty cell changes the constant mapping. Deleting cell contents, or entering an empty string, deletes an existing constant mapping. Message column contains the result and time of the last mapping operation. The column is read-only. Data Source sheet The columns of Data Source sheet have the following purposes: Data Var # contains the number of the data variable. The column is read-only. Data Var Name contains the name of the data variable. Entering a non-empty string to an empty cell creates a new data variable. Entering a non-empty string to a non-empty cell renames the data variable. Deleting cell contents, or entering an empty string, deletes the data variable (but not the values of the editable attribute cells of the row). It is not recommended to have several data variables with equal name in one data source. Data Var Type contains the type of the data variable. The valid types can be seen and changed from the data validation in-cell dropdown. If text type is selected, length of the data variable is set to 16 characters. Public indicates the scope of the data variable. If the scope is public, the cell contains "x". If the scope is private, the cell is empty. Setting the scope to public is done by entering any non-empty string to the cell, and setting the scope to private is done by deleting the cell contents or entering an empty string. MicroSCADA Object Reference contains the process object logical name + ":P" (+ possible attribute name) + index. The column applies only to MicroSCADA data sources. MicroSCADA Variable Type contains the type of the MicroSCADA variable. The valid types can be seen and changed from the data validation in-cell dropdown. The column applies only to MicroSCADA data sources. "Swap Values 0 and 1" and "Swap Values 1 and 2" columns contain the value swapping information for state indication variables. Enabled swapping type is indicated with "x". Entering any non-empty string to the cell enables the swapping type. Deleting cell contents, or entering an empty string, sets the swapping type to none. Both swapping types cannot be enabled simultaneously 40

41 1MRS MicroSCADA Pro SYS for one MicroSCADA data variable. The columns apply only to MicroSCADA data sources. OPC Item ID contains the MicroSCADA object reference in complete format ie. "\\APL\" + application number + "\P\" + process object logical name + "\" + index (+ ":" + possible attribute name). The column is read-only and applies only to MicroSCADA data sources. Mapping Count contains the sum of subdrawing data variables and other object dynamics that are mapped to the display data variable. A data variable with one or more mappings cannot be deleted. The column is read-only. Message column contains the result and time of the last operation related to the data variable name. The column is read-only User interface components Symbols sheet The user interface components of Symbols sheet have the following purposes: Table Button Open Save As Show Preview Clear Sheets Buttons in Symbols sheet Function Opens a file selection dialog and reads the contents of the selected Process Display file to memory and to Symbols, Mappings and Data Source sheets. Only the attributes of subdrawing objects are displayed in Symbols sheet, other graphical object types are ignored (but not deleted from memory). Previous contents of the sheets are cleared without further notice. Opens a file selection dialog and writes the contents of the active Process Display to the selected file. Shows the current Process Display file in a preview window. Right mouse button enlarges and left mouse button reduces the window size. SHIFT + any mouse button shows the Zoom Control. If Symbols or Mappings sheet is active, a rectangle is drawn around the graphical object that is being edited (the rectangle does is not drawn if multiple rows are selected). Clears the contents of Symbols, Mappings and Data Source sheets, and opens the template display file, without prompting for confirmation. Mapping sheet The user interface components of Mappings sheet have following purposes: Write Object Details to Each Row check box Defines whether or not LBE writes object numbers and names to each row. When this option is not checked, the Mappings sheet is usually more readable, but the object details are needed in each row sometimes when AutoFilters are applied. Data Source sheet The user interface components of Data Source sheet have the following purposes: Data Source text box, spin button and list box Active data source can be changed by entering a valid data source number to the text box, changing the data source number with the spin button, or selecting the 41

42 SYS MicroSCADA Pro 1MRS data source from the list box. Entering a string to the list box renames the active data source. It is not recommended to have empty data source names, or several data sources with equal name in one Process Display. Application text box and spin button Application number of the data source can be changed by entering a valid number to the text box or changing the number with the spin button. The controls are enabled only when a MicroSCADA data source is active. Blink Period text box and spin button Blink period of blinking status colors can be changed by entering a valid millisecond value to the text box or changing the value with the spin button. The controls are enabled only when a MicroSCADA data source is active Defaults sheet Defaults sheet contains settings, attribute names and default values that are essential to the functionality of other sheets, macros and event handlers. General section of Defaults sheet contains the following settings: Number and name of the application where process objects are created to OPC Server ProgID Path to the root directory of SYS 600 Process Display section contains the following settings: Path and file name of the Process Display that is used as a template when the contents of Symbols, Mappings and Data Source sheets is cleared X and Y coordinates of the first symbol of the first bay of the first station in Process Display when Add Symbols button is clicked Y-offset of symbols in a bay when Add Symbols button is clicked X-offset of bays next to each other when Add Symbols button is clicked Y-offset of stations, if symbols are created to more than one station when Add Symbols button is clicked Default visibility priority for new graphical objects Default X and Y coordinates for new graphical objects Default X and Y scale factors for new graphical objects Default Mappings section contains the following settings that are used when Add Symbols button is clicked: Subdrawing data variable names that are mapped to data variables that are created to the first MicroSCADA data source of the active Process Display Possible attribute name + index that are used for creating the object reference of each MicroSCADA data variable Variable type of each MicroSCADA data variable Swapping type of each MicroSCADA data variable, used only if variable type is "State Indication" Subdrawing data variable names that are mapped to constant values 42

43 1MRS MicroSCADA Pro SYS The values for each subdrawing data variable that is specified to be mapped to constant LIB Object Attributes and Default Values section contains the following settings for each supported process object type: Marker that is used in device name and process object logical name when Create Names button is clicked. Subdrawing file name that is used when graphical object (symbol) is added to the Symbols sheet with Add Symbols button. Process object attribute names and default values that are copied to LIB object sheets when Create Names button is clicked Note the following: The attribute names and default values are copied starting from left to right until an empty cell occurs. Both breakers and disconnectors are created in the Switching Device sheet and therefore they have common attribute names. Both 2-winding and 3-winding transformers are created in the Transformer sheet, so they have common attribute names Clipboard sheet This sheet is not used by LBE tool macros at all. It can be used freely as a workspace and for storing cell contents copied or cut from other sheets. By default, its first column contains the file names of all SA symbols, so that they can be copied and pasted instead of manually typing to Subdrawing File column in the Symbols sheet and in the Defaults sheet Object Navigator engineering The function of an application is to fulfil the requirements to monitor and control the process devices related to certain application area. The application area may be an electricity distribution, a heat distribution or an other related application. The application requires its own connections to the process equipment in the form of system and application objects. System objects describe how the system is configured. Application objects are more related to the signal flow, when indications are received in the application database or process devices, which are controlled in the application. For more information, refer to the Application Objects and System Objects manuals Installing standard functions Object Navigator is capable to create application objects or standard functions. In the case of standard functions, a set of application objects is created during the standard function installation. Object Navigator can be used for the objects application engineering with regard to the following operations: Add Delete Modify 43

44 SYS MicroSCADA Pro 1MRS Export Import Document The functionality of the Object Navigator to create and engineer certain types of application objects is described more detailed in the Application Objects manual. The following section describes how Object Navigator can be used for creating and engineering the standard functions Standard Functions of LIB 5xx and SA-LIB The Substation Automation Library (SA-LIB) is included in SYS 600. This library contains the most generic Substation Automation library functions. These functions can be used during the application engineering to model the application related process. Each standard function contains a set of configurable attributes, which specify how the signal flow is passed between the process devices and the application database. The following application process related standard functions are included in the SA- LIB: Station Bay Switching Device Tap Changer Measurement Alarm Indicator Auto Reclose Trip Signal Generator Line Indicator If the SYS 600 system also contains Standard Application Library LIB 5xx products, they are included in the list of standard functions as well. For more information on the symbols, refer to Chapter 6. Standard functions of SA- LIB Installation and configuration of standard functions In the Object Navigator, installing of standard functions is possible when Object > Install Standard Function is selected from the menu bar. The Install Standard Function dialog is then opened, see Fig

45 1MRS MicroSCADA Pro SYS A Fig Install Standard Function Expand the SA_LIB Process node, select a standard function, then click Install or press Enter. The Standard Function Tool is now opened, see Fig

46 SYS MicroSCADA Pro 1MRS Standard Function Tool has the Attributes, Programs and Tools tabs, see Fig A Fig Standard Function Tool In Standard Function Tool, the standard function related configurable attributes are displayed and configured in Attributes tab. In the Programs tab, select the program you want to edit. The standard function specific tool is found on the Tools tab. When Standard Function Tool is opened, the default values are assigned in the attribute list. During the application engineering, these attributes are engineered to the values required by the application in question. When Apply is clicked, the configuration for these attributes is created. When this is done, the Apply button is dimmed. The next step is to start the Process Object Tool from the Tools tab. This can be done either by double-clicking the Process Object Tool in the list or selecting the Process Object Tool and clicking Open. When this is done, the Process Object Tool is opened, see Fig

47 1MRS MicroSCADA Pro SYS Fig Process Object Tool Process Object Tool In the Process Object Tool, there are three tabs: New Existing Other On the New tab, the standard function related process objects can be created one by one or in small groups with the Create button located on the bottom row of the tool. The Create All button creates all the process objects on the New tab. After the process objects have been created, they appear on the Existing tab. The Existing tab of the Process Object Tool includes functionality to directly edit the process object attribute values usually modified in the Process Object Form of Object Navigator. The editable process object attributes are: IU = In Use SS = Switch State UN = Unit Number OA = Object Address OB = Object Bit Address The OA and OB attributes are displayed and handled as process object type dependent encoded values, like in the Process Object Form of Object Navigator, thus they are not necessarily the same values as stored in the SYS 600 process 47

48 SYS MicroSCADA Pro 1MRS database. The titles for OA and OB fields are surrounded with brackets to indicate this encoding and slight address naming inaccuracy. Both the OA and OB attributes are displayed as decimal numbers, ignoring the Output Type attribute definition. A separate edit area (bottom of the Existing tab) is used for editing purposes in this tab. Read-only columns for the attributes are also shown in the process object list of the Existing tab. When a existing process object is selected in the Process Object Tool, the current attribute values for IU, SS, UN, OA and OB are displayed in the edit area together with their corresponding dialog commands. When multiple process objects are selected, the attribute values of the first selected object are shown in edit area, and if an attribute value is modified, this has effect on the attribute value for all the selected process objects. However, if multiple process objects are selected, then the OA and OB attribute fields are disabled; the UN attribute is the only address attribute, which can be changed alone. If the OA or OB attribute is changed, all the three/two address attributes must be defined before applying the change. If all address attributes UN, OA and OB have their initial values (UN=0, OA=0 and OB=16), they are shown as empty fields. The change in IU or SS attribute value is executed immediately after modifying the value of the edit control, except for multiple selected objects. After this, a confirmation prompt appears. The UN, OA and OB attribute changes are executed only after the user clicks the Enter button, on the right hand-side of the attribute edit areas, or after the user presses the Enter key on the keyboard. The Other tab shows indexes that are not recognized by a standard function. This happens when the user creates new indexes for an existing process object group in the Object Navigator. For more information on the Object Navigator, refer to the Application Objects manual Connecting standard functions to display Object Browser can be used for creating display symbols based on existing process objects in the process database. The browser contains the insertable objects structured in tree view. Object Browser is opened by selecting the command Object Browser in the Actions menu of Display Builder. Object Browser displays the object structure for all the applications. An application can be selected from the drop-down list in the upper part of the dialog. Select an application from the list and click the Select button to update the view. The symbols can be inserted in the display by dragging them to the drawing area. Station and bay symbols are dragged from the corresponding node. As an example, dragging an Incoming 110kV object in Fig creates a bay symbol in the display. Dragging an Eastwick object creates a station symbol. 48

49 1MRS MicroSCADA Pro SYS Fig View of the Object Browser A Connectivity package support With SCL import function you can import new objects with configurations from an existing scl file. This function can be used with IEC Protocol. The SCL Importer tool is opened from the Tool Manager s Application Objects tab. Using SCL Importer 1. Open the tool from the Tool Manager by clicking its icon. Fig SCL Importer icon 49

50 SYS MicroSCADA Pro 1MRS Fig SCL Import dialog A In the SCL Import dialog, browse the scl file you want to import. See Fig Select the application and language from the drop-down list if needed. 4. Click Import. 5. You can see the created process objects and their indexes by clicking the View Log, which activates after importing. Fig Viewing Log File A

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

52 SYS MicroSCADA Pro 1MRS Right-click the Input Object and select Input Object Properties to open the Input Object Properties dialog. The data variable that is mapped to the object is displayed in the Variables list box, see Fig Fig Mapped data variable 4. To change the mapped data variable, click the Change button and select the data variable. 5. Click OK. 6. Right-click the Input Object and select Properties. A

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

54 54

55 1MRS MicroSCADA Pro SYS Defining application options To define application options, select Tools > Options... You can specify application specific options such as: Application owner First picture shown after login Application logo picture System location System name Product info Lockout duration Language settings Daylight Saving time Process control Show object ID HD space alarm Report Settings Switch device presentation To modify these options, your authorization level must be Engineering (2), refer to Chapter 18. Authorization Application settings You can modify the application settings by selecting the Application Setting tab. The application name is shown in the title bar of the Option dialog. In practice, this is the name of the customer to whom this product is licensed. The name of the application cannot be changed in the Application Settings tab, see Fig

56 SYS MicroSCADA Pro 1MRS Fig Application settings You can define a certain Process Display to be shown after logging by browsing the Process Display to the First picture shown after login box. This picture can be any.v or.sd type of picture. System location is an attribute that needs to be configured. This defines whether SYS 600 is running as Network Control Center (NCC) or Substation Control System (SCS). To be able to make any changes in the application settings, the authorization level must be Engineering (2) in the authorization group PRO_OPTIONS_HANDLING. For more information about authorization, refer to Chapter 17. User management. The only exception to this rule is the monitor language that can be set by all the users. To save the new settings, click OK or Apply. Clicking Cancel returns the previous settings Application Language You can modify the language settings in the Application Language tab. You can select the language in the drop-down list, see Fig The default language is English and the following customized languages (if any) are defined as local languages. The monitor language changes the language used in pictures and dialogs. The selected language will remain active as long as the application in the monitor is open. 56

57 1MRS MicroSCADA Pro SYS When printing to an event printer, the application language is used. The application language is the same for all the users within the same application regardless of the used monitor language. The change of the application language will be valid until it is altered again in the Application Language. The application language does not have any effect on the language shown in the monitors. The monitor language and the application language are selected from the drop-down list. To save the new settings, click OK or Apply. Clicking Cancel returns the previous settings. A Fig Application Language tab When copying a user profile from an existing user to a new user, the user language is also copied Lockout duration You can set the lockout duration time in the Lockout Duration tab. The lockout duration sets the session length, see Fig When the lockout duration time expires, the authorization level is reset to View (0). For more information about the authorization levels, refer to Chapter 18. Authorization. The lockout duration time is given in hours (from 1 to 255). 57

58 SYS MicroSCADA Pro 1MRS A Fig Lockout Duration tab The program informs you about the authorization level reset. The notification regarding the expiring time is displayed according to the times defined in the Session expiring notify times field. The times are given in minutes before the resetting. A maximum of five different notifications can be given. To quickly delay the expiring time, click the Delay One Hour or Delay Eight Hours button in the Autologout dialog. If you change the lockout duration or session length notify times, the new values are not taken into use until the next login Daylight settings The session duration can be activated or deactivated with the Enable and Disable lockout duration check boxes. By default, the lockout duration time is disabled. If the session duration is in use, the session duration time and the session expiring notify times can be changed. Otherwise the session duration is unlimited and the session expiring notify times are not accessible. To save the new settings, click OK or Apply. Clicking Cancel returns the previous settings. The lockout function can be configured to close the Monitor Pro application window when the lockout duration time expires by checking Close Monitor Pro. Closing the Monitor Pro application window frees a license. You can set the daylight saving time on the Daylight Setting tab. If the daylight saving time function is set in use, the system time will be automatically adjusted to the normal time and to the daylight saving time, see Fig

59 1MRS MicroSCADA Pro SYS Fig Daylight Settings tab A When the operating system changes the time to daylight saving time or standard time, application specific action may have to be performed in SYS 600. If adjusting applications for daylight saving is enabled, the event is set to the Event Display and event printer. You can create two command procedures for application specific programming: BGU_TIMEFO:C is executed when the clock is moved forwards BGU_TIMEBA:C is executed when the clock is moved backwards The point of execution time is 20 seconds after the change. Command procedures mentioned above are executed in each application found. It is recommended to define the point of the time change few minutes over an even hour in order to avoid unnecessary system load. When the Automatically adjust applications for daylight saving changes option is enabled, the application handling the actions can be selected from the drop-down list. To save the new settings, click OK or Apply. Clicking Cancel returns the previous settings Process control settings You can define the process control settings on the Process Control tab. You can set the behaviour of printing and the MV process control when operations are executed, see Fig When the Close dialog after execution option is selected, the control dialogs, for example breaker dialogs, are closed after the operation is done. The Horizontal offset and Vertical offset values configure the position of the Control Dialog. 59

60 SYS MicroSCADA Pro 1MRS Fig Process Control tab To activate or deactivate the options, select or clear the check boxes. To save the new settings, click OK or Apply. Clicking Cancel returns the previous settings. A HD space alarm You can define the hard disk supervision function on the HD Space Alarm tab to supervise the free hard disk space. With this function you receive an early warning if there is a risk of running out of space on the hard disk, see Fig

61 1MRS MicroSCADA Pro SYS A Fig HD space alarm dialog You can give a lower alarm limit for the disk space by selecting the alarm limit from the Alarm limit drop-down list. You can also type the required limit. The limit is presented as mega bytes. If you set the alarm limit to zero (0) or select Not in use from the drop-down list, the hard disk supervision is stopped. A warning limit is calculated from the alarm limit. The warning limit is 10% higher than the low alarm limit. To save the new settings, click OK or Apply. Clicking Cancel returns the previous settings Report settings You can define the report settings on the Report Settings tab. The report settings function defines the application specific parameters used by the LIB 510 Measurement Reports 2, see Fig For more information on configuring LIB 510, refer to the LIB 510 *

62 SYS MicroSCADA Pro 1MRS A Fig Report Settings dialog Before defining the reports, the following definitions should be settled: Table Report settings Setting Explanation Default Base Period (min) * Defines a period cycle to be used within the 60 min. reports. The period cycle can be either 15 min., 30 min. or 60 min. Base Period History Length (years) * Defines the length of the period values history in years. The history length can be from 1 year up to 5 years. 2 years Forecast Period (days) Defines the length of the forecast period area in 0 days days. The forecast period area can be used within the reports, for example for monitoring predicted future values. The forecast period area can be up to 15 days. Begin Of Day (hour) * Defines the beginning of the report day in hours 0 after midnight. Begin of Week Defines the beginning of the report week. Monday Default Sampling Frequency (min) * Default Sampling History Length (days) * Defines a sampling cycle to be used within the reports. Defines the length of the sampled values history in days. The history length can be up to 15 days. If the history length is set to 0, the only sampled values of the current period will be stored into the report database. 3 min. - These definitions are valid for the entire application. Changing these definitions (the ones marked with *) afterwards causes loss of all the existing history data. 62

63 1MRS MicroSCADA Pro SYS Each parameter can be selected from the drop-down lists, where all the available choices are listed. To save the new settings, click OK or Apply. Clicking Cancel returns the previous settings. If there are any previous report settings made within the application, the existing report database will be reset and all data will be lost. The report database is checked during the saving and if resetting is needed, an information dialog will be shown to confirm or cancel the saving Customizing Time Formats Date format for Alarm and Event Display, Alarm Row and time fields in Monitor Pro can be customized for each user individually. Date format is defined by the key FreeDateTimeField in section DAYFORMAT of the FrameWindow.ini configuration file: [DAYFORMAT] ;Datetime format, can be for example "%Y-%m-%d %H:%M:%S" (notice quotation marks!). If not defined the format is get from MicroSCADA (when logged in) FreeDateTimeField= The configuration file is located at \sc\apl\<application name>\par\<user name>\framewindow.ini. Quotation marks must be used in the date format string. If FreeDateTimeField key is empty (default), the time format is taken from SYS:BTF (Time Format) -attribute: If SYS:BTF is 0, then format %Y-%m-%d %H:%M:%S is used. If SYS:BTF is 1, then format %m-%y-%d %H:%M:%S is used. If %S specifier is used and milliseconds are available for the attribute in question, milliseconds are automatically added to formatted string in Event Display and Alarm Display. Milliseconds are displayed immediately after %S, separated with period (.) character. Following format specifiers can be used in format string. Table Custom time format specifiers Specifier Description %a Abbreviated weekday name %A Full weekday name %b Abbreviated month name %B Full month name %d Day of month as decimal number (01 31) %H Hour in 24-hour format (00 23) 63

64 SYS MicroSCADA Pro 1MRS Table Custom time format specifiers %I Hour in 12-hour format (01 12) %m Month as decimal number (01 12) %M Minute as decimal number (00 59) %p Current locale's A.M./P.M. indicator for 12-hour clock %S Second as decimal number (00 59) %y Year without century, as decimal number (00 99) %Y Year with century, as decimal number Any other charactes are added to resulting string as given 64

65 1MRS MicroSCADA Pro SYS SQL Exporter 5.1. Using SQL Exporter SQL Exporter is used to get an HSI (human-system interface) for selecting process objects to be sent to an SQL database. With SQL Exporter, a process object can be connected to a history database, a measurement database (cyclic) or to both. To set up the connection between the SQL server and SYS 600: 1. Create a database. 2. Create tables for cyclical measurement recording and history recording. 3. Create user accounts. 4. Enable communication between the SQL database and SYS Edit command procedures. 6. Test the user accounts and database. To open SQL Exporter, click the SQL Exporter icon in Tool Manager. The left pane of the SQL Exporter dialog contains process objects in the SYS 600 database, see Fig The process objects are filtered according to the options specified in the filter options below. The right pane contains the process objects that are connected to the SQL database, also filtered according to the filter options below. In the middle of the dialog, there are buttons for adding and removing objects to/from the SQL database. Fig SQL Exporter A

66 SYS MicroSCADA Pro 1MRS Menu bar Toolbar The main menu bar contains four menus: File, Edit, View and Help. File contains three menu commands: Exit Exit closes the tool. Import from file Export to file For information about the import and export functions, refer to Section 5.9. Exporting list and Section Importing list. Edit has three menu commands: Clean RDBMS Objects SQL Logging enabled/disabled For information about the functions, refer to Section Cleaning objects and Section Enabling and disabling SQL logging. View contains one menu command Toolbar Hides the main toolbar. Help contains one menu command RDBMS Tool Provides the information about SQL Exporter and the SYS 600 system such as version numbers and license information. Table Toolbar buttons Toolbar button Description Use Exit for exiting the program. The same command can be found in File > Exit. Use Import for importing the CSV files (comma delimited). The same command can be found in File > Import from file. For more information about importing files, refer to Section Importing list. Use Export for exporting the CSV files. The same command can be found in File > Export to file. For more information about importing files, refer to Section 5.9. Exporting list. Use Enable to enable the SQL logging. The same command can be found in Edit > SQL Logging enabled. Use Disable to disable the SQL logging. The same command can be found in Edit > SQL Logging disabled. 66

67 1MRS MicroSCADA Pro SYS Dialog selections Database Objects Process objects in the database are filtered according to the database filter options. When an object is selected, the object's OI (Object Identifier) and OX (Object Text) are shown in the Selected Process Object field. If the object can be added to the SQL system, Add is activated. Selected Process Object info When a process object in the Database Objects or the objects list is clicked, the object is displayed in this field. If several objects are selected, the field is empty. RDBMS objects The process objects connected to the SQL database are listed under the objects. When a process object is selected, the information about the object is displayed in the Selected Process Object info field and Remove is activated. Database selection To choose whether the object should be connected to the history database, the cyclic database or both, select one of the check boxes or both. SQL Exporter suggests the history database for indications and alarms and the cyclic database for analog values. If more than one object is selected, no suggestions are made. The Add and Remove buttons To add or remove objects that are to be connected to the SQL system, use Add or Remove. These buttons are enabled and disabled according to what is allowed to do with the selected process objects. For more information about adding or removing process objects, refer to Section Adding process object and Section Removing process objects. Process object filter options The five optional filters can be used one at a time or together. The selected filters apply to both the process objects and to the SQL process objects lists. For more information about the filter options, refer to Section Using database filter options Creating database To create a database: 1. Install Microsoft SQL 2000 Server. 2. Select Start > Programs > Microsoft SQL Server > Enterprise Manager to start the Enterprise Manager of the SQL Server. 3. Create a new database by right-clicking the server and selecting New > Database, see Fig

68 SYS MicroSCADA Pro 1MRS Fig Creating a new database 4. Name the database, for example SCADA. A Creating cyclical measurement recording table The cyclically sent values are saved in the process object table (MSPDB). Typically, values are measurements. The SYS 600 command procedure updates the values every 15 minutes and a new value is inserted to a new row in the table. If SYS 600 does not send the process objects, the process objects are no longer updated. The old process object are not removed. Unique ID consists of: LN IX Moment Moment_IX If several signals from a process object have the same LN and IX, the values are indexed with the Moment_IX time stamp. To create a table: 1. Open Enterprise Manager and create a new table. 2. Name the table columns for the database as shown in Fig

69 1MRS MicroSCADA Pro SYS Fig Defining table for the cyclical recording 3. Save the table as a MSPDB. 4. Run the following code to create a table. The table can be created with the Query Analyzer, for example. CREATE TABLE [mspdb] ( [LN] [varchar] (50) NOT NULL, [IX] [int] NOT NULL, [Moment] [varchar] (23) NULL, [Object_identifier] [varchar] (50) NULL, [Object_text] [varchar] (50) NULL, [Value] [float] NULL, [Status] [varchar] (15) NULL, [Last_Update] [varchar] (25) NULL, [Sort_type] [varchar] (10) NULL, [Process_type] [varchar] (20) NULL ) ON [PRIMARY] You must have engineering rights to run the code. A Fig describes how an update of a process object s value is distributed to the cyclic database, or in other words, to the MSPDB SQL table. 69

70 SYS MicroSCADA Pro 1MRS MSPDB What is updated? Process Object When the user adds a process object to the cyclic database in the tool, the process object is added to a list in the file T_objects.dat When the object is removed from the cyclic database it is also removed from T_objects.dat Updating data Time Channel SQL_FLUSH_T Executes the SQL_FLUSH_T command procedure Execution cycle (CY2) = 15 min Command Procedure SQL_FLUSH_T Executes com.proc. SQL_FLUSH with variable TIME= yes SQL_FLUSH reads from T_objects.dat which process object s values to update in MSPDB A Fig Information flow to MSPDB The SQL table register changes only. If the states of the process objects are static, nothing is updated in the tables Creating history recording table The history and event values are saved in the process object table (MSPDB_hist). Typically, values are indications or alarms. The values are saved in the SYS 600 queue file and sent every five seconds to the history table. Every value from the queue file is added to the table. Therefore, there can be several entries from the same process object. The new rows are added until the table size reaches the limit of the SQL system. A unique ID consists of: LN IX RT RT_IX If several signals from a process object have the same LN and IX, the values are indexed with the RT_IX time stamp. To create a table: 1. Open Enterprise Manager and create a new table. 2. Name the table columns for the database as shown in Fig

71 1MRS MicroSCADA Pro SYS Fig Defining table for the history recording 3. Save the table as a MSPDB_hist. 4. Run the following code to create a table. The table can be created with the Query Analyzer, for example. CREATE TABLE [mspdb_hist] ( [LN] [varchar] (50) NOT NULL, [IX] [int] NOT NULL, [DI_OV] [int] NULL, [AI_OV] [float] NULL, [RT] [varchar] (23) NULL, [OI] [varchar] (30) NULL, [OX] [varchar] (50) NULL, [OS] [varchar] (30) NULL, [Sort_type] [varchar] (10) NULL, [Process_type] [varchar] (20) NULL ON [PRIMARY] You must have engineering rights to run the code. A When the user adds a process object to the history database (MSPDB_Hist SQL table) in SQL Exporter, the process object is connected to the SQL_WRITE_DB_EVENT event channel. Fig describes how, for example, a change in an indication object is distributed to the history database. 71

72 SYS MicroSCADA Pro 1MRS MSPDB_HIST Queuing data Process Object Connected to the event channel via attribute AN Action Activation (AA) on new value or ack. Event Channel SQL_WRITE_DB_EVENT Connected to the command procedure via attribute AN Command Procedure SQL_WRITE_DB_EVENT Writes SQL commands to Queue.txt about what to insert to MSPDB_Hist Dequeuing data Time Channel SQL_FLUSH Executes the SQL_FLUSH command procedure Execution cycle (CY2) = 5 sec Command Procedure SQL_FLUSH Reads SQL commands from Queue.txt about what to insert into MSPDB_Hist. A Fig Information flow to MSPDB_Hist The SQL tables register changes only. If the states of the process objects are static, nothing is updated in the tables Creating user accounts To create a new user: 1. Select <new> from the login name drop-down list to create a new user account, see Fig Fig Creating a new user A

73 1MRS MicroSCADA Pro SYS Define options for the new SQL user, see Fig Type the user name in the Name field. 4. Select the SQL Server Authentication option button from the Authentication field. 5. Type the default password in the Password field. 6. Select a database created before, for example SCADA, from the Database dropdown list. 7. Select the Database Access tab. Fig Defining a new SQL user options. A

74 SYS MicroSCADA Pro 1MRS Define the database that the user can access by selecting the database defined before, see Fig Select the new user from the Database Role field. Fig Defining database access 10.Click Properties to open the Database User Properties dialog, see Fig Define the needed permissions. A The user must have at least write/delete permissions. 74

75 1MRS MicroSCADA Pro SYS Fig Defining access rights 12.Click OK to save the settings. A Enabling and disabling SQL logging Select Edit > SQL enabled/disabled to turn on or off the logging to SQL. The function is useful when working with the application Enabling communication between SQL database and SYS 600 To enable communication between the SQL database and SYS 600, define the ODBS/DDE connection settings. 1. Select Start > Settings > Control Panel > Administrative tools > DataSources (ODBC). 75

76 SYS MicroSCADA Pro 1MRS Select Add in the System DSN tab, see Fig Fig Adding SQL Server A

77 1MRS MicroSCADA Pro SYS Select the SQL Server in the Create New Data Source dialog, see Fig Fig Selecting a database 4. Click Finish to display the SQL server configuration dialog. A

78 SYS MicroSCADA Pro 1MRS Type the name of the data source in the Name field. The name is used to connect to the database through SYS 600, see Fig Type the description of the data souce in the Description field. 7. Select the server that SYS 600 is connected to. If the server and the client are on the same computer, it is possible to use localhost as an SQL server. Fig Creating a new data source 8. Click Next. A

79 1MRS MicroSCADA Pro SYS Select the SQL server authentication and type the user name and password in the Login ID and Password fields, see Fig Use the same user name as created in Section 5.5. Creating user accounts. Fig Click Next. Defining authentication when logging on A

80 SYS MicroSCADA Pro 1MRS Select a default database, for example SCADA, see Fig Select the same database as created in Section 5.2. Creating database. Fig Selecting the default database 12.Click Next. 13.Select the Perform translation for character data check box, see Fig A Fig Selecting the Perform translation for character 14.Click Finish. After creating the database, test it as described in Section 5.7. Testing user accounts and databases. A

81 1MRS MicroSCADA Pro SYS Editing command procedures To enable SQL Exporter to log on to the SQL database, edit the SQL_FLUSH command procedure in SYS 600, see Table Table Command procedures to be edited. SQL_DATABASE Rename the value with the same name as used to refer to the data source in Section 5.6. Enabling communication between SQL database and SYS 600. SQL_USER Rename the value with the same name as created in Section 5.5. Creating user accounts. SQL_PASSWD Rename the value with the same name as created in Section 5.5. Creating user accounts. ;*************** ;set "on" to log, "off" to disable ;********************************************* Do not change the rest of the configuration. Connect the RDBMS event channel (SQL_WRITE_DB_EVENT) to a Process Object with SQL Exporter in SYS Testing user accounts and databases Test the connection to the SQL Server with SQL Query Analyzer. 1. Select Start > Programs > Microsoft SQL Server > Query Analyzer to start SQL Query Analyzer. 2. Type the required information in the Connect to SQL Server dialog. 3. Try a simple query to see the content of the database, for example type select * from mspdb in the upper pane, see Fig The column headers are the same as defined in Section 5.3. Creating cyclical measurement recording table. 81

82 SYS MicroSCADA Pro 1MRS Fig Testing the database connection A It is possible to type several queries at a time, for example: Select * from mspdb Order by mspdb.moment Select * from mspdb_hist Order by mspdb_hist.rt 5.8. Managing process objects Adding process object To add a process object to the SQL system: 1. Open SQL Exporter. 2. Select a process object from the Database Objects list. 3. Select whether you want to add the process object to the history or to the cyclic database (or both). 4. Click Add. The process object is displayed in the objects list. To add several process objects to the SQL system at once: 1. Hold down the CTRL key and click all the process objects you would like to select or drag the cursor over the process objects to select them. 2. Select whether you want to add the process objects to the history or to the cyclic database (or both). 3. Click Add. In general, measurements are added to the cyclic database while indications, alarms, and so on are added to the history database. 82

83 1MRS MicroSCADA Pro SYS Removing process objects To remove a process object from the SQL system: 1. Open SQL Exporter. 2. Select a process object from the objects list. 3. Click Remove. The process object disappears from the objects list. To remove several process objects from the SQL system at once: 1. Press CTRL and click all the process objects you would like to select or drag the cursor over the process objects to select them. 2. Click Remove. Note that you cannot actually remove anything from the history database with the SQL Exporter. You only stop the process object s value from being registered in the history database when you remove it from the objects list. Clicking the Remove button does not remove any rows from the cyclic database. It only stops the object s value from being updated in the SQL database Selecting process objects Excel can be used to create a list where you have selected which process objects are to be connected to the SQL database. Create a list in Excel with four columns: 1. In the first column, add logical names (LN). 2. In the second column, add an index (IX). 3. In the third column, add an X if you would like to connect the process object to the history database. 4. In the fourth column, add an X if you would like to connect it to the measurement database. The column headers do not necessarily need to be included. The import function in the SQL Exporter starts reading process objects only from the second row, so if a process object is on the first row, it is ignored. Make sure that the columns are separated with commas or semicolons and not with any other character. Otherwise, the SQL Exporter cannot read your file correctly. For information about saving the Excel list in a correct format, see Section Importing list. An easy way to get a pre-made list of the process objects in the current application, is to use the export function in SQL Exporter. For more information about exporting, refer to Section 5.9. Exporting list. After export, import the list to Excel and add X:s. For more information about importing, refer to Section Opening list in Excel. 83

84 SYS MicroSCADA Pro 1MRS Using database filter options You can filter the process objects in the SYS 600 and SQL databases according to their attributes LN, IX, PT, OA and UN. To use a filter, select the check box of the filter you would like to use. It is possible to use the filters independently or several filters combined. Note that both the Database Objects and RDMS Objects lists in the SQL Exporter are filtered using the same filters. Filters: LN (Logical Name): You can use an asterisk (*) as a wildcard character at the end of the filter string. The filter is case sensitive. IX (Index): Enter an index number. It is only possible to enter numbers; wildcard characters are not allowed. PT (Process Object Type): Select the type of objects list you would like to be visible: 3 Single indication 6 Digital input 9 Analog input 12 Double indication OA (Object Address): Enter an object address number. It is possible to enter numbers only; wildcard characters are not allowed. UN (Unit Number): Enter a unit number. It is possible to enter numbers only; wildcard characters are not allowed Exporting list To export the Database Objects list to a CSV file (comma delimited file): Click Export Select File > Export to file. Use the shortcut CTRL+E. A list with the filtered process objects in the Database Objects list is written to a CSV file. The list in the file has 4 columns separated with commas. The column headers are: LN IX Send to history database Send to measurement database Mark the process objects that are connected to the history or the measurement database respectively with an X in the corresponding column. The CSV file can be imported to Excel, for example. For more information about opening the CSV file in Excel, refer to Section Opening list in Excel. 84

85 1MRS MicroSCADA Pro SYS Opening list in Excel To import the list to Excel: 1. Open the text file created with SQL Exporter in Excel. 2. Text Import Wizard opens, see Fig Select the Delimited option in the Original data type field. The signal list generated with the SQL Exporter has the columns separated with a comma as a delimiter. 4. Click Next. Fig Excel Text Import Wizard, step 1 A Select Comma in the Delimiters field, see Fig

86 SYS MicroSCADA Pro 1MRS Fig Excel Text Import Wizard, step 2 A In the Data preview area, you are able to preview the results of the import operation. 7. Click Finish to import the list into an Excel worksheet Opening list in refreshable Excel range Use this procedure if you want to refresh the data in Excel whenever the original text file changes. If you want to copy the data into Excel without maintaining a connection to the original file, you can open the text file in Excel. Once the list is imported, it can be saved as a normal Excel file. To create a refreshable Excel: 1. Click the cell where you want to place the data from the text file. To ensure that the external data does not replace existing data, make sure that the worksheet has no data below or to the right of the cell you click. 2. Select Data > Import External Data > Import Data. 3. Select the text file you want to import as an external data range. 4. To specify how you want to divide the text into columns, follow the instructions in Text Import Wizard. 5. Click Finish. 6. Click Properties in the Import Data dialog to set formatting and layout options for how the external data range is imported into Microsoft Excel. 7. In the Import Data dialog, do one of the following: 7.1. To place the data to the existing worksheet, select Existing worksheet. 86

87 1MRS MicroSCADA Pro SYS To place the data to a new worksheet, select New worksheet. Microsoft Excel adds a new worksheet to your workbook and automatically puts the external data range in the upper-left corner of the new worksheet. 8. Click OK. To refresh the external data range when the original text file changes: 1. Click Refresh Data on the External Data toolbar. 2. Select the text file in the Import Text File dialog. 3. Click Import. To change the settings made in the Text Import Wizard: 1. Click Edit Text Import on the External Data toolbar. 2. Select the text file in the Import Text File dialog. 3. Click Import. 4. Make the changes you want in Text Import Wizard. If you want to import only part of the data in a text file as a refreshable data range, you can create a query to retrieve the data Importing list The import function concerns only the process objects in the objects list. This function enables the user to import a list of process objects that are to be connected to the SQL database. The file should be the same file type as in the export function, in other words a CSV file. To import objects to the objects list from a CSV file (or another comma delimited text file): Click the Import button, or Select Import to file from the File menu, or Use the shortcut CTRL+I. In the import list, the column headers are: LN IX Send to history database Send to measurement database The list contains a process object in the LN column and the index in the IX column. Mark the process objects that will be connected to the SQL database respectively with an X in the corresponding column, see Fig Currently it is possible to add process objects only by using the import function. If an X is removed and the list is imported, the process object is not removed from the objects list. The CSV file can be generated with Excel or Notepad, for example. Save a file as a CSV file. The most convenient way to create a list to be imported to SQL Exporter is to use Excel on an existing process object list. 87

88 SYS MicroSCADA Pro 1MRS To import a list by using Excel: 1. Select File > Save As. 2. Save the file as a CSV file. 3. Answer Yes if you are asked whether you want to keep the workbook in this format, see Fig Fig Save the workbook in CSV format A The file is saved as a text file with semicolons separating the columns and each row ending with a carriage return. Make sure that the columns are separated with commas or semicolons, and not with any other character. You can check this by opening the file with, for example Notepad, see Fig Otherwise SQL Exporter cannot read the text file correctly. If any other character than semicolon or comma is used as a delimiter, replace the character with a semicolon or comma. To replace delimiters in Notepad, select Edit > Replace. Fig Comma delimited process object list in Notepad A Example In Fig , the process object FMU_ALARM is added to the history database and B_HDS is added to the measurement database. 88

89 1MRS MicroSCADA Pro SYS Fig Creating a signal list in Excel for importing A All process objects available in the current application do not necessarily have to be included in the imported list. Including only the objects you wish to add to the SQL system is enough. An error log is created: If the process object list contains a process object that does not exist in your current application. If you try to add a process object that already is connected to an event channel to the history database. The error log is located in the same folder as the file you are trying to import (filename: <imported file>_error.log) Cleaning objects When building a SYS 600 application, process objects are added and removed. Sometimes the objects are left in the SQL_OBJECTS command procedure. The cleaning function removes non-existing process objects from the command procedure (SQL_OBJECTS:C). Select Edit > Clean RDBMS Objects to clean the command procedure. 89

90 90

91 1MRS MicroSCADA Pro SYS Standard functions of SA-LIB 6.1. Preliminary work Before the configuration of the standard functions can start, some preparatory configurations are required (that is, configurations that are required only once). The usage of the object identification (OI) attribute has to be settled, the naming convention of the process object has to be decided and the translation of the signal texts into the local language has to be performed. Some of the symbols in this chapter have different presentations, for example the vertical and horizontal presentation. For more information on the different presentations, refer to the SYS 600 Process Display Design manual Procedures for use with standard functions Procedure U_OTHER_OBJECTS This procedure can be used to define other process objects that are needed by the standard function. This procedure can be used for optimizing performance of control dialog. When these logical names are defined, control dialog does not need to make query to process database to find the objects but it can directly refer to the objects with given logical names. For STATION_LN and BAY_LN, value "NONE" can be used to define that corresponding object does not prohibit operations in control dialog. When STATION_LN or BAY_LN is "", corresponding object state is checked and it is searched from process database by object identification (OI). Default contents of the procedure is = LIST(- STATION_LN = "",- BAY_LN = "",- AR_LN = "",- TRIP_LN = "") #RETURN %U_OTHER_OBJECTS STATION_LN defines logical name of station standard function. Table Attributes for Procedure U_OTHER_OBJECTS Attribute Description STATION_LN TEXT, logical name of station standard function. BAY_LN TEXT, logical name of bay standard function. AR_LN TEXT, logical name of auto-reclosure standard function. TRIP_LN TEXT, logical name of trip tag standard function. 91

92 SYS MicroSCADA Pro 1MRS Procedure U_INTERLOCKING This procedure can be used for defining custom interlocking condition for control dialog. The procedure is executed at control dialog startup. The procedure must return a LIST with following attributes: Table Attributes for Procedure U_INTERLOCKING Attribute Description OPEN_INTERLOCKED BOOLEAN, open interlocking state. If TRUE, Open button is disabled in control dialog CLOSE_INTERLOCKED BOOLEAN, close interlocking state. If TRUE, Close button is disabled in control dialog INTERLOCKING_CAUSE TEXT, reason of the interlocking to be displayed in control dialog info field. See below default contents of the procedure: #RETURN LIST(- OPEN_INTERLOCKED=%OPEN_INTERLOCKED, - CLOSE_INTERLOCKED=%CLOSE_INTERLOCKED, - INTERLOCKING_CAUSE=%INTERLOCKING_CAUSE) The procedure is executed only at dialog startup. If the prerequisities of the interlocking state change while the dialog is open, the changes are not dynamically updated in the dialog Communication support The following protocols are supported in SA-LIB: SPA ANSI LON RP-570 RP-570 with FTABs IEC IEC IEC DNP 3.0 MODBUS RTU PROCOL 92

93 1MRS MicroSCADA Pro SYS Station Standard function installation This chapter describes the installation of station standard function from the SA-LIB. The standard function for the station is found in the directory /SA_LIB/BASE/ BBONE/INST and it should be installed by using the SA-LIB installation procedures (SA_LIB/Process/Station). The standard function can be configured by using the following configuration tools: Object Navigator List-Based Engineering Tool 93

94 SYS MicroSCADA Pro 1MRS Symbol installation The SA symbol for station standard function is installed by using Display Builder functions: 1. Object Browser 2. Palette For more information, refer to the SYS 600 Process Display Design manual. Table SA symbol for station standard function File name Station BI.sd Station.sd Symbol Standard function configuration Configuration with a tool The station standard function has the following attributes to be configured with the Standard Function Tool: Table Configurable attributes Attribute Meaning Default STATION_NAME Name of the substation - P_OBJECT_LN Logical name of database process objects - STATION_TYPE The type of control device & protocol LON CMD_PARAMETER The type of control command for IEC N/A 101 or DNP 3.0 protocol OUTPUT_STATUS Process objects for output status with DNP 3.0 N/A protocol AUTHORIZATION_ The name of the authorization group MV_CONTROL GROUP STATION_LR_IN_USE Station local/remote switch used for control Yes authority checking IND_DOUBLE_BINARY Indication type double binary/single binary Double binary LR_REMOTELY_ CONTROLLABLE Station local/remote switch remotely controllable/ manually operated Yes EVENT_RECORDING Process objects for event recording with RP-570 No process objects OPC_ITEM_PREFIX OPC_LN_INSTANCES Specifies the OPC Item Prefix used as an IEC instance information Specifies the OPC Logical Node names used as IEC instance information IEC61850 Subnetwork.IE D1.LD1" VECTOR("LLN 0") For more detailed description on the configurable attributes, refer to Section Descriptions to the configurable attributes. 94

95 1MRS MicroSCADA Pro SYS Configuration with the Process Object Tool Depending on the configuration of the station standard function, the Process Object Tool creates a certain set of the process objects into the database. Those process objects which are going be linked to the actual process should be edited to have a station number, an address and a proper switching state. Otherwise, by default, all other attributes should have suitable values for normal operation. The Process Object Tool creates process objects based on the following list: Table Process objects created by the Process Object Tool Index Explanation Purpose 10 Station local/remote switch indication 11 Station local/remote switch to Local-command or Station/ Remote command 12 Station local/remote switch to Station-command 13 Station local/remote switch to Remote-command 14 Station local/remote switch to Out of use-command 15 Station blockings (optional) 16 Station selected on monitor (optional) 110 Station local/remote-switch indication Indication for command termination (optional) The station local/remote switch is used to determine whether the control to the station objects is allowed from the panel (local), from the substation control system, from the remote control system or station authority checking is out of use. The station local/remote switch to Local-command object is an output object which is designed to set the station control to local (panel) when the attribute IND_DOUBLE_BINARY is checked. If IND_DOUBLE_BINARY is not checked, output object is used for setting the switch either to Station or Remote. The station local/remote switch to Stationcommand object is an output object, which is designed to set the station control to substation control system (station). The station local/remote switch to Remotecommand object is an output object, which is designed to set the station control to network control system (remote). The station local/remote switch to Out of usecommand object is an output object, which is designed to set the station authority checking out of use. The indication for station blockings is an internal object, which is meant for generating events and printouts of the station blockings. The indication for station selected on monitor is an internal object and it is used to inform other users that the station dialog has been opened by another user(s). Created only for ANSI and RTU type stations. For ANSI it is used for converting the indication from analog value to double binary value. For RTU it is used as an event recording object. Indicates with IEC and -103 whether the issued command was successful or not. 95

96 SYS MicroSCADA Pro 1MRS Example of a station configuration Table Example of a station standard function configuration Attribute STATION_NAME P_OBJECT_LN STATION_TYPE AUTHORIZATION_GROUP STATION_LR_IN_USE IND_DOUBLE_BINARY LR_REMOTELY_CONTROLLABLE EVENT_RECORDING Value Eastwick EST LON MV_CONTROL Yes Yes No N/A Application engineering information Structure of the station standard function This section describes the structure of the station standard function. All sub-drawing files form pictures, help and other text files as well as database objects are included. The station is a part of the standard functions of SA-LIB and has the directory /SA_LIB/BASE/BBONE and the standard SA-LIB subdirectories INST, LANG0 and USE Files Below is the list of all the station standard function related files and their functionality. Table Station standard function related files File Functionality Path Station BI.sd Station.sd SA symbol for station standard function FORM5SAGR1.PIC Generic format picture for printing /PROG/GRAPHICSENGINE/ PALETTE/04-SA_Indication /SA_LIB/BASE/BBONE/USE Language text file The following Text Translation Tool compatible text files are used by the station standard function. The path is /SA_LIB/BASE/BBONE/LANG0. Table File SAI_STA2.TXT Text Translation Tool compatible text files Functionality Text file for the database creation of the standard function Help text file The path to the station help text file is /SA_LIB/BASE/BBONE/LANG0. Table File SAI_STA2.HLP Station help text file Functionality Standard function installation help file 96

97 1MRS MicroSCADA Pro SYS Configuration files The following configuration files are used by the station standard function. The path is /SA_LIB/BASE/BBONE/INST. Table Configuration files used by the station standard function Other text files File Functionality SAI_STA2.DAT Contains the configuration data for station when it is created, modified or deleted by the configuration tools SAI_STA2.POT Contains the process object definitions for the Process Object Tool and the List-Based Engineering Tool SAI_DAU.TXT Contains the list of data acquisition units INDEX5_B1.TXT Selection list of SA-LIB standard functions for the installation tool The following text file is used by the station. The path is /SA_LIB/BASE/BBONE/ USE. Table Another text file used by the station Process objects File Functionality BGU_AUTH.TXT Contains the SCIL code for the station authority check. The code is executed by the dialog for the station. The following process objects are created depending on the configuration of the station. Table Process objects created by manually operated station local/remote switch Index Obj. type Process object Remarks Group identifier 10 DB/BI Station local/remote switch ind. - FPASTAILRS 15 AI Blockings Internal FPASTAXBLK Optional 16 AI Station selected on monitor Internal FPASTAXMEV Optional 110 EVREC Station local/remote switch ind. RP-570 only FPASTAELRS Optional 110 AI Station local/remote switch ind. ANSI only FPASTAELRS Table Process objects created by remotely controllable station local/remote switch Index Obj. type Process object Remarks Group identifier 10 DB/BI Station local/remote switch ind. - FPASTAILRS 11 BO L/R-sw. to Local -command or Station Remote command - FPASTACLRS 12 BO L/R-sw. to Station -command - FPASTACLRS 13 BO L/R-sw. to Remote -command - FPASTACLRS 14 BO L/R-sw. to Out of use -command - FPASTACLRS 15 AI Blockings Internal Optional FPASTAXBLK 97

98 SYS MicroSCADA Pro 1MRS Table Process objects created by remotely controllable station local/remote switch (Continued) Index Obj. type Process object Remarks Group identifier 16 AI Station selected on monitor Internal Optional FPASTAXMEV 110 EVREC Station local/remote switch ind. RP-570 only. FPASTAELRS Optional 110 AI Station local/remote switch ind. ANSI only FPASTAELRS TERM Command termination indication for output signals IEC and only. Optional FPASTATOBC Scale objects At the first installation the station creates the scale 1_1 (linear 1:1 scale). For SPACOM / SRIO (ANSI) type of station, the installation will also create the scale FPU_1_1000 (linear 1:1000 scale) Command procedures At the first installation, the station creates the command procedure BGU_UPDATE, which updates process objects when they are update-deblocked. This feature is similar to the SYS 600 Blocking List function. It is also used by the Update process data dialog. For SPACOM / SRIO (ANSI) type of station, the installation creates the command procedure BGU_AI2DB, which updates the station level local/remote switch indication double binary from an analog input Event channels For SPACOM / SRIO (ANSI) type of station, the installation creates the event channel BGU_AI2DB, which is set to activate the command procedure BGU_AI2DB Bay Standard function installation This section describes the installation of the bay standard function in SA-LIB. The standard function for the bay is found in the directory /SA_LIB/BASE/BBONE/ INST and it should be installed by using the SA-LIB installation procedures (SA_LIB/Process/Bay). This standard function is configured by using configuration tools such as: 1. Object Navigator 2. List-Based Engineering Tool 98

99 1MRS MicroSCADA Pro SYS Symbol installation The SA symbol for the bay standard function is installed by using the Display Builder functions: 1. Object Browser 2. Palette For more information, refer to the SYS 600 Process Display Design manual. Table Bay Switch Indication File name Bay BI.sd Bay.sd Symbol Standard function configuration Configuration with tools The bay standard function has the following attributes to be configured with the Object Navigator or with the List-Based Engineering Tool: Table Configurable attributes Attribute Meaning Default STATION_NAME Name of the substation - BAY_NAME Name of the bay - P_OBJECT_LN Logical name of database process - objects STATION_TYPE The type of control device & protocol LON CMD_PARAMETER Parameter for control method for IEC N/A and DNP 3.0 protocol OUTPUT_STATUS Process objects for output status with N/A DNP 3.0 protocol AUTHORIZATION_GROUP The name of the authorization group MV_CONTROL BAY_LR_IN_USE Physical L/R-switch exists/not Bay L/R-switch exists available BAY_LR_POLARITY Polarity of the bay L/R switch L1 IND_DOUBLE_BINARY Indication type double binary/single binary Double binary LR_REMOTELY_CONTROLL Bay L/R-switch remotely controllable/ Manually operated ABLE manually operated EVENT_RECORDING Process objects for event recording with RP-570 No process objects OPC_ITEM_PREFIX Specifies the OPC Item Prefix used as IEC instance information IEC61850 Subnetwork.IED1.LD1" OPC_LN_INSTANCES Specifies the OPC Logical Node VECTOR("LLN0") names used as IEC instance information For more detailed description on the configurable attributes, refer to Section Descriptions to the configurable attributes. 99

100 SYS MicroSCADA Pro 1MRS Configuration of process objects Depending on the configuration of the bay standard function, the tools create a certain set of process objects in the database. Those process objects which are going to be linked to the actual process should be edited to have a station number, an address and a proper switching state. Otherwise, by default, all other attributes should have suitable values for normal operation. The tools create process objects based on the following list: Table Process objects created for the bay Index Explanation Purpose 10 Bay local/remote switch indication 11 Bay local/remote switch to Disabled -command, or bay local/remote command 12 Bay local/remote switch to Local -command 13 Bay local/remote switch to Remote -command 14 Bay local/remote switch to Reserved -command 15 External interlocking ON/OFF (HW) -indication (optional) 16 External interlocking ON/OFF (SW) -indication (optional) 17 External interlocking ON/OFF -command (optional) The bay (disabled)/local/remote switch is used to determine whether the control to the bay objects is completely inhibited, or it is allowed locally or remotely. The bay local/remote switch to Disabled - command object is an output object which is designed to set the bay control to disabled (no control locally or remotely). If IND_DOUBLE_BINARY is not checked and STATION_TYPE is IEC , this output object is used for setting bay L/R switch either to local or remote. The bay local/remote switch to Local -command object is an output object, which is designed to set the bay control to the local (panel). The bay local/remote switch to Remote - command object is an output object, which is designed to set the bay control to substation or network control system (remote). The bay local/remote switch to Reserved - command object is an output object, which is designed to set the bay control to reserved. The reserved position can be used for special purposes. The external interlocking in use/out of use (HW) - ind. is meant as an ON/OFF type of indication for the hardware switch of the interlocking function. The external interlocking in use/out of use (SW) - ind. is meant as an ON/OFF type of indication for the software switch of the interlocking function. The external interlocking in use/out of use - command is an output object, which can be used to remotely enable/disable interlocking function of the field device. 18 Internal interlocking ON/OFF -indication (optional) The internal interlocking in use/out of use - indication is meant as an ON/OFF type of indication of the internal interlocking functions. By disabling internal interlocking, there will not be any interlocking checking in the control dialogs during operation. 100

101 1MRS MicroSCADA Pro SYS Table Process objects created for the bay (Continued) Index Explanation Purpose 19 Internal interlocking ON/OFF -command (optional) 20 Bay blockings (optional) 21 Bay selected on monitor (optional) 110 Bay local/remote switch indication , 117 Indication for command termination The internal interlocking in use/out of use - command is an object, which is defined to internally control the state of the internal interlocking in use/out of use -indication. The bay blockings -indication is an internal object, which is meant for generating events and printouts of the bay blockings. The bay selected on monitor -indication is an internal object and it is used to inform other users that the bay dialog has been opened by another user(s). Created only for ANSI and RTU type stations. For ANSI it is used for converting the indication from analog value to double binary value. For RTU it is used as an event recording object. Indicates with IEC and -103 whether the issued command was successful or not. (optional) 115 External interlocking ON/OFF (HW) (optional) 116 External interlocking ON/OFF (SW) (optional) Example of a bay configuration Output status object with DNP 3.0 type of stations. Event recording object (for accurate time stamp) with RTU 2xx/RP-570 type of stations. Event recording object (for accurate time stamp) with RTU 2xx/RP-570 type of stations. Table Example configuration of the bay standard function Attribute STATION_NAME BAY_NAME P_OBJECT_LN STATION_TYPE CMD_PARAMETER OUTPUT_STATUS AUTHORIZATION_GROUP BAY_LR_IN_USE BAY_LR_POLARITY IND_DOUBLE_BINARY LR_REMOTELY_CONTROLLABLE EVENT_RECORDING Value Eastwick Outgoing HA2 ESTHA02BAY LON N/A N/A MV_CONTROL Yes L1 Yes No N/A 101

102 SYS MicroSCADA Pro 1MRS Application engineering information Structure of the bay standard function This section describes the structure of the bay standard function. All sub-drawing files, form pictures, help and other text files, as well as database objects are included. The bay is a part of the standard functions of the SA-LIB and has the directory /SA_LIB/BASE/BBONE and the standard SA-LIB subdirectories INST, LANG0 and USE Files Below there is a list of all bay standard function related files and their functionality.. Table Bay standard function related files File Functionality Path Bay BI.sd Bay.sd SA symbol for the bay standard function FORM5SAGR1.PIC Generic format picture for printing /PROG/GRAPHICSENGINE/ PALETTE/04-SA_Indication /SA_LIB/BASE/BBONE/USE Language text file The following Text Translation Tool compatible text files are used by the bay standard function. The path is /SA_LIB/BASE/BBONE/LANG0. Table File SAI_BAY2.TXT Text Translation Tool compatible text files Functionality Text file for the database creation of the standard function Help text file The path to the bay help text file is /SA_LIB/BASE/BBONE/LANG0. Table File SAI_BAY2.HLP Bay help text file Functionality Standard function installation help file Configuration files The following configuration files are used by the bay standard function. The path is /SA_LIB/BASE/BBONE/INST. Table File SAI_BAY2.DAT SAI_BAY2.POT INDEX5_B1.TXT Configuration files used by the bay standard function Functionality Contains the configuration data for the bay when it is created, modified or deleted by the configuration tools Contains the process object definitions for the Object Navigator and the List-Based Engineering Tool Selection list of SA-LIB standard functions for the installation tool 102

103 1MRS MicroSCADA Pro SYS Other text files The following text file is used by the bay. The path is /SA_LIB/BASE/BBONE/ USE. Table File BGU_AUTH.TXT Another text file used by the bay Functionality Contains the SCIL code for the station authority check. The code is executed by the dialog of the bay Command procedures At the first installation, the bay creates the command procedure BGU_UPDATE, which updates process objects when they are update-deblocked. This feature is similar to the SYS 600 Blocking List function. It is also used by the Update process data dialog. Table File BGU_CONTROL Command procedures used by bay Functionality Performs the actual control operations Process objects The following process objects are created depending on the configuration of the bay. Table Process objects created by manually operated bay local/remote switch Index Obj. type Process object Remarks Group identifier 10 DB/BI Bay local/remote switch ind. - FPABAYILRS 15 BI Interl. in use/out of use (SW) Hardware sw. (MFU) FPABAYIINH Optional 16 BI Interl. in use/out of use (HW) Software sw. (MFU) FPABAYIINH Optional 17 BO Interl. in use/out of use -cmd Command to MFU FPABAYCINH Optional 18 BI Interl. in use/out of use Internal FPABAYIINH Optional 19 BO Interl. in use/out of use -cmd Internal FPABAYCINH Optional 20 AI Blockings Internal FPABAYXBLK Optional 21 AI Bay selected on monitor Internal FPABAYXMEV Optional 110 EVREC Bay local/remote switch ind. RP-570 only FPABAYELRS Optional 110 AI Bay local/remote switch ind. ANSI only FPABAYELRS 115 EVREC Interl. in use/out of use (SW) RP-570 only FPABAYEINH Optional 116 EVREC Interl. in use/out of use (HW) RP-570 only FPABAYEINH Optional 117, 119 TERM Command termination indication for output signals IEC and -103 only Optional FPASTATINH 103

104 SYS MicroSCADA Pro 1MRS Table Process objects created by remotely controllable bay local/remote switch Index Obj. type Process object Remarks Group identifier 10 DB/BI Bay local/remote switch ind. - FPABAYILRS 11 BO L/R-sw. to Local -command or Local Remote command Scale objects Event channels Local Remote command if FPABAYCLRS station type is IEC BO L/R-sw. to Local -command - FPABAYCLRS 13 BO L/R-sw. to Remote -command - FPABAYCLRS 14 BO L/R-sw. to Reserved -command Only if ind. type DB FPABAYCLRS 15 BI Interl. in use/out of use (HW) Hardware sw. (MFU) FPABAYIINH Optional 16 BI Interl. in use/out of use (SW) Software sw. (MFU) FPABAYIINH Optional 17 BO Interl. in use/out of use -cmd Command to MFU FPABAYCINH Optional 18 BI Interl. in use/out of use -ind. Internal FPABAYIINH Optional 19 BO Interl. in use/out of use -cmd Internal FPABAYCINH Optional 20 AI Blockings Internal FPABAYXBLK Optional 21 AI Bay selected on monitor Internal FPABAYXMEV Optional 110 EVREC Bay local/remote switch ind. RP-570 only FPABAYELRS Optional 110 AI Bay local/remote switch ind. ANSI only FPABAYELRS TERM/OS Command termination indication for output signals Output status object IEC and -103 only Optional Output status object when station type is DNP 3.0, optional 115 EVREC Interl. in use/out of use (HW) RP-570 only Optional 116 EVREC Interl. in use/out of use (SW)-ind. Only RP-570 only Optional 117, 119 TERM Command termination indication for output signals IEC and -103 only Optional FPASTATOBC FPABAYEINH FPABAYEINH FPASTATINH At the first installation the bay creates the scale 1_1 (linear 1:1 scale). For SPACOM/SRIO (ANSI) type of station. The installation also creates the scale FPU_1_1000 (linear 1:1000 scale). For SPACOM/SRIO (ANSI) type of station, the installation creates the event channel BGU_AI2DB, which is set to activate the command procedure BGU_AI2DB. 104

105 1MRS MicroSCADA Pro SYS Switching device Standard function installation This section describes the installation of the switching device standard function from the SA-LIB. The standard function for the switching device is found in the directory /SA_LIB/BASE/BBONE/INST and it should be installed by using the SA-LIB installation procedures (SA_LIB/Process/Switching Device). This standard function is configured by using configuration tools such as: 1. Object Navigator 2. List-Based Engineering Tool Symbol installation The SA symbol for the switching device standard function is installed by using the following Display Builder functions: 1. Object Browser 2. Palette For more information, refer to the SYS 600 Process Display Design manual. Table SA Symbol for switching device standard function File name Representation Symbol Horizontal Vertical Horizontal Vertical Breaker H.sd Breaker.sd ANSI Disconnector H.sd Disconnector.sd ANSI Truck H.sd Truck.sd Common ANSI, IEC Breaker H.sd Breaker.sd IEC Contactor H.sd Contactor.sd IEC Disconnector H.sd Disconnector.sd IEC 105

106 SYS MicroSCADA Pro 1MRS Table SA Symbol for switching device standard function (Continued) File name Representation Symbol Load Breaker H.sd Load Breaker.sd IEC Earth H.sd Earth.sd Common ANSI, IEC Standard function configuration Configuration with tools The switching device standard function has the following attributes to be configured with the Object Navigator or with the List-Based Engineering Tool:l Table Configurable attributes Attribute Meaning Default STATION_NAME Name of the substation - BAY_NAME Name of the bay - DEVICE_NAME Name of the device - P_OBJECT_LN Logical name of database process - objects SWITCHING_DEVICE_TYPE Type of switching device Circuit breaker SWITCHING_DEVICE_ PURPOSE Usage of the selected switching device Circuit breaker type SWITCH_SECTION Switch section of the truck or 3-state switch Truck: first section 3-state switch: disconnector STATION_TYPE Type of control device & protocol LON INDICATION_TYPE Type of position indication process Double binary object MOTORIZED Selection of motorized or manually Motorized operated CMD_PARAMETER Parameter for control method for IEC N/A and DNP 3.0 protocol CONTROL_TYPE Type of control process object(s) Secured control with 4 binary outputs OUTPUT_STATUS Process objects for output status with N/A DNP 3.0 protocol CONTROL_PULSE_LENGTH Length of control pulse 0 CONTROL_BITS Bits to be used to send a control Empty vector command AUTHORIZATION_GROUP Name of the authorization group MV_CONTROL BAY_LR_POLARITY Polarity of bay L/R switch L1 AUXILIARY_PLUG Selection if the switching device is mounted in the truck Stand-alone switch EVENT_RECORDING Process objects for event recording with RP-570 No process objects 106

107 1MRS MicroSCADA Pro SYS Table Configurable attributes (Continued) Attribute Meaning Default INTERLOCKING_BYPASS Specifies whether the interlocking FALSE bypass function is used or not SYNCHROCHECK_BYPASS Specifies whether the synchrocheck bypass function is used or not FALSE OPC_ITEM_PREFIX Specifies the OPC Item Prefix used as "IEC61850 IEC Instance information Subnetwork.IED1. LD1" OPC_LN_INSTANCES QUALIFIERS ADD_CAUSE_IX For more detailed description on the configurable attributes, refer to Section Descriptions to the configurable attributes Configuration of process objects Specifies the OPC Logical Node names used as IEC Instance information Qualifier is the value written to the QL attribute of process object when writing the control command. Qualifiers are given as a vector of integers. AddCause explains why an operation is not allowed. VECTOR("CSWI1 ","CILO1") Minimum length is 0 (default) and maximum length 5 Depending on the configuration of the switching device standard function, the tools create a certain set of process objects in the database. Those process objects which are going to be linked to the actual process should be edited to have a station number, an address and a proper switching state. Otherwise, by default, all other attributes should have suitable values for normal operation. The tools create process objects based on the following list:. - Table Process objects created for switching device Index Explanation Purpose 10 Position indication Used for position indication of the switching device state open/closed/ intermediate/faulty 11 Open select or open execute 12 Close select or close execute 13 Execute selected or select open/close and execute/cancel or execute open 14 Cancel command or execute close command 15 External control blocking (optional) 16 Open interlocked (optional) Depending on the defined control type it is used for sending Open select or Open execute to the control unit. Depending on the defined control type it is used for sending Close select or Close execute to the control unit. Depending on the defined control type it is used for sending Execute or Select open/close and Execute/ Cancel to the control unit. Used for sending Cancel command or Execute close command to the control unit. Receives a control blocking signal from the control unit and prevents the control actions in the single line diagram. Receives a control blocking signal for Open command from the control unit and prevents the Open command in the single line diagram. 107

108 SYS MicroSCADA Pro 1MRS Table Process objects created for switching device Index Explanation Purpose 17 Close interlocked (optional) 18 Interlocking cause (optional) 19 Selected on monitor (optional) 20 Command event (optional) 21 Auxiliary plug state (optional) Example of a switching device configuration Receives a control blocking signal for Close command from the control unit and prevents the Close command in the single line diagram. Receives an interlocking cause, that is, an integer value that represents a reason for an unsuccessful control action. An internal tag that shows if the switching device is selected on different picture(s) or monitor(s). An internal or external tag that shows if the switching device is right under the command sequence. An internal or external tag to indicate if the switching device is fully racked out from the cubicle and therefore, it should not be shown in the single line diagram. 25 Cancel command Used for sending a Cancel command to the control unit. (108) 110 Position indication other type than double indication Indication for command termination or indication for output status (optional) 115 External control blocking (optional) 116 Open interlocked (optional) 117 Close interlocked (optional) 120 Command event (optional) 121 Auxiliary plug state (optional) (208) 210 Position indication other type than double indication Receives position indication as a single indication (110), analog input (110) or two single indications (110-open, 108-close) Indicates with IEC and -103 whether the issued command was successful or not. With DNP 3.0 indicates the status of output object. Event recording object (for accurate time stamp) with RTU 2xx/RP-570 type of stations. Event recording object (for accurate time stamp) with RTU 2xx/RP-570 type of stations. Event recording object (for accurate time stamp) with RTU 2xx/RP-570 type of stations. Event recording object (for accurate time stamp) with RTU 2xx/RP-570 type of stations. Event recording object (for accurate time stamp) with RTU 2xx/RP-570 type of stations. Event recording object (for accurate time stamp) with RTU 2xx/RP-570 type of stations. The configuration of a switching device as a circuit breaker can be given as an example: Table Configuration of the switching device Attribute Value STATION_NAME Eastwick BAY_NAME Outgoing HA2 DEVICE_NAME Q0 P_OBJECT_LN ESTHA02Q0 SWITCHING_DEVICE_TYPE Circuit breaker SWITCHING_DEVICE_PURPOSE Main busbar circuit breaker SWITCH_SECTION N/A STATION_TYPE LON 108

109 1MRS MicroSCADA Pro SYS Table Configuration of the switching device (Continued) Attribute INDICATION_TYPE MOTORIZED CMD_PARAMETER CONTROL_TYPE OUTPUT_STATUS CONTROL_PULSE_LENGTH CONTROL_BITS AUTHORIZATION_GROUP BAY_LR_POLARITY AUXILIARY_PLUG EVENT_RECORDING Value Double binary Yes N/A Secured control with 4 binary outputs N/A N/A N/A MV_CONTROL L1 No N/A Application engineering information Structure of the switching device standard function This section describes the structure of the switching device standard function. All sub-drawing files, form pictures, help and other text files, as well as database objects are included. The switching device is a part of the standard functions of the SA-LIB and has the directory /SA_LIB/BASE/BBONE and the standard SA-LIB subdirectories INST, LANG0 and USE Files Below there is a list of all switching device standard function related files and their functionality. Table Switching device standard function related files File Functionality Path Breaker.sd SA ANSI symbol for breaker /PROG/GRAPHICSENGINE/PALETTE/03 - SA_ANSI Disconnector.sd SA ANSI symbol for disconnector /PROG/GRAPHICSENGINE/PALETTE/03 - SA_ANSI Truck.sd SA Common symbol for truck /PROG/GRAPHICSENGINE/PALETTE/01 - SA_Common Breaker.sd SA IEC symbol for breaker /PROG/GRAPHICSENGINE/PALETTE/02 - SA_IEC Contactor.sd SA IEC symbol for contactor /PROG/GRAPHICSENGINE/PALETTE/02 - SA_IEC Disconnector.sd SA IEC symbol for disconnector /PROG/GRAPHICSENGINE/PALETTE/02 - SA_IEC Load Breaker.sd SA IEC symbol for load breaker /PROG/GRAPHICSENGINE/PALETTE/02 - SA_IEC Earth.sd SA Common symbol for earth /PROG/GRAPHICSENGINE/PALETTE/01 - SA_Common FORM5SAGR1.PIC Generic format picture for printing /SA_LIB/BASE/BBONE/USE Language text file The following Text Translation Tool compatible text files are used by the switching device standard function. The path is /SA_LIB/BASE/BBONE/LANG0. Table File SAI_SSW.TXT Text Translation Tool compatible text files Functionality Text file for the database creation of the standard function 109

110 SYS MicroSCADA Pro 1MRS Help text file The path to the switching device help text file is /SA_LIB/BASE/BBONE/LANG0. Table File SAI_SSW.HLP Switching device help text file Functionality Standard function installation help file Configuration files Other text files The following configuration files are used by the switching device standard function. The path is /SA_LIB/BASE/BBONE/INST. Table function The following text file is used by the switching device. The path is /SA_LIB/BASE/BBONE/USE Command procedures Configuration files used by the switching device standard File Functionality SAI_SSW.DAT Contains the configuration data for the switching device when it is created, modified or deleted by the configuration tools SAI_SSW.POT Contains the process object definitions for the Object Navigator and the List-Based Engineering Tool INDEX5_B1.TXT Selection list of the SA-LIB standard functions for the installation tool Table Another text file used by the switching device File Functionality BGU_AUTH.TXT Contains the SCIL code for the station authority check. The code is executed by the dialog of the switching device. At the first installation, the bay creates the command procedure BGU_UPDATE, which updates process objects when they are update-deblocked. This feature is similar to the SYS 600 Blocking List function. For the indication type of single indication (BI), the installation will create the command procedure BGU_BI2DB, which updates the position indication double binary from the binary input. For the indication type of an analog input (AI), the installation will create the command procedure BGU_AI2DB, which updates the position indication double binary from the analog input. 110

111 1MRS MicroSCADA Pro SYS Table For the indication type of two single indication (2xBI), the installation creates the command procedures BGU_2BI2DB and BGU_SETDB, which are used to update the position indication double binary from two binary inputs. Command procedures used by the switching device BGU_CONTROL Performs the actual control operations File OBJECT_INFO SELECT_ON_MONITOR OPEN_SELECT UNSELECT_ON_MONITOR CLOSE_SELECT OPEN_EXECUTE CLOSE_EXECUTE CANCEL SEARCH_OBJECTS CHECK_AUTHORITY Functionality Get configuration of the standard function Set standard function to selected on monitor -state Perform open select command on standard function.uses text file /sa_lib/base/bbone/use/ BGU_SW_SEL.TXT Remove selected on monitor -state from standard function Perform close select command on standard function.uses text file /sa_lib/base/bbone/use/ BGU_SW_SEL.TXT Perform open execute command on standard function.uses text file /sa_lib/base/bbone/use/ BGU_SW_EXE.TXT Perform close execute command on standard function.uses text file /sa_lib/base/bbone/ use/bgu_sw_exe.txt Perform cancel command on standard function. Uses text file Search for objects that belong to standard function. Check if the user is authorized to control the station. INTERRUPT_AR_SEQUENCE Interrupt running auto-reclosure sequence. SET_SIMULATION Set simulation state for objects that belong to standard function. GET_SIMULATION Get simulation state of objects that belong to standard function. GET_ALARMS Get alarms of standard function ACKNOWLEDGE_ALARM Acknoledge single alarm of standard function GET_OFFSETS Get index offsets for indexes that are used for selected on monitor indication, command event indication and control block setting. BGU_BLOCK Performs the blocking operations Function GET_BLOCKING_STATE SET_BLOCKING_STATE Description Get blocking state for objects that belong to the standard function. Set blocking state for the objects that belong to the standard function. If standard function is a bay, applies to all objects that belong to the bay. If standard function is a station, applies to all objects that belong to the station Process objects The following process objects are created depending on the configuration of the switching device. Table Manually operated circuit breaker, disconnector or earth switch. The process objects to be created with the tools. Index Obj. type Process object Remarks Group identifier 10 DB Position indication FPQxxxIPOS 19 AI Object selected on Optional FPQxxxXMEV monitor 21 BI Auxiliary plug indication Optional FPQxxxIAUX 108 BI Close position indication Indication type 2xBI FPQxxxEPOS 111

112 SYS MicroSCADA Pro 1MRS Table Manually operated circuit breaker, disconnector or earth switch. The process objects to be created with the tools. (Continued) Index Obj. type Process object Remarks Group identifier 110 BI or AI Position indication or open position indication 110 EVREC DB 121 EVREC BI 208 EVREC BI 210 EVREC BI or AI Event recording for position indication Event recording for auxiliary plug indication Event recording for close position indication Event recording for position indication or open position indication Ind. type AI, BI or 2xBI FPQxxxEPOS Indication type DB RP-570 only Optional RP-570 only Optional Indication type 2xBI RP-570 only Optional Ind. type AI, BI or 2xBI RP-570 only Optional FPQxxxEPOS FPQxxxEAUX FPQxxxEPOS FPQxxxEPOS Three characters (xxx) in the group identifier are replaced by other characters based on the selection made with configurable attributes SWITCHING_DEVICE_TYPE and SWITCHING_DEVICE_PURPOSE. Table Motorized circuit breaker, disconnector or earth switch. The process objects to be created with the tools. Index Obj. type Process object Remarks Group identifier 10 DB Position indication FPQxxxIPOS 11 BO Open command or Open Sec. control with FPQxxxCOBC execute 4xBO, 2xBO or 2xDO 12 BO Close command or Close execute 13 BO Execute command or Open/Close select and Execute/Cancel command or Open execute command 14 BO Cancel command or close execute command Sec. control with 4xBO, 2xBO or 2xDO Sec. control with 4xBO, or 5xBO Sec. control with 4xBO or 5xBO FPQxxxCOBC FPQxxxCOBC FPQxxxCOBC 15 BI/AI External control blocking AI when the selected station type is IEC FPQxxxIBLK 16 BI External interlock for Optional FPQxxxIINH open cmd 17 BI External interlock for Optional FPQxxxIINH close cmd 18 AI External interlocking Optional FPQxxxIINH cause 19 AI Object selected on Optional FPQxxxXMEV monitor 20 BI Object command event Optional FPQxxxICEV 21 BI Auxiliary plug indication Optional FPQxxxIAUX 25 BO Cancel command 5xBO FPQxxxCOBC 108 BI Close position indication Indication type 2xBI FPQxxxEPOS 112

113 1MRS MicroSCADA Pro SYS Table Motorized circuit breaker, disconnector or earth switch. The process objects to be created with the tools. (Continued) Index Obj. type Process object Remarks Group identifier 110 BI or AI Position indication or open position indication 110 EVREC DB Event recording for position indication TERM/OS Command termination indication for output signals 115 EVREC BI Event recording for external control blocking Ind. type AI, BI or 2xBI FPQxxxEPOS Indication type DB RP-570 only Optional IEC and only Optional Only RP-570 Optional FPQxxxEPOS FPQxxxTOBC FPQxxxEBLK 116 EVREC BI 117 EVREC BI 120 EVREC BI 121 EVREC BI 208 EVREC BI 210 EVREC BI or AI Event recording for external interlock for open cmd Event recording for external interlock for close cmd Event recording for object command event Event recording for auxiliary plug indication Event recording for close position indication Event recording for position indication or open position indication 252 AI Calculated interlocking cause Only RP-570 Optional Only RP-570 Optional RP-570 only Optional RP-570 only Optional Indication type 2xBI RP-570 only Optional Ind. type AI, BI or 2xBI RP-570 only Optional Optional FPQxxxEINH FPQxxxEINH FPQxxxECEV FPQxxxEAUX FPQxxxEPOS FPQxxxEPOS FPQxxxIINH Table with the tools. Three characters (xxx) in the group identifier are replaced by other characters based on the selection made with configurable attributes SWITCHING_DEVICE_TYPE and SWITCHING_DEVICE_PURPOSE. Manually operated truck. The process objects to be created Index Obj. type Process object Remarks Group identifier 30 DB Position indication FPQT01IPOS 39 AI Object selected on monitor Optional FPQT01XMEV 128 BI Close position indication Indication type 2xBI FPQT01EPOS 130 BI or AI Position indication or open position indication Ind. type AI, BI or 2xBI FPQT01EPOS 130 EVREC DB Event recording for position indication Indication type DB RP-570 only Optional FPQT01EPOS 113

114 SYS MicroSCADA Pro 1MRS Table Manually operated truck. The process objects to be created with the tools. (Continued) Index Obj. type Process object Remarks Group identifier FPQT01EPOS 228 EVREC BI 230 EVREC BI or AI Table tools. Event recording for close position indication Event recording for position indication or open position indication Indication type 2xBI RP-570 only Optional Ind. type AI, BI or 2xBI RP-570 only Optional FPQT01EPOS Motorized truck. The process objects to be created with the Index Obj. type Process object Remarks Group identifier 30 DB Position indication FPQT01IPOS 31 BO Open command or Open Sec. control with FPQT01COBC execute 4xBO, 2xBO or 2xDO 32 BO Close command or Close execute 33 BO Execute command or Open/Close select and Execute/Cancel command or Open execute command Sec. control with 4xBO, 2xBO or 2xDO Sec. control with 4xBO or 5xBO FPQT01COBC FPQT01COBC 34 BO Cancel command or Sec. control with 4xBO FPQT01COBC Close execute command or 5xBO 35 BI/AI External control blocking AI when the selected station type is IEC FPQT01IBLK 36 BI External interlock for Optional FPQT01IINH open cmd 37 BI External interlock for Optional FPQT01IINH close cmd 38 AI External interlocking Optional FPQT01IINH cause 39 AI Object selected on Optional FPQT01XMEV monitor 40 BI Object command event Optional FPQT01ICEV 45 BO Cancel command 5xBO FPQT01COBC 128 BI Close position indication Indication type 2xBI FPQT01EPOS 130 BI or AI Position indication or open position indication Ind. type AI, BI or 2xBI FPQT01EPOS 130 EVREC DB Event recording for position indication TERM Command termination indication for output signals 135 EVREC BI 136 EVREC BI Event recording for external control blocking Event recording for external interlock for open cmd Indication type DB RP-570 only Optional IEC and -103 only Optional Only RP-570 Optional Only RP-570 Optional FPQT01EPOS FPQxxxTOBC FPQT01EBLK FPQT01EINH 114

115 1MRS MicroSCADA Pro SYS Table Motorized truck. The process objects to be created with the tools. (Continued) Index Obj. type Process object Remarks Group identifier FPQT01EINH 137 EVREC BI 140 EVREC BI 228 EVREC BI 230 EVREC BI or AI Event recording for external interlock for close cmd Event recording for object command event Event recording for close position indication Event recording for position indication or open position indication 251 AI Calculated interlocking cause Only RP-570 Optional RP-570 only Optional Indication type 2xBI RP-570 only Optional Ind. type AI, BI or 2xBI RP-570 only Optional Optional FPQT01ECEV FPQT01EPOS FPQT01EPOS FPQT01IINH Table Manually operated three-state switch. The process objects to be created with the tools. Index Obj. type Process object Remarks Group identifier 10 DB Position indication Disconnector section FPQ301IPOS 11 DB Position indication Earth switch section FPQ301IPOS 25 AI Object selected on monitor Optional FPQ301XMEV 108 BI Close position indication Indication type 2xBI FPQ301EPOS Disconnector section 109 BI Earth position indication Indication type 2xBI Earth switch section FPQ301EPOS 110 BI or AI Position indication or open position indication Ind. type AI, BI or 2xBI FPQ301EPOS Disconnector section 111 BI or AI Position indication or free position indication 110 EVREC DB 111 EVREC DB 208 EVREC BI 209 EVREC BI 210 EVREC BI or AI 211 EVREC BI or AI Event recording for position indication Event recording for position indication Event recording for close position indication Event recording for earth position indication Event recording for position indication or open position indication Event recording for position indication or free position indication Ind. type AI, BI or 2xBI Earth switch section Indication type DB RP-570 only Optional Indication type DB RP-570 only Optional Indication type 2xBI RP-570 only Optional Indication type 2xBI RP-570 only Optional Ind. type AI, BI or 2xBI RP-570 only Optional Ind. type AI, BI or 2xBI RP-570 only Optional FPQ301EPOS FPQ301EPOS FPQ301EPOS FPQ301EPOS FPQ301EPOS FPQ301EPOS FPQ301EPOS 115

116 SYS MicroSCADA Pro 1MRS Table Motorized three-state switch. The process objects to be created with the tools. Index Obj. type Process object Remarks Group identifier 10 DB Position indication Disconnector section FPQ301IPOS 11 DB Position indication Earth switch section FPQ301IPOS 12 BO Open command or Open execute Sec. control with 4xBO, 2xBO or 2xDO FPQ301COBC 13 BO Close command or Close execute 14 BO Free command or Free execute 15 BO Earth command or Earth execute 16 BO Execute command or open/close select and execute/ cancel cmd 17 BO Cancel command or free/earth select and execute/cancel cmd Sec. control with 4xBO, 2xBO or 2xDO Sec. control with 4xBO, 2xBO or 2xDO Sec. control with 4xBO, 2xBO or 2xDO Sec. control with 4xBO, BO or AO Direct control with BO Sec. control with 4xBO, BO or AO Direct control with BO FPQ301COBC FPQ301COBC FPQ301COBC FPQ301COBC FPQ301COBC 18 BI External control blocking Optional FPQ301IBLK 19 BI External interlock for Optional FPQ301IINH open cmd 20 BI External interlock for Optional FPQ301IINH close cmd 21 BI External interlock for Optional FPQ301IINH free cmd 22 BI External interlock for Optional FPQ301IINH earth cmd 23 AI External inter-locking Optional FPQ301IINH cause 24 AI External interlocking Optional FPQ301IINH cause 25 AI Object selected on Optional FPQ301XMEV monitor 26 BI Object command event Optional FPQ301ICEV 108 BI Close position indication Indication type 2xBI FPQ301EPOS 109 BI Earth position indication Indication type 2xBI FPQ301EPOS 110 BI or AI Position indication or Ind. type AI, BI or 2xBI FPQ301EPOS open position indication 111 BI or AI Position indication or free position indication Ind. type AI, BI or 2xBI FPQ301EPOS 110 EVREC DB Event recording for position indication Indication type DB RP-570 only Optional FPQ301EPOS 111 EVREC DB Event recording for position indication TERM Command termination indication for output signals 118 EVREC BI Indication type DB RP-570 only Optional IEC and -103 only Optional Event recording for RP-570 only external control blocking Optional FPQ301EPOS FPQxxxTOBC FPQ301EBLK 116

117 1MRS MicroSCADA Pro SYS EVREC BI Scale objects Operation counters Table Motorized three-state switch. The process objects to be created with the tools. (Continued) Index Obj. type Process object Remarks Group identifier FPQ301EINH 120 EVREC BI 121 EVREC BI 122 EVREC BI 126 EVREC BI 208 EVREC BI 209 EVREC BI 210 EVREC BI or AI 211 EVREC BI or AI Event recording for external interlock for open cmd Event recording for external interlock for close cmd Event recording for external interlock for free cmd Event recording for external interlock for earth cmd Event recording for object command event Event recording for close position indication Event recording for earth position indication Event recording for position indication or open position indication Event recording for position indication or free position indication 251 AI Calculated interlocking cause 252 AI Calculated interlocking cause RP-570 only Optional RP-570 only Optional RP-570 only Optional RP-570 only Optional RP-570 only Optional Indication type 2xBI RP-570 only Optional Indication type 2xBI RP-570 only Optional Ind. type AI, BI or 2xBI RP-570 only Optional Ind. type AI, BI or 2xBI RP-570 only Optional Optional Optional FPQ301EINH FPQ301EINH FPQ301EINH FPQ301ECEV FPQ301EPOS FPQ301EPOS FPQ301EPOS FPQ301EPOS FPQ301IINH FPQ301IINH At the first installation the switching device creates the scale 1_1 (linear 1:1 scale). For indication type of analog input, the installation will also create the scale BGU_1_1000 (linear 1:1000 scale). In a switch control dialog, the CO, CV, CE and CL attributes of the DB process object are used for operation counting. Regardless of whether the counting is used or not, the attributes are always readable. 117

118 SYS MicroSCADA Pro 1MRS Tap changer Standard function installation This chapter describes the installation of the tap changer standard function from the SA-LIB. The standard function for the tap changer is found in the directory /SA_LIB/BASE/BBONE/INST and it should be installed by using the SA-LIB installation procedures (SA_LIB/Process/Tap Changer). This standard function is configured by using configuration tools such as: 1. Object Navigator 2. List-Based Engineering Tool Symbol installation The SA symbol for the tap changer standard function is installed by using the following Display Builder functions: 1. Object Browser 2. Palette For further information, refer to the SYS 600 Process Display Design manual. Table SA symbol for tap changer standard function File name Representation Symbol Horizontal Vertical Horizontal Vertical Transformer2w.sd Transformer2w.sd ANSI Transformer2w H.sd Transformer2w.sd IEC Transformer3w.sd Transformer3w.sd ANSI Transformer3w H.sd Transformer3w.sd IEC 118

119 1MRS MicroSCADA Pro SYS Standard function configuration Configuration with tools The tap changer standard function has the following attributes to be configured with the Object Navigator or with the List-Based Engineering Tool: Table Tap changer attributes configured with the tools Attribute Meaning Default STATION_NAME Name of the substation - BAY_NAME Name of the bay - DEVICE_NAME Name of the device - MIN_POSITION Minimum position of tap changer 1 MAX_POSITION Minimum position of tap changer 19 P_OBJECT_LN Logical name of database process object - STATION_TYPE The type of control device & protocol ANSI CMD_PARAMETER A selector for selecting of control method. N/A This attribute has meaning only if IEC or DNP 3.0 protocol is selected, otherwise this attribute is disabled. OUTPUT_STATUS Process objects for output status with N/A DNP 3.0 protocol. AUTO_MANUAL_IND_TYP E The type of the auto/manual signal 01=manual, 10=auto (DB) AUTHORIZATION_GROUP The name of the authorization group MV_CONTROL TRANSFORMER_TYPE The number of windings 2-winding OPC_ITEM_PREFIX OPC_LN_INSTANCES Specifies the OPC Item Prefix to as IEC instance information Specifies the OPC Logical Node names used as IEC Instance information "IEC61850 Subnetwork.IED1. LD1" VECTOR ("ATCC1") For more detailed description on the configurable attributes, refer to Section Descriptions to the configurable attributes Configuration of process objects Depending on the configuration of the tap changer standard function, the tools create a certain set of process objects into the database. Those process objects which are going be linked to the actual process should be edited to have a station number, an address and a proper switching state. Otherwise, by default, all other attributes should have suitable values for normal operation. When process objects are created, default scales are assigned to the analog input signals meant to be connected to the process (indices 24,25 and 26). Table Process objects created for tap changer Index Explanation Purposes 10 Tap position indication Used for indication of the tap changer position. 11 Tap ch. auto/manual ind. Used for indication of the transformer auto manual state. 119

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

121 1MRS MicroSCADA Pro SYS Example of a tap changer configuration Table Example configuration of a tap changer Attributes Value STATION_NAME Eastwick BAY_NAME Transformer 1 DEVICE_NAME TR1 MIN_POSIT 1 MAX_POSIT 19 P_OBJECT_LN ESTH03_T1 STATION_TYPE SPA AUTHORIZATION_GROUP MV_CONTROL TRANSFORMER_TYPE 2-winding Application engineering information Structure of the tap changer standard function This section describes the structure of the tap changer standard function. All subdrawing files, form pictures, help and other text files, as well as database objects are included. The tap changer is a part of the standard functions of SA-LIB and has the directory /SA_LIB/BASE/BBONE and the standard SA-LIB subdirectories INST, LANG0 and USE Files Below there is a list of all tap changer standard function related files and their functionality. Table Tap changer standard function related files File Functionality Path Transformer2w.sd SA ANSI symbol for two winding /PROG/GRAPHICSENGINE/ transformer PALETTE/03 - SA_ANSI Transformer3w.sd SA ANSI symbol for three winding transformer Transformer2w.sd SA IEC symbol for two winding transformer Transformer3w.sd SA IEC symbol for three winding transformer FORM5SAGR1.PIC Generic format picture for printing /PROG/GRAPHICSENGINE/ PALETTE/03 - SA_ANSI /PROG/GRAPHICSENGINE/ PALETTE/03 - SA_IEC /PROG/GRAPHICSENGINE/ PALETTE/02 - SA_IEC /SA_LIB/BASE/BBONE/USE Language text files The following Text Translation Tool compatible text files are used by the tap changer standard function. The path is /SA_LIB/BASE/BBONE/LANG0. Table Text Translation Tool compatible text files used by the tap changer standard function File SAI_TR2R.TXT SAI_TR2S.TXT Functionality Text file for the database creation of the standard function Text file for the database creation of the standard function 121

122 SYS MicroSCADA Pro 1MRS SAI_HVT2.TXT SAI_HVT3.TXT Help text file Table Text Translation Tool compatible text files used by the tap changer standard function (Continued) File Functionality Text file for the database creation of the standard function network topology coloring Text file for the database creation of the standard function network topology coloring The path to the tap changer help text file is /SA_LIB/BASE/BBONE/LANG0. Table File SAI_TR2.HLP Tap changer help text file Functionality Standard function installation help file Configuration files The following configuration files are used by the tap changer standard function. The path is /SA_LIB/BASE/BBONE/INST. Table function File SAI_TRI_2.DAT SAI_TRI_2.POT SAI_HVT23.POT SAI_TRAIDX.TXT SAI_HVT2.TPL SAI_HVT3.TPL INDEX5_B1.TXT Configuration files used by the tap changer standard Functionality Contains the configuration data for tap changer when it is created modified or deleted by configuration tools Contains the process object definitions for the Object Navigator and List-Based Engineering Tool Contains the process object network topology coloring definitions for the Object Navigator and List-Based Engineering Tool Contains the process object network topology coloring definitions for the Object Navigator and List-Based Engineering Tool Contains the process object network topology coloring template definitions for the Object Navigator and List-Based Engineering Tool Contains the process object network topology coloring template definitions for the Object Navigator and List-Based Engineering Tool Selection list of SA-LIB standard functions for installation tool Other text file The following text file is used by the tap changer. The path is /SA_LIB/BASE/ BBONE/USE. Table File BGU_AUTH.TXT Text file used by the tap changer Functionality Contains the SCIL code for station authority check. The code is executed by the dialog of the tap changer. 122

123 1MRS MicroSCADA Pro SYS Command procedures At the first installation, the tap changer creates the command procedure BGU_UPDATE, which updates process objects when they are update-deblocked. This feature is similar to the SYS 600 Blocking List function. For ANSI type of station, the command procedure BGU_AI2DB will be created while installing. The command procedure BGU_AI2DB updates the position indication double binary from the analog input. The command procecure BGU_TCCO is created for updating the operation counter object. Table Command procedures used by the tap changer BGU_TRAFO Performs the control operations Function AUTOMATIC_SELECT AUTOMATIC_EXECUTE AUTOMATIC_CANCEL LOWER_SELECT LOWER_EXECUTE LOWER_CANCEL MANUAL_SELECT MANUAL_EXECUTE MANUAL_CANCEL PARALLEL_SELECT PARALLEL_EXECUTE PARALLEL_CANCEL RAISE_SELECT RAISE_EXECUTE RAISE_CANCEL SINGLE_SELECT SINGLE_EXECUTE SINGLE_CANCEL SELECT_ON_MONITOR UNSELECT_ON_MONITOR Description Performs select operation for automatic command on transformer standard function. Uses text file /SA_LIB/BASE/BBONE/USE/BGU_SW_SEL.TXT Performs execute operation for automatic command on transformer standard function. Uses text file /SA_LIB/BASE/BBONE/USE/BGU_SW_EXE.TXT Performs cancel operation for automatic command on transformer standard function. Uses text file /SA_LIB/BASE/BBONE/USE/BGU_SW_CAN.TXT Performs select operation for lower command on transformer standard function. Uses text file /SA_LIB/BASE/BBONE/USE/BGU_SW_SEL.TXT Performs execute operation for lower command on transformer standard function. Uses text file /SA_LIB/BASE/BBONE/USE/BGU_SW_EXE.TXT Performs cancel operation for lower command on transformer standard function. Uses text file /SA_LIB/BASE/BBONE/USE/BGU_SW_CAN.TXT Performs select operation for manual command on transformer standard function. Uses text file /SA_LIB/BASE/BBONE/USE/BGU_SW_SEL.TXT Performs execute operation for manual command on transformer standard function. Uses text file /SA_LIB/BASE/BBONE/USE/BGU_SW_EXE.TXT Performs cancel operation for manual command on transformer standard function. Uses text file /SA_LIB/BASE/BBONE/USE/BGU_SW_CAN.TXT Performs select operation for parallel command on transformer standard function. Uses text file /SA_LIB/BASE/BBONE/USE/BGU_SW_SEL.TXT Performs execute operation for parallel command on transformer standard function. Uses text file /SA_LIB/BASE/BBONE/USE/BGU_SW_EXE.TXT Performs cancel operation for parallel command on transformer standard function. Uses text file /SA_LIB/BASE/BBONE/USE/BGU_SW_CAN.TXT Performs select operation for raise command on transformer standard function. Uses text file /SA_LIB/BASE/BBONE/USE/BGU_SW_SEL.TXT Performs execute operation for raise command on transformer standard function. Uses text file /SA_LIB/BASE/BBONE/USE/BGU_SW_EXE.TXT Performs cancel operation for raise command on transformer standard function. Uses text file /SA_LIB/BASE/BBONE/USE/BGU_SW_CAN.TXT Performs select operation for single command on transformer standard function. Uses text file /SA_LIB/BASE/BBONE/USE/BGU_SW_SEL.TXT Performs execute operation for single command on transformer standard function. Uses text file /SA_LIB/BASE/BBONE/USE/BGU_SW_EXE.TXT Performs cancel operation for single command on transformer standard function. Uses text file /SA_LIB/BASE/BBONE/USE/BGU_SW_CAN.TXT Set transformer standard function to selected on monitor -state Remove selected on monitor -state from transformer standard function 123

124 SYS MicroSCADA Pro 1MRS Table Command procedures used by the tap changer (Continued) BGU_TRAFO Performs the control operations Function Description OBJECT_CONF Get object configuration for transformer standard function GET_STATES Get process object states of transformer standard function GET_MESSAGES Get object messages of transformer standard function BGU_BLOCK Performs the blocking operations Function GET_BLOCKING_STATE SET_BLOCKING_STATE Description Get blocking state for objects that belong to standard function. Set blocking state for objects that belong to standard function. If standard function is bay, applies to all objects that belong to bay. If standard function is station, applies all objects that belong to station Process objects The following process objects will be created depending on the configuration of the tap changer. Table Process objects for Generic tap changer Index Object type Meaning of Process object Remarks Group identifier 10 AI Tap changer position - FPTAVRIPOS 11 BI/DB Tap changer manual/ - FPTAVRIMAN auto -ind. 12 BI/DB Tap changer single/ DB with IEC FPTAVRISGL parallel -ind. 13 BI/AO Tap changer master/ slave -ind. or AO with IEC FPTAVRIMST or FPTAVRCPOS Raise/Lower cmd 14 BO Tap changer Manual cmd or Auto/Manual cmd - FPTAVRCMAN 15 BO Tap changer Auto cmd or Parallel select cmd 16 BO Tap changer Raise cmd or tap changer Raise/ Lower cmd or Single select cmd 17 BO Tap changer Lower cmd or Parallel execute cmd - FPTAVRCMAN or FPTAVRCSGL - FPTAVRCPOS or FPTAVRCSGL - FPTAVRCPOS or FPTAVRCSGL 18 BO Single execute cmd Only IEC FPTAVRCSGL 19 BO Single/Parallel cancel Only IEC FPTAVRCSGL cmd 20 BI/AI Tap changer external AI with IEC FPTAVRIBLK blocking 24 AI Voltage - FPTAVRMVOL 29 AI Tap changer operation - FPTAVRICNR counter 30 AI Tap changer selected on monitor - FPTAVRXMEV 124

125 1MRS MicroSCADA Pro SYS Table Process objects for network topology coloring purposes Scale objects Operation counters Index Object type Meaning of process object Remarks 240 BI Transformer switch1-241 BI Transformer switch2-242 BI Transformer switch3-243 BI Transformer switch4 3-winding 244 BI Transformer switch5 3-winding 246 AI Transformer passive node1-247 AI Transformer passive node2-248 AI Transformer passive node3 3-winding 250 AI Transformer active color1-251 AI Transformer active color2-252 AI Transformer active color3 3-winding 253 BI Transformer switch6-254 BI Transformer switch7-255 BI Transformer switch8 3-winding At the first installation, the tap changer creates the scale 1_1 (linear 1:1 scale). For ANSI type of station, the installation creates also the scale BGU_1_1000 (linear 1:1000 scale). In the tab changer dialog, the AZ, OV, IU and HI attributes of the dedicated analog input point are used for operation counting. The AZ, OV and HI attributes are not readable if the IU attribute value is Measurement Standard function installation This chapter describes the installation of measurement standard function from the SA-LIB. The standard function for the measurement is found in the directory /SA_LIB/BASE/BBONE/INST and it should be installed by using the SA-LIB installation procedures (SA_LIB/Process/Measurement). This standard function is configured by using the configuration tools such as: 1. Object Navigator 2. List-Based Engineering Tool Symbol installation The SA symbol for the measurement standard function is installed by using the Display Builder functions: 1. Object Browser 2. Palette For further information, refer to the SYS 600 Process Display Design manual. 125

126 SYS MicroSCADA Pro 1MRS Table SA symbols for measurement standard function File name Representation Symbol Horizontal Vertical Horizontal Vertical Bar Graph.sd Line Graph 20 Sample.sd Value.sd Circle.sd Current Transducer ANSI H.sd Current Transducer ANSI.sd ANSI Current Transducer IEC H.sd Current Transducer IEC.sd IEC Voltage Transducer ANSI H.sd Voltage Transducer ANSI.sd ANSI Voltage Transducer IEC H.sd Voltage Transducer IEC.sd IEC Standard function configuration Configuration with tools The measurement standard function has the following attributes to be configured with the Object Navigator or the List-Based Engineering Tool: Table Configurable measurement picture function attributes Attribute Meaning Default STATION_NAME Name of the substation - BAY_NAME Name of the bay - DEVICE_NAME Name of the device - P_OBJECT_LN Logical name of database process objects - STATION_TYPE The type of control device & protocol LON TYPE_MEAS_ number The type of the measurement None FOLDER_ number_titl E Abbreviation of the measurement - 126

127 1MRS MicroSCADA Pro SYS Table Configurable measurement picture function attributes Attribute Meaning Default Decimals used for presenting the value 0 MEAS_ number_decim ALS AUTHORIZATION_GRO UP EVENT_RECORDING OPC_ITEM_PREFIX OPC_LN_INSTANCE_1 OPC_LN_INSTANCE_2 OPC_LN_INSTANCE_3 OPC_LN_INSTANCE_4 The name of the authorization group Process objects for event recording with RP-570 For more detailed description on the configurable attributes, refer to Section Descriptions to the configurable attributes Configuration of process objects Specifies the OPC Item Prefix used as IEC Instance information Specifies the OPC Logical Node names used as IEC Instance information for the measurement type 1 Specifies the OPC Logical Node names used as IEC Instance information for the measurement type 2 Specifies the OPC Logical Node names used as IEC Instance information for the measurement type 3 Specifies the OPC Logical Node names used as IEC Instance information for the measurement type 4 MV_CONTROL No process objects "IEC61850 Subnetwork.IED1.LD1" VECTOR("MMXU1") VECTOR("MMXU1") VECTOR("MMXU1") VECTOR("MMXU1") Depending on the measurement standard function configuration, the tools create a certain set of process objects in the database. Those process objects which are going to be linked to the actual process should be edited to have a station number, an address and a proper switching state. Otherwise, by default, all other attributes should have suitable values for normal operation. Table Process objects created for measurement Index Explanation Purpose 10 Current L1 Current measurement on phase L1 11 Current L2 Current measurement on phase L2 12 Current L3 Current measurement on phase L3 13 Neutral current I0 Neutral current measurement 14 Directional neutral current Ij Directional neutral current measurement 15 Maximum demand I15min Current measurement of 15 minutes maximum demand 16 Voltage U12 Phase to phase voltage measurement on phases L1-L2 17 Voltage U23 Phase to phase voltage measurement on phases L2-L3 18 Voltage U31 Phase to phase voltage measurement on phases L3-L1 19 Residual voltage U0 Residual voltage measurement 20 Active power P Active power measurement 127

128 SYS MicroSCADA Pro 1MRS Table Process objects created for measurement (Continued) Index Explanation 21 Reactive power Q Reactive power measurement 22 Apparent power S Apparent power measurement 23 Power factor Cosj Power factor measurement 24 Frequency f Frequency measurement 25 Harmonic distortion Harmonic distortion measurement 26 Temperature Temperature measurement User-defined measurement Any analog input (AI) type of user-defined measurement User-defined pulse counter Any pulse counter (PC) type of user-defined measurement 38 Active energy (kwh) Active energy counter for kwh 39 Active energy (MWh) Active energy counter for MWh 40 Active energy (GWh) Active energy counter for GWh 41 Reversed active energy (kwh) Reversed active energy counter for kwh 42 Reversed active energy (MWh) Reversed active energy counter for MWh 43 Reversed active energy (GWh) Reversed active energy counter for GWh 44 Reactive energy (kvarh) Reactive energy counter for kvarh 45 Reactive energy (Mvarh) Reactive energy counter for Mvarh 46 Reactive energy (Gvarh) Reactive energy counter for Gvarh 47 Reversed reactive energy (kvarh) Reversed reactive energy counter for kvarh 48 Reversed reactive energy (Mvarh) Reversed reactive energy counter for Mvarh 49 Reversed reactive energy (Gvarh) Reversed reactive energy counter for Gvarh 110 Current L1 (optional) 111 Current L2 (optional) 112 Current L3 (optional) 113 Neutral current I0 (optional) 114 Directional neutral current Ij (optional) 115 Maximum demand I15min (optional) 116 Voltage U12 (optional) 117 Voltage U23 (optional) 118 Voltage U31 (optional) 119 Residual voltage U0 (optional) 120 Active power P (optional) 121 Reactive power Q (optional) 122 Apparent power S (optional) Purpose Event recording object (for accurate time stamp) with RTU 2xx/RP-570 type of stations. Event recording object (for accurate time stamp) with RTU 2xx/RP-570 type of stations. Event recording object (for accurate time stamp) with RTU 2xx/RP-570 type of stations. Event recording object (for accurate time stamp) with RTU 2xx/RP-570 type of stations. Event recording object (for accurate time stamp) with RTU 2xx/RP-570 type of stations. Event recording object (for accurate time stamp) with RTU 2xx/RP-570 type of stations. Event recording object (for accurate time stamp) with RTU 2xx/RP-570 type of stations. Event recording object (for accurate time stamp) with RTU 2xx/RP-570 type of stations. Event recording object (for accurate time stamp) with RTU 2xx/RP-570 type of stations. Event recording object (for accurate time stamp) with RTU 2xx/RP-570 type of stations. Event recording object (for accurate time stamp) with RTU 2xx/RP-570 type of stations. Event recording object (for accurate time stamp) with RTU 2xx/RP-570 type of stations. Event recording object (for accurate time stamp) with RTU 2xx/RP-570 type of stations. 128

129 1MRS MicroSCADA Pro SYS Table Process objects created for measurement (Continued) Index Explanation 123 Power factor Cosj (optional) 124 Frequency f (optional) 125 Harmonic distortion (optional) 126 Temperature (optional) User-defined measurement (optional) Purpose Event recording object (for accurate time stamp) with RTU 2xx/RP-570 type of stations. Event recording object (for accurate time stamp) with RTU 2xx/RP-570 type of stations. Event recording object (for accurate time stamp) with RTU 2xx/RP-570 type of stations. Event recording object (for accurate time stamp) with RTU 2xx/RP-570 type of stations. Event recording object (for accurate time stamp) with RTU 2xx/RP-570 type of stations Example of measurement configuration The configuration of the measurement with a horizontal field can be given as an example: Table Measurement configuration Attribute Value STATION_NAME Eastwick BAY_NAME Outgoing HA2 DEVICE_NAME CT P_OBJECT_LN ESTHA02CT STATION_TYPE LON TYPE_MEAS_1 Current L1 FOLDER_1_TITLE IL1 MEAS_1_DECIMALS 0 TYPE_MEAS_2 Active power P FOLDER_2_TITLE P MEAS_2_DECIMALS 1 TYPE_MEAS_3 Reactive power Q FOLDER_3_TITLE Q MEAS_3_DECIMALS 1 TYPE_MEAS_4 None FOLDER_4_TITLE N/A MEAS_4_DECIMALS N/A AUTHORIZATION_GROUP MV_CONTROL EVENT_RECORDING N/A Application engineering information Structure of the measurement standard function This section describes the structure of the measurement standard function. All subdrawing files, form pictures, help and other text files, as well as database objects are included. The measurement is a part of the standard functions of SA-LIB and has a directory /SA_LIB/BASE/BBONE, and the standard SA-LIB subdirectories INST, LANG0 and USE. 129

130 SYS MicroSCADA Pro 1MRS Files Below there is a list of all measurement standard function related files and their functionality. Table Measurement standard function files File Functionality Path Bar Graph.sd Line Graph.sd Value.sd Circle.sd Current Transducer ANSI.sd Current Transducer IEC.sd Voltage Transducer ANSI.sd Voltage Transducer IEC.sd FORM5SAGR1.PIC Measurement bar graph symbol Measurement line graph symbol Measurement value symbol Measurement circle symbol SA ANSI symbol for current transducer SA IEC symbol for current transducer SA ANSI symbol for voltage transducer SA IEC symbol for voltage transducer Generic format picture for printing /PROG/GRAPHICSENGINE/PALETTE/05 - SA_Measurement /PROG/GRAPHICSENGINE/PALETTE/05 - SA_Measurement /PROG/GRAPHICSENGINE/PALETTE/05 - SA_Measurement /PROG/GRAPHICSENGINE/PALETTE/05 - SA_Measurement /PROG/GRAPHICSENGINE/PALETTE/05 - SA_Measurement /PROG/GRAPHICSENGINE/PALETTE/05 - SA_Measurement /PROG/GRAPHICSENGINE/PALETTE/05 - SA_Measurement /PROG/GRAPHICSENGINE/PALETTE/05 - SA_Measurement /SA_LIB/BASE/BBONE/USE Language text file The following Text Translation Tool compatible text file is used by the measurement standard function. The path is /SA_LIB/BASE/BBONE/LANG0. Table File SAI_ME.TXT Language text file Functionality Text file for the database creation of the standard function Help text file The path to the measurement help text file is /SA_LIB/BASE/BBONE/LANG0. Table File SAI_ME1.HLP Help text file Functionality Standard function installation help file 130

131 1MRS MicroSCADA Pro SYS Configuration files The following configuration files are used by the measurement standard function. The path is /SA_LIB/BASE/BBONE/INST. Table function File SAI_ME1.DAT SAI_ME1.POT INDEX5_B1.TXT Configuration files used by the measurement standard Functionality Contains the configuration data for measurement when it is created modified or deleted by configuration tools Contains the process object definitions for the Object Navigator and List-Based Engineering Tool Selection list of SA-LIB standard functions for installation tool Other text files The following text file is used by the measurement. The path is /SA_LIB/BASE/ BBONE/USE. Table File BGU_AUTH.TXT Text file used by the measurement Functionality Contains the SCIL code for station authority check. The code is executed by the dialog of the measurement Command procedures At the first installation the measurement creates the command procedure BGU_UPDATE, which updates process objects when they are update-deblocked. This feature is similar to the SYS 600 Blocking List function. Table Command procedures used by measurement BGU_CONTROL Performs the control operations Function OBJECT_INFO SELECT_ON_MONITOR OPEN_SELECT UNSELECT_ON_MONITOR CLOSE_SELECT OPEN_EXECUTE CLOSE_EXECUTE CANCEL SEARCH_OBJECTS Description Get configuration of the standard function Set standard function to selected on monitor -state Perform open select command on standard function. Uses text file /sa_lib/base/bbone/use/bgu_sw_sel.txt Remove selected on monitor -state from standard function Perform close select command on standard function. Uses text file /sa_lib/base/bbone/use/bgu_sw_sel.txt Perform open execute command on standard function. Uses text file /sa_lib/base/bbone/use/bgu_sw_exe.txt Perform close execute command on standard function. Uses text file /sa_lib/base/bbone/use/bgu_sw_exe.txt Perform cancel command on standard function. Uses text file /sa_lib/base/bbone/use/bgu_sw_can.txt Search for objects that belong to standard function. 131

132 SYS MicroSCADA Pro 1MRS Table Command procedures used by measurement (Continued) BGU_CONTROL Performs the control operations Function CHECK_AUTHORITY INTERRUPT_AR_ SEQUENCE SET_SIMULATION GET_SIMULATION GET_ALARMS ACKNOWLEDGE_ALARM GET_OFFSETS Description Check if the user is authorized to control the station. Interrupt running auto-reclosure sequence. Set simulation state for objects that belong to standard function. Get simulation state of objects that belong to standard function. Get alarms of standard function Acknoledge single alarm of standard function Get index offsets for indexes that are used for selected on monitor indication, command event indication and control block setting Process objects The following process objects are created depending on the configuration of the measurement. Table Measurement process objects Index Obj. type Process object Remarks Group identifier 10 AI Current L1 - FPPMEAMCUR 11 AI Current L2 - FPPMEAMCUR 12 AI Current L3 - FPPMEAMCUR 13 AI Neutral current I0 - FPPMEAMNCU 14 AI Directional neutral current Ij - FPPMEAMDNC 15 AI Maximum demand I15min - FPPMEAMMDC 16 AI Voltage U12 - FPPMEAMVOL 17 AI Voltage U23 - FPPMEAMVOL 18 AI Voltage U31 - FPPMEAMVOL 19 AI Residual voltage U0 - FPPMEAMRVL 20 AI Active power P - FPPMEAMAPW 21 AI Reactive power Q - FPPMEAMRPW 22 AI Apparent power S - FPPMEAMAPP 23 AI Power factor Cosj - FPPMEAMCOS 24 AI Frequency f - FPPMEAMFRQ 25 AI Harmonic distortion - FPPMEAMHDS 26 AI Temperature - FPPMEAMTMP AI User defined measurement - FPPMEAMXXX PC User defined pulse counter - FPPMEAMXXX 38 PC Active energy E (kwh) - FPPMEAMAEN 39 PC Active energy E (MWh) - FPPMEAMAEN 40 PC Active energy E (GWh) - FPPMEAMAEN 41 PC Reverse active energy E (kwh) - FPPMEAMAEN 42 PC Reverse active energy E (MWh) - FPPMEAMAEN 43 PC Reverse active energy E (GWh) - FPPMEAMAEN 44 PC Reactive energy E (kvarh) - FPPMEAMREN 45 PC Reactive energy E (Mvarh) - FPPMEAMREN 132

133 1MRS MicroSCADA Pro SYS Table Measurement process objects (Continued) Scale objects Index Obj. type Process object Remarks Group identifier 46 PC Reactive energy E (Gvarh) - FPPMEAMREN 47 PC Reverse reactive energy E (kvarh) - FPPMEAMREN 48 PC Reverse reactive energy E (Mvarh) - FPPMEAMREN 49 PC Reverse reactive energy E (Gvarh) - FPPMEAMREN 110 EVREC Current L1 Only RP-570; FPPMEAECUR optional 111 EVREC Current L2 Only RP-570; FPPMEAECUR optional 112 EVREC Current L3 Only RP-570; FPPMEAECUR optional 113 EVREC Neutral current I0 Only RP-570; FPPMEAENCU optional 114 EVREC Directional neutral current Ij Only RP-570; FPPMEAEDNC optional 115 EVREC Maximum demand I15min Only RP-570; FPPMEAEMDC optional 116 EVREC Voltage U12 Only RP-570; FPPMEAEVOL optional 117 EVREC Voltage U23 Only RP-570; FPPMEAEVOL optional 118 EVREC Voltage U31 Only RP-570; FPPMEAEVOL optional 119 EVREC Residual voltage U0 Only RP-570; FPPMEAERVL optional 120 EVREC Active power P Only RP-570; FPPMEAEAPW optional 121 EVREC Reactive power Q Only RP-570; FPPMEAERPW optional 122 EVREC Apparent power S Only RP-570; FPPMEAEAPP optional 123 EVREC Power factor Cosj Only RP-570; FPPMEAECOS optional 124 EVREC Frequency f Only RP-570; FPPMEAEFRQ optional 125 EVREC Harmonic distortion Only RP-570; FPPMEAEHDS optional 126 EVREC Temperature Only RP-570; FPPMEAETMP optional EVREC User defined measurement Only RP-570; FPPMEAEXXX optional At the first installation, the measurement creates the scale 1_1 (linear 1:1 scale). For ANSI type of station, the scale BGU_1_1000 (linear 1:1000 scale) is also created at the installation. 133

134 SYS MicroSCADA Pro 1MRS Alarm indicator Standard function installation This chapter describes the installation of alarm indicator standard function from the SA-LIB. The standard function for the alarm indicator is found in the directory /SA_LIB/BASE/BBONE/INST and it should be installed by using the SA-LIB installation procedures (SA_LIB/Process/Alarm Indicator). This standard function is configured by using configuration tools such as: 1. Object Navigator 2. List-Based Engineering Tool Symbol installation The SA symbol for alarm indicator standard function is installed by using the Display Builder functions: 1. Object Browser 2. Palette For further information, refer to the SYS 600 Process Display Design manual. Table SA symbol for the alarm indicator standard function File Name Alarm A.sd Symbol Alarm Bell.sd Alarm Led.sd Alarm Star.sd Configuration with tools The alarm indicator standard function has the following attributes to be configured with the Object Navigator or the List-Based Engineering Tool: Table Alarm indication attributes to be configured with the tools Attribute Meaning Default STATION_NAME Name of the substation - BAY_NAME Name of the bay - DEVICE_NAME Name of the device - P_OBJECT_LN Logical name of database process object - 134

135 1MRS MicroSCADA Pro SYS Table Alarm indication attributes to be configured with the tools Attribute Meaning Default STATION_TYPE The type of control device & protocol. LON TYPE_OF_SIGNAL x The type of the input signal. - SIGNAL x _TEXT Identification for signal shown in event Not available lists, alarm list and so on ALARMING_STATE_OF_SIG The state of the signal when an alarm Not available NAL x (warning) is activated. LINK_SIGNAL x _LN The logical name of the process Not available object to which the signal is linked. LINK_SIGNAL x _IX The index of the process object to Not available which the signal is linked. AUTHORIZATION_GROUP The name of the authorization group. MV_CONTROL EVENT_RECORDING Selection whether the event recording Not available process objects are created when the RP-570 protocol is used. ACK_SOUND Enables Audible alarm acknowledgement button in Monitor Pro toolbar 1 For more detailed description on the configurable attributes, refer to Section Descriptions to the configurable attributes Configuration of process objects Depending on the configuration of the alarm indicator standard function, the tools will create a certain set of process objects in the database. Those process objects which are going to be linked to the actual process should be edited to have a station number, an address and a proper switching state. Otherwise, by default, all other attributes should have suitable values for normal operation. If the value of the attribute TYPE_OF_SIGNAL nr is linked, the process object is not created by the tools, but the name and the index of the signal is given to the attributes LINK_SIGNAL nr _TO_LN and LINK_SIGNAL nr _TO_IX. Table Process objects created for the alarm indicator Index Explanation Purpose Alarm indication Used for indication of the alarming state of the signal 135

136 SYS MicroSCADA Pro 1MRS Example of alarm indicator configuration Table Alarm indicator configuration Attribute Value STATION_NAME Eastwick BAY_NAME Outgoing HA5 DEVICE_NAME AI P_OBJECT_LN EST_HA5AI STATION_TYPE LON TYPE_OF_SIGNAL1 Binary Input (BI) SIGNAL1_TEXT SF6 low pressure ALARMING_STATE_OF_SIGNAL1 (1) AUTHORIZATION_GROUP MV_CONTROL Application engineering information Structure of the alarm indicator standard function This section describes the structure of the alarm indicator standard function. All subdrawing files, form pictures, help and other text files, as well as database objects are included. The alarm indicator is a part of the standard functions of SA-LIB and has a directory /SA_LIB/BASE/BBONE, and the standard SA-LIB subdirectories INST, LANG0 and USE Files Below there is a list of all alarm indicator standard function related files and their functionality. Table Alarm indicator standard function related files File Functionality Path Alarm A.sd SA symbol for alarming A /PROG/GRAPHICSENGINE/PALETTE/04 - SA_Indication Alarm Bell.sd SA symbol for alarming bell /PROG/GRAPHICSENGINE/PALETTE/04 - SA_Indication Alarm Led.sd Alarm Star.sd FORM5SAGR1.PIC SA symbol for alarming led SA symbol for alarming star Generic format picture for printing /PROG/GRAPHICSENGINE/PALETTE/04 - SA_Indication /PROG/GRAPHICSENGINE/PALETTE/04 - SA_Indication /SA_LIB/BASE/BBONE/USE Language text file The following Text Translation Tool compatible text files are used by the alarm indicator standard function. The path is /SA_LIB/BASE/BBONE/LANG0. Table indicator File SAI_AI.TXT Text Translation Tool compatible text file used by the alarm Functionality Text file for the database creation of the standard function 136

137 1MRS MicroSCADA Pro SYS Help text file The path to the alarm indicator help text file is /SA_LIB/BASE/BBONE/LANG0. Table File SAI_AI.HLP Alarm indicator help text file Functionality Standard function installation help file Configuration files The following configuration files are used by the alarm indicator standard function. The path is /SA_LIB/BASE/BBONE/INST. Table File SAI_AI.DAT SAI_AI.POT NDEX5_B1.TXT Configuration files used by the alarm indicator Functionality Contains the configuration data for alarm indicator when it is created modified or deleted by configuration tools Contains the process object definitions for the Object Navigator and List-Based Engineering Tool Selection list of SA-LIB standard functions for installation tool Auto Reclose Standard function installation This chapter describes the installation of Auto Reclose standard function from the SA-LIB. The standard function for the Auto Reclose is found in the directory / SA_LIB/BASE/BBONE/INST and it should be installed by using the SA-LIB installation procedures (SA_LIB/Process/Auto Reclose). This standard function is configured by using configuration tools such as: 1. Object Navigator 2. List-Based Engineering Tool Symbol installation The SA symbol for Auto Reclose standard function is installed by using the Display Builder functions: 1. Object Browser 2. Palette For further information, refer to the SYS 600 Process Display Design manual. Table SA symbol for Auto Reclose standard function File Name Symbol Auto-Reclosing BI.sd 137

138 SYS MicroSCADA Pro 1MRS Table SA symbol for Auto Reclose standard function (Continued) File Name Symbol Auto-Reclosing.sd Configuration with tools The Auto Reclose standard function has the following attributes to be configured with the Object Navigator or the List-Based Engineering Tool: Table Auto Reclose standard function configurable attributes Attribute Meaning Default STATION_NAME Name of the substation - BAY_NAME Name of the bay - DEVICE_NAME Name of the device - P_OBJECT_LN Logical name of database - process objects STATION_TYPE The type of control device & protocol LON OUTPUT_STATUS Process objects for output status N/A with DNP 3.0 protocol AR_WITH_MULTIPLE_CYCLE Select object type to indicate No S auto-reclosure in progress SHOW_AR_IN_USE Show tag during auto-reclosure Show tag SHOW_AR_NOT_IN_USE Show tag also when no autoreclosing Do not show tag is in progress EVENT_RECORDING Process objects for event No process objects recording with RP-570 LINK_AR_TAG_TO_LN Create link between existing - auto-reclosing objects from other Object Browser functions LINK_AR_TAG_TO_MODULE Select type designation of the auto-reclosing module No linking OPC_ITEM_PREFIX OPC_LN_INSTANCES Specifies the OPC Item Prefix used as IEC Instance information Specifies the OPC Logical Node names used as IEC Instance information "IEC61850 Subnetwork.IED1.LD1" VECTOR("RREC1") For more detailed description on the configurable attributes, refer to Section Descriptions to the configurable attributes. 138

139 1MRS MicroSCADA Pro SYS Configuration of process objects Depending on the configuration of the Auto Reclose standard function, the tools create a certain set of process objects in the database. The process objects which are going to be linked to an actual process should be edited to have a station number, an address and a proper switching state. Otherwise, by default, all other attributes should have suitable values for normal operation. Table Process objects created for Auto Reclose Index Explanation Purpose 10 Auto-reclosing in use/out of use indication (optional) 11 Auto-reclosing in use/out of use indication (optional) 12 Auto-reclosing in progress/not in progress ind. (optional) 13 Auto-reclosing interrupt command (optional) 14 Auto-reclosing in use/out of use command (optional) 110 Auto-reclosing in use/out of use indication (optional) 111 Auto-reclosing in use/out of use indication (optional) 112 Auto-reclosing in progress/not in progress ind. (optional) 113 Auto-reclosing interrupt command (optional) 114 Auto-reclosing in use/out of use command (optional) Application engineering information Indicates if the auto-reclose is in use (software switch of the auto-reclosing unit). Indicates if the auto-reclose is in use (hardware switch of the auto-reclosing unit). Indicates if there is an auto-reclosing sequence running. Interrupts the auto-reclosing sequence. Enables/disables the auto-reclosure. Event recording object (for accurate time stamp) with RTU 2xx/RP-570 type of stations. Event recording object (for accurate time stamp) with RTU 2xx/RP-570 type of stations. Event recording object (for accurate time stamp) with RTU 2xx/RP-570 type of stations. Command termination object with IEC and -103 type of stations. Output status object with DNP 3.0 type of stations. Command termination object with IEC and -103 type of stations. Output status object with DNP 3.0 type of stations Structure of the Auto Reclose standard function This section describes the structure of the Auto Reclose standard function. All subdrawing files, form pictures, help and other text files, as well as database objects are included. The Auto Reclose is a part of the standard functions of SA-LIB and has a directory /SA_LIB/BASE/BBONE, and the standard SA-LIB subdirectories INST, LANG0 and USE. 139

140 SYS MicroSCADA Pro 1MRS Files Language text file Below there is a list of all Auto Reclose standard function related files and their functionality. Table Auto Reclose standard function related files File Functionality Path Auto-Reclosing.sd SA symbol for Auto Reclose /PROG/GRAPHICSENGINE/ PALETTE/04 - SA_Indication FORM5SAGR1.PIC Generic format picture for /SA_LIB/BASE/BBONE/USE printing The following Text Translation Tool compatible text files are used by the Auto Reclose standard function. The path is /SA_LIB/BASE/BBONE/LANG0. Table Text Translation Tool compatible text file used by the Auto Reclose standard function File SAI_ARC2.TXT Functionality Text file for the database creation of the standard function Help text file The path to the Auto Reclose help text file is /SA_LIB/BASE/BBONE/LANG0. Table Auto Reclose help text file File SAI_ARC2.HLP Functionality Standard function installation help file Configuration files The following configuration files are used by the Auto Reclose standard function. The path is /SA_LIB/BASE/BBONE/INST. Table Configuration files used by the Auto Reclose stardard function File SAI_ARC2.DAT SAI_ARC2.POT NDEX5_B1.TXT Functionality Contains the configuration data for the Auto Reclose when it is created, modified or deleted by configuration tools Contains the process object definitions for the Object Navigator and List- Based Engineering Tool Selection list of SA-LIB standard functions for installation tool 140

141 1MRS MicroSCADA Pro SYS Process objects The following process objects are created for the Auto Reclose standard function. Table Process objects created for the Auto Reclose standard function Index Obj. type Process object Remarks Group ident. 10 BI Auto-reclosing in use Software switch Optional 11 BI Auto-reclosing in use Hardware switch Optional 12 BI or AI Auto-reclosing in Optional progress 13 BO Auto-reclosing Optional interruption 14 BO AR in use/ out of use - Optional cmd 110 EVREC Event recording for auto-reclosing in use 111 EVREC Event recording for auto-reclosing in use 112 EVREC Event recording for auto-reclosing in progress 113 TERM / OS Command termination of auto-reclosing interruption Output status object 114 TERM / OS Command termination of auto-reclosing in use/ out of use cmd Only RP-570 Optional Only RP-570 Optional Only RP-570 Optional Only IEC and -103; Optional Output status object when station type is DNP 3.0, Optional Only IEC and -103; Optional FPFARCISCE FPFARCISCE FPFARCIARC FPFARCCINR FPFARCCSCE FPFARCESCE FPFARCESCE FPFARCEARC FPFARCTINR FPFARCTSCE Output status object Output status object when station type is DNP 3.0, Optional Scale objects At the first installation the Auto Reclose creates the scale 1_1 (linear 1:1 scale). For multiple shots with ANSI type of station the installation creates also the scale BGU_1_1000 (linear 1:1000 scale) Trip Signal Standard function installation This chapter describes the installation of Trip Signal standard function from the SA- LIB. The standard function for the Trip Signal is found in the directory /SA_LIB/ BASE/BBONE/INST and it should be installed by using the SA-LIB installation procedures (SA_LIB/Process/Trip Signal). This standard function is configured by using the configuration tools, such as: 141

142 SYS MicroSCADA Pro 1MRS Object Navigator 2. List-Based Engineering Tool Symbol installation The SA symbol for Trip Signal standard function is installed by using the Display Builder functions: 1. Object Browser 2. Palette For further information, refer to the SYS 600 Process Display Design manual.. 142

143 1MRS MicroSCADA Pro SYS Table SA symbol for the Trip Signal standard function File Name Symbol Tripping.sd Configuration with tools The Trip Signal standard function has the following attributes to be configured with the Object Navigator or the List-Based Engineering Tool: Table Configurable Attributes Attribute Meaning Default STATION_NAME Name of the substation - BAY_NAME Name of the bay - DEVICE_NAME Name of the device - P_OBJECT_LN Logical name of database process - objects STATION_TYPE The type of control device & protocol LON OUTPUT_STATUS Process objects for output status with N/A DNP 3.0 protocol EVENT_RECORDING Process objects for event recording No process objects with RP-570 LINK_TRIP_TAG_TO_LN_x The logical name of the database - process objects to which this trip tag is linked. LINK_TRIP_TAG_TO_ MODULE_x The module to which this trip tag is linked. No linking For more detailed description on the configurable attributes, refer to Section Descriptions to the configurable attributes Configuration of process objects Depending on the configuration of the Trip Signal standard function, the tools create a certain set of process objects in the database. Those process objects which are going be linked to actual process should be edited to have a station number, an address and a proper switching state. All other attributes should have suitable values for normal operation by default. Table Process objects created for Trip Signal Index Explanation Purpose 10 General protection trip indication (optional) 11 General trip relay latched indication (optional) General trip relay reset command (optional) The general protection trip indication can be used as ON/OFF type indication of any protection trip within the bay. The general trip relay latched indication can be used as ON/OFF type indication of any latched protection trip relay within the bay. The general trip relay reset command object is an output object which can be used to reset latched output relays, trip indicators and memorised parameters. 143

144 SYS MicroSCADA Pro 1MRS Table Process objects created for Trip Signal (Continued) Index Explanation Purpose 110 General protection trip indication (optional) 111 General trip relay latched indication (optional) Indication for command termination (optional) Event recording object (for accurate time stamp) with RTU 2xx/RP-570 type of stations. Event recording object (for accurate time stamp) with RTU 2xx/RP-570 type of stations. Indicates with IEC and -103 whether the issued command was successful or not Application engineering information Structure of the Trip Signal standard function This section describes the structure of the Trip Signal standard function. All subdrawing files, form pictures, help and other text files, as well as database objects are included. The Trip Signal is a part of the standard functions of SA-LIB and has the directory /SA_LIB/BASE/BBONE, and the standard SA-LIB subdirectories INST, LANG0 and USE Files Below there is a list of all Trip Signal standard function related files and their functionality. Table Trip Signal stardard function related files File Functionality Path Tripping.sd SA symbol for Trip Signal PROG/GRAPHICSENGINE/PALETTE/04 - SA_Indication FORM5SAGR1.PIC Generic format picture for SA_LIB/BASE/BBONE/USE printing Language text file The following Text Translation Tool compatible text file is used by the Trip Signal standard function. The path is /SA_LIB/BASE/BBONE/LANG0. Table Text Translation Tool compatible text file used by the Trip Signal standard function File SAI_TRIP2.TXT Functionality Text file for the database creation of the standard function Help text file The path to the Trip Signal help text file is /SA_LIB/BASE/BBONE/LANG0. Table Help text file used by the Trip Signal File SAI_TRIP2.HLP Functionality Standard function installation help file 144

145 1MRS MicroSCADA Pro SYS Configuration files The following configuration files are used by the Trip Signal standard function. The path is /SA_LIB/BASE/BBONE/INST. Table Configuration files used by the Trip Signal standard function File SAI_TRIP2.DAT SAI_TRIP2.POT NDEX5_B1.TXT Functionality Contains the configuration data for Trip Signal when it is created modified or deleted by configuration tools Contains the process object definitions for the Object Navigator and List-Based Engineering Tool Selection list of SA-LIB standard functions for installation tool Process objects Scale objects The following process objects are created for the Trip Signal standard function. Table Process objects created for the Trip Signal Index Obj. type Process object Remarks Group ident. 10 BI Protection trip Optional FPFTRPITRP 11 BI Trip relay latched Optional FPFTRPITRL 12- BO Latched trip relay reset Optional FPFTRPCTRL EVREC Protection trip Only RP-570 FPFTRPETRP Optional 111 EVREC Trip relay latched Only RP-570 FPFTRPETRL Optional TERM Command termination of latched trip relay reset Only IEC and -103; Optional FPFTRPTTRL At the first installation the Trip Signal creates the scale 1_1 (linear 1:1 scale) Generator Standard function installation This chapter describes the installation of generator standard function from the SA- LIB. You can find the standard function for generator in the /SA_LIB/BASE/ BBONE/INST directory and install it by using the SA-LIB installation procedures (SA_LIB/Process/Generator). To configure this standard function, you can use the following tools: 1. Object Navigator 2. List-Based Engineering Tool 145

146 SYS MicroSCADA Pro 1MRS Symbol installation You can install the SA symbol for the generator standard function by using the following Display Builder functions: 1. Object Browser 2. Palette For further information, refer to the SYS 600 Process Display Design manual. Table SA symbol for the generator standard function File Name Symbol Generator.sd Configuration with tools You can configure the following generator standard function attributes with the Object Navigator or the List-Based Engineering Tool: Table Generator standard function configurable attributes Attribute Meaning Default STATION_NAME Name of the substation - BAY_NAME Name of the bay - DEVICE_NAME Name of the device - P_OBJECT_LN Logical name of database process objects - For more detailed description on the configurable attributes, refer to Section Descriptions to the configurable attributes Configuration of process object The generator s configuration creates one process object in the database. Table Process object created for the generator Index Explanation Purpose 255 Generator color Used for generator coloring object by DMS Application engineering information Structure of the generator standard function This section describes the structure of the generator standard function. All the subdrawing files, form pictures, help and other text files, as well as database objects are included in it. The generator is a part of the standard functions of SA-LIB and has the directory /SA_LIB/BASE/BBONE and the standard SA-LIB subdirectories INST, LANG0 and USE. 146

147 1MRS MicroSCADA Pro SYS Files Below, there is a list of all the generator standard function related files and their functionality. Table Generator standard function related files File Functionality Path Generator.sd SA symbol for the generator PROG/GRAPHICSENGINE/PALETTE/ 01 - SA_Common Language text file The following Text Translation Tool compatible text file is used by the generator standard function. The path is /SA_LIB/BASE/BBONE/LANG0. Table Text Translation Tool compatible text file used by the generator standard function File SAI_GEN.TXT Functionality Text file for the database creation of the standard function Help text file The path to the generator help text file is /SA_LIB/BASE/BBONE/LANG0. Table Help text file used by the generator File SAI_GEN.DAT Functionality Contains the configuration data and process object definitions for the generator when it is created, modified or deleted by configuration tools Configuration files The following configuration files are used by the generator standard function. The path is /SA_LIB/BASE/BBONE/INST. Table Configuration files used by the generator standard function File SAI_GEN.DAT INDEX5_B1.TXT Functionality Contains the configuration data and process object definitions for the generator when it is created, modified or deleted by configuration tools Selection list of SA-LIB standard functions for the Installation tool Process object The following process object is created for the generator standard function. Table Process object created for the generator Index Obj. type Process object Remarks Group ident 255 AI Generator color - BCHTCIXPCD Scale object At the first installation the generator creates the scale 1_1 (linear 1:1 scale). 147

148 SYS MicroSCADA Pro 1MRS Line Indicator Standard function installation This chapter describes the installation of line indicator standard function from SA- LIB. You can find the standard function for the line indicator in the /SA_LIB/BASE/ BBONE/INST directory and install it by using the SA-LIB installation procedures (SA_LIB/Process/Line Indicator). To configure this standard function, you can use the following configuration tools: 1. Object Navigator 2. List-Based Engineering Tool Symbol installation You can install the SA symbol for the line indicator standard function by using the Display Builder functions: 1. Object Browser 2. Palette For further information, refer to the SYS 600 Process Display Design manual. Table SA symbol for the generator standard function File Name Symbol Horizontal Vertical Horizontal Vertical Line Indicator H.sd Line Indicator.sd Configuration with tools The line indicator standard function has the following attributes to be configured with the Object Navigator or the List-Based Engineering Tool: Table Line indicator standard function configurable attributes Attribute Meaning Default STATION_NAME Name of the substation - BAY_NAME Name of the bay - P_OBJECT_LN Logical name of the database process - objects LINE_INDICATOR_ COLORED_BY Specifies which product or function is used for the coloring DMS 600 For more detailed description on the configurable attributes, refer to Section Descriptions to the configurable attributes. 148

149 1MRS MicroSCADA Pro SYS Configuration of process objects Configuration of the line indicator creates a certain set of process objects in the database. Table Process objects created for the line indicator Index Explanation Purpose 10 DMS 600 color number Used for line indicator coloring object by DMS Virtual switch for Topol. Col. Virtual switch for network topology coloring 254 Ext. ground ind. For Topol. Col. External ground indicator for network topology coloring 255 Infeed color for Topol. Col. Infeed color for network topology coloring Application engineering information Structure of the line indicator standard function This section describes the structure of the line indicator standard function. All the sub-drawing files, form pictures, help and other text files, as well as database objects are included. The line indicator is a part of the standard functions of SA-LIB and has the directory /SA_LIB/BASE/BBONE, and the standard SA-LIB subdirectories INST, LANG0 and USE Files Below, there is a list of all the line indicator standard function related files and their functionality. Table Line indicator standard function related files File Functionality Path Line Indicator.sd Vertical SA symbol for Line Indicator Line Indicator H.sd Horizontal SA symbol for Line Indicator FORM5SAGR1.PIC Generic format picture for printing PROG/GRAPHICSENGINE/PALETTE/ 01 - SA_Common PROG/GRAPHICSENGINE/PALETTE/ 01 - SA_Common SA_LIB/BASE/BBONE/USE Language text file The following Text Translation Tool compatible text file is used by the line indicator standard function. The path is /SA_LIB/BASE/BBONE/LANG0. Table Text Translation Tool compatible text file used by the line indicator standard function File SAI_LIND.TXT Functionality Text file for the database creation of the standard function 149

150 SYS MicroSCADA Pro 1MRS Help text file The path to the line indicator help text file is /SA_LIB/BASE/BBONE/LANG0. Table Help text file used by the line indicator File SAI_LIND.HLP Functionality Standard function installation help file Configuration files The following configuration files are used by the line indicator standard function. The path is /SA_LIB/BASE/BBONE/INST. Table Configuration files used by the line indicator File SAI_LIND.DAT INDEX5_B1.TXT Functionality Contains the configuration data and process object definitions for the line indicator when it is created, modified or deleted by configuration tools Selection list of SA-LIB standard functions for the Installation tool Command procedures At first installation, the line indicator creates the command procedure SAI_MTSTS, which updates the status of the line indicator color. For the indication type of an analog input (AI), the installation creates the command procedure SAI_MT2TC, which updates the fictitious power indicator, grounding indicator and active voltage color Process objects The following process objects are created for the line indicator standard function. Table Process objects created for the line indicator Index Obj. type Process object Remarks Group ident. 10 AI DMS 600 color number - BCHMTCXFCD 253 BI Virtual switch for Topol. Col. - BCHTCIXFPI 254 AI Ext. ground ind. for Topol. Col. - BCHTCIXCCD 255 AI Infeed color for Topol. Col - BCHTCIXPCD Scale object At first installation, the line indicator creates the scale 1_1 (linear 1:1 scale). 150

151 1MRS MicroSCADA Pro SYS Descriptions to the configurable attributes STATION_NAME A selector type of an editable combo box to select or enter the name of the substation. By default, the maximum length of the text is 9 characters. The selection list shows up to ten latest entries. The configurable attribute is read directly from the process object database, if there is any process object linked to the selected station picture function. Therefore, the configurable attribute within a picture function has only meaning when the process objects have not been created. This text is used as a substation identifier of the common station objects on event list, alarm list, printout, database query, and so on. It is very important that this text is similar to all objects within the same substation. P_OBJECT_LN The logical name of the database process objects. The maximum length of the text is 10 characters. Allowed characters are letters A-Z, all digits and the underscore (_). The logical names of process objects have to be unique throughout the entire system, that is, different objects cannot have the same logical name. Therefore, it is very important to have a proper naming convention for the process object database. Certain naming convention is also required to speed up the opening time of the main dialogs. With the predefined naming convention it is possible to collect all station and bay related database objects without searching through the complete database. Therefore, it is advised to use the following naming convention: The first three characters identify the substation The following four characters identify the bay The last three characters can be freely used to identify the source of the signal, that is device, unit, and so on. The following list is presented as an example of the proper naming convention within one bay. The station name is Green Bay and the bay name is HA12 Downtown: GRB, station GRBHA12BAY, bay GRBHA12Q0, circuit breaker Q0 GRBHA12Q1, truck Q1 GRBHA12Q9, earth switch Q9 GRBHA12CT, measurements/current transformer GRBHA12VT, measurements/voltage transformer GRBHA12ALA, alarm indicator GRBHA12AR, auto-reclosing tag GRBHA12TRP, tripping tag 151

152 SYS MicroSCADA Pro 1MRS GRBHA12R1, feeder terminal or protection unit 1 GRBHA12R2, feeder terminal or protection unit 1 If some other naming convention than 3+4 is used, it usually takes a longer time to open the main control dialogs. STATION_TYPE A selector type of a combo box to select the station type of the objects. The database process objects are created for the station type defined here. The list of supported protocols is as follows: SPA ANSI LON RP-570 RP-570 with FTABs IEC IEC IEC DNP 3.0 Modbus RTU PROCOL CMD_PARAMETER A selector type of a combo box to select a command parameter for the control method. This attribute has meaning only if IEC or DNP 3.0 protocol is selected, otherwise this attribute is disabled. The supported control parameters for the IEC protocol are: Double command (TY = 46) Single command (TY = 45) and for DNP 3.0 protocol: Direct Direct - No ack. OUTPUT_STATUS An ON/OFF type of a toggle button to select whether there is need for output status process objects with the DNP 3.0 protocol. If STATION_TYPE is other than DNP 3.0, the configurable attribute is disabled, and the value has no meaning. 152

153 1MRS MicroSCADA Pro SYS AUTHORIZATION_GROUP A selector type of an editable combo box to select the authorization group for the object. The maximum length of the text is 63 characters. The given text has to be usable as a SCIL list attribute name. For more information about the SCIL list attribute name, refer to Programming Language SCIL. The contents of the selection list is taken from the existing authorization groups. The name may not be composed of two letters followed by a number. The attribute needs to be defined, if the object is wanted to be included in some authorization group. The authorization level of each user in this group can be defined afterwards by the system manager with User Management pictures. STATION_LR_IN_USE An ON/OFF type of a toggle button to select if the station local/remote switch is in use, that is, a physical switch exists. By default, the station local/remote switch is in use. If this selection is set OFF, the control authority is given to everyone whose personal authorization level is high enough for the control actions. This is gained by setting the state (value) of the station local/remote switch permanently out of use. The process object for station local/remote switch is created regardless of the selection. If the station local/remote switch is NOT in use, the process object should be left as it is created, that is, switching state (SS) to manual and value (DB) as 3 (out of use). IND_DOUBLE_BINARY An ON/OFF type of toggle button to select whether the station/remote switch indication type is double binary or single binary. This selection is disabled and it has no meaning if the station/remote switch is not in use, that is, STATION_LR_IN_USE is not set. Depending on the actual field device or communication protocol, the indication of the local/remote switch is sent either as a single binary (0/1) or as a double binary (0/1/2/3) format. Binary input: 0 = Remote 1 = Station Double binary input: 0 = Local 1 = Station 2 = Remote 3 = Out of use 153

154 SYS MicroSCADA Pro 1MRS LR_REMOTELY_CONTROLLABLE An ON/OFF type of a toggle button for the selection, whether the station local/ remote switch can be controlled remotely by SYS 600, or not. By default, the station local/remote switch is defined as manually controllable only. Typically, if there is a remote control for the station local/remote switch, switching election between the station and remote can be done remotely, whereas switching election to or from local has to be performed locally. Switching to and from local: This can be achieved by setting the attribute SS (switching state) of the local command -process object to OFF (0). Setting the SS-attribute to 0 will make the relevant radio-button in the dialog insensitive for selections. EVENT_RECORDING An ON/OFF type of a toggle button to select whether there is need for event recording process objects with the RP-570 protocol. If STATION_TYPE is other than RTU 2xx or RTU 2xx/FTABs, the configurable attribute is disabled and the value has no meaning. With the RP-570 the time stamp from process device comes into the event recording process object. If no accurate time stamp is needed or available, or the device is emulating the RP-570 without an event recording possibility, do not set this attribute ON. ACK_SOUND When set to 1, the Audible alarm acknowledgement button is enabled on the Monitor Pro toolbar when related process object is taken into use by setting IU attribute value to 1. This command procedure can be used to launch appropriate actions that are required to acknowledge audible alarm. After changing value of IU attribute, logging out/in is necessary before the button becomes visible in the toolbar. OPC_ITEM_PREFIX Specifies the OPC Item Prefix used as an IEC instance information. The default is IEC61850 Subnetwork.IED1.LD1". OPC_LN_INSTANCES Specifies the OPC Logical Node names used as IEC instance information. The dafult is VECTOR("LLN0"). 154

155 1MRS MicroSCADA Pro SYS BAY_NAME A selector type of an editable combo box to select or enter the name of the bay (feeder). By default, the maximum length of the text is 14 characters. The selection list shows up to ten latest entries. The configurable attribute is read directly from the process object database, if there is any process object linked to the selected bay picture function. Therefore, the configurable attribute within a picture function has meaning only when the process objects have not been created. This text will be used as a bay (feeder) identifier of the common bay objects on event list, alarm list, printout, database query, and so on. It is very important that this text is similar to all objects within the same bay (feeder). BAY_LR_IN_USE An ON/OFF type of a toggle button to select if the bay local/remote switch is in use, that is, a physical switch exists. By default, the bay local/remote switch is in use. It is typical that if RTU 200 or RTU 210 is used as a remote terminal unit, there is no bay local/remote switches at bay level. The control authority of a single bay is determined by using station local/remote switch only. The process object for bay local/remote switch is created regardless of the selection. If the bay local/remote switch is NOT in use, the process object should be left as it is created, that is, switching state (SS) to manual and value (DB) as 2 (remote). BAY_LR_POLARITY The polarity of the bay local/remote-switch input signal. LR_REMOTELY_CONTROLLABLE An ON/OFF type of a toggle button to select if the bay local/remote switch can be controlled remotely by SYS 600. This selection is disabled and it has no meaning if the bay local/remote switch in not in use, that is, BAY_LR_IN_USE is not set. By default, bay local/remote switch is defined as manually controllable only. It is typical that if there is a remote control for bay local/remote switch, shift to local can be done remotely, whereas shift from local to remote has to be performed locally. This can be achieved by setting the attribute SS (switching state) of the local command process object to OFF (0). By setting the SS-attribute to 0, the relevant radio-button on dialog becomes insensitive for shifting. DEVICE_NAME A selector type of an editable combo box to select or enter the name (identifier) of the switching device. By default, the maximum length of the text is 5 characters. The selection list shows up to ten latest entries. 155

156 SYS MicroSCADA Pro 1MRS The configurable attribute is read directly from the process object database, if there is any process object linked to the selected switching device. Therefore, the configurable attribute within a picture function has meaning only when the process objects have not been created. This text will be used as an identifier of the switching device on event list, alarm list, printout, database query, and so on. SWICHING_DEVICE_TYPE A selector type of a combo box to select the type of the switching device. By default, the type is a circuit breaker. The configurable attribute has a great effect since it defines the index range for process objects, the texts within database and dialogs, the functionality and methods on dialogs, and so on. It is also used by the event and alarm list when filtering certain types of switching devices. Circuit breakers: Circuit breaker Circuit breaker with synchro-check Circuit breaker-disconnector (no full breaking capacity) Disconnectors: Disconnector Fuse switch Load breaking switch Earth switch Fault-making switch Truck Three-state switch (needs to be set up by installing two picture functions) SWICHING_DEVICE_PURPOSE A selector type of a combo box to select the purpose of the switching device. The configurable attribute has just an informative purpose since by the default it is not used by any function within LIB 5xx. The attribute is stored into process object database (the 25 th or the 26 th character of the RX attribute) for user-defined purposes, for example, for special search condition on the alarm or event list. Circuit breakers: Circuit breaker Main busbar circuit breaker Main busbar A circuit breaker Main busbar B circuit breaker 156

157 1MRS MicroSCADA Pro SYS Reserve busbar circuit breaker By-pass circuit breaker Bus-section circuit breaker Bus-coupler circuit breaker Disconnectors: Disconnector Main busbar disconnector Main busbar A disconnector Main busbar B disconnector Reserve busbar disconnector By-pass disconnector Line disconnector Line disconnector A Line disconnector B Bus-section disconnector Bus-section A disconnector Bus-section B disconnector Bus-section C disconnector Bus-coupler disconnector Earth switches: Earth switch Main busbar earth switch Main busbar A earth switch Main busbar B earth switch Reserve busbar earth switch By-pass earth switch Line earth switch Line earth switch A Line earth switch B CT-section earth switch Fault-making switch Truck Three-state switch SWITCH_SECTION A selector type of a combo box to select the switch section for the truck and the three-state switch. If SWITCHING_DEVICE_TYPE is some other than truck or three-state switch, the configurable attribute is disabled, and the value has no meaning. 157

158 SYS MicroSCADA Pro 1MRS When the type of the switching device is truck, this configurable attribute is needed to combine two picture functions as one physical truck for Network Topology Coloring. If there is a circuit breaker with two truck picture functions, this attribute should have a different value for both truck picture functions. In that way, the Network Topology Coloring calculation algorithm knows that the other picture function is not a duplicate but a part of the other one. Any of the two picture functions can be selected as the first section, as long as the other picture function is selected as the second section of the truck. If only one picture function will be used (that is, one sided installation), the attribute can be left by default. As far as the three-state switch is concerned, this selection will be used to identify whether the picture function is for the disconnector section or for the earth switch section of the three-state switch. INDICATION_TYPE A selector type of a combo box to select the type of the position indication process object(s). By default, the process object type is defined as a double indication (DB). The purpose of this configurable attribute is to support other data type than double indication as the position indication of the switching device. The supported data types are: Double indication (DB) Single indication (BI) 2 x Single indications (2 x BI) Analog input (AI) The interface between the picture function and the process object database is always with double indication object, that is, there is an additional process object(s) receiving information and then passing it to double indication. MOTORIZED An ON/OFF type of a toggle button to select if the switching device is motorized and remotely controllable. By default, the switching device is defined as a motorized object. By selecting Motorized option, the Process Object Tool (POT) will create a set of process objects for control purpose and all configurable attributes related to control are being enabled. CONTROL_TYPE A selector type of a combo box to select the control method and the type of the control process object(s). If the configurable attribute MOTORIZED is not selected, this attribute is disabled, and the value has no meaning. 158

159 1MRS MicroSCADA Pro SYS The purpose of this configurable attribute is to support other control methods and process object types than the conventional one. The conventional control method depends very much on the configurable attribute STATION_TYPE since there is a certain default method for each protocol to control the switching device. The supported control methods are: Secured command with four binary outputs (open select, close select, execute, cancel) Secured command with two binary outputs (open execute, close execute) Secured command with two digital outputs (open execute, close execute; pulse length configurable) Secured command with a single binary output (*) (open select/close select/execute/cancel) Secured command with a single analog output (open select, close select, execute, cancel or open execute/close execute) Secured command with five binary outputs (open select, close select, open execute, close execute,cancel) Direct command with a single binary output (open execute/close execute) (*) Control method not supported with SPA and ANSI protocols Normally, A RTU 2xx with RP-570 uses secured command with a single binary output. CONTROL_PULSE_LENGTH An input field for integer value to set the pulse length of the control pulses. The configurable attribute is enabled, if the attribute MOTORIZED is set and CONTROL_TYPE is secured control with two digital outputs. CONTROL_BITS A vector type of an input field for integer values to specify the bits to be used to send a control command to the switching device. The configurable attribute is enabled if the attribute MOTORIZED is set and CONTROL_TYPE is a secured control with an analog output. There is a need to specify two or four elements for that vector. If two elements are specified, the first element represents the bit for Open execute while the second element is for Close execute. When four elements are used, the first represents the bit for Open select, the second represents Close select, the third represents Execute and the fourth represents Cancel. When five elements are used, the first represents the bit for Open select, the second represents Close select, the third represents Open execute, the fourth represents Close execute and the fifth represents Cancel. 159

160 SYS MicroSCADA Pro 1MRS The bit vector shall be given to the SCT in the following way: (0,1) or (9,10,11,8) or (0,0,1,2,3). AUXILIARY_PLUG An ON/OFF type of a toggle button to select whether the device utilizes an auxiliary plug or not. If the SWITCHING_DEVICE_TYPE is truck or three-state switch, the configurable attribute is disabled, and the value has no meaning. The process object for an auxiliary plug informs if the control cable from the switching device to the cubicle has been disconnected, that is, if the switching device is fully racked out from the cubicle. In that case, no switching device symbol is shown in the single line diagram. The process object can also be used as an internal tag without the process connection. In that case, the control dialog asks the auxiliary plug state when the object state is intermediate. INTERLOCKING_BYPASS Specifies whether the interlocking bypass function is used or not. The default is FALSE. SYNCHROCHECK_BYPASS Specifies whether the synchrocheck bypass function is used or not. The default is FALSE. QUALIFIERS Qualifier is a value that is written to the QL attribute of process object when writing the control command. The qualifiers are given as a vector of integers. Minimum length is 0 (default) and maximum length 5. The vector items have the following meanings: Item Meaning 1 = Qualifier for open select 2 = Qualifier for close select 3 = Qualifier for open execute 4 = Qualifier for close execute 5 = Qualifier for cancel For example, (1,2,3) defines qualifier 1 for open select, qualifier 2 for close select and qualifier 3 for open execute. It is not possible to give "empty" items e.g. (,,,,3), but all the values must be given, e.g. (0,0,0,0,3). 160

161 1MRS MicroSCADA Pro SYS NOMINAL_VOLTAGE The nominal voltage of the voltage regulator. MIN_POSITION The minimum position of the tap changer. MAX_POSITION The maximum position of the tap changer. TRANSFORMER_TYPE Selection for the 2-winding or 3-winding transformer. HARD_WIRED The connection type between different SPAU modules when parallel operation is used. Hardwired means that different SPAU modules have a physical wiring between them. This is used when master/slave operation mode is wanted. AUTO_MANUAL_ID_TYPE The type and polarity of the auto/manual indication object for Generic tap changer. TYPE_MEAS_ number The type of the measurement. The type identifies the measurement for the creation of database (indexes, object texts, units...). In case no suitable alternative can be found, the indexes can be used. The indexes are for user-defined analog (AI) objects, and the indexes are for user-defined pulse counter (PC) objects. The database objects are not created until the Process Object Tool has been used to create them. FOLDER_ number _TITLE The name of the measurement to be shown in the measurement dialog. Attribute is optional, if it is not given, the measurement is referred to as "Meas. 'number'" in the dialog. If the configurable attribute TYPE_MEAS_'number' is not configured, this attribute is disabled, and the value has no meaning. MEAS_ number _DECIMALS The number of decimals used when presenting the measurement value in the dialog. 161

162 SYS MicroSCADA Pro 1MRS If the configurable attribute TYPE_MEAS_'number' is not configured, this attribute is disabled, and the value has no meaning. OPC_LN_INSTANCE_1 Specifies the OPC Logical Node names used as IEC Instance information for the measurement type 1. The default is VECTOR("MMXU1"). OPC_LN_INSTANCE_2 Specifies the OPC Logical Node names used as IEC Instance information for the measurement type 2. The default is VECTOR("MMXU1"). OPC_LN_INSTANCE_3 Specifies the OPC Logical Node names used as IEC Instance information for the measurement type 3. The default is VECTOR("MMXU1"). OPC_LN_INSTANCE_4 Specifies the OPC Logical Node names used as IEC Instance information for the measurement type 4. The default is VECTOR("MMXU1"). TYPE_OF_SIGNAL nr A selector type of a combo box to select the type of the signal. The list of supported input signals is as follows: Binary Input (BI) Double Binary (DB) Analog Input (AI) Linked If any of the first three choices is selected, the process objects are created by using the Process Object Tool. When Linked is selected, the logical name and the index of the process object where the signal is connected to has to be given. When an empty string is selected, it means that the signal is discarded by the alarm indicator. SIGNAL nr _TEXT This text is used as an identifier of the signal on event list, alarm list, printouts, and so on. 162

163 1MRS MicroSCADA Pro SYS ALARMING_STATE_OF_SIGNAL nr The alarming state of the signal is defined by this attribute. The value of the attribute is related to the type of the signal. The following examples clarify how this attribute should be defined: Type of signal is BI, alarming state is 1 value to be set: (1) Type of signal is DB, alarming states are 0 and 3 values to be set: (1,0,0,1) Type of signal is AI, high alarm = 12, high warning = 10, low warning = 8, low alarm = 6 values to be set: (12,10,8,6) LINK_SIGNAL nr _TO_LN The logical name of the process object to which the signal is linked. LINK_SIGNAL nr _TO_IX The index of the process object to which the signal is linked. AR_WITH_MULTIPLE_CYCLES An ON/OFF type of a toggle button to select the object type for the indication autoreclosing in progress. The configurable attribute is enabled, if the attribute P_OBJECT_LN has been configured. The database process objects will be created either as a binary input or as an analog input depending on the selection. SHOW_AR_IN_USE An ON/OFF type of a toggle button to select if the tag is shown when the autoreclosing is in use. The configurable attribute is enabled, if the attribute P_OBJECT_LN has been configured. By default no tag is shown. This is useful when the auto-reclosure is normally OFF and a warning should be produced if the auto-reclosing is in use. SHOW_AR_NOT_IN_USE An ON/OFF type of a toggle button to select if the tag is shown when the autoreclosing is not in use. The configurable attribute is enabled, if the attribute P_OBJECT_LN has been configured. By default, no tag is shown. This is useful when the auto-reclosure is normally ON and the warning should be produced if the auto-reclosing is not in use. 163

164 SYS MicroSCADA Pro 1MRS LINK_AR_TAG_TO_LN The logical name of the database process objects of the auto-reclosing module. The maximum length of the text is 10 characters. Allowed characters are the letters A-Z, all digits and the underscore (_). However, an object name cannot begin with a digit or an underscore. The configurable attributes LINK_AR_TAG_TO_LN and LINK_AR_TAG_TO_MODULE are utilized to create a link between existing autoreclosing objects from the other Object Browser function (for example. autoreclosing module) and the auto-reclosing tag. It even supports linking of userdefined process objects as LINK_AR_TAG_TO_MODULE is an editable selector. LINK_AR_TAG_TO_MODULE An editable selector type of a combo box to select the type designation of the autoreclosing module. The configurable attribute is enabled, if the attribute LINK_AR_TAG_TO_LN has been configured. By default, all auto-reclosing modules from SPACOM family have been implemented for the users to choose from. The supported modules are: SPCT 2C5 SPCT 2C17 SPCT 2D38 SPCT 2D46 SPCT 5D54 SPTO 6D3 SPCT 2D38 index 70 HSAR started/reset (E1/E2) index 74 SSAR started/reset (E6/E7) index 78 delayed SSAR started/reset (E11/E12) SPCT 2D46 index 91 HSAR forward started/reset (E1/E2) index 95 SSAR started/reset (E6/E7) index 109 auto-reclosing interrupted (E25) During the relay installation and configuration, the following indexes have to be created and SPACOM events have to be enabled as a minimum requirement for the auto-reclosing tag by using the SPACOM Relay Configuration Tool: SPCT 2C5 index 65 auto-reclosing started/reset (E1/E2) SPCT 2C17 index 151 auto-reclosing started/reset (E1/E2) SPCT 5D54 164

165 1MRS MicroSCADA Pro SYS index 32 auto-reclosing interrupted by ARINH (E30) index 33 auto-reclosing interrupted manually (E31) index 34 auto-reclosing interrupted by open cmd (E32) index 40 shot 1 started/reset (channel 1 - E1/E2) index 46 shot 2 started/reset (channel 2 - E1/E2) index 52 shot 3 started/reset (channel 3 - E1/E2) index 58 shot 4 started/reset (channel 4 - E1/E2) index 64 shot 5 started/reset (channel 5 - E1/E2) SPTO 6D3 index 16 auto-reclosing interrupted (E7) index 17 auto-reclosing interrupted by open cmd (E8) index 18 auto-reclosing interrupted by ARINH (E9) index 20 shot 1 started/reset (E11/E12) index 25 shot 2 started/reset (E16/E17) index 30 shot 3 started/reset (E21/E22) index 35 shot 4 started/reset (E26/E27) index 40 shot 5 started/reset (E31/E32) If there is no appropriate auto-reclosing module to choose, or if freely defined process objects are going to be used, it is possible to link those objects by using the following syntax: "IDENT","INDX1","REPR1","INDX2","REPR2",... IDENT = module ID - (used only as a comment) INDX1 = DB index of "AR in progress" -object 1 REPR1 = representation (symbol set) for object 1 INDX2 = DB index of "AR in progress" -object 2 REPR2 = representation (symbol set) for object 2 As an example, the auto-reclosing module SPCT 2D46: "SPCT 2D46","91","F_REPR/F_ARRUN4","95","F_REPR/ARRUN5" The type designation of the auto-reclosing module is not necessary; it is just additional information for users. LINK_TRIP_TAG_TO_LN_x The logical name of the database process objects of the protection module x (x=1..5). The maximum length of the text is 10 characters. Allowed characters are the letters A-Z, all digits and the underscore (_). The configurable attributes LINK_TRIP_TAG_TO_LN_x and LINK_TRIP_TAG_TO_MODULE_x are utilized to create a link between the existing protection tripping indication objects from the other picture function (for example protection module) and the trip indication tag. It even supports linking of user-defined process objects as LINK_TRIP_TAG_TO_MODULE_x, which is an editable selector. 165

166 SYS MicroSCADA Pro 1MRS LINK_TRIP_TAG_TO_MODULE_x An editable selector type of a combo box to select the type designation of the protection module x (x=1..5). The configurable attribute is enabled, if the attribute LINK_TRIP_TAG_TO_LN_x has been configured. By default, all protection modules from the SPACOM family have been implemented for the users to choose from. The supported modules are: SPAM 05x SPCD 2D55 SPCD 3C21 SPCD 3C22 SPCD 3C23 SPCD 3D53 SPCJ 1C7 SPCJ 1C8 SPCJ 2C30 SPCJ 3C3 SPCJ 3C48 SPCJ 3D35 SPCJ 4D24 SPCJ 4D28 SPCJ 4D29 SPCJ 4D34 SPCJ 4D36 SPCJ 4D40 SPCJ 4D44 SPCJ 4D61 SPCP 3C2 SPCS 2D26 SPCS 2D32 SPCS 2D37 SPCS 3C4 SPCS 4D11 SPCS 4D12 SPCS 4D13 SPCU 1C1 SPCU 1C6 SPCU 1D39 SPCU 1D47 SPCU 3C14 SPCU 3C15 SPEF 3A2 The minimum requirement for the tripping tag to function is that the following indexes have been created and SPACOM events have been enabled by using the Relay Configuration Tool: SPAM 05x 166

167 1MRS MicroSCADA Pro SYS index 122 thermal trip (E5/E6) index 125 di> trip (E11/E12) index 126 Is> trip (E13/E14) index 128 I0> trip (E17/E18) index 129 I> trip (E19/E20) SPCD 2D55 index 26 TS2 (E31/E32) Note! index 12 di01> (E3/E4) index 15 di02> (E9/E10) SPCD 3C21 index 32 di> L1 (E3/E4) SPCD 3C22 index 34 di> L2 (E3/E4) SPCD 3C23 index 36 di> L3 (E3/E4) SPCD 3D53 index 44 TS2 (E27/E28) Note! index 31 3dI> trip (E1/E2) index 32 3dI>> trip (E3/E4) index 49 3dI> trip/l1 (1E1/1E2) index 50 3dI>> trip/l1 (1E3/1E4) index 53 3dI> trip/l2 (2E1/2E2) index 54 3dI>> trip/l2 (2E3/2E4) index 57 3dI> trip/l3 (3E1/3E2) index 58 3dI>> trip/l3 (3E3/3E4) SPCJ 1C7 index 12 I0> trip (E3/E4) index 14 I0>> trip (E7/E8) SPCJ 1C8 index 16 I0> trip (E3/E4) index 18 I0>> trip (E7/E8) SPCJ 2C30 index 23 di0> trip (E1/E2) index 25 I0> trip (E5/E6) SPCJ 3C3 index 20 I> trip (E3/E4) index 22 I>> trip (E7/E8) SPCJ 3C48 167

168 SYS MicroSCADA Pro 1MRS index 57 I> trip (E3/E4) index 59 I>> trip (E7/E8) index 61 I0> trip (E11/E12) SPCJ 3D35 index 51 TS2 (E23/E24) Note! index 41 I1> trip (E3/E4) index 43 I2> trip (E7/E8) index 45 I3> trip (E11/E12) index 47 I4> trip (E15/E16) SPCJ 4D24 index 44 TS2 (E25/E26) index 33 I> trip (E3/E4) index 35 I>> trip (E7/E8) index 37 I0> trip (E11/E12) index 39 I0>> trip (E15/E16) SPCJ 4D28 index 80 TS2 (E25/E26) Note! index 66 I> trip (E3/E4) index 68 I>> trip (E7/E8) index 70 I>>> trip (E11/E12) index 72 I0> trip (E15/E16) index 74 I0>> trip (E19/E20) index 76 di> trip (E23/E24) SPCJ 4D29 index 57 TS2 (E25/E26) index 46 I> trip (E3/E4) index 48 I>> trip (E7/E8) index 50 I0> trip (E11/E12) index 52 I0>> trip (E15/E16) SPCJ 4D34 index 78 TS2 (E41/E42) index 60 thermal alarm trip (E5/E6) index 61 thermal overload trip (E7/E8) index 63 Is> trip (E11/E12) index 65 I>> trip (E15/E16) index 67 I0> trip (E19/E20) index 69 di> trip (E23/E24) index 71 I< trip (E27/E28) SPCJ 4D36 index 39 TS2 (E25/E26) index 28 I> trip (E3/E4) index 30 I>> trip (E7/E8) index 32 I0> trip (E11/E12) index 34 I0>> trip (E15/E16) 168

169 1MRS MicroSCADA Pro SYS SPCJ 4D40 index 95 TS2 (E33/E34) index 80 Ib> trip (E3/E4) index 82 Ia> trip (E7/E8) index 84 I< trip (E11/E12) index 86 di1> trip (E15/E16) index 88 di2> trip (E19/E20) SPCJ 4D44 index 108 TS2 (E25/E26) index 97 I> trip (E3/E4) index 99 I>> trip (E7/E8) index 101 I01> trip (E11/E12) index 103 I02> trip (E15/E16) SPCJ 4D61 index 135 TS2 (E31/E32) Note! index 121 I> trip (E3/E4) index 123 I>> trip (E7/E8) index 125 I>>> trip (E11/E12) index 127 I0> trip (E15/E16) index 129 I0>> trip (E19/E20) index 131 di> trip (E23/E24) SPCP 3C2 index 62 U>, U>> trip (E3/E4) index 64 reverse power trip (E7/E8) SPCS 2D26 index 95 TS2 (E19/E20) Note! index 87 U0b> trip (E3/E4) SPCS 2D32 index 107 TS2 (E22/E30) Note! index 97 I0> trip (E5/E6) index 99 U02> trip (E9/E10) index 101 I0>> trip (E13/E14) index 103 Itr> trip (E17/E18) SPCS 2D37 index 22 TS2 (E23/E24) Note! index 12 I01> first trip (E3/E4) index 14 I01> second trip (E7/E8) index 16 I02> trip (E11/E12) index 18 I03> trip (E15/E16) SPCS 3C4 index 29 I0> trip (E3/E4) index 31 I0>> trip (E7/E8) 169

170 SYS MicroSCADA Pro 1MRS SPCS 4D11 index 121 TS2 (E25/E26) index 111 I> trip (E5/E6) index 113 I>> trip (E9/E10) index 115 I>>> trip (E13/E14) SPCS 4D12 index 134 TS2 (E25/E26) index 124 I> trip (E5/E6) index 126 I>> trip (E9/E10) index 128 I>>> trip (E13/E14) SPCS 4D13 index 147 TS2 (E25/E26) index 137 I> trip (E5/E6) index 139 I>> trip (E9/E10) index 141 I>>> trip (E13/E14) SPCU 1C1 index 12 U> trip (E3/E4) index 14 U< trip (E7/E8) SPCU 1C6 index 16 U0> trip (E3/E4) index 18 U0>> trip (E7/E8) SPCU 1D39 index 126 TS2 (E23/E24) Note! index 120 U0> trip (E11/E12) SPCU 1D47 index 142 TS2 (E23/E24) Note! index 136 U> trip (E11/E12) SPCU 3C14 index 20 U> trip (E3/E4) index 22 U< trip (E7/E8) SPCU 3C15 index 20 U< trip (E3/E4) index 22 3U<< trip (E7/E8) SPEF 3A2 index 101 I> alarm (E3/E4) index 103 I0> alarm (E7/E8) index 105 di> alarm (E11/E12) As a presumption, these modules are using TS2 as the indicator of latched output. 170

171 1MRS MicroSCADA Pro SYS If there is no appropriate protection module to pick or if freely defined process objects are going to be used, it is possible to link those objects by using the following syntax: "ID","I1","R1","I2","R2","I3","R3",... ID = module ID - (used only as a comment) I1 = DB index of latch indication object R1 = representation (symbol set) for latch indication I2 = DB index of trip indication object 1 R2 = representation (symbol set) for object 1 I3 = DB index of trip indication object 2 R3 = representation (symbol set) for object 2 If the module does not support sending of an event of a latched output relay, the vector element I1 has been left as an empty element, that is " ". As an example, non-directional overcurrent and neutral earth-fault of REF 54x feeder terminal: "REF54x","","F_REPR/F_LATCH1","1","F_REPR/F_TRIP3",- 60","F_REPR/F_TRIP11" The type designation of the protection module x (x=1..5) is not necessary, if there is no logical name for the protection module in question. LINE_INDICATOR_COLORED_BY A selector type of combo box to select the color of line indicator. The line indicator can get its color either from DMS 600, Network Topology Coloring or by manual settings. ADD_CAUSE_IX An ADD_CAUSE_IX attribute of the AddCause feature is defined in the standard function configuration. The ADD_CAUSE_IX value is the index of a process object that contains an AddCause value. The AddCause feature is informative, that is the AddCause process object value does not prevent an execution operation. Values 0, , and have a descriptive text for AddCause, otherwise a number is displayed as a description. Assuming that the AddCause value is 1001, the following text is shown if the AddCause value changes after the selected operation: Control failed: Not supported (1001). Assuming that the AddCause value is 1020, the following text is shown if a descriptive text is not available: Control failed: The value 0 is also considered as an error: Unknown state. 171

172 172

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

174 SYS MicroSCADA Pro 1MRS Connecting signals The data variable properties can be edited by selecting Edit >Data Variables, see Fig Usually, the Object Browser tool generates automatically the data variables for those symbols that are dragged to the display from the object browser tree, and connects the symbol to the variables. Sometimes it is necessary to edit these settings manually. In the data source settings, the application number can be set to all data variables that exist in the data source. This makes it possible to create more than one data source in the same picture and define the application for them separately. Fig Creating data source in Data Selection dialog A To create a data source manually: 1. Select Edit > Data Variables to open the Data Variables dialog. 2. Select MicroSCADA from the New Data Source drop-down menu and click the Add New Data Source button. 3. Under the Data Source Settings field, select the application number from the Application drop-down menu and click Apply. This application number is applied to all data variables that are created under this data source. 174

175 1MRS MicroSCADA Pro SYS The data variable properties contain settings for the data variable name, type and scope. Type Float can be used for all signal types. The scope should normally be private. The public scope can be used if the edited view is used as a subdrawing in other displays, and the variable value has to be accessed in the parent display. Fig Creating data variables A To create data variables manually: 1. Select the MicroSCADA data source from the data source hierarchy and click the New variable button. 2. Define the data variable settings under the Data Variable field. These settings are related to a so called view data variable that is visible to view. Set the type to Float and scope to Private. Data variables can also be created with vector and matrix data from MicroSCADA. To create data variables with vector and matrix data: 1. In Display Builder, Open Edit -> Data Variables. 2. Create a MicroSCADA data source and connect it to an application. 3. Create a data variable to MicroSCADA data source. 4. Give an object reference in MicroSCADA data variable settings. 5. Select Generic signal as variable type. 175

176 SYS MicroSCADA Pro 1MRS Select Create and edit new file... in Run SCIL combo box. 7. Modify the result value. 8. Press Apply button. Shape options are activated in Data Variable group. 9. Select vector or matrix shape. For vector data source, Length setting is activated. For matrix data source, rows/cols setting is activated. 10.Type appropriate length or row/column value. 11.Create a graph object and select Graph Properties from context menu of the object. 12.Select suitable type from Types tab sheet of Graph Properties window (e.g. surface type for matrix). 13.Connect the graph to data variable and set suitable range in Variables tab sheet. When matrix data type is used, data must be a vector set. Each inner vector represent one column. For example, when defining matrix that has two rows and three columns, it is represented following way: VECTOR(VECTOR(1,2),VECTOR(3,4),VECTOR(5,6)) As SCIL code this would be #modify L_INPUT:V=LIST(VALUE=VECTOR(VECTOR(1,2),VECTOR(3,4),V ECTOR(5,6))) #RETURN %L_INPUT.VALUE Following example returns vector of length 3: #modify L_INPUT:V=LIST(VALUE=VECTOR(1,2,3)) #RETURN %L_INPUT.VALUE When an OPC item with vector data type is used to launch SCIL code, the VALUE attribute is not created in %L_INPUT, and %L_INPUT. DATA_TYPE value is "NONE", therefore it can not be used as an argument. Instead, create the value with SCIL, this way it can be passed to data variable. Only numerical items are supported in the vector and matrix data. To connect the data variable to the process database: 1. Under the Data Variable Settings field, type the process object reference in the Object Reference text field. The format is <process object logical name>:p<process object attribute><process object index>. For example, ESTH01_Q0:POV10. Note that the object reference must be typed in upper case letters. 2. Select the Type of Variable, refer to Section Data variable types. 3. Click the Validate button to check that the name was typed correctly and the process object exists, see Fig

177 1MRS MicroSCADA Pro SYS Fig Validation notice for existing process object ResultOfValid 4. Click Apply to save the settings Data variable types The type of the data variable is selected from the Type of Variable drop-down menu. Three types are available: State indication Status color Generic signal The state indication is used for integer state values. There is a possibility to swap values 1 and 2. If the signal value read from the process object is for example 1, it can be changed to 2 and written to the view data variable. The status color is used when the data variable should represent the status color value for the symbol. Internally this is done by subscribing several process objects attribute values from the OPC Server, and the status color is calculated based on the attribute values. Some attribute values are also subscribed from other process indexes, such as values for command event, selected on monitor status and control blocked signal. These values are subscribed from indexes <current index> + 10, <current index> + 9,<current index> + 3, respectively. When the Generic signal is used, no type conversion is done when moving data from the OPC Server to the data variable. This variable type can be used with measurement values and other floating point data types, or text values Customizing used process object indexes It is possible to configure the process object indexes that graphical symbols use to indicate status colors. The status colors are based on the following process object values: State indication object The data source uses object s attributes to define the device s state, for example object state, blockings and alarms. Command event object The data source uses the OV attribute of the object to define if the device is selected for the operation. Selected on monitor object The data source uses the OV attribute of the object to define if the control dialog is open for the device in another monitor. 177

178 SYS MicroSCADA Pro 1MRS Control blocked object By default, the index is set to 13. Data source uses the UB attribute of the object to define if the control is blocked. To configure the indexes, modify the SA_LIB_INDEXES attribute contents to the standard function configuration list that is located on the attribute CD. The attribute CD is located on the process object group of the standard function in Object Navigator. Run the rescan function to update the changes to the Process Display as described in the following. For example, if the SA_LIB_INDEXES attribute is added to the standard function configuration, the attribute sets the command event index to 20, the selected monitor index to 19 and the control block index to 13: SA_LIB_INDEXES="20,19,13" Object configuration files can be found on \sc\apl\<application name>\pobjconf. After the SA_LIB_INDEXES attribute is created or changed to the configuration file, update the Process Display. The Process Display can be updated with Display Builder as follows: 1. Select Edit > Data Variables to open the Data Variables dialog. 2. Select the appropriate data source on the left pane. See Fig Click Rescan in the Data Source Settings field both to scan the configuration files and to update and save the index configurations to the picture, see Fig

179 1MRS MicroSCADA Pro SYS Fig Rescanning configuration files and updating and saving index configurations 4. Ensure the indexes were updated correctly, see Fig Select a data variable on the left pane which type is Status Color. The variable type can be seen from the Type of Variable drop-down menu in the Data Source Settings field Used indexes are displayed under the Used indexes field. Point to the Used indexes field to display the semantics as a tool tip. Changes do not take effect before clicking Rescan and saving the picture in Display Builder. A

180 SYS MicroSCADA Pro 1MRS Fig Ensuring that data variables are updated correctly A Configuring status signals A status signal can be connected to an other process object than the indication signal. For example, the status signal is read from index 110 in the ANSI enviroment. Control dialogs use the index automatically for switch devices with the ANSI protocol. To take the feature in use in another protocol, define an object type that has the STATUS_IX attribute defined. Object types can be found on \sc\sa_lib\defaults\object_types. The object type is saved in this directory as a text file with a.dat extension. File contents is a dump list containing the attributes, for example LIST(STATUS_IX=110). To take the object type in use, define the LIB_OBJECT_TYPE attribute in the standard function file. The attribute value is an object type file name with the file name extension and without path, for example ANSI.DAT. Standard function files can be found on \sc\apl\<application name>\pobjconf. 180

181 1MRS MicroSCADA Pro SYS Customizing Object Browser Object Browser displays objects that can be inserted as a symbol to the Process Display, see Fig Insertable objects are defined in the Object Browser configuration file. The configuration file is located in [drive]\sc\prog\graphicsengine\ etc\objnav.ini. The file contains settings related to Object Browser and mappings between the process objects and the symbols. Table shows the possible options for the Object Browser configuration file. A substring field of the RX attribute identifies process objects. By default, the substring consists of characters of the RX attribute value. Example QB01 = 02 - SA_IEC\Breaker.sd 02 - SA_IEC\Breaker H.sd 03 - SA_ANSI\Breaker.sd 03 - SA_ANSI\Breaker H.sd The example above defines the process object that have the QB01 string in the RX attribute. The process object is used in the following subdrawings: 02 - SA_IEC\Breaker.sd 02 - SA_IEC\Breaker H.sd 03 - SA_ANSI\Breaker.sd 03 - SA_ANSI\Breaker H.sd Subdrawings are displayed in the Selected object list, see Fig Table Options for the Object Browser configuration file Setting group Key name Description [Options] UsesReversedSingleIndications Swaps values 1 and 2 for double state indications. (0 = No swap, 1 = Swap) [Options] IxFilter Includes process objects with a certain IX value. (0 = not used, <n> = only include this IX value) [Options] IxMax Excludes process objects with IX value greater than a certain value. Useful for skipping LIB 510 event recording objects that all have IX > 100. (0 = not used, <n> = Skip objects with greater IX) [Options] IncludeAllIndicesForRxValues Shows all IX values for certain RX values even if they do not qualify the IxFilter value, objects with IX > IxMax are still excluded though. The RX values are separated with the colon, for example PMEA:ABAY:GHRE. White space, excluding spaces, between the separators and RX values are included in. 181

182 SYS MicroSCADA Pro 1MRS Table Options for the Object Browser configuration file (Continued) Setting group Key name Description [Options] LocalRemoteSwitchRxValues The RX values for local/remote switches. The RX values are separated with the colon, for example ASTA:ABAY. White space, excluding spaces, between the separators and RX values are included in. [Options] EarthingSwitchRxValues The RX values for earth switches. The RX values are separated with the colon. White space, excluding spaces, between the separators and RX values are included in. [Options] EarthingSymbolSubdrawing Subdrawing for earth symbol is created under the switch symbol when an earth switch object is created. H.sd replaces the last 3 characters, if the horizontal switch symbol is created. [Options] ExcludedRxValues The RX values that is not included. The RX values are separated with the colon, for example ASTA:ABAY. White space, excluding spaces, between the separators and RX values are included in. [Options] ExcludedRxValues The RX values that is not included. The RX values are separated with the colon, for example ASTA:ABAY. White space, excluding spaces, between the separators and RX values are included in. [Options] UsePtSpecificMappingRxValues The RX values that use the PT specific mapping. _<PT> is added to the RX key. The RX values are separated with the colon, for example ASTA:ABAY. White space, excluding spaces, between the separators and RX values are included in. 182

183 1MRS MicroSCADA Pro SYS Table Options for the Object Browser configuration file (Continued) Setting group Key name Description [Options] ExcludeLNsStartingWith Excludes all LNs that start with the certain substring. The LN values are separated with the colon. White space, excluding spaces, between the separators and LN starting substrings are included in. [Options] IncludedSpecifiedIndicesForRxValue Always includes the specified indices for the specified RX values. Also when the indicies > IxMax. Example syntax: RX1#Index1,Index2,Index3 : RX2#Index1 : RX3#Index4,Index6 White space, excluding spaces, between the separators and LN starting substrings are included in. [Options] ExcludedStValues The ST values that is not included. The ST values are separated with the colon. White space, excluding spaces, between the separators and the ST values are included in. [RX_Settings] StartIndex Specifies the start position of the substring in the RX attribute value that contains the object type. [RX_Settings] Length Specifies the length of the substring in the RX attribute value that contains the object type. [RX_Mapping] <any key name> Key name is RX substring. Key name format: <RXkey[_<PT>]> = <Subdrawing file path>[: <variable mapping>] { <Subdrawing file path>[: <variable mapping>]} For more information about the fields, refer to the Table White space, excluding spaces, between the separators are included in. Table Field RXkey Field description Description The part of the RX attribute used to identify the object (subdrawing) type. Specified in RX_Settings. If the RXkey is included in UsePtSpecificMappingRxValues, _<PT> is added to RXkey. PT <PT> is the PT attribute value and the PT attribute is the process object. Subdrawing file path The subdrawing s path relative to the Palette directory 183

184 SYS MicroSCADA Pro 1MRS Table Field Variable mapping Field description (Continued) Description Optional, a string specifies the variables to be created for the subdrawing, default value is SC. Each character in the string specifies the data variable type for the corresponding variable mapping of the subdrawing. Possible characters S = state indication signal/variable C = status (color) signal/variable G = Generic (measurement) signal/variable If other characters are used, the variable is not created for the variable mapping index. To ensure the compability wit the newer extensions, use - for indicating missing variable. Specify the process object index for each data variable, either directly or relatively to the selected process object index. If the process object index is not specified, the selected process index is used. Syntax: TypeChar[index] TypeChar[+inc_index_with_this] where TypeChar is the type character. Examples: "SC" - The first variable mapping is state indication, the second is color signal. "GC" - The first variable mapping is generic signal, the second is color signal. "G" - The only variable mapping is generic signal. "C" - The only variable mapping is color signal. "-C" - The first variable mapping is empty, the second is color signal. "" - Same as "SC". "SCS[20] - Uses 20 as index for the third variable. "SC[+1]GC - Increment the selected index with 1 for the first color signal. Example contents of objnav.ini: [Options] UsesReversedSingleIndications=0 UsesReversedDoubleIndications=1 IxFilter=10 IxMax=99 IncludeAllIndicesForRxValues = PMEA LocalRemoteSwitchRxValues = ASTA:ABAY EarthingSwitchRxValues = QE01:QE02:QE03:QE04:QE05:QE06:QE07:QE08:QE09:QE10 EarthingSymbolSubdrawing = 01 - SA_Common\Earth.sd ExcludedRxValues = WAPL:WNET:WPRI:WSTA:WSYS:WOSY:ASYS:ESYS:PCOS:Q301:FMFU:MFUI:WMFU:FARC:HALA UsePtSpecificMappingRxValues = ASTA:ABAY:FARC ExcludeLNsStartingWith = BNCC:SAGR_:TOPO_ IncludedSpecifiedIndicesForRxValue = HTCI#255 : XRST#10000 : QT01#30 : FARC#12 : HALA#10,11,12,13,14,15,16,17 ExcludedStValues = IN_COLOR [RX_Settings] StartIndex=23 Length=4 [RX_Mapping] ABAY_12= 04 - SA_Indication\Bay.sd ASTA_12 = 04 - SA_Indication\Station.sd ABAY_3 = 04 - SA_Indication\Bay BI.sd ASTA_3 = 04 - SA_Indication\Station BI.sd FARC_3 = 04 - SA_Indication\Auto-Reclosing BI.sd : G 184

185 1MRS MicroSCADA Pro SYS FARC_9 = 04 - SA_Indication\Auto-Reclosing.sd : G QB01 = 02 - SA_IEC\Breaker.sd 02 - SA_IEC\Breaker H.sd 03 - SA_ANSI\Breaker.sd 03 - SA_ANSI\Breaker H.sd QE08 = 02 - SA_IEC\Disconnector.sd 02 - SA_IEC\Disconnector H.sd 03 - SA_ANSI\Disconnector.sd 03 - SA_ANSI\Disconnector H.sd QI01 = 02 - SA_IEC\Breaker.sd 02 - SA_IEC\Breaker H.sd 03 - SA_ANSI\Breaker.sd 03 - SA_ANSI\Breaker H.sd QL01 = 02 - SA_IEC\Load Breaker.sd 02 - SA_IEC\Load Breaker H.sd 03 - SA_ANSI\Breaker.sd 03 - SA_ANSI\Breaker H.sd QM01 = 02 - SA_IEC\Breaker.sd 02 - SA_IEC\Breaker H.sd 03 - SA_ANSI\Breaker.sd 03 - SA_ANSI\Breaker H.sd QS01 = 02 - SA_IEC\Breaker.sd 02 - SA_IEC\Breaker H.sd 03 - SA_ANSI\Breaker.sd 03 - SA_ANSI\Breaker H.sd PMEA = 05 - SA_Measurement\Value.sd : GC 05 - SA_Measurement\Bar Graph.sd : GC 05 - SA_Measurement\Line Graph 20 Samples.sd : GC TAVR = 02 - SA_IEC\Transformer2w.sd : GCC 02 - SA_IEC\Transformer2w H.sd : GCC 03 - SA_ANSI\Transformer2w.sd : GCC QT01 = 01 - SA_Common\Truck.sd 01 - SA_Common\Truck H.sd HMTC = 01 - SA_Common\Line Indicator.sd : G 01 - SA_Common\Line Indicator H.sd : G FTRP = 04 - SA_Indication\Tripping.sd : C HTCI = 01 - SA_Common\Generator.sd : G XRST = 01 - SA_Common\IED.sd : HALA = 04 - SA_Indication\Alarm Led.sd : C 04 - SA_Indication\Alarm A.sd : C 04 - SA_Indication\Alarm Bell.sd : C 04 - SA_Indication\Alarm Star.sd : C 7.5. Network topology coloring The larger network topology is called network overview. The network overview is a large geographical area displayed in a large Process Display. Inner networks of the network overview are sub areas of a larger area. The system contains a realistic status information both in network overview and inner networks. Furthermore, the information displayed in both networks is consistent. It is possible to have the whole network displayed in a single Process Display. The operator can select and zoom areas, for example the inner network. Having a network in a Process Display is not flexible to use, because it is awkward to zoom and browse large Process Displays. It is recommended to divide the network overview to separate networks that can be opened in separate windows. The network overview is used for calculating status information for network objects and line segments. The status information can be read from line segments or from connectivity points. Connectivity points are placed to bind to the network overview. The network topology coloring system is a general application in software that is used to display the network s status, see Fig and Fig The system consists of a server that calculates the network s status. Clients use the server to have access to the network data. Network topology coloring in the SYS 600 Monitor Pro can be used to indicate the status of the line segments in several different ways. It can indicate which line segments are powered, unpowered or in certain other states, and also which level 185

186 SYS MicroSCADA Pro 1MRS each line segment has. Alternatively, each feeding point type can have a color that is used for the line segments they are connected to. Network topology coloring can also be used to indicate situations where feeding points form a loop. The status colors can be configured. A Process Display is a graphical user interface for presenting an area of the network. Network topology consists of network objects and connections between the network objects, that is line segments. The network topology coloring system supports various systems such as heating, and telecommunication networks. Feeding points in these systems can be pumps, routers, and generators. Network topology contains: Switching device Line segment Feeding point Line indicator Transformer Fig Process Display with network topology coloring A

187 1MRS MicroSCADA Pro SYS Fig Process Display with static network topology coloring A To enable network topology coloring in Monitor Pro, the following information must be saved in the display file. Voltage level information must be specified for all line indicators, transformers and generators in the display. Supported voltage levels are listed in the SYS 600 Process Display Design manual. The levels are given by mapping the following data variables to constant kilovolt values: Line indicators: Voltage Level (kv) 2-Winding transformers: Primary Voltage Level (kv) and Secondary Voltage Level (kv) 3-Winding transformers: Primary Voltage Level (kv), Secondary Voltage Level (kv) and Tertiary Voltage Level (kv) Generators: Voltage Level (kv) Mapping is done by activating a symbol and then selecting Object > Properties. Select the Subdrawing tab from the appearing dialog. Set Mapping Type to Map to Constant, and enter the value in the Is Mapped To column. 187

188 SYS MicroSCADA Pro 1MRS Fig Mapping voltage level of line indicator to 110 kilovolts A All graphical objects that are part of the network topology coloring topology must have a unique identifier and information on which objects they are connected to. When an object that can be part of the topology is created, the identifier is given automatically and stored in the value of the object specific custom attribute key SAObjectName. By default, all graphical objects that can be part of the topology are also given custom attribute keys to store in the information on the connections. These keys are named NextObject1, NextObject2, and so on depending on how many connections each symbol can have. If the keys do not exist, create them by selecting Actions > Add Selected Objects to Topology. The values for the keys can be specified manually or generated automatically by selecting Actions > Build Topology. Each value contains an SAObjectName, colon, and number of the location (Hotspot) which the object is connected to. If the exact location cannot be given, 0 is used. Topology details can be viewed one by one by activating an object, selecting Object > Properties and selecting the Custom tab, or all in one by selecting Actions > Topology Information. 188

189 1MRS MicroSCADA Pro SYS A Fig Topology information of SA symbols in bay All dynamic objects that are part of the topology must have an ID of the data source item, because they are mapped to the stored in value of the custom attribute key OPCItemID. The keys and values are generated automatically from the data variable mappings when the display file is saved. Check that the primary winding of a transformer is connected to the primary side of the topology. In addition, be careful when connecting line segments to the main and reserve busbars from the bay. Verify that line segments "jump" to the correct busbar. Start new line segments in crossing points. The loop indication is displayed better when using multiple line segments instead of a long line Switching device A switching device is a special object in a network. The switching device has a certain position. This position has values open, closed and uncertain at least. Furthermore, the uncertain position has intermediate or faulty value. The position determines whether or not to flow the status through the device to the next vertex. The position also has a quality tag that has good, bad or uncertain value. If the bad or uncertain quality occurs, the switching device s position is set to intermediate or faulty Line segment Line segment has at least statuses on and off, for example, powered and unpowered, or active and inactive. Two or more line segments can be connected to each other. Each line segment knows its neighbors. 189

190 SYS MicroSCADA Pro 1MRS Feeding point Line indicator The network has at least one network object, where the feeding is started. The object is called a feeding point. The feeding point can be a generator in power systems, a water pump in heating systems, or a router in telecommunication systems. Normally, the feeding point has a process connection to a real-world object and its status can be active or inactive. For example, if the water pump is inactive, it is not pumping. A Line indicator is a network s general feeding point. A line indicator can be incoming (active) or outgoing (inactive). The positive value determines the incoming line indicator, and the negative value determines the outgoing line indicator. The zero value is an undefined value. A incoming line indicator is generally a feeding point with powered/active state in the network Transformer A Transformer converts a measurement value level to another. A transformer is a bidirectional, one-to-many and many-to-one device. A transformer has primary and secondary sides. The primary side has one level and the secondary side can have several levels. If the flow of powered state comes from the secondary side and the line segment is connected to the primary side, a level is configured to the primary side. If a flow of powered state comes from the primary side and the line segment is connected to a location on the secondary side, a level is configured to that location. For example, a transformer takes a unit with value 20 in the primary side (input) and the transformer reflects secondary side values 6 and 10 (outputs) to line segments connected to places on the secondary side. If the flow comes from an other location on the secondary side, the value 20 reflects to a line segment connected to the primary side Network topology coloring modes The network topology coloring is enabled if it uses the dynamic coloring. The network topology coloring is disabled if it uses the static coloring. 1. Disabled network topology coloring If the network topology coloring is disabled, switching device s position does not affect the network topology coloring. Therefore, a static foreground color is used for objects in a Process Display. It is possible to use the configured foreground color or the original color defined in Process Display Builder. 2. One color for all powered line segments Define color called Powered that is used for all powered line segments. 3. Coloring based on level 190

191 1MRS MicroSCADA Pro SYS In a level-based network topology coloring, a feeding point has a level, for example a voltage level. After the feeding point, a level color applies to the network s powered line segments. 4. Feeding point type and its color determine coloring of powered line segments There are predefined colors for feeding points in SYS 600. In SYS 600, feeding points are voltage sources such as generators, transformers, and incoming line indicators. A priority order of the feeding point type is applied for this mode. 5. Customized feeding point colors Define feeding point colors in Process Display Builder by setting a custom foreground color for line indicators. Foreground colors are determined by using the value of the data variable Position in the line indicator. The valid values are shown in Table Table Valid foreground color values Color Values Unpowered 0 Powered 1-5 Uncertain 11 Looped 12 Earhed Used states and colors States used in network topology coloring are defined in Table Configure the state s color by using the Color Setting tool, refer to the Process Display Design manual. The network object can have one of the following states: Powered Unpowered Looped Uncertain Error Earthed Table States and colors Color name Description Color Earthed The object is connected to ground. Yellow Error The color is used in error situations. For example, powered line Magenta segment is earthed. Looped (meshed) The color is used when two or more feeding points form a loop. Red Powered/active, common Default color used on powered objects Green Powered, generator Color used for line after generator Green Powered, incoming line indicator Color used for line segment after line indicator Green Powered, transformer (primary) Color used for line segments when power flows to transformer Cyan primary winding side Powered, transformer (secondary) Color used for line segment after transformer secondary winding Dark Green Powered, transformer (tertiary) Color used for line segment after transformer tertiary winding Olive Green 191

192 SYS MicroSCADA Pro 1MRS Table Color name Description Color Powered, custom 1-5 Reserved for future development Several colors Green Uncertain The state of a switching device Magenta Unpowered/inactive Line segment is cold, no power flow. Light Grey Level colors Line segments (Network topology coloring disabled) States and colors (Continued) Colors that are used for level based coloring. For example, possible voltage levels in kilovolts (kv): 0, 3, 6, 10, 15, 20, 30, 45, 66, 110, 132, 150, 220, 300, 362, 400, 420, , 1050, 1200 and One color used for all line segments when network topology coloring is disabled. Color priorities In the network, situations can arise where a line segment can have two or more colors that could be used in the line segment, for example, uncertain and looped color. A default priority order of colors are shown in Table Some of the priorities are not configurable and you can only configure priorities of feeding point types. Table Color priority order State Priority Configurable Description Network topology coloring system The Network topology coloring (NTC) system has two configurations: Several colors Green Black Error 1 NO Uncertain 2 NO The used color after uncertain switching device. Looped 3 NO Earthed 4 NO Earthed color is always indicated before and unpowered. Powered, feeding line 5 YES The priority of a feeding point type Powered, generator 5 YES Powered, transformer, windings (primary, secondary, tertiary) 5 YES color in powered line segments is configurable. Functionality can be seen in the line segments, which are looped. The coloring mode must be set to feeding point or voltage source type to enable priorities. Unpowered 5 NO Powered and unpowered objects have lowest priority Client-server communication - the server calculates the network states and the client runs the coloring process, and Fat client - the client calculates the network states and runs the coloring process and does not communicate with the server. 192

193 1MRS MicroSCADA Pro SYS Fig Network topology coloring (NTC) system Network topology coloring system consists of a set of applications, as shown in Fig With SYS both client and server application are run on the same host. The applications availble are: Network Topology Coloring Manager (NTCManager.exe) Manages the starting and stopping of NTC servers according to the status of SYS 600 Service. Network Topology Coloring Manager Proxy (NTCStarter.exe) This application is executed every time MicroSCADA application goes hot or cold. It connects to and requests NTC Manager to start and stop NTC server for the application. 193

194 SYS MicroSCADA Pro 1MRS Network Topology Coloring Server Application - (NTCServer.exe) The NTC server application is responsible for calculation of network overview file and providing network status information to client applications. By default, there is no NTC Server running for the application. The network overview file must be built and set using Display Builder, see Section 7.6. Building network overview. Network Topology Coloring Client Application - (FrameWindow.exe SYS 600 Monitor Pro) The client application is responsible for connecting to the NTC Server Application and providing colors according to network status and network topology coloring settings. If the server is not available, the client application calculates the network. Client-server The client application (SYS 600 Monitor Pro window) uses the NTC server to get network status. The network overview file has to be configured for the server application before this communication model is used. To verify that the network topology coloring client is operating in client-server communication, open the Network Topology Coloring Settings dialog, as shown in Fig Network topology server is running and Network topology is found from the server are displayed. If the network overview is not correctly configured, the system automatically switches to the fat client calculation. The Network Topology Coloring Settings dialog will display Network topology not found from the server. This means that network topology colors are calculated by the client application using the process display open at the time. Fat client Fat client performs network calculation and coloring itself and the process display opened in Monitor Pro does not have connection to upper or lower networks. When network topology coloring server is not running for the application, the system automatically uses fat client to perform calculation. To verify that the network topology coloring client is a fat client, that is, calculating the process display itself, open the Network Topology Coloring Settings dialog, as shown in Fig Network topology found from the server will be displayed. Note that the server may still be running Building network overview A network overview can be divided to smaller networks as described in Section 7.5. Network topology coloring. The network can be displayed as a larger Process Display containing the whole network or as smaller Process Displays containing a part of the larger network. This section describes how the information can be consistent in different Process Displays and how the subnetworks are connected to the network overview. Start building the network overview by creating the subnetworks and adding them to the network overview. 194

195 1MRS MicroSCADA Pro SYS Each subnetwork refers to the network overview. Changes made in the subnetwork change also the network overview display. To build the network overview: 1. Build a Process Display for a small geographical area, for example for a station. 2. Connect a line indicator symbol to a line segment that is to be connected to a larger network. 3. Uniquely identify the subnetwork name by setting a custom attribute for the process display 3.1. Create attribute SADisplayName by selecting View > Properties > Custom Attributes Name the Process Display with a unique name. 4. Select Actions > Batch Operations > Enable Mouse Click > To all objects to enable the control dialogs and the shortcut menus in the overview display. For more information about mouse click, refer to Process Display Design. 5. Select Actions > Build Topology to build the topology for the subnetwork and save the Process Display as a V file To confirm a valid topology, select Actions > Topology Information Repeat steps 1. to 5. until the large network is divided into small enough Process Displays. 7. Create a new Process Display used as a network overview. 8. Embed the small Process Displays in the large Process Display as objects or symbols Select Objects toolbar > Subdrawing Open a V file to embed a Process Display as an object or a symbol. 9. Repeat step 8. for each Process Display that is required to be embedded in the network overview. 10.Connect the small Process Displays to the network overview by using Network Connecting Busbars Create a Network Connecting Busbar symbol Use the snap-to-symbol function to connect the symbol to the line indicator of the small Process Displays Continue building the network overview with the normal busbars. 11.Select Actions > Build topology to build the topology for the network overview. 12.Uniquely identify the network overview by creating a new attribute SADisplayName by selecting View > Properties > Custom Attributes and setting the value, for example, Overview. 13.Save the V file. 14.Select Actions > Network Topology Coloring > Use Display as Network Overview to set the large Process Display to be used as a network overview. 15.Select Actions > Network Topology Coloring > List Network Overviews to confirm that the large Process Display is used as a network overview. 16.Login again to Monitor Pro to make the new setting take effect To verify the successful configuration: 195

196 SYS MicroSCADA Pro 1MRS Login to Monitor Pro 2. Open the network overview display 3. Select Tools > System Tools > Network Topology Coloring..., see Fig Verify the status for the server and the topology 5. Network Topology Coloring Server running for the application 6. Network topology found from the server 7. Open one of the small process displays being part of the network overview and repeat steps 3. and 4. Fig Network Topology Coloring Settings dialog indicating server-client configuration 196

197 1MRS MicroSCADA Pro SYS Fig Network Topology Coloring Settings dialog indicating fat client configuration Embed the small Process Displays as described above. Unique identifications for network objects are lost if a display is embedded in the network overview display as described in Section 7.9. Alternative building of network overview. You can create a Process Display where you can make references to line segments and line indicators in the network overview. Do not set the SADisplayName attribute for this Process Display. Example 1. Create a line segment. 2. Select Object > Properties. 3. Select the Custom tab. 4. Set the value of the attribute SAObjectName to format <SADisplayName>.<SAObjectName>, where SADisplayName is the name of the subnetwork in the network overview, for example Rivendell.Section42. See Section Troubleshooting Network Topology Coloring Removing the network overview configuration You can completely remove the connection between the MicroSCADA application and the network overview display. This will inform the network topology coloring system not to use network topology coloring server for the application. 197

198 SYS MicroSCADA Pro 1MRS For the current network overview display in use, open Display Builder and select Actions > Network Topology Coloring. Use as network overview menu should be checked. Select Use as network overview menu. Verify the removal by selecting Actions > Network Topology Coloring > List Network Overviews. No network overview file configured will be reported Troubleshooting Network Topology Coloring This section gives some solutions for common problems in client-server based system and in network topology coloring. To verify correct configuration, use Network Topology Coloring Settings dialog to see if network topology server is running and the network topology is found from the server. In correctly configured client-server based system there are at least two processes running in the machine: NTCManager.exe and NTCServer.exe. Table Network Coloring Topology troubleshooting Problem Reason Solution Network topology coloring server is not running for the application The application may not have a network overview display configured. Open Display Builder and select Actions > Network Topology Coloring > Use Display as Network Overview for some network overview display. Select Actions > Network Topology Coloring > List Network Overviews to verify that setting succeeded. Login to Monitor Pro and select Tools > System Tools > Network Topology Coloring... to see that the server is running for the application 198

199 1MRS MicroSCADA Pro SYS Table The network topology coloring server is running but the network topology is not found from the server Network topology coloring is working in the process display but there is no network topology coloring server running for the application The server is running and the topology is found but some sub-network does not have correct information Network Coloring Topology troubleshooting Problem Reason Solution There may be several reasons for this: 1. The display opened in the Monitor Pro might not be a part of the network overview. 2. The display opened does not have unique name (SADisplayName). 3. The display opened contains at least one symbol (network object), which does not exist in the network overview. 4. The display hierarchy is too deep, that is, there are several nested displays. The network topology coloring system is not using client-server communication. The client application, that is SYS 600 Monitor Pro, is performing calculation and coloring by itself. The network overview is not configured for the application The line indicator connecting sub-networks in the network overview display is not connected correctly with network connecting busbar. 1. Verify that the process display is part of the network overview. If not, see Building network overview. 2. To set SADisplayName, see Building network overview. Note, the SYS 600 Service must be restarted. 3. See the latest items in the log file:..\sc\<apl>\apl _\NTCServer.log 4. Verify that network overview display contains only process symbols and V files that do not contain other V files. See Building network overview to configure network topology coloring system to use network overview file. Open network overview display in Display Builder. Verify that the busbar connected to the line indicator of the subnetwork has at least two custom attributes NextObjectX (where X is a number) and one has value <SADisplayName of subnetwork>.nodex 199

200 SYS MicroSCADA Pro 1MRS Table When using measurement values in the line indicator for determining incoming/ outgoing line indicator and measurement value quality feature is enabled, uncertain color is always propagating from the line indicator. NTCManager.exe process running even if SYS 600 Service is shutdown. Network Coloring Topology troubleshooting Problem Reason Solution There might be line indicators in the process displays that are instantiated using Display Builder's Object Browser, i.e., the user has installed a standard function Line Indicator a.k.a. MicroTopology Pen, which has the switch state set to value Fictive. In this case, line indicators might not be updated by any component, e.g. DMS 600. This means that the quality for these line indicators is always bad. Line indicator symbols do not indicate any error in this situation 1. Network Topology Coloring Manager is shutdown from..\sc\proc\exec \shutdown.cin. The file is not updated automatically by the installation. The reason might be that the latest shutdown.cin file is not in use. 2. SYS 600 Service was Forced shutdown Process values mapped to Position attribute of the line indicator must be reset using MicroSCADA Object Navigator: 1. Select Object Navigator > Process Objects 2. Select Options > View in Table 3. Set filter RX==" BCHMTCXFCD" 4. Select in User-defined combo box: SS 5. Select all objects, right-click, Edit 6. Set new value to Manual 1. Verify that..\sc\proc\exec \shutdown.cin contains the line where NTC Manager is shutdown. If the line does not exist, the latest shutdown.cin file is not used. The latest version is..\sc\proc\exec \ shutdown$cin. 2. MicroSCADA base system does not call shutdown.cin None of the above none The log file of NTC Server Application may give more information, see..\sc\<apl> \APL_\NTCServer.log. 200

201 1MRS MicroSCADA Pro SYS Status information A large network is a subnetwork in a larger network, therefore a status information is missing that is coming from the outer network. You can solve the problem in the following ways: Use external color handling for voltage sources provided by DMS 600 Use an additional circuit breaker and earth switch Use measurement values Using external color handling This scenario is suitable in systems where: DMS 600 is installed the network is larger than the used network in SYS 600 To color the line indicators with the status information received from DMS 600: 1. Select Tools > System tools > Network Topology Coloring in Monitor Pro 2. Select the Coloring modes tab. 3. Select External handling for voltage source colors. 4. Click OK Additional circuit breaker and earthing switch This scenario is mostly suitable in electric networks. An additional circuit breaker and an earthing switch can be used after an incoming line indicator. The devices can be virtual or real. In this scenario, virtual devices are created. These two switches simulate the state of the upper level network enabling to simulate all the states that a feeding line may have, except the looped state. 1. Open Tool Manager > Object Navigator. 2. Select Object > Install standard function. 3. Browse for Standard Functions/SA_LIB/Process/Switching Device and click Install. 4. Fill in STATION_NAME, BAY_NAME, DEVICE_NAME and P_OBJECT_NAME. 5. Click Apply. 6. Open Process Object Tool from the Tools tab. 7. Click Create All. 8. Repeat steps to create more virtual circuit breakers. 9. Use Object Browser in Display Builder to create symbols to the station Process Display. It is recommended to separate virtual circuit breakers from the station picture. An example of an earthed upper level network (Rivendell 110 kv) is shown in Fig

202 SYS MicroSCADA Pro 1MRS Fig Example of an earthed upper level network UpperLevelProblem_VirtualCircuitBreakers Using measurement values Generally, measurements can be used to control the direction of the line indicator (incoming/outgoing, or powered/not powered, respectively) from the transmission network. Map a measurement value to the Position data variable of the line indicator. The attribute's positive value indicates the powered state and the negative value indicates the unpowered state Measurement value quality If a measurement value is not sampled, for example, the value cannot be read through the communication, the network topology coloring logic ignores the quality of the Position attribute of the line indicator. However, the quality can be enabled and taken into use with a parameter in the settings file. The purpose of this feature is to propagate uncertain state from the line indicator to adjacent line segments if, for example, current or voltage measurements are not sampled. The uncertain state is not propagated, if the quality is uncertain. This is because it would cause flickering in the process display if the communication to the process is slow. Here are the cases when the uncertain state is propagated from the line indicator: - Incoming line indicator quality goes bad, when there is no loop 202

203 1MRS MicroSCADA Pro SYS Special case: When a loop exists in the network and loop indication is enabled, the loop is no more indicated. Note that there is no other indication that the incoming line indicator now has a bad quality. Uncertain state is not propagated from the line indicator because adjacent line segments are certainly known to be powered. - Outgoing line indicator quality goes bad, when adjacent line segments are unpowered Special case: When adjacent line segments have some other state than unpowered, the state has higher priority. Adjacent line segments are certainly known to be in that state. Enabling source quality Enabling this feature is a system specific setting, and the setting value should be same both in NTC Server Application and in NTC Client Application. There are two files where the setting value has to be set:..\sc\prog\sa_lib\ntcserver.exe.config and..\sc\prog\sa_lib\framewindow.exe.config. To enable this feature set the value of EnableSourceQualityValidation key to 1 (0 to disable) in both files. <?xml version="1.0" encoding="utf-8"?> <configuration> <appsettings> <add key="enablesourcequalityvalidation" value="1" /> </appsettings> Listing. Enabling source quality to the settings file System specific files are not shadowed, modify the files also in the secondary system When this feature is enabled, there might be line indicators whose quality is always bad. For more information, see Section Troubleshooting Network Topology Coloring 7.8. Network topology coloring and different representations in same Process Display If both horizontal and vertical layouts need to be used in the same Process Display, only one Process Display can be embedded in the network overview. Select View Properties > Custom Attributes > SADisplayName attribute to set the same attribute value for the identical Process Displays that have the same uniquely identified objects but different appearances. Both displays are integrated to the network topology coloring system. 203

204 SYS MicroSCADA Pro 1MRS Alternative building of network overview This scenario is suitable for relatively small networks (a maximum of three stations due to performance). 1. Build separate Process Displays for every station. 2. Save every station to separate V files. 3. Open an empty station Process Display. 4. Embed and scale each station in an empty Process Display. 5. Select File > Merge > Data Source Name to open a station. 6. Select Object > Scale > Shrink to scale the station. 7. Move the station to its place in the Process Display. 8. Connect stations with Horizontal and Vertical Busbars after embedding the stations. 9. Select Actions > Build topology to build the topology. 10.Select Actions > Topology Information to access the information about the unconnected objects. 11.Fix the topology if needed. 12.Select File > Save to save the topology. Fig Several stations in a Process Display UpperLevelProblem_SeveralStations.tif For more information on preparing Process Displays for network topology coloring, refer to the SYS 600 Process Display Design manual. 204

205 1MRS MicroSCADA Pro SYS Launching external application from Process Displays There is a possibility to open external programs, like relay tools from the Process Displays of the SYS 600 Monitor Pro. Below there is an example of how to launch the REF542plus tool by right-clicking a relay symbol. To create a rule for opening external tools: 1. Open the properties for the selected object and select the Rules tab from the appearing dialog. 205

206 SYS MicroSCADA Pro 1MRS Create a new rule as defined in Fig A Fig Creating new rule 3. Connect to a correct script file by clicking the Create or Select a Rules Script File button. Browse the file \sc\prog\graphicsengine\etc\execute.bas. 4. When the script file s path is showing under the Script File Name, click Close. Fig Connecting to specific script file A

207 1MRS MicroSCADA Pro SYS Select Execute from the Action drop-down menu. Fig Creating action 6. Select the Custom tab. A

208 SYS MicroSCADA Pro 1MRS Add two custom attributes for the object (Executable and Arguments) by clicking the Create New Custom Attribute button. Assign proprietary strings for them. Note that if there are spaces in the strings, you have to use quotation marks as in the Fig Fig Adding custom attributes A Click Close in the Object Properties dialog. When running the Process Display, right-clicking the mouse opens the external tool Modificating data variable with SCIL Modify the data variable values by running SCIL when the process object value changes, and place the result to the data variable. It is also possible to run SCIL when data variable changes, for example when user clicks a Process Display object. Place the result to the process object. A SCIL code is located in \sc\apl\[application name]\pict\. LIST is given as a predefined variable, which name is %L_INPUT, to the code: LIST(ITEM=<Item ID of OPC item>, VALUE=<value of opc item>, DATA_TYPE=<data type of OPC item>, DIRECTION=<"READ" "WRITE">) Same SCIL file is run in both cases, when the process object value changes. The DIRECTION list attribute has value READ. when data variable value changes. The DIRECTION list attribute has value WRITE. 208

209 1MRS MicroSCADA Pro SYS When writing, the VALUE list attribute is written to the process object. When reading, the VALUE list attribute is written to the Process Display data variable. The OPC item name and data type are also passed to the SCIL code, and they are available in the ITEM and DATA_TYPE attributes respectively. To modify the data variable value when process object changes: 1. Create a Process Display. 2. Create a data variable to the data source. 3. Define process object or process index where the variable is connected to. 4. Set data variable s type to Generic signal. 5. Select Create and edit new file from the Run SCIL drop-down menu. 6. Notepad opens the created SCIL file for editing. 7. Write the SCIL code to modify the variable value and save the file. The file suffix must be scil. 8. Run the Process Display in Monitor Pro. To modify the process object value when the data variable changes: 1. Create a Process Display. 2. Create a data variable to the data source. 3. Define process object where the variable is connected to. 4. Set the data variable s type to Generic signal. 5. Select Create and edit new file from the Run SCIL drop-down menu. 6. Notepad opens the created SCIL file for editing. 7. Write the SCIL code to modify the variable value and save the file. Use the DIRECTION attribute of the %L_INPUT variable in the code to define the direction where the data is going. The file suffix must be scil. 8. Define input object that modifies the data variable value. 9. Run the Process Display in Monitor Pro. 209

210 210

211 1MRS MicroSCADA Pro SYS Event List The SYS 600 Event List provides information on events occuring in the system. Thus, you can make the right decisions and verify that the taken measures are successfully performed. It is also possible to receive information on activities carried out by other users, operations of objects, acknowledging of alarms, editing of limit values, logging in, etc. The Event List presents the data in a structured way for the user's convenience. Each event is normally presented by displaying an event text line, which describes the cause of the event in the process. Event text lines usually have an event row number, a time stamp, an object identification, a signal text, a text indicating the state and event, see Fig For more information on SYS 600 Event List functions, see SYS 600 Operation Manual. Fig Event List, main view event_list 211

212 SYS MicroSCADA Pro 1MRS In this chapter, you learn how to configure the SYS 600 Event List, that is, how to customize column layouts, event coloring and advanced condition in the preconfiguration Customizing the column layout The Event List can be configured to have column layouts, which are application or user specific. If the user specific column layout file is not located in the system, the default column layout template for the application is used. If additional attributes for events are needed, custom columns can also be created. The default column layout template for the application contains the following columns: Event row number Status columns with symbols for Alarm, Comment, Status Date Time Station Bay Device Object Text State Text Event Text Fig Default column layout for Event List elist_layout You can find the column layout template for the application in the following folder: \sc\apl\<application name>\par\apl\event. User specific column layout templates are located in the following folder: \sc\apl\<application name>\par\<user name>\event. The column layout files always use the file name layout.ini. You can manage the contents of these layout files by using the Layout Settings dialog of the Event List. 212

213 1MRS MicroSCADA Pro SYS It is possible to add the following columns to the Event List, see Table Mainly, the information source for the supported columns is either from the process database or from the history database. Table Column AB AC AG AH AL AR AS AZ BC BL CA CE CL CO CT CV DATE ED EVENT EX GT HA HB HD HH HI HM HO HT HW IU IN IX LA LI LN LO LW NV OA OB OF OI Columns for Event List Information Source Alarm Blocking (AB) attribute Alarm Class (AC) attribute Alarm Generation (AG) attribute Action on History (AH) attribute Alarm (AL) attribute Alarm Receipt (AR) attribute Alarm State (AS) attribute Alarm Zone (AZ) attribute Bit Count (BC) attribute Blocked (BL) attribute Changed Attribute (CA) attribute of history database Counter Enable (CE) attribute Counter Limit (CL) attribute Counter Overflow (CO) attribute Cause of Transmission (CT) attribute Counter Value (CV) attribute Date of event from Event Time (ET) attribute of history database Event Daylight Saving (ED) attribute of history database Message Text (MX) attribute Event Comment Text (EX) attribute of history database Group Type (GT) attribute History Activation (HA) attribute History Blocking (HB) attribute History Logging Daylight Saving (HD) attribute of history database History on History (HH) attribute of history database Higher Input (HI) attribute History logging time Milliseconds (HT) attribute of history database Higher Output (HO) attribute History logging Time (HT) attribute of history database Higher Warning (HW) attribute In Use (IU) attribute Item Name (IN) attribute Index (IX) attribute Alarm Activation (LA) attribute Lower Input (LI) attribute Logical Name (LN) attribute Lower Output (LO) attribute Lower Warning (LW) attribute Normal Value (NV) attribute Object Address (OA) attribute Object Bit Address (OB) attribute Overflow (OF) attribute Object Identifier (OI) attribute 213

214 SYS MicroSCADA Pro 1MRS Table Columns for Event List (Continued) Column OI1 OI2 OI3 OI4 OI5 OR OS OT OV OX PF PH PT RA RB RC RI RM RT RX SB SE SP SS ST STATUS SZ SX TIME UB UN UTC_TIME XB ZD ZE Information Source The 1st level of Object Identifier (OI) attribute The 2nd level of Object Identifier (OI) attribute The 3rd level of Object Identifier (OI) attribute The 4th level of Object Identifier (OI) attribute The 5th level of Object Identifier (OI) attribute Out of Range (OR) attribute Object Status (OS) attribute Output Type (OT) attribute Object Value (OV) attribute Object Text (OX) attribute Physical Format (PF) attribute Printout on History (PH) attribute Process Object Type (PT) attribute Reserved A (RA) attribute Reserved B (RB) attribute Receipt (RC) attribute Reserved Integer (RI) attribute Registration Milliseconds (RM) attribute Registration Time (RT) attribute Reserved Text (RX) attribute Substituted (SB) attribute Selection (SE) attribute Stop Execution (SP) attribute Switch State (SS) attribute Sort Type (ST) attribute Status columns with symbols for Alarm, Comment, Status SCADA Zone Supervision (SZ) attribute State Text (SX) attribute Time of event from Event Time (ET) and Event Milliseconds (EM) attributes of history database Update Blocking (UB) attribute Unit Number (UN) attribute UTC time of event converted from the Event Time (ET) and Event Milliseconds (EM) attributes of history database. Activation Blocking (XB) attribute Zero Deadband (ZD) attribute Zero deadband supervision Enabled (ZE) attribute 8.2. Creating custome Event List columns Custom columns can be created to display addition attributes for events. 214

215 1MRS MicroSCADA Pro SYS Defining event coloring Event coloring displays the most important events in a way that they are easily located from the Event List. The SYS 600 Event List can be configured to use different colors for events, which fulfill the defined conditions in the Event Color Settings dialog. By using this functionality, the Event List can be adapted to display the events according to the convention required by the application Event coloring example The following is an example of event coloring in an application and the steps of how it has been defined in the Event Color Settings dialog. 1. Open the Event Color Settings by selecting Event List > Color Settings. 2. Click the Add button. The new event coloring condition row is now displayed. 3. Double-click the the first column of the Attribute column. Select the HI - Higher Input attribute from the drop-down list. 4. Double-click the first row of the Condition column. Select Condition < (smaller than) from the drop-down list. 5. Double-click the first row of the Value column. Enter the value 10 in the Value field. 6. Double-click the first row of the Color column. Select the color Red from the drop-down list. 7. Repeat the conditions for the rows 2, 3, 4, 5, 6 and 7 according to the following Fig Event coloring example. 8. Click OK to accept the defined settings. The Event List now displays the events according to the defined conditions. Fig Event coloring example. elist_color 215

216 SYS MicroSCADA Pro 1MRS Preconfiguring events with advanced conditions You can configure the Event List to use advanced condition when defining preconfigurations for displayed events. You can access the Advanced Condition dialog by clicking the More button in the Filter dialog and by selecting the Advanced Condition option. An example of advanced condition, which you can use in your application is presented in the following section Advanced condition example When an event occurs in the system, the information on the event is stored in the history database. Several attributes are stored in the application as event history attributes. The attribute for the daylight saving (HD - History logging time Daylight saving) is stored in the history database together with these attributes. Fig presents an example of how to configure an advanced condition, which specifies that only the events that occurred when daylight saving time was in use, are displayed in the Event List. Fig Advanced condition example ad_event_cond 8.5. Locating object When right-clicking the selected line and selecting Locate Object in DMS or Locate Object in Monitor Pro, the location of the GET_DISPLAY_NAME.TXT procedure file is displayed, that is, \SC\APL_\<application name>\ PICT\. If the procedure file exists, it is run. The function sends the following arguments to the procedure: Order number Name Meaning 1 LN The LN attribute value of the selected object 2 IX The IX attribute value of the selected object 216

217 1MRS MicroSCADA Pro SYS Order number Name Meaning 3 OI The OI attribute value of the selected object The procedure returns a display name without the file extension. If the display name is the always same as the station name, the performed procedure can be run @OI=argument(3) #return EDIT(SUBSTR(%OI, 1, 10),"TRIM") If the GET_DISPLAY_NAME.TXT procedure file does not exist or its execution fails, the function reads the PI attribute value of the object that produces the alarm or event. The PI attribute value contains a display name without the file extension. Finally, the display is opened and the same object that was selected on the Event List is displayed with the highligt symbol, see Fig Fig Higlighted symbol displayed on the selected line of the Event List. A The PI attribute accepts only display names no longer than 10 characters and the name cannot contain punctuation or spaces. 217

218 218

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

220 SYS MicroSCADA Pro 1MRS Customizing column layout Alarm List can be configured to have column layouts, which are application or userspecific. For each user, the default column layout template for application is used if a user-specific column layout file is not located from the system. A default column layout template for an application contains the following columns: Alarm row number Date Time Station Bay Device Object Text Status Class Fig Default column layout for Alarm List AlarmListColumns You can find the column layout template for application in folder \sc\apl\<application name>\par\apl\alarm. User-specific column layout templates are located in folder \sc\apl\<application name>\par\<user name>\alarm. The column layout files are always using the file name layout.ini. You can edit the contents of these layout files by using a normal text editor application of Windows operating system (for example Notepad). The format of this file is Windows Initialization (INI) file, which is used typically to describe the configuration settings in Windows operating system applications, see Fig

221 1MRS MicroSCADA Pro SYS Fig Describing configuration settings in layout.ini file AlarmListAplLayout Each column of Alarm List is described by its own section name, for example [Column1]. The column order is defined by the number in the end of the section name. 221

222 SYS MicroSCADA Pro 1MRS The key names for each column are presented in the table below. Table Key name Label Attribute Length Table Keyword DATE TIME OI OI1 OI2 OI3 OI4 OI5 OX STATUS_TEXT AC AZ OS PT LN IX Column key names and their contents Contents Identifies the column name in the Alarm List (for example Date) Identifies the information which the Alarm List application reads from the system, see Table Identifies the length of the column Supported attribute keywords Source Date of alarm Time of alarm Object Identifier (OI) attribute The 1st level of Object Identifier (OI) attribute The 2nd level of Object Identifier (OI) attribute The 3rd level of Object Identifier (OI) attribute The 4th level of Object Identifier (OI) attribute The 5th level of Object Identifier (OI) attribute Object Text (OX) attribute Status Alarm Class (AC) attribute Alarm Zone (AZ) attribute Object Status (OS) attribute Process Object Type (PT) attribute Logical Name (LN) attribute Index (IX) attribute 9.2. Preconfiguring alarm buffer with advanced conditions You can configure the Alarm List to use advanced conditions when defining preconfigurations for displayed alarms. You can access the Advanced Condition dialog in both Alarm List Templates by clicking the More button in the Filter dialog and by selecting the option Advanced Condition. Two examples of advanced conditions, which you can use in your application are presented in the following section Advanced condition, example 1 Typically, the alarms of the system are categorized into several alarm classes. This categorization is used to indicate the functional purpose and importance of alarm classes. The result of this work depends on the application area in question. Fig presents an example of how to configure an advanced condition, which specifies that only the alarms belonging to classes 1, 2 and 3 are displayed in the Alarm List. 222

223 1MRS MicroSCADA Pro SYS Fig Configuring advanced conditions for alarms, example 1 AdvancedAlarmCondition Advanced condition, example 2 For the signals of type analog input, the alarming process objects contain information about limit value supervision, that is, about the reason why the alarm limit has been violated. The four different reasons for alarm limit violation can be: 1. Low alarm, the value received from the process is equal or smaller than Low Alarm (LI) attribute in the limit value configuration 2. High alarm, the value received from the process is equal or greater than High Alarm (HI) attribute in the limit value configuration 3. Low warning, the value received from the process is equal or smaller than Low Warning (LW) attribute in the limit value configuration 4. High warning, the value received from the process is equal or greater than High Warning (HW) attribute in the limit value configuration Fig presents an example of how to configure an advanced condition in such a way that only the alarms from analog input s process objects violating the low alarm or high alarm are displayed in the Alarm List. 223

224 SYS MicroSCADA Pro 1MRS Fig Configuring advanced conditions for alarm limit violation, example 2 AdvancedAlarmCondition Locating object When right-clicking the selected line and selecting Locate Object in DMS or Locate Object in Monitor Pro, the location of the GET_DISPLAY_NAME.TXT procedure file is displayed, that is, \SC\APL_\<application name>\ PICT\. If the procedure file exists, it is run. The function sends the following arguments to the procedure: Order number Name Meaning 1 LN The LN attribute value of the selected object 2 IX The IX attribute value of the selected object 3 OI The OI attribute value of the selected object The procedure returns a display name without file extension. If the display name is always the same as the station name, the performed procedure can be run @OI=argument(3) #return EDIT(SUBSTR(%OI, 1, 10),"TRIM") If the GET_DISPLAY_NAME.TXT procedure file does not exist or its execution fails, the function reads the PI attribute value of the object that produces the alarm or event. The PI attribute value contains a display name without file extension. Finally, the display is opened and the same object that was selected on the Alarm List is displayed with the highligt symbol, see Fig

225 1MRS MicroSCADA Pro SYS Fig Higlight symbol displayed on the selected line of the Alarm List. A The PI attribute accepts only display names no longer than 10 characters and the name cannot contain punctuation or spaces. 225

226 226

227 1MRS MicroSCADA Pro SYS Blocking List SYS 600 Blocking List displays a summary of the present signal blocking situation of the supervised process. Each signal is presented as a signal text line, describing the signal in the process, see Fig A signal text line consists of: Blocked signal row number Signal text Check boxes indicating the blocking state You can find a more detailed description of the Blocking List functions in SYS 600 Operation Manual. In this chapter, you learn how to customize the SYS 600 Blocking List blocking settings. Fig Blocking List main view BlockListExp Explanations to Fig : 1. Tool menu for Blocking List 2. Toolbar buttons 3. Check boxes indicating the blocking state of the signal 4. Current page and the total amount of pages 5. Signal text 6. Scroll box 7. Arrows for scrolling the page up or down 8. Fields presenting sum of signals for each blocking type 227

228 SYS MicroSCADA Pro 1MRS Customizing blocking settings You can configure application or user-specific settings for Blocking List. If a userspecific blocking settings file can not be located from the system, a default blocking settings template for application is used for each user. A default blocking settings template contains the following settings: Show Update Blockings Show Control Blockings Show Alarm Blockings Show Event Blockings Show Printout Blockings Show Action Blockings Enable event on block/deblock (Off) Enable printout (Off) Fig Default blocking settings for Blocking List BlockingListSettings You can find the default blocking settings template in folder \sc\apl\<application name>\par\apl\blocking. The templates for user-specific blocking settings are located in folder \sc\apl\<application name>\par\<user name>\blocking. Blocking settings files always use the file name blocking_settings.ini. You can manage the contents of these layout files in the Blocking Settings dialog of the Blocking List. 228

229 1MRS MicroSCADA Pro SYS Trends Trend Display is a component included in the Monitor Pro application. Trend Display functionality is similar to one of the Trend Reports picture in LIB 510. Trend Display is used for trend analyses and for showing measured values in curve or table form. Fig Trend Display A

230 SYS MicroSCADA Pro 1MRS Introduction to trends A trend is a time-related follow-up of process data. All types of process objects, like in and out data, binary, analogue and digital data can be illustrated as trends. When a trend picture is shown, you can select the data to be displayed in the picture by using a trend basket. When the trend basket is closed, the selected trends are displayed in the trend picture. The trend display configuration includes a set of parameters (colors, fonts and so on), which are called the trend preconfigurations. You can create, delete or apply an existing preconfiguration to the trend picture shown Copying the trends In Trend Display, you can copy the selected trend items from the tabular or graphical view to the clipboard of the operating system. In the graphical view, there are usually several trend items that are included in the selection to be copied. When you paste the selection to the clipboard, the data is divided into several sections, where each section has a header and contents of each selected trend item Exporting trends to the.csv or.txt file In Trend Display, you can export the selected trend item from the tabular or graphical view to a.csv or.txt file. You can choose the file name and folder in the Save As dialog. When you select a rectangular region in the graphical view, the graph is zoomed automatically. To enable other selection mechanisms than zooming in the graphical view, you need to change the modes of the graphical view. The following modes and submodes are available: Table Modes and submodes of Trend Display Mode Sub-mode Functionality Panning No Trend data in the graphical view is panned according to the mouse movements. Selection Auto-zooming Trend data in the graphical view is zoomed enabled automatically according to the mouse selection. Selection Auto-zooming Trend data in the graphical view is selected according to disabled the mouse selection. There is no automatic zooming, instead the selection is indicated to be either copied to the clipboard or exported to a file. You can zoom or pan by using the keyboard and mouse: Panning: Click the mouse wheel and move the mouse. Zoom selection: Press CTRL, click the left mouse button and select the zoom area. Zooming in: Rotate the mouse wheel forward. OR Press CTRL and click the left mouse button. 230

231 1MRS MicroSCADA Pro SYS Zooming out: Rotate the mouse wheel backward. OR Press CTRL + SHIFT and click the left mouse button. 100 % view Selection zooms the process graphics to 100 percent. Press CTRL + Alt + SPACE to reset the selected zooming and panning options. The selection mode policy, whether the auto-zooming is enabled or disabled is defined in the toggle toolbar button. It is enabled by default Trend Display parameters The Trend Display has a set of parameters, such as the number of data logs and the maximum length of data logs that can be changed if required. These parameters are stored in the text file: \sc\sa_lib\base\bbone\use\bgu_ta_setup.txt. You can edit the file by using the SCIL Editor. The parameters are stored as SCIL variables. Therefore, ensure that the file syntax is correct when editing a file. The syntax can be checked, for example, by using the Check Syntax option of the SCIL Editor. The parameters are described in the following table: Table Parameter descriptions Parameter Number of Datalog Max Length of Datalogs Description The number of data logs created for the trends, that is, the maximum number of process objects that can be logged at the same time. The maximum value of this attribute depends on the size of the system and the hardware used, and it should be found out experimentally. The maximum number of registrations in one data log, that is, the maximum number of history values stored for one process object. The maximum value of this attribute is The number and maximum length of the data logs used in the Trend Display are application-specific parameters. Their effect on the system performance should always be measured by using the actual hardware. Too large values of these parameters may cause poor system performance. After changing one of the parameters, restart the Trend Display and delete the existing data logs. After this, the changes take effect. The following two data log ASCII files are used in the Trend Display: \sa_lib\base\bbone\use\bgu_ta_setup.txt \sc\sa_lib\base\bbone\lang<*>\bgu_ta_objec.txt Both files are used in the Trend Display to create and initialize necessary application objects. Marking <*> refers to the current application language number. 231

232 SYS MicroSCADA Pro 1MRS Application objects Data objects Time channels Trend Display in the Monitor Pro application uses the same application objects as LIB 510 Trend Picture. The objects include a set of Data Objects and Time Channels. All the needed application objects are created when the Trend Display is started for the first time. If the full set of needed objects exist before the first Trend Display start-up, the objects are not updated. To reinitialize the objects completely, delete the old objects and restart the Trend Display. Trend Display uses data objects named FTU_TRD*, where * means 1 to the maximum number of trends. The default trend number is 20 (NUMBER_OF_DATALOGS parameter of the bgu_ta_setup.txt file). Trend Display uses the following time channels: FTU_TRT30 (time channel for 30 seconds time interval) FTU_TRT60 (time channel for 1 minute time interval) FTU_TRT120 (time channel for 2 minutes time interval) FTU_TRT300 (time channel for 5 minutes time interval) FTU_TRT600 (time channel for 10 minutes time interval) 232

233 1MRS MicroSCADA Pro SYS Measurement Reports Features and options Measurement Reports is used for various types of time related reports, such as hourly, daily, weekly, monthly and yearly reports. Measurement Reports can be used for: Reporting of energy (active, reactive) Reporting of current (for example bay level) Reporting of voltage (for example 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. The data can be illustrated as reports. The data for the reports is calculated and stored in real time. The report data is collected and calculated either cyclically or triggered by events. The most common method is to collect raw data from the process, refine it and store it in the report database. The collection and calculation of the report data can be initiated in the following way: At predefined time intervals When a predefined event occurs As a result of a calculation Based on a condition On the operator's request Measurement Reports 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 user specific reports. The divided structure and independent components help to use the reports dynamically and in many ways. Measurement Reports 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 a daily basis (time resolution: according to a period cycle) 233

234 SYS MicroSCADA Pro 1MRS Quick report on a weekly basis (time resolution: 1 day) Quick report on a monthly basis (time resolution: 1 day) Quick report on a yearly basis (time resolution: 1 month) Each report display is composed of a number of report columns and common functions which can be used within report displays. For example, common functions report header, type and unit. The report columns consist of different types of data, for example, points in time and measured, metered, manually entered or calculated values. All the data values within the report can be presented either in a tabular (numerical) or in a graphical form as curves. In maximum, a report picture can contain 11 columns per report page, including the time column. Report Base includes a set of functions (for example 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 unambiguously. Report Tool includes a set of functions which provide report-specific tools for installing and configuring Report Base (for example the configuration of report object, calculation and database settings) and Report HSI (the configuration of the report picture columns) when defining the user specific reports. The general features and options of Measurement Reports are: 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 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 a daily basis enabled Beginning of a day and beginning of a week configurable Application specific definitions enabled Application specific definitions (reports) Before defining the reports, set the following definitions in the Report Setting tab of the Application Options dialog: Period cycle * 15, 30 or 60 minutes Default: 60 minutes 234

235 1MRS MicroSCADA Pro SYS Length of the period values history * 1-5 years Default: 2 years Length of the forecast period 0-15 days Default: 0 days Beginning of the report day in hours after midnight * 0-23 Default: 0 Beginning of the report week Monday - Sunday Default: Monday Sampling cycle * 3 minutes Default: 3 minutes, reserved for future use Length of the sampled values history * 0-15 days Default: 8 days The definitions are valid for the entire application. Changing the definitions (marked with asterix (*)) afterwards causes loss of the existing history data. To define the application specific definitions in the Report Settings tab: 1. Select Tools > Options. 2. Select Report Settings tab, see Fig After defining settings, click OK to save the settings. 235

236 SYS MicroSCADA Pro 1MRS Fig Example of the Report Settings tab A Migrating existing Measurement Reports built with LIB 5xx application library Configuration Data Export tool offers means to reuse the existing Measurement Reports, built with LIB 5xx application library, when an application is upgraded to the MicroSCADA Pro user interface. Configuration Data Export tool locates the report configuration of the picture functions from the SCIL picture. The tool transfers the separated information to Measurement Reports related configuration files. After the upgrade, the contents of the migrated Measurement Reports are displayed in Object Navigator, see Fig For more information about using the Configuration Data Export tool, refer to Section Configuration Data Export tool. 236

237 1MRS MicroSCADA Pro SYS Fig Migrated measurement reports A Creating new Measurement Reports Use Object Navigator to create a new measurement report. Add a new measurement report by selecting Object > Install Standard Function, see Fig The different report types can be found from the SA-LIB s Measurement Reports category. 237

238 SYS MicroSCADA Pro 1MRS A Fig Creating a new measurement report When the suitable report type is selected, the Standard Function tool is displayed, see Fig Use the Standard Function tool for configuring reports related to the attributes. Select the Tools tab to use the Measurement Reports configuration tools, see Fig

239 1MRS MicroSCADA Pro SYS Fig Configuring a measurement report A

240 SYS MicroSCADA Pro 1MRS A Fig Measurement Reports configuration tools There is a locking mechanism for Report Object Configuration Tool, the Execution Delays tool and the User-defined Definitions tool. A locking mechanism prevents concurrent editing. Editing the report configuration data simultaneously is not possible without breaking the lock. Unlocking causes a corruption of the report configuration data. For example, if one user uses the Execution Delays tool, and another user tries to open the same tool, a notice dialog is displayed, see Fig Fig Example of a notice dialog indicating that the tool is locked 240

241 1MRS MicroSCADA Pro SYS Report object settings Before creating and configuring report displays, define and create report objects. It is possible to connect the forms, for example, to a process object or to a calculation operation. With Report Configuration Tool you can: 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. If the needed report objects already exist, you do not need to configure report objects every time you add a display. Before you create or configure the report objects, define the application specific report settings. Changing the definitions afterwards causes a loss of the existing report data. To define the report objects: 1. Open Report Configuration Tool 2. Insert new report objects 3. Edit the existing report objects 4. Save the report objects configuration data, or create the needed data objects, command procedures and time channels by updating the configuration data to the report database. The report database consists of data objects, command procedures and time channels used by the report system Report Object Configuration Tool Report Object Configuration Tool is opened from the Object Navigator s Standard Function Tool. To open Report Object Configuration Tool: 1. Select Report Configuration Tool in the Tools tab of the Standard Function Tool dialog, see Fig Select the Report Object Settings command to open the tool. When the Report Object Configuration Tool is opened, you can insert new report objects and modify the existing report objects. Report objects listed in the report database are displayed in Fig

242 SYS MicroSCADA Pro 1MRS Fig Report object lists of Report Object Configuration Tool A Report Object Configuration Tool tabs In Database The page contains report objects that are updated to the database. In other words, the page contains the setup of the present reports. Inserted The page contains the inserted report objects that are not updated to the database. The report objects are not taken into account in the present reports. Deleted If a report object is deleted on the In Database tab, the object is moved to the Deleted tab. The report object s data can be found on the Deleted tab. The deleted object is removed when updating the modifications to the database. Delete the process object by clicking the Delete button on the In Database tab. Restore the process object by clicking the Delete button on the Deleted tab. Modified When a report object is edited, the modifications are saved to the Modified tab. Update modifications to the database by clicking the Modify DB button. The report object s configuration on the Modified tab replaces the object s configuration with the same logical name on the In Database tab. The database is configured according to new configurations. The report objects are not taken into account in the present reports. 242

243 1MRS MicroSCADA Pro SYS Report Object Configuration Tool buttons Edit Opens the Report Object Editor dialog concerning the selected object. You can edit the attributes excluding the report object s logical name. Insert Opens an empty Report Object Editor dialog. You can create a new report object and configure the attributes. Delete The Delete button on the In Database tab The deleted object is marked as deleted. The object is permanently removed from the database during the following database update. It is possible to undo the operation. Information about the deleted object is added to the Deleted tab. The Delete button on the Inserted tab The object is permanently removed from the configuration data. It is not possible to undo the operation. The Delete button on the Deleted tab Restores the deleted object. The report object is not removed during the next database update. The Delete button on the Deleted tab The object is permanently removed from the configuration data. It is not possible to undo the operation. Advanced Opens the selected report object in a tree view. You can examine the configuration attributes of a report object. Modify DB Updates the configurations to the report database. OK Saves the configuration data and closes the Report Object Configuration Tool dialog. The configuration data is saved, but the report database is not updated. Cancel Discards the changes and closes the Report Object Configuration Tool dialog. Apply If the group ID is changed, the data objects of the report object are deleted. The data objects are recreated when the modifications are updated to the report database. Saves the configuration data. The configuration data is saved, but the report database is not updated. 243

244 SYS MicroSCADA Pro 1MRS Help Opens a help dialog Inserting new report object New report objects are inserted using Report Object Configuration Tool. To insert a new report object: 1. Select Report Configuration Tool in the Tools tab of the Standard Function Tool dialog, see Fig Select the Report Object Settings command to open the tool. 3. Open Report Object Editor by clicking the Insert button in Report Configuration Tool. 4. Make configurations for the report object. 5. Save the object by clicking OK or by clicking Add. The OK button also closes the dialog. The Add button leaves the configuration data ready for the next report object. When the report object is inserted, the objects are diplayed in the Inserted tab, see Fig Configuring report object with Report Object Editor Tool You can configure report objects in the Report Object Editor dialog. If the dialog is opened by clicking the Insert button in Report Object Configuration Tool, the dialog is in an insertion mode. In an insertion mode, you can define the logical name for the report object. If the dialog is opened by clicking the Edit button in Report Object Configuration Tool, the dialog is in an edit mode. In an edit mode, you cannot change the logical name, see Fig

245 1MRS MicroSCADA Pro SYS A Fig Report Object Editor The Report Object Editor dialog includes at least the General Settings tab. The dialog also contains the Additional Settings tab, which is visible only for the measured and calculated report objects. For more information about the Additional Settings tab, refer to Section Additional Settings for measured report object types. When you save the edited object, Report Object Editor checks the required information in the dialog. If any information is invalid, a message is displayed Dialog buttons OK Saves the report object to a report object list and closes the dialog. If the configurations are unacceptable, a message is displayed. Add Saves the configuration data to a report object list and leaves the current configuration as a base for the following insertion. The function is useful when adding the same process objects to different report objects. Clear Clears the fields. Cancel Discards the changes and closes the Report Object Editor dialog. Help Opens a help dialog. 245

246 SYS MicroSCADA Pro 1MRS General Settings of report object The fields on the General Settings tab are the same for the different report object types, see Fig It is required to fill the Logical name and the Group ID fields. The configurable attributes and fields are as follows: Logical name (LN) Defines the name of the report object in the Logical name field. Furthermore, logical name defines the names of the data objects that are created when insertions are updated to the report database. The report object name can consist of maximum 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. Comment (CM) The comment text is displayed on the report object list and in the CM attribute of data objects. Unit (ST) An informative field showing which unit is displayed only on the report object list. Group ID (ID) 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. If you use a digit on the end of the logical name, there is a risk of malfunction. For example, two report objects, ENERGY and ENERGY1, are created. If the length of the period history is 2 years, created names of the data objects created for the ENERGY report object are ENERGY, ENERGY0, ENERGY1 and ENERGY2. ENERGY is the data object for the sampling values. ENERGY0, ENERGY1 and ENERGY2 are the year data objects of the period values. Similarly the names of the data objects created for the ENERGY1 report objects are ENERGY1, ENERGY10, ENERGY11 and ENERGY12. ENERGY1 is the data object for the sampling values. In this case, the ENERGY1 data object is used both as a sampling as well as a period data object, which is impossible. The type of the report object. The possible main categories are measured, calculated, entered, user defined and gauged report objects. The measured report objects are connected to process objects. The measured report object types are sum calculated (MS), mean calculated (MM), minimum value (MN), maximum value (MX) and period value (MP), see Table

247 1MRS MicroSCADA Pro SYS Table The measured report object types Object type MS MM MN MX MP Description Sum. Data objects are created in the report database for both sampled and period values. A period value is the sum of the sampled values within that period. Average. Data objects are created in the report database for both sampled and period values. A period value is the average value of the sampled values within that period. Minimum. Data objects are created in the report database for both sampled and period values. A period value is the smallest value of the sampled values within this period. Maximum. Data objects are created in the report database for both sampled and period values. A period value is the largest of the sampled values within this period. Period. Data objects are created in the report database for both sampled and period values, but the length of sampled object is 1, and the values are read only once within a period cycle. A period value is read from a process object. The values of the calculated report objects are evaluated according to the definitions of input parameters and calculation orders. The calculated report object types are sampled value (CS), period value (CP) and sampled and period values (CB), see Table Table The calculated report object types Object type CS CP CB Description Data object is created only for the sampled values. A defined calculation is made once in a sampling cycle (for example once every 3 minutes) and the value of this calculation is saved in the report database. Data object is created only for period values. Defined calculations are made once in a period cycle (for example once every 15 minutes, 30 minutes or 1 hour) and the values of this calculation are stored in the report database. 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. When you define an entered or a gauge report object, only the data objects are created in the report database. Automatic configurations or value samplings are not created. The identification for an entered report object is EN. The identification for a gauge (meter) report object is GA. Use the user defined types to build an own reporting function. When you define the user groups with the User Defined Groups and Procedures tool, the groups are displayed in the drop-down menu. Using user-defined groups requires deep knowledge of the reports, and therefore, it is recommended to use the feature only when it is not possible to implement the wanted functionality in some other way. 247

248 SYS MicroSCADA Pro 1MRS Additional Settings for measured report object types The Additional Settings tab is displayed only when a measured type of the Group ID is selected, see Fig Only the Update instructions needed field is not obligatory. The fields are described in Table Fig Additional Settings page for a measured report object type A Open Process Object Browser by clicking the Browse button, see Fig Process Object Browser searches signals from the process database. The signal types searched are analog input (AI), digital input (DI) and pulse counter (PC). If the size of the process database exceeds signals, the buttons of the next/ previous signals at the bottom of the dialog are activated. To fill in the fields in Report Object Editor, see Fig : 1. Select a signal 2. Click OK, see Fig

249 1MRS MicroSCADA Pro SYS Fig Process Object Browser dialog Table Attributes Attribute Application of the process object (P_APL) Logical name of the process object (P_LN) Index of the process object (P_IX) Type of the process object (P_PT) A Field The application of the process object where the report object is connected. 0 is current application. The logical name of the process object where the report object is connected. 0 is the 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. The index of the process object to which this report object is connected. When the Browse button is used, this field is also updated. 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. 249

250 SYS MicroSCADA Pro 1MRS Table Attributes (Continued) Attribute Max value of the pulse counter (PS) Field If the type of the process object is PC, a maximum value of the pulse counter is needed. If the counter counts pulses repetitiously, this value must be 0 (zero). The data object attribute PS indicates the width of the pulse counter, that is, the value that resets the physical pulse counter to zero. In other words, the PS attribute should be set to the maximum value of the pulse counter + the size of one pulse. Note, that the maximum value of the pulse counter has to be divided by the linear scale of the process object (see below). The result should be placed into the field of the Max value of the pulse counter (PS), if needed. Examples of the maximum values of the pulse counters: SPACOM * - SPTO 1D2, 1D5, 1D6, 6D (0V8-0V15) (0V5) - SPOC 110C, 111C, 112C ( V5) RTU 200/210 - within RP570 PROCOL 2^Bit Count (2^31) Linear scale of the process object (P_SC) Update instructions needed (P_ACT) Value type of data object (VT) 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. Also note, that the parameter V5 (SPTO) cannot be used, if the pulse counters are used with a SRIO type of station. The linear scale of the process object is a multiplier, which is used when values from the process database are stored into the report database. If the process object does not update spontaneously, the update instruction is required 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 in writing the instruction. The value type of the data object in which the report is connected to. The possible values are REAL and INTEGER. In general, the value type REAL is used, but in certain circumstances the value type INTEGER is preferred to avoid rounding errors, for example when reporting the pulse differences of large pulse counter values Additional Settings for calculated report object types The Additional Settings tab is displayed only when a calculated type of the Group ID is selected, see Fig

251 1MRS MicroSCADA Pro SYS Fig Additional Settings page for a calculated report object type A Configurable parameters: Input parameters for calculation (DATAIN) If the object s calculation operation uses values of other report objects as input parameters, the parameter objects have to be introduced. The logical names of the parameter report objects have to be written one by one, each name on a separate line. An example of input parameters for the calculation operation is displayed in Fig A Fig Example of input parameters for calculation Calculation operation (OPER) The calculation operation can be an single line calculation, or a multi line SCIL program with a #RETURN command. The input parameters can be referenced with variables %OBJ1..%OBJn. The %OBJ1 is the first report object on the input parameter list and %OBJn is the last. 251

252 SYS MicroSCADA Pro 1MRS If there is only one input parameter, the %OBJ variable without index number refers to the input parameter. The %OBJn variable type is VECTOR. The type of a result calculation operation can be INTEGER or REAL, or a vector of the types. An example of an single line calculation operation is displayed in Fig and an example of an multi line calculation operation is displayed in Fig Fig Example of a single line calculation operation A Fig Example of a multi line calculation operation A Calculation order of sampled and period values The calculation order of sampled values enabled when the group identification is CS or CB. The calculation order for period 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 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 clicking the Add button, the report object is added to the calculation order list. By clicking the Up and Down buttons, you can move the current report object up and down on the calculation order list. The calculation order goes from top to bottom. 252

253 1MRS MicroSCADA Pro SYS Logical names can be mentioned twice on the calculation order list. In such a case there is a place for the original and the modified name in the calculation order. The place in the calculation order after modifications is marked with a character (M). When inserting a new object, there is a character (I) after the inserted logical name, but not after the updated report object. The calculation order must be defined every time when new calculated objects are inserted, or some existing calculated object is modified Execution delays You can define execution delays for period cycles and for sampling cycles. The execution delays must be used when process objects are not spontaneous, and the execution delays need an update command to be used before the current value is available in the process database. After time channels are triggered, an execution delay defines for how long the program waits before the evaluation of values starts. When update commands are used, the commands are sent after the time channels are triggered. The program reads the value from the process database after the execution delay User defined groups and procedures You can create own report object types. You can write methods for different cases, for example: what is done when the system starts up what is done when the period cycle is full Using user-defined groups requires deep knowledge about the reports and therefore, it is recommended to use the feature only when it is not possible to implement the wanted function in some other way Call-back procedure for sampling cycle A call-back procedure for the sampling cycle is executed when the other sampling cycle routines have been executed. Therefore, it is possible to execute programs defined by the user every time the sampling routines have been executed Call-back procedure for period cycle A call-back procedure for the period cycle is executed when the other period cycle routines have been executed. Therefore, it is possible to execute programs defined by the user every time the period routines have been executed. 253

254 254

255 1MRS MicroSCADA Pro SYS Customizing application window Customization dialog With Monitor Pro you can: Add custom toolbars Rename custom toolbars Delete custom toolbars Rename menu commands Delete menu commands Copy or move menu commands from one place to another Rename toolbar buttons Delete toolbar buttons Copy or move toolbar buttons from one place to another However, some menu commands and toolbars are generated programmatically. Therefore they cannot be customized, for example the menu commands in the picture specific menu and the buttons in the application-specific toolbar. In addition, you cannot add new menus, menu commands or toolbar buttons, but you can copy and move the existing ones. Furthermore, pre-defined toolbars cannot be deleted, but you can hide or show them. The Monitor Pro layouts are user-specific. The default layout is loaded when the user logs on the application for the first time.you can start the Monitor Pro customization in three different ways: 1. By double-clicking any empty area of the band. 2. By right-clicking the mouse to open the customization dialog. From this menu, select the Menu Customize menu command. 3. By selecting Tools > Customize. In the Customization dialog you can: Add, rename and delete custom toolbars (that is, user-defined toolbars) 1 Delete and rename menu commands 1 Change the caption and style of the tool shortcut menu Get an action tool categorized listing Drag and drop to any band, menu or submenu Create new customized menus and menu commands Access full keyboard shortcut customization dialog 1. Some menu commands (for example the menu commands in picture specific menu) and some toolbars (for example the buttons in application specific toolbar) are not customizable because they are generated programmatically. 255

256 SYS MicroSCADA Pro 1MRS When the Customization dialog is open, the main menu and shortcut menus can be displayed differently than at run-time. It is not possible to select any menus during the customization. You can use the tool shortcut menu for customization, see Fig The tool shortcut menu can be displayed while the Customization dialog is open. It can be opened by right-clicking the toolbar button. The styles for this tool are the following: Default style: includes both the text and icon, if available Text only: only the text (caption of the tool) is shown Image only: only the icon is displayed, if available Image and text: includes both the text and icon, if available Fig Tool shortcut menu, selecting style CustomizeToolContextMenu When the Customization dialog is open, you can move toolbar buttons and menu commands around. You can create a copy of the tool by pressing down the CTRL key while moving the tool. If you are allowed to customize the toolbar, a More tools button is displayed, see Fig This quick customization shortcut menu allows you to show or hide tools from the toolbar without opening the Customization dialog. However, menu commands must be customized by using the Customization dialog. 256

257 1MRS MicroSCADA Pro SYS You can move or delete tools from the bands (toolbars) without opening the Customization dialog: hold the Alt key down and drag with the mouse the tools between bands (toolbars) to move them, or away from the band to delete them. If you hold the Alt+CTRL keys down while moving the tool, a copy of the tool is made. Fig More tools button CustomizeMoreTools Toolbars tab A Fig Customization dialog s Toolbars tab When the created toolbar is selected, the Rename and Delete buttons become active and you can rename or delete the toolbar. By clicking the Undo button in the Toolbars tab, you can load the last saved layout. By clicking the Keyboard button in the Toolbars tab, a new dialog is displayed, see Fig

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

259 1MRS MicroSCADA Pro SYS You can configure the visibility of the toolbars and menus. For customization you can use either the Customization dialog s Toolbars tab or by right-clicking on the area of bands and selecting or deselecting toolbars. You have access to different toolbars according to the display used, see Table Table Toolbars according to different displays Display Process Event Alarm Blocking Trends Template 1 Template 2 Toolbars Alarm Row Network Topology Coloring View Info Process Displays Zoom Control Alarm Row Event Display View Info Process Displays Alarm Row Alarm Display Template 1 View Info Process Displays Alarm Row Alarm Display Template 2 View Info Process Displays Alarm Row Blocking Display View Info Process Displays Graphical Mode Alarm Row Trends Display Trends Graphical Mode View Info Process Display Tabular Mode Alarm Row Trends Display Trends Tabular Mode View Info Process Displays Toolbar visibility is view specific. For Process Display, Alarm Display, Event Display, Blocking Display, Trends Display and full screen mode, there are different configurations on which toolbars are shown. Change the visibility of the toolbar in a view by selecting the view and changing the visibility of toolbars. The configuration is automatically saved when some other view is selected. 259

260 SYS MicroSCADA Pro 1MRS Fig CustomizeBands Selecting/deselecting toolbars by right-clicking on the bands area Fig Toolbar menu in full screen mode CustomizeFullScreen 260

261 1MRS MicroSCADA Pro SYS Commands tab A Fig Customization dialog s Commands tab The Categories and Commands functions are the same as in assigning new keyboard shortcut keys, described earlier in Section Toolbars tab.the tools can be moved around as described in the beginning of the Section Customization dialog. When you click the Modify selection button, a same kind of shortcut menu appears as when a toolbar button or menu command is right-clicked while the Customization dialog is open. The Modify selection button becomes active when you select a tool either from the menu or the toolbar. 261

262 SYS MicroSCADA Pro 1MRS Options tab Fig Customization dialog s Options tab A You can take the personalized menus into use via the Options tab. Only the most recently used menus are visible. The data of menu usage is saved when the application is exited, and loaded again when the application is started (or the user logs into some application, and userspecific layout loading actions are done). Also logging into application loads the menu usage data (in addition to the user-specific layout file). Correspondingly when logging out, the menu usage data is saved (in addition to the user specific layout file). In Options tab, you can select to use menu animations and large icons.you can clear the menu usage data by clicking the Reset Menu Usage Data button Adding new menus and toolbars It is possible to create new Monitor Pro menus and menu commands in Customization Mode. You can add menus by creating a new menu or copying an existing menu Creating new menu To create a new menu: 1. Select Tools > Customize to open the Customize dialog. 2. Right-click a menu, for example Help. 262

263 1MRS MicroSCADA Pro SYS Select Create menu, see Fig Fig Creating a new menu 4. A new menu is created to the end of the menu bar. A

264 SYS MicroSCADA Pro 1MRS Right-click a new menu and select Name to rename the menu with a descriptive name, see Fig Fig Renaming a new menu A Define a function for the menu. For more information about menu functions, refer to Section Creating new menu by copying existing menu To create a new menu by copying an existing menu: 1. Select Tools > Customize to open the Customize dialog. 2. Right-click a menu, for example Help. 264

265 1MRS MicroSCADA Pro SYS Select Copy as Nlew Item, see Fig A Fig Creating a new menu by copying an existing menu 4. A new menu is created to the end of the menu bar. The new menu uses the existing menu as a template. The menu name and style is copied from the existing menu. 5. Right-click the new menu and select Name to rename the menu with a descriptive name, see Fig Define a function for the menu. For more information about menu functions, refer to Section The Copy as New Item menu command is displayed on the customization shortcut menu, if the user has the authorization level 2 (Engineering) in the authorization group PRO_CONFIG_COMMANDS. If the current authorization group is not defined, the authorization group GENERAL is used. For more information about authorization, refer to Chapter 18. Authorization Creating a sub-menu Sub-menus can be created in the same way as a new menu, see Creating new menu. When the new menu has been created, select the menu item with the mouse cursor and drag it to the menu where it is required, see Fig

266 SYS MicroSCADA Pro 1MRS Fig Creating a new submenu Creating new toolbar To create a new toolbar: 1. Select Tools > Customize to open the Customize dialog. 2. Right-click a toolbar button or a menu, for example Help. 266

267 1MRS MicroSCADA Pro SYS Select Create toolbar, see Fig Fig Creating a new toolbar 4. A new toolbar is displayed as a floating toolbar, see Fig A Fig A floating toolbar 5. Right-click a new toolbar and select Name to rename the toolbar with a descriptive name. A

268 SYS MicroSCADA Pro 1MRS Define a function for the toolbar. For more information about menu functions, refer to Section Creating new toolbar in Customize dialog To create a new toolbar: 1. Select Tools > Customize to open the Customize dialog. 2. Click New in the Toolbars tab. 3. Name the new toolbar with a descriptive name in the New Toolbar dialog, see Fig Fig New Toolbar dialog A Save the toolbar name by clicking OK Customizing menu commands You can customize the menus as follows: Add menu commands to the new menu by dragging a command from the Commands tab. Move the existing menu command from a menu to another. Copy the existing menu command to another menu Adding menu commands from Commands tab Add a menu command by dragging it from the Commands tab to the new menu, see Fig The new menu command acts as the original menu command. The drag-and-drop operation creates a copy of the original menu command. The original menu command is located also in its original place. 268

269 1MRS MicroSCADA Pro SYS Fig Copying menu commands to a new menu A Moving menu command between menus Move a menu command by dragging it from the existing menu to the new menu, see Fig A new menu command acts as the original menu command. Example If the Status bar menu command is moved from the View menu to the new menu, the menu command does not exist anymore in the View menu. 269

270 SYS MicroSCADA Pro 1MRS Fig Moving menu commands to a new menu A Copying existing menu command To create a copy from an existing menu command: 1. Press CTRL 2. Drag a menu command from the existing menus to the new menu, see Fig The new menu command acts as the original menu command. Example If the Status bar menu command is copied to the new menu, the menu command exists also in the View menu Resetting layout, toolbars or localizations You can access these functions from the Tools menu in the application window. Reset Layout resets the Monitor Pro layout. The old layout files are deleted and the new layout files are localized and taken into use. Reset Toolbars resets the toolbar positions. The user specific customizations are not deleted. Reset Localizations relocalizes the current Monitor Pro layout with the language used in the current session. 270

271 1MRS MicroSCADA Pro SYS Context-sensitive shortcut menus You can create shortcut menus whose content depends on the open application window. To open a context-sensitive shortcut menu and to run the selected menu command: 1. Right-click a symbol in the Process Display, see Fig Select a corresponding menu command to run the menu command. Fig Context-sensitive shortcut menu A The menu structure is similar to the Windows Start menu. The menu commands are organized as folders and files in the file system.therefore, no special tool is needed to configure the menu. The configuration is done by organizing the files, such as programs, documents or shortcuts and the directories in a file system. 271

272 SYS MicroSCADA Pro 1MRS For example, a menu command can be: a file a folder containing submenu commands a link a shortcut to a file a shortcut to a directory an Internet hyperlink The shortcut menu commands can be added, modified or removed by using Windows Explorer. Object types and instances have separate directories, where files such as technical documentation, Internet shortcuts or control commands (SCIL or VB scripts) exist. There is also a folder for the common menu commands. The following parameters are used for the shortcut menu commands whose file type is VBS, SCIL, VSO, BAT or COM: 1 = SYS 600 User Name 2 = SYS 600 User Authorization Level (GENERAL) 3 = SYS 600 User Authorization Level (TOOLS) 4 = SYS 600 User Authorization Level (ALARM_HANDLING) 5 = SYS 600 User Authorization Level (EVENT_HANDLING) 6 = SYS 600 User Authorization Level (REPORTS) 7 = SYS 600 User Language 8 = SYS 600 User Path 9 = SYS 600 Application Name 10 = SYS 600 Application Number 11 = SYS 600 Installed Drive Letter 12 = SYS 600 Application Path 13 = SYS 600 Application is LIB Application 14 = SYS 600 Application is Prepared LIB Application 15 = Current Open Picture File Path 16 = Monitor Pro Window Handle 17 = Monitor Pro Process Id 18 = Terminal Server Sessions Identifier 19 = Mouse Pointer X Coordinate, Mouse Pointer Y Coordinate 20 = Object Name 21 = OPC Item ID Language support The menu commands have a national language support (NLS). Changing the language of the application window in run time affects the menu commands. However, this is not the case with the files, because the file name determines the 272

273 1MRS MicroSCADA Pro SYS name of the menu command. Thus, for each culture (country or language), there should be a folder where language specific files are located. Language specific menus can be built in these directories. Use two-letter language codes when generating a menu structure. For more information about language codes, refer to iso639.htm Title A title is used to give the operator additional information about the process object, whose shortcut menu was opened. For example, the title may be "Erador 20kV Station, Weathertop, Breaker 1" Icon An icon and a caption of a menu command is in fact an icon that is associated to a file type. A caption is a file name without the file extension (.doc for example ) Menu commands Disabled menu commands are grayed. The menu does not support check boxes, radio buttons, or shortcut keys. A file or a folder is an input for a menu command. Changing the name or the icon of the file changes the appearance of the menu command. If a file or a folder is hidden, it is not shown or the menu command is disabled. If a target of a link does not exist, the menu command is disabled. The icon, name, and the file or folder attributes are read and a menu command is shown accordingly. If the file or the folder is a link or a shortcut, its icon and name are used. Thus, the target of the link does not affect to the menu command appearance. The operator receives additional information about a process object by opening a context-sensitive shortcut menu. It contains the menu commands common to all process objects, that is menu commands that are process object type specific and instance specific. There can be menu commands that are shown only for a certain process object instance, such as a log, a figure, a video clip or a maintenance record. When a menu command is clicked, a file is opened (using the application that is associated to it in the operating system). A menu command may also be executable or a script. It is possible to give arguments to the executables or scripts. Each application has its own directory in the file system, where the menu structure is constructed. The directory contains subdirectories, which determine the menu commands for: All process objects Process object types, for example breaker and transformer Process object instances For more information about the menu structure, refer to Section MENUS directory. 273

274 SYS MicroSCADA Pro 1MRS MENUS directory MENUS directory consists of directories such as all, objecttypes and instances. Menu commands, which are to be shown on each shortcut menu, should be stored under the directory all. The directory objecttypes consists of all object types that a station overview can have. Menu commands that each object type can have are also located here. It is also possible that an instance of a breaker might have some menu commands that are instance specific, such as a figure of a breaker, online video stream, maintenance log or a web link to the manufacturer s home page. In that case, the menu commands are located in \<unique object id>. The menu for all objects are located in <apl>\menus\all Generating shortcut menus SYS 600 supports two-letter language codes. When generating the menu structure, use the /culture <language> option. When the option is selected, the menu commands are displayed under the culture specific folder. Table Menu command descriptions Name Description Path <apl> Path of the application E.g. C:\sc\apl\510_403_1 <object type> For more information about <apl>\menus\objecttypes\ object types, refer to Section <object type> Object types (common menu for an object type) <display name> Name of the display file (without extension.v) Menu structures are not shadowed. If a HSB system is used, the menus have to be manually copied between Hot/Stand-by - computers after the modifications have been done. Otherwise, the directories are deleted during the switch-over. By default, context-sensitive shortcut menus are empty. Generate the shortcut menus by using the batch file FSMenuGeneratorGenerateMenu.bat. The file is located in \SC\prog\sa_lib. The BAT file contains instructions for generating the menus. Edit the batch file before generating a shortcut menu structure. Use the batch file for generating a shortcut menu structure and to ensure localized shortcut menus. The file generation creates the file \MENUS\config.ini. You can run the batch file over and over again anytime. Existing menu commands are not removed or modified during the process. 274

275 1MRS MicroSCADA Pro SYS Object types The possible object types are: Arc suppression coil Branch Breaker Busbar Capacitor Condensator Current transformer Disconnector Earth disconnector Fault indicator Fuse Generator Line indicator Motor Primary transformer Serial reactor Shunt reactor Transformer2w Transformer3w Voltage transformer Zero current transformer When object specific custom menus are created in Hot-Stand-By systems, the same file structure must be copied manually into both computers Examples of creating shortcut menus for symbols The examples described: Example 1: a menu structure is generated for an application that uses English. The example also describes adding the menu commands. Example 2: a menu structure is generated for an application that uses English and Finnish. Example 3: a menu structure is generated for graphical symbol instances that use English. 275

276 SYS MicroSCADA Pro 1MRS Example 1 A menu structure is generated for an application that uses English. The example also describes adding the menu commands. In the example, the application used is Weathertop. 1. Open the FSMenuGeneratorGenerateMenu.bat file for editing. 2. Add the following line before the pause statement: FSMenuGenerator.exe /applpath "c:\sc\apl\weathertop" /culture en 3. Save the file. 4. Run the file by double-clicking the file in Windows Explorer. 5. Ensure that the folder structure is correct under the Weathertop folder. The correct folder structure is c:\sc\apl\weathertop\menus. 6. The following folders are located under the MENUS folder: all, objecttypes, and instances. The folder instances is empty. 7. Create and save a ALL_EN file in \MENUS\all\en to create a menu command for all process objects. The file can be a Word document, for example. 8. Define the menu command visible for all objects. 9. Create and save a BREAKER_EN file in \MENUS\objecttypes\Breaker\en to create a menu command for all process objects that belong to the object type Breaker. File can be a Word document, for example. 10.Log on to the Weathertop application. 11.Open a Process Display containing a circuit breaker. 12.Right-click a circuit breaker and ensure that the menu commands are named as described above. Example 2 A menu structure is generated for an application that uses both English and Finnish. 1. Open the FSMenuGeneratorGenerateMenu.bat file for editing. 2. Add the following lines before the pause statement: FSMenuGenerator.exe /applpath "c:\sc\apl\weathertop" /culture en FSMenuGenerator.exe /applpath "c:\sc\apl\weathertop" /culture fi 3. Save the file. 4. Run the file by double-clicking the file in Windows Explorer. 5. Ensure that the folders en and fi exist in \MENUS\all\. Example 3 A menu structure is generated for graphical symbol instances that use English. 1. Open the FSMenuGeneratorGenerateMenu.bat file for editing. 2. Add the following lines to the batch file: FSMenuGenerator.exe /applpath "c:\sc\apl\weathertop" /viewpath "c:\sc\apl\weathertop\pict\fangornforest.v" /culture en 3. Save the file. 4. Run the file by double-clicking the file in Windows Explorer. 5. Ensure that the folders for all symbols, excluding line segments, exist in \MENUS\instances\fangornforest. 276

277 1MRS MicroSCADA Pro SYS The name of the instance specific folder is read from the Object Name property of a symbol, see Fig If the Object Name property is empty, the instance specific folder is not created. Use Display Builder to name a symbol. The menu command name is not the same as the object name. A Fig Object Name property The application path, that is applpath, is a mandatory parameter. Use quotation marks around the path. Once an instance specific menu structure is created, it is not recommended to change the Process Display name. If the Process Display name is changed, also change the directory name: \MENUS\instances\<new Process Display name>. The menu generator does not support some custom object types. Add manually a new folder for the custom object type. Add the folder to \MENUS\<objecttypes folder>. Remember to add a folder also for culture. 277

278 SYS MicroSCADA Pro 1MRS Troubleshooting Table Possible problems with context-sensitive shortcut menus Description of the problem Possible cause Solution Only a description of a shortcut menu is displayed. A message No items or the icon indicates that the shortcut menu is empty. The folder is displayed as a menu command and can be browsed. The folder does not contain submenu commands. The Open With dialog is displayed when running a menu command. A menu command is disabled. The custom object type does not have menu commands An instance specific menu structure is not created for a symbol. There are no commands in the menu directory, that is, menu is empty. The file type of the menu command is unknown. The file has not been associated with any program. User is not authorized to run the menu command or a link target does not exist. A menu structure was not generated for the custom object type or the type does not have an SAObjectType attribute. No view was defined when the menu structure was generated or the symbol's Object Name field is empty Check that the application has a menu structure, see section Furthermore, is there a culture defined for the menu structure? Is it same as the user has, e.g. en. Use the Open With dialog to select the program in which you want to open the file. Check the authorization level or the link target. Add a menu structure manually for the custom object type and ensure that the object has an SAObjectType attribute. Use Display Builder to set the Object Name field for the symbol. Run the menu generator and use a viewpath argument to generate menus for instances Process Display menu A Process Display menu displays both the common parts for the process pictures and the specific parts for the currently active process picture. The menu structure is similar to the Windows Start menu. The menu commands are organized as folders and files in the file system.therefore, no special tool is needed to configure the menu. The configuration is done by organizing the files, such as programs, documents or shortcuts and the directories in a file system. For example, a menu command can be: a file a folder containing submenu commands a link a shortcut to a file a shortcut to a directory an Internet hyperlink 278

279 1MRS MicroSCADA Pro SYS Language support Icon Picture specific menu For more information about the national language support (NLS), refer to Section Language support For more information about the icons, refer to Section Icon. Common files for the process are located in [Appl path]\pict\common_menu\. The files are displayed before the command separator on the Picture Specific menu, see Fig Process Display specific files are separate files. For example, Process Display specific files for Example.v are in [Example]\MENU\, where the [Example] folder is the name of the Process Display file without the suffix v. The picture specific files are displayed after the command separator on the Picture Specific menu, see Fig Fig Picture Specific menu A Opening Visual SCIL tools The Visual SCIL tools can be opened by using a display element Creating subdrawing for Visual SCIL tool 1. Create a subdrawing, for example copy the existing IED.sd file. Any other subdrawing can also be used. The ToolLauncherProgId custom key with the value LIB510RT.LIB510IEDTools must be defined in the view properties of the subdrawing used. 2. To define the custom key, first open the subdrawing in Display Builder Right-click the subdrawing background and select Properties Select the Custom tab and define the custom key by double-clicking the key name on the line Type the appropriate custom key name to the line Taking subdrawing into use 1. Create a new Process Display and import the new subdrawing. 2. Select the object that presents the subdrawing. 3. Add the OpenVso custom key for the object Right-click the object and select Properties. 279

280 SYS MicroSCADA Pro 1MRS Click the Custom tab and define the custom key Create a new custom key by clicking the ( ) button and typing the key name on the line Type OpenVso on the line Define the VSO tool ID as a key value, for example EXAMPLE, see Fig Fig Defining the OpenVso custom key A Tool IDs can be found in the Tools.ini file and each part of the file is a tool ID. If LIB 500 is installed, the file is located in \sc\lib4\base\bbone\use, otherwise it is is located in \sc\stool\misc. 4. Add the VsoAuthGroup custom key for the subdrawing object, and define a authorization group name that specifies the authorization level for the tool in the User Management. The authorization group can be MY_TOOLS, for example. 5. In User Management, add the new authorization group for the users, for example MY_TOOLS. 6. Define the authorization level for the group. If the authorization level is 0, the user is not allowed to open the tool and the error message is displayed. If the level is 1 or higher, the user is allowed to open the tool. 7. Create an ini file for the tool, for example EXAMPLE.INI. Save the file, for example in \sc\apl\510_403_1\aplmod4\use. The ini file contains the following information, provided that the implementation is in EXAMPLE.VSO and the main dialog object name is Main. [EXAMPLE] Tool_Type_=OBJ Tool_Description_=Example Tool 280

281 1MRS MicroSCADA Pro SYS Tool_VSO_File_=EXAMPLE.vso Tool_VSO_Dialog_=Main Tool_VSO_Method_= Tool_Default_Path_= Tool_Ver_Maj_=1.0 Tool_Ver_Min_=2 Tool_Icon_=Product_Icon_M Tool_Exclusive_=1 8. Create the new tool ID to the Tools.ini file by adding the following lines: [EXAMPLE] Tool_Dir_ = \sc\apl\510_403_1\aplmod4\use Command Line Support Open the Application Window from the Command Prompt by using the following parameters: FrameWindow.exe [process event alarm(template) blocking trends(mode) reports( mode) display][event alarm trends reports preconf] -closeonce -disablemousemiddlepan -disablemousewheelzoom -display:ulx,uly,width,height -lang:[lang code] -light -ll:x1,y1 -ur:x2,y2 -coordsys:world screen [Process Display] -login [username] [password][sys600 application] -loginonce -loginscript [file] -loginscriptwithargs [file] -loginruntoolid:[id,size] -loginrunvso:[file,object,look,size,custom] -logoutonce -pid -scold:[.bat file] -sdown:[closemonitorpro closetssession] -silentexit -topmost -tsid -wait [alarm(template) display] Alarm Display to be opened in appropriate template (alarmlist_temp1 alarmlist_temp2). Preconfiguration can be given as an additional argument. 281

282 SYS MicroSCADA Pro 1MRS [blocking display] Blocking Display to be opened (blockinglist). [event display] Event Display to be opened (eventlist). Preconfiguration can be given as an additional argument. [Process Display] Process Display to be opened (path to.v file). [reports(mode) display] Reports Display to be opened in appropriate mode (reports_graphical reports_tabular). Preconfiguration can be given as an additional argument. [trends(mode) display] Trends Display to be opened in appropriate mode (trends_graphical trends_tabular). Preconfiguration can be given as an additional argument. -closeonce Close all Monitor Pros with appropriate user that have the argument defined. -coordsys:world screen Defines the coordinate system if flags -ll and -ur are defined, default is world coordinate system. -display:ulx,uly,width,height Monitor Pro upper left coordinates (ulx,uly), width and height (width,height). -disablemousemiddlepan Disable panning with middle mouse button in Process Display. -disablemousewheelzoom Disable mouse wheel zooming in Process Display. -lang Defines the default language used in Monitor Pro when not logged in to any SYS600 application. -light Starts Monitor Pro without toolbars and menus. -ll:x1,y1 -ur:x2,y2 Lower left (x1,y1) and upper right coordinates (x2,y2) of Process Display area to be zoomed to. -login Login to SYS600 application. If only SYS600 application is given login dialog is shown. Additional argument can be one of the displays. -loginonce Login to SYS600 application that last Monitor Pro has logged to. Additional argument can be one of the displays. -loginscript [file] After successful login the contents of file is executed. -loginscriptwithargs [file] After successful login the contents of file is executed. Monitor Pro specific arguments are provided. -loginruntoolid:[id,size] After successful login scil tool is executed with selected size (0,1,2,3,4). 282

283 1MRS MicroSCADA Pro SYS Tool sizes: 0=640x480,1=960x720,2=1280x960,3=1600x1200,4=1920x loginrunvso:[file,object,look,size,custom] After successful login vso file executed with appropriate object name, modern look&feel (0,1), selected size (0,1,2,3,4) and custom scil attribute value. Tool sizes: 0=640x480,1=960x720,2=1280x960,3=1600x1200,4=1920x logoutonce Logout from all Monitor Pros with appropriate user that have the argument defined. -pid Show Monitor Pro process id in application window title. -scold:[.bat file] When SYS600 is stopped (cold) the contents of.bat file is executed. -sdown:[closemonitorpro closetssession] Close Monitor Pro or Terminal Server Session when SYS600 is stopped. -silentexit Exit Monitor Pro without information messages (autologout, SYS600 stopped...). -topmost Open Monitor Pro as topmost application window. -tsid Show current terminal server session id in application window title. -wait Wait for SYS600 to start. Examples FrameWindow.exe C:\samplepic.v FrameWindow.exe C:\samplepic.v -ll:100,400 -ur:300,500 FrameWindow.exe C:\samplepic.v -display:0,0,400,400 FrameWindow.exe C:\samplepic.v -light FrameWindow.exe alarmlist_temp1 FrameWindow.exe -loginscript C:\samplefile.bat FrameWindow.exe C:\samplepic.v -loginscript C:\samplefile.bat FrameWindow.exe eventlist -loginscript C:\samplefile.bat FrameWindow.exe -login 510_403_1 FrameWindow.exe -login demo "" 510_403_1 FrameWindow.exe -login demo "" 510_403_1 C:\samplepic.v FrameWindow.exe -login demo "" 510_403_1 trends_graphical my_trend_preconf FrameWindow.exe -login demo "" 510_403_1 alarmlist_temp1 my_alarm_preconf FrameWindow.exe -login demo "" 510_403_1 eventlist my_event_preconf FrameWindow.exe -loginonce C:\samplepic.v FrameWindow.exe -loginonce alarmlist_temp1 FrameWindow.exe -loginonce -loginscript C:\samplefile.bat FrameWindow.exe -loginonce eventlist -loginscript C:\samplefile.bat 283

284 SYS MicroSCADA Pro 1MRS Starting Monitor Pro with a delay If Monitor Pro is started by using the -wait command line argument, SYS 600 is started with a delay and the Monitor Pro - Waiting dialog is displayed, see Fig The command line argument can be used when the Monitor Pro program file (exe) is added to the Start menu, for example. Clicking Skip Waiting opens Monitor Pro but the connection to SYS 600 is not established. Clicking Exit Monitor Pro closes Monitor Pro. Fig Monitor Pro Waiting dialog A When SYS 600 is running, the Monitor Pro login dialog is displayed. For more information about login in Monitor Pro, refer to Operation Manual Customizing Monitor Pro appearance Authorized users can customize Monitor Pro, for example by creating new menus and toolbars. After customizing the appearance, the corresponding file is updated. For more information about the customization file, refer to Table When logging on, the project and application specific appearances are synchronized with the user specific appearance. Therefore, the user specific appearance is up-to-date. For more information about authorization levels, refer to Chapter 18. Authorization. The availability of the application and system specific appearances are checked when a user logs in. The toolbars are also synchronized. The unique IDs of the toolbar in the application and the system specific appearances are compared with the IDs in the user specific appearance. The unique ID is generated when the toolbar is set as application or system specific. The ID is also saved to the user specific appearance. When the user logs in and the ID does not match with the user specific appearance, the contents of application or system specific toolbar is copied to the user specific appearance. Toolbars and menus can be set as system or application specific in the customization mode in Monitor Pro. For example, right-click a toolbar and select Set as System Specific or Set as Application Specific, see Fig For more information about the customization mode, refer to Chapter 13. Customizing application 284

285 1MRS MicroSCADA Pro SYS window. The whole toolbar or menu is set as system or application specific, and it is updated for other users when they log in. By default, the toolbar is visible in every display. If the toolbar is closed, it is not visible in the display in question. Fig Setting toolbar visibility Toolbar names support translation. For more information about translating the application specific appearance, refer to Section Translating user interface components. Table Customization files A File path Use \sc\prog\sa_lib\sdiactivebar.tb2 A default appearence for the user. \sc\prog\sa_lib\default_sdiactivebar_prj.tb2 System specific appearance, which includes system specific toolbars and which is synchronized with the user specific appearance when user logs in. \sc\prog\sa_lib\default_sdiactivebar.tb2 \sc\prog\sa_lib\default_sdiactivebar.chg The apperance used when the user is logged off. 285

286 SYS MicroSCADA Pro 1MRS Table Customization files (Continued) File path \sc\apl\[appl]\par\[user]\sdiactivebar.tb2 \sc\apl\[appl]\par\[user]\sdiactivebar.chg \sc\apl\[appl]\par\apl\sdiactivebar_apl.tb2 You can customize the menu commands as follows: Moving, deleting, copying and resetting menu commands. Resetting loads the last appearance saved. Changing the caption and tooltip. Copying, pasting and changing an icon. While changing an icon, select a new icon from a file. For more information about icons, refer to Section Context-sensitive shortcut menus. Changing a style to one of the following: default, text and image, or image and text. For more information about appearance modes, refer to Section Customization dialog. Creating a new menu command. A new menu uses an existing menu as a template, that is, the menu name and style is copied from the existing menu. For more information about creating a new menu command, refer to Section Adding new menus and toolbars. Adding custom menu commands, for example execute command line and execute SCIL. For more information about custom commands, refer to Section Authorizing If the main menu, a custom command with display or a picture specific menu with process graphics display, is not defined. For more information about authorization levels, refer to Chapter 18. Authorization. You can customize the toolbar buttons as follows: Use The user specific appearance. Application specific appearance, which includes application specific toolbars and which is synchronized with the user specific appearance when the user logs in. Creating, copying, moving, renaming, deleting and resetting toolbar buttons. Resetting loads the last appearance saved. Changing the caption and tooltip. Copying, pasting and changing an icon. For more information about icons, refer to Section Context-sensitive shortcut menus. Changing the appearance mode to one of the following: default, text and image, or image and text. For more information about styles, refer to Section Customization dialog. Creating a new menu command or a toolbar button. For more information about creating a new menu command, refer to Section Authorizing It is not possible to authorize the general toolbar buttons and application picture 286

287 1MRS MicroSCADA Pro SYS toolbar buttons. For more information about authorization levels, refer to Chapter 18. Authorization User specific appearance The user specific appearance defines the basic appearance for the user, for example toolbars and menus. The layout file is SDIActiveBar.tb2 and it can be found in \sc\apl\[appl]\par\[user]. The user specific appearance consists of the following files: The TB2 file is the layout file including menus, toolbars, menu commands, toolbar buttons, icons and so on. The CHG file includes the layout changes, for example toolbar positions. The MNU file is used when the personalized menus and toolbars are taken into use in the Customization dialog. The default layout file for all users is located in \sc\prog\sa_lib. By default, the project and application specific layout files do not exist in a user specific folder. Copy the files to the folder. In addition, copy the files to the user specific folder used for translation. The Monitor Pro apperance changes are saved in the user specific file. For more information about translating the user specific appearance, refer to Section Translating user interface components Application specific appearance The application specific layout file is SDIActiveBar.tb2 and it is located in \sc\apl\[appl]\par\apl. If a toolbar is set as application specific, the toolbar is copied to the application specific layout either from the user specific layout or from the system specific layout. The application specific layout is generated, if it does not exist. When logging in to the appropriate application next time, the toolbar is copied to the user specific layout. For more information about translating the application specific appearance, refer to Section Translating user interface components System specific appearance The system specific layout file is SDIActiveBar_Prj.tb2 and it can be found in \sc\prog\sa_lib\.if a toolbar is set as system specific, it is copied either from the user specific layout or from the application specific layout to the system specific layout. The system specific layout is generated, if it does not exist. When logging in to an application next time, the toolbar is copied to the user specific layout. For more information about translating the system specific appearance, refer to Section Translating user interface components. 287

288 SYS MicroSCADA Pro 1MRS Defining shortcuts to Process Displays The user access rights can be restricted by showing the needed Process Displays as shortcuts. The user can only open the Process Displays shown in a toolbar, if the shortcut files have been defined. Process Display shortcuts are configured using the Process Display Shortcut Configuration Tool on the Process Display toolbar, see Fig : Fig Process Display Shortcut Configuration Tool Clicking on the Process Display Shortcut Configuration Tool opens the Process Graphics Displays Visibility dialog, shown in Fig : Fig Process Graphics Displays Visibility dialog The Process Displays currently available for current SYS600 application are shown in the left window. The right window displays the currently visible Process Display Shortcuts. Visibility is configured to be either Application specific of User specific. Application specific visibility allows all the users in current SYS600 application to access the configured Process Displays. User specific visibility allows a selected user access to the configured Process Displays To enable the Process Display shortcut: 1. Select the required Process Display shortcut from the left window. 2. Click the button with right-facing arrows ( >> ) 288

289 1MRS MicroSCADA Pro SYS Select the required Visibility by checking the appropriate radio button. If User specific visibility is selected, select the required user from the Users window to the right. 4. Click OK to apply the changes. An authorization level 5 defined in GENERAL authorization group is required to make Process Display Shortcut modifications. The following operations are unavailable for the user: Opening Process Displays by using the menu operation Main > Open File. Dragging Process Displays to an application window. Custom commands related to opening the Process Displays are blocked. 289

290 SYS MicroSCADA Pro 1MRS Shortcut files must be shortcut files at the operating system level. Copying the picture is not the right way to create the shortcuts. Application specific Process Display shortcuts are shown to all users. The shortcut files are located in [Appl path]\par\apl\process\ TOOLBAR_SHORTCUTS. The user is not allowed to open Process Displays that are not defined on toolbar of the application specific Process Displays. User specific Process Display shortcuts are shown individually to each user. The user specific shortcut files are located in [User path]\process\ TOOLBAR_SHORTCUTS. The user is not allowed to open Process Displays that are not defined on toolbar of the user specific Process Displays. If the user specific shortcut files exists, the application specific files are ignored Hiding Process Displays from Process Displays Toolbar It may also be required to hide a Process Display from the Process Displays Toolbar. This is achieved by changing the file attributes of the specific Process Display File (.v file), through the file properties context menu in Windows Explorer Custom commands in Monitor Pro New menu commands and toolbar buttons can be configured to act as custom commands. The function for the menu command and toolbar button can be changed in the customization mode in Monitor Pro. Custom commands can also be defined for the process graphics objects. For more information about creating a new menu, refer to Section Adding new menus and toolbars. Custom commands provide functions for opening a display executing a command line executing a SCIL opening a VSCIL tool setting an alarm indicator Custom commands support translation. For more information about translating the application specific appearance, refer to Section Translating user interface components. Monitor Pro supports drag and drop from Windows Explorer. Files of the appropriate format can be selected in Windows Explorer, dragged and then dropped to any toolbar in Monitor Pro. Suported file types are:.v - open display, see Section Opening display..vso - visual scil tool opening, see Section Defining Visual SCIL tool file. 290

291 1MRS MicroSCADA Pro SYS scil - Section Running SCIL. Files that are not supported by Monitor Pro will be excecuted from the command line and opened by the operating system, see Section Running Command Line. The use should be at least authorization level 2 in authorization group PRO_CONFIG_COMMANDS in order to add Custom Commands. Authorization level 1 is required in PRO_MENU_CUSTOMIZE authorization group if custom commands are to be dropped to menus and PRO_TOOLBAR_CUSTOMIZE if dropped to toolbars Opening display The open display function opens a defined display with specific settings. The display can be opened in the same or in a new application window. To define a display to be opened: 1. Select Tools > Customize to open the Customize dialog. 2. Right-click a menu or a toolbar and select Open Display. 291

292 SYS MicroSCADA Pro 1MRS The Specify Display dialog is displayed, see Fig Fig Specifying an opened display A Alarms 4. Select a display to be opened in the Display type box. 5. Select a display to be opened in the Arguments field. 6. The Predefined Values box displays the default functions. 7. Select the necessary check boxes in the Monitor Pro Application Window field. If the New window check box is selected, the Process Display is opened in a new window. If the Light Version check box is selected, the window does not contain buttons or menus, and therefore only the Process Display is displayed in a window. 8. Click OK to confirm the selection. A.v file can also be dragged from Windows Explorer and dropped to the required toolbar or menu in Monitor Pro. The alarms function opens the Alarm List Template 1 or Alarm List Template 2 display with defined filters. The display can be opened in the same or in a new application window. 292

293 1MRS MicroSCADA Pro SYS Blockings Events Trends Alarm List Template 1 Select Alarm List Template 1 in the Display type box. Select a display to be opened in the Arguments field. If filters are defined for the selected display, they are displayed in the Predefined Values box. Alarm List Template 2 Select Alarm List Template 2 in the Display type box. Select a display to be opened in the Arguments field. If filters are defined for the selected display, they are displayed in the Predefined Values box. The blocking function opens the Blocking display with defined preconfigurations. The display can be opened in the same or in a new application window. Select Blocking Display in the Display type box. Select a display to be opened in the Arguments field. If preconfigurations are defined for the selected display, they are displayed in the Predefined Values box. The events function opens the Event display with defined filters. The display can be opened in the same or in a new application window. Select Event Display in the Display type box. Select a display to be opened in the Arguments field. If filters are defined for the selected display, they are shown in the Predefined Values box. The trends function opens the Trends display in a graphical or tabular mode. A display can contain preconfigurations. The display can be opened in the same or in a new application window. Trends Display Graphical Mode Select Trends Display Graphical Mode in the Display type box. Select a display to be opened in the Arguments field. If preconfigurations are defined for the selected display, they are displayed in the Predefined Values box. Trends Display Tabular Mode Select Trends Display Tabular Mode in the Display type box. Select a display to be opened in the Arguments field. 293

294 SYS MicroSCADA Pro 1MRS Measurement Reports Process graphics If preconfigurations are defined for the selected display, they are displayed in the Predefined Values box. The measurement reports function opens the Measurement Reports display in a graphical or tabular mode. The display can contain preconfigurations. The display can be opened in the same or in a new application window. Measurement Reports Display Graphical Mode Select Measurement Reports Display Graphical Mode in the Display type box. Select a display to be opened in the Arguments field. If preconfigurations are defined for the selected display, they are displayed in the Predefined Values box. Measurement Reports Display Tabular Mode Select Measurement Reports Display Tabular Mode in the Display type box. Select a display to be opened in the Arguments field. If preconfigurations are defined for the selected display, they are displayed in the Predefined Values box. Custom commands can also be defined for the process graphics objects. Current process graphics picture Opens the Process Graphics display with the defined process graphics picture. The display can be opened in the same or in a new application window. Select Current process graphics picture in the Display type box. Select a display to be opened in the Arguments field. Current process graphics picture with current zoom area Opens the Process Graphics display with the zoomed area of the defined process graphics picture. The display can be opened in the same or in a new application window. Select Current process graphics picture with current zoom area in the Display type box. Select a display to be opened in the Arguments field Renaming Process Display To renaming Process Display: 1. Select Tools > Customize... to open the Customize dialog. 2. Right-click on the Process Display name. 3. Select Name and enter new name for the Process Display. See Fig : 294

295 1MRS MicroSCADA Pro SYS Fig Opening the localization dialog Running Command Line Runs the defined command lines. Table shows the parameters of the command lines that can be defined in a BAT, COM, SCIL, VBS or VSO file. It is possible to define whether the parameters are provided for the EXE files. Table Parameters for the command lines Parameter Description 1 SYS 600 user name 2 SYS 600 user authorization level (GENERAL) 3 SYS 600 user authorization level (TOOLS) 4 SYS 600 user authorization level (ALARM_HANDLING) 5 SYS 600 user authorization level (EVENT_HANDLING) 6 SYS 600 user authorization level (REPORTS) 7 SYS 600 user language 8 SYS 600 user path 9 SYS 600 application name 10 SYS 600 application number 11 SYS 600 installed drive 12 SYS 600 application path 13 SYS 600 application is a LIB application 14 SYS 600 application is a prepared LIB application 295

296 SYS MicroSCADA Pro 1MRS Table Parameters for the command lines (Continued) Parameter Description 15 Current open picture file path 16 Monitor Pro window handle 17 Monitor Pro process ID 18 Terminal server sessions identifier 19 Mouse pointer X coordinate, Mouse pointer Y coordinate 20 Object name (reserved for shortcut menus), in this case empty 21 OPC item ID (reserved for shortcut menus), in this case empty 22 Configured authorization group for current item 23 Configured authorization level for current item 24 Real authorization for the current item in the SYS 600 user management Define a command line to be run: 1. Select Tools > Customize to open the Customize dialog. 2. Right-click a menu or a toolbar and select Execute Command Line. 296

297 1MRS MicroSCADA Pro SYS The Specify Command Line dialog is displayed, see Fig Fig Specifying a command line A Select a file to be run in the Executable field. 5. Select a file to be opened in the Arguments field. 6. If you want to use the Monitor Pro specific arguments, select the Provide Monitor Pro Specific Arguments check box. 7. Click OK to confirm the selection. Any excutable file can be dragged from Windows Explorer and dropped to the required toolbar or menu in Monitor Pro Running SCIL To define a SCIL file to be run: 1. Select Tools > Customize to open the Customize dialog. 2. Right-click a menu or toolbar and select Execute SCIL. 3. The Specify SCIL File dialog is displayed, see Fig Fig Specifying a SCIL file A Select a SCIL file to be run by clicking Select File. the full path is required. 5. After selecting a SCIL file, you can edit the SCIL file by clicking Edit. create a new SCIL file by clicking New File. delete the SCIL file by clicking Delete File. 6. Click OK to confirm the selection. 297

298 SYS MicroSCADA Pro 1MRS A.scil file can also be dragged from Windows Explorer and dropped to the required toolbar or menu in Monitor Pro. Table shows the arguments for executing SCIL. 298

299 1MRS MicroSCADA Pro SYS Table Arguments for executing SCIL Argument Description USER_NAME SYS 600 user name GENERAL_AUTH_LEVEL SYS 600 user authorization level (GENERAL) TOOLS_AUTH_LEVEL SYS 600 user authorization level (TOOLS) ALARM_HANDLING_AUTH_LEVEL SYS 600 user authorization level (ALARM_HANDLING) EVENT_HANDLING_AUTH_LEVEL SYS 600 user authorization level (EVENT_HANDLING) REPORTS_AUTH_LEVEL SYS 600 user authorization level (REPORTS) USER_LANG SYS 600 user language USER_PATH SYS 600 user path MSCADA_APP_NAME SYS 600 application name MSCADA_APP_NUM SYS 600 application number MSCADA_INSTALLED_DRIVE SYS 600 installed drive MSCADA_APP_PATH SYS 600 application path IS_LIB_APP SYS 600 application is a LIB application IS_PREPARED_LIB_APP SYS 600 application is a prepared LIB application PROCESS_GRAPHICS_PIC_PATH Current openpicture file path WINDOW_HANDLE Monitor Pro window handle PROCESS_ID Monitor Pro process ID TERMINAL_SERVER_ID Terminal server sessions identifier MOUSECOORDS Mouse pointer X coordinate, Mouse pointer Y coordinate CURRENT_CONF_AUTH_GROUP Configured authorization group for current item CURRENT_CONF_AUTH_LEVEL Configured authorization level for current item CURRENT_REAL_AUTH_LEVEL Real authorization for the current item in the SYS 600 user management Opening Visual SCIL tool Opening a Visual SCIL tool can be defined by selecting the tool form the list or by definig the file used Selecting Visual SCIL tool from list To select a Visual SCIL tool to be opened from the list: 1. Select Tools > Customize to open the Customize dialog. 2. Right-click a menu or toolbar and select Open Visual SCIL Tool (tool id). 299

300 SYS MicroSCADA Pro 1MRS The Specify SCIL Tool dialog is displayed, see Fig Fig Specifying a SCIL tool 4. Select the SCIL tool used from the Predefined Values list. 5. Click OK to confirm the selection. A A.vso file can also be dragged from Windows Explorer and dropped to the required toolbar or menu in Monitor Pro Defining Visual SCIL tool file To define a file of the Visual SCIL tool: 1. Select Tools > Customize to open the Customize dialog. 2. Right-click a menu or toolbar and select Open Visual SCIL Tool (vso file). 3. The Specify SCIL Tool dialog is displayed, see Fig

301 1MRS MicroSCADA Pro SYS A Fig Selecting a VSIL tool to be run 4. Define the VSCIL tool used in the Specify VSCIL Tool dialog. File Specify the VSO file path and file name containing the dialog that is opened. Create the VSO files by using the Visual SCIL editor. For more information about editing Visual SCIL dialog, refer to Visual SCIL. Object Name Specifies the object name in the VSO file that is opened. The object type must be VS_DIALOG or VS_MAIN_DIALOG. It is required to define the object name, because a VSO file can contain several dialogs. Custom SCIL Attribute Value Optional information that can be passed in the dialog object at start-up. The field s value is evaluated as a SCIL expression, see Table Table Examples of SCIL expressions Expression SCIL data type "Some text" TEXT VECTOR( A,!) VECTOR LIST(LN= ABC, IX=10) LIST 5.0 REAL In option group "Tool Appearance" some settings for the visual scil tool can be defined. Tool size Defines size setting used for semigraphics tools opened from this visual scil 301

302 SYS MicroSCADA Pro 1MRS tool. This setting is equivalent to setting monitor size when opening classic monitor. Note that this setting affects only the VSO tool opened from the menu item/toolbar button and it it does not affect appearance of VSO tool itself. Use modern style Defines the look and feel of Visual SCIL controls that are used in the VSO dialog. When this Use Modern Style is checked, dialog controls are displayed in the same style as Windows dialogs, as shown in the left image of Fig The default style is shown to the right of Fig Fig Effect of Use Modern Style Setting alarm indicator Define and monitor the state of the configured alarm indicators based on the value in the OPC Item. The configured alarm states are described in Table Table Configured alarm indicator states State Description Example 0 No active unacked alarms The configured menu command is disabled. 1 Active alarms that are not uncacked The configured menu command not blinking 2 Active and unacked alarms The configured menu command is blinking To set an alarm indicator for the current tool: 1. Select Tools > Customize to open the Customize dialog. 2. Right-click a menu or toolbar and select Set Alarm Indicator. 302

303 1MRS MicroSCADA Pro SYS The Set Alarm Indicator dialog is displayed, see Fig Used OPC items are displayed in a Used OPC Items field. Free OPC items are displayed in a Free OPC Items field. Fig Setting an alarm indicator A Set an alarm indicator by selecting a free OPC item. 5. Click Select to confirm the selection. The selected alarm indicators are displayed in the Selected OPC Items field. You can remove the selected alarm indicators by clicking Remove. 6. Click OK to confirm the selection. 303

304 304

305 1MRS MicroSCADA Pro SYS Localizing application Translantions of the text are included in the SYS 600 Visual SCIL Objects Manual. For example, button labels and menu texts are normally defined by using Dialog Editor and stored in same objects. For more information on using language dependent texts, refer to the SYS 600 Visual SCIL Manual. Other translations of the application texts, for example texts describing process objects and their states, are stored in the text databases. The texts are translated explicitly by the TRANSLATION function, or implicitly by referencing the object s language sensitive attribute. Text Translation Tool translates the texts. To save the translation, you can use a Windows based localization tool, such as RCWinTrans, Multilizer or Lingobit Localizer. For example, the Lingobit Localizer can be downloaded from Language identifiers It is recommended, but not required, that the two letter language identifiers which are used in the applications are defined by the ISO standard 639. When ISO 639 language identifiers are used, the system is able to map the Windows language ID's, which are derived from the Windows locale ID's, to the language identifiers of applications. Consequently, the OPC clients connected to the SYS 600 OPC Data Access Server may define their language by the means specified in the OPC standard. The SYS 600 base system automatically converts the Windows language ID s to the ISO 639 language identifiers. For more information on using language functions, refer to the SYS 600 Programming Language SCIL Manual Text Translation Tool In the SYS 600 application, there is a large amount of language dependent text, which has to be translated. Text Translation Tool can be used to translate the SYS 600 system s different file formats. For more information on using Text Translation Tool, refer to SYS 600 Installation and Commissioning Manual Text databases The translations of application texts are stored in data files called text databases. The databases have three different scopes for different needs of software components using translated texts: 1. The application text database, APL_TEXT.sdb, is designed to contain the site specific texts of the application. 2. The text databases listed by the application attribute, APL:BTD, are used by various software products, such as LIBxxx products and their localizations. 3. The system text database, SYS_TEXT.sdb, is delivered with the product and should not be modified. The databases are searched in the scope order, APL_TEXT.sdb first and SYS_TEXT.sdb last. 305

306 SYS MicroSCADA Pro 1MRS It is not allowed to modify SYS_TEXT.sdb by any tool or SCIL programming language. A later version of SYS 600 always overrides this file Monitor Pro, tools and components Monitor Pro and some other SYS 600 components use the satellite resource Dynamic Linking Libraries (.dll) to store resources. In this method, each supported language has its resources in a separate dll. Each dll uses the same resource identifiers, but also contains strings in the appropriate language. Each dll s name and directory indicates the language of its resources. For example, Monitor Pro has executable \sc\prog\sa_lib\framewindow.exe, which loads its EN resources from \sc\prog\sa_lib\en\framewindow_en.dll. These language dlls can be translated by using a third party software. Table DLLs that can be translated Dll name (default installation path c:\sc\prog\sa_lib\en) Description alarmctl_en.dll Resources for the alarm list Basket_texts_EN.dll Resources for the trend basket 1 blockingctl_en.dll Resources for the blocking list BusbarColoring_EN.dll Resources for the network topology coloring ControlDialog2_EN.dll Resources for the control dialogs eventctl_en.dll Resources for the event list FrameWindow_EN.dll Resources for the Monitor Pro MeasReports_texts_EN.dll Resources for the measurement reports MSCGraph_texts_EN.dll Resources for the graph control 1 Options_EN.dll Resources for the option dialog TrendApp_texts_EN.dll Resources for the trend display 1 1. FrameWindow.exe -loginonce eventlist -loginscript C: \samplefile.bat For more information about FrameWindow program file (.exe), refer to Section Command Line Support Basic workflow of localization All the separate tasks listed below are not needed, but they are recommended to get the whole Operator user interface translated for the selected application. SYS 600 system tools translation. All SYS 600 tools (\sc\stool\), which the operator uses daily, need to be translated either by using Visual SCIL Editor or Text Translation Tool. If the application is LIB 500 based, the LIB 500 and other needed LIBxxx based applications need to be translated by using Text Translation Tool. Translate Monitor Pro, tools and its components Translating the SYS 600 System Texts: 1. Shutdown SYS

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

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

309 1MRS MicroSCADA Pro SYS Basic work flow in translating Monitor Pro, tools and components Here is an example on how to use the Lingobit Localizer in translation. When you start the Lingobit Localizer, it creates a new project or loads an existing project automatically. The c:\data project location is used in the example below. 1. Fill in the Name field with the project name and click Browse to find the project location, see Fig A Fig Main window of the Localizer and the Project Wizard dialog 2. Click Next to open the list of dll files, see Fig Click Add if you want to add more files, and Remove if there are unnecessary files on the list. Fig List of dll files to be translated A

310 SYS MicroSCADA Pro 1MRS Click Next to open the dialog for selecting the languages, see Fig Select the original language from the drop-down list and click Add to select the target language. Fig Selecting the original and target languages 6. Click Next to open the list of dll files in the application window. The list is shown on the left side of the window, see Fig A Fig List of dll files in the application window A

311 1MRS MicroSCADA Pro SYS Click the dll files to see the strings to be translated. The resources are collected to a string table, and all the strings in each table should be translated, see Fig Fig String table in the application window A

312 SYS MicroSCADA Pro 1MRS Click the string you want to translate and type in the translation in the language column. The strings that are not translated use the original language, see Fig Fig EN translation in the application window 9. When you have done the translations, save them by selecting Edit >Save. 10.To generate the dll files, open the Language to export dialog by selecting Project > Create Localized Files, see Fig Select the language to which the dll files are generated to and click OK. A

313 1MRS MicroSCADA Pro SYS Fig Generating the translation 12.You can find the translated dll files where the project was created, which is c:\data\sys600 in this example, see Fig Depending on your project setup and the generated languages, there is a directory for each language. As only Finnish language was generated in this example, there is only one subdirectory in the project structure c:\data\sys600\finnish-finland. A Fig Contents of the localized files 13. When you have generated the files, they should be copied from the project directory to c:\sc\prog\sa_lib\fi and renamed according to Table A

314 SYS MicroSCADA Pro 1MRS Table Renamed dll files DLL name (default installation path c:\sc\prog\sa_lib\en) Alarmctl_en.dll New name, if translated to "Finnish- Finland" Alarmctl_fi.dll Basket_texts.dll Basket_texts.dll 1 Blockingctl_en.dll Blockingctl_fi.dll BusbarColoring_en.dll BusbarColoring_fi.dll ControlDialog_en.dll ControlDialog_fi.dll Eventctl_en.dll Eventctl_fi.dll FrameWindow_en.dll FrameWindow_fi.dll LIB510RelayTools_en.dll LIB510RelayTools_fi.dll MSCGraph_texts.dll MSCGraph_texts.dll 1 Options_en.dll Options_fi.dll TrendApp_texts.dll TrendApp_texts.dll 1 1. These dll files do not require the language id as part of they name. It is not allowed to modify anything else but the strings in the resource dll files Translating user interface components You can translate menus, toolbars and custom commands in the customization mode. For more information about Customization dialog, refer to Chapter 13. Customizing application window. Define the visibility for the custom commands before translation. For more information about the visibility, refer to Section Customizing Monitor Pro appearance. The localization information for the system specific toolbars and custom commands is saved to \sc\prog\sa_lib\default_framewindow.ini. The localization information for the application specific toolbars and custom commands is saved to \sc\apl\[appl]\par\apl\framewindow.ini. The localization information for the user created menus, toolbars and custom commands is saved to \sc\apl\[appl]\par\[user]\framewindow.ini. For more information about Monitor Pro appearances, refer to Section Customizing Monitor Pro appearance. For the default toolbars and menus, the localization information is presented in the language specific satellite resource Dynamic Linking Library (DLL). For more information about DLLs, refer to Section Monitor Pro, tools and components Translating system and application specific toolbars To translate a toolbar: 1. Select Tools > Customize to open the Customize dialog. 314

315 1MRS MicroSCADA Pro SYS Right-click a component and select Localize to open the Localize dialog, see Fig and Fig Fig Opening the localization dialog A Fig Localization dialog A Select the In Use check box in the Localizations field or the User Definition field. Select the check box in the Localizations field, if you want to use the defined translations. Select the check box in the User definition field, if you want to use the user specific definition. 315

316 SYS MicroSCADA Pro 1MRS To use a translation: 1. Select the In Use check box in the Localizations field, see Fig Click New to add a new translation. 3. Select the target language, see Fig Fig Selecting a target language A Click OK to confirm the target language. 5. Type the translation in the Name box, see Fig

317 1MRS MicroSCADA Pro SYS Fig Typing a translation A Click OK to save the translation. To use the user specific definition: 1. Select the In Use check box in the User Definitions field, see Fig Type the user specific definition in the Name box. 3. Click OK to save the definition Translating custom commands To translate a custom command: 1. Select Tools > Customize to open the Customize dialog. 2. Right-click a component and select Localize to open the Localize dialog, see Fig and Fig Fig Opening the localization dialog A

318 SYS MicroSCADA Pro 1MRS Fig Localization dialog A Select the In Use check box in the Localizations field or the User Definition field. Select the check box in the Localizations field, if you want to use the translations. Select the check box in the User definition field, if you want to use the user specific definition. To use a translation: 1. Select the In Use check box in the Localizations field, see Fig Click New to add a new translation. 318

319 1MRS MicroSCADA Pro SYS Select the target language, see Fig Fig Selecting a used language 4. Click OK to confirm the target language. 5. Type the translation in the Name box, see Fig A

320 SYS MicroSCADA Pro 1MRS Type a short description of the component in the Tooltip box, see Fig The tooltip is shown when the cursor points to the custom command. Fig Typing a translation A Click OK to save the translation. To use a user specific definition: 1. Select the In Use check box in the User Definition field, see Fig Type the user specific definition in the Name box. 3. Type a short description of the component in the Tooltip box. The tooltip is shown when the cursor points to the custom command. 4. Click OK to save the definition. 320

321 1MRS MicroSCADA Pro SYS Fig Defining a user specific translation A Click OK to save the translation Removing translation To remove a translation: 1. Select Tools > Customize to open the Customize dialog. 2. Right-click a component and select Localize to open the Localize dialog. 3. Click Remove either in the Localizations field or in the User Definition field. 4. Click OK to remove the translation Adding new language in Monitor Pro In Monitor Pro, the operator language is based on the current user language. The user language can be changed from the User Management Tool and taken into use in the next login Using Asian characters To view the Asian characters correctly: 1. To change the Windows language settings, select Start > Control Panel > Regional and Language Options. 2. Select the Languages tab to set the input language according to the local language to enable writing of the special characters: 321

322 SYS MicroSCADA Pro 1MRS Click Details to open the Text Services and Input Languages dialog Select the Settings tab and click Add to open the Add Input Language dialog To add an input language, select the appropriate language from the Input language drop-down list. If the Keyboard layout/ime check box is selected, it is possible to write, for example, the Chinese characters with the keyboard Click OK If the Visual SCIL tools do not accept the special characters from the keyboard, set the language used as a default input language by selecting the appropriate language from the Default input language drop-down list Click OK. 3. Select the Advanced tab to set the local language as a system locale and load the code pages: 3.1. Select the appropriate language from the Language for non-unicode programs drop-down list. Load the Asian characters, before selecting them as system locale. To load the characters select the Languages tab and select the Install files for East Asian languages check box. Click Apply To display the text correctly, use the fonts that contain the local language characters or load more code pages. In the Code page conversion tables field, select the appropriate code pages to be loaded Click Apply. If it is not possible to write the characters directly, keystrokes can be used. To write a special character, press Alt and type the character code, for example Use the Windows Character Map tool, to find out the correct character code. You can also paste the character to the Visual SCIL text field. To open the Character Map tool, select Start > Programs > Accessories > System Tools > Character Map. 4. Click OK and restart the computer so that the new setting takes effect. Use Text Translation Tool to translate a new language in MicroSCADA Pro. For more information about Text Translation Tool, refer to Installation and Commissioning Manual. To take the user language into use, refer to Section Adding new language in Monitor Pro. 322

323 1MRS MicroSCADA Pro SYS Saving Customized Application Search Path and Relative Paths in Process Displays In Monitor Pro and Display Builder, there is an internal search path that is used to convert relative file paths to absolute file paths in runtime when searching for subdrawings, Process Displays, input object layout files, bitmaps and so on, from disk. The search path contains the following directories: \sc\apl\<application name>\pict\ \sc\apl\<application name>\aplmod4\palette\ :\sc\prog\graphicsengine\palette\ \sc\prog\graphicsengine\etc\ \sc\prog\graphicsengine\lib\ \sc\prog\graphicsengine\lib\views\ \sc\prog\graphicsengine\lib\fonts\ \sc\prog\graphicsengine\lib\templates\ \sc\prog\graphicsengine\lib\templates\drawings\ \sc\prog\graphicsengine\support\ If the AplMod4\Palette\ directory is manually created afterwards, Monitor Pro and Display Builder have to be restarted to take it in use. When, for example, a subdrawing object is added to a Process Display, the related subdrawing file can be referenced in three different ways: Absolute full path, for example, C:\sc\prog\graphicsEngine\Palette\01 - SA_Common\Generator.sd A full path without the drive letter, for example, \sc\prog\graphicsengine\palette\01 - SA_Common\Generator.sd A relative path containing only the Palette tab name and the subdrawing file name, for example: 01 - SA_Common\Generator.sd The relative path is the recommended way and the default when for example, a subdrawing is added from Palette or Object Browser. The absolute full path is the default whenever for example, a subdrawing is added or changed by browsing the file system. It should always be manually changed to back to relative path, or at least the drive letter should be extracted away. 323

324 324

325 1MRS MicroSCADA Pro SYS System Self Supervision System Self Supervision (SSS) is used for supervising and monitoring the system. It provides status information of hardware and software used by the Monitor Pro symbols Supervision Application Objects Communication Supervision Application Objects provide communication status information of the supervised components in the system. The status information provides two values, one value indicates a good status and another value indicates a bad status. The status of the supervised components is shown by color indications in Supervision Display. Communication can be based either on IEC or on PC-NET. For IEC OPC Server, the supervision is based on mapping the specific OPC Item that locates on the IEC OPC Server. For PC-NET, the supervision is based on cyclical reading of the PC-NET internal communication line. In both cases, the binary input process object is found in the process database Station The station object supervision depends on the used protocol. If stations are connected through the IEC communication protocol, the station supervision is based on mapping the Device Connection Status OPC item that locates on the IEC OPC server. If other protocols are used, the station supervision is based on mapping the system message process object received from PC-NET. In both cases, the binary input process object is found in the process database Supervision Monitoring Supervision Monitoring provides supervision of a running system through dynamic symbols SA symbols The Display Builder palette contains SA symbols for System Self Supervision, see Table For more information about using the Display Builder palette, refer to the Process Display Design manual. Table SA symbols for System Self Supervision Functionality File name Symbol Base System Angled PC.sd 325

326 SYS MicroSCADA Pro 1MRS Table SA symbols for System Self Supervision (Continued) Functionality File name Symbol Monitor Monitor.sd Application Communication Communication Line Decrease.sd Station IED.sd LON Clock Master Satellite dish -white.sd Printer Laser printer.sd After adding dynamics to the supervision symbols, the symbols reflect the communication status of the components in the system. To take dynamics in use: 1. Define the location of the dynamics in a symbol. 2. Define settings for the dynamics. 3. Save the supervision display Defining object dynamics location in symbol Use the Objects toolbar of Display Builder to include the dynamics in a supervision symbol. The Objects toolbar displays buttons for a graphical object that can be created. For more information about the Object toolbar, refer to the Process Display Design manual. Define the dynamics either inside or beside the symbol. It is possible to add dynamics inside the symbol to save the space. In Fig , the green color indicates an active monitor where the operator is logged in. The grey color indicates a passive monitor. If there is no suitable area inside the supervision symbol that could be used for dynamics, it is recommended to place the dynamics beside the symbol. In Fig , the dynamics are included in a rectangle beside a static symbol. Fig Dynamics inside the symbol A

327 1MRS MicroSCADA Pro SYS Fig Dynamics beside the symbol A Settings object dynamics Object dynamics can be set in Display Builder. Select the Dynamic tab in the Object Properties dialog. The related Data Variable for a source application object is mapped to the selected property of an object. For more information about setting object dynamics, refer to the Process Display Design manual. It is required to set the minimum and maximum values for the object. When using Threshold Editor, the possible values of Data Variable are mapped to use certain colors, see Table After defining the threshold values for a supervision symbol type, save the definitions to the threshold file. After that, load the threshold file for every supervision symbol that has the same threshold value semantics Saving supervision display Before saving the supervision display, select the graphical objects. Select Actions > Remove Selected Objects from Topology. The action ensures, that Network Topology Coloring ignores that supervision display in Monitor Pro Supervising base system It is possible to map Data Variable to a memory type of data variable. In the supervision display the memory type of data variables are mapped to the application objects one per object. Table Threshold colors Color Index Description Green 32 Logical normal color. By default, green. Red 46 Logical alarm color. By default, red. Gray 14 By default, gray When using the SYS:Bnn attributes as a source for a base system supervision, a computer name, see Table , a node number and a station address can be shown beside the base system symbol, see Fig

328 SYS MicroSCADA Pro 1MRS Fig Base system supervision symbol A Table SYS:Bnn attributes Supervising monitor Attribute Description Functionality NN Node Name Name of the computer ND Node Number SYS 600 Node Number SA Station Address SYS 600 Station Address Map the related process objects to the object s Foreground Color property. Value 0 with green color indicates the OK status. Value 1 with red color indicates the alarming status. Use the predefined process objects to supervise the Monitor Pro sessions. A process a object value is incremented each time the user logs in to Monitor Pro in remote system. The process object value is decremented when the user logs off. There is one process object per client computer that connects to the server by using Terminal Server or Citrix Metaframe. The process object is automatically created when the user logs in the first time from a remote computer. The process object s logical name is SAGR_L_CNT and the indexes are 10...N. The OI attribute of the process object consists of the system node name (OI field 1) and the client node name (OI field 2). The OV attribute value of the process object represents the count of the Monitor Pro instances in the client computer. The value 0 indicates, that there are no Monitor Pro instances running on the client computer. When using the MONn:Bnn attributes as a source for monitor supervision, see Table , a translation type, a display type and a language can be shown beside the monitor symbol, see Fig Fig Monitor supervision symbol A Table MONn:Bnn attributes Attribute Description Functionality TT Translation Type Translation type of the monitor DT Display Type Display type of the monitor LA Language Language of the operator 328

329 1MRS MicroSCADA Pro SYS When the monitor mapping of the application (APLn:BMONnn) is used as a source for monitor supervision, the semantics defined in Table are found in the attribute value Supervising application Supervising communication The used communication defines the application objects of communication supervision. Possible communication types are the following: PC-NET IEC OPC Server PC-NET The PC-NET status is supervised during a cyclical period. The application object for the PC-NET supervision is updated through a time channel. The semantics are defined in Table Supervising communication line The connection type between the communication line and the base system defines the application objects to a communication line supervision. Possible connection types are the following: PC-NET IEC OPC Server PC-NET Table Monitor Mapping of an Application Value Functionality -1 Monitor not in use > 0 and <151 Monitor in use Table Process object semantics Value Purpose 0 PC-NET communication error 1 PC-NET communication OK PC-NET provides status information about the communication line supervision regardless of the protocol type. To enable this function, configure the Enabled (SE) attribute of the PC-NET node system messages: #SET NET3:SSE=4 (analog and binary status points updated) 329

330 SYS MicroSCADA Pro 1MRS The corresponding binary status object has an address: Message Identification (MI) (MI hex). The received value in the binary process object indicates whether the communication line is OK (value 1) or not OK (value 0). To create system message process objects, refer to the Application Objects IEC OPC Server If the communication line is connected to IEC OPC Server, map the process objects to the OPC Item of the Object status per a IEC Subnetwork. When using the process objects as a source for communication line supervision, the semantics defined in Table are found in the attribute value Supervising station The connection type between station and SYS 600 defines the application objects to station supervision. Possible connection types are the following: PC-NET IEC OPC Server PC-NET Table Process object semantics Value Functionality 89 Initialize error 90 Not connected 91 Initializing 100 Ready 101 Suspended (=not in use) 102 Simulated If stations are connected through PC-NET, it is possible to use the related STAn:Bnn attributes together with the process objects. The PC-NET system messages update the process objects. When using the STAn:Bnn attributes as a source for a station supervision, a comment text and the station types can be shown beside the station symbol, see Table Table STAn:Bnn attributes Attribute Description Functionality CX Comment Text Comment Text of the station ST Station Type Type of the station To create system message process objects, refer to the Application Objects manual. PC-NET provides status information about the station supervision regardless of the protocol type. To enable this function, configure the Enabled (SE) attribute of the PC-NET node system messages. 330

331 1MRS MicroSCADA Pro SYS The corresponding binary status object has an address: Message Identification (MI) (MI hex). The received value in the binary process object indicate whether the station is OK (value 1) or not OK (value 0). Mapping data variables The process objects can be mapped to the data variables in the following ways: Use the SYS_S0001:P10 binary input process objects. The process objects are updated from the analog input process objects with index 110. The analog input process objects receive the actual system messages from PC-NET. The System Self Supervision application objects provide this logic. Create binary input process objects, which receive the extended status reporting messages from PC-NET. It is recommended to use the index 210. Map the related process objects, for example SYS_S0001:P10 or SYS_S0002:P210, to the object s Foreground Color property. Value 0 with green color indicates the OK status. Value 1 with red color indicates the alarming status. Table Process object related to PC-NET (Binary Input) Name SYS_S0001:P10 SYS_S0002:P210 Functionality Contains the communication status of PC-NET Contains the extended communication status of PC-NET When using the process objects mentioned above as a source for station supervision, the semantics defined in Table are found in the attribute value IEC OPC Server Table Semantics of PC-NET process objects Value Purpose 0 Station communication error 1 Station communication OK When using Threshold Editor, define the dynamics for both states: OK and not OK. If stations are connected through IEC OPC Server, the station supervision is based on mapping the Device Connection Status OPC item that locates on the IEC OPC server. Process objects related to IEDs are shown in Table Table Process objects related to IEDs in IEC OPC Server (Binary Input) Name SYS_S0001:P10 SYS_S0002:P10 OPC Item Example IEC61850 Subnetwork\AA1CP2\Attributes\ Device connection status IEC61850 Subnetwork\AA2CP2\Attributes\ Device connection status When using the process objects mentioned above as a source for station supervision, the semantics defined in Table is found from the attribute value. 331

332 SYS MicroSCADA Pro 1MRS Table Semantics of process objects Value Functionality 0 Communication error 1 Communication is OK NOT_SAMPLED_STATUS Communication is not known. If the related In Use OPC Item has the In Use state, it indicates a communication error. The related In se OPC Item can be for example IEC61850 Subnetwork\AA1CP2\Attributes\In Use. If the related OPC Item has the Not In Use state, it indicates a configuration error Supervising LON Clock Master When STAn:Bnn attributes are used as a source for the station supervision, the following semantics can be used to provide additional information beside the station symbol itself. When using the STAn:Bnn attributes as a source for the station supervision, a comment text and the station type can be shown beside the station symbol, see Table Table The STAn:Bnn attributes Attribute Description Functionality CX Comment Text Comment Text of the station ST Station Type Type of the station 332

333 1MRS MicroSCADA Pro SYS User management This section describes the elements and functions of the user management. You can change the user rights if your authorization level is System manager (5). With the User Management tool you can define users and access rights with authorization levels. In the LIB 500 applications, the standard functions in the Process Displays can be freely grouped into authorization groups. This means that you can have different authorization levels for different apparatus. Users can also be defined to have different authorization levels for different tools, substations, and so on. The authorization levels used: View (0) = The operator is allowed to view the functions, but not to make control operations. Control (1) = The operator is allowed to make control operations, for example to control switching devices with limited rights. Engineering (2) = All rights are grandted, excluding user management, which can be performed only by the system manager. System manager (5) = The user with this authority level is the system manager. All rights are grandted, including the rights to add and remove users and authorization groups. The user who first logs into an application is the system manager. Thus, each application has only one system manager. The user levels of the selected user are displayed in the main display. The levels can be directly modified. Note that the GENERAL level of the system manager cannot be changed. Valid values are 0 (View), 1 (Control) and 2 (Engineering). The modifications cannot be taken into use until they are saved in the User Management picture Defining user interface You can select the language from a list of supported languages. The default language is English. For more information, refer to Chapter 4. Defining application options. The authorization levels of the selected users are displayed. The levels can be directly modified by the system manager. The GENERAL level for the system manager cannot be changed. You can change the levels by selecting the authorization group(s) from the list and selecting a new authorization level from the list box below the list. The authorization level is shown under the authorization level column. The User list shows the users and you can define their user language from the list box of supported languages. Various tools and functions can be accessed from the toolbar and menus, and also with keyboard shortcuts. Fig shows the user management interface and its elements. 333

334 SYS MicroSCADA Pro 1MRS Fig User Management User_manage The User Management window contains the following menus to operate: The File menu contains the main functions for saving, printing and exiting. The Print command prints the following informations: User User's language Authorization group list Authorization level list The Edit menu enables and disables the viewing of the toolbar buttons. The Tools menu contains the tools for user management. The Help menu contains general information on user management help. The toolbar contains shortcuts for fast access to the frequently used functions Adding user The system manager can add users from the Add User dialog. To add a new user: 1. Select Tools > Add User. 2. Type a user name. The name must not contain special characters and it must not consist of two characters followed by a number. Also, the name cannot begin with a number. 3. You can copy the authority level from another user (not from the system manager) by selecting the source. 4. Click Apply to save the user information. Clicking Done closes the dialog without saving. 334

335 1MRS MicroSCADA Pro SYS The password for the new user is enter before the user changes it. You can see the run time help by clicking Help. Fig Adding user AddUser The modifications do not become active until you save the User Management dialog Removing user If you have system manager rights, you can remove users. To remove a user: 1. Select Tools > Remove User. 2. Select the user that you want to delete from the Remove selected user box. 3. Click Remove. The system manager cannot be removed. Clicking Done closes the dialog. You can see the run time help by clicking Help. Fig Removing user Rem_User 335

336 SYS MicroSCADA Pro 1MRS The modifications do not become active until you save the User Management dialog Adding group To add a new group: 1. Select Tools > Add Group. 2. Type a group name. The name must not contain special characters and it must not consist of two characters followed by a number. Also, the name cannot begin with a number. 3. You can copy the authority level from another group (not from the GENERAL group) by selecting the source. If the user levels are not copied from another group, then all the users get view rights (0) as default. 4. Click Apply to save the user information. Clicking Done closes the dialog without saving. You can see the run time help by clicking Help. Fig Adding group Add_Gro The modifications do not become active until they are saved in the User Management picture Removing group Only the system manager can remove authorization groups. To remove group: 1. Select Tools > Remove Group. 2. Select the group that you want to delete from the Remove selected group box. 3. Click Remove. The group GENERAL cannot be removed. 336

337 1MRS MicroSCADA Pro SYS All the tools and standard picture functions configured to the group will automatically start using the definitions of the GENERAL group. Clicking Done closes the dialog. You can see the run time help by clicking Help. Fig Removing group Rem_Gro The modifications do not become active until you save the User Management dialog Changing password All users can change their own password. To change the password: 1. Type the old password. 2. Type the new password and confirm it. 3. Click OK. The new password is taken into use right away. Fig Changing password Cha_Pass The new password has to be given twice to be confirmed. The modifications do not become active until you save the User Management dialog. 337

338 338

339 1MRS MicroSCADA Pro SYS Authorization User names are associated with a certain user profile that restricts the user s access rights, for example to access Process Displays. The authorization levels are defined in Table Table Authorization levels Authorization level Description 0 - View The operator is allowed to view the functions, but not to make control operations. 1 - Control The operator is allowed to make control operations, for example to control switching devices with limited rights. 2 - Engineering All rights are granted, excluding user management, which can be performed only by the system manager. 5 - System Management The user with this authority level is the system manager. All rights are granted, including the rights to add and remove users and authorization groups. The user who first logs into an application is the system manager. Thus, each application has only one system manager. The system administrator can restrict a user s access rights either by defining an authorization level for each object in a Process Display or by defining shortcuts for Process Displays. It is possible to define the authorization level for each object in a Process Display. The authorization level for the object is defined in Display Builder. Right-click the object and select Tool Launcher. In the Tool Launcher dialog, select the Required check box and define the authorization level. The user s access rights can be restricted also by defining the shortcuts for the Process Displays. The system manager can define that the user can access Process Displays only through the shortcuts and prevent the use of the menu commands. For example, the user cannot open a Process Display by selecting Main > Open. The shortcuts are displayed on the toolbar of each Process Display. For more information about defining the shortcuts, refer to Section Defining shortcuts to Process Displays. The user is automatically logged off, if Monitor Pro is not used when a certain time has elapsed since the last login. If you have the access rights for the appropriate authorization level, you can configure the authorization group and the level which is needed for using certain menu commands and toolbar buttons. The menu commands and toolbar buttons are disabled, if you are not authorized to use them. The configurable authorization level definitions override the default authorization group in Monitor Pro. If some menu commands are disabled due to the authorization group, default values in the user management. It is possible to override the default values with the configurable authorization level definitions. 339

340 SYS MicroSCADA Pro 1MRS The authorization levels can be managed in the customization mode in Monitor Pro. For example, right-click the menu or the toolbar button and select Authorize. For more information about the customization mode, refer to Section Customization dialog. If a standard function does not have an authorization group defined or the group is not included in the authorization definitions, a General authorization level from a predefined group is used. The authorization group GENERAL cannot be removed. System Tools are managed from the Tools authorization group. To dedicate the system tools to certain users, define the Tools authorization group. Only the system manager can add and remove users and grant access rights to the users. The password is selected and can be changed by the user exclusively. Password is changed in the Change Password dialog Default authorization levels The default authorization levels for menu commands and toolbar buttons are shown in Table Table Default authorization levels Action Authorization group Authorization level Tool Manager TOOLS (GENERAL) 2 - Engineering Display Builder TOOLS (GENERAL) 2 - Engineering MicroSCADA Control Panel GENERAL 2 - Engineering Alarm acking from the alarm row, ALARM_HANDLING (GENERAL) 1 - Control shortcut menu in the alarm control, menu command, toolbar button Clear Current Trend Log TREND_HANDLING (GENERAL) 2 - Engineering Adding comments to events EVENT_HANDLING 1 - Control Authorization Groups It is not possible to define the authorization level for the menu. Therefore, set the authorization level for the menu commands and submenus individually by rightclicking the command in the customization mode, see Fig and Fig The authorization groups and levels can be managed through User Management. For more information about using User Management, refer to SYS 600 Operation Manual. 340

341 1MRS MicroSCADA Pro SYS Fig Setting the authorization level for the menu command A Fig Setting the authorization level for the submenu command A