EP3997531A1 - Feldgerät - Google Patents
FeldgerätInfo
- Publication number
- EP3997531A1 EP3997531A1 EP20736985.1A EP20736985A EP3997531A1 EP 3997531 A1 EP3997531 A1 EP 3997531A1 EP 20736985 A EP20736985 A EP 20736985A EP 3997531 A1 EP3997531 A1 EP 3997531A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- field device
- configuration
- field
- designed
- devices
- 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
- 230000006870 function Effects 0.000 claims description 19
- 238000012546 transfer Methods 0.000 claims description 4
- 238000013461 design Methods 0.000 claims description 2
- 230000008901 benefit Effects 0.000 description 8
- 238000012544 monitoring process Methods 0.000 description 4
- 238000013459 approach Methods 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 230000000295 complement effect Effects 0.000 description 2
- 230000007547 defect Effects 0.000 description 2
- 238000013467 fragmentation Methods 0.000 description 2
- 238000006062 fragmentation reaction Methods 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 238000000034 method Methods 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000002730 additional effect Effects 0.000 description 1
- 210000000988 bone and bone Anatomy 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000018109 developmental process Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012905 input function Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/38—Information transfer, e.g. on bus
- G06F13/382—Information transfer, e.g. on bus using universal interface adapter
- G06F13/385—Information transfer, e.g. on bus using universal interface adapter for adaptation of a particular data processing system to different peripheral devices
-
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3236—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions
- H04L9/3239—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/50—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using hash chains, e.g. blockchains or hash trees
-
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/16—Error detection or correction of the data by redundancy in hardware
- G06F11/1658—Data re-synchronization of a redundant component, or initial sync of replacement, additional or spare unit
Definitions
- the present invention relates to a field device or a field bus device and a system made up of several field devices that can be connected to one another.
- the object of the invention is therefore to provide a field device and a system made up of several field devices which can be connected to one another and which overcome the disadvantage of the prior art described above.
- the object is achieved by the features of the independent claims.
- Advantageous configurations are specified in the subclaims.
- the object is achieved by a field device with a storage device that stores a configuration of a further field device, the field device being designed to output the configuration to the further field device and / or to receive the configuration from the further field device.
- a field device can be a device that is designed to control and / or monitor an actuator and / or a sensor.
- the field device can have an input interface and / or an output interface.
- the field device can be designed to communicate with further field devices in or via a network.
- the field device can be designed to communicate with the further field device and / or a control or guidance system via a field bus.
- the field device can be designed to communicate with the further field device and / or a control or guidance system via a real-time data connection.
- the real-time data connection can be a real-time Ethernet connection.
- the field device can be designed to output a current or an actual state of a sensor and / or actuator connected to it to the control system.
- the field device can be designed to receive a target state of a sensor and / or actuator connected to it from the control system, to process it and to the sensor and / or actuator connected to it to spend.
- the field device can be designed to send a notification to a control system in the event of certain, possibly presettable states.
- the field device is or has a controller, in particular a programmable logic controller (PLC). Additionally or alternatively, the field device can be or have a network switch or a network switch or distributor. It is also conceivable that the field device is designed as part of a sensor or the sensor functions as a field device. This means that the sensor stores the configuration of the field device and / or of the further field device.
- PLC programmable logic controller
- the storage device can be provided in or on the field device.
- the storage device may be non-volatile memory such as read only memory (ROM), random access memory (RAM), programmable read only memory (PROM), and / or electrically erasable programmable read only -Memory (EEPROM).
- ROM read only memory
- RAM random access memory
- PROM programmable read only memory
- EEPROM electrically erasable programmable read only -Memory
- the storage device can store data and programs for controlling and / or monitoring a sensor and / or actuator.
- the storage device can be connected to a central processing unit (CPU) which is arranged in or on the field device.
- the computing unit can be connected to an input and / or output interface of the field device.
- the computing unit can be designed to load programs stored in the storage device into a main memory and to execute the programs.
- the configuration can enable a field device to start.
- the configuration can include programs for controlling and / or monitoring a sensor and / or actuator.
- the further field device can have the same configuration as the field device or a different one.
- the further field device can be designed to search for the respective configuration in a network to which it is connected if there is no configuration.
- the configuration can include an operating system.
- This solution offers the advantage, among other things, that if individual hardware modules, ie field devices, fail, a mostly lengthy and error-prone manual reconfiguration of the field device can be avoided.
- the field device has a storage device which is designed to store a configuration of a further field device.
- the field device is designed to output the stored configuration to the further field device and / or to receive the configuration from the further field device and to store the received configuration in the storage device.
- the configuration of the further field device can be stored in a blockchain.
- a blockchain is a continuously expandable list of data records or blocks that are linked to one another using cryptographic processes. Each block can have a cryptographically secure hash or scatter value of the previous block, a time stamp and / or transmission or reception data, such as from which device and / or user the configuration originates, received and / or was saved. Saving the configuration in a blockchain offers the advantages that the configuration for restoring the further field device is actually intended for this, any manipulation of the configuration is detected and it is ensured that the configuration comes from a trustworthy device, for example from the same network .
- the field device can have an interface for a monitor and / or protocol function.
- the interface for the monitor and / or protocol function can make it possible to read out the information stored in the field device.
- the monitor and / or log function can make it possible to influence the saving of the configuration, ie, for example, to set which configuration and / or which parts of the configuration are saved in the respective field device.
- the interface can therefore be read from or from the field device, which for example provide information on actions that have taken place and / or planned in relation to the distributed backup of the configuration.
- the interface can be designed so that it can be connected to a graphic user interface, for example a display device of a maintenance device.
- the information output via the interface can include from which further field device the configuration is saved, possibly also in which version, how many configurations from the further field device are saved possibly also in which version and / or when a configuration was restored.
- the field device can be designed to log this information internally.
- the interface can also include an input function so that stored information can be reset, changed and / or deleted.
- the configuration can include firmware, parameterization and / or other software.
- the firmware here can be software belonging to the flardware of the further field device, stored by the Fiersteller in a read-only memory and / or cannot be changed by the user.
- the parameterization can include input variables for programs for controlling and / or monitoring a sensor and / or actuator.
- the other software can include programs for controlling and / or monitoring a sensor and / or actuator. This enables a decentralized storage of several or all files required for the configuration of the further field device.
- a decentrally secured "object” (e.g. parameterization, programming or software) of a device does not require any special identification of what type of "object” it is, since the "object” can be identified, for example, via an overall device ID . It is also conceivable that a distinction is made according to the type of “object” so that different types of “objects” of a device can be saved. This should also be done on different devices if necessary.
- object e.g. parameterization, programming or software
- the device can be designed to store further information in addition to the configuration of the further device. Not only can the configuration or a configuration blob of the additional device be transferred, but this (r) can be divided into individual objects.
- the device and / or the further device can be based on an object structure that is stored in a device-specific database.
- the objects to be backed up can be defined or predetermined. This has the advantage that when an object model is expanded at a later date (eg new device firmware with additional properties), it is still possible to restore the objects (the old version of the device firmware). Compatibility can thus be achieved
- the field device can be designed to identify the further field device.
- the further field device can be the physical neighbor of the field device in a system with several field devices.
- the identification can take place, for example, via LLDP.
- the LLDP (Link Layer Discovery Protocol) is a manufacturer-independent Layer 2 protocol which is defined according to the IEEE 802.1AB standard and offers the possibility of exchanging information between neighboring devices.
- a software component, the so-called LLDP agent which sends information about itself at periodic intervals and receives information from neighboring devices, can be provided on the field device for this purpose.
- the information received can be stored locally on the field device in a data structure, for example in the blockchain described above.
- the field device can be designed to delete its configuration and / or the configuration of the further field device as soon as it is connected to a field device other than the further field device.
- the field device can be designed to encrypt its configuration and / or the configuration of the further field device as soon as it is connected to a field device other than the further field device. This offers the advantage that sensitive configurations that are stored on the field device cannot be read out when installed in a different environment. In this way, misuse of such information can be reliably prevented.
- the encryption can be done with a password, for example.
- the field device can be designed to delete its configuration and / or the configuration of the further field device, or to encrypt its configuration and / or the configuration of the further field device when it is connected to a field device other than the further field device when driving. If the environment is the same when such a field device is started up, the field device accepts the environment. If there has been a change in the environment, misuse of the information stored on the field device is reliably prevented
- the field device can be designed to adapt a stored configuration to the further field device.
- the field device can have stored software which, after identifying the further field device connected to it, adapts or individualizes a stored configuration to the specific requirements of the further field device connected to it.
- This also makes it possible not only to exchange identical or structurally identical field devices, but it is sufficient if the field devices are functionally interchangeable. This can mean that a device with a higher range of functions can replace a device with a lower range of functions, but also a device with a lower range of functions can be used if the currently used one has a higher range of functions but does not require it.
- the field device can be designed to output its configuration to the further field device, wherein the output of the configuration to the further field device by an operator can preferably be prevented.
- the security function in the field devices can therefore be selectively switched off, so that in particular sensitive or secret configurations cannot be copied and saved in the system at will. It is also conceivable that only a certain group of further field devices is released in order to save the configuration of the field device.
- a further field device is also provided.
- the above statements on the field device also apply to the further field device, unless this is explicitly different specified.
- the further field device is designed to interact with the field device described above, ie to be able to exchange data, such as a configuration, at least unidirectionally.
- the further field device can also be designed to output its configuration to the field device (1, 2, 3, 4) but not to receive and / or store any configurations of the field device (1, 2, 3, 4) itself.
- the further field device is designed to receive and / or store any (any) configuration from the field device (1, 2, 3, 4) in order to transfer the received configuration (itself) to its (own) adapt technical design
- the storing field device adapts the configuration to the further field device (i.e., for example, a replacement device). This can be done before the adapted configuration is sent to the further field device.
- the storing field device needs information about the properties of the original and the replacement device in order to be able to make the adjustment. An operator can enter this information for the field device, for example, and / or the field device can receive this information from the replacement device. In the latter case, it may be sufficient that the replacement device only sends information about its properties to the field device, since the field device can be designed to determine the properties of the original further field device based on the stored configuration of the original further field device.
- the second further variant offers the advantage that the securing field device can send the original configuration unchanged to the further replacement device and the replacement device independently adjusts the configuration. Because the replacement device knows its own techn. Opportunities anyway and the exchange of information described above can become obsolete.
- a system is provided with several field devices of the type described above that can be connected to one another.
- Multiple means at least two field bones.
- a configuration of one of the field devices can be stored on several further field devices. This means that even if Autarkic reconfiguration between the field devices takes place between several field devices.
- the configuration of one of the field devices can be stored in fragmented form on the several further field devices. Fragmented means that the entire configuration of the one field device is not stored on one of the multiple additional field devices, but that the configuration is stored in multiple corresponding parts on the multiple additional field devices. In other words, the configuration of the one field device is stored distributed over several field devices. This can preferably be the case when the storage capacity of an individual field device is insufficient to store the entire configuration.
- the system can have a field device functioning as a central instance, which is designed to store multiple configurations of further field devices and to output the multiple configurations for each of these.
- a field device with a high capacity compared to the other field devices, such as a high storage capacity can be used.
- the field device functioning as a central instance can have a further dedicated function in addition to its storage function.
- the field device can preferably be designed to output the configurations simultaneously, so that the system can be restarted quickly if several field devices fail.
- the field device on which the configuration of the further field device is stored can be a field device that is not directly adjacent. Directly adjacent can mean that no other field device is physically arranged between the respective field devices.
- Field devices can be directly adjacent if a direct, straight connecting line from one field device to the other does not intersect a third field device. This offers the advantage that, in the event of damage, the risk is reduced that the field device on which the configuration for restoring the further field device is stored is also affected.
- FIG. 2 schematically shows a system made up of several of the systems shown in FIG.
- each field device 1, 2 has one
- the two field devices 1, 2 are connected via a data connection 5, which can be wireless or wired.
- the first and the second field device can be of identical construction or differ from one another in terms of their size, computing power and / or computing capacity.
- the first field device 1 outputs its configuration stored in the memory 11 via the input / output interface 13, controlled by the CPU 12 by means of the data connection 5 to the second field device 2.
- the second field device 2 receives the configuration of the first field device 1 via its input / output interface 23 and stores the received configuration in its memory 21 in a blockchain controlled by the CPU 22.
- the configuration can include firmware, parameterization and / or other software.
- the second field device 2 is also designed to identify the first field device 1. This can be done, for example, based on the configuration received from the first field device 1. More precisely, the second field device 2 can be configured to determine, controlled by its CPU 22, based on the configuration received from the first field device 1, a type of the first field device 1 and to store this information together with its configuration. The second field device can also be configured to receive further information in addition to the configuration of the first field device 1 via its input / output interface 23 and to store it in its memory 21 together with the configuration of the first field device 1. For example, in addition to its configuration, the first field device 1 can transmit its identification in a system with multiple field devices described later, its position in the system and / or information about which configurations of further field devices it has stored in its memory 11. An operator (not shown) can read out the information stored in the memory 21 of the second field device 2 via the input / output interface 23, which also functions as an interface for a monitor and / or log function.
- the second field device 2 transmits its configuration to the first field device 1.
- This transmission can then take place simultaneously with or at the same time as the transmission from the first to the second field device 1, 2 described above, or the configurations can be exchanged sequentially between the field devices 1, 2.
- the transfer of the configurations between the field devices 1, 2 can take place periodically during operation, so that the field devices 1, 2 always have the current configuration of the respective other field device 1, 2 saved.
- the first and the second field device 1, 2 each have a safety function.
- This safety function allows the field devices 1, 2 to delete their configuration and / or the configuration of the other field device 1, 2 as soon as it is connected to a field device other than the first or second field device 1, 2.
- the field device 1, 2, as described above recognizes the field device 1, 2 to which it is currently connected. If one of the field devices 1, 2 is separated from the other field device 1, 2 in each case and introduced into a new system of field devices, it will delete the stored configurations, for example when driving by floch. Alternatively, it can also encrypt its configuration and / or the configuration of the further field device.
- the field devices 1, 2 are designed to adapt a configuration already stored in their memory 11, 21 to the respective other field device 1, 2.
- the field device 1, 2 recognizes, for example when a field device is replaced in a system with several field devices, based on the configuration transmitted by the new field device, of the type of this new field device. By means of information stored in its memory 11, 21, it adapts or adapts the stored configuration of the field device 1, 2 previously connected to it to the new field device, controlled by its CPU 12, 22.
- the field device 1, 2 can also have a further safety function. It may be possible that it is designed to receive a configuration from another field device 1, 2 but not to output its own configuration. This safety function can be designed in such a way that it can be activated selectively by an operator.
- the field device 1, 2 can also be designed so that, although it outputs its own configuration to a further field device 1, 2, it does not accept and / or store any configurations of a further field device 1, 2. This can be useful, for example, if the field device 1, 2 is located in a physically less secure area (e.g. in the open-air / outdoor area of a plant) and no sensitive configurations of other field devices 1, 2 are to be stored in this area .
- a system 6 with several, here four, field devices 1, 2, 3, 4 connected to one another is described below with reference to FIG.
- the field devices ie the first 1, the second 2, the third 3 and the fourth 4 field device, all have the configuration described above with reference to FIG.
- Each field device 1, 2, 3, 4 thus has a storage device 11, 21, 31, 41, a CPU 12, 22, 32, 42 and input / output interface 13, 23, 33, 43.
- the field devices 1, 2, 3, 4 are each connected to one another via a data connection 5, which can be wireless or wired.
- the first field device 1 is physically directly adjacent to the second field device 2.
- the second field device 2 is physically adjacent to the first and third field devices 1, 3, that is, between the first and third field devices 1, 3.
- the fourth field device 4 is arranged at a distance from the first, second and third field device 1, 2, 3, which is greater than the respective distance between the first, second and third field device 1, 2, 3.
- Each field device 1, 2, 3, 4 stores its own configuration in its memory 11, 21, 31, 41
- the configuration of the first field device 1 is also stored on both the third and fourth field device 3, 4, with either the entire configuration of the first field device 1 being stored on the third and fourth field device 1, 4 or parts that complement each other are stored on these, ie there is a fragmentation of the configuration of the first field device 1.
- the configuration of the second field device 2 is also stored on the fourth field device 4.
- the configuration of the third field device 3 is also stored on both the first and fourth field device 1, 4, with either the entire configuration of the third field device 3 being stored on the first and fourth field device 1, 4 or parts that complement each other are stored on these, ie there is a fragmentation of the configuration of the third field device 3.
- the configuration of the fourth field device 4 is only stored on the fourth field device 4 itself. Since the fourth field device 4 stores the configuration of the other three field devices 1, 2, 3, its storage device 41 is larger in relation to the storage devices 11, 21, 31 of the other three field devices 1, 2, 3. In the system 6, a configuration of the first, the second and the third field device 1, 2, 3 is stored in at least one further, here the fourth field device 4, possibly also fragmented. In the system 6, the fourth field device 4 functions as a central entity, ie several configurations of further field devices, here all further field devices 1, 2, 3, are stored on it. The fourth field device 4 is designed to output the plurality of configurations to the first, second and third field device 1, 2, 3 in the event of a defect and / or an exchange.
- the fourth field device 4 is designed to output the respective configuration to the first and the second field device 1, 2 at the same time or simultaneously so that the system 6 can be used again as quickly as possible is.
- the system 6 is constructed in such a way that the configuration of the first and the third field device 1, 3 is not stored in the second field device 2, that is to say in the respective physically directly adjacent device. Even if there is a defect in an area in which both the first and the second field device 1, 2 are arranged, for example a local fire, the configuration of the first and the second field device can be reloaded from the third, as yet undamaged field device 3 . The same applies if the first, the second and the third field device 1, 2, 3 are damaged. The respective configuration can then be loaded from the field device 4 functioning as the central instance.
- the field devices 1, 2, 3, 4 described above and the system 6 consequently offer the advantage that a production plant can be automatically restarted as quickly as possible without manual programming effort in the event of a failure of one or more field devices.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Automation & Control Theory (AREA)
- General Engineering & Computer Science (AREA)
- Health & Medical Sciences (AREA)
- Bioethics (AREA)
- General Health & Medical Sciences (AREA)
- Computer Hardware Design (AREA)
- Software Systems (AREA)
- Programmable Controllers (AREA)
- Selective Calling Equipment (AREA)
Abstract
Description
Claims
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE102019118919.5A DE102019118919A1 (de) | 2019-07-12 | 2019-07-12 | Feldgerät |
PCT/EP2020/068762 WO2021008894A1 (de) | 2019-07-12 | 2020-07-03 | Feldgerät |
Publications (1)
Publication Number | Publication Date |
---|---|
EP3997531A1 true EP3997531A1 (de) | 2022-05-18 |
Family
ID=71515146
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP20736985.1A Withdrawn EP3997531A1 (de) | 2019-07-12 | 2020-07-03 | Feldgerät |
Country Status (4)
Country | Link |
---|---|
US (1) | US20220357711A1 (de) |
EP (1) | EP3997531A1 (de) |
DE (1) | DE102019118919A1 (de) |
WO (2) | WO2021008894A1 (de) |
Family Cites Families (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8255692B2 (en) * | 2008-07-11 | 2012-08-28 | Rosemount Inc. | Method of providing secure tamper-proof acquired data from process instruments |
EP2237123A1 (de) * | 2009-03-30 | 2010-10-06 | Siemens Aktiengesellschaft | Verfahren, Vorrichtung und Computerprogramm zur dezentralen Kompatibilitätsprüfung zwischen Komponenten in einem Automatisierungssystem |
US8832236B2 (en) * | 2010-06-21 | 2014-09-09 | Fisher-Rosemount Systems, Inc. | Methods, apparatus and articles of manufacture to replace field devices in process control systems |
DE102011007571A1 (de) * | 2011-04-18 | 2012-10-18 | Siemens Aktiengesellschaft | Tamperschutzvorrichtung zum Tamperschutz eines Feldgeräts |
KR20140054158A (ko) * | 2011-08-05 | 2014-05-08 | 케이피아이티 테크놀로지스 엘티디. | 임베디드 소프트웨어 코드의 보호를 위한 시스템 |
DK2811173T4 (da) * | 2013-06-04 | 2022-01-10 | Danfoss Power Solutions Aps | Hydraulisk system og fremgangsmåde til drift af hydraulisk system |
DE102014116768A1 (de) * | 2014-11-17 | 2016-05-19 | Endress + Hauser Flowtec Ag | Verfahren zum Betreiben eines ersten und zumindest eines zweiten Feldgerätes |
DE102016215915A1 (de) * | 2016-08-24 | 2018-03-01 | Siemens Aktiengesellschaft | Sicheres Konfigurieren eines Gerätes |
US20180074521A1 (en) * | 2016-09-09 | 2018-03-15 | Wal-Mart Stores, Inc. | Geographic area monitoring systems and methods utilizing interchangeable tool systems |
GB2568368B (en) * | 2017-09-13 | 2022-08-24 | Fisher Rosemount Systems Inc | Assistant application for a modular control system |
EP3502810B1 (de) * | 2017-12-19 | 2021-09-08 | Bürkert Werke GmbH & Co. KG | Verfahren und vorrichtung zur automatischen konfiguration eines austauschfeldgeräts in einem prozessleitsystem |
US11621973B2 (en) * | 2019-07-03 | 2023-04-04 | Battelle Memorial Institute | Blockchain cybersecurity audit platform |
-
2019
- 2019-07-12 DE DE102019118919.5A patent/DE102019118919A1/de active Pending
-
2020
- 2020-07-03 WO PCT/EP2020/068762 patent/WO2021008894A1/de unknown
- 2020-07-03 US US17/624,268 patent/US20220357711A1/en active Pending
- 2020-07-03 EP EP20736985.1A patent/EP3997531A1/de not_active Withdrawn
- 2020-07-03 WO PCT/EP2020/068760 patent/WO2021008893A1/de active Application Filing
Also Published As
Publication number | Publication date |
---|---|
US20220357711A1 (en) | 2022-11-10 |
DE102019118919A1 (de) | 2021-01-14 |
WO2021008893A1 (de) | 2021-01-21 |
WO2021008894A1 (de) | 2021-01-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP3520350B1 (de) | Manipulationssicheres speichern einer prozessgrösse in einem automatisierungssystem | |
EP1906277A1 (de) | Verfahren zum Synchronisieren von zwei Steuereinrichtungen und redundant aufgebaute Automatisierungsvorrichtung | |
EP4020103B1 (de) | Verfahren und industrieanlage zum verwalten und steuern von produktionsmitteln | |
EP2233991A1 (de) | Sicherheitsgerichtetes Automatisierungssystem mit automatischer Adresswiederherstellung | |
DE102008019195A1 (de) | Verfahren zum Betreiben einer Sicherheitssteuerung und Automatisierungsnetzwerk mit einer solchen Sicherheitssteuerung | |
DE10208530A1 (de) | Betriebseinheit, Peripheriegerät und Verfahren zum Betrieb eines Peripheriegeräts | |
EP1903530B1 (de) | Anordnung mit Vakuumgerät und Verfahren zu deren Betrieb | |
EP2770382B1 (de) | Verfahren zur Inbetriebnahme eines Automatisierungssystems | |
EP3588277A1 (de) | Firmware-aktualisierungsverfahren | |
EP3997531A1 (de) | Feldgerät | |
EP2480940B1 (de) | Verfahren zum bereitstellen von sicherheitsfunktionen | |
DE10131944A1 (de) | Verfahren zur Verarbeitung von Daten | |
WO2012028366A1 (de) | Verfahren zur sicherstellung der korrekten funktionsweise einer automatisierungsanlage | |
DE10353052A1 (de) | Automatisierungsanlage mit untereinander kommunizierenden Komponenten | |
WO2016079091A1 (de) | Verfahren zum betreiben eines ersten und zumindest eines zweiten feldgerätes | |
WO2021058244A1 (de) | Konfigurationsverfahren für eine eisenbahnsignalanlage und aktualisierungssystem | |
EP4038844A1 (de) | Ein/ausgabe-station für ein feldbussystem, feldbus-koppler für die ein/ausgabe-station, sowie platzhaltermodul für die ein/ausgabe-station | |
EP3144756A1 (de) | Steuerungssystem sowie verfahren zum betrieb eines steuerungssystems mit einer realen und einer virtuellen steuerung zur reduzierung von ausfallzeiten | |
DE10259342A1 (de) | Automatisierungssystem und Verfahren zum Betrieb eines Automatisierungssystems | |
EP2350753B1 (de) | Verfahren zum erstellen einer leittechnischen einrichtung für eine industrieanlage | |
DE20314410U1 (de) | Konfigurierbare industrielle Fertigungsanlage | |
EP2416528B1 (de) | Verfahren zur Kommunikation in einem Automatisierungsnetzwerk | |
EP3118739B1 (de) | Verfahren zur durchführung eines betriebssystem-updates | |
WO2024132496A1 (de) | Verfahren zum betrieb einer produktions- oder werkzeugmaschine sowie produktions- oder werkzeugmaschine | |
EP3208982B1 (de) | Router mit separater schnittstelle zur konfiguration des routers sowie verfahren zur konfiguration eines routers |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: UNKNOWN |
|
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: 20220111 |
|
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 |
|
DAV | Request for validation of the european patent (deleted) | ||
DAX | Request for extension of the european patent (deleted) | ||
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: EXAMINATION IS IN PROGRESS |
|
17Q | First examination report despatched |
Effective date: 20230704 |
|
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: 20231115 |