Analysis method, system and equipment of industrial robot configuration program and storage medium

Abstract

The invention discloses an industrial robot configuration program analysis method, system and device and a storage medium, and relates to the field of industrial robots, and the method comprises the steps: obtaining a full-amount configuration program file of an industrial robot, and carrying out the concurrent program analysis operation of each configuration program file in the full-amount configuration program file of the industrial robot, the concurrent program analysis operation comprises at least two of a program editing standard analysis operation, a program key field missing analysis operation, a program key field position analysis operation and a program key field parameter analysis operation, and determining a program analysis result of the industrial robot based on an execution result of the program analysis operation. Concurrent program analysis operation is performed on each configuration program file in the full-amount configuration program file of the industrial robot, so that compared with a mode of manually executing the program analysis operation one by one, the analysis efficiency of the configuration program of the industrial robot is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of industrial robots, and particularly relates to an analysis method, system and device of a configuration program of an industrial robot and a storage medium. BACKGROUND

[0002] An industrial robot is a device for realizing automatic production of industrial products based on a configuration program. Due to the characteristics of high production efficiency and high production precision, the industrial robot is widely used in a production line. Since the execution of a process flow by the industrial robot completely depends on the configuration program, when the configuration program has defects or errors, the precision of the process robot in executing the corresponding process flow is reduced, and even the process robot or the product to be processed is damaged. Therefore, analyzing the configuration program of the process robot is an indispensable step in the deployment process of the process robot.

[0003] However, since the process flows executed by the industrial robots in the production line are different, the configuration programs of the existing industrial robots are all set based on the process flow executed by the industrial robot itself. This requires the operation and maintenance personnel to manually analyze the configuration programs of the industrial robots in the production line one by one. For a factory equipped with a large number of industrial robots, the manual analysis undoubtedly has the problem of low efficiency, which further affects the production efficiency of the factory. Therefore, how to improve the analysis efficiency of the configuration program of the industrial robot has become a problem to be solved. SUMMARY

[0004] In view of the above problems, the present application provides an analysis method, system, device and storage medium of a configuration program of an industrial robot to realize the purpose of improving the analysis efficiency of the configuration program of the industrial robot. The specific scheme is as follows:

[0005] The first aspect of the present application provides an analysis method of a configuration program of an industrial robot, comprising:

[0006] obtaining a full-amount configuration program file of the industrial robot;

[0007] performing a concurrent program analysis operation on each configuration program file in the full-amount configuration program file of the industrial robot, the concurrent program analysis operation comprising at least two of a program editing standard analysis operation, a program key field absence analysis operation, a program key field position analysis operation and a program key field parameter analysis operation;

[0008] determining a program analysis result of the industrial robot based on an execution result of the program analysis operation.

[0009] In a possible implementation, the program editing standard analysis operation comprises:

[0010] According to a file name of the configuration program file, a standard program file with the file name is extracted from a standard file library, similarity of common string sequences of the configuration program file and the standard program file is calculated, and a first execution result of each of the common string sequences and the similarity is output.

[0011] In a possible implementation, the program key field missing analysis operation includes:

[0012] In response to a key field analysis request sent by a user end, fields in the configuration program file that match each key field in the key field analysis request are found, and a second execution result of the key fields that are not matched is output.

[0013] In a possible implementation, the program key field position analysis operation includes:

[0014] In response to a key field positioning request sent by a user end, index positions in the configuration program file that correspond to each of the key fields in the key field positioning request are found, and a third execution result of the index positions corresponding to each of the key fields is output.

[0015] In a possible implementation, the program key field parameter analysis operation includes:

[0016] In response to a parameter extraction request sent by a user end, according to each key field, a positioning rule and a matching rule in the parameter extraction request, parameters corresponding to each of the key fields that match the positioning rule are extracted from at least one target configuration program file, and a fourth execution result of the parameters corresponding to each of the key fields is output, the target configuration program file being a configuration program file in the full-amount configuration program file that adapts to the matching rule.

[0017] In a possible implementation, the obtaining of the full-amount configuration program file of the industrial robot includes:

[0018] According to an identity of the industrial robot, configuration program file storage addresses that have a corresponding relationship with the identity are obtained from a preset program file library; the configuration program file storage addresses are accessed, and the full-amount configuration program file of the industrial robot is obtained.

[0019] In a possible implementation, after the full-amount configuration program file of the industrial robot is obtained, the method further includes:

[0020] In response to a preprocessing request sent by a user end, the full-amount configuration program file is subjected to interference amount removal according to a preprocessing rule in the preprocessing request.

[0021] The second aspect of the present application provides an analysis system of an industrial robot configuration program, comprising:

[0022] a file obtaining module configured to obtain full-amount configuration program files of an industrial robot;

[0023] a program analysis module configured to perform concurrent program analysis operations on each configuration program file in the full-amount configuration program files of the industrial robot, wherein the concurrent program analysis operations comprise at least two of a program editing standard analysis operation, a program key field absence analysis operation, a program key field position analysis operation and a program key field parameter analysis operation;

[0024] a result determining module configured to determine a program analysis result of the industrial robot based on execution results of the program analysis operations.

[0025] In a possible implementation, the program analysis module is configured to, when performing the program editing standard analysis operation:

[0026] extract a standard program file with a file name of the configuration program file from a standard file library according to the file name, and calculate similarity of common string sequences between the configuration program file and the standard program file, and output a first execution result including each of the common string sequences and the similarity.

[0027] In a possible implementation, the program analysis module is configured to, when performing the program key field absence analysis operation:

[0028] in response to a key field analysis request sent by a user end, find fields matching each key field in the key field analysis request in the configuration program file, and output a second execution result including the key fields that are not matched.

[0029] In a possible implementation, the program analysis module is configured to, when performing the program key field position analysis operation:

[0030] in response to a key field positioning request sent by a user end, find index positions corresponding to each key field in the key field positioning request in the configuration program file, and output a third execution result including the index positions corresponding to each key field.

[0031] In a possible implementation, the program analysis module is configured to, when performing the program key field parameter analysis operation:

[0032] In response to a parameter extraction request sent by the user, the system extracts parameters corresponding to each key field that matches the positioning rule from at least one target configuration program file according to each key field, positioning rule, and matching rule in the parameter extraction request, and outputs a fourth execution result containing the parameters corresponding to each key field. The target configuration program file is a configuration program file in the full configuration program file that is adapted to the matching rule.

[0033] In one possible implementation, the file acquisition module is configured as follows:

[0034] Based on the industrial robot's identification, obtain the storage addresses of each configuration program file corresponding to the identification from the preset program file library; access each of the configuration program file storage addresses to obtain the full configuration program files of the industrial robot.

[0035] In one possible implementation, the system further includes:

[0036] The preprocessing module is used to remove interference from the full configuration program file of the industrial robot in response to a preprocessing request sent by the user terminal after obtaining the full configuration program file. This is done according to the preprocessing rules in the preprocessing request.

[0037] A third aspect of this application provides an electronic device, comprising at least one processor and a memory connected to the processor, wherein:

[0038] The memory is used to store computer programs;

[0039] The processor is used to execute the computer program to enable the electronic device to implement the analysis method of the industrial robot configuration program of the first aspect or any implementation thereof.

[0040] A fourth aspect of this application provides a computer storage medium carrying one or more computer programs, which, when executed by an electronic device, enable the electronic device to perform an analysis method for an industrial robot configuration program according to the first aspect or any implementation thereof.

[0041] By employing the above technical solution, this application provides a method, system, device, and storage medium for analyzing industrial robot configuration programs. It obtains the full configuration program file of the industrial robot through configuration and performs concurrent program analysis operations on each configuration program file within the full configuration program file. This improves the analysis efficiency for individual configuration program files compared to existing methods that involve repeated manual analysis. Subsequently, by configuring the execution results based on the program analysis operations, the program analysis results of the industrial robot are determined, achieving automatic generation of program analysis results. Compared to manual recording and summarization, this application improves both the accuracy and efficiency of program analysis results. Therefore, this application improves both the analysis efficiency and accuracy of industrial robot configuration programs. Attached Figure Description

[0042] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and elements are not necessarily drawn to scale.

[0043] Figure 1 A flowchart illustrating an analysis method for an industrial robot configuration program provided in this application;

[0044] Figure 2 A flowchart of a standard analysis operation for program editing is provided in this application;

[0045] Figure 3 A flowchart of a missing key field analysis operation provided in this application;

[0046] Figure 4 A flowchart of a program key field location analysis operation is provided for this application;

[0047] Figure 5 A flowchart of a key field parameter analysis operation provided in this application;

[0048] Figure 6 A flowchart illustrating how to obtain a full configuration program file for an industrial robot, as provided in this application;

[0049] Figure 7 This application provides a flowchart for removing interference from configuration program files;

[0050] Figure 8 A block diagram of an analysis system for an industrial robot configuration program provided in this application;

[0051] Figure 9 This is a schematic diagram of the structure of an electronic device provided in this application. Detailed Implementation

[0052] The embodiments of this application are described below with reference to the accompanying drawings. The terminology used in the implementation section of this application is for explaining specific embodiments only and is not intended to limit the scope of this application.

[0053] The embodiments of this application will now be described with reference to the accompanying drawings. Those skilled in the art will recognize that, with technological advancements and the emergence of new scenarios, the technical solutions provided in the embodiments of this application are equally applicable to similar technical problems.

[0054] The terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such terms are interchangeable where appropriate; this is merely a way of distinguishing objects with the same attributes in the embodiments of this application. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion, so that a process, method, system, product, or apparatus that comprises a series of elements is not necessarily limited to those elements, but may include other elements not explicitly listed or inherent to those processes, methods, products, or apparatuses.

[0055] It should be noted that, in practical application scenarios, this application improves the efficiency of analyzing industrial robot configuration programs compared to existing manual analysis methods. Specifically, existing manual analysis methods involve maintenance personnel loading the configuration program files of the industrial robot to be analyzed from the industrial robot backup platform, followed by manual verification of the configuration program files. Since industrial robots perform multiple processes simultaneously, meaning a single industrial robot may have multiple configuration program files, maintenance personnel need to analyze each of these multiple configuration program files individually. Furthermore, while there are multiple dimensions to analyze the configuration program files, maintenance personnel can only analyze one dimension at a time, requiring them to repeatedly analyze the same configuration program file to obtain the final analysis results. For factories with a large number of industrial robots, manual analysis obviously reduces analysis efficiency. Moreover, in scenarios with a large number of industrial robots, the large number of repetitive analyses increases the risk of errors and omissions in the analysis results obtained by maintenance personnel. This application obtains the full configuration program file of the industrial robot through configuration and performs concurrent program analysis on each configuration program file within the full configuration program file. Compared to existing methods of repeated manual analysis, this application improves the analysis efficiency for individual configuration program files. Furthermore, by employing automated analysis, this application avoids the risk of errors or omissions in the analysis results compared to manual analysis. Therefore, this application improves both the efficiency and accuracy of industrial robot configuration program analysis.

[0056] The first aspect of this application provides a method for analyzing the configuration program of an industrial robot, such as... Figure 1 As shown, the analysis method for the industrial robot configuration program includes:

[0057] S101. Obtain the full configuration program file of the industrial robot.

[0058] It should be noted that in practical applications, the aforementioned full configuration program file can be a backup file of all configuration program files for an industrial robot, stored in an industrial robot backup platform. This industrial robot backup platform can be a server used to store the backup files of the industrial robot configuration program files. By configuring this industrial robot backup platform to store the industrial robot's configuration program files, the configuration program files can be quickly loaded after an industrial robot malfunctions or is upgraded, thereby improving the industrial robot's production efficiency.

[0059] It should be noted that, in practical application scenarios, for the above-mentioned... Figure 1 The step S101 shown can obtain the full configuration program file of one industrial robot at a time, or it can obtain the full configuration program file of multiple industrial robots at a time.

[0060] S102. Perform concurrent program analysis operations on each configuration program file in the full configuration program file of the industrial robot. The concurrent program analysis operations include at least two of the following: program editing standard analysis operation, program key field missing analysis operation, program key field position analysis operation, and program key field parameter analysis operation.

[0061] It should be noted that, in practical application scenarios, this application configures concurrent program analysis operations on various configuration program files of the industrial robot. Compared with existing manual methods that involve repeated analysis, this reduces the analysis time for a single configuration program file, thereby improving analysis efficiency. For example, based on actual business scenarios, the developers of this application calculated that when manually performing standard program editing analysis, missing key field analysis, key field position analysis, and key field parameter analysis on a single configuration program file, the standard program editing analysis takes 3 minutes, the missing key field analysis takes 3 minutes, the key field position analysis takes 3 minutes, and the key field parameter analysis takes 2 minutes. Therefore, the total time to complete a single configuration program file is 11 minutes. When this solution uses automated execution, the standard program editing analysis takes 3 seconds, the analysis of missing key program fields takes 1 second, the analysis of key program field positions takes 1 second, and the analysis of key program field parameters takes 1 second. Furthermore, since these operations are performed concurrently—that is, using the concurrent program analysis method described in this application for the configuration program files—the total time required is only 3 seconds. In the case of an industrial robot with 80 configuration program files, this application only takes 4 minutes, while existing manual analysis methods would take 14 hours. Therefore, this application significantly improves the efficiency of program analysis for industrial robots compared to existing technologies.

[0062] It should be noted that, in practical applications, the aforementioned standard program editing analysis operation is used to analyze whether the format of the configuration program file meets the requirements for the industrial robot to read. Since the configuration program files of industrial robots are manually written by engineers according to the corresponding process flow, influenced by the engineers' own writing habits, the configuration program files may contain program formats or structures that the industrial robot cannot read or write correctly. When the industrial robot cannot correctly read the program to be executed during operation, it is easy to cause the industrial robot to malfunction or cause the workpiece to be processed to be scrapped. Because existing manual analysis methods require engineers to analyze the format of the configuration program file based on their own experience, the analysis efficiency is greatly affected by the engineer's own factors. Therefore, this application, by configuring the aforementioned standard program editing analysis operation, achieves automatic identification and analysis of the format of the configuration program file, improving analysis efficiency compared to manual analysis.

[0063] It should be noted that, in practical applications, the aforementioned "key field missing analysis" operation is used to analyze whether fields, functions, parameters, etc., representing the corresponding process flow in the configuration program file are missing. Taking an industrial robot used for spot welding as an example, the TC_ONLINE field in its configuration program file is used for water supply management. If this field is missing, the spot welding robot will continue to work even when the water supply is stopped. However, due to the lack of cooling water, this could lead to the risk of the industrial robot's inverter overheating and being damaged. Since a process flow can include a large number of fields, functions, parameters, etc., manual identification and analysis are prone to omissions or errors, thus reducing analysis efficiency and accuracy. Therefore, this application, by configuring the aforementioned "key field missing analysis" operation, achieves automatic identification of missing fields representing the process flow in the configuration program file, improving analysis efficiency and accuracy compared to manual analysis.

[0064] It should be noted that, in practical application scenarios, the above-mentioned key field position analysis operation is used to analyze whether the fields, functions, parameters, etc., representing the corresponding process flow in the configuration program file are in the correct positions in the program. Taking the TC_ONLINE field as an example again. Under normal circumstances, a configuration program file of a spot welding robot should include two TC_ONLINE fields, one located in the program segment representing the spot welding process and the other in the program segment terminating the spot welding. The TC_ONLINE field located in the program segment representing the spot welding process should have a DI

[2314] field, which is used to represent the normal circulating water flow rate. TC_ONLINE(ON ANDDI

[2314] ) indicates that water should be supplied at the normal circulating water flow rate during the welding process. The TC_ONLINE(ON) located in the program segment terminating the spot welding indicates that water should be supplied at the minimum flow rate after the welding is completed. If TC_ONLINE(ON ANDDI

[2314] ) appears in the program segment terminating the spot welding, it will lead to the normal circulating water flow rate after the welding is completed, which will result in the risk of the temperature being too low and affecting the welding effect. Since the same field in different locations within a configuration program file represents different process flows, their actual control effects also differ. When there are many identical fields in the configuration program file, existing manual analysis methods are prone to misjudgment or omission, thereby reducing analysis efficiency and accuracy. Therefore, this application, by configuring the above-mentioned key field location analysis operation, enables the identification of missing fields representing the process flow in the configuration program file, improving analysis efficiency and accuracy compared to manual analysis methods.

[0065] It should be noted that in practical applications, the aforementioned key field parameter analysis operation is used to extract the relevant control parameters of key fields in the configuration program file. For example, an industrial robot used to perform spot welding needs to move on the workpiece to perform spot welding operations at multiple locations. This requires setting corresponding motion control parameters in the relevant control fields of the configuration program file. For industrial robots, a single configuration program file can contain a large number of motion control parameters. An error in any of these parameters can cause the robot to rub against the workpiece during movement, resulting in damage. Furthermore, manually identifying each motion control parameter in the configuration program file is tedious; therefore, each parameter needs to be extracted separately for maintenance personnel to troubleshoot. Since a single configuration program file can contain a large number of related control parameters, existing manual analysis methods require engineers to manually distinguish between control parameters and key fields, and manually associate and record each key field with its related control parameters. In application scenarios with a large number of industrial robots, each with multiple configuration program files, existing manual analysis methods suffer from low extraction efficiency. This application configures the above-mentioned key field parameter analysis operation to automatically extract the relevant control parameters of key fields in the configuration program file, which improves the extraction efficiency compared with the manual recording method.

[0066] S103. Based on the execution results of the program analysis operation, determine the program analysis results of the industrial robot.

[0067] It should be noted that in practical applications, existing manual analysis methods require maintenance personnel to record erroneous fields encountered during manual troubleshooting. The final program analysis results can only be obtained after all analyses are completed and the recorded information is organized, leading to reduced analysis efficiency. This application, however, determines the program analysis structure of the industrial robot by configuring the execution results based on the program analysis operations, thereby achieving automatic generation of program analysis results. This improves both the accuracy and efficiency of the program analysis results.

[0068] This solution obtains the full configuration program file of the industrial robot through configuration and performs concurrent program analysis operations on each configuration program file within the full configuration program file. Compared to existing methods of repeated manual analysis, this application improves the analysis efficiency for individual configuration program files. Subsequently, by configuring the execution results based on the program analysis operations, the program analysis results of the industrial robot are determined, realizing the automatic generation of program analysis results. Compared to manual recording and summarization, this application improves both the accuracy and efficiency of program analysis results. Therefore, this application improves both the analysis efficiency and accuracy of industrial robot configuration programs.

[0069] In one possible implementation, the standard analysis operations for program editing include:

[0070] Based on the filename of the configuration program file, extract the standard program file with the filename from the standard file library, calculate the similarity of the common string sequences between the configuration program file and the standard program file, and output the first execution result of each common string sequence and its similarity.

[0071] It should be noted that in practical application scenarios, there are multiple ways to implement the above-mentioned standard program editing analysis operation. Here, we provide an example, which includes the following steps A1 to A3.

[0072] Step A1: Based on the filename of the configuration program file, extract the standard program file with that filename from the preset standard library. Then, trigger step A2.

[0073] In one possible implementation, the aforementioned default standard library could be the Python difflib library.

[0074] Step A2: Load the configuration program file and the standard program file respectively. Determine the field positions of each common string sequence based on the tags in the standard program file. Identify the string sequences in the configuration program file that are in the same field position as common string sequences, and establish the correspondence between the common string sequences in the standard program file and the configuration program file that are in the same field position. Then trigger step A3.

[0075] Step A3: Call the SequenceMatcher function of the preset standard library to calculate the similarity of corresponding common string sequences, and use the report generation tool (HtmlDiff) of the preset standard library to output the first execution result, which includes the content of each common string sequence and its similarity.

[0076] It should be noted that this application automatically obtains the similarity between the configuration program file and the standard program file by extracting the standard program file with the configuration program file name and by calculating the similarity of the common string sequences. This improves the analysis efficiency compared to the existing manual analysis of differences.

[0077] It should be noted that in practical application scenarios, such as those with a large number of industrial robots, each with multiple configuration program files, the above-mentioned standard program editing and analysis operations can be implemented by executing them sequentially according to the order in which the industrial robots are arranged. Specifically:

[0078] like Figure 2 The diagram shows a flowchart of a standard program editing analysis operation. The specific operation steps are as follows:

[0079] Step S201: Obtain a list of industrial robots to be searched, including multiple industrial robot identifiers arranged in chronological order of import time, and create an analysis results table. Step S202 is then triggered.

[0080] Step S202: Determine if there are any industrial robots in the list of robots to be checked that have not yet had a completed inspection tag added. If yes, trigger step S203; otherwise, output the analysis result table and end the process.

[0081] Step S203: The identifier of the industrial robot to be inspected that has not yet been added to the list of industrial robots to be inspected and has the earliest import time is identified as the current identifier to be inspected. Step S204 is then triggered.

[0082] Step S204: Obtain the storage addresses of each configuration program file that corresponds to the current identifier to be queried, and access each configuration program file storage address to obtain the full set of configuration program files corresponding to the current identifier to be queried. Then trigger step S205.

[0083] Step S205: Determine whether there is a configuration program file in the full configuration program file that has not been marked with the "completed analysis" tag. If yes, then trigger step S206; otherwise, trigger step S210.

[0084] Step S206: Identify any configuration program file that does not have a "Completed Analysis" tag as the current configuration program file. Then trigger step S207.

[0085] Step S207: Extract the standard program file with the filename of the current configuration program file, and calculate the similarity of the common string sequences between the current configuration program file and the standard program file. Then trigger step S208.

[0086] Step S208: Import the first execution result, which contains the common string sequences and their similarity, into the analysis result table. This triggers step S209.

[0087] Step S209: Add a "Completed Analysis" tag to the current configuration program file. This triggers step S205.

[0088] Step S210: Add a completion check tag to the current identifier to be checked, and trigger step S202.

[0089] In one possible implementation, the program's critical field missing analysis operation includes:

[0090] In response to the key field analysis request sent by the client, the system searches the configuration file for fields that match each key field in the key field analysis request, and outputs the second execution result containing the key fields that were not matched.

[0091] It should be noted that in actual application scenarios, there are multiple ways to implement the above-mentioned key field missing analysis operation. Here, we provide an example, which includes the following steps B1 to B3.

[0092] Step B1: In response to the key character segment analysis request sent by the user, parse each key field in the key field analysis request. This triggers step B2.

[0093] Step B2: Using a preset string matching algorithm, search for fields in the configuration program file that match each key field.

[0094] It should be noted that, in practical applications, the aforementioned preset string matching algorithms can be of various types, including but not limited to the Brute algorithm, the KMP algorithm (Knuth-Morris-Pratt), and the Rabin-Karp Hash algorithm (RK). This application does not impose excessive restrictions or elaborate on the specific types and configuration processes of the aforementioned preset string matching algorithms.

[0095] Step B3: Based on the matching results, the output content is the second execution result of the key fields that were not matched.

[0096] It should be noted that this application configures a preset string matching algorithm to sequentially search for fields that match each key field in the key field analysis request in the configuration program file, and outputs the second execution result of the unmatched key fields based on the matching results. This achieves automatic filtering and analysis of missing key fields in the configuration program file, which improves the analysis efficiency and accuracy compared to manual analysis.

[0097] It should be noted that in practical application scenarios, such as those with a large number of industrial robots, each with multiple configuration program files, the aforementioned analysis of missing key program fields can be performed sequentially according to the order in which the industrial robots are listed. Specifically:

[0098] like Figure 3 The diagram shows a flowchart of a procedure for analyzing missing key fields in a program. The specific steps are as follows:

[0099] Step S301: Obtain a list of industrial robots to be searched, including multiple industrial robot identifiers arranged in chronological order of import time, and create an analysis results table. Trigger step S302.

[0100] Step S302: Determine if there are any industrial robots in the list of robots to be checked that have not yet had a completed inspection tag added. If yes, trigger step S303; otherwise, output the analysis result table and end the process.

[0101] Step S303: The identifier of the industrial robot to be inspected that has not yet had a completed inspection tag added and has the earliest import time is identified as the current identifier to be inspected. Step S304 is then triggered. Step S304: The storage addresses of each configuration program file corresponding to the current identifier to be inspected are obtained, and each configuration program file storage address is accessed to obtain the full set of configuration program files corresponding to the current identifier to be inspected. Step S305 is then triggered.

[0102] Step S305: Determine whether there is a configuration program file in the full configuration program file that has not been marked with the "completed analysis" tag. If yes, then trigger step S306; otherwise, trigger step S310.

[0103] Step S306: Identify any configuration program file that does not have a "Completed Analysis" tag as the current configuration program file. Then, trigger step S307.

[0104] Step S307: Using a preset string matching algorithm, sequentially search the current configuration program file for fields that match each key field in the key character segment analysis request sent by the user. This triggers step S308.

[0105] Step S308: Import the second execution result containing the unmatched key fields into the analysis results table. This triggers step S309.

[0106] Step S309: Add a "Completed Analysis" tag to the current configuration program file. This triggers step S305.

[0107] Step S310: Add a completion check tag to the current check identifier and trigger step S302.

[0108] In one possible implementation, the program's key field location analysis operation includes:

[0109] In response to the key field location request sent by the client, the system searches the configuration program file for the index position corresponding to each key field in the key field location request, and outputs the third execution result, which is the index position corresponding to each key field.

[0110] It should be noted that in actual application scenarios, there are multiple ways to implement the above-mentioned key field location analysis operation. Here, we provide an example, which includes the following steps C1 to C3.

[0111] Step C1: In response to the key field location request sent by the user, parse the key fields arranged in sequence in the key field location request.

[0112] Step C2: Using a string matching algorithm, following the order of the key fields in Step C1, traverse the configuration file starting from the beginning, sequentially searching for fields in the configuration file that match each key field, and recording their index positions. This triggers Step C3.

[0113] It should be noted that in practical applications, the order of the key fields mentioned above follows the order of key fields in the standard program file. Therefore, to improve search efficiency, after recording the index position of the current key field, the search is performed starting from the position of the last character of that current key field, looking for the adjacent key field following it. This avoids wasting time by starting the search from the beginning of the program for each lookup, thus improving analysis efficiency.

[0114] Step C3, based on the recorded results, outputs the third execution result corresponding to the index positions of each key field in the configuration program file.

[0115] It should be noted that this application uses a configuration string matching algorithm to sequentially search for fields in the configuration program file that match each key field and their index positions according to the order of the key fields in the key field location request. This enables automatic identification and recording of the position of key fields in the configuration program file, which improves the efficiency and accuracy of key field index position analysis compared to manual analysis.

[0116] It should be noted that in practical application scenarios, such as those with a large number of industrial robots, each with multiple configuration program files, the above-mentioned key field location analysis operation can be implemented by executing the operations sequentially according to the order in which the industrial robots are arranged. Specifically:

[0117] like Figure 4 The diagram shows a flowchart of a program key field location analysis operation. The specific operation steps are as follows:

[0118] Step S401: Obtain a list of industrial robots to be checked, including multiple industrial robot identifiers arranged in chronological order of import time, and create an analysis results table. Trigger step S402.

[0119] Step S402: Parse the key fields in the key field location request, arranged in sequence. Then trigger step S403.

[0120] Step S403: Determine if there are any industrial robots in the list of robots to be checked that have not yet had a completed inspection tag added. If yes, trigger step S403; otherwise, output the analysis result table and end the process.

[0121] Step S404: The identifier of the industrial robot to be inspected that has not yet been added to the list of industrial robots to be inspected and has the earliest import time is identified as the current identifier to be inspected. Step S405 is then triggered.

[0122] Step S405: Obtain the storage addresses of each configuration program file corresponding to the current identifier to be queried, and access each configuration program file storage address to obtain the full set of configuration program files corresponding to the current identifier to be queried. Then trigger step S406.

[0123] Step S406: Determine whether there is a configuration program file in the full configuration program file that has not added the analysis completion tag. If yes, then trigger step S407; otherwise, trigger step S414.

[0124] Step S407: Identify any configuration program file that does not have a "Completed Analysis" tag as the current configuration program file. Then trigger step S408.

[0125] Step S408: Determine if there are any key fields for which index tags have not been added. If yes, trigger step S409; otherwise, trigger step S413.

[0126] Step S409: Determine the key field that appears first in the sorting order as the current key field. Then trigger step S410.

[0127] Step S410: Starting from the current traversal start position and moving towards the end of the program, use a string matching algorithm to search for the current key field in the current configuration program file, record the index position of the found key field, and import the index position of the found key field into the analysis results table. Then, step S411 is triggered.

[0128] In one possible implementation, since the aforementioned key field location request is manually edited by operations and maintenance personnel through the user terminal, if the personnel make a mistake and the order of the key fields is incorrect, it is very easy to fail to find the key fields. Therefore, after step S410 is completed, it can be determined whether the last character position of the currently found key field is the last character position of the program configuration file. If so, then when executing step S411 below, the current traversal start position is updated to the first character position of the program configuration file.

[0129] Step S411: Update the current traversal start position to the position of the last character of the currently found key field. Then trigger step S412.

[0130] Step S412: Add a completion index tag to the current key field. This triggers step S408.

[0131] Step S413: Add a "Completed Analysis" tag to the current configuration program file. This triggers step S406.

[0132] Step S414: Add a completion check tag to the current identifier to be checked. And trigger step S403.

[0133] In one possible implementation, the analysis of key field parameters in the program includes:

[0134] In response to a parameter extraction request sent by the user, the system extracts the parameters corresponding to each key field that matches the positioning rule from at least one target configuration program file based on the key fields, positioning rules, and matching rules in the parameter extraction request. The system then outputs the fourth execution result of the parameters corresponding to each key field. The target configuration program file is the configuration program file in the full configuration program file that is adapted to the matching rule.

[0135] It should be noted that in actual application scenarios, there are multiple ways to implement the above-mentioned key field parameter analysis operation. Here, we provide an example, which includes the following steps D1 to D3.

[0136] Step D1: In response to the parameter extraction request sent by the user, parse the key fields, location rules, and matching rules in the parameter extraction request. Then, step D2 is triggered.

[0137] In one possible implementation, the configuration file includes characters or content unrelated to program execution, such as comment lines, capitalization, blank lines, and line numbers, in addition to the corresponding program code. To reduce the risk of erroneous extraction, the parameter extraction request in step D1 above can also include preprocessing rules to define character content in the configuration file that does not need to be traversed or searched. For example, the preprocessing rules could include: "ignore comment lines", "ignore capitalization", "ignore blank lines", etc.

[0138] Step D2: Select at least one target configuration file from the full set of configuration files that meets the matching rules. Then, trigger step D3.

[0139] It should be noted that in practical applications, different program files are used to execute different processes, and these processes share the same control parameters. For example, both spot welding on the outside and inside of a car door involve path control of the robotic arm; the only difference lies in the specific control parameters. Therefore, this application, by configuring the aforementioned matching rules, enables the extraction of key field parameters from specific configuration program files, thereby improving the flexibility of the analysis.

[0140] Step D3: Based on the positioning rules, extract the parameters corresponding to each key field from each target configuration program file in sequence. This triggers step D4.

[0141] It should be noted that in practical applications, since the aforementioned key fields can be fields that mark a certain control program segment, the number of parameters to be extracted for different key fields, as well as their positions within the program segment, will vary. Therefore, by configuring the above positioning rules, accurate and rapid extraction of the parameters corresponding to the key fields can be achieved. For example, assuming the key field represents "spot welding path," its corresponding parameters include four categories: weld point position, motion mode, and switch travel. These four types of parameters are enclosed in parentheses after the key field and separated by commas. The positioning rule can then be set to "four independent strings within parentheses after the key field, with adjacent independent strings separated by commas, and the number of commas is three."

[0142] Step D4: After all the parameters in the target configuration program files have been extracted, the output is the fourth execution result of the parameters corresponding to each key field.

[0143] It should be noted that this application automatically extracts the parameters corresponding to the key fields in the request based on the configuration of the parameters, the positioning rules and the matching rules, and at least one target configuration file that meets the matching rules. This improves the extraction efficiency and accuracy compared to the existing manual recording method.

[0144] It should be noted that in practical application scenarios, such as those with a large number of industrial robots, each with multiple configuration program files, the above-mentioned key field parameter analysis operations can be implemented by executing them sequentially according to the order of the industrial robots. Specifically:

[0145] like Figure 5 The diagram shows a flowchart of a key field parameter analysis operation for a program. The specific operation steps are as follows:

[0146] Step S501: Obtain a list of industrial robots to be checked, including multiple industrial robot identifiers arranged in chronological order of import time, and create an analysis results table. Trigger step S502.

[0147] Step S502: Parse the parameters to extract the key fields, location rules, and matching rules from the request. Then, step S503 is triggered.

[0148] Step S503: Determine if there are any industrial robots in the list of industrial robots to be checked that have not yet had a completed inspection tag added. If yes, trigger step S504; otherwise, output the analysis result table and end the process.

[0149] Step S504: The identifier of the industrial robot to be inspected that has not yet been added to the list of industrial robots to be inspected and has the earliest import time is identified as the current identifier to be inspected. Step S505 is then triggered.

[0150] Step S505: Obtain the storage addresses of each configuration program file corresponding to the current identifier to be queried, and access each configuration program file storage address to obtain the full set of configuration program files corresponding to the current identifier to be queried. Then trigger step S506.

[0151] Step S506: Identify at least one configuration program file in the full configuration program files that matches the matching rules as the target configuration program file. Then trigger step S507.

[0152] Step S507: Determine if there is a target configuration program file without a completed parameter extraction tag. If yes, trigger step S508; otherwise, trigger step S511. Step S508: Identify any target configuration program file without a completed parameter extraction tag as the current target configuration program file, and trigger step S509.

[0153] Step S509: Based on the positioning rules, extract the parameters corresponding to each key field from the current target configuration program file, and import the extracted parameters corresponding to each key field into the analysis result table. This triggers step S510.

[0154] Step S510: Add a "Complete Parameter Extraction" tag to the current target configuration program file. This triggers step S507.

[0155] Step S511: Add a completion check tag to the current identifier to be checked. And trigger step S503.

[0156] In one possible implementation, the full configuration file for the industrial robot is obtained, including:

[0157] Based on the industrial robot's identification, obtain the storage addresses of each configuration program file corresponding to the identification from the preset program file library; access each configuration program file storage address to obtain the full configuration program files of the industrial robot.

[0158] It should be noted that, in scenarios with a large number of industrial robots, the above-mentioned implementation method for obtaining the full configuration program files of the industrial robots can be:

[0159] like Figure 6 The diagram shows a flowchart for obtaining the full configuration program file of an industrial robot. The specific operation steps are as follows:

[0160] Step S601: Obtain the identification identifiers of multiple industrial robots, and based on the correspondence between the identification identifiers and the storage addresses of the configuration program files, construct a list of program addresses corresponding to each identification identifier. Then, trigger step S602.

[0161] Step S602: Determine if there is an identity identifier for which the full configuration program file loading tag has not been added. If yes, trigger step S603; otherwise, end the process.

[0162] Step S603: Identify the identity that has not yet added the tag for loading the full configuration program file and designate it as the current identity. Then, step S604 is triggered.

[0163] Step S604: Sequentially access the storage addresses of each configuration program file in the program address list corresponding to the current identifier to obtain the stored configuration program files. Then trigger step S605.

[0164] Step S605: If the full configuration program file for the current identifier is obtained, add a tag indicating that the full configuration program file has been loaded to the current identifier. Then, step S602 is triggered.

[0165] In one possible implementation, after obtaining the full configuration program file of the industrial robot, the above-mentioned... Figure 1 The analysis method for the industrial robot configuration program shown also includes:

[0166] In response to a preprocessing request sent by the client, interference is removed from the full configuration program file according to the preprocessing rules in the preprocessing request.

[0167] It should be noted that in practical application scenarios, the preprocessing request sent by the client can carry user-defined preprocessing rules. These preprocessing rules are used to define the interference quantities that need to be deleted or transformed in the configuration program file. The types of interference quantities include, but are not limited to: full-line comments, inline comments, blank lines, capitalization, line numbers, etc.

[0168] It should be noted that in practical applications, there are multiple ways to remove interference from the entire configuration program file based on the preprocessing rules in the preprocessing request. Here, one example is provided:

[0169] like Figure 7The diagram shows a flowchart for removing interference from configuration files. This flowchart uses a single configuration file as an example; the process can be applied to all configuration files. The specific steps are as follows:

[0170] Step S701: Read the configuration program file and preprocessing rules. Then trigger step S702.

[0171] Step S702: Determine whether only the main program segment should be retained. If yes, then trigger step S708; otherwise, trigger step S703.

[0172] Step S703: Determine whether to delete the entire line comment. If yes, trigger step S709; otherwise, trigger step S704.

[0173] Step S704: Determine whether to delete the inline comment. If yes, trigger step S710; otherwise, trigger step S705.

[0174] Step S705: Determine whether all letters should be converted to uppercase. If yes, trigger step S711; otherwise, trigger step S706.

[0175] Step S706: Determine whether to delete empty lines. If yes, trigger step S712; otherwise, trigger step S707.

[0176] Step S707: Determine whether to delete the row number. If yes, trigger step S713; otherwise, trigger step S714.

[0177] Step S708: Delete all program segments in the configuration program file except for the main program segment. Then, step S703 is triggered.

[0178] Step S709: Delete all entire lines of comments in the configuration program file. Then trigger step S704.

[0179] Step S710: Delete all inline comments in the configuration program file. Then trigger step S705.

[0180] Step S711: Perform capitalization on the configuration program file. This triggers step S706.

[0181] Step S712: Delete all blank lines in the configuration program file. Then trigger step S707.

[0182] Step S713: Delete all line numbers in the configuration program file. Then trigger step S714.

[0183] Step S714: Output the preprocessed configuration program file.

[0184] The second aspect of this application provides an analysis system for industrial robot configuration programs, such as...Figure 8 As shown, the analysis system for this industrial robot configuration program includes:

[0185] File acquisition module 801 is used to obtain the full configuration program file of the industrial robot;

[0186] The program analysis module 802 is used to perform concurrent program analysis operations on each configuration program file in the full configuration program file of the industrial robot. The concurrent program analysis operations include at least two of the following: program editing standard analysis operation, program key field missing analysis operation, program key field position analysis operation, and program key field parameter analysis operation.

[0187] The result determination module 803 is used to determine the program analysis results of the industrial robot based on the execution results of the program analysis operation.

[0188] In one possible implementation, the program analysis module 802 described above is configured to perform standard program editing analysis operations as follows:

[0189] Based on the filename of the configuration program file, extract the standard program file with the filename from the standard file library, calculate the similarity of the common string sequences between the configuration program file and the standard program file, and output the first execution result of each common string sequence and its similarity.

[0190] In one possible implementation, the program analysis module 802 described above is configured to perform a missing key field analysis operation:

[0191] In response to the key field analysis request sent by the client, the system searches the configuration file for fields that match each key field in the key field analysis request, and outputs the second execution result containing the key fields that were not matched.

[0192] In one possible implementation, the program analysis module 802 described above is configured to perform the program key field location analysis operation as follows:

[0193] In response to the key field location request sent by the client, the system searches the configuration program file for the index position corresponding to each key field in the key field location request, and outputs the third execution result, which is the index position corresponding to each key field.

[0194] In one possible implementation, the program analysis module 802 described above is configured to perform the analysis of key program field parameters as follows:

[0195] In response to a parameter extraction request sent by the user, the system extracts the parameters corresponding to each key field that matches the positioning rule from at least one target configuration program file based on the key fields, positioning rules, and matching rules in the parameter extraction request. The system then outputs the fourth execution result of the parameters corresponding to each key field. The target configuration program file is the configuration program file in the full configuration program file that is adapted to the matching rule.

[0196] In one possible implementation, the file acquisition module 801 described above is configured as follows:

[0197] Based on the industrial robot's identification, obtain the storage addresses of each configuration program file corresponding to the identification from the preset program file library; access each configuration program file storage address to obtain the full configuration program files of the industrial robot.

[0198] In one possible implementation, such as Figure 8 The analysis system for the industrial robot configuration program shown also includes:

[0199] The preprocessing module is used to remove interference from the full configuration program file of the industrial robot in response to the preprocessing request sent by the user. This is done according to the preprocessing rules in the preprocessing request.

[0200] A third aspect of this application provides an electronic device including at least one processor and a memory connected to a preprocessor, wherein:

[0201] Memory is used to store computer programs;

[0202] The processor is used to execute computer programs to enable electronic devices to implement the industrial robot configuration program described in the first aspect or any implementation thereof.

[0203] This application also provides an electronic device in its embodiments. (See reference...) Figure 9 The diagram illustrates a structural schematic suitable for implementing the electronic device in the embodiments of this application. The electronic device in the embodiments of this application may include, but is not limited to, fixed terminals such as mobile phones, laptops, PDAs (personal digital assistants), PADs (tablet computers), desktop computers, etc. Figure 9 The electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0204] like Figure 9As shown, the electronic device may include a processing unit (e.g., a central processing unit, a graphics processing unit, etc.) 901, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 902 or a program loaded from a storage device 908 into a random access memory (RAM) 903. When the electronic device is powered on, the RAM 903 also stores various programs and data required for the operation of the electronic device. The processing unit 901, ROM 902, and RAM 903 are interconnected via a bus 904. An input / output (I / O) interface 905 is also connected to the bus 904.

[0205] Typically, the following devices can be connected to I / O interface 905: input devices 906 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 907 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 908 including, for example, memory cards, hard drives, etc.; and communication devices 909. Communication device 909 allows electronic devices to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 9 Electronic devices with various devices are shown, but it should be understood that it is not required to implement or have all of the devices shown. More or fewer devices may be implemented or have alternatively.

[0206] This application also provides an analysis method that includes a computer program product, including computer-readable instructions, which, when executed on an electronic device, cause the electronic device to implement any of the industrial robot configuration programs provided in this application.

[0207] This application also provides a computer-readable storage medium that carries one or more computer programs. When the one or more computer programs are executed by an electronic device, the electronic device can implement any of the industrial robot configuration program analysis methods provided in this application.

[0208] It should also be noted that the device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. In addition, in the device embodiment drawings provided in this application, the connection relationship between modules indicates that they have a communication connection, which can be implemented as one or more communication buses or signal lines.

[0209] Through the above description of the embodiments, those skilled in the art can clearly understand that this application can be implemented by means of software plus necessary general-purpose hardware, and of course, it can also be implemented by special hardware including application-specific integrated circuits, special CPUs, special memory, special components, etc. Generally, any function performed by a computer program can be easily implemented by corresponding hardware, and the specific hardware structure used to implement the same function can also be diverse, such as analog circuits, digital circuits, or special-purpose circuits. However, for this application, software program implementation is more often the preferred implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a readable storage medium, such as a computer floppy disk, USB flash drive, mobile hard disk, ROM, RAM, magnetic disk, or optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, training equipment, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0210] In the above embodiments, the implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, in the form of a computer program product.

[0211] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, training device, or data center to another website, computer, training device, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a training device or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).

Claims

1. An analysis method of an industrial robot configuration program, characterized by, The method comprises the following steps: obtaining full-quantity configuration program files of an industrial robot; performing concurrent program analysis operations on each configuration program file in the full-quantity configuration program files of the industrial robot, wherein the concurrent program analysis operations comprise at least two of program editing standard analysis operations, program key field absence analysis operations, program key field position analysis operations, and program key field parameter analysis operations; determining a program analysis result of the industrial robot based on an execution result of the program analysis operations.

2. The analysis method of an industrial robot configuration program according to claim 1, characterized in that, The program editing standard analysis operations comprise: extracting a standard program file having a file name of the configuration program file from a standard file library according to the file name, calculating a similarity of common string sequences between the configuration program file and the standard program file, and outputting a first execution result including each of the common string sequences and the similarity.

3. The analysis method of an industrial robot configuration program according to claim 1, characterized in that, The program key field absence analysis operations comprise: in response to a key field analysis request sent by a user terminal, searching for a field matching each key field in the key field analysis request in the configuration program file, and outputting a second execution result including the key field that is not matched.

4. The analysis method of an industrial robot configuration program according to claim 1, characterized by, The program key field position analysis operations comprise: in response to a key field positioning request sent by a user terminal, searching for an index position corresponding to each key field in the key field positioning request in the configuration program file, and outputting a third execution result including the index position corresponding to each key field.

5. The analysis method of an industrial robot configuration program according to claim 1, characterized by, The program key field parameter analysis operations comprise: in response to a parameter extraction request sent by a user terminal, extracting a parameter corresponding to each key field matching the positioning rule from at least one target configuration program file according to each key field, a positioning rule, and a matching rule in the parameter extraction request, and outputting a fourth execution result including the parameter corresponding to each key field, wherein the target configuration program file is a configuration program file in the full-quantity configuration program files that is adapted to the matching rule.

6. The analysis method of an industrial robot configuration program according to any one of claims 1 to 5, characterized in that, The method for obtaining the full-quantity configuration program files of the industrial robot comprises: obtaining, according to an identity of the industrial robot, a storage address of each configuration program file having a corresponding relationship with the identity from a preset program file library; and accessing each of the storage addresses of the configuration program files to obtain the full-quantity configuration program files of the industrial robot.

7. The analysis method of an industrial robot configuration program according to claim 1, characterized by, After obtaining the full-quantity configuration program files of the industrial robot, the method further comprises: in response to a preprocessing request sent by a user terminal, removing an interference quantity from the full-quantity configuration program files according to a preprocessing rule in the preprocessing request.

8. An analysis system of an industrial robot configuration program, characterized by The method comprises the following steps: a file obtaining module for obtaining full-quantity configuration program files of an industrial robot; a program analysis module for performing concurrent program analysis operations on each configuration program file in the full-quantity configuration program files of the industrial robot, wherein the concurrent program analysis operations comprise at least two of program editing standard analysis operations, program key field absence analysis operations, program key field position analysis operations, and program key field parameter analysis operations; A result determining module is configured to determine a program analysis result of the industrial robot based on an execution result of the program analysis operation.

9. An electronic device, comprising: The electronic device comprises at least one processor and a memory connected to the processor, wherein: The memory is configured to store a computer program; The processor is configured to execute the computer program, so that the electronic device is enabled to implement the method for analyzing a configuration program of an industrial robot according to any one of claims 1 to 7.

10. A computer storage medium, characterized in that, The storage medium carries one or more computer programs, and when the one or more computer programs are executed by an electronic device, the electronic device is enabled to implement the method for analyzing a configuration program of an industrial robot according to any one of claims 1 to 7.

Images