The present disclosure relates generally to HVAC systems, and more particularly, to HVAC control systems for adjusting HVAC system settings.
Heating, ventilation, and/or air conditioning (HVAC) systems are often used to control the comfort level within a building or other structure. Such HVAC systems typically include an HVAC controller that controls various HVAC components of the HVAC system in order to affect and/or control one or more environmental conditions within the building. Such HVAC controllers typically have a user interface for allowing a user to interact and the HVAC controller. The user interface is often integral with the HVAC controller housing, but in some instances, can be remote from the HVAC controller, such as when using a user interface of a smart phone, tablet computer, personal computer, laptop etc.
The present disclosure relates generally to HVAC systems, and more particularly, to HVAC control systems for adjusting HVAC system settings.
In one example, an HVAC system of a building may be controlled by an HVAC control system. The HVAC control system may include a communications block, a controller operatively coupled to the communications block, and a user interface operatively coupled to the controller. The communications block may receive sensed data from each of two or more sensing devices located at different spaced locations within the building. The controller may receive the sensed data from the communications block and based, at least in part, on the received sensed data, determine a recommended setting change to the HVAC control system. The user interface may display the recommended setting change.
In some cases, the HVAC control system may be at least partially implemented on a cloud server configured to communicate with a plurality of HVAC systems each in a separate building. Each of the plurality of HVAC systems may include two or more spaced sensing devices and an HVAC controller for controlling one or more HVAC components of the corresponding HVAC system. The cloud server may include a communications block, a memory, and a controller. The communications block may receive HVAC data from each of the plurality of HVAC systems. The HVAC data may include environmental data that is based at least in part on one or more of the environmental parameters sensed by the two or more spaced sensing devices of a corresponding HVAC system. The memory may store the HVAC data and the controller may analyze at least part of the received HVAC data stored in the memory and determine a recommended setting change for a first HVAC system of the plurality of HVAC systems. In some cases, the controller may output the recommended setting change to a user interface via the communications block. The user interface may be located remotely from the cloud server.
In operation, the HVAC control system may collect environmental sensor data via two or more sensing devices located at two or more identified locations within a building. Then, the HVAC control system may analyze the collected environmental sensor data in conjunction with the two or more identified locations of the sensing devices to determine a recommended setting change to the HVAC control system. The recommended setting change may be displayed to a user via a user interface that may be associated with the HVAC control system.
The preceding summary is provided to facilitate an understanding of some of the innovative features unique to the present disclosure and is not intended to be a full description. A full appreciation of the disclosure can be gained by taking the entire specification, claims, drawings, and abstract as a whole.
The disclosure may be more completely understood in consideration of the following description of various illustrative embodiments in connection with the accompanying drawings, in which:
While the disclosure is amenable to various modifications and alternative forms, specifics thereof have been shown by way of example in the drawings and will be described in detail. It should be understood, however, that the intention is not to limit aspects of the disclosure to the particular illustrative embodiments described. On the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the disclosure.
The following description should be read with reference to the drawings wherein like reference numerals indicate like elements throughout the several views. The description and drawings show several embodiments which are meant to be illustrative in nature.
In some instances, the building automation system 4 may include and/or be in communication with a remote system 36 (see
An HVAC system of building 2 may be controlled by an HVAC control system implemented in one or more of a wall mounted thermostat, an equipment interface module, a remote system 36 (e.g., cloud server) or other device. The HVAC control system may include a communications block and a controller operatively coupled to the communications block. The communications block may receive information from the HVAC system and the controller may receive the information and in response, use the information in analyses, to make determinations, to provide recommendations to a user interface, and/or to provide control signals to the HVAC system. In some cases, the HVAC control system (e.g., a building control system) may include a building automation controller 18, a remote system 36, and/or other controller.
The illustrative HVAC system of
In some instances, one or more of the HVAC components 6 (e.g., hydronic heating, electric heating strips, etc.) may be utilized in a stage with one or more other HVAC components 6 (e.g., in a forced air heating system, etc.). In an example, electric heating strips may be a stage in a heat pump system, where the electric heating strips may supplement the heat pump system when outdoor temperatures become too cold.
In some cases, combinations of HVAC components 6 may be used to provide quicker response times in reaching a set point than if only a single HVAC component 6 or system is used. Faster response times may be particularly noticeable when manually changing the setpoint temperature or when recovering from a programmed setback temperature, particularly when using a hydronic or other heating system that has a slower response time.
It is contemplated that a building automation controller(s) 18 may be configured to activate, deactivate, and/or otherwise modulate the building automation sub-system(s) 12 (e.g., the HVAC system) or components of the building automation sub-system(s) 12 (e.g., HVAC components 6) of the building automation system 4 in a controlled manner (e.g., to control the comfort level in in one or more spaces of the structure or building 2 and/or otherwise operate electronic features of the building 2 and provide suggestions for manual configuration of manually adjustable devices). The building automation controller(s) 18 may be configured to control the devices of the building automation system 4 or building automation sub-systems 12 via a wired or wireless communication link 20.
In some cases, the building automation controller(s) 18 may be or may include a thermostat, such as, for example, a wall mountable thermostat or intelligent power switch (e.g., for controlling appliances not equipped with communications capabilities and other appliances), but this is not required in all instances. An example thermostat may include (e.g. within the thermostat housing), or have access to, a temperature sensor for sensing an ambient temperature at, near, or spaced from the thermostat and/or other sensors for sensing other comfort level conditioning parameters (e.g., humidity, occupancy, sound, light, particle levels, etc.). In some instances, the building automation controller(s) 18 may be or may include an equipment interface module (EIM), a zone controller, or multiple EIMs or zone controllers each monitoring and/or controlling the comfort level within a particular zone or space (e.g., a comfort level conditioned space) in the building 2 or other structure.
In the illustrative building automation system 4 shown in
In many instances, one or more air filters 23 may be used to remove dust and other pollutants from the air inside the building 2. In the illustrative example shown in
In some cases, the system of vents or ductwork 10 and/or 14 may include one or more dampers 24 to regulate the flow of air through the vent, but this is not required. The dampers 24 may be positioned along the ductwork 10 and/or 14 at any location. One or more active dampers 24 may be coupled (e.g., in a wired or wireless manner) to one or more HVAC controller(s) 18, EIMs, or zone controllers and may be coordinated with the operation of one or more HVAC components 6. The one or more HVAC controller(s) 18 may actuate active dampers 24 to an opened position, a closed position, and/or to a position between the opened position and closed position (e.g., a partially opened position) to modulate the flow of air from the one or more HVAC components 6 to an appropriate room and/or zone in the building 2 or other structure. The dampers 24 may be particularly useful in zoned HVAC systems, and may be used to control which zone(s) receive(s) conditioned air from the HVAC component(s) 6.
In some instances, register vents 26 may include one or more vent dampers 30 located at or adjacent a position which air or fluid exits the ductwork 10 and enters a conditioned space to control delivery of the conditioned air from the one or more supply air duct 10 into the building 2. The register vents 26 may include one or more manually operated register vents 26 with manually operated vent damper 30a (see
Illustratively, the register vents 26 may be utilized in any manner to facilitate comfort level conditioning in one or more spaces. In some instances, the register vents 26 may be utilized to form one or more zones in a comfort level conditioned space. For example, the register vents 26 may be utilized to create one or more zones in the conditioned space even though, to that point, the HVAC system was not a zoned system. Alternatively, or in addition, register vents 26 may be utilized to create one or more further zones or one or more sub-zones in an HVAC system that is already configured to be at least partially zoned.
As shown in
As mentioned, each zone of a building (e.g., building 2) may include at least one sensor. In some instances, a sensor (e.g., a local sensor 34) may be associated with each register vent 26, but this is not required. In some cases, a sensor may be associated with two or more register vents 26 (such as two register vents located in the same zone). Alternatively, or in addition, a sensor may be associated with the building automation controller 18 and/or may be a remote sensor in communication with the building automation controller 18. The sensors may be configured to sense one or more environmental parameters and may be in communication with a local controller or other mechanism for communicating the sensed parameter to a device configured to adjust and/or monitor comfort level conditioning settings of the building automation system 4 (e.g., the HVAC system of building 2).
Register vents 26 may include a vent 28 configured to receive fluid flow from a building automation sub-system 12 (e.g., fan 21, a furnace, an air conditioner, etc. of an HVAC system) and a manually operated vent damper 30a, as best shown in
In some instances, one or more register vents 26 of a plurality of register vents 26 of a conditioned space may be manually operated. Manually operated register vents 26 may be manually adjusted by a user by manually adjusting a mechanism to open and/or close a vent damper 30 with respect to an associated vent 28. Alternatively, or in addition, adding a manually operated vent damper 30a to a vent 28 may form a manually adjustable register vent 26.
In some cases, when a manually operable vent damper 30a is added to a vent 28, the vent damper 30 may be a magnetic sheet that is mechanically and/or electrically connected to a proximal side or distal side of the vent 28 and/or other vent damper 30 mechanism that may be mechanically connected to the vent 28. Manually operated register vents 26 refer to register vents 26 that include a manually operated vent damper 30a which may be manually adjusted by a user to control flow of fluid through an associated vent 28. In some instances, the manually operated register vents 26 may include a local controller and/or a local sensor for sensing environmental parameters, but this is not required.
In some instances, but not all, electronically controlled register vents 26 may include one or more of a vent 28, an electronically controlled vent damper 30b, an actuator 31, a local controller 32, a communications port or block 33 having a wired or wireless interface for communicating with the HVAC control system and/or other register vents 26, and/or a local sensor 34. An electronically controlled register vent 26 may be a register vent 26 that is capable of being selectively and/or automatically controlled by a controller (e.g. a local controller 32, a building automation controller 18, a remote system 36 and/or other controller).
When a register vent 26 includes a local sensor 34 or other sensor, it may be considered a sensing device. The local controller 32 of the register vent may be in communication with a building automation controller 18 other controller of the HVAC control system via communications port or block 33 of the register vent 26 and/or or other communications port or block (e.g., communications port or block 42, 44) having a wired or wireless interface and may be electronically controlled from the building automation controller 18 or other device or system in communication with the building automation controller 18. In instances when a plurality of electronically controlled register vents 26 are included in a building automation system 4, positions (e.g., an opened position, a closed position, or positions therebetween) of the electronically controlled vent dampers 30b with respect to the vents 28 of the electronically controlled register vents 26 may be controlled by the building automation controller 18 and/or any other controller including, but not limited to, the local controllers 32 at the register vent 26, and/or any device or system connected thereto.
Illustratively, the local sensor 34 of a register vent 26 associated with an electronically controlled register vent damper 30b may sense one or more local conditions in the building and the local controller 32 of the register vent 26 may communicate or issue one or more requests to the building automation controller 18 or other controller of the HVAC control system for conditioned air or other request of the HVAC system. In response to receiving the request, a controller of the HVAC control system may be configured to determine a setting (e.g., damper setting) for the electronically controlled register vent damper 30b and communicate the determined setting for the electronically controlled register vent damper 30b via the communications block of the HVAC control system to a user interface (e.g., user interface 46), to the local controller 32 of the register vent 26, and/or to one or more other device of the HVAC system or HVAC control system. The controller of the HVAC control system may determine which HVAC component(s) 6 should be active, if any, and provide one or more control signals to that HVAC component 6 to activate or keep active that HVAC component 6.
In some cases, the local controllers 32 may be in communication with one another to facilitate zone or sub-zone synchronization and/or optimization. In such instances, each local controller 32 may set a position of an associated vent damper 30 electronically in view of other set positions of other vent dampers 30 associated with other local controllers 32. In some instances, the local controllers 32 and/or other controllers in communication with the vent dampers 30 may consider the state of manually operated register vents 26, electronically operated register vents 26, vents 28 without vent dampers 30, and/or input from controllers (e.g., building automation controllers 18 or other controllers) of the building automation system 4 in addition to or other than the local controllers 32.
The local controllers 32 may be configured to have one-way or two-way communication with the building automation controller(s) 18 and/or a remote system 36 via communications port or block 33. In instances of one-way communication with the building automation controller(s) 18 and/or remote system 36, the local controllers 32 may communicate positions of the vent dampers 30, sensed parameters at or about the register vent 26, and/or other information to the building automation controller(s) 18 and/or the remote system 36. Alternatively, the local controllers 32 having one-way communication with the building automation controller(s) 18 and/or remote system 36 may receive positioning commands for the vent dampers 30 and/or other information from the building automation controller(s) 18 and/or the remote system 36. In instances of two-way communication with the building automation controller(s) 18 and/or the remote system 36, the local controllers 32 may communicate positions of the vent dampers 30, sensed parameters at or about the register vents 26, and/or other information to the building automation controller(s) 18 and/or the remote system 36, and the local controllers 32 may receive positioning commands for the vent dampers 30 and/or other comfort level conditioning information/commands from the building automation controller(s) 18 and/or the remote system 36. In one example of communication between the register vents 26 and the building automation controller 18, the register vents 26 may be configured to call for conditioning (e.g., heating and/or cooling) of an associated space (e.g., a zone or sub-zone), call for fan 21 operation, call for humidification, call for dehumidification, call for air purification, and/or call for operation of one or more other pieces of equipment.
Control of the register vents 26 may be centralized at the building automation controller 18, at any other controller in the building 2 (e.g., including, but not limited to, one of the local controllers 32), and/or at the remote system 36. When register vents 26 are centrally controlled, the building automation controller 18, other controller, and/or the remote system 36 may be able to control comfort level conditioning in a calculated manner (e.g., keep at least 10%-70%, 20%-60%, 30%-50%, or other range of vent dampers 30 in an open position) due to the knowledge of how much fluid is passing to one or more locations and at what time that fluid is reaching one or more locations within a comfort level controlled space. Illustratively, a building automation controller 18 or other controller that centrally controls the register vents 26 may take into consideration vent damper 30 position settings of manually controlled register vents 26, along with position settings of electronically controlled register vents 26. Understanding the positioning of all of the vent dampers 30, if any, associated with vents 28 in a comfort level conditioned space allows the building automation controller 18 or other central controller to apply comfort level conditioning settings for the building automation system 4 in view of an amount of fluid calculated to be reaching one or more locations of a space or zone. Keeping some minimum percentage of the vent dampers open may also help prevent excessive load on the fan 21 of the HVAC system servicing the building.
As discussed, and in some instances, a register vent 26 may include one or more local sensors 34. The local sensors 34 may be configured to sense one or more parameters related to setting a comfort level in the conditioned space and store and/or communicate the sensed parameters via the local controller 32. In one example, the local sensors 34 may be configured to sense one or more of a temperature, physical occupancy/presence, changes in temperature, humidity levels, changes in humidity level, air quality levels or conditions (e.g., particle count, light, volatile organic compound (VOC) concentration or levels, CO2 concentration or levels, etc.), changes in air quality levels or conditions, sound through or around the register vents 26, vibrations, voice patterns, pressure, flow, and/or any other suitable sensed parameters. In some instances, the local sensors 34 and the local controllers 32 may be separate components or may be part of a single component.
In response to sensing one or more parameters with a sensing device of the building automation system 4, the local controllers 32, the building automation controllers 18, and/or the remote system 36 may take one or more actions to adjust a comfort level conditioning level within one or more particular spaces. In one example of using sensed parameters to adjust a comfort level within one or more particular spaces, a sensing device may provide a measurement of one or more sensed air quality conditions (e.g., particle count, light, volatile organic compound (VOC) concentration or levels, CO2 concentration or levels, etc.) to a controller and the controller may determine settings for one or more air quality components (e.g., UV lamps, air purification systems, air cleaning systems, air exchangers, etc.) of the HVAC components 6 in the building automation system 4 based, at least in part, on the provided measurements of sensed air quality conditions.
As discussed in greater detail below, the HVAC control system may save or store values of sensed parameters in a remote system 36 (e.g., in a cloud server) and, in some cases, control one or more HVAC components 6 and/or register vent dampers 30 based, at least in part, on stored values of the sensed environmental parameters. Additionally, or alternatively, the HVAC control system may be configured to receive a request for data related to the sensed parameters and provide (e.g., to a user interface) a report for the data related to the sensed parameters based, at least in part, on the stored values of the sensed parameter.
The local controllers 32, the building automation controllers 18, and/or the remote system 36 may utilize outputs of a local sensor 34 as a primary sensed parameter for controlling comfort level conditioning of a space, as an averaged sensed parameter that is used in conjunction with other outputs of local sensors 34 and/or other sensors to control comfort level conditioning of a space, as a sensed zone parameter for controlling comfort level conditioning of a particular zoned or sub-zoned space, and/or as a sensed parameter for other comfort level conditioning. Such use of local sensors 34 at register vents 26 may facilitate dividing a comfort level conditioned space into zones (e.g., macro-zones) and/or sub-zones (e.g., micro-zones), identifying temperature gradients across a comfort level conditioned space and/or zones to optionally identify further zoning opportunities, improving an accuracy of a sensed parameter from a user comfort level perspective for a comfort level conditioned space by averaging a plurality of sensed parameters sensed by the local sensors 34, and/or may facilitate providing other functions and/or benefits.
In some instances, the local sensors 34 or other sensors may sense when someone is present in a comfort level conditioned space and apply settings for the comfort level conditioned space associated with a “space occupied” profile or other profile. In other similar or different instances, the local sensors 34 may be configured to sense when a particular individual is present in a comfort level conditioned space and apply settings for the comfort level conditioned space associated with that particular individual's profile saved in a memory of one or more of the local controller 32, the building automation controller 18, and the remote system 36. The local sensors 34 may identify particular individuals in any manner, including but not limited to, sensing an individual's biometrics, sensing an individual's voice, sensing vibrations caused by an individual advancing through a space, sensing an identification tag carried by the individual (e.g. RFID tag, cell phone, etc.), and/or other identifying techniques. Additionally, or alternatively, the local sensors 34 or other sensors may sense other parameters and/or apply one or more comfort level conditioning profiles as determined by a preset or predefined program of the HVAC system.
In some instances, a controller of or in communication with the HVAC system may be capable of identifying one or more local devices 56 (see
A building automation controller 18 (e.g., a thermostat or other controller), as depicted in
The device controller 52 may be configured to automatically or upon request sense a local device 56, sense an action taken thereby through detecting one or more changes in environmental parameters, and/or send a control signal to the local device 56. In such instances, the device controller 52 may be in communication with the local sensors 34 or other sensors of the HVAC system to receive environment parameter data. Through analyses of changes in the received environmental parameter data, the device controller 52 may identify the presence of a local device 56 and/or an action taken thereby. In some cases, the device controller 52 may detect a presence of a local device 56 via a wired or wireless communication and the device controller 52 may identify an action taken by a local device 56 via analysis of environmental parameter data. In one example, the device controller 52 may analyze data received from a local sensor 34 adjacent a stove and may determine when the data from the local sensor 34 is indicating a rise in temperature. From the identification of the rise in temperature, the device controller 52 may identify the stove has taken a heating action and indicate that action taken to the processor 48 of the building automation controller 18. In response, the building automation controller 18 may set a vent damper 30 of a register vent 26 adjacent the space in which the stove is located to an opened position to cool the space and/or take other actions to compensate for the identified action taken by the stove.
When the device controller 52 detects that a local device 56 has taken an action or has been caused to make an action, the device controller 52 may provide a signal to the processor 48 of the building automation controller 18. In response to receiving a signal from the device controller 52 indicating a local device is taking or has made an action, the building automation controller 18 may, via a user interface 46 (e.g., the user interface 46 may be, but is not limited to one or more of, a mobile phone, a personal digital assistant, a laptop computer, a desktop computer, a thermostat screen, a voice control system, and other interfaces), suggest an adjustment to, or may automatically adjust, an environmental parameter set point of one or more HVAC components 6 conditioning a particular space or particular zone. In one instance, the building automation controller 18 may be configured to adjust a position setting of a vent damper 30 of one or more register vents 26 adjacent the space in which the local device 56 is located in response to the device controller 52 detecting one or more of a local device 56 and an action taken or made by the detected local device 56.
In some cases, the device controller 52 may be configured to detect one or more auxiliary environmental parameter control devices (e.g., a portable heater, a window air conditioner, or space conditioning device not directly controlled by the building automation controller 18). In response to detection of one or more of the auxiliary environmental parameter control devices and communication of the detection to the processor 48 of the building automation controller 18, the building automation controller 18 may be configured to adjust a position setting of a vent damper 30 of one or more register vents 26 and/or adjust one or more other settings. In some instances, the device controller 52 may receive a status signal from the auxiliary environmental parameter control device indicating a setting thereof (e.g., on/off, hi/low, level 1 or 2 or 3, etc.), and the building automation controller 18 may adjust a position of vent damper 30 of one or more register vents 26 and/or other settings to account for the setting of the auxiliary environmental parameter control device and maintain proper comfort level conditioning in a space. In some cases, the device controller 52 may change a setting of the auxiliary environmental parameter control device, such as turn on or off the auxiliary environmental parameter control device.
In some cases, the local sensors 34 and/or other sensors of the building automation system 4 that may be configured to sense one or more parameters of a comfort level conditioned space and may communicate the sensed parameters to the remote system 36 via one or more operably coupled local controllers 32 and/or the building automation controller 18 through the use of an operably coupled local communications port or block 44, as best shown in
The user interface 46 may be configured to communicate with controllers (e.g., the remote system 36 (e.g., cloud server), the local controller 32, the building automation controller 18, and/or other controllers) of or in communication with the HVAC system to obtain and/or receive analyses from one or more of the controllers based on data received from the local sensors 34 and/or other data. The obtained and/or received analyses may be of data specific to one or more particular zones or sub-zones and/or to any portion of or an entirety of the space that is conditioned with the building automation system 4. Illustratively, the controllers of the HVAC system of a building 2 may monitor the thermodynamics of different areas of the building 2. Such monitoring may include tracking heat gain and/or loss of each zone independently of other zones, which may allow the controllers to send to the user interface 46 suggested position settings for vent dampers 30 that may impact a rate of heating or cooling of a particular conditioned space of a building 2. The positioning of vent dampers 30 according to suggested position settings may facilitate establishing more even temperatures throughout a building because different spaces/zones/sub-zones throughout a building 2 may reach a set temperature at a more similar time, rather than at different times, which is often the case when all of the vent dampers 30 are set to the fully open position.
In addition, or as an alternative, to obtained and/or received analyses of data from local sensors 34, the obtained and/or received analyses at a user interface 46 may take into account data for area conditioning parameters of a plurality of HVAC systems, sizes of the vents 28 of the register vents 26, and/or sizes of the vent dampers 30 of the register vents 26. In some cases, the plurality of HVAC systems may be located in a single building or in one or more buildings about or around a subject building 2 (e.g., buildings in a neighborhood, on a same city block, etc.). In one example, the remote system 36 may be configured to monitor homes (e.g., buildings 2) in a community and track the impact of suggested changes to positions of vent dampers 30 and/or suggested changes to other HVAC components 6 on the operation of HVAC systems or thermodynamics in those homes. The remote system 36 may then compare the suggested changes of similar type, sized, geographically positioned, and/or geographically oriented homes to one another to determine successful changes. The successful changes may then be tracked over time and suggested to other users of the remote system 36 in response to environmental season changes, solar strength changes, humidity level changes, and/or other changes.
In some cases, analyses obtained and/or received by the user interface 46, may include recommendations for configuring one or more HVAC components 6 of an HVAC system. Illustratively, the recommendations may include one or more zoning recommendations, register vent 26 setting recommendations, temperature set point (or temperature program schedule) recommendations, etc., from the remote system 36, the local controllers 32, the building automation controllers 18, and/or other controllers.
The one or more zoning recommendations may, as discussed in further detail below, be developed based at least partially on sensed conditioning parameters of an area to be comfort level conditioned and/or data for sensed conditioning parameters of areas to be comfort level conditioned by one or more other HVAC systems (e.g., HVAC systems in buildings other than a subject building 2) received through a communications port or block (e.g., communications port or block 42 and/or communications port or block 44). Zoning recommendations may include general instructions or suggestions on how to zone a building 2, how to manually set zones, how to modify an existing zone to create sub-zones, when to modify an existing zone, how to set vent dampers 30 of register vents, and/or other instructions.
In one example of a building automation system 4 obtaining instructions, the remote system 36, local controller 32, the building automation controller 18, and/or other controller may provide an instruction to one or more register vents 26 (e.g., an electronically controlled register vent) to adjust a vent damper 30 for the purpose of improving the efficiency of establishing a desired comfort level conditioning setting or for other building conditioning-related purposes in response to obtaining or receiving the analyses from a controller of the HVAC system based, at least in part, on sensed data from local sensors 34 or other sensors. In some cases, the instruction to one or more register vents 26 may be provided to improve uniformity of temperature between spaced sensor locations, between spaced register vent locations, register dampers locations and/or generally within a space, to allow at least a minimum air flow from the HVAC system to help protect the HVAC system from damage, to maintain at least a minimum number of register vent dampers 30 in an open state, and/or for one or more other purposes. An indication of the provided instruction may be sent to the user interface 46 to alert a user of the instruction. In some cases, the controller of the HVAC system may be optionally and/or selectively set to automatically provide an instruction to one or more register vents 26 to adjust its vent damper 30 in response to a received recommendation and/or the controller may be optionally or selectively set to require a confirmation from a user at the user interface 46 before sending an instruction to one or more register vents 26 to adjust its vent damper 30. In some cases, an instruction may be sent to one or more register vents 26 for execution, and nothing may be sent to the user interface.
The user interface 46 or other user interface may be configured to indicate and/or display one or more suggestions or recommendations from a controller of the HVAC control system for manually setting positions of vent dampers 30 (e.g., a manually adjustable register vent dampers 30a) of one or more register vents 26 based, at least in part, on sensed data received from local sensors 34 or other sensors. The one or more suggestions may be obtained from one or more controllers of or in communication with the HVAC system of a building 2 (e.g., the controllers may include one or more of the remote system 36, the local controller 32, the building automation controller 18, and/or other controller). The controllers of the HVAC system of the building 2 may base the suggestions for manually setting positions of the vent dampers 30a at least partially on either or both of area conditioning parameters sensed by a sensor of the HVAC system and data related to conditioning parameters of one or more HVAC systems in a similar geographic region as a subject HVAC system.
As referred to above, the HVAC system of building 2 may include a plurality of register vents 26, where all of the plurality of register vents 26 are electronically controlled, all of the plurality of register vents 26 are manually controlled, and/or a portion of the plurality of register vents 26 are electronically controlled and a portion of the register vents 26 are manually controlled. In instances where the plurality of register vents 26 include one or more manually controlled register vents 26, a controller of or in communication with the HVAC system may suggest to the user a setting for a manually operated register vent 26 (e.g., a position setting for a manually operated vent damper 30a) to improve uniformity of temperature between spaced sensor locations, between spaced register vent locations, register dampers locations and/or generally within a space, to allow at least a minimum air flow from the HVAC system to help protect the HVAC system from damage, to maintain at least a minimum number of register vent dampers 30 in an open state, and/or for one or more other purposes. In instances where the plurality of register vents 26 include one or more electronically controlled register vents 26, a controller of or in communication with the HVAC system may suggest a setting for an electronically operated register vent 26 (e.g., a position setting for an electronically controllable vent damper 30b). In instances where the plurality of register vents 26 include both manually controlled register vents and electronically controlled register vents 26, a controller of or in communication with the HVAC system may suggest a setting for a manually operable register vent 26 and may request authorization to automatically set the position of the electronically operable register vents 26.
In response to receiving a suggestion at the user interface 46 for position settings of vent dampers 30 of the register vents 26, a user may, in some cases, be presented with an option to accept the suggestion, reject the suggestion, or modify the suggestion via the user interface 46. When the register vents 26 include both electronically controlled and manually controlled vent dampers 30a, the user interface 46 may provide or display options to accept the suggestion, reject the suggestion, or modify the suggestion with respect to the electronically operable vent dampers 30b, the manually operable vent dampers 30a, or both.
When the register vents 26 have manually operable vent dampers 30a, a user may accept, reject, or modify the position setting suggestion for the manually operable vent dampers 30a and then either manually adjust the manually operable vent dampers 30a according to the suggestion or the modified suggestion, or do nothing in the event the suggestion was rejected. After the user has made a selection or confirmation at the user interface 46 with respect to acceptance, rejection, or modification of the suggested position setting for the vent dampers 30, one or more controllers of the HVAC system may monitor heat gain and/or loss, or other parameter, to determine whether the user positioned the vent dampers 30 consistent with accepting, rejecting, or modifying the suggested position setting of the vent dampers 30. If no change in heat gain and/or loss, or other parameter, is realized by the controller of or in communication with the HVAC system, the controller may determine no changes were made (which may be consistent with rejecting a suggested vent damper 30 position setting) or that the changes made had no impact. Identification by the controller of or in communication with the HVAC system of either situation may prompt the controller to recommend the changes again or recommend new changes to the system to try and impact the comfort level conditioning in a space in a desirable manner. Alternatively, the controller may recognize that a user is not interested in obtaining instructions, and refrain from providing further suggestions of position settings for vent dampers 30 for a selected or default period of time.
When the register vents 26 have electronically operable vent dampers 30b, a user may accept, reject, or modify the position setting suggestion for the electronically operable vent dampers 30b and then, in response, the controller(s) of or in communication with the HVAC system may automatically effect the position settings of the vent dampers 30. Alternatively, the controllers of or in communication with the HVAC system may automatically effect any suggestion and provide a confirmation to the user interface 46 of such changes to the position settings of the vent dampers 30. After a suggestion has been implemented/accepted, rejected, or modified, one or more controllers of the HVAC system may monitor heat gain and/or loss, or other parameter, as discussed above, to determine the effect of the modification of the vent damper position setting on sensed comfort level parameters in the conditioned space. The controller(s) of or in communication with the HVAC system may learn from the monitoring which vent damper 30 position settings may be effective and which are not as effective for improving the operation of the HVAC system over time.
When either or both electronically operable vent dampers 30b and manually operable vent dampers 30a are included in a building automation system 4, the controllers of or in communication with the HVAC system may take into consideration whether a user accepted, rejected, or modified one or more of the suggested position settings for either or both of the manually operable vent dampers 30a and the electronically operable vent dampers 30b. For example, if the suggested position settings for the manually operable vent dampers 30a are rejected and the position settings for the electronically operable vent dampers 30b are accepted, the controller(s) of or in communication with the HVAC system may modify the suggested position settings taking into account the lack of desire on the part of a user to change the position settings of the manually operable vent dampers 30a.
The HVAC system may store an indicator of vent damper settings or positions of one or more of the vent dampers 30 in memory 38 or other memory. Additionally or alternatively, the HVAC system may store data sensed by the local sensors 34 or other sensors, sensor locations of the local sensors 34 or other sensors within the building 2, an indicator of register vent 26 locations within the building 2, an indicator of register vent damper 30 locations within the building 2, thermodynamic properties of the building 2, historical sensed data, and/or other building automation system 4 information. The building automation controller 18 or other controller may determine recommended settings for devices of or related to the HVAC system (e.g., one or more manually adjustable register vent dampers 30a, etc.) and/or may control device of or related to the HVAC system (e.g., one or more electronically controllable register vent dampers 30b, etc.) based, at least in part, on the received sensed data, the stored indicators of the sensor locations, the stored indicators of register vent 26 locations within the building 2, the stored indicators of register vent damper 30 locations within the building 2, analyses of thermodynamic properties of the building 2, historical sensed data, other building automation system 4 information, and/or similar or dissimilar HVAC related data from each of a plurality of HVAC systems.
The building automation controller 18 or other controller (e.g., a controller of the remote system 36) may use stored or other building information (e.g., as discussed above) to make and/or implement recommendations including setting changes to the building automation system 4 and display those recommendations via a user interface. In one example, operation of an HVAC control system may include collecting environmental sensor data via two or more sensing devices located at two or more identified locations within a building. Then, analyzing the collected environmental sensor data in conjunction with the two or more identified locations of the sensors providing the data to determine recommended HVAC component 6 setting changes, if any, based at least partially on the sensed and/or stored data (e.g., collected data) and displaying the recommended setting changes to a user via a user interface that may be associated with the HVAC control system. If no changes are recommended, an indication that no changes were identified may be displayed on the user interface.
In one case, recommended setting changes and/or setting changes based on the sensed and/or stored data may include a manual adjustment to one or more manually adjustable register dampers, an adjustment to one or more electronically controllable register dampers, a suggestion to incorporate an electronically controllable register damper in the building at a particular location, an adjustment to a fan setting of the HVAC system (e.g., changing a mode of the fan between an on mode (e.g., the fan is always running when in this mode), an off mode (e.g., the fan is never runs while in this mode), an auto mode (e.g., when in this mode, the fan runs while the furnace, air conditioner, or other forced air HVAC component is running), a circulate mode (e.g., when in this mode, the fan runs according to a set schedule or a set percentage of the time in addition to running when the furnace, air conditioner, or other forced air HVAC component is running), and/or other modes) and/or other HVAC related recommendations. Such recommended setting changes and/or setting changes may facilitate optimizing a flow of air through a building to adjust a comfort level in the building and/or a specified zone, sub-zone, or area of the building.
In one example of using stored building automation system 4 information, the building automation controller 18 or other controller may be configured to make macro-zone and/or micro-zone adjustments and/or recommendations. When a building is zoned by floors, for example, the building automation controller 18 may be configured to maintain a first comfort level in a first macro zone of a first floor and a second comfort level in a second macro zone of a second floor. By using stored building automation system 4 information (e.g., settings or positions of register vent dampers 30 or other building automation system 4 information) or other information, the building automation controller 18 or other controller may adjust or provide a recommendation to adjust one or more settings (e.g., to adjust a register vent damper 30 setting, change a fan setting of the HVAC system to one of an on mode, an off mode, an auto mode, and a circulation mode, change a position of a window treatment) for a sub-zone or micro-zone within one or more of the first macro-zone and the second macro-zone that may be considered to be more effective than another option based on the stored building automation system 4 information. In some instances, a micro-zone may be established to compensate for a hot spot or cool spot within the macro-zone and/or to allow a user to adjust a comfort level of only a portion of a larger zone.
As discussed, the building automation controller 18 or other controllers may adjust or provide instructions or recommendations for adjusting individual register vent dampers in one or more zones of a building 2. In one example, the building automation controller 18 may be configured to adjust and/or determine a first recommended setting for one or more register vent dampers 30 (e.g., manually adjustable and/or electronically controllable register vent dampers) that service a first zone of the building 2 and a second recommended setting for one or more register vent dampers 30 (e.g., manually adjustable and/or electronically controllable register vent dampers) that service a second zone of the building 2 based, at least in part, on stored building automation system 4 information and/or other information.
The controllers of or in communication with the HVAC system may continually monitor the impact of suggested and/or implemented adjustments on a performance of the HVAC system (e.g., vent dampers 30 settings, fan 21 settings, etc.). In response to the monitoring of the HVAC system, the controllers of or in communication with the HVAC system may (optionally) automatically adjust settings of the HVAC components 6 and/or recommend or suggest changes to settings of the HVAC components 6. In some cases, the controllers of the HVAC system may learn from the monitoring of the HVAC system settings and the effect of those settings on a conditioned space, such that the controllers of or in communication with the HVAC system may provide improved suggestions over time.
In one example of controllers of or in communication with an HVAC system that monitor adjustments to the settings of HVAC components and the associated effect on a comfort level of a conditioned space, if any, the controllers may suggest through the user interface 46 that a user closes all vent dampers 30 in a basement, the user set all of the vent dampers 30 on a middle level to a 50% open position, and leave all vent dampers 30 on the upper level fully open. The user then may indicate through the user interface 46 that such suggested changes were made. In the example, the controllers of or in communication with the HVAC system may notice the user changed a sleeping temperature when the HVAC system was in a cooling mode to a higher setting. The controllers of or in communication with the HVAC system may then conclude that the suggested changes and/or changes made were successful and potentially resulted in energy savings due to the allowed higher temperature when the system was in a cooling mode. The controllers (e.g., via the remote system 36) may then push the suggested HVAC component 6 settings (e.g., settings of vent dampers 30) to other buildings (e.g., homes) in a community around the monitored building. Additionally, or alternatively, the controllers may store the suggested HVAC component 6 settings for similar situations (e.g., situations taking into account past, current, and expected future thermodynamics of a building 2, conditions outdoors, etc.) in the future. In some cases, these settings may be automatically applied when similar environmental situations are identified in the future.
In some instances, the remote system 36 may include a remote communications port or block 42, where the remote communications port or block 42 may be in communication with the processor 40 and the memory 38 of the remote system 36, along with a local communications port or block 44 of one or more building automation systems 4. The local communications port or block 44 may be in communication with the local controllers 32 and/or local sensors 34 of the register vents 26, the building automation controllers 18, and/or a user interface 46 of the building automation system 4. The local communications port or block 44 may be a part of or may be a separate device from one or more of the local controllers 32 of the register vents 30, the building automation controllers 18, the user interface 46, and/or other device or feature of the building automation system 4.
The remote system 36 may be a cloud based (e.g., internet connected) system that is configured to connect and/or monitor one or more HVAC systems of one or more related or unrelated buildings. In one instance, the remote system 36 may be configured to monitor the number of register dampers in a building 2 and ensures a requisite amount of air is delivered to one or more conditioned spaces of the building 2. In an example and similar to as discussed above regarding centralized control, the remote system 36 may attempt to ensure 10%-70%, 20%-60%, 30%-50%, or other appropriate percentage range of the number of register vents 26 in the building are open and fluid is flowing form an HVAC component 6 through the vents 28. Such monitoring is helpful in preventing and/or mitigating static pressure build up in ductwork of an HVAC system of the building 2 and protecting HVAC components 6 of the HVAC system.
In some instances, the remote system 36 may monitor previous, current, and/or anticipated outdoor conditions. Such monitoring may include, but is not limited to, monitoring temperature, humidity, solar strength, solar position, and/or other outdoor conditions. In response, at least in part, to analyses performed on the outdoor conditions, the remote system 36 may suggest adjusting a position of one or more vent dampers 30 to ensure proper conditioning of all areas of a conditioned space (e.g., a house). In one example, the remote system 36 may determine an expected sun pattern will heat up a south facing side of a building faster than a north facing side at a particular time and thus, the remote system 36 may suggest maintaining vent dampers 30 on the south side of the building 2 in an open position longer during the summer months to cool the conditioned space adjacent the south side of the building 2 and compensate for the predicted solar load. Alternatively, or in addition, to monitoring and/or configuring a position of the vent dampers 30, the remote system 36 may be configured to adjust one or more HVAC related accessories and/or other accessories in the building that may be able to impact comfort level conditioning in a building or space in an efficient manner. For example, the remote system 36 may suggest that a user opens or closes shades and/or opens or closes windows in response to monitoring an outdoor condition. In instances where a building automation controller 18 is connected to or in communication with building accessories (e.g., window coverings, windows, etc.), the remote system 36 may communicate directly to the connected building accessories to position one or more of those building accessories at a particular setting to more efficiently operate the HVAC system in an economical manner while maintaining comfort for users in the building 2. In some cases, the remote system 36 may suggest turning on an auxiliary environmental parameter control device (e.g. a window air conditioning unit, a wall air conditioning unit, a portable electric heater, an electric fireplace, a portable electric fan, a ceiling fan, an electric floor heater) to maintain comfort if appropriate. When one or more auxiliary environmental parameter control devices can be controlled by the remote system 36, the remote system 36 may automatically active/deactivate such auxiliary environmental parameter control devices as appropriate.
The remote system 36 may be configured to monitor past, current, and/or future utility rates and/or usage of gas, electric, water, etc. for and/or at the building 2. From the information obtained by monitoring utility rates and/or utility usage, the remote system 36 may communicate with the building automation controller(s) 18 to facilitate operating the HVAC system at an energy efficient level while maintaining comfort for users occupying the conditioned space. In one example, the remote system 36 may suggest the HVAC system utilize a lower cost HVAC component 6 (e.g., electric heaters) when the cost of using an associated type of energy (electricity) is less than the cost of using a different type of energy (e.g., gas) for a different HVAC component (e.g., a gas furnace) that performs a similar conditioning function. The remote system 36 may, in some cases, automatically instruct the HVAC system to utilize a lower cost HVAC component 6 (e.g., electric heaters) when the cost of using an associated type of energy (electricity) is less than the cost of using a different type of energy (e.g., gas) for a different HVAC component (e.g., a gas furnace) that performs a similar conditioning function.
In some cases, the remote system 36, the building automation controller 18, and/or other systems or controllers may monitor an occupancy of the building 2. In one example of monitoring occupancy of the building 2, the remote system 36, the building automation controller 18, and/or other systems or controllers may utilize geofencing, an occupancy sensor, and/or one or more other mechanisms providing occupancy related information and/or data to monitor and/or determine occupancy of the building 2. Through monitoring occupancy of a building 2, such as through geofencing, the remote system 36 may suggest position settings for vent dampers 30 and/or other settings for HVAC components 6 to assist in limiting or minimizing cycling and/or run time of HVAC components 6. Cycling and/or run times may be limited or minimized by running heating and/or cooling operations of the HVAC system at a lower frequency when the building 2 or a space thereof is determined to be unoccupied. Such limiting or minimizing of cycling and/or run time of the HVAC components 6 may reduce the energy usage of the HVAC system, extend the life of one or more of the HVAC components 6, and/or allow zones of a zoned system to sync and operate similar to a non-zoned system. Geofencing may be particularly useful when HVAC components 6 that may be slower to condition a space to a set point (e.g., hydronics) are utilized for conditioning a space because the crossing of a geofence can be utilized to turn the HVAC component 6 on in sufficient time, or use additional HVAC components 6 to assist in reaching the desired set point before the space is expected to be occupied.
Geofencing is a term used to refer to sensing locations of an individual or device (e.g. via a location aware device) with respect to a geographically defined fence that is established a particular distance from the building. When an individual or device leaves the building and advances to a position outside of the particular distance from the building, the location aware device may detect that the user has crossed the geofence and is leaving for some time. Once a user exits the geofence, the building automation controller 18 may be configured to modify the operation of one or more HVAC components 6 (e.g., to a no occupancy profile). When an individual or device is returning to the building and advances to a position inside of the particular distance from the building, the location aware device may detect that the user has crossed the geofence and is returning home. Once a user enters the geofence, the building automation controller 18 may be configured to modify the operation of one or more HVAC components 6 (e.g., to an occupied profile).
In some instances, a system of the building automation system 4 (e.g., remote system 36 or other system) may be configured to create a model of one or more spaces of a building 2 to be controlled with a developed HVAC system configuration created by the remote system 36. Illustratively, a processing module (e.g., the processor 40 of the remote system 36 or processor of a mobile phone, a tablet, a laptop computer, or other computing device) may be configured to execute one or more sets of instructions stored in memory (e.g., the memory 38) to develop an HVAC system configuration for the modeled space(s) of the building 2. Through a user interacting with the remote system 36 via a web portal or other user interface accessible via the user interface 46 (e.g., a user interface of a thermostat, a mobile application, a web site, a PC application, thermostat screen, etc. accessible on a mobile phone, a tablet, laptop computer, or other computing device) of the building automation system 4, an HVAC system configuration for controlling one or more environmental parameters of the one or more spaces of a building 2 may be developed by the processor 40 of the remote system 36. As an alternative to or in addition to using the remote system 36 to create a model of one or more spaces of a building 2 to be controlled with a developed HVAC system configuration, a building automation controller 18 or other electronic device with appropriate software or applications executable thereon may be configured to develop a model for one or more spaces of a building 2 and one or more HVAC system configurations for those spaces. The user interface 46 may be configured to display the developed model for the one or more spaces of the building 2 and/or the one or more HVAC system configurations.
A model of a space and an HVAC system configuration for that space may be developed by the remote system 36 or other system based on building information that at least partially defines an exterior and/or inner structure of at least part of the building including a space to be conditioned and/or controlled, at least in part, by the developed HVAC system configuration, which may be received via a user interface (e.g., the user interface 46) and a communications port or block (e.g., the communications port or block 42). For example, a user may upload or otherwise provide building information (e.g., selection of one of two or more building type options presented via the user interface, photographs of the interior and/or exterior of the building, a 2-dimensional floorplan or layout of at least part of the building, a 3-dimensional model or layout of at least part of the building, building dimensions, current HVAC system confirmation information for the HVAC system of the building (e.g., including, but not limited to, current locations of one or more register vents within the building), non-HVAC device configurations, etc.) to the remote system 36 through the user interface 46 and/or the remote system 36 may obtain the building information from the user's accounts (e.g., social media or photo sharing/storing databases, etc.) and/or publicly available sources. Additionally, or alternatively, controllers of an existing HVAC control system of the building may automatically detect existing sensors, vent dampers, and/or HVAC or non-HVAC devices of the building and use this information in developing a model of the space and HVAC system. Once the building information is received, a processing module (e.g., processor 40) operatively coupled to the user interface 46 may be configured to create a model of the one or more spaces to be conditioned or controlled by a suggested or developed HVAC system configuration, where the model is developed, at least in part, from the received building information.
Additionally, or alternatively, to developing the model based on building information received via the user interface 46, the processor may be configured to develop the model of the one or more spaces to be controlled and/or conditioned by the developed HVAC system based, at least in part, on information obtained by the processor 40 of the remote system 36. In some cases, a user may enter instructions at the user interface 46 for the remote system 36 to obtain publicly accessible information and/or information stored in the remote system 36 that relates to the building 2 in which the space to be controlled and/or conditioned is located (e.g., building type information, building dimension, or other information). In some instances, the processor 40 of the remote system 36 may obtain the information from a publicly available database, such as an online mapping database, online real estate databases, online tax records, online municipality records, and the like.
In some cases, the remote system 36 may be configured to communicate with the building automation controller 18, if the building 2 includes one, to determine what, if any, HVAC component 6 or other local devices 56 are located in the building 2. If the remote system 36 detects the building includes one or more HVAC components 6, the processor 40 of the remote system 36 may develop an HVAC configuration for the one or more spaces of the building 2 that may incorporate one or more of the detected HVAC components 6 and/or takes into account one or more of the detected local devices 56. One example of taking a detection of a local device 56 into account, is to develop an HVAC system configuration that provides a register vent 26 in a room with a stove, but does not place the register vent behind the stove, where the local device 56 is the stove.
The HVAC system configuration developed by the remote system 36 may be displayed on the user interface and may include a two-dimensional and/or three-dimensional model of the building 2 and/or the spaces of the building 2 to be conditioned and/or controlled, an HVAC system layout, and suggested HVAC system products for implementing a suggested HVAC system configuration. Additionally, or alternatively, the developed HVAC system configuration may include one or more devices having environmental parameter sensors (e.g., local sensors 34 or other sensors) and one or more register vents 26 (e.g., register vents with vent dampers), among other HVAC components 6, where the developed HVAC system configuration may include suggestions to replace specific HVAC system elements (e.g., a suggestion to replace a manually operated vent damper with an electronically controllable register vent). The HVAC system layout developed by the processor 40 may include suggested zone configurations and/or positions of register vents 26 for the one or more spaces to be controlled and/or conditioned. The user interface may be configured to accept selection of a suggested HVAC system configuration and or purchases of suggested HVAC system products of implementing a suggested HVAC system configuration.
The HVAC system configuration for the building 2 developed by the remote system 36 may include one or more HVAC system configuration options. In some cases, the remote system 36 may provide an HVAC system configuration utilizing HVAC components 6 existing in a modeled space of the building 2 and/or a basic HVAC system configuration. In addition, or as an alternative, the remote system 36 may provide one or more advanced level HVAC system configurations that may increase in cost and/or complexity to implement. In some examples, the advanced level HVAC system configurations may include cost estimates and/or time estimates to implement the proposed advanced level HVAC system configuration in the modeled space, along with estimated benefits of the advanced level HVAC system configurations including, but not limited to, energy conservation, increased comfort, and/or potential utility cost savings. In some instances, the HVAC system configuration for the building 2 that is developed by the remote system 36 may include an ability to order one or more HVAC components 6 of the developed HVAC system via the user interface 46.
In operation, a method of developing an HVAC system configuration for an HVAC system of a building may include accepting building information via a user interface of a computing device, where the accepted information at least partially defines or provides access to information defining an inner structure of at least part of the building. Such information may include current HVAC system configuration information for the HVAC system of the building. In one instance, the current HVAC system configuration information may include, among other information, a current location of one or more register vents within the building. Based, at least in part, on the accepted building information, a processor may determine one or more suggested HVAC system configuration for the building and the suggested one or more HVAC system configurations may be displayed via the user interface. In some cases, a suggested HVAC system configuration may be accepted or rejected and products for implementing an accepted suggested HVAC system configuration may be purchased via the user interface.
Although examples of five levels of HVAC system configuration components are described above, other components may be included or excluded at any of the levels of HVAC system configurations in view of a modeled space to be comfort level conditioned and/or in view of other considerations. For example, if a space is already conditioned based on components of a LEVEL 3 configuration described above, a level 3 configuration may be a baseline configuration and one or more levels (e.g., 1, 2, 3, 4, 5, 10, 20, and so on) of HVAC system configuration components may be provided to a user that may be used to incrementally decrease energy consumption. Illustratively, if a space is already conditioned with an HVAC system configuration that is substantially completely automated, a suggested next level of HVAC system configuration componentry may include suggesting a user utilize renewable energy to reduce energy consumption by the HVAC system configuration through incorporating one or more of solar panels, geothermal heating/cooling, etc. into the HVAC system configuration of the comfort level conditioned space. In some cases, a plurality of HVAC system configuration options are provided, sorted by the expected cost/benefit for each option.
Having thus described several illustrative embodiments of the present disclosure, those of skill in the art will readily appreciate that yet other embodiments may be made and used within the scope of the claims hereto attached. Numerous advantages of the disclosure covered by this document have been set forth in the foregoing description. It will be understood, however, that this disclosure is, in many respect, only illustrative. Changes may be made in details, particularly in matters of shape, size, and arrangement of parts without exceeding the scope of the disclosure. The disclosure's scope is, of course, defined in the language in which the appended claims are expressed.
This application claims the benefit of U.S. Provisional Application Ser. No. 62/015,168, filed Jun. 20, 2014, entitled “HVAC Zoning Devices, Systems, and Methods”, which is incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
1949101 | Greenewalt | Feb 1934 | A |
1950101 | Dixon | Mar 1934 | A |
1951101 | Miller | Mar 1934 | A |
5024265 | Buchholz et al. | Jun 1991 | A |
5303767 | Riley | Apr 1994 | A |
5305953 | Rayburn et al. | Apr 1994 | A |
5318099 | Zivalich et al. | Jun 1994 | A |
5337955 | Burd | Aug 1994 | A |
5344068 | Haessig et al. | Sep 1994 | A |
5348078 | Dushane et al. | Sep 1994 | A |
5394324 | Clearwater et al. | Feb 1995 | A |
5415346 | Bishop | May 1995 | A |
5447037 | Bishop et al. | Sep 1995 | A |
5449112 | Heitman et al. | Sep 1995 | A |
5449319 | Dushane et al. | Sep 1995 | A |
5495887 | Kathnelson et al. | Mar 1996 | A |
5520328 | Bujak, Jr. | May 1996 | A |
5651264 | Lo et al. | Jul 1997 | A |
5704545 | Sweitzer, Jr. | Jan 1998 | A |
5751572 | Maciulewicz et al. | May 1998 | A |
5768121 | Federspiel et al. | Jun 1998 | A |
5810245 | Heitman et al. | Sep 1998 | A |
5829674 | Vanostrand et al. | Nov 1998 | A |
5833134 | Ho et al. | Nov 1998 | A |
5839654 | Weber et al. | Nov 1998 | A |
5860473 | Belden | Jan 1999 | A |
5882254 | Jacob et al. | Mar 1999 | A |
5927398 | Maciulewicz et al. | Jul 1999 | A |
5944098 | Jackson et al. | Aug 1999 | A |
5962989 | Baker | Oct 1999 | A |
5983890 | Martin et al. | Nov 1999 | A |
6021252 | Faris et al. | Feb 2000 | A |
6079626 | Hartman et al. | Jun 2000 | A |
6102792 | Nystrom | Aug 2000 | A |
6213404 | Dushane et al. | Apr 2001 | B1 |
6216956 | Ehlers et al. | Apr 2001 | B1 |
6219590 | Bernaden, III et al. | Apr 2001 | B1 |
6237854 | Avni | May 2001 | B1 |
6295823 | Odom et al. | Oct 2001 | B1 |
6296193 | West et al. | Oct 2001 | B1 |
6349883 | Simmons et al. | Feb 2002 | B1 |
6364211 | Saleh | Apr 2002 | B1 |
6574581 | Bohrer et al. | Jun 2003 | B1 |
6575233 | Krumnow | Jun 2003 | B1 |
6659359 | Kwak | Dec 2003 | B2 |
6676508 | Graham | Jan 2004 | B1 |
6688384 | Eoga | Feb 2004 | B2 |
6692349 | Brinkerhoff et al. | Feb 2004 | B1 |
6741915 | Poth | May 2004 | B2 |
6879881 | Attridge, Jr. | Apr 2005 | B1 |
6983889 | Alles | Jan 2006 | B2 |
6986469 | Gauthier et al. | Jan 2006 | B2 |
6997390 | Alles | Feb 2006 | B2 |
7003378 | Poth | Feb 2006 | B2 |
7055759 | Wacker et al. | Jun 2006 | B2 |
7063140 | Woo | Jun 2006 | B1 |
7130720 | Fisher | Oct 2006 | B2 |
7147168 | Bagwell et al. | Dec 2006 | B1 |
7156316 | Kates | Jan 2007 | B2 |
7163156 | Kates | Jan 2007 | B2 |
7168627 | Kates | Jan 2007 | B2 |
7222494 | Peterson et al. | May 2007 | B2 |
7222800 | Wruck | May 2007 | B2 |
7261241 | Eoga | Aug 2007 | B2 |
7392661 | Alles | Jul 2008 | B2 |
7455236 | Kates | Nov 2008 | B2 |
7455237 | Kates | Nov 2008 | B2 |
7548833 | Ahmed | Jun 2009 | B2 |
7551983 | Attridge, Jr. | Jun 2009 | B2 |
7601054 | Bagwell et al. | Oct 2009 | B2 |
7606635 | Fisher | Oct 2009 | B2 |
7693591 | Hoglund et al. | Apr 2010 | B2 |
7726582 | Federspiel | Jun 2010 | B2 |
7788936 | Peterson et al. | Sep 2010 | B2 |
7809472 | Silva et al. | Oct 2010 | B1 |
7832465 | Zou et al. | Nov 2010 | B2 |
7880421 | Karwath | Feb 2011 | B2 |
7904209 | Podgorny et al. | Mar 2011 | B2 |
7957839 | Takach et al. | Jun 2011 | B2 |
7983796 | Kassel | Jul 2011 | B2 |
8010237 | Cheung et al. | Aug 2011 | B2 |
8014902 | Kates | Sep 2011 | B2 |
8020777 | Kates | Sep 2011 | B2 |
8024073 | Imes et al. | Sep 2011 | B2 |
8033479 | Kates | Oct 2011 | B2 |
8038075 | Walsh | Oct 2011 | B1 |
8078325 | Poth | Dec 2011 | B2 |
8086352 | Elliott | Dec 2011 | B1 |
8090477 | Steinberg | Jan 2012 | B1 |
8108076 | Imes et al. | Jan 2012 | B2 |
8112181 | Remsburg | Feb 2012 | B2 |
8116913 | Mirpourian et al. | Feb 2012 | B2 |
8143828 | Becerra et al. | Mar 2012 | B2 |
8147302 | Desrochers et al. | Apr 2012 | B2 |
8185244 | Wolfson | May 2012 | B2 |
8190301 | Voysey | May 2012 | B2 |
8209059 | Stockton | Jun 2012 | B2 |
8219252 | Nanami | Jul 2012 | B2 |
8224490 | Knyazev | Jul 2012 | B2 |
8224491 | Koster et al. | Jul 2012 | B2 |
8229596 | Mejias | Jul 2012 | B2 |
8369995 | Nanami | Feb 2013 | B2 |
8387892 | Koster et al. | Mar 2013 | B2 |
8397527 | Miller | Mar 2013 | B2 |
8417386 | Douglas et al. | Apr 2013 | B2 |
8418128 | Pouchak et al. | Apr 2013 | B2 |
8495888 | Seem | Jul 2013 | B2 |
8515584 | Miller et al. | Aug 2013 | B2 |
8543244 | Keeling et al. | Sep 2013 | B2 |
8550370 | Barrett et al. | Oct 2013 | B2 |
8555662 | Peterson et al. | Oct 2013 | B2 |
8579205 | Augusto et al. | Nov 2013 | B2 |
8651391 | Patch | Feb 2014 | B2 |
8660708 | Narayanamurthy et al. | Feb 2014 | B2 |
8661165 | Grohman et al. | Feb 2014 | B2 |
8695888 | Kates | Apr 2014 | B2 |
8702482 | Helt et al. | Apr 2014 | B2 |
8963726 | Kates | Feb 2015 | B2 |
8963727 | Kates | Feb 2015 | B2 |
8963728 | Kates | Feb 2015 | B2 |
8981950 | Kates | Mar 2015 | B1 |
9007225 | Kates | Apr 2015 | B2 |
9019110 | Kates | Apr 2015 | B2 |
9182140 | Kates | Nov 2015 | B2 |
9183733 | Kates | Nov 2015 | B2 |
9194599 | Kates | Nov 2015 | B2 |
9194600 | Kates | Nov 2015 | B2 |
9222692 | Kates | Dec 2015 | B2 |
20010048030 | Sharood et al. | Dec 2001 | A1 |
20020123896 | Diez et al. | Sep 2002 | A1 |
20030014161 | Orthlieb et al. | Jan 2003 | A1 |
20030200050 | Sharma | Oct 2003 | A1 |
20040118933 | Readio et al. | Jun 2004 | A1 |
20040166797 | Thrasher et al. | Aug 2004 | A1 |
20050090915 | Geiwitz | Apr 2005 | A1 |
20050127196 | Gottlieb | Jun 2005 | A1 |
20050155365 | Shah et al. | Jul 2005 | A1 |
20050156049 | Van Ostrand et al. | Jul 2005 | A1 |
20050156050 | Shah et al. | Jul 2005 | A1 |
20050159848 | Shah et al. | Jul 2005 | A1 |
20050173548 | Kramer | Aug 2005 | A1 |
20050194456 | Tessier et al. | Sep 2005 | A1 |
20050270151 | Winick | Dec 2005 | A1 |
20050278071 | Durham | Dec 2005 | A1 |
20050279845 | Bagwell et al. | Dec 2005 | A1 |
20060036350 | Bohrer et al. | Feb 2006 | A1 |
20060071087 | Kates | Apr 2006 | A1 |
20060099904 | Belt et al. | May 2006 | A1 |
20060185373 | Butler et al. | Aug 2006 | A1 |
20070012052 | Butler et al. | Jan 2007 | A1 |
20070023533 | Liu | Feb 2007 | A1 |
20070045431 | Chapman et al. | Mar 2007 | A1 |
20070051822 | Wolfson | Mar 2007 | A1 |
20070228183 | Kennedy et al. | Oct 2007 | A1 |
20080011864 | Tessier et al. | Jan 2008 | A1 |
20080033599 | Aminpour et al. | Feb 2008 | A1 |
20080054083 | Evans | Mar 2008 | A1 |
20080099568 | Nicodem | May 2008 | A1 |
20080133033 | Wolff et al. | Jun 2008 | A1 |
20080161976 | Stanimirovic | Jul 2008 | A1 |
20080179053 | Kates | Jul 2008 | A1 |
20080251590 | Arneson | Oct 2008 | A1 |
20090008463 | Holland et al. | Jan 2009 | A1 |
20090065595 | Kates | Mar 2009 | A1 |
20090140064 | Schultz et al. | Jun 2009 | A1 |
20090166442 | Stark | Jul 2009 | A1 |
20090266904 | Cohen | Oct 2009 | A1 |
20090271154 | Coad et al. | Oct 2009 | A1 |
20100012737 | Kates | Jan 2010 | A1 |
20100045470 | Araiza et al. | Feb 2010 | A1 |
20100082162 | Mundy et al. | Apr 2010 | A1 |
20100084482 | Kennedy et al. | Apr 2010 | A1 |
20100106334 | Grohman et al. | Apr 2010 | A1 |
20100168924 | Tessier et al. | Jul 2010 | A1 |
20100204834 | Comerford et al. | Aug 2010 | A1 |
20100307733 | Karamanos et al. | Dec 2010 | A1 |
20110015802 | Imes | Jan 2011 | A1 |
20110031322 | Zou et al. | Feb 2011 | A1 |
20110034120 | Jaiyeola | Feb 2011 | A1 |
20110046798 | Imes et al. | Feb 2011 | A1 |
20110046799 | Imes et al. | Feb 2011 | A1 |
20110054701 | Wang et al. | Mar 2011 | A1 |
20110062246 | Khalafi | Mar 2011 | A1 |
20110112875 | Johnson et al. | May 2011 | A1 |
20110127340 | Aiken | Jun 2011 | A1 |
20110172828 | Schmidt et al. | Jul 2011 | A1 |
20110198404 | Dropmann | Aug 2011 | A1 |
20110202185 | Imes et al. | Aug 2011 | A1 |
20110214060 | Imes et al. | Sep 2011 | A1 |
20110246898 | Imes et al. | Oct 2011 | A1 |
20110257795 | Narayanamurthy et al. | Oct 2011 | A1 |
20110270446 | Scharf et al. | Nov 2011 | A1 |
20110276183 | Liu | Nov 2011 | A1 |
20120041603 | Wilmsen et al. | Feb 2012 | A1 |
20120048952 | Slingsby et al. | Mar 2012 | A1 |
20120072030 | Elliott | Mar 2012 | A1 |
20120072031 | Elliott | Mar 2012 | A1 |
20120072033 | Imes et al. | Mar 2012 | A1 |
20120101637 | Imes et al. | Apr 2012 | A1 |
20120101648 | Federspiel et al. | Apr 2012 | A1 |
20120161682 | Becerra et al. | Jun 2012 | A1 |
20120217315 | Witbeck | Aug 2012 | A1 |
20120221718 | Imes et al. | Aug 2012 | A1 |
20120228393 | Storm et al. | Sep 2012 | A1 |
20120239202 | Voysey | Sep 2012 | A1 |
20120239208 | Federspiel et al. | Sep 2012 | A1 |
20120298763 | Young | Nov 2012 | A1 |
20120310416 | Tepper | Dec 2012 | A1 |
20130057937 | Berman | Mar 2013 | A1 |
20130069541 | Feri | Mar 2013 | A1 |
20130081799 | Loblich et al. | Apr 2013 | A1 |
20130085613 | Bester et al. | Apr 2013 | A1 |
20130138249 | Cho | May 2013 | A1 |
20130138250 | Mowery et al. | May 2013 | A1 |
20130182905 | Myers | Jul 2013 | A1 |
20130245838 | Zywicki et al. | Sep 2013 | A1 |
20130268129 | Fadell et al. | Oct 2013 | A1 |
20130297078 | Kolavennu | Nov 2013 | A1 |
20130310986 | Gust | Nov 2013 | A1 |
20130310987 | Sobek et al. | Nov 2013 | A1 |
20130334326 | Shan | Dec 2013 | A1 |
20130338837 | Hublou et al. | Dec 2013 | A1 |
20130338839 | Rogers et al. | Dec 2013 | A1 |
20140000861 | Barrett et al. | Jan 2014 | A1 |
20140031993 | Matsuoka | Jan 2014 | A1 |
20140034284 | Butler et al. | Feb 2014 | A1 |
20140041846 | Leen et al. | Feb 2014 | A1 |
20140052300 | Matsuoka et al. | Feb 2014 | A1 |
20140067130 | Pillai | Mar 2014 | A1 |
20140101082 | Matsuoka et al. | Apr 2014 | A1 |
20140319232 | Gourlay | Oct 2014 | A1 |
20150369503 | Flaherty et al. | Dec 2015 | A1 |
20150369504 | Flaherty et al. | Dec 2015 | A1 |
20150369507 | Flaherty et al. | Dec 2015 | A1 |
Number | Date | Country |
---|---|---|
667634 | Mar 1996 | AU |
688762 | Mar 1998 | AU |
2005294681 | Apr 2006 | AU |
2009231670 | Oct 2009 | AU |
2008229674 | Apr 2010 | AU |
2010276364 | Aug 2012 | AU |
2010284375 | Oct 2014 | AU |
1326705 | Feb 1994 | CA |
2005497 | May 1994 | CA |
2077199 | Aug 1997 | CA |
2025279 | May 1998 | CA |
2582232 | Apr 2006 | CA |
2599471 | Feb 2009 | CA |
2748724 | Jul 2010 | CA |
2699034 | Aug 2010 | CA |
2698794 | Sep 2010 | CA |
2677047 | Nov 2010 | CA |
2668812 | Dec 2010 | CA |
2768799 | Jan 2011 | CA |
2771280 | Feb 2011 | CA |
2771638 | Feb 2011 | CA |
2818696 | May 2012 | CA |
2769288 | Sep 2012 | CA |
2798477 | Jun 2013 | CA |
2719932 | Oct 2013 | CA |
2698845 | Nov 2013 | CA |
101048624 | Oct 2007 | CN |
101145276 | Mar 2008 | CN |
101194129 | Oct 2010 | CN |
101999252 | Mar 2011 | CN |
202328615 | Jul 2012 | CN |
102882752 | Jan 2013 | CN |
103229116 | Jul 2013 | CN |
10126475 | Mar 2003 | DE |
201200174 | Sep 2013 | DK |
0660051 | Jun 1995 | EP |
0632234 | Mar 1998 | EP |
0721089 | Aug 2000 | EP |
0892330 | Oct 2002 | EP |
0889291 | Apr 2004 | EP |
2014994 | Jan 2009 | EP |
2690372 | Jan 2014 | EP |
2452345 | Mar 2009 | GB |
2477860 | Aug 2011 | GB |
2002245102 | Aug 2002 | JP |
2003287240 | Oct 2003 | JP |
2006300484 | Nov 2006 | JP |
2012078049 | Apr 2012 | JP |
2006041599 | Apr 2006 | WO |
2006099125 | Sep 2006 | WO |
2007027632 | Mar 2007 | WO |
2008016500 | Feb 2008 | WO |
2008030791 | Mar 2008 | WO |
2009073034 | Jun 2009 | WO |
2009124217 | Oct 2009 | WO |
2010078459 | Jul 2010 | WO |
2011011404 | Jan 2011 | WO |
2011022379 | Feb 2011 | WO |
2011062942 | May 2011 | WO |
2011100736 | Aug 2011 | WO |
2011120091 | Oct 2011 | WO |
2012068591 | May 2012 | WO |
2012092622 | Jul 2012 | WO |
2012092625 | Jul 2012 | WO |
2012092627 | Jul 2012 | WO |
2012112415 | Aug 2012 | WO |
WO 2013043863 | Mar 2013 | WO |
2013173433 | Nov 2013 | WO |
2013179080 | Dec 2013 | WO |
2014033189 | Mar 2014 | WO |
2014051632 | Apr 2014 | WO |
Entry |
---|
Arzel Zoning Technology, Inc., “Zonocity: Zoning for Small Duct High Velocity Applications (SDHV),” http://www.arelzoning.com/products/zonocity, 2 pages, printed Jun. 17, 2014. |
Brown, “Multizone Register Controlled Residential Heating: Optimized for Energy Use and Comfort,” Center for the Built Environment, UC Berkeley, 62 pages, 2007. |
Carrier, “A 6-in-1 Device: Intelligent Residential Control Introduced by Carrier,” http://www.transicold.carrier.com/Carrier+Corporate+Sites/Corporate/Side+Bar+ULinks/Global+News/ci.A+6-in-1+Device%3A+Intelligent+Residentiai+Control . . . , 3 pages, May 29, 2014. |
Carrier, Carrier Comfort System (VVTIII), 6 pages, Aug. 1996. |
Carrier, “VVT Comfort System, 33 CS,” 6 pages, Oct. 1997. |
Dounis Et al., “Advanced Control Systems Engineering for Energy and Comfort Management in a Building Environment—A Review,” Renewable and Sustainable Energy Reviews, vol. 13, pp. 1246-1261, 2009. |
Home Climate Control, “Technical FAQ: HVAC: Excess Static Pressure Relief,” http://www.homeclimatecontrol.com/faq/technical-hvac-excess-static-pressure-relief, 5 pages, printed, May 19, 2014. |
Honeywell, “WiFi Color Touchscreen Programmable Thermostat, RTH9590 WiFi With Voice Control, Quick Start Guide,” 20 pages, Feb. 2014. |
http://www.linkedin.com/groups/JCI-new-ASSET-tool-is-4767612.S.198141514, “JCI New ASSET Tool is a Game Changer,” 2 pages, printed Jun. 17, 2014. |
http://www.statscrop.com/www/theactivent.com, “Theactivent.com, The Activent, Web Analysis,” 5 pages, printed May 16, 2014. |
https://developer.apple.com/homekit/, “HomeKit, Apple Developer,” 2 pages, printed Jan. 21, 2016. |
https://web.archive.org/web/20040609142352/http://diy-zoning.sourceforge.net/Advanced/dampers.html, “DIY Zoning: Dampers,” 2 pages, Jun. 9, 2004. |
https://web.archive.org/web/20040613050818/http://www.smarthomeusa.com/Shop/Climate/rcs/RCS-Zone-Controllers/Item/ZC6R-232/, “RCS HVAC 6 Zone Controller (RS-232 Version)—ZC6R-232—SmartHomeUSA.com,” 2 pages, Jun. 13, 2004. |
https://web.archive.org/web/20040624153603/http://diy-zoning.sourceforge.net/Development/contract.html, “DIY Zoning: Design Contract,” 2 pages, Jun. 24, 2004. |
https://web.archive.org/web/20081204093741/http://www.smarthome.com'3096H146/In-Wall-Motorized-Registers/p.aspx, “In-Wall Motorized Registers—Smarthome,” 2 pages, Dec. 4, 2008. |
https://web.archive.org/web/20130724192824/http://diy-zoning.sourceforge.net/Advanced/dampers.html, “DIY Zoning: Dampers,” 4 pages, Jul. 24, 2013. |
https:www.webarchive.org/web/20080602013118/http://www.commercial.carrier.com/commercial/hvac/productdescription/1,3059,CLI1_DIV12 ETI434_PRD189.00 . . . , “Carrier: 33ZCFANTRM VAV Fan Terminal Zone Controller,” 6 pages, Jun. 2008. |
Jackson Systems, “Comfort System VAV Diffuser,” 2 pages, downloaded May 19, 2014. |
Johnson Controls, “Facility Explorer ASSET Application/System Selection & Estimating Tool,” 2 pages, 2012. |
Nova, “Activent Electronic Room Temperature Regulator, User Manual and Installation Guide,” 7 pages, downloaded May 16, 2014. |
Redfern et al., “Design Architecture for Multi-Zone HVAC Control Systems From Existing Single-Zone Systems Using Wireless Sensor Networks,” Proceedings of SPIE, vol. 6414, 2007. |
Residential Control Systems Inc., “RCS Model ZC6R, 6 Zone HVAC Control Unit,” 2 pages, Feb. 2002. |
Siemens, “HIT: Online Version Supports Energy Efficiency Standard,” Press Release, 2 pages, Feb. 20, 2009. |
Telkonet, “EcoWave Remote Thermostat Package,” 2 pages, Jan. 2013. |
The Activent, “Individual Room Zoning Systems,” http://www.theactivent.com/, 2 pages, printed May 16, 2014. |
Trane, “Light Commercial Integrated Comfort System,” 6 pages, 2004. |
Trane, “Light Commercial Integrated Comfort System,” 6 pages, 2001. |
Trane, “VariTrac Central Control Panel, Intallation Manual, VAV-SVNO3A-EN,” 72 pages, Jun. 2002. |
Trane, “VariTrane Products,” VAV-PRC008-EN, 308 pages, Mar. 2003. |
Trane, “VariTrane Products,” VAV-PRC008-EN, 321 pages, May 2006. |
Vadim Tkachenko, “DIY Zoning: Design Contract,” 3 pages, 2000. |
Number | Date | Country | |
---|---|---|---|
20150369503 A1 | Dec 2015 | US |
Number | Date | Country | |
---|---|---|---|
62015168 | Jun 2014 | US |