ABB Network PartnerRelay Configuration Tool (4)Specification for RE_ 54_ Configurations (5)Editing the RE_ 54_ Relay Terminal Configurations (6)Getting started (6)Libraries (6)Logical POUs (7)Program Organisation Unit (POU) (7)Physical hardware (9)Configuration (10)Resource (11)Hardware version (11)Analogue channels (11)Binary inputs (16)Measurements (17)Condition monitoring (18)Tasks (19)Programs and tasks (19)Task interval (19)Global variables (20)Declaring variables (21)Variables declared as global (25)Compiling the project (28)Main Configuration Rules for RE_ 54_ (29)General (29)Binary inputs (29)Explicit feedback (30)Measurement function blocks (31)Warnings (31)Execution order (32)F-key (33)APPENDIX A (35)APPENDIX B............................................................................................ 37-50 APPENDIX C............................................................................................ 51-65About this manualThis guideline describes in general the procedures for configuring the REF 54_ feeder terminals or REM 543 machine terminals correctly with the Relay Configuration Tool. Furthermore, chapter 4 provides some practical tips as well as recommendations and restrictions for doing the configuration.Please note that the examples and dialogue pictures of the Relay Configuration Tool in this manual refer to REF 54_ feeder terminals.1.Relay Configuration ToolThe Relay Configuration Tool, which is a standard programming system for RED500devices, is used for configuring the protection, control, condition monitoring, measure-ment and logic functions of the feeder terminal. The tool is based on the IEC 1131-3standard, which defines the programming language for relay terminals, and includes thefull range of IEC features. The PLC logics are programmed with Boolean functions,timers, counters, comparators and flip-flops. The programming language described inthis manual is a function block diagram (FBD) language.2.Specification for RE_ 54_ ConfigurationsPrior to starting the configuration of a relay terminal, the Specification for Relay Con-figuration is to be filled out. The specification can be found as appendix B for REF 54_and appendix C for REM 543 in the end of this manual.The purpose of the specification is to provide the technical information required for theproper configuration of the relay terminals.3.Editing the RE_ 54_ Relay Terminal Configurations 3.1.Getting startedStart up the tool by double clicking the icon. After adding a new object as an empty con-figuration to the CAP505 environment (refer to the CAP505 Operator’s Manual, 1MRS750838-RUM), the program opens an empty project template (see figure below) with atoolbar at the top. The next step is to build the project tree structure by inserting librar-ies, 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 theproject and different looking icons represent different types of files. The tree alwayscontains 4 subtrees: Libraries, Data Types, Logical POUs and Physical Hardware.Fig. 3.1-1. The project tree with its four subtrees.The project tree is the main tool for editing the project structure. Editing the projectstructure means inserting POUs or worksheets to the project structure or deleting exist-ing ones. The editors for editing the data of the code bodies and the variable declarationcan be called by double clicking the corresponding object icons.If you intend to edit an old project, note that saving the changes made with the “save as”project unchanged, the project has to be saved with a new name before making anychanges.3.1.1.LibrariesBefore editing any worksheets of POUs, the whole project tree structure must be build.The function block library (protection, control, measurement, condition monitoring andstandard functions) needed in the relay configuration is to be inserted to the “Libraries”subtree.Before inserting the library to the project, all worksheets are to be closed; otherwise theI/O description of function blocks will be confused. The programs, function blocks (e.g.NOC3Low, the low set stage of non-directional three-phase overcurrent protection) andfunctions of the library can be reused in the new project, which is edited.The library, e.g. REFLIB01 for REF54_ (see the figure below), includes all availablefunction blocks. Therefore, attention is to be paid to which function blocks can be usedin a specific configuration. For example, if the protection library PR116005(1MRS116005) has been ordered, the auto-reclose function block AR5Func cannot beinserted to the project since AR5Func is not included in that library.Fig. 3.1.1.-1. Libraries for REF54_ and REM 543.3.1.2.Logical POUsIn the project tree editor and in the library editor, the “Logical POUs” subtree representsa directory for all POUs related to the project. The maximum of 20 POUs can beinserted to the subtree. The figure below shows a “Logical POUs” subtree with 6 POUs;“Measure”, “Prot_Me” and “Co_CM_A” represent FBD (Function Block Diagram)programs, and “Horizon”, “CONDIS” and “SWG” are FBD function blocks.Fig. 3.1.2.-1. “Logical POUs” subtree with 6 POUs.3.1.3.Program Organisation Unit (POU)Each Program Organisation Unit, a POU, consists of several worksheets: a POUdescription worksheet for comments, a variable worksheet for variable declarations anda code body worksheet for the relay configuration. The name of each worksheet is indi-cated beside the corresponding icon and the *-symbol after the name of a worksheetindicates that the worksheet has not been compiled yet.Fig. 3.1.3.-1. Program organisation unit with three worksheets.The description worksheet (e.g. ProtectT) illustrated below is for describing the POU or the configuration element. The worksheet is named by adding a ’T’ to the name of the POU.Fig. 3.1.3.-2. Description worksheet.The variable worksheet (e.g. ProtectV) is for the variable declaration. The worksheet is named by adding a ’V’ to the name of the POU.Fig. 3.1.3.-3. Variable declaration worksheet.A code body worksheet (e.g. Protect, Measure) is for a code body declaration in theform of an FBD, a Function Block Diagram. All configurations for relays of the RED500 platform are made in the graphical FBD language. A code body programmed in theFBD language is composed of functions and function blocks that are connected to eachother using variables or lines. An output of a function block can be connected to the out-put of another function block only via an OR gate (refer to section 4.1.)Fig. 3.1.3.-4. Code body declaration in FBD language.Even though the tool permits adding several graphical worksheets under one POU, onlyone worksheet is recommended to be used per POU. If more space is needed for a con-figuration, the worksheet size can be increased or, if more I/O points are required, thefunctionality can be divided to several POUs. Note that one POU has altogether 511 I/Opoints available for function blocks. For example, the function block NOC3High in thefigure above includes 15 I/O points, which means that there are still 496 I/O pointsavailable.3.1.4.Physical hardwareIn the project tree editor, the physical hardware is represented as a subtree (see below)after the hardware of the relay terminal, i.e. Configuration, Resource and Tasks, hasbeen defined.Fig. 3.1.4.-1. Example of a subtree for the physical hardware.The configuration elements available in the “Physical Hardware” subtree may differfrom configuration to configuration. Each terminal of the RED 500 platform can beconfigured separately.3.1.4.1.ConfigurationThe name and target of the configuration are first defined in the dialogue Properties/Configuration.Fig. 3.1.4.1.-1. Defining the configuration type.3.1.4.2.ResourceThe configuration “Conf” above is for the REF 543 resource (the selected processortype), which is defined in the dialogue Properties/Resource. The resource must also begiven a name.Fig. 3.1.4.2.-1. Defining the processor type.Hardware versionAfter selecting the processor type, click “Settings...” in the dialogue Properties/Resource (see figure above) to define the correct hardware version.Note! After selecting the correct hardware version (Relay Variant; see figure below), donot click OK but wait until the next dialogue opens and select “Analog Channels” (seefigure 3.1.4.2.-3.).Fig. 3.1.4.2.-2. Defining the hardware version.Analogue channelsIn the dialogue Settings/Analog Channels, click each channel in turn to select the meas-uring device and signal type for the channels used and select “Not in use” for otherchannels.Furthermore, the technical data and measurements for the selected channels are to becompleted correctly before the configuration is used in a real application.Fig. 3.1.4.2.-3. Defining the analogue channels.Technical dataFig. 3.1.4.2.-4. Defining the rated values for the selected channel.MeasurementsFor information about the special measurements required for each function block, refer to the Technical Descriptions of Functions (CD-ROM 1MRS 750889-MCD).Phase currents and voltagesIf the signal type selected for an analogue channel is to be shown in the MIMIC view via the MMIDATA_ function block (MIMIC dynamic data point), the true RMS mode must be selected in the “Special Measurements” dialogue. 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 analogue channels (IL1, IL2, IL3) used.Fig. 3.1.4.2.-5. Selecting the required special measurement modes for phase current measurement.Neutral currentWhen e.g. 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 Io is measured. Unless intermittent earth-fault protection has been chosen, the following configuration error indication will appear on the display of the relay terminal ( # denotes the number of the analogue channel in question):System: SUPERVCh # errorFig. 3.1.4.2.-6. Selecting the required special measurement modes for neutral current measurement.FrequencyWhen, for example, any of the function blocks MEFR_ (system frequency measure-ment), SCVCSt_ or Freq1St_ 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 / Measurements button in the “Con-figuration of REF543” dialogue).Fig. 3.1.4.2.-7. Selecting the required special measurement modes for frequency meas-urement.Virtual channelsIn case no measuring devices are applied for measuring residual voltage (Uo) and neu-tral current (Io), the virtual channels 11 and 12 must be used.Fig. 3.1.4.2.-8. Using virtual channels 11 and 12 in case no measuring devices are applied for measuring Io and Uo.In case of the virtual channel 12, voltage measuring devices must be associated with phase voltages.Fig. 3.1.4.2.-9. Associating voltage measuring devices with phase voltages.After a compiled configuration is downloaded to a relay and the relay is started (storing and resetting are done), it will internally check whether the analogue channels are cor-rectly configured regarding the analogue inputs of function blocks. If the connectedchannels have been configured incorretly, the ERR output signal of the specific function block goes active and the event E48 is sent. Furthermore, either the event E13 or E5 is sent depending on the function block in question.Binary inputsThe filter time is set for each binary input of the relay terminal via the resource settings dialogue “Binary Inputs”. Inversion of the inputs can also be set. For further informa-tion refer to the Technical Reference Manual of REF 54_ or REM 543.Fig. 3.1.4.2.-10. Defining the binary inputs.MeasurementsWhen the MEPE7 function block (power and energy measurement) is used, the measur-ing mode must be selected via the resource settings dialogue “Measurements”.Fig. 3.1.4.2.-11. Selecting the measuring mode for power and energy measurement.Condition monitoringValues for the circuit-breaker wear function blocks CMBWEAR 1 and 2 can be set via the resource settings dialogue “Condition Monitoring”.Fig. 3.1.4.2.-12. Setting the values for circuit-breaker wear.3.1.4.3.TasksPrograms and tasksPrograms are associated with tasks via the dialogues Properties/Task and Properties/Program. Cyclic tasks are activated within a specific time interval and the program isexecuted periodically.The two dialogues below illustrate the association of a program type (Prot_Me) with atask (Task1) (see also figure 3.1.4.-1. in section “Physical hardware”).Fig. 3.1.4.3.-1. Naming a cyclic task.Fig. 3.1.4.3.-2. Associating the selected task with the desired program type.Task intervalGenerally, the operation accuracy is increased when the task speed is increased, but atthe same time, the load of the microprocessors is increased as well. Although the taskspeed can be freely chosen with the tool, it is necessary to determine a maximum taskexecution interval for each function block; otherwise the operation accuracy and operatetimes for protection functions cannot be guaranteed. The maximum task executioninterval is based on test results and has also been used in the type testing of the functionblocks. The recommended task execution interval quaranteed by the manufactirer canbe found in section Technical Data in the technical description of each function block.According to the standard, the Relay Configuration Tool includes the possibility ofdefining the tasks on two different levels:1) each POU (= program organisation unit) can be tied to a separate task2) a separate function block inside a POU can be tied to any taskHowever, the alternative 2) is not yet supported in the RED environment, which meansthat if a separate function block inside a POU is given a separate task definition, it willbe ignored when transferred to the relay. This means that when the function blocks arebeing placed in different POUs, not only the category of the function (protection, con-trol, etc.) but also the maximum task execution interval should be considered since allfunction blocks inside a POU will run at the same speed.For further information about the microprocessor loads and task execution intervals offunction blocks refer to the manual “Technical Descriptions of Functions, Introduction”(CD-ROM: Technical Descriptions of Functions, 1MRS750889-MCD).The task execution interval for each task is defined via the dialogue Properties/Task(click “Settings...”). For example, the task execution interval for Task1 in figure belowis defined as 10 ms, which means that the program Prot_Me is run 100 times per onesecond.Fig. 3.1.4.3.-3. Setting the task execution interval for a program.3.2.Global variablesThe physical contacts of RE_ 54_ are defined in the “Global Variables” worksheet.Declarations for the physical contacts are automatically defined when the correct hard-ware version of RE_ 54_ is selected. Declarations for the analogue channels are createdafter the analogue channel settings defined in the resource settings dialogue have beenapproved.Fig. 3.2-1. Global Variables worksheet.3.3.Declaring variablesAt its beginning, each programmable controller POU type declaration is to contain atleast one declaration part that specifies the types of the variables used in the organisa-tion unit. The declaration part shall have the textual form of one of the keywordsV AR_INPUT, VAR_OUTPUT, V AR and V AR_EXTERNAL followed by one or moredeclarations separated by semicolons and terminated by the keyword END_V AR. Allthe comments you write must be edited in parentheses and asterisks.(**********************************)(*Variable declaration*)(*of REF 541*)(**********************************)Caution is required regarding comments and variable declarations. The following codeexample will be compiled successfully but because of the non-closed comment theEND_VAR - V AR_EXTERNAL couple will be excluded and thus the channel numbersbecome local variables of the POU and they get the initial value zero.V AR (*AUTOINSERT*)NOC3Low_1:NOC3Low; (* Erroneous nonclosed comment *END_VARV AR_EXTERNALU12:SINT;(* Measuring channel 8 *)U23:SINT;(* Measuring channel 9 *)U31:SINT;(* Measuring channel 10 *)END_VARThree examples of creating the textual declaration for different kinds of graphical pro-grams are given below.EXAMPLE 1.•POU type:FBD program •Function block type declaration: VARINPUT1:BOOL :=FALSEINPUT2:BOOL :=FALSEINPUT3:BOOL :=FALSEOUTPUT:BOOL :=FALSE END_VARFig. 3.3-1. Function block image.EXAMPLE 2.•POU type:NOC3Low, manufacturer dependent function block •Function block type declaration:V AR_INPUTIL1:SINT :=0;(* Analogue channel *)IL2:SINT :=0;(* Analogue channel *)IL3:SINT :=0;(* Analogue 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_VARV AR_OUTPUTSTART:BOOL :=FALSE; (* Start signal *)TRIP:BOOL :=FALSE; (* Trip signal *)CBFP:BOOL :=FALSE; (* CBFP signal *)ERR:BOOL :=FALSE; (* Error signal *)END_VARFig. 3.3-2. Function block image of NOC3Low.EXAMPLE 3.•POU type:Configurer dependent FBD function block CONDIS •Function block type declaration:Fig. 3.3-3. Type declaration of the configurer made function block CONDIS.Fig. 3.3-4. Use of the configurer made function block CONDIS.Fig. 3.3-5. Contents of the CONDIS function block.In the example 3 above, part of the configuration has been separated to a configurermade function block called CONDIS. Such function blocks may not be given namesalready belonging to library functions blocks or IEC standard function blocks. Thefunction block CONDIS has been used like any other function block in the graphicalprogram. The order of inputs of a function block that has been inserted to a worksheetmay not be changed. It must also be remembered that a function block with an instancenamed by the configurer can only be inserted to the project once.3.4.Variables declared as globalThe range of validity of the declarations included in the declaration part shall be“local”to the POU in which the declaration part is contained. One exception to this rule are var-iables that have been declared to be “global”. Such variables are only accessible to aPOU via a V AR_EXTERNAL declaration. The type of a variable declared in aV AR_EXTERNAL block shall agree with the type declared in the V AR_GLOBALblock of the associated program, configuration or resource.Fig. 3.4-1. Local and global variables.The figure above illustrates the ways how values of variables can be communicated among software elements. 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 pro-grams 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. Do not use binary inputs or outputs for data transfer between tasks.Despite the fact that according to the IEC standard 1131-3 all local variables that have no initial value are initially FALSE (0), the initial values for all local variables have to be given in the variable worksheet of the logical POU. This is because somewhere in the configuration, especially in the beginning of running the configuration i.e. when the relay is started up, the variable can be used before the initial value has been created for the variable. The initial values for global variables are given in the global variable worksheet (see CASE 1 below).CASE 1. Variables declarationV ARIABLE WORKSHEET of logical POU*********************************************************************V ARTRIPPING:BOOL:= FALSE;BLOCK:BOOL:= TRUE;TMP1:BOOL:= FALSE;END_VARV AR_EXTERNALPS1_4_HSPO1 :BOOL; (* Double pole high speed power output *)(* 4.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_VARV AR_EXTERNALTCS1_ALARM:BOOL;END_VAR********************************************************************* GLOBAL V ARIABLE WORKSHEET*********************************************************************V AR_GLOBALPS1_4_HSPO1AT %QX 1.1.2 :BOOL := FALSE;(* Double pole high speed power output X4.1/10,11,12,13 *) PS1_4_HSPO2AT %QX 1.2.2 :BOOL := FALSE;(* Double pole high speed power output X4.1/15,16,17,18 *) PS1_4_HSPO3AT %QX 1.3.2 :BOOL := FALSE;(* Double pole high speed power output X4.1/6,7,8,9 *) END_VARV AR_GLOBALTCS1_ALARM:BOOL:= FALSE;END_VAR*********************************************************************piling the projectThe “Build Project” mode in the “Make” menu is used to compile the whole project forthe first time after editing, which means compiling all POUs, global variables, resourcesetc., whereas the “Make” mode can be used to compile the worksheets that have beenedited. The changed worksheets are marked with an asterisk in the project tree editor.“Make” is the standard mode for compiling and should normally be used when you havefinished editing.In the Relay ConfigurationTool you can view the execution order of the different func-tions or function blocks in your worksheet. The execution order corresponds to theintermediate PLC code created while compiling. Note that the execution order can onlybe seen if you have already compiled the worksheet using the menu item “CompleteWorksheet” in the submenu “Make”.By editing the mwt.ini file, one can affect the execution order. The line below can beadded to section [MAKE]:SH_EXECUTION_ORDER_TOP_BOTTOMSets the order of execution of functions and function blocks in graphical editor0Sets the execution order from left to right1Sets the execution order from top to bottomThe default value is …0“. The execution order can only be changed when compiling aworksheet again.4.Main Configuration Rules for RE_ 54_4.1.General Make sure that all analogue 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 figure below).Fig. 4.1-1. Use of an explicit Boolean OR gate (on the right).4.2.Binary inputs Do not write binary inputs - like BIO2_7_BI2.Fig. 4.2-1. Writing global binary inputs is not allowed.Binary inputs can be read from several locations.I>I>>TRIP TRIP PS1_4_HSPO1PS1_4_HSPO1I>I>>TRIP TRIP PS1_4_HSPO1"wired-OR" structure is not allowed an explicit Boolean "OR" block is required instead ORFig. 4.2-2. Correct way of using global binary inputs.4.3.Explicit feedbackAn explicit feedback loop may not be used. In case the tool gives a warning about thefeedback loop after compiling, the loop must be broken up by connecting the input ofthe function block and the output of another function block separately to the auxiliaryvariable.Fig. 4.3-1. Explicit feedback loop is not allowed.Fig. 4.3-2. Explicit feedback via the auxiliary variable FEEDBACK.4.4.Measurement function blocksAll the measurement inputs of the function blocks must be connected. In case e.g. thethree-phase current measurement function block MECU3A is implemented by twophases of currents, one of the currents available must be connected to the remainingthird input of MECU3A. Unless something is connected to the third current input, thefunction block will attempt to use the sensor channel 1 instead of the empty channel,and if no measurements have been defined for channel 1, a supervision error will result.4.5.WarningsIn case of the indication “Warning: Instance ‘xx’ is never used” in connection with Array compilation, remove the corresponding instances of the function block from the varia-bles worksheet of the POU. The tool will not give a separate warning for unused varia-bles, which is why they need to be removed manually. When a global variable is addedto a sheet as a copy-paste -function, the global radio button has to be chosen (see figurebelow); otherwise the variable becomes a local variable of the POU, which is due to theauto-insert feature of the tool (global variable = V AR_EXTERNAL, local variable =V AR).Fig. 4.5-1. Copying a global variable to a worksheet of a POU.4.6.Execution orderCheck the execution order after the compilation. The connection of simple variables toeach other generates a code, the execution order of which in relation to the callingsequence of POUs cannot be seen by means of the Layout Execution Order function.Fig. 4.6-1. The INTERLOCKING variable is updated (TMP1) during the task executioncycle (see the execution order 1,2,3).In addition, the execution order may be illogical or even incorrect considering the func-tionality.Fig. 4.6-2. The explicit feedback (TMP1) delays the updating of the INTERLOCKINGvariable by one task execution cycle.If the MOVE function is used instead of direct connection, the execution order can beutilised in concluding whether the result is desirable.4.7.F-keyThe freely programmable F-key is declared as VAR_GLOBAL in the global variableworksheet as follows:F001V021:BOOL:=0;(* Free configuration point (F-key) *)The F-key parameter can be added to the configuration logic as an external variable(V AR_EXTERNAL). Similar parameters that can be inserted to a relay logic are listedbelow: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 & wave-form memory*)*)F001V020:BOOL:=0;(*(W) Resetting of accumulated energy measurement*) F001V021:BOOL:=0;(’(R, W) Free configuration point (F-key)*)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)*)。
