REFRIGERANT DETECTION SYSTEMS AND METHODS

Abstract

A refrigerant detection system (RDS) implementation system for an HVAC unit includes a tangible, non-transitory, computer-readable medium having instructions stored thereon. The instructions, when executed by processing circuitry, are configured to cause the processing circuitry to prompt a user to input first data indicative of an identity an HVAC unit, prompt the user to input second data indicative of an amount of a refrigerant to be implemented in a refrigerant circuit of the HVAC unit, prompt the user to input third data indicative of a dimension associated with a space to be conditioned by the HVAC unit, determine whether a refrigerant detection system is to be implemented with the HVAC unit based on the first data, the second data, and the third data, and output, via a display, a notification indicative of whether the refrigerant detection system is to be implemented with the HVAC unit

Description

BACKGROUND

This section is intended to introduce the reader to various aspects of art that may be related to various aspects of the present techniques, which are described and/or claimed below. This discussion is believed to be helpful in providing the reader with background information to facilitate a better understanding of the various aspects of the present disclosure. Accordingly, it should be understood that these statements are to be read in this light and not as an admission of any kind.

A heating, ventilation, and/or air conditioning (HVAC) system may be used to control certain environmental parameters, such as temperature and humidity, within a building, home, or other structure. The HVAC system may include a circuit configured to circulate a refrigerant that exchanges heat with a fluid, such as air or water, to cool or heat the fluid. The air may be supplied to the environment in order to condition the environment, or the water may be directed to other equipment to heat or cool air or other fluids. The refrigerant may exchange heat with the fluid via a heat exchanger disposed along the circuit. In some instances, during operation of the HVAC system, refrigerant may inadvertently escape from the HVAC system and/or the circuit, such as via the heat exchanger or other component of the HVAC system. In some applications, it may be desirable to include a refrigeration detection system to detect refrigerant that may inadvertently escape from the HVAC system.

SUMMARY

A summary of certain embodiments disclosed herein is set forth below. It should be understood that these aspects are presented merely to provide the reader with a brief summary of these certain embodiments and that these aspects are not intended to limit the scope of this disclosure. Indeed, this disclosure may encompass a variety of aspects that may not be set forth below.

In one embodiment, a refrigerant detection system (RDS) implementation tool for a heating, ventilation, and air conditioning (HVAC) unit includes processing circuity and a tangible, non-transitory, computer-readable medium including instructions stored thereon. The instructions, when executed by the processing circuitry, are configured to cause the processing circuitry to receive first data indicative of an amount of a refrigerant to be implemented in a refrigerant circuit of the HVAC unit and compare the first data to a predetermined value corresponding to the amount of the refrigerant. The instructions, when executed by the processing circuitry, are also configured to cause the processing circuitry to receive second data indicative of dimensions associated with a space to be conditioned by the HVAC unit, where the second data includes a vertical distance extending from a floor of the space to a duct outlet configured to direct air flow from the HVAC unit into the space. The instructions, when executed by the processing circuitry, are further configured to cause the processing circuitry to determine whether implementation of a refrigerant detection system with the HVAC unit is mandated based on the first data and the second data and to output, via a display, a notification indicating whether implementation of the refrigerant detection system is mandated.

In another embodiment, a refrigerant detection system (RDS) implementation system for a heating, ventilation, and air conditioning (HVAC) unit includes a tangible, non-transitory, computer-readable medium having instructions stored thereon. The instructions, when executed by processing circuitry, are configured to cause the processing circuitry to prompt a user to input first data indicative of an identity an HVAC unit, prompt the user to input second data indicative of an amount of a refrigerant to be implemented in a refrigerant circuit of the HVAC unit, and prompt the user to input third data indicative of a dimension associated with a space to be conditioned by the HVAC unit. The instructions, when executed by processing circuitry, are also configured to cause the processing circuitry to determine whether a refrigerant detection system is to be implemented with the HVAC unit based on the first data, the second data, and the third data and to output, via a display, a notification indicative of whether the refrigerant detection system is to be implemented with the HVAC unit.

In a further embodiment, a refrigerant detection system (RDS) implementation system for a heating, ventilation, and air conditioning (HVAC) unit includes processing circuity and a tangible, non-transitory, computer-readable medium comprising instructions stored thereon. The instructions, when executed by the processing circuitry, are configured to cause the processing circuitry to receive first data indicative of a configuration of the HVAC unit, where the first data includes a serial number of the HVAC unit, an operating mode of the HVAC unit, a product line of the HVAC unit, or a combination thereof and to receive second data indicative of an amount of a refrigerant to be implemented in a refrigerant circuit of the HVAC unit. The instructions, when executed by the processing circuitry, are also configured to cause the processing circuitry to receive third data indicative of a dimension associated with a space to be conditioned by the HVAC unit, where the dimension is a smallest value of a plurality of dimensions associated with the space, and each dimension of the plurality of dimensions is a respective vertical distance from a floor of the space to a respective duct outlet of a plurality of duct outlets configured to discharge air from the HVAC unit into the space. The instructions, when executed by the processing circuitry, are further configured to cause the processing circuitry to based on the first data, the second data, and the third data, determine whether implementation of a refrigerant detection system with the HVAC unit is mandated by a regulatory standard, output, via a display, a notification indicative of whether implementation of the refrigerant detection system is mandated by the regulatory standard, and in response to a determination that implementation of the refrigerant detection system is mandated by the regulatory standard, output a signal to a controller of the HVAC unit to configure the controller for operation with the refrigerant detection system.

BRIEF DESCRIPTION OF THE DRAWINGS

Various aspects of this disclosure may be better understood upon reading the following detailed description and upon reference to the drawings in which:

FIG. 1 is a perspective view of an embodiment of a building that may utilize a heating, ventilation, and/or air conditioning (HVAC) system in a commercial setting, in accordance with an aspect of the present disclosure;

FIG. 2 is a perspective view of an embodiment of a packaged HVAC unit, in accordance with an aspect of the present disclosure;

FIG. 3 is a perspective view of an embodiment of a split, residential HVAC system, in accordance with an aspect of the present disclosure;

FIG. 4 is a schematic diagram of an embodiment of a vapor compression system that may be used in an HVAC system, in accordance with an aspect of the present disclosure;

FIG. 5 is a partial perspective view of an embedment of a building and an HVAC system configured to supply air to multiple zones within the building, in accordance with an aspect of the present disclosure;

FIG. 6 is a schematic of an embodiment of a screen of a graphical user interface that may be utilized in a refrigerant detection system analysis tool, in accordance with an aspect of the present disclosure;

FIG. 7 is a schematic of an embodiment of a screen of a graphical user interface that may be utilized in a refrigerant detection system analysis tool, in accordance with an aspect of the present disclosure;

FIG. 8 is a schematic of an embodiment of a screen of a graphical user interface that may be utilized in a refrigerant detection system analysis tool, in accordance with an aspect of the present disclosure;

FIG. 9 is a schematic of an embodiment of a screen of a graphical user interface that may be utilized in a refrigerant detection system analysis tool, in accordance with an aspect of the present disclosure;

FIG. 10 is a schematic of an embodiment of a screen of a graphical user interface that may be utilized in a refrigerant detection system analysis tool, in accordance with an aspect of the present disclosure;

FIG. 11 is a schematic of an embodiment of a screen of a graphical user interface that may be utilized in a refrigerant detection system analysis tool, in accordance with an aspect of the present disclosure;

FIG. 12 is a schematic of an embodiment of a screen of a graphical user interface that may be utilized in a refrigerant detection system analysis tool, in accordance with an aspect of the present disclosure;

FIG. 13 is a schematic of an embodiment of a screen of a graphical user interface that may be utilized in a refrigerant detection system analysis tool, in accordance with an aspect of the present disclosure;

FIG. 14 is a flow diagram of an embodiment of a method for evaluating a building for implementation of a refrigerant detection system, in accordance with an aspect of the present disclosure;

FIG. 15 is a flow diagram of an embodiment of a method for evaluating a building for implementation of a refrigerant detection system, in accordance with an aspect of the present disclosure;

FIG. 16 is a flow diagram of an embodiment of a method for evaluating a building for implementation of a refrigerant detection system, in accordance with an aspect of the present disclosure;

FIG. 17 is a flow diagram of an embodiment of a method for evaluating a building for implementation of a refrigerant detection system, in accordance with an aspect of the present disclosure;

FIG. 18 is a flow diagram of an embodiment of a method for evaluating a building for implementation of a refrigerant detection system, in accordance with an aspect of the present disclosure;

FIG. 19 is a flow diagram of an embodiment of a method for evaluating a building for implementation of a refrigerant detection system, in accordance with an aspect of the present disclosure;

FIG. 20 is a schematic of an embodiment of a screen of a graphical user interface that may be utilized in a refrigerant detection system analysis tool, in accordance with an aspect of the present disclosure;

FIG. 21 is a schematic of an embodiment of a screen of a graphical user interface that may be utilized in a refrigerant detection system analysis tool, in accordance with an aspect of the present disclosure;

FIG. 22 is a schematic of an embodiment of a screen of a graphical user interface that may be utilized in a refrigerant detection system analysis tool, in accordance with an aspect of the present disclosure;

FIG. 23 is a schematic of an embodiment of a screen of a graphical user interface that may be utilized in a refrigerant detection system analysis tool, in accordance with an aspect of the present disclosure;

FIG. 24 is a schematic of an embodiment of a screen of a graphical user interface that may be utilized in a refrigerant detection system analysis tool, in accordance with an aspect of the present disclosure; and

FIG. 25 is a flow diagram of an embodiment of a method for evaluating an HVAC unit for implementation of a refrigerant detection system based on a manufacturer designation, in accordance with an aspect of the present disclosure.

DETAILED DESCRIPTION

One or more specific embodiments of the present disclosure will be described below. These described embodiments are examples of the presently disclosed techniques. Additionally, in an effort to provide a concise description of these embodiments, all features of an actual implementation may not be described in the specification. It should be appreciated that in the development of any such actual implementation, as in any engineering or design project, numerous implementation-specific decisions must be made to achieve the developers' specific goals, such as compliance with system-related and business-related constraints, which may vary from one implementation to another. Moreover, it should be appreciated that such a development effort might be complex and time consuming, but would nevertheless be a routine undertaking of design, fabrication, and manufacture for those of ordinary skill having the benefit of this disclosure.

When introducing elements of various embodiments of the present disclosure, the articles “a,” “an,” and “the” are intended to mean that there are one or more of the elements. The terms “comprising,” “including,” and “having” are intended to be inclusive and mean that there may be additional elements other than the listed elements. Additionally, it should be understood that references to “one embodiment” or “an embodiment” of the present disclosure are not intended to be interpreted as excluding the existence of additional embodiments that also incorporate the recited features.

As mentioned above, a heating, ventilation, and/or air conditioning (HVAC) system may be used to thermally regulate an environment, such as a building, home, or other structure. For example, a refrigerant circuit of the HVAC system may circulate a refrigerant that exchanges heat with an air flow to be provided to the environment, thereby cooling or heating the air flow. A heat exchanger disposed along the circuit may direct the refrigerant therethrough, and the air flow may be directed over or across the heat exchanger to facilitate heat exchange between the refrigerant and the air flow. In some instances, refrigerant may inadvertently escape from the HVAC system (e.g., refrigerant circuit), such as at or proximate to the heat exchanger. For example, refrigerant may escape from a coupling or joint between components of the heat exchanger, from tubing of the heat exchanger, from conduits of the refrigerant circuit, from another portion of the heat exchanger, and/or from other components of the refrigerant circuit. In some circumstances, the escaped (e.g., leaked) refrigerant may mix with the air flow and/or other fluids circulating through the HVAC system.

As will be appreciated, it may be desirable to detect refrigerant that inadvertently escapes from the refrigerant circuit and/or components of the refrigerant circuit. For example, it may be desirable to detect an operating parameter of the HVAC system that is indicative of potential escape of refrigerant. Additionally or alternatively, it may be desirable to detect the presence of refrigerant that has escaped from the refrigerant circuit and is external to the refrigerant circuit. Accordingly, some HVAC systems may include a refrigerant detection system configured to detect one or more indications that are indicative of escaped refrigerant and/or a refrigerant leak. Moreover, in certain applications, incorporation of a refrigerant detection system in an HVAC system may be mandated by one or more regulatory standards or guidelines. For example, incorporation of a refrigerant detection system in an HVAC system may be mandated for particular implementations or installations of the HVAC system. A determination of whether or not implementation a refrigerant detection system is mandated for a particular HVAC system and/or implementation of the HVAC system may be based on numerous factors, such as a type of the HVAC system, a configuration of the HVAC system, operating modes of the HVAC system, a type of refrigerant utilized by the HVAC system, an amount of refrigerant utilized by the HVAC system, a building or space to be serviced by the HVAC system, one or more characteristics of the building or space to be serviced by the HVAC system, and so forth. Thus, it may be difficult or challenging to determine whether a refrigerant detection system should be incorporated with an HVAC system, for example, in order to comply with regulatory standards or guidelines.

Accordingly, present embodiments are directed to refrigerant detection system (RDS) analysis system (e.g., calculator, tool, assessment system) configured to evaluate, analyze, process, and assess characteristics of an HVAC system and a building with which the HVAC system is to be utilized in order to determine whether a refrigerant detection system should be incorporated with the HVAC system. In particular, present embodiments include systems and methods configured to determine whether a refrigerant detection system should be incorporated with the HVAC system, based on characteristics of the HVAC system and the building, in order to satisfy and comply with regulatory standards.

Turning now to the drawings, FIG. 1 illustrates an embodiment of a heating, ventilation, and/or air conditioning (HVAC) system for environmental management that may employ one or more HVAC units. As used herein, an HVAC system includes any number of components configured to enable regulation of parameters related to climate characteristics, such as temperature, humidity, air flow, pressure, air quality, and so forth. For example, an “HVAC system” as used herein is defined as conventionally understood and as further described herein. Components or parts of an “HVAC system” may include, but are not limited to, all, some of, or individual parts such as a heat exchanger, a heater, an air flow control device, such as a fan, a sensor configured to detect a climate characteristic or operating parameter, a filter, a control device configured to regulate operation of an HVAC system component, a component configured to enable regulation of climate characteristics, or a combination thereof. An “HVAC system” is a system configured to provide such functions as heating, cooling, ventilation, dehumidification, pressurization, refrigeration, filtration, or any combination thereof. The embodiments described herein may be utilized in a variety of applications to control climate characteristics, such as residential, commercial, industrial, transportation, or other applications where climate control is desired.

In the illustrated embodiment, a building 10 is air conditioned by a system that includes an HVAC unit 12. The building 10 may be a commercial structure or a residential structure. As shown, the HVAC unit 12 is disposed on the roof of the building 10; however, the HVAC unit 12 may be located in other equipment rooms or areas adjacent the building 10. The HVAC unit 12 may be a single package unit containing other equipment, such as a blower, integrated air handler, and/or auxiliary heating unit. In other embodiments, the HVAC unit 12 may be part of a split HVAC system, such as the system shown in FIG. 3, which includes an outdoor HVAC unit 58 and an indoor HVAC unit 56.

The HVAC unit 12 is an air cooled device that implements a refrigeration cycle to provide conditioned air to the building 10. Specifically, the HVAC unit 12 may include one or more heat exchangers across which an air flow is passed to condition the air flow before the air flow is supplied to the building. In the illustrated embodiment, the HVAC unit 12 is a rooftop unit (RTU) that conditions a supply air stream, such as environmental air and/or a return air flow from the building 10. After the HVAC unit 12 conditions the air, the air is supplied to the building 10 via ductwork 14 extending throughout the building 10 from the HVAC unit 12. For example, the ductwork 14 may extend to various individual floors or other sections of the building 10. In certain embodiments, the HVAC unit 12 may be a heat pump that provides both heating and cooling to the building with one refrigeration circuit configured to operate in different modes. In other embodiments, the HVAC unit 12 may include one or more refrigeration circuits for cooling an air stream and a furnace for heating the air stream.

A control device 16, one type of which may be a thermostat, may be used to designate the temperature of the conditioned air. The control device 16 also may be used to control the flow of air through the ductwork 14. For example, the control device 16 may be used to regulate operation of one or more components of the HVAC unit 12 or other components, such as dampers and fans, within the building 10 that may control flow of air through and/or from the ductwork 14. In some embodiments, other devices may be included in the system, such as pressure and/or temperature transducers or switches that sense the temperatures and pressures of the supply air, return air, and so forth. Moreover, the control device 16 may include computer systems that are integrated with or separate from other building control or monitoring systems, and even systems that are remote from the building 10.

FIG. 2 is a perspective view of an embodiment of the HVAC unit 12. In the illustrated embodiment, the HVAC unit 12 is a single package unit that may include one or more independent refrigeration circuits and components that are tested, charged, wired, piped, and ready for installation. The HVAC unit 12 may provide a variety of heating and/or cooling functions, such as cooling only, heating only, cooling with electric heat, cooling with dehumidification, cooling with gas heat, or cooling with a heat pump. As described above, the HVAC unit 12 may directly cool and/or heat an air stream provided to the building 10 to condition a space in the building 10.

As shown in the illustrated embodiment of FIG. 2, a cabinet 24 encloses the HVAC unit 12 and provides structural support and protection to the internal components from environmental and other contaminants. In some embodiments, the cabinet 24 may be constructed of galvanized steel and insulated with aluminum foil faced insulation. Rails 26 may be joined to the bottom perimeter of the cabinet 24 and provide a foundation for the HVAC unit 12. In certain embodiments, the rails 26 may provide access for a forklift and/or overhead rigging to facilitate installation and/or removal of the HVAC unit 12. In some embodiments, the rails 26 may fit into “curbs” on the roof to enable the HVAC unit 12 to provide air to the ductwork 14 from the bottom of the HVAC unit 12 while blocking elements such as rain from leaking into the building 10.

The HVAC unit 12 includes heat exchangers 28 and 30 in fluid communication with one or more refrigeration circuits. Tubes within the heat exchangers 28 and 30 may circulate refrigerant, such as R-410A, R-454B, or other suitable refrigerant, through the heat exchangers 28 and 30. The tubes may be of various types, such as multichannel tubes, conventional copper or aluminum tubing, and so forth. Together, the heat exchangers 28 and 30 may implement a thermal cycle in which the refrigerant undergoes phase changes and/or temperature changes as it flows through the heat exchangers 28 and 30 to produce heated and/or cooled air. For example, the heat exchanger 28 may function as a condenser where heat is released from the refrigerant to ambient air, and the heat exchanger 30 may function as an evaporator where the refrigerant absorbs heat to cool an air stream. In other embodiments, the HVAC unit 12 may operate in a heat pump mode where the roles of the heat exchangers 28 and 30 may be reversed. That is, the heat exchanger 28 may function as an evaporator and the heat exchanger 30 may function as a condenser. In further embodiments, the HVAC unit 12 may include a furnace for heating the air stream that is supplied to the building 10. While the illustrated embodiment of FIG. 2 shows the HVAC unit 12 having two of the heat exchangers 28 and 30, in other embodiments, the HVAC unit 12 may include one heat exchanger or more than two heat exchangers.

The heat exchanger 30 is located within a compartment 31 that separates the heat exchanger 30 from the heat exchanger 28. Fans 32 draw air from the environment through the heat exchanger 28. Air may be heated and/or cooled as the air flows through the heat exchanger 28 before being released back to the environment surrounding the rooftop unit 12. A blower assembly 34, powered by a motor 36, draws air through the heat exchanger 30 to heat or cool the air. The heated or cooled air may be directed to the building 10 by the ductwork 14, which may be connected to the HVAC unit 12. Before flowing through the heat exchanger 30, the conditioned air flows through one or more filters 38 that may remove particulates and contaminants from the air. In certain embodiments, the filters 38 may be disposed on the air intake side of the heat exchanger 30 to prevent contaminants from contacting the heat exchanger 30.

The HVAC unit 12 also may include other equipment for implementing the thermal cycle. Compressors 42 increase the pressure and temperature of the refrigerant before the refrigerant enters the heat exchanger 28. The compressors 42 may be any suitable type of compressors, such as scroll compressors, rotary compressors, screw compressors, or reciprocating compressors. In some embodiments, the compressors 42 may include a pair of hermetic direct drive compressors arranged in a dual stage configuration 44. However, in other embodiments, any number of the compressors 42 may be provided to achieve various stages of heating and/or cooling. As may be appreciated, additional equipment and devices may be included in the HVAC unit 12, such as a solid-core filter drier, a drain pan, a disconnect switch, an economizer, pressure switches, phase monitors, and humidity sensors, among other things.

The HVAC unit 12 may receive power through a terminal block 46. For example, a high voltage power source may be connected to the terminal block 46 to power the equipment. The operation of the HVAC unit 12 may be governed or regulated by a control board 48. The control board 48 may include control circuitry connected to a thermostat, sensors, and alarms. One or more of these components may be referred to herein separately or collectively as the control device 16. The control circuitry may be configured to control operation of the equipment, provide alarms, and monitor safety switches. Wiring 49 may connect the control board 48 and the terminal block 46 to the equipment of the HVAC unit 12.

FIG. 3 illustrates a residential heating and cooling system 50, also in accordance with present techniques. The residential heating and cooling system 50 may provide heated and cooled air to a residential structure, as well as provide outside air for ventilation and provide improved indoor air quality (IAQ) through devices such as ultraviolet lights and air filters. In the illustrated embodiment, the residential heating and cooling system 50 is a split HVAC system. In general, a residence 52 conditioned by a split HVAC system may include refrigerant conduits 54 that operatively couple the indoor unit 56 to the outdoor unit 58. The indoor unit 56 may be positioned in a utility room, an attic, a basement, and so forth. The outdoor unit 58 is typically situated adjacent to a side of residence 52 and is covered by a shroud to protect the system components and to prevent leaves and other debris or contaminants from entering the unit. The refrigerant conduits 54 transfer refrigerant between the indoor unit 56 and the outdoor unit 58, typically transferring primarily liquid refrigerant in one direction and primarily vaporized refrigerant in an opposite direction.

When the residential heating and cooling system 50 shown in FIG. 3 is operating as an air conditioner, a heat exchanger 60 in the outdoor unit 58 serves as a condenser for re-condensing vaporized refrigerant flowing from the indoor unit 56 to the outdoor unit 58 via one of the refrigerant conduits 54. In these applications, a heat exchanger 62 of the indoor unit 56 functions as an evaporator. Specifically, the heat exchanger 62 receives liquid refrigerant, which may be expanded by an expansion device, and evaporates the refrigerant before returning it to the outdoor unit 58.

The outdoor unit 58 draws environmental air through the heat exchanger 60 using a fan 64 and expels the air above the outdoor unit 58. When operating as an air conditioner, the air is heated by the heat exchanger 60 within the outdoor unit 58 and exits the unit at a temperature higher than it entered. The indoor unit 56 includes a blower or fan 66 that directs air through or across the heat exchanger 62, where the air is cooled when the residential heating and cooling system 50 is operating in air conditioning mode. Thereafter, the air is passed through ductwork 68 that directs the air to the residence 52. The overall system operates to maintain a desired temperature as set by a system controller. When the temperature sensed inside the residence 52 is higher than the set point on the thermostat, or a set point plus a small amount, the residential heating and cooling system 50 may become operative to refrigerate additional air for circulation through the residence 52. When the temperature reaches the set point, or a set point minus a small amount, the residential heating and cooling system 50 may stop the refrigeration cycle temporarily.

The residential heating and cooling system 50 may also operate as a heat pump. When operating as a heat pump, the roles of heat exchangers 60 and 62 are reversed. That is, the heat exchanger 60 of the outdoor unit 58 will serve as an evaporator to evaporate refrigerant and thereby cool air entering the outdoor unit 58 as the air passes over the heat exchanger 60. The heat exchanger 62 will receive a stream of air blown across the heat exchanger 62 and will heat the air by condensing the refrigerant.

In some embodiments, the indoor unit 56 may include a furnace system 70. For example, the indoor unit 56 may include the furnace system 70 when the residential heating and cooling system 50 is not configured to operate as a heat pump. The furnace system 70 may include a burner assembly and a corresponding heat exchanger, among other components, inside the indoor unit 56. Fuel is provided to the burner assembly of the furnace 70 where it is mixed with air and combusted to form combustion products. The combustion products may pass through tubes or piping of the corresponding heat exchanger, separate from the heat exchanger 62, such that air directed by the blower 66 passes over the tubes or pipes and extracts heat from the combustion products. The heated air may then be routed from the furnace system 70 to the ductwork 68 for heating the residence 52.

FIG. 4 is a schematic of an embodiment of a vapor compression system 72 that can be used in any of the systems described above. The vapor compression system 72 may circulate a refrigerant through a circuit starting with a compressor 74. The circuit may also include a condenser 76, an expansion valve(s) or device(s) 78, and an evaporator 80. The vapor compression system 72 may further include a control panel 82 that has an analog to digital (A/D) converter 84, a microprocessor 86, a non-volatile memory 88, and/or an interface board 90. The control panel 82 and its components may function to regulate operation of the vapor compression system 72 based on feedback from an operator, from sensors of the vapor compression system 72 that detect operating conditions, and so forth.

In some embodiments, the vapor compression system 72 may use one or more of a variable speed drive (VSDs) 92, a motor 94, the compressor 74, the condenser 76, the expansion valve or device 78, and/or the evaporator 80. The motor 94 may drive the compressor 74 and may be powered by the variable speed drive (VSD) 92. The VSD 92 receives alternating current (AC) power having a particular fixed line voltage and fixed line frequency from an AC power source, and provides power having a variable voltage and frequency to the motor 94. In other embodiments, the motor 94 may be powered directly from an AC or direct current (DC) power source. The motor 94 may include any type of electric motor that can be powered by a VSD (e.g., VSD 92) or directly from an AC or DC power source, such as a switched reluctance motor, an induction motor, an electronically commutated permanent magnet motor, or another suitable motor.

The compressor 74 compresses a refrigerant vapor and delivers the vapor to the condenser 76 through a discharge passage. In some embodiments, the compressor 74 may be a centrifugal compressor. The refrigerant vapor delivered by the compressor 74 to the condenser 76 may transfer heat to a fluid passing across the condenser 76, such as ambient or environmental air 96. The refrigerant vapor may condense to a refrigerant liquid in the condenser 76 as a result of thermal heat transfer with the environmental air 96. The liquid refrigerant from the condenser 76 may flow through the expansion device 78 to the evaporator 80.

The liquid refrigerant delivered to the evaporator 80 may absorb heat from another air stream, such as a supply air stream 98 provided to the building 10 or the residence 52. For example, the supply air stream 98 may include ambient or environmental air, return air from a building, or a combination of the two. The liquid refrigerant in the evaporator 80 may undergo a phase change from the liquid refrigerant to a refrigerant vapor. In this manner, the evaporator 80 may reduce the temperature of the supply air stream 98 via thermal heat transfer with the refrigerant. Thereafter, the vapor refrigerant exits the evaporator 80 and returns to the compressor 74 by a suction line to complete the cycle.

In some embodiments, the vapor compression system 72 may further include a reheat coil in addition to the evaporator 80. For example, the reheat coil may be positioned downstream of the evaporator 80 relative to the supply air stream 98 and may reheat the supply air stream 98 when the supply air stream 98 is overcooled to remove humidity from the supply air stream 98 before the supply air stream 98 is directed to the building 10 or the residence 52.

It should be appreciated that any of the features described herein may be utilized in conjunction with embodiments of the HVAC unit 12, the residential heating and cooling system 50, or other HVAC systems. Additionally, while the features disclosed herein are described in the context of embodiments that directly heat and cool a supply air stream provided to a building or other load, embodiments of the present disclosure may be applicable to other HVAC systems as well. For example, the features described herein may be utilized in conjunction with systems that include mechanical cooling systems, free cooling systems, chiller systems, or other heat pump or refrigeration applications.

The description above with reference to FIGS. 1-4 is intended to be illustrative of the context of the present disclosure. Accordingly, it should be noted that the embodiments of the present disclosure may include any of features of the description above. As will be discussed in more detail below, embodiments of the present disclosure a refrigerant detection system (RDS) analysis system (e.g., calculator, tool, assessment system) configured to evaluate, analyze, process, and assess characteristics of an HVAC system and a building with which the HVAC system is to be utilized in order to determine whether a refrigerant detection system (RDS) should be incorporated with the HVAC system. In particular, present embodiments include systems and methods configured to determine whether an RDS should be incorporated with the HVAC system, based on characteristics of the HVAC system and the building, in order to satisfy and comply with regulatory standards. It should be appreciated that embodiments of the RDS analysis system described herein may be utilized with any suitable HVAC system, such as the HVAC system 12 (e.g., a packaged unit), the residential heating and cooling system 50 (e.g., a split system), a heat pump, a hybrid heat pump, a commercial HVAC system, an HVAC system configured to provide cooling only, an HVAC system configured to provide electric heat, an HVAC system configured to provide gas heat, an HVAC system configured to provide hydronic heat, and so forth. Additionally, embodiments of the RDS analysis system described herein may be configured to assess and determine whether an RDS should be implemented with an HVAC system configured to utilized any suitable refrigerant, such as R-454B. In some implementations, the present techniques may be utilized to assess and determine whether an RDS should be implemented with an HVAC system in order to comply with any suitable or desired regulatory standards or guidelines such as the UL 60335-2-40, ASHRAE 15 guidelines, and so forth.

With the foregoing in mind, FIG. 5 is a perspective view of an embodiment of a building 100 and an HVAC system 102 configured to supply conditioned air to the building 100. For example, the HVAC system 102 may be an embodiment of the HVAC unit 12 described above. In some instances, it may be desirable or mandated that a refrigerant detection system (RDS) 104 (e.g., refrigerant detection sensor) be implemented with the HVAC system 102. For example, one or more regulatory standards or guidelines may mandate that the RDS 104 be implemented with the HVAC system 102 to detect refrigerant escaped from the HVAC system 102 and/or detect an indication that refrigerant has escaped or may potentially escape from the HVAC system 102. Accordingly, present embodiments include an RDS analysis system 106 (e.g., RDS tool, RDS implementation tool, RDS calculator, RDS application assessment system, refrigerant detection management system, RDS implementation system) configured to process, evaluate, and analyze characteristics of the HVAC system 102 and the building 100 to determine whether the RDS 104 is to be incorporated with the HVAC system 102, such as to satisfy or comply with one or more regulatory standards. The RDS analysis system 106 may be utilized by a manufacturer of the HVAC unit 108, a customer intending to order (e.g., purchase) the HVAC unit 108, an installer and/or technician of the HVAC unit 108, a sales representative, and/or any other suitable person or entity. For example, the RDS analysis system 106 may be utilized during an ordering and/or configuration process of the HVAC unit 108.

In the illustrated embodiment, the HVAC system 102 includes an HVAC unit 108 configured to discharge supply air and direct the supply air into the building 100 via a system of ductwork 110. More specifically, the ductwork 110 extends from the HVAC unit 108 to an interior of the building 100. The building 100 may include one zone or multiple zones configured to receive the supply air from the HVAC unit 108 via the ductwork 110. In the illustrated embodiment, the building 100 includes multiple (e.g., eight) zones 112. The various zones 112 may be at least partially separated from one another within the building 100 via walls, doors, windows, and so forth. The ductwork 110 includes various ducts 114 that extend to the zones 112. Each duct 114 terminates at one or more discharge outlets 116 (e.g., duct outlets) associated with one of the zones 112 and is configured to discharge a flow of the supply air into the corresponding zone 112.

As described in further detail below, the RDS analysis system 106 (e.g., RDS implementation tool) may be configured to evaluate characteristics of one or more of the zones 112 to determine whether the RDS 104 should be implemented with the HVAC system 102 (e.g., the HVAC unit 108) in order to comply with one or more regulatory standards. For example, the RDS analysis system 106 may assess, evaluate, and/or process a size (e.g., volume, respective sizes) of the zones 112 based on dimensions of each zone 112, such as a width 118 and a length 120 of each zone 112. Additionally, the RDS analysis system 106 may determine whether the RDS 104 should be implemented with the HVAC system 102 based on (e.g., for each zone 112) a height 122 extending from a floor 124 of the zone 112 to the discharge outlet 116 (e.g., diffuser, register) corresponding to the zone 112. The RDS analysis system 106 may also evaluate other characteristics to determine whether the RDS 104 should be implemented with the HVAC system 102, such as a type of the HVAC unit 108, a configuration of the HVAC unit 108, a type of refrigerant utilized in the HVAC unit 108, an amount (e.g., charge) of refrigerant utilized in the HVAC unit 108 (e.g., a refrigerant circuit of the HVAC unit 108), and so forth. Operation of the RDS analysis system 106 is described in further detail below.

The RDS analysis system 106 (e.g., RDS implementation tool) may include a computing device 126 (e.g., computer system, computing tool) configured to perform (e.g., execute) one or more of the techniques and/or processes described herein. For example, the computing device 126 may be a personal computer, a laptop, a mobile phone, a tablet, a portable user device, and/or any other suitable device configured to execute programmable instructions (e.g., code). In some embodiments, the computing device 126 may be a component of the HVAC unit 108 (e.g., control board 48, control panel 82).

As shown, the computing device 126 may include processing circuitry 128, such as one or more microprocessors, which may execute software to perform one or more of the techniques described herein. The processing circuitry 128 may include multiple microprocessors, one or more “general-purpose” microprocessors, one or more special-purpose microprocessors, and/or one or more application specific integrated circuits (ASICS), or some combination thereof. For example, the processing circuitry 128 may include one or more reduced instruction set (RISC) processors. The computing device 126 may also include a memory device 130 (e.g., memory) that may store information, such as instructions, control software, look up tables, configuration data, etc. The memory device 130 may include a volatile memory, such as random access memory (RAM), and/or a nonvolatile memory, such as read-only memory (ROM). The memory device 130 may store a variety of information and may be used for various purposes. For example, the memory device 130 may store processor-executable instructions including firmware or software for the processing circuitry 128 execute, such as instructions for evaluating, analyzing, and/or assessing characteristics of the HVAC unit 108 and the building 100 (e.g., the zones 112) in order to determine whether the RDS 104 is to be incorporated with the HVAC system 102 (e.g., mandated, in order to comply with a regulatory standard). In some embodiments, the memory device 130 includes one or more tangible, non-transitory, machine-readable-media that may store machine-readable instructions for the processing circuitry 128 to execute. The memory device 130 may include ROM, flash memory, a hard drive, or any other suitable optical, magnetic, or solid-state storage medium, or a combination thereof. The memory device 130 may store data, instructions, and any other suitable data. It should be appreciated that the memory device 130 may store executable instructions that may be executed by the processing circuitry 128 to perform one or more of the methods and techniques described herein.

The computing device 126 may also include a display 132 (e.g., display device, screen) and a user interface 134 configured to receive user input. In some embodiments, the display 132 may be a touchscreen configured to additionally function as the user interface 134. Additionally or alternatively, the user interface 134 may include a button, scroll wheel, switch, and/or other component configured to receive user input. The user interface 134 may be utilized to receive user input from a user, such as input indicative of characteristics of the building 100 and/or the HVAC system 102 (e.g., HVAC unit 108), as described further below. The display 132 may be configured to output one or more indications or notifications to the user. For example, the processing circuitry 128 may be configured to generate and display a graphical user interface (GUI) on the display 132, and a user may utilize the GUI to provide user input to the computing device 126. The processing circuitry 128 may also output one or more notifications or indications to the user via the display 132 and/or the user interface 134.

FIGS. 6-13 are illustrations of embodiments of a graphical user interface (GUI) 150 that may be displayed via the display 132 (e.g., touchscreen) of the computing device 126 to enable functionalities of embodiments of the RDS analysis system 106 described herein. For example, FIG. 6 illustrates a first screen 152 displaying multiple selectable icons 154 (e.g., images, menus, options, fields) that a user may select to enable and utilize various functionalities and/or operations of the RDS analysis system 106, such searching for a particular embodiment of the HVAC unit 108 (e.g., stored on the memory device 130) based on a type of the HVAC unit 108 (e.g., a configuration of the HVAC unit 108, a characteristic of the HVAC unit 108, a model of the HVAC unit 108, a product line of the HVAC unit 108). The first screen 152 also includes a calculator icon 156 that may be selected by a user to access a second screen 158 of the GUI 150. The second screen 158 is included in the GUI 150 illustrated in FIG. 7, and the second screen 158 includes additional selectable icons 154 associated with various calculating functions that may be performed by the computing device 126. As shown, the selectable icons 154 of the second screen 158 include an RDS calculator icon 160 that a user may select to access and/or initialize certain functionalities and/or operations of the RDS analysis system 106.

For example, upon selection of the RDS calculator icon 160, the processing circuitry 128 may cause the GUI 150 to display a third screen 162, as shown in FIG. 8. The third screen 162 may prompt a user to input various information and/or data, such as a name (e.g., “job name”) of the particular implementation of the HVAC unit 108, a name of the HVAC unit 108, a serial number of the HVAC unit 108 (e.g., identifier of the HVAC unit, unique identifier of the HVAC unit), and a type of the building 100. In some embodiments, the third screen 162 of the GUI 150 may display a menu (e.g., pulldown menu) to select a type of the building 100, such as a data center, a lab, a hospital, manufactured housing, a multi-family residence, a church, an office building, a school, a retail building, a warehouse, a residential building, a recreational building, a multi-level building, or any other suitable type of structure with which the HVAC system 102 (e.g., HVAC unit 108) may be implemented.

As shown in FIG. 9, the processing circuitry 128 may also cause the GUI 150 to display a fourth screen 164 configured to enable user input of information and/or characteristics of the HVAC unit 108. For example, the fourth screen 164 of the GUI 150 may present various selectable unit types 166 of the HVAC unit 108. The fourth screen 164 may also enable user input indicative of a configuration of the HVAC unit 108, such as a cooling only configuration, an electric heat configuration, a gas heat configuration, a heat pump configuration, a hybrid heat pump configuration, or any other suitable type of HVAC unit 108 configuration. As shown, the fourth screen 164 also includes refrigerant charge input field 168. In some embodiments, a user may select the refrigerant charge input field 168, and the processing circuitry 128 may cause the GUI 150 to enable the user to input a value (e.g., number) indicative of an amount or charge of refrigerant (e.g., in pounds or other suitable unit) that is or will be included in the HVAC unit 108 (e.g., in a refrigerant circuit of the HVAC unit 108).

FIG. 10 illustrates a fifth screen 170 of the GUI 150 that is configured to enable input of various characteristics of the building 100. For example, the fifth screen 170 may be utilized to enable user input of a number of zones 112 within the building 100. In some embodiments, the building 100 may have one zone 112, but other embodiments of the building 100 may include multiple zones 112. In some applications, the GUI 150 may instruct a user to input information regarding zones 112 in a lower floor of the building 100. For each zone 112, a user may utilize the GUI 150 to input respective characteristics (e.g., measurements, dimensions) of the zone 112. For example, FIG. 11 illustrates a sixth screen 172 of the GUI 150 that may be utilized to input the respective width 118, length 120, and smallest duct discharge height 122 (e.g., vertical distance from the respective floor 124 to the discharge outlet 116) of each zone 112 (e.g., metric units, imperial units). It should be appreciated that the smallest duct discharge height may correspond to the height 122 extending from the floor 124 to the discharge outlet 116 (e.g., duct discharge) of the zone 112 with the smallest value. For example, if one of the zones 112 includes two discharge outlets 116 disposed at different corresponding heights 122 (e.g., vertical distance) from the floor 124 of the zone 112, the user may input the height 122 having the smallest dimension via the sixth screen 172. In some embodiments, a value of the user input for the smallest duct discharge height may be limited or constrained by the RDS analysis system 106 (e.g., equal to or greater than 2 feet, equal to or less than 9 feet). In some embodiments, the RDS analysis system 106 may output an indication that the RDS 104 is required in response to input of a smallest duct discharge height of less than a particular or predetermined value (e.g., 2 feet). Further, in some embodiments, the RDS analysis system 106 may prompt the user to input the smallest duct discharge height for the building 100 (e.g., overall smallest duct discharge height) or the smallest duct discharge height for each floor of the building 100 instead of the smallest duct discharge height for each zone 112.

Upon entry of the user input prompted by and entered via the various screens of the GUI 150 described above, the RDS analysis system 106 may evaluate (e.g., compare, perform calculations) the data input by the user to determine whether implementation of the RDS 104 is mandated, such as in accordance with one or more regulatory standards. Details of the assessment and determination performed by the RDS analysis system 106 is described further below. Based on the determination, the processing circuitry 128 may cause the GUI 150 to display a seventh screen 174, as illustrated in FIG. 12. Via the seventh screen 174, the processing circuitry 128 may output various information related to the assessments (e.g., calculations, processes) performed by, and the determinations made by, the RDS analysis system 106. For example, the seventh screen 174 may display a total area (e.g., square footage) of the building 100 (e.g., cumulative area of the zones 112) determined based on the user input. Based on the user input, the RDS analysis system 106 may also determine a maximum or upper limit of refrigerant charge of the HVAC unit 108 that may be utilized without incorporation of the RDS 104. Based on a comparison of the upper limit (e.g., upper allowable limit) of refrigerant charge (e.g., 25 pounds) and the charge of the HVAC unit 108 input by the user (e.g., 27 pounds, via the fourth screen 164), the RDS analysis system 106 may determine that the charge of the HVAC unit 108 exceeds the upper allowable limit without implementation of the RDS 104. Accordingly, the GUI 150 may output an indication that the RDS 104 is mandated, such as to comply with one or more regulatory standards. In some embodiments, in response to a determination that the RDS 104 is mandated, the RDS analysis system 106 may be configured to output a signal (e.g., programming instructions, control signal) to update and/or implement particular programming (e.g., code) for a controller of the HVAC unit 108 (e.g., control board 48, control panel 82), where the particular programming is configured to enable operation of the HVAC unit 108 with the RDS 104 (e.g., refrigerant leak detection operations). The RDS analysis system 106 may also determine whether additional ventilation of the building 100 should be facilitated, such as to comply with one or more regulatory standards, as described further below. In some embodiments, the processing circuitry 128 may further cause the GUI 150 to display an eighth screen 176 on the display 132 to provide the user with a summary of the user input, as well as the determinations made by the RDS analysis system 106, as shown in FIG. 13.

FIGS. 14-19 illustrate flow diagrams of embodiments of various methods that may be implemented and performed by the RDS analysis system 106 to enable and/or perform the functionalities and techniques described herein. As mentioned above, the memory device 130 may store executable instructions that may be executed by the processing circuitry 128 to perform any or all of the methods and techniques described below with reference to FIGS. 14-19. Further, execution of the methods described below may be facilitated by the computing device 126, including the display 132 and/or the user interface 134, described above. It should be appreciated that any (e.g., one or more, all) of the methods described herein may be executed together, simultaneously, and/or in any suitable order (e.g., sequential order). Further, in some embodiments, one or more of the methods may include additional steps, alternative steps, and/or may omit one or more of the steps described herein.

FIG. 14 is a flow diagram of an embodiment of a method 200 that may be implemented (e.g., executed, performed) by the RDS analysis system 106 to determine whether the RDS 104 should (e.g., must) be incorporated with the HVAC system 102 (e.g., HVAC unit 108), based on characteristics of the HVAC unit 108 and the building 100, in order to comply with one or more regulatory standards. As similarly discussed above, the method 200 may be performed based on input provided by a user, such as via the computer device 126 (e.g., user interface 134, display 132).

At block 202, a user may provide and/or input information indicative of characteristics of the HVAC unit 108 and the building 100. For example, the user may input an amount of refrigerant charge (e.g., in pounds) of the HVAC unit 108, a model number of the HVAC unit 108, a configuration and/or type of the HVAC unit 108, one or more parameters associated with piping or conduits of the HVAC unit 108 (e.g., for an embodiment of the HVAC unit 108 configured as a split system), another suitable parameter or characteristic, or any combination thereof. In some embodiments, the HVAC unit 108 may include multiple refrigerant circuits, and each refrigerant circuit may have a respective amount or charge of refrigerant contained therein. In such embodiments, the RDS analysis system 106 may prompt the user to input a value of the largest refrigerant charge utilized by a refrigerant circuit (e.g., of a plurality of refrigerant circuits) in the HVAC unit 108. At block 202, the RDS analysis system 106 may assign the value of the refrigerant charge as mc (e.g., a variable) and may store the value of mc in the memory device 130.

At block 204, the RDS analysis system 106 may compare the value of mc to a lower threshold value and an upper threshold value. The lower threshold value and upper threshold values may be fixed or predetermined values (e.g., stored in the memory device 130). In some embodiments, particular values (e.g., predetermined values) of the lower threshold value and the upper threshold value may be selected or determined based on a type of the refrigerant (e.g., R-454B), a characteristic of the HVAC unit 108, another suitable factor, or a combination thereof. For example, the lower threshold value may be 4 pounds, and the upper threshold value may be 169 pounds. In response to a determination that the value of mc is or less than the lower threshold value and/or in response to a determination that mc is greater than the upper threshold value, the method 200 may proceed to block 206, whereby the method 200 may stop, return to the beginning of the method 200, and/or proceed to an alternative method. In some embodiments, the RDS analysis system 106 may cause the GUI 150 to display the first screen 152 with the menu of selectable icons 154 corresponding to the first screen 152 at block 206. In some embodiments, the method 200 may proceed to block 206 in response to a determination that the value of mc is less than the lower threshold value because regulatory standards may not mandate incorporation of the RDS 104 for HVAC unit 108 with a refrigerant charge less than the lower threshold value. In some embodiments, the method 200 may proceed to block 206 in response to a determination that the value of mc is greater than the upper threshold value because the RDS analysis system 106 may not be configured to analyze and/or assess embodiments of the HVAC unit 108 (e.g., for compliance with regulatory standards) having a refrigerant charge greater than the upper threshold value.

In response to a determination that the value of mc is not less than the lower threshold value and that mc is not greater than the upper threshold value (e.g., the value of mc is equal to or between the lower threshold value and the upper threshold value), the method 200 may proceed to block 208. At block 208, the RDS analysis system 106 may prompt the user to input an indication of whether the HVAC system 102 (e.g., HVAC unit 108, air handling unit, rooftop unit) is configured to supply air (e.g., via the ductwork 110) to multiple zones 112 in the building 100. That is, the user may input an indication (e.g., response to a question or prompt) that the building 100 includes multiple zones 112 to be serviced by the HVAC system 102 or includes one zone 112 serviced by the HVAC system 102 (e.g., HVAC unit 108). In response to a determination (e.g., based on the user input) that the HVAC system 102 is not configured to supply air to multiple zones 112, the method 200 may proceed to block 210. At block 210, the RDS analysis system 106 may prompt the user to input additional characteristics of the building 100 (e.g., the single zone 112), such as the width 118, length 120, and height 122 (e.g., lowest or smallest height from floor 124 to discharge outlet 116) of the zone 112. After block 210, the method 200 may proceed to block 212, which is described in further detail below.

In response to a determination (e.g., based on the user input) at block 208 that the HVAC system 102 (e.g., HVAC unit 108) is configured to supply air to multiple zones 112, the method 200 may proceed to block 214, whereby the RDS analysis system 106 may prompt the user to input an indication of the number of zones 112 (e.g., within the building 100) to be serviced by the HVAC system 102. The method 200 may then proceed to block 216. At block 216, the RDS analysis system 106 may prompt the user to input additional characteristics of each zone 112 of the building 100 that will be serviced by the HVAC system 102. In particular, the RDS analysis system 106 may prompt the user to input the respective width 118 and the respective length 120 of each zone 112. The RDS analysis system 106 may also prompt the user to input a value of the height 122, where the value is the smallest or lowest height 122 for any and/or all of the zones 112 within the building 100 to be serviced by the HVAC system 102. At block 216, the RDS analysis system 106 may also assign the lowest height 122 value input by the user as a value of H, which may be stored in the memory device 130.

After block 216, or alternatively after block 210 discussed above, the method 200 may proceed to block 212. At block 212, the RDS analysis system 106 may compare the value of mc to a predetermined value, which may be stored in the memory device 130. The predetermined value may be any suitable value and, in some embodiments, may be selected or determined based on a type of the refrigerant (e.g., R-454B), a characteristic of the HVAC unit 108, another suitable factor, or any combination thereof. For example, the predetermined value may be 34 pounds (e.g., of refrigerant charge). In some embodiments, the RDS analysis system 106 may determine that embodiments of the HVAC unit 108 having a refrigerant charge greater than the predetermined value should (e.g., must) include the RDS 104 in order to comply with one or more regulatory standards.

In response to a determination that the value of mc is less than the predetermined value, the method 200 may proceed to block 218. In some embodiments, such as embodiments of the HVAC unit 108 configured as a rooftop unit, the RDS analysis system 106 executing the method 200 and proceeding to block 218 may default to indicating that the RDS 104 should be incorporated with the HVAC unit 108, but the RDS analysis system 106 may enable the user to de-select the option of incorporating the RDS 104 with the HVAC unit 108 (e.g., based on additional calculations described below). At block 218, the RDS analysis system 106 may compare the value of mc to the lower threshold value and the predetermined value discussed above. In response to a determination that the value of mc is equal to or greater than the lower threshold value and is equal to or less than the predetermined value, the method 200 may proceed to block 220, whereby the RDS analysis system 106 may execute a first scenario method 250, which is described below with reference to FIG. 15. Alternatively, in some embodiments, block 218 may be omitted from the method 200, and in response to the determination that the value of mc is less than the predetermined value, the method 200 may proceed to block 220 and the first scenario method 250.

In response to a determination that the value of mc is not less than the predetermined value, the method 200 may proceed to block 222. In some embodiments, the RDS analysis system 106 executing the method 200 and proceeding to block 222 may determine that the RDS 104 should be incorporated with the HVAC unit 108 and may block or prevent the user from de-selecting an option or indication of incorporating the RDS 104 with the HVAC unit 108. At block 222, the RDS analysis system 106 may compare the value of mc to the lower threshold value and the upper threshold value discussed above. In response to a determination that the value of mc is not equal to or greater than the lower threshold value and is not equal to or less than the upper threshold value, the method 200 may proceed to block 224, whereby the RDS analysis system 106 may output an indication (e.g., via the display 132) of an error. Additionally or alternatively at block 224, the RDS analysis system 106 may return to block 202 of the method 200. In response to a determination that the value of mc is equal to or greater than the lower threshold value and is equal to or less than the upper threshold value, the method 200 may proceed to block 226, whereby the RDS analysis system 106 may execute a second scenario method 280, which is described below with reference to FIG. 16. In some embodiments, in response to the determination that the value of mc is equal to or greater than the lower threshold value and is equal to or less than the upper threshold value, the RDS analysis system 106 may output an indication that implementation of the RDS 104 with the HVAC unit 108 is mandated.

FIG. 15 is a flow diagram of an embodiment of the first scenario method 250 mentioned above. The first scenario method 250 may begin with block 252, whereby the RDS analysis system 106 may perform one or more calculations to provide one or more values of an area (e.g., square footage) associated with the building 100. In particular, the RDS analysis system 106 may perform a first calculation to determine a value of A_{cal_one} (e.g., first area limit value) utilizing the equation shown in block 252 based on the value of mc, the value of H, and a first constant value (e.g., stored in the memory device 130). The first constant value may be selected or determined (e.g., predetermined) based on a type of the refrigerant (e.g., R-454B), a characteristic of the HVAC unit 108, another suitable factor, or a combination thereof. In some embodiments, the RDS analysis system 106 may be configured to determine (e.g., using artificial intelligence) a value of the first constant value based on one or more of the parameters or characteristics of the HVAC unit 108. For example, the first constant value may be 8.5462.

The RDS analysis system 106 may also perform a second calculation to determine a value of A_{cal_two} (e.g., second area limit value) utilizing the equation shown in block 252 based on the value of mc, the value of H, and a second constant value (e.g., stored in the memory device 130). The second constant value may also be selected or determined (e.g., predetermined) based on a type of the refrigerant (e.g., R-454B), a characteristic of the HVAC unit 108, another suitable factor, or a combination thereof. In some embodiments, the RDS analysis system 106 may be configured to determine (e.g., using artificial intelligence) a value of the second constant value based on one or more of the parameters or characteristics of the HVAC unit 108. For example, the second constant value may be 21.6466. In some embodiments, respective values of A_{cal_one} and A_{cal_two} may be determined for each zone 112 of the building 100 utilizing the respective lowest discharge height 122 of the corresponding zone 112. In other words, if the respective value of the lowest discharge height 122 differs for different zones 112, the same value of the lowest discharge height 122 may not be utilized in the calculations shown in block 252. Alternatively, the respective values of A_{cal_one} and A_{cal_two} may be determined for each zone 112 of the building 100 utilizing the lowest discharge height 122 within the building 100 (e.g., lowest discharge height 122 amongst all zones 112).

The first scenario method 250 may then proceed to block 254, whereby the RDS analysis system 106 may compare the respective values of A_{cal_one} and A_{cal_two}, select the larger value of the respective values based on the comparison, and assign the larger value as A_cal (e.g., calculated area limit value, area limit reference value, determined area limit value), and the value of A_cal may be stored in the memory device 130. Thereafter, the first scenario method 250 may proceed to block 256. At block 256, the value of A_cal may be compared to one or more area values calculated by the RDS analysis system 106 for the one or more zones 112 to be serviced by the HVAC system 102. In particular, the RDS analysis system 106 may calculate a respective area value (e.g., A_entered, entered area value, calculated area value) for each zone 112 based on the respective width 118 and the respective length 120 of each zone 112 provided by the user (e.g., at block 210 or block 216 described above). In some embodiments, the RDS analysis system 106 may calculate the respective area value of each zone 112 based on data (e.g., measurement data, sensed measurements) received from one or more sensors.

In response to a determination that the respective area value (e.g., A_entered) of each zone 112 (e.g., at least one zone 112) is not greater than or equal to the value of A_cal, the first scenario method 250 may proceed to block 258, whereby the RDS analysis system 106 may execute the second scenario method 280 mentioned above and discussed further below. Such a determination may be indicative of a determination that all zones 112 to be serviced by the HVAC system 102 (e.g., HVAC unit 108) do not satisfy a minimum area requirement, which may be stipulated by one or more regulatory standards based on the characteristics of the HVAC unit 108. In response to a determination that the respective area value (e.g., A_entered) of each zone 112 is greater than or equal to the value of A_cal, the first scenario method 250 may proceed to block 260. At block 260, the RDS analysis system 106 may determine that the HVAC unit 108 to be utilized with the building 100 and service the zones 112 may be implemented with the building 100 without including the RDS 104 and/or the HVAC system 102 may be implemented with the building 100 without being configured to provide additional (e.g., continuous) ventilation, but may nevertheless comply with one or more regulatory standards. Accordingly, at block 260, the RDS analysis system 106 may output one or more indications (e.g., via the display 132) indicating that implementation of the RDS 104 is not required according to the one or more regulatory standards and that additional or continuous ventilation via the HVAC unit 108 and/or HVAC system 102 is not required according to the one or more regulatory standards. In some embodiments, the RDS analysis system 106 may output a control signal to a controller of the HVAC unit 108 to enable operation of the HVAC unit 108 without additional or continuous ventilation via the HVAC unit 108 at block 260.

FIG. 16 is a flow diagram of an embodiment of the second scenario method 280 mentioned above. The second scenario method 280 may begin with block 282, whereby the RDS analysis system 106 may perform one or more calculations to provide a value of an area (e.g., minimum total area value, minimum required area) associated with the building 100 and/or the zones 112 to be serviced by the HVAC system 102, as well as a value indicative of air circulation through the building 100 and/or the zones 112. For example, the air circulation value may be a minimum or lower limit continuous air circulation value that is mandated by one or more regulatory standards based on the characteristics of the HVAC system 102 (e.g., HVAC unit 108) and/or the building 100.

A value associated with the minimum total area of the one or more zones 112 (e.g., TA_min) may be calculated using the equation shown in block 282 based on the value of mc and a third constant value. The third constant value may be selected or determined based on a type of the refrigerant (e.g., R-454B), a characteristic of the HVAC unit 108, another suitable factor, or any combination thereof. In some embodiments, the RDS analysis system 106 may be configured to determine (e.g., using artificial intelligence) a value of the third constant value based on one or more of the parameters or characteristics of the HVAC unit 108. For example, the third constant value may be 14.9952.

Additionally, a value associated with the minimum continuous circulation of air throughout the zones 112 (e.g., Q_min, minimum continuous air flow circulation rate, minimum continuous air flow circulation value, lower limit air flow circulation rate) may be calculated using the equation shown in block 282 based on the value of mc and a fourth constant value. The fourth constant value may be selected or determined (e.g., predetermined) based on a type of the refrigerant (e.g., R-454B), a characteristic of the HVAC unit 108, another suitable factor, or a combination thereof. In some embodiments, the RDS analysis system 106 may be configured to determine (e.g., using artificial intelligence) a value of the fourth constant value based on one or more of the parameters or characteristics of the HVAC unit 108. For example, the fourth constant value may be 27.0883. In some embodiments, the minimum continuous circulation of air value may be indicative of a minimum flow rate of air that must be enabled or provided upon detection of escaped refrigerant (e.g., leaked refrigerant) from the HVAC system 102 and/or HVAC unit 108 by the RDS 104.

The second scenario method 280 may then proceed to block 284. At block 284, a total area (e.g., total actual area, A_zones, total area value) of the one or more zones 112 may be compared to the minimum total area value of the zones 112 (e.g., TA_min, minimum total area, minimum area value, lower threshold area value). As will be appreciated, the total area of the one or more zones 112 (e.g., A_zones) may be determined by the RDS analysis system 106 based on the respective width 118 and the respective length 120 of each zone 112 of the one or more zones 112 provided by the user (e.g., a summation of the respective areas of all zones 112). In response to a determination that the actual total area of the zones 112 (e.g., A_zones) is not greater than or equal to value of the minimum total area of the zones 112 (e.g., TA_min) calculated at block 282, the second scenario method 280 may proceed to block 286, whereby the RDS analysis system 106 may execute a third scenario method 300. The third scenario method 300 is described further below with reference to FIG. 17.

In response to a determination that the actual total area of the zones 112 (e.g., A_zones) is greater than or equal to value of the minimum total area of the zones 112 (e.g., TA_min) calculated at block 282, the second scenario method 280 may proceed to block 288. At block 288, the RDS analysis system 106 may output one or more indications (e.g., via the display 132) indicating that the RDS 104 should be implemented with the HVAC unit 108 (e.g., to comply with a regulatory standard). Additionally, the RDS analysis system 106 may output an indication of the respective values of the minimum total area of the zones 112 (e.g., TA_min) and/or the minimum continuous circulation of air throughout the zones 112 (e.g., Q_min), such as via the display 132. In some embodiments, the RDS analysis system 106 may also provide additional information and/or options associated with implementation of the RDS 104 with the HVAC unit 108 for reference by the user. Further, in some embodiments, the RDS analysis system 106, at block 288, may output a control signal to a controller of the HVAC unit 108 to program the controller to operate the HVAC unit 108 to provide circulation of air (e.g., at the minimum continuous air flow circulation rate) in response to detection of refrigerant via the RDS 104.

FIG. 17 is a flow diagram of an embodiment of the third scenario method 300 mentioned above. The third scenario method 300 may begin with block 302, whereby the RDS analysis system 106 may perform one or more calculations to provide a value of an upper limit or maximum refrigerant charge (e.g., m_max) that may be utilized in the HVAC unit 108 with the building 100 and/or the zones 112 based on a total area of the zones 112 (e.g., A_zones, TA). The maximum refrigerant charge (e.g., m_max) may be calculated using the equation shown in block 302 based on the total area (e.g., total actual area, TA) of the zones 112 and the third constant value (e.g., 14.9952). At block 302, the RDS analysis system 106 may also perform a calculation to determine the minimum continuous circulation of air throughout the zones 112 (e.g., minimum flow rate, Q_min) using the equation shown in block 302 based on a fifth constant value, the value of mc provided by the user, and the maximum refrigerant charge (e.g., m_max) calculated by the RDS analysis system 106. The fifth constant value may be selected or determined (e.g., predetermined) based on a type of the refrigerant (e.g., R-454B), a characteristic of the HVAC unit 108, another suitable factor, or a combination thereof. In some embodiments, the RDS analysis system 106 may be configured to determine (e.g., using artificial intelligence) a value of the fifth constant value based on one or more of the parameters or characteristics of the HVAC unit 108. For example, the fifth constant value may be 54.1165.

Further, the RDS analysis system 106 may perform a calculation to determine a minimum exhaust air flow rate (e.g., EA_min) using the equation shown in block 302 based on a sixth constant value, the value of m_c provided by the user, and the maximum refrigerant charge (e.g., m_max) calculated by the RDS analysis system 106. The sixth constant value may be selected or determined based on a type of the refrigerant (e.g., R-454B), a characteristic of the HVAC unit 108, another suitable factor, or a combination thereof. In some embodiments, the RDS analysis system 106 may be configured to determine (e.g., using artificial intelligence) a value of the sixth constant value based on one or more of the parameters or characteristics of the HVAC unit 108. For example, the sixth constant value may be 0.4346. As will be appreciated, the respective values for the minimum continuous circulation of air (e.g., minimum flow rate, Q_min) and the minimum exhaust air flow rate (e.g., EA_min) may be indicative of respective air flow rates that should be provided by the HVAC system 102 in response to detection of escaped refrigerant (e.g., leaked refrigerant) by the RDS 104.

The third scenario method 300 may then proceed to block 304. At block 304, the RDS analysis system 106 may output one or more indications (e.g., via the display 132) indicating that the RDS 104 should (e.g., must) be implemented with the HVAC unit 108 (e.g., to comply with a regulatory standard). Additionally, the RDS analysis system 106 may output an indication of the respective values of the minimum continuous circulation of air (e.g., minimum flow rate, Q_min) and the minimum exhaust air flow rate (e.g., EA_min), such as via the display 132. In some embodiments, the RDS analysis system 106 may also provide additional information and/or options associated with implementation of the RDS 104 with the HVAC unit 108 for reference by the user. In some embodiments, the RDS analysis system 106, at block 304, may output a control signal to a controller of the HVAC unit 108 to program the controller to operate the HVAC unit 108 to provide flow rates of air (e.g., circulation air at the minimum continuous air flow circulation rate, exhaust air at the minimum exhaust air flow rate) in response to detection of refrigerant via the RDS 104. In this way, improved operation of the controller of the HVAC unit 108 may be enabled. For example, the determinations and calculations performed and/or completed by the RDS analysis system 106 may not be demanded of the controller of the HVAC unit 108. Instead, the controller of the HVAC unit 108 may receive programming instructions, commands, and/or control signals from the RDS analysis system 106 to operate in a desired manner, and the controller of the HVAC unit 108 may thereby be configured to operate accordingly without undertaking extensive data processing and evaluation.

FIG. 18 is a flow diagram of an embodiment of another method 320 that may be performed by the RDS analysis system 106. For example, the method 320 may be executed by the RDS analysis system 106 in response to receipt of an input (e.g., user input) indicative of the HVAC unit 108 being configured as a residential split system (e.g., residential heating and cooling system 50). The method 320 may begin with block 322, whereby the RDS analysis system 106 prompts the user to input a value indicative of a number of indoor units (e.g., indoor units 56, indoor HVAC units) connected to an outdoor unit (e.g., outdoor unit 58, outdoor HVAC units). In response to a determination that the input is indicative of the number of indoor units connected to the outdoor unit being greater than one, the method 320 may proceed to block 324, and the RDS analysis system 106 may output a notification to contact an equipment manufacturer (e.g., of the HVAC unit 108). In some embodiments, the RDS analysis system 106 may not be configured to implement the present techniques with HVAC systems 102 having multiple indoor units connected to a single outdoor unit.

In response to a determination that the input received at block 322 is indicative of the number of indoor units being equal to one, the method 320 may proceed to block 326. At block 326, the RDS analysis system 106 may prompt the user to input a value indicative of the refrigerant charge (e.g., in pounds) of the HVAC unit 108. The RDS analysis system 106 may compare the refrigerant charge value input by the user to the lower threshold value (e.g., 4 pounds) and the predetermined value (e.g., 34 pounds) discussed above. In response to a determination that the refrigerant charge value input by the user is less than the lower threshold value (e.g., 4 pounds), the RDS analysis system 106 may output a notification indicating that implementation of the RDS 104 with the HVAC unit 108 is not required according to one or more regulatory standards, as indicated by block 328. In response to a determination that the refrigerant charge value input by the user is greater than the predetermined value (e.g., 34 pounds), the RDS analysis system 106 may output a notification to contact an equipment manufacturer (e.g., of the HVAC unit 108), as indicated by block 330. In some embodiments, the RDS analysis system 106 may not be configured to implement the present techniques with residential split systems having a refrigerant charge greater than the predetermined value. In response to a determination that the refrigerant charge value input by the user is greater than the lower threshold value (e.g., 4 pounds) and less than the predetermined value (e.g., 34 pounds), the RDS analysis system 106 may proceed with the method 200 described above, as indicated by block 332.

FIG. 19 is a flow diagram of an embodiment of another method 350 that may be performed by the RDS analysis system 106, such as in addition to the various methods described above. In some embodiments, the method 350 may be implemented by the RDS analysis system 106 for embodiments of the HVAC unit 108 that have the RDS 104 (e.g., RDS sensor) installed or pre-installed with the HVAC unit 108 (e.g., at a factory, at a manufacturing facility). The method 350 may begin with block 352, whereby the RDS analysis system 106 prompts the user to input a value indicative of the refrigerant charge of the HVAC unit 108. In response to a determination that the refrigerant charge value input by the user is greater than the predetermined value (e.g., 34 pounds), the method 350 may proceed to block 354. At block 354, the RDS analysis system 106 may output an indication to force activation of the RDS 104 within the HVAC unit 108. For example, the RDS analysis system 106 may output a signal (e.g., control signal) to the HVAC unit 108, to a controller of the HVAC unit 108 (e.g., control board 48, control panel 82) and/or to the RDS 104 to activate and/or enable operation of the RDS 104 (e.g., installed or pre-installed with the HVAC unit 108). In some embodiments, the RDS analysis system 106 may output one or more signals to a controller of the HVAC unit 108 to program the controller of the HVAC unit 108 to operate the RDS 104 and to operate the HVAC unit 108 based on data and/or feedback received from the RDS 104.

In response to a determination that the value of the refrigerant charge input by the user is less than the predetermined value (e.g., 34 pounds), the method 350 may proceed to block 356. At block 356, the RDS analysis system 106 may determine whether the RDS 104 should be (e.g., must be) implemented with the HVAC unit 108 to comply with one or more regulatory standards. For example, the determination at block 356 may be facilitated by execution of one or more of the methods described above (e.g., method 280, method 300). In response to a determination that the RDS 104 is required or mandated, the method 350 may proceed to block 358. At block 358, the RDS analysis system 106 may enable or cause activation of the RDS 104 installed with the HVAC unit 108. For example, if a user previously de-selected activation of the RDS 104 during set up of the HVAC unit 108, the RDS analysis system 106 may output a signal (e.g., control signal) to a controller (e.g., control panel 82) of the HVAC unit 108 and/or RDS 104 to cause activation of the RDS 104 at block 358. For example, the RDS analysis system 106 may output one or more signals to a controller of the HVAC unit 108 to program the controller of the HVAC unit 108 to operate the RDS 104 and to operate the HVAC unit 108 based on data and/or feedback received from the RDS 104. If a user previously selected activation of the RDS 104 during set up of the HVAC unit 108, the RDS analysis system 106 may continue with another method and/or may end the method 350 at block 358.

In response to a determination that the RDS 104 is not required or mandated (e.g., via method 250), the method 350 may proceed to block 360. If a user previously de-selected activation of the RDS 104 during set up of the HVAC unit 108, the RDS analysis system 106 may continue with another method and/or may end the method 350 at block 360. If the user previously selected activation of the RDS 104 during set up of the HVAC unit 108, the RDS analysis system 106 may disable activation of the RDS 104 installed with the HVAC unit 108 at block 360, in some embodiments. In other embodiments, the RDS analysis system 106 may permit prior use activation of the RDS 104 at block 360.

It should be appreciated that the embodiments described above may include various additional or alternative features. For example, in some embodiments, the RDS analysis system 106 may output an indication that the RDS 104 is required or mandated in response to input of a smallest duct discharge height of less than a particular and/or predetermined value (e.g., 2 feet). In some embodiments, the RDS analysis system 106 may be configured to output an indication that the RDS 104 is required or mandated for incorporation with the HVAC unit 108 based on certain characteristics of the HVAC unit 108 (e.g., a cooling only configuration of the HVAC unit 108 is selected by the user). As another alternative, the RDS analysis system 106 may be configured to force activation of the RDS 104 (e.g., pre-installed RDS 104, output a signal to a controller of the HVAC unit 108 to activate and/or enable operation of the RDS 104) as a default, unless one or more of the methods described above are executed to determine that activation of the RDS 104 is not required according to one or more regulatory standards.

FIGS. 20-24 are illustrations of additional embodiments of the graphical user interface (GUI) 150 that may be displayed via the display 132 (e.g., touchscreen) of the computing device 126 to enable and/or perform functionalities of embodiments of the RDS analysis system 106 described herein. In some embodiments, the RDS analysis system 106 may be configured to prompt a user for additional input regarding the HVAC unit 108 and/or the HVAC system 102. Based on the additional input, the RDS analysis system 106 may determine whether the RDS 104 is prescribed for the HVAC unit 108. In some embodiments, a manufacturer of the HVAC unit 108 may pre-select or designate certain embodiments or types (e.g., models, configurations, minimum tonnage, electric heating component or feature, product lines, etc.) of the HVAC unit 108 for which the RDS 104 is to be incorporated and utilized. For example, the manufacturer of the HVAC unit 108 may mandate that the RDS 104 is required to be incorporated in certain embodiments of the HVAC unit 108 having a particular feature, configuration, and/or other characteristic. The manufacturer may mandate that the RDS 104 be incorporated and utilized with embodiments of the HVAC unit 108 that have the particular feature, configuration, and/or other characteristic independent of whether the incorporation of the RDS 104 with the HVAC unit 108 is demanded by one or more regulatory standards or guidelines and/or prescribed by another determination of the RDS analysis system 106 (e.g., by one or more of the calculations and/or methods described above).

Accordingly, the RDS analysis system 106 may be configured to prompt a user to input additional information regarding the manufacturer of the HVAC unit 108, identification of a type of the HVAC unit 108 (e.g., serial number, model name, product line name, etc.), features and/or a configuration of the HVAC unit 108, another characteristic of the HVAC unit 108, or any combination thereof. Based on the additional information, the RDS analysis system 106 may determine whether the HVAC unit 108 should incorporate the RDS 104 to satisfy a requirement or mandate of the manufacturer of the HVAC unit 108 (e.g., independent of other calculations and/or determinations made by the RDS analysis system 106). It should be appreciated that the functionalities and operations of the RDS analysis system 106 described below may be incorporated with (e.g., in addition to) any of the functionalities and operations of the RDS analysis system 106 described above and herein. For example, the methods and techniques described below may be performed prior to execution or performance of the method 200 described above.

FIG. 20 illustrates a first initial screen 400 of the GUI 150 that may be displayed via the display 132. For example, the processing circuitry 128 may cause the GUI 150 to display the first initial screen 400 upon selection of the RDS calculator icon 160 presented on the second screen 158 of the GUI 150. In some embodiments, the processing circuitry 128 may cause the GUI 150 to display the first initial screen 400 instead of the third screen 162 discussed above. The first initial screen 400 may prompt a user to input various information and/or data, such as a name (e.g., “job name”) of the particular implementation of the HVAC unit 108, a name of the HVAC unit 108, a type of the building 100, or a combination thereof. In some embodiments, the GUI 150 may display a menu (e.g., pulldown menu) to select a type of the building 100, such as a data center, a lab, a hospital, manufactured housing, a multifamily residence, a church, an office building, a school, a retail building, a warehouse, a residential building, a recreational building, or any other suitable type of structure that may be serviced by the HVAC system 102 (e.g., HVAC unit 108).

The first initial screen 400 may also prompt a user to indicate whether the HVAC unit 108 is manufactured by a particular manufacturer (e.g., “Company A”). The first initial screen 400 may also provide or display an indication regarding whether user input indicating that the HVAC unit 108 is or is not manufactured by the particular manufacturer (e.g., “Company A”) is mandatory, such as via an asterisk 402 or other marking (e.g., highlight, text, symbol, etc.) displayed next to the question prompting the user input regarding the manufacturing entity of the HVAC unit 108. In response to a user input indicating that the HVAC unit 108 is not manufactured by the particular manufacturer, the processing circuitry 128 may cause the GUI 150 to display another screen, such as the fourth screen 164 (e.g., via the display 132), and the RDS analysis system 106 may proceed as similarly described above (e.g., via performance of the method 200).

In response to a user input indicating that the HVAC unit 108 is manufactured by the particular manufacturer, the processing circuitry 128 may cause the GUI 150 to display a second initial screen 404, as illustrated in FIG. 21. As shown in the illustrated embodiment, the second initial screen 404 displays an indication that the user identified (e.g., via user input at the first initial screen 400) the HVAC unit 108 as manufactured by the particular manufacturer (e.g., “Company A”). The second initial screen 404 may also include a field to enable the user to provide additional identification information related to the HVAC unit 108 (e.g., indicative of an identity of the HVAC unit 108). For example, the second initial screen 404 may provide a plurality of category selections 406 from which the user may select to specify a category or type of information that the user may input via the GUI 150 to further identify the HVAC unit 108. In the illustrated embodiment, the user may select “Serial number” or “Product line” via the second initial screen 404. The second initial screen 404 may also indicate that a user input indicating a selection of a category or type of information is mandatory, such as via an asterisk 408 or other marking displayed next to the prompt related to user selection of one of the plurality of category selections 406.

Upon user selection (e.g., via user input) of one of the plurality of category selections 406, the processing circuitry 128 may cause the GUI 150 to display a third initial screen 410, as illustrated in FIG. 22. As shown in the illustrated embodiment, the third initial screen 410 displays an indication that the user selected one of the plurality of category selections 406 (e.g., “Serial number”) via the second initial screen 404. Based upon the user selection, the third initial screen 410 may display an input field 412 to prompt the user to input information corresponding to the category selection 406 selected by the user via the second initial screen 404. For example, upon selection of the “Serial number” category selection via the second initial screen 404, the input field 412 may be identified with a “Serial number” heading to indicate that the user should input the serial number of the HVAC unit 108 in the input field 412. Upon selection of the “Product line” category selection via the second initial screen 404, the input field 412 may be identified with a “Product line” heading to indicate that the user should input information regarding the product line of the HVAC unit 108. In such embodiments, the GUI 150 may display a menu (e.g., pulldown menu) via the input field 412 to enable the user to select a name of a product line or model of the HVAC unit 108 from a predetermined list of product lines and/or product models. The third initial screen 410 may also indicate that a user input (e.g., via the input field 412) providing identification information of the HVAC unit 108 corresponding to the category selection 406 selected by the user is mandatory, such as via an asterisk 414 displayed next to the heading identifying the category selection 406 selected by the user on the second initial screen 404.

Subsequent to entry of the identification information of the HVAC unit 108 via the input field 412, the processing circuitry 128 may cause the GUI 150 to display a fourth initial screen 416, as illustrated in FIG. 23. In some embodiments, the fourth initial screen 416 may display the category selection 406 selected by the user on the second initial screen 404 with the identification information entered via the input field 412 on the third initial screen 410. The fourth initial screen 416 may also prompt the user to input additional information regarding the embodiment of the HVAC unit 108 to be implemented in the HVAC system 102, such as a configuration, characteristic, feature, equipment, and/or other aspect of the HVAC unit 108. Additionally or alternatively, the fourth initial screen 416 may prompt the user to input additional information regarding a particular implementation or installation of the HVAC unit 108, such as a characteristic, feature, configuration, or aspect of the HVAC system 102, the building 100 serviced by the HVAC unit 108 (e.g., whether the HVAC unit 108 will service a single zone in the building 100), and so forth. In some embodiments, the fourth initial screen 416 may include multiple input fields 418 prompting various types of information (e.g., a refrigerant charge of a largest circuit of the HVAC unit 108), and one or more of the multiple input fields 418 may include an indication (e.g., an asterisk 420) indicating that input of the information requested by the input field 418 is mandatory.

As described in further detail below, the RDS analysis system 106 may perform an initial determination of whether the RDS 104 is prescribed for the HVAC unit 108 based on the additional information input by the user via the first initial screen 400, the second initial screen 404, the third initial screen 410, and/or the fourth initial screen 416. The determination may be based on one or more designations, specifications, requirements, and/or requisites imposed by the particular manufacture of the HVAC unit 108. Based on a determination that the RDS 104 is prescribed for the HVAC unit 108, the processing circuitry 128 may cause the GUI 150 to display a fifth initial screen 422, as shown in FIG. 24. The fifth initial screen 422 includes a first notification 424 that the RDS 104 is required based on the additional input provided by the user described above. In some embodiments, the fifth initial screen 422 may display a second notification 426 indicating that the RDS analysis system 106 may subsequently make one or more additional determinations pertaining to other requirements or stipulations that may be prescribed (e.g., based on regulatory standards, based on one or more calculations described herein) based on further calculations and/or assessments performed by the RDS analysis system 106. For example, the second notification 426 may indicate that additional ventilation of the space serviced by the HVAC unit 108 may be prescribed based on subsequent determinations. Accordingly, the user may be prompted, via the fifth initial screen 422, to continue with execution of one or more of the methods described herein (e.g., method 200) to enable such determinations via the RDS analysis system 106.

FIG. 25 is a flow diagram of an embodiment of a method 450 that may be implemented (e.g., executed, performed) by the RDS analysis system 106 to determine whether the RDS 104 should (e.g., must) be incorporated with the HVAC system 102 (e.g., HVAC unit 108), based on characteristics of the HVAC unit 108 and the building 100, in accordance with one or more designations or mandates imposed by a particular manufacturer of the HVAC unit 108. As similarly discussed above, the method 450 may be performed based on input provided by a user, such as via the computer device 126 (e.g., user interface 134, display 132). For example, the method 450 may be executed via the processing circuitry 128 causing the GUI 150 to display the first initial screen 400, the second initial screen 404, the third initial screen 410, and/or the fourth initial screen 416 to prompt the user to input the information relevant to make the determination in accordance with the designations imposed by the particular manufacturer of the HVAC unit 108.

At block 452, a user may provide an indication (e.g., via the first initial screen 400) indicating whether the HVAC unit 108 is manufactured by a particular (e.g., predetermined) manufacturer, such as Company A. In response to a user input that the HVAC unit 108 is not manufactured by the particular manufacturer, the method 450 may proceed to block 454, whereby the method 450 may end and the RDS analysis system 106 may proceed with performance of one or more additional methods described herein, such as method 200, to perform additional analysis and determine whether the HVAC unit 108 should include the RDS 104 (e.g., to satisfy one or more regulatory standards). Based on a determination at block 452 that the user input indicates that the HVAC unit 108 was manufactured by the particular manufacturer, the method 450 may proceed to block 456.

At block 456, the user may be prompted (e.g., via the second initial screen 404 and/or the third initial screen 410) to input identification information associated with the HVAC unit 108. For example, the RDS analysis system 106 (e.g., via the GUI 150) may prompt the user to input a serial number of the HVAC unit 108, to select a product line of the HVAC unit 108, to select a model name or other identifier of the HVAC unit 108, and/or to provide any other suitable input (e.g., identification information) to identify a type, classification, configuration, category, or other group encompassing the embodiment of the HVAC unit 108. In some embodiments, the user may be presented with a list of options for selection to identify the type, classification, configuration, category, or other group encompassing the embodiment of the HVAC unit 108.

After block 456, the method 450 may proceed to block 458. At block 458, the HVAC unit 108 may be identified as a commercial unit or a residential unit. For example, the RDS analysis system 106 (e.g., the processing circuitry 128) may identify the HVAC unit 108 as a commercial unit or a residential unit based on the user input provided at block 456. In response to a determination that the HVAC unit 108 is a residential unit at block 458, the method 450 may proceed to block 454, whereby the method 450 may end and the RDS analysis system 106 may proceed with performance of one or more additional methods described herein (e.g., method 320) to perform additional analysis and determine whether the HVAC unit 108 should (e.g., must) include the RDS 104 (e.g., to satisfy one or more regulatory standards). In response to a determination that the HVAC unit 108 is a commercial unit, the method 450 may proceed to block 460.

At block 460, a determination is made regarding whether the HVAC unit 108 is one of a plurality of preselected or pre-identified types, categories, groups, or other classifications of HVAC units (e.g., commercial HVAC units). For example, the preselected type, category, and/or classification of HVAC unit may be a particular product line of commercial HVAC unit, a particular model of commercial HVAC unit, a particular configuration of commercial HVAC unit, or any other particular type or category of commercial HVAC unit. The RDS analysis system 106 (e.g., processing circuitry 128) may identify the HVAC unit 108 as one of the plurality of preselected or pre-identified types, categories, groups, and/or other classifications of HVAC units based on the user input provided at block 456. The preselected types, categories, and/or classifications of HVAC unit may be identified and designated by the manufacturer of the HVAC unit 108. In response to a determination that the HVAC unit 108 is one of the plurality of preselected or pre-identified types, categories, groups, and/or other classifications of HVAC units, the method 450 may proceed to block 462. At block 462, a notification may be output (e.g., via the GUI 150, via the display 132, via the fifth initial screen 422) to indicate that the RDS 104 is prescribed for the HVAC unit 108 (e.g., based on a designation or requirement of the manufacturer of the HVAC unit 108). In some embodiments, the RDS analysis system 106 may output a signal to a controller of the HVAC unit 108 and/or the RDS 104 to activate and/or enable operation of the RDS 104 based on the determination that the RDS 104 is prescribed for the HVAC unit 108.

In response to a determination that the HVAC unit 108 is not one of the plurality of preselected or pre-identified types, categories, groups, and/or other classifications of HVAC units, the method 450 may proceed to block 464. At block 464, a determination is made regarding whether the HVAC unit 108 includes one or more of a plurality of preselected or pre-identified features, configurations, and/or other aspects, which may be designated by the manufacturer of the HVAC unit 108. The preselected or pre-identified features, configurations, and/or aspects may be designated by the manufacturer based on a designation by the manufacturer of the HVAC unit 108 that the RDS 104 is to be incorporated with the HVAC unit 108 having one or more of the preselected features, configurations, and/or aspects. The preselected features, configurations, and/or aspects may be any suitable characteristic of the HVAC unit 108 designated by the manufacturer, such as an electric heat system or component incorporated with the HVAC unit 108, an option or configurability to incorporate an electric heat system or component with the HVAC unit 108 subsequent to manufacture of the HVAC unit 108 (e.g., subsequent to installation of the HVAC unit 108, in the field), a configuration of the HVAC unit 108 to provide cooling and to not provide heating (e.g., cooling only), a configuration of the HVAC unit 108 as a heat pump, a refrigerant charge, capacity, and/or tonnage of the HVAC unit 108 that is equal to or greater than a corresponding threshold value, another suitable characteristic, or any combination thereof.

In response to a determination at block 464 that the HVAC unit 108 does not include (e.g., is characterized by) one or more of the preselected features, configurations, and/or aspects, the method 450 may proceed to block 454, whereby the method 450 may end and the RDS analysis system 106 may proceed with performance of one or more additional methods described herein to perform additional analysis and determine whether the HVAC unit 108 should include the RDS 104 (e.g., to satisfy one or more regulatory standards). In response to a determination at block 464 that the HVAC unit 108 does include (e.g., is characterized by) one or more of the preselected features, configurations, and/or aspects, the method 450 may proceed to block 462. As discussed above, a notification may be output to indicate that the RDS 104 is prescribed for the HVAC unit 108 (e.g., based on a designation or requirement of the manufacturer of the HVAC unit 108) at block 462. In some embodiments, the RDS analysis system 106 may output a signal to a controller of the HVAC unit 108 and/or the RDS 104 to activate and/or enable operation of the RDS 104 based on the determination that the RDS 104 is prescribed for the HVAC unit 108.

Subsequent to block 462, the method 450 may proceed to block 466. At block 466, a further notification may be output (e.g., via the GUI 150, via the display 132, via the fifth initial screen 422) to indicate that the RDS analysis system 106 may subsequently make one or more additional determinations pertaining to other requirements or stipulations that may be prescribed (e.g., based on regulatory standards, based on one or more calculations described herein) based on further calculations and/or assessments performed by the RDS analysis system 106. In other words, the additional notification at block 466 may indicate that operation of the RDS analysis system 106 should proceed via performance of one or more of the methods, calculations, and/or determinations described herein. For example, the additional notification may provide an indication that additional ventilation may be prescribed for the HVAC unit 108 and/or the building 100 having the HVAC unit 108 based on further analysis performed by the RDS analysis tool 106, in accordance with the techniques described herein. To this end, the method 450 may proceed from block 466 to block 454, whereby the method 450 may end and the RDS analysis system 106 may proceed with performance of one or more additional methods described herein to perform additional analysis and determine whether the HVAC unit 108 should include the RDS 104 (e.g., to satisfy one or more regulatory standards). Based on a determination via the method 450 that the RDS 104 is prescribed (e.g., required) for the HVAC unit 108 (e.g., based on a designation or requirement of the manufacturer of the HVAC unit 108), subsequent analysis and/or determinations performed by the RDS analysis system 106 may not alter the determination that the RDS 104 is prescribed for the HVAC unit 108.

While only certain features and embodiments have been illustrated and described, many modifications and changes may occur to those skilled in the art, such as variations in sizes, dimensions, structures, shapes and proportions of the various elements, values of parameters, such as temperatures and pressures, mounting arrangements, use of materials, colors, orientations, and so forth, without materially departing from the novel teachings and advantages of the subject matter recited in the claims. The order or sequence of any process or method steps may be varied or re-sequenced according to alternative embodiments. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the disclosure.

Furthermore, in an effort to provide a concise description of the exemplary embodiments, all features of an actual implementation may not have been described, such as those unrelated to the presently contemplated best mode, or those unrelated to enablement. It should be appreciated that in the development of any such actual implementation, as in any engineering or design project, numerous implementation specific decisions may be made. Such a development effort might be complex and time consuming, but would nevertheless be a routine undertaking of design, fabrication, and manufacture for those of ordinary skill having the benefit of this disclosure, without undue experimentation.

The techniques presented and claimed herein are referenced and applied to material objects and concrete examples of a practical nature that demonstrably improve the present technical field and, as such, are not abstract, intangible or purely theoretical. Further, if any claims appended to the end of this specification contain one or more elements designated as “means for [perform]ing [a function] . . . ” or “step for [perform]ing [a function] . . . ”, it is intended that such elements are to be interpreted under 35 U.S.C. 112(f). However, for any claims containing elements designated in any other manner, it is intended that such elements are not to be interpreted under 35 U.S.C. 112(f).

Claims

1. A refrigerant detection system (RDS) implementation tool for a heating, ventilation, and air conditioning (HVAC) unit, comprising: processing circuity; anda tangible, non-transitory, computer-readable medium comprising instructions stored thereon, wherein the instructions, when executed by the processing circuitry, are configured to cause the processing circuitry to: receive first data indicative of an amount of a refrigerant to be implemented in a refrigerant circuit of the HVAC unit;compare the first data to a predetermined value corresponding to the amount of the refrigerant;receive second data indicative of dimensions associated with a space to be conditioned by the HVAC unit, wherein the second data comprises a vertical distance extending from a floor of the space to a duct outlet configured to direct air flow from the HVAC unit into the space;determine whether implementation of a refrigerant detection system with the HVAC unit is mandated based on the first data and the second data; andoutput, via a display, a notification indicating whether implementation of the refrigerant detection system is mandated.

2. The RDS implementation tool of claim 1, wherein the instructions, when executed by the processing circuitry, are configured to cause the processing circuitry to: in response to a determination that the amount of the refrigerant is less than the predetermined value: determine a first area limit value corresponding to the space based on the amount of the refrigerant, the vertical distance, and a first constant value;determine a second area limit value corresponding to the space based on the amount of the refrigerant, the vertical distance, and a second constant value, different from the first constant value;compare the first area limit value to the second area limit value;in response to a determination that the first area limit value is greater than the second area limit value, assign the first area limit value as a calculated area limit value; andin response to a determination that the second area limit value is greater than the first area limit value, assign the second area limit value as the calculated area limit value.

3. The RDS implementation tool of claim 2, wherein the second data comprises a length dimension of the space and a width dimension of the space, and wherein the instructions, when executed by the processing circuitry, are configured to cause the processing circuitry to: determine an entered area value of the space based on the length dimension and the width dimension;compare the entered area value to the calculated area limit value.

4. The RDS implementation tool of claim 3, wherein the instructions, when executed by the processing circuitry, are configured to cause the processing circuitry to: in response to a determination that the entered area value is equal to or greater than the calculated area limit value, output the notification indicating that that implementation of the refrigerant detection system with the HVAC unit is not mandated.

5. The RDS implementation tool of claim 3, wherein the instructions, when executed by the processing circuitry, are configured to cause the processing circuitry to: in response to a determination that the entered area value is less than the calculated area limit value: determine a minimum total area value corresponding to the space based on the amount of the refrigerant and a third constant value, different from the first constant value and the second constant value;determine a total area value of the space;compare the minimum total area value to the total area value of the space; andin response to a determination that the total area value of the space is greater than or equal to the minimum total area value, output the notification indicating that implementation of the refrigerant detection system with the HVAC unit is mandated.

6. The RDS implementation tool of claim 5, wherein the instructions, when executed by the processing circuitry, are configured to cause the processing circuitry to: in response to the determination that the entered area value is less than the calculated area limit value: determine a minimum continuous air flow circulation value corresponding to the space based on the amount of the refrigerant and a fourth constant value, different from the first constant value, the second constant value, and the third constant value; andoutput, via the display, an additional notification corresponding to the minimum continuous air flow circulation value.

7. The RDS implementation tool of claim 6, wherein the first constant value, the second constant value, the third constant value, the fourth constant value, or a combination thereof is based on a type of the refrigerant, a characteristic of the HVAC unit, or both.

8. The RDS implementation tool of claim 2, wherein the instructions, when executed by the processing circuitry, are configured to cause the processing circuitry to: in response to a determination that the amount of the refrigerant is equal to or greater than the predetermined value, output the notification indicating that implementation of the refrigerant detection system with the HVAC unit is mandated.

9. The RDS implementation tool of claim 1, wherein the duct outlet is one of a plurality of duct outlets configured to direct air flow from the HVAC unit into the space, and the vertical distance is a lowest value of respective dimensions extending from the floor to the plurality of duct outlets.

10. The RDS implementation tool of claim 1, wherein the instructions, when executed by the processing circuitry, are configured to cause the processing circuitry to: receive third data indicative of a serial number of the HVAC unit, a product line of the HVAC unit, or both; andin response to a determination that the third data is indicative of the HVAC unit being one of a plurality of predetermined types of HVAC unit, output the notification indicating that implementation of the refrigerant detection system with the HVAC unit is mandated.

11. The RDS implementation tool of claim 10, wherein the plurality of predetermined types of HVAC unit comprises a product line of HVAC unit, a minimum tonnage of HVAC unit, a particular heating feature of the HVAC unit, a configuration of HVAC unit, or a combination thereof.

12. The RDS implementation tool of claim 1, wherein the instructions, when executed by the processing circuitry, are configured to cause the processing circuitry to: in response to a determination that implementation of the refrigerant detection system with the HVAC unit is mandated, output a control signal to implement programming in a controller of the HVAC unit to enable the HVAC unit to operate with the refrigerant detection system.

13. A refrigerant detection system (RDS) implementation system for a heating, ventilation, and air conditioning (HVAC) unit, comprising: a tangible, non-transitory, computer-readable medium comprising instructions stored thereon, wherein the instructions, when executed by processing circuitry, are configured to cause the processing circuitry to: prompt a user to input first data indicative of an identity an HVAC unit;prompt the user to input second data indicative of an amount of a refrigerant to be implemented in a refrigerant circuit of the HVAC unit;prompt the user to input third data indicative of a dimension associated with a space to be conditioned by the HVAC unit;determine whether a refrigerant detection system is to be implemented with the HVAC unit based on the first data, the second data, and the third data; andoutput, via a display, a notification indicative of whether the refrigerant detection system is to be implemented with the HVAC unit.

14. The RDS implementation system of claim 13, wherein the instructions, when executed by the processing circuitry, are configured to cause the processing circuitry to prompt the user to input a serial number of the HVAC unit, product line information of the HVAC unit, a first selection indicative of a particular manufacturer of the HVAC unit, or a combination thereof as the first data.

15. The RDS implementation system of claim 13, wherein the instructions, when executed by the processing circuitry, are configured to cause the processing circuitry to input, as the third data, a smallest value of a plurality of dimensions associated with the space, wherein each dimension of the plurality of dimensions is a respective vertical distance from a floor of the space to a respective duct outlet of a plurality of duct outlets configured to discharge air from the HVAC unit into the space.

16. The RDS implementation system of claim 13, wherein the instructions, when executed by the processing circuitry, are configured to cause the processing circuitry to: compare the amount of the refrigerant to a predetermined value; andin response to a determination that the amount of the refrigerant is greater than predetermined value, output a signal to implement programming in a controller of the HVAC unit to enable the HVAC unit to operate with the refrigerant detection system.

17. The RDS implementation system of claim 16, wherein the instructions, when executed by the processing circuitry, are configured to cause the processing circuitry to: in response to a determination that the amount of the refrigerant is less than the predetermined value: determine a calculated area limit value of the space based on the amount of the refrigerant;determine an entered area value of the space based on the dimension associated with the space;compare the entered area value to the calculated area limit value; andin response to a determination that the entered area value is equal to or greater than the calculated area limit value, output the notification indicating that that the refrigerant detection system is to be implemented with the HVAC unit.

18. The RDS implementation system of claim 17, wherein the instructions, when executed by the processing circuitry, are configured to cause the processing circuitry to: in response to a determination that the entered area value is less than the calculated area limit value: determine a minimum total area value corresponding to the space based on the amount of the refrigerant;determine a minimum continuous air flow circulation value corresponding to the space based on the amount of the refrigerant; anddetermine a total area value of the space based on the entered area value.

19. The RDS implementation system of claim 18, wherein the instructions, when executed by the processing circuitry, are configured to cause the processing circuitry to: in response to a determination that the total area value of the space is greater than or equal to the minimum total area value: output, via the display, the notification indicating that the refrigerant detection system is to be implemented with the HVAC unit; andoutput, via the display, an additional notification corresponding to the minimum continuous air flow circulation value.

20. A refrigerant detection system (RDS) implementation system for a heating, ventilation, and air conditioning (HVAC) unit, comprising: processing circuity; anda tangible, non-transitory, computer-readable medium comprising instructions stored thereon, wherein the instructions, when executed by the processing circuitry, are configured to cause the processing circuitry to: receive first data indicative of a configuration of the HVAC unit, wherein the first data comprises a serial number of the HVAC unit, an operating mode of the HVAC unit, a product line of the HVAC unit, or a combination thereof;receive second data indicative of an amount of a refrigerant to be implemented in a refrigerant circuit of the HVAC unit;receive third data indicative of a dimension associated with a space to be conditioned by the HVAC unit, wherein the dimension is a smallest value of a plurality of dimensions associated with the space, and each dimension of the plurality of dimensions is a respective vertical distance from a floor of the space to a respective duct outlet of a plurality of duct outlets configured to discharge air from the HVAC unit into the space;based on the first data, the second data, and the third data, determine whether implementation of a refrigerant detection system with the HVAC unit is mandated by a regulatory standard;output, via a display, a notification indicative of whether implementation of the refrigerant detection system is mandated by the regulatory standard; andin response to a determination that implementation of the refrigerant detection system is mandated by the regulatory standard, output a signal to a controller of the HVAC unit to configure the controller for operation with the refrigerant detection system.