Method for generating communication network in 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), comprising: in an identification step (101), identifying the at least one field device (507) of the automation system (500) by means of a communication gateway (400) of the automation system (500); in the generation step (103), a set of OPC-UA nodes (401) for the identified field device (507) is generated by means of the communication gateway (400); and in the node set storage step (105), the OPC-UA node set (401) is stored on the OPC-UA server (403). The invention also relates to a method (200) for data communication, a method (300) for data analysis, a communication gateway (400) and an automation system (500).

Description

Technical Field

[0001] The present invention relates to 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 the operating information of field devices through an OPC-UA client on the control panel of an automation system, and a communication gateway. Background Art

[0002] In automation technology, analytical processes are crucial. These analyses are essential for the trouble-free execution of individual automated processes, requiring precise understanding of the technological processes and functionalities of each piece of equipment or entire facility segment. This is particularly true in large-scale automation systems, where numerous different components must precisely coordinate to ensure flawless operation. In such systems, centralized analysis of individual automated processes or subprocesses is especially advantageous. These analyses are advantageously implemented in the central control console of the automation system, where data from various devices or facility sections are aggregated for analytical purposes. This necessitates establishing communication channels between the control console and the components of the automation system. Summary of the Invention

[0003] Therefore, the objective of this invention is 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 the operating information of field devices through an OPC-UA client, and a communication gateway.

[0004] This task is accomplished using the method and communication gateway described in the independent claim. Preferred embodiments are given in the dependent claims.

[0005] According to one aspect of the present invention, a computer-implemented method is provided for generating a communication network between at least one OPC-UA client and at least one field device of an automation system, comprising:

[0006] In the identification step, at least one field device of the automation system is identified by the communication gateway of the automation system, which is configured to communicate with field devices for data.

[0007] In the generation step, the communication gateway generates an OPC-UA node set for the identified field devices; and

[0008] In the node set storage step, the OPC-UA node set is stored on an OPC-UA server, wherein the OPC-UA node set stored on the OPC-UA server can be invoked by at least one OPC-UA client of the automation system, and wherein the OPC-UA node set may store operating information that can be provided by at least one field device in data communication and that the operating information can be read by the OPC-UA client.

[0009] The resulting technical advantage is that it provides an improved method for generating a communication network between an OPC-UA client and at least one field device in an automation system. This communication network is automatically created by a suitably configured communication gateway. Here, the communication gateway, the OPC-UA client, and the field device are all part of the communication network.

[0010] The automatic generation of communication networks via communication gateways is particularly advantageous when integrating new field devices into existing automation systems. During integration, the corresponding OPC-UA node sets for the field devices can be automatically created, thus generating the communication network. This eliminates the need for programming to create the corresponding OPC-UA node sets.

[0011] 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. Here, the OPC-UA server includes information from field devices, stored or provided in the OPC node set, and provides services to the OPC-UA client, such as information services. Here, the OPC-UA client can log in to the OPC-UA server and use its services in a manner similar to a typical client-server architecture. For example, the OPC-UA client can read information from field devices provided in the OPC-UA node set.

[0012] An OPC-UA node set comprises multiple nodes and references connecting these nodes in the address space of an OPC-UA server. These nodes can represent objects, variables, and methods of the corresponding field devices. Furthermore, nodes can represent object types or object categories, variable types or variable categories, data types or data structures, and reference types of the corresponding field devices. Nodes in an OPC-UA node set can also be assigned attributes, such as the node's address or name. For example, a node representing a variable can also be assigned attributes such as the variable's value, data type, or access permissions for reading or writing the corresponding value by an OPC-UA client. The structure of the OPC-UA node set, especially the nodes and references, can be standardized for each field device according to the OPC-UA specifications for each device type used in the field device.

[0013] Here, the OPC-UA supporting specifications describe industry-specific standards that pertain to the communication models to be used for data communication with devices in the relevant industry.

[0014] OPC-UA clients can be designed as terminals in the control console of automation systems. OPC-UA clients can be designed as computer workstations, personal computers, or software modules. OPC-UA clients may also include additional gateways for data transformation.

[0015] According to one implementation, generating an OPC-UA node set includes:

[0016] In the first reading step, the communication gateway reads at least one configuration information about the identified field device from its internal database, wherein the configuration information includes information about the configuration of the OPC-UA node set; and

[0017] In the conversion step, the configuration information read from the internal database is converted into an OPC-UA node set.

[0018] The resulting technical advantage is that, by reading the configuration files of specific field devices from an internal database, the communication gateway can generate a corresponding set of OPC-UA nodes. Here, the configuration information in the internal database defines at least the type of the corresponding field device and the types of data that can be provided by that field device.

[0019] Here, the configuration information can be configured in the sense of the accompanying specifications and includes all the information required for the individual creation of OPC-UA node sets.

[0020] For example, configuration information may include mapping attributes, which define the relationship between the operating information provided by the field device and the OPC-UA variables of the OPC-UA node set for the corresponding field device.

[0021] The data structure of the OPC-UA node set can be defined or stored in the conversion module of the communication gateway. Here, the data structure of the OPC-UA node set can be individualized or assigned to the corresponding field devices based on the device type.

[0022] Alternatively or additionally, in the conversion information used for field devices, in addition to mapping and assignment, the data structure of the OPC-UA node set can also be defined.

[0023] The communication gateway can generate corresponding OPC-UA node sets for specific field devices based on configuration information. This avoids the tedious programming process of creating individualized OPC-UA node sets for each field device.

[0024] After identifying the corresponding field devices and reading the corresponding configuration information, the communication gateway can autonomously create an OPC-UA node set.

[0025] According to one embodiment, the method further includes:

[0026] In the second reading step, the communication gateway reads at least one communication information about the identified field device from its internal database. This communication information defines at least one communication command of the fieldbus protocol, which causes the field device to transmit at least one operating parameter to the communication gateway.

[0027] In the command storage step, at least one communication command is stored in the communication gateway.

[0028] The resulting technical advantage is that, through communication information, the communication gateway can store the corresponding field devices and the corresponding communication commands for predefined fieldbus protocols. By reading the communication information from the internal database, the communication gateway thus obtains the communication commands required for data communication with the corresponding field devices.

[0029] By retrieving communication information from its internal database for each identified field device, the communication gateway can automatically communicate with the corresponding field device and request operational information from it. This eliminates the need for tedious programming of the communication gateway to enable communication with the relevant field devices.

[0030] Here, communication information may include or define parameters required for data communication between the communication gateway and field devices according to a predefined fieldbus protocol.

[0031] According to one implementation, the internal database includes configuration information and / or communication information for multiple different field devices.

[0032] The resulting technical advantage is the ability to provide a comprehensive internal database. This internal database includes configuration and / or communication information for at least all existing field devices present in the automation system.

[0033] Preferably, the internal database also includes configuration and / or communication information for multiple different field devices that are not currently present in the automation system but can be integrated into it in the future. This allows the information in the internal database to be accessed when integrating new field devices into the automation system, enabling the generation of corresponding OPC-UA node sets.

[0034] According to one implementation, the configuration information and / or communication information of the internal database are provided by the manufacturer of the field equipment.

[0035] The resulting technical advantage is that the internal database can be expanded by receiving new field devices. This keeps the configuration and / or communication information stored in the internal database up-to-date. Consequently, for newly acquired field devices that can be integrated into the automation system, the corresponding configuration and / or communication information is already included in the internal database. Therefore, when integrating field devices into the automation system, the relevant information can be read from the internal database, and the corresponding OPC-UA node set can be automatically generated through the communication gateway.

[0036] According to one embodiment, the method further includes:

[0037] In the replication step, the communication gateway copies configuration information and / or communication information about multiple field devices from an external database to an internal database set on the communication gateway, wherein the internal database is set on an external server.

[0038] The resulting technological advantage is that manufacturers can easily obtain external databases. These external databases can be kept up-to-date, constantly updated with the latest configuration and / or communication information from field devices. This information can then be downloaded to the communication gateway's internal database for updating.

[0039] According to one implementation, the identified field device is a field device newly integrated into the automation system.

[0040] The resulting technological advantage is that newly integrated field devices into the automation system can be automatically integrated into the communication network via a communication gateway.

[0041] According to one implementation, the identification step includes:

[0042] In the sending step, the communication gateway sends identification commands to the field devices of the automation system; and

[0043] In the receiving step, the communication gateway receives an identification response from at least one field device, wherein the identification response defines at least one device identifier of at least one field device.

[0044] The resulting technical advantage is the ability to reliably identify field devices. Identification commands can be sent by the communication gateway to multiple field devices, or individually to selected field devices. In particular, when changes are detected in the field devices, the communication gateway can send corresponding identification commands.

[0045] For example, such a change could include the integration of new field devices into the automation system. The communication gateway can then identify these field devices by sending communication commands, thereby retrieving the corresponding configuration and / or communication information from its internal database, generating a corresponding OPC-UA node set, and storing it on the OPC-UA server. Therefore, when a new field device is identified, a communication network can be automatically generated.

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

[0047] In the network generation step, the communication gateway generates a communication network between the OPC-UA client and at least one field device of the automation system by executing the method for generating a communication network between the OPC-UA client and at least one field device according to any of the above embodiments.

[0048] In the message receiving step, the communication gateway receives the communication message from the field device, wherein the communication message contains at least one piece of operating information about at least one operating parameter of the field device;

[0049] In the information storage step, operational information regarding the operating parameters of the field equipment is stored in the OPC-UA node set on the OPC-UA server; and

[0050] In the provisioning step, the communication gateway provides the OPC-UA client with operating information about the operating parameters of the field equipment through the OPC-UA node set of the OPC-UA server.

[0051] The resulting technical advantage is that it provides an improved method for data communication between an OPC-UA client and field devices in an automation system. To generate the communication network required for data communication, the method according to the invention, which possesses the aforementioned technical advantages, is first executed.

[0052] Here, the communication network includes at least one OPC-UA client, at least one field device, and a communication gateway according to the invention, which acts as an intermediary between the control console and the field devices of the automation system. In particular, the communication gateway is capable of automatically generating the communication network. Therefore, data communication can be automatically initiated through the communication gateway.

[0053] According to one implementation, a communication gateway periodically receives communication messages from field devices, wherein the operational information in the communication messages is correspondingly periodically stored in the OPC-UA node set of the OPC-UA server.

[0054] The resulting technical advantage is the ability to provide reliable data communication between the control console and the field devices of the automation system. For this purpose, operational information is provided periodically by the individually identified field devices, specifically during the control cycle in which the automation system is controlled.

[0055] Accordingly, operational information is periodically written to the node set generated during the communication network setup and stored on the OPC-UA server. The console can access the operational information stored on the OPC-UA server and use it for data analysis. By providing operational information periodically from field devices—that is, during control cycles—the simplest possible data communication can be provided, eliminating the need for additional queries from the console to the field devices. Updated data that can be read by the control system can be transmitted during data communication.

[0056] Here, data communication mainly includes the path from the field device to the OPC-UA client, in which operational information is provided by the field device and can be read by the OPC-UA client.

[0057] According to one implementation, the operating parameters include the operating time and / or operating power and / or maintenance status and / or service life and / or next maintenance schedule of the field equipment.

[0058] The resulting technological advantage is that, in particular, the operational information of field devices is transmitted, information that is largely overlooked during the control of the automation system by the corresponding control units. This transmitted operational information also enables the analysis of the operational status of each field device.

[0059] By monitoring the operational information provided by field devices in subsequent data analysis performed by the OPC-UA client, the load on field devices can be monitored, and the likely time to replace them can be determined. By monitoring the number of operating hours, remaining useful life, or planned maintenance schedules in subsequent data analysis, the appropriate field devices can be replaced or maintained at the appropriate time.

[0060] According to one implementation, the operational information of field devices stored in the OPC-UA node set is provided to the OPC-UA client through point-to-point channels and / or message channels and / or publish-subscribe channels and / or message buses and / or data type channels.

[0061] The resulting technical advantage is that it enables reliable transmission of field device operating information from the communication gateway to the OPC-UA client.

[0062] According to one aspect, a method is provided for data analysis of operational information of field devices via an OPC-UA client of an automation system, comprising:

[0063] In the information receiving step, the OPC-UA client receives operating information provided by the method for data communication between the OPC-UA client and at least one field device of the automation system according to any of the above embodiments.

[0064] In the analysis step, the OPC-UA client analyzes the runtime information; and

[0065] In the output step, if the analysis determines the functional faults and / or the operating time and / or the operating power exceeding the limit of the field equipment and / or the determined maintenance status and / or the expired service life and / or the maintenance schedule, then the output is an operation instruction for stopping the operation of the field equipment and / or for replacing the field equipment.

[0066] The resulting technical advantage is that it provides an improved method for data communication between an OPC-UA client and field devices in an automation system. To generate the communication network required for data communication, the method according to the invention, which possesses the aforementioned technical advantages, is first executed.

[0067] Here, the communication network includes at least one OPC-UA client, at least one field device, and a communication gateway according to the invention, which acts as an intermediary between the OPC-UA client and the field device of the automation system.

[0068] Communication gateways are particularly capable of automatically generating communication networks. Therefore, data communication can be automatically initiated through a communication gateway.

[0069] 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 perform a method for generating a communication network according to any of the above embodiments and / or a method for performing data communication between an OPC-UA client and at least one field device of an automation system according to any of the above embodiments.

[0070] The resulting technical advantage is that it provides an improved communication gateway configured to perform methods for generating a communication network and methods for data communication, which have the aforementioned technical advantages.

[0071] In particular, the communication gateway can automatically generate a communication network without developer intervention. Especially in the case of field devices newly integrated into an automation system, the communication gateway can generate a corresponding set of OPC-UA nodes, thereby creating a communication network.

[0072] According to one embodiment, the communication gateway includes:

[0073] An internal database containing configuration and / or communication information for multiple different field devices; and / or

[0074] A fieldbus module, wherein the fieldbus module is configured to send communication commands to field devices and / or receive communication messages from field devices and / or identify field devices in accordance with the fieldbus protocol; and / or

[0075] The parsing module is configured to read configuration and / or communication information about field devices in the automation system from an internal database. The configuration information includes information about the configuration of the OPC-UA node set. The communication information defines at least one communication command of the fieldbus protocol, and through this communication command, the field device can transmit at least one piece of operational information about the field device to the communication gateway; and / or

[0076] The conversion module is configured to generate a corresponding OPC-UA node set for each identified field device in the automation system based on the configuration information of the field devices; and / or

[0077] An OPC-UA server, used to store the set of OPC-UA nodes for identified field devices; and / or

[0078] The OPC-UA communication interface allows the communication gateway to connect to the OPC-UA client and provide the OPC-UA node set to the OPC-UA client.

[0079] The resulting technological advantage is that the communication gateway can automatically and without user intervention execute methods for generating communication networks and methods for data analysis through multiple different modules. Especially when changes occur in the automation system, such as when field equipment is replaced, the communication gateway can autonomously create communication networks.

[0080] This eliminates the need for developers to tediously generate corresponding OPC-UA node sets or perform complex planning for newly integrated field devices in the automation system. Therefore, system outages can be limited to the replacement of field devices.

[0081] According to one aspect, an automation system is provided, having at least one field device, at least one OPC-UA client, and a communication gateway according to any of the above embodiments, wherein the OPC-UA client is configured to perform a data analysis method.

[0082] The resulting technical advantage is that it enables the provision of an automated system configured to perform data analysis that offers the aforementioned technical advantages.

[0083] According to one implementation, the OPC-UA client is implemented in the terminal of the console in the cloud server.

[0084] The resulting technological advantage is the ability to centrally analyze operational information from field equipment. Furthermore, by using cloud servers, the higher computing power offered by this type of server can also be utilized. Attached Figure Description

[0085] The invention will now be explained in more detail with the aid of the accompanying drawings.

[0086] Figure 1 A schematic diagram of an automation system with a communication gateway according to one embodiment is shown;

[0087] Figure 2 A flowchart illustrating 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;

[0088] Figure 3 Another flowchart illustrates 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 another embodiment.

[0089] Figure 4 Another flowchart illustrates 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 another embodiment.

[0090] Figure 5 A flowchart illustrating a computer-implemented method for data communication between an OPC-UA client and at least one field device of an automation system, according to one embodiment; and

[0091] Figure 6 A flowchart is shown, according to one embodiment, of a computer-implemented method for performing data analysis on operational information of field devices via an OPC-UA client of an automation system. Detailed Implementation

[0092] Figure 1 A schematic diagram of an automation system 500 having a communication gateway 400 according to one embodiment is shown.

[0093] In the illustrated embodiment, the automation system 500 includes 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 also includes an OPC-UA client 502. The OPC-UA client 502 can be connected to the communication interface 427 of the communication gateway 400 via a wireless data connection 515. Alternatively, the data connection can also be a wired connection.

[0094] In the illustrated embodiment, the OPC-UA client 502 is configured as a terminal 503 of the console 505 of the automation system 500.

[0095] In this embodiment, the console 505 is configured as a cloud server 513 and is connected to the communication interface 427 of the communication gateway 400 via a wireless data connection 515.

[0096] In the illustrated embodiment, the communication gateway 400 includes an internal database 407. The internal database 407 stores configuration information 409 and / or communication information 411 for multiple different field devices 507.

[0097] The communication gateway 400 also includes a parsing module 423. The parsing module 423 is configured to search the internal database 407 for relevant information and read such information from the internal database 407.

[0098] The communication gateway 400 also includes a fieldbus module 421. The fieldbus module 421 is configured to communicate data with multiple field devices 507 of the automation system 500 according to the fieldbus protocol of the fieldbus 517.

[0099] The communication gateway 400 also includes a conversion module 425. The conversion module 425 is configured to convert information obtained from the parsing module 423 and the fieldbus module 421 into the OPC-UA communication standard.

[0100] In the illustrated embodiment, the communication gateway 400 further includes an OPC-UA server 403. The OPC-UA server 403 may store an OPC-UA node set 401 for different field devices 507 of the automation system 500, according to the OPC-UA communication standard.

[0101] In the illustrated embodiment, the automation system 500 also includes an external database 509 that can be executed on an external server 511. The external database 509 is connected to the communication gateway 400 via a separate wireless data connection 516.

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

[0103] In this context, for the purposes of this application, the communication network 501 includes at least one OPC-UA client 502, at least one field device 507, and a communication gateway 400.

[0104] In order to generate the communication network 501 according to the present invention, the communication gateway 400 first identifies at least one of the plurality of field devices 507 of the automation system 500.

[0105] Alternatively, multiple field devices 507 of the automation system 500 can be identified, and all field devices 507 can be identified if necessary.

[0106] To this end, the communication gateway 400 can send at least one identification command 415 to the field device 507 via the fieldbus 517 through the fieldbus module 421. Here, the identification command 415 can be sent as a general identification command 415 to all field devices 507 of the automation system 500. Alternatively or additionally, the identification command 415 can be sent to each selected field device 507. The identification command 415 requires each field device 507 to identify itself to the communication gateway 400.

[0107] Therefore, the field device 507 that receives the corresponding identification command 415 sends a corresponding identification response 417 to the communication gateway 400. The identification response 417 defines at least the device identifier and / or device type of the corresponding field device 507. Thus, based on the information in the identification response 417, the corresponding field device 507 can be identified, for example, as a certain type of sensor or actuator, i.e., a temperature sensor or a pressure sensor, or a servo motor with a specific structural form.

[0108] Subsequently, the fieldbus module 421 forwards the corresponding information from the identification response 417 to the parsing module 423. Here, the identification response 417 may include a device identification code, which clearly identifies the corresponding field device 507. The device identification code can be defined according to the HART protocol.

[0109] Alternatively or additionally, the identification response 417 may include information about the device type of the corresponding field device 507.

[0110] Subsequently, the parsing module 423 can search the internal database 407 for the corresponding information stored in the field device 507 for the corresponding device type based on the information in the identification response 417 (which at least indicates the device type or device identifier of the field device 507 identified respectively).

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

[0112] The parsing module 423 finds the configuration information 409 and / or communication information 411 of the corresponding field device 507 based on the device identification code, i.e., the device identifier of the field device 507.

[0113] Alternatively, configuration information 409 or communication information 411 can also be stored in an internal database 407 according to the various device types or device type structures of the field devices 705. The parsing module 423 can then be configured to search the internal database 407 to find the device type.

[0114] The configuration information 409 stored in the internal database 407 for different field devices 507 includes configuration information for the OPC-UA node set 401 of each field device 507.

[0115] Here, configuration information 409 may include mapping assignments, wherein the mapping assignments define which operating information 405 or operating parameters of the field device 507 should be mapped to which OPC-UA variables of the OPC-UA node set 401 respectively assigned to the field device 507.

[0116] The data structure of the OPC-UA node set 401 can be defined or stored in the conversion module 425. Here, the data structure of the OPC-UA node set 401 can be individually assigned to each field device 507 or according to the device type of the field device 507. In the case of individual assignment, the data structure, or information about the data structure, can be stored regarding the device identification code of the field device 507.

[0117] Here, the data structure is understood as the non-instantiated structure of nodes and references in OPC-UA node set 401.

[0118] Alternatively or additionally, in the conversion information used for field device 507, in addition to mapping assignment, the data structure of OPC-UA node set 401 can be defined.

[0119] Alternatively or additionally, the configuration of each field device 507 or the configuration of the corresponding OPC-UA node set 401 for the corresponding type of field device 507 can be defined in the configuration information 409. Here, the configuration information 409 can define various characteristics of the field device 507, such as the sensor type or actuator type of the corresponding field device 507, and the data type of information that can be provided by the field device 507 respectively.

[0120] The information in configuration information 409 or the data structure of non-instantiated OPC-UA node set 401 can be constructed based on the information in the accompanying specifications for the OPC-UA standard.

[0121] Taking into account the mapping and assignment of configuration information 409 and the data structure of OPC-UA node set 401, conversion module 425 can generate corresponding instantiated OPC-UA node set 401 for field device 507. In each instantiated node set 401 that is individually and explicitly assigned to field device 507, each operating parameter that can be provided by field device 507 is explicitly assigned to an OPC-UA variable of the corresponding OPC-UA node set 401. Through instantiation, the values ​​of each operating parameter that can be provided by field device 507 to communication gateway 400 via data communication via fieldbus protocol can be written into the OPC-UA variables of OPC-UA node set 401 respectively assigned to the operating parameters.

[0122] The instantiated OPC-UA node set 401 can be stored in the OPC-UA memory 403. The current value of the operating parameters provided by the field device 507 can be stored in the OPC-UA server 403 by writing the value of the operating parameters into the OPC-UA variable set for this purpose according to the conversion information 409 of the OPC-UA node set 401.

[0123] Communication information 411 defines the parameters required for data communication between communication gateway 400 and field device 507 according to a predefined fieldbus protocol.

[0124] For example, when using the HART protocol as the fieldbus protocol, the following information can be defined in communication information 411 for each parameter to be read from field device 507 or each piece of operational information 405:

[0125] -HART command

[0126] - Write data

[0127] -Write length

[0128] -Byte offset

[0129] -Read length

[0130] -type

[0131] Here, the HART commands describe the communication commands 413 required for communication under the HART protocol. Through the communication commands 413, the addressed field devices 507 can be requested to send the requested information. Based on the requested information, multiple communication commands 413 can be defined for a single field device 507 in the corresponding communication information 411. Write data defines the data to be written. Write length defines the length of the data to be written. Byte offset defines which part of the sent response the information to be read is located in. Read length defines the length of the data to be read. Type defines the data type of the data to be read.

[0132] The above description of communication information 411 is only illustrative of the HART protocol. This invention can also be applied to other fieldbus protocols. For other fieldbus protocols, communication information 411 may include information or communication commands 413 that are different from those described above.

[0133] Therefore, the communication information 411 includes at least the communication commands 413, which enable data communication between the communication gateway 400 and the field device 507 according to the respective fieldbus protocols used.

[0134] Communication information 411 can be defined for the corresponding field device 507 in a manner similar to configuration information 409. That is, communication information 411 can be stored individually for the field device 507 in the internal database 407, for example, stored under the corresponding device identification code.

[0135] Alternatively, the communication information 411 can be adapted to a specific device type or a specific device model of the field device 507, and can be distinguished for different field devices 507 of different device types or different implementations.

[0136] Therefore, the internal database 407 includes, at least for multiple field devices 507 of the automation system 500, preferably all field devices 507, corresponding configuration information 409 and / or communication information 411.

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

[0138] The conversion module 425 is configured to generate at least one corresponding OPC-UA node set 401 for each field device based on the configuration information 409.

[0139] Therefore, the conversion module 425 can consider the corresponding stored data structure and mapping of the OPC-UA node set 401 for the field device 507 of the automation system 500 according to the configuration information 409, and generate a corresponding instantiated OPC-UA node set 401 for the field device 507.

[0140] In the instantiated OPC-UA node set 401, OPC-UA variables that are explicitly assigned in the corresponding OPC-UA node set 401 are defined for possible operating parameters that can be provided by the field device 507.

[0141] The OPC-UA node set 401 instantiated in this way can then be stored in the OPC-UA server 403.

[0142] Based on the mapping of configuration information 409, conversion module 425 can then write the values ​​of operating information 405 or operating parameters provided by field device 507 into the corresponding OPC-UA variables set for this purpose in each OPC-UA node set 401, and store them in OPC-UA server 403.

[0143] Accordingly, the instantiated OPC-UA node set 401 generated based on the configuration information 409 is individually adapted to the respective identified field devices 507, and has a data structure defined for the corresponding device type of field device 507 according to the OPC-UA standard, that is, according to the corresponding supporting specifications or according to customer requirements compatible with the OPC-UA standard.

[0144] Furthermore, the parsing module 423 transmits the communication information 411 read from the internal database 407 for each identified field device 507 to the fieldbus module 421. The fieldbus module 421 stores information from the communication information 411 (including communication commands 413) and is thus configured to communicate with the identified field devices 507 via the corresponding fieldbus protocol and request them to send desired information.

[0145] OPC-UA client 502 can connect to communication gateway 400 via wireless data connection 515 and read OPC-UA node set 401 stored in OPC-UA server 403. Depending on personalized access permissions as needed, OPC-UA client 502 can also write to variables in OPC-UA node set 401.

[0146] Thus, according to the present invention, a communication network 501 is generated between the OPC-UA client 502 and the respective identified field devices 507.

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

[0148] In addition, 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 perform data communication with the field devices 507 based on the fieldbus protocol.

[0149] According to the present invention, the generation of the communication network 501 is automatically performed by the communication gateway 400. Therefore, especially when integrating a new field device 507 into an existing automation system 500, a corresponding OPC-UA node set 401 can be automatically generated and stored in the OPC-UA server 403, and the various communication commands 413 of the communication information 411 can be stored in the fieldbus module 421.

[0150] Therefore, when a new field device 507 is integrated into the automation system 500, the communication gateway 400 receives information about the integration of the new field device 507 into the automation system 500 and then sends a corresponding identification command 415.

[0151] Similarly, when the automation system 500 restarts, the communication gateway 400 can perform corresponding identification for the field devices 507 integrated into the automation system 500, and on this basis, generate each OPC-UA node set 401 by reading the configuration information 409 and communication information 411 stored in the internal database 407 for each field device 507 and store them in the OPC-UA server 403, and store each configuration information 409 in the fieldbus module 421.

[0152] Here, the tedious programming process is eliminated, which requires manually creating the corresponding OPC-UA node set 401 and generating the corresponding communication command 413 for each new field device 507.

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

[0154] After establishing a communication network 501 between the OPC-UA client 502 and at least one field device 507, in order to enable data communication between the OPC-UA client 502 and the field device 507, the communication gateway 400 receives a communication message 419 from at least one identified field device 507.

[0155] Communication message 419 includes operating information 405 of the corresponding field device 507. This communication message 419 can be received periodically by the communication gateway 400. For this purpose, at least one or all field devices 507 of the automation system 500 periodically send corresponding communication messages 419. Each communication message 419 contains current operating information 405 of each field device 507. For this purpose, the communication gateway 400 can periodically send corresponding requests to the field devices 507 for sending communication information 411.

[0156] The communication message 419 may be periodically sent by the field device 507, for example, during the control cycle of the automation system 500. Alternatively or additionally, the communication message 419, which includes the operating information 405 contained therein, may also be sent non-periodically by the field device 507.

[0157] According to one embodiment, in order to prompt the field devices 507 to send communication messages 419, the communication gateway 400 may first send corresponding communication commands 413 to each field device 507. The sent communication commands 413 then prompt the field devices 507 that receive the corresponding commands to send their respective communication messages 419.

[0158] For example, this can be particularly done when communication messages 419 are sent aperiodically by field devices 507, such as between successive control cycles of the automation system 500.

[0159] Communication message 419 and communication command 413 are defined according to the fieldbus protocol used respectively.

[0160] The communication command 413 sent here can correspond to the communication information 411 stored in the fieldbus module 421 in the internal database 407.

[0161] Based on the sent communication command 413, different operating information 405 may be included in the subsequent communication messages 419 sent by the field devices 507. Therefore, the communication command 413 may be intended to invoke different operating information 405 for each field device 507.

[0162] After receiving communication message 419, the operating information 405 contained therein is transmitted by fieldbus module 421 to conversion module 425. Conversion module 425 is configured to write the operating information 405 of field device 507 into the OPC-UA node set 401 assigned to each field device 507, and to store the OPC-UA node set 401 in OPC-UA server 403 for each field device 507.

[0163] According to one implementation, in the OPC-UA server 403, and particularly in each OPC-UA node set 401, the operating information 405 of the field device 507 is stored for multiple successive control cycles.

[0164] Subsequently, each OPC-UA client 502 can view the running information 405 stored in the OPC-UA node set 401 on the OPC-UA server 403.

[0165] Therefore, the corresponding OPC-UA client 502 can send a corresponding read command to the communication interface 427 of the communication gateway 400 via the wireless data connection 515. Thus, the OPC-UA client 502 is configured to invoke the OPC-UA node set 401 stored in the OPC-UA server 403 for a specific field device 507 and read the operating information 405 stored therein.

[0166] Data communication between the OPC-UA client 502 and the communication gateway 400 can be conducted through point-to-point channels and / or message channels and / or publish-subscribe channels and / or message buses and / or data type channels.

[0167] By reading (which may also include uploading the operating information 405 stored in the OPC-UA server 403 to, for example, the terminal 503 of the console 505 or the cloud server 513), the OPC-UA client 502, i.e. the terminal of the console 505, can perform data analysis on the operating information 405 of the field devices 507 of the automation system 500.

[0168] For this purpose, the operating information 405 may include, for example, the operating parameters of each field device 507. The operating parameters may include, for example, the runtime of the corresponding field device 507, the average load or maximum or minimum load, the upcoming maintenance schedule of the corresponding field device 507, the error message of the corresponding field device 507, or other parameters describing the functionality or operating load of the corresponding field device 507.

[0169] Alternatively or additionally, the operating information 405 may include information about the last calibration (e.g., the date of calibration), information about the hardware version and / or software version of the field device 507, information about the temperature of the electronics of the field device 507, information about device-specific counter variables, and other device-specific information.

[0170] Alternatively or additionally, the operational information 405 may also include actual useful data from the various field devices 507, such as measurement data from the sensors of the automation system 500.

[0171] Operation information 405 can also describe the defined operating range of each field device 507. For example, the operating range can define the power range or speed range in which a motor can operate, or the pressure range or temperature range in which the pressure sensor or temperature sensor of the automation system 500 can operate.

[0172] Based on the operational information 405 of different field devices 507, the control console 505 can perform corresponding analysis on the functional modes and usage of the field devices 507 in the automation system 500. Based on this analysis, the operation of the automation system 500 can be optimized.

[0173] In one implementation, the fieldbus protocol used is the HART protocol. Each communication message 411 defines a corresponding HART command, which enables HART-based data communication between the communication gateway 400 and the field devices 507 of the automation system 500.

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

[0175] According to another implementation, data communication between the console 505 and the field devices 507 of the automation system 500 can be performed according to the NAMUR Open Architecture (NOA).

[0176] To this end, communication network 501 (including OPC-UA client 502 or console 505, field device 507, and communication gateway 400) defines a second communication channel for data communication between field device 507 and control unit of automation system 500. Therefore, data communication via communication network 501 can occur in parallel with data communication between control unit and field device 507.

[0177] Therefore, the operational information 405 transmitted to the communication gateway 400 via the communication message 419 of the field device 507 can be supplemented with useful data provided by the field device 507 to the control unit of the automation system 500 during the control cycle. Thus, through the communication network 501, data communication can be realized that is largely independent of the periodic data communication between the field device 507 and the control unit of the automation system 500.

[0178] According to one implementation, the communication gateway 400 and / or OPC-UA server 403 and / or internal database 407 are integrated into the control unit, such as a memory programmable controller (SPS).

[0179] Figure 2 A flowchart is shown of 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, according to one embodiment.

[0180] In order to establish a communication network 501 between at least one OPC-UA client 502 and at least one field device 507 of the automation system 500, in the identification step 101, at least one field device 507 of the automation system 500 is first identified by the communication gateway 400 of the automation system 500.

[0181] By identifying the field device 507, at least one device type can be determined.

[0182] Field devices 507 can be identified for selected field devices 507. Alternatively or additionally, multiple field devices 507 of the automation system 500 can be identified, and all field devices 507 can be identified if necessary.

[0183] For example, identification can be performed during the startup of the automation system 500.

[0184] Alternatively or additionally, identification may be repeated at predetermined time intervals during the operation of the automation system 500.

[0185] Alternatively or additionally, identification can be performed when a predefined event occurs, in particular identification of the selected field device 507.

[0186] These predefined events may include, for example, the new integration of field device 507 into the existing automation system 500. Therefore, the newly integrated field device 507 will be automatically recognized by the communication gateway 400.

[0187] Alternatively or additionally, such events may include updates to the external database 509 of the external server 511. The external database 509 is accessible to the manufacturers of the field devices 507. When existing field devices 507 change or new field devices 507 are developed, the external database 509 can be configured with appropriate information by the respective manufacturers of the field devices 507.

[0188] Through the wireless data connection 515 between the communication gateway 400 and the external server 511, information from the external database 509 can be integrated into the internal database 407 of the communication gateway 400, so that the internal database 407 of the communication gateway 400 can be kept up-to-date.

[0189] When changes occur in the internal database 407 of the communication gateway 400, the existing communication network 501 can be regenerated according to the steps described above, so that new information in the updated internal database 407 can be considered when necessary.

[0190] Subsequently, in generation step 103, the communication gateway 400 generates at least one OPC-UA node set 401 for the identified field devices 507. Here, the OPC-UA node set 401 is adapted to the device type of each identified field device 507 according to the OPC-UA communication standard.

[0191] In the node set storage step 105, at least one OPC-UA node set 401 of the identified field device 507 is stored on the 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-UA client 502. Furthermore, the operating information 405 of the identified field device 507 can be stored in the OPC-UA node set 401 and thus can be read by the OPC-UA client 502.

[0192] According to the present invention, the correspondingly generated communication network 501 includes at least one OPC-UA client 502, at least one identified field device 507, and a communication gateway 400 connected to the OPC-UA client 502 and the field device 507 in terms of data technology.

[0193] Therefore, data communication between the OPC-UA client 502 and the corresponding field device 507 of the generated communication network 501 can be coordinated through the communication gateway 400.

[0194] Figure 3Another flowchart of 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, according to another embodiment, is shown.

[0195] The implementation shown is based on Figure 2 The implementation methods described herein include all method steps described therein.

[0196] and Figure 2 The implementation methods differ from those described above. In the illustrated implementation, after identifying the field device 507 or multiple field devices 507, in the first reading step 107, the communication gateway 400 reads at least one configuration information 409 about the respective identified field devices 507 from the internal database 407.

[0197] Configuration information 409 includes information about the configuration of the OPC-UA node set 401 for the corresponding field device 507.

[0198] For example, configuration information 409 may include mapping attributes, which define the mapping between operating information 405 or operating parameters that can be provided by field device 507 and the corresponding OPC-UA variables of the OPC-UA node set 401 respectively assigned to field device 507.

[0199] For this purpose, the corresponding data structure of the non-instantiated OPC-UA node set 401 can be stored, for example, in the conversion module 425. Alternatively, the data structure of the non-instantiated OPC-UA node set 401 can be stored in another storage location such that the conversion module 425 can access these data structures and instantiate the non-instantiated OPC-UA node set 401 with the help of the conversion information 409.

[0200] Operating information 405 or operating parameters that can be provided by field device 507 may include, for example, measured parameters (such as temperature or pressure or operating time in units), average maximum or minimum load of field device 507, planned maintenance schedule, expected service life, or similar parameters describing the operating or functional capabilities of the corresponding field device 507.

[0201] In conversion step 109, the configuration information 409 read from the internal database 407 by the communication gateway 400 is then converted into the corresponding OPC-UA node set 401 of the identified field device 507.

[0202] To this end, the conversion module 425 can individually adapt the predefined data structure of the non-instantiated OPC-UA node set 401 for each field device 507 to each field device 507, such as to the field devices 507 newly integrated into the automation system 500, based on the mapping assignment, thereby generating an instantiated OPC-UA node set 401. In the instantiated OPC-UA node set 401, based on the conversion information 409 of the internal database 407, for each operating parameter that can be explicitly determined by the corresponding field device 507, at least one variable of the OPC-UA node set 401 can be written into that variable.

[0203] Here, the predefined data structure of the non-instantiated OPC-UA node set 401 is determined according to the provisions of the OPC-UA protocol standard, and when necessary, is determined according to the corresponding supporting specifications for the corresponding type of field device 507.

[0204] In addition to or in addition to the first reading step 107, in the second reading step 111, the communication gateway 400 reads communication information 411 from the internal database 407 for the respective identified field devices 507.

[0205] Communication information 411 defines at least one communication command 413 of the fieldbus protocol for each field device 507. Here, the communication command 413 is designed to cause the field device 507 to send or provide at least one operating parameter or provide operating information 405 in data communication between the communication gateway 400 and the corresponding field device 507.

[0206] Depending on the complexity of each field device 507, or on the number of different operating information 405, including different operating parameters, that can be provided by the field device 507 in data communication, the communication information 411 for the corresponding field device 507 may include a corresponding number of communication commands 413. A communication command 413 may be used precisely to request a specific operating parameter.

[0207] Subsequently, in command storage step 113, at least one communication command 413 of the communication information 411 of the corresponding field device 507 is stored in the communication gateway 400. By storing at least one communication command 413 in the communication gateway 400, the communication gateway 400 is configured to prompt the field device 507 to provide corresponding operating information 405 in data communication with the corresponding field device 507.

[0208] Figure 4Another flowchart of 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, according to another embodiment, is shown.

[0209] The implementation shown is based on Figure 3 The implementation methods described herein include all method steps described therein.

[0210] In the illustrated embodiment, in copying step 115, the communication gateway 400 first copies the configuration information 409 and / or communication information 411 from the external database 509 to the internal database 407.

[0211] Replication can be performed automatically at predetermined time intervals. Alternatively or additionally, replication can be performed event-driven when a predefined event occurs, such as when the automation system 500 is started, a new field device 507 is added to the automation system 500, or information in the external database 509 is updated or changed.

[0212] and Figure 3 The implementation methods differ from those shown. In the implementation method shown, the identification of at least one field device 507 by the communication gateway 400 in the identification step 101 includes performing the sending step 117.

[0213] In 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 prompt each field device 507 to send an identification response 417 upon receiving the corresponding identification command 415.

[0214] The identification command 415 can be sent to each selected field device 507, multiple field devices 507, or preferably to all field devices 507 of the automation system 500.

[0215] In receiving step 119, the communication gateway 400 identifies the field devices 507 by receiving identification responses 417 from each field device 507. The identification response 417 includes at least one device identifier for each field device 507, which allows the field device 507 to be identified. Identification of a corresponding field device 507 may at least include determining the device type of the corresponding field device 507.

[0216] After setting up the OPC-UA node set 401 in the OPC-UA server 403 according to the configuration information 409 stored in the internal database 407 for each field device 507, and after storing the communication information 411 stored in the internal database 407 for each field device 507, including the communication commands 413 contained therein, the communication gateway 400 is configured to perform data communication with each field device 507.

[0217] The corresponding communication network 501 is then installed.

[0218] Figure 5 A flowchart is shown of a computer-implemented method 200 for data communication between an OPC-UA client 502 and at least one field device 507 of an automation system 500, according to one embodiment.

[0219] In order to enable data communication between the OPC-UA client 502 and at least one field device 507 of the automation system 500, in the network generation step 201, the communication network 501 is first generated between the OPC-UA client 502 and at least one field device 507 of the automation system 500 by executing the method 100 for generating a communication network 501 according to the present invention.

[0220] After successfully establishing the communication network 501, in message receiving step 203, the communication gateway 400 receives the communication message 419 from the field device 507. The communication message 419 includes at least one operational information 405 of the corresponding field device 507. The operational information 405 includes at least one operational parameter of the field device 507.

[0221] In the information storage step 205, the operating information 405 of the field device 507 is then stored in the OPC-UA node set 401 stored on the OPC-UA server 403 for the corresponding field device 507.

[0222] By storing the operating parameters of the field device 507 in the OPC-UA node set 401, in step 207, information about the corresponding operating parameters, namely the operating information 405 of the corresponding field device 507, is provided to the OPC-UA client 502. The OPC-UA client is connected to the communication gateway 400 through data communication and can access the OPC-UA server 403 and the OPC-UA node set 401 stored thereon.

[0223] Subsequently, the OPC-UA client 502 can read the information about operating parameters contained in the operating information 405 by calling the corresponding OPC-UA node set 401 of the corresponding field device 507. Alternatively or additionally, the corresponding information can be uploaded by the OPC-UA client 502 to a personal computer, external server, or similar device.

[0224] This enables data communication between the OPC-UA client 502 and the corresponding field device 507.

[0225] Figure 6 A flowchart is shown of a computer-implemented method 300 for data analysis of operational information 405 of field device 507 via an OPC-UA client 502 of an automation system 500, according to one embodiment.

[0226] In order to perform data analysis on the operation information 405 of the field device 507 through the OPC-UA client 502, in the information receiving step 301, the corresponding OPC-UA client 502 first receives the operation information 405 provided by the corresponding field device 507 according to the above-described method 200 for data communication between the OPC-UA client 502 and at least one field device 507.

[0227] As previously described, receiving may include OPC-UA client 502 reading the runtime information 405 stored in the corresponding OPC-UA node set 401 and / or uploading the corresponding runtime information 405 of OPC-UA node set 401 to OPC-UA client 502, i.e., console 505.

[0228] In analysis step 303, the OPC-UA client 502 analyzes the runtime information 405.

[0229] The analysis of the operating information 405, or in particular the operating parameters of the various field devices 507 contained therein, may include different analysis steps 303.

[0230] For example, the load on field device 507 can be determined by analyzing the number of operating hours performed by field device 507 up to the point in time of data analysis. Alternatively or additionally, functional failures of field device 507 can be identified or analyzed.

[0231] Alternatively or additionally, it can be checked whether the corresponding field device 507 is operating within the preset load range.

[0232] Alternatively or additionally, the analysis can identify or assess the predefined maintenance schedule for the corresponding field equipment 507.

[0233] The possible analysis steps 303 mentioned herein are merely exemplary and should not limit the invention.

[0234] In addition to the steps mentioned herein, other analysis steps 303 may be envisioned, which may vary depending on the implementation of the corresponding field device 507 or the use of the corresponding field device 507 in the automation system 500.

[0235] If the analysis of the operation information 405 determines that the field device 507 has a functional failure and / or exceeds the limit determined for the operating time of the field device 507 and / or the service life of the field device 507 has expired and / or the maintenance schedule of the field device 507 has arrived, then in the output step 305, an operation instruction for stopping the operation of the corresponding field device 507 and / or for replacing the corresponding field device 507 is output.

[0236] In addition to the conditions mentioned above, other conditions can also cause corresponding operation instructions to be output when the corresponding conditions are identified during the analysis.

[0237] For example, an operation command can be output from the console 505 to the control unit of the automation system 500, thereby stopping the execution of the corresponding field device 507.

[0238] If the above conditions that would cause the output of the operation command according to the output step 305 are not identified in the analysis of analysis step 303, then in the operation step 307, the corresponding field device 507 continues to operate in the automation system 500.

[0239] List of reference numerals

[0240] 100 methods

[0241] 101 Identification Steps

[0242] 103 Generation Steps

[0243] 105-node set storage steps

[0244] 107 First Reading Step

[0245] 109 Conversion Steps

[0246] 111 Second reading step

[0247] 113 Command Storage Steps

[0248] 115 Copying Steps

[0249] 117 Sending Steps

[0250] 119 Receiving Steps

[0251] 200 methods

[0252] 201 network generation steps

[0253] 203 Message Receiving Steps

[0254] 205 Information Storage Steps

[0255] 207 provides steps

[0256] 300 methods

[0257] 301 Information Receiving Steps

[0258] 303 Analysis Steps

[0259] 305 Output Steps

[0260] 307 Operating Procedures

[0261] 400 Communication Gateway

[0262] 401 OPC-UA Node Set

[0263] 403 OPC-UA server

[0264] 405 Operation Information

[0265] 407 Internal Database

[0266] 409 Configuration Information

[0267] 411 Communication Information

[0268] 413 Communication command

[0269] 415 Identification Command

[0270] 417 Identification Response

[0271] 419 Communication messages

[0272] 421 Fieldbus Module

[0273] 423 Parsing Module

[0274] 425 Conversion Module

[0275] 427 Communication Interface

[0276] 500 Automation System

[0277] 501 Communication Network

[0278] 502 OPC-UA client

[0279] 503 Terminal

[0280] 505 console

[0281] 507 Field Equipment

[0282] 509 External Database

[0283] 511 External Server

[0284] 513 Cloud Server

[0285] 515 Wireless Data Connection

[0286] 516 Additional wireless data connections

[0287] 517 Fieldbus.

Claims

1. A computer-implemented method (100) for establishing a communication network (501) between at least one OPC-UA client (502) and at least one field device (507) of an automation system (500), comprising: In the identification step (101), at least one field device (507) of the automation system (500) is identified by the communication gateway (400) of the automation system (500) configured to communicate with the field device (507) via data. In the generation step (103), the communication gateway (400) generates an OPC-UA node set (401) for the identified field device (507); as well as In the node set storage step (105), the OPC-UA node set (401) is stored on the OPC-UA server (403), wherein the OPC-UA node set (401) stored on the OPC-UA server (403) can be invoked by the at least one OPC-UA client (502) of the automation system (500), and wherein the OPC-UA node set (401) can store operating information that can be provided by the at least one field device (507) in data communication, and the operating information can be read by the OPC-UA client (502).

2. The method (100) according to claim 1, wherein, Generating the OPC-UA node set (401) includes: In the first reading step (107), at least one configuration information (409) regarding the identified field device (507) is read from the internal database (407) via the communication gateway (400), wherein the configuration information (409) includes information regarding the configuration of the OPC-UA node set (401); and In the conversion step (109), the configuration information (409) read from the internal database (407) is converted into the OPC-UA node set (401).

3. The method (100) according to claim 1 or 2, further comprising: In the second reading step (111), at least one communication information (411) about the identified field device (507) is read from the internal database (407) via the communication gateway (400), wherein the communication information (411) defines at least one communication command (413) of the fieldbus protocol, wherein the communication command (413) causes the field device (507) to transmit at least one operating parameter to the communication gateway (400); and In the command storage step (113), the at least one communication command (413) is stored in the communication gateway (400).

4. The method (100) according to claim 2 or 3, wherein, The internal database (407) includes configuration information (409) and / or communication information (411) for multiple different field devices (507).

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

6. The method (100) according to any one of claims 2 to 5 further comprises: In the copying step (115), configuration information (409) and / or communication information (411) of multiple field devices (507) are copied from the external database (509) to an internal database (407) set on the communication gateway (400) via the communication gateway (400), wherein the internal database (407) is set 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 newly integrated field device (507) into the automation system (500).

8. The method (100) according to any one of the preceding claims, wherein, The identification step (101) includes: In the sending step (117), an identification command (415) is sent to the field device (507) of the automation system (500) via the communication gateway (400); and In the receiving step (119), an identification response (417) of the at least one field device (507) is received through the communication gateway (400), wherein at least one device identifier of the at least one field device (507) is defined in the identification response (417).

9. A computer-implemented method (200) for data communication between an OPC-UA client (502) and at least one field device (507) of an automation system (500), comprising: In the network generation step (201), the communication gateway (400) generates the communication network (501) between the OPC-UA client (502) and at least one field device (507) of the automation system (500) by executing the method (100) for generating a communication network (501) between the OPC-UA client (502) and at least one field device (507) according to any one of the preceding claims 1 to 8. In the message receiving step (203), a communication message (419) of the field device (507) is received through the communication gateway (400), wherein the communication message (419) contains at least one operating information (405) about at least one operating parameter of the field device (507); In the information storage step (205), the operating information (405) regarding the operating parameters of the field device (507) is stored in the OPC-UA node set (401) on the OPC-UA server (403); and In the provisioning step (207), the communication gateway (400) provides the OPC-UA client (502) with operating information (405) about the operating parameters of the field device (507) via the OPC-UA node set (401) of the OPC-UA server (403).

10. The method (200) according to claim 9, wherein, The communication gateway (400) periodically receives communication messages (419) from the field device (507), and the operation information (405) of the communication message (419) is correspondingly periodically stored 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 parameters of the field device (507) include the operating time and / or operating power and / or maintenance status and / or service life and / or the next maintenance schedule of the field device (507).

12. The method (200) according to any one of 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) through a point-to-point channel and / or a message channel and / or a publish-subscribe channel and / or a message bus and / or a data type channel.

13. A computer-implemented method (300) for performing data analysis on operational information (405) of field devices (507) via an OPC-UA client (502) of an automation system (500), comprising: In the information receiving step (301), the OPC-UA client (502) receives the operating information (405) provided by the method (300) for data communication between the OPC-UA client (502) and at least one field device (507) of the automation system (500) according to any one of claims 9 to 12. In analysis step (303), the operational information (405) is analyzed using the OPC-UA client (502); and In the output step (305), if the analysis determines the functional failure and / or the running time and / or the operating power and / or the maintenance status and / or the expired service life and / or the maintenance schedule of the field device (507), then an operation instruction for stopping the operation of the field device (507) and / or for replacing the field device (507) is output.

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

15. The communication gateway (400) according to claim 14, wherein, The communication gateway (400) includes: An internal database (407) containing configuration information (409) and / or communication information (411) for multiple different field devices (507); and / or A fieldbus module (421), wherein the fieldbus module (421) is configured to send communication commands (413) to a field device (507) and / or receive communication messages (419) from a field device (507) and / or identify a field device (507) in accordance with a fieldbus protocol; and / or A parsing module (423) is configured to read configuration information (409) and / or communication information (411) of field devices (507) of the automation system (500) from the internal database (407), wherein the configuration information (409) includes information on the configuration of the OPC-UA node set (401), wherein the communication information (411) defines at least one communication command (413) of the fieldbus protocol, and wherein the communication command (413) enables the field device (507) to transmit at least one 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-UA node set (401) for each identified field device (507) of the automation system (500) based on the configuration information (409) of the field device (507); and / or OPC-UA server (403), the OPC-UA server being used to store the OPC-UA node set (401) of the identified field devices (507); and / or OPC-UA communication interface (427), wherein the communication gateway (400) can connect to the OPC-UA client (502) through the OPC-UA communication interface (427), and wherein the OPC-UA node set (401) can be provided to the OPC-UA client (502) through the OPC-UA communication interface (427).

16. An automation system (500) comprising 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 perform the method (300) for data analysis as described in claim 13.

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

Images