(none)
This disclosure relates to identification of a faulted phase or phases for a fault event in an electric power delivery system. More particularly, this disclosure relates to identifying a fault type based on an angular difference between a total negative-sequence current and a total positive-sequence current, and a comparison of a phase-to-phase current against a threshold.
Non-limiting and non-exhaustive embodiments of the disclosure are described, including various embodiments of the disclosure with reference to the figures, in which:
Electric power delivery systems (transmission, distribution, and the like) are subject to faults, which may include faults between one or more phases in electrical communication with each other and/or faults to ground. Protection of electric power delivery systems may require a determination of which phase or phases are involved in the fault. Certain fault conditions, for example high-resistive faults, may complicate proper fault determination. However, fault determination according to the embodiments described herein remains accurate for high-resistive faults.
Electric power generation, transmission, and delivery systems may utilize intelligent electronic devices (IEDs) to monitor for faults on electrical equipment such as transmission lines, distribution lines, buses, transformers, capacitor banks, generators, tap changers, voltage regulators, or the like. IEDs may further be configured to issue control instructions to equipment upon the detection of a fault.
Reference throughout this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, an “embodiment” may be a system, a method, or a product of a process.
Some of the infrastructure that can be used with embodiments disclosed herein is already available, such as: general-purpose computers, computer programming tools and techniques, digital storage media, and communications networks. A computer may include a processor such as a microprocessor, microcontroller, logic circuitry, or the like. The processor may include a special purpose processing device such as an ASIC, PAL, PLA, PLD, Field Programmable Gate Array, or other customized or programmable device. The computer may also include a computer-readable storage device such as non-volatile memory, static RAM, dynamic RAM, ROM, CD-ROM, disk, tape, magnetic, optical, flash memory, or other computer-readable storage medium.
As used herein, the term IED may refer to any processor-based device that monitors, controls, automates, and/or protects monitored equipment within the system. Such devices may include, for example, phase angle comparators, amplitude comparators, voltage and/or current comparators, remote terminal units, differential relays, distance relays, directional relays, feeder relays, overcurrent relays, voltage regulator controls, voltage relays, breaker failure relays, generator relays, motor relays, automation controllers, bay controllers, meters, recloser controls, communications processors, computing platforms, programmable logic controllers (PLCs), programmable automation controllers, input and output modules, and the like. IEDs may be connected to a network, and communication on the network may be facilitated by networking devices including but not limited to multiplexers, routers, hubs, gateways, firewalls, and switches, each of which may also be considered an IED.
Aspects of certain embodiments described herein may be implemented as software modules or components. As used herein, a software module or component may include any type of computer instruction or computer executable code located within or on a computer-readable storage medium. A software module may, for instance, comprise one or more physical or logical blocks of computer instructions, which may be organized as a routine, program, object, component, data structure, etc., that performs one or more tasks or implements particular abstract data types.
In certain embodiments, a particular software module may comprise disparate instructions stored in different locations of a computer-readable storage medium, which together implement the described functionality of the module. Indeed, a module may comprise a single instruction or many instructions, and may be distributed over several different code segments, among different programs, and across several computer-readable storage media. Some embodiments may be practiced in a distributed computing environment where tasks are performed by a remote processing device linked through a communications network. In a distributed computing environment, software modules may be located in local and/or remote computer-readable storage media. In addition, data being tied or rendered together in a database record may be resident in the same computer-readable storage medium, or across several computer-readable storage media, and may be linked together in fields of a record in a database across a network.
The software modules described herein tangibly embody a program, functions, and/or instructions that are executable by computer(s) to perform tasks as described herein. Suitable software, as applicable, may be provided using the teachings presented herein and programming languages and tools, such as XML, Java, Pascal, C++, C, database languages, APIs, SDKs, assembly, firmware, microcode, and/or other languages and tools. Additionally, software, firmware, and hardware may be interchangeably used to implement a given function.
In the following description, numerous details are provided to give a thorough understanding of various embodiments; however, the embodiments disclosed herein can be practiced without one or more of the specific details, or with other methods, components, materials, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of this disclosure.
IEDs 102 and 104 may use the local and/or remote current information from the electric power delivery system 100 to determine whether fault 106, is present on the electric power delivery system. Such current information may be obtained from each of the phases present on the electric power delivery system and processed within IEDs 102 and 104 to determine whether a fault is present on the system.
IEDs 102 and 104 may be in communication using communication channel 132. IEDs 102 and 104 may share data obtained from the electric power delivery system 100 over the communication channel. For example, IED 104 may communicate remote current information to IED 102, and/or IED 102 may communicate local current information to IED 104. The current information may be current information for each phase, symmetrical components, alpha components, phasors, synchrophasors, or the like.
As described in more detail herein, the fault type may be identified using symmetrical components of the current information from IEDs 102 and 104. The local and remote current information from IEDs 102 and 104 may be used to calculate local zero-sequence current (IL), remote zero-sequence current (I0R), local negative-sequence current (I2L), and remote negative-sequence current (I2R). Using these values, total zero-sequence current (I0T) and total negative-sequence current (I2T) may be calculated using Equations 1 and 2:
I0T=I0L+I0R Eq. 1
I2T=I2L+I2R Eq. 2
An angle difference between I0T and I2T may be calculated and compared with a set of predetermined angular difference sectors.
An additional check is then performed to select appropriate fault type in each sector. One possible check is comparing the total phase-to-phase current with a threshold. In one embodiment, the threshold is a function of a maximum total phase-to-phase current (Imax
As mentioned above, the proper fault type for each sector of
Both I2T and I0T may be inputs to block 308, where the angle difference between I2T and I0T may be determined. Once the angle difference is determined, block 308 may determine in which of the predetermined sectors the angle difference is located. A signal from one of the sector blocks 312, 314, 316, 320, 322, and 324 may be used with signals from phase-to-phase comparison blocks and further logic blocks to identify the fault type. If the angle difference is greater than −30° but less than or equal to 30°, then block 312 signals AND gate 344 and OR gate 332. AND gate 344 signals an AG fault if it receives the signal from block 312 and comparator 338 indicates that the magnitude of OCT is less than a threshold. As described above, this threshold may be a function of a maximum phase-to-phase current such as 0.8*Imax
Returning to block 308, if the angle difference is greater than 30° but less than or equal to 90° (which, according to
If OR gate 326 receives a signal from either block 320 or block 322, it signals OR gate 334. If OR gate 334 receives a signal from either OR gate 326 or block 314, then it signals AND gate 358. If AND gate 358 receives a signal from both OR gate 334 and comparator 352 indicates that the magnitude of IACT is greater than a threshold, then AND gate 358 signals that the fault type is ACG.
If OR gate 328 receives a signal from either block 322 or block 324, it signals OR gate 336. If OR gate 336 receives a signal from either OR gate 328 or block 316, then it signals AND gate 360. If AND gate 360 receives a signal from both OR gate 336 and comparator 354 indicates that the magnitude of IABT is greater than a threshold, then AND gate 360 signals that the fault type is ABG.
If OR gate 330 receives a signal from either block 324 or block 320, it signals OR gate 332. If OR gate 332 receives a signal from either OR gate 330 or block 312, then it signals AND gate 356. If AND gate 356 receives a signal from both OR gate 332 and comparator 350 indicates that the magnitude of IBCT is greater than a threshold, then AND gate 356 signals that the fault type is BCG.
If step 518 is not satisfied, the method determines in step 526 if the angle difference is greater than 30° but less than or equal to 90°. If step 526 is satisfied, then the method determines whether the magnitude of IACT is greater than a threshold 528. If it is, then the method determines that the fault is ACG 530. Otherwise, the method determines if the magnitude of IBCT is greater than a threshold 532. If it is, the method determines that the fault type is BCG 536. Otherwise, the method ends 534.
If step 526 is not satisfied, the method determines in step 538 if the angle difference is greater than 150° but less than or equal to −150°. If step 538 is satisfied, then the method determines whether the magnitude of IACT is greater than a threshold 540. If it is, then the method determines that the fault is ACG 542. Otherwise, the method determines if the magnitude of IABT is greater than a threshold 544. If it is, the method determines that the fault type is ABG 548. Otherwise, the method ends 546.
If step 538 is not satisfied, the method determines in step 550 if the angle difference is greater than −90° but less than or equal to −30°. If step 550 is satisfied, then the method determines whether the magnitude of IABT is greater than a threshold 552. If it is, then the method determines that the fault is ABG 554. Otherwise, the method determines if the magnitude of IBCT is greater than a threshold 556. If it is, the method determines that the fault type is BCG 560. Otherwise, the method ends 558. If step 550 is not satisfied, then the method ends 562.
As illustrated in
IED 600 includes a communications interface 632 configured to communicate with other IEDs, such as IED 680. IED 680 may be configured to monitor the electric power delivery system at another location thereon. The communications interface 632 may facilitate direct communication with another IED or communicate with another IED over a communications network. Communications interface 632 may facilitate communications with multiple IEDs. IED 600 also may include a time input 640, which may be used to receive a time signal, such that it may include a time-stamp on communications therefrom, and/or it may synchronize sampling with other IEDs. In certain embodiments, a common time reference may be received via communications interface 632, and accordingly, a separate time input would not be necessary. One such embodiment may employ the IEEE 1588 protocol. A monitored equipment interface 646 may be configured to receive status information from, and issue control instructions to a piece of monitored equipment (such as a circuit breaker, conductor, transformer, or the like). For example, when a fault is detected, IED 600 may send a command to a circuit breaker using monitored equipment interface 646. IED 600 may be further configured to send an alarm and/or report detailing the fault type using the communication interface 632.
A computer-readable storage medium 625 may be the repository of a database 628 containing specific electric power line properties or other information. Another computer-readable storage medium 626 may be the repository of various software modules configured to perform any of the methods described herein, such as a fault type selection module 660. The fault type selection module may store computer instructions for determining a fault type on the electric power delivery system. Such instructions may follow the methods described herein. A data bus 642 may link monitored equipment interface 646, time input 640, communications interface 632, and computer-readable storage mediums 625 and 626 to a processor 624.
Computer-readable storage mediums 625 and 626 may be the same medium (i.e., the same disk, the same non-volatile memory device, or the like) or separate mediums as illustrated. Further, the database 628 may be stored in a computer-readable storage medium that is not part of the IED 600, but that is accessible to the processor using, for example, a data bus, a computer network, or the like.
Processor 624 may be configured to process communications received via communications interface 632, time input 640, signal processing 650, and/or monitored equipment interface 646. Processor 624 may operate using any number of processing rates and architectures. Processor 624 may be configured to perform various algorithms and calculations described herein. Processor 624 may be embodied as a general purpose integrated circuit, an application specific integrated circuit, a field-programmable gate array, and other programmable logic devices.
In one embodiment, IED 600 may receive all current signals I from other IEDs that are in communication with the electric power delivery system. According to this embodiment, local and remote current values may be obtained by IEDs such as IEDs 102 and 104 of
While specific embodiments and applications of the disclosure have been illustrated and described, it is to be understood that the disclosure is not limited to the precise configuration and components disclosed herein. Various modifications, changes, and variations apparent to those of skill in the art may be made in the arrangement, operation, and details of the methods and systems of the disclosure without departing from the spirit and scope of the disclosure.
Number | Name | Date | Kind |
---|---|---|---|
3488559 | Souillard | Jan 1970 | A |
3626281 | Souillard | Dec 1971 | A |
4513340 | Drain | Apr 1985 | A |
4670811 | Eda | Jun 1987 | A |
4704653 | Li | Nov 1987 | A |
4795983 | Crockett | Jan 1989 | A |
5140492 | Schweitzer | Aug 1992 | A |
5208545 | Schweitzer | May 1993 | A |
5390067 | Eriksson | Feb 1995 | A |
5455776 | Novosel | Oct 1995 | A |
5515227 | Roberts | May 1996 | A |
5793750 | Schweitzer | Aug 1998 | A |
5796258 | Yang | Aug 1998 | A |
6008971 | Duba | Dec 1999 | A |
6256592 | Roberts | Jul 2001 | B1 |
6496342 | Horvath | Dec 2002 | B1 |
6518767 | Roberts | Feb 2003 | B1 |
6525543 | Roberts et al. | Feb 2003 | B1 |
6590397 | Roberts | Jul 2003 | B2 |
6608742 | Schweitzer | Aug 2003 | B2 |
6650969 | Sieleman | Nov 2003 | B1 |
6697240 | Nelson | Feb 2004 | B2 |
6738719 | Stoupis | May 2004 | B2 |
6760670 | Stoupis | Jul 2004 | B2 |
6839210 | Roberts | Jan 2005 | B2 |
6904549 | Jurisch | Jun 2005 | B2 |
7345488 | Fischer | Mar 2008 | B2 |
7355412 | Cannon | Apr 2008 | B1 |
7400150 | Cannon | Jul 2008 | B2 |
7425778 | Labuschagne | Sep 2008 | B2 |
7660088 | Mooney | Feb 2010 | B2 |
8081002 | Wahlroos | Dec 2011 | B2 |
8183871 | Saha | May 2012 | B2 |
8558551 | Mynam et al. | Oct 2013 | B2 |
8717725 | Labuschagne et al. | May 2014 | B2 |
20060152866 | Benmouyal | Jul 2006 | A1 |
20070035902 | Schweitzer et al. | Feb 2007 | A1 |
20090009180 | Varghai et al. | Jan 2009 | A1 |
20090088989 | Guzman-Casillas | Apr 2009 | A1 |
20090091867 | Guzman-Casillas | Apr 2009 | A1 |
20120053744 | Manson | Mar 2012 | A1 |
20120140365 | Labuschagne | Jun 2012 | A1 |
Number | Date | Country |
---|---|---|
2007032697 | Mar 2007 | WO |
2007110004 | Apr 2007 | WO |
2009010169 | Jan 2009 | WO |
2009136975 | Nov 2009 | WO |
2010006652 | Jan 2010 | WO |
2010148570 | Dec 2010 | WO |
WO2010148570 | Dec 2010 | WO |
Entry |
---|
Edmund O. Schweitzer, III, New Developments in Distance Relay Polarization and Fault Type Selection, Spokane, WA, Oct. 1989. |
Daqing Hou, Normann Fischer, DeterministicHigh-Impedance Fault Detection and Phase Selection on Ungrounded Distribution Systems, Sep. 2005. |
David Costello, Karl Zimmerman, Determining the Faulted Phase, Jul. 2010. |
David Costello, Karl Zimmerman, Effect of Zone 3 Settings on Fault Type Selection in SEL-121F, SEL-121S, SEL-121-0, SEL-221F, SEL-221S, and SEL-221-16 Relays, Sep. 2009. |
Karl Zimmerman, David Costello, Impedance-Based Fault Location Experience, Aug. 2005. |
Demitrios Tziouvaras, Jeff Roberts, Gabriel Benmouyal, New Multi-Ended Fault Location Design for Two- or Three-Terminal Lines, Nov. 2004. |
Number | Date | Country | |
---|---|---|---|
20130088239 A1 | Apr 2013 | US |