EP2828713A1 - Procédé de paramétrage d'un appareil de terrain - Google Patents

Procédé de paramétrage d'un appareil de terrain

Info

Publication number
EP2828713A1
EP2828713A1 EP13707353.2A EP13707353A EP2828713A1 EP 2828713 A1 EP2828713 A1 EP 2828713A1 EP 13707353 A EP13707353 A EP 13707353A EP 2828713 A1 EP2828713 A1 EP 2828713A1
Authority
EP
European Patent Office
Prior art keywords
field device
parameter set
field
model
replacement
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.)
Ceased
Application number
EP13707353.2A
Other languages
German (de)
English (en)
Inventor
Steffen Ochsenreither
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Endress and Hauser Process Solutions AG
Original Assignee
Endress and Hauser Process Solutions AG
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Endress and Hauser Process Solutions AG filed Critical Endress and Hauser Process Solutions AG
Publication of EP2828713A1 publication Critical patent/EP2828713A1/fr
Ceased legal-status Critical Current

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
    • G05B17/00—Systems involving the use of models or simulators of said systems
    • G05B17/02—Systems involving the use of models or simulators of said systems electric
    • 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
    • G05B19/00—Programme-control systems
    • G05B19/02—Programme-control systems electric
    • G05B19/04—Programme control other than numerical control, i.e. in sequence controllers or logic controllers
    • G05B19/042—Programme control other than numerical control, i.e. in sequence controllers or logic controllers using digital processors
    • G05B19/0426—Programming the control sequence
    • 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/25061—Configuration stored in central database
    • 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/25101—Detect connected module, load corresponding parameters, variables into module
    • 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/25428—Field device

Definitions

  • the present invention relates to a method for parameterizing a field device and to a computer program product.
  • Field devices are sensors, actuators or display and / or operator devices. Many of these devices are sold and manufactured by the applicant.
  • Such field devices are often connected to one another via a field bus and / or to a higher-level unit.
  • These higher-level units serve, for example, for process control,
  • Such a higher-level unit may, for example, be a so-called gateway which has access to the
  • a higher-level unit can also be a computer on which a
  • Operating program such as Fieldcare, for operating one or more field devices installed.
  • Parameterization is assigned, as the field device originally integrated in the bus system.
  • the replacement field device it can not always be ensured that the replacement field device can be operated with the same parameterization.
  • the parameter set originally used is not suitable for operating the new field device.
  • the present invention is therefore based on the object to simplify the exchange of field devices, especially in a so-called. Incompatible field device exchange, to ensure the functionality of the system and a
  • the object is achieved by a method for parameterizing a field device and a computer program product.
  • the object is achieved by a method for parameterizing a field device, wherein a field device via a parameterization according to a first device model and a first device model
  • Parameter set wherein in the case that the field device is replaced by a replacement field device, a second parameter set according to a second device model for parameterizing the replacement field device is transmitted to the replacement field device, wherein the second device model is derived from the first device model, and wherein the second Device model and the second parameter set from the first device model and the first parameter set.
  • the object is achieved by a method for parameterizing a field device, wherein the field device has an identifier that identifies a configuration of the field device, and a parameterization according to a first device model and a first parameter set, wherein in the case that the identifier of the field device, a second parameter set corresponding to a second device model for parameterizing the field device is transmitted to the field device, wherein the second device model is derived from the first device model, and wherein the second device model and the second parameter set of the first device model and the first parameter set differ.
  • an operating program (operating tool) is usually provided in a higher-level unit (eg. B. FieldCare from
  • the higher-level unit can be connected directly to the fieldbus to which the relevant field devices are connected, or to a higher-level communication network.
  • a field device by an operating device such as by a portable
  • the field device model can be taken from the structure and the data content of a field device.
  • the field device model can be taken from the structure and the data content of a field device.
  • individual parameters are addressed by specifying the slot and index of this parameter.
  • the assignment of slot and index to individual parameters is described, for example, in the "Device Description" (DD).
  • This parameter addressing system hereafter referred to as field device model, may differ from the device-internal parameter addressing system the parameters, depending on the affiliation to individual function blocks (eg
  • the device-internal parameter addressing system in particular the allocation of the "Blockld” and the "Parameterld" to individual
  • Parameters is determined by the manufacturer of a field device.
  • the field device model thus serves to carry out a parameterization of the field device, for example, with a first parameter set.
  • the device replacement from an old generation to a new generation of field devices is u.U. problematic.
  • the replacement field device is, for example, a field device of a newer generation, adoption of the parameters is not readily possible because the replacement field device may have differently arranged function blocks, etc., which are no longer compatible with the field device model used.
  • the first parameter set can not be used for parameterizing the replacement field device.
  • An incompatibility can occur not only in the replacement of a field device by another field device, but also, for example, in the update of the firmware of a field device.
  • a corresponding assignment is stored in a database which indicates for which changes of the identifier also a
  • the first parameter set is retrieved from the field device and stored in a first database.
  • Field device can also be repeatedly updated and retrieved from the field, so that there is always a current parameterization of the field device available. If the field device is then exchanged, for example, by a replacement field device or if the identifier of the field device changes, this first parameter set is available to generate a second parameter set according to the second device model and the replacement field device or the field device with the changed identifier corresponding to the second parameter set to parameterize.
  • the first parameter set in a first database and the mapping rules by means of which the second device model is derived from the first device model are stored in a second database, which second database is preferably physically separated from the first database.
  • a first database is available in the (only)
  • Parameter sets are stored, while in a second database the
  • Mapping rules from which the second device model is derived from the first device model are stored. For example, it is possible to retrieve only the first parameter set from the first database, for example a
  • Parameterize replacement field device whose parameterization is compatible with the field device that is to be replaced.
  • corresponding information for example in the form of the o.g. Mappings, also stored in the first database.
  • mapping rules from the second database and thus the second device model are required to parameterize the replacement field device or the field device with the changed identifier.
  • Field device and / or an identifier of the replacement field device which identifier denotes a Figuration of the replacement field device determines the mapping rules and / or the second parameter set.
  • the first parameter set and the mapping rules are retrieved from the first or second database.
  • the second parameter set and / or the second device model based on manufacturer's information from the manufacturer of the field device or the replacement field device from the first parameter set and / or the first
  • Device model determined. In the determination of the second device model from the first device model may be, for example, a mere addition to the first
  • the field device or the replacement field device are connected to a field bus, via which fieldbus the parameterization of the field device or the replacement field device is performed from a higher-level unit.
  • the first parameter set can be retrieved from the field device and / or the second parameter set can be transmitted to the field device or the replacement field device.
  • the second parameter set is transmitted from the higher-level unit to the device via the fieldbus
  • Replacement field device or field device with the changed identifier transmitted can be done automatically. For this purpose, for example, by means of the higher-level unit at regular intervals perform a corresponding query from a field bus address. This query can be used to determine whether the field device which can be addressed under this address has been replaced, ie whether it is a replacement field device or the identifier of the field device has changed.
  • the field device has a
  • Fieldbus address on and the replacement field device is provided with the same fieldbus address as the field device when it is connected to the fieldbus.
  • the fieldbus address of the replacement field device or the field device with the changed identifier can be set, for example, before connecting the field device or the replacement field device to the fieldbus. From the state of the art, for example, DIP switches have become known, via which the fieldbus address of a field device can be represented.
  • the configuration of the field device is a software and / or hardware configuration of the field device of components of the field device. Since this configuration is, for example, processed and / or reproduced in the identifier of the field device, the software version, such as, for example, can be queried by the higher-level unit
  • the field device can be determined. Furthermore, thereby also the hardware configuration of the field device, for example by appropriate
  • the device model is a field-device-internal addressing of the parameters of the field device, preferably according to a so-called slot and a so-called index, the first and the second device model differing according to this addressing. If, for example, a first slot and a first index were assigned to a parameter corresponding to the first device model, the same parameter can be assigned a second slot and a second index corresponding to the second device model, which second slot and second index are assigned to the first slot and the first index different. This association between the first slot and the second slot as well as the first index and the second index can be done using the mapping rule stored in the second database.
  • a fieldbus access unit which may be a MasterClass2, such as a gateway, serves to translate this parameterization to the fieldbus.
  • the higher-level unit in which, for example, an operating program such as Fieldcare is installed and / or executed, should carry out the assignment of the addresses, also referred to as mapping. It would also be conceivable that this mapping is then stored in the database. Thus, a mapping database could then grow over time and you would not have a mapping every time in a field device exchange o.ä. Make changes to the identifier of a fieldbus address again.
  • the identifier of the field device addressable by a fieldbus address is queried from the higher-order unit via the fieldbus, and this identifier is compared with an identifier previously fetched from this fieldbus address. This can be initiated, for example, at regular intervals or by a user input.
  • Figure 1 a schematic representation of the structure of a system of
  • FIG. 2 shows a schematic representation of a transmission of a first parameter set from a field device into a first database
  • FIG. 3 shows a schematic representation of the transmission of the first parameter set from the first database to a replacement field device
  • FIG. 4 shows a schematic representation of a transmission of a second parameter set to a replacement field device, which second parameter set was derived from the first parameter set and the first device model.
  • FIG. 1 shows a schematic representation of the topology of an installation of the
  • Automation technology which is connected via a data bus ETH, in this case an Ethernet connection and the Internet INET with a higher-level unit.
  • the fieldbus FB via which the field devices F1, F2, F3 are connected to one another, can be, for example, a PROFIBUS, a FOUNDATION fieldbus or a HART bus.
  • a so-called MasterClass 1 MC1 or MasterClass 2 MC2 are connected to the fieldbus FB.
  • the MasterClass 1 MC1 is, for example, the control unit used for the
  • the MasterClass 2 MC2 is a so-called gateway, which allows the access of the higher-level unit, not explicitly shown, to the fieldbus FB and thus the field devices F1, F2, F3.
  • the superordinate unit is a computer which is connected to the higher-level data bus ETH and the gateway MC2 and the fieldbus FB via the Internet INET.
  • the higher-level unit can be used to access the first and the second database DB1, DB2, the first database DB1 for storing at least one parameter set or several parameter sets and the second database DB2 for storing the first database
  • the first database DB1 and / or the second database DB2 may be a logical and / or a physical database.
  • the first database DB1 may be logically and / or physically separate from the second database DB2.
  • the first and second database DB1, DB2 can be part of a (single) computer or several interconnected computers.
  • the superordinate data bus ETH can, for example, be separated from the Internet by a so-called firewall FW.
  • Figure 2 shows a section of a schematic representation of a system of
  • the field device F1 has a firmware, designated by way of example with the first version number 1.00. Furthermore, the field device F1 has a serial number, designated by way of example by XX. Both the parameter set P1 and the firmware 1.00 and the serial number XX are transmitted to the higher-level unit, by means of which higher-level unit the firmware or its version number 1.00, the serial number XX and the parameter set P1 are stored in the first database DB1. The transmission of the identifier consisting of serial number XX and firmware or version number 1.00 and / or the first one
  • Parameter set P1 is carried out by the field device F1 via the field bus FB and the gateway MC2 and via the higher-level data bus ETH to the higher-level unit or to the first database DB1.
  • This transmission can, for example, take place and be repeated at a defined time interval for all the field devices F1, F2, F3 connected to the fieldbus FB or only for a part of the field devices F1, F2, F3 connected to the fieldbus FB.
  • the transmission can also be initiated, for example, manually by a user from the higher-level unit. In this way, the latest version of the configuration of one of the field devices F1, F2, F3 is always recorded in the database DB1. If, for example, it is determined that the identifier of a field device has changed in comparison with a previously determined identifier, the parameterization can be adjusted.
  • FIG. 3 shows the schematic representation of the replacement of a field device F1 by a replacement field device F1 '. In this case, it is transmitted to the replacement field device in the higher-level unit or in the first database DB1 stored first parameter set P1. This process is shown schematically in Figure 3 by an arrow. The transmission can be triggered by matching the identifier assigned to a fieldbus address. If the identifier differs from a previously stored identifier, it is determined in a second step whether the
  • Replacement field device F1 is compatible with the originally installed at the bus address field device F1. Compatibility is understood here as meaning whether the first parameter set P1 and / or the first device model are also used for operation, in particular for
  • the first parameter set P1 can therefore also be used to operate the replacement field device FT.
  • the first parameter set P1 can thus gem. the first device model to the replacement field device FT are transmitted. Since the exchange field device F1 and the replacement field device FT over the same
  • Fieldbus address a corresponding telegram or telegrams can be addressed to this fieldbus address.
  • Figure 4 shows a schematic representation of a system of
  • Replacement field device FT is exchanged. According to the embodiment in Figure 3, the identifier of the replacement field device F1 'with the identifier of the previously under the
  • the replacement field device FT has a firmware with the version number 2.00, which firmware differs from the firmware with the version number 1.00. Due to the different
  • the first parameter set P1 stored in the first database DB1 can not readily be used to parameterize the spare field device F1 '. On the contrary, it is necessary to supplement or change the first parameter set P1 and thus to generate a second parameter set P2, which is used for
  • Parameterization of the replacement field device FT can be used.
  • the parameters assigned under a specific address may change.
  • This adjustment can be made by the mapping rules stored in the second database DB2.
  • mapping rules for example, the slot and index assigned to a parameter are changed such that they point to the address under which the parameter is retrievable or stored in the field device in the newer firmware version.

Landscapes

  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Automation & Control Theory (AREA)
  • Testing And Monitoring For Control Systems (AREA)
  • Programmable Controllers (AREA)

Abstract

L'invention concerne un procédé de paramétrage d'un appareil de terrain (F1, F1'). Un appareil de terrain (F1) dispose d'un paramétrage correspondant à un premier modèle d'appareil et à un premier ensemble de paramètres (P1). Lorsque l'appareil de terrain (F1) doit être remplacé par un appareil de terrain de remplacement (F1'), un deuxième ensemble de paramètres (P2) correspondant à un deuxième modèle d'appareil et servant à paramétrer l'appareil de terrain de remplacement (F1') est transmis à l'appareil de terrain de remplacement (F1'), le deuxième modèle d'appareil étant dérivé du premier modèle. Le deuxième modèle d'appareil et le deuxième ensemble de paramètres (P2) sont différents du premier modèle d'appareil et du premier ensemble de paramètres.
EP13707353.2A 2012-03-23 2013-02-28 Procédé de paramétrage d'un appareil de terrain Ceased EP2828713A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE201210102518 DE102012102518A1 (de) 2012-03-23 2012-03-23 Verfahren zum Parametrieren eines Feldgeräts
PCT/EP2013/053983 WO2013139569A1 (fr) 2012-03-23 2013-02-28 Procédé de paramétrage d'un appareil de terrain

Publications (1)

Publication Number Publication Date
EP2828713A1 true EP2828713A1 (fr) 2015-01-28

Family

ID=47790199

Family Applications (1)

Application Number Title Priority Date Filing Date
EP13707353.2A Ceased EP2828713A1 (fr) 2012-03-23 2013-02-28 Procédé de paramétrage d'un appareil de terrain

Country Status (4)

Country Link
US (1) US20150105871A1 (fr)
EP (1) EP2828713A1 (fr)
DE (1) DE102012102518A1 (fr)
WO (1) WO2013139569A1 (fr)

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2960730A1 (fr) 2014-06-25 2015-12-30 Siemens Aktiengesellschaft Procédé destiné à la configuration d'une partie de réseau de distribution
DE102014112226A1 (de) * 2014-08-26 2016-03-03 Endress + Hauser Process Solutions Ag Verfahren zum Übertragen von Feldgerätedaten
DE102014016402B4 (de) * 2014-11-05 2022-09-15 Abb Schweiz Ag Verfahren und System zum externen Austausch oder Update eines Geräts
DE102014016819A1 (de) 2014-11-14 2016-05-19 Abb Technology Ag Verfahren und Einrichtung zur Verwaltung und Konfiguration von Feldgeräten einer Automatisierungsanlage
DE102015103727A1 (de) * 2015-03-13 2016-09-15 Phoenix Contact Gmbh & Co. Kg Projektiergerät und Verfahren zum Konfigurieren und/oder Parametrieren von Automatisierungskomponenten eines Automatisierungssystems
BE1022975B1 (nl) * 2015-04-22 2016-10-25 Texfinity PLC voor een industriële wasserijmachine en besturingssoftware daarvoor
DE102015120734A1 (de) * 2015-11-30 2017-06-01 Endress+Hauser Process Solutions Ag Verfahren und System zur Optimierung der Bedienung von zumindest einem einer Vielzahl von Feldgeräten der Automatisierungstechnik
DE102015120731A1 (de) * 2015-11-30 2017-06-01 Endress+Hauser Process Solutions Ag Verfahren und System zur Optimierung der Inbetriebnahme von zumindest einem einer Vielzahl von Feldgeräten der Automatisierungstechnik
DE102015122437A1 (de) * 2015-12-21 2017-06-22 Endress + Hauser Process Solutions Ag Energierelevante Messstelle in einer Automatisierungsanlage
DE102017005769A1 (de) * 2016-07-04 2018-01-18 Sew-Eurodrive Gmbh & Co Kg Sicherheitseinrichtung mit ortsgebundenem Schlüsselspeicher, System und Verfahren
JP6984301B2 (ja) * 2017-10-13 2021-12-17 横河電機株式会社 設定システム、設定装置、設定方法、及び設定プログラム
EP3502810B1 (fr) * 2017-12-19 2021-09-08 Bürkert Werke GmbH & Co. KG Procédé et dispositif de configuration automatique d'un appareil de champ de remplacement dans un système de commande de processus
DE102021133959A1 (de) * 2021-12-21 2023-06-22 Endress+Hauser Process Solutions Ag Verfahren zum Austausch eines Feldgeräts mit einem Ersatzfeldgerät in einer Messstelle einer Anlage der Automatisierungstechnik

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5909368A (en) * 1996-04-12 1999-06-01 Fisher-Rosemount Systems, Inc. Process control system using a process control strategy distributed among multiple control elements
US5970430A (en) * 1996-10-04 1999-10-19 Fisher Controls International, Inc. Local device and process diagnostics in a process control network having distributed control functions
WO2000070417A1 (fr) * 1999-05-17 2000-11-23 The Foxboro Company Systeme de configuration de commande de processus via des objets parametres
JP2007536634A (ja) * 2004-05-04 2007-12-13 フィッシャー−ローズマウント・システムズ・インコーポレーテッド プロセス制御システムのためのサービス指向型アーキテクチャ
DE102004040282A1 (de) * 2004-08-19 2006-03-09 Siemens Ag Parameteridentifikation für Feldgeräte in der Automatisierungstechnik
DE102007026678A1 (de) * 2007-06-08 2008-12-11 Abb Ag Verfahren zum Austausch eines defekten Feldgerätes gegen ein neues Feldgerät in einem über digitalen Feldbus kommunizierenden System, insbesondere Automatisierungssystem
DE102007028841B4 (de) * 2007-06-20 2015-10-08 Endress + Hauser Flowtec Ag Feldbuseinheit und Verfahren zur Konfiguration einer Feldbuseinheit
US20100217448A1 (en) * 2007-10-12 2010-08-26 Siemens Aktiengesellschaft Method for Configuring an Arrangement for Protecting, Controlling or Monitoring an Electrical Switch or Power Supply Gear
DE102008042919A1 (de) * 2008-10-16 2010-04-22 Endress + Hauser Flowtec Ag Feldgerät der Prozessautomatisierungstechnik
DE102008055192A1 (de) * 2008-12-30 2010-07-01 Endress + Hauser Gmbh + Co. Kg Verfahren zum Übertragen von Parameterdaten beim Hochladen und/oder Herunterladen von Parametereinstellungen zwischen Feldgeräten und/oder einer Leitstelle
DE102009028655B4 (de) 2009-08-19 2019-07-04 Endress + Hauser Process Solutions Ag Verfahren zum Austausch eines Feldgeräts der Automatisierungstechnik durch ein typengleiches Feldgerät
JP5045724B2 (ja) * 2009-10-15 2012-10-10 横河電機株式会社 機器情報設定装置
DE102010038457A1 (de) * 2010-07-27 2012-02-02 Endress + Hauser Process Solutions Ag Verfahren zur Integration eines Ersatz-Feldgerätes anstelle eines Feldgeräts in ein Feldbussystem

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
None *
See also references of WO2013139569A1 *

Also Published As

Publication number Publication date
WO2013139569A1 (fr) 2013-09-26
US20150105871A1 (en) 2015-04-16
DE102012102518A1 (de) 2013-09-26

Similar Documents

Publication Publication Date Title
EP2828713A1 (fr) Procédé de paramétrage d'un appareil de terrain
EP2591404B1 (fr) Procédé de configuration d'un dispositif de commande
DE102008019053B4 (de) Verfahren zum Betreiben einer Anlage der Prozessautomatisierungstechnik
EP2181368B1 (fr) Dispositif de programmation pour un réseau constitué de noeuds de commande et installation équipée d'un tel dispositif de programmation
DE102009045386A1 (de) Verfahren zum Betreiben eines Feldbus-Interface
DE102016124348A1 (de) System und Mikroservice zum Überwachen einer Anlage der Prozessautomatisierung
EP2789145A2 (fr) Dispositif de commande d'au moins un appareil de terrain utilisé dans le domaine de l'automatisation
DE102012105446B4 (de) Vorrichtung zur Bestimmung und/oder Überwachung einer chemischen oder physikalischen Prozessgröße in der Automatisierungstechnik
EP1472851A2 (fr) Systeme et procede pour analyser un reseau et/ou produire la topologie d'un reseau
DE102017109030A1 (de) Verfahren zum Betreiben eines Feldgeräts
EP1714197B1 (fr) Pilote pour appareils de champ de la technologie d'automatisation des processus
DE102014001462B4 (de) Feldbusmodul, Maschinensteuerung und Verfahren zur Parametrierung eines, insbesondere sicherheitsgerichteten, Feldbusmoduls
WO2012079946A1 (fr) Procédé pour intégrer au moins un appareil de terrain dans un réseau de la technique d'automatisation
DE102009046041A1 (de) Anordnung zur Bedienung von Feldgeräten in der Automatisierungstechnik mittels eines Konfigurier-/Managementsystems
DE102010040055B4 (de) System zur Kommunikation von mehreren Clients mit mehreren Feldgeräten in der Automatisierungstechnik
EP1653308B1 (fr) Procédé et dispositif pour enregistrer et mettre à disposition des informations
EP2456124A1 (fr) Ingénierie d'interface de capteur
DE102011077787A1 (de) System zum Zugriff von zumindest einem Client auf zumindest ein Feldgerät
EP3025458A1 (fr) Unité d'accès à un bus de terrain pour l'exploitation dudit bus
DE102007052031B4 (de) Verfahren zum Betreiben eines Parametrier-Gerätes
DE102007039427A1 (de) Steuerknoten für ein Netzwerk aus Steuerknoten
DE102017109029A1 (de) Anordnung, Feldbuszugriffseinheit und Verfahren zum Überwachen einer Anlage der Automatisierungstechnik
EP3679431B1 (fr) Procédé pour faire fonctionner un programme d'application à exécuter sur un appareil de commande électrique pour un système d'entraînement, appareil de commande électrique, système d'entraînement et système
WO2016102194A1 (fr) Dispositif et procédé de fonctionnement d'un appareil de terrain pourvu d'un serveur web
EP2486459A2 (fr) Procédé pour faire fonctionner une interface de bus de terrain

Legal Events

Date Code Title Description
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

17P Request for examination filed

Effective date: 20140828

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

DAX Request for extension of the european patent (deleted)
17Q First examination report despatched

Effective date: 20160310

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: ENDRESS+HAUSER PROCESS SOLUTIONS AG

REG Reference to a national code

Ref country code: DE

Ref legal event code: R003

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED

18R Application refused

Effective date: 20170915