Programmable function block generation method and system based on equipment information model

Abstract

The invention provides a programmable function block generation method and system based on an equipment information model, and relates to the technical field of industrial process control. The method comprises the following steps: uploading industrial equipment information to obtain an equipment information model; uploading the control execution standard of the industrial controller to obtain a function block execution standard; according to the equipment information model, automatic equipment registration is carried out through the equipment management shell, and equipment registration information is obtained; and based on the function block execution standard, generating mapping through the device function manager according to the device registration information, and obtaining the programmable device function block. The programmable function block generation method based on the equipment information model is high in development efficiency, maintainability and reusability.

Description

Technical Field

[0001] The present invention relates to the technical field of industrial process control, and in particular to a method and system for generating programmable function blocks based on a device information model. Background Art

[0002] A typical industrial automation system consists of controllers, actuators, sensors and other devices. The controller is the core device in the system. It uses fieldbus or industrial Ethernet to connect with industrial control devices such as actuators and sensors, and is responsible for executing control programs to achieve automatic control of the equipment. However, the current communication protocol standards of industrial control equipment are complicated, and the operation semantics are defined by the manufacturer. This leads to a very complicated design process of the control program, and the program's reusability and maintainability are poor.

[0003] With the advancement of technology and the increase in consumer market demand, the manufacturing industry has begun to shift from large-scale mass production to personalized intelligent manufacturing. The disadvantages of traditional industrial control systems have become increasingly prominent, and they cannot meet the needs of rapid system reconstruction. Therefore, international industrial organizations have proposed a series of technical solutions to unify the communication interfaces and operation semantics of industrial control equipment to improve the interoperability between devices. For example, solutions such as Asset Administration Shell (AAS) and Module Type Package (MTP) have been proposed.

[0004] MTP is to develop the production process units of process industries into a series of modules with specific functions, and the modules are arranged and combined by the orchestration tool to create a production process. Based on unified standards, the functional description and standardized interface that are independent of the manufacturer are realized to improve the efficiency of system integration. The industrial control system design process based on MTP is divided into two stages: module engineering and orchestration engineering. Usually in the module engineering stage, an MTP file describing the module functions and interfaces is formed, and the MTP file is manually imported into the orchestration tool for orchestration engineering design. In terms of hardware, MTP is based on the existing programmable logic controller (PLC) and distributed control system (DCS), and the PLC and the industrial control equipment connected to the PLC are regarded as a whole and packaged as a module. The integrated development work between PLC and industrial control equipment still relies on the traditional model.

[0005] AAS is a standardized digital representation of assets in manufacturing systems. It supports the establishment of information models to describe asset-related characteristics and technical functions, and realizes open interconnection and unified management of assets. The application areas of AAS focus on asset maintenance management and high-level production scheduling, and do not provide configuration design solutions for field-level industrial control systems.

[0006] Existing technologies support the establishment of standardized information models for industrial control equipment to shield heterogeneous information related to manufacturers, but this technology focuses on the encapsulation of equipment functions and attributes, and does not further propose technical solutions to give equipment autonomous integration capabilities. In existing technologies, device description files are usually integrated into system engineering by manual import, and there is a lack of real-time dynamic monitoring mechanism for the functional status of equipment.

[0007] Existing technical solutions are mainly applied to the levels above the system control layer. In the field-level industrial control system with PLC / DCS as the core, there is a lack of technical solutions to map the device information model to the control program development environment, which makes it impossible to efficiently use the standardized device information model in the control application development process, hindering the further improvement of the system's open interconnection capabilities and reconstruction speed.

[0008] In the prior art, there is a lack of a method for generating programmable function blocks based on a device information model with high development efficiency, high maintainability and high reusability. Summary of the invention

[0009] In order to solve the technical problems in the prior art that the communication protocol of industrial control equipment is complicated, the operation semantics is defined by the manufacturer, resulting in a very complicated design process of the control program, and the reusability and maintainability of the industrial control program are poor, the embodiment of the present invention provides a method and system for generating programmable function blocks based on a device information model. The technical solution is as follows:

[0010] In one aspect, a method for generating a programmable function block based on a device information model is provided. The method is implemented by a programmable function block generating device. The method includes:

[0011] Based on the device management shell, read the industrial equipment information and obtain the equipment information model; upload the industrial controller control execution standard and obtain the function block execution standard;

[0012] According to the device information model, automatically register the device through the device management shell to obtain device registration information;

[0013] Based on the function block execution standard and according to the device registration information, a mapping is generated through a device function manager to obtain a programmable device function block.

[0014] On the other hand, a system for generating programmable function blocks based on a device information model is provided, the system being applied to a method for generating programmable function blocks based on a device information model, the system comprising an industrial controller, a device management shell and an electronic device, wherein:

[0015] The industrial controller is used to upload the industrial controller control execution standard and obtain the function block execution standard;

[0016] The device management shell is used to read industrial device information based on the device management shell to obtain a device information model; according to the device information model, the device is automatically registered through the device management shell to obtain device registration information;

[0017] The electronic device is used to generate mapping through a device function manager based on the function block execution standard and the device registration information to obtain a programmable device function block.

[0018] On the other hand, a programmable function block generation device is provided, the programmable function block generation device comprising: a processor; a memory, the memory storing computer-readable instructions, and the computer-readable instructions, when executed by the processor, implement any one of the programmable function block generation methods based on the device information model as described above.

[0019] On the other hand, a computer-readable storage medium is provided, wherein at least one instruction is stored in the storage medium, and the at least one instruction is loaded and executed by a processor to implement any one of the above-mentioned programmable function block generation methods based on a device information model.

[0020] The beneficial effects brought about by the technical solution provided by the embodiment of the present invention include at least:

[0021] The present invention proposes a method for generating programmable function blocks based on a device information model. The device function manager receives an online registration request of a device management shell, obtains the management shell server address and the device information model, and creates function blocks for the node information matching the mapping rules in the model one by one, and stores the generated function blocks in a library. The manager continuously monitors the device status, and synchronizes the device online status and the device function availability status to the device function library. The development environment can use the function blocks in the library to write device control applications. The function blocks inherit the semantic information of the information model, provide industrial control application developers with device function blocks with clear semantics, simplify the application development process, and improve the system reconstruction efficiency. The present invention is a method for generating programmable function blocks with high development efficiency, high maintainability, and high reusability based on a device information model. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] 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.

[0023] Figure 1 It is a flow chart of a method for generating a programmable function block based on a device information model provided by an embodiment of the present invention;

[0024] Figure 2 It is a schematic diagram of the internal program structure of a device function block based on the IEC 61131-3 PLC standard provided by an embodiment of the present invention;

[0025] Figure 3 It is a block diagram of a programmable function block generation system based on a device information model provided by an embodiment of the present invention;

[0026] Figure 4 It is a structural schematic diagram of a programmable function block generating device provided by an embodiment of the present invention. DETAILED DESCRIPTION

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

[0028] 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.

[0029] In the embodiments of the present invention, "image" and "picture" can sometimes be used interchangeably. It should be noted that when the difference between them is not emphasized, the meanings they intend to express are the same. "of", "corresponding, relevant" and "corresponding" can sometimes be used interchangeably. It should be noted that when the difference between them is not emphasized, the meanings they intend to express are the same.

[0030] In the embodiments of the present invention, sometimes a subscript such as W1 may be written as a non-subscript such as W1. When the difference is not emphasized, the meanings to be expressed are the same.

[0031] 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.

[0032] The embodiment of the present invention provides a method for generating a programmable function block based on a device information model. The method can be implemented by a programmable function block generating device, which can be a terminal or a server. Figure 1 The flowchart of the method for generating a programmable function block based on a device information model is shown. The processing flow of the method may include the following steps:

[0033] S1. Based on the device management shell, read the industrial equipment information and obtain the device information model; upload the industrial controller control execution standard and obtain the function block execution standard.

[0034] The equipment information model is a structured description of industrial equipment information using a modeling language; the modeling language includes an Automation Markup Language or an Open Platform Communication Unified Architecture;

[0035] The equipment information model includes the properties, functions, operating status and geometric structure of industrial equipment.

[0036] In a feasible implementation, the overall architecture of the present invention can be divided into a device layer, an execution layer, and a management layer. The device information model is a structured description of device attributes, functions, operating status, geometric structure and other information using an object-oriented modeling language. The available modeling languages ​​include Open Platform Communications Unified Architecture (OPC UA), Automation Markup Language (AML), etc. The device information model needs to be instantiated in the model address space to provide accessible device objects for external users. The OPC UA server can be used to establish an address space and create device object instances therein.

[0037] S2. According to the device information model, the device is automatically registered through the device management shell to obtain device registration information.

[0038] Among them, the device management shell includes a registrar, a server, a model space, a device function program, an industrial protocol stack, and a peripheral driver;

[0039] The deployment methods of the device management shell include device integrated deployment or separate deployment.

[0040] In a feasible implementation, the device layer of the present invention includes all industrial equipment, which refers to field-level physical equipment used in industrial manufacturing systems, including traditional OT (Operation Technology, OT) domain equipment and new information technology (Information Technology, IT) domain equipment, all of which realize standardized representation of equipment attributes, functions and other information by loading the device management shell. Physically, the device management shell can be deployed integrated with the device or separately deployed across the factory network, and the deployment method can be flexibly selected according to the interface between the management shell and the device. The functions of the device management shell revolve around the device information model.

[0041] The device management shell uses a semantic information model to encapsulate the functional set of the device. The device management shell consists of a registrar, a server, a model space, a device function program, an industrial protocol stack or a peripheral driver. After the management shell program is started, it automatically sends the server address and the information model of the device object in the address space to the device function manager at the system management level to complete the automatic registration of the device.

[0042] Optionally, according to the device information model, the device is automatically registered through the device management shell to obtain device registration information, including:

[0043] In the model space, instantiate the device information model to obtain the device object; the device object includes object nodes, variable nodes and method nodes;

[0044] Based on the registrar, the device is registered according to the device object and the server address to obtain the device registration information.

[0045] In a feasible implementation, in the device management shell, the model space is used to maintain instances of the device information model, namely, device objects. In the model space, the instantiation of the device information model creates a device object. The device information model is a static file, and the device object is an object accessible in the model space.

[0046] The structure of the device object is consistent with that of the device information model. The device object consists of object nodes, variable nodes, and method nodes. The nodes can be nested in multiple layers and connected through reference relationships. The node has a node name that describes the purpose of the node. The node has a node identifier that is unique in the same model space.

[0047] The device object is a virtualized representation of industrial equipment, describing the device attributes, configuration, function, status, etc. The device object provides an access interface with semantic information to the outside and is bound to the device function program internally. External devices can access any node under the device object to trigger the device function program bound to each node to read device attributes, modify device configuration, monitor device status, or call device functions.

[0048] The device function program is bound to each node in the device object, providing the node with the function corresponding to the node name. When the node is accessed by an external device, the bound function program will be triggered to execute and complete the node function. For example, the device object created using the device information model of the conveyor belt contains the method node information for controlling the forward rotation of the conveyor belt, so a function program needs to be written for the node information. In the program, the data format and communication method supported by the conveyor belt are used to control the conveyor belt to realize the forward rotation function.

[0049] Industrial protocol stacks / peripheral drivers are used to connect industrial devices. The device function program establishes a data connection with the industrial device through the industrial protocol stack or peripheral driver supported by the industrial device, supports data exchange between the device function program and the industrial device, and performs the required functions.

[0050] The server is the communication interface provided by the device management shell for external devices. External devices can connect to the server inside the device management shell through the client and access each node under the device object in the model space. The client / server communication mode can be established based on communication protocols such as OPC UA.

[0051] The registrar is used to send a registration request to the programmable function block generation device, the registration request includes the device information model, the identifiers of all nodes under the device object in the model space, and the server address of the device management shell.

[0052] S3. Based on the function block execution standard and according to the device registration information, a mapping is generated through the device function manager to obtain a programmable device function block.

[0053] In a feasible implementation manner, the management layer in the present invention includes a device function manager, a device function library and a control program development environment to complete the function discovery of field devices, the generation and storage of programmable device function blocks, and the control program development based on the device function blocks.

[0054] Among them, the device function manager includes a model parser, a node mapper, a template filler and a state synchronizer.

[0055] In a feasible implementation manner, in the present invention, the model parser is used to parse the information model, extract the node type, node name, node nesting level, reference relationship between the node and the adjacent node, node input data, and node output data of each node from the device information model. After parsing the above information of a node from the device information model, the above node information and node identifier are sent to the node mapper.

[0056] The node mapper is used to determine whether the nodes in the device information model can be mapped to device function blocks. The node mapper stores mapping rules, which specify the mapping relationship between nodes and device function blocks. When the node mapper receives the node information sent by the model parser, it traverses the mapping rules to check whether the node information meets the mapping rules. If it meets the mapping rules, the node information and node identifier are sent to the template filler; if it does not meet the rules, the information is discarded.

[0057] The template filler fills the device function block template according to the node information to generate a programmable device function block file. The programmable device function block file includes a function block description file and a function block internal program.

[0058] The state synchronizer obtains the node identifiers of all nodes that meet the mapping rules from the node mapper, connects to the device management shell server, continuously monitors the node status, and synchronizes the node availability status to the library.

[0059] The device manager receives the device's online registration information, generates a programmable device function block that complies with the industrial controller support standard based on the device information model, continuously monitors the device management shell online status, and synchronizes the status information to the device function library.

[0060] The device function library provides the development environment with device function block description files and function block internal program files. The device function blocks can be directly called in the development environment to efficiently develop industrial control programs. All registered device names are stored in the library, and all function block names, function block description files, and function block internal program files of the device are stored. The storage structure of the device function library is shown in Table 1 (Device Function Library Storage Structure Table).

[0061] Table 1

[0062]

[0063] Among them, the programmable device function block also includes an input reading module, an output writing module, an enable judgment module, a node access module and a result processing module.

[0064] In a feasible implementation manner, the programmable device function block generated in the present invention includes not only the function block description file necessary for running the industrial control program and the control logic program inside the function block, but also some function modules cooperating therewith.

[0065] The input read module is used to read the input variables of the function block and pass them to the subsequent function program. The input read module fixedly reads the Boolean type Execute input variable. During the execution of the programmable device function block, the input read module passes the Execute variable value to the enable judgment module. The template filler adds other input variables in the input read module according to the node information. During the execution of the programmable device function block, the input read module passes other input variable values ​​to the node access module.

[0066] The output write module is used to write the processing results to the output variables of the function block. The output write module fixedly writes data to the Done, Busy, Error and ErrorID output variables. The template filler adds output variables in the output write module according to the node information. During the execution of the device function block, the data received from the result processing module is written to the corresponding output variable.

[0067] The enable judgment module continuously receives the Execute input variable. When the enable signal is received, the subsequent functions of the function block are enabled. In other cases, the subsequent functions will not be enabled.

[0068] The node access module is used to connect to the device management shell server and access the nodes in the device object. The template filler writes the device management shell server address and node identifier into the node access module. And according to the node information, fill the node value reading / writing or node calling function program in the node access module. During the execution of the device function block, the node access module receives other input variable values, connects to the device management shell to access the node, completes the value writing, value reading, or method node calling operation. After the access is completed, the access result is sent to the result processing module.

[0069] The result processing module processes the access result, which includes the access operation execution status identifier and the data returned after accessing the node. The template filler fills the node return data processing program in the result processing module according to the node information. During the execution of the device function block, the result processing module first determines whether the access operation is successfully executed according to the access operation execution status identifier. If successful, the node return data processing program is executed; otherwise, it is not executed. Then the result data is written to the corresponding output variable through the output writing module.

[0070] Optionally, based on the function block execution standard and according to the device registration information, a mapping is generated by a device function manager to obtain a programmable device function block, including:

[0071] Read the device registration information to obtain the device information model;

[0072] According to the device information model, the model parser is used to parse the information and obtain the node information;

[0073] Based on the preset mapping rules and the node information, the node information is filtered through the node mapper to obtain the filtered node information;

[0074] Based on the function block execution standard and the description template of the template filler, a description is generated according to the filtered node information to obtain a function block description file; the function block description file includes a function block name, an input variable name, an output variable name and a data type;

[0075] Based on the function block execution standard and the program template of the template filler, the control program template is filled according to the filtered node information to obtain the internal program of the function block.

[0076] In a feasible implementation, the model parser is used to parse the information model, extract the node type, node name, node nesting level, reference relationship between the node and adjacent nodes, node input data, and node output data of each node from the device information model. After parsing the above information of a node from the device information model, the above node information and node identifier are sent to the node mapper.

[0077] like Figure 2 The figure shows the internal program structure of the device function block based on the IEC 61131-3 PLC standard. The mapping rules specify the mapping relationship between the device information model designed based on the custom modeling standard and the function block based on the IEC 61131-3 PLC standard.

[0078] The function block description file describes the name of the function block, the names of the input and output variables, and the data types. The file format uses the format supported by the industrial controller development environment, such as the PLCOpenXML format for the IEC 61131 PLC standard. The device function manager integrates the description template internally, and the mapping module fills the node information that meets the mapping rules into the template to generate the function block description file.

[0079] The internal program of the function block is used to implement the execution logic of the programmable device function block. The device manager integrates the program template internally, and the mapping module fills the program template according to the node information to complete the internal program of the function block. The structure of the program template must comply with the industrial controller development environment standard.

[0080] In a feasible implementation, the execution layer is the operating environment of the industrial control program, and the developed industrial control program can be downloaded to the operating environment for operation. During the program operation, the device function block runs the internal program and implements the required functions by accessing the device node in the device management shell.

[0081] When executing the automatic generation process of device function blocks, the device function manager stores the device information and the generated function block files in the device function library. It also uses the device management shell server address in the registration information to continuously access the device management shell, monitor the device online status and synchronize the status information to the device function library.

[0082] After the development environment of the industrial control program loads the device function library, the device function blocks in the library can be called. Users call the required device function blocks in the development environment and add processing logic to form the industrial control program. Download the industrial control program to the running environment and run the program. During the operation of the industrial control program, when the device function block is triggered to execute, the device function block connects to the corresponding device management shell server and accesses the nodes in the device object to control the device to complete the required functions.

[0083] The present invention proposes a method for generating programmable function blocks based on a device information model. The device function manager receives an online registration request of a device management shell, obtains the management shell server address and the device information model, and creates function blocks for the node information matching the mapping rules in the model one by one, and stores the generated function blocks in a library. The manager continuously monitors the device status, and synchronizes the device online status and the device function availability status to the device function library. The development environment can use the function blocks in the library to write device control applications. The function blocks inherit the semantic information of the information model, provide industrial control application developers with device function blocks with clear semantics, simplify the application development process, and improve the system reconstruction efficiency. The present invention is a method for generating programmable function blocks with high development efficiency, high maintainability, and high reusability based on a device information model.

[0084] Figure 3 The present invention is a block diagram of a system for generating programmable function blocks based on a device information model according to an exemplary embodiment. The system is used in a method for generating programmable function blocks based on a device information model. Figure 3 , the system includes an industrial controller 310, a device management shell 320 and an electronic device 330, wherein:

[0085] The industrial controller 310 is used to upload the control execution standard of the industrial controller and obtain the function block execution standard;

[0086] The device management shell 320 is used to read industrial device information based on the device management shell to obtain a device information model; according to the device information model, the device is automatically registered through the device management shell to obtain device registration information;

[0087] The electronic device 330 is used to generate mapping through a device function manager based on the function block execution standard and according to the device registration information to obtain a programmable device function block.

[0088] The equipment information model is a structured description of industrial equipment information using a modeling language; the modeling language includes an Automation Markup Language or an Open Platform Communication Unified Architecture;

[0089] The equipment information model includes the properties, functions, operating status and geometric structure of industrial equipment.

[0090] Among them, the device management shell includes a registrar, a server, a model space, a device function program, an industrial protocol stack, and a peripheral driver;

[0091] The deployment methods of the device management shell include device integrated deployment or separate deployment.

[0092] Optionally, the device management shell 320 is further configured to:

[0093] In the model space, instantiate the device information model to obtain the device object; the device object includes object nodes, variable nodes and method nodes;

[0094] Based on the registrar, the device is registered according to the device object and the server address to obtain the device registration information.

[0095] Among them, the programmable device function block also includes an input reading module, an output writing module, an enable judgment module, a node access module and a result processing module.

[0096] Among them, the device function manager includes a model parser, a node mapper, a template filler and a state synchronizer.

[0097] Optionally, the electronic device 330 is further configured to:

[0098] Read the device registration information to obtain the device information model;

[0099] According to the device information model, the model parser is used to parse the information and obtain the node information;

[0100] Based on the preset mapping rules and the node information, the node information is filtered through the node mapper to obtain the filtered node information;

[0101] Based on the function block execution standard and the description template of the template filler, a description is generated according to the filtered node information to obtain a function block description file; the function block description file includes a function block name, an input variable name, an output variable name and a data type;

[0102] Based on the function block execution standard and the program template of the template filler, the control program template is filled according to the filtered node information to obtain the internal program of the function block.

[0103] The present invention proposes a method for generating programmable function blocks based on a device information model. The device function manager receives an online registration request of a device management shell, obtains the management shell server address and the device information model, and creates function blocks for the node information matching the mapping rules in the model one by one, and stores the generated function blocks in a library. The manager continuously monitors the device status, and synchronizes the device online status and the device function availability status to the device function library. The development environment can use the function blocks in the library to write device control applications. The function blocks inherit the semantic information of the information model, provide industrial control application developers with device function blocks with clear semantics, simplify the application development process, and improve the system reconstruction efficiency. The present invention is a method for generating programmable function blocks with high development efficiency, high maintainability, and high reusability based on a device information model.

[0104] Figure 4is a schematic diagram of the structure of a programmable function block generation device provided by an embodiment of the present invention, such as Figure 4 As shown, the programmable function block generation device may include the above Figure 3 The programmable function block generation system based on the device information model is shown. Optionally, the programmable function block generation device 410 may include a first processor 2001 .

[0105] Optionally, the programmable function block generating device 410 may further include a memory 2002 and a transceiver 2003 .

[0106] The first processor 2001, the memory 2002 and the transceiver 2003 may be connected via a communication bus.

[0107] Combine the following Figure 4 The components of the programmable function block generation device 410 are specifically introduced as follows:

[0108] The first processor 2001 is the control center of the programmable function block generation device 410, and may be a processor or a general term for multiple processing elements. For example, the first processor 2001 is one or more central processing units (CPUs), or an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present invention, such as one or more microprocessors (digital signal processors, DSPs), or one or more field programmable gate arrays (field programmable gate arrays, FPGAs).

[0109] Optionally, the first processor 2001 may execute various functions of the programmable function block generation device 410 by running or executing a software program stored in the memory 2002 and calling data stored in the memory 2002 .

[0110] In a specific implementation, as an embodiment, the first processor 2001 may include one or more CPUs, such as Figure 4 CPU0 and CPU1 are shown in FIG.

[0111] In a specific implementation, as an embodiment, the programmable function block generation device 410 may also include multiple processors, such as Figure 4The first processor 2001 and the second processor 2004 are shown in FIG. Each of these processors may be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). The processor here may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0112] The memory 2002 is used to store the software program for executing the solution of the present invention, and is controlled to be executed by the first processor 2001. The specific implementation method can refer to the above method embodiment, which will not be repeated here.

[0113] Optionally, the memory 2002 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 2002 may be integrated with the first processor 2001, or may exist independently, and may be generated through the interface circuit ( Figure 4 (not shown) is coupled to the first processor 2001, which is not specifically limited in this embodiment of the present invention.

[0114] The transceiver 2003 is used to communicate with a network device or a terminal device.

[0115] Optionally, the transceiver 2003 may include a receiver and a transmitter ( Figure 4 The receiver is used to implement a receiving function, and the transmitter is used to implement a sending function.

[0116] Optionally, the transceiver 2003 may be integrated with the first processor 2001, or may exist independently and generate an interface circuit ( Figure 4 (not shown) is coupled to the first processor 2001, which is not specifically limited in this embodiment of the present invention.

[0117] It should be noted that Figure 4 The structure of the programmable function block generation device 410 shown in the figure does not constitute a limitation on the router, and the actual knowledge structure recognition device may include more or less components than shown in the figure, or combine certain components, or arrange the components differently.

[0118] In addition, the technical effects of the programmable function block generation device 410 can refer to the technical effects of the programmable function block generation method based on the device information model described in the above method embodiment, which will not be repeated here.

[0119] It should be understood that the first processor 2001 in the embodiment of the present invention may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0120] It should also be understood that the memory in the embodiments of the present invention may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0121] The above embodiments can be implemented in whole or in part by software, hardware (such as circuits), firmware or any other combination. When implemented by software, the above embodiments can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, the process or function described in the embodiment of the present invention is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable system. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center by wired (such as infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that contains one or more available media sets. The available medium can be a magnetic medium (for example, a floppy disk, a hard disk, a tape), an optical medium (for example, a DVD), or a semiconductor medium. The semiconductor medium can be a solid-state hard disk.

[0122] It should be understood that the term "and / or" in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. A and B can be singular or plural. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship, but it may also indicate an "and / or" relationship. Please refer to the context for specific understanding.

[0123] In the present invention, "at least one" means one or more, and "more than one" means two or more. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0124] 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.

[0125] 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.

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

[0127] In the several embodiments provided by the present invention, it should be understood that the disclosed devices, systems and methods can be implemented in other ways. For example, the system 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 the system or unit, which can be electrical, mechanical or other forms.

[0128] 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.

[0129] 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.

[0130] 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.

[0131] 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 method for generating a programmable function block based on a device information model, characterized in that: The method comprises: Based on the device management shell, read the industrial equipment information and obtain the equipment information model; upload the industrial controller control execution standard and obtain the function block execution standard; According to the device information model, automatically register the device through the device management shell to obtain device registration information; Based on the function block execution standard and according to the device registration information, a mapping is generated through a device function manager to obtain a programmable device function block.

2. The method for generating a programmable function block based on a device information model according to claim 1, characterized in that: The device information model is a structured description of industrial device information using a modeling language; the modeling language includes Automation Markup Language or Open Platform Communication Unified Architecture; The equipment information model includes the attributes, functions, operating status and geometric structure of the industrial equipment.

3. The method for generating programmable function blocks based on a device information model according to claim 1, characterized in that: The device management shell includes a registrar, a server, a model space, a device function program, an industrial protocol stack and a peripheral driver; The deployment mode of the device management shell includes device integrated deployment or separate deployment.

4. The method for generating programmable function blocks based on device information model according to claim 3, characterized in that: The step of automatically registering a device through a device management shell according to the device information model to obtain device registration information includes: In the model space, instantiate according to the device information model to obtain a device object; the device object includes an object node, a variable node and a method node; Based on the registrar, device registration is performed according to the device object and the address of the server to obtain device registration information.

5. The method for generating programmable function blocks based on device information model according to claim 1, characterized in that: The programmable device function block also includes an input reading module, an output writing module, an enabling judgment module, a node access module and a result processing module.

6. The method for generating programmable function blocks based on device information model according to claim 1, characterized in that: The device function manager includes a model parser, a node mapper, a template filler and a state synchronizer.

7. The method for generating programmable function blocks based on device information model according to claim 6, characterized in that: The method of generating a mapping based on the function block execution standard and according to the device registration information through a device function manager to obtain a programmable device function block includes: Reading the device registration information to obtain a device information model; According to the device information model, information is parsed by the model parser to obtain node information; Based on the preset mapping rule, according to the node information, the node information is screened by the node mapper to obtain the screened node information; Based on the function block execution standard and the description template of the template filler, a description is generated according to the filtered node information to obtain a function block description file; the function block description file includes a function block name, an input variable name, an output variable name and a data type; Based on the function block execution standard and the program template of the template filler, the control program template is filled according to the filtered node information to obtain the internal program of the function block.

8. A system for generating programmable function blocks based on a device information model, wherein the system for generating programmable function blocks based on a device information model is used to implement the method for generating programmable function blocks based on a device information model as claimed in any one of claims 1 to 7, characterized in that: The system comprises an industrial controller, a device management shell and electronic equipment, wherein: The industrial controller is used to upload the industrial controller control execution standard and obtain the function block execution standard; The device management shell is used to read industrial device information based on the device management shell to obtain a device information model; according to the device information model, the device is automatically registered through the device management shell to obtain device registration information; The electronic device is used to generate mapping through a device function manager based on the function block execution standard and the device registration information to obtain a programmable device function block.

9. A programmable function block generation device, characterized in that: The programmable function block generating device comprises: processor; A memory having computer-readable instructions stored thereon, wherein when the computer-readable instructions are executed by the processor, the method according to any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores program codes, which can be called by a processor to execute the method according to any one of claims 1 to 7.

Images