Zero-code development platform, development method, electronic device and medium

Abstract

The present invention discloses a zero-code development platform, a development method, an electronic device and a medium, belonging to the field of software development. The zero-code development platform includes a data protocol layer, a device layer, an operator and module library, a business logic layer and an application layer; the data protocol layer manages industrial control protocols and database systems; the device layer accesses and manages hardware resources; the operator and module library provides functional operators, resource component operators and HMI modules for calling; the business logic layer calls the modules in the operator and module library in a graphical manner through a designer to construct a business task process; the application layer provides a running environment for the business process and executes the process. The zero-code development platform, development method, electronic device and medium provided by the present invention can achieve the efficient development and management of complex industrial automation applications through multi-level architecture design, improve the overall performance of the system and the development experience of users, simplify the development process and shorten the development cycle.

Description

Technical Field

[0001] The present invention belongs to the technical field of software development, and particularly relates to a zero-code development platform, a development method, an electronic device, and a medium. Background Art

[0002] In the field of industrial automation, especially in the development process of non-standard automation equipment, the development of industrial control software has always been a complex and high-threshold technical problem. In the traditional non-standard automation industry, due to the highly customized requirements of equipment and production lines, the development of existing industrial control software often faces the following main problems:

[0003] Non-standard automation equipment needs to be developed customized according to user requirements, and the software needs to be highly adapted to specific hardware devices, involving a large amount of code writing and debugging. Especially when it comes to the integration of multi-field technologies (such as PLC programming, vision algorithms, motion control, etc.), developers need to spend a lot of time developing and optimizing different modules, resulting in low overall development efficiency.

[0004] Traditional development methods usually require developers to be proficient in multiple programming languages and technical frameworks, such as C++, Python, PLC Ladder Diagram, etc. In addition, developers also need to be familiar with industrial control protocols (such as Modbus, OPC, etc.) and the communication logic of industrial devices (such as PLCs, cameras, sensors), which poses high requirements on the professional capabilities of developers. For enterprises, the cost of cultivating compound talents who understand both programming and industrial field applications is extremely high, and resources are scarce.

[0005] The development process of non-standard automation software is usually customized for specific requirements, resulting in difficulty in quickly adjusting and implementing function expansion or module upgrade for new requirements after development.

[0006] Therefore, in view of the above technical problems, it is necessary to provide a new solution. Summary of the Invention

[0007] The purpose of the present invention is to provide a zero-code development platform, a development method, an electronic device, and a medium, which can realize zero-code in the software development process, quickly build industrial automation programs, and shorten the development cycle.

[0008] To achieve the above purpose, the technical solutions provided by the present invention are as follows:

[0009] In a first aspect, the present invention provides a zero-code development platform, which includes a data protocol layer, a device layer, an operator and module library, a business logic layer, and an application layer; the data protocol layer is used to manage and access industrial control protocols and database systems; the device layer is connected to the data protocol layer and is used to access hardware resources and abstract and manage the hardware resources; the operator and module library is connected to the device layer and is used to provide callable function operators, resource component operators, and HMI modules; the business logic layer is connected to the operator and module library and is used to call the function operators, resource component operators, and HMI modules in the operator and module library through a designer to graphically construct a business task process; the application layer is connected to the business logic layer and is used to provide a running environment for the business task process and run the business task process.

[0010] In one or more embodiments, the operator and module library includes an industry solution library, and the industry solution library stores industry solution task process templates under preset scenarios.

[0011] In one or more embodiments, the designer includes a resource manager, and the resource manager includes a first canvas interaction designer and a component property configurator; the first canvas interaction designer is used to call the resource component operators in the operator and module library to create resource component objects on the canvas interface; the component property configurator is used to configure parameters for the resource component objects.

[0012] In one or more embodiments, the designer further includes a business generation manager, and the business generation manager includes a second canvas interaction designer and an algorithm property configurator; the second canvas interaction designer is used to call the function operators in the operator and module library to create function operator objects on the canvas interface, and the function operator objects can call the output data of the resource component objects; the algorithm property configurator is used to configure parameters for the function operator objects.

[0013] In one or more embodiments, the designer further includes an HMI interface generation manager, and the HMI interface generation manager includes an HMI human-computer interaction designer, an HMI property configurator, an event manager, and an HMI system manager; the HMI human-computer interaction designer is used to call the HMI modules in the operator and module library to create HMI objects on the design interface, and the HMI objects can call and respond to the output data of the resource component objects and function operator objects, the resource component objects can adjust parameters in response to the output data of the HMI objects, and the function operator objects can respond to the interaction commands of the HMI objects; the HMI property configurator is used to configure the parameters of the HMI objects; the event manager is used to bind, delete, or modify the events of the HMI objects; the HMI system manager is used to perform visual management, window management, and data persistence of the HMI objects.

[0014] In one or more embodiments, the application layer includes an execution engine, and the execution engine is used to call the designer in the business logic layer to manage and execute the business task process.

[0015] In one or more embodiments, the zero-code development platform further includes a task process debugger for debugging the business task process; and / or the zero-code development platform further includes a release generator for releasing the business task process to generate an executable program file; and / or the zero-code development platform further includes a document generator for generating and managing parameter description documents and interface description documents of each operator and module in the operator and module library.

[0016] In a second aspect, the present invention provides a development method based on the foregoing zero-code development platform, which includes:

[0017] In response to a user instruction, call the function operators, resource component operators, and HMI modules in the operator and module library through the designer in the business logic layer; in response to a user instruction, configure the attributes, parameters, reference relationships, and logical connection relationships of the called object modules in the design interface of the designer to graphically construct a business task process; based on the operating environment provided by the application layer, run the business task process.

[0018] In a third aspect, the present invention provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, and when the processor executes the program, it implements the development method as described above.

[0019] Fourthly, the present invention provides a computer-readable medium having computer-executable instructions stored thereon, and when the computer-executable instructions are executed by a processor, they are used to implement the development method described above.

[0020] Compared with the prior art, the zero-code development platform, development method, electronic device and medium provided by the present invention can achieve efficient development and management of complex industrial automation applications through a multi-level architecture design, improve the overall performance of the system and the development experience of users, simplify the development process, and shorten the development cycle; also enhance the flexibility and scalability of the system through modular and visual designs, lower the technical threshold, and provide an efficient, convenient and reliable development solution for the industrial automation field. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings required for the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some embodiments recorded in the present invention, and those of ordinary skill in the art can obtain other drawings based on these drawings without creative efforts.

[0022] Figure 1 It is the architecture diagram of the zero-code development platform in an embodiment of the present invention;

[0023] Figure 2 It is the module block diagram of the zero-code development platform in an embodiment of the present invention;

[0024] Figure 3 It is the interface diagram of the resource manager in an embodiment of the present invention;

[0025] Figure 4 It is the interface diagram of the service generation manager in an embodiment of the present invention;

[0026] Figure 5 It is the interface diagram of the HMI interface generation manager in an embodiment of the present invention;

[0027] Figure 6 It is the flowchart of the development method based on the zero-code development platform in an embodiment of the present invention;

[0028] Figure 7 It is the structural block diagram of the electronic device in an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0029] To enable those skilled in the art to better understand the technical solutions in the present invention, the following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all of the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the scope of protection of the present invention.

[0030] With the rapid development of industrial automation technology, especially in the field of non-standard automation, the traditional software development method faces a series of challenges. In the prior art, the development process of industrial automation software usually relies on complex programming work, which not only requires developers to have profound programming capabilities and in-depth understanding of industrial protocols, but also results in a long software development cycle, high development costs, and difficult customization and upgrading. In addition, the requirements of industrial automation projects often have strong individuality and variability, which makes the software reusability low and unable to effectively meet the changing market demands and application scenarios.

[0031] In this context, the inventor realizes that the existing development mode overly relies on traditional programming and manual coding, with a long development cycle and difficult maintenance. Therefore, there is an urgent need for a new way to simplify the development process, improve efficiency, lower the development threshold, and at the same time enhance the flexibility and scalability of the software. Based on an in-depth analysis of the defects of the prior art, the present invention proposes a new zero-code development platform, aiming to provide a convenient, efficient, and flexible software development solution for the non-standard automation industry.

[0032] The core of the technical implementation idea of the present invention is to build a zero-code development platform, enabling developers to complete complex software development tasks through a graphical interface without writing code. This platform transforms the traditional programming process into a modular and visual design process, relying on a series of preset operators and modules, which can be combined and configured through simple drag-and-drop operations to complete the construction and debugging of business task processes. The design idea of the zero-code development platform is to simplify the complex programming logic and hardware interaction process into simple component calls and configurations through highly abstract functional module encapsulation, avoiding complex code writing and debugging processes.

[0033] The architecture of the platform includes multiple layers. Among them, the data protocol layer and the device layer provide the system with the functions of accessing underlying hardware resources and protocol management; the operator and module library layer provides reusable functional operators, resource component operators, and HMI modules; the business logic layer is the core of the platform, organizing and constructing business logic through a graphical designer, and effectively combining and connecting different component modules; the application layer is the final operating environment, supporting the execution and monitoring of the designed business processes. Through this architecture, users can flexibly design, modify, and debug their business task processes without involving code writing.

[0034] Specifically, the present invention provides flexible customization support by designing a modular operator library and a business process construction tool, enabling users to customize automation control solutions according to their own needs. At the same time, the platform supports graphical management of complex business processes, allowing developers to intuitively view, modify, and debug task processes, and complete the management of hardware resources, algorithm configuration, and human-machine interface design through visual operations.

[0035] The technical implementation idea of the present invention not only breaks through the complexity and technical barriers existing in traditional automation software development, but also greatly reduces the technical threshold for developers through the simplified design of the graphical interface. Developers can quickly build and customize an automation system that meets actual needs without having to deeply understand the underlying code logic and complex industrial control protocols. Therefore, the platform can greatly improve development efficiency, shorten the development cycle, reduce development costs, and make software maintenance and upgrade more flexible and convenient.

[0036] Please refer to Figure 1 As shown, it is the architecture diagram of the zero-code development platform in an embodiment of the present invention. The zero-code development platform includes a data protocol layer, a device layer, an operator and module library, a business logic layer, and an application layer.

[0037] The data protocol layer is used to manage and access industrial control protocols and database systems. The device layer is connected to the data protocol layer and is used to access hardware resources and abstract and manage the hardware resources. The operator and module library is connected to the device layer and is used to provide callable functional operators, resource component operators, and HMI modules. The business logic layer is connected to the operator and module library and is used to call the functional operators, resource component operators, and HMI modules in the operator and module library through a designer to graphically construct business task processes. The application layer is connected to the business logic layer and is used to provide the operating environment for the business task processes and run the business task processes.

[0038] As the bottom layer of the platform, the data protocol layer undertakes the management and access functions of industrial control protocols (such as OPC, TCP / IP, serial port, Modbus, S7, MC, Can protocol, etc.) and database systems. Its core task is to provide a communication bridge between the platform and external hardware devices and data systems, and is responsible for handling the conversion of different data protocols and the efficient transmission of information.

[0039] In industrial automation systems, various devices and database systems often use different protocols for data interaction. The existence of such heterogeneous systems makes the platform face complex problems such as protocol incompatibility and inconsistent data formats when integrating with different devices and systems. The design solution of the data protocol layer is precisely to solve these problems. By providing a unified interface and protocol conversion mechanism, different types of data can flow smoothly, thus ensuring that the platform can be efficiently docked with a variety of hardware and systems.

[0040] In terms of design, the data protocol layer provides a set of general interfaces for upper-layer applications to call by abstracting and encapsulating various industrial protocols and database communication standards. Whether it is common industrial control protocols such as Modbus, OPC, Profinet, or database systems of types such as SQL and NoSQL, the data protocol layer can flexibly handle the compatibility issues between them. Specifically, the data protocol layer first identifies and parses communication requests from external devices or databases, and then normalizes the data according to different types of protocols.

[0041] The device layer is connected to the data protocol layer and is used for the access, abstraction, and management of hardware resources, providing a unified hardware interaction interface for the platform. In industrial automation applications, various hardware devices (such as sensors, actuators, PLCs, cameras, etc.) are the core basis for realizing control and monitoring functions. However, devices from different manufacturers usually adopt different communication protocols and hardware interfaces, resulting in complexity and compatibility issues when integrating these devices. The design of the device layer aims to solve these problems through abstraction and standardization, providing the upper-layer logic with a consistent hardware resource management ability.

[0042] The design solution of the device layer is based on the principles of modularity and abstraction. First, by connecting to the data protocol layer, it accesses hardware resources supported by various industrial protocols. The device layer standardizes these resources, converting complex underlying hardware interfaces into unified device objects. These device objects not only encapsulate the communication logic required for hardware interaction but also provide unified property, operation method, and status information interfaces, facilitating users to call and manage them in the business process. Through this abstraction, the platform can shield hardware differences, enabling developers to use devices without having to concern themselves with specific hardware characteristics and underlying implementation details, thereby reducing development complexity.

[0043] The device layer can also implement the dynamic management function of hardware resources, including automatic discovery of resources, configuration initialization, status monitoring, and real-time operations. Through the device layer, users can easily complete the registration and management of hardware and intuitively call relevant resources in the designer. For example, users can access sensors through the device layer for real-time data collection or control the PLC to execute actions. The dynamic management ability of the device layer enables users to flexibly adapt to various hardware environments and supports the online addition and removal of devices, enhancing the flexibility and scalability of the platform.

[0044] The operator and module library is a key module for implementing the core functions in the zero-code development platform. It is connected to the device layer and provides rich callable functions for platform users, including function operators, resource component operators, and HMI (Human Machine Interface) modules. Through this operator and module library, developers can call encapsulated functional components with minimal technical investment, thus quickly completing the construction and implementation of complex industrial automation tasks. Its design scheme aims to abstract complex underlying technical logics into functional units that users can directly drag and call through a modular, standardized, and highly scalable operator architecture, providing basic support for zero-code development.

[0045] The design of the operator and module library is based on the concept of high modularity, which abstracts and encapsulates common industrial control functions, algorithm logics, resource management operations, and human-machine interface components. The operators in the module library are designed as standardized units, including reusable interfaces, attribute configuration options, and input / output parameter structures. Users can call these operators through configuration without writing underlying code. For example, function operators cover functions widely used in industrial applications such as 2D / 3D vision algorithms, data processing algorithms, and logic control; resource component operators are responsible for calling and operating resources in the device layer, such as sensor data reading and device status control; the HMI module provides functional components for designing and managing the human-machine interface, including basic elements such as buttons, charts, and input boxes. Through the organic combination of these operators, platform users can quickly achieve integrated development from underlying hardware operations to upper-layer human-machine interaction.

[0046] In an exemplary embodiment, the operator and module library includes an industry solution library, which stores industry solution task flow templates under preset scenarios. By storing industry solution task flow templates under preset scenarios, ready-to-use functional modules and business processes are provided for users. The industry solution library forms process templates applicable to specific scenarios by abstracting and standardizing typical task requirements in complex industrial applications. These templates contain both common functional logics in the industry and algorithm configurations and process settings optimized based on actual requirements.

[0047] In the design solution, the industry solution library decomposes complex business processes into reusable modules and combines them with best practices in specific industry scenarios to form complete process templates. These templates cover a variety of industrial automation scenarios, including production line monitoring, quality inspection, visual positioning, data collection and analysis, motion control, and automated operations.

[0048] The role of the industry solution library in the platform is reflected in significantly reducing the development time cost, enhancing the reusability of solutions, and improving the user's development experience. It provides users with ready-to-use functional processes, greatly shortening the development cycle. Users do not need to build the entire task logic from scratch. They only need to call the template and perform scenario adaptation to quickly meet complex functional requirements. The templated design greatly improves the reusability of processes. Similar application scenarios within the industry can directly call existing templates without repeated design and debugging.

[0049] Please refer to Figure 2 As shown, the business logic layer is one of the core layers of the zero-code development platform. It is connected to the operator and module library. Its main function is to provide a visual development environment through the designer, enabling users to call functional operators, resource component operators, and HMI modules in the operator and module library to quickly build business task processes in a graphical manner. The design of this layer aims to simplify the development process, lower the technical threshold, and provide users with an efficient and intuitive development platform, enabling the rapid implementation of complex industrial automation logic.

[0050] In the design solution, through cooperation with the operator and module library, the business logic layer presents various predefined functional modules (including functional operators, resource component operators, and HMI modules) to users in a visual way. Users can drag and drop these modules on the canvas through the graphical interface of the designer and combine them into specific business logic processes. These modules can be functional operators for data processing (such as 2D vision inspection, 3D modeling, path planning, etc.), resource component operators for device control (such as sensor data reading, PLC control instructions, etc.), or HMI modules for user interaction (such as buttons, charts, and display panels, etc.). The business logic layer connects the inputs, outputs, and behaviors of these modules through configuration interfaces and logical connection lines to form a complete task process.

[0051] The business logic layer not only supports the dragging and combination of modules but also allows users to set the behaviors of each module in detail through the property panel and parameter configuration functions. For example, users can set operation parameters for functional operators, configure associated hardware devices for resource components, or define user interaction events and display rules for HMI modules. In addition, the business logic layer supports multi-level process nesting and logical conditional branching, enabling developers to flexibly define and manage multi-level process structures in complex business scenarios.

[0052] During the process of function implementation, the business logic layer also takes into account the data flow and event-driven mechanism. The output data of each module can be passed to the next module through logical connection lines, enabling seamless data transfer in the process. At the same time, the business logic layer supports an event-driven logic triggering mechanism, where users can define specific event conditions to trigger the operation of certain modules, thus achieving dynamic control of the task process. This design significantly improves the flexibility of the process logic, allowing users to build a more real-time and responsive automated system.

[0053] The role of the business logic layer is to closely integrate the abstract functions of the zero-code development platform with actual application scenarios, providing users with an efficient and intuitive development environment, significantly reducing the development threshold. Users can quickly build complex business logic processes through a graphical interface without the need to master programming skills. The modular and visual design of the business logic layer greatly shortens the development cycle. Users can quickly complete the full-process development from hardware resource invocation to data processing and then to human-computer interaction through simple drag-and-drop and configuration operations.

[0054] In addition, the business logic layer also provides convenience for team collaboration. Through its intuitive process design and modular function decomposition, team members with different roles (such as algorithm engineers, hardware engineers, and process experts) can collaborate efficiently on the same platform, each responsible for the definition, configuration, and optimization of their respective modules. This collaboration method not only improves the efficiency of project development but also ensures that the final system can better meet the actual application requirements. The business logic layer also supports docking with third-party systems or platforms, such as OPencv, Halcon, Labview, VisionPro, etc.

[0055] In an exemplary embodiment, please refer to Figure 3 As shown, the designer includes a resource manager, and the resource manager includes a first canvas interaction designer and a component property configurator; the first canvas interaction designer is used to call the resource component operators in the operator and module library to create resource component objects on the canvas interface; the component property configurator is used to configure the parameters of the resource component objects.

[0056] The resource manager is used to manage and configure hardware resources, related components, data resources, etc., providing a basis for the efficient construction of business task processes. The core of the resource manager includes a first canvas interaction designer and a component property configurator, enabling users to intuitively and flexibly manage and configure various resource components, thus significantly reducing the complexity of the development process.

[0057] The first canvas interaction designer is one of the core modules of the resource manager, providing users with an intuitive graphical interface that enables them to easily call resource component operators in the operator and module library and create resource component objects on the canvas. This design transforms the complex code call process in traditional development into a simple drag-and-drop operation. Users only need to select the required resource component operators and drag them to the specified position on the canvas to complete the creation of resource objects. The canvas interaction designer displays resource components in a modular and visual form, enabling users to understand and manage the involved hardware resources, such as sensors, actuators, PLC controllers, etc., in a more intuitive way. In this way, developers can quickly build complex resource management logic without having to concern themselves with the underlying implementation details.

[0058] The component property configurator is a supporting module of the first canvas interaction designer, used to configure the parameters of the created resource component objects. Each resource component object contains a set of predefined properties, and the component property configurator provides an intuitive interface through which users can adjust these properties through simple input and selection operations. For example, users can set parameters such as sampling frequency and range for sensor resources, and define action modes or operation delays for actuator resources. This function not only simplifies the initialization and configuration process of hardware resources but also enables users to flexibly adjust system operation parameters according to actual needs to ensure the best performance of resource components.

[0059] Specifically, please refer to Figure 4 As shown, the designer also includes a service generation manager, which includes a second canvas interaction designer and an algorithm property configurator; the second canvas interaction designer is used to call the function operators in the operator and module library to create function operator objects on the canvas interface, and the function operator objects can call the output data of the resource component objects; the algorithm property configurator is used to configure the parameters of the function operator objects.

[0060] Through the collaborative work of the second canvas interaction designer and the algorithm property configurator, the service generation manager provides users with an intuitive graphical development environment for the design of business logic and the implementation of algorithm processes.

[0061] The second canvas interactive designer provides users with an interactive graphical canvas for invoking functional operators in the operator and module library and creating corresponding functional operator objects on the canvas interface. This design greatly simplifies the complex code calling process in traditional development, allowing users to place functional operators at appropriate positions on the canvas through simple drag-and-drop operations. The creation of functional operator objects is not just a simple invocation of operator functions; it also achieves seamless integration with resource component objects, enabling direct utilization of the output data of resource component objects to complete the closed-loop design from data acquisition to algorithm processing. In this way, users can easily design complex industrial logics such as vision algorithms, data analysis, and path planning without having to worry about the underlying code implementation.

[0062] The algorithm property configurator is used to precisely configure the parameters of functional operator objects. Each functional operator object has a set of adjustable properties, and the algorithm property configurator provides an intuitive interface for users to adjust parameter settings to meet different business requirements. For example, in an image processing algorithm, users can set parameters such as the threshold for edge detection and the image resolution through the algorithm property configurator; in a data analysis process, users can set the type of statistical model or the threshold range of calculation metrics. The design of the algorithm property configurator not only makes parameter settings more flexible but also helps users verify the effect of parameter settings through real-time visualization feedback, improving the efficiency of process debugging.

[0063] The design of the business generation manager also fully considers the interactivity between modules and the management of data flow. Through standardized data interfaces and logical connection lines, functional operator objects can flexibly interact with resource component objects and other functional operator objects to achieve dynamic data transfer. Users can easily connect different modules on the canvas to build complex multi-level task logics. In addition, the business generation manager supports logical branching and conditional judgment, allowing users to design more intelligent and flexible business processes.

[0064] Furthermore, please refer to Figure 5As shown, the designer further includes an HMI interface generation manager, which includes an HMI human-machine interaction designer, an HMI property configuration manager, an event manager, and an HMI system manager; the HMI human-machine interaction designer is used to call the HMI modules in the operator and module library to create HMI objects on the design interface, and the HMI objects can call and respond to the output data of the resource component objects and function operator objects. The resource component objects can adjust parameters in response to the output data of the HMI objects, and the function operator objects can respond to the interaction commands of the HMI objects; the HMI property configurator is used to configure parameters for the HMI objects; the event manager is used to bind, delete, or modify the events of the HMI objects; the HMI system manager is used to perform visual management, window management, and data persistence for the HMI objects.

[0065] The HMI interface generation manager is a module for human-machine interaction interface design and management in the zero-code development platform. Its core consists of an HMI human-machine interaction designer, an HMI property configuration manager, an event manager, and an HMI system manager. Through modular design and visual operation, this module provides users with an efficient and flexible way to build interfaces, enabling users to quickly design and manage complex interaction interfaces, thereby realizing the docking of human-machine interaction and business logic.

[0066] The HMI human-machine interaction designer is the core part of this module, responsible for calling the HMI modules in the operator and module library, allowing users to create HMI objects on the design interface. Users can place components such as buttons, sliders, charts, and input boxes on the design canvas through simple drag-and-drop operations and define the layout and interaction logic of these components through intuitive operations. HMI objects can not only call the output data of resource component objects and function operator objects but also dynamically respond to changes in these data. For example, users can create a chart component that displays sensor data in real time or a control that adjusts the operation parameters of an actuator through a slider. Through this two-way data interaction mechanism, HMI objects are both the terminals for information display and the entrances for business operations.

[0067] The HMI property configuration manager provides parameter configuration functions for each HMI object. Users can perform detailed settings on the appearance (such as color, size, font) and behavior (such as data binding method, interaction response rule) of the object through the property configuration interface. For example, the data refresh frequency can be set for a chart component, and the feedback action after a button component is pressed can be defined. This flexible configuration method not only enhances the freedom of interface design but also ensures that HMI objects can precisely meet business requirements.

[0068] The event manager acts as a logical connection in the HMI interface generation manager, and is used to bind, delete, or modify the events of HMI objects. Users can define the trigger conditions and response logic of each component through the event manager. For example, when a button is clicked, a certain algorithm is started, and an alarm is issued when the data exceeds the threshold. The existence of the event manager makes the HMI interface not just a static display tool, but an intelligent system with dynamic interaction capabilities.

[0069] The HMI system manager is responsible for the overall management of the interface components, including visualization management, window management, and data persistence functions. Visualization management allows users to intuitively adjust the interface layout and component hierarchy. Window management supports multi-interface switching and dynamic window generation. The data persistence function ensures that the interface layout, properties, and logic configured by users can be saved and reused, facilitating calls during subsequent development or system upgrades. This overall management ability not only improves the efficiency of interface design but also enhances the maintainability of the system.

[0070] Through the collaboration of each sub-module, the HMI interface generation manager provides users with comprehensive support from interface layout to logical design, significantly reducing the complexity of human-machine interface development and enabling users to focus on function implementation without worrying about underlying technical details. In addition, through the connection with the resource manager and the service generation manager, this module realizes the deep integration of the business process and the user interface, ensuring the consistency between information display, user operations, and background logic.

[0071] The application layer is responsible for providing a running environment for the business task process and ensuring that the task process can be executed smoothly according to the logic defined by the user. As the execution core of the platform, the application layer provides a solid guarantee for the stability and efficiency of the entire system by managing, scheduling, and monitoring the operation of the business task process.

[0072] The design scheme of the application layer fully considers the complex requirements of industrial automation applications. Through a flexible task scheduling mechanism and an efficient execution engine, the task processes designed in the business logic layer can run smoothly in the actual environment. The execution engine is the core component of the application layer. It parses the flowcharts and algorithm call logics defined in the business logic layer and converts them into underlying execution instructions. The execution engine can call the functions of resource component objects and functional operators in real time, dynamically manage the data flow and event triggers, and ensure the efficient operation of the business process in various complex scenarios. For example, in a production line monitoring task, the execution engine can collect sensor data in real time according to the set logic, call image processing algorithms for quality inspection, and trigger the operation instructions of related devices based on the inspection results.

[0073] The application layer not only provides a running environment but also has task management and monitoring capabilities. During the task execution process, the application layer monitors the status and data flow of each module in real time to ensure that each link of the process is executed as planned. Once an abnormality occurs in a certain task process (such as device offline or data anomaly), the application layer can promptly abort the current task or initiate a predefined emergency process to enhance the reliability and fault tolerance of the system. Users can also, through the log recording function of the application layer, trace back the detailed process of task execution, thereby quickly locating problems and optimizing the process design.

[0074] In addition, the task scheduling mechanism of the application layer enables multiple task processes to run in parallel or sequentially, thus meeting the requirements for multi-task processing in complex scenarios. Users can customize the scheduling order and running strategy of tasks according to business priorities and resource allocation situations. For example, high-priority tasks can be set to preempt resources or different task processes can be executed according to time periods. Through this flexible scheduling method, the application layer can maximize the utilization of system resources and improve the overall operation efficiency of the platform.

[0075] The role of the application layer is also reflected in the feedback and visual display of task execution results. After the execution is completed, the application layer further processes the data output by the business logic layer and presents it to the user through the HMI interface. For example, the application layer can present real-time production data, detection results, or running status in the form of charts or reports to help users intuitively understand the working conditions of the system. This closed-loop feedback mechanism not only improves the usability of the system but also provides a basis for users to further optimize the task process.

[0076] In an exemplary embodiment, the zero-code development platform further includes a task process debugger for debugging the business task process; and / or the zero-code development platform further includes a release generator for releasing the business task process to generate an executable program file; and / or the zero-code development platform further includes a document generator for generating and managing parameter description documents and interface description documents for each operator and module in the operator and module library.

[0077] The task flow debugger is an important tool for debugging in the platform. It can help users discover and solve potential problems before the execution of business task flows. The debugger is designed with rich debugging functions, including breakpoint setting, step-by-step execution, variable monitoring, and error logging. Users can set breakpoints at key nodes of the task flow to gradually check the running status and data flow of each operator or module, thereby quickly locating the cause of problems. For example, when a user is debugging a task flow that includes sensor data acquisition, data cleaning, and visual detection, breakpoints can be set before and after the data cleaning operator to monitor whether the input and output of the data meet expectations. The task flow debugger also supports real-time log analysis, presenting warning and error messages during the process execution intuitively to the user, thus greatly reducing the difficulty of troubleshooting and problem-solving.

[0078] The release generator is a module in the platform for delivering business achievements. Its function is to package the completed business task flow of the user into an executable program file. The release generator integrates information such as task logic, operator calls, and resource configurations, and transforms the development result into a complete and independent executable file, which enables the development result to be easily deployed and run on the target system. For example, the production line monitoring and control task designed and completed by the user can be quickly generated into a running program through the release generator and deployed to an industrial control computer or server, thus realizing rapid application and production in the industrial field. The design of the release generator emphasizes automation and compatibility, supporting the generation of program files adapted to multiple operating environments (such as Windows, Linux) to ensure that the task flow can run stably on different hardware platforms.

[0079] The document generator provides perfect document management capabilities for the platform. Its core task is to automatically generate and maintain parameter description documents and interface description documents for various operators and modules in the operator and module library. In traditional development processes, document writing is often a time-consuming and easily overlooked link. The document generator generates standardized description documents through automatic parsing of the operator and module library, including detailed information such as the purpose of each operator, parameter configuration methods, input and output interfaces, etc. These documents not only facilitate developers to understand and use the operators but also provide support for subsequent maintenance, upgrading, and collaboration. For example, in team development, developers with different roles can quickly understand the functions of the modules used in the task flow and their configuration requirements by referring to the documents, thereby improving collaboration efficiency.

[0080] Please refer to Figure 6 As shown, it is a flowchart of the development method based on the aforementioned zero-code development platform in an embodiment of the present invention. The development method specifically includes the following steps:

[0081] S601: In response to a user instruction, call functional operators, resource component operators, and HMI modules in the operator and module library through the designer in the business logic layer.

[0082] Users can call functional operators, resource component operators, and HMI modules in the operator and module library through the designer in the business logic layer. The core of this step is to enable users to quickly obtain the preset functional modules in the platform. The platform provides a rich operator library and module library, covering a wide range of functions from data processing, hardware control to interface interaction. Users only need to perform drag-and-drop operations to place the required modules into the task flow on the designer interface. The design of this step completely shields the complexity of the underlying implementation, and users do not need to write any code to achieve module calls from resource access to algorithm application.

[0083] S602: In response to a user instruction, configure the attributes, parameters, reference relationships, and logical connection relationships of the called object module in the design interface of the designer to graphically construct a business task flow.

[0084] Users can configure the attributes, parameters, reference relationships, and logical connection relationships of the called module in the designer interface to graphically construct a business task flow. The key to this step is to endow users with the ability to flexibly define and optimize business logic through a graphical interface. Users can refine the behavior of the module through the attribute configuration interface, such as adjusting the threshold of the functional operator or optimizing the layout of the HMI control. At the same time, users can connect the input and output relationships of different modules through logical connection lines to construct a dynamic data flow and event trigger mechanism. The configuration process is completely intuitive, and users can clearly see the overall structure of the process and the data transfer logic.

[0085] S603: Based on the operating environment provided by the application layer, run the business task flow.

[0086] Users can actually run the designed business task flow through the operating environment provided by the application layer. This step is to verify and execute the entire development process. Based on the execution engine of the application layer, each module in the task flow is gradually called and run according to the preset logic. During the running process, the platform dynamically manages the data transfer between modules, triggers event responses, and monitors the running status of the process in real time. Once the process runs to completion, the platform will output the running results, such as detection data, alarm status, or interface display effects. Through this process, users can not only verify the rationality of the task flow design but also optimize and adjust the process according to the actual running effect.

[0087] Please refer to Figure 7As shown in the figure, an embodiment of the present invention further provides an electronic device 700, which includes at least one processor 701, a memory 702 (such as a non-volatile memory), a memory 703, and a communication interface 704, and at least one processor 701, the memory 702, the memory 703, and the communication interface 704 are connected together via an internal bus 705. The at least one processor 701 is configured to call at least one program instruction stored or encoded in the memory 702, so that the at least one processor 701 performs various operations and functions of the development method described in the various embodiments of this specification.

[0088] In the embodiments of this specification, the electronic device 700 may include, but is not limited to: personal computers, server computers, workstations, desktop computers, laptop computers, notebook computers, mobile electronic devices, smart phones, tablet computers, cellular phones, personal digital assistants (PDAs), handheld devices, messaging devices, wearable electronic devices, consumer electronic devices, and so on.

[0089] An embodiment of the present invention further provides a computer-readable medium, on which computer-executable instructions are carried. When the computer-executable instructions are executed by a processor, they can be used to implement various operations and functions of the development method described in the various embodiments of this specification.

[0090] The computer-readable medium in the present invention may be a computer-readable signal medium, a computer-readable storage medium, or any combination of the above two. A computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present invention, a computer-readable storage medium may be any tangible medium that contains or stores a program, and this program can be used by or combined with an instruction execution system, apparatus, or device.

[0091] In the present invention, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries computer-readable program code. Such a propagated data signal may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. The computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium may be transmitted by any appropriate medium, including but not limited to: wireless, wire, optical fiber cable, RF, etc., or any suitable combination of the above.

[0092] Those skilled in the art will appreciate that the embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0093] The present invention is described with reference to the flowcharts and / or block diagrams of methods, apparatuses, systems, and computer program products according to embodiments of the present invention. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and combinations of flows and / or blocks in the flowcharts and / or block diagrams, can be realized by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to produce a machine, such that the instructions executed by the processor of the computer or other programmable data processing devices generate means for realizing the functions specified in one Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.

[0094] For those skilled in the art, it is obvious that the present invention is not limited to the details of the above-described exemplary embodiments, and can be implemented in other specific forms without departing from the spirit or essential characteristics of the present invention. Therefore, in any aspect, the embodiments should be regarded as exemplary and non-limiting. The scope of the present invention is defined by the appended claims rather than the above description. Therefore, all changes falling within the meaning and scope of the equivalent elements of the claims are intended to be included in the present invention. Any reference signs in the claims should not be construed as limiting the claims involved.

[0095] In addition, it should be understood that although this specification is described in terms of embodiments, not every embodiment contains only one independent technical solution. This narrative manner of the specification is only for clarity. Those skilled in the art should regard the specification as a whole, and the technical solutions in each embodiment can also be appropriately combined to form other embodiments that can be understood by those skilled in the art.

Claims

1. A zero-code development platform, characterized in that: include: Data protocol layer, used to manage and access industrial control protocols and database systems; The device layer is connected to the data protocol layer and is used to access hardware resources and abstract and manage the hardware resources; An operator and module library, connected to the device layer, for providing callable function operators, resource component operators and HMI modules; The business logic layer is connected to the operator and module library, and is used to call the function operator, resource component operator and HMI module in the operator and module library through the designer to build the business task process in a graphical manner; The application layer is connected to the business logic layer and is used to provide an operating environment for the business task process and run the business task process; Wherein, the designer includes a resource manager, a business generation manager and an HMI interface generation manager, and the HMI interface generation manager includes an HMI human-computer interaction designer, an HMI property configurator, an event manager and an HMI system manager; The resource manager includes a first canvas interaction designer and a component property configurator; the first canvas interaction designer is used to call the resource component operator in the operator and module library to create a resource component object on the canvas interface; the component property configurator is used to configure parameters of the resource component object; The business generation manager includes a second canvas interaction designer and an operator attribute configurator; the second canvas interaction designer is used to call the operator and the function operator in the module library to create a function operator object on the canvas interface, and the function operator object can call the output data of the resource component object; the operator attribute configurator is used to configure parameters of the function operator object; The HMI human-machine interaction designer is used to call the HMI modules in the operator and module library to create an HMI object on the design interface. The HMI object can call and respond to the output data of the resource component object and the function operator object. The resource component object can adjust parameters in response to the output data of the HMI object, and the function operator object can respond to the interactive command of the HMI object; the HMI attribute configurator is used to configure parameters of the HMI object; the event manager is used to bind, delete, query or modify the events of the HMI object; the HMI system manager is used to perform visualization management, window management and data persistence on the HMI object.

2. The zero-code development platform according to claim 1, characterized in that: The operator and module library includes an industry solution library, which stores industry solution task process templates under preset scenarios.

3. The zero-code development platform according to claim 1, characterized in that: The application layer includes an execution engine, and the execution engine is used to call the designer of the business logic layer to manage and execute the business task process.

4. The zero-code development platform according to claim 1, characterized in that: The zero-code development platform also includes a task flow debugger, which is used to debug the business task flow; and / or The zero-code development platform further includes a publishing generator, which is used to publish the business task process and generate an executable program file; and / or The zero-code development platform also includes a document generator, which is used to generate and manage parameter description documents and interface description documents for each operator and module in the operator and module library.

5. A development method based on the zero-code development platform according to any one of claims 1 to 4, characterized in that: include: In response to user instructions, the designer of the business logic layer calls the function operators, resource component operators and HMI modules in the operator and module library; In response to user instructions, in the design interface of the designer, the attributes, parameters, reference relationships and logical connection relationships of the called object module are configured to construct the business task process in a graphical manner; The business task process is run based on the operating environment provided by the application layer.

6. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the development method according to claim 5 is implemented.

7. A computer-readable medium, characterized in that The computer-readable medium carries computer-executable instructions, and when the computer-executable instructions are executed by a processor, they are used to implement the development method according to claim 5.

Images