EP3616011B1 - Arrangement and method for monitoring an automation technology system - Google Patents

Description

The invention relates to an arrangement, a fieldbus access unit and a method for monitoring an automation technology system, which system has a fieldbus access unit, in particular a computing unit, a gateway or an edge device, which is in communication with at least one first wired or wireless communication network , wherein the first communication network comprises a plurality of field devices and network nodes.

Field devices that are used in industrial plants are already known from the prior art. Field devices are often used in automation technology as well as in production automation. In principle, all devices that are used close to the process and that supply or process process-relevant information are referred to as field devices. Thus, field devices are used to record and/or influence process variables. Measuring devices or sensors are used to record process variables. These are used, for example, for pressure and temperature measurement, conductivity measurement, flow measurement, pH measurement, level measurement, etc. and record the corresponding process variables pressure, temperature, conductivity, pH value, level, flow rate, etc. Actuators are used to influence process variables. These are, for example, pumps or valves that can influence the flow of a liquid in a pipe or the fill level in a container. In addition to the measuring devices and actuators mentioned above, field devices also include remote I/Os, wireless adapters or devices in general that are arranged at the field level.

A large number of such field devices are produced and sold by the Endress+Hauser Group.

In modern industrial plants, field devices are usually connected to higher-level units via communication networks such as fieldbuses ( ^Profibus® , Foundation® ^Fieldbus , ^HART® , etc.). The higher-level units are control units, such as a PLC (programmable logic controller) or a PLC (programmable logic controller). The higher-level units are used, among other things, for process control and for commissioning the field devices. The measured values recorded by the field devices, in particular by sensors, are transmitted via the respective bus system to one (or possibly several) higher-level unit(s), which further process the measured values and forward them to the control center of the plant. The control station is used for process visualization, process monitoring and process control via the higher-level units. In addition, there is also data transmission from the higher-level unit to the field devices via the bus system required, in particular for the configuration and parameterization of field devices and for the control of actuators.

Appropriate operating programs (operating tools) are required to operate the field devices; Emerson Delta V) are integrated. The term "operating" is understood to mean, among other things, parameterization of the field device, updating of the field device and/or querying and visualizing process data and/or diagnostic data of the field device.

Field devices are integrated into such operating programs via device drivers or via device descriptions. These are provided by the device manufacturers so that the higher-level units, or the operating programs running on these higher-level units, can recognize and interpret the meaning of the information supplied by the field devices. Such an operating program, into which the device descriptions or device drivers are loaded, is also referred to as a frame application.

Special device drivers, so-called DTMs (Device Type Manager), which correspond to the FDT (Field Device Tool) specifications, are available for comprehensive operation of the field devices. Many field device manufacturers supply corresponding DTMs for their field devices. The DTMs encapsulate all variables and functions of the respective field device and usually offer a graphical user interface for operating the devices within the frame application.

In addition to the higher-level units, operating units in the form of client computers, on which a corresponding frame application runs, are often used to operate the field devices. These client computers are, for example, laptops, but also mobile devices such as tablet PCs. They are connected to a fieldbus access unit connected to the fieldbus network for communication with the field devices. A frame application is also executed on the fieldbus access unit. Using a special communication driver, for example the "YCommDTMs" offered by the applicant for the "Fieldcare" frame application, it is possible to access the frame application of the fieldbus access unit and to gain access to the field devices via this. The network infrastructure between the field device and the fieldbus access unit is completely transparent for the client computer, since it only needs to be known to the fieldbus access unit. The client computer only needs to know the network address of the field device that it wants to access.

The network infrastructure, i.e. the respective (partial) networks, the field devices and network nodes present in the respective network (e.g. segment couplers, remote IOs, etc.), is usually visualized in the frame application in two different ways: On the one hand, by means of a network topology which Network topology provides for a sorting and structuring of the network nodes and field devices according to their network addresses. On the other hand by means of a plant topology, the plant topology providing for a sorting and structuring of the network nodes and field devices according to the respective plant parts in which the network nodes and field devices are used.

Previously, the information on the network infrastructure had to be transferred manually from the fieldbus access unit to the client computer. For this purpose, project files were converted into the said information in a generator and then transmitted to the client computer, which is a complex process. Since the information was only synchronized manually, the information on the network infrastructure on the client computer could deviate from the actual network infrastructure in the plant and quickly become outdated, for example if field devices were exchanged or updated.

the DE102010063164 A1 relates to a method for integrating a field device that is unknown in a network of automation technology into an existing network.

U.S. 2012/004743 A1 shows a procedure for an optimized maintenance of field devices in a network.

DE 10 2015 108053 A1 shows the scanning of an address space to query device specifications from the field devices present in the address space.

Proceeding from this problem, the invention is based on the object of presenting a method, a fieldbus access unit and an arrangement which, in a simple manner, allow an up-to-date overview of the network infrastructure in a process automation system.

The object is achieved by a method for monitoring an automation technology system according to patent claim 1 and an arrangement according to patent claim 12 .

The advantage of the method according to the invention is that the data on the network infrastructure of the first communication network that is current at the time of the request is always transmitted to an operator. This gives him a "live" view of the system or the first communication network of the system. In contrast to the methods known in the prior art, the structural data are created automatically.

The first frame application is in particular an FDT/FDI frame application or a DD (Device Description) or EDD (Electronic Device Description) host.

If the first communication network is wired, it is, for example, a fieldbus used in automation technology, for example Foundation Fieldbus, Profibus PA, Profibus DP, HART, CANBus, etc. However, it can also be a modern industrial communication network For example, an "Industrial Ethernet" fieldbus, in particular Profinet, HART-IP or Ethernet/IP, or a communication network known from the field of communications, for example Ethernet based on the TCP/IP protocol.

If the first communication network is designed to be wireless, this is in particular WirelessHART, Bluetooth, Wifi, ZigBee, etc.

The first communication network typically consists of a number of sub-networks, so-called network levels, which are connected to one another by means of network nodes. The sub-networks can have different network types and network protocols.

A network node is a network device that connects the individual network levels with each other. If necessary, the network nodes carry out a protocol translation between the respectively connected network levels. Depending on the type of network levels connected, the network nodes are, for example, gateways, remote IOs, links, couplers, protocol converters, multiplexers, etc.

A remote IO is, for example, a local distributor node to which one or more field devices or network nodes can be connected. The remote IO is primarily used to reduce the amount of cabling. Instead of wiring each component individually to a remote fieldbus network, a remote IO is connected to the communication network as a distribution node, and data traffic is routed through the remote IO forwarded to various field devices located in the vicinity. With a remote IO, the focus is on the local distribution of the data traffic.

A gateway is primarily about the coupling between different network levels. The gateway ensures that the data traffic is appropriately implemented between the individual network levels. This translation may include protocol translation, but this is not mandatory.

With a protocol converter, on the other hand, the protocol conversion is in the foreground. The incoming data traffic is converted from a first fieldbus protocol into a second fieldbus protocol or in the opposite direction from the second protocol into the first protocol.

With a multiplexer, the focus is on expanding the available address range. The multiplexer provides an address range that can be used to address a large number of devices connected to the multiplexer. The incoming data traffic is then routed to the respective target device according to the addressing.

The second communication network is, for example, an Internet/intranet connection between the client computer and the fieldbus access unit, which can be implemented wirelessly or wired.

Field devices, which are mentioned in connection with the method according to the invention, have already been described by way of example in the introductory part of the description.

An advantageous embodiment of the method according to the invention provides that when the first frame application is started, the fieldbus access unit automatically creates and transmits the structure data of that network level of the first communication network which is directly connected to the fieldbus access unit.

According to a preferred embodiment of the method according to the invention, it is provided that the fieldbus access unit creates the structure data of the entire first communication network in addition to the structure data of the network level and transmits it to the client computer. The entire current network infrastructure of the first communication network is thus visible to an operator. In particular in modern industrial communication networks based on Ethernet, there is typically sufficient bandwidth available to perform a complete scan of the communications network without affecting traditional data traffic.

According to an advantageous development of the method according to the invention, it is provided that the fieldbus access unit adds network addresses and identification data of the network nodes and field devices determined in each case to the structure data before the transmission.

In an advantageous development of the method according to the invention, it is provided that one/one of the specific network nodes and field devices is operated using the first frame application by using its identification data and its network address to establish a communication channel between the client computer and the field device or the network node. is established via the fieldbus access unit. The operator thus not only receives the information about the network infrastructure, but also the current network parameters of the field devices and network nodes located in the first communication network. A functioning access to these network components is thus guaranteed at all times. The respective field device or the network node is accessed by means of a special communication driver which is executed on the first frame application of the client computer and which accesses the first frame application executed in the fieldbus access unit. According to an advantageous embodiment of the method according to the invention, it is provided that, in order to operate the field device or the network node, a device driver corresponding to the field device or to the network node is loaded in the first frame application. The appropriate device driver is automatically selected in particular based on the transmitted identification data. In particular, it is provided that a large number of device drivers are located on the client computer, from which the appropriate device driver is selected. In the event that no suitable device driver is available on the client computer, it can be provided that the client computer accesses a server of the field device manufacturer via the Internet and downloads the suitable device driver from there.

An advantageous embodiment of the method according to the invention provides that the specific network nodes and field devices are visualized in the first frame application according to the structure data transmitted.

According to a first variant of the method according to the invention, it is provided that the specific network nodes and field devices are visualized in a network topology, which network topology provides for sorting and structuring of the network nodes and field devices according to their network addresses.

According to a second variant of the method according to the invention, it is provided that the specific network nodes and field devices are visualized in a system topology, the system topology providing for sorting and structuring of the network nodes and field devices according to the respective system parts in which the network nodes and field devices are used.

According to an advantageous embodiment of the method according to the invention, it is provided that by selecting a network node in the visualization, the structural data of further network levels of the first communication network connected to the network node are newly created, transmitted and visualized. In this way, the current visualization of the network levels connected to the network node, or the field devices and/or network nodes located in the network levels, is always displayed to the operator.

According to an advantageous embodiment of the method according to the invention, it is provided that the operation of the field device/the network node is initiated by its selection in the visualization in the first frame application. This relieves the operator of work, since he does not have to set up a separate connection to the field device or to the network node.

Method according to claim at least one of the preceding claims, wherein the structural data is transmitted to the client computer in a structured text format, in an XML data format, in an SQL data format or in a JavaScript Object Notation data format.

Furthermore, the object is achieved by a fieldbus access unit for use in the method according to the invention.

The object is also achieved by an arrangement comprising a client computer on which a first frame application and a communication driver running on the first frame application are implemented, and a fieldbus access unit on which a second frame application is implemented for carrying out the method according to the invention.

The invention is explained in more detail with reference to the figure below. It shows

1 : an exemplary embodiment of the method according to the invention.

1 shows an embodiment of the method according to the invention. Part of a is shown Plant A of process automation. A multiplicity of field devices F1, F2, F3, . . . , Fn are connected to a first communication network KN1. The first communication network KN1 consists of several network levels NE1, NE2. In a first network level NE1, several network nodes NK1, NK2, NK3, . . . NKm are connected to one another in the form of remote IOs by means of a Profinet field bus. A large number of field devices F1, F2, F3 are connected to each of the network nodes NK1, NK2, NK3, .

A fieldbus access unit FE is connected to the first network level NE1. This is, for example, a computer. A second frame application is implemented on the fieldbus access unit FE, by means of which the individual field devices F1, F2, F3, . . . , Fn can be operated and/or monitored. The fieldbus access unit is connected to an Ethernet network via an additional interface. This forms, for example, the network of the control level of plant A. One or more access points are connected to the Ethernet network. These grant access to the Ethernet network by means of a wireless connection, for example WiFi.

An operating unit in the form of a client computer CR can also be used to operate the field devices F1, F2, F3, . . . , Fn. For this purpose, the client computer CR can be connected directly to a HART communication loop of a field device F1, F2, F3, . . . Fn. A special adapter AD, which represents a HART modem, is required for this. In this way, however, only one of the field devices F1, F2, F3, . . . , Fn can be operated at a time.

Alternatively, the client PC can therefore be connected to the fieldbus access unit FE by means of a second communication network KN2. In this case, the second communication network consists of a WiFi radio link between the client computer CR and the fieldbus access unit FE.

If the client computer knows the network address of a field device F1, F2, F3, . . . , Fn, it can access the field device F1, F2, F3, . For this purpose, a first frame application FR1 is running on the client computer. Using a special communication driver KT, for example the "YCommDTMs" offered by the applicant for the "Fieldcare" frame application, which is executed in the first frame application FR1, it is possible to access the second frame application FR2 of the fieldbus access unit FE and via this a communication channel KK to establish between client computer CR and field device F1, F2, F3, ..., Fn and to gain access to the field device F1, F2, F3, ..., Fn. In this way it is also possible to use multiple field devices F1, F2, F3, . . . , Fn to operate and/or monitor at the same time.

As already explained in the introductory part of the description, there is a need to obtain an up-to-date overview of the network infrastructure of the first communication network KN1 in plant A. For this purpose, the client computer CR transmits a request to the fieldbus access unit FE. This then determines for at least one network level NE1, NE2 all components located in this network level NE1, NE2, ie the field devices F1, F2, F3, . . . , Fn and network nodes NK1, NK2, NK3, . .., NKm. For this purpose, the fieldbus access unit FE scans the address space of the network level NE1, NE2. The fieldbus access unit FE creates structure data based on the determined field devices F1, F2, F3, ..., Fn and network nodes NK1, NK2, NK3, ..., NKm. This structural data contains the determined field devices F1, F2, F3, ..., Fn and network nodes NK1, NK2, NK3, ..., NKm, as well as the network level NE1, NE2 in which they are located. Alternatively, the entire first communication network KN1 can also be scanned, but this is associated with an increased expenditure of time and data traffic on the first communication network KN1.

Before the structure data is transmitted to the client computer CR, the network addresses and identification data, for example the respective tag and/or the respective serial number, of the specific network node NK1, NK2, NK3, ..., NKm and field devices F1, F2 , F3, ..., FN added.

The structure data is then converted into a suitable format, advantageously into a structured text format, into an XML data format, into an SQL data format or into a JavaScript Object Notation data format, and is transmitted to the client computer CR. The structural data are processed on this and displayed as a visualization VS in the first frame application FR1. in the in 1 In the example shown, the visualization VS is a so-called network topology. In a network topology, the network nodes NK1, NK2, NK3, . . . , NKm and field devices F1, F2, F3, . . . , Fn are sorted and structured according to their network addresses.

Alternatively, the visualization can take place as a system topology. In a plant topology, the network nodes NK1, NK2, NK3, ..., NKm and field devices F1, F2, F3, ..., Fn are sorted and structured according to the respective parts of the plant A, in which the network nodes NK1, NK2, NK3, ..., NKm and field devices F1, F2, F3, ..., Fn are used, made.

By selecting a field device F1, F2, F3, ..., Fn or a network node NK1, NK2, NK3, ..., NKm in the visualization VS, for example by clicking or typing (when using a Touchscreens) is, as described above, a communication channel KK between the field device F1, F2, F3, ..., Fn, or the network node F1, F2, F3, ..., Fn and the client computer CR via the fieldbus access unit FE constructed (in which in 1 shown example between Cleint computer RC and field device FN). The identification data and network addresses added to the structure data are used here. To operate a field device F1, F2, F3, ..., Fn or a network node NK1, NK2, NK3, ..., NKm, the appropriate device driver GT is automatically loaded into the first frame application FR1 and executed.

It is also possible to update the VS visualization. It can be provided for this purpose to select one or more of the nodes NK1, NK2, NK3, . . . , NKm. A request is then automatically sent to the fieldbus access unit FE and the structure data of the underlying network level NE1, NE2 of the network node NK1, NK2, NK3, ..., NKm is collected and transmitted to the client computer CR. The existing structural data is then updated with the newly collected structural data.

The method according to the invention offers the great advantage that an operator always has an up-to-date view of the network infrastructure of his plant A. In contrast to the methods known in the prior art, the structural data are automatically created in an efficient manner using the method according to the invention.

Reference List

A

Plant of automation technology

AD

adapter

CR

client machine

F1, F2, F3, ..., FN

field devices

FE

fieldbus access unit

FR1

first frame application

FR2

second frame application

GT

device driver

KK

communication channel

KN1

first communication network

KN2

second communication network

KT

communication driver

NE1, NE2

network levels

NK1, NK2, NK3, ..., NKm

network nodes

vs

visualization

Claims (12)

1. Procedure for monitoring a system (A) used in automation engineering, wherein said system has a fieldbus access unit (FE), particularly a computing unit, a gateway or an edge device, wherein said fieldbus access unit (FE) has a communication connection to at least a first wired or wireless communication network (KN1), wherein the first communication network (KN1) has multiple field devices (F1, F2, F3, ..., FN) and network nodes (NK1, NK2, NK3, ..., NKm),

   wherein a communication driver (KT) - which runs in a first framework application (FR1), wherein said first framework application (FR1) is implemented on a client computer (CR) connected directly or indirectly to the fieldbus access unit (FE) via at least a second communication network (KN2) - retrieves structure data of network nodes (NK1, NK2, NK3, ..., NKm) and field devices (F1, F2, F3, ..., FN) present in at least one network level (NE1, NE2) of the first communication network (KN1),

   wherein the retrieval of the structure data is transmitted to the fieldbus access unit (FE) and the latter unit creates said structure data and transmits the data to the client computer (CR); and

   wherein, within the framework of the data retrieval, the structure data is created by the fieldbus access unit (FE) in that the fieldbus access unit (FE) scans the address space of the network level (NE1, NE2) and determines the network nodes (NK1, NK2, NK3, ..., NKm) and field devices (F1, F2, F3, ..., FN) present in the address space, wherein the structure data concerns the infrastructure of the first communication network and contains network addresses and identification data of the determined field devices (F1, F2, F3, ..., FN) and network nodes (NK1, NK2, NK3, ..., NKm), as well as the network level (NE1, NE2) in which the determined field devices (F1, F2, F3, ..., FN) and network nodes (NK1, NK2, NK3, ..., NKm) are determined.
2. Procedure as claimed in Claim 1, wherein, when the first framework application (FR1) is created, the fieldbus access unit (FE) automatically creates and transmits the structure data of the network level (NE1) of the first communication network (KN1) that is directly connected to the fieldbus access unit (FE).
3. Procedure as claimed in at least one of the Claims 1 or 2, wherein, in addition to the structure data of the network level (NE1, NE2), the fieldbus access unit (FE) creates the structure data of the entire first communication network (KN1) and transmits this data to the client computer (CR).
4. Procedure as claimed in Claim 1, wherein one of the determined network nodes (NK1, NK2, NK3, ..., NKm) and field devices (F1, F2, F3, ..., FN) is operated using the first framework application (FR1) in that, using the identification data and the network address, a communication channel (KK) is established between the client computer (CR) and the field device (F1, F2, F3, ..., FN) or the network node (NK1, NK2, NK3, ..., NKm) via the fieldbus access unit (FE).
5. Procedure as claimed in Claim 4, wherein, to operate the field device (F1, F2, F3, ..., FN) or the network node (NK1, NK2, NK3, ..., NKm), a device driver (GT) corresponding to the field device (F1, F2, F3, ..., FN) or the network node (NK1, NK2, NK3, ..., NKm) is loaded in the first framework application (FR1).
6. Procedure as claimed in at least one of the previous claims, wherein the determined network nodes (NK1, NK2, NK3, ..., NKm) and field devices (F1, F2, F3, ..., FN) are visualized in the first framework application (FR1) in accordance with the transmitted structure data.
7. Procedure as claimed in Claim 6, wherein the determined network nodes (NK1, NK2, NK3, ..., NKm) and field devices (F1, F2, F3, ..., FN) are visualized in a network topology, wherein said network topology provides for the sorting and structuring of the network nodes (NK1, NK2, NK3, ..., NKm) and field devices (F1, F2, F3, ..., FN) according to their network addresses.
8. Procedure as claimed in Claim 6, wherein the determined network nodes (NK1, NK2, NK3, ..., NKm) and field devices (F1, F2, F3, ..., FN) are visualized in a system topology, wherein the system topology provides for the sorting and structuring of the network nodes (NK1, NK2, NK3, ..., FN) and field devices (F1, F2, F3, ..., FN) in accordance with the various system parts in which the network nodes (NK1, NK2, NK3, ..., NKm) and field devices (F1, F2, F3, ..., FN) are used.
9. Procedure as claimed in at least one of the Claims 6 to 8, wherein, by selecting a network node (NK1, NK2, NK3, ..., NKm) in the visualization (VS), the structure data of other network levels (NE1, NE2) of the first communication network (KN1) connected to the network node (NK1, NK2, NK3, ..., NKm) are recreated, transmitted and visualized.
10. Procedure as claimed in one of the Claims 4 to 9, wherein the operation of the field device (F1, F2, F3, ..., FN) or the network node (NK1, NK2, NK3, ..., NKm) is initiated by selecting it in the visualization (VS) in the first framework application (FR1).
11. Procedure as claimed in at least one of the previous claims, wherein the structure data is transmitted to the client computer (CR) in a structured text format, in an XML data format, in an SQL data format or in a JavaScript Object Notation data format.
12. Arrangement comprising a client computer (CR) on which a first framework application (FR1) and a communication driver (KT) running on the first framework application (FR1) is implemented, and a fieldbus access unit (FE) on which a second framework application (FR2) is implemented, wherein the arrangement is set up to perform the procedure as claimed in at least one of the Claims 1 to 11.

Images