The present invention relates to thermostats and other thermal comfort controllers and particularly to a graphical user interface for such thermal comfort controllers.
Current thermal comfort controllers, or thermostats, have a limited user interface which typically includes a number of data input buttons and a small display. Hereinafter, the term thermostat will be used to reference a general comfort control device and is not to be limiting in any way. For example, in addition to traditional thermostats, the present such control device could be a humidistat or used for venting control. As is well known, thermostats often have setback capabilities which involves a programmed temperature schedule. Such a schedule is made up of a series of time-scheduled set-points. Each set-point includes a desired temperature and a desired time. Once programmed with this temperature schedule, the controller sets-up or sets-back the temperature accordingly. For example, a temperature schedule could be programmed so that in the winter months, a house is warmed to 72 degrees automatically at 6:00 a.m. when the family awakes, cools to 60 degrees during the day while the family is at work and at school, re-warms to 72 degrees at 4:00 p.m. and then cools a final time to 60 degrees after 11:00 p.m., while the family is sleeping. Such a schedule of lower temperatures during off-peak hours saves energy costs.
It is well known that users have difficulty using the current form of a user interface for thermostats because such an interface is not intuitive and is somewhat complicated to use. Therefore, users either do not utilize the energy saving programmable functions of the controller, or they do not change the schedule that is programmed by either the installer or that is the factory default setting.
Another limitation of the current user interfaces for thermostats is that once programmed, the temperature schedule cannot be easily reviewed. Usually, the display is configured to show one set-point at a time in a numerical manner. Using the input buttons, the user must ‘page forward’ to the next set-point in the schedule or ‘page backward’ to the previous set-point.
Although the user can, with difficulty, determine the temperature schedule that is programmed into the controller, the user cannot determine how closely this temperature schedule was followed. Of course, when a new set-point determines that the controller should either raise or lower the temperature in a house or other building, the temperature does not immediately change to that new temperature. It can take some time for the room or building to warm up or cool down to the desired temperature. The thermostat typically tracks this information to allow adjustment to be easily made. At present, the user has no way of viewing this information and no way of correlating the temperature schedule with actual house temperatures.
What is needed in the art is a user interface for a thermostat in which the temperature schedule is more easily programmed. The user interface should display a more user friendly representation of the schedule so that the user can review an entire day's schedule all at once. The user interface should also easily display alternative schedules, such as a weekend and weekday schedule. Further, the graphical representation should itself be the intuitive means to programming the schedule. The user interface should also be able to compare the temperature schedule against the actual historical temperature over a period of time.
This invention can be regarded as a graphical user interface system for thermal comfort controllers. In some embodiments, the user interface system is mounted on the wall as part of a thermostat. In other embodiments, the user interface system is a hand held computing unit which interfaces with a thermostat located elsewhere. The user interface system includes a central processing unit, a memory and a display with a touch-sensitive screen used for input. The memory stores at least one temperature schedule. The temperature schedule has at least one set-point, which associates a desired temperature to a desired time. The display graphically represents the temperature schedule and allows the user to easily and intuitively program the temperature schedule. The temperature schedule may be displayed as a step-function graph, as a listing of set-points, or as a clock and temperature control (such as a dial). In some embodiments, the display can also graphically represent the actual temperature history compared to the desired temperature schedule. In other embodiments, the temperature schedule can be displayed and changed in other graphical ways, such as with slider or scroll bar controls.
Several objects and advantages of the present invention include: the temperature schedule is more easily programmed than in past user interfaces; the step-function or other display is more informative and intuitive; historical data can be displayed to the user; and multiple schedules can be programmed.
The present invention is a user interface system for a thermostat or other comfort controller. Throughout the drawings, an attempt has been made to label corresponding elements with the same reference numbers. The reference numbers include:
Referring to the drawings,
As previously mentioned, the display unit 200 includes a graphical display/touch sensitive screen. This configuration will provide for very flexible graphical display of information along with a very user friendly data input mechanism. The display unit 200 may be very similar to the touch screen display used in a hand-held personal digital assistant (“PDA”), such as a Palm brand PDA manufactured by 3Com, a Jornada brand PDA manufactured by Hewlett Packard, etc. Of course the graphical user interface system could also be manufactured to be integrated with a thermostat itself. In such an embodiment, a touch-sensitive LCD display is coupled with the thermostat's existing central processing unit and RAM.
The temperature schedule data structure 400 and temperature history data structure 500 are data structures configured and maintained within memory 300. For example, the temperature schedule data structure 400 and temperature history data structure 500 could be simple two-dimensional arrays in which a series of times are associated to corresponding temperatures. In
Of course, the temperature schedule data structure 400 and temperature history data structure 500 could also be more advanced data structures capable of organizing more data. For example, the temperature schedule data structure 400 could be configured to allow more than one schedule to be programmed. One schedule could be assigned to run from Monday through Friday while a second schedule could be assigned to run on Saturdays and Sundays. Alternately, different schedules could be assigned for each day of the week. Different schedules could be devised and stored for the summer months and winter months as well.
Temperature history data structure 500 could be configured to store more information, including historical information over a period of several days, weeks, or months. The data could be aggregated to show the average temperatures by time, day, or season. A person skilled in the art of computer programming could readily devise these data structures.
The user interface system also has conduits 800 to the heating/cooling devices or thermostats thereof so that user interface system can communicate with the thermostat or other comfort controller.
The display unit 200 can also be configured with additional controls 230, which could, for example, switch the display between Fahrenheit and Celsius for the temperature, between standard and military time, and between showing a single day's schedule versus showing a week's schedule. In addition to the controls programmed and displayed on display unit 200, physical buttons of the thermostat 235 could be programmed to be used for working with the user interface system as well. This is similar to the operation of a PDA.
The graphical representations, controls and other data that are displayed on display unit 200 is accomplished by a computer program stored in memory 300. The computer program could be written in any computer language. Possible computer languages to use include C, Java, and Visual Basic.
The operation of the user interface system is more intuitive than previous user interfaces for other thermal comfort controllers. The various set-points 600 can displayed on the display unit 200 in a graphical format 215, such as in a step-function, bar chart, etc. In the step-function embodiment, which is shown in
In some embodiments, the buttons 235 or additional controls 230 can be configured so that the user can perform additional programming. For example, one of the buttons 235 or additional controls 230 might cause an alternate schedule to be displayed—such as one for the weekend—which the user can program. Or, pressing one of the buttons 235 or additional controls 230 might cause the temperature history 500 to be displayed by the display unit 200.
In other embodiments of the present invention, the temperature schedule 215 could be displayed in other formats. Again, the step-function shown in
There are many ways in which the user interface system can work with the thermal comfort controller. The user interface system would probably be integrated into a thermal comfort control system and installed on a wall much like current programmable thermostats. However, if the user interface system is configured on a hand-held PDA, the user-interface could communicate with the thermal comfort controller via the PDA's infra-red sensor. Or, the PDA could be synchronized with a personal computer and the personal computer could set the appropriate instructions to the thermal comfort controller. Or, the PDA could use a cellular/mobile phone feature to telephone the controller (i.e., thermostat, personal computer, etc.) to exchange pertinent and relevant data.
From the foregoing detailed description, it will be evident that there are a number of changes, adaptations and modifications of the present invention which come within the province of those skilled in the art. However, it is intended that all such variations not departing from the spirit of the invention be considered as within the scope thereof.
This application is a continuation of prior U.S. application Ser. No. 09/697,633, filed Oct. 26, 2000, now U.S. Pat. No. 6,595,430.
Number | Name | Date | Kind |
---|---|---|---|
4224615 | Penz | Sep 1980 | A |
4314665 | Levine | Feb 1982 | A |
4401262 | Adams et al. | Aug 1983 | A |
4914568 | Kodosky et al. | Apr 1990 | A |
4948040 | Kobayashi et al. | Aug 1990 | A |
5086385 | Launey et al. | Feb 1992 | A |
5170935 | Federspiel et al. | Dec 1992 | A |
5289362 | Liebl et al. | Feb 1994 | A |
5782296 | Mehta | Jul 1998 | A |
5818428 | Eisenbrandt et al. | Oct 1998 | A |
5873519 | Beilfuss | Feb 1999 | A |
5886697 | Naughton et al. | Mar 1999 | A |
5947372 | Tiernan | Sep 1999 | A |
6020881 | Naughton et al. | Feb 2000 | A |
6059195 | Adams et al. | May 2000 | A |
6140987 | Stein et al. | Oct 2000 | A |
6192282 | Smith et al. | Feb 2001 | B1 |
6259074 | Brunner et al. | Jul 2001 | B1 |
6285912 | Ellison et al. | Sep 2001 | B1 |
6290140 | Pesko et al. | Sep 2001 | B1 |
6330806 | Beaverson et al. | Dec 2001 | B1 |
6344861 | Naughton et al. | Feb 2002 | B1 |
6398118 | Rosen et al. | Jun 2002 | B1 |
6478233 | Shah | Nov 2002 | B1 |
6483906 | Iggulden et al. | Nov 2002 | B1 |
6578770 | Rosen | Jun 2003 | B1 |
6580950 | Johnson et al. | Jun 2003 | B1 |
6581846 | Rosen | Jun 2003 | B1 |
6595430 | Shah | Jul 2003 | B1 |
6619555 | Rosen | Sep 2003 | B2 |
6621507 | Shah | Sep 2003 | B1 |
6786421 | Rosen | Sep 2004 | B2 |
20010029585 | Simon et al. | Oct 2001 | A1 |
20010042684 | Essalik et al. | Nov 2001 | A1 |
20010052459 | Essalik et al. | Dec 2001 | A1 |
20020092779 | Essalik et al. | Jul 2002 | A1 |
20030142121 | Rosen | Jul 2003 | A1 |
20030150926 | Rosen | Aug 2003 | A1 |
20030150927 | Rosen | Aug 2003 | A1 |
20040074978 | Rosen | Apr 2004 | A1 |
20040245352 | Smith | Dec 2004 | A1 |
Number | Date | Country |
---|---|---|
3334117.6 | Apr 1985 | DE |
3334177 | Apr 1985 | DE |
29600654 | Mar 1996 | DE |
0 434 926 | Jul 1991 | EP |
0678204 | Mar 2000 | EP |
0985994 | Mar 2000 | EP |
0985994 | Mar 2000 | EP |
1074009 | Jul 2001 | EP |
WO 9711448 | Mar 1997 | WO |
WO 9739392 | Oct 1997 | WO |
WO9739392 | Oct 1997 | WO |
WO 0152515 | Jul 2001 | WO |
WO 0179952 | Oct 2001 | WO |
Number | Date | Country | |
---|---|---|---|
20030208282 A1 | Nov 2003 | US | |
20070198099 A9 | Aug 2007 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 09697633 | Oct 2000 | US |
Child | 10453027 | US |