The present invention is related to co-pending applications assigned to the assignee of the present invention and entitled “Load Control Receiver with Line Under Voltage and Line Under Frequency Detection and Load Shedding”, filed Feb. 25, 2004, Ser. No. 10/786,628, and “Utility Load Control Management Protocol”, filed Aug. 20, 2003, Ser. No. 60/496,532, the disclosures of which are hereby incorporated by reference.
Generally, the present invention relates to a system and a method for providing a response to electric distribution power delivery disturbances related to under frequency events. In particular, load shedding close to the local disturbance is provided as it relates to under frequency events.
Disturbances in the delivery of power to end user equipment are presently quite common. These disturbances may be brownout disturbances in which low power levels are delivered, or complete blackout situations in which no power is delivered. These disturbances occur for a variety of reasons but are frequently related to high demand situations (i.e., hot summer days when air conditioners and other end user equipment are run at peak levels) or delivery system equipment maintenance or failure.
Such disturbances that result in brownout or blackout situations can cause damage to end user equipment when voltage levels delivered to the equipment fall below required levels. This damage can cost end users a significant amount of money to either repair or replace the damaged equipment. Additionally, brownout or blackout situations cost utilities money and their own delivery system equipment may be damaged, requiring repair or replacement. Further, an isolated disturbance can affect a large number of end users if an entire subsystem load must be shed in response to the disturbance.
Some disturbances result in under voltage or under frequency events. An under voltage event occurs when a voltage level drops below a minimum or rated value. For example, electric consumer devices are frequently rated at 120 volts. While such devices may continue to operate uninterruptedly at values slightly below the rated voltage, the devices may be damaged or destroyed if the voltage delivered drops significantly, for example to 90 volts. Similarly, an under frequency event occurs when the frequency of a signal drops below a minimum or rated value. If an electronic device operates at a 60 Hertz signal, damage or destruction of the device may occur if the frequency drops to, for example, 40 Hertz. Some examples of systems that detect undervoltage and underfrequency conditions are disclosed and described in U.S. Pat. No. 3,993,984 to Penrod issued on Nov. 23, 1976, which is herein incorporated by reference. Consumers currently have no adequate way of protecting their equipment during under voltage or under frequency events.
Presently, systems exist in which utilities monitor and control end user equipment remotely to control load levels. These systems, however, are controlled by the utility and are primarily only used in peak demand situations. These systems typically do not operate to protect end user equipment in non-peak demand situations. Further, present systems may not provide a sufficiently rapid response to decreasing power delivery levels to protect end user equipment from damage; it may take a utility control center operator several minutes or more to respond to a system disturbance. Additionally, present systems may not operate to automatically shed load in under voltage or under frequency conditions to aid a utility in bringing the voltage or frequency back up to standard. One prior art system proposes to initiate load shedding via demand load control of air conditioning compressors and the like by lowering the frequency output at the utility thereby tripping frequency-sensitive switches located close to the load. For further details on such a system, reference is made to U.S. Pat. No. 5,687,139 to Budney issued Nov. 11, 1997, which is incorporated herein by reference.
There is a need in the industry for an apparatus or device that protects a consumer's end user equipment from electric distribution power delivery disturbances, primarily under frequency events, is located internally in end user equipment, and is automatic in its response, thereby substantially reducing the need for utilities to directly monitor end user equipment in instances of frequency drop offs.
The disturbance response apparatus of the present invention substantially meets the aforementioned needs of the industry. In one example embodiment, the disturbance response device of the present invention comprises a thermostat-type device that makes intelligent decisions that are local to the frequency disturbance to disconnect the end user in response to an under-frequency event in an electrical distribution system. Further, the apparatus of the present invention is able to respond quickly and efficiently to frequency disturbances, minimizing the overall impact of each disturbance on the equipment and helping a utility to bring the frequency or voltage back up to standard.
According to one example embodiment of the present invention, a line under frequency (LUF) detection and load shedding system and method measures the time period of each power line cycle and then compares the measured time period to a configurable (or utility-settable) trigger period. If the cycle time period (or length) is greater than or equal to the trigger period, a counter is incremented. If the cycle time period is less than the trigger period, the counter is decremented. If the counter is incremented to a counter trigger, an under-frequency condition is detected and the LUF response is implemented. The LUF response may be a command to control load but may also be some other command or commands that fit within the allocated space in the firmware. When the frequency rises above a restore value, an under-frequency counter begins to count down; when the under frequency counter reaches zero, an out response is initiated. This out response is typically to restore all loads, but it may also be some other command or commands that fit within the allocated space in the firmware.
According to another example embodiment of the present invention, an under frequency protection thermostat-type device is disclosed that includes a thermostat-type housing with a transformer adapted to be electrically connected to a primary voltage source having a predefined frequency level that is disposed within the housing. A line under frequency (LUF) detection and measurement module electrically connected to the transformer is adapted to detect a line under frequency condition from a signal received from the transformer. A microcontroller connected to the LUF detection and measurement module is adapted to send a command to disengage and engage an electrical load as a function of a measured frequency of the voltage source over a predefined period of time, wherein the measured frequency is compared to a predefined frequency threshold. A load switch connected to the microcontroller is adapted to respond to a command from the microcontroller to disengage and engage an electrical load from the voltage source.
According to yet another example embodiment of the present invention, a line under frequency detection system includes a microcontroller that is adapted to send a command to disengage and engage an electrical load as a function of a measured frequency of a voltage source over a predefined time period, wherein the measured frequency is compared to a predefined frequency threshold. The detection system also includes a level shift and limit module connected to the microcontroller and to the voltage source and a first memory arrangement adapted to provide a trigger period and a restore period that is connected to a comparator module within the microcontroller. The detection system further includes a crystal oscillator connected to the comparator module, wherein the comparator module is adapted to compare the time period to the trigger period for decreasing measured frequency and to a restore period for an increasing measured frequency. A second memory arrangement is also included in the detection system that is adapted to provide an under frequency count value to an under frequency counter within the microcontroller.
The invention may be more completely understood in consideration of the following detailed description of various embodiments of the invention in connection with the accompanying drawings, in which:
While the invention is amenable to various modifications and alternative forms, specifics thereof have been shown by way of example in the drawings and will be described in detail. It should be understood, however, that the intention is not to limit the invention to the particular embodiments described. On the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the invention as defined by the appended claims.
The disturbance response system of the present invention includes a line under voltage (LUV) system included within an end user climate control system. The LUV system enables a quick and efficient response to delivery system disturbances by identifying under voltage events. While the present invention is not necessarily limited to such an application, the invention will be better appreciated using a discussion of example embodiments in such a specific context.
Referring now to
When a power-fail event occurs, the LUV system operates to make intelligent decisions, local to the disturbance, to disconnect the furnace or compressor to avoid damage to the units, and to shed load to help a utility bring the voltage back up to standard system-wide. In this example embodiment, the LUV/LUF system operates within the climate control system, to disconnect the heating or cooling units of the climate control system. Frequently the devices shed will be lower priority, higher consumption end user devices such as air conditioners and water heaters. The predetermined device can be a single electrical load, such as a single air conditioner in a home or a single transformer in a power distribution network, or any combination of a plurality of electrical loads such as in a home or in a power distribution network. When the voltage level increases to an acceptable level, the LUV/LUF modified load control receiver re-engages the heating or cooling units.
Referring back to
Referring now to
Detection of Power Failure
If the line voltage drops below 80% of nominal line voltage, the microprocessor prepares itself for a perceived outage. To protect the microprocessor from line voltage oscillation, microprocessor start-up occurs when line voltage reaches 85% of nominal line voltage. When a power fail is detected, critical counters are immediately saved to EEPROM (indicated as 312) and a CRC is calculated over the entire protected RAM. At below threshold 310, the device ceases to function, as indicated as point 314. Subsequently, if the line voltage is normal (i.e. a glitch occurred), then normal operation is resumed. If the line voltage is not normal (but the processor is still running) then this is a brownout state. The error LEDS report the brownout. When the brownout finishes, and normal voltage returns, the processor will then be reset.
Power fail is detected by sampling the power supply with an analog to digital converter. The line is sampled every 2 ms; the sampled value is called the Power Reading with a value in the range of 00-FF. If the Power Reading is less than Power Fail Level (discussed below) then it is considered a power failure. The Power Fail Level parameter should be configured to be at 80% of nominal line voltage. The Power Fail Level is the power fail reading that will cause the power fail routines to be activated (1 byte). For this parameter, the ExpressCom Configuration Command Code is 3A (Hex). A value of 00h or FFh disables powerfail detection (this should only be used by an unprogrammed EEPROM in manufacture).
The power fail state is exited, and normal operation resumed, when the Power Reading rises above the combined Power Fail Level+Power Fail Hysteresis level (discussed below). The combined value should be configured to be at 85% of nominal line voltage. The lowest Power Reading sampled (since its last reset) is displayed in the serial data stream. The Power Reading is dependent both on the input AC voltage and on the number and type of relays that are controlled. The Power Fail Hysteresis level is reached when the power fail reading rises above the combined Power Fail Level+Power Fail Hysteresis, at which time the device can exit power failed mode. The ExpressCom Configuration Command Code for this threshold is 3A (Hex).
For a printed circuit board with a single 5A relay, which is controlled, the power readings at various voltages are:
In operation, a power-fail is detected by sampling the power supply with an analog-to-digital converter every two milliseconds to obtain a power reading. When it reaches a trigger level and stays below the trigger level for the specified amount of time, an under-voltage response is triggered. This under-voltage response is typically a command to control load but may be any command or commands that fit in the allocated space in the firmware. If a power reading is below the specified power fail level, it is considered a power failure and the power-fail routines of the LUV system are activated. When it reaches the power-fail level and stays below the power-fail level for the specified amount of time, a brownout LED pattern is displayed.
As depicted in
Undervoltage Detection Parameters
Because the LUV system uses firmware rather than hardware to detect powerfail, the powerfail points are configurable. In a preferred embodiment, the under voltage feature is enabled with a single 5A relay. This will provide sufficient response time for the microprocessor to manage powerfails. In this example embodiment, the operating voltage is indicated as 354, the UV restore is indicated as 356, the UV trigger is indicated as 358, the combination of the powerfail and hysteresis voltage is indicated as 360, the Vpowerfail is indicated as 362 and is set at about 60% to provide for a sufficient response time while Vrestore is set at about 70% for the recovering part of curve 352. As the voltage source quality begins to drop (as indicated in curve 352), at point 366 after the UV time period has elapsed, the UV in response mode begins, wherein the load is controlled. As the voltage source continues to deteriorate (further along curve 352), at point 368, the brownout LED pattern is displayed, indicating that the voltage level is well below the powerfail voltage level of 60% and the system is about to transition to a totally inactive state. As the voltage source begins to recover (indicated on curve 352), at point 370 the UV outresponse begins (e.g., restore load randomly over 15 minutes).
Not only are the following parameters configurable, but they correspond to each other in
UVtrigger is the voltage at which under voltage ‘in response’ is triggered (e.g. 85% level). This is also the power fail reading which will cause the under voltage response to trigger (1 byte). The ExpressCom Configuration Command Code for this parameter is 41 (Hex).
UVrestore is the voltage at which the under voltage condition is finished, and the ‘out response’ begins (e.g. 95% level). This is also the power fail reading which will cause the under voltage response to restore (1 byte). The ExpressCom Configuration Command Code for this parameter is 41 (Hex).
UVin time is the length of time that the voltage must be continuously under the UVtrigger threshold to cause an under voltage response (UVin response), which is in the range of 0-130 seconds in 2 ms increments. This is necessary so that momentary spikes (caused by air conditioner compressors starting, for example) don't cause an under voltage response. This is also the time (in 2 ms increments) that the power fail reading must be less than UV Trigger value or threshold so as to trigger a UV response (1 byte). The ExpressCom Configuration Command Code for this parameter is 41 (Hex).
UVout time is the length of time that the voltage must be continuously over the UVrestore to exit an under voltage condition and cause an UVout response (0-130 seconds in 2 ms increments). This is also the time (in increments of 2 ms) that the power fail reading must be above UV Restore to cause a UV restore (1 byte). The ExpressCom Configuration Command Code for this parameter is 41 (Hex).
UVin response is the ExpressCom command to perform when an under voltage condition begins (e.g. shed relay for (up to) to hours). This is typically a command to control all loads, but may be any ExpressCom command(s) that fits within 16 Nibbles. The ExpressCom command commences with the MessageType and includes the MessageData. Multiple commands can be specified, if they fit (e.g., control all loads for 255 hours 08,20,FF).
UVout response is the ExpressCom command to perform when exiting an under voltage condition (e.g. restore relay 1 randomly over the next 15 minutes). If the under voltage response is not configured (UVtrigger=0) then the power line will continue to behave exactly as illustrated in
LUF_UV_Response is the parameter that determines what response occurs if LUF and LUV features are activated together.
Bit 0: If set then LUF IN response may occur while UVStatus non-zero.
Bit 1: If set then UV I response may occur while LUFStatus non-zero.
Bit 2: If set then LUF OUT response may occur while UVStatus non-zero.
Bit 3: If set then UV OUT response may occur while LUFStatus non-zero.
So, a value of 05h means that LUF response takes priority over UV response, and a value of OAh means UV response takes priority over LUF response. The UVStatus is kept in RAM. It is 00 if the device is not in an under voltage condition, and 01 if it is has triggered an under voltage response.
UV Counter is the Line Under Voltage Counter that is incremented each time the UV Status changes from ‘Normal’ to ‘UnderVoltage.’ It may be cleared by a Counter Reset command. The Counter Reset Command can also ‘freeze’ the UV Counter by copying its value to the Frozen UV Counter.
Frozen UV Counter is the Frozen Line Under Voltage Counter that is set by the Extended Counter Command which can ‘freeze’ the UV Counter by copying the UV Counter value to the Frozen UV Counter.
Referring now to
Referring now more particularly to
The line voltage is restored at point 524 for both restoration schemes and at point 522 the LUV system of the load control receiver device starts to function. At point 520, both restoration curves start a cold load pickup control and a counter starts counting. At this point, curve 504 progresses quickly to full restoration and re-engagement of loads. Curve 502, on the other hand, progresses more slowly such that at point 518 a UVIn Response begins (and the load is controlled0 after the UV time elapses. When the power increases sufficiently, a UVout response is triggered at point 516. This out response is typically a command to restore load randomly over fifteen minutes but may be any command or commands that fit in the allocated space in the firmware.
In a related embodiment, the disturbance response system of the present invention can also include a line under frequency (LUF) detection and load shed system operating within an end user climate control system. The LUF detection system enables a quick and efficient response to delivery system disturbances by identifying under frequency events and disconnecting the load.
Referring now to
In summary, the LUF detection and load shed system of the present invention executes pre-loaded commands in response to line under frequency conditions. The LUF system is included in a load control device located within an end user climate control system and operates to detect power fail events and to disconnect loads in response to the power fail events. In one example embodiment, the LUF detection system of the present invention is incorporated into a thermostat device of the type known in the art, such as the thermostats disclosed in U.S. Pats. D248,838 and D270,815 assigned to Honeywell, Inc. (see prior art
In this example embodiment, the LUF detection and load shed system incorporated into the thermostat module or shell operates within the consumer's climate control system to disconnect the heating or cooling units of the climate control system. Once the line frequency increases to an acceptable level and crosses a predefined threshold, the LUF-modified thermostat module re-engages the heating or cooling units. The LUF detection system determines the line frequency status of each power line cycle by counting the ticks on an internal timer between two successive zero-crossing falling edges of the power line. The LUF detection system of the present invention includes a microcontroller and firmware stored in a ROM with configurable variables being stored in an EEPROM.
In this example embodiment, the LUF detection system of the present invention measures the time period of each power line cycle and then compares the measured time period to a utility-settable (or configurable) trigger period. If the cycle length is greater than or equal to the trigger period, a counter is incremented. If the cycle is less than the trigger period, the counter is decremented. If the counter is incremented to a counter trigger, an under-frequency condition is detected and the LUF response is implemented. The LUF response may be a command to control load but may also be some other command or commands that fit within the allocated space in the firmware. When the frequency rises above a restore value, an under-frequency counter begins to count down. When the underfrequency counter reaches zero, an out response is executed that typically restores or re-engages all loads, but it may also be some other command or commands that fit within the allocated space in the firmware.
Referring now more specifically to
Referring to
In this example embodiment, when the frequency is at 60 Hz the NUF Count is initialized to zero. As the frequency line 804 drops below UFT Trigger 808, NUF Count starts counting up (see line 824). NUF Count starts to decrement in count at point 826 when frequency line 804 climbs above Trigger 808 and then resumes counting up at point 828 when frequency line 804 drops below Trigger 808 again. An NUF Trigger threshold 830 is defined on graph 820 as the point where the LUF detection system will signal that there is an under frequency condition. If the NUF Count reaches NUF Trigger at point 832, then an under frequency condition has been detected. At this point, LUF Status changes from 0 to 1 and the LUF-In Response is implemented and the LUF Status is set.
Referring now to
In this example embodiment, as the frequency is below 59.8 Hz the NUF Count is at the same value as the NUF Trigger 922. As the frequency line 904 rises above UFT Trigger 908, NUF Count starts counting down (see line 924). NUF Count starts to decrement in count at point 926 when frequency line 904 climbs above Trigger 908 and then resumes counting up at point 928 when frequency line 904 drops below UFT Restore 906. An NUF Trigger threshold 922 is defined on graph 920 as the point where the LUF detection system signaled that there was an under frequency condition. If the NUF Count reaches zero at point 932, then an under frequency condition has ceased. At this point, LUF Status changes from 1 to 0 and the LUF-Out Response is executed and the LUF Status is reset.
As described earlier, the Line Under Frequency (LUF) system of the present invention executes pre-loaded commands in response to line under-frequency conditions. Two different conditions are possible: LUF In and LUF Out. The LUF system determines the line frequency status of each power line cycle by counting the ‘ticks’ on an internal timer between two successive zero-crossing falling edges of the power line. The LUF detection system of the present invention correlates the Tick count with a Time period to generate a frequency calculation. The table below provides examples of this correlation:
In particular, the LUF system compares the period of each power line cycle to a utility-settable (or utility configurable) under frequency threshold trigger (UFT). The microcontroller then increments or decrements a Net Under Frequency counter (NUFCount) based on the frequency of the selected power line cycle. The internal “Tick” calculations are performed on the cycle periods, wherein the Period=1/frequency. For each power line cycle, the LUF module 604 measures the length of the cycle in ticks (781.914 ns per tick). Therefore, a smaller tick count corresponds to a smaller time period, which translates to a higher frequency. The frequency detection hardware of the present invention has a resolution of about +0.1 Hz for any given frequency sample, but over several frequency samples the software can accurately detect an under frequency condition.
Internal and Configurable LUF Variables
The MLP (Measured Line Period) is calculated for each power line cycle. At cold start, the NUFCount is cleared and it is incremented if the MLP of a particular power line cycle is greater than the UFT. If the MLP is less than the UFT, then the NUFCount is decremented. The LUF Status is an internal flag indicating the current line under-frequency status (0=Normal, 1=Under-Frequency). At cold start, LUF Status is set to Normal but the setting changes to Under-Frequency when NUF Count reaches the NUF Trigger threshold. It changes back to Normal when NUF Count reaches zero. This provides hysteresis in the system.
The configurable variables/parameters of the present invention include: NUF_Trigger, UFT_Trigger, UFT_Restore, LUFInResponse and LUFOutResponse. Each will be described in more detail as follows.
UFT_Trigger—This parameter is the Under Frequency Threshold Trigger to trigger the LUF State (in units of ‘Ticks’ as explained above). The Under Frequency Threshold sets the dividing point determining whether each power line cycle is considered a ‘Normal’ cycle or an ‘Under-Frequency’ cycle. The UFT value may be set between 0000 and FFFF. For this parameter the ExpressCom Configuration Command Code is 3D (Hex).
UFT_Restore—This parameter is the Under Frequency Threshold Restore to exit LUF State, where UFT_Restore≦UFT_Trigger (in “Tick” units). The Under Frequency Threshold sets the dividing point determining whether each power line cycle is considered an ‘Under-Frequency’ cycle or a ‘Normal’ cycle. The UFT value may be set between 0000 and FFFF. For this parameter the ExpressCom Configuration Command Code is 3D (Hex).
NUFTrigger—The Net Under Frequency Trigger parameter sets the NUFCount value at which the LUFInResponse is activated. The lower the NUFTrigger, the faster the LUFInResponse occurs during an under-frequency condition. If the NUFTrigger is zero, then the Line Under Frequency routines are disabled. For this parameter the ExpressCom Configuration Command Code is 3F (Hex).
LUFIn Response—The Line Under Frequency In Response is activated when the NUFCount reaches the NUFTrigger value while the LUFStatus is ‘Normal’. The LUFInResponse is typically a command to control all loads, but may be any ExpressCom command(s) that fits within 16 Nibbles. The ExpressCom command commences with the MessageType, and includes the MessageData. Multiple commands can be specified, if they fit. If this does not contain a valid ExpressCom command (eg all zeroes) then no response is implemented. eg, control all loads for 255 hours 08,20,FF. For this parameter the Expresscom Configuration Command Code is 3E (Hex).
LUFOut Response—The Line Under Frequency Out Response is activated when the NUFCount reaches the zero value while the LUFStatus is ‘Under-Frequency’. The LUFOutResponse is typically a command to restore all loads, but may be any ExpressCom command(s) that fits within 16 Nibbles. The ExpressCom command commences with the MessageType and includes the MessageData. Multiple commands can be specified, it they fit. If this does not contain a valid ExpressCom command (e.g., all zeroes) then no response is implemented (e.g., restore all loads randomly over 15 minutes 09,80,0F). For this parameter the ExpressCom Configuration Command Code is 3E (Hex).
LUFCounter—The Line Under Frequency Counter is incremented each time the LUFStatus changes from ‘Normal’ to ‘UnderFrequency’. It may be cleared by a Counter Reset command. The Counter Reset Command can also ‘freeze’ the LUFCounter by copying its value to the FrozenLUFCounter.
FrozenLUFCounter—The Frozen Line Under Frequency Counter is set by the Extended Counter Command which can ‘freeze’ the LUFCounter by copying the LUFCounter value to the FrozenLUFCounter.
LUF_UV_Response—This parameter determines what response occurs if LUF and LUV features are activated together in the detection system.
Bit 0: If set then LUF IN response may occur while UVStatus non-zero.
Bit 1: If set then UV IN response may occur while LUFStatus non-zero.
Bit 2: If set then LUF OUT response may occur while UVStatus non-zero.
Bit 3: If set then UV OUT response may occur while LUFStatus non-zero.
So, a value of 05h means that LUF response takes priority over UV response, and a value of OAh means that UV response takes priority over LUF response.
Referring now to
Where the electrical system is in a state of Under-Frequency (LUF Status=1) and MLP is greater than or equal to UFT_Restore and further where NUFCount is less than NUFTrigger, then the LUF system increments NUFCount. The LUF system decrements NUFCount where the MLP value is less than UFT_Restore and where NUFCount is greater than NUFTrigger. Where NUFCount is zero or NUFTrigger is zero, then LUF Status is se to Normal and the LUF system performs an LUFOutResponse, which typically restores all loads previously disconnected.
In the various embodiments described above, the power-fail and power-restore responses for the LUF system are controlled by the thermostat-type device, thereby not requiring monitoring by an electrical utility operator. This enables the thermostat-type device to respond to under-frequency events very quickly, usually within seconds, so as to protect valuable heating or cooling equipment and aid utility recovery on a system-wide basis. Further, the thermostat-type device may be either communicating or non-communicating. In a communicating embodiment, various parameters of the thermostat-type device and its operation can be enabled or disabled over the air. The thermostat-type device can use a number of wireless communications techniques including, but not limited to, radio frequency (RF) and Bluetooth (short distance RF) to communicate with the various HVAC units in and around the home. In a non-communicating embodiment, local under frequency protection is provided by the thermostat-type device without over-the-air communications capability. In a related embodiment, the under frequency protection thermo stat-type device need not include the transformer and the load control switch within the housing. The device can be connected to the externally located transformer and load switch.
The present invention may be embodied in other specific forms without departing from the spirit of the essential attributes thereof; therefore, the illustrated embodiments should be considered in all respects as illustrative and not restrictive, reference being made to the appended claims rather than to the foregoing description to indicate the scope of the invention.
This application is a divisional application of U.S. application Ser. No. 10/824,825 filed Apr. 15, 2004, now U.S. Pat. No. 7,242,114 entitled “Thermostat Device with Line Under Frequency Detection and Load Shedding Capability”, and claims priority to U.S. Application Ser. No. 60/485,435, filed Jul. 8, 2003, entitled “Thermostat Device With Line Under Frequency and Line Under Voltage Protection”, both of which are herein incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
3558911 | Muchuan | Jan 1971 | A |
3683343 | Feldman et al. | Aug 1972 | A |
3993984 | Penrod | Nov 1976 | A |
D248838 | Pasquarette et al. | Aug 1978 | S |
4156280 | Griess | May 1979 | A |
4190800 | Kelly, Jr. et al. | Feb 1980 | A |
4228511 | Simcoe et al. | Oct 1980 | A |
4341345 | Hammer et al. | Jul 1982 | A |
4345162 | Hammer et al. | Aug 1982 | A |
4371947 | Fujisawa | Feb 1983 | A |
4389577 | Anderson et al. | Jun 1983 | A |
4390876 | Bjorklund et al. | Jun 1983 | A |
D270815 | Odom | Oct 1983 | S |
4415943 | Wortman | Nov 1983 | A |
4464724 | Gurr et al. | Aug 1984 | A |
4551812 | Gurr et al. | Nov 1985 | A |
4583090 | Eden et al. | Apr 1986 | A |
4620283 | Butt et al. | Oct 1986 | A |
4635214 | Kasai et al. | Jan 1987 | A |
4657179 | Aggers et al. | Apr 1987 | A |
4672501 | Bilac et al. | Jun 1987 | A |
4708910 | Forss | Nov 1987 | A |
4780910 | Huddleston et al. | Oct 1988 | A |
4804938 | Rouse et al. | Feb 1989 | A |
4819180 | Hedman et al. | Apr 1989 | A |
4845685 | Wechsler et al. | Jul 1989 | A |
4902964 | Szabela et al. | Feb 1990 | A |
5099348 | Huddleston et al. | Mar 1992 | A |
5197668 | Ratz et al. | Mar 1993 | A |
5203497 | Ratz et al. | Apr 1993 | A |
5210712 | Saito | May 1993 | A |
5218552 | Stirk et al. | Jun 1993 | A |
5319296 | Patel | Jun 1994 | A |
5414640 | Seem | May 1995 | A |
5426620 | Budney | Jun 1995 | A |
5462225 | Massara et al. | Oct 1995 | A |
5475609 | Apothaker | Dec 1995 | A |
5502339 | Hartig | Mar 1996 | A |
5519622 | Chasek | May 1996 | A |
5576700 | Davis et al. | Nov 1996 | A |
5619121 | Trainor | Apr 1997 | A |
5640153 | Hildebrand et al. | Jun 1997 | A |
5675503 | Moe et al. | Oct 1997 | A |
5687139 | Budney | Nov 1997 | A |
5696695 | Ehlers et al. | Dec 1997 | A |
5761083 | Brown et al. | Jun 1998 | A |
5936817 | Matsko et al. | Aug 1999 | A |
6029092 | Stein | Feb 2000 | A |
6098893 | Berglund et al. | Aug 2000 | A |
6157874 | Cooley et al. | Dec 2000 | A |
6167389 | Davis et al. | Dec 2000 | A |
6181985 | O'Donnell et al. | Jan 2001 | B1 |
6208905 | Giddings et al. | Mar 2001 | B1 |
6254009 | Proffitt et al. | Jul 2001 | B1 |
6264110 | Proffitt et al. | Jul 2001 | B1 |
6305611 | Proffitt et al. | Oct 2001 | B1 |
6314378 | Hodge et al. | Nov 2001 | B1 |
6356426 | Dougherty | Mar 2002 | B1 |
6377874 | Ykema | Apr 2002 | B1 |
6480803 | Pierret et al. | Nov 2002 | B1 |
6496342 | Horvath et al. | Dec 2002 | B1 |
6509841 | Colton et al. | Jan 2003 | B1 |
6512966 | Lof et al. | Jan 2003 | B2 |
6519509 | Nierlich et al. | Feb 2003 | B1 |
6574581 | Bohrer et al. | Jun 2003 | B1 |
6622926 | Sartain et al. | Sep 2003 | B1 |
6634566 | Archacki, Jr. et al. | Oct 2003 | B2 |
6671586 | Davis et al. | Dec 2003 | B2 |
6681154 | Nierlich et al. | Jan 2004 | B2 |
6745106 | Howard et al. | Jun 2004 | B2 |
6747571 | Fierro et al. | Jun 2004 | B2 |
6789739 | Rosen | Sep 2004 | B2 |
6806446 | Neale | Oct 2004 | B1 |
6816350 | Hoopes | Nov 2004 | B1 |
6828695 | Hansen | Dec 2004 | B1 |
6891478 | Gardner | May 2005 | B2 |
6975926 | Schanin | Dec 2005 | B2 |
6975958 | Bohrer et al. | Dec 2005 | B2 |
7010363 | Donnelly et al. | Mar 2006 | B2 |
7136725 | Paciorek et al. | Nov 2006 | B1 |
7163158 | Rossi et al. | Jan 2007 | B2 |
7172132 | Proffitt et al. | Feb 2007 | B2 |
7216015 | Poth | May 2007 | B2 |
7222111 | Budike, Jr. | May 2007 | B1 |
7242114 | Cannon | Jul 2007 | B1 |
7292114 | Greenberg | Nov 2007 | B2 |
7346467 | Bohrer et al. | Mar 2008 | B2 |
7355301 | Ockert | Apr 2008 | B2 |
20020087234 | Lof et al. | Jul 2002 | A1 |
20020103655 | Boies et al. | Aug 2002 | A1 |
20020138176 | Davis et al. | Sep 2002 | A1 |
20030150925 | Archacki, Jr. et al. | Aug 2003 | A1 |
20030158632 | Nierlich et al. | Aug 2003 | A1 |
20040255601 | Kwon et al. | Dec 2004 | A1 |
20050097905 | Kwon et al. | May 2005 | A1 |
20050143865 | Gardner | Jun 2005 | A1 |
20060036349 | Kates | Feb 2006 | A1 |
20060036350 | Bohrer et al. | Feb 2006 | A1 |
20060283964 | Garozzo | Dec 2006 | A1 |
20060283965 | Mueller et al. | Dec 2006 | A1 |
20070021874 | Rognli et al. | Jan 2007 | A1 |
20080133065 | Cannon et al. | Jun 2008 | A1 |
Number | Date | Country |
---|---|---|
00 593 225 | Apr 1997 | EP |
WO 0152478 | Jul 2001 | WO |
Number | Date | Country | |
---|---|---|---|
60485435 | Jul 2003 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 10824825 | Apr 2004 | US |
Child | 11811144 | US |