Protection & Control Terminals REF 54_, REM 54_, RET 54_, REC 523. Configuration Guideline

Transcription

1

2

3 1MRS MUM Issued: Version: L/ Contents 1. About this manual Copyrights Trademarks General Use of symbols Document conventions Abbreviations Terminology Related documents Document revisions Safety information Relay Configuration Tool Specification for relay configuration Editing the relay configurations Getting started Libraries Program organisation unit Logical POUs Physical hardware Configuration Resource for REF 54_, REM 54_ and REC Resource for REF 54_ Release 2.5 or later, REC 523 revision F and RET 54_ Tasks Declaring variables Global variables Local variables Compiling project Add-on protocol Downloading the configuration REF 54_ Release 2.5, RET 54_ and REC 523 revision F additions Main configuration rules General Digital inputs and outputs Explicit feedback path Analog inputs Error outputs of application function blocks...66 Copyright 2005 ABB Oy, Distribution Automation, Vaasa, FINLAND 3

4 1MRS MUM 6.6. Warnings Execution order F-key Engineering tips Horizontal communication Guideline for using LON NV-variables in PLC logic COMM_IN COMM_OUT Cyclic sending generation Cyclic communication check Blocking Control of objects Bypass mode Events from the measurement function blocks APPENDIX A: Relay configuration procedure APPENDIX B: Specification for REF 54_ feeder terminal configuration General data Electrotechnical data Analog inputs System frequency Digital inputs Digital outputs RTD module RTD/analog inputs RTD outputs Functionality Order number Application function blocks used Communication Relay MIMIC configuration Illustration of the system, MIMIC diagram Alarm LEDs Functionality logic Feeder terminal settings APPENDIX C: Specification for REM 54_ machine terminal configuration General data Electrotechnical data Analog inputs

5 1MRS MUM Hardware versions with 5 current and 4 voltage transformers Hardware versions with 6 current and 3 voltage transformers Hardware versions with 7 current and 2 voltage transformers Hardware versions with 8 current and 1 voltage transformer Sensor inputs System frequency Digital inputs Digital outputs RTD module RTD/analog inputs RTD outputs Functionality Order number Application function blocks used Communication Relay MIMIC configuration Illustration of the system, MIMIC diagram Alarm LEDs Functionality logic Machine terminal settings APPENDIX D: Specification for RET 54_ transformer terminal configuration General data Electrotechnical data Analog inputs Hardware versions with 6 current and 3 voltage transformers Hardware versions with 7 current and 2 voltage transformers Hardware versions with 8 current and 1 voltage transformer System frequency Digital inputs Digital outputs RTD module RTD/analog inputs RTD outputs Functionality Order number

6 1MRS MUM Application function blocks used Communication Relay MIMIC configuration Illustration of the system, MIMIC diagram Alarm LEDs Functionality logic Transformer terminal settings APPENDIX E: Specification for REC 523 Remote Monitoring and Control Unit configuration General data Electrotechnical data Analog inputs System frequency Digital inputs Digital outputs Functionality Order number Application function blocks used Communication Virtual channels LED configuration Remote monitoring and control unit settings APPENDIX F: Power quality application guide for harmonics Power quality and harmonics Background for harmonics Harmonic sources Single-phase power supplies Three-phase power converters Other harmonic sources System response characteristics Effects of harmonics Applications for harmonic measurements Power quality and harmonics Harmonic monitoring with individual loads and devices Locating sources of harmonics Harmonic filter performance monitoring Index

7 1MRS MUM 1. About this manual 1.1. Copyrights 1.2. Trademarks 1.3. General The information in this document is subject to change without notice and should not be construed as a commitment by ABB Oy. ABB Oy assumes no responsibility for any errors that may appear in this document. In no event shall ABB Oy be liable for direct, indirect, special, incidental or consequential damages of any nature or kind arising from the use of this document, nor shall ABB Oy be liable for incidental or consequential damages arising from use of any software or hardware described in this document. This document and parts thereof must not be reproduced or copied without written permission from ABB Oy, and the contents thereof must not be imparted to a third party nor used for any unauthorized purpose. The software or hardware described in this document is furnished under a license and may be used, copied, or disclosed only in accordance with the terms of such license. Copyright 2005 ABB Oy All rights reserved. Brand and product names mentioned in this document are trademarks or registered trademarks of their respective companies. This guideline describes in general the procedures for configuring REF 54_ feeder terminals, REM 54_ machine terminals, RET 54_ transformer terminals and REC 523 remote monitoring and control units correctly with the Relay Configuration Tool. In this document, the term device is used when referring to all the above mentioned products. Chapter 5. Editing the relay configurations describes step-by-step the engineering actions required to create a relay configuration for a single device. Chapter 6. Main configuration rules defines a set of programming rules that should be followed while creating the configuration. These rules should be carefully checked when finalizing the configuration. Chapter 7. Engineering tips provides some engineering tips for doing the configuration. For instructions on operating the tool itself, refer to the operator s manual for CAP 505 (see Section 1.8. Related documents). This version of the Configuration Guideline complies with products of Release For information about the changes and additions compared to earlier revisions, refer to the technical reference manual of the appropriate product (see Section 1.8. Related documents). 1. Except REC 523 with revision D or later, and REM 54_ with Release 2.5 7

8 1MRS MUM 1.4. Use of symbols For information on what RE_ 5 products support which add-on protocols, refer to the product manuals (Section 1.8. Related documents). Note that in this manual, the examples and dialog box pictures of the Relay Configuration Tool refer to REF 54_ feeder terminals (except Fig ). The corresponding cases and dialog boxes can be slightly different for REM 54_, RET 54_ and REC 523. This publication includes warning, caution, and information icons that point out safety-related conditions or other important information. It also includes tip icons to point out useful information to the reader. The corresponding icons should be interpreted as follows: The electrical warning icon indicates the presence of a hazard which could result in electrical shock. The warning icon indicates the presence of a hazard which could result in personal injury. The caution icon indicates important information or warning related to the concept discussed in the text. It might indicate the presence of a hazard which could result in corruption of software or damage to equipment or property. The information icon alerts the reader to relevant facts and conditions. The tip icon indicates advice on, for example, how to design your project or how to use a certain function. Although warning hazards are related to personal injury, and caution hazards are associated with equipment or property damage, it should be understood that operation of damaged equipment could, under certain operational conditions, result in degraded process performance leading to personal injury or death. Therefore, comply fully with all warning and caution notices. 8

9 1MRS MUM 1.5. Document conventions The following conventions are used for the presentation of material: The words in names of screen elements (for example, the title in the title bar of a dialog box, the label for a field of a dialog box) are initially capitalized. The names of push and toggle buttons are boldfaced. For example, click OK. The names of menus and menu items are boldfaced. For example, the File menu. The following convention is used for menu operations: Menu Name > Menu Item > Cascaded Menu Item. For example: select File > Open > New Project Abbreviations ASD CPU CSI FBD HMI I/O LCD LED LON NV PLC POU PWM RCT RMS RS RTD VD Adjustable speed drive Central processing unit Current source inverter Function block diagram Human-machine interface Input/output Liquid chrystal display Light-emitting diode Locally operating network Network variable Programmable logic controller Program organisation unit Pulse width modulation Relay Configuration Tool Root mean square Rogowski sensor Resistance temperature device Voltage Divider 1.7. Terminology device In this document refers to REF 54_ feeder terminal, REM 54_ machine terminal, RET 54_ transformer terminal and REC 523 remote monitoring and control unit DNP 3.0 Distributed Network Protocol, a communication protocol controlled by the DNP Users Group IEC Communication protocol standardized by International Electrotechnical Commission IEC Communication protocol standardized by International Electrotechnical Commission MIMIC Graphic configuration picture on the relay s LCD Modbus Communication protocol introduced by Modicon Inc. RCT project file Relay Configuration Tool project, a zipped project file SPA Communication protocol developed by ABB 9

10 1MRS MUM 1.8. Related documents Document Manuals for RET 54_ and REC 523 Installation Manual RE_ 5 a 1MRS MUM Operator s Manual RE_ 54_ a 1MRS MUM Feeder Terminal REF 54_ 1MRS MUM Technical Reference Manual, General a Technical Reference Manual REM 54_ a 1MRS MUM Transformer Terminal RET 54_ 1MRS Technical Reference Manual, General Remote Monitoring and Control Unit REC 523 1MRS MUM Technical Reference Manual a REM 54_ Machine Terminal Technical Reference Manual, General 1MRS MUM Technical Descriptions of Functions (CD-ROM) 1MRS MCD REF 54_ and RET 54_ Modbus Communication Protocol 1MRS Technical Description Modbus Remote Communication Protocol for REM 54_ 1MRS MUM Technical Description REM 543 Modbus Configurations (CD-ROM) 1MRS MUM Modbus Remote Communication Protocol for REC 523 1MRS MUM Technical Description REF 54_, RET 54_ and REX 521 DNP 3.0 Communication Protocol 1MRS Technical Description DNP 3.0 Remote Communication Protocol for REC 523 1MRS MUM Technical Description IEC Remote Communication Protocol for REC 523, 1MRS MUM Technical Description Tool-specific manuals CAP 505 Installation and Commissioning Manual b 1MRS MEN CAP 505 Operator s Manual b 1MRS MUM CAP 505 Protocol Mapping Tool Operator s Manual b 1MRS CAP 501 Installation and Commissioning Manual c 1MRS MEN CAP 501 Operator s Manual c 1MRS MUM Relay Configuration Tool, Quick Start Reference b 1MRS MEN Relay Configuration Tool, Tutorial b 1MRS MEN Relay Mimic Editor, Configuration Manual b 1MRS MEN LIB, CAP and SMS, Tools for Relays and Terminals, User s Guide 1MRS MUM a. Included on the CD-ROM Technical Descriptions of Functions, 1MRS MCD b. Included on the CD-ROM Relay Product Engineering Tools c. Included on the CD-ROM Relay Setting Tools ID 10

11 1MRS MUM 1.9. Document revisions Version Date History G Manual updated H RET 54_ added to manual K Updates according to REC 523 revision F L Updates according to REF 54_, Release

12 12

13 1MRS MUM 2. Safety information! Dangerous voltages can occur on the connectors, even though the auxiliary voltage has been disconnected. National and local electrical safety regulations must always be followed. The device contains components which are sensitive to electrostatic discharge. Unnecessary touching of electronic components must therefore be avoided. The frame of the device has to be carefully earthed. Only a competent electrician is allowed to carry out the electrical installation. Non-observance can result in death, personal injury or substantial property damage. Breaking the sealing tape on the rear panel of the device will result in loss of warranty and proper operation will no longer be guaranteed. When a plug-in unit has been detached from the case, do not touch the inside of the case. The relay case internals may contain high voltage potential and touching these may cause personal injury. 13

14 14

15 1MRS MUM 3. Relay Configuration Tool The Relay Configuration Tool is a standard programming system for RED 500 devices. It is used for configuring the protection, control, condition monitoring, measurement and logic functions of the feeder terminal. The tool is based on the IEC standard, which defines the programming language for relay terminals, and includes a wide range of IEC features. The programmable logic controller (PLC) logics are programmed with Boolean functions, timers, counters, comparators and flip-flops. The programming language described in this manual is a function block diagram (FBD) language. 15

16 16

17 1MRS MUM 4. Specification for relay configuration Prior to starting the configuration of a product, the specification for relay configuration is to be filled out. Separate specifications for RET 54_ and REC 523 can be found in appendices B, C, D and E in the end of this manual. The purpose of the specification is to provide the technical information required for the proper configuration of the products. 17

18 18

19 1MRS MUM 5. Editing the relay configurations 5.1. Getting started 1. Start up the CAP 505 tool by double clicking the tool icon. 2. Add a new object as an empty configuration to the CAP 505 environment. For instructions, refer to the operator s manual for CAP 505 (see Section 1.8. Related documents). The program opens an empty project template (see Fig ) with a toolbar at the top. 3. Build the project tree structure by inserting libraries, program organisation units (POUs) and target-specific items to the project tree. The project tree editor is a window in which the whole project is represented as a tree. The project tree is illustrated with several icons. Most of the icons represent a file of the project, and different looking icons represent different types of files. The tree always contains 4 subtrees: Libraries, Data Types, Logical POUs and Physical Hardware. Fig Project tree and the four subtrees ProjectTree Libraries The project tree is the main tool for editing the project structure. Editing the project structure means inserting POUs or worksheets to the project structure, or deleting existing ones. The editors for editing the code-body data and the variable declaration can be opened by double-clicking the corresponding object icons. If you edit an old project, note that saving the changes made with the Save as command does not work as in other Windows programs. If you want to keep the old project unchanged, save the project with a new name before making any changes. Before editing any worksheets of POUs, the whole project tree structure must be build. The function block library (protection, control, measurement, condition monitoring and standard functions) needed in the relay configuration needs to be inserted to the Libraries subtree. For instructions on announcing libraries, refer to the tutorial manual for the Relay Configuration Tool, see Section 1.8. Related documents. Before inserting a library to the project, close all open worksheets in order to avoid confusing the I/O description of the function blocks. 19

20 1MRS MUM The programs, function blocks (for example NOC3Low, the low-set stage of nondirectional three-phase overcurrent protection) and functions of the library can be reused in the new project, which is edited. The library, for example REFLIB01 for REF 54_ (see Fig ), includes the full set of function blocks, but only those ordered by the customer can be used in the configuration. If a configuration is transferred to a newer version of the product, the library in the project must also be updated. ref/rem/ret/reclib01 Fig Libraries for RET 54_ and REC 523 The library version to be selected depends on the software revision of the product as listed in the table below. The directory path to the libraries is <installation drive>\cap505\common\ieclibs\fi. Table Product software revisions and libraries Product Software revision Library file name REF 541 A COMMU_01, CONDM_01, CONTR_01, MEASU_01, PROTE_01, STAND_01 B REFLIB01 C REFLIB02 D and E REFLIB03 K REFLIB04 REF 541 (RTD1) A REFLIB02 B and C REFLIB03 K REFLIB04 REF 543 C and D COMMU_01, CONDM_01, CONTR_01, MEASU_01, PROTE_01, STAND_01 E REFLIB01 F REFLIB02 G and H REFLIB03 K REFLIB04 REF 543 (RTD1) A REFLIB02 B and C REFLIB03 K REFLIB04 20

21 1MRS MUM Table Product software revisions and libraries (Continued) Product Software revision Library file name REF 545 A COMMU_01, CONDM_01, CONTR_01, MEASU_01, PROTE_01, STAND_01 B REFLIB01 C REFLIB02 D and E REFLIB03 K REFLIB04 REM 543 A REMLIB01 B REMLIB02 C REMLIB03 REM 543 (RTD1) A REMLIB02 B REMLIB03 REM 545 A REMLIB02 B REMLIB03 REM 545 (RTD1) A REMLIB02 B REMLIB03 RET 541 A RETLIB01 RET 541 (RTD1) A RETLIB01 RET 543 A RETLIB01 RET 543(RTD1) A RETLIB01 RET 545 A RETLIB01 REC 523 A RECLIB01 B RECLIB01 C RECLIB02 D RECLIB03 E RECLIB03 F RECLIB Program organisation unit Each Program Organisation Unit (POU) consists of several worksheets: Description worksheet for comments Variable worksheet for variable declarations Code body worksheet for the configuration. The name of each worksheet is indicated beside the corresponding icon. The * symbol after the name of a worksheet indicates that the worksheet has not been compiled yet. Fig Program organisation unit with three worksheets POU_unit 21

22 1MRS MUM The description worksheet (for example ProtectT) illustrated below is for describing the POU or the configuration element. The worksheet is automatically named by adding a T to the name of the POU. Fig Description worksheet The variable worksheet (for example ProtectV) is for the variable declaration. The worksheet is automatically named by adding a V to the name of the POU. The variable worksheet is not edited manually but is created by the tool. text variables Fig Variable declaration worksheet A code body worksheet (for example Protect) is for a code body declaration in the form of an function block diagram (FBD). All configurations for the devices of the RED 500 platform are made in the graphical FBD language. A code body programmed in the FBD language is composed of functions and function blocks that are connected to each other using variables, connection lines or connectors. An output of a function block can be combined with the output of another function block for example via an OR gate (refer to Section 6.1. General). Connectors are objects that can be used instead of connection lines, for example where the distance between two objects on the worksheet is long. The connectors can only be used within one worksheet, and they are resolved by textual names. 22

23 1MRS MUM Connectors should be used with care since the tool may not warn if a match to a connector cannot be found (for example, the comparison of connectors is case sensitive). Note that visually the connectors are distinguished from variables by embedding them with larger than signs, > > Logical POUs Connectors Fig Code body declaration in FBD language Even though the tool permits adding several code body worksheets under one POU, only one worksheet is recommended to be used per POU. If more space is needed for a configuration, the worksheet size can be increased or the functionality can be divided into several POUs. Avoid creating very large configurations per POU since the RED 500 PLC environment has an inherent limit for the number of input/output points per POU. The limit is 511 I/O points and is consumed by called function block instances only. Note that the limit is checked during the configuration downloading. If the downloading fails for this reason, the user has to divide the POU into smaller units. For example, the function block NOC3Low in Fig includes 14 I/O points. The I/O points are consumed regardless of whether they are connected or not. In the project tree editor and in the library editor, the Logical POUs subtree represents a directory for all the POUs related to the project. The maximum of 20 POUs can be inserted to the subtree. Fig shows a Logical POUs subtree 23

24 1MRS MUM with 4 POUs; CondMon represents a function block, Confirm represents a function, and Measure and Control are programs. The associated icon represents the POU type. Fig Logical POUs subtree with 4 POUs LogicalPOUs Each POU type has specific characteristics from the programming point of view. A function yields exactly one data element which is evaluated from its input parameters. In other words, a function cannot contain any internal state information. Furthermore, a function can call other functions but not function blocks. A function block (FB) can return 0,1,2.. output values and can have internal variables. Function blocks can call any other function or function block except itself. Multiple copies of function blocks are called instances and each instance is given an identifier. Programs are specialized function blocks that can only be called by tasks. Note that recursion is not allowed for any POU type. The POU category is selected when a POU is inserted to the project tree. Fig below shows the dialog box for inserting POUs. The programming language (FBD) for the POU and the return data type for functions are also selected here. The PLC type and Processor type selections should be left to their default values. 24

25 1MRS MUM InsertNewPOU Fig Inserting a new program POU called Demo which is programmed by using the function block diagram language At first, a POU framework is created, that is, empty POUs are inserted to the project according to the Specification for Relay Configuration filled out prior to starting the configuration procedure. The physical hardware must be defined before creating the actual contents for the POUs, otherwise the predefined target-specific POUs are not available for the programmer. The task execution intervals recommended for function blocks must be considered already when defining the POU framework. In general, each POU forms a functional unit for example for protection function blocks. Some function blocks, however, require a different task than most of the same category, and must therefore be assigned a separate POU. For example, the task execution interval of most protection function blocks is 10 ms but Freq1St_ requires the task of 5 ms, which is why it usually needs a separate POU. However, if all the protection function blocks used are associated with the task of 5 ms, no separate POU is required for Freq1St_ Physical hardware In the project tree editor, the physical hardware is represented as a subtree (see Fig ) after the hardware of the device, that is, Configuration, Resource and Tasks, has been defined. 25

26 1MRS MUM Fig Example of a subtree for the physical hardware PhysicalHardware Configuration The configuration elements available in the Physical Hardware subtree may differ from configuration to configuration. Each terminal of the RED 500 platform can be configured separately. In the Relay Configuration Tool, the name of the configuration and the appropriate product family, programmable logic controller (PLC) type, are first defined: 1. Select a Physical Hardware tree element and select Edit > Insert. 2. Define Name and PLC type, and click OK. Fig Defining the configuration type configuration_b 26

27 1MRS MUM Resource for REF 54_, REM 54_ and REC 523 For REF 54_ Release 2.5 and later, RET 54_, and REC 523 revision F, refer to Section Resource for REF 54_ Release 2.5 or later, REC 523 revision F and RET 54_. The PLC type selected in the Configuration dialog box above determines which processor types are available. To select the processor type and name the resource: 1. Select an object under the Physical Hardware tree and select Edit>Insert. 2. In the opening dialog box, click the option button Resource, select the correct processor type and name the resource. For example, the processor type REF543R refers to a REF 543 feeder terminal equipped with an resistance temperature device (RTD) module. Fig Defining the processor type resource Hardware version After selecting the processor type, click the Settings button in the dialog box (see Fig above) to define the correct hardware version (see Fig ). Do not click OK after selecting the correct hardware version (see Fig ), but wait until the next dialog box opens and click the option button Analog Channels (see Fig ). The hardware version number is included in the order number of the product. The order number is labelled on the marking strip on the front panel of the product. Example: Order No: REF543FC127AAAA Note that for REC 523, the selectable relay variants are given as order numbers, for example REC523C 033AAA. Refer to the technical reference manual of REC 523, see Section 1.8. Related documents) 27

28 1MRS MUM Fig Defining hardware version hw_variant Fig Selecting the dialog box for analog settings select_analog_channels Analog channels In the dialog box for defining analog channels (Fig ), click the option button for each channel in turn, and select the measuring device and signal type for the channels in use from the drop-down list. Select the option Not in use for other channels. 28

29 1MRS MUM Fig Defining the analog channel settings analog_channels Furthermore, define the technical data and measurements for the selected channels before the configuration is used in a real application. 29

30 1MRS MUM Technical data Fig Defining the rated values for the selected measuring device Measurements rated_values For information about the special measurements required for each function block, refer to the Technical Descriptions of Functions (see Section 1.8. Related documents). True RMS measurement and 2nd harmonic restraint measurements If the signal type selected for an analog channel is going to be measured by any measurement function block (MECU3A etc.), select the option True RMS mode in the Special Measurements dialog box. If the Inrush3 function block (3-phase transformer inrush and motor start-up current detector) is to be used, select the option 2nd Harmonic Restraint for the analog channels (IL1, IL2, IL3) used. 30

31 1MRS MUM SpecMeasIL1 Fig Selecting the required special measurement modes for phase current measurement Neutral current When the DEF2_ function block (directional earth-fault protection) is going to be used, select the option Intermittent earth-fault protection in the Special Measurements dialog box for the channel via which the current I 0 is measured. The intermittent earth-fault protection can be enabled for the maximum of two physical channels at a time. Note that the intermittent earth-fault protection requires the residual voltage for directional operation. Therefore, the channel for the residual voltage U 0 must be defined before the selection can be made. Unless intermittent earth-fault protection has been chosen, the following configuration error indication appears on the display of REF 54_, REM 54_ or RET 54_ ( # denotes the number of the analog channel in question): System: SUPERV Ch # error Fig Selecting the required special measurement modes for neutral current measurement SpecMeasIo 31

32 1MRS MUM Frequency When, for example, the function block MEFR1 (system frequency measurement) is in use, frequency measurement must be selected for the channel via which the voltage is measured for frequency measurement. For example Channel 10 (Voltage Transformer 4, Signal type U3), click the Measurements button in the Configuration of REF543 dialog box. The power quality function blocks PQCU3H and PQVO3H require frequency measurement for the channel that is connected to the FREQ_REF input, that is, the channel for frequency reference (for more information, refer to the manuals of PQCU3H and PQVO3H on the CD-ROM Technical Descriptions of Functions, see Section 1.8. Related documents). Furthermore, frequency protection must be selected if any of the function blocks SCVCSt_ or Freq1St_ is in use. SpecMeasUL1 Fig Selecting the required special measurement modes for frequency measurement Virtual channels In case no measuring devices are applied for measuring residual voltage (U 0 ) and neutral current (I 0 ), the virtual channels 11 and 12 can be used. If only one virtual channel is used, the channel is numbered as channel 11 regardless of whether residual voltage or neutral current is calculated. If both I 0 and U 0 are calculated, channel 11 is used for I 0S and channel 12 for U 0S. 32

33 1MRS MUM virtual_channels Fig Using virtual channels 11 and 12 in case no measuring devices are applied for measuring I 0 and U 0 In case of the virtual channels for calculating I 0 and U 0, phase currents and voltages must be associated with current and voltage measuring devices (see Fig and Fig ). Fig Associating phase currents with current measuring devices Summed_Ios 33

34 1MRS MUM Fig Associating phase voltages with voltage measuring devices Summed_Uos Digital inputs After a compiled configuration is downloaded to a device, it checks internally whether the analog channels are correctly configured regarding the analog inputs of function blocks. If the connected channels have been configured incorretly, the ERR output signal of the specific function block activates and the analog channel configuration error event (E48) is sent. Some function blocks have special error events that are explained in the corresponding function block manuals on the CD-ROM Technical Descriptions of Functions (see Section 1.8. Related documents). The filter time is set for each digital input of the device via the resource settings dialog box Binary Inputs. Inversion of the inputs can also be set. Note, however, that the inversion of an input cannot be seen from the configuration. For further information refer to the technical reference manual of RET 54_ or REC 523 (see Section 1.8. Related documents). 34

35 1MRS MUM Fig Defining the digital inputs Measurements BIN_INPUT When the MEPE7 function block (power and energy measurement) is used, the measuring mode must be selected via the resource settings dialog box Measurements. True RMS measurement must also be selected for the channels used by MEPE7. Note that the measuring modes can only be selected after the analog channels have been defined (see Fig ). 35

36 1MRS MUM Fig Selecting the measuring mode for power and energy measurement MEPE7 Condition monitoring Values for the circuit-breaker wear function blocks CMBWEAR 1 and 2 can be set via the resource settings dialog box Condition Monitoring. 36

37 1MRS MUM Fig Setting the values for circuit-breaker wear cbwear Resource for REF 54_ Release 2.5 or later, REC 523 revision F and RET 54_ The PLC type selected in the Configuration dialog box determines which processor types are available. To select the processor type and name the resource: 1. Select an object under the Physical Hardware tree and select Edit > Insert. 2. In the opening dialog box, click the option button Resource, select the correct processor type and name the resource. For example, the processor type REF543R refers to a REF 543 feeder terminal equipped with an RTD module. 37

38 1MRS MUM Fig Defining the processor type Hardware version processtype2.5 After selecting the processor type, click the Settings button in the dialog box (see Fig above) to define the correct hardware version (see Fig ). Do not click OK after selecting the correct hardware version (Fig ), but wait until the next dialog box opens and select the option Analog Channels (see Fig ). The hardware version number is included in the order number of the product. The order number is labelled on the marking strip on the front panel of the product. Example: Order No: REF543GC127AAAA Fig Defining the hardware version hardware2.5 38

39 1MRS MUM Fig Selecting the dialog box for analog settings Analog channels analog_settings2.5 In the dialog box for defining analog channels (see Fig ), click the option button for each channel in turn, and select the measuring device and signal type for the channels in use from the drop-down list. Select the option Not in use for other channels. Furthermore, the technical data and measurements for the selected channels are to be completed correctly before the configuration is used in a real application. Fig Defining the analog channels analog_channels2.5 39

40 1MRS MUM Technical data Fig Defining the rated values for the selected measuring device Measurements rated_values2.5 For information about the special measurements required for each function block, refer to the Technical Descriptions of Functions (see Section 1.8. Related documents). True RMS and 2nd harmonic restraint measurements If the signal type selected for an analog channel is going to be measured by any measurement function block (MECU3A etc.), the true RMS mode must be selected in the Special Measurements dialog box. Moreover, in case the Inrush3 function block (3-phase transformer inrush and motor start-up current detector) is to be used, the 2nd harmonic restraint must be selected for the analog channels (IL1, IL2, IL3) used. 40

41 1MRS MUM phase_measu2.5 Fig Selecting the required special measurement modes for phase current measurement Neutral current When the DEF2_ function block (directional earth-fault protection) is going to be used, intermittent earth-fault protection must be selected for the channel via which the current I 0 is measured. The intermittent earth-fault protection can be enabled for the physical channels I 0 and I 0b as well as for the virtual channels I 0s and I 0bs at the same time. The intermittent earth-fault protection requires the residual voltage for directional operation. Therefore, the channel for the residual voltage U 0 must be defined before the selection for I 0 measurement channels can be made. The amount of the U 0 channels used for the intermittent earth-fault protection is limited to one. The first available U 0 channel should be selected from the list: U 0, U 0b, U 0s and U 0bs. Unless intermittent earth-fault protection has been chosen correctly, a configuration error indication will appear on the error list of the Relay Download Tool. neutral_measu2.5 Fig Selecting the required special measurement modes for neutral current measurement 41

42 1MRS MUM Frequency When, for example, the function block MEFR1 (system frequency measurement) is in use, frequency measurement must be selected for the channel via which the voltage is measured for frequency measurement. For example Channel 10 (Voltage Transformer 4, Signal type U3), click the Measurements button in the Configuration of REF543 dialog box. The power quality function blocks PQCU3H and PQVO3H require frequency measurement for the channel that is connected to the FREQ_REF input, that is, the channel for frequency reference (for more information refer to the manuals of PQCU3H and PQVO3H on the CD-ROM Technical Descriptions of Functions, see Section 1.8. Related documents). Furthermore, frequency protection must be selected if any of the function blocks SCVCSt_ or Freq1St_ is in use. freq_measu2.5 Fig Selecting the required special measurement modes for frequency measurement Virtual channels The virtual channels can be used if no measuring devices are applied for measuring phase-to-phase voltages, residual voltage (U 0 ) and neutral current (I 0 ). The virtual channels selected for use are numbered from the channel number 11. For further information about the channel numbers of the calculated virtual channels, refer to the technical reference manual of the terminal in question (see Section 1.8. Related documents). An example of when the virtual channels can be used is shown in Fig

43 1MRS MUM virtual_channels2.5 Fig Using virtual channels if phase-to-phase voltages, residual voltage and neutral current measurement are not available The virtual channels are selectable according to the selections in the Analog Channels view. The selection of the virtual channels can be done in Virtual Channels view (see Fig ). 43

44 1MRS MUM select_virtual_channels2.5 Fig The selectable virtual channels when the configuration of the analog channel is as in Fig The special measurements are selectable for each used virtual channel (see Fig and Fig ). The special measurement view for the virtual channel Ios is shown in Fig The analog channels used for derivation and derivation equation are also shown. The analog channels are as in Fig Fig Special measurement view for the virtual channel Ios Ios_measu2.5 Special measurement view for the virtual channel U 12s is shown in the Fig The analog channels used for derivation and derivation equation are also shown. The analog channels are as in Fig

45 1MRS MUM Fig Special measurement view for the virtual channel U 12s. Ios_measu_2.5_2 Digital inputs After a compiled configuration is downloaded to a device, the device checks internally whether the analog channels are correctly configured regarding the analog inputs of function blocks. If the connected channels have been configured incorrectly, the ERR output signal of the specific function block activates and the analog channel configuration error indication appears on the error list of the Relay Download Tool. For more information, refer to Section 5.5. Downloading the configuration. The filter time is set for each digital input of the device via the resource settings dialog box Binary Inputs field. Inversion of the inputs can be set as well. Note, however, that the inversion of an input cannot be seen from the configuration. For further information, refer to the technical reference manual of the terminal in question (see Section 1.8. Related documents). Fig Defining the digital inputs digital_inputs2.5 45

46 1MRS MUM Measurements When the MEPE7 function block (power and energy measurement) is used, the measuring mode must be selected by clicking the option button Measurements in the resource settings dialog box. True RMS measurement must also be selected for the channels used by MEPE7. The measuring modes can only be selected after the analog channels have been defined (see Fig ). power&energy_measu2.5 Fig Selecting the measuring mode for power and energy measurement Condition monitoring Values for the circuit-breaker wear function blocks CMBWEAR 1 and 2 can be set via the resource settings dialog box by clicking the option button Condition Monitoring. 46

47 1MRS MUM Fig Setting the values for circuit-breaker wear wear2rle Tasks Programs and tasks Programs are associated with tasks via the dialog boxes Properties/Task and Properties/Program. To define task properties in the Relay Configuration Tool: 1. Select an object in the project tree. 2. Select Edit > Insert and define task name and type. One task may include several programs. Cyclic tasks are activated within a specific time interval and the program is executed periodically. As many as 10 POUs can be associated to a task. To define program properties in the Relay Configuration Tool: 1. Select a task in the project tree. 2. Select Edit > Insert and define program instance and type. The two dialog boxes below illustrate the association of a program type (Prot_Me) with a task (Task1) (see also Fig ). 47

48 1MRS MUM Fig Naming a cyclic task TASK1 Fig Associating the selected task with the desired program type Task interval PROT_ME Generally, operation accuracy is increased when task speed is increased, but at the same time, the load of the microprocessors is increased as well. Although the task speed can be freely chosen with the tool, it is necessary to define a maximum task execution interval for each function block. If not defined, the operation accuracy and operate times for protection functions cannot be guaranteed. The maximum task execution interval is based on test results and it has been used in the type testing of the function blocks. The recommended task execution interval quaranteed by the manufacturer can be found in technical data section in the technical description of each function block. Furthermore, certain function blocks, for example MEDREC16, must be tied to the task given by the manufacturer in order to enable the operation of these function blocks. For more information about the task execution intervals of function blocks, refer to the introduction chapter in the Technical Descriptions of Functions CD-ROM, see Section 1.8. Related documents. For microprocessor loads, refer to Section 5.5. Downloading the configuration. According to the standard, the Relay Configuration Tool offers a possibility to define the tasks on two different levels: 1. Each program organisation unit (POU) can be tied to a separate task. 2. Separate function block inside a POU can be tied to any task. 48

49 1MRS MUM However, the second alternative is not supported in the RED 500 environment; if a separate function block inside a POU is given a separate task definition, it is ignored when transferred to the device. This means that when the function blocks are being placed in different POUs, not only the category of the function (protection, control, and so on) but also the maximum task execution interval should be considered, since all function blocks inside a POU run at the same speed. Define the task execution interval for each task by selecting a task and by selecting Edit > Insert; click the Settings button in the opening dialog. For example, the task execution interval for Task1 in the figure below is defined as 10 ms, which means that the program Prot_Me is run 100 times per one second. The maximum number of tasks with different intervals is 4. The tool automatically modifies the task setting if the set network frequency is other than 50 Hz (see the Network Frequency text box in Fig ). For example at 60 Hz, 10 ms becomes ms. interval Fig Setting the task execution interval for a program If there is a need for several different tasks that control the same output relay, it is recommended that the output relay is controlled directly in the fastest task and other control commands are brought to that task via global variables. Example: Some protection function blocks can be run in the 5 ms task, some in the 10 ms task and some even using the 100 ms task. Still, all these function blocks use the same output relay. Another way to avoid also the software delays when communicating between the different tasks is to use a separate output relay for each protection task. Example: The trip signal from the 5 ms task is connected to High-Speed Power Output 1 and the trip signal from the 10 ms task to High-Speed-Power-Output 2. The outputs can then control the same opening coil of the circuit breaker Declaring variables The validity range of the declarations that are included in the declaration part should be local to the POU in which the declaration part is contained. However, variables that are declared to be global are only accessible to a POU via a 49

50 1MRS MUM VAR_EXTERNAL declaration. The type of a variable declared in a VAR_EXTERNAL block should agree with the type declared in the VAR_GLOBAL block of the associated program, configuration or resource. Program B Program A FB1 FB_X a y y b FB2 FB_Y VAR y:bool; FB1:FB_X; FB2:FB_Y; END_VAR FB1 FB_X a b FB2 FB_Y VAR FB1:FB_X; FB2:FB_Y; END_VAR Configuration C Program A Program B VAR_EXTERNAL x:bool; END_VAR VAR FB1:FB_X; END_VAR FB1 FB_X a x VAR_GLOBAL x:bool; END_VAR x b FB2 FB_Y VAR_EXTERNAL x:bool; END_VAR VAR FB2:FB_Y; END_VAR Fig Local and global variables The figure above illustrates the how variable values can be communicated among software elements either directly or via global variables. Variable values within a program can be communicated directly by connecting the output of one program element to the input of another, or via local variables, such as the variable y illustrated in the upper-left corner of the figure above. In the same configuration, variable values can be communicated between programs via global variables, such as the variable x illustrated in Configuration C in the figure above. In such a case, make sure that the global variable is only written from one location in the project. The global variable can still be read from several locations. According to the IEC , all the variables that have no explicit initializer are initialized with a data-type dependent default value. Despite of this, it is always recommended that the initial value is given explicitly. Naturally, the value to which each variable should be initialised depends on the logical function of the program. Table Default values according to data types Data type Default initial value ANY_REAL 0.0 ANY_INT 0 ANY_BIT 0 (=FALSE) TIME T#0s 50

51 1MRS MUM Especially the initial values of global variables are logically significant for the program. The user cannot choose the order in which tasks are initialised. This means that if a task reading a global variable is initialized before another task gives the variable its first value, it is important that an appropriate initial value has been selected for the global variable. CASE 1. Variables declaration VARIABLE WORKSHEET of logical POU ****************************************************************** VAR TRIPPING :BOOL := FALSE; BLOCK :BOOL := TRUE; TMP1 :BOOL := FALSE; END_VAR VAR_EXTERNAL PS1_4_HSPO1 :BOOL; (* Double pole high speed power output *) (* X4.1/10,11,12,13 *) PS1_4_HSPO2 :BOOL; (* Double pole high speed power output *) (* X4.1/15,16,17,18 *) PS1_4_HSPO3 :BOOL; (* Double pole high speed power output *) (* X4.1/6,7,8,9 *) END_VAR VAR_EXTERNAL TCS1_ALARM :BOOL; END_VAR ****************************************************************** GLOBAL VARIABLE WORKSHEET ****************************************************************** VAR_GLOBAL PS1_4_HSPO1 AT %QX :BOOL := FALSE; (* Double pole high speed power output X4.1/10,11,12,13 *) PS1_4_HSPO2 AT %QX :BOOL := FALSE; (* Double pole high speed power output X4.1/15,16,17,18 *) PS1_4_HSPO3 AT %QX :BOOL := FALSE; (* Double pole high speed power output X4.1/6,7,8,9 *) END_VAR VAR_GLOBAL TCS1_ALARM :BOOL := FALSE; END_VAR ****************************************************************** 51

52 1MRS MUM Global variables The physical contacts are defined in the Global Variables worksheet (Fig ). Declarations for the physical contacts are automatically defined when the correct hardware version of RE_ 54_ is selected. Declarations for the analog channels are created after the analog channel settings defined in the resource settings dialog box have been approved. The textual names of the inputs and outputs, for example BIO2-7_BI10IV (see the figure below), can be modified. Note, however, that the address (for example AT %IX :BOOL := TRUE) following the name may not be changed. Fig Global Variables worksheet global Local variables At the beginning of each programmable controller POU type declaration there should be at least one declaration part that specifies the types of the variables used in the organisation unit. The declaration part should have the textual form of one of the keywords VAR_INPUT, VAR_OUTPUT, VAR and VAR_EXTERNAL followed by one or more declarations separated by semicolons and terminated by the keyword END_VAR. All the comments you write must be edited in parentheses and asterisks:. (*******************************) (* Variable declaration *) (* of REF 541 *) (*******************************) 52

53 1MRS MUM Caution is required regarding comments and variable declarations. The following code example would be compiled successfully but because of the non-closed comment, the END_VAR - VAR_EXTERNAL couple is excluded and thus the channel numbers become local variables of the POU and they get the initial value zero: VAR (*AUTOINSERT*) NOC3Low_1 : NOC3Low; (* Erroneous nonclosed comment * END_VAR VAR_EXTERNAL (*AUTOINSERT*) U12 : SINT; (* Measuring channel 8 *) U23 : SINT; (* Measuring channel 9 *) U31 : SINT; (* Measuring channel 10 *) END_VAR Three examples of creating the textual declaration for different kinds of graphical programs are given below. Example 1: POU type: FBD program Function block type declaration: VAR SIGNAL1 SIGNAL2 SIGNAL3 SIGNAL4 END_VAR :BOOL :=FALSE; :BOOL :=FALSE; :BOOL :=FALSE; :BOOL :=FALSE; and_or_gates Fig Function block image 53

54 1MRS MUM Example 2: POU type: NOC3Low, manufacturer-dependent function block Function block type declaration: VAR_INPUT IL1 :SINT :=0; (* Analog channel *) IL2 :SINT :=0; (* Analog channel *) IL3 :SINT :=0; (* Analog channel *) BS1 :BOOL :=FALSE; (* Blocking signal *) BS2 :BOOL :=FALSE; (* Blocking signal *) TRIGG :BOOL :=FALSE; (* Triggering *) GROUP :BOOL :=FALSE; (* Grp1/Grp2 select *) DOUBLE :BOOL :=FALSE; (* Doubling signal *) BSREG :BOOL :=FALSE; (* Blocking registering *) RESET :BOOL :=FALSE; (* Reset signal *) END_VAR VAR_OUTPUT START :BOOL :=FALSE; (* Start signal *) TRIP :BOOL :=FALSE; (* Trip signal *) CBFP :BOOL :=FALSE; (* CBFP signal *) ERR :BOOL :=FALSE; (* Error signal *) END_VAR Fig Function block image of NOC3Low NOC3Low_b 54

55 1MRS MUM Example 3: POU type: Programmer-dependent FBD function block CONDIS Function block type declaration: Fig condisv Type declaration of the programmer made function block CONDIS 55

56 1MRS MUM Fig FBD worksheet contents of the CONDIS function block condis Fig Use of the programmer made function block CONDIS condis_control In the Example 3 above, part of the configuration has been separated to a programmer-made function block called CONDIS. Such function blocks may not be given names already belonging to library functions blocks or IEC standard function blocks. The function block CONDIS has been used like any other function block in the graphical program. It must also be remembered that a function block with an instance named by the programmer can only be inserted to the project once. 56

57 1MRS MUM 5.3. Compiling project In the Relay Configuration Tool s Make menu, select the command Build Project to compile the whole project for the first time after editing. This means compiling all POUs, global variables, resources and so on. In the Make menu, use the Make command to compile the worksheets that have been edited. The changed worksheets are marked with an asterisk, *, in the project tree editor. The Make command is the standard mode for compiling and should normally be used when you have finished editing. It is recommended that the Build Project command is given once more just before downloading the configuration to the product. In the Relay Configuration Tool you can view the execution order of the different functions or function blocks in your worksheet. The execution order corresponds to the intermediate PLC code created while compiling. Note that the execution order can only be seen if you have already compiled the worksheet by using the menu command Make > Compile Worksheet Add-on protocol If an add-on protocol is used, the protocol mapping must be created by using the Protocol Mapping Tool (PMT). For more information, refer to the documents in Section 1.8. Related documents. Table Available add-on protocols Relay version Modbus DNP 3.0 IEC REF 54_ Release 2.5 X REF 54_ Release 3.0 X X X REF 54_ Release 3.5 X X X REM 54_ Release 2.5 X RET 54_ Release 3.0 X X X REC 523 does not have any add-on protocols, but the device includes fixed protocols according to the device s software configuration. In REC 523 revision F, the protocol interface can be modified by using the Protocol Mapping Tool. In earlier releases, the protocol interface can be modified by using the Protocol Editing Tool. These tools are included in CAP 505. For more information on the REC 523 protocols, refer to the technical reference manual of REC 523 (see Section 1.8. Related documents) Downloading the configuration After the configuration has been built and succesfully compiled in the Relay Configuration Tool and the MIMIC configuration has been designed, the project can be downloaded to the device. 57

58 1MRS MUM The parts of the project to be downloaded are selected via a dialog box. The MIMIC configuration and the Relay Configuration Tool project can be downloaded separately. The project can also be downloaded separately as a compressed file. This enables later uploading of the project from the device. The compressed file is automatically created if the check box RCT project has been selected (see Fig ). The target device has an inherent limitation over the size of a stored project file. If this is exceeded, the tool interrupts the downloading and issues a warning. It is useful to include some information of the project in the file by giving, for example, the name of the designer, the date and the version or other description of the configuration. To add project information, select File > Project Info in the Relay Configuration Tool. Add-on protocols (for example Modbus and IEC ) of the relay terminal are activated in the relay according to Add-On protocol selection in object properties. Fig Selecting RCT project (for REC 523, the mimic configuration is not available) When the configuration is downloaded, the total CPU load in percent can be checked via the parameter Config. capacity. In the Relay Setting Tool s Main menu view, select the Configuration tab and the General subtab to view Config. capacity parameter (on the device, select MAIN MENU/Configuration/ General/Config. capacity). If the load exceeds 100%, the downloading fails, an indication Failed is displayed in the assisting window of the REF 54_, 58

59 1MRS MUM REM 54_ or RET 54_ display, and a message appears in the CAP 505. The exceeded CPU load can also be read via the parameter after a failed downloading, that is, the load value can be for example 115%. Whenever downloading fails, a storing sequence cannot be started but the device must be reset before next downloading. Moreover, the device is automatically reset after a failed downloading when the download dialog box in the Relay Download Tool is closed. Note that the exceeded CPU load must be checked before resetting; after the device is restarted, the parameter Config. capacity only shows the load of the previous configuration that was downloaded succesfully and has become valid again REF 54_ Release 2.5, RET 54_ and REC 523 revision F additions The REF 54_ Release 2.5 and later, REC 523 revision F and RET 54_ includes the following functions supported by the Configuration Download Tool: Relay and configuration tool compatibility checking Improved configuration error reporting Easier identification of the relay configuration Compatibility checking The download tool verifies that the connected relay matches the type and revision set in the relay configuration. If a mismatch occurs, downloading is not allowed. Fig Relay type mismatch when downloading the configuration comp The download tool also prevents downloading, if the configuration has been modified after the last compilation. 59

60 1MRS MUM Improved configuration error reporting After downloading the configuration, the relay checks, that all the function block specific requirements regarding analog channel configuration and task cycle time are fulfilled. If errors are detected, a list containing all errors is shown. The list contains the name of the function block that reported the error and a plain text error description. The error list can be copied to the clipboard and printed by using any text editor for easy reference when correcting the configuration. Fig Example of an error list when downloading an incorrect configuration Configuration identification The relay contains parameters for configuration identification: Title Author Last modification date Last download date of the configuration program A parameter is also included to identify the bay in which the configuration is used. The title and author are set from the File > Project info menu of the Relay Configuration Tool. The bay name is taken from the bay object in the project structure navigator or from the protection and control object, if no bay object is used. The last download/modification date parameters are set automatically. The Download Tool shows the identification data of the present configuration and the new configuration, and asks the user to verify, that the present configuration can be overwritten before proceeding with the download. err 60

61 1MRS MUM The configuration identification data can also be viewed from the relay (menu path Information/Configuration) and the Relay Setting Tool (open the Information tab and select the Configuration subtab). Note that the relay stores a maximum of 15 characters for each configuration identification parameter, although more characters are allowed in the Relay Configuration Tool. Fig Relay configuration identification trace 61

62 62

63 1MRS MUM 6. Main configuration rules 6.1. General Make sure that all analog signals are connected and all necessary inputs and outputs are wired. Note that the outputs of function blocks may not be connected together. There are also many other FBD programming rules to follow. One of the most typical rules is not to use the wired-or connection. All signals that are connected to the same output signal (both output relays and horizontal communication outputs) must be connected via an OR gate (see Fig ). I> I>> PS1_4_HSPO1 PS1_4_HSPO1 I> I>> TRIP TRIP OR PS1_4_HSPO1 "wired-or" structure is not allowed an explicit Boolean "OR" block is required instead Fig Use of an explicit Boolean OR gate (on the right) ORgate 6.2. Digital inputs and outputs Digital inputs and outputs of RED 500 devices are implemented as directly represented global variables. As such, they are special cases and their use in the configuration is limited. Directly represented variables are declared in the Global Variables sheet of the project tree. They can be recognized by the AT keyword as in the examples below. BIO1_5_BI1 AT %IX :BOOL := FALSE; ( *Binary input X5.1/1,2 *) BIO2_7_PO1 AT %QX :BOOL := FALSE; ( *Single pole output X7.1/17,18 *) Note that the parts of the line following the AT keyword may not be changed. Only the name of the signal, that is, the part before the AT keyword, may be changed if required. If the names are adapted to the logical meanings of the signals, the user is encouraged to create and to follow a naming convention. The name should indicate, apart from the logical meaning, whether the signal is an input or output signal. Examples of such names following a naming convention could be: Q9_close_sta_IN AT %IX :BOOL := FALSE; (* Binary input X5.1/1,2 *) Q9_close_cmd_OUT AT %QX :BOOL := FALSE; (* Single pole output X7.1/17,18 *) Access direction for the directly represented variables is restricted by their purpose. This means that a digital input can be read but not written, see Fig below. Accordingly, an output can be written but not read. Note that an input can be read from several locations within a worksheet and even from any program organisation unit within the configuration, whereas an output can only be written from one location at a time. 63

64 1MRS MUM Fig Digital3 Neither writing a digital input nor reading a digital output is allowed 6.3. Explicit feedback path A feedback path exists on the FBD worksheet when an output of a function block is used as an input to a function block that precedes it in the execution order. There are two types of feedback paths, an explicit and an implicit feedback loop (see Fig and Fig below). It is strongly recommended that explicit feedback loops are changed to implicit loops by using a feedback variable. The Relay Configuration Tool can detect explicit loops during compilation. If you click the checked command Display warnings in the Make menu, the compiler gives warnings about the detected explicit feedback loops. To view the feedback loops, select the checked command Highlight feedback in the Layout menu. The execution order of functions compared to the expected behaviour may in some cases dictate where the feedback variable should be added (for instructions on how to view the execution order, refer to Section 6.7. Execution order). The initial value of the feedback variable should also be selected with care. 64

65 1MRS MUM Fig Explicit feedback loop is detected and highlighted ExplFeedbck Fig Implicit feedback via the local variable FEEDBACK ImplFeedbck 6.4. Analog inputs Analog channels defined in the resource can be connected to the analog inputs of application function blocks on a code body worksheet. Most of the function blocks with several analog inputs support unconnected inputs. For example, in Fig below, the function block NOC3Low operates on only two inputs. The third and unused input constantly measures a zero current amplitude. This function block only requires that at least one of the three inputs is connected. On the other hand, certain function blocks require that all analog inputs are connected. An example of such a function block is OV3Low (see Fig below). If the analog channel requirements of a function block are violated, a configuration error is generated. For more information on how analog inputs are expected to be connected, refer to the function block manuals on the CD-ROM Technical Descriptions of Functions, see Section 1.8. Related documents. 65

66 1MRS MUM Analog channels connected to application function blocks may not be changed runtime. Therefore, do not use any selectors between analog channels and function blocks. Fig analog_inputs3 Connecting analog inputs of application function blocks. Do not use a selector to switch between channels Error outputs of application function blocks If a configuration for a function block is not correct, its ERR output is activated immediately after configuration downloading and the function block is forced to the Not in use mode. In this case, application function blocks that have the Operation mode parameter in their actual setting menu display the Not in use operation mode, regardless of which mode has been selected for the parameter in the setting group menu. Currently, with most function blocks, this will result in an automatic resetting, without storing, of the relay. The automatic reset does not occur in REM 54_. The error signals of all application function blocks should be collected together via an OR gate and connected to, for example, an HMI alarm indication of REF 54_ or REM 54_, that is, an MMIALAR_ function block. Detecting any untreated configuration errors is fast and easy when the error signals of all application function blocks are collected together via an OR gate and connected to MMIALAR_ function block. Configuration errors typically originate from missing special measurements, the type, order or number of analog channels connected to function blocks, or task interval requirements. 66

67 1MRS MUM 6.6. Warnings In case of the indication Warning: Instance xx is never used in connection with compilation, remove the corresponding instances of the function block from the variables worksheet of the POU. The tool does not give a warning for unused variables, which is why they are recommended to be removed manually. When a global variable is added to a sheet as a copy-paste -function, the Global option button has to be chosen (see figure below - properties can be accessed by double-clicking the right mouse button); otherwise the variable becomes a local variable of the POU, which is due to the auto-insert feature of the tool (global variable = VAR_EXTERNAL, local variable = VAR). Fig Copying a global variable to a worksheet of a POU radio 6.7. Execution order After compilation, check the execution order in relation to the calling sequence of POUs by using the Layout Execution Order function. Note, however, that although the connection of simple variables to each other generates code, the execution order cannot be seen by means of the Layout Execution Order function. If the MOVE function is used instead of direct connection, the execution order can be utilised in concluding whether the result is desirable, for example, the reading and writing order of the variables. Fig Direct connection of variables and a connection via the MOVE function MoveExpl 67

68 1MRS MUM EXECUTIObw Fig The INTERLOCKING variable is updated (TMP1) during the task execution cycle (see the execution order 1,2,3) In addition, the execution order may be illogical or even incorrect considering the functionality. Fig The implicit feedback (TMP1) delays the updating of the INTERLOCKING variable by one task execution cycle EXECUTE2bw 6.8. F-key The freely programmable F-key of REF 54_, REM 54_ and RET 54_ is declared as VAR_GLOBAL in the global variable worksheet as follows: F001V021:BOOL:=0; (* (R, W) Free configuration point (F-key) *) The F-key parameter can be added to the configuration logic as an external variable (VAR_EXTERNAL). 68

69 1MRS MUM medrec6 Fig Example of using F-key with the disturbance recorder function block MEDREC16 The variables below are internal variables of the system and are thus not recommended to be used like the F-key parameter. F001V011:BOOL:=0; (* (W) Resetting of operation indications *) F001V012:BOOL:=0; (* (W) Resetting of operation indications & latched output signals *) F001V013:BOOL:=0; (* (W) Resetting of operation indications, latched output signals & *) waveform memory F001V020:BOOL:=0; (* (W) Resetting of accumulated energy measurement *) F002V004:BOOL:=0; (* (R, W) Control: Interlocking bypass mode for all control objects *) (Enables all) F002V005:USINT:=0; (* (W) Control: Recent control position *) F002V006:BOOL:=0; (* (W) Control: Virtual LON input poll status *) F900V251:BOOL:=0; (* (W) Control: Execute all command for selected objects (inside *) module) F900V252:BOOL:=0; (* (W) Control: Cancel all command for selected objects (inside *) module) F000V251:BOOL:=0; (* (W) Control: Execute all command for selected objects (inside *) module) F000V252:BOOL:=0; (* (W) Control: Cancel all command for selected objects (inside module) *) 69

70 70

71 1MRS MUM 7. Engineering tips 7.1. Horizontal communication This example includes four (4) bays. The logic is basically the same in every bay. The intention of this guideline is to point out how to ensure the horizontal inter-bay communication, including correct state indication of control objects via LON communication. The logic also includes an alarm function in case of a broken fibre optic. Incorrect updating of interlocking information blocks the control of objects, but the blocking can be bypassed by setting the device to the bypass mode Guideline for using LON NV-variables in PLC logic COMM_IN Communication between terminals is executed by using the communication input and output signals (global variables COMM_IN_ and COMM_OUT_). The logic must be designed in a Relay Configuration Tool project. The LON network variable bindings can be created with the LON Network Tool. Communication inputs and outputs are bound to each other on a one-to-one basis by means of unacknowledged repeated unicast service. The signals are named so that the number at the end of COMM_OUT_ (for example COMM_OUT2) denotes the bay to which the signal is sent. Accordingly, the number at the end of COMM_IN_ denotes the bay from which the signal is received. This way, COMM_OUT2 of bay 1 is bound to COMM_IN1 of bay 2. COMM_IN_ signals are converted into Boolean logic mode by INT2BOOL function blocks. The B0 output signal (BLOCK1) in an INT2BOOL function block is used for blocking the control of objects except for the one that is sending the signal. In other words, only one object can be controlled at a time. Furthermore, Comm-Check_ signals are used for checking the condition of fibre optics. Signals for bay interlocking are also received. See Fig

72 1MRS MUM Fig Example of the COMM_IN logic comm_in COMM_OUT Communication signals sent from one bay to other bays include the reservation of control objects, updating of communication output signals and some indications needed in other bays. Overall, digital signals are sent via LON and converted from Boolean logic to unsigned integer (UINT, 16 bits) values. 72

73 1MRS MUM Fig Example of the COMM_OUT logic comm_out Cyclic sending generation The logic below shows an example of how the cyclic sending of communication output signals can be generated. The idea is to generate a boolean signal with a 5-second pulse duration and a 50-percent duty cycle. update all Fig Example of generating the cyclic sending of communication output signals 73

74 1MRS MUM Cyclic communication check Timers check the horizontal communication The timers activate an alarm signal as a result of failed communication (Bay Comm_Failed) 15 seconds after the new value of a Comm-Check_ signal has been received. Comm_Check_ signals are updated every 5 seconds, which affects the TON timer functions thus preventing the activation of Q output signals. If the communication fails, all four bays are blocked. Fig Cyclic communication check check Blocking If horizontal communication has failed, the BLOCK2 signal is sent to every controllable function block to prevent the control of local objects. Furthermore, the HMI alarm indication 8 (in REF 54_, REM 54_ or RET 54_) is activated. The BLOCK1 signal is used to create a mutual exclusion effect between bays. The signal is activated by horizontal communication when a control object is selected in one of the other bays. 74

75 1MRS MUM Fig Blocking the control of objects BLOCK Control of objects The control of an object, for example a breaker, can be executed if the BLOCK input is not active (TRUE). Accordingly, an object cannot be controlled during the reservation of other objects (in the same bay or in other bays) or the failing of horizontal communication. However, the blocking can be bypassed by setting the terminal to the bypass mode (MAIN MENU/Control/General/Interlocking Bypass). The bypass mode overrides interlockings provided the bypass signal is included in the logic (see also Section Bypass mode). Fig Defining the bypass mode for the control object Q1 75

76 1MRS MUM Bypass mode The bypass mode signal can be generated in the logic via the COLOCAT function block. After activation of the bypass mode, the BYPASS signal is active and therefore prevents activation of the BLOCK input. Fig Generation of the bypass mode signal bypass 7.2. Events from the measurement function blocks SPA protocol used Measurement values have to be polled because they are not sent with events. Thereby the delta supervision events of the measurement function blocks can be masked off. If limit supervision is set to be done by RTU, the limit event sending must be allowed in event masks. In this case, the client is informed of the activation and resetting of each limit with the corresponding event code numbers. LON protocol used Each measured variable is individualized by an IEC address. Measurement values and the corresponding IEC addresses are sent to a client, for example to MicroSCADA, with both delta supervision events and limit supervision events. The limit supervision events are not recommended to be masked off if limit supervision is used. When the warning and alarm limit supervision is active, the priority for limit event sending is higher than that for delta event sending if both type of events are sent concurrently. Concurrent event sending appears, for example, when a measured value changes considerably during a short period, for example when a circuit breaker is closed or opened. This causes problems if limit supervision events have been masked off since the client does not receive all measurement values even if major changes have taken place. 76

77 1MRS MUM 8. APPENDIX A: Relay configuration procedure 1. Create a new project 2. Create a tree structure a) Libraries b) Logical POU framework (programs and function blocks) c) Physical Hardware i) configuration ii) resource - hardware version - used analog channels and measurement signal types - digital inputs - power and energy measurement - condition monitoring (circuit breaker breaker wear) iii) tasks - connection between program and task - task interval d) Logical POU contents 3. Design logics 4. Check variable declarations a) Data types and initialisers b) Instances of functions and function blocks c) Variable categories i) VAR - END_VAR ii) VAR_EXTERNAL - END_VAR iii) VAR_INPUT - END_VAR iv) VAR_OUTPUT - END_VAR v) VAR_GLOBAL - END_VAR 5. Compile a project 6. If an add-on protocol (DNP 3.0 or Modbus) is used, create protocol mapping. 7. Download it to the device 77

78 78

79 1MRS MUM 9. APPENDIX B: Specification for REF 54_ feeder terminal configuration 9.1. General data Project name: Date: This specification suitable for bays: Substation name: Feeder terminal type: Software revision Order number: REF54 (for example REF543HC127AAAA) Handled by: Company: Telephone number: Fax number: This document serves as a technical specification of substation protection and is used for the configuration of REF 54_ feeder terminals. Special requirements can be specified under Further information at the bottom of each page. 79

80 1MRS MUM 9.2. Electrotechnical data Analog inputs Table Analog input channel connections Measuring devices that can be connected to the corresponding analog Channel measuring channels 1 Rogowski sensor, voltage divider or general measurement Current transformer, Rogowski sensor, voltage divider or general measurement 6 Current transformer Voltage transfomer, Rogowski sensor, voltage divider or general measurement Further information: 80

81 SIMX2.fh8 MIMX1.1.fh8 1MRS MUM Module type Board Terminal number Connected object Signal type MIM X V V V V ,2A 1A 1A 5A 1A 5A 1A 5A 1A 5A Ch 10 Ch 9 Ch 8 Ch 7 Ch 6 Ch 5 Ch 4 Ch 3 Ch 2 X1.1:25, X1.1:27 X1.1:22, X1.1:24 X1.1:19, X1.1:21 X1.1:16, X1.1:18 X1.1:13, X1.1:14, X1.1:15 X1.1:10, X1.1:11, X1.1:12 X1.1:7, X1.1:8, X1.1:9 X1.1:4, X1.1:5, X1.1:6 X1.1:1, X1.1:2, X1.1:3 VT4 VT3 VT2 VT1 CT5 CT4 CT3 CT2 CT1 MIMX1.1 Module type Board Terminal number Connected object Signal type SIM X2.1 DIFF Ch 10, sensor X2.1 X2.2 DIFF Ch 9, sensor X2.2 X2.3 DIFF Ch 8, sensor X2.3 X2.4 DIFF Ch 7, sensor X2.4 X2.5 DIFF Ch 5, sensor X2.5 X2.6 DIFF Ch 4, sensor X2.6 X2.7 DIFF Ch 3, sensor X2.7 X2.8 DIFF Ch 2, sensor X2.8 X2.9 DIFF Ch 1, sensor X2.9 The measuring device can be connected exclusively to the analog channels of either MIM or SIM type modules. Ten channels are available. Simx2 Further information: 81

82 BIO1X5.1.fh8 PS1X4.2.fh8 1MRS MUM System frequency Digital inputs 50 Hz 60 Hz Module type Board Terminal number Connected object PS1 (REF541, REF543) X PS1_4_BI1 X4.2:1, X4.2:2 1) 4 5 PS1_4_BI2 X4.2:4, X4.2:5 1) 6 7 PS1_4_BI3 X4.2:6, X4.2:7 1) 1) Digital input / counter input PS1X4.2 Module type Board Terminal number Connected object BIO1 X BIO1_5_BI1 BIO1_5_BI2 X5.1:1, X5.1:2 X5.1:2, X5.1: BIO1_5_BI3 BIO1_5_BI4 X5.1:4, X5.1:5 X5.1:5, X5.1: BIO1_5_BI5 BIO1_5_BI6 X5.1:7, X5.1:8 X5.1:8, X5.1: BIO1_5_BI7 BIO1_5_BI8 X5.1:10, X5.1:11 X5.1:11, X5.1: BIO1_5_BI9 BIO1_5_BI10 BIO1_5_BI11 X5.1:13, X5.1:14 X5.1:15, X5.1:16 X5.1:17, X5.1:18 1) 1) 1) 1) Digital input / counter input BIO1X5.1 Further information: 82

83 BIO2X7.1.fh8 BIO1X5.2.fh8 1MRS MUM Module type Board Terminal number Connected object BIO1 X BIO1_5_BI12 X5.2:1, X5.2:2 1) 1) Digital input/ counter input/ time sync BIO1X5.2 Module type Board Terminal number Connected object BIO2 (REF543, REF545) X BIO2_7_BI1 BIO2_7_BI2 X7.1:1, X7.1:2 X7.1:2, X7.1: BIO2_7_BI3 BIO2_7_BI4 X7.1:4, X7.1:5 X7.1:5, X7.1: BIO2_7_BI5 BIO2_7_BI6 X7.1:7, X7.1:8 X7.1:8, X7.1: BIO2_7_BI7 BIO2_7_BI8 X7.1:10, X7.1:11 X7.1:11, X7.1: BIO2_7_BI9 X7.1:13, X7.1:14 1) BIO2_7_BI10 X7.1:15, X7.1:16 1) 1) Digital input / counter input BIO2X7.1 Further information: 83

84 PS2X4.1.fh8 PS1X4.1.fh8 1MRS MUM Digital outputs Module type Connected object Terminal number Board PS1 (REF541, REF543) 1) X4.1:1, X4.1:2 1) PS1_4_ACFail PS1_4_TempAlarm + Mains - X X4.1:3, X4.1:4, X4.1:5 IRF X X4.1:6, X4.1:7, X4.1:8, X4.1:9 PS1_4_HSPO ) X4.1:10, X4.1:11, X4.1:12, X4.1:13 PS1_4_HSPO1 PS1_4_TCS1 TCS ) X4.1:15, X4.1:16, X4.1:17, X4.1:18 PS1_4_HSPO2 PS1_4_TCS2 TCS ) Please indicate whether the trip circuit supervision inputs will be configured to use or not PS1X4.1 Module type Connected object Terminal number Board PS2 (REF545) 1) X4.1:1, X4.1:2 1) PS2_4_ACFail PS2_4_TempAlarm + Mains - X X4.1:3, X4.1:4, X4.1:5 IRF X X4.1:6, X4.1:7, X4.1:8, X4.1:9 PS2_4_HSPO ) X4.1:10, X4.1:11, X4.1:12, X4.1:13 PS2_4_HSPO1 PS2_4_TCS1 TCS ) X4.1:15, X4.1:16, X4.1:17, X4.1:18 PS2_4_HSPO2 PS2_4_TCS2 TCS ) Please indicate whether the trip circuit supervision inputs will be configured to use or not PS2X4.1 Further information: 84

85 PS2X4.2o.fh8 PS1X4.2o.fh8 1MRS MUM Module type PS1 (REF541, REF543) Connected object Terminal number Board X4.2 8 X4.2:8, X4.2:9, X4.2:10, X4.2:11 PS1_4_HSPO X4.2:12, X4.2:13, X4.2:14, X4.2:15 PS1_4_HSPO X4.2:16, X4.2:17, X4.2:18 PS1_4_SO1 18 PS1X4.2o Module type PS2 (REF545) Connected object Terminal number Board X4.2 1 X4.2:1, X4.2:2, X4.2:3, X4.2:4 X4.2:5, X4.2:6, X4.2:7, X4.2:8 X4.2:9, X4.2:10, X4.2:11, X4.2:12 X4.2:13, X4.2:14, X4.2:15, X4.2:16 PS2_4_HSPO4 PS2_4_HSPO5 PS2_4_HSPO6 PS2_4_HSPO X4.2:17, X4.2:18 PS2_4_HSPO PS2X4.2o Further information: 85

86 BIO1X6.2.fh8 BIO1X5.2o.fh8 1MRS MUM Module type BIO1 Connected object Terminal number Board X5.2 3 X5.2:3, X5.2:4 BIO1_5_SO1 4 5 X5.2:5, X5.2:6 BIO1_5_SO X5.2:7, X5.2:8, X5.2:9 BIO1_5_SO X5.2:10, X5.2:11, X5.2:12 BIO1_5_SO X5.2:13, X5.2:14, X5.2:15 BIO1_5_SO X5.2:16, X5.2:17, X5.2:18 BIO1_5_SO6 17 BIO1X5.2o Module type BIO1 (REF545) Connected object Terminal number Board X6.2 3 X6.2:3, X6.2:4 BIO1_6_SO1 4 5 X6.2:5, X6.2:6 X6.2:7, X6.2:8, X6.2:9 BIO1_6_SO2 BIO1_6_SO X6.2:10, X6.2:11, X6.2:12 X6.2:13, X6.2:14, X6.2:15 BIO1_6_SO4 BIO1_6_SO X6.2:16, X6.2:17, X6.2:18 BIO1_6_SO6 17 BIO1X6.2 Further information: 86

87 BIO2X7.2.fh8 BIO2X7.1o.fh8 1MRS MUM Module type BIO2 (REF543, REF545) Connected object Terminal number Board X7.1 X7.1:17, X7.1:18 BIO2_7_PO BIO2X7.1o Module type Connected object Terminal number Board BIO2 (REF543, REF545) X7.2:1, X7.2:2 BIO2_7_PO2 X X7.2:3, X7.2:4, X7.2:5, X7.2:6 BIO2_7_PO X7.2:7, X7.2:8, X7.2:9, X7.2:10 BIO2_7_PO X7.2:11, X7.2:12, X7.2:13, X7.2:14 BIO2_7_PO X7.2:15, X7.2:16, X7.2:17, X7.2:18 BIO2_7_PO BIO2X7.2 Further information: 87

88 RTD1X6._.fh8 1MRS MUM RTD module RTD/analog inputs Module type Board Terminal number 1) Connected object RTD1 (REF541, REF543) X SHUNT + - DIFF RTD1_6_AI1 X6.1:1, X6.1:2, X6.1: SHUNT - + DIFF RTD1_6_AI2 X6.1:5, X6.1:6, X6.1: SHUNT + - DIFF RTD1_6_AI3 X6.1:8, X6.1:9, X6.1: SHUNT - + DIFF RTD1_6_AI4 X6.1:12, X6.1:13, X6.1: SHUNT + - DIFF RTD1_6_AI5 X6.1:15, X6.1:16, X6.1:17 X SHUNT - + DIFF RTD1_6_AI6 X6.2:1, X6.2:2, X6.2: SHUNT + - DIFF RTD1_6_AI7 X6.2:4, X6.2:5, X6.2: SHUNT - + DIFF RTD1_6_AI8 X6.2:7, X6.2:8, X6.2:9 1) Current transducer / voltage transducer / resistance sensor RTD1X6._ Further information: 88

89 RTD1X6.2.fh8 1MRS MUM RTD outputs Module type Connected object Terminal number Board RTD1 (REF541, REF543) X6.2:11, X6.2:12 RTD1_6_AO1 + ma - X X6.2:13, X6.2:14 RTD1_6_AO2 + ma X6.2:15, X6.2:16 RTD1_6_AO3 + ma X6.2:17, X6.2:18 RTD1_6_AO4 + ma RTD1X6.2 Further information: 9.3. Functionality Order number REF54 (for example REF543HD127AAAA) 89

90 1MRS MUM Application function blocks used The lists below represent the full set of function blocks, but the selected functionality level (indicated by a letter in the order number, for example REF543HC127AAAA) determines the function blocks available for the configuration. Note that optional functions, that is, those selectable in addition to the functions included in a functionality level, are listed separately. Protection AR5Func Freq1St2 NEF1Inst ROV1High CUB3Low Freq1St3 NOC3Low ROV1Inst DEF2Low Freq1St4 NOC3High SCVCSt1 DEF2High Freq1St5 NOC3Inst SCVCSt2 DEF2Inst Fusefail OV3Low TOL3Cab DOC6Low Inrush3 OV3High TOL3Dev DOC6High MotStart PSV3St1 UV3Low DOC6Inst NEF1Low PSV3St2 UV3High Freq1St1 NEF1High ROV1Low Measurement MEAI1 MEAI7 MECU1A MEPE7 MEAI2 MEAI8 MECU1B MEVO1A MEAI3 MEAO1 MECU3A MEVO1B MEAI4 MEAO2 MECU3B MEVO3A MEAI5 MEAO3 MEDREC16 MEVO3B MEAI6 MEAO4 MEFR1 Control COCB1 COIND1 COSW1 MMIALAR6 COCB2 COIND2 COSW2 MMIALAR7 COCBDIR COIND3 COSW3 MMIALAR8 CO3DC1 COIND4 COSW4 MMIDATA1 CO3DC2 COIND5 MMIALAR1 MMIDATA2 CODC1 COIND6 MMIALAR2 MMIDATA3 CODC2 COIND7 MMIALAR3 MMIDATA4 CODC3 COIND8 MMIALAR4 MMIDATA5 CODC4 COLOCAT MMIALAR5 CODC5 90

91 1MRS MUM Condition monitoring CMBWEAR1 CMBWEAR2 CMCU3 CMGAS1 CMGAS3 CMSCHED CMSPRC1 CMTCS1 CMTCS2 CMTIME1 CMTIME2 CMTRAV1 CMVO3 Communication EVENT230 General INDRESET SWGRP5 SWGRP11 SWGRP17 MMIWAKE SWGRP6 SWGRP12 SWGRP18 SWGRP1 SWGRP7 SWGRP13 SWGRP19 SWGRP2 SWGRP8 SWGRP14 SWGRP20 SWGRP3 SWGRP9 SWGRP15 SWGRP4 SWGRP10 SWGRP16 Optional functions COPFC CUB1Cap CUB3Cap FLOC OL3Cap PQCU3H PQVO3H PQVO3Sd Communication Protocol used: Port X3.2 Port X3.3 Modbus LON DNP 3.0 SPA IEC SPA 91

92 1MRS MUM Virtual channels Virtual meas. Channel number Analog meas. 1 Channel number Analog meas. 2 Channel number Analog meas. 3 Channel number I 0s I L1 I L2 I L3 I 0bs I L1b I L2b I L3b U 0s U 1 U 2 U 3 U 0bs U 1b U 2b U 3b U 12s U 1 U 2 U 23s U 2 U 3 U 31s U 1 U 3 U 12bs U 1b U 2b U 23bs U 2b U 3b U 31bs U 1b U 3b Further information: 92

93 1MRS MUM 9.4. Relay MIMIC configuration Illustration of the system, MIMIC diagram Symbol used closed open undef. 0 0 undef. 1 1 Disconnector: (truck symbols) Circuit breaker: Earth switch: Further information: 93

94 1MRS MUM Alarm LEDs Fill in the table below to describe the legend text used as well as the flashing sequence and colour of the LEDs. Table LED OFF state Descriptions for legend texts and LEDs ON state Text (max. 16 characters) Colour Flashing seq. Text (max. 16 characters) Colour Flashing seq off green yellow red latched, blinking latched, steady non-latched, blinking Interlocking Control test mode off green yellow red latched, blinking latched, steady non-latched, blinking X X X X Further information: 94

95 1MRS MUM 9.5. Functionality logic Please specify the required special PLC logic functionality (see the examples below), by drawing or otherwise, on separate sheets and enclose all additional information with this document (Specification for Feeder Terminal Configuration). Example 1: Earthing sequence Earthing of the outgoing feeder can be done by a circuit breaker when an earthing sequence is activated, an earthing switch is earthed and no voltage is measured. If all conditions are fulfilled, the circuit breaker can be closed after 1 second. The figure below shows the implementation of the desired logic. Earthing Example 2: Usage of the F-key and a software switch F key 95

96 1MRS MUM Example 3: Voltage measurement in the MIMIC view Phase-to-phase voltage must be shown in voltages [V] in the MIMIC view. Voltage 9.6. Feeder terminal settings Responsibility: The end user defines the feeder terminal settings Feeder terminal settings according to the turn-key principle The setting of the parameters is not part of the configuration. The end user will normally be responsible for the setting parameters. Further information: 96

97 1MRS MUM 10. APPENDIX C: Specification for REM 54_ machine terminal configuration General data Project name: Date: This specification suitable for bays: Substation name: Machine terminal type: Software revision Order number: REM54 (for example REM543BM212AAAA) Handled by: Company: Telephone number: Fax number: Electrotechnical data Analog inputs This document serves as a technical specification of substation protection and is used for the configuration of REM 54_ machine terminals. Special requirements can be specified under Further information at the bottom of each page Hardware versions with 5 current and 4 voltage transformers Table Analog input channel connections Measuring devices that can be connected to the corresponding analog Channel measuring channels 1 Rogowski sensor, voltage divider or general measurement Current transformer, Rogowski sensor, voltage divider or general measurement 6 Current transformer Voltage transfomer, Rogowski sensor, voltage divider or general measurement The sensor inputs are shown in Section Sensor inputs. 97

98 1MRS MUM Module type Board Terminal number Connected object Signal type MIM 1MRS AA_/CA_ RemMim1 X V 100V 100V 100V 0.2A 1A Ch 6 1A 5A 1A 5A 1A 5A 1A 5A Ch 10 Ch 9 Ch 8 Ch 7 Ch 5 Ch 4 Ch 3 Ch 2 X1.1:25, X1.1:27 X1.1:22, X1.1:24 X1.1:19, X1.1:21 X1.1:16, X1.1:18 X1.1:13, X1.1:14, X1.1:15 X1.1:10, X1.1:11, X1.1:12 X1.1:7, X1.1:8, X1.1:9 X1.1:4, X1.1:5, X1.1:6 X1.1:1, X1.1:2, X1.1:3 VT4 VT3 VT2 VT1 CT5 CT4 CT3 CT2 CT1 Further information: Hardware versions with 6 current and 3 voltage transformers Measuring devices that can be connected to the corresponding analog Channel measuring channels 1 Rogowski sensor, voltage divider or general measurement Current transformer, Rogowski sensor, voltage divider or general measurement 5 Voltage transformer, Rogowski sensor, voltage divider or general measurement 6 Voltage transformer Current transformer, Rogowski sensor, voltage divider or general measurement 10 Voltage transformer, Rogowski sensor, voltage divider or general measurement The sensor inputs are shown in Section Sensor inputs. 98

99 1MRS MUM Module type Board Terminal number Connected object Signal type MIM 1MRS AA_/CA_ X V 1A 5A 1A 5A 1A 5A Ch 10 Ch 9 Ch 8 Ch 7 X1.1:25, X1.1:27 X1.1:22, X1.1:23, X1.1:24 X1.1:19, X1.1:20, X1.1:21 X1.1:16, X1.1:17, X1.1:18 VT3 CT6 CT5 CT4 RemMim V 100V 1A 5A 1A 5A 1A 5A Ch 6 Ch 5 Ch 4 Ch 3 Ch 2 X1.1:13, X1.1:15 X1.1:10, X1.1:12 X1.1:7, X1.1:8, X1.1:9 X1.1:4, X1.1:5, X1.1:6 X1.1:1, X1.1:2, X1.1:3 VT2 VT1 CT3 CT2 CT1 RemMim2 Further information: Hardware versions with 7 current and 2 voltage transformers Channel Measuring devices that can be connected to the corresponding analog measuring channels 1 Rogowski sensor, voltage divider or general measurement Current transformer, Rogowski sensor, voltage divider or general measurement 6 Voltage transformer Current transformer, Rogowski sensor, voltage divider or general measurement 10 Voltage transformer, Rogowski sensor, voltage divider or general measurement The sensor inputs are shown in Section Sensor inputs. 99

100 1MRS MUM Module type Board Terminal number Connected object Signal type MIM 1MRS AA_/CA_ X V 1A 5A 1A 5A 1A 5A Ch 10 Ch 9 Ch 8 Ch 7 X1.1:25, X1.1:27 X1.1:22, X1.1:23, X1.1:24 X1.1:19, X1.1:20, X1.1:21 X1.1:16, X1.1:17, X1.1:18 VT2 CT7 CT6 CT5 RemMim V 1A 5A 1A 5A 1A 5A 1A 5A Ch 6 Ch 5 Ch 4 Ch 3 Ch 2 X1.1:13, X1.1:15 X1.1:10, X1.1:11, X1.1:12 X1.1:7, X1.1:8, X1.1:9 X1.1:4, X1.1:5, X1.1:6 X1.1:1, X1.1:2, X1.1:3 VT1 CT4 CT3 CT2 CT1 RemMim3 Further information: 100

101 1MRS MUM Hardware versions with 8 current and 1 voltage transformer Channel Measuring devices that can be connected to the corresponding analog measuring channels 1 Rogowski sensor, voltage divider or general measurement Current transformer, Rogowski sensor, voltage divider or general measurement 6 Current transformer Current transformer, Rogowski sensor, voltage divider or general measurement 10 Voltage transformer, Rogowski sensor, voltage divider or general measurement The sensor inputs are shown in Section Sensor inputs. Module type Board Terminal number Connected object Signal type MIM 1MRS AA_/CA_ X V 1A 5A 1A 5A 1A 5A Ch 10 Ch 9 Ch 8 Ch 7 X1.1:25, X1.1:27 X1.1:22, X1.1:23, X1.1:24 X1.1:19, X1.1:20, X1.1:21 X1.1:16, X1.1:17, X1.1:18 VT1 CT8 CT7 CT6 RemMim4 15 1A 14 5A Ch A 11 5A Ch A 8 5A Ch A 5 5A Ch A 2 5A Ch 2 1 X1.1:13, X1.1:14, X1.1:15 X1.1:10, X1.1:11, X1.1:12 X1.1:7, X1.1:8, X1.1:9 X1.1:4, X1.1:5, X1.1:6 X1.1:1, X1.1:2, X1.1:3 CT5 CT4 CT3 CT2 CT1 RemMim4 Further information: 101

102 SIMX2.fh8 1MRS MUM Sensor inputs Module type Board Terminal number Connected object Signal type SIM X2.1 DIFF Ch 10, sensor X2.1 X2.2 DIFF Ch 9, sensor X2.2 X2.3 DIFF Ch 8, sensor X2.3 X2.4 DIFF Ch 7, sensor X2.4 X2.5 DIFF Ch 5, sensor X2.5 X2.6 DIFF Ch 4, sensor X2.6 X2.7 DIFF Ch 3, sensor X2.7 X2.8 DIFF Ch 2, sensor X2.8 X2.9 DIFF Ch 1, sensor X2.9 The measuring device can be connected exclusively to the analog channels of either MIM or SIM type modules. Ten channels are available. Simx2 Further information: System frequency 50 Hz 60 Hz 102

103 BIO1X5.1.fh8 PS1X4.2b.fh8 1MRS MUM Digital inputs Module type Board Terminal number Connected object PS1 X PS1_4_BI1 X4.2:1, X4.2:2 1) 4 5 PS1_4_BI2 X4.2:4, X4.2:5 1) 6 7 PS1_4_BI3 X4.2:6, X4.2:7 1) 1) Digital input / counter input PS1X4.2b Module type Board Terminal number Connected object BIO1 X BIO1_5_BI1 BIO1_5_BI2 X5.1:1, X5.1:2 X5.1:2, X5.1: BIO1_5_BI3 BIO1_5_BI4 X5.1:4, X5.1:5 X5.1:5, X5.1: BIO1_5_BI5 BIO1_5_BI6 X5.1:7, X5.1:8 X5.1:8, X5.1: BIO1_5_BI7 BIO1_5_BI8 X5.1:10, X5.1:11 X5.1:11, X5.1: BIO1_5_BI9 BIO1_5_BI10 BIO1_5_BI11 X5.1:13, X5.1:14 X5.1:15, X5.1:16 X5.1:17, X5.1:18 1) 1) 1) 1) Digital input / counter input BIO1X5.1 Further information: 103

104 BIO2X7.1b.fh8 BIO1X5.2.fh8 1MRS MUM Module type Board Terminal number Connected object BIO1 X BIO1_5_BI12 X5.2:1, X5.2:2 1) 1) Digital input/ counter input/ time sync BIO1X5.2 Module type Board Terminal number Connected object BIO2 (RET 543) (RET 545) X BIO2_7_BI1 BIO2_7_BI2 X7.1:1, X7.1:2 X7.1:2, X7.1: BIO2_7_BI3 BIO2_7_BI4 X7.1:4, X7.1:5 X7.1:5, X7.1: BIO2_7_BI5 BIO2_7_BI6 X7.1:7, X7.1:8 X7.1:8, X7.1: BIO2_7_BI7 BIO2_7_BI8 X7.1:10, X7.1:11 X7.1:11, X7.1: BIO2_7_BI9 X7.1:13, X7.1:14 1) BIO2_7_BI10 X7.1:15, X7.1:16 1) 1) Digital input / counter input BIO2X7.1b Further information: 104

105 PS1X4.2o_b.fh8 PS1X4.1b.fh8 1MRS MUM Digital outputs Module type Connected object Terminal number Board PS1 1) X4.1:1, X4.1:2 1) PS1_4_ACFail PS1_4_TempAlarm + Mains - X X4.1:3, X4.1:4, X4.1:5 IRF X X4.1:6, X4.1:7, X4.1:8, X4.1:9 PS1_4_HSPO ) X4.1:10, X4.1:11, X4.1:12, X4.1:13 PS1_4_HSPO1 PS1_4_TCS1 TCS ) X4.1:15, X4.1:16, X4.1:17, X4.1:18 PS1_4_HSPO2 PS1_4_TCS2 TCS ) Please indicate whether the trip circuit supervision inputs will be configured to use or not PS1X4.1b Module type PS1 Connected object Terminal number Board X4.2 8 X4.2:8, X4.2:9, X4.2:10, X4.2:11 PS1_4_HSPO X4.2:12, X4.2:13, X4.2:14, X4.2:15 PS1_4_HSPO X4.2:16, X4.2:17, X4.2:18 PS1_4_SO1 18 PS1X4.2o_b Further information: 105

106 BIO1X5.2o.fh8 1MRS MUM Module type BIO1 Connected object Terminal number Board X5.2 3 X5.2:3, X5.2:4 BIO1_5_SO1 4 5 X5.2:5, X5.2:6 BIO1_5_SO X5.2:7, X5.2:8, X5.2:9 BIO1_5_SO X5.2:10, X5.2:11, X5.2:12 BIO1_5_SO X5.2:13, X5.2:14, X5.2:15 BIO1_5_SO X5.2:16, X5.2:17, X5.2:18 BIO1_5_SO6 17 BIO1X5.2o Module type BIO2 (RET 543) (RET 545) Connected object Terminal number Board X7.1 X7.1:17, X7.1:18 BIO2_7_PO BIO2X7.1o_b Further information: 106

107 1MRS MUM Module type Connected object Terminal number Board BIO2 (RET 543) (RET 545) X7.2:1, X7.2:2 BIO2_7_PO2 X X7.2:3, X7.2:4, X7.2:5, X7.2:6 BIO2_7_PO X7.2:7, X7.2:8, X7.2:9, X7.2:10 BIO2_7_PO X7.2:11, X7.2:12, X7.2:13, X7.2:14 BIO2_7_PO X7.2:15, X7.2:16, X7.2:17, X7.2:18 BIO2_7_PO BIO2X7.2b Further information: 107

108 RTD1X6._b.fh8 1MRS MUM RTD module RTD/analog inputs Module type Board Terminal number 1) Connected object RTD1 X SHUNT + - DIFF RTD1_6_AI1 X6.1:1, X6.1:2, X6.1: SHUNT - + DIFF RTD1_6_AI2 X6.1:5, X6.1:6, X6.1: SHUNT + - DIFF RTD1_6_AI3 X6.1:8, X6.1:9, X6.1: SHUNT - + DIFF RTD1_6_AI4 X6.1:12, X6.1:13, X6.1: SHUNT + - DIFF RTD1_6_AI5 X6.1:15, X6.1:16, X6.1:17 X SHUNT - + DIFF RTD1_6_AI6 X6.2:1, X6.2:2, X6.2: SHUNT + - DIFF RTD1_6_AI7 X6.2:4, X6.2:5, X6.2: SHUNT - + DIFF RTD1_6_AI8 X6.2:7, X6.2:8, X6.2:9 1) Current transducer / voltage transducer / resistance sensor RTD1X6._b Further information: 108

109 RTD1X6.2b.fh8 1MRS MUM RTD outputs Module type Connected object Terminal number Board RTD1 X6.2 X6.2:11, X6.2:12 RTD1_6_AO1 + ma X6.2:13, X6.2:14 RTD1_6_AO2 + ma X6.2:15, X6.2:16 RTD1_6_AO3 + ma X6.2:17, X6.2:18 RTD1_6_AO4 + ma RTD1X6.2b Further information: Functionality Order number REM54 (for example REM543CM212AAAA) 109

110 1MRS MUM Application function blocks used The lists below represent the full set of function blocks, but the selected functionality level (indicated by a letter in the order number, for example REM543CM212AAAA) determines the function blocks available for the configuration. Protection DEF2Low Inrush3 OPOW6St1 TOL3Dev DEF2High MotStart OPOW6St2 UE6Low DEF2Inst NEF1Low OPOW6St3 UE6High Diff3 NEF1High OV3Low UI6Low Diff6G NEF1Inst OV3High UI6High DOC6Low NOC3Low PREV3 UPOW6St1 DOC6High NOC3High PSV3St1 UPOW6St2 DOC6Inst NOC3Inst PSV3St2 UPOW6St3 Freq1St1 NPS3Low REF1A UV3Low Freq1St2 NPS3High ROV1Low UV3High Freq1St3 NUC3St1 ROV1High VOC6Low Freq1St4 NUC3St2 ROV1Inst VOC6High Freq1St5 OE1Low SCVCSt1 FuseFail OE1High SCVCSt2 Measurement MEAI1 MEAI6 MEAO3 MEDREC16 MEAI2 MEAI7 MEAO4 MEFR1 MEAI3 MEAI8 MECU1A MEPE7 MEAI4 MEAO1 MECU1B MEVO1A MEAI5 MEAO2 MECU3A MEVO3A Control COCB1 CODC5 COLOCAT MMIALAR5 COCB2 COIND1 COSW1 MMIALAR6 COCBDIR COIND2 COSW2 MMIALAR7 CO3DC1 COIND3 COSW3 MMIALAR8 CO3DC2 COIND4 COSW4 MMIDATA1 CODC1 COIND5 MMIALAR1 MMIDATA2 CODC2 COIND6 MMIALAR2 MMIDATA3 CODC3 COIND7 MMIALAR3 MMIDATA4 CODC4 COIND8 MMIALAR4 MMIDATA5 Condition monitoring CMBWEAR1 CMBWEAR2 CMTCS1 CMTCS2 110

111 1MRS MUM Condition monitoring (Continued) CMCU3 CMGAS1 CMGAS3 CMSCHED CMSPRC1 CMTIME1 CMTIME2 CMTRAV1 CMVO3 Communication EVENT230 General INDRESET SWGRP5 SWGRP11 SWGRP17 MMIWAKE SWGRP6 SWGRP12 SWGRP18 SWGRP1 SWGRP7 SWGRP13 SWGRP19 SWGRP2 SWGRP8 SWGRP14 SWGRP20 SWGRP3 SWGRP9 SWGRP15 SWGRP4 SWGRP10 SWGRP Communication Protocol used: LON SPA Modbus 111

112 1MRS MUM Relay MIMIC configuration Illustration of the system, MIMIC diagram Symbol used closed open undef. 0 0 undef. 1 1 Disconnector: (truck symbols) Circuit breaker: Earth switch: Further information: 112

113 1MRS MUM Alarm LEDs Please fill in the table below to describe the legend text used as well as the flashing sequence and colour of the LEDs. Table Descriptions for legend texts and LEDs LED OFF state ON state Text (max. 16 characters) Colour Flashing seq. Text (max. 16 characters) Colour Flashing seq off green yellow red latched, blinking latched, steady non-latched, blinking Interlocking Control test mode off green yellow red latched, blinking latched, steady non-latched, blinking X X X X Further information: 113

114 1MRS MUM Functionality logic Please specify the required special PLC logic functionality (see the examples below), by drawing or otherwise, on separate sheets and enclose all additional information with this document (Specification for Machine Terminal Configuration). Example 1: Earthing sequence Earthing of the outgoing feeder can be done by a circuit breaker when an earthing sequence is activated, an earthing switch is earthed and no voltage is measured. If all conditions are fulfilled, the circuit breaker can be closed after 1 second. The figure below shows the implementation of the desired logic. Earthing Example 2: Usage of the F-key and a software switch F key 114

115 1MRS MUM Example 3: Voltage measurement in the MIMIC view Phase-to-phase voltage must be shown in voltages [V] in the MIMIC view. Voltage Machine terminal settings Responsibility: The end user defines the machine terminal settings Machine terminal settings according to the turn-key principle The setting of the parameters is not part of the configuration. The end user will normally be responsible for the setting parameters. Further information: 115

116 116

117 1MRS MUM 11. APPENDIX D: Specification for RET 54_ transformer terminal configuration General data Project name: Date: This specification suitable for bays: Substation name: Machine terminal type: Software revision Order number: RET54 (for example RET543A_240AAAA) Handled by: Company: Telephone number: Fax number: This document serves as a technical specification of substation protection and is used for the configuration of RET 54_ transformer terminals. Special requirements can be specified under Further information at the bottom of each page. 117

118 1MRS MUM Electrotechnical data Analog inputs Hardware versions with 6 current and 3 voltage transformers Channel Measuring devices that can be connected to the corresponding analog measuring channels Current transformer 5..6 Voltage transformer Current transformer 10 Voltage transformer Module type Board Terminal number Connected object Signal type MIM 1MRS AA_/CA_ X V 1A 5A 1A 5A 1A 5A Ch 10 Ch 9 Ch 8 Ch 7 X1.1:25, X1.1:27 X1.1:22, X1.1:23, X1.1:24 X1.1:19, X1.1:20, X1.1:21 X1.1:16, X1.1:17, X1.1:18 VT3 CT6 CT5 CT4 RemMim V 100V 1A 5A 1A 5A 1A 5A Ch 6 Ch 5 Ch 4 Ch 3 Ch 2 X1.1:13, X1.1:15 X1.1:10, X1.1:12 X1.1:7, X1.1:8, X1.1:9 X1.1:4, X1.1:5, X1.1:6 X1.1:1, X1.1:2, X1.1:3 VT2 VT1 CT3 CT2 CT1 RemMim2 Further information: 118

119 1MRS MUM Hardware versions with 7 current and 2 voltage transformers Channel Measuring devices that can be connected to the corresponding analog measuring channels Current transformer 6 Voltage transformer Current transformer 10 Voltage transformer Module type Board Terminal number Connected object Signal type MIM 1MRS AA_/CA_ X V 1A 5A 1A 5A 1A 5A Ch 10 Ch 9 Ch 8 Ch 7 X1.1:25, X1.1:27 X1.1:22, X1.1:23, X1.1:24 X1.1:19, X1.1:20, X1.1:21 X1.1:16, X1.1:17, X1.1:18 VT2 CT7 CT6 CT5 RemMim V 1A 5A 1A 5A 1A 5A 1A 5A Ch 6 Ch 5 Ch 4 Ch 3 Ch 2 X1.1:13, X1.1:15 X1.1:10, X1.1:11, X1.1:12 X1.1:7, X1.1:8, X1.1:9 X1.1:4, X1.1:5, X1.1:6 X1.1:1, X1.1:2, X1.1:3 VT1 CT4 CT3 CT2 CT1 RemMim3 Further information: 119

120 1MRS MUM Hardware versions with 8 current and 1 voltage transformer Channel Measuring devices that can be connected to the corresponding analog measuring channels Current transformer 10 Voltage transformer Module type Board Terminal number Connected object Signal type MIM 1MRS AA_/CA_ X V 1A 5A 1A 5A 1A 5A Ch 10 Ch 9 Ch 8 Ch 7 X1.1:25, X1.1:27 X1.1:22, X1.1:23, X1.1:24 X1.1:19, X1.1:20, X1.1:21 X1.1:16, X1.1:17, X1.1:18 VT1 CT8 CT7 CT6 RemMim4 15 1A 14 5A Ch A 11 5A Ch A 8 5A Ch A 5 5A Ch A 2 5A Ch 2 1 X1.1:13, X1.1:14, X1.1:15 X1.1:10, X1.1:11, X1.1:12 X1.1:7, X1.1:8, X1.1:9 X1.1:4, X1.1:5, X1.1:6 X1.1:1, X1.1:2, X1.1:3 CT5 CT4 CT3 CT2 CT1 RemMim4 Further information: System frequency 50 Hz 60 Hz 120

121 BIO1X5.1.fh8 PS1X4.2b.fh8 1MRS MUM Digital inputs Module type Board Terminal number Connected object PS1 X PS1_4_BI1 X4.2:1, X4.2:2 1) 4 5 PS1_4_BI2 X4.2:4, X4.2:5 1) 6 7 PS1_4_BI3 X4.2:6, X4.2:7 1) 1) Digital input / counter input PS1X4.2b Module type Board Terminal number Connected object BIO1 X BIO1_5_BI1 BIO1_5_BI2 X5.1:1, X5.1:2 X5.1:2, X5.1: BIO1_5_BI3 BIO1_5_BI4 X5.1:4, X5.1:5 X5.1:5, X5.1: BIO1_5_BI5 BIO1_5_BI6 X5.1:7, X5.1:8 X5.1:8, X5.1: BIO1_5_BI7 BIO1_5_BI8 X5.1:10, X5.1:11 X5.1:11, X5.1: BIO1_5_BI9 BIO1_5_BI10 BIO1_5_BI11 X5.1:13, X5.1:14 X5.1:15, X5.1:16 X5.1:17, X5.1:18 1) 1) 1) 1) Digital input / counter input BIO1X5.1 Further information: 121

122 BIO2X7.1b.fh8 BIO1X5.2.fh8 1MRS MUM Module type Board Terminal number Connected object BIO1 X BIO1_5_BI12 X5.2:1, X5.2:2 1) 1) Digital input/ counter input/ time sync BIO1X5.2 Module type Board Terminal number Connected object BIO2 (RET 543) (RET 545) X BIO2_7_BI1 BIO2_7_BI2 X7.1:1, X7.1:2 X7.1:2, X7.1: BIO2_7_BI3 BIO2_7_BI4 X7.1:4, X7.1:5 X7.1:5, X7.1: BIO2_7_BI5 BIO2_7_BI6 X7.1:7, X7.1:8 X7.1:8, X7.1: BIO2_7_BI7 BIO2_7_BI8 X7.1:10, X7.1:11 X7.1:11, X7.1: BIO2_7_BI9 X7.1:13, X7.1:14 1) BIO2_7_BI10 X7.1:15, X7.1:16 1) 1) Digital input / counter input A Further information: 122

123 PS1X4.2o_b.fh8 PS1X4.1b.fh8 1MRS MUM Digital outputs Module type Connected object Terminal number Board PS1 1) X4.1:1, X4.1:2 1) PS1_4_ACFail PS1_4_TempAlarm + Mains - X X4.1:3, X4.1:4, X4.1:5 IRF X X4.1:6, X4.1:7, X4.1:8, X4.1:9 PS1_4_HSPO ) X4.1:10, X4.1:11, X4.1:12, X4.1:13 PS1_4_HSPO1 PS1_4_TCS1 TCS ) X4.1:15, X4.1:16, X4.1:17, X4.1:18 PS1_4_HSPO2 PS1_4_TCS2 TCS ) Please indicate whether the trip circuit supervision inputs will be configured to use or not PS1X4.1b Module type PS1 Connected object Terminal number Board X4.2 8 X4.2:8, X4.2:9, X4.2:10, X4.2:11 PS1_4_HSPO X4.2:12, X4.2:13, X4.2:14, X4.2:15 PS1_4_HSPO X4.2:16, X4.2:17, X4.2:18 PS1_4_SO1 18 PS1X4.2o_b Further information: 123

124 BIO1X5.2o.fh8 1MRS MUM Module type BIO1 Connected object Terminal number Board X5.2 3 X5.2:3, X5.2:4 BIO1_5_SO1 4 5 X5.2:5, X5.2:6 BIO1_5_SO X5.2:7, X5.2:8, X5.2:9 BIO1_5_SO X5.2:10, X5.2:11, X5.2:12 BIO1_5_SO X5.2:13, X5.2:14, X5.2:15 BIO1_5_SO X5.2:16, X5.2:17, X5.2:18 BIO1_5_SO6 17 BIO1X5.2o Module type BIO2 (RET 543) (RET 545) Connected object Terminal number Board X7.1 X7.1:17, X7.1:18 BIO2_7_PO A Further information: 124

125 1MRS MUM Module type Connected object Terminal number Board BIO2 (RET 543) (RET 545) X7.2:1, X7.2:2 BIO2_7_PO2 X X7.2:3, X7.2:4, X7.2:5, X7.2:6 BIO2_7_PO X7.2:7, X7.2:8, X7.2:9, X7.2:10 BIO2_7_PO X7.2:11, X7.2:12, X7.2:13, X7.2:14 BIO2_7_PO X7.2:15, X7.2:16, X7.2:17, X7.2:18 BIO2_7_PO A Further information: 125

126 RTD1X6._b.fh8 1MRS MUM RTD module RTD/analog inputs Module type Board Terminal number 1) Connected object RTD1 X SHUNT + - DIFF RTD1_6_AI1 X6.1:1, X6.1:2, X6.1: SHUNT - + DIFF RTD1_6_AI2 X6.1:5, X6.1:6, X6.1: SHUNT + - DIFF RTD1_6_AI3 X6.1:8, X6.1:9, X6.1: SHUNT - + DIFF RTD1_6_AI4 X6.1:12, X6.1:13, X6.1: SHUNT + - DIFF RTD1_6_AI5 X6.1:15, X6.1:16, X6.1:17 X SHUNT - + DIFF RTD1_6_AI6 X6.2:1, X6.2:2, X6.2: SHUNT + - DIFF RTD1_6_AI7 X6.2:4, X6.2:5, X6.2: SHUNT - + DIFF RTD1_6_AI8 X6.2:7, X6.2:8, X6.2:9 1) Current transducer / voltage transducer / resistance sensor RTD1X6._b Further information: 126

127 RTD1X6.2b.fh8 1MRS MUM RTD outputs Module type Connected object Terminal number Board RTD1 X6.2 X6.2:11, X6.2:12 RTD1_6_AO1 + ma X6.2:13, X6.2:14 RTD1_6_AO2 + ma X6.2:15, X6.2:16 RTD1_6_AO3 + ma X6.2:17, X6.2:18 RTD1_6_AO4 + ma RTD1X6.2b Further information: Functionality Order number RET54 (for example RET543AC240AAAA) 127

128 1MRS MUM Application function blocks used The lists below represent the full set of function blocks, but the selected functionality level (indicated by a letter in the order number, for example RET543AC240AAAA) determines the function blocks available for the configuration. Protection DEF2Low Freq1St4 NOC3Inst REF4A DEF2High Freq1St5 NPS3Low REF4B DEF2Inst FuseFail NPS3High ROV1Low Diff6T Inrush3 OE1Low ROV1High DOC6Low NEF1Low OE1High ROV1Inst DOC6High NEF1High OV3Low TOL3Dev DOC6Inst NEF1Inst OV3High UI6Low Freq1St1 NOC3Low PSV3St1 UI6High Freq1St2 NOC3LowB PSV3St2 UV3Low Freq1St3 NOC3High REF1A UV3High Measurement MEAI1 MEAI7 MECU1A MEPE7 MEAI2 MEAI8 MECU1B MEVO1A MEAI3 MEAO1 MECU3A MEVO1B MEAI4 MEAO2 MECU3B MEVO3A MEAI5 MEAO3 MEDREC16 MEVO3B MEAI6 MEAO4 MEFR1 Control COCB1 COIND1 COSW1 MMIALAR7 COCB2 COIND2 COSW2 MMIALAR8 COCBDIR COIND3 COSW3 MMIDATA1 CO3DC1 COIND4 COSW4 MMIDATA2 CO3DC2 COIND5 MMIALAR1 MMIDATA3 CODC1 COIND6 MMIALAR2 MMIDATA4 CODC2 COIND7 MMIALAR3 MMIDATA5 CODC3 COIND8 MMIALAR4 CODC4 COLOCAT MMIALAR5 CODC5 COLTC MMIALAR6 Condition monitoring CMBWEAR1 CMBWEAR2 CMCU3 CMGAS1 CMTCS1 CMTCS2 CMTIME1 CMTIME2 128

129 1MRS MUM Condition monitoring CMGAS3 CMSCHED CMSPRC1 CMTRAV1 CMVO3 Communication EVENT Communication General INDRESET SWGRP5 SWGRP11 SWGRP17 MMIWAKE SWGRP6 SWGRP12 SWGRP18 SWGRP1 SWGRP7 SWGRP13 SWGRP19 SWGRP2 SWGRP8 SWGRP14 SWGRP20 SWGRP3 SWGRP9 SWGRP15 SWGRP4 SWGRP10 SWGRP16 Protocol used: Port X3.2 Port X3.3 Modbus LON DNP 3.0 SPA IEC SPA 129

130 1MRS MUM Relay MIMIC configuration Illustration of the system, MIMIC diagram Q1 Q A Q4 AVR AUT 0POS PAR ON Q A 0. 0 kw 0. 0 A Io Symbol used closed open undef. 0 0 undef. 1 1 Disconnector: (truck symbols) Circuit breaker: Earth switch: Further information: 130

131 1MRS MUM Alarm LEDs Please fill in the table below to describe the legend text used as well as the flashing sequence and colour of the LEDs. Table Descriptions for legend texts and LEDs LED OFF state ON state Text (max. 16 characters) Colour Flashing seq. Text (max. 16 characters) Colour Flashing seq off green yellow red latched, blinking latched, steady non-latched, blinking Interlocking Control test mode off green yellow red latched, blinking latched, steady non-latched, blinking X X X X Further information: 131

132 1MRS MUM Functionality logic Please specify the required special PLC logic functionality (see the examples below), by drawing or otherwise, on separate sheets and enclose all additional information with this document (Specification for Transformer Terminal Configuration). Example 1: Earthing sequence Earthing of the outgoing feeder can be done by a circuit breaker when an earthing sequence is activated, an earthing switch is earthed and no voltage is measured. If all conditions are fulfilled, the circuit breaker can be closed after 1 second. The figure below shows the implementation of the desired logic. Example 2: Usage of the F-key and a software switch Earthing F key 132

133 1MRS MUM Example 3: Voltage measurement in the MIMIC view Phase-to-phase voltage must be shown in voltages [V] in the MIMIC view. Voltage Transformer terminal settings Responsibility: The end user defines the machine terminal settings Machine terminal settings according to the turn-key principle The setting of the parameters is not part of the configuration. The end user will normally be responsible for the setting parameters. Further information: 133

134 134

135 1MRS MUM 12. APPENDIX E: Specification for REC 523 Remote Monitoring and Control Unit configuration General data Project name: Date: This specification suitable for bays: Substation name: Monitoring and control unit type: Software revision Order number: REC523 (for example REC523F 033AAA) Handled by: Company: Telephone number: Fax number: This document serves as a technical specification of remote monitoring and control of secondary substations in medium-voltage networks and is used for the configuration of REC 523 remote monitoring and control units. Special requirements can be specified under Further information at the bottom of each page. 135

136 1MRS MUM Electrotechnical data Analog inputs Table Analog input channel connections Measuring devices that can be connected to the corresponding analog Channel measuring channels 1 Rogowski sensor, voltage divider or general measurement Current transformer, Rogowski sensor, voltage divider, or general measurement 5, Voltage transfomer,current transformer, Rogowski sensor, voltage divider or general measurement 6 Voltage transformer or general measururement 10 Voltage transformer, Rogowski sensor, voltage divider or general measurement Further information: 136

137 1MRS MUM Module type Board Terminal number Connected object Signal type MIM (032 _AA, 037 _AA) RecMim1 X A 5A 1A 5A 1A 5A Ch 4 Ch 3 Ch 2 X1.1:7, X1.1:8, X1.1:9 X1.1:4, X1.1:5, X1.1:6 X1.1:1, X1.1:2, X1.1:3 CT3 CT2 CT1 RecMim1 Module type Board Terminal number Connected object Signal type MIM (033 _AA, 038 _AA) X V 100V Ch 10 Ch 9 X1.1:25, X1.1:27 X1.1:22, X1.1:24 VT3 VT V Ch 8 X1.1:19, X1.1:21 VT1 RecMim A 5A 1A 5A 1A 5A Ch 4 Ch 3 Ch 2 X1.1:7, X1.1:8, X1.1:9 X1.1:4, X1.1:5, X1.1:6 X1.1:1, X1.1:2, X1.1:3 CT3 CT2 CT1 RecMim2 Further information: 137

138 1MRS MUM Module type Board Terminal number Connected object Signal type MIM (034 _AA, 039 _AA) X V 230V Ch 10 Ch 9 X1.1:25, X1.1:27 X1.1:22, X1.1:24 VT3 VT V Ch 8 X1.1:19, X1.1:21 VT1 RecMim A 5A 1A 5A 1A 5A 1A 5A Ch 5 Ch 4 Ch 3 Ch 2 X1.1:10, X1.1:11, X1.1:12 X1.1:7, X1.1:8, X1.1:9 X1.1:4, X1.1:5, X1.1:6 X1.1:1, X1.1:2, X1.1:3 CT4 CT3 CT2 CT1 RecMim3 Module type Board Terminal number Connected object Signal type MIM (061 _AA, 066 _AA) X V 1A 5A 1A 5A 1A 5A Ch 10 Ch 9 Ch 8 Ch 7 X1.1:25, X1.1:27 X1.1:22, X1.1:23, X1.1:24 X1.1:19, X1.1:20, X1.1:21 X1.1:16, X1.1:17, X1.1:18 VT3 CT6 CT5 CT4 RecMim V 100V 1A 5A 1A 5A 1A 5A Ch 6 Ch 5 Ch 4 Ch 3 Ch 2 X1.1:13, X1.1:15 X1.1:10, X1.1:12 X1.1:7, X1.1:8, X1.1:9 X1.1:4, X1.1:5, X1.1:6 X1.1:1, X1.1:2, X1.1:3 VT2 VT1 CT3 CT2 CT1 RecMim4 Further information: 138

139 1MRS MUM Module type Board Terminal number Connected object Signal type MIM (062 _AA, 067 _AA) X V 100V Ch 10 Ch 9 X1.1:25, X1.1:27 X1.1:22, X1.1:24 VT6 VT5 RecMim V V V V A 8 5A 7 6 1A 5 5A 4 3 1A 2 5A 1 Ch 8 Ch 7 Ch 6 Ch 5 Ch 4 Ch 3 Ch 2 X1.1:19, X1.1:21 X1.1:16, X1.1:18 X1.1:13, X1.1:15 X1.1:10, X1.1:12 X1.1:7, X1.1:8, X1.1:9 X1.1:4, X1.1:5, X1.1:6 X1.1:1, X1.1:2, X1.1:3 VT4 VT3 VT2 VT1 CT3 CT2 CT1 RecMim5 Module type Board Terminal number Connected object Signal type MIM (054_AA, 059_AA X V V V V ,2A 15 1A A 5A 10 1A 9 5A 8 7 1A 6 5A 5 4 1A 3 5A 2 1 Ch 10 Ch 9 Ch 8 Ch 7 Ch 6 Ch 5 Ch 4 Ch 3 Ch 2 X1.1:25 X1.1:27 X1.1:22 X1.1:24 X1.1:19 X1.1:21 X1.1:16 X1.1:18 X1.1:13 X1.1:14 X1.1:15 X1.1:10 X1.1:12 X1.1:7 X1.1:8 X1.1:9 X1.1:4 X1.1:5 X1.1:6 X1.1:1 X1.1:2 X1.1:3 VT4 VT3 VT2 VT1 CT5 CT4 CT3 CT2 CT1 A Further information: 139

140 SIMX2.fh8 1MRS MUM Module type Board Terminal number Connected object Signal type SIM X2.1 DIFF Ch 10, sensor X2.1 X2.2 DIFF Ch 9, sensor X2.2 X2.3 DIFF Ch 8, sensor X2.3 X2.4 DIFF Ch 7, sensor X2.4 X2.5 DIFF Ch 5, sensor X2.5 X2.6 DIFF Ch 4, sensor X2.6 X2.7 DIFF Ch 3, sensor X2.7 X2.8 DIFF Ch 2, sensor X2.8 X2.9 DIFF Ch 1, sensor X2.9 Simx2 The measuring device can be connected exclusively to the analog channels of either MIM or SIM type modules. Further information: System frequency 50 Hz 60 Hz 140

141 BIO1X3.2.fh8 BIO1X3.1.fh8 PSCX7.3.fh8 1MRS MUM Digital inputs Module type Board Terminal number Connected object PSC X PSC_7_BI1 X4.2:1, X4.2:2 1) 3 4 PSC_7_BI2 X4.2:4, X4.2:5 1) 5 6 PSC_7_BI3 X4.2:6, X4.2:7 1) 1) Digital input / counter input PSCX7.3 Module type Board Terminal number Connected object BIO1 X BIO1_3_BI1 X3.1:1, X3.1:2 BIO1_3_BI2 X3.1:2, X3.1: BIO1_3_BI3 X3.1:4, X3.1:5 BIO1_3_BI4 X3.1:5, X3.1: BIO1_3_BI5 X3.1:7, X3.1:8 BIO1_3_BI6 X3.1:8, X3.1: BIO1_3_BI7 BIO1_3_BI8 X3.1:10, X3.1:11 X3.1:11, X3.1: BIO1_3_BI9 X3.1:13, X3.1: BIO1_3_BI10 X3.1:15, X3.1: BIO1_3_BI11 X3.1:17, X3.1:18 BIO1X3.1 Module type Board Terminal number Connected object BIO1 X BIO1_3_BI12 X3.2:1, X3.2:2 BIO1X3.2 Further information: 141

142 BIO1X3.2o.fh8 PSCX7.3o.fh8 1MRS MUM Digital outputs Module type PSC Connected object Terminal number Board X7.3 8 PSC_7_SO1 or Heater Output 9 11 X7.3:11, X7.3:12, X7.3:13, X7.3:14 PSC_7_HSPO X7.3:15, X7.3:16, X7.3:17, X7.3:18 PSC_7_HSPO PSCX7.3o Module type BIO1 Connected object Terminal number Board X3.2 3 X3.2:3, X3.2:4 BIO1_3_SO1 4 5 X3.2:5, X3.2:6 BIO1_3_SO X3.2:7, X3.2:8, X3.2:9 BIO1_3_SO X3.2:10, X3.2:11, X3.2:12 BIO1_3_SO X3.2:13, X3.2:14, X3.2:15 BIO1_3_SO X3.2:16, X3.2:17, X3.2:18 BIO1_3_SO6 17 BIO1X3.2o Further information: 142

143 1MRS MUM Functionality Order number REC523 (for example REC523F033AAA) Application function blocks used Measurement MEAI1 MEAI6 MECU3A MEVO1A MEAI2 MEAI7 MECU3B MEVO1B MEAI3 MEAI8 MEDREC16 MEVO3A MEAI4 MECU1A MEFR1 MEVO3B MEAI5 MECU1B MEPE7 Fault indication AR5Func DEF2High Inrush3 NOC3Low CUB3Low DOC6Low NEF1Low NOC3High DEF2Low DOC6High NEF1High UV3Low UV3High Control COCB1 CODC2 COIND2 COIND7 COCB2 CODC3 COIND3 COIND8 CO3DC1 CODC4 COIND4 COLOCAT CO3DC2 CODC5 COIND5 COPFC CODC1 COIND1 COIND6 Condition monitoring CMBWEAR1 CMGAS1 CMTCS1 CMTIME2 CMBWEAR2 CMSCHED CMTCS2 CMTRAV1 CMCU3 CMSPRC1 CMTIME1 CMVO3 Communication EVENT230 General INDRESET SWGRP6 SWGRP12 SWGRP18 SWGRP1 SWGRP7 SWGRP13 SWGRP19 SWGRP2 SWGRP8 SWGRP14 SWGRP20 SWGRP3 SWGRP9 SWGRP15 143

144 1MRS MUM General (Continued) SWGRP4 SWGRP10 SWGRP16 SWGRP5 SWGRP11 SWGRP Communication Protocol used: LON SPA IEC DNP 3.0 Modbus Virtual channels Virtual meas. Channel number Analog meas. 1 Channel number Analog meas. 2 Channel number Analog meas. 3 Channel number I 0s I L1 I L2 I L3 I 0bs I L1b I L2b I L3b U 0s U 1 U 2 U 3 U 12s U 1 U 2 U 23s U 2 U 3 U 31s U 1 U LED configuration The optional LED panel of REC 523 includes 21 LEDs that can be freely configured with the Relay Configuration Tool (for an example configuration, see Fig below). Each LED has four states: on (steady), off, fast blinking (2 Hz) and slow blinking (0.5Hz). Please specify the desired LED configuration in Table below. 144

145 1MRS MUM PSC_7_ACFail FALSE PSC_7_BattTest PSC_7_BattStatus BIO1_3_BI1 BIO1_3_BI2 PSC_7_HeatStat PSC_7_TempAlarm BIO1_3_BI3 FALSE PSC_7_Bl1 NOT Leds 1-8 in REC 523 Led panel BOOL2INT_1 BOOL2INT PSC_7_LED1_8 B0 Q Led 1: Fast blink = B1 AC Fail occurred B2 Led 2: On = B3 Battery Test running B4 B5 B6 B7 B8 B9 B10 B11 B12 B13 B14 B15 Led 3: Led 4: Led 5: On = Battery Poor Off = Battery Good OFF = BI1&BI2 OFF Slow blink = BI1 OFF&BI2 ON Fast blink = BI1 ON&BI2 OFF ON = BI1&BI2 ON On = Heater on Led 6: On = Temp. limit exceeded Led 7: Led 8: On = BI3 OFF Fast blink = BI3 ON Slow blink = BI1 OFF Fast blink = BI1 ON Fig Example of the LED configuration for REC 523 A Table Specification for the LED configuration LED no 1 On (steady) Off Fast blink Slow blink Purpose

146 1MRS MUM Table Specification for the LED configuration LED no 8 On (steady) Off Fast blink Slow blink Purpose Remote monitoring and control unit settings Responsibility: The end user defines the remote monitoring and control unit settings Remote monitoring and control unit settings according to the turn-key principle The setting of the parameters is not part of the configuration. The end user will normally be responsible for the setting parameters. Further information: 146

147 1MRS MUM 13. APPENDIX F: Power quality application guide for harmonics Power quality and harmonics Power quality is a topic that defines the limits for delivered electricity in power network. The key issue is to define acceptable variation limits to ensure that endcustomers are able to utilise the delivered power. Power quality is ultimately a customer-driven issue. Excellent power without interruptions is the ultimate target. Today this target has not been reached. There are many kind of disturbances in the network affecting power quality. Interruptions and other disturbances weaken the utilisation of delivered power in end-customer facilities. If these disturbances have noticeable effects on the utilisation of power, disturbances should be blocked out or the system should be made immune to these disturbances. Before taking action to reduce the effects of disturbances, the reason and source of the disturbance should be found. Only after that can reasonable solutions be weighted against costs and benefits. Harmonics, that is, distortion in the voltage and current waveforms, are one of the factors affecting power quality. Harmonic distortion is caused by non-linear loads that are, for example, electronic power supplies, converters, arc furnaces and arc welders. Harmonics may cause maloperation of devices, additional heating in devices and telecommunication interference. The importance of harmonics is emphasized by the fact that the amount of equipment generating harmonics constantly increases. Still, it should be noticed that the existence of harmonics is not automatically a problem Background for harmonics A periodic distorted waveform can be expressed as a sum of sinusoids. The waveform can be represented as a sum of pure sine waves in which the frequency of each sinusoid is an integer multiple of the fundamental frequency. This multiple h is called a harmonic of the fundamental. Harmonics added to the fundamental frequency can be odd harmonics (the integer multiple h is 3,5,7...) or even harmonics (where h is 2,4,6...). In Fig odd harmonics with the amplitude 0.1 p.u. of the fundamental are added to the fundamental frequency. 147

148 1MRS MUM 1) 2) 3) 4) Oddharm.CNV Fig Odd harmonics added to the 1.0 p.u. fundamental frequency (50Hz) waveform are illustrated in the first picture. The second picture shows the fundamental frequency with 0.1 p.u. third harmonic. The third picture represents the fundamental frequency with the 0.1 p.u. third and 0.1 p.u. fifth harmonics. In the last picture, the 0.1 p.u. seventh harmonic is added to the fundamental frequency with the third and fifth harmonics. The relationship for current and voltage harmonics is shown in Fig Pure Sinusoid Voltage drop Distorted voltage Distorted load current Voltdist.CNV Fig Voltage distortion in power system 148

149 1MRS MUM Harmonic sources Voltage sources, that is, generation plants do not generally generate harmonics. Harmonics are created because of power system non-linearity. Non-linear components and loads cause distorted currents because of their operational principles. Distorted currents flow through system impedance causing a voltage drop for each harmonic. This results in voltage harmonics appearing at the load bus. The created voltage distortion can be calculated if current harmonics as well as system frequency response are known. In most cases the system frequency response is very difficult to determine. Power system is a very large system that contains many non-linear components. This makes it difficult to precisely predict the effects of harmonics in different parts of the power system. The most important harmonic sources are basically converters and power supplies for numerous electrical equipment. This equipment is a source for harmonics, and at the same time, its operation principles may be very sensitive to harmonics, especially to voltage harmonics. Still, some devices can be designed to decrease their characteristic harmonics Single-phase power supplies A major harmonic concern in commercial buildings is that power supplies for single-phase electronic equipment will produce too much distortion for the wiring. Direct current power for modern electronic and microprocessor-based office equipment is commonly derived from single-phase full-wave diode bridge rectifiers. Modern technology for single-phase power supplies is based on switch-mode. A distinctive characteristic of switch-mode power supplies is the very high thirdharmonic content in the current. Other characteristic harmonics are the 5th and 7th harmonics. Switch-mode power supplies are beginning to find applications in fluorescent lighting systems. Typical current harmonics and the waveform for a switch-mode power supply are shown in Fig Magnitude p.u. of fundamental Harmonic Fig Typical current harmonics and the waveform for a switch-mode power supply Currharm.CNV 149

150 1MRS MUM Three-phase power converters Three-phase electronic power converters differ from single-phase converters mainly because they do not generate the third harmonic or the third harmonic is quite small. There are many designs and types of converters for AC or DC drives with different power ratings. Harmonics may vary significantly between designs and operation conditions. Still, some examples are given below. Six-pulse and twelve-pulse converters Harmonic components of the AC current waveform with q-pulse rectifier are: h = kq ± 1 and the magnitudes of the harmonic currents are: Ih where = I1 --- h h k q I h I 1 the harmonic order any positive integer the pulse number of the rectifier circuit the amplitude of the harmonic current of order h the amplitude of the fundamental current The most significant harmonics for six-pulse converters are the 5th, 7th, 11th and 13th. For twelve-pulse converters, the 11th, 13th, 23rd and 25th harmonics are the most significant. PWM-type ASD Typical current harmonics and the waveform for a Pulse Width Modulation-type Adjustable Speed Drive with rated speed are shown in Fig Magnitude p.u. of fundamental Harmonic HarmPWM.CNV Fig CSI-type ASD Current harmonics and the waveform for a PWM-type ASD Typical current harmonics and the waveform for a Current Source Inverter-type Adjustable Speed Drive are shown in Fig