Device commissioning in a heating, ventilation and air conditioning network

Abstract

An HVAC system includes first and second devices coupled via a subnet. A feature manifest stored by the second device is readable by the first device after the first device enters a commissioning process. The first device is configured to determine a value of an internal parameter based on the feature manifest.

Description

TECHNICAL FIELD

This application is directed, in general, to distributed-architecture heating, ventilation and air conditioning (HVAC) system, more specifically, to a memory scheme and data recovery in an HVAC network.

BACKGROUND

Climate control systems, also referred to as HVAC systems (the two terms will be used herein interchangeably), are employed to regulate the temperature, humidity and air quality of premises, such as a residence, office, store, warehouse, vehicle, trailer, or commercial or entertainment venue. The most basic climate control systems either move air (typically by means of an air handler or, or more colloquially, a fan or blower), heat air (typically by means of a furnace) or cool air (typically by means of a compressor-driven refrigerant loop). A thermostat is typically included in the climate control systems to provide some level of automatic temperature control. In its simplest form, a thermostat turns the climate control system on or off as a function of a detected temperature. In a more complex form, a thermostat may take other factors, such as humidity or time, into consideration. Still, however, the operation of a thermostat remains turning the climate control system on or off in an attempt to maintain the temperature of the premises as close as possible to a desired setpoint temperature. Climate control systems as described above have been in wide use since the middle of the twentieth century.

SUMMARY

One embodiment provides an HVAC system that includes first and second devices coupled via a subnet. A feature manifest stored by the second device is readable by the first device after the first device enters a commissioning process. The first device is configured to determine a value of an internal parameter based on the feature manifest.

Another embodiment provides a method of commissioning devices in an HVAC network. The method includes a first device of a subnet reading a feature manifest of a second device of the subnet. The first device determines a validity of a parameter of the first device based on the feature manifest.

Yet another embodiment provides a communicating device of an HVAC system. The communicating device is configured to read a feature manifest stored by a second device after the communicating device enters a commissioning process. The device is further configured to determine a value of an internal parameter based on the feature manifest.

BRIEF DESCRIPTION

Reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:

FIG. 1 is a high-level block diagram of an HVAC system within which a device abstraction system and method may be contained or carried out;

FIG. 2 is a high-level block diagram of one embodiment of an HVAC data processing and communication network 200;

FIG. 3A is a diagram of a series of steps in an event sequence that depicts a device commissioning in an HVAC network having an active subnet controller

FIG. 3B is a diagram of a series of steps that occur in relation to a commissioning of a subnet including an addressable unit;

FIG. 3C is a diagram of the above series of steps of FIG. 3B to be followed by a subnet controller to synchronize with a device of the HVAC system;

FIG. 4A is an illustration of method flow of a first approach directed towards a parameter configuration in a communicating HVAC network;

FIGS. 4Bi and 4Bii illustrate an exemplary flow diagram of a second approach of a method directed towards configuration of variable parameters of an HVAC device that are dependent upon other parameters, having a value and a range, within that same HVAC device

FIG. 5 illustrates an exemplary flow for a method for a third approach commissioning an HVAC device attached to a non-communicating device that enables the use of a manifest of parameter types to configure a non-communicating HVAC device;

FIG. 6A illustrates an exemplary signaling flow for a method for commissioning parameters when validity and value of internal parameters of a device depend on network configuration and/or other device features of the device or devices;

FIG. 6B illustrates an exemplary overview of signaling flows implemented in a commissioning between a subnet controller, a user interface/gateway and another device

FIGS. 6C1-1 and 6C1-2 illustrates an exemplary signal flow associated with a “Non-Communicating Check Scan” and “Parameter Scan” sub-states of commissioning state in an HVAC network;

FIGS. 6C2-1 and 6C2-2 illustrates an exemplary Signal flow associated with a “Non-Communicating Check Update” and “Parameter Update” sub-states of commissioning state in an HVAC network;

FIG. 7A1 illustrates an exemplary embodiment of a method flow of propagating variable parameters in an HVAC system as initiated by a subnet controller;

FIG. 7A2 illustrates an exemplary embodiment of illustrates an exemplary embodiment of a method flow of propagating variable parameters in an HVAC system as initiated by a user interface;

FIG. 7B is an illustration of a high-level block diagram of commissioning steps that includes an active subnet controller that can be practices with the method of FIG. 7A2.

FIG. 8A illustrates an exemplary flow regarding controlling dependent parameters when a parameter of a first device is dependent upon a parameter of a second device of a subnet of an HVAC system;

FIGS. 8B-1, 8B-2 and 8B-3 illustrates an exemplary signal flow associated with a “Replacement Check Message Flow” sub-states of commissioning state in an HVAC network; and

FIG. 9 is a block diagram of a system device of the disclosure.

DETAILED DESCRIPTION

As stated above, conventional climate control systems have been in wide use since the middle of the twentieth century and have, to date, generally provided adequate temperature management. However, it has been realized that more sophisticated control and data acquisition and processing techniques may be developed and employed to improve the installation, operation and maintenance of climate control system.

Described herein are various embodiments of an improved climate control, or HVAC, system in which at least multiple components thereof communicate with one another via a data bus. The communication allows identity, capability, status and operational data to be shared among the components. In some embodiments, the communication also allows commands to be given. As a result, the climate control system may be more flexible in terms of the number of different premises in which it may be installed, may be easier for an installer to install and configure, may be easier for a user to operate, may provide superior temperature and/or relative humidity (RH) control, may be more energy efficient, may be easier to diagnose and perhaps able to repair itself, may require fewer, simpler repairs and may have a longer service life.

FIG. 1 is a high-level block diagram of an HVAC system, generally designated 100. The HVAC system may be referred to herein simply as “system 100” for brevity. In one embodiment, the system 100 is configured to provide ventilation and therefore includes one or more air handlers 110. In an alternative embodiment, the ventilation includes one or more dampers 115 to control air flow through air ducts (not shown.) Such control may be used in various embodiments in which the system 100 is a zoned system. In the context of a zoned system 100, the one or more dampers 115 may be referred to as zone controllers 115. In an alternative embodiment, the system 100 is configured to provide heating and therefore includes one or more furnaces 120, typically associated with the one or more air handlers 110. In an alternative embodiment, the system 100 is configured to provide cooling and therefore includes one or more refrigerant evaporator coils 130, typically associated with the one or more air handlers 110. Such embodiment of the system 100 also includes one or more compressors 140 and associated condenser coils 142, which are typically associated in one or more so-called “outdoor units” 144. The one or more compressors 140 and associated condenser coils 142 are typically connected to an associated evaporator coil 130 by a refrigerant line 146. In an alternative embodiment, the system 100 is configured to provide ventilation, heating and cooling, in which case the one or more air handlers 110, furnaces 120 and evaporator coils 130 are associated with one or more “indoor units” 148, e.g., basement or attic units.

For convenience in the following discussion, a demand unit 155 is representative of the various units exemplified by the handler 110, furnace 120, and compressor 140, and more generally includes an HVAC component that provides a service in response to control by the control unit 150. The service may be, e.g., heating, cooling, or air circulation. The demand unit 155 may provide more than one service, and if so, one service may be a primary service, and another service may be an ancillary service. For example, for a cooling unit that also circulates air, the primary service may be cooling, and the ancillary service may be air circulation (e.g. by a blower).

The demand unit 155 may have a maximum service capacity associated therewith. For example, the furnace 120 may have a maximum heat output (often expressed in terms of British Thermal Units, or BTU), or a blower may have a maximum airflow capacity (often expressed in terms of cubic feet per minute, or CFM). In some cases, the addressable unit 155 may be configured to provide a primary or ancillary service in staged portions. For example, blower may have two or more motor speeds, with a CFM value associated with each motor speed.

One or more control units 150 control one or more of the one or more air handlers 110, the one or more furnaces 120 and/or] the one or more compressors 140 to regulate the temperature of the premises, at least approximately. In various embodiments to be described, the one or more displays 170 provide additional functions such as operational, diagnostic and status message display and an attractive, visual interface that allows an installer, user or repairman to perform actions with respect to the system 100 more intuitively. Herein, the term “operator” will be used to refer collectively to any of the installer, the user and the repairman unless clarity is served by greater specificity.

One or more separate comfort sensors 160 may be associated with the one or more control units 150 and may also optionally be associated with one or more displays 170. The one or more comfort sensors 160 provide environmental data, e.g. temperature and/or humidity, to the one or more control units 150. An individual comfort sensor 160 may be physically located within a same enclosure or housing as the control unit 150. In such cases, the commonly housed comfort sensor 160 may be addressed independently. However, the one or more comfort sensors 160 may be located separately and physically remote from the one or more control units 150. Also, an individual control unit 150 may be physically located within a same enclosure or housing as a display 170. In such embodiments, the commonly housed control unit 150 and display 170 may each be addressed independently. However, one or more of the displays 170 may be located within the system 100 separately from and/or physically remote to the control units 150. The one or more displays 170 may include a screen such as a liquid crystal display (not shown).

Although not shown in FIG. 1, the HVAC system 100 may include one or more heat pumps in lieu of or in addition to the one or more furnaces 120, and one or more compressors 140. One or more humidifiers or dehumidifiers may be employed to increase or decrease humidity. One or more dampers may be used to modulate air flow through ducts (not shown). Air cleaners and lights may be used to reduce air pollution. Air quality sensors may be used to determine overall air quality.

Finally, a data bus 180, which in the illustrated embodiment is a serial bus, couples the one or more air handlers 110, the one or more furnaces 120, the one or more evaporator coils 130, the one or more condenser coils 142 and compressors 140, the one or more control units 150, the one or more remote comfort sensors 160 and the one or more displays 170 such that data may be communicated there between or there among. As will be understood, the data bus 180 may be advantageously employed to convey one or more alarm messages or one or more diagnostic messages.

FIG. 2 is a high-level block diagram of one embodiment of an HVAC data processing and communication network 200 that may be employed in the HVAC system 100 of FIG. 1. One or more air handler controllers (“AHCs”) 210 may be associated with the one or more air handlers 110 of FIG. 1. One or more integrated furnace controllers (“IFCs”) 220 may be associated with the one or more furnaces 120. One or more damper controller modules 215, also referred to as a zone controller module 215, may be associated with the one or more dampers 114 the interface the one or more dampers to the data bus 180. One or more AC controllers 225 may be associated with one or more evaporator coils 130 and one or more condenser coils 142 and compressors 140 of FIG. 1. The network 200 includes an active subnet controller (“aSC”) 230a and an inactive subnet controller (“iSC”) 230i. The aSC 230a is responsible for configuring and monitoring the system 100 and for implementation of heating, cooling, air quality, ventilation or any other functional algorithms therein. Two or more aSCs 230a may also be employed to divide the network 200 into subnetworks, or subnets, simplifying network configuration, communication and control. The iSC 230i is a subnet controller that does not actively control the network 200. In some embodiments, the iSC 230i listens to all messages passed over the data bus 180, and updates its internal memory to match that of the aSC 230a. In this manner, the iSC 230i may backup parameters stored by the aSC 230a, and may be used as an active subnet controller if the aSC 230a malfunctions. Typically there is only one aSC 230a in a subnet, but there may be multiple iSCs therein, or no iSC at all. Herein, where the distinction between an active or a passive SC is not germane the subnet controller is referred to generally as an SC 230.

A user interface (UI) 240 provides a means by which an operator may communicate with the remainder of the network 200. In an alternative embodiment, a user interface/gateway (UI/G) 250 provides a means by which a remote operator or remote equipment may communicate with the remainder of the network 200. Such a remote operator or equipment is referred to generally as a remote entity. A comfort sensor interface 260 may provide an interface between the data bus 180 and each of the one or more comfort sensors 160.

FIG. 9 illustrates a device 910 according to the disclosure. The following description pertains to the HVAC data processing and communication network 200 that is made up of a number of system devices 910 operating cooperatively to provide HVAC functions. Hereinafter the system device 910 is referred to more briefly as the device 910 without any loss of generality. The term “device” applies to any component of the system 100 that is configured to communicate with other components of the system 100 over a wired or wireless network. Thus, the device 910 may be, e.g., the air handler 110 in combination with its AHC 210, or the furnace 120 in combination with its IFC 220. This discussion may refer to a generic device 910 or to a device 910 with a specific recited function as appropriate. An appropriate signaling protocol may be used to govern communication of one device with another device. While the function of various devices 910 in the network 200 may differ, each device 910 shares a common architecture for interfacing with other devices, e.g. the local controller 290 appropriately configured for an HVAC component 920 with which the local controller 290 is associated. The microprocessor or state machine in the local controller 290 may operate to perform any task for which the device 910 is responsible, including, without limitation, sending and responding to messages via the data bus 180, controlling a motor or actuator, or performing calculations.

In various embodiments, signaling between devices 910 relies on messages. Messages are data strings that convey information from one device 910 to another device 910. The purpose of various substrings or bits in the messages may vary depending on the context of the message. Generally, specifics regarding message protocols are beyond the scope of the present description. However, aspects of messages and messaging are described when needed to provide context for the various embodiments described herein.

Each of the components 210, 220, 225, 230a, 230i, 240,250, 260 may include a general interface device configured to interface to the bus 180, as described below. (For ease of description any of the networked components, e.g. the components 210, 220, 225, 230a, 230i, 240, 250, 260, may be referred to generally herein as a device 290. In other words, the device 290 of FIG. 2 is a proxy for any of a furnace, a heat pump, a subnet controller, etc, and that device's associated interface means.) The data bus 180 in some embodiments is implemented using the Bosch CAN (Controller Area Network) specification, revision 2, and may be synonymously referred to herein as a residential serial bus (RSBus) 180. The data bus 180 provides communication between or among the aforementioned elements of the network 200. It should be understood that the use of the term “residential” is nonlimiting; the network 200 may be employed in any premises whatsoever, fixed or mobile. In wireless embodiments, the data bus 180 may be implemented, e.g., using Bluetooth™ or a similar wireless standard.

Turning now to FIG. 3A, illustrated is a diagram 300 of a series of steps that occur in relation to a commissioning of the unit 155. The diagram 300 includes an enter state 301, a device commissioning state 303, and an exit state 305. The HVAC system 100 can be described as being partitioned into a plurality of subnets, each subnet controlled by its own active subnet controller 230a.

Device commissioning can generally be defined as setting operational parameters for a device in the network of the HVAC system, including its installation parameters. Generally, device commissioning 300 is used by the subnet controller 230 when it is active to: a) set operating “Installer Parameters” for a networked device, such as air handlers 110, (henceforth to be referred to collectively, for the sake of convenience, as the unit 155, although other devices are also contemplated), b) to load UI/Gs 240, 250 with names and settings of “Installer Parameters and Features” of the units 155, c) to configure replacement parts for the units 155, and d) to restore values of “Installer Parameters and Features” in units 155 if those “Parameters and Features” were lost due to memory corruption or any other event. Device commissioning is a process used in the HVAC system 100, either in a “configuration” mode or in a “verification” mode.

In the “configuration” mode, the unit 155 shares its information with the subnet controller 230a in an anticipation of being employable in the HVAC system 100, and an appropriate subnet. Generally, the commissioning process 300 provides a convenient way to change or restore functional parameters, both for the subnet controller 230a and the unit 155.

In both the “verification” mode and the “configuration” mode, the unit 155 is checked for memory errors or other configuration or programming errors. There are differences in device 260 behavior between the “configuration” mode and in the “verification” mode, to be detailed below.

The “subnet startup” mode programs the Subnet controller 230 to be active. The “subnet startup” mode enables subnet communications, (i.e., communication within a subnet), and also deactivates a “link” sub-mode. A “link” mode may be generally defined as a mode that allows a number of subnets to work together on the same HVAC network 100, and that assigns subnet numbers for each subnet to allow this communication.

The “installer test” mode is employed when an installer installs and tests aspects and devices 110 of the HVAC system 100. The “normal operations” mode is an ongoing operation of units 155 of the HVAC system 100 in a normal use.

More specifically, the device commissioning state machine 300 can be employed with: a) the “configuration” mode, which is invoked when transitioning to the commissioning state from the “subnet startup mode” or “installer test” mode, or the “normal mode”, or b) a “verification” mode. The “verification” mode is invoked when transitioning to the commissioning state from the “subnet startup” mode.

The following describes an illustrative embodiment of a process of commissioning 300 the HVAC unit 155, first for a “configuration” mode, and then for a “verification” mode. The process of commissioning differs from a “subnet startup,” in that commissioning requires that the network configuration, including configuration and activation of subnet controllers 230, has already been completed before the commissioning 300 of the device 260 can start. Please note that there can be more than one subnet controller 230 on a subnet, but only subnet controller 230a is active at any one time.

In one embodiment, in order to enter into the state 320 of the process 300 in the “configuration” mode, the unit 155 receives either: a) an “aSC” (‘active subnet controller’) Device Assignment message”, having “Assigned State” bits set to “Commissioning”; or b) a receipt of an “aSC Change State” message, with “New aSC State” bits set to “Commissioning,” from the active subnet controller 230. For both “configuration” and “verification” modes, an “aSC Device Assignment” message can be generally regarded as a message that assigns the unit 155 to a particular active subnet controller 230a. For both “configuration” and “verification” modes, an “aSC Change State” message can be generally regarded as a message that starts and ends employment of the commissioning state diagram 300 for the units 155 and all other devices on the subnet.

In one embodiment, in the state 320 in the configuration mode, all units 155 respond to the “aSC Device Assignment” message with their respective “Device Status” messages, indicating that the units 155 are now in commissioning process 300 due to their response to this previous message. For both “configuration” and “verification” modes, the “Device Status” message can be generally defined as message that informs the active subnet controller 230a of what actions are being taken by the unit 155 at a given time.

However, alternatively, in other embodiments, in the state 320 in the “configuration” mode, if the units 155 are instead busy, as indicated by “aSC Acknowledge” bits of the “Device Status” message sent to the subnet controller 230a set as a “Control Busy,” the active subnet controller 230a will wait for the busy units 155 to clear their “aSC Acknowledge” bits before proceeding with further elements of the Commissioning 320 process. The units 155 then resend their “Device Status” messages as soon as they are no longer busy.

From this point on, all units 155 send their “Device Status” messages periodically and on any status change, both during and after the commissioning 300. If the unit 155 does not clear its “aSC Acknowledge” bits within a minute (indicating its control is no longer “busy”), the active subnet controller 230a sends an “Unresponsive Device2” alarm for each such unit 155. If in “configuration” mode, the active subnet controller 230a remains in the waiting mode indefinitely, until the unit 155 responds correctly, or the subnet is reset manually or after a timeout is reached. In “verification” mode the active subnet controller 230a proceeds further to exit the state.

In the “configuration” mode, each unit 155 remembers all of its optional sensors that are currently attached to it. Furthermore, each unit 155 may store a local copy in its non-volatile memory (“NVM”) of all of any other unit features that it is dependent on. A unit 155 feature can be generally defined as any datum that is fixed and cannot be changed by the installer, serviceman or the home owner. Changing of a “Feature” value normally involves reprogramming of the units 155 firmware.

In at least some embodiments, a feature is something that is fixed value, that is hard-wired into a device. In other words, no installer or home owner can change it. Features are programmed into the unit 155 during a manufacturing or an assembly process. Features can be recovered in a home, during a Data non-volatile memory (“NVM”) recovery substate of Commissioning state only—the recovery substate happens automatically and without installer or user intervention. In a further embodiment, parameters can be changed by the installers only. In a yet further embodiment, the HVAC system 100 employs “variables”—those can be changed by the installers and also the home owners.

In some embodiments, a “Parameter List” is normally a Feature that contains a special list of specific parameters included in the unit 155. Parameter values can be changed, and their state can be changed also (from enabled to disabled and vice-versa), but their presence is set once and for all in a given firmware version. Therefore, a list of Parameters (not their values) is also fixed, and is thus treated as a “Feature.”

However, although elements of the “configuration” mode commissioning and “verification” mode commissioning are similar, when the active subnet controller 230 is in “verification” mode instead of in “configuration” mode, the active subnet controller 230a can exit commissioning 300 regardless of the value of the alarms of the units 155. However, alternatively, if the active subnet controller 230a is in “configuration” mode, the active subnet controller 230a will not exit from its commissioning state 300 for as long as at least one unit's 155 “aSC Acknowledge” flags are set to “Control Busy.” In one embodiment of the “verification” mode, the active subnet controller 230a timeouts the installation and resets the subnet to default parameters.

In the “verification” mode, assuming the unit 155 operates with a non-corrupted (original or restored copy) NVM, each unit 155 checks any of its attached sensors to see if they match with the parameters that were present in a most recent configuration of the unit 155. In some embodiments, alarms are generated by the unit 155 for missing or malfunctioning sensors as soon as the faulty condition is detected, to be employed by the user interfaces and gateways present on the subnet to notify the installer or homeowner of the encountered problem. The unexpected absence of certain sensors may inhibit the operation of the unit 155 or the subnet. This is normally manifested by the signaling of the appropriate Service Bits in the Device Status message used by the active subnet controller 230a, to determine the operational viability or health of the subnet's systems.

In some embodiments, the device commissioning process 300 then transitions into a state 330, and then ends, upon either: a) the last unit 155 receiving all of unit 155 parameters that it is dependent on, when in “verification” mode; or b) upon a request by a user, when in “configuration” mode. The active subnet controller 230a then proceeds to ensure that no subnet unit 155 has its “aSC Acknowledge” flag set to a “Control Busy” state. The “aSC Acknowledge” flag not being set indicates that all of a non-volatile memory of a given unit 155 had been written to with the necessary parameters. If no “Control Busy” state is detected, the active subnet controller 230a then issues the “aSC Change State” message, which forces the unit 155 from a commissioning state to a non-commissioning state, in either a “configuration” or a “verification” mode.

In some embodiments, when the unit 155 in the process 300 fails its NVM data integrity check in an “NVM Check State,” and the active subnet controller is unable to perform NVM Recovery, the unit 155 instead employs its default data stored in its non-volatile (Flash) memory and/or uses default calculations to initialize the data dependent on other devices in the system. The other device data to be used for commissioning could have been obtained in either the “verification” or “configuration” mode. For data or other parameters that were not transferred or generated as part of that commissioning 300 session, default values are used.

In one embodiment, upon a detection of a system configuration error, such as a missing device whose features or parameters the unit 155 depends upon, it uses the locally stored copy of the other device's features that it depends upon, and ignores any potential feature value conflicts. In another embodiment, the unit 155 uses the locally stored copy of other parameters of the unit 155 that it depends on and ignores any potential dependent parameter value conflicts. In other words, the unit 155 employs a first installed parameter as a template for a second installed parameter on a second device. In a third embodiment, the unit 155 will change its parameter or feature values only if explicitly instructed by the active subnet controller 230 or the UI/G 240, 250.

The system 100 may be configured to limit allowed configurations of units 155. For example, it may be determined that certain configurations of the system 100 are undesirable or incompatible with proper operation of the various units 155. In various embodiments the various units 155 in the subnet are assigned credentials during commissioning to operate on the subnet. The aSC 230a may be configured to ignore a request made during the commissioning state from a unit 155 outside a permitted configuration set from registering with the aSC 230a to prevent undesired or unpredictable operation that might otherwise result.

Turning now to FIG. 3B, illustrated is an HVAC device state machine 310 illustrated for a subnet, including the unit 155, in more detail. Heavy solid lines indicate normal state transitions when the subnet is transitioning from one state to another state, dashed lines indicate a subroutine call, and light solid lines indicate unexpected yet valid transitions. All states other than state 326 represent device states, and the state 326 represents a message handling routine.

As is illustrated in the present embodiment, a reset state 312 of a subnet advances to a NVM CRC check 316 for a given device (such as unit 155). If the device fails the test, the device advances to a NVM programming 318. If the device passes, however, then in subnet startup 320, the device is assigned an address (Equipment Type number) and some features and parameters of the unit 155 may be shared with the subnet. Then, in substate 324, device commissioning as described in FIG. 3A occurs. This then leads to an installer test state 328. This, in turn, then leads to a link mode startup 330, as described above. Finally, then in a step 334, normal system operation occurs, although system can reset to state 312 or be brought to states 314 or 332 via diagnostic messages handled in a state 326.

In a further embodiment, during the NVM CRC check 316, the state machine 310 can advance to a NVM programming state 318. This can occur due to such factors as a failure of a non-volatile memory, or an initial programming of the NVM. In a yet further embodiment, each of these units 155 is programmed to deal with one form of a diagnostic message regarding system errors in a state 326, and from there to testing the device 160 itself in an OEM test mode 332.

Turning now to FIG. 3C, illustrated is a state flow diagram 340 for the active subnet controller 230 in relation to the unit 155. Generally, is the responsibility of the active subnet controller 230a to implement proper state transitions. The other units 155 follow the explicit direction of the aSC 230a for all valid transactions. These state diagrams are included to help ensure that a state of the unit 155 is the same as the subnet controller. The SC 230a is responsible for device synchronization. If the unit 155 is detected out of synch with the rest of the system, the aSC 230a, in some embodiments, immediately tries to bring the unit 155 to the current system state, if possible.

If an addressable unit 155 is detected in subnet startup 342, the subnet controller 230a applies asynchronous startup rules, which generally pertain to how many parameters are to be passed between device 160 and the active subnet controller 230a.

If an addressable unit 155 is detected in commissioning 345, installer test 346, link mode 347 or normal operation 348 substates, the unit 155, in some embodiments, is brought to the current state via a resend of an “aSC Change State” message, which involves transitioning from a first current aSC state to a second current aSC state.

In some embodiments, if a unit 155 is detected in OEM Test or Soft Disabled state, the unit 155 shall be reset by the active subnet controller 230a in a step 342. If a unit 155 is detected in “Hard Disabled” or “NVM Programming” state, the active subnet controller 230a assumes that it is not available on the subnet

In a further embodiment, inactive subnet controllers 230i are required to keep the most up to date subnet and HVAC system configuration information. Inactive subnet controllers 230i listen to all UI/G and aSC messages and continuously update their non-volatile memory to attempt to be as consistent as possible with the settings stored in active subnet controller 230a.

Various Aspects of Updating Variable Parameters in Communicating and Non-Communicating Devices

There are various approaches to updating parameters within addressable units 155, which will first be introduced, and discussed in more detail below.

a) retrieving both fixed and non-fixed parameters from the device 155 of the HVAC network 100, and allowing a user to update the non-fixed parameters of the HVAC network 100, such as described regarding FIG. 4B, below;

b) updating parameters when the updated values of one set of variable parameters within the HVAC addressable unit 155 are dependent upon the values of another parameter within the same device, such as described regarding FIG. 4C, below.

c) updating parameters of a second non-communicating device when the value of a non-communicating device is updated by a communicating device with the employment of “non-communicating parameters,” such as is described regarding FIG. 5, below. In other words, a list of variable parameters, itself a feature, is used to update the non-communicating device;

d) updating parameters of first unit 155 when a first device depending upon the features (non-changing parameters) of the second unit 155, such as is described regarding FIG. 6, below. For example, the unit's parameter value depends on the other device's feature value. For example the default “High Cooling CFM” setting is calculated and its possible range is adjusted based on the tonnage of the outdoor unit. So, if the outdoor unit's tonnage is 4 ton than the High Cooling CFM is limited to range 1400 to 1600 (3.5*OU tonnage to 4*OU tonnage).

e) when a change of a variable parameter of a first device is dependent upon a change of a variable parameter of a second device, and this change gets propagated through an HVAC system, such as discussed regarding FIGS. 7A and 7B, below. For example, a value of sensor “zone number” parameter may be dependent on the value of “total number of zones” parameter, so that one sensor is not mistakenly assigned to a zone number that does not exist.

Turning now to FIG. 4A, illustrated is an exemplary method 400 for updating variable device parameters within devices of the HVAC network 200 of the HVAC system 100. This flow generally applies to subsection “a”, above. For ease of explanation, addressable units 155 may be interchangeably referred to as “devices” for the rest of this document. After a start step 402, in a step 410, all fixed parameters are retrieved from all networked devices on an HVAC subnet, and these variable parameter values are stored to a user interface, such as user interface 240. In a step 415, in some embodiments, all variable parameters are retrieved from all networked devices on the HVAC subnet and are stored in the user interface. In a step 417, a user is given an option by the user interface to modify a value of a variable parameter of at least one networked device of the subnet.

Turning now to FIGS. 4Bi and 4Bii, illustrated is an exemplary flow diagram for a method 425, such as may be employed with the above commissioning steps of the subnet 400, that updates parameters within an HVAC device that are dependent upon other parameters that are stored or updated within that same device. This can relate to situation “b”, described above.

In the exemplary method 425, after a start step 430, in a step 435, a UIG (either a user interface or a gateway that can include a user interface) sends a device parameter value change message to a device, such as the addressable unit 155, with an updated value of an installer parameter.

In one embodiment, in a step 440, an HVAC networked device determines whether a parameter definition, received from the UIG 405, has changed. An example of a changed parameter definition would be a change of a flag from enabled to disabled for a given networked device. If the parameter definition has not changed, the method advances to step 455. If the parameter definition has changed, in a step 445, the device sends a “Device UIG Parameter Definition by Number” message to the UIG 405 that contains the new parameter definition. Then in step 450, the device sends a “Device UIG Parameter Value by Number” message containing the parameter value and its flags for all other affected parameters in the same group. For example, if a comfort level parameter were changed, this could affect a humidity range that is allowable, and a work schedule for the networked HVAC device, all of which could be related parameters within the same device.

In an exemplary further embodiment, an enable/disable flag indicates if a parameter is currently applicable based on values of the other parameters within the device. After a “UI/G DEVICE Parameter Value Change” is received, the IFC 220 will send parameter value messages for every parameter that changed its enabled/disabled status due to that parameter value change. After those messages are transmitted, the IFC 220 sends an appropriate acknowledge message to confirm the parameter value update.

In a step 455, it can be determined by the networked HVAC device, such as the device 910, whether a parameter update is within an allowed range. If the parameter update is within an allowed range, the networked HVAC device updates its own internal memory to include a copy of the updated parameter that was found to be within range by the networked HVAC device in a step 460. If the parameter update is not within the allowed range, the HVAC networked device keeps its previous parameter value in a step 465.

In a step 470, the networked HVAC device, such as the device 910, can send the UIG the parameter value now stored within in the device, which can be either the updated parameter value or the previous parameter value, as determined in the step 455. In a step 475, the UIG relays all changed parameters to an active subnet controller, such as the active subnet controller 415. In a step 480, the active subnet controller updates its stored backup parameter values and acknowledges all changed parameters that were forwarded from the UIG, such as the UIG 405.

In a step 485, the UIG can relay all of the changed parameter values received from the networked HVAC device, such as the device 910, to other HVAC devices (not illustrated) on the subnet that have registered a parameter dependency that matches a changed parameter of the device 910. This registration process can occur when the active subnet controller had previously forwarded to the UIG an “aSC Device Found Devices List Parameters” received in a “parameter scan” state of the active subnet controller during an activation sequence of the active subnet controller.

In a step 490, the UIG determines whether all of any other HVAC networked devices on the subnet have updated their parameters that depend upon the updated parameter and acknowledged such. If it is determined a given networked HVAC device has not acknowledged its updated parameters, the exemplary method 400 can loop back to step 435, and has that device go through the method 425 for its new parameter. If it is determined that all other devices have updated the appropriate parameters, then the method stops in a step 490.

Turning now to FIG. 5, illustrated is an exemplary flow for a method 500 for commissioning a networked HVAC device that is a non-communicating device. This corresponds to situation “c”, described above, wherein a communicating device commissions a non-communicating device. Generally, in the method 500, a communicating device can mimic a non-communicating device so that the installer programs the communicating device in lieu of the non-communicating device. The communicating HVAC device then programs non-communicating HVAC device through use of a feature set of definitions of variable parameters that are programmed within the first device.

Generally, the exemplary method 500 can allow a communicating device, defined as an HVAC device that can directly communicate with an installer, the communicating device often being an indoor HVAC device, to set its own internal parameters and to also operate with another HVAC device that is either communicating or non-communicating device of a same type, i.e., a device that can not directly communicate with an installer. The non-communicating device can be an outdoor device, although not all outdoor devices are non-communicating units. Generally, information about non-communicating equipment is stored as fixed parameter types in a feature manifest in the various communicating units 155, e.g. indoor units that can program this non-communicating equipment, e.g. outdoor units.

In one embodiment, before entering into the method 500, if during a “feature manifest communication” in the configuration process of the commissioning 300, if the IFC 220 did not recognize a presence of a communicating outdoor unit, such as a communicating Humidifier or Dehumidifier, as opposed to a non-communicating device, the IFC 220 will enable its own non-communicating parameters for those missing devices. These parameters, although they represent variables, the types of parameters are fixed and part of the feature manifest. When requested by the active subnet controller 230, the IFC 220 sends all “non-communicating parameters” with enabled/disabled flag based on the communicating feature manifest of the other communicating devices on the subnet.

Generally, default parameter values for non-communicating and installer parameters are then loaded into the non-volatile memory of the communicating devices 110 on first entry in configuration (commissioning state, such as discussed in the state diagram 300, above), and also when diagnostic inquiry command “Set Default Installer Parameter Values” is executed.

In the exemplary method 500, after a start step 510, a communicating HVAC device checks for both a communicating and a non-communicating device of a sake kind in a step 515, such as through employment of a “Non_Comm_Check_Scan_State” enquiry. A goal of a “Non_Comm_Check_Scan_State” is to inquire of an installer or the subnet controller 230, which is an active subnet controller, what non-communicating equipment there is attached to the communicating devices.

In a step 520, it can be determined whether a found device on a HVAC subnet during a manifest check is a non-communicating device or a communicating device. If the found device is a communicating device, the method 500 advances to a stop step 530. However, if the found device is not a communicating device, in a step 525, the communicating device allows an installer to program the non-communicating device, through a programming of known fixed-type parameters, the parameter types are stored in the communicating device as part of the feature manifest. The communicating unit 155 then conveying the fixed type but variable value parameters to the non-communicating device. The internal features of the non-communicating device typically mimic features of a communicating device when being installed by an installer.

In one embodiment of the method 500, the information about non-communicating equipment is stored as parameter types in the devices that directly control this equipment, e.g., indoor units, which would therefore be communicating devices. The process of configuring the non-communicating equipment can be equivalent to updating parameter values. This state is optional and it is only entered when in configuration mode.

For example, with the non-communicating parameter “Non-communicating Outdoor Unit” initially at default value (0=no non-communicating outdoor unit attached to the IFC), both the “Non-communicating Outdoor unit capacity” and the “Minimum non-communicating outdoor unit capacity” are disabled (not applicable) parameters. If the “Non-communicating Outdoor Unit” is changed to “2 stage A/C” unit, both parameters will become enabled (applicable) and the IFC 220 will send “Device Parameter Value By Number” messages with the enabled bit set for both parameters followed by the message to confirm the “Non-communicating Outdoor Unit” parameter change. This is applicable for all IFC parameters within a same group/list. The IFC 220 stores the non-communicating parameter values in non-volatile memory and protects them with a checksum. These values can then be employed by the networked HVAC device.

The above example employs device parameter dependencies using the non-communicating parameters. Non-communicating parameters can also be dependent on one another.

Turning now to FIG. 6A, illustrated is an exemplary flow of a method 600 for commissioning the parameters of the addressable unit 155 wherein its own internal parameters when parameter validity of the networked HVAC unit 155 depend upon network configuration and/or other device manifest features of a second device. This generally corresponds to situation “d”, discussed above.

Various device internal parameters are configured differently, depending upon other feature parameter values (i.e., permanent) components of the network 200 of the HVAC system 100. In a further embodiment, the method 600 allows for one device to set its own internal parameters and operating modes, based on information published by other devices 110 on the subnet, without an involvement of the active subnet controller 230a.

An example of commissioning parameters when internal parameters and parameter validity depend upon network configuration and/or other device features of a second network device is programming an indoor unit blower having a cubic feet per minute (CFM) speed for outdoor units having various numbers of heating or cooling stages. During the commissioning process 300, the unit 155 listens to an “outdoor unit feature manifest” and then sets its own internal parameter values as well as parameter validity, i.e., whether the parameter is enabled or disabled. An “outdoor unit feature manifest” can be generally defined as a manifest of parameter types of outdoor units for a subnet, and their parameter values. Indoor units can calculate default values, such as whether a given parameter setting is applicable for the unit 155 of the HVAC system 100 for HVAC network 200 operation or not, and send the information to the installer. For example, setting a “Low Cooling CFM” for a 1-stage outdoor unit 155 is not applicable. Similarly, the indoor unit 155 can monitor for the presence of other accessories such as a “Humidifier” and “Dehumidifier,” and set its own internal parameters as determined by these devices, as well.

In the exemplary method 600, after a start step 610, a plurality of devices, one of which can be an indoor device, enters the commissioning process 300. In a step 620, the device reads a feature manifest of the second device, which is a listing of what permanent features are available and disclosed to the device. In a step 625, the first device sets its own parameter validity as determined by an element of the outdoor feature manifest. In a step 630, the first device 155 sets its own internal parameter value as determined by the outdoor feature manifest.

In a step 635, the first unit 155 informs an installer on the validity and value of the set parameter. In a step 640, it is determined if there is yet another HVAC device on the subnet. This can be determined by finding indicia of another outside device in the outdoor feature manifest. If there is another device, then the method loops back to step 615, and the device looks at parameters of yet another device, and uses the parameters of the yet another device to set its own parameters, and again transitions through the method 600. If there is not another device, the method 600 stops in a step 645.

Turning briefly now to FIG. 6B, illustrated is an exemplary overview of a messaging flow messages implemented in a commissioning state between the subnet controller 230a, the UIG 250, and the unit 155, and includes messages in the beginning and an end of the state. For example, FIG. 6B illustrates both the “Device Status” message and the “GUI Status state” discussed above.

Turning briefly now to FIG. 6C1, illustrated are exemplary communication flows for a “non-communicating check scan and parameter scan” message flow. As is illustrated, various messages, such as a “Device Dependent Parameter List” and corresponding definitions are provided. This flow can be employed in conjunction with the method 600.

Turning briefly now to FIG. 6C2, illustrated is an exemplary “Non-Communicating Check Update and Parameter Update” message flow. As a plurality of devices 110 are disclosed as having their parameters modified, such as by the “Device UI/G Parameter Value By Number” message to a first unit 155 and the device 2110. This flow can also be employed by the method 600.

Turning now to FIG. 7A1, illustrated is an exemplary method 700 for updating and propagating a value of an internal parameter of a first device when the value is dependent upon a second device. After a step start 710, in a step 720, devices on a subnet of the HVAC 100 enter into the commissioning process. In a step 730, each device publishes its own variable parameter values. In a step 735, the ASC 230a asks all devices whether they have read various variable parameters, such as all necessary variable parameters. If all devices have read all variable parameters, the flow stops in a step 745. However, if they have not, the in step 740, the ASC commands the devices having the needed variable value information to republish all necessary parameters in a step 740, and the method again asks all devices in the step 735.

Turning now to FIG. 7A2, illustrated is a method 750 for updating variable parameter values in an HVAC network 200 through employment of a user interface, such as user interface 240. After a start step 752, in a step 754, a user interface asks each device for a list of dependent parameters.

In a step 756, it is determined whether a user has modified a value of a variable parameter of a first device of the HVAC network from which a second device depends? If no, then the method ends in a stop step 768. However, if yes, then in a step 758, the second device updates and confirms acceptance of the new parameter value to user interface.

In a step 758, the user interface conveys the modified parameter value to the second device employing the variable parameter. In a step 760, the user interface conveys the modified parameter to the second device employing the variable parameter.

In a step 762, it is determined whether a selected device, which can be a third device, a fourth device, and so on, has a variable parameter within it from which a yet still further device depends, which can be a fifth device, a sixth device, and so on. If not, the method ends in a step 768. However, if yes, in a step 764, the selected device updates and confirms acceptance of the new parameter value to the user interface. In a step 766, a user interface conveys modified parameter values to the further device that employs the variable parameter. In one embodiment of the flow 700, the method ends in the stop step 768. In another embodiment, the flow loops back to step 762.

Turning now to FIG. 7B, illustrated is an exemplary high level block diagram of commissioning steps of an embodiment of a subnet 770 including a user interface or gateway (“UIG”) 775 coupled to a device 780, which can be the unit 155, and an active subnet controller 785. These commissioning steps can be used with method 700, which corresponds to situation “e”, described above.

In one embodiment, the active subnet controller 785 enters the commissioning state when an installer interacts with a given device 780 and updates its “Installer Parameters” in a configuration mode. The active subnet controller 785 can also verify in a verify mode.

In FIG. 7B, in state transition “1),” the UIG 775 sends a “UI/G Device Parameter Value Change” message with a new value of an installer parameter “A.” The device 780 updates the value of the requested parameter “A,” if possible. This can correspond to step 720 of the flow 700.

In an optional state transition “2),” after updating, the device 780 responds with a “Device UI/G Parameter Number Definition By Number message” if the definition of the parameter was changed. The unit 155 further responds with a “Device UI/G Parameter Value By Number” message for each other parameter that was affected by the new value of “A,” as long as these newly updated parameters are within the same group, either a non-communicating scan or parameter scan. This can correspond to a step 730 of the flow 700.

A “non-communicating group” can be generally defined as a group of parameters that pertain to a device that can not be directly updated by an installer, but instead by another device 780 or active subnet controller 785. A “parameter group” in this context can be generally defined as a group of parameters that can be directly altered by an installer.

In state transition “3),” the device 780 responds with a “Device UI/G Parameter Value By Number” message for parameter “A.” This message includes the following: parameter number, current value of the parameter, its enable and structure change flags. If the requested parameter change (for the parameter “A”) is outside an acceptable range, the device 780 responds to the UI/G 775 with an unchanged value, i.e., the current value of parameter “A” stored in the device 780, in the “Device UI/G Parameter Value By Number” message. In any event, upon receipt of this message, the UIG 775 can update all changed installer parameters with their new values. This can also correlate to step 730.

In a state transition “4),” the UIG 405 then relays all changed installer parameters to the ASC 415. In a state transition “5),” the ASC 415 acknowledges to the UIG 405 all changed installer parameters. This can correlate to the step 735.

In a further state transition (not illustrated), the UIG 405 then relays the new installer parameter values to other devices 910 (FIG. 9) that have registered any of the installer parameters just changed in their “Device Dependent Parameters List” messages sent to the UIG 405 in previous “Parameter Scan” state. This continues until all updates are made with all devices by all devices that depend upon these changed parameters, and acknowledged by them. The UIG 405 keeps track of all device features and parameters for all devices 910 on the subnet based on the information previously forwarded to it, in the preceding commissioning state substates, by the active subnet controller 415. This can also collate to the step 735 and the step 740.

One employment of the state diagram illustrated in the diagram of FIG. 7B is directed towards allowing a configuration of parameters of the device 910 that are in turn, themselves dependent upon other values within the device 780. In a further embodiment, a plurality of other devices 780 having parameters are updated as a result of updating this device 780.

For example, the IFC 220, in conjunction with the UIG 405, for setting Gas Heating Airflow device dependent parameters. The IFC parameters “Low Heating Airflow,” “High Heating Airflow,” “Low Discharge Air Temperature” and “High Discharge Air Temperature” are dependent on the value of the IFC parameter “Heating Airflow Control Type” (“HACT” parameter). “Low Heating Airflow” and “High Heating Airflow” dependent parameters are enabled, and thus shown to the installer when the “HACT” param=0. However, if the “HACT” param=1, the last two parameters are enabled and shown to the installer. The installer modifies the parameters seen by him or her on the UIG, but not the unseen parameters

Turning now to FIG. 8A, illustrated is an exemplary method flow 800 regarding controlling dependent parameters when a parameter of a first device is dependent upon a parameter of a second device of a subnet of an HVAC system, as initiated in system state machine, primarily in the subnet controller. After an enter step 802, in a step 804, it is determined whether a subnet controller is in configuration mode. If it is, then in step 806, variable parameters are propagated, such as discussed in flow 700. The method 800 then advances to step 808, wherein it is determined whether any device has non-volatile memory (NVM) corrupted. If yes, then a NVM backup data routine is initiated in a step 810. In a step 812, it is again determined whether the subnet controller is in configuration mode.

If not, then in a step 826, either a full or abbreviated feature manifest is generated by the device at the behest of the subnet controller. In a step 828, a non-communicating parameter scan is generated by the subnet controller for a given device. Then in a step 830, a full or abbreviated parameter scan is generated within the device 130, and the method ends in a step 832.

Alternatively, in a step 814, if the state of the subnet is in configuration mode, in a step 814, a replacement check for all devices is performed. In a step 816, a full feature manifest is then performed on the various HVAC devices. In a step 828, a non-communicating parameter scan is generated by the subnet controller for a given device. Then in a step 822, a full or abbreviated parameter scan is generated within the device 130, and the method ends in a step 832. Then, in a step 824, a parameter update, such as described in FIGS. 5-7B, is performed.

Turning now to FIG. 8B, illustrated is a FIG. 8B illustrates an exemplary signal flow associated with a “Replacement Check Message Flow” sub-states of commissioning state in an HVAC network.

Those skilled in the art to which this application relates will appreciate that other and further additions, deletions, substitutions and modifications may be made to the described embodiments.

Claims

1. An HVAC system, comprising: first and second devices coupled via a subnet of said HVAC system; a feature manifest stored by said second device and readable by said first device after said first device enters a commissioning process; and an internal parameter of said first device that is determined by said first device based on said feature manifest.

2. The system of claim 1, further comprising a parameter validity indicium determined by said first device from said feature manifest; and a display employable to convey to an installer said parameter validity indicium and said value of said internal parameter.

3. The system of claim 1, wherein said first device is configured to: set an internal parameter value based on a third device on said subnet; and convey said value to said third device.

4. The system of claim 1, wherein said first device is a subnet controller capable of being configured to operate as a selectable one of an active subnet controller and an inactive subnet controller, and wherein said first device is configured to operate as said inactive subnet controller.

5. The system of claim 1, wherein a validity of said internal parameter is determined by whether said internal parameter is enabled or disabled.

6. The system of claim 2, wherein said value to be conveyed to said installer is a default value.

7. The system of claim 1, wherein said first device is a communicating device capable of determining if said second device is a communicating device, and wherein, in the event that said second device is a non-communicating device, said first device is configured to allow an installer to set internal parameters for said non-communicating device.

8. The system of claim 7, wherein said first device can convey said parameters to said non-communicating device after said installer sets said internal parameters into said first device.

9. The system of claim 1, further comprising a subnet controller coupled to said subnet and configured to control operation of said subnet to implement a heating, cooling, air quality or ventilation algorithm.

10. A method of commissioning devices in an HVAC network, comprising: a first device of a subnet reading a feature manifest of a second device of said subnet; and said first device determining validity of a parameter of said first device based on said feature manifest.

11. The method of claim 10, further comprising said first device setting a value of said parameter based on said feature manifest.

12. The method of claim 11, further comprising reporting said validity and value of said parameter to an installer.

13. The method of claim 10, further comprising: said first device setting an internal parameter value based on a third device on said subnet; and said first device conveying said internal parameter value to said third device.

14. The method of claim 10, wherein said first device is a subnet controller capable of being configured to operate as a selectable one of an active subnet controller and an inactive subnet controller, and wherein said first device is configured to operate as said inactive subnet controller.

15. The method of claim 10, wherein a validity of said parameter is determined by whether said parameter is enabled or disabled.

16. The method of claim 10, wherein said first device is not commissioned in the event said feature manifest is outside a permitted configuration set.

17. A communicating device of an HVAC system, configured to: read a feature manifest stored by a second device after said communicating device enters a commissioning process; and determine a value of an internal parameter based on said feature manifest.

18. The system of claim 17, wherein said communicating device is further configured to: determine a parameter validity indicium from said feature manifest; and communicate said indicium and said value to a display employable to display said indicium and said value.

19. The system of claim 17, wherein said communicating device is further configured to: set an internal parameter value based on a third device on said subnet; and convey said value to said third device.

20. The system of claim 17, wherein said communicating device is a subnet controller capable of being configured to operate as a selectable one of an active subnet controller and an inactive subnet controller, and wherein said first device is configured to operate as said inactive subnet controller.