PLC device with convenient cloud connection

Abstract

The present patent application discloses a PLC device with convenient cloud connectivity. The PLC device with convenient cloud connectivity according to the application is characterized in that the PLC device has an underlying operating system, wherein the PLC device comprises an integrated first OPC UA server and an application installed in the underlying operating system of the PLC device. The application is used to access the first OPC UA server running in the PLC device in order to obtain data from a first end device that is networked with the PLC device within a local network. The application is further used to access a second OPC UA server running in a gateway device within the same local network in order to obtain data from a second end device that is networked with the gateway device.The application will continue to be used to communicate with a cloud service device via the MQTT protocol and to upload data from the first and second end devices.

Description

Technical field

[0001] The present patent application relates to a PLC device with convenient cloud connectivity in industrial automation applications. State of the art

[0002] Programmable logic controllers (PLCs) are widely used in the Industrial Internet of Things (IIoT). For example, in an IoT environment, PLCs can act as gateways for production control, data acquisition, safety monitoring, and more. In PLC-based data acquisition and processing applications, the PLCs can collect and process data (such as temperature, pressure, and electrical current) from various sensors and devices. Furthermore, by connecting to a cloud platform or other system, PLCs enable real-time data monitoring, analysis, and prediction to optimize production processes and improve efficiency.

[0003] In industrial automation scenarios, PLC devices or other Internet of Things gateways can collect data from lower levels using the OPC UA protocol. In the OPC UA topology, a gateway device acts as an OPC UA server to provide various services, and other applications on the gateway device can call the services provided by the OPC UA server.

[0004] On the other hand, communication between PLC devices and cloud platforms or cloud devices is more internet-oriented and typically requires the use of internet protocols other than OPC UA to transmit data to the cloud. For example, PLC devices can enable communication between PLC devices and cloud platforms based on the MQTT (Message Queuing Telemetry Transport) protocol. Such MQTT-based cloud migration occurs via a local server, requiring the local deployment of hardware devices, including controllers such as PLCs, PCs, industrial computers, or the use of dedicated gateway modules. Another MQTT-based cloud migration approach involves the use of dedicated function blocks within the PLC devices.For example, one vendor's PLC product uses the LMQTT_CLIENT function block to implement MQTT cloud server parameters, thus enabling MQTT protocol communication with the cloud. Using MQTT clients via PLC function blocks is cumbersome and requires opening special programming software to create a corresponding project.

[0005] In the affected area, a new architectural solution is desirable that simplifies the process of migrating the data collected by PLC to the cloud and reduces the associated deployment costs. Disclosure of the invention

[0006] The present patent application describes a PLC device with convenient cloud connectivity. The PLC device employs an application to support enhanced cloud connectivity. This application accesses OPC UA servers in various gateways within a local network to receive data from various Internet of Things (IoT) devices and transmit it to a cloud server. The application can provide the user with a web interface for configuring the MQTT cloud server parameters. A cloud connectivity solution based on such a PLC device can therefore reduce the use of local hardware and decrease the software complexity.

[0007] In a first aspect of the application, a PLC device with convenient cloud connectivity is provided, characterized in that the PLC device has an underlying operating system, comprising an integrated first OPC UA server and an application installed in the underlying operating system of the PLC device. The application is used to access the first OPC UA server running in the PLC device to retrieve data from a first end device connected to the PLC device within a local network. The application is further used to access a second OPC UA server running in a gateway device within the same local network to retrieve data from a second end device connected to the gateway device.The application will continue to be used to communicate with a cloud service device via the MQTT protocol and to upload data from the first and second end devices.

[0008] In the PLC device solution described above with convenient cloud connection, an optional implementation is provided for the gateway device to be a programmable logic controller.

[0009] In the PLC device solution described above with convenient cloud connection, an optional implementation is provided for the operating system to be a Linux operating system.

[0010] In the PLC device solution described above with convenient cloud connectivity, an optional implementation is provided in which the first OPC UA server is integrated into a PLCnext firmware, and the application is located in a PLCnext extension component.

[0011] In the PLC device solution described above with convenient cloud connectivity, an optional implementation is provided for the application being used as a container in the Linux operating system.

[0012] In the PLC device solution described above with convenient cloud connectivity, an optional implementation is provided for the application to offer a web-based interface for configuring parameters.

[0013] In the PLC device solution described above with convenient cloud connectivity, an optional implementation allows the web page to be accessed from a computer or mobile device that has access to the local network.

[0014] In the PLC device solution described above with convenient cloud connection, an optional implementation is provided that the user is prompted to enter MQTT cloud server parameters on the parameter configuration interface.

[0015] In the PLC device solution described above with convenient cloud connectivity, an optional implementation is provided that the MQTT cloud server parameters include at least one of the following parameters: Broker Client Name, Broker URL, Broker Port, Broker Username, Broker Password, Broker Message Topic, Publisher Name, Default Send Interval, Broker Command Topic, Broker Command Response Topic, Broker Metadata Topic, Metadata Send Interval.

[0016] In the PLC device solution described above with convenient cloud connectivity, an optional implementation is provided that the user is prompted on the parameter configuration interface to configure parameters for a node of the OPC UA server. Short description of the characters

[0017] For better understanding, the drawings that form part of the patent application are shown. The drawings illustrate the embodiments of the patent application and, together with the description, explain the principle of the patent application. They show: Fig. 1 a schematic view of an extended cloud connection based on a PLC device according to an embodiment of the present application; Fig. 2 the architecture of a PLC device for the in Fig. 1 shown extended cloud connection; and Fig. 3A to 3D each show a screenshot of a website interface for configuration, which is accessed from a main device of the Fig. The extended cloud connection shown in section 1 is provided. Detailed descriptions

[0018] The following description presents the patent application by means of various embodiments. However, it should be clear to those skilled in the art that these embodiments can be implemented without one or more specific details or in conjunction with other substitutions and / or additional methods, materials, or components. In other cases, the known structures, materials, or operations are not shown or described in detail to avoid confusion regarding the aspects of the embodiments of the patent application. For explanatory purposes, certain figures, materials, and configurations are also mentioned to provide a comprehensive understanding of the embodiments of the patent application. However, the patent application can also be implemented without these detailed specifications.It should also be understood that the examples shown in the figures are illustrative and do not need to be shown to scale.

[0019] Below, various embodiments and variants of the present patent application are described in more detail in conjunction with the accompanying drawings.

[0020] Fig. Figure 1 shows a schematic view of an extended cloud connection based on a PLC device according to an embodiment of the present application. As in Fig. Figure 1 shows that several gateway devices (e.g., programmable logic controllers, PLCs) are used within a local network 50. For clarification, the following are shown in Figure 1: Fig. Figure 1 shows a first PLC device (10), a second PLC device (20), a third PLC device (30), and a cloud server (40), and it should be clear that the number here is only exemplary. It should also be understood that the first, second, and third PLC devices can each be connected, either wired or wirelessly, to some controlled or monitored Internet of Things end devices (e.g., sensors), with the graphical representation of these end devices in Figure 1. Fig. Number 1 was omitted.

[0021] The first PLC device 10, the second PLC device 20, and the third PLC device 30 can be essentially identical, e.g., all PLC devices have the features shown in Fig. The architecture shown in Figure 2 is used. However, in some implementations, only the first PLC device (10) needs to have the architecture and execution resources, as shown, for example, in Figure 2. Fig. The PLC devices shown in Figure 2 exhibit certain characteristics, while the other PLC devices may be structured differently from the first PLC device 10. It is sufficient that these PLC devices have an integrated OPC UA server function and communicate with the first PLC device 10 as described in Figure 2. Fig. The topological structure shown in 1 can be formed and transmit the data of the Internet of Things.

[0022] According to the embodiments of the present application, the first PLC device 10 includes an OPC UA server 120 in its integrated system components, the second PLC device 20 includes an OPC UA server 220 in its integrated system components, and the third PLC device 30 includes an OPC UA server 320 in its integrated system components. In other words, these OPC UA servers are present as integrated function modules in the PLC device platform and can thus be called up as needed. The PLC device with the integrated OPC UA server could, for example, be a PLCnext controller commercially available from PHOENIX CONTACT GMBH & CO. KG, Germany, or its affiliated companies. Of course, the invention need not be limited to a PLC device from this source.It should be noted that in this embodiment the OPC UA server is integrated into the firmware of PLCnext, but this does not represent a limitation for the PLC device used to implement the invention.

[0023] Furthermore, the first PLC device 10 can be equipped with an application 110 that enables the acquisition of OPC UA data between gateways and the migration of this data to the cloud via the MQTT protocol. This application 110 can be in the form of open-source software or software derived from the further development of open-source code. For example, it could be commercially available software from PHOENIX CONTACT GMBH & CO. KG, Germany, or its affiliated companies (e.g., named OPC UA OVER MQTT APP). The application 110 supports communication with the OPC UA server using the OPC UA protocol and communication with the cloud server 40 using the MQTT protocol.

[0024] In contrast to the OPC UA Server 120, which is integrated into the PLCnext firmware, Application 110 is deployed and operated as an extension component on PLCnext. Application 110 can provide a web-based access interface, allowing users to configure MQTT cloud server parameters via this webpage and also configure parameters for the OPC UA server nodes networked within the Internet of Things. This demonstrates Fig. 3D shows an example of a user interface for configuring cloud server parameters via web access (this is explained in more detail below).

[0025] With renewed reference to Fig. Figure 1 shows that each of the three PLC devices has an integrated OPC UA server, and that the three PLC devices are located within the same local network and are mutually addressable. This allows these PLC devices to exchange data using Application 110 and, if necessary, receive information about the Internet of Things (IoT) devices they have collected. Accordingly, in the topological structure of this application, the use of Application 110 is only required in the first PLC device 10. Application 110 can then utilize the properties of the OPC UA protocol to obtain data from various types of IoT devices that are associated with all OPC UA servers in the local network 50.

[0026] In a further, optional implementation, redundant devices can be configured in the network topology. Specifically, it is provided that an identical application 210 to application 110 can be used in the second PLC device 20 if the first PLC device 10 serves as the primary device for running application 110. This way, if the primary device fails, the redundant device, i.e., application 210 of the second PLC device 20, is activated and thus continues the task of collecting and uploading data from the Internet of Things devices to the cloud.

[0027] In a preferred implementation, the application 110 is deployed as a container (the name of a containerization tool supplied with Linux) in a Linux operating system. Fig. Figure 2 shows the architecture of a PLC device 80 for the in Fig. 1. Extended cloud connection shown. Such an architecture enables the deployment of Docker containers as a deployment environment for application 110.

[0028] In particular, this should be in Fig. The PLC device 80 shown primarily comprises underlying hardware 801. A Linux operating system 802, such as an RT-Linux system, can be used as the operating system. Compared to Windows, Linux is characterized by higher stability and efficiency, fewer bugs, faster patching, multitasking and multi-user capabilities, and a more secure policy for user and file privileges, enabling both development freedom and real-time program operation. Furthermore, the most important feature of the Linux system is that the underlying layer consists of files that can be securely accessed via SSH, SFTP, or similar methods, and that the configuration of file parameters can be directly modified, resulting in a more secure, flexible, and faster configurable system.

[0029] A middleware 803 can be implemented based on the Linux operating system 802. For example, in PLCnext from Phoenix Contact, the middleware 803 can include: GDS (Global Data Space), which ensures data consistency during exchange between different real-time components; and RSC (Remote Service Call), whereby a program running on an extension component 805 (this is explained in more detail below) can communicate with a core component 804 via an RSC interface.

[0030] Middleware 803 serves to link an operating system software (Linux operating system 802) and a user application software (core component 804, extension component 805).

[0031] The core component 804 can include I / O, a fieldbus component, a system component, a service component, and so on. I / O is used to process input and output data. The fieldbus can include a PROFINET controller, a PROFINET device, an Axioline-F master (local buses), and so forth. The system component provides all the basic functions of the underlying layer of the PLC device 80 and can include, depending on the application, a system manager, a PLC manager, an ESM (Execution Synchronization Manager), a user manager, IEC 61131 runtimes, and so forth, with some of these components being firmware components. The service component then provides access to system components such as the ESM, GDS, and so forth.

[0032] The OPC UA server 820 is usually also implemented in the core component 804, especially in the system component of the core component 804, so that the OPC UA server 820 can be accessed via the service component.

[0033] The 805 extension component further expands the functionality of the PLC device 80. An example of the 805 extension component is a Docker container 8050 running on a Linux system, within which the 810 application can be deployed. The 810 application within the 8050 Docker container can access the 820 OPC UA server and thus collect data from Internet of Things (IoT) devices via the 820 OPC UA server. Furthermore, the 810 application within the 8050 Docker container can migrate data to the cloud via the MQTT protocol, either independently or by calling other MQTT communication services within the 805 extension component.

[0034] With regard to Linux operation, the Docker container itself can be implemented using various well-known and mature technologies. Therefore, the implementation of Docker containers in itself does not constitute a limitation of the present application.

[0035] In the implementations described above, an Internet of Things (IoT) gateway is implemented based on a programmable logic controller (PLC). It should be understood that in other implementations, the IoT gateway may be an edge device based on a Linux system (e.g., an EPC1522 edge device, commercially available from PHOENIX CONTACT GMBH & CO. KG, Germany, or its affiliates), and that application 110 is deployed within the Linux system's Docker container.

[0036] Fig. Figures 3A to 3D each show a screenshot of a web interface for configuration, which is accessed by a main device (i.e., the first PLC device 10) of the Fig. The extended cloud connection shown in section 1 is provided. In a further implementation, it is used in conjunction with the Fig. Sections 3A to 3D describe the configuration of the parameters in the solution of the present application.

[0037] One aspect of the present application provides that the parameter configuration interface provided by Application 110 can be accessed using a device with a web browser, such as a mobile phone or computer. Therefore, no conventional programming software needs to be opened. The parameter configuration interface can be used in the form described in Fig. The diagrams shown in 3A to 3D are designed and presented to guide the user in a simple and clear way through the configuration of the OPC UA server nodes and the configuration of the connection parameters for the Cloud MQTT broker.

[0038] For example, the user can log in with an account and password for the first PLC device 10 or with a dedicated account and password on the in Fig. Log in to the OPC UA Server Connect page shown in section 3A. By using the interface on this page, you can configure the OPC UA server nodes, in particular selecting which nodes should be published (i.e., from which nodes the Internet of Things data should be collected and migrated to the cloud).

[0039] Furthermore, by clicking on the tab or in some other way, you can access the content in Fig. The page shown in 3B for the published nodes can be accessed to manage the published nodes of the OPC UA server, including importing, exporting, reloading, etc.

[0040] Furthermore, by clicking on the tab or otherwise, accessing the content in Fig. The 3C page shown for diagnostics can be accessed to view monitoring information about the connectivity of OPC UA server nodes and MQTT brokers, including statistics on the number of sessions, message queuing, etc., as well as visual graphs for some variables.

[0041] Furthermore, by clicking on the tab or otherwise accessing the content in Fig. The 3D-shown page for the configuration (Configuration) can be accessed, where the connection parameters for the Cloud MQTT broker can be configured, e.g. the following parameters can be set: • Broker Client Name • Broker URL • Broker Port • Broker Username • Broker Password • Broker Message Topic • Publisher Name • Default Send Interval • Broker Command Topic • Broker Command Response Topic • Broker Metadata Topic • Metadata Send Interval

[0042] It should be noted that these interfaces in Fig. Figures 3A to 3D represent only an example of the implementation of the interface for configuring parameters according to the solutions of the present application, and the arrangement of these interfaces and the specific graphic and textual content on these interfaces do not constitute a limitation of the present application.

[0043] Although the advantages of the Linux operating system are explained in the above description, the present invention does not preclude the implementation of an Internet of Things gateway or PLC device based on the Windows operating system and other operating systems.

[0044] Although the examples above are described as a network with three PLC devices, more or fewer PLC devices can also be used to build the corresponding Internet of Things.

[0045] In some variants, the PLC device can be replaced by another Internet of Things gateway, provided that the underlying operating system of this Internet of Things gateway allows the installation of an additional application and has OPC UA server services and MQTT network communication services that can be called by this application.

[0046] In some variants, the interface provided by application 110 for configuring parameters can be further simplified to meet practical requirements or include additional configuration options.

[0047] The present application also uses specific words to describe the embodiments of the application. The expressions "an embodiment," "an embodiment," and / or "some embodiments" represent a feature, structure, or special characteristic associated with at least one embodiment of the present application. Therefore, it should be emphasized and noted that "an embodiment," "an embodiment," and / or "an alternative embodiment" mentioned in different paragraphs of the description do not necessarily refer to the same embodiment or embodiment. Furthermore, some of the features, structures, or special characteristics of one or more embodiments of the present application may be appropriately combined.

[0048] As shown in the context of the present application, the terms "a" and / or "the" do not necessarily refer to the singular form, but may also include the plural form unless clearly indicated otherwise in the context. Generally, the terms "comprise" and "contain" only include the clearly specified steps and elements, which do not constitute an exclusive list, so that the process or apparatus may also include a further step or element.

[0049] It should also be noted that in the preceding description of the embodiments of the present application, various features are sometimes grouped together in one embodiment, one figure, or its description(s) in order to simplify the description of the disclosure of the present application and to facilitate the understanding of one or more embodiments of the invention. However, this disclosure does not mean that the features of the subject matter of the present application are greater than those mentioned in the claims. In fact, the features of the embodiments are fewer than all the features of any one of the individual embodiments disclosed above.

[0050] The basic concepts have been described above. Naturally, the above disclosure serves only as an example for the person skilled in the art, without limiting the application. Although not explicitly stated, a person skilled in the art may make various modifications, improvements, and changes to the application. These modifications, improvements, and changes are indicated in the application so that they are still within the spirit and scope of the embodiments presented in the application.

Claims

[1] PLC device with convenient cloud connection, characterized by , that the PLC device has an underlying operating system, wherein the PLC device comprises an integrated first OPC UA server (120) and an application (110) installed in the underlying operating system of the PLC device, wherein the application is used to access the first OPC UA server running in the PLC device to obtain data from a first terminal device that is networked with the PLC device within a local network, wherein the application is further used to access a second OPC UA server (220, 320) running in a gateway device (20, 30) within the same local network to obtain data from a second terminal device networked with the gateway device, and wherein the application is further used to communicate with a cloud service device (40) via MQTT protocol and to upload data of the first terminal and the second terminal. [2] PLC device according to claim 1, characterized by that the gateway device is a programmable logic controller. [3] PLC device according to claim 1, characterized by that the operating system is a Linux operating system. [4] PLC device according to claim 3, characterized by that the first OPC UA server is integrated into a PLCnext firmware and that the application is located in an extension component of PLCnext. [5] PLC device according to claim 3, characterized by that the application is deployed as a container in the Linux operating system. [6] PLC device according to claim 1, characterized bythat the application provides a web page based interface for configuring parameters. [7] PLC device according to claim 6, characterized by that the WEB page is accessible from a computer device or a mobile device that has access to the local network. [8] System according to claim 7, characterized by , on the parameter configuration interface, a user is prompted to enter MQTT cloud server parameters. [9] PLC device according to claim 8, characterized by that the MQTT cloud server parameters include at least one of the following parameters: Broker Client Name, Broker URL, Broker Port, Broker Username, Broker Password, Broker Message Topic, Publisher Name, Default Send Interval, Broker Command Topic, Broker Command Response Topic, Broker Metadata Topic, Metadata Send Interval. [10] PLC device according to claim 7, characterized bythat on the parameter configuration interface the user is prompted to configure parameters for a node of the OPC UA server.

Images