Apparatus and method for storing event information for an HVAC system

Information

  • Patent Grant
  • 8713697
  • Patent Number
    8,713,697
  • Date Filed
    Wednesday, July 9, 2008
    16 years ago
  • Date Issued
    Tuesday, April 29, 2014
    10 years ago
Abstract
An apparatus for storing event information relating to operation of an HVAC system includes: (a) at least one memory controller coupled with the HVAC system for receiving the event information; and (b) at least one memory unit coupled with the at least one memory controller. A first memory unit of the at least one memory unit is configured for receiving first selected information of the event information for accessing by at least one of a first party and a second party. A second memory unit of the at least one memory unit is configured for receiving second selected information of the event information for accessing by the second party.
Description
BACKGROUND OF THE INVENTION

The present invention is directed to heating ventilating air conditioning (HVAC) systems, and especially to collection of event or operation data or information in HVAC systems.


Users of HVAC systems such as, by way of example and not by way of limitation, homeowners may prefer that only minimal information be displayed or otherwise presented to them to inform them of details regarding operation of the HVAC system. Too much information may be confusing or frustrating to a homeowner. Further, there is little need for a homeowner to remember when certain events may have occurred.


In contrast, greater detail of information regarding operation or events regarding the HVAC system, including when events may have occurred, may be quite valuable to a serviceman seeking to diagnose or debug a problem. Generally speaking, the more information that may be made available regarding operation of an HVAC system, the easier it is to service the system, and the easier it is to develop improvements to the system.


The information is from a common system and may be collected at the same time, but it would be advantageous to present different presentations of the information—a less detailed version to a user, and a more detailed version to a serviceman or other professional.


There is a need for an apparatus and method for storing event information for an HVAC system that can present differing levels of information detail to different users.


SUMMARY OF THE INVENTION

An apparatus for storing event information relating to operation of an HVAC system includes: (a) at least one memory controller coupled with the HVAC system for receiving the event information; and (b) at least one memory unit coupled with the at least one memory controller. A first memory unit of the at least one memory unit is configured for receiving first selected information of the event information for accessing by at least one of a first party and a second party. A second memory unit of the at least one memory unit is configured for receiving second selected information of the event information for accessing by the second party.


A method for storing event information relating to operation of an HVAC system includes: (a) providing at least one memory controller coupled with the HVAC system for receiving the event information; (b) providing at least one memory unit coupled with the at least one memory controller; (c) in no particular order: (1) configuring a first memory unit of the at least one memory unit for storing first selected information of the event; and (2) configuring a second memory unit of the at least one memory unit for storing second selected information of the event information; and (d) in no particular order: (1) operating the first memory unit for permitting access to the first selected information by at least one of a first party and a second party; and (2) operating the second memory unit for permitting access to the second selected information by the second party.


It is, therefore, a feature of the present invention to present an apparatus and method for storing event information for an HVAC system that can present differing levels of information detail to different users.


Further features of the present invention will be apparent from the following specification and claims when considered in connection with the accompanying drawings, in which like elements are labeled using like reference numerals in the various figures, illustrating the preferred embodiments of the invention.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 is a schematic diagram of a first embodiment of the apparatus of the invention.



FIG. 2 is a flow chart illustrating treatment of event information in the embodiment of the apparatus illustrated in FIG. 1.



FIG. 3 is a schematic diagram of a second embodiment of the apparatus of the invention.



FIG. 4 is a flow chart illustrating treatment of event information in the embodiment of the apparatus illustrated in FIG. 3.



FIG. 5 is a flow diagram illustrating treatment of a reset event in the embodiment of the apparatus illustrated in FIG. 3.



FIG. 6 is a schematic diagram of a third embodiment of the apparatus of the invention.



FIG. 7 is a flow chart illustrating treatment of event information in a first buffer unit of the embodiment of the apparatus illustrated in FIG. 6.



FIG. 8 is a flow diagram illustrating treatment of a reset event in a first buffer unit of the embodiment of the apparatus illustrated in FIG. 6.



FIG. 9 is a flow chart illustrating treatment of event information in a second buffer unit of the embodiment of the apparatus illustrated in FIG. 6.



FIG. 10 is a flow diagram illustrating treatment of a reset event in a second buffer unit of the embodiment of the apparatus illustrated in FIG. 6.





DETAILED DESCRIPTION

A new apparatus and method for storing and displaying operational event information such as, by way of example and not by way of limitation, error codes in an HVAC system involves having two memory buffers storing the event information. The HVAC system may be a communicating HVAC system included in a communicating HVAC network involving a plurality of HVAC systems. The present invention may be employed in some or all of the HVAC systems in an HVAC network.


Generally, a first buffer stores all operational information, such as by way of example and not by way of limitation, events, error codes or alarms present in the system. Each event may be identified with time stamping or storage may be effected in a chronological order. A further option may be to record consecutive, substantially identical events as one entry with an event counter associated with the entry to count the number of times the same event is consecutively presented.


A second buffer is preferably independent of the first buffer. The second buffer may store the same information that is stored in the first buffer. Time stamps or chronological storing may be employed in the second buffer. The second buffer substantially duplicates the information stored in the first buffer. However, information in the second buffer is preferably not reset when the primary buffer is reset. It may be advantageous to provide that the second buffer store any resetting of the primary buffer as an event. It is preferred that access to the second buffer be controlled to limit disclosure of information stored in the second buffer to authorized persons. Access to information stored in the second buffer may require use of a non-published, secret access code or another access control arrangement.


Either of the first and second buffers can store information in RAM (Random Access Memory) or in a non-volatile memory independently of each other. The first and second buffers may reside on the same HVAC system or may reside on different HVAC systems.


Preferably, both of the first and second buffers may be reset and cleared independently of each other by the person or an apparatus servicing the HVAC system or clearing of an individual device in an HVAC system in which the buffers may reside.


Buffer content for either of the first and second buffers preferably may be displayed in a human-readable form on any appropriate device in an HVAC system including, by way of example and not by way of limitation, a thermostat, zoning panel, furnace controller or any other control with a human-machine interface able to display information.


Buffer content may also be displayed on a remote device with human-machine interface such as a thermostat, home security panel, home automation panel, a personal digital assistant, a cellular phone, a wireless phone, a personal computer, a television set any other device connected to the HVAC system over a proprietary or common communicating interface such as wired or wireless Ethernet connection, Universal Serial Bus connection, RS-232 connection or other interface.



FIG. 1 is a schematic diagram of a first embodiment of the apparatus of the invention. In FIG. 1, an information storing system 10 for an HVAC (Heating Ventilating Air Conditioning) system includes a memory controller 12 and a memory section 14. Memory section 14 includes a first memory unit 16 and a second memory unit 18. Second memory unit 18 includes a plurality of memory sites 1, 2, 3, . . . K−2, K−1, K, . . . N−2, N−1, N. First memory unit 16 is a virtual memory unit having pointers 20, 22. Pointer 20 is a beginning pointer that remains pointed at memory site 1 to mark the beginning of first memory unit 16, so long as there is data stored in first memory unit 16. Pointer 22 is an ending pointer that points to the memory site containing the earliest-stored event within memory sites 1 through K.


Event data is provided to memory controller 12 from a host HVAC system (not shown in FIG. 1) via an event data input locus 11. Memory controller 12 also has a RESET locus 15 via which memory controller 12 may receive RESET signals. A RESET signal may cause memory controller 12 to move pointers 20, 22 to positions not indicating any data in second memory unit 18 is intended for consideration as being stored in first memory unit 16. Alternatively, memory controller 12 may respond to a RESET signal by eliminating one or both of pointers 20, 22 until needed to indicate that data in second memory unit 18 is intended for consideration as being stored in first memory unit 16.


First memory unit 16 operates as a rolling buffer memory unit, “bumping” event data or information to a next memory cell when new event data is received and stored. Thus, event data is stored on a first-in-first-out basis in first memory unit 16. First memory unit 16 discards event information after the event information is “bumped” from memory site K.


Second memory unit 18 also operates as a rolling buffer memory unit, “bumping” event data to a next memory cell when new event data is received and stored. Thus, event data is stored on a first-in-first-out basis in second memory unit 18. Second memory unit 18 keeps event data stored for a longer period than first memory unit 16. Second memory unit 18 keeps event data stored longer than it takes to fill memory site K. Second memory unit 18 discards event information after the event information is “bumped” from memory site N. N is greater than K.


In a preferred embodiment of HVAC system information store 10, pointers 20, 22 simply identify which memory sites 1 through K are included in first memory unit 16. However, not all information stored in memory sites 1 through K is to be regarded as stored in first memory unit 16. One may recall that the intent of first memory unit 16 is to provide less complex, less confusing information for a user, such as a homeowner. Thus, it is preferred that selected information stored in memory sites 1 through K, but not necessarily all information stored in memory sites 1 through K, may be regarded as stored in first memory unit 16 and may be displayed to a user without limiting access.


Events stored in information store 10 may include alarm events. Alarm events may be continuous alarms, occasion-based alarms or alarm clears. Continuous alarms may relate to a continuously monitored event such as an event indicated by a sensor. By way of example and not by way of limitation, a continuous alarm may relate to whether a particular window to a conditioned space is open. An occasion-based alarm may relate to an occurrence of a particular event such as, by way of example and not by way of limitation, failure by a control unit to achieve a requisite thermal condition to permit lighting a furnace. Thus, an event alarm may be entered or stored in information store 10 on each occasion of failure by a control unit to achieve a requisite thermal condition to permit lighting a furnace.


Information store 10 may also store circumstances generally occurring with an alarm, including by way of example and not by way of limitation, specified parameters extant when an alarm occurs, specified parameters extant shortly before an alarm occurs, specified parameters extant shortly after an alarm occurs or specified parameters during a time interval spanning a time at which an alarm occurs.


An alarm clear preferably identifies at least one earlier occurring alarm to which the alarm clear pertains. By way of example and not by way of limitation, an alarm clear may effect clearing of an earlier-occurring continuous alarm (e.g., indicating that a offending window has been closed). An alarm clear may effect clearing of all active or pending event alarms relating to a particular occasion or event that are identified by the alarm clear. By way of further example and not by way of limitation, upon successful lighting of a furnace an alarm clear may be or stored in information store 10 to effect clearing of all active or pending alarms relating to each occasion of failure by a control unit to achieve a requisite thermal condition to permit lighting a furnace.


It is preferred that first memory unit 16 and second memory unit 18 be embodied in a non-volatile type memory device or unit. A volatile memory unit such as, by way of example and not by way of limitation, a Random Access Memory (RAM) memory unit may be employed when it is desired that information stored in a memory device be erased or otherwise removed or lost whenever the volatile memory device or unit is reset.


By way of example and not by way of limitation, events entered into first memory unit 16 may be provided upon the occasion of resetting a short-term RAM device for storing events (not shown in FIG. 1; understood by those skilled in the art of memory system design). Using such an arrangement, events may be first entered into a RAM memory unit substantially upon their respective occurrences, and whenever the RAM memory unit is reset or otherwise cleared, entries in the RAM memory unit are first transferred to first memory unit 16 before being removed from the RAM memory unit. By way of example and not by way of limitation, a RAM memory unit may be cleared in response to a clearing action by a user, a clearing action by a repair person or in response to another event.



FIG. 2 is a flow chart illustrating treatment of event information in the embodiment of the apparatus illustrated in FIG. 1. In FIG. 2, a treatment protocol 30 begins with the occurrence of a new event, as indicated by a beginning locus 32.


Treatment protocol 30 continues by posing a query whether the new event being treated is substantially identical to the last reported event, as indicated by a query block 34. If the new event is substantially identical to the last reported event, treatment protocol 30 continues from query block 34 via a YES response line 36 and an occurrence count for the last event reported is incremented, as indicated by a block 38. Maintaining an incremented count for tracking substantially identical occurrences is a treatment step that permits counting occurrences while conserving memory. Alternatively, each separate occurrence may be accounted for using a separate memory entry and no occurrence count may be required.


Treatment protocol 30 continues by updating the recorded day and time of occurrence of the latest-to-occur similar event, as indicated by a block 40. Updating the recorded day and time of occurrence of the latest-to-occur similar event may be an optional treatment step, as indicated by the broken line format of block 40. If an alternate design is employed in which a separate occurrence is accounted for using a separate memory entry, a date and time entry may accompany the event notation in storage and no updating of the day and time of occurrence of the latest-to-occur similar event may be required.


If the new event is not substantially identical to the last reported event, treatment protocol 30 continues from query block 34 via a NO response line 42 and a record of the occurrence of the new event is pushed to the top of a memory buffer, as indicated by a block 44. When the record of the occurrence of the new event is pushed to the top of a memory buffer, a count indicating occurrence of the new event may be set to 1, as also indicated by block 44. Treatment protocol 30 may continue by setting the first and last occurrence day and time entries for the new event, as indicated by a block 46. Setting the first and last occurrence day and time entries for the new event may be an optional treatment step, as indicated by the broken line format of block 46.


Treatment protocol 30 may continue from block 40 or from block 46 by posing a query whether the new event being treated is a reset event, as indicated by a query block 48. If the new event is a reset event, treatment protocol 30 continues from query block 48 via a YES response line 50 and the primary buffer end (see element 22; FIG. 1) is set to the primary buffer beginning (see element 20; FIG. 1) at the beginning of the secondary buffer (see second memory unit 18; FIG. 1), as indicated by a block 52. Treatment protocol 30 proceeds from block 52 to an exit locus 56. If the new event is not a reset event, treatment protocol 30 continues from query block 48 via a NO response line 54 to exit locus 56.



FIG. 3 is a schematic diagram of a second embodiment of the apparatus of the invention. In FIG. 3, an information storing system or information store 60 for an HVAC (Heating Ventilating Air Conditioning) system includes a common memory controller 62 and a memory section 64. Memory section 64 includes a first memory unit 66 and a second memory unit 68. First memory unit 66 includes a plurality of memory sites 1, 2, 3, . . . K−2, K−1, K. Second memory unit 68 includes a plurality of memory sites 1, 2, 3, . . . N−2, N−1, N.


Event data is provided to memory controller 62 from a host HVAC system (not shown in FIG. 3) via an event data input locus 61. Memory controller 62 also has a RESET locus 65 via which memory controller 62 may receive RESET signals. A RESET signal may cause memory controller 62 to reset or erase entries in first memory unit 66 or to otherwise empty first memory unit 66. Response by information storing system 60 to a RESET signal is described in greater detail in connection with FIG. 5.


First memory unit 66 operates as a rolling buffer memory unit, “bumping” event data or information to a next memory cell when new event data is received and stored. Thus, event data is stored on a first-in-first-out basis in first memory unit 66. First memory unit 66 discards event information after the event information is “bumped” from memory site K.


Second memory unit 68 also operates as a rolling buffer memory unit, “bumping” event data to a next memory cell when new event data is received and stored. Thus, event data is stored on a first-in-first-out basis in second memory unit 68. Second memory unit 68 keeps event data stored for a longer period than first memory unit 66. Second memory unit 68 discards event information after the event information is “bumped” from memory site N. N is greater than K.


In a preferred embodiment of HVAC system information store 60, not all information stored in first memory unit 66 in memory sites 1 through K is the same information stored in second memory unit 68 in memory sites 1 through K, or in memory sites K+1 through N. One may recall that the intent of first memory unit 66 is to provide less complex, less confusing information for a user, such as a homeowner. Thus, it is preferred that selected information stored in first memory unit 66 in memory sites 1 through K may contain fewer data entries than information stored in second memory unit 68 in memory sites 1 through K, and in memory sites K+1 through N.


Events stored in information store 60 may include alarm events. Alarm events may be continuous alarms, occasion-based alarms or alarm clears. Continuous alarms may relate to a continuously monitored event such as an event indicated by a sensor. By way of example and not by way of limitation, a continuous alarm may relate to whether a particular window to a conditioned space is open. An occasion-based alarm may relate to an occurrence of a particular event such as, by way of example and not by way of limitation, failure by a control unit to achieve a requisite thermal condition to permit lighting a furnace. Thus, an event alarm may be entered or stored in information store 60 on each occasion of failure by a control unit to achieve a requisite thermal condition to permit lighting a furnace.


Information store 60 may also store circumstances generally occurring with an alarm, including by way of example and not by way of limitation, specified parameters extant when an alarm occurs, specified parameters extant shortly before an alarm occurs, specified parameters extant shortly after an alarm occurs or specified parameters during a time interval spanning a time at which an alarm occurs.


An alarm clear preferably identifies at least one earlier occurring alarm to which the alarm clear pertains. By way of example and not by way of limitation, an alarm clear may effect clearing of an earlier-occurring continuous alarm (e.g., indicating that a offending window has been closed). An alarm clear may effect clearing of all active or pending event alarms relating to a particular occasion or event that are identified by the alarm clear. By way of further example and not by way of limitation, upon successful lighting of a furnace an alarm clear may be or stored in information store 60 to effect clearing of all active or pending alarms relating to each occasion of failure by a control unit to achieve a requisite thermal condition to permit lighting a furnace.


It is preferred that first memory unit 66 and second memory unit 68 be embodied in a non-volatile type memory device or unit. A volatile memory unit such as, by way of example and not by way of limitation, a Random Access Memory (RAM) memory unit may be employed when it is desired that information stored in a memory device be erased or otherwise removed or lost whenever the volatile memory device or unit is reset.


By way of example and not by way of limitation, events entered into first memory unit 66 may be provided upon the occasion of resetting a short-term RAM device for storing events (not shown in FIG. 3; understood by those skilled in the art of memory system design). Using such an arrangement, events may be first entered into a RAM memory unit substantially upon their respective occurrences, and whenever the RAM memory unit is reset or otherwise cleared, entries in the RAM memory unit are first transferred to first memory unit 66 before being removed from the RAM memory unit. By way of example and not by way of limitation, a RAM memory unit may be cleared in response to a clearing action by a user, a clearing action by a repair person or in response to another event.



FIG. 4 is a flow chart illustrating treatment of event information in the embodiment of the apparatus illustrated in FIG. 3. In FIG. 4, a treatment protocol 70 begins with the occurrence of a new event, as indicated by a beginning locus 72.


Treatment protocol 70 continues by posing a query whether the new event being treated is substantially identical to the last reported event, as indicated by a query block 74. If the new event is substantially identical to the last reported event, treatment protocol 70 continues from query block 74 via a YES response line 76 and an occurrence count for the last event reported is incremented in both memory units 66, 68 (FIG. 3), as indicated by a block 78. Maintaining an incremented count for tracking substantially identical occurrences is a treatment step that permits counting occurrences while conserving memory. Alternatively, each separate occurrence may be accounted for using a separate memory entry and no occurrence count may be required.


Treatment protocol 70 continues by updating the recorded day and time of occurrence of the latest-to-occur similar event, as indicated by a block 80. Updating the recorded day and time of occurrence of the latest-to-occur similar event may be an optional treatment step, as indicated by the broken line format of block 80. If an alternate design is employed in which a separate occurrence is accounted for using a separate memory entry, a date and time entry may accompany the event notation in storage and no updating of the day and time of occurrence of the latest-to-occur similar event may be required.


If the new event is not substantially identical to the last reported event, treatment protocol 70 continues from query block 74 via a NO response line 82 and a record of the occurrence of the new event is pushed to the top of both memory units 66, 68, as indicated by a block 84. When the record of the occurrence of the new event is pushed to the top of both memory units 66, 68, a count indicating occurrence of the new event may be set to 1, as also indicated by block 84. Treatment protocol 70 may continue by setting the first and last occurrence day and time entries for the new event, as indicated by a block 86. Setting the first and last occurrence day and time entries for the new event may be an optional treatment step, as indicated by the broken line format of block 86.


Treatment protocol 30 may continue from block 80 or from block 86 to an exit locus 88.



FIG. 5 is a flow diagram illustrating treatment of a reset event in the embodiment of the apparatus illustrated in FIG. 3. In FIG. 5, a treatment protocol 90 begins with the occurrence of a reset event, as indicated by a beginning locus 92. A reset event may occur, by way of example and not by way of limitation, when a RESET signal or other RESET indication is received at a RESET locus (e.g., RESET locus 65; FIG. 3). A reset event may cause a resetting or erasing of entries in a memory unit or may otherwise empty a memory unit.


Treatment protocol 90 continues by posing a query whether a resetting of a primary buffer (e.g., first memory unit 66; FIG. 3) is being requested, as indicated by a query block 94. If a resetting of a primary buffer is being requested, treatment protocol 90 continues from query block 94 via a YES response line 96 information relating to the reset event is stored in the secondary buffer (e.g., second memory unit 68; FIG. 3), as indicated by a block 98. Such related information to be stored may include, by way of example and not by way of limitation, the occurrence of a reset event, and the date and time of the occurrence. Storing information relating to the reset event may be an optional treatment step, as indicated by the broken line format of block 98.


Treatment protocol 90 may continue by resetting the primary buffer (e.g., first memory unit 66; FIG. 3), as indicated by a block 100. Treatment protocol 90 may continue from block 100 to an exit locus 104.


If a resetting of a primary buffer is not being requested, treatment protocol 90 continues from query block 94 via a NO response line 102 to exit locus 104.



FIG. 6 is a schematic diagram of a third embodiment of the apparatus of the invention. In FIG. 6, an information storing system 110 for an HVAC (Heating Ventilating Air Conditioning) system includes a first memory controller 112, a second memory controller 113 and a memory section 114. Memory section 114 includes a first memory unit 116 and a second memory unit 118. First memory unit 116 includes a plurality of memory sites 1, 2, 3, . . . K−2, K−1, K. Second memory unit 118 includes a plurality of memory sites 1, 2, 3, . . . N−2, N−1, N.


Event data is provided to memory controllers 112, 113 from a host HVAC system (not shown in FIG. 6) via an event data input locus 111. Memory controller 112 has a RESET locus 115 via which memory controller 112 may receive RESET signals. A RESET signal may cause memory controller 112 to reset or erase entries in first memory unit 116 or to otherwise empty first memory unit 116. Memory controller 113 has a RESET locus 117 via which memory controller 113 may receive indications of RESET signals received by memory controller 112. In an alternate arrangement, RESET locus 117 may be coupled with RESET locus 115. A RESET signal may cause memory controller 112 to reset or erase entries in first memory unit 116 or to otherwise empty first memory unit 116. Response by information storing system 110 to a RESET signal is described in greater detail in connection with FIGS. 8 and 10.


First memory unit 116 operates as a rolling buffer memory unit, “bumping” event data or information to a next memory cell when new event data is received and stored. Thus, event data is stored on a first-in-first-out basis in first memory unit 116. First memory unit 116 discards event information after the event information is “bumped” from memory site K.


Second memory unit 118 also operates as a rolling buffer memory unit, “bumping” event data to a next memory cell when new event data is received and stored. Thus, event data is stored on a first-in-first-out basis in second memory unit 118. Second memory unit 118 keeps event data stored for a longer period than first memory unit 116. Second memory unit 118 discards event information after the event information is “bumped” from memory site N. N is greater than K.


In a preferred embodiment of HVAC system information store 110, not all information stored in first memory unit 116 in memory sites 1 through K is the same information stored in second memory unit 118 in memory sites 1 through K, or in memory sites K+1 through N. One may recall that the intent of first memory unit 116 is to provide less complex, less confusing information for a user, such as a homeowner. Thus, it is preferred that selected information stored in first memory unit 116 in memory sites 1 through K may contain fewer data entries than information stored in second memory unit 118 in memory sites 1 through K, and in memory sites K+1 through N.


Events stored in information store 10 may include alarm events. Alarm events may be continuous alarms, occasion-based alarms or alarm clears. Continuous alarms may relate to a continuously monitored event such as an event indicated by a sensor. By way of example and not by way of limitation, a continuous alarm may relate to whether a particular window to a conditioned space is open. An occasion-based alarm may relate to an occurrence of a particular event such as, by way of example and not by way of limitation, failure by a control unit to achieve a requisite thermal condition to permit lighting a furnace. Thus, an event alarm may be entered or stored in information store 110 on each occasion of failure by a control unit to achieve a requisite thermal condition to permit lighting a furnace.


Information store 110 may also store circumstances generally occurring with an alarm, including by way of example and not by way of limitation, specified parameters extant when an alarm occurs, specified parameters extant shortly before an alarm occurs, specified parameters extant shortly after an alarm occurs or specified parameters during a time interval spanning a time at which an alarm occurs.


An alarm clear preferably identifies at least one earlier occurring alarm to which the alarm clear pertains. By way of example and not by way of limitation, an alarm clear may effect clearing of an earlier-occurring continuous alarm (e.g., indicating that a offending window has been closed). An alarm clear may effect clearing of all active or pending event alarms relating to a particular occasion or event that are identified by the alarm clear. By way of further example and not by way of limitation, upon successful lighting of a furnace an alarm clear may be or stored in information store 10 to effect clearing of all active or pending alarms relating to each occasion of failure by a control unit to achieve a requisite thermal condition to permit lighting a furnace.


It is preferred that first memory unit 116 and second memory unit 118 be embodied in a non-volatile type memory device or unit. A volatile memory unit such as, by way of example and not by way of limitation, a Random Access Memory (RAM) memory unit may be employed when it is desired that information stored in a memory device be erased or otherwise removed or lost whenever the volatile memory device or unit is reset.


By way of example and not by way of limitation, events entered into first memory unit 116 may be provided upon the occasion of resetting a short-term RAM device for storing events (not shown in FIG. 6; understood by those skilled in the art of memory system design). Using such an arrangement, events may be first entered into a RAM memory unit substantially upon their respective occurrences, and whenever the RAM memory unit is reset or otherwise cleared, entries in the RAM memory unit are first transferred to first memory unit 116 before being removed from the RAM memory unit. By way of example and not by way of limitation, a RAM memory unit may be cleared in response to a clearing action by a user, a clearing action by a repair person or in response to another event.



FIG. 7 is a flow chart illustrating treatment of event information in a first buffer unit of the embodiment of the apparatus illustrated in FIG. 6. In FIG. 7, a treatment protocol 120 begins with the occurrence of a new event, as indicated by a beginning locus 122.


Treatment protocol 120 continues by posing a query whether the new event being treated is substantially identical to the last reported event, as indicated by a query block 124. If the new event is substantially identical to the last reported event, treatment protocol 120 continues from query block 124 via a YES response line 126 and an occurrence count for the last event reported is incremented in first memory unit 116 (FIG. 6), as indicated by a block 128. Maintaining an incremented count for tracking substantially identical occurrences is a treatment step that permits counting occurrences while conserving memory. Alternatively, each separate occurrence may be accounted for using a separate memory entry and no occurrence count may be required.


Treatment protocol 120 continues by updating the recorded day and time of occurrence of the latest-to-occur similar event, as indicated by a block 130. Updating the recorded day and time of occurrence of the latest-to-occur similar event may be an optional treatment step, as indicated by the broken line format of block 130. If an alternate design is employed in which a separate occurrence is accounted for using a separate memory entry, a date and time entry may accompany the event notation in storage and no updating of the day and time of occurrence of the latest-to-occur similar event may be required.


If the new event is not substantially identical to the last reported event, treatment protocol 120 continues from query block 124 via a NO response line 132 and a record of the occurrence of the new event is pushed to the top of first memory units 116, as indicated by a block 134. When the record of the occurrence of the new event is pushed to the top of first memory unit 116, a count indicating occurrence of the new event may be set to 1, as also indicated by block 134. Treatment protocol 120 may continue by setting the first and last occurrence day and time entries for the new event, as indicated by a block 136. Setting the first and last occurrence day and time entries for the new event may be an optional treatment step, as indicated by the broken line format of block 136.


Treatment protocol 120 may continue from block 130 or from block 136 to an exit locus 138.



FIG. 8 is a flow diagram illustrating treatment of a reset event in a first buffer unit of the embodiment of the apparatus illustrated in FIG. 6. In FIG. 8, a treatment protocol 140 begins with the occurrence of a reset event, as indicated by a beginning locus 142. A reset event may occur, by way of example and not by way of limitation, when a RESET signal or other RESET indication is received at a RESET locus (e.g., RESET locus 115; FIG. 6). A reset event may cause a resetting or erasing of entries in a memory unit or may otherwise empty a memory unit.


Treatment protocol 140 continues by posing a query whether a resetting of a primary buffer (e.g., first memory unit 116; FIG. 6) is being requested, as indicated by a query block 144. If a resetting of a primary buffer is being requested, treatment protocol 140 continues from query block 144 via a YES response line 146 information relating to the reset event is stored in the secondary buffer (e.g., second memory unit 118; FIG. 3), as indicated by a block 148. Such related information to be stored may include, by way of example and not by way of limitation, the occurrence of a reset event, and the date and time of the occurrence. Storing information relating to the reset event may be an optional treatment step, as indicated by the broken line format of block 148.


Treatment protocol 140 may continue by resetting the primary buffer (e.g., first memory unit 116; FIG. 6), as indicated by a block 150. Treatment protocol 140 may continue from block 150 to an exit locus 154.


If a resetting of a primary buffer is not being requested, treatment protocol 140 continues from query block 144 via a NO response line 152 to exit locus 154.



FIG. 9 is a flow chart illustrating treatment of event information in a second buffer unit of the embodiment of the apparatus illustrated in FIG. 6. In FIG. 9, a treatment protocol 150 begins with the occurrence of a new event, as indicated by a beginning locus 152.


Treatment protocol 150 continues by posing a query whether the new event being treated is substantially identical to the last reported event, as indicated by a query block 154. If the new event is substantially identical to the last reported event, treatment protocol 150 continues from query block 154 via a YES response line 156 and an occurrence count for the last event reported is incremented in second memory unit 118 (FIG. 6), as indicated by a block 158. Maintaining an incremented count for tracking substantially identical occurrences is a treatment step that permits counting occurrences while conserving memory. Alternatively, each separate occurrence may be accounted for using a separate memory entry and no occurrence count may be required.


Treatment protocol 150 continues by updating the recorded day and time of occurrence of the latest-to-occur similar event, as indicated by a block 160. Updating the recorded day and time of occurrence of the latest-to-occur similar event may be an optional treatment step, as indicated by the broken line format of block 160. If an alternate design is employed in which a separate occurrence is accounted for using a separate memory entry, a date and time entry may accompany the event notation in storage and no updating of the day and time of occurrence of the latest-to-occur similar event may be required.


If the new event is not substantially identical to the last reported event, treatment protocol 150 continues from query block 154 via a NO response line 162 and a record of the occurrence of the new event is pushed to the top of second memory unit 118, as indicated by a block 164. When the record of the occurrence of the new event is pushed to the top of second memory unit 118, a count indicating occurrence of the new event may be set to 1, as also indicated by block 164. Treatment protocol 150 may continue by setting the first and last occurrence day and time entries for the new event, as indicated by a block 166. Setting the first and last occurrence day and time entries for the new event may be an optional treatment step, as indicated by the broken line format of block 166.


Treatment protocol 150 may continue from block 160 or from block 166 to an exit locus 168.



FIG. 10 is a flow diagram illustrating treatment of a reset event in a second buffer unit of the embodiment of the apparatus illustrated in FIG. 6. In FIG. 10, a treatment protocol 170 begins with the occurrence of a reset event requesting reset of a primary buffer (e.g., first memory unit 116; FIG. 6), as indicated by a beginning locus 172.


Treatment protocol 170 continues by posing a query whether the primary buffer was reset, as indicated by a query block 174. If the primary buffer was reset, treatment protocol 170 continues from query block 174 via a YES response line 176 and poses a query whether the last event was a primary buffer reset event, as indicated by a query block 178.


If the last event was a primary buffer reset event, treatment protocol 170 continues from query block 178 via a YES response line 180 and an occurrence count for the last reset event reported is incremented in second memory unit 118 (FIG. 6), as indicated by a block 182. Maintaining an incremented count for tracking substantially identical occurrences, such as reset events, is a treatment step that permits counting occurrences while conserving memory. Alternatively, each separate reset event occurrence may be accounted for using a separate memory entry and no reset event occurrence count may be required.


Treatment protocol 170 continues by updating the recorded day and time of the latest-to-occur reset event, as indicated by a block 184. Updating the recorded day and time of occurrence of the latest-to-occur reset event may be an optional treatment step, as indicated by the broken line format of block 184. If an alternate design is employed in which a separate reset event occurrence is accounted for using a separate memory entry, a date and time entry may accompany the reset event notation in storage and no updating of the day and time of the latest-to-occur reset event may be required.


If the last event was not a primary buffer reset event, treatment protocol 170 continues from query block 178 via a NO response line 186 a record of the “Reset Primary Buffer” event is pushed to the top of second memory unit 118 (FIG. 6), as indicated by a block 188. When the record of the occurrence of the “Reset Primary Buffer” event is pushed to the top of second memory unit 118, a count indicating occurrence of the “Reset Primary Buffer” event may be set to 1. Treatment protocol 170 may continue by setting the first and last occurrence day and time entries for the “Reset Primary Buffer” event, as indicated by a block 190. Setting the first and last occurrence day and time entries for the “Reset Primary Buffer” event may be an optional treatment step, as indicated by the broken line format of block 190.


If the primary buffer was not reset, treatment protocol 170 continues from query block 174 via a NO response line 192. Treatment protocol 170 may continue from query block 174 via a NO response line 192 or from block 184 to an exit locus 194.


It is to be understood that, while the detailed drawings and specific examples given describe preferred embodiments of the invention, they are for the purpose of illustration only, that the apparatus and method of the invention are not limited to the precise details and conditions disclosed and that various changes may be made therein without departing from the spirit of the invention which is defined by the following claims:

Claims
  • 1. An apparatus for storing event information relating to operation of an HVAC system; the apparatus comprising: (a) at least one memory controller coupled with said HVAC system for receiving said event information; and(b) at least one memory unit coupled with said at least one memory controller; a first memory unit of said at least one memory unit being configured for receiving first selected information of said event information for accessing by at least one of a first party and a second party; a second memory unit of said at least one memory unit being configured for receiving second selected information of said event information for accessing by said second party, said second selected information including reset event information of said first memory unit;wherein said event information includes alarm event information that indicates types of alarms associated with operating said HVAC system, operating parameters of said HVAC system associated with an occurrence of an alarm thereof, or alarm clears of said HVAC system.
  • 2. An apparatus for storing event information relating to operation of an HVAC system as recited in claim 1 wherein said second party is a servicing party, and wherein said accessing said second selected information is a controlled accessing.
  • 3. An apparatus for storing event information relating to operation of an HVAC system as recited in claim 1 wherein said second selected information is more detailed than said first selected information.
  • 4. An apparatus for storing event information relating to operation of an HVAC system as recited in claim 1 wherein said second memory unit is a rolling buffer unit storing a limited number of most-recently received entries of said event information.
  • 5. An apparatus for storing event information relating to operation of an HVAC system as recited in claim 4 wherein said first memory unit is a virtual rolling buffer unit including pointers; said pointers pointing to a subset of information contained in said limited number of most-recently received entries.
  • 6. An apparatus for storing event information relating to operation of an HVAC system as recited in claim 5 wherein said subset of information is contained in a smaller number of said most-recently received entries than said limited number.
  • 7. An apparatus for storing event information relating to operation of an HVAC system as recited in claim 1 wherein said at least one memory controller is a common memory controller coupled with said first memory unit and said second memory unit, wherein said first memory unit is a first rolling buffer unit storing a first limited number of most-recently received entries of selected information items of said event information, and wherein said second memory unit is a second rolling buffer unit storing a second limited number of most-recently received entries of said event information.
  • 8. An apparatus for storing event information relating to operation of an HVAC system as recited in claim 1 wherein said at least one memory controller is a first memory controller coupled with said first memory unit and a second memory controller coupled with said second memory unit, wherein said first memory unit is a first rolling buffer unit storing a first limited number of most-recently received entries of selected information items of said event information, and wherein said second memory unit is a second rolling buffer unit storing a second limited number of most-recently received entries of said event information.
  • 9. An apparatus for storing event information relating to operation of an HVAC system as recited in claim 5 wherein said types of alarms associated with operating said HVAC system includes a continuous alarm related to a continuously monitored event associated with operating said HVAC system and an occasion-based alarm related to an occurrence of a particular event associated with operating said HVAC system.
  • 10. An apparatus for storing event information relating to operation of an HVAC system as recited in claim 1 wherein said operating parameters of said HVAC system associated with an occurrence of an alarm thereof including at least one of specified parameters extant when an alarm occurs, before an alarm occurs, after an alarm occurs, and during a time interval spanning a time at which an alarm occurs.
  • 11. An apparatus for storing event information relating to operation of an HVAC system as recited in claim 1 wherein said alarm clears of said HVAC system identifying at least one earlier occurring alarm to which said alarm clears pertain.
  • 12. An apparatus storing operating information relating to a communicating control system; the apparatus comprising: (a) at least one controller unit coupled with said communicating control system; and(b) a memory unit coupled with said at least one controller unit; said memory unit including a first memory device and a second memory device; said first memory device being configured for storing first selected information of said operational information; said second memory device being configured for storing second selected information of said operational information; said first memory device being configured for permitting access to said first selected information without restriction; said second memory device permitting only authorized access to said second selected information, said second selected information including reset event information of said first memory unit;wherein said operating information includes alarm event information that indicates types of alarms associated with operating said communicating control system, operating parameters of said communicating control system associated with an occurrence of an alarm thereof, or alarm clears of said communicating control system.
  • 13. An apparatus storing operational information relating to a communicating control system as recited in claim 12 wherein said first memory device is a virtual rolling buffer unit including pointers; said pointers pointing to a subset of information contained in said second selected information; said second memory device being a rolling buffer unit; said second selected information being a limited number of most-recently received entries of said operational information.
  • 14. An apparatus storing operational information relating to a communicating control system as recited in claim 12 wherein said at least one controller unit is a common memory controller coupled with said first memory device and said second memory device, wherein said first memory device is a first rolling buffer unit, and wherein said second memory device is a second rolling buffer unit; said first selected information being a first limited number of a portion of most-recently received entries of said operational information; said second selected information being a second limited number of most-recently received entries of said operational information.
  • 15. An apparatus storing operational information relating to a communicating control system as recited in claim 12 wherein said at least one controller unit is a first memory controller coupled with said first memory device and a second memory controller coupled with said second memory device, wherein said first memory device is a first rolling buffer unit and said second memory device is a second rolling buffer unit; said first selected information being a first limited number of a portion of most-recently received entries of said operational information; said second selected information being a second limited number of most-recently received entries of said operational information.
  • 16. A method for storing event information relating to operation of an HVAC system; the method comprising: (a) providing at least one memory controller coupled with said HVAC system for receiving said event information;(b) providing at least one memory unit coupled with said at least one memory controller;(c) in no particular order: (1) configuring a first memory unit of said at least one memory unit for storing first selected information of said event; and(2) configuring a second memory unit of said at least one memory unit for storing second selected information of said event information; and(d) in no particular order: (1) operating said first memory unit for permitting access to said first selected information by at least one of a first party and a second party; and(2) operating said second memory unit for permitting access to said second selected information by said second party, said second selected information including reset event information of said first memory unit;wherein said event information includes alarm event information that indicates types of alarms associated with operating said HVAC system, operating parameters of said HVAC system associated with an occurrence of an alarm thereof, or alarm clears of said HVAC system.
  • 17. A method for storing event information relating to operation of an HVAC system as recited in claim 16 wherein said first memory unit is a virtual rolling buffer unit including pointers; said pointers pointing to a subset of information contained in said second selected information; said second memory unit being a rolling buffer unit; said second selected information being a limited number of most-recently received entries of said event information.
  • 18. A method for storing event information relating to operation of an HVAC system as recited in claim 16 wherein said at least one memory controller is a common memory controller coupled with said first memory unit and said second memory unit, wherein said first memory unit is a first rolling buffer unit, and wherein said second memory unit is a second rolling buffer unit; said first selected information being a first limited number of a portion of most-recently received entries of said event information; said second selected information being a second limited number of most-recently received entries of said event information.
  • 19. A method for storing event information relating to operation of an HVAC system as recited in claim 16 wherein said at least one memory controller is a first memory controller coupled with said first memory unit and a second memory controller coupled with said second memory unit, wherein said first memory unit is a first rolling buffer unit and said second memory unit is a second rolling buffer unit; said first selected information being a first limited number of a portion of most-recently received entries of said event information; said second selected information being a second limited number of most-recently received entries of said event information.
  • 20. A method for storing event information relating to operation of an HVAC system as recited in claim 16 wherein said second party is a servicing party, and wherein said accessing said second selected information is a controlled accessing.
US Referenced Citations (500)
Number Name Date Kind
4048491 Wessman Sep 1977 A
4187543 Healey et al. Feb 1980 A
4231351 Bowden et al. Nov 1980 A
4262736 Gilkeson et al. Apr 1981 A
4381549 Stamp et al. Apr 1983 A
4464543 Kline et al. Aug 1984 A
4482785 Finnegan et al. Nov 1984 A
4497031 Froehling et al. Jan 1985 A
4606042 Kahn et al. Aug 1986 A
4616325 Heckenbach et al. Oct 1986 A
4829447 Parker et al. May 1989 A
4843084 Parker et al. Jun 1989 A
4884214 Parker et al. Nov 1989 A
4967567 Proctor et al. Nov 1990 A
5039980 Aggers et al. Aug 1991 A
5061916 French et al. Oct 1991 A
5065813 Berkeley et al. Nov 1991 A
5086385 Launey et al. Feb 1992 A
5128855 Hilber et al. Jul 1992 A
5165465 Kenet Nov 1992 A
5170935 Federspiel et al. Dec 1992 A
5259553 Shyu Nov 1993 A
5274571 Hesse et al. Dec 1993 A
5278957 Chan Jan 1994 A
5341988 Rein et al. Aug 1994 A
5361982 Liebi et al. Nov 1994 A
5374200 Giroux Dec 1994 A
5384697 Pascucci Jan 1995 A
5434965 Matheny et al. Jul 1995 A
5444851 Woest Aug 1995 A
5449112 Heitman et al. Sep 1995 A
5450570 Richek et al. Sep 1995 A
5463735 Pascucci et al. Oct 1995 A
5475364 Kenet Dec 1995 A
5481481 Frey et al. Jan 1996 A
5511188 Pascucci et al. Apr 1996 A
5522044 Pascucci et al. May 1996 A
5544036 Brown et al. Aug 1996 A
5550980 Pascucci et al. Aug 1996 A
5555509 Dolan et al. Sep 1996 A
5581478 Cruse et al. Dec 1996 A
5598566 Pascucci et al. Jan 1997 A
5613157 Davidson et al. Mar 1997 A
5621662 Humphries et al. Apr 1997 A
5631825 van Weele et al. May 1997 A
5675756 Benton et al. Oct 1997 A
5684463 Diercks et al. Nov 1997 A
5706190 Russ et al. Jan 1998 A
5729442 Frantz Mar 1998 A
5751948 Dolan et al. May 1998 A
5784647 Sugimoto Jul 1998 A
5793646 Hibberd et al. Aug 1998 A
5801942 Nixon et al. Sep 1998 A
5803357 Lakin Sep 1998 A
5810245 Heitman et al. Sep 1998 A
5818347 Dolan et al. Oct 1998 A
5822512 Goodrum et al. Oct 1998 A
5862052 Nixon et al. Jan 1999 A
5884072 Rasmussen Mar 1999 A
5887651 Meyer Mar 1999 A
5924486 Ehlers et al. Jul 1999 A
5927398 Maciulewicz Jul 1999 A
5962989 Baker Oct 1999 A
5974554 Oh Oct 1999 A
5976010 Reese et al. Nov 1999 A
5983353 McHann, Jr. Nov 1999 A
6052525 Carlson et al. Apr 2000 A
6061600 Ying May 2000 A
6115713 Pascucci et al. Sep 2000 A
6141595 Gloudeman et al. Oct 2000 A
6169964 Alsa et al. Jan 2001 B1
6170044 McLaughlin et al. Jan 2001 B1
6240326 Gloudeman et al. May 2001 B1
6241156 Kline et al. Jun 2001 B1
6271845 Richardson Aug 2001 B1
6307331 Bonasia et al. Oct 2001 B1
6349306 Malik et al. Feb 2002 B1
6359220 Schiedegger et al. Mar 2002 B2
6363422 Hunter et al. Mar 2002 B1
6370037 Schoenfish Apr 2002 B1
6374373 Helm et al. Apr 2002 B1
6377283 Thomas Apr 2002 B1
6411857 Flood Jun 2002 B1
6427454 West Aug 2002 B1
6430953 Roh Aug 2002 B2
6437805 Sojoodi et al. Aug 2002 B1
6441723 Mansfield et al. Aug 2002 B1
6453374 Kovalan et al. Sep 2002 B1
6493661 White et al. Dec 2002 B1
6501995 Kinney et al. Dec 2002 B1
6505087 Lucas et al. Jan 2003 B1
6508407 Lefkowitz et al. Jan 2003 B1
6552647 Thiessen et al. Apr 2003 B1
6564348 Barenys et al. May 2003 B1
6594272 Ketcham et al. Jul 2003 B1
6639939 Naden et al. Oct 2003 B1
6644557 Jacobs Nov 2003 B1
6717919 Ketcham et al. Apr 2004 B1
6747888 Klein Jun 2004 B2
6817757 Wallace Nov 2004 B1
6833787 Levi Dec 2004 B1
6868292 Ficco et al. Mar 2005 B2
6874691 Hildebrand et al. Apr 2005 B1
6914893 Petite Jul 2005 B2
6944785 Gadir et al. Sep 2005 B2
6955302 Erdman, Jr. Oct 2005 B2
6967565 Lingemann Nov 2005 B2
7002462 Welch Feb 2006 B2
7027808 Wesby Apr 2006 B2
7031880 Seem et al. Apr 2006 B1
7055759 Wacker et al. Jun 2006 B2
7085814 Gandhi et al. Aug 2006 B1
7089530 Dardinski et al. Aug 2006 B1
7092768 Labuda Aug 2006 B1
7096465 Dardinski et al. Aug 2006 B1
7127327 O'Donnell Oct 2006 B1
7142948 Metz Nov 2006 B2
7154866 Shurmantine et al. Dec 2006 B2
7172160 Piel et al. Feb 2007 B2
7222111 Budke, Jr. May 2007 B1
7225054 Amundson et al. May 2007 B2
7259666 Hermsmeyer et al. Aug 2007 B1
7281697 Reggiani Oct 2007 B2
7302642 Smith et al. Nov 2007 B2
7313465 O'Donnell Dec 2007 B1
7318089 Stachura et al. Jan 2008 B1
7337191 Haeberle et al. Feb 2008 B2
7343226 Ehlers et al. Mar 2008 B2
7346433 Budike, Jr. Mar 2008 B2
7349761 Cruse Mar 2008 B1
7359335 Knop et al. Apr 2008 B2
7379791 Tamarkin et al. May 2008 B2
7379997 Ehlers et al. May 2008 B2
7418428 Ehlers et al. Aug 2008 B2
7424345 Norbeck Sep 2008 B2
7434744 Garozzo et al. Oct 2008 B2
7439862 Quan Oct 2008 B2
7446660 Posamentier Nov 2008 B2
7448435 Garozzo Nov 2008 B2
7457853 Chari et al. Nov 2008 B1
7476988 Mulhouse et al. Jan 2009 B2
7516106 Ehlers et al. Apr 2009 B2
7526364 Rule et al. Apr 2009 B2
7567523 Black et al. Jul 2009 B2
7567844 Thomas et al. Jul 2009 B2
7571195 Billingsley et al. Aug 2009 B2
7571355 Shabalin Aug 2009 B2
7574871 Bloemer et al. Aug 2009 B2
7584897 Schultz et al. Sep 2009 B2
7587459 Wewalaarachchi Sep 2009 B2
7593124 Sheng et al. Sep 2009 B1
7593787 Feingold et al. Sep 2009 B2
7604046 Bergman et al. Oct 2009 B2
7624931 Chapman et al. Dec 2009 B2
7641126 Schultz et al. Jan 2010 B2
7650323 Hesse et al. Jan 2010 B2
D610475 Beers et al. Feb 2010 S
7693583 Wolff et al. Apr 2010 B2
7693591 Hoglund et al. Apr 2010 B2
7706923 Amundson et al. Apr 2010 B2
7730223 Bavor et al. Jun 2010 B1
7734572 Wiemeyer et al. Jun 2010 B2
7743124 Holdaway et al. Jun 2010 B2
7747757 Garglulo et al. Jun 2010 B2
7752289 Kikkawa et al. Jul 2010 B2
7761563 Shike et al. Jul 2010 B2
7774102 Butler et al. Aug 2010 B2
7797349 Kosaka Sep 2010 B2
7809472 Silva et al. Oct 2010 B1
7827963 Li et al. Nov 2010 B2
7847790 Bewley et al. Dec 2010 B2
7861941 Schultz et al. Jan 2011 B2
7870080 Budike, Jr. Jan 2011 B2
7886166 Shnekendorf et al. Feb 2011 B2
7898147 Grabinger et al. Mar 2011 B2
7904209 Podgorny et al. Mar 2011 B2
7934504 Lowe et al. May 2011 B2
7949615 Ehlers et al. May 2011 B2
7963454 Sullivan et al. Jun 2011 B2
D642081 Kashimoto Jul 2011 S
7979164 Garozzo et al. Jul 2011 B2
8005576 Rodgers Aug 2011 B2
8024054 Mairs et al. Sep 2011 B2
8032254 Amundson et al. Oct 2011 B2
8042049 Killian et al. Oct 2011 B2
D648641 Wallaert Nov 2011 S
D648642 Wallaert Nov 2011 S
8050801 Richards et al. Nov 2011 B2
8082068 Rodgers Dec 2011 B2
8083154 Schultz et al. Dec 2011 B2
8087593 Leen Jan 2012 B2
8091796 Amundson et al. Jan 2012 B2
8099178 Mairs et al. Jan 2012 B2
8103390 Rodgers Jan 2012 B2
8112181 Remsburg Feb 2012 B2
8116917 Rodgers Feb 2012 B2
8122110 Wilbur et al. Feb 2012 B1
8127060 Doll et al. Feb 2012 B2
8167216 Schultz et al. May 2012 B2
8183995 Wang et al. May 2012 B2
8219249 Harrod et al. Jul 2012 B2
8224491 Koster et al. Jul 2012 B2
8239066 Jennings et al. Aug 2012 B2
8239073 Fausak et al. Aug 2012 B2
8244383 Bergman et al. Aug 2012 B2
8255086 Grohman Aug 2012 B2
8255090 Frader-Thompson Aug 2012 B2
8352081 Grohman Jan 2013 B2
8437877 Grohman May 2013 B2
8452906 Grohman May 2013 B2
8463442 Curry et al. Jun 2013 B2
8463443 Grohman et al. Jun 2013 B2
8548630 Grohman Oct 2013 B2
8564400 Grohman Oct 2013 B2
20010025349 Sharood et al. Sep 2001 A1
20010055311 Trachewsky et al. Dec 2001 A1
20020002425 Dossey et al. Jan 2002 A1
20020013897 McTernan et al. Jan 2002 A1
20020016639 Smith et al. Feb 2002 A1
20020033252 Sasao et al. Mar 2002 A1
20020048194 Klein Apr 2002 A1
20020053047 Gold May 2002 A1
20020065948 Morris et al. May 2002 A1
20020104323 Rash et al. Aug 2002 A1
20020116550 Hansen Aug 2002 A1
20020124211 Gray et al. Sep 2002 A1
20020143523 Balaji et al. Oct 2002 A1
20020152298 Kikta et al. Oct 2002 A1
20020157054 Shin et al. Oct 2002 A1
20020178288 McLeod Nov 2002 A1
20020191026 Rodden et al. Dec 2002 A1
20020191603 Shin et al. Dec 2002 A1
20020198990 Bradfield et al. Dec 2002 A1
20030061340 Sun et al. Mar 2003 A1
20030088338 Phillips et al. May 2003 A1
20030097482 DeHart et al. May 2003 A1
20030109963 Oppedisano et al. Jun 2003 A1
20030116637 Ellingham Jun 2003 A1
20030154355 Fernandez Aug 2003 A1
20030179721 Shurmantine et al. Sep 2003 A1
20030191857 Terrell et al. Oct 2003 A1
20030206100 Richman et al. Nov 2003 A1
20040001478 Wong Jan 2004 A1
20040003051 Kryzanowski et al. Jan 2004 A1
20040003415 Ng Jan 2004 A1
20040024483 Holcombe Feb 2004 A1
20040025089 Haswarey et al. Feb 2004 A1
20040059815 Buckingham et al. Mar 2004 A1
20040066788 Lin et al. Apr 2004 A1
20040088069 Singh May 2004 A1
20040111254 Gogel et al. Jun 2004 A1
20040133314 Ehlers et al. Jul 2004 A1
20040133704 Krzyzanowski Jul 2004 A1
20040138981 Ehlers et al. Jul 2004 A1
20040148482 Grundy et al. Jul 2004 A1
20040222307 DeLuca Nov 2004 A1
20040245352 Smith et al. Dec 2004 A1
20040260427 Wimsatt Dec 2004 A1
20040260812 Rhodes et al. Dec 2004 A1
20040260927 Grobman Dec 2004 A1
20040267385 Lingemann Dec 2004 A1
20040267395 Discenzo et al. Dec 2004 A1
20050040247 Pouchak Feb 2005 A1
20050040250 Wruck Feb 2005 A1
20050041033 Hilts et al. Feb 2005 A1
20050046584 Breed Mar 2005 A1
20050051168 DeVries et al. Mar 2005 A1
20050073789 Tanis Apr 2005 A1
20050090915 Gelwitz Apr 2005 A1
20050097478 Killian et al. May 2005 A1
20050103874 Erdman May 2005 A1
20050119765 Bergman Jun 2005 A1
20050119771 Amundson et al. Jun 2005 A1
20050119793 Amundson et al. Jun 2005 A1
20050119794 Amundson et al. Jun 2005 A1
20050154494 Ahmed Jul 2005 A1
20050159848 Shah et al. Jul 2005 A1
20050159924 Shah et al. Jul 2005 A1
20050182498 Landou et al. Aug 2005 A1
20050192727 Shostak et al. Sep 2005 A1
20050198040 Cohen et al. Sep 2005 A1
20050240312 Terry et al. Oct 2005 A1
20050252673 Kregle et al. Nov 2005 A1
20050256591 Rule et al. Nov 2005 A1
20050256935 Overstreet et al. Nov 2005 A1
20050258259 Stanimirovic Nov 2005 A1
20060009861 Bonasia Jan 2006 A1
20060009863 Lingemann Jan 2006 A1
20060027671 Shah Feb 2006 A1
20060036350 Bohrer et al. Feb 2006 A1
20060036952 Yang Feb 2006 A1
20060045107 Kucenas et al. Mar 2006 A1
20060063523 McFarland et al. Mar 2006 A1
20060105697 Aronstam et al. May 2006 A1
20060159007 Frutiger et al. Jul 2006 A1
20060185818 Garozzo Aug 2006 A1
20060192022 Barton et al. Aug 2006 A1
20060206220 Amundson Sep 2006 A1
20060212194 Breed Sep 2006 A1
20060250578 Pohl et al. Nov 2006 A1
20060250979 Gauweller et al. Nov 2006 A1
20060267756 Kates Nov 2006 A1
20070012052 Butler et al. Jan 2007 A1
20070019683 Kryzyanowski Jan 2007 A1
20070035255 Shuster et al. Feb 2007 A1
20070043477 Ehlers et al. Feb 2007 A1
20070053513 Hoffberg Mar 2007 A1
20070055757 Mairs et al. Mar 2007 A1
20070067062 Mairs et al. Mar 2007 A1
20070097993 Bojahra et al. May 2007 A1
20070109114 Farley et al. May 2007 A1
20070114291 Pouchak May 2007 A1
20070131784 Garozzo et al. Jun 2007 A1
20070157016 Dayan et al. Jul 2007 A1
20070194138 Shah Aug 2007 A9
20070205916 Blom et al. Sep 2007 A1
20070219645 Thomas et al. Sep 2007 A1
20070220301 Brundridge et al. Sep 2007 A1
20070220907 Ehlers Sep 2007 A1
20070221741 Wagner et al. Sep 2007 A1
20070233323 Wiemeyer et al. Oct 2007 A1
20070236156 Lys et al. Oct 2007 A1
20070241203 Wagner et al. Oct 2007 A1
20070260782 Shaikli Nov 2007 A1
20070268667 Moorer et al. Nov 2007 A1
20080003845 Hong et al. Jan 2008 A1
20080013259 Barton et al. Jan 2008 A1
20080029610 Nichols Feb 2008 A1
20080048046 Wagner et al. Feb 2008 A1
20080056722 Hendrix et al. Mar 2008 A1
20080057872 McFarland et al. Mar 2008 A1
20080057931 Nass et al. Mar 2008 A1
20080058996 Sachdev et al. Mar 2008 A1
20080082767 Nulkar et al. Apr 2008 A1
20080083834 Krebs et al. Apr 2008 A1
20080120335 Dolgoff May 2008 A1
20080121729 Gray May 2008 A1
20080129475 Breed et al. Jun 2008 A1
20080144302 Rosenblatt Jun 2008 A1
20080148098 Chen Jun 2008 A1
20080161976 Stanimirovic Jul 2008 A1
20080161978 Shah Jul 2008 A1
20080167931 Gerstemeier et al. Jul 2008 A1
20080168255 Abou-Emara et al. Jul 2008 A1
20080184059 Chen Jul 2008 A1
20080192649 Pyeon et al. Aug 2008 A1
20080192745 Spears Aug 2008 A1
20080195581 Ashmore et al. Aug 2008 A1
20080198036 Songkakul et al. Aug 2008 A1
20080216461 Nakano et al. Sep 2008 A1
20080217419 Ehlers et al. Sep 2008 A1
20080235611 Fraley et al. Sep 2008 A1
20080272934 Wang et al. Nov 2008 A1
20080281472 Podgorny et al. Nov 2008 A1
20090052105 Soleimani et al. Feb 2009 A1
20090057424 Sullivan et al. Mar 2009 A1
20090057425 Sullivan et al. Mar 2009 A1
20090062964 Sullivan et al. Mar 2009 A1
20090065597 Garozzo et al. Mar 2009 A1
20090077423 Kim et al. Mar 2009 A1
20090094506 Lakkis Apr 2009 A1
20090105846 Hesse et al. Apr 2009 A1
20090113037 Pouchak Apr 2009 A1
20090119092 Balasubramanyan May 2009 A1
20090132091 Chambers et al. May 2009 A1
20090140056 Leen Jun 2009 A1
20090140057 Leen Jun 2009 A1
20090140058 Koster et al. Jun 2009 A1
20090140061 Schultz et al. Jun 2009 A1
20090140062 Amundson et al. Jun 2009 A1
20090140063 Koster et al. Jun 2009 A1
20090140064 Schultz et al. Jun 2009 A1
20090143879 Amundson et al. Jun 2009 A1
20090143880 Amundson et al. Jun 2009 A1
20090143916 Boll et al. Jun 2009 A1
20090143918 Amundson et al. Jun 2009 A1
20090157529 Ehlers et al. Jun 2009 A1
20090195349 Frader-Thompson Aug 2009 A1
20090198810 Bayer et al. Aug 2009 A1
20090245278 Kee Oct 2009 A1
20090257431 Ramanathan et al. Oct 2009 A1
20090259785 Perry et al. Oct 2009 A1
20090261767 Butler et al. Oct 2009 A1
20090266904 Cohen Oct 2009 A1
20090267540 Chemel et al. Oct 2009 A1
20090271336 Franks Oct 2009 A1
20090287736 Shike et al. Nov 2009 A1
20100011437 Courtney Jan 2010 A1
20100023865 Fulker et al. Jan 2010 A1
20100050075 Thorson et al. Feb 2010 A1
20100050108 Mirza Feb 2010 A1
20100063644 Kansal et al. Mar 2010 A1
20100070086 Harrod et al. Mar 2010 A1
20100070089 Harrod et al. Mar 2010 A1
20100070093 Harrod et al. Mar 2010 A1
20100070907 Harrod et al. Mar 2010 A1
20100073159 Schmickley et al. Mar 2010 A1
20100076605 Harrod et al. Mar 2010 A1
20100100253 Fausak et al. Apr 2010 A1
20100101854 Wallaert et al. Apr 2010 A1
20100102136 Hadzidedic et al. Apr 2010 A1
20100102948 Grohman et al. Apr 2010 A1
20100102973 Grohman et al. Apr 2010 A1
20100106305 Pavlak et al. Apr 2010 A1
20100106307 Grohman et al. Apr 2010 A1
20100106308 Filbeck et al. Apr 2010 A1
20100106309 Grohman et al. Apr 2010 A1
20100106310 Grohman Apr 2010 A1
20100106311 Wallaert Apr 2010 A1
20100106312 Grohman et al. Apr 2010 A1
20100106313 Grohman et al. Apr 2010 A1
20100106314 Grohman et al. Apr 2010 A1
20100106315 Grohman Apr 2010 A1
20100106316 Curry et al. Apr 2010 A1
20100106317 Grohman et al. Apr 2010 A1
20100106318 Grohman et al. Apr 2010 A1
20100106319 Grohman et al. Apr 2010 A1
20100106320 Grohman et al. Apr 2010 A1
20100106321 Hadzidedic Apr 2010 A1
20100106322 Grohman Apr 2010 A1
20100106323 Wallaert Apr 2010 A1
20100106324 Grohman Apr 2010 A1
20100106325 Grohman Apr 2010 A1
20100106326 Grohman Apr 2010 A1
20100106327 Grohman et al. Apr 2010 A1
20100106329 Grohman Apr 2010 A1
20100106330 Grohman Apr 2010 A1
20100106333 Grohman et al. Apr 2010 A1
20100106334 Grohman et al. Apr 2010 A1
20100106787 Grohman Apr 2010 A1
20100106809 Grohman Apr 2010 A1
20100106810 Grohman Apr 2010 A1
20100106814 Hadzidedic et al. Apr 2010 A1
20100106815 Grohman et al. Apr 2010 A1
20100106925 Grohman et al. Apr 2010 A1
20100106957 Grohman et al. Apr 2010 A1
20100107007 Grohman et al. Apr 2010 A1
20100107070 Devineni et al. Apr 2010 A1
20100107071 Pavlak et al. Apr 2010 A1
20100107072 Mirza et al. Apr 2010 A1
20100107073 Wallaert Apr 2010 A1
20100107074 Pavlak et al. Apr 2010 A1
20100107076 Grohman Apr 2010 A1
20100107083 Grohman Apr 2010 A1
20100107103 Wallaert Apr 2010 A1
20100107109 Filbeck et al. Apr 2010 A1
20100107110 Mirza Apr 2010 A1
20100107111 Mirza Apr 2010 A1
20100107112 Jennings et al. Apr 2010 A1
20100107232 Grohman et al. Apr 2010 A1
20100115364 Grohman May 2010 A1
20100131884 Shah May 2010 A1
20100142526 Wong Jun 2010 A1
20100145528 Bergman et al. Jun 2010 A1
20100145629 Botich et al. Jun 2010 A1
20100168924 Tessier et al. Jul 2010 A1
20100169419 DeVilbiss et al. Jul 2010 A1
20100179696 Grohman et al. Jul 2010 A1
20100211546 Grohman et al. Aug 2010 A1
20100241245 Wiemeyer et al. Sep 2010 A1
20100259931 Chemel et al. Oct 2010 A1
20100264846 Chemel et al. Oct 2010 A1
20100270933 Chemel et al. Oct 2010 A1
20100272102 Kobayashi Oct 2010 A1
20100295474 Chemel et al. Nov 2010 A1
20100295475 Chemel et al. Nov 2010 A1
20100295482 Chemel et al. Nov 2010 A1
20100301768 Chemel et al. Dec 2010 A1
20100301769 Chemel et al. Dec 2010 A1
20100301770 Chemel et al. Dec 2010 A1
20100301771 Chemel et al. Dec 2010 A1
20100301772 Chemel et al. Dec 2010 A1
20100301773 Chemel et al. Dec 2010 A1
20100301774 Chemel et al. Dec 2010 A1
20100305761 Remsburg Dec 2010 A1
20100314458 Votaw et al. Dec 2010 A1
20100319362 Hisaoka Dec 2010 A1
20110001436 Chemel et al. Jan 2011 A1
20110001438 Chemel et al. Jan 2011 A1
20110004823 Wallaert Jan 2011 A1
20110004824 Thorson et al. Jan 2011 A1
20110007016 Mirza et al. Jan 2011 A1
20110007017 Wallaert Jan 2011 A1
20110010620 Mirza et al. Jan 2011 A1
20110010621 Wallaert Jan 2011 A1
20110010652 Wallaert Jan 2011 A1
20110010653 Wallaert Jan 2011 A1
20110010660 Thorson et al. Jan 2011 A1
20110032932 Pyeon et al. Feb 2011 A2
20110040785 Steenberg et al. Feb 2011 A1
20110061014 Frader-Thompson et al. Mar 2011 A1
20110063126 Kennedy et al. Mar 2011 A1
20110066297 Saberi et al. Mar 2011 A1
20110160915 Bergman et al. Jun 2011 A1
20110251726 McNulty et al. Oct 2011 A1
20120012662 Leen et al. Jan 2012 A1
20120046792 Secor Feb 2012 A1
20120065805 Montalvo Mar 2012 A1
20120116593 Amundson et al. May 2012 A1
20120181010 Schultz et al. Jul 2012 A1
Foreign Referenced Citations (7)
Number Date Country
0980165 Feb 2000 EP
1956311 Aug 2008 EP
2241836 Oct 2010 EP
2241837 Oct 2010 EP
2117573 Oct 1983 GB
02056540 Jul 2002 WO
2008100641 Aug 2008 WO
Non-Patent Literature Citations (19)
Entry
Checket-Hanks, B., “Zoning Controls for Convenience's Sakes, High-End Residential Controls Move Into New Areas,” Air Conditioning, Heating & Refrigeration News, ABI /Inform Global, Jun. 28, 2004, 3 pages.
Leeb, G., “A User Interface for Home-Net,” IEEE Transactions on Consumer Electronics, vol. 40, Issue 4, Nov. 1994, pp. 897-902.
“IPMI—Intelligent Platform Management Interface Specification v1.5,” Document Revision 1.1, Intel Hewlett-Packard NEC Dell, Feb. 20, 2002, 460 pages.
Nash, H., “Fire Alarm Systems for Health Care Facilities,” IEEE Transactions on Industry Applications, vol. 1A-19, No. 5, Sep./ Oct. 1983, pp. 848-852.
Bruggeman, E., et al., “A Multifunction Home Control System,” IEEE Transactions on Consumer Electronics, CE-29, Issue 1, 10 pages.
Fischer, H., et al., “Remote Building Management and DDc-Technology to Operate Distributed HVAC-Installations,” The first International Telecommunications Energy Special Conference, Telescon '94, Apr. 11-15, 1994, pp. 127-132.
Gallas, B., et al., “ Embedded Pentium® Processor System Design for Windows CE,” Wescon 1998, pp. 114-123.
“iView-100 Series (iView/iView-100-40) Handheld Controller User's Manual,” ICP DAS, Mar. 2006, Version 2.0.
“Spectra™ Commercial Zoning System, Engineering Data,” Lennox, Bulletin No. 210366E, Oct. 2002, 33 pages.
Sharma, A., “Design of Wireless Sensors Network for Building Management Systems,” University of California-Berkley, 57 pages.
“Linux Programmer's Manual, UNIX Man Pages: Login (1), ”http://unixhelp.ed.ac.uk/CGI/man-cgi?login, Util-linux 1.6, Nov. 4, 1996, 4 pages.
“Field Display for Tridium Jace Controllers Product Data,” HVAC Concepts, Inc. 2005, 22 pages.
“HVAC Concepts,” Jace Network-Installation, 2004, 2 pages.
Bruggeman, E., et al., “A Multifunction Home Control System,” IEEE Transactions on Consumer Electronics, CE-29, Issue 1, Feb. 1983, 10 pages.
Sharma, A., “Design of Wireless Sensors Network for Building Management Systems,” University of California-Berkley, 2003, 57 pages.
“Definition of encase by The Free Dictionary,” http://www.thefreedictionary.com/encase, 2013, 2 pages.
“Define Track at Dictionary.com ,” http://dictionary.reference.com/browse/track, Mar. 12, 2013, 3 pages.
“Definition of Track by Macmillan Dictionary,” http://www.macmillandictionary.com/dictionary/british/track, Mar. 12, 2013, 4 pages.
“Definition of track by the Free Online Dictionary, Thesaurus, and Encyclopedia,” http://www.thefreedictionary.com/track, Mar. 12, 2013, 6 pages.
Related Publications (1)
Number Date Country
20100011437 A1 Jan 2010 US