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 having a programmable service event display mode.
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 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 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 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 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 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 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.
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 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
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
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
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
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
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.
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.
As shown in
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), causing the controller 72 to display the desired servicing information on the display panel 76.
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.
The present application is a Continuation of U.S. patent application Ser. No. 10/726,243 filed Dec. 2, 2003.
Number | Name | Date | Kind |
---|---|---|---|
4079366 | Wong | Mar 1978 | A |
4174807 | Smith et al. | Nov 1979 | A |
4206872 | Levine | Jun 1980 | A |
4224615 | Penz | Sep 1980 | A |
4264034 | Hyltin et al. | Apr 1981 | A |
4298946 | Hartsell et al. | Nov 1981 | A |
4308991 | Peinetti et al. | Jan 1982 | A |
4337822 | Hyltin et al. | Jul 1982 | A |
4382544 | Stewart | May 1983 | A |
4386649 | Hines et al. | Jun 1983 | A |
4388692 | Jones et al. | Jun 1983 | 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 |
4606401 | Levine et al. | Aug 1986 | A |
4621336 | Brown | Nov 1986 | A |
4622544 | Bially et al. | Nov 1986 | A |
4717333 | Carignan | Jan 1988 | A |
4725001 | Carney et al. | Feb 1988 | A |
4819714 | Otsuka et al. | Apr 1989 | A |
4837731 | Levine et al. | Jun 1989 | A |
4881686 | Mehta | Nov 1989 | A |
4918439 | Wozniak et al. | Apr 1990 | A |
4948040 | Kobayashi et al. | Aug 1990 | A |
4992779 | Sugino et al. | Feb 1991 | A |
4997029 | Otsuka 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 |
5140310 | DeLuca et al. | Aug 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 |
5329991 | Mehta et al. | Jul 1994 | A |
5348078 | Dushane et al. | Sep 1994 | A |
5386577 | Zenda | Jan 1995 | A |
5395042 | Riley et al. | Mar 1995 | A |
5482209 | Cochran et al. | Jan 1996 | A |
5526422 | Keen | Jun 1996 | A |
5537106 | Mitsuhashi | Jul 1996 | A |
5566879 | Longtin | Oct 1996 | A |
5570837 | Brown et al. | Nov 1996 | A |
5673850 | Uptegraph | Oct 1997 | A |
5682206 | Wehmeyer et al. | Oct 1997 | A |
5782296 | Mehta | Jul 1998 | A |
5818428 | Eisenbrandt et al. | Oct 1998 | A |
5841112 | Brooks et al. | Nov 1998 | A |
5873519 | Beilfuss | Feb 1999 | A |
5877957 | Bennett | Mar 1999 | A |
5886697 | Naughton et al. | Mar 1999 | A |
5901183 | Garin et al. | May 1999 | A |
5902183 | D'Souza | May 1999 | A |
5937942 | Bias et al. | Aug 1999 | A |
5947372 | Tiernan | Sep 1999 | A |
6020881 | Naughton et al. | Feb 2000 | A |
6032867 | Dushane et al. | Mar 2000 | A |
6059195 | Adams et al. | May 2000 | A |
6064310 | Busak 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 |
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 |
6285912 | Ellison et al. | Sep 2001 | B1 |
6290140 | Pesko et al. | Sep 2001 | B1 |
6315211 | Sartain et al. | Nov 2001 | B1 |
6318639 | Toth | 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 |
6466132 | Caronna et al. | Oct 2002 | B1 |
6478233 | Shah | Nov 2002 | B1 |
6502758 | Cottrell | Jan 2003 | B2 |
6518957 | Lehtinen et al. | Feb 2003 | B1 |
6578770 | Rosen | Jun 2003 | B1 |
6580950 | Johnson et al. | Jun 2003 | B1 |
6581846 | Rosen | Jun 2003 | B1 |
6595430 | Shah | Jul 2003 | B1 |
6608560 | Abrams | Aug 2003 | B2 |
6619555 | Rosen | Sep 2003 | B2 |
6621507 | Shah | Sep 2003 | B1 |
6736112 | Ho | May 2004 | B2 |
6741915 | Poth | May 2004 | B2 |
6786421 | Rosen | Sep 2004 | B2 |
6789739 | Rosen | Sep 2004 | B2 |
6824069 | Rosen | Nov 2004 | B2 |
6868293 | Schurr et al. | Mar 2005 | B1 |
6967565 | Lingermann | Nov 2005 | B2 |
7000849 | Ashworth et al. | Feb 2006 | B2 |
7047092 | Wimsatt | May 2006 | B2 |
7050026 | Rosen | May 2006 | B1 |
7152806 | Rosen | Dec 2006 | B1 |
7156318 | Rosen | Jan 2007 | B1 |
7225054 | Amundson et al. | May 2007 | B2 |
20010029585 | Simon et al. | Oct 2001 | A1 |
20010042684 | Essalik et al. | Nov 2001 | A1 |
20010052459 | Essalik et al. | Dec 2001 | A1 |
20020005435 | Cottrell | Jan 2002 | A1 |
20020092779 | Essalik et al. | Jul 2002 | A1 |
20020180590 | Abrams | Dec 2002 | A1 |
20030034897 | Shamoon et al. | Feb 2003 | A1 |
20030034898 | Shamoon et al. | Feb 2003 | A1 |
20030121652 | Carey et al. | Jul 2003 | A1 |
20030123224 | LaCroix et al. | Jul 2003 | A1 |
20030136135 | Kim et al. | Jul 2003 | A1 |
20030142121 | Rosen | Jul 2003 | A1 |
20030150926 | Rosen | Aug 2003 | A1 |
20030150927 | Rosen | Aug 2003 | A1 |
20030195640 | Krocker et al. | Oct 2003 | A1 |
20040074978 | Rosen | Apr 2004 | A1 |
20040193324 | Hoog et al. | Sep 2004 | A1 |
20040245352 | Smith | Dec 2004 | A1 |
20050040247 | Pouchak | Feb 2005 | A1 |
20050040249 | Wacker et al. | Feb 2005 | A1 |
20050103875 | Ashworth et al. | May 2005 | A1 |
20070057079 | Stark et al. | Mar 2007 | A1 |
20070278320 | Lunacek et al. | Dec 2007 | A1 |
Number | Date | Country |
---|---|---|
3334117.6 | Apr 1985 | DE |
0678204 | Mar 2000 | EP |
0985994 | Mar 2000 | EP |
1074009 | Feb 2001 | EP |
11159846 | Jun 1999 | JP |
9711448 | Mar 1997 | WO |
9739392 | Oct 1997 | WO |
0152515 | Jul 2001 | WO |
0179952 | Oct 2001 | WO |
Number | Date | Country | |
---|---|---|---|
20070225869 A1 | Sep 2007 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 10726243 | Dec 2003 | US |
Child | 11752816 | US |