Mechanical arm task execution method based on low code configuration
Through the low-code configuration method, the problems of long development cycle, high cost and high technical requirements of traditional robotic arm task execution methods are solved, and the flexible and dynamic execution of tasks is achieved, and the production efficiency and system stability are improved.
Patent Information
- Application Number
- CN202411207924.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-30
- Publication Date
- 2024-11-08
- Estimated Expiration
- 2044-08-30
AI Technical Summary
Traditional robotic arm task execution methods rely on professional programming, have long development cycles and high costs, high technical requirements for operators, and are difficult to adapt to rapidly changing production environments, and performance and stability may be affected in large-scale and high-concurrency scenarios.
Using the low-code configuration method, we can realize the flexible and dynamic execution of robotic arm tasks by defining state modules, creating low-code task configuration files, building task tree structures, analyzing and storing task configuration sequences, and support the hierarchical and modular design of tasks. , reduce programming skills requirements, improve task configuration efficiency and maintainability.
It reduces the requirements for programming skills, improves task configuration efficiency and flexibility, supports dynamic task execution, quickly adapts to changes in the production environment, and improves production efficiency and system stability and reliability.
Smart Images

Figure CN118906061A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of mechanical automation control, and specifically to a robot arm task execution method based on low-code configuration. Background Art
[0002] With the development of industrial automation and intelligent manufacturing, robotic arms have been widely used in many fields such as manufacturing, logistics and warehousing, and medical health. Traditional robotic arm task execution methods usually rely on professional programmers to use complex programming languages to write control codes. This method not only has a long development cycle and high cost, but also has high technical requirements for operators, which limits the popularity and application of robotic arms.
[0003] Traditional robotic arm task execution solutions mainly rely on professional programmers to use complex programming languages to write control codes. The advantage of this method is that it can achieve highly customized task execution logic to meet complex and changing industrial needs. However, its disadvantages are also very obvious: long development cycle, high cost, and high technical requirements for operators, which limit the popularity and application of robotic arms. In addition, traditional programming methods are difficult to adapt to the rapidly changing production environment and difficult to achieve rapid iteration and update.
[0004] Existing technical solutions, such as the robotic arm task execution method based on graphical programming, reduce the programming difficulty by providing a visual programming interface, so that non-professionals can also perform simple task configuration. However, such solutions often have functional limitations and are difficult to meet the needs of complex tasks. In addition, when dealing with large-scale, high-concurrency scenarios, performance and stability may be affected.
[0005] This technical solution aims to address the shortcomings of the existing technology by introducing a low-code configuration method for executing robotic arm tasks. First, the low-code configuration file makes task configuration more intuitive and simple, reduces the requirements for programming skills, and improves the efficiency of task configuration. Secondly, by organizing tasks into a tree structure, this solution can better manage complex task logic, support the hierarchical and modular design of tasks, and improve the maintainability and scalability of tasks. Finally, this solution controls the action sequence of the robotic arm by parsing the configuration file, making task execution more flexible and dynamic, able to quickly adapt to changes in the production environment, and improve production efficiency and flexibility. Summary of the invention
[0006] A method for executing a robotic arm task based on low-code configuration includes the following steps:
[0007] S1. Define a state module, which includes the position, posture, kinematic properties, path planning constraints, and state sequences of peripheral operations and abnormal logic processing of the position and posture of the robot terminal TCP;
[0008] S2. Create a low-code task configuration file, where the configuration file is stored in YAML format or JSON format to represent the hierarchical relationship between items at different levels;
[0009] S3, constructing a task tree structure, wherein the structure includes a task array or list, subtasks, a state module and its attributes, and uses a tree structure to organize task configuration;
[0010] S4. Define data structure and node type, parse and store tree-shaped task configuration sequences organized by low code, and convert text-based task configurations into data structures that can be processed by programs;
[0011] S5. Parse the low-code task configuration file, and read the task tree structure configuration in the YAML format or the JSON format into the data structure. The data structure also satisfies the tree topology structure, so that each node of the task sequence can be traversed when the software is executed.
[0012] S6. Execute the task tree data structure, traverse each node in the task tree data structure, and cooperate with the robot arm driver to implement the task execution operation of the robot arm according to the state module and attributes defined by each node.
[0013] Preferably, the state module specifically includes: velocity and acceleration, joint coordinate system path and Cartesian coordinate system path, peripheral operation before execution, peripheral operation after execution, time interval after execution, state sequence of abnormal logic processing;
[0014] The speed and acceleration are used to define the speed and acceleration of the robot arm moving to the position or posture;
[0015] The joint coordinate system path and the Cartesian coordinate system path are used to plan the movement path of the robotic arm;
[0016] The pre-execution peripheral operation is used to start the peripheral operation before executing the path point. The peripheral operation includes but is not limited to switch operation, trigger type operation and custom IO type operation. The peripheral operation also defines the number of attempts after the operation fails, the delay time before and after the operation is executed, the state value of the switch and the specific attributes of the IO type operation;
[0017] The post-execution peripheral operation is a peripheral operation after the execution of the path point is completed. The peripheral operation also includes switch operation, trigger type operation and custom IO type operation. The peripheral operation also defines the number of attempts after the operation fails, the delay time before and after the operation is executed, the state value of the switch and the specific attributes of the IO type operation;
[0018] The post-execution time interval uses the time interval after the path is executed, and defines the waiting time after the path point is executed;
[0019] The state sequence of the abnormal logic processing is a state sequence for executing the abnormal logic processing after the state fails, and jumps to other state modules through goto to perform recovery operations. The goto jump defines the maximum number of execution attempts after the exception occurs.
[0020] Preferably, the low-code task configuration file in S2 is stored in YAML format or JSON format, the YAML format storage uses indentation to represent the hierarchical relationship between entries of different levels; the JSON format storage uses "{}" to enclose to represent the hierarchical relationship between entries of different levels; the YAML format storage and JSON format storage support vector data type and map data type; the vector data type is array data; the map data type is hash data with unique keywords.
[0021] Preferably, the task tree structure in S3 is defined by a low-code task configuration file, and the task tree structure consists of a parent node corresponding to multiple child nodes, and the child nodes are sequentially combined in the form of an array or list, and the sequential combination is: parent node>child node array or list>child node attribute array or list.
[0022] Preferably, the task tree configuration in S3 specifically includes:
[0023] The task tree configuration defines three basic node structures: top parent node, middle node and bottom node;
[0024] The top parent node is "arm task" which is the root node of the task tree;
[0025] The middle layer node is an array or list of "tasks" child nodes, which is a series of task nodes, and each task node is represented by "name";
[0026] The bottom layer node is a "poses" array or list, each "poses" node corresponds to a "name" node and contains a series of "pose" nodes; each child node "pose" in the "poses" array or list represents a state module; various attributes and peripheral operations of the state module are defined in the form of child nodes;
[0027] The task tree configuration defines two node types: "necessary" and "optional", where necessary nodes must exist and have corresponding information set, while optional nodes are omitted based on actual needs and default values are used.
[0028] Preferably, the S4 data structure specifically includes: vector data type and regular data type:
[0029] The vector data type uses square brackets "[]" to enclose the data, and commas "," are used to separate the data.
[0030] The conventional data type is Byte data, and the data type includes decimal / hexadecimal data or character string data.
[0031] Preferably, the S4 node types specifically include task nodes and status nodes:
[0032] The task node belongs to the array or list "tasks", and the child node with the keyword "name" is the start of a new task. At the same time, the task node contains the array or list "poses" of state nodes as a child node, and the child nodes "name" and "poses" are peer child nodes;
[0033] The state node defines the TCP end position and posture of each path point in the robot arm execution path, as well as its attributes and operations that need to interact with the periphery; the state node includes necessary "pose" nodes, peripheral operation nodes and other optional nodes.
[0034] Preferably, the peripheral operation node is a type before starting to execute the state node to which it belongs, and a type after completing the execution of the state node to which it belongs. The node structure, attributes, and sub-node definitions of the two types are exactly the same, and the difference lies in the time point when they are executed; three standard subclasses are defined in the two types of sub-nodes: bool switch type, trigger type, and IO type.
[0035] Preferably, the S5 parses the low-code task configuration file by parsing the configuration file in YAML format or JSON format to build a tree structure of the task. Each task node may contain one or more sub-task nodes, converting the task tree into a data structure. Each task node has a unique identifier, status, and sub-task list. The complete parsing structure is constructed through recursive processing to guide the robotic arm to perform tasks in a predefined order. It supports dynamic adjustment of the task execution order or conditional skipping of certain tasks, thereby improving the clarity, maintainability and scalability of task management.
[0036] Preferably, the S6 execution task tree data structure traverses each node in the task tree data structure, and calls the corresponding robotic arm driver to perform operations according to the status and attributes of each node; uses a recursive algorithm to process each task node and its subtask nodes to ensure that all subtasks are executed in a predefined order; the execution task tree data structure supports dynamic adjustment of task execution order and real-time update of task status, allowing dynamic modification of task parameters or status during execution to adapt to environmental changes or changes in task requirements.
[0037] The present invention defines the tasks of the robot arm through the YAML format or JSON format of the low-code configuration file. These files are easy to write and understand, reducing the requirements for programming skills, so that non-professionals can also perform task configuration. This solves the problem that traditional programming methods have high technical requirements for operators and improves the efficiency of task configuration.
[0038] The present invention organizes tasks into a tree structure, and each task node can contain subtasks to form a hierarchical task structure. This structured method makes task management clearer, supports the hierarchical and modular design of tasks, and improves the maintainability and scalability of tasks. In addition, by defining the task tree structure and configuration, automatic control and intelligent decision-making can be achieved, and work efficiency and accuracy can be improved.
[0039] The present invention controls the action sequence of the robot arm by parsing the configuration file, making the task execution more flexible and dynamic. The control system can execute each subtask in sequence according to the task tree structure and configuration in the task configuration file until the entire task is completed. This dynamic task execution method can quickly adapt to changes in the production environment and improve production efficiency and flexibility.
[0040] The present invention introduces an exception handling mechanism during the task execution process. When an abnormal situation occurs during the task execution process, the system can automatically identify and take corresponding processing measures, such as pausing the task, retrying the task, or skipping the abnormal task. This exception handling mechanism improves the stability and reliability of the system and reduces production interruptions and losses caused by abnormal situations.
[0041] The present invention makes the structure and content of the task configuration file more standardized and unified through the data format and node type of the task configuration file. By defining the data format and node type, a task configuration file that meets the requirements of the task tree structure can be constructed, so that the control system can correctly parse and execute these tasks. This standardized data format and node type definition improves the accuracy and consistency of task configuration and reduces system failures and production delays caused by configuration errors.
[0042] The above description is only an overview of the technical solution of the present application. In order to more clearly understand the technical means of the present application so that it can be implemented in accordance with the contents of the specification, and to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the following is a detailed description of the preferred embodiments of the present application in conjunction with the accompanying drawings as follows.
[0043] Based on the detailed description of the specific embodiments of the present application in combination with the accompanying drawings below, those skilled in the art will become more aware of the above and other objects, advantages and features of the present application. BRIEF DESCRIPTION OF THE DRAWINGS
[0044] In order to more clearly illustrate the technical solutions in the embodiments of the present application or 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 some embodiments of the present application. For ordinary technicians in this field, other drawings can also be obtained based on these drawings without creative work. In all drawings, similar elements or parts are generally identified by similar reference numerals. In the drawings, each element or part is not necessarily drawn according to the actual scale.
[0045] Figure 1 Robotic arm task execution flow chart configured for low code;
[0046] Figure 2 Flowchart of robot task parsing configured for low code;
[0047] Figure 3 Implementation flowchart for robotic arm configured for low code;
[0048] Figure 4 It is a task tree structure diagram. Specific embodiments
[0049] To make the purpose, technical scheme and advantages of the embodiment of the present application clearer, the technical scheme in the embodiment of the present application will be clearly and completely described below in conjunction with the accompanying drawings in the embodiment of the present application. Obviously, the described embodiment is a part of the embodiment of the present application, rather than all of the embodiments. In the following description, specific details such as specific configuration and components are provided only to help fully understand the embodiments of the present application. Therefore, it should be clear to those skilled in the art that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present application. In addition, for clarity and brevity, the description of known functions and structures is omitted in the embodiment.
[0050] It should be understood that the references to "one embodiment" or "this embodiment" throughout the specification mean that the specific features, structures, or characteristics associated with the embodiment are included in at least one embodiment of the present application. Therefore, the references to "one embodiment" or "this embodiment" appearing throughout the specification do not necessarily refer to the same embodiment. In addition, these specific features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
[0051] In addition, the present application may repeat reference numerals and / or letters in different examples. This repetition is for the purpose of simplicity and clarity, and does not in itself indicate the relationship between the various embodiments and / or settings discussed.
[0052] The term "and / or" in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, B exists alone, and A and B exist at the same time. The term " / and" in this article describes another type of association object relationship, indicating that there can be two relationships. For example, A / and B can mean: A exists alone, and A and B exist alone. In addition, the character " / " in this article generally indicates that the previous and next associated objects are in an "or" relationship.
[0053] The term "at least one" in this article is merely a description of the association relationship of associated objects, indicating that there may be three relationships. For example, at least one of A and B can mean: A exists alone, A and B exist at the same time, and B exists alone.
[0054] It should also be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusions.
[0055] Example 1
[0056] This embodiment mainly and specifically describes a method for executing a robotic arm task based on low-code configuration;
[0057] Further, if Figure 3 As shown, a method for executing a robotic arm task based on low-code configuration includes the following steps:
[0058] S1. Define the state module, which includes the position, posture, kinematic properties, path planning constraints, and the state sequence of the position and posture dependent peripheral operations and abnormal logic processing of the robot terminal TCP;
[0059] S2. Create a low-code task configuration file. The configuration file is stored in YAML format or JSON format to represent the hierarchical relationship between items at different levels.
[0060] S3. Build a task tree structure, which includes a task array or list, subtasks, status modules and their attributes, and use the tree structure to organize task configuration;
[0061] S4. Define data structure and node type, parse and store tree-shaped task configuration sequences organized by low code, and convert text-based task configurations into data structures that can be processed by programs;
[0062] S5. Parse the low-code task configuration file and read the task tree structure configuration in YAML format or JSON format into the data structure. The data structure also satisfies the tree topology structure, which facilitates traversing each node of the task sequence when the software is executed;
[0063] S6. Execute the task tree data structure, traverse each node in the task tree data structure, and cooperate with the robot arm driver to implement the task execution operation of the robot arm according to the state module and attributes defined by each node.
[0064] Furthermore, the state module specifically includes: velocity and acceleration, joint coordinate system path and Cartesian coordinate system path, pre-execution peripheral operation, post-execution peripheral operation, post-execution time interval, and state sequence of abnormal logic processing;
[0065] Velocity and acceleration, which define the speed and acceleration at which the robot moves to that position or pose;
[0066] Joint coordinate system path and Cartesian coordinate system path are used to plan the movement path of the robot arm;
[0067] The pre-execution peripheral operation is used to start the peripheral operation before executing the path point. The peripheral operation includes but is not limited to switch operation, trigger type operation and custom IO type operation. The peripheral operation also defines the number of attempts after the operation fails, the delay time before and after the operation is executed, the state value of the switch quantity and the specific attributes of the IO type operation;
[0068] The post-execution peripheral operation is used for the peripheral operation after the execution of the path point is completed. The peripheral operation also includes switch operation, trigger type operation and custom IO type operation. The peripheral operation also defines the number of attempts after the operation fails, the delay time before and after the operation, the state value of the switch and the specific attributes of the IO type operation;
[0069] The post-execution time interval uses the time interval after the path is executed, which defines the waiting time after the execution of the path point;
[0070] The state sequence of exception logic processing is used to execute the state sequence of exception logic processing after the state fails. Goto jumps to other state modules for recovery operations. The goto jump defines the maximum number of execution attempts after the exception occurs.
[0071] Furthermore, the low-code task configuration file in S2 is stored in YAML format or JSON format, and the YAML format storage uses indentation to indicate the hierarchical relationship between entries of different levels; the JSON format storage uses "{}" to enclose the hierarchical relationship between entries of different levels; the YAML format storage and JSON format storage support vector data type and map data type; the vector data type is array data; the map data type is hash data with a unique keyword.
[0072] Further, if Figure 4 As shown, the task tree structure in S3 is defined by the low-code task configuration file. The task tree structure consists of a parent node corresponding to multiple child nodes. The child nodes are sequentially combined in the form of an array or list. The sequential combination is: parent node > child node array or list > child node attribute array or list;
[0073] Figure 4 The tasks shown in the figure are task arrays or lists, which have one or more subtasks. Each subtask contains an array or list of poses, where each pose is a "state module" and each pose state module contains an array or list of properties. Similarly, each property can also contain multiple child nodes in the form of arrays or lists, and so on to form a tree structure in which a parent node contains multiple child nodes in the form of arrays or lists. The advantage of using a one-to-many tree structure is that the inclusion relationship can be infinitely expanded according to the characteristics of the child nodes, ensuring the mechanism's adaptability to future expansion scenarios.
[0074] Furthermore, the task tree configuration in S3 specifically includes the following:
[0075] The task tree configuration in S3 defines the three most basic node structures: top parent nodes, middle nodes, and bottom nodes;
[0076] The top parent node is "arm task" which is the root node of the task tree;
[0077] The middle layer node is an array or list of "tasks" child nodes, which is a series of task nodes, each of which is represented by "name";
[0078] The bottom layer node is a "poses" array or list. Each "poses" node corresponds to a "name" node and contains a series of "pose" nodes. Each child node "pose" in the "poses" array or list represents a state module. Various attributes in the state module and the peripheral operations that depend on each other are defined in the form of child nodes.
[0079] The task tree configuration defines two types of nodes: "required" and "optional". The required nodes must exist and have corresponding information set, while the optional nodes can be omitted according to actual needs and the default values are used.
[0080] Furthermore, the S4 data structure specifically includes: vector data type and regular data type:
[0081] Vector data type, with square brackets "[]" surrounding the data and commas "," separating the data;
[0082] The general data type is a Byte data, and the data type includes decimal / hexadecimal data or string data.
[0083] Furthermore, S4 node types specifically include task nodes and status nodes:
[0084] The task node belongs to the array or list "tasks", with the child node of the keyword "name" as the start of a new task. At the same time, the task node contains the array or list of state nodes "poses" as child nodes, and the child nodes "name" and "poses" are sibling child nodes;
[0085] The state node defines the TCP position and posture of each path point in the robot's execution path, as well as its attributes and operations that need to interact with the periphery; the state node includes necessary "pose" nodes, peripheral operation nodes, and other optional nodes.
[0086] Furthermore, the peripheral operation node is the type before starting to execute the state node to which it belongs, and the type after completing the execution of the state node to which it belongs. The node structure, attributes, and child node definitions of the two types are exactly the same, and the difference lies in the time point when they are executed; three standard subclasses are defined in the two types of child nodes: bool switch type, trigger type, and IO type.
[0087] Furthermore, S5 parses the low-code task configuration file by parsing the configuration file in YAML format or JSON format to build a tree structure of the task. Each task node can contain one or more sub-task nodes, converting the task tree into a data structure. Each task node has a unique identifier, status, and sub-task list. The complete parsing structure is constructed through recursive processing to guide the robotic arm to perform tasks in a predefined order. It supports dynamic adjustment of task execution order or conditional skipping of certain tasks, thereby improving the clarity, maintainability, and scalability of task management.
[0088] Furthermore, the S6 execution task tree data structure traverses each node in the task tree data structure, and calls the corresponding robot arm driver to perform operations according to the status and attributes of each node; uses a recursive algorithm to process each task node and its subtask nodes to ensure that all subtasks are executed in a predefined order; the execution task tree data structure supports dynamic adjustment of task execution order and real-time update of task status, allowing dynamic modification of task parameters or status during execution to adapt to environmental changes or changes in task requirements.
[0089] This embodiment realizes the automated execution of robot arm tasks by defining a state module, creating a task configuration file in YAML or JSON format, building a task tree structure, defining data structure and node type, parsing the configuration file, and executing the task tree data structure. This solution solves the problems of complex programming and poor flexibility of traditional robot arms. It improves the simplicity and maintainability of task configuration through intuitive configuration files and hierarchical task management methods. It also supports dynamic adjustment of task execution order and parameters, enhancing the adaptability and flexibility of the system. In addition, through the definition of state modules and peripheral operations, the system can better cope with abnormal situations and interactions with external devices, improving overall stability and reliability.
[0090] Example 2
[0091] This embodiment is based on Embodiment 1 and mainly describes the state nodes of the node type in S4:
[0092] The state node defines the TCP position and posture of each path point in the robot's execution path, as well as its attributes and operations that need to interact with the periphery; the state node includes necessary "pose" nodes, peripheral operation nodes, and other optional nodes. The specific state nodes are shown in the following table:
[0093]
[0094] The necessary pose nodes are the TCP terminal position and pose definitions;
[0095] The optional variable is a variable node used to modify the TCP terminal position and posture;
[0096] The optional joints constraint is a joint constraint, which is used to set constraints on one or more joints during path planning;
[0097] The optional goto try max is the maximum number of attempts, which is used to define the maximum number of retries after a goto-style operation fails;
[0098] The required name is the state name, which is used to uniquely identify the state node;
[0099] The optional frame id is the name of the coordinate system, which is used to define the coordinate system of the state node to facilitate TCP coordinate transformation;
[0100] The optional velocity scale is a speed scale used to define the speed of TCP movement;
[0101] The optional acceleration scale is the acceleration ratio, which is used to define the acceleration of TCP motion;
[0102] The optional is cartesian is the path planning method selection, which is used to specify whether to use the Cartesian coordinate system or the joint coordinate system for path planning;
[0103] The optional delay to next is a delay time, which is used to define the time interval after the state execution is completed;
[0104] The optional alignment request is a hand-eye positioning request, which is used to perform hand-eye calibration when a positioning camera is installed;
[0105] The optional peripheral operation nodes include: preceding services and following services.
[0106] Optional preceding services, which are used to define the peripheral operations that need to be performed before starting to execute this state node;
[0107] The optional following services post-peripheral operations are used to define the peripheral operations that need to be performed after the state node starts executing;
[0108] An optional exception logic processing state sequence, which is used to define the state node for the recovery action to be performed after an error occurs in the execution of this state node.
[0109] The state node of this embodiment is the core component of task execution. It is used to define the position, posture and related attributes and peripheral operations of each path point in the robot arm's execution path, ensuring that the robot arm can perform tasks on the correct path with appropriate speed and acceleration, and effectively interact with external devices. It also provides the ability to handle abnormal situations to facilitate better operations.
[0110] Example 3
[0111] This embodiment is based on embodiment 1. Figure 2 As shown in the figure, the detailed process steps for parsing low-code task configuration files in S5 are mainly introduced:
[0112] S5.1 obtains the task name and reads the task name from the task configuration file;
[0113] S5.2 determines whether there is a pose child node, and checks whether there is a pose child node in the task configuration file;
[0114] S5.3 obtains the name of the pose node and determines whether the last pose has been traversed. If so, the operation is completed. If not, the pose node is parsed according to the 6-dimensional position and posture, the predefined position and posture group, and the goto name in sequence;
[0115] S5.4 extracts the 6-dimensional position and posture, and determines whether there is a variable. If so, extracts the variable keyword and operator to determine whether there is an exception. If not, directly determines whether there is an exception.
[0116] If there is an exception in S5.5, return to S5.2 and perform the operation again; if not, determine whether there is a constraint condition;
[0117] S5.6 If constraints exist, extract the constraints as a basis for subsequent processing; if not, determine whether other attributes exist;
[0118] S5.7 If other attributes exist, extract the other attributes as a basis for subsequent processing; if not, determine whether there is any peripheral operation;
[0119] S5.8 If the peripheral operation exists, obtain the service name; if not, return to S5.1 and perform the operation again;
[0120] S5.9 After obtaining the service name, determine whether it is a bool switch type. If so, extract the bool switch attribute as the basis for subsequent processing; otherwise, determine whether it is an IO type;
[0121] S5.10 If the IO type exists, extract the bool switch attribute as the basis for subsequent processing; if the IO type does not exist, determine whether the Trigger type exists, and if so, extract the bool switch attribute; Trigger type;
[0122] S5.11 determines whether there is a Trigger type, and the Trigger attribute is the trigger condition; if so, extract the Trigger attribute as the basis for subsequent processing; if not, determine whether the last one has been traversed;
[0123] S5.12 If the last node has been traversed, return to step 5.1 and repeat the operation; otherwise, return to step S5.9 to obtain the service name again for judgment;
[0124] S5.13 parses the predefined position and posture group of the pose node, extracts the predefined position and posture group, and returns to S5.5 to perform operations in sequence;
[0125] S5.14 parses the goto name of the pose node, extracts the goto name, and returns to S5.3 to perform operations in sequence;
[0126] S5.15 Repeat the above process until the last node is traversed and the operation ends.
[0127] The parsing process in S5 of this embodiment realizes efficient parsing of the task tree structure by automatically reading and processing each node in the task configuration file, obtaining the task name, then checking and parsing the pose subnode, extracting the position, posture information and related attributes, processing peripheral operations and services, and supporting exception handling and dynamic adjustment. This process improves the flexibility and scalability of the robot arm task configuration and ensures the accuracy and reliability of task execution.
[0128] Example 4
[0129] This embodiment is based on embodiment 1. Figure 1 As shown in the figure, the detailed process steps for executing low-code task profiles in S6 are mainly introduced:
[0130] S6.1 After the system is started, check whether there is a new task to be executed. If not, wait for the arrival of the new task;
[0131] S6.2 When a new task arrives, the system obtains the task;
[0132] S6.3 determines whether there is a pose node, if so, obtains the pose node; if not, ends the operation;
[0133] S6.4 obtains the pose node and determines whether there is a preceding service. If so, executes the preceding delay operation of the preceding service. Otherwise, executes the operations in sequence according to the 6-dimensional position and posture, the predefined position and posture group, and the goto name.
[0134] After the pre-delay operation of S6.5 is completed, the system will check the bool switch value, IO and Trigger attributes, and pass them to the post-delay operation of the pre-service, and determine whether it is successfully completed;
[0135] If the post-delay operation is not successfully completed in S6.6, determine whether there is an abnormal pose. If there is an abnormal pose, return to S6.4. If not, complete the operation process. If the post-delay operation is successfully completed, perform operations in sequence according to the 6-dimensional position and posture, predefined position and posture group, and goto name.
[0136] S6.7 extracts the 6-dimensional position and posture, and determines whether there is variable modification. If there is variable modification, the position and posture are modified, and the modification is passed to the constraint condition for superposition, and the IK inverse solution algorithm is executed; if there is no variable modification, the modification is directly passed to the constraint condition for superposition, and the IK inverse solution algorithm is executed;
[0137] S6.8 extracts the predefined position and posture group and performs the IK inverse solution algorithm execution operation;
[0138] S6.9 extracts the goto node and determines whether the goto node is found. If so, returns to S6.7 to perform operations in sequence; if not, returns to S6.3 to perform operations in sequence;
[0139] S6.10 executes the IK inverse solution algorithm operation to determine whether it is successful. If so, determine whether there is a following service. If not, determine whether there is an abnormal pose. If there is an abnormal pose, return to S6.4. If not, complete the operation process.
[0140] S6.11 If there is a following service, the pre-delay operation of the preceding service is executed. The system checks the bool switch quantity, IO and Trigger attributes, and passes them to the post-delay operation of the preceding service to determine whether it is successfully completed. If there is no following service, the operation process ends.
[0141] If S6.12 is completed successfully, the operation process ends; if not, it is determined whether there is an abnormal pose. If there is an abnormal pose, it returns to S6.4; if not, the operation process is completed.
[0142] This embodiment introduces the execution process in S6, which realizes the efficient execution of the robot arm task by automatically processing each node in the task configuration file. This process ensures that the system can accurately execute the actions and services defined in each task node, supports exception handling and dynamic adjustment, and improves the flexibility, reliability and accuracy of the robot arm task execution.
[0143] The above are only preferred embodiments of the present invention, which do not limit the scope of protection of the present invention. For those skilled in the art, the present invention may have various modifications and changes. Any changes, modifications, replacements, integrations and parameter changes to these embodiments within the spirit and principles of the present invention through conventional substitutions or without departing from the principles and spirit of the present invention fall within the scope of protection of the present invention.
Claims
1. A method for executing a robotic arm task based on low-code configuration, characterized in that: The following steps are involved: S1. Define a state module, which includes the position, posture, kinematic properties, path planning constraints, and state sequences of peripheral operations and abnormal logic processing of the position and posture of the robot terminal TCP; S2. Create a low-code task configuration file, where the configuration file is stored in YAML format or JSON format to represent the hierarchical relationship between items at different levels; S3, constructing a task tree structure, wherein the structure includes a task array or list, subtasks, a state module and its attributes, and uses a tree structure to organize task configuration; S4. Define data structure and node type, parse and store tree-shaped task configuration sequences organized by low code, and convert text-based task configurations into data structures that can be processed by programs; S5. Parse the low-code task configuration file and read the task tree structure configuration in YAML format or JSON format into the data structure; the data structure also satisfies the tree topology structure, which is convenient for traversing each node of the task sequence when the software is executed; S6. Execute the task tree data structure, traverse each node in the task tree data structure, and cooperate with the robot arm driver to implement the task execution operation of the robot arm according to the state module and attributes defined by each node.
2. According to a method for executing a robotic arm task based on low-code configuration according to claim 1, it is characterized in that: The state module specifically includes: velocity and acceleration, joint coordinate system path and Cartesian coordinate system path, peripheral operation before execution, peripheral operation after execution, time interval after execution, and state sequence of abnormal logic processing; The speed and acceleration are used to define the speed and acceleration of the robot arm moving to the position or posture; The joint coordinate system path and the Cartesian coordinate system path are used to plan the movement path of the robotic arm; The pre-execution peripheral operation is used to start the peripheral operation before executing the path point. The peripheral operation includes but is not limited to switch operation, trigger type operation and custom IO type operation. The peripheral operation also defines the number of attempts after the operation fails, the delay time before and after the operation is executed, the state value of the switch and the specific attributes of the IO type operation; The post-execution peripheral operation is a peripheral operation after the execution of the path point is completed. The peripheral operation also includes switch operation, trigger type operation and custom IO type operation. The peripheral operation also defines the number of attempts after the operation fails, the delay time before and after the operation is executed, the state value of the switch and the specific attributes of the IO type operation; The post-execution time interval uses the time interval after the path is executed, and defines the waiting time after the path point is executed; The state sequence of the abnormal logic processing is a state sequence for executing the abnormal logic processing after the state fails, and jumps to other state modules through goto to perform recovery operations. The goto jump defines the maximum number of execution attempts after the exception occurs.
3. According to a method for executing a robotic arm task based on low-code configuration according to claim 1, it is characterized in that: The low-code task configuration file in S2 is stored in YAML format or JSON format. The YAML format storage uses indentation to indicate the hierarchical relationship between entries of different levels; the JSON format storage uses "{}" to enclose the hierarchical relationship between entries of different levels; the YAML format storage and JSON format storage support vector data type and map data type; the vector data type is array data; the map data type is hash data with unique keywords.
4. According to a method for executing a robotic arm task based on low-code configuration according to claim 1, it is characterized in that: The task tree structure in the S3 is defined by a low-code task configuration file. The task tree structure consists of a parent node corresponding to multiple child nodes. The child nodes are sequentially combined in the form of an array or list. The sequential combination is: parent node>child node array or list>child node attribute array or list.
5. According to a method for executing a robotic arm task based on low-code configuration according to claim 1, it is characterized in that: The task tree configuration in S3 specifically includes: The task tree configuration defines three basic node structures: top parent node, middle node and bottom node; The top parent node is "arm task" which is the root node of the task tree; The middle layer node is an array or list of "tasks" child nodes, which is a series of task nodes, and each task node is represented by "name"; The bottom layer node is a "poses" array or list, each "poses" node corresponds to a "name" node and contains a series of "pose" nodes; each child node "pose" in the "poses" array or list represents a state module; various attributes and peripheral operations of the state module are defined in the form of child nodes; The task tree configuration defines two node types: "necessary" and "optional", where necessary nodes must exist and have corresponding information set, while optional nodes can be omitted based on actual needs and default values are used.
6. According to a method for executing a robotic arm task based on low-code configuration according to claim 1, it is characterized in that: The S4 data structure specifically includes: vector data type and regular data type: The vector data type uses square brackets "[]" to enclose the data, and commas "," are used to separate the data. The conventional data type is Byte data, and the data type includes decimal / hexadecimal data or character string data.
7. According to a method for executing a robotic arm task based on low-code configuration according to claim 1, it is characterized in that: The S4 node types specifically include task nodes and status nodes: The task node belongs to the array or list "tasks", and the child node with the keyword "name" is the start of a new task. At the same time, the task node contains the array or list "poses" of state nodes as a child node, and the child node "name" and "poses" are peer child nodes; The state node defines the TCP end position and posture of each path point in the robot arm execution path, as well as its attributes and operations that need to interact with the periphery; the state node includes necessary "pose" nodes, peripheral operation nodes and other optional nodes.
8. A method for executing a robotic arm task based on low-code configuration according to claim 1 or 7, characterized in that: The peripheral operation node is a type before starting to execute the state node to which it belongs, and a type after completing the execution of the state node to which it belongs. The node structure, attributes, and sub-node definitions of the two types are exactly the same, and the difference lies in the time point when they are executed; three standard subclasses are defined in the two types of sub-nodes: bool switch type, trigger type, and IO type.
9. According to a method for executing a robotic arm task based on low-code configuration according to claim 1, it is characterized in that: The S5 parses the low-code task configuration file by parsing the configuration file in YAML format or JSON format to build a tree structure of the task. Each task node can contain one or more sub-task nodes, converting the task tree into a data structure. Each task node has a unique identifier, status, and sub-task list. The complete parsing structure is constructed through recursive processing to guide the robotic arm to perform tasks in a predefined order. It supports dynamic adjustment of the task execution order or conditional skipping of certain tasks, thereby improving the clarity, maintainability, and scalability of task management.
10. A method for executing a robotic arm task based on low-code configuration according to claim 1, characterized in that: The S6 execution task tree data structure traverses each node in the task tree data structure, and calls the corresponding robotic arm driver to perform operations according to the status and attributes of each node; uses a recursive algorithm to process each task node and its subtask nodes to ensure that all subtasks are executed in a predefined order; the execution task tree data structure supports dynamic adjustment of task execution order and real-time update of task status, allowing dynamic modification of task parameters or status during execution to adapt to environmental changes or changes in task requirements.
Citation Information
Patent Citations
Adaptation method based on CANBUS communication protocol
CN116346531A
Autonomous task arranging and scheduling system and method for inspection robot
CN117400243A
Task creation method and device, equipment and storage medium
CN118485414A
Man-machine cooperation assembly method and system based on low-code programming and storage medium
CN118493401A
Method for programming at least one machine in an industrial automation system
WO2021254715A1
Cited By
Workflow generation method of robot, terminal equipment and readable storage medium
CN119952692A
