The disclosure pertains generally to HVAC control, and more particularly, to HVAC control with utility time of day pricing support.
Heating, ventilation, and/or air conditioning (HVAC) systems are often used to control the comfort level within a building or other structure. Many HVAC systems include a controller that activates and deactivates one or more HVAC units or components of the HVAC system to affect and control one or more environmental conditions within the building. These environmental conditions can include, but are not limited to, temperature, humidity, and/or ventilation. In many cases, such an HVAC controller may include, or have access to, one or more sensors, and may use parameters provided by the one or more sensors to control the one or more HVAC components to achieve desired programmed or set environmental conditions.
An HVAC controller may be equipped with a user interface that allows a user to monitor and adjust the environmental conditions at one or more locations within the building. With more modern designs, the interface typically includes a display panel, such as a liquid crystal display panel, inset within a housing that contains a microprocessor as well as other components of the HVAC controller. In some designs, the user interface may permit the user to program the controller to activate on a certain schedule determined by the user. For example, the interface may include a routine that permits the user to change the temperature at one or more times during a particular day and/or group of days. Such a programmable schedule may help reduce energy consumption of the HVAC system by changing the setpoint to an energy saving set back temperature during certain times, such as when the building or space is expected to be unoccupied or when the occupants are expected to be sleeping.
When a programmable schedule is employed, and because it is not physically possible to warm up or cool down the space instantaneously to match the programmable schedule, the HVAC controller may be configured to command the HVAC unit(s) (furnace. air conditioner, etc.) to begin changing space temperature well before a scheduled set point change. For example, if an upcoming setpoint is scheduled to change from 68 degrees to 72 degrees at 6:00 AM, the HVAC controller may activate a furnace or the like at 5:30 AM so that the temperature in the building reaches the desired setpoint of 72 degrees at about the desired setpoint time of 6:00 AM. This is often referred to as “recovery” or “setpoint recovery”.
Energy is supplied to most HVAC systems by one or more utilities, such as an electric utility and/or a gas utility. During peak demand periods, such as during hot summer days, such utilities may vary the rates that they charge for energy. Customers may wish to modify their energy consumption in response to these varying rates in order to reduce their energy bills. What would be desirable is a new HVAC controller and control methods that can help customers modify their energy consumption during peak or anticipated peak demand periods in concert with other HVAC system control objectives.
The disclosure relates generally to Heating, Ventilation, and Air Conditioning (HVAC) control, and more particularly, to HVAC control with utility time of day pricing support. In one illustrative embodiment, an HVAC controller may include a nominal schedule that includes, for example, a number of days and one or more time periods for each of at least some of the days, as well as at least one setpoint associated with each of the one or more time periods. The HVAC controller may also include a utility pricing schedule that corresponds to scheduled price changes of a utility, including one or more enhanced pricing time periods each having corresponding one or more enhanced pricing time period setpoints. The HVAC controller may establishing or modifying an enhanced pricing setpoint recovery schedule based at least in part upon the nominal schedule and the utility pricing schedule, and may control the one or more HVAC units in accordance with the setpoint recovery schedule. In some instances, the HVAC controller may identify recovery opportunities based at least in part upon the nominal schedule and the utility pricing schedule.
The above summary is not intended to describe each and every disclosed illustrative example or every implementation of the disclosure. The Description that follows more particularly exemplifies various illustrative embodiments.
The following description should be read with reference to the drawings. The drawings, which are not necessarily to scale, depict selected illustrative embodiments and are not intended to limit the scope of the disclosure. 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:
The following description should be read with reference to the drawings, in which like elements in different drawings are numbered in like fashion. The drawings, which are not necessarily to scale, depict selected illustrative embodiments and are not intended to limit the scope of the invention. Although examples of construction, dimensions, and materials are illustrated for the various elements, those skilled in the art will recognize that many of the examples provided have suitable alternatives that may be utilized.
The illustrative HVAC system 10 of
HVAC controller 12 may include any suitable components related to effecting control of the HVAC system 10. For example, HVAC controller 12 may include a user interface 32. The user interface 32 may include one or more displays and/or buttons that a user may interact with. In some instances, a touchscreen display may be provided. In the illustrative embodiment, HVAC controller 12 includes a processor 34, which may be a microprocessor, and a memory 36 which may be used to store any appropriate information such as HVAC control routines or code, historical performance data, HVAC system parameters, one or more programmable schedules for changing HVAC system parameters over time, a utility pricing schedule that includes one or more enhanced pricing time periods, and so on. HVAC system parameters may include setpoints for heating, cooling, humidity, etc., modes for ventilation equipment, fan settings, and the like.
As shown, HVAC controller 12 may include one or more sensors, such as an internal sensor 38 located within a housing 42 of the HVAC controller 12, and/or external sensors 40, which may be located external to the controller housing 42. The external sensors 40 may be 1within the building and/or outside the building, as desired. HVAC controller 12 may include one or more outputs 44 configured to issue operation commands to HVAC equipment 14 including units 16, 18, 20. It is contemplated that HVAC controller 10 may be configured to execute any method of the present disclosure.
One or more utilities 22 may provide energy to the HVAC system 10, including HVAC equipment 14. The utility or utilities 22 may supply a source of energy such as electricity, natural gas, hot water, steam, and/or any other suitable sources of energy. In order to help reduce peak loads, utilities are increasingly employing variable pricing schemes. Any number of pricing (rate) schemes may be employed. For example, energy rates may be raised during an enhanced pricing time period during the day compared to at night, due to higher anticipated demand for industrial and commercial use and/or greater demand for cooling during daylight hours. Any appropriate number of rate changes may be made during a day, such as a mid-tier or mid-peak rate becoming effective at the start of the work day, then a higher-tier or higher-peak rate becoming effective for the greatest temperature period later in the day when air conditioning loads are usually highest, then returning to a non-peak rate after the work day ends. In some arrangements, enhanced pricing time periods may recur on a daily basis, or they may recur daily within a group of days such as weekdays, with different rate schedules being effective on other groups of days such as weekends. In some cases, enhanced pricing time periods of a utility may recur on a weekly basis.
Schedules for recurrences of enhanced pricing time periods may vary over longer time intervals, such as between seasons. For example, a summer schedule for weekly recurrences of enhanced pricing time periods may be in force during warmer months of the year, and a different winter schedule may be in effect for colder months.
In some instances, utilities may plan and communicate schedules for rate/price changes well in advance of the dates for such changes. For example, summer and winter enhanced pricing rate schedules may be determined long before the in-force dates for the schedules. In other situations, enhanced pricing time periods may be declared and/or scheduled on shorter time scales, such as in response to a heat wave or a cold snap (periods of relatively extreme environmental temperatures), or even due to an unforeseen cause such as failure of a power generation facility or an international crisis that constrains energy supplies. In some situations, a utility may enact an enhanced pricing time period of Critical Peak Pricing (CPP) with short notice (for example announcing a CPP event one day in advance or less), for example in response to actual or anticipated very high demand for energy.
In response to higher rates during such enhanced pricing time periods, customers may desire to curtail energy consumption (and hence, demand on the utility) relative to consumption during periods of normal or nominal pricing. This may be accomplished by, for example, temporarily setting less comfortable setpoints. Generally speaking, a demand-side response to enhanced pricing may be achieved in any number of ways. A homeowner with a simple non-programmable thermostat may manually adjust the thermostat setpoint in response to rate changes. This approach may be relatively labor intensive and require substantial diligence on the part of the homeowner. In a more sophisticated approach, a local HVAC controller such as a thermostat may be configured to receive automated signals from a utility (such as via a wired and/or radio-frequency communication link) that communicate enhanced pricing information, and the HVAC controller may be configured to adjust HVAC system operation in a predetermined response to price changes without the need for immediate user action and/or awareness. Aspects of such a system are disclosed in, for example, U.S. Pat. No. 6,574,581, “PROFILE BASED METHOD FOR DERIVING A TEMPERATURE SETPOINT USING A ‘DELTA’ BASED ON CROSS-INDEXING A RECEIVED PRICE-POINT LEVEL SIGNAL,” Bohrer, et al., which is hereby incorporated by reference in its entirety.
Other approaches to responding to variable pricing schemes having scheduled enhanced pricing time periods provide methods and devices that assist utility customers in modifying HVAC system operation and energy consumption in view of rates changes of utilities during enhanced pricing time periods, without necessarily requiring an automated communication link between a utility and the HVAC system controller. In some instances, manual entry of pricing schedule information into an HVAC controller may be performed by a utility customer such as a homeowner. Aspects of such systems are disclosed in, for example, U.S. patent application Ser. No. 12/692,334, “HVAC CONTROL WITH UTILITY TIME OF DAY PRICING SUPPORT,” Amundson, et al., filed Jan. 22, 2010, which is hereby incorporated by reference in its entirety.
In some illustrative embodiments of the present disclosure, HVAC controller 12 may store in memory 36 a utility pricing schedule that includes one or more enhanced pricing time periods including at least one scheduled price change of a utility. The utility pricing schedule may be entered into the controller's memory 36 by any suitable method. The utility pricing schedule may be entered, for example, by manual input via the user interface 32, but this is not required. Other possible methods for entering a utility pricing schedule into memory 36 include transfer via a wired or wireless communications protocol or via a flash memory device, for example.
Methods of the present disclosure may be described in relation to an HVAC system operating during a heating season, but it is contemplated that analogous considerations may apply to HVAC system operation during other seasons, such as cooling seasons, as well.
Each enhanced pricing time period may have at least one associated enhanced pricing time period setpoint, and may have multiple setpoints, for example to correspond to heating and cooling seasons or modes of operation. Enhanced pricing time period setpoints may be associated with enhanced pricing time period in any suitable way. As discussed herein, in some illustrative embodiments an enhanced pricing time period may be associated with a utility price level, which in turn may be associated with at least one utility price level setpoint, and hence, the enhanced pricing time period may be transitively associated with at least one utility price level setpoint. In some illustrative embodiments, enhanced pricing time period setpoints may be associated with enhanced pricing time periods directly, for example, without necessarily associating either with a utility price level. Such associations may be made by user input through a user interface of an HVAC controller, or by any other suitable method. In some illustrative embodiments, enhanced pricing time period setpoints may be generated or otherwise determined as offsets from setpoints of another schedule such as a nominal programmable schedule.
Enhanced pricing time period setpoints may, in some situations, represent setpoints that an HVAC controller will attempt to maintain, but not necessarily in all situations. Enhanced pricing time period setpoints may sometimes be regarded as enhanced pricing time period setpoint limits in that they may demark a limit to a range of setpoints to which an HVAC may control. For example, during an enhanced pricing time period, a controller may be configured to compare a nominal setpoint (i.e., a setpoint to which it would attempt to control without regard to energy saving considerations) with an applicable enhanced pricing time period setpoint. During an enhanced pricing time period in the heating season, a nominal setpoint may be 70° F. while the enhanced pricing time period setpoint may be 68° F. In this case, the HVAC controller may select the utility price level setpoint of 68° F. as being more economical, and control to that setpoint. At a different time, during an enhanced pricing time period when the enhanced pricing time period setpoint is still 68° F., but the nominal setpoint is 64° F., the HVAC controller may select the nominal setpoint of 64° F. as being more economical.
Referring back to
In some illustrative embodiments, the HVAC controller 12 may maintain in its memory a nominal schedule that may be used to control the HVAC system during non-enhanced pricing periods. The nominal schedule may be similar to that shown and described below with respect to
The nominal schedule may represent the normal programmable schedule of a programmable thermostat. The nominal schedule may, for example, be a 7 day programmable schedule (where each of the seven days of the week can have a separate schedule), a 5-2 programmable schedule (where the five week days have a common schedule, and the two weekend days have a common schedule), or any other schedule. In some cases, the nominal schedule may have a number of days and one or more time periods for each of at least some of the days. In some instances, the nominal schedule may include a “sleep,” a “wake,” a “leave,” and a “return” time period for each of the days of a week. The nominal schedule may have at least one setpoint associated with each of the one or more time periods. The nominal schedule may be maintained in the local HVAC controller's memory, and typically may be modified by an end user. The nominal schedule may be programmed using an interface such as one of those disclosed in U.S. Pat. No. 7,114,554, “CONTROLLER INTERFACE WITH MULTIPLE DAY PROGRAMMING,” Bergman et al., which is hereby incorporated by reference in its entirety.
The lower nominal setpoints of 62° F. in effect during the “sleep” and “leave” time periods may be considered to be energy efficient setpoints, as they generally may be maintained with less energy usage than higher setpoints during a heating season. Conversely, the nominal setpoints of 72° F. in effect during the “wake” and “return” time periods may be considered to be less energy efficient setpoints, or comfort setpoints.
As noted elsewhere, it is not physically possible to instantaneously transition to a comfort setpoint temperature from a prior more economical temperature, and hence, an HVAC controller may actuate one or more HVAC units such as a furnace or air conditioner in advance of a target time (e.g., in advance of the 6:30 am “wake” period in the nominal schedule of
We now consider setpoint recovery in the context of utility pricing schedules and enhanced pricing time periods. If an enhanced pricing time period is in effect when recovery is initiated at 416, then setpoint recovery will entail greater consumption of energy during the enhanced pricing time period, at least compared to an alternative of not initiating recovery at 416 and continuing to control the HVAC system in accordance with the energy efficient setpoint. This alternative may be practiced, for example, by controlling an HVAC system without regard to setpoint recovery, and only setting the operating setpoint of an HVAC controller according to a nominal programmable schedule such as that illustrated in
Reduced energy consumption during enhanced pricing time periods also may be achieved with HVAC control methods that move the inside air temperature to the less energy efficient setpoint but with less delay than in the method illustrated in
In a variation of the method detailed in relation to
In some illustrative embodiments of the present disclosure, methods of controlling an HVAC system may include establishing an enhanced pricing recovery schedule based at least in part upon a nominal target setpoint and a nominal target time of a programmable schedule and a utility pricing schedule, and controlling one or more HVAC units of the HVAC system in accordance with the enhanced pricing recovery schedule. Establishing an enhanced pricing recovery schedule may include setting recovery targets, determining recovery ramps, determining recovery start times, etc., as described in the discussions of the methods of
In some illustrative embodiments of the present disclosure, methods of controlling an HVAC system may include enabling recovery during enhanced pricing time periods whose corresponding utility price levels do not exceed utility price levels of subsequent enhanced pricing time periods preceding the nominal target time, and/or disabling recovery during enhanced pricing time periods whose corresponding utility price levels exceed utility price levels of subsequent enhanced pricing time periods preceding the nominal target time.
In some illustrative embodiments of the present disclosure, methods of controlling an HVAC system may include accepting a selection of preference for economy or comfort, and establishing an enhanced pricing recovery schedule based at least in part upon the preference selection. For example, a selection of economy may result in establishing an enhanced pricing recovery schedule in accordance with the method discussed in connection with
In some illustrative embodiments of the present disclosure, methods of controlling an HVAC system may include identifying recovery opportunities based at least in part upon the nominal schedule, with each recovery opportunity having an associated nominal target setpoint corresponding to a nominal target time. Recovery opportunities may correspond to programmed returns to comfort setpoints from more energy efficient setpoints, for example, when transitioning from a “sleep” period to a “wake” period, and/or when transitioning from a “leave” period to a “return” period. For identified recovery opportunities, methods of the present disclosure may be used for determining recovery start times, establishing and/or modifying enhanced pricing recovery schedules, and otherwise operating the HVAC system to recover setpoints while possibly modifying recovery actions in consideration of enhanced pricing time periods of utility pricing schedules.
The disclosure should not be considered limited to the particular examples described above, but rather should be understood to cover all aspects of the invention as set out in the attached claims. Various modifications, equivalent processes, as well as numerous structures to which the invention can be applicable will be readily apparent to those of skill in the art upon review of the instant specification.
Number | Name | Date | Kind |
---|---|---|---|
4216384 | Hurley | Aug 1980 | A |
4228511 | Simcoe et al. | Oct 1980 | A |
4337401 | Olson | Jun 1982 | A |
4341345 | Hammer et al. | Jul 1982 | A |
4345162 | Hammer et al. | Aug 1982 | A |
4382544 | Stewart | May 1983 | A |
4401262 | Adams et al. | Aug 1983 | A |
4509585 | Carney et al. | Apr 1985 | A |
4583182 | Breddan | Apr 1986 | A |
4657179 | Aggers et al. | Apr 1987 | A |
4702413 | Beckey et al. | Oct 1987 | A |
4706882 | Barnard | Nov 1987 | A |
4764766 | Aoyama et al. | Aug 1988 | A |
4828016 | Brown et al. | May 1989 | A |
4839636 | Zeiss | Jun 1989 | A |
4911358 | Mehta | Mar 1990 | A |
4991770 | Bird et al. | Feb 1991 | A |
5025984 | Bird et al. | Jun 1991 | A |
5218399 | Izumi et al. | Jun 1993 | A |
5219119 | Kasper et al. | Jun 1993 | A |
5244146 | Jefferson et al. | Sep 1993 | A |
5270952 | Adams et al. | Dec 1993 | A |
5289362 | Liebl et al. | Feb 1994 | A |
5314004 | Strand et al. | May 1994 | A |
5395042 | Riley et al. | Mar 1995 | A |
5454511 | Van Ostrand et al. | Oct 1995 | A |
5459374 | Thoeny et al. | Oct 1995 | A |
5462225 | Massara et al. | Oct 1995 | A |
5482209 | Cochran et al. | Jan 1996 | A |
5539633 | Hildebrand et al. | Jul 1996 | A |
5555927 | Shah | Sep 1996 | A |
5572438 | Ehlers et al. | Nov 1996 | A |
5598349 | Elliason et al. | Jan 1997 | A |
5622310 | Meyer | Apr 1997 | A |
5644173 | Elliason et al. | Jul 1997 | A |
5729474 | Hildebrand et al. | Mar 1998 | A |
5816491 | Berkeley et al. | Oct 1998 | A |
5822997 | Atterbury | Oct 1998 | A |
5833134 | Ho et al. | Nov 1998 | A |
5884248 | Hall | Mar 1999 | A |
5903327 | Hijii | May 1999 | A |
5924486 | Ehlers et al. | Jul 1999 | A |
5926776 | Glorioso et al. | Jul 1999 | A |
6104399 | Volkel | Aug 2000 | A |
6122603 | Budike, Jr. | Sep 2000 | A |
6152375 | Robison | Nov 2000 | A |
6167389 | Davis et al. | Dec 2000 | A |
6216956 | Ehlers et al. | Apr 2001 | B1 |
6236443 | Carlsen | May 2001 | B1 |
6254009 | Proffitt et al. | Jul 2001 | B1 |
6260765 | Natale et al. | Jul 2001 | B1 |
6264110 | Proffitt et al. | Jul 2001 | B1 |
6305611 | Proffitt et al. | Oct 2001 | B1 |
6311105 | Budike, Jr. | Oct 2001 | B1 |
6437692 | Petite et al. | Aug 2002 | B1 |
6478233 | Shah | Nov 2002 | B1 |
6480803 | Pierret et al. | Nov 2002 | B1 |
6496168 | Tomida | Dec 2002 | B1 |
6502758 | Cottrell | Jan 2003 | B2 |
6519509 | Nierlich et al. | Feb 2003 | B1 |
6549870 | Proffitt et al. | Apr 2003 | B2 |
6574581 | Bohrer et al. | Jun 2003 | B1 |
6619555 | Rosen | Sep 2003 | B2 |
6622925 | Carner et al. | Sep 2003 | B2 |
6634566 | Archacki, Jr. et al. | Oct 2003 | B2 |
6643567 | Kolk et al. | Nov 2003 | B2 |
6671586 | Davis et al. | Dec 2003 | B2 |
6681154 | Nierlich et al. | Jan 2004 | B2 |
6741915 | Poth | May 2004 | B2 |
6785630 | Kolk et al. | Aug 2004 | B2 |
6786421 | Rosen | Sep 2004 | B2 |
6789739 | Rosen | Sep 2004 | B2 |
6862498 | Davis et al. | Mar 2005 | B2 |
6868293 | Schurr et al. | Mar 2005 | B1 |
6879806 | Shorty | Apr 2005 | B2 |
6904385 | Budike, Jr. | Jun 2005 | B1 |
6931445 | Davis | Aug 2005 | B2 |
6975958 | Bohrer et al. | Dec 2005 | B2 |
6980080 | Christensen et al. | Dec 2005 | B2 |
6988671 | DeLuca | Jan 2006 | B2 |
6993417 | Osann, Jr. | Jan 2006 | B2 |
7000849 | Ashworth et al. | Feb 2006 | B2 |
7010363 | Donnelly et al. | Mar 2006 | B2 |
7039532 | Hunter | May 2006 | B2 |
7049976 | Hunt et al. | May 2006 | B2 |
7053767 | Petite et al. | May 2006 | B2 |
7103511 | Petite | Sep 2006 | B2 |
7130719 | Ehlers et al. | Oct 2006 | B2 |
7133414 | Archacki, Jr. | Nov 2006 | B2 |
7172132 | Proffitt et al. | Feb 2007 | B2 |
7184861 | Petite | Feb 2007 | B2 |
7225171 | Kikuchi et al. | May 2007 | B2 |
7230544 | Van Heteren | Jun 2007 | B2 |
7279659 | Gagas et al. | Oct 2007 | B2 |
7346467 | Bohrer et al. | Mar 2008 | B2 |
7364093 | Garozzo | Apr 2008 | B2 |
7420293 | Donnelly et al. | Sep 2008 | B2 |
7434742 | Mueller et al. | Oct 2008 | B2 |
7516106 | Ehlers et al. | Apr 2009 | B2 |
7949615 | Ehlers et al. | May 2011 | B2 |
20010010032 | Ehlers et al. | Jul 2001 | A1 |
20040034484 | Solomita, Jr. et al. | Feb 2004 | A1 |
20040260411 | Cannon | Dec 2004 | A1 |
20050040943 | Winick | Feb 2005 | A1 |
20050119766 | Amundson et al. | Jun 2005 | A1 |
20050194456 | Tessier et al. | Sep 2005 | A1 |
20050195757 | Kidder et al. | Sep 2005 | A1 |
20060049694 | Kates | Mar 2006 | A1 |
20070165835 | Berkman | Jul 2007 | A1 |
20070239317 | Bogolea et al. | Oct 2007 | A1 |
20080011864 | Tessier et al. | Jan 2008 | A1 |
20080122585 | Castaldo et al. | May 2008 | A1 |
20080177678 | Di Martini et al. | Jul 2008 | A1 |
20080262979 | Metcalfe | Oct 2008 | A1 |
20080272934 | Wang et al. | Nov 2008 | A1 |
20090001180 | Siddaramanna et al. | Jan 2009 | A1 |
20090001181 | Siddaramanna et al. | Jan 2009 | A1 |
20090077397 | Shnekendorf et al. | Mar 2009 | A1 |
20090187499 | Mulder et al. | Jul 2009 | A1 |
20090198384 | Ahn | Aug 2009 | A1 |
20090295594 | Yoon | Dec 2009 | A1 |
20090302994 | Rhee et al. | Dec 2009 | A1 |
20090302996 | Rhee et al. | Dec 2009 | A1 |
20090305644 | Rhee et al. | Dec 2009 | A1 |
20100070101 | Benes et al. | Mar 2010 | A1 |
20100094737 | Lambird et al. | Apr 2010 | A1 |
20100243231 | Rosen | Sep 2010 | A1 |
Number | Date | Country |
---|---|---|
0735516 | Jun 2004 | EP |
2333494 | Jan 1998 | GB |
8501851 | Apr 1985 | WO |
9621264 | Jul 1996 | WO |
9808179 | Feb 1998 | WO |
0152478 | Jul 2001 | WO |
03032103 | Apr 2003 | WO |
03084022 | Oct 2003 | WO |
2006096854 | Sep 2006 | WO |
Number | Date | Country | |
---|---|---|---|
20110238224 A1 | Sep 2011 | US |