THERMOSTAT WITH ELECTRONIC IMAGE DISPLAY

FIELD OF THE INVENTION

The present invention relates generally to the field of programmable controllers for homes and/or buildings and their related grounds. More specifically, the present invention relates to such controllers with a display, and an I/O interface for uploading electronic images and/or other information for use by the controller and/or for viewing on the display of the controller.

BACKGROUND OF THE INVENTION

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 such as thermostats, water heater controllers, water softener controllers, security system controllers, lawn sprinkler controllers, and lighting system controllers.

In a typical HVAC system, for example, such controllers can be employed to monitor and, if necessary, control various environmental conditions occurring within a structure. The controller may include a microprocessor and/or microcontroller that interacts with other components in the system via an I/O interface to regulate the temperature, humidity, venting, and air quality occurring at one or more locations within the structure. 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 HVAC system.

In some instances, the controller may be configured to detect when a service event has occurred in one or more of the system components. In certain circumstances, for example, the controller may be configured to detect when one or more system components have malfunctioned or have gone offline, or have been in service beyond a recommended period of time and thus require maintenance. Depending on the type of service event detected, the controller can be configured to shut down one or more of the components until the system can be restored.

In some cases, the component triggering the service event may require servicing from the manufacturer or other authorized service technician in order to restore the system to normal operation. To notify the user where to obtain service, many manufacturers will place a sticker containing servicing information in an inconspicuous place such as on the inside door panel of the controller housing. After a service event has occurred, the user must know to open the controller door in order to obtain the servicing information. Accordingly, there is a need in the art to better provide the user with servicing information when a fault or other service event has been detected.

Many HVAC controllers, such as thermostats, have a user interface that includes a fixed segment display. In fixed segment displays controllers, all of display segments are typically predefined and manufactured into the display. During use, and to display one or more settings or parameters of the thermostat, the controller simply turns on appropriate segments on the display. While the use of fixed segment displays has worked satisfactorily for many applications, they can be somewhat limiting. For example, only those parameters and settings that were predefined and manufactured into the display can be typically be displayed, and updates or changes often cannot be made in the field. In addition, and because of the fixed nature of the segments on the fixed segment display, a location or region on the display is typically dedicated to displaying certain information. In some cases, this leads to the layout of the display items not to be optimal from an ease of use and/or ease of understanding point of view. Moreover, fixed segment displays can be somewhat limited in the types of content that can be displayed on the display. For example, graphical images, menus as well as other types of content often cannot be displayed.

Some of the limitations of fixed segment displays have been overcome with the use of graphical displays such as dot matrix displays. For example, some HVAC controllers have incorporated dot matrix displays in order to display a wider variety of menus with better placement of information and selections on the display, which can help make the operation of the controller more intuitive to the user. However, to date, many of these controllers are limited in the type of content that can be displayed on the display, and typically do not provide a mechanism for updating and/or uploading new information for use by the controller and/or for viewing on the display.

SUMMARY OF THE INVENTION

The present invention relates to programmable controllers having a programmable service event display mode. A programmable controller in accordance with an illustrative embodiment of the present invention may include an interface for programming a service event display mode in the controller, and/or for displaying servicing information when a service event is detected by the controller. In certain embodiments, the interface may be provided as part of a user interface such as a touch screen or LCD panel/keypad inset within a controller housing. In other embodiments, the interface may be provided as a separate interface from the user interface, allowing the controller to be programmed from a location outside of the controller.

The controller may be operatively coupled to a number of other system components including, for example, a heating unit, a cooling unit, a ventilation unit, a filtration unit, a UV lamp unit, a humidifier/dehumidifier unit, and/or one or more local or remote sensors. The controller can be configured to check the status of the system components to determine if one or more of the components is functioning properly, has malfunctioned, or has gone offline. An event such as the triggering of a service indicator or the expiration of an equipment service event timer may cause the controller to display servicing information on the display unit, informing the user that servicing may be necessary or recommended. Alternatively, or in addition, the controller may be programmed to automatically contact a designated contractor, a service referral organization, a utility, a retailer, a manufacturer, and/or some other person or organization, requesting service for the detected event. In certain embodiments, the user may send a signal to the controller requesting that certain servicing information be displayed on the display unit, and/or that the controller contact a designated contractor, a service referral organization, a utility, a retailer, a manufacturer, and/or some other person or organization, as desired.

The present invention also relates to programmable controllers for homes and/or buildings and their related grounds, such as thermostats, that have a display and an external interface. The external interface may be use for uploading electronic images and/or other information from an external data source, and may use the uploaded electronic images and/or other information for programming and/or updating the controller and/or for viewing the electronic images and/or other information on the display of the controller.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an illustrative HVAC system employing a controller having a programmable service event display mode;

FIG. 2 is a block diagram of the controller and user interface of FIG. 1;

FIG. 3 is block diagram showing the controller of FIGS. 1-2 equipped with a programmable interface;

FIG. 4 is a flow chart of an illustrative service event routine programmed within a controller equipped with a service event display mode;

FIG. 5 is a view of an illustrative HVAC controller equipped with a touch screen interface;

FIG. 6 is a pictorial view showing the illustrative controller and user interface of FIG. 5 during normal controller operation;

FIG. 7 is a pictorial view showing the illustrative controller and user interface of FIG. 5 after a service event has been detected;

FIG. 8 is a view of another illustrative HVAC controller equipped with a display panel and keypad interface;

FIG. 9 is a pictorial view showing the illustrative controller and user interface of FIG. 8 during normal controller operation;

FIG. 10 is a pictorial view showing the illustrative controller and user interface of FIG. 8 after a service event has been detected by the controller;

FIG. 11 is a block diagram of an illustrative controller having a display and an external interface;

FIGS. 12-13 are pictorial views showing an illustrative controller and user interface having a background image displayed on part of the display;

FIG. 14 is a pictorial view showing another illustrative controller and user interface having an electronic image displayed on the display;

FIG. 15 is a schematic view of an illustrative controller and user interface displaying a plurality of electronic images in a slide show format;

FIG. 16 is an illustrative view of an illustrative controller having a screensaver; and

FIGS. 17A-17F are illustrative pictorial views of a controller having a menu for selecting electronic images for display.

DETAILED DESCRIPTION OF THE INVENTION

The following description should be read with reference to the drawings, in which like elements in different drawings are numbered in like fashion. The drawings, which are not necessarily to scale, depict selected 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 the many of the examples provided have suitable alternatives that can be utilized. While the various devices and systems illustrated herein are described specifically with respect to HVAC systems, it should be understood that the present invention could be employed in other systems, including, for example, security systems, lighting systems, sprinkler or drip water systems, audio/video systems, etc.

Referring now to FIG. 1, a block diagram of an illustrative HVAC system 10 employing a controller 12 having a programmable service event display mode will now be described. Controller 12 may be operatively connected to one or more system components that can be activated to regulate various environmental conditions such as temperature, humidity and air quality levels occurring within a structure. As shown in FIG. 1, for example, the controller 12 can be connected to a heater unit 14 and cooling unit 16 that can be activated to maintain the structure at a particular temperature level. A ventilation unit 18 such as a fan or blower equipped with one or more dampers may be employed to regulate the volume of air delivered to the various rooms of the structure. A filtration unit 20, UV lamp unit 22, and humidifier/dehumidifier unit 24 may also be provided to regulate the air quality and moisture levels within the structure. One or more local and/or remote sensors 26 as well as other system components can also be connected to controller 12 to monitor and regulate the environment, as desired. The system components may be directly connected to a corresponding Input/Output (I/O) port or I/O pins on the controller 12, and/or connected to the controller via a network or the like, as desired.

The controller 12 may include a user interface 28 that allows a user or service technician to transmit signals to and from the controller 12. The user interface 44 can include a touch screen, a liquid crystal display (LCD) panel and keypad, a dot matrix display, a computer, and/or any other suitable device for sending and receiving signals to and from the controller 12. The controller 12 can be configured to display servicing information on the user interface 28 to notify the user when a fault or malfunction has been detected, or when servicing is necessary or desirable. In certain embodiments, for example, the controller 12 can be programmed to display the name, logo, URL and/or telephone number of a designated contractor, a service referral organization, a utility, a retailer, a manufacturer, and/or some other person or organization when a fault or other service event has been detected in one or more of the system components. In some cases, the controller may display a different name, logo, URL and/or telephone number, depending on the nature of the service event detected and/or the component or unit that needs service. For example, the name, logo, URL and/or telephone number of a designated heating contractor may be displayed when a service event related to the heating system is detected, and the name, logo, URL and/or telephone number of a designated security system contractor may be displayed when a service event related to the security system is detected. In some cases, a service event code and/or short description of the service event may be displayed.

As is discussed in greater detail with respect to FIGS. 5-10 below, such servicing information can be displayed prominently on a display unit, providing the user with information on where to call for servicing. Alternatively, or in addition, the controller 12 may be programmed to automatically contact a designated contractor, a service referral organization, a utility, a retailer, a manufacturer, and/or some other person or organization, requesting service for the detected event. In one illustrative embodiment, a Telephone Access Module (TAM) 29 may be provided. The TAM 29 may call the appropriate person or organization when a service event is detected by the controller 12. While a TAM is shown in FIG. 1, it is contemplated that the controller 12 may notify an appropriate person or organization when a service event is detected via an internet connection, a wireless connection (e.g. cell phone), or any other suitable communication method, as desired.

FIG. 2 is a block diagram of the controller 12 and user interface 28 of FIG. 1. As illustrated in FIG. 2, the controller 12 may include a processor 30 (e.g. a microprocessor/CPU), a storage memory 32, a clock 34, and an I/O interface 36 that connects the controller 12 to the various system components illustrated in FIG. 1. An internal sensor 38 located within the controller 12 can be employed to measure the temperature, humidity levels and/or other environmental conditions occurring within the structure. In some cases, the sensor 38 may be external to the controller 12.

FIG. 3 is a block diagram showing the programmable controller 12 of FIGS. 1-2 equipped with an interface 40. The interface 40 may be configured to permit the manufacturer or other authorized technician to program the controller 12 to display servicing information on the user interface 40 when a fault is detected in one or more of the system components, or when the controller 12 has determined that a system component requires maintenance or other servicing. For example, the interface 40 can be used to set various equipment service event timers that can be used to remind the user to replace or clean the filter for the filtration unit 20, the pads for the humidifier/dehumidifier unit 24, the UV lamp for the UV lamp unit, the controller batteries, etc., after a certain period of time has elapsed. Other equipment service event timers may, of course, be implemented depending on the particular application.

The parameters for each equipment service event timer can be set to a particular default value, which can then be adjusted using the interface 40, as desired. When the equipment event timer elapses, the controller 12 can be configured to display a service reminder via the user interface 28 of FIG. 2 informing the user that service is suggested for the system.

The interface 40 may be provided as part of the user interface 28 described above, or may be provided as a separate interface from the user interface 28. In certain embodiments, for example, the interface 40 may include a menu or screen accessible via the user interface 28 using a security code or password. The menu or screen may be configured to permit only the manufacturer or other authorized technician or organization to program the servicing information into the controller 12, if desired.

In some embodiments, the controller 12 can be programmed at any time before, during or after the controller 12 has been installed. For example, the interface 40 may permit the servicing information to be programmed into the controller 12 in-house at the manufacturer, or at a later time during installation or servicing. In certain embodiments, for example, the interface 40 may include a data port for transferring data to the controller 12, allowing the manufacturer and/or service technician to program the servicing information into the controller 12. For example, using the data port, a service technician or manufacturer may upload servicing information into the controller 12. This information may include, for example, a logo, telephone number, email address, web page URL, etc., of a contractor, service referral organization, retailer, utility or other organization, as desired. This data may be uploaded from a PDA, laptop, or other portable or handheld device, if desired. In some cases, the logo may be in a graphical representation stored in the memory of the controller. The logo may be in, for example, bitmap, jpeg, gif, tiff, or any other suitable format.

In some embodiments, the interface 40 may be provided as part of a remote interface, allowing the manufacturer or other authorized technician to program the controller 12 at a location outside of the controller 12. In certain embodiments, for example, the interface 40 may include a receiver that can be used to receive servicing information over a wireless connection, such as an infrared connection, over a cell phone network, over a wired connection such as a telephone line, or any other suitable connection. Alternatively, or in addition, the interface 40 may be connected to the World Wide Web (WWW), which may allow the servicing information to be uploaded into the controller 12 from a remote location across the WWW.

Referring now to FIG. 4, an illustrative service event routine programmed within a controller equipped with a service event display mode will now be described. The service event routine, indicated generally by reference number 42, may begin from a normal controller operation mode, indicated generally by block 44. From the normal controller operation mode 44, the controller may be configured to check the operating status of one or more of the system components to determine if the system components are functioning properly, as indicated generally by block 46. In some embodiments, the controller may periodically poll each of the system components and obtain current status information. If the controller receives a signal from one or more of the system components indicating a system fault, loss of power or other service indicator, the controller can be configured to display servicing information such as the name, logo, URL, telephone number and/or other information for a designated contractor, service referral organization, manufacturer, retailer, utility and/or other person or organization. The controller may also be configured to display a service event code, a description of the fault, and/or any other useful information, as indicated generally by block 48. In some cases, different servicing information can be displayed depending on which system component(s) indicated a positive service indicator. For example, one contractor logo and telephone number may be displayed if the cooling system provided a service indicator, and another contractor logo and telephone number may be displayed if the heating system provided a service indicator. The servicing information can be displayed temporarily for a certain period of time until the controller is reset and/or until the faulty system component is restored to normal operation.

If the controller does not receive a service indicator from one or more of the system components, the controller can be configured to determine whether any of the equipment service timers (if any) have elapsed, as indicated generally by block 50. If, for example, the controller determines that the filter for the filtering unit has been in use for a certain period of time and likely requires replacement, the controller can be configured display a logo and telephone number for an authorized filter contractor or dealer. Information about the type of filter to replace as well as other pertinent servicing information can also be displayed, as desired.

In certain embodiments, the controller 12 can include a help mode that can be activated by the user to obtain servicing information. As indicated by block 52, for example, the user may send a signal to the controller via a “help” button or other similar command. When the controller 12 receives a signal from the user requesting help, as indicated generally by block 54, the controller can be configured to display servicing information such as the logo, telephone number, etc. of a designated contractor, service referral organization, manufacturer, retailer, utility and/or other person or organization as desired. The controller can be configured to display the servicing information irrespective of whether a service indicator or expired equipment service event timer has been detected.

While the illustrative service event routine 42 shown in FIG. 4 includes a particular sequence of events which occur during the routine 42, it should be understood that the particular order at which each step occurs can be altered, if desired. For example, the controller may be configured to perform each step in parallel, or in a sequence different from that illustrated in FIG. 4. In addition, one or more steps in the service event routine 42 may be eliminated, if desired, depending on type of controller employed.

FIG. 5 is a view of an illustrative controller 56 equipped with a user interface 58 for displaying servicing information when a service event is detected. In the illustrative embodiment of FIG. 5, user interface 58 includes a touch screen 60 configured to display information and transmit signals to and from the controller 56. Some examples of suitable touch screens 60 for use with the controller 56 may include resistive, capacitive, infrared or surface acoustic wave (SAW) type touch screens. The touch screen 60 may be either inset or recessed within a controller housing 62, as shown in FIG. 5, or may be provided as a separate component for use with a personal digital assistant (PDA), PC computer, or other remote device. In certain embodiments, the touch screen 60 can be provided as part of a liquid crystal display (LCD) panel, cathode ray tube (CRT), dot matrix display, or other suitable display device.

FIG. 6 is a pictorial view showing the illustrative controller 56 and user interface 58 of FIG. 5 during normal controller operation. As shown in FIG. 6, the touch screen 60 may be configured to display a main menu screen 64 that provides the user with information about the operational status of the controller 56, the current inside and outside temperature, the current time and day of week, the current heat and/or cool set point, as well as other operational information. The main menu screen 64 may be the default screen that appears on the touch screen 60 when the controller 56 is initially activated, after a loss of power has occurred, or after no activity has been detected by the user interface 58 for a certain period of time (e.g. after 1 minute of non-activity).

By pressing various icon buttons on the touch screen 60, the controller 56 can be configured to cycle through one or more menus or screens to view and, if desired, modify various operational settings within the controller 56. For example, the user can use the touch screen 60 to adjust the current temperature or humidity levels, change the clock or date settings on the controller 56, set a vacation schedule on the controller 56 that can be run while the user is away, etc. The touch screen 60 may also be used to check the status of the various system components connected to the controller 56.

FIG. 7 is a pictorial view showing the illustrative controller 56 and user interface 58 of FIG. 6 after a service event has been detected. As shown in FIG. 7, the controller 56 can be configured to display a service event display screen 66 on the touch screen 70 that informs the user that a service event has been detected. The service event display screen 66 may include, for example, a logo 68 and telephone number 70 indicating where to call for servicing or replacement. Other information in addition to, or in lieu of, the logo 68 and telephone number 70 may also be provided on the service event display screen 66, as desired. In some cases a service event code and/or short description of the service event may also be displayed, as shown at 69. The service event code may help a service technician diagnose the problem on the phone and possibly help provide a corrective action to the user via the phone. Also, the service event code may help the service technician determine what parts to order or bring to correct the problem.

A short description of the service event may help the user identify and possibly correct the problem. For example, if the service event was triggered as a result of the controller 56 determining that an equipment service event timer has expired, the controller 56 can be configured to display the particular device requiring service, and a recommended course of action. If, for example, an equipment service event timer for the filter has expired, the controller 56 can be configured to display the text “REPLACE FILTER” or other similar text on the touch screen 60, along with an appropriate logo, telephone number, and/or address for an authorized dealer of the filter, along with the part number of the filter, if desired. Similar messages can be displayed for other system components such as the humidifier pad, UV lamp, and batteries, as necessary.

The service event display screen 66 can be triggered when the controller 56 detects a fault in one or more of the system components, or when an equipment service event timer previously programmed in the controller 56 expires. In certain embodiments, the service event display screen 66 can be activated by the user by pressing one or more of the icon buttons on the touch screen 60, causing the controller 56 to display the desired servicing information on the screen 60.

FIG. 8 is a view of another illustrative controller 72 equipped with a user interface 74 for displaying servicing information when a service event is detected. In the illustrative embodiment of FIG. 8, user interface 74 includes a display panel 76 and a series of buttons 78, 80 that can be pressed by the user to scroll through various menus or screens displayable on the display panel 76. The display panel 76 can include any number of suitable display devices, including, for example, a backlit LCD panel or LED screen.

FIG. 9 is a pictorial view showing the illustrative controller 72 and user interface 74 of FIG. 8 during normal controller operation. As shown in FIG. 9, the controller 72 can be configured to display a main menu screen 82 on the display panel 76, similar to that described above with respect to FIG. 6.

As shown in FIG. 10, the controller 72 can be configured to display a service event display screen 82 on the display panel 76 that informs the user that a service event has been detected. The service event display screen 82 may include, for example, a logo 86 and telephone number 88 indicating where to call for servicing or replacement. Other information in addition to, or in lieu of, the contractor logo 86 and telephone number 88 may also be provided on the service event display screen 84, as desired.

The service event display screen 84 can be triggered when the controller 72 detects a fault in one or more of the system components, or when an equipment service event timer previously programmed in the controller 72 expires. In certain embodiments, the service event display screen 84 can be activated by the user by pressing one of the buttons 78, 80 (e.g. a help button 12), causing the controller 72 to display the desired servicing information on the display panel 76.

FIG. 11 is a block diagram of an illustrative HVAC controller having a user interface 28 with a display, and an external interface 27 for interfacing with an external data source 31. The HVAC controller shown in FIG. 11 may, in some cases, be similar in many respects to that shown and described with reference to FIG. 1. That is, the HVAC controller of FIG. 11 may be operatively connected to one or more system components, such as, for example, a heating unit, a cooling unit, a ventilation unit, a filtration unit, a UV lamp unit, a humidifying/dehumidifying unit, and/or one or more local and/or remote sensors, as discussed with respect to FIG. 1. In some cases, the HVAC controller may be a thermostat.

The illustrative HVAC controller of FIG. 11 may have a controller 12 that is connected to the user interface 28. The controller 12 may any suitable controller such as a microprocessor, a microcontroller or the like. The user interface 28 may include a display such as a touch screen display. In some cases, the user interface 28 may include a display and one or more buttons, knobs, dials or other user input devices. The display of the user interface 28 may be, for example a liquid crystal display (LCD), a dot matrix display, a plasma display, and/or any other suitable type of display, preferably capable of displaying electronic images.

In the illustrative embodiment, the controller 12 is shown coupled to an external interface 27. The external interface 27 may be adapted to provide an interface between the controller 12 and an external data source 31. The controller 12 may in some instances have a memory, and the external interface 27 may facilitate uploading and/or downloading data between the controller 12 and the external data source 31.

In one illustrative embodiment, the external interface 27 may facilitate uploading electronic images from an external data source 31 to the controller 12, and the controller 12 may display the electronic images files on the display of the user interface 28. For example, the one or more electronic images that are uploaded from the external data source 31 may be displayed on the display of the user interface 28 as a background image (i.e. wallpaper image), an image on only part of the display, as a sequence of slide show images, a screensaver image, a scrolling text line image, and/or any other suitable image as desired. The electronic images may include still images, video images, text images, computer generated images, flash player images, or any other suitable image or image sequence, as desired. The electronic images may be in a JPEG, GIF, BMP, TIFF, PNG, WMF, PCX, MPEG, SWF (Adobe Flash), SCR (Windows™ Screen Saver Format), or any other suitable format.

External interface 27 may include a wired and/or wireless interface. For example, the external interface 27 may include a wired connector interface, a wireless interface (e.g. an optical interface and/or an RF interface), or any other suitable interface, as desired. For example, the wired connector interface may include one or more of a Universal Serial Bus (USB) interface, an Ethernet interface, a FireWire interface, a digital camera or cellular phone interface, and/or any other suitable electronic interface or interfaces, as desired. In some cases, the wired connector interface may include a port or connector for accepting one or more removable flash memories. Example removable flash memories include Compact Flash (CF), Secure Digital (SD), MicroSD, XD, thumb drives, and/or any other suitable removable memory, as desired.

When provided, the wireless interface may include, for example, a radio frequency (RF) wireless interface, an infrared wireless interface, a microwave wireless interface, and/or any other suitable wireless interface, as desired. In some cases, the wireless interface may operate according to one or more wireless protocols, such as, for example, a cellular communication protocol, the ZigBee protocol, the Bluetooth protocol, the WiFi protocol, an IrDA protocol, a dedicated short range communication (DSRC) protocol, the EnOcean protocol, and/or any other wireless protocol, as desired.

The external data source 31 may be any suitable data source that is capable of interfacing with the external interface 27. For example, the external data source 31 may be computer, a network (e.g. private network or World Wide Web), a cell phone, a PDA, a removable flash memory, or any other external data source, as desired. It is contemplated that the controller 12 may upload data from the external data source 31 and/or download data to the external data source 31 via the external interface 27.

In some cases, the controller 12 may upload one or more electronic images from the external data source 31, and then display the uploaded electronic images on the display of the user interface 28. In one instance, controller 12 may include a memory (internal and/or external) for storing at least one of the one or more electronic images uploaded from the external data source 31. In some cases, the memory of the controller 12 may be RAM, ROM, EEPROM, Flash memory, and/or any other suitable type of memory, as desired. In some cases, the controller 12 may be configured to read at least one electronic image stored in the external data source 31, before displaying the at least one electronic image on the display of the user interface 28.

In some embodiments, the memory of the controller 12 may only store a subset of the electronic images to be displayed, with the remainder of the electronic images stored on the external data source 31. During operation, the controller 12 may read up a desired electronic image or set of electronic images from the external data source 31, and display the electronic images or set of electronic images on the display of the user interface 28. Once displayed, the controller 12 may read up another desired electronic image or set of electronic images from the external data source 31, and display the other electronic images or set of electronic images on the display of the user interface 28. This may reduce the memory requirements of the controller 12, by using the external data source 31 as a storage medium. However, the external data source 31 may need to remain connected to the external interface 27 during operation.

In one specific example, it is contemplated the external data source 31 may include electronic images from, for example, a digital camera. When uploading such electronic images to the controller 12, the controller 12 may receive a first electronic image from the external data source 31, such as, for example, a removable flash memory, and display the first electronic image on the user interface 28. Then, controller 12 may receive a second electronic image from the external data source 31 and display the second electronic image on the user interface 28. This illustrative embodiment may use the external data source 31 as a storage medium for storing some or all of the electronic images while the controller 12 selects and/or displays the electronic images on the display of the user interface 28.

In another illustrative embodiment, the controller 12 may read up the desired electronic images from the external data source 31, and store the electronic images in a local memory that is accessible by controller (internal and/or external to the controller by within the HVAC controller). Then, during operation, the controller 12 may read up a desired electronic image from the local memory, and display the electronic images on the display of the user interface 28. In this illustrative embodiment, the external data source 31 may not need to remain connected during operation.

In one specific example, it is contemplated the external data source 31 may include electronic images from, for example, a digital camera. The controller 12 may upload and store a number of electronic images from the external data source 31, and in some cases all of the electronic images, and then display one or more of the uploaded electronic images on the display of the user interface 28. In this illustrative embodiment, the external data source 31 may not be used by the controller 12 as storage medium after the electronic images have been uploaded to the controller 12 and while the controller 12 selects and/or displays the electronic images on the display of the user interface 28.

In some cases, the controller 12 may download electronic images and/or other information to the external data source 31 via the external interface 27. For example, the controller 12 may download one or more electronic images to the external data source 31, and the external data source 31 may then be used to upload the one or more electronic images to another device, such as another HVAC controller, a computer, a PDA and/or any other suitable device. Alternatively, or in addition, the controller 12 may download one or more programming parameters, such as set points, schedules, confirmation information, or any other information to the external data source 31, and the external data source 31 may then be used to upload the information to another device, such as another HVAC controller, a computer, a PDA and/or any other suitable device.

In some embodiments, controller 12 may include an image selection tool to help a user in selecting which of the at least one electronic images to display on the display of the user interface 28. In some cases, the image selection tool may display thumbnail images of the at least one electronic images on the user interface 28 to aid a user in selecting which of the electronic images to display on the user interface 28, and in some cases for what purpose. In other cases, the image selection tool may display a list of the at least one electronic images on the user interface 28 to aid the user in selecting which of the electronic images to display on the user interface 28, and in some cases for what purpose. It is contemplated that the controller may provide one or more menus on the display of the user interface 28 to help the user upload, download, categorize, select, organize, move, delete, customize or otherwise work with the available electronic images.

In some illustrative embodiments, the controller 12 may be configured to select and display one of at least two electronic images according to one or more parameters of the HVAC controller. Example parameters may include a time of day related parameter, a date related parameter, a season related parameter, an operating mode related parameter, an outside temperature related parameter, an inside temperature related parameter, a ventilation related parameter, a schedule related parameter, a schedule period parameter, a local weather parameter, a parameter related to the birthday, anniversary and/or another special day of a user of the HVAC controller, and/or any other suitable parameter, as desired.

In one example, the controller 12 may be programmed to select and display a particular electronic image depending on the state or value of a parameter of the HVAC controller. For example, a first electronic image may be displayed when rainy weather is predicted, a second electronic image may be displayed when sunny weather is predicted, a third electronic image may be displayed when cloudy weather is predicted, and a fourth electronic image may be displayed when snowy weather is predicted. In this example, if the weather is predicted to be rainy, controller 12 may select and display the first electronic image, if the weather is predicted to be sunny, the controller 12 may display the second image, and so on.

In another example, it is contemplated that different electronic images may be associated with each of the four seasons of the year, and displayed accordingly. In another example, one or more electronic images may be associated with at least some holidays, such as, for example, Christmas, Halloween, 4^thof July, Easter, and/or any other holiday, as desired. In yet another example, one or more electronic images may be associated with the time or period of a day. For example, the controller 12 may have an electronic image associated with each of a wake, a leave, a return, and a sleep period of a thermostat schedule. Then, the controller 12 may display the associated images during the corresponding periods of the thermostat schedule. More generally, it is contemplated that one or more electronic images may be associated with any suitable parameter of the HVAC controller, as desired, and displayed accordingly.

In some cases, it is contemplated that the controller 12 may display regularly updated electronic images or other information, such as, for example, weather, traffic and/or news information. In some cases, the controller may be in communication with the World Wide Web (WWW) or some other information source via external interface 27. In this example embodiment, the controller 12 may display weather information as the weather changes including providing electronic images associates with severe weather alerts and/or radar images (including radar loops if desired). Alternatively, or in addition, the controller 12 may provide electronic images of news information, such as, for example, top news stories, which may be retrieved by one or more media organizations via a wired or wireless network (e.g. the WWW).

More specifically, controller 12 may be configured to upload updated weather information, such as local or national weather forecasts, radar information, and/or severe weather alerts. In another example, controller 12 may be configured to upload updated news information, such as, for example, top news stories, local headlines, national headlines, world headlines, sports headlines, business headlines, or any other news data, as desired. In some cases, the user may enter information related to the location of the thermostats and/or information related to his/her interests, and the controller 12 may then displayed information that is most relevant to the user's location and/or interests on the display of the user interface 28.

In some cases, the controller 12 may be configured to upload one or updates to the controller software and/or operating system from the external data source 31, and then install the updated controller software and/or operating system on the controller 12. The software updates may, in some cases, be or include firmware updates. The software updates may correct known bugs, improve performance, add functionality, and/or otherwise improve the operation of the controller 12.

FIGS. 12-13 are pictorial views showing an illustrative HVAC controller 100 and user interface 106 having a background image displayed on part of the display. In the illustrative embodiment, user interface 106 includes an LCD touch screen 102 configured to display information and transmit signals to and from the controller 100. Some examples of suitable touch screens 102 may include resistive, capacitive, infrared or surface acoustic wave (SAW) type touch screens. The touch screen 102 may be either inset or recessed within a controller housing 110, as shown in FIG. 12. In certain embodiments, the touch screen 102 can be provided as part of a liquid crystal display (LCD) panel, cathode ray tube (CRT), dot matrix display, or any other suitable display device.

In the illustrative embodiment of FIG. 12, the touch screen 102 may be configured to display a main menu screen 108 that provides the user with information about the operational status of the HVAC controller 100, the current inside and outside temperature, the current time and day of week, the current heat and/or cool set point, as well as other operational information. The main menu screen 108 may be the default screen that appears on the touch screen 102 when the controller 100 is initially activated, after a loss of power has occurred, or after no activity has been detected by the user interface 106 for a certain period of time (e.g. after 1 minute of non-activity).

By pressing various icon buttons on the touch screen 102, the controller 100 can be configured to access one or more sub-menus or screens to view and, if desired, modify various operational settings of the HVAC controller 100. For example, the user may use the touch screen 102 to adjust the current temperature or humidity levels, change the clock or date settings of the controller 100, set a vacation schedule on the controller 100 that can be run while the user is on vacation, etc. In the illustrative embodiment, the touch screen 102 may also be used to check the status of the various system components connected to the HVAC controller 100.

In the illustrative embodiment, touch screen 102 may be configured to display an electronic image 104 as a background image, or wallpaper, on the display. The electronic image 104 is illustrated in dashed lines in FIG. 12. The electronic image 104 may be uploaded onto the controller 100 via an external interface (see FIG. 11), or, in other cases, the electronic image 104 may be preloaded onto the controller 100, if desired. As illustrated, the one or more thermostat parameters may be displayed on top of at least a portion of the background image 104. In the illustrative example, the one or more thermostat parameters that are displayed on top of the background image 104 include a date/time parameter, an outdoor temperature parameter, a HVAC status parameter and an inside temperature parameter. However, these are only illustrative in nature.

As illustrated, the electronic image 104 can be displayed on the main menu screen 108. It is contemplated that the electronic image 104 may be displayed on only the main menu screen 108 of the controller, or on the main menu screen 108 and at least some of one or more sub-menus or screens of the controller 100, as desired. In some cases, electronic image 104 may be displayed on only a portion of touch screen 102, as shown. However, in other cases, it is contemplated that electronic image 104 may be displayed on substantially the entire area of the touch screen 102 display, if desired.

It is contemplated that the controller 100 may be configured to display regularly updated news and/or weather information in a display box or region (not shown) on the display. For example, touch screen 102 may include a box or region including, for example, scrolling text displaying the regularly updated electronic images and/or data, such as in a crawl along a top or bottom of the of the display screen. Alternatively, the regularly updated electronic images and/or data may be displayed as a background image, or wallpaper, on the display, if desired.

FIG. 13 is similar to FIG. 12, with the controller 100 having a user interface 106 displaying an electronic image 112 as a background image, or wallpaper. In the illustrative embodiment, information about the operational status of the controller 100, the current inside and outside temperature, the current time, date, and day of week, the current heat and/or cool set point, the humidity, as well as other operational information may be displayed on top of the electronic image 112, if desired. In the illustrative example, the electronic image 112 shows clouds. However, it is contemplated that any suitable electronic image 112 may be used, as desired.

FIG. 14 is a pictorial view showing another illustrative controller 100 and user interface 106 having an electronic image 114 displayed on only part of the display. In the illustrative embodiment, the touch screen 102 includes a first region and a second region. The first region of the touch screen 102 may display the electronic image 114 as a background image. The second region of the touch screen 102 may display one or more operational parameters, such as thermostat parameters. In the illustrative embodiment, the first region and the second region may not overlap, but this is not required. In some cases, it is contemplated that at least some of the one or more thermostat parameters may overlap or overlay a portion of the electronic image 114 as shown in FIGS. 12-13, but this is not required or even desired in some embodiments.

In the illustrative example, the first region displaying the electronic image 114 is illustrated as containing a left side of the touch screen 102. However, it is contemplated that the first region may be positioned on the right side of the touch screen 102, in the middle of the touch screen 102 having the one or more thermostat parameters on both the right and left side of the first region, along the top and/or bottom of the touch screen 102, or any other suitable position, as desired.

FIG. 15 is a schematic view of an illustrative controller 100 and user interface 106 displaying a plurality of electronic images 116, 118, 120 in a slide show format. Again, the electronic images are illustrated in dashed lines, with subsequently displayed electronic images illustrated below the controller 100. In the illustrative embodiment, the controller 100 may be configured to sequentially display two or more electronic images 116, 118, and 120 on at least a portion of the touch screen 102. In some cases, the sequential display may be in slide show format. In some cases, it is contemplated that the slide show may function as a screensaver for the controller 100, and may automatically activate after a period of no user interaction.

In some illustrative embodiments, the user may select which electronic images to include in the slide show. However, in other cases, the controller 100 may select the electronic images to include in the slide show, such as all available electronic images, or some portion thereof. In some cases, the electronic images 116, 118, 120 may be selected from a group of uploaded and/or preloaded electronic images, if desired.

Once the user has selected the electronic images 116, 118, 120, or the controller 100 has determined the electronic images 116, 118, 120 to display, an order of display may be determined. In some cases, the user may select the order of display, while in other cases, the controller 100 may determine the order. For example, the order of display may be random, by date, by file name, etc., if desired. In some cases, the controller 100 may be configured to allow a user to select which of the electronic images 116, 118, 120 will be shown more often (e.g. given priority) in the slide show format than other available electronic images.

As indicated above, and in some illustrative embodiments, the slide show may function as a screen saver for the controller 100. That is, the slide show may be automatically initiated after a period of non-use by the user. In other cases, the slide show may be initiated by a user command, a time of day, a programmed schedule of the controller 100, or at any other suitable time.

During operation, and in the illustrative embodiment, the controller 100 may sequentially display the plurality of electronic images 116, 118, 120 on the display. The sequential display may display a first electronic image 116 for a period of time. In some cases, the period of time may be selectable by the user. Then, the controller may display a second electronic image 118 for a period of time, and so forth until the controller 100 display a last electronic image 120. Then, and in some cases, the slide show may be repeated, or the slide show may terminate, as desired.

As noted above, the controller 100 may display each electronic image 116, 118, 120 for a period of time. In some cases, the period of time may be in the range of 1 second to 5 minutes, such as, for example, 1 second, 2 seconds, 3 seconds, 10 seconds, 20 seconds, 30 seconds, or 1 minute. However, it is contemplated that any suitable period of time may be used, as desired. The period of time that an electronic image is displayed may be about the same for each image, but this is not required.

In some embodiments, the slide show may have a transition between electronic images, such as, for example, a slide show effect. The slide show effects may include, but is not limited to, a fade effect, a dissolve effect, a shutter effect, a cross-comb effect, a mask effect, a brick effect, a fly-in effect, as well as many other slide show effects. In some embodiments, the slide show effect may vary throughout the slide show, but this is not required.

It is contemplated that the controller 100 may display one or more parameters of the controller 100 during the slide show. For example, and as illustrated in FIG. 15, the controller 100 may include a parameter box 122 displayed on a portion of the touch screen 102 during the slide show. In the illustrative example, the parameter box 122 is positioned across the bottom of the touch screen 102. However, it is contemplated that a parameter box 122 may be positioned on the top, right side, left side, or in any other suitable location on the touch screen, as desired. More generally, it is contemplated that one or more parameters of the controller 100 may be displayed in any suitable manner during the slide show, if desired. It is also contemplated that a previous and/or next button may be provided on the touch screen 102 during the slide show. The previous and/or next buttons may allow the user to manually sequence through the slide show.

FIG. 16 is an illustrative view of an illustrative controller 100 having a screensaver. The embodiment of FIG. 16 is similar to that of FIG. 15 except instead of having a slide show of electronic images, the screensaver may include one electronic image 124, such as, for example, a digital still image, a video, an electronic animation, or any other suitable electronic image, as desired. In some cases, the electronic image 124, again illustrated in dashed lines, may be uploaded to the controller 100 via the external interface 27 (see FIG. 11). When an animation is provided, the animation may include a scrolling marquee, 3D boxes, flying objects, moving/changing shapes, and/or any other suitable animation, as desired. In some cases, the screensaver may be downloaded from the World Wide Web, or provided to the controller 100 by way of a removable memory card, as desired. In some cases, the particular electronic image 124 used for the screen saver may be selected by the user, and/or in some cases, may depend on one or more current parameters of the controller 100, if desired.

FIGS. 17A-17F are illustrative pictorial views of a controller having a menu for selecting electronic images for display. FIG. 17A is an illustrative view of a controller 100 displaying a menu 130 after selecting the “Menu” option of FIG. 13. The illustrative menu 130 may include multiple options to control various settings of controller 100. For example, there may be a set/create schedule option, a vacation option, a humidification option, a dehumidification option, a system information option, a date/time option, a preferences option, a temporary schedule option, a schedule fan option, a security settings option, an installer set up option, as well as any other settings option, as desired.

If the preferences option of menu 130 is selected, menu 132 as shown in FIG. 17B may be displayed. Menu 132, or the preference option menu, may include many controller preferences, such as, for example, a reminders option, a Fahrenheit/Celsius option, a 12h/24h clock option, a display option, a language option, a schedule option, an adaptive intelligent recovery option, a restore energy star settings option, a wireless device manager option, a daylight savings time option, as well as any other preference option, as desired. As illustrated, menu 132 may also include a previous menu option to return to menu 130 of FIG. 17A, if desired.

If the display option of menu 132 is selected, menu 134, as shown in FIG. 17C, may be displayed. Menu 134, or the display option menu, may include many options that may control display settings. For example, menu 134 may include a backlight option, a contrast option, a screensaver option, a wallpaper option, as well as many other display options, as desired. In some cases, as illustrated, menu 134 may include a previous menu option to return to menu 132 of FIG. 17B, and a help option that may display help information related to the use of the display option of menu 132.

When the screensaver option of menu 134 is selected, menu 136, as shown in FIG. 17D, may be displayed. Menu 136, or the screensaver settings menu, may include settings to control the screensaver for the controller 100. For example, menu 136 may include a screensaver timeout setting that may be adjusted by the user to increase or decrease the screensaver timeout time. For example, the screensaver timeout time may range from 1 minute to 90 minutes. However, it is contemplated that any suitable time may be used, as desired.

In some cases, menu 136 may also include an image option 137. The image option 137 may control the settings of the one or more electronic images that are displayed by the screensaver, and in some cases, the desired screensaver effects (e.g. single image screen saver, slideshow, animation, etc.). Additionally, in some embodiments, menu 136 may include a cancel option, a help option, and a done option. In some cases, though not explicitly illustrated in FIG. 17D, menu 136 or image option 137 may include a transition option that may control the settings of the transitions or slide show effects between electronic images of the screensaver, if a slide show is desired.

If the image option 137 of menu 136 is selected, menu 138, as shown in FIG. 17E may be displayed. Menu 138 may include one or more thumbnails 142 or icons, each corresponding to one or more electronic images uploaded and/or preloaded onto controller 100. With menu 138 displayed, a user may select one or more desired images for use by a slide show and/or screensaver by selecting one or more thumbnails 142. To select a thumbnail 142, a user may simply touch the touch screen 102 on the thumbnail 142 highlighting the thumbnail 142. To deselect a selected electronic image, a user may touch the touch screen 102 on the selected thumbnail 142, removing the highlighting from the thumbnail 142. Once all the desired thumbnails 142 are selected, the user may select “Done” to save the settings in memory. If a user does not want the settings saved, the user may select “Cancel” to exit the menu 138.

If in menu 134 of FIG. 17C, a wallpaper setting option is selected, a menu similar to menu 138 may be displayed allowing the user to select one or more thumbnails for the wallpaper image, as desired. Furthermore, menu 138, or any other suitable menu, may include an option to display a thumbnail or icon for one or more regularly updated electronic images from the World Wide Web or other information source on the touch screen 102 display, as desired. For example, a thumbnail or icon may be presented for displaying regularly updated weather, news, or any other information, and sometimes an option to select the format, as desired.

Additionally, in some cases, there may be an additional menu option to select the format for the wallpaper, such as, for example, the entire display wallpaper or split display wallpaper with the electronic image in a first region and the controller 100 parameters in a second region, as described with respect to FIG. 14.

As an alternative to FIG. 17E, menu 140 may be provided when selecting the image option of menu 136 and/or the wallpaper option of menu 134, if desired. Menu 140 may provide a list of electronic images that may be selected to display in the screensaver and/or wallpaper. In the illustrative embodiment, the list may include a box next to each electronic image indicating if the image is selected. Alternatively, the image name may be highlighted in the list if selected. However, it is contemplated that any suitable method of selecting the image(s) may be used, as desired.

In some cases, menu 138 and/or menu 140 may include an option to preview an image full size on the display. For example, tapping on the touch screen 102 twice in a rapid manner may expand the thumbnail 142 or list item to a full screen preview. Furthermore, it is contemplated that any suitable method of creating a full screen preview may be used, as desired. Once all the desired electronic images are selected, a user may select the “Done” option to store the settings in controller 100 memory.

It is also contemplated that a menu may be provided for selecting a theme or skin for the user interface of the controller 100. A theme typically includes a set of colors, sounds, images, icons, screensavers, and/or background images that are consistent with a specified theme. For example, one illustrative theme may include a Halloween theme, where the set of colors, sounds, images, icons, screensavers, and/or background images that consistent with a Halloween theme. In a theme, the size and locations of the menus, parameter and other features of the user interface are typically not changed. A skin is typically changes the size and locations of the menus, parameter and other features of the user interface. For example, one illustrative skin may include a star wars skin, wherein the size, shape and locations of the menus, parameter and other features of the user interface are changed to reflect a star wars feel. In some illustrative embodiments, one or more themes and/or skins may be uploaded to the controller 100 via the external interface 27 (see FIG. 11), and a menu similar to that shown in FIGS. 17E-17F may be used to select a theme or skin for use by the controller 100.

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.

	Number	Date	Country
Parent	10726243	Dec 2003	US
Child	11752816	May 2007	US

	Number	Date	Country
Parent	11752816	May 2007	US
Child	11840290	Aug 2007	US

THERMOSTAT WITH ELECTRONIC IMAGE DISPLAY

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

US Classifications

International Classifications

Abstract

Description

Claims

Parent Case Info

Continuations (1)

Continuation in Parts (1)