The present disclosure relates generally to heating, ventilation, and air conditioning (HVAC) systems and applications and more particularly, but not by way of limitation, to methods and systems for relieving pressure within HVAC systems.
This section provides background information to facilitate a better understanding of the various aspects of the disclosure. It should be understood that the statements in this section of this document are to be read in this light, and not as admissions of prior art.
Currently, most HVAC systems utilize a charge compensator located in a liquid line downstream of a condenser as a way to accommodate variations in refrigerant discharge pressure. During normal operation, such liquid-line charge compensators are kept free of liquid by utilizing radiant heat from the condenser. This approach, however, is not effective in re-heat applications. When an HVAC system operates in re-heat mode, heat is first rejected from the refrigerant in a re-heat coil. By the time the refrigerant reaches the condenser, it is already saturated and not hot enough to drive liquid from the liquid-line condenser. This causes the HVAC system to operate undercharged resulting in significant loss of latent capacity in the re-heat mode.
This summary is provided to introduce a selection of concepts that are further described below in the detailed description. This summary is not intended to identify key or essential features of the claimed subject matter, nor is it to be used as an aid in limiting the scope of the claimed subject matter.
In one aspect, the present disclosure relates to a heating, ventilation, and air conditioning (“HVAC”) system. The HVAC system includes an evaporator. A compressor is fluidly coupled to the evaporator via a suction line. A condenser is fluidly coupled to the compressor via a discharge line. The condenser includes a first pass and a second pass. A common manifold fluidly couples the first pass and the second pass. A charge compensator is fluidly coupled to the common manifold above a maximum liquid level of the common manifold.
In another aspect, the present disclosure relates to a condenser. The condenser includes a first pass and a second pass. A common manifold fluidly couples the first pass to the second pass. A charge compensator is fluidly coupled to the common manifold above a maximum liquid level of the common manifold via an upper connection line and a lower connection line.
In another aspect, the present invention relates to a method for addressing elevated discharge pressure. The method includes fluidly coupling a manifold to a first pass and to a second pass of a condenser. A charge compensator is fluidly coupled to the common manifold. The charge compensator is positioned above a maximum liquid level of the manifold.
The disclosure is best understood from the following detailed description when read with the accompanying figures. It is emphasized that, in accordance with standard practice in the industry, various features are not drawn to scale. In fact, the dimensions of various features may be arbitrarily increased or reduced for clarity of discussion.
Various embodiments will now be described more fully with reference to the accompanying drawings. The disclosure may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein.
HVAC systems are frequently utilized to adjust both temperature of conditioned air as well as relative humidity of the conditioned air. A cooling capacity of an HVAC system is a combination of the HVAC system's sensible cooling capacity and latent cooling capacity. Sensible cooling capacity refers to an ability of the HVAC system to remove sensible heat from conditioned air. Latent cooling capacity refers to an ability of the HVAC system to remove latent heat from conditioned air. Sensible cooling capacity and latent cooling capacity vary with environmental conditions. Sensible heat refers to heat that, when added to or removed from the conditioned air, results in a temperature change of the conditioned air. Latent heat refers to heat that, when added to or removed from the conditioned air, results in a phase change of, for example, water within the conditioned air. Sensible-to-total ratio (“S/T ratio”) is a ratio of sensible heat to total heat (sensible heat+latent heat). The lower the S/T ratio, the higher the latent cooling capacity of the HVAC system for given environmental conditions. The S/T ratio is negative in the case of heating.
Sensible cooling load refers to an amount of heat that must be removed from the enclosed space to accomplish a desired temperature change of the air within the enclosed space. The sensible cooling load is reflected by a temperature within the enclosed space as read on a dry-bulb thermometer. Latent cooling load refers to an amount of heat that must be removed from the enclosed space to accomplish a desired change in humidity of the air within the enclosed space. The latent cooling load is reflected by a temperature within the enclosed space as read on a wet-bulb thermometer. Setpoint or temperature setpoint refers to a target temperature setting of the HVAC system as set by a user or automatically based on a pre-defined schedule.
When there is a high sensible cooling load such as, for example, when outside-air temperature is significantly warmer than an inside-air temperature setpoint, the HVAC system will continue to operate in an effort to effectively cool and dehumidify the conditioned air. Such operation of the HVAC system is known as “cooling mode.” When there is a low sensible cooling load but high relative humidity such as, for example, when the outside air temperature is relatively close to the inside air temperature setpoint, but the outside air is considerably more humid than the inside air, supplemental air dehumidification is often undertaken to avoid occupant discomfort. Such operation of the HVAC system is known as “re-heat mode.”
An existing approach to air dehumidification involves lowering the temperature setpoint of the HVAC system. This approach causes the HVAC system to operate for longer periods of time than if the temperature setpoint of the HVAC system were set to a higher temperature. This approach serves to reduce both the temperature and humidity of the conditioned air. However, this approach results in over-cooling of the conditioned air, which over-cooling often results in occupant discomfort. Additionally, consequent extended run times cause the HVAC system to consume more energy, which leads to higher utility costs.
Another air dehumidification approach involves re-heating of air leaving an evaporator coil. This approach typically involves directing refrigerant from the compressor to a re-heat coil positioned adjacent to the evaporator coil. The re-heat coil transfers some heat energy from the refrigerant to the air leaving the evaporator thereby raising the temperature of air leaving the evaporator and lowering the temperature of the refrigerant before the refrigerant moves to the condenser.
The HVAC system 100 includes a circulation fan 110, a gas heat 120, electric heat 122 typically associated with the circulation fan 110, and a refrigerant evaporator coil 130, also typically associated with the circulation fan 110. The circulation fan 110, the gas heat 120, the electric heat 122, and the refrigerant evaporator coil 130 are collectively referred to as an “indoor unit” 148. In various embodiments, the indoor unit 148 is located within, or in close proximity to, the enclosed space 101. The HVAC system 100 also includes a compressor 140 and an associated condenser coil 142, which are typically referred to as an “outdoor unit” 144. In various embodiments, the outdoor unit 144 is, for example, a rooftop unit or a ground-level unit. The compressor 140 and the associated condenser coil 142 are connected to an associated evaporator coil 130 by a refrigerant line 146. In various embodiments, the compressor 140 is, for example, a single-stage compressor, a multi-stage compressor, a single-speed compressor, or a variable-speed compressor. In various embodiments, the circulation fan 110, sometimes referred to as a blower, may be configured to operate at different capacities (i.e., variable motor speeds) to circulate air through the HVAC system 100, whereby the circulated air is conditioned and supplied to the enclosed space 101.
Still referring to
The HVAC controller 150 may be an integrated controller or a distributed controller that directs operation of the HVAC system 100. The HVAC controller 150 includes an interface to receive, for example, thermostat calls, temperature setpoints, blower control signals, environmental conditions, and operating mode status for various zones of the HVAC system 100. For example, in various embodiments, the environmental conditions may include indoor temperature and relative humidity of the enclosed space 101. In various embodiments, the HVAC controller 150 also includes a processor and a memory to direct operation of the HVAC system 100 including, for example, a speed of the circulation fan 110.
Still referring to
In various embodiments, the HVAC system 100 is configured to communicate with a plurality of devices such as, for example, a monitoring device 156, a communication device 155, and the like. In various embodiments, the monitoring device 156 is not part of the HVAC system. For example, the monitoring device 156 is a server or computer of a third party such as, for example, a manufacturer, a support entity, a service provider, and the like. In other embodiments, the monitoring device 156 is located at an office of, for example, the manufacturer, the support entity, the service provider, and the like.
In various embodiments, the communication device 155 is a non-HVAC device having a primary function that is not associated with HVAC systems. For example, non-HVAC devices include mobile-computing devices that are configured to interact with the HVAC system 100 to monitor and modify at least some of the operating parameters of the HVAC system 100. Mobile computing devices may be, for example, a personal computer (e.g., desktop or laptop), a tablet computer, a mobile device (e.g., smart phone), and the like. In various embodiments, the communication device 155 includes at least one processor, memory and a user interface, such as a display. One skilled in the art will also understand that the communication device 155 disclosed herein includes other components that are typically included in such devices including, for example, a power supply, a communications interface, and the like.
The zone controller 180 is configured to manage movement of conditioned air to designated zones of the enclosed space 101. Each of the designated zones include at least one conditioning or demand unit such as, for example, the gas heat 120 and at least one user interface 170 such as, for example, the thermostat. The zone-controlled HVAC system 100 allows the user to independently control the temperature in the designated zones. In various embodiments, the zone controller 180 operates electronic dampers 185 to control air flow to the zones of the enclosed space 101.
In some embodiments, a data bus 190, which in the illustrated embodiment is a serial bus, couples various components of the HVAC system 100 together such that data is communicated therebetween. The data bus 190 may include, for example, any combination of hardware, software embedded in a computer readable medium, or encoded logic incorporated in hardware or otherwise stored (e.g., firmware) to couple components of the HVAC system 100 to each other. As an example and not by way of limitation, the data bus 190 may include an Accelerated Graphics Port (AGP) or other graphics bus, a Controller Area Network (CAN) bus, a front-side bus (FSB), a HYPERTRANSPORT (HT) interconnect, an INFINIBAND interconnect, a low-pin-count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a serial advanced technology attachment (SATA) bus, a Video Electronics Standards Association local (VLB) bus, or any other suitable bus or a combination of two or more of these. In various embodiments, the data bus 190 may include any number, type, or configuration of data buses 190, where appropriate. In particular embodiments, one or more data buses 190 (which may each include an address bus and a data bus) may couple the HVAC controller 150 to other components of the HVAC system 100. In other embodiments, connections between various components of the HVAC system 100 are wired. For example, conventional cable and contacts may be used to couple the HVAC controller 150 to the various components. In some embodiments, a wireless connection is employed to provide at least some of the connections between components of the HVAC system such as, for example, a connection between the HVAC controller 150 and the circulation fan 110 or the plurality of environment sensors 160.
Still referring to
The low-pressure, low-temperature, super-heated vapor refrigerant is introduced into the compressor 140 via the suction line 204. The compressor 140 increases the pressure of the low-pressure, low-temperature, super-heated vapor refrigerant and, by operation of the ideal gas law, also increases the temperature of the low-pressure, low-temperature, super-heated vapor refrigerant to form a high-pressure, high-temperature, superheated vapor refrigerant. The high-pressure, high-temperature, superheated vapor refrigerant leaves the compressor 140 via a discharge line 206 and enters a re-heat valve 205. When operating in re-heat mode, the re-heat valve 205 directs at least a portion of the high-pressure, high-temperature, superheated vapor refrigerant to a re-heat coil 266 via a re-heat feed line 264. The re-heat coil is positioned down wind of the evaporator coil 130. The re-heat coil 266 transfers heat energy from the high-pressure, high-temperature, superheated vapor refrigerant to air leaving the evaporator coil 130 thereby raising a temperature of air leaving the evaporator coil 130. The refrigerant then returns to the discharge line 206 via a re-heat return line 268. Upon returning to the discharge line 206, the refrigerant moves to the condenser 142.
When operating in cooling mode, the re-heat valve 205 directs the high-pressure, high-temperature, superheated vapor refrigerant from the compressor 140 to the condenser coil 142 via the discharge line 206. Outside air is circulated around the condenser coil 142 by a condenser fan 210. The outside air is typically cooler than the high-pressure, high-temperature, superheated vapor refrigerant present in the condenser coil 142. Thus, heat is transferred from the high-pressure, high-temperature, superheated vapor refrigerant to the outside air. Removal of heat from the high-pressure, high-temperature, superheated vapor refrigerant causes the high-pressure, high-temperature, superheated vapor refrigerant to condense and change from a vapor state to a high-pressure, high-temperature, sub-cooled liquid state. The high-pressure, high-temperature, sub-cooled liquid refrigerant leaves the condenser coil 142 via the liquid line 208 and enters the metering device 202.
In the metering device 202, the pressure of the high-pressure, high-temperature, sub-cooled liquid refrigerant is abruptly reduced by, for example, regulating an amount of refrigerant that travels to the distributor 203. Abrupt reduction of the pressure of the high-pressure, high-temperature, sub-cooled liquid refrigerant causes sudden, rapid, evaporation of a portion of the high-pressure, high-temperature, sub-cooled liquid refrigerant, commonly known as flash evaporation. The flash evaporation lowers the temperature of the resulting liquid/vapor refrigerant mixture to a temperature lower than a temperature of the air in the enclosed space 101. The liquid/vapor refrigerant mixture leaves the metering device 202 and enters the distributor 203 via the evaporator intake line 209. The distributor 203 divides refrigerant flow into the evaporator circuit line 211 and directs refrigerant to the evaporator coil 130.
Still referring to
Still referring to
Still referring to
Depending on the embodiment, certain acts, events, or functions of any of the algorithms, methods, or processes described herein can be performed in a different sequence, can be added, merged, or left out altogether (e.g., not all described acts or events are necessary for the practice of the algorithms, methods, or processes). Moreover, in certain embodiments, acts or events can be performed concurrently, e.g., through multi-threaded processing, interrupt processing, or multiple processors or processor cores or on other parallel architectures, rather than sequentially. Although certain computer-implemented tasks are described as being performed by a particular entity, other embodiments are possible in which these tasks are performed by a different entity.
Conditional language used herein, such as, among others, “can,” “might,” “may,” “e.g.,” and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or states. Thus, such conditional language is not generally intended to imply that features, elements and/or states are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without author input or prompting, whether these features, elements and/or states are included or are to be performed in any particular embodiment.
While the above detailed description has shown, described, and pointed out novel features as applied to various embodiments, it will be understood that various omissions, substitutions, and changes in the form and details of the devices or algorithms illustrated can be made without departing from the spirit of the disclosure. As will be recognized, the processes described herein can be embodied within a form that does not provide all of the features and benefits set forth herein, as some features can be used or practiced separately from others. The scope of protection is defined by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.
This application is a continuation of U.S. patent application Ser. No. 15/957,075, filed on Apr. 19, 2018, U.S. patent application Ser. No. 15/957,075; U.S. patent application Ser. No. 14/279,043, filed on May 15, 2014 and U.S. patent application Ser. No. 14/706,945, filed on May 7, 2015 are incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
1944899 | Miller | Jan 1934 | A |
3563304 | McGrath | Feb 1971 | A |
3643462 | Eberhart | Feb 1972 | A |
3777508 | Imabayashi et al. | Dec 1973 | A |
4030315 | Harnish | Jun 1977 | A |
4110998 | Owen | Sep 1978 | A |
4215555 | Cann et al. | Aug 1980 | A |
4242873 | Hino | Jan 1981 | A |
4383419 | Bottum | May 1983 | A |
4437317 | Ibrahim | Mar 1984 | A |
4480446 | Margulefsky et al. | Nov 1984 | A |
4522037 | Ares et al. | Jun 1985 | A |
4551983 | Atsumi et al. | Nov 1985 | A |
4554792 | Margulefsky et al. | Nov 1985 | A |
4655051 | Jones | Apr 1987 | A |
4766734 | Dudley | Aug 1988 | A |
4771610 | Nakashima et al. | Sep 1988 | A |
4861561 | Pritchard | Aug 1989 | A |
RE33212 | Lower et al. | May 1990 | E |
4942743 | Gregory | Jul 1990 | A |
5042271 | Manz | Aug 1991 | A |
5117645 | Bryant | Jun 1992 | A |
5136855 | Lenarduzzi | Aug 1992 | A |
5159817 | Hojo et al. | Nov 1992 | A |
5548971 | Rockenfeller et al. | Aug 1996 | A |
5628200 | Pendergrass | May 1997 | A |
5651263 | Nonaka et al. | Jul 1997 | A |
5651265 | Grenier | Jul 1997 | A |
5653120 | Meyer | Aug 1997 | A |
5758514 | Genung et al. | Jun 1998 | A |
5802859 | Zugibe | Sep 1998 | A |
5848537 | Biancardi et al. | Dec 1998 | A |
5896754 | Balthazard et al. | Apr 1999 | A |
5937665 | Kiessel et al. | Aug 1999 | A |
6055818 | Valle et al. | May 2000 | A |
6470704 | Shibata et al. | Oct 2002 | B2 |
6904963 | Hu | Jun 2005 | B2 |
8051675 | Carlson et al. | Nov 2011 | B1 |
8602093 | Iwasaki | Dec 2013 | B2 |
9499026 | Brodie et al. | Nov 2016 | B2 |
9599380 | Yamashita | Mar 2017 | B2 |
9618237 | Kim et al. | Apr 2017 | B2 |
9644906 | Shimamoto et al. | May 2017 | B2 |
9651287 | Morimoto et al. | May 2017 | B2 |
9664191 | Tanaka | May 2017 | B2 |
9732992 | Yamashita | Aug 2017 | B2 |
9777950 | Uselton | Oct 2017 | B2 |
9823000 | Wang | Nov 2017 | B2 |
9834063 | Kang et al. | Dec 2017 | B2 |
9855821 | Kang et al. | Jan 2018 | B2 |
9862251 | Brodie et al. | Jan 2018 | B2 |
10330358 | Goel | Jun 2019 | B2 |
20010029747 | Gaul | Oct 2001 | A1 |
20020003037 | Cousineau et al. | Jan 2002 | A1 |
20040000153 | Bagley | Jan 2004 | A1 |
20040025526 | Aflekt et al. | Feb 2004 | A1 |
20040148956 | Arshansky et al. | Aug 2004 | A1 |
20050066678 | Kamimura | Mar 2005 | A1 |
20050120733 | Healy et al. | Jun 2005 | A1 |
20050132728 | Lifson et al. | Jun 2005 | A1 |
20050247070 | Arshansky et al. | Nov 2005 | A1 |
20060010899 | Lifson et al. | Jan 2006 | A1 |
20060123834 | Hwang et al. | Jun 2006 | A1 |
20070193285 | Knight et al. | Aug 2007 | A1 |
20080034777 | Copeland et al. | Feb 2008 | A1 |
20080104975 | Gorbounov et al. | May 2008 | A1 |
20080296005 | Taras et al. | Dec 2008 | A1 |
20080314064 | Al-Eidan | Dec 2008 | A1 |
20090211283 | Koh et al. | Aug 2009 | A1 |
20090229285 | Sato et al. | Sep 2009 | A1 |
20090229300 | Fujimoto et al. | Sep 2009 | A1 |
20090241569 | Okada et al. | Oct 2009 | A1 |
20090241573 | Ikegami et al. | Oct 2009 | A1 |
20100064710 | Slaughter | Mar 2010 | A1 |
20100218513 | Vaisman et al. | Sep 2010 | A1 |
20100326075 | Fong et al. | Dec 2010 | A1 |
20110041523 | Taras et al. | Feb 2011 | A1 |
20110146321 | Jin | Jun 2011 | A1 |
20110154848 | Jin | Jun 2011 | A1 |
20110192176 | Kim et al. | Aug 2011 | A1 |
20110197600 | Hamada et al. | Aug 2011 | A1 |
20120111042 | Hamada et al. | May 2012 | A1 |
20120227426 | Deaconu | Sep 2012 | A1 |
20120227429 | Louvar et al. | Sep 2012 | A1 |
20120324911 | Shedd | Dec 2012 | A1 |
20130098088 | Lin | Apr 2013 | A1 |
20130174595 | Okuda et al. | Jul 2013 | A1 |
20130340451 | Sapp | Dec 2013 | A1 |
20140311172 | Iwasaki | Oct 2014 | A1 |
20140326018 | Ignatiev | Nov 2014 | A1 |
20140345310 | Tamaki et al. | Nov 2014 | A1 |
20150020536 | Lee et al. | Jan 2015 | A1 |
20150040594 | Suzuki et al. | Feb 2015 | A1 |
20150075204 | Brodie et al. | Mar 2015 | A1 |
20150089967 | Kim et al. | Apr 2015 | A1 |
20150267925 | Inada et al. | Sep 2015 | A1 |
20150267946 | Lowstuter, Jr. et al. | Sep 2015 | A1 |
20150276271 | Uselton | Oct 2015 | A1 |
20150276290 | Aoyama | Oct 2015 | A1 |
20150330685 | Goel | Nov 2015 | A1 |
20160178222 | Bush et al. | Jun 2016 | A1 |
20160195311 | Li et al. | Jul 2016 | A1 |
20160273795 | Takenaka et al. | Sep 2016 | A1 |
20160298893 | Knatt et al. | Oct 2016 | A1 |
20170016659 | Chen et al. | Jan 2017 | A1 |
20170059219 | Goel | Mar 2017 | A1 |
20180094841 | Kester et al. | Apr 2018 | A1 |
20190323747 | Giles et al. | Oct 2019 | A1 |
20200124313 | Todoroki et al. | Apr 2020 | A1 |
20200240684 | Reardon et al. | Jul 2020 | A1 |
Number | Date | Country |
---|---|---|
10317551 | Apr 2004 | DE |
1821048 | Aug 2007 | EP |
H05203275 | Aug 1993 | JP |
11248266 | Sep 1999 | JP |
2002195705 | Jul 2002 | JP |
WO-9414016 | Jun 1994 | WO |
Entry |
---|
U.S. Appl. No. 16/014,436, Bachellor. |
Lattanzi, Matt and Priestley, Doug, Micro-Channel Evaporator-Coil Technology, RSES Journal [online], Oct. 2012, pp. 14-18, [retrieved on Sep. 30, 2017]. Retrieved from the internett <URL: https://www.rses.org/assets/rses_journal/1012_Evaporators.pdf>. |
“Microchannel Coil Servicing Guidelines: Trane Unitary Light and Commercial Units”, Trane [online], May 5, 2011, pp. 1-16, [retrieved on Sep. 30, 2017]. Retrieved from the internet <https://www.trane.com/content/dam/Trane/Commercial/lar/es/product-systems/comercial/Rooftops/Accesorios-Rooftops;/IOM/Microchannel%20IOM%20(Ingl%C3%A9s).pdf>. |
Ito et al., Air Conditioner, Aug. 10, 1993, JPH05203275A Whole Document (Year: 1993). |
Number | Date | Country | |
---|---|---|---|
20200200452 A1 | Jun 2020 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15957075 | Apr 2018 | US |
Child | 16809884 | US |