The present invention relates generally to the field of programmable controllers for homes and/or buildings are their related grounds. More specifically, the present invention relates to simplified interfaces for such controllers having multiple-day programming capabilities.
Controllers are used on a wide variety of devices and systems for controlling various functions in homes and/or buildings and their related grounds. Some controllers have schedule programming that modifies device parameters such as set points as a function of date and/or time. Some such device or system controllers that utilize schedule programming for controlling various functions in homes and/or buildings and their related grounds include, for example, HVAC controllers, water heater controllers, water softener controllers, security system controllers, lawn sprinkler controllers, and lighting system controllers.
In a typical HVAC application, for example, such controllers can be employed to monitor and, if necessary, control various environmental conditions occurring within a home or office building. The controller may include a microprocessor that interacts with other components in the system to regulate the temperature, humidity, venting, and/or air quality occurring at one or more locations. An internal sensor located within the controller and/or one or more remote sensors may be employed to sense when the temperature and/or humidity level reaches a certain threshold level, causing the controller to send a signal to activate or deactivate one or more components in the system.
The controller may be equipped with a user interface that allows the user to monitor and adjust various parameters of the controller. With more modern designs, the user interface typically comprises a liquid crystal display (LCD) or light emitting diode (LED) display inset within a controller housing that contains a microprocessor or the like, an I/O interface, and other components of the controller. The user interface may include a menu-driven interface that allows the user to scroll through one or more menus or screens to adjust the different settings on the controller. In some cases, a program within the controller prompts the user at each menu or screen to input various commands into the interface to adjust the controller settings.
In certain designs, the user interface can be configured to permit the user to program the controller to run on a certain schedule. For example, the controller can include a scheduling routine that allows the user to adjust the heat and cool set points for one or more periods during a particular day in order to conserve energy. Once the parameters for that day have been programmed, the user can then repeat the process to change the settings for the other remaining days. With some designs, the controller may include a feature that allows the user to program a separate schedule for weekday and weekend use, or to copy settings for a particular day and apply those settings towards other days of the week.
Interaction with the user interface can often prove difficult, discouraging many users from attempting to program the controller to run on a schedule. While some modern controllers allow the user to copy settings from one day to another, the number of steps typically required to program the controller are often deemed too complex or time consuming. In some cases, the user interface may not allow the user to select multiple days outside of the normal weekday/weekend scheme. Accordingly, there is an ongoing need in the art to decrease the time and complexity associated with programming a controller to run a multiple-day schedule.
The present invention pertains to simplified interfaces for controllers having multiple-day programming capabilities. In one illustrative embodiment, a method of programming a multiple-day schedule in a controller equipped with a user interface can include the steps of entering a scheduling routine, selecting multiple days for schedule modification, changing the schedule parameters for one or more periods during the selected days, and then exiting the scheduling routine. The user may select or de-select days of the week to be modified at any point within the scheduling routine, including at certain pre-selected times. In some embodiments, the controller can be programmed to run the schedule for any day or combination of days, as desired by the user.
The controller may include a user interface that can be used for both displaying and modifying various parameters within the controller. For example, the user interface can include a touch screen, display panel/keypad, or any other suitable device adapted to transmit various commands to and from the controller. A number of mechanical and/or soft buttons (e.g. variable function, software configured) may be configured to accept input commands from the user. In certain embodiments, the user interface can include a menu-driven interface that allows the user to navigate through one or more menus or screens to modify various operational settings within the controller. The menu-driven interface may include a number of icons (e.g. descriptive buttons) prompting the user to input various commands with, for example, the touch screen or keypad. Using the interface, the user can program the controller to run a particular schedule for one or more days without having to copy the settings from one particular day and then apply those settings to other days of the week.
The following description should be read with reference to the drawings, in which like elements in different drawings are numbered in like fashion. The drawings, which are not necessarily to scale, depict illustrative embodiments and are not intended to limit the scope of the invention. Although examples of various programming and operational steps are illustrated in the various views, those skilled in the art will recognize that many of the examples provided have suitable alternatives that can be utilized. While the various devices, systems and methods illustrated herein are described specifically with respect to HVAC controllers, it should be understood that the present invention can be employed in other applications where multiple-day schedules are implemented, including, for example, water heater systems, water softener systems, security systems, lighting systems, sprinkler or drip water systems, audio/video (A/V) systems, etc.
Referring now to
Within each period, the controller can include various event time and set point parameters that can be utilized to regulate various environmental conditions within a particular space. In certain embodiments, for example, the controller may include a heat set point parameter and cool set point parameter that can be utilized to regulate the amount of heating and/or cooling occurring within the home. The controller may further include a fan mode parameter that can be set to operate the fan in a particular manner during each period. For example, the controller can be configured to operate the fan constantly during each selected period (i.e. an “On Mode”), or automatically as needed (i.e. an “Auto Mode”) during each selected period. Other parameters such as the ventilation, humidity level, frost level, air quality, etc. may also be regulated via the controller, as desired. The particular parameter(s) regulated by the controller will, of course, vary depending on the type of system in which the device is employed.
From a normal controller operation mode indicated generally by block 12, the user may initialize a scheduling routine within the controller that allows the user to view the current schedule parameters stored in memory, and, if desired, modify one or more of the parameters to create a new schedule. To initialize the scheduling routine, the user may send a request to the controller via the user interface, causing the controller to initiate a schedule review mode that displays the current settings on the user interface. Initialization of the schedule review mode may occur, for example, when the user presses a button on a touch screen or keypad, speaks a command, or otherwise sends a signal to the controller.
When the schedule review mode is initiated, the controller can be configured to display the current day and period settings for the schedule on the user interface, as indicated generally by block 14. For example, if the current time and day is 7:00 AM on Wednesday, the controller can be configured to display the “wake” period parameters for Wednesday upon initiating the schedule review mode.
To view other selected days and/or periods within the current schedule, the user may select each day and/or period, causing the controller to display the parameters for the selected day and/or period on the user interface, as indicated generally by block 16. The user can select each day individually within the schedule review mode to view the schedule parameters for each period without modification. If, for example, the user is currently viewing the schedule parameters for Wednesday during the “wake” period, the user can select other individual days of the week (e.g. Tuesday) to view the schedule parameters for that day's “wake” period. Within each individual day selected, the user can select each period to display the parameters scheduled to occur for that day. At any point during the schedule review mode, the user can send a signal to the controller to terminate the scheduling routine and return to the normal controller operation mode indicated by block 12.
In one illustrative embodiment, the user can modify one or more of the schedule parameters by initiating an editing mode within the controller. The user can initiate the editing mode by, for example, pressing an “edit” button on a touch screen, keypad or other input device, sending a signal to the controller to initiate the editing mode.
Upon initiation of the editing mode, the user interface can be configured to display a message that prompts the user to select the day or days that are to be modified in the schedule. As indicated by block 18, for example, the controller can be configured to display the message “OK TO PICK MULTIPLE DAYS” or other similar text or graphic on the user interface, prompting the user to select those days in the schedule to modify. The user can then select each day that is to be modified within the schedule, as desired.
As the first day is selected, the various periods in the schedule are then displayed on the user interface, as indicated generally by block 20. At this step, the user may select one or more days during the week to modify the schedule. For example, the user may select to run the schedule on alternating days of the week, during only the weekdays or weekends, or any other desired combination. The controller can be configured to notify the user of each day or combination of days selected using, for example, a check mark, blinking text, and/or other suitable indicator on the user interface.
The controller can be configured to default to one of the periods upon selecting the first day, displaying the schedule parameters for that particular day and period on the user interface. For example, if the user selects Monday as the first day to modify in the schedule, the controller can be configured to display the parameters for the “wake” period on the user interface. In certain embodiments, the controller can be configured to default to the period last modified in the schedule, or to the period following the last period modified in the schedule. In other embodiments, all periods for the selected day may be displayed.
Once the user has selected one or more days to be modified in the schedule, the controller can be configured to display the schedule parameters scheduled for each individual period, as indicated generally by block 22. The user can then modify one or more of the parameters for each selected period, as desired, causing the controller to display the new parameters on the user interface, as indicated generally by block 24.
To modify the schedule parameters for other periods, the user can select each desired period individually, and then repeat the process again until all desired periods have been modified in the schedule. In some cases, the user can select more than one period at once in order to simultaneously modify at least some of the parameters, such as the set points, at the selected periods and across the selected days. At any time during this process, the user may select or deselect one or more days of the week to include/exclude the modified parameters. For example, if the user decides after initially modifying the schedule parameters for one or more periods of selected days of the week, the user may select an additional day to include the modified schedule parameters. If desired, the user may choose to cancel the modified parameters by hitting a “cancel” button or other similar command on the user interface, causing the controller to terminate the schedule routine, discard the modified parameters, and return to the normal controller operation mode indicated by block 12.
The process of selecting the parameters for each period can be easily applied to one or more selected days during the week without having to first copy settings from one particular day, and then apply those settings to other selected days. For example, if the user has previously selected only Monday and Wednesday, but later decides to add Friday to the schedule, the user can send a signal to the controller to select Friday at any step during the editing routine to apply the modified schedule parameters for Friday. Since days can be easily selected or de-selected via the user interface, the user is not required to copy the settings for a particular day, and then apply those settings for the other days. Moreover, since the user can select any day or combination of days via the user interface, greater flexibility is provided to create a customized schedule.
After the user has finished modifying the schedule, the user can send a signal to the controller to either save or discard the modified settings. As indicated generally by block 26, the controller can be configured to display the text “Saving Changes” or other similar message on the user interface to notify the user that the controller has saved the modified schedule parameters. Once the modified schedule parameters have been either saved or cancelled, the controller can be configured to terminate the scheduling routine and revert to the normal controller operation mode indicated by block 12. Alternatively, and as shown by dashed line 28, the controller may revert back to, for example, block 18 to allow the user to select another day or set of days, as desired. Once saved, the controller can be configured to automatically run the modified schedule.
In one illustrative embodiment, the user can modify one or more of the schedule parameters by initiating an editing mode within the controller. The user can initiate the editing mode by, for example, pressing an “edit” button on a touch screen, keypad or other input device, sending a signal to the controller to initiate the editing mode.
Upon initiation of the editing mode, the user interface can be configured to display a message that prompts the user to select one or more days and/or one or more periods that can be modified in the schedule. As indicated by block 38, for example, the controller can be configured to display the message “OK TO PICK ONE OR MORE PERIODS AND/OR DAYS” or other similar text or graphic on the user interface, prompting the user to user to select one more days and/or periods to be modified within the schedule, as desired.
As the first period and/or day is selected, the various period(s) and/or day(s) to be modified are then displayed on the user interface, as indicated generally by block 40. At this step, the user may select any combination of days and/or periods to modify the schedule, as desired. For example, the user may select to run the schedule on multiple days for a certain period, for a single day with multiple periods, or for multiple days with multiple periods for each selected day. The controller can be configured to notify the user of each day and/or period selected using, for example, a check mark, blinking text, and/or other suitable indicator on the user interface.
Once the user has selected one or more periods and/or days to be modified in the schedule, the controller can be configured to display the schedule parameters scheduled for the selected period(s) and/or day(s), as indicated generally by block 42. The user can then modify one or more of the schedule parameters, as desired, causing the controller to display the new parameters on the user interface, as indicated generally by block 44. At any time during this process, the user may select or de-select one or more periods and/or days of the week to run the schedule without modifying the schedule parameters. If desired, the user may choose to cancel the modified parameters by hitting a “cancel” button or other similar command on the user interface, causing the controller to terminate the scheduling routine, discard the modified parameters, and return to the normal controller operation mode indicated by block 32.
Once the user has finished modifying the schedule, the user can send a signal to the controller to save the modified settings, as indicated generally by block 46. In certain embodiments, the controller can be configured to display the text “Saving Changes” or other similar message on the user interface to notify the user that the controller has saved the modified schedule parameters. Once the modified schedule parameters have been either saved or cancelled, the controller can be configured to terminate the scheduling routine and revert to the normal controller operation mode indicated by block 32. Alternatively, and as shown by dashed line 48, the controller may revert back to, for example, block 38 to allow the user to select one or more additional periods and/or days, as desired. Once saved, the controller can be configured to automatically run the modified schedule.
The controller 52 can be equipped with a user interface 66 that can be used to transmit signals to and from the controller 52. The user interface 66 can include a touch screen, LCD panel and keypad, dot matrix display, computer (e.g. a PDA), or any other suitable device for sending and receiving signals to and from the controller 52. In certain embodiments, the user interface 66 may include a menu-driven interface that allows the user to cycle through one or more menus or screens to view and, if desired, modify various operational settings within the controller 52. For example, the controller 52 can be pre-programmed to run separate routines for adjusting the current temperature or humidity levels, changing the clock or date settings on the controller 52, setting a vacation mode on the controller 52 that can be run while the user is away, or checking the status of the various system components connected to the controller 52. The menus or screens corresponding to a particular routine can be organized from general to more specific, providing the user with only pertinent information at each step within the routine.
In the illustrative embodiment, the controller 68 is configured to display a current inside temperature parameter 78 (in either ° F. or ° C.), a current outside temperature parameter 80 (in either ° F. or ° C.), a time of day parameter 82, and a day of week parameter 84 on the touch screen 72. The current heat/cool set point parameter 86 may also be displayed on the touch screen 72, indicating the temperature at which the controller 68 is currently set to maintain. An alphanumeric message 88 displayed on the touch screen 72 may be provided to inform the user whether the controller 68 is currently following the schedule.
A set of up/down buttons 90 displayed on the touch screen 72 can be pressed, if desired, to temporarily change the current heat/cool set point parameter 86 to a setting different from that contained in the schedule. A fan mode button 92 and system mode button 94 displayed on the touch screen 72 allow the user to view and, if desired, modify the fan and system settings. For example, and in the illustrative embodiment, the fan mode button 92 can be pressed repeatedly to cycle the fan between an “On Mode”, “Auto Mode”, and other modes as desired, allowing the user to control the operation of the fan. In similar fashion, the system mode button 94 can be pressed repeatedly to cycle the controller 68 through various heating and cooling modes, as desired.
A “SCHED” button 96 located on the main menu screen 76 can used to initialize a scheduling routine within the controller 68 to modify one or more parameters within the current schedule. When the “SCHED” button 96 is pressed, the controller 68 can be configured to initiate a schedule review mode, causing the controller 68 to access the current schedule parameters and display them on the touch screen 72. As shown in
In the illustrative embodiment, a series of buttons 104 located on the top of the touch screen 72 correspond to the days of the week, and can be pressed to send a signal to the controller 68 to display the schedule parameters for each individual day in the schedule. An icon, blinking text or other suitable indicator for informing the user the current day selected may be displayed on the touch screen 72. For example, in the pictorial view illustrated in
The controller 68 can be configured to default to the current day of the week when the schedule review mode is initiated. For example, if the current time and day is 7:00 AM on Wednesday, the controller 68 can be configured to display the “wake” period parameters for Wednesday on the touch screen 72. To view the schedule parameters for other days of the week, the user may press the appropriate day button 104 on the touch screen 72, causing the controller 68 to display the corresponding parameters for that selected day.
Within each selected day, the user may press one or more period buttons on the touch screen 72, causing the controller 68 to display the parameters scheduled for that day. The touch screen 72 may include, for example, a “WAKE” button 108, a “LEAVE” button 110, a “RETURN” button 112, and a “SLEEP” button 114 that correspond to a separate “wake” period, “leave” period, “return” period, and “sleep” period programmed in the controller 68. In the pictorial view depicted in
While four periods are specifically illustrated in
Once the user has finished viewing the desired schedule parameters for each day and/or period, the user can terminate the schedule review mode by pressing a “DONE” button 116 or “CANCEL” button 118 displayed on the touch screen 72, causing the controller 68 to terminate the scheduling routine and return to the main menu screen 76 of
To modify one or more parameters in the schedule, the user can initiate an editing mode within the controller 68 by pressing an “EDIT” button 120 on the touch screen 72. As shown in
The controller 68 can be configured to indicate the particular period the user is viewing on the touch screen 72 using an icon, blinking text or other indicator means. In
If the user desires to modify one or more of schedule parameters for the selected period, the user may use the appropriate set of up/down buttons 124,126,128 to modify the parameter. As shown in
To display the parameters for the other periods, the user may press the appropriate period button on the bottom of the touch screen 72, causing the controller 68 to display the schedule parameters for that selected period. To display the settings for the “leave” period, for example, the user may press the “LEAVE” button 110 on the touch screen 72, causing the controller 68 to display the event time parameter 98, heat set point parameter 100, and cool set point parameter 102 for the “leave” period on the touch screen 72, as shown in
In the illustrative embodiment, the user may select or de-select one or more days at any point during the editing mode using the appropriate day button(s) 104 located on the touch screen 72. In the illustrative view of
If the user desires to cancel a particular period from the schedule, the user can select the appropriate period button 108,110,112,114 and then press a “CANCEL PERIOD” button 130 on the touch screen 72. As shown in
After the user has finished modifying the schedule, the user can press either the “DONE” button 116 to save the modified parameters in the schedule, or the “CANCEL” button 118 to discard the modified changes without saving. As shown in
To initialize the scheduling routine within the controller 136, the user may press the button 158 located immediately below the text “SCHEDULE” located on the display panel 140. When pressed, the controller 136 can be configured to initiate a schedule review mode, causing the display panel 140 to display each day of the week, as shown in
To modify one or more parameters in the schedule, the user can initiate an editing mode within the controller 136. The user can modify the schedule either individually on a day-by-day basis from within the schedule review mode, or directly via the screen illustrated in
To edit the parameters on a day-by-day basis, the user, while within the schedule review mode, may select the individual day of the week to modify, and then press button 158 located below the text “Edit” located on the display panel 140 (see
The controller 136 can be configured to prompt the user to cycle through the various schedule parameters for each period by blinking the text for the selected schedule parameter on the display panel 140. For example, the event time parameter 162 in
To change the other parameters for that selected period, the user can press button 158 located immediately below the text “Next Step” on the display panel 140, causing the controller 136 to cycle to the next schedule parameter in that period. As the user cycles through each schedule parameter, the controller 136 can be configured to blink the appropriate text on the display panel 140, as shown in
To select multiple days to program at once in the illustrative embodiment, the user can initiate the editing mode directly from the screen depicted in
Once the user has selected the desired day or days to modify the schedule, the user can then press the “Next Step” button 158, causing the controller 136 to display the schedule parameters for one period. As shown in
When the user has cycled through each of the parameters for a particular period, the user may press button 158 again, causing the controller 136 to cycle to the next period in the schedule. The process of selecting and modifying the parameters can then be repeated, as desired, until all of the parameters for each period have been selected and modified (if desired). At any point during this process, the user can save the modified settings by pressing button 160 located under the text “Done” on the display panel 140, causing the controller 136 to save the modified schedule parameters.
As shown in
In some embodiments, the user interface 182 may also allow a user to select certain days (and/or period—e.g. Wake, Leave, Return, Sleep), as generally shown at 190. When so provided, the HVAC controller may search through the set points on the selected days (and/or periods) of the schedule 180, and replace those set points that have the current value with the new set point value.
In the example shown, and referring to user interface 182, the user has selected a current set point value of 70 degrees via current set point selection box 184, a new set point value of 72 degrees via new set point selection box 186, and days Tuesday, Wednesday, Thursday and Friday via days selection boxes generally shown at 190. In response, the HVAC controller may replace all set points on Tuesday, Wednesday, Thursday and Friday of the schedule 180 that have a value of 70 degrees with a new value of 72 degrees, regardless of the period (e.g. Wake, Leave, Return and Sleep periods). The set points to be updated to 72 degrees in this example are highlighted with a circle in the schedule 180. As noted above, and in some embodiments, the user interface 182 may allow a user to select one or more periods (e.g. Wake, Leave, Return and Sleep periods) rather than days, or in addition to days, as desired. In any event, the illustrative embodiment of
In this illustrative embodiment, the set points in the schedule 200 are set to a tag or pointer value, rather than a temperature value. For example, the set points in the schedule 200 are set to tag or pointer value of High “H”, Medium “M” or Low “L”, corresponding to a high set point value, a medium set point value and a low set point value, respectively. A user interface, such as user interface 202, may then be used to assign and/or change a temperature value that is associated with each tag or pointer value. In the illustrative user interface 202 of
By using a tag or point value, rather than a temperature value for the set points in the schedule 200, the user may more easily change a set point across the schedule. For example, in the illustrative embodiment, by changing the value assigned to the High “H” heat set point 206 from 73 degrees to 75 degrees, all of the heat set points with a tag or pointer value of high “H” may be changed across the schedule 200. This may help reduce or eliminate the need to scroll through each day and/or period of the schedule, and make individual changes to the set points.
In some cases, it may be desirable to display some, many or all of the parameters of a schedule on a single or limited number of screens. This may help a user to get a more complete picture of the schedule without having to traverse many different display screens.
The illustrative display 250 also shows a number of day columns. Only a Monday column 260 and part of a Tuesday column 262 are shown on the illustrative display 250. However, in the illustrative embodiment, the schedule may also include day columns for the other days of the week. A number of schedule parameters are shown under each day column. For example, the Monday column 260 includes a “time” column 264 that shows the time that the corresponding schedule period begins, an “H” column 266 that shows the heat set point for the corresponding schedule period, a “C” column 268 that shows the cool set point for the corresponding schedule period, and a “FAN” column 270 that shows the fan mode for the corresponding schedule period. In the illustrative embodiment, the day columns for the other days of the week (not shown) may include the same or similar schedule parameter columns, if desired. It should be recognized that these schedule parameter columns are only illustrative, and that different programmed schedule parameters may be used as desired.
In one illustrative embodiment, the display 250 allows the user may scroll or pan across the controller schedule using scroll or pan buttons 280 and 282. For example, the user may press the right scroll or pan button 282 to move the display in a rightward direction relative to the controller schedule to display, for example, the rest of the Tuesday day column 262. When this occurs, some or all of the Monday day column 260 may fall off the left of the display and no longer be displayed. The user may again press the right scroll or pan button 282 to display all or part of the Wednesday day column (not shown). This may be repeated to view the entire schedule of the controller. At any time, the user may press the scroll or pan button 280 to scroll or pan back through the schedule in a leftward direction, as desired. The amount that the display travels relative to the controller schedule with each push of the scroll or pan buttons 280 and 282 may depend on the application, and in some cases, set by the user. For example, the display may travel a portion of a day column, an entire day column, or more than one day column with each push of the scroll or pan buttons 280 and 282.
In some embodiments, part of the display may remain stationary as the scroll or pan buttons 280 and 282 are pressed. For example, the “Wake”, “Leave”, “Return” and “Sleep” designators shown at 252, 254, 256 and 258 may remain stationary on the display 250. Likewise, the scroll or pan buttons 280 and 282 may remain stationary, as well as other control buttons, as desired.
In some embodiments, the user may select a particular parameter or set of parameters for modification. In the illustrative embodiment, the user may select, for example, the heat set point 290 for the wake period on Monday. The user may select the particular parameter in any number of ways. For example, if the display 250 is a touch screen, the user may simply touch the particular parameter. If the display 250 is not a touch screen, one or more navigation buttons (not shown) may be used to traverse and select various parameters of the schedule. Once selected, the user may edit the parameter, if desired. For example, and in the illustrative embodiment, the user may press the edit button 292 to enter an edit mode. Then, one or more up/down buttons (not shown) or the like may be used to change the value of the selected schedule parameter.
The schedule may appear to be one continuous schedule extending from Monday through Sunday, with the display 250 appearing as a “window” that displays only a portion of the schedule. The scroll or pan buttons 280 and 282 may be used to move the display “window” across the schedule. It is believed that this may provide an intuitive interface that may help a user can get a more complete picture of the schedule without having to traverse many different display screens.
To view additional schedule parameters, and in the illustrative embodiment, the user may select a particular schedule period and day. For example, and in
In some embodiments, the user may select a particular schedule parameter in the pop-up window 304 for editing. For example, the user may select the Wake Start Time 306 for editing. Once selected, the user may change the value of the Wake Start Time, as desired. Again, it is believed that this may provide an intuitive interface that may help a user get a more complete picture of the schedule without having to traverse many different display screens.
Each of the seven days of a week is shown along the left of the graph. While seven days are shown, it is contemplated that fewer or more days may be provided, or groups of days, or other time periods, may be provided depending on use. Each of the seven days includes a line graph that indicates when each of a number of schedule time periods begins. In the illustrative embodiment, “wake”, “leave”, “return” and “sleep” time periods are available for each day. However, it should be recognized that other schedule time periods may be used, if desired.
Referring the line graph 330 for Monday, the “sleep” time period begins at 12:00 AM as indicated at 330a, the “wake” time period begins at 4:00 AM as indicated at 330b, the “leave” time period begins at 8:00 AM as indicated at 330c and the “return” time period begins at 6:00 PM as indicated at 330d. In the illustrative embodiment, the height of the line graph only indicates a relative temperature (e.g. comfort temperature versus energy saving temperature), and does not indicate an actual temperature set point. Instead, the heat set point, fan setting, and other parameters may be shown adjacent to the line graph in each or selected schedule periods. For example, and in the illustrative embodiment, designations “68” “A” are provided adjacent to the line graph during the “sleep” period. The designation “68” indicates that the heat set point is set to 68 degrees, and the designation “A” indicates that the fan mode is set to AUTO. Similar designations may be provided for the “wake”, “leave” and “return” schedule time periods, as shown. Although not explicitly shown, cool set points and/or other schedule parameters may be provided on the display. Also, in some embodiments, the height of the line graph may provide a measure of, for example, a set point temperature. That is, the horizontal lines of the line graph 330 may be positioned along a vertical temperature scale provided for line graph 330 so that the vertical position of each horizontal segment provides an indication of the heat set point or some other schedule parameter of the schedule. Alternatively, or in addition, the color of graph segments may provide an indication of the value of the schedule parameter (e.g. set point temperature). It is believed that this embodiment may also provide an intuitive interface that may help a user get a more complete picture of the schedule without having to traverse many different display screens.
Each of the seven days of a week is shown along the left of the graph. While seven days are shown, it is contemplated that fewer or more days may be provided, or groups of days, or other time periods, may be provided depending on use. In the illustrative embodiment, each of the seven days includes two linear line graphs, each having a number of segments. The upper linear line graph corresponds to the programmed cool set point, and the lower linear line graph corresponds to the programmed heat set point. A fan setting indicator is shown between the two linear line graphs. While two linear graphs for each day are shown in
In the illustrative embodiment, each linear line graph includes a number of line segments. Each line segment corresponds to a schedule time period. For example, a first segment may correspond to a “sleep” time period. A second, a third and a fourth segment may correspond to a “wake”, a “leave”, and a “return” time period, respectively. As noted above, it should be recognized that other schedule time periods may be used, if desired. If the start time of a particular schedule time period is changed, the length and position of the corresponding line segment(s) may also change to correspond to the changed start time.
As shown in
Having thus described the several embodiments of the present invention, those of skill in the art will readily appreciate that other embodiments may be made and used which fall within the scope of the claims attached hereto. Numerous advantages of the invention covered by this document have been set forth in the foregoing description. It will be understood that this disclosure is, in many respects, only illustrative. Changes can be made with respect to various elements described herein without exceeding the scope of the invention.
This is a continuation of co-pending U.S. patent application Ser. No. 12/978,903, filed Dec. 27, 2010, entitled “CONTROLLER INTERFACE WITH MULTIPLE DAY PROGRAMMING”, which is a continuation of U.S. patent application Ser. No. 12/700,656, filed Feb. 4, 2010, entitled “CONTROLLER INTERFACE WITH MULTIPLE DAY PROGRAMMING”, now U.S. Pat. No. 7,890,195, which is a continuation of U.S. patent application Ser. No. 11/532,355, filed Sep. 15, 2006, entitled “CONTROLLER INTERFACE WITH MULTIPLE DAY PROGRAMMING”, now U.S. Pat. No. 7,693,582, which is a continuation of U.S. patent application Ser. No. 10/726,201, filed Dec. 2, 2003, entitled “CONTROLLER INTERFACE WITH MULTIPLE DAY PROGRAMMING”, now U.S. Pat. No. 7,114,554.
Number | Name | Date | Kind |
---|---|---|---|
3656112 | Paul | Apr 1972 | A |
3900842 | Calabro et al. | Aug 1975 | A |
4079366 | Wong | Mar 1978 | A |
4174807 | Smith et al. | Nov 1979 | A |
4206872 | Levine | Jun 1980 | A |
4215408 | Games et al. | Jul 1980 | A |
4224615 | Penz | Sep 1980 | A |
4235368 | Neel | Nov 1980 | A |
4264034 | Hyltin et al. | Apr 1981 | A |
4267966 | Neel et al. | May 1981 | A |
4270573 | Sturman et al. | Jun 1981 | A |
4296334 | Wong | Oct 1981 | A |
4298946 | Hartsell et al. | Nov 1981 | A |
4308991 | Peinetti et al. | Jan 1982 | A |
4337822 | Hyltin et al. | Jul 1982 | A |
4357665 | Korff | Nov 1982 | A |
4382544 | Stewart | May 1983 | A |
4386649 | Hines et al. | Jun 1983 | A |
4388692 | Jones et al. | Jun 1983 | A |
4399510 | Hicks | Aug 1983 | A |
4429299 | Kabat et al. | Jan 1984 | A |
4431134 | Hendricks et al. | Feb 1984 | A |
4442972 | Sahay et al. | Apr 1984 | A |
4446913 | Krocker | May 1984 | A |
4479604 | Didner | Oct 1984 | A |
4506827 | Jamieson et al. | Mar 1985 | A |
4510398 | Culp et al. | Apr 1985 | A |
4511979 | Amirante | Apr 1985 | A |
4551812 | Gurr et al. | Nov 1985 | A |
4556865 | Fukugawa et al. | Dec 1985 | A |
4591988 | Kima et al. | May 1986 | A |
4606401 | Levine et al. | Aug 1986 | A |
4608560 | Allgood | Aug 1986 | A |
4621336 | Brown | Nov 1986 | A |
4622544 | Bially et al. | Nov 1986 | A |
4630670 | Wellman et al. | Dec 1986 | A |
4642607 | Strom et al. | Feb 1987 | A |
4656835 | Kiddler | Apr 1987 | A |
4657179 | Aggers et al. | Apr 1987 | A |
4717333 | Carignan | Jan 1988 | A |
4725001 | Carney et al. | Feb 1988 | A |
4730941 | Levine et al. | Mar 1988 | A |
4742475 | Kaiser et al. | May 1988 | A |
4771185 | Feron et al. | Sep 1988 | A |
4783800 | Levine | Nov 1988 | A |
4819714 | Otsuka et al. | Apr 1989 | A |
4837731 | Levine et al. | Jun 1989 | A |
4881686 | Mehta | Nov 1989 | A |
4909041 | Jones | Mar 1990 | A |
4916328 | Culp, III | Apr 1990 | A |
4918439 | Wozniak et al. | Apr 1990 | A |
4924404 | Reinke, Jr. | May 1990 | A |
4948040 | Kobayashi et al. | Aug 1990 | A |
4992779 | Sugino et al. | Feb 1991 | A |
4997029 | Otsuka et al. | Mar 1991 | A |
5003457 | Ikei et al. | Mar 1991 | A |
5012973 | Dick et al. | May 1991 | A |
5038851 | Mehta | Aug 1991 | A |
5053752 | Epstein et al. | Oct 1991 | A |
5065813 | Berkeley et al. | Nov 1991 | A |
5086385 | Launey et al. | Feb 1992 | A |
5088645 | Bell | Feb 1992 | A |
5107918 | McFarlane et al. | Apr 1992 | A |
5140310 | DeLuca et al. | Aug 1992 | A |
5153837 | Shaffer et al. | Oct 1992 | A |
5161606 | Berkeley et al. | Nov 1992 | A |
5170935 | Federspiel et al. | Dec 1992 | A |
5181653 | Foster et al. | Jan 1993 | A |
5230482 | Ratz et al. | Jul 1993 | A |
5238184 | Adams | Aug 1993 | A |
5251813 | Kniepkamp | Oct 1993 | A |
5259445 | Pratt et al. | Nov 1993 | A |
5270952 | Adams et al. | Dec 1993 | A |
5289362 | Liebl et al. | Feb 1994 | A |
5329991 | Mehta et al. | Jul 1994 | A |
5348078 | Dushane et al. | Sep 1994 | A |
5386577 | Zenda | Jan 1995 | A |
5392042 | Pellon | Feb 1995 | A |
5395042 | Rilley et al. | Mar 1995 | A |
5412377 | Evans et al. | May 1995 | A |
5461558 | Patsiokas et al. | Oct 1995 | A |
5481481 | Frey et al. | Jan 1996 | A |
5482209 | Cochran et al. | Jan 1996 | A |
5526422 | Keen | Jun 1996 | A |
5537106 | Mitsuhashi | Jul 1996 | A |
5544036 | Brown, Jr. et al. | Aug 1996 | A |
5566879 | Longtin | Oct 1996 | A |
5570837 | Brown et al. | Nov 1996 | A |
5644173 | Elliason et al. | Jul 1997 | A |
5673850 | Uptegraph | Oct 1997 | A |
5782296 | Mehta | Jul 1998 | A |
5802467 | Salazar et al. | Sep 1998 | A |
5818428 | Eisenbrandt et al. | Oct 1998 | A |
5873519 | Beilfuss | Feb 1999 | A |
5886697 | Naughton et al. | Mar 1999 | A |
5901183 | Garin et al. | May 1999 | A |
5902183 | D'Souza | May 1999 | A |
5909378 | De Milleville | Jun 1999 | A |
5937942 | Bias et al. | Aug 1999 | A |
5947372 | Tiernan | Sep 1999 | A |
6009355 | Obradovich et al. | Dec 1999 | A |
6020881 | Naughton et al. | Feb 2000 | A |
6032867 | Dushane et al. | Mar 2000 | A |
6059195 | Adams et al. | May 2000 | A |
6081197 | Garrick et al. | Jun 2000 | A |
6121875 | Hamm et al. | Sep 2000 | A |
6140987 | Stein et al. | Oct 2000 | A |
6144971 | Sunderman et al. | Nov 2000 | A |
6192282 | Smith et al. | Feb 2001 | B1 |
6196467 | Dushane et al. | Mar 2001 | B1 |
6208331 | Singh et al. | Mar 2001 | B1 |
6236326 | Murphy | May 2001 | B1 |
6256378 | Iggulden et al. | Jul 2001 | B1 |
6285912 | Ellison et al. | Sep 2001 | B1 |
6290140 | Pesko et al. | Sep 2001 | B1 |
6305611 | Proffitt et al. | Oct 2001 | B1 |
6315211 | Sartain et al. | Nov 2001 | B1 |
6318639 | Toth | Nov 2001 | B1 |
6323882 | Jerome et al. | Nov 2001 | B1 |
6330806 | Beaverson et al. | Dec 2001 | B1 |
6344861 | Naughton et al. | Feb 2002 | B1 |
6351693 | Monie et al. | Feb 2002 | B1 |
6398118 | Rosen et al. | Jun 2002 | B1 |
6478233 | Shah | Nov 2002 | B1 |
6502758 | Cottrell | Jan 2003 | B2 |
6518957 | Lehtinen et al. | Feb 2003 | B1 |
6553777 | Dillenback | Apr 2003 | B2 |
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 |
6628997 | Fox et al. | Sep 2003 | B1 |
6658303 | Hatemata et al. | Dec 2003 | B2 |
6685098 | Okano et al. | Feb 2004 | B2 |
6687678 | Vorimatsu et al. | Feb 2004 | B1 |
6718213 | Enberg | Apr 2004 | B1 |
6782706 | Holmes et al. | Aug 2004 | B2 |
6783079 | Carey et al. | Aug 2004 | B2 |
6786421 | Rosen | Sep 2004 | B2 |
6789739 | Rosen | Sep 2004 | B2 |
6824069 | Rosen | Nov 2004 | B2 |
6833990 | LaCroix et al. | Dec 2004 | B2 |
6845918 | Rotondo | Jan 2005 | B2 |
6851621 | Wacker et al. | Feb 2005 | B1 |
6886754 | Smith et al. | May 2005 | B2 |
6975958 | Bohrer et al. | Dec 2005 | B2 |
6983889 | Alles | Jan 2006 | B2 |
6997390 | Alles | Feb 2006 | B2 |
7001495 | Essalik et al. | Feb 2006 | B2 |
7028912 | Rosen | Apr 2006 | B1 |
7050026 | Rosen | May 2006 | B1 |
7089066 | Hesse et al. | Aug 2006 | B2 |
7114554 | Bergman et al. | Oct 2006 | B2 |
7130719 | Ehlers et al. | Oct 2006 | B2 |
7142948 | Metz | Nov 2006 | B2 |
7146253 | Hoog et al. | Dec 2006 | B2 |
7152802 | Kell et al. | Dec 2006 | B2 |
7152806 | Rosen | Dec 2006 | B1 |
7156318 | Rosen | Jan 2007 | B1 |
7302642 | Smith et al. | Nov 2007 | B2 |
7306165 | Shah | Dec 2007 | B2 |
7310559 | Walko, Jr. | Dec 2007 | B2 |
7320110 | Shah | Jan 2008 | B2 |
7556207 | Mueller et al. | Jul 2009 | B2 |
7604046 | Bergman et al. | Oct 2009 | B2 |
7636604 | Bergman et al. | Dec 2009 | B2 |
7693582 | Bergman et al. | Apr 2010 | B2 |
7890195 | Bergman et al. | Feb 2011 | B2 |
20010029585 | Simon et al. | Oct 2001 | A1 |
20010052459 | Essalik et al. | Dec 2001 | A1 |
20020092779 | Essalik et al. | Jul 2002 | A1 |
20030034897 | Shamoon et al. | Feb 2003 | A1 |
20030034898 | Shamoon et al. | Feb 2003 | A1 |
20040260411 | Cannon | Dec 2004 | A1 |
20040262410 | Hull | Dec 2004 | A1 |
20050108091 | Sotak et al. | May 2005 | A1 |
20050116023 | Amundson et al. | Jun 2005 | A1 |
20050119766 | Amundson et al. | Jun 2005 | A1 |
20060004492 | Terlson et al. | Jan 2006 | A1 |
20060192021 | Schultz et al. | Aug 2006 | A1 |
20110160915 | Bergman et al. | Jun 2011 | A1 |
Number | Date | Country |
---|---|---|
3334117.6 | Apr 1985 | DE |
0070414 | Jan 1983 | EP |
0678204 | Mar 2000 | EP |
0985994 | Mar 2000 | EP |
1033641 | Sep 2000 | EP |
1074009 | Feb 2001 | EP |
2711230 | Apr 1995 | FR |
9711448 | Mar 1997 | WO |
9739392 | Oct 1997 | WO |
0152515 | Jul 2001 | WO |
0179952 | Oct 2001 | WO |
Entry |
---|
All Non-Patent References Have Been Previously Provided in U.S. Appl. No. 11/532,355, filed Sep. 15, 2006, U.S. Appl. No. 10/726,201, filed Dec. 2, 2003 and U.S. Appl. No. 12/700,656, filed Feb. 4, 2010. |
“A Full Range of Alternative User Interfaces for Building Occupants and Operators,” http://www.automatedbuildings.com/news/janOO/articles/andover/andover.htm, 5 pages, dated Jan. 2000, printed Sep. 20, 2004. |
“CorAccess Systems/In Home,” http://web.archive.org/web20011212084427/vwvw.coraccess.com/home.html, 1 page, copyright 2001, printed Aug. 19, 2004. |
“HAI Company Background,” http://www.homeauto.com/AboutHAI/abouthai main.htm, 2 pages, printed Aug. 19, 2004. |
“High-tech options take hold in new homes—Aug. 28, 2000—Dallas Business Journal,” http://bizjournals.com/dallas/stories/2000/08/28/focus4, 3 pages, dated Aug. 28, 2000, printed Aug. 19, 2004. |
“Home Toys Review-TouchLinc”, http://www.hometoys.com/htinews/aug99/reviews/touchlinc/touchlinc.htm, 3 pages, dated Aug. 1999, printed Aug. 20, 2004. |
“Mark of Excellence Award Finalist Announced,” http://64.233.167.104/search?Q=cache:ciOA2YtYaBIJ:www.hometoys.com/releases/mar. . . , 6 pages, Leopard Touchscreen on p. 2, dated prior to Mar. 4, 2000, printed Aug. 20, 2004. |
“Product Review—Philips Pronto Remote Control,” http://hometheaterhifi.com/volume—6—2/philipsprontoremotecontrol.html, 5 pages, dated May 1999, printed Aug. 20, 2004. |
“RC X10 Automation Forum: Control your Heating and Cooling System with Proton(1/1),” http://www.remotecontral.com/cgi-bin/mboard/rc-x10/thread.cgi?12, 2 pages, dated Apr. 23, 1999, printed Aug. 20, 2004. |
“Spotlight on integrated systems,” Custom Builder, V8, N2, p. 66(6), Mar.-Apr. 1993. |
“Vantage Expands Controls for Audio/Video, HVAC and Security,” http://www.hometoys.com/htinews/aug99/releases/vantage03:htm, 2 pages, dated Aug. 3, 1999, printed Aug. 20, 2004. |
ADI, “Leopard User Manual,” 93 pages, 2001. |
Adicon 2500, “The Automator,” 4 pages, Oct.-Dec. 2000. |
ADT Security Services, “iCenter Advanced User Interface 8142ADT,” Installation and Setup Guide, 5 pages, May 2001; First Sale Feb. 2001. |
ADT Security Systems, “iCenter Advanced User Interface 8142ADT User Guide,” pp. 1-136, 2001. |
Aprilaire Electronic Thermostats Models 8344, 8346, 8348, 8363, 8365, 8366 Operating Instructions, 8 pages, 2003. |
Aube Technologies, Electronic Thermostat for Heating System Model TH135-01, 5 pages, Aug. 14, 2001. |
Aube Technologies, TH140-28 Electronic Programmable Thermostat, Installation Instructions and User Guide, pp. 1-4, Jan. 22, 2004. |
AutomatedBuildings.com Article—“Thin Client” Solutions, “Pressure, Air Flow, Temperature, Humidity & Valves,” Dwyer Instruments, Inc., 5 pages, printed Sep. 20, 2004. |
Blake etal., “Seng 310 Final Project Demo Program” Illustration, 3 pages, Apr. 6, 2001. |
Blake etal., “Seng 310 Final Project” Report, dated Apr. 6, 2001. |
Braeburn Model 3000 Owner's Manual, pp. 1-13, 2001. |
Braeburn Model 5000 Owners Manual, pp. 1-17, 2001. |
BRK First Alert, User's Manual, Smoke and Fire Alarms, pp. 1-7, Nov. 2002. |
Business Wire, “MicroTouch Specialty Products Group to Capitalize on Growing Market for Low-Cost Digital Matrix Touchscreens,” p. 1174 (2 pages), Jan. 6, 1999. |
Cardio Manual, available at http://www.secant.ca/En/Documentation/Cardio2e-Manual.pdf, Cardio Home Automation Inc., 55 pages, printed Sep. 28, 2004. |
Cardio, by Secant; http://www.hometoys.com/htinews/apr98/reviews/cardio.htm. “HTINews Review,” Feb. 1998, 5 pages, printed Sep. 14, 2004. |
Carrier TSTATCCRF01 Programmable Digital Thermostat, pp. 1-21, prior to Apr. 21, 2005. |
Carrier Microelectronic Programmable Thermostat Owner's Manual, pp. 1-24, May 1994. |
Carrier, “Programmable Dual Fuel Thermostat,” Installation, Start-Up & Operating Instructions, pp. 1-12, Oct. 1998. |
Carrier, “Programmable Thermostats,” Installation, Start-Up & Operating Instructions, pp. 1-16, Sep. 1998. |
Carrier, “Standard Programmable Thermostat,” Homeowner's Manual, pp. 1-8 pages, 1998. |
Carrier, “Thermidistat Control,” Installation, Start-Up, and Operating Instructions, pp. 1-12, Aug. 1999. |
Climatouch, User Manual, Climatouch CT03TSB Thermostat, Climatouch CT03TSHB Thermostat with Humidity Control, Outdoor UHF Temperature Transmitter 217S31, 19 pages, Printed Sep. 15, 2004. |
CorAccess, “Companion 6,” User Guide, pp. 1-20, Jun. 17, 2002. |
Danfoss RT51/51RF & RT52/52RF User Instructions, 2 pages, Jun. 2004. |
DeKoven et al., “Designing Collaboration in Consumer Products.” 2 pages, 2001. |
DeKoven et al., “Measuring Task Models in Designing Intelligent Products,” 2 pages, Jan. 13-16, 2002. |
Domotique Secant Home Automation—Web Page, available at http://www.secant.ca/En/Company/Default.asp, 1 page, printed Sep. 28, 2004. |
Firex Smoke Alarm, Ionization Models AD, ADC Photoelectric Model Pad, 4 pages, prior to Apr. 21, 2005. |
Freudenthal et al., “Communicating extensive smart home functionality to users of all ages: the design of a mixed-initiative multimodal thermostat-interface,” pp. 34-39, Mar. 12-13, 2001. |
Gentex Corporation, HD135, 135° Fixed Temperature Heat Detector AC Pwered, 120V, 60Hz With Battery Backup, Installation Instructions—Owner's Information, pp. 1-5, Jun. 1, 1998. |
Gentex Corporation, 9000 Series, Photoelectric Type Single Station/Multi-Station Smoke Alarms AC Powered With Battery Backup, Installation Instructions—Owner's Information, pp. 9-1 to 9-6, Jan. 1, 1993. |
Honeywell Brivis Deluxe Programmable Thermostat, pp. 1-20, 2002. |
Honeywell Brivis T8602C Chronotherm IV Deluxe Programmable Thermostats, Installation Instructions, pp. 1-12, 2002. |
White-Rodgers Installation Instructions for Heating & Air Conditioning IF78 5/2 Day Programmable Thermostat, 7 pages, prior to Jul. 7, 2004. |
White-Rodgers, “Comfort-Set 90 Series Thermostat,” Manual, pp. 1-24, prior to Jul. 7, 2004. |
White-Rodgers Comfort-Set III Thermostat, pp. 1-44, prior to Jul. 7, 2004. |
White-Rodgers, 1F80-240 “(for Heating Only systems) Programmable Electronic Digital Thermostat,” Installation and Operation Instructions, 8 pages, prior to Jul. 7, 2004. |
White-Rodgers, 1F80-241 “Programmable Electronic Digital Thermostat,” Installation and Operation Instructions, 6 pages, prior to Jul. 7, 2004. |
White-Rodgers, 1F80-261 “Programmable Electronic Digital Thermostat,” Installation and Operation Instructions, 8 pages, prior to Jul. 7, 2004. |
White-Rodgers, 1F81-261 “Programmable Electronic Digital Multi-Stage Thermostat,” Installation and Operation Instructions, 8 pages, prior to Jul. 7, 2004. |
White-Rodgers, 1F82-261 “Programmable Electronic Digital Heat Pump Thermostat,” Installation and Operation Instructions, 8 pages, prior to Jul. 7, 2004. |
White-Rodgers, Comfort-Set 90 Series Premium, 4 pages, prior to Apr. 21, 2005. |
www.icmcontrols.com, Simplecomfort, SC3000 Single Stage Heat/Single Stage Cool or Single Stage Heat Pump/Manual Changeover, 1 page, prior to Jul. 7, 2004. |
www.icmcontrols.com, Simplecomfort, SC3001 Single Stage Heat/Single Stage Cool or Single Stage Heat Pump/Manual Changeover, 1 page, prior to Jul. 7, 2004. |
www.icmcontrols.com, Simplecomfort, SC3006 Single Stage Heat/Single Stage Cool or Single Stage Heat Pump/Manual Changeover, 1 page, prior to Jul. 7, 2004. |
www.icmcontrols.com, Simplecomfort, SC3201 2 Stage Heat Pump Manual Changeover, 1 page, prior to Jul. 7, 2004. |
www.icmcontrols.com, Simplecomfort, SC3801 2 Stage Heat/2 Stage Cool 2 Stage Heat Pump/Audio Changeover, 1 page, prior to Jul. 7, 2004. |
Lennox User's Manual, “Network Control Panel (NCP),” pp. 1-18, Nov. 1999. |
Goolamabbas, “Computing Classes, Fall 1994, Georgia Tech,” 53 pages, Nov. 4, 1994. |
“HTINews Review of Cardio by Secant,” 5 pages, Printed From the Internet on Mar. 20, 2009, First appeared Feb. 1998. |
Blister Pack Insert from a Ritetemp 8082 Touch Screen Thermostat Product, 2 pages, 2002. |
Trouble Shooting Guide for Ritetemp Thermostat 8082, 1 page, 2002. |
Quick Start Guide for Ritetemp Thermostat 8082, 1 page, 2002. |
Install Guide for Ritetemp Thermostat 8082, 6 pages, 2002. |
Honeywell T8002 Programmable Thermostat, Installation Instructions, pp. 1-8, 2002. |
Honeywell T8602A,B,C,D and TS8602A.C Chronotherm III Fuel Saver Thermostats, Installation Instructions, pp. 1-12, 1995. |
Honeywell T8602D Chronotherm IV Deluxe Programmable Thermostats, Installation Instructions, pp. 1-12, 2002. |
Honeywell TH8000 Series Programmable Thermostats, Owner's Guide, pp. 1-44, 2004. |
Honeywell, “Introduction of the S7350A Honeywell WebPAD Information Appliance,” Home and Building Control Bulletin, 2 pages, Aug. 29, 2000; Picture of WebPad Device with touch screen, 1 Page; and screen shots of WebPad Device, 4 pages. |
Honeywell, “W7006A Home Controller Gateway User Guide,” 31 pages, Jul. 2001. |
Honeywell, MagicStat® CT3200 Programmable Thermostat, Installation and Programming Instructions, pp. 1-24, 2001. |
http://www.cc.gatech.edu/computing/classes/cs6751—94—fall/groupc/climate-2/node1.html, “Contents,” 53 pages, printed Sep. 20, 2004. |
http://www.hometoys.com/htinews/apr99/releases/hal01.htm, HTI News Release, pp. 1-3, printed Oct. 28, 2004. |
http://www.ritetemp.info/rtMenu—13.html, Rite Temp 8082, 8 pages , printed Jun. 20, 2003. |
http://www.thermostatsales.com, Robertshaw, “9610 Digital Programmable Thermostat,” 3 pages, printed Jun. 17, 2004. |
http://www.thermostatsales.com, Robertshaw, “9700 Deluxe Programmable Thermostat” 3 pages, printed Jun. 17, 2004. |
http://www.thermostatsales.com, Robertshaw, “9710 Deluxe Programmable Thermostat,” 3 pages, printed Jun. 17, 2004. |
http://www.thermostatsales.com, Robertshaw, “9720 Deluxe Programmable Thermostat,” 3 pages, printed Jun. 17, 2004. |
Hunter, “44200/44250,” Owner's Manual, 32 pages, prior to Jul. 7, 2004. |
Hunter, “44300/44350,” Owner's Manual, 35 pages, prior to Jul. 7, 2004. |
Hunter, “Auto Saver 550”, Owner's Manual Model 44550, 44 pages, prior to Jul. 7, 2004. |
Invensys™, “9700i 9701 i 9715i 9720i Deluxe Programmable Thermostats,” User's Manual, pp. 1-28, prior to Jul. 7, 2004. |
LuxTX9000 Installation, 3 pages, prior to Apr. 21, 2005. |
Lux ELV1 Programmable Line Voltage Thermostat, Installation Instructions, 3 pages, prior to Jul. 7, 2004. |
Lux, “511 Series Smart Temp Electronic Thermostat,” Owner's Manual, 3 pages, prior to Jul. 7, 2004. |
Lux, “600 Series Smart Temp Electronic Thermostat,” Owner's Manual, 3 pages, prior to Jul. 7, 2004. |
Lux, “602 Series Multi-Stage Programmable Thermostat,” Owner's Manual, 2 pages, prior to Jul. 7, 2004. |
Lux, “605/2110 Series Programmable Heat Pump Thermostat,” Owner's Manual, 3 pages, prior to Jul. 7, 2004. |
Lux, “700/9000 Series Smart Temp Electronic Thermostat,” Owner's Manual, 3 pages, prior to Jul. 7, 2004. |
Lux, “PSPH521 Series Programmable Heat Pump Thermostat,” Owner's Manual, 3 pages, prior to Jul. 7, 2004. |
Lux, “TX1500 Series Smart Temp Electronic Thermostat,” Owner's Manual, 6 pages, prior to Jul. 7, 2004. |
Lux TX500 Series Smart Temp Electronic Thermostat, 3 pages, prior to Jul. 7, 2004. |
METASYS, “HVAC PRO for Windows User's Manual,” 308 pages, 1998. |
Proliphix, “Web Enabled IP Thermostats, Intelligent HVAC Control,” Proliphix Inc., 2 pages, on or before Aug. 28, 2004. |
Ritetemp Operation 8029, 3 pages, Jun. 19, 2002. |
Ritetemp Operation 8050, 5 pages, Jun. 26, 2002. |
Ritetemp Operation 8085, pp. 1-6, prior to Apr. 21, 2005. |
Sealed Unit Parts Co., Inc., Supco & CTC Thermostats . . . loaded with features, designed for value!, 6 pages, prior to Apr. 21, 2005. |
Totaline Model P474-1035 Owner's Manual Programmable 5-2 Day Digital Thermostat, pp. 1-21, Apr. 2003. |
Totaline Star CPE230RF, Commercial Programmable Thermostat Wireless Transmitter, Owner's Manual, pp. 1-16, Oct. 1998. |
Totaline Star P/N P474-0130 Non-Programmable Digital Thermostat Owner's Manual, pp. 1-22, prior to Apr. 21, 2005. |
Totaline, “1 For All programmable Digital Thermostat,” Owner's Manual P/N P374-1100FM, 23 pages, Nov. 1998. |
Totaline, “1 For All Programmable Digital Thermostat,” Owner's Manual P/N P474-1050, 21 pages, Nov. 1998. |
Totaline, “1 For All Programmable Digital Thermostat,” Owner's Manual P/N P374-1100, 24 pages, Apr. 2001. |
Totaline, “Intellistat Combination Temperature and Humidity Control,” Owner's Manual P/N P374-1600, 25 pages, Jun. 2001. |
Totaline, “Programmable Thermostat Configurable for Advanced Heat Pump or Dual Fuel Operation,” Owner's Manual P/N P374-1500, 24 pages, Jun. 1999. |
Totaline, “Instructions P/N P474-1010”, Manual, 2 pages, Dec. 1998. |
Totaline, “Programmable Thermostat”, Homeowner's Guide, 27 pages, Dec. 1998. |
Totaline, “Wireless Programmable Digital Thermostat,” Owner's Manual 474-1100RF, 21 pages, 2000. |
Visor Handheld User Guide, 280 pages, Copyright 1999-2000. |
White-Rodgers 1F80-224 Programmable Electronic Digital Thermostat, Installation and Operation Instructions, 8 pages, prior to Apr. 21, 2005. |
White-Rodgers Installation Instructions for Heating & Air Conditioning IF78 Non-Programmable Thermostat, 6 pages, prior to Apr. 21, 2005. |
White-Rodgers, “Installation Instructions for Heating & Air Conditioning IF72 5/2 Day Programmable Heat Pump Thermostat,” 8 pages, prior to Jul. 7, 2004. |
Home Automation, Inc., “OmniPro Owner's Manual,” 153 pages, prior to Dec. 27, 2010. |
Home Automation, Inc., “OmniTouch Touchscreen Model 32A00-1, User's Guide,” Document No. 32R00-1 Rev A, 15 pages, Aug. 2003. |
Warmly Yours, “Model TH111GFCI-P (120 VAC),” Manual, pp. 1-4, prior to Jul. 7, 2004. |
Remote Control Power Requirement for Ritetemp Thermostat 8082, 1 page, 2002. |
Mounting Template for Ritetemp Thermostat 8082, 1 page, 2002. |
Honeywell, “Excel Building Supervisor-Integrated R7044 and FS90 Ver. 2.0,” Operator Manual, 70 pages, Apr. 1995. |
Trane, “System Programming, Tracer Summit Version 14, BMTW-SVP01D-EN,” 623 pages, 2002. |
Honeywell CT8602C Professional Fuel Saver Thermostat, pp. 1-6, 1995. |
Honeywell Electronic Programmable Thermostat, Owner's Guide, pp. 1-20, 2003. |
Honeywell Electronic Programmable Thermostats, Installation Instructions, pp. 1-8, 2003. |
Honeywell News Release, “Honeywell's New Sysnet Facilities Integration System for Boiler Plant and Combustion Safety Processes,” 4 pages, Dec. 15, 1995. |
Matty, T.C., “Advanced Energy Management for Home Use”, in IEEE Transactions on Consumer Electronics, vol. 35, No. 3, Aug. 1989. |
Reza, S. Raji, “Smart Networks for Control,” Jun. 1994, IEEE Spectrum, pp. 49-55. |
Number | Date | Country | |
---|---|---|---|
20130018486 A1 | Jan 2013 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12978903 | Dec 2010 | US |
Child | 13548072 | US | |
Parent | 12700656 | Feb 2010 | US |
Child | 12978903 | US | |
Parent | 11532355 | Sep 2006 | US |
Child | 12700656 | US | |
Parent | 10726201 | Dec 2003 | US |
Child | 11532355 | US |