DE102007063311A1 - Field device, system of process automation technology and method for reading out profile parameters of the field device - Google Patents

Abstract

A field device with one or more memory areas in which profile parameters are stored at predetermined memory positions, with a profile memory for storing copies of the profile parameters of the field device, and a processor unit which is designed to have an associated copy of the profile parameter in each case when a profile parameter changes Update profile memory (Fig. 4).

Description

The The invention relates to a field device according to the generic term of claim 1. Furthermore, the invention relates to a system the process automation technology according to the preamble of the claim 7 and a method for reading profile parameters of a field device according to the preamble of claim 19.

In Process automation technology is often used in field devices, which serve to detect and / or influence process variables. examples for such field devices are level gauges, mass flow meters, pressure and temperature measuring devices etc., as sensors, the corresponding process variables level, Record flow, pressure or temperature.

to Influence of process variables serve akturen, z. B. valves or pumps over the flow of a liquid be changed in a pipe section or the level in a container can.

When field devices In principle, all devices are called, which are used close to the process and the process-relevant information deliver or process.

A Variety of such field devices is manufactured and distributed by the company Endress + Hauser.

Separate Fieldbus segments can have a broadband Data transmission network be connected to each other and to a host computer. When starting up Such a system must have the respective device profile of each connected field device be retrieved. This takes about 30 seconds to minutes. Significant waiting times arise, especially with larger systems until the host of each connected device to operate the system required Profile parameter has received.

task The invention is the loading of device profiles in a host system to accelerate.

Is solved this object by the specified in claims 1, 7 and 19 Characteristics.

advantageous Further developments of the invention are specified in the subclaims.

The essential idea of the invention is a side of the field device Provide profile memory, stored in the copies of the profile parameters are. These profile parameters are updated by the field device every time the respective profile parameter changes. For reading the profile parameters must be the host device the profile parameters are no longer one by one as before their over Retrieve the different memory areas of the field device scattered memory locations. Instead, with a read access to the profile memory according to the invention a coherent one Data area of the profile memory read and transmitted to the host device become. Preferably, this data area comprises a plurality of profile parameters. This makes it possible read a multitude of profile parameters with a read access and the host device transferred to.

By Use of the profile memory according to the invention can dramatically reduce the time required to load the profile parameters become. Instead of polling hundreds of profile parameters one at a time, are in the inventive solution depending according to embodiment a read access or a few read accesses to the profile memory necessary to the entire device profile retrieve. This can save the time needed to load the device profile be significantly reduced. While Downloading a device profile in the solutions of the prior art took about 30 seconds to a few minutes, can the profile parameters when using the profile memory according to the invention transfer to the host within seconds become. This falls especially for larger systems of automation technology, in which the waiting times when booting the system so far made very disturbing noticeable.

following The invention is explained in more detail with reference to an embodiment shown in the drawing.

It shows:

1 : an overview of a host system;

2 : a more detailed representation of a host system;

3 a known approach to reading profile parameters;

4 a solution according to the invention for reading profile parameters;

5 a data structure of a profile memory according to the invention;

6 : an example of the use of the profile memory according to the invention;

7 an access table for the profile memory according to the invention.

1 gives an overview of a host system 1 that is a host computer 2 as well as a broadband network 3 includes, to the directly or indirectly different field devices 4 . 5 . 6 . 7 . 8th are connected. In the broadband network 3 For example, it may be a high-speed Ethernet network in accordance with the HSE (High Speed Ethernet) standard. High Speed Ethernet (HSE) provides specifications for a low-cost, high-speed, plant-wide process automation network. HSE operates at 100 Mbps and is intended for use in process automation, but also provides information integration into the production management level and management information systems.

The Using a broadband Ethernet network has the advantage that are common to building a network infrastructure Ethernet resources, such as switches, routers, connectors, wires and fiber optic media can be used.

To the broadband network 3 Different types of devices can be connected. On the one hand, it is possible for HSE field devices equipped with an HSE interface to connect directly to the broadband network 3 to join. In the field device 4 it is such a HSE field device.

A second possibility is a so-called linking device 9 via an HSE interface with the broadband network 3 connect to. A linker connects H1 fieldbus segments locally via an integrated bridge or via FDA (Field Device Access) services. The linking device 9 Provides one or more H1 interfaces for connecting a fieldbus 10 available in the Foundation Fieldbus standard. To the fieldbus 10 can use different field devices 5 . 6 be connected. An H1 interface enables a data transfer rate of 31.25 kbit / s.

The third option is an I / O gateway 11 by means of an HSE interface to the broadband network 3 be connected. While to a linking device 9 only field devices in the Foundation Fieldbus standard can be connected, allows the use of an I / O gateway 11 a coupling of field devices of other standards, in particular of Profibus field devices. For this, the Profibus field devices are connected via a Profibus 12 to corresponding I / O interfaces of the I / O gateway 11 connected and can then over the broadband network 3 with the host 2 communicate.

In 2 a more detailed view of a host system is shown. A host computer 13 communicates via a broadband network 14 , preferably via an HSE network, with one or more connected devices. To the broadband network 14 can immediately a field device equipped with a corresponding interface 15 be connected. The field device 15 includes a system management kernel (SMK) 16 , a Network Management Agent (NMA) 17 and at least one functional block application process (FBAP) 18 , In the system management kernel 16 become system parameters of the field device 15 saved. 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 , About the functional block application process 18 can be applied to the respective function blocks (FBs) of the field device 15 be accessed. For example, readings taken by a sensor 19 be detected by appropriate function blocks of the functional block application process 18 are processed.

In addition to these three functional units, the field device includes 15 an FDA (Field Device Access) agent 20 , the host computer 13 access to the system management kernel 16 , the network management agent 17 as well as the functional block application process 18 allows. The host computer 13 communicates with the FDA agent 20 in the field device 15 on the exchange of FDA (Field Device Access) messages.

To the broadband network 14 can also have a shortcut device 21 be connected. The linking device 21 includes two H1 stacks 22A and 22B , to the two H1 fieldbuses 23A and 23B can be connected. About the H1 stack 22A and the H1 fieldbus 23A become the two H1 field devices 24 and 25 to the linking device 21 connected. The two H1 field devices 26 . 27 are over the H1 stack 22B and the H1 fieldbus 236 with the linking device 21 connected. In addition, the linking device includes 21 a system management kernel 28 and a network management agent 29 , as well as an FDA agent 30 , About the FDA agent 30 may be from the host device 13 out over the H1 stacks 22A . 22B the H1 field devices are accessed. In addition, the FDA agent allowed 30 access to the system management kernel 28 as well as the network management agent 29 , The linking device 21 It is used to transfer data between HSE devices and H1 devices, and between H1 devices that are interconnected by an HSE network. The linking device 21 can be an H1 bridge 31 contain a communication between the H1 fieldbuses 23A and 23B allows.

To the broadband network 14 is also an I / O gateway device 32 connected. The I / O gateway device 32 serves to connect between the broadband network 14 and a non-Foundation Fieldbus standard fieldbus 33 manufacture. To the fieldbus 33 are the field devices 34 . 35 connected. 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 units can be accessed from the broadband network 14 from over the FDA agent 39 be accessed.

To identify the various devices connected to the host system, 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. On the host 13 For example, a configuration application can be implemented which recognizes a reporting device and sends a so-called set-assignment-info 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 to the broadband network 14 Connected device 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 containing the version numbers of all system management information bases (SMIBs), network management information bases (NMIBs), and function block 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. The device informs the host computer with the device version number 13 about changes in its configuration.

in the Represented case of a linking device the device version number the overall status of all connected H1 field devices. The Managed link device a list of the version numbers of the connected H1 field devices. Every change the live list refers to a single H1 device that added or deleted has been. The linking device is responsible for the Geräteversionsnummerjedesmal to increase, if an H1 device address added to the live list or removed from it.

When starting up the in 2 shown host system reads the host 13 from each of the connected devices a device profile comprising a plurality of profile parameters stored at different memory locations. In addition, the host reads 13 Whenever the device version number of a connected device changes, the device profile of this device is reissued. In this way, those from the host computer 13 read out device profiles are always kept up to date.

Of the Memory of a connected device is in different memory areas such as SMIB or FBAP split, and the one to a device profile belonging Profile parameters are scattered at different locations in these memory areas stored. According to the Foundation Fieldbus standard, the respective memory locations these memory areas over an OD (Object Dictionary) index structure are addressed. It is a particular profile parameter under a given OD index of a equipment stored.

Based on 3 is shown as in previous solutions of the prior art, the profile profile belonging to a profile parameters are successively read from the different memory areas. The host system includes a host computer 40 , a broadband network 41 , a linking device 42 as well as a field device 43 that via a fieldbus 44 to the linking device 42 connected. The field device 43 includes different storage areas 45 . 46 For example, a SMIB and an FBAP. The profile parameters of the field device 43 are under different OD indices in the storage areas 45 and 46 stored. On the field device 43 is an operating software 47 Installed. If there is a change in the configuration of the field device 43 comes, then the device version number 49 of the linking device 42 incremented. The changed device version number 49 becomes the host 40 with the next device message message 50 communicated. The host computer 40 then starts the device profile of the field device 43 re-read. To read out the profile parameters, a separate FMS (Fieldbus Message Specification) read request was used in the prior art for each profile parameter 51 from the host 40 to the field device 43 transmitted. The OD index of the profile parameter to be read was specified in the respective read request. In the field device 43 the corresponding profile parameter was read out of the memory position specified by OD index and to the host computer by means of an FMS read response 40 transmitted.

at this approach can the profile parameters are only read one by one, being for each profile parameter transmit a separate FMS read request and an associated read response must become. Reading a larger number of profile parameters is therefore very time consuming. For example, the loading a device profile take about half a minute or even a minute. For example, when Starting up the host system Device profiles from many field devices have to be loaded one after the other, arise at large Host systems exceptionally long load times.

4 shows an embodiment of a host system according to the invention. The host system includes a host computer 53 , a broadband network 54 to which a linking device 55 is connected, as well as a field device 56 that via a fieldbus 57 with the linking device 55 connected is. The profile parameters at different memory positions of the memory areas 58 . 59 stored.

Unlike the in 3 The solution shown comprises the field device according to the invention 56 In addition, a separate profile memory 60 , in each of which a current copy of all profile parameters is stored. The operating software 61 of the field device 56 is configured to update the profile parameters each time a profile parameter is updated in one of the memory areas 58 . 59 also the corresponding entry in the profile memory 60 to update. The use of a separate profile store 60 enables an accelerated reading of the device profile by the host computer 53 , Reading is not done as before using FMS read requests, but by uploading 62 the entire memory contents or at least of 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 accessed by one or a few read accesses from the field device 56 to the host computer 53 be transmitted. In this case, 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. In the HSE protocol could be either a specific service for reading this profile memory 60 or the standardized domain upload service could be used.

In 5 a possible data structure is shown for the profile parameters in the profile 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. First, the OD index 63 indicated the respective profile parameter. The OD index 63 For example, it can be specified as an unsigned 16-bit value. Subsequently, the data length becomes 64 of the respective profile parameter specified. An unsigned 16-bit value can also be used to specify the data length. Then follows the actual data field 65 , where the number of data bytes is determined by the previous indication of the data length.

In the following, the access method of the prior art with the in 4 shown access method can be compared using a concrete example.

Around accessing data stored under an OD index structure are to facilitate, become frequent under a predetermined OD index information about the number of stored data and provided for the occupied OD index range. In front the actual access to the data is predetermined at this OD index accessed, then using the information stored there the actual access to those in a given OD index range perform stored data objects to be able to.

• 1. der Hostrechner liest die Daten am OD-Index 700,
• 2. das Hostsystem bestimmt, dass 512 Linkobjekte beginnend beim OD-Index 46200 abgelegt sind,
• 3. Schleife: die Variable „Indexoffset" wird von 0 bis 511 hochgezählt,
• 4. das Hostsystem liest jeweils am OD-Index (46200+Indexoffset) ein Linkobjekt aus, bis die Schleife abgearbeitet ist.

In our example, it should be assumed that a 64-byte data structure is stored under the OD index 700, which indicates in which index area a number of link objects are stored and how many link objects can be found there. In this example, assume that the link objects are stored starting at OD index 46200 and that 512 link objects are stored there. In the prior art access method, these 512 link objects would have been read as follows:

• 1. the host reads the data at OD index 700,
• 2. the host system determines that 512 link objects are stored beginning with the OD index 46200,
• 3rd loop: the variable "Indexoffset" is incremented from 0 to 511,
• 4. The host system reads a link object at the OD index (46200 + index offset) until the loop is processed.

Out This example shows that when using the previous Access method 513 consecutively performed read requests necessary are to read out the 512 link objects.

In the following, it will be discussed how the readout would occur when using the profile memory according to the invention. In 6 it is shown how the data for the above example are stored in the profile memory according to the invention. First, the OD index 700 is specified, then it is stated that below this OD index 64 Data bytes are stored, and then followed by the 64 bytes of data. Subsequently, the OD indices from 46200 to 46711 are stored together with the data length (16 bytes each) stored under the OD index and the actual data bytes in the profile memory.

To read this data, the OD indices are not read out individually. Instead, the whole is in 6 shown memory contents 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.

Of the Advantage of the access method according to the invention is that instead of 513 consecutive read accesses only a read access or a few read accesses to the profile memory carried out so that reading out compared to previous solutions much faster expires. While so far for the implementation the read times in the range of about 30 seconds or even were required in the minute range, can in the process according to the invention the entire contents of the profile memory within seconds to Transfer host computer and evaluated there.

A prerequisite for the functioning of the method according to the invention is that in the profile memory 60 stored profile parameters are kept up to date. The on the field device 56 installed operating software 61 Therefore, every time you change something in the memory areas 58 and 59 stored profile parameter also the corresponding entry in the profile memory 60 correct. This requires quick access to the profile memory 60 Profile parameters stored under different OD indices. To speed up the data in profile memory associated with an OD index 60 can access an access table of the in 7 shown used type. In this access table, there is an associated memory offset for the profile memory for each OD index 60 specified. With the help of this access table it is possible to quickly access the profile parameters stored in the profile memory under a certain OD index 60 be accessed. This will be illustrated below by way of example. It should be assumed that the OD indices are stored in the profile memory as follows:
OD index 0 at position 4,
OD index 256 at position 20,
OD index 257 at position 40,
OD index 700 at position 160.

For example, if you want to update the profile parameter stored under the OD index 257, you can use the in 7 The access table shown can be determined that the corresponding entry in position 40 of the profile memory is stored. Preferably, a binary search is used to quickly find the appropriate offset position in profile memory for a given OD index 60 to find. For this purpose, the OD indices in the access table are preferably arranged in either ascending or descending order. In the actual profile memory 60 on the other hand, the entries for the various OD indices do not necessarily have to be arranged in an ordered order.

With the help of in 7 shown access table it becomes for the operating software 61 much easier, fast on the profile memory 60 stored profile parameters and keep them up to date.

Claims (21)

Field device ( 56 ), which has one or more storage areas ( 58 . 59 ) in which profile parameters are stored at predetermined memory positions, characterized by a profile memory ( 60 ) for storing copies of the profile parameters of the field device, a processor unit which is designed, each time a profile parameter is changed, an associated copy of the profile parameter in the profile memory ( 60 ) to update. field device according to claim 1, characterized in that the profile memory as more coherent Memory area is designed. field device according to claim 1 or claim 2, characterized in that the Profile store from a host device is read out. field device according to one of the claims 1 to 3, characterized in that the profile parameters in the profile memory along with associated Indexes are stored. Field device according to one of Claims 1 to 3, characterized by an access table which, for each index stored in the profile memory, contains a memory offset which indicates where an entry is stored for this index in the profile memory. field device according to claim 5, characterized in that the processor unit is designed using the access table to a specific index an associated one To find position in the profile memory under which an entry to this Index is stored. A system of process automation technology, which comprises a host device ( 53 ), a data transmission network ( 54 ), whereby the host device ( 53 ) to the data transmission network ( 54 ), a field device ( 56 ), directly or via another device ( 55 ) to the data transmission network ( 54 ), characterized in that the field device ( 53 ) a profile memory ( 60 ) for storing copies of profile parameters of the field device, the host device ( 53 ) is designed to be read-only ( 62 ) a contiguous data area of the profile memory ( 60 ) read out. System according to claim 7, characterized in that the coherent one Data area includes a variety of profile parameters. System according to claim 7 or claim 8, characterized that the host device is designed to complete the entire contents of the profile memory read in a read access. System according to claim 7 or claim 8, characterized marked that the host device is designed to the contents of the profile memory sections Read out in several read accesses. System according to one of claims 7 to 10, characterized that the field device a processor unit which is adapted to different Memory positions stored profile parameters in the profile memory to copy. System according to one of claims 7 to 11, characterized that the field device a processor unit which is adapted to each then, if a profile parameter is changed, one in profile memory updated copy of the profile parameter. System according to one of claims 7 to 12, characterized that the field device directly to the data transmission network connected. System according to one of claims 7 to 12, characterized that the field device over a Linking device or a I / O gateway to the communications network connected, wherein the host device via the linking device or the I / O gateway to the field device accesses. System according to one of claims 7 to 14, characterized that the host device is designed to the profile parameters of a field device respectively then read out if the device version number of the field device or of the linking device to the the field device connected, changes. System according to one of claims 7 to 15, characterized that it is the data transmission network is an Ethernet network, especially an HSE network. System according to one of claims 7 to 16, characterized that the host device is designed to the profile parameters stored in the profile memory read out from the profile memory with less than 5 read accesses. System according to one of claims 7 to 17, characterized that the host device is designed to the stored in the profile memory device profile by means of an "Upload Domain "command from the profile memory of the field device to the host device to load. Method for reading profile parameters of a field device ( 56 ) in a system of process automation technology, which is a host device ( 53 ), a data transmission network ( 54 ) as well as directly or via another device ( 55 ) to the data transmission network ( 54 ) connected field device ( 56 ), characterized by the following steps: updating copies of the profile parameters in a profile memory ( 60 ) on the side of the field device ( 56 ), Reading out a contiguous data area of the profile memory ( 60 ) by the host device ( 53 ). Method according to claim 19, characterized that the coherent one Data area includes a variety of profile parameters. A method according to claim 19 or claim 20 by reading the entire contents of the profile memory in one Read access by the host device.