US20130158720A1 - Hvac controller with performance log - Google Patents

Abstract

An HVAC controller is configured to log and record performance related data related to a performance of an HVAC system over a period of time in one or more performance logs stored in a memory of the HVAC controller. In some cases, the HVAC controller may be configured to retrieve at least some of the performance related data from the performance log that corresponds to a selected period of time that may be selected by a user, and display the retrieved performance related data on a display of the HVAC controller.

Description

TECHNICAL FIELD
• This disclosure relates generally to HVAC systems, and more particularly, to HVAC controllers that may be used for controlling HVAC systems.
BACKGROUND
• 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. Over time, the HVAC system may begin to operate less efficiently. Diagnosing the cause of the loss in system efficiency may be difficult. Diagnostics may be employed to assist in monitoring the performance of an HVAC system over time.
SUMMARY
• This disclosure relates generally to HVAC systems, and more particularly, to HVAC controllers that may be used for controlling HVAC systems.
• In some illustrative embodiments, an HVAC controller may be configured to log and record performance parameter data related to the performance of a connected HVAC system over a period of time. The performance parameter data related may be written to a performance log that is stored in a memory of the HVAC controller. In some instances, the HVAC controller may receive a first user request via the user interface, and in response, retrieve at least some of the performance related data from the performance log that corresponds to a first selected subset of the period of time, and display at least some of the retrieved performance parameter data on a display of the HVAC controller.
• In some cases, the HVAC controller may receive a second user request via the user interface and, in response, retrieve at least some of the performance parameter data from the performance log that corresponds to a second selected subset of the period of time, and display at least some of the retrieved performance parameter data on the display of the HVAC controller. In some cases, the second subset of the period of time may be longer that the first subset of the period of time.
• In some instances, and to reduce the storage requirement for the performance parameter data, the HVAC controller may only store a minimum and/or a maximum value over a specified period of time for each of the one or more different performance parameters, but this is not required. Also, and in some instances, it is contemplated that the HVAC controller may automatically change a format of the performance parameter data that is displayed on the display of the HVAC controller based on a current setup configuration of the connected HVAC 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.
BRIEF DESCRIPTION OF THE DRAWINGS
• The disclosure may be more completely understood in consideration of the following detailed description of various embodiments in connection with the accompanying drawings, in which:
• FIG. 1 is a schematic view of an illustrative HVAC system servicing a building or structure;
• FIG. 2 is a schematic view of an illustrative HVAC controller;
• FIG. 3 is a front view of an illustrative HVAC controller;
• FIG. 4 provides an illustrative example of a home screen that may be displayed upon the HVAC controllers ofFIGS. 2 and 3; and
• FIGS. 5-23 provide several illustrative examples of screens that may be displayed upon the HVAC controllers ofFIGS. 2 and 3 when in use.
• 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 embodiments described. On the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the disclosure.
DESCRIPTION
• The following description should be read with reference to the drawings wherein like reference numerals indicate like elements throughout the several views. The detailed description and drawings show several embodiments which are meant to illustrative of the claimed disclosure.
• FIG. 1 is a schematic view of abuilding2 having an illustrative heating, ventilation, and air conditioning (HVAC)system4. WhileFIG. 1 shows a typical forced air type HVAC system, other types of HVAC systems are contemplated including, but not limited to, boiler systems, radiant heating systems, electric heating systems, cooling systems, heat pump systems, and/or any other suitable type of HVAC system, as desired. Theillustrative HVAC system4 ofFIG. 1 includes one ormore HVAC components6, a system of ductwork and air vents including asupply air duct10 and areturn air duct14, and one ormore HVAC controllers18. The one ormore HVAC components6 may include, but are not limited to, a furnace, a heat pump, an electric heat pump, a geothermal heat pump, an electric heating unit, an air conditioning unit, a humidifier, a dehumidifier, an air exchanger, an air cleaner, a damper, a valve, and/or the like.
• It is contemplated that the HVAC controller(s)18 may be configured to control the comfort level in the building or structure by activating and deactivating the HVAC component(s)6 in a controlled manner. The HVAC controller(s)18 may be configured to control the HVAC component(s)6 via a wired orwireless communication link20. In some cases, the HVAC controller(s)18 may be a thermostat, such as, for example, a wall mountable thermostat, but this is not required in all embodiments. Such a thermostat may include (e.g. within the thermostat housing) or have access to a temperature sensor for sensing an ambient temperature at or near the thermostat. In some instances, the HVAC controller(s)18 may be a zone controller, or may include multiple zone controllers each monitoring and/or controlling the comfort level within a particular zone in the building or other structure.
• An illustrative HVAC controller, which is not meant to be limiting in any way, is disclosed in: US Published Patent Application No. 20090140062, entitled “HVAC CONTROLLER THAT SELECTIVELY REPLACES OPERATING INFORMATION ON A DISPLAY WITH SYSTEM STATUS INFORMATION”; US Published Application No. 20090143880, entitled “HVAC CONTROLLER WITH CONTEXT SENSITIVE HELP SCREENS”; US Published Application No. 20090143918, entitled “METHOD AND APPARATUS FOR CONFIGURING AN HVAC CONTROLLER”; US Published Application No. 20090143916, entitled “HVAC CONTROLLER HAVING A PARAMETER ADJUSTMENT ELEMENT WITH A QUALITATIVE INDICATOR”; US Published Application No. 20090143879, entitled “HVAC CONTROLLER WITH PARAMETER CLUSTERING”; US Published Application No. 20090140056, entitled “HVAC CONTROLLER WITH QUICK SELECT FEATURE,” the entireties of which are incorporated herein by reference for all purposes.
• In theillustrative HVAC system4 shown inFIG. 1, the HVAC component(s)6 may provide heated air (and/or cooled air) via the ductwork throughout thebuilding2. As illustrated, the HVAC component(s)6 may be in fluid communication with every room and/or zone in thebuilding2 via theductwork10 and14, but this is not required. In operation, when a heat call signal is provided by the HVAC controller(s)18, an HVAC component6 (e.g. forced warm air furnace) may be activated to supply heated air to one or more rooms and/or zones within thebuilding2 viasupply air ducts10. The heated air may be forced throughsupply air duct10 by a blower orfan22. In this example, the cooler air from each zone may be returned to the HVAC component6 (e.g. forced warm air furnace) for heating viareturn air ducts14. Similarly, when a cool call signal is provided by the HVAC controller(s)18, an HVAC component6 (e.g. air conditioning unit) may be activated to supply cooled air to one or more rooms and/or zones within the building or other structure viasupply air ducts10. The cooled air may be forced throughsupply air duct10 by the blower orfan22. In this example, the warmer air from each zone may be returned to the HVAC component6 (e.g. air conditioning unit) for cooling viareturn air ducts14.
• In some cases, the system of vents orductwork10 and/or14 can include one ormore dampers24 to regulate the flow of air, but this is not required. For example, one ormore dampers24 may be coupled to one or more HVAC controller(s)18, and can be coordinated with the operation of one ormore HVAC components6. The one or more HVAC controller(s)18 may actuatedampers24 to an open position, a closed position, and/or a partially open position to modulate the flow of air from the one or more HVAC components to an appropriate room and/or zone in the building or other structure. Thedampers24 may be particularly useful in zoned HVAC systems, and may be used to control which zone(s) receives conditioned air from the HVAC component(s)6.
• In many instances, one ormore air filters30 may be used to remove dust and other pollutants from the air inside thebuilding2. In the illustrative example shown inFIG. 1, the air filter(s)30 is installed in thereturn air duct14, and may filter the air prior to the air entering theHVAC component6, but it is contemplated that any other suitable location for the air filter(s)30 may be used. The presence of the air filter(s)30 may not only improve the indoor air quality, but may also protect theHVAC components6 from dust and other particulate matter that would otherwise be permitted to enter the HVAC component.
• In some cases, and as shown inFIG. 1, theillustrative HVAC system4 may include an equipment interface module (EIM)34. When provided, theequipment interface module34 may be configured to measure or detect a change in a given parameter between the return air side and the discharge air side of theHVAC system4. For example, theequipment interface module34 may be adapted to measure a difference in temperature, flow rate, pressure, or a combination of any one of these parameters between the return air side and the discharge air side of theHVAC system4. In some cases, theequipment interface module34 may be adapted to measure the difference or change in temperature (delta T) between a return air side and discharge air side of theHVAC system4. For example, theequipment interface module34 may include afirst temperature sensor38alocated in the return (incoming)air duct14, and asecond temperature sensor38blocated in the discharge (outgoing or supply)air duct10. Alternatively, or in addition, theequipment interface module34 may include a differential pressure sensor including afirst pressure tap39alocated in the return (incoming)air duct14, and asecond pressure tap39blocated downstream of theair filter30 to measure a change in a parameter related to the amount of flow restriction through theair filter30. In some cases, theequipment interface module34, when provided, may include at least one flow sensor that is capable of providing a measure that is related to the amount of air flow restriction through theair filter30. In some cases, theequipment interface module34 may include an air filter monitor. These are just some examples.
• When provided, theequipment interface module34 may be configured to communicate with theHVAC controller18 via, for example, a wired orwireless communication link42. In some cases, theequipment interface module34 may be incorporated or combined with theHVAC controller18. In either cases, theequipment interface module34 may communicate, relay or otherwise transmit data regarding the selected parameter (e.g. temperature, pressure, flow rate, etc.) to theHVAC controller18. In some cases, theHVAC controller18 may use the data from theequipment interface module34 to evaluate the system's operation and/or performance. For example, theHVAC controller18 may compare data related to the difference in temperature (delta T) between the return air side and the discharge air side of theHVAC system4 to a previously determined delta T limit stored in theHVAC controller18 to determine a current operating performance of theHVAC system4.
• FIG. 2 is a schematic view of anillustrative HVAC controller18. In some instances,HVAC controller18 may be a thermostat, but this is not required. In the illustrative embodiment ofFIG. 2,HVAC controller18 includes a processor (e.g. microprocessor, microcontroller, etc.)44, amemory52 anduser interface48 including a display. In some cases, theHVAC controller18 may optionally include an input/output block (I/O block)58 for receiving one or more signals from the HVAC system and/or for providing one or more control signals to the HVAC system. The I/O block58 may communicate with one ormore HVAC components6 of theHVAC system4. Alternatively, or in addition, the I/O block58 may communicate with another controller, which is in communication with one ormore HVAC components6 of theHVAC system4, such as a zone panel in a zoned HVAC system.
• In the illustrative embodiment ofFIG. 2,user interface48 may be any suitable use interface that permitsHVAC controller18 to display and/or solicit information, as well as accept one or more user interactions with theHVAC controller18. For example, theuser interface48 may permit a user to enter data such as temperature set points, humidity set points, starting times, ending times, diagnostic limits, conditions under which diagnostic limits may be suspended, responses to alerts, and the like. In some cases,user interface48 may include a display and a distinct keypad. A display may be any suitable display. In some instances, a display may include or may be a liquid crystal display (LCD), and in some cases a fixed segment display or a dot matrix LCD display. If desired,user interface48 may be a touch screen LCD panel that functions as both display and keypad. In some instances, a touch screen LCD panel may be adapted to solicit values for a number of operating parameters and/or to receive such values, but this is not required.
• Theprocessor44 may operate in accordance with an algorithm that controls or at least partially controls one ormore HVAC components6 of an HVAC system such as, for example,HVAC system4 shown inFIG. 1. Theprocessor44 may, for example, operate in accordance with an algorithm that provides temperature set points, starting and/or ending times, and the like. In some cases,HVAC controller18 may include a timer (not shown). The timer may be integral to theprocessor44 or may be provided as a separate component.
• In some cases, theprocessor44 may be programmed to receive one or more signals related to a current performance of the HVAC system from the HVAC system, either directly or via the I/O block58. The one or more signals received by theprocessor44 from theHVAC system4 may be indicative of one or more performance parameters that may be used to characterize the performance of theHVAC system4. For example, the one or more signals may be indicative of the total run time since installation of theHVAC system4, the total run time for a selected time period, the number of heating or cooling cycles completed since installation of theHVAC system4, the number of heating or cooling cycles during a selected time period, the maximum and minimum indoor air temperature, the maximum and minimum outdoor air temperature, the maximum and minimum indoor humidity, the maximum and minimum outdoor humidity, the maximum and minimum discharge air temperature, the maximum and minimum delta T, and/or the like. These are just some examples.
• Theprocessor44 may receive and record data related to any combination of those performance parameters listed above, as well as other parameters as desired. For example, in some cases, theprocessor44 may receive and record parameter data relating to two different performance parameters such as an indoor air temperature and an indoor humidity, an outdoor temperature and an outdoor humidity, a discharge air temperature and a delta T, but these are just examples. Additionally, it is useful to note that the data that is received and subsequently recorded by theprocessor44 may be dependent upon the type of HVAC equipment installed. For example, if theHVAC system4 does not include an outdoor air temperature sensor, data related to the outdoor air temperature may not be recorded by theprocessor44 in thememory52.
• In some cases, theprocessor44 may be configured to store data related to the performance of the HVAC system over a period of time. The performance data may be logged and recorded in one or more performance data logs stored in theHVAC controller memory52. In some cases, heating performance data corresponding to the heating mode of theHVAC system4 may be stored in a heating performance log, and cooling performance data corresponding to the cooling mode of theHVAC system4 may be stored in a cooling performance log. In some cases, the heating performance log and the cooling performance log may be recorded in separate data logs in theHVAC controller memory52, but this is not required. In other cases, the heating performance log and the cooling performance log may be combined into a single HVAC system performance data log. In such instances, the heating performance data may be displayed and viewed separately from the cooling performance data when desired, but this is not required. The performance data log(s) may be displayed on a display of theuser interface48 in response to a request initiated by a user, or may be downloaded to a remote device for viewing and/or analysis. In many cases, the heating and the cooling performance data logs may be similar to one another. As such, the heating and cooling performance logs may be described together, and may simply be referred to herein as performance data logs.
• In some cases, theprocessor44 may be configured to log and record performance data related to the performance of the HVAC system for a period of time of: up to about five years; of up to about three years; of up to about two years; of up to about one year, or more or less. As discussed above, the performance data may be logged and recorded in a performance data log (heating, cooling, and/or combined) stored in theHVAC controller memory52. In some cases, theprocessor44 may be programmed to group performance data into one or more subsets of data according to, for example, various time periods. For example, theprocessor44 may be programmed to group, classify or sort performance data stored in the performance data logs into data subsets corresponding to a one hour period, a one day period, a one week period, a one month period, a three month period, a six month period, a one year period, an eighteen month period, a two year period, and/or any other suitable time period(s). Grouping the performance related data into subsets according to various different time periods may allow the performance related data to be more easily sorted, classified and/or viewed according to one or more of the selected time periods. Additionally, data subsets corresponding to shorter periods of time (e.g. a minute, an hour, a day, a week, etc.) may be used to provide a more contemporary view the most recently collected performance related data. Data subsets corresponding to longer periods of time (e.g. a month, a three month period, a six month period, a year period, etc.) may be used to provide a more long term, historical view of the collected performance related data.
• Theprocessor44 may be configured to record and log performance related data on a second, minute, hourly, daily, weekly, monthly, yearly, or any other suitable basis. In one specific example, theprocessor44 may be configured to record and log performance related data on an hourly basis for the most recent 192 hours, on a daily basis for the most recent fifteen days, on a weekly basis for the most recent eight weeks, and on a monthly basis for the most recent twenty-five months. In some cases, the amount of data entries that may be logged and recorded on an hourly, daily, weekly, monthly and/or yearly basis by theprocessor44 may only be limited by the capacity of thecontroller memory52.
• To help conserve memory, theprocessor44 may be programmed to record and log only the minimum and maximum values for each of the performance related parameters being monitored during the corresponding time period. For example, each data log entry logged and recorded at the end of an hour period of time may include only the minimum and maximum values detected during the hour period for the indoor air temperature, the outdoor air temperature, the indoor humidity, the outdoor humidity, the discharge air temperature, the delta T, and/or the like, as applicable. Also, each data log entry logged and recorded at the end of a daily time period may include only the minimum and maximum values detected during the daily time period for the indoor air temperature, the outdoor air temperature, the indoor humidity, the outdoor humidity, the discharge air temperature, the delta T, and/or the like, as applicable.
• Additionally, the data log entry may record the total run time of theHVAC system4 since installation, the total run time for each time period, the number of heating or cooling cycles completed since installation of the HVAC system, the number of heating or cooling cycles during each time period, as applicable. In some cases, each data log entry logged and recorded by theprocessor44 may include a date and time stamp. The date and time stamp may be provided by the processor according to the date and time when the data log entry was recorded. In some cases, an HVAC cycle number count may be used in addition to, or in lieu of, a date and time stamp.
• When the shortest time period corresponds to an hour, the content of the performance data logs may be updated on an hourly basis at the end of every sixty minute period as determined by an internal clock or timer provided with theprocessor44. The internal clock or timer may be integral with theprocessor44 or may be provided as a separate component. In some cases, when the amount of data log entries exceeds the capacity of the data log, the oldest data log entry may be removed from the performance data log before a new data log entry is recorded (First-In-First-Out). The oldest data log entry may be the oldest entry that was created for a selected period of time. For example, at the end of every hour a new data log entry may be recorded. If there are 192 hourly data entries previously recorded in the hourly data log before the new data log entry is made, the oldest created hourly data log entry may be removed. Similarly, at the end of every hour, theprocessor44 may be programmed to compare the day of the current time and date stamp to the current daily data log entry. If the days are different, a new daily log entry may be created. In some cases, this may cause theprocessor44 to remove the oldest daily log entry from the performance data log.
• Theprocessor44 may be further programmed to compare the week of the current date and time stamp to the week of the currently weekly entry and, if the weeks are different, a new weekly data log entry may be added to the performance data log. As a result, in some cases, the oldest weekly data log entry may be removed from the performance data log. Theprocessor44 may also be programmed to compare the month of the current time date and time stamp to the month of the current monthly data log entry. If the months differ, theprocessor44 may be programmed to add a new monthly data log entry. In some cases, the oldest monthly log entry may be removed. These time periods are only illustrative. Also, in some cases, only the minimum and maximum values may be stored for each time period, which may help conserve memory space withinmemory52.
• In some cases, theprocessor44 also may be configured to monitor one or more signals from theHVAC system4 to determine whether or not theHVAC system4 has violated a pre-determined diagnostic limit for a selected parameter stored in theHVAC controller memory52. In some cases, for example, theprocessor44 may monitor one or more signals to/from theHVAC system4 to determine whether or not the HVAC system has violated a pre-determined delta T limit in either the heating and/or cooling mode. A violation of a pre-determined diagnostic limit such as, for example, a delta T limit may occur if, for example, theHVAC system4 fails to reach a minimum delta T limit or exceeds a maximum delta T limit. Additionally, a violation may occur if, for example, theHVAC system4 fails to meet or exceed a minimum delta T limit within a pre-determined period of time. These are just some examples. The diagnostic limits and the conditions for violating a diagnostic limit may be dependent upon the HVAC system set-up, the number and type ofHVAC components6 included in theHVAC system4, whether or not theHVAC system4 is subject to a utility load shutoff, user preferences, user specified conditions for determining a diagnostic fault, and the like.
• In many cases, when a diagnostic limit has been violated, theprocessor44 may be configured to indicate to the user that a diagnostic fault has occurred. This may be accomplished in a variety of ways. For example, if theprocessor44 has determined that a diagnostic limit has been violated, and a diagnostic fault has occurred, theprocessor44 may display a user alert on a display of theuser interface48. In some cases, theprocessor44 may be programmed to alert the user to a diagnostic fault only after a pre-determined number of faults are detected by theprocessor44. In some cases, the user alert may be a simple text string displayed on the display of theuser interface48 describing the nature of the violation that has occurred. In other instances, theprocessor44 may provide some visual indication to alert the user that a fault has occurred. Such visual indication may include a colored, flashing, highlighted, or grayed-out button or icon provided on theuser interface48. In still other instances, theprocessor44 may be configured to send an email, instant message, or text message to a user to alert the user that a fault has occurred. Such an alert may be provided to the user even when the user is away from the home, building, or other structure in which theHVAC system4 is installed.
• Memory52 of theillustrative HVAC controller18 may be in communication with theprocessor44.Memory52 may be any suitable type of storage device including, but not limited to, RAM, ROM, EPROM, flash memory, a hard drive, and/or the like. In some cases,processor44 may store information withinmemory52, and may subsequently retrieve the stored information.Memory52 may be used to store any desired information, such as control algorithms, set points, diagnostic limits such as, for example, differential pressure limits, delta T limits, and the like, for theHVAC controller18. As eluded to above,memory52 may also be used to store performance data related to the performance of theHVAC system4 in one or more performance logs. The performance data may be stored in thememory52 such that it may be retrieved from the memory upon request. In some cases, the performance data may be stored in thememory52 such that at least one subset of the data may be retrieved from the memory in response to a request from a user.
• In some cases,HVAC controller18 may also include adata port56.Data port56 may be a wireless port such as a Bluetooth™ port or any other wireless protocol. In other cases,data port56 may be a wired port such as a serial port, a parallel port, a CATS port, a USB (universal serial bus) port, or the like. In some instances,data port56 may be a USB port and may be used to download and/or upload information from a USB flash drive. Other remote devices may also be employed, as desired.
• Data port56 may be configured to communicate withprocessor44 and may, if desired, be used to either upload information toprocessor44 or to download information fromprocessor44. Information that can be uploaded or downloaded may include values of operating parameters. In some instances,data port56 may be used to upload a previously-created thermostat configuration intoHVAC controller18, thereby hastening the programming process. In some cases,data port56 may be used to download a thermostat configuration that has been created usingHVAC controller18, so that the thermostat configuration may be transferred to other similar thermostats. In some cases,data port56 may be used to upload and/or download information pertaining to an HVAC dealer or contractor.
• In some cases,data port56 may be used to download data stored within thememory52 for analysis. For example,data port56 may be used to download a performance data log or parts thereof to a remote device such as a USB memory stick (also sometimes referred to as a thumb drive or jump drive), personal computer, laptop, iPAD® or other tablet computer, PDA, smart phone, or other remote device, as desired. In some cases, the data may be convertible to an MS EXCEL®, MS WORD® file, text, or XML file, but this is not required.
• FIG. 3 is a front view of anillustrative HVAC controller18 that has auser interface48 that includes adisplay62 disposed within ahousing66 but viewable from external to thehousing66. In some cases,display62 may be a touch screen LCD display. If desired,display62 may be a dot matrix touch screen LCD display. A dot matrix touch screen LCD display is a touch screen LCD that permits images such as letters, numbers, graphics, and the like to be displayed anywhere on the LCD, rather than being confined to predetermined locations such as is the case with a fixed segment LCD display.Housing66 may be formed of any suitable material, such as a polymeric material. In some cases, thehousing66 may be formed such that it defines a data port56 (seeFIG. 2). Thehousing66 may also include suitable wiring and/or otherelectrical connections68 such that theHVAC controller18 may be electrically coupled to theHVAC system4.
• In some cases,HVAC controller18 may be configured to provide substantial display and/or programming functionality, but this is not required. In some cases,HVAC controller18 may be configured to display a default display, referred to herein as a home screen, which is displayed byHVAC controller18 when no other data entry is underway for a period of time.FIG. 4 provides anexample home screen72 that may be displayed byHVAC controller18. In some cases, home screens may include screens that can be accessed by a top level navigational menu. A home screen may, if desired, display one or more parameters relating to environmental conditions such as indoor and/or outdoor air temperature and/or humidity, expected weather conditions, and/or the status of equipment that is at least partially controlled byHVAC controller18.
• Theillustrative home screen72 shown inFIG. 4 includes anavigational bar76 along the top.Navigational bar76 may be considered as providing top level navigation, but this is not required. In some cases, if desired,navigational bar76 may include one or more of aHOME button78, aFAN button80, aSYSTEM button82 and/or aMENU button84.FIG. 4 is an example of a screen that may be displayed after a user has pushedHOME button78, or when no other data entry is underway for a period of time. Additionally, throughhome screen72, the user may access one or menus from which the user may make a temperature set point change, a humidity set point change, an indoor air quality change, a programmable schedule change, a system mode change, a fan setting change, an installer setting change, among others. Such changes may be considered a user interaction.
• In some cases,illustrative home screen72 may be considered as having two or more regions. For example,home screen72 may include afirst region86 and asecond region88. In some instances,first region86 may be considered as displaying or otherwise providing primary information, whilesecond region88 may be considered as displaying or otherwise providing secondary information. In some cases, primary information may be information that is considered to be more important, more interesting and/or more useful than secondary information. To illustrate,first region86 may display one or more of a current air temperature reading, a current indoor humidity, a schedule status, and the like.Second region88 may display one or more of a date and time, an outdoor air temperature reading, an outdoor humidity reading, an equipment status, and the like.
• Home screen72 may also include athird region90 that may be used for displaying and/or adjusting a set point value. In the example shown,third region90 may display afirst parameter92, a first uparrow94 and afirst down arrow96.Third region90 may also display asecond parameter98, a second uparrow100 and a second downarrow102.First parameter92 may be adjusted up or down by a user using first uparrow94 and/orfirst down arrow96, as appropriate.Second parameter98 may be adjusted up or down by a user using second uparrow100 and/orsecond down arrow102, as desired. In some cases,third region90 may, as illustrated, display both a heating temperature set point and a cooling temperature set point, but this is not required.
• FIGS. 5-14 show illustrative screens that may be displayed when a contractor or other user is attempting to access a performance log stored in thememory52 of theHVAC controller18. Selecting theMENU button84 onhome screen72 ofFIG. 4 may cause themenu screen110 ofFIG. 5 to be displayed. Theillustrative menu screen110 may include a table114 that has one or moreselectable menu options118 that may be selected by a user. In some cases, the table114 may be a scrolling table, in which case themenu screen110 may also include ascroll bar122 including first andsecond arrows124a,124bthat may facilitate a user in scrolling through theavailable menu options118.
• Upon selection of the INSTALLEROPTIONS menu options118, theillustrative HVAC controller18 may be configured to display a passwordprompt screen128, as illustrated inFIG. 6. The passwordprompt screen128 may include auser prompt132 that may prompt the user to enter a user login ID, which may include a user name and/or password. In some cases, certain rights may be associated with different user login IDs or passwords. For example, a homeowner may have a different login ID and different user rights than an HVAC contractor. The user login ID and/or password may include any combination of alphanumeric characters. In one example, as illustrated inFIG. 6, the password may be a sequence of numbers. The sequence of numbers may be adjusted to the correct sequence using corresponding arrow keys. The user may then select theDONE button144 to confirm entry of the password. In some cases, the passwordprompt screen128 may include a CANCELbutton148, which upon its selection may cancel the user's current actions and return the user to the previous screen, such as themenu screen110 ofFIG. 5. In some cases, the passwordprompt screen128 may include aHELP button152. Selection of theHELP button152 may cause theHVAC controller18 to display additional information about the use of the currently displayed screen. Sometimes this information screen may appear on an additional screen or a pop-up screen that overlays the current screen, but this is not required.
• Upon selection of the DONEbutton144 confirming entry of a password, theHVAC controller18 may confirm that a valid password has been entered. If a valid password has been entered, theHVAC controller18 may display an installeroptions menu screen156, such as illustrated inFIG. 7. Like theprevious menu screen110, the installeroptions menu screen156 may include a table160 including one or more installer options. In some cases, the table160 may be a scrolling table, in which case the installeroptions menu screen156 may also include ascroll bar164 having first andsecond arrows168a,168bthat may facilitate a user to scroll through and view the available installer options presented in table160. The installeroptions menu screen156 may also include a BACK button orPREVIOUS MENU button172 which, when selected, may causemenu screen110 ofFIG. 5 to be displayed. Additionally, in some cases, the installer options menu screen may include aHELP button176, which when selected, may cause additional information pertaining to the use of the currently displayed screen to be displayed.
• In the example shown, the table160 includes a number ofinstaller options180 that may be selected by the user. In some cases, aDATA LOGS option180 may be provided, which may provide access to a performance data log stored in theHVAC controller memory52. In some instances, selection of the DATA LOGSoption180 may cause a datalogs menu screen184 to be displayed by theHVAC controller18, as shown inFIG. 8. The data logsmenu screen184 may display one or more data log options188a-188ethat may be selected by the user. The data logsmenu screen184 may include a back button or aPREVIOUS MENU button197, which when selected, may return the user to the installeroptions menu screen156 illustrated inFIG. 7. The data logsmenu screen184 may include aHELP button196, which when selected, may cause additional information pertaining to the use of the currently displayed screen to be displayed.
• In the example shown, a user may select eitherperformance log option188cor188dto access a performance data log stored in theHVAC controller memory52. For example, a user may select the COOLINGPERFORMANCE LOG option188dto access a cooling performance log stored in theHVAC controller memory52. In some instances, upon selection of the COOLINGPERFORMANCE LOG option188d, theHVAC controller18 may retrieve at least some of the cooling performance data stored in thememory52 and display the cooling performance data via one or more screens such as, for example, screens200,202,204,206 as shown in the illustrative examples provided byFIGS. 9-12.
• Tabs orbuttons208,212,216, and220 shown inFIGS. 9-12 each correspond to a subset of data for a selected period of time (e.g. hourly, daily, weekly, monthly). A user may select a tab orbutton208,212,216 or220 that corresponds to the subset of cooling performance data for which the user desires to view. In some cases, this may include a first userrequest selecting tab208, a second userrequest selecting tab212, a third userrequest selecting tab216, and a fourth userrequest selecting tab220. The user may be free to select any oftabs208,212,216 or220 in any order. In one example, a user may select: the HOURLY tab208 (seeFIG. 9) to view the most recent cooling performance data on an hourly basis (FIG. 9); theDAILY tab212 to review the most recent cooling performance data on a daily basis (FIG. 10); theWEEKLY tab216 to review cooling performance data on a weekly basis (FIG. 11); and/or theMONTHLY tab220 to review cooling performance data on monthly basis (FIG. 12). In some cases, and to help reduce the amount of performance parameter data that must be stored inmemory52, only maximum and/or minimum values may be stored in the performance log, and then subsequently displayed onscreens200,202,204 and206.
• FIG. 9 provides an illustrative example of a performancedata log screen200 that may display one or more subsets of cooling performance data corresponding to a period of time of one hour.Screen200 includes afirst label228 that identifies the performance log (e.g. cooling, heating, or combined). For example,first label228 inFIG. 9 identifies the performance log as the “Cooling Performance Log.” In some cases,screen200 may also include asecond label232 that may identify the time period for which performance data is currently being displayed. For example,second label232 identifies the time period for which performance data is currently displayed as “Thursday, January 21: 11 AM-12 PM.” In some cases, the year of the data period may be included in thesecond label232. In some cases,second label232 may be updated to display a new date and time period in response to selection of a new time period by a user for viewing.
• In the example shown, performance data logscreen200 displays hourly performance data from the performance data log identified by thefirst label228. In some cases, the hourly performance data may be presented in a table, such as table236. In some cases, table236 may be a scrolling table, in which case the performance data log screen may include a scroll bar and/or arrow keys (not shown) to facilitate navigation of table236. In some cases, table236 may display maximum and minimum values for one or more performance parameters identified in afirst column240 of table236. The maximum and minimum values may be displayed in separate columns244,248 of table236, but this is not required. Table236 may include one ormore rows252, each corresponding to a performance parameter monitored by theHVAC controller18. Each performance parameter may include alabel254 identifying the monitored performance parameter for which the maximum and minimum values are displayed. Because the performance data that may be logged and recorded by theHVAC controller18 may be dependent upon type of HVAC equipment and the equipment setup, theHVAC controller18 may be programmed to dynamically change the format of table236 displayed onscreen200 so as to not display rows/labels252,254 for one or more performance parameters that do not include corresponding performance parameter data stored in thecontroller memory52. For example, if the HVAC equipment does not include discharge air temperature sensor, then table236 may not display a row/label252,254 corresponding to either the discharge air temperature or delta T.
• In some cases, even if a particular type of HVAC equipment (e.g. air temperature sensor) may be present as part of theHVAC system4, the HVAC equipment may not report any data, may report only data outside the allowable range, or may report data indicating the equipment is not operating or available over a certain time period for any number of reasons including, for example, an equipment malfunction. As such, table236 may still include a row/label252,254 for the performance parameter related to that equipment type (e.g. air temperature sensor), but will not display any data in the adjacent row. Instead, the table236 may include an indicator that may indicate that data is missing, out of range, or not available for the selected period of time. Exemplary indicators may include “--,” “-,” “N/A,” “NA,” “Error,” and the like. If some data is reported during the selected time period, then table236 may include a data entry related to that equipment type for the selected time period.
• In some cases, performance data logscreen200 may include first andsecond buttons258,262 for navigating forward and backward in time within the hourly performance data stored in the performance data log. For example, selection offirst button258 labeled “Previous Hour” by a user may causeHVAC controller18 to cause table236 to display performance log data from the previous hour. Similarly, selection ofsecond button262 labeled “Next Hour” by a user may causeHVAC controller18 to display performance log data from the next succeeding hour. In some cases, holdingfirst button258 orsecond button262 may causeHVAC controller18 to rapidly move through the hourly performance log data displayed in table236, sometimes by four or more hours at a time. This feature may help a user to more quickly navigate to a desired time period contained with the performance data log.
• Performance data logscreen200 may also include aHELP button266 that, when selected may causeHVAC controller18 to display additional information that may be helpful to a user in using the current screen. The user may selectbutton270 labeled “OK” or “Done” when they are finished viewing the performance log data displayed onscreen200. Selection ofbutton270 labeled “OK” may cause theHVAC controller18 to return to a previous screen such asmenu screen184 shown inFIG. 8 or, in some cases, may cause theHVAC controller18 to display a home screen such as, for example,home screen72 ofFIG. 4.
• In some cases, a user may select another subset of performance data for viewing by selecting a corresponding tab orbutton212,216,220 provided along atop portion224 ofscreen200. For example, a user may selecttab212 corresponding to daily performance data for the performance data log identified by thefirst label228. In some cases, the daily performance data may overlap and/or include at least some of the hourly performance data contained within the identified performance data log.
• FIG. 10 provides an illustrative example of a cooling performance data logscreen202 that may display one or more subsets of cooling performance data corresponding to a period of time of one day.Screen202 includes afirst label228 that identifies the performance log (e.g. cooling). In the example shown,first label228 still identifies the performance log as the “Cooling Performance Log.” In some cases,screen202 may also includesecond label232 that may be updated to identify the day for which performance data is currently being displayed. For example,second label232 identifies the day as “Thursday, January 21.” In some cases, the year of the data period may be included insecond label232. In some cases,second label232 may be updated to identify a different day in response to selection of a different day by a user. Upon selection of a new subset of performance data by a user, table236, as shown inFIG. 10, may be updated to display performance data for the selected day identified byfirst label228. In the example shown inFIG. 10, table236 has been updated to display cooling performance data for Thursday, January 21.
• Similar to the performance data logscreen200 shown inFIG. 9, performance data logscreen202 may include first andsecond buttons274,278 for navigating forward and backward within the daily performance data stored in the performance data log. For example, selection offirst button274 labeled “Previous Day” by a user may causeHVAC controller18 to display performance log data in table236 from the previous day (e.g. January 20). Similarly, selection ofsecond button278 labeled “Next Day” by a user may causeHVAC controller18 to display performance log data from the next day (e.g. January 22). In some cases, pressing and holdingfirst button274 orsecond button278 may causeHVAC controller18 to rapidly move through the daily performance log data displayed in table236, sometimes by three or more days at a time. This feature may help a user more quickly navigate to a desired day contained with the performance data log.
• The user may selectbutton270 labeled “OK” or “Done” when they are finished viewing the performance log data displayed onscreen202. Selection ofbutton270 labeled “OK” may cause theHVAC controller18 to return to a previous screen such asmenu screen184 shown inFIG. 8 or, in some cases, may cause theHVAC controller18 to display a home screen such as, for example,home screen72 ofFIG. 4.
• In some cases, a user may select yet another subset of performance data for viewing by selecting the corresponding tab orbutton208,216,220 provided long thetop portion224 ofscreen202. For example, a user may selecttab216 corresponding to weekly performance data for the performance data log identified by thefirst label228. In some cases, the weekly performance data may overlap and/or include at least some of the hourly and/or daily performance data contained within the identified performance data log.
• FIG. 11 provides an illustrative example of a cooling performance data logscreen204 that may display one or more subsets of cooling performance data corresponding to a period of time of one week. Likescreens200 and202 ofFIGS. 9 and10,screen204 may include afirst label228 that identifies the performance log (e.g. cooling). In the example shown, thefirst label228 still identifies the performance log as the “Cooling Performance Log.” In some cases,screen202 may also includesecond label232.Second label232 may be updated to identify the week for which performance data is currently being displayed. In the example shown,second label232 identifies the week for which performance data is currently being displayed as “January 21-January 28.” In some cases, the year of the data period may be included insecond label232. In some cases,second label232 may be updated to display a new week in response to selection of a different week by a user. Upon selection of a new subset of performance data by a user, table236 may be updated to display performance data for the selected week identified byfirst label228. In the example shown, table236 has been updated to display cooling performance data for the week of January 21-January 28.
• Similar to performance data logscreens200 and202 shown inFIGS. 9 and 10, performance data logscreen204 may include first andsecond buttons282,286 for navigating forward and backward within the weekly performance data stored in the performance data log. For example, selection offirst button282 labeled “Previous Week” by a user may causeHVAC controller18 to update table236 to display performance log data from the previous week (e.g. January 13-January 20). Similarly, selection ofsecond button286 labeled “Next Week” by a user may causeHVAC controller18 to display performance log data from the next succeeding week (e.g. January 29-February 6). In some cases, pressing and holdingfirst button282 orsecond button286 may causeHVAC controller18 to rapidly move through the weekly performance log data displayed in table236, sometimes by three or more weeks at a time. This feature may help a user more quickly navigate to a desired week contained with the performance data log.
• The user may selectbutton270 labeled “OK” or “Done” when they are finished viewing the performance log data displayed onscreen204. Selection ofbutton270 labeled “OK” may cause theHVAC controller18 to return to a previous screen such asmenu screen184 shown inFIG. 8 or, in some cases, may cause theHVAC controller18 to display a home screen such as, for example,home screen72 ofFIG. 4.
• In some cases, a user may select yet another subset of performance data for viewing by selecting the corresponding tab orbutton208,212,220 provided long atop portion224 ofscreen202. For example, a user may selecttab220 corresponding to monthly performance data for the performance data log identified by thefirst label228. In some cases, the monthly performance data may overlap and/or include at least some of the hourly, daily, and/or weekly performance data contained within the identified performance data log.
• FIG. 12 provides an illustrative example of a cooling performance data logscreen206 that may display one or more subsets of cooling performance data corresponding to a period of time of one month. Likescreens200,202, and204 ofFIGS. 9,10, and11,screen206 may includefirst label228 that identifies the performance log (e.g. cooling). In the example shown,first label228 still identifies the performance log as the “Cooling Performance Log.” In some cases,screen202 may also includesecond label232.Second label232 may be updated to identify the month for which performance data is currently being displayed. In the example shown,second label232 identifies the month as “January.” In some cases,second label232 may be updated to display a new month in response to selection of a different month by a user. Upon selection of a new subset of performance data by a user, table236 may be updated to display performance data for the selected month identified byfirst label228 andsecond label232. For example, inFIG. 12, table236 has been updated to display cooling performance data for January.
• Performance data logscreen206 may also include first andsecond buttons290,294 for navigating forward and backward within the monthly performance data stored in the performance data log. For example, selection offirst button290 labeled “Previous Month” by a user may causeHVAC controller18 to update table236 to display performance log data from the previous month (e.g. December). Similarly, selection ofsecond button294 labeled “Next Month” by a user may causeHVAC controller18 to display performance log data from the next month (e.g. February). In some cases, pressing and holdingfirst button290 orsecond button294 may causeHVAC controller18 to rapidly move through the monthly performance log data displayed in table236, sometimes by three or more months at a time. This feature may help a user to more quickly navigate to a desired month contained with the performance data log.
• The user may selectbutton270 labeled “OK” or “Done” when they are finished viewing the performance log data displayed onscreen206. Selection ofbutton270 labeled “OK” may cause theHVAC controller18 to return to a previous screen such asmenu screen184 shown inFIG. 8 or, in some cases, may cause theHVAC controller18 to display a home screen such as, for example,home screen72 ofFIG. 4.
• WhileFIGS. 9-12 generally relate to screens relating to a cooling performance log that may be displayed byHVAC controller18, it should be understood thatHVAC controller18 may display one or more similar screens relating to a heating performance log, and/or any other suitable performance log as desired. For example,FIGS. 13 and 14 provide illustrative examples of performance data logscreens302,306 that may be displayed on the display of theHVAC controller18 upon selection of the HEATINGPERFOMANCE LOG option188cprovided on the data logsmenu screen184 ofFIG. 8.
• Performance data logscreen302 ofFIG. 13 includes weekly heating performance data. Similarly, performance data logscreen306 ofFIG. 14 includes monthly heating performance data. The weekly and monthly heating performance data may be presented in a table310. Like above, table310 includes maximum and minimum values for the indoor air temperature, the discharge air temperature, and the delta T. This is just an example of the type of data that may be included. It should be noted that unlike table236 ofscreens200,202,204 and206 ofFIG. 9-12, table310 does not display data relating to the indoor humidity, the outdoor air temperature, and the outdoor humidity. As discussed above, theHVAC controller18 may be programmed to dynamically change the format of table310 displayed onscreens302,306 so as to not display rows/labels312/314 for one or more performance parameters that do not include heating performance parameter data stored in theHVAC controller memory52. For example, if the HVAC heating equipment does not include an indoor humidity sensor, an outdoor air temperature sensor, and an outdoor humidity sensor, then table310 may not display a row/label312,314 corresponding to these parameters.
• In some cases, theHVAC controller18 may be configured to display heating or cooling performance data by stage combination of the HVAC system. Referring now back toFIG. 8, a user may select eitherperformance log option188cor188dto access a performance data log stored in theHVAC controller memory52. For example, a user may select the HEATINGPERFORMANCE LOG option188cto access a heating performance log stored in theHVAC controller memory52. In some instances, upon selection of the HEATINGPERFORMANCE LOG option188c, theHVAC controller18 may then display asubsequent user screen400, as shown inFIG. 15, which may query the user about viewing the selected performance log by stage combination of the HVAC system.
• User query screen400, as shown inFIG. 15, may include auser query statement404 that queries a user about viewing heating performance data by equipment stage.User query screen400 may also include one or more options for responding to the user query presented to a user byuser query screen400. For example, in some cases,user query screen400 may include afirst button408 labeled “YES” and asecond button412 labeled “NO” for responding to theuser query statement404 displayed by theHVAC controller18 onuser query screen400.User query screen400 may also include aHELP button416 that when selected by a user may causer theHVAC controller18 to display additional information on thescreen400 that may be helpful to the user.User query screen400 also may include aBACK button418 that when selected by a user may cause thecontroller18 to display a previous screen such as, for example, the data logmenus screen184 as shown inFIG. 8.
• Upon receiving positive confirmation from a user viauser query screen400 that viewing the performance data by stage is desired,HVAC controller18 may then display an equipmentstage selection screen430 as shown inFIG. 16. Equipment stage selection screen may430 may display one or moreselectable options434aand/or434b, eachoption434a,434bcorresponding to an equipment stage for which performance data is available. If no data is available for a particular stage, then an option corresponding to that stage may not be available. In some cases,screen430 may also display anadditional option438 that may correspond to all of the stages for which performance data may be available combined.User query screen430 may also include aHELP button442 that when selected by a user may causer theHVAC controller18 to display additional information on thescreen430 that may be helpful to the user, and aBACK button446 that when selected by a user may cause thecontroller18 to display a previous screen.
• In some instances, upon selection of theHEAT1,2option434b, theHVAC controller18 may retrieve at least some of the heating performance data for the selected stage (e.g. HEAT1,2) stored in thememory52 and display the heating performance data for the selected heating stage (e.g. HEAT1,2) via one or more screens such as, for example, screens500,502,504,506 as shown in the illustrative examples provided byFIGS. 17-20.
• Tabs orbuttons508,512,516, and520 shown inFIGS. 17-20 each correspond to a subset of data for a selected period of time (e.g. hourly, daily, weekly, monthly) for the selected heating stage (e.g. HEAT1,2). A user may select a tab orbutton508,512,516 or520 that corresponds to the subset ofHEAT1,2 performance data for which the user desires to view. In some cases, this may include a first userrequest selecting tab508, a second userrequest selecting tab512, a third userrequest selecting tab516, and a fourth userrequest selecting tab520. The user may be free to select any oftabs508,512,516 or520 in any order. In one example, a user may select: the HOURLY tab508 (seeFIG. 17) to view the mostrecent HEAT1,2 performance data on an hourly basis (FIG. 17); theDAILY tab512 to review the mostrecent HEAT1,2 performance data on a daily basis (FIG. 18); theWEEKLY tab516 to reviewHEAT1,2 performance data on a weekly basis (FIG. 19); and/or theMONTHLY tab520 to reviewHEAT1,2 performance data on monthly basis (FIG. 20). In some cases, and to help reduce the amount of performance parameter data that must be stored inmemory52, only maximum and/or minimum values may be stored in the performance log for each stage of heating and/or cooling equipment, and then subsequently displayed onscreens500,502,504 and506.
• FIG. 17 provides an illustrative example of an equipment stage performance data logscreen500 that may display one or more subsets of heating performance data for a selected heating equipment stage (e.g. HEAT1,2) corresponding to a period of time of one hour.Screen500 includes afirst label528 that identifies the performance log (e.g. COOL1,COOL1,2, COOL All Stages,HEAT1,HEAT1,2, HEAT All Stages, and the like). For example,first label528 inFIG. 17 identifies the performance log as the “HEAT1,2 Performance Log.” In some cases,screen500 may also include asecond label532 that may identify the time period for which theHEAT1,2, performance data is currently being displayed. For example,second label532 identifies the time period for which performance data is currently displayed as “Thursday, January 21: 11 AM-12 PM.” In some cases, the year of the data period may be included in thesecond label532. In some cases,second label532 may be updated to display a new date and time period in response to selection of a new time period by a user for viewing.
• In the example shown, equipment stage performance data logscreen500 displays hourly performance data from the performance data log identified by thefirst label528. In some cases, the hourly performance data may be presented in a table, such as table536. In some cases, table536 may be a scrolling table, in which case the performance data log screen may include a scroll bar and/or arrow keys (not shown) to facilitate navigation of table536. In some cases, table536 may display maximum and minimum values for one or more performance parameters identified in afirst column540 of table536. The maximum and minimum values may be displayed in separate columns of table536, but this is not required. Table536 may include one ormore rows552, each corresponding to a performance parameter monitored by theHVAC controller18. Each performance parameter may include alabel554 identifying the monitored performance parameter for which the maximum and minimum values are displayed. Because the performance data that may be logged and recorded by theHVAC controller18 may be dependent upon the type of HVAC equipment and the equipment setup, theHVAC controller18 may be programmed to dynamically change the format of table536 displayed onscreen500 so as to not display rows/labels552,554 for one or more performance parameters that do not include corresponding performance parameter data stored in thecontroller memory52. For example, if the HVAC equipment does not include discharge air temperature sensor, then table536 may not display a row/label552,554 corresponding to either the discharge air temperature or delta T.
• In some cases, equipment stage performance data logscreen500 may include first andsecond buttons558,562 for navigating forward and backward in time within the hourly performance data stored in the performance data log. For example, selection offirst button558 labeled “Previous Hour” by a user may causeHVAC controller18 to cause table536 to display performance log data from the previous hour. Similarly, selection ofsecond button262 labeled “Next Hour” by a user may causeHVAC controller18 to display performance log data from the next succeeding hour. In some cases, holdingfirst button558 orsecond button562 may causeHVAC controller18 to rapidly move through the hourly performance log data displayed in table536, sometimes by four or more hours at a time. This feature may help a user to more quickly navigate to a desired time period contained with the performance data log.
• Equipment stage performance data logscreen500 may also include aHELP button566 that, when selected may causeHVAC controller18 to display additional information that may be helpful to a user in using the current screen. The user may selectbutton570 labeled “OK” or “Done” when they are finished viewing the performance log data displayed onscreen500. Selection ofbutton570 labeled “OK” may cause theHVAC controller18 to return to a previous screen such asmenu screen184 shown inFIG. 8 or, in some cases, may cause theHVAC controller18 to display a home screen such as, for example,home screen72 ofFIG. 4.
• In some cases, a user may select another subset of performance data corresponding to an equipment stage for a selected mode for viewing by selecting the corresponding tab orbutton512,516,520 provided along atop portion524 ofscreen500. For example, a user may selecttab512 corresponding to daily performance data by equipment stage for the performance data log identified by thefirst label528. In some cases, the daily performance data may overlap and/or include at least some of the hourly performance data contained within the identified performance data log.FIG. 18 provides an illustrative example of an equipment stage performance data logscreen502 that may display one or more subsets of heating performance data corresponding to a period of time of one day for a selected equipment stage (e.g. HEAT1,2).
• In some cases, a user may select yet another subset of performance data corresponding to an equipment stage for a selected mode for viewing by selecting the corresponding tab orbutton508,516,520 provided long thetop portion524 ofscreen502. For example, a user may selecttab516 corresponding to weekly performance data for the performance data log identified by thefirst label228. In some cases, the weekly performance data may overlap and/or include at least some of the hourly and/or daily performance data contained within the identified performance data log.FIG. 19 provides an illustrative example of an equipment stage performance data logscreen504 that may display one or more subsets of heating performance data corresponding to a period of time of one week for a selected equipment stage.
• In some cases, a user may select yet another subset of performance data corresponding to an equipment stage for a selected mode for viewing by selecting the corresponding tab orbutton508,512,520 provided long atop portion524 ofscreen502. For example, a user may selecttab520 corresponding to monthly performance data for the equipment stage performance data log identified by thefirst label528. In some cases, the monthly performance data for the identified equipment stage may overlap and/or include at least some of the hourly, daily, and/or weekly performance data contained within the identified performance data log.FIG. 20 provides an illustrative example of an equipment stage performance data logscreen502 that may display one or more subsets of heating performance data corresponding to a period of time of one day for a selected equipment stage (e.g. HEAT1,2).
• In some cases, equipment stage performance data logscreens500,502,504, and506 may also include first andsecond buttons578,582 for navigating forward and backward between different equipment stages for which performance data may be available. This may allow a user to quickly access information for a different equipment stage for which performance data may be available. The different equipment stages for which performance data may be available may be listed on the stageselection menu screen430, as shown inFIG. 16 discussed above. In some cases, selection ofbutton578 labeled “Previous Stage” by a user may causeHVAC controller18 to display performance log data corresponding to a different equipment stage (e.g. HEAT1) for the identified time period (e.g. Thursday, January 21: 11 AM-12 PM, Thursday, January 21, January, 21-January 28 and/or January as shown inFIGS. 17-20). Selection ofbutton582 labeled “Next Stage” by a user may causeHVAC controller18 to display performance log data corresponding to yet another equipment stage (e.g. HEAT1,2,3) or a performance log showing the combined performance data for all available equipment stages for the identified time period. In some cases, holdingfirst button578 orsecond button582 may causeHVAC controller18 to rapidly move through the available performance logs by stage listed on the stageselection menu screen430. While first andsecond buttons578 and582 may include labels, as provided in the illustrative examples, it is also contemplated that first andsecond buttons578 and582 may also be represented by first and second arrow keys, forward and backward arrows keys, and the like. These are just some examples.
• As discussed above,HVAC controller18 may be configured to display the combined performance data for all available equipment stages for a selected time period for the identified mode (e.g. heating or cooling). In some cases, theHVAC controller18 may be configured to retrieve the combined performance data for all available equipment stages for the identified mode upon selection ofoption438 displayed on equipment stageselection menu screen430 as shown inFIG. 16. In other cases, selection of the “Previous Stage”button578 or the “Next Stage”button582 by a user may causeHVAC controller18 to retrieve the combined performance data for all available equipment stages for the identified mode for the selected time period. The combined performance data for all available equipment stages for the identified mode may displayed on a combined stages performancelog data screen600, as shown inFIG. 21.
• WhileFIGS. 17-21 generally relate to screens relating to a heating equipment stage performance log that may be displayed byHVAC controller18, it should be understood thatHVAC controller18 may display one or more similar screens relating to a cooling equipment stage performance log, and/or any other suitable performance log as desired.
• In some cases, an HVAC system may include two or more different equipment types for either heating and/or cooling. For example, an HVAC system for heating may include a heat pump or compressor and a backup heat. Each of the heat pump and the backup heat may have multiple equipment stages. As such, for HVAC systems including two or more different equipment types, it may be desirable to view a performance data log by equipment type. In some cases, the data for the selected equipment type also may be presented by equipment stage.
• Referring now again toFIG. 8, a user may select eitherperformance log option188cor188dto access a performance data log stored in theHVAC controller memory52. For example, a user may select the HEATINGPERFORMANCE LOG option188cto access a heating performance log stored in theHVAC controller memory52. In some instances, when theHVAC system4 includes two or more heating equipment types, selection of the HEATINGPERFORMANCE LOG option188cmay cause the controller to display asubsequent screen700 or704 (FIGS. 22 and 23) that may allow a user to select an equipment type and/or equipment stage for which they can then view a performance data log.
• FIGS. 22 and 23 provideillustrative screens700 and704 that relate to a heating system that includes a compressor and a backup heat. It will be understood that similar screens may be displayed for a cooling system having two or more cooling equipment types. In some cases, each of the compressor and the backup heat may have multiple stages. Backup heat sometimes may be referred to as an emergency heat and is often electric.Screen700 relates to a system in which the backup heat is allowed to run at the same time as the compressor.Screen704 relates to a system in which the backup heat is not allowed to run at the same time as the compressor. Each of the different equipment types and their respective stages (if applicable) may be presented in a table712. The table may include one or more selectable options716, each option corresponding to a different equipment type and/or equipment stage, as applicable. Upon selection of an equipment type and/or equipment stage, theHVAC controller18 may then display a performance data log for the selected equipment type. In some cases, if the selected equipment type has more than one stage, the HVAC system may display a performance data log for the selected equipment type by equipment stage. The performance data for the selected equipment type may be provided as a subset of data corresponding to a one hour period, a day period, a one week period, and a one month period, as discussed above. Additionally, theHVAC controller18 may be configured to allow a user to navigate between different selected periods of time within the performance data log and between different equipment types and/or stages without having to returnscreen700 or704.
• It should be noted with respect to each of the illustrative examples discussed herein, that if theHVAC controller18 is not in direct control of the one or more HVAC components, a performance log for heating may not offer display of the minimum discharge temperature and the minimum delta T. Similarly, if theHVAC controller18 is not in direct control of the one or more HVAC components, a performance log for cooling may not offer display of the maximum discharge temperature. The performance log also may not display what the internal algorithm considers the maximum delta T that would normally be displayed as the minimum delta T. Finally, if all of the minimum and maximum indoor temperature, minimum and maximum outdoor temperature, minimum and maximum indoor humidity, minimum and maximum outdoor humidity, minimum and maximum discharge temperature, and minimum and maximum delta T information is available, then the results may be displayed in a table. However, if some discharge and delta T information is not to be displayed, then the discharge and delta T values could be displayed separate from the table so that it does not appear that information is missing.
• 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.

Claims (27)

What is claimed is:

1. An HVAC controller for use with an HVAC system including one or more HVAC components, the HVAC controller comprising:

a user interface including a display;

a memory; and

a controller coupled to the user interface and the memory, the controller configured to store performance parameter data related to the performance of the HVAC system in a performance log in the memory of the HVAC controller over a period of time, the controller also configured to receive a first user request via the user interface, and in response to the first user request, retrieve at least some of the performance parameter data from the performance log that corresponds to a first selected subset of the period of time, and to display at least some of the retrieved performance parameter data on the display of the HVAC controller.

2. The HVAC controller ofclaim 1, wherein the performance parameter data includes performance parameter data for one or more different performance parameters.

3. The HVAC controller ofclaim 2, wherein the one or more different performance parameters includes one or more of an indoor temperature value.

4. The HVAC controller ofclaim 2, wherein the one or more different performance parameters includes one or more of an outdoor temperature value.

5. The HVAC controller ofclaim 2, wherein the one or more different performance parameters includes a discharge temperature value of the HVAC system.

6. The HVAC controller ofclaim 2, wherein the one or more different performance parameters includes a delta T value of the HVAC system.

7. The HVAC controller ofclaim 2, wherein the controller stores a minimum value and/or a maximum value over a specified period of time for each of one or more different performance parameters.

8. The HVAC controller ofclaim 1, wherein the performance parameter data includes performance parameter data for one or more different performance parameters for each equipment stage of the HVAC system for a selected mode.

9. The HVAC controller ofclaim 1, wherein the controller is configured to retrieve at least some of the performance parameter data from the performance log that corresponds to a first selected subset of the period of time for a selected equipment stage, and to display at least some of the retrieved performance parameter data for the selected equipment stage on the display of the HVAC controller.

10. The HVAC controller ofclaim 1, wherein the controller is configured to receive a second user request via the user interface, and in response to the second user request, retrieve at least some of the performance parameter data from the performance log that corresponds to a second selected subset of the period of time and to display at least some of the retrieved performance parameter data that corresponds to the second selected subset of the period of time on the display of the HVAC controller, wherein the second selected subset of the period of time is longer than the first subset of the period of time.

11. The HVAC controller ofclaim 10, wherein the second selected subset of the period of time overlaps the first selected subset of the period of time.

12. The HVAC controller ofclaim 11, wherein the first selected subset of the period of time corresponds to an hour, and the second selected subset of the period of time corresponds to a day.

13. The HVAC controller ofclaim 10, wherein the performance parameter data includes performance parameter data for one or more different performance parameters, and wherein:

the controller is configured to display a minimum value and/or a maximum value for one or more of the one or more different performance parameters over the first selected subset of the period of time in response to the first user request; and

the controller is configured to display a minimum value and/or a maximum value for one or more of the one or more different performance parameters over the second selected subset of the period of time in response to the second user request.

14. The HVAC controller ofclaim 13, wherein the first selected subset of the period of time corresponds to an hour, and the second selected subset of the period of time corresponds to a day.

15. The HVAC controller ofclaim 13, wherein the first selected subset of the period of time and the second selected subset of the period of time are selected from a minute, an hour, a day, a week, a month and a year.

16. The HVAC controller ofclaim 10, wherein the controller is further configured to:

receive a third user request via the user interface, and in response to the third user request, retrieve at least some of the performance parameter data from the performance log that corresponds to a third selected subset of the period of time and to display at least some of the retrieved performance parameter data that corresponds to the third selected subset of the period of time on the display of the HVAC controller, wherein the third selected subset of the period of time is longer than the second subset of the period of time; and

receive a fourth user request via the user interface, and in response to the fourth user request, retrieve at least some of the performance parameter data from the performance log that corresponds to a fourth selected subset of the period of time and to display at least some of the retrieved performance parameter data that corresponds to the fourth selected subset of the period of time on the display of the HVAC controller, wherein the fourth selected subset of the period of time is longer than the third subset of the period of time.

17. The HVAC controller ofclaim 1, wherein the controller is configured to receive a second user request via the user interface, and in response to the second user request, retrieve at least some of the performance parameter data from the performance log that corresponds to a second selected subset of the period of time and to display at least some of the retrieved performance parameter data that corresponds to the second selected subset of the period of time on the display of the HVAC controller, wherein the second selected subset of the period of time is shorter than the first subset of the period of time.

18. The HVAC controller ofclaim 2, wherein the controller is configured to dynamically change the format of the display so as to not display labels for at least some performance parameters that do not include corresponding performance parameter data stored in the memory.

19. The HVAC controller ofclaim 2, wherein the controller is configured to display an indicator indicating that performance parameter data for at least one of the performance parameters stored in the performance data log for the first selected subset of the period of time is not available.

20. An HVAC controller for use with an HVAC system including one or more HVAC components, the HVAC controller comprising:

a user interface including a display;

a memory; and

a controller coupled to the user interface and the memory, the controller configured to store performance parameter data related to the performance of the HVAC system in a performance log in the memory of the HVAC controller over a period of time, the controller configured to display performance parameter data retrieved from the performance log that corresponds to a first selected subset of the period of time on the display, the controller configured to receive a user interaction via the user interface, and in response, display on the display performance parameter data that corresponds to a second selected subset of the period of time, wherein the selected subset of the period of time immediately following the first selected subset of the period of time.

21. The HVAC controller ofclaim 20, wherein the first selected subset of the period of time corresponds to a first hour, and the second selected subset of the period of time corresponds to a next succeeding hour.

22. The HVAC controller ofclaim 20, wherein the first selected subset of the period of time corresponds to a first day, and the second selected subset of the period of time corresponds to a next succeeding day.

23. The HVAC controller ofclaim 20, wherein the first selected subset of the period of time corresponds to a first week, and the second selected subset of the period of time corresponds to a next succeeding week.

24. The HVAC controller ofclaim 20, wherein the first selected subset of the period of time corresponds to a first month, and the second selected subset of the period of time corresponds to a next succeeding month.

25. The HVAC controller ofclaim 20, wherein the performance parameter data includes performance parameter data for one or more different performance parameters, and wherein the controller is configured to:

display a minimum value and/or a maximum value for one or more different performance parameters over the first selected subset of the period of time, and

in response to the user interaction, display a minimum value and/or a maximum value for one or more different performance parameters over the second selected subset of the period of time.

26. A method for monitoring an HVAC system, the HVAC system including one or more HVAC components that are controlled, at least in part, by an HVAC controller having a user interface including a display, a memory, and a controller, the method comprising:

storing performance parameter data related to the performance of the HVAC system in a performance log in the memory of the HVAC controller over a period of time;

display a minimum value and/or a maximum value for one or more different performance parameters over a first selected subset of the period of time on the display of the HVAC controller; and

display a minimum value and/or a maximum value for the one or more different performance parameters over a second selected subset of the period of time on the display of the HVAC controller, wherein the selected subset of the period of time is longer than the first selected subset of the period of time.

27. An HVAC controller for use with an HVAC system including one or more HVAC components, the HVAC controller comprising:

a user interface including a display;

a memory;

an input/output block for sending and receiving one or more signals to and from the one or more HVAC components of the HVAC system; and

a controller coupled to the user interface, the memory, and the input/output block, the controller programmed to record data related to a performance of the HVAC system in a performance log stored in the controller memory, the controller programmed to display at least some performance information from the performance log on the display of the HVAC controller, the controller programmed to automatically change a format of the performance information that is displayed on the display based on a current set-up configuration of the HVAC system.

Images