System recovery in a heating, ventilation and air conditioning network

• US 8,255,086 B2
• Filed: 10/21/2009
• Issued: 08/28/2012
• Est. Priority Date: 10/27/2008
• Status: Active Grant

• Current Assignee: Lennox Industries Incorporated (Lennox International Incorporated)
• Original Assignee: Lennox Industries Incorporated (Lennox International Incorporated)
• Inventors: Grohman, Wojciech
• Primary Examiner(s): VON BUHR, MARIA N
• Application Number:
  US12/603,490
• Publication Number:
  US 20100106315A1
• Time in Patent Office: 1,042 Days
• Field of Search: 700/82, 700275-277, 700/306, 709/208, 709/209, 709223-229, 709248-250, 709/253, 710/107, 710/109, 710/110, 714 10- 13, 714/55, 714/56
• US Class Current: 700/276
• CPC Class Codes: F24F 11/30 for purposes related to the operation of the system, e.g. for safety or monitoring
• CPC Class Codes: F24F 11/46 Improving electric energy efficiency or saving
• CPC Class Codes: F24F 11/62 characterised by the type of control or by internal processing, e.g. using fuzzy logic, adaptive control or estimation of values
• CPC Class Codes: H04L 12/2803 Home automation networks
• CPC Class Codes: H04L 43/10 Active monitoring, e.g. heartbeat, ping or trace-route

Abstract

The disclosure provides various embodiments of systems and methods of generating a heartbeat in an HVAC system and networks. In an embodiment, a method includes a heartbeat message being sent by a first subnet controller upon the first subnet controller taking active control of a subnet of the HVAC network. The active heartbeat message timer is reset. Another heartbeat message is sent if a specified amount of time has elapsed since a previous heartbeat message was sent by said heartbeat generator.

Claims

1. A method of using a heartbeat in an HVAC network that includes a first subnet controller and a second subnet controller on a subnet, comprising:

said first subnet controller providing a heartbeat message via said network;

said second subnet controller in an inactive state determining if said first subnet controller has provided said heartbeat message within a first specified time period;

said second subnet controller remaining in said inactive state in the event that said first subnet controller provides said heartbeat message within said first specified time period;

said second subnet controller switching to an active state in the event that said first subnet controller does not provide said heartbeat message within said first specified time period; and

a device on said subnet determining the presence or absence of said heartbeat within a second specified time period;

wherein;

in the event that said device detects said heartbeat message within said second specified time period, said device continues to operate in a prior mode; and

in the event that said device fails to detect said heartbeat message within said second specified time period, said device

a) issues a heartbeat-message-missing alarm;

b) ceases to operate in a communication mode; and

c) continues to generate device status messages via said subnet.

2. The method of claim 1, wherein said first specified time period is about three minutes.

3. The method of claim 1, wherein said second specified time period is shorter than said first specified time period.

4. The method of claim 1, wherein said first or said second subnet controller is collocated with a furnace controller, a heat pump controller, a compressor controller, a fan controller or a damper controller.

5. An HVAC network, comprising:

a first subnet controller on a subnet of said HVAC network, said first subnet controller being configured to periodically send a heartbeat message over said network; and

a second subnet controller on said subnet, said second subnet controller being configured to determine if said first subnet controller has provided said heartbeat message within a first specified time period;

a device on said subnet configured to determine the presence or absence of said heartbeat within a second specified time period;

wherein;

in the event that said device detects said heartbeat message within said second specified time period, said device continues to operate in a prior mode; and

in the event that said device fails to detect said heartbeat message within said second specified time period, said device

a) issues a heartbeat-message-missing alarm;

b) ceases to operate in a communication mode; and

c) continues to generate device status messages via said subnet.

6. The network of claim 5, wherein said first specified time period is about three minutes.

7. The network of claim 5, further comprising:

a heartbeat message timer; and

a heartbeat generator configured to;

a) generate said heartbeat message by said first subnet controller upon said first subnet controller taking active control of a subnet of said HVAC network;

b) send another heartbeat message if said first subnet controller detects a subnet controller message on said subnet from said second subnet controller;

c) send another heartbeat message if said first subnet controller detects a device message on said subnet; and

d) send another heartbeat message if said heartbeat message timer determines a specified time period has elapsed since a previous heartbeat message has been generated by said heartbeat generator.

8. The network of claim 7, wherein said heartbeat message timer is reset by any step of sending another heartbeat message.

9. The network of claim 7, wherein said specified time period is about one minute.

10. The network of claim 5, further comprising a field-programmable device to be used in said HVAC network, comprising:

at least two field pins configured to be shorted together;

a field system feature selector;

a processor coupled to said field system feature selector and to said at least two pins, wherein said processor can read a plurality of shorts between two of said pins and an output of said field system feature selector, to generate a value; and

an LED coupled to said processor configured to display said value.

11. The network of claim 10, wherein said processor can further configured to:

read a duration of a first selected time period of a short between said two field pins to enable a presentation of an instance of said value for a selected dependent feature; and

present an increment of said instance when said first and second field pins are shorted together for a second selected time period.

12. The network of claim 11, wherein a feature selected by said feature selection is selected from the group consisting of:

a) a unit capacity, and

b) a model number.

13. The network of claim 10, wherein said value is presented to a user with said LED.

14. The system of claim 5, wherein said second subnet controller is configured to:

in the event that said first subnet controller provides said heartbeat message within said specified time period, remain in an inactive state,

in the event that said first subnet controller fails to provide said heartbeat message within said specified time period, initiate an arbitration process with any other inactive subnet controllers on said subnet; and

in response to said arbitration process, switch to an active state and initiate an active subnet startup state for said subnet.