ABB SUE3000 switching device troubleshooting

ABB SUE3000 switching device troubleshooting

Introduction: Why is it easy for fast switching devices to "fail to detect problems"

The ABB SUE 3000 high-speed switching device is responsible for the critical task of "quickly transferring the load to the backup feeder line in case of power failure" in power plants, chemical continuous production, data centers, and other places that require extremely high power supply continuity. Its core action is to simultaneously issue opening and closing commands to the circuit breaker after protection startup or undervoltage startup, in order to minimize the time of bus power loss. For synchronous feeders, perform fast switching; For asynchronous feeders, the first phase coincidence switching, residual voltage switching, or delay switching are used sequentially.

When on-site engineers are troubleshooting switching failures, they often encounter an awkward situation: the protective device has action records and the circuit breaker mechanism is normal, but the SUE 3000 is either "not switching" or "switched but failed". The reason often lies not in the device itself, but in external interfaces, circuit breaker position signals, control circuits, voltage measurement circuits, or parameter configurations. ABB clearly states in the manual that the error source of switching failure is rarely inside the high-speed switching device, but more often appears on the interface and external equipment. Therefore, the first step in troubleshooting is not to dismantle the device, but to understand its alarm page and event records.

First, look at the four page diagnostic information on the alarm page: SUE 3000

The SUE 3000 provides 4 alarm pages and 1 event page to indicate characteristic external faults and statuses that occur during operation. The alarm page should be grouped by priority and object, and on-site engineers should develop the order of "looking at the alarm page first, then the event page, and finally the external circuit".

Alarm page 1 mainly provides the "total fault" and switch ready status. The first item "Alarm" is the overall alarm indicator. As long as there is an alarm that causes "Not Ready", the light will light up and lock the switch. The second item "CB Fault" indicates that a circuit breaker has malfunctioned, and specific information can be found on alarm pages 2 to 4. The third item "Overcurrent activation" indicates that the "I>blocking" input is activated, the switch is locked, and manual reset is required. The fourth item "Block. Decoupling" indicates that the circuit breaker that should be opened during the switching process refuses to open, and the device re closes the just closed circuit breaker and enters the locking mode, requiring manual reset.

Alarm page 2 focuses on feeder side 1: overcurrent start, switch infeasible, external lockout, backup feeder voltage too low, circuit breaker 1 has no determined position, circuit breaker 1 command issued but not activated, circuit breaker 1 action time exceeded, circuit breaker 1 coil fault.

Alarm page 3 and alarm page 4 correspond to feeder line 2 and bus tie circuit breaker, respectively. The content is symmetrical to page 2: no determined position, command refusal, action time exceeding limit, coil fault.

The common feature of these alarms is that most require manual reset and will not automatically reset as the fault disappears. The on-site engineer must confirm that the cause of the fault has been eliminated before returning, otherwise switching again after returning will still fail.

Six typical scenarios and troubleshooting paths for switching failures

Scenario 1: The device displays "Not Ready" and does not perform any switching at all. Firstly, check if the backup feeder voltage is below 80% of the rated value. SUE 3000 considers the backup feeder without voltage as' not having a complete backup power supply 'and directly enters Not Ready. Next, check if the position signal of the circuit breaker is "one on one off". The device performs XOR evaluation on the position indication of two circuit breakers. If both are closed, both are tripped, or the position is uncertain, the device cannot determine the switching direction and will also lock. Recheck if the control circuit coil monitoring reports an error. If the coil breaks, it will be directly locked and ready for switching.

Scenario 2: The circuit breaker does not trip after the protection is activated. First, look at the "command" item corresponding to the circuit breaker on the alarm page: If the command has been issued but the circuit breaker has not acted, the problem lies in the trip coil, auxiliary contacts, terminal block, or control voltage. Recheck the "coil error" item: SUE 3000 selectively monitors the coils participating in the next switch. If the monitored coil breaks, it will report "Not Ready" and clearly indicate which circuit breaker it is. If the circuit breaker is in the test position or the spring is not storing energy, the position contact or motor energy storage contact will be locked and ready for switching. The manual recommends connecting the motor energy storage contact in series to the operating position contact and internally delaying the "Not Ready" during the energy storage process.

Scenario 3: Fast switching becomes residual voltage switching or delayed switching. Fast switching requires meeting four criteria simultaneously: phase angle less than the set value (factory 20 °), frequency difference less than the set value (factory 1Hz), backup feeder voltage greater than 80% of the rated value, and bus voltage greater than 70% of the rated value. If the bus voltage has dropped below 70%, the fast switching criterion does not hold, and the device automatically degrades to first phase coincidence, residual voltage, or delayed switching. This is not a malfunction, but a physical condition that is not met. If rapid switching is desired on site, the fault removal time, circuit breaker action time, and bus voltage drop depth should be checked to ensure they are within the design range.

Scenario 4: Decoupling occurs during the switching process. Quickly switch and issue opening and closing commands simultaneously. If the circuit breaker that should be opened refuses to open, both circuit breakers will close simultaneously, forming a short-term parallel connection. After the set disconnection delay (factory 100ms), the SUE 3000 trips the newly closed circuit breaker again and enters the lock that needs to be reset. The "Block. Decoupling" on alarm page 1 and the "CB 1 Decoupling" and "CB 1 Decoupling failed" on event page can help determine which circuit breaker refused to disconnect and whether the disconnection was successful. The disconnection itself is a protective logic, not a misoperation; Frequent disconnection should check the opening circuit and mechanism action time of the circuit breaker.

Scenario 5: The first phase coincidence switch was unsuccessful. This type of switching requires high repeatability in the closing time of the circuit breaker. The device needs to issue a closing command in advance before the minimum pressure difference occurs, compensating for the system processing time and circuit breaker closing time. If the closing time of the circuit breaker is highly discrete, or if the "CB close time" setting in the parameters does not match the actual value, the closing point will deviate from the phase coincidence window. The "CB operating time violation" prompt on the alarm page indicates that the action time has exceeded the limit, and the event page will record the failure to switch direction. When troubleshooting, the actual closing time of the circuit breaker should be measured first, and then the device parameters should be checked, rather than repeatedly adjusting the phase angle setting.

Scenario 6: Switching command issued but with incorrect direction or refusal to move. Check if the protection startup input is connected in the correct direction. The protection start input of SUE 3000 is direction dependent, with 1 → 2 and 2 → 1 wired separately. If the direction is reversed, the device may switch or lock in the wrong direction. For the configuration of three circuit breakers, it is also necessary to verify the position signal and switching direction definition of the bus tie circuit breaker. Manual startup is not directional and should be executed according to the current possible direction. It cannot replace protective startup.

Event page and fault recording: locating 'which step was not completed'

The alarm page provides "what type of fault", and the event page provides "what time, which direction, and which circuit breaker". The event page of SUE 3000 can store up to 50 records, which are overwritten by first in first out. Events include undervoltage startup, protection startup, successful and delayed switching, residual voltage or delayed switching, initial phase coincidence switching, disconnection, disconnection failure, switching direction failure, circuit breaker opening and closing commands, etc. When troubleshooting a switch failure, the chronological order of the events should be recorded: whether there was no disconnection command after the protection was activated, whether there was a disconnection command but the circuit breaker did not operate, or whether the disconnection was successful but the closing was not completed.

For more detailed analysis, fault waveform data can be exported. The fault recording of SUE 3000 can record 7 analog quantities and up to 32 digital quantities, with a total recording time of 5 seconds. It supports setting the time before and after the fault. After exporting the waveform data in COMTRADE format, tools such as ABB WinEve or REVAL can be used to view the timing of bus voltage, backup feeder voltage, differential pressure, feeder current, and circuit breaker position signals. For the first phase coincidence switching failure, the differential pressure waveform and closing command timing in the waveform recording are direct evidence to determine whether the "advance amount is sufficient".

Debugging and maintenance: Move troubleshooting to the operational phase

The debugging of SUE 3000 is divided into "cold debugging" and "hot debugging". Cold commissioning checks the position signal, control circuit, voltage measurement circuit, protection start input, and communication interface of the circuit breaker item by item under the condition of no load on the busbar and operable circuit breaker. If necessary, analog bridging is used to replace the missing busbar voltage. Hot commissioning is conducted under load conditions for switching tests, including rapid switching in two directions, disconnection tests, residual voltage switching, initial phase coincidence switching, and rapid switching of protection startup. The switching time, no current time, startup current, and voltage drop are recorded using waveform recording.

Many problems with on-site troubleshooting can actually be discovered during the cold commissioning phase. For example, poor contact of circuit breaker position contacts, coil monitoring circuit not connected in series, protection starting direction reversed, auxiliary contacts of voltage transformer MCB not connected in series, and motor energy storage contacts not connected in series in the operating position circuit. Checking these interfaces point by point during cold debugging is safer and more efficient than repeatedly switching during hot debugging.

In terms of maintenance, the SUE 3000 consists of electronic and electromechanical components, which are generally maintenance free. However, the continuity monitoring of the control circuit and the status monitoring of the circuit breaker should be checked regularly. It is recommended to prepare at least the motherboard, power module, binary I/O board, analog input transformer board, HMI cable, and HMI control unit as spare parts. After replacing the board, it is necessary to download the configuration again and check the FUPLA cycle time. The cycle time must be less than 15ms, otherwise the device cannot guarantee the switching timing. The parameters are stored in Flash and will not be lost during long-term power outages, but they need to be rechecked and configured after replacing the motherboard.