A METHOD OF COMMISSIONING PHYSICAL HVAC DEVICES OF AN HVAC SYSTEM FOR AN HVAC APPLICATION

Abstract

A method of commissioning physical HVAC devices for an HVAC application including communicatively connecting physical HVAC devices to a communication bus, one physical HVAC device being selected as master HVAC device, identifying the physical HVAC devices connected to the communication bus, determining device type(s) of the physical HVAC devices, receiving an application model including a device list listing virtual HVAC devices of the HVAC application, generating, by the master HVAC device, a mapping of the physical HVAC devices to the virtual HVAC devices using the device type(s) of the physical HVAC devices and of the virtual HVAC devices.

Description

FIELD OF THE INVENTION

The present invention relates to a method of commissioning physical HVAC devices of an HVAC system for an HVAC application. The present invention further relates to a master HVAC device for commissioning physical HVAC devices of an HVAC system for an HVAC application. The present invention even further relates to an HVAC system and a computer program product comprising instructions to be executed by a processor of an HVAC device for commissioning physical HVAC devices of an HVAC system for an HVAC application.

BACKGROUND OF THE INVENTION

In the field of Heating, Ventilating and Air Conditioning, HVAC systems typically comprise a fluid transportation system and a plurality of HVAC devices, including motorized HVAC devices, such as actuators, valves, dampers, pumps, and fans, and other devices connected to the HVAC system, such as flow sensors, pressure sensors, temperature sensors, rotation sensors, position sensors, humidity sensors, etc. In the field of HVAC, the electric motor is coupled, through gears and/or other mechanical coupling, to an actuated part, such as a valve or damper for controlling the flow of a fluid such as water or air. In addition to an electric motor, motorized HVAC devices or HVAC actuators, respectively, are typically provided with a controller having a processing unit and a data store for storing data content comprising configuration data for operating the HVAC device, and for operation-related data recorded by the HVAC device. The configuration data includes configuration parameters such as motor speed, closing time, opening time, etc. The operation-related data includes values such as number of cycles, number of movements, maximum travel angle, minimum travel angle, etc. In HVAC applications, the controller is connected to sensors, such as flow sensors, pressure sensors, temperature sensors, humidity sensors, air quality sensors, rotation sensors, position sensors, etc., and the configuration data further includes configuration parameters such as a target value of flow rate, a set value of altitude for adjusting the measurement of a flow sensor, etc. Moreover, a section of the data store further has stored therein program code for controlling the processing unit. In HVAC applications, the program code includes various control algorithms such as for controlling the motor to open and close an orifice of the valve or damper to regulate the flow of fluid, e.g. with regards to differential pressure, room temperature, flow of energy, etc.

HVAC systems comprising a plurality of HVAC devices are deployed for a purpose, i.e. in order to fulfill a specific functionality/set of functionalities. The purpose of an HVAC system, comprising a set of HVAC functionalities, is defined by what shall be hereafter referred to as an HVAC application. An HVAC application may comprise functionalities related to heating, ventilation, cooling and/or monitoring of an environment using a plurality of HVAC devices such as actuators or sensors.

The set-up, or commissioning of an HVAC system, in particular of an HVAC system comprising a multitude of HVAC devices is time and hence cost intensive.

SUMMARY OF THE INVENTION

It is an object of embodiments disclosed herein to provide an improved method of commissioning physical HVAC devices of an HVAC system for an HVAC application.

According to the present invention, an application model is defined for an HVAC application, the application model comprising a list of devices required to implement the respective HVAC application. The HVAC devices as listed in the HVAC application are referred to as virtual HVAC devices. The application model also comprises data indicative of the device type of each virtual HVAC device. The device type defines the minimum capabilities a physical HVAC device needs to possess in order to fulfill the required functions for the HVAC application. For example, an HVAC application for heating a space comprises a device list of virtual HVAC devices listing: a first virtual HVAC device of the device type “valve actuator” for closing an opening a fluid transportation line to/from a heat exchanger; and a second virtual HVAC device of the device type “temperature sensor” for measuring the temperature of the fluid return flow from the heat exchanger.

Addressing the objective of providing an improved method of commissioning of physical HVAC devices for an HVAC application, it has been recognized that it is a particularly time consuming activity to identify the correct/compatible physical HVAC device corresponding to each virtual HVAC device of the HVAC application, as defined by the HVAC application model.

According to the present disclosure, this object is achieved by the features of the independent claim 1. In addition, further advantageous embodiments follow from the dependent claims and the description.

In particular, this object is achieved by a method of commissioning physical HVAC devices of an HVAC system for an HVAC application. In a preparatory step of the method, a plurality of physical HVAC devices of the HVAC system are communicatively inter-connected by a communication bus via each physical HVAC device's bus communication interface. One of the plurality of physical HVAC devices is selected as master HVAC device. The selection of one of the plurality of physical HVAC devices as master HVAC device may be an automatic selection of a first physical HVAC device comprising a processing unit powerful enough and configured for the carrying out the methods steps of commissioning physical HVAC devices. Alternatively, or additionally, one of the plurality of physical HVAC devices is selected as master HVAC device by a configuration, either by input received by the respective physical HVAC device or configuration pre-recorded into a data store of the master HVAC device.

After a physical HVAC device has been selected as master HVAC device, the master HVAC device identifies each of the physical HVAC devices connected to the communication bus by retrieving respective identification data of the physical HVAC devices. According to embodiments of the present disclosure, the identification data may be a mere ID number of the physical HVAC device. Alternatively, or additionally, the identification data may further comprise data descriptive of the device type and/or functionalities supported by the respective physical HVAC device.

Once the physical HVAC devices connected to the communication bus have been identified, the master HVAC device determines the device type(s) of the physical HVAC devices using the respective identification data. According to embodiments of the present disclosure, the master HVAC device determines the device type(s) of the physical HVAC devices by way of a database query, stored either locally in the master HVAC device or on a remote computer communicatively connected to the master HVAC device.

In a further step, subsequent, preceding or parallel to the previously described steps (connecting, identifying and determining the type of the HVAC devices), the master HVAC device receives an application model of an HVAC application.

According to embodiments disclosed herein, the master HVAC device receives an application model of an HVAC application corresponding to a selection of an HVAC application amongst a list of available HVAC applications. The list of available HVAC applications comprises HVAC applications stored locally in the master HVAC device and/or stored on a remote computer communicatively connected to the master HVAC device via a remote communication interface. Depending on whether the available HVAC applications are stored locally or remotely, the master HVAC device retrieves the application model corresponding to the selected HVAC application from a data storage of the master HVAC device and/or from a remote computer communicatively connected to the master HVAC device via a remote communication interface.

The HVAC application resides and/or is executed by the master HVAC device and/or a remote computer communicatively connected to the master HVAC device via a remote communication interface. The HVAC application comprises computer readable instructions for generating control data for controlling the physical HVAC devices, in particular to actuators. Alternatively, or additionally, the HVAC application comprises computer readable instructions for generating control data for processing operational data received from the physical HVAC devices, in particular from sensors.

The application model comprises at least a device list listing a plurality of virtual HVAC devices of an HVAC application. The virtual HVAC devices are indicative of the physical HVAC devices that are needed to implement the HVAC application. In any case, the virtual HVAC devices comprising at least data indicative of a device type of each virtual HVAC device, i.e. the type of physical HVAC device needed to implement the HVAC application.

According to further embodiments disclosed herein, the application model further comprises data indicative of the interaction between the virtual HVAC devices, such as direction of data communication there-between.

Once the physical HVAC devices have been identified, their device types determined and the application model has been received, the master HVAC device generates a mapping of one or more of the plurality of physical HVAC devices to one or more of the plurality of virtual HVAC devices of an HVAC application. The mapping is generated using the respective determined device type(s) of the plurality of physical HVAC devices and the device type(s) of the virtual HVAC devices. According to embodiments disclosed herein, the mapping is based on identical device types of physical HVAC devices and the device type(s) of the virtual HVAC devices. Alternatively, the mapping is based on the device type of physical HVAC devices being compatible with the device type(s) of the virtual HVAC devices. According to a particular embodiment, the device type of the virtual HVAC device defines a set of capabilities that a physical HVAC device must possess. Correspondingly, a physical HVAC device is compatible with such a device type if it possesses at least the capabilities defined by the device type, irrespective whether the physical HVAC device possesses additional capabilities. According to further embodiments disclosed herein, one or more parameters are associated with each capability listed in the device type of the virtual HVAC devices. Correspondingly, a physical HVAC device is compatible with such a device type if it possesses at least the capabilities defined by the device type and satisfies the parameter of the respective capability. Continuing with the example above of an HVAC application for heating a space, the device list of the application model lists a device type “valve actuator” as a virtual HVAC device. The “valve actuator” device type of the virtual HVAC device is associated with a parameter “Torque>5 Nm”. In this example, a physical HVAC device of the HVAC system is compatible with the virtual HVAC device if it is of device type “valve actuator” and is capable of applying a torque of 5 Nm or higher.

In other words, the mapping comprises an association of physical HVAC devices of the HVAC system to virtual HVAC devices of the HVAC application based on the compatibility of their device types.

According to embodiments of the present disclosure, generating the mapping of physical HVAC device(s) to virtual HVAC device(s) comprises one or more of:

• • Automatically mapping each singular physical HVAC device of a device type to a singular virtual HVAC device. In this context, “singular . . . of a device type” refers to a physical HVAC device of a particular device type from which no other HVAC device has been identified in the HVAC system. In other words, the physical HVAC device is unique (singular) amongst the identified physical HVAC devices of the HVAC system. In this context, “singular . . . of a device type” further refers to a virtual HVAC device of a particular device type from which no other HVAC device is listed on the device list of the HVAC application. In other words, the virtual HVAC device is unique (singular) amongst the virtual HVAC devices of the HVAC application.
  • Providing a selection list of a plurality of physical HVAC devices having compatible device type(s) with the device type(s) of the virtual HVAC devices of the HVAC application and receiving user input indicative of a selection of one or more physical HVAC devices from the selection list to be mapped. In particular, if more than one compatible physical HVAC devices have been identified for a particular virtual HVAC device, a selection of all compatible physical HVAC devices is provided. The mapping is then performed according to a user selection of the physical HVAC device amongst the more than one compatible physical HVAC devices. According to embodiments of the present disclosure where mapping involves user input, the method further comprises the step of generating a warning if a physical HVAC device has been mapped to more than one virtual HVAC device and/or if a selected physical HVAC device type is not compatible with the device type of the mapped virtual HVAC device.

In an embodiment, before, during or after the mapping, the master HVAC device retrieves the device profile(s) corresponding to the determined device type(s). Alternatively, or additionally, the device profile(s) are retrieved corresponding to the identification data of the physical HVAC devices. The device profiles comprise a set of computer executable instructions, which—when executed—enable data communication with the physical HVAC device and enable processing/interpretation of data communication therefrom. In other words, the device profiles comprise a device driver and—deepening on the embodiment—also device-specific configuration/calibration data.

Device profile(s) corresponding to a device type(s) are referred to as generic device profile(s), while device profile(s) specific to the particular identification data are referred to as device-specific profile(s).

In an embodiment, once the device profile(s) have been retrieved, data communication between the HVAC application and the plurality of physical HVAC devices is enabled by the master HVAC device. Enabling data communication between the HVAC application and the plurality of physical HVAC devices comprising directing data communication from the HVAC application to the appropriate physical HVAC device and attributing data communication from the physical HVAC device to the appropriate virtual HVAC device based on the mapping. According to embodiments of the present disclosure, before data communication between the HVAC application and the plurality of physical HVAC devices is enabled, as a safety measure, manual user interaction is required, such as the entry of a password.

The method of commissioning physical HVAC devices according to the present invention is advantageous as it allows an efficient way to identify compatible physical HVAC devices for the virtual HVAC devices of an HVAC application, greatly reducing or even eliminating the risks of erroneous mapping. Furthermore, retrieval and application of the device profiles ensures that, after correct mapping of the compatible physical HVAC devices to the virtual HVAC devices, the communication between the HVAC application and the physical HVAC devices is carried out according to the exact specifics of each physical HVAC device.

According to embodiments of the present disclosure, the device profile(s) comprise device-specific processing data corresponding to the physical HVAC devices identified by the identification data. Enabling data communication between the HVAC application and the plurality of physical HVAC devices comprises processing, by the master HVAC device, operational data received from the physical HVAC devices, in particular from sensors, using the device-specific processing data and forwarding the thereby processed operational data to the HVAC application. Alternatively, or additionally, enabling data communication between the HVAC application and the plurality of physical HVAC devices comprises processing, by the master HVAC device, control data generated by the HVAC application using the device-specific processing data and forwarding the thereby processed control data to the respective physical HVAC devices.

The device-specific processing data comprises—according to embodiments of the present disclosure, calibration data specific to the physical HVAC devices identified by the identification data, wherein the processing by the HVAC gateway device comprises applying the calibration data to operational data received from the physical HVAC devices and/or applying the calibration data to control data generated by the HVAC application.

Alternatively, or additionally, the device-specific processing data comprises conversion data including conversion parameters and/or conversion formulae, wherein the processing by the master HVAC device, comprises applying the conversion parameters and/or conversion formulae to operational data received from the physical HVAC devices.

Depending on the connected physical HVAC devices, the operational data comprises status data of the respective physical HVAC devices and/or sensor values measured by one or more sensor(s) of the respective physical HVAC devices. Alternatively, or additionally, the control data comprises actuator values, the method further comprising: actuating, by actuator(s) of the respective physical HVAC devices, of one or more mechanically connected actuated parts, e.g. flow regulating valves, in accordance with the actuator values as processed and forwarded by the master HVAC device.

According to further embodiments disclosed herein, the method of commissioning further comprises testing the HVAC application using the mapping of the plurality of physical HVAC devices to the plurality of virtual HVAC devices of the HVAC application. The testing comprises running a testing routine by the master HVAC device verifying the data communication between the HVAC application and the physical HVAC devices, including testing directing data communication from the HVAC application to the appropriate physical HVAC device and/or testing the attribution of data communication from the physical HVAC device to the appropriate virtual HVAC device. Furthermore, according to embodiments, testing comprises testing the functionality of the individual physical HVAC devices using operational data received from the physical HVAC devices and/or control data generated by the master HVAC device addressed to the individual physical HVAC devices. For example, the control data may cause the physical HVAC device to be move an actuated part into a defined setpoint position, whereas testing the physical HVAC device(s) comprises verifying whether the actuated position as reported (based on operational data received from the physical HVAC device) matches the setpoint position. Testing of individual physical HVAC devices by means of control data generated by the master HVAC device is particularly advantageous as it allows testing the HVAC system, respectively its constituent physical HVAC devices without the need for a remote computer, such as a Building Management System BMS being connected to the HVAC system.

It is an object of further embodiments of the present disclosure to provide an improved method of replacement of a physical HVAC device to be replaced—either due to a malfunction or due to an upgrade thereof. This further object is achieved by an assisted device replacement, wherein the master HVAC device identifies a physical HVAC device C1 to be replaced and a replacement physical HVAC device. Identification of a physical HVAC device to be replaced may be performed automatically by the master HVAC device by detecting a malfunctioning physical HVAC device and/or by detecting a physical HVAC device being disconnected from the communication bus. Alternatively, or additionally, identification of a physical HVAC device to be replaced may be performed by the master HVAC device by receiving user input indicative of a physical HVAC device to be replaced.

Identification of a replacement physical HVAC device C2 may be performed automatically by the master HVAC device by detecting a physical HVAC device being connected to the communication bus, the newly connected physical HVAC device having a device type compatible with the device type of the physical HVAC device to be replaced. Alternatively, or additionally, identification of a replacement physical HVAC device may be performed by the master HVAC device by receiving user input indicative of a replacement physical HVAC device.

After having identified both a physical HVAC device to be replaced and a replacement physical HVAC device, the master HVAC device updates the mapping of the physical HVAC device to be replaced with the replacement physical HVAC device. Hence, the replacement physical HVAC device takes over seamlessly the place of physical HVAC device to be replaced, the HVAC application being able to continue operation with the virtual HVAC device (to which the replacement HVAC device is now mapped).

According to particular embodiments of the assisted device replacement, operational data is retrieved from the physical HVAC device to be replaced and the retrieved operational data is then transmitted with the replacement physical HVAC device. Alternatively, or additionally, parameters of the device profile of the replacement physical HVAC device are updated using parameters of the device profile of the physical HVAC device to be replaced, which have been previously stored by the master HVAC device.

It is a further object of embodiments disclosed herein to provide an improved master HVAC device for commissioning physical HVAC devices of an HVAC system for an HVAC application. According to the present disclosure, this object is achieved by the features of the independent claim 14. In addition, further advantageous embodiments follow from the dependent claims and the description. In particular, this object is achieved by a master HVAC device comprising

• • a bus communication interface for communicatively connecting one or more further physical HVAC device(s); a processor; wherein the processor is configured to control the master HVAC device to carry out the method according to one of the embodiments disclosed above and hereinafter.

It is a further object of embodiments disclosed herein to provide an HVAC system enabling improved commissioning of its physical HVAC devices for an HVAC application. According to the present disclosure, this object is achieved by the features of the independent claim 16. In addition, further advantageous embodiments follow from the dependent claims and the description. In particular, this object is achieved by an HVAC system comprising a master HVAC device, one or more physical HVAC devices comprising one or more actuator(s) for actuating mechanically connected actuated part(s) and/or one or more sensor(s), wherein the master HVAC device and the one or more physical HVAC devices are communicatively connected by a communication bus via respective bus communication interfaces. The sensor is configured to measure a parameter of the HVAC system, in particular an environmental parameter, such as a temperature, humidity, particulate matter (PM) and/or CO2 level of an environment controlled by the HVAC system. Alternatively, or additionally, the sensor is provided to measure operational parameters of various components of the HVAC system such as an actuated position of actuated part(s) and/or the operational state of the HVAC device and/or other parameters of the HVAC system, such as a flow rate or differential pressure at locations of a liquid through a fluid transportation system.

It is a further object of embodiments disclosed herein to provide a computer program product, which—when executed by a processor of an HVAC device of an HVAC system—enable improved commissioning of its physical HVAC devices for an HVAC application. According to the present disclosure, this object is achieved by the features of the independent claim 17. In addition, further advantageous embodiments follow from the dependent claims and the description. In particular, this object is achieved by a computer program product comprising instructions, which when executed by a processor of a master HVAC device, cause the master HVAC device to carry out the method according to one of the embodiments disclosed above and hereinafter.

BRIEF DESCRIPTION OF THE DRAWINGS

The herein described disclosure will be more fully understood from the detailed description given herein below and the accompanying drawings which should not be considered limiting to the disclosure described in the appended claims. The drawings which show:

FIG. 1: a highly schematic block diagram of an HVAC system according to an embodiment of the present disclosure;

FIG. 2: a flowchart illustrating a method of commissioning physical HVAC devices of an HVAC system for an HVAC application according to an embodiment of the present disclosure;

FIG. 3: a flowchart illustrating a method of commissioning physical HVAC devices of an HVAC system for an HVAC application according to an embodiment of the present disclosure, illustrating substeps of generating a mapping of physical HVAC devices to virtual HVAC devices;

FIG. 4: a flowchart illustrating a method of commissioning physical HVAC devices of an HVAC system for an HVAC application according to an embodiment of the present disclosure, illustrating substeps of enabling communication HVAC application and physical HVAC devices using device profiles;

FIG. 5: a flowchart illustrating a method of commissioning physical HVAC devices of an HVAC system for an HVAC application according to an embodiment of the present disclosure, illustrating the step of assisted replacement of a physical HVAC device;

FIG. 6A: a pseudo-screenshot of a user interface according to an embodiment of the present disclosure, comprising display elements for displaying a list of available HVAC applications and user interaction elements for receiving a selection of a HVAC application amongst the list of available HVAC applications;

FIG. 6B: a pseudo-screenshot of a user interface according to an embodiment of the present disclosure, comprising display elements for displaying a device list listing a plurality of virtual HVAC devices;

FIG. 6C: a pseudo-screenshot of a user interface according to an embodiment of the present disclosure, further comprising user interaction elements for altering one or more parameters of the device types of the virtual HVAC devices of the selected HVAC application;

FIG. 6D: a pseudo-screenshot of a user interface according to an embodiment of the present disclosure, further comprising user interaction elements for triggering identification of the physical HVAC devices connected to the communication bus;

FIG. 6E: a pseudo-screenshot of a user interface according to an embodiment of the present disclosure, further comprising display elements for displaying progress of identifying the physical HVAC devices;

FIG. 6F: a pseudo-screenshot of a user interface according to an embodiment of the present disclosure, further comprising display elements for displaying list of physical HVAC devices connected to the communication bus and user interaction elements for triggering the mapping of the plurality of physical HVAC devices to the plurality of virtual HVAC devices of the HVAC application;

FIG. 6G: a pseudo-screenshot of a user interface according to an embodiment of the present disclosure, further comprising display elements for displaying a visual representation of the mapping of the plurality of physical HVAC devices to the plurality of virtual HVAC devices of the HVAC application;

FIG. 6H: a pseudo-screenshot of a user interface according to an embodiment of the present disclosure, further comprising user interaction elements for triggering application of the device profiles to enable data communication between the HVAC application and the plurality of physical HVAC devices;

FIG. 6I: a pseudo-screenshot of a user interface according to an embodiment of the present disclosure, further comprising display elements for displaying a visual representation of the commissioned HVAC application;

FIG. 6J: a pseudo-screenshot of a user interface according to an embodiment of the present disclosure, further comprising display elements and user interaction elements for the parametrization and/or testing of physical HVAC device(s); and

FIG. 7: a schematic block diagram of an HVAC system according to an embodiment of the present disclosure, comprising an Air Handling Unit AHU with a plurality of physical HVAC devices interconnected by a ModBus communication bus.

DETAILED DESCRIPTION

Reference will now be made in detail to certain embodiments, examples of which are illustrated in the accompanying drawings, in which some, but not all features are shown. Indeed, embodiments disclosed herein may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Whenever possible, like reference numbers will be used to refer to like components or parts.

In the following figures, like elements of which one or more are part of embodiments disclosed herein, are denoted with a reference numeral followed by an index range, such as. 1-n, wherein n is a whole number greater than or equal to 1, an x denotes any one of the like elements in the range of 1-n.

FIG. 1 shows a highly schematic block diagram of an HVAC system 1 according to an embodiment of the present disclosure. The HVAC system 1 comprises a plurality of HVAC devices C1, C2, C3, Cn, referred to hereafter in general as Cx. The HVAC devices Cx include one or more of motorized HVAC devices, such as actuators, valves, dampers, pumps, and fans, and other devices connected to the HVAC system, such as flow sensors, pressure sensors, temperature sensors, rotation sensors, position sensors, humidity sensors, etc. Each HVAC device Cx comprises a bus communication interface 14 for being connected to the communication bus 40, such as an MP-Bus, Modbus, BACnet, KNX, BLE, Thread, ZigBee, or Z-Wave.

One of the physical HVAC devices is selected as master HVAC device Cmaster. In order to be selectable as master HVAC device, a physical HVAC device must comprise processing capabilities to enable the steps of identifying S20, determining S30, receiving an application model S40, generating the mapping of physical HVAC devices to virtual HVAC devices S50, retrieving device profiles S60 and enabling data communication between the physical HVAC devices and virtual HVAC devices S70 (for a description of steps S10 to S80, please refer to the following paragraph related to FIGS. 2 to 5). According to the embodiment shown on FIG. 1, the physical HVAC device selected as master HVAC device Cmaster comprises a processing unit 20, a data storage 30 and an actuator and/or sensor A/S. The data storage 30 stores a computer program product, which, when executed by the processing unit 20, causes the master HVAC device Cmaster to carry out the method of commissioning.

FIG. 1 further shows the optional connection of the HVAC system 1 to a remote computer 100, such as a Building Management System BMS, located on a server computer or in a cloud environment. The remote computer 100 is communicatively connected to the HVAC system 1 via a remote communication interface 12 of the master HVAC device Cmaster. According to particular use cases, the HVAC application, the application model and/or the device profile(s) reside(s) on the remote computer 100.

Turning now to FIGS. 2 to 4, steps of the method of commissioning physical HVAC devices Cx of an HVAC system 1 for an HVAC application shall be described.

FIG. 2 shows a flowchart illustrating a method of commissioning physical HVAC devices Cx of an HVAC system 1 for an HVAC application. In a preparatory step S10 of the method, a plurality of physical HVAC devices Cx of the HVAC system 1 are communicatively inter-connected by a communication bus 40 via each physical HVAC device's Cx bus communication interface 14. According to embodiments of the present disclosure, one or more of the plurality of physical HVAC devices Cx are automatically addressed upon being connected to the communication bus 40.

Further in step S10, one of the plurality of physical HVAC devices Cx is selected as master HVAC device Cmaster. The selection of one of the plurality of physical HVAC devices Cx as master HVAC device Cmaster may be an automatic selection of a first physical HVAC device comprising a processing unit 20 powerful enough and configured for the carrying out the methods steps of commissioning physical HVAC devices Cx. Alternatively, or additionally, one of the plurality of physical HVAC devices Cx is selected as master HVAC device Cmaster by a configuration, either by input received by the respective physical HVAC device Cx or configuration pre-recorded into a data store 30 of the master HVAC device Cmaster.

After a physical HVAC device Cx has been selected as master HVAC device Cmaster, in step S20, the master HVAC device Cmaster identifies each of the physical HVAC devices Cx connected to the communication bus 40 by retrieving respective identification data of the physical HVAC devices Cx. According to embodiments of the present disclosure, the identification data may be a mere ID number of the physical HVAC device Cx. Alternatively, or additionally, the identification data may further comprise data descriptive of the device type and/or functionalities supported by the respective physical HVAC device Cx.

Once the physical HVAC devices Cx connected to the communication bus 40 have been identified, in step S30, the master HVAC device Cmaster determines the device type(s) of the physical HVAC devices Cx using the respective identification data. According to embodiments of the present disclosure, the master HVAC device Cmaster determines the device type(s) of the physical HVAC devices Cx by way of a database query, stored either locally in the master HVAC device Cmaster; on a remote computer 100 or a configuration device 200 communicatively connected to the master HVAC device Cmaster.

In step S40, which may be subsequent, preceding or parallel to the previously described steps S10, S20 and/or S30, the master HVAC device Cmaster receives an application model of an HVAC application. The application model, defined for an HVAC application, comprising a list of virtual devices required to implement the respective HVAC application. The application model also comprises data indicative of the device type of each virtual HVAC device. The device type defines the minimum capabilities a physical HVAC device Cx needs to possess in order to fulfill the required functions for the HVAC application.

After the physical HVAC devices have been identified, their device types determined and the application model has been received (Steps S10 to S40), in step S50, the master HVAC device Cmaster generates a mapping of one or more of the plurality of physical HVAC devices Cx to one or more of the plurality of virtual HVAC devices of an HVAC application. The mapping is generated using the respective determined device type(s) of the plurality of physical HVAC devices Cx and the device type(s) of the virtual HVAC devices. According to embodiments disclosed herein, the mapping is based on identical device types of physical HVAC devices Cx and the device type(s) of the virtual HVAC devices. Alternatively, the mapping is based on the device type of physical HVAC devices Cx being compatible with the device type(s) of the virtual HVAC devices. According to a particular embodiment, the device type of the virtual HVAC device defines a set of capabilities that a physical HVAC device X must possess. Correspondingly, a physical HVAC device Cx is compatible with such a device type if it possesses at least the capabilities defined by the device type, irrespective whether the physical HVAC device Cx possesses additional capabilities.

Before, during or after the mapping has been generated, in a step S60, the master HVAC device Cmaster retrieves the device profile(s) corresponding to the device type(s) determined for the physical HVAC devices Cx. Alternatively, or additionally, the device profile(s) are retrieved corresponding to the identification data of the physical HVAC devices Cx. According to embodiments of the present disclosure, the master HVAC device Cmaster retrieves the device profile(s) by way of a database query, stored either locally in the master HVAC device Cmaster; on a remote computer 100 or a configuration device 200 communicatively connected to the master HVAC device Cmaster.

Once the device profile(s) have been retrieved and the mapping generated, in step S70, data communication between the HVAC application and the plurality of physical HVAC devices Cx is enabled by the master HVAC device Cmaster. Enabling data communication between the HVAC application and the plurality of physical HVAC devices Cx comprising directing data communication from the HVAC application to the appropriate physical HVAC device Cx based on the mapping and attributing data communication from the physical HVAC device Cx to the appropriate virtual HVAC device based on the mapping.

Details of step S50 of generating a mapping of physical HVAC devices to virtual HVAC devices shall now be elaborated on with reference to FIG. 3.

In a substep S52—of step S50—each singular physical HVAC device Cx of a device type is automatically mapped to a singular virtual HVAC device. In this context, “singular . . . of a device type” refers to a physical HVAC device of a particular device type from which no other HVAC device has been identified in the HVAC system. In other words, the physical HVAC device is unique (singular) amongst the identified physical HVAC devices of the HVAC system. In this context, “singular . . . of a device type” further refers to a virtual HVAC device of a particular device type from which no other HVAC device is listed on the device list of the HVAC application. In other words, the virtual HVAC device is unique (singular) amongst the virtual HVAC devices of the HVAC application.

Alternatively, or additionally, in a substep S54—of step S50—a selection list of a plurality of physical HVAC devices Cx having compatible device type(s) with the device type(s) of the virtual HVAC devices of the HVAC application is provided. Thereafter, in substep S56—of step S50—user input is received indicative of a selection of one or more physical HVAC devices Cx from the selection list to be mapped. In particular, if more than one compatible physical HVAC devices Cx have been identified for a particular virtual HVAC device, a selection of all compatible physical HVAC devices Cx is provided. The mapping is then performed according to a user selection of the physical HVAC device Cx amongst the more than one compatible physical HVAC devices Cx.

Details of step S70—enabling data communication between the HVAC application and the plurality of physical HVAC devices Cx—shall be described with reference to FIG. 4. According to embodiments of the present disclosure, the device profile(s) comprise device-specific processing data corresponding to the physical HVAC devices Cx identified by the identification data.

Correspondingly, step S70 of enabling data communication between the HVAC application and the plurality of physical HVAC devices Cx comprises substep S 72 of processing, by the master HVAC device Cmaster, operational data received from the physical HVAC devices Cx, in particular from sensors, using the device-specific processing data. In a subsequent substep S74, the thereby processed operational data is forwarded to the HVAC application.

Alternatively, or additionally, step S70 of enabling data communication between the HVAC application and the plurality of physical HVAC devices Cx comprises substep S76 of processing, by the master HVAC device Cmaster, control data generated by the HVAC application using the device-specific processing data. Subsequently, in substep s78, the thereby processed control data is forwarded to the respective physical HVAC devices Cx.

FIG. 5 shows a flowchart illustrating a method of commissioning physical HVAC devices Cx of an HVAC system 1 for an HVAC application according to an embodiment of the present disclosure, illustrating the step S80 of assisted replacement of a physical HVAC device Cx. In a first substep S82—of step S80—a physical HVAC device C1 to be replaced is identified by the master HVAC device Cmaster (by automatic detection or user selection). In further substep S82—of step S80—a replacement physical HVAC device C2 is identified by the master HVAC device Cmaster (by automatic detection or user selection). Thereafter, in a substep S86—the master HVAC device Cmaster updates the mapping of a virtual HVAC device to the physical HVAC device C1 to be replaced with the replacement physical HVAC device C2 such that the replacement physical HVAC device C2 is addressed instead of the now removed physical HVAC device C1 to be replaced. Hence, the replacement physical HVAC device C2 takes over seamlessly the place of physical HVAC device C1 to be replaced, the HVAC application being able to continue operation with the virtual HVAC device (to which the replacement HVAC device is now mapped).

Turning now to the sequence of FIGS. 5A through 5l, an exemplary implementation of the method according to an embodiment of the present disclosure shall be described. FIGS. 5A through 5l shows pseudo-screenshots of a user interface generated by instructions of a computer program product executed by a processor 20 of the master HVAC device Cmaster, also referred to as “Startup Assistant”. The user interface may be rendered on browser or a dedicated application (mobile app) running on a configuration device 200 (see FIG. 1) communicatively connected to the HVAC system 1. The configuration device 200 may one or more of a portable device, such as a general purpose mobile computing device (e.g. a smartphone) or a dedicated configuration tool. The configuration device 200 may be connected directly to the master HVAC device Cmaster, by a local area network communication link (such as Ethernet, or Wireless LAN) and/or a short range wireless communication link (such as Bluetooth, Bluetooth low energy BLE, Thread and/or Zigbee) and/or a close-range wireless communication link (such as Radio Frequency Identification RFID or a Near Field Communication NFC). Alternatively, or additionally, the configuration device 200 may be connected indirectly—via a communication provider—to the master HVAC device Cmaster via Wide Area Network communication (such as GSM, LTE, 3G, 4G or 5G mobile communication) and/or a Low Power Wide Area Network communication (such as Narrowband Internet of Things NB-IoT, Long Range LoRa/LoRaWAN, SigFox, or Long Term Evolution Category M1 LTECatM1).

FIG. 6A shows a first pseudo-screenshot of the user interface as rendered on the configuration device 200, comprising display elements for displaying a list of available HVAC applications, such as an Air Handling Unit application, a Fan Coil Unit FCU application, a Variable Air Volume application or a Constant Air Volume application. The list of available HVAC applications comprises HVAC applications stored locally in the master HVAC device and/or stored on a remote computer communicatively connected to the master HVAC device via a remote communication interface. The display elements for displaying a list of available HVAC applications also acts as user interaction elements for receiving a selection of a HVAC application amongst the list of available HVAC applications, for example by selection using a cursor or a touching a touch sensitive display.

FIG. 6B shows a further pseudo-screenshot of the user interface as rendered on the configuration device 200, comprising display elements for displaying a device list listing a plurality of virtual HVAC devices of a selected HVAC application—in the illustrated example, an Air Handling Unit AHU. The list of virtual HVAC devices indicates what physical HVAC devices are needed to implement the HVAC application of an Air Handling Unit AHU, namely an Exhaust-Air Damper, an Outdoor-Air Damper and a Fan.

FIG. 6C shows a further pseudo-screenshot of the user interface as rendered on the configuration device 200, further comprising user interaction elements for altering one or more parameters of the device types of the virtual HVAC devices of the selected HVAC application. In the illustrated example, the user interaction elements enable the selection of the appropriate range of torque of the EXA Damper actuator.

FIG. 6D shows a pseudo-screenshot of the user interface as rendered on the configuration device 200, further comprising a user interaction element (labelled “SCAN”) for triggering a scan of the HVAC system 1, comprising identification of the physical HVAC devices Cx connected to the communication bus 40 by the master HVAC device Cmaster by retrieving respective identification data of the physical HVAC devices. According to embodiments of the present disclosure, the identification data may be a mere ID number of the physical HVAC devices Cx. Alternatively, or additionally, the identification data may further comprise data descriptive of the device type and/or functionalities supported by the respective physical HVAC device Cx. Once the physical HVAC devices connected to the communication bus have been identified, the master HVAC device determines the device type(s) of the physical HVAC devices using the respective identification data.

The results of scanning the HVAC system 1 by the master HVAC device Cmaster are shown on the display elements of FIG. 6F, displaying a list of physical HVAC devices Cx connected to the communication bus 40 besides their determined device types.

As shown on FIG. 6F, the user interface also comprises user interaction elements (labelled “MAP”) for triggering the mapping of the plurality of physical HVAC devices Cx to the plurality of virtual HVAC devices of the HVAC application.

FIG. 6G shows a pseudo-screenshot of the user interface as rendered on the configuration device 200, further comprising display elements for displaying a visual representation of the mapping of the plurality of physical HVAC devices Cx to the plurality of virtual HVAC devices of the HVAC application.

FIG. 6H shows a pseudo-screenshot of the next step of the user interface as rendered on the configuration device 200, comprising user interaction elements for triggering application of the device profiles to enable data communication between the HVAC application and the plurality of physical HVAC devices Cx.

Optionally, as shown on FIG. 6I, display elements are provided in a further screen of the user interface for displaying a visual representation of the commissioned HVAC application.

According to further embodiments, as shown on FIG. 6J, display elements and user interaction elements are provided for the parametrization and/or testing of the functionality of the individual physical HVAC devices Cx.

As illustrated, for example, control data may be input using the user interaction elements and sent to the physical HVAC device to move an actuated part into a defined setpoint position. Thereafter, testing of the respective physical HVAC device comprises verifying whether the actuated position as reported (based on operational data received from the physical HVAC device) matches the setpoint position (optionally with a defined tolerance). The user interaction elements may comprise means to cause the physical HVAC device(s) to emit an identifying signal, such as a visual signal (such as the blinking of a light) to allow a user to identify the physical HVAC device Cx. Alternatively, or additionally, a radio signal beacon may be activated as identifying signal. FIG. 7 shows a schematic block diagram of an HVAC system 1 according to a particular HVAC application of a particular type of Air Handling Unit AHU. Air handler units AHUs are commonly employed to condition and circulate air as part of an HVAC system 1 for buildings, and large buildings in particular. AHUs may provide heating, cooling, or both to change the supply air temperature, humidity level, or both depending on geographic location and current environmental factors. Such conditioning is provided by coil(s) (e.g., heat exchanger coils or cooling coils) located to interact with the AHU's air flow. Conditioning of the air flow employs the use of hot water or steam for heating and cool or chilled water, and sometimes refrigerant for cooling. Coils for transferring heat may take the form of metallic tubes combined with metallic fins to encourage heat transfer; whereas cooling coils may also employ eliminator plates and condensate pans to remove and drain condensation.

The AHU includes two fluid circuits that receive heated or cooled water, respectively, (or sometimes heated and cooled simultaneously for humidity control purposes) from a cold water supply line and a hot water supply line, respectively. The flow of the cooled water through a first heat exchanger and back to the chilled water return line is controlled (e.g., modulated) by a first valve actuated by a first actuator C4. Similarly, the flow of heating water through a second heat exchanger and back to the hot water return line is controlled by a second valve actuated by a second actuator C5. Air temperature sensors C1 and C2 are positioned within the AHU. Furthermore, a combined temperature and relative humidity sensor C3 is provided at an exit side of the second heat exchanger to control the temperature in view of the relative humidity, e.g. such as to prevent condensation.

The temperature sensors C1 and C2, the relative humidity sensor C3, the first actuator C4 and second actuator C5—all physical HVAC devices—are interconnected by a ModBus communication bus 40.

In the example shown on FIG. 7, the physical temperature sensors C1 and C2, the relative humidity sensor C3 are each mapped to virtual HVAC devices of the device type temperature sensor and relative humidity sensor, respectively. The actuators C4 and C5 are mapped to virtual HVAC devices of the device type Exhaust-Air and Outdoor-Air Damper, respectively.

LIST OF REFERENCE NUMERALS

• • HVAC system 1
  • physical HVAC device Cx
  • physical HVAC device to be replaced C1
  • replacement physical HVAC device C2
  • master HVAC device Cmaster
  • remote communication interface (of physical HVAC devices) 12
  • bus communication interface (of physical HVAC devices) 14
  • processing unit (of physical HVAC devices) 20
  • data storage (of physical HVAC devices) 30
  • communication bus 40
  • remote computer 100
  • configuration device 200

Claims

1. A method of commissioning physical HVAC devices of an HVAC system for an HVAC application, the method comprising: communicatively connecting a plurality of physical HVAC devices to a communication bus via each physical HVAC device's bus communication interface, one of the plurality of physical HVAC devices being selected as master HVAC device;identifying, by the master HVAC device, the physical HVAC devices connected to the communication bus by retrieving respective identification data of the physical HVAC devices;determining, by the master HVAC device, device type(s) of the physical HVAC devices using the respective identification data;receiving, by the master HVAC device, an application model comprising a device list listing a plurality of virtual HVAC devices of the HVAC application and, comprising data indicative of a device type of each virtual HVAC device;generating, by the master HVAC device, a mapping of the plurality of physical HVAC devices to the plurality of virtual HVAC devices of the HVAC application using the respective determined device type(s) of the plurality of physical HVAC devices and the device type(s) of the virtual HVAC devices.

2. The method according to claim 1 further comprising: retrieving, by the master HVAC device, device profile(s) corresponding to the determined device type(s) and/or the identification data of the physical HVAC devices; andenabling, by the master HVAC device using the respective device profile(s) and the mapping, data communication between the HVAC application and the plurality of physical HVAC devices.

3. The method according to claim 1, wherein the HVAC application resides and/or is executed by the master HVAC device and/or a remote computer communicatively connected to the master HVAC device via a remote communication interface and wherein the HVAC application comprises computer readable instructions for generating control data for controlling the physical HVAC devices and/or for processing operational data received from the physical HVAC devices.

4. The method according to claim 1, further comprising: receiving a selection of an HVAC application amongst a list of available HVAC applications; andretrieving, by the master HVAC device, an application model corresponding to the selected HVAC application.

5. The method according to claim 4, wherein: the list of available HVAC applications comprises HVAC applications stored locally in the master HVAC device and/or stored on a remote computer communicatively connected to the master HVAC device via a remote communication interface; andthe master HVAC device retrieves the application model corresponding to the selected HVAC application from a data storage of the master HVAC device and/or from a remote computer communicatively connected to the master HVAC device via a remote communication interface.

6. The method according to claim 1, wherein generating the mapping of physical HVAC device(s) to virtual HVAC device(s) comprises one or more of: automatically mapping each singular physical HVAC device of a device type to a singular virtual HVAC device;providing a selection list of a plurality of physical HVAC devices having compatible device type(s) with the device type(s) of the virtual HVAC devices of the HVAC application and receiving user input indicative of a selection of one or more physical HVAC devices from the selection list to be mapped.

7. The method according to claim 2, wherein the device profile(s) comprise device-specific processing data corresponding to the physical HVAC devices identified by the identification data; and wherein enabling data communication between the HVAC application and the plurality of physical HVAC devices comprises: processing, by the master HVAC device, operational data received from the physical HVAC devices using the device-specific processing data and forwarding the thereby processed operational data to the HVAC application; and/orprocessing, by the master HVAC device, control data generated by the HVAC application using the device-specific processing data and forwarding the thereby processed control data to the respective physical HVAC devices.

8. The method according to claim 7, wherein the device-specific processing data comprises calibration data specific to the physical HVAC devices identified by the identification data, wherein the processing by the HVAC gateway device comprises: applying the calibration data to operational data received from the physical HVAC devices and/orapplying the calibration data to control data generated by the HVAC application.

9. The method according to claim 7, wherein the device-specific processing data comprises conversion data including conversion parameters and/or conversion formulae, wherein the processing by the master HVAC device, comprises applying the conversion parameters and/or conversion formulae to operational data received from the physical HVAC devices.

10. The method according to claim 1, further comprising the step of testing the HVAC application using the mapping of the plurality of physical HVAC devices to the plurality of virtual HVAC devices of the HVAC application.

11. The method according to claim 7, wherein, the control data comprises actuator values, the method further comprising: actuating, by actuator(s) of the respective physical HVAC devices, of one or more mechanically connected actuated parts in accordance with actuator values of the control data as processed and forwarded by the master HVAC device.

12. The method according to claim 1, further comprising: identifying, by the master HVAC device, a physical HVAC device to be replaced;identifying, by the master HVAC device, a replacement physical HVAC device; andupdating, by the master HVAC device, the mapping of a virtual HVAC device from the physical HVAC device to be replaced with the replacement physical HVAC device.

13. The method according to claim 12, further comprising: retrieving operational data from the physical HVAC device to be replaced and transmitting the retrieved operational data to the replacement physical HVAC device; and/orupdating parameters of the device profile of the replacement physical HVAC device using parameters of the device profile of the physical HVAC device to be replaced.

14. A master HVAC device comprising: a bus communication interface for communicatively connecting one or more further physical HVAC device(s);a processor;wherein the processor is configured to control the master HVAC device to carry out the method according to claim 1.

15. The master HVAC device according to claim 14, further comprising one or more actuator(s) for actuating mechanically connected actuated part(s) and/or one or more sensor(s).

16. An HVAC system comprising: the master HVAC device according to claim 14; andone or more physical HVAC devices comprising one or more actuator(s) for actuating mechanically connected actuated part(s) and/or one or more sensor(s),wherein the master HVAC device and the one or more physical HVAC devices are communicatively connected by a communication bus via respective bus communication interfaces.

17. A non-transitory computer readable medium comprising instructions, which, when executed by a processor of a master HVAC device, cause the master HVAC device to carry out the method according to claim 1.

18. The non-transitory computer readable medium according to claim 17, further comprising instructions, which, when executed by the processor of the master HVAC device, cause generation of a user interface comprising: display elements for displaying a list of available HVAC applications;user interaction elements for receiving a selection of a HVAC application amongst the list of available HVAC applications;display elements for displaying the device list listing a plurality of virtual HVAC devices of the selected HVAC application;display elements for displaying a list of physical HVAC devices connected to the communication bus; anddisplay elements for displaying a visual representation of mapping of the plurality of physical HVAC devices to the plurality of virtual HVAC devices of the HVAC application.

19. The non-transitory computer readable medium according to claim 18, wherein the user interface further comprises: display elements for displaying a device type of virtual HVAC devices of the selected HVAC application; anduser interaction elements for altering one or more parameters of the device types of the virtual HVAC devices of the selected HVAC application.