CAP581. Configuration Tool for COM581. p Operating Instructions. 1MRB Uen Edition July 2005

Transcription

1 CAP581 1MRB Uen Edition July 2005 Configuration Tool for COM581 p Operating Instructions

2 2000 ABB Switzerland Ltd Baden/Switzerland 4 th Edition Applies for software version V6.0 We reserve all rights with respect to this document and the software it describes. Unauthorized use, in particular reproduction or making available to third parties, is prohibited. ABB Switzerland Ltd, is responsible for the correct operation of the function blocks provided, i.e. the function of the blocks conforms to the description. The creator of the control logic is responsible for the correct operation of the application program. This document has been carefully prepared and reviewed. Should in spite of this the reader find an error, he is requested to inform us at his earliest convenience. The data contained herein purport solely to describe the product and are not a warranty of performance or characteristic. It is with the best interest of our customers in mind that we constantly strive to improve our products and keep them abreast of advances in technology. This may, however, lead to discrepancies between a product or software and its "Technical Description" or "Instructions for Installation and Operation".

3 Version Introduction C 2. Safety instructions B 3. Compatibility B 4. Installation B 5. Operating instructions B 6. Creating a project C 7. Engineering a CAP581 project C 8. Attribute and protocol configurations C 9. Finalizing C 10. Example of a project B 11. Fault finding A 12. Appendices B

4

5 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd July Introduction 1.1. Application Overview of the COM581 engineering procedure Overview of the CAP581 engineering procedure CAP Excel signal list Project documentation Database downloaded to COM Warranty conditions

6 C1 B3 B8 T1 B1 B4 DEC 3000 AXP Station B5 A B9 T2 B2 B6 B7 C2 C7 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C 1. Introduction 1.1. Application The gateway COM581 is used to link a substation automation system to a control system at a higher level, bay control units to the substation automation system and protection and metering devices to bay control units. It is a component of the ABB station automation system. The unit s modular design enables it to be configured to fulfill the communication requirements of a particular application (physical interfaces, protocols etc.). A parallel processing architecture capable of multiple protocol processing was chosen. SYS500 Connection to remote control centers IEC , DNP3.0 or RP571 COM581 COM581 External clock Optical LON bus COM581 GPS C M Star-coupler COM581 Optical LON bus REL REC580 REL REC580 REL REC580 REL REC cc c cc c cc c cc c IEC ABB control and protection Third-party protection Fig. 1.1 Example of a typical station automation system 1-2

7 C E CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd 1.2. Overview of the COM581 engineering procedure The gateway COM581 is configured by creating a configuration database. The configuration data for the specific device and bay are determined using the configuration tool CAP581. The configuration tool comprises essentially an object database from which the specific project data are obtained. CAP581 DIS581 Excel Signallist Create database Import Signals 2 Configuration work Compile signal database Import DB with Hardware Configuration Download Basesoftware Download signal database SWT Tool 6 COM581 COM581 Fig. 1.2 CAP581 engineering procedure A new CAP581 database is created using a CAP581 template. An Excel macro permits signals to be simply transferred to the database from the Excel signal list. Other specific project settings can also be made by means of CAP581. These include, for example, serial interface settings and adjustment of the scale for the measured variables. CAP581 generates an Access database for downloading to COM581 via an optical serial interface (LMI) using the Diagnostic and Information System Tool (DIS581). In order to transfer the signal database, it is necessary to upload the basic COM581 software first using the software tool (SWT). The latter also enables basic data such as device ID and slot number to be read from the database, which has been generated, and use them for configuring SIMON. 1-3

8 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C 1.3. Overview of the CAP581 engineering procedure CAP581 is a tool for configuring the gateway COM581. Fig. 1.3 CAP581 data inputs and outputs CAP581 CAP581 is used to configure the hardware structure (number of CPU s, interfaces etc.) and also for selecting the various protocols (e.g. LON, IEC101, RP571 etc.). The corresponding procedure is described in Section 5. Although all the protocol and signal parameters can be configured using CAP581, it is more expedient to use the respective Excel signal list if a large number of signals have to be handled Excel signal list The figure below shows an extract from the signal list that has to be used for importing data. The sections of the list for the various protocols are colored differently. A row corresponds to a connection between at least two signals. The procedure for importing data is described in Section The signals in this list can be created manually or imported from IET using import functions. 1-4

9 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd There are two import functions to be used according to the interbay bus of the substation. For more details on import functions see Section Fig. 1.4 Extract from the signal list for importing data Project documentation An entire COM581 project can be documented from the data contained in the database. The data always correspond to the current status of the project and export functions are provided for transferring them to a number of different lists. The procedure for generating project documentation is described in Section Database downloaded to COM581 The data of consequence for COM581 are obtained from the project database created using CAP581. The resulting download database can be transferred to the memory of the respective gateway via its optical interface with the aid of the Diagnostic and Information System Tool (DIS581). The procedure is described in Section 9.1. If the IEC61850 application is used, there is an additional.ccf file produced by CAP581 tool. This file is later used together with download database by DIS Warranty conditions The warranty conditions are defined in the supply contract. The manufacturer accepts no responsibility for any damage resulting from improper use or treatment, or incorrect configuration of the gateway COM581. Any special agreements are only valid providing they are included in the contract. 1-5

10 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C 1-6

11 CAP581 1MRB Uen/Rev. B ABB Switzerland Ltd August Safety instructions 2.1. Safety instruction flags General rule General safety instructions

12 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. B 2. Safety instructions 2.1. Safety instruction flags Safety instructions in these operating instructions are marked as follows: DANGER: This symbol indicates immediate danger due to high electrical voltage, or a mechanical or other cause. Non-observance can lead to serious injury or even death. WARNING: This symbol draws attention to a dangerous situation. Non-observance can lead to serious injury to persons or damage to property. CAUTION ESD: This symbol indicates specific information for the avoidance of equipment damage due to electrostatic discharge. The constructional elements and modules may only be touched by persons who are earthed CAUTION LASER/LED: This symbol indicates the use of a laser of Class Ι Laser/LED in the product. You should therefore avoid any direct eye contact with the laser NOTICE: An important instruction that must be observed. IMPORTANT: It must be ensured that no possibly damaging situation can arise for the product or for its surroundings. 2-2

13 CAP581 1MRB Uen/Rev. B ABB Switzerland Ltd 2.2. General rule Only ABB personnel are authorized to change the configuration of the device(s). To avoid infringing the warranty conditions, the user should only make changes to the configuration after consultation with the ABB Company supplying the device. The gateway COM581 may only be operated while in perfect working order and in strict accordance with the operating instructions. There may be a risk of damage if it is improperly applied General safety instructions Safety at work regulations (company, regional and national) must be strictly observed. Take careful note of the details given in the data sheet for the gateway COM581. Strictly observe local and national safety regulations and the safety instructions in these operating instructions during installation and commissioning of the device or equipment. Heed all warning labels and signs on the device(s) and in these operating instructions and all instructions regarding its operation. Only ABB personnel are authorized to change the configuration of the device(s). To avoid infringing the warranty conditions, the user should only make changes to the configuration after consultation with the ABB Company supplying the device. Take the usual precautions to guard against electrostatic discharge. Read the operating instructions carefully. Store the operating instructions in a place where they are safe, but are at hand if needed. 2-3

14

15 CAP581 1MRB Uen/Rev. B ABB Switzerland Ltd July Compatibility 3.1. PC requirements for CAP

16 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. B 3. Compatibility 3.1. PC requirements for CAP581 Hardware requirements At least 64 MB RAM, 128 MB recommended IBM-type PC better than 586/166 MHz (Pentium II recommended) CD-ROM drive Mouse Approx. 80 MB available on the hard disc for tools At least 100 MB available on the hard disc for a database, e.g. for a COM581 with IEC101 and 3000 configured signals Software requirements Microsoft Windows NT 4.0 Service Pack 5 for Windows NT MS Excel, MS Access (Office 97) Microsoft Windows 2000 including Service Pack 2 is supported from Version 5.00 onwards MS Excel and MS Access (Office 2000) are supported from Version 5.00 onwards Object Store (database system) V. 5.1 Microsoft Windows XP 3-2

17 CAP581 1MRB Uen/Rev. B ABB Switzerland Ltd August Installation 4.1. Overview Installing Object Store De-installing Object Store Installing CAP Updating CAP De-installing CAP

18 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. B 4. Installation 4.1. Overview Unless Object Store 5.1 is already installed on the PC, it has to be installed before installing CAP581. Both software packages are on the COM581/CAP581 installation CD. The installation procedure is given in Section 4.2 Installing Object Store and Section 4.4 Installing CAP581. Upon inserting the installation CD, Acrobat Reader is automatically started and displays the installation menu with links and installation help. Communicate IT Substation COM581 The Communication Gateway for High and Medium-Voltage Substations Documentation & Software Vx.y Edition Xxx yz Deutsch English Bedienungsanleitung Datenblatt 1MRB Bde User s Guide Data Sheet 1MRB Bde COM581 (SWT) Vx.y CAP581 Vx.y DIS581 Vx.y RER581 Documentation & Software Exit 2002 ABB Switzerland Ltd All rights reserved Made in Switzerland ABB Fig. 4.1 Installation menu displayed by Acrobat Reader Preliminary checks prior to installation Check that the minimum system requirements given in Section 3 are fulfilled. NOTICE: Local administrator rights are necessary to install the program and use the configuration tool CAP

19 CAP581 1MRB Uen/Rev. B ABB Switzerland Ltd 4.2. Installing Object Store To install Object Store 5.1 without using the installation menu that would normally start automatically proceed as follows: Insert the COM581/CAP581 installation CD Open Windows Explorer Run the program Setup.exe in the directory CD drive :\Object Store V5.1. Installation procedure: User Information dialogue: Enter information in fields as necessary and click on Next Choose Destination Location dialogue: Either accept the proposed directory or select or enter (no spaces or full stops) a desired directory {e.g. C:\Programs\Ostore}) and click on Next Fig. 4.2 Object Store setup: Choose Destination Location 4-3

20 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. B Setup Type: Select Online Runtime Stand alone. Fig. 4.3 Object Store setup: Setup Type Information: Changes to Environment click on OK Click on Finish. NOTICE: Full stops. or spaces are not permitted in the installation path. Object Store Services The function Object Store Services starts automatically every time the PC is rebooted, but if necessary it can be started manually. The installation of CAP581 described below does not require the PC to be rebooted. Procedure for WinNT: Select Start / Settings / Control Panel / Services and then the desired service and activate the desired procedure. 4-4

21 CAP581 1MRB Uen/Rev. B ABB Switzerland Ltd Fig. 4.4 WinNT Services dialogue Procedure for Win2000: Select Start / Settings / Control Panel / Administrative Tools / Services and then the desired service and open the context menu with the right mouse button. Fig. 4.5 Win2000 Services dialogue Creating a suitable cache for Object Store It is possible to adjust the size of the Object Store cache to suit the hardware configuration of the PC on which the program is being installed. This permits optimization of Object Store performance (default cache size 8 MB). 4-5

22 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. B Procedure for WinNT: Select Start / Settings / Control Panel / System Properties and click on the Environment tab, enter the corresponding values in the System Variables field and click on OK. Fig. 4.6 Dialogue for adjusting the WinNT system variables 4-6

23 CAP581 1MRB Uen/Rev. B ABB Switzerland Ltd Procedure for Win2000: Select Start / Settings / Control Panel / System Properties and the Advanced tap and click on the Environment Variables button in the Environment Variables field and on New in the dialogue which opens. Enter the corresponding values and click on OK three times. Fig. 4.7 Dialogue for adjusting the Win2000 system variables Enter the variable name OS_CACHE_SIZE and the value (64 MB for 128 MB RAM) (see Fig. 4.5 and Fig. 4.6). NOTICE: As a general rule, a setting of half the available RAM is recommended for the Object Store cache. (System operation and the CAP581 tool can be slowed if the setting is too high.) 4.3. De-installing Object Store An Uninstall command is included under CAPEC in the Programs group in the Start menu. Once the de-installation has been successfully accomplished, delete the main directory OSTORE manually. 4-7

24 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. B 4.4. Installing CAP581 To install CAP581 without using the installation menu that would normally start automatically proceed as follows: Insert the COM581/CAP581 installation CD Open Windows Explorer Run the program CAP581_V5_xx.msi in CD-Drive :\CAP581 V5.xx Installation procedure: Welcome to the : => Next User Information: Fill in the details under Full Name und Organization => Next Destination Folder: Select a folder where the application will be installed (we recommend to use the suggestion). => Next Fig. 4.8 CAP581 set-up: Destination Folder 4-8

25 CAP581 1MRB Uen/Rev. B ABB Switzerland Ltd Ready to Install the Application: => Next Setup Complete: => Finish Fig. 4.9 CAP581 set-up: Set-up Complete NOTICE: Full stops. are not permitted in the installation path (system checks this) and it should be close to the root directory. 4-9

26 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. B 4.5. Updating CAP581 From CAP581 Version 5.00 onwards, it is permissible to have several versions of the tool installed at the same time. WARNING: Older versions should be de-installed before installing a new version De-installing CAP581 Windows de-installation Open the Control Panel and double click on Add/Remove Programs. Select CAP581 in the dialogue and click on the Add/Remove button. Fig CAP581 tool: De-installing CAP

27 CAP581 1MRB Uen/Rev. B ABB Switzerland Ltd August Operating instructions 5.1. Starting CAP General operating instructions Project menu Tree menu View menu Messages menu Tools menu Help menu Toolbar Status bar Keyboard commands Use of the mouse Single click with the left button Single click with the right button Double click with the left mouse button Double click with the right mouse button Drag with left mouse button depressed Moving with the right mouse button depressed Instructions for using context menu functions Move here Rearrange here Copy here Link here Insert new item Delete item Remove link Properties Instructions for using the various views Location structure Signal tree

28 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. B 5. Operating instructions 5.1. Starting CAP581 To start the configuration tool CAP581, simply double click on the CAP581_V5_x icon on the Windows desktop or select it from the Start menu, i.e. Start/Programs/ABB/COM581/CAP581_V5_x. Fig. 5.1 CAP581 icon on the desktop Fig. 5.2 Starting CAP581 via the Start menu Providing the CAP581 configuration tool has been properly installed on your PC, the following window appears after the program starts. Fig. 5.3 Main CAP581 window divided into three fields 5-2

29 CAP581 1MRB Uen/Rev. B ABB Switzerland Ltd 5.2. General operating instructions The operating structure and procedures are those typical of all Windows programs. The menus and menu items are selected either via the keyboard or using the mouse. Fig. 5.4 CAP581 main menu Project menu Fig. 5.5 CAP581 Project context menu New Creates a new project database. This function can also be selected by entering Ctrl+N. Fig. 5.6 New in the CAP581 Project menu Open Displays the Open project dialogue, which provides facility for opening an existing CAP581 database or one of the last four files that was opened. Fig. 5.7 Open in the CAP581 Project menu Fig. 5.8 List of the last four CAP581 databases opened 5-3

30 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. B Close Closes the CAP581 database that is open. Fig. 5.9 Close in the CAP581 Project menu NOTICE: The database remains blocked until the CAP581 tool is closed. Exit Closes the CAP581 application. Fig Exit in the CAP581 Project menu View menu Fig CAP581 View menu Toolbar Shows or hides the toolbar. Fig Toolbar in the CAP581 View menu Status bar Shows or hides the status bar. Fig Status Bar in the CAP581 View menu Tree menu Fig CAP581 Tree menu 5-4

31 CAP581 1MRB Uen/Rev. B ABB Switzerland Ltd Expand one level Displays the next level down in the branch. Fig Expand One Level in the CAP581 Tree menu Expand branch Displays all menu levels below the cursor. Fig Expand Branch in the CAP581 Tree menu Expand all Displays the entire menu structure. Fig Expand All in the CAP581 Tree menu Collapse branch Reduces the branch, i.e. closes all the levels, below the cursor. Fig Collapse Branch in the CAP581 Tree menu Enable context naming Enables or disables the detailed designation of all data points. Fig Enable Context Naming in the CAP581 Tree menu Messages menu Fig CAP581 Messages menu Import hardware messages Shows error messages and warnings that occurred while importing hardware. Fig Import Hardware Messages in the CAP581 Messages menu 5-5

32 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. B Builder Messages Shows all error messages and warnings that occurred while creating the download database. Messages from the database builder and the consistency check are listed separately. Fig Builder Messages in the CAP581 Messages menu Tools menu Fig CAP581 Tools menu Import Hardware Copies the hardware structure of an existing database to an empty or new CAP581 database. This saves time when creating new databases. Structures from previous versions can also be copied. Fig Import Hardware in the CAP581 Tools menu Report Configurator Opens the report configurator for creating special lists for documentation purposes. Fig Report Configurator in the CAP581 Tools menu Help menu Fig CAP581 Help menu 5-6

33 CAP581 1MRB Uen/Rev. B ABB Switzerland Ltd Books Online Displays the on-line manuals with selection of English or German. Fig Books Online and language sub-menu in the CAP581 Help menu About CAP581 Displays the version of the currently installed CAP581. Fig About CAP581 in the Help menu CAP581 Error Log File Logs errors that are not displayed in error messages. The last menu function used is also recorded. Fig CAP581 Error Log File in the Help menu Toolbar Fig CAP581 toolbar Status bar The functions New, Open and About CAP581 are also available on the toolbar and can be directly accessed from there. Fig CAP581 status bar 5-7

34 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. B Keyboard commands The keys for navigating in the menu structure are the standard Microsoft keys and are therefore not listed below. Other keyboard commands have no influence. The following keyboard commands are supported: Function Accept property sheet changes Reject changes and close the properties dialogue Toggle between the properties dialogue and CAP581 view Next property field or cycle through the CAP581 windows Keys ENTER ESC ALT+F6 TAB (Shift+TAB) Expand one level (Num) + Expand branch (Num) * Expand all Ctrl+(Num) * Collapse branch (Num) - Go to beginning of tree Go to end of tree Go up one level in tree Go down one level in tree Go down one level in branch Go up one level in branch Open project Create new project from a template Build all Stop build Close application Table 5.1 Keyboard commands supported by CAP581 Page Down Page Up Arrow key Arrow key Arrow key Arrow key Ctrl+o Ctrl+N ALT+C ESC ALT+F4 5-8

35 CAP581 1MRB Uen/Rev. B ABB Switzerland Ltd 5.3. Use of the mouse The many operations described below can be executed quicker and more simply using the mouse. Scrolling in windows is greatly simplified should your mouse be equipped with a wheel. NOTICE: The Undo function does not apply to mouse operations Single click with the left button Selects an item in the tree structure Single click with the right button On an item in the tree opens a context menu that lists the operations available for the particular item. Fig Opening a context menu for an item in the CAP581 tree structure Double click with the left mouse button Goes to the next level down below the cursor Double click with the right mouse button No special function, equivalent to a single click Drag with left mouse button depressed To move an item, select it and then hold the left mouse button depressed and drag the item to the new position. This is useful, for example, for changing the order of a structure (see Section Rearrange here ). If the <CTRL> button is pressed first, the selected item can be either linked or copied Moving with the right mouse button depressed To link, move, copy or otherwise sort items, select the item concerned and then hold the right mouse button depressed. Upon 5-9

36 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. B releasing the button, a context menu appears and you can select the desired operation Instructions for using context menu functions There are two different kinds of context menu. The first concerns the possibilities described in Section Moving with the right mouse button depressed and the second a single click with the right mouse button described in Section Single click with the right button. A context menu only lists those operations that are available in the particular situation. NOTICE: Undo is not available for operations selected from a context menu Move here This operation permits signals or complete branches to be moved to positions at any level of a structure. Fig Moving signal IEC101 to another IEC101 application. 5-10

37 CAP581 1MRB Uen/Rev. B ABB Switzerland Ltd Rearrange here Rearrange here permits signals or complete branches to be moved to another position on the same level of a structure. Fig The third item is moved to second position Copy here Copy here permits complete items together with their substructure to be copied to another position at the same level. Fig Copying a complete IEC101 application NOTICE: Any links between signals are broken. 5-11

38 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. B Link here Link here permits signals and particular items to be assigned or linked to another signal or item. Fig Linking signals in the signal tree Insert new item Upon selecting this function, a list of those items is displayed that can be inserted in the case of the current item (see Section Single click with the right button for context menu). Fig List of items that can be inserted for Insert new item 5-12

39 CAP581 1MRB Uen/Rev. B ABB Switzerland Ltd Delete item Clicking on this function deletes the item that is selected. Should it include a substructure, a dialogue appears in which you are required to confirm the deletion. Fig Dialogue displayed where a substructure exists NOTICE: Deleting part or all of the structure in the Signal Tree view, only the links to between signals are deleted. The signals shown in the Location Structure view are unaffected. NOTICE: To delete the entire structure including links and signals, delete the item Plant, External Device or External MVB Device in the Location Structure view. NOTICE: Deleting a signal in the Location Structure view also deletes the associated link. If a source item is deleted, the associated sink item in the Location Structure view is not Remove link Clicking on this function for a selected linked item deletes it. Should it have a substructure, a dialogue appears in which the deletion has to be confirmed (see Fig. 5.38). 5-13

40 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. B Properties Clicking on properties opens a dialogue with information relating to the item selected. Fig Example of a properties dialogue with tabs for different categories Mark the Value of an Attribute to edit it. Point to the attribute to view a list of the values available for it. The integrity of the data entered in the fields is checked and a message is displayed if a value is not in the permissible range. Fig Message displayed if an out-of-range value is entered NOTICE: Changes only take effect after pressing the <Return> key, closing a window or selecting a new item with the mouse. 5-14

41 CAP581 1MRB Uen/Rev. B ABB Switzerland Ltd 5.5. Instructions for using the various views To make working with the configuration tool CAP581 more efficient, there is a choice of different types of views. To change the type of view, point to the title bar of the window and click the right mouse button. A context menu opens from which the desired view can be selected. Fig Context menu effective for the various views Window View ACP tree DIA tree DNP30 tree IEC101 tree IEC103 tree IEC104 tree Itype2 tree LON tree Location structure MVB tree PSF tree RP571 tree Configuration for the ACP protocol Diagnostic messages as configured Configuration for the DNP3.0 protocol Configuration for the IEC101 protocol Configuration for the IEC103 protocol Configuration for the IEC104 protocol Configuration for the Itype2 protocol Configuration for the LON protocol Hardware configuration including all protocol data Configuration for the MVB protocol Specific project functions Configuration for the RP571 protocol 5-15

42 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. B Window View Signal tree Linked signals of all protocols TG809 tree Configuration for the TG809 protocol Time tree Time management settings Table 5.2 Various CAP581 views Context menu function Project container Description Creates a new or opens and existing project in the corresponding view. Facility is thus provided for opening a second (and third) project at the same time. Default Open New Opens the main project (displayed on the toolbar). Displays the Open dialogue for opening another project. Displays the New dialogue for creating a new project. Cancel Table 5.3 Closes the menu Sub-menus accessed via the context Fig Sub-menu referred to in Table Location structure The Location structure view permits the basic settings for the project to be made and all the settings to be viewed. 5-16

43 CAP581 1MRB Uen/Rev. B ABB Switzerland Ltd Fig Part of the Location structure view NOTICE: With the exception of the signal connections, the Location Structure view provides all the information relating to a project Signal tree Signal tree is used for viewing all the linked signals or for configuring new signal links. Fig Part of the Signal tree view NOTICE: This view is the starting point for creating the configuration database for the plant. 5-17

44

45 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd July Creating a project 6.1. Creating a new project Project tree files and naming conventions Basic configuration Hardware engineering Importing hardware Adding hardware manually Signal engineering Importing signals Adding signals manually Specific configurations Starting the database builder Additions and corrections Documenting and saving the project

46 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C 6. Creating a project Fig. 6.1 Procedure for creating a project The objective in this section is to understand the operating principle of the engineering tool and to be able to create the basic structure of a project and engineer a few signal connections. Those steps in the above diagram in bold print are explained briefly in the following sections. The detailed procedure for engineering signals and hardware is given in Section 7. Settings and alternative configurations are dealt with in Section

47 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd 6.1. Creating a new project To create a new project select New... in the Project menu. Fig. 6.2 Selecting New... to open the New Project Database dialogue This opens the dialogue below for entering the name of the new project and the path of the directory where it should be saved. Fig. 6.3 CAP581 New Project Database dialogue Clicking on the Create button saves and opens the new project with a basic configuration in the designated directory and its name appears on the title bar of the window. The root object gets the name of the project automatically. 6-3

48 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Fig. 6.4 New CAP581 project Project tree files and naming conventions When a new project is created, CAP581 tool creates a project directory tree in the specified directory and copies the template files into it. The project directory tree has a pre-defined structure and the all project files are stored on the predefined places. The names of the files in a project follow the naming conventions and should not be changed. The following picture shows an example of project directory after a build with the following files: 1. IAL mapping database used for SCD file processing (only IEC61850) 2. CAP581 tool database file 3. Project s Signal List 4. File containing the CAP581 tool version 5. Temporary file used for CCF file creation; (only IEC61850) 6. Builder Log file (Contains errors and warnings of last build) 7. CCF file for COM581 device (only IEC61850) to be loaded into COM581 device. 8. Database for COM581 device to be loaded into COM581 device. 9. Work file used for possible reports 10. Work file used for possible reports 11. Work file used for possible reports 6-4

49 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Fig. 6.5 CAP581: Files in a new created project directory NOTICE: Files 1-4 are created during a project creation. File 5 is created during an SCL import (only IEC61850) Files 6-11 are created during a build of the project. In IEC61850 projects the file 7 and 8 get name from imported SCD file according to the COM581 IED name Basic configuration A newly created project is saved with a predefined basic configuration, i.e. a COM581 with a diagnosis application on the IMP board. The next step in engineering a project is explained in Section 6.3 Hardware engineering below. Fig. 6.6 Basic CAP581 tree structure Although only a basic configuration, various attributes can be set for the items of plant that are included. These concern primarily the items COM581, VME, IMP and the DIA application. Further details on settings are given in Section

50 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C 6.3. Hardware engineering There are two ways of adding more hardware components (lines, buses, protocols etc.). Both methods can also be combined. Hardware is imported at the beginning (see Section Importing hardware ) and added manually (see Section Adding hardware manually ) at the end. This prevents any collisions during the importing procedure Importing hardware This function permits copying the structure of an existing COM581 that has already been configured for purposes of importing its project database as a basis for creating the new project. Fig. 6.7 Opening the Import Hardware function Fig. 6.8 Dialogue for selecting a database with a suitable structure The existing hardware structure of the desired source database is inserted in the new database. While this is taking place, an hourglass appears on the screen and a message is presented when the transfer has been completed. At this point, the attributes of the items that have been inserted are those of the source database. 6-6

51 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd NOTICE: The builder has to be started to import an existing hardware structure. NOTICE: If the source database had previously been opened during the CAP581 session, CAP581 has to be restarted before attempting the transfer Adding hardware manually Fig. 6.9 Adding a new item below the selected item Click the right mouse button on the item to open the context menu for selecting this function (see Section 5.3.). Which item is inserted at which location is explained in detail in Section

52 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C 6.4. Signal engineering Similarly there are two ways of adding signals that can then also be linked. Both can once again be combined. The detailed procedure is given in Section Importing signals Signal connections between different protocols are achieved using the signal list. The list is an Excel table, which includes a special macro for importing data. Establishing a connection between two signals requires filling in a line in the signal list, i.e. the field in the Technical Signal Description column and those of the desired two protocols (e.g. LON General Settings with LAG Data and IEC 101 Protocol Data). Fig Connection between LON and IEC103 To import signals into the project database, the corresponding lines in the signal list have to be selected and the import macro started. This macro (Open_CAP581Database_And_Import_ Signal List) is accessed by selecting Macro Macros in the Tools menu, or alternatively by clicking on the button on the CAP581 toolbar bearing the icon dialogue. to open a corresponding Fig CAP581 Toolbar The target database is selected from the list in the Open Project dialogue. The detailed procedure for using the Excel signal list is given in Section

53 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Adding signals manually Signals are added manually in the same structure and linked in Signal Tree as one signal. Signal flow is from the source to the sink. The detailed procedure for adding signals manually is given in Section NOTICE: In order to preserve data consistency between the project databank and the Excel signal list, it is recommended that signals be added manually only as an exception. 6-9

54 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C 6.5. Specific configurations This provides facility for configuring protocols according to a user s specific requirements. Before starting the database builder, check the following settings: Station bus protocol settings Remote control protocol settings Measured variable scales Configuration of the commands Counter configuration Response to diagnostic messages Use of specific project functions 6.6. Starting the database builder Once configuration of the project is complete, the COM581 download database can be generated using the builder. At the conclusion of the building procedure, a number of consistency checks are carried out and details of any errors displayed in an Info box. Fig Example of an Info box after the builder has finished 6-10

55 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd 6.7. Additions and corrections It is still possible to make additions to accommodate user requirements or other changes. However, any corrections that may be necessary as a consequence of error messages or warnings in the message file created by the database builder have to be implemented. Fig Opening the message file The detailed building procedure is described in Section Documenting and saving the project CAP581 can generate two types of list to document the project, firstly a signal list resulting from engineering the signals and secondly a report file, which can be specifically, compiled using the report configurator. The signal export and report configuration procedures are described in detail in Section 9.2. Fig Generating the signal list NOTICE: The builder has to be started to update the documentation to take account of any changes made to CAP

56

57 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd July Engineering a CAP581 project 7.1. Hardware engineering Hardware checklist Importing hardware Error messages Adding hardware manually General hardware structure Signal engineering Signal List Signal list template Select protocols macro Creating signals Creating signals from an SCL file Using the Import IET (IEC61850) function Import signals from IET (LON) Signal choice in the CCT tool Importing signals from CCT tool Product Perspective Product Functions Supported devices Address calculation macros Address calculation for IEC Address calculation for DNP Address calculation for RP Address calculation for TG Re-import of signals (merge) Description of signal attributes Compiling and structuring a signal list Example of exporting signals Starting the signal export function Re-exporting a signal list Errors while exporting signals Work in CAP581 Tool Connecting SPI signals (single point indication) Connecting command signals Adding and connecting signals manually Eliminating a signal connection Automatic transfer of attributes

58 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C 7. Engineering a CAP581 project 7.1. Hardware engineering Hardware checklist A number of things have to be known before it is possible to determine the COM581 settings with the aid of the configuration tool CAP581. This information has to be acquired in advanced to be able to determine the complete structure of the CAP581 unit. The table below lists the data that are needed. Number of protocols Number of signals Station bus protocol Remote control protocol IMP slot Number of ISG s and slot Number of ISP s and slot Radio clock Time master Redundant time master Time slave Number of devices connected to bus How many protocols must COM581 handle? Is the total number of signals within the permissible limit (see COM581 Data Sheet) Which protocols will be used to connect the bay units and protection devices? MVB, LON, IEC103 etc. Which protocols will be used to communicate with the Network Control Centre? IEC101, RP570, RP571 etc. Which slot will be used for the IMP in the COM581 rack (see COM581 Data Sheet)? Which slot will be used for the ISG in the COM581 rack (see COM581 Data Sheet)? Which slot will be used for the ISP s in the COM581 rack (see COM581 Data Sheet)? Where is the radio clock located? RER111, µ-scada or COM581 Which board in COM581 is the time master? Which board in COM581 is the redundant time master? Which board in COM581 is the time slave? How many bay units and protection devices are connected to the station bus? Interface parameters to be set Table 7.1 Hardware checklist Which parameters have to be set to communicate with the NCC? Data transfer rate, parity, stop bits, number of data bits etc. (see interoperability list for the respective protocols). 7-2

59 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd NOTICE: Certain data can still be entered after importing a signal list Importing hardware The hardware structure of an existing project that has already been configured and used in practice can be used again. The function Import Hardware permits the existing structure to be imported into the new projected complete with all its settings. NOTICE: Data can only be transferred from an existing project if its database builder is started beforehand. The first step is to create the new project using CAP581. For this purpose, select Import Hardware in the Tools menu (Fig. 6.6) to open the dialogue for selecting the CAP581 database of the existing project with the hardware settings to be copied. Fig. 7.1 Import: Dialogue for selecting the project from which the hardware should be copied NOTICE: Should the error message Error Full Import, appear, delete COM581 from your template database and repeat the import procedure. 7-3

60 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Error messages At present the program only generates error messages of a general nature Adding hardware manually Provision is also made for adding hardware manually. The various operations with the mouse described in Section 5 are used for this purpose. After creating a new project, the next thing is to add the CPU boards. Fig. 7.2 VMF directory where CPU boards are added NOTICE: A COM581 can have a maximum of six CPU boards (IMP, ISP and ISG), i.e. one IMP (always fitted), n ISP s, and m ISG s. Thus with a maximum complement 1 + n + m = 6. The desired protocols are then added for the respective CPU boards, while observing the following restrictions: Protocol DIA PSF LON DNP30 RP571 / RP570 Restrictions Only permitted for the IMP board and has to be configured; applications per board limited to one. Permitted for ISG and/or ISP boards; applications per board limited to one. Only permitted for IMP and ISP boards and is optically connected (LON devices); number of LON devices limited to three (1 on IMP and 2 on ISP boards per COM581); applications per board limited to one and only DIA (IMP) or PSF (ISP) additionally allowed on the same board. Only permitted for ISG board via a serial connection (NCC), only use Port 3 or 4; applications per ISG board limited to one and only PSF additionally allowed on the same board. Only permitted for ISG board via a serial connection (NCC), only use Port 3 or 4; applications per ISG board limited to one and only PSF additionally allowed on the same board. 7-4

61 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Protocol TG809 IEC101 ACP IType2 IEC103 Restrictions Only permitted for ISG board via a serial connection (NCC), only use Port 3 or 4; applications per ISG board limited to one and only PSF additionally allowed on the same board. Only permitted for ISG board via a serial connection (NCC), only use Port 3 or 4; applications per ISG board limited to one and only PSF additionally allowed on the same board. Only permitted for ISG board via an Ethernet connection (NCC), only use Port 3 or 4; applications per ISG board limited to one and only PSF additionally allowed on the same board. Only permitted for ISG board via an Ethernet connection (NCC), only use Port 3 or 4; applications per ISG board limited to one and only PSF additionally allowed on the same board. Only permitted for ISG board via a serial connection (IEC103 devices), only use Ports 1 to 8 (electrical) and 11 and 12 (optical); number of ISP boards with IEC103 per COM581 limited to three; four applications per ISP board and only PSF additionally allowed on the same board. IEC104 Table 7.2 Only permitted for ISG board via an Ethernet connection (NCC); applications per ISG board limited to one and only PSF additionally allowed on the same board. Hardware restrictions Other protocol configurations are described in Section

62 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C General hardware structure The figure below shows the CAP581 tree structure after importing the lines of the example. The hardware ID s (CPU s, lines, protocols etc.) must be assigned before importing the signals. Fig. 7.3 Location Structure: External Devices and COM581 together with the protocols 7-6

63 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd 7.2. Signal engineering Signal List Engineering a station project consists primarily in compiling the lists of signals. The larger the project the more signals there are and hundreds and often thousands of signals have to be defined. The data of the bay units and protection devices are entered in the signal lists created using Microsoft Excel. These data can be automatically exported into CAP581 by running a VBA macro. NOTICE: At least one line with at least one master and a slave/master has to be filled in per signal connection Signal list template The template for the signal list (SignalList.xls) is copied to CAP581 install directory" \Microsoft Office\Office\XLStart" when installing the configuration tool CAP581.. This file is copied into the project directory when the project is created. The file is renamed to SignalList_ProjectName.xls where ProjectName is the actual project name. The file is stored under:..\projectname\signallist_projectname.xls NOTICE: The name of the Signal List file and its location should not be changed because some functions use it to find the project name and other project files. The macros must be enabled if a signal list is opened for processing or is being newly created. The following dialogue appears: 7-7

64 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Fig. 7.4 Dialogue displayed upon opening an Excel signal list Select protocols macro The Signal List is very wide, which makes it difficult to navigate in. To make it easer it is recommended to use the Select Protocols macro to select only the protocols actually used in the project. Use Tools menu to access the Select Protocols macro and select protocols you want to use. The macro will hide all columns of unused protocols and adjust accordingly the navigation buttons. Fig. 7.5 Select Protocols window Fig. 7.6 Navigation buttons in the Signal List toolbar The navigation buttons allows the fast jump into the specific protocol section 7-8

65 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Creating signals A signal list is basically an Excel table. The signals are defined by the attributes entered in the columns. Attributes are grouped in several sections and color coded according to protocol. A signal is defined generally by the data entered on its line in the table and in at least two protocol sections. The data of the bay units and protection devices form the basis of a signal list. Signal lists are created using the signal export function in the Tools menu. Data from older versions of a list can also be copied, but only by inserting the values (Paste Special ; Values). The versions are not necessarily the same and the number of columns may vary. The locations of the values in the columns must therefore be checked after copying. The Signal List can also be filled-up using import from IET functions. There are two import functions: One is to be used for the installations using IEC61850 definitions (SCL file as source of data) and the other is to import data for LON based installations (uses directly IET database query). The version of a signal list is given on line B1 and its characteristics in the comment. Errors can occur when exporting data from a signal list created using another version of CAP581. It is therefore important to use the template belonging to the current version of CAP581 when engineering a project. Nevertheless, exporting signal list data makes efficient use of existing CAP581 solutions and reduces project engineering and testing costs considerably. The signal lists created can be used to document the project and also for subsequent projects Creating signals from an SCL file This function process the SCL file and creates the signals list. At the same time it creates a temporary file containing all of the necessary data (input section) to be later transformed into device configuration file (CCF file). The IAL mapping database is used to define the mapping of IEC61850 data objects into Signal List structure. The copy of this database file is stored in the project directory during project creation (see CAP581 new project creation). 7-9

66 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C NOTICE: The SCL file has to contain the definitions of all necessary Data Set and Report Control Blocks to be used by COM581 gateway. The Signal List is created based on this data Using the Import IET (IEC61850) function Select the button Import IET (IEC61850) in a Signal List toolbar Fig. 7.7 Signal List toolbar Select the SCL file Here the project SCL file has to be selected. All COM581 IEDs will be found and presented for selection in the COM581 and Access Point selection window. Fig. 7.8 Select the SCL file dialog 7-10

67 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Fig. 7.9 Choose the COM581 device and Access Point dialog A dialog window is shown presenting all COM581 devices defined in the SCL file. Choose the right one. The device has to be correctly defined having at least on Access Point connected to the MMS-8 bus. If the chosen COM581 device has more than one IEC61850 Access Point, it will be displayed again and the right Access Point has to be selected. Additionally it is possible to specify that one Signal List sheet per bay has to be created. Once the choices are done the processing starts and the progress window shows the actual steps. During the processing, the SCD file is scanned for all IEDs on the bus connected to the chosen Access Point. The RCBs are checked if the given COM581 IED is specified as client. If it is the case the RCBs referenced Data Set is scanned and all Data Points referenced in them are mapped to into the Access Point Input Section and corresponding signals are created in the Signal List. To map a Data Point the function uses the IAL mapping database. Each project has its own copy of this database stored in the project tree under:..\projectname\databases\ialmapping_ ProjectName.mdb At the same time the processing produces a temporary SCD file where the COM581 IED is extended with generated Input Section. This file is later used to create the final COM581 IED configuration file (CCF file). This file is stored in the project tree under:..\projectnama\temp.tmp 7-11

68 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C NOTICE: This file is needed during the CAP581 tool build process and should not be deleted. It is always re-created during an SCL import but in can be used for several consecutive builds. Fig Progress window At the end of the processing a Log window is presented. In his window it is possible to see (selectively) all errors, warnings and information messages generated during the processing. It is also possible to save the log as a file. This log can be useful for troubleshooting. 7-12

69 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Import signals from IET (LON) Signal choice in the CCT tool In the CCT tool the terminals/signals are selected to be transmitted to the NCC in 2 steps. On LN level all of candidates to be used by NCC are flagged (this definition is inherited from LN templates) In the second step the user has a possibility to choose from the candidates the signals he wants to be effectively used by the specific gateway he is defining. Fig NCC candidates on LN level 7-13

70 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Fig Final NCC signal choice in CCT Importing signals from CCT tool To import signals from the CCT tool the Signal List provides a function giving the possibility to select the CCT tool database and the NCC to be import signals from. Fig IET Import (LON) macro button 7-14

71 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Fig Import from CCT window After the button (1) has been activated the user has to select the CCT tool database. The window (2) will present the list of NCCs defined in the CCT. The user selects one Fig Selection of CCT tool database 7-15

72 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Fig Selection of NCC The window (2) will presents the list of NCCs defined in the CCT. The user selects one of them. If the button Split Signallist per bay (3) is activated multiple sheets Signal List will be created with on sheet per bay. Once the choices are done, activate the Import Signals button and the list will be created. If there are more NCCs to be imported they can be selected one by one and imported. The button Exit (6) terminates the function. Fig The status window reports the number of signals created 7-16

73 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Product Perspective This solution relies totally on the functionality of CCT to define the signals. Actually only LON protocol is supported. The SCL files are not used at all for in this case. Due to the limitations of Excel Signal List it did not implement any transmission of additional parameters from IET to CAP581, which forces the engineering of COM581 to be distributed between different tools with all inconsistencies which this can introduce. This has to be seen as a provisory solution. The solution consists of a macro defined in the CAP581 Excel Signal List. This macro retrieve all signals configured for the given COM581 (NCC) in the IET database and store them in the Signal List. In the case when the signal list contains already signals from the previous sessions they will be merged. The macro uses the query defined in the IET database. This query fetches all of the data to be filled into the Signal List. Additionally to facilitate the merge with the previous versions of the list the terminal/signal GUID has to be retrieved and stored in a hidden column in the list. Fig Excel Signals List - Data to be imported from the CCT The data imported from the IET shall not be modified in the signal list. During the signal list generation the IET terminal type is converted to the CAP581 signal type. In this subsection put the product into perspective with other related products or projects. If the product is independent and totally self-contained, it should be stated here. 7-17

74 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C If the TRS defines a product that is a component of a larger system then this subsection should Describe the functions of each component of the larger system, or project relevant for the product, and identify interfaces Identify the principal external interfaces of this software product Describe the computer hardware and peripheral equipment to be used Product Functions This functionality requires the following components: MS Access query to retrieve the signal list data from the IET database Following parameters have to be retrieved from CTT database: - GUID from T_MicroScadaAspect.GUID (to be stored in a hidden column in the Signal List) - Station Name from T_MicroScadaAspect.StationName - Bay Name from T_MicroScadaAspect.BayName - Device Name from T_Device.Name - Signal Name from T_Terminal.Name - Signal Type from T_MicroScadaAspect.ProcessObjectType (to be converted into CAP581 signal type) - ABB Signal text from T_MicroScadaAspect.ObjectText1 - Cust. Signal text from T_MicroScadaAspect.ObjectText2 - LON parameters NOTICE: During the creation of the Signal List the function manipulates some signal parameters received from the IET to fulfill the CAP tool requirements. 7-18

75 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Supported devices LON IEC101 IEC103 IEC104 IEC61850 ACP DNP3.0 RP57x TG809 (PSF) (DIA) Address calculation macros Once the signals created the addresses of the NCC protocols have to be defined. The user can use address calculation macros for this purpose. Five macros are available for IEC101, IEC104, DNP3, RP570 and TG809. They can be accessed trough the Tools menu of the Signal List. To delete the address info corresponding Delete macros are provided. Fig Tools menu in the Signal List 7-19

76 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Address calculation for IEC101 Fig Calculate IEC101 address range window 7-20

77 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Address calculation for DNP3 Fig Calculate DNP3 address range window 7-21

78 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Address calculation for RP570 Fig Calculate RP570 address range window 7-22

79 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Address calculation for TG809 Fig Calculate TG809 address range window Re-import of signals (merge) Very often arise the necessity of re-importing of signals when the source data has changed. The both import functions allow the repetition of import for no empty signal list. When the import function is reapplied on such on a list all of the signals which have been already in the old source and have been not modified are untouched. All of signals where some of the imported columns have been modified are marked with flag M in the import/export column. According to the import function all of the columns, which are imported by are overwritten from the source 7-23

80 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C data. The both functions do not provide the same columns to the Signal List. All of the signals, which are new in the source are marked with N. Finally the signals which do not exist anymore in the source are marked with D. These signals have to be removed manually from CAP tool database if they were already exported into. NOTICE: To recognize the signals both functions use the key columns on basis of which the signal is recognized as such. The SCL import uses the IEC61850 Signal Identification column for this and IET (LON) import uses an additional column (FN) where it stores the IETs GUID of the signal. These columns should not be modified otherwise the import function will consider a signal as deleted and at the same time it will create the new one. Fig Merge result example Description of signal attributes Category/Section Attribute Remarks Signal Import Import / ExportFlag N new signal created during the import M signal modified during the import (modified columns marked) D signal deleted during the import (not anymore in the source). Such a signal must be manually deleted from CAP tool if already exported into. X signal successfully exported Technical Signal Description Export Message Station Name Bay Name Device Name Error message when a line could not be successfully exported. Text; full stop. not permitted Text; enter value, full stop. not permitted Text; value recommended, full stop. not permitted 7-24

81 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Category/Section Attribute Remarks Signal Name Signal Type Text; enter (definite) value (excepting for PSF function block); full stop. not permitted Text; enter (pull-down) value (excepting for PSF function block) Signal Text Supplier Signal Text Text; supplementary information not exported when building database Customer Signal Text Text; supplementary information not exported when building database LON General Settings LON Application ID Needed for protocol LON Unit Address Or SPA Unit Address Needed for protocol LAG Data Object Address Only needed for LON NV Data NV Selector Only needed for NV LON-LON SPA-Gateway Communication MVB Message Data MVB Process Data SPA Channel SPA Reg Type SPA Reg1 SPA Reg2 SPA Event 00 SPA Event 01 SPA Event 10 SPA Event 11 MVB Bus Line MVB Node Address MVB Station Address MVB REB Node Address MVB Original Signal Location MVB Dataset No MVB Bit Offset MVB Individual Period MVB Dataset Size Only needed for SPA Pull-down MVB MVB Application ID Needed for protocol IEC 101 Protocol Data IEC101 Application ID NCC1 Needed for first protocol IEC101 Application ID NCC2 IEC101 Application ID NCC3 IEC101 Application ID NCC4 Needed for second protocol Needed for third protocol Needed for fourth protocol IEC101 Common Address ASDU NCC1 IEC101 Information Object Address NCC1 IEC101 Common Address ASDU NCC2 IEC101 Information Object Address NCC2 IEC 101 Common Address ASDU NCC3 7-25

82 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Category/Section Attribute Remarks IEC 101 Information Object Address NCC3 IEC 101 Common Address ASDU NCC4 IEC 101 Information Object Address NCC4 IEC 103 Protocol Data IEC103 Application ID Needed for protocol IEC 103 Link Address IEC 103 CAA IEC 103 FUN IEC 103 INF RP57X Protocol Data RP57X Application ID NCC1 Needed for first protocol RP57X Application ID NCC2 RP57X Application ID NCC3 RP57X Application ID NCC4 Needed for second protocol Needed for third protocol Needed for fourth protocol Process RTU No NCC1 Block No NCC1 Bit No NCC1 Process RTU No NCC2 Block No NCC2 Bit No NCC2 Process RTU No NCC3 Block No NCC3 Bit No NCC3 Process RTU No NCC4 Block No NCC4 Bit No NCC4 ACP Protocol Data ACP Application ID NCC1 Needed for first protocol ACP Application ID NCC2 ACP Application ID NCC3 ACP Application ID NCC4 Needed for second protocol Needed for third protocol Needed for fourth protocol ACP Object Address NCC1 ACP Device Address NCC1 ACP Object Address NCC2 ACP Device Address NCC2 ACP Object Address NCC3 ACP Device Address NCC3 ACP Object Address NCC4 ACP Device Address NCC4 DNP3.0 Protocol Data DNP Application ID NCC1 Needed for first protocol DNP Application ID NCC2 Needed for second protocol 7-26

83 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Category/Section Attribute Remarks DNP Application ID NCC3 DNP Application ID NCC4 Needed for third protocol Needed for fourth protocol DNP3.0 Object Address NCC1 DNP3.0 Priority NCC1 Pull-down DNP 3.0 Object Address NCC2 DNP3.0 Priority NCC2 Pull-down DNP 3.0 Object Address NCC3 DNP3.0 Priority NCC3 Pull-down DNP 3.0 Object Address NCC4 DNP3.0 Priority NCC4 Pull-down ITYPE2 Protocol Data ITYPE2 Application ID NCC1 Needed for first protocol ITYPE2 Application ID NCC2 ITYPE2 Application ID NCC3 ITYPE2 Application ID NCC4 Needed for second protocol Needed for third protocol Needed for fourth protocol ITYPE2 Device No NCC1 ITYPE2 Group No NCC1 ITYPE2 Offset NCC1 ITYPE2 Device No NCC2 ITYPE2 Group No NCC2 ITYPE2 Offset NCC2 ITYPE2 Device No NCC3 ITYPE2 Group No NCC3 ITYPE2 Offset NCC3 ITYPE2 Device No NCC4 ITYPE2 Group No NCC4 ITYPE2 Offset NCC4 TG809 Protocol Data TG809 Application ID NCC1 Needed for first protocol TG809 Application ID NCC2 TG809 Application ID NCC3 TG809 Application ID NCC4 Needed for second protocol Needed for third protocol Needed for fourth protocol TG809 Station No NCC1 TG809 Cabinet No NCC1 TG809 Tier No NCC1 TG809 Slot No NCC1 TG809 Point No NCC1 TG809 Is Hardware Point NCC 1 Bool; Pull-down TG809 Station No NCC2 TG809 Cabinet No NCC2 TG809 Tier No NCC2 7-27

84 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Category/Section Attribute Remarks TG809 Slot No NCC2 TG809 Point No NCC2 TG809 Is Hardware Point NCC 2 Bool; Pull-down TG809 Station No NCC3 TG809 Cabinate No NCC3 TG809 Tier No NCC3 TG809 Slot No NCC3 TG809 Point No NCC3 TG809 Is Hardware Point NCC 3 Bool; Pull-down TG809 Station No NCC4 TG809 Cabinate No NCC4 TG809 Tier No NCC4 TG809 Slot No NCC4 TG809 Point No NCC4 TG809 Is Hardware Point NCC 4 Bool; Pull-down Sinaut Protocol Data Sinaut Application ID NCC1 Not supported Sinaut Application ID NCC2 Not supported IEC 104 Protocol Data IEC104 Application ID NCC1 Needed for first protocol IEC104 Application ID NCC2 Needed for second protocol IEC104 Common Address ASDU NCC1 IEC104 Information Object Address NCC1 Group Configuration No NCC1 Additional Data Type description NCC1 IEC104 Common Address ASDU NCC2 IEC104 Information Object Address NCC2 Group Configuration No NCC1 Additional Data Type description NCC1 IEC61850 Protocol IEC61850 Application ID COM581 Application Id IEC61850 Signal Identification Needed for each signal (do not modify) IEC61850 Used As PSF Protocol Data PSF Application ID Always needed for module PSF Application Caption Always needed for module PSF Sequence No PSF Entry Type Pull-down value needed only for signal PSF Signal Port PSF FUP Function Name PSF FUP Scaling Factor PSF FUP Function Type Text Value only needed for function block Text; Pull-down 7-28

85 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Category/Section Attribute Remarks PSF FUP Scanning Cycle Time PSF FUP Input Type PSF FUP Output Type Pull-down value only needed for function block Pull-down value only needed for function block PSF FUP Function Variant DIA Protocol Data DIA Application ID Needed for protocol DIA Station Address DIA Application Address DIA Information Address Table 7.3 DIA Sequential Event Recording Signal attributes Pull-down NOTICE: A full stop (.) is not permitted in the text fields. 7-29

86 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Compiling and structuring a signal list It is advisable to devise scheme for assigning signal names that enables the signals to be easily recognized and associated when working with CAP581. Signal addresses are based on the data entered in the Technical Signal Description column of the table and the specified protocol. As far as the signal structure for CAP581 is concerned, only the data entered in the Technical Signal Description column are of consequence, i.e.: Station Name: Name of the Plant object node in the CAP581 database Bay Name: Name of the External Device object node in the CAP581 database Device Name: Name of the Device object node in the CAP581 database Signal Name: Name des Signals Signal Type: Signal type selected from the pull-down list Fig Signal types permitted in the signal list Example of exporting signals The example below illustrates the effect of the data entered in the Technical Signal Description column of the signal table on the CAP581 tree structure. The following signal list is exported into CAP581: Fig Example 1 of an exported signal list 7-30

87 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd NOTICE: The grey columns of a section are essential for exporting the data for a line. 7-31

88 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Starting the signal export function Once the signal list has been compiled according to the requirements of the COM581 gateway, exporting data to the CAP581 can start. This is done by selecting the relevant lines and starting the data export macro. Fig Signal list: Signals marked for exporting into CAP581 Starting the MS Excel macro: Click on the button Export to CAP581 on the CAP581 toolbar. Fig Export To CAP581 button The macro first displays a dialogue which permits a target CAP581 database for the exported data to be selected. Fig Dialogue for selecting a target CAP581 database The data are exported upon clicking on the Open button. This process can take some time depending on the number of lines being exported. MS Excel cannot be used during this time. An x appears in the Import/Export Flag column for every signal that has been correctly exported into the CAP581 database. The Excel list is saved as soon as exportation is complete. 7-32

89 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Fig Signal list after successfully exporting a CAP581 project database NOTICE: Lines that are either not selected or have a x in the Export Flag column are not exported. The N and M marked lines will be exported. The lines marked with D flag are ignored during the export (They have to be manually deleted in the CAP tool). NOTICE: Providing they are selected, signals from different sheets can be exported from the same Excel file. NOTICE: Import operations for several COM581 s must be performed separately if the same application ID is used. This necessitates arranging the order of the COM581 objects first. NOTICE: While data is being imported, the target CAP581 database must not be processed or viewed Re-exporting a signal list While signals are being exported, they are compared with those specified in the signal list and the protocol attributes of a signal that already exists are overwritten. However, it is not possible to overwrite the attributes in the Technical Signal Description section of an existing signal and an error message is generated in such cases. Only new signals and changes are imported into the protocol section. NOTICE: The x in the Import Flag column has to be deleted before signals can be re-exported. 7-33

90 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Errors while exporting signals If an x is missing from the Import Flag column, the cause could be one of the following: The line was not selected No bay name entered No signal name entered No signal type entered An inadmissible signal type entered Two station bus addresses Two remote control addresses Missing addresses Incorrect application ID s entered. The following example shows some signals that were not imported and explains why. Fig Errors while exporting signals Explanation: The first two signals were correctly imported and the Import Flag was set. Signal and address errors are marked red and where necessary a comment relating to the error is added in the Import Message column. Line No. 6: Line No. 7: Line No. 8: Line No. 9: Line No.10: Line No.11: Line No.12: No bay name entered No signal name entered No signal type entered Incorrect signal type entered, select correct one from pull-down list LON Object Address already assigned Incorrect application ID entered Application ID missing, input compulsory 7-34

91 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Line No.13: Line No.14: Line No.15: Line No.16: Line No.17: Line No.18: Line No.19: LON Unit Address missing, input compulsory LON Object Address missing IEC101 addresses already assigned Incorrect application ID entered Application ID missing, input compulsory Imported with the default IEC101 addresses Default IEC101 addresses already assigned. Other error messages such as Import Error 150 may be displayed following importation. A complete list of error messages is included in Section NOTICE: Ranges of error message numbers: IEC103 master connections General errors LON connections MVB connections PSF connections Work in CAP581 Tool Once all signals imported the rest of the work has to be done in the CAP581 Tool. 7-35

92 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Connecting SPI signals (single point indication) Fig Location Structure: LON SPI signal or IEC101 SPI signal Fig Signal Tree: Linked signals for an object signal version 7-36

93 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Connecting command signals Fig Location Structure: LON CMD signal or IEC101 CMD signal Fig Signal Tree: Linked signals for an object signal version Adding and connecting signals manually NOTICE: In order to preserve data consistency between the project databank and the Excel signal list, it is recommended that signals be added manually only as an exception. 7-37

94 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C In the case of projects into which no signals have been imported hitherto, a Plant and an External Device object have to be inserted after the hardware (see Fig. 7.36). (These objects are automatically added when data are imported.) Fig Structure down to the External Device level in the Location Structure and Signal Tree views Before two signals can be connected, a SignalVersion object has to be created in the Signal Tree (see Fig. 7.37). Fig Signal Tree after a SignalVersion object has been inserted A Source Signal (see Fig. 7.38) and a Sink Signal (see Fig. 7.39) are also necessary. These are added to the protocols being used in the basic structure together with their associated data type. Details of the protocols and their signal data types are given in Section 8. Fig LON as signal source 7-38

95 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Fig IEC 101 as signal sink The next thing is to link the Source Signal to the SignalVersion that has been added (see Fig. 7.40). This can be achieved using the drag and drop technique (see Section 5.3.6). A context menu with a choice of permissible operations appears when the right mouse button is released (see Fig. 7.41). Fig Linked Source signals Fig Context menu with a choice of permissible operations 7-39

96 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C The Sink signal is then linked in the same way under the previously linked Source Signal (see Fig and Fig. 7.44). Fig Linked Sink signals Fig Context menu with a choice of permissible operations Fig A completely linked signal connection from LON to IEC Eliminating a signal connection A signal connection may be eliminated stepwise in the signal tree. As a first step the sink signal is removed by activating the context menu on the object and calling up Remove Link (Section 7-40

97 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd and 5.4.7). As a second step the source signal is removed like in the first step. If there are further sink signals present they are also removed. As a third step the SignalVersion may be erased and the signals connected under this object are removed. NOTICE: All objects erased in the signal tree are exclusively removed from this tree. Objects with the source in the location structure (e.g. signal objects) are erased in the location structure. 7-41

98 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C 7.3. Automatic transfer of attributes The Apply to same in branch function is intended for editing an attribute which concerns a number of data points, e.g. measured variable scaling factors and settings, types of commands, single and double signals, signal edge filters etc. NOTICE: Attributes are only transferred automatically for the first tab after the General tab. Example: Normally changes, e.g. of a measured variable, have to be made in the Properties dialogue. Having to perform this for more than 100 measured variables can be somewhat tiresome. Thus the Apply to... function permits a change to be applied to all the measured variables assigned to a signal name, a bay unit or all the measured variables that have been configured in a COM581. Fig Apply to : Measured variable settings Fig shows the currently valid default measured variable settings. By way of example, it is assumed that the scaling factor has to be set to and the accumulating value to 10% for all the measured variables. 7-42

99 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Open the Apply to... function by clicking on the button with the icon to the left of the question mark in the top left-hand corner of the properties dialogue. Fig Apply to : Measured variable settings to be changed Check boxes of the attributes to be changed and enter the new values in the respective Value fields (see Fig. 7.46). Select the object in the tree with the mouse for which the measured values have to be changed at the lower hierarchical level, i.e. on Measurand Value (Fig. 7.47). This means that the new settings apply to all the measured variables below this level. Fig Apply to : Settings to be changed for all measured variables Now click on the Apply to same in branch button to change the settings for all the measured values. 7-43

100 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Click on the button with the red arrow to close the Apply to... dialogue. Fig shows the confirmation of the settings for the measured variables after executing the Apply to... function. Fig Apply to : Confirmation of the new settings 7-44

101 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd July Attribute and protocol configurations 8.1. Basic configuration settings Project External devices Plant External Device COM Queue Configurations Queue configuration Time management General description of time management Example of configuring time management for operation via LON Example of configuring time management for operation via an MVB TIM configuration with a redundant time master VME CPU (IMP, ISG, ISP) IMP board ISG board ISP board Serial line Ethernet line VME device Modem Signal version LON (LON device) LON application LON data point LON integrated totals LON measurand LON transparent data LON SPA data point LON NV data point LON NV measurand LON NV Bit string Filter configuration LON Nodes LON node LON logical device

102 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C LON Node (LSG) Logical SPA Device LON/SPA gateway (LSG) SPA command on a LON device LON SPA commands for REF and REO devices Configuring an Eberle tap-changer Configuring the node and device Configuring signals Limitations Settings specifically for theiec101 protocol Settings specifically for thetg809 protocol Switching authority (local/remote handling) Configuring the node and device Configuring signals Limitations IEC IEC103 master application IEC103 Datapoint Engineering procedure and suggestions IEC IEC101 slave application IEC101 data point IEC101 counter IEC101 indication IEC101 measurand IEC101 command IEC101 maintenance information Destination device configuration Masking addresses Address masking example Group configuration IEC101 group RP570 / RP RP57x slave application RP57x data point RP57x counter RP57x indication RP57x measurand RP57x command DNP DNP30 slave application DNP3 data point

103 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd DNP3 Counter DNP3 Indication DNP3 measurand DNP3 command TG TG809 application TG809 data point TG809 counter TG809 indication TG809 measurand TG809 RTU configuration ACP ACP application ACP data point Example for configuring the communication MicroSCADA - COM IEC IEC61850 application IEC61850 data points Engineering procedure and suggestions IEC IEC104 slave application IEC104 data point DIA diagnosis signals DIA application DIA data point Error messages generated by the DIA system (Error No.) Example for the configuration of an error message Project-specific function (PSF) Limitations and miscellaneous Special requirements Response during system start-up Data processing Status messages Measured variables Sequence of events (SOE) Commands Transparent data Counts Basic functions

104 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Generating binary general alarms Generating diagnostic general alarms Generating command sequences Type conversion in general Other functions Overview of the function blocks Engineering a PSF using the import function Creating a PSF application Configuring a function in the signal list Configuring function input and output signals Schematic illustration of PSF engineering procedure Manually engineering a PSF Creating a PSF function Configuring an inversion Engineering a PSF by importing data Fleeting signals, command sequences and conversion Introduction to engineering a PSF for neutral current General explanation Example of scale adjustment Example of addition Example of Geometric Add Example of Complex Addition Example of the neutral current function

105 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd 8. Attribute and protocol configurations Overview Basic configuration Project External devices Plant External device COM581 Queue Time Interbay bus LON IEC61850 Connection to protection IEC103 Protocols IEC101 RP57x DNP30 IEC104 Diagnosis DIA PSF TG809 ACP VME CPU (IMP, ISG, IMP) Serial line Ethernet line Modem Signal version 8.1. Basic configuration settings Fig. 8.1 Overview of the items included in the basic configuration 8-5

106 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Properties The Properties dialogue of all the items in a project includes at least a General tab. The attributes are identical in all cases; just the value entered for Caption is different (the ID is also different, but cannot be changed). Fig. 8.2 General tab in the Properties dialogue Attribute Caption Comment ID Freeze Table 8.1 Remarks Attribute name Provision for entering a comment Internal address of the CAP581 tool Finalizes the name, no further change possible (not supported) COM581: General settings NOTICE: No further explanation is given of the properties dialogue Project Fig. 8.3 Project object in Location Structure Project object at the top of the CAP581 tree structure, which can neither, be deleted nor linked below another object. 8-6

107 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Insert new object COM581 Configuration Structuring node Properties Fig. 8.4 Database information tab in the Project properties dialogue Version Number This refers to the version of the database, which has to correspond to the version of the tool for new projects External devices Fig. 8.5 External Devices object This is basically an auxiliary object that enables an item of plant to be added. It can be neither deleted nor linked below another object, nor does it have any special attributes. Insert new object Plant Delete object No Remove link No Properties None 8-7

108 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Plant Fig. 8.6 Plant in the Location Structure view Plant is generally the station or the designation of the project. Insert new object External Device Delete object Yes This object can only be deleted in the Location Structure view, in which case all the signals and their connections below the device in the structure are also deleted. Remove link No Properties None After this object is added, a link is automatically created in the signal tree. Fig. 8.7 Plant object linked in the Signal Tree Insert new object None Delete object No Remove link No Properties None NOTICE: The database builder can be started by opening the context menu in the Signal Tree view with the right mouse button. 8-8

109 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd External Device Fig. 8.8 External Device in the Location Structure view Insert new object None Delete object Yes This object can only be deleted in the Location Structure view, in which case all the signals and their connections below the external devices in the structure are also deleted. Remove link No Properties None After this object is added, a link is automatically created in the signal tree. Fig. 8.9 External Device in the Signal Tree view Insert new object Signal Version Structuring node Delete object No Remove link No Properties None 8-9

110 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C COM581 Fig A COM581 object as a device In this case, a COM581 is included as a device. A project can include several COM581 s, which have been added and configured in this way. Insert new object None Delete object Everything below this object is deleted. Remove link No Properties Fig Node ID tab in the COM581 properties dialogue Node ID Range: 1 63 Default: Automatically incremented (starting at 1) Description: This identifies the various COM581 s in a system and has to be unique within the system. 8-10

111 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Fig Download tab in the COM581 properties dialogue Download Table Range: Filename text Default: Com581.mdb Description: Any text as the name for the download database. The extension.mdb is optional. Target data model Range: Default: 5.0 Description: This setting determines the version of the download database, which must be the same as the version of the basic COM581 software. Create signal list Runs the export procedure when creating a signal list. Runs the export procedure when creating a report file. NOTICE: The project database has to be created first before either of the export procedures will run. 8-11

112 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Queue Configurations This is a structuring object. Insert new object Queue Configuration Delete object No Remove link No Properties None Queue configuration Fig Alternative queue responses The response of the system to a queue is configured automatically when creating a new project. Insert new object None Delete object Yes Remove link No Properties Fig Specific tab in the Queue Configuration dialogue 8-12

113 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Queue Size Range: Default: Description: Queue1 = 5000 Queue2 = 5000 Queue3 = 100 Defines the maximum number of entries in the three queues. These definitions provide choice of configurations for the six protocol application queues, which have to be configured for every application. Queue Overflow Strategy Range: Keep_the_Newest; Keep_the_Oldest; Keep_the_Oldest_and_then_the_Newest Default: Queue1 = Keep the newest Queue2 = Keep the oldest Queue3 = Keep the oldest and then the newest Description: Defines the response in the event of a queue overflow. Keep the newest: The event, which took place last, is saved and the oldest events are lost. The advantage of this response is that the process image is always correct when the queue is empty. Keep the oldest: The oldest events are saved. The advantage of this response is that the events that were recorded immediately after the series of events started are not lost. Keep the oldest and then the newest: This is a combination of the first two responses. It has the advantages of both, but the disadvantage of a gap in the middle of the records. NOTICE: Object settings may only be changed following consultation with the respective product manager. 8-13

114 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Time management Fig Structure created automatically The objects (links) created automatically below the Time Man- The structure de- agement object can neither be deleted nor set. pends on the hardware configuration General description of time management The synchronization scheme and time management depend on the hardware configuration, the protocols being used and the user s preferences. The CPU boards used in COM581 (IMP, ISG and ISP) have to be configured in the time management function. Each of the three boards can be connected to several interfaces (MVB, VME, serial line or Ethernet) via which the system time is distributed. Some interfaces (MVB and VME) can accommodate several CPU boards. Each of the boards at any of the interfaces can perform different time management functions (master, slave or redundant master). Either absolute or relative time can be transferred via the respective medium (MVB, VME, serial line or Ethernet). 8-14

115 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Time master A time master generates the time for all the other units. Time slave A time slave receives the time signal from the time master. Redundant time master The redundant time master operates as a backup for the time master, i.e. when the latter fails the redundant time master acts as time master. NOTICE: Both boards have to be registered for the corresponding bus segment in both COM581 gateways. COM581 RP571 Slave DCF77 IMP Master Slave ISP ISG Slave Slave ISP Slave VME MVB IP Master/red. Master MVB IP Master/red. Master MVB IP Master/red. Master IBB Fig Illustration of the various time management schemes Fig shows the different synchronization functions performed by the respective processor units. Their functions can be seen from the examples below. 8-15

116 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Ethernet_Line Serial_Line2 COM581 IMP ISP IG IType2 ISG IS VME Serial_Line1 RP571 External Clock IBB1 IBB2 RTU REx... IBC Master Clock Slave Clock Hardware Clock Fig COM581 acting as time master on an MVB and synchronized to a radio clock Ethernet_Line COM581-1 IMP ISG IType2 ISG VME IBB1 External Clock COM581-2 I MP VME ISG ISG M aster Clock S lave Clock Hardware Clock Fig COM581 acting as redundant time master on an MVB 8-16

117 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Synchronization on an MVB: Synchronization on a LON: COM581 is synchronized to a DCF77 or GPS radio clock from which it receives a time telegram (time string in seconds). It also requires a minute impulse from the radio clock. The internal COM581 clock continues to operate and synchronize the system as master in the event of a radio clock failure, however, the qual- ity attribute IV (invalid) is added to all the time tags. COM581 cannot act as time master via a LON Example of configuring time management for operation via LON This Section describes the procedure for configuring the distribution of synchronizing signals for a system with LON station bus protocol. Fig Time management after configuring the hardware Fig shows the time management scheme, which is automatically created by CAP581 once the hardware, has been configured. The final configuration is based on this initial configuration. Both ISG boards are connected to the VME as slaves. The IMP board is time master. It is only necessary to configure the time management scheme for LON operation. Explanation of time management: The radio clock is located on the RER111 (star-coupler) and distributes the time signal via the LON bus. It is thus the time master. The master board (IMP) with the LON master application receives the time signal from the LON bus and therefore acts as a slave. 8-17

118 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C The IMP board is also the time master on the VME and has to distribute the time signal to the two ISG boards which are there- fore slaves on the VME. Configuring the time management scheme does not present a problem providing one can determine for each project which unit acts as time master and which as time slave. The next step is to set the IMP board in the LON device as time slave. This is achieved by selecting the IMP board and dragging it while holding the right mouse button depressed to Slave below LON Device. Fig TIM: Selecting an object for linking the IMP board Upon releasing the mouse button, a context menu appears in which selecting Link here concludes the operation. 8-18

119 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Fig TIM: Linking the IMP board at Slave below LON Device If the above operation is carried out correctly, the configuration of the project example is as given in the next figure. Fig Time management scheme configured for the example project 8-19

120 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Example of configuring time management for operation via an MVB The following example explains in steps the configuration of the time management function in the case of an MVB. Fig MVB time management with radio clock and RP571 protocol An external radio clock (DCF77 or GPS) is connected via a serial line, e.g. serial line GPS, to the COM581. The radio clock is time master and synchronizes the IMP board via communication port 3. The serial line has to be established manually on the IMP board and linked below Time Management. Since the IMP board receives the time signal via the serial interface, it acts as a time slave. This board, however, has to distribute the time signal via the MVB to all the bay units connected to it and is therefore the time master as far as the MVB and also the VME are concerned. The ISG board with the RP571 protocol receives the time signal via the VME and therefore has to be configured as a time slave. 8-20

121 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd TIM configuration with a redundant time master A second COM581 has to be configured in this case and the respective CPU board linked to the time management function. There is the possibility of configuring several COM581 s as re- dundant time masters, however; at least two redundant COM581 s have to be entered. Should, for example, COM581_1 not be available for local time control, COM581_2 takes over as time master for power system control (see Fig. 8.24). The COM581 that completes initiation first becomes the active time master and the one that initiates second the standby time master. If the active time master fails, the standby time master becomes the active time master and distributes the time signal via the MVB. This configuration requires that both COM581 s be equipped with independent connections to the DCF 77 or GPS radio clock. Ideally, two radio clocks are used or one with two outputs. The figure below shows a redundant time master scheme in a redundant MVB (IBB) scheme. 8-21

122 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Fig TIM settings for the redundant time master COM581_1 The settings for the second communication processor (COM581_2) i n a redundant time management scheme are the same as shown above. 8-22

123 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd VME Fig VME bus object A VME is part of the COM581 object structure and an IMP board is automatically included. Insert new object ISG ISP Delete object No Remove link No Properties Fig Time Mode tab in the VME properties dialogue Time Distribution Mode Range: Absolute or relative time Default: Absolute time Description: Not supported by COM CPU (IMP, ISG, ISP) Fig Overview of the three CPU types 8-23

124 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C IMP board Insert new object LON device Serial line A VME device with DIA is automatically added. Delete object No Remove link No Properties Fig The attributes for all the CPU s are the same Station Address Range: Default: In ascending order starting at 1 Description: Station address as configured (same as the Device ID entered in the COM581) Slot Number Range: Default: Description: 4 19 (in steps of three) 4 = IMP, ascending in threes (7, 10, 13 etc.) Corresponds to the CPU slot in the COM581 rack ISG board Insert new object Ethernet line Serial line VME device with PSF 8-24

125 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Delete object Yes Deletes everything below this object. Remove link No Properties See IMP board ISP board Insert new object LON device Serial line VEM device with PSF Delete object Yes Deletes everything below this object. Remove link No Properties See IMP board Serial line Fig Insert new object DNP30 Slave application (ISG board only) IEC101 Slave application (ISG board only) IEC103 Master application (ISP board only) Modem RP570 Slave application (ISG board only) RP571 Slave application (ISG board only) TG809 Application (ISG board only) Delete object Yes Deletes everything below this object. Remove link No 8-25

126 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Properties Fig Specific tab in the Serial Line properties dialogue Port Number Range: 1 21 Default: 3 Description: This defines the port for data communication via the serial line. Serial communication takes place either electrically via an RS232 serial port, an optical interof a CPU03 board or the back- face on the front plane and an RS445 star-coupler. The following convention applies to all protocols with the exception of IEC103: Port No. 3 SCC3 4 SCC4 Electrical interface on CPU03 For the convention applicable to the IEC103 protothe col refer to Configuring IEC103 serial lines at beginning of Section Engineering procedure and suggestions. 8-26

127 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Baud Rate Range: Default: Description: Parity Range: Default: Description: Stop Bit Range: Default: Description: 50 Baud 110 Baud 200 Baud 300 Baud 600 Baud 1200 Baud 2400 Baud 4800 Baud 9600 Baud Baud Baud Baud Baud 9600 Baud Data transfer rate via the serial communication line in Baud (Bits per second). Even; Odd; No_Parity Even The parity bit serves to detect transmission errors. This data check is applied to every data byte (8 Bits). Even Parity: The sum of the bits in a data byte must be an even number. Odd Parity: The sum of the bits in a data byte must be an odd number. No_Parity: The parity bit function for checking data integrity is disabled. The type of parity check is often specified for the particular protocol. One_Bit; one_and_a_half_bit; two_bits One_Bit A receiver has to be able to detect the start of a new data byte. This is achieved with the aid of control bits, i.e. a Start Bit and one or several Stop Bits. The data byte as such is between start and stop bit(s). The value of the stop bit defines the number of stop bits. Number of Data Bits Range: 7 8 Default: 8 Description: Defines the number of bits in a data byte. Most protocols specify a value of

128 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Transmission Mode Range: Half duplex; full duplex; simplex Default: Half duplex Description: Defines the transmission mode via the communica- tions line. Half duplex: Transmission and receiving lines are never active at the same time. Only one communi- node can initiate a dialogue, i.e. the master. cation The RTU at the remote end only answers in response to a demand from the master. Full Duplex: Transmission and receiving lines can be active at the same time. Both master and RTU can initiate communication and both can transmit data without being requested to do so. Simplex: Data transmission is only possible in one direction. Bit Order Range: Default: Description: LSB first; MSB first LSB first Defines whether the first or last bit of a data byte is transmitted first. Bit Sense Range: Normal; inverted Default: Normal Description: Defines whether the bits in a data byte are normal or inverted. NOTICE: This information is not evaluated by COM581. Frame Range: None; IEC xxx Default: None Description: Defines to which standard the data telegrams conform. NOTICE: This information is not evaluated by COM

129 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Format Class Range: FT1 2; FT1 1; FT2; FT3 Default: FT1 2 Description: Defines which telegram format according to the international standard IEC defined by TC57 is used. Distribution Mode Range: Absolute time; relative time Default: Absolute time Description: Not supported by COM Ethernet line Fig Ethernet line object An Ethernet requ ires the protocols ACP, IEC104 or IEC Insert new object ACP IEC61850 Delete object Yes Deletes everything below this object. Remove link No Properties Fig Specific tab of the Ethernet Line properties dialogue 8-29

130 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Number of Buffered Messages Range: 4 10 Default: 4 Description: Defines the maximum number of buffered mesused for the Type 2 application for statistical sages purposes VME device Fig VME device object A VME device is a structuring object. Depending on the type of CPU board, it automatically includes a DIA or PSF application. Insert new object DIA (IMP board only) PSF (ISP and ISG boards) Delete object Yes Deletes everything Remove link No Properties None below this object Modem Fig Modem object The serial communication can operate via a modem. Insert new object No Delete object Yes Remove link No 8-30

131 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Properties Fig Specific tab of the Modem properties dialogue Modem Type Range: Default: Description: None; Mod 23WT20; Standard None Defines the data communication via a modem and the type of modem. RTS On Delay (ms) Range: Default: 0 Description: Only applies to modem operation and defines the time in milliseconds when the carrier should be switched on before data are transferred via the communications line. RTS Off Delay (ms) Range: Default: 0 Description: Only applies to modem operation and defines the time in milliseconds when the carrier should be switched off after data have been transferred via the communications line. RTS On Range: Default: Description: True; false True Only applies to modem operation and defines whether the carrier is permanently switched on or operates in a pulsed mode. 8-31

132 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Signal version Fig Signal Version object in the signal tree Insert new object No Delete object Yes Deletes everything below this object. Remove link No Properties Fig Specific tab of the Signal properties dialogue Signaltype Range: Integrated totals (DI) Single point indication Measured value 16 Bit Step position information Command Sequence of events (BI) System diagnosis (SON) System control Transparent data Maintenance information Double point indication File transfer Integrated totals (PC) Measured value 32 Bit System diagnosis (BLS) Bit string undefined 8-32

133 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Default: Description: undefined While linking source and sink, this attribute is redefined each time, firstly by the source signal and then by the sink signal. There is only a limited choice of data types after the source signal. The final data type is chosen and set to Read only by the sink signal. If a corresponding data type is not detected in the sink signal, the limited choice continues to be available and the value remains undefined. In this case, the desired value has to be set manually. NOTICE: During an import operation, the value of the data type is assigned automatically according to the import list. ABB Signal Text Range: Text Default: Description: Signal description determined during project engineering Customer Signal Text Range: Text Default: Description: Signal description chosen by the user. NOTICE: Signal description texts are not written in the download database. NOTICE: All the objects in the signal tree that are deleted are only deleted from the signal tree. Objects of local structure origin (e.g. signal objects) are not deleted from the local structure. 8-33

134 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C 8.2. LON (LON device) The LON bus can be configured on either an IMP or an ISP board. The first thing to configure is a LON Device object at the hig hest level of the tree. All structuring objects below which the signals, filters an d nodes are added are created automatically. Each of the obje cts belonging to a LON device is described in this section. Fig LON Device at the highest level in the tree Insert new object No Delete object Yes Remove link No Properties Fig Specific tab of the LON Device properties dialogue with the setting for the time distribution mode Time Distribution Mode Range: Absolute time; relative time Default: Absolute time Description: Not supported by COM

135 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd LON application Fig LON Application object No distinction is made between master and slave for a LON ap- The differing response at the connection level (cli- plication. ent/server) follows from the configuration. The application s LON Unit Address can be derived from the LON Node Configuration. It is a logical device address at the ap- (events, signals and plication level. All process information measured values) for which the application acts as a server have this LON Unit Address (source oriented address assignment). Insert new object No Delete object No Remove link No Properties Fig Specific tab of the LON Application properties dialogue 8-35

136 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Subnet and Node ID Range: [1 255].[1 127] Default: 1.2 Description: In systems with a large data volume and a short re- a domain can be divided sponse time requirement, into sub-networks (1 255). Each sub-network can for its part be divided into nodes (1 127). Theoreti- can be connected to cally up to 65,535 logical units each node. Application ID Range: Default: Description: Suppress SOE Range: Default: Description: Allocated while adding object. Identification number which uniquely identifies the application within COM581. It is incremented each time by one and can then be reset. True; false False Determines whether an event with time tag is passed on simply as a status signal or event with time tag. When set to True, only a status signal is forwarded. Command Supervision Timeout (s) Range: Default: 10.0 Description: Determines the time during which commands are supervised. Should a bay unit fail to execute a de- or device failure), a signal is mand (device missing returned after this time reporting the event and in- cluding details as to the cause. Event Setup Retry Time (s) Range: Default: Description: Determines the time during which the LON applica- communication with the tion attempts to establish bay units. DIA Object Address Range: Default: 4 Description: Defines the object address of the diagnosis signal. 8-36

137 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd DIA Data Type Range: Single indication; system diagnosis Default: Single indication Description: Determines the data type to be used as diagnosis signal. NO TICE: The diagnosis signal is 0 in normal operation and 1 when a device is faulty. Send Indication Range: Default: Description: LON data point with Time Tag True; false True Determines whether an event is transferred to Channel 2 with or without a time tag. The time tag is the local time on the LON board of the COM581. Fig Unlinked LON Sink Double Indication object Fig Linked LON Sink Double Indication object in the signal tree Fig Arrangement of the structuring objects for a LON data point 8-37

138 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Insert new object Sink data points Integrated Totals LON sink integrated totals Structuring node Indication LON sink double indication LON sink single indication Structuring node Measurand Value Measured 16 bit LON sink value Measured 32 bit LON sink value Structuring node Step Position Information LON sink step position information Structuring node Command LON sink command Structuring node Sequence of Events LON sink sequence of events Structuring node System Diagnosis LON sink sequence of events LON sink single indication LON sink system diagnosis Structuring node System Control LON sink sequence of events LON sink single indication Structuring node Transparent Data LON sink transparent data Structuring node Maintenance Information LON sink sequence of events LON sink single indication Structuring node Bitstring LON sink Bit string Structuring node Source data points Integrated Totals LON sink integrated totals Structuring node Indication LON source double indication LON source single indication Structuring node 8-38

139 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Measurand Value Measured 16 bit LON source value Measured 32 bit LON source value Structuring node Step Position Information LON source step position information Structuring node Command LON source command Structuring node Sequence of Events LON source sequence of events Structuring node System Diagnosis LON source sequence of events LON source single indication LON source system diagnosis Structuring node System Control LON source sequence of events LON source single indication Structuring node Transparent Data LON source transparent data Structuring node Maintenance Information LON source sequence of events LON source single indication Structuring node Bitstring LON source bit string Structuring node Delete object Yes, all the signals that have been added can be deleted. Remove link This is permitted in the signal tree. 8-39

140 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Properties Fig Address tab in the LON Sink Double Indication properties dialogue Unit and Object Address Range: [ ].[ ] Default: Allocated when object added (per application starting at 1.0). Description: In each LON application, a LON data point has a unique Unit Address and Object Address. Unit Address: This is the same as the bay unit address which is a logical node number. A physical LON node can comprise several logical LON nodes. For example, control and protection devices in a bay unit can be divided into logical units and connected to a LON node interface. Object Address: This is the signal address in a logical LON node. It must be unique within the logi- LON cal node. 8-40

141 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Data Type Range: Single indication Double indication Sequence of events Step position information Measured value signed 16 Measured value scaled 32 Measured value real 32 Integrated totals Command Transparent SPA data File System diagnosis Bit string16 Bit string32 Pulse counter Transparent data 101 Transparent data 103 (source only) (source only) Default Depends on the signal object. Description: The attribute is automatically set to suit the data type of the signal object. However, the value for certain objects can be changed manually (see next section). Internal Address (read only) Range: Default: Inadmissible value Description: A consecutive value is automatically allocated when linking a source signal. The same value is allocated to the sink signal as to the respective source signal. This ID is uniquely identifies the signal connection. Fig Filter Configuration tab in the LON Sink Double Indication properties dialogue 8-41

142 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Filter Configuration No. Range: Default: 1 Description: By linking the LON data points to the Filter Configu- with a Filter No. at ration, all spontaneous events can be transferred to the devices that are configured the time communication is established. A LON data point can therefore belong to many (max. 127) difassigned to several event ferent filters and can be filters. The filters enable the client to determine which information is spontaneously sent when opening an event session LON integrated totals The data types of the LON Sink Integrated Totals and LON Source Integrated Totals objects can be changed. Data Type Range: Default: Description: LON measurand LON sink integrated totals LON pulse counter LON sink integrated totals Defines the data type for LON counter objects. LON sink integrated totals: These are the binary totals of cumulated impulses during a predefined period. When transferred the values are tagged as Intermediate Reading or End Of Period Reading and have a consecutive number. LON sink pulse counter: These are the binary totals of cumulated impulses during a predefined pe- riod. The data types of the LON Sink Measurand value 32 Bit and LON Source Measurand value 32 Bit objects can be changed. Data Type Range: Default: Description: LON measurand value Real32 LON measurand value Scaled32 LON measurand value Real32 Determines the data transfer format for LON measured values. Real32: Corresponds to R32-IEEE STD 754 floating point. Scaled32: 32 Bit signed integer in twos complement format. 8-42

143 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd LON transparent data The data type of the LON Source Transparent Data object can be changed. Data Type Range: Default: Description: LON transparent data SPA LON transparent data 101 LON transparent data 103 LON transparent data SPA Determines the data format that can be packed into a transparent data object LON SPA data point All SPA signal objects are located in the structure described in Section LON data point. Insert new object Sink data points Command LON SPA Sink Command Structuring node Source data po Indication Command Delete object Yes, all the signals ints LON SPA source command Structuring node Remove link This is permitted in the signal tree. LON SPA source double indication LON SPA source single indication Structuring node that have been added can be deleted. 8-43

144 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Properties Fig Address tab in the LON SPA Sink Command properties dialogue Unit Address Range: Default: 1 Description: The Unit Address is used as the SPA node ad- connected to an LSG dress. Every SPA device must be configured as a logical unit. The maximum permissible value is 999. Data Type Range: Default: Description: LON SPA command LON transparent data SPA Depends on what is selected in the signal tree. Depends on the type of signal selected and cannot be changed. SPA Channel Range: Default: 0 Description: This is part of the data point address. The SPA data point address comprises unit, channel and data number. The maximum permissible SPA channel value is

145 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd SPA Reg Type Range: Unused; I; O; S; V; M Default: 0 Description: Data transferred by the devices are allocated to one of the following data types: I: Input data O: S: V: Output data Setting values Variables (Internal) M: Memory data SPA Reg Nr. 1 Range: Default: 1 Description: This is the normal case and defines the starting position of the data range. SPA Reg Nr. 2 Range: Default: 1 Description: Defines the end of a data range and is only used in special cases. SPA Event 00 Range: 0 63 Default: 0 Description: Event number that associates an event with status 00 causing a change of status with an event with time tag. SPA Event 01 Range: 0 63 Default: 0 Description: Event number that associates an event with status 01 causing a change of status with an event with time tag. SPA Event 10 Range: 0 63 Default: 0 Description: Event number that associates an event with status 10 causing a change of status with an event with time tag. 8-45

146 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C SPA Event 11 Range: 0 63 Default: 0 Description: Event number that associates an event with status 11 causing a change of status with an event with time tag. Internal Address (read only) Range: Default: Inadmissible value Description: A consecutive value is automatically allocated when linking a source signal. The same value is allocated to the sink signal as to the respective source signal. This ID is uniquely identifies the signal connection LON NV data point All NV signal objects are located in the structure described in Section LON data point. Insert new object Sink data points Command LON NV sink command Structuring node Source data points Indication LON NV source double indication LON NV source single indication Structuring node Measurand Value LON NV source measurand value 16 bit LON NV source measurand value 32 bit Structuring node Command LON NV source command Structuring node System Diagnosis LON NV source system diagnosis Structuring node Bitstring LON NV source Bit string Structuring node Delete object Yes, all the signals that have been added can be deleted. 8-46

147 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Remove link This is permitted in the Signal Tree. Properties Fig Address tab in the LON NV Sink Command properties dialogue Unit Address Range: Default: 1 Description: The Unit Address is used as the LON node address. Every LON device must be configured as a logical unit. The maximum permissible value is 127. NV Selector Range: Default: Allocated while adding an object (per application starting at 0). Description: The NV Selector is used as a LON data number. The maximum permissible value is Data Type Range: Single indication Double indication Measured value signed 16 Measured value scaled 32 Measured value real 32 Command System diagnosis Bit string16 Bit string

148 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Internal Address (read only) Range: Default: Inadmissible value Description: A consecutive value is automatically allocated when linking a source signal. The same value is allocated to the sink signal as to the respective source signal. This ID is uniquely identifies the signal connection LON NV measurand The data type of a LON NV Source Measurand Value 32 Bit object can be changed. Data Type Range: LON NV measurand value real 32 LON NV measurand value scaled 32 Default: LON NV measurand value real 32 Description: Determines the data transfer format of LON NV measured values. Real32: Corresponds to R32-IEEE STD 754 floating point. Scaled32: 32 Bit signed integer in twos complement format LON NV Bit string The data type of a LON NV Source Bitstring object can be changed. Data Type Range: Default: Description: LON NV Bitstring16 LON NV Bitstring32 LON NV Bitstring16 Determines whether the data point is of type Bitstring16 as a 16 bit field or Bitstring32 as 32 bit field Filter configuration Fig Filter Configuration structure Filter Configuration enables any number of LON filters to be combined to form a typical configuration. Several filters can be selected at once by creating proper rules for Filter Configuration. 8-48

149 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd These filters enable the client to determine which information is spontaneously sent when opening an event session. For this purpose, every bay unit must be assigned a filter number and the data points must bear the respective filter number. Insert new object Filter number (in Filter Configurations). Delete object Yes (the filter configuration itself). Remove link No Properties Fig Filter number tab in the Filter Configuration properties dialogue Filter Number Range: Default: Allocated while adding object and is only indicated on the object itself. Description: Filters enable the events generated by a LON de- vice to be grouped and selectively scanned. Example: Events configured with filter 1 can only be trans- in a LON session that was ferred to the LON client opened using filter

150 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C LON Nodes Fig LON Nodes Insert new object LON Node LON Node (LSG) Delete object No Remove link No Properties None LON node Fig LON Node Its Subnet and Node ID uniquely determine the address of every physical device connected to the LON. LON Node: A LON network is a communication system to which several devices can be connected providing they are equipped with a LON coupler (neuron chip). Some devices can be connected to various sub-networks and each has its own unique addr ess (Domain, Subnet, Node) in each sub-network. Its LON Unit Address identifies a physical device at the application layer. Generally a device will have only one Unit Address, i.e. it is a LON Logical Device. It is possible, however, for several logical devices to be assigned to a physical unit (LON Node). Information relating to logical devices can be obtained by opening an event session. Insert new object LON logical device Delete object No Remove link No 8-50

151 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Properties Fig Address tab in the LON Node properties dialogue Subnet and Node ID Range: [1 255].[1 127] Default: Allocated while adding object. Description: In systems with a large data volume and a short response time requirement a domain can be divided into sub-networks (1 255). Each sub-network can for its part be divided into nodes (1 127). Theoreti- units can be connected to cally up to 65,535 logical each node. Activate History Events Range: True; false Default: False Description: Optionally, time tagged events from a bay unit can be saved without filtering. Records are removed should the list overflow. The LON application can request transfer of these events during a period of a minute before failure of the communication up to the time communication is restored. This parameter determines whether saved events are transferred after communication is established with a LON node. 8-51

152 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C LON logical device Fig LON Logical Device object The LON_Logical_Device table lists the allocation of unique logi- device addresses (application layer) to physical device with a cal unique LON address derived from its Node_No and Subnet_No (LON_Node table). As a rule, precisely one LON_Unit_Address is assigned to a physical device. In principle, however, many logical units can be assigned to a physical device. For example, by using the IEC103 protocol, 10 protective devices can be assigned to a unit address. During system initialization, an event session request is issued and communication established with all the devices listed in the LON_Logical_Device table from which data are to be received. All the servers are also listed in the LON_Logical_Device table with which a LON_Application has to establish communication as a client in order to receive (or transmit) data. Insert new object No Delete object Yes Remove link No Properties Fig Address tab in the LON Logical Device properties dialogue 8-52

153 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Unit Address Range: Default: Allocated while adding object. Descri ption: Defines the logical device address. Several logical Unit Addresses can be configured for a physical device LON Node ( LSG) Fig LON Node (LSG) object Insert new object Logical SPA device Delete object Yes Remove link No Properties Fig Addres s tab in th e LON Node (LSG) properties d ialogue Subnet and Node ID Range: [1 255].[1 127] Default: Allocated while adding object Description: In systems with a large data volume and a short response time requirement a domain can be divided into sub-networks (1 255). Each sub-network can for its part be divided into nodes (1 127). Theoretiup to 65,535 logical units can be connected to cally each node. 8-53

154 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C NV ALARM Selector Range: True; false Default: Description: Designates the address of a special signal. Maximum permissible value is Background Poll Cycle Range: 1 12 Default: 1 Description: All the data points of a unit in an LSG device are polled cyclically by a background function Logical SPA Device Fig Logical SPA Device object Insert new object No Delete object Yes Remove link No Properties Fig Address tab in the Logical SPA Device properties dialogue Unit Address Range: Default: Allocated while adding object Description: Defines the logical device address on the SPA bus. 8-54

155 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd LON/SPA gateway (LSG) COM581 supports SPA devices as well as purely LON devices. For this purpose, the SPA devices are connected to the LON bus via a LON/SPA gateway. The latter has capacity for up to eight SPA devices. The procedure for engineering a LON/SPA gateway (LSG) is as follows: 1. Create a LON NODE (LSG) with Subnet, Node ID and NV ALARM Selector for each LSG. Fig Dialogue for configu ring LSG s 2. Create a S PA device with a unit address for each LSG. Provision is made for a maximum of eight SPA devices per LSG. Fig Dialogue for configuring SPA devices 3. Importing the required data: Import the data from the Excel list into the CAP581 database. Note that an associated LSG and a SPA device were configured for every data point. 4. Rules for creating SPA signals in the Excel list: Either the LON Unit Address + NV Selector (e.g. for analogue values and the SON signa l) or the LON Unit Address + SPA Addresses (SPA channel + SPA Reg Type + SPA Reg 1 + SPA Reg 2 + possibly SPA Event SPA Event 11). 5. SPA command: An SPA command requires just the LON Unit Address, the SPA channel and the SPA Reg Type. 6. Supervision o f LSG and SPA devices: Insert a data point for system diagnosis (SON) in the Excel 8-55

156 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C list to supervise the SPA devices, taking care to configure the LON Unit Address and an NV Selector (any NV selector can be chosen) SPA command on a LON device If a LON device does not support the LAG 1.4 format in the command direction, COM581 can send an SPA Transparent Command via the LON bus. The LON Unit Address and the SPA data have to be configured in the Excel list for an SPA command LON SPA commands for REF and REO devices For REF541, REF543, REF545, REO5XX and REC561 devices extended LON SPA command handling is available. This en- ables to configure the select before operate or direct LON SPA commands as one datapoint with one NCC address. Fig LON SPA command dialog in CAP To configure the extended handling for a LON SPA command set the parameters according to Table

157 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Command IET SPA SPA SPA SPA SPA SPA Event type import Reg Reg Event 00 Event 01 Event sup- Nr.1 Nr.2 ported REF_SBO Yes X 6 select open 7 select close 11 execute 10 cancel REF_Direct Yes X 4 direct open 5 direct close X X REF_SBO_ Or_Direct 2 oper- ate open or direct open No X 1 select open or close 3 operate close or direct close 4 cancel REO_Single _SBO No X 10 select open 11 select close 12 execute 9 cancel REO_Single _Direct No X 7 direct open 8 direct close X X REO_Single _SBO_Or_D irect No X 10 select open or close 11 operate open or direct open 12 operate close or direct close 9 cancel REO_Single No X _Direct_To_ select select SBO open close 12 execute 9 cancel REO_Multiple_SBO Yes (first SPA data number) 512 select open 1024 select close 2048 execute 256 cancel REO_Multiple_Direct Yes (first SPA data number) 1 direct open 2 direct close X X REO_Multi- ple_sbo_or _Direct No (first 512 SPA select data open or number) close 1024 operate open or direct open 2048 operate close or direct close 256 cancel REO_Multiple_Direct_T o_sbo No (first SPA data number) select select open close 2048 execute 256 cancel 8-57

158 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Table 8.2 Command types For REF and REO devices 10 different types of commands can be configured. Dialog field SPA Reg Nr. 1 identifies the type of the command. Based on this type the IEC select before operate or direct command coming from NCC is converted to LON SPA command. Select before operate command for REF device (REF_SBO) is identified by value The import of a command of this type f rom IET to CAP581 excel list is supported. Whe n select off comes from NCC, a LON SPA command with SPA data number entered in co lumn SPA E vent 00 is sent. When select on comes from NCC, a LON SPA command with SPA data number entered in column SPA Ev ent 01 is sent. When execute off or execute on comes from NCC, a LON SPA command with SPA data number entered in column SPA Event 10 is sent. When cancel comes from NCC, a LON SPA command with SPA data number entered in column SPA Event 11 is sent (see Table 8.3). SPA Event Special meaning IEC meaning Data number (COCB1) 00 Open select Select off V6 01 Close select Select on V7 10 Execute Execute off or execute on V10 11 Cancel Cancel V11 Table 8.3 Meaning of SPA Event fields for REF_SBO command type Direct command for REF devic e (REF_Direct) is identified by valu e The import of a command of this type from IET to CAP581 excel list is supported (see Table 8.4). SPA Event Special meaning IEC meaning Data number 00 Direct open Execute off V4 (COCB1) 01 Direct close Execute on V5 Table 8.4 Meaning of SPA Event fields for REF_Direct command type 8-58

159 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Select before operate or direct command for REF device (REF_SBO_Or_Direct) is identified by value The import of a command of this type from IET to CAP581 excel list is not supported. The datapoint of this command type accepts from NCC select before operate or direct command (see Table 8.5). SPA Event Special meaning Special meaning IEC meaning Data number SBO direct 00 Select open or close X Select off or Not supported select on 01 Operate open Direct open Execute off By REF 10 Operate close Direct close Ex ecute on 11 Cancel X Cancel Table 8.5 Meaning of SPA type Event fields for REF_SBO_Or_Direct command REO devices with single command function configured are engineered in the same way as REF devices. Select before operate command for REO device single command function (REO_Single_SBO) is identified by value The import of a command of this type from IET to CAP581 excel list is not supported (see Table 8.6). SPA Event Special meaning IEC meaning Data number (CD01) 00 Open select Select off I9 01 Close select Select on I10 10 Execute Execute off or execute on I11 11 Cancel Cancel I12 Table 8.6 Meaning of SPA Event fields for REO_Single_SBO command type 8-59

160 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Direct command for REO device single command function (REO_Single_Direct) is identified by value The import of a command of this type from IET to CAP581 excel list is not sup- p orted (see Table 8.7). SPA Event Special meaning IEC meaning Data number (CD01) 00 Direct open Execute off I1 01 Direct close Execute on I2 Table 8.7 Meaning of SPA Event fields for REO_Single_Direct command type Select before operate or direct command for REO device single command function (REO_Single_SBO_Or_Direct) is identified by value The import of a command of this type from IET to CAP581 excel list is not supported. The datapoint of this command type accepts from NCC select before operate or direct command (see Table 8.8). SPA Event Special mean- Special mean- IEC meaning Data number ing SBO ing direct (CD01) 00 Select open or X Select off or I9 close select on 01 Operate open Direct open Execute off I10 10 Operate close Direct close Execute on I11 11 Cancel X Cancel I12 Table 8.8 Meaning of SPA Event fields for REO_Single_SBO_Or_Direct command type Direct to select before operate command for REO device single command function (REO_Single_Direct_To_SBO) is identified by value The import of a command of this type from IET to CAP581 excel list is not supported. The datapoint of this command type converts direct command from NCC to select be- fore operate LON SPA command (see Table 8.9). 8-60

161 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd SPA Event Special meaning IEC meaning Data numbers 00 Open select Execute off I9 (CD01) 01 Close select Execute on I10 10 Execute Execute off or on I11 11 Cancel Cancel I12 Table 8.9 Meaning of SPA Event fields for REO_Single_Direct_To_SBO command type REO devices with multiple command function configured are engineered in different way comparing to REO devices with single command function. The additional field that has to be set is SPA Reg Nr. 2. This field contains the SPA data number address of the first input of the configured multiple command function block. For the first multiple command function block CM01 the Spa Reg Nr. 2 would be 221. Which input of the multiple command function will be activated is defined by the integer data value sent in LON SPA command. To activate first input send value 1. To activate second input send value 2 to activate third input send value 4. Select before operate command for REO device multiple command function (REO_Multiple_SBO) is identified by value The import of a command of this type from IET to CAP581 excel list is supported (see Table 8.10). SPA Event Special meaning IEC meaning Data number (CM01) Value 00 Select open Select off I10 2**9 = Select close Select on I11 2**10 = Execute Execute off or execute on I12 2**11 = Cancel Cancel I9 2**8 = 256 Table 8.10 Meaning of SPA Event fields for REO_Multiple_SBO command type 8-61

162 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Direct command for REO device multiple command function (REO_Multiple_Direct) is identified by value The import of a command of this type from IET to CAP581 excel list is supported (see Table 8.11). SPA Event Special meaning IEC meaning Data numbers (CM01) Value 01 Operate open Execute off I1 2**0 = 1 10 Operate close Execute on I2 2**1 = 2 Table 8.11 Meaning of SPA Event fields for REO_Multiple_Direct command type Select before operate or direct command for REO device multiple command function (REO_Multiple_SBO_Or_Direct) is idenva lue The import of a command of this type from tified by IET to CAP581 excel list is not supported. The datapoint of this command type accepts from NCC select before operate or direct command (see Table 8.12). SPA Event Special Special IEC meaning Data number Value meaning meaning (CM01) SBO direct 00 Open or X Select off or I10 2**9 = 512 close select select on 01 Execute open 10 Execute close Direct open Execute off I11 2**10 = 1024 Direct close Execute on I12 2**11 = Cancel X Cancel I9 2**8 = 256 Table 8.12 Meaning of SPA Event fields for REO_Multiple_SBO_Or_Direct command type Direct to select before operate command for REO device multified by value The import of a command of this type from ple command function (REO_Multiple_Direct_To_SBO) is identi- IET to CAP581 excel list is not supported. The datapoint of this 8-62

163 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd command type converts direct command from NCC to select before operate LON SPA command (see Table 8.13) SPA Event Special meaning IEC meaning Data numbers Value SBO (CM01) 00 Open select Execute off I10 2**9 = Close select Execute on I11 2**10 = Execute Execute off or I12 2**11 = 2048 execute on 11 Cancel Cancel I9 2**8 = 256 Table 8.13 Meaning of SPA Event fields for REO_Multiple_Direct_To_SBO command type The LON SPA commands can be exported from excel list to CAP581 database like any other commands. The extended LON SPA command handling enables the NCC to operate in case of select before operate command four LON SPA addresses from one NCC address. That means only one datapoint (one line in excel list) is needed comparing to four datapoints used in the old implementation. However there are some limitations. The one datapoint for whole LON SPA select before operate command can be used only with IEC101, IEC104, DNP3s and ACP proto- cols. When configuring select before operate command from RP571 protocol for REF, REO single command function or REO multiple command function, two datapoints (two excel lines) are needed. It is because RP571 protocol select command carries no value information (see Table 8.14). 8-63

164 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Com- SPA SPA SPA SPA SPA SPA RP571 mand Reg Nr.1 Reg Nr.2 Event 00 Event 01 Event 10 Event 11 Address type REF X 6 select X 11 exe- 10 can SBO open cute cel open (Select (Operate (Cancel) Off) On Off) REF X 7 select X 11 exe- 10 can SBO close cute cel close (Select (Operate (Cancel) On) On Off) Table 8.14 REF, REO and RP571 When REO single or REO multiple command function with com- mand type select before operate or direct command and RP571 protocol is used one datapoint is enough because in this case select is common for o pen and for close. When using TG809 protocol only direct command can be used. (see Table 8.15). Com- SPA SPA SPA SPA SPA SPA TG809 mand Reg Nr.1 Reg Nr.2 Event 00 Event 01 Event 10 Event 11 Address type REF X 4 direct 5 direct X X 100 direct open close open (Operate (Operate Off) On) Table 8.15 REF, REO and TG809 The TG809 address that is configured is the address of the operate open command. The next address (101) is not configured and it is used for operate close command. SPA addresses used in Tables above depend on the REF or REO device configuration. 8-64

165 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Configuring an Eberle tap-changer For COM581 to be able to communicate with a tap-changer an LSG node (see Fig. 8.63) has to be configured which defines the bus and node address. A logical SPA/TC device also has to be added for each tap-changer to define the unit address. The signal type Network Variable is used for commands and status signals Configuring the node and device A LON node (LSG) has to be added to be able to configure a Logical SPA/Tap-changer device and the logical devices for the tap-changer added below it. The value of the unit address for the tap-changer must be in the range 901 to 999. Fig Configuring an SPA/Tap-changer device ( ) Configuring signals Signals have to be configured using the signal import list. A macro is provided for this purpose, which adds the 62 tap- changer signals. Fig Starting the macro for adding a tap-changer 8-65

166 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Fig Safety query to confirm the position Firstly the signal list is scanned for free unit addresses and free NV selector ranges that are available for the signals. Depending on the capacity of the PC processor, this procedure may take some time. Several tap-changers can be added in a single operation. The attributes Unit address and NV selector are incremented starting at the initial value. The station, bay and device names and the LON Application ID can already be set at this stage if desired. Fig Dialogue for setting supplementary information 8-66

167 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Fig Tap-. ch anger signals added by the macro 8-67

168 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C N OTICE: The data type (DINT) of the 32 Bit measured values of the signals TC position changes indication and TC position changes under load ind have to be edited in CAP581 after being imported. This involves changing the data type of these objects on the address p roperty tab to LON NV Measurand Real32. Fig Address properties tab Limitations Configuration: The Unit Address of the tap-changer must be the same as its Node Address The number of tap-changers is limited to 8. The CAP581 LSG node parameter Background Poll Cycle provides facility for setting the interval at which the COM581 general polling command is transmitted to the tap-changer. Settings: Parameter 1 corresponds to 600 seconds Parameter 2 corresponds to 1200 seconds (etc.) The tap-changer SNVT Alarm Selector may not be used (information only). WARNING: A tap-changer does not have a SON signal. 8-68

169 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Response in operation: COM581 transmits a Status Query Command to the tapchanger every 10 seconds. If the tap-changer does not retransmitted to the power system control centre (NCC). The 10 play, all the tap-changer data points are set to invalid and seconds are a fixed setting and cannot be changed by CAP Settings specifically for theiec101 protocol Fo r all IEC101 commands which are defined as set points, it is necessary to ma nually set the Command Type parameter to Scaled Set Point or Normalised Set Point using CAP Settings specifically for thetg809 protocol Tap-changer operation is restricted because TG809 only sup- ports pulsed (double) commands and no set point commands Switching authority (local/remote handling) A special configuration is available in COM581 for changing the switching authority of all LON protocols simultaneously from lo- cal to remote and vice versa. The change is executed by a nor- transmitted by a LON client (MicroScada or other COM581) via LON to the COM581. When a change is mal double command made from local to remote and vice versa, the status is transmitd to the power system control centres (NCC s). In the local te mode, NCC commands are not relayed to the LON bus and therefore the return confirmations are negative. 8-69

170 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Fig Overview of the local/remote switching authority function Configuring the node and device This is a special configuration, which requires the configuration of a number of ad ditional LON units. For a LON application in the same LON segment as MicroScada configure a virtual device with the same unit address as the LON application node ID. The unit can be configured under any node and receives the switching authority command from MicroScada. The object address for the command has to be The switching authority comma nd also has to be configured for other LON applications in orand therefore a virtual unit has to be config- der to block them ured for each of them. Their unit addresses depend on the address of the first virtual LON unit. General: Unit Address of the virtual LON device Board 1 (Slot ID 4) Unit Address Board 2 (Slot ID 7) = Unit Address Board 3 (Slot ID 10) = = Node ID of the LON application on Board 1 Unit Address of the virtual device on LON Board Unit Address of the virtual device on LON Board Example (see Fig. 8.70): Node ID Board 1 = 110 Unit Address of the virtual device on Board 1 = 110 Unit Address of the virtual device on Board 2 =

171 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Fig Configuring the node and device Configuring signals The switching authority command transmitted by MicroScada does not have to be configured using CAP581, but the signal s object address has to be The unit address is the same as the node ID of the LON application, in this example 110. The command has to be configured from the first LON board to the other in order to block it as well. In the example (see Fig. 8.71) this is the command data point (first LON application) (second LON application). The transmission of a status report to the NCC can also be configured. For this purpose, a source double indication from LON has to be linked to a sink indica tion from the NCC. The unit address of the LON indi- must be the same as the virtual unit. The indication object cation address must be set to

172 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Fig Configuring the indication and command Limitations The switching authority command has to be transmitted via the LON bus and not come from MicroScada via ACP to COM581. The unit and object addresses for switching authority (local/remote handling) cannot be configured using CAP581 in this version, because they are predefined and cannot be changed. 8-72

173 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd 8.3. IEC103 This section explains the processing of events generated by digi- tal protection devices, for example, an SAB (protection connec- tion) via IEC (IEC103), their internal transmission and marshalling in the ABB control system and their transfer to power system control via IEC101. An image of the process is maintained locally in COM581 on the basis of the protection signals it receives. Only such information is entered in the image as can be polled via IEC103. The events received from digital protection devices are transferred by COM58 1 without further processing via the IBB. Data relating to fleeting signals are transferred as such internally in the system via IEC103 and are not entered in the process imsystem permits protection events sent to the lo- cal control point or to power system control to be marshalled in age. The control any way. It is necessary to configure the target device on the bus (local control or power system control) and enter the addresses of the information to be transferred. Information provided by the protection devices, which has not been configured in the control system, is discarded by COM IEC103 master application Fig IEC103 Master Application object Insert new object No Delete object Yes Remove link No 8-73

174 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Properties Fig Specific tab with the settings in the IEC103 Master Application properties dialogue Application ID Range: Default: Allocated while adding object Description: Unique identification of the application within the COM581 system. Allocated in ascending order in increments of one and can then be reset. Period of Synchronization (s) Range: Default: 60 Description: Determines the period of the synchronizing cycle in seconds for all stations (broadcast). Period of General Interrogation (min) Range: 5 60 Default: 15 Description: To keep the process image up-to-date, a general polling request is sent periodically to all the stations as a background function. The period of the polling cycle is entered in minutes. 8-74

175 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Blocking Indication INF Range: Default: 20 D escription: Defines the Information Number of the Blocking In- dication INF. Throw Away Test Mode Telegram Range: True; false Default: False Description: Determines whether telegrams from stations designated by Test Mode (COT 7) should be forwarded or not. When set to False, the telegrams are forwarded to the next higher control level. Blocking Command FUN Range: Default: 255 Description: Neither power system control nor the IEC103 master can directly transfer data in the reporting direction. The follow ing scheme for disabling and enabling the transfe r of data in the reporting direction has been included: 1) A special command configured in association with the address FUN/INF for the attributes Blocking Command FUN and Blocking Com- the transfer of data in the re- mand INF controls porting direction. 2) A special signal configured together with the address FUN/INF in the attributes for Blocking Indication FUN and Blocking Indication INF con- of the above command. firms the receipt D efines the Function Type of the Blocking Command FUN. Blocking Command I NF Range: Default: 20 Description: Defines the Information Number of the Blocking Command INF. Blocking Indication FUN Range: Default: 255 Description: Defines the Function Type of the Blocking Indication FUN. 8-75

176 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Number of Telegram Retries Range: 0 10 Default: 3 Description: Determines how often a telegram is repeated in the event of communication failure. Should the latter be detected, the last telegram sent to a station is repeated as many times as specified (Number of Telegram Retries). At the same time, communication with the station at the link level is discontinued, declared to be not reachable and reinitialized by the next cycle. Generate IEC101 ACTTERM Range: True; false Default: True D escription: Determines whether the IEC103 master generates an ACTTERM telegram in the command sequence upon receipt of a command from the higher com- mand level. Example: Assuming a device receives an ACTIVATION com- mand from the IEC103 master and returns a confirmation of receipt to the IEC103 master, an ACTCON is sent to the higher control level. Should in this case Generate IEC101 ACTTERM be set to True, an ACTTERM telegram is also sent to the higher control level. No of Class One Requests Range: Default: 10 Description: Determines the maximum number of Class 1 re- 2 quests that are sent to a device in the active polling cycle. An active polling cycle starts with a Class request and a sequence of Class 1 requests, pro- viding Class 1 data are waiting to be transmitted in the device. ACTTERM Time Out (s) Range: De fault: 60 Description: If Generate IEC101 ACTTERM is set to True, this parameter determines the time in seconds after which the ACTTERM telegram is automatically generated. 8-76

177 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Base Polling Range: Default: Description: Suppress SOE Range: Default: Description: Status; Class1; Class2 Class2 Defines the telegram type for the basic polling cycle: Status: No Class 2 data are requested for Request Status of Link, Class 1 data are re- for ACD Bit = 1. quested Class 1: Request User Data Class 1 Class 2: For Request User Data Class 2, Class 1 data are requested for ACD Bit = 1. True; false False Determines whether the additional transmission of time tagged events via Channel 3 is disabled. Force Channel 3 Range: True; false Default: True Description: Determines whether Time Tagged Message with Relative Time is sent via Channel IEC103 Datapoint Fig Unlinked IEC103 Source Indication object Fig Linked IEC103 Source Indication object in the signal tree The various signals are added according to data type below the predefined structuring objects, which are arranged as shown in the figure below. 8-77

178 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Fig Arrangement of the structuring objects in the case of IEC103 data points Insert new object Sink Datapoints Command IEC103 Sink Command Structuring node Transparent Data IEC103 Sink File (generic data) Structuring node Source Datapoint Indication Sequence of Events System Diagnosis System Control Maintenance Information IEC103 Source Indication (signals) Structuring node Measurand Value IEC103 Source Measurand Value Structuring node Transparent Data IEC103 Source File (generic data) Structuring node Delete object Yes, all signals that are added can be deleted again. Remove link This operation is possible in the signal tree. 8-78

179 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Properties Fig Address tab in the IEC103 Source Indication properties dialogue Link Address, CAA, FUN, INF Range: [0 255].[0 255].[0 255].[0 255] Default: Allocated while adding object (starting at ) Description: The four-part IEC103 address (IEC103 Link Address, CAA, FUN, INF) must be unique for each protection link and direction of transmission, i.e. commands and signals can use the same address. The address range of the various protection devices depends on the protection functions that are implemented and is fixed. The application addresses of the data points (CAA, FUN, INF) are only unique in relation to the link address (IEC103 Link Address) for each IEC103 master. The process database for an IEC103 master application only includes data that can be requested by a general polling cycle. The standard IEC103 specifies which data may be polled in the compatible range. In the private range, this has to be determined from the reaction of the protection devices in response to a general polling cycle. Data Type Range: Default: Description: IEC103 Command IEC103 Indication IEC103 Measurand IEC103 File Determined at time of selection. Defines the signal data type, which cannot be changed on an existing object. 8-79

180 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Internal Address (read only) Range: Default: Inadmissible value Description: A consecutive value is automatically allocated when linking a source signal. The same value is allocated to the sink signal as to the respective source signal. This ID is uniquely identifies the signal connection Engineering procedure and suggestions The procedure for configuring the CAP581 database for the IEC103 lines and star-coupler are given below: 1. Configuring IEC103 serial lines: The Serial Line Port No. has to be configured in CAP581 for each IEC103 line (e.g. 1, 2, and 3). Fig Configuring IEC103 serial lines 2. Several IEC103 applications or serial lines are needed where there are a considerable number of IEC103 devices to be connected. NO TICE: Up to 10 devices can be connected to each IEC103 line. 3. The following table illustrates the connection of an IEC103 application and serial line (e.g. backplane Line 2a). A back- the star-coupler plane line is needed to configure (SCM02). 8-80

181 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Configuring the CAP581 serial line at Port No. CPU03 backplane line or optical output used 1 Serial backplane Line 2a 2 Serial backplane Line 2b 3 Serial backplane Line 3a 4 Serial backplane Line 3b 5 Serial backplane Line 4a 6 Serial backplane Line 4b 7 Serial backplane Line 5a 8 Serial backplane Line 5b 11 1st optical output directly at the CPU 12 2nd optical output directly at the CPU Table 8.16 Configuring IEC103 lines 4. Possible combinations of the various IEC103 lines: The following IEC103 lines can be configured together: Interface Available ports Example 1 1 or or or 7 or or 8 or Rules for allocating serial lines The first IEC103 board should always use serial lines 1, 2, 3 and 4 (backp lane Lines 2a, 2b, 3a and 3b) for connecting to protection devices. The second IEC103 board should always use serial lines 5, 7, 8 and 9 (backplane Lines 4a, 4b, 5a and 5b) for connecting to protection devices. The third IEC103 board can then only use the optical outputs directly at CPU03 for connecting the protection devices. 5. Converting from IEC103 Double Indication: IEC103 only specifies the data type Double Indication. Some projects, however, require the transmission of the data type Single Indication. From IEC103 to LON, double indication is converted to single indication when the data point is config- 8-81

182 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C ured as a single indication in the CAP581 database. All other NCC protocols do not support this conversion. Data points that are already configured as double indications are transmitted as such by LON. The PSF function has to be used for all other protocols. 6. Converting signals with relative time (e.g. Siemens protection devices): Various third-party devices (e.g. Siemens) send telegrams with relative time. These have to be converted for all NCC protocols using a PSF function (convert Type 162 to Type 140). This does not apply, however, to the LON protocol. 7. IEC103 measured values with relative time (IEC103 Data Type 4) have to be configured as Sequence of Event in CAP Configuring IEC103 events that are not transmitted in response to general polling (fleeting signals): There are some signals in the standards that are not transmitted in response to a general polling request. Where these are configured as single or double indications, they are tagged by COM581 as invalid during general polling, be- the data cause the bay unit does not transmit point. NO TICE: All IEC103 events that are not transmitted in response to a general po lling request (see Recommendation IEC103) have to be configured in COM581 as SOE. 9. Device supervision / configuring device status (SON): To supervise IEC103 devices, a special SON (Status of Node) signal has to be configured in the CAP581 database. All the protection devices are dealt with in the same way. Status of Node (SON) configuration PEA CAA Same as the other signals of the protection device Same as the other signals of the protection device FUN 128 INF

183 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd 8.4. IEC101 Nu merous remote control and station automation system manufacturers supported the remote control protocol according to [IEC ] (equivalent to the German and European Standard [DIN EN ]), although the degree of con- formity varies IEC101 slave application Fig Unlinked Slave Application ID object Insert new object No Delete object Yes Remove link No Properties Fig Specific tab in the IEC101 Slave Application properties dialogue 8-83

184 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Application ID Range: Default: Allocated while adding object Description: Identification number which uniquely identifies the application within COM581. It is incremented each time by one and can then be reset. Link Address Range: Default: Description: Common Addre Range: Default: Description: Defines the IEC101 link address of the IEC101 Slave Application and the higher level serial line. If Size of Link is set to 1, the value 255 is reserved for broadcast, i.e. telegram to all stations. The same applies to the value 65535, if Size of Link Address is set to 2. ss of ASDU (CAA) Defines the IEC101 station address of the IEC101 Slave Application and the higher level serial line. If Size of Common Address of ASDU is set to 1, the value 255 is reserved for broadcast, i.e. telegram to all stations. The same applies to the value 65535, if Size of Common Address of ASDU is set to 2. NOTICE: The attri butes Link Address and Common Address of ASDU (CAA) include the address of the IEC101 slave application. Only one logical address (Common Address of ASDU (CAA)) can be allocated per device (Link Address). Size of Common Address of ASDU (bytes) Range: 1 or 2 Default: 2 Description: Determines the length of the Common Address of ASDU field in Bytes. Size of Link Address (bytes) Range: 0 2 Default: 1 Description: Determines the length of the Link Address field in Bytes. The only values permitted are 1 and

185 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Size of Info Object Address (bytes) Range: 1 3 Default: 3 Description: Determines the length of the Object Address field Bytes. Size of Cause of Transmission (bytes) Range: 1 or 2 Default: 2 Description: Determines the length of the Cause of Transmission field in Bytes. The value has to be set to 2 to transfer the optional field Originator Address as well. Originator Address is of consequence when transferring commands; a command telegram has to in- Originator Address in the command direc- clude the tion, which is then also included in the response in the reporting direction. Number of Telegram Retries Range: 0 10 Default: 3 Description: Determines the number of times a telegram is repeated should communication fail in balanced op- eration. In such cases, RTU can transmit telegrams spontaneously in the SEND/CONFIRM mode, i.e. RTU expects a confirmation of receipt for every telegram it sends. If either a receipt is not received or a faulty telegram is received, RTU repeats the telegram that was sent last up to the maximum number of retries (Number of Telegram Retries). The period between repeats is described below under Timeout Interval for Repetition. Meaning of Signal Control Character Range: Short Telegram Is Used; Single Character Is Used Default: Single Character Is Used Description: Determines which type of confirmation of receipt telegram is used by RTU. Single Character Is Used: Corresponds to the character E5. If the RTU also transfers control data, e.g. DFC (flow control) or ACD (Class 1 data ready) is set, a Short Telegram is sent. Short Telegram Is Used: This corresponds to a Short Telegram with a length of 5 Bytes if Size of Link Address is set to 1, otherwise 6 Bytes. in 8-85

186 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Min Idle Bits between Telegrams Range: Default: 33 Description: Determines in accordance with the number of Idle Bits the waiting time before the next telegram is sent in the event of a communication failure. Min Idle Bits after Send No Reply Range: Default: 0 Description: Determines in accordance with the number of Idle Bits the waiting time after sending a telegram by means of SEND/CONFIRM before the next telegram is sent. Max No. of High Priority Telegrams Range: Default: 5 Description: Determines the maximum quantity of sequential high priority data that can be packed in a tele- Data with higher priority are sent before data gram. of lower priority. Max No. of Medium Priority Telegrams Range: Default: 3 Description: Determines the maximum quantity of sequential medium priority data that can be packed in a tele- Data with higher priority are sent before data gram. of lower priority. Max No. of Low Priority Telegrams Range: Default: 1 Description: Determines the maximum quantity of sequential low priority data that can be packed in a telegram. Data with higher priority are sent before data of lower priority. Max Frame Length (bytes) Range: Default: 255 Description: Maximum number of bytes that can be transmitted in a telegram on the IEC101 communication line. 8-86

187 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Interchange Mode Range: Balanced; unbalanced Default: Unbalanced Description: Determines the transmission mode for communication between master and RTU. Balanced (i.e. X.24/X.27): Every RTU can send telegrams to the master with- being requested to do so. However, this is only out permissible in point-to-point and multiple point-tomode is applied in systems where point schemes. Unbalanced (i.e. V.24/V.28): This transmission the master initiates data transfer by sequentially polling the RTU s. The master always initiates data transfer and the RTU s only send data when requested to do so. Counter Time Ta Range: Default: Description: If this parameter is set to True, the time tags at- tached to the counter values are suppressed. NCC No. Range: 0 4 Default: 1 Description: Auxiliary attribute which is not relevant for setting the COM581. It is used as a position parameter when importing and exporting data. A setting of 0 determines that signals are not exported to the signal list. Send GI with Ti Range: Default: Description: gs are Suppressed True; false False me Tag True; false True Determines whether general polling takes place with time tags or not. If yes, the time tag corresponds to the time of the local COM

188 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Properties Fig Time tab in the IEC101 Slave Application properties dialogue Timeout Interval for Repetition (ms) Range: Default: 1000 Description: Determines the time in milliseconds between tele- gram transmission repeats in the event of a communications failure in the balance transmission mo- Retries de. The maximum number of repeats is defined under Number of Telegram above. Baud Rate Generator Range: True; false Default: True Description: Determines whether the trigger impulse from the in- serial interface driver or the one from the modem. The trigger impulse from the modem is used if this ternal CPU03 baud rate generator is used for the parameter is set to False. 8-88

189 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd CP56Time2a Format is Used Range: CP56; CP24 Default: CP56 Description: IEC supports neither the time tagging format for the full time (CP56Time2a) from milliseconds up to a year nor the relative time (CP24Time2a) from milliseconds up to minutes. The CP24Time2a format thus includes the time in relation to the hour given in the last time tagged event. Should, however, the time tagged event to be sent not have the same time in hours up to a year as the last telegram, a Clock Synchronization telegram is sent in advance. Status Request Cycle Time (ms) Range: Default: 500 Description: Determines the cycling time in milliseconds for peritest telegram in the balanced odically sending a link mode from COM581 to the NCC using FC 9 Request status of link to test the status of the IEC101 masters. Link Test Cycle Time (s) Range: Default: 30.0 Description: Determines the cycling time in seconds for periodically sending a link test telegram from COM581 to the NCC in the balanced mode using FC 2 Test function for link to test the status of the IEC101 communication line. Test Command Cycle Time (s) Range: Default: 60.0 Description: Determines the cycling time for periodically sending IEC101 Test Command. NO TICE: This data is not evaluated by COM581. Scanning Cycle Time (s) Range: Default: 1.0 Description: Scanning Cycle Time determines the sampling cy- cle for spontaneous measured values that are stabilized using the cumulating threshold value technique. 8-89

190 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Clock Synchronization Cycle Time (s) Range: Default: 60.0 Description: Determines the waiting time allowed for receiving synchronizing telegrams from the NCC. The waiting time is not started for a setting of 0. For time settings higher than 0, the system detects whether a synchronization telegram is received from the NCC within the set time. If not, the local time on the board running the protocol application is set to invais success- lid until a new synchronization telegram fully received. Timeout for Keeping Information (s) Range: Default: 60.0 Description: After a communication failure has been detected, this parameter determines the time in seconds during which all the data ready for transmission are stored in a queue before being reset. Command Range: Supervision Timeout (s) Default: 10.0 Description: Determines the waiting time in seconds for the general polling to finish after communication has been established. Should general polling not be finished within the Command Supervision Timeout, i.e. the RTU data received were incomplete, a new general polling request is sent. This attribute is only of consequence when IEC101 Application has been configured as master. Indication Time Tags are Suppressed Range: True; false Default: True Description: Determines whether time tagged signal events that are received via Channel 2 are forwarded with or without time tag. They are forwarded without time tag for a setting of True, respectively with time tag for a setting of False. This parameter is of consequence when time tagged events are transferred via Channel 2 and Channel

191 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Step Position Time Tags are Suppressed Range: True; false Default: True Description: This is basically the same as for Indication Time Tags are Suppressed, but for the data type Step Position. Summer Time Offset [h] Range: Default: 1 Description: Defines summer time (daylight saving) in hours. The Summer Time Offset is only added to time tagged events when the bay units send them with the summer time flag set. Link Startup De Range: Default: Description: lay [s] Determines the delay for establishing communication with the NCC in the Balanced in Seconds communication mode. Thus when starting the system, the process image is updated by the bay units before the NCC can initiate general polling. This prevents the NCC from temporarily tagging the data it receives as invalid when COM581 is restarted IEC101 data point Fig Unlinked IEC101 Sink Indication object and the object linked in the signal tree The various signals are added according to data type below the predefined structuring objects, which are arranged as shown in the figure below. 8-91

192 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Fig Arrangement of the structuring objects in the case of IEC101 data points Insert new object Sink Datapoints Integrated Totals IEC101 Sink Integrated Totals Structuring node Indication IEC101 Sink Indication Structuring node Measurand Value IEC101 Sink Measurand Value Structuring node Step Position Information IEC101 Sink Step Position Information Structuring node Command IEC101 Sink Command Structuring node Sequence of Events IEC101 Sink Sequence of Event Structuring node System Diagnosis System Control IEC101 Sink Indication IEC101 Sink Sequence of Event Structuring node Transparent Data IEC101 Sink File IEC101 Sink Transparent Data Structuring node 8-92

193 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Maintenance Information IEC101 Sink Maintenance Information IEC101 Sink Indication IEC101 Sink Sequence of Event Structuring node Bitstring IEC101 Sink Bitstring 32 Structuring node Source Datapoi Command nt IEC101 Source Command Structuring node Transparent Data IEC101 Source File IEC101 Source Transparent Data Structuring node Bitstring IEC101 Source Bitstring 32 Structuring node Delete object Yes, all signals that are added can be deleted again. Remove link Th is operation is possible in the signal tree. General data type and internal address attributes: Data Type Range: IEC101 Indication IEC101 Sequence of Event IEC101 Step Position Information IEC101 Bitstring32 IEC101 Measurand Value IEC101 File IEC101 Integrated Totals IEC101 Command IEC101 Transparent Data Default: Determined at time of selection. Description: Defines the data type for the signal, which cannot subsequently be changed for an existing object. Internal Address (read only) Range: Default: Inadmissible value Description: A consecutive value is automatically allocated when linking a source signal. The same value is allocated to the sink signal as to the respective source signal. This ID is uniquely identifies the signal connection. 8-93

194 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C IEC101 counter Fig IEC101 counter Properties Fig Specific tab in the IEC101 Sink Integrated Totals properties dialogue Intermediate Reading Time (min) Range: Default: 0 Description: Determines the Intermediate Reading Time (IR) in minutes and is only of consequence when the Counter Transmission Mode attribute is set to EOP and Intermediate. End of Period Time (min.) Range: Default: 0 Description: Determines the End Of Period (EOP) in minutes and is only of consequence when the Counter Transmission Mode attribute is set to EOP. Counter Reset Type Range: Wrap around; Set zero EOP; Set zero after freeze Default: Wrap around Description: Determines according to which criterion the counter is reset. Wrap around: An overflow resets the counter. Set Zero EOP: End Of Period resets the counter. Set Zero after Freeze: The counter freeze command is followed by a counter reset. 8-94

195 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Counter Transmission Mode Range: None; EOP; EOP and Intermediate Default: None Description: Determines the counter transfer mode. None: The transfer of the count is not controlled periodically. EOP: The count is transferred cyclically at End of Period Time. EOP and Intermediate: The count is transferred cy- at End of Period Time and also in response clically to an intermediate reques t (IR) IEC101 indicati on Fig Unlinked Sink Indicat ion object Properties Fig Specific tab in the IEC101 Sink Indication properties dialogue Suppress Intermediate State Range: True; false Default: False Description: This only applies to double indication signals with or without time tag and determines whether an intermediate state (i.e. 00 or 11) is suppressed or not. An intermediate state occurs when a change of position of a double indication takes place during a change of status. 8-95

196 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Indication Type Range: Single; double Default: Single Description: The status of a single indication is described by a bit corresponding to the positions ON or OFF. The status of a double indication is described by two bits corresponding to the positions ON or OFF and two intermediate positions. Sequential Event Recording Range: None; Zero to One; One To Zero; Both Default: Both Description: Determines which kind of change of state, i.e. posi- edge, initiates transmission of tive or negative-going an event. NOTICE: IEC101 data points, which are configured as Sequence_of_Events, are not stored in the process database. All other process information is available for detection by general polling. Properties Fig Address tab in the IEC101 Sink Indication properties dialogue 8-96

197 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd ASDU and Object Address Range: [ ].[ ] Default: Allocated while adding object (starting at 0.0). Description: Defines the address of a type IEC101 signal on the basis of the IEC101 device address (ASDU adto another. The pair of addresses of every two- dress) and object address. The IEC101 address can either be physical or logical. The ranges of values of the various Bytes can differ from one project stage device and object must be unique for each data type and for each a system. Example: Common Address of ASDU using a two-byte long address field and structured addressing: ASDU address = 2 8 * Region * Station The Common Address of ASDU is therefore a combination of two addresses for region and station. Information Object Address, using a three-byte long address field for ASDU Common Address and structured addressing: Object address = 2 16 * rated voltage * bay number + information object number The Information Object Address is therefore a combination of three addresses for rated voltage, bay number and information object number. Properties Fig Group Configuration tab in the IEC101 Sink Indication properties dialogue 8-97

198 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Group Configuration No. Range: Default: 0 Description: This parameter enables a signal to be assigned to a group configuration, which defines one or several groups. This is used for selective polling, e.g. for polling measured values or general polling in cases where single groups have to be individually polled IEC101 measurand Fig Unlinked Sink Measurand Value object Properties Fig Specific tab in the IEC101 Sink Measurand Value properties dialogue Deadband Threshold (%) Range: 0 20 Default: 0 Description: This is a relative threshold input when integration is not being used. A fixed absolute threshold is entered as a percentage of the measured variable. If the current measurement differs from the last value transmitted by more than the amount of the threshold setting, the current value of the measured variable is transferred and then serves as reference value for determining a new difference. The fluctuations of the measured variable are thus smoothed and fewer signals have to be transferred. 8-98

199 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd NOTICE: If Deadband Threshold > 0 then Accumulating Value = 0. Deadband threshold: When using the threshold method, enter the threshold as a percentage > 0. The current value of the measured variable is transferred if the threshold is exceeded. NOTICE: In order to use the threshold method, Accumulation Value must = 0. Accumulating Value (%) Range: Default: 5 Description: Percentage of the cumulated sum. The variation of the measured variable is determined in relation to the cycling time and the last value transmitted and the difference added or subtracted in accordance with its sign. If the sum exceeds the set limit, the current value of the meas- ured variable is transferred and the summation procedure starts again. Measured variable stabilization: This attribute is used for stabilizing measured variables according to the integration principle. Measurand Type Range: Scaled; normalized; floating point Default: Scaled Description: Defines the type of measured variable. Scaled: Integer in the range Normalized: Floating value in the range Floating Point: for < fraction, exponent, sign > Background Cycle Time (s) Range: Default: 0.0 Description: Facilitates defining a refresh cycle for spontaneous measured variables. Even if the set threshold setting is not exceeded, measured variables have to be transferred at the end of the Background Cycle Time. The function is disabled at the default setting of zero. 8-99

200 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Fast Cycle Time (s) Range: Default: 1.0 Description: The measured variable transfer cycle can be controlled by a command of the type Switch Cycle Time for Measurands. This parameter determines the cycling time for transferring measured variables should the transfer cycle was switched on using the command given above. Default Cycle Time (s) Range: Default: 1.0 Description: Period during which summation takes place, e.g. 1 s after detecting the deviation of the measured variable and calculation by COM581. Cycle Time: If Default/Fast Cycle Time is not zero, the unstabilised measured variable is transferred cyclically to the station. NOTICE: If Accumulating Value and Deadband Threshold = 0 and Default Cycle Time > 0, the measured variables are trans- ferred in any event. IEC101 Scaling Factor Range: Default: Description: The measured variable is multiplied by the scaling factor before it is transferred to the remote control station. To achieve the best possible accuracy, only relative values are transmitted (i.e. the measured variable is normalized). The scaling factor chosen can vary according to the protocol in use, the type of measured variable and any special user preferences. Example: The protocols to be used are MVB and IEC101. The bay unit can transfer a maximum value of 1200 = 120% to the MVB. Thus the entire range (±32000 or 320%) of the MVB is not used. To utilize the full range, COM581 multiplies the measured variable by 320%/120%. Scaling factor: 320% / 120% =

201 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd NOTICE: Phase-to-phase voltages transferred by the bay unit 1 generally have to be multiplied by the factor. 3 Dead band Cumulating Type Back- Fast Default Scaling Offset Remarks on transfer threshold value [%] ground cycle cycle factor [%] scan time time 0 5 scaled Default setting 0 20 scaled Transferred at the latest after 30 s 0 20 scaled Double the value 0 20 scaled % offset 0 20 normal Default with normalized data 0 20 normal Transferred at the latest after 30 s 0 20 normal % offset 0 0 scaled Spontaneous unstabilized transfer Table 8.17 IEC101 measured variable settings Offset (%) Range: Default: 0.0 Description: Measured variable offset in percent with the correct sign NOTICE: The entries for Address and Group Configuration on the Specific tab of the IEC101 Sink Measurand Value properties dialogue are the same as for IEC101 Sink Indication

202 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C IEC101 command Fig Unlinked Sink Command object Properties Fig Specific tab in the IEC101 Sink Command properties dialogue Generate ACTTERM Range: True; false Default: False Description: Determines whether (activation termination) telegram is sent to the NCC after receiving the respective configured confirmation. CA of Associated Indication Range: Default: 0 Description: IEC101 station address of a signal associated with a command (see Generate ACTTERM above) IOA of Associated Indication Range: Default: 0 Description: IEC101 object address of a signal associated with a command (see Generate ACTTERM above) NOTICE: If CA / IOA of Associated Indication is set to default (i.e. to 0), the IEC101 application does not have to generate a confirmation signal in response to a command

203 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Command Type Range: Normalized Set point Scaled Set Point Bay Interrogation Switch Cycle Time For Measurands Transmit Measurands Defined by Group Bay Suppression Line Suppression GI Request Other Synchrocheck Switching Default: Other Description: Command Type is a data type supplement, which has to be modified when the command is not a normal switching operation (Type Other) (e.g. Bay Interrogation, Switch Cycle Time For Measurands). NOTICE: Special commands such as remote control blocking, bay and line suppression are dealt with in the following Sections Remote control blocking Either remote control lines or the remote control of a bay can be disabled. The process information affected by disabling remote control continues to be entered in the process image, but is not transferred to the power system control centre. The fact that remote control has been disabled is stored in a volatile memory. The information is therefore lost should the system be restarted (e.g. following an interruption of the power supply) and the disable setting has to be restored. Remote control can be disabled or enabled either locally or remotely. When remote control is enabled again, a general polling request is automatically generated Bay Lock function (bay suppression) Disabling the remote control of a bay: A disabled bay acknowledges control commands negatively. This also applies to general polling requests, because they are of the single command type. The response to general polling requests to the voltage levels and lines is normal. Data from disabled bays are transferred with the attribute BL=

204 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Operating principle of the Bay Lock function 1. A single command (Type 45, COT 6, Execute, with the value 1 to disable the bay or 0 to enable the bay) is transmitted from power system control 1 (NCC1) via the RP571 application to the IEC101 application. 2. NCC1 receives acknowledgement of the command (COT 7) from the IEC101 application. 3. The IEC101 application concerned transmits an SPI (Type 2 or 30) to the associated NCC2 with the value 1 to signal that the bay is disabled, respectively 0 to signify that it is enabled. 4. NCC1 receives a finish of command signal (COT 10) from the IEC101 application. 5. The IEC101 concerned transmits all the data points belonging to the bay to NCC2 tagged with the quality attribute BL=1. The Bay_Lock function is used, for example, to disable a bay with the aid of a command on one remote control line or a local control command on another. Providing the command is suc- line, the cessfully transmitted via the second remote control COM581 will not transmit the bay data on the line in question, but will continue to enter it in the process image. The signals are tagged with the quality attribute Blocked (disabled, BL=1)

205 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd RP571 NCC1 Line 1 IEC-101 NCC2 Line Baud 64 kbaud 571s 101s COM581 LSK LAC VME IBB: LON RER111 LAC REC580 LAC REF542(1) LAC REF542(10) Time synch. DCF77 Radio clock BIO BIO BIO Fig Example of a configuration illustrating the Bay Lock function Configuration: Creating an Address mask of the type Bay with the values: Common Address Mask = 30 Information Object Address Mask = 0 Fig Creating the Bay Lock command in RP

206 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Fig Creating the Bay Lock command in IEC101 Fig Specific tab in the IEC101 Sink Command properties dialogue 8-106

207 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Fig Address tab in the IEC101 Sink Command properties dialogue Fig Specific tab in the Address Mask properties dialogue 8-107

208 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Fig Linking signals in the signal tree view Line Lock function Disabling the remote control of a line: When disabling a remote control line, the application layer (Layer 7) is separated from the connection layer (Layer 2). The line continues to respond to connection layer services (e.g. status query) and confirmed user data (FC 3) are acknowledged negatively (FC 1). A maintenance message is generated whenever remote control is disabled or enabled. Operating principle of the Line Lock function 1. A single command (Type 45, COT 6, Execute, with the value 1 to disable the line or 0 to enable the line) is transmitted from power system control 1 (NCC1) via the RP571 applica- tion to the IEC101 application. 2. NCC1 receives acknowledgement of the command (COT 7) from the IEC101 application. 3. The IEC101 application concerned transmits the remaining data points in the queue buffer and then an SPI (Type 2 or 30) to the associated NCC2 with the value 1 to signal that the line is disabled, respectively 0 to signify that it is enabled. 4. NCC1 receives a finish of command signal (COT 10) from the IEC101 application. 5. From this instant, communication between the IEC101 application and NCC2 only functions at the link level until the remote control line is enabled again by a command, which can only come from NCC1. The Line L ock function is used to disable a remote control line by a command from another remote control line. Providing the command is successfully, the disabled remote control line only continues to communicate on the link layer

209 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd RP571 NCC1 Line 1 IEC-101 NCC2 Line Baud 64k Baud 571s 101s COM581 LSK LAC VME IBB: LON RER111 LAC REC580 LAC REF542(1) LAC REF542(10) Time synch. DCF77 Radio clock BIO BIO BIO Fig Example of a configuration illustrating the Line Lock function Configuration: Fig Creating the Line Lock command in RP571 Fig Creating the Line Lock command in IEC

210 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Fig Specific tab in the IEC101 Sink Command properties dialogue Fig Address tab in the IEC101 Sink Command properties dialogue Fig Linking Line Lock signals in the signal tree view 8-110

211 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Bay Interrogation function General polling of a bay: COM581 responds to a general polling request received by a bay. Once the command has been acknowledged positively (TK 45), all the data that have been configured for the respective line are transferred together with the cause of transmission attribute interrogated (COT=5). Generating an ACTTERM terminates this. The polled data include: all the data objects that have been set for the bay addressed by a single command. The relevant elements are the voltage level and bay number of the data model. Configuration: Fig Creating a bay polling command (bay interrogation) 8-111

212 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Fig Specific tab in the IEC101 Source Datapoint Command properties dialogue Fig Address tab in the IEC101 Source Datapoint Command properties dialogue 8-112

213 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Fig Creating an address mask (form) using Address Mask Type set to Bay and Common Address Mask set to 30 NOTICE: The Bay interrogation command must be linked to a LON drain command to enable the COM581 to respond to it. However, the command must not have a LON target. Fig Linking bay polling signals in the signal tree view General polling of voltage levels and lines The COM581 also responds to a general polling request for voltage levels and lines. Once the command has been acknowl- positively (TK 100), all the data that have been edged configured 8-113

214 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C for the respective line are transferred together with the cause of transmission attribute general polling request (COT=20). Gen- an ACTTERM terminates this. erating The polled data include: General polling of a voltage level (ASDU address = ): All the data objects that are set and have the same ASDU address genera l polling of a line (ASDU-Address = = FFFFh): All the data objects configured for the respective line NOTICE: This function does not need to be configured General Interrogation Request function The local control station (e.g. RP571) can issue a command to the COM581 to generate a message, which initiates general poll- ing by the remote control station (e.g. IEC101). RP571 Emulator Line 1 IEC-101 Emulator Line Baud 64 kbaud 571 s 101 s COM581 LSK LAC VME IBB: LON RER111 LAC REC580 LAC REF542(1) LAC REF542(10) Time synch. DCF77 Radio clock BIO BIO BIO Fig Example of the configuration for the general polling request function 8-114

215 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Fig Creating an RP571 general polling request Fig Creating an IEC101general polling request Fig Message and command type settings for a general polling re- the IEC101 Sink Command proper- quest on the Specific tab of ties dialogue 8-115

216 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Fig Address settings for a general polling request on the Address tab of the IEC101 Sink Command properties dialogue Fig Linking general polling request signals in the signal tree view Switch Cycle Time for Measurands function The single command to switch over the cycling time for polling measured variables is processed by both the COM581 and the corresponding bay unit. At the time of transmission, the cyclic data is read from the process image maintained in the COM581 and packed for transmission, while in the background the proc- the bay unit. The refreshing ess image is refreshed cyclically by and reading functions are completely independent to exclude any influence from transmission delays on the IBB. Up to two bays can be simultaneously selected per remote control line with short cycling times. Any attempt to select a third bay results in a negative acknowledgement. Every measured variable can be configured for either spontane- the aid of the cycling time switching ous transmission with optimum stabilization or cyclic transmission. In the case of cyclic transmission, a short and a long cycling time can be configured and the system can switch between the two with function

217 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Configuration: The measured variable data for the IEC101 protocol have to be configured in the bay units and the COM581 and an address mask (form) has to be created using type Bay and CA.IOA=30. Fig Creating a new command for switching the cycling time Fig Specific tab in the IEC101 Source Datapoint Command properties dialogue Fig Address tab in the IEC101 Source Datapoint Command properties dialogue 8-117

218 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Fig Creating a new LON command for switching cycling time function Fig Linking commands for the cycling time switching function 8-118

219 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Fig Specific tab in the Address Mask dialogue for creating a new ad- dress mask with type setting Bay and CA.IOA=30 Fig Specific tab in the IEC101 Sink Measurand Value dialogue 8-119

220 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Transmit Measurands defined by Group function Inhibiting the transmission of measured variables The group reporting command provides facility for enablin g and disabling the transmission of groups of measured variables. Every measured variable can be configured for either spontaneous transmission with optimum stabilization or cyclic transmission. In the case of cyclic transmission, a short and a long cy- time can be configured and the system can switch between cling the two with the aid of the cycling time switching function. NOTICE: Setting the Fast or Default cycle time attribute to zero when this cycling time is selected inhibits transmission of a measured variable regardless of whether long or short (see Table 8.32). Configuration: (see Section Switch Cycle Time for Measurands function) The only difference in the configuration compared to the previous section is that Measured Variables Defined By Group replaces the command type Switch Cycling Time For Measured Variables. In this case, command and measured variables are assigned to groups, which then have to be configured in the IEC101 application. Fig Specific tab in the IEC101 Source Datapoint Command properties dialogue and the setting Measurands defined by Group 8-120

221 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Fig Group Configuration tab in the IEC101 Source Datapoint Command properties dialogue and the setting for switching the cycling time Fig Creating a new group with the number 1 Fig Group Configuration tab in the IEC101 Sink Measurand Value properties dialogue 8-121

222 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Fig Specific tab in the IEC101 Sink Measurand Value properties dialogue and settings for measured variables to be disabled IEC101 maintenance information Configuring maintenance information This section describes the creation and configuration of the maintenance messages supported by COM581. Up to a maximum of ten maintenance messages can be created, but only for the remote control protocols IEC101 and IEC104. The following example refers to the protocol IEC

223 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Fig Adding a new Maintenance Information object Fig Creating a maintenance message The type of maintenance message has to be selected in the following dialogue

224 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Properties Fig Specific tab in the IEC101 Sink Maintenance Information dialogue Locally Generated Information Range: Plausibility Error Interrogation request End of Initialization Unknown Address Unknown Type ID Unknown Cause of Transmission Unknown Value for Info Element Configuration_Error Internal Exception was Raised Queue Overflow Default: Plausibility Error Description: A special group of IEC101 Maintenance Information is generated locally by the IEC101 application and sent to the NCC for supervision and diagnosis purposes. Their configuration depends on the particular project. And their addresses must be unique in the IEC101 address range for messages. Table IEC101_Maintenance_Information includes the two-part address of all the messages used for diagnosis purposes and generated directly by the IEC581 application. They must not be used for other IEC581 data points

225 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Maintenance messages Plausibility error Interrogation request End of Initialization Unknown Address Unknown Type ID Unknown Cause of Transmission Unknown Value for Info Element Configuration Error Internal Exception was Raised Remarks This message is generated for an error that is detected in one of the fields of the application data received. Request for polling of data Initialization procedure has finished The address of an IEC101 data point was not configured. The type of an ASDU telegram is unknown, invalid or not implemented in the IEC101 application. Cause of transmission (COT) unknown. A COT has been received which is invalid for the type of ASDU telegram. Invalid value in the ASDU range of messages. Error in the CAP581 database configuration. General error indicating internal software problems in the IEC101 application. Queue Overflow Table 8.18 Maintenance messages An overflow of the data queue has occurred. Properties Fig Address tab in the IEC101 Sink Maintenance Information dialogue 8-125

226 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C ASDU and Object Address Range: [ ].[ ] Default: 0 Description: Defines the station address of IEC101 Slave Appli- address of the Maintenance cation and the object Information data point. The station address range depends on the parameter IEC101_Size_of_ Common_Address_of_ASDU. The object address range depends on the parameter IEC101_Size _of_info_object_address. NOTICE: A maintenance information address must not be used for an IEC101 indication data point. Fig Maintenance mess directory ages created in the Maintenance Information Destination device configuration Fig Linked Destination Device Configuration object Insert new object Destination Device Configuration Delete object Yes, a Destination Device Configuration object can Remove link No be deleted

227 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Properties Fig Address tab in the Destination Device Configuration dialogue Common Address of ASDU (CAA) Range: Default: Allocated while adding object. Description: Defines the IEC101 station address to which the data link target address has to be linked. Link Address Range: Default: Description: Allocated while adding object. Defines the data link target address to be linked to Common Address of ASDU Masking addresses Fig Linked Address Mask object Address masking is necessary for the following IEC101 functions: General polling of the bays Switching the cycling time for measured variables Disabling remote control: Bay Lock function Various functions (e.g. station or bay polling) of an IEC101 application can be linked to the physical interpretation of an IEC101 address

228 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C It is only necessary to mask addresses if functions are used in a project that require the data points to be grouped in relation to the addresses. Insert new object Address Mask Delete object Yes, an Address Mask object can be deleted. Remove link No Properties Fig Specific tab in the Address Mask dialogue Common Addre Range: Default: Description: ss Mask Defines the IEC101 Common Address Mask. Information Object Address Mask Range: Default: 0 Description: Defines the IEC101 Information Object Address Mask. NOTICE: The address masks given above have either a physical or a logical significance. In the case of a structured address, the user can determine the significance of the individual Bytes

229 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Address Mask Type Range: Station; Region; Bay; Voltage; not used Default: Station Description: Specifies which IEC101 functions have to be configured Address masking example Three high bytes in Common_Address_of_ASDU define the station address: Common Address Mask = (corresponding to FFF0 Hex) Information Object Address Mask = 0 Common address Resulting bay numbers Resulting bay numbers Basis dec bin dec dec REC REC R EC REF REF REF REF REF REF R EF REF REF REF REC Bay Filter: For bay filter = 30 B ay Filter: For bay filter = 32 Table 8.19 Address Mask filter settings 8-129

230 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Creating a type Bay address mask with the values: Common Address Mask = 32 Information Object Address Mask = 0 Masking means that a bay will have the following common addresses: All REF542 s and REC580 s (CA= 63) belong to the same bay. Th e column Resulting bay number follows from the Bit pattern for the particular range determined by the bay filter Group configuration Group Configuration enables any number of IEC101 groups to be combined to form a typical configuration. It is only necessary to fill in the table when the project requires IEC101 group polling. Group configurations are used for transferring the values of measured variables in groups. Fig Group objects linked under Group Configurations Insert new object IEC101 Group Configuration Delete object Yes, IEC101 Group Configuration together with its substructures can be deleted. Remove link No 8-130

231 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Properties Fig Specific tab in the IEC101 Group Configuration properties dialogue Group Configuration No. Range: Default: Allocated while adding object. Description: Defines a typical configuration, which can be selectively polled by the NCC. The response to NCC group polling includes data points configured with the same group numbers and listed in an IEC101 Group Configuration. NOTICE: Group Configurations for data points of the IEC101 Indication type can include a maximum of 12 IEC101 Group Configuration elements

232 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C IEC101 group Fig Unlinked IEC101 Group object Insert new object IEC101 Group Delete object Yes, an IEC101 Group object can be deleted. Remove link No Properties Fig Group Number tab in the IEC101 Group properties dialogue Group Number Range: Default: Description: Allocated while adding object. Defines the IEC101 data point group number to be configured for IEC101 Group Configuration. NO TICE: An IEC101 Group Configuration No. element for data po ints of the IEC101 Indication type can include a maximum of 5 IEC101 Groups

233 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd 8.5. RP570 / RP571 A COM581 uses a data transfer protocol to communicate with a central control system. This protocol is based on the interna- tional standard IEC The RP570/571 protocol fulfils the requirements of Format Class FT 1.2 in IEC RP570/571 uses frames with windows and a variable number of us er data as described in IEC , Section 6,2,4,2 ( issue). The most significant difference between the RP570 and RP571 protocols is the addition of a second RTU address for the router. With the exception of the additional part of the address, the configuration for RP5 70 and RP571 slaves is identical. The attribute Router_RTU_No has to be defined and assigned to all data points as an extension to the RP571 addresses RP57x slave application Fig RP570 and RP571 Slave Application objects Insert new object No Delete object Yes Remove link No 8-133

234 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Properties Fig Specific tab in the RP570/RP571 Slave Application properties dialogues Application ID Range: Default: Description: Allocated while adding object. Identification number which uniquely identifies the application within COM581. It is incremented each time by one and can then be reset. Router RTU Number (nur RP57) Range: Default: 1 Description: Defines the Router RTU address. In a hierarchically structured communication model, RTU 1 to 255 control the process RTU s. RP571 Midposition Suppression Time (s) Range: 1 25 Default: 20 Description: Not implemented Command Time out (factor 0.1 s) Range: Default: 0 Description: Not implemented 8-134

235 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Communication Time out to NCC (s) Range: Default: 0 Description: Determines the supervision time in seconds for the communication link between COM581 and the NCC. If COM581 does not receive an NCC request within this period, RP57x application generates a minor error External_Line_1_Not_Available and a new supervision period starts. Priority of ERMI Range: 1 3 Default: 2 Description: Determines the priority for transmitting ERMI (time tagged signals) to the NCC. Priority of ERMA Range: 1 3 Default: 2 Description: Determines the priority for transmitting ERMA (time tagged measured variables) to the NCC. Priority of Counter Range: 1 3 Default: 3 Description: Determines the priority for transmitting the values of counters to the NCC. NOTICE: The priority for transmitting data to the NCC also depends on data type and not just on the priority of the data points. Data types have fixed priorities as follows (from high to low): Confirmation telegram Terminal status Indication values Analogue values Digital values Pulse counter messages Terminal events Transparent data responses Event recording messages for indica- Event recording messages for ana- R_ACK R_TSTA R_IND R_AVM R_DVM R_PCV R_TEV R_TDR R_ERMI tions R_ERMA logue signals 8-135

236 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C NCC No. Range: 0 4 Default: 1 Description: Auxiliary attribute which is not relevant for setting the COM581. It is used as a position parameter when importing and exporting data. A setting of 0 determines that signals are not exported to the signal list RP57x data point Fig Unlinked RP57x Sink Indication object Fig Linked RP57x Sink Indication object in the signal tree Fig Structuring RP57x data point objects 8-136

237 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Insert new object Sink Datapoints Integrated Totals RP57x Sink Counter Structuring node Indication RP57x Sink Indication Structuring node Measurand Value RP57x Sink Measurand Structuring Node Step Position Information RP57x Sink Measurand Structuring node Sequence of Event RP57x Sink Indication RP57x Sink Measurand Structuring node System Diagnosis RP57x Sink Indication Structuring node System Control RP57x Sink Indication Structuring node Transparent Data RP57x Sink Transparent Data Structuring node Maintenance Information RP57x Sink Indication Structuring node Source Datapoint Command RP57x Source Command Structuring node Transparent Data RP57x Source Transparent Data Structuring node Delete object Yes, all signals that have been added can be deleted. Remove link This operation is possible in the Signal Tree view

238 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Properties Fig Address tab in the RP57x Sink Indication properties dialogue RTU, BlockNo, Bit No. Range: [1 254].[1 255].[0 15] Default: Allocated while adding object (per data type starting at 1.1.0). Description: Defines the three-part data point address. RTU: RTU process number. This is frequently specified by the user. To simplify copying bay configurations, we recommend specifying a number of your own for the highest address level. When handling disturbance records using transparent data. Block No: Second part of the address. Only block numbers up to 254 may be assigned to messages; the range up to 2047 is reserved for commands. A block contains a single message. Bit No: Bit No. applies to messages and commands Bit = 0. NOTICE: Single or double type RP57x indications: In the case of double indications, generally return confirmations from switchgear, observe the RP57x convention, i.e. that it is only permissible to configure even Bits and that they then occupy the adjacent intervening Bit

239 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd NOTICE: The same RP570/1 address can be assigned for different data types. A switchgear object can have different internal addresses (same RP57x address) if there is more than one command source in a COM581. Data Type Range: Default: Description: RP57x Indication RP57x Analogue Measurand (measurand default) RP57x Digital Measurand RP57x Counter RP57x Command (command default) RP57x Regulation RP57x General Output RP57x Setpoint RP57x Terminal Status (not available) RP57x Transparent Data RP57x FCOM The type can be more accurately defined for measure variables and commands; otherwise the type is determined at the time of selection. Defines the data type of the signal, which can only be changed in the case of an existing measured variable or command object. Internal Address (read only) Range: Default: Automatically assigned. Description: Consecutive values are automatically allocated to the sink signals when linking the source signals. The same value is allocated to a sink signal as to the respective source signal. This ID is uniquely identifies the signal connection RP57x counter Fig Unlinked RP57x Sink Counter object 8-139

240 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Properties Fig Specific tab in the RP57x Sink Counter properties dialogue Counter Res Range: Default: Description: et Type Wrap around; Set zero EOP; Set zero after freeze wrap around Determines according to which criterion the counter is reset. Wrap around: An overflow resets the counter. Set Zero EOP: End Of Period resets the counter. Set zero after freeze: The counter freeze command is followed by a counter reset. Counter Transmission Mode Range: None; EOP; EOP and Intermediate Default: None Description: Determines the counter transfer mode. None: The transfer of the count is not controlled pe- cyclically at End of riodically. EOP: The count is transferred Period Time. EOP and Intermediate: The count is transferred cyclically at End of Period Time and also in re- request sponse to an intermediate (IR). End of Period Time (min) Range: Default: 0 Description: Determines the End Of Period (EOP) in minutes and is only of consequence when the Counter Transmission Mode attribute is set to EOP

241 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Intermediate Reading Time (min) Range: Default: 0 Description: Determines the Intermediate Reading Time (IR) in minutes and is only of consequence when the Counter Transmission Mode attribute is set to EOP and Intermediate. Counter Type Range: PCM; PCT Default: PCM Description: PCM Pulse Counter Message: Counter with a resolution in minutes and a range of a day. PCT Pulse Counter Telegram: Counter with a resolution in seconds and a range of a month. NOTICE: The attributes: Counter Reset Type, Counter Transmission Mode, End of Period Time, Intermediate Reading Time are taken into account neither by the software nor the tool at present RP57x indication Fig Unlinked RP57x Sink Indication object Properties Fig Specific tab in the RP57x Sink Indication properties dialogue 8-141

242 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C RP571 Priority Range: Default: Description: Determines the transmission priority, 1 being the highest and 3 the lowest. Sequential Event Recording Range: None; Zero to One; One to Zero; Both Default: Both Description: Determines which kind of change of state, i.e. leading or lagging edge, releases an event for transmission. None: Real time signal not desired. Zero_to_One: Real time signal on a positive going edge. One_to_Zero: Real time signal on a negative going edge. Both: Real time signal on a positive and negative going edge. Mid-position Suppression for SOE Range: True; false Default: False Description: Determines whether the intermediate position is suppressed in the case of real time double indications. NOTICE: The intermediate position is between ON and OFF positions. Mid-position Suppression for IDM Range: True; false Default: False Description: Determines whether the intermediate position is suppressed in the case of double indications without a time tag (indication message) RP57x measurand Fig Unlinked RP57x Sink Analogue Measurand object 8-142

243 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Properties Fig Specific tab in the RP57x Sink Measurand properties dialogue RP571 Priority Range: 1 3 Default: 2 Description: Determines the transmission priority, 1 being the highest and 3 the lowest. Accumulating Value (%) Range: Default: 0 Description: Percentage of the cumulated sum. The variation of the measured variable is determined in relation the cycling time and the last value transmitted and then the difference added or subtracted in accordance with its sign. If the sum exceeds the set limit, the current value of the measured variable is transferred and the summation procedure starts again. Scanning Cycle Time (s) Range: Default: 1.0 Description: Period during which summation takes place, e.g. 1 s after detecting the deviation of the measured variable and calculation by COM581. Limit Supervision Range: None; ERMA; AVS Default: None Description: Determines the limit value supervision mode: None: No supervision of limits required. ERMA: The bay unit has to generate a real time signal when a limit is exceeded

244 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C AVS: Analogue measured variable which has exceeded a limit and general polling is desired. NOTICE: ERMA and AVS have to be provided by the bay because COM581 does not generate a telegram. unit Offset (%) Range: Default: 0.0 Description: Offset of the measured variable in percent and taking the sign into account. Scaling Factor Range: Default: Description: The measured variable is multiplied by the scaling factor before it is transferred to the remote control station. To achieve the best possible accuracy, only relative values are transmitted (i.e. the measured variable is normalized). The scaling factor chosen can vary according to the protocol in use, the type of measured variable and any special user preferences. Example: The protocols to be used are MVB and RP571. The bay unit can transfer a maximum value of = 120% to the MVB. Thus the entire range (±32000 or 320%) of the MVB is not used. In order to utilize the full range, COM581 multiplies the measured variable by 320%/120%. Scaling factor: 320%/120% = NOTICE: Phase-to-phase voltages transferred by the bay unit 1 generally have to be multiplied by the factor

245 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Dead band Threshold (%) Range: 0 20 Default: 0 Description: A fixed absolute threshold is entered as a percentage of the measured variable. If the current meas- urement differs from the last value transmitted by more than the amount of the threshold setting, the current value of the measured variable is trans- value for de- ferred and then serves as reference termining a new difference. The fluctuations of the measured variable are thus smoothed and fewer signals have to be transferred. Data Type: (see Address tab of the RP57x Sink Measurand properties dialogue) Range: RP57x Analog Measurand; RP57x Digital Measurand RP57x Analogue Measurand Default: Description: Defines the type of measured variable. Analogue Measurand: 12 Bit value in twos comformat. plement format. Digital Measurand: 16 Bit value in twos complement RP57x command Fig Unlinked RP57x Source Command object Properties Fig Address tab in the RP57x Source Command properties dialogue 8-145

246 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C RTU, Block No, Bit No. Range: [1 254].[1 2047].[0 15] Default: Allocated while adding object (for each data type starting at 1.1.0). Description: Defines the three-part address of a data point. RTU: RTU process number. This is frequently specified by the customer. To simplify copying bay configurations, it is recommended to specify a number of your own for the highest bay unit address level. When handling disturbance records using transparent data. Block No: Second part of the address. A block contains one command. Bit No: Bit No. always equals zero for commands, i.e. it is not used for commands. Data Type Range: Default: Description: RP57x Command RP57x_FCOM (function command) RP57x Setpoint RP57x Regulation RP57x General Output RP57x Command Defines the type of command

247 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd 8.6. DNP30 DNP3.0 is an o pen, intelligent, robust, modern and efficient SCADA protocol. It can: send and receive with several data types in the same telegram divide telegrams in several frames to achieve better error detection and data recovery only include data that have changed in responses assign priorities to data points periodically request data according to their assigned priorities respond automatically and supports: time synchronization and standard time format multiple master and point-to-point operations user-defined tasks including file transfer DNP30 slave application Fig Unlinked DNP30 Slave Application object Insert new object No Delete object Yes Remove link No 8-147

248 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Properties Fig Specific tab of the DNP30 Slave Application properties dialogue Application ID Range: Default: Allocated while adding object. Description: Uni que identification of the application within the COM581 system. Allocated in ascending order in increments of one and can then be reset. Slave Address Range: Default: 10 Description: The slave address corresponds to the station address of the DNP30 application. Master Address Range: Default: 1 Description: This is the address of the DNP30 master that polls the DNP30 application. NOTICE: Spontaneous data transfer (FC130 unsolicited messages) by the DNP30 application is not supported! 8-148

249 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Counter Time Tags are Suppressed Range: True; false Default: True Description: Count time tags are suppressed when the parameter is set to True. Max Data Frame Size Range: Default: 149 Description: Maximum number of Bytes that can be transferred in a telegram via the DNP3 communication line. Data Link Confirm Time [ms] Range: Default: 200 Description: Waiting time in milliseconds allowed for the receipt of a telegram sent by the COM581 to be confirmed by the master. This value is used for dialogues that require a Data link Acknowledge. Immediate Process Mode is Enabled Range: True; false Default: False Description: If the spontaneous transfer of RTU events is configured and the immediate processing mode is enabled (i.e. set to True), DNP30 responds immediately to requests received from the master, although the confirmation of receipt for a spontaneously sent telegram still has not been received. If set to False, on the other hand, the RTU waits for the above confirmation before it processes the request from the master. This mode of operation is referred to as Process After Confirm. NOTICE: This parameter is not supported by the DNP30 application in COM581. No. of Multiple Requests Range: Default: 4 Description: Determines the maximum number of requests that are permitted in a telegram sent by the master. A typical example is a DNP30 master that requests general polling (Class 0) and events of all three classes in one telegram. The format of this request is therefore: Class data (object 60) Var. 1 Qualifier 06x Class data (object 60) Var. 2 Qualifier 06x 8-149

250 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Class data (object 60) Var. 3 Qualifier 06x Class data (object 60) Var. 4 Qualifier 06x Spontaneous Messages are Enabled Range: True; false Default: False Description: This controls the spontaneous transfer of events by the RTU. If set to True, the RTU transfers events spontaneously without waiting for a request. Counter Interrogation Address Range: Default: 0 Description: This DNP30 address is reserved for polling counters and may not be used for commands or settings. Reason: The DNP3 master does not send a DNP3 object address in the case of counter polling and therefore it has to be defined for counter polling for each project. NCC No. Range: 0 4 Default: 1 Description: Auxiliary attribute which is not relevant for setting the COM581. It is used as a position parameter when importing and exporting data. A setting of 0 determines that signals are not exported to the signal list. Suppress indication with time tag Range: True; false False Default: Description: Time tagged signals referred to as SOE s are sup- if this parameter is set to True. For exam- pressed ple, assuming a bay unit connected to the LON bus generates signal events with and without time tags, the DNP30 master only expects a change of state and not a time tagged signal

251 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd DNP3 data point Fig Unlinked DNP30 Sink Binary Input data point Fig Linked DNP30 Sink Binary Input data point Fig Structuring objects for DNP30 data points Insert new object Sink Datapoints Integrated Totals DNP30 Sink Binary Counter DNP30 Sink Frozen Counter Structuring node Indication DNP30 Sink Binary Input Structuring node Measurand Value Step Position Information DNP30 Sink Analogue Input DNP30 Sink Binary Coded Decimal DNP30 Sink Floating Point DNP30 Sink Frozen Analogue Input Structuring node Sequence of Event DNP30 Sink Binary Input Structuring node System Diagnosis System Control DNP30 Sink Binary Input Structuring node 8-151

252 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Transparent Data DNP30 Sink Transparent Data Structuring node Maintenance Information DNP30 Sink Binary Input Structuring node Source Datapoint Command DNP30 Source Command Structuring node Transparent Data DNP30 Source Transparent Data Structuring node Delete object Yes, all signals that are added can be deleted. Remove link This operation is possible in the signal tree. Properties Fig Address tab in the DNP30 Sink Binary Input properties dialogue Object Address Range: Default: Allocated while adding object (starting at 0). Description: Defines the DNP3 object address, also referred to as DNP30 point. An object address must be unique in the address range of a data type

253 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Data Type Range: Default: Description: DNP30 Binary Input DNP30 Binary Counter DNP30 Frozen Counter DNP30 Analogue Input DNP30 Frozen Analogue Input DNP30 Floating Point DNP30 Binary Coded Decimal DNP30 Command DNP30 Transparent Data Determined at the time of selection. Determines the data type of a signal and cannot be changed subsequently. Internal Address (read only) Range: Default: Inadmissible value Description: A consecutive value is automatically allocated when linking a source signal. The same value is allocated to the sink signal as to the respective source signal. This ID is uniquely identifies the signal connection DNP3 Counter Fig Unlinked DNP30 Sink Binary/Frozen Counter objects Properties Fig Specific tab in the DNP30 Sink Binary Counter properties dialogue 8-153

254 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Priority Range: Default: Description: Class 0 Class 3 Class 0 Determines the priority of a DNP30 signal and apall other DNP30 signals. Class 0 is intended plies to for static objects used for updating the process image. They are transferred, for example, in response to a Class 0 general polling request. Classes 1, 2 and 3, however, are event objects, i.e. they are transferred in the event of a status change. Counter Reset Type Range: Wrap around; Set zero EOP; Set zero after freeze Default: Wrap around Description: Determines according to which criterion the counter is reset. Wrap around: An overflow resets the counter. Set Zero EOP: End Of Period resets the counter. Set zero after freeze: The counter freeze command is followed by a counter reset. Counter Transmission Mode Range: None; EOP; EOP and Intermediate Default: None Description: Determines the counter transfer mode. None: The transfer of the count is not controlled pe- is transferred cyclically at End of riodically. EOP: The count Period Time. EOP and Intermediate: The count is transferred cyclically at End of Period Time and also in re- intermediate request sponse to an (IR)

255 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd DNP3 Indication Fig Unlinked DNP30 Sink Binary Input object Properties Fig Specific tab in the DNP30 Sink Binary Input properties dialogue Priority See DNP3 Counter Indication Type Range: Default: Description: Single, double Single The status of a single indication is described by a Bit corresponding to the positions ON or OFF. The status of a double indication is described by two Bits corresponding to the positions ON or OFF and two intermediate positions. Sequential Event Recording Range: None; Zero to One; One To Zero; Both Default: Both Description: Determines which kind of change of state, i.e. positive or negative-going edge, initiates transmission of an event

256 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Convert DPI into two SPI Range: True; false Default: True Description: Determines whether a double indication is divided between two DNP points with consecutive addresses. The distribution of a DPI with point address n between two DNP30 binary input points conforms to the following principle: DPI status SPI statuses of the two DNP30 point addresses n n DNP3 measurand Fig Unlinked DNP30 Sink objects Properties Fig Specific tab in the DNP30 Sink Analogue Input properties dia- logue 8-156

257 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Priority See DNP3 Counter Deadband Threshold (%) Range: 0 20 Default: 0 Description: A fixed absolute threshold is entered as a percentage of the measured variable. If the current meas- urement differs from the last value transmitted by more than the amount of the threshold setting, the current value of the measured variable is trans- as reference value for de- ferred and then serves termining a new difference. The fluctuations of the measured variable are thus smoothed and fewer signals have to be transferred. NOTICE: Deadband Threshold > 0 then Accumulating Value = 0. Deadband threshold: When using the threshold method, enter the threshold as a percentage > 0. The current value of the measured variable is trans- ferred if the threshold is exceeded. NOTICE: In order to use the threshold method, set Accumulation Value = 0 and Scanning Cycle Time = 0. Accumulating Value (%) Range: Default: 5 Description: Percentage of the accumulated sum. The variation of the measured variable is determined in relation to the cycling time and the last value transmitted and the difference is added or subtracted in accordance with its sign. If the sum exceeds the set limit, the current value of the measured variable is transferred and the summaprocedure starts again. tion Measured variable stabilization: The attributes Accumulating Value and Scanning Cycle Time are used for stabilizing measured variables according to the integration principle

258 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C NOTICE: If Accumulating Value and Scanning Cycle Time 0 then Deadband Threshold = 0 Scanning Cycle Time (s) Range: Default: 1.0 Description: Period during which summation takes place, e.g. 1 s after detecting the deviation of the measured value and calculation by COM581. Offset (%) Range: Default: 0.0 Description: Offset of the measured variable in percent and taking the sign into account. Scaling Factor Range: Default: Description: The measured variable is multiplied by the scaling factor before it is transferred to the remote control station. To achieve the best possible accuracy, only relative values are transmitted (i.e. the measured variable is normalized). The scaling factor chosen can vary according to the protocol in use, the type of measured variable and any special user preferences. The bay units provide measured variables referred to their r.m.s. values. The range is -320% to 320% and is converted to a 16 Bit value between and An individual offset and scaling factor enable every value to be converted to the required format. Example: An NCC can only process 12 Bit measured vari- with ables and therefore they have to be transferred values in the range to The full-scale value should be 120% of the r.m.s. value. Offset: = 0 DNP30_Scaling_Factor:= (320% / 120%) * (2000 / 32000) = NOTICE: Phase-to-phase voltages transferred by the bay unit generally have to be multiplied 1 by the factor

259 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Limit Supervision is Active Range: True; false Default: False Description: Determines whether the limit value supervision is enabled or disabled. False: Limit value supervision is disabled. True: Limit value supervision is enabled. The parameters Deadband Threshold and Accumulating Value are used to stabilize the measured variables DNP3 command Fig Unlinked DNP30 Source Command object Properties Fig Specific tab in the DNP30 Source Command properties dialogue Priority See DNP3 Counter Associated DNP30 Input Signal Range: Default: 0 Description: A command address can be linked to a signal address so that the status of the DNP3 command ob- ject can be updated together with the associated signal object. The permitted signal types are DNP3 process signals and SON signals

260 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C For single process indications, a DNP3 Binary Input Signal is linked to a DNP3 Binary Output Sig- nal as follows: DNP3 binary input signal DNP3 binary output signal State On/Offline State On/Offline 0 Off-line 0 Off-line 0 On-line 0 On-line 1 Off-line 1 Off-line 1 On-line 1 On-line For double process indications, a DNP3 Binary Input Signal is linked to a DNP3 Binary Output Signal as follows (the first signal is evaluated should they be split into two DNP signals): DNP3 binary input signal status DNP3 binary output signal (status only) A bay unit SON signal is linked to a DNP3 Binary Output as follows: SON signal status DNP3 binary output signal status 0 RTU OK 1 On-line 1 RTU disturbed 0 Off-line 8-160

261 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd 8.7. TG TG809 application Fig Unlinked TG809 Application object Insert new object No Delete object Yes Remove link No Properties Fig Specific tab of the TG809 Application properties dialogue Application ID Range: Default: Description: Allocated while adding object. Unique identification of the application within the COM581 system. Allocated in ascending order in increments of one and can then be reset. NCC No. Range: 0 4 Default: 1 Description: Auxiliary attribute which is not relevant for setting the COM581. It is used as a position parameter when importing and exporting data. A setting of 0 determines that signals are not exported to the signal list

262 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Max Data Frame Size Range: Default: 80 Description: Maximum number of Bytes that can be transferred in a telegram on the TG809 communication line TG809 data point Fig Unlinked TG809 Sink Indication data point Fig Linked DNP30 TG809 Sink Indication data point Fig Structuring objects for TG809 data points Insert new object Source Datapoint Command TG809 Source Command Structuring node Transparent Data TG809 Source Transparent Data Structuring node Sink Datapoints Integrated Totals TG809 Sink Counter Structuring node Indication TG809 Sink Indication Structuring node 8-162

263 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Measurand Value Step Position Information TG809 Sink Measurand Structuring node Sequence of Events TG809 Sink Indication TG809 Sink Measurand Structuring node System Diagnosis System Control Maintenance Information TG809 Sink Indication Structuring node Delete object Yes, all signals that are added can be deleted. Remove link This operation is possible in the signal tree. Properties Fig Address tab in the TG809 Sink Indication properties dialogue Station, Cabinet, Tier, Slot and Point No. Range: [0 1020].[0 3]. [0 4].[0 15].[ ] Default: Allocated while adding object (starting at ). Description: Defines the TG809 signal address. NOTICE: The TG800 protocol, supports hardware (physical) and software (logical) addresses. The address mode is determined individually for each signal by the setting for the attribute Is_Hardware_Point on the Specific tab. It is permissible to mix hardware and software addresses in a station

264 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C The two address modes in more detail: Hardware addresses The address is determined by the physical location of the signal on the input/output terminals. The specific hardware address parameters are: Station: Station or device. The device address has to be unique in a TG809 system. Cubicle: The cubicle number in a TG809 station is always = 0 Rack: The row in the cubicle. Slot: Location of the input/output board in a rack. Point No.: Position or offset of the process signal s terminals on the input/output board. Software addresses The addresses are not related to hardware ele- have to be unique within the particular ments, but station. NOTICE: Software addresses in the point number range are reserved for internal objects and may not be used for the addresses of TG809 sig- nals. Data Type Range: Default: Description: TG809 Indication TG809 Analogue Measurand TG809 Digital Measurand TG809 Counter TG809 Command TG809 Setpoint TG809 Transparent Data Determined at time of selection. Determines the data type of a signal and can only be changed for existing objects of type Measurands and Command. Internal Address (read only) Range: Default: Inadmissible value. Description: A consecutive value is automatically allocated when linking a source signal. The same value is allocated to the sink signal as to the respective source signal. This ID is uniquely identifies the signal connection

265 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd TG809 counter Fig Unlinked DNP30 TG809 Sink Counter object Properties Fig Specific tab in the TG809 Sink Counter properties dialogue Current Type Range: Default: Description: Closed Circuit Current Operating Current Double Current Closed Circuit Current Determines the counter operating mode. Closed circuit current: The counter has a single input which is normally closed and conducting and may only be open-circuited for a maximum of 200 ms. Open circuit current: The counter has a single input and is normally open and non-conducting. There is no restriction on the duration of an activat- The ing impulse. Double Current: A double current counter has two inputs, which have to be activated alternately. ID of a double current input is the designation of the first of the two points and must be an even number

266 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C NOTICE: This parameter is only of significance for hardware counters. Mixing double current inputs and other counter inputs should be avoided wherever possible so that large groups can be formed for data transfer. Is Hardware Point Range: True; false Default: False Description: Determines whether the signal address defined on the Address tab of the property dialogue is a hard- (logical) address ware (physical) or software type TG809 indication Fig Unlinked TG809 Sink Indication object Properties Fig Specific tab in the TG809 Sink Indication properties dialogue 8-166

267 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd TG809 Priority Range: 0 3 Default: 0 Description: Determines the transmission priority for a TG809 signal, 0 being the highest and 3 the lowest. When the TG809 master polls for events, signals with the higher priority are transmitted before those with a lower priority. Sequential Event Recording Range: None; Zero to One; One To Zero; Both Default: Both Description: Determines for which kind of change of state, i.e. leading or lagging edge, an event is released for transmission. Indication Type Range: Single; double Default: Single Description: The status of a single indication is described by a bit corresponding to the positions ON or OFF. The status of a double indication is described by two bits corresponding to the positions ON or OFF and two intermediate positions. Is Hardware Po Range: Default: Description: int True; false False Determines whether the signal address defined on the Address tab of the property dialogue is a hardsoftware (logical) address ware (physical) or type. TG809 Mid-position Suppression Time (s) Range: Default: Description: This only applies to signals of the Double Indication type and determined their supervision time. When a double indication changes its state it does not change instantly to the opposite end position, but remains for a given period in an intermediate posi- (00 or 11). The TG809 Mid-position Suppres- tion sion Time (s) determines the maximum time in secindication signal can take when onds that a double changing from one state to another

268 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C TG809 measurand Fig Unlinked TG809 Sink Analogue Measurand object Properties Fig Specific tab in the TG809 Sink Analogue Measurand properties dialogue TG809 Priority Range: 0 3 Default: 0 Description: Determines the transmission priority for a TG809 signal, 0 being the highest and 3 the lowest. When the TG809 master polls for events, signals with the higher priority are transmitted before those with a lower priority. Null Zone Activation Range: True; false Default: False Description: Determines whether a measure value is set precisely to zero if it is in the zero zone. The width of the zero zone is set in the TG809 RTU Configuration properties dialogue for the parameter Null Zone Delta. NOTICE: This parameter is not implemented in the COM581 TG809 application

269 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Accumulating Value (%) Range: Default: 5 Description: Percentage of the accumulated sum. The variation of the measured variable is determined in relation to the cycling time and the last value transmitted and the difference is added or subtracted in accordance with its sign. If the sum exceeds the set limit, the current value of the measured variable is transferred and the summation procedure starts again. Measured value stabilization: This attribute is used for measured value stabiliza- tion according to the integration principle. Scannin g Cycle Time (s) Range: Default: 1.0 Description: Period during which summation takes place, e.g. 1 s after detecting the deviation of the measured value and calculation by COM581. Default value = 1 second Offset (%) Range: Default: Description: Offset of the measured variable in ing the sign into account. percent and tak- Scaling Factor Range: Default: Description: The measured variable is multiplied by the scaling factor before it is transferred to the remote control station. To achieve the best possible accuracy, only relative values are transmitted (i.e. the measured variable is normalized). The scaling factor chosen can vary according to the protocol in use, the type of measured variable and any special user preferences. Example: An NCC can only process 15 Bit measured variables and therefore they have to be transferred with values in the range to The fullscale value should be 120% of the r.m.s. value. Offset: = 0 TG809 Scaling Factor:= (320% / 120%) * (32000 / 32000) =

270 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C NOTICE: Phase-to-phase voltages transferred by the bay unit generally have to be multiplied 1 by the factor. 3 Is Hardware Point Range: True; false Default: False Description: Determines whether the signal address defined on the Address tab of the property dialogue is a hard- or software (logical) address ware (physical) type TG809 RTU configuration Fig Insert new object TG809 RTU configuration Delete object Yes, a TG809 RTU Configuration object can be deleted. Remove link No Properties Fig Specific tab in the TG809 RTU Configuration properties dialogue 8-170

271 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Station No. Range: Default: Allocated while adding object (starting at 0). Description: Every station has a number, which is unique throughout the system. It is included in the ID of every process object and thus part of the TG809 signal addresses. Communication No. Range: Default: 0 Description: Defines the address at the data link level used by the master to call the station on a TG800 communication line. Null Zone Delta (in thousandths) Range: Default: 0 Description: Determines the width of the zero zone in thouscale. If the Null Zone Activation pa- sandths of full rameter is set to True, the measured variable is set precisely to zero as soon as the measurement enzone (-delta to croaches on the zero +delta). NOTICE: This parameter is not implemented in the COM581 TG809 application. Call Group Range: 0 7 Default: 0 Description: Determines the call group to which a counter is assigned. A master counter call includes a bay, which defines the group to be queried. The TG809 station responds with counts relating to the group queried. The group form in the query can include more than one group. NOTICE: This parameter is not implemented in the COM581 TG809 application. Counter Call Type Range: Remote Call; Periodic; Fixed Times Default: Remote Call Description: The call mode determines from where the RTU obtains the count requests

272 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Remote Call: The master requests the count periodically. Periodic: Counts are transferred periodically. The respective parameters Period Hour, Period Minute and Period Call Type are set in the properties dialogue. Fix-Times: Counts are transferred at specified fixed times. NOTICE: This parameter is not implemented in the COM581 TG809 application. Periodic Call Type Range: Freeze, Freeze Reset, Freeze Transmit, Freeze Reset Transmit Default: Freeze Description: This only applies when Counter Call Type is set to Periodic and determines whether the count is frozen or reset and/or immediately transferred when a request input is excited. NOTICE: This parameter is not implemented in the COM581 TG809 application. Period Hour Range: 0 23 Default: 0 Description: This only applies when Counter Call Type is set to Fixed Times and determines at which hour the RTU counts are transferred. NOTICE: This parameter is not implemented in the COM581 TG809 application. Period Minute Range: 0 59 Default: 0 Description: This only applies when Counter Call Type is set to Fixed Times and determines at which minute of the hour set for Period Hour the RTU counts are transferred. NOTICE: This parameter is not implemented in the COM581 TG809 application

273 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd 8.8. ACP The ACP (Application Communication Protocol) is used by bay units to communicate with MicroSCADA (SYS500). It is a point- ANSI X3.28 with various exten- to-point protocol, which permits both subscribers to transmit data spontaneously, and is based on sions on the higher protocol layers. The following diagram illustrates a typical application of ACP. LSK-Server SYS500-Client SYS500 Server IEC101 ACP Appl.Id=20 Appl.Id= 1 MDP ACP Appl.Id= 2 ACP Appl.Id=7 Node=5 MVB Appl.Id= 3 COM581-1 TCP/IP COM-Client SYS500-Client COM-Client SYS500-Client ACP Appl.Id=7 ACP Appl.Id= 8 ACP Appl.Id= 6 ACP Appl.Id=7 MDP MDP Appl.Id=4 IEC103 Appl.Id=21 IEC101 Appl.Id=4 IEC103 COM581-2 COM581-3 Fig Point-to-point communication with an ACP application ACP application Fig Insert new object Yes Delete object Yes 8-173

274 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Remove link No Properties Fi g Specific tab in the ACP Applications properties dialogue Application ID Range: Default: Allocated while adding object. Description: Identification number which uniquely identifies the application within COM581. It is incremented each time by one and can then be reset. ACP Device Address Range: Default: 0 Description: Defines the ACP Device Address for the ACP application at the COM581 end. The address is based on the MicroSCADA address definitions given in Section Example for configuring the commu- MicroSCADA - COM581 and determined nication according to the following relationship: ACP Device Address = 2048 * 24 + STA(COM581) 8-174

275 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd ACP Node Number Range: Default: 0 Description: Defines the ACP Node Number for the ACP application at the COM581 end. The address is based on the MicroSCADA address definitions given in Section Example for configuring the communication MicroSCADA - COM581 and determined according to the following relationship: ACP Node Number = NODE(COM581) ACP Link Device Address Range: Default: 0 Description: Defines the ACP Link Device Address for the ACP application at the COM581 end. The address is based on the MicroSCADA address definitions given in Section Example for configuring the communication MicroSCADA - COM581 and determined according to the following relationship: ACP Link Device Address = 2048 * 2 + NET(COM581) Destination Device Address Range: Default: 0 Description: Defines the Destination Device Address for the ACP application at the opposite end of the link. The address is based on the MicroSCADA address definitions given in Section Example for configuring the communication MicroSCADA - COM581 and determined according to the following relationship: Destination Device Address = 2048 * 1 + APL(MicroSCADA) Destination Node Number Range: Default: 0 Description: Defines the Destination Node Number for the ACP application at the opposite end of the link. The address is based on the MicroSCADA address definitions given in Section Example for configuring the communication MicroSCADA - COM581 and determined according to the following relationship: Destination Node Number = NODE(MicroSCADA) 8-175

276 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Destination Link Device Address Range: Default: 0 Description: Defines the Destination Link Device Address for the ACP application at the opposite end of the link. The address is based on the MicroSCADA address definitions given in Section Example for configur- ing the communication MicroSCADA - COM581 and determined according to the following relationship: Destination Link Device Address = 2048 * 2 + NET(MicroSCADA) Client IP Address Range: Entire IP address range Default: ###.###.###.### Description: Defines the client s IP address, which determines whether the ACP application operates in a server or client mode. See remarks below. ACP Error Msg Enabled Range: True; false Default: False Description: This attribute is not used by the ACP application. ACP Service Type Range: SYS500 1; SYS500 2; COM 1; COM 2 Default: SYS500 1 Description: Defines the various supported client/server types. NCC No. Range: 0 4 Default: 1 Description: Auxiliary attribute which is not relevant for setting the COM581. It is used as a position parameter when importing and exporting data. A setting of 0 determines that signals are not exported to the signal list. An ACP application always establishes a point-to-point link (server client). Enter the client s IP Address for every application for which ACP Application Type = Server. This ensures that the data (e.g. switching command) go to the right client. A pointto-point link (server client) enables full advantage to be taken of the MDP mechanisms for marshalling data and in addition the clients are isolated from each other. In the case of a client application, the Client IP Address is its own IP address

277 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd The ACP configuration is subject to the following restrictions: - A maximum of 6 server applications per CPU board may be defined. - All the server applications must be configured for the same Service Type. Destination Link Device Address monitors the Ethernet connec- tion at the TCP/IP level. A Minor Error signals a failure. - Only two client applications may be configured on each board. - The Service Type attributes of the client applications must be different. - Client and server with the same Service Type must not run simultaneously on the same board. All ACP applications running on the same board have the same ACP Node Number. Configuring an ACP application as a point-to-point link: ACP Service Type The following TCP/IP host addresses for the various types of server are the default entries in the SWT for the ACP board: SYS500_1: SYS500_2: COM_1: COM_2: Refer to Section 4.4. SWT Software Download Tool in the COM581 Operating Instructions for the procedure for changing these addresses. Client IP Address NOTICE: If the entry for Client IP Address in the ACP Applications properties dialogue is the same as in the SWT, the application is an ACP server, otherwise an ACP client. The following rules must be observed when assigning the IP addresses: 8-177

278 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C The first three bytes of an IP (also referred to a the network address) in a subnet must agree. The fourth byte defines the target device. If a client is connected to a server with a different network address (i.e. another sub-network), server and client communicate via a gateway (router). In this case, the routers in the clients or server sub-networks must have valid IP addresses. Example: Clients sub-network Client_IP Gateway = Z Server s sub-network Server_IP Gateway = X = Y = W COM581 Ethernet TCP/IP x (Client) Ethernet TCP/IP Z Gateway Ethernet TCP/IP W MicroSCADA Base System Ethernet TCP/IP Y (Server) TCP/IP LAN TCP/IP LAN Fig Assigning network addresses If the gateway network address set on the client (server) does not agree with its own network address, an error occurs when at- and this in turn causes an error in tempting to link two subnets the COM ACP data point Fig Unlinked ACP Sink Single Indication object Fig Linked ACP Sink Single Indication object 8-178

279 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Fig ACP data point selection Insert new object Sink Datapoints Integrated Totals ACP Sink Integrated Totals Structuring node Indication ACP Sink Single Indication ACP Sink Double Indication Structuring node Measurand Value ACP Sink Measurand Scaled 16 ACP Sink Measurand Real 32 Structuring node Step Position Information ACP Sink Step Position Information Structuring node Command ACP Sink Command Structuring node Sequence of Events ACP Sink Sequence Of Events Structuring node 8-179

280 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C System Diagnosis ACP Sink System Diagnosis ACP Sink Single Indication ACP Sink Sequence Of Events Structuring node System Control ACP Sink Single Indication ACP Sink Sequence Of Events Structuring node Transparent Data ACP Sink Transparent Data Structuring node Maintenance Information ACP Sink Single Indication ACP Sink Sequence Of Events Structuring node Source Datapoint Integrated Totals ACP Source Integrated Totals Structuring node Indication ACP Source Single Indication ACP Source Double Indication Structuring node Measurand Value ACP Source Measurand Scaled 16 ACP Source Measurand Real 32 Structuring node Step Position Information ACP Source Step Position Information Structuring node Command ACP Source Command Structuring node Sequence of Events ACP Source Sequence Of Events Structuring node System Diagnosis ACP Source System Diagnosis ACP Source Single Indication ACP Source Sequence Of Events Structuring node System Cont rol ACP Source Single Indication ACP Source Sequence Of Events Structuring node Transparent Data ACP Source Transparent Data Structuring node 8-180

281 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Maintenance Information ACP Source Single Indication ACP Source Sequence Of Events Structuring node Delete object Ye s, all signals that have been added can be deleted. Remove link This operation is possible in the Signal Tree view. Properties Object and Dev Range: Default: Description: ice Address [ ].[ ] Fig Address tab in the RP57x Sink Single Indication properties dialogue Allocated while adding object (starting at 0.0). Defines the ACP data point address as follows: Object address: Corresponds to the OA as used for the MicroSCADA database. Device address: The address is based on the MicroSCADA address definitions given in Section Example for configuring the communication MicroSCADA - COM581 and determined according to the following relationship: ACP Device Address = 2048 * 24 + STA 8-181

282 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Data Type Range: Default: Description: ACP Single Indication ACP Double Indication ACP Sequence of Event ACP Step Position Information ACP Measurand Value Scaled 16 ACP Measurand Value Real 32 ACP Integrated Totals ACP Command ACP Transparent Data ACP File ACP System Diagnosis ACP Bitstring32 Determined at time of selection. Defines the data type of the signal, which in the case of an existing object cannot be changed. Internal Address (read only) Range: Default: Inadmissible value Description: Consecutive values are automatically allocated to the sink signals when linking the source signals. The same value is allocated to a sink signal as to the respective source signal. This ID is uniquely identifies the signal connection. ACP data points that are configured as signals (indications) or measured variables (measurands) are stored in the process database. They can be viewed by issuing a general polling request. Sequence of Events designates real-time signals (e.g. limit exceeded, circuit-breaker operation etc.), which are transferred to the higher-level control system, but not retained by the process image. Signals configured for system diagnostics are set as soon as an error in the target application is detected Example for configuring the communication MicroSCADA - COM581 The following example illustrates how to set up an ACP communications link between a basic MicroSCADA system and COM581. In order to fully understand the settings of the application parameters, it is necessary to explain a number of concepts in relation to MicroSCADA and COM581. Prior knowledge of Micro- SCADA is assumed

283 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Mi croscada front end As far as a basic MicroSCADA system is concerned, a COM581 a front end computer acting as an interface for all the devices co mmunicating via it with MicroSCADA. Such devices must be defined in MicroS CADA (configuration file SYS_BASCON.COM) as IAL stations Type 24 (IAL= Internal Application Layer; Type 24 can be changed following consultation). Entry in the SYS_ BASCON.COM file: #CREATE STY24:B = LIST(NA = "IAL", DB = "REX", CX = "ACP") Type 24 stations are configured to use the Ethernet interface of the basic system as communications link. The COM581 is thus itself defined as an IAL station. ACP protocol and COM581 communication parameters Every ACP telegram contains specific address information. The table below relates the most important expressions used in the standard ACP protocol and the corresponding COM581 ACP communications parameter. ACP protocol parameters COM581 ACP parameters Destination Node Address (DST) Destination Node Number Source Node Address (SRC) Packed Logical Destination Address (LDR) ACP Node Number Destination Device Address Packed Logical Source Address (LSR) ACP Device Address Table 8.20 Relation between expressions used in the ACP protocol and the COM581 CAP tool 8-183

284 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Example of a configuration: MicroSCADA (8.4.3) Base System 1 Apl 1 (base) Apl 2 (wd) Apl 3 (base_ext) Apl 4 (wd_ext) SA 209 / Node 9 (NET 9) sys_bascon.com Link 3 (integrated) Link 1 ( LAN) SA 203 / Node 3 (NET 3) PC-NET Line 1 com 1 Line 2 com 2 Line 5 PCLTA Ch 1 1/127 Line 6 PCLTA Ch 2 2/126 Ethernet TCP/IP (Server) COM581 SA 201 / Node 1 (NET 1) ACP card Ethernet TCP/IP (Client) TCP/IP LAN Fig Example of configuring MicroSCADA and COM581 In this example, COM581 is configured to communicate with the MicroSCADA application base (APL 1), MicroSCADA acting as an ACP server and COM581 as client. This necessitates determining the ACP communication parameters: ACP parameters specific for COM581 a) ACP Device Address (IAL Station No. =1) = 2048 * = b) ACP Node Number (Node = 1) = = 201 c) ACP Link Device Address (NET = 1) = 2048 * = 4097 Ta ble 8.21 Determining the ACP communication parameters for COM581 For a) COM581 IAL Station Type = 24 Specific MicroSCADA ACP parameters a) Destination Device Address (APL No. = 1) = 2048 * = 2049 b) Destination N ode Number (Node = 9) = = 209 c) Destination Link Device Address (NET = 9) = 2048 * = 4105 Table 8.22 Determining the ACP communication parameters for Micro- SCADA Fo r a) MicroSCADA IAL Station Type =

285 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd CAP581 settings: Fig Setting the ACP application communication parameters Settings using the software tool (SWT) The valid TCP/IP addresses have to be entered in the SWT before loading the basic COM581 software. Fig Setting the TCP/IP addresses on the ACP board 8-185

286 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C 8.9. IEC61850 This is an application which supports interbay bus using the IEC61850 protocol IEC61850 application Fig IEC61850 Application ID object Insert new object No Delete object Yes Remove link No Properties Fig Specific tab in the IEC61850 Application properties dialogue 8-186

287 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Application ID Range: Default: Allocated while adding object. Description: Unique identification of the application within the COM581 system. Allocated in ascending order in increments of one and can then be reset. IEC61850_Redundancy Range: - NOT_REDUNDANT - REDUNDANT I - REDUNDANT II - REDUNDANT III Default: Allocated while adding object. Description: Defines Redundancy of application Server_Timeout Range: Default: Allocated while adding object. Description: Polling_Cycle_Time_For_Active_List Range: Default: Allocated while adding object. Description: Server_Supervision_Cycle_Time Range: Default: Allocated while adding object. Description: GI_Request_Delay Range: Default: Allocated while adding object. Description: Polling_Cycle_Time_For_Background_List Range: Default: Allocated while adding object. Description: 8-187

288 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Max_Retries_In_Active_Polling_List Range: Default: Allocated while adding object. Description: Autentication_Present Range: - No - Yes Default: Allocated while adding object. Description: Autentication_Password Range: 16 Characters Default: No. Description: NOTICE: There are other parameters of IEC61850 application, which are taken directly from imported SCD file and directly written into the download database. Example: TCP/IP address, COM 581 IED name IEC61850 data points Fig Unlinked IEC61850 Sink Single Indication object 8-188

289 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Fig Structuring objects for IEC61850 data points Insert new object NOTICE: All signals for this application MUST be defined and imported from an SCD file which have to define the whole come system level. The COM581 engineering can munication on th only choose from signals already available for the communication. (Defined Data Sets and Report Control Blocks). Delete object Ye s, all signals that are added can be deleted. Remove link This operation is possible in the signal tree

290 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Engineering procedure and suggestions To define the signals to be used by the IEC61850 application the substation definition file (the SCD file ) has to be imported into the Signal List. The signal list provides the functionality to create the signal list and prepare the COM581 device configuration file (the CCF file). The automatically created Signal List has to be completed with NCC address and applications numbers for each signal to be exported into the CAP Tool. There is no possibility to add manually a signal in the Signal List because the same signal must exist also in the CCF file, which is derived from the SCD file. The COM581 configuration engineer can only choose from signals already available for communicata Sets and Report Control Blocks). The tion. (Pre-defined Da only exception is the g eneration of signals with the PSF functions

291 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd IEC104 The remote control and station automation equipment and sys- of manufacturers support the remote control protocol [IEC ], although to differing degrees as described in the interoperability lists tems supplied by a number Recommendation IEC defines the use of an open TCP/IP interface for transferring IEC ASDU s within the bounds of a netwo rk (Ethernet LAN). With the exception of the modifications given below, the applica- tion layer of the IEC remote control protocol corre- sponds to IEC : Additions: Process command ASDU s are time tagged. Changes: All ASDU s conformin g to the IEC recommendation and having a Type CP24 time tag are not included in recommendation IEC Test command with tim e tag CP56Time2a replaces the ASDU type Test command (without time tag). The transportation and physical layers of remote control protocol IEC are implemented in IEC with TCP/IP (Transmission Control Protocol/ Internet Protocol). Limitations: Only the slave end is implemented at present IEC104 slave application Fig IEC104 Slave Application ID object Insert new object No Delete object Yes Remove link No 8-191

292 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Properties Fig Address tab of the IEC104 Slave Application properties dialogue Application ID Range: Default: Allocated while adding object. Description: Unique identification of the application within the COM5 81 system. Allocated in ascending order in increments of one and can then be reset. Common Address of ASDU (CAA) Range: Default: 0 Description: Defines the station address for the IEC104 Slave Applica tion. This address occupies 2 bytes. The value is reserved for broadcast, i.e. inforthat is distributed to all mation stations. NOTICE: The attribute Common Address of ASDU (CCA) de- of the IEC104 Slave Application itself. fines the logical address Normally one logical address (Common Address of ASDU (CCA)) is assigned per device, however, this is not mandatory. A physical device can have several logical station addresses

293 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Properties Fig Telegram tab of the IEC104 Slave Application properties dialogue Max Frame Length (bytes) Range: Default: 249 Description: Maximum number of bytes that can be transmitted in a telegram on the IEC104 communication line. Max No. of High Priority Telegrams Range: Default: 10 Description: Determines the maximum quantity of sequential high priority data that can be packed in a telegram. Data with higher priority are sent before data of lower priority. Max No. of Medium Priority Telegrams Range: Default: 3 Description: Determines the maximum quantity of sequential medium priority data that can be packed in a telegram. Data with higher priority are sent before data of lower priority. Max No. of Low Priority Telegrams Range: Default: 1 Description: Determines the maximum quantity of sequential low priority data that can be packed in a telegram. Data with higher priority are sent before data of lower priority

294 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Properties Fig Application Time tab of the IEC104 Slave Application properties dialogue Clock Synchronization Cycle Time (s) Range: Default: 60 Description: Determines the waiting time allowed for the receipt of synchronizing telegrams from the NCC. The waiting time is not started for a setting of 0. For time settings higher than 0, the system detects whether a synchronization telegram is received from the NCC within the set time. If not, the local time on the board running the protocol application is set to invalid until a new synchronization telegram is successfully received. Summer Time Offset (h) Range: Default: 1 Description: Defines the summer time (daylight saving) in hours. The Summer Time Offset is only added to time tagged events when the bay units send them with the summer time flag set. Timeout for Keeping Information (s) Range: Default: 60 Description: After a communication failure has been detected, this parameter determines the time in seconds during which all the data ready for transmission are stored in a queue before being reset (deleted)

295 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Baudrate Generator Range: NO, YES Default: NO Description: Not used by the IEC104 application. Link Test Cycle Time (s) Range: 0 50 Default: 30 Description: Not used by the IEC104 application. Instead, the link to the NCC is supervised with the aid of the transport layer parameter t 0 Time out of connection establishment. Scanning Cycle Time (s) Range: Default: 30 Description: Scanning Cycle Time determines the sampling cycle for spontaneous measured values that are stabilized using the accumulating threshold value technique. Test Command Cycle Time (s) Range: Default: 60 Description: Determines the cycling time for periodically sending IEC104 Test Command. The test command is sent for a setting of 0. This attribute is only effective when the IEC104 application is configured as master, but this is not supported at present. Command Supervision Timeout (s) Range: Default: 10 Description: Determines the waiting time in seconds for the general polling to finish after communication has been established. Should general polling not be finished within the Command Supervision Timeout, i.e. the RTU data received were incomplete, a new general polling request is sent. This attribute is only of consequence when IEC104 Application has been configured as master, but this is not supported at present

296 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Link Start-up Delay (s) Range: Default: 0 Description: Determines the delay in seconds for establishing communication with the NCC. Thus when starting the system, the process image is updated by the bay units before the NCC can initiate general polling. This prevents the NCC from temporarily tagging the data it receives as invalid when COM581 is restarted. Properties Fig Time Tag tab of the IEC104 Slave Application properties dialogue Indication Time Tags are Suppressed Range: NO, YES Default: YES Description: Determines whether time tagged events received via Channel 2 are forwarded with or without time tag. They are forwarded without time tag for a setting of Yes and with for a setting of No. This is used, for example, when time tagged events are transmitted via Channels 2 and 3. Counter Time Tags are Suppressed Range: NO, YES Default: NO Description: As for Indication Time Tags are Suppressed, but applies to the data type Integrated Totals

297 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Step Position Time Tags are Suppressed Range: NO, YES Default: YES Description: As for Indication Time Tags are Suppressed, but applies to the data type Step Position. Send GI with Time Tag Range: NO, YES Default: NO Description: Determines whether general polling takes place with time tags or not. If yes, the time tag corresponds to the time of the local COM581. Properties Fig Transport Interface tab of the IEC104 Slave Application properties dialogue Own IP Address Range: Default: Description: Defines the applications own address. The transport layer of the IEC104 application only confirms receipt of requests for connection sent to it. Client IP Address 1 4 Range: Default: Description: Defines the IP address of clients that are permitted to establish a connection with the transport layer of the IEC104 application. Only requests for connection from the clients listed are confirmed

298 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C IEC104 data point The data point description in this case is the same as that for the IEC101 Slave Application, the only difference being the application name in the signal tree, i.e. IEC104 instead of IEC101. The- refore please refer to Section IEC101 data point. Service Type Range: COM 1, COM 2; COM 3; COM 4 Default: COM1 Description: Determines the operating mode of the transport layer. In the case of the IEC104 Slave Application, this attribute has to be set to COM 1, because COM 1 corresponds to the operating mode. Max No of Client Connections Range: 1 4 Default: 1 Description: Determines the maximum permissible number of logical TCP/IP connections that can communicate simultaneously with the transport layer of the IEC104 application. Redundancy Group Range: None Default: None Description: Defines the configuration of a redundant group. Within a redundant group, telegrams with useful data are only transmitted via the active line and all other lines are in a standby mode, which only per- The mits line supervision and control telegrams. Redundancy Group attribute is defined as a client index pattern, the client number of the configuration being the index

299 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd DIA diagnosis signals This Section describes how to create and configure the diagnostic messages that are supported by COM581. COM581 includes a DIA application that distributes the config- (Type_ID=200) to various ured error messages as DIA telegrams addresses in the system. Since only the last state of a subsystem can be saved for Object State, fast distribution of minor and major system errors is impossible with the existing DIA polling function. Thus only the current status at the time of polling can be transmitted. The self-supervision and diagnostic function (DIA) only runs on the IMP board. DIA application Fig Unlinked DIA Application ID object Insert new object No Delete object Yes Remove link No Properties Fig Specific tab of the DIA Application properties dialogue 8-199

300 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Application ID Range: Default: Allocated while adding object. Description: Unique identification of the application within the COM581 system. Allocated in ascending order in increments of one and can then be reset. Fig LMI Text tab of the DIA Application properties dialogue The LMI (local HMI) text type Configuration Version includes the designation of the configuration and this can be viewed on the local HMI. Before downloading the configuration a unique designation should be created by the tool or the user. NOTICE: Provision is made for automatically incrementing the version number of the download database for each build

301 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd The name of the loaded download database or the project name is entered as the value for Configuration Version. A version number can be added at the end of this name. Enter # before the version number for it to be automatically incremented DIA data point Fig Unlinked DIA System Diagnosis object Fig Linked DIA System Diagnosis object in the signal tree Insert new object DIA System Diagnosis Delete object Yes Remove link No Properties Fig Specific tab in the DIA System Diagnosis properties dialogue 8-201

302 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Sequential Event Recording Range: Zero to One; One To Zero; Both Default: Both Description: Determines which change of state, i.e. leading or lagging edge, releases an event for transmission. Fig Address tab in the DIA System Diagnosis properties dialogue Station Address Range: Default: 0 Description: Device ID of the board to be supervised. Subsystem Range: DIA MPL DAC TIM DBS MDP RP571S RP570S RP570M TCS2S MAC TG809S IEC101S IEC103M IEC101M RP571M IEC103S DNP3S ACP LAC PSF Default: DIA Description: Defines the type of application (subsystem) to be supervised. The subsystems in bold print apply to the COM581 system supervision. Error Number Range: Default: 0 Description: Unique number identifying an error message. The latter can be viewed on the local HMI and together with the Device ID and Subsystem gives a clear indication of the cause of the failure

303 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Internal Address (read only) Range: Default: Inadmissible value. Description: A consecutive value is automatically allo cated when linking a source signal. The same value is allocated to the sink signal as to the respective source signal. This ID is uniquely identifies the signal connec tion E rror messages generated by the DIA system (Error No.) The table below lists all the diagnostic messages. Those can be selected from this table that have t o be configured using CAP581 for transfer to the power system control centre. The error messages in bold print are the main ones of conse- quence for supervising the COM581. Error No. Designation Significance (subsystem) 0 No_Error (RP571, MDP, DIA) 11 Ial_Queue_Overflow_Ch_1 IAL Channel 1 queue is full Note: Queue overflow (MDP queues) for commands (slave application) or return confirmations (master application) 12 Ial_Queue_Overflow_Ch_2 IAL Channel 2 queue is full Note: Queue overflow (MDP queues) for signals and measured variables. This can mean that too many (unsmoothed) measured variables are being transferred. 13 Ial_Queue_Overflow_Ch_3 IAL Channel 3 queue is full Note: Ditto, but for spontaneous data. 14 Ial_Queue_Overflow_Ch_4 IAL Channel 4 queue is full Note: Ditto, but for metered values. 15 Ial_Queue_Overflow_Ch_5 IAL Channel 5 queue is full NOTICE: Ditto, but for transparent data. 16 Ial_Queue_Overflow_Ch_6 IAL Channel 6 queue is full Note: Ditto, but for diagnostic messages (scarcely likely to occur). 21 Appl_Queue_Overflow_1 An application queue is full Note: Queue overflow for commands from the application to an external line (e.g. return confirmation from IEC101 to power system control). 22 Appl_Queue_Overflow_2 An application queue is full Note: Ditto for signals. 23 Appl_Queue_Overflow_3 An application queue is full Note: Ditto for spontaneous data

304 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Error No. Designation Significance (subsystem) 24 Appl_Queue_Overflow_4 An application queue is full Note: Ditto for metered values. 25 A ppl_queue_overflow_5 An application queue is full Note: Ditto for transparent data. 26 Appl_Queue_Overflow_6 An application queue is full Note: Irrelevant. 31 Radio Clock not available 41 External line 1 not available Radio clock not available. Note: The radio clock is defective, not inserted or incorrectly configured. Fault on external line (HW, SW, Ethernet, modem). Note: External connection to the first instance of an application failed (e.g. optical fiber cable not plugged in, no TCP/IP link etc.). This is of consequence only for applications that can be configured several times. 42 External line 2 not available Fault on external line (HW, SW, Ethernet, modem). Note: External connection to the second instance of an application failed (e.g. optical fiber cable not plugged in, no TCP/IP link etc.). This is of consequence only for applications that can be configured several times. 43 External line 3 not available Fault on external line (HW, SW, Ethernet, modem). Note: External connection to the third instance of an application failed (e.g. optical fiber cable not plugged in, no TCP/IP link etc.). This is of consequence only for applications that can be configured several times. 44 E xternal line 4 not available Fault on external line (HW, SW, Ethernet, modem). Note: External connection to the fourth instance of an application failed (e.g. optical fiber cable not plugged in, no TCP/IP link etc.). This is of consequence only for applications that can be configured several times. 45 External line 5 not available Fault on external line (HW, SW, Ethernet, modem). Note: External connection to the fifth instance of an application failed (e.g. optical fiber cable not plugged in, no TCP/IP link etc.). This is of consequence only for applications that can be configured several times. 46 External line 6 not available Fault on external line (HW, SW, Ethernet, modem). Note: External connection to the sixth instance of an application failed (e.g. optical fiber cable not plugged in, no TCP/IP link etc.). This is of consequence only for applications that can be configured several times. 47 External line 7 not available Fault on external line (HW, SW, Ethernet, modem). Note: External connection to the seventh instance of an application failed (e.g. optical fiber cable not plugged in, no TCP/IP link etc.). This is of consequence only for applications that can be configured several times

305 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Error No. Designation Significance (subsystem) 48 External line 8 not available Fault on external line (HW, SW, Ethernet, modem). Note: External connection to the eighth instance of an application failed (e.g. optical fiber cable not plugged in, no TCP/IP link etc.). This is of consequence only for applications that can be configured several times. 50 External line not available Fault on external line (HW, SW, Ethernet, modem). Note: External connection failed (e.g. optical fiber cable not plugged in, no TCP/IP link etc.). 51 Item not found Item not found in database Note: Address not configured. 52 Unknown function Type_ID or COT not defined Note: The requested function has not been configured (e.g. Type_ID and COT that are not supported). 53 Configuration error Error caused by illegal configuration. Note: Generated during start-up when the configura- tion data are inconsistent. 54 VME bus error Error on VME bus. 55 One power supply is down One power supply has failed. Note: One of a pair of redundant supplies has failed or is switched off. 59 IBB_Time_Sync_Fail IBB not connected. Note: No synch impulse, bus administrator failed or optical fiber cable to COM581 not plugged in. 176 Storage_Error A configured exception storage error has occurred (DBS). Note: Generated during start-up when the heap setting for starting the database is insufficient. This can occur when the default database has changed. 177 Set_Not_Ready_Error Error while attempting Set_Not_Ready. 178 Subtask_Error Another (sub-) task has signaled an error. 179 Time_Exceeded Waiting time for a lower control level device exceeded. 180 Set_Ready_Error Error while attempting Set_Ready (DIA). 181 Shutdown_Error Error during system shutdown (DBS, MAC, EVP). 182 Subtask_Lost Subtask did not respond within the specified timeout. 183 Lower_Level_Error Error occurred on a lower abstraction level. 184 Startup_Error Error occurred while starting application (DBS, DIA, MAC, EVP, TIM). 185 Initial_Check_Error Error occurred during initial application check. 186 Application_Not_Licensed Application found to be not licensed

306 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Error No. Designation Significance (subsystem) 187 Transition_Error Error due to attempting forbidden state transition (OBJ and therefore all subsystems). 189 Other_Appl_Fail Another application has failed to transfer the required data. 190 Other_Appl_Inconsistent Another application has transferred inconsistent or unexpected data. 191 Own_Appl_Inconsistent The application itself has inconsistent data or data is missing. 192 Num_Restarts_Exceeded The number of restarts in the case of failure has been exceeded. 193 Load_New_Error An error has occurred while loading a new system. 194 Default_Values_Loaded An application has loaded its default values from the database. 195 Attributes_Not_Valid The attributes for an application during Load_New have been found invalid or inconsistent (EVP). 196 Signal_Not_Connectable A signal could not be connected using another signal. 197 Unknown_Error An unknown internal error has been detected and no error code assigned (MDP). 198 Own_Exception An internal exception has been detected. 199 Own_Unexplained_Except An unexplained exception (exception/when others) has been detected (RP571). 200 Own_ Constraint_Except An exception due to a constraint error has been detected. Table 8.23 Configurable error messages generated by the diagnostic system 8-206

307 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Example for the configuration of an error message The procedure for configuring an error (diagnostic) message is explained by the following example: Example for Error code 41: Supervision of the operation of one remote control line (IEC101) via the other remote control line (RP571). Should the communication between COM581 and power system control (IEC101) be interrupted, an error (diagnostic) message has to be sent to power system control (RP571). The first step of the configuration is to create a diagnostic application on the IMP board. Fig Preinstalled DIA application Only the system data points of type System Diagnosis can be created below diagnosis application. Fig Creating a DIA system diagnosis function 8-207

308 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Fig Address tab of the DIA IEC101 Line Supervision properties dialogue for setting the diagnosis signal address Fig Creating a new data point on the RP571 slave board 8-208

309 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Fig General tab of the RP571 DIA 101 Line Supervision properties dialogue for entering the name of a data point Fig Address tab of the RP571 DIA 101 Line Supervision properties dialogue How the signals are linked in the Signal Tree view is explained below. Firstly, a new Signal Version has to be created so that the signals can be uniquely assigned to an object

310 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Fig Creating a new Signal Version below COM581 in the signal tree view Fig Linking the signals for the line supervision function in the signal tree view 8-210

311 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Project-specific function (PSF) The functional requirements that a PSF subsystem has to fulfill and the requirements it places on other subsystems are given in this section. A PSF can establish project-specific links and convert and multiply signals. However, the additional engineering cost of configuring additional signals and their links should not be ignored. The following functions are provided: Generation of binary general signals: AND, OR, dynamic OR Type conversion: 103 measured variables to 101 measured variables, signals (indications), diagnosis messages and signals with relative time tags Multiplication of signals Generation of command sequences or multiplication of com- distributed to several mands (e.g. counter polling command bus segments) Generation of fleeting signals Generation of error (diagnosis) messages, warnings and disturbance signals Signal inversion Suppression of telegrams generated by standard modules: AND, OR, NOT, DISPATCHER, CONVERT, PULSE and TRASH SCALE, ADD, Geometric_ADD and Comlpex_ADD Regardless of data type (Type_ID) and function blocks there is only one basic procedure for handling data points. Deviations from this for specific projects are implemented as variants, which can be selected when configuring the system (e.g. accepting the time tag, COT calculation etc.)

312 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Limitations and miscellaneous Number of PSF instances Only one PSF application can run per board. Type_ID of input data points All input data points must have the same Type_ID. Logically linking different data types (i.e. with different Type_ID s) in the same function block is not permitted. Signal race in the case of multi-stage processing When PSF modules are combined for multi-stage processing, signal race phenomena between input signals with different processing paths cannot be excluded. The time tags and/or or- not be as der of the resulting output signals may then expected. NOTICE: Careful choice of function variants may produce an improvement in such cases. Signal race resulting from non-observance of the chronological order of input data points Data points that are not received from the VME in the correct chronological order (e.g. due to discrepancies between the source devices) result in an incorrect chronological order of the outtags) and correct logical put data points (in relation to their time linking for general alarms is not assured. No feedback permitted Feeding output signals back to the inputs of function blocks (or a connected group of blocks) results in no output signals being generated at all (see Initiation of function blocks). Signal multiplication The processing of a data point by a PSF module always creates a new signal (with the PSF as source), which must be config- ured. All the data points at the output of a function block thererequire new internal fore addresses

313 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Engineering cost Signal processing by t he PSF application means additional configuration costs. Additional signals have to be defined that are then linked to input da ta points and function blocks Special requirements Basic PSF software The PSF application is included in the basic software and can be executed on every board (ISP/ISG). Supported function block types The following basic function blocks are available: Function Proc. mode Description Data type AND spont. cyclically Generation of general alarms Status OR spont. cyclically Generation of general alarms Status NOT spont. Signal inversion Status and SOE DISPATCHER spont. Signal multiplication Command, status and SOE CONVERT spont. Data type conversion Command, status and SOE PULSE spont. Generation of fleeting signals SOE TRASH spont. Signal suppression All SCALE spont. Multiplies the input signal by a constant Meas. variable Add spont. Sums the input signals Meas. variable Geometric_Add spont. Sums the input signals Meas. variable geometrically Complex_Add spont. Complex summation of the input signals Meas. variable Table 8.24 PSF: Basic function blocks Further details (function type and processing mode) are given in relation to the other requirements

314 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Supported processing modes Blocks that perform logical functions can operate either sponta- operate neously or cyclically. All the other blocks spontaneously. Spontaneous processing of data Processing is initiated by the reception of input signals via the VME or from other function blocks that processed or generated them. The output signals are entered in the process image and transmitted via the VME (see Transmitting telegrams below). Cyclic processing of data Function blocks that cyclically process data act on image cyclically at a preset rate. the process Transmitting telegrams (standard response) Providing a value, time or attribute change is detected in the result of processing and the data point is not an internal intermediate result (see Saving intermediate results below), the output data point is distributed throughout the system via the VME. Function blocks CONVERT, DISPATCH and PULSE send their output signals at the end of each processing routine to the VME (with the exception of intermediate results). The channel number for transmitting data points is the same as the channel via which the input telegram was received. Multi-stage processing PSF functions can be combined to multi-stage processing units providing there are no signal race problems

315 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Input1 Input2 Input3 Input4 PSF function A PSF function B Output1 Output2 Fig PSF functions combined for multi-stage processing Saving intermediate results Intermediate results, which are only used as input signals for other PSF function blocks and not transmitted via the VME, are configured as internal outputs for entry in the internal process image. Input1 Input2 Input3 Input4 PSF function A Internal_output1 PSF function B Output1 Fig PSF handling of intermediate results Fault tolerance With the exception of plausibility errors in the configuration, which are always a Major Error, all errors that are detected during operation generate an EVL output and the PSF application is set to Minor Error

316 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Description EVL output Error Data cannot be transmitted via the VME. Connection fault 50 IAL address not configured. Item not found 51 Type_ID not supported. Unknown Type_ID 52 IAL telegram could not be assigned to a function block (e.g. wrong Type_ID, Channel No. etc.). No configuration data available. Plausibility error in the configuration data. Plausibility error in a telegram (see conversion of signals with relative time tags, i.e. single indication). Conversion error (e.g. unknown COT etc.). Table 8.25 Response to errors Unhandled IAL message No configuration data Depends on plausibility error, see release notes. Depends on plausibility error, see release notes. Depends on error, see release notes Response during system start-up No configuration data PSF starts in the Minor Error status if there are no configuration data for the application. There is a response to status requests from the diagnostic function (DIA), but no other functions are activated. Plausibility check during start-up The plausibility of the function block configuration is checked during start-up with respect to the following: At least one input signal must be defined. At least one output signal must be defined (exception: TRASH). The function blocks CONVERTER, DISPATCHER and NOT may only process one input data point. The function blocks AND, OR, ADD, Geometric ADD, Complex ADD and NOT may only generate one output data point. The detection of a plausibility error causes an EVL output and sets the PSF application to Major_Error

317 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Internal PSF process image The PSF application stores all the data points that have been configured including time tag in the internal process image. The format used is an internal PSF representation of the IAL telegrams. Initializing data points All data points are set to zero. The quality attributes are at their default settings: IV = 1, SB = 0, BL = 0, NT = 0 and OV = 0 Initializin g function blocks The function blocks are in the Ready mode and can process in- data points. No output data points are generated until all the put input signals configured for the respective function block have been sent once by their sources (e.g. bay unit). The output signals are calculated when all the input signals have been set (regardless of value and quality attributes), entered in the internal process image and distributed throughout the system via the VME (excepting for an internal output which is not transferred via the VME, see Saving intermediate results). The PSF function block is set to Processing and operates in the configured mode Data processing Assigning input data points to functions An input signal can be processed by several PSF function blocks. Standard processing of input telegrams All IAL telegrams that have been configured (have defined IAL addresse s ) are processed according to the same procedure re- of data type and function block, gardless i.e.: Save input telegram in the PSF process image. Activate the function block(s) (event controlled) to generate the output signals. Save the output signals in the PSF process image. Make output signals available as input telegrams for other function blocks. Send output signals to the VME (see Transmitting telegrams (standard response) in Section above)

318 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Input telegrams can be received via the VME or be derived from PSF output signals (see Multi-stage processing in Section above). Time tagging (standard response) In the case of time tagged messages, the time tag of the output telegram is the same as that of the input telegram that activated processing (i.e. the last input telegram). Deviations from the standard response are defined as variants. Cause of transmission (standard response) PSF supports all IAL COT s. PSF does not process the COT, which in the output telegram corresponds to that of the input telegram causing the change of value, attribute or time tag. Quality attributes With the exception of when IV or BL and SB are set, the quality attributes of output data points are obtained by means of an OR logic of all the input data point attributes. Output data point attribute IV (invalid) NT (not topical) BL (blocked) Setting condition IV bit set in an input telegram NT bit set in an input telegram BL bit set in an input telegram Resetting condition All IV input bits reset All NT input bits reset All BL input bits reset SB ( not substituted) SB bit set in an input telegram and both IV output and BL output are reset Table 8.26 Setting quality attributes All SB input bits reset Function block variants Different variants of a basic function block can be selected for the same configuration. A variant is a slight departure in the processing procedure from the standard (see Table 8.33 Alternative processing modes by PSF function blocks)

319 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Queue overflow strategy PSF supports one of the following overflow strategies per channel: 1. Keep the Newest: After three unsuccessful attempts to send telegrams via the VME, PSF is set to Minor Error and the message is discarded and the failed attempts recorded in the EVL. The VME Application Input Queues continue to be polled. 2. Keep the Oldest: Polling of the VME Application Input Queues discontinues when telegrams cannot be sent via the same channel. There is therefore a queue of data back to the source. PSF is set to Minor Error and the failed attempts recorded in the EVL Status messages Processing status messages (Channel 2) Status messages are processed in the function blocks CON- VERT, DISPATCH, AND, OR and TRASH. Binary general alarms are obtained using AND, OR and dynamic OR logics. Converting double to single signals Converting single to double signals Multiplying telegrams Converting device statuses to warnings Converting device statuses to alarms Converting queue overflow in relation to device status OR logic for device status diagnostic messages Processing signals without a time tag All the function blocks process signals with time tags (Input_Type_ID = 140/141). Signals without a time tag, which are usually the result of general polling, are processed in the same function block and also generate an output data point. The time tag of an output telegram corresponds to that of an input telegram: 8-219

320 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Variant 0: Time tag of the last input telegram Variant 2: Time tag of the input telegram that resulted in change of value or attribute. If the corresponding input telegram does not have a time tag, the output telegram is sent without one (standard response). Time tagging signals In contrast to the response described in Processing signals without a time tag, the output signal of the PSF application is time tagged (CP56Time2a of TIM), if the process did not attach a time tag. This response is implemented in Variant 5 and 6 (see Function block variants in Section above) Measured variables Processing measured variables (Channel 2) Measured variables are processed in the function blocks CON- VERT, DISPATCH and TRASH. Refer to the paragraphs with the following headings for details: Converting 103 measured variables Type I Converting 103 measured variables Type II Multiplying telegrams Sequence of events (SOE) Processing SOE s (Channel 3) Data points received via the VME Channel 3 (SOE channel) can be processed in the function blocks CONVERT, DISPATCH, PULSE and TRASH. Refer to the paragraphs with the following headings for details: Generating fleeting signals Converting double to single signals Converting single to double signals Multiplying telegrams Converting device statuses to warnings Converting device statuses to alarms Converting queue overflow in relation to device status 8-220

321 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Commands Processing commands (Channel 1) Data points received via the VME Channel 1 can be processed by the function blocks CONVERT, DISPATCH and TRASH (see Generating command sequences and Converting single to double commands). No supervision of command runtimes PSF waits for the return confirmation of commands sent to the process (see Generating command responses below). Generating command responses Command responses (COT = 7, 9, 10, 48 and 49) are generated as a result of processing the respective commands and sent with the address IAL+1. The response is only sent if at least one re- confirmation per command has been received from the turn process. ACTTERM is also generated when all the responses from the process include a COT = ACTTERM. Converting the type of command responses The Type ID of the return confirmation is the same as the Input Type ID of the function block. Cause of transmission for command responses The COT of a return confirmation generated by the PSF is derived from the individual COT s of the process responses. Variant 3 sends a positive return confirmation providing the response to all the commands of a sequence is positive. Variant 4 generates a positive response when there is a positive response to at least one of the commands (possible application: commands to redundant bay units). The function block CONVERT forwards the COT from the process without processing it itself

322 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Return confirmation from process PSF response COT1 COT 2 to n COT Variant 3 COT Variant or or 9 or = COT 2 to n 49 7 or 9 or 10 or = COT 2 to n other 49 EVL output 49 EVL output Table 8.27 COT for the return confirmation of commands Processing command return confirmations A return confirmation from a command (COT = 7, 9, 10, 48 and 49) received via Channel 1 is only processed by the PSF application providing it can be assigned to a valid command and function block. Other return confirmations are lost (EVL output and Minor Error). Interlocked processing of commands All commands are temporarily saved by PSF to enable com- responses to be properly assigned to them. A new com- mand mand with the same IAL address is only then accepted, if it was possible to generate a command response for the initial command Transparent data Counts It is not planned for PSF to process transparent data at present. It is not planned for PSF to process counter statuses at present

323 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Basic functions Generating binary general alarms General alarms are only generated in response to statuses (VME Channel 2). The processing of quality attributes and COT s is described in Quality attributes and Cause of transmission (standard response). The time tag depends on which variant of the function block that has been configured: Variant 0 (standard): The time tag of the output data point corresponds to that of the input telegram that resulted in a change of value or attribute (see Time tag (standard response) and Dynamic OR logic). Variant 2: The time tag of the output telegram corresponds to that of the last input telegram, which caused a change of value or attribute (see Function block variants and AND/OR logic). Number of input signals included in a general alarm PSF can base a general alarm on any number of binary input signals. AND logic of status signals The response described is fulfilled by the standard AND function block. The setting of the time tag departs from the standard response and is defined as variant 2. A new general alarm is only generated, if a change in value or attribute is detected at the outputs of an AND gate of the input values and an OR gate of the attributes (see Quality attributes). Type_Id=140 Type_Id=140 Type_Id=140 Type_Id=140 Type_Id=140 Fig AND gate for binary input signals 8-223

324 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C OR gate of status signals The response described is fulfilled by the standard OR function block. The setting of the time tag departs from the standard response and is defined as Variant 2. A new general alarm is only generated, if a change in value or attribute is detected at the output of an OR gate of the input values and an OR gate of the attributes (see Quality attributes). Type_Id=140 Type_Id=140 Type_Id=140 Type_Id=140 Type_Id=140 Fig OR gate for binary input signals Dynamic OR gate for status signals The response described is fulfilled by the standard OR function block. The time tag is determined by every input telegram received and therefore corresponds to the standard response (see Time tag (standard response)). Thus every input telegram re- sults in a new general alarm, because of the change in time tag Generating diagnostic general alarms COM581 includes a logic that generates a warning based on deinformation derived from the various subsys- tailed diagnostic tems. Diagnostic general alarms are only generated for statuses (VME Channel 2). The processing of quality attributes and COT s is described under Quality attributes and Cause of transmission (standard response). Whether or not a time tag is attached depends on which variant of the function block has been configured: Variant 0 (standard): The time tag of the output telegram corresponds to that of the last input telegram (see Time tag (standard response)). Variant 2: The time tag of the output data point corresponds to that of the input telegram that resulted in the change of value or attribute (see Function block variants). Refer also to: 8-224

325 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Converting device statuses to warnings Converting device statuses to alarms Logic for sorting similar diagnostic information The PSF OR function block can base a general alarm on any number of similar diagnostic signals (Type_ID = 200). Similar diagnostic messages are those that transfer the same type of in- to formation EQL2. EQL1=0 and EQL1=3 and EQL1=4 define the device status (status of node) (see OR logic of device status diagnostic messages) EQL1=1 is redundant (bus line status) EQL1=2 is queue overflow Type_Id=200 Type_Id=200 Type_Id=200 Type_Id=200 Type_Id=200 Fig OR gate for diagnostic messages Setting Status_of_Node The status of node (SON) value in the output telegram results from an OR logic of the SON values of all the data points: Device status OR signals Running (0 Ready or Minor_ Error) when all the subsystems are running (Ready or Minor_Error). Device statu s OR signals Not running (1 Not Ready and Not Minor_Error) when one of the subsystems is no longer in the Ready or Minor_Error status

326 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C OR logic for Status_of_Node Input 1 Input 2 to N Output OR SON Input1 = SONInput1 = SON Input1 Initialization Major_Error Initialization; Minor_Error; Not_Ready; Ready Initialization; Minor_Error; Major_Error; Not_Ready; Ready Initialization Major_Error Minor_Error Minor_Error; Minor_Error Ready N ot_ready Not_Ready; Not_Rea dy Ready; Minor_Error Ready Ready Ready Last_Wish Last_Wish; Last_Wish Shutdown; No_State Shutdown Shutdown Shutdown No_State Other combinations Table 8.28 OR gate with Status_of_Node inputs No_State OR gate of device status diagnostic messages A new general alarm is only generated, if a change in value, attribute or time tag is detected at the outputs of an OR gate of SON values (see Setting the Status_of_Node) and an OR gate of the attributes (see Quality at tributes) and all the input data points contain a defined SON value (EQL1 = 0 or 3 or 4). EQL1, EQL3 and EQL4 are always zero in the output telegram

327 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Generating command sequences Refer to the paragraphs with the following headings: Generating command responses Cause of transmission for command responses Processing command return confirmations Interlocked processing of commands Command sequences A DISPATCHER function block is used to create command sein any order. Where the or- quences and the commands can be der of the commands has not been configured by assigning numbers, they are in ascending order of their IAL addresses. Command sequences are processed in two stages: Generation of the command sequences Processing and generation of the responses 1) Command direction: Generating a command sequence (COT = 6 and 8) Type_ID=46 DISPATCH 46 Type_ID=46 Type_ID=46 Type_ID=46 Type_ID= Command IAL = aa Command sequence IAL = bb... IAL = zz 2) Supervision direc tion: Generating the response (COT = 7, 9, 10, 48 and 49) Type_ID=46 Type_ID=46 Type_ID=46 Type_ID=46 DISP AT46 CH Type_ID=46 5. Return confirmation from process PSF response IAL = bb+1... IAL = zz+1 IAL = aa+ 1 Fig Generating command sequences 8-227

328 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Type conversion in general Converting 103 measured variables Type I A Type I 103 measured variable (IAL Type_ID = 163) is con- verted to fo ur scaled 16 Bit measured variables (IAL Type_ID = 11). How many measured variables (Type_ID = 11) are gener- ated depends on the value of the SQ_No, which defines the number of measured variables transferred to ASDU = 163. The quality attributes are derived from an OR gate of the attributes of the original measured variables (ER, OV) and QDS. There are not restrictions on the assignment of the output signals: 1 I L2, 2 U L1-L2, 3 P and 4 Q. Type_ID=163 CONVERT 163->11 Type_ID=11 (I L2 ) Type_ID=11 (U L1-L2 ) Type_ID=11 (P) Type_ID=11 (Q) Mapping 163->11 in relation to SQ_No Type_ID=163 SQ_No=1 COT IAL_Address=xx MVAL EROV MVAL EROV MVAL EROV MVAL EROV QDS Type_ID=11 SQ_No=1 COT IAL_Address=yy SVA_16 QDS_AAC IV=OR(ER,IV) NT=NT SB=SB BL=BL AAC=0 OV=OR( OV,OV) Type_ID=163 SQ_No=2 COT IAL_Address=xx MVAL EROV MVAL EROV MVAL EROV MV AL EROV QDS Type_ID=11 SQ_No=1 COT IAL_Address=yy SVA_16 QDS_AAC Type_ID=11 SQ_No=1 COT IAL_Address=zz SVA_16 QDS_AAC IV=OR(ER,IV) NT=NT SB=SB BL=BL AAC=0 OV=OR(OV,OV) Fig Converting 103 measured variables (Type I) Converting 103 measured variables Type II A Type II 103 measured variable (IAL Type_ID = 169) is converted to nine scaled 16 Bit measured variables (IAL Type_ID = 11). How many measured variables (Type_ID = 11) are generated depends on the value of the SQ_No, which defines the number of measured variables transferred to ASDU = 163. There are not restrictions on the assignment of the output signals: 1 I L2, 2 U L2, 3 U L3, 4 U L1-E, 5 U L2-E, 6 U L3-E, 7 P, 8 Q and 9 f. The telegram mapping is the same as converting 103 measured variables Type I

329 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Type_Id=169 Type_Id=11(I ) L1 Type_Id=11(I ) L2 Type_Id=11(I ) L3 Type_Id=11(I ) L1-E Type_Id=11(I ) L2-E Type_Id=11(I ) L3-E Type_Id=11(P) Type_Id=11(Q) Type_Id=11(f) Fig Converting 103 measured variables (Type II) Converting single to double signals (indications) The CONVERT function block generates a DPI signal in respons e to an SPI signal it receives via Channel 2 or 3. The DPI signal is transmitted via the same channel. Intermediate DPI position s (00, 11) are not transmitted. Converting double to single signals (indications) There are two possible procedures for converting double signals. In both ca ses, the CONVERT function block is used with either one or two output data points. In the first case, the semantic significance of the DPI value (input or output) is converted to an SPI value. Intermediate DPI positions (00, 11) do not generate any new SPI telegrams. In the second case, the individual Bits of a double signal are transferred as two independent single signals. Type_Id=141 Type_Id=140 DPI value SPI value 01 (OFF) 0 (OFF) 10 (ON) 1 (ON) Fig Converting a double to a single signal 8-229

330 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Type_Id=140 Type_Id=141 DPI value SPI-1 SPI2 01 (OFF) 0 (OFF) 1 (ON) 10 (ON) 1 (ON) 0 (OFF) (OFF) (ON) Fig Converting a double to two single signals Converting single to double commands and vice versa The CONVERT function block is used for both directions, but with a different Input/Output_Type_ID configuration (45 46 and 46 45). Conversion only involves changing the SCO DCO and the IAL address. The type has to be converted in the case of the command responses. Type_Id=46 Type_Id= DCO value SCO value 01 (OFF) 0 (OFF) 10 (ON) 1 (ON) Fig Converting a double to a single signal Converting Select before operate to Direct command The CONVERT function block is used and both single and double commands (45 45, 46 46) are supported. During conversion, the PSF application returns the SELECT as soon as it is received and then the EXECUTE is forwarded. This applies for both SCO SCO and DCO DCO. The type has to be converted in the case of the command responses

331 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Type_Id= CONVERT 45 -> > 46 Type_Id= Type_Id= E RT CONV 45 -> 46 -> Type_Id= NCC PSF IBB Select Selected Execute Excecute Executed Executed Fig Converting Select before operate to Direct command Converting device status to warnings A warning is generated when an error has occurred (Minor_Error) which does not impair the operability of the device. Status = Ready is transferred as SPI = 0 (not a warning), while all other SON values count as warnings. This response is im- plemented as Variant 7 (see Function block variants)

332 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Type_Id=200 Type_Id=140 <= IAL tele gram Type_ID=200 VSQ COT IAL_Address=xx EI EQL1=0, 3, 4 EQL2 EQL3 EQL4 CP56Time2a Type_ID=140 VSQ COT IAL_Address=yy IV NTSBBL CP56Time2a SPI=0 when EQL2=Ready SPI=1 for all other EQL2 values QDS Fig Generating a device status warning Converting device status to an alarm In contrast to converting the device status to a warning, SPI = 1 is only set when the device can no longer operate (SON READY or Minor_Error). This response is implemented as Variant 8 (see Function block variants). Converting a queue overflow to device status When a generic queue overflow signal has to be converted to a device status, Input/Output Type ID = 200 is set in the CON- VERT function block. This response is implemented as Variant 9 (see Function block variants). INPUT OUTPUT EQL1 EQL2 EQL3 EQL1 EQL = overflow 0 Minor_Error = no overflow 0 Ready other 0 No_State Table 8.29 Converting diagnostic messages (Variant 9) 8-232

333 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Converting Bus_Line_Status to a double signal When a BLS diagnostic message is converted to a DPI, the high value Bit is set to equal LAT and OLD is transferred to the LSB. This response is implemented as Variant 11 (see Function block variants). Type_Id=200 Type_Id=141 Type_Id=200 VSQ COT IAL _Address=xx EI EQL1=1 EQ L2=LA T EQ L3=OLD EQ L4 CP56Time2a Type_Id=140 VSQ COT IAL_Address=yy IV NTSBBL CP56Tim e2a DPI=2*LAT+OLD QDS Fig Converting Bus_Line_Status to a double signal Converting Bus_Line_Status to a single signal When a BLS diagnostic message is converted to two single signals. The value of SPI is set either to LAT of OLD depending on the sequence number (output parameter). This response is implemented as Variant 11 (see Function block variants)

334 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Type_Id=200 Type_Id=140 Type_Id=140 SPI=LAT SPI=OLD Fig Converting Bus_Line_Status to two single signals INPUT OUTPUT EQL1 EQL2 EQL3 SPI_1 SPI_2 1 LAT=0 1 OLD=0 1 LAT OLD Table 8.30 Converting BLS diagnostic messages (Variant 11) Conversion of relative time signals to single signals Relative time signals are generated by an IEC103 master application and transferred via VME Channel 3 (SOE). The CON- VERT function block in the PSF module can convert them into single time tagged signals (SOE). Since IEC103 relative time signals are not included in the process image (i.e. they are not polled), but need to be part of the general polling procedure for other (user-specific) applications, Variant 1 makes provision for obtaining a status signal from the SOE which is transferred via Channel 2. The intermediate statuses of double signals cannot be converted and result in a Minor_Error (190)

335 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Variant 0: Type_ID=162 CONVERT 162->140 Type_ID= Variant 1: Type_ID=162 CONVERT 162->140 Type_ID= Ty pe_id= 162 VSQ COT IAL_Address=xx DPI RET FAN Type_ID=140 VSQ COT IAL_Address=yy IV NTSB BL CP56Time2a DPI value 01 (OFF) 10 (ON) SPI value 0 (OFF) 1 (ON) Minor_Error Minor_Error CP56Time2a QDS Fig Two alternatives for converting relative time signals Other functions Generating fleeting signals Fleeting signals produced by the process can only be input events and are transferred via VME Channel 3 (SOE). The PULSE function block in the PSF module can generate an output event (Variant 0) and two status signals (Variant 1). After converting the address (IAL1 IAL2), the input event is transferred to the VME and then an output signal is generated. The time tag offset for the output event can be selected in the range s. The function blocks guarantee the order of the events and status signals (1 input and 2 output)

336 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Variant 0: Type_ID=141 PULSE 141 Type_ID= config. duration Variant 1: Type_ID=141 PULSE 141 Type_ID= config. duration Fig Two alternatives for generating fleeting signals Inverting signals The NOT function block inverts the value (00 11, 01 10, 10 01, 11 00, 1 0 and 0 1) of any signal (status and/or SOE). A new data point is created which is sent via the same channel that the input telegram was received. Type_Id=141 Type_Id=141 Fig Example of signal inversion Suppressing signals Although relatively seldom, it is sometimes necessary to suppress signals. This is the case, when the source application only permits a message to be suppressed with functional restrictions, e.g. an MVB application does not transfer any process data from the bay unit unless a SON data point has been configured. If these signals should not be sent via an external connection, the TRASH function block in the PSF can suppress it

337 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Multiplying telegrams The DISPATCHER function block is used to send an IAL tele- No con- gram to several addresses via an external connection. version or evaluation of data is involved. The IAL telegram that has been received is forwarded multiple times, each time with a new IAL address (depending on the number of output data points that have been configured) via the VME. Multiplication of commands (see Generating command sethe quences) is a special case. Filtering SOE s The DISPATCHER function block provides facility for suppressing SOE s (Channel 3) when their values change. Neither quality attributes nor the time tag is taking into account. Thus SOE s are only transferred when a positive or negative-going edge is detected (0 1 or 1 0). A status signal (Channel 2) is forwarded unfiltered. Changing the scale of signals This function block changes the scale of measured variables. Th e scaling factor is a fraction, which may also be negative. Only this block responds to it although it can be configured for other blocks. In Scaling SCALE Out = In Scaling _ Factor Out Fig Function block for changing the scale of measured variables Adding signals This function block adds measured variables. The two inputs In1 and In2 are identical and several inputs can be defined

338 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Addition Out = In 1 + In 2 In 1 ADD Out In 1 Fig Function block for adding measured variables Geometrically adding signals This function block geometrically adds measured two inputs In1 and In2 are identical. Geometric Addition variables. The In 1 Out = In 1 + In GEOMETRIC _ADD Out In 1 Fig Function block for geometrically adding measured variables Complex addition of signals This function block adds measured variables in complex notation

339 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd I 1 P 1 Q 1 Complex Addition COMPLEX_ADD } Phy1 sin cos ϕ1 ϕ1 Q1 = = S 1 P1 = = S P 2 1 P Q 1 + Q P 1 + Q I out I 2 I = + out 2 2 ( I1 _ 2_ WIRK ) ( I1_ 2_ BLIND ) P 2 Q 2 } Phy2 Fig = I 2 2 ( I1 cos ϕ 1 + I 2 cos ϕ 2) + ( I1 sin ϕ1 + 2 sin ϕ 2) = I + I + I ( sin sin cos ϕ 2 cos 1 2) 1 ϕ + ϕ ϕ I1 2 Function block for adding measured variables in complex notation Inputs I, P and Q are not the same. When engineering a project using the CAP581 tool, care must be taken to configure the inthe following puts using the parameter Signal_Attributes in the order given in table: Input Signal port I 1 1 P 1 2 Q 1 3 I 2 4 P 5 2 Q 2 6 Table 8.31 Assignment of signal ports to inputs Only this function block uses this parameter. Its default setting for all other parameters is zero Overview of the function blocks Refer also to: Supported function block types in Section Supported processing modes in Section

340 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Function block Number of inputs/outputs Input_Type_ID Output_Type_ID Variants AND 1 N / (SPI with TT) Output_Type_Id = 0, 2, 5, 6 Input_Type_Id OR 1 N / (SPI with TT), Output_Type_Id = 200 (DIA with TT) Input_Type_Id 0, 2, 5, 6 NOT 1 / 1 140, 141 (SPI/DPI with TT) Output_Type_Id = Input_Type_Id 0, 5 CONVERT 1 / (SPI with TT) 141 (DPI with TT) 0, 5 1 / (DPI with TT) 140 (SPI with TT) 0, 5 1/1 200 (DIA with TT) 200 (DIA with TT) 9 1 / (DIA with TT) 140 (SPI with TT) 7, 8, 11 1 / 1 45 (SCO) 46 (DCO) 0 1 / 1 46 (DCO) 45 (SCO) 0 1 / 1 45 (SCO) 45 (SCO) 0 1 / 1 46 (DCO) 46 (DCO) 0 1 / (Meas I) 11 (SVA_16 QDS) 0 1 / (Meas II) 11 (SVA_16 QDS) 0 1 / (DIA with TT) 141 (DPI with TT) 11 1 / (RelTime) 140 (SPI with TT) 0, 1 1 / 1 N 1 / 1 140, 141, 200, 210 Output_Type_Id = Input_Type_Id 0, 5, 10 DISPATCH 1 / n n / 1 45, 46, 101 Output_Type_Id = Input_Type_Id 3, 4 PULSE 1 / 1 140, 141 Output_Type_Id = Input_Type_Id 0, 1 TRASH 1 / 0 alle keine 0 SCALE 1 / 1 11, 12, 13 Output_Type_Id = Input_Type_Id ADD N / 1 (N = 255) 11, 12, 13 Output_Type_Id = Input_Type_Id 0 0 Geometric_ ADD Complex_ ADD 2 / 1 11, 12, 13 Output_Type_Id = Input_Type_Id 6 / 1 11, 12, 13 Output_Type_Id = Input_Type_Id Table 8.32 Function blocks

341 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Variant Description 0 No departure from the standard processing procedure (see Processing input telegrams (standard response) in Section ) 1 When an input telegram is received via channel 3 (SOE), the output signal is sent via channels 2 (status) and 3 (SOE) (e.g. generation of fleeting signals, see Generating fleeting signals in Section ). 2 The time tag of the output data point is the same as that of the input telegram that resulted in a change of value or attribute (see Section Generating diagnostic general alarms ). 3 Special processing of the COT of the return confirmation (see Cause of transmission for command responses in Section ). 4 Special processing of the COT of the return confirmation (see Cause of transmission for command responses in Section ). 5 Time tagging of output telegrams when the last input telegram has not got a time tag (see Time tagging signals in Section ) 6 Time tagging of output telegrams when the input telegram that resulted in a change in value or attribute has not got a time tag (see Time tagging signals in Section ) 7 Special conversion of diagnostic messages (see Converting device statuses to warnings in Section ). 8 Special conversion of diagnostic messages (see Converting device statuses to alarms in Section ). 9 Special conversion of diagnostic messages (see Converting queue overflows in relation to device status in Section ). 10 Special SOE filter (see Filters for SOE s in Section ). 11 Special conversion of bay control diagnostic messages (see Conversion of Bus_Line_Status into double signals and Conversion of Bus_Line_Status into single signals in Section ). Table 8.33 Alternative processing modes by PSF function blocks 8-241

342 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Type ID Description 1 Single point information 3 Double point information 11 Measured variable value 16 Bit 12 Measured variable value Measured variable value 32 Bit (Short Float) 45 Single command 46 Double command 101 Count interrogation command Bit 140 Single point information with time tag 141 Double point information with time tag 162 Message with relative time 163 Measured variables 1 (blocking of measured variables in one phase I, V, P, Q) 169 Measured variables 2 (blocking of measured variables in three phases I, V, P, Q, f) 200 Diagnosis information with time tag 210 Diagnosis information Table 8.34 Available function input and output type ID s 8-242

343 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Engineering a PSF using the import function The signal list provides facility for configuring functions for the specific project and then to automatically import them into CAP581. As with the other protocols, the hardware, i.e. a PSF application, has to be added to the project database. The columns below PSF Protocol Data (violet) are color coded, the colors signifying: GREY General data that are always needed for the functions and signals. LIGHT GREY Special data only needed for signals. VIOLET Special data only needed for the functions. Table 8.35 Columns used when configuring a PSF Creating a PSF application A PSF application can be created on ISP and ISG boards. A PSF application is automatically added when selecting a VME device below the desired board. Fi g Structure after adding a VME device Insert new object No Delete object Yes 8-243

344 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Remove link No Properties Fig Specific tab of the PSF Application properties dialogue with the PSF attributes Application ID Range: Default: Allocated while adding object. Description: Unique identification of the application within the COM581 system. Allocated in ascending order in increments of one and can then be reset Configuring a function in the signal list The various functions are configured directly in the signal list and added by the import function. A function necessitates filling in a line in the Excel table. The general part below Technical Signal Description comprises the columns Station, Bay and Device name, which was also the case with the other protocols. The part for the specific application PSF Protocol Data includes the grey and violet columns. Fig Line 4 defines a complete OR logic 8-244

345 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Fig OR logic after being imported Properties Fig Specific tab of the Alarm properties dialogue with the PSF function attributes Function Name Range: AND; OR; PULSE; TRASH; NOT; DISPATCHER; CONVERT; SCALE; ADD; GEOMETRIC ADD; COMPLEX ADD Default: AND Description: Name of the basic function, see Section Function Type Range: Default: Description: Cyclic; Event Driven Event Driven Scanning Cycle Time (s) Range: Default: 0.0 Description: 8-245

346 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Input Type ID Range: 1 Single Point Info 3 Double Point Info 11 Measurand Value 16 Bit 12 Measurand Value 32 Bit 13 Measurand Value 32 Bit (Short Float) 45 Single Command 46 Double Command 101 Count Interrogation Command 140 Single Point Info with Time 141 Double Point Info with Time 162 Message with relative Time 163 Measurands Measurands Diagnosis Info with Time 210 Diagnosis Info Default: 141 Double Point Info with Time Description: Output Type ID Range: Default: Description: as for Input Type ID as for Input Type ID Function Variant Range: Default: 0 Description: Special variants of the basic functions can also be selected (see Section Overview of the function blocks ). Scaling Factor Range: Default: Description: This attribute is only needed for the scaling function. NOTICE: From Version 4.80 onwards, it is sufficient to enter just the number for the attributes PSF FUP Input Type and PSF FUP Output Type. NOTICE: The default values are used when importing the data in the case of cells for which nothing has been entered

347 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Configuring function input and output signals One line of the Excel table has to be filled in for each input and output signal. The general part below Technical Signal Descrip- prises the columns Station, Bay, Device name, Signal tion com Name and Signal Type, which was also the case with the other protocols. The part for the specific application PSF Protocol Data includes the grey and bright blue columns and the data for a source or a sink protocol (see Section 7.2.). Fig Lines 5 to 7 define two input and one output signal for the OR logic added in Section

348 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Fig The PSF Application signals after being imported Fig The linked imported signals in the signal tree 8-248

349 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Schematic illustration of PSF engineering procedure "link points" PSF Application LON, MVB,... Source 1 2 Function Sin k Inputs Outputs Source Sink (AND, OR,...) IEC101, RP57x,... Fig Schematic of the engineering procedure for the PSF signals The figures below refer to the various points in the CAP581 figure above and originate from the example in Section Source signal (location structure) LON/PSF signal link (signal tree) Sink signal (location structure) Function inputs (within the PSF function) Possible connections in the PSF application 8-249

350 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Function outputs Source signal (location structure) PSF/IEC101 signal link Sink signal (location structure) 8-250

351 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Manually engineering a PSF Creating a PSF function Click the right mouse button on the PSF FUP object to open the context menu and select Insert new object to create a new function. The attributes for this object are described in Section Configuring an inversion In this example, an inversion of the CAP581 signals is described. Problem: A single point indication in a bay unit has to be inverted and sent using the IEC101 protocol to the remotely controlled station. The following data points and signal versions have to be created: 1 LON (source) signal 1 PSF (sink) signal 1 PSF (source) signal 1 IEC101 (sink) signal 2 Signal versions in the signal tree Fig Creating a single LON indication 8-251

352 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Fig Creating a PSF sink data point Fig Creating a PSF source data point Fig Creating an inverted IEC101 single indication 8-252

353 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Fig Creating the two signal version normal and inverted The following settings are necessary: Fig Address tab of the LON Source Single Indication properties dialogue for the LON data point Fig Address tab of the LON Sink Indication properties dialogue for the IEC101 data point 8-253

354 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Fig Specific tab of the PSF Function properties dialogue The following links must now be configured: Fig Linking the PSF signals in the PSF function block Fig Linking the four data points in the signal tree 8-254

355 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Engineering a PSF by importing data Fleeting signals, command sequences and conversion The examples in this section are presented without further comment as they are discussed in detail in Section 7.2. Fig General and LON parts Fig Protocol part 8-255

356 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Fig PSF configuration Fig Overview of the function blocks 8-256

357 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Fig Fleeting signals (signal tree) Fig Command sequence (signal tree) Fig Conversion of data types (signal tree) 8-257

358 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Introduction to engineering a PSF for neutral current Function Number of inputs/ outputs Description SCALE 1 / 1 Multiplies the input signals by a constant Add 1...n / 1 Sums the input signals Geometric_ Add 2 / 1 Geometrically sums the input signals (90 between In1 and In2) Complex_Add 6 / 1 Complex addition of the input signals Neutral current 10 / 6 Combination of the above function blocks (see Fig ) Table 8.36 Overview of the neutral current scheme General explanation The five examples of the new PSF functions, which now follow, give an insight into the engineering procedure. Each block is shown on its own first and then their combination to determine the neutral current of two bays. The attribute PSF Signal Port is only needed for the input signals of the COMPLEX ADD block. All other signals are set to zero. The attributes PSF Sequence No. und PSF FUP Function Variant are set to zero for all four function blocks. Only measured value signals are permitted. In the case of Technical Signal Description: INT and DINT, and in the case of PSF Protocol Data: Measurand Value 16 Bit, 32 Bit and 32 Bit (short float) Example of scale adjustment In Scaling Out = In Scaling _ Factor Out Fig Scaling function block 8-258

359 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Excel table: Fig A block comprises three lines CAP581 structure: Fig Location structure Fig Signal tree Properties PSF Application ID Must be set the same for all lines. PSF Application Caption Must be set the same for all lines. PSF Sequence No No influence (default 0) PSF Entry Type Definition mandatory PSF Signal Port No influence (default 0) PSF FUP Function Name Definition mandatory PSF FUP Scaling Factor Definition mandatory (zero not permitted) 8-259

360 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C PSF FUP Function Type Definition mandatory PSF FUP Scanning Cycle Time Definition mandatory for Fct. Type = Cyclic PSF FUP In- Output Type Definition mandatory (Types 11, 12 and 13 only) PSF FUP Function Variant No influence (default 0) Example of addition Addition Out = In 1 + In 2 In 1 Out In 1 Fig Addition function block Excel table: Fig A block comprises four lines CAP581 structure Fig Location structure 8-260

361 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Fig Signal tree Properties As Section Example of Geometric Add Geometric Addition In 1 Out = In 1 + In Out In 1 Fig Geometric Addition function block Excel table: Fig A block comprises four lines 8-261

362 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C CAP581 structure: Fig Location structure Fig Signal tree Properties As Section NOTICE: A typical application of this function block is the calculation of the apparent power S from the active and reactive power components (P and Q). NOTICE: A second typical application is the calculation of the impedance Z from the resistance R and the reactance X

363 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Example of Complex Addition Signal Port I 1 P 1 Q 1 Complex Addition } Phy1 sin cos ϕ1 ϕ1 Q1 = = S 1 P1 = = S 1 Q P + Q 2 1 P P + Q I out 4 I 2 I = + out 2 2 ( I1 _ 2 _ WIRK ) ( I1_ 2_ BLIND ) 5 6 P 2 Q 2 } Phy2 = I 2 2 ( I1 cos ϕ 1 + I 2 cos ϕ 2) + ( I1 sin ϕ1 + 2 sin ϕ 2) = I + I + I ( sin ϕ 1 sin ϕ 2 + cos ϕ1 cos ϕ 2) I1 2 Fig Complex Addition function block Excel table: Fig A block comprises eight lines CAP581 structure: Fig Location structure 8-263

364 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Fig Signal tree Properties As Section

365 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Example of the neutral current function 6 Scaling Units 3 Complex Addition Units I 1_R I R_Out I 1_S I 1_T I 2_R I S_Out I 2_S I 2_T I T_Out P 1 P 2 2 Addition Units P out Q 1 Q out Q 2 S out 1 Geometric Addition Unit Fig Block diagram of the scheme for determining the neutral current Excel table: This composite block comprises at least 36 lines and depending on the number of scaling blocks used, another 18 (30) lines can be necessary

366 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Fig PSF part of the signal list 8-266

367 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Fig General and LON parts of the signal list 8-267

368 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Fig CAP581 structure in the Location Structure view Fig CAP581 structure in the Signal Tree view Properties As Section

369 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd July Finalizing 9.1. Generating the download database ( Builder ) Starting the Builder function Builder error messages Data consistency checks Documentation Create signal list Create specific report Starting the configuration program Configuring a specific user report file Configuring a page in the report file Copying and moving existing projects

370 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C 9. Finalizing 9.1. Generating the download database ( Builder ) Now that all the data have been imported into the CAP581 tool and all the settings have been made, the download file for COM581 can be generated. The Builder function creates an MS Access database from the CAP581 database, which is downloaded to the target COM581 using the DIS581. After the database has been created, check its consistency. The name of the download file and the version of the database model are entered together with the settings for the COM581 (see Fig. 9.1) in the COM581 properties dialogue. NOTICE: For IEC61850 projects this name is set automatically to the name of COM581 IED and should not be changed. For such a project Builder creates also a CCF file with the same name as download database. The both files are later uploaded into the COM581 device. Fig. 9.1 Download tab in the COM581 properties dialogue for entering the Download file name and database model version 9-2

371 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Attribute Download table Remarks Enter the MS Access file for downloading to the target COM581. Target data model Table 9.1 Builder settings There are no restrictions on the name. Available settings: 3.0 for basic COM581 SW release 3.0 (not supported) 4.0 for basic COM581 SW release 4.0 (not supported) 4.5 for basic COM581 SW release for basic COM581 SW release 4.6x and for basic COM581 SW release 4.7x 4.8 for basic COM581 SW release 4.8x and 4.7x 4.9 for basic COM581 SW release 4.9x (not supported)5.0 for basic COM581 SW release 5.0x 5.1 for basic COM581 SW release 5.1x 6.0 for basic COM581 SW release 6.0x Starting the Builder function The Builder takes a few minutes to create the file and the following influences the operation: Number of signal links configured Programs running in the background on the PC Available PC main memory PC performance Start the build operation by pressing Alt + C or clicking the right mouse button on a plant object (second hierarchical level) in the signal tree view and selecting Build All from the context menu. Fig. 9.2 Generating the download database The build process can be discontinued by clicking on the Cancel button on the progress bar display. 9-3

372 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Fig. 9.3 Progress of the building operation Fig. 9.4 Info box when the build operation has finished with any errors Fig. 9.5 Info box when the build operation has finished without any errors The download database has been created in the directory \Project\Builder Builder error messages After the build operation has finished, the CAP581 tool provides facility for viewing any error messages and warnings by selecting Messages / Builder / (see Section Data consistency checks ). Project information including the COM581 release to which the database belongs is displayed. 9-4

373 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Fig. 9.6 Error messages generated by the download file builder Data consistency checks The consistency checks are performed immediately after the build function has finished. They determine whether errors were made or anything omitted during the database engineering procedure. A list of the respective messages is given in Section NOTICE: For IEC61850 projects when Builder creates the CCF file, it writes the internal COM581 (IAL) into it. It can happen that not all of the signals automatically created in the Signal List were imported into the CAP581 tool. In this case the Builder will generate warnings saying that it did not found the IAL addresses for some data points. This is the case of discrepancy between the CAP581 database and what is the Input Section of the CCF file. These warnings can be ignored if COM581 effectively will not use all of the available signals. NOTICE: Do not download the database to the COM581 before the consistency checks run without error messages. NOTICE: It is, however, permissible to download the database to the target COM581 if only warnings are displayed. 9-5

374 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C 9.2. Documentation Project documentation By using the contents of COM581 database for the documentation, the consistency of the documentation with the actual state is assured. Parameter lists, signal lists and function plans of the graphically created software are at all times based on the current status of the project database and therefore consistent in every respect. The information for the documentation is obtained from the signal import lists that have been created. Provision is made for exporting the project data to two types of files: Signal list (see Section Create signal list ) Specific report (see Section Create specific report ) Fig. 9.7 Creating signal lists and reports 9-6

375 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Create signal list Signal list data are available as Excel and Access files. In each case just the data are exported that are required for an import operation. The version of the signal list file is the same as that of the current CAP581 version. The files are stored in the directory \Project\ExportData. Fig. 9.8 Signal list directory Click on No in the following. Fig. 9.9 Caution message, which is acknowledged by clicking on No (default) 9-7

376 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Create specific report Starting the configuration program Using the auxiliary program Configurator supplied with the tool, it is possible to customize a report. Select Report Configurator in the Tools menu to start it. Fig Report Configurator in the Tools menu Fig Report Configurator window Configuring a specific user report file The menu item Report in the Configure menu opens the dialogue for configuring a report file (see Fig. 9.13), which permits the pages to appear in the report to be selected. Fig Select Report in the Configure menu 9-8

377 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Fig Dialogue for configuring a report file Configuring a page in the report file Select Sheet in the Configure menu to open the dialogue for configuring the pages (sheets) of a report (see Fig. 9.15), which permits the information to be selected for inclusion in the tables on a page. This is done by selecting each parameter and dragging it down with the mouse to the table list. The default column headings, which are inserted automatically, can be edited as necessary. The heading, however, is mandatory in order to generate the table. Fig Select Sheet in the Configure menu 9-9

378 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C Fig Dialogue for configuring the pages (sheets) of a report NOTICE: The Caption cell has to be filled in for each addition to the table list (replace default) Example of a special report (not currently applicable) The data to be included in the report are available in Excel and Access files and saved in the directory \ExportData\Report\. Fig Files report A report (Excel or Access table) exists for every data type and protocol that has been configured. Signal Name Bay Name Customer Signal Text Common Address of ASDU Information Object Address CMD REC Other CMD REF Other Command Type Fig Commands report 9-10

379 CAP581 1MRB Uen/Rev. C ABB Switzerland Ltd Signal Name Bay Name Customer Signal Text Common Address of ASDU Information Object Address IEC101 Data Type SF6 REC Indication POS REC Indication I1 REC Measured_Value U1 REC Measured_Value CMD REC Command SF6 REF Indication POS REF Indication I1 REF Measured_Value U1 REF Measured_Value CMD REF Command Fig IEC101 addresses and types report Common Informatio Sequential Suppress Address n Object Indicati Event Intermediate Signal Name Bay Name Customer Signal Text of ASDU Address on Type Recording State SF6 REC Single Both False POS REC Double Both False SF6 REF Single Both False POS REF Double Both False Fig Signal report Common Address of ASDU Information Object Address Scaling Factor Measurand Type Signal Name Bay Name Customer Signal Text I1 REC Scaled U1 REC Scaled I1 REF Scaled U1 REF Scaled Fig Measured variables report Copying and moving existing projects The project directory tree has a pre-defined structure and the all project files are stored on predefined places. When project has to be copied or moved, the whole tree has to be moved to keep the consistency of the project. The names of the files in a project follow the naming conventions and should not be changed. The following picture shows an example of project directory after a build with the following files: 9-11

380 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. C 1. IAL mapping database used for SCD file processing; (only IEC61850) 2. CAP581 tool database file 3. Project s Signal List 4. File containing the CAP581 tool version 5. Temporary file used for CCF file creation; (only IEC61850) 6. Builder Log file (Contains erros and warnings of last build) 7. CCF file for COM581 device; (only IEC61850) to be loaded into COM581 device. 8. Database for COM581 device) to be loaded into COM581 device. 9. Work file used for possible reports 10. Work file used for possible reports 11. Work file used for possible reports Fig CAP581: Files in a new created project directory NOTICE: Files 1-4 are created during a project creation. File 5 is created during an SCL import (only IEC61850) Files 6-11 are created during a build of the project. In IEC61850 projects the file 7 and 8 get name from imported SCD file according to the COM581 IED name. 9-12

381 CAP581 1MRB Uen/Rev. B ABB Switzerland Ltd August Example of a project Configuration Signal engineering definitions Open new project Configuring LON Configuring the master board (IMP) Add the LON bay units Configuring IEC Configuring the slave board (ISG) Adding a serial link Adding the IEC101 application Adding the PSF application Synchronizing system time Tree structure Engineering the signals LON part IEC101 part PSF Diagnosis messages Importing the signal list Tree structure after the import operation Configuring the measured variables Building and downloading the database

382 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. B 10. Example of a project The figure below shows a simple example of a project. The problem is to link two LON interbay bus controllers to the power system control centre via a COM581. The protocol to be used for communication with the power system control centre is IEC The synchronization of system time is performed by the LON star-coupler. Station TEST NCC COM581 Protocoll converter Power Supply 500PSM03 BIO 1 BIO 2 Slot 1 Power Supply 500PSM03 BIO 1 BIO 2 Slot 20 LON 500CPU03 SMC3 LAN CH 1 CH 2 Slot 4 IEC CPU03 Star Coupler SFIBER MM SFIBER MM SFIBER MM SFIBER MM Rx Tx Rx Tx Rx Tx SMC3 LAN CH 1 CH 2 Rx Tx Rx Tx Rx Tx Rx Tx Rx Tx Rx Tx Rx Tx Rx Tx Rx Tx FOC 1 FOC 2 FOC 3 FOC 1 FOC 2 FOC 3 Slot 7 FOC 1 FOC 2 FOC 3 FOC 1 FOC 2 FOC 3 Rx Tx Rx Tx RER111 Star coupler LON GPS Meinberg 167SV/UAT/2T/1R/BGT Slot 1 Star Coupler Star Coupler Star Coupler Slot 2 Slot 3 Slot 4 Star Coupler SFIBER MM Slot 9 COM0 RS232 COM1 RS232 PPS1 Tx COM2 Tx Rx Antenna Koax Rx Tx Rx Tx Rx Tx Rx Tx Rx Tx FOC 1 FOC 2 FOC 3 serial PI Slot 5 PO Rx Tx Rx Tx Clock Master SLCM-FO MM BAY A Control/Supervision -A201 CONTROLLER REC316*4 Steuerung/ Überwachung Messung Tx Rx BAY B Control/Supervision -A201 CONTROLLER REC316*4 Steuerung/ Überwachung Messung Tx Rx Fig Block diagram for the project example 10-2

383 CAP581 1MRB Uen/Rev. B ABB Switzerland Ltd Configuration Number of protocols 2 Signal volume Station bus protocol Remote control protocol IMP slot ISG slot ISP slot Radio clock Time master (in COM581) Time slave (in COM581) Number of devices connected to the interbay bus 2000 per line LON IEC No. 4 for LON No. 7 for IEC101 None Installed on RER111 VME-BUS to IMP No.4 VME-BUS to ISG No.7 IEC101 LON-BUS to IMP No.4 LON devices connected to the bus COM581 Node ID 126 Subnet 1 REC316 Node ID 10 Subnet 5 REC316 Node ID 12 Subnet 5 Interface parameters to be set Table 10.1 Configuration parameters Signal engineering definitions 3 Default settings for IEC101 and LON. Details of the various protocol settings are given in Section 8. In order to illustrate the principle, only typical signals are configured in this example. The database contains the following signals: Significance Cranking handle inserted Miniature circuit-breaker general alarm Circuit-breaker position Q0 Command for Q0 Power measurements Bay unit status (communication alarm) COM581 synchronization error Type Single Point Information (SPI) Single Point Information (SPI) Double Point Information (DPI) Command (CMD) Measurement (DINT) Status of Node (SON) Status of Node (SON) Table 10.2 Signal types All the signals originate from the LON bus and are transferred to the IEC101 bus. The general alarm for the miniature circuit- 10-3

384 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. B breaker is provided by a PSF. The Q0 command is transferred from the IEC101 bus to the LON bus Open new project Select New in the Project menu to create a new database with the following structure: Fig Basic structure for a new project The above structure already exists when a new project is created from a template. 10-4

385 CAP581 1MRB Uen/Rev. B ABB Switzerland Ltd Configuring LON Configuring the master board (IMP) The first step is to add a LON device to the master board (IMP). As far as the LON bus is concerned, this device is the COM581 itself. Fig Adding a LON device The procedure for setting the LON protocol parameters is described in detail in Section 8. For this example, just the procedure for setting the COM 581 parameters Subnet and Node ID is shown. For this purpose, click the right mouse button on the LON application to open the following dialogue: Fig Specific tab of the LON Application properties dialogue for defining the Subnet and Node ID for the COM

386 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. B Enter the specific project address for the parameter for the value of User-defined Subnet and Node ID. In this example, this is Subnet 1 and Node 126. Subnet and Node ID are rewritten automatically in the neuron chip in the COM581 every time the system is started and initialized Add the LON bay units To enable COM581 to communicate with all the LON devices connected to the station bus, its Subnet und Node ID has to be defined. Fig Adding a new LON object A LON device always comprises a LON node and the associated logical device. Fig Adding a LON node 10-6

387 CAP581 1MRB Uen/Rev. B ABB Switzerland Ltd The Subnet and Node ID have to be set for this device as well: Fig Address tab of the LON Node properties dialogue for setting the Subnet and Node ID for a LON device Now a LON logical device has to be added below the LON node that has just been created. Fig Adding a LON logical device 10-7

388 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. B An address also has to be entered for the logical device which is the same as the Node ID. Fig Address tab of the LON Logical Device properties dialogue for setting the address of the LON logical device Repeat this procedure for all the devices connected to the LON bus that communicate with COM Configuring IEC Configuring the slave board (ISG) After configuring the LON IMP board, the next thing is the ISG board for the IEC (IEC101) protocol. This requires the creation of a new ISG board in the VME directory. Fig Adding the ISG board Edit the addresses as necessary. 10-8

389 CAP581 1MRB Uen/Rev. B ABB Switzerland Ltd Fig Address tab of the ISG properties dialogue for setting the address of the ISG board Attribute Remarks Station address User-defined station address Slot number User-defined slot number Default station address (internal COM address; same as the Device ID set in COM581) Enter the station address (same as the Device ID set in COM581). Only has to be entered, if the address has to be changed from the default address. Standard slot for the board Enter the slot of the corresponding board in the rack. Only has to be entered, if the slot has to be changed from the standard slot. Table 10.3 ISG board settings The attributes are explained in detail in Section

390 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. B Adding a serial link Communication with the power system control centre is by serial link which means that a serial line to the ISG board has to be added. Fig Adding the serial link Provision is made for setting the communication parameters for this link: Fig Specific tab of the Serial Line properties dialogue with the communication settings 10-10

391 CAP581 1MRB Uen/Rev. B ABB Switzerland Ltd Attribute Port Number User-defined Port Number Baud Rate Parity Stop Bit Number of Data Bits Transmission Mode Timeout (sec) Bit Order Bit Sense Frame Format class Time Distribution Mode Remarks Configured communication port, default = 3 for protocols User-defined communication port: Load firmware = 1, EVL (event logger) = 2, Electrical protocol port = 3, 4 Optical protocol port for IEC103 protocol and application of SCM02: Data transfer rate setting (protocol and user-defined) Parity setting Enter the number of stop bits. Enter the number of data bits. Full duplex or half duplex Set the timeout for communication. Set the order of the bits for transmission. Set whether the data are normal or inverted. Set the format frame for the protocol in use. Set the format for the protocol in use. Set whether the time distributed is absolute or relative. Table 10.4 Communication parameters for the serial link 10-11

392 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. B Adding the IEC101 application The next step is to specify which protocol will communicate via the link. This necessitates adding an IEC101 application. Fig Adding the IEC101 Slave Application Those settings, which vary with project and protocol, can be changed. Fig Specific tab of the IEC101 Slave Application properties dialogue with the protocol settings The parameter settings for the IEC101 protocol are explained in detail in Section

393 CAP581 1MRB Uen/Rev. B ABB Switzerland Ltd Adding the PSF application Since it is planned to send a general alarm to the power system control centre, it is necessary to add a PSF function block to generate it. The corresponding PSF Application is added as a new VME device below the ISG board. PSF Application is then selected below VME Device. Fig Adding the VME Device for the PSF application Fig Adding the PSF Application 10-13

394 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. B Synchronizing system time The system is synchronized via the LON bus. The star-coupler includes a special board, which obtains the time information from a GPS receiver and forwards it to the LON bus. The following settings are necessary before COM581 can be synchronized via the LON bus. IEC101 is time slave on the VME bus in slot 07 Master on the VME bus is the IMP (LON) card in slot 04 The IMP card in slot 04 is slave on the LON bus, i.e. it reads the time telegrams from the LON bus Fig Configuring the synchronization of system time The IMP board must also be configured as a LON time slave, i.e. it has to be linked below LON Device Time Slave (click the right mouse button on the IMP board below VME and drag to LON Device Slave and select Link here)

395 CAP581 1MRB Uen/Rev. B ABB Switzerland Ltd Tree structure The tree structure is now as follows: Fig Location Structure view Engineering the signals LON part This concludes the configuration of the CAP database for the time being and just the signals have to be imported. The signals are engineered with the aid of Microsoft Excel and a signal list template. The signals defined in Section are used for this example. The first thing is to fill in the signal description and the LON part of the signal list. The figure below shows what this looks like in the case of the example: 10-15

396 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. B Fig Engineering the signals in the LON part of the signal list There are no restrictions on the choice of names in the columns Station Name, Bay Name, Device Name and Signal Name, however they may not include any full stops.. The first line defines the PSF, which is treated as a normal signal. From the second line onwards, entries also have to be made in the LON part. This concerns signals that are transmitted directly by the bay unit. The LON Application ID must be as it is configured in the CAP database (2 in this example). The Unit Address corresponds to the address of the LON Logical Devices (the same as NodeID in the example). The Object Address of the signal depends on the configuration of the bay unit. Each bay also has a special signal, the Status of Node (SON). If the SON signal is missing, all the signals of the device concerned are tagged invalid and the download builder generates a warning. The last signal in the list is the one supervising the synchronization of system time. Since it is generated internally by COM581, it does not have a LON address

397 CAP581 1MRB Uen/Rev. B ABB Switzerland Ltd IEC101 part The IEC101 part concerns the power system control centre addresses, which must be defined before engineering the signals. Fig PSF Engineering the signals in the IEC101 part of the signal list The IEC101 Application ID must once again be as it is configured in the CAP database (3 in this example). The Common Address of ASDU is the same as the station address of the power system control centre. The Information Object Address is an individual address for each signal. A project specific function (PSF) is needed to generate a general alarm. As soon as one of the defined signals changes to logical 1, the output of the function switches and COM581 transmits a general alarm to the power system control centre

398 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. B Fig Engineering the PSF, Part 1 As for LON and IEC101, the PSF Application ID is the same as the application number configured in the CAP database. The PSF Application Caption is the designation of the PSF and must be the same for all inputs and outputs of the PSF block. PSF Entry Type determines whether an input or an output is concerned. PSF FUP Function Name describes what the function block does (in this case, it acts as an OR logic). Fig Engineering the PSF, Part 2 PSF FUP Input or Output Type is the type of input or output signal. Type140 is a Single Indication with time tag

399 CAP581 1MRB Uen/Rev. B ABB Switzerland Ltd Diagnosis messages The message Time synchronization failure is generated by the diagnosis application (DIA). Fig Engineering the diagnosis messages The corresponding error codes (DIA Application Address and DIA Information Address) are described in Section Importing the signal list After all the signals have been added to the Excel table, they are imported into CAP581 by selecting them and running the import macro (see Section 7.2). They are then imported into the CAP database Tree structure after the import operation The tree structure for BAY_A after importing the signals is now as shown below: 10-19

400 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. B Fig Signal tree structure 10-20

401 CAP581 1MRB Uen/Rev. B ABB Switzerland Ltd Configuring the measured variables The scale of the measured variables can be adjusted in CAP581 by making the appropriate settings in the respective properties dialogue: Fig Specific tab of the IEC101 Sink Measurand Value properties dialogue for setting the scaling factor for the measured variables Building and downloading the database Click the right mouse button on the project name in the signal tree and select Build All in the context menu. This generates an MS ACCESS database, which can be loaded into COM581 using the DIS581. It is advisable, however, to view the builder messages to check for any error messages first. These should be rectified before loading the database into COM581. The building procedure must be restarted after correcting the errors

402

403 CAP581 1MRB Uen/Rev. A ABB Switzerland Ltd October Fault Finding Configuration errors using the CAP581 tool Error messages generated by COM Import error list Consistency check messages Event viewer Bypassing an event log overflow Switch off event logging (V5.1 onwards)

404 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. A 11. Fault Finding Configuration errors using the CAP581 tool IEC101_Link_Layer: Transmit operation returned an error This message appears on the EVL when communication cannot be established with the master. Reason: Interchange Mode must be set to unbalanced. Invalid attribute assignment does not function for LON Reason: The IV attribute can only be assigned to data points, if the unit address has been assigned to a physical device that has failed (Table LON_Logical_Device). Cycle switching for IEC101 measured variables does not function Reason: This error occurs when the address masking function has not been configured at all (or incorrectly configured) for a bay. IEC103 signals cannot be transferred via LON Reason: The signals are rejected by LAC (wrong PI data type) if Double_Point_Indication was not set as LON_Data_Type for IEC103 signals. RP571 Error 199 by Standard Services (during start-up) Reason: The block numbers are checked to make sure that none higher than 254 have been used for RP571 data points. Higher numbers are only permissible for commands (Block_Number = Object_Number). 11-2

405 CAP581 1MRB Uen/Rev. A ABB Switzerland Ltd Error Cause Recommended test Corrective action Signals with high bit offsets only occur during a GA (wrong value but correct status). Data sets were defined with the wrong size in COM581, RER581 or the bay unit. The offsets are too high for these data sets The bay unit is not sending the IDM to the MVB. No signals are being transferred (the status is always invalid for a GA). A bay unit SON was not defined in the imported signal list. Signal list and CAP581 Import SON separately. The bay unit SON data set was not defined with Valid_Check = True. CAP581 Correct The bay unit SON data set was configured in COM581 and does not match the bay unit node ID. Data set: 1023 Node_ID: 63 Using the MCB monitor, check whether the bay unit SON data set is updated. Enter, for example, another node ID in the parameter section. The bay unit SON must be configured as status signal, Signal list Delete and re-import No signals are being transferred (not even by the GA). Signal defined as Sequence_of_ Events. Signal list properties dialogue in CAP581 Change settings Signals are only received by the GA (with wrong value but correct status). Data sets were defined with the wrong size in COM581, IBC or the bay unit. MVB_Dataset Bus monitor Correct The offsets are too high for this data set. Signal list properties Correct The bay unit is not sending the IDM to the MVB. Bus monitor The data point was defined as a signal, but only with message data. MVB Change IEC101 signals are being received sporadically with the wrong value but correct status. The signal type does not agree with that sent by the bay unit. IEC101 Correct single to double or vice versa. Only IDM s are being transferred. There is an error in the fivepart MVB address. CAP581 MVB Re-import and correct manually The ERMI s are being suppressed in RP57x. Signal properties Change in form The bay unit is not transferring the ERMI s. Bus monitor The CAP581 database cannot be opened any more. Incorrect directory structure or error during installation Event viewer; Is there a full stop. in the project or installation directory? Reinstall tool. Correct project directory CAP581 crashes. Possibly incorrect directory structure Event viewer Various actions depending on event viewer entry (see customer feedback database) Builder causes CAP581 to crash with the error message Enter memory and read during import and export. The *.DLL files are wrong or incorrectly registered Event viewer Register the DLL file using reqsvr32*.dll. 11-3

406 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. A Error Cause Recommended test Corrective action COM581 cannot start its MVB application. Interlocking data sets (16-32 ms) are being used for transferring data to COM581 and sampled too often. MVB_Dataset Signal list Correct in CAP581 Signals are not being transferred (bay unit invalid in the GA). Optical fiber cable disconnected at either the bay unit or COM581 end. Bay unit sets SON to Not_Ready on the MVB. Bus monitor Check the status on the MVB. A RESET occurs while starting the IEC101 protocol (start applications). The Slot/Port_No for the serial interface has been incorrectly configured. Event log: configuration error Slot/Port_No = 3 or 4, excepting for the IEC103 protocol The IEC101 protection links are not generating any signals (only events). The data points have been configured as Sequence_of_ Events. Signal list CAP581 IEC101 Correct differential import RESET when starting TIM: synch point 8 (in the case of a COM581 without a radio clock). COM581 acts as slave on the MVB and uses the radio clock. Time_Management Correct accordingly in the database: IMP, serial, delete Slave IMP, MVB, Slave IMP, VME, MASTER ISG, VME, Slave A binary file was transferred when loading using PC-Term Send a test file without LF. Reset at Synchro point 8 Wrong Node_ID on both COM581 boards. Use SiMon to check parameter block. Simon > pb Metered values cannot be polled (incl. Type ID 101 via 101). FCOM3 must be defined in COM581. RP57x_Datapoint FCOM MVB_Datapoint (0, 0, 255, 0, 0) Configure accordingly Data sets must be configured in BA. In BA 128 bit, 512 ms Metered values are not transferred as message data. MVB Five-part MVB address > 0 For REF542: 1, x, 1, 158 Protection events are not transferred as signals. Must be defined in the AEG protection device as data type 17. Protocol analyzer Signals are not imported correctly. DataType_NCC incorrectly set Signal list Signal list COM581 is not sending its own SON data set to the bus. A SON data set from the BA is configured in COM581, but no SON signal is generated as a COM581 data point (process signal). MVB_Datapoint Generate a COM581 data point A SON data set from the BA is configured in COM581, but does not match the BA node ID. Data set: 1023 Node_ID: 63 Use the MVB monitor to check that the BA SON data set is updated. Reset at Start applications The star-coupler is in the wrong slot. Put star-couple in the correct slot. The data points are incorrectly configured, e.g. measured variables from RP571 to MVB. CAP581 Correct Reset after or during the startup of the slave. Its own SON signal is not linked to the MVB (created as data point). 11-4

407 CAP581 1MRB Uen/Rev. A ABB Switzerland Ltd Error Cause Recommended test Corrective action COM581 sticks at Synchro point 8. There must be least one COM581 data point in the download database. Create a COM581 data point. Wrong Node/Device_ID on the ISG board. Use SiMon to check parameter block. Simon > pb RESET: SIG Error 97 Bay unit SON was only configured as MVB_Signal_Location. No COM581 data point or other bay unit signals exist. Configure data point completely. COM581 cannot be changed to the Limited_Ready status at Synchro_Point 6. Different Node_ID s on the two boards. Use SiMon to check parameter block. Simon > pb DNP3.0 data points set incorrectly The DNP3.0 object addresses are not numbered consecutively for each data point. Change DNP3.0 data points. Polling command incorrect. Check settings in the IEC101 emulation tool. Check settings in the IEC101 emulation tool: Cause_of_Transmission = 6; activation Qualifier_of_Command QCC.FRZ: = 2; 1 is IR and 2 is EPR QCC. RQT: = 5; Request counter Table 11.1 Typical configuration errors 11-5

408 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. A Error messages generated by COM581 Serial line Slot/Port_No Only slots or ports number 3 and 4 may be configured when using electrical outputs. A typical error and its consequences: RAM version does not start when using slot or port No. 1, because the application occupies the communication interface for Alsymon and this stops both the application and Alsymon. Time stamp is IV (invalid) The radio clock itself must be correctly set (CAP581 settings have no effect). Corrective action: Correct the radio clock settings. In the case of the MACM IMP board, the following parameter values must be set for the radio clock: 9600, 8, n, 1. SIC/MAC Error 6 A Major_Error 6 is generated when the SIG queue is blocked. This can happen when a remote control line is not in operation and a tailback was configured for the MDP channels. Corrective action: Unplug the MVB optical fiber cable if there is a remote control channel failure. SIG Error 183 A Minor_Error 183 is generated when the MVB Channel 2 (signals) output queue is too small to transfer a full GA. SIG Error 97 This minor error is generated periodically when Signals attempts to sample data sets for which a SON data set (status of node) was not configured. Care must therefore be taken when configuring the system that a SON signal is configured in a SON data set (Valid_Check for True) for every device connected to the MVB from which data shall be received. There is an additional EVL output during start-up (DBS) showing the HW_Component_ID of the device for which a SON was not configured. SIG SIG-H: DRAM_Access_Error Error 9 This error can occur, for example, when signals were configured as sinks in the MVB application. The configuration is correct when the MVB application is a source for signals and a sink for commands. 11-6

409 CAP581 1MRB Uen/Rev. A ABB Switzerland Ltd Import error list Various error messages such as Import Error 150 may be displayed after importing. The table below lists all the possible error codes and in the cases where the user can correct the situation, a likely cause and the suggested corrective action. No. Cause Corrective action Wrong application ID Enter the correct ACP Application ID Correct the ACP Application ID in the database or signal list. 167 Incomplete PSF configuration Enter the PSF Signal Entry Type Wrong application ID Enter the correct LON Application ID. Correct the LON Application ID in the database or signal list. 182 Wrong partner LON Application ID Enter the correct Application ID. Correct the Application ID in the database or signal list. Add a PSF block for the PSF signal Signal with the same LON configuration already exists Change LON configuration. Delete the signal from the database. Change signal name. 11-7

410 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. A No. Cause Corrective action 190 Wrong Application ID Enter the correct MVB Application ID. Correct the MVB Application ID in the database or signal list. 191 Wrong Application ID Enter the correct IEC103 Application ID Correct the IEC103 Application ID in the database or signal list. 201 Wrong Application ID Enter the correct PSF Application ID. Correct the PSF Application ID in the database or signal list. 202 Function block not found Check the function name Wrong Application ID Enter the correct DIA Application ID Correct the DIA Application ID in the database or signal list. Table 11.2 Import error codes 11-8

411 CAP581 1MRB Uen/Rev. A ABB Switzerland Ltd NOTICE: Error code ranges: IEC103 master connections General errors LON connections MVB connections PSF connections Consistency check messages Consistency check description Category Error identification / text General COM581 engineering check: Error At least one signal must be configured for every application. - Sink or source LON - Sink RP57x, DNP30, ACP, IType2, IEC101, TG809 - Source DIA, IEC103, MVB - Sink and source PSF General COM581 engineering check: A maximum of 6 CPU boards may be defined per COM581. General COM581 engineering check: The node ID of each bay must be unique (only occur once). Error Warning There are CPUNo CPU cards defined. Only 6 CPU cards are allowed. COM: COMName. Two equal Node ID's were found. Node ID = NodeID General COM581 engineering check: Are there source signals that are linked in the signal tree, but not linked to a sink signal? Warning The source signal (internal address = ICC_Internal_Address ) on the ApplicationName application Source_Application_ID has no linked sink signal. 11-9

412 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. A Consistency check description Category Error identification / text General COM581 engineering check: MVB time management: 1.) Is there precisely one link TimeManagement MVB Master? (OK) 2.) Are there precisely two links TimeManagement MVB Redundant master? 2.1.) Are there two redundant masters and one link TimeManagement VME Master IMP? If so, a check is performed whether a link exists TimeManagement SerialLine Slave IMP. (OK) 2.2.) If there is no link TimeManagement VME Master IMP, there must not be a serial link either. 3.) Are there more than two redundant time masters in one COM581? (error) LON time management: 1.) Is there precisely one link TimeManagement LON Slave? (OK) Every other combination generates an error message. General COM581 engineering check: Time management master: 1.) Is there precisely one link TimeManagement Master? General COM581 engineering check: Redundant time management: Is there either none or more than two redundant time masters in a COM581? (error) ACP engineering check: Is there a signal address that is used several times for the same ACP application? DIA engineering check: Is the same DIA error number been assigned twice in the same subsystem? IEC101 engineering check: Whenever Deadband_Threshold or Accumulating_Value are not zero, at least one of the two attributes Fast/Default_Cycle_Time must be greater than zero. Background_Scan can only be greater than zero when either Deadband_Threshold or Accumulating_Value is not zero. Only Deadband_Threshold or Accumulating_Value may not be zero. IEC101 engineering check: Is there an IEC101 maintenance signal below each IEC101 application? Error Error Error Error Error Warning MVB) There is no link under Time Management MVB Master; COM: COMName There is a wrong link under. There are two links under Time Management MVB, but not under Redundant Master; COM: COMName There is a Redundant Master defined under Time Management MVB, a IMP-Card under VME Master, but there is no link under Serial Line Slave; COM: COMName There is a redundant master defined under Time Management MVB, no IMP-Card under VME Master, but there is a link under Serial Line Slave; COM: COMName There are more than two links under Time Management MVB; COM: COMName LON) There is no link under Time Management LON Slave; COM: COMName There is a wrong link under. There is more than one link under. There is not only one time master defined for VME. COM581 COMName, number = VMEMasterCount There are more or less then two redundant time masters defined. COM: ComName, number = RedundantMasterCount The following ACP application signal addresses Application_ID are not unique. Datatype with object address ACP_Object_Address, device address ACP_Device_Address and internal address ICC_Internal_Address The attribute Error Number ErrNumber is defined Number times on the CPU card with Station Address AddressNo. (on COM: Name ) Measured variables on IEC101 Application with ID Application_ID are inconsistent, i.e. signal with ASDU and object address: X.Y,..must not be zero. It is advisable to configure an IEC101 maintenance information data point for the IEC101 application with ID: ID 11-10

413 CAP581 1MRB Uen/Rev. A ABB Switzerland Ltd Consistency check description Category Error identification / text IEC103 engineering check: 1.1) Have more than 10 applications been configured for one COM581? 1.2.) Have more than 15 applications been configured for one COM581? 2) Has the correct number of SON signals been configured? IEC103 engineering check: Have the default values for transparent data been changed? 1.) Warning 1.2) Error Warning 1.1) This number Number of IEC103 application ID devices has not been released for this COM581 version. The performance of the protocol may be affected. 1.2) This COM581 version does not support this number Number of devices. 2) No system diagnosis signal configured on the IEC103 master. More than one system diagnosis signal on the IEC103 master. The default attribute values FUN=254 and INF=0 for IEC103 Transparent Data have been changed. IEC103 master ID: Application_ID ; Internal Address: ICC_Internal_Address. LON engineering check: 1.) Has the same filter configuration been used for all the source signals that belong to the same LON logical node? 2.) Only one filter per LON node and filter configuration. Error 1.) The filter configuration is not the same for all LON source data points of the LON node. COM: Name, LON Node = NodeID, LON unit address = UnitAddress, filter configuration = ConfigurationID LON engineering check: Have all the LON source signals been assigned to a LON logical device? LON-SPA engineering check: Have all the SPA source signals been assigned to a SPA logical device? LON-NV engineering check: Have all the NV source signals been assigned to a LON logical device? LON engineering check: Has one SON signal been configured for every LON logical device? MVB engineering check: Are there two data sets and offsets the same in two different bays? MVB engineering check: Have other signals been created in a data set which contains a SON signal? Error Error Error Error Warning Error 2.) More than 1 Filter No. has been configured for the LON node NodeID and the filter configuration ConfigurationId. COM: Name A LON logical device with the same unit address has not been defined for the LON source data point. COM: Name, application ID = ApplicationID, unit address = UnitAddress A SPA logical device with the same unit address has not been defined for the LON SPA source data point. COM: Name, application ID = ApplicationID, unit address = UnitAddress A SPA logical device with the same unit address has not been defined for the LON NV source data point. COM: Name, application ID = ApplicationID, unit address = UnitAddress Configure a SON data point for the LON with unit address UnitAddress. More than one SON data point has been configured for the LON with unit address UnitAddress. Two data sets and offsets have been found which are the same. Node ID 1 = NodeID1, logical address = LogicalAddress, Bit offset = BitOffset. In the data set of a MVB SON signal is another signal configured. Node Id = "NodeId", Logical Address = "LogicalAddress" 11-11

414 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. A Consistency check description Category Error identification / text MVB engineering check: Has one BLS or SON signal been correctly configured in each bay (described in the error message)? PSF engineering check: A Port No. from 1 to 6 has to be configured for all six inputs of a complex addition function block. A Port No. is not required for the output. Queue engineering check: Have the default settings for the application queue been changed? Queue engineering check: Have the default values of the various queue configurations been changed or even deleted or added? RP570 engineering check: Has only one RTU process number been used for all the signals of each RP570 application? Error Error Warning Warning Error MVB SON signal has been wrongly configured. Node ID = NodeID, telegram period = TelegramPeriod ms. Change the following attributes to: logical address (MVB data set No.) = LogicalAddress ; Bit offset = 0; data set size = 16 Bit; individual period = 512 ms MVB BLS signal has been wrongly configured. Node ID = NodeID, telegram period = TelegramPerio ms. Change the following attributes to: logical address (MVB data set No.) = LogicalAddress ; Bit offset = 8; data set size = 16 Bit; individual period = 512 ms There is an error in the configuration of the complex addition function block NameOfComplexFunction! No Port No. PortNo. has been entered. There is an error in the configuration of the complex addition function block NameOfComplexFunction! The default configuration settings for the application queue for the application with ID ApplicationID have been changed. The default queue configuration values QueueConfigId have been changed. One or more queues deleted. QueueCheckError QueueErrNo One or more queues added. QueueCheckError QueueErrNo Main error codes QueueErrNo: 0 No Q 1 2 and 3 missing 4 1 and 3 missing 5 3 missing 8 1 and 2 missing 9 2 missing 12 1 missing 16 One new Q Set only one Process_RTU_No for all data points of the RP570 application ApplicationID

415 CAP581 1MRB Uen/Rev. A ABB Switzerland Ltd Consistency check description Category Error identification / text TG809 engineering check: Are the settings for the signal attributes cubicle, rack, slot and point number (concerning Is Hardware Point and data type) correct? TG809 engineering check: Has a corresponding RTU configuration been assigned to each of the signals having the same station number? Error Error The main settings: Cubicle Number: 0 3 If HardwarePoint = False 0 only Rack No.: If HardwarePoint = False 0 only Slot No.: If HardwarePoint = False 0 only Point No.: Is HardwarePoint = True for Sink for Source Is HardwarePoint = False One RTU configuration with the station No. StationNo below the TG809 application with ID ApplicationId, or change the station No. on the data point with internal address InternalAddress. Table 11.3 Consistency checks Refer to Section 8 for a detailed explanation of the engineering steps

416 ABB Switzerland Ltd CAP581 1MRB Uen/Rev. A Event viewer Certain events and also a CAP581 system crash are recorded in the event viewer log file Bypassing an event log overflow Depending on the settings, an error message quickly appears to the effect that the event log is full. By accordingly configuring the event viewer, the problem can be quickly resolved without complication (but not the cause). 1. Open the event viewer and select Log Settings in the Log menu. 2. Appropriately edit the individual log settings in the dialogue which appears: 3. Increase the file size