This disclosure relates to minimizing circulating current and, in particular, to minimizing circulating current using time-aligned data.
Additional aspects and advantages will be apparent from the following detailed description of preferred embodiments, which proceeds with reference to the accompanying drawings.
Power transformers used in electrical power systems typically include multiple taps, which may allow for the dynamic selection of the voltage ratio provided thereby. Changing taps on a power transformer may allow a power engineer to regulate the voltage profile of a power system (e.g., in response to changes in demand on the power system, in response to fault conditions, and so on). For example, a transformer tap change may be performed in order to maintain the system voltage of the power system within predefined bounds (e.g., maintain the system voltage within an upper and lower band).
A power system may include multiple power transformers operating in parallel. The power transformers may be located at the same or different substations, and may be connected via a buses or transmission lines. A voltage differential may exist between two or more of the parallel transformers, which may cause a circulating current to flow therebetween. In some embodiments, the transformer voltage differential may be caused by differences in the transformers (e.g., different winding configurations, turn ratios, tap settings, impedance, etc.), different transformer tap settings, operating conditions in the electrical power system, or the like. The circulating current may adversely affect the performance of the power system (e.g., result in power losses, cause transformer overheating, disrupt power transmission, etc.). The circulating current (ICIRC) flowing between two parallel transformers may be expressed as follows:
In Equation 1, ICIRC represents the circulating current, ΔV represents the voltage differential between the transformers, and ZT represents a sum of the transformer impedances.
As discussed above, a tap change operation may be performed in order to, inter alia, maintain the power system voltage within upper and lower band settings. In addition, a tap change operation under the teachings of this disclosure may comprise configuring two or more parallel transformers to maintain system voltage levels at acceptable levels while minimizing circulating current flowing therebetween.
When a tap change operation is performed, the operation may be adapted to minimize the voltage differential ΔV 108 to thereby minimize the circulating current ICIRC 114. Adapting a tap change operation may comprise selecting which transformer(s) 110 and/or 112 to configure to adjust the system voltage to an appropriate level while minimizing circulating current ICIRC 114. For example, if the transformer 110 is operating at a higher voltage than transformer 112, and the tap change operation requires lowering the system voltage (voltage on node 106), the tap change command 162 may be configured to decrease the tap setting of transformer 110, since this will lower the system voltage and decrease the voltage differential ΔV 108, whereas, although a tap change to decrease the tap setting of transformer 112 would decrease the system voltage, it will have the negative effect of increasing the voltage differential ΔV 108 (and hence the circulating current ICIRC 114). Likewise, if the tap change operation requires raising the system voltage, a tap change command 162 configured to increase the tap setting of transformer 112 would increase the system voltage while reducing the voltage differential ΔV 108 (as opposed to a tap increase on the transformer 110, which would increase the system voltage, but increase the voltage differential ΔV 108).
It has been observed that the phase angle of the current at the transformer from which the circulating current flows lags the phase angle of the current of the other transformer. Therefore, in the
The angular difference between the transformers may be calculated as follows:
ADIF=∠I1−∠I2 Eq. 2
In Equation 2, ADIF represents the angular difference between the phase angle of the current of a first transformer ∠1 (e.g., angle of current 111) and the phase angle of the current of a second transformer ∠2 (e.g., angle of current 113). If the angle difference (ADIF) is greater than zero, the current phasor of the first current (e.g., current 111) leads the current phasor of the second current (e.g., current 113), and if angle difference is negative, the current phasor of the second current (e.g., current 113) leads the phasor of the first current (e.g., current 111). A tap change command may be generated based on the bias (e.g., phase angle lag/lead) information obtained using Equation 2.
In the
The IEDs 120 and 122 may be configured to transmit the current phasor measurements to the IED 124, which may comprise a data processing module 160. As will be discussed below, the data processing module 160 may be configured to time-align the current phasor measurements, calculate an angular difference therebetween, and to generate tap change commands adapted to modify the system voltage while minimizing the circulating current ICIRC 114 flowing in the system 100 using the angular difference. Accordingly, the data processor 160 and/or the IED 124 may be communicatively coupled to the transformers 110 and 112 and may be capable of configuring the transformers 110 and 112 via, inter alia, tap change commands 162.
The current phasor measurements obtained by the IEDs 120 and 122 may be transmitted to the data processor 160 via respective communications channels 121 and 123. The communication channels 121 and 123 may each introduce a communication delay due to, inter alia, the communications protocol implemented on the channels 121 and 123, traffic on the channels 121 and 123, the distance between the IEDs 120 and 122 and the data processor 160, and so on. In some cases, the communication delay of the channels 121 and/or 123 may be variable.
In order to, inter alia, compensate for communication delay, the measurement data transmitted by the IEDs 120 and 122 may include a time stamp and/or be associated with information configured to allow the data processor 160 to time-align the measurements (e.g., time align measurement data received from the IED 120 to measurements received from the IED 122). The IEDs 120 and/or 122 may include time-stamp information associated with the measurements. In some embodiments, the IEDs 120 and 122 may be configured to communicate measurement data as synchrophasors according to the IEEE C37.118-2005 standard. However, the disclosure is not limited in this regard, and any time-alignment technique and/or mechanism known in the art could be used under the teachings of this disclosure. Additional examples of such are disclosed in: U.S. Pat. No. 6,662,124 entitled, “Protective Relay with Synchronized Phasor Measurement Capability for Use in Electric Power Systems,” to Schweitzer, III et al.; U.S. Pat. No. 6,845,333 entitled, “Protective Relay with Synchronized Phasor Measurement Capability for Use in Electric Power Systems,” to Anderson et al.; and U.S. Application Pub. No. 2007/0086134 entitled, “Apparatus and Method for Estimating Synchronized Phasors at Predetermined Times Referenced to an Absolute Time Standard in an Electrical System” to Zweigle et al., each of which is hereby incorporated by reference in its entirety.
In some embodiments, the IEDs 120 and 122 may be synchronized to a common time reference 170, which may be provided by: a Global Positioning System (GPS); a radio time source, such as the short-wave WWV transmitter operated by the National Institute of Standards and Technology (NIST) at 2.5 MHz, 5 MHz, 10 MHz, 15 MHz, and 20 MHz, or a low frequency transmitter, such as WWVB operated by NIST at 60 Hz; a cesium clock; an atomic clock; an IEEE-1588 time-over-Ethernet system; or the like. Alternatively, or in addition, a common time reference signal may be provided by the communication channels 121 and/or 123 communicatively coupling the IEDs 120, 122, and 124.
Although
The IED 126 comprises the data processor 160, which, as discussed above, may be configured to use the time-aligned current phasor measurements to generate tap change commands 162 adapted to minimize the circulating current ICIRC 114 flowing in the system 100 while maintaining the system voltage within upper and lower bounds.
The data processor 160 of
As shown in
At step 210, the method 200 may start and be initialized, which may comprise loading one or more computer-readable instructions from a computer-readable storage medium, accessing one or more communications interfaces, accessing one or more measurement devices (e.g., current transformers, IEDs, PMUs, or the like), accessing a common time reference, and so on. The instructions comprising the method 200 may be embodied as one or more discrete software modules stored on a computer-readable storage medium (e.g., disc, optical storage media, file system, network attached storage, or the like). Certain of the instructions and/or steps of the method 200 may be implemented as hardware components, such as digital logic components, analog circuits, or the like. Moreover, one or more of the instructions may be adapted to interface with particular hardware components, such as communications interfaces, measurement devices, or the like. Therefore, one or more of the steps of the method 200 may comprise and/or be tied to particular machine components.
At step 220, the system 200 may determine whether the system voltage needs to be modified (e.g., raised or lowered) in order to maintain the voltage within upper and lower bounds. The determination of step 220 may be made by comparing a system voltage measurement to upper and lower voltage bounds. Alternatively, the method 200 may be communicatively coupled to another device or method, which may be configured to monitor the system voltage. The device or method may cause the method 200 to perform a tap change operation when it determines that a modification of the system voltage is required. If the system voltage is to be modified, the flow may continue to step 230; otherwise, the flow may end at step 260 until the process is initiated upon the next processing interval.
At step 230, an angle difference between currents of the parallel transformers may be determined. The angle difference may be calculated per Equation 2, using time-aligned current phasor measurements obtained at each of the parallel transformers in the electrical power system (e.g., transformers 110 and 112 of
Calculating the angle difference at step 230 may further comprise applying one or more correction factors to the measurement data (according to a topology of the power system, properties of the measurement device(s) used to acquire the measurements, or the like), filtering the measurements, refining the measurements, applying one or more measurement checks (e.g., a KCL check), and so on.
At step 240, a bias of the transformers may be determined. The bias may be indicative of which transformer lags the other (e.g., which current lags the other). The bias may be determined using the sign of the angle difference as described above.
At step 250, a tap change command may be generated according to the bias determined at step 240. The tap change command may be adapted to modify the system voltage (e.g., raise or lower the system voltage), while minimizing circulating current between the transformers as described above.
At step 320, the method 300 may determine whether the system voltage is to be raised in order to be maintained at an acceptable level (e.g., above a lower bound). The determination of step 320 may be made by comparing a voltage level of the system (e.g., voltage level on Node 106 of
At step 321, the method 300 may determine whether the system voltage is to be lowered in order to be maintained at an acceptable level (e.g., lower than an upper bound). The determination of step 320 may be made as described above (e.g., by comparing a voltage level measured in the power system to an upper bound). If at step 321, the voltage level is to be lowered, the flow may continue to step 331; otherwise, the flow may go to the end 370.
In some embodiments, steps 320 and 321 may be implemented by another device or method (e.g., implemented by a protective relay or other monitoring device), which may be configured to provide protective or other monitoring services to the power system, including maintaining the system voltage within upper and lower bounds. The device or method may monitor the system voltage and, upon detecting the system voltage nearing the upper or lower bounds, may cause the method 300 to perform step 330 or 331.
At steps 330 and 331, the angle difference between the first and the second parallel transformers may be calculated as described above in conjunction with
Calculating the angle difference at steps 330 and 331 may comprise receiving and time-aligning current phasor measurements of the first and the second transformers at step 322. The current phasor measurements may have been acquired by respective IEDs, a first IED to measure a current of the first transformer (e.g., using a first current transformer), and a second IED to measure a current of the second transformer (e.g., using a second current transformer). The phasor measurements acquired by the first and the second IEDs may be transmitted to the method 300 using a communication channel. The IEDs may be configured to include time-alignment information with the measurements, such as time-stamp information. In some embodiments, the measurements may comprise synchrophasors per the IEEE C37.118-2005 standard. Alternatively, or in addition, the measurements may include time-alignment information in another form (e.g., include a time stamp with each measurement, include a time offset parameter, tie the measurements to a common time reference, or the like). In some embodiments, the IEDs and/or the method 300 may be communicatively coupled to a common time reference (e.g., GPS time, radio, etc.), to which the measurements may be synchronized. Alternatively, or in addition, the communications channel through which the measurements are transmitted to the method 300 may provide for time synchronization (e.g., may time-stamp messages, etc.).
At step 322, the current phasor measurements may be time aligned to one another. The time alignment may allow for the angle difference to be calculated correctly. In addition, at step 322 (or steps 330 and 331), the current phasor measurements may be corrected (for differences in measuring devices, orientation, etc.), filtered, verified (e.g., using a KCL or other check), and/or refined as described above. The time-aligned current phasor measurements may then be supplied to steps 330 and/or 331 where the angle difference may be calculated as described above.
Following the calculating of the angle difference at step 330 (using the time-aligned phasor measurements), the flow may continue to step 340, where the bias between the first and the second transformers may be determined (e.g., the direction of the circulating current (if any) may be determined). If, at step 340, angle difference is not greater than zero, the flow may continue to step 350; otherwise, if angle difference is greater than zero, the flow may continue to step 352.
At step 350, a tap change command may be generated to modify the tap setting of the second transformer to generate a higher voltage, which is typically done by configuring the transformer to use a higher tap setting. Accordingly, at step 350, a tap change command to increase the tap setting of the second transformer may be generated.
At step 352, a tap change command may be generated to modify the tap setting of the first transformer to generate a higher voltage. As described above, this generally comprises a command to cause the first transformer to use a higher tap setting.
Although not depicted in
Following the generation of the tap change command at step 350 or 352, the flow may continue to step 360. At step 360, a tap change command may be transmitted to the first or the second transformer. In some embodiments, the transmission of the tap change command may be performed by another device or process (e.g., an IED, protective relay, PMCU, or the like), which may be configured to communicate with and/or control the first and the second transformers. Alternatively, or in addition, the tap change command may be transmitted by the method 300. After the tap change command is generated and/or transmitted, the flow may end at step 370. Alternatively, at step 370, the program sequence may start again at the next processing interval. In addition, the method 300 may continue receiving current measurements from the first and the second transformers at step 322, calculating the angle difference and bias, and the like so as to be able to respond quickly to a tap change request.
Referring back to step 331, in which the system voltage is to be lowered, after angle difference is calculated at step 341 (using the time-aligned current measurements acquired at step 322), the flow continues to step 341.
At step 341, the method 300 determines the bias between the first and the second transformers using the angle difference and generates a tap change command adapted to lower the system voltage while minimizing circulating current. If the angle difference is greater than zero, the flow may continue to step 351, where the second transformer may be configured to generate a lower voltage. Since lowering the transformer tap setting typically lowers the transformer voltage, the tap change command generated at step 351 may be configured to cause the second transformer to use a lower tap setting. If the angle difference is not greater than zero, the flow may continue to step 353, where a tap change command may be generated to configure the first transformer to generate a lower voltage (e.g., the first transformer may be configured to use a lower tap setting).
Following step 351 or 353, the flow may continue to steps 360 and 370, where the tap change command generated at step 351 or 353 may be transmitted to the first or the second transformer, and the method 300 may end as described above.
The device 400 of
The device 400 may be communicatively coupled to a first IED 420 and a second IED 422 via a communications interface 430 to receive current phasor measurements therefrom. The current phasor measurements from the first IED 420 may correspond to the current of the first transformer 410, and the measurements from the second IED 422 may correspond to the current of the second transformer 412. The communications interface 430 may be configured to communicate with the IEDs 420 and 422 using any number of different communications protocols, including, but not limited to: IEEE C37.118-2005, IEEE 1344, BPA PDCStream, IEC 61850, OPC-DA/OPC-HAD, Internet Protocol (IP), Transmission Control Protocol (TCP), TPC/IP, User Datagram Protocol (UDP), or the like. The current phasor measurements transmitted to the device 400 by the IEDs 420 and 422 may include time-alignment information (e.g., time stamps with the measurements, as part of the communications channels' communication protocol and/or infrastructure, or the like). In some embodiments, the measurements may comprise synchrophasors (e.g. per IEEE C37.118-2005).
The current phasor measurements from the IEDs 420 and 422 may be time-aligned to one another by a time alignment module 432. The time-alignment may be performed using time-alignment information associated with the measurements, using a time-alignment system provided by the communications channel, according to IEEE C37.118-2005, using a buffer, or the like. In some embodiments, the IEDs 420 and 422 may be synchronized to a common time reference (not shown), such as the common time reference 170 described above in conjunction with
The time-aligned current phasor measurements may flow to a tap change control module 461, which may be configured to generate tap change commands adapted to modify system voltage levels while minimizing circulating current between the first and the second transformers 410 and 412 as described above (e.g., by calculating an angle difference between the currents of the transformers 410 and 412, determining a bias therebetween (based on the sign of the angle difference), and selecting an appropriate tap change accordingly).
In some embodiments, the device 400 may perform tap change operations responsive to a tap change command received from an external device (not shown), such as a protective relay, PMCU, or the like. The tap change commands may be received via the communications interface 430, and may be transmitted to the device 400 responsive to the external device detecting the system voltage falling below a lower voltage bound or exceeding an upper voltage bound.
Alternatively, or in addition, the device 400 may be configured to determine when tap change operations are needed (e.g., by comparing a system voltage to predefined upper and lower voltage bounds). In the
After determining the tap change operation to perform (based on the angle difference and bias determined using the time-aligned current phasor measurements), a tap change command 462 is generated. In some embodiments, the tap change command 462 may be transmitted to one of the transformers 410 or 412 by a local PMCU 465 and/or using the communications interface 430. Alternatively, or in addition, the tap change command 462 may be generated and/or transmitted by another module and/or device (not shown), such as another IED, protective relay, PMCU, or the like.
The operation of the device 400 may be managed using a human-machine-interface 475. HMI 475 may include a display, input/output devices, and the like. Through HMI 475, a human operator may configure various parameters of the device 400, such as the upper and lower bounds of the system voltage, sensitivity thresholds, communications protocols, system configuration, topology information, correction factors, and the like.
The above description provides numerous specific details for a thorough understanding of the embodiments described herein. However, those of skill in the art will recognize that one or more of the specific details may be omitted, or other methods, components, or materials may be used. In some cases, operations are not shown or described in detail.
Furthermore, the described features, operations, or characteristics may be combined in any suitable manner in one or more embodiments. It will also be readily understood that the order of the steps or actions of the methods described in connection with the embodiments disclosed may be changed as would be apparent to those skilled in the art. Thus, any order in the drawings or Detailed Description is for illustrative purposes only and is not meant to imply a required order, unless specified to require an order.
Embodiments may include various steps, which may be embodied in machine-executable instructions to be executed by a general-purpose or special-purpose computer (or other electronic device). Alternatively, the steps may be performed by hardware components that include specific logic for performing the steps, or by a combination of hardware, software, and/or firmware.
Embodiments may also be provided as a computer program product including a computer-readable medium having stored instructions thereon that may be used to program a computer (or other electronic device) to perform processes described herein. The computer-readable medium may include, but is not limited to: hard drives, floppy diskettes, optical disks, CD-ROMs, DVD-ROMs, ROMs, RAMs, EPROMs, EEPROMs, magnetic or optical cards, solid-state memory devices, or other types of media/machine-readable medium suitable for storing electronic instructions.
As used herein, a software module or component may include any type of computer instruction or computer executable code located within a memory device and/or 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 perform 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 memory device, 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 memory devices. 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 memory storage devices. In addition, data being tied or rendered together in a database record may be resident in the same memory device, or across several memory devices, and may be linked together in fields of a record in a database across a network.
It will be understood by those having skill in the art that many changes may be made to the details of the above-described embodiments without departing from the underlying principles of the disclosure.
This Application is a continuation-in-part of U.S. patent application Ser. No. 12/239,678, filed Sep. 26, 2008, now U.S. Pat. No. 7,856,327, and entitled “State and Topology Processor,” which claims priority to U.S. Provisional Application No. 60/978,711, entitled “Real Time State and Topology Processor” filed Oct. 9, 2007, both of which are hereby incorporated by reference in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
4387336 | Joy | Jun 1983 | A |
4829298 | Fernandes | May 1989 | A |
5006846 | Granville | Apr 1991 | A |
5224011 | Yalla | Jun 1993 | A |
5271572 | Grandi | Dec 1993 | A |
5315527 | Beckwith | May 1994 | A |
5341265 | Westrom | Aug 1994 | A |
5422561 | Williams | Jun 1995 | A |
5446682 | Janke | Aug 1995 | A |
5498954 | Bassett | Mar 1996 | A |
5498956 | Kinney | Mar 1996 | A |
5530338 | Beckwith | Jun 1996 | A |
5541498 | Beckwith | Jul 1996 | A |
5544064 | Beckwith | Aug 1996 | A |
5550459 | Laplace | Aug 1996 | A |
5550460 | Bellin | Aug 1996 | A |
5581173 | Yalla | Dec 1996 | A |
5592393 | Yalla | Jan 1997 | A |
5646512 | Beckwith | Jul 1997 | A |
5680324 | Schweitzer, III | Oct 1997 | A |
5694281 | Roberts | Dec 1997 | A |
5699219 | Arita | Dec 1997 | A |
5703745 | Roberts | Dec 1997 | A |
5731943 | Roberts | Mar 1998 | A |
5793750 | Schweitzer, III | Aug 1998 | A |
5821716 | Okanik | Oct 1998 | A |
5963404 | Guzman-Casillas et al. | Oct 1999 | A |
6028754 | Guzman-Casillas | Feb 2000 | A |
6236949 | Hart | May 2001 | B1 |
6265881 | Meliopoulos | Jul 2001 | B1 |
6313614 | Persson | Nov 2001 | B1 |
6341055 | Guzman-Casillas | Jan 2002 | B1 |
6356421 | Guzman-Casillas | Mar 2002 | B1 |
6411865 | Qin | Jun 2002 | B1 |
6442010 | Kasztenny | Aug 2002 | B1 |
6446682 | Viken | Sep 2002 | B1 |
6603298 | Guzman-Casillas | Aug 2003 | B2 |
6608742 | Schweitzer, III | Aug 2003 | B2 |
6662124 | Schweitzer, III | Dec 2003 | B2 |
6757146 | Benmouyal | Jun 2004 | B2 |
6839210 | Roberts | Jan 2005 | B2 |
6845333 | Anderson | Jan 2005 | B2 |
6946753 | Kernahan | Sep 2005 | B2 |
7027896 | Thompson | Apr 2006 | B2 |
7196884 | Guzman-Casillas | Mar 2007 | B2 |
7319576 | Thompson | Jan 2008 | B2 |
7323852 | Hoffman | Jan 2008 | B2 |
7355369 | Lavieville | Apr 2008 | B2 |
7425778 | Labuschagne | Sep 2008 | B2 |
7463467 | Lee | Dec 2008 | B2 |
7480580 | Zweigle | Jan 2009 | B2 |
7504806 | Labuschagne | Mar 2009 | B2 |
7570469 | Guzman-Casillas | Aug 2009 | B2 |
7582986 | Folkers | Sep 2009 | B2 |
7595614 | Stich | Sep 2009 | B2 |
7630863 | Zweigle | Dec 2009 | B2 |
7642736 | Genkawa | Jan 2010 | B2 |
7660088 | Benmouyal et al. | Feb 2010 | B2 |
7710693 | Guzman-Casillas | May 2010 | B2 |
20040027748 | Kojovic | Feb 2004 | A1 |
20040059469 | Hart | Mar 2004 | A1 |
20050280965 | Lee | Dec 2005 | A1 |
20060193099 | Schweitzer | Aug 2006 | A1 |
20060224336 | Petras | Oct 2006 | A1 |
20070086134 | Zweigle | Apr 2007 | A1 |
20070090811 | Labuschagne | Apr 2007 | A1 |
20080071482 | Zweigle | Mar 2008 | A1 |
20080088466 | Labuschagne | Apr 2008 | A1 |
20080281540 | Zweigle | Nov 2008 | A1 |
20090085407 | Venkatasubramanian | Apr 2009 | A1 |
20090088989 | Guzman-Casillas | Apr 2009 | A1 |
20090088990 | Schweitzer, III | Apr 2009 | A1 |
20090089608 | Guzman-Casillas | Apr 2009 | A1 |
20090091867 | Guzman-Casillas | Apr 2009 | A1 |
20090099798 | Gong | Apr 2009 | A1 |
20090125158 | Schweitzer, III | May 2009 | A1 |
20090134854 | Labuschagne | May 2009 | A1 |
20090231769 | Fischer | Sep 2009 | A1 |
20100002348 | Donolo | Jan 2010 | A1 |
20100114390 | Stevenson | May 2010 | A1 |
Number | Date | Country | |
---|---|---|---|
20100125373 A1 | May 2010 | US |
Number | Date | Country | |
---|---|---|---|
60978711 | Oct 2007 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12239678 | Sep 2008 | US |
Child | 12695778 | US |