Fault diagnosis function test method, device, equipment and storage medium

Abstract

The application discloses a fault diagnosis function test method, device and equipment and a storage medium, and belongs to the technical field of function test. The application can find a fault code type and a fault triggering condition corresponding to a to-be-tested line control system from a fault information set corresponding to a fault diagnosis function, then sets multiple groups of fault test information based on the fault code type and the fault triggering condition, and finally sequentially performs fault diagnosis function test on the to-be-tested line control system through each group of fault test information respectively, so that automatic generation of fault test information is realized, the fault diagnosis function test is automatically performed, the degree of automation in the test process is improved, and the test time is reduced.

Description

TECHNICAL FIELD

[0001] The present application relates to the functional test technical field, and particularly relates to a fault diagnosis function test method, device, equipment and storage medium. BACKGROUND

[0002] The drive-by-wire technology originates from the aircraft control system. The new flight control system of the aircraft is a drive-by-wire system, which converts the control command of the aircraft pilot into an electrical signal and controls the flight of the aircraft by using a computer. In recent years, this control mode is introduced into the automobile driving. The drive-by-wire system of the automobile driving is to convert the operation action of the driver into an electrical signal through a sensor, transmit the electrical signal to an electronic control unit through a CAN bus, and drive an actuator by the electronic control unit.

[0003] Since the drive-by-wire system is driven by an electrical signal, in order to prevent faults in the driving execution process, a fault diagnosis function is usually configured in the drive-by-wire system. However, the effectiveness of the fault diagnosis function also needs to be tested. In the prior art, the effectiveness of the fault diagnosis function of the drive-by-wire system is generally tested manually, which results in low automation and long test time in the test process. SUMMARY

[0004] The main purpose of the present application is to provide a fault diagnosis function test method, device, equipment and storage medium, which aims to solve the technical problems of low automation and long test time of the fault diagnosis function test in the prior art.

[0005] To achieve the above purpose, the present application provides a fault diagnosis function test method, which comprises the following steps:

[0006] Finding the fault code type and fault trigger condition corresponding to the to-be-tested drive-by-wire system from a fault information set corresponding to the fault diagnosis function;

[0007] Setting a plurality of groups of fault test information based on the fault code type and fault trigger condition;

[0008] Respectively testing the fault diagnosis function of the to-be-tested drive-by-wire system through each group of fault test information in sequence.

[0009] Optionally, each group of fault test information comprises a test input quantity, a test method and a test range.

[0010] The step of respectively testing the fault diagnosis function of the to-be-tested drive-by-wire system through each group of fault test information in sequence comprises:

[0011] Traversing the fault test information, and taking the traversed fault test information as the current fault test information.

[0012] sending a current test input quantity in the current fault information to the to-be-tested drive-by-wire system, so that the to-be-tested drive-by-wire system generates and feeds back a corresponding current execution quantity, and generates and feeds back a current actual fault diagnosis result corresponding to the current execution quantity;

[0013] determining a current theoretical fault diagnosis result based on the current test input quantity, the current execution quantity, a test mode and a test range;

[0014] performing a fault diagnosis function test according to the current theoretical fault diagnosis result and the current actual fault diagnosis result.

[0015] Optionally, the determining of the current theoretical fault diagnosis result based on the current test input quantity, the current execution quantity, the test mode and the test range comprises:

[0016] calculating a deviation value between the current test input quantity and the current execution quantity, and determining a diagnosis threshold value and a quantity threshold value based on the current test mode and the test range;

[0017] if the deviation value is greater than the diagnosis threshold value, adding 1 to a cumulative number, and returning to the step of sending the current test input quantity in the current fault information to the to-be-tested drive-by-wire system, so that the to-be-tested drive-by-wire system generates and feeds back a corresponding current execution quantity;

[0018] determining a current theoretical fault diagnosis result based on the cumulative number and the quantity threshold value.

[0019] Optionally, the number of the to-be-tested drive-by-wire systems is two, and the two to-be-tested drive-by-wire systems form a dual-machine hot backup system.

[0020] The determining of the current theoretical fault diagnosis result based on the current test input quantity, the current execution quantity, the test mode and the test range comprises:

[0021] calculating a first deviation value between the current execution quantities, calculating a second deviation value between the current test input quantity and the current execution quantity, and determining a first diagnosis threshold value, a second diagnosis threshold value and a quantity threshold value based on the current test mode and the test range;

[0022] if the first deviation value is greater than the first diagnosis threshold value, or the second deviation value is greater than the second diagnosis threshold value, adding 1 to a cumulative number, and returning to the step of sending the current test input quantity in the current fault information to the to-be-tested drive-by-wire system, so that the to-be-tested drive-by-wire system generates and feeds back a corresponding current execution quantity;

[0023] determining a current theoretical fault diagnosis result based on the cumulative number and the quantity threshold value.

[0024] Optionally, the method further comprises:

[0025] determining a hardware type of a corresponding sensor in the to-be-tested drive-by-wire system based on the fault code type;

[0026] determining a test input range corresponding to the sensor based on the hardware type;

[0027] selecting a plurality of test input quantities from the test input range;

[0028] setting a test mode and a test range corresponding to the test input quantities based on the fault trigger condition;

[0029] taking each group of associated test input quantities, test modes and test ranges as fault test information.

[0030] Optionally, the fault information set is a drive-by-wire system configuration tree, the drive-by-wire system configuration tree has fault code information of drive-by-wire systems with different hardware information, and the fault code information includes a fault code type and a fault code trigger condition;

[0031] The method further comprises:

[0032] obtaining hardware information of the to-be-tested drive-by-wire system;

[0033] finding fault code information corresponding to the to-be-tested drive-by-wire system from the drive-by-wire system configuration tree based on the hardware information;

[0034] extracting a fault code type and a fault trigger condition corresponding to the to-be-tested drive-by-wire system from the found fault code information.

[0035] Optionally, before the step of finding fault code information corresponding to the to-be-tested drive-by-wire system based on the hardware information, the method further comprises:

[0036] obtaining a drive-by-wire system configuration tree, wherein a root node of the drive-by-wire system configuration tree represents a drive-by-wire system, a first-level child node represents different types of drive-by-wire systems, a second-level child node represents components included in each type of drive-by-wire system, and a third-level child node represents component types of the components included in each type of drive-by-wire system;

[0037] sending a fault information request to a fault code database and receiving fault code information fed back by the fault code database, wherein the fault code information further includes fault code descriptions;

[0038] performing word segmentation processing on the fault code descriptions to obtain fault keywords of each fault code description;

[0039] The fault keywords described by each fault code are matched with the drive-by-wire system configuration tree in the direction from the root node to the leaf node in sequence;

[0040] Based on the matching result, each fault code information is taken as a leaf node of the drive-by-wire system configuration tree.

[0041] In addition, to achieve the above object, the application further provides a fault diagnosis function test device, which comprises:

[0042] An information searching module is configured to search for fault code types and fault triggering conditions corresponding to a to-be-tested drive-by-wire system from a fault information set corresponding to a fault diagnosis function;

[0043] An information setting module is configured to set a plurality of groups of fault test information based on the fault code types and fault triggering conditions;

[0044] A function test module is configured to sequentially perform fault diagnosis function tests on the to-be-tested drive-by-wire system through each group of fault test information.

[0045] In addition, to achieve the above object, the application further provides a fault diagnosis function test device, which comprises a memory, a processor and a fault diagnosis function test program stored in the memory and executable on the processor, and the fault diagnosis function test program is configured to implement the steps of the fault diagnosis function test method.

[0046] In addition, to achieve the above object, the application further provides a computer readable storage medium, which stores a fault diagnosis function test program, and the fault diagnosis function test program implements the steps of the fault diagnosis function test method when executed by a processor.

[0047] The application can search for fault code types and fault triggering conditions corresponding to a to-be-tested drive-by-wire system from a fault information set corresponding to a fault diagnosis function, set a plurality of groups of fault test information based on the fault code types and fault triggering conditions, and finally sequentially perform fault diagnosis function tests on the to-be-tested drive-by-wire system through each group of fault test information, thereby realizing automatic generation of fault test information and automatic fault diagnosis function tests, improving the degree of automation in the test process and reducing the test time. BRIEF DESCRIPTION OF DRAWINGS

[0048] Figure 1 A flowchart of a first embodiment of the fault diagnosis function test method of the application;

[0049] Figure 2The flowchart of step S30 in the second embodiment of the fault diagnosis function test method of the present application is shown in the figure.

[0050] Figure 3 The flowchart of step S10 in the third embodiment of the fault diagnosis function test method of the present application is shown in the figure.

[0051] Figure 4 The schematic diagram of the configuration tree of the drive-by-wire system in the third embodiment of the fault diagnosis function test method of the present application is shown in the figure.

[0052] Figure 5 The structural block diagram of an embodiment of the fault diagnosis function test device of the present application is shown in the figure.

[0053] Figure 6 The schematic diagram of the fault diagnosis function test device structure of the hardware running environment involved in the embodiment scheme of the present application is shown in the figure.

[0054] The implementation, functional features and advantages of the present application will be further described with reference to the accompanying drawings in combination with the embodiments. DETAILED DESCRIPTION

[0055] It should be understood that the specific embodiments described herein are only used to explain the present application, and are not used to limit the present application.

[0056] Reference Figure 1 , Figure 1 The flowchart of the first embodiment of the fault diagnosis function test method of the present application is shown in the figure.

[0057] In the first embodiment, the fault diagnosis function test method comprises the following steps:

[0058] S10: searching for the fault code type and the fault trigger condition corresponding to the to-be-tested drive-by-wire system from the fault information set corresponding to the fault diagnosis function.

[0059] It should be noted that the to-be-tested drive-by-wire system is a drive-by-wire system configured on a movable carrier, and the movable carrier has various forms of expression, such as a vehicle, a robot, a flying vehicle and other carriers with moving ability, and the present embodiment does not make specific limitation.

[0060] Of course, when the movable carrier is a vehicle, the drive-by-wire system refers to a system that uses electronic signals to replace the parts connected by mechanical, hydraulic or pneumatic systems, such as shift connecting rods, throttle pull wires, steering gear transmission mechanisms, brakes, throttles, etc., and the drive-by-wire technology requires good real-time performance and high reliability of the network, and some drive-by-wire parts require redundant function implementation to ensure that the basic function of the device can still be realized in a certain fault.

[0061] In a specific implementation, linear systems in a vehicle are mainly divided into five different types of systems, namely, a steer-by-wire system, a brake-by-wire system, a throttle-by-wire system, an air suspension-by-wire system, and a gear shift-by-wire system.

[0062] The steer-by-wire system refers to canceling the mechanical connection between a steering wheel and a steered wheel, using an electrical signal to control the steering of the wheel, and freely designing the angle transmission characteristics and force transmission characteristics of the vehicle steering system to realize many functions that traditional steering systems do not have.

[0063] The brake-by-wire system refers to using an electric wire to replace part or all of the brake pipeline, and controlling the brake force size through a controller to control the electric control element.

[0064] The throttle-by-wire system refers to replacing a cable or a pull rod with a wire harness, and installing a micro motor at the throttle position to drive the throttle opening degree.

[0065] The air suspension-by-wire system refers to providing various state information of the system in operation to the control system through various sensors, and performing feedforward adjustment and control on state parameters such as suspension damping, stiffness, height, and vehicle body posture according to the real-time working conditions of the vehicle.

[0066] The gear shift-by-wire system refers to changing the traditional mechanical manual gear shift to an electronic signal output mode such as a handle, a lever, a turntable, or a button.

[0067] It can be understood that, in order to be supported, the fault diagnosis function needs to have support data required for fault diagnosis, and the fault information set is support data corresponding to the fault diagnosis function. Specifically, the fault information set has fault code types and fault trigger conditions of different types of steer-by-wire systems, and therefore, the fault code types and fault trigger conditions corresponding to the to-be-tested steer-by-wire system can be found from the fault information set corresponding to the fault diagnosis function.

[0068] In a specific implementation, the fault code type is used to represent the type of fault in the steer-by-wire system, for example, a brake pedal fault or a throttle pedal fault.

[0069] It should be understood that the fault trigger condition is a condition used by the fault diagnosis function for fault diagnosis.

[0070] S20: Set multiple groups of fault test information based on the fault code type and the fault trigger condition.

[0071] It should be noted that once the fault code type and fault triggering conditions are determined, the fault test information required for the fault diagnosis function test of the wire control system under test can be determined. Since a single fault test information is accidental and cannot truly reflect the fault diagnosis function, in this embodiment, multiple sets of fault test information need to be set based on the fault code type and fault triggering conditions.

[0072] S30: The fault diagnosis function test of the drive-by-wire system under test is performed sequentially using each group of fault test information.

[0073] Understandably, since each set of fault test information can be used to perform fault diagnosis function tests on the drive-by-wire system under test independently, by sequentially performing fault diagnosis function tests on the drive-by-wire system under test using each set of fault test information, the test results corresponding to multiple sets of fault test information can be combined to determine whether the fault diagnosis function is normal.

[0074] In a specific implementation, when the fault diagnosis function is abnormal, the cause of the abnormality can be analyzed based on the test results. Based on the analysis results, the fault triggering conditions corresponding to the fault diagnosis function can be logically modified or the detection standards corresponding to the fault diagnosis function can be adjusted. Then, regression testing can be performed on the wire control system under test after the logical modification or standard adjustment.

[0075] This embodiment can search for the fault code type and fault triggering condition corresponding to the wire control system under test from the fault information set corresponding to the fault diagnosis function. Then, based on the fault code type and fault triggering condition, multiple sets of fault test information are set. Finally, the fault diagnosis function test is performed on the wire control system under test in turn through each set of fault test information. This realizes the automatic generation of fault test information and the automatic testing of the fault diagnosis function, which improves the degree of automation in the testing process and reduces the testing time.

[0076] like Figure 2 As shown, a second embodiment of the fault diagnosis function test method of the present invention is proposed based on the first embodiment. In this embodiment, each group of fault test information includes: test input quantity, test method and test range.

[0077] Step S30 specifically includes:

[0078] S31: Traverse the fault test information and use the traversed fault test information as the current fault test information.

[0079] It should be noted that since the fault test information consists of multiple sets, the fault test information can be traversed by set. In other words, the current fault test information is the set of fault test information that has been traversed.

[0080] S32: Send the current test input quantity in the current fault information to the wire control system under test, so that the wire control system under test generates and feeds back the corresponding current execution quantity, and generates and feeds back the current actual fault diagnosis result corresponding to the current execution quantity.

[0081] It is understandable that, since each group of fault test information includes: test input quantity, test method, and test range, the current fault information includes the current test input quantity, the current test method, and the current test range.

[0082] In practical implementation, since the drive-by-wire system of a car converts the driver's operation into electrical signals through sensors, and transmits the electrical signals to the electronic control unit through the CAN bus, and the electronic control unit drives the actuator, the current test input can be understood as an electrical signal generated by the analog sensor. After the current test input is input into the drive-by-wire system under test, the drive-by-wire system under test will perform a corresponding response action and generate the corresponding current execution quantity.

[0083] For multiple sets of fault test information, in this embodiment, each set of fault test information includes: test input quantity, test method, and test range. Therefore, multiple sets of fault test information need to be set in advance. In order to quickly set multiple sets of fault test information, step S20 can be specifically as follows: first, determine the hardware type of the corresponding sensor in the wire control system under test based on the fault code type; then, determine the test input range corresponding to the sensor based on the hardware type; then, select multiple test input quantities from the test input range; then, set the test method and test range corresponding to the test input quantities based on the fault triggering conditions; and finally, use the associated test input quantity, test method, and test range of each set as fault test information.

[0084] Understandably, since different sensors have different electrical signal ranges, it is necessary to first determine the hardware type of the corresponding sensor in the drive-by-wire system under test. The fault code type reflects the object that needs to be tested in the drive-by-wire system under test. Therefore, the hardware type of the corresponding sensor in the drive-by-wire system under test can be determined based on the fault code type, and then the test input range corresponding to the sensor can be determined based on the hardware type.

[0085] In a specific implementation, after determining the hardware type of the sensor, the corresponding test input range of the sensor can be determined based on the hardware type.

[0086] Assuming the fault code type is accelerator pedal fault, it can be determined that the type of the drive-by-wire system under test is a drive-by-wire throttle system, and the sensor is an accelerator pedal displacement sensor. Then, the test input range corresponding to the accelerator pedal displacement sensor can be determined. For example, if the electrical signal generated by the accelerator pedal displacement sensor is a voltage signal in the range of 0 to 5V, then the voltage signal in the range of 0 to 5V can be used as the test input range.

[0087] Of course, when selecting multiple test inputs from the test input range, a random selection method can be used. That is, determine the number of test inputs to be selected, and then randomly select that number of test inputs from the test input range. This can quickly select the corresponding test inputs. However, since the selection of test inputs is relatively random, multiple test inputs may sometimes be selected too closely, resulting in less than ideal test results. Therefore, in order to improve the test results and ensure a more comprehensive test of the test inputs, in this embodiment, assuming the number of test inputs is n, the test input range can be divided into n+1 equal parts, and the intersection of the n+1 equal parts can be used as the test inputs. For example, if n is 4 and the electrical signal range is a voltage signal of 0 to 5V, then 0 to 5V can be divided into 5 equal parts, namely 0 to 1V, 1 to 2V, 2 to 3V, 3 to 4V, and 4 to 5V. In this case, the test inputs can be selected as voltage signals of 1V, 2V, 3V, and 4V.

[0088] It should be understood that after selecting multiple test input quantities, the test method and test range corresponding to the test input quantities can be set based on the fault triggering conditions (i.e., the basis for generating fault diagnosis results corresponding to the fault diagnosis function). In other words, the corresponding test method and test range can be set based on the parameters and triggering logic involved in the fault triggering conditions, and the test input quantities, test methods and test ranges associated with each group can be used as fault test information.

[0089] S33: Determine the current theoretical fault diagnosis result based on the current test input, current execution, test method, and test scope.

[0090] It should be noted that the current test input quantity in the current fault test information can be understood as the theoretical value corresponding to the current execution quantity, while the current execution quantity can be understood as the actual value. Therefore, it is possible to determine whether a fault has been diagnosed based on the current test input quantity and the current execution quantity, and the judgment result is understood as the theoretical fault diagnosis result.

[0091] In specific implementation, to ensure the accuracy of the theoretical fault diagnosis result, step S33 can specifically involve first calculating the deviation between the current test input and the current execution, and determining the corresponding diagnostic threshold and quantity threshold based on the current test method and the current test range. If the deviation is greater than the diagnostic threshold, the cumulative count is incremented by 1, and the step of sending the current test input in the current fault information to the wire control system under test so that the wire control system under test generates and feeds back the corresponding current execution is returned. Then, the current theoretical fault diagnosis result is determined based on the cumulative count and quantity threshold.

[0092] Understandably, the current testing method determines the types of data involved in the test, and the current testing scope determines the boundary values ​​of the parameters involved in the test. Therefore, by combining the two, the corresponding diagnostic threshold and quantity threshold can be determined.

[0093] Assuming the drive-by-wire system under test is a brake-by-wire system, if fault diagnosis of the brake pedal signal is required, the current test input can be the brake pedal opening, and the current execution input is the vehicle's feedback brake pedal opening. If the deviation between the two is too large within a certain time period (i.e., the cumulative number of times exceeds the threshold) (i.e., the deviation is greater than the diagnostic threshold), the current theoretical fault diagnosis result can be considered to be faulty. Since the drive-by-wire system under test has a fault diagnosis function, it should also generate and feedback the current actual fault diagnosis result corresponding to the current execution input. At this time, the fault diagnosis function can be judged to be normal based on whether the current actual fault diagnosis result is faulty.

[0094] It should be understood that, for drive-by-wire systems, since hardware failures can occur at times, it is usually necessary to set up corresponding redundant hardware. In other words, some drive-by-wire systems will use dual-machine hot standby technology to improve security. Therefore, the number of drive-by-wire systems to be tested is two, and the two drive-by-wire systems to be tested form a dual-machine hot standby system.

[0095] Accordingly, step S33 can specifically involve first calculating the first deviation value between the current execution quantities, calculating the second deviation value between the current test input quantity and the current execution quantity, and determining the corresponding first diagnostic threshold, second diagnostic threshold, and quantity threshold based on the current test method and current test range. If the first deviation value is greater than the first diagnostic threshold, or the second deviation value is greater than the second diagnostic threshold, then the cumulative count is incremented by 1, and the step of sending the current test input quantity in the current fault information to the wire control system under test so that the wire control system under test generates and feeds back the corresponding current execution quantity is returned. Then, the current theoretical fault diagnosis result is determined based on the cumulative count and quantity threshold.

[0096] It should be noted that for a dual-machine hot standby system, the fault diagnosis function needs to consider not only the deviation between the current test input and the current execution, but also the consistency of the execution of the dual-machine hot standby system. This is because the execution of both linear systems under test may be used. If the deviation between the execution of the two linear systems under test is too large, unsafe situations may occur. Therefore, it is necessary to calculate the first deviation between the current execution (since both linear systems under test will generate corresponding executions, and the two executions are not necessarily consistent) and the current execution. At this time, due to the addition of this deviation, it is also necessary to determine the corresponding diagnostic threshold based on the current test method and the current test range.

[0097] Of course, since the two linear systems under test may share some hardware, it is not possible to generate two current execution quantities based on a single current test input. Therefore, the current test input can be sent to the two linear systems under test one after the other, and the two linear systems under test can generate their respective current execution quantities.

[0098] S34: Perform fault diagnosis function testing based on the current theoretical fault diagnosis results and the current actual fault diagnosis results.

[0099] In practice, the theoretical fault diagnosis results can be compared with the actual fault diagnosis results.

[0100] If the theoretical fault diagnosis result is consistent with the actual fault diagnosis result, it can be understood that the fault diagnosis function test is normal for the current fault test information.

[0101] If the theoretical fault diagnosis results and the actual fault diagnosis results are inconsistent, it can be understood that the fault diagnosis function test is not normal for the current fault test information.

[0102] This embodiment can send the current test input quantity from the current fault information to the wire control system under test, so that the wire control system under test can generate and feedback the corresponding current execution quantity, and generate and feedback the current actual fault diagnosis result corresponding to the current execution quantity. Then, based on the current test input quantity, current execution quantity, test method, and test scope, the current theoretical fault diagnosis result is determined. Finally, the fault diagnosis function test is performed based on the current theoretical fault diagnosis result and the current actual fault diagnosis result. Since the current theoretical fault diagnosis result is determined based on the current test input quantity, current execution quantity, test method, and test scope, it can theoretically reflect whether a fault exists. Combining the current actual fault diagnosis result generated and fed back by the wire control system under test, it can more accurately determine whether the fault diagnosis function is normal.

[0103] like Figure 3 As shown, a third embodiment of the fault diagnosis function test method of the present invention is proposed based on the first embodiment or the second embodiment. In this embodiment, the fault information set is a wire control system configuration tree. The wire control system configuration tree contains fault code information of wire control systems with different hardware information. The fault code information includes fault code type and fault code triggering condition.

[0104] Step S10 specifically includes:

[0105] S11: Obtain the hardware information of the wire-controlled system under test.

[0106] It should be noted that the hardware involved in the wire-controlled system under test is fixed, therefore, the hardware information of the wire-controlled system under test can be obtained.

[0107] S12: Based on the hardware information, search for the fault code information corresponding to the drive-by-wire system under test from the drive-by-wire system configuration tree.

[0108] It is understandable that, since the fault information set is a drive-by-wire system configuration tree, and the drive-by-wire system configuration tree contains fault code information of drive-by-wire systems with different hardware information, the fault code information corresponding to the drive-by-wire system under test can be found based on the hardware information.

[0109] Since it is necessary to search for the fault code information corresponding to the drive-by-wire system under test from the drive-by-wire system configuration tree, it is necessary to establish the drive-by-wire system configuration tree in advance. To quickly establish the drive-by-wire system configuration tree, in this embodiment, the drive-by-wire system configuration tree can be obtained first, referring to... Figure 4 The root node of the drive-by-wire system configuration tree represents the drive-by-wire system, the first-level child nodes represent different types of drive-by-wire systems, the second-level child nodes represent the components included in each type of drive-by-wire system, and the third-level child nodes represent the component types of the components included in each type of drive-by-wire system. Then, a fault information request is sent to the fault code database, and fault code information fed back from the fault code database is received. The fault code information also includes a fault code description. The fault code description is then segmented to obtain fault keywords for each fault code description. Then, the fault keywords of each fault code description are sequentially matched with the drive-by-wire system configuration tree in the direction from the root node to the leaf node. Finally, based on the matching results, each fault code information is used as a leaf node of the drive-by-wire system configuration tree.

[0110] It should be noted that the fault code database contains fault code information for different drive-by control systems with different hardware information. In other words, the fault code database can be used to obtain the corresponding fault code information for all drive-by control systems.

[0111] Understandably, the fault code information also includes a fault code description, which details the specific fault. This means the fault code description indicates which component in the steer-by-wire system is malfunctioning. However, since the expression of the fault code description may not be consistent with the expressions of each node in the steer-by-wire system configuration tree, fuzzy matching can be used in this embodiment to ensure a high success rate of matching. For example, assuming the fault code description is: "The execution amount of the floor-mounted throttle component is continuously significantly different from the set value," it can be segmented into words such as "floor-mounted," "throttle component," "execution amount," "set value," "continuous," "difference," and "significantly different." Fuzzy matching can then determine that the fault code description refers to the floor-mounted throttle pedal in the steer-by-wire system. Therefore, the fault code information corresponding to this description can be added to the leaf node of the floor-mounted node branch under the throttle pedal in the steer-by-wire system configuration tree.

[0112] Of course, since not all hardware in the drive-by-wire system needs to be tested, not all third-level child nodes in the drive-by-wire system configuration tree will have corresponding fault code information added.

[0113] S13: Extract the fault code type and fault triggering conditions corresponding to the drive-by-wire system under test from the fault code information found.

[0114] In a specific implementation, since the fault code information includes the fault code type and the fault code triggering condition, the fault code type and fault triggering condition corresponding to the drive-by-wire system under test can be extracted from the found fault code information.

[0115] This embodiment sets up a wire control system configuration tree. Since the configuration tree contains fault code information of wire control systems with different hardware information, and the fault code information includes fault code type and fault code triggering conditions, it is possible to find the fault code type and fault triggering conditions corresponding to the wire control system under test more quickly and conveniently.

[0116] Furthermore, embodiments of the present invention also propose a fault diagnosis function testing device, referring to... Figure 5 The fault diagnosis function testing device includes:

[0117] Information lookup module 10 is used to look up the fault code type and fault triggering conditions corresponding to the drive-by-wire system under test from the fault information set corresponding to the fault diagnosis function;

[0118] Information setting module 20 is used to set multiple sets of fault test information based on the fault code type and fault triggering conditions;

[0119] The functional test module 30 is used to perform fault diagnosis function tests on the wire control system under test in turn by sequentially using each group of fault test information.

[0120] This embodiment, through the above scheme, can search for the fault code type and fault triggering condition corresponding to the wire control system under test from the fault information set corresponding to the fault diagnosis function. Then, based on the fault code type and fault triggering condition, multiple sets of fault test information are set. Finally, the fault diagnosis function test of the wire control system under test is performed sequentially through each set of fault test information. This realizes the automatic generation of fault test information and the automatic testing of the fault diagnosis function, thereby improving the degree of automation in the testing process and reducing the testing time.

[0121] It should be noted that each module in the above-mentioned device can be used to implement each step in the above-mentioned method and achieve the corresponding technical effect. This embodiment will not elaborate further here.

[0122] Reference Figure 6 , Figure 6 This is a schematic diagram of the structure of a fault diagnosis function testing device for the hardware operating environment involved in the embodiments of the present invention.

[0123] like Figure 6 As shown, the fault diagnosis function test device may include: a processor 1001, such as a CPU, a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. The communication bus 1002 is used to establish communication between these components. The user interface 1003 may include a display screen and an input unit such as a keyboard; optionally, the user interface 1003 may also include a standard wired interface or a wireless interface. The network interface 1004 may optionally include a standard wired interface or a wireless interface (such as a Wi-Fi interface). The memory 1005 may be high-speed RAM or non-volatile memory, such as a disk drive. Optionally, the memory 1005 may also be a storage device independent of the aforementioned processor 1001.

[0124] Those skilled in the art will understand that Figure 6 The structure shown does not constitute a limitation on the fault diagnosis function test equipment, and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0125] like Figure 6 As shown, the memory 1005, which serves as a computer storage medium, may include an operating system, a network communication module, a user interface module, and a fault diagnosis function test program.

[0126] exist Figure 6In the fault diagnosis function test equipment shown, the network interface 1004 is mainly used for data communication with an external network; the user interface 1003 is mainly used for receiving user input commands; the movable carrier calls the fault diagnosis function test program stored in the memory 1005 through the processor 1001 and performs the following operations:

[0127] Search for the fault code type and fault triggering condition corresponding to the drive-by-wire system under test from the fault information set corresponding to the fault diagnosis function;

[0128] Multiple sets of fault test information are set based on the fault code type and fault triggering conditions;

[0129] The fault diagnosis function of the drive-by-wire system under test is tested sequentially using each set of fault test information.

[0130] Furthermore, each group of fault test information includes: test input quantity, test method, and test range; the processor 1001 can call the fault diagnosis function test program stored in the memory 1005 and also perform the following operations:

[0131] The fault test information is traversed, and the traversed fault test information is used as the current fault test information;

[0132] The current test input quantity in the current fault information is sent to the wire control system under test, so that the wire control system under test generates and feeds back the corresponding current execution quantity, and generates and feeds back the current actual fault diagnosis result corresponding to the current execution quantity;

[0133] The current theoretical fault diagnosis result is determined based on the current test input, current execution, test method, and test scope.

[0134] The fault diagnosis function is tested based on the current theoretical fault diagnosis results and the current actual fault diagnosis results.

[0135] Furthermore, the processor 1001 can call the fault diagnosis function test program stored in the memory 1005 and also perform the following operations:

[0136] Calculate the deviation between the current test input and the current execution, and determine the corresponding diagnostic threshold and quantity threshold based on the current test method and the current test range;

[0137] If the deviation value is greater than the diagnostic threshold, the cumulative count is incremented by 1, and the step of sending the current test input quantity in the current fault information to the wire control system under test, so that the wire control system under test generates and feeds back the corresponding current execution quantity, is returned.

[0138] The current theoretical fault diagnosis result is determined based on the cumulative number of occurrences and the quantity threshold.

[0139] Furthermore, the number of drive-by-wire systems under test is two, and the two drive-by-wire systems under test form a dual-machine hot standby system; the processor 1001 can call the fault diagnosis function test program stored in the memory 1005, and also perform the following operations:

[0140] Calculate the first deviation value between the current execution volume, calculate the second deviation value between the current test input volume and the current execution volume, and determine the corresponding first diagnostic threshold, second diagnostic threshold and quantity threshold based on the current test method and the current test range;

[0141] If the first deviation value is greater than the first diagnostic threshold, or the second deviation value is greater than the second diagnostic threshold, then the cumulative count is incremented by 1, and the step of sending the current test input quantity in the current fault information to the wire control system under test so that the wire control system under test generates and feeds back the corresponding current execution quantity is returned.

[0142] The current theoretical fault diagnosis result is determined based on the cumulative number of occurrences and the quantity threshold.

[0143] Furthermore, the processor 1001 can call the fault diagnosis function test program stored in the memory 1005 and also perform the following operations:

[0144] The hardware type of the corresponding sensor in the drive-by-wire system under test is determined based on the fault code type.

[0145] Determine the test input range corresponding to the sensor based on the hardware type;

[0146] Select multiple test input quantities from the test input range;

[0147] Based on the fault triggering conditions, set the test method and test range corresponding to the test input quantity;

[0148] The test input quantities, test methods, and test ranges associated with each group are used as fault test information.

[0149] Furthermore, the fault information set is a drive-by-wire system configuration tree, which contains fault code information for drive-by-wire systems with different hardware information. The fault code information includes the fault code type and the fault code triggering condition. The processor 1001 can call the fault diagnosis function test program stored in the memory 1005 and also perform the following operations:

[0150] Obtain the hardware information of the wire-controlled system under test;

[0151] Based on the hardware information, search the drive-by-wire system configuration tree for the fault code information corresponding to the drive-by-wire system under test;

[0152] Extract the fault code type and fault triggering conditions corresponding to the drive-by-wire system under test from the fault code information found.

[0153] Furthermore, the processor 1001 can call the fault diagnosis function test program stored in the memory 1005 and also perform the following operations:

[0154] Obtain the configuration tree of the wire control system. The root node of the configuration tree represents the wire control system, the first-level child nodes represent different types of wire control systems, the second-level child nodes represent the components included in each type of wire control system, and the third-level child nodes represent the component types of the components included in each type of wire control system.

[0155] Send a fault information request to the fault code database and receive fault code information from the fault code database, wherein the fault code information also includes a fault code description;

[0156] The fault code descriptions are segmented to obtain the fault keywords for each fault code description;

[0157] The fault keywords describing each fault code are sequentially matched with the configuration tree of the drive-by-wire system in the direction from the root node to the leaf node;

[0158] Based on the matching results, each fault code information is used as a leaf node in the configuration tree of the drive-by-wire system.

[0159] This embodiment, through the above scheme, can search for the fault code type and fault triggering condition corresponding to the wire control system under test from the fault information set corresponding to the fault diagnosis function. Then, based on the fault code type and fault triggering condition, multiple sets of fault test information are set. Finally, the fault diagnosis function test of the wire control system under test is performed sequentially through each set of fault test information. This realizes the automatic generation of fault test information and the automatic testing of the fault diagnosis function, thereby improving the degree of automation in the testing process and reducing the testing time.

[0160] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or system. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or system that includes that element.

[0161] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0162] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of the present invention.

[0163] The above are merely preferred embodiments of the present invention and do not limit the scope of the patent. Any equivalent structural or procedural transformations made based on the description and drawings of the present invention, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of the present invention.

Claims

1. A method for testing fault diagnosis functions, characterized in that, The fault diagnosis function test method includes the following steps: Search for the fault code type and fault triggering condition corresponding to the drive-by-wire system under test from the fault information set corresponding to the fault diagnosis function; Multiple sets of fault test information are set based on the fault code type and fault triggering conditions; The fault diagnosis function test of the drive-by-wire system under test is performed sequentially using each set of fault test information. The fault test information for each group includes: test input quantity, test method, and test range; The step of sequentially performing fault diagnosis function tests on the drive-by-wire system under test using each set of fault test information includes: The fault test information is traversed, and the traversed fault test information is used as the current fault test information; The current test input quantity in the current fault test information is sent to the wire control system under test, so that the wire control system under test generates and feeds back the corresponding current execution quantity, and generates and feeds back the current actual fault diagnosis result corresponding to the current execution quantity; The current theoretical fault diagnosis result is determined based on the current test input, current execution, test method, and test scope. The fault diagnosis function is tested based on the current theoretical fault diagnosis results and the current actual fault diagnosis results.

2. The fault diagnosis function test method as described in claim 1, characterized in that, The process of determining the current theoretical fault diagnosis result based on the current test input, current execution volume, test method, and test scope includes: Calculate the deviation between the current test input and the current execution, and determine the corresponding diagnostic threshold and quantity threshold based on the current test method and the current test range; If the deviation value is greater than the diagnostic threshold, the cumulative count is incremented by 1, and the step of sending the current test input quantity in the current fault test information to the wire control system under test, so that the wire control system under test generates and feeds back the corresponding current execution quantity, is returned. The current theoretical fault diagnosis result is determined based on the cumulative number of occurrences and the quantity threshold.

3. The fault diagnosis function testing method as described in claim 1, characterized in that, The number of the wire control systems to be tested is two, and the two wire control systems to be tested form a dual-machine hot standby system; The process of determining the current theoretical fault diagnosis result based on the current test input, current execution volume, test method, and test scope includes: Calculate the first deviation value between the current execution volume, calculate the second deviation value between the current test input volume and the current execution volume, and determine the corresponding first diagnostic threshold, second diagnostic threshold and quantity threshold based on the current test method and the current test range; If the first deviation value is greater than the first diagnostic threshold, or the second deviation value is greater than the second diagnostic threshold, then the cumulative count is incremented by 1, and the step of sending the current test input quantity in the current fault test information to the wire control system under test, so that the wire control system under test generates and feeds back the corresponding current execution quantity, is returned. The current theoretical fault diagnosis result is determined based on the cumulative number of occurrences and the quantity threshold.

4. The fault diagnosis function test method according to any one of claims 1 to 3, characterized in that, The system sets multiple sets of fault test information based on the fault code type and fault triggering conditions, including: The hardware type of the corresponding sensor in the drive-by-wire system under test is determined based on the fault code type. Determine the test input range corresponding to the sensor based on the hardware type; Select multiple test input quantities from the test input range; Based on the fault triggering conditions, set the test method and test range corresponding to the test input quantity; The test input quantities, test methods, and test ranges associated with each group are used as fault test information.

5. The fault diagnosis function test method according to any one of claims 1 to 3, characterized in that, The fault information set is a drive-by-wire system configuration tree, which contains fault code information of drive-by-wire systems with different hardware information. The fault code information includes fault code type and fault triggering condition. The step of searching for the fault code type and fault triggering conditions corresponding to the drive-by-wire system under test from the fault information set corresponding to the fault diagnosis function includes: Obtain the hardware information of the wire-controlled system under test; Based on the hardware information, search the drive-by-wire system configuration tree for the fault code information corresponding to the drive-by-wire system under test; Extract the fault code type and fault triggering conditions corresponding to the drive-by-wire system under test from the fault code information found.

6. The fault diagnosis function test method as described in claim 5, characterized in that, Before searching for the fault code information corresponding to the drive-by-wire system under test based on the hardware information, the method further includes: Obtain the configuration tree of the wire control system. The root node of the configuration tree represents the wire control system, the first-level child nodes represent different types of wire control systems, the second-level child nodes represent the components included in each type of wire control system, and the third-level child nodes represent the component types of the components included in each type of wire control system. Send a fault information request to the fault code database and receive fault code information from the fault code database, wherein the fault code information also includes a fault code description; The fault code descriptions are segmented to obtain the fault keywords for each fault code description; The fault keywords describing each fault code are sequentially matched with the configuration tree of the drive-by-wire system in the direction from the root node to the leaf node; Based on the matching results, each fault code information is used as a leaf node in the configuration tree of the drive-by-wire system.

7. A fault diagnosis function testing device, characterized in that, The fault diagnosis function testing device includes: The information search module is used to search for the fault code type and fault triggering conditions corresponding to the drive-by-wire system under test from the fault information set corresponding to the fault diagnosis function. The information setting module is used to set multiple sets of fault test information based on the fault code type and fault triggering conditions; The functional testing module is used to perform fault diagnosis function tests on the drive-by-wire system under test by sequentially using each set of fault test information. The fault test information for each group includes: test input quantity, test method, and test range; The step of sequentially performing fault diagnosis function tests on the drive-by-wire system under test using each set of fault test information includes: The fault test information is traversed, and the traversed fault test information is used as the current fault test information; The current test input quantity in the current fault test information is sent to the wire control system under test, so that the wire control system under test generates and feeds back the corresponding current execution quantity, and generates and feeds back the current actual fault diagnosis result corresponding to the current execution quantity; The current theoretical fault diagnosis result is determined based on the current test input, current execution, test method, and test scope. The fault diagnosis function is tested based on the current theoretical fault diagnosis results and the current actual fault diagnosis results.

8. A fault diagnosis function testing device, characterized in that, The fault diagnosis function test device includes: a memory, a processor, and a fault diagnosis function test program stored in the memory and executable on the processor, wherein the fault diagnosis function test program is configured to implement the steps of the fault diagnosis function test method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a fault diagnosis function test program, which, when executed by a processor, implements the steps of the fault diagnosis function test method as described in any one of claims 1 to 6.

Images