Cloud PLC runtime task dynamic reconstruction system and method

Abstract

The invention discloses a cloud PLC runtime task dynamic reconstruction system and method, and relates to the technical field of automation control, the system comprises a function library used for storing function block types and function block instances; the task trigger is used for managing the execution time of the task executor; the task executor is used for calling the corresponding function block instance from the function library; the configuration file analysis unit is used for receiving and analyzing the parameter information of the new function block type to obtain the new function block type, and receiving and analyzing the task process description file to construct task process information; the function block management unit is used for storing the new function block type into a function library and constructing a corresponding function block instance based on the function block type; and the task construction unit is used for modifying the task flow information and configuring the execution time. The technical problems that in the prior art, the system reconstruction resource loss is large, and reconstruction can only be carried out in the existing function block range during operation are solved.

Description

Technical Field

[0001] The present invention relates to the field of automation control technology, and in particular to a system and method for dynamically reconfiguring tasks at a cloud-based PLC runtime. Background Art

[0002] In the industrial control field environment, the controlled object is usually hosted by a programmable logic controller (PLC) and controlled by function blocks written in the International Electrotechnical Commission (IEC) 61131-3 programming language. Traditional PLCs are also constantly adapting to changes in on-site production needs, gradually developing in the direction of software, virtualization, and cloudification to improve the flexibility, scalability, and intelligence of PLC controllers, forming a cloud-edge distributed industrial control system architecture. In order to meet the changing field control needs, cloud-based PLC controllers need to have certain dynamic adjustment and task reconstruction capabilities. However, in the current industrial control scenarios, the PLC program must be configured and downloaded to the PLC using specific engineering tools provided by the supplier during the engineering phase. Usually, these task programs will remain in this state after deployment, lacking the ability to dynamically adjust to adapt to the changing field control needs and dynamic production environment.

[0003] One of the disadvantages of the traditional PLC system architecture is the locked architecture. The traditional PLC system architecture lacks the flexibility to dynamically change the internal application or network-side configuration, resulting in functional islands. For example, to transfer the application control function in one PLC to another PLC and let the application continue to control the original I / O device; or to recombine certain functions being executed in a PLC with new functions to form a new control application, a lot of redesign is required, and the industrial operation will be interrupted during the task reconstruction process, affecting the actual production operation.

[0004] The distributed reconfigurable PLC proposed by IEC61499 divides tasks into the smallest unit of FB (Function Block), which can meet the dynamic reconstruction function of runtime tasks to a certain extent. However, its task reconstruction scope is limited to the built-in function blocks at runtime, and it is impossible to dynamically add and reconstruct the newly designed function blocks that are not included in the runtime. Summary of the invention

[0005] In order to solve the above technical problems existing in the prior art, an embodiment of the present invention provides a cloud-based PLC runtime task dynamic reconstruction system and method. The technical solution is as follows:

[0006] On the one hand, a cloud-based PLC runtime task dynamic reconstruction system is provided, comprising: a function library, a task trigger, a task executor and a runtime management module; wherein the runtime management module comprises a configuration file parsing unit, a function block management unit and a task construction unit; the function library is used to store function block types and function block instances required to be executed during PLC runtime; the task trigger is used to manage the execution time of the task executor; the task executor is used to call the corresponding function block instance from the function library at the execution time based on the calling order in the task flow information; the configuration file parsing unit is used to receive and parse the newly created function block type parameter information to obtain the newly created function block type, and to receive and parse the task flow description file to construct the task flow information; the function block management unit is used to store the newly created function block type in the function library, and to construct the corresponding function block instance based on the function block type; the task construction unit is used to modify the task flow information, and to configure the execution time.

[0007] Furthermore, the function block type includes: a function block variable data area, a function block processing logic, an input data connection point and an output data connection point; wherein the input data connection point is used to receive exchange data between function blocks and describe the relationship between the input data connection point and the variables in the function block variable data area; the output data connection point is used to output exchange data between function blocks and describe the relationship between the output data connection point and the variables in the function block variable data area; the function block variable area is used to describe the data types of input, output and internal variables required by the function block during execution; the function block processing logic is used to describe the processing function of the function block.

[0008] Furthermore, the task trigger includes a periodic timing trigger with time as a trigger source and an event trigger with an event as a trigger source.

[0009] Furthermore, the task executor includes a task flow organization unit for describing the organization relationship and execution sequence between function blocks.

[0010] Furthermore, the task construction unit includes a task flow modification interface and a task trigger configuration interface; wherein the task flow modification interface is used to modify the organizational relationship and execution order between the functional blocks in the task flow organization unit, and to modify the task flow information; the task trigger configuration interface is used to configure relevant triggers through the task trigger form described in the task flow information.

[0011] Furthermore, the configuration file parsing unit includes a function block parsing interface and a task configuration parsing interface; wherein the function block parsing interface is used to receive and parse the newly created function block type parameter information to obtain the newly created function block type; and the task configuration parsing interface is used to receive and parse the task flow description file to construct the task flow information.

[0012] Furthermore, the function block management unit includes a function type loading interface and a function instance building interface; wherein the function type loading interface is used to store the newly created function block type in the function library; and the function instance building interface is used to build a corresponding function block instance based on the function block type.

[0013] On the other hand, a method for dynamic reconstruction of cloud-based PLC runtime tasks is also provided, which is applied to a cloud-based PLC runtime task dynamic reconstruction system provided by the present invention; the method includes: obtaining parameter information of a newly created function block type, and parsing the newly created function block type based on the configuration file parsing unit; based on a solution of dynamic linking and real-time dynamic loading of function types, storing the newly created function block type in the function library; obtaining a process description file of the task to be reconstructed; based on the process description file and the function library, completing the dynamic reconstruction of the task during PLC runtime through the runtime management module, the task executor and the task trigger.

[0014] Furthermore, the newly created function block type parameter information is obtained, and the newly created function block type is obtained by parsing based on the configuration file parsing unit, including: based on the function block parsing interface, the newly created function block type parameter information is obtained and parsed to obtain the newly created function block type, and a dynamic link file of the newly created function block type is generated; based on the function type dynamic linking and real-time dynamic loading scheme, the newly created function block type is stored in the function library, including: based on the function type loading interface, the newly created function block type and the dynamic link file are loaded and stored in the function library through a dynamic linking mechanism.

[0015] Furthermore, based on the process description file and the function library, the dynamic reconstruction of the task during PLC runtime is completed through the runtime management module, the task executor and the task trigger, including: parsing the process description file based on the task configuration parsing interface, and obtaining the task flow information required for the task to be reconstructed in combination with the function library; the task flow information includes: function block type, execution order between function blocks, input and output data connection relationship between function blocks, and task triggering method; sending the task flow information to the task flow modification interface, so that the task flow modification interface modifies the task flow of the task flow organization unit based on the task flow information; transmitting the task triggering method and the task executor to be triggered to the task trigger through the task trigger configuration interface.

[0016] The embodiment of the present invention provides a cloud-based PLC runtime task dynamic reconstruction system and method. During the PLC runtime, by designing an execution mode that separates the task executor from the specific processing logic of the function block, the PLC runtime can rebuild the task execution process and functions inside the runtime in real time as needed during the execution of the task, and support the dynamic insertion of new functions without affecting the execution of the original runtime. This solution can provide users with a finer PLC task reconstruction granularity. At the same time, the designed general FB function block model can support most control logic designs based on the IEC61131 standard, so that the function block can be inserted into the PLC runtime system in a unified form through dynamic loading, so as to shorten the time required for task reconstruction and reduce the impact on the field control task during reconstruction. The present invention alleviates the technical problems of the prior art that the system reconstruction resource loss is large and the reconstruction can only be performed within the scope of the existing function blocks at runtime. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0018] Figure 1 It is a schematic diagram of a cloud-based PLC runtime task dynamic reconstruction system provided by an embodiment of the present invention;

[0019] Figure 2 is a schematic diagram of a function block type model provided by an embodiment of the present invention;

[0020] Figure 3 It is a flow chart of a method for dynamically reconfiguring tasks at a cloud-based PLC runtime provided by an embodiment of the present invention;

[0021] Figure 4 It is a specific execution flow chart of a new function type dynamic loading solution provided by an embodiment of the present invention;

[0022] Figure 5 It is a flowchart of performing task reconstruction within the existing functional scope at runtime provided by an embodiment of the present invention;

[0023] Figure 6 It is a flowchart provided by an embodiment of the present invention for performing task reconstruction when a new function block needs to be added during runtime. DETAILED DESCRIPTION

[0024] The technical solution of the present invention is described below in conjunction with the accompanying drawings.

[0025] In the embodiments of the present invention, words such as "exemplarily" and "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "example" in the present invention should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of the word "example" is intended to present the concept in a specific way. In addition, in the embodiments of the present invention, the meaning expressed by "and / or" can be both, or it can be either of the two.

[0026] In order to make the technical problems, technical solutions and advantages to be solved by the present invention more clear, a detailed description will be given below with reference to the accompanying drawings and specific embodiments.

[0027] Embodiment 1

[0028] Figure 1 Schematic diagram of a cloud-based PLC runtime task dynamic reconstruction system provided according to an embodiment of the present invention. Figure 1 As shown, the system includes: a function library 10, a task trigger 20, a task executor 30 and a runtime management module 40; wherein the runtime management module 40 includes a configuration file parsing unit 41, a function block management unit 42 and a task construction unit 43.

[0029] Specifically, the function library 10 is used to store the function block types and function block instances that need to be executed when the PLC is running.

[0030] The task trigger 20 is used to manage the execution time of the task executor 30.

[0031] Specifically, Figure 1 As shown, the task trigger 20 includes a periodic timing trigger 21 with time as a trigger source and an event trigger 22 with an event as a trigger source.

[0032] The task executor 30 is used to call the corresponding function block instance from the function library 10 based on the calling sequence in the task flow information at the execution time.

[0033] Specifically, Figure 1 As shown, the task executor 30 includes a task flow organization unit 31, which is used to describe the organization relationship and execution order between function blocks. When the task executor 30 is triggered to execute by the task trigger 20, the task executor 30 completes the execution of the PLC task by reading the organization relationship between the function blocks described by the task flow organization unit 31 of the internal task in real time and calling the corresponding function block instances from the function library 10 in sequence.

[0034] The configuration file parsing unit 41 is used for receiving and parsing the newly created function block type parameter information to obtain the newly created function block type, and for receiving and parsing the task flow description file to construct the task flow information.

[0035] Specifically, Figure 1 As shown, the configuration file parsing unit 41 includes a function block parsing interface 411 and a task configuration parsing interface 412; wherein,

[0036] The function block parsing interface 411 is used to receive and parse the newly created function block type parameter information to obtain the newly created function block type, and then call the function block type loading interface 421 to add the newly created function block type into the function library 10 for storage.

[0037] The task configuration parsing interface 412 is used to receive and parse the task flow description file to construct task flow information, and then call the task construction unit 43 to modify the task executor 30 and the task trigger 20.

[0038] The function block management unit 42 is used to store the newly created function block type in the function library 10 and to construct a corresponding function block instance based on the function block type.

[0039] Specifically, Figure 1 As shown, the function block management unit 42 includes a function type loading interface 421 and a function instance building interface 422; wherein,

[0040] Function type loading interface 421, used to store the newly created function block type into the function library;

[0041] The function instance construction interface 422 is used to construct a corresponding function block instance based on the function block type. Specifically, by providing the required function block type information, reading the corresponding function block type in the function library 10, and then generating a corresponding function block instance for the task executor 30 to call.

[0042] The task construction unit 43 is used to modify the task flow information and to configure the execution time.

[0043] Specifically, Figure 1 As shown, the task construction unit 43 includes a task flow modification interface 431 and a task trigger configuration interface 432; wherein,

[0044] The task flow modification interface 431 is used to modify the organizational relationship and execution order between the functional blocks in the task flow organization unit, and to modify the task flow information; it is also used to modify elements such as the data transmission direction.

[0045] The task trigger configuration interface 432 is used to configure relevant triggers through the task trigger form described in the task flow information, and then wait for the trigger source to be generated and trigger the execution of the relevant task.

[0046] In order to achieve compatibility and uniformity when dynamically loading function blocks, the embodiment of the present invention designs a universal function block type description method. Figure 2 is a schematic diagram of a functional block type model provided according to an embodiment of the present invention. Figure 2 As shown, the function block type includes: function block variable data area, function block processing logic, input data connection point and output data connection point; wherein,

[0047] Input data connection point, used to receive exchange data between function blocks, and describe the relationship between the input data connection point and the variables in the function block variable data area;

[0048] Output data connection points are used to output exchange data between function blocks and describe the relationship between output data connection points and variables in the function block variable data area;

[0049] Function block variable area, used to describe the data types of input, output and internal variables required by the function block during execution;

[0050] Function block processing logic is used to describe the processing function of the function block, that is, the specific processing logic designed by the user to implement certain functions.

[0051] An embodiment of the present invention provides a cloud-based PLC runtime task dynamic reconstruction system. Based on the cloud-based PLC runtime, a task executor and a task trigger are designed. The task executor includes a task flow organization unit, which uses the FB function block as the minimum granularity to describe the organizational relationship and execution order between the function blocks that make up the PLC task. After receiving the trigger of the task trigger, the task executor can call the specific function block processing logic in sequence according to the organizational relationship between the function blocks described by the task flow organization unit to realize the execution of the PLC task. During the execution process, the PLC can dynamically modify the organizational relationship and execution order between the function blocks in the PLC task through the task flow organization unit, thereby realizing the dynamic reconstruction function of the PLC task.

[0052] At the same time, in order to meet the requirements of unified management of internal function blocks at runtime and dynamic loading of new function blocks, a corresponding runtime management module is designed, which includes configuration file parsing unit, function block management unit, task construction unit, etc., and provides corresponding module interfaces to provide management and operation functions for various parts of the runtime. In particular, in order to achieve compatibility when dynamically loading function blocks, a general FB function block type description method is designed, which includes function block variable data area, function block processing logic, input and output data connection points, etc. Finally, the dynamic reconstruction function of cloud PLC runtime tasks is realized.

[0053] Embodiment 2

[0054] Figure 3 1 is a flowchart of a method for dynamically reconfiguring a task at a cloud-based PLC runtime provided by an embodiment of the present invention, and the method is applied to a system for dynamically reconfiguring a task at a cloud-based PLC runtime provided by an embodiment of the present invention. Figure 3 As shown, the method specifically comprises the following steps:

[0055] Step S302, obtaining parameter information of the newly created function block type, and obtaining the newly created function block type through parsing based on the configuration file parsing unit.

[0056] Specifically, based on the function block parsing interface, the parameter information of the newly created function block type is acquired and parsed to obtain the newly created function block type, and a dynamic link file of the newly created function block type is generated.

[0057] Step S304: based on the solution of dynamic linking and real-time dynamic loading of function types, the newly created function block type is stored in the function library.

[0058] Specifically, based on the function type loading interface, the newly created function block type and dynamic link file are loaded and stored in the function library through the dynamic link mechanism.

[0059] Step S306, obtaining a process description file of the task to be reconstructed.

[0060] Step S308, based on the process description file and the function library, the dynamic reconstruction of the tasks during the PLC runtime is completed through the runtime management module, the task executor and the task trigger.

[0061] Specifically, in the PLC runtime system, in addition to some existing functions preloaded in the function library, some user-defined functions usually need to be added during operation to build the actual PLC task execution logic to meet actual control needs.

[0062] In the embodiment of the present invention, in order to dynamically add new functions during the execution of the PLC runtime without stopping the PLC runtime, in step S302 and step S304, a solution of dynamic linking of function types and real-time dynamic loading is adopted. Figure 4 1 is a specific execution flow chart of a new function type dynamic loading solution provided according to an embodiment of the present invention. Figure 4 As shown, the process specifically includes the following steps:

[0063] During the functional design phase, users will follow Figure 2 The unified format of the function block type model shown is used to design a custom function block type, and a dynamic link file of the function block is generated. After the design is completed, the custom function block type is parsed through the function block parsing interface of the configuration file parsing unit in the runtime management module to include: function block type name, function block variable name and data type, function block processing logic and other information, and the information is passed to the function type loading interface in the function block management unit. The interface loads and stores the parsed information and the function block dynamic link file into the function library of the PLC runtime system through the dynamic link mechanism, thereby realizing the dynamic loading of the new function block type, and finally providing the required function type for subsequent FB function block instance generation, PLC task dynamic reconstruction and other functions.

[0064] Specifically, step S308 also includes the following steps:

[0065] Step S3081, parsing the process description file based on the task configuration parsing interface, and obtaining the task process information required for the task to be reconstructed in combination with the function library; the task process information includes: function block type, execution order between function blocks, input and output data connection relationship between function blocks, and task triggering method;

[0066] Step S3082, sending the task flow information to the task flow modification interface, so that the task flow modification interface modifies the task flow of the task flow organization unit based on the task flow information;

[0067] Step S3083: The task triggering mode and the task executor to be triggered are transmitted to the task trigger through the task triggering configuration interface.

[0068] Specifically, in the PLC runtime system, when the field control requirements change, it is necessary to modify the task execution logic or add, delete, or replace some functions on the basis of the original task to meet the field control requirements. Under the existing technology, to achieve the above-mentioned requirements for dynamic generation or modification of PLC tasks, the executable program of the entire task needs to be reloaded into the PLC runtime, and in this process, the PLC runtime must suspend the execution of the original task, resulting in a long time required for task modification and affecting the normal execution of the system.

[0069] In the embodiment of the present invention, under the cloud-based PLC runtime task dynamic reconstruction system architecture, a design mode of separating the task executor from the specific control logic is adopted, so that even during the PLC runtime execution, the dynamic modification of tasks and the dynamic addition, deletion or replacement of new functions and other PLC task dynamic generation functions can be realized. The main process and reconstruction scenario are as follows:

[0070] (1) Refactor tasks within the existing functional scope of the runtime.

[0071] Figure 5 1 is a flowchart of performing task reconstruction within the existing functional scope at runtime according to an embodiment of the present invention. Figure 5 As shown in the figure, in this scenario, since the runtime already has all the functions required for the task, there is no need to dynamically load new functions. Then the user only needs to provide the process description file of the task to the PLC runtime system. The task process description file is parsed through the task configuration parsing interface in the configuration file parsing unit of the runtime management module to obtain information such as the type of function blocks required for the task, the execution order between function blocks, the input and output data connection relationship between function blocks, and the task triggering method; then this information is transmitted to the task configuration parsing interface in the task construction unit of the runtime management module, and the task process of the task process organization unit in the current executor is modified through this interface. After the modification is completed, the task triggering method and the task executor to be triggered are transmitted to the corresponding trigger through the task trigger configuration interface, and the specified task executor is triggered after the trigger source arrives, so that the task executor calls the specific FB function block instance stored in the function library to complete the control task.

[0072] (2) When new function blocks need to be added, new tasks are generated dynamically.

[0073] Figure 6FIG. 1 is a flowchart of performing task reconstruction when a new function block needs to be added during operation according to an embodiment of the present invention. Figure 6 As shown in the figure, in this scenario, since new function blocks need to be added to the PLC runtime, during the design phase, users need to design new function blocks according to the needs of the specific control scenario, and combine these new function blocks with the original function blocks to form a new task flow description file. After the design is completed, the new function blocks will first be dynamically loaded into the PLC runtime through the new function block type dynamic loading scheme; after the dynamic loading of the function blocks is completed, the process of the above scenario (1) can be executed to complete the dynamic generation function of the new PLC task in the case where the new function blocks need to be added.

[0074] From the above description, it can be seen that the embodiment of the present invention provides a method for dynamic reconstruction of cloud PLC runtime tasks. During the PLC runtime, by designing an execution mode that separates the task executor from the specific processing logic of the function block, the PLC runtime can rebuild the task execution process and functions inside the runtime in real time as needed during the execution of the task, and support the dynamic insertion of new functions without affecting the execution of the original runtime. This solution can provide users with a finer PLC task reconstruction granularity, and the designed general FB function block model can support most control logic designs based on the IEC61131 standard, so that the function block can be inserted into the PLC runtime system in a unified form through dynamic loading, so as to shorten the time required for task reconstruction and reduce the impact on field control tasks during reconstruction.

[0075] It should be understood that in various embodiments of the present invention, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0076] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

[0077] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described equipment, devices and units can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0078] In the several embodiments provided by the present invention, it should be understood that the disclosed devices, apparatuses and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0079] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0080] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0081] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, and other media that can store program codes.

[0082] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present invention, which should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims

1. A cloud-based PLC runtime task dynamic reconstruction system, characterized in that: include: Function library, task trigger, task executor and runtime management module; wherein the runtime management module includes a configuration file parsing unit, a function block management unit and a task construction unit; The function library is used to store the function block types and function block instances that need to be executed when the PLC is running; The task trigger is used to manage the execution time of the task executor; The task executor is used to call the corresponding function block instance from the function library based on the calling sequence in the task flow information at the execution time; The configuration file parsing unit is used to receive and parse the newly created function block type parameter information to obtain the newly created function block type, and to receive and parse the task flow description file to construct the task flow information; The function block management unit is used to store the newly created function block type in the function library, and to construct a corresponding function block instance based on the function block type; The task construction unit is used to modify the task flow information and to configure the execution time.

2. The system according to claim 1, characterized in that The function block type includes: function block variable data area, function block processing logic, input data connection point and output data connection point; wherein, The input data connection point is used to receive exchange data between function blocks and describe the relationship between the input data connection point and the variables in the variable data area of ​​the function block; The output data connection point is used to output exchange data between function blocks and describe the relationship between the output data connection point and the variables in the function block variable data area; The function block variable area is used to describe the data types of input, output and internal variables required by the function block during execution; The functional block processing logic is used to describe the processing function of the functional block.

3. The system according to claim 1, characterized in that The task trigger includes a periodic timing trigger with time as a trigger source and an event trigger with an event as a trigger source.

4. The system according to claim 1, characterized in that The task executor includes a task flow organization unit, which is used to describe the organization relationship and execution order between function blocks.

5. The system according to claim 4, characterized in that The task construction unit includes a task flow modification interface and a task trigger configuration interface; wherein, The task flow modification interface is used to modify the organizational relationship and execution order between the function blocks in the task flow organization unit, and to modify the task flow information; The task trigger configuration interface is used to configure relevant triggers through the task trigger form described in the task flow information.

6. The system according to claim 5, characterized in that The configuration file parsing unit includes a function block parsing interface and a task configuration parsing interface; wherein, The function block parsing interface is used to receive and parse the newly created function block type parameter information to obtain the newly created function block type; The task configuration parsing interface is used to receive and parse the task flow description file to construct task flow information.

7. The system according to claim 6, characterized in that The function block management unit includes a function type loading interface and a function instance building interface; wherein, The function type loading interface is used to store the newly created function block type into the function library; The function instance construction interface is used to construct a corresponding function block instance based on the function block type.

8. A method for dynamic reconstruction of tasks during cloud PLC runtime, characterized in that: A cloud-based PLC runtime task dynamic reconstruction system applied to claim 7; the method comprises: Acquire parameter information of the type of the newly created function block, and parse the configuration file parsing unit to obtain the type of the newly created function block; Based on the solution of dynamic linking and real-time dynamic loading of function types, storing the newly created function block type in the function library; Get the process description file of the task to be refactored; Based on the process description file and the function library, dynamic reconstruction of tasks during PLC runtime is completed through the runtime management module, the task executor and the task trigger.

9. The method according to claim 8, characterized in that Acquiring parameter information of the type of a newly created function block, and obtaining the type of the newly created function block by parsing based on the configuration file parsing unit, including: Based on the function block parsing interface, acquiring and parsing the newly created function block type parameter information, obtaining the newly created function block type, and generating a dynamic link file of the newly created function block type; Based on the solution of dynamic linking and real-time dynamic loading of function types, the newly created function block type is stored in the function library, including: Based on the function type loading interface, the newly created function block type and the dynamic link file are loaded and stored into the function library through a dynamic link mechanism.

10. The method according to claim 8, characterized in that Based on the process description file and the function library, the dynamic reconstruction of tasks during PLC runtime is completed through the runtime management module, the task executor and the task trigger, including: Parsing the process description file based on the task configuration parsing interface, and obtaining the task process information required for the task to be reconstructed in combination with the function library; the task process information includes: function block type, execution order between function blocks, input and output data connection relationship between function blocks, and task triggering method; Sending the task flow information to the task flow modification interface, so that the task flow modification interface modifies the task flow of the task flow organization unit based on the task flow information; The task triggering mode and the task executor to be triggered are transmitted to the task trigger through the task triggering configuration interface.

Images