re 54 confenc

8/8/2019 RE 54 ConfENc

1/113

$%% $XWRPDWLRQ

5() B 5(0 B 5(&

&RQILJXUDWLRQ *XLGHOLQH


2/113


3/113


4/113

4 ABB Automation

1MRS 750745-MUMConfiguration Guideline5() B 5(0 B5(&

5.1.1.3. Cyclic sending generation ..................................435.1.1.4. Cyclic communication check .............................. 445.1.1.5. Blocking ............................................................. 455.1.1.6. Control of objects ............................................... 465.1.1.7. Bypass mode ..................................................... 46

5.2. Events from the measurement function blocks ...........................47

$33(1',; $ 5HOD\ &RQILJXUDWLRQ 3URFHGXUH

$33(1',; % 6SHFLILFDWLRQ IRU )HHGHU 7HUPLQDO&RQILJXUDWLRQ7.1. General data ...............................................................................497.2. Electrotechnical data .................................................................. 507.3. Functionality ................................................................................ 607.4. Relay MIMIC configuration .........................................................627.5. Functionality logic .......................................................................647.6. Feeder terminal settings ............................................................. 65

$33(1',; & 6SHFLILFDWLRQ IRU 0DFKLQH 7HUPLQDO&RQILJXUDWLRQ8.1. General data ...............................................................................678.2. Electrotechnical data .................................................................. 688.3. Functionality ................................................................................ 798.4. Relay MIMIC configuration .........................................................818.5. Functionality logic .......................................................................838.6. Machine terminal settings ........................................................... 84

$33(1',; ' 6SHFLILFDWLRQ IRU 5HPRWH 0RQLWRULQJ DQG&RQWURO 8QLW &RQILJXUDWLRQ9.1. General data ...............................................................................859.2. Electrotechnical data .................................................................. 869.3. Functionality ................................................................................ 939.4. LED configuration .......................................................................949.5. Remote monitoring and control unit settings .............................. 96

$33(1',; ( 3RZHU 4XDOLW\ $SSOLFDWLRQ *XLGHIRU +DUPRQLFV10.1.Power quality and harmonics ..................................................... 9710.2.Background for harmonics ......................................................... 9710.3.Harmonic sources ...................................................................... 9910.4.System response characteristics ............................................. 10210.5.Effects of harmonics ................................................................. 10410.6.Applications for harmonic measurements ................................ 105

5HIHUHQFHV

*ORVVDU\

,QGH[


5/113

1MRS 750745-MUM Configuration Guideline 5() B 5(0 B 5(&

ABB Automation 5

$ERXW WKLV PDQXDO

This guideline describes in general the procedures for configuring the REF 54_feeder terminals, REM 54_ machine terminals and REC 523 remote monitoring andcontrol units correctly with the Relay Configuration Tool. In this document, the termdevice will be used when referring to all three products.

Section 3 describes step-by-step the engineering actions required to create a relayconfiguration for a single device. Section 4 defines a set of programming rules thatshould be followed while creating the configuration or at least carefully checkedwhen finalizing the configuration. Finally, section 5 provides some engineering tipsfor doing the configuration.

For instructions on operating the tool itself, refer to the CAP 505 Operators Manual(see References on page 108 ).

The version C of the Configuration Guideline complies with products of the ReleaseSA 2.0. For information about the changes and additions compared to earlierrevisions, refer to the Technical Reference Manual of the appropriate product (seeReferences on page 108 ).

Please note that the examples and dialogue pictures of the Relay Configuration Toolin this manual refer to REF 54_ feeder terminals. The corresponding cases anddialogues may be slightly different for REM 54_ and REC 523.

5HYLVLRQ KLVWRU\

Version B/30.06.99:- Text changed in the following sections: Libraries, Analogue channels/Measurements/Frequency,

Analogue channels/Virtual channels- Index added

Version C/11.05.2000:- Text added/changed and figures updated throughout the manual- Sections Error outputs of application function blocks and Engineering Tips added- Appendices D (Specification for Remote Monitoring and Control Unit Configuration) and

E (Power Quality Application Guide for Harmonics) added- Appendices B and C updated- References added- Glossary added


6/113


7/113


ABB Automation 7

6SHFLILFDWLRQ IRU 5HOD\ &RQILJXUDWLRQ

Prior to starting the configuration of a product, the specification for relayconfiguration is to be filled out. Separate specifications for REF 54_, REM 54_ andREC 523 can be found in appendices B, C and D in the end of this manual.

The purpose of the specification is to provide the technical information required forthe proper configuration of the products.


8/113

8 ABB Automation


(GLWLQJ WKH 5HOD\ &RQILJXUDWLRQV

*HWWLQJ VWDUWHG

Start up the CAP505 tool by double clicking the icon. After adding a new object as

an empty configuration to the CAP505 environment (refer to the CAP505Operators Manual, see References on page 108 ), the program opens an emptyproject template (see Figure 3.1.-1 below) with a toolbar at the top. The next step isto 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 atree. The project tree is illustrated with several icons. Most of the icons represent afile of the project and different looking icons represent different types of files. Thetree always contains 4 subtrees: Libraries, Data Types, Logical POUs and PhysicalHardware.

)LJ 7KH SURMHFW WUHH ZLWK LWV IRXU VXEWUHHV

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 deletingexisting ones. The editors for editing the data of the code bodies and the variabledeclaration can be called by double clicking the corresponding object icons.

If you intend to edit an old project, note that saving the changes madewith the save as command will not work as in other Windowsprograms. In case you want to keep the old project unchanged, theproject has to be saved with a new name before making any changes.

/LEUDULHV

Before editing any worksheets of POUs, the whole project tree structure must bebuild. The function block library (protection, control, measurement, conditionmonitoring and standard functions) needed in the relay configuration is to be

inserted to the Libraries subtree. (For instructions on announcing libraries, referto the manual Relay Configuration Tool, Tutorial, see References on page 108. )

Before inserting the library to the project, all worksheets must be closed; otherwisethe I/O description of function blocks will be confused. The programs, functionblocks (e.g. NOC3Low, the low set stage of non-directional three-phase overcurrentprotection) and functions of the library can be reused in the new project, which isedited.

The library, e.g. REFLIB01 for REF54_ (see Figure 3.1.1.-1 below), includes thefull set of function blocks, but only those ordered by the customer can be used in theconfiguration.

!


9/113


ABB Automation 9

Note that if a configuration is transferred to a newer version of the product, thelibrary in the project must also be updated.

)LJ /LEUDULHV IRU 5() B 5(0 B DQG 5(&

The library version to be selected depends on the software revision of the product aslisted in the table below. The directory path to the libraries is \CAP505\Common\IECLibs\Fi.

3URGXFW 6RIWZDUHUHYLVLRQ

/LEUDU\ ILOH QDPH

REF 541 A COMMU_01, CONDM_01, CONTR_01,MEASU_01, PROTE_01, STAND_01

B REFLIB01C REFLIB02

REF 541 (RTD1) A REFLIB02REF 543 C and D COMMU_01, CONDM_01, CONTR_01,

MEASU_01, PROTE_01, STAND_01E REFLIB01F REFLIB02

REF 543 (RTD1) A REFLIB02REF 545 A COMMU_01, CONDM_01, CONTR_01,

MEASU_01, PROTE_01, STAND_01B REFLIB01

C REFLIB02REM 543 A REMLIB01B REMLIB02

REM 543 (RTD1) A REMLIB02REM 545 A REMLIB02REM 545 (RTD1) A REMLIB02REC 523 A RECLIB01

B RECLIB01C RECLIB02


10/113

10 ABB Automation


3URJUDP RUJDQLVDWLRQ XQLW

Each Program Organisation Unit, a POU, consists of several worksheets: adescription worksheet for comments, a variable worksheet for variable declarationsand a code body worksheet for the configuration. The name of each worksheet isindicated beside the corresponding icon and the *-symbol after the name of aworksheet indicates that the worksheet has not been compiled yet.

)LJ 3URJUDP RUJDQLVDWLRQ XQLW ZLWK WKUHH ZRUNVKHHWV

The description worksheet (e.g. ProtectT) illustrated below is for describing thePOU or the configuration element. The worksheet is automatically named by adding

a T to the name of the POU.

)LJ 'HVFULSWLRQ ZRUNVKHHW

The variable worksheet (e.g. ProtectV) is for the variable declaration. The worksheetis automatically named by adding a V to the name of the POU. The variableworksheet is not edited manually but is created by the tool.

)LJ 9DULDEOH GHFODUDWLRQ ZRUNVKHHW


11/113


ABB Automation 11

A code body worksheet (e.g. Protect) is for a code body declaration in the form of an FBD, a Function Block Diagram. All configurations for the devices of the RED500 platform are made in the graphical FBD language. A code body programmed inthe FBD language is composed of functions and function blocks that are connectedto each other using variables, connection lines or connectors. An output of a function

block can be combined with the output of another function block e.g. via an OR gate(refer to section General on page 35 ). Connectors are objects that can be usedinstead of connection lines, for example where the distance between two objects onthe worksheet is great. Connectors can only be used within one worksheet and theyare resolved by textual names. Connectors should be used with care since the toolmay not warn if a match to a connector cannot be found (for example, thecomparison of connectors is case sensitive). Note that visually, connectors aredistinguished from variables by embedding them with brackets.

)LJ &RGH ERG\ GHFODUDWLRQ LQ )%' ODQJXDJH

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 neededfor a configuration, the worksheet size can be increased or the functionality can be

divided into several POUs. Avoid creating very large configurations per POU sincethe RED500 PLC environment has an inherent limit for the number of input/outputpoints per POU. The limit is 511 I/O points and is consumed by called function block instances only. Note that this limit is checked during the configuration downloading.If the downloading fails for this reason, the user has to divide the POU into smallerunits. For example, the function block NOC3Low in Figure 3.1.2.-4 above includes15 I/O points. I/O points are consumed regardless of whether they are connected ornot.


12/113

12 ABB Automation


/RJLFDO 328V

In the project tree editor and in the library editor, the Logical POUs subtreerepresents a directory for all POUs related to the project. The maximum of 20 POUscan be inserted to the subtree. Figure 3.1.3.-1 below shows a Logical POUssubtree with 4 POUs; CondMon represents a function block, Confirmrepresents a function, and Measure and Control are programs. The associatedicon represents the POU type.

)LJ /RJLFDO 328V VXEWUHH ZLWK 328V

Each POU type has specific characteristics from the programming point of view.

A function yields exactly one data element which is evaluated from its inputparameters. In other words, a function cannot contain any internal stateinformation. Furthermore, a function can call other functions but no functionblocks.

A function block (FB) can return 0,1,2.. output values and can have internalvariables. Function blocks can call any other function or function block. Multiplecopies of function blocks are called instances and each instance is given anidentifier.

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. Figure3.1.3.-2 below shows the dialogue for inserting POUs. The programming language(FBD) for the POU and the return data type for functions are also selected here. ThePLC type and Processor type selections should be left to their default values.


13/113


ABB Automation 13

)LJ ,QVHUWLQJ D QHZ SURJUDP 328 FDOOHG 'HPR ZKLFK LV SURJUDPPHG XVLQJ WKH IXQFWLRQ EORFN GLDJUDP ODQJXDJH

At first, a POU framework is created, i.e. empty POUs are inserted to the project

according to the Specification for Relay Configuration filled out prior to starting theconfiguration procedure. The physical hardware must be defined before creating theactual contents for the POUs, otherwise predefined target-specific POUs will not beavailable for the programmer.

The task execution intervals recommended for function blocks must be consideredalready when defining the POU framework. In general, each POU forms a functionalunit, e.g. for protection function blocks. Some function blocks, however, require adifferent task than most of the same category and must thus be assigned a separatePOU. For example, the task execution interval of most protection function blocks is10 ms but Freq1St_ requires the task of 5 ms, which is why it usually needs aseparate POU. However, if all the protection function blocks used are associated

with the task of 5 ms, no separate POU is required for Freq1St_.


14/113

14 ABB Automation


3K\VLFDO KDUGZDUH

In the project tree editor, the physical hardware is represented as a subtree (seeFigure 3.1.4.-1 below) after the hardware of the device, i.e. Configuration, Resourceand Tasks, has been defined.

)LJ ([DPSOH RI D VXEWUHH IRU WKH SK\VLFDO KDUGZDUHThe configuration elements available in the Physical Hardware subtree may differfrom configuration to configuration. Each terminal of the RED 500 platform can beconfigured separately.

&RQILJXUDWLRQ

The name of the configuration and the appropriate product family, PLC type, arefirst defined in the dialogue Properties/Configuration.

)LJ 'HILQLQJ WKH FRQILJXUDWLRQ W\SH


15/113


16/113

16 ABB Automation


)LJ 6HOHFWLQJ WKH GLDORJXH IRU DQDORJXH VHWWLQJV VHH )LJXUHEHORZ

$QDORJXH FKDQQHOV

In the dialogue Settings/Analog Channels, click each channel in turn to select themeasuring device and signal type for the channels used and select Not in use forother channels.

Furthermore, the technical data and measurements for the selected channels are tobe completed correctly before the configuration is used in a real application.

)LJ 'HILQLQJ WKH DQDORJXH FKDQQHOV


17/113


ABB Automation 17

7HFKQLFDO GDWD

)LJ 'HILQLQJ WKH UDWHG YDOXHV IRU WKH VHOHFWHG PHD

0HDVXUHPHQWV

For information about the special measurements required for each function block,refer to the Technical Descriptions of Functions (see References on page 108 ).

7UXH 506 DQG QG KDUPRQLF UHVWUDLQW PHDVXUHPHQWV

If the signal type selected for an analogue channel is going to be measured by anymeasurement function block (MECU3A etc.), the true RMS mode must be selectedin 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, the2nd harmonic restraint must be selected for the analogue channels (IL1, IL2, IL3)used.

)LJ 6HOHFWLQJ WKH UHTXLUHG VSHFLDO PHDVXUHPHQW PRGFXUUHQW PHDVXUHPHQW


18/113

18 ABB Automation


1HXWUDO FXUUHQW

When the DEF2_ function block (directional earth-fault protection) is going to beused, intermittent earth-fault protection must be selected for the channel via whichthe current I 0 is measured. The intermittent earth-fault protection can be enabled forthe maximum of two physical channels at a time. Note that the intermittent earth-fault protection requires the residual voltage for directional operation. Therefore, thechannel for the residual voltage U 0 must be defined before the selection can bemade. Unless intermittent earth-fault protection has been chosen, the followingconfiguration error indication will appear on the display of REF 54_ or REM 54_ (# denotes the number of the analogue channel in question):

System: SUPERV

Ch # error

)LJ 6HOHFWLQJ WKH UHTXLUHG VSHFLDO PHDVXUHPHQW PRGHVFXUUHQW PHDVXUHPHQW

)UHTXHQF\ When, for example, any of the function blocks MEFR_ (system frequencymeasurement) or SCVCSt_ (synchrocheck/voltagecheck function) is in use,frequency measurement must be selected for the channel via which the voltage ismeasured for frequency measurement (for example: Channel 10, VoltageTransformer 4, Signal type U3 / Measurements button in the dialogueConfiguration of REF543). The power quality function blocks PQCU3H andPQVO3H require frequency measurement for the channel that is connected to theFREQ_REF input i.e. the channel for frequency reference (for more informationrefer to the manuals of PQCU3H and PQVO3H on the CD-ROM TechnicalDescriptions of Functions, see References on page 108) . Furthermore, frequency

protection must be selected if the function block Freq1St_ is in use.


19/113


ABB Automation 19

)LJ 6HOHFWLQJ WKH UHTXLUHG VSHFLDO PHDVXUHPHQW PRGPHDVXUHPHQW

9LUWXDO FKDQQHOV

In case no measuring devices are applied for measuring residual voltage (U 0) andneutral current (I 0), the virtual channels 11 and 12 can be used. If only one virtualchannel is used, the channel will be numbered as channel 11, regardless of whetherresidual voltage or neutral current is calculated. If both I 0 and U 0 are calculated,channel 11 will be used for I 0S and channel 12 for U 0S .

)LJ 8VLQJ YLUWXDO FKDQQHOV DQG LQ FDVH QR PHDVDSSOLHG IRU PHDVXULQJ ,

DQG 8


20/113

20 ABB Automation


In case of the virtual channels for calculating I 0 and U 0, phase currents and voltagesmust be associated with current and voltage measuring devices (see Figures3.1.4.2.-10 and 3.1.4.2.-11 below).

)LJ $VVRFLDWLQJ SKDVH FXUUHQWV ZLWK FXUUHQW PHDVXUL

)LJ $VVRFLDWLQJ SKDVH YROWDJHV ZLWK YROWDJH PHDVXULQ

After a compiled configuration is downloaded to a device, it willinternally check whether the analogue channels are correctly configuredregarding the analogue inputs of function blocks. If the connectedchannels have been configured incorretly, the ERR output signal of thespecific function block goes active and the analogue channelconfiguration error event (E48) is sent. Some function blocks havespecial error events that are explained in the corresponding functionblock manuals on the CD-ROM Technical Descriptions of Functions(see References on page 108 ).

!


21/113


ABB Automation 21

'LJLWDO LQSXWV

The filter time is set for each digital input of the device via the resource settingsdialogue 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 furtherinformation refer to the Technical Reference Manual of REF 54_, REM 54_ orREC 523 (see References on page 108 ).

)LJ 'HILQLQJ WKH GLJLWDO LQSXWV


22/113

22 ABB Automation


0HDVXUHPHQWV

When the MEPE7 function block (power and energy measurement) is used, themeasuring mode must be selected via the resource settings dialogueMeasurements. True RMS measurement must also be selected for the channelsused by MEPE7.

Note that the measuring modes can only be selected after the analogue channels havebeen defined (see Figure 3.1.4.2.-4 on page 16 ).

)LJ 6HOHFWLQJ WKH PHDVXULQJ PRGH IRU SRZHU DQG HQHUJ\ P


23/113


ABB Automation 23

&RQGLWLRQ PRQLWRULQJ

Values for the circuit-breaker wear function blocks CMBWEAR 1 and 2 can be setvia the resource settings dialogue Condition Monitoring.

)LJ 6HWWLQJ WKH YDOXHV IRU FLUFXLW EUHDNHU ZHDU


24/113

24 ABB Automation


7DVNV

3URJUDPV DQG WDVNV

Programs are associated with tasks via the dialogues Properties/Task and Properties/ Program. One task may include several programs. Cyclic tasks are activated within

a specific time interval and the program is executed periodically.The two dialogues below illustrate the association of a program type (Prot_Me) witha task (Task1) (see also Figure 3.1.4.-1 on page 14 ).

)LJ 1DPLQJ D F\FOLF WDVN

)LJ $VVRFLDWLQJ WKH VHOHFWHG WDVN ZLWK WKH GHVLUHG

7DVN LQWHUYDO

Generally, the operation accuracy is increased when the task speed is increased, butat 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 determine amaximum task execution interval for each function block; otherwise the operationaccuracy and operate times for protection functions cannot be guaranteed. Themaximum task execution interval is based on test results and has also been used inthe type testing of the function blocks. The recommended task execution intervalquaranteed by the manufacturer can be found in section Technical Data in thetechnical description of each function block. Furthermore, certain function blocks,e.g. MEDREC16, must be tied to the task given by the manufacturer, otherwise theoperation of these function blocks is not possible. For more information about thetask execution intervals of function blocks, refer to the manual Technical


25/113


ABB Automation 25

Descriptions of Functions, Introduction on the CD-ROM 1MRS750889-MCD, seeReferences on page 108 ). For microprocessor loads refer to sectionDownloading the configuration on page 33 .

According to the standard, the Relay Configuration Tool includes the possibility of defining the tasks on two different levels:

1. each program POU (= program organisation unit) can be tied to a separate task

2. a separate function block inside a POU can be tied to any task

However, the alternative 2) is not supported in the RED environment, which meansthat if a separate function block inside a POU is given a separate task definition, itwill be ignored when transferred to the device. This means that when the functionblocks are being placed in different POUs, not only the category of the function(protection, control, etc.) but also the maximum task execution interval should beconsidered, since all function blocks inside a POU will run at the same speed.

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 the figurebelow is defined as 10 ms, which means that the program Prot_Me is run 100 timesper one second. The maximum number of tasks with different intervals is 4.

Note that the task setting is automatically modified by the tool if the setnetwork frequency is other than 50 Hz (see Network Frequency inFigure 3.1.4.2.-4 on page 16 ). At 60 Hz, for example, 10 ms becomes8.333 ms.

)LJ 6HWWLQJ WKH WDVN H[HFXWLRQ LQWHUYDO IRU D SUR

If there is a need for several different tasks that control the same output relay, it isrecommended that the output relay is controlled directly in the fastest task and othercontrol commands are brought to that task via global variables.

E.g. 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 functionblocks use the same output relay.

Another way to avoid also the software delays when communicating between thedifferent tasks is to use a separate output relay for each protection task.

E.g. the trip signal from the 5 ms task is connected to High-Speed PowerOutput 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 circuitbreaker.

!


26/113

26 ABB Automation


'HFODULQJ YDULDEOHV

The range of validity of the declarations included in the declaration part shall belocal to the POU in which the declaration part is contained. One exception to thisrule are variables that have been declared to be global. Such variables are onlyaccessible to a POU via a VAR_EXTERNAL declaration. The type of a variabledeclared in a VAR_EXTERNAL block shall agree with the type declared in theVAR_GLOBAL block of the associated program, configuration or resource.

)LJ /RFDO DQG JOREDO YDULDEOHV

The figure above illustrates the ways how values of variables can be communicatedamong software elements. Variable values within a program can be communicateddirectly by connecting the output of one program element to the input of another orvia local variables such as the variable y illustrated in the upper left corner of thefigure above. In the same configuration, variable values can be communicatedbetween programs via global variables such as the variable x illustrated inConfiguration C in the figure above. In such a case, make sure that the globalvariable is only written from one location in the project. The global variable can stillbe read from several locations.

According to the IEC standard 61131-3, all variables that have no explicit initialiserare initialised with a data type dependent default value. Despite of this, it is alwaysrecommended that the initial value is given explicitly. Naturally, the value to whicheach variable should be initialised depends on the logical function of the program .

'DWD W\SH 'HIDXOW LQLWLDO YDOXH

ANY_REAL 0.0ANY_INT 0ANY_BIT 0 (=FALSE)TIME T#0s

VARy:BOOL;FB1:FB_X;FB2:FB_Y;

END_VAR

FB_XFB1

a y

FB_YFB2

by

Program B

VAR_EXTERNALx:BOOL;

END_VAR

VARFB1:FB_X;

END_VAR

FB_XFB1

a x

Program A

VAR_GLOBALx:BOOL;

END_VAR

Configuration C

VARFB1:FB_X;FB2:FB_Y;

END_VAR

FB_XFB1

a

FB_YFB2

b

Program A

VAR_EXTERNALx:BOOL;

END_VAR

VARFB2:FB_Y;

END_VAR

FB_YFB2

bx

Program B


27/113


ABB Automation 27

Especially the initial values of global variables are logically significant for theprogram. The user cannot choose the order in which tasks are initialised, whichmeans that if a task reading a global variable is initialised before another task givesthe variable its first value, it is important that an appropriate initial value has beenselected for the global variable.

&$6( 9DULDEOHV GHFODUDWLRQ

9$5,$%/( :25.6+((7 RI ORJLFDO 328

******************************************************************VAR

TRIPPING :BOOL )$/6( BLOCK :BOOL 758( TMP1 :BOOL )$/6(

END_VARVAR_EXTERNAL

PS1_4_HSPO1 :BOOL; (* Double pole high speed power output *)(* X4.1/10,11,12,13 *)



END_VARVAR_EXTERNAL

TCS1_ALARM :BOOL;END_VAR

******************************************************************

*/2%$/ 9$5,$%/( :25.6+((7

******************************************************************VAR_GLOBAL

PS1_4_HSPO1 AT %QX 1.1.2 :BOOL )$/6( (* Double pole high speed power output X4.1/10,11,12,13 *)



END_VAR

VAR_GLOBALTCS1_ALARM :BOOL )$/6(

END_VAR

******************************************************************


28/113

28 ABB Automation


*OREDO YDULDEOHV

The physical contacts of RE_ 54_ are defined in the Global Variables worksheet.Declarations for the physical contacts are automatically defined when the correcthardware version of RE_ 54_ is selected. Declarations for the analogue channels arecreated after the analogue channel settings defined in the resource settings dialoguehave been approved.

The textual names of the inputs and outputs, e.g. BIO2-7_BI10IV (see figurebelow), can be modified. Note, however, that the address (e.g. AT %IX 1.29.1:BOOL := TRUE) following the name may not be changed.

)LJ *OREDO 9DULDEOHV ZRUNVKHHW

/RFDO YDULDEOHV

At its beginning, each programmable controller POU type declaration is to containat least one declaration part that specifies the types of the variables used in theorganisation unit. The declaration part shall have the textual form of one of thekeywords VAR_INPUT, VAR_OUTPUT, VAR and VAR_EXTERNAL followedby one or more declarations separated by semicolons and terminated by the keywordEND_VAR. All the comments you write must be edited in parentheses and asterisks.

Caution is required regarding comments and variable declarations. The followingcode example will be compiled successfully but because of the non-closedcomment, the END_VAR - VAR_EXTERNAL couple will be excluded and thus thechannel numbers become local variables of the POU and they get the initial valuezero.

(*******************************)(* Variable declaration

of REF 541*)

(* *)(*******************************)


29/113


ABB Automation 29

Three examples of creating the textual declaration for different kinds of graphicalprograms are given below.

(;$03/(

POU type: FBD program

Function block type declaration:

)LJ )XQFWLRQ EORFN LPDJH

VARSIGNAL1 :BOOL :=FALSE;SIGNAL2 :BOOL :=FALSE;SIGNAL3 :BOOL :=FALSE;SIGNAL4 :BOOL :=FALSE;

END_VAR

VAR (*AUTOINSERT*)NOC3Low_1 : NOC3Low; (* Erroneous nonclosed comment *

END_VARVAR_EXTERNAL (*AUTOINSERT*)

U12 : SINT; (* Measuring channel 8 *)U23 : SINT; (* Measuring channel 9 *)U31 : SINT; (* Measuring channel 10 *)

END_VAR


30/113

30 ABB Automation


(;$03/(

POU type: NOC3Low, manufacturer dependent function block


)LJ )XQFWLRQ EORFN LPDJH RI 12& /RZ

VAR_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_VAR

VAR_OUTPUTSTART :BOOL :=FALSE; (* Start signal *)TRIP :BOOL :=FALSE; (* Trip signal *)CBFP :BOOL :=FALSE; (* CBFP signal *)ERR :BOOL :=FALSE; (* Error signal *)

END_VAR


31/113


ABB Automation 31

(;$03/(

POU type: Programmer dependent FBD function block CONDIS


)LJ 7\SH GHFODUDWLRQ RI WKH SURJUDPPHU PDGH IXQFWLRQ


32/113

32 ABB Automation


)LJ )%' ZRUNVKHHW FRQWHQWV RI WKH &21',6 IXQFWLRQ EORFN

)LJ 8VH RI WKH SURJUDPPHU PDGH IXQFWLRQ EORFN &21',6

In the example 3 above, part of the configuration has been separated to aprogrammer made function block called CONDIS. Such function blocks may not begiven names already belonging to library functions blocks or IEC standard functionblocks. The function block CONDIS has been used like any other function block inthe graphical program. The order of inputs of a function block that has been insertedto a worksheet may not be changed. It must also be remembered that a function block with an instance named by the programmer can only be inserted to the project once.


33/113


ABB Automation 33

&RPSLOLQJ WKH SURMHFW

The Build Project mode in the Make menu is used to compile the whole projectfor the first time after editing, which means compiling all POUs, global variables,resources etc., whereas the Make mode can be used to compile the worksheets thathave been edited. The changed worksheets are marked with an asterisk in the projecttree editor. Make is the standard mode for compiling and should normally be usedwhen you have finished editing. However, it is recommended that the BuildProject command is given once more right before downloading the configurationto the product.

In the Relay Configuration Tool you can view the execution order of the differentfunctions or function blocks in your worksheet. The execution order corresponds tothe intermediate PLC code created while compiling. Note that the execution ordercan only be seen if you have already compiled the worksheet using the menu itemCompile Worksheet in the submenu Make.

'RZQORDGLQJ WKH FRQILJXUDWLRQAfter the configuration has been built and succesfully compiled in the RelayConfiguration Tool, and the MIMIC configuration has been designed, the projectcan be downloaded to the device. The parts of the project to be downloaded areselected via a dialogue box. The MIMIC configuration and the Relay ConfigurationTool project can be downloaded separately. The project can also be downloadedseparately as a compressed file, which enables later uploading of the project fromthe device. The compressed file is automatically created if RCT project has beenselected (see Figure 3.4.-1 below). The target device has an inherent limitation overthe size of a stored project file. If this is exceeded, the tool will interrupt thedownloading and issue a warning. It is useful to include some information of the

project in the file (Relay Configuration Tool: File/Project Info) by giving e.g. thename of the designer, the date and the version or other description of theconfiguration.

)LJ 6HOHFWLQJ 5&7 SURMHFW 1RWH WKDW IRU 5(& RQO\&RQILJXUDWLRQ LV SRVVLEOH


34/113

34 ABB Automation


When the configuration is downloaded, the total CPU load in percent can be checkedvia the parameter Config. capacity (Main menu/Configuration/General/Config.capacity). If the load exceeds 100%, the downloading fails, an indication Failed isdisplayed in the assisting window of the display of REF 54_ or REM 54_ and amessage appears in the CAP 505. The exceeded CPU load can also be read via the

parameter after a failed downloading, i.e. the load value can be e.g. 115%.Whenever the downloading fails, no storing sequence is allowed to be started but thedevice must be reset before next downloading. Moreover, the device isautomatically reset after a failed downloading when the download dialogue in theRelay Download Tool is closed. Note that the exceeded CPU load must be checkedbefore resetting, since after the device is restarted, the parameter Config. capacityshows the load of the previous configuration that was downloaded succesfully andhas become valid again.


35/113


ABB Automation 35

0DLQ &RQILJXUDWLRQ 5XOHV IRU 5(B BB

*HQHUDO

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 connectedtogether. There are also many other FBD programming rules to follow. One of themost typical rules is not to use the wired-OR connection. All signals that areconnected to the same output signal (both output relays and horizontalcommunication outputs) must be connected via an OR gate (see figure below).

)LJ 8VH RI DQ H[SOLFLW %RROHDQ 25 JDWH RQ WKH ULJKW

I>

I>>

PS1_4_HSPO1

PS1_4_HSPO1

I>

I>>

TRIP

TRIP

PS1_4_HSPO1OR

"wired-OR" structure is not allowed an explicit Boolean "OR" block is required instead


36/113

36 ABB Automation


'LJLWDO LQSXWV DQG RXWSXWV

Digital inputs and outputs of RED500 devices are implemented as directlyrepresented global variables. As such, they are special cases and their use in theconfiguration is limited. Directly represented variables are declared in the GlobalVariables sheet of the project tree. They can be recognized by the AT keyword as inthe examples below.

Note that the parts of the line following the AT keyword may not be changed. Onlythe name of the signal, i.e. 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 isencouraged 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:

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 Figure 4.2.-1 below.Accordingly, an output can be written but not read. Note that an input can be readfrom several locations within a worksheet and even from any program organisationunit within the configuration, whereas an output can only be written from onelocation at a time.

)LJ :ULWLQJ RU UHDGLQJ D GLJLWDO LQSXW LV QRW DOORZHG

BIO1_5_BI1 6 U %IX 1.8.2 :BOOL := FALSE; ( *Binary input X5.1/1,2 *)BIO2_7_PO1 6 U %QX 1.13.2 :BOOL := FALSE; ( *Single pole output X7.1/17,18 *)

R ( f p y r f h f D I AT %IX 1.8.2 :BOOL := FALSE; (* Binary input X5.1/1,2 *)R ( f p y r f p q f P V U AT %QX 1.13.2 :BOOL := FALSE; (* Single pole output X7.1/17,18 *)


37/113


ABB Automation 37

([SOLFLW IHHGEDFN SDWK

A feedback path exists on the FBD worksheet when an output of a function block isused as an input to a function block that precedes it in the execution order. There aretwo types of feedback paths, an explicit and an implicit feedback loop (see Figures4.3.-1 and 4.3.-2 below). It is strongly recommended that explicit feedback loops arechanged to implicit loops by means of a feedback variable.

The Relay Configuration Tool can detect explicit loops during compilation. If themenu item Display warnings in the Make menu is checked, the compiler willgive warnings about the detected explicit feedback loops. To view the feedback loops, select Highlight feedback in the Layout menu. The execution order of functions compared to the expected behaviour may in some cases dictate where thefeedback variable should be added (for instructions on how to view the executionorder, refer to section Execution order on page 39 ). The initial value of thefeedback variable should also be selected with care.

)LJ ([SOLFLW IHHGEDFN ORRS LV GHWHFWHG DQG KLJKOLJKWHG

)LJ ,PSOLFLW IHHGEDFN YLD WKH ORFDO YDULDEOH )(('%$&.


38/113

38 ABB Automation


$QDORJXH LQSXWV

Analogue channels defined in the resource can be connected to the analogue inputsof application function blocks on a code body worksheet. Most of the functionblocks with several analogue inputs support unconnected inputs. For example, inFigure 4.4.-1 below, the function block NOC3Low operates on only two inputs. Thethird and unused input constantly measures a zero current amplitude. This functionblock only requires that at least one of the three inputs is connected. On the otherhand, certain function blocks require that all analogue inputs are connected. Anexample of such a function block is OV3Low (see Figure 4.4.-1 below). If theanalogue channel requirements of a function block are violated, a configurationerror is generated. For more information on how analogue inputs are expected to beconnected, refer to the function block manuals on the CD-ROM TechnicalDescriptions of Functions, see References on page 108 .

Analogue channels connected to application function blocks may not be changedruntime. Therefore, do not use any selectors between analogue channels andfunction blocks.

)LJ &RQQHFWLQJ DQDORJXH LQSXWV RI DSSOLFDWLRQ IXQFWLRQ EVHOHFWRU WR VZLWFK EHWZHHQ FKDQQHOV LV IRUELGGHQ

(UURU RXWSXWV RI DSSOLFDWLRQ IXQFWLRQ EORFNV

If a configuration for a function block is not correct, its ERR output is activatedimmediately after configuration downloading and the function block is forced to theNot in use mode. In this case, application function blocks that have the Operationmode parameter in their actual setting menu will display the Not in use operationmode, regardless of which mode has been selected for the parameter in the settinggroup menu.

The error signals of all application function blocks should be collected together viaan OR gate and connected to e.g. an MMI alarm indication of REF 54_ or REM 54_,i.e. an MMIALAR_ function block. This way, detecting any untreated configurationerrors is fast and easy.

Configuration errors typically originate from missing special measurements, thetype, order or number of analogue channels connected to function blocks, or task interval requirements.


39/113


40/113

40 ABB Automation


In addition, the execution order may be illogical or even incorrect considering thefunctionality.

)LJ 7KH LPSOLFLW IHHGEDFN 703 GHOD\V WKH XSGDWLQJ RI WK

,17(5/2&.,1* YDULDEOH E\ RQH WDVN H[HFXWLRQ F\FOH

) NH\

The freely programmable F-key of REF 54_ or REM 54_ is declared asVAR_GLOBAL in the global variable worksheet as follows:

The F-key parameter can be added to the configuration logic as an external variable(VAR_EXTERNAL).

)LJ ([DPSOH RI XVLQJ ) NH\ ZLWK WKH GLVWXUEDQFH UHFRUGHU I 0('5(&

F001V021:BOOL:=0; (* (R, W) Free configuration point (F-key) *)


41/113


ABB Automation 41

The variables below are internal variables of the system and are thus notrecommended 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 (insidemodule)

*) *)

F900V252:BOOL:=0; (* (W) Control: Cancel all command for selected objects (insidemodule)

*)

F000V251:BOOL:=0; (* (* (W) Control: Execute all command for selected objects (insidemodule)

*) *)

F000V252:BOOL:=0; (* (W) Control: Cancel all command for selected objects (insidemodule)

*)


42/113

42 ABB Automation


(QJLQHHULQJ 7LSV

+RUL]RQWDO FRPPXQLFDWLRQ

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-baycommunication, including correct state indication of control objects via LONcommunication. The logic also includes an alarm function in case of a broken fibreoptic. Incorrect updating of interlocking information blocks the control of objects,but the blocking can be bypassed by setting the device to the bypass mode.

*XLGHOLQH IRU 19 SROOLQJ DV 3/& ORJLF

Communication between terminals is executed by using the communication inputand output signals (global variables COMM_IN_ and COMM_OUT_). The logicmust be designed in a Relay Configuration Tool project. The LON network variablebindings 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 unacknowledgedrepeated unicast service. The signals are named so that the number at the end of COMM_OUT_ (e.g. COMM_OUT ) denotes the bay to which the signal is sent.Accordingly, the number at the end of COMM_IN_ denotes the bay from which thesignal is received. This way, COMM_OUT2 of bay 1 is bound to COMM_IN1 of bay 2.

&200B,1

COMM_IN_ signals are converted into Boolean logic mode by INT2BOOLfunction 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. Signalsfor bay interlocking are also received.

)LJ ([DPSOH RI WKH &200B,1 ORJLF


43/113


ABB Automation 43

&200B287

Communication signals sent from one bay to other bays include the reservation of control objects, updating of communication output signals and some indicationsneeded in other bays. Overall, digital signals are sent via LON and converted fromBoolean logic to unsigned integer (UINT, 16 bits) values.

)LJ ([DPSOH RI WKH &200B287 ORJLF

&\FOLF VHQGLQJ JHQHUDWLRQ

The logic below shows an example of how the cyclic sending of communicationoutput signals can be generated. The idea is to generate a boolean signal with a5-second pulse duration and a 50-percent duty cycle.

)LJ ([DPSOH RI JHQHUDWLQJ WKH F\FOLF VHQGLQJ RI FRPPXQLVLJQDOV


44/113

44 ABB Automation


&\FOLF FRPPXQLFDWLRQ FKHFN

Checking of horizontal communication is performed by timers, which activate analarm signal as a result of failed communication (Bay__Comm_Failed) 15 secondsafter 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 thuspreventing the activation of Q output signals. If the communication fails, all fourbays will be blocked.

)LJ &\FOLF FRPPXQLFDWLRQ FKHFN


45/113


ABB Automation 45

%ORFNLQJ

If horizontal communication has failed, the BLOCK2 signal is sent to everycontrollable function block to prevent the control of local objects. Furthermore, theMMI alarm indication 8 (for REF 54_ or REM 54_) will be activated.

The BLOCK1 signal is used to create a mutual exclusion effect between bays. Thesignal is activated by horizontal communication when a control object is selected inone of the other bays.

)LJ %ORFNLQJ WKH FRQWURO RI REMHFWV


46/113

46 ABB Automation


&RQWURO RI REMHFWV

The control of an object, e.g. a breaker, can be executed if the BLOCK input is notactive (TRUE). Accordingly, an object cannot be controlled during the reservationof other objects (in the same bay or in other bays) or the failing of horizontalcommunication. However, the blocking can be bypassed by setting the terminal tothe bypass mode (MAIN MENU/CONTROL/GENERAL/INTERLOCKINGBYPASS). The bypass mode (see also section Bypass mode below) overridesinterlockings provided the bypass signal is included in the logic.

)LJ 'HILQLQJ WKH E\SDVV PRGH IRU WKH FRQWURO REMHFW

%\SDVV PRGH

The bypass mode signal can be generated in the logic via the COLOCAT functionblock. After activation of the bypass mode, the BYPASS signal will be active andwill therefore prevent activation of the BLOCK input.

)LJ *HQHUDWLRQ RI WKH E\SDVV PRGH VLJQDO


47/113


ABB Automation 47

(YHQWV IURP WKH PHDVXUHPHQW IXQFWLRQ EORFNV

63$ SURWRFRO XVHG

Measurement values have to be polled because they are not sent with events. Hence,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 beallowed in event masks. In this case, the client is informed of the activation andresetting of each limit with the corresponding event code numbers.

/21 SURWRFRO XVHG

Each measured variable is individualised by an IEC address. Measurement valuesand the corresponding IEC addresses are sent to a client, e.g. to MicroSCADA, withboth delta supervision events and limit supervision events.

When the supervision of warning and alarm limits is active, the priority for limitevent sending is higher than that for delta event sending if both type of events aresent concurrently. Concurrent event sending appears, for example, when a measuredvalue changes considerably during a short period, e.g. when a circuit breaker isclosed or opened. This causes problems if limit supervision events have beenmasked off, since the client will not receive all measurement values even if majorchanges have taken place.

Thus, the limit supervision events are not recommended to be maskedoff if limit supervision is used.!


48/113

48 ABB Automation


$33(1',; $ 5HOD\ &RQILJXUDWLRQ 3URFHGXUH

1. Create a new project2. Create a tree structure

a) Librariesb) Logical POU framework (programs and function blocks)c) Physical Hardware

i) configurationii) resource

- hardware version- used analogue 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 contents3. Design logics4. Check variable declarations

a) Data types and initialisersb) Instances of functions and function blocksc) Variable categories

i) VAR - END_VARii) VAR_EXTERNAL - END_VARiii) VAR_INPUT - END_VARiv) VAR_OUTPUT - END_VARv) VAR_GLOBAL - END_VAR

5. Compile a project6. Download it to the device


49/113


ABB Automation 49

$33(1',; % 6SHFLILFDWLRQ IRU )HHGHU 7HUPLQDO&RQILJXUDWLRQ

*HQHUDO GDWD

This document serves as a technical specification of substation protection and isused for the configuration of REF 54_ feeder terminals.

Special requirements can be specified under Further information at the bottom of each page.

Project name: Date:

This specification suitable for bays: Substation name:

Feeder terminal type: Software revision

Order number:

REF54 __ __ __ __ __ __ __ __ __ (e.g. REF543FC127AAAA)

Handled by: Company:

Telephone number: Fax number:


50/113

50 ABB Automation


(OHFWURWHFKQLFDO GDWD

$QDORJXH LQSXWV

&KDQQHO 0HDVXULQJ GHYLFHV WKDW FDQ EH FRQQHFWHG WR WKH FRUUHVSRQGLQJ DQDPHDVXULQJ FKDQQHOV

1 Rogowski sensor, voltage divider or general measurement2...5 Current transformer, Rogowski sensor, voltage divider or general measurement6 Current transformer7...10 Voltage transfomer, Rogowski sensor, voltage divider or general measurement

Further information:


51/113


ABB Automation 51

The measuring device can be connected exclusively to the analoguechannels of either MIM or SIM type modules. Ten channels areavailable.


1A5A

1A0,2A

100V

100V

100V

100V

1A5A

1A

5A

1A5A

X1.1

161514131211

87

654321

109

1918

2221

27

2524

M I M X 1

. 1 . f

h 8

Board Terminal number Connectedobject

Signal typeModule type

MIM

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

CT1Ch 2

Ch 3

Ch 4

Ch 5

Ch 6

Ch 7

Ch 8

Ch 9

Ch 10

X2.1

X2.2

X2.3

X2.4

X2.5

X2.6

X2.7

DIFF

DIFF

DIFF

DIFF

DIFF

DIFF

DIFF

X2.9DIFF S

I M X 2

. f h 8

X2.8DIFF

Terminalnumber

Board

SIM

Module type Connectedobject

Signal type

Ch 9, sensor

Ch 10, sensor

Ch 8, sensor

Ch 7, sensor

Ch 4, sensor

Ch 3, sensor

Ch 2, sensor

Ch 1, sensor

Ch 5, sensor

X2.1

X2.2

X2.3

X2.4

X2.5

X2.6

X2.7

X2.8

X2.9

!


52/113

52 ABB Automation


6\VWHP IUHTXHQF\

'LJLWDO LQSXWV

50 Hz 60 Hz


12

45

67

X4.2

P S 1 X 4

. 2 . f

h 8

Terminalnumber

Board Connectedobject

X4.2:1, X4.2:2

X4.2:4, X4.2:5

X4.2:6, X4.2:7

PS1(REF541,REF543)

Module type

1) Digital input / counter input

1)

1)

1)

PS1_4_BI1

PS1_4_BI3

PS1_4_BI2

123

456

789

101112

131415161718

X5.1

B I O 1 X 5

. 1 . f

h 8

X5.1:1, X5.1:2

X5.1:2, X5.1:3

X5.1:4, X5.1:5

X5.1:5, X5.1:6

X5.1:7, X5.1:8

X5.1:8, X5.1:9

X5.1:10, X5.1:11

X5.1:11, X5.1:12

X5.1:13, X5.1:14

X5.1:15, X5.1:16

X5.1:17, X5.1:18


BIO1

Terminalnumber


Module type

1)

1)

1)

BIO1_5_BI1

BIO1_5_BI11

BIO1_5_BI9

BIO1_5_BI8

BIO1_5_BI7

BIO1_5_BI6

BIO1_5_BI5

BIO1_5_BI4

BIO1_5_BI3

BIO1_5_BI2

BIO1_5_BI10


53/113


ABB Automation 53


12

X5.2

B I O 1 X 5

. 2 . f

h 8

BIO1

Terminalnumber


Module type

BIO1_5_BI12 X5.2:1, X5.2:2


1)

X7.1

101112

1314

1516

456

789

123

B I O 2 X 7

. 1 . f

h 8

BIO2(REF543,REF545)

Terminalnumber


Module type


1)

1)

BIO2_7_BI9

BIO2_7_BI8

BIO2_7_BI7

BIO2_7_BI6

BIO2_7_BI5

BIO2_7_BI4

BIO2_7_BI3

BIO2_7_BI2

BIO2_7_BI10

BIO2_7_BI1 X7.1:1, X7.1:2

X7.1:2, X7.1:3

X7.1:4, X7.1:5

X7.1:5, X7.1:6

X7.1:7, X7.1:8

X7.1:8, X7.1:9

X7.1:10, X7.1:11

X7.1:11, X7.1:12

X7.1:13, X7.1:14

X7.1:15, X7.1:16


54/113

54 ABB Automation


'LJLWDO RXWSXWV


PS1(REF541,REF543)

Terminalnumber

BoardConnectedobject

Module type

P S 1 X 4

. 1 . f

h 8

I R F

TCS2

TCS1

X4.1

5

6

798

10

111312

15

161817

34

-

X4.1

1

2

1)

1)

1)

1)

1) Please indicate whether the trip circuit supervision inputs will be configured to use or not

X4.1:1, X4.1:2

PS1_4_HSPO3

PS1_4_HSPO1

PS1_4_TCS1

PS1_4_HSPO2

PS1_4_TCS2

PS1_4_TempAlarm

PS1_4_ACFail

X4.1:3, X4.1:4, X4.1:5

X4.1:6, X4.1:7,X4.1:8, X4.1:9

X4.1:10, X4.1:11,X4.1:12, X4.1:13

X4.1:15, X4.1:16,X4.1:17, X4.1:18

+

Mains

PS2(REF545)

Terminalnumber


Module type

P S 2 X 4

. 1 . f

h 8

I R F

TCS2

TCS1

X4.1

5

6

798

10

111312

15

161817

3

4

-

X4.1

1

2

1)

1)

1)

1)


X4.1:1, X4.1:2

PS2_4_HSPO3

PS2_4_HSPO1

PS2_4_TCS1

PS2_4_HSPO2

PS2_4_TCS2

PS2_4_TempAlarm

PS2_4_ACFail

X4.1:3, X4.1:4, X4.1:5

X4.1:6, X4.1:7,X4.1:8, X4.1:9

X4.1:10, X4.1:11,X4.1:12, X4.1:13

X4.1:15, X4.1:16,X4.1:17, X4.1:18

+Mains


55/113


ABB Automation 55


PS1(REF541,REF543)

Terminalnumber


Module type

111012

1315141617

18

8

9

X4.2

P S 1 X 4

. 2 o

. f h 8

PS1_4_HSPO5

PS1_4_SO1

PS1_4_HSPO4X4.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, X4.2:17,X4.2:18

X4.2

2435

6879

10121113

141615

1718 P

S 2 X 4

. 2 o

. f h 8

PS2(REF545)

Terminalnumber


Module type

1

PS2_4_HSPO4

PS2_4_HSPO5

PS2_4_HSPO6

PS2_4_HSPO7

PS2_4_HSPO8

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

X4.2:17, X4.2:18


56/113

56 ABB Automation



5

6

79

8

1012

11

1315

141618

17

X5.23

4

B I O 1 X 5

. 2 o

. f h 8

BIO1

Terminalnumber


Module type

BIO1_5_SO1

BIO1_5_SO2

BIO1_5_SO3

BIO1_5_SO4

BIO1_5_SO5

BIO1_5_SO6

X5.2:3, X5.2:4

X5.2:5, X5.2:6

X5.2:7, X5.2:8, X5.2:9

X5.2:10, X5.2:11, X5.2:12

X5.2:13, X5.2:14, X5.2:15

X5.2:16, X5.2:17, X5.2:18

5

6

79

81012

11

1315

141618

17

X6.23

4

B I O 1 X 6

. 2 . f

h 8

BIO1(REF545)

Terminalnumber


Module type

BIO1_6_SO1

BIO1_6_SO2

BIO1_6_SO3

BIO1_6_SO4

BIO1_6_SO5

BIO1_6_SO6

X6.2:3, X6.2:4

X6.2:5, X6.2:6

X6.2:7, X6.2:8, X6.2:9

X6.2:10, X6.2:11, X6.2:12

X6.2:13, X6.2:14, X6.2:15

X6.2:16, X6.2:17, X6.2:18


57/113


ABB Automation 57


1718

X7.1

B I O 2 X 7

. 1 o

. f h 8

BIO2(REF543,REF545)

Terminalnumber


Module type

BIO2_7_PO1X7.1:17, X7.1:18

X7.2

65

7

8

141315

16

11

12

12

3

4

1817 B I

O 2 X 7

. 2 . f

h 8

BIO2(REF543,REF545)

Terminalnumber


Module type

109

BIO2_7_PO2

BIO2_7_PO3

BIO2_7_PO4

BIO2_7_PO5

BIO2_7_PO6

X7.2:1, X7.2:2

X7.2:3, X7.2:4,X7.2:5, X7.2:6

X7.2:7, X7.2:8,X7.2:9, X7.2:10

X7.2:11, X7.2:12,X7.2:13, X7.2:14

X7.2:15, X7.2:16,X7.2:17, X7.2:18


58/113


59/113


ABB Automation 59

57' RXWSXWV


X6.2

1112

1314

1516

1718

mA+-

mA

+-

mA

+-

mA

+-

R T D 1 X 6

. 2 . f

h 8

RTD1(REF541,REF543)

Terminal number BoardModule type Connected object

RTD1_6_AO1

RTD1_6_AO2

RTD1_6_AO3

RTD1_6_AO4

X6.2:11, X6.2:12

X6.2:13, X6.2:14

X6.2:15, X6.2:16

X6.2:17, X6.2:18


60/113

60 ABB Automation


)XQFWLRQDOLW\

2UGHU QXPEHU

REF54 __ __ __ __ __ __ __ __ __ __(e.g. REF543FC127AAAA)

$SSOLFDWLRQ IXQFWLRQ EORFNV XVHG

The lists below represent the full set of function blocks, but the selectedfunctionality level (indicated by a letter in the order number, e.g.REF543F &127AAAA) determines the function blocks available for theconfiguration. Note that optional functions, i.e. those selectable inaddition to the functions included in a functionality level, are listedseparately.

3URWHFWLRQAR5Func Freq1St1 NEF1Inst ROV1HighCUB3Low Freq1St2 NOC3Low ROV1InstDEF2Low Freq1St3 NOC3High SCVCSt1DEF2High Freq1St4 NOC3Inst SCVCSt2DEF2Inst Freq1St5 OV3Low TOL3CabDOC6Low Inrush3 OV3High TOL3DevDOC6High MotStart PSV3St1 UV3LowDOC6Inst NEF1Low PSV3St2 UV3High

NEF1High ROV1Low

0HDVXUHPHQW

MEAI1 MEAI7 MECU1A MEPE7MEAI2 MEAI8 MECU1B MEVO1AMEAI3 MEAO1 MECU3A MEVO1BMEAI4 MEAO2 MECU3B MEVO3AMEAI5 MEAO3 MEDREC16 MEVO3BMEAI6 MEAO4 MEFR1

&RQWURO

COCB1 COIND1 COSW1 MMIALAR6COCB2 COIND2 COSW2 MMIALAR7COCBDIR COIND3 COSW3 MMIALAR8CO3DC1 COIND4 COSW4 MMIDATA1CO3DC2 COIND5 MMIALAR1 MMIDATA2CODC1 COIND6 MMIALAR2 MMIDATA3CODC2 COIND7 MMIALAR3 MMIDATA4CODC3 COIND8 MMIALAR4 MMIDATA5CODC4 COLOCAT MMIALAR5CODC5

!


61/113


62/113

62 ABB Automation


5HOD\ 0,0,& FRQILJXUDWLRQ

,OOXVWUDWLRQ RI WKH V\VWHP 0,0,& GLDJUDP

6\PERO XVHG FORVHG RSHQ XQGHI XQGHI

Disconnector:(truck symbols)

Circuit breaker:

Earth switch:



63/113


ABB Automation 63

$ODUP /('V

Please fill in the table below to describe the legend text used as well as the flashingsequence and colour of the LEDs.

/(' 2)) VWDWH 21 VWDWHU r

h % p u h h p r

8 y A y h u v t

r

U r

h % p u h h p r

8 y A y h u v t

r

o f f

g r e e n

y e

l l o w

r e d

l a t c h e

d ,

b l i n k i n g

l a t c h e

d ,

s t e a

d y

n o n - l a

t c h e

d ,

b l i n k i n g

o f f

g r e e n

y e

l l o w

r e d

l a t c h e

d ,

b l i n k i n g

l a t c h e

d ,

s t e a

d y

n o n - l a

t c h e

d ,

b l i n k i n g

1 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

2 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

3 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

4 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

5 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

6 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

7 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

8

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Interlocking

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ X XControl test mode

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ X X



64/113

64 ABB Automation


)XQFWLRQDOLW\ ORJLF

Please specify the required special PLC logic functionality (see the examplesbelow), by drawing or otherwise, on separate sheets and enclose all additionalinformation with this document (Specification for Feeder Terminal Configuration).

([DPSOH (DUWKLQJ VHTXHQFHEarthing of the outgoing feeder can be done by a circuit breaker when an earthingsequence 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. Thefigure below shows the implementation of the desired logic.

([DPSOH 8VDJH RI WKH ) NH\ DQG D VRIWZDUH VZLWFK


65/113


ABB Automation 65

([DPSOH 9ROWDJH PHDVXUHPHQW LQ WKH 0,0,& YLHZ

Phase-to-phase voltage must be shown in voltages [V] in the MIMIC view.

)HHGHU WHUPLQDO VHWWLQJV

Responsibility:

The setting of the parameters is not part of the configuration. The enduser will normally be responsible for the setting parameters.

The end user defines the feeder terminal settingsFeeder terminal settings according to the turn-key principle


!


66/113

66 ABB Automation



67/113


ABB Automation 67

$33(1',; & 6SHFLILFDWLRQ IRU 0DFKLQH7HUPLQDO &RQILJXUDWLRQ

*HQHUDO GDWD

This document serves as a technical specification of substation protection and isused for the configuration of REM 54_ machine terminals.

Special requirements can be specified under Further information at the bottom of each page.

Project name: Date:

This specification suitable for bays: Substation name:

Machine terminal type: Software revision

Order number:

REM54 __ __ __ __ __ __ __ __ __ __ (e.g. REM543BM212AAAA)

Handled by: Company:

Telephone number: Fax number:


68/113

68 ABB Automation


(OHFWURWHFKQLFDO GDWD

$QDORJXH LQSXWV

&KDQQHO 0HDVXULQJ GHYLFHV WKDW FDQ EH FRQQHFWHG WR WKH FRUUHVSRQGLQJ DQDPHDVXULQJ FKDQQHOV

1 Rogowski sensor, voltage divider or general measurement2...5 Current transformer, Rogowski sensor, voltage divider or general measurement6 Current transformer7...10 Voltage transfomer, Rogowski sensor, voltage divider or general measurement



69/113


ABB Automation 69


MIM1MRS090212-

AA_/CA_

Terminal number Board Connectedobject

Module type Signal type

1A5A

100V

100V

100V

100V

1A5A

1A5A

1A5A

X1.1

R e m M i m 1

2725

24

2221

19

18

16151413121110987654321

0.2A1A Ch 6

Ch 7

Ch 8

Ch 9

Ch 10

Ch 2

Ch 3

Ch 4

Ch 5

CT5

VT1

VT2

VT3

VT4

CT1

CT2

CT3

CT4

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

MIM1MRS090214-

AA_/CA_



1A5A

1A5A

100V

1A5A

100V

100V

1A5A

1A5A

1A5A

X1.1

R e m M i m 2

2725

24

2221

1918

16

15

13

1210987654321

23

20

17

Ch 6

Ch 7

Ch 8

Ch 9

Ch 10

Ch 2

Ch 3

Ch 4

Ch 5

VT2

CT4

CT5

CT6

VT3

CT1

CT2

CT3

VT1

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

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


70/113

70 ABB Automation



MIM1MRS090216-

AA_/CA_



1A5A

1A5A

100V

1A5A

1A5A

100V

1A5A

1A5A

1A5A

X1.1

R e m M i m 3

2725

24

2221

1918

16

15

13

12

10987654321

23

20

17

11

Ch 6

Ch 7

Ch 8

Ch 9

Ch 10

Ch 2

Ch 3

Ch 4

Ch 5

VT1

CT5

CT6

CT7

VT2

CT1

CT2

CT3

CT4

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

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

MIM1MRS090218-

AA_/CA_



1A5A

1A5A

1A5A

1A5A

1A5A

100V

1A5A

1A5A

1A5A

X1.1

R e m M i m 4

2725

24

2221

1918

16

15

1312

10987654321

23

20

17

11

14 Ch 6

Ch 7

Ch 8

Ch 9

Ch 10

Ch 2

Ch 3

Ch 4

Ch 5

CT5

CT6

CT7

CT8

VT1

CT1

CT2

CT3

CT4

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

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


71/113


ABB Automation 71

The measuring device can be connected exclusively to the analogue

channels of either MIM or SIM type modules. Ten channels areavailable.

6\VWHP IUHTXHQF\


X2.1

X2.2

X2.3

X2.4

X2.5

X2.6

X2.7

DIFF

DIFF

DIFF

DIFF

DIFF

DIFF

DIFF

X2.9DIFF S

I M X 2

. f h 8

X2.8DIFF

Terminalnumber

Board

SIM

Module type Connectedobject

Signal type

Ch 9, sensor

Ch 10, sensor

Ch 8, sensor

Ch 7, sensor

Ch 4, sensor

Ch 3, sensor

Ch 2, sensor

Ch 1, sensor

Ch 5, sensor

X2.1

X2.2

X2.3

X2.4

X2.5

X2.6

X2.7

X2.8

X2.9

!

50 Hz 60 Hz


72/113

72 ABB Automation


'LJLWDO LQSXWV


12

45

67

X4.2

P S 1 X 4

. 2 b

. f h 8

Terminalnumber


X4.2:1, X4.2:2

X4.2:4, X4.2:5

X4.2:6, X4.2:7

PS1

Module type


1)

1)

1)

PS1_4_BI1

PS1_4_BI3

PS1_4_BI2

123

456

789

101112

1314151617

18

X5.1

B I O 1 X 5

. 1 . f

h 8

X5.1:1, X5.1:2

X5.1:2, X5.1:3

X5.1:4, X5.1:5

X5.1:5, X5.1:6

X5.1:7, X5.1:8

X5.1:8, X5.1:9

X5.1:10, X5.1:11

X5.1:11, X5.1:12

X5.1:13, X5.1:14

X5.1:15, X5.1:16

X5.1:17, X5.1:18


BIO1

Terminalnumber


Module type

1)

1)

1)

BIO1_5_BI1

BIO1_5_BI11

BIO1_5_BI9

BIO1_5_BI8

BIO1_5_BI7

BIO1_5_BI6

BIO1_5_BI5

BIO1_5_BI4

BIO1_5_BI3

BIO1_5_BI2

BIO1_5_BI10


73/113


74/113

74 ABB Automation


'LJLWDO RXWSXWV


PS1

Terminalnumber


Module type

P S 1 X 4

. 1 b

. f h 8

I R F

TCS2

TCS1

X4.1

5

6

798

10

111312

15

161817

34

-

X4.1

1

2

1)

1)

1)

1)


X4.1:1, X4.1:2

PS1_4_HSPO3

PS1_4_HSPO1

PS1_4_TCS1

PS1_4_HSPO2

PS1_4_TCS2

PS1_4_TempAlarm

PS1_4_ACFail

X4.1:3, X4.1:4, X4.1:5

X4.1:6, X4.1:7,X4.1:8, X4.1:9

X4.1:10, X4.1:11,X4.1:12, X4.1:13

X4.1:15, X4.1:16,X4.1:17, X4.1:18

+

Mains

PS1

Terminalnumber


Module type

111012

1315141617

18

8

9

X4.2

P S 1 X 4

. 2 o

_ b

. f h 8

PS1_4_HSPO5

PS1_4_SO1

PS1_4_HSPO4X4.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, X4.2:17,X4.2:18


75/113


ABB Automation 75


5

6

79

8

1012

11

1315

141618

17

X5.23

4

B I O 1 X 5

. 2 o

. f h 8

BIO1

Terminalnumber


Module type

BIO1_5_SO1

BIO1_5_SO2

BIO1_5_SO3

BIO1_5_SO4

BIO1_5_SO5

BIO1_5_SO6

X5.2:3, X5.2:4

X5.2:5, X5.2:6

X5.2:7, X5.2:8, X5.2:9

X5.2:10, X5.2:11, X5.2:12

X5.2:13, X5.2:14, X5.2:15

X5.2:16, X5.2:17, X5.2:18

1718

X7.1

B I O 2 X 7

. 1 o

_ b

. f h 8

BIO2(REM545)

Terminalnumber


Module type

BIO2_7_PO1X7.1:17, X7.1:18


76/113

76 ABB Automation



X7.2

65

7

8

141315

16

11

12

12

3

4

1817 B I

O 2 X 7

. 2 b

. f h 8

BIO2(REM545)

Terminalnumber


Module type

109

BIO2_7_PO2

BIO2_7_PO3

BIO2_7_PO4

BIO2_7_PO5

BIO2_7_PO6

X7.2:1, X7.2:2

X7.2:3, X7.2:4,X7.2:5, X7.2:6

X7.2:7, X7.2:8,X7.2:9, X7.2:10

X7.2:11, X7.2:12,X7.2:13, X7.2:14

X7.2:15, X7.2:16,X7.2:17, X7.2:18


77/113


ABB Automation 77

57' DQDORJXH PRGXOH

57' DQDORJXH LQSXWV


RTD1_6_AI1

RTD1_6_AI2

RTD1_6_AI3

RTD1_6_AI4

RTD1_6_AI5

RTD1_6_AI6

RTD1_6_AI7

RTD1_6_AI8

RTD1

Terminalnumber

Board Connected objectModule type

DIFF

DIFF

DIFF

DIFF

DIFF

X6.2

4567

123

89

10

DIFF

DIFF

DIFF

X6.1

567

1234

121314

89

1011

15161718

+

-

+

-

+

-

+

-

SHUNT

SHUNT

SHUNT

SHUNT

SHUNT

SHUNT

SHUNT

SHUNT

-

+

-

+

-

+

-+

R T D 1 X 6

._ b

. f h 8

X6.1:1, X6.1:2, X6.1:3

X6.1:5, X6.1:6, X6.1:7

X6.1:8, X6.1:9, X6.1:10

X6.1:12, X6.1:13, X6.1:14

X6.1:15, X6.1:16, X6.1:17

X6.2:1, X6.2:2, X6.2:3

X6.2:4, X6.2:5, X6.2:6

X6.2:7, X6.2:8, X6.2:9

1) Current transducer / voltage transducer / resistance sensor

1)


78/113


79/113


ABB Automation 79

)XQFWLRQDOLW\

2UGHU QXPEHU

REM54 __ __ __ __ __ __ __ __ __ __(e.g. REM543BM212AAAA)

$SSOLFDWLRQ IXQFWLRQ EORFNV XVHG

The lists below represent the full set of function blocks, but the selectedfunctionality level (indicated by a letter in the order number, e.g.REM543B 0 212AAAA) determines the function blocks available for theconfiguration.

3URWHFWLRQ

DEF2Low NEF1Low OPOW6St2 UE6High

DEF2High NEF1High OPOW6St3 UI6LowDEF2Inst NEF1Inst OV3Low UI6HighDiff3 NOC3Low OV3High UPOW6St1Diff6G NOC3High PREV3 UPOW6St2Freq1St1 NOC3Inst PSV3St1 UPOW6St3Freq1St2 NPS3Low PSV3St2 UV3LowFreq1St3 NPS3High REF1A UV3HighFreq1St4 NUC3St1 ROV1Low VOC6LowFreq1St5 NUC3St2 ROV1High VOC6HighFuseFail OE1Low ROV1InstInrush3 OE1High TOL3DevMotStart OPOW6St1 UE6Low

0HDVXUHPHQW

MEAI1 MEAI6 MEAO3 MEDREC16MEAI2 MEAI7 MEAO4 MEFR1MEAI3 MEAI8 MECU1A MEPE7MEAI4 MEAO1 MECU1B MEVO1AMEAI5 MEAO2 MECU3A MEVO3A

&RQWURO

COCB1 CODC5 COLOCAT MMIALAR5COCB2 COIND1 COSW1 MMIALAR6COCBDIR COIND2 COSW2 MMIALAR7CO3DC1 COIND3 COSW3 MMIALAR8CO3DC2 COIND4 COSW4 MMIDATA1CODC1 COIND5 MMIALAR1 MMIDATA2CODC2 COIND6 MMIALAR2 MMIDATA3CODC3 COIND7 MMIALAR3 MMIDATA4CODC4 COIND8 MMIALAR4 MMIDATA5

!


80/113

80 ABB Automation


&RPPXQLFDWLRQ

&RQGLWLRQ PRQLWRULQJ

CMBWEAR1 CMTCS1CMBWEAR2 CMTCS2

CMCU3 CMTIME1CMGAS1 CMTIME2CMGAS3 CMTRAV1CMSCHED CMVO3CMSPRC1

&RPPXQLFDWLRQ

EVENT230

*HQHUDO

INDRESET SWGRP5 SWGRP11 SWGRP17MMIWAKE SWGRP6 SWGRP12 SWGRP18SWGRP1 SWGRP7 SWGRP13 SWGRP19SWGRP2 SWGRP8 SWGRP14 SWGRP20SWGRP3 SWGRP9 SWGRP15SWGRP4 SWGRP10 SWGRP16

Protocol used: LON SPABUS


81/113


ABB Automation 81

5HOD\ 0,0,& FRQILJXUDWLRQ

,OOXVWUDWLRQ RI WKH V\VWHP 0,0,& GLDJUDP

6\PERO XVHG FORVHG RSHQ XQGHI XQGHI

Disconnector:(truck symbols)

Circuit breaker:

Earth switch:



82/113

82 ABB Automation


$ODUP /('V

Please fill in the table below to describe the legend text used as well as the flashingsequence and colour of the LEDs.

/(' 2)) VWDWH 21 VWDWHU r

h % p u h h p r

8 y A y h u v t

r

U r

h % p u h h p r

8 y A y h u v t

r

o f f

g r e e n

y e

l l o w

r e d

l a t c h e

d ,

b l i n k i n g

l a t c h e

d ,

s t e a

d y

n o n - l a

t c h e

d ,

b l i n k i n g

o f f

g r e e n

y e

l l o w

r e d

l a t c h e

d ,

b l i n k i n g

l a t c h e

d ,

s t e a

d y

n o n - l a

t c h e

d ,

b l i n k i n g

1 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

2 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

3 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

4 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

5 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

6 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

7 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

8

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Interlocking

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ X XControl test mode

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ X X



83/113


ABB Automation 83

)XQFWLRQDOLW\ ORJLF

Please specify the required special PLC logic functionality (see the examplesbelow), by drawing or otherwise, on separate sheets and enclose all additionalinformation with this document (Specification for Machine TerminalConfiguration).

([DPSOH (DUWKLQJ VHTXHQFH

Earthing of the outgoing feeder can be done by a circuit breaker when an earthingsequence 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. Thefigure below shows the implementation of the desired logic.

([DPSOH 8VDJH RI WKH ) NH\ DQG D VRIWZDUH VZLWFK


84/113

84 ABB Automation


([DPSOH 9ROWDJH PHDVXUHPHQW LQ WKH 0,0,& YLHZ

Phase-to-phase voltage must be shown in voltages [V] in the MIMIC view.

0DFKLQH WHUPLQDO VHWWLQJV

Responsibility:

The setting of the parameters is not part of the configuration. The enduser will normally be responsible for the setting parameters.

The end user defines the machine terminal settingsMachine terminal settings according to the turn-key principle


!


85/113


ABB Automation 85

$33(1',; ' 6SHFLILFDWLRQ IRU 5HPRWH0RQLWRULQJ DQG &R

re 54 confenc

Documents