[go: up one dir, main page]

WO2011131752A1 - Enregistrement d'informations d'historique dans un appareil de champ - Google Patents

Enregistrement d'informations d'historique dans un appareil de champ Download PDF

Info

Publication number
WO2011131752A1
WO2011131752A1 PCT/EP2011/056418 EP2011056418W WO2011131752A1 WO 2011131752 A1 WO2011131752 A1 WO 2011131752A1 EP 2011056418 W EP2011056418 W EP 2011056418W WO 2011131752 A1 WO2011131752 A1 WO 2011131752A1
Authority
WO
WIPO (PCT)
Prior art keywords
field device
change history
configuration
changes
change
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
PCT/EP2011/056418
Other languages
German (de)
English (en)
Inventor
Frank Birgel
Julien Messer
Jochen Stinus
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 WO2011131752A1 publication Critical patent/WO2011131752A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01D—MEASURING NOT SPECIALLY ADAPTED FOR A SPECIFIC VARIABLE; ARRANGEMENTS FOR MEASURING TWO OR MORE VARIABLES NOT COVERED IN A SINGLE OTHER SUBCLASS; TARIFF METERING APPARATUS; MEASURING OR TESTING NOT OTHERWISE PROVIDED FOR
    • G01D9/00—Recording measured values
    • G01D9/40—Producing one or more recordings, each recording being produced by controlling either the recording element, e.g. stylus or the recording medium, e.g. paper roll, in accordance with two or more variables
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 

Definitions

  • the invention relates to a field device according to the preamble of claim 1 and to a fieldbus system according to claim 10. Furthermore, the invention relates to a method for monitoring a change history of a field device according to the preamble of claim 12.
  • field devices are often used to detect and / or influence process variables.
  • Examples of such field devices are level gauges, mass flowmeters, pressure and temperature measuring devices, etc., which detect the corresponding process variables level, flow, pressure or temperature as sensors.
  • field devices are all devices that are used close to the process and that provide or process process-relevant information.
  • the object of the invention is to simplify the monitoring of configuration or state changes in a fieldbus system.
  • An inventive field device for connection to a fieldbus is designed to exchange data with a host computer via the fieldbus.
  • the field device includes a change history detection module that is configured to acquire predetermined configuration or state changes of the field device and store them as change history data in a change history memory.
  • the field device includes the change history memory configured to store the change history data on the configuration or state changes of the field device detected by the change history acquiring module.
  • the field device makes it possible to record the change history by the field device itself. By checking the recorded change history, predetermined standards can be observed during the production process, as defined, for example, in the foodstuffs and pharmaceutical sectors. In this way, for example, it can be judged whether or not a particular lot of a product being produced has a trustworthy quality.
  • the invention is based on the drawing shown in the drawing
  • FIG. 1 shows an overview of a fieldbus system according to the invention
  • FIG. 2 shows the structure of a field device according to the invention
  • Fig. 3 is a flowchart showing the detection of new hardware at startup
  • Fig. 4 is a flow chart showing the detection of new hardware at regular time intervals
  • Fig. 5 is a flowchart showing the detection of new software
  • Fig. 6 is a flowchart showing how parameter changes are detected and documented
  • Fig. 7 is a flowchart showing how predetermined events are detected and stored.
  • FIG. 1 shows a fieldbus system according to the invention in which configuration or status changes can be recorded on the side of the field devices in the form of a change history.
  • the fieldbus system comprises a host computer 100, which can communicate via a field bus 101 with various field devices 102, 103 connected to the fieldbus 101.
  • the fieldbus 101 may be, for example, a fieldbus according to one of the established standards Fieldbus Foundation, Profibus, HART.
  • the fieldbus 1 01 can be a field bus according to the Industrial Ethernet standards EtherNet / IP, Profinet, EtherCat, Modbus TCP, etc.
  • a device administration tool 1 04 is installed, with which a parameterization and configuration of the field devices 102, 103 connected to the fieldbus 101 can be performed. Via the device management tool 104, the parameters of these field devices can be retrieved and monitored.
  • the device management tool 104 is preferably a device management tool in accordance with the FDT (Field Device Tool) standard, for example the program "FieldCare" from Endress + Hauser
  • FDT Field Device Tool
  • driver files 105 associated with the individual field devices 102, 103 and specifying the properties of these field devices are incorporated into the device management tool 104.
  • the driver files 105 may be, for example, driver files according to the standard DTM (Device Type Manager).
  • a history functionality is respectively implemented on the side of the field devices 102, 103, which has the task of chronologically recording configuration or state changes of the field device in the form of a change history.
  • a history component 106 is provided on the side of the field device 102, which detects and documents a plurality of previously defined configuration or state changes.
  • the configuration or state changes to be tracked may be, for example, changes in the values of predefined parameters, but may also be the occurrence of predetermined events.
  • changes in the hardware configuration such as the replacement or addition of hardware modules, may also be detected by the history component 106. Changes to the software configuration, such as the complete or partial updating of the software, can also be recognized and documented by the history component 106.
  • All configuration or status changes detected by the history component 106 are written by the history component 106 into a specially provided history memory 107.
  • a timestamp indicating when the particular change has occurred is also stored.
  • the timestamps are provided by a timer 108 provided on the side of the field device 102.
  • the timer 108 is set to zero each time the field device 102 is started up.
  • the timer 108 is also implemented as a real time timer and provides timestamps in real time.
  • the history component 106 Since the history component 106 stores each configuration or status change of the field device 102 to be logged together with an associated time stamp in the history memory 107, a chronologically continuous change history builds up in the history memory 107, which provides a comprehensive overview of the information on the side of the field device 102 occurred changes and events. It is advantageous here to form the history memory 107 as a separate memory unit independent of the hardware modules of the field device 102, which is preferably fixedly mounted on the housing or on the sensor of the field device 102. This prevents the history memory 107 from also being exchanged when replacing a hardware module. By implementing the history memory 107 as a separate memory unit, the change history of the field device 102 may be recorded for extended periods of time unaffected by any changes in the hardware configuration.
  • a history component 109 is likewise provided, which is designed to recognize configuration or state changes of the field device 103.
  • the detected configuration or state changes are then stored together with a time stamp, which is provided by a timer 1 1 1, in the history memory 1 10 as a change history.
  • the change history of the respective field device 102, 103 is stored in the history memories 107, 110.
  • the host computer 100 can access the field devices 102, 103 via the fieldbus 101 and read out the history data stored in the history memories 107, 110.
  • all history data recorded by the various field devices of the fieldbus system can be merged to obtain a change history of the overall system.
  • This change history of the entire system can then be further evaluated. In particular, it is possible to check whether specified standards were adhered to in the production process, as defined, for example, in the food and pharmaceutical sector.
  • the present invention offers the possibility to record a change history across systems and then to check whether the changes to the individual Move field device configuration or state changes within the given rules. In this way, it can be judged whether or not a particular lot of a produced product has a trustworthy quality.
  • the history data recorded on the side of the respective field device can be queried and evaluated by the host computer.
  • a novel DTM module for the device management tool is preferably provided which queries the change history of the field device and provides the user with a visualization of the history data.
  • a printing function can be provided which generates and prints out necessary basic documents for the safety-related acceptance of a production process. The printed documents are then signed and filed. With such acceptance documents can be proven that a certain manufacturing process complies with the specified standards. Such acceptance documents are needed in particular for manufacturing processes in the food and pharmaceutical industries, but can also be used generally in quality management.
  • a user changes parameters of a field device, changes a configuration or installs new software on a field device, this is considered critical from a safety point of view because a faulty configuration of a field device will affect the entire manufacturing process of a food or drug can. It may therefore be useful to require a user to identify himself to the system before making any changes to the fieldbus system. It is also possible to give different user groups different access rights.
  • the user can legitimize himself either to the host computer or directly to the field device. This legitimization can be done for example by means of an electronic signature whose integrity is then checked by the respective device. It is advantageous if the signature complies with the legal requirements, ie in Germany by the signature law Paragraph 2 No.
  • the history component 106 can recognize which user made the change. In these cases, the history component 106 may store together with information about the parameter change or the software update in the history memory 107, who has caused the respective change. In this case, the change history stored in the history memory 107 also includes the identifiers of the users who have made the respective changes.
  • FIG. 2 gives an overview of the components of a field device 200 according to the invention.
  • the field device 200 comprises a processor 201, a volatile memory 202, for example a RAM, a nonvolatile memory 203, for example an EEPROM or an FRAM, and a separate history memory 204 to save the history data.
  • the history memory 204 is preferably attached to the housing or to the sensor of the field device 200.
  • field device 200 includes a timer 205 that provides timestamps for the entries in history memory 204.
  • a charging component 206 which is also referred to as a "bootloader", is stored in the nonvolatile memory 203. When the field device 200 is booted, the charging component 206 is responsible for starting the application software 207.
  • the charging component 206 is responsible for a corresponding one Request to perform by means of a so-called "flash update" a complete or partial update of the application software 207.
  • the application software 207 comprises a history component 208 which is designed to recognize a multiplicity of previously defined configuration or state changes and to document them in the history memory 204.
  • the history component 208 comprises a plurality of different modules. In the embodiment shown in FIG.
  • the history component 208 includes, for example, a power on / power off module 209 that logs the power up and power down of the field device 200, an event module 210 that detects and documents the occurrence of predetermined events, a software recognition module 21 1, which queries the current software version, and a hardware detection module 212, which queries the current hardware version.
  • the history component 208 includes a change checking module 213 that compares the current hardware or software version with the previous hardware or software version to determine if a change has occurred.
  • the history component 208 comprises a memory access module 214, which performs the accesses to the history memory 204 and stores the configuration or state changes in the history memory 204.
  • the application software 207 also includes parameter management 215.
  • the parameter management 215 monitors, for example, whether a user is authorized to change a parameter, whether range limits of a parameter are adhered to, how the individual parameters are linked to each other, in which units a specific parameter should be specified etc.
  • the parameter management 215 comprises a parameter change tracking module 216, which has the task of identifying changes to p a ra mete rts to identi fi ed. Parameter change tracking works closely with the history component 208 of the present invention to detect and document changes in the values of certain predefined parameters.
  • one or more of the following configuration or state changes can be detected and recorded: the raising and lowering of the field device 200, the occurrence of predefined events, changes to predefined parameters, changes to the software version and changes to the hardware version ,
  • the recognition and the flowchart shown in FIGS. 3 to 7 Logging the individual configuration or state changes of the field device 200 is accomplished.
  • FIG. 3 shows the procedure when the field device 200 is started up, with hardware detection being performed during startup.
  • the application software 207 is started by the loading component 206.
  • the system startup is documented by the power on / off module 209 by writing a corresponding entry to the history memory 204 along with a timestamp provided by the timer 205.
  • the hardware detection module 212 is called.
  • the hardware detection module 212 determines the type, version, and serial numbers of the hardware modules of the field device. For this purpose, the hardware detection module 212 reads out a specified memory area of the hardware modules.
  • the change checking module 213 is called and the information about the type, version and serial numbers of the hardware modules is transferred to the change checking module 213.
  • the change checking module 213 now has the task of determining whether the hardware of the field device has changed. For this purpose, the change checking module 213 checks in step 305 whether the type, version and serial numbers of the current hardware modules determined in step 303 match the stored values. If the type, version and serial number match, the hardware has not changed. In accordance with step 306, no entry needs to be written to history memory 204 in this case. If, on the other hand, the current values do not match the stored values, then the hardware has changed and an entry needs to be written to history memory 204.
  • step 307 the memory access module 214 is called, whose task is to access the history memory 204.
  • step 308 an entry concerning the new hardware is written to the history memory 204, such as the type, version and serial number of the new hardware modules, along with a timestamp provided by the timer 205.
  • Such hardware configuration entries in history memory 304 could look like the following, for example: - module M1 (module "sensor module amplifier”): output module M1 a, module M1 b installed (time stamp of switching on M1 b);
  • Module M17 (module “communication module”): Communication module M17a, module M17b installed (time stamp of switching on M17b).
  • step 400 the application software 207 calls the hardware detection module 212 at regular time intervals.
  • the hardware detection module 212 may be invoked at approximately 1 minute intervals.
  • step 401 the hardware detection module 212 determines the type, version, and serial numbers of the hardware modules by reading out a designated memory area of the hardware modules of the field device.
  • step 402 the change checking module 213 is called and the information read out about the hardware is passed to the change checking module 213.
  • the change checking module 213 checks whether the hardware of the field device has changed.
  • the change check module 213 compares the current type, version and serial numbers of the hardware modules with the stored previous values of the hardware modules. If the current values match the previous values, the hardware has not changed. In accordance with step 404, no entry needs to be written to history memory 204 in this case. On the other hand, if the current values deviate from the previous values, then the hardware configuration has changed and this is logged in history memory 204. In step 405, the memory access module 214 which accesses the history memory 204 is called. In step 406, a corresponding entry is written to history memory 204, which specifically includes the type, version, and serial number of the new hardware modules, along with a timestamp provided by timer 305.
  • Step 500 is the field device 200 in wait mode.
  • step 501 it is checked whether there is a flash request. If not, the system remains in wait mode (step 500).
  • step 502 it is checked whether the currently offered software matches the device type and the hardware modules of the field device 200. If the software does not match the hardware, step 503 will not perform the flash update. If the software offered matches the hardware, the field device enters the flash update mode in step 504.
  • step 505 the field device 200 receives, via the fieldbus interface or via the service interface, a stream of data packets containing the new software.
  • the loading component 206 ensures that the received data is stored in the volatile memory 202.
  • the software recognition module 21 1 is called.
  • the software recognition module 21 1 determines the software version of the new software based on the headers of the received data packets.
  • step 507 the change checking module 213 is called, with the version of the received software determined by the software recognition module 21 1 being transferred to the change checking module 213.
  • step 508 the change checking module 213 checks whether or not the version of the software just received matches the previous software version.
  • step 509 If the new software version matches the previous software version, it is not necessary to flash-update the non-volatile memory according to step 509. Accordingly, no entry is also written in the history memory 204. If, on the other hand, the new software version differs from the previous software version, then this change of the software is documented in the history memory 204. For this purpose, the memory access module 214 which accesses the history memory 204 is called in step 510. In step 51 1, an entry for the new software version is written in the history memory 204, which in particular comprises the version of the software as well as a time stamp made available by the timer 205. In addition, the user who initiated the software update is also noted in the relevant entry in history memory 204.
  • the actual flash update is performed in the subsequent step 512. This ensures that there will be an entry in the history memory 204 even if there are disruptions during the flash update.
  • the new software stored in the volatile memory 202 is copied to the non-volatile memory 203 where it replaces the previously used software.
  • FIG. 6 shows how a change of a parameter is detected and logged.
  • parameters are processed by the parameter manager 2 1 5.
  • the parameter change tracking module 216 detects a change in a parameter to be documented.
  • the memory access module 214 of the history component 208 is called.
  • the memory access module 214 accesses the history memory 204 and stores an entry for the parameter change in the history memory 204.
  • the entry in the history memory 204 may include the following information: the new parameter value, a parameter ID, ie an identifier that uniquely identifies the changed parameter and a timestamp provided by the timer 205.
  • the entry can also store which user initiated the parameter change.
  • some entries for parameter changes are given by way of example, as they are stored in the history memory 204:
  • parameter P1 (parameter “mass flow unit”): output value A1 a, parameter value changed to A1 b (time stamp P1 b, user A);
  • the history component 208 can be used to detect and document certain predefined events or "events".
  • the event module 210 is provided in the history component 208. In the flowchart shown in Fig. 7, the detection and logging of an event is illustrated. In step 700, the event module 210 is in the waiting position. In step 701, it is determined whether or not one of the predetermined events has occurred. A distinction is made between "incoming events"("EventAppearing”) and “Outgoing Events"("EventDisappearing").
  • Incoming events designate a transition from an inactive state to an active state
  • outgoing events designate a transition from an active state to an inactive state.
  • the event module 210 remains in the wait position (step 700). If one of the predetermined events is detected, in the next step 702, the memory access module 214, which is configured to perform accesses to the history memory 204, is called.
  • the incoming or outgoing event is written to history memory 204.
  • the event memory history entry includes an event number that uniquely identifies the event that occurred, and a timestamp that indicates when the event occurred. This timestamp is provided by the timer 205.
  • the entry may be stored whether it is an event event ("Event Appearing") or an event event (“Event Disappearing").
  • Event E1 (event “medium inhomogeneous”): output value E1 inactive, event E1 occurs (time stamp T1b);
  • Event E17 (event “Low flow rate active”): Output value E17 active, event E17 is no longer active (time stamp T17b).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Debugging And Monitoring (AREA)

Abstract

L'invention concerne un appareil de champ permettant de se raccorder à un bus de champ, l'appareil de champ étant réalisé pour échanger des données avec un ordinateur hôte par l'intermédiaire du bus de champ, l'appareil de champ comprenant un module de saisie d'historique des modifications qui est réalisé pour saisir des modifications de configuration ou d'état prédéfinies de l'appareil de champ et pour les enregistrer en tant que données d'historique de modifications dans une mémoire d'historique de modifications; et l'appareil de champ comprenant la mémoire de l'historique des modifications, qui est réalisée pour enregistrer les données de l'historique des modifications avec les modifications de configuration ou d'état de l'appareil de champ saisies par le module de saisie de l'historique des modifications.
PCT/EP2011/056418 2010-04-23 2011-04-21 Enregistrement d'informations d'historique dans un appareil de champ Ceased WO2011131752A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE102010028152.2 2010-04-23
DE102010028152.2A DE102010028152B4 (de) 2010-04-23 2010-04-23 Aufzeichnung von History-Informationen in einem Feldgerät

Publications (1)

Publication Number Publication Date
WO2011131752A1 true WO2011131752A1 (fr) 2011-10-27

Family

ID=44479373

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2011/056418 Ceased WO2011131752A1 (fr) 2010-04-23 2011-04-21 Enregistrement d'informations d'historique dans un appareil de champ

Country Status (2)

Country Link
DE (1) DE102010028152B4 (fr)
WO (1) WO2011131752A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103914033A (zh) * 2013-01-08 2014-07-09 Vega格里沙贝两合公司 监视和控制现场设备的方法和控制设备
US9489278B2 (en) 2013-03-08 2016-11-08 Krohne Messtechnik Gmbh Field device
US10503224B2 (en) 2016-06-23 2019-12-10 Krohne Messtechnik Gmbh Method for operating a flowmeter and flowmeter
US20240097992A1 (en) * 2022-09-20 2024-03-21 Servicenow, Inc. Smart Detection for Determination of Database Accuracy
US12500820B2 (en) * 2022-09-20 2025-12-16 Servicenow, Inc. Smart detection for determination of database accuracy

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102024204414A1 (de) * 2024-05-13 2025-11-13 Knick Elektronische Messgeräte GmbH & Co. KG Verfahren zum Übertragen von Ereignisdaten von einem Feldgerät an eine entfernt gelegene Recheneinrichtung, Computerprogrammprodukt, Feldgerät und System

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1003018A2 (fr) * 1998-11-18 2000-05-24 Fujitsu Limited Dispositif d' extraction de caractéristiques pour objets mobiles et méthode
WO2003058506A1 (fr) * 2001-12-28 2003-07-17 Kimberly-Clark Worldwide, Inc. Gestion de la qualite et fabrication intelligente au moyen d'etiquettes fixes et d'etiquettes amovibles intelligentes dans la fabrication de produits commandee par des evenements
WO2007039307A1 (fr) * 2005-10-05 2007-04-12 Vega Grieshaber Kg Enregistreur de donnees pour appareil de calibrage
DE102006024743A1 (de) * 2006-05-26 2007-12-06 Siemens Ag Messumformer und Bedien- und Beobachtungsgerät für einen Messumformer
US20090292662A1 (en) * 2008-05-26 2009-11-26 Kabushiki Kaisha Toshiba Time-series data analyzing apparatus, time-series data analyzing method, and computer program product
EP2138919A1 (fr) * 2008-06-27 2009-12-30 Abb Research Ltd. Dispositif de terrain sans fil et son procédé de configuration

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE10052836A1 (de) 2000-10-24 2002-05-16 Endress Hauser Gmbh Co Vorrichtung zur Bestimmung und/oder Überwachung einer Prozeßvariablen
DE10132038A1 (de) * 2001-07-03 2003-01-23 Siemens Ag Automatisierungssystem und Verfahren zur Anlagenvisualisierung
DE10203555A1 (de) * 2002-01-29 2003-08-07 Endress & Hauser Wetzer Gmbh Feldgerät
WO2006069763A1 (fr) 2004-12-23 2006-07-06 Abb Patent Gmbh Procede de configuration d'appareils de terrain

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1003018A2 (fr) * 1998-11-18 2000-05-24 Fujitsu Limited Dispositif d' extraction de caractéristiques pour objets mobiles et méthode
WO2003058506A1 (fr) * 2001-12-28 2003-07-17 Kimberly-Clark Worldwide, Inc. Gestion de la qualite et fabrication intelligente au moyen d'etiquettes fixes et d'etiquettes amovibles intelligentes dans la fabrication de produits commandee par des evenements
WO2007039307A1 (fr) * 2005-10-05 2007-04-12 Vega Grieshaber Kg Enregistreur de donnees pour appareil de calibrage
DE102006024743A1 (de) * 2006-05-26 2007-12-06 Siemens Ag Messumformer und Bedien- und Beobachtungsgerät für einen Messumformer
US20090292662A1 (en) * 2008-05-26 2009-11-26 Kabushiki Kaisha Toshiba Time-series data analyzing apparatus, time-series data analyzing method, and computer program product
EP2138919A1 (fr) * 2008-06-27 2009-12-30 Abb Research Ltd. Dispositif de terrain sans fil et son procédé de configuration

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103914033A (zh) * 2013-01-08 2014-07-09 Vega格里沙贝两合公司 监视和控制现场设备的方法和控制设备
US9489278B2 (en) 2013-03-08 2016-11-08 Krohne Messtechnik Gmbh Field device
US10503224B2 (en) 2016-06-23 2019-12-10 Krohne Messtechnik Gmbh Method for operating a flowmeter and flowmeter
US20240097992A1 (en) * 2022-09-20 2024-03-21 Servicenow, Inc. Smart Detection for Determination of Database Accuracy
US12500820B2 (en) * 2022-09-20 2025-12-16 Servicenow, Inc. Smart detection for determination of database accuracy

Also Published As

Publication number Publication date
DE102010028152A1 (de) 2011-10-27
DE102010028152B4 (de) 2019-09-19

Similar Documents

Publication Publication Date Title
DE102009045386A1 (de) Verfahren zum Betreiben eines Feldbus-Interface
DE112012007224T5 (de) System und Verfahren zur Betriebsablauf-Überwachung und/oder -Diagnose einer Fertigungsstraße einer Industrieanlage
EP3538962B1 (fr) Procédé d'analyse de dysfonctionnements dans une installation de l'automatisation de processus
DE102010028152B4 (de) Aufzeichnung von History-Informationen in einem Feldgerät
EP3732868A1 (fr) Procédé de sécurisation d'un composant d'automatisation
EP3688937B1 (fr) Structure de données pour la transmission de données d'un réseau de bus de terrain à un nuage
DE102018106514A1 (de) Speichern von gerätebezogenen Daten zu Feldgeräten in einer Cloud
EP3821306B1 (fr) Procédé de paramétrage d'un système de capteurs
EP3566102A1 (fr) Dispositif de surveillance autoconfigurable pour un système d'automatisation basé sur un réseau de communication de données industriel
WO2017102363A1 (fr) Procédé de production d'un modèle de diagnostic générique
WO2012028366A1 (fr) Procédé garantissant le mode de fonctionnement correct d'une installation d'automatisation
EP3234707A1 (fr) Procédé de vérification d'au moins un télégramme
WO2024132417A1 (fr) Procédé et système de vérification mutuelle de l'intégrité d'une pluralité d'appareils de terrain dans le domaine de l'automatisation
DE102016122051A1 (de) Verfahren und System zum Ermitteln von Diagnoseinformationen von zumindest einem Feldgerät der Prozessautomatisierung
EP2486459A2 (fr) Procédé pour faire fonctionner une interface de bus de terrain
DE102006053866A1 (de) Verfahren zum Betreiben eines nach dem Blockmodell arbeitenden modularen Feldgerätes der Automatisierungstechnik
EP3912002B1 (fr) Journal d'audit de sécurité contextuel d'un système technique
DE102023136446A1 (de) Verfahren zum Erstellen eines Geräteberichts eines Feldgeräts sowie System zum Erstellen eines Geräteberichts eines Feldgeräts
DE102014104916A1 (de) Vorrichtung zur Sicherstellung einer fehlerfreien Datenkommunikation zwischen zwei elektronischen Komponenten eines Feldgeräts der Automatisierungstechnik
DE102022134322A1 (de) Feldgerät der Automatisierungstechnik und Verfahren zum sicheren Bedienen eines Feldgeräts
DE102022203325A1 (de) Verfahren zur Überprüfung der Ausführbarkeit einer Softwareanwendung
WO2013053559A1 (fr) Procédé de transmission de données sous forme de télégramme
EP4530766A1 (fr) Procédé et système de vérification d'une fonction d'appareil de terrain
DE102018105872A1 (de) Verfahren zur Analyse einer Kommunikationsqualität
WO2024260719A1 (fr) Procédé et système pour autoriser une action d'opération envoyée d'un premier dispositif de terrain à un second dispositif de terrain

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11716524

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 11716524

Country of ref document: EP

Kind code of ref document: A1