Zero code development platform, development method, electronic equipment and medium

Abstract

The invention discloses a zero-code development platform and method, electronic equipment and a medium, and belongs to the field of software development. The zero code development platform comprises a data protocol layer, an equipment layer, an operator and module library, a business logic layer and an application layer, the data protocol layer manages an industrial control protocol and a database system; the equipment layer accesses and manages hardware resources; the operator and module library provides a function operator, a resource component operator and an HMI module for calling; the business logic layer calls operators and modules in a module library in a graphical mode through a designer to construct a business task process; and the application layer provides a running environment for the business process and executes the process. According to the zero-code development platform, the development method, the electronic equipment and the medium provided by the invention, efficient development and management of complex industrial automation applications can be realized through a multi-layer architecture design, the overall performance of a system and the development experience of a user are improved, the development process is simplified, and the development period is shortened.

Description

Technical Field

[0001] The present invention belongs to the technical field of software development, and in particular 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 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 high degree of customization of equipment and production lines, the existing industrial control software development often faces the following major problems: Non-standard automation equipment needs to be customized according to user needs, and the software needs to be highly compatible with specific hardware devices, involving a lot of code writing and debugging. Especially when it comes to multi-field technology integration (such as PLC programming, visual algorithms, motion control, etc.), developers need to spend a lot of time developing and optimizing different modules, resulting in low overall development efficiency.

[0003] Traditional development methods usually require developers to be proficient in multiple programming languages ​​and technical frameworks, such as C++, Python, PLC Adder 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 equipment (such as PLC, cameras, sensors), which places high demands on the professional capabilities of developers. For enterprises, it is extremely costly to cultivate compound talents who are familiar with both programming and industrial field applications, and resources are scarce.

[0004] The development process of non-standard automation software is usually tailored to specific needs, which makes it difficult to quickly adjust and implement functional expansion or module upgrades to meet new needs after development is completed.

[0005] Therefore, it is necessary to provide a new solution to the above technical problems. Summary of the invention

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

[0007] To achieve the above purpose, the technical solution provided by the present invention is as follows: 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 for accessing hardware resources and abstracting and managing the hardware resources; the operator and module library is connected to the device layer for providing callable functional operators, resource component operators and HMI modules; the business logic layer is connected to the operator and module library for calling the functional 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 for providing an operating environment for the business task process and running the business task process.

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

[0009] In one or more embodiments, the designer includes a resource manager, which 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.

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

[0011] In one or more embodiments, the designer further includes an HMI interface generation manager, which includes an HMI human-machine interaction designer, an HMI property configurator, an event manager, and an HMI system manager; the HMI human-machine interaction designer is used to call the HMI module 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 property configurator is used to configure parameters of the HMI object; the event manager is used to bind, delete or modify events of the HMI object; the HMI system manager is used to perform visualization management, window management and data persistence on the HMI object.

[0012] In one or more implementations, 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.

[0013] In one or more embodiments, 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 also includes a release generator, which is used to publish the business task flow 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.

[0014] In a second aspect, the present invention provides a development method based on the aforementioned zero-code development platform, which comprises: In response to user instructions, the designer of the business logic layer calls the operator and the function operator, resource component operator and HMI module in the 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; based on the operating environment provided by the application layer, the business task process is run.

[0015] In a third aspect, the present invention provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the development method as described above when executing the program.

[0016] In a fourth aspect, the present invention provides a computer-readable medium, wherein the computer-readable medium carries computer-executable instructions, and the computer-executable instructions are used to implement the development method as described above when executed by a processor.

[0017] Compared with the prior art, the zero-code development platform, development method, electronic device and medium provided by the present invention can realize efficient development and management of complex industrial automation applications through multi-level architecture design, improve the overall performance of the system and the user's development experience, simplify the development process, and shorten the development cycle; it also enhances the flexibility and scalability of the system through modular and visual design, lowers the technical threshold, and provides efficient, convenient and reliable development solutions for the field of industrial automation. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the prior art descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present invention, and for ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0019] Figure 1 This is an architecture diagram of a zero-code development platform in one embodiment of the present invention; Figure 2 It is a module block diagram of a zero-code development platform in one embodiment of the present invention; Figure 3 This is an interface diagram of a resource manager in one embodiment of the present invention; Figure 4 This is an interface diagram of a service generation manager in one embodiment of the present invention; Figure 5 An interface diagram of an HMI interface generation manager in one embodiment of the present invention; Figure 6 It is a flow chart of a development method based on a zero-code development platform in one embodiment of the present invention; Figure 7 FIG. 4 is a structural block diagram of an electronic device in an embodiment of the present invention. DETAILED DESCRIPTION

[0020] In order to enable those skilled in the art to better understand the technical solutions in the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0021] With the rapid development of industrial automation technology, especially in the field of non-standard automation, traditional software development methods are facing a series of challenges. In existing technologies, the development process of industrial automation software usually relies on complex programming work, which not only requires developers to have deep programming skills and a deep understanding of industrial protocols, but also leads to long software development cycles, high development costs, and difficult customization and upgrades. In addition, the requirements of industrial automation projects are often highly personalized and changeable, which makes the software less reusable and unable to effectively respond to changing market demands and application scenarios.

[0022] In this context, the inventors realized that the existing development model is too dependent on traditional programming and manual coding, with a long development cycle and difficult maintenance. Therefore, a new approach is urgently needed to simplify the development process, improve efficiency, lower the development threshold, and 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, which aims to provide a convenient, efficient and flexible software development solution for the non-standard automation industry.

[0023] The core of the technical implementation idea of ​​the present invention is to build a zero-code development platform so that developers can complete complex software development tasks through a graphical interface without writing code. The 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.

[0024] The architecture of the platform includes multiple layers, among which the data protocol layer and the device layer provide the underlying hardware resource access and protocol management functions for the system; 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, which organizes and builds business logic through a graphical designer and effectively combines and connects different component modules; the application layer is the final operating environment, which supports the execution and monitoring of the designed business processes. Through this architecture, users can flexibly design, modify and debug their own business task processes without involving code writing.

[0025] Specifically, the present invention provides flexible customization support by designing modular operator libraries and business process building tools, so that users can 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 hardware resource management, algorithm configuration and human-computer interface design through visual operations.

[0026] The technical implementation ideas of the present invention not only break through the complexity and technical barriers existing in traditional automation software development, but also greatly reduce the technical threshold for developers through the simplified design of the graphical interface. Developers can quickly build and customize automation systems that meet 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 upgrades more flexible and convenient.

[0027] Please refer to Figure 1 FIG. 1 is an architecture diagram of a 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.

[0028] 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 to access hardware resources and abstract and manage the hardware resources. The operator and module library is connected to the device layer to provide callable functional operators, resource component operators and HMI modules. The business logic layer is connected to the operator and module library to call the functional operators, resource component operators and HMI modules in the operator and module library through the designer to build business task processes in a graphical manner. The application layer is connected to the business logic layer to provide the operating environment of the business task process and run the business task process.

[0029] As the bottom layer of the platform, the data protocol layer is responsible for 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 processing the conversion of different data protocols and the efficient transmission of information.

[0030] In industrial automation systems, various devices and database systems often use different protocols for data exchange. 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 of the data protocol layer is 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 achieve efficient docking with a variety of hardware and systems.

[0031] In terms of design, the data protocol layer provides a set of common 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 such as SQL and NoSQL, the data protocol layer can flexibly handle 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.

[0032] The device layer is connected to the data protocol layer and is used for 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 foundation for realizing control and monitoring functions, but devices from different manufacturers usually use 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 consistent hardware resource management capabilities for the upper-level logic.

[0033] The design of the device layer is based on the principles of modularization and abstraction. First, it connects to the hardware resources supported by various industrial protocols through the connection with the data protocol layer. The device layer standardizes these resources and converts the complex underlying hardware interface into a unified device object. These device objects not only encapsulate the communication logic required to interact with the hardware, but also provide unified properties, operation methods, and status information interfaces, which are convenient for users to call and manage in business processes. Through this abstraction, the platform can shield hardware differences, so that developers do not need to pay attention to specific hardware features and underlying implementation details when using the device, thereby reducing development complexity.

[0034] The device layer can also realize dynamic management functions for hardware resources, including automatic discovery of resources, configuration initialization, status monitoring and real-time operation. Users can easily complete hardware registration and management through the device layer, and intuitively call related resources in the designer. For example, users can access sensors through the device layer for real-time data collection or control PLC to perform actions. The dynamic management capabilities of the device layer enable users to flexibly adapt to a variety of hardware environments, while supporting online addition and removal of devices, enhancing the flexibility and scalability of the platform.

[0035] The operator and module library is a key module for implementing core functions in the zero-code development platform. It is connected to the device layer and provides platform users with a wealth of callable functions, including functional operators, resource component operators, and HMI (human-machine interface) modules. Through this operator and module library, developers can call packaged functional components with minimal technical investment, thereby quickly completing the construction and implementation of complex industrial automation tasks. Its design aims to abstract the complex underlying technical logic 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.

[0036] The design of operators and module libraries is based on the concept of high modularity, abstracting and encapsulating common industrial control functions, algorithm logic, resource management operations, and human-computer interaction interface components. Operators in the module library are designed as standardized units, containing reusable interfaces, property configuration options, and input and output parameter structures. Users can call these operators through configuration without writing underlying code. For example, functional 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 device-level resources, such as sensor data reading, device status control, etc.; the HMI module provides functional components for designing and managing human-machine interfaces, 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-level human-computer interactions.

[0037] In an exemplary embodiment, the operator and module library includes an industry solution library, which stores industry solution task process templates under preset scenarios. By storing industry solution task process templates under preset scenarios, users are provided with ready-to-use functional modules and business processes. The industry solution library abstracts and standardizes typical task requirements in complex industrial applications to form process templates suitable for specific scenarios. These templates contain both common functional logic in the industry and algorithm configurations and process settings optimized based on actual needs.

[0038] In terms of design, the industry solution library breaks down complex business processes into reusable modules and combines the best practices of 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.

[0039] The role of the industry solution library in the platform is reflected in significantly reducing development time costs, enhancing solution reusability, and improving user development experience. It provides users with ready-to-use functional processes and greatly shortens the development cycle. Users do not need to build the entire task logic from scratch. They only need to call templates and adapt the scenarios to quickly implement complex functional requirements. The templated design greatly improves the reusability of the process. Similar application scenarios in the industry can directly call existing templates without repeated design and debugging.

[0040] Please refer to Figure 2 As shown in the figure, 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, allowing users to call the function operators, resource component operators and HMI modules in the operator and module library to quickly build business task processes in a graphical way. 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 to quickly implement complex industrial automation logic.

[0041] In terms of design, the business logic layer presents various predefined functional modules (including functional operators, resource component operators and HMI modules) to users in a visual way by collaborating with operators and module libraries. Users can drag these modules in the canvas through the designer's graphical interface and combine them into specific business logic processes. These modules can be functional operators for data processing (such as 2D visual 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 in series by configuring interfaces and logical connections to form a complete task flow.

[0042] The business logic layer not only supports the dragging and combination of modules, but also allows users to set the behavior of each module in detail through the property panel and parameter configuration function. For example, users can set operating parameters for function 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 branches, and developers can flexibly define and manage multi-level process structures in complex business scenarios.

[0043] In the process of function realization, the business logic layer also considers data flow and event-driven mechanism. The output data of each module can be passed to the next module through the logical connection line, realizing the seamless flow of data in the process. At the same time, the business logic layer supports the event-driven logic trigger mechanism. Users can define specific event conditions to trigger the operation of certain modules, thereby realizing dynamic control of task processes. This design greatly improves the flexibility of process logic, enabling users to build more real-time and responsive automation systems.

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

[0045] In addition, the business logic layer also provides convenience for team collaboration. Through its intuitive process design and modular functional 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 the module. This collaborative approach not only improves the efficiency of project development, but also ensures that the final system can better meet actual application requirements. The business logic layer also supports docking with third-party systems or platforms, such as OPencv, Halcon, Labview, VisionPro, etc.

[0046] 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 operator and the resource component operator in the module library to create a resource component object on the canvas interface; the component property configurator is used to perform parameter configuration on the resource component object.

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

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

[0049] The component property configurator is a supporting module of the First Canvas Interactive Designer, which is used to configure the parameters of the created resource component objects. Each resource component object contains a set of predefined properties. The component property configurator provides an intuitive interface where 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 operating parameters according to actual needs to ensure the optimal performance of resource components.

[0050] For details, please refer to Figure 4 As shown, the designer also includes a business generation manager, which includes a second canvas interaction designer and an algorithm property configurator; the second canvas interaction designer is used to call the operator and the functional operator in the module library to create a functional operator object on the canvas interface, and the functional operator object can call the output data of the resource component object; the algorithm property configurator is used to configure parameters of the functional operator object.

[0051] The Business Generation Manager provides users with an intuitive graphical development environment for the design of business logic and the implementation of algorithm processes through the collaborative work of the Second Canvas Interactive Designer and the Algorithm Property Configurator.

[0052] The second canvas interactive designer provides users with an interactive graphical canvas for calling operators and functional operators in the 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 in appropriate locations on the canvas with simple drag and drop operations. The creation of functional operator objects is not just a simple call of operator functions, it also achieves seamless integration with resource component objects, and can directly use the output data of resource component objects to complete the closed-loop design from data collection to algorithm processing. In this way, users can easily design complex industrial logic such as visual algorithms, data analysis, path planning, etc. without having to pay attention to the underlying code implementation.

[0053] The algorithm property configurator is used to accurately configure the parameters of the function operator object. Each function operator object has a set of adjustable properties. The algorithm property configurator provides an intuitive interface, and users can adjust the parameter settings to meet different business needs. For example, in an image processing algorithm, users can set the edge detection threshold, image resolution and other parameters through the algorithm property configurator; in the data analysis process, users can set the type of statistical model or the threshold range of the calculation indicator. 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 visual feedback, thereby improving the efficiency of process debugging.

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

[0055] For further information, please refer to Figure 5As shown, the designer also 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 module 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 respond to the output data of the HMI object to adjust parameters, and the function operator object can respond to the interactive command of the HMI object; the HMI property configurator is used to configure parameters of the HMI object; the event manager is used to bind, delete 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.

[0056] The HMI interface generation manager is a module used for human-machine interaction interface design and management in the zero-code development platform. Its core consists of the HMI human-machine interaction designer, HMI attribute configuration manager, event manager and HMI system manager. Through modular design and visual operation, this module provides users with an efficient and flexible interface construction method, enabling users to quickly design and manage complex interaction interfaces, thereby achieving the connection between human-machine interaction and business logic.

[0057] The HMI human-machine interaction designer is the core part of this module. It is 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, input boxes, etc. 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 functional 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 operating parameters of an actuator through a slider. Through this two-way data interaction mechanism, the HMI object is both a terminal for information display and an entry point for business operations.

[0058] The HMI property configuration manager provides parameter configuration functions for each HMI object. Users can use the property configuration interface to set detailed settings for the appearance (such as color, size, font) and behavior (such as data binding method, interactive response rules) of the object. For example, you can set the data refresh frequency for a chart component and define the feedback action after pressing a button component. This flexible configuration method not only enhances the freedom of interface design, but also ensures that the HMI object can accurately meet business needs.

[0059] 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 the HMI object. Users can use the event manager to define the trigger conditions and response logic of each component, such as starting an algorithm when a button is clicked, and issuing an alarm 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.

[0060] The HMI system manager is responsible for overall management of interface components, including visualization management, window management, and data persistence. Visual management allows users to intuitively adjust the interface layout and component hierarchy, while window management supports multi-interface switching and dynamic window generation. The data persistence function ensures that the user-configured interface layout, attributes, and logic can be saved and reused, making it easy to call in subsequent development or system upgrades. This overall management capability not only improves the efficiency of interface design, but also enhances the maintainability of the system.

[0061] Through the collaboration of various sub-modules, the HMI interface generation manager provides users with all-round support from interface layout to logic design, significantly reducing the complexity of human-computer interaction interface development, allowing users to focus on function implementation without having to worry about underlying technical details. In addition, through the connection with the resource manager and business generation manager, the module realizes the deep integration of business processes and user interfaces, ensuring the consistency between information display, user operations and background logic.

[0062] The application layer is responsible for providing an operating environment for business task processes and ensuring that the task processes 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 business task processes.

[0063] The design of the application layer fully considers the complex needs of industrial automation applications. Through a flexible task scheduling mechanism and an efficient execution engine, the task process 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 flowchart and algorithm call logic 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 data flows and event triggers, and ensure the efficient operation of business processes in a variety of 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 equipment based on the inspection results.

[0064] The application layer not only provides the operating environment, but also has the ability to manage and monitor tasks. During the task operation, 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 task process (such as device offline or data abnormality), the application layer can promptly terminate the current task or start a predefined emergency process to improve the reliability and fault tolerance of the system. Users can also use the logging function of the application layer to trace back the detailed process of task operation, so as to quickly locate problems and optimize process design.

[0065] In addition, the task scheduling mechanism of the application layer enables multiple task processes to run in parallel or sequentially, thus meeting the needs of multi-tasking in complex scenarios. Users can customize the scheduling order and operation strategy of tasks according to business priorities and resource allocation, such as setting high-priority tasks to preempt resources or executing different task processes by time period. Through this flexible scheduling method, the application layer can maximize the use of system resources and improve the overall operation efficiency of the platform.

[0066] The role of the application layer is also reflected in the feedback and visual display of task operation results. After the operation is completed, the application layer further processes the data output by the business logic layer and displays it to the user through the HMI interface. For example, the application layer can present real-time production data, test results or operation status in the form of charts or reports to help users intuitively understand the working status of the system. This closed-loop feedback mechanism not only improves the ease of use of the system, but also provides users with a basis for further optimizing task processes.

[0067] In an exemplary embodiment, 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 also includes a release generator, which is used to publish the business task flow 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.

[0068] The task flow debugger is an important tool for debugging in the platform. It can help users discover and solve potential problems before the business task flow is executed. The design of the debugger provides a wealth of debugging functions, including breakpoint setting, single-step execution, variable monitoring, and error logging. Users can set breakpoints at key nodes in the task flow and gradually check the operating status and data flow of each operator or module to quickly locate the cause of the problem. For example, when debugging a task flow that includes sensor data acquisition, data cleaning, and visual inspection, users can set breakpoints 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, which intuitively presents warnings and error information in the process execution to users, thereby greatly reducing the difficulty of troubleshooting and solving problems.

[0069] The release generator is a module for the platform to deliver business results. Its function is to package the business task processes completed by users into executable program files. The release generator converts the development results into a complete and independent executable file by integrating information such as task logic, operator calls, and resource configuration, which makes it easy to deploy the development results to the target system for operation. For example, the production line monitoring and control tasks designed by users can be generated into running programs with one click through the release generator, and deployed to industrial computers or servers, so as to achieve rapid application and production at industrial sites. The design of the release generator emphasizes automation and compatibility, and supports the generation of program files that are compatible with multiple operating environments (such as Windows, Linux), ensuring that the task process can run stably on different hardware platforms.

[0070] The document generator provides the platform with comprehensive document management capabilities. 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 the traditional development process, document writing is often a time-consuming and easily overlooked link. The document generator automatically parses the operators and module libraries to generate standardized description documents, including detailed information such as the purpose of each operator, parameter configuration methods, input and output interfaces, etc. These documents not only make it easier for developers to understand and use operators, but also provide support for subsequent maintenance, upgrades, and collaboration. For example, in team development, developers in different roles can quickly understand the module functions and configuration requirements used in the task process by consulting the documents, thereby improving collaboration efficiency.

[0071] Please refer to Figure 6 FIG. 1 is a flow chart of a development method based on the aforementioned zero-code development platform in one embodiment of the present invention. The development method specifically includes the following steps: S601: In response to a user instruction, the designer of the business logic layer calls the function operator, resource component operator and HMI module in the operator and module library.

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

[0073] S602: 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 a business task process in a graphical manner.

[0074] Users can configure the properties, parameters, reference relationships, and logical connection relationships of the called modules in the designer interface to build business task processes in a graphical way. The key to this step is to give users the ability to flexibly define and optimize business logic through a graphical interface. Users can use the property configuration interface to refine the behavior of the module, such as adjusting the threshold of the function 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 build dynamic data flows and event triggering mechanisms. The configuration process is completely intuitive, and users can clearly see the overall structure of the process and the data transfer logic.

[0075] S603: Run the business task process based on the operating environment provided by the application layer.

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

[0077] Please refer to Figure 7As shown, 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 the 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 used 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 various embodiments of this specification.

[0078] In the embodiments of the present 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 the like.

[0079] An embodiment of the present invention further provides a computer-readable medium carrying computer-executable instructions. 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 various embodiments of this specification.

[0080] The computer-readable medium in the present invention can be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium can be, for example, but not limited to, a system, device or component of electricity, magnetism, light, electromagnetic, infrared, or semiconductor, or any combination of the above. More specific examples of computer-readable storage media can 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 can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it.

[0081] 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 a computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, device, or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0082] It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, 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.

[0083] The present invention is described with reference to 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 process and / or block in the flowchart and / or block diagram, as well as a combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the process in the flowchart. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0084] It will be apparent to those skilled in the art that the invention is not limited to the details of the exemplary embodiments described above and that the invention can be implemented in other specific forms without departing from the spirit or essential features of the invention. Therefore, the embodiments should be considered exemplary and non-limiting in all respects, and the scope of the invention is defined by the appended claims rather than the foregoing description, and it is intended that all variations falling within the meaning and scope of the equivalent elements of the claims be included in the invention. Any reference numeral in a claim should not be considered as limiting the claim to which it relates.

[0085] In addition, it should be understood that although the present specification is described according to implementation modes, not every implementation mode contains only one independent technical solution. This description of the specification is only for the sake of clarity. Those skilled in the art should regard the specification as a whole. The technical solutions in each embodiment may also be appropriately combined to form other implementation modes 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.

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 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 operator in the operator and module library to create a resource component object on the canvas interface; The component property configurator is used to perform parameter configuration on the resource component object.

4. The zero-code development platform according to claim 3, characterized in that: The designer further includes a service generation manager, and the service generation manager includes a second canvas interaction designer and an operator attribute configurator; The second canvas interaction designer is used to call the functional operator in the operator and module library to create a functional operator object on the canvas interface, and the functional operator object can call the output data of the resource component object; The operator attribute configurator is used to configure parameters of the functional operator object.

5. The zero-code development platform according to claim 4, characterized in that: The designer also includes an HMI interface generation manager, which includes an HMI human-computer interaction designer, an HMI property configurator, an event manager, and an HMI system manager; The HMI human-machine interaction designer is used to call the HMI module 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 respond to the output data of the HMI object to adjust parameters, and the function operator object can respond to the interaction command of the HMI object; The HMI attribute configurator is used to perform parameter configuration on 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.

6. 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.

7. 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.

8. A development method based on the zero-code development platform according to any one of claims 1 to 7, 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.

9. 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 8 is implemented.

10. 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 8.

Images