A low-code device information digital twin model creation method

Abstract

The present application relates to the technical field of digital twinning, in particular to a low-code device information digital twinning model creation method, which builds a model framework by dragging and dropping predefined input, output and logic processing components from a component library to a canvas, flexibly configures component parameters using a context attribute panel, and establishes data flow between component ports using intuitive graphical connection operations, and performs real-time data type checking to ensure the correctness of the connection. Finally, by configuring the address binding of I / O components with external controllers or data sources, and supporting real-time data monitoring and input forced assignment during the simulation stage, a device information model is constructed that is complete in function and can directly interact with the real control system for data verification. The traditional code writing work is transformed into visual configuration and connection operation, greatly reducing the technical threshold and development workload, enabling domain experts to quickly build, modify and debug models without deep programming background.

Description

Technical Field

[0001] This invention relates to the field of digital twin technology, specifically to a low-code method for creating digital twin models of device information. Background Technology

[0002] In industrial sectors such as aviation logistics and intelligent manufacturing, digital twin technology has become a key tool for system design, virtual debugging, and performance optimization. A digital twin model of equipment information can map the state and behavior of physical equipment in real time and interact with the controller, thereby simulating the operation of the actual system in a virtual environment.

[0003] Currently, creating digital twin models of such equipment, especially implementing data interfaces between the model and the controller, primarily relies on traditional programming methods. However, traditional programming methods have high technical barriers, a shortage of talent, and involve a large workload and long development cycle for code development from scratch, resulting in low model building efficiency and difficulty in adapting to the needs of rapid iteration. Furthermore, some commonly used graphical programming or dataflow tools are not specifically designed for industrial equipment digital twin modeling and lack support for the specific needs of this field. Existing virtual debugging solutions mostly focus on the 3D motion simulation of equipment, and their support for pure data information logic modeling, especially the modular reuse and hierarchical organization of complex logic, as well as the integrated modeling and testing, is significantly insufficient.

[0004] Therefore, there is an urgent need for a method to create digital twin models of equipment information that can lower the technical threshold, improve development efficiency, and facilitate maintenance. Summary of the Invention

[0005] In view of the shortcomings of the existing technology, the purpose of this invention is to provide a low-code method for creating a digital twin model of device information to solve the technical problems of high technical threshold, low development efficiency and difficulty in maintenance of the existing technology.

[0006] To achieve the above objectives, the present invention adopts the following technical solution:

[0007] A low-code method for creating a digital twin model of device information, performed within a graphical user interface, includes the following steps:

[0008] S1: Model building phase:

[0009] S11: Add model elements by dragging and dropping predefined components from the graphical component library onto the main canvas; the components include input parameter components, output parameter components, and logic processing components;

[0010] S12: In response to the user's selection of a component on the canvas, dynamically display and configure the parameters of the component in a context-sensitive property panel;

[0011] S13: Connect the ports of the components to form a data stream via a graphical connection operation; wherein, when performing the connection operation, the system performs data type matching and verification in real time, and if the data types are incompatible, the connection is prohibited or a visual warning is provided;

[0012] S14: In the property panel, configure the address binding relationship between at least one input parameter component or output parameter component and an external controller or data source;

[0013] S2: Model Validation Phase

[0014] S21: Start the simulation in the graphical user interface and display the data values ​​transmitted in the data stream in real time;

[0015] S22: Receive a forced assignment instruction for at least one input parameter triggered by the user through the graphical user interface, and drive the model to run based on the input data after forced assignment, so as to observe the output results.

[0016] Furthermore, the logic processing components in the graphical component library in S11 include at least a set of the following components: basic logic gates, comparators, mathematical operators, timers, counters, script function blocks, and state machines.

[0017] Furthermore, in step S13, connecting the port of the component via a graphical connection operation includes the following steps:

[0018] S131: In response to the user's dragging operation from the output anchor point of the first component to the input anchor point of the second component, a connecting line with a directional arrow is generated on the main canvas;

[0019] S132: During simulation, the transmitted data values ​​are dynamically displayed along the connection line.

[0020] Furthermore, the model building phase also includes the steps of building and reusing logical units:

[0021] S15: In response to a user instruction, combine and save multiple components that are connected by wires on the main canvas into a named logical unit; add the saved logical unit as an independent component to the graphical component library; when building a new model, realize logic reuse by dragging and dropping the named logical unit from the component library to the main canvas.

[0022] Furthermore, the logic unit can be nested as a sub-model within a higher-level digital twin model; when entering the editing state of the logic unit, the system presents a sub-canvas to display its internal structure; the input and output parameters of the sub-model are represented as independent input / output ports in the higher-level model, and interact with other components of the higher-level model through graphical connections.

[0023] Furthermore, the model building phase also includes a parameter grouping step:

[0024] S16: In response to user instructions, define multiple related input parameters or output parameters as a parameter group in the graphical user interface; during model construction, the parameter group can be dragged, moved, connected, or assigned values ​​as a whole.

[0025] Furthermore, the graphical component library contains predefined device templates, which encapsulate standardized input parameters, output parameters, and internal logical relationships for specific types of devices; the model building phase also includes:

[0026] S17: In response to the user selecting a device template and dragging it to the main canvas, automatically instantiate all components and internal connections corresponding to the template; the user can adjust the parameters of the instantiated device template through the property panel.

[0027] Furthermore, the model validation phase also includes automated testing steps:

[0028] S23: Define test cases in the graphical user interface. Each test case includes a set of input data and corresponding expected output data. Automatically execute all test cases and compare the actual output data generated by the model based on the input data with the expected output data. Generate and display a test report. The test report visually identifies the test cases that passed and failed, and displays the data comparison details.

[0029] Compared with the prior art, the present invention has the following beneficial effects:

[0030] This invention builds a model framework by dragging and dropping predefined input, output, and logic processing components from a component library onto a canvas. Component parameters are flexibly configured using a contextual property panel, and intuitive graphical connection operations are employed to establish data flow between component ports. Real-time data type validation ensures the correctness of the connections. Finally, by configuring address bindings for I / O components to external controllers or data sources and supporting real-time data monitoring and forced input assignment during simulation, a fully functional device information model capable of direct data interaction and verification with a real control system is constructed. Transforming traditional coding work into visual configuration and connection operations significantly reduces the technical threshold and development workload, enabling domain experts to quickly build, modify, and debug models without extensive programming backgrounds, thus significantly improving the development efficiency and maintainability of digital twin models. Attached Figure Description

[0031] Figure 1 This is a flowchart illustrating the steps of an embodiment of a low-code digital twin model creation method for device information according to the present invention. Detailed Implementation

[0032] The present invention will be further described in detail below through specific embodiments:

[0033] The specific implementation process is as follows:

[0034] Example 1

[0035] Example 1 is attached. Figure 1 As shown, a low-code method for creating a digital twin model of device information, executed in a graphical user interface, includes the following steps:

[0036] S1: Model building phase:

[0037] S11: Add model elements by dragging and dropping predefined components from the graphical component library onto the main canvas; the components include input parameter components, output parameter components, and logic processing components;

[0038] S12: In response to the user's selection of a component on the canvas, dynamically display and configure the parameters of the component in a context-sensitive property panel;

[0039] S13: Connect the ports of the components to form a data stream via a graphical connection operation; wherein, when performing the connection operation, the system performs data type matching and verification in real time, and if the data types are incompatible, the connection is prohibited or a visual warning is provided;

[0040] S14: In the property panel, configure the address binding relationship between at least one input parameter component or output parameter component and an external controller or data source;

[0041] S2: Model Validation Phase

[0042] S21: Start the simulation in the graphical user interface and display the data values ​​transmitted in the data stream in real time;

[0043] S22: Receive a forced assignment instruction for at least one input parameter triggered by the user through the graphical user interface, and drive the model to run based on the input data after forced assignment, so as to observe the output results.

[0044] This invention transforms the traditional programming modeling process into a fully graphical operation, constructing a digital twin model of a device in a "what you see is what you get" manner. This method abstracts complex device data interactions into intuitive graphical elements and visualized data flows, allowing users to complete the entire process from basic modeling to functional verification through simple operations such as dragging, connecting lines, and configuring.

[0045] In the implementation process, engineers first enter the model building phase. They drag and drop the required model elements from the graphical component library on the left side of the interface to the central main canvas area. These predefined components include input parameter components, output parameter components, and various logic processing components, which together constitute the basic element library for modeling.

[0046] This embodiment uses conveyor belt control in an airport baggage handling system as an example. Engineers need to establish a simple start-stop control logic. First, drag two input parameter components from the component library, naming them "Manual Start Button" and "Photoelectric Sensor" respectively, to receive external control signals. Then, drag an output parameter component, naming it "Motor Start / Stop Command," to output control commands to the controller. Finally, drag an AND logic gate component to handle the start-stop logic. All these components are presented as graphical icons on the canvas, and users can freely adjust their positions by dragging and dropping to create a clear visual layout.

[0047] When a user selects any component on the canvas, the properties panel on the right immediately switches to display the configurable parameters corresponding to that component. This context-sensitive property configuration mechanism ensures that users can quickly locate and modify relevant parameters without having to search for the required functions in complex menus.

[0048] When the user selects the "Manual Start Button" input component, the property panel displays its name, data type, default value, and other parameters. The user sets its data type to Boolean and the default value to False. Similarly, the "Photoelectric Sensor" input component is also configured as a Boolean type. For the "AND" logic gate, the property panel displays its logic type as "AND" and shows it has two input ports. Finally, the "Motor Start / Stop Command" output component is configured, also set to a Boolean data type. This unified configuration method allows even equipment engineers unfamiliar with programming languages ​​to easily understand and complete the parameter settings.

[0049] After configuring the components, the next step is to establish data flow relationships through graphical connections. The essence of connection operations is to establish data transfer paths between components, which is similar to the edge connection in a directed graph, but the visualization greatly reduces the difficulty of operation.

[0050] When performing a connection operation, the user moves the mouse to the output anchor point of the "Manual Start Button" component (usually represented by a small circular icon on the right side of the component), presses the left mouse button, and drags out a connection line to the first input anchor point of the "AND" logic gate before releasing it. This operation is repeated to connect the output of the "Photoelectric Sensor" to the second input port of the "AND" logic gate, and finally, to the input port of the "Motor Start / Stop Command". The system performs real-time data type matching verification during connection execution. If the user attempts to connect a Boolean output to a component that only accepts numeric input, the system will disable the connection and display a red warning. This real-time verification mechanism effectively prevents logical errors.

[0051] During the simulation run, the transmitted data values ​​will be dynamically displayed on these connection lines. For example, when both the "manual start button" and the "photoelectric sensor" are True, the connection lines will display the flow of the "True" value to the "AND" logic gate. After calculation, the "True" value will be output to the motor start / stop command, providing users with an intuitive visualization of the data flow.

[0052] Furthermore, the logic processing components in the graphical component library of this invention include at least a set of the following components: basic logic gates, comparators, mathematical operators, timers, counters, script function blocks, and state machines. These components cover a wide range of needs, from simple logical judgments to complex control.

[0053] In a baggage sorting system, basic logic gates are used to handle simple AND, OR, and NOT logic; comparators can be used to compare baggage weight with a set threshold; mathematical operators can calculate the total volume of baggage; timers are used to control the delay of the sorting arm's movements; counters can count the number of baggage passing through a specific location; script function blocks allow users to embed custom complex algorithms; and state machines are used to model the complete workflow of the sorting equipment, such as state transitions like "idle-scan-sort-complete".

[0054] Furthermore, connecting the port of the component via a graphical connection operation includes the following steps:

[0055] S131: In response to the user's dragging operation from the output anchor point of the first component to the input anchor point of the second component, a connecting line with a directional arrow is generated on the main canvas;

[0056] S132: During simulation, the transmitted data values ​​are dynamically displayed along the connection line.

[0057] The implementation of graphical connection operations involves two key steps. The first is the connection establishment process: the system responds to the user's dragging operation from the output anchor point of the first component to the input anchor point of the second component, generating a connection line with a directional arrow on the main canvas to clearly indicate the data flow direction.

[0058] Secondly, there is the visualization feedback during simulation: during simulation, the system dynamically displays the transmitted data values ​​along the connection lines. For example, in the conveyor belt speed control model, when the speed setpoint changes from 100 to 150, the change is displayed in real time on the connection line, and after being processed by the mathematical calculator, the calculated result is displayed on the output connection line, providing the user with a complete data flow trajectory.

[0059] Furthermore, the model building stage in this embodiment also includes the steps of building and reusing logic units:

[0060] S15: In response to a user instruction, combine and save multiple components that are connected by wires on the main canvas into a named logical unit; add the saved logical unit as an independent component to the graphical component library; when building a new model, realize logic reuse by dragging and dropping the named logical unit from the component library to the main canvas.

[0061] This invention provides a complete implementation mechanism for the construction and reuse of logical units. It encapsulates a set of verified logical components and their connections into reusable modules, similar to functions or subroutines in programming, but implemented graphically.

[0062] In practice, users can select an already connected AND gate, two input components, and one output component, and then choose the "Combined into Logic Unit" command via the right-click menu. The system will prompt the user to name the logic unit, such as "Basic Start / Stop Module." Once completed, this newly created logic unit will be automatically added to the graphical component library. When the user needs the same start / stop logic in another project, they only need to drag and drop the "Basic Start / Stop Module" from the component library onto the canvas; there is no need to rebuild the same logic structure.

[0063] Furthermore, in this embodiment, the logic unit can be nested as a sub-model within a higher-level digital twin model; when entering the editing state of the logic unit, the system presents a sub-canvas to display its internal structure; the input and output parameters of the sub-model are represented as independent input / output ports in the higher-level model, and interact with other components of the higher-level model through graphical connections.

[0064] The nesting functionality of logical units further expands the flexibility of modeling. These logical units can be nested as sub-models within higher-level digital twin models. For example, when building a complete sorting system, users can treat the "basic start / stop module" as a sub-component and combine it with other logical units (such as speed control modules, fault detection modules, etc.) through connections to form a more complex system.

[0065] In practice, double-clicking a logic unit allows access to its internal editing interface, where users can view or modify its internal structure, while only its input / output interfaces are displayed in the higher-level model. This hierarchical design significantly improves the modeling efficiency and maintainability of complex systems, enabling users to employ a "divide and conquer" strategy to build large-scale digital twin systems.

[0066] Furthermore, the model building stage in this embodiment also includes a parameter grouping step:

[0067] S16: In response to user instructions, define multiple related input parameters or output parameters as a parameter group in the graphical user interface; during model construction, the parameter group can be dragged, moved, connected, or assigned values ​​as a whole.

[0068] To improve the processing efficiency of large batches of parameters, this invention provides a parameter grouping function. By bundling multiple logically related parameters into a whole and operating them as a unit in the graphical interface, both logical coherence and operational efficiency are maintained.

[0069] In a modeling example of an airport baggage sorting system, a motor may involve multiple control parameters: start signal, stop signal, speed setting, fault reset, etc. Users can select these related input / output parameters simultaneously on the canvas, then right-click and select "Create Parameter Group," naming it "Motor Control Group." After successful creation, these parameters will appear as a border with the group name on the canvas, allowing users to move, copy, or delete them as a whole.

[0070] Furthermore, the graphical component library in this embodiment includes predefined device templates, which encapsulate standardized input parameters, output parameters, and internal logic relationships for specific types of devices; the model building stage also includes:

[0071] S17: In response to the user selecting a device template and dragging it to the main canvas, automatically instantiate all components and internal connections corresponding to the template; the user can adjust the parameters of the instantiated device template through the property panel.

[0072] For common standard equipment in the industry, this invention predefines device templates in a graphical component library. These templates, based on domain knowledge, encapsulate standardized input / output parameters and internal logic relationships for specific types of equipment, which users can directly call and fine-tune according to actual needs.

[0073] In airline baggage handling systems, for example, the component library provides standard equipment templates such as "roller conveyors," "sorters," and "barcode readers." When a user drags and drops a "sorter template" onto the canvas, the system automatically instantiates all relevant components of the equipment: including multiple sensor inputs (package detection, position sensing), actuator outputs (sorting arm control, direction indication), and internal processing logic (sorting timing control, mode selection). Users only need to adjust individual parameters in the properties panel according to the actual equipment specifications, such as sorting action delay time and scanning sensitivity, to quickly complete the modeling of a standard piece of equipment.

[0074] Furthermore, the model verification stage of this embodiment also includes automated testing steps:

[0075] S23: Define test cases in the graphical user interface. Each test case includes a set of input data and corresponding expected output data. Automatically execute all test cases and compare the actual output data generated by the model based on the input data with the expected output data. Generate and display a test report. The test report visually identifies the test cases that passed and failed, and displays the data comparison details.

[0076] The automated testing function in the model validation phase provides a systematic verification method. By defining complete test cases, it automatically executes and compares the expected results with the actual output, generating detailed test reports.

[0077] Users can create multiple test cases. For example, test case 1 simulates normal startup conditions (manual startup = True, photoelectric sensor = True), with the expected output being motor start = True; test case 2 simulates a state without items (manual startup = True, photoelectric sensor = False), with the expected output being motor start = False. After executing automated testing, the system generates a detailed test report, clearly listing the pass / fail status of each test case and displaying a comparison between the expected and actual outputs, helping users quickly locate and fix logical errors.

[0078] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention, and all such modifications or substitutions should be covered within the scope of the claims of the present invention.

Claims

1. A low-code method for creating a digital twin model of device information, characterized in that, This method is executed in a graphical user interface and includes the following steps: S1: Model building phase: S11: Add model elements by dragging and dropping predefined components from the graphical component library onto the main canvas; the components include input parameter components, output parameter components, and logic processing components; S12: In response to the user's selection of a component on the canvas, dynamically display and configure the parameters of the component in a context-sensitive property panel; S13: Connect the ports of the components to form a data stream via a graphical connection operation; wherein, when performing the connection operation, the system performs data type matching and verification in real time, and if the data types are incompatible, the connection is prohibited or a visual warning is provided; S14: In the property panel, configure the address binding relationship between at least one input parameter component or output parameter component and an external controller or data source; S2: Model Validation Phase S21: Start the simulation in the graphical user interface and display the data values ​​transmitted in the data stream in real time; S22: Receive a forced assignment instruction for at least one input parameter triggered by the user through the graphical user interface, and drive the model to run based on the input data after forced assignment, so as to observe the output results.

2. The method for creating a low-code digital twin model of device information according to claim 1, characterized in that: The logic processing components in the graphical component library in S11 include at least a set of the following components: basic logic gates, comparators, mathematical operators, timers, counters, script function blocks, and state machines.

3. The method for creating a low-code digital twin model of device information according to claim 1, characterized in that: The step S13, which connects the port of the component via a graphical connection operation, includes the following steps: S131: In response to the user's dragging operation from the output anchor point of the first component to the input anchor point of the second component, a connecting line with a directional arrow is generated on the main canvas; S132: During simulation, the transmitted data values ​​are dynamically displayed along the connection line.

4. The method for creating a low-code digital twin model of device information according to claim 1, characterized in that: The model building phase also includes the steps of building and reusing logical units: S15: In response to a user instruction, combine and save multiple components that are connected by wires on the main canvas into a named logical unit; add the saved logical unit as an independent component to the graphical component library; when building a new model, realize logic reuse by dragging and dropping the named logical unit from the component library to the main canvas.

5. The method for creating a low-code digital twin model of device information according to claim 4, characterized in that: The logical unit can be nested as a sub-model into a higher-level digital twin model; When entering the editing state of the logic unit, the system presents a sub-canvas to display its internal structure; the input and output parameters of the sub-model are represented as independent input / output ports in the higher-level model, and interact with other components of the higher-level model through graphical connections.

6. The method for creating a low-code digital twin model of device information according to claim 5, characterized in that: The model building phase also includes a parameter grouping step: S16: In response to user instructions, define multiple related input parameters or output parameters as a parameter group in the graphical user interface; during model construction, the parameter group can be dragged, moved, connected, or assigned values ​​as a whole.

7. The method for creating a low-code digital twin model of device information according to claim 6, characterized in that: The graphical component library contains predefined device templates, which encapsulate standardized input parameters, output parameters, and internal logic relationships for specific types of devices; the model building phase also includes: S17: In response to the user selecting a device template and dragging it to the main canvas, automatically instantiate all components and internal connections corresponding to the template; the user can adjust the parameters of the instantiated device template through the property panel.

8. The method for creating a low-code digital twin model of device information according to claim 7, characterized in that: The model validation phase also includes automated testing steps: S23: Define test cases in the graphical user interface, wherein the test cases include a set of input data and corresponding expected output data; All test cases are executed automatically, and the actual output data generated by the model based on the input data is compared with the expected output data; a test report is generated and displayed, which visually identifies the test cases that passed and failed, and shows the data comparison details.

Images