DE102014108126A1 - FDT host as FDI UIP in generic FDI package - Google Patents

Abstract

Method for operating a field device of automation technology via an FDI server running on a computer and an FDI device package which has at least a minimal generic device description (gDD) and a user interface plugin (UIP), wherein the user interface plugin (UIP) includes an FDT host in which a Device Type Manager (DTM), which includes a device model of the field device, executable or interpretable, wherein the method for operating the field device comprises the steps of: - Importing the FDI Device Package in the FDI server ; Executing the FDI device package from the FDI server, wherein when running the minimal generic device description (gDD) is interpreted by the FDI server and provided for the operation of the field device graphical user interface (GUI) is generated, and wherein a connection to Field device is manufactured; - Starting the User Interface Package (UIP) from the graphical user interface (GUI); - Loading the Device Type Manager (DTM) into the User Interface Plugin (UIP); - Execution or interpretation of the Device Type Manager (DTM) by the FDT host of the User Interface Plugin (UIP), so that the device model of the field device described in the Device Type Manager (DTM) on the graphical user interface (GUI) for the operation of the Field device is displayed; Operating the field device via the Device Type Manager (DTM) running in the FDT host of the User Interface Plug-in from the graphical user interface (GUI).

Description

The invention relates to a method for operating a field device, a computer program and a computer program product.

In process automation technology, field devices are often used to detect and / or influence process variables. Sensors such as fill level measuring devices, flowmeters, pressure and temperature measuring devices, pH redox potential measuring devices, conductivity measuring devices, etc., which record the corresponding process variables level, flow, pressure, temperature, pH or conductivity, are used to record process variables. To influence process variables are actuators, such as valves or pumps, through which the flow of a liquid in a pipe section or the level can be changed in a container. In principle, field devices are all devices that are used close to the process and that provide or process process-relevant information. In addition to the aforementioned sensors and actuators, field devices are generally also understood as meaning those units which are connected directly to a field bus and serve to communicate with the superordinate units, such as e.g. Remote I / Os, Gateways, Linking Devices and Wireless Adapters. A large number of such field devices are manufactured and distributed by the Endress + Hauser Group.

Before commissioning and changing the function of the field device, these must be parameterized. For parameterization, in particular for reading and / or writing parameters, operating tools or operating tools are used. Such operating tools are usually implemented on a separate from the respective field device communication unit and are connected via a fieldbus or via a service interface of the field device (possibly also communicates with a manufacturer-specific protocol) with the field device in communication. But also for integrating such field devices in a control system, the field devices must be parameterized accordingly by the control system. In addition to the parameterization, diagnostics of the field devices is also possible.

For this purpose, modern field devices offer the possibility to carry out the parameterization or the diagnosis by means of a computer program, which was developed especially for the respective field device. In order to reduce the effort that has to be made to write a separate program for each field device, automation technology has brought into being the manufacturer-independent concept of FDT / DTM with the aim of requiring only one program for all field devices. FDT stands for "Field Device Tool" and standardizes the communication and configuration interface between all field devices and control systems. The FDT interface is specified for this purpose and standardizes the data exchange between the field devices, the control system and / or an asset management system. The basis of this concept is the so-called FDT frame application, which is also familiar to the person skilled in the art under the term FDT host, which is a software program which loads the Device Type Manager (short form: DTM). The Device Type Manager is in principle a driver that has all the functions, the structure, the parameters and a graphical user interface (short form: GUI) for a specific field device or possibly a device family and is supplied by the field device manufacturer. The field device can thus be parameterized by a higher-level unit, such as, for example, an operating tool or the control system, via the FDT host into which the Device Type Manager has been loaded, and / or if necessary. Perform diagnostic steps.

In addition to the technique described above, so-called device descriptions, which are familiar to the person skilled in the art under "Device Descriptions", are used to perform parameterization and / or diagnostics in field devices. These device descriptions (or device descriptions) of the field devices to be integrated are based on so-called machine description languages, such as the Electronic Device Description Language (EDDL), which is described in US Pat IEC 61804-3 standardized. EDDL is a text-based description language used to describe the field device and its functions. The description is based on syntactic and semantic specifications or rules and is similar to simple programming languages. The description thus generated in a file or multiple files is also referred to as the Electronic Device Description (EDD) file. This device description or device description is installed on a host, for example a handheld, laptop, etc., and thus allows access to all data and parameters of the corresponding field device.

In addition to the two concepts described above, the FDI specification (FDI stands for Field Device Integration) has recently been brought into being, which brings together the two described field device integration techniques FDT / DTM and DD / EDDL. This FDI Standard provides that more process control communication protocols (eg. B. Hart ^®, Foundation Fieldbus ™ and Profibus ^®) are supported, making it possible to process control systems to manage field devices using a universal tool set. This universal toolkit, known in technical terms as the FDI Device Package is, so to speak, forms the heart of the FDI specification and includes everything that a host system, consisting of a server and a client, such as a process control system, for the integration of a field device needed. Each FDI Device Package must contain a Device Description (EDD) that includes a variety of parameter definitions, context-specific view parameter structures, and automated device procedures such as calibration for a specific field device. An FDI Device Package may include user interface plug-ins, software components to support advanced device commissioning and diagnostics. Furthermore, the FDI Device Package may include user manuals and other attachments.

The concept of FDT / DTM has existed for a long time and existing FDT / DTMs exist for a large number of field devices or types in order to be able to parameterize them in FDT hosts. These existing DTMs consist of compiled program libraries and can not be converted into an FDI Device Package. Accordingly, field devices for which only one DTM is present can not be operated via an FDI host, that is to say parameterized and / or diagnosed.

It is therefore an object of the invention to propose a method with which the operation of a field device by means of a DTMs via an FDI host is possible.

The object is achieved by a method for operating, a computer program and a computer program product.

• – Importieren des FDI Device Package in den FDI-Server;
• – Ausführen des FDI Device Packages von dem FDI-Server, wobei beim Ausführen die minimale generische Device Description vom FDI-Server interpretiert wird und eine für die Bedienung des Feldgerätes vorgesehene grafische Benutzeroberfläche erzeugt wird, und wobei eine Verbindung zum Feldgerät hergestellt wird;
• – Starten des User Interface Packages von der grafischen Benutzeroberfläche aus;
• – Laden des Device Type Managers in das User Interface Plugin;
• – Ausführen bzw. Interpretieren des Device Type Managers durch den FDT-Host des User Interface Plugins, sodass das in dem Device Type Manager beschriebenen Gerätemodell des Feldgerätes auf der grafischen Benutzeroberfläche für die Bedienung des Feldgerätes dargestellt wird;
• – Bedienen des Feldgerätes über den im FDT-Host des User Interface Plugins ausgeführten Device Type Manager von der grafischen Benutzeroberfläche aus.

With regard to the method, the object is achieved according to the invention by a method for operating a field device of automation technology via a FDI server running on a computer and an FDI device package, the FDI device package having at least a minimal generic device description and a user interface plug-in in which the user interface plugin contains an FDT host in which a device type manager which contains a device model of the field device can be executed or interpreted, the method for operating the field device comprising the following steps:

• Importing the FDI Device Package into the FDI server;
• Executing the FDI device package from the FDI server, wherein upon execution the minimal generic device description is interpreted by the FDI server and a graphical user interface provided for operating the field device is generated, and wherein a connection to the field device is established;
• - Starting the user interface package from the graphical user interface;
• - Loading the Device Type Manager into the User Interface Plugin;
• - Executing or interpreting the Device Type Manager by the FDT host of the User Interface Plug-in so that the device model of the field device described in the Device Type Manager is displayed on the graphical user interface for the operation of the field device;
• - Operating the field device via the Device Type Manager running in the FDT host of the User Interface Plugin from the graphical user interface.

For the purposes of the present application, a minimum generic device description is understood to mean a device description which does not comprise a large number of parameter definitions, parameter structures for context-specific views and automated device procedures such as calibration, but only a subset, as explained in the background of the prior art including thereof. Typically, the minimal generic device description comprises only a single identification feature, such as, for example, a TAG, ie a unique identifier, by means of which the field device can be identified. Thus, minimal refers to the content of the device description and, unlike the device description known from the prior art, a minimal device description comprises only a few (typically even a single) definition and / or structures. Further generically designates that the device description for a variety of field devices from different manufacturers used or valid. In technical terms, this is called a generic device description. In contrast, a device description is said to be specific if it is usable / compatible or valid only for a manufacturer's field device or field device type.

Thus, according to the invention, an FDI device package is proposed that comprises as a main component a "DTM Host - User Interface Package" (UIP). This user interface package contains a complete FDT host or FDT frame, also called FDT frame application, in which a Device Type Manager (DTM) or various Device Type Manager for different field devices are executable. Both the DTM user interface, ie the graphical user interface, on which functions of the field device are displayed, and the business logic, which contains all functions that are not displayed on the graphical user interface, such as calculation of coefficients, become within the user interface Packages (UIPs). For a comprehensive operation of field devices, ie all on the market available field devices, is a minimal generic, that is compatible to a variety of field devices, device description provided in the FDI device package according to the invention. The DTMs supplied with the commissioning of the field devices are thus executable via the "DTM Host - User Interface Package" in an FDI host and communicate with the corresponding field device via the FDI client and the FDI server.

An advantageous embodiment provides that the Device Type Manager, which is loaded into the User Interface Plugin, comes from the computer on which the FDI server runs.

A further advantageous embodiment provides that the generic device description in the electronic device description language, according to international standards IEC 61804-3 , is written.

A further advantageous embodiment provides that the generic device description is present in tokenized form in the FDI device package. Tokenized in this context means that a decomposition of the plain text (English: Plain text) in sequences of logically related units, called tokens (English: tokens) takes place. This procedure is typically used during compilation, so that the generic device description is compiled or compiled.

With regard to the computer program, the object is achieved by a computer program, the computer program having program code for carrying out the method according to one of the previously described embodiments when the computer program is executed in a computer.

With regard to the computer program product, the object is achieved by a computer program product which can be loaded directly into the internal memory of a computer and comprises software code sections with which the method according to one of the embodiments described above is executed when the product runs on a computer.

The invention will be explained in more detail with reference to the following drawings.

It shows:

1 : schematic representation of the known from the prior art FDI technology, and

2 : an embodiment of an FDI host according to the invention.

1 shows a schematic representation of the known from the prior art FDI technology.

In FDI, a field device is represented by means of a so-called FDI device package. It replaces the previously used EDD or the previously supplied DTM. The FDI Device Package consists of several standardized components with different responsibilities, but presents itself to the user as a single file and is thus easy to distribute and install. In addition to the package content descriptive catalog and the so-called attachments (or systems) for providing device documentation or integration files (such as GSD, CFF), the FDI Device Package consists of the following components: an electronic device description (EDD), and optional on User Interface Plugin and / or optional attachments.

The following section deals with the components of an FDI Device Package. The EDD describes three logical components of the Device Package. The device description or device description (DD) shows the parameters of the device, their dependencies on each other, as well as the hierarchical structure of the device parameters. The User Interface Description (UID) allows a description of a user interface, similar to the HTML technology in the Internet world. The so-called logic of the device is implemented in the Business Logic (BL). The Business Logic (BL) ensures the data integrity of the device data and actively responds to parameter changes. Also the so-called "Nested Communication", the "translation" of communication requests into different protocols, is implemented by the Business Logic (BL).

For very complex calculations of parameter values or complex user interfaces for evaluating input data that can not be implemented using EDDL, user interface plug-ins (one or more) can be provided by the device manufacturer with the FDI Device Package. The device can therefore be described using descriptive (EDD) or programmatic means (user interface plug-in). This approach enables full scalability of device integration and device management solution, as well as the ability to service all device functions. For simplest devices, the FDI Device Package contains only the EDD. In contrast, very complex devices still contain numerous user interface plug-ins.

This FDI device package is imported into or loaded into a FDI server, thus enabling the operation of the field device F by means of an FDI host. As mentioned above, these are out The FDI Device Packages known from the prior art have been developed for a specific field device and can not be developed by converting existing or existing DTMs.

In 1 Dashed lines indicate an FDI host that includes both an FDI client and an FDI server. The FDI host may, for example, represent a configuration software for operating a field device, an asset management software which both run on a higher-level unit, a special operating tool or operating tool that runs on a laptop or a so-called hand or field communicator. In 1 indicated by the dashed lines that the FDI host is running on the parent unit.

An alternative embodiment of the FDI host may provide that the FDI server runs on a first computer and the FDI client runs on a second computer, the first computer in communication connection, for example via a fieldbus 4 , with the first computer is.

After importing or executing the FDI Device Package 5 from the FDI server 3 a graphical user interface GUI is generated and a connection, for example via a fieldbus 4 , to the corresponding field device F, the operation of this field device F via the FDI host 1 to enable.

2 schematically shows an inventive embodiment of a FDI host 1 , This FDI host 1 runs again, as in the description 1 explained, for example, on a higher unit E from. The superordinate unit E is in communication connection, for example via a fieldbus 4 , with a variety of field devices F. In the in 2 illustrated embodiment, run the FDI client 2 and FDI server 3 on a single machine. It is also conceivable how to 1 described an embodiment in which they run separately or separately from each other on different computers. The inventive FDI device package 6 includes at least a minimal generic device description gDD and a user interface plug-in UIP. It is also conceivable that the FDI Device Package 6 In addition, further user interface plug-ins UIP and "attachments", for example in the form of data sheets, GSD files (files that are held in a data format for Profibus and Profinet devices) or the like. This FDI device package according to the invention 6 becomes in a first step in the FDI server 3 imported or loaded. By using a minimal generic Device Description gDD, the FDI Device Package used is 6 usable for all field devices F, since it is compatible with every single field device F. In 2 Several field devices are shown schematically with the reference numerals Fa to Fe. Typically, the minimal generic device description gDD comprises only one identification feature, such as, for example, a TAG, that is to say a unique identifier, by means of which the field device F can be identified. Thanks to the use of a minimal generic device description gDD, the desired field device F can thus be selected and a connection made to the corresponding field device F. Also is from the FDI server 3 generates a graphical user interface GUI for the field device F to be operated. The user interface package UIP can be started from this graphical user interface GUI, wherein the user interface plugin UIP contains an FDT host in which a device type manager DTM, which contains a device model of the field device F, can be executed or interpreted. By virtue of the identification feature stored in the minimal generic device description gDD, it is then possible to select a corresponding one, ie the field device which an operator wishes to operate. After selecting the corresponding field device, that is, for example, the field device Fe, which is located at the far right in FIG 2 1, the specific Device Type Manager DTMe of this field device can be loaded into the started User Interface Package via the communication connection between the higher-order unit E and this field device Fe. Thus, a DTM associated with a specific field device, in this case the field device Fe, in this case the DTMe, is loaded into the started user interface package UIP. Since this DTM is typically already stored in the field device F at the time of delivery of the field device, and has been initialized in the already existing superordinate unit when the field device was commissioned, it is advantageous if the DTM already initialized on the higher-level unit enters the FDI server is loaded. Thus, the DTM comes from the computer, in 1 and 2 the parent device on which the FDI server is running.

Alternatively, it can also be provided that is loaded via the communication link between the parent unit E and the field device Fe, the DTM, which is stored in the delivery state of the field device in this.

However, other variants are also conceivable in which the DTM suitable for a specific field device F is loaded from a storage medium, for example a USB stick or also from a web server. Such a DTM typically consists both of a user interface, ie a graphical user interface, on which functions of the field device are displayed, as well as of a business logic 10 , which contains all functions that are not displayed in the graphical user interface, such as calculating coefficients.

After the DTM necessary for a specific field device F has been loaded into the user interface plug-in, the DTM (in the in 2 represented example, the DTMe) executed or interpreted by the FDT host located in the user interface, so that the device model of the field device Fe described in the Device Type Manager DTMe is displayed on the graphical user interface GUI of the FDI client for the operation of the field device. In this way, the device model described in the DTM is accessible to an operator on the graphical user interface of the FDI client and the operator can operate or configure the specific field device accordingly.

LIST OF REFERENCE NUMBERS

F

 field device

e

 Parent unit

DD

 Device Description or Device Description

UID

 User Interface Description

GDD

 generic device description

GUI

 Graphical user interface or graphical user interface

EDD

 Electronic Device Description

1

 FDI host

2

 FDI client

3

 FDI server

4

 fieldbus

5

 FDI Device Package according to the prior art

6

 Inventive FDI Device Package

7

 Launched User Interface Package

8th

 FDT host, which is included in the user interface package

9

 User interface or user interface of the DTM

10

 Business logic of the DTM

11

 Attachments

QUOTES INCLUDE IN THE DESCRIPTION

This list of the documents listed by the applicant has been generated automatically and is included solely for the better information of the reader. The list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions.

Cited non-patent literature

• IEC 61804-3 [0005]
• IEC 61804-3 [0014]

Claims (6)

Method for operating a field device of automation technology via an FDI server running on a computer (E) ( 3 ) and an FDI device package ( 6 ), which has at least a minimal generic device description (gDD) and a user interface plugin (UIP), wherein the user interface plugin (UIP) an FDT host ( 1 ) in which a Device Type Manager (DTM), which includes a device model of the field device (F), is executable or interpretable, wherein the method for operating the field device (F) comprises the following steps: - Importing the FDI Device Package ( 6 ) in the FDI server ( 3 ); - Execute the FDI Device Package ( 6 ) from the FDI server ( 3 ), where the minimum generic device description (gDD) from the FDI server ( 3 ) is interpreted and provided for the operation of the field device (F) graphical user interface (GUI) is generated, and wherein a connection to the field device (F) is established; - Starting the User Interface Package (UIP) from the graphical user interface (GUI); - Loading the Device Type Manager (DTM) into the User Interface Plugin (UIP); - Execution or interpretation of the Device Type Manager (DTM) by the FDT host ( 1 ) of the User Interface Plugin (UIP) so that the device model of the field device (F) described in the Device Type Manager (DTM) is displayed on the graphical user interface (GUI) for the operation of the field device (F); Operating the field device (F) via the Device Type Manager (DTM) running in the FDT host of the User Interface Plug-in (UIP) from the graphical user interface (GUI). The method of claim 1, wherein the Device Type Manager (DTM), which is loaded into the User Interface Plugin (UIP), comes from the computer on which the FDI server is running. Method according to claim 1 or 2, wherein the generic device description (gDD) is written in the electronic device description language (EDDL) according to the international standard IEC 61804-3. Method according to one or more of the preceding claims, wherein the generic Device Description (gDD) in tokenized form in the FDI Device Package ( 6 ) is present. Computer program with program code for carrying out all method steps according to one of claims 1 to 4, when the computer program is executed in a computer. A computer program product that can be loaded directly into the internal memory of a computer and includes software code portions that perform the steps of the method of any one of claims 1 to 4 when the product is run on a computer.

Images