Method for updating device descriptions for field devices in process automation technology
5 claims: 5 independent, 0 dependent
- 1Verfahren zum Aktualisieren von Gerätebeschreibungen für Feldgeräte der Prozessautomatisierungstechnik, wobei die Funktionalität eines Feldgerätes mittels der Gerätebeschreibung beschrieben wird, dadurch gekennzeichnet, dass ein Anwendungsprogramm in einer Steuereinheit (PC1;PC2) Gerätebeschreibungen für Feldgeräte (F1, F2, F3) von einem externen Server (S) lädt, wobei vom Anwendungsprogramm eine Anfrage an ein Feldgerät gesendet wird und der Gerätetyp des Feldgerätes abgefragt wird, dass in dem Fall, dass das Anwendungsprogramm die benötigten Informationen zu dem Feldgerät nicht oder nicht in der aktuellen Version besitzt, die notwendigen Gerätebeschreibungen via Internet vom externen Server geladen werden, auf welchem externen Server die aktuellsten Gerätebeschreibungen gespeichert sind, und dass das Anwendungsprogramm in regelmäßigen Abständen Anfragen an den externen Server (S) richtet, ob neue Gerätebeschreibungen vorliegen.
- 2Verfahren nach einem der vorhergehenden Ansprüche, dadurch gekennzeichnet, dass es sich bei den Gerätebeschreibungen um Device Descriptions DDs handelt.
- 3Verfahren nach einem der vorhergehenden Ansprüche, dadurch gekennzeichnet, dass im Server (S) vorkonfigurierte Gerätebeschreibungen abgespeichert sind.
- 4Verfahren nach einem der vorhergehenden Ansprüche, dadurch gekennzeichnet, dass die Gerätebeschreibungen im Server (S) in der jeweiligen Landessprache abgespeichert sind.
- 5Verfahren nach einem der vorhergehenden Ansprüche, dadurch gekennzeichnet, dass die Steuereinheit (PC1;PC2) und der Server (S) über das Internet (I) miteinander verbunden sind.
Independent claims5
30 paragraphs, as filed
p0001The invention relates to a method for updating device descriptions for field devices of the process automation technology according to the preamble of claim 1.
p0002In the field of process automation technology, field devices are frequently used for recording and influencing process variables. Examples of field devices are temperature measuring devices, which measure the temperature of a process medium, flow meters which detect the flow of a process medium in a pipeline section or fill level meters which detect the fill level of a liquid or a bulk material in a container.
p0003The field devices are generally connected via a data bus to superordinate control units, eg process control systems PLS or engineering system, from which the process sequence is controlled or monitored and direct access to individual field devices is also possible. Direct access to the field device can be used to change settings on the field device from the control unit or to call diagnostic functions of the field device. The measured values of the various sensors are evaluated or monitored in the control unit and the corresponding actuators are controlled for process control. Data transmission between field device and control units is carried out according to known international standards for fieldbuses such as HART®, Foundation Fieldbus®, Profibus® or CAN-Bus®, etc.
p0004Frequently, field devices from different manufacturers are used in process automation technology. The field devices are operated by means of PC-based applications which, in particular, support the parameterization, commissioning and diagnosis of individual field devices, in some cases also graphically.
p0005Examples of such display and operating programs are AMS® from Fisher-Rosemount, Simatic PDM® from Siemens, Smart Vision® from ABB, VVO® from Vega or Commuwin® II from Endress + Hauser.
p0006In order to enable the operation of various field devices from a control unit, the functionality of the respective field device must be known to the control device. The functionality of the field device is described by the so-called device description (Device Descriptions DDs). For this purpose, a special language, the Device Descriptions Language DDL, is available. By means of this standardized language, the necessary information about the functionality of a particular field device can be made available to other bus subscribers, in particular to the control system or a further operating device (handheld). As a rule, the device descriptions are generated by the field device manufacturer and delivered with the respective field device eg by floppy disk.
p0007When the field device is put into operation, the corresponding device description is then installed from the application program.
p0008The problem here is that device descriptions are partly updated by the manufacturer. The current device descriptions (updates) must then be sent to the corresponding user and then installed manually by means of the application program.
p0009This method does not ensure that the user has the current device description in use. Particularly in the case of safety-relevant process applications, it is absolutely necessary that the user has the latest device description, especially when programming errors (bugfixing) have occurred in a device description version.
p0010The object of the present invention is to provide a method for updating device descriptions for field devices in the process automation system, which does not have the above-mentioned disadvantages, which in particular enable a simpler and secure updating.
p0011This object is achieved by the method specified in claim 1.
p0012The essential idea of the invention is to spell device descriptions for field devices on a central server, and that an application program in a control unit, which requires corresponding device information for operating a field device, loads it from the server after querying the device type of the field device.
p0013Advantageous further developments of the invention are given in the subclaims.
p0014The invention is explained in more detail below with reference to an exemplary embodiment shown in the drawing. Show it:<ul><li>1 shows a process automation system in schematic representation.</li></ul>
p00151 is a process automation system with a plurality of field devices F1, F2, F3, which are connected to a company network via a data bus and a gateurray G. FIG. The folding devices F1, F2, F3 can be, for example, pressure meters, temperature meters or flow meters, etc. In addition to the field devices, a remote IO is also connected to the data bus. HART® field devices can be connected to the data bus D via the remote IO. The data bus D can, for example, be a Foundation Fieldbus® H1 bus, the company network F in the printed copy<patcit id="pcit0001" dnum="US20020004370A1"><text>US 2002/0004370 A1</text></patcit> A field device of the process automation technology is described in which a control device for the field device is provided as a separate portable unit. The field device and the control device communicate via a radio link. Software changes of the software of the field device can be loaded by the control device via the Internet and then transmitted to the field device.
p0016The print <patcit id="pcit0002" dnum="WO0239638A2"><text>WO 02/39638 A2</text></patcit> Describes a method in which several computer units connected to the Internet form a user group, and each user releases specific data on his computer unit for access by other users.
p0017In the printings <patcit id="pcit0003" dnum="US6047222A"><text>US 6,047,222</text></patcit> and <patcit id="pcit0004" dnum="DE10029448A1"><text>DE 100 29 448 A1</text></patcit> Field bus systems are described in which at least one field device is connected to at least one control unit via a communication link. The print<patcit id="pcit0005" dnum="EP0989713A2"><text>EP 0 989 713 A2</text></patcit> Relates to a method for updating Internet access devices.
p0018Works according to the Ethernet standard (TCP / IP protocol). Two computers (eg workstations or PCs) PC1 and PC2, which are used for controlling, engineering or monitoring the process plant, are connected to the company network F as control units. Furthermore, the company network F is connected to a firewall IS, which communicates with a remote server S via the Internet I.
p0019The method according to the invention is explained in more detail below. If, for example, a special application, eg for operating, configuring, parameterizing or diagnosing a field device F1, F2, F3, which requires device descriptions (device descriptions) for field devices, is sent to a control unit, eg PC1, Application program sends a request to the field device to be operated, eg F1, and asks the device type of this field device. If the application program in the control unit does not have the required information for this particular field device F1 or not in the current version, the necessary device descriptions are downloaded via the Internet from the server S on which the most recent device descriptions are stored.
p0020This means that the latest device information is always available in the application program. In order to avoid unnecessary data transfer, the current device information is only loaded by the server S when the device information stored in the control unit PC1 differs from the memory information stored in the field device F1. This is the case, in particular, during the commissioning of the field device since, at this time, no information about this field device is yet stored in the control unit PC1.
p0021Because device descriptions can change over time due to updates and bug fixes, the application program periodically sends requests to the server S to see if changed device descriptions are available.
p0022In a simple manner, the connection between the control unit PC1 or PC2 and the server S is made via the Internet I via the firewall IS.
p0023The connection between control unit PC1 and field device F1 is effected via a data bus D. The display and operating program of the company,
p0024Endress + Hauser CommuWin II® permits a graphical device parameterisation which provides device diagnostics with error code and text explanation as well as the device operation. Device Descriptions DDs are required as device descriptions for this application.
p0025Advantageously, therefore, the device descriptions are device descriptions DD to the field devices F1, F2, F3
p0026Since it is not only possible to change device descriptions over time, but also firmware for specific field devices, it is also useful to load the current firmware from server S.
p0027By requesting the application program to the server S, specific information from different field devices and different field device users is transmitted to the server S. These can be temporarily stored in the server S for statistical purposes. It is certainly very advantageous for the user if the updated device description or the current firmware is installed automatically.
p0028A further advantage of the method according to the invention is that preconfigured device descriptions for special applications of a field device are stored in the server S and, after corresponding selection, are loaded by the user from the application program. This makes the parameterization of field devices considerably easier. In part, application programs (eg ToF-Tool® by Endress + Hauser) also use the corresponding country language.
p0029In a simple way, the device descriptions are stored in the respective country language. This provides the user with the required information in his country language and translates errors easily.
p0030By means of the method according to the invention, it is ensured that the most recent device descriptions are always available to an application program.
1 sheet
Sheet 1
Every citation, both ways
| Document | Relation | Office |
|---|---|---|
| EP0989713A | Cites | European Patent Office (EPO) |
| WO0239638A | Cites | World Intellectual Property Organization (WIPO) |
| DE10029448A | Cites | Germany |
| US6047222A | Cites | United States of America |
| US2002004370A1 | Cites | United States of America |
10 members in 5 offices
Priority claims3
| Document | Office | Kind | Date |
|---|---|---|---|
| 10234304 | Germany | – | |
| 10234304 | Germany | A | |
| 0307839 | European Patent Office (EPO) | W |
Members10
| Document | Office | Kind | |
|---|---|---|---|
| WO2004013712A1 | World Intellectual Property Organization (WIPO) | A1 | |
| DE10234304A1 | Germany | A1 | |
| AU2003254379A1 | Australia | A1 | |
| EP1525518A1 | European Patent Office (EPO) | A1 | |
| US2006120316A1 | United States of America | A1 | |
| US8250174B2 | United States of America | B2 | |
| US2012284377A1 | United States of America | A1 | |
| EP1525518B1This record | European Patent Office (EPO) | B1 | |
| US9106532B2 | United States of America | B2 | |
| EP1525518B9 | European Patent Office (EPO) | B9 |
83 legal events, as 9 offices reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | Office | |
|---|---|---|---|
| Revocation of the patentMA03 | MA03 | AT | |
| Patent revokedRevoked27W | 27W | EP | |
| Gb: patent revoked under art. 102 of the ep convention designating the uk as contracting stateRevokedGBPR | GBPR | EP | |
| Revoked following oppositionRevokedMGE | MGE | FI | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Patent revokedRevokedORIGINAL CODE: 0009271RDAG | RDAG | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: PATENT REVOKEDSTAA | STAA | EP | |
| Communication despatched that patent is revokedRevokedORIGINAL CODE: EPIDOSNREV1RDAF | RDAF | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Appeal procedure closedAppealORIGINAL CODE: EPIDOSNNOA9OAPBU | APBU | EP | |
| Epo's revocation decision now finalR064 | R064 | DE | |
| Patent revoked by epoRevokedR103 | R103 | DE | |
| Fee paymentPLFP | PLFP | FR | |
| Party data changed (patent owner data changed or rights of a patent transferred)RAP2 | RAP2 | EP | |
| Change of applicant/patenteeR081 | R081 | DE | |
| Fee paymentPLFP | PLFP | FR | |
| Date of receipt of statement of grounds of appeal recordedAppealORIGINAL CODE: EPIDOSNNOA3OAPBQ | APBQ | EP | |
| Date of receipt of statement of grounds of appeal recordedAppealORIGINAL CODE: EPIDOSNNOA3OAPBQ | APBQ | EP | |
| Appeal reference recordedAppealORIGINAL CODE: EPIDOSNREFNOAPBM | APBM | EP | |
| Date of receipt of notice of appeal recordedAppealORIGINAL CODE: EPIDOSNNOA2OAPBP | APBP | EP | |
| Appeal reference modifiedAppealORIGINAL CODE: EPIDOSCREFNOAPAH | APAH | EP | |
| Appeal reference recordedAppealORIGINAL CODE: EPIDOSNREFNOAPBM | APBM | EP | |
| Date of receipt of notice of appeal recordedAppealORIGINAL CODE: EPIDOSNNOA2OAPBP | APBP | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Fee paymentPLFP | PLFP | FR | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapse because of not paying annual feesLapsedMM01 | MM01 | AT | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Patent lapsedLapsedMM4A | MM4A | IE | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Patent ceasedCeasedPL | PL | CH | |
| Reply of patent proprietor to notice(s) of opposition receivedOppositionORIGINAL CODE: EPIDOSNOBS3PLBB | PLBB | EP | |
| Information modified related to communication of a notice of opposition and request to file observations + time limitOppositionORIGINAL CODE: EPIDOSCOBS2PLAF | PLAF | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Opposition filed against patentOppositionR026 | R026 | DE | |
| Notice of opposition and request to file observation + time limit sentOppositionORIGINAL CODE: EPIDOSNOBS2PLAX | PLAX | EP | |
| Opposition filedOpposition26 | 26 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Opposition filedOppositionORIGINAL CODE: 0009260PLBI | PLBI | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Discontinued in the netherlands as no translation has been filedVDEP | VDEP | NL | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Discontinued in the netherlands as no translation has been filedVDEP | VDEP | NL | |
| Dpma publication of mentioned ep patent grantGrantedR096 | R096 | DE | |
| European patents granted designating irelandGrantedLANGUAGE OF EP DOCUMENT: GERMANFG4D | FG4D | IE | |
| Reference to at number (ep patent validated in austria)REF | REF | AT | |
| European patent takes effect as a national patent in ch/liEP | EP | CH | |
| Designated contracting statesAK | AK | EP | |
| European patent grantedGrantedNOT ENGLISHFG4D | FG4D | GB | |
| (expected) grantORIGINAL CODE: 0009210GRAA | GRAA | EP | |
| Grant fee paidORIGINAL CODE: EPIDOSNIGR3GRAS | GRAS | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Despatch of communication of intention to grant a patentORIGINAL CODE: EPIDOSNIGR1GRAP | GRAP | EP | |
| First examination report despatched17Q | 17Q | EP | |
| Request for extension of the european patent (deleted)DAX | DAX | EP | |
| Request for examination filed17P | 17P | EP | |
| Designated contracting statesAK | AK | EP | |
| Request for extension of the european patentAX | AX | EP | |
| Public reference made under article 153(3) epc to a published international application that has entered the european phaseORIGINAL CODE: 0009012PUAI | PUAI | EP |
Numbers
- Publication
- 1525518
- Application
- 37662236
Titles3
- German
- VERFAHREN ZUM AKTUALISIEREN VON GERÄTEBESCHREIBUNGEN FÜR FELDGERÄTE DER PROZESSAUTOMATISIERUNGSTECHNIK
- English
- METHOD FOR UPDATING DEVICE DESCRIPTIONS FOR FIELD DEVICES IN PROCESS AUTOMATION TECHNOLOGY
- French
- PROCEDE D'ACTUALISATION DE DESCRIPTIONS D'APPAREILS POUR DES APPAREILS DE TERRAIN EMPLOYES DANS L'AUTOMATISATION DE PROCESSUS
Classification
- CPC, 7
- H04L41/082
- G05B19/042
- G05B2219/23295
- G05B2219/25428
- H04L12/2812
- H04L2012/4026
- H04L41/12
- IPC, 7
- G05B19 04
- G06F9 445
- H04L29 06
- H04L12 40
- G05B19 042
- H04L12 24
- H04L12 28
Designated states27
- Contracting states, 27
- Austria
- Belgium
- Bulgaria
- Switzerland
- Cyprus
- Czechia
- Germany
- Denmark
- Estonia
- Spain
- Finland
- France
- United Kingdom
- Greece
- Hungary
- Ireland
- Italy
- Liechtenstein
- Luxembourg
- Monaco
- Netherlands (Kingdom of the)
- Portugal
- Romania
- Sweden
and 3 moreShow fewer
- Slovenia
- Slovakia
- Türkiye
