Hardware-software communication system for sensor signal monitoring in process automation technology

Abstract

Hardware-software communication system (1) for sensor signal monitoring in process automation technology, comprising: at least one client (10), one system layer (12) and one application layer (14) ◯ where the client (10) and the system layer (12) are connected via communication technology and are set up to communicate with each other, ◯ where the system layer (12) and the application layer (14) are interconnected and configured to communicate with each other independently of the client (10), where the system layer (12) is implemented as a server, wherein the system layer (12) and the application layer (14) are suitable to be configured as software version (24, 26) and the hardware-software communication system (1) comprises at least a first software version (24) and a second software version (26) and a routing component (28), wherein the routing component (28) is suitable to connect the first version (24) and / or the second version (26) to the client (10), wherein the first software version (24) and the second software version (26) are structured like a web service (4) and the routing component (28) is a load balancer for HTTP or HTTPS.

Description

[0001] The invention relates to a hardware-software communication system for sensor signal monitoring in process automation technology.

[0002] In process automation technology, sensors are used to monitor and control processes. These sensors send the measurement signals to a transmitter, which processes the signals and displays them directly on the transmitter or forwards them to a central data processing unit.

[0003] Transmitters consist of hardware and software. The usability and operation of a transmitter are now largely determined by the software.

[0004] A web interface is known from US Patent 6,732,191 B1. A system and method for space-optimized storage and generation of web pages are known from US Patent 2002 / 0169,804 A1. A method and device for remote control of processes using applets are known from US Patent 6,799,195 B1. An adaptable converter interface is known from US Patent 2002 / 0147,936 A1. A method and system for managing network resources are known from WO 2008 / 155,597 A1. A method and device for control using control devices that provide a virtual machine environment and communicate over an IP network are known from US Patent 6,788,980 B1.

[0005] The disadvantage of today's transmitters is that the transmitter software is tied to the specific transmitter and cannot be operated independently. This implies several drawbacks. For example, specific transmitter software must be developed for each transmitter. Furthermore, when the transmitter software of one transmitter model is updated, each transmitter of that model must be updated separately.

[0006] Therefore, one of the aims of the invention is to make the transmitter software flexible and cost-effective for different transmitter models.

[0007] This problem is solved according to the invention by the features of claim 1.

[0008] The hardware-software communication system according to the invention for sensor signal monitoring in process automation technology comprises at least one client, a system layer, and an application layer. The client and the system layer are connected and configured to communicate with each other. The system layer and the application layer are connected and configured to communicate with each other independently of the client. The system layer is implemented as a server. wherein the system layer and the application layer are suitable to be designed as a software version and the hardware-software communication system comprises at least a first software version and a second software version and a routing component, wherein the routing component is suitable to connect the first version and / or the second version to the client, where the first software version and the second software version are structured like a web service and the routing component is a load balancer for HTTP or HTTPS.

[0009] The hardware-software communication system according to the invention makes it possible to operate transmitter software on a system external to the transmitter, so that simpler, less powerful and cheaper transmitter hardware can be used for the transmitter itself.

[0010] A further advantage is that the hardware-software communication system according to the invention allows the transmitter software for a large number of transmitter hardware to be updated simultaneously, thus eliminating the need to update each transmitter separately. The hardware-software communication system according to the invention also enables remote control and remote diagnostics of the transmitters. Furthermore, the hardware-software communication system according to the invention allows connection to control systems and, for example, office computers.

[0011] According to one embodiment of the invention, the client and the system layer are configured to communicate via a network protocol.

[0012] According to one embodiment of the invention, the server is designed as a web service and the network protocol is HTTP or HTTPS.

[0013] According to one embodiment of the invention, the client comprises a transmitter as a thin client and / or a control system and / or remote access via a web browser.

[0014] According to one embodiment of the invention, the hardware-software communication system comprises at least two clients and the routing component is suitable for first connecting both clients to the first version and then connecting at least one client only to the second version.

[0015] According to one embodiment of the invention, the client includes remote access via a web browser and the web browser is suitable for displaying a web page with a simulated transmitter.

[0016] The invention is explained in more detail with reference to the following description of figures. The figures show: - Fig. 1: a schematic outline of the hardware-software communication system according to the invention, - Fig. 2: an embodiment of the hardware-software communication system made up of Fig. 1, - Fig. 3: a detailed section of another embodiment of the hardware-software communication system, - Fig. 4: a detailed section of an additional embodiment of the hardware-software communication system and - Fig. 5: a detailed section of an additional embodiment of the hardware-software communication system.

[0017] Fig. Figure 1 shows a schematic structure of the hardware-software communication system 1 according to the invention. The hardware-software communication system 1 comprises at least one client 10, a system layer 12 and an application layer 14.

[0018] Client 10 and system layer 12 are connected via communication technology and configured to communicate with each other. Client 10 will be discussed in more detail later.

[0019] System layer 12 is an implementation tailored to a specific hardware / software environment, on which application layer 14 is used, resulting in Fig. Figure 1 shows that application layer 14 is enclosed by system layer 12. Application layer 14 is configured to interact with system layer 12.

[0020] A hardware / software environment is the hardware and software on which application layer 14 and system layer 12 are executed. Examples of a hardware / software environment include a Windows PC, an embedded system with a minimal operating system, or a cloud server.

[0021] Application layer 14 is implemented in such a way that it is independent of the specific hardware / software environment. However, all concrete implementations of system layer 12 offer a uniform interface 13 to application layer 14. System layer 12 and application layer 14 are connected via this uniform interface 13 and are configured to interact with each other independently of the client 10. This allows application layer 14 to be ported to new hardware / software environments without modification, if necessary. For example, there could be system layers 12 for different processors such as ARM or PowerPC, or different operating systems such as Linux or Windows.

[0022] Application layer 14 is hardware-independent. Application layer 14 includes, for example, menu navigation, diagnostic functionality, and data processing for pH measurements, conductivity measurements, and other parameters. Application layer 14 also includes, for example, fieldbus connectivity and input / output interfaces (not shown).

[0023] For a concrete implementation of application layer 14, finer divisions into applications and base system are also conceivable (not shown). The applications then contain, for example, the measurement data processing, diagnostic functionality, and menu navigation, while the base system provides the fieldbus connection and input / output interfaces.

[0024] If system layer 12 is implemented as a server, the software becomes detachable from specific transmitters and can be experienced and used across the boundaries of the transmitter, thus enabling a wide variety of use cases. A server is software that provides the functionality of application view 14 to one or more clients 10, 10', ..., 10 n offers as a service.

[0025] Client 10 and system layer 12 communicate, for example, via a network protocol NP. This network protocol NP could be a Hypertext Transfer Protocol (HTTP) or a Hypertext Transfer Protocol Secure (HTTPS), which is transmitted over a Transmission Control Protocol / Internet Protocol (TCP / IP). Communication via HTTP or HTTPS is facilitated, for example, by a Representational State Transfer application programming interface (REST API). A system layer 12 implemented as a server that communicates via at least HTTP or HTTPS over TCP / IP is called a Web Service 4.

[0026] Fig. 2 and Fig. Figure 3 shows an embodiment in which system layer 12 is implemented as a web service 4. The web service 4 runs, for example, on a cloud server, meaning it is accessible via the internet. In this example, the cloud server is the hardware / software environment of the web service 4.

[0027] As in Fig. As shown in Figure 2, the hardware-software communication system 1 can also handle multiple clients 10, 10', ..., 10 n exhibit.

[0028] For multiple clients: 10, 10', ..., 10 n , as in Fig. As shown in 2, the web service 4 communicates individually with the respective client 10, 10', ..., 10 n .

[0029] Web service 4 communicates with one or more clients 10 via the network. The content of this communication includes, for example, display data, measured values, events (e.g., the main menu has been selected), or results of executed actions. Data transmitted from web service 4 to client 10 originates from application layer 14. Data transmitted from client 10 to web service 4 is then passed on to application layer 14.

[0030] Client 10 can, as in Fig. Figure 3 depicts a device configured as a so-called thin client 18. A thin client 18 has minimal processing power; for example, it comprises an input unit, a communication module, and a display. The input unit allows a user to enter information. The actual measurement processing takes place on the server. The communication module of the thin client 18 sends the input, such as raw data or menu navigation data, to a higher-level system, for example, a cloud server, which is implemented, for example, as a web service 4 server. The higher-level system is capable of sending a response, such as data to be displayed, to the thin client 18. The thin client 18 can display the received data on its screen. In one embodiment, the thin client 18 periodically queries the web service 4 for the current processing status and displays the measured values ​​on its screen.

[0031] If the measurement processing runs in a web service 4, remote access and remote diagnostics are also easily possible. In this case, the component for remote access is another client 10' which communicates with the web service 4. The client 10' for remote access is, for example, a web browser 22. Fig. Figure 3 shows the web browser 22, which is suitable for sending data for menu navigation and receiving data to be displayed.

[0032] As also in Fig. As shown in Figure 3, client 10 can also include a control system 20. The control system 20 is capable of sending commands to web service 4 and receiving measured values ​​from web service 4.

[0033] If the transmitter software runs in a Web Service 4 and the communication interfaces between Client 10 and Web Service 4 remain stable, then in this case, an update only requires updating the software in Web Service 4. This use case is described in Fig. 4 shown.

[0034] Fig. Figure 4 also shows that the hardware-software communication system 1 can have a routing component 28, a first software version 24, and a second software version 26. The routing component 28 handles the communication with clients 10, 10', ..., 10 n and forwards the requests to the first software version 24 or the second software version 26. The routing component 28 communicates via the network protocol NP.

[0035] The first software version 24 and the second software version 26 are each implementations of system layer 12 and application layer 14, respectively. The second software version 26, for example, is supplemented by additional functions compared to the first software version 26.

[0036] The first software version 24 and the second software version 26 are implemented, for example, as a web service 4. The routing component 28, for example, is based on a load balancer for HTTP or HTTPS, which handles requests from clients 10, 10', ..., 10 n receives and forwards to the first software version 24 or the second software version 26.

[0037] Should a software update for one or all clients take 10, 10', ..., 10 n To perform the update, the second software version 26 is first installed on the server hardware-software communication system 1. While the update is running, the routing component 28 continues to forward all communication to the first software version 24, as before. Once the second software version 26 is operational, the routing component 28 forwards all new communication to the second software version 26. As soon as no client 10, 10', ..., 10 nIf the first software version 24 no longer communicates, this software version can be removed from the hardware-software communication system 1.

[0038] However, scenarios are also conceivable in which several software versions are operated in parallel. If, for example, the communication interfaces or protocols change between two software versions, then the transmitters must also be updated. This can happen in stages: transmitters that have already been updated use the new second software version 26, while older transmitters communicate with the previous first software version 24. This gradual communication is also controlled by the routing component 28.

[0039] In the event that a client 10, 10', ..., 10 nDesigned as a web browser 22, the transmitter functionality, which essentially consists of software, can be experienced online. If the software of an existing transmitter is restructured into an application layer 14 and a system layer 12, and the system layer 12 is implemented via a web service 4, or if the transmitter software already has this structure, then customers can try out a transmitter in advance via a web browser 22 and do not need to have a physical product in hand first.

[0040] Fig.Figure 5 illustrates this embodiment. The software for a given transmitter product is installed as a web service 4 on a cloud server, for example, within a website or a company's online shop. The company website is structured so that an interactive interface resembling a transmitter is displayed in the user's web browser 22. This interface communicates with the web service 4 to, for example, inform the web service 4 about key presses, which the service then forwards to the transmitter software. Similarly, the web service 4 can also, for example, provide the web browser 22 with display content, which is then shown on the simulated display. Since the display and buttons are modeled after the real product, the software in the web service 4 behaves exactly like the software in the actual transmitter. Therefore, a user can get a preview of the actual product online.

[0041] Such an embodiment is also suitable, for example, for offering training on a specific device via a web browser. These can thus be implemented, for example, as an interactive online course.

Claims

[1] Hardware-software communication system (1) for sensor signal monitoring in process automation technology, comprising: at least one client (10), one system layer (12) and one application layer (14) ◯ where the client (10) and the system layer (12) are connected via communication technology and are set up to communicate with each other, ◯ where the system layer (12) and the application layer (14) are interconnected and configured to communicate with each other independently of the client (10), where the system layer (12) is implemented as a server, wherein the system layer (12) and the application layer (14) are suitable to be configured as software version (24, 26) and the hardware-software communication system (1) comprises at least a first software version (24) and a second software version (26) and a routing component (28), wherein the routing component (28) is suitable to connect the first version (24) and / or the second version (26) to the client (10), wherein the first software version (24) and the second software version (26) are structured like a web service (4) and the routing component (28) is a load balancer for HTTP or HTTPS. [2] Hardware-software communication system (1) according to claim 1, wherein the client (10) and the system layer (12) are configured to communicate via a network protocol (NP). [3] Hardware-software communication system (1) according to claim 2, wherein the server is designed as a web service (4) and the network protocol (NP) is HTTP or HTTPS. [4] Hardware-software communication system (1) according to one of the preceding claims, wherein the client (10) comprises a transmitter as a thin client (18) and / or a control system (20) and / or remote access via web browser (22). [5] Hardware-software communication system (1) according to any of the preceding claims, wherein the hardware-software communication system (1) comprises at least two clients (10, 10') and the routing component (28) is suitable for first connecting both clients (10, 10') to the first version (24) and then connecting at least one client (10, 10') only to the second version (26). [6] Hardware-software communication system (1) according to one of the preceding claims, wherein the client (10) comprises remote access via web browser (22) and the web browser (22) is suitable for displaying a web page with a simulated transmitter (30).

Images