WO2009083426A2 - Appareil de terrain, système d'automatisation et procédé permettant d'extraire des paramètres de profil de cet appareil - Google Patents

Appareil de terrain, système d'automatisation et procédé permettant d'extraire des paramètres de profil de cet appareil Download PDF

Info

Publication number
WO2009083426A2
WO2009083426A2 PCT/EP2008/067480 EP2008067480W WO2009083426A2 WO 2009083426 A2 WO2009083426 A2 WO 2009083426A2 EP 2008067480 W EP2008067480 W EP 2008067480W WO 2009083426 A2 WO2009083426 A2 WO 2009083426A2
Authority
WO
WIPO (PCT)
Prior art keywords
profile
memory
field device
read
stored
Prior art date
Application number
PCT/EP2008/067480
Other languages
German (de)
English (en)
Other versions
WO2009083426A3 (fr
Inventor
Emilio Schiavi
Original Assignee
Endress+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+Hauser Process Solutions Ag filed Critical Endress+Hauser Process Solutions Ag
Publication of WO2009083426A2 publication Critical patent/WO2009083426A2/fr
Publication of WO2009083426A3 publication Critical patent/WO2009083426A3/fr

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
    • G05B19/00—Programme-control systems
    • G05B19/02—Programme-control systems electric
    • G05B19/418—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM]
    • G05B19/4185—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM] characterised by the network communication
    • 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/23—Pc programming
    • G05B2219/23325—Transfer modified data from ram to eprom, flash after system have run several cycles
    • 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/25305—MMA, memory management, set ram and eprom part for flash memory, store state also
    • 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
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]

Definitions

  • the invention also relates to a system of process automation technology according to the preamble of claim 7 and to a method for reading out profile parameters of a field device according to the preamble of claim 19.
  • field devices are often used which serve 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.
  • Individual fieldbus segments can be connected to one another and to a host computer via a broadband data transmission network.
  • the respective device profile When starting up such a system, the respective device profile must be called up from each connected feeder. This takes about 30 seconds to minutes.
  • the object of the invention is to accelerate the loading of device profiles in a host system.
  • the essential idea of the invention is to provide a profile memory on the side of the field device in which copies of the profile parameters are stored. These profile parameters are updated by the field device each time the respective profile parameter changes.
  • the host device no longer needs to retrieve the Profi I parameters one by one on their memory locations scattered across the various memory areas of the field device.
  • a contiguous data area of the profile memory can be read out and transmitted to the host device.
  • this data area comprises a plurality of profile parameters. This makes it possible to read with a read access a variety of Profiiparameter and transfer it to the host device.
  • the time required for loading the profile parameters can be drastically reduced.
  • read access or a few read accesses to the profile memory are necessary in order to retrieve the entire device profile. This can significantly reduce the time required to load the device profile.
  • the Profi I parameters can be used when using the Profile memory according to the invention can be transmitted within seconds to the host. This is particularly important for larger systems of automation technology in which the waiting times when booting the system made very disturbing so far.
  • Fig. 1 an overbook on a host system
  • Fig. 2 a more detailed representation of a host system
  • FIG. 5 shows a data structure of a profile memory according to the invention
  • Fig. 6 a Beispie! for the use of the inventive profile memory
  • Fig. 7 an access table for the profile memory according to the invention.
  • Fig. 1 gives an overview of a host system 1, which comprises a host computer 2 and a broadband network 3, to which directly or indirectly different field devices 4, 5, 6, 7, 8 are connected.
  • the broadband network 3 may, for example, be a high-speed Ethernet network according to the HSE (High Speed Ethernet) standard.
  • High Speed Ethernet (HSE) offers
  • HSE is operated at 100 Mbps and is suitable for use in the but also serves for information integration in the production management level and in management snoming systems.
  • the advantage of using a broadband Ethernet network is that the Ethernet resources commonly used to build a network infrastructure, such as switches, routers, connectors, wires, and fiber optic media, can be used.
  • HSE field devices which are equipped with an HSE interface
  • the Feid réelle 4 is such a HSE field device.
  • a second possibility is to connect a so-called linking device 9 to the broadband network 3 via an HSE interface.
  • a linker connects H1 field segments locally via an integrated bridge or through FDA (Field Device Access) services.
  • the logic device 9 provides one or more H 1 interfaces for the attachment of a fieldbus 10 in the Foundation Fieldbus standard.
  • Various field devices 5, 6 can be connected to the fieldbus 10.
  • An H1 interface allows a data transfer rate of 31, 25 kbit / s.
  • an i / o gateway 11 can be connected to the broadband network 3 by means of an HSE interface. While only field devices in the Foundation Fieldbus standard can be connected to a logic device 9, the use of an I / O gateway 1 1 enables a coupling of field devices of other standards, in particular of Profibus field devices.
  • the Profibus field devices are connected via a Profibus 12 to corresponding I / O interfaces of the i / O gateway 1 1 and can then communicate with the host computer 2 via the broadband network 3.
  • Fig. 2 shows a more detailed view of a host system.
  • a host computer 13 communicates via a broadband network 14, preferably via an HSE network, with one or more connected devices.
  • the gadget 15 includes a system management kernel (SMK) 16, a network management agent (NMA) 17, and at least one functional block application process (FBAP) 18.
  • System parameters of the field device 15 are stored in the system management kernel 16.
  • the network management agent 17 provides access to the network management information base (NMiB) and the system management information base (SMIB) of the field device 15.
  • the functional block application process 18 can be used to access the respective functional blocks (FBs) of the field device 15. For example, measured values which are detected by a sensor 19 can be processed by corresponding function blocks of the function block application process 18.
  • the gadget 15 includes an FDA (Field Device Access) agent 20, which allows the host computer 13 access to the system management kernel 16, the network management agent 17, and the function block application process 18.
  • the host computer 13 communicates with the FDA agent 20 in the feeder 15 via the exchange of FDA (Field Device Access) messages.
  • the link device 21 comprises two H1 stacks 22A and 22B, to which two H1 feeder buses 23A and 23B can be connected.
  • the two H1 field devices 24 and 25 are connected to the logic device 21 via the HI stack 22A and the H1 field bus 23A.
  • the two H1 field devices 26, 27 are connected to the logic device 21 via the H1 stack 22B and the H1 field bus 23B.
  • the link device 21 includes a system management kernel 28 and a network management agent 29, as well as an FDA agent 30.
  • the FDA agent 30 can access the HI field devices from the host device 13 via the H1 stacks 22A, 22B be accessed.
  • the FDA agent 30 allows access to the system management kernel 28 and the network management agent 29.
  • the link device 21 is used for data transmission between HSE devices and H1 devices and between HI devices that are interconnected by an HSE network.
  • the linking device 21 may include an H1 bridge 31 that allows communication between the H1 feeder buses 23A and 23B.
  • an I / O gateway device 32 is connected to the broadband network 14.
  • the I / O gateway device 32 is used to establish a connection between the broadband network 14 and a non-Foundation Fieidbus standard corresponding fieldbus 33.
  • the field devices 34, 35 are connected to the fieldbus 33.
  • the I / O gateway device 32 includes a system management kernel 36, a network management agent 37, and a functional block application process 38. These devices can be accessed from the broadband network 14 via the FDA agent 39,
  • the attached devices send device message messages to a multicast IP address reserved for system management.
  • the device message messages are sent at regular intervals, for example every 15 seconds.
  • a configuration application can be implemented, which recognizes a reporting device and sends a so-called set-assignment information request to the device. With this set assignment info request, the registering device is prepared for participation in the network. The respective device receives, checks and acknowledges the info request and uses the information received from the configuration application to update its device message message. The device will then continue to report to the broadband network at regular intervals.
  • Each device connected to the broadband network 14 transmits in the device message message a so-called device version number to the host computer 13.
  • the device version number is determined from a list of version numbers representing the version numbers of all system management information bases (SMIBs), network management information bases (NMIBs) and function blocks. Application Processes (FBAP). All version numbers are initially set to zero. Each time a configuration parameter in the SMIB or NMIB is changed, the associated SMIB or NMIB version number is incremented by one.
  • the version number of a function block application process FBAP is incremented whenever a configuration object, such as a link object or a trend object, is changed.
  • the device version number of a device represents the aggregate state of a device and is incremented by 1 whenever a version number in the list of version numbers changes. With the device version number, the device informs the host computer 13 of changes in its configuration.
  • the device version number represents the overall status of all connected H1 drivers.
  • the link device maintains a list of the version numbers of the connected H1 field device. Each change to the live list refers to a single H 1 device that has been added or deleted.
  • the shortcut device is responsible for increasing the device version number each time a H 1 device address is added to or removed from the live list.
  • the host computer 13 When the host system shown in FIG. 2 starts up, the host computer 13 reads from each of the connected devices a device profile that includes a plurality of profile parameters stored at different memory locations. In addition, every time the device version number of a connected device changes, the host computer 13 retrieves the device profile of that device. In this way, the device profiles read out by the host computer 13 can always be kept up to date.
  • the memory of a connected device is divided into various memory areas such as SMIB or FBAP, and the profile parameters belonging to a device profile are stored scattered at different locations of these memory areas.
  • the respective memory locations of these memory areas can be defined via an OD (Object Dictionary) index structure be addressed.
  • a specific profile parameter is stored under a specific OD index of a device.
  • the host system comprises a host computer 40, a broadband network 41, a linking device 42 and a field device 43, which is connected via a field bus 44 to the linking device 42.
  • the field device 43 comprises various memory areas 45, 46, for example a SMIB and an FBAP.
  • the profile parameters of the field device 43 are stored in the memory areas 45 and 46 under different OD indices.
  • An operating software 47 is installed on the field device 43. If there is a change in the configuration of the field device 43, then the device version number 49 of the link device 42 is incremented. The changed device version number 49 is communicated to the host computer 40 with the next device message message 50.
  • Host computer 40 then begins to re-read the device profile of the feeder 43.
  • a separate FMS (Fieldbus Message Specification) read request 51 was transmitted from the host computer 40 to the field device 43 in the prior art for each profile parameter.
  • the OD index of the profile parameter to be read was specified in the respective read request.
  • the corresponding profile parameter was read from the storage position specified by the OD index and transmitted to the host computer 40 by means of an FMS read response.
  • the profile parameters can only be output one at a time, whereby a separate FMS read request and an associated read response must be transmitted for each profile parameter.
  • the reading of a larger number of profile parameters is therefore very tedious. For example, loading a device profile can take about half a minute or even a minute. For example, when booting the host system
  • the host system comprises a host computer 53, a broadband network 54, to which a linking device 55 is connected, and a field device 56, which is connected via a field bus 57 to the linking device 55.
  • the profile parameters are stored at different memory positions of the memory areas 58, 59.
  • the field device 56 further comprises a separate profile memory 60, in each of which a current copy of all the profile parameters is stored.
  • the operating software 61 of the field device 56 is designed to update the profile parameters in each case when updating a profile parameter in one of the memory areas 58, 59 and the associated entry in the profile memory 60.
  • the use of a separate profile memory 60 allows accelerated reading of the device profile by the host computer 53. The reading is not as previously using FMS read requests, but by uploading 62 of the entire memory contents or at least larger data areas of the profile memory 60 from the field device 56 to the host computer 53, In this way, the profile parameters can be transmitted from the field device 56 to the host computer 53 by one or a few read accesses.
  • a multiplicity of profile parameters can be transmitted in each transmitted data area, so that the reading out of the device profile is considerably accelerated.
  • a specific service for reading out this profile memory 60 could be specified or the standardized domain upload service could be used.
  • FIG. 5 shows a possible data structure for the profile parameters in the professional memory.
  • the profile memory includes a SMIB section for the profile parameters of the SMIB and an FBAP section for the profile parameters of the FBAP.
  • the OD index 63 of the respective profile parameter is specified.
  • the OD index 63 can be specified as an unsigned 16-bit value.
  • the data length 64 of the respective profile parameter is specified.
  • An unsigned 16-bit value can also be used to specify the data length.
  • the actual Data field 65 wherein the number of data bytes is determined by the previous indication of the data length.
  • information about the number of stored data and the occupied OD index range is often provided under a predetermined OD index. Before the actual access to the data, this predetermined OD index is accessed in order to be able to use the information stored there to actually access the data objects stored in a specific OD index area.
  • the host reads the data at the OD index 700,
  • the host system reads out a link object at the OD! Ndex (46200 + lndexoffset) until the loop has been processed.
  • FIG. 6 shows how the data for the above example are stored in the profile memory according to the invention.
  • the OD index 700 is specified, then it is indicated that 64 data bytes are stored under this OD index, and then the 64 follow data bytes.
  • the OD-indexes from 46200 to 46711 are stored together with the data length (16 bytes each) stored under the OD! Ndex and the actual data bytes in the profile memory.
  • the OD indices are not read out individually. Instead, the entire memory contents shown in Fig. 6 are transferred from the field device to the host computer with a single memory access or with a few memory accesses. Once the entire amount of data has been transferred to the host computer, the data can be interpreted by the software of the host computer exactly as before.
  • the advantage of the access method according to the invention is that, instead of 513 consecutive read accesses, only one read access or a few read accesses to the profile memory are performed, so that the readout in the
  • a prerequisite for the functioning of the method according to the invention is that the profile parameters stored in the profile memory 60 are each kept up to date.
  • the operating software 61 installed on the field device 56 therefore has to be stored at each change of one of the memory areas 58 and 59
  • Profile parameters also correct the corresponding entry in the profile memory 60. This requires quick access to those in the profile memory 60 under various OD indexes stored profile parameters.
  • an access table of the type shown in FIG. 7 can be used. In this access table, an associated memory offset for the profile memory 60 is given for each OD index. With the help of this access table can be accessed very quickly to the stored under a certain OD index profile parameters in the profile memory 60. This will be illustrated below by way of example. It should be assumed that the OD indices in the Profiis memory are stored as follows:
  • OD index 256 at position 20 OD index 257 at position 40, OD index 700 at position 160.
  • the profile parameter stored under OD index 257 is to be updated, then it can be determined from the access bar shown in FIG. 7 that the corresponding entry is stored at position 40 of the profile memory.
  • a binary search is used to quickly find the appropriate offset position in the profile memory 60 for a given OD index.
  • the OD indices in the access table are preferably arranged in either ascending or descending order.
  • the entries for the various OD indices do not necessarily have to be arranged in an ordered order.

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Manufacturing & Machinery (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Automation & Control Theory (AREA)
  • Computer And Data Communications (AREA)
  • Image Processing (AREA)

Abstract

L'invention concerne un appareil de terrain comprenant: une ou plusieurs zones de mémoire dans lesquelles sont enregistrés des paramètres de profil à des positions de mémoire prédéfinies; une mémoire de profils permettant de stocker des copies des paramètres de profil de l'appareil de terrain, et une unité centrale conçue pour mettre à jour, dans la mémoire de profils, une copie associée à un paramètre de profil, à chaque modification de ce paramètre de profil.
PCT/EP2008/067480 2007-12-28 2008-12-15 Appareil de terrain, système d'automatisation et procédé permettant d'extraire des paramètres de profil de cet appareil WO2009083426A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE102007063311A DE102007063311A1 (de) 2007-12-28 2007-12-28 Feldgerät, System der Prozessautomatisierungstechnik und Verfahren zum Auslesen von Profilparametern des Feldgeräts
DE102007063311.6 2007-12-28

Publications (2)

Publication Number Publication Date
WO2009083426A2 true WO2009083426A2 (fr) 2009-07-09
WO2009083426A3 WO2009083426A3 (fr) 2009-10-15

Family

ID=40690833

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2008/067480 WO2009083426A2 (fr) 2007-12-28 2008-12-15 Appareil de terrain, système d'automatisation et procédé permettant d'extraire des paramètres de profil de cet appareil

Country Status (2)

Country Link
DE (1) DE102007063311A1 (fr)
WO (1) WO2009083426A2 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102008038417B4 (de) * 2008-08-19 2016-08-04 Endress + Hauser Process Solutions Ag Verfahren zum Übertragen von gerätespezifischen Daten zwischen einem Feldgerät der Automatisierungstechnik und einer übergeordneten Steuereinheit

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2000077585A1 (fr) * 1999-06-11 2000-12-21 Invensys Systems, Inc. Hebergement d'egal a egal de dispositifs intelligents sur site
US20010032038A1 (en) * 1998-08-13 2001-10-18 Thomas Eiting Method for applying control data for an electronic motor vehicle control unit

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20010032038A1 (en) * 1998-08-13 2001-10-18 Thomas Eiting Method for applying control data for an electronic motor vehicle control unit
WO2000077585A1 (fr) * 1999-06-11 2000-12-21 Invensys Systems, Inc. Hebergement d'egal a egal de dispositifs intelligents sur site

Also Published As

Publication number Publication date
WO2009083426A3 (fr) 2009-10-15
DE102007063311A1 (de) 2009-07-02

Similar Documents

Publication Publication Date Title
DE102010029952B4 (de) Verfahren zum Integrieren von zumindest einem Feldgerät in ein Netzwerk der Automatisierungstechnik
DE102008019053B4 (de) Verfahren zum Betreiben einer Anlage der Prozessautomatisierungstechnik
DE102009045386A1 (de) Verfahren zum Betreiben eines Feldbus-Interface
DE112004000223T5 (de) Schnittstellenmodul zur Verwendung mit einem Modbus-Gerätenetz und Fieldbus-Gerätenetz
EP3616365A1 (fr) Procédé permettant de faire fonctionner un appareil de terrain
WO2007051837A1 (fr) Procédé d’utilisation d’un appareil de terrain de la technique d’automatisation aux fonctionnalités spéciales
WO2009047193A1 (fr) Procédé de commande d'appareils de terrain utilisés dans l'automatisation des processus au moyen d'un programme de commande indépendant des appareils
WO2009074544A1 (fr) Procédé pour faire fonctionner un système présentant un appareil de terrain et un système de commande
EP0916466B1 (fr) Machine d'injection avec connexion LAN
DE102016120972A1 (de) Bereitstellung von Informationen zu Zusatzfunktionalitäten von Feldbuskomponenten
WO2012079946A1 (fr) Procédé pour intégrer au moins un appareil de terrain dans un réseau de la technique d'automatisation
WO2010020661A1 (fr) Procédé de détermination d'une structure de données statique d'un appareil de terrain
DE102009046041A1 (de) Anordnung zur Bedienung von Feldgeräten in der Automatisierungstechnik mittels eines Konfigurier-/Managementsystems
DE10208530A1 (de) Betriebseinheit, Peripheriegerät und Verfahren zum Betrieb eines Peripheriegeräts
EP3652595B1 (fr) Procédé et système pour surveiller une installation de la technologie d'automatisation
DE102007052031B4 (de) Verfahren zum Betreiben eines Parametrier-Gerätes
DE102008042919A1 (de) Feldgerät der Prozessautomatisierungstechnik
DE102010027963A1 (de) Verfahren zum Betreiben eines Feldgerätes der Prozessautomatisierungstechnik
WO2012028366A1 (fr) Procédé garantissant le mode de fonctionnement correct d'une installation d'automatisation
WO2009083426A2 (fr) Appareil de terrain, système d'automatisation et procédé permettant d'extraire des paramètres de profil de cet appareil
DE102008043683A1 (de) Feldgerät der Prozessautomatisierungstechnik
WO2011042258A2 (fr) Procédé pour faire fonctionner une interface de bus de terrain
DE102010003741A1 (de) Verfahren zum Datenaustausch
EP1478990B1 (fr) Procede de transmission de donnees d'appareils de terrain a une base de donnees externe
DE102009046934A1 (de) Statisch und dynamisch konfigurierte Multi-Variablen-Container

Legal Events

Date Code Title Description
122 Ep: pct application non-entry in european phase

Ref document number: 08866924

Country of ref document: EP

Kind code of ref document: A2