This disclosure relates to monitoring and protection of electric power equipment. More particularly, this disclosure relates to monitoring and protection of electric power motors using an intelligent electronic device (IED).
Non-limiting and non-exhaustive embodiments of the disclosure are described, including various embodiments of the disclosure with reference to the figures, in which:
The embodiments of the disclosure will be best understood by reference to the drawings, wherein like parts are designated by like numerals throughout. It will be readily understood that the components of the disclosed embodiments, as generally described and illustrated in the figures herein, could be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the systems and methods of the disclosure is not intended to limit the scope of the disclosure, as claimed, but is merely representative of possible embodiments of the disclosure. In addition, the steps of a method do not necessarily need to be executed in any specific order, or even sequentially, nor need the steps be executed only once, unless otherwise specified.
In some cases, well-known features, structures or operations are not shown or described in detail. Furthermore, the described features, structures, or operations may be combined in any suitable manner in one or more embodiments. It will also be readily understood that the components of the embodiments as generally described and illustrated in the figures herein could be arranged and designed in a wide variety of different configurations.
Several aspects of the embodiments described may be illustrated 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 a memory device and/or transmitted as electronic signals over a system bus or wired or wireless network. A software module or component 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 or component may comprise disparate instructions stored in different locations of a memory device, which together implement the described functionality of the module. Indeed, a module or component 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 or components 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.
Embodiments may be provided as a computer program product including a machine-readable medium having stored thereon instructions that may be used to program a computer (or other electronic device) to perform processes described herein. The machine-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.
Three-phase motors are widely used throughout industry to transform electrical energy to mechanical energy which may be used to perform work. Motors are often necessary pieces of equipment for performing numerous industrial tasks from pumping water to processing materials. Because motors are such an integral part of many industries, loss of use of a motor can cause great delays and loss of income while the motor is off line. Therefore, many motor conditions are monitored. Some of these conditions include, for example, temperatures at various points of the motor (bearing, winding, ambient, etc.), neutral current, phase current, phase voltage, thermal capacity used during start and/or while running, motor start time, starts since last reset, phase current imbalance, negative-sequence current, time to trip, phase-to-phase voltage, impedance during start, starts per hour (or day), and the like.
Monitoring and protection of motors is carefully controlled such that a motor is not taken off line unless it is indeed experiencing a condition that would warrant such action. For example, motor protection schemes meant to interrupt a motor startup due to overheating attempt to determine as accurately as possible the temperature conditions of the rotor. If the schemes are overly conservative, the motor startup would be prematurely stopped, resulting in unnecessary and disruptive downtime. However, if the schemes underestimate the actual temperature conditions, the motor may experience unnecessary and premature harm due to the elevated temperature conditions.
Intelligent electronic devices (IEDs) are often used to monitor various aspects of electric motors and provide protection thereto. Using certain values provided by the motor manufacturer as well as the currents and voltages supplied to the motor, IEDs can be programmed to determine various conditions of the motor and provide protection to the motor by taking the motor off line when certain conditions are determined to be present in the system. For example, the IED may be programmed to determine the temperature of the rotor and take the motor off line if the temperature exceeds a certain value. 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.
As used herein, the term IED may refer to any microprocessor-based device that monitors, controls, automates, and/or protects monitored equipment within the system. Such devices may include, for example, digital fault recorders, phase measurement units (PMUs), phase measurement and control units (PMCUs), phasor data concentrators (PDCs), Supervisory Control and Data Acquisition (SCADA) systems, 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. Furthermore, networking and communication devices may be incorporated in an IED or be in communication with an IED. The term IED may be used interchangeably to describe an individual IED or a system comprising multiple IEDs.
With the various current, voltage, and temperature information, the IED can calculate numerous monitoring values of the IED. Using various settings and static information about the motor, IED 120 can calculate many of the monitoring values. For example, using current and voltage values, the slip and rotor temperature can be calculated (using, for example, the methods described in U.S. Pat. No. 7,675,720). Some additional monitoring values that can be calculated include: temperatures at various points of the motor (bearing, winding, ambient, etc.); neutral current; phase current; phase voltage; thermal capacity used during a start and/or while running; motor start time; starts since last reset; phase current imbalance; negative-sequence current; time to trip; phase-to-phase voltage; impedance during start; and, starts per time (e.g. hour, day).
As mentioned above, because motors may play a central role in various industrial and utility operations, tripping a motor is typically done quite conservatively so as to not interrupt processes. The present disclosure allows a user to set an IED to protect the motor using various monitoring values available and/or calculated within the IED. For example, an alarm based on the values available within the IED may alert a user that a corrective action or other preventative maintenance should be performed such that motor failure is avoided.
IED 120 may be configured to calculate various monitoring values such as those listed above. IED 120 may be further configured to allow a user to set thresholds for a number of the monitoring values, and actions to be taken when the thresholds are breached. Furthermore, IED 120 may be configured to allow a user to set multiple thresholds for a number of the monitoring values, and separate actions to be taken when each of the thresholds are breached. Finally, IED 120 may be configured to allow a user to assign predetermined actions only when a set of thresholds are breached. IED 120 may include a computer programming capability wherein a user can configure such thresholds.
Furthermore, IED 120 may be configured to calculate many of the thresholds based on operation of the motor. For example, IED 120 may be configured to record current, voltage, slip, and temperature during startup. After a predetermined number of successful startups, the IED may use the recorded time-to-start, thermal capacity used, maximum phase current, maximum neutral current, and minimum voltage, for example, to determine thresholds for the monitored time-to-start, thermal capacity used, maximum phase current, maximum neutral current, and minimum voltage. IED 120 may use an average of the recorded values for a particular monitoring value to determine the threshold value. IED 120 may multiply the average by a predetermined number to obtain the threshold for the particular monitoring value. Using the motor startup information to determine the thresholds allows monitoring for changes without extensive data entry for each motor.
As described briefly above, various actions may be taken based on a deviation from or exceeding a threshold for the monitoring values. Actions to be taken may depend on the monitoring value tracked. One action that can be taken is to open a breaker or starter contactor, and trip the motor. Another is to trigger an alarm. Another may be to send a message to a database, a supervisory control and data acquisition system, or a user. Further, the action may include initiating a separate monitoring function. For example, if excessive voltage sags are detected, monitoring of the electric power supply system may be initiated to diagnose broader electrical system problems and prevent motor damage. Excessive start times may be indicative of a broken bar, and may, therefore, cause a broken bar detection algorithm to run on the next startup. Excessive start times may further be indicative of changes in process operation, and may trigger an alarm to ensure that the process operation is functioning correctly.
Table 1 indicates a number of possible monitoring parameters, the types of thresholds associated therewith, and a possible alarm level for each.
The various modules, calculators and/or computer instructions may include a positive-sequence current calculator for calculating positive-sequence current values from the current samples. A positive-sequence voltage calculator may also be included for calculating positive-sequence voltage values from the voltage samples. A resistance calculator may be included for calculating a resistance from the positive-sequence current values and the positive-sequence voltage values as described above. An initial resistance calculator may be included for determining an initial resistance value that is equal to a minimum of the resistance values calculated by the resistance calculator during the predetermined initiation period. The initial resistance calculator may be an initial rotor resistance calculator or an initial stator resistance calculator, as described above. A slip calculator may be included for determining slip values using the initial resistance value and the resistance values, as described above. A rotor resistance calculator may be included for calculating a slip-dependent rotor resistance from the slip values using the methods described herein. The rotor resistance calculator may further calculate positive-sequence rotor resistance values from the slip values and calculate negative-sequence rotor resistance values, as described above. Further, a rotor temperature calculator may be included for calculating a rotor temperature from the current values and the slip-dependent rotor resistance values, using the methods described herein. The rotor temperature calculator may be configured to calculate rotor temperature values from the calculated positive-sequence rotor resistance values, the negative-sequence rotor resistance values, and the current values, using the equations and methods described above. Thus, the IED is capable of monitoring the motor using an accurate value of slip, calculated using a minimum of the resistance values during an initiation period.
The IED 120 further includes a communication device 916 that is capable of receiving commands from the processor 906 and transmitting them to receiving devices such as circuit breakers 910A, 910B, and 910C. If the protection modules operating on the processor 906 call for the motor to be tripped, the processor 906 can send a signal to the communications device 916 which signals circuit breakers 910A, 910B, and 910C to open, thus tripping off the motor.
Further, the communications device 916 may include a transceiver for communicating with a human-machine interface (HMI) 918 such as a computer, a laptop computer, a computer accessed via a network, or the like. Certain inputs such as motor parameters (e.g. full load current (FLA in amps), locked rotor current (LRA in per unit of FLA), locked rotor time (LRTHOT in seconds), locked rotor torque (LRQ in per unit of rated torque), full load slip (FLS in per unit)), thresholds, actions, alarms, other programming commands, and the like may be entered using the HMI and communicated to the processor 906, which may then store the values using the data storage 908.
As described above, the processor may execute modules and/or computer instructions to monitor the motor, take the requisite actions, and report the monitored values and actions taken.
The method then determines a threshold for the monitoring value 608. This may be done by averaging the monitoring value for a predetermined number of successful operations. This may include multiplying the average by a predetermined number. The method then proceeds to compare the monitoring value to the threshold. The monitoring value may be newly received monitoring values from the electric motor. If the monitoring value deviates from the threshold 610, then the method initiates a defined action 612, and may then continue to receive electrical signals representing operating parameters of the motor 614, calculating a monitoring value base on the electrical signals 616, and determining whether the monitoring value deviates from the threshold 610. Otherwise, the method may end.
If, however, the monitoring value does not deviate from the threshold 610, then the method proceeds to receive electrical signals representing operating parameters of the motor 614, calculating a monitoring value base on the electrical signals 616, and determining whether the monitoring value deviates from the threshold 610.
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.
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.
This application claims the benefit under 35 U.S.C. §119(e) of U.S. Provisional Application No. 61/545,031, filed 7 Oct. 2011, naming Mark L. Zeller as inventor, which is hereby incorporated by reference herein in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
4547826 | Premerlani | Oct 1985 | A |
4743818 | Quayle | May 1988 | A |
4914386 | Zocholl | Apr 1990 | A |
4939437 | Farag et al. | Jul 1990 | A |
5086264 | Kelledes | Feb 1992 | A |
5436784 | Schweitzer | Jul 1995 | A |
5448442 | Farag | Sep 1995 | A |
5539601 | Farag | Jul 1996 | A |
5726911 | Canada et al. | Mar 1998 | A |
5793595 | Schweitzer | Aug 1998 | A |
5852351 | Canada et al. | Dec 1998 | A |
6042265 | Kliman | Mar 2000 | A |
6138078 | Canada et al. | Oct 2000 | A |
6199018 | Quist et al. | Mar 2001 | B1 |
6262550 | Kliman et al. | Jul 2001 | B1 |
6297742 | Canada et al. | Oct 2001 | B1 |
6356421 | Guzman-Casillas | Mar 2002 | B1 |
6757146 | Benmouyal | Jun 2004 | B2 |
6900607 | Kleinau et al. | May 2005 | B2 |
6975946 | Al-Hamrani | Dec 2005 | B2 |
7065437 | Mir et al. | Jun 2006 | B2 |
7123457 | Schweitzer | Oct 2006 | B2 |
7141953 | Cohen et al. | Nov 2006 | B2 |
7161778 | Zocholl | Jan 2007 | B2 |
7176650 | Mayes | Feb 2007 | B2 |
7190137 | Lelkes | Mar 2007 | B2 |
7199549 | Kleinau et al. | Apr 2007 | B2 |
7202629 | Jadot et al. | Apr 2007 | B2 |
7576506 | Kleinau et al. | Aug 2009 | B2 |
7586281 | Cohen et al. | Sep 2009 | B2 |
7652444 | Kessler et al. | Jan 2010 | B2 |
7675720 | Zocholl et al. | Mar 2010 | B1 |
7898203 | Davis et al. | Mar 2011 | B2 |
8054609 | Santos | Nov 2011 | B2 |
8080964 | Hudson et al. | Dec 2011 | B2 |
8084984 | Lu et al. | Dec 2011 | B2 |
8232750 | Smugeresky et al. | Jul 2012 | B2 |
8232760 | Lu et al. | Jul 2012 | B2 |
8255200 | Ingraham et al. | Aug 2012 | B2 |
8339093 | Lu et al. | Dec 2012 | B2 |
8484150 | Sparling | Jul 2013 | B2 |
8618761 | Hudson et al. | Dec 2013 | B2 |
20030071594 | Kleinau et al. | Apr 2003 | A1 |
20030076061 | Kleinau et al. | Apr 2003 | A1 |
20030076064 | Kleinau et al. | Apr 2003 | A1 |
20030076065 | Shafer et al. | Apr 2003 | A1 |
20030077179 | Collins et al. | Apr 2003 | A1 |
20040056615 | Jonsson et al. | Mar 2004 | A1 |
20040260488 | Al-Hamrani | Dec 2004 | A1 |
20050029983 | Mijalkovic et al. | Feb 2005 | A1 |
20050043873 | Mir et al. | Feb 2005 | A1 |
20050088137 | Cohen et al. | Apr 2005 | A1 |
20050122642 | Plemmons et al. | Jun 2005 | A1 |
20050151494 | Lelkes | Jul 2005 | A1 |
20060091846 | Mayes | May 2006 | A1 |
20060196265 | Dimino et al. | Sep 2006 | A1 |
20060209480 | Fritsch et al. | Sep 2006 | A1 |
20060232237 | Jadot et al. | Oct 2006 | A1 |
20060250102 | Payne | Nov 2006 | A1 |
20060273753 | Cohen et al. | Dec 2006 | A1 |
20070132446 | Kleinau et al. | Jun 2007 | A1 |
20070182352 | Oxle et al. | Aug 2007 | A1 |
20070182359 | Wahler | Aug 2007 | A1 |
20080017245 | Kessler et al. | Jan 2008 | A1 |
20080018288 | Malrait et al. | Jan 2008 | A1 |
20080266728 | Santos | Oct 2008 | A1 |
20080315811 | Hudson et al. | Dec 2008 | A1 |
20090299720 | Ingraham et al. | Dec 2009 | A1 |
20100007299 | Davis et al. | Jan 2010 | A1 |
20100060227 | Zocholl et al. | Mar 2010 | A1 |
20100156338 | Lu et al. | Jun 2010 | A1 |
20100214709 | Hall et al. | Aug 2010 | A1 |
20100315033 | Lu et al. | Dec 2010 | A1 |
20100315034 | Lu et al. | Dec 2010 | A1 |
20110204829 | Smugeresky et al. | Aug 2011 | A1 |
20110213744 | Sparling | Sep 2011 | A1 |
20110279076 | Hirt | Nov 2011 | A1 |
20120056570 | Hudson et al. | Mar 2012 | A1 |
20120217908 | Wu et al. | Aug 2012 | A1 |
20120280645 | Olsson et al. | Nov 2012 | A1 |
20130107400 | Meng | May 2013 | A1 |
Entry |
---|
Stanley E. Zocholl, Schweitzer Engineering Laboratories, Inc.—Tutorial: From Steinmetz Model to the Protection of High Inertia Drives, Oct. 2006. |
E.O. Schweitzer, III, S.E. Zocholl, Aspects of Overcurrent Protection for Feeders and Motors, May 1994. |
Stanley E. Zocholl, Comparing Motor Thermal Models, 2003. |
Patrick Whatley, Mark Lanier, Lee Underwood, Stan Zocholl, Enhanced Motor Protection with the Slip-Dependent Thermal Model: A Case Study, Sep. 12, 2007. |
S.E. Zocholl, Induction Motors: Part I—Analysis, 1996. |
S.E. Zocholl, Induction Motors: Part II—Protection, 1996. |
Stanley E. Zocholl, Optimizing Motor Thermal Models, Apr. 24, 2006. |
Stanley E. Zocholl, Armando Guzman-Casillas, Thermal Models in Power System Protection, 1999. |
S.E. Zocholl, Understanding Service Factor, Thermal Models, and Overloads, Oct. 2005. |
S.E. Zocholl, Gabriel Benmouyal, Using Thermal Limit Curves to Define Thermal Models of Induction Motors, Oct. 2001. |
Ed Lebenhaft, Field Evaluation of Slip-Dependent Thermal Model for Motors with High-Inertia Starting, May 2007. |
Ed Lebenhaft, Mark Zeller, Estimating Key Parameters for Protection of Undocumented AC Motors, Mar. 18, 2008. |
Ed Lebenhaft, Mark Zeller, Advanced Thermal Motor Protection Using Digital Relays, Oct. 6, 2008. |
Number | Date | Country | |
---|---|---|---|
20130088799 A1 | Apr 2013 | US |
Number | Date | Country | |
---|---|---|---|
61545031 | Oct 2011 | US |