Method for generating a communication network in an automation system

Abstract

The invention relates to a computer-implemented method (100) for generating a communication network (501) between at least one OPC UA client (502) and at least one field device (507) of an automation system (500), said method comprising: identifying at least one field device (507) of the automation system (500) using a communication gateway (400) of the automation system (500) in an identification step (101); generating an OPC UA nodeset (401) for the identified field device (507) using the communication gateway (400) in a generating step (103); and storing the OPC UA nodeset (401) on an OPC UA server (403) in a nodeset storing step (105). The invention also relates to: a data communication method (200); a data analysis method (300); a communication gateway (400); and an automation system (500).

Description

[0001] Description

[0002] Method for generating a communication network in an automation system

[0003] The invention relates to a computer-implemented method for generating a communication network between at least one OPC-IIA client and at least one field device of an automation system, a computer-implemented method for data communication between an OPC-IIA client and at least one field device of an automation system, a method for data analysis of operating information of a field device by an OPC-IIA client of a control center of an automation system, and a communication gateway.

[0004] In automation technology, analysis processes in which process operations, functionalities of individual devices, or entire plant sections are analyzed are of great importance for the error-free execution of the respective automation processes. Especially in large automation systems, where numerous different components must precisely interact to ensure error-free operation, a centralized analysis of the individual automation processes or subprocesses is particularly advantageous. The analysis processes are best carried out in central control centers of the automation system, where data from individual devices or plant sections are consolidated for analysis. This requires communication channels between the control centers and components of the automation system.

[0005] It is therefore an object of the invention to provide a computer-implemented method for generating a communication network between at least one OPC-UA client and at least one field device of an automation system, a computer-implemented method for data communication between an OPC-UA client and at least one field device of an automation system, a method for data analysis of operating information of a field device by an OPC-UA client and a communication gateway.

[0006] The object is achieved by the methods and the communication gateway of the independent claims. Preferred embodiments are specified in the dependent claims. According to one aspect of the invention, a computer-implemented method for generating a communication network between at least one OPC-11A client and at least one field device of an automation system is provided, comprising:

[0007] Identifying at least one field device of the automation system by a communication gateway of the automation system configured for data communication with the field device in an identification step;

[0008] Generating an OPC-UA node set for the identified field device by the communication gateway in one generation step; and

[0009] Storing the OPC-UA node set on an OPC-UA server in a node set storage step, wherein the OPC-UA node set stored on the OPC-UA server can be called by at least one OPC-UA client of the automation system, and wherein operating information that can be provided by the at least one field device in a data communication can be stored in the OPC-UA node set and read by the OPC-UA client.

[0010] This provides the technical advantage of providing an improved method for generating a communication network between an OPC UA client and at least one field device of an automation system. The communication network is automatically created by a correspondingly configured communication gateway. The communication gateway, along with the OPC UA client and the field devices, is part of the communication network.

[0011] The automatic generation of the communication network by the communication gateway is particularly advantageous when integrating new field devices into an existing automation system. The OPC UA node sets for the respective field devices can be automatically created during integration, thus generating the communication network. This eliminates the need for programming the respective OPC UA node sets.

[0012] The OPC UA communication standard is designed as a client-server architecture with at least one OPC server and at least one OPC UA client. The OPC UA server contains the field device information stored or provided in OPC node sets and provides services to the OPC UA client, for example, in providing the information. Similar to a conventional client-server architecture, the OPC UA client can connect to the OPC 11A server and utilize the services of the OPC 11A server. For example, the OPC 11A client can read the field device information provided in the OPC UA node sets.

[0013] The OPC UA node set comprises a plurality of nodes and references connecting the nodes in the address space of the OPC UA server. The nodes can represent objects, variables, and methods of the respective field device. In addition, nodes can represent object types or object classes, variable types or variable classes, data types or data structures, and reference types of the respective field device. The nodes of the OPC UA node set can also be assigned attributes, such as an address or a name of the node. A node representing a variable can also be assigned, for example, the attribute of the value of the respective variable, a data type, or access rights for reading or writing the respective value by an OPC UA client.The structure of the OPC UA node sets, in particular the nodes and references, can be standardized for the individual field devices according to OPC UA Companion Specifications for the respective device types of the field devices.

[0014] OPC-UA Companion Specifications describe industry-specific standards regarding the communication models to be used for data communication with devices in the respective industry.

[0015] The OPC UA client can be configured as a terminal of a control center of the automation system. The OPC UA client can be configured as a computer workstation, a PC, or a software module. The OPC UA client can also include an additional gateway for data conversion.

[0016] According to one embodiment, generating the OPC-UA node set comprises: reading at least one piece of configuration information relating to the identified field device from an internal database by the communication gateway in a first reading step, wherein the configuration information comprises information relating to a configuration of the OPC-UA node set; and

[0017] Converting the configuration information read from the internal database into the OPC UA node set in a single conversion step. This provides the technical advantage that by reading the configuration file of a specific field device from the internal database, the communication gateway is able to generate the corresponding OPC 11A node sets. The configuration information in the internal database defines at least the type of field device and the type of data that can be provided by the field device for each field device.

[0018] The configuration information can be designed in the sense of a companion specification and include all information required to individually create an OPC-11A node set.

[0019] The configuration information may, for example, include mappings that define, for a respective field device, a mapping between operating information provided by the field device and OPC-IIA variables of the OPC-UA node set.

[0020] The data structures of the OPC UA node sets can be defined or stored in a conversion module of the communication gateway. The data structures of the OPC UA node sets can be assigned to the respective field devices individually or depending on the device type.

[0021] Alternatively or additionally, the data structures of the OPC UA node sets can be defined in the conversion information for the field devices in addition to the mapping assignments.

[0022] Based on the configuration information, the communication gateway can generate the corresponding OPC UA node sets for the respective field devices. This avoids the cumbersome programming process of creating an individual OPC UA node set for each field device.

[0023] After identifying the respective field device and reading the respective configuration information, the communication gateway is able to independently create the OPC UA node sets.

[0024] According to one embodiment, the method further comprises:

[0025] Reading out from the internal database at least one piece of communication information relating to the identified field device by the communication gateway in a second reading step, wherein the communication information defines at least one communication command of a fieldbus protocol, wherein the field device can be driven to transmit the at least one operating parameter to the communication gateway via the communication command; and

[0026] Storing the at least one communication command in the communication gateway in a command storage step.

[0027] This provides the technical advantage that the communication information can be used to store the respective field device and the corresponding communication commands for a predefined fieldbus protocol in the communication gateway. By reading the communication information from the internal database, the communication gateway receives the communication commands required for data communication with the respective field device.

[0028] By reading the communication information for a specific field device from the internal database, the communication gateway is automatically able to communicate with the respective field device and request operating information from it. This eliminates the need for laborious programming of the communication gateway to enable communication with the respective field device.

[0029] The communication information can include or define parameters that are necessary for data communication between the communication gateway and the field devices according to a predefined fieldbus protocol.

[0030] According to one embodiment, the internal database comprises configuration information and / or communication information for a plurality of different field devices.

[0031] This provides the technical advantage of having a comprehensive internal database. The internal database contains configuration information and / or communication information for at least all field devices present in the automation system.

[0032] Preferably, the internal database additionally contains configuration information and / or communication information for a number of different field devices that are not currently present in the automation system but could be integrated into it in the future. This ensures that, when a new field device is integrated into the automation system, the information in the internal database can be accessed to generate the corresponding OPC-11A node sets.

[0033] According to one embodiment, the configuration information and / or communication information of the internal database is provided by manufacturers of the field devices.

[0034] This provides the technical advantage of expanding the internal database by adding new field devices. This allows the configuration and / or communication information stored in the internal database to be updated. This ensures that the corresponding configuration and / or communication information for newly available field devices that can be integrated into the automation system is already contained in the internal database. This means that when the field devices are integrated into the automation system, the corresponding information can be read from the internal database and the corresponding OPC UA node sets can be automatically generated by the communication gateway.

[0035] According to one embodiment, the method further comprises:

[0036] Copying configuration information and / or communication information relating to a plurality of field devices from an external database into the internal database set up on the communication gateway by the communication gateway in one copying step, wherein the internal database is set up on an external server.

[0037] This provides the technical advantage of making the external database easily accessible to manufacturers. This ensures that the external database can be updated at any time, allowing it to be expanded at any time with the configuration and / or communication information of the most recent field devices. The corresponding configuration and / or communication information can then be downloaded to the communication gateway's internal database for updating.

[0038] According to one embodiment, the identified field device is a newly integrated field device into the automation system. This offers the technical advantage that the communication gateway can automatically integrate a newly integrated field device into the automation system into the communication network.

[0039] According to one embodiment, the identification step comprises:

[0040] Sending an identification command through the communication gateway to field devices of the automation system in one sending step; and

[0041] Receiving an identification response of the at least one field device by the communication gateway in a receiving step, wherein at least one device identifier of the at least one field device is defined in the identification response.

[0042] This provides the technical advantage of enabling reliable identification of field devices. The identification command can be sent via the communication gateway to a plurality of field devices or to a selected field device individually. In particular, the communication gateway can send a corresponding identification command when it detects that a change has occurred in the field devices.

[0043] The change may, for example, include the integration of a new field device into the automation system. The communication gateway can then identify the field device by sending the communication command. Based on this, the respective configuration information and / or communication information of the respective field device can be read from the internal database and the corresponding OPC-IIA node sets can be generated and stored in the OPC-IIA server. This allows the communication network to be generated automatically upon identification of the new field device.

[0044] According to one aspect, a computer-implemented method for data communication between an OPC-11A client and at least one field device of an automation system is provided, comprising:

[0045] Generating a communication network between the OPC-11A client and the at least one field device of the automation system by executing the method for generating a communication network between an OPC-11A client and at least one field device according to one of the preceding embodiments by a communication gateway in a network generation step;

[0046] Receiving a communication message from the field device by the communication gateway in a message receiving step, wherein the communication message contains at least one piece of operating information relating to at least one operating parameter of the field device;

[0047] Storing the operating information regarding the operating parameter of the field device in the OPC-11A node set on the OPC-11A server in an information storage step; and providing the operating information regarding the operating parameter of the field device to the OPC-11A client via the OPC-UA node set of the OPC-11A server by the communication gateway in a provisioning step.

[0048] This makes it possible to achieve the technical advantage of providing an improved method for data communication between an OPC UA client and a field device of an automation system. To generate a communication network required for data communication, the method according to the invention for generating a communication network with the aforementioned technical advantages is first implemented.

[0049] The communication network comprises at least one OPC UA client, at least one field device, and the communication gateway according to the invention as an intermediary between the control center and the field devices of the automation system. The communication gateway is particularly capable of automatically generating the communication network. Data communication can thus be initiated automatically via the communication gateway.

[0050] According to one embodiment, communication messages of the field device are received cyclically by the communication gateway, whereby operational information of the communication messages is stored cyclically in the OPC-UA node set of the OPC-UA server.

[0051] This provides the technical advantage of ensuring reliable data communication between the control center and the field devices of the automation system. To achieve this, the operating information is provided cyclically by the identified field device, i.e., during the control cycles in which the automation system is controlled.

[0052] The operating information is written cyclically to the node sets created during the generation of the communication network and stored on the OPC UA server. Once stored on the OPC UA server, the control center can access the operating information and use it for data analysis. By providing the operating information cyclically, i.e., during control cycles, by the field device, data communication can be as simple as possible, eliminating the need for additional queries from the control center to the field device. Current data can be communicated during data communication and viewed by the controller.

[0053] The data communication primarily covers the path from the field device to the OPC-IIA client, in which the operating information is provided by the field device and can be read in by the OPC-IIA client.

[0054] According to one embodiment, the operating parameter comprises an operating time and / or an operating performance and / or a maintenance state and / or a service life and / or a next maintenance date of the field device.

[0055] This can achieve the technical advantage of communicating field device operating information that is largely ignored during the control of the automation system by a corresponding control unit. The correspondingly communicated operating information also enables analysis of the operating status of the respective field device.

[0056] By monitoring the operational information provided by the field device in a subsequent data analysis performed by the OPC UA client, the utilization of the field device can be monitored and a possible time for replacing the field device can be determined. By monitoring the operating hours, remaining service life, or a scheduled maintenance date in a subsequent data analysis, the respective field device can be replaced or serviced at the appropriate time.

[0057] According to one embodiment, the operational information of the field device stored in the OPC-UA node set is provided to the OPC-UA client via a point-to-point channel and / or a message channel and / or a publisher-subscriber channel and / or a message bus and / or a data type channel.

[0058] This can achieve the technical advantage of enabling reliable transmission of the field device's operating information from the communication gateway to the OPC UA client. According to one aspect, a method for analyzing operating information of a field device by an OPC 11A client of an automation system is provided, comprising:

[0059] Receiving operating information provided by the method for data communication between an OPC-11A client and at least one field device of an automation system according to one of the preceding embodiments by the OPC-UA client in an information receiving step;

[0060] Analyzing the operating information by the OPC-11A client in one analysis step; and

[0061] Outputting an instruction to stop operation of the field device and / or to replace the field device in an output step if the analysis has determined a malfunction and / or an operating time that has exceeded a limit and / or an operating performance that has exceeded a limit and / or a specific maintenance condition and / or an expired service life and / or a maintenance date of the field device.

[0062] This makes it possible to achieve the technical advantage of providing an improved method for data communication between an OPC-11A client and a field device of an automation system. To generate a communication network required for data communication, the method according to the invention for generating a communication network with the aforementioned technical advantages is first implemented.

[0063] The communication network comprises at least one OPC-11A client, at least one field device and the communication gateway according to the invention as an intermediary between the OPC-11A client and the field devices of the automation system.

[0064] In particular, the communication gateway is capable of automatically generating the communication network. Data communication can thus be initiated automatically through the communication gateway.

[0065] According to one aspect, a communication gateway is provided for data communication between an OPC-UA client and at least one field device of an automation system, wherein the communication gateway is configured to execute the method for generating a communication network according to one of the preceding embodiments and / or the method for executing data communication between an OPC-UA client and at least one field device of an automation system according to one of the preceding embodiments.

[0066] This makes it possible to achieve the technical advantage that an improved communication gateway can be provided which is configured to carry out the method for generating a communication network and the method for data communication with the technical advantages described above.

[0067] In particular, the communication gateway is capable of generating the communication network automatically and without the intervention of a developer. Especially for newly integrated field devices in the automation system, the communication gateway is capable of generating corresponding OPC UA node sets and using these to generate the communication network.

[0068] According to one embodiment, the communication gateway comprises: an internal database with configuration information and / or communication information relating to a plurality of different field devices; and / or a fieldbus module, wherein the fieldbus module is configured to send communication commands to field devices in a fieldbus protocol and / or to receive communication messages from field devices and / or to identify field devices;and / or a parsing module configured to read configuration information and / or communication information relating to the field devices of the automation system from the internal database, wherein the configuration information comprises information relating to a configuration of the OPC-UA node set, wherein the communication information defines at least one communication command of a fieldbus protocol, and wherein, via the communication command, a field device can be driven to transmit at least one piece of operating information of the field device to the communication gateway; and / or a conversion module, wherein the conversion module is configured to generate a corresponding OPC-UA node set for each identified field device of the automation system based on the configuration information of the field devices; and / or an OPC-UA server for storing the OPC-UA node sets of the identified field devices;and / or an OPC-UA communication interface, wherein the communication gateway is connectable to an OPC-UA client via the OPC-UA communication interface, and wherein the OPC-UA node set is provided to the OPC-UA client via the OPC-UA communication interface. This can achieve the technical advantage that the communication gateway, via the plurality of different modules, is capable of automatically and without user intervention executing the method for generating a communication network and the method for data analysis. In particular, in the event of changes in the automation system, for example, when a field device is replaced, the communication gateway can independently create the communication network.

[0069] This eliminates the need for a developer to laboriously create a corresponding OPC-IIA node set or configure the configuration for the newly integrated field device into the automation system. Any interruption to the automation system can thus be limited to replacing the field devices.

[0070] According to one aspect, an automation system is provided with at least one field device, at least one OPC-UA client and a communication gateway according to one of the preceding embodiments, wherein the OPC-UA client is configured to execute the method for data analysis.

[0071] This can achieve the technical advantage of providing an automation system that is configured to perform data analysis with the technical advantages described above.

[0072] According to one embodiment, the OPC-UA client is implemented in a terminal of a control center in a cloud server.

[0073] This offers the technical advantage of enabling centralized analysis of field device operating information. Using a cloud server also allows for the increased computing capacity provided by such server types.

[0074] The invention is explained in more detail with reference to the accompanying figures. Herein:

[0075] Fig. 1 is a schematic representation of an automation system with a communication gateway according to an embodiment;

[0076] Fig. 2 is a flowchart of a computer-implemented method for generating a communication network between at least one OPC-UA client and at least one field device of an automation system according to one embodiment;

[0077] Fig. 3 shows a further flowchart of the computer-implemented method for generating a communication network between at least one OPC-11A client and at least one field device of an automation system according to a further embodiment;

[0078] Fig. 4 shows a further flowchart of the computer-implemented method for generating a communication network between at least one OPC-11A client and at least one field device of an automation system according to a further embodiment;

[0079] Fig. 5 is a flowchart of a computer-implemented method for data communication between an OPC-11A client and at least one field device of an automation system according to one embodiment; and

[0080] Fig. 6 is a flowchart of a computer-implemented method for data analysis of operational information of a field device by an OPC-11A client of an automation system according to one embodiment.

[0081] Fig. 1 shows a schematic representation of an automation system 500 with a communication gateway 400 according to an embodiment.

[0082] In the embodiment shown, the automation system 500 comprises a communication gateway 400. The communication gateway 400 is connected to a plurality of field devices 507 via a fieldbus 517. The automation system 500 further comprises an OPC-IIA client 502. The OPC-IIA client 502 can be connected to a communication interface 427 of the communication gateway 400 via a wireless data connection 515. Alternatively, the data connection can also be wired.

[0083] In the embodiment shown, the OPC-11A client 502 is embodied as a terminal 503 of a control center 505 of the automation system 500. In the embodiment shown, the control center 505 is embodied as a cloud server 513 and is connected to the communication interface 427 of the communication gateway 400 via the wireless data connection 515.

[0084] In the embodiment shown, the communication gateway 400 comprises an internal database 407. Configuration information 409 and / or communication information 411 for a plurality of different field devices 507 are stored in the internal database 407.

[0085] The communication gateway 400 further comprises a parsing module 423. The parsing module 423 is configured to search the internal database 407 for corresponding information and to read this information from the internal database 407.

[0086] The communication gateway 400 further comprises a fieldbus module 421. The fieldbus module 421 is configured to carry out data communication according to a fieldbus protocol of the fieldbus 517 with the plurality of field devices 507 of the automation system 500.

[0087] The communication gateway 400 further comprises a conversion module 425. The conversion module 425 is configured to convert information that it receives from both the parsing module 423 and the fieldbus module 421 into the OPC-LIA communication standard.

[0088] In the embodiment shown, the communication gateway 400 further comprises an OPC-LIA server 403. OPC-UA node sets 401 for various field devices 507 of the automation system 500 can be stored on the OPC-LIA server 403 in accordance with the OPC-UA communication standard.

[0089] In the embodiment shown, the automation system 500 further comprises an external database 509 executable on an external server 511. The external database 509 is connected to the communication gateway 400 via a further wireless data connection 516.

[0090] The communication gateway 400 according to the invention is configured to execute the method according to the invention for generating a communication network 501 between an OPC-11A client 502 and at least one field device 507 of the automation system 500.

[0091] In the sense of the application, the communication network 501 comprises at least one OPC-LIA client 502, at least one field device 507 and the communication gateway 400.

[0092] To generate a communication network 501 according to the invention, the communication gateway 400 first identifies at least one field device 507 of the plurality of field devices 507 of the automation system 500.

[0093] Alternatively, a plurality of field devices 507, possibly all field devices 507, of the automation system 500 can be identified.

[0094] For this purpose, the communication gateway 400 can send at least one identification command 415 via the fieldbus module 421 to the field devices 507 via the fieldbus 517. The identification command 415 can be sent as a common identification command 415 to all field devices 507 of the automation system 500. Alternatively or additionally, identification commands 415 can be sent to individual selected field devices 507. In the identification command 415, the respective field devices 507 are requested to identify themselves to the communication gateway 400.

[0095] For this purpose, the field devices 507 that received the respective identification command 415 send a corresponding identification response 417 to the communication gateway 400. The identification response 417 defines at least one device identifier and / or a device type of the respective field device 507. Using the information in the identification response 417, the respective field device 507 can thus be identified, for example, as a sensor or actuator of a certain type, i.e., as a temperature sensor or pressure sensor, or as a servo motor of a specific design.

[0096] The corresponding information of the identification response 417 is subsequently forwarded by the fieldbus module 421 to the parsing module 423. The identification response 417 can include a device identification code by which the respective field device 507 can be uniquely identified. The device identification code can be defined according to the HART protocol. Alternatively or additionally, the identification response 417 can include information regarding the device type of the respective field device 507.

[0097] The parsing module 423 is then able, based on the information of the identification response 417, in which at least the device type or the device identifier of the respectively identified field device 507 is specified, to search the internal database 407 for corresponding information stored for field devices 507 of the respective device type.

[0098] The internal database 407 preferably stores configuration information 409 and / or communication information 411 for a plurality of different field devices 507 of different device types or different models of the same device type.

[0099] The parsing module 423 searches the configuration information 409 and / or communication information 411 of the respective field device 507 for the device identification code, i.e. the device identifier, of the field device 507.

[0100] Alternatively, the configuration information 409 or communication information 411 can also be stored in the internal database 407 according to the respective device types or device types of the field devices 705. The parsing module 423 can then be configured to search the internal database 407 for the device types.

[0101] The configuration information 409 stored for the various field devices 507 in the internal database 407 includes information regarding configurations of OPC-LIA node sets 401 of the respective field devices 507.

[0102] The configuration information 409 can comprise mapping assignments, wherein the mapping assignments define which operating information 405 or operating parameters of the field devices 507 are to be mapped to which OPC-LIA variables of the field devices 507 of a respectively assigned OPC-UA node set 401.

[0103] The data structures of the OPC UA node sets 401 can be defined or stored in a conversion module 425. The data structures of the OPC UA node sets 401 can be assigned to the respective field devices 507 individually or depending on the device types of the field devices 507. With individual assignment, the data structures or information regarding the data structures can be stored with reference to the device identification codes of the field devices 507.

[0104] The data structure here refers to the non-instantiated structure of the nodes and references of an OPC-UA Nodeset 401.

[0105] Alternatively or additionally, in addition to the mapping assignments, the data structures of the OPC UA node sets 401 can be defined in the conversion information for the field devices 507.

[0106] Alternatively or additionally, configurations of the respective field devices 507 or a design of corresponding OPC UA node sets 401 for field devices 507 of the respective type can be defined in the configuration information 409. The configuration information 409 can define the individual characteristics of the field device 507, for example, the sensor or actuator type of the respective field device 507, as well as the data types of the information that can be provided by the field device 507.

[0107] The information of the configuration information 409 or the data structures of the non-instantiated OPC-UA node sets 401 can be structured according to the information of a companion specification for the OPC-UA standard.

[0108] Taking into account the mapping assignments of the configuration information 409 and the data structures of the OPC UA node sets 401, the conversion module 425 is able to generate correspondingly instantiated OPC UA node sets 401 for the field devices 507. In the instantiated node sets 401, which are each individually and uniquely assigned to the field devices 507, an OPC UA variable of the respective OPC UA node set 401 is in turn uniquely assigned to each possible operating parameter that can be provided by a field device 507. Through instantiation, the values ​​of the respective operating parameters that can be provided to the communication gateway 400 by the field devices 507 through data communication via the fieldbus protocol can be written into the OPC UA variables of the OPC UA node sets 401 that are respectively assigned to the operating parameters.

[0109] The instantiated OPC-UA node sets 401 can be stored in the OPC-UA memory 403. By writing the values ​​of the operating parameters into the OPC-UA variables of the OPC-UA node sets 401 provided for this purpose according to the conversion information 409, the current values ​​of the operating parameters provided by the field devices 507 can be stored in the OPC-UA server 403. The communication information 411 defines parameters necessary for data communication between the communication gateway 400 and the field devices 507 according to a predefined fieldbus protocol.

[0110] For example, when using the HART protocol as a fieldbus protocol, the following information can be defined in the communication information 411 for each parameter to be read out or each operating information 405 of the field devices 507:

[0111] - HART Command

[0112] - Write Data

[0113] - WriteLength

[0114] - ByteOffset

[0115] - ReadLength

[0116] - Type

[0117] HART-Command describes the communication command 413 of the HART protocol required for communication. Using the communication command 413, the addressed field device 507 can be requested to transmit requested information. Depending on the requested information, multiple communication commands 413 can be defined for a field device 507 in the respective communication information 411. WriteData defines the data to be written. WriteLength defines the length of the data to be written. ByteOffset defines in which part of the sent response the information to be read is located. ReadLength defines the length of the data to be read. Type defines the data type of the data to be read.

[0118] The contents of the communication information 411 described above refer only to the HART protocol by way of example. The present invention is also applicable to other fieldbus protocols. For other fieldbus protocols, the communication information 411 may include information or communication commands 413 that differ from the information or communication commands 413 described above.

[0119] The communication information 411 thus comprises at least communication commands 413, by means of which data communication between the communication gateway 400 and the field devices 507 is enabled in accordance with the respective fieldbus protocol used.

[0120] The communication information 411 can be defined for the respective field device 507 analogously to the configuration information 409, i.e., the communication information 411 can be stored individually in the internal database 407 for the field devices 507, for example, under the respective device identification code. Alternatively, the communication information 411 can be adapted to specific device types or specific device versions of the field devices 507 and can differ for different field devices 507 of different device types or different versions.

[0121] The internal database 407 thus comprises corresponding configuration information 409 and / or communication information 411 for at least a majority of the field devices 507, preferably for all field devices 507, of the automation system 500.

[0122] After parsing the internal database 407, the parsing module 423 transmits the configuration information 409 of the respectively identified field device 507 to the conversion module 425.

[0123] The conversion module 425 is designed to generate at least one corresponding OPC-LIA node set 401 for the respective field devices based on the configuration information 409.

[0124] For this purpose, the conversion module 425 can take into account the correspondingly stored data structures of the OPC-UA node sets 401 and the mapping assignments based on the configuration information 409 for the field devices 507 of the automation system 500 and generate correspondingly instantiated OPC-UA node sets 401 for the field devices 507.

[0125] In the instantiated OPC-UA node sets 401, uniquely assigned OPC-UA variables are defined in the corresponding OPC UA node sets 401 for the possible operating parameters that can be provided by the field devices 507.

[0126] The OPC-UA Nodesets 401 instantiated in this way can then be stored in the OPC-UA Server 403.

[0127] According to the mapping assignments of the configuration information 409, the conversion module 425 can then write the values ​​of the operating information 405 or operating parameters provided by the field devices 507 into the correspondingly provided OPC-UA variables of the respective OPC-UA node sets 401 and store them in the OPC-UA server 403. The instantiated OPC-UA node set 401 generated accordingly based on the configuration information 409 is individually adapted to a respectively identified field device 507 and has the data structure defined for a field device 507 of the respective device type in accordance with the OPC-LIA standard, i.e., in accordance with corresponding companion specifications or in accordance with a customer request compatible with the OPC-LIA standard.

[0128] Furthermore, the parsing module 423 transmits the communication information 411 read from the internal database 407 for the respectively identified field device 507 to the fieldbus module 421. The fieldbus module 421 stores the information of the communication information 411 including the communication commands 413 and is thus configured to communicate with the identified field device 507 via the respective fieldbus protocol and to request it to transmit the desired information.

[0129] The OPC-LIA client 502 can connect to the communication gateway 400 via the wireless data connection 515 and read the OPC-LIA node sets 401 stored in the OPC-LIA server 403. Depending on any personalized access rights, the OPC-LIA client 502 can also write to variables of the OPC-UA node sets 401.

[0130] According to the invention, the communication network 501 is thereby generated between the OPC UA client 502 and the respectively identified field device 507.

[0131] Preferably, the communication gateway 400 creates corresponding OPC-UA node sets 401 for all field devices 507 of the automation system 500 by reading the configuration information 409 from the internal database 407 and stores them in the OPC-UA server 403.

[0132] Furthermore, for all identified field devices 507, the corresponding communication commands 413 of the communication information 411 are stored in the fieldbus module 421, so that the fieldbus module 421 is configured to carry out data communication with the field devices 507 based on the fieldbus protocol.

[0133] According to the invention, the generation of the communication network 501 is carried out automatically by the communication gateway 400. In particular, when a new field device 507 is integrated into the existing automation system 500, corresponding OPC-UA node sets 401 can thus be automatically generated and stored in the OPC-UA server 403, and the respective communication commands 413 of the communication information 411 can be stored in the fieldbus module 421. For this purpose, when a new field device 507 is integrated into the automation system 500, the communication gateway 400 receives information that a new field device 507 has been integrated into the automation system 500 and subsequently sends a corresponding identification command 415.

[0134] Similarly, when an automation system 500 is started up again, the communication gateway 400 can carry out a corresponding identification of the field devices 507 for the field devices 507 integrated in the automation system 500 and, based on this, generate the respective OPC UA node sets 401 by reading in the configuration information 409 and communication information 411 stored for the respective field devices 507 in the internal database 407 and store them in the OPC LIA server 403 and store the respective configuration information 409 in the fieldbus module 421.

[0135] A cumbersome programming process in which a corresponding OPC-UA Nodeset 401 must be manually created for each new field device 507 and corresponding communication commands 413 must be generated, is thus eliminated.

[0136] After generating the communication network 501, the communication gateway 400 is able to execute the inventive method for data communication between an OPC UA client 502 and at least one field device 507 of an automation system 500.

[0137] After setting up the communication network 501 between the OPC-UA client 502 and at least one field device 507, the communication gateway 400 receives a communication message 419 from the at least one identified field device 507 for data communication between the OPC-UA client 502 and the field device 507.

[0138] The communication message 419 includes operating information 405 of the respective field device 507. The communication message 419 can be received cyclically by the communication gateway 400. For this purpose, the at least one field device 507 or all field devices 507 of the automation system 500 cyclically transmit corresponding communication messages 419. The respective communication messages 419 contain current operating information 405 of the respective field devices 507. For this purpose, the communication gateway 400 can cyclically transmit a corresponding request to the field devices 507 to transmit the communication information 411.

[0139] The cyclic transmission of communication messages 419 by field devices 507 can occur, for example, during control cycles of automation system 500. Alternatively or additionally, communication messages 419, including the operating information 405 contained therein, can also be transmitted acyclically by field devices 507.

[0140] According to one embodiment, the communication gateway 400 can first send corresponding communication commands 413 to the respective field devices 507 to trigger the field devices 507 to transmit the communication messages 419. The transmitted communication commands 413 trigger the field devices 507 that receive the commands to transmit the respective communication messages 419.

[0141] This can be done, for example, in particular in the case of an acyclic transmission of the communication messages 419 by the field devices 507, in which the communication messages 419 are transmitted, for example, between successive control cycles of the automation system 500.

[0142] The communication messages 419, as well as the communication commands 413, are defined according to the fieldbus protocol used.

[0143] The transmitted communication commands 413 can correspond to the communication information 411 of the internal database 407 stored in the fieldbus module 421.

[0144] Depending on the transmitted communication commands 413, the subsequently transmitted communication messages 419 of the field devices 507 can contain different operating information 405. Communication commands 413 can therefore be directed to retrieving different operating information 405 from the respective field devices 507.

[0145] After receiving the communication messages 419, the operating information 405 contained therein is forwarded by the fieldbus module 421 to the conversion module 425. The conversion module 425 is configured to write the operating information 405 of the field devices 507 into the OPC-LIA node sets 401 assigned to the respective field devices 507 and to store the OPC-UA node sets 401 on the OPC-LIA server 403 for the respective field devices 507.

[0146] According to one embodiment, operating information 405 of the field devices 507 for a plurality of consecutive control cycles is stored in the OPC-UA server 403, in particular in the respective OPC-UA node sets 401.

[0147] The operating information 405 stored in the OPC-UA node sets 401 of the OPC-UA server 403 can subsequently be viewed by the respective OPC-UA client 502.

[0148] For this purpose, the respective OPC-UA client 502 can send corresponding read commands to the communication interface 427 of the communication gateway 400 via the wireless data connection 515. This enables the OPC-UA client 502 to call the OPC-UA node sets 401 stored for a specific field device 507 in the OPC-UA server 403 and to read the operating information 405 stored therein.

[0149] The data communication between the OPC UA client 502 and the communication gateway 400 can take place via a point-to-point channel and / or a message channel and / or a publisher-subscriber channel and / or a message bus and / or a data type channel.

[0150] By reading in, which may also include uploading the operating information 405 stored in the OPC-UA server 403, for example, to a terminal 503 of the control center 505 or to the cloud server 513, the OPC-UA client 502, i.e. the terminal of the control center 503, is able to carry out or cause a data analysis of the operating information 405 of the field devices 507 of the automation system 500.

[0151] For this purpose, the operating information 405 can include, for example, operating parameters of the respective field devices 507. The operating parameters can include, for example, an operating time of the respective field device 507, an average load or a maximum or minimum load of the respective field device 507, an upcoming maintenance date of the respective field device 507, an error message of the respective field device 507, or other parameters describing the functionality or operating load of the respective field device 507. Alternatively or additionally, the operating information 405 can include information regarding a last calibration, such as the date of the calibration, information regarding the hardware version and / or software version of the field device 507, information regarding a temperature of the electronics of the field device 507, information regarding device-specific counter variables, and other device-specific information.

[0152] Alternatively or additionally, the operating information 405 may further comprise actual user data of the respective field devices 507, for example measurement data from sensors of the automation system 500.

[0153] The operating information 405 can further describe defined operating ranges of the respective field devices 507. The operating ranges can, for example, define a power or revolution range in which a motor can be operated, or a pressure or temperature range in which a pressure or temperature sensor of the automation system 500 can be operated.

[0154] Based on the operating information 405 of the various field devices 507, the control center 505 can perform a corresponding analysis of the functionality or use of the field devices 507 in the automation system 500. Based on this, the operation of the automation system 500 can be optimized.

[0155] According to one embodiment, the fieldbus protocol used is a HART protocol. The respective communication information 411 defines corresponding HART commands, by means of which data communication based on the HART protocol is enabled between the communication gateway 400 and the field devices 507 of the automation system 500.

[0156] According to one embodiment, the internal database 407 of the communication gateway 400 is in the form of at least one JSON file.

[0157] According to a further embodiment, the data communication between the control center 505 and the field devices 507 of the automation system 500 can take place according to the NAMUR Open Architecture NOA.

[0158] For this purpose, the communication network 501, including the OPC UA client 502 or the control center 505, the field devices 507, and the communication gateway 400, defines a second communication channel for data communication between the field devices 507 and a control unit of the automation system 500. Data communication via the communication network 501 can thus occur in parallel with the data communication between the control unit and the field devices 507.

[0159] The operating information 405 transmitted via the communication messages 419 of the field devices 507 to the communication gateway 400 can thus be provided in addition to the user data provided by the field devices 507 to the control unit of the automation system 500 during the control cycles. The communication network 501 can thus enable data communication that is largely independent of the cyclic data communication between the field devices 507 and the control unit of the automation system 500.

[0160] According to one embodiment, the communication gateway 400 and / or the OPC UA server 403 and / or the internal database 407 are integrated into a control unit, for example a programmable logic controller (PLC).

[0161] Fig. 2 shows a flowchart of a computer-implemented method 100 for generating a communication network 501 between at least one OPC-LIA client 502 and at least one field device 507 of an automation system 500 according to one embodiment.

[0162] To generate a communication network 501 between at least one OPC UA client 502 and at least one field device 507 of an automation system 500, in an identification step 101, at least one field device 507 of the automation system 500 is first identified by a communication gateway 400 of the automation system 500.

[0163] Through the identification, at least one device type of the respectively identified field device 507 can be determined.

[0164] The identification of the field devices 507 can be performed for selected field devices 507. Alternatively or additionally, a plurality of field devices 507, possibly all field devices 507 of the automation system 500, can be identified.

[0165] The identification can be performed, for example, during startup of the automation system 500. Alternatively or additionally, the identification can be performed repeatedly at predetermined time intervals during operation of the automation system 500.

[0166] Alternatively or additionally, the identification, in particular of selected field devices 507, can be carried out when predefined events occur.

[0167] These predefined events may, for example, include the reintegration of a field device 507 into the existing automation system 500. The newly integrated field device 507 would thus be automatically identified by the communication gateway 400.

[0168] Alternatively or additionally, such an event may include an update of the external database 509 of the external server 511. The external database 509 is accessible to the manufacturers of the field devices 507. In the event of changes to existing field devices 507 or the development of new field devices 507, the external database 509 can be provided with corresponding information by the respective manufacturers of the field devices 507.

[0169] Via the wireless data connection 515 between the communication gateway 400 and the external server 511, the information of the external database 509 can be integrated into the internal database 407 of the communication gateway 400 in order to keep the internal database 407 of the communication gateway 400 up to date.

[0170] If changes are made to the internal database 407 of the communication gateway 400, the existing communication networks 501 can be regenerated according to the steps described above in order to be able to take into account any new information from the updated internal database 407.

[0171] In a generation step 103, at least one OPC-UA node set 401 is subsequently generated for the identified field device 507 by the communication gateway 400. The OPC-UA node set 401 is adapted to the device type of the respective identified field device 507 in accordance with the OPC-UA communication standard.

[0172] In a node set storage step 105, the at least one OPC-UA node set 401 of the identified field device 507 is stored on an OPC-UA server 403 of the communication gateway 400. The OPC-UA node set 401 stored on the OPC-UA server 403 can be accessed by at least one OPC-11A client 502. Furthermore, operating information 405 of the respectively identified field device 507 can be stored in the OPC-LIA node set 401 and thus read by the OPC-LIA client 502.

[0173] According to the invention, the correspondingly generated communication network 501 comprises at least one OPC-LIA client 502, at least one identified field device 507 and the communication gateway 400, which is data-technically connected to both the OPC-LIA client 502 and the field device 507.

[0174] Data communication between the OPC-LIA client 502 and the respective field device 507 of the generated communication network 501 can thus be moderated via the communication gateway 400.

[0175] Fig. 3 shows a further flowchart of the computer-implemented method 100 for generating a communication network 501 between at least one OPC UA client 502 and at least one field device 507 of an automation system 500 according to a further embodiment.

[0176] The embodiment shown is based on the embodiment in Figure 2 and includes all method steps described there.

[0177] In contrast to the embodiment in Figure 2, in the embodiment shown, after the identification of the field device 507 or the plurality of field devices 507, in a first readout step 107, at least one piece of configuration information 409 relating to the respectively identified field device 507 is read out from an internal database 407 by the communication gateway 400.

[0178] The configuration information 409 includes information regarding a configuration of the OPC-LIA node set 401 of the respective field device 507.

[0179] The configuration information 409 can, for example, comprise mapping assignments that define assignments between the operating information 405 or operating parameters that can be provided by the field device 507 and the corresponding OPC-LIA variables of the OPC-UA node sets 401 assigned to the field devices 507.

[0180] For this purpose, the corresponding data structures of the non-instantiated OPC-UA node sets 401 can be stored, for example, in the conversion module 425. Alternatively, the data structures of the non-instantiated OPC-UA node sets 401 are stored in another memory location such that the conversion module 425 can access them and instantiate the non-instantiated OPC-UA node sets 401 using the conversion information 409.

[0181] The operating information 405 or operating parameters that can be provided by the field devices 507 can include, for example, a measured variable, such as a temperature or a pressure with a corresponding unit or an operating time, an average, maximum or minimum utilization of the field device 507, a planned maintenance date, an expected service life, or similar parameters describing the operation or functionality of the respective field device 507.

[0182] In a conversion step 109, the communication gateway 400 subsequently converts the configuration information 409 read from the internal database 407 into the corresponding OPC-UA node set 401 of the respectively identified field device 507.

[0183] For this purpose, the conversion module 425 can adapt the data structures of the non-instantiated OPC-UA node sets 401 predefined for the individual field devices 507 to the respective field devices 507, for example to a field device 507 newly integrated into the automation system 500, according to the mapping assignments, and thereby generate an instantiated OPC-UA node set 401. In the instantiated OPC-UA node set 401, according to the conversion information 409 of the internal database 407, at least one variable of the OPC-UA node set 401 is uniquely defined for each operating parameter that can be provided by a respective field device 507, into which variable a respective value of the operating parameter is to be written.

[0184] The predefined data structures of the non-instantiated OPC-UA node sets 401 are defined in accordance with the provisions of the OPC-UA protocol standard and, if applicable, in accordance with the corresponding companion specifications for a field device 507 of the respective type.

[0185] Alternatively or in addition to the first readout step 107, in a second readout step 111, the communication gateway 400 reads communication information 411 from the internal database 407 for the respectively identified field device 507. The communication information 411 defines at least one communication command 413 of a fieldbus protocol for the respective field device 507. The communication command 413 is designed to drive the field device 507 to transmit or provide the at least one operating parameter or to provide the operating information 405 in a data communication between the communication gateway 400 and the respective field device 507.

[0186] Depending on the complexity of the respective field device 507 or the number of different operating information items 405, including various operating parameters, that can be provided by the field device 507 in a data communication, the communication information 411 for the respective field device 507 can include a corresponding number of communication commands 413. A communication command 413 can be precisely tailored to requesting a specific operating parameter.

[0187] In a command storage step 113, the at least one communication command 413 of the communication information 411 of the respective field device 507 is subsequently stored in the communication gateway 400. By storing the at least one communication command 413 in the communication gateway 400, the communication gateway 400 is configured to drive the respective field device 507 in a data communication with the latter to provide the corresponding operating information 405.

[0188] Fig. 4 shows a further flowchart of the computer-implemented method 100 for generating a communication network 501 between at least one OPC UA client 502 and at least one field device 507 of an automation system 500 according to a further embodiment.

[0189] The embodiment shown is based on the embodiment in Figure 3 and includes all method steps described there.

[0190] In the embodiment shown, in a copying step 115, the communication gateway 400 first copies configuration information 409 and / or communication information 411 from the external database 509 to the internal database 407. The copying can occur automatically at predetermined time intervals. Alternatively or additionally, the copying can be executed in an event-driven manner upon the occurrence of a predefined event, such as the startup of the automation system 500, the addition of a new field device 507 to the automation system 500, or an update or change to the information in the external database 509.

[0191] In contrast to the embodiment in Figure 3, in the embodiment shown, the identification of the at least one field device 507 by the communication gateway 400 in the identification step 101 comprises the execution of a transmission step 117.

[0192] In transmission step 117, the communication gateway 400 sends an identification command 415 to the field devices 507 of the automation system 500. The identification command 415 is configured to drive the respective field devices 507 to transmit an identification response 417 after receiving the respective identification command 415.

[0193] The identification command 415 can be sent to individual selected field devices 507, to a plurality of field devices 507 or preferably to all field devices 507 of the automation system 500.

[0194] In a receiving step 119, an identification response 417 from the respective field devices 507 is received by the communication gateway 400 to identify the field devices 507. The identification response 417 includes at least one device identifier of the respective field device 507, via which the field device 507 can be identified. Identifying the respective field device 507 can include at least determining a device type of the respective field device 507.

[0195] After setting up the OPC-UA node sets 401 in the OPC-UA server 403 according to the configuration information 409 stored in the internal database 407 for the respective field devices 507 and after saving the communication information 411 stored in the internal database 407 for the respective field devices 507, including the communication commands 413 contained therein, the communication gateway 400 is set up for data communication with the respective field devices 507.

[0196] The respective communication network 501 is thus installed. Fig. 5 shows a flowchart of a computer-implemented method 200 for data communication between an OPC-LIA client 502 and at least one field device 507 of an automation system 500 according to one embodiment.

[0197] For data communication between an OPC-LIA client 502 and at least one field device 507 of the automation system 500, in a network generation step 201, a communication network 501 is first generated between the OPC-LIA client 502 and the at least one field device 507 of the automation system 500 by executing the above-described inventive method 100 for generating a communication network 501.

[0198] In a message reception step 203, after the communication network 501 has been successfully generated by the communication gateway 400, a communication message 419 from a field device 507 is received. The communication message 419 includes at least one piece of operating information 405 of the respective field device 507. The operating information 405 includes at least one operating parameter of the field device 507.

[0199] In an information storage step 205, the operating parameter of the operating information 405 of the field device 507 is subsequently stored in the OPC-UA node set 401 stored on the OPC-LIA server 403 for the respective field device 507.

[0200] By storing the operating parameter of the field device 507 in the OPC-UA node set 401, the information regarding the respective operating parameter, i.e. the operating information 405 of the respective field device 507, is provided to the OPC-UA client 502, which is connected to the communication gateway 400 via data communication and can access the OPC-UA server 403 and the OPC-UA node sets 401 stored thereon, in a provisioning step 207.

[0201] The OPC-UA client 502 can then read the information contained in the operating information 405 regarding the operating parameter by calling the respective OPC-UA node set 401 of the respective field device 507. Alternatively or additionally, the respective information can be uploaded by the OPC-UA client 502 to a PC or external server or similar.

[0202] This enables data communication between the OPC UA client 502 and the respective field device 507. Fig. 6 shows a flowchart of a computer-implemented method 300 for analyzing operating information 405 of a field device 507 by an OPC LIA client 502 of an automation system 500 according to one embodiment.

[0203] In order to carry out a data analysis of operating information 405 of a field device 507 by an OPC-LIA client 502, in an information reception step 301, operating information 405 of a corresponding field device 507, provided according to the above-described inventive method 200 for data communication between an OPC-LIA client 502 and at least one field device 507, is first received by the respective OPC-LIA client 502.

[0204] As described above, receiving can comprise reading the operating information 405 stored in the respective OPC-LIA node set 401 by the OPC-LIA client 502 and / or uploading the respective operating information 405 of the OPC-UA node set 401 to the OPC-UA client 502, i.e. the control center 505.

[0205] In an analysis step 303, the operating information 405 is analyzed by the OPC-UA client 502.

[0206] The analysis of the operating information 405 or in particular of the operating parameters of the respective field device 507 contained therein can comprise various analysis steps 303.

[0207] For example, the utilization of a field device 507 can be determined by analyzing the operating hours performed by the field device 507 up to the time of data analysis. Alternatively or additionally, malfunctions of the field device 507 can be identified or analyzed.

[0208] Alternatively or additionally, it can be checked whether the respective field device 507 is operated in the intended load range.

[0209] Alternatively or additionally, a predefined maintenance date for the respective field device 507 can be identified or evaluated in the analysis.

[0210] The possible analysis steps 303 mentioned here are merely exemplary and are not intended to limit the present invention. In addition to the steps mentioned here, further analysis steps 303 are also conceivable, which may vary depending on the design of the respective field device 507 or depending on the use of the respective field device 507 in the automation system 500.

[0211] If, in the analysis of the operating information 405, a malfunction of the field device 507 and / or an exceedance of a limit value defined for the operating time of the field device 507 and / or an expired service life of the field device 507 and / or a due date for a maintenance appointment of the field device 507 is determined, an instruction to stop the operation of the respective field device 507 and / or to replace the respective field device 507 is output in an output step 305.

[0212] In addition to the conditions mentioned, further conditions may also result in a corresponding action instruction being issued when the respective condition is identified during the analysis.

[0213] The action instruction can, for example, be issued by the control center 505 to a control unit of the automation system 500 in order to stop the execution of the respective field device 507.

[0214] If, however, none of the conditions mentioned that lead to the output of an action instruction according to the output step 305 are detected in the analysis of the analysis step 303, the operation of the respective field device 507 in the automation system 500 is continued in an operating step 307.

[0215] List of reference symbols

[0216] 100 procedures

[0217] 101 Identification step

[0218] 103 Generation step

[0219] 105 Nodeset storage step

[0220] 107 first selection step

[0221] 109 Conversion step

[0222] 111 second reading step

[0223] 113 Instruction storage step

[0224] 115 Copy step

[0225] 117 Send step

[0226] 119 Receiving step

[0227] 200 procedures

[0228] 201 Network generation step

[0229] 203 Message reception step

[0230] 205 Information storage step

[0231] 207 Deployment step

[0232] 300 procedures

[0233] 301 Information reception step

[0234] 303 Analysis step

[0235] 305 Output step

[0236] 307 Operating step

[0237] 400 Communication Gateway

[0238] 401 OPC-UA Nodeset

[0239] 403 OPC UA Server

[0240] 405 Operating information

[0241] 407 internal database

[0242] 409 Configuration information

[0243] 411 Communication information

[0244] 413 Communication command

[0245] 415 Identification Order

[0246] 417 Identification response

[0247] 419 Communication message 421 Fieldbus module

[0248] 423 Parsing module

[0249] 425 Conversion module

[0250] 427 Communication interface

[0251] 500 automation system

[0252] 501 communication network

[0253] 502 OPC UA Client

[0254] 503 Terminal 505 Control Center

[0255] 507 field device

[0256] 509 external database

[0257] 511 external server

[0258] 513 cloud servers

[0259] 515 Wireless data connection

[0260] 516 additional wireless data connections

[0261] 517 Fieldbus

Claims

Claims 1. Computer-implemented method (100) for generating a communication network (501) between at least one OPC-LIA client (502) and at least one field device (507) of an automation system (500), comprising: identifying at least one field device (507) of the automation system (500) by a communication gateway (400) of the automation system (500) set up for data communication with the field device (507) in an identification step (101); Generating an OPC-UA node set (401) for the identified field device (507) by the communication gateway (400) in a generation step (103); and storing the OPC-UA node set (401) on an OPC-UA server (403) in a node set storage step (105), wherein the OPC-UA node set (401) stored on the OPC-UA server (403) can be called by at least one OPC-UA client (502) of the automation system (500), and wherein operating information that can be provided by the at least one field device (507) in a data communication can be stored in the OPC-UA node set (401) and read by the OPC-UA client (502).

2. The method (100) according to claim 1, wherein generating the OPC-UA node set (401) comprises: Reading out from an internal database (407) at least one piece of configuration information (409) relating to the identified field device (507) by the communication gateway (400) in a first reading step (107), wherein the configuration information (409) comprises information relating to a configuration of the OPC-UA node set (401); and Converting the configuration information (409) read from the internal database (407) into the OPC-UA node set (401) in a conversion step (109).

3. The method (100) of claim 1 or 2, further comprising: Reading out from the internal database (407) at least one piece of communication information (411) relating to the identified field device (507) by the communication gateway (400) in a second reading step (111), wherein the communication information (411) defines at least one communication command (413) of a fieldbus protocol, wherein the field device (507) is drivable to transmit the at least one operating parameter to the communication gateway (400); and Storing the at least one communication command (413) in the communication gateway (400) in a command storage step (113).

4. The method (100) according to claim 2 or 3, wherein the internal database (407) comprises configuration information (409) and / or communication information (411) relating to a plurality of different field devices (507).

5. The method (100) according to any one of the preceding claims 2 to 4, wherein the configuration information (409) and / or communication information (411) of the internal database (407) is provided by manufacturers of the field devices (507).

6. The method (100) according to any one of the preceding claims 2 to 5, further comprising: Copying configuration information (409) and / or communication information (411) relating to a plurality of field devices (507) from an external database (509) into the internal database (407) set up on the communication gateway (400) by the communication gateway (400) in a copying step (115), wherein the internal database (407) is set up on an external server (511).

7. The method (100) according to any one of the preceding claims, wherein the identified field device (507) is a field device (507) newly integrated into the automation system (500).

8. Method (100) according to one of the preceding claims, wherein the identification step (101) comprises: Sending an identification command (415) by the communication gateway (400) to field devices (507) of the automation system (500) in a sending step (117); and Receiving an identification response (417) of the at least one field device (507) by the communication gateway (400) in a receiving step (119), wherein at least one device identifier of the at least one field device (507) is defined in the identification response (417).

9. Computer-implemented method (200) for data communication between an OPC-LIA client (502) and at least one field device (507) of an automation system (500), comprising: Generating a communication network (501) between the OPC-LIA client (502) and the at least one field device (507) of the automation system (500) by executing the method (100) for generating a communication network (501) between an OPC-LIA client (502) and at least one field device (507) according to one of the preceding claims 1 to 8 by a communication gateway (400) in a network generation step (201); Receiving a communication message (419) from the field device (507) by the communication gateway (400) in a message receiving step (203), wherein the communication message (419) contains at least one piece of operating information (405) relating to at least one operating parameter of the field device (507); storing the operating information (405) relating to the operating parameter of the field device (507) in the OPC-UA node set (401) on the OPC-LIA server (403) in an information storing step (205); and Providing the operating information (405) regarding the operating parameter of the field device (507) for the OPC-UA client (502) via the OPC-UA node set (401) of the OPC-UA server (403) by the communication gateway (400) in a provisioning step (207).

10. The method (200) according to claim 9, wherein communication messages (419) of the field device (507) are received cyclically by the communication gateway (400), and wherein operational information (405) of the communication messages (419) is correspondingly stored cyclically in the OPC-UA node set (401) of the OPC-UA server (403).

11. The method (200) according to claim 9 or 10, wherein the operating parameter of the field device (507) comprises an operating time and / or an operating performance and / or a maintenance state and / or a service life and / or a next maintenance date of the field device (507).

12. Method (200) according to one of the preceding claims 9 to 11, wherein the operating information (405) of the field device (507) stored in the OPC-UA node set (401) is provided to the OPC-UA client (502) via a point-to-point channel and / or a message channel and / or a publisher-subscriber channel and / or a message bus and / or a data type channel.

13. Computer-implemented method (300) for data analysis of operating information (405) of a field device (507) by an OPC-LIA client (502) of an automation system (500), comprising: Receiving operating information (405) provided according to the method (300) for data communication between an OPC-LIA client (502) and at least one field device (507) of an automation system (500) according to one of the preceding claims 9 to 12 by the OPC-LIA client (502) in an information receiving step (301); Analyzing the operating information (405) by the OPC-LIA client (502) in an analysis step (303); and Outputting an instruction to stop operation of the field device (507) and / or to replace the field device (507) in an output step (305) if the analysis has determined a malfunction and / or an operating time that has exceeded a limit value and / or an operating performance that has exceeded a limit value and / or a specific maintenance status and / or an expired service life and / or a maintenance date of the field device (507).

14. Communication gateway (400) for data communication between an OPC-LIA client (502) and at least one field device (507) of an automation system (500), wherein the communication gateway (400) is configured to carry out the method (100) for generating a communication network (501) according to one of the preceding claims 1 to 8 and / or the method (200) for data communication between an OPC-LIA client (502) and at least one field device (507) of an automation system (500) according to one of the preceding claims 9 to 12.

15. Communication gateway (400) according to claim 14, wherein the communication gateway (400) comprises: an internal database (407) with configuration information (409) and / or communication information (411) relating to a plurality of different field devices (507); and / or a fieldbus module (421), wherein the fieldbus module (421) is configured to send communication commands (413) to field devices (507) in a fieldbus protocol and / or to receive communication messages (419) from field devices (507) and / or to identify field devices (507); and / or a parsing module (423), wherein the parsing module (423) is configured to read configuration information (409) and / or communication information (411) relating to the field devices (507) of the automation system (500) from the internal database (407), wherein the configuration information (409) comprises information relating to a configuration of the OPC-LIA node set (401), wherein the communication information (411) defines at least one communication command (413) of a fieldbus protocol, and wherein, via the communication command (413), a field device (507) can be driven to transmit at least one item of operating information (405) of the field device (507) to the communication gateway (400);and / or a conversion module (425), wherein the conversion module (425) is configured to generate a corresponding OPC-LIA node set (401) for each identified field device (507) of the automation system (500) based on the configuration information (409) of the field devices (507); and / or an OPC-LIA server (403) for storing the OPC-UA node sets (401) of the identified field devices (507); and / or an OPC-UA communication interface (427), wherein the communication gateway (400) is connectable to an OPC-UA client (502) via the OPC-UA communication interface (427), and wherein the OPC-UA node set (401) is provided to the OPC-UA client (502) via the OPC-UA communication interface (427); 16. Automation system (500) with at least one field device (507), at least one OPC-UA client (502) and a communication gateway (400) according to claim 14 or 15, wherein the OPC-UA client (502) is configured to execute the method (300) for data analysis according to claim 13.

17. Automation system (500) according to claim 16, wherein the OPC-UA client (502) is implemented in a terminal (503) of the control center (505) in a cloud server (513).

Images