Actuator for hvac systems and method for operation thereof

FIELD: information technology.

SUBSTANCE: actuator for a heating, ventilating, and air conditioning (HVAC) system comprises a stored model definition defining an HVAC control application, and an element library including a plurality of stored model elements and controller modules, having instructions for controlling a processor of the actuator. The controller modules include model elements and are configured to control the sequential order of their execution. The controller modules are further configured to propagate any external data input to their model elements prior to executing their first model element and propagate any data output to external components after executing their last model element. The controller modules are instantiated in different threads of execution, so that data is interchanged asynchronously between instantiated controller modules and neither temporal dependencies nor change of value links are imposed on components of the control application.

EFFECT: high accuracy of control.

15 cl, 9 dwg

The technical field to which the invention relates.

The present invention relates to an actuator for heating, ventilation and air conditioning (HVAC), as well as to method of operation of this actuator. In particular, the present invention relates to the actuator HVAC containing a network interface for connecting the actuator to the network communication bus interface for connecting the actuator to the bus sensors/actuators, data store and a processor connected to the data store.

Prior art

In the past, the HVAC system was developed and implemented in the form of combined and, as a rule, proprietary control systems. With the development of technologies based on the Internet HVAC system more adapted towards a more open approach. In particular, the field devices were provided with information processing capabilities and platform Java virtual machine that facilitated the use of control objects in a variety of field devices from different vendors. In addition, thanks to the implementation of field devices, Web servers can access data in field devices through a standard Web browser over the network Internet Protocol (IP).</>

In the patent US 7020532 disclosed control device for a control system that contains a field device, such as a sensor or actuator, and a processor to execute the control algorithm, for example for monitoring environmental parameters in a residential, commercial or industrial sector. The control algorithm maintains a management system at the required level and/or act on it so that this level is dependent on one or more measured values or preset settings. In addition, the control device includes a network interface, an IP (Internet Protocol) and Web server that provides configuration, monitoring, and/or support management system.

In the patent US 6510352 disclosed a control device, such as a field device interface sensors/actuators that contains the Java virtual machine to run Java objects, so that the control device provided the control function, such as process control. These objects process control transmit data values, such as the results of measurement or setpoint on the principle of the links, then there is only one object stores the data value itself, while other objects can only reference (for example, a pointer or address) for the compliance with the adequate data value. Thanks to the transfer of data values based on the reference data is distributed between management facilities to meet the processing requirements for real-time applications, control of technological processes.

In the patent US 6832120 disclosed object-oriented control system containing a network processor and station type field controllers that implement the Java virtual machine that can be programmed using Java objects for specific control functions. As specified in the explicit form of the key for achieving a distributed object-oriented control system in the patent US 6832120 features administrator synchronization information in real time at each station, which controls the flow of data between objects in the system.

In the patent US 6788980 disclosed a control device for controlling system, which can be implemented in the form of an actuating mechanism that contains the processor, configured to provide the operating system in real-time Java virtual machine. This control device also contains a Web server that provides configuration and control of the management system and application development environment that generates Java classes to implement them in control devices. inchbonnie functioning of operator stations and similar data sources, not related to technological processes, supported using simple network time Protocol synchronization (SNTP); while controllers that require high precision machining, are controlled by networks or equipped with means interrupts used to coordinate time update.

To meet the requirements of real-time operation for a typical control applications known control system configured for synchronized data transmission. In essence, synchronized transmission transmission in which the data values are created and/or issued by the data source (the data provider), transferred and/or delivered to a data source (data consumer) in a given time window to meet the specific requirements of the transfer in real time to relevant management applications. Thus, implementation of the synchronized stream data instructs temporary and/or sequential dependence for component participating in the distributed control application. In particular, for the synchronized stream data, you must implement synchronization mechanisms, which require significant computing power and/or capacity is th communication systems.

In the patent US 6167316 disclosed a distributed object-oriented system building automation with asynchronous communication between objects running on different devices. Application objects, which should be informed about the changes in the values of governors of the attributes of another object, use the connection object to establish asynchronous communication between application objects. The connection object manages the transmission of data between two application objects. The connection object is registered in the source object for the source object messages containing the control value of the attribute when changing the value exceeds the specified value (the processing of changing the value). In turn, the connecting object passes the received control value attribute on the destination object. Thus, in patent US 6167316 implemented the messaging engine, which provides timely manner of significant changes in data values between objects that reside in different devices.

The invention

The purpose of this invention is the provision of an actuating mechanism for heating, ventilation and air conditioning (HVAC), as well as the method of operation of this actuator, where the actuator and the corresponding method is missing a number of disadvantages, inherent in the prior art. In particular, the present invention is the provision of an actuating mechanism for HVAC systems and method of its operation, the result of which Executive mechanism allows for control applications in the HVAC systems, not prescriptive temporal dependencies for component management application that communicate.

According to the present invention these objectives are achieved by the features of independent claims. In addition, of the dependent claims and the description is followed by an additional predominant variants of the invention.

Actuator for HVAC systems includes a network interface for connecting the actuator to the network communication bus interface for connecting the actuator to the bus sensors/actuators, data store and a processor connected to the data store.

According to the present invention, achieving the above objectives are derived partly to the fact that the description of the model that defines the controller application HVAC, memorized in the enforcement mechanism. For example, the description of the model is downloaded via the communications network to the data store of the actuator. The description of the model is defined on I is ice markup for example, XML (extensible markup language). For example, the communication network includes a network connection Ethernet and configured for communication in accordance with the Internet Protocol. In addition, the actuator element is stored library, which includes many different model elements and controller modules. Model elements and controller modules contain commands to control the processor of the actuator. For example, the stored model elements and controller modules defined in the byte code of Java, and the processor is a Java processor configured to execute the byte code of Java (for example, IMSYS IM 1101). For example, the stored model elements include elements representing the controller, PID (proportional-integral-differential)controller, on-off controller, limiter, timer, Boolean logic module, the control module time periods, the module of the curve of heat, the filter module, the evaluation module, floating medium, the trigger module, the input selector module constant value, the comparator module mathematical operations, module status, module fixing errors and/or the launcher errors. On the basis of the description of the model in the enforcement mechanism is implemented, the controller application is La its execution in the processor by the instantiation of the controller modules elemental library and the corresponding model elements, referenced in the description of the model, assigning at least one instantiated model element to a device connected to the bus sensors/actuators, and controller instantiation of modules in each case, as distinct from the other thread. For example, the tire sensors/actuators includes MP-bus (proprietary bus sensors/actuators Corporation Bellimo Automation AG), BACnet, Profibus or other Fieldbus. The controller application is appropriate controller modules, each of which controls the sequential order of execution for associated model elements referenced by the respective controller module distributes any external input (i.e. the input data stored components outside of the respective controller module peripheral input buffers of the respective controller module) to its associated model elements prior to the execution of the model element defined in the first sequential order, and distributes any output of its associated model elements outside of the respective controller module after execution of the model element defined in the last paragraph is coherent order, so that provides asynchronous communication between instancevalue controller modules.

Thus, the controller module enables users to hierarchically group (to invest) a lot of different modular elements (components) and to identify the input/output buffers on the peripheral border controller module so that the input/output buffers internal modular elements can be accessed only through these peripheral input/output buffers. For the controller module, it is recommended to periodically performed, the individual update interval/processing. Controller module configured to control, in its interval, sequential processing model elements, resulting in any of the input data are initially (i.e. before processing model elements) from the peripheral input buffer controller module in the input buffers connected model elements. Then the model elements, individually fired in accordance with the sequential order defined by the controller module calculates the output values on the basis of their current data values read from the input buffers. After processing model element controller module distributes the values vyjadrytesyh a corresponding model element connected model elements by reading in each case, the data values stored in the buffer of the output of the modular element (source), and write it to the buffer input is connected modular elements (receivers). If the buffer output data model element is connected to a peripheral buffer its output controller module, the controller module also extends the current value data from the buffer output data model element to the corresponding peripheral output buffer. Different controller modules operate in different threads with individual processing intervals of different duration (i.e. with a different frequency).

Due to the presence of controller modules configured to distribute any external input to all relevant model elements before processing the first model element in the corresponding sequence processing, and distribution of any output from the corresponding model elements on components outside the model of the controller, upon completion of all relevant model elements in the corresponding sequence processing, and thanks to the instantiated controller modules in the form of parallel threads of execution provides asynchronous communication between different controller mod is Olami, that is, between model elements associated with a different controller modules. This gives you the ability to implement and execute management applications in the HVAC systems without temporal dependencies imposed on the components of the control application to communicate, and link application objects to handle the change of value (COV). Therefore, there is no need neither synchronization mechanisms, no messages, providing signaling between objects. Thus, the asynchronous data transfer between the model elements associated with different model controllers, allows you to save a significant amount of processing power, processing time and bandwidth when transferring data, which, otherwise, would be required for synchronization and messaging. In addition, asynchronous data transfer enables the construction and implementation of control HVAC applications with loosely coupled components and, therefore, flexibly and effectively to distribute the control application across multiple logical controller modules in one processor device, but also on multiple processor devices connected between a communication network, for example, by hosting and performing different controller module is th on multiple CPU devices such as actuators or other hardware device containing the processor.

Preferably, the model elements in each case are configured to read input data from one or more specific input buffers associated with the respective model element, and to write the output data in one or more specific output buffers associated with the respective model element. In addition, the configured shell models for binding, based on the information link included in the description of the model, the output buffers are instantiated model elements with the input buffers are instantiated model elements. In addition, the controller module configured to distribute, in each case after the execution of the model elements referenced by the respective controller module, the data values from the output buffer of the model element on the associated input buffer model element referenced by the respective controller. Thus, the model element that provides an output that records (stores) its output in the output buffer. Because of the coupling between the first instantiated model element with the second instantiated model is essential element for forwarding the output of the first model element in the second model element is an output buffer of the first model element associated with the input buffer of the second model element. At the end of processing of a model element, that is, when the output of a model element are placed in a buffer (buffers) output data corresponding to the controller module transmits the data values associated buffers the input data.

In one embodiment, the model includes the identifiers of model elements and parameter values used in each case to the corresponding model element, and the shell model configured for instantiation in each case, the model element from the library based on the identifier and parameter values.

In another embodiment, the actuator includes a server module configured to transmit to the Web browser via the communication network a graphical representation of a control application on the basis of the description of the model. Model description preferably includes data of a graphical user interface associated with model elements referenced in the description of the model. For example, the data of the graphical user interface includes information about the position and/or size information for positioning and/or dimensioning, graphical presentation of the relevant model elements on the display. In addition, in one embodiment, the implementation of the program loader is configured to remember the actuator at least one of HTML (hypertext markup language)version of the model description. The server module also configured to send to the Web browser to display a graphical representation of input/output values associated in each case with a model element referenced in the description of the model, to obtain from a Web browser parameter values associated in each case with a model element referenced in the description of the model, and to remember the actuator parameter values allocated for the instantiation of a corresponding model element. Thus, the current values of the model elements, such as values representing the result of measurement from the sensor or the setting of the actuator, can be presented to the user via a Web browser with a graphical view of a control application. In addition, the user may input settings, such as settings for the PID-controller, through the browser, a graphical representation of a control application to automatically update the appropriate settings in the host application that runs in the enforcement mechanism.

In yet another embodiment, at least some of the stored model elements configured in such a way that they can work in various R is the presses, moreover, these modes can be selected via the settings during the implementation status associated with the instantiation of a corresponding model element. Preferably, these model elements have been configured to specify, as the output value, the current state or mode of a corresponding model element.

Preferably, the network interface configured to exchange data with other relevant actuators via the communication network. Thanks to the network connection to connection more than one actuator, implemented a distributed control application for HVAC systems. Distributed control application operates decentralized network of actuators, each actuator in communication network operates as part of a distributed control application, and this part is determined by the corresponding model description (submodels) and manages as a master device from other devices (slaves)that are connected to the bus sensors/actuators.

In addition to the actuator and a corresponding method of operation of the present invention also relates to a computer software product, with the means containing a series of computer program code for controlling one or more processors of the actuator for HVAC systems, moreover, the computer program product preferably contains machine-readable media containing these tools are computer software code.

Brief description of drawings

Further, the present invention is explained in more detail based on examples with reference to the drawings, in which:

Figure 1 - block diagram illustrating the HVAC system containing actuators, which are connected to the bus sensors/actuators, and communication network;

figure 2 - block diagram, schematically illustrating an actuator containing various functional modules;

figure 3 - block diagram, schematically illustrating a possible sequence of development and creation of model description for full or partial control application HVAC;

4 is a graphical representation of the example of the description of the model, including the controller module, the module bus controller and the module network controller with the corresponding model elements.

5 is a timing diagram illustrating an example of a sequential processing model elements associated with the controller module;

6 is a timing diagram illustrating an example of parallel processing controller modules, which are executed in separate threads;

7 is a timing chart, illustrer is the one example of the sequence of steps of operation of the actuator to perform HVAC control application;

Fig - block diagram, schematically illustrating a possible sequence of the handling of error conditions that appear in the host application HVAC;

Fig.9 is a block diagram illustrating an example of an element with nested (composite element).

Detailed description of the invention

In figure 1 reference number 1 refers to the system of heating, ventilation and air conditioning (HVAC)containing one or more actuators 10, 10'are connected via the communication network 2, such as network IP Protocol over an Ethernet network. Preferably, the actuators 10, 10' includes the engine and are configured to actuate valves and/or dampers for pipes, the feed fluid, for example, to control the flow of water or air in the HVAC system 1 by changing the settings of the dampers or valves, respectively. Depending on the variant of the invention, the communication network 2 is connected to the world wide web (WWW) and is available for remote computers 5, for example a stationary personal computers 51 (PC), via a fixed telecommunications network and/or mobile computers, such as computers 52 type "laptop" or "notebook", personal digital assistants (PDA) or mobile radiotelephones 53, via the mobile radio network such as GSM (global system for mobile communications) network, a UMTS (Universal mobile communication system) and/or wireless local area network (WLAN).

As shown in figure 1, each of the actuators 10, 10' includes a processor 11, 11' and store 12, 12' of data, connected to the processor 11, 11'. Preferably, processor 11, 11' is a Java processor, configured to direct execution of the byte code of Java, such as Java processor IMSYS IM 1101 company Imsys Technologies AB.

Each actuator 10, 10' connected to the bus 3 sensors/actuators, for example the bus MP-Bus company Belimo Automation AG, the BACnet or Profibus. Actuators 10, 10' is configured as the leading device management (subordinates) devices 4 connected to the bus 3 sensors/actuators, such as sensors 41, 41', the actuators 42, 42' or other field devices 43, 43'.

As shown in figure 2, the actuator 10 includes a network interface 20 for connecting the actuator 10 to the communication network 2 and the bus interface 30 for connecting the actuator 10 to the bus 3 sensors/actuators. In addition, the actuator 10 includes various functional modules, including the boot loader 101 software loader 102 model, the shell 17 of the model, the module 103 parameterization module 104 of the monitoring and recording module 105 warning alarm and the operation and error handling module 19 of the Web server.

Loader 101 software is configured to download the firmware (firmware) via the network 2 connection and installation of this firmware to the actuator 10. In addition, the loader 101 software is configured to download and memorize the different model elements in the element library 16 storage 12 data. Each model element represents a functional block that contains commands, such as Java byte code to control the processor 11. Typically, the model element includes one or more buffers of the input data (some model elements, for example element a constant value, can be implemented without the buffer of input data), the functional component, it is possible (input) parameters associated with the functional component, and one or more output buffers (some model elements, for example the launcher errors, can be implemented without buffer output). Model elements configured to read the current values of the input data stored in their corresponding input buffer (buffers), to calculate based on the value (values) of the input data one or more output data values using a functional component of the s and associated with it parameters and to write the value (values) of the output data buffers (buffers) output. Model elements can be developed and provided in the form of public modules open source.

Model elements are divided into groups of control elements, elements, input/output and items of General use. For example, the model elements in the group of control elements include various controllers, such as PID controller or a two-position controller, limiter, to create and limits the output value to a specific range of values of the input data, the timer module Boolean logic, for example, the function of the logical AND, OR and/or NOT, the control module time periods, for example, to install a temporary period, such as time of day (day/night, until morning/afternoon), holiday period or time of year (winter, spring, summer, autumn), the module of the curve of heat, the module filter module calculate the floating medium, the trigger module, the input selector to select the output value on the basis of a certain criterion based on different input data, the module constant value, a comparator for comparing the values of the input data, the module mathematical operations to perform mathematical operations such as addition, subtraction, multiplication, division, accumulation, average calculation or determination of the minimum or maximum values and/or module check status to check the current status of the nested model elements. For example, the model elements in the I/o include elements representing device 4 on the bus 3 sensors/actuators, such as sensors, actuators and connecting elements for connecting more than one sensor or actuator to the bus 3 sensors/actuators or actuators 10, 10'connected to network 2 connection. For example, the model elements in the General purpose include the module fixing errors and/or the launcher errors for the connection management application HVAC module 105 alarms and error handling.

Element library 16, in addition, contains model elements with nested (composite elements), and controller modules, in particular the model controller modules, the bus controller modules and the network controller modules. Controller modules and components configured to include a variety of selected model elements, which are connected to each other. Table 1 shows the hierarchical relationship of controller modules, model elements with nested (composite elements) and model elements. Figure 9 shows an example of element 90 with nested (composite element)containing two interconnected is of nutrena nested element 901, 902. Each of the inner nested elements 901, 902 contains several interconnected model elements. As shown in Fig.9, the internal elements are connected only to other internal elements on the same hierarchical level and/or buffers input/output data covering element of a higher level of nesting. Depending on the specific application controller modules include model elements and/or model elements with nested (composite elements); and a model element with nested (composite element) includes model elements and/or model elements with nesting. Typically, the model controller module 401 is associated with interconnected (linked) controls, while the bus controller module 402 and a network controller module 403 is associated with the elements of input/output. Bus controller module 402 and a network controller module 403 encapsulate all interactions with the underlying bus 3 sensors/actuators and the communication network 2, respectively. In particular, the bus controller module 402 and a network controller module 403 encapsulate the retrieval of sensor data from the job configuration values of the actuators on the devices connected to the bus 3 sensors/use the enforcement mechanisms and the communication network 2, respectively.

Controller modules and components configured to control the sequential order of execution of the associated model elements and/or model elements with nesting and to control the propagation of data between related model elements and/or model elements with nesting. The processing sequence is determined by the order in which linked (connected) model elements, types of model elements and/or the established priorities. A composite element (model element nesting) is processed taking into account the sequential order, and the levels of its elements, all the elements are processed, and the output value are distributed to the appropriate connections. For example, on Fig for processing(updating) of a model element 90 with nesting initially processed internal model elements model element 901 nesting, then exit the nested model element 901 is transmitted to the nested model element 902, and then processed internal model elements nested model element 902. Also the user has the possibility to set the order for items with nesting. In particular, controller modules configured to distribute at the start, the current values of the input data from their I / o buffers input data on relevant related buffers the input data associated model elements. In addition, controller modules configured to carry out the subsequent execution of their model elements based on the specified sequence processing, and after the execution of the model element (or component) is to distribute the output from the buffer (buffers) output completed model item in the data buffers associated with the output buffer (buffers) completed data model element. Due to this, the output distributed control modules associated buffers the input data of other model elements included in the controller module, and a peripheral output buffers associated with the controller module.

Figure 5 shows an example of sequential processing of m is sensible elements And, B and C, associated with the controller module or component (for example, the controller module D 6). In this example, the model element 8 is executed at the step S51. At steps S52 and S52' model element distributes its output to the input buffers of the data model elements of C and a respectively. At step S53, the following model element to be executed (in this sample sequence is a model element), reads the current value of the data in its input buffer and performs its function on the basis of this value. At step S54 model element distributes its output to the input buffers of the data model element And buffers the output of the model elements b and C are associated with different buffers input data model element). At step S55 model element And starts using the current values of the input data stored in its buffer input data model element C.

Controller modules, in addition, is configured to distribute, after completing all associated model elements, data values of all their I / o buffers output data on relevant related peripheral buffers input data other controller modules. Controller modules konfigurera the Ana to operate as an independent process without any pre-defined mutual synchronization with other controller modules. Each controller module has assigned individual processing interval; however, no pre-planned time for processing. Rather, controller modules configured to operate independently of each other; that is, each controller module is configured to function as distinct from the other thread. Therefore, we implemented an asynchronous exchange of data between related components of the system. In particular, it provides asynchronous data transmission between the control elements associated with the model controller module, and input/output associated with the bus controller module or the network controller module.

Figure 6 shows an example of parallel processing controller for modules D and E, as well as asynchronous data transmission between controller modules D and E. On the steps S61 and S62 controller modules C and D operate in parallel in separate threads. After completion of step S61 controller module D output is propagated to step S63 from the peripheral buffers the output controller module D associated peripheral buffers input controller module E. However, since the controller module E in the beginning of stage S62 already gave input from their peripheralisation input data to its corresponding model elements, the current input data provided by the model controller D at step S63, will not be considered until the next processing interval for the controller module at step S66. Only after that in the early stage S66, at step S66', controller module E will perform the reading of data from the buffers of the input data as the current input data. Accordingly, the controller module D will not take into account the output common at step S65, at the end of stage S62 of the peripheral buffers the output controller module E on related peripheral buffers the input data controller D-module, since the controller module D already circulated internally input from their peripheral buffers the input data to its corresponding model elements in the early stage S64. Then in early stage S68, step S68' controller module D will read the data from its buffer the input data as the current input data. Accordingly, the output of which is distributed on the steps S67 and S69, will not be distributed controller module E during the execution of step S66 or controller module D during the execution of step S68, respectively. Specialists in the art it is obvious that alternative distribution strategies, call the Commissioner to distribute the input data to the model elements, the execution of which has not started yet in the current processing interval controller module.

Bus controller module is also configured to establish a mapping of the associated input/output devices 4 on the bus 3 sensors/actuators, and control and processing in relation to the bus interface 30 and transfer data via the bus 3 sensors/actuators.

Network controller module is also configured to establish a mapping of the associated input/output, for example, the element of the actuator device connected to the communication network 2, for example, the actuator 10', as well as for management and treatment in relation to the network interface 20 and data transmission through the communication network 2.

The loader 102 model configured to download description 15 the model via the communication network 2 and installing it in the actuator 10. Description 15 model defines a markup language such as XML, HVAC control application or part of the HVAC control application to control the HVAC system 1.

Table 2 shows an example of a model description language XML related to the control application with the heating-up curve, shown in figure 4. The controller application with the heating-up curve includes an element a control the population by the timer, item a of the ambient temperature sensor, the control element 401b with the curve of the heating element s PID controller, the element 402b of the flow temperature sensor and the element s actuator valve.

Figure 4 shows a graphical representation 400 of example 105 model. As shown in figure 4, the description of the model contains one or more model controller module 401, a bus controller module 402 and an optional network controller module 403. These controller modules associated with (i.e. include various interconnected model elements 4011, 4021. Typically, the model controller module 401 includes control elements, while the bus controller module 402 and a network controller module 403 includes elements of input/output. Depending on the specific application, description 15 model and/or controller modules can also refer to model elements with enclosure containing more than one linked, that is, having a view of other model element.

Description 15 model not only has links to different model elements 4011, 4021 (or model elements with nested), but also includes values of parameters associated with the respective model elements, as well as bind information that specifies swapimage model elements. The relationship between model elements 4011 assigns a buffer "on" output of the model element a, 401b, s providing output data to the input buffer "i" model element 401b, s using the data. For example, figure 4 buffer "on" output of the model element a, such as a control timer is tied to the clipboard "i" input data model element 401b, for example control the heating-up curve; and a buffer "on" output of the model element 401b is bound to the buffer i input data model element is, for example item PID-controller.

As can be seen from figure 4, the model elements associated with the different controller modules, have no direct relation, that is, the buffer is "on" the output of a model element is not directly associated with the buffer i input data model element in another controller module. Relationships between model elements in different controller modules, are defined through the peripheral buffers input/output data associated with the respective controller modules. For example, figure 4 output buffers "on" model elements a, for example element of the sensor outside temperature and 402b, for example element of the flow temperature sensor, connected respectively with the input b is Fermi "i" model element 401b (heating curve) or the model element s (PID controller) through the corresponding peripheral buffer output "OO" bus controller module 402 and the corresponding peripheral buffer ii input data model controller module 401. Accordingly, figure 4 buffer "on" output of the model element is associated with the buffer i input data model element is, for example, the actuator of the valve, through the corresponding peripheral buffer "PA" output model controller module 401 and the corresponding peripheral buffer ii input data bus controller module 402.

In figure 4 the reference position 4031 refers to a model element network controller module 403, where the model element 4031 is optional actuator, which is available to the Executive mechanism 10 via the communication network 2. Accordingly, figure 4 shows an optional link from buffer "on" output of the model element s (PID controller) to the clipboard "i" input data model element 4031 through the corresponding peripheral buffer "PA" output model controller module 401 to the corresponding peripheral buffer ii input network controller module 403.

The shell 17 of the model is configured to implement a control application HVAC, a specific description of the 15 models, to be executed by the CPU 11. The shell 17 of the model instantiates the model elements based on the element library 16 according to the armed description 15 model using parameters, specific description of the 15 models. Control HVAC application contains at least one model controller module bus controller module and an optional network controller module.

Thus, as shown in figure 2, as soon as the interpreter 17 model implemented control application HVAC actuator 10 will include one or more instantiated model controllers 18, instantiated bus controller 300 and the instantiated network controller 200. Model controller 18 includes various instantiate control elements (and/or model elements with nested)interconnected to implement (control) part of the HVAC control application, for example, in accordance with the model controller module 401, shown in figure 4. The bus controller 300 includes instantiate elements of input/output devices 4 on the bus 3 sensors/actuators, for example, in accordance with the bus controller module 402, shown in figure 4. The network controller 200 contains (but not necessarily) instantiate input/output representing the device in the communication network 2, for example, in accordance with the network controller module 403, shown in figure 5.

The support system 100 is configured to perform processing and routing of trafi the and data between the network controller 200, bus controller 300 and managing HVAC application, as determined by the description of the 15 models and implemented by the interpreter 17 model.

Module 103 parameterization configured to receive from the remote computer 5 via the network 2 link parameters for HVAC control application, a specific description of the 15 models, and to store those parameters in the storage 12 of the data. Module 103 parameterization, in addition, is configured to transmit to the remote computer 5 via the network 2 due to the current values of parameters of the HVAC control application (e.g., for display on a remote computer (5).

The module 104 and control register configured to provide remote computer 5 via the network 2 connection the current values of the data provided and stored by the HVAC system, as well as module 105 alarms and error handling.

Module 19 of the Web server configured to provide Web access, for example, Web browsers running on remote computers 5, to access the loader 102 model, the module 103 parameterization, the module 104 monitoring and recording module 105 alarms and error handling, and possibly to the loader 101 software through the communication network 2.

Thus, using a standard Web browser, the user of the remote computer 5 has vozmozhnosti only monitor graphically represent the current values of the data related to sensors, settings, actuators and/or operating States and error conditions HVAC control application running on one or more actuators 10, 10', but also set in the initial state and dynamically adjust settings for HVAC control application during its execution.

This approach gives the flexibility to adapt the system to specific HVAC, and possibly changing application requirements. If the HVAC system, you must have more than one branch bus 3 sensors/actuators, it will require a decentralized HVAC control application and its efficient distribution of multiple actuators 10, 10'. If the HVAC application is divided into several subsystems for distributed operation across multiple actuators 10, 10', each subsystem is determined by your own description of the model as part of a model. To ensure the efficiency and reliability of submodels preferably be designed as independent, loosely coupled processes. If an HVAC system requires only one bus 3 sensors/actuators, full HVAC control application will be centralized and run on a single actuator, which will be deistvovat is as a single system controller and a master device to device 4, connected to the bus 3 sensors/actuators.

Figure 3 presents the steps and tools involved in the design and creation of descriptions of the 15 models. At the first step S21, the user computer 5, for example, the system engineer uses the 501 model development to build and 150 models of HVAC control application or part of the HVAC control application, as shown, for example, in figure 4. The tool 501 model contains a graphical editor that allows the user to select controller modules, the basic model elements and model elements with nested defined, for example, a markup language such as XML and stored in the library 502 basic elements or library 503 elements with nested respectively. Using the graphical editor of model elements associated with the selected controller module, as shown on the exemplary graphical representation 400. The selected controller modules and model elements are connected to each other by setting in the graphics editor relations (information link) between the controller modules and model elements. The user assigns the selected controller modules individual processing intervals. In addition, we are parameters that are specific modules that Pris is awayda model elements.

At step S22, the model generator tool 501 model development based on the data entered by the user, creates a description 150 models, for example, a markup language such as XML.

At step S23, using the 504 commissioning and deployment model is the task of matching the descriptions 150 models (for example, by the user computer 5) the real hardware configuration bus 3 sensors/actuators, that is, the actuator 10 and specific devices 4 connected to the bus. Depending on the variant embodiment of the invention, the tool 504 commissioning and deployment model supports dynamic discovery and/or manual input of address information. Description 150 model is loaded from the tool 504 commissioning and deployment models in the actuator 10 through the loader 102 model (as shown under the reference position 15 figure 2). The tool 504 commissioning and deployment models, in addition, is configured to download the firmware, model elements for the elemental library 16 and/or view the HTML description of the model in the actuator 10 through the loader 101 software. For each model element model description includes data GUI (graphical user interface is the body), specifies the size and position of a corresponding model element in the graphical representation 400 description 15/150 model HVAC control application. The tool 504 commissioning and deployment models, in addition, is configured to provide the computer user 5 access to the current description 15 model stored in the actuator 10, and, in particular, to give the user the ability to change the description of the 15 model during execution of the application, for example, by adding or removing model elements from the current descriptions of the 15 models.

At step S24 in order to control, parameterisation and/or reverse engineering the user computer 5 uses a Web browser such as Internet Explorer from Microsoft Inc., Mozilla Firefox Mozilla Foundation or Safari Apple Inc., to load and display a graphical representation 400 description 15 model representing the HVAC control application, implemented and running on the actuator 10, including the current values of system States, emergency and warning notifications, settings, system settings, and device settings, and/or data values, such as temperature values or the values of the parameters of air quality.

7 shows a possible sequence of steps of operation of the actuator 10 after download the key and configuration commissioning and deployment model) description 15 model where at step S71 begins execution management application, HVAC, a specific description of the 15 models.

At step S72, the interpreter 17 model implements and creates HVAC control application by instantiating the model elements from the element library 16, identified by model description. Model elements are instantiated with specific items of the parameter values specified respectively in the descriptions of the 15 models and/or module 103 parameterization. In particular, controller modules instantiated to work as independent processes in separate threads in the processor 11. To connect model elements according to a given data link is established Association between the input buffers and output buffers of the data model elements, as well as peripheral input buffers and output buffers controller modules.

At step S73 begins execution management application, HVAC, and triggers the execution of the instantiated model, tire, but not necessarily, network controllers, in the form of parallel processes.

At step S731 to manage their own respective processing intervals Td, Te, each of the instantiated controller sets the timestamp at the initial time Ts single execution (the ScanSnap models) as shown in figure 5, for example, for a single computation controller module D at step S61.

At step S732, each of the instantiated controller distributes the current data value of their peripheral input buffers to the output buffers of the respective associated model elements.

At step S733 each of the instantiated controller starts the sequential processing of their instantiated and connected model elements, that is, each of the controllers performs a one-time calculation for your chart States, resulting in the individual elements are transitions from one state to another, as shown in figure 5 for sequential processing, for example, the model elements B, C and A.

On stage S7331 model element to be processed, reads the current data entered from its associated input buffer (buffers), if necessary.

On stage S7332 corresponding model element computes its output value (s) based on input data, read from the input buffer (buffers), and writes the output to the appropriate output buffer (the buffer).

On stage S7333 corresponding controller module distributes data from the output buffer (buffers) item input buffers related to fashion is lnyh elements and/or peripheral buffers the output. Specialists in the art it is obvious that the feedback regarding the data values on a model element that has already been processed in the current processing interval, more will not be processed for a given model element in the current processing interval, and will only be processed in the next processing interval.

On stage S7334 the controller checks whether all model elements are processed. If you still have the model elements to be processed, then processing continues at step S7331 by starting the processing of the next model element; otherwise, processing continues at step S734. The following model element to be processed is determined, for example, on the basis of the processing sequence stored in the corresponding controller, for example, in the form of a table that identifies instancevalue model elements in sequential order processing.

At step S734 after all the modeling elements of the controller are processed and the corresponding values of the output data transmitted to the peripheral output buffers of the controller corresponding to the controller module D distributes the data values of the peripheral output buffers of the controller to the associated peripheral input buffers other controllers, as shown in the example is as 6 to steps S63, S65, S67 and S69.

At step S735 to control the processing interval Td, Te appropriate controller D sets the timestamp at the time Tc complete a single execution (update models), as shown in figure 5, for example, disposable calculations performed by controller module D at step S61. The actual time Tp processing is determined on the basis of the initial timestamp timestamp Ts and Tc complete.

In step S736, the corresponding controller D waits until the start of the new interval Td processing, or immediately starts a new interval Td of the processing, if the actual time Tp processing exceeds the duration of the interval Td of the controller. For the new interval Td, the processing proceeds to step S731 by performing other one-time calculation instantiated and connected model elements of the controller.

Module 105 error handling provides centralized error handling, and it is configured to provide event handling errors and management failure scenarios for all parts of the application HVAC. Module 105 error handling is implemented as a separate layer, separated from the control logic. Error scenarios describe the conditions (the conditions) of the error and the corresponding system response. As schematically shown in Fig, script 1050 error is determined by one or the multiple filters 1051 error and appropriate action 1052 errors. Filter 1051 error defines the criteria for events 82, 83 errors, such as the severity of one or more associated actions 1052, subject to implementation errors. Errors can occur and be detected in the various components of the system. For example, if the temperature sensor does not provide a temperature value, this error condition may be detected by system components at a higher level. Alternatively, this sensor may have built-in functionality to poll its working condition. In addition, the system engineer can specify the exact condition as error conditions, for example, when the value provided by the sensor, does not fit within the specified range. Thus, the mechanisms startup errors can be implemented at different hierarchical levels in the different system components.

For example, on Fig element 4020 I/o bus controller module 402 includes a module 4021 run error, which is configured to detect error conditions in the element 4020 I/o. After the error state is detected in step S82 module 4021 run error creates an event 82 errors and indicates it to the module 105 error handling. Accordingly, the element 4030 input/output network controller module 403 contains the module 4031 confuse the ka errors which is configured to detect error conditions in the element 4030 input/output and run the event 83 errors on step S83.

Module 105 error handling uses their filters 1051 errors to identify any actions 1052, wish to execute in response to an event 82, 83 errors. Accordingly, at step S81 module 105 error handling, triggers one or more actions 1052. For example, at step S84, the corresponding error is written to the log 84 errors.

At step S85 module 105 error handling starts the module 4012 fixing errors in the model controller module 401. Module 4012 fixing bugs configured for the installation of buffer "on" the output to a specific value, for example the unit when it starts module 105 error handling. In this way the alarm about the error is available for any model (Manager) element 4013, which has a buffer of "i" input data associated with the module 4012 commit errors. For example, the model element 4013 is a multimode model element configured to work in different modes depending on the state selected for the appropriate model element during its execution. Thus, due to the connection between the buffer "on" output module 4012 fixing errors and buffer "i" input mnogorazemny what about the model element 4013, model element 4013 is in normal mode or in the mode of the error depending on the error conditions found in the item 4020, 4030 input/output and controlled by module 105 error handling. In each state of the multi-mode model element this element is present in the form of different combinations of model elements model elements with containment and connections between them. At any given point in time for multimode model element can be activated only one state, that is, a single mode. State mode or multimode model element is selected by setting the input values. The current state or mode multimode model element is indicated by the corresponding output value.

At step S86, the module 105 error handling starts the module 86 of electronic messaging. Module 86 of electronic messaging configured to generate and transmit via the network 2 link email messages to one or more specified addresses. Depending on the variant of the invention, this electronic message may be an e-mail message, an SMS message (message transfer service short message or other message containing the data.

The proposed actuator 10, 10' provide the t platform for the implementation of decentralized and distributed control for HVAC systems. The HVAC application can be dynamically changed by downloading new model specifications. Components of the HVAC system, in particular actuators 10, 10' and controller modules, weakly related to each other and provided with connections for asynchronous data transfer. Since applications HVAC work in an environment to which changes occur gradually, the system performance may be relatively low. Therefore, there is no real need to enforce temporal dependencies for component management application that communicate.

It should be noted that in this description of computer program code containing commands to control the processor Java, associated with specific functional modules and the sequence of steps presented in a specific order; however, specialists in the art it is obvious that the structure of this computer program code may be different and that you can change the order of at least some of the stages, without going beyond the scope of the present invention.

1. The actuator (10) for systems (1) heating, ventilation and air conditioning (HVAC), and actuator (10) includes a network interface (20) for connecting the actuator (1) to the network (2) communication bus interface (30) for larger connecting apertures is inane actuator (10) to the bus (3) sensors/actuators, store (12) and data processing unit (11)connected to the storage (12) data; however, the Executive mechanism (10) further comprises:
loader (102)configured to receive over the network (2) communication and to remember the data warehouse description (15) the model that defines the controller application HVAC;
element library (16), which includes a set of stored model elements (4011, 4021)that contains the commands to control the processor (11), and controller modules (401, 402, 403)configured in each case to control sequential order of execution for associated model elements (4011, 4021)referenced by the respective controller module (401, 402, 403), distribute external input to its associated model elements (4011, 4021) prior to the execution of the model element defined first in this sequential order, and distribute the output of its associated model elements (4011, 4021) outside the respective controller module (401, 402, 403) upon completion of the execution of the model element defined in the last mentioned sequential order; and the interpreter (17) model, configured to implement on the basis of the description (15) model control application for execution on a processor (11) by instantiating controllers the modules (D, E) and associated model elements (A, B, C), referenced in the description (15) model, assigning at least one instantiated model element device (4)connected to the bus (3) sensors/actuators, and instantiating controller modules (D, E) in each case in the form different from the other thread, so between instancevalue controller modules (D, E) is asynchronous communication.

2. The actuator (10) according to claim 1, in which model elements (4011, 4021) in each case configured to read input data from one or more specific buffers (i) the input data associated with the respective model element, and write output data to one or more specific buffers (o) output data associated with the respective model element; the interpreter (17) the model is additionally configured to associate on the basis of the information of the link included in the description (15) model, the output buffers are instantiated model elements (A, B, C) with input buffers instantiated model elements (A, B, C); and controller modules (401, 402, 403) in each case configured to distribute upon completion of model elements (4011, 4021)referenced by the respective controller is hydrated module, data values from the output buffer (o) of the model element on the associated input buffer (i) a model element referenced by the respective controller module.

3. The actuator (10) according to claim 1 or 2, in which the description of (15) the model includes the identifiers of model elements (4011, 4021) and the parameter values applied in each case to the corresponding model element; the interpreter (17) the model is configured to instantiate in each case the model element from the element library (16) on the basis of the identifier and parameter values; and a controller modules configured to run in the individual processing intervals assigned in each case to the respective controller module.

4. The actuator (10) according to claim 1 or 2, in which the description of (15) the model includes data of a graphical user interface associated with model elements (4011, 4021), referenced in the description (15) models, and data of the graphical user interface includes at least position information for positioning on the display a graphical representation (400) of the corresponding model element.

5. The actuator (10) according to claim 1 or 2, in which at least some of the stored model elements konfigurera the s to work in different modes, moreover, these modes can be selected through the configuration at runtime state associated with the instantiation of a corresponding model element.

6. The actuator (10) according to claim 1 or 2, additionally containing the server module (19)configured to transmit to the Web browser graphical representation (400) of the control application across the network (2) communication on the basis of the description (15) model to pass to the Web browser for display in a graphical representation (400) input/output, associated in each case with a model element referenced in the description (15) models to accept from a Web browser parameter values associated in each case with a modeling element that there is a link in the description (15) models, and to remember the actuator (10) the parameter values allocated for the instantiation of a corresponding model element (A, B, C).

7. The actuator (10) according to claim 1 or 2, wherein the stored model elements (4011, 4021) include elements representing at least one of the following: controller, PID controller, on-off controller, limiter, timer, Boolean logic module, the control module time periods, the curve module heating module filter module calculate the floating medium, the trigger module, fashion the b input of the selector, module constant value, the comparator module mathematical operations, module status, module fixing errors and launcher error.

8. The actuator (10) according to claim 1 or 2, in which the network interface (20) is configured for communication according to the Internet Protocol network Ethernet communication; bus (3) sensors/actuators includes one of the tyres MP-Bus or BACnet bus; description (15) model is specified in the markup language; the stored model elements (4011, 4021) is defined in the byte code of the Java processor (11) is a Java processor configured to execute the byte code of Java; and the loader (102) is additionally configured for storage in enforcement mechanism (10) at least one version of the description (15) model in HTML.

9. The method of operation of the actuator (10) of system (1) heating, ventilation and air conditioning (HVAC)system, comprising stages, which are:
remember the actuator (10) description (15) the model that defines the controller application HVAC;
remember the actuator (10) element library (16), which includes many of the model elements (4011, 4021) and controller modules (401, 402, 403), contains the commands to control the processor (11) of the actuator (10); implement the actuator (1) on the basis of the description (15) model control application for execution in the processor (11) by instantiation of the element library (16) controller modules (D, E) and associated model elements (A, B, C), referenced in the description (15) model, assigning at least one instantiated model element (a, b, C) device (4)connected to the bus (3) sensors/actuators, and instantiating controller modules (D, E) in each case in the form different from the other thread; and performing a control application by means of respective controller modules (D, E), governors in each case, the sequential order of execution for associated model elements (A, B, C)referenced by the respective controller module (D, E), distribute external input to its associated model elements (A, B, C) prior to execution of the model element defined first in this sequential order, and distribute the output of its associated model elements (A, B, C) outside the respective controller module (D, E) upon completion of the execution of the model element defined in the last mentioned sequential order, so that between instancevalue controller modules (D E) is asynchronous communication.

10. The method according to claim 9, in which model elements (A, B, C) read input data from one or more specific input buffers Yes the data associated with the respective model element (A, B, C), and write output data to one or more specific output buffers associated with the respective model element (A, B, C); and output buffers of the model elements (A, B, C) associated with the input buffers of the model elements (A, B, C) based on the information link included in the description (15) model; and upon completion of the model elements (A, B, C)referenced by the respective controller module (D, E), the data values are distributed in each case from the output buffer of the model element on the associated input buffer model element (A, B, C)referenced by the respective controller module (D, E).

11. The method according to claim 9 or 10, in which model elements (A, B, C) instantiated from the element library (16) in each case on the basis of the identifier and the corresponding values of the parameters included in the description (15) model; and instancevalue controller modules are executed in the individual processing intervals allocated in each case to the respective controller module.

12. The method according to claim 9 or 10, in which the description of (15) the model includes data of a graphical user interface associated with model elements (4011, 4021), referenced in the description (15) model and a graphical representation (400) of the corresponding model element is positioned on the display based on the position information, included in the graphical user interface.

13. The method according to claim 9 or 10, in which at runtime is selected, the status associated with the instantiation of a model element (A, B, C), and this condition sets the corresponding model element (A, B, C) to work in one of at least two different modes.

14. The method according to claim 9 or 10, in which on the basis of the description (15) model graphical representation (400) control application is transmitted from the actuator (10) through a network (2) communication to the Web browser; the values of the input/output data, associated in each case with model elements (4011, 4021), referenced in the description (15) model is transmitted from the actuator (10) to the Web browser for display in a graphical representation (400); the values of parameters associated with the model element (4011, 4921), referenced in the description (15) model, accepted to the actuator (10) from a Web browser; and parameter values are stored in the actuator (10)for an instantiation of a corresponding model element (A, B, C).

15. Machine-readable media on which is stored a means of computer software code for controlling a processor (11) of the actuator (10) of system (1) heating blower adjust the tion and air conditioning (HVAC), so that the actuator (10):
takes through the network (2) communication description (15) the model that defines the controller application HVAC;
remembers description (15) model repository (12) data of the actuator (10);
implements on the basis of the description (15) model control application for execution in the processor (11) of the actuator (10) by instantiation of the element library (16) controller modules (D, E) and associated model elements (A, B, C), referenced in the description (15) model, assigning at least one instantiated model element (A, B, C) device (4)connected to the bus (3) sensors/actuators, and instantiating controller modules (D E) in each case in the form different from the other thread of execution; and
performs a control application by controlling the sequential order of execution for associated model elements (A, B, C)referenced by the respective controller module (D, E), distribution of external data entered for the respective controller module (D, E), its associated model elements (A, B, C) prior to execution of the model element defined first in this sequential order, and dissemination of data, the output of the associated model elements (A,B, C)outside the respective controller module (D, E) upon completion of the execution of the model element defined in the last mentioned sequential order, so that between instancevalue controller modules (D, E) is asynchronous communication.