EP3155489A1 - Verfahren zur gebäudeautomatisation - Google Patents
Verfahren zur gebäudeautomatisationInfo
- Publication number
- EP3155489A1 EP3155489A1 EP15706166.4A EP15706166A EP3155489A1 EP 3155489 A1 EP3155489 A1 EP 3155489A1 EP 15706166 A EP15706166 A EP 15706166A EP 3155489 A1 EP3155489 A1 EP 3155489A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- data
- automation
- management system
- building management
- field device
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
Classifications
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B15/00—Systems controlled by a computer
- G05B15/02—Systems controlled by a computer electric
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2803—Home automation networks
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/20—Pc systems
- G05B2219/25—Pc structure of the system
- G05B2219/25011—Domotique, I-O bus, home automation, building automation
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/20—Pc systems
- G05B2219/26—Pc applications
- G05B2219/2642—Domotique, domestic, home control, automation, smart house
Definitions
- the field device via a data line with connected to the automation system
- Automation system transmitted to the field device via the data line at least data, the building management system via a
- Bus system is connected to the automation system, wherein the building management system via the bus system with the automation system mutually exchanges records, the automation system comprises an automation controller, the automation controller controls the field device directly, the automation system comprises a record memory, the records stored in the record memory and wherein the record store exchanges the records with the building management system using a common communication protocol.
- BMS building management system
- the building management system is connected directly to the automation systems via a bus system or with the interposition of gateways or routers.
- the automation systems can be designed as a controller or as a so-called controller or controller for a field device.
- the field device is regularly connected via a data line or connection cable or a fieldbus to the automation system, whereby the automation controller can control the field device or a plurality of field devices directly or communicate with the field devices or exchange data.
- Field devices may be actuators, sensors or other devices for building automation, for example a fan of a ventilation and air-conditioning system.
- a connection between the building management system and the automation system via a bus protocol is also regularly referred to as an interface, wherein a protocol-based communication between automation systems and field devices can also be referred to as fieldbus.
- the communication protocols are used for the exchange of so-called data points or data objects between the building management system, the automation system and the field device, wherein a bidirectional and also unidirectional exchange of data can take place.
- the automation system comprises an automation controller, which may be, for example, a software application.
- the automation controller is then designed so that it can communicate directly with the field device and control it.
- the automation control is individually adapted to the field device.
- a correspondingly adapted automation control or programming of a control is required in each case for different manufacturers of a field device.
- a direct communication of the automation control with the building management system is therefore not readily possible.
- the automation system has a data record memory, which is integrated separately from the automation controller in the automation system.
- the automation controller or an individualized software application exchanges data records pertaining to the respective field device to the data record memory according to previously defined conventions, ie data sets are synchronized between the automation controller and the data record memory, the data records being in their respective data format are different from each other.
- the records located in the record store are then in a format that corresponds to the communication protocol used by the building management system or the bus system so that the record store can immediately exchange the respective records with the building management system using the common communication protocol.
- the data set memory accordingly makes log-compliant data of the field device available to the building management system or receives it from the building management system. It is thus possible to communicate with a single building management system via a common communication protocol with a multiplicity of automation systems and different field devices connected thereto, regardless of the type of field device, its manufacturer, the respective connection and the exchanged data formats.
- the present invention is therefore based on the object to propose a method for building automation, which simplifies commissioning and operation of a building control system.
- the inventive method for building automation in particular for data exchange between a building management system (GLT) and a field device, actuator, sensor or the like, is performed with a building management system, at least one automation system and in each case at least one field device, wherein the field device via a data line or ., A fieldbus system is connected to the automation system, wherein the automation system the
- the building management system is connected via a bus system with the automation system, the building management system via the bus system with the automation system mutually exchanged data sets, the automation system includes an automation control, the automation controller controls the field device directly, wherein the automation system comprises a record store, wherein the records are stored in the record store, the record store exchanging the records with the building management system using a common communication protocol, the automation controller comprising the record store, the automation controller providing a data object representing the field device , wherein the obj ect from the automation controller as a record in a obj eectformat of the Communic is stored and / or read in the record memory.
- a plurality of automation systems can also be connected to the building management system via the bus system.
- the field device (s) are in each case connected to the automation system via the data line, wherein the data line is an analog line connection or a digital line connection, such as a fieldbus system, via which data is exchanged with the field device.
- the building management system and the automation system are in each case essentially a computer or a similar device for data processing with a computer program running thereon.
- the automation controller is designed as a computer program or as an application, which is executed to carry out the method with the automation system.
- the automation controller can be adapted to the j eix field device based on a standardized computer program platform and specifically designed.
- the automation control comprises the data record memory and that the data record memory is no longer, as known from the prior art, an application separate from the automation control.
- the automation controller provides a data object or software object for each field device connected to the automation system, or it can also generate this optionally, wherein the data object is assigned to the field device and thus represents the field device in the automation system.
- the data object is stored and / or read as a data record in the data object format of the common communication protocol of the building management system and the automation system in the data record memory.
- the building management system can communicate directly with the automation controller via the common communication protocol by storing and / or reading these records from the building management system in the record store.
- the data record memory is thus within the automation control or integrated in the individual applications adapted to the respective field devices. This integration is only possible because the automation controller operates data objects with a data obj ect format which corresponds to the common communication protocol.
- a value for example in the form of a voltage
- a value is provided by an output of the field device so that it is read by the automation system or the automation controller via the data line and stored directly in the data record memory as a data record.
- the data record is read out directly from the building block management system via the bus system from the data record store.
- the building management system can also write the data record directly into the data record memory so that a value is given to the field device via the data line via an input of the field device and the field device is thus controlled.
- an interface of the bus system can be integrated in the automation controller, wherein data records are exchanged directly between the building management system and the automation controller.
- the interface can be a data-oriented interface, whereby the common communication protocol of the interface can transmit object-oriented data records. Due to the then possible, direct data exchange from the building management system with the automation control, errors during data exchange can be effectively avoided.
- the automation system may comprise a programmable logic controller (PLC) for data exchange with the field device, in which case the automation controller is formed by the stored-program controller and communicates with the field device.
- PLC programmable logic controller
- the automation control can accordingly be designed as a memory-programmed controller and exchange data directly with the field device or with a plurality of field devices.
- the programmable controller may further have a human-machine interface or input and output means for programming and operation.
- an interface of the data line or the field bus system may be integrated in the stored-program controller.
- the programmable logic controller according to the standard IEC 61 13 1, EN 6 1 13 1 -3, IEC 61499 or EN 61499 be formed and communicate with the field device. In this way, it can be ensured that the programmable controller operates in accordance with international standards and can be easily operated by different persons.
- object-oriented programming of the stored-program control it is then also possible to provide data objects or software objects for the field devices.
- the automation controller may use as the communication protocol Building Automation and Control Networks (BACnet) are used.
- BACnet Building Automation and Control Networks
- a data point of the communication protocol BACnet is a property of a data object. Furthermore, interoperability of BACnet devices or field devices can be ensured with the BACnet communication protocol. Thus, special functions, such as a common data usage, alarm and event processing, processing of value changes and device and network management can be shared.
- At least one further data record memory can be provided by the automation controller, wherein the automation controller can synchronize a data record of the data object in the data record memory with the further data record memory in accordance with a further data format format of a further communication protocol.
- the automation controller can synchronize a data record of the data object in the data record memory with the further data record memory in accordance with a further data format format of a further communication protocol.
- other communication protocols which, for example, are not object-oriented but datapoint-oriented.
- This can essentially be made possible by synchronization of data records contained in the data record store with data records in the further data record store within the automation control.
- the data records contained in the further data record memory are adapted during synchronization to the conventions of the further communication protocol. This makes it possible to use the automation controller, in principle, regardless of a particular communication protocol.
- the further data record memory can exchange the data records with the building management system by means of the further communication protocol, wherein as another communication protocol Modbus according to the standard IEC 61 158, Simple Network Management Protocol (SNMP), Process Field Bus (Profibus), Process Field Network (Profinet), Local Operating Network (LON) or KNX can be used.
- SNMP Simple Network Management Protocol
- Profilet Process Field Bus
- LON Local Operating Network
- KNX KNX
- the automation controller can export the data objects contained in the data record memory into an EDE file (Electronic Data Exchange File).
- the export of the data objects can be automated.
- the EDE file may continue as one
- Section location documentation serve.
- the building management system can also import the EDE file, whereby an export and / or import can take place statically or dynamically according to a specification. This makes it possible to import the EDE file exported by the automation controller into the building management system by an operator or also automatically. Any errors due to a manual input of data, as known from the prior art, are thus avoided. Because the EDE file can be imported into the building management system, the building management system has immediate, direct access to the automation control. As a result, integration times and efforts can be minimized or even eliminated on the part of the building management. Thus test runs and their documentation can be partially or completely automated, which considerably simplifies commissioning and revision of the building management system with the automation system.
- the point-to-point test prescribed so far could possibly only be carried out in the future by a representative of the building management systems, without additional on-site involvement of a representative of the automation systems. This alone results in considerable savings, since up to now several man-days of several trades had to be applied for point-to-point tests for commissioning, but also for revisions.
- the data objects contained in the data record memory can be read in directly statically or dynamically by the building management system. For example, you can completely dispense with exporting and importing an EDE file. The building management system can read them in directly by accessing the data objects or import them directly, without detours, and implement the data objects in the building management system.
- data points of the data sets in the data memory are marked or supplemented with attributes by the automation controller when exchanging the data records with the building management system, the data points then being marked with the attribute visible, invisible, readable, unreadable, writable or unwriteable can be.
- unimportant or superfluous data points can be removed as needed for the building management system.
- These data points then continue to be part of the respective data records, but only within the automation control. All information is then permanently available within the automation control, so that if the interface to the building management system is changed, subsequent programming of the automation control becomes unnecessary. It may only be necessary to change attributes of the data points of the records as needed.
- the marking of the data points can be carried out in the context of the method according to a specification or also dynamically. This considerably simplifies the commissioning of an interface between the building management system and the automation system. For example, an identification of the data points then also occur in situ during the operation of the building management system and be tested immediately.
- the automation controller can at least one predefined authorization profile for data points of data records have, wherein the identification of the data points by means of the authorization profile fils can be performed.
- the predefined authorization profile can be a so-called access rights profile, via which different standard write authorizations of the data objects can be defined.
- individual profiles of the respective user can also be created and managed. A change of the authorization profiles can be done dynamically. It also opens up the possibility of using once created authorization profiles in other building management systems without having to reconcile the authorization profiles.
- the automation system may advantageously have a profile memory for different authorization profiles, wherein a change in a permissions pro fils can be performed by means of the automation control, with such a change can be made even during operation of the automation control.
- the authorization profiles can be saved as so-called templates in the profile memory.
- a storage of the authorization profile in the profile memory as well as its change can be carried out by means of the automation control, for example via a man-machine interface.
- the automation controller logs a change of data records in the data record memory together with an address of a device connected to the bus system with which the change was initiated, preferably stores a history of changes.
- accesses from the building management system as well as from external devices via the bus system to the automation system or the automation control can be identified and recorded as part of the logging. It is thus easy to find the cause of any problems that might occur with a view to obtaining a guarantee.
- the data set The stored protocol can then be read out directly at the automation control or also remotely. If a change history is also stored in the log or in the log file, it is clearly comprehensible which device was used to change a record in the past.
- FIG. 1 shows a representation of a method for building automation according to the prior art in a block diagram
- FIG. 2 shows an illustration of an embodiment of a method for building automation in a block diagram
- FIG. 3 shows an illustration of a further embodiment of the method for building automation in a block diagram.
- Fig. 1 is a block diagram of a prior art method of building automation. The method is carried out with a building management system (GLT) or a building management system 10, an automation system 1 1 with an automation controller 12 and a data set memory 13 and a field device 14.
- the building management system 10 is connected to the data record memory 13 via a bus system 15 or fieldbus system.
- the field device 14 is connected to the automation controller 12 via a data line 16.
- a data exchange between building management system 10 and data record memory 13 via the bus system 15 takes place via a common communication protocol.
- the building management system 10 receives individual user information from the field device 14 or provided from the field level.
- An example analog output 17 of the field device 15 outputs for a fan control a voltage (volts), which is provided as a data point of a data set 1 8 or a manipulated variable of a fan speed in percent of the corresponding unit of the automation controller 12. If necessary, the automation controller 12 processes and visualizes the variable of the data set 1 8 via a human-machine interface 19.
- the automation controller 12 or its application provides the data set 1 8 via a link 20 to the data record memory 1 3, so that a data object format 21 in which a data record 22 is stored is set up in the data record memory 13.
- the building management system 10 can now access the data record 22.
- the data record 22 is in the format of the common communication protocol used by the building management system 10 and
- the building management system 10 accordingly writes or reads data records 22 from the record store 13.
- mapping of variables of the respective data sets 1 8 and 22 takes place, which bidirectionally ensures that both in the data record memory 13 and in the automation controller 12, the respective value or the variable remains the same.
- a documentation of the link 20 or interface takes place in the form of an EDE file 23, which is manually or manually created and imported into the building management system 10. The building management system 10 then has direct access to the data via the record memory 13
- Automation Control 12 As a rule, after commissioning of the automation system 1 1, the connection between the building management system 10 and the automation control 12 becomes separate tested, with a faulty EDE file 23, the link 20 can not function as intended, which requires a complex troubleshooting and correction.
- FIG. 2 shows a block diagram of a first embodiment of the method for building automation.
- the method is carried out with a building control system or a building management system 24, an automation system 25, an automation controller 26 and a data set memory 27 and a field device 28.
- automation systems 25, each having a plurality of field devices 28 may be connected.
- the data record memory 27 is integrated in the automation controller 26, resulting in a different method implementation.
- the building management system 24 is linked to the automation system 25 via a bus system 29 or the automation system 25 is connected to the field device 28 via a data line 30 or a fieldbus system.
- BACnet Building Automation and Control Networks
- IEC 61 1 3 1 An analog output 3 1 of the field device 28 also outputs a value in the form of a voltage in volts or provides it via the data line 30.
- the automation controller 26 or the corresponding software application provides a obj ect 32, which represents the field device 28.
- the data object 32 represents a data obj ect format
- the data object format 33 corresponds to the BACnet communication protocol, wherein the data record
- the data sets 34 assigned to the data object 32 are written or read in the data object memory 33 in the data record memory 27.
- the data records 34 are thus always adapted to the BACnet communication protocol.
- the automation controller 26 is provided with natively available classes and methods or functions of the protocol and can be addressed or instantiated by means of conventional methods of object-oriented software development.
- the Obj ektmodell the automation controller 26 thus uses the payload of the field device 28 in the form of an instantiation of the native payload and services of the BACnet communication protocol.
- the data obj ect format 33 inherits from the data object 32 all the properties and methods that are required or can be used for communication with the communication protocol.
- a programming of the automation controller 26 or an application can thus logically process a data record without regard to properties of the communication protocol.
- a human-machine interface 35 is provided, via which the automation controller 26 can be accessed directly.
- the man-machine interface 35 may comprise, for example, the known input and output means, such as keyboard and screen, wherein the automation system 25 and the automation controller 26 is a programmable logic controller (PLC).
- PLC programmable logic controller
- the method for building automation is executed as a result of the analog output 3 1 providing a value in the form of a voltage which is read via the data line 30 from the automation system 25 or the automation controller 26 and into the data record memory 27 is stored as a record 34.
- the data record 34 is read out by the building management system 24 via the bus system 29 from the data record memory 27 directly.
- the building management system 24 the record 34 also write to the data set memory 27, so that via the data line 30 to the field device 28, via an analog input not shown here, a value specified and the field device 28 is controlled so.
- an EDE file 36 is imported into the building management system 24.
- the EDE file 36 is created by an exporter 37 of the automation controller 26 and automatically exported.
- the exporter 37 uses this directly back to the used obj ektformat 33 of the automation controller 26. This eliminates a manual creation of an EDE file 36, which also no errors can occur due to the omitted here work step. Accordingly, an adaptation of the building management system 24 to the data format format 33 used takes place via the EDE file 36. This adaptation can also take place dynamically during the runtime of the automation controller 26.
- FIG. 3 shows a further embodiment of the method for building automation in a block diagram.
- an automation controller 38 with an additional communication protocol comprising data object 39 is formed here.
- the data record 34 is synchronized with a second data record 41 and a third data record 42.
- the second data record 41 here corresponds to the Modbus communication protocol
- the third data record 42 corresponding to the Simple Network Management Protocol (SNMP)
- SNMP Simple Network Management Protocol
- a second export device 47 or a third export device 48 an export of a data point list 49 or an export of a MIB list 50 and their respective import into the second building management system 45 or the third Building Management System 46 erfo conditions.
- the thus formed automation controller 38 is then not only usable with the based on the BACnet communication protocol building management system 24, but also with alternative communication protocols according to the second building management system 45 or the third building management system 46 or other building management systems not shown here.
Landscapes
- Engineering & Computer Science (AREA)
- Automation & Control Theory (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Programmable Controllers (AREA)
Abstract
Description
Claims
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP14002068 | 2014-06-16 | ||
PCT/EP2015/051735 WO2015192976A1 (de) | 2014-06-16 | 2015-01-28 | Verfahren zur gebäudeautomatisation |
Publications (1)
Publication Number | Publication Date |
---|---|
EP3155489A1 true EP3155489A1 (de) | 2017-04-19 |
Family
ID=51300488
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP15706166.4A Withdrawn EP3155489A1 (de) | 2014-06-16 | 2015-01-28 | Verfahren zur gebäudeautomatisation |
Country Status (2)
Country | Link |
---|---|
EP (1) | EP3155489A1 (de) |
WO (1) | WO2015192976A1 (de) |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8055387B2 (en) * | 2005-08-22 | 2011-11-08 | Trane International Inc. | Building automation system data management |
US7734572B2 (en) * | 2006-04-04 | 2010-06-08 | Panduit Corp. | Building automation system controller |
DK2831680T3 (en) * | 2012-03-28 | 2018-10-01 | Siemens Schweiz Ag | SYSTEM AND PROCEDURE FOR GROUPING BUILDING AUTOMATION OBJECTS FOR GROUP COMMUNICATION IN A BUILDING AUTOMATION SYSTEM |
-
2015
- 2015-01-28 WO PCT/EP2015/051735 patent/WO2015192976A1/de active Application Filing
- 2015-01-28 EP EP15706166.4A patent/EP3155489A1/de not_active Withdrawn
Non-Patent Citations (2)
Title |
---|
None * |
See also references of WO2015192976A1 * |
Also Published As
Publication number | Publication date |
---|---|
WO2015192976A1 (de) | 2015-12-23 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP1558975B1 (de) | Verfahren zur offline-parametrierung eines feldgerätes der prozessautomatisierungstechnik | |
EP2789145B1 (de) | Vorrichtung zur bedienung von mindestens einem feldgerät der automatisierungstechnik | |
DE102008019053B4 (de) | Verfahren zum Betreiben einer Anlage der Prozessautomatisierungstechnik | |
DE102010062266A1 (de) | Verfahren zur Realisierung von zumindest einer Zusatzfunktion eines Feldgeräts in der Automatisierungstechnik | |
DE102009046806A1 (de) | Verfahren zum Bereitstellen von gerätespezifischen Informationen eines Feldgeräts der Automatisierungstechnik | |
DE102009054901A1 (de) | Verfahren zur offline Bedienung eines Feldgeräts der Automatisierungstechnik | |
DE102007058606A1 (de) | Verfahren zur Integration von Geräteobjekten in ein objektbasiertes Managementsystem für Feldgeräte in der Automatisierungstechnik | |
EP2247987A1 (de) | Verfahren zum betreiben eines feldgerätes | |
DE10313389A1 (de) | Verfahren zur Übertragung von Softwarecode von einer Steuereinheit zu einem Feldgerät der Prozessautomatisierungstechnik | |
EP2171553A1 (de) | Verfahren zum bedienen eines feldgerätes der automatisierungstechnik | |
EP1653306B1 (de) | Verfahren zum Bedienen eines Feldgerätes der Automatisierungstechnik | |
DE102010026494A1 (de) | Verfahren zur Konfigurierung einer Steuerungseinrichtung | |
DE102007054417A1 (de) | Bestimmen von geräteinternen Parameteradressen aus feldbusspezifischen Parameteradressen eines Feldgerätes | |
WO2009074544A1 (de) | Verfahren zum betreiben eines systems aufweisend ein feldgerät und ein bediensystem | |
DE102008027846A1 (de) | Vorrichtung zum automatischen Erfassen der Topologie der einzelnen Komponenten einer Prozessanlage in der Automatisierungstechnik | |
EP1714197B1 (de) | Gerätetreiber für feldgeräte der prozessautomatisierungstechnik | |
DE102011005062A1 (de) | Verfahren zum Bereitstellen von Daten eines Feldgeräts | |
WO2012013424A1 (de) | Verfahren zur integration eines ersatz-feldgeräts anstelle eines feldgeräts in ein feldbussystem | |
DE102008038501A1 (de) | Verfahren zum Bestimmen einer statischen Datenstruktur eines Feldgerätes | |
DE10208530A1 (de) | Betriebseinheit, Peripheriegerät und Verfahren zum Betrieb eines Peripheriegeräts | |
DE102010040055B4 (de) | System zur Kommunikation von mehreren Clients mit mehreren Feldgeräten in der Automatisierungstechnik | |
WO2008058991A1 (de) | Verfahren zum betreiben eines nach dem blockmodell arbeitenden modularen feldgerätes der automatisierungstechnik | |
DE102007062395A1 (de) | Verfahren zum Parametrieren eines Feldgerätes der Prozessautomatisierungstechnik | |
DE102009000052A1 (de) | Verfahren zur Integration von Geräteobjekten in ein objektbasiertes Managementsystem für Feldgeräte in der Automatisierungstechnik | |
DE102007035159B4 (de) | Verfahren zum Parametrieren von mehreren Feldgeräten der Automatisierungstechnik |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE |
|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE |
|
17P | Request for examination filed |
Effective date: 20170110 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
AX | Request for extension of the european patent |
Extension state: BA ME |
|
RIN1 | Information on inventor provided before grant (corrected) |
Inventor name: GRAESSNER, PETER Inventor name: SCHULZE, TOBIAS |
|
DAX | Request for extension of the european patent (deleted) | ||
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: WEISS KLIMATECHNIK GMBH |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: GRANT OF PATENT IS INTENDED |
|
INTG | Intention to grant announced |
Effective date: 20191018 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN |
|
18D | Application deemed to be withdrawn |
Effective date: 20200229 |