Not Applicable.
Not Applicable.
Compressors used in heating, ventilating, and air conditioning (HVAC) systems are connected to lines carrying refrigerants that are under pressure. For various reasons, pressure in these systems fluctuate which can cause inefficiencies, mechanical problems, and even premature failure of HVAC systems and components, such as compressors.
In one embodiment, a system is provided that includes a compressor, a heat exchanger, and at least one refrigerant line to promote movement of refrigerant between the compressor and the heat exchanger. The system also includes a high pressure cut out (HPCO) switch to promote disabling the compressor based on a system pressure, and a pressure sensor to monitor the system pressure. The system also includes a control component, configured based on the system pressure monitored by the pressure sensor to infer a status of the HPCO switch.
In other embodiments, a system to reduce heating, ventilating, and air conditioning (HVAC) compressor wear is provided. The system includes a processor and a component configured to receive information related to a system pressure monitored by one or more pressure sensors and to use the information to infer whether a high pressure cut out (HPCO) switch has opened.
In yet other embodiments, a method to reduce heating, ventilating, and air conditioning (HVAC) compressor wear is provided. The method includes monitoring a system pressure to infer whether a high pressure cut out (HPCO) switch has opened.
In other embodiments, a system is provided that includes a compressor, a heat exchanger, at least one refrigerant line to promote communication of refrigerant between the compressor and the heat exchanger. The system includes a low pressure cut out (LPCO) switch to promote disabling the compressor based on a system pressure, and an ambient temperature sensor configured to determine an ambient temperature. The system includes a control component coupled to communicate with the LPCO switch and the ambient temperature sensor, the component configured to determine a mode state of the system and to disable the compressor based on a status of the LPCO switch, the ambient temperature, and the mode state.
In another embodiment, a method is provided that includes determining a mode state of the system, determining a status of an LPCO switch, and determining an ambient temperature. The method includes determining whether to disable the compressor based on a status of the LPCO switch, the ambient temperature, and the mode state.
The various characteristics described above, as well as other features, will be readily apparent to those skilled in the art upon reading the following detailed description of the embodiments of the disclosure, and by referring to the accompanying drawings.
For a more complete understanding of this disclosure, reference is now made to the following brief description, taken in connection with the accompanying drawings and detailed description, wherein like reference numerals represent like parts.
It should be understood at the outset that although illustrative implementations of one or more embodiments of the present disclosure are provided below, the disclosed methods and/or systems may be implemented using any number of techniques, whether currently known or in existence. The disclosure should in no way be limited to the illustrative implementations, drawings, and techniques illustrated below, including the exemplary designs and implementations illustrated and described herein, but may be modified within the scope of the appended claims along with their full scope of equivalents.
Compressors used in HVAC systems typically have high pressure cutout (HPCO) and low pressure cutout (LPCO) safety switches installed in their refrigerant lines to prevent the compressors from operating under abnormal system conditions and being damaged as a result. For example, an abnormally high or low refrigerant line pressure causes the respective HPCO or LPCO switch to open, which breaks an electrical connection to the compressor's contact relay coil and turns the compressor off. The HVAC system then periodically attempts to turn the compressor back on. However, during each such attempt, if the HPCO or LPCO switch is still open, then the compressor turns off. After the underlying problem is corrected and normal high and low line pressures are achieved, the HPCO or LPCO switch closes and thus enables the system to run the compressor for an extended period of time.
This process of turning on and then turning back off again quickly and running more often for shorter periods of time while an HPCO or LPCO switch is open is referred to as a “short-cycle” or “short-cycling” of the compressor. Such excessive on/off “short-cycling” decreases the reliability and performance life of the compressor.
Furthermore the HPCO switch or LPCO switch can be inadvertently tripped or inferred to trip. For example, an HPCO switch can be inadvertently inferred to trip due to a drop in ambient temperature caused by a typical summer storm. Also for example, an LPCO switch can be inadvertently tripped due to low ambient cooling or operating in an extremely low ambient heating mode. Under normal operating conditions, there may be a minimum required compressor off time (e.g., 5 minutes) if an HPCO or LPCO switch is tripped. However, if an HPCO or LPCO switch is inadvertently tripped, then the compressor may be cycled off and remain inoperable for the entire required off time.
The HVAC system 100 may be referred to as a “split-system” because the compressor 108, the ambient zone heat exchanger 110, and the ambient zone fan 126 are colocated in the ambient zone unit 104 while the restriction device 114, comfort zone heat exchanger 116, and comfort zone blower 118 are colocated in the comfort zone unit 106 separate from the ambient zone unit 104. However, in alternative embodiments of an HVAC system, substantially all of the components of the ambient zone unit 104 and the comfort zone unit 106 may be colocated in a single housing in a system called a “package system.” Further, in alternative embodiments, an HVAC system may comprise heat generators such as electrically resistive heating elements and/or gas furnace elements so that a comfort zone heat exchanger and the heat generators are both in a shared airflow path of a comfort zone blower.
While the comfort zone 102 may commonly be associated with a living space of a house or an area of a commercial building occupied by people, the comfort zone 102 may be also be associated with any other area in which it is desirable to control the temperature, humidity, and/or other air quality factors (i.e. computer equipment rooms, animal housings, chemical storage facilities, and so on). Further, while the comfort zone unit 106 is shown as being located outside the comfort zone 102 (i.e. within an unoccupied attic or crawlspace), the comfort zone unit may alternatively be located within or partially within the comfort zone 102 (i.e. in an interior closet of a building).
Each of the ambient zone heat exchanger 110 and the comfort zone heat exchanger 116 may be constructed as air coils, shell and tube heat exchangers, plate heat exchangers, regenerative heat exchangers, adiabatic wheel heat exchangers, dynamic scraped surface heat exchangers, or any other suitable form of heat exchanger. The compressor 108 may be constructed as any suitable compressor, for example, a centrifugal compressor, a diagonal or mixed-flow compressor, an axial-flow compressor, a reciprocating compressor, a rotary screw compressor, a rotary vane compressor, a scroll compressor, or a diaphragm compressor. In this embodiment, the compressor 108 is capable of operating in multiple stages (e.g., stage A and stage B). For example, the compressor 108 can be operated at a low speed (stage A) or a high speed (stage B). Alternative embodiments of an HVAC system may comprise more than one compressor and the compressors may be operable at more than one speed or at a range of speeds (i.e., a variable speed compressor). Further, while the HVAC system 100 is shown as operated in a cooling mode to remove heat from the comfort zone 102, the HVAC system 100 is configured as a “heat pump” system that selectively allows flow of refrigerant in the direction shown in
In the cooling mode, the compressor 108 operates to compress low pressure gas refrigerant into a hot and high pressure gas that is passed through the ambient zone heat exchanger 110. As the refrigerant is passed through the ambient zone heat exchanger 110, the ambient zone fan 112 operates to force air from the ambient zone 124 into contact with the ambient zone heat exchanger 110, thereby removing heat from the refrigerant and condensing the refrigerant into high pressure liquid form. The liquid refrigerant is then delivered to the restriction device 114. Forcing the refrigerant through the restriction device 114 causes the refrigerant to transform into a cold and low pressure gas. The cold gas is passed from the restriction device 114 into the comfort zone heat exchanger 116. While the cold gas is passed through the comfort zone heat exchanger 116, the comfort zone blower 118 operates to force air from the comfort zone 102 into contact with the comfort zone heat exchanger 116, heating the refrigerant and thereby providing a cooling and dehumidifying effect to the air, which is then returned comfort zone 102. In this embodiment, the HVAC system is using a vapor compression cycle, namely, the Rankine cycle. In the heating mode, generally, the direction of the flow of the refrigerant is reversed (compared to that shown in
Generally, the controller 128 communicates with the ambient zone temperature sensor 140 that is located in the ambient zone 124 (i.e. outdoors, outdoors within the ambient zone unit in an embodiment where the ambient zone unit is located in the ambient zone, adjacent the ambient zone unit in an embodiment where the ambient zone unit is located in the ambient zone, or any other suitable location for providing an ambient zone temperature or a temperature associated with the ambient zone). While the controller 128 is illustrated as positioned within the ambient zone unit 104, in alternative embodiments, the controller 128 may be positioned adjacent to but outside an ambient zone unit, outside a comfort zone, within a comfort zone unit, within a comfort zone, or at any other suitable location. It will be appreciated that in alternative embodiments, an HVAC system may comprise a second controller substantially similar to controller 128 and that the second controller may be incorporated into a comfort zone unit substantially similar to comfort zone unit 106. In the embodiment shown in
In the present embodiment, HVAC system 100 also may include an HPCO switch 180 installed in a discharge line of compressor 108 and coupled to flow-line 120a, and an LPCO switch 182 installed in a suction line of compressor 108 and coupled to flow-line 120b. The HPCO switch 180 may be configured to sense the pressure of the vapor at the discharge line or output of compressor 108 and may open if this pressure approaches a predefined high pressure cutout limit value. The LPCO switch 182 may be configured to sense the pressure of the refrigerant at the suction line or input of compressor 108 and may open if this pressure approaches a predefined low pressure cutout limit value. If either the HPCO switch or LPCO switch is open (e.g., due to an abnormal line pressure, etc.), an electrical connection (not shown) to the compressor or to the controller is broken and the compressor is turned off.
High Pressure Cut Out
The status of the HPCO switch, such as whether it is open or closed, may be determined by directly monitoring the switch. For example, a direct electrical connection may be made to the switch to detect whether the switch is open. Also such monitoring and detection of the status of the compressor, such as whether the compressor is receiving power, might provide helpful information for HVAC system operation control related to the HPCO switch status.
In some instances however such direct detection may not be possible or desirable. Instead the present disclosure describes systems and methods for inferring the status of the HPCO switch by monitoring aspects of the system pressure via one or more pressure sensors. For example, when the system pressure rises above an upper threshold (which might typically cause the HPCO switch to open) and then the system pressure subsequently falls below a lower threshold (which might typically follow a compressor shut-down), the present disclosure infers that the HPCO switch opened and shut-down the compressor. Thereafter the present disclosure might take certain actions, for example, disengaging the compressor for a period of time to prevent short-cycling, cycling on a high pressure limit indefinitely, and the associated detrimental effects. Additional system capabilities, details, and advantages are provided below.
Referring to
Next, if the compressor involved is turned on (e.g., controller 128 and control processor 132 may determine that a “Y” call or suitable other heating or cooling demand call from communicating thermostat 130 has been retrieved or received and either a high stage or low stage compressor has turned on), method 200 may determine whether or not the refrigerant pressure in the compressor's high pressure line has increased to a predetermined high pressure threshold value (state 206). As used herein, “Y” or “Y call” may refer to a state of the compressor, such as a continuous run of the compressor at a given state.
Control processor 132 may retrieve or receive high pressure values or data from one or more suitable pressure sensors (not shown) attached to or disposed in high pressure flow-line 120a. For an example refrigerant such as R-410A, the high pressure threshold value can fall within a range of pressure values between 590-625 psig (e.g., a threshold value of 595 psig). While in this state, if the compressor involved is turned off (e.g., control processor 132 may determine that the demand or “Y” call is no longer present, or the HVAC system is now operating in a defrost cycle), then method 200 proceeds back to the initialization state 204.
However, if in state 206, method 200 determines that the refrigerant pressure in the compressor's high pressure line is at or higher than the predetermined high threshold value, then method 200 determines whether or not the vapor pressure in the compressor's high pressure line has decreased to a predetermined low threshold value (state 208). Such a pressure drop may infer that the compressor is turned off. Again, for example, control processor 132 may retrieve or receive high pressure values or data from one or more suitable pressure sensors (not shown) attached to or disposed in high pressure flow-line 120a. For an example refrigerant such as R-410A, the low pressure threshold value can fall within a range of pressure values between 490-550 psig (e.g., a threshold value of 535 psig). While in this state, if the compressor involved is turned off (e.g., control processor 132 may determine that the demand or “Y” call is no longer present, or the HVAC system is now operating in a defrost cycle), then method 200 proceeds back to the initialization state 204.
Next, if method 200 subsequently determines that the refrigerant pressure in the compressor's high pressure line 120a falls to or less than the low pressure threshold value, method 200 may determine that a high pressure cutout event has occurred (e.g., as a result, the compressor has shut down) and may proceed to a lock out decision state 210. For example, while in state 208, if control processor 132 determines that the refrigerant pressure in the compressor's high pressure line is less than the low pressure threshold value and a high pressure cutout event has thus occurred, the control processor 132 may increment a fault bin 0 (e.g., in a memory storage area) by the value 1, and also sum up all of the fault bin values to form a total Fault Count value.
In some embodiments, method 200 may use multiple bins, such as 12 bins, to track the overall time interval during which high pressure cutout events may have occurred. In this embodiment, each bin of the 12 bins may represent a specific “bin timer length” (e.g., time interval between 0.5-3 hours, such as 2 hours). Consequently, for example, the use of 12 bins may represent a 22-24 hour window for the overall length of the bin timer involved.
While in the lock out decision state 210, method 200 may determine whether or not the value of the Fault Count is less than or equal to 1. If the Fault Count value is less than or equal to 1, method 200 may proceed back to the initialization state 204. If the Fault Count value is greater than 1, and the maximum count value (e.g., total number of high pressure events that have occurred over all 12 bins) is greater than or equal to the Fault Count value, method 200 may initiate a “short” lock out event (state 212). For example, during this state, control processor 132 may start a “Short Fault” timer and set a “Short Fault” flag. In response to a “short” lock out event, control processor 132 may cause the compressor to be disabled for a predetermined period of time (e.g., the value of the “Short Fault” timer). An example “short” lock out time period that may be used is three to six minutes, (e.g. five minutes), and during this time period, the outdoor fan (e.g., fan 114) may remain energized and operating or may be disabled as well. When the “short” lock out time period is expired (e.g., the Short Fault” timer has counted down to zero), method 200 may proceed back to the initialization state 204.
Returning to the lock out decision state 210, if method 200 determines that the value of the “Fault Count” is greater than the maximum count value, method 200 may initiate a “hard” lock out event (state 214). For example, in response to a “hard” lock out event, control processor 132 may set a system lock out that disables the compressor and the outdoor fan. The control processor 132 may also set a “call for service” flag to notify the HVAC system that service should be performed to clear the fault. The “hard” lock out event may be continued until method 200 determines that a power cycle or reset event 216 has occurred.
It is readily apparent to one of ordinary skill in the art that different processes or steps may be implemented to promote monitoring the system pressure as a means for inferring whether the HPCO switch has opened. Method 200 is merely exemplary of one such process, and the present disclosure should not be limited to this specific implementation since others are contemplated and will suggest themselves to one skilled in the art in view of the present disclosure and teachings.
Low Pressure Cut Out
Similar problems may exist in low pressure situations. Accordingly the present disclosure provides for similar systems and methods to prevent short cycling or cycling indefinitely when the LPCO switch is opened as was disclosed for the HPCO. Furthermore, alternate systems and methods are disclosed where the system repeatedly cuts out on low pressure above a threshold ambient temperature, the present disclosure provides for disabling the compressor until serviced by a technician. When the system cuts out at an ambient temperature below the threshold, the present disclosure promotes disabling the compressor until the ambient temperature rises.
Unlike the high pressure system example discussed above where the pressure was monitored because the HPCO switch was not directly monitored, in the present embodiment of the low pressure cut out, the LPCO switch may be monitored directly. As will be apparent to those skilled in the art based on the present disclosure, by inverting the high and low threshold limits, either method would apply to either switch type, depending on whether the choice is made to directly monitor the switch or to monitor the refrigerant pressure.
Regardless of the system mode, the method 300 then proceeds to block 312 where the LPCO switch is monitored. In the present disclosure, it is preferable to implement the method 300 anytime the HVAC system 100 includes a LPCO switch 182. At decision block 314, when the LPCO switch has not tripped, the process proceeds to block 316 where the system continues to operate as called the by the thermostat 130 and the LPCO switch may continue to be monitored. At decision block 314 when the LPCO switch has tripped, the process proceeds to block 318 where a compressor run timer is enabled. The process then proceeds to 320 where either a cool or heat counter is incremented depending on the mode that the system is in when the LPCO switch is tripped. The cool and heat counters may be periodically reset to zero. For example, after five hours of accumulated compressor run time since either counter was last incremented the counters may be reset. In other embodiments, run times that are shorter or longer than five hours might be required before resetting the counters.
At decision block 322, a lock out counter that tracks the number of previous lock outs is checked. In this embodiment, if the lock out counter is less than or equal to two, the process branches to block 324 which initiates a short lock out turning off the compressor. The threshold number of lock outs before initiating a short or hard lock out may be in a range of integers, but is two in the present embodiment. A higher threshold setting before initiating a hard lock out may reduce the nuisance related to a compressor lock out and associated disruption of the HVAC system 100; however, a higher number also increases the work load on the compressor, which may reduce compressor reliability.
As noted at block 326, the outdoor fan remains energized during a short lock out in the present embodiment, but the fan may also be disabled. At block 328, a short off timer is enabled. The timer for the short lock out period is five minutes, in this embodiment. In other embodiments, the short lock out duration may range from between one and ten minutes. At block 328, the compressor run timer is reset to zero. Next the process proceeds to decision block 330 where the process waits until the short off timer expires. Once the short off timer expires, the process moves to block 332, where the short off timer is reset, other exit routines may be executed. The process then returns to block 304.
Returning to decision block 322, when the lock out counter exceeds the threshold, the process branches to decision block 334 shown in
At block 342, the process will initiate a long lock out until the outdoor ambient temperature rises above a release threshold temperature, which will be discussed in greater detail below. The process then proceeds to block 344 where the compressor and outdoor fan are disabled. At blocks 346 and 348 a long off timer is enabled, a compressor timer may be reset, and alerts may be sent to various systems. The process proceeds to decision block 350 where the outdoor ambient temperature sensor is checked for fault conditions. Since this sensor was previously checked, a flag or other indicator might be sufficient at this step to determine the status of the sensor. When the sensor is missing or not working properly, at block 352, default temperatures, as described above might be used as the current Tamb. When the sensor is operational, at block 354, the current Tamb would be obtained.
The method then proceeds to block 356 where the current Tamb is compared to a release threshold temperature. In a cooling mode, the release threshold temperature might be in a range of about 55 to about 75 degrees Fahrenheit (e.g. 60° F.). As such, in cooling mode when the Tamb exceeds, for example, 60 degrees Fahrenheit, the process proceeds to block 358. Similarly, in a heating mode, the release threshold might be in a range of about 0 to about 20 degrees Fahrenheit (e.g. 15° F.). As such, in heating mode when the Tamb exceeds, for example, 15 degrees Fahrenheit, the process proceeds to block 358.
At decision block 356, if the Tamb does not exceed the respective release threshold, the process returns to block 342 and the long lock out continues. It will be appreciated that when the sensor is not working or absent, the default Tamb would not increase and accordingly certain values of default temperatures might not reach the above release thresholds. Thus, the long lock out might effectively be a hard lock out. Hard lock out will be described in greater detail below.
At block 358, the process executes an exit routine to exit the long lock out, which may include resetting short lock out flags and timers and otherwise readying the system for restart. At block 360, the process returns to the start 302 in
Returning to decision block 340, the outdoor ambient temperature (Tamb) is measured against cool and heat mode initiate threshold temperatures. As described above, when the LPCO switch has tripped and the system is in cooling mode, the cool mode initiate threshold may be set to a specific temperature, such as 55 degrees Fahrenheit (e.g. 55° F.). In this case in a cooling mode when the Tamb is greater than or equal to 55 degrees Fahrenheit, the process proceeds to block 362 to perform a hard lock out. Similarly as described above, when the LPCO switch has tripped and the system is in heating mode, the heat mode initiate threshold may be set to a specific temperature, such as 10 degrees Fahrenheit (e.g. 10° F.). For example, in a heating mode when the Tamb is greater than or equal to 10 degrees Fahrenheit, the process proceeds to block 362 as well.
At block 362, the process initiates a hard lock out and disables the compressor and outdoor fan. Next at block 364, a service call alert may be initiated. At block 366, the system stays in a hard lock out until the control board is reset, such as via cycling the power by a service technician. Once the system has been reset, at block 368, the process returns to start at block 302 in
Although various steps have been described, in other embodiments, some of the steps may be omitted or reordered to promote monitoring the LPCO switch to prevent the compressor from cycling on low pressure cut out and to keep the compressor from short cycling. Method 300 is merely exemplary of one such process, and the present disclosure should not be limited to this specific implementation since others are contemplated and will suggest themselves to one skilled in the art in view of the present disclosure and teachings.
While numerous embodiments have been provided in the present disclosure, it should be understood that the disclosed systems and methods may be embodied in many other specific forms without departing from the spirit or scope of the present disclosure. The present examples are to be considered as illustrative and not restrictive, and the intention is not to be limited to the details given herein. For example, the various elements or components may be combined or integrated in another system or certain features may be omitted, or not implemented.
Also, techniques, systems, subsystems and methods described and illustrated in the various embodiments as discrete or separate may be combined or integrated with other techniques, systems, subsystems or methods without departing from the scope of the present disclosure. Other items shown or discussed as coupled or directly coupled or communicating with each other may be indirectly coupled or communicating through some interface, device, or intermediate component, whether electrically, mechanically, or otherwise. Other examples of changes, substitutions, and alterations are ascertainable by one skilled in the art and could be made without departing from the spirit and scope disclosed herein.
Number | Name | Date | Kind |
---|---|---|---|
4221116 | Harnish | Sep 1980 | A |
4326387 | Friedman | Apr 1982 | A |
4467613 | Behr et al. | Aug 1984 | A |
4602484 | Bendikson | Jul 1986 | A |
4749881 | Uhrich | Jun 1988 | A |
4974420 | Kramer | Dec 1990 | A |
5138844 | Clanin et al. | Aug 1992 | A |
5377497 | Powell | Jan 1995 | A |
5507154 | Grant | Apr 1996 | A |
5605053 | Otori | Feb 1997 | A |
5689963 | Bahel et al. | Nov 1997 | A |
5970727 | Hiraoka et al. | Oct 1999 | A |
6021644 | Ares et al. | Feb 2000 | A |
6181538 | Yoo | Jan 2001 | B1 |
6216479 | Elwood | Apr 2001 | B1 |
6434957 | Nishizuka et al. | Aug 2002 | B1 |
6842650 | Bennett | Jan 2005 | B2 |
7024254 | Salsbury et al. | Apr 2006 | B2 |
7222494 | Peterson et al. | May 2007 | B2 |
Number | Date | Country | |
---|---|---|---|
20100080713 A1 | Apr 2010 | US |