Automatic debugging method and system for tightening device interface

Abstract

The present invention provides a method and system for automatic debugging of the interface of a tightening device. According to the business and data characteristics of the tightening equipment, the present invention selects three knowledge subjects, namely hardware interface, connection protocol, and manufacturer information, to construct a knowledge graph. The present invention adopts the method of knowledge graph to construct a tightening intelligent debugging system with autonomous learning, which improves the efficiency of tightening debugging and the stability of final data access. The present invention can be used to solve the problem of efficient and stable integrated debugging of multi-variety, multi-protocol, and multi-format data in the integration of tightening equipment and information systems.

Description

Technical Field

[0001] The invention relates to an automatic debugging method and system for a tightening device interface. Background Art

[0002] With the continuous development of social economy and the continuous improvement of people's living standards, the application of automation equipment and intelligent equipment is becoming more and more extensive. As the core equipment in the assembly link of production, the intelligence level of tightening equipment has been greatly improved in recent years. In order to ensure the quality of assembly, more and more companies have implemented information systems to collect and store real-time data of tightening equipment.

[0003] Due to the large quantity, variety and types of tightening equipment, the access and debugging of tightening equipment has hindered the development of digital production in enterprises. Summary of the invention

[0004] The object of the present invention is to provide a method and system for automatic debugging of a tightening device interface.

[0005] In order to solve the above problems, the present invention provides a method for automatic debugging of a tightening device interface, comprising:

[0006] Obtain the hardware interface, connection protocol and manufacturer corresponding to each tightening device;

[0007] The integrated debugging system generates a parsing path for each tightening device in a tree structure of hardware interface, connection protocol, manufacturer and data parsing format from top to bottom, and stores the data parsing path in the integrated debugging knowledge graph, wherein the data parsing format includes: data acquisition format and instruction control format;

[0008] When the integrated debugging system obtains the operation parameters from the data acquisition interface of the tightening equipment to be debugged, the corresponding data acquisition format is queried based on the parsing path corresponding to the tightening equipment to be debugged in the integrated debugging knowledge graph, and the operation parameters are converted into the corresponding data format according to the obtained data acquisition format to obtain the converted acquisition data, and the converted acquisition data is stored in the information system;

[0009] When the integrated debugging system obtains the control instructions of the tightening device to be debugged from the information system, the corresponding instruction control format is queried based on the parsing path corresponding to the tightening device to be debugged in the integrated debugging knowledge graph, and the control instructions of the tightening device to be debugged are converted to the corresponding instruction protocol according to the obtained instruction control format to obtain the converted instructions, and the converted instructions are sent to the corresponding control interface of the tightening device to be debugged for execution.

[0010] Furthermore, in the above method, the corresponding data acquisition format is queried based on the parsing path corresponding to the tightening equipment to be debugged in the integrated debugging knowledge graph, the operation parameters are converted into the corresponding data format according to the obtained data acquisition format to obtain the converted collected data, and the converted collected data is stored in the information system, including:

[0011] Step S31, based on the corresponding data collection format of the analytical path query corresponding to the tightening equipment to be debugged in the integrated debugging knowledge graph,

[0012] Step S32, if the corresponding data acquisition format is found under the parsing path corresponding to the tightening device, the operation parameters are converted into the corresponding data format according to the queried data acquisition format to obtain the converted collected data, and it is determined whether the parsing format of the converted collected data is correct. If it is correct, the converted collected data is stored in the information system; if it is not correct, go to step S33;

[0013] Step S33, if the corresponding data acquisition format is not found under the parsing path corresponding to the tightening device, or if it is judged that the parsing format of the converted collected data is incorrect, then obtain the parsing path corresponding to other tightening devices with the same hardware interface and the same connection protocol as the tightening device to be debugged but from different manufacturers, query the corresponding data acquisition format under the parsing path corresponding to the other tightening devices obtained, perform corresponding data format conversion on the operating parameters according to the obtained data acquisition format to obtain the converted collected data, and judge whether the parsing format of the converted collected data is correct. If correct, store the converted collected data in the information system, and query the corresponding data acquisition format under the parsing path corresponding to other tightening devices with the same hardware interface and the same connection protocol but from different manufacturers, and update it to the parsing path corresponding to the tightening device to be debugged to be queried in the integrated debugging knowledge graph; if incorrect, go to step S34;

[0014] Step S34, obtain the parsing path corresponding to other tightening devices with the same hardware interface as the tightening device to be debugged but different connection protocols and from different manufacturers, query the corresponding data acquisition format under the parsing path corresponding to the other tightening devices obtained, convert the operation parameters into the corresponding data format according to the obtained data acquisition format to obtain the converted acquisition data, and judge whether the parsing format of the converted acquisition data is correct. If correct, store the converted acquisition data in the information system, and query the corresponding data acquisition format under the parsing path corresponding to other tightening devices with the same hardware interface but different connection protocols and from different manufacturers, and update it to the parsing path corresponding to the tightening device to be queried and debugged in the integrated debugging knowledge graph.

[0015] Further, in the above method, the data acquisition format includes: a sequence composed of a plurality of first feature points arranged in sequence; the data acquisition format used in the parsing format of the converted collected data determined to be incorrect includes: a first correct feature point and / or a first erroneous feature point, wherein the parsing format of the collected data converted based on the first correct feature point is partially correct, and the parsing format of the collected data converted based on the first erroneous feature point is partially erroneous;

[0016] Step S34, obtaining the parsing path corresponding to other tightening devices with the same hardware interface as the tightening device to be debugged but with different connection protocols and from different manufacturers, querying the corresponding data acquisition format under the parsing path corresponding to the other tightening devices obtained, converting the operation parameters into the corresponding data format according to the obtained data acquisition format to obtain the converted acquisition data, and judging whether the parsing format of the converted acquisition data is correct, including:

[0017] Acquire a first correct feature point from a data collection format used by the converted collection data whose parsing format is determined to be incorrect;

[0018] Filtering out the first key feature point from each of the first correct feature points obtained according to the importance level;

[0019] Obtain the parsing paths corresponding to other tightening devices with the same hardware interface as the tightening device to be debugged but with different connection protocols and from different manufacturers, and query the corresponding data collection format under the obtained parsing paths corresponding to the other tightening devices;

[0020] According to the number of matches of the first key feature points of the same rank in the sequence of each data collection format, the queried data collection formats are sorted from high to low according to the priority level;

[0021] Each time, the data collection format with the highest current priority is selected, and the operation parameters are converted into corresponding data formats according to the data collection format with the highest current priority to obtain the converted collection data, and it is determined whether the parsing format of the converted collection data is correct.

[0022] Further, in the above method, based on the parsing path corresponding to the tightening device to be debugged in the integrated debugging knowledge graph, the corresponding instruction control format is queried, and the control instruction of the tightening device to be debugged is converted to the corresponding instruction protocol according to the obtained instruction control format to obtain the converted instruction, and the converted instruction is sent to the control interface of the corresponding tightening device to be debugged for execution, including:

[0023] Step S41, querying the corresponding instruction control format based on the parsing path corresponding to the tightening equipment to be debugged in the integrated debugging knowledge graph,

[0024] Step S42, if the corresponding instruction control format is found under the parsing path corresponding to the tightening device to be debugged, the control instruction is converted into the corresponding instruction protocol according to the instruction control format obtained by the query to obtain the converted instruction, and the converted instruction is sent to the control interface of the corresponding tightening device to be debugged for execution, and it is determined whether the execution result is correct. If not, go to step S43;

[0025] Step S43, if the corresponding instruction control format is not found under the parsing path corresponding to the tightening device to be debugged, or if the execution result is judged to be incorrect, then obtain the parsing path corresponding to other tightening devices with the same hardware interface and the same connection protocol as the tightening device to be debugged but from different manufacturers, and query the corresponding instruction control format under the parsing path corresponding to the other tightening devices obtained, perform the corresponding instruction protocol conversion on the control instruction according to the obtained instruction control format to obtain the converted instruction, and send the converted instruction to the control interface of the corresponding tightening device to be debugged for execution, and judge whether the execution result is correct. If correct, query the corresponding instruction control format under the parsing path corresponding to other tightening devices with the same hardware interface and the same connection protocol but from different manufacturers, and update it to the parsing path corresponding to the tightening device to be debugged to be queried in the integrated debugging knowledge graph; if incorrect, go to step S44;

[0026] Step S44, obtain the parsing path corresponding to other tightening devices with the same hardware interface as the tightening device to be debugged but different connection protocols and from different manufacturers, query the corresponding instruction control format under the parsing path corresponding to the other tightening devices obtained, perform corresponding instruction protocol conversion on the control instruction according to the obtained instruction control format to obtain the converted instruction, send the converted instruction to the control interface of the corresponding tightening device to be debugged for execution, and judge whether the execution result is correct. If correct, update the corresponding instruction control format queried under the parsing path corresponding to other tightening devices with the same hardware interface but different connection protocols and from different manufacturers to the parsing path corresponding to the tightening device to be queried and debugged in the integrated debugging knowledge graph.

[0027] Further, in the above method, the instruction control format includes: a sequence composed of a plurality of second characteristic points arranged in sequence; the instruction control format used for the incorrect execution result includes: a second correct characteristic point and / or a second error characteristic point, wherein the execution result of the instruction converted based on the second correct characteristic point is partially correct, and the execution result of the instruction converted based on the second error characteristic point is partially wrong;

[0028] Step S44, obtaining the parsing path corresponding to other tightening devices with the same hardware interface as the tightening device to be debugged but with different connection protocols and from different manufacturers, querying the corresponding instruction control format under the parsing path corresponding to the other tightening devices obtained, performing the corresponding instruction protocol conversion on the control instruction according to the obtained instruction control format to obtain the converted instruction, sending the converted instruction to the control interface of the corresponding tightening device to be debugged for execution, and judging whether the execution result is correct, including:

[0029] Acquire a second correct feature point from an instruction control format used by the converted instruction whose execution result is determined to be incorrect;

[0030] Selecting the second key feature points from each second correct feature point according to the importance level;

[0031] Obtain the parsing path corresponding to other tightening devices with the same hardware interface as the tightening device to be debugged but with different connection protocols and from different manufacturers, and query the corresponding instruction control format under the obtained parsing path corresponding to the other tightening devices;

[0032] According to the number of matches of the second key feature points of the same order in the sequence of each instruction control format, the queried instruction control formats are sorted from high to low according to the priority level;

[0033] Each time, the instruction control format with the highest current priority is selected, and the control instruction is converted to the corresponding instruction protocol according to the instruction control format with the highest current priority to obtain the converted instruction, and the converted instruction is sent to the control interface of the corresponding tightening device to be debugged for execution, and it is determined whether the execution result is correct.

[0034] According to another aspect of the present invention, there is also provided a tightening device interface automatic debugging system, comprising:

[0035] An integrated debugging system is used to obtain the hardware interface, connection protocol and manufacturer corresponding to each tightening device; generate a parsing path for each tightening device according to the tree structure of the hardware interface, connection protocol, manufacturer and data parsing format from top to bottom, and store the data parsing path in the integrated debugging knowledge graph, wherein the data parsing format includes: a data acquisition format and an instruction control format; when the integrated debugging system obtains the operation parameters from the data acquisition interface of the tightening device to be debugged, the corresponding data acquisition format is queried based on the parsing path corresponding to the tightening device to be debugged in the integrated debugging knowledge graph, the operation parameters are converted to the corresponding data format according to the obtained data acquisition format to obtain the converted collected data, and the converted collected data is stored in the information system; when the integrated debugging system obtains the control instruction of the tightening device to be debugged from the information system, the corresponding instruction control format is queried based on the parsing path corresponding to the tightening device to be debugged in the integrated debugging knowledge graph, the control instruction of the tightening device to be debugged is converted to the corresponding instruction protocol according to the obtained instruction control format to obtain the converted instruction, and the converted instruction is sent to the corresponding control interface of the tightening device to be debugged for execution;

[0036] The information system is used to store the converted collected data and send control instructions of the tightening equipment to be debugged to the integrated debugging system.

[0037] Furthermore, in the above system, the integrated debugging system includes:

[0038] The first unit is used for querying the corresponding data collection format based on the parsing path corresponding to the tightening equipment to be debugged in the integrated debugging knowledge graph;

[0039] Unit 12 is used to convert the operation parameters into corresponding data formats according to the data acquisition format obtained by the query if the corresponding data acquisition format is found under the parsing path corresponding to the tightening device, so as to obtain the converted collected data, and to determine whether the parsing format of the converted collected data is correct. If it is correct, the converted collected data is stored in the information system; if it is not correct, the process goes to Unit 13;

[0040] The first three units are used for, if the corresponding data acquisition format is not found under the parsing path corresponding to the tightening device, or if it is judged that the parsing format of the converted collected data is incorrect, obtaining the parsing path corresponding to other tightening devices with the same hardware interface and the same connection protocol as the tightening device to be debugged, but from different manufacturers, querying the corresponding data acquisition format under the parsing path corresponding to the other tightening devices obtained, performing corresponding data format conversion on the operation parameters according to the obtained data acquisition format to obtain the converted collected data, judging whether the parsing format of the converted collected data is correct, and if it is correct, storing the converted collected data in the information system, and querying the corresponding data acquisition format under the parsing path corresponding to other tightening devices with the same hardware interface and the same connection protocol, but from different manufacturers, and updating it to the parsing path corresponding to the tightening device to be queried and debugged in the integrated debugging knowledge graph; if it is incorrect, going to the first four units;

[0041] The first four units are used to obtain the parsing paths corresponding to other tightening devices with the same hardware interface as the tightening device to be debugged but different connection protocols and from different manufacturers, query the corresponding data acquisition format under the parsing path corresponding to the other tightening devices obtained, convert the operation parameters into the corresponding data format according to the obtained data acquisition format to obtain the converted acquisition data, and judge whether the parsing format of the converted acquisition data is correct. If correct, store the converted acquisition data in the information system, and query the corresponding data acquisition format under the parsing path corresponding to other tightening devices with the same hardware interface but different connection protocols and from different manufacturers, and update it to the parsing path corresponding to the tightening device to be queried and debugged in the integrated debugging knowledge graph.

[0042] Furthermore, in the above system, the data acquisition format includes: a sequence composed of a plurality of first feature points arranged in sequence; the data acquisition format used in the parsing format of the converted collected data determined to be incorrect includes: a first correct feature point and / or a first erroneous feature point, wherein the parsing format of the collected data converted based on the first correct feature point is partially correct, and the parsing format of the collected data converted based on the first erroneous feature point is partially erroneous;

[0043] The first four units are used to obtain the first correct feature point from the data collection format used by the converted collected data whose parsing format is judged to be incorrect; screen out the first key feature point from each of the first correct feature points obtained according to the importance level; obtain the parsing path corresponding to other tightening devices with the same hardware interface as the tightening device to be debugged but different connection protocols and different manufacturers, and query the corresponding data collection format under the parsing path corresponding to the other tightening devices obtained; sort the queried data collection formats from high to low according to the priority level according to the number of matches of the first key feature points of the same order in the sequence of each data collection format from more to less; each time, select the data collection format with the highest current priority, and perform corresponding data format conversion on the operation parameters according to the data collection format with the highest current priority to obtain the converted collected data, and judge whether the parsing format of the converted collected data is correct.

[0044] Furthermore, in the above system, the integrated debugging system includes:

[0045] The second unit is used to query the corresponding instruction control format based on the parsing path corresponding to the tightening equipment to be debugged in the integrated debugging knowledge graph;

[0046] Unit 22, if the corresponding instruction control format is found under the parsing path corresponding to the tightening device to be debugged, the control instruction is converted into the corresponding instruction protocol according to the instruction control format obtained by the query to obtain the converted instruction, and the converted instruction is sent to the control interface of the corresponding tightening device to be debugged for execution, and it is judged whether the execution result is correct. If not, it goes to unit 23;

[0047] Unit 23: If the corresponding instruction control format is not found under the parsing path corresponding to the tightening device to be debugged, or the execution result is judged to be incorrect, then the parsing path corresponding to other tightening devices with the same hardware interface and the same connection protocol as the tightening device to be debugged but from different manufacturers is obtained, and the corresponding instruction control format is queried under the parsing path corresponding to the other tightening devices obtained, and the control instruction is converted to the corresponding instruction protocol according to the obtained instruction control format to obtain the converted instruction, and the converted instruction is sent to the control interface of the corresponding tightening device to be debugged for execution, and it is judged whether the execution result is correct. If it is correct, the corresponding instruction control format is queried under the parsing path corresponding to other tightening devices with the same hardware interface and the same connection protocol but from different manufacturers, and updated to the parsing path corresponding to the tightening device to be debugged to be queried in the integrated debugging knowledge graph; if it is incorrect, go to Unit 24;

[0048] The second and fourth units obtain the parsing paths corresponding to other tightening devices with the same hardware interface as the tightening device to be debugged but different connection protocols and from different manufacturers, query the corresponding instruction control format under the parsing path corresponding to the other tightening devices obtained, convert the control instructions to the corresponding instruction protocol according to the obtained instruction control format to obtain the converted instructions, send the converted instructions to the control interface of the corresponding tightening device to be debugged for execution, and judge whether the execution result is correct. If correct, update the corresponding instruction control format queried under the parsing path corresponding to other tightening devices with the same hardware interface but different connection protocols and from different manufacturers to the parsing path corresponding to the tightening device to be queried and debugged in the integrated debugging knowledge graph.

[0049] Further, in the above system, the instruction control format includes: a sequence composed of a plurality of second characteristic points arranged in sequence; the instruction control format used for the incorrect execution result includes: a second correct characteristic point and / or a second error characteristic point, wherein the execution result of the instruction converted based on the second correct characteristic point is partially correct, and the execution result of the instruction converted based on the second error characteristic point is partially wrong;

[0050] The second fourth unit is used to obtain the second correct feature point from the instruction control format used by the converted instruction that is judged to have an incorrect execution result; screen out the second key feature point from each second correct feature point according to the importance level; obtain the parsing path corresponding to other tightening devices with the same hardware interface as the tightening device to be debugged but different connection protocol and different manufacturer, and query the corresponding instruction control format under the parsing path corresponding to the other tightening devices obtained; sort the queried instruction control formats from high to low according to the priority level according to the number of matches of the second key feature points of the same order in the sequence of each instruction control format; each time select the instruction control format with the highest current priority, perform the corresponding instruction protocol conversion on the control instruction according to the instruction control format with the highest current priority to obtain the converted instruction, send the converted instruction to the control interface of the corresponding tightening device to be debugged for execution, and judge whether the execution result is correct.

[0051] Compared with the prior art, the present invention selects three knowledge subjects, namely hardware interface, connection protocol and manufacturer information, to construct a knowledge graph based on the business and data characteristics of the tightening equipment. The present invention adopts the knowledge graph method to construct a tightening intelligent debugging system with autonomous learning, which improves the efficiency of tightening debugging and the stability of final data access. The present invention can be used to solve the problem of efficient and stable integrated debugging of multi-variety, multi-protocol and multi-format data in the integration of tightening equipment and information systems. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] Figure 1 It is a principle diagram of an automatic debugging method for a tightening device interface according to an embodiment of the present invention;

[0053] Figure 2 is a schematic diagram of the connection between the middleware, the tightening equipment and the information system according to an embodiment of the present invention;

[0054] Figure 3 is a schematic diagram of an example of a knowledge graph according to an embodiment of the present invention;

[0055] Figure 4 This is a flowchart of updating a knowledge graph according to an embodiment of the present invention. DETAILED DESCRIPTION

[0056] In order to make the above-mentioned objects, features and advantages of the present invention more obvious and easy to understand, the present invention is further described in detail below with reference to the accompanying drawings and specific embodiments.

[0057] like Figures 1 to 4 As shown, the present invention provides a method for automatic debugging of a tightening device interface, comprising:

[0058] Step S1, obtaining the hardware interface, connection protocol and manufacturer corresponding to each tightening device;

[0059] Here, the tightening device may be, for example, a semi-automatic or automated tightening gun having a data acquisition interface;

[0060] like Figure 1 As shown, it may include: a data acquisition interface and a device control interface, wherein the data acquisition interface is a data output interface provided by the tightening device, which can output parameters such as output torque and operation time in the tightening operation; the device control interface is a data output interface provided by the tightening device, which can obtain operation instructions: such as shutdown, startup, start, torque range adjustment, etc.;

[0061] Step S2, the integrated debugging system generates a parsing path for each tightening device in a tree structure of hardware interface, connection protocol, manufacturer and data parsing format from top to bottom, and stores the data parsing path into the integrated debugging knowledge graph, wherein the data parsing format includes: data acquisition format and instruction control format;

[0062] Here, if Figure 1 As shown, the integrated debugging system may include: a hardware interface selection unit, a connection protocol selection unit, a device manufacturer selection unit, an integrated debugging knowledge graph unit, a data instruction receiving unit, an instruction protocol conversion unit and a data analysis and confirmation unit.

[0063] Among them, the hardware interface selection unit can be used to select the interface mode used for data access of the tightening equipment: such as network port, RS232, etc.;

[0064] The connection protocol selection unit can be used to select the connection protocol used for data access of the tightening equipment: QMTT, Modbus, Profinet, CC-Link, etc.

[0065] Equipment manufacturer selection unit, used to select the source manufacturer of the tightening equipment;

[0066] The integrated debugging knowledge graph unit is used to generate the following information based on the hardware interface selection unit, the connection protocol selection unit, and the device manufacturer selection unit: Figure 3 The integrated debugging knowledge graph shown;

[0067] The data instruction receiving unit is used to receive the control instruction of the tightening lower system, and the tightening lower system sends the control instruction package to the integrated debugging system through the API interface.

[0068] Instruction protocol conversion is used for the integrated debugging system to convert the received instruction data format according to the integrated debugging knowledge graph and send it to the tightening equipment.

[0069] Data analysis and confirmation, as the interactive interface of the debugger, after obtaining the output data of the integrated debugging knowledge graph, compare it with the expected business goals, correct the output data and form the new information into new knowledge in the knowledge graph.

[0070] Specifically, when the hardware interface matches, the integrated debugging system can provide the supported connection protocols according to the hardware interface;

[0071] When the connection protocol matches, the integrated debugging system can provide all the vendor information under the connection protocol according to the connection protocol;

[0072] When the manufacturer information matches, the integrated debugging system can provide the device data collection format and instruction control format according to the manufacturer information;

[0073] Step S3, when the integrated debugging system obtains the operation parameters from the data acquisition interface of the tightening device to be debugged, the corresponding data acquisition format is queried based on the parsing path corresponding to the tightening device to be debugged in the integrated debugging knowledge graph, and the operation parameters are converted into the corresponding data format according to the obtained data acquisition format to obtain the converted acquisition data, and the converted acquisition data is stored in the information system;

[0074] Here, the information system, for example, can be a tightening lower-level system of a factory or workshop, which is mainly responsible for the management of tightening guns and the data collection and storage of tightening operations.

[0075] like Figure 1 As shown, the information system may include: a real-time acquisition and storage unit and a device control instruction unit.

[0076] The real-time acquisition and storage unit is used to obtain and store tightening data through the API provided by the integrated debugging system and the information system.

[0077] The equipment control instruction unit is used for the lower system of the tightening equipment to receive the operator's action requirements for the equipment and convert them into equipment control instruction data.

[0078] Step S4, when the integrated debugging system obtains the control instructions of the tightening device to be debugged from the information system, the corresponding instruction control format is queried based on the parsing path corresponding to the tightening device to be debugged in the integrated debugging knowledge graph, and the control instructions of the tightening device to be debugged are converted to the corresponding instruction protocol according to the obtained instruction control format to obtain the converted instructions, and the converted instructions are sent to the corresponding control interface of the tightening device to be debugged for execution.

[0079] Here, examples of the connection between the integrated commissioning system and the tightening equipment and the information system are shown, such as Figure 2 As shown, the data interface of the integrated debugging system is the data transmission interface between the tightening equipment and the integrated debugging system, and the integrated debugging system and the information system; the debugging interface of the integrated debugging system is the adjustment interface for the operator to confirm the output data and the output analysis.

[0080] According to the business and data characteristics of tightening equipment, the present invention selects three knowledge subjects, namely hardware interface, connection protocol and manufacturer information, to construct a knowledge graph. Figure 3 To organize knowledge graph data, you can refer to Figure 4 Use knowledge graph data.

[0081] The present invention adopts the knowledge graph method to construct a tightening intelligent debugging system with autonomous learning, which improves the efficiency of tightening debugging and the stability of final data access. The present invention can be used to solve the problem of efficient and stable integration and debugging of multi-variety, multi-protocol and multi-format data in the integration of tightening equipment and information system.

[0082] In one embodiment of the method for automatic debugging of the tightening device interface of the present invention, step S3, based on the analytical path corresponding to the tightening device to be debugged in the integrated debugging knowledge graph, queries the corresponding data acquisition format, converts the operation parameters into the corresponding data format according to the obtained data acquisition format to obtain the converted collected data, and stores the converted collected data into the information system, including:

[0083] Step S31, based on the corresponding data collection format of the analytical path query corresponding to the tightening equipment to be debugged in the integrated debugging knowledge graph,

[0084] Step S32, if the corresponding data acquisition format is found under the parsing path corresponding to the tightening device, the operation parameters are converted into the corresponding data format according to the queried data acquisition format to obtain the converted collected data, and it is determined whether the parsing format of the converted collected data is correct. If it is correct, the converted collected data is stored in the information system; if it is not correct, go to step S33;

[0085] Step S33, if the corresponding data acquisition format is not found under the parsing path corresponding to the tightening device, or if it is judged that the parsing format of the converted collected data is incorrect, then obtain the parsing path corresponding to other tightening devices with the same hardware interface and the same connection protocol as the tightening device to be debugged but from different manufacturers, query the corresponding data acquisition format under the parsing path corresponding to the other tightening devices obtained, perform corresponding data format conversion on the operating parameters according to the obtained data acquisition format to obtain the converted collected data, and judge whether the parsing format of the converted collected data is correct. If correct, store the converted collected data in the information system, and query the corresponding data acquisition format under the parsing path corresponding to other tightening devices with the same hardware interface and the same connection protocol but from different manufacturers, and update it to the parsing path corresponding to the tightening device to be debugged to be queried in the integrated debugging knowledge graph; if incorrect, go to step S34;

[0086] Here, by querying the corresponding data acquisition format under the parsing path corresponding to other tightening devices with the same hardware interface and the same connection protocol but different manufacturers with the correct parsing format, updating it to the parsing path corresponding to the tightening device to be queried and debugged in the integrated debugging knowledge graph, so as to save the correct data acquisition format to the parsing path corresponding to the tightening device to be debugged, it can be ensured that the tightening device with the same hardware interface, the same connection protocol and the same manufacturer can be directly retrieved and used next time, avoiding repeated debugging and improving data parsing efficiency;

[0087] In addition, if the collected data converted by the high-priority data collection format is incorrect under the parsing path corresponding to other tightening devices with the same hardware interface and the same connection protocol as the tightening device to be debugged but from different manufacturers, the converted collected data can be converted by the lower-priority data collection format, and then it can be determined whether the converted collected data is correct;

[0088] Step S34, obtain the parsing path corresponding to other tightening devices with the same hardware interface as the tightening device to be debugged but different connection protocols and from different manufacturers, query the corresponding data acquisition format under the parsing path corresponding to the other tightening devices obtained, convert the operation parameters into the corresponding data format according to the obtained data acquisition format to obtain the converted acquisition data, and judge whether the parsing format of the converted acquisition data is correct. If correct, store the converted acquisition data in the information system, and query the corresponding data acquisition format under the parsing path corresponding to other tightening devices with the same hardware interface but different connection protocols and from different manufacturers, and update it to the parsing path corresponding to the tightening device to be queried and debugged in the integrated debugging knowledge graph.

[0089] Here, by querying the corresponding data acquisition format under the parsing path corresponding to other tightening devices with the correct parsing format, the same hardware interface but different connection protocols, and different manufacturers, and updating it to the parsing path corresponding to the tightening device to be queried and debugged in the integrated debugging knowledge graph, so that the correct data acquisition format can be saved in the parsing path corresponding to the tightening device to be debugged, it can be ensured that the tightening device with the same hardware interface, the same connection protocol, and the same manufacturer can be directly retrieved and used next time, avoiding repeated debugging and improving data parsing efficiency.

[0090] In one embodiment of the method for automatic debugging of the tightening device interface of the present invention, the data acquisition format includes: a sequence composed of a plurality of first characteristic points arranged in sequence; the data acquisition format adopted by the parsing format of the converted collected data judged to be incorrect includes: a first correct characteristic point and / or a first error characteristic point, wherein the parsing format of the collected data converted based on the first correct characteristic point is partially correct, and the parsing format of the collected data converted based on the first error characteristic point is partially wrong;

[0091] Here, data analysis is performed in sequence. During the data analysis process, the integrated debugging system divides the data acquisition format, such as in the existing data acquisition format A: 1-2 digits represent the first characteristic point of the model, 3-4 digits represent the first characteristic point of the rated voltage, 5-6 digits represent the first characteristic point of the rated current, 7-8 digits represent the first characteristic point of the rated torque, 9-10 digits represent the first characteristic point of the real-time voltage, 11-12 digits represent the first characteristic point of the real-time current, and 13-14 digits represent the first characteristic point of the real-time torque. The collected data will be divided by the first characteristic point, and the result information after analysis will be provided.

[0092] Step S34, obtaining the parsing path corresponding to other tightening devices with the same hardware interface as the tightening device to be debugged but with different connection protocols and from different manufacturers, querying the corresponding data acquisition format under the parsing path corresponding to the other tightening devices obtained, converting the operation parameters into the corresponding data format according to the obtained data acquisition format to obtain the converted acquisition data, and judging whether the parsing format of the converted acquisition data is correct, including:

[0093] Step S341, obtaining a first correct feature point from the data collection format adopted by the converted collection data whose parsing format is determined to be incorrect;

[0094] Step S342, selecting the first key feature point from each of the acquired first correct feature points according to the importance level;

[0095] Step S343, obtaining the parsing paths corresponding to other tightening devices with the same hardware interface as the tightening device to be debugged but with different connection protocols and from different manufacturers, and querying the corresponding data collection format under the obtained parsing paths corresponding to the other tightening devices;

[0096] Step S344, sorting the queried data collection formats from high to low in terms of priority according to the number of matches of the first key feature points of the same rank in the sequence of each data collection format from large to small;

[0097] Step S345, each time the data acquisition format with the highest current priority is selected, and the operation parameters are converted into the corresponding data format according to the data acquisition format with the highest current priority to obtain the converted acquisition data, and it is determined whether the parsing format of the converted acquisition data is correct.

[0098] Here, if the collected data converted by adopting the high-priority data collection format is incorrect, the converted collected data may be further converted by adopting the low-priority data collection format, and then it is determined whether the converted collected data is correct.

[0099] If the first feature point is obtained from the data collection format used by the converted collected data that is judged to be incorrect from the parsing format, the information of the first feature points of 1-2, 7-8, and 13-14 is correct, and the first feature points of other positions are incorrect; the first feature points of 1-2, 7-8, and 13-14 are used as the first key feature points;

[0100] The integrated debugging system will give priority to the first correct feature point matching more existing data acquisition format B: 1-2 digits represent the model, 3-4 digits represent the rated current, 5-6 digits represent the rated voltage, 7-8 digits represent the rated torque, 9-10 digits represent the real-time current, 11-12 digits represent the real-time voltage, 13-14 digits represent the real-time torque, etc.;

[0101] Secondly, if the existing data acquisition format B is used to convert the operating parameters into the corresponding data format to obtain the converted acquisition data, and the parsing format of the converted acquisition data is incorrect, the existing data acquisition format C with fewer first correct feature point matches can be considered: 1-2 digits represent the manufacturer, 3-4 digits represent the type, 5 digits represent the equipment model, 6 digits represent the equipment number, 7-8 digits represent the rated torque, 9-10 digits represent the rated voltage, 11-12 digits represent the rated voltage, 13-14 digits represent the real-time torque, 15-16 digits represent the rated torque, 17-18 digits represent the rated voltage, etc.

[0102] In one embodiment of the method for automatic debugging of the tightening device interface of the present invention, step S4, based on the analytical path corresponding to the tightening device to be debugged in the integrated debugging knowledge graph, queries the corresponding instruction control format, performs corresponding instruction protocol conversion on the control instruction of the tightening device to be debugged according to the obtained instruction control format to obtain the converted instruction, and sends the converted instruction to the control interface of the corresponding tightening device to be debugged for execution, including:

[0103] Step S41, querying the corresponding instruction control format based on the parsing path corresponding to the tightening equipment to be debugged in the integrated debugging knowledge graph,

[0104] Step S42, if the corresponding instruction control format is found under the parsing path corresponding to the tightening device to be debugged, the control instruction is converted into the corresponding instruction protocol according to the instruction control format obtained by the query to obtain the converted instruction, and the converted instruction is sent to the control interface of the corresponding tightening device to be debugged for execution, and it is determined whether the execution result is correct. If not, go to step S43;

[0105] Step S43, if the corresponding instruction control format is not found under the parsing path corresponding to the tightening device to be debugged, or if the execution result is judged to be incorrect, then obtain the parsing path corresponding to other tightening devices with the same hardware interface and the same connection protocol as the tightening device to be debugged but from different manufacturers, and query the corresponding instruction control format under the parsing path corresponding to the other tightening devices obtained, perform the corresponding instruction protocol conversion on the control instruction according to the obtained instruction control format to obtain the converted instruction, and send the converted instruction to the control interface of the corresponding tightening device to be debugged for execution, and judge whether the execution result is correct. If correct, query the corresponding instruction control format under the parsing path corresponding to other tightening devices with the same hardware interface and the same connection protocol but from different manufacturers, and update it to the parsing path corresponding to the tightening device to be debugged to be queried in the integrated debugging knowledge graph; if incorrect, go to step S44;

[0106] Here, by querying the corresponding instruction control format under the parsing path corresponding to other tightening devices with the same hardware interface and the same connection protocol but different manufacturers with the correct execution result, updating it to the parsing path corresponding to the tightening device to be queried and debugged in the integrated debugging knowledge graph, so as to save the correct instruction control format to the parsing path corresponding to the tightening device to be debugged, it can be ensured that the tightening device with the same hardware interface, the same connection protocol and the same manufacturer is directly retrieved and used next time, avoiding repeated debugging and improving data parsing efficiency;

[0107] In addition, when the execution result of the instruction converted by the high-priority instruction control format is incorrect under the parsing path corresponding to other tightening devices with the same hardware interface and the same connection protocol as the tightening device to be debugged but from different manufacturers, the instruction control format with the lower priority can be further used for conversion, and then it can be determined whether the execution result is correct;

[0108] Step S44, obtain the parsing path corresponding to other tightening devices with the same hardware interface as the tightening device to be debugged but different connection protocols and from different manufacturers, query the corresponding instruction control format under the parsing path corresponding to the other tightening devices obtained, perform corresponding instruction protocol conversion on the control instruction according to the obtained instruction control format to obtain the converted instruction, send the converted instruction to the control interface of the corresponding tightening device to be debugged for execution, and judge whether the execution result is correct. If correct, update the corresponding instruction control format queried under the parsing path corresponding to other tightening devices with the same hardware interface but different connection protocols and from different manufacturers to the parsing path corresponding to the tightening device to be queried and debugged in the integrated debugging knowledge graph.

[0109] Here, by querying the corresponding instruction control format under the parsing path corresponding to other tightening devices with the same hardware interface but different connection protocols and different manufacturers with correct execution results, and updating it to the parsing path corresponding to the tightening device to be queried and debugged in the integrated debugging knowledge graph, so as to save the correct instruction control format to the parsing path corresponding to the tightening device to be debugged, it can be ensured that the tightening device with the same hardware interface, the same connection protocol and the same manufacturer can be directly retrieved and used next time, avoiding repeated debugging and improving data parsing efficiency.

[0110] In one embodiment of the method for automatic debugging of the tightening device interface of the present invention, the instruction control format includes: a sequence composed of a plurality of second characteristic points arranged in sequence; the instruction control format used for the incorrect execution result includes: a second correct characteristic point and / or a second error characteristic point, wherein the execution result of the instruction converted based on the second correct characteristic point is partially correct, and the execution result of the instruction converted based on the second error characteristic point is partially wrong;

[0111] Here, data analysis is performed in sequence. During the data analysis process, the integrated debugging system divides the data acquisition format, such as in the existing data acquisition format A: 1-2 digits represent the first characteristic point of the model, 3-4 digits represent the second characteristic point of the rated voltage, 5-6 digits represent the second characteristic point of the rated current, 7-8 digits represent the second characteristic point of the rated torque, 9-10 digits represent the second characteristic point of the real-time voltage, 11-12 digits represent the second characteristic point of the real-time current, and 13-14 digits represent the second characteristic point of the real-time torque. The collected data will be divided according to the second characteristic point, and the result information after analysis will be provided.

[0112] Step S44, obtaining the parsing path corresponding to other tightening devices with the same hardware interface as the tightening device to be debugged but with different connection protocols and from different manufacturers, querying the corresponding instruction control format under the parsing path corresponding to the other tightening devices obtained, performing the corresponding instruction protocol conversion on the control instruction according to the obtained instruction control format to obtain the converted instruction, sending the converted instruction to the control interface of the corresponding tightening device to be debugged for execution, and judging whether the execution result is correct, including:

[0113] Step S441, obtaining a second correct feature point from the instruction control format used by the converted instruction whose execution result is determined to be incorrect;

[0114] Step S442, selecting second key feature points from each second correct feature point according to the importance level;

[0115] Step S443, obtaining the parsing paths corresponding to other tightening devices with the same hardware interface as the tightening device to be debugged but with different connection protocols and from different manufacturers, and querying the corresponding instruction control format under the obtained parsing paths corresponding to the other tightening devices;

[0116] Step S444, sorting the queried instruction control formats in descending order of priority according to the number of matches of the second key feature points of the same order in the sequence of each instruction control format;

[0117] Step S445, each time select the instruction control format with the highest current priority, perform corresponding instruction protocol conversion on the control instruction according to the instruction control format with the highest current priority to obtain the converted instruction, send the converted instruction to the control interface of the corresponding tightening device to be debugged for execution, and judge whether the execution result is correct.

[0118] Here, when the execution result of the instruction converted by the high-priority instruction control format is incorrect, the instruction control format of the second-priority instruction may be further converted, and then it is determined whether the execution result is correct.

[0119] According to another aspect of the present invention, there is also provided a tightening device interface automatic debugging system, comprising:

[0120] An integrated debugging system is used to obtain the hardware interface, connection protocol and manufacturer corresponding to each tightening device; generate a parsing path for each tightening device according to the tree structure of the hardware interface, connection protocol, manufacturer and data parsing format from top to bottom, and store the data parsing path in the integrated debugging knowledge graph, wherein the data parsing format includes: a data acquisition format and an instruction control format; when the integrated debugging system obtains the operation parameters from the data acquisition interface of the tightening device to be debugged, the corresponding data acquisition format is queried based on the parsing path corresponding to the tightening device to be debugged in the integrated debugging knowledge graph, the operation parameters are converted to the corresponding data format according to the obtained data acquisition format to obtain the converted collected data, and the converted collected data is stored in the information system; when the integrated debugging system obtains the control instruction of the tightening device to be debugged from the information system, the corresponding instruction control format is queried based on the parsing path corresponding to the tightening device to be debugged in the integrated debugging knowledge graph, the control instruction of the tightening device to be debugged is converted to the corresponding instruction protocol according to the obtained instruction control format to obtain the converted instruction, and the converted instruction is sent to the corresponding control interface of the tightening device to be debugged for execution;

[0121] The information system is used to store the converted collected data and send control instructions of the tightening equipment to be debugged to the integrated debugging system.

[0122] Furthermore, in the above system, the integrated debugging system includes:

[0123] The first unit is used for querying the corresponding data collection format based on the parsing path corresponding to the tightening equipment to be debugged in the integrated debugging knowledge graph;

[0124] Unit 12 is used to convert the operation parameters into corresponding data formats according to the data acquisition format obtained by the query if the corresponding data acquisition format is found under the parsing path corresponding to the tightening device, so as to obtain the converted collected data, and to determine whether the parsing format of the converted collected data is correct. If it is correct, the converted collected data is stored in the information system; if it is not correct, the process goes to Unit 13;

[0125] The first three units are used for, if the corresponding data acquisition format is not found under the parsing path corresponding to the tightening device, or if it is judged that the parsing format of the converted collected data is incorrect, obtaining the parsing path corresponding to other tightening devices with the same hardware interface and the same connection protocol as the tightening device to be debugged, but from different manufacturers, querying the corresponding data acquisition format under the parsing path corresponding to the other tightening devices obtained, performing corresponding data format conversion on the operation parameters according to the obtained data acquisition format to obtain the converted collected data, judging whether the parsing format of the converted collected data is correct, and if it is correct, storing the converted collected data in the information system, and querying the corresponding data acquisition format under the parsing path corresponding to other tightening devices with the same hardware interface and the same connection protocol, but from different manufacturers, and updating it to the parsing path corresponding to the tightening device to be queried and debugged in the integrated debugging knowledge graph; if it is incorrect, going to the first four units;

[0126] The first four units are used to obtain the parsing paths corresponding to other tightening devices with the same hardware interface as the tightening device to be debugged but different connection protocols and from different manufacturers, query the corresponding data acquisition format under the parsing path corresponding to the other tightening devices obtained, convert the operation parameters into the corresponding data format according to the obtained data acquisition format to obtain the converted acquisition data, and judge whether the parsing format of the converted acquisition data is correct. If correct, store the converted acquisition data in the information system, and query the corresponding data acquisition format under the parsing path corresponding to other tightening devices with the same hardware interface but different connection protocols and from different manufacturers, and update it to the parsing path corresponding to the tightening device to be queried and debugged in the integrated debugging knowledge graph.

[0127] Furthermore, in the above system, the data acquisition format includes: a sequence composed of a plurality of first feature points arranged in sequence; the data acquisition format used in the parsing format of the converted collected data determined to be incorrect includes: a first correct feature point and / or a first erroneous feature point, wherein the parsing format of the collected data converted based on the first correct feature point is partially correct, and the parsing format of the collected data converted based on the first erroneous feature point is partially erroneous;

[0128] The first four units are used to obtain the first correct feature point from the data collection format used by the converted collected data whose parsing format is judged to be incorrect; screen out the first key feature point from each of the first correct feature points obtained according to the importance level; obtain the parsing path corresponding to other tightening devices with the same hardware interface as the tightening device to be debugged but different connection protocols and different manufacturers, and query the corresponding data collection format under the parsing path corresponding to the other tightening devices obtained; sort the queried data collection formats from high to low according to the priority level according to the number of matches of the first key feature points of the same order in the sequence of each data collection format from more to less; each time, select the data collection format with the highest current priority, and perform corresponding data format conversion on the operation parameters according to the data collection format with the highest current priority to obtain the converted collected data, and judge whether the parsing format of the converted collected data is correct.

[0129] Furthermore, in the above system, the integrated debugging system includes:

[0130] The second unit is used to query the corresponding instruction control format based on the parsing path corresponding to the tightening equipment to be debugged in the integrated debugging knowledge graph;

[0131] Unit 22, if the corresponding instruction control format is found under the parsing path corresponding to the tightening device to be debugged, the control instruction is converted into the corresponding instruction protocol according to the instruction control format obtained by the query to obtain the converted instruction, and the converted instruction is sent to the control interface of the corresponding tightening device to be debugged for execution, and it is judged whether the execution result is correct. If not, it goes to unit 23;

[0132] Unit 23: If the corresponding instruction control format is not found under the parsing path corresponding to the tightening device to be debugged, or the execution result is judged to be incorrect, then the parsing path corresponding to other tightening devices with the same hardware interface and the same connection protocol as the tightening device to be debugged but from different manufacturers is obtained, and the corresponding instruction control format is queried under the parsing path corresponding to the other tightening devices obtained, and the control instruction is converted to the corresponding instruction protocol according to the obtained instruction control format to obtain the converted instruction, and the converted instruction is sent to the control interface of the corresponding tightening device to be debugged for execution, and it is judged whether the execution result is correct. If it is correct, the corresponding instruction control format is queried under the parsing path corresponding to other tightening devices with the same hardware interface and the same connection protocol but from different manufacturers, and updated to the parsing path corresponding to the tightening device to be debugged to be queried in the integrated debugging knowledge graph; if it is incorrect, go to Unit 24;

[0133] The second and fourth units obtain the parsing paths corresponding to other tightening devices with the same hardware interface as the tightening device to be debugged but different connection protocols and from different manufacturers, query the corresponding instruction control format under the parsing path corresponding to the other tightening devices obtained, convert the control instructions to the corresponding instruction protocol according to the obtained instruction control format to obtain the converted instructions, send the converted instructions to the control interface of the corresponding tightening device to be debugged for execution, and judge whether the execution result is correct. If correct, update the corresponding instruction control format queried under the parsing path corresponding to other tightening devices with the same hardware interface but different connection protocols and from different manufacturers to the parsing path corresponding to the tightening device to be queried and debugged in the integrated debugging knowledge graph.

[0134] Further, in the above system, the instruction control format includes: a sequence composed of a plurality of second characteristic points arranged in sequence; the instruction control format used for the incorrect execution result includes: a second correct characteristic point and / or a second error characteristic point, wherein the execution result of the instruction converted based on the second correct characteristic point is partially correct, and the execution result of the instruction converted based on the second error characteristic point is partially wrong;

[0135] The second fourth unit is used to obtain the second correct feature point from the instruction control format used by the converted instruction that is judged to have an incorrect execution result; screen out the second key feature point from each second correct feature point according to the importance level; obtain the parsing path corresponding to other tightening devices with the same hardware interface as the tightening device to be debugged but different connection protocol and different manufacturer, and query the corresponding instruction control format under the parsing path corresponding to the other tightening devices obtained; sort the queried instruction control formats from high to low according to the priority level according to the number of matches of the second key feature points of the same order in the sequence of each instruction control format; each time select the instruction control format with the highest current priority, perform the corresponding instruction protocol conversion on the control instruction according to the instruction control format with the highest current priority to obtain the converted instruction, send the converted instruction to the control interface of the corresponding tightening device to be debugged for execution, and judge whether the execution result is correct.

[0136] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

[0137] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

[0138] Obviously, those skilled in the art can make various changes and modifications to the invention without departing from the spirit and scope of the invention. Thus, if these modifications and variations of the invention fall within the scope of the claims of the invention and their equivalents, the invention is also intended to include these modifications and variations.

Claims

1. A method for automatic debugging of a tightening device interface, characterized in that: include: Obtain the hardware interface, connection protocol and manufacturer corresponding to each tightening device; The integrated debugging system generates a parsing path for each tightening device in a tree structure of hardware interface, connection protocol, manufacturer and data parsing format from top to bottom, and stores the data parsing path in the integrated debugging knowledge graph, wherein the data parsing format includes: data acquisition format and instruction control format; When the integrated debugging system obtains the operation parameters from the data acquisition interface of the tightening equipment to be debugged, the corresponding data acquisition format is queried based on the parsing path corresponding to the tightening equipment to be debugged in the integrated debugging knowledge graph, and the operation parameters are converted into the corresponding data format according to the obtained data acquisition format to obtain the converted acquisition data, and the converted acquisition data is stored in the information system; When the integrated debugging system obtains the control instructions of the tightening device to be debugged from the information system, the corresponding instruction control format is queried based on the parsing path corresponding to the tightening device to be debugged in the integrated debugging knowledge graph, and the control instructions of the tightening device to be debugged are converted to the corresponding instruction protocol according to the obtained instruction control format to obtain the converted instructions, and the converted instructions are sent to the corresponding control interface of the tightening device to be debugged for execution.

2. The method for automatic debugging of the tightening device interface according to claim 1, characterized in that: Based on the analytical path corresponding to the tightening equipment to be debugged in the integrated debugging knowledge graph, the corresponding data acquisition format is queried, and the operation parameters are converted into the corresponding data format according to the obtained data acquisition format to obtain the converted acquisition data, and the converted acquisition data is stored in the information system, including: Step S31, based on the corresponding data collection format of the analytical path query corresponding to the tightening equipment to be debugged in the integrated debugging knowledge graph, Step S32, if the corresponding data acquisition format is found under the parsing path corresponding to the tightening device, the operation parameters are converted into the corresponding data format according to the queried data acquisition format to obtain the converted collected data, and it is determined whether the parsing format of the converted collected data is correct. If it is correct, the converted collected data is stored in the information system; if it is not correct, go to step S33; Step S33, if the corresponding data acquisition format is not found under the parsing path corresponding to the tightening device, or if it is judged that the parsing format of the converted collected data is incorrect, then obtain the parsing path corresponding to other tightening devices with the same hardware interface and the same connection protocol as the tightening device to be debugged but from different manufacturers, query the corresponding data acquisition format under the parsing path corresponding to the other tightening devices obtained, perform corresponding data format conversion on the operating parameters according to the obtained data acquisition format to obtain the converted collected data, and judge whether the parsing format of the converted collected data is correct. If correct, store the converted collected data in the information system, and query the corresponding data acquisition format under the parsing path corresponding to other tightening devices with the same hardware interface and the same connection protocol but from different manufacturers, and update it to the parsing path corresponding to the tightening device to be debugged to be queried in the integrated debugging knowledge graph; if incorrect, go to step S34; Step S34, obtain the parsing path corresponding to other tightening devices with the same hardware interface as the tightening device to be debugged but different connection protocols and from different manufacturers, query the corresponding data acquisition format under the parsing path corresponding to the other tightening devices obtained, convert the operation parameters into the corresponding data format according to the obtained data acquisition format to obtain the converted acquisition data, and judge whether the parsing format of the converted acquisition data is correct. If correct, store the converted acquisition data in the information system, and query the corresponding data acquisition format under the parsing path corresponding to other tightening devices with the same hardware interface but different connection protocols and from different manufacturers, and update it to the parsing path corresponding to the tightening device to be queried and debugged in the integrated debugging knowledge graph.

3. The method for automatic debugging of the tightening device interface according to claim 2, characterized in that: The data acquisition format includes: a sequence composed of a plurality of first feature points arranged in sequence; the data acquisition format used by the parsing format of the converted collected data determined to be incorrect includes: a first correct feature point and / or a first erroneous feature point, wherein the parsing format of the collected data converted based on the first correct feature point is partially correct, and the parsing format of the collected data converted based on the first erroneous feature point is partially erroneous; Step S34, obtaining the parsing path corresponding to other tightening devices with the same hardware interface as the tightening device to be debugged but with different connection protocols and from different manufacturers, querying the corresponding data acquisition format under the parsing path corresponding to the other tightening devices obtained, converting the operation parameters into the corresponding data format according to the obtained data acquisition format to obtain the converted acquisition data, and judging whether the parsing format of the converted acquisition data is correct, including: Acquire a first correct feature point from a data collection format used by the converted collection data whose parsing format is determined to be incorrect; Filtering out the first key feature point from each of the first correct feature points obtained according to the importance level; Obtain the parsing paths corresponding to other tightening devices with the same hardware interface as the tightening device to be debugged but with different connection protocols and from different manufacturers, and query the corresponding data collection format under the obtained parsing paths corresponding to the other tightening devices; According to the number of matches of the first key feature points of the same rank in the sequence of each data collection format, the queried data collection formats are sorted from high to low according to the priority level; Each time, the data collection format with the highest current priority is selected, and the operation parameters are converted into corresponding data formats according to the data collection format with the highest current priority to obtain the converted collection data, and it is determined whether the parsing format of the converted collection data is correct.

4. The method for automatic debugging of the tightening device interface according to claim 1, characterized in that: Based on the parsing path corresponding to the tightening device to be debugged in the integrated debugging knowledge graph, the corresponding instruction control format is queried, and the control instruction of the tightening device to be debugged is converted to the corresponding instruction protocol according to the obtained instruction control format to obtain the converted instruction, and the converted instruction is sent to the control interface of the corresponding tightening device to be debugged for execution, including: Step S41, querying the corresponding instruction control format based on the parsing path corresponding to the tightening equipment to be debugged in the integrated debugging knowledge graph, Step S42, if the corresponding instruction control format is found under the parsing path corresponding to the tightening device to be debugged, the control instruction is converted into the corresponding instruction protocol according to the instruction control format obtained by the query to obtain the converted instruction, and the converted instruction is sent to the control interface of the corresponding tightening device to be debugged for execution, and it is determined whether the execution result is correct. If not, go to step S43; Step S43, if the corresponding instruction control format is not found under the parsing path corresponding to the tightening device to be debugged, or if the execution result is judged to be incorrect, then obtain the parsing path corresponding to other tightening devices with the same hardware interface and the same connection protocol as the tightening device to be debugged but from different manufacturers, and query the corresponding instruction control format under the parsing path corresponding to the other tightening devices obtained, perform the corresponding instruction protocol conversion on the control instruction according to the obtained instruction control format to obtain the converted instruction, and send the converted instruction to the control interface of the corresponding tightening device to be debugged for execution, and judge whether the execution result is correct. If correct, query the corresponding instruction control format under the parsing path corresponding to other tightening devices with the same hardware interface and the same connection protocol but from different manufacturers, and update it to the parsing path corresponding to the tightening device to be debugged to be queried in the integrated debugging knowledge graph; if incorrect, go to step S44; Step S44, obtain the parsing path corresponding to other tightening devices with the same hardware interface as the tightening device to be debugged but different connection protocols and from different manufacturers, query the corresponding instruction control format under the parsing path corresponding to the other tightening devices obtained, perform corresponding instruction protocol conversion on the control instruction according to the obtained instruction control format to obtain the converted instruction, send the converted instruction to the control interface of the corresponding tightening device to be debugged for execution, and judge whether the execution result is correct. If correct, update the corresponding instruction control format queried under the parsing path corresponding to other tightening devices with the same hardware interface but different connection protocols and from different manufacturers to the parsing path corresponding to the tightening device to be queried and debugged in the integrated debugging knowledge graph.

5. The method for automatic debugging of the tightening device interface according to claim 4, characterized in that: The instruction control format includes: a sequence composed of a plurality of second characteristic points arranged in sequence; the instruction control format used for the incorrect execution result includes: a second correct characteristic point and / or a second error characteristic point, wherein the execution result of the instruction converted based on the second correct characteristic point is partially correct, and the execution result of the instruction converted based on the second error characteristic point is partially wrong; Step S44, obtaining the parsing path corresponding to other tightening devices with the same hardware interface as the tightening device to be debugged but with different connection protocols and from different manufacturers, querying the corresponding instruction control format under the parsing path corresponding to the other tightening devices obtained, performing the corresponding instruction protocol conversion on the control instruction according to the obtained instruction control format to obtain the converted instruction, sending the converted instruction to the control interface of the corresponding tightening device to be debugged for execution, and judging whether the execution result is correct, including: Acquire a second correct feature point from an instruction control format used by the converted instruction whose execution result is determined to be incorrect; Selecting the second key feature points from each second correct feature point according to the importance level; Obtain the parsing path corresponding to other tightening devices with the same hardware interface as the tightening device to be debugged but with different connection protocols and from different manufacturers, and query the corresponding instruction control format under the obtained parsing path corresponding to the other tightening devices; According to the number of matches of the second key feature points of the same order in the sequence of each instruction control format, the queried instruction control formats are sorted from high to low according to the priority level; Each time, the instruction control format with the highest current priority is selected, and the control instruction is converted to the corresponding instruction protocol according to the instruction control format with the highest current priority to obtain the converted instruction, and the converted instruction is sent to the control interface of the corresponding tightening device to be debugged for execution, and it is determined whether the execution result is correct.

6. An automatic debugging system for a tightening device interface, characterized in that: include: Integrated debugging system, used to obtain the hardware interface, connection protocol and manufacturer corresponding to each tightening device; Generate a parsing path for each tightening device in sequence according to the tree structure of hardware interface, connection protocol, manufacturer and data parsing format from top to bottom, and store the data parsing path in the integrated debugging knowledge graph, wherein the data parsing format includes: data acquisition format and instruction control format; when the integrated debugging system obtains the operation parameters from the data acquisition interface of the tightening device to be debugged, the corresponding data acquisition format is queried based on the parsing path corresponding to the tightening device to be debugged in the integrated debugging knowledge graph, the operation parameters are converted to the corresponding data format according to the obtained data acquisition format to obtain the converted collected data, and the converted collected data is stored in the information system; when the integrated debugging system obtains the control instruction of the tightening device to be debugged from the information system, the corresponding instruction control format is queried based on the parsing path corresponding to the tightening device to be debugged in the integrated debugging knowledge graph, the control instruction of the tightening device to be debugged is converted to the corresponding instruction protocol according to the obtained instruction control format to obtain the converted instruction, and the converted instruction is sent to the corresponding control interface of the tightening device to be debugged for execution; The information system is used to store the converted collected data and send control instructions of the tightening equipment to be debugged to the integrated debugging system.

7. The automatic debugging system for the tightening device interface according to claim 6, characterized in that: The integrated debugging system comprises: The first unit is used for querying the corresponding data collection format based on the parsing path corresponding to the tightening equipment to be debugged in the integrated debugging knowledge graph; Unit 12 is used to convert the operation parameters into corresponding data formats according to the data acquisition format obtained by the query if the corresponding data acquisition format is found under the parsing path corresponding to the tightening device, so as to obtain the converted collected data, and to determine whether the parsing format of the converted collected data is correct. If it is correct, the converted collected data is stored in the information system; if it is not correct, the process goes to Unit 13; The first three units are used for, if the corresponding data acquisition format is not found under the parsing path corresponding to the tightening device, or if it is judged that the parsing format of the converted collected data is incorrect, obtaining the parsing path corresponding to other tightening devices with the same hardware interface and the same connection protocol as the tightening device to be debugged, but from different manufacturers, querying the corresponding data acquisition format under the parsing path corresponding to the other tightening devices obtained, performing corresponding data format conversion on the operation parameters according to the obtained data acquisition format to obtain the converted collected data, judging whether the parsing format of the converted collected data is correct, and if it is correct, storing the converted collected data in the information system, and querying the corresponding data acquisition format under the parsing path corresponding to other tightening devices with the same hardware interface and the same connection protocol, but from different manufacturers, and updating it to the parsing path corresponding to the tightening device to be queried and debugged in the integrated debugging knowledge graph; if it is incorrect, going to the first four units; The first four units are used to obtain the parsing paths corresponding to other tightening devices with the same hardware interface as the tightening device to be debugged but different connection protocols and from different manufacturers, query the corresponding data acquisition format under the parsing path corresponding to the other tightening devices obtained, convert the operation parameters into the corresponding data format according to the obtained data acquisition format to obtain the converted acquisition data, and judge whether the parsing format of the converted acquisition data is correct. If correct, store the converted acquisition data in the information system, and query the corresponding data acquisition format under the parsing path corresponding to other tightening devices with the same hardware interface but different connection protocols and from different manufacturers, and update it to the parsing path corresponding to the tightening device to be queried and debugged in the integrated debugging knowledge graph.

8. The automatic debugging system for the tightening device interface according to claim 7, characterized in that: The data acquisition format includes: a sequence composed of a plurality of first feature points arranged in sequence; the data acquisition format used by the parsing format of the converted collected data determined to be incorrect includes: a first correct feature point and / or a first erroneous feature point, wherein the parsing format of the collected data converted based on the first correct feature point is partially correct, and the parsing format of the collected data converted based on the first erroneous feature point is partially erroneous; The first four units are used to obtain the first correct feature point from the data collection format used by the converted collected data whose parsing format is judged to be incorrect; screen out the first key feature point from each of the first correct feature points obtained according to the importance level; obtain the parsing path corresponding to other tightening devices with the same hardware interface as the tightening device to be debugged but different connection protocols and different manufacturers, and query the corresponding data collection format under the parsing path corresponding to the other tightening devices obtained; sort the queried data collection formats from high to low according to the priority level according to the number of matches of the first key feature points of the same order in the sequence of each data collection format from more to less; each time, select the data collection format with the highest current priority, and perform corresponding data format conversion on the operation parameters according to the data collection format with the highest current priority to obtain the converted collected data, and judge whether the parsing format of the converted collected data is correct.

9. The automatic debugging system for the tightening device interface according to claim 6, characterized in that: The integrated debugging system comprises: The second unit is used to query the corresponding instruction control format based on the parsing path corresponding to the tightening equipment to be debugged in the integrated debugging knowledge graph; Unit 22, if the corresponding instruction control format is found under the parsing path corresponding to the tightening device to be debugged, the control instruction is converted into the corresponding instruction protocol according to the instruction control format obtained by the query to obtain the converted instruction, and the converted instruction is sent to the control interface of the corresponding tightening device to be debugged for execution, and it is judged whether the execution result is correct. If not, it goes to unit 23; Unit 23: If the corresponding instruction control format is not found under the parsing path corresponding to the tightening device to be debugged, or the execution result is judged to be incorrect, then the parsing path corresponding to other tightening devices with the same hardware interface and the same connection protocol as the tightening device to be debugged but from different manufacturers is obtained, and the corresponding instruction control format is queried under the parsing path corresponding to the other tightening devices obtained, and the control instruction is converted to the corresponding instruction protocol according to the obtained instruction control format to obtain the converted instruction, and the converted instruction is sent to the control interface of the corresponding tightening device to be debugged for execution, and it is judged whether the execution result is correct. If it is correct, the corresponding instruction control format is queried under the parsing path corresponding to other tightening devices with the same hardware interface and the same connection protocol but from different manufacturers, and updated to the parsing path corresponding to the tightening device to be debugged to be queried in the integrated debugging knowledge graph; if it is incorrect, go to Unit 24; The second and fourth units obtain the parsing paths corresponding to other tightening devices with the same hardware interface as the tightening device to be debugged but different connection protocols and from different manufacturers, query the corresponding instruction control format under the parsing path corresponding to the other tightening devices obtained, convert the control instructions to the corresponding instruction protocol according to the obtained instruction control format to obtain the converted instructions, send the converted instructions to the control interface of the corresponding tightening device to be debugged for execution, and judge whether the execution result is correct. If correct, update the corresponding instruction control format queried under the parsing path corresponding to other tightening devices with the same hardware interface but different connection protocols and from different manufacturers to the parsing path corresponding to the tightening device to be queried and debugged in the integrated debugging knowledge graph.

10. The automatic debugging system for the tightening device interface according to claim 9, characterized in that: The instruction control format includes: a sequence composed of a plurality of second characteristic points arranged in sequence; the instruction control format used for the incorrect execution result includes: a second correct characteristic point and / or a second error characteristic point, wherein the execution result of the instruction converted based on the second correct characteristic point is partially correct, and the execution result of the instruction converted based on the second error characteristic point is partially wrong; The second fourth unit is used to obtain the second correct feature point from the instruction control format used by the converted instruction that is judged to have an incorrect execution result; screen out the second key feature point from each second correct feature point according to the importance level; obtain the parsing path corresponding to other tightening devices with the same hardware interface as the tightening device to be debugged but different connection protocol and different manufacturer, and query the corresponding instruction control format under the parsing path corresponding to the other tightening devices obtained; sort the queried instruction control formats from high to low according to the priority level according to the number of matches of the second key feature points of the same order in the sequence of each instruction control format; each time select the instruction control format with the highest current priority, perform the corresponding instruction protocol conversion on the control instruction according to the instruction control format with the highest current priority to obtain the converted instruction, send the converted instruction to the control interface of the corresponding tightening device to be debugged for execution, and judge whether the execution result is correct.

Images