Actuator for HVAC systems and method for operating the actuator

• US 8,521,332 B2
• Filed: 07/03/2008
• Issued: 08/27/2013
• Est. Priority Date: 07/03/2008
• Status: Active Grant

• Current Assignee: Belimo Holding AG
• Original Assignee: Belimo Holding AG
• Inventors: Tiemann, Dirk, Gort, Urs
• Primary Examiner(s): PATEL, RAMESH B
• Application Number:
  US13/002,266
• Publication Number:
  US 20110153089A1
• Time in Patent Office: 1,881 Days
• Field of Search: 700276-278, 165/58, 165/67, 165/155, 236/1.R, 236/1.E
• US Class Current: 700/276
• CPC Class Codes: F24F 11/46 Improving electric energy efficiency or saving
• CPC Class Codes: F24F 11/54 using one central controller connected to several sub-controllers
• CPC Class Codes: F24F 11/58 using Internet communication
• CPC Class Codes: G05B 19/056 Programming the PLC
• CPC Class Codes: G05B 2219/13063 Synchronization between modules
• CPC Class Codes: G05B 2219/13076 Interprete in pc a ladder diagram, use of sequence engine
• CPC Class Codes: G05B 2219/13148 Object oriented programming

Abstract

An actuator for an HVAC system having a stored model definition defining an HVAC control application, and an element library including a variety of stored model elements and controller modules (D, E) having instructions for controlling a processor of the actuator. The controller modules (D, E) include model elements and are configured to control the sequential order of their execution. The controller modules (D, E) are further configured to propagate any external data input (S66′, S68′) to their model elements prior to executing their first model element, and to propagate any data output (S63, S65, S67, S69) to external components after executing their last model element. The controller modules (D, E) are instantiated in different threads of execution, so that data is interchanged asynchronously between instantiated controller modules (D, E) and neither temporal dependencies nor change of value links are imposed on components of the HVAC control application.

Claims

1. An actuator for HVAC systems, the actuator comprising:

a network interface for connecting the actuator to a communication network,

a bus interface for connecting the actuator to a sensor/actuator bus,

a data store, and

a processor connected to the data store;

wherein the actuator further comprises;

a loader configured to receive via the communication network and store in the data store a model definition defining an HVAC control application;

an element library including a variety of stored model elements comprising instructions for controlling the, processor, and

controller modules configured in each case to control the sequential order of execution for associated model elements referenced by the respective controller module, to propagate external data input to its associated model elements prior to beginning the execution of the model element defined first in the sequential order, and to propagate data output from its associated model elements to the outside of the respective controller module at completion of the execution of the model element defined last in the sequential order; and

a model interpreter configured to implement based an the model definition the control application for execution on the processor, by instantiating controller modules and their associated model elements as referenced by the model definition, assigning at least one instantiated model element to a device attached to the sensor/actuator bus, and instantiating the controller modules in each case as a different thread of execution, wherein data is interchanged asynchronously between instantiated controller modules.

2. The actuator of claim 1, wherein the model elements are in each case configured to read input data from one or more defined data input buffers associated with the respective model element, and to write output data to one or more defined data output buffers associated with the respective model element;

the model interpreter is further configured to link, based on linking information included in the model definition, output buffers of instantiated model elements to input buffers of instantiated model elements; and

the controller modules are configured to propagate in each case, upon completion of the execution of model elements referenced by the respective controller module, data values from the model element'"'"'s output buffer to a linked input buffer of a model element referenced by the respective controller.

3. The actuator of claim 1, wherein the model definition includes identifiers of model elements and parameter values applicable in each case to the respective model element;

the model interpreter is configured to instantiate in each case the model element from the element library based on the identifier and parameter values; and

the controller modules are configured to execute in individual processing intervals assigned in each case to the respective controller module.

4. The actuator of claim 1, wherein the model definition includes graphical user interface data associated with model elements referenced by the model definition, the graphical user interface data including at least position information for positioning on a display a graphical representation of the respective element.

5. The actuator of claim 1, wherein at least some of the stored model elements are configured to be operable in different modes, the modes being selectable through setting at run-time of a state associated with all instantiation of the respective model element.

6. The actuator of claim 1, further comprising a server module configured to transmit to a web browser a graphical representation of the control application via the communication network based on the model definition, to transmit to the web browser for display in the graphical representation input/output values associated in each case with a model element referenced by the model definition, to receive from the web browser parameter values associated in each case with a model element referenced by the model definition, and to store in the actuator the parameter values assigned to an instantiation of the respective model element.

7. The actuator of claim 1, wherein the stored model elements include elements representative, of at least one of controller, PID controller, two point controller, limiter, timer, Boolean logic module, time period management module, heating curve module, filter module, floating average calculation module, flip flop module, input selector module, constant value module, comparator, mathematical operation module, state checking module, error catching module, and error trigger module.

8. The actuator of claim 1, wherein the network interface is configured for communication according to the Internet Protocol over an Ethernet communication network;

the sensor/actuator bus includes one of MP-Bus and BACnet-bus;

the model definition is defined in a mark-up language;

the stored model elements are defined in Java byte code;

the processor is a Java processor configured to execute Java byte code; and

the loader is further configured to store in the actuator at least one HTML version of the model definition.

9. A method for operating an actuator of an HVAC system, the method comprising:

storing in the actuator a model definition defining an HVAC control application;

storing in the actuator an element library which includes a variety of model elements and controller modules, the model elements and controller modules comprising instructions for controlling a processor of the actuator;

implementing in the actuator, based on the model definition, the control application for execution on the processor, by instantiating from the element library controller modules and associated model elements as referenced by the model definition,

assigning at least one instantiated model element to a device attached to a sensor/actuator bus, and instantiating the controller modules in each case as a different thread of execution; and

executing the control application ‘

by the respective controller modules in each case controlling the sequential order of execution for associated model elements referenced by the respective controller module, propagating external data input to its associated model elements prior to beginning the execution of the model element defined first in the sequential order, and propagating data output from its associated model elements to the outside of the respective controller module at completion of the execution of the model element defined last in the sequential order, wherein data is interchanged asynchronously between instantiated controller modules.

10. The method of claim 9, wherein the model elements read input data from one or more defined data input buffers associated with the respective model element, and write output data to one or more defined data output buffers associated with the respective model element;

output buffers of model elements are linked to input buffers of model elements, based on linking information included in the model definition; and

, upon completion of the execution of model elements referenced by a respective controller module, data values are propagated in each case from the model element'"'"'s output buffer to a linked input buffer of a model element referenced by the respective Controller.

11. The method of claim 10, wherein the model elements are instantiated from the element library in each case based on an identifier and respective parameter values included in the model definition;

and instantiated controller modules execute in individual processing intervals assigned in each case to the respective controller module.

12. The method of claim 10, wherein the model definition includes graphical user interface data associated with model elements referenced by the model definition, and a graphical representation of a respective model element is positioned on a display based on position information included in the graphical user interface data.

13. The method of claim 10, wherein selected at run-time is a state associated with an instantiation of a model element, the state setting the respective model element to operate in one of at least two different modes.

14. The method of claim 10, wherein, based on the model definition, a graphical representation of the control application is transmitted from the actuator via the communication network to a web browser;

input/data output values, associated in each case with a model element referenced by the model definition, are transmitted from the actuator to the web browser for display in the graphical representation;

parameter values, associated in each ease with a model element, referenced by the model definition, are received in the actuator from the web browser, and the parameter values are stored in the actuator assigned to an instantiation of the respective model element.

15. The method of claim 9, wherein the model elements are instantiated from the element library in each case based on an identifier and respective parameter values included in the’

model definition; and

instantiated controller modules execute in individual processing intervals assigned in each case to the respective controller module.

16. The method of claim 9, wherein the model definition includes graphical user interface data associated with model elements referenced by the model definition, and a graphical representation of a respective model element is positioned on a display based on position information included in the graphical user interface data.

17. The method of claim 9, wherein selected at runtime is a state associated with an instantiation of a model element, the state setting the respective model element to operate in one of at least two different modes.

18. The method of claim 9, wherein, based on the model definition, a graphical representation of the control application is transmitted from the actuator via the communication network to a web browser;

input/data output values, associated in each case with a model element referenced by the model definition, are transmitted from the actuator to the web browser for display in the graphical representation;

parameter values, associated in each case with a model element referenced by the model definition, are received in the actuator from the web browser; and

the parameter values are stored in the actuator assigned to an instantiation of the respective model element.

19. A computer program product comprising a non-transitory computer readable medium embodying computer program code means for controlling a processor of an actuator of an HVAC system, wherein the actuator

receives via a communication network a model definition defining an HVAC control application;

stores the model definition in a data store of the actuator;

implements based on the model definition the control application for execution on the processor of the actuator, by instantiating from a stored element library controller modules and associated model elements as referenced by the model definition, assigning at least one instantiated model element to a device attached to a sensor/actuator bus, and instantiating the controller modules in each case as a different thread of execution, and

executes the control application by controlling the sequential order of execution for associated model elements referenced by the respective controller module, by propagating external data input for the respective controller module to its associated model elements prior to beginning the execution of the model element defined first in the sequential order, and by propagating data output from the associated model elements to the outside of the respective controller module at completion of the execution of the model element defined last in the sequential order, wherein data is interchanged asynchronously between instantiated controller modules.