Device for controlling field devices in an automation system

Abstract

The invention relates to a system for controlling, in particular remotely controlling, at least one automation technology field device (1) by means of a control tool (2), wherein the field device (1) is designed to communicate via a predetermined field bus protocol (BP), wherein a Remote IO (RIO) is arranged between the at least one field device (1) and the control tool (2), wherein communication between the control tool (2) and the Remote IO (RIO) takes place via an Ethernet-based protocol (EP), wherein a frame application (FDT) is installed on the control tool (2), to which frame application (FDT) a communication DTM (CommDTM), a gateway DTM (GatewayDTM) for the Remote IO (RIO) and a Device DTM (DTM1) for the at least one field device (1) are assigned, wherein the communication DTM (CommDTM) is a communication-specific driver which is designed to make available, to the gateway DTM (GatewayDTM) and to the Device DTM (DTM1), necessary information about the communication protocol (BP) used by the field device (1), wherein the gateway DTM is a gateway iDTM which enables communication between the control tool (2) and the field device (1) using the information of an FDI package for the Remote IO (RIO), and wherein the Device DTM (DTM1) is designed such that it enables fully comprehensive control of the field device (1) via the control tool (2).

Description

[0001] Device for operating field devices in an automation system

[0002] The invention relates to a device for operating field devices in an automation system.

[0003] A wide variety of field devices are known from the state of the art and are used in industrial automation systems. They are used in many areas of process automation and manufacturing automation. In the context of the invention, field devices are considered to be all devices that are used close to the process and that provide and / or process-relevant information. Depending on the area of ​​application, field devices detect and / or influence physical, chemical, or biological process variables of at least one process medium.

[0004] Measuring instruments, which typically consist of a sensor unit and a transmitter unit, are used to record process variables. These are used, for example, for pressure and temperature measurement, conductivity measurement, flow measurement, pH measurement, or level measurement and record the corresponding process variables: pressure, temperature, conductivity, pH value, level, or flow. Actuators such as pumps or valves are used to influence process variables, for example, controlling the flow of a liquid in a pipeline or the level in a container. In addition to the measuring instruments and actuators mentioned above, the term "field devices" also includes remote I / Os, so-called RIOs, radio adapters, components of the communication network such as gateways and edge devices, or - generally speaking - devices that are arranged at the field level or process level in the automation system.A large number of such field devices are developed, manufactured and distributed by the Endress+Hauser Group.

[0005] An edge device is a connecting device located at the "edge" of an automation technology network, and its name refers to this special arrangement. Depending on requirements, an edge device provides various interfaces to wired and wireless transmission technologies and communication standards, such as Ethernet, Wi-Fi, or mobile communications such as LTE (4G), 5G, etc. The task of an edge device is to transfer data—if appropriately processed—between the field devices of an automation system and an external server platform.

[0006] Communication between the field devices and, if applicable, a higher-level control unit takes place via one of the communication protocols used in automation technology, such as HART, PROFIBUS, or FOUNDATION Fieldbus. A gateway or remote IO (RIO) converts the communication protocol at the field level to a higher-level protocol, such as EtherNet / IP or an Ethernet-based fieldbus used in automation technology, such as PROFINET.

[0007] Fig. 1 shows an embodiment of a device for operating field devices 1, as is known from the prior art. The field devices 1 used in an automation system are, in the case shown, HART field devices (1) that communicate with an operating tool 2 via a remote IO (RIO). Using the operating tool 2, the operating personnel BL have access to each of the field devices 1 and can fully operate them.

[0008] In the context of the invention, operation is understood to mean commissioning, configuration and calibration, as well as the display of measured and manipulated variables or further, complex information, such as the echo curve of a radar-based level measuring device, on the display of an operating tool. A PC, for example, can be used as the operating tool 2. Furthermore, the operating tool 2 can be used for the diagnosis and predictive maintenance of the field devices 1. The operating system of the PC can be WINDOWS or LINUX, for example. The ET200 from Siemens can be mentioned as an example of a remote IO (RIO). The remote IO (RIO) converts the data supplied in the HART protocol to an Ethernet-based fieldbus, here PROFINET, and transmits it via an Ethernet interface 3 to the operating tool 2 or the host computer, in the case shown to the Windows-based PC.Conversely, requests from the operating personnel BL are transmitted via the Ethernet interface 3 of the PC 2 to an addressed field device 1 , RIO, using the remote IO (RIO).

[0009] A framework application, in this case based on the FDT standard, is installed on operating tool 2. This framework application provides a graphical user interface for communication with field devices 1 and the remote IO (RIO). Using FDT technology, field devices and communication components (remote IOs, gateways, etc.) can be operated across manufacturers and independently of the communication protocol using a single software tool. Different types of device type managers are stored in the FDT framework application to implement communication with field devices 1, enabling the remote IO to be operated:

[0010] • At least one communication DTM CommDTM, which provides the connected field device DTMs or gateway DTMs with the functions of the corresponding communication protocol HART, PROFINET and forwards requests to the hardware in the function of a driver.

[0011] • A gateway DTM that allows the communication path up to field device 1 including the necessary transitions between different protocols and thus forms the basis for establishing vertical or networked communication (nested communication).

[0012] • A Device Type Manager DTM1 for each of the field devices 1, whereby the Device Type Manager DTM1 fully maps the assigned field device 1 or each assigned field device type with regard to its available functions and information.

[0013] The Fieldgate operating tool from Endress+Hauser, with complete libraries of certified DTMs (Device Type Managers) and FDI packages, can be used universally to operate all Endress+Hauser field devices. It includes CommDTMs for protocols such as HART, PROFIBUS, FOUNDATION Fieldbus, IO-Link, PROFINET, and Endress+Hauser. It can also be used to operate field devices from third-party manufacturers if they support the FDT / FDI standard. Devices from manufacturers that do not have device DTMs or FDI packages can be operated using a generic DTM with certain standardized parameters.

[0014] For the purpose of integrating an additional tool into a network for monitoring or controlling processes in an automation system, which tool is intended to obtain additional information that is useful for the user, the following solution is proposed in US 2008 / 0112388 A1: An FDT framework application is provided, into which at least one device DTM, at least one generic DTM, a communication DTM, a router DTM and an RIO gateway DTM are integrated. A unit called the Asset Optimization Device Manager, which is EDDL-based, is connected to the router DTM of the FDT framework application via an interface. The router DTM is arranged between the device DTM / the generic DTM and the RIO gateway DTM. This router DTM is configured such that from the perspective of the device DTM / the generic DTM it functions as an RIO gateway DTM, while from the perspective of the RIO gateway DTM it is treated as a device DTM or generic DTM.

[0015] Another option for operating field devices in a bus system is based on EDD technology. EDDs (Electronic Device Descriptions) are text-based device description files. EDD technology also makes it possible to operate and parameterize different device types from different manufacturers using a single software tool. The EDDs are written in the Electronic Device Description Language (EDDL), which serves as a universal language for systems such as HART, PROFIBUS, and FOUNDATION Fieldbus.

[0016] FDI technology represents a further development. Field Device Integration (FDI) combines the advantages of the two previously mentioned integration technologies. Existing EDDs can continue to be used with FDI technology without modification. FDI technology was jointly developed by process industry associations including the Fieldcomm Group, PROFIBUS International, the OPC Foundation, and the FDT Group and is standardized in IEC 62769.

[0017] The core of the FDI standard is the FDI Device Package. This is a standardized container that contains all components required to describe the field devices in an automation system. FDI device packages contain EDDs for field devices and optional UIPs (User Interface Plug-Ins) for implementing complex device functions, such as the aforementioned echo curve of a radar level measuring device, and DTMs. The FDT DTM technology, with an iDTM, enables the use of FDI device packages - FDI Packages - on any host computer on which an FDT frame application is installed. The CodeWrights product is an example of an iDTM. EDDs and, if applicable, UIP components within the FDI device package are represented by the iDTM as device DTMs.The invention is based on the object of providing a device for operating field devices of an automation system with which networked communication can be easily implemented.

[0018] The object is achieved by a system for operating, in particular remote control of at least one field device of automation technology by means of an operating tool,

[0019] • wherein the field device is designed such that it communicates via a predetermined fieldbus protocol, wherein a remote IO is arranged between the at least one field device and the operating tool,

[0020] • where communication between the operating tool and the remote IO takes place via an Ethernet-based protocol,

[0021] • where a frame application is installed on the operating tool, to which a communication DTM, a gateway DTM for the remote IO and a device DTM for the at least one field device are assigned,

[0022] • the communication DTM is a communication-specific driver designed to provide the gateway DTM and the device DTM with the necessary information about the communication protocol used by the field device,

[0023] • the Gateway DTM is a Gateway iDTM that enables communication between the operating tool and the field device using the information of an FDI package for the remote IO, and

[0024] • the device DTM is designed in such a way that it enables full operation of the field device via the operating tool.

[0025] The invention enables the simple implementation of nested communication. The gateway iDTM uses FDI device packages that represent the remote IO, the RIO, or the gateway to use the remote IO in a framework application, particularly the FDT framework application used in automation technology.

[0026] A further development of the system according to the invention proposes that the FDI device package be a standardized container that contains all the information required to describe the functions of the remote IO. In particular, the information stored in the FDI package includes the following components:

[0027] • At least one electronic device description for the remote IO, whereby the electronic device description fully describes the remote IO;

[0028] • A software component designed to contain the necessary rules to perform the conversion between the Ethernet-based protocol and the fieldbus protocol;

[0029] • Additional information that further describes the remote IO. It goes without saying that this additional information can be omitted as needed.

[0030] One embodiment of the system according to the invention provides that an interpreter is provided in the gateway iDTM for the remote IO, which implements the electronic device description of the remote IO. In conjunction with the conversion rules stored in the software component for converting the Ethernet-based protocol and fieldbus protocol, the device type manager, i.e., the iDTM, is generated for the remote IO. The electronic device description (EDD) and the software component for the remote IO are provided by the FDI package. The interpreter generates the gateway iDTM, preferably in real time.

[0031] As already mentioned, the fieldbus protocol via which the field devices communicate is preferably one of the fieldbus protocols used in automation technology, such as HART, PROFIBUS PA, FOUNDATION Fieldbus or IO-Link.

[0032] The Ethernet-based protocol is an Ethernet-based fieldbus protocol, specifically PROFINET. It goes without saying that other Ethernet-based protocols, such as Ethernet APL, can also be used in conjunction with the invention.

[0033] It is considered advantageous if the Gateway Device Type Manager iDTM for the Remote IO is designed to allow access to the Remote IO from the frame application via a graphical interface assigned to the operating tool. This enables operating personnel to access all device functions provided by the Gateway iDTM for the Remote IO and to operate the Remote IO. The meaning of the term "operate" in connection with the invention has already been explained above. For example, the invention can be integrated into a Windows-based operating tool, such as FieldCare – a product of the Endress+Hauser Group.

[0034] The invention is explained in more detail with reference to the following figures. They show:

[0035] Fig. 1 : a schematic representation of a device known from the prior art for operating field devices of an automation system,

[0036] Fig. 2: a schematic representation of the components of an embodiment of the device according to the invention for operating field devices of an automation system, and

[0037] Fig. 3: a schematic representation of two components shown in Fig. 2 with further details.

[0038] Fig. 1 shows a schematic representation of a prior art device for operating field devices of an automation system. The corresponding device was already introduced in the introduction to the description.

[0039] Fig. 2 shows a schematic representation of the components of an embodiment of the device according to the invention for operating field devices 1 of an automation system. As already described in connection with Fig. 1, a large number of field devices 1 are arranged in an automation system. Their various functions were already presented in the introduction to the description. The field devices 1 communicate with an operating tool 2 via a remote IO (RIO), which converts the HART protocol used at the field level to the PROFINET protocol. The conversion between the PROFINET and HART protocols also takes place. It goes without saying that any of the protocols used in automation technology can be used at the field level; likewise, another Ethernet-based protocol, for example EtherNet / IP, can be used instead of PROFINET.The connection to the operating tool 2 is established via an Ethernet interface 3 assigned to the operating tool 2. The FDT frame application (FDT) contains various components / modules: a communication DTM, a gateway iDTM for the remote IO (RIO), and a device DTM. An FDI package for the remote IO is assigned to the gateway iDTM for the remote IO (RIO).

[0040] Fig. 3 shows further details of the FDI package for the Remote IO (RIO) and the Gateway iDTM for the Remote IO (RIO). The FDI package for the Remote IO (RIO) comprises an EDD designed to fully describe the Remote IO (RIO). Furthermore, a software component SK, in this case .NET, is provided, which contains the Remote IO rules for converting PROFINET to HART. Additionally, a module A is provided, which contains further information on the Remote IO. This information can be provided in PDF format, for example, and corresponds, for example, to a manual describing the Remote IO (RIO).

[0041] The FDI package provides the gateway iDTM for the remote IO (RIO) with the software component SK, which contains the remote IO rules for converting PROFINET to HART. The EDD for configuring the remote IO (RIO) of the FDI package is provided to an EDD interpreter I. The interpreter I is a computer program that executes a sequence of instructions immediately – in real time – with a standardized instruction format. The interpreter I reads the EDD for the remote IO (RIO), analyzes it, and provides it as executable code.

[0042] Since the information for operating the Remote IO (RIO) is now available as an iDTM—that is, as an executable program—and is integrated into an FDT framework application, the Remote IO (RIO)—like any other field device-specific DTM—can be used for the full operation of the Remote IO (RIO).

[0043] 1 field device

[0044] 2 operating tool, PC

[0045] 3 Ethernet interface

[0046] RIO Remote / Remote IO

[0047] CommDTM Communication DTM

[0048] Gateway iDTM iDTM for RIO

[0049] DTM1 DTM for field device 1

[0050] FDI FDI Software for RIO

[0051] FDT FDT frame application

[0052] BL operating personnel

[0053] BP bus protocol (HART, FOUNDATION Fieldbus, PROFIBUS, ..)

[0054] EP Ethernet-based protocol (Profinet, EtherNet / IP,..)

[0055] EDD electronic device description

[0056] I Interpreter for the electronic device description iDTM Device Type Manager with interpreter for FDI Package

[0057] SK software component (.NET, ....)

[0058] A Additional information (PDF, ... )

Claims

Patent claims 1. System for operating at least one field device (1) of automation technology by means of an operating tool (2), wherein the field device (1) is designed such that it communicates via a predetermined fieldbus protocol (BP), wherein a remote IO (RIO) is arranged between the at least one field device (1) and the operating tool (2), wherein the communication between the operating tool (2) and the remote IO (RIO) takes place via an Ethernet-based protocol (EP), wherein a frame application (FDT) is installed on the operating tool (2), to which a communication DTM (CommDTM), a gateway DTM (Gateway DTM) for the remote IO (RIO) and a device DTM (DTM1) for the at least one field device (1) are assigned, wherein the communication DTM (CommDTM) is a communication-specific driver which is designed such thatthat it provides the Gateway DTM (Gateway DTM) and the Device DTM (DTM1) with the necessary information about the communication protocol (BP) used by the field device (1), wherein the Gateway DTM is a Gateway iDTM that enables communication between the operating tool (2) and the field device (1) using the information of an FDI package for the Remote IO (RIO), and wherein the Device DTM (DTM1) is designed in such a way that it enables full operation of the field device (1) via the operating tool (2).

2. The system of claim 1, wherein the FDI device package is a standardized container that contains all information required to describe the functions of the remote IO (RIO).

3. System according to claim 1 or 2, wherein the information stored in the FDI package comprises in particular the following components: at least one electronic device description (EDD) for the remote IO (RIO), wherein the device description fully describes the remote IO (RIO); a software component (SK) designed to contain the necessary rules to perform the conversion between the Ethernet-based protocol (EP) and the fieldbus protocol (BP); if necessary, additional information (A) that further describes the remote IO (RIO).

4. System according to claim 1, 2 or 3, wherein an interpreter (I) is provided in the gateway iDTM for the RIO, which interpreter converts the electronic device description (EDD) of the remote IO (RIO), and wherein the gateway device type manager (iDTM) for the remote IO (RIO) is generated in conjunction with the conversion rules stored in the software component (SK) for converting the Ethernet-based protocol (EP) and fieldbus protocol (BP), wherein the electronic device description (EDD) and the software component (SK) for the remote IO (RIO) are provided by the FDI package.

5. System according to one or more of the preceding claims, wherein the fieldbus protocol (BP) is one of the fieldbus protocols used in automation technology, such as HART, PROFIBUS PA, FOUNDATION Fieldbus or IO-Link.

6. System according to one or more of the preceding claims, wherein the Ethernet-based protocol (EP) is an Ethernet-based fieldbus protocol, in particular PROFINET.

7. System according to one or more of the preceding claims, wherein the Ethernet-based protocol (EP) is an Ethernet APL-based fieldbus protocol.

8. System according to one or more of the preceding claims, wherein the device DTM (iDTM) for the remote IO (RIO) is designed such that it allows access to the remote IO (RIO) from the frame application (FDT) via a graphical interface assigned to the operating tool (2), whereby the operating personnel (BL) can access all device functions provided by the device DTM (iDTM) for the remote IO (RIO) and can operate the remote IO (RIO), in particular configure, parameterize and maintain it.

Images