Field device and method of integrating a field device

Abstract

The invention relates to a method for integrating a field device (110) in an automation system. The field device (100) comprises an actuator (112) and / or a sensor (112) and a control unit (116) having a data connection (114) to the actuator (112) and / or the sensor (112), which is configured to detect and / or output data of the actuator (112) and / or the sensor (112) via the data connection (114). The field device (100) further comprises a data interface (118) configured to exchange data packets between the control unit (116) and a system controller (120) of the automation system (100), wherein the control unit (116) is further configured to establish a Transmission Control Protocol, TCP, connection to the system controller (120) via the data interface (118) and to receive a Request Message, REQ message, for data of the actuator (112) and / or the sensor (112) and to send a Response Message, RES message, for the data to the system controller (120) via the TCP connection according to the Hypertext Transfer Protocol, HTTP.

Description

TECHNICAL FIELD

[0001] The present invention relates to a field device of an automation system and a method of integrating such a field device in an automation system. BACKGROUND

[0002] Field devices (also referred to as field devices in the professional terminology) can comprise actuators (such as final elements or valves) as well as sensors (such as measuring transducers). In factory and process automation, field devices are networked with system controllers (also referred to as control systems in the professional terminology, such as process control systems with process controllers) via field buses or real-time Ethernet. The data of the sensors can be acquired at fixed intervals and transmitted to the process controller.

[0003] The system controller evaluates these data in order to carry out further processing and to control or regulate the field devices. This includes the visualization and display of evaluation results, such as the pressure, flow and temperature of a fluid, and whether a valve is open or closed. The system controller can display analysis and alarm data on a device panel, for example, based on these data.

[0004] In the prior art, the process control system assumes the function of a master device, which interrogates the sensors as slave devices. The master device controls the slave devices connected to it via the bus system and in communication with it and processes the data received from the slave devices. For this purpose, the master device identifies the slave devices via the bus system in order to subsequently automatically generate a device configuration for setting up the slave devices based on the identification, so that the slave devices are ready for operation in the process control system. The document EP 1 594 023 B1 describes an above-mentioned method for automatically configuring a process control system.

[0005] But the prerequisite for this conventional configuration method is that drivers and configurations for a plurality of different identifications of field devices are stored in the process control system. Due to the large number of different process control systems and a plurality of potential field devices, the aforementioned approach is inefficient.

[0006] Another conventional approach to integrating field devices in an existing automation system is to procure a copy of the field device. In combination with the copy, it is possible to start developing a driver suitable for the combination of the field device and the system controller, so that data communication between the field device and the system controller is possible. But it can be found during the development of the driver that the correctly selected field device in terms of actuator or sensor functionality is not suitable for data communication with the control system of the automation system, so that the aforementioned approach has to be repeated for another field device, which is not necessarily successful. SUMMARY

[0007] In view of the above, it is an object of the present application to provide a field device which can be reliably and efficiently integrated in a plurality of different automation systems.

[0008] Embodiments of the present application are described below, partly in conjunction with the enclosed drawings.

[0009] According to a first aspect, a field device of an automation system comprises at least one actuator and / or at least one sensor (in short: actuator and / or sensor). The field device further comprises a control unit which has a data connection to the actuator and / or sensor. The control unit is configured to detect and / or output data of the actuator and / or sensor via the data connection. The field device further comprises a data interface which is configured to exchange data packets between the control unit and a system controller of the automation system. The control unit is further configured to establish a Transmission Control Protocol (TCP) connection to the system controller via the data interface according to the TCP, and to receive a request message (REQ message) for data of the actuator and / or sensor via the TCP connection according to the Hypertext Transfer Protocol (HTTP), and to send a response message (RES message) for the data to the system controller.

[0010] Embodiments of the field device can be integrated in an automation system by means of the REQ and RES messages for data according to the HTTP, preferably without the need for a field device-specific driver for the system controller of the automation system and / or without the need for a field device-specific configuration of the system controller of the automation system.

[0011] Embodiments of the field device can communicate with the system controller of the automation system by means of the REQ and RES messages according to the HTTP, without the need for a field device-specific driver and / or a field device-specific configuration. Preferably, the control unit of the field device is configured to receive data in the REQ message, output to the actuator via the data connection, and send an acknowledgement of the data output and / or an acknowledgement feedback (e.g. a movement) of a response of the actuator to the output in the RES message. Alternatively or additionally, the control unit of the field device is configured to receive an instruction for detecting data in the REQ message, detect data from the sensor via the data connection, and send the detected data to the control system in the RES message.

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

[0013] The field device can also be referred to as a field device. The field device can be an industrial electronic.

[0014] The field device can be built-in in a production or process plant. The field device can comprise an actuator (such as an actuating element, a valve, etc.) and / or a sensor (such as a measuring transducer), which are preferably located in the production or process plant.

[0015] The control unit can be built to establish a TCP connection with the system controller via the data interface according to TCP, wherein the control unit is built to receive a synchronization packet (SYN-Paket) from the system controller via the data interface according to TCP and to send an acknowledgement (SYN-ACK) of the reception of the SYN-Paket to the system controller, thereby establishing the TCP connection with the system controller.

[0016] The control unit, which has a data connection to the actuator and / or the sensor, can be built to process data (e.g. detected or output or to be output) of the actuator and / or the sensor. Alternatively or additionally, the control unit can be built to receive data (e.g. detected or output or to be output) of the actuator and / or the sensor in a data packet from the system controller and / or to send (i.e. transmit) it in a data packet to the system controller.

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

[0018] The system controller can be a control center of the automation system or a 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 (e.g. local) application. The application can be built to plan and / or operate a power generation unit and / or a power consumption unit. The field device can be part of such a power generation unit or power consumption unit.

[0019] The automation system can be a production plant or a process plant.

[0020] Embodiments of the field device can flexibly provide data to the system controller with HTTP as language by means of the control unit as a server (in particular a REST server). Thereby, the adjustment or development of a client for the system controller to receive or (e.g. asynchronously) record data is simplified. Alternatively or additionally, the control unit can provide an (e.g. "REpresentational State Transfer" or REST compliant) interface to the system controller by means of messages according to HTTP over a TCP connection.

[0021] The above or further embodiments of the field device enable an adaptation or development of a client for a system controller of an automation system in order to receive or record (e.g. asynchronously) data before the field device is integrated in the automation system or connected with the system controller of the automation system via a data interface, preferably before the field device for the automation system is purchased. The adaptation or development of the client for the system controller can be started or carried out, for example, by accessing a corresponding control unit (e.g. of the manufacturer of the field device) via a TCP connection. Subsequently, an adaptation of an internet protocol address (IP address) of the field device in the client is sufficient for the integration of the field device.

[0022] The REQ message can comprise a request for data. The RES message can comprise the requested data.

[0023] The REQ message can give a time period. The RES message can comprise data detected by or output to the actuator and / or sensor within the given time period.

[0024] The data can be assigned a timestamp. The timestamps can give the point in time of the detection and / or output of the data, respectively. The RES message can comprise, for example, certain data which are assigned a timestamp within the given time period. Alternatively or additionally, the RES message can comprise the timestamps assigned to the data.

[0025] The data can comprise, for example, a data sequence (e.g. a measurement sequence) and the system controller can record the data sequence. After a failure of the communication between the control unit and the system controller (e.g. after an exchange of data packets and / or a disruption of the TCP connection), the gaps in the recorded data sequence can be filled in a targeted manner or with minimal communication resources by means of the given time period.

[0026] The REQ message can give a plain text. The RES message can comprise data corresponding to the plain text.

[0027] The control unit can store the detected and / or output data. The control unit can be configured to check the detected or output or stored data by means of the plain text given in the REQ message. In the case that the data are assigned a keyword (e.g. a keyword) contained in the plain text, the data can correspond to the plain text given in the REQ message.

[0028] Alternatively or additionally, the data can be assigned a plain text which describes the data, respectively. The RES message can comprise, for example, the plain text assigned to the data.

[0029] These data can not only include raw data of actuators and / or sensors, but also include descriptions, such as of measurement points. Embodiments of the device enable a system controller to present a dashboard (also known in the art as: "Dashboard" or panel) based on communication with the control unit.

[0030] These data can be designed such that a field controller can be configured to evaluate and / or visualize and / or display these data, e.g. results of evaluations. These data can include, for example, measurement values and corresponding physical units for indicating pressure, flow (preferably flow rate) and / or temperature of a fluid. Alternatively or additionally, these data can include symbols for presenting measurement values or operating states, e.g. whether a valve is open or closed.

[0031] The plain text given in the REQ message and / or the plain text assigned to the data can include key words or text blocks for describing the data.

[0032] For example, the REQ message can include certain data whose plain text contains the plain text given in the REQ message, e.g. in full or at least one key word. Alternatively or additionally, the RES message can include the plain text assigned to the data.

[0033] These data can include at least two different data sequences. The assigned plain text can give the respective data sequence. Alternatively or additionally, these data can include at least two different measurement values. The assigned plain text can give the respective measurement value.

[0034] Optionally, the RES message can include an association to a previous RES message, wherein the previous RES message includes the plain text assigned to the data. It is not necessary to repeat the same plain text in different or successive RES messages, e.g. to more efficiently use communication resources.

[0035] The communication device can include at least two different actuators and / or sensors having a data connection to the control unit. The plain text assigned to the data can give the actuator and / or sensor used for detecting the data and / or output or to be output by the data.

[0036] The field device can be a measurement device (also known as: measuring instrument).

[0037] The plain text given by the REQ message and / or the plain text assigned to the data can comprise a description of the measurement point. Alternatively or additionally, the data can comprise at least one measurement value and the assigned plain text can give the physical unit of the at least one measurement value. Alternatively or additionally, the plain text can comprise an identification of the field device and / or of the actuator and / or of the sensor.

[0038] The data can comprise a measurement value detected by the sensor. Alternatively or additionally, the data can comprise a control instruction to be output to the actuator. Alternatively or additionally, the data can comprise an operating parameter detected by the actuator and / or the sensor and / or output to the actuator and / or the sensor. The control instruction and / or the operating parameter can determine an operating state of the actuator and / or the sensor.

[0039] The data can further comprise a timestamp. Alternatively or additionally, the timestamps can be assigned to one measurement value and / or control instruction and / or operating parameter, respectively. The assigned timestamp can give, for example, the point in time at which the measurement value was detected and / or the control instruction was output and / or the operating parameter was detected and / or output.

[0040] The measurement values can comprise a voltage and / or a frequency.

[0041] The RES message can comprise data in the form of an HTTP document. Alternatively or additionally, the RES message, like the HTTP document, can comprise data according to JavaScript Object Notation (JSON) or Extensible Markup Language (XML) or as Comma-Separated Values (CSV).

[0042] The data can be contained in the message body (also referred to as "Body" in the technical jargon) of the RES message. Alternatively or additionally, the header (also referred to as "Head" in the technical jargon) of the RES message can give the firmware version of the field device, preferably the firmware version of the firmware executed by the control unit, and / or comprise an association to the previous RES message.

[0043] The REQ message and / or the RES message by means of the TCP connection can be contained in an Internet Protocol packet (IP packet or IP packet for short).

[0044] The control unit can be a server by means of the TCP connection. The data communication of the control unit by means of the TCP connection comprising the REQ message and the RES message can be simulated by a server located outside the automation system.

[0045] The control unit can further be configured to establish a TCP connection with a server located outside the automation system via the data interface and to receive a message according to HTTP via the TCP connection with the server. The message from the server can comprise a configuration of the field device. The server can be configured to select the configuration via the internet, e.g. as a web service. The server can be identical or different from the server emulating the data communication with the control unit.

[0046] The control unit can further be configured to establish a TCP connection with a server located outside the automation system via the data interface and to send a message according to HTTP via the TCP connection with the server. The message can give an operating state or a fault state of the field device. The server can be identical or different from the server emulating the data communication with the control unit and / or the server sending the configuration of the field device.

[0047] According to a second aspect, a method of integrating a field device in an automation system is provided. The field device can be a field device according to the first aspect. The method comprises the step of setting up (e.g. adjusting and / or developing and / or testing) an application interface of a system controller of the automation system for communication with a data interface of the field device. The application interface is configured to send a REQ message and to receive a RES message in data packets via a TCP connection. The data packets comprise an address field of the field device or of the data interface of the field device. During the setup, the address field gives a first address pointing to a server located outside the automation system. The method further comprises the step of integrating the field device in the automation system by changing the address field in the data packets to a second address pointing to the field device or to the data interface of the field device located inside the automation system.

[0048] The server located outside the automation system (also referred to as external server) can comprise an entity or a replica of the control unit of the field device. During the setup step, the configuration of the system controller, preferably the application interface, can be set up (e.g. developed or adjusted or tested) for communication with the data interface of the field device via a TCP connection, preferably without the need to acquire a copy of the field device.

[0049] The entity or the replica of the control unit of the field device can also be referred to as a digital twin of the field device. During the step of setting up the application interface for communication of the REQ and RES messages, the entity or the replica of the control unit of the field device can be reached via the first address.

[0050] The first address can be a network address of the external server. Alternatively or additionally, the second address can be a network address of a field device installed and / or connected in the automation system, e.g. an address of a data interface of the field device. The first address and the second address can be IP addresses, e.g. according to IPv4 or IPv6.

[0051] The first address and the second address can differ. The first address and the second address can differ (preferably at least) in one segment of the address field. The segment can give different subnets, e.g. according to a subnet mask or a prefix length of the segment. A subnet given by the first address can correspond to a subnet comprising the external server. A subnet given by the second address can correspond to a subnet comprising the automation system and / or the system controller.

[0052] Changing the address field for the data interface of the field device can comprise changing a destination address in the data packet, e.g. in a data packet of the REQ message, and / or a sender address in the data packet, e.g. in a data packet of the REQ message.

[0053] According to a third aspect, a system controller of an automation system is provided herein. The system controller can be configured to implement the method according to the second aspect. Alternatively or additionally, the system controller can comprise an application interface. The application interface of the system controller can be configured to communicate with the data interface of the field device according to the first aspect. Alternatively or additionally, the application interface of the system controller can be configured to transmit a REQ message according to the Hypertext Transfer Protocol (HTTP), preferably a REQ message according to the first or second aspect, preferably in a data packet of a TCP connection, and to receive a RES message according to the HTTP, preferably a RES message according to the first or second aspect.

[0054] In each aspect, the address field in the data packet, e.g. for a network address of the field device or a data interface of the field device, is optionally:

[0055] - giving a first address or pointing to a server located outside the automation system, preferably for setting up the application interface of the system controller, and

[0056] - giving a second address or pointing to a field device located inside the automation system, preferably for integrating the field device.

[0057] The method according to the second aspect and / or the system controller according to the third aspect can comprise any step and / or any feature disclosed in connection with the first aspect or a corresponding step or a corresponding feature. BRIEF DESCRIPTION OF DRAWINGS

[0058] The present invention will now be described in detail with reference to the accompanying drawings and preferred embodiments.

[0059] in:

[0060] Figure 1 A schematic block diagram of an automated system having the field devices of the first embodiment;

[0061] Figure 2 This is a schematic communication diagram for integrating field devices into an automation system in the second embodiment; and

[0062] Figure 3 A schematic flowchart illustrating a method for integrating field devices into an automation system. Detailed Implementation

[0063] Figure 1 The schematic block diagram of an illustrative automation system 100 shows a first embodiment with a field device generally indicated by reference numeral 110. The field device 110 may be an industrial electronic device, such as a measuring instrument.

[0064] The automation system 100 includes at least one embodiment of a field device 110, which is read (e.g., monitored) and / or controlled (e.g., regulated) by the system controller 120 of the automation system 100. Figure 1 The diagram shows a system controller 120, while in the automation system 100, multiple system controllers 120 for reading and / or controlling field devices 110 may be redundantly or hierarchically constructed.

[0065] Field device 110 Figure 1 The first embodiment shown includes an actuator 112 and / or a sensor 112, and a control unit 116 connected to the actuator 112 and / or sensor 112 via a data connection 114. The control unit 116 is configured to detect and / or output data from the actuator 112 and / or sensor 112 via the data connection 114. The field device 110 also includes a data interface 118 configured to exchange data packets between the control unit 116 and the system controller 120 of the automation system 100.

[0066] Data interface 118 may include a network interface. Data interface 118 may, for example, be configured to communicate via local line network 102. Local line network 102 may include one or more conductor pairs for symmetrical signal transmission. Alternatively or supplementarily, local line network 102 may include at least one network switch (also known in technical terms as a tap switch) that connects different branches of the conductor pairs together to exchange data packets. Local line network 102 may include Ethernet and / or Real-time Ethernet and / or Single-Pair Ethernet (SPE), preferably according to the standard IEEE 802.3 in a series of standards.

[0067] As an alternative or supplementary solution, data interface 118 can be configured to communicate via wireless local area network 104, such as 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 the 3rd Generation Partnership Project (3GPP) radio access technology, preferably according to fifth generation radio access technology (also known in technical terms as Fifth Generation New Radio or 5G NR). For this purpose, data interface 118 may include a baseband chip configured to send or receive data packets according to the radio access technology using a protocol stack. Data interface 118 can, for example, be configured to communicate with extremely reliable and low latency (technical term: Ultra-Reliable Low-Latency Communication or URLLC) according to standard documents 3GPP TR 38.824V16.0.0 and / or standard document 3GPP TR 33.825V16.0.1.

[0068] Line network 102 and / or radio network 104 can form a subnet of automated equipment 100 (such as a campus network). Integrated field devices 110 and system controller 120 are connected in the same subnet.

[0069] The control unit 116 is also configured to establish a TCP connection with the system controller 120 via the data interface 118 according to the Transmission Control Protocol (TCP), and to receive request messages (REQ messages) about data of actuators and / or sensors via the TCP connection according to the Hypertext Transfer Protocol (HTTP), and to send response messages (RES messages) about the data to the system controller 120.

[0070] In the first variant of each embodiment, for example in Figure 1 In the illustrated variants, the control unit 116 and data interface 118 are arranged externally to the sensor 112 or actuator 112. In a second variant of each embodiment, the control unit 116 and / or data interface 118 are integrated into the sensor 112 and / or actuator 112. In a third variant of each embodiment, multiple sensors 112 and / or actuators 112 are connected to the control unit 116 via data connection 114.

[0071] To integrate field devices 110 (such as industrial electronic devices) into automation system 100, data exchange (i.e., communication) is established within automation system 100 after the physical installation of field devices 110 is completed. This integration can be monitored or implemented by, for example, the R&D personnel of a system integrator.

[0072] The commissioning of the field device 110 can be preceded by a test run of the field device 110. The test run of the field device 110, e.g. an industrial electronic, can comprise operating the field device 110 before final commissioning, e.g. before physically installing and / or connecting the field device 110 and / or before setting up the field device 110 for detecting data with the sensor 112 and / or outputting data to the data interface 118. The field device 110 is prepared for being commissioned in the automation system 100 by the test run.

[0073] The automation system 100, e.g. the system controller 120, can be a system superimposed on the field device 110. Alternatively or additionally, the system controller 120 can be a programmable logic controller (PLC) and / or a virtual machine. Alternatively or additionally, the system controller 120 can comprise and / or implement a local application and / or the system controller 120 can comprise and / or implement a development environment for the application interface 122, e.g. an API.

[0074] The development environment can e.g. be a tool which tests the communication with the data interface 118 of the external server 200 or a data interface functionally identical to the data interface 118 and / or which outputs code snippets for communicating with the data interface 118. The code snippets can be applied in the local application of the system controller 120.

[0075] The local application can comprise controlling, preferably regulating, the field device 110 interconnected with the system controller 120 via the application interface 122.

[0076] In the commissioning phase of the field device 110, e.g. an industrial electronic, the communication of the field device 110, e.g. as a server of a TCP connection, with the system controller 120, e.g. as a client of a TCP connection, is established and / or the system controller 120, e.g. a PLC or a local application, is built to process data and / or to perform plausibility checks on data and / or to write plausibly data to a database, e.g. a database of the automation system 100 or an external database outside the automation system 100.

[0077] Conventional field devices comprise e.g. Modbus servers. Conventionally, a driver for the communication between the conventional field device and the system controller has to be developed at the time of commissioning. In this process, the developer studies the documentation of the Modbus server and classifies the values required for the application. The driver is then implemented in the programming environment. Usually, a copy of the conventional field device is first purchased as a sample device, which is then made to run on the desk or in the network of the automation system, and the development of the driver is started.

[0078] The first embodiment of the field device 110 comprises a control unit 116 which is able to establish a TCP connection with the system controller 120 without a field device specific driver and to exchange messages (e.g. instructions regarding the data or the data itself) regarding the data according to HTTP.

[0079] The RES message can be closed (also called "self-contained" in the jargon) for example. The RES message can comprise additional information besides the data. The additional information can describe the data (preferably as plain text or text block) and / or comprise a configuration of the system controller 120 for processing or outputting the data.

[0080] In each embodiment, the system controller 120 can also be interconnected (i.e. connected for exchanging data packets) with an external server 200 external to the automation system 100. The attribute "external" can be synonymous with "located externally". The external server 200 can be located externally to the automation system 100 in case a router 202 is arranged between the system controller 120 and the external server 200 for transmitting exchanged data packets between the system controller 120 and the external server 200.

[0081] The external server 200 can provide functionalities of the control unit 116 which are provided by the control unit 116 of the field device 110 via the data interface 118.

[0082] The functionalities of the control unit 116 are provided by the external server 200 so that the integrability 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 a copy of the field device 110 is procured. Alternatively or additionally, the integration of the field device 110 can be prepared by exchanging messages according to HTTP, preferably before a copy of the field device 110 is procured.

[0083] Figure 2 Schematic communication diagram for the integration of the field device 110 in the automation system 100 in the second embodiment. The interaction of the field device 110, the system controller 120 and the external server 200 according to the second embodiment is described in the following for the sake of clarity and conciseness, but the present disclosure is not premised on such a total system. Rather, the functional features disclosed with respect to the interaction are disclosed with respect to the field device 110, the system controller 120 and the external server 200, respectively.

[0084] Furthermore, the field device 110, the system controller 120 and the external server 200 in the second embodiment can be improvements of the field device 110, the system controller 120 and the external server 200 in the first embodiment, respectively.

[0085] The control unit 116 can act as a server, for example with respect to TCP connections and / or messages according to HTTP. Based on this feature of the field device 110, the second embodiment of the field device 110 provides a digital twin of the field device 110 outside the automation system, i.e. by means of the external server 200.

[0086] The communication properties of the external server 200 are identical to the communication properties of the field device 110 via the data interface 118. Thus, the external server 200 can be referred to as a digital twin of the field device 110 or the control unit 116.

[0087] The control unit 116 of the field device 110 comprises, for example, a memory and at least one processor which executes instructions encoded in the memory of the field device 110, wherein a control module with encoded instructions is stored in the memory of the field device 110. By execution of the control module, the control unit 116 is able to output data to the actuator 112 via the data connection 114 and / or to send data from the data packets detected by the sensor 112 via the data connection 114, for example based on data packets received on the data interface 118.

[0088] The external server 200 comprises, for example, a memory and a processor which executes instructions encoded in the memory of the external server 200, wherein the same control module as stored in the memory of the field device 110 is stored in the memory of the external server 200.

[0089] Preferably, the external server 200 is available via the Internet. The external server 200 is configured, for example based on the control module, to receive at least one message 130, for example a REQ message 130, which corresponds to a future REQ message 140 to be sent to the field device 110, from the system controller 120. The external server 200 is further configured, for example based on the control module, to provide a message 132, for example a response, preferably a RES message 132, which corresponds to a future RES message 142 originating from the field device 110, via the Internet, preferably to the system controller 120, as a response to the received message 130.

[0090] With the help of the external server 200, the application interface 122 of the system controller 120 can be set up for the field device 110, preferably without having a copy of the field device 110. For example, a developer can program the system controller 120 as its client to the external server 200 on the Internet (as a digital twin). In this way, the developer can prepare or implement the integration of the field device 110 in the automation system 100 without having to have a sample device of the field device 110 (e.g. an industrial electronic) on site.

[0091] Alternatively or additionally, the developer can start the evaluation of the field device 110 (e.g. an industrial electronic) without having a sample device of the field device 110 on site.

[0092] Each REQ and RES message according to HTTP can be contained (preferably respectively) in a data packet (e.g. IP packet). The respective data packet comprises an address field for the sender address (also called "Source address" in the professional terminology) and an address field for the target address (also called "destination address" in the professional terminology).

[0093] The address field of the sender address of the REQ message 130 can point to the system controller 120, i.e. comprise the address 121 of the system controller 120, for example. The address field of the target address of the REQ message 130 can point to the external server 200, i.e. comprise the address 201 (also called: first address) of the external server 200.

[0094] The address field of the target address of the RES message 132 can point to the system controller 120, i.e. comprise the address 121 of the system controller 120, for example. The address field of the sender target address of the RES message 132 can point to the external server 200, i.e. comprise the address 201 (also called: first address) of the external server 200.

[0095] Compared to the conventional procurement of samples, the integration or integration suitability evaluation process (e.g. prototype evaluation process) for the field device 110 is simplified, time-saving and less risky with the help of the external server 200.

[0096] With the help of the external server 200 to set up the application interface 122 of the system controller 120, the field device 110 can be integrated in the automation system 100 by replacing the first address with the address of the field device 110.

[0097] The address field of the sender address of the REQ message 140 can point to the system controller 120, i.e. comprise the address 121 of the system controller 120, for example. The address field of the target address of the REQ message 140 can point to the field device 110, i.e. comprise the address 111 of the field device 110 (also referred to as: second address).

[0098] The address field of the target address of the RES message 142 can point to the system controller 120, i.e. comprise the address 121 of the system controller 120, for example. The address field of the sender address of the RES message 142 can point to the field device 110, i.e. comprise the address 111 of the field device 110 (also referred to as: second address).

[0099] This way, the integration can basically only comprise replacing the first address by the second address after the setup of the system controller 120 has been completed by means of the external server 200.

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

[0101] Figure 2 The second embodiment, which is combined with the communication diagram, can comprise a web server of the external server 200 for the integration of the system locally without the field device 110.

[0102] The control module implemented by the control unit 116 of the field device 110 and by the external server 200 can comprise the functionality of a REST server for the field device 110, such as a complex measuring instrument, for example.

[0103] Alternatively or additionally, the control module implemented by the control unit 116 of the field device 110 can comprise the functionality of a REST server for the field device 110, such as for a complex measuring instrument. Based on the control module or the REST server of the field device 110, a REST server 200 in the Internet can be developed, which technically provides the same responses as the REST server of the field device 110. A virtual and digitalized mirror image of the field device 110 is thus realized in terms of communication via the data interface 118.

[0104] This way, in the step of setting up the system controller 120, preferably the application interface 122, a developer can develop a client, which works when communicating with the REST server 200 in the Internet.

[0105] In the step of integrating the field device, the second address can be changed to the first address, for example by changing the network parameters of the client. The integration 304 of the field device 110 is thus significantly accelerated compared to conventional approaches.

[0106] In addition, a technical solution for integrating the field device 110 in the automation system 100 (short: system integration), for example the data interface 118 for exchanging HTTP messages over a TCP connection, can also be applied for configuring the field device 110. The field device 110, for example an industrial electronic, is configured by guiding the user in the Internet via a web-based service of the external server 200 (or another external server) for personal configuration of the field device 110. Guiding via the web service increases the comfort and shortens the configuration time of the field device 110.

[0107] Alternatively or additionally, a technical solution for system integration, for example the data interface 118 for exchanging HTTP messages over a TCP connection, can also be applied for supporting and / or monitoring and / or remote maintenance of the field device 110. The control unit 116 can be configured, for example, to transmit the 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, for example an industrial electronic, can be supported by guiding the user in the Internet via a web-based service of the external server 200 (or another external server) for preliminary diagnosis. Guiding via the web service increases the satisfaction of the after-sales service process or enables an early elimination of a fault status, thus avoiding or shortening the downtime of the automation system 100.

[0108] Figure 3 Fig. 3 shows a schematic flow chart of a method 300 for integrating a field device 110 in an automation system 100 according to a third embodiment. The field device 110, which is integrated or to be integrated, can be configured according to the first and / or second embodiment.

[0109] In step 302, an application interface 122 of a system controller 120 of the automation system 100 is set up for communication with a data interface 118 of the field device 110. The application interface 122 is set up to transmit REQ messages and to receive RES messages in data packets over a TCP connection, wherein the data packets comprise an address field for the data interface of the field device 110 giving a first address 201 pointing to a server 200 located outside the automation system 100 during the setup 302. The method 300 further comprises a step 304 of integrating the field device 110 in the automation system 100 by changing the address field in the data packets to a second address 111 pointing to the data interface of the field device 110 located inside the automation system 100.

[0110] As described in connection with the preceding embodiments, embodiments of the field device 110 and the method 300 can enable to set up or verify the communication with the system controller 120 before procuring a copy of the field device 110, in particular in that the system controller 120 first communicates with the external server 200. This communication of the system controller 120 with the external server 200 can be identical or indistinguishable or equivalent to the future communication of the system controller 120 with the field device 110, in general except for the address 111 of the field device 110 in the address field. The integration of the field device 110 can in general comprise adapting the address in the address field of the data packet from the address 201 of the external server 200 to the address 111 of the field device 110 in the automation system 100.

[0111] In this way, a user of the system controller 120, e.g. a developer of a local application, can judge whether and / or how to integrate the field device 110 in the automation system 100. For example, the user can prepare or support the decision to procure the first copy of the field device 110 as a recommender or advisor before procuring the first copy of the field device 110. Thereby, compared to conventional approaches, time and resources for shipping and, if necessary, returning samples are avoided.

[0112] For example, the developer can evaluate whether the field device is suitable for integration and / or future procurement and / or bulk investment.

[0113] The control unit 116 of one embodiment of the field device 110 is configured to communicate according to HTTP over a TCP connection, so that the (renewal, adaptation, development or verification) of the (preferably future) data communication between the system controller 120 and the field device 110 can be set up by the equivalent data communication between the system controller 120 and the external server 200. From the perspective of the system controller 120, the establishment of the TCP connection and / or the sending of the REQ message and / or the receiving of the RES message when communicating with the external server 200 can be equivalent or implemented as when communicating with the field device 110 integrated in the automation system 100, e.g. even if the TCP connection for the data communication with the external server 200 is routed out of the subnet of the automation system. Thereby, embodiments of the field device 110 or the method 300 of integrating the field device 110 substantially simplify the preparation of the decision to integrate and / or the implementation of the integration of the field device 110 for a user, e.g. a developer.

[0114] The application has been described above with reference to exemplary embodiments, but it will be apparent to a person skilled in the art that various modifications are possible and equivalents can be used instead. Furthermore, a number of modifications can be made to adapt the application to specific circumstances or specific sensors or specific actuators to the principles of the application. The application is therefore not limited to the disclosed embodiments, but includes all embodiments falling within the scope of the appended claims.

[0115] Legend of the drawing

[0116] Automation system 100

[0117] Local line network, preferably 4-wire Ethernet or Single Pair Ethernet (SPE) 102

[0118] Wireless local area network, preferably according to the 5th Generation of Wireless Access Technology 104

[0119] Field device, also called field instrument (FG), preferably an industrial electronic or a measuring instrument 110

[0120] Network address of the field device, preferably an IP address 111

[0121] Actuator and / or sensor of the field device 112

[0122] Data connection between the control unit and the actuator and / or sensor 114

[0123] Control unit of the field device 116

[0124] Data interface between the field device and the system controller 118

[0125] System controller of the automation system 120

[0126] Network address of the system controller, preferably an IP address 121

[0127] Application interface of the system controller 122

[0128] REQ message at setup 130

[0129] RES message at setup 132

[0130] Integrated REQ message 140

[0131] Integrated RES message 142

[0132] External server located outside the automation system 200

[0133] Network address of the external server, preferably an IP address 201

[0134] Gateway router 202 between automation system and external server

[0135] Method 300 of integrating field devices

[0136] Step 302 of setting up application interface

[0137] Step 304 of integrating field devices

Claims

1. A method (300) of integrating a field device (110) in an automation system (100), comprising: - setting up an application interface (122) of a system controller (120) of the automation system (100) for communication with a data interface (118) of the field device (110), wherein the application interface (122) is set up to send a request message, REQ message, and to receive a response message, RES message, in data packets over a TCP connection, wherein during the setup the data packets comprise an address field for the data interface (118) of the field device (110), which address field gives a first address (201) pointing to a server (200) located outside the automation system (100), wherein the setup comprises testing the communication with a data interface of the external server (200) that is functionally identical to the data interface (118); and - integrating the field device (110) in the automation system (100) by changing the address field in the data packets to a second address (111) pointing to the data interface (118) of the field device (110) located inside the automation system (100), wherein the first address (201) is replaced by the second address (111) by changing network parameters of a client of the system controller (120).

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

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

4. The method (300) of claim 2, wherein the REQ message gives a time period and the RES message comprises data detected by the actuator and / or sensor (112) or data output to the actuator and / or sensor (112) within the given time period.

5. The method (300) according to claim 2, wherein the data are assigned a time stamp, which gives a point in time of detection and / or output of the data, respectively.

6. The method (300) according to claim 2, wherein the REQ message gives plain text and the RES message comprises data corresponding to the plain text.

7. The method (300) of claim 6, wherein the data is assigned a plain text that respectively describes the data, wherein, The RES message comprises plain text assigned to the data.

8. The method (300) according to claim 2, wherein the field device (110) comprises at least two different actuators and / or sensors (112) having a data connection to the control unit (116), and the plain text assigned to the data gives the actuator and / or sensor (112) used to detect the data and / or output or to be output by the data.

9. The method (300) of claim 7, wherein the plain text given with the REQ message and / or the plain text assigned to the data comprises a description of a measurement point, and / or wherein the data comprises at least one measurement value and the assigned plain text gives the physical unit of the at least one measurement value, and / or wherein The plain text comprises an identification of the field device (110) and / or the actuator and / or the sensor (112).

10. The method (300) according to claim 2, wherein the data comprise: - a measured value detected by the sensor; and / or - a control command sent to the actuator; and / or - an operating parameter detected by the actuator and / or sensor (112) and / or output to the actuator and / or sensor (112), which determines an operating state of the actuator and / or sensor (112).

11. The method (300) according to claim 1, wherein the RES message comprises data in a HTTP document according to JavaScript Object Notation, JSON, or Extensible Markup Language, XML, or as Comma-Separated Value, CSV.

12. The method (300) according to claim 1, wherein the REQ message and the RES message are contained in an Internet Protocol packet, IP packet, via the TCP connection.

13. The method (300) according to claim 2, wherein the control unit (116) is a server of the TCP connection, and wherein the control unit (116) is emulated by a server (200) located outside the automation system (100) via data communication of the TCP connection comprising the REQ message and the RES message.

14. The method (300) according to claim 2, wherein the control unit (116) is further configured to establish a TCP connection via the data interface (118) with a server (200) located outside the automation system (100) and to receive messages according to HTTP via the TCP connection with the server (200), wherein the messages originating from the server (200) comprise a configuration of the field device (110).

15. The method (300) according to claim 2, wherein the control unit (116) is further built to establish a TCP connection with a server (200) located outside the automation system (100) via the data interface (118) and to send a message according to HTTP via the TCP connection with the server (200), wherein the message gives an operating state or a fault state of the field device (110).

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

Images