HVAC SYSTEM WITH CENTRALIZED CONTROL CONNECTED TO A FRESH AIR VENTILATION SYSTEM

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the priority benefit of U.S. 63/651,929 (filed May 24, 2024), which is incorporated herein by reference in its entirety.

BACKGROUND

HVAC systems can include a variety of different components that, in order to control the operations of the system, communicate with one another (e.g., via electronic signals), such as thermostats, zone panels, dampers, ventilation controls, sensors, etc. Some systems include components for pulling in fresh air (e.g., outside air) into the system or property, but it can be undesirable to bring in fresh air all of the time or when an air handling unit (AHU) is not running, since the fresh air can be too hot, humid, or cold, leading to excessive electricity costs, discomfort, and indoor air quality issues.

Some systems (e.g., installations of systems) include controls and accessories to reduce the likelihood of fresh air being pulled in when the AHU is not running, but often the HVAC components and controls (e.g., such as in a Variable Refrigerant Volume (VRV) system or a Variable Refrigerant Flow (VRF) system) are equipped to communicate only through proprietary communication means (e.g., encrypted communications). This can make it challenging for HVAC components (e.g., from third parties) that do not communicate via the proprietary communications means to operate in coordination with those systems.

DETAILED DESCRIPTION OF DRAWINGS

The present systems and methods for an HVAC system with centralized control connected to a fresh air ventilation system are described in detail below with reference to these figures.

FIG. 1 depicts an example system or environment based on an example of this disclosure.

FIG. 2 depicts an example of a PCB for a controller based on an example of this disclosure.

FIG. 3 depicts an example of a control that includes a current sensor based on an example of this disclosure.

FIG. 4 depicts an example of a control that includes a pressure sensor based on an example of this disclosure.

DETAILED DESCRIPTION

Some acronyms might be used in this description, including (but are not limited to) the below. Unless otherwise described to the contrary, these terms can include meanings as understood in the field of heating, ventilation, and air conditioning (inclusive of cooling, humidity control, and air quality).

• • AHU Air Handling Unit
  • CFM Cubic Feet Per Min
  • DAT Discharge Air Temperature Sensor
  • ECM Electronically Commutated Motor
  • FAPV-L Fresh Air Power Ventilator Lite
  • FCMC Fresh Command Multi-Family
  • HVAC Heating Ventilation Air Conditioning
  • MF Multi-Family
  • OEM Original Equipment Manufacturer
  • VRF Variable Refrigerant Flow
  • VRV Variable Refrigerant Volume
  • FAV Fresh Air Ventilation
  • IAQ Indoor Air Quality

The present disclosure is related to a controller for an HVAC system that can receive signals and/or measurements associated with the HVAC system and that can control one or more operations of fresh-air-ventilation (FAV) equipment (e.g., a fresh air fan and/or a fresh air damper). For example, the controller can receive one or more signals from a first sensor indicating whether an air handling unit (AHU) fan is on and one or more signals from a second sensor indicating a quality of the fresh air (e.g., temperature and/or humidity), and based on the signals, the controller can control an operation of the FAV equipment.

In some examples, the controller can control the operations of the FAV equipment without relying on proprietary communication means. That is, the subject matter of the present disclosure can be integrated into an HVAC system (e.g., VRV or VRF system) that includes proprietary communication and can, via one or more non-proprietary communication mechanisms, control when fresh air is introduced into the system (e.g., without communicating/interfacing via the proprietary communication).

In conventional solutions HVAC systems can include some components that communicate with proprietary communication (e.g., VRV and VRF types), such that operations of these systems can often be controlled with only accessories and parts that use the proprietary communication. This limits the availability of equipment and accessories that can work with the system and drives up cost and availability. This can be true in many different types of systems, and especially in multi-family units.

In general “proprietary communication protocol” can include a protocol that might be controlled by a manufacturer (e.g., the manufacturer of a component or system of components) or other entity, and often, the technical details of how to “talk” via the protocol are not widely published or otherwise made available. The technical details that can remain proprietary (or otherwise unknown to third parties thereby making communication more challenging) can include various attributes, features, or characteristics, such as data format and structure; addressing scheme(s); framing and synchronization; and/or encryption. Any one or more of these details can be kept private and not disclosed to third parties.

The present solution includes HVAC system components and accessories that do not use proprietary communication means and that can be used in a variety of different HVAC systems to control operations, including systems (e.g., VRV and VRF) that use proprietary communication means. For example, some HVAC system operations can be configured to bringing fresh air into the system at the appropriate times (e.g., when the AHU is running and/or when the outside air is not too hot, humid, or cold). Bringing outside/fresh air into the system at appropriate or optimized times can reduce the likelihood of excessive electricity costs, discomfort, and indoor air quality issues.

In examples, the system of the present disclosure includes components (e.g., a controller) that can, without relying on proprietary communication protocols or means, provide fresh air when the HVAC system is operating (e.g., when the AHU fan is on) and/or when the outside air includes properties that are conducive to desired states or operating conditions of the system. In some instances, this capability (e.g., to bring in fresh air) can be listed under a building code, such that this solution provides a solution for the engineer/builder/contractor to (without relying on components that only use proprietary communication) meet the ventilation code requirements, even when the system includes proprietary communication equipment (e.g., VRV/VRF equipment).

In at least some examples, the controller of the present solution includes components that detect when the HVAC air handling unit (AHU) is operating (e.g., fan running). In some examples, the present solution includes a component that can determine, via a low voltage signal, when the HVAC AHU is operating. For example, in some instances, the present solution can include an electricity current sensor and/or pressure sensor. In some examples, this can be referred to as an AHU-state sensor, which can be one part of the ventilation controller.

In addition, the system (e.g., the controller) can intelligently determine whether properties or conditions of the outside air are suitable for delivering to the system. For example, the system can include a temperature sensor, a humidity sensor, and/or other sensors to assess properties of the outside air and determine whether the properties/conditions are satisfactory. In some examples, this can include a fresh-air-conditions sensor (e.g., the fresh-air-conditions sensor can be a component of the ventilation controller). The fresh-air-conditions sensor can, in some cases, be positioned in a mixed plenum. In some instances, it can be positioned on the exterior of the building.

In examples, the system of the present disclosure, including the ventilation controller, uses the combination of the AHU-state sensor and the fresh-air-conditions sensor to determine whether to bring in fresh air for delivery to the property.

Referring to FIG. 1, an example system 100 is illustrated. In examples, the system 100 includes some plenum 102 (e.g., mixed plenum) in which fresh air 104 (e.g., unconditioned air from outside or exterior to the building envelope) can be introduced to the system (e.g., via the duct 105) and then distributed to the home 106. For example, the system 100 can include an air-handling-unit (AHU) 108, which can include an AHU fan with an impeller that rotates via a motor (e.g., ECM) to propel air (e.g., conditioned air) into the conditioned-air space 106. In some cases, the fresh air 104 is drawn into the AHU 108 and distributed to the space 106. For example, if the HVAC AHU 108 is in a utility closet, the fresh air 104 can be delivered into the utility closet (sometimes called a mixed plenum and via the duct 105), after which the AHU 108 can deliver the fresh air to the home 106 (conditioned-air space).

In some examples, the AHU 108 can be a component in a VRV or VRF system, such that the AHU is configured to operate and communicate via proprietary communications. For example, the system 100 can include a controller 107 (e.g., a first controller) that exchanges communications with the AHU 108 via a proprietary communication protocol. In some instances, the controller 107 can include a thermostat or other type of control system.

In some examples of the present disclosure, the system can include a fan powered product 110 (e.g., FAPV) to actively bring fresh air 104 from outside into the plenum 102. In addition, or alternatively, the system 100 can include a duct 105 from the plenum 102 to the outside that is controlled via a damper 112 (e.g., FAD).

In examples, the system 100 includes a controller 114 (e.g., second controller or ventilation controller) that can control operations related to ventilation, such as by bringing fresh air into the system 100. For example, the controller 114 can, based on the state of the AHU 108 and/or the conditions of the outside air 104, control operations associated with the FAPV 110 and/or FAD 112.

FIG. 2 includes an example of a printed circuit board (PCB) 200 of a controller 114, based on an example of this disclosure. In at least some examples, the controller 114 can include (or otherwise be in communication with) a temperature sensor, a humidity sensor, and/or other sensors (e.g., sensor 116). For example, one or more of these sensors can be mounted to the PCB 200 (e.g., could be mounted directly to the PCB 200, such as in the lower right corner at component 202), such that the sensors are positioned in the mixed plenum 102 (e.g., where the controller 114 is mounted). In some examples, these sensors can be externally mounted (e.g., external to the controller 114) and can communicate with the controller 114 (e.g., with the components of the PCB 200) via a wired or wireless connection. In examples, the sensor(s) can provide signals and data to the controller that represents conditions or properties (e.g., temperature, humidity, etc.) associated with the outside air 104 and/or the properties of the mixed air in the mixed plenum. The PCB 200 can also include connectors 204 for connection (e.g., wired connection) to one or more other components, such as the FAV equipment, DAT sensor, and AHU-state sensor.

In at least some examples, the system 100 can include a component that does not rely on proprietary communications and that can determine when the AHU fan 108 is on (e.g., the component can detect a condition that indicates or suggests the AHU fan is running). That is, even though the AHU 108 can be a component of a system that uses proprietary communication (e.g., a VRF or VRV system), the system 100 can still determine when the AHU fan 108 is likely running and can use that status information to optimize control and operations of other components (e.g., the FAV components). Based on the determination, fresh air 104 can be pulled into the system (e.g., via the fan powered product 110 and/or the dampered duct 112).

In some examples, the component (AHU-state sensor) for determining when the AHU fan 108 is lily on includes provisions for a low voltage signal to be used with a current sensing switch or a pressure sensing switch to indicate when the motor of the AHU fan is operating (e.g., ECM).

Referring to FIG. 3, a schematic of a system 300 is depicted, and the system 300 can be a part or subsystem within the system 100. For example, the system 300 can include connections 302 (e.g., connectors) that are associated with the controller 114 (e.g., the connections 302 can correspond with the connectors 204 on the PCB 200). In at least one example, the AHU-state sensor 304 includes a current-sensing switch (e.g., C-sensor) that connects to the controller 114, such as via a wired connection into the connections 302. In addition, the controller 114 can be connected (e.g., via the connections 302) to the ventilation fan 306 (e.g., FAPV fan) that draws in outside air, and this could also/alternatively include a damper (e.g., FAD).

In FIG. 3, the state sensor 304 can (e.g., via the current sensing switch) isolate activation of the switch due to idle currents common with motors of AHU fans (e.g. ECM-type motors). In examples, this current sensing switch could be installed onto the mains line feed or on the motor lead supplying power to the motor unit. In examples, the current sensing switch can be adjustable to compensate for idle current within the system to reduce the likelihood of false triggering of the ventilation controller. In examples, when the central fan (e.g. AHU fan) becomes active (e.g., such as by the controlling thermostat 107), the sensing switch will close its contacts to complete a low voltage circuit within the controller 114 (e.g., via the connections 302) to indicate the fan 108 might be operating. In other words, the sensor 304 can detect a condition (e.g., current) and send a signal (e.g., data) to the controller 114. When the central fan 108 stops activity and power is no longer supplied, the circuit of the sensor 304 will become open, which can be interpreted by the controller 114 as a signal from the sensor 304 that the AHU fan might not be running. In at least some examples, this solution provides a mechanism to determine when the AHU fan 308 (e.g., the fan of the AHU 108) is likely on without having to rely on proprietary communication associated with the system 100 (e.g., such as when the AHU is part of a VRV or VRF system).

Referring to FIG. 4, a schematic of a system 400 is depicted, and the system 400 can be a part or subsystem within the system 100. For example, the system 400 can include connections 402 that are associated with the controller 114 (e.g., the connections 402 can correspond with the connectors 204 on the PCB 200). In at least one example, the AHU-state sensor 404 includes a pressure switch that connects to the controller 114, such as via a wired connection into the connections 402. In addition, the controller 114 can be connected (e.g., via the connections 402) to the ventilation fan 406 (e.g., FAPV fan) that draws in outside air, and this could also/alternatively include a damper (e.g., FAD).

In examples, the sensor 404 might be a less invasive installation, as compared to the current sensing switch of the sensor 304. For example, an adjustable pressure switch could be easier to install in the ductwork before and/or after the AHU fan (e.g., easier as compared to the sensor 304 in which it might be necessary to break a mains circuit or fitting the device in the non-class II area of the AHU). In examples, the pressure sensing switch of the AHU-state sensor 404 can be adjustable to cover a wide range of static pressures starting as low as 0.08 in. WC up to 1.2 in. WC. In examples, the pressure switch contacts are made (e.g., to complete the circuit) when the pressure changes beyond some threshold (e.g., pressure increases above a threshold). In response, a signal (e.g., data) can be provided to the controller 114 to indicate the AHU fan 408 is likely running. In addition, when the pressure falls below the threshold, the circuit is broken, which can similarly be interpreted as a signal (e.g., data) by the controller 114 that the AHU fan may not be running. In at least some examples, this solution provides a mechanism to determine when the AHU fan 408 (e.g., similar to the fan of the AHU 108) is likely on without having to rely on proprietary communication associated with the system 100.

In some examples, the system 100 can include the system 300 and the system 400, which can provide redundancy related to determining a state of the AHU without relying on proprietary communications. In some examples, the system 100 can include the system 400 without the system 300 (e.g., without the current sensor 304). In some examples, the system 100 can include the system 300 without the system 400 (e.g., without the pressure sensor 404)

In at least some examples, and consistent with FIGS. 3 and 4, the discharge-air-temperature (DAT) sensor 310 or 410 can be used to determine (e.g., by inference) whether the thermostat is calling for cooling or heating (e.g., due to temperature change monitored by the sensor 310 or 410). In this respect the DAT sensor 310 or 410 can be used determine if the system 100 is in heating (e.g., the air temperature measured is increasing by at least a threshold amount), cooling (e.g., the air temperature measured is decreasing by at least a threshold amount), or the thermostat is operating the fan for circulation purposes only (e.g., the air temperature is not changing by more than a threshold amount).

The controller 114 (e.g., ventilation controller) can be programmed to execute various protocols. In at least one example, for some initial threshold duration of activity from the ECM motor (e.g., first 45 seconds), the ventilation controller 114 can measure the return air temperature and humidity (e.g., via one or more sensors in the return air supply duct) to get a baseline of the interior conditions (e.g., inside the home 106). After the initial threshold duration of central fan activity, the ventilation controller 114 can turn on the FAPV-L 110 and/or FAD 112 and allow for a grace period (e.g., 45 seconds) of which, the ventilation controller 114 can determine whether the fresh air ventilation should continue (e.g., based on whether outside air 104 humidity and temperature are suitable for ventilation, such as using the sensors connected via 202) or whether the ventilation should be terminated (e.g., outside air is too humid, too hot or too cold to continue ventilation). If the fresh air 104 from the outside is unsuitable for ventilation, the ventilation controller 114 can place a hold on fresh air ventilation and wait for a change in the DAT sensor 310 or 410 temperature. A drop in temperature (as measured via the DAT sensor 310 or 410) can indicate the system 100 is in cooling mode and a rise in temperature (as measured via the DAT sensor 310 or 410) can indicate the system 100 is in heating.

If the ventilation controller 114 has aborted a fresh air ventilation due to temperature or humidity, the ventilation controller 114 can be in waiting mode for heating or cooling to become active in order to continue with the fresh air ventilation activity. If the measured humidity levels are on a rise due to fresh air ventilation (e.g., based on receiving data from the sensors connected to 202), the ventilation controller 114 can terminate the call for ventilation and wait until humidity levels monitored in the mixed plenum 102 have dropped to suitable levels before continuing the ventilation activity.

In examples, the controller 114 can, based on one or more various settings, optimize the delivery of fresh air to the system (e.g., after the controller 114 has determined that one or more pre-conditions are met for the delivery of fresh air, such as the AHU fan 108 being on and/or the outside fresh air being associated with suitable conditions).

In some instances, the controller 114 can adjust the fresh air activity time (e.g., operating time of the FAV fan 110 or opening time of the damper 112) due to increase or decrease in mixed plenum 102 relative humidity (e.g., based on data from the sensors 116).

In some examples, the controller 114 can adjust the fresh air activity time (e.g., operating time of the FAV fan 110 or opening time of the damper 112) due to increase or decrease in mixed plenum 102 temperature (e.g., based on data from the sensors 116).

In some examples, the controller 114 can adjust the fresh air flow rate (e.g., by adjusting a fresh-air damper position to be more open or closed and/or by adjusting FAV fan motor speeds/operation) due to increase or decrease in mixed plenum relative humidity.

In some examples, the controller 114 can adjust the fresh air flow rate due to increase or decrease in mixed plenum temperature.

In some examples, the controller 114 can dynamically control fresh air ventilation across a wide activity range (e.g., 0% to 150% of the fresh air ventilation activity) based on the air conditions. For example, fresh-air ventilation activity could be reduced to some level greater than 0% (e.g., to 25%) when conditions do not result in saturated humidity levels but are not quite favorable to sustain a longer running time. In at least some examples, during periods of good to prime environmental conditions (e.g., associate with the fresh air conditions), the FAV activity can be increased up to 150%. In doing this over a 24 hour period, this can compensate for periods of activity that were less suitable for ventilation.

As used herein, a recitation of “and/or” with respect to two or more elements should be interpreted to mean only one element, or a combination of elements. For example, “element A, element B, and/or element C” may include only element A, only element B, only element C, element A and element B, element A and element C, element B and element C, or elements A, B, and C. In addition, “at least one of element A or element B” may include at least one of element A, at least one of element B, or at least one of element A and at least one of element B. Further, “at least one of element A and element B” may include at least one of element A, at least one of element B, or at least one of element A and at least one of element B.

This detailed description is provided in order to meet statutory requirements. However, this description is not intended to limit the scope of the invention described herein. Rather, the claimed subject matter may be embodied in different ways, to include different steps, different combinations of steps, different elements, and/or different combinations of elements, similar or equivalent to those described in this disclosure, and in conjunction with other present or future technologies. The examples herein are intended in all respects to be illustrative rather than restrictive. In this sense, alternative examples or implementations can become apparent to those of ordinary skill in the art to which the present subject matter pertains without departing from the scope hereof.