Testing methods, equipment, and computer-readable storage media for wearable mechs
By generating a complete test plan and using a causal matrix to identify the root cause of faults, the problem of incomplete causal relationships in wearable mechs was solved, improving test coverage and diagnostic efficiency, and ensuring the comprehensiveness and reliability of the tests.
Patent Information
- Application Number
- CN202611346328.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-09-01
- Publication Date
- 2026-11-17
AI Technical Summary
Existing technologies cannot fully cover the causal relationships between battery energy, wiring harness topology, bus synchronization, sensor consistency, lightweight structural components, and wearable tasks in wearable mechs, resulting in incomplete testing.
By reading the product configuration information of the device under test, a complete device test plan is generated. Basic function tests and fault injection tests are performed in stages according to the risk level. The root cause of the fault is inferred using the causal matrix, a complete fault causal chain is output, and a test report is generated.
It improves the test coverage, diagnostic efficiency, and reliability of wearable mechs in cross-system interaction scenarios, avoids missing test items from fixed test lists, and ensures the comprehensiveness and accuracy of testing.
Smart Images

Figure CN123111733A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of automated testing and control technology, and in particular to a testing method, device and computer-readable storage medium for wearable mechs. Background Technology
[0002] Currently, testing methods for wearable mechs typically include the following approaches: First, joint benches or rehabilitation exoskeleton test benches, which simulate the stress state during operation using a loading system to accurately measure key indicators such as torque, positioning accuracy, transmission efficiency, and temperature rise, thereby verifying whether individual components meet design standards; second, user-centric evaluation protocols, which collect heart rate, respiration, skin conductance, subjective questionnaires, and comfort indicators through tasks such as walking on flat ground and walking with weight; third, transparency or human-machine interaction force testing, which evaluates the additional resistance caused by straps, joint alignment, and human-machine connection through modeling and experimentation; fourth, factory testing methods, which test power supply, communication, sensors, actuators, emergency stop, and safety protection item by item; and fifth, reliability testing, which verifies individual aspects of wiring harness bending, vibration, temperature rise, protection level, and durability. These tests are mostly conducted on single joints, single modules, fixed test benches, or fixed user tasks. However, for wearable mechs, individual tests cannot cover the causal relationship between battery energy, wiring harness topology, bus synchronization, sensor consistency, lightweight structural components, and wearable tasks.
[0003] The above content is only used to help understand the technical solution of this application and does not represent an admission that the above content is prior art. Summary of the Invention
[0004] The main objective of this application is to provide a testing method, device, and storage medium for wearable mechs, aiming to solve the technical problem that single tests cannot cover the causal relationship between battery energy, wiring harness topology, bus synchronization, sensor consistency, lightweight structural components, and wearable tasks.
[0005] To achieve the above objectives, this application proposes a testing method for wearable mechs, the method comprising: A complete machine test plan is generated by reading the product configuration information of the machine under test; Based on the testing phases of each test item within the aforementioned test plan, basic function tests and fault injection tests are executed sequentially from low to high, and test results are output. When the test results are abnormal, the root cause of the fault is inferred through the causal matrix, and the complete causal chain of the fault is output. Based on the test results and the causal link, a test report is output.
[0006] In one embodiment, the step of generating a whole-machine test plan by reading the product configuration information of the machine under test includes: Obtain the pre-stored topology association database, parsing rule base, parameter baseline database, and fault rule base; According to the parsing rule base, the product configuration information is parsed into standardized attributes, and the capability tags in the standardized attributes are used as keywords to match the corresponding mapping rules in the topology association database to generate initial test items; Based on the inference rules pre-stored in the topological association database, the derived test items of the initial test items are derived, and the initial test items and the derived test items are merged to generate a test item set; The risk level is determined based on the type of each test item in the test item set, and the test stage of each test item is determined based on the risk level. Extract the test items contained in each of the test phases, perform basic function tests based on a preset test order, and obtain the measured values of each test item; Based on the test items and the component version and component type in the standardized attributes, query the judgment thresholds in the parameter baseline library, wherein the judgment thresholds include pass thresholds, downgrade thresholds and fail thresholds; The measured value is compared with the judgment threshold to generate the test result of the basic function test; When the basic function test passes, the fault injection sequence and expected response corresponding to each test item are matched in the fault rule base according to the test item and the component version and component type in the standardized attributes. Based on the order in the fault sequence, fault injection tests are executed sequentially, and the actual response during fault injection is monitored in real time. The actual response is compared with the expected response to generate the test results of the fault injection test; Based on the test item set, the test phase, the basic function test, the parameter threshold, the fault injection sequence, and the expected response generation test plan.
[0007] In one embodiment, before the step of reasoning the root cause of the fault through a causal matrix and outputting the complete causal chain of the fault when the test result is abnormal, the following steps are included: The received coverage and testing requirements of the wearable mech test are input into a pre-trained root cause analysis model to obtain the fault causes corresponding to each abnormal test result. The abnormal test results and the causes of the failures are encoded into structured data to generate a causal matrix containing at least one causal mapping table.
[0008] In one embodiment, the step of performing basic functional tests and fault injection tests sequentially from low to high based on the test phases of each test item within the test plan, and outputting the test results, includes: Based on the testing phases of each test item within the aforementioned testing plan, basic function tests are executed sequentially from low to high. When the basic function test passes, a preset fault sequence is injected into the test, the fault injection test is executed, and it is determined whether the fault injection test response meets the expected response. If the fault injection test response meets the expected response, the current stage of the test passes, and the next stage of the test is executed. If the fault injection test response does not meet the expected response, then there is an anomaly in the current stage of the test; Based on the results of the basic function tests and the fault injection tests, the test results of the testing phase are generated.
[0009] In one embodiment, after the step of performing basic functional tests sequentially from low to high based on the test items within the test plan, the process includes: When the basic function test result is downgraded or fails, the first-order diagnostic process is triggered; Obtain abnormal indicators; the causal matrix retrieves a preset causal mapping table based on the abnormal indicators and outputs a list of fault causes with priority. Based on the priority of the list of possible causes, perform a verification operation; If an anomaly is confirmed in a certain verification step, the investigation should be stopped and the cause should be marked as the root cause of the failure. Based on the abnormal indicators, the root cause of the failure, the direct cause and triggering conditions corresponding to the root cause of the failure, and the judgment criteria for verifying the root cause of the failure, a complete causal chain is generated.
[0010] In one embodiment, after the step of outputting the complete causal chain, the following is included: Based on the root cause of the fault, a repair instruction is generated; After the repair is completed, a supplementary test plan is generated, and the test process is re-executed; If the test passes, proceed to the next stage of testing.
[0011] In one embodiment, the step of determining that the current stage of the test is abnormal if the fault injection test response does not meet the expected response includes: When the fault injection test response does not meet the expected response, the second-order diagnostic process is triggered; Based on the type of error response, and referring to the pre-defined cause-effect mapping table in the cause-effect matrix, the priority of the fault cause is output. Verification and troubleshooting will be performed sequentially based on the priority order of the aforementioned fault causes; If an anomaly is confirmed in a certain verification step, the investigation should be stopped and the cause should be marked as the root cause of the failure. The investigation results are categorized into specific fault types, and corresponding handling instructions are output.
[0012] In one embodiment, after the step of classifying the investigation results into specific fault types and outputting corresponding handling instructions, the method includes: Execute the aforementioned disposal instructions; After the repair is completed, the testing process is re-executed based on the fault type identified in the troubleshooting results. When the test passes, update the cause-effect matrix and optimize the test plan.
[0013] In addition, to achieve the above objectives, this application also proposes a test device for wearing a mech, the device comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the test method for wearing a mech as described above.
[0014] In addition, to achieve the above objectives, this application also proposes a storage medium, which is a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, it implements the steps of the test method for wearing a mech as described above.
[0015] One or more technical solutions proposed in this application have at least the following technical effects: This solution generates a complete system test plan by reading the product configuration information of the device under test. The test plan includes the risk level of each test item. Based on the risk level, all test items are divided into different test phases. Test items in each phase are executed sequentially from low to high risk, and test results are output. When test results show anomalies, the root cause of the fault is inferred using a causal matrix, outputting a complete causal chain. Finally, a final test report is output based on the test results and the causal chain. Compared to related technologies that rely on single-item tests for single joints, single modules, fixed test benches, or fixed user tasks, this solution, by reading product configuration information to generate a test plan, avoids missing test items from a fixed test list. The test plan contains multiple test items, and multiple test items are executed in stages according to their risk level. Then, when test results show anomalies, the cause of the anomaly can be investigated and verified using a causal matrix, outputting a causal chain. Through continuous updates and iterations, a final test report is obtained. Therefore, this solution can comprehensively improve the test coverage, diagnostic efficiency, and reliability assurance level of complex products in cross-system interaction scenarios. Attached Figure Description
[0016] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.
[0017] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0018] Figure 1 A flowchart illustrating the testing method for wearing a mecha as described in this application (Example 1). Figure 2 A simplified flowchart illustrating the testing method for wearable mechs provided in Embodiment 1 of this application; Figure 3 A simplified flowchart illustrating the testing method for the wearable mech provided in Embodiment 2 of this application; Figure 4 This is a schematic diagram of the hardware operating environment involved in the test method for wearing a mecha in this application embodiment.
[0019] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation
[0020] It should be understood that the specific embodiments described herein are merely illustrative of the technical solutions of this application and are not intended to limit this application.
[0021] Testing methods for wearable mecha products typically include the following aspects: First, joint benches or rehabilitation exoskeleton test benches, which simulate the stress state during operation using a loading system to accurately measure key indicators such as torque, positioning accuracy, transmission efficiency, and temperature rise, thereby verifying whether individual components meet design standards; second, user-centered evaluation protocols, which collect heart rate, respiration, skin conductance, subjective questionnaires, and comfort indicators through tasks such as walking on flat ground and walking with weight; third, transparency or human-machine interaction force testing, which evaluates the additional resistance caused by straps, joint alignment, and human-machine connection through modeling and experimentation; fourth, factory testing methods, which test power supply, communication, sensors, actuators, emergency stop, and safety protection item by item; and fifth, reliability testing, which verifies individual aspects of wiring harness bending, vibration, temperature rise, protection level, and durability. These tests are mostly for single joints, single modules, fixed test benches, or fixed user tasks. However, for wearable mecha, individual tests cannot cover the causal relationship between battery energy, wiring harness topology, bus synchronization, sensor consistency, lightweight structural components, and wearable tasks.
[0022] Based on this, the main solution of this application embodiment is: to generate a whole machine test plan by reading the product configuration information of the whole machine under test; to perform basic function tests and fault injection tests in order from low to high based on the risk level of each test item in the test plan, and output the test results; when the test results are abnormal, to infer the root cause of the fault through the causal matrix and output the complete fault causal link; and to output a test report based on the test results and the causal link.
[0023] In the test method for wearable mechs provided in this application, a test plan is generated by reading the product configuration information of the device under test. The test plan includes the risk level of each test item, and the test items are divided into different stages according to the risk level. Basic functional tests of each test item in the test stage are executed sequentially from low to high risk. After the basic functional tests are passed, a fault injection test is performed, and the test response after the injected fault is observed to see if it meets the expected response. If it meets the expected response, the test for that stage is passed; otherwise, it indicates an anomaly in the current stage. The next stage of testing can only be executed after the previous stage is passed, and the test results for each stage are output. When the basic functional test results show an anomaly, a first-order diagnostic process is triggered. The cause of the fault is investigated and verified using a causal matrix, and a complete causal chain is output. When the test result after the injected fault does not meet the expected response, a second-order diagnostic process is triggered. The cause of the fault is investigated and verified using a causal matrix, and a complete causal chain is output. Finally, a final test report is output based on the test results and causal chain. This process effectively solves the problem that single-item tests cannot cover the causal relationships between battery energy, wiring harness topology, bus synchronization, sensor consistency, lightweight structural components, and wearable tasks. It enables automated identification, tracing, and verification of cross-system causal relationships, significantly improving the test coverage, fault location efficiency, and overall reliability assurance level of wearable mechs in cross-system interaction scenarios.
[0024] It should be noted that the executing entity in this embodiment can be a computing service system with data processing, network communication, and program execution functions, such as a tablet computer, personal computer, server, or a system capable of performing the above functions. For ease of description, the test equipment for wearing mechs will be uniformly described as mech test equipment, and the following embodiments will be described accordingly.
[0025] To better understand the technical solution of this application, a detailed description will be provided below in conjunction with the accompanying drawings and specific implementation methods.
[0026] First Embodiment This embodiment provides a testing method for wearable mechs, referring to... Figure 1 The flowchart shown in Embodiment 1 of the test method for wearable mechs includes steps S10 to S40: Step S10: Generate a whole machine test plan by reading the product configuration information of the whole machine under test.
[0027] The test host reads the product configuration information corresponding to the wearable mech under test. This product configuration information includes a structural component ID (Identifier, a string of characters or codes used to uniquely identify a specific component or software version), wiring harness ID, domain controller ID, power supply, sensor topology, software version, and application scenario configuration. Based on this product configuration information, the host queries the pre-built parsing rule base to find the standardized attributes corresponding to each piece of product configuration information. This parsing rule base is a pre-built structured database that stores the standardized attributes corresponding to each piece of product configuration information.
[0028] After completing the query, the system uses the capability tag in the standardized attribute as a keyword, matches the corresponding test item mapping rules in the pre-set topology association database, generates initial test items, and then infers from the initial test items one by one according to the pre-stored inference rules in the topology association database, including dependency rules, coupling rules, scenario rules, and threshold rules, automatically deriving the necessary supplementary derivative test items. After the derivation is completed, the system merges the initial test items with the derivative test items derived from each inference rule, and after deduplication and integration, forms the final complete set of test items.
[0029] As an optional implementation, after obtaining the test item set, the risk level of each test item is determined according to its type, and they are then sorted into stages T0-T7 according to their risk levels. After determining the test stages, tests are executed sequentially from T0 to T7. Only after the test of the current stage passes can the test of the next stage be executed. Each test item in the test stage is extracted, the preset test order for each test item is obtained, and the basic functional tests of each test item are executed through software instructions to obtain the measured values of each test item.
[0030] The system extracts test item names from the currently executing basic functional tests, and extracts the associated component version and component type from standardized attributes. It then combines the test item name, component version, and component type to form query conditions. These query conditions are input into a parameter baseline library to obtain the parameter thresholds for each test item. These thresholds include pass thresholds, downgrade thresholds, and fail thresholds. The parameter baseline library is a pre-built structured database that stores the judgment thresholds corresponding to each component type, component version, and test item combination.
[0031] After obtaining the parameter thresholds for each test item, the measured values obtained in the basic function test are compared with the parameter thresholds to generate the test results of the basic function test, which include qualified, downgraded, and unqualified.
[0032] When the basic functional test result is passed, the extracted test item name, component version, and component type combination are used as query conditions and input into the fault rule base. The fault injection sequence and expected response corresponding to that test item are extracted from the matching records in the fault rule base. The fault rule base is a pre-built structured database that stores the fault injection sequence and expected response corresponding to each component type, component version, and test item combination.
[0033] After obtaining the fault injection sequence, the fault injection test is executed sequentially according to the sequence order in the fault sequence, and the actual response after fault injection is monitored in real time. At the same time, the monitored actual response is compared with the expected response in real time, and the test result of the fault injection test is output. The test result includes the response that meets the expected response and the response that does not meet the expected response.
[0034] Therefore, the test host transforms the original product configuration information into a complete test plan that includes test items, test phases, basic function tests, parameter thresholds, fault injection sequences, and expected responses, serving as the basis for subsequent security door tests.
[0035] Step S20: Based on the testing phases of each test item within the test plan, perform basic function tests and fault injection tests sequentially from low to high, and output the test results.
[0036] Specifically, the testing system executes basic functional tests in a pre-arranged T0-T7 sequence, verifying whether the product meets the standards under interference-free conditions. When the basic functional tests pass, the corresponding fault injection test is executed. When the basic functional test result is a degradation, the system automatically decides whether to execute the subsequent fault injection test based on the severity of the degradation and whether it affects the verification validity. Execution is allowed for minor degradation that does not affect verification validity; for severe degradation or if it affects verification validity, the fault injection test is skipped, and the first-order diagnostic process is triggered directly. When the basic functional tests fail, the first-order diagnostic process is executed; when the fault injection test does not meet the expected response, the second-order diagnostic process is executed.
[0037] Based on the combined results of basic functional testing and fault injection testing, output a judgment conclusion of whether this stage passes, is downgraded, or fails.
[0038] Specifically, if the basic function test passes and the fault injection test meets the expected response, the result is considered pass; if the basic function test result is downgraded, but the fault injection test meets the expected response, the result is considered downgraded; if the basic function test fails or the fault injection test does not meet the expected response, the result is considered fail. When the basic function test result shows downgrade or failure, the output includes test results containing anomaly location and preliminary diagnostic direction.
[0039] It should be noted that T0 only reads identity and topology, without releasing power; T1 verifies power energy, pre-charge curve, reverse power, and emergency stop link; T2 verifies harness continuity, impedance, shielding grounding, and bending health; T3 verifies EtherCAT (EtherCAT is an Ethernet control automation technology used for synchronous motion control of multiple joint motors in wearable mechs), CANFD (a flexible data rate controller area network used for command and status transmission between domain controllers and modules), RS485 (the recommended standard RS485 used for connecting long-distance sensor nodes or communicating with older external devices), and UART (Universal Audio Receiver). The system includes a transceiver for short-distance data exchange between the main control chip and board-level peripheral devices, and ADC communication (an analog-to-digital converter used to read analog sensor data, such as voltage signals from plantar pressure sensors, knee joint angle potentiometer signals, and battery voltage monitoring). T4 verifies sensor time alignment and consistency. T5 performs no-load, loaded, and thermal tests on a test bench. T6 performs pressure, ROM (the maximum range of motion of a wearer's joints when using the device, or the maximum physical range of motion of the device's joints), skin temperature rise, and emergency stop response tests in wearable mode. T7 performs tasks such as lifting heavy objects, archery, and billiards.
[0040] Step S30: When the test results are abnormal, the root cause of the fault is inferred through the causal matrix, and the complete fault causal chain is output.
[0041] The causal matrix is a pre-built, structured fault diagnosis knowledge base used to establish the mapping relationship between test phenomena, fault causes, and verification steps, and to drive the system to complete automated reasoning from phenomena to root causes when test anomalies occur.
[0042] A causal chain is a complete chain of cause-and-effect relationships that describes the triggering phenomenon, the direct cause, the root cause, the inducing condition, and the final consequence.
[0043] Specifically, when the basic function test results show a downgrade or failure, abnormal indicators are extracted. By comparing these indicators with the pre-set causal mapping table in the causal matrix, the system automatically determines the priority direction for investigation. After obtaining the investigation order, the system executes the verification steps one by one according to priority. When an abnormality is identified in a verification step, subsequent investigations are immediately stopped, and the current cause is marked as the root cause of the fault. After verification, a complete causal chain is generated based on the abnormal indicators, the root cause of the fault, the direct cause and triggering conditions corresponding to the root cause, and the judgment criteria used when verifying the root cause. Based on the causal chain, a repair instruction is generated. The system completes the repair action according to the repair instruction. After the repair is completed, a supplementary test plan is generated, and the supplementary test process is re-executed. When the test results show a pass, a fault injection test is executed; when the test results show a downgrade or failure, the system returns to the steps of investigating and verifying the cause of the abnormality.
[0044] When the test results after fault injection do not meet the expected response, a second-order diagnostic process is triggered. The type of fault injection is identified, and based on the type of error response, the priority direction for investigation is automatically determined by referring to the pre-set causal mapping table in the causal matrix.
[0045] For example, when the response type is no response, the cause may be a failure of the detection link, and the detection and capture link should be checked first; when the response type is response error, the cause may be a policy logic error, and the policy decision link should be checked first; when the response type is response lag, the cause may be a delay in the execution link, and the policy execution link should be checked first; when the response type is reason code error, the cause may be a chaotic mapping relationship, and the diagnostic mapping link should be checked first.
[0046] Verification and troubleshooting are performed sequentially according to the order of detection, decision-making, and execution, and the priority of their corresponding possible causes. Once a verification step confirms the root cause of the anomaly, subsequent troubleshooting is immediately terminated, the determined error type and corresponding handling instructions are output, and the system completes the repair action based on the handling instructions. After repair, the test for this stage is re-executed. If the supplementary test result shows a pass, the cause-effect matrix is updated, the test plan is optimized, and the next stage of testing is executed; if the supplementary test result shows a downgrade or failure, the system returns to the step of troubleshooting and verifying the cause of the anomaly.
[0047] Based on the abnormal indicators, root causes of failures, direct causes and triggering conditions corresponding to the root causes of failures, and the criteria for verifying the root causes of failures during the investigation process, a complete causal chain is generated.
[0048] Step S40: Based on the test results and causal links, output a test report.
[0049] After testing, all test data is compiled and generated into a structured data archive permanently bound to the device's serial number. The system then integrates the test results from each stage to output the final release decision. The archive includes the device serial number, structural component ID, wiring harness ID, domain controller ID, battery ID, software version, test plan version, results from each stage, degradation reason codes, fault injection responses, repair records, and supplementary test results. The system stores the generated data archive on the main controller, in a cloud database, or in maintenance tools. This data archive continues to be useful in after-sales service. Finally, the system formats the structured data in the archive into a test report according to readability requirements.
[0050] For example, in the after-sales process, when a product has a component replaced due to repair, the system reads the old file to obtain the product's original test records and topology. Then, it scans the new topology, identifies the ID of the new component after replacement and the new configuration, automatically compares the differences between the old file and the new topology, and generates a supplementary test plan to perform supplementary verification only on the replaced component and its associated functions.
[0051] To help understand the specific implementation process of this embodiment, please refer to... Figure 2 The diagram shows a simplified flowchart of the testing method for wearable mechs provided in Embodiment 1.
[0052] In this embodiment, a test plan for the entire device is generated by reading the product configuration information of the device under test. This step ensures accurate coverage of test items and avoids omissions due to a fixed list. Next, the test items are sorted according to risk level, and each test item is executed in stages. The next stage of testing can only proceed after the previous stage has passed, verifying each level step by step and preventing the risk from being passed across levels. Then, when anomalies occur during the test, the cause of the anomaly is investigated and verified using a causal matrix, and the causal chain is output to ensure that the diagnosis is based on evidence and to avoid misjudgments or omissions. Finally, a data archive is generated based on all data and causal chains during the test process, storing the entire test process and ensuring the traceability of test records. This comprehensively improves the test coverage, diagnostic efficiency, and reliability of wearable mechs in cross-system interaction scenarios.
[0053] Second Embodiment Based on the first embodiment of this application, in the second embodiment of this application, referring to... Figure 3 The simplified flowchart of the test method for the wearable mech provided in Embodiment 2 is identical or similar to that in Embodiment 1 above, and will not be repeated hereafter. Based on this, before step S30, the test method for the wearable mech also includes steps S01-S02.
[0054] Step S01: Construct the causal matrix.
[0055] The system receives the coverage and testing requirements of the wearable mech test and inputs these into a pre-trained root cause analysis model. The coverage clarifies the boundaries of the causal matrix that need to be diagnosed, including which components or links need to be diagnosed, the types of fault modes that need to be covered for each diagnostic object, and the extent to which the diagnosis is considered complete. The testing requirements include the standards for fault determination, priority requirements, and industry standards.
[0056] The system parses the received coverage area and test requirements, transforming them into structured parameter information. Based on the parsed coverage area and test requirements, the system matches them against a pre-built fault knowledge base to establish a preliminary mapping relationship between test anomalies and fault causes.
[0057] The system inputs the initial mapping relationships, coverage, and test requirements into a pre-trained root cause analysis model. The model then infers multi-factor coupled failure modes that cannot be detected by rule matching alone, thereby generating composite failure root causes and a list of failure causes. The root cause analysis model is trained based on historical failure data.
[0058] After obtaining the list of possible causes of the fault, the system executes verification steps sequentially from highest to lowest priority based on the preset fault cause priority. After completing the verification steps, the system obtains the measured values and compares them with the preset judgment criteria. If the measured value meets the confirmation conditions in the judgment criteria, the cause is determined to be the root cause of the fault, the system immediately stops subsequent verification, marks the cause as the root cause, outputs the causal link, and the diagnostic process ends. If the measured value does not meet the confirmation conditions in the judgment criteria, the cause is determined to be excluded, and the system continues to verify the next cause in the priority list, repeating the verification steps and the process of comparing judgment criteria.
[0059] After completing the above design, the abnormal test results and fault causes are encoded into structured data, generating a causal matrix containing at least one causal mapping table, and stored in the causal matrix database. Specifically, the diagnostic object, fault mode, test anomaly, fault cause, verification steps, judgment criteria, and troubleshooting priority are encoded into system-readable structured data to generate the causal mapping table.
[0060] Step S02: Verify the causal matrix.
[0061] As an optional implementation method, after the causal matrix is constructed, it is fully verified through methods such as historical fault data playback, simulation verification, and expert review to ensure that the mapping relationship is accurate and the verification steps are executable.
[0062] Specifically, during the historical fault data playback verification, the system extracts recorded real fault cases from the historical test database. Each case clearly includes the test anomaly, the actual root cause of the fault, and the verification data at that time. The system uses the test anomaly in each case as a query keyword to input into the constructed cause-effect matrix, obtains the possible cause list and corresponding verification steps output by the matrix, and then compares them one by one to see if they point to the cause consistent with the actual root cause of the fault. If the possible cause list output by the matrix contains the actual root cause, and the verification steps can effectively confirm the root cause, then the mapping relationship passes the verification; if the cause list output by the matrix does not contain the actual root cause, or the verification steps cannot effectively confirm or exclude the cause, it indicates that there is an omission or error in the mapping relationship, and it is necessary to go back to the corresponding step for correction.
[0063] During simulation verification, the system artificially injects preset faults into the test environment and observes the actual performance of the causal matrix during the diagnostic process. The system records the complete diagnostic path from the input of the abnormal phenomenon to the output of the root cause of the fault, verifies whether the fault cause list output by the verification matrix includes the artificially injected fault cause, whether the verification steps can effectively confirm the cause, whether the priority of troubleshooting is reasonable, and whether the entire diagnostic process meets the design expectations. If a deviation occurs at any stage, such as the matrix failing to match the injected fault cause, or the verification steps failing to confirm the fault, the system will record the deviation and trigger the corresponding correction process to ensure that the causal matrix can work reliably in actual operation.
[0064] During expert review, a review team composed of system architects, test engineers, and fault diagnosis experts manually reviews the causal matrix. The review includes three levels: first, a completeness assessment, checking whether the matrix omits important failure modes or mapping relationships; second, an accuracy assessment, verifying whether each mapping relationship conforms to the system design logic and actual testing experience; and third, an executability assessment, confirming whether each verification step is operable in a real testing environment and whether the judgment criteria are clear and quantifiable. Any issues discovered during the review process are recorded by the team and fed back to the build team, who then correct and improve the matrix accordingly.
[0065] After the above verification is passed, the causal matrix is activated, making it queryable.
[0066] During the continuous use of the causal matrix after its official deployment, each newly diagnosed fault mode serves as a source of continuously updated data. When a test anomaly cannot be matched with a valid root cause in the existing matrix, the system marks it as a root cause not located and triggers manual intervention. Engineers, through in-depth analysis, ultimately pinpoint the true root cause of the fault, design corresponding verification steps and judgment criteria, and add this complete mapping relationship as a new causal mapping entry to the causal matrix. Simultaneously, if the investigation priority of a fault cause is found to be unreasonable during the diagnostic process, engineers will adjust its sorting position in the list to make the diagnosis of subsequent similar problems more efficient, ultimately forming a complete and operational causal matrix knowledge base.
[0067] In this embodiment, the construction of the causal matrix pre-sorts and solidifies complex cross-system dependencies into a structured mapping table, becoming standardized data that the system can query and execute. Simultaneously, the causal matrix pre-designs a list of possible causes, verification steps, and judgment criteria for each anomaly, and sets investigation priorities. This means that when an anomaly occurs during testing, the system no longer needs to rely on manual temporary analysis to query the source, but instead automatically executes verification according to the preset path in the matrix, shortening the anomaly localization time and avoiding misjudgments or omissions due to differences in individual experience. Furthermore, the causal matrix simultaneously carries two sets of mapping tables: a first-order diagnostic mapping table specifically for investigating hardware component failures, and a second-order diagnostic mapping table specifically for investigating failures in the degradation strategy itself. This design enables the system to accurately distinguish between component failures and strategy failures, avoiding wasting time in the wrong direction and significantly improving the efficiency of fault diagnosis.
[0068] It should be noted that the above examples are only for understanding this application and do not constitute a limitation on the testing method of wearing a mecha in this application. Any simple modifications based on this technical concept are within the protection scope of this application.
[0069] This application provides a test device for wearable mechs, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the test method for wearable mechs in the first embodiment described above.
[0070] The following is for reference. Figure 4The diagram illustrates a structural schematic of a test device suitable for implementing the wearable mechs of the embodiments of this application. The test device for the wearable mechs in the embodiments of this application may include, but is not limited to, mobile terminals such as mobile phones, laptops, PDAs (Personal Digital Assistants), PADs (Portable Application Description), etc., and fixed terminals such as desktop computers. Figure 4 The test equipment for wearing the mech shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.
[0071] like Figure 4 As shown, the test equipment for wearing a mech may include a processing unit 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage device 1003 into a random access memory (RAM) 1004. The RAM 1004 also stores various programs and data required for the operation of the test equipment for wearing the mech. The processing unit 1001, ROM 1002, and RAM 1004 are interconnected via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to I / O interface 1006: input devices 1007 including, for example, touchscreens, touchpads, keyboards, mice, image sensors, microphones, accelerometers, gyroscopes, etc.; output devices 1008 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 1003 including, for example, magnetic tapes, hard disks, etc.; and communication devices 1009. Communication device 1009 allows the test equipment for the wearable mech to communicate wirelessly or wiredly with other devices to exchange data. Although a test equipment for the wearable mech with various systems is shown in the figure, it should be understood that it is not required to implement or possess all the systems shown. More or fewer systems may be implemented alternatively.
[0072] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from storage device 1003, or installed from ROM 1002. When the computer program is executed by processing device 1001, it performs the functions defined in the methods of the embodiments disclosed in this application.
[0073] The wearable mecha testing equipment provided in this application, employing the wearable mecha testing method described in the above embodiments, can solve the technical problem that single-item tests cannot cover the causal relationship between battery energy, wiring harness topology, bus synchronization, sensor consistency, lightweight structural components, and wearable tasks. Compared with the prior art, the beneficial effects of the wearable mecha testing equipment provided in this application are the same as those of the wearable mecha testing method provided in the above embodiments, and other technical features in this wearable mecha testing equipment are the same as those disclosed in the previous embodiment method, and will not be repeated here.
[0074] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples.
[0075] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
[0076] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, the computer-readable program instructions being used to execute the test method for wearing a mech in the above embodiments.
[0077] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems or devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or flash memory, optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination thereof.
[0078] The aforementioned computer-readable storage medium may be included in the test equipment for the wearable mech, or it may exist independently and not be installed in the test equipment for the wearable mech.
[0079] The aforementioned computer-readable storage medium carries one or more programs, which, when executed by a test device for wearing a mech, cause the test device to perform the steps of the test method for wearing a mech as described above.
[0080] Computer program code for performing the operations of this application can be written in one or more programming languages or a combination thereof, including object-oriented programming languages such as Java, Smalltalk, and C++, and conventional procedural programming languages such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).
[0081] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation that may be implemented in systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.
[0082] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.
[0083] The storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the above-described test method for wearable mechs. This solves the technical problem that single tests cannot cover the causal relationship between battery energy, wiring harness topology, bus synchronization, sensor consistency, lightweight structural components, and wearable tasks. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as those of the test method for wearable mechs provided in the above embodiments, and will not be repeated here.
[0084] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the test method for wearing a mech as described above.
[0085] The computer program product provided in this application can solve the technical problem that single tests cannot cover the causal relationship between battery energy, wiring harness topology, bus synchronization, sensor consistency, lightweight structural components, and wearable tasks. Compared with the prior art, the beneficial effects of the computer program product provided in this application are the same as the beneficial effects of the wearable mech testing method provided in the above embodiments, and will not be repeated here.
[0086] The above description is only a part of the embodiments of this application and does not limit the patent scope of this application. All equivalent structural transformations made under the technical concept of this application and using the contents of the specification and drawings of this application, or direct / indirect applications in other related technical fields, are included in the patent protection scope of this application.
Claims
1. A testing method for wearable mechs, characterized in that, The testing method for the wearable mech includes: A complete machine test plan is generated by reading the product configuration information of the machine under test; Based on the testing phases of each test item within the aforementioned test plan, basic function tests and fault injection tests are executed sequentially from low to high, and test results are output. When the test results are abnormal, the root cause of the fault is inferred through the causal matrix, and the complete causal chain of the fault is output. Based on the test results and the causal link, a test report is output.
2. The testing method for wearable mechs as described in claim 1, characterized in that, The step of generating a test plan for the entire machine by reading the product configuration information of the machine under test includes: Obtain the pre-stored topology association database, parsing rule base, parameter baseline database, and fault rule base; According to the parsing rule base, the product configuration information is parsed into standardized attributes, and the capability tags in the standardized attributes are used as keywords to match the corresponding mapping rules in the topology association database to generate initial test items; Based on the inference rules pre-stored in the topological association database, the derived test items of the initial test items are derived, and the initial test items and the derived test items are merged to generate a test item set; The risk level is determined based on the type of each test item in the test item set, and the test stage of each test item is determined based on the risk level. Extract the test items contained in each of the test phases, perform basic function tests based on a preset test order, and obtain the measured values of each test item; Based on the test items and the component version and component type in the standardized attributes, query the judgment thresholds in the parameter baseline library, wherein the judgment thresholds include pass thresholds, downgrade thresholds and fail thresholds; The measured value is compared with the judgment threshold to generate the test result of the basic function test; When the basic function test passes, the fault injection sequence and expected response corresponding to each test item are matched in the fault rule base according to the test item and the component version and component type in the standardized attributes. Based on the order in the fault sequence, fault injection tests are executed sequentially, and the actual response during fault injection is monitored in real time. The actual response is compared with the expected response to generate the test results of the fault injection test; Based on the test item set, the test phase, the basic function test, the parameter threshold, the fault injection sequence, and the expected response generation test plan.
3. The testing method for wearable mechs as described in claim 1, characterized in that, Before the step of reasoning the root cause of the fault through a causal matrix and outputting the complete causal chain of the fault when the test result is abnormal, the following steps are included: The received coverage and testing requirements of the wearable mech test are input into a pre-trained root cause analysis model to obtain the fault causes corresponding to each abnormal test result. The abnormal test results and the causes of the failures are encoded into structured data to generate a causal matrix containing at least one causal mapping table.
4. The testing method for wearable mechs as described in claim 1, characterized in that, The steps for performing basic functional tests and fault injection tests sequentially from low to high, based on the test items within the test plan, and outputting the test results, include: Based on the testing phases of each test item within the aforementioned testing plan, basic function tests are executed sequentially from low to high. When the basic function test passes, a preset fault sequence is injected into the test, the fault injection test is executed, and it is determined whether the fault injection test response meets the expected response. If the fault injection test response meets the expected response, the current stage of the test passes, and the next stage of the test is executed. If the fault injection test response does not meet the expected response, then there is an anomaly in the current stage of the test; Based on the results of the basic function tests and the fault injection tests, the test results of the testing phase are generated.
5. The testing method for wearable mechs as described in claim 4, characterized in that, The testing phase based on each test item within the test plan, after executing the basic functional tests sequentially from low to high, includes: When the basic function test result is downgraded or fails, the first-order diagnostic process is triggered; Obtain abnormal indicators; the causal matrix retrieves a preset causal mapping table based on the abnormal indicators and outputs a list of fault causes with priority. Based on the priority of the list of possible causes, perform a verification operation; If an anomaly is confirmed in a certain verification step, the investigation should be stopped and the cause should be marked as the root cause of the failure. Based on the abnormal indicators, the root cause of the failure, the direct cause and triggering conditions corresponding to the root cause of the failure, and the judgment criteria for verifying the root cause of the failure, a complete causal chain is generated.
6. The testing method for wearable mechs as described in claim 5, characterized in that, Following the step of outputting the complete causal chain, the following is included: Based on the root cause of the fault, a repair instruction is generated; After the repair is completed, a supplementary test plan is generated, and the test process is re-executed; If the test passes, proceed to the next stage of testing.
7. The testing method for wearable mechs as described in claim 4, characterized in that, The step of determining that the current stage of the test is abnormal if the fault injection test response does not meet the expected response includes: When the fault injection test response does not meet the expected response, the second-order diagnostic process is triggered; Based on the type of error response, and referring to the pre-defined cause-effect mapping table in the cause-effect matrix, the priority of the fault cause is output. Verification and troubleshooting will be performed sequentially based on the priority order of the aforementioned fault causes; If an anomaly is confirmed in a certain verification step, the investigation should be stopped and the cause should be marked as the root cause of the failure. The investigation results are categorized into specific fault types, and corresponding handling instructions are output.
8. The testing method for wearable mechs as described in claim 7, characterized in that, After the step of classifying the investigation results into specific fault types and outputting corresponding handling instructions, the following steps are included: Execute the aforementioned disposal instructions; After the repair is completed, the testing process is re-executed based on the fault type identified in the troubleshooting results. When the test passes, update the cause-effect matrix and optimize the test plan.
9. A testing device for wearable mechs, characterized in that, The device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the test method for wearing a mech as described in any one of claims 1 to 8.
10. A computer-readable storage medium, characterized in that, The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, it implements the steps of the test method for wearing a mech as described in any one of claims 1 to 8.
