1mrb520292-uen-reb500sys_chap 7 _8

REB500/REB500sys 1MRB520292-Uen/Rev. C ABB Switzerland Ltd

January 05

7. COMMISSIONING

7.1. Safety instructions ................................................................... 7-3 7.1.1. Assumptions and preconditions ............................................... 7-3 7.1.2. Regulations.............................................................................. 7-3

7.2. General remarks on commissioning the REB500 protection system ..................................................................................... 7-5

7.3. Commissioning procedure ....................................................... 7-6

7.4. Checks prior to switching on .................................................... 7-7 7.4.1. Record the equipment data...................................................... 7-7 7.4.2. Visually inspect for transport damage...................................... 7-7 7.4.3. Visually inspect the external wiring and cables........................ 7-7 7.4.4. Check the grounding of cubicles and other units ..................... 7-7 7.4.5. Check the auxiliary DC battery supply ..................................... 7-8 7.4.6. Check the settings ................................................................... 7-9 7.4.7. Check the CT circuits............................................................... 7-9 7.4.8. Check the VT circuits ............................................................. 7-12

7.5. Commissioning the protection system ................................... 7-13 7.5.1. Communicating with the protection system............................ 7-13 7.5.2. Simulation of isolator and circuit-breaker status signals ........ 7-14 7.5.3. Comparison of diagrams........................................................ 7-14 7.5.4. Comparison with the layout of the primary system ................ 7-15 7.5.5. Checking the analog inputs (CTs).......................................... 7-16 7.5.6. Checking the analog inputs (VTs).......................................... 7-16 7.5.7. Checking the binary inputs signals (opto-coupler inputs)....... 7-17 7.5.8. Check auxiliary contacts on the isolators and

circuit-breakers and the “CLOSE” command ......................... 7-17 7.5.8.1. Wiring the auxiliary contacts .................................................. 7-17 7.5.8.2. Timing sequence ...................................................................7-18 7.5.8.3. Special version “Not CLOSED = OPEN”................................ 7-20 7.5.8.4. Checking the isolator and circuit-breaker auxiliary contacts .. 7-21 7.5.8.5. Checking the manual “CLOSE” command............................. 7-21 7.5.9. Checking the binary output signals (tripping circuits

and alarms)............................................................................ 7-22 7.5.10. Checking the starting of the breaker failure protection........... 7-24 7.5.11. Checking protection stability .................................................. 7-24 7.5.11.1. Checking through-fault stability with de-energized busbars ... 7-25 7.5.11.2. Checking through-fault stability with load current................... 7-27

7-1

ABB Switzerland Ltd REB500/REB500sys 1MRB520292-Uen/Rev. C

7.5.12. Setting the system time.......................................................... 7-28 7.5.13. Viewing traceability data ........................................................ 7-28 7.5.14. Final test and inspection ........................................................ 7-28

7.6. Configuring REB500 to match the layout of the primary plant7-30 7.6.1. Introduction ............................................................................ 7-30 7.6.2. Procedure .............................................................................. 7-31 7.6.3. Adding a bay to an existing station ........................................ 7-32 7.6.3.1. Activating provisionally configured bays ................................ 7-32 7.6.3.2. Activating central unit modules .............................................. 7-33 7.6.4. Removing a bay from operation............................................. 7-34 7.6.4.1. Deactivating bays .................................................................. 7-34 7.6.4.2. Deactivating central unit modules .......................................... 7-35 7.6.5. Special cases when adding or decommissioning plant .......... 7-35 7.6.5.1. Deactivating (items of plant shorted)...................................... 7-35 7.6.5.2. Activating and deactivating individual items of plant .............. 7-36

7.7. Additional checks for REB500sys .......................................... 7-37 7.7.1. Commissioning a new station without any HV ....................... 7-37 7.7.2. Additions to an existing station .............................................. 7-37

7-2


7. COMMISSIONING

7.1. Safety instructions

7.1.1. Assumptions and preconditions

It is assumed that the REB500 protection system is already installed and all the input and output signals that have been configured are also wired and the optical fiber cables run and tested.

It must also be assumed that the busbars or sections of them are in operation and that circuit-breakers and isolators are in the process of being installed or maintained.

The commissioning engineer requires the operating instructions and the station diagrams prepared by the engineering depart-ment.

The protection system may only be commissioned by corre-spondingly trained commissioning personnel.

7.1.2. Regulations

DANGER: Note that when commissioning REB500sys, the analog input signals act on the bay protection (BP functions) as well as the busbar protection and the REB500 functions (EFP, BFP etc.). Especially when the commissioning subsequently (e.g. following additions to the system), care must be taken to prevent part of the system which are already in operation from mal-operating. Corresponding precautions must be taken (interrupting tripping circuits, blocking system functions, disabling auxiliary tripping relays).

DANGER: The greatest care must be taken when testing a bus-bar protection system on busbars in operation, as the consequences of tripping a circuit-breaker by mistake when there is no fault, or not tripping it when there is a fault can be extremely serious.

7-3


DANGER: Before testing the operation of circuit-breakers or isolators, check that no maintenance is being carried out on the circuit-breakers or the busbars. Even with the power switched off, switching operations with people in the vicinity can cause accidents and injury.

WARNING: Unnecessary switching operations should be avoided as far as possible, because switchgear has a limited number of operations and switching disturbs the normal operation of the station.

7-4


7.2. General remarks on commissioning the REB500 protection system

The REB500 protection system operates digitally and is equipped with a continuous self-supervision and diagnostics function (see Section 3.6. "Self-supervision"). All the functions are (protection) algorithms computed by the system software.

ABB exhaustively tests the system software before it is released.

The customer’s specific data are also recorded in software form in a database, which is similarly tested by the ABB test depart-ment before being released.

The self-supervision function is so extensive that only few hard-ware components are not covered. These include the binary inputs (opto-couplers) and outputs and the analog channels (CT and VT inputs).

For these reasons, it is superfluous to test the internal func-tions of the protection by secondary injection. Secondary injec-tion is therefore restricted to those components which are not covered by the self-supervision function, i.e.:

• binary inputs and outputs and

• analog channels

7-5


7.3. Commissioning procedure

The following procedure has proved the best in practice:

Checks prior to switching on

1 Record the equipment data

2 Visually inspect for transport damage

3 Visually inspect the external wiring and cables

4 Check the grounding of cubicles and other units

5 Check the auxiliary DC battery supply

6 Check the settings

7 Check the CT circuits

8 Check the VT circuits

Checks after switching on the protection system

9 Secondary injection tests using the test set

10 Check the binary input signals

11 Check auxiliary contacts on the isolators and circuit-breakers and the “CLOSE” command

12 Check the control signal and alarm circuits

13 Check the tripping circuits

14 Check the stability factor

15 Set the system time

16 Record traceability data

17 Final test and inspection

NOTE: Fill in the respective pages of the TEST REPORT in Section 13.4. “Test Report”!

7-6


7.4. Checks prior to switching on

7.4.1. Record the equipment data

For purposes of identification and quality assurance, the following equipment data shall be recorded:

• Rated voltage of the primary plant

• Busbar configuration (double busbars, 1½ breaker scheme etc.)

• Type of station (outdoor/indoor, gas insulated)

• Cubicle number(s)

• Central unit number

• Designations and revision indices of the diagrams

7.4.2. Visually inspect for transport damage

Deformed housings, dents and damaged paintwork are an indication of transport damage. Where such indications are observed, check the proper function of the respective unit especially thoroughly. In severe cases, consult the supplier to assess the best course of action.

Electrical and optical fiber cables must not be bent or pinched.

Check that all the plug-in boards and modules are properly inserted and secure.

Check that the consignment is complete.

7.4.3. Visually inspect the external wiring and cables

Check that the gauges of all cables are adequate for the current to be conducted.

Check that the cable screens are properly grounded.

Check the tightness of the connections by exerting moderate force.

Screened leads must be used for CT and VT circuits as described in Chapter 6. “Erection and Installation”.

7.4.4. Check the grounding of cubicles and other units

Cubicles and equipment must be grounded as described in Chapter 6. “Erection and Installation”.

7-7


7.4.5. Check the auxiliary DC battery supply

Disconnect the auxiliary supply from the protection equipment (green connector).

Check the grounding of the battery supply. The battery circuit can be grounded

• at either positive or negative pole

• symmetrically via impedances

• not at all (ungrounded)

Check for ground faults if the battery circuit is symmetrically grounded via impedances or ungrounded. A ground fault on the station battery does not influence the operation of REB500 itself, but the correct operation of the binary inputs and outputs and therefore the system as a whole cannot be guaranteed.

Measure the following voltages:

• positive to negative

• positive to ground

• negative to ground

For higher availability, the station may be equipped with redundant auxiliary supplies. In this case, check the second battery supply in the same way as the first. The two supplies must not be connected in parallel at any point.

The battery voltage must be within the permissible range of the power supply unit(s) in the busbar protection system under all operating conditions (refer to the technical data of the respective power supply unit). Check that the battery leads are connected with the correct polarity.

If all these checks are satisfactory, reinsert the green auxiliary supply connectors.

NOTE: Make sure that the battery circuits are properly protected and multiple circuits are not interconnected.


7-8


WARNING: Power supply units may never be inserted or with-drawn with the auxiliary supply connected. Therefore place the switch on the front of the power supply unit in the off position and unplug the green connector on the end of the battery cable.

The other modules may only be inserted or withdrawn when the switch on the front of the power supply unit in the off position or there is no power supply unit fitted.

7.4.6. Check the settings

The commissioning engineer does not generally have to calculate or confirm the calculation of the protection settings. He only checks and records

• whether there appear to be basic or obvious errors

• who calculated the settings


7.4.7. Check the CT circuits

DANGER: Never interrupt CT circuits during operation. Where manipulations in CT circuits are necessary, be sure to short-circuit them at the shorting and isolating terminals beforehand. After completing work on the CT circuits, make sure that they are closed, i.e. no longer interrupted, and switch the shorting and isolating terminals back to their normal operation position again.

NOTE: The CT circuits are not normally tested by the protec-tion commissioning engineer. He only records who checked them.

Check that the CTs are connected in strict accordance with the diagram supplied.

Perform the following checks to establish the correctness of the CTs and CT circuits:

7-9


Polarity

The test circuit is given in Fig. 7.1.

There must be a positive deflection on the voltmeter when the switch (S) closed. The polarity must be checked at every protec-tion unit.

This provisionally checks the CT circuit and confirms the polarity of the CT.

P1

P2 s2

s1 +

Battery(e.g. 4.5 V) V

HEST 005040 C

S

+

Fig. 7.1 Circuit for checking CT polarity

Ratio and wiring

The CT ratios and wiring are checked by primary injection be-tween the three phases R,S and T and ground (R-0, S-0 and T-0) and phase-to-phase (R-S and R-T). The phase and neutral currents flowing in protection input circuits are tested.

Apart from checking the ratios and wiring, the phase-to-phase injection also checks that all three phases are connected with the same polarity.

7-10


L1L2L3

L0

~~

Protection

HEST 005041 C

Fig. 7.2 Example of primary phase-to-ground injection

Knee-point voltage

This requires the connection of an AC test voltage (HV!) to the CT secondary and the measurement of current and voltage. The primary winding must not be short-circuited.

The values recorded indicate whether the CT has a protection or metering core. A protection core has a relatively high knee-point voltage (the point at which a 10% reduction of voltage pro-duces a 50% reduction of current).

NOTE: This check is very important, since swapped protection and metering cores are only apparent during a power system fault (possible false tripping of the BBP or failure of the BFP to trip) not in normal operation.

Fig. 7.3 Recording the magnetizing curve

7-11


Grounding

Every electrically insulated CT circuit must be grounded at one point (of advantage is a point that is accessible during normal operation).


7.4.8. Check the VT circuits

NOTE: The VT circuits are not normally tested by the protec-tion commissioning engineer. He only records who checked them. Check that the VTs are connected in strict accordance with the diagram supplied.

Perform the following checks to establish the correctness of the VTs and VT circuits:

Polarity

This test is generally performed on the secondary windings.

Ratio

Measure the secondary voltage after switching on.

Grounding

Every electrically insulated VT circuit must be grounded at one point (of advantage is a point that is accessible during normal operation).


7-12


7.5. Commissioning the protection system

DANGER: To avoid any possible false tripping due to wiring mistakes, interrupt all the tripping circuits before switching the protection on for the first time.

The protection system is switched on by placing the switch on the power supply units in the “ON” position. Providing all the bay units (BU’s) are switched on and correctly connected by optical fiber cables to the central unit (CU), the system is ready for operation and standing by after the initialization procedure (about 5 min). The display shows, for example:

Ready Alarm Trip

ABB REB 500 V7.xx (xx = Softwareversion)

V1.50AB 03-11-03

Should this not be the case, follow the procedure given in Chapter 9 “Fault finding”.

There should not be any alarms, assuming all the isolators and return confirmation signals are properly connected and energized (if not, see Section 7.5.2. 'Simulation of isolator and circuit-breaker status signals').

Other operations require the connection of a PC (HMI500 pro-gram) in order to be able to communicate with the protection system.

7.5.1. Communicating with the protection system

Connecting the PC

The PC is connected to the central unit or bay unit by means of the optical connecting cable supplied.

Minimum PC requirements

The PC operator program runs on an IBM PC or compatible running MS Windows. The minimum PC requirements are described in Section 4.3.1.

Starting the operator program

See Section 4.4. “Starting HMI500”.

7-13


7.5.2. Simulation of isolator and circuit-breaker status signals

In order to operate, the REB500 protection system requires signals from the isolators and circuit-breakers indicating their status. If one or several positions are unknown, the protection system starts incompletely. The system is only fully operational and standing by when all the position signals are available.

At the beginning of commissioning, these signals are frequently incorrectly wired or the supply for the auxiliary contacts is not switched on. To enable commissioning of the protection system to proceed in spite of this, the positions of the isolators and circuit-breakers have to be simulated. This can be achieved either using jumpers at the terminals or by simulating opto-coupler positions in the test mode (see Section 4.5.5.1. for the operation of the test generator). Double click on status field of an opto-coupler input to change its status. The color of the status field then changes to yellow.

Once this has been done, no alarms with the exception of “Test generator active” may be active.

7.5.3. Comparison of diagrams

Check that the binary and analog inputs and binary outputs in the station diagram conform to the REB500 diagram. Systematic discrepancies such as a different polarity of all CTs can, of course, occur and are permissible. The diagrams must then be corrected accordingly.

7-14


1 A

5 A

N

12

3

IL1

1 A

5 A

N

45

6

IL2

1 A

5 A

N

78

9

IL3

1 A

5 A

N

1011

12

IL0

HEST 025002 C

L3 L2 L1

Fig. 7.4 Standard CT wiring diagram

7.5.4. Comparison with the layout of the primary system

Check that the REB500 plant diagram (layout) conforms to the primary system (see Section 7.6.).

NOTE: Check that the locations of the CTs in the single-line diagram in the REB500 database (HMI500, menu item “Single-line diagram” in the “View” menu) conforms to the actual primary system. This check is essential if an end fault protection is installed, because it influences the tripping logic and none of the tests discloses an incorrect location.

Should some items of primary system plant not yet be installed, the have to be “masked” accordingly (see Section 7.6.).

7-15


7.5.5. Checking the analog inputs (CTs)

Using a test set, SVERKER or ABB MODURES Type XS92b, inject a current into each of the CT inputs.

The CTs can be checked in one of the following ways:

• Reading the injected currents on the local HMI. (Note: The readings are referred to the primary values.)

• Reading the injected currents via HMI500 by selecting “Analog input measurements” in the “View” menu

• Reading the injected currents via HMI500 by selecting “Protection zone measurements” in the “View” menu

• Reading the injected currents via HMI500 by selecting “Single-line diagram” in the “View” menu

• Increasing the currents until the protection function (e.g. busbar or end fault protection function) picks up.

Checking usually involves increasing the current until the protection function picks up, but this is not imperative.


7.5.6. Checking the analog inputs (VTs)

Using a test set, SVERKER or ABB MODURES Type XS92b, injects a voltage into each of the voltage transformer inputs.

The checks can be executed in different ways:

• Reading the injected voltage on the local HMI

• Reading the injected voltage via HMI500 by selecting “Analog input measurements” in the “View” menu.

NOTE: Primary values of phase-to-neutral voltages are displayed.

7-16



7.5.7. Checking the binary inputs signals (opto-coupler inputs)

Check the proper function of every binary opto-coupler input by exciting the signal source.

The binary inputs can be checked in one of the following ways:

• Reading the statuses on the local control unit

• Reading the statuses via the HMI500 by selecting “Binary input/output status” in the “View” menu

• Checking the events generated in the event list.

The event list enables the correct assignment of the signals as well as their operation to be checked.


7.5.8. Check auxiliary contacts on the isolators and circuit-breakers and the “CLOSE” command

The function of these signals is described in Sections 3.7.3. and 3.7.4.

7.5.8.1. Wiring the auxiliary contacts

NOTE: The standard wiring of the N/C auxiliary contacts on L1, L2 and L3 phases of isolators and circuit-breakers is in series and the N/O contacts in parallel (see Fig. 7.5).

This is reversed in the case of the special version “Not CLOSED = OPEN” (see Fig. 7.7).

7-17


+

+

Switchopen

Switchclosed

CB closecommand

CB close command

HEST 005039 C

Fig. 7.5 Isolator and circuit-breaker statuses for the manual “CLOSE” signal

7.5.8.2. Timing sequence

To be able to operate discriminatively, the protection has to know the actual configuration of the busbars. For this purpose, all auxiliary contacts on the isolators and circuit-breakers must be connected to the binary inputs of the respective bay units.

Thus every isolator and circuit-breaker has to be equipped with potentially-free normally open and normally closed contacts for every phase, the N/O contact signaling that the corresponding pole is closed and the N/C contact that it is open.

Isolators

During the closing operation of an isolator, the N/O contact must already signal its closed status before the main contacts reach their breakdown voltage.

Conversely, during the opening operation, the N/O contact (“CLOSED” signal) should not open before the main contacts have exceeded their breakdown voltage and it is impossible for an arc to ignite. If this condition cannot be fulfilled, i.e. the N/O

7-18


contact signals that the isolator is open before it has reached its breakdown voltage, the N/C contact must not close before the main contact exceeds its breakdown voltage.

Circuit-breakers

In the case of a closed circuit-breaker, the auxiliary contact for “CLOSED” simply has to signal “CLOSED”.

The auxiliary contact for “OPEN” simply has to signal “OPEN” when the circuit-breaker is open.

The auxiliary contacts on a circuit-breaker do not have to take its breakdown voltage into account (see Fig. 7.6).

The problem is therefore solved using the circuit-breaker “CLOSE” command and an adjustable reclaim time (see Section 3.8.7.4.).

NOTE: The minimum duration of the circuit-breaker “CLOSE” command must guarantee that the “CLOSE” auxiliary contact is definitely closed (must overlap). If necessary this has to be achieved by configuring an input signal prolongation for the circuit-breaker “CLOSE” command.

End position:Isolator/bus-tie breakeropen

Aux. contact must be closed

Isolator/bus-tie breaker closing

N/O aux.contact signallingmain contact CLOSED

Isolator/bus-tie breaker opening

Flashover gap

End position:Isolator/bus-tie breakerclosed

Aux. contact may be closedAux. contact must be open

N/O aux.contact signallingmain contact OPEN

Isolator/bus-tie breakermain contact

HEST 005036 C

Fig. 7.6 Isolator timing sequence

7-19


The protection system supervises that only one signal is being generated (i.e. either “CLOSED” or “OPEN”), otherwise an isolator alarm is given after a delay. The alarm can be configured to block the protection if necessary (see Section 3.7.4.6.).

7.5.8.3. Special version “Not CLOSED = OPEN”

If the auxiliary contacts do not fulfill the above conditions, the logic “Not CLOSED = OPEN” can be used. (This is, however, a special version and not absolutely necessary. Its application has to be decided from case to case.) The arrangement must include an additional input signal which supervises the isolator auxiliary supply.

ABB principle:

Isolator

closed

open

Current measurement

open closed open1

0

1

1

1

1

1

1

1

0

0

0

0

0

0

0

closed

open

Current measurement

not CLOSED = OPEN:

(When both isolator position inputs are inverted)

HEST 005042 C

Fig. 7.7 Switching sequence of the isolator auxiliary contacts

Inverting the logic means that local events are generated while a bay unit is starting that signal a change of input status that did not take place. Correct operation is nevertheless unimpaired.

7-20


7.5.8.4. Checking the isolator and circuit-breaker auxiliary contacts

Check the timing sequence of the isolator auxiliary contacts by inspecting the construction of the isolator or assessing it from the respective data sheet.

Verify the operation of the “CLOSED” and “OPEN” contacts 1. according to the circuit diagram and 2. by physically opening and closing the isolator. This can be

accomplished by opening one of the following HMI500 or local HMI dialogues: • “View/Switchgear objects”

• “View/Binary input/output status”

• “View/Single-line diagram” (HMI500 only)


7.5.8.5. Checking the manual “CLOSE” command

Further information on the operation is given in Section 3.8.7.

NOTE: Check for every configured circuit-breaker that its “CLOSED” signal (command) is detected by the protection, i.e. “CLOSE” commands from local and remote devices, from the station automation system (SAS) or from the auto-reclosure equipment. The local HMI is the best way of checking the circuit-breaker “CLOSE” command, because the signal is generated only briefly and the local HMI is refreshed the quickest. The corresponding menu item is “Measurements/Inputs”.

Alternatively the circuit-breaker “CLOSE” command can be temporarily configured as and event and its operation observed in the HMI500 event list.


7-21


7.5.9. Checking the binary output signals (tripping circuits and alarms)

The contact load and rupture capacity given in Chapter 3. “Structure, Function and Technical specification” must not be exceeded.

WARNING: Test operations of circuit-breakers and isolators require the permission of the user and all the prescribed safety precautions must be observed. Avoid unnecessary switching operations.

The tripping circuits are tested in the same way as the alarm circuits by setting them appropriately in the test mode (the operation of the test generator is described in Section 4.5.5.1.).

Set the HMI500 to the test mode by selecting “Test mode” from the “Testing” menu.

NOTE: To enable a start to be made, the password is set to “Test” (case sensitive) when the program is supplied.

Click on the “Unblock all relays” button in the test mode dialogue.

In the test mode, select “Binary input/output status” in the “View” menu to view the outputs of a binary module. The status of an output can be changed by double-clicking on the corresponding field, which then changes to yellow.

7-22


Fig. 7.8 HMI500 dialogue “Binary input/output status” in the “View” menu

Check that the correct circuit-breaker tripping coil is tripped by the correspondingly configured tripping output. Energizing the output relay checks all the external alarms and trips.

NOTE: It is recommended to transmit the signals to activate all the external alarms on the system (annunciator panels, station automation system etc.) to ensure that an alarm is always externally signaled. This can also be achieved by combining several alarms (general alarm).

WARNING: All external relay coils must be fitted with freewheel diodes or voltage-dependent resistors (VDRs). Tripping signals are generally interrupted by the circuit-breaker itself.


7-23


7.5.10. Checking the starting of the breaker failure protection

The breaker failure protection is started by various other protection functions and therefore its connections to each of them have to be checked (same procedure as in Section 7.5.7. “Checking the binary inputs signals (opto-coupler inputs)”).

NOTE: In principle, every protection function that can trip the circuit-breaker should also start the breaker failure protection.

These are typically:

• Busbar protection (when busbar and breaker failure protection functions are performed by REB500, the connection between the two is established in the software)

• Bay protection (distance or longitudinal differential)

• Remote trip from the other end of a line (direct transfer tripping)

• Transformer protection (differential, Buchholz or overtemperature)

• Overcurrent protection trip.

NOTE: Take care that the tripping signals generated by the bay protection (e.g. distance protection) are used to start the breaker failure protection and not the starting signals of the bay protection functions (e.g. distance protection starting signals).

NOTE: Starting has to be single-phase where single-phase reclosure is being applied, otherwise three-phase starting is permissible.

7.5.11. Checking protection stability

The stability check verifies that all the CTs are connected with the correct polarity and have the correct ratio.

All the feeder and bus-tie breaker CTs must be included, otherwise correct operation of the protection cannot be guaranteed.

Wherever possible the stability should be checked before the busbar is energized, because the risk of a busbar fault is

7-24


especially high when it is being energized for the first time (flashovers, grounding isolators still closed etc.).

7.5.11.1. Checking through-fault stability with de-energized busbars

Inject a current from a primary injection test set (25 % of the CT rated current is recommended) into two feeders (a reference feeder and one other feeder, see Fig. 7.9). Any feeder can be used as reference. Compare each of the other feeders and bus-tie breaker with the reference feeder.

If a bus-tie breaker is only equipped with one set of CTs, note that the they are used by two busbar sections.

In the case of a bus-tie breaker equipped with two sets of CTs (see Fig. 7.10), make sure that the set of CTs assigned to the busbar section under test is checked. The simplest way of ensuring this is to short-circuit the CTs belonging to the section not under test directly at the CTs or as close as possible to them.

The feeder currents and the differential current can be read using HMI500.

NOTE: The comparison with the reference feeder must be con-ducted for phase and neutral currents for protection schemes that evaluate the neutral current.

7-25


Reference feeder

Primaryinjectiontest set

I

II

Fig. 7.9 Test set-up for checking protection through-fault stability by primary injection (2 feeders)

Reference feeder

Primary injection test set

Short-circuit CTs

I

II

Fig. 7.10 Test set-up for checking protection through-fault stability by primary injection on busbar I (bus-tie breaker with two sets of CTs)

Result of the check of Fig. 7.10

• BBI and BBII are not conducting differential current.

Repeat the check for the CTs of BBII.

7-26


7.5.11.2. Checking through-fault stability with load current

Where protection stability cannot be tested before the busbar is energized or in the case of an extension to an existing system, it has to be tested using load current.

WARNING: For this test, either tripping by the protection has to be blocked or the tripping circuits have to be interrupted before the currents are applied to the protection.

In order to carry out the test, all the amplitudes and directions of the primary currents must be known. Perform one of the following:

Alternative a) Short-circuit the CTs and isolate them from the protection.

Alternative b) Use the test mode to simulate that all the isolators are open (this is the simpler method).

In the case of a), connect the infeeds one by one, or in the case of b), simulate the closure of the isolators one by one. Whichever method is chosen, check that the differential current increases as each infeed is connected (either HMI500 or the local HMI in the central unit). Repeat this procedure with the loads and the differential current must reduce as each feeder is connected.

NOTE: In the case of systems, which evaluate the neutral current, the differential current of the neutral measurement must be checked as well. A neutral current has to be simulated in a symmetrical power system in order to perform the stability test (see Fig. 7.11).

7-27


Fig. 7.11 Testing the through-fault stability of the neutral circuit

WARNING: Take great care not to open-circuit a CT secondary by mistake.

Any other protection devices in the same CT secondary circuit must not be influenced in any way (e.g. transformer differential protection or ground fault relays).


7.5.12. Setting the system time

Set the date and local time by selecting “Set system time” in the HMI500 “Tools” menu.

7.5.13. Viewing traceability data

Refer to Section 4.5.5.2. “Testing / Installation mode”.

7.5.14. Final test and inspection

Print the report with all the settings and the configuration by selecting “Reports” in the “Tools” menu and checking the “Print all reports” checkbox in the dialogue that opens (see Section 4.5.6.2. “Tools / Reports”).

Check all the settings and the configured features such as as-signment of modules, auxiliary supply values and the assign-

7-28


ment of signals to each opto-coupler input and relay output once again in the report!!

Visually check that all the temporary changes have been re-moved and the system restored to its operational state. Pay special attention to:

• interrupted tripping circuits

• interrupted alarms

• interrupted input signals

• short-circuited CTs

• interrupted VTs

Make sure that the report has been completely filled in.

7-29


7.6. Configuring REB500 to match the layout of the primary plant

7.6.1. Introduction

If the layout of the primary plant changes, the image of the station in REB500 has to be reconfigured to suit.

The simplest way of achieving this is activating and deactivating individual items of plant or groups of items using HMI500.

NOTE: The layout of the station as presented by HMI500 under “View/Single-line diagram” must always reflect the actual arrangement of the primary plant.

Reconfiguration can become necessary when:

• a bay has been added to the station (see Section 7.6.3.)

• a bay is either taken out of service (e.g. a feeder which is no longer needed is dismantled) or cannot be commissioned immediately (see Section 7.6.4.)

• a bus-tie breaker or longitudinal isolator is planned for the future and is shorted on the primary side during commis-sioning (see Section 7.6.5.)

• for example, a feeder circuit-breaker has not been installed yet, but the feeder itself has to be commissioned (see Section 7.6.5.)

NOTE: All planned additions to the station must be provision-ally configured when engineering the system.

Provisionally configured bays and items of plant (future addi-tions) appear white in the single-line diagram presented by HMI500 under View/Single-line diagram (see Fig. 7.12 “View/Single-line diagram”).

7-30


Fig. 7.12 View/Single-line diagram

7.6.2. Procedure

The procedure for reconfiguring REB500 is as follows:

1. Activate or deactivate bays and items of plant to correspond to the actual situation of the station (see Sections 7.6.3., 7.6.4. and 7.6.5.).

2. Block REB500 by applying a signal to the input “Block output relays” on the central unit.

3. If a bay unit has to be deactivated, it must be switched off from this point on.

4. If modules have to be added to or removed from the central unit, this has to be done now (see Section 8.5. “Replacing units”).

5. Enter the HMI500 installation mode by selecting “Testing/Installation mode” and delete the existing REB500 database by selecting “Delete database in the protection system”. HMI500 then terminates automatically.

6. In can occur occasionally with CPU 04 that the installation mode does not correctly delete the database. REB500 cannot then restart and the database has to be deleted a second time using RebLoad (see Section 8.5.7. “Delete database”).

7. Restart HMI500 when “Load database” appears on the local HMI of the central unit.

7-31


8. Download the modified database by selecting “File/Download to protection system”. REB500 then restarts automatically.

9. If additions to the station have been unmasked, the corresponding bay units must now be connected and addresses assigned to them (see Section 8.5.3.).

10. If plant that has been removed from operation is being recommissioned, this has to be carried out in accordance with the present Chapter 7. “Commissioning”.

7.6.3. Adding a bay to an existing station

If a complete bay is being added to a station (e.g. feeder or bus-tie), then

• the bay has to be activated in HMI500 (see Section 7.6.3.1.)

• the new hardware (e.g. bay unit) has to be connected in accordance with the REB500 wiring diagram

7.6.3.1. Activating provisionally configured bays

To activate a provisionally configured bay, select “Configuration / Activate/deactivate device” in HMI500 and then click on the button “Activate all” (see Fig. 7.13 “Configuration - Activate/deactivate device”).

A bay that has been newly activated appears black in the single-line diagram (see Fig. 7.12 “View/Single-line diagram”).

Occasionally, it is a condition that although the primary equip-ment of a bay has not been installed and thus no signals can be transmitted to the protection, the REB500 bay unit has to be fitted and in operation. In this case, open the dialogue “Activate/deactivate device” in the “Configuration” menu and with the corresponding bay selected click on the button “Activate (no objects)” (see Fig. 7.13).

Bays activated in this mode still appear white, but their designations are black to show that they are active.

7-32


Fig. 7.13 Configuration - Activate/deactivate device

7.6.3.2. Activating central unit modules

It is necessary to activate central unit modules when:

• an additional power supply unit is inserted

• an additional bay is connected to a bus segment (node ID) that is deactivated. All the modules of the bus segment concerned then have to be activated, i.e. CPU, TRM, MBA and SCM (see Section 3.2.2.)

Central unit modules are activated by selecting in HMI500 and clicking on the button “Activate” (see Fig. 7.14 “Configuration - Activate/deactivate / device modules in the central unit”).

7-33


Fig. 7.14 Configuration - Activate/deactivate / device modules in the central unit

7.6.4. Removing a bay from operation

If a bay (e.g. feeder or bus-tie) in a station is being removed from operation or not commissioned yet, then

• the bay has to be deactivated in HMI500 (see Section 7.6.4.1.)

• the deactivated hardware (e.g. bay unit) has to be disconnected

This can become necessary, for example, when the primary equipment has been removed or de-energized (including the auxiliary DC supply) for a long period.

7.6.4.1. Deactivating bays

To deactivate a complete bay, select “Configuration / Activate/deactivate device” in HMI500 and then click on the button “Deactivate (all objects open)” (see Fig. 7.13 “Configuration - Activate/deactivate device”).

A bay that has been deactivated appears white in the single-line diagram (see Fig. 7.12 “View/Single-line diagram”).

7-34


7.6.4.2. Deactivating central unit modules

It is necessary to deactivate central unit modules when:

• an additional power supply unit is removed

• after deactivating a bay, a bus segment (node ID) is no longer needed. All the modules of the bus segment concerned then have to be deactivated, i.e. CPU, TRM, MBA and SCM (see Section 3.2.2.)

Central unit modules are deactivated by selecting in HMI500 and clicking on the button “Deactivate” (see Fig. 7.14).

7.6.5. Special cases when adding or decommissioning plant

In a very few cases, it may be necessary to activate or deacti-vate devices in the following manner:

7.6.5.1. Deactivating (items of plant shorted)

Application example:

Where a bus-tie breaker or longitudinal isolator is only planned for the future and is shorted during commissioning, it is configured by clicking on the button “Deactivate (all objects closed)” (see Fig. 7.15 “Shorted longitudinal isolator”).

Fig. 7.15 Shorted longitudinal isolator

7-35


7.6.5.2. Activating and deactivating individual items of plant

Application example:

The circuit-breaker of a feeder has not been installed, the feeder, however, has to be commissioned without it.

This is achieved by selecting “Configuration – Activate/ deactivate device/System objects” and clicking on the button “Deactivate (object closed)” (see Fig. 7.16 “Deactivating individual items of plant“).

WARNING: Activating and deactivating individual items of plant such as individual isolators can cause the protection system to respond in an unexpected manner. Deactivating items of plant affects the protection intertripping and tripping logic and may therefore only be carried out following consultation with ABB. ABB cannot accept any responsibility for incorrect use of this function!

Fig. 7.16 Deactivating individual items of plant

7-36


7.7. Additional checks for REB500sys

The following additional checks described below are necessary to commission the bay protection function.

7.7.1. Commissioning a new station without any HV

When commissioning a new station or a station, which is not energized, the busbar and breaker failure protection functions (standard REB500sys functions) and the bay protection function (line protection options) can be commissioned separately, although certain tests do overlap and should be coordinated to save time.

Note also that, for example, injecting current in the analog input of one feeder can trip other feeders via the intertripping logic. This can, however, be prevented by taking the appropriate precautions (interrupting tripping circuits, blocking station protection functions or blocking tripping relays).

7.7.2. Additions to an existing station

When adding to an existing station protected by REB500sys, more checks have to be carried out than is the case with REB500 (e.g. auto-reclosure cycle). To avoid any risk of the station protection functions (BBP, BFP and EFP) being affected and possibly mal-operating when performing the additional checks, the following procedure is recommended. The basic philosophy is to check the bay unit on its own first (without the rest of the REB500 system). This is done in the stand-alone bay unit mode and requires that the setfile be loaded in the bay unit to be extended beforehand as follows:

• Step 1

Interrupt the optical fiber link between the central unit and the by unit to be commissioned.

• Step 2

Switch on the auxiliary supply to the new bay unit.

• Step 3

Appropriately update the setfile of the REB500sys in question to include the new bay unit (activate the feeder, see Section 7.6.) and download it to the new bay unit. The setfile must include all the settings needed for the new bay unit.

7-37


• Step 4

Check the analog inputs.

Refer to Sections 7.5.5. and 7.5.6.

Measuring the pick-up values of functions (e.g. distance protection function) is unnecessary, because they are fully processed by the software and any error would be detected by the self-supervision function. However, it is normal to measure the reactances of the various distance measuring zones. This may be omitted if a suitable test set is not available.

• Step 5

Check the binary inputs and outputs.

Refer to Sections 7.5.7., 7.5.8. and 7.5.9.

• Step 6

Providing the auto-reclosure function is active, a complete auto-reclosure cycle with the circuit-breaker should be carried out, since it depends on various external signals (circuit-breaker status, spring pressure etc.). The correct processing of these signals can be verified using the test sequencer (see Chapter 12). An external current or voltage source is not necessary.

• Step 7

Block the REB500 system (e.g. using “Block output relays” on the central unit).

• Step 8

Download the updated setfile to the central unit. This requires that the PC running HMI500 be connected either directly to the central unit or a bay unit, which is already operational.

WARNING: On no account connect the optical fiber link to the new bay unit before the setfile has been successfully downloaded to the central unit.

7-38


• Step 9

Switch off the bay unit.

Connect the optical fiber cable going to the central unit.

Switch on the bay unit.

• Step 10

Perform the busbar protection through-fault stability check (see Section 7.5.11.).

• Step 11

Check the direction of the distance protection function with load current.

This is achieved by measuring real and apparent power in L1 phase.

The real and apparent power measurements of all the directional functions can viewed by selecting “View/BP function monitoring”.

The direction “Forwards” or “Backwards” is also displayed for both real and apparent power as soon as a valid measurement has been made.

The display is influenced by the setting ‘CT Neutral’ “Line side/Busbar side” for the distance protection function.

The default setting of ‘CT Neutral’ for the distance protection function is CTs grounded on the busbar side.

Note the following with respect to busbar protection:

The side on which the CTs are grounded is of no consequence for the busbar protection and does not therefore have a setting. What is important, however, is that the grounding of all the CTs on the busbars is the same (and have the same winding sense), otherwise the differential current will not be correct.

Where this is not the case, the connections to the corresponding CT inputs on the respective bay units must be reversed (current phase-angle rotated by 180°).

In the feeders in which the current direction has been rotated in the bay unit by 180°, the setting parameter 'CT Neutra' of the distance function must also be respectively corrected to corresspond to actual earting direction of the CT.

7-39


Check the direction of the transformer differential protection function with load current.

The stability check is performed by comparing the incoming and outgoing current with the differential current.

The differential current should be very small (in the low % values) in comparison to the throughput current.

The incoming and the outgoing current can be checked in the display 'Analog input measurements' for the respective feeder.

The circulating current (and the restraining current) are displayed in the menu 'BP function monitoring' under 'Transformer differential protection'.

• Step 12

Restore REB500 to normal operation.

7-40

REB500/REB500sys 1MRB520292-Uen/Rev. D ABB Switzerland Ltd

August 05

8. OPERATION AND MAINTENANCE

8.1. Introduction .............................................................................. 8-3 8.1.1. Safety instructions ................................................................... 8-4

8.2. Operation ................................................................................. 8-5 8.2.1. Introduction .............................................................................. 8-5 8.2.2. Viewing data on the local HMI ................................................. 8-5 8.2.2.1. Menu structure......................................................................... 8-8 8.2.3. Signalling LEDs and display texts............................................ 8-9 8.2.3.1. Normal operation with no failures ............................................ 8-9 8.2.3.2. Alarm status............................................................................. 8-9 8.2.3.3. Tripped status .......................................................................... 8-9 8.2.3.4. Resetting the protection after a trip........................................ 8-10 8.2.4. Viewing the event list and disturbance recorder records........ 8-10 8.2.5. Critical switching operations during normal operation............ 8-10

8.3. Maintenance .......................................................................... 8-12 8.3.1. Protection system defect........................................................ 8-12 8.3.1.1. General alarm ........................................................................ 8-12 8.3.1.2. Unexpected restart and start-up phase.................................. 8-12 8.3.1.3. Differential current alarm........................................................ 8-13 8.3.1.4. Isolator alarm ......................................................................... 8-13 8.3.2. Protection blocking functions ................................................. 8-13 8.3.3. Protection tripping.................................................................. 8-15 8.3.4. Special operating modes ....................................................... 8-17 8.3.4.1. Inspection and maintenance .................................................. 8-17 8.3.4.2. Transfer tripping.....................................................................8-18 8.3.4.3. Isolator auxiliary contact logic “Not OPEN=CLOSED” ........... 8-18

8.4. Periodic maintenance ............................................................ 8-19 8.4.1. General .................................................................................. 8-19 8.4.2. Examples of maintenance checks ......................................... 8-19 8.4.3. Example: Maintenance check on a feeder circuit-breaker ..... 8-20 8.4.4. Example: Maintenance check on a bus-tie breaker ............... 8-29 8.4.5. Maintenance of bay protection functions

(REB500sys only) .................................................................. 8-32 8.4.6. Checking the local HMI .......................................................... 8-32

8.5. Replacing units ......................................................................8-33 8.5.1. Procedure .............................................................................. 8-33 8.5.2. Replacing modules in the central unit .................................... 8-34

8-1

ABB Switzerland Ltd REB500/REB500sys 1MRB520292-Uen/Rev. D

8.5.3. Replacing a bay unit .............................................................. 8-35 8.5.4. Checking newly installed hardware........................................ 8-37 8.5.5. Report and traceability data ................................................... 8-37 8.5.6. Restoring the system to operation ......................................... 8-37 8.5.7. Delete database.....................................................................8-38

8.6. Returning modules for repair ................................................. 8-39

8-2


8. OPERATION AND MAINTENANCE

8.1. Introduction

REB500 includes continuous comprehensive self-supervision and diagnosis of the software and hardware components. By setting up a proper signaling scheme while commissioning the system, most failures are signaled externally (see Section 7.5.9. “Checking the binary output signals”). They can include internal REB500 as well as external failures in primary and secondary systems that influence the response of the protection. Other failures that are not detected (e.g. interrupted tripping circuit) are located and cleared while carrying out periodic inspection and maintenance (see Section 8.4.). Checks and measurements while the system is in normal operation (no active alarms) are therefore unnecessary.

NOTE: Normal operation without any faults is also indicated by the fact that only green LED are lit on he local HMI.

An alarm (external or on the local HMI) can concern a failure in the REB500 system (e.g. hardware failure) or in the associated primary plant (e.g. incorrect isolator status signal).

WARNING: Should the system generate an alarm, inform the trained maintenance personnel responsible.

8-3


8.1.1. Safety instructions

WARNING: Checks and maintenance on the REB500 system may only be carried out by properly trained personnel.

WARNING: Only properly trained and authorized personnel should be in possession of the HMI500 password.

8-4


8.2. Operation

8.2.1. Introduction

Operation in the case of the REB500 busbar protection system is confined to supervising the proper function of the system and assessing the system data.

There are different ways of viewing operating, disturbance and tripping data:

• local HMI (see Section 8.2.2.)

• PC running HMI500 (see Chapter 4)

• remote HMI (see Chapter 11)

• station automation system (SCS) (see Chapter 11)

8.2.2. Viewing data on the local HMI

The local HMI provides a quick overview of the status of the protection (normal operation, alarms and trips) without having to connect a PC.

It is fitted in every central unit and as an option in the bay units. On the front, it has a four-line display, three LEDs and six pushbuttons. These enable the equipment to be operated and controlled simply and conveniently where it is installed. An interface is also provided, however, for connecting a PC, which comprises an opto-electrical converter for electrically isolating the computer from the protection equipment, thus preventing the ingress of electrical interference.

Whether on the central unit or a bay unit, the local HMI enables the following to be viewed:

• current and voltage measurements

• statuses of inputs and outputs

• alarms (generated by the respective bay unit)

• system (or respective bay unit) settings

• settings of all the specific bay unit protection functions

8-5


HEST 005025 C

LEDs: green yellow red

Optical PCinterface

X.XXTripAlarmStandby

Fig. 8.1 Local human-machine-interface (LHMI)

LEDs

Each LED can be on one of three conditions: not lit, flashing or continuously lit. All the LEDs flash while the system is being initialized.

Green

The green LED does not light before the system has completed initialization and is standing by. If the green LED is not lit or flashes, the device is either not switched on or defective.

Yellow

The yellow LED flashes to signal an alarm condition (e.g. differential current or isolator alarm). When a button is pressed or a trip occurs while it is flashing, the LED changes to being continuously lit.

Red

The red LED indicates a trip. It remains lit until reset by a binary signal applied to the reset input or by selecting the HMI Reset latching function.

20 LED signals

20 additional LEDs are provided on the local HMI, each of which can be assigned to any output signal and configured to latch or not latch as the case may be.

8-6


LCD

In the event of an alarm or a trip, the functions of the three LEDs are shown on the top line and the other lines describe the event that has occurred. The respective information is displayed according to the location in the menu structure.

If none of the buttons are operated for about 10 minutes, the display backlight switches of. It switches on again automatically as soon as a button is pressed. The initial pressing of a button while the backlight is off does not change the previous display.

Pushbuttons

The six pushbuttons are used primarily to navigate through the menu structure. Any of them switches the display backlight on again if it was switched off. If the backlight is switched on, any of the buttons acknowledges the current HMI display.

Button E

Press button E to go to the next menu down.

Button C

Press button C to return to the main menu. If Reset latching is the current menu, pressing this button resets any relays that are latched.

Arrow buttons

The buttons marked “↑” and “↓” are for scrolling through displays of information needing more than four lines.

The buttons marked “←” and “→” are for moving through the menus item by item.

Setting the bay unit ID

See Section 8.5.

Checking the local HMI

See Section 8.4.6.

8-7


8.2.2.1. Menu structure

The menu structures of central unit and bay unit are basically the same. The central unit has additional menu items for system settings and specific bay units.

Menu structure of the central unit Alarms Trips Reset Latching LEDs (500BU03 only) Blocking (500BU03 only) Central unit Meas. var. Bus zones Bus zone 1 Diff. cur. alarm Bus zone 2 Diff. cur. alarm ... (other bus zones as configured) Inputs Slot 16 (where fitted) Slot 18 (where fitted) Outputs Slot 16 (where fitted) Slot 18 (where fitted) Global values Settings System response Busbar protection Phases Neutral Module check Bay units Bay unit 1 Meas. var. Currents Voltages Inputs Outputs Circuit-breakers Breaker designation ... (where configured) Settings BBP BFP (where configured) OCDT (where configured) EFP (where configured) PDF (where configured) Bay unit 2 See bay unit 1 ... (other bay units as configured)

8-8


Menu structure of the bay unit Alarms

Trips Reset Latching LEDs (500BU03 only) Blocking (500BU03 only) Global values System response BBP Phases Neutral current Overcurrent enable BFP (where configured) OCDT (where configured) EFP (where configured) PDF (where configured) Measured variables Currents Voltages Inputs Outputs Circuit-breakers Breaker designation … (where configured)

8.2.3. Signaling LEDs and display texts

8.2.3.1. Normal operation with no failures

No action is necessary in normal operation.

Central unit and bay units

HMI text LEDs Event

ABB REB500 V7.xx V1.00A 02-08-05

Green lit -

Table 8.1 Normal operation

8.2.3.2. Alarm status

In the alarm status, the system alarms that have operated can be viewed in the alarm list.

8.2.3.3. Tripped status

The trips generated by REB500 can be viewed in the trip list together with the times they occurred and the protection functions that caused them. The list shows the ten latest trips, but is deleted when the particular device is switched off.

8-9


8.2.3.4. Resetting the protection after a trip

Provision is made on the local HMI for resetting the protection system and all the signals. This is done by selecting the menu item Reset latching and pressing button ‘C’.

HMI text LEDs Event

Reset latching C: Reset E: Quit

- -

Table 8.2 Resetting latched signals and relays

Resetting latched signals and relays by pressing button ‘C’ on the local HMI is equivalent an active signal “31810_External reset” (e.g. generated by pressing an external reset button).

8.2.4. Viewing the event list and disturbance recorder records

NOTE: Viewing the event list and disturbance recorder records is recommended should an alarm occur.

The corresponding procedure is described in Section 4.5.2.7. “View / Disturbance recorder” respectively Section 4.5.2.9. “View / Event list”.

8.2.5. Critical switching operations during normal operation

WARNING: Avoid performing switching operations in the event of the following alarms before the failure has been analyzed by correspondingly trained personnel. • Isolator alarm • Switch inhibit • Differential current alarm • Inspection and maintenance Non-observance of this precaution can cause mal-operation in normal operation or a failure to trip in response to a fault (see Section 3.7.4.).

8-10


WARNING: Isolator alarm may only be acknowledged by correspondingly trained and authorized personnel.

Non-observance of this precaution can cause mal-operation in normal operation or a failure to trip in response to a fault (see Section 3.7.4.).

8-11


8.3. Maintenance

WARNING: Strictly observe station procedures in the event of a defect be it failure to trip or mal-operation.

8.3.1. Protection system defect

This section lists the signals, which occur for the various kinds of faults.

NOTE: The possible causes of failures and the action to be taken by maintenance personnel are given in Chapter 9 “Fault-finding”.

8.3.1.1. General alarm


HMI text LEDs Event

General alarm Green lit, yellow flashes until button on the local HMI pressed

CU: “41805_Alarm”

BU: No event

Table 8.3 Protection failure

8.3.1.2. Unexpected restart and start-up phase

Central unit

HMI text LEDs Event

- or CU start-up signals

The three LEDs flash

CU: “41810_In service” resets

Table 8.4 Central unit restarts

8-12


Bay units

HMI text LEDs Event

- or BU start-up signals

The three LEDs flash

BU: “21805_In service” resets

Table 8.5 Bay unit restarts

8.3.1.3. Differential current alarm

Central unit

HMI text LEDs Event

Diff. cur. alarm Green lit, yellow flashes until button on the local HMI pressed

CU: “41815_Diff. current alarm” active

Table 8.6 Differential current alarm on the central unit

8.3.1.4. Isolator alarm


HMI text LEDs Event

Isol. alarm Feeder name Isol. alarm

Green lit, yellow flashes until button on the local HMI pressed

CU: “41505_Isolator alarm” active

CU: “41830_Switch inhibit” active

BU: No event

Table 8.7 Isolator alarm

8.3.2. Protection blocking functions

This section lists the signals when the protection is blocked and the possible causes.


HMI text LEDs Event

<Subsystem> blocked (Subsystem = BBP, BFP, EFP, OCDT, PDF, BP)


CU: “41405_SP blocked” active BU: “21405_SP blocked” active

8-13


HMI text LEDs Event

Contacts blocked Green lit, yellow flashes until button on the local HMI pressed

CU: “41410_Output relays blocked” active

BU: “21410_Output relays blocked” active

BBP blocked Feeder BBP blocked


CU: “42405_BBP blocked” active

BU: “22405_BBP blocked” active

BFP blocked Feeder BFP blocked


CU: “43405_BFP blocked” active

BU: “23405_BFP blocked” active

EFP blocked Feeder EFP blocked


CU: “44405_EFP blocked” active

BU: “24405_EFP blocked” active

OCDT blocked Feeder OCDT blocked


CU: “45405_OCDT blocked” active

BU: “25405_OCDT blocked” active

PDF blocked Feeder PDF blocked


CU: “47405_PDF blocked” active

BU: “27405_PDF blocked” active

BP blocked Green lit, yellow flashes until button on the local HMI pressed

CU: “49405_BP blocked” active BU: “29405_BP blocked” active

Table 8.8 Blocking protection functions

Possible causes

The blocking of a protection function is due to either an active opto-coupler input or an internal alarm, e.g. differential current alarm.

Corrective action

Corrective action is only necessary if blocking is unintentional. If this is the case, check whether a voltage is being applied to an opto-coupler input, which would indicate a fault in the external circuit. If the fault appears to be caused by an internal alarm, check whether there is a corresponding display and correct the cause of the alarm. Refer to the instructions for the corresponding alarm in Section 8.3.1.1.

8-14


8.3.3. Protection tripping

This section lists the signals which occur when the protection trips.

Central unit

HMI text LEDs Event

Date Time Trip Feeder name Bus zone *

Green lit, red lit

CU: “42305_BBP trip” CU: “42310_BBP trip L0” CU: “42315_BBP trip L1” CU: “42320_BBP trip L2” CU: “42325_BBP trip L3”

Date Time BFP trip t1/2 Feeder name

Green lit, red lit

CU: “43305_BFP trip t1” CU: “43310_BFP trip t2”

Date Time EFP trip Feeder name

Green lit, red lit

CU: “44305_EFP trip”

Date Time OCDT trip Feeder name

Green lit, red lit

CU: “45305_OCDT trip”

Date Time PDF trip Feeder name

Green lit, red lit

CU: “47305_PDF trip”

Date Time DIST trip Feeder name

Green lit, red lit

CU: None

Date Time OCSTD trip Feeder name

Green lit, red lit

CU: None

Date Time OCINV trip Feeder name

Green lit, red lit

CU None

Date Time DIROCDT trip Feeder name

Green lit, red lit

CU: None

Date Time DIROCINV trip Feeder name

Green lit, red lit

CU: None

Date Time OVSTD trip Feeder name

Green lit, red lit

CU: None

Date Time DIREFGND trip Feeder name

Green lit, red lit

CU: None

Date Time I0INV trip Feeder name

Green lit, red lit

CU: None

8-15


HMI text LEDs Event

Date Time OCINST trip Feeder name

Green lit, red lit

CU: None

Date Time TH trip Feeder name

Green lit, red lit

CU: None

Date Time DIFTRA trip Feeder name

Green lit, red lit

CU: None

Table 8.9 Central unit trips

Bay units

HMI text LEDs Event

Date Time BBP TRIP

Green lit, red lit

BU: 21110_TRIP BU: 21115_REMOTE TRIP BU: 21305_Trip

Date Time BFP trip t1/2

Green lit, red lit

BU: 23105_BFP TRIP BU: 23110_BFP REMOTE TRIP BU: 23305_BFP trip t1 BU: 23310_BFP trip t2 BU: 23315_BFP TRIP L1 BU: 23320_BFP TRIP L2 BU: 23325_BFP TRIP L3 BU: 23335_Trip by BFP

Date Time EFP trip

Green lit, red lit

BU: 24105_EFP REMOTE TRIP BU: 24305_EFP trip

Date Time OCDT trip

Green lit, red lit

BU: 25105_OCDT TRIP BU: 25305_OCDT trip

Date Time PDF trip

Green lit, red lit

BU: 27105_PDF TRIP BU: 27305_PDF trip

Date Time DIST trip Feeder name

Green lit, red lit

BU: 2111xx_DIST Trip CB x

Date Time OCSTD trip Feeder name

Green lit, red lit

BU: 212105_OCSTD TRIP

Date Time OCINV trip Feeder name

Green lit, red lit

BU: 213105_OCINV TRIP

Date Time DIROCDT trip Feeder name

Green lit, red lit

BU: 214105_DIROCDT TRIP

Date Time DIROCINV trip Feeder name

Green lit, red lit

BU: 215305_DIROCINV TRIP

8-16


HMI text LEDs Event

Date Time OVSTD trip Feeder name

Green lit, red lit

BU: 216105_OVSTD TRIP

Date Time DIREFGND trip Feeder name

Green lit, red lit

BU: 220105_DIREFGND TRIP

Date Time I0INV trip Feeder name

Green lit, red lit

BU: 221105_I0INV TRIP

Date Time CHKI3PH trip Feeder name

Green lit, red lit

BU: 224605_CHKI3PH Picked up

Date Time CHKU3PH trip Feeder name

Green lit, red lit

BU: 225605_CHKU3PH Picked up

Date Time OCINST trip Feeder name

Green lit, red lit

BU: 226105_ OCINST TRIP

Date Time TH trip Feeder name

Green lit, red lit

BU: 228105 TH TRIP

Date Time DIFTRA trip Feeder name

Green lit, red lit

BU: 229105_DIFTRA TRIP CB L1L2L3 229110_DIFTRA TRIP CB L1 229115_DIFTRA TRIP CB L2 229120_DIFTRA TRIP CB L3

Table 8.10 Bay unit trips

8.3.4. Special operating modes

This section list the signals generated in special operating modes.

8.3.4.1. Inspection and maintenance

The inspection status is signaled when an inspection/main-tenance input is active (see Section 11.12.).

Central unit

HMI text LEDs Event

Insp./Maintenance Feeder name


CU: “41825_Inspection/main-tenance”

Table 8.11 Inspection/maintenance on central unit

8-17


Bay units

HMI text LEDs Event

Inspection Inspection number


BU: “21815_Inspection/main-tenance”

Maintenance Green lit, yellow flashes until button on the local HMI pressed

BU: “21815_Inspection/main-tenance” active

Table 8.12 Inspection/maintenance on bay units

8.3.4.2. Transfer tripping

A transfer trip is signaled when a transfer trip input is active (see Section 11.11.).

Central unit

HMI text LEDs Event

Trip transferred Green lit, yellow flashes until button on the local HMI pressed

Depends on configuration

Table 8.13 Transfer trip

8.3.4.3. Isolator auxiliary contact logic “Not OPEN=CLOSED”

A failure of the isolator image auxiliary supply is signaled when the isolator auxiliary contact logic “Not CLOSED=OPEN” is active (see Section 7.5.8.3.).

Central unit

HMI text LEDs Event

Isol. alarm Feeder name Isol. alarm


CU: “41505_Isolator alarm” CU: “41830_Switch inhibit” CU: “41820_Loss of supply

voltage” BU: “21810_Loss of supply

voltage”

Table 8.14 Isolator alarm for “Not OPEN=CLOSED” logic

8-18


8.4. Periodic maintenance

8.4.1. General

Depending on the ambient conditions, we recommend removing the dust (e.g. with a vacuum cleaner) and wiping the front of the LCD with a damp cloth (perhaps with a little washing up liquid) from time to time. Do not use petrol or cleaning agents containing alcohol.

As explained in Section 8.1. REB500 includes continuous and comprehensive self-supervision and diagnosis of the software and hardware components. Since it is in the software that the protection functions are computed, they do not require any periodic maintenance.

The protection equipment, however, is only part of the overall protection system, we recommend periodically checking all the parts that are not automatically supervised (details of the self-supervision routines are given in Section 3.6. “Self-supervision”).

The following components must be tested periodically:

• all external circuits (e.g. tripping, BFP starting, CT and VT, etc.)

• all external switching devices (circuit-breakers and isolators)

• all REB500 tripping and signaling contacts

• all REB500 opto-coupler inputs

• all REB500 analog inputs

• the local HMI

8.4.2. Examples of maintenance checks

NOTE: The following examples illustrate the advantages of the digital protection system. The protection functions do not require any testing. The examples of maintenance checks are based on a double busbar configuration operating under the following conditions:

1. Maintenance is not performed specifically on the REB500 system, but in combination with the routine maintenance of the feeder (circuit-breaker) and therefore only applies to the bay unit.

8-19


2. REB500 must not be blocked while maintenance is being performed.

3. Maintenance of the REB500 bay unit must not require that the supply be interrupted.

Since with REB500, its maintenance can be combined with that of the circuit-breaker, the power supply to consumers is not interrupted although testing covers 100% of bay equipment. Protection of the remainder of the station is unimpaired, because the bay under test is isolated from the system (busbar isolators and circuit-breaker are open because the bay is isolated for inspection and maintenance).

WARNING: Maintenance involves opening and closing circuit-breakers. Make sure that all safety notices are in place and all the safety precautions taken.

WARNING: REB500 is still fully operational while the maintenance described below is being carried out and responds accordingly.

NOTE: A test procedure similar to the examples of Sections 8.4.3 and 8.4.4. must be established for all feeders and performed at approximately 2 yearly intervals.

8.4.3. Example: Maintenance check on a feeder circuit-breaker

Fig. 8.2 Maintenance check on a feeder circuit-breaker

8-20


Conditions:

• The isolator image auxiliary supply must not be switched off for certain checks.

• The feeder must not be grounded for certain checks.

• The maintenance procedure must be gone through step by step.

• The feeder is isolated from the busbars during the test and therefore cannot conduct power.

The maintenance procedure for a feeder connected to double busbars is illustrated in Fig. 8.3 “Steps of the feeder maintenance procedure”.

Fig. 8.3 Steps of the feeder maintenance procedure

8-21


Step 1: Isolate the feeder

The conditions before Step 1 can be seen from Fig. 8.4 “Configuration of the feeder before Step 1 (on load)”.

Fig. 8.4 Configuration of the feeder before Step 1 (on load)

• Connect the PC to the central unit and start HMI500

• Open the circuit-breaker

• Open the isolators.

Check the statuses of the isolators and the circuit-breaker (providing they are active in the protection system) in HMI500 by selecting “Switchgear objects” in the “View” menu (see Fig. 8.5 “Checking the statuses of the switchgear”).

Fig. 8.5 Checking the statuses of the switchgear

• Interrupt the tripping and transfer tripping circuits.

8-22


Step 2: Check the analog input circuits

The conditions prior to step 2 can be seen from Fig. 8.6 “Configuration of the feeder before step 2”.

Fig. 8.6 Configuration of the feeder before step 2

• Short circuit the main CT leads at the terminals of the protection cubicle and open the jumper to the protection.

• As an extra precaution block the busbar protection completely for a short period by applying the signal “32205_Block BBP” to the central unit (not absolutely essential because the busbar isolators are open).

• Inject a current of 1 x IN and, it there are voltage inputs, a voltage of 1 x UN into each phase of the analog inputs.

• Read the currents and voltages via HMI500 by selecting “Analog input measurements” in the “View” menu (see Fig. 8.7 “Checking the signals at the analog inputs” and Sections 7.5.5. and 7.5.6.).

• Enable the busbar protection again.

8-23


Fig. 8.7 Checking the signals at the analog inputs

Step 3: Check the output circuit using the HMI500 test generator

The conditions prior to step 3 can be seen from Fig. 8.8 “Configuration of the feeder before Step 3”.

Fig. 8.8 Configuration of the feeder before Step 3

• Start the HMI500 test generator in the “Test mode” dialogue. This automatically blocks all the output relays (see Section 7.5.9.).

• Enable all the relays again so that the system is operating normally.

8-24


• Close the circuit-breaker.

• Operated the tripping relay of the trip circuit in question (see Fig. 8.9 “Using the test generator to initiate tripping”).

Fig. 8.9 Using the test generator to initiate tripping

• Check that the circuit-breaker has tripped. Note: If tripping is phase by phase and a CB pole discrepancy function is configured, the latter will trip the other two poles.

• Repeat the last two operations for the other phases and trip circuits.

• Check that the circuit-breaker is open, otherwise open it.

• Check the remote tripping function of the breaker failure protection if configured. The remote circuit-breaker must be ready to trip before this test. Operate the remote tripping relay and trip the remote circuit-breaker. Check that this has indeed happened.

• Check the signals to other systems (annunciator panel etc.).

8-25


Step 4: Check that the breaker failure protection starts

The conditions prior to Step 4 can be seen from Fig. 8.10 “Configuration of the feeder before Step 4”.

Fig. 8.10 Configuration of the feeder before Step 4

• Interrupt the transfer tripping circuit.

• Initiate a starting signal from the bay protection to the breaker failure protection (by simulation or secondary injection).

• Check that the starting signal has been received from the bay protection by the breaker failure protection by opening the “Binary input/output status” dialogue (see Fig. 8.11 “Checking the binary inputs”) or viewing the event list (see Section 7.5.10.).

• Restore the transfer tripping circuit.

Step 5: Check the input signals from the circuit-breaker

The following test must also be performed if the busbar image of the circuit-breaker is being used:

• Close and reopen the circuit-breaker.

• Check the status of the circuit-breaker in the same way as for an isolator (see step 7).

• Check the close command on the local HMI by opening the “Binary input/output status” dialogue, because this input signal only lasts a short time and the local HMI is refreshed more frequently (see Section 7.5.8.5.).

8-26


Fig. 8.11 Checking the binary inputs

Step 6: Check the input signals from the isolators



• Close and open the isolators to busbars I and II.

• Check the statuses of the isolators by opening the “Binary input/output status” dialogue (see Fig. 8.11 “Checking the binary inputs” and Section 7.5.8.4.).

8-27


Step 7: Recommissioning the bay



• Reinsert the jumpers in the CT secondary circuit and remove the short-circuit from the main CT leads.

• Close the isolator to connect the feeder to the desired busbars.

• Close the circuit-breaker.

Step 8: Check the load current

The conditions prior to step 8 can be seen from Fig. 8.14 “Configuration of the feeder before step 8 (on load)”.

Fig. 8.14 Configuration of the feeder before step 8 (on load)

• Compare the actual load current with the value in the “Analog input measurements” dialogue (see Fig. 8.7 “Checking the signals at the analog inputs” and Section 7.5.11.2.).

8-28


8.4.4. Example: Maintenance check on a bus-tie breaker

Fig. 8.15 Steps of the bus-tie breaker maintenance procedure

Conditions:

• The isolator image auxiliary supply must not be switched off for certain checks.

• The bus-tie breaker circuit must not be grounded for certain checks.

• The maintenance procedure must be gone through step by step.

• The bus-tie breaker is isolated from the busbars during the test and therefore cannot conduct power.

The maintenance procedure for a bus-tie breaker connected to double busbars is illustrated in Fig. 8.15 “Steps of the bus-tie breaker maintenance procedure”.

Step 1: Isolate the bus-tie breaker

The conditions prior to maintenance can be seen from Fig. 8.16 “Configuration of the bus-tie breaker before Step 1 (on load)”.

8-29


Fig. 8.16 Configuration of the bus-tie breaker before Step 1 (on load)

• Connect the PC to the central unit and start HMI500.

• Open the bus-tie breaker.

• Open the isolators.

Step 2: Check the analog input circuits

The conditions prior to step 2 can be seen from Fig. 8.17 “Configuration of the bus-tie breaker before step 2”.

Fig. 8.17 Configuration of the bus-tie breaker before step 2

• Short circuit the main CT leads at the terminals of the protection cubicle and open the jumper to the protection.

• As an extra precaution block the busbar protection completely for a short period by applying the signal “32205_Block BBP” to the central unit (not absolutely essential because the busbar isolators are open).

• Inject a current of 1 x IN and, if there are voltage inputs, a voltage of 1 x UN into each phase of the analog inputs.

• Read the currents and voltages via HMI500 by selecting “Analog input measurements” in the “View” menu (see Fig. 8.7 “Checking the signals at the analog inputs” and Sections 7.5.5. and 7.5.6.).

• Enable the busbar protection again.

8-30


Step 3: Check the output circuit using the HMI500 test generator


• Start the HMI500 test generator in the “Test mode” dialogue. This automatically blocks all the output relays (see Section 7.5.9.).

• Enable all the relays again so that the system is operating normally.

• Close the bus-tie breaker.

• Trip circuit 1, R phase (see Fig. 8.9 “Using the test generator to initiate tripping”).

• Check that the R phase pole of the circuit-breaker has tripped.

• Repeat the last two operations for the other phases and trip circuits.

• Check that the bus-tie breaker is open, otherwise open it.

• Check the signals to other systems.

Step 4: Check that the breaker failure protection starts


• Check that the starting signal has been received from the bus-tie breaker protection by the breaker failure protection by opening the “Binary input/output status” dialogue (see Fig. 8.11 “Checking the binary inputs” and Section 7.5.10.).

Step 5: Check the input signals from the circuit-breaker

• Close and reopen the bus-tie breaker.

• Check the status of the circuit-breaker as described in Section 8.4.3 “Example: Maintenance check on a feeder circuit-breaker”.

• Check the close command as described in Section 8.4.3 “Example: Maintenance check on a feeder circuit-breaker”.

8-31


Step 6: Check the load current

The conditions prior to step 6 can be seen from Fig. 8.16 “Configuration of the bus-tie breaker before Step 1 (on load)”.

• Compare the actual load current with the value in the “Analog input measurements” dialogue (see Fig. 8.7 “Checking the signals at the analog inputs” and Sections 7.5.5. and 7.5.6.).

8.4.5. Maintenance of bay protection functions (REB500sys only)

Before checking the auto-reclosure cycle of the bay protection, consider the possible effect of, for example, secondary injection on other protection functions such as the busbar and breaker failure protection functions.

WARNING: Where there is doubt, block the station protection functions by applying the input signal “31205_Block SP” to the central unit.

8.4.6. Checking the local HMI

Start the self-testing function of the local HMI by holding buttons <E> and <C> simultaneously depressed for about 5 seconds.

8-32


8.5. Replacing units

WARNING: Units and modules may only be replaced with the permission of the engineer responsible for the protection system.

8.5.1. Procedure

The best time to replace assemblies is when the station is out of operation, but even in this case, care must be taken that no unintentional operation of switchgear can take place (danger to persons close to the item of plant).

While the station is in operation, care must be taken that the station is still adequately protected when REB500 is switched off.

WARNING: Power supply units may never be inserted or withdrawn with the auxiliary supply connected. Therefore place the switch on the front of the power supply unit in the off position and unplug the green connector on the end of the battery cable. It is insufficient to simply switch off the unit. Other modules may only be withdrawn or inserted when the power supply unit 500PSM03 is switched off.

WARNING: Observe ESD (electrostatic discharge) procedures when replacing hardware components, otherwise parts sensitive to ESD may be destroyed.

8-33


8.5.2. Replacing modules in the central unit

Module Slot on backplane 500CUB03

500PSM03 1, 20

500CPU05 3, 5, 7, 9, 11, 13, 15, 19

500SCM01 4, 6, 8, 10, 12, 14, 16, 18

500BIO01 16, 18

500CIM06 19

Table 8.15 Central unit modules

After replacing the 500CMP05 module in slot 3 (CMP), it is necessary to reload the setfile. Using the TCP/IP link for the HMI500, reconfigure the new communications parameter.

Procedure:

1. Switch on the CU:

When this display appears on the local HMI, press the “E” button.

┌────────────────┐ │Simon │ │ │ │Press E for │ │Setup ... │ └────────────────┘

2. The Setup Menu will be displayed on the HMI. With the '↑' or '↓' arrows the menu item “Change IP Addr.“ can be selected. With the 'E' resp. '→' key the menu item is activated.

┌────────────────┐ │SETUP MENU │ │Change IP Addr. │ │Delete Database │ │Exit │ └────────────────┘

3. The IP address is displayed on the HMI With the '↑' or '↓' arrows the desired menu item can be selected. With the 'E' resp. '→' key the menu item is activated.

┌────────────────┐ │CHANGE IP ADDR. │ │IP Address │ │Subnet Mask │ │Gateway Adress │ └ ────────────────┘

8-34


4. With the keys '↑' bzw. '↓' the value of an item can be changed, and, move the cursor from one value to the other with the keys '←' resp. '→'. The new values are displayed, and with 'E' 'C“ are stored or cancelled.

┌────────────────┐ │IP ADDRESS │ │000.000.000.000 │ │ │ │E=Save C=Cancel │ └────────────────┘

5. The Setup Menu is displayed on the HMI. With the keys '↑' resp. '↓' the menu item 'Exit' is selected. With the key 'E' resp. '→' exit the Setup Menu.


After confirmation the central unit will be restarted automatically with the new communication parameters.

8.5.3. Replacing a bay unit

Before replacing a bay unit, check that the new unit contains the same modules (BU03 and what options are included, see Section 3.3.). When connecting a bay unit to a central unit for the first time, for example, when replacing a defective module, it is necessary to configure the communications parameters, the node ID and the device ID as they were on the old unit.

NOTE: The communication parameters that have to be set, i.e. node ID and device ID (addresses) are given in the draft report “Bus section and device allocation” accessed via the “Reports” menu item in the HMI500 “Tools” menu.

WARNING: Incorrect or incorrectly executed settings will prevent the bay unit from starting and can disable the entire system.

8-35


The setting procedure is as follows:

1. Switch on the bay unit.:

When this display appears on the local HMI, press the “E” button.


2. The Setup Menu will be displayed on the HMI. With the '↑' or '↓' arrows the menu item “Change MVB Addr.“ can be selected. With the 'E' resp. '→' key the menu item is activated

┌────────────────┐ │SETUP MENU │ │Change MVB Addr.│ │Delete Database │ │Exit │ └────────────────┘

3. With the keys '←' resp. '→' a value can be changed, with the keys '↑' bzw. '↓' move from one item to the other. The new values are displayed, and with 'E' 'C“ are stored or cancelled.

┌────────────────┐ │MVB Address │ │Node Id = 001│ │Device Id = 001│ │E=Save C=Cancel │ └────────────────┘


┌────────────────┐ │SETUP MENU │ │Change MVB Addr.│ │Delete Database │ │Exit │ └────────────────┘

Once the values have been confirmed, the bay unit restarts automatically with the new communication settings.

8-36


8.5.4. Checking newly installed hardware

Hardware components that are not included in the self-super-vision system (see Section 8.4.1.) have to be checked according to Section 8.4. or Section 7.5. “Commissioning the protection system”.

8.5.5. Report and traceability data

Record all modules that are replaced in a report and update the report every time a module is replaced.

The traceability data must also be read (see Section 7.5.13.).

8.5.6. Restoring the system to operation

Refer to Section 8.4. or Section 7.5. “Commissioning the protection system”.

WARNING: The protection system may only be restored to operation with the permission of the engineer responsible for it.

8-37


8.5.7. Delete database

It can occur occasionally with 500CPU05 or the 500BU03 (in stand-alone operation) that the installation mode does not correctly delete the database.

REB500 cannot then restart and the database has to be deleted manually using the local HMI.

The setup procedure:

1. Switch on the CU:When this display appears on the local HMI, press the “E” button.


2. The Setup Menu will be displayed on the HMI. With the '↑' or '↓' arrows the menu item “Delete Database“ can be selected. With the 'E' resp. '→' key the menu item is activated.


3. The 'Delete Database' menu is displayed on the HMI. With the 'E' key the database is deleted. With the 'C' key exit the menu item.

┌────────────────┐ │DELETE DATABASE │ │ │ │ E = Delete DB │ │ C = Cancel │ └────────────────┘



After confirmation the central unit will be restarted automatically with the new communication parameters.

8-38


8.6. Returning modules for repair

Defective modules should be shipped accompanied by a full description of the failure, wherever possible in the original packing or in packing that affords adequate protection from moisture, vibration and electrostatic discharge to your ABB company or agent or to the following address:

ABB Switzerland Ltd Power Systems Repair Centre Warenannahme PT-EG Bruggerstrasse 72

CH-5401 Baden

8-39

1mrb520292-uen-reb500sys_chap 7 _8

Documents

protection stability

reb500 protection system

breaker failure protection

circuitbreaker status

fault stability

primary system

commissioning procedure

analog inputs cts