WO2011009746A1

WO2011009746A1 - Method for data synchronization between an operator device and a configuration/management system

Info

Publication number: WO2011009746A1
Application number: PCT/EP2010/059919
Authority: WO
Inventors: Michael Maneval
Original assignee: Endress+Hauser Process Solutions Ag
Priority date: 2009-07-23
Filing date: 2010-07-09
Publication date: 2011-01-27
Also published as: DE102009027949A1

Abstract

The invention relates to a method for synchronizing the current configuration/parameterization data (18) associated with a field device (F) in process automation engineering in the form of a standardized device description (DD) with a device driver (7, DeviceDTM) which comprehensively describes the field device (F) and which is associated with a superordinate management/configuration system (1), wherein the management/configuration system (1) contains a standardized software system (FDT Frame) which allows access to the device driver (DeviceDTM), wherein the field device (F) is connected to an operator device (2) in situ in the field by means of a point-to-point connection and is configured or parameterized by means of digital communication in a bus system (3), wherein the current device-specific configuration/parameterization data from the field device (F) are stored (18) as a current DD-based data record in the operator device (2) by means of a standardized device description (11, DD), wherein the operator device (2) is subsequently connected, in temporal and spatial isolation, to the superordinate management/configuration system (1), and wherein the device driver (7, DeviceDTM) associated with the management/configuration system (1) and the current DD-based data record stored in the operator device (2) are synchronized, so that the current configuration/parameterization data (18) are available in the synchronized device driver (8, DeviceDTM').

Description

Method for data synchronization between

an operator panel and a configuration / management system

The invention relates to a method for data synchronization between an operating device and a configuration / management system.

In process as well as in factory automation technology, field devices are often used which serve to detect and / or influence process variables. To capture process variables

Measuring instruments, such as level gauges, flowmeters, pressure and temperature measuring instruments, pH meters, conductivity meters, etc., which record the respective process variables level, flow, pressure, temperature, pH or conductivity. To influence the process variables, actuators are used, such as valves or pumps, via which e.g. the flow of a liquid in a pipeline or the level of a medium in a container is changed. In principle, field devices are all devices that are used close to the process and that provide or process process-relevant information. A large number of such field devices are offered and distributed by the Endress + Hauser Group. Under the term field device used in connection with the invention, all types of measuring devices and actuators are thus to be subsumed. Furthermore, the term field device also includes e.g. a gateway, a radio adapter or other bus users integrated / integrable into a bus system.

In modern industrial plants, field devices are generally connected to at least one higher-level control unit via bus systems, such as, for example, via Profibus® PA, Foundation Fieldbus® or HART®. Normally the higher-level control unit - as already mentioned - is a control system. The higher-level control unit is used for

Process control, process visualization, process monitoring and commissioning and operation of field devices. Programs independent on higher-level configuration / management systems These include, for example, the FieldCare operating tool from the Endress + Hauser Group, the Pactware operating tool, the Fisher-Rosemount AMS operating tool or the Siemens PDM operating tool. Configuration / management systems that are integrated into control system applications are the PCS7 from Siemens, the Symphony from ABB and the Delta V from

Emerson.

The integration of field devices in configuration / management systems or in control systems takes place via device descriptions, which ensure that the systems can recognize and interpret the information provided by the field devices. The device descriptions for each field device type are provided in different applications by the respective device manufacturer. So that the field devices in different

Bus systems must be integrated, must be different

Device descriptions for the different bus systems are created. So there are - to name just a few examples - HART, Fieldbus

Foundation and Profibus device descriptions.

In order to create a uniform description for the field devices, the Fieldbus Foundation (FF), the HART Communication Foundation (HCF) and the Profibus User Organization (PNO) have created a uniform electronic device description (EDD). The EDD is defined in the standard IEC 61804-2. For a complete operation of the field devices via any configuration / management system are also special

Device descriptions, so-called DTMs - Device Type Manager or Device Manager or Device Driver - available. These DTMs comply with the FDT Field Device Tool specification (IEC 62453). The current FDT specification is available from the ZVEI or the PNO or the FDT Group. It is customary, in particular in process automation technology, to configure field devices in the field by means of a handheld device or another configuration tool, eg PC, via a point-to-point connection, eg via a modem. HART, Profibus, FF or a proprietary service protocol can be used for this point-to-point connection. The field devices are usually integrated into the control of the process plant via device descriptions, such as the standardized EDDs or DTMs. In many cases, the field devices are still two-wire devices that usually work on the 4-2OmA basis. The analog current signal representing the measured value is superimposed on a digital communication here. If changes are made in the field, they must be sent to the configuration / management system for the purpose of

Data synchronization to be forwarded. There are several ways of data synchronization between the

Field device and the configuration / management system. On the one hand, a user in the configuration / management system can trigger an upload of the data from the field device via the bus system. In EDD or DD based configuration / management systems, a manual synchronization between the HMI device and the

Configuration / management system based on the EDD information to be made. The disadvantage here is that an upload of

Device configuration can take a lot of time, which in particular has to do with the fact that the description of the field devices is becoming increasingly complex.

In general, the problem arises that the data synchronization between a handheld, which is based on a standardized device description, such as EDD, and a configuration / management system that has a standardized software system, such as the FDT frame, under which the device drivers are executable , can not be guaranteed consistent. This is because between EDD interpreters and DTMs no uniform data exchange interface is defined. The creation of an appropriate interface is possible only with great effort.

The invention is based on the object, a simple method

to suggest that the current a field device of the

Automation technology in the form of a standardized device description associated configuration / Parametherdaten with a field device fully descriptive device driver, which are assigned to a parent management / configuration system, synchronized.

The object is achieved by a method for the synchronization of current configuration data assigned to a field device of process automation technology in the form of a standardized device description with a device driver which fully describes the field device, wherein the device driver is assigned to a higher-level device driver

Management / Konfiguhersystem is assigned and where in the

Management / configuration system is provided a standardized software system that allows access to the device driver.

According to the field device, ie in the field, with a

HMI device via a point-to-point connection, e.g. by means of a

Modems, connected and configured or parameterized via digital communication of a bus system. Usually, the configuration or parameterization in the field takes place successively on a large number of field devices. The current device-specific configuration / parameterization data of the field device or the field devices are used as a current DD-based data set or as current DD-based data sets in the operating device by means of a

stored standardized device description. Then the HMI device - separated in time and space - is connected to the higher-level management / configuration system. The device driver assigned to the management / configuration system and the current DD-based data set stored in the operator panel are synchronized so that the current configuration / parameterization data are available in the synchronized device driver. Generally speaking, the terms used "Configuration / Management System" and "Operator Panel" are of course also replaced by the terms "Device Control Tool 1" and "Device Control Tool 2" - as shown in FIG. Known configuration / management systems have already been mentioned in the introduction to the description. It should also be mentioned that the configuration / management system is also a plant asset

Management System (PAM), as for example offered and distributed by the Applicant under the term 'FieldCare'. A known on-site operator tool is offered and distributed by the assignee under the name Field Xpert.

A device driver encapsulates all device-specific data, functions and operating rules, such as the device structure, existing communication options and the graphical user interface, in other words the GUI, for a specific field device or for a specific field device type.

As a runtime environment, the DTMs require a frame application, ie FDT frame. The frame application and the corresponding DTMs allow very convenient access to field devices, e.g. on

Device parameters, on measured values, diagnostic information, status information, etc., as well as the call of special functions that are available to individual DTMs. In order for the DTMs from different manufacturers to function correctly in the frame application, the interfaces to the frame application and to the other DTMs must be clearly defined. This interface definition is hidden behind the abbreviation FDT. FDT technology unifies the communication interface between the field devices and the higher-level configuration / management system. FDT allows any field device via any higher level configuration / management systems over any bus systems

to appeal. A known FDT frame is the Applicant's already mentioned tool 'FieldCare'. In the HMI device, it may be a whatsoever

Handheld operating device, which can be used in the field to operate the field devices. For example, it can be a portable PC or a PDA or a handheld device known as a handheld.

The standardized device description used is preferably an EDD, an electronic device description, which is used in the field of

Process automation is widespread. It goes without saying that other device descriptions in conjunction with the inventive solution can be used.

According to an advantageous development of the method according to the invention, it is proposed that, for the purpose of synchronization, the current configuration / parameterization data stored in the operating device in the form of a standardized device description and that in the management

In the FDT example, a communication DTM is also created in the standardized software system of the management / configuration system. The control system-side topology of all field devices that are used in a process plant with the management / configuration - System are connected, is stored. In the event that all field devices or only some of the field devices that are / are arranged in the process plant are / is configured to communicate with the management / configurator system via the software system, the communicable field devices are each replaced by a device driver referenced in two different topologies: by the zu

updating device drivers in the management / configuring system topology and by the corresponding updated device drivers under the communication driver in the operator topology. An advantageous development of the method according to the invention provides that the data synchronization of the management / configuration system assigned to be updated device driver on the

Communication driver of the operator panel by means of a fieldbus protocol or by means of appropriate fieldbus commands is performed.

Preferred variants of the inventive solution provide that for the purpose of data synchronization between the two device drivers alternatively the following functionalities are used:

- in both topologies, the management / configuration system side

Topology and the operator side topology, is about the

standardized software system implements a proxy device driver for each device driver pointing to the respective device driver instance in the two topologies,

the device driver to be updated and the updated device driver are synchronized via the alternately stored data record in the data memory 17,

- By means of a called via the control software and implemented in the device driver comparison function of the two device drivers, the two data sets are compared and corresponding deviations are displayed.

In addition, it is provided that the data set to be updated is matched in accordance with the deviations found in the dialog after approval by the operating personnel.

An alternative embodiment of the solution according to the invention suggests that in the event that none of the connected to the control unit

Field devices of the process plant has an equipment that allows him to use the control unit via the standardized software system

in the management / configuring system topology only the operator specific communication driver is listed, at All device drivers of non-communicable field devices of the process plant are integrated.

In this context, it is provided that, for the purpose of data synchronization, the respective device driver to be updated is set online with the HMI device via the communication device driver assigned to the HMI device, and the current configuration / parameterization data is transmitted via the bus system to the device driver to be updated, so that All device-specific or device-specific offline functionalities of the device driver with the data of the field device

To be available.

Furthermore, it is proposed that the offline changed configuration / parameterization data of the device driver are transferred to the HMI device and that the configuration / parameterization data of the device driver are subsequently transmitted via the HMI device in the field in the field device. Alternatively, the offline configuration / parameterization data of the

Transfer device drivers to the HMI device; below are the

Transfer the configuration / parameterization data of the device driver with the HMI device in production to a field device of the same type and the same application. This method is also suitable because in many applications similar processes or identical process plants are operated in parallel. An advantageous embodiment of the method according to the invention provides that a software component is used for the synchronization, the configuration / Parametherdaten a download of the

Configuration / management system reads in and upload the

HMI device provides. Alternatively, it is proposed that a software component be used for the synchronization, which the

Read configuration / parameter data via download from the operator panel and make it available to the configuration / management system via an upload. This embodiment is particularly advantageous and necessary if for a full sync

Device-specific behavior must be taken into account, that is, if in particular an upload or a download is not unique. Is e.g. If a fieldbus command of a device type is unique only via further information or if the sequence of the fieldbus commands in the upload or download is significant, the appropriate additional knowledge is required for the correct synchronization of the configuration / parameter data. This additional knowledge is provided in the software component. In particular, the software component used for the synchronization for the synchronization of the data set formed from the configuration / parameterization data is a device-specific file. Preferred is a device description or an electronic device

Description or simply a device description used.

The invention will be explained in more detail with reference to the following figures. It shows:

1 shows a representation of exemplary hardware components of a process control of automation technology, which are suitable for carrying out the method according to the invention,

1: the left-hand detail of the hardware components shown in FIG. 1, FIG. 2: a representation of an FDT software topology suitable for the device shown in FIG. 1 a for carrying out a first variant of the method according to the invention,

3 shows an illustration of a second variant of the method according to the invention,

4 shows a representation of a third variant of the method according to the invention and 5 shows an illustration of a fourth variant of the method according to the invention. 6 shows a schematic representation of the method according to the invention for a special case.

1 shows a representation of exemplary hardware components of a process control of automation technology, which are suitable for carrying out the method according to the invention. The inventive method is used to synchronize the current field device F of the process automation technology in the form of a standardized

Device description, e.g. DD, assigned configuration / Parametherdaten 18 with a full field device F.

descriptive device driver 7, DeviceDTM, which is assigned to the higher-level management / configuration system 1. The management / configuration system 1 runs a standardized software system FDT Frame. The standardized software system in the case shown is an FDT frame, which provides access to the device driver 7,

DeviceDTM allowed. In a first embodiment - Scenario 1 (FIG. 1 a) - the standardized software system FDT Frame is integrated in a management / configuration system 1. The control system 1 is connected via a company network Factory LAN and a control unit 5 with the fieldbus level 9, 12. While at the corporate network level Factory LAN the

Communication preferably over a fast connection, e.g. Ethernet TCP / IP, the communication is carried out at the field bus level, for example via Profibus DP, Profibus PA 12 and HART 9. By means of the gateway 4, the fieldbus protocol Profibus PA is converted to the HART protocol.

In a second embodiment - Scenario 2 (FIG. 1) - the standardized software system FDT frame is in a via a fieldbus interface 6 or over integrated plant asset management system PAM 1 a plant access point to the bus system 9,12. Called at this point is the product FieldCare the Anmeldehn. Since users typically protect their plant networks Factory LAN via a firewall 13, the PAM system 1 accesses the bus system 9 and the field devices F, F1, F2,... Via a secure fieldbus interface 6 and a gateway 4 at the fieldbus level.

The field device F is locally connected in the field with an operating device 2 via a point-to-point connection 3, in particular via a modem. The connection can be wired or wireless. About the

Bus protocol of the bus system 3, the field device F is configured or parameterized via the HMI device 2. On the bus system 3 is the

Communication preferred over one of the previously mentioned

Fieldbus protocols of the bus system used. The current

Device-specific configuration / parameterization data 18 of the field device F are stored as a current DD-based data record 18 in the operating device 2 by means of a standardized device description, here a DD.

As can be seen from FIG. 2, the operating device 2 is subsequently, temporally and spatially separated, connected to the higher-level management / configuration system 1. The connection is made via an operator-specific communication port 10, for example via USB or Blue Tooth. Subsequently, the synchronization of the management / configuration system 1 associated device driver 7, DeviceDTM and stored in the operating device 2 current DD-based data set DD ', so that in the synchronized device driver 8, DeviceDTM also the current configuration / Parametherdaten 18 are available. The

Synchronization is based on fieldbus communication. For synchronization of the current configuration / parameterization data 18 stored in the operating device 2 in the form of a standardized device description DD and the device driver 7, DeviceDTM, to be updated in the management / configuration system 1, the operating device specific communication driver 14, CommDTM, which in this case is an FDT communication driver.

As can be seen in Figure 2, the FDT Frame software system provides two functionalities for synchronization: There are two topologies, one control-system topology and one operator-side topology, in which each field device F is represented by a corresponding device driver

DeviceDTM of the same type 7 and 8 is referenced. One

Device driver 7, DeviceDTM is integrated in the control system topology or in the network topology. The second device driver 8, DeviceDTM 8, is in the sub-topology, ie the user-device-side topology, under the user-device-specific communication driver 14, CommDTM

involved. By means of the software system FDT Frame is now the

Data synchronization of the device driver 7, DeviceDTM via the

operator-specific communication driver 14, CommDTM with the device driver s, DeviceDTM.

For synchronization of the configuration / parameterization data of the device driver 7, DeviceDTM with the device driver 8, DeviceDTM in the two

Topology branches implement the following functionalities:

- The software system FDT Frame has in both topology branches

Proxy device driver ProxyDTMs 15, 16, which is based on a single

Device driver reference Instance DeviceDTM 8. This embodiment is shown in Fig. 3. Access to the data set of the device driver instance DeviceDTM 8 is made by the software system FDT Frame via the alternate access via the ProxyDTM 15 or the

ProxyDTM 16 synchronized.

- The software system FDT Frame allows mutually

Synchronized storage of both device drivers 7, DeviceDTM, 8, DeviceDTM in a data memory 17 (FIG. 2)

- A device driver DeviceDTM provides a software system specific

Comparison function for matching the data sets DD, DD 'by the user. (Fig. 4) FIG. 5 shows a further variant of the method according to the invention. In this variant, that has from the HMI device 2 to

synchronizing field device F does not have the option over that

Software system FDT Frame to communicate with the communication device driver 14, CommDTM. For example, the field device is a 4-2OmA device. Now, the FDT Frame software system provides the following functionality for synchronization. The

Software system FDT Frame has only the user-specific communication device driver 14, CommDTM in its topology. Under the operator-specific communication device driver 14 are all

Device driver 7, DeviceDTM, ... of the field devices F, F1, F2, ... to be updated. For synchronization, the to be updated

Device drivers 7, DeviceDTM /, the DeviceDTM 7, ... device drivers to be updated are set online and communicate with the operating device 2 via the respective fieldbus protocol 10. The field device F not connected to the FDT Frame software system now behaves like one via the FDT Frame software system communicable field device F. Via a deviceDTM upload functionality implemented in the device driver 7, DeviceDTM, all parameters 18 are loaded from the operating device 2 into the device driver 7, DeviceDTM. A functionality DeviceDTM Download implemented in the device driver 7, DeviceDTM writes the current configuration / parameter ether data 18 into the operator device 2 in order subsequently to write it in the field or in production into a field device F of the same type. Fig. 6 shows a schematic representation of the invention

Procedure for the special case that for complete data transmission between the configuration / Paramethersystem 1 and the HMI device 2 additional information is required. In particular, this is the case when using the HART protocol, in which often manufacturer-specific information is attached to the individual commands. For example, behind a fieldbus command several options can be hidden. As shown in FIG. 6, this additional knowledge is integrated in a software component 19, the so-called device simulation component. These Software component 19 enables the correct download / upload of a data set of configurator / parameter ether data 18 between the configuration / parameter ether system 1 and the operating device 2. In the case shown, the software component 19 is integrated in a PC on which the configuration / management system 1 is running. It goes without saying that the integration of the software component 19 is not restricted to this embodiment shown in FIG. 6.

LIST OF REFERENCE NUMBERS

1 configuration / management system

2 HMI device

3 fieldbus / bus system

4 gateway / converter unit

5 Control / Control

6 Fieldbus interface

7 device driver / DeviceDTM to update

8 current device drivers / DeviceDTM '

9 System-side fieldbus communication

10 HMI device-specific communication port, for example: via USB, BlueTooth, ...

11 standardized device description DD

12 communication drivers (bussystem-specific)

13 Firewall to protect the factory LAN

14 communication device drivers (operator specific)

15 Proxy device driver

16 Proxy device drivers

17 data memory

18 configuration / parameterization data stored in the HMI device based on the DD / EDD

19 software component

F field device

Claims

claims

1. A method for synchronization of the current field device (F) of the process automation technology in the form of a standardized

Device description (DD) assigned configuration / parameterization data

(18) with a device driver (DeviceDTM) which fully describes the field device (F) and which is assigned to a higher-level management / configuration system (1), wherein a standardized software system (FDT frame) is provided in the management / configuration system (1), which allows access to the device driver (7, DeviceDTM),

wherein the field device (F) is locally connected in the field with an operating device (2) via a point-to-point connection 3 and configured or parameterized via digital communication of a bus system (9, 12),

the current device-specific configuration / parameterization data (18) of the field device (F) being stored as a current DD-based data record in the operating device (2) by means of a standardized device description (DD, 11),

wherein the HMI device (2) is then, temporally and spatially separated, connected to the parent management / configuration system (1), and

the one associated with the management / configuration system (1)

Device driver (7, DeviceDTM) and stored in the operating device (2) current DD-based data set 18 are synchronized so that in the synchronized device driver (8, DeviceDTM ') the current configuration / parameterization data (18) are available.

2. The method according to claim 1,

wherein for the purpose of synchronization in the operating device (2) in the form of a standardized device description (DD) stored current

Configuration / parameter data (18) and the one in the management

/ Configuration system (1) device driver to be updated (7, DeviceDTM) an operator-specific communication driver (14, Com m DTM) is created.

3. The method according to claim 1,

in the standardized software system (FDT frame) of the

Management / configuration system (1) the control system topology of all field devices (F, F1, F2, ...) operating in a process plant with the

Management / configuration system (1) is stored.

4. The method according to claim 1, 2 or 3,

wherein in the case that all field devices (F, F1, F2,...) or only a part of the field devices (F, F1, F2,...) arranged in the process plant are / are designed in this way is that they are standardized with the management / configuration system (1) via the software system (FDT frame)

Communication drivers communicate, the communicable field devices (F, F1, F2, ...) each by a device driver (7, DeviceDTM; 8,

DeviceDTM ') are referenced in two different topologies: by the device drivers to be updated (7, DeviceDTM) in the topology of the management / configuring system and by the corresponding updated device drivers (8, DeviceDTM') under the communication driver (14, CommDTM) in the operator-side topology.

5. The method according to claim 4,

the data synchronization of the device driver (8, DeviceDTM ') to be updated assigned to the management / configuration system (1) via the communication driver (14, CommDTM) of the operating device (2) by means of a fieldbus protocol or by means of corresponding fieldbus commands of the bus system (3). is carried out.

6. The method according to claim 4 and / or 5,

wherein for the purpose of data synchronization between the two device drivers (7, DeviceDTM; 8, DeviceDTM ') the following functionalities are alternatively used:

- in both topologies, the management / configuration system side

Topology and the operator side topology, is about the standardized software system (FDT frame) for each device driver (7, DeviceDTM, 8, DeviceDTM ') a proxy device driver (15, 16;

ProxyDTM) pointing to the respective device driver instance in the two topologies,

the device driver (7, DeviceDTM) to be updated and the updated device driver (8, DeviceDTM) are synchronized via the alternately stored data record in the data memory (17),

- By means of a called via the control software and in the device driver (7, DeviceDTM) realized comparison function of the two device drivers (7, 8) the two data sets are compared and corresponding deviations are displayed.

7. The method according to claim 6,

wherein the updated DD-based data set according to the deviations found in the dialogue after approval by the operating staff.

8. The method according to claim 1, 2 or 3,

in the event that none of the field devices connected to the management / configuration system (1) (F, F1, F2,

Equipment that allows him to communicate with the control unit (1) via the standardized software system (FDT frame), in the management / configurator system topology only the user-specific communication driver (14, CommDTM) is listed under the All device drivers (DeviceDTM) of the non-communicable field devices of the process plant are integrated.

9. The method according to claim 8,

wherein for the purpose of data synchronization of each to be updated

Device driver (7, DeviceDTM) online with the operating device (2) via the communication device driver (14) assigned to the operating device (2)

CommDTM) is set, and wherein the current configuration / Parametherdaten (18) via the fieldbus protocol of the bus system (12) to the device drivers to be updated (7, DeviceDTM) are transmitted, so that all device-specific or device-specific offline functionalities of the device driver (7, DeviceDTM) with the data of the

Field device (F, F1, F2, ...) are available.

10. The method according to claim 9,

wherein the offline changed configuration / parameterization data (18) of the device drivers (8, DeviceDTM ') are transmitted to the operating device (2) and wherein the configuration / parameterization data of the device drivers (8,

DeviceDTM ') are subsequently transferred to the field device (F) in the field using the operator panel (2).

11. The method according to claim 9,

wherein the offline changed configuration / parameter ether data (18) of the device driver (8, DeviceDTM ') are transmitted to the operating device (2) and wherein the configuration / parameter ether data (18) of the device driver (8, DeviceDTM') subsequently to the operating device ( 2) during maintenance or production for preconfiguration into a field device (F, F1, F2, ...) of the same type and same application.

12. The method according to claim 1,

wherein a software component is used for the synchronization, which downloads the configuration / parameterization data (18) via a download from the management / confi guration system (1) and makes it available to the operating unit (2) via an upload.

13. The method according to claim 1,

wherein a software component is used for the synchronization, which reads the configuration / parameterization data (18) via a download from the operating device (2) and provides the management / configuration system (1) via an upload.

14. The method according to claim 12 or 13, wherein the software component used for the synchronization for the synchronization of the data set formed from the configuration / parameterization data (18) uses a device-specific file, in particular a device description (DD).