FIELD DEVICE AND METHOD FOR INTEGRATION OF A FIELD DEVICE

Description

[0001] The invention relates to a field device of an automation system and a method for integrating such a field device into an automation system.

[0002] Field devices (also known as field equipment) can include actuators (such as control elements or valves) as well as sensors (such as transmitters). In factory and process automation, field devices are networked with a system controller (also known as a control system, such as a process control system with a process controller) via a fieldbus or real-time Ethernet. Sensor data can be collected at defined intervals and transmitted to the process controller.

[0003] The control system evaluates the data for further processing and for controlling or regulating the field devices. This can include visualizing and displaying the results of the evaluation, such as the pressure, flow rate, and temperature of a fluid, and whether a valve is open or closed. For example, the control system can display analysis and alarm data on plant panels based on this data.

[0004] In the prior art, a process control system acts as a master, querying sensors as slaves. The master controls the slave, which is connected to and communicates with the master via a bus system, and processes the data received from the slave. To do this, the master identifies the slave via the bus system and then automatically generates a device configuration to set up the slave according to its identifiers, so that the slave is ready for operation in the process control system. Document EP 1 594 023 B1 describes such a method for the automatic configuration of the process control system.

[0005] However, such a conventional configuration method requires that drivers and configurations for a large number of different field device identifiers are already stored in the process control system. This approach can be inefficient given the variety of existing process control systems combined with the large number of potential field devices.

[0006] Patent document US 2002 / 046263 A1 teaches a method for configuring an automation module using a stored configuration table.

[0007] Another conventional approach to integrating a field device into an existing automation system involves acquiring a sample of the field device. Based on this sample, development can then begin on a driver specific to the combination of field device and system controller, enabling data communication between the field device and the system controller. However, during driver development, it may become apparent that the field device, correctly selected in its function as an actuator or sensor, is unsuitable for data communication with the automation system's control system. Therefore, this process must be repeated with uncertain success for another field device.

[0008] The invention is therefore based on the objective of providing a field device that can be reliably and efficiently integrated into a variety of different automation systems.

[0009] This problem is solved by the features of the independent claims. Advantageous embodiments and further developments of the invention are specified in the dependent claims.

[0010] Exemplary embodiments of the invention are described below with partial reference to the figures.

[0011] According to a first aspect, a field device of an automation system comprises at least one actuator and / or at least one sensor (hereinafter referred to as an actuator and / or sensor). Furthermore, the field device comprises a control unit that is in data communication with the actuator and / or sensor. The control unit is configured to acquire and / or output data from the actuator and / or sensor via the data connection. The field device also includes a data interface configured to exchange data packets between the control unit and a system controller of the automation system.The control unit is further designed to establish a TCP connection with the system control via the data interface according to a transmission control protocol (TCP), and to receive a request message (REQ message) about the data of the actuator and / or sensor and to send a response message (RES message) about the data to the system control via the TCP connection according to a hypertext transfer protocol (HTTP).

[0012] Exemplary embodiments of the field device can be integrated into the automation system by means of HTTP-compliant REQ and RES messages to the data, preferably without the development of field device-specific drivers for the system control of the automation system and / or without a field device-specific configuration of the system control of the automation system.

[0013] Exemplary embodiments of the field device can communicate with the control system of the automation system using HTTP-compliant REQ and RES messages without the development of field-device-specific drivers and / or without field-device-specific configuration. Preferably, the control unit of the field device is configured to receive the data in the REQ message, output it to the actuator via the data connection, and send an acknowledgment of the data output and / or feedback of an actuation (e.g., movement) of the actuator in response to the output in the RES message. Alternatively or additionally, the control unit of the field device is configured to receive an instruction to acquire the data in the REQ message, acquire the data from the sensor via the data connection, and send the acquired data to the control system in the RES message.

[0014] The field device, preferably the control unit, can act as a server within the TCP connection. Alternatively or additionally, the system control unit can act as a client within the TCP connection.

[0015] The field device can also be called a field instrument. The field device can be an industrial electronics component.

[0016] The field device can be designed for integration into a production plant or a process plant. The field device can include actuators (e.g., control elements, valves, etc.) and / or sensors (e.g., transmitters), preferably in a production or process automation system.

[0017] The control unit can be configured to establish a TCP connection with the system controller via the data interface according to TCP by being configured to receive a synchronization packet (SYN packet) from the system controller via the data interface according to TCP to establish the TCP connection with the system controller and to send an acknowledgment (SYN-ACK) of the receipt of the SYN packet to the system controller.

[0018] The control unit communicating with the actuator and / or sensor can be configured to process the data from the actuator and / or sensor (e.g., acquired, output, or to be output). Alternatively or additionally, the control unit can be configured to receive the data from the actuator and / or sensor (e.g., acquired, output, or to be output) in data packets from the system controller and / or to send (i.e., transmit) the data to the system controller in data packets.

[0019] The data interface can be configured to exchange the data of the actuator and / or sensor between the control unit and the system control of the automation system.

[0020] The system controller can be a control center or process control system of the automation system. Alternatively or additionally, the system controller can be a programmable logic controller (PLC) and / or a virtual machine (VM) with a (for example, local) application. The application can be designed for planning and / or operating energy generation units and / or consumption units. The field device can be part of such a generation unit or consumption unit.

[0021] The automation system can be a manufacturing plant or a process plant.

[0022] Exemplary implementations of the field device can use the control unit as a server, particularly as a REST server, to flexibly provide data to the system controller using HTTP. This simplifies the adaptation or development of a client for the system controller to receive or (for example, asynchronously) record the data. Alternatively or additionally, the control unit can provide a stateless (for example, a "Representational State Transfer" or REST-compliant) interface to the system controller via the TCP connection using HTTP messages.

[0023] The same or other embodiments of the field device can enable the adaptation or development of a client for the control system to receive or (for example, asynchronously) record the data before the field device is integrated into the automation system or connected to the control system of the automation system via the data interface, preferably before the field device is acquired for the automation system. For example, the adaptation or development of a client for the control system can begin or be carried out by accessing a corresponding control unit (for example, of the field device manufacturer) via the TCP connection. For the integration of the field device, it may then be sufficient to adapt an Internet Protocol address (IP address) of the field device in the client.

[0024] The REQ message can contain a request for data. The RES message can contain the requested data.

[0025] The REQ message can specify a time period. The RES message can include the data acquired by the actuator and / or sensor or data output to the actuator and / or sensor within the specified time period.

[0026] Data can be associated with timestamps. These timestamps can indicate the point in time when the data was captured and / or output. For example, the RES message can include the data to which timestamps within the specified time period are assigned. Alternatively or additionally, the RES message can include the timestamps associated with the data.

[0027] For example, the data can comprise a data series (such as a series of measurements), and the control unit can record this data series. After a communication failure between the control unit and the control unit (for example, an interruption in the exchange of data packets and / or the TCP connection), a gap in the recorded data series can be filled selectively or with minimal communication resources using the specified time period.

[0028] The REQ message can specify plaintext. The RES message can contain the data corresponding to the plaintext.

[0029] The control unit can store the captured and / or output data. The control unit can be configured to search the captured, output, or stored data using the plaintext specified in the REQ message. The data can match the plaintext specified in the REQ message if a key term (e.g., a keyword) is associated with the data and is contained within the plaintext.

[0030] Alternatively or additionally, plaintext descriptions can be assigned to the data. For example, the RES message can contain the plaintext descriptions assigned to the data.

[0031] The data can include not only raw data from the actuator and / or sensor, but also a description (for example, a description of a measuring point). Exemplary embodiments of the device can enable the system control to display an instrument panel (also known as a "dashboard" or "panel") based on communication with the control unit.

[0032] The data can be configured to allow the system controller to evaluate, visualize, and / or display the data (for example, a result of the evaluation). For instance, the data can include measured values ​​and an associated physical unit to indicate pressure, flow rate (preferably a flow rate), and / or temperature of a fluid. Alternatively or additionally, the data can include a symbol to indicate the measured value or the operating status (e.g., valve open or closed).

[0033] The plaintext specified by the REQ message and / or the plaintext associated with each data item may include a keyword or a block of text to describe the data.

[0034] For example, the RES message can include the data whose plaintexts contain the plaintext specified in the REQ message (for example, completely or at least one keyword). Alternatively or additionally, the RES message can include the plaintexts associated with the data.

[0035] The data can comprise at least two different time series. The associated plaintext can specify the respective time series. Alternatively or additionally, the data can comprise at least two different measured values. The associated plaintext can specify the respective measured value.

[0036] Optionally, the RES message can include a reference to a previous RES message, where the previous RES message contains the plaintexts associated with the data. Repetition of the same plaintexts in different or consecutive RES messages can be omitted, for example, to use communication resources more efficiently.

[0037] The field device can comprise at least two different actuators and / or sensors that are in data communication with the control unit. The plaintext associated with the data can specify the respective actuator or sensor from which the data is acquired and / or to which the data is to be output or be output.

[0038] The field device can be a measuring device (also: measuring instrument).

[0039] The plaintext specified in the REQ message and / or the plaintext associated with the data can include a description of a measurement point. Alternatively or additionally, the data can include at least one measured value, and the associated plaintext can specify a physical unit for that at least one measured value. Alternatively or additionally, the plaintext can include an identifier for the field device and / or the actuator and / or the sensor.

[0040] The data can include measured values ​​acquired by the sensor. Alternatively or additionally, the data can include control instructions to be issued to the actuator. Alternatively or additionally, the data can include operating parameters acquired by and / or issued to the actuator and / or sensor. The control instructions and / or operating parameters can determine an operating state of the actuator and / or sensor.

[0041] The data may also include timestamps. Alternatively or additionally, the timestamps may be assigned to one of the measured values ​​and / or one of the control instructions and / or one of the operating parameters. For example, the assigned timestamp may indicate the time of acquisition of the measured values ​​and / or the output of the control instructions and / or the acquisition and / or output of the operating parameters.

[0042] The measured values ​​can include electrical voltage and / or frequency.

[0043] The RES message can contain the data in an HTTP document. Alternatively or additionally, the RES message (for example, the HTTP document) can contain the data according to JavaScript Object Notation (JSON), Extensible Markup Language (XML), or as Comma-Separated Values ​​(CSV).

[0044] The data can be contained in the message body of the RES message. Alternatively or additionally, a header of the RES message can specify a firmware version of the field device, preferably a firmware version of the firmware executed by the control unit, and / or include a reference to the preceding RES message.

[0045] The REQ message and / or the RES message over the TCP connection can be contained in the data packets of the Internet Protocol (IP data packets or IP packets for short).

[0046] The control unit can act as a server for the TCP connection. Data communication between the control unit and the TCP connection, including REQ and RES messages, can be simulated by a server outside the automation system.

[0047] The control unit can also be configured to establish a TCP connection with a server outside the automation system via its data interface and to receive a message from the server in accordance with HTTP. The message from the server can include a configuration for the field device. The server can be configured to select the configuration via the internet (for example, as a web service). The server can be identical to or different from a server simulating data communication with the control unit.

[0048] The control unit can also be configured to establish a TCP connection with a server outside the automation system via its data interface and to send a message to the server in accordance with HTTP. The message can indicate an operating state or a fault state of the field device. The server can be identical to or different from a server simulating data communication with the control unit and / or a server sending the field device configuration.

[0049] According to a second aspect, a method for integrating a field device into an automation system is provided. The field device can be a field device as defined in the first aspect. The method includes a step of setting up (for example, adapting and / or developing and / or testing) an application interface of the automation system's control unit for communication with the field device's data interface. The application interface is configured to send the REQ message and receive the RES message in the data packets over the TCP connection. The data packets include an address field for the field device or an address field for the field device's data interface. During setup, the address field specifies an initial address pointing to a server outside the automation system.The procedure further includes a step of integrating the field device into the automation system by changing the address field in the data packets to a second address referring to the field device or the data interface of the field device within the automation system.

[0050] The server outside the automation system (also: external server) can comprise an instance or copy of the field device's control unit. During the setup step, a configuration of the system control (preferably the application interface) for communication via the TCP connection with the field device's data interface can be established (for example, developed, adapted, or tested), preferably without acquiring a physical copy of the field device.

[0051] The instance or copy of the field device's control unit can also be referred to as the field device's digital twin. This instance or copy of the field device's control unit can be accessed via the first address in the application interface setup step for communicating REQ and RES messages.

[0052] The first address can be a network address of the external server. Alternatively or additionally, the second address can be a network address of the field device installed and / or connected in the automation system (for example, the address of the field device's data interface). Both the first and second addresses can be IP addresses, for example, according to IPv4 or IPv6.

[0053] The first and second addresses can be different. The first and second addresses can differ (preferably at least) in a section of the address field. This section can specify different subnets, for example, according to a subnet mask or a prefix length. The subnet specified by the first address can correspond to a subnet encompassing the external server. The subnet specified by the second address can correspond to a subnet encompassing the automation system and / or the control panel.

[0054] Changing the address field for the data interface of the field device can include changing a destination address in the data packet (for example, in the data packet of the REQ message) and / or a sender address in the data packet (for example, in the data packet of the REQ message).

[0055] According to a third aspect, a control system for an automation system is provided. The control system can be configured to execute the procedure according to the second aspect. Alternatively or additionally, the control system can include an application interface. The application interface of the control system can be configured to communicate with the data interface of a field device according to the first aspect. Alternatively or additionally, the application interface of the control system can be configured to send a REQ message according to a Hypertext Transfer Protocol (HTTP), preferably the REQ message according to the first or second aspect, and to receive a RES message according to HTTP, preferably the RES message according to the first or second aspect, preferably in data packets of a TCP connection.

[0056] In every aspect, an address field in the data packets, for example for a network address of the field device or the data interface of the field device, can be optionally: (preferably for setting up the application interface of the control system) specify the first address or refer to the server outside the automation system and (preferably for integrating the field device) specify the second address or refer to the field device inside the automation system.

[0057] The procedure according to the second aspect and / or the system control according to the third aspect may each comprise any step and / or any feature disclosed in the context of the first aspect, or a corresponding step or feature.

[0058] The invention is explained in more detail below with reference to the drawings and by way of preferred embodiments.

[0059] They show: Fig. 1 a schematic block diagram of an automation system with field devices according to a first embodiment; Fig. 2 a schematic communication diagram for the integration of a field device into an automation system according to a second embodiment; and Fig. 3 a schematic flowchart of a method for integrating a field device into an automation system.

[0060] Fig. 1 Figure 1 schematically shows a block diagram of an exemplary automation system 100 with first embodiments of a field device generally designated by reference numeral 110. The field device 110 can be industrial electronics, for example a measuring instrument.

[0061] The automation system 100 comprises at least one embodiment of the field device 110, which is read (e.g., monitored) and / or controlled (e.g., regulated) by a system controller 120 of the automation system 100. While in Fig. 1 Where a system controller 120 is shown, several system controllers 120 can be configured redundantly or hierarchically for reading and / or controlling the field device 110 in the automation system 100.

[0062] The in Fig. 1The first embodiments of the field device 110 shown each comprise an actuator 112 and / or sensor 112, as well as a control unit 116 that is in data communication 114 with the actuator 112 and / or sensor 112. The control unit 116 is configured to acquire and / or output data from the actuator 112 and / or sensor 112 via the data connection 114. Furthermore, the field device 110 comprises a data interface 118, which is configured to exchange data packets between the control unit 116 and the system controller 120 of the automation system 100.

[0063] The data interface 118 can include a network interface. For example, the data interface 118 can be configured for communication over a local area network 102. The local area network 102 can include one or more wire pairs for balanced signal transmission. Alternatively or additionally, the local area network 102 can include at least one network switch that connects different branches of the wire pairs for exchanging data packets. The local area network 102 can include Ethernet, preferably according to a standard of the IEEE 802.3 series, and / or Real-Time Ethernet and / or Single-Pair Ethernet (SPE).

[0064] Alternatively or additionally, the data interface 118 can be configured for communication via a local area network 104, for example, a wireless local area network (WLAN) according to the Wi-Fi Alliance or the IEEE 802.11 series of standards, or a cellular network according to a radio access technology of the Third Generation Partnership Project (3GPP), preferably according to the fifth generation radio access technology (also known as Fifth Generation New Radio or 5G NR). For this purpose, the data interface 118 can include a baseband chip configured to send or receive data packets using a protocol stack according to the radio access technology. For example, the data interface 118 can be configured for ultra-reliable low-latency communication (URLLC) according to the standards document 3GPP TR 38.824 V16.0.0 and / or the standards document 3GPP TR 33.825 V16.0.1.

[0065] The wired network 102 and / or the wireless network 104 can form the subnetwork (for example, a campus network) of the automation system 100. The integrated field device 110 and the system controller 120 are connected to the same subnetwork.

[0066] The control unit 116 is further designed to establish a TCP connection with the system controller 120 via the data interface 118 in accordance with a transmission control protocol (TCP) and to receive a request message (REQ message) regarding the data of the actuator and / or sensor via the TCP connection in accordance with a hypertext transfer protocol (HTTP) and to send a response message (RES message) regarding the data to the system controller 120.

[0067] In a first variant of each embodiment, for example as in the Fig. 1In a schematic representation, the control unit 116 and the data interface 118 are arranged outside the sensor 112 and / or actuator 112, respectively. In a second variant of each embodiment, the control unit 116 and / or the data interface 118 are integrated into the sensor 112 and / or actuator 112. In a third variant of each embodiment, several sensors 112 and / or actuators 112 are connected to the control unit 116 via data connections 114.

[0068] To integrate the field device 110 (for example, industrial electronics) into the automation system 100, the data exchange (i.e., communication) within the automation system 100 is established after the physical installation of the field device 110. The integration can be monitored or performed, for example, by a developer from a system integrator.

[0069] Commissioning of the field device 110 can precede its integration. Commissioning of the field device 110 (e.g., the industrial electronics) can include operating the field device 110 until it is fully commissioned, for example, until the field device 110 is physically installed and / or connected and / or until it is configured to acquire data using the sensor 112 and / or to output data at the data interface 118. Once commissioned, the field device 110 is ready for integration into the automation system 100.

[0070] The automation system 100, for example the control unit 120, can be a system superimposed on the field device 110. Alternatively or additionally, the control unit 120 can be a programmable logic controller (PLC) and / or a virtual machine. Alternatively or additionally, the control unit 120 can include and / or execute a local application and / or the control unit 120 can include and / or execute a development environment for an application interface 122 (for example, an API).

[0071] In the claimed embodiment, the development environment is a tool ,This tests communication with data interface 118 or a functionally equivalent data interface of an external server 200, and / or outputs source code sections (also known as "code snippets") for communication with data interface 118. These source code sections can be used in the local application of the Control Panel 120.

[0072] The local application can include a control (preferably a regulation) of the field devices 110 networked with the system control 120 via the application interface 122.

[0073] During the integration phase of the field device 110 (e.g., industrial electronics), communication is established between the field device 110 (e.g., as the server of the TCP connection) and the control system 120 (e.g., as the client of the TCP connection) and / or the control system 120 (e.g., the PLC or the local application) is trained to process the data and / or to check the data for plausibility and / or to write plausible data to a database (e.g., a database of the automation system 100 or an external database outside the automation system 100).

[0074] Conventional field devices typically include a Modbus server. Integration usually involves developing drivers for communication between the field device and the system controller. The developer consults the Modbus server documentation and selects the values ​​required for the application. The driver is then implemented in a programming environment. Typically, a prototype field device is purchased first, then tested on-site at the workstation or within the automation system's network, before driver development begins.

[0075] In contrast, the first embodiment of the field device 110 includes the control unit 116, which is able to establish a TCP connection with the system control 120 without field device-specific drivers and is able to exchange messages regarding the data (for example, instructions about the data or the data itself) according to HTTP.

[0076] For example, the RES message can be self-contained. In addition to the data, the RES message can include supplementary information. This supplementary information can describe the data (preferably as plain text or a text block) and / or include a configuration of the Control Panel 120 for processing or outputting the data.

[0077] In each embodiment, the control unit 120 can also be networked (i.e., connected to exchange data packets) with an external server 200 located outside the automation system 100. The attributes "external" and "outside" can be used synonymously. The external server 200 can be located outside the automation system 100 if a router 202 is positioned between the control unit 120 and the external server 200, which forwards the data packets exchanged between the control unit 120 and the external server 200.

[0078] The external server 200 can provide the same functionality of the control unit 116 that the control unit 116 provides to the field device 110 via the data interface 118.

[0079] By providing the functionality of the control unit 116 from the external server 200, the integration capability of the field device 110 can be ensured by establishing a TCP connection between the control unit 116 and the external server 200 and / or by exchanging messages according to HTTP, preferably before acquiring a unit of the field device 110. Alternatively or additionally, the integration of the field device 110 can be prepared by exchanging messages according to HTTP, preferably before acquiring a unit of the field device 110.

[0080] Fig. 2Figure 1 schematically shows a communication diagram for integrating a field device 110 into an automation system 100 according to a second embodiment. While the following description, for the sake of clarity and conciseness, details the interaction of the field device 110, the system controller 120, and the external server 200 according to the second embodiment, this disclosure does not presuppose such a complete system. Rather, the functional features disclosed for the interaction are disclosed separately for the field device 110, the system controller 120, and the external server 200.

[0081] Furthermore, the field device 110, the system control 120 and the external server 200 according to the second embodiment can each be a further development of the field device 110, the system control 120 and the external server 200 according to the first embodiment.

[0082] The control unit 116 can function as a server, for example with regard to the TCP connection and / or the messages according to HTTP. Due to this feature of the field device 110, the second embodiment of the field device 110 makes it possible to provide a digital twin of the field device 110 outside the automation system, namely by means of an external server 200.

[0083] The external server 200 exhibits communication behavior that is identical to the communication behavior of the field device 110 via the data interface 118. Therefore, the external server 200 can be described as a digital twin of the field device 110 or the control unit 116.

[0084] For example, the control unit 116 of the field device 110 comprises a memory and at least one processor that executes instructions encoded in the memory of the field device 110, wherein a control module containing the encoded instructions is stored in the memory of the field device 110. By executing the control module, the control unit 116 can, for example, output data to the actuator 112 via the data connection 114 based on data packets received at the data interface 118, and / or send data acquired by the sensor 112 via the data connection 114 in data packets from the data interface 118.

[0085] For example, the external server 200 comprises a memory and at least one processor that executes instructions encoded in the memory of the external server 200, wherein the same control module is stored in the memory of the external server 200 as is stored in the memory of the field device 110.

[0086] Preferably, the external server 200 is accessible via the Internet. The external server 200 is configured (for example, by means of its control module) to receive at least one message 130 from the control unit 120 (for example, a REQ message 130 corresponding to a subsequent REQ message 140 to the field device 110). Furthermore, the external server 200 is configured (for example, by means of its control module) to offer a message 132 (for example, a reply, preferably a RES message 132 corresponding to a subsequent RES message 142 from the field device 110) via the Internet in response to the received message 130, preferably to send it to the control unit 120.

[0087] An application interface 122 of the system control 120 for the field device 110 can be set up using the external server 200, preferably without having a copy of the field device 110.

[0088] For example, a developer can program the control unit 120 as its client against the external server 200 (as a digital twin) on the internet. This allows the developer to prepare or execute the integration of the field device 110 into the automation system 100 without needing a physical prototype of the field device 110 (e.g., the industrial electronics) on site.

[0089] Alternatively or additionally, the developer can begin the evaluation of the field device 110 (for example, the industrial electronics) without a prototype of the field device 110 being on site.

[0090] Each of the REQ and RES messages according to HTTP Each element can (preferably each) be contained within a data packet (for example, an IP data packet). The respective data packet comprises an address field for a sender address (also known as a "source address") and an address field for a destination address (also known as a "destination address").

[0091] For example, the address field of the sender address of REQ message 130 can refer to the control panel 120, i.e., include the address 121 of control panel 120. The address field of the destination address of REQ message 130 can refer to the external server 200, i.e., include the address 201 of the external server 200 (also: the first address).

[0092] For example, the destination address field of RES message 132 can refer to Control Panel 120, i.e., it can include address 121 of Control Panel 120. The sender address field of RES message 132 can refer to external server 200, i.e., it can include address 201 of external server 200 (also: the first address).

[0093] Using the external server 200 simplifies, shortens the time and involves fewer risks in the evaluation process for the integration or integration suitability of the field device 110 (e.g. a prototype evaluation process) compared to the conventional procurement of a sample.

[0094] After setting up the application interface 122 of the control unit 120 using the external server 200, only the first address needs to be replaced by the address of the field device 110 in order to integrate the field device 110 into the automation system 100.

[0095] For example, the address field of the sender address of REQ message 140 can refer to the control unit 120, i.e., it can include address 121 of control unit 120. The address field of the destination address of REQ message 140 can refer to the field device 110, i.e., it can include address 111 of field device 110 (also: the second address).

[0096] For example, the address field of the destination address of RES message 142 can refer to the control unit 120, i.e., it can include address 121 of control unit 120. The address field of the sender address of RES message 142 can refer to the field device 110, i.e., it can include address 111 of field device 110 (also: the second address).

[0097] Thus, after the system control 120 has been set up using the external server 200, the integration can essentially involve replacing the first address with the second address.

[0098] The data packets are preferably structured according to the Internet Protocol (IP) (i.e., so-called IP data packets). The addresses are preferably IP addresses.

[0099] The in Fig. 2 The second embodiment shown in the communication diagram can include a web service of the external server 200 for system integration without a sample of the field device 110.

[0100] For example, the control module, which is executed by both the control unit 116 of the field device 110 and the external server 200, can include the function of a REST server for the field device 110 (for example, a complex measuring instrument).

[0101] Alternatively or additionally, the control module implemented by the control unit 116 of the field device 110 can include the function of a REST server for the field device 110 (for example, for a complex measuring instrument). Based on the control module or the REST server of the field device 110, a REST server 200 can be developed on the internet, which technically provides exactly the same responses as the REST server of the field device 110. This results in a virtual or digitized representation of the field device 110 with regard to communication via the data interface 118.

[0102] In the step of setting up the control panel 120 (preferably the application interface 122), the developer can then develop a client that communicates with the REST server 200 on the Internet.

[0103] During the integration step of the field device, the first address is changed to the second address (for example, by changing a network parameter of the client). This significantly speeds up the integration of field device 110 compared to the conventional method.

[0104] The technical solution for integrating the field device 110 into the automation system 100 (in short: system integration), for example, the data interface 118 for exchanging HTTP messages via a TCP connection, can also be used to configure the field device 110. The field device 110 (for example, an industrial electronic device) is configured by guiding the user through a web-based service of the external server 200 (or another external server) on the internet, leading to their individual configuration of the field device 110. This guidance via web services results in increased convenience and a reduction in the time required to configure the field device 110.

[0105] Alternatively or additionally, the technical solution for system integration, for example, the data interface 118 for exchanging HTTP messages via a TCP connection, can also be used to support and / or monitor and / or remotely maintain the field device 110. For example, the control unit 116 can be configured to send an operating status of the field device 110 to the external server 200 (preferably periodically or triggered by a fault event). Alternatively or additionally, the field device (e.g., industrial electronics) can be supported by guiding the user through a web-based service of the external server 200 (or another external server) on the internet, which, for example, leads to an initial diagnosis.Management via the web service leads to increased satisfaction in after-sales service or can resolve fault conditions earlier in order to avoid or shorten downtime of the automation system 100.

[0106] Fig. 3 Figure 1 shows a schematic flowchart of a method 300 for integrating a field device 110 into an automation system 100 according to a third embodiment. The field device 110 integrated or to be integrated can be designed according to the first and / or the second embodiment.

[0107] In step 302, an application interface 122 of the control unit 120 of the automation system 100 is configured for communication with the data interface 118 of the field device 110. The application interface 122 is configured to send the REQ message and receive the RES message in the data packets via the TCP connection. During configuration 302, the data packets include an address field for the data interface of the field device 110, specifying a first address 201 that points to a server 200 outside the automation system 100. The procedure 300 further includes step 304 of integrating the field device 110 into the automation system 100 by changing the address field in the data packets to a second address 111 that points to the data interface of the field device 110 within the automation system 100.

[0108] As can be seen from the preceding embodiments, embodiments of the field device 110 and the method 300 can enable the establishment or verification of communication with the control unit 120 even before a unit of the field device 110 has been procured, by the control unit 120 first communicating with the external server 200. This communication between the control unit 120 and the external server 200 can be essentially the same or indistinguishable from, or equivalent to, the subsequent communication between the control unit 120 and the field device 110 (for example, except for address 111 in the address field for the field device 110). The integration of the field device 110 can essentially involve adjusting the address in the address field of the data packets from address 201 of the external server 200 to address 111 of the field device 110 in the automation system 100.

[0109] This allows a user of the system controller 120, for example, a developer of the local application, to assess whether and / or how the field device 110 can be integrated into the automation system 100. For example, the user thus assumes the role of a recommender or advisor who prepares or supports the decision regarding the procurement of the field device 110 before a first unit of the field device 110 is acquired. This saves time and resources compared to the conventional approach, for example, in the transport and, if necessary, the return transport of a sample unit.

[0110] The developer can, for example, provide an assessment of whether the field device is suitable for integration and / or should be purchased and / or used in series production later.

[0111] By configuring the control unit 116 of an embodiment of the field device 110 for communication according to HTTP via the TCP connection, data communication (preferably at a later stage) between the system controller 120 and the field device 110 can be established (for example, reproduced, adapted, developed, or verified) by means of equivalent data communication between the system controller 120 and the external server 200. During data communication with the external server 200, establishing the TCP connection and / or sending the REQ message and / or receiving the RES message can proceed or be executed from the perspective of the system controller 120 in the same way as during data communication with the field device 110 integrated into the automation system 100, for example, even if the TCP connection of the data communication with the external server 200 leads out of the automation system's subnet via a router 202.This allows the embodiments of the field device 110 or the method 300 for integrating the field device 110 to significantly simplify for a user (for example, the developer) the preparation of the decision on the integration and / or the execution of the integration of the field device 110.

[0112] Although the invention has been described with reference to exemplary embodiments, it is apparent to those skilled in the art that various modifications can be made and equivalent components can be used as replacements. Furthermore, many modifications can be made to adapt a particular situation, sensor, or actuator to the teaching of the invention. Consequently, the invention is not limited to the disclosed embodiments but encompasses all embodiments that fall within the scope of the appended claims. Reference symbol list Automation system 100 Local area network, preferably 4-pair Ethernet or 1-pair Ethernet (SPE) 102 Local wireless network, preferably based on the fifth generation of mobile communications 104 Field device, also field instrument (FG), preferably industrial electronics or measuring instrument 110 Network address, preferably IP address, of the field device 111 Actuator and / or sensor of the field device 112 Data connection between control unit and actuator and / or sensor 114 Control unit of the field device 116 Data interface between field device and system control 118 Control system of the automation system 120 Network address, preferably IP address, of the control panel 121 Application interface of the control panel 122 REQ message during setup 130 RES message during setup 132 REQ message after integration 140 RES message after integration 142 External server outside the automation system 200 Network address, preferably IP address, of the external server 201 Gateway router between automation system and external server 202 Method for integrating a field device 300 Step in setting up an application interface 302 Step of integrating the field device 304

Claims

1. A method (300) for integrating a field device (110) into an automation system (100), comprising: - configuring (302) an application interface (122) of a system controller (120) of the automation system (100) to communicate with a data interface (118) of the field device (110), wherein the application interface (122) is configured to send, in data packets, a request message, REQ message (130, 140), and to receive a response message, RES message (132, 142), over a TCP connection, wherein during configuration (302) the data packets comprise an address field for the data interface (118) of the field device (110) that indicates a first address (201) pointing to a server (200) outside of the automation system (100), wherein configuring (302) comprises testing the communication with a data interface of the external server (200) that is functionally identical to the data interface (118); and - integrating (304) the field device (110) into the automation system (100) by changing the address field in the data packets into a second address (111) pointing to the data interface (118) of the field device (110) within the automation system (100), wherein by changing a network parameter of the client of the system controller (120) the first address (201) is changed into the second address (111).

2. The method (300) of claim 1, further comprising: - providing the field device (110) of the automation system (100), comprising an actuator (112) and / or sensor (112), a control unit (116) that is in data communication (114) with the actuator (112) and / or sensor (112), which is configured to acquire data of the actuator (112) and / or sensor (112) over the data connection (114) and / or to output data, and the data interface (118), which is configured to exchange data packets between the control unit (116) and the system controller (120) of the automation system (100), wherein the control unit (116) is further configured to, ∘ establish, over the data interface (118) according to a Transmission Control Protocol, TCP, the TCP connection with the system controller (120), and ∘ over the TCP connection according to a Hypertext Transfer Protocol, HTTP, receive the request message, REQ message, relating to the data of the actuator (112) and / or sensor (112) and send the response message, RES message, relating to the data to the system controller (120).

3. The method (300) of claim 1 or 2, wherein the REQ message comprises a request of the data and the RES message comprises the requested data.

4. The method (300) of any of claims 1 to 3, wherein the REQ message indicates a time period and the RES message comprises the data acquired by the actuator (112) and / or sensor (112) in the indicated time period or the data output to the actuator (112) and / or sensor (112).

5. The method (300) of any of claims 1 to 4, wherein timestamps are associated with the data, which each indicate a point in time of acquiring and / or of outputting the data.

6. The method (300) of any of claims 1 to 5, wherein the REQ message specifies a plain text and the RES message comprises the data corresponding to the plain text.

7. The method (300) of one of claim 6, wherein plain texts are associated with the data, which each describe the data, preferably wherein the RES message comprises the plain texts associated with the data; and / or wherein the field device (110) comprises at least two different actuators (112) and / or sensors (112) being in data communication with the control unit (116), and the plain text associated with the data indicates the respective actuator (112) or sensor (112) from which the data are acquired and / or to which the data are output or are to be output.

8. The method (300) of any of claims 6 to 7, wherein the plain text specified by the REQ message and / or the plain text respectively associated with the data comprises a description of a measurement point, and / or wherein the data comprise at least one measured value and the associated plain text indicates a physical unit of the at least one measured value, and / or wherein the plain text comprises an identifier of the field device (110) and / or of the actuator (112) and / or of the sensor (112).

9. The method (300) of any of claims 1 to 8, wherein the data comprises: - measured values acquired by the sensor (112); and / or - control instructions to be output to the actuator (112); and / or - operating parameters acquired by the actuator (112) and / or sensor (112) and / or output to the actuator (112) and / or sensor (112), which determine an operating state of the actuator (112) and / or sensor (112).

10. The method (300) of any of claims 1 to 9, wherein the RES message comprises the data in an HTTP document, preferably according to a JavaScript Object Notation, JSON, or an Extensible Markup Language, XML, or as comma-separated value (CSV).

11. The method (300) of any of claims 1 to 10, wherein the REQ message and the RES message are contained in the data packets of the Internet Protocol, IP packets, over the TCP connection.

12. The method (300) of any of claims 2 to 11, wherein the control unit (116) is a server of the TCP connection, and wherein a data communication comprising the REQ message and the RES message of the control unit (116) over the TCP connection is simulatable by the server (200) outside of the automation system (100).

13. The method (300) of any of claims 2 to 12, wherein the control unit (116) is further configured to establish, over the data interface (118), a TCP connection with the server (200) outside of the automation system (100) and to receive, over the TCP connection with the server (200), a message according to HTTP, wherein the message from the server (200) comprises a configuration of the field device (110).

14. The method (300) of any of claims 2 to 13, wherein the control unit (116) is further configured to establish, over the data interface (118), a TCP connection with the server (200) outside of the automation system (100) and to send, over the TCP connection with the server (200), a message according to HTTP, wherein the message indicates an operating state or an error state of the field device (110).

15. A system controller (120) of an automation system (100), wherein the system controller (120) is configured to carry out the method (300) according to any of claims 1 to 15.