The present invention relates to electrical power distribution systems, and more particularly, to intelligent power switch controllers suitable for three-phase high voltage power distribution systems.
In the prior art, high voltage power distribution systems have conventionally employed protective devices such as reclosing breakers (reclosers), hydraulic-mechanical sectionalizers (sectionalizers), and per-phase fuses to protect the power distribution system against damage in the presence of catastrophic events, such as phase faults and ground faults. Reclosing breakers cycle repeatedly for long duration faults, eventually locking out the entire downstream power distribution system or portions of the system having sectionalizers in order to isolate faults. Fuses similarly protect the power distribution system by melting in the presence of overcurrent events of sufficient duration. The protective actions of reclosing breakers and fuses can impact a significant number of customers and result in extensive power outages. Power interruptions and downtime negatively impact reliability metrics of the power distribution system, such as the System Average Interruption Frequency Index (SAIFI), System Average Interruption Duration Index (SAIDI), Customer Average Interruption Frequency Index (CAIFI), and Customer Average Interruption Duration Index (CAIDI).
The present disclosure appreciates that with the obsolescence of three-phase hydraulic-mechanical technology it would be desirable to supplement the protection to a power distribution system provided by conventional protective devices (e.g., reclosing breakers, hydraulic-mechanical sectionalizers, and fuses) with an intelligent switch configured as a three-phase sectionalizer.
In some embodiments, an intelligent switch configured as a sectionalizer is used in coordination with an upstream and/or downstream protective device such as reclosing breaker to automatically isolate a faulted section of a power distribution system.
In some embodiments, a controller of an intelligent switch detects an overcurrent event that is cleared by a downstream protective device without a corresponding voltage change on an upstream power distribution circuit. In response to the detection, the controller employs voltage restraint and does not open the switch, but instead permits a coordinating downstream protective device to cycle to clear the overcurrent event.
In some embodiments, a controller of an intelligent switch senses that a current on one or more phases of a power distribution circuit has exceeded a threshold current and initiates counting of a number of times that an upstream protective device de-energizes the circuit. The intelligent controller discriminates between normal inrush current while energizing and load-starting versus fault current. In response to the count satisfying a predetermined threshold count, and while the circuit is de-energized, the controller opens the switch, which isolates a section of the power distribution system without the upstream protective device locking out the entire circuit.
In some embodiments, a controller of an intelligent switch analyzes the power system and, if a fault is detected upon closing the switch, then normal counting of a number of times the circuit is de-energized by an upstream device is bypassed. The controller opens the switch immediately when the circuit becomes de-energized. The intelligent controller thus detects close-on-fault conditions, overrides the normal counter sequence, and protects the high voltage system and operations personnel from damage and danger caused by repeated cycling of a faulted circuit.
With reference now to the figures, and in particular with reference to
Power lines 104 are coupled to a load break switch (LBS) 106, which in some embodiments comprises a vacuum interrupter encapsulated in a molded hydrophobic cycloaliphatic epoxy bushing. In some embodiments, LBS 106 is configured to be compliant with International Electrotechnical Commission (IEC) 6227-103. One supplier of such an LBS is Entec Electric and Electronic Co., Ltd. As further shown in
Referring now to
Interposed between the input and output sides of LBS 106 is a three pole switch 220. Three pole switch 220 has a tripped (open) state in which power conduction between input 210 and output 212 is interrupted for all three phases and a closed state in which power is conducted between input 210 and output 212 on all three phases. Three pole switch 220 transitions between its tripped and closed states in response to a trip/close signal 222 supplied by controller 200. Three pole switch 220 additionally provides controller 200 with a switch position signal 224 indicating whether three pole switch 220 is in the tripped or closed state and a lock signal 226 indicating whether three pole switch 220 is locked in the tripped state (e.g., by actuation of a mechanical safety lock).
Controller 200 receives the indications of the input currents and voltages, output voltages, and signals 224-226 via control cable 108. Based on these signals and its internal logic, controller 200 selectively and intelligently asserts trip/close signal 222 to trip and to close switch 220 in order to protect power distribution systems and the electrically powered equipment coupled thereto.
As further shown in
In the illustrated embodiment, human interface 232 includes a display 240 through which control logic circuitry 230 can present status information, configuration information, instructions and the like to a human operator. In addition, human interface 232 includes a bank of status lights 242 providing a visual indication of the status of LBS 106 and/or controller 200. Human interface 232 also includes a number of buttons 244 that a human operator can utilize to enter configuration information into controller 200, open and close LBS 106, request display of status information in display 240, etc.
I/O circuitry 234 is configured to communicate with LBS 106 via control cable 108 as described above. In addition, I/O circuitry 234 preferably supports communication between controller 200 and other devices utilizing wired and/or wireless communication protocols (e.g., EIA-232 and/or Ethernet).
Battery backup system 236 provides battery backup power for controller 106. In this manner, controller 106 is able to operate when three-phase line input 210 and/or a local controller power system (not illustrated) is/are without power. In one exemplary embodiment, battery backup system includes a 24 V battery capable of providing a 10-hour power supply to controller 106, as well as a battery charging circuit.
In one exemplary embodiment, controller 200 can be implemented with a custom-programmed off-the-shelf device, such as the SEL-751 available from Schweitzer Engineering Laboratories (SEL).
With reference now to
Control logic circuitry 230 also includes ground fault detection logic 302 and phase fault detection logic 304 for detecting faults to ground and between phases. These faults can be reported by controller 200, for example, via display 240, status lights 242, and/or remote communication.
In order to reduce or avoid damage to electrical equipment or the power distribution system, control logic circuitry 230 is preferably equipped with close-on-fault detection logic 306. Close-on-fault detection logic 306 detects closure of LBS 106 on a faulting circuit, and in response to this detection, opens LBS 106 on a line clear condition without any counting.
Control logic circuitry 230 further includes voltage restraint logic 308, count restraint logic 310, and inrush restraint logic 312. As discussed further herein, voltage restraint logic 308 inhibits line clear logic 300 from detecting a line clear condition and from opening LBS 106 in response to a fault unless the sensed input voltage is less than a threshold voltage. Count restraint logic 310 additionally inhibits line clear logic 300 from detecting a line clear condition and from opening LBS 106 unless the sensed input current is less than a threshold current. Inrush restraint logic 312 further inhibits detection of a fault under conditions having the signature of inrush current, which can occur, for example, at motor startup or when energizing a transformer.
Control logic circuitry 230 further includes block close logic 314, which blocks closure of LBS 106 under predetermined conditions. For example, in a preferred embodiment, block close logic 314 prevents closure of LBS 106 if signal 224 indicates that a mechanical safety lock is engaged, regardless of any close command entered either remotely or via human interface 232.
Control logic circuitry 230 additionally includes interface logic 316, alarm logic 318, and communication protocol logic 320. Interface logic 316 provides the logic to receive inputs from, and provide outputs to, human interface 232. Alarm logic 318 triggers communication of alarms to human interface 232 and/or remote network-connected devices in response to alarm conditions, such as engagement of battery backup system 236, the detection of various fault conditions, etc. Communication protocol logic 316 supports communication of command, alarm, and status information between controller 200 and remote network-connected devices. As noted above, this communication, which may be over wired and/or wireless communication networks, may employ communication protocols such as EIA-232, Ethernet, SCADA, etc.
Referring now to
The process begins at block 400 of
At blocks 408-410, control logic circuitry 230 determines whether or not a line clear condition is detected by line clear logic 300 within the close-on-fault monitoring period. As indicated above, line clear logic 300 preferably only detects a line clear condition if the input voltage and input current on all phases of line input 210 are below predetermined thresholds for at least a predetermined line clear interval (e.g., about 1 s). In response to detection of the line clear condition within the close-on-fault monitoring period, control logic circuitry 230 causes I/O circuitry 234 to assert trip/close signal 222 to trip (open) LBS 106 (block 412). It should be noted that, in this case, controller 200 opens LBS 106 without any counting of fault detections or line clear conditions. As a result, damage to electrical equipment and/or the power distribution system can be reduced or avoided. If, however, no line clear condition is detected within the close-on-fault monitoring period, controller 200 refrains from operating LBS 106 with an active fault (as it is not rated for such operation), and the process passes to block 422, which is described below.
Referring now to block 420, if no close-on-fault condition was detected following closure of LBS 106, controller 200 assumes a normal operating condition. At blocks 422 and 424, controller 200 monitors for the first to occur of a line clear condition (block 422) and a fault (block 424). In response to detection of a line clear condition, the process proceeds from block 422 to block 426, which illustrates a determination of whether or not an inrush timer (which is started at block 444 in response to detection of a fault) has expired or is inactive. If the process reaches block 426 without a fault first being detected and latched, then the inrush timer will be inactive. If the inrush timer is expired or inactive, inrush restraint logic 312 blocks fault detection by fault detection logic 304, 306 for an inrush delay period. In this manner, a high current surge associated with the startup of AC motors or energizing a transformer is not incorrectly detected as a fault condition (which could potentially cause LBS 106 to be tripped). Thereafter, the process returns through page connector C to blocks 422-424.
Returning to block 426, if controller 200 determines that the inrush timer is active and has not expired, then a line clear condition has been detected following a fault. This sequence can occur, for example, if the cycling of an upstream reclosing breaker clears the detected fault. The process accordingly proceeds from block 426 to block 430, which illustrates controller 200 waiting for expiration of latch reset timer (which is started at block 442 following detection of a fault). In response to expiration of the latch reset time, the process returns to blocks 422-424.
Referring now to block 424, in response to detection of a fault by fault detection logic 304 or 306, controller 200 latches and identifies the type of fault (e.g., ground fault or phase fault). In response to detection of the fault, controller 200 starts the latch reset timer (block 442) and the inrush timer (block 444). The latch reset timer, which can have a duration of about 15 s, defines a time window after which the latched fault will be discarded if a selected number of line clear conditions is not satisfied within the time window. In at least some embodiments, the inrush timer, which defines the duration of the inrush delay period, has a longer duration, for example, of about 45 s. Following blocks 442-444, the process passes through page connector A to
With reference now to
As indicated by AND gate 460, if controller 200 detects that both of the low current and low voltage conditions indicated at blocks 450-452 are satisfied, controller 200 determines whether or not the low current and low voltage conditions remain true for a predetermined line clear duration determined by a line clear timer (blocks 462-464). In an exemplary embodiment, the line clear duration may be, for example, 1 s. If controller determines at blocks 462-464 that the low current and low voltage conditions remain true for the predetermined line clear duration, controller 200 increments a line clear count (block 450). As depicted at block 452, if the line clear count satisfies a count threshold (e.g., 2, 3, or 4), the process passes through page connector B to block 412 of
With reference now to
Referring now to
In the depicted embodiment, utility feeder branches 607a, 607b are each coupled to a respective one of intelligent LBSs 608a, 608b as described above. In each utility feeder branch 607a, 607b, the primary metering equipment (PME) 610a, 610b of the utility and the customer's reclosing breaker 612a, 612b are downstream of the LBS 608. Each utility feeder branch 607a, 607b terminates at customer premises equipment (CPE) 616a, 616b, which may comprise, for example, three-phase motors or other electrical equipment.
In the described environment, a fault 614a or 614b may occur in CPE 616 and/or on the power lines between reclosing breaker 612 and CPE 616. In the illustrated configuration, the customer's reclosing breaker 612 cycles (opens and closes) in an attempt to clear the detected fault. However, because LBS 608 continues to sense voltage on line input 210 during the cycling of reclosing breaker 612, voltage restraint logic 308 prevents controller 200 from opening LBS 608. However, because the cycling of reclosing breaker 612 clears the fault, the fault does not cause station breaker 604 to open, leaving power lines 606 energized.
With reference now to
In the described industrial environment, a fault 712a in zone A 706 or fault 712b in zone B 708 may occur. If a fault 712a occurs in zone A 706, upstream reclosing breaker 702 cycles (opens and closes) in an attempt to clear the detected fault. LBS 704 is configured with appropriate count thresholds to coordinate with reclosing breaker 702 so that controller 200 opens LBS 704 during the cycling of reclosing breaker 702 prior to reclosing breaker 702 ending its cycling and remaining a locked open state. As a result, LBS 704 isolates fault 712a and permits CPE 705 to continue to operate.
If, however, a fault 712b occurs in zone B 708, downstream reclosing breaker 710 cycles (opens and closes) in an attempt to clear the detected fault. Because LBS 704 continues to sense voltage on its line input 210 during the cycling of reclosing breaker 710, voltage restraint logic 308 prevents controller 200 from opening LBS 704. As fault 712b is cleared, power continues to be supplied to CPE 705, permitting it to continue to operate.
While various inventions have been particularly shown as described with reference to one or more preferred embodiments, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the invention. Reference made herein to an “embodiment” or “embodiments” do not all necessarily refer to one and the same embodiment, and those skilled in the art will appreciate that features of different embodiments can be combined and/or substituted in accordance with the disclosure provided herein. Further, as used herein, the term “about” indicates a value that is equal to the stated value ±20%.
The inventions disclosed herein may be realized as a system, a method, and/or a computer program product. A computer program product may include a storage device having computer-readable program code stored thereon for causing a processor (which may be part of control logic circuitry 230) to carry out aspects of the inventions. The storage device may be, for example, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. Specific examples of the storage device include a portable computer diskette, hard disk, random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), an erasable programmable memory (EPROM or Flash memory), compact disc (CD), digital versatile disk (DVD), and a memory stick. A storage device, as used herein, is specifically defined to include only statutory subject matter and to exclude non-statutory subject matter, such as signal media per se, transitory propagating signals per se, and energy per se.
Number | Date | Country | |
---|---|---|---|
62736310 | Sep 2018 | US |