The present disclosure relates generally to heating, ventilation, and air conditioning (HVAC) systems and more particularly, but not by way of limitation, to methods and systems for preventing a freeze event using refrigerant temperature.
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.
HVAC systems are used to regulate environmental conditions within an enclosed space. Typically, HVAC systems have a circulation fan that pulls air from the enclosed space through ducts and pushes the air back into the enclosed space through additional ducts after conditioning the air (e.g., heating, cooling, humidifying, or dehumidifying the air). To direct operation of the circulation fan and other components, HVAC systems include a controller. In addition to directing operation of the HVAC system, the controller may be used to monitor various components, (i.e. equipment) of the HVAC system to determine if the components are functioning properly.
A more complete understanding of embodiments of the present invention may be obtained by reference to the following Detailed Description when taken in conjunction with the accompanying Drawings wherein:
Various embodiments of the present invention will now be described more fully with reference to the accompanying drawings. The invention 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. In a typical embodiment, 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 (“SIT 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. In a typical embodiment, 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.
During operation of an HVAC system, evaporator coils may suffer loss in performance as a result of ice forming on an evaporator itself. Ice may form on an exterior of the evaporator due to a variety of conditions. Common causes of ice formation include, for example, loss of refrigerant charge, low ambient temperatures, dirty evaporator coils, uneven air flow distribution over the evaporator, low load requirement, indoor blower fan degradation, low refrigerant saturation suction temperature, and reduced air flow over the evaporator which may occur due to a dirty or blocked air filter. These conditions may cause surface temperature of the evaporator coil, either across the entire evaporator or localized to particular regions, to fall. If the temperature of air passing over the evaporator drops below a dew point, any water vapor that may be present in the air will begin to condense onto the evaporator.
An evaporator experiencing a freeze risk and ultimately experiencing ice buildup on the surface of the evaporator coil will have diminished performance. The ice buildup may increase heat resistance of the evaporator and slow heat transfer between the refrigerant and air. Ice buildup may also reduce a rate of air flow that passes over a surface of the evaporator, further reducing cooling capacity. The reduced heat transfer between the evaporator and the air may exacerbate the temperature drop of the evaporator coil, leading to further ice buildup and increasingly poor performance of the HVAC system. Not only is reduced cooling to a conditioned space an inconvenience, it may cause reliability issues and decrease the life of the HVAC system. For example, reduction in the evaporator's heat transfer rate as a result of the ice buildup, leads to lower refrigerant suction pressure, which may cause reliability issues for the HVAC system's compressor.
Some conventional systems may use a freeze stat installed proximate the evaporator to protect against the HVAC system from operating once the evaporator has begun to experience a freeze event such as, for example, ice or frost buildup. Typically, the freeze stat may have a first setpoint for a temperature close to the freezing point. When the freeze stat detects that the temperature of the evaporator coil has reached the first setpoint, the HVAC system will deactivate the compressor. The compressor will not resume operation until the freeze stat detects that the temperature of the evaporator coil has increased to a second setpoint indicating that there is no remaining ice or frost buildup on the evaporator.
Certain embodiments of the present disclosure may have advantages over conventional systems using the freeze stat. For example, certain embodiments reduce material cost and operational cost because the freeze stat and associated components can be omitted from the HVAC system. Another advantage of certain embodiments is that the HVAC system can detect the freeze event (e.g., ice or frost buildup) that occurs anywhere on the evaporator. This is an advantage compared to the conventional freeze stat because the conventional freeze stat may only detect freezing of a discrete portion of the evaporator coil (which might not necessarily be the portion of the evaporator coil that is experiencing the risk of freezing). Additionally, certain embodiments improve user comfort within the conditioned space. For example, rather than employing the freeze stat that causes the compressor to completely power off when detecting the freeze event, embodiments of the present disclosure may take actions to mitigate the freeze event in order to reduce a likelihood of having to completely power off the compressor. It is understood that certain embodiments may include other advantages and that the advantages described are merely examples. Certain embodiments may include all, some, or none of the above-described advantages.
The HVAC system 100 includes a variable-speed circulation fan 110, a gas heat 120, electric heat 122 typically associated with the variable-speed circulation fan 110, and a refrigerant evaporator coil 130, also typically associated with the variable-speed circulation fan 110. The variable-speed 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 a typical embodiment, the indoor unit 148 is located within, or in close proximity to, the enclosed space 101. The HVAC system 100 also includes a variable-speed 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 variable-speed compressor 140 and the associated condenser coil 142 are connected to an associated evaporator coil 130 by a refrigerant line 146. In a typical embodiment, the variable-speed compressor 140 is, for example, a single-stage compressor, a multi-stage compressor, a single-speed compressor, or a variable-speed compressor. The variable-speed circulation fan 110, sometimes referred to as a blower, is 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. In a typical embodiment, 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 a typical embodiment, the environmental conditions may include indoor temperature and relative humidity of the enclosed space 101. In a typical embodiment, 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 variable-speed circulation fan 110.
Still referring to
In a typical embodiment, 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 a typical embodiment, 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 a typical embodiment, 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 a typical embodiment, 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 a typical embodiment, 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. In a typical embodiment, 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 variable-speed 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 214. In a typical embodiment, 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 the discharge line 216 and enters the condenser coil 142.
Still referring to
In the metering device 202, the pressure of the high-pressure, high-temperature, sub-cooled liquid refrigerant is abruptly reduced. In various embodiments where the metering device 202 is, for example, a thermostatic expansion valve, the metering device 202 reduces the pressure of the high-pressure, high-temperature, sub-cooled liquid refrigerant by regulating an amount of refrigerant that travels to the evaporator coil 130. 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 directs refrigerant to the refrigerant evaporator coil 130 via the evaporator circuit line 226.
Some conventional systems may use the freeze stat installed proximate the evaporator to protect against the HVAC system continually operating once the evaporator has begun to experience the freeze event. Rather than employing the freeze stat that causes the compressor to completely power off when detecting the freeze event, embodiments of the present disclosure utilize at least one temperature sensor and temperature values obtained from the at least one temperature sensor to control operation of the compressor upon detecting the freeze event to mitigate the risk of ice or frost buildup.
According to an exemplary embodiment, a temperature sensor 224 is disposed proximate the distributor 203 on the evaporator circuit line 226. In various embodiments, the temperature sensor 224 may be, for example, a thermocouple, a thermometer, a thermostat, or any other appropriate temperature sensor. The temperature sensor 224 is electrically coupled to the HVAC controller 150 and measures a refrigerant temperature prior to the refrigerant entering the evaporator coil 130 (also known as the “saturated suction temperature”). In other embodiments, however, the temperature sensor 224 may be disposed at various locations within the HVAC system 200 such as, for example, on an exterior surface of the evaporator coil 130 (illustrated by dotted circle 224A) thereby using an evaporator coil 130 surface temperature as a proxy measurement for the saturated suction temperature. In a typical embodiment, only one temperature sensor 224 is utilized to measure the saturated suction temperature; however, in other embodiments, any number of temperature sensors can be utilized as dictated by design requirements. In various embodiments, the temperature sensor 224, is electrically coupled to the HVAC controller 150 via, for example, a wired or a wireless connection. For illustrative purposes, the temperature sensor 224 is described to measure the saturated suction temperature; however, in alternate embodiments, the saturated suction temperature can be calculated using a refrigerant suction pressure which can be measured using a pressure transducer. For example, the saturated suction temperature can be calculated from the refrigerant suction pressure utilizing the table below:
Still referring to
At step 306, the HVAC controller 150 determines if the saturated suction temperature is below the first pre-determined minimum threshold temperature value. In a typical embodiment, the first pre-determined minimum threshold temperature value may be, for example, 32° F. If, at step 306, the HVAC controller 150 determines that the saturated suction temperature is above the first pre-determined minimum threshold temperature value of, for example, 32° F., the process 300 returns to step 304. However, if, at step 306, the HVAC controller 150 determines that the saturated suction temperature is below the first pre-determined minimum threshold temperature value of, for example, 32° F., the process 300 proceeds to step 308. At step 308, a timer is initiated for a pre-determined time interval. In a typical embodiment, the pre-determined time interval may be, for example, 180 seconds. From step 308, the process 300 proceeds to step 310.
At step 310, the HVAC controller 150 determines if the saturated suction temperature is greater than or equal to a second pre-determined minimum threshold temperature value. In a typical embodiment, the second pre-determined minimum threshold temperature value may be, for example, 32° F. plus 1° F. (e.g., 33° F.) to account for temperature variations. If, at step 310, the HVAC controller 150 determines that the saturated suction temperature is at or above the second pre-determined minimum threshold temperature value of, for example, 33° F., the process 300 proceeds to step 312. At step 312, the controller 150 resets the timer. From step 312, the process 300 proceeds to step 304. However, if, at step 310, the HVAC controller 150 determines that the saturated suction temperature is below the second pre-determined minimum threshold temperature value of, for example, 33° F., the process 300 proceeds to step 314. In real solutions, a rate at which the saturated suction temperature drops below a pre-determined minimum threshold temperature value and an extent to which the saturated suction temperature drops below the pre-determined minimum threshold temperature value has great importance. Exemplary embodiments take into account the rate and the extent to which the saturated suction temperature drops below the pre-determined minimum threshold temperature value to modify operation of the compressor 140 in an effort to mitigate the risk of ice or frost buildup. As such, the timer is initiated to operate for a modified time interval. At step 314, the modified time interval is calculated using the equation listed below:
MODIFIED TIME INTERVAL=(T_DEF/LIMIT3)*SST3 where
T_DEF=180 seconds;
LIMIT=32° F.; and
SST is the saturated suction temperature.
From step 314, the process 300 proceeds to step 316. At step 316, the HVAC controller 150 determines if the timer operating for the modified time interval (step 314) has expired. If, at step 316, the HVAC controller 150 determines that the timer operating for the modified time interval (step 314) has not expired, the process 300 returns to step 310. However, if, at step 316, the HVAC controller 150 determines that the timer operating for the modified time interval (step 314) has expired, the process 300 proceeds to step 318. At step 318, the controller 150 raises an alarm and modifies operation of the compressor 140 to mitigate the risk of ice or frost buildup. In embodiments, where the compressor 140 is a variable-speed compressor, the modification may include adjusting the speed of the compressor 140 to a value between a maximum-rated speed and a minimum-rated speed. In embodiments where the compressor 140 is a fixed-speed compressor, the modification may include cycling the compressor 140 between an activated state and a deactivated state. Adjusting the speed of the compressor 140 impacts the saturated suction temperature such that the saturated suction temperature can be lowered by either deactivating the compressor 140 or reducing speed of the compressor 140. From step 318, the process 300 ends at step 320.
For purposes of this patent application, the term computer-readable storage medium encompasses one or more tangible computer-readable storage media possessing structures. As an example and not by way of limitation, a computer-readable storage medium may include a semiconductor-based or other integrated circuit (IC) (such as, for example, a field-programmable gate array (FPGA) or an application-specific IC (ASIC)), a hard disk, an HDD, a hybrid hard drive (HHD), an optical disc, an optical disc drive (ODD), a magneto-optical disc, a magneto-optical drive, a floppy disk, a floppy disk drive (FDD), magnetic tape, a holographic storage medium, a solid-state drive (SSD), a RAM-drive, a SECURE DIGITAL card, a SECURE DIGITAL drive, a flash memory card, a flash memory drive, or any other suitable tangible computer-readable storage medium or a combination of two or more of these, where appropriate.
Particular embodiments may include one or more computer-readable storage media implementing any suitable storage. In particular embodiments, a computer-readable storage medium implements one or more portions of the processor 320, one or more portions of the system memory 330, or a combination of these, where appropriate. In particular embodiments, a computer-readable storage medium implements RAM or ROM. In particular embodiments, a computer-readable storage medium implements volatile or persistent memory. In particular embodiments, one or more computer-readable storage media embody encoded software.
In this patent application, reference to encoded software may encompass one or more applications, bytecode, one or more computer programs, one or more executables, one or more instructions, logic, machine code, one or more scripts, or source code, and vice versa, where appropriate, that have been stored or encoded in a computer-readable storage medium. In particular embodiments, encoded software includes one or more application programming interfaces (APIs) stored or encoded in a computer-readable storage medium. Particular embodiments may use any suitable encoded software written or otherwise expressed in any suitable programming language or combination of programming languages stored or encoded in any suitable type or number of computer-readable storage media. In particular embodiments, encoded software may be expressed as source code or object code. In particular embodiments, encoded software is expressed in a higher-level programming language, such as, for example, C, Python, Java, or a suitable extension thereof. In particular embodiments, encoded software is expressed in a lower-level programming language, such as assembly language (or machine code). In particular embodiments, encoded software is expressed in JAVA. In particular embodiments, encoded software is expressed in Hyper Text Markup Language (HTML), Extensible Markup Language (XML), or other suitable markup language.
Depending on the embodiment, certain acts, events, or functions of any of the algorithms 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). 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.