Test method and device for detecting vehicle fault diagnosis system

By inputting preset fault information into the vehicle control system, obtaining and proofreading the fault code, diagnosis vector code and execution information, the problem of low testing efficiency in traditional testing methods is solved, and efficient monitoring and accurate judgment of the vehicle fault handling process is achieved. .

CN119087961AActive Publication Date: 2024-12-06CHINA FAW CO LTD

Patent Information

Application Number
CN202411152795.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-21
Publication Date
2024-12-06
Estimated Expiration
2044-08-21

AI Technical Summary

Technical Problem

Due to the numerous functions and complex working conditions, traditional vehicle fault diagnosis and testing methods have huge test volume, low efficiency, long time, and difficult to effectively detect the fault handling capabilities of the vehicle control system.

Method used

By inputting preset fault information into the vehicle control system, obtaining fault codes, diagnostic vector codes and execution information, and proofing, ensuring its accuracy, so as to monitor the fault processing process and improve testing efficiency.

Benefits of technology

Through the fault diagnosis requirement table, the fault code and diagnostic vector code are proofread, their accuracy is judged, and the fault processing process is monitored, which improves the testing efficiency, timely aborts the test process, and improves the testing efficiency of the fault processing function of the vehicle control system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119087961A_ABST
    Figure CN119087961A_ABST
Patent Text Reader

Abstract

The invention provides a test method and device for detecting a vehicle fault diagnosis system, and the method comprises the steps: inputting preset fault information to a vehicle control system, so as to obtain at least one fault code generated by the vehicle control system; checking the at least one fault code; when the fault code is checked and confirmed to be correct, receiving at least one first diagnosis vector code generated by the vehicle control system according to the fault code, and checking the at least one first diagnosis vector code; wherein one first diagnosis vector code is used for representing one fault processing strategy; when the first diagnosis vector code is checked and confirmed to be correct, receiving at least one piece of first execution information generated by the vehicle control system according to the at least one first diagnosis vector code, and checking the first execution information; wherein one piece of first execution information is used for driving the vehicle control system to control one execution component or multiple execution components to change the state. The test efficiency is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of vehicle control systems, and in particular to a testing method and device for detecting a vehicle fault diagnosis system. Background Art

[0002] Compared with traditional cars, hybrid cars have added high-voltage components such as high-voltage batteries and motors, and the electrical and electronic control systems are more complex. Any component in the system may fail, such as sensor failure, IO failure, PWM interface failure, CAN communication failure, LIN communication failure, motor system failure, battery system failure, engine system failure, cooling system failure, etc., which may cause the car's performance to decline or fail to start, or even cause major safety accidents. Therefore, the vehicle fault diagnosis function is an important guarantee for vehicle safety and reliability, so it needs to be fully tested in the development stage, that is, it is necessary to detect whether the vehicle's control system can correctly solve its various faults.

[0003] According to the traditional testing method, since the vehicle control system involves many functions and each function involves many working conditions, the fault handling measures triggered by each function under different working conditions may be the same or different. Therefore, it is necessary to exhaustively test all functions and all working conditions, resulting in a large test volume and low test efficiency, which leads to a long test time. Summary of the invention

[0004] The object of the present invention is to provide a testing method and device for detecting a vehicle fault diagnosis system, so as to solve one or more technical problems existing in the prior art and at least provide a beneficial choice or create conditions.

[0005] The technical solutions adopted to solve the above technical problems are:

[0006] The present invention provides a testing method for detecting a vehicle fault diagnosis system, comprising:

[0007] Inputting preset fault information into a vehicle control system to obtain at least one fault code generated by the vehicle control system;

[0008] Verifying at least one of the fault codes to determine whether the fault code is correct;

[0009] When the fault code is checked and confirmed to be correct, receiving at least one first diagnostic vector code generated by the vehicle control system according to the fault code, and checking at least one of the first diagnostic vector codes to determine whether the first diagnostic vector code is correct; wherein a first diagnostic vector code is used to represent a fault handling strategy;

[0010] After the first diagnostic vector code is proofread and confirmed to be correct, at least one first execution information generated by the vehicle control system based on at least one of the first diagnostic vector codes is received, and the first execution information is proofread to determine whether the first execution information is correct; wherein, one first execution information is used to drive the vehicle control system to control an execution component or multiple execution components to change state.

[0011] As a further improvement of the above technical solution, the preset fault information includes a fault signal, and the inputting the preset fault information into the vehicle control system to obtain at least one fault code generated by the vehicle control system includes:

[0012] The fault signal is generated according to a test sequence, and the fault signal is input into the vehicle control system to obtain at least one fault code generated by the vehicle control system according to the fault signal to simulate a vehicle fault environment; wherein the test sequence includes multiple fault numbers, multiple fault codes and multiple diagnostic vector categories, and multiple different fault numbers, multiple different fault codes and multiple different diagnostic vector categories are established in a one-to-one correspondence according to a table.

[0013] As a further improvement of the above technical solution, after the first execution information is checked and confirmed to be correct, a first designated trigger diagnostic vector signal is sequentially input into the vehicle control system under a plurality of different working conditions to obtain a second diagnostic vector code sequentially generated by the vehicle control system under a plurality of different working conditions, and a second diagnostic vector code is checked to determine whether the second diagnostic vector code is correct; wherein a second diagnostic vector code is used to represent a fault handling strategy;

[0014] After the second diagnostic vector code is proofread and confirmed to be correct, the vehicle control system receives second execution information generated based on the second diagnostic vector code, and proofreads the second execution information to determine whether the second execution information is correct; wherein, a second execution information is used to drive the vehicle control system to control an execution component or multiple execution components to change state.

[0015] As a further improvement of the above technical solution, the testing method further includes:

[0016] After the first execution information is checked and confirmed to be correct, a first designated trigger diagnostic vector signal is sequentially input to the vehicle control system under a plurality of different working conditions; including:

[0017] When the first execution information is checked and confirmed to be correct, the first designated trigger diagnostic vector signal is sequentially input into the vehicle control system under a variety of different operating conditions according to a test sequence.

[0018] As a further improvement of the above technical solution, the testing method further includes:

[0019] When the second execution information is checked and confirmed to be correct, a plurality of second designated trigger diagnostic vector signals having conflicting fault handling strategies are input to the vehicle control system, or a plurality of second designated trigger diagnostic vector signals having a preset priority response level are input to the vehicle control system to obtain at least one third diagnostic vector code generated by the vehicle control system, and check at least one of the third diagnostic vector codes to determine whether the third diagnostic vector code is correct; wherein a third diagnostic vector code is used to represent a fault handling strategy;

[0020] After the third diagnostic vector code is proofread and confirmed to be correct, the vehicle control system receives third execution information generated based on at least one of the third diagnostic vector codes, and proofreads the third execution information to determine whether the third execution information is correct; wherein, one third execution information is used to drive the vehicle control system to control an execution component or multiple execution components to change state.

[0021] As a further improvement of the above technical solution, when the second execution information is checked and confirmed to be correct, a plurality of second designated trigger diagnostic vector signals with functional conflicts are input to the vehicle control system, or a plurality of second designated trigger diagnostic vector signals with preset priority response levels are input to the vehicle control system, including:

[0022] When the second execution information is proofread and confirmed to be correct, a plurality of second designated trigger diagnostic vector signals having conflicting processing strategies are input into the vehicle control system in sequence according to the test sequence, or a plurality of second designated trigger diagnostic vector signals having preset priority response levels are input into the vehicle control system.

[0023] The present invention also provides a testing device for detecting a vehicle fault diagnosis system, comprising:

[0024] A fault injection module, used to input preset fault information into the vehicle control system;

[0025] A fault code acquisition module, used to acquire at least one fault code generated by the vehicle control system;

[0026] A diagnostic vector acquisition module, used to receive at least one first diagnostic vector code generated by the vehicle control system according to the fault code; wherein a first diagnostic vector code is used to represent a fault handling strategy;

[0027] A fault processing related data acquisition module, used for receiving at least one first execution information generated by the vehicle control system according to at least one of the first diagnostic vector codes; wherein one first execution information is used to drive the vehicle control system to control one execution component or multiple execution components to change state;

[0028] A data analysis module is used to proofread at least one of the fault codes to determine whether the fault code is correct; and to proofread at least one of the first diagnostic vector codes to determine whether the first diagnostic vector code is correct; and to proofread the first execution information to determine whether the first execution information is correct.

[0029] As a further improvement of the above technical solution, the testing device further includes:

[0030] The vehicle fault environment simulation module is used to simulate the vehicle fault environment according to the fault signal input by the fault injection module to input preset fault information into the vehicle control system.

[0031] As a further improvement of the above technical solution, the testing device further includes:

[0032] A diagnostic vector injection module, used to sequentially input a first designated trigger diagnostic vector signal to a vehicle control system under a plurality of different operating conditions;

[0033] The diagnostic vector acquisition module is also used to obtain a second diagnostic vector code sequentially generated by the vehicle control system under a plurality of different working conditions; wherein a second diagnostic vector code is used to represent a fault handling strategy;

[0034] The fault processing related data acquisition module is also used to receive second execution information generated by the vehicle control system according to one of the second diagnostic vector codes; wherein one of the second execution information is used to drive the vehicle control system to control one or more execution components to change state;

[0035] The data analysis module is also used to proofread a second diagnostic vector code to determine whether the second diagnostic vector code is correct; and is used to proofread the second execution information to determine whether the second execution information is correct.

[0036] As a further improvement of the above technical solution, the diagnostic vector injection module is further used to input a plurality of second designated trigger diagnostic vector signals having conflicting fault handling strategies into the vehicle control system, or to input a plurality of second designated trigger diagnostic vector signals having a preset priority response level into the vehicle control system;

[0037] The diagnostic vector acquisition module is further used to acquire at least one third diagnostic vector code generated by the vehicle control system; wherein a third diagnostic vector code is used to represent a fault handling strategy;

[0038] The fault processing related data acquisition module is also used to receive third execution information generated by the vehicle control system according to at least one of the third diagnostic vector codes; wherein one third execution information is used to drive the vehicle control system to control one execution component or multiple execution components to change state;

[0039] The data analysis module is further used to proofread at least one of the third diagnostic vector codes to determine whether the third diagnostic vector code is correct; and to proofread the third execution information to determine whether the third execution information is correct.

[0040] As a further improvement of the above technical solution, the testing device also includes a test sequence generation module, which is used to generate a test sequence, and the fault injection module, the fault code acquisition module, the diagnostic vector acquisition module, and the fault processing related data acquisition module are all connected to the test sequence generation module to respectively obtain the test sequence; wherein, the test sequence includes multiple fault numbers, multiple fault codes and multiple diagnostic vector categories, and multiple different fault numbers, multiple different fault codes and multiple different diagnostic vector categories are established in a one-to-one correspondence according to a table.

[0041] A computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the test method for detecting a vehicle fault diagnosis system is implemented.

[0042] The beneficial effects of the present invention are:

[0043] A test method for detecting a vehicle fault diagnosis system verifies a fault code and a first diagnostic vector code through a fault diagnosis requirement table, and verifies first execution information, so as to determine whether the fault code, the first diagnostic vector code and the first execution information are accurate, thereby being able to monitor the process of handling faults in the vehicle control system, thereby improving the test efficiency. When a flaw is detected in the test process, the test can be terminated in time to improve the test efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] Figure 1 It is a schematic diagram of signal flow between a test device and a vehicle control system of the present invention;

[0045] Figure 2 for Figure 1 The signal flow of the vehicle control system is shown in FIG.

[0046] Figure 3 The present invention is a control flow chart of a testing device. DETAILED DESCRIPTION

[0047] This section will describe in detail the specific embodiments of the present invention. The preferred embodiments of the present invention are shown in the accompanying drawings. The purpose of the accompanying drawings is to supplement the description of the text part of the specification with graphics, so that people can intuitively and vividly understand each technical feature and the overall technical solution of the present invention, but it cannot be understood as a limitation on the scope of protection of the present invention.

[0048] In the description of the present invention, it should be understood that descriptions involving orientations, such as up, down, front, back, left, right, etc., and orientations or positional relationships indicated are based on the orientations or positional relationships shown in the accompanying drawings, and are only for the convenience of describing the present invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore should not be understood as a limitation on the present invention.

[0049] In the description of the present invention, if there are words such as "several", it means one or more, "more" means more than two, greater than, less than, exceed, etc. are understood as not including the number, and above, below, within, etc. are understood as including the number.

[0050] In the description of the present invention, unless otherwise clearly defined, terms such as setting, installing, connecting, etc. should be understood in a broad sense, and technicians in the relevant technical field can reasonably determine the specific meanings of the above terms in the present invention based on the specific content of the technical solution.

[0051] join Figure 1-Figure 3The present invention provides a test method for detecting a vehicle fault diagnosis system, which is used to detect whether the vehicle control system can accurately identify faults and handle faults. In order to reduce the test volume, a test method for detecting a vehicle fault diagnosis system includes: a test device in a workshop, which is equivalent to a quality inspection system. The test device has a proofreading table similar to Table 1. The proofreading table in Table 1 is called a fault diagnosis requirement table, so as to calibrate various types of information through the proofreading table, thereby identifying whether various types of information fed back to the test device by the tested vehicle control system are the same or matched with the proofreading table, so as to determine whether the fault identification function and fault handling function of the tested vehicle control system are accurate. Table 1 is a table of test sequences. The data in Table 1 is intuitive, which is conducive to the test device to quickly complete the proofreading work. Among them, the test sequence includes multiple fault numbers (multiple fault numbers include fault 1, fault 2, fault 3...), multiple fault codes (multiple fault codes include P1XXXXXXX, P2XXXXXXX, P1XXXXXXX3...) and multiple diagnostic vector categories (multiple diagnostic vector categories include diagnostic vector code 1, diagnostic vector code 2, diagnostic vector code 3...), and multiple different fault numbers, multiple different fault codes and multiple different diagnostic vector categories are established in a one-to-one correspondence according to a table.

[0052] Among them, the vehicle control system, namely the vehicle controller HCU (Hybrid Control Unit), is the core control component of the hybrid vehicle, responsible for the energy management, torque coordination and distribution, motor battery coordination management, safety monitoring, UDS fault diagnosis, and brake energy recovery of the vehicle. The control strategy of HCU determines the driving performance, power, safety and economy of the vehicle. It analyzes driving demand input signals, such as pedal input and vehicle speed signals, and uses these signals to manage system energy output, torque distribution, motor control, battery pack and traditional power system.

[0053] Among them, fault 1, fault 2, fault 3, etc. can be: sensor fault, IO fault, PWM interface fault, CAN communication fault, LIN communication fault, motor system fault, battery system fault, engine system fault or cooling system fault, etc. Diagnostic vector code 1, diagnostic vector code 2, diagnostic vector code 3, etc. can be: high voltage under-voltage diagnostic vector or request engine shutdown diagnostic vector, etc.

[0054] Table 1 is as follows

[0055]

[0056] Referring to Table 1, the test device is configured with the corresponding Table 1 according to the specified vehicle model, that is, the vehicle control systems of different vehicle models may be different. The test device will pre-set their own calibration tables according to different vehicle control systems (that is, their respective Tables 1 are different). The preset fault codes corresponding to Fault 1, Fault 2... in each calibration table may be different, and the fault handling strategies corresponding to the diagnostic vector code 1, diagnostic vector code 2... in each calibration table may be different (fault handling strategies include, for example, requesting emergency high-voltage power-off, requesting normal high-voltage power-off, requesting engine shutdown or prohibiting engine shutdown, etc.). Simply put, for the vehicle control systems of five different types of vehicles, the workshop will be equipped with five different proofreading tables (i.e., different Tables 1), and in each proofreading table, the preset fault codes corresponding to Fault 1, Fault 2, Fault 3, Fault 4, Fault 5, etc. may be partially the same or may be completely different, and the fault handling strategies corresponding to Diagnostic Vector Code 1, Diagnostic Vector Code 2, Diagnostic Vector Code 3, Diagnostic Vector Code 4, Diagnostic Vector Code 5, Diagnostic Vector Code 6, etc. may be partially the same or may be completely different. Therefore, before the vehicle control system of each type of vehicle is tested, the test device in the workshop will customize the corresponding proofreading table (i.e., Table 1) according to its fault testing process, that is, the test device has preset the correct value in advance, as shown in Table 1. The established accurate preset fault code for fault 1, and the established accurate results of diagnostic vector code 1, diagnostic vector code 2, diagnostic vector code 3, diagnostic vector code 4... are set to 0 (0 represents that there is no diagnostic requirement) or are set to 1 (1 represents that there is a diagnostic requirement); such as the established accurate preset fault code for fault 2 in Table 1, and the established accurate results of diagnostic vector code 1, diagnostic vector code 2, diagnostic vector code 3, diagnostic vector code 4... are set to 0 or are set to 1; such as the established accurate preset fault code for fault 3 in Table 1, and the established accurate results of diagnostic vector code 1, diagnostic vector code 2, diagnostic vector code 3, diagnostic vector code 4... are set to 0 or are set to 1, and so on. Among them, taking the above Table 1 as an example, the preset fault code corresponding to fault 1 is P1XXXXXXX, where X is an unknown number, which can be set by the test device later. Here, the unknown number is temporarily used as an example. The setting of the diagnostic vector code 1 corresponding to P1XXXXXXX is 0 (set to 0 means that there is no need to execute the fault handling strategy of the diagnostic vector code 1), the setting of the diagnostic vector code 2 corresponding to P1XXXXXXX is 1 (set to 1 means that the fault handling strategy of the diagnostic vector code 1 needs to be executed), and the setting of the diagnostic vector code 3 corresponding to P1XXXXXXX is 1 (set to 1 means that the fault handling strategy of the diagnostic vector code 1 needs to be executed)... Use the data in Table 1 as a checklist to determine whether the results fed back by the vehicle control system have passed the test, that is, whether it is qualified. The signal flow is: See Figure 1 and Figure 2When the vehicle control system under test is input with the corresponding preset fault information by the test device, it will generate a fault code and feed the fault code back to the fault code acquisition module of the test device. The fault code acquisition module then transmits the fault code to the data analysis module of the test device. The data analysis module checks the preset fault code in Table 1 with the fault code from the fault code acquisition module to check whether the two are the same or match, that is, to determine whether the fault code from the fault code acquisition module is accurate. And, the vehicle control system under test inputs the fault code into the fault processing requirement module of the vehicle control system under test to generate at least one first diagnostic vector code (such as Figure 2The test device detects one or more of the diagnostic vector codes 1, 2, 3, ... in the diagnostic vector acquisition module, and feeds back the first diagnostic vector code to the diagnostic vector acquisition module of the test device. The diagnostic vector acquisition module of the test device then transmits the first diagnostic vector code to the data analysis module of the test device. The data analysis module of the test device calibrates the diagnostic vector code 1, 2, 3, 4, ... in Table 1 with the first diagnostic vector code from the diagnostic vector acquisition module to check whether the two are identical or match (for example, the diagnostic vector code 1 in Table 1 is set to 0, while the diagnostic vector code 2 and the diagnostic vector code 3 are set to 1, and the first diagnostic vector code is the diagnostic vector code 2 and the diagnostic vector code 3, which means that the two are identical and accurate), that is, to determine whether the first diagnostic vector code from the diagnostic vector acquisition module is accurate. And, the vehicle control system under test inputs the first diagnostic vector code into the fault handling execution module of the vehicle control system under test to generate at least one first execution information, and feeds back the first execution information to the fault handling related data acquisition module of the test device, and the fault handling related data acquisition module of the test device then transmits the first execution information to the data analysis module of the test device, and the data analysis module of the test device checks the first execution information from the fault handling related data acquisition module according to the pre-stored established accurate execution result data to check whether the two are the same or match, that is, to determine whether the first execution information from the fault handling related data acquisition module is accurate. Among them, the first execution information is used to drive the vehicle control system to control one or more execution components to change state. Among them, the action executed by the execution component may be to clear the motor torque, prohibit the air conditioner from working, disconnect the main negative relay and the main positive relay, actively discharge the motor, clear the engine torque or control the engine to stop, etc. It can be understood that a fault code in the vehicle control system under test may correspond to the output of one or more first diagnostic vector codes, and a first diagnostic vector code corresponds to the output of a first execution information. The fault handling strategies corresponding to the first diagnostic vector code include, for example, requesting emergency high-voltage power-off, requesting normal high-voltage power-off, requesting engine shutdown or prohibiting engine shutdown, etc. A first execution information may cause the control system under test to control one or more execution components of the vehicle to change the state in order to complete the fault handling.

[0057] Therefore, the present invention provides a test method for detecting a vehicle fault diagnosis system. In summary, step S100 includes: step S101, step S102, and step S103.

[0058] Step S101: input preset fault information to the vehicle control system to obtain at least one fault code generated by the vehicle control system. Specifically, the test device inputs preset fault information to the vehicle control system to obtain at least one fault code generated by the vehicle control system. The fault code is further input into the fault processing requirement module of the vehicle control system to generate a first diagnostic vector code, and the vehicle control system feeds back the fault code to the fault code acquisition module of the test device, which then inputs the fault code into the data analysis module of the test device.

[0059] Step S102: Check at least one of the fault codes to determine whether the fault code is correct. Specifically, the data analysis module of the test device checks at least one of the fault codes according to Table 1 to determine whether the fault code is correct, that is, whether the fault code is the same as or matches that in Table 1. If the fault code is inaccurate after checking, it means that the test of the fault handling function of the current vehicle control system has failed.

[0060] Step S103: When the fault code is proofread and confirmed to be correct, at least one first diagnostic vector code generated by the vehicle control system according to the fault code is received, and at least one of the first diagnostic vector codes is proofread to determine whether the first diagnostic vector code is correct; wherein, a first diagnostic vector code is used to characterize a fault handling strategy. Specifically, when the fault code is proofread and confirmed to be correct by the data analysis module of the test device, the diagnostic vector acquisition module of the test device receives at least one first diagnostic vector code generated by the vehicle control system according to the fault code, and proofreads at least one of the first diagnostic vector codes according to Table 1 through the data analysis module of the test device to determine whether the first diagnostic vector code is correct, that is, to determine whether the first diagnostic vector code is the same as or matches that in Table 1. If the first diagnostic vector code is inaccurate after proofreading, it means that the test of the fault handling function of the current vehicle control system has failed.

[0061] Step S104: When the first diagnostic vector code is proofread and confirmed to be correct, at least one first execution information generated by the vehicle control system according to at least one of the first diagnostic vector codes is received, and the first execution information is proofread to determine whether the first execution information is correct; wherein, one first execution information is used to drive the vehicle control system to control one or more execution components to change state, so as to complete the current fault processing. Specifically, when the first diagnostic vector code is proofread and confirmed to be correct by the data analysis module of the test device, the fault processing related data acquisition module of the test device receives at least one first execution information generated by the vehicle control system according to at least one of the first diagnostic vector codes, and proofreads at least one first execution information through the pre-stored established accurate execution result data of the data analysis module of the test device to determine whether the first execution information is correct, that is, to determine whether the first execution information is the same as or matches the established accurate execution result data. If the first execution information is inaccurate after proofreading, it means that the test of the fault processing function of the current vehicle control system has failed. If the first execution information is determined to be accurate after proofreading, it means that the test of the fault processing function of the current vehicle control system has passed.

[0062] In this way, by checking the fault code and the first diagnostic vector code through the fault diagnosis requirement table, and checking the first execution information, it is possible to determine whether the fault code, the first diagnostic vector code and the first execution information are accurate, so that the vehicle control system can monitor the process of handling faults, thereby improving the test efficiency. When the test process is detected to have omissions, it can be terminated in time to improve the test efficiency.

[0063] In one implementation, the preset fault information includes a fault signal, and inputting the preset fault information into the vehicle control system to obtain at least one fault code generated by the vehicle control system includes:

[0064] Generate the fault signal according to the test sequence, and input the fault signal into the vehicle control system to obtain at least one fault code generated by the vehicle control system according to the fault signal to simulate the vehicle fault environment. Figure 1 , generate the fault signal according to the test sequence of the fault diagnosis requirement table, and input the fault signal into the vehicle control system, the fault identification module of the vehicle control system simulates the vehicle fault environment according to the fault signal to generate at least one fault code, not only transmit the at least one fault code to the fault processing requirement module of the vehicle control system, but also feed back the at least one fault code to the fault code acquisition module of the test device.

[0065] It can be understood that by performing automatic testing on the test device according to the test sequence, that is, testing one by one according to the fault sequence number, and making the fault signal simulate the vehicle fault environment, rapid testing is achieved, which greatly improves the test efficiency.

[0066] In one embodiment, the testing method further comprises:

[0067] The testing method further includes step S200, which includes step S210 and step S220.

[0068] Step S210: When the first execution information is proofread and confirmed to be correct, a first designated trigger diagnostic vector signal is sequentially input into the vehicle control system under various different operating conditions to obtain a second diagnostic vector code sequentially generated by the vehicle control system under various different operating conditions, and a second diagnostic vector code is proofread to determine whether the second diagnostic vector code is correct; wherein a second diagnostic vector code is used to characterize a fault handling strategy; specifically: when the first execution information is proofread and confirmed to be correct, a first designated trigger diagnostic vector signal is input into the vehicle control system under various different operating conditions using a diagnostic vector injection module to obtain a second diagnostic vector code sequentially generated by the vehicle control system under various different operating conditions (such as Figure 2 The test device receives one of the diagnostic vector codes 1, 2, 3, etc. in the vehicle control system, and proofreads one of the second diagnostic vector codes to determine whether the second diagnostic vector code is correct. The specific process is that the test device inputs a first designated trigger diagnostic vector signal to the vehicle control system through the diagnostic vector injection module. The first designated trigger diagnostic vector signal will prompt the fault processing execution module of the vehicle control system to receive one of the diagnostic vector codes 1, 2, 3, etc., and input the same input first designated trigger diagnostic vector signal under different working conditions, so that the diagnostic vector acquisition module of the test device receives a second diagnostic vector code generated sequentially by the vehicle control system under a variety of different working conditions. Based on the fact that the data analysis module of the test device knows the correct diagnostic vector code (one or more) corresponding to the first designated trigger diagnostic vector signal under different working conditions, the fault processing requirement module of the vehicle control system feeds back the one or more second diagnostic vector codes generated sequentially to the diagnostic vector acquisition module of the test device, and the diagnostic vector acquisition module of the test device transmits the one or more second diagnostic vector codes to the data analysis module of the test device for proofreading, so as to monitor whether the vehicle control system correctly generates the second diagnostic vector code.

[0069] Step S220: When the second diagnostic vector code is proofread and confirmed to be correct, the second execution information generated by the vehicle control system according to the second diagnostic vector code is received, and the second execution information is proofread to determine whether the second execution information is correct; wherein, a second execution information is used to drive the vehicle control system to control an execution component or multiple execution components to change state. The action performed by the execution component may be to clear the motor torque, prohibit the air conditioner from working, disconnect the main negative relay and the main positive relay, actively discharge the motor, clear the engine torque or control the engine to stop, etc. It can be understood that a second diagnostic vector code (the fault handling strategy corresponding to the second diagnostic vector code, for example, requests emergency high voltage power-off, requests normal high voltage power-off, requests engine shutdown or prohibits engine shutdown, etc.) corresponds to the output of a second execution information, and a second execution information may cause the tested control system to control one or more execution components of the vehicle to change state to complete the fault handling.

[0070] Simply analyzing, this step directly triggers the diagnostic vector signal by inputting the first specified trigger diagnostic vector signal to output the specified diagnostic vector code 1, diagnostic vector code 2, diagnostic vector code 3 or diagnostic vector code 4... without triggering the diagnostic vector code through the fault code, that is, this step can directly detect a certain diagnostic vector code.

[0071] In one embodiment, in order to automatically test all diagnostic vector codes, after the first execution information is checked and confirmed to be correct, a first designated trigger diagnostic vector signal is sequentially input to the vehicle control system under a variety of different working conditions; including:

[0072] When the first execution information is checked and confirmed to be correct, the first designated trigger diagnostic vector signal is sequentially input into the vehicle control system under a variety of different operating conditions according to a test sequence.

[0073] Through the test sequence, the same first designated trigger diagnostic vector signal is sequentially input into the vehicle control system under a variety of different working conditions, and through the test sequence, different first designated trigger diagnostic vector signals are sequentially input into the vehicle control system under a variety of different working conditions, so as to measure whether the setting of diagnostic vector code 1, diagnostic vector code 2, diagnostic vector code 3, diagnostic vector code 4...all diagnostic vector codes under different working conditions are consistent with Table 1. Obviously, when all diagnostic vector codes pass the test, it means that the fault identification module, fault handling requirement module, and fault handling execution module of the vehicle control system are all normal. In this way, a small number of tests are equivalent to exhaustively enumerating all test conditions, without exhaustively enumerating all conditions for testing under each fault code, which greatly reduces the test volume.

[0074] It should be noted that the vehicle control system has different fault handling responses under different working conditions, such as the corresponding diagnostic vector code and the first execution information are different, which leads to the vehicle control system controlling different execution components. Therefore, when testing the fault handling function of the vehicle control system, different working conditions need to be set to ensure coverage. In particular, the working condition setting does not need to be exhaustive, but different working conditions can be set for different diagnostic vectors. The selection of the working condition is related to the function related to the diagnostic vector. For example, the high-voltage power-down diagnostic vector is strongly associated with the high-voltage power-up and power-down functions. When setting the working condition, only the three working conditions before high-voltage power-up, during high-voltage power-up, and after high-voltage power-up need to be considered. There is no need to consider other unrelated working conditions such as the accelerator pedal opening and different vehicle speeds. In this way, the test volume is greatly reduced under the premise of meeting the test working conditions. The request engine shutdown diagnostic vector is strongly related to the engine start-stop function. When setting the working condition, only four working conditions need to be considered: before engine start (engine shutdown), during engine start, normal engine operation, and during engine shutdown.

[0075] In one embodiment, the test method further includes step S300. Step S300 includes step S310 and step S320.

[0076] Step S310: When the second execution information is proofread and confirmed to be correct, specifically: when the data analysis module proofreads the second execution information and confirms that it is correct, it means that the fault identification module, fault handling requirement module, and fault handling execution module of the vehicle control system are all normal and have passed the routine test. Next, multiple second designated trigger diagnostic vector signals with conflicting fault handling strategies are input to the vehicle control system, or multiple second designated trigger diagnostic vector signals with preset priority response levels are input to the vehicle control system to obtain at least one third diagnostic vector code generated by the vehicle control system, and proofread at least one of the third diagnostic vector codes to determine whether the third diagnostic vector code is correct; wherein, a third diagnostic vector code is used to characterize a fault handling strategy. Specifically: a plurality of second designated trigger diagnostic vector signals having conflicting fault handling strategies are input into the vehicle control system through the diagnostic vector injection module of the test device, or a plurality of second designated trigger diagnostic vector signals having a preset priority response level are input into the vehicle control system through the diagnostic vector injection module of the test device to obtain at least one third diagnostic vector code (diagnostic vector code 1, diagnostic vector code 2 or diagnostic vector code 3...) generated by the vehicle control system, and at least one of the third diagnostic vector codes is proofread to determine whether the third diagnostic vector code is correct.

[0077] Step S320: After the third diagnostic vector code is proofread and confirmed to be correct, the third execution information generated by the vehicle control system according to at least one of the third diagnostic vector codes is received, and the third execution information is proofread to determine whether the third execution information is correct; wherein, one third execution information is used to drive the vehicle control system to control an execution component or multiple execution components to change state.

[0078] For example, if the two diagnostic vector codes, diagnostic vector code 1 and diagnostic vector code 2, conflict, and when there is a conflict, the data analysis module and the vehicle control system have been preset to only respond to diagnostic vector code 1 and ignore diagnostic vector code 2, which means that the third diagnostic vector code is diagnostic vector code 1, and diagnostic vector code 2 is terminated or shelved. In this way, after the vehicle is actually driven, when multiple faults trigger multiple diagnostic vector codes, diagnostic vector code 1 and diagnostic vector code 2 may be triggered at the same time, so it is necessary to test the conflict between the two diagnostic vector codes to determine whether the vehicle control system passes the test.

[0079] For example, if there is a priority between diagnostic vector code 1 and diagnostic vector code 2, when diagnostic vector code 1 and diagnostic vector code 2 are input into the vehicle control system by the diagnostic vector injection module of the test device for testing, since the data analysis module and the vehicle control system have been preset to only respond to diagnostic vector code 1 and ignore diagnostic vector code 2, it means that the third diagnostic vector code is diagnostic vector code 1, and diagnostic vector code 2 is terminated or shelved. In this way, after the vehicle is actually driven, when multiple faults trigger multiple diagnostic vector codes, diagnostic vector code 1 and diagnostic vector code 2 may be triggered at the same time, so it is necessary to test the priority of the two diagnostic vector codes to determine whether the vehicle control system passes the test.

[0080] In order to enable the vehicle control system to automatically test the diagnostic vector code for processing conflict situations or the diagnostic vector code for processing priority situations, in one embodiment, after the second execution information is checked and confirmed to be correct, a plurality of second designated trigger diagnostic vector signals with functional conflicts are input to the vehicle control system, or a plurality of second designated trigger diagnostic vector signals with preset priority response levels are input to the vehicle control system, including:

[0081] When the second execution information is proofread and confirmed to be correct, a plurality of second designated trigger diagnostic vector signals having conflicting processing strategies are input into the vehicle control system in sequence according to the test sequence, or a plurality of second designated trigger diagnostic vector signals having preset priority response levels are input into the vehicle control system.

[0082] It should be noted that the diagnostic vector code itself also has priority and conflict situations. For example, the high-voltage power-off diagnostic vector code can also be divided into an emergency high-voltage power-off diagnostic vector code and a normal high-voltage power-off diagnostic vector code. When the emergency high-voltage power-off diagnostic vector code is set, the high voltage needs to be immediately turned off, while when the normal high-voltage power-off diagnostic vector code is set, the power-off condition must be met before the high voltage is turned off. Among the above two diagnostic vector codes, the priority of the emergency high-voltage power-off is higher than the priority of the normal high-voltage power-off diagnostic vector code. Therefore, by setting two diagnostic vector codes with different priorities at the same time, the fault handling consequences can be observed by the data analysis module to confirm whether the vehicle control system performs fault handling according to the fault handling strategy of the diagnostic vector code with a higher priority. For another example, the engine shutdown prohibition diagnostic vector code and the engine shutdown request diagnostic vector code are two conflicting diagnostic requirements (the engine shutdown request diagnostic vector code should be executed, and the engine shutdown prohibition diagnostic vector code should not be responded to). By setting the two diagnostic vector codes at the same time and observing the fault handling consequences, it can be confirmed whether the expected result of multiple faults is achieved. This step utilizes the association between diagnostic vector codes and faults, and indirectly tests the fault handling strategy when multiple faults occur by simultaneously setting diagnostic vector codes with different priorities and conflicts. This can simplify the test strip volume (the number of permutations and combinations of multiple fault codes far exceeds the number of diagnostic vector code combinations).

[0083] The present invention also provides a testing device for detecting a vehicle fault diagnosis system, comprising: a fault injection module, a fault code acquisition module, a diagnosis vector acquisition module, a fault processing related data acquisition module and a data analysis module.

[0084] The fault injection module is used to input preset fault information into the vehicle control system.

[0085] The fault code acquisition module is used to obtain at least one fault code generated by the vehicle control system;

[0086] The diagnostic vector acquisition module is used to receive at least one first diagnostic vector code generated by the vehicle control system according to the fault code; wherein a first diagnostic vector code is used to represent a fault handling strategy;

[0087] The fault processing related data acquisition module is used to receive at least one first execution information generated by the vehicle control system according to at least one of the first diagnostic vector codes; wherein one first execution information is used to drive the vehicle control system to control one execution component or multiple execution components to change state;

[0088] The data analysis module is used to proofread at least one of the fault codes to determine whether the fault code is correct; and to proofread at least one of the first diagnostic vector codes to determine whether the first diagnostic vector code is correct; and to proofread the first execution information to determine whether the first execution information is correct.

[0089] The use scheme of the testing device for detecting a vehicle fault diagnosis system of the present invention can be carried out according to the testing method for detecting a vehicle fault diagnosis system, and will not be expanded here to avoid redundancy.

[0090] In one implementation, the testing device further includes: a vehicle failure environment simulation module.

[0091] The vehicle fault environment simulation module is used to simulate the vehicle fault environment according to the fault signal input by the fault injection module, so as to input preset fault information into the vehicle control system, thereby avoiding the need to actually create the corresponding fault on the car, which not only saves costs but also improves test efficiency.

[0092] In one implementation, the testing device further includes: a diagnostic vector injection module.

[0093] The diagnostic vector injection module is used to sequentially input a first designated trigger diagnostic vector signal to the vehicle control system under a plurality of different operating conditions;

[0094] The diagnostic vector acquisition module is also used to obtain a second diagnostic vector code sequentially generated by the vehicle control system under a plurality of different working conditions; wherein a second diagnostic vector code is used to represent a fault handling strategy;

[0095] The fault processing related data acquisition module is also used to receive second execution information generated by the vehicle control system according to one of the second diagnostic vector codes; wherein one of the second execution information is used to drive the vehicle control system to control one or more execution components to change state;

[0096] The data analysis module is also used to proofread a second diagnostic vector code to determine whether the second diagnostic vector code is correct; and is used to proofread the second execution information to determine whether the second execution information is correct.

[0097] The test device inputs a first designated trigger diagnostic vector signal to the vehicle control system through a diagnostic vector injection module. The first designated trigger diagnostic vector signal will prompt the fault processing execution module of the vehicle control system to receive one of the diagnostic vector code 1, diagnostic vector code 2, diagnostic vector code 3, etc., and input the same input first designated trigger diagnostic vector signal under different working conditions, so that the diagnostic vector acquisition module of the test device receives a second diagnostic vector code sequentially generated by the vehicle control system under a variety of different working conditions. Based on the data analysis module of the test device, the correct diagnostic vector code (one or more) corresponding to the first designated trigger diagnostic vector signal under different working conditions is known. Therefore, after the fault processing requirement module of the vehicle control system feeds back the one or more second diagnostic vector codes generated sequentially to the diagnostic vector acquisition module of the test device, the diagnostic vector acquisition module of the test device transmits the one or more second diagnostic vector codes to the data analysis module of the test device for proofreading, so as to monitor whether the vehicle control system correctly generates the second diagnostic vector code.

[0098] In one embodiment, the diagnostic vector injection module is further used to input a plurality of second designated trigger diagnostic vector signals having conflicting fault handling strategies to the vehicle control system, or to input a plurality of second designated trigger diagnostic vector signals having a preset priority response level to the vehicle control system;

[0099] The diagnostic vector acquisition module is further used to acquire at least one third diagnostic vector code generated by the vehicle control system; wherein a third diagnostic vector code is used to represent a fault handling strategy;

[0100] The fault processing related data acquisition module is also used to receive third execution information generated by the vehicle control system according to at least one of the third diagnostic vector codes; wherein one third execution information is used to drive the vehicle control system to control one execution component or multiple execution components to change state;

[0101] The data analysis module is further used to proofread at least one of the third diagnostic vector codes to determine whether the third diagnostic vector code is correct; and to proofread the third execution information to determine whether the third execution information is correct.

[0102] A plurality of second designated trigger diagnostic vector signals having conflicting fault handling strategies are input into the vehicle control system through the diagnostic vector injection module of the test device, or a plurality of second designated trigger diagnostic vector signals having a preset priority response level are input into the vehicle control system through the diagnostic vector injection module of the test device to obtain at least one third diagnostic vector code (diagnostic vector code 1, diagnostic vector code 2 or diagnostic vector code 3, etc.) generated by the vehicle control system, and at least one of the third diagnostic vector codes is proofread to determine whether the third diagnostic vector code is correct.

[0103] In one embodiment, the test device further includes a test sequence generation module, the test sequence generation module is used to generate a test sequence, the fault injection module, the fault code acquisition module, the diagnostic vector acquisition module, and the fault processing related data acquisition module are all connected to the test sequence generation module to respectively obtain the test sequence; wherein, the test sequence includes multiple fault numbers, multiple fault codes, and multiple diagnostic vector categories, and multiple different fault numbers, multiple different fault codes, and multiple different diagnostic vector categories are established in a one-to-one correspondence according to a table (i.e., Table 1). By testing the test sequence in sequence, the test efficiency is improved.

[0104] The present invention also provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the test method for detecting a vehicle fault diagnosis system is implemented.

[0105] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "illustrative embodiments", "examples", "specific examples", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.

[0106] Although the embodiments of the present invention have been shown and described, a person skilled in the art may make various changes, modifications, substitutions and variations to these embodiments without departing from the principles and spirit of the present invention. These changes, modifications, equivalent variations or substitutions are all included in the scope defined by the claims of this application. The scope of the present invention is defined by the claims and their equivalents.

Claims

1. A test method for detecting a vehicle fault diagnosis system, characterized in that: include: Inputting preset fault information into a vehicle control system to obtain at least one fault code generated by the vehicle control system; Verifying at least one of the fault codes to determine whether the fault code is correct; When the fault code is checked and confirmed to be correct, receiving at least one first diagnostic vector code generated by the vehicle control system according to the fault code, and checking at least one of the first diagnostic vector codes to determine whether the first diagnostic vector code is correct; wherein a first diagnostic vector code is used to represent a fault handling strategy; After the first diagnostic vector code is proofread and confirmed to be correct, at least one first execution information generated by the vehicle control system based on at least one of the first diagnostic vector codes is received, and the first execution information is proofread to determine whether the first execution information is correct; wherein, one first execution information is used to drive the vehicle control system to control an execution component or multiple execution components to change state.

2. The testing method for detecting a vehicle fault diagnosis system according to claim 1, characterized in that: The preset fault information includes a fault signal, and the inputting the preset fault information into the vehicle control system to obtain at least one fault code generated by the vehicle control system includes: The fault signal is generated according to a test sequence, and the fault signal is input into the vehicle control system to obtain at least one fault code generated by the vehicle control system according to the fault signal to simulate a vehicle fault environment; wherein the test sequence includes multiple fault numbers, multiple fault codes and multiple diagnostic vector categories, and multiple different fault numbers, multiple different fault codes and multiple different diagnostic vector categories are established in a one-to-one correspondence according to a table.

3. The testing method for detecting a vehicle fault diagnosis system according to claim 2, characterized in that: The test method also includes: When the first execution information is checked and confirmed to be correct, a first designated trigger diagnostic vector signal is sequentially input to the vehicle control system under a plurality of different working conditions to obtain a second diagnostic vector code sequentially generated by the vehicle control system under a plurality of different working conditions, and a second diagnostic vector code is checked to determine whether the second diagnostic vector code is correct; wherein a second diagnostic vector code is used to represent a fault handling strategy; After the second diagnostic vector code is proofread and confirmed to be correct, the vehicle control system receives second execution information generated based on the second diagnostic vector code, and proofreads the second execution information to determine whether the second execution information is correct; wherein, a second execution information is used to drive the vehicle control system to control an execution component or multiple execution components to change state.

4. The testing method for detecting a vehicle fault diagnosis system according to claim 3, characterized in that: After the first execution information is checked and confirmed to be correct, a first designated trigger diagnostic vector signal is sequentially input to the vehicle control system under a plurality of different working conditions; including: When the first execution information is checked and confirmed to be correct, the first designated trigger diagnostic vector signal is sequentially input into the vehicle control system under a variety of different operating conditions according to a test sequence.

5. The testing method for detecting a vehicle fault diagnosis system according to claim 3, characterized in that: The test method also includes: When the second execution information is checked and confirmed to be correct, a plurality of second designated trigger diagnostic vector signals having conflicting fault handling strategies are input to the vehicle control system, or a plurality of second designated trigger diagnostic vector signals having a preset priority response level are input to the vehicle control system to obtain at least one third diagnostic vector code generated by the vehicle control system, and check at least one of the third diagnostic vector codes to determine whether the third diagnostic vector code is correct; wherein a third diagnostic vector code is used to represent a fault handling strategy; After the third diagnostic vector code is proofread and confirmed to be correct, the vehicle control system receives third execution information generated based on at least one of the third diagnostic vector codes, and proofreads the third execution information to determine whether the third execution information is correct; wherein, one third execution information is used to drive the vehicle control system to control an execution component or multiple execution components to change state.

6. The testing method for detecting a vehicle fault diagnosis system according to claim 5, characterized in that: After the second execution information is checked and confirmed to be correct, a plurality of second designated trigger diagnostic vector signals having functional conflicts are input to the vehicle control system, or a plurality of second designated trigger diagnostic vector signals having preset priority response levels are input to the vehicle control system, including: When the second execution information is proofread and confirmed to be correct, a plurality of second designated trigger diagnostic vector signals having conflicting processing strategies are input into the vehicle control system in sequence according to the test sequence, or a plurality of second designated trigger diagnostic vector signals having preset priority response levels are input into the vehicle control system.

7. A test device for detecting a vehicle fault diagnosis system, characterized in that: include: A fault injection module, used to input preset fault information into the vehicle control system; A fault code acquisition module, used to acquire at least one fault code generated by the vehicle control system; A diagnostic vector acquisition module, used to receive at least one first diagnostic vector code generated by the vehicle control system according to the fault code; wherein a first diagnostic vector code is used to represent a fault handling strategy; A fault processing related data acquisition module, used for receiving at least one first execution information generated by the vehicle control system according to at least one of the first diagnostic vector codes; wherein one first execution information is used to drive the vehicle control system to control one execution component or multiple execution components to change state; A data analysis module is used to proofread at least one of the fault codes to determine whether the fault code is correct; and to proofread at least one of the first diagnostic vector codes to determine whether the first diagnostic vector code is correct; and to proofread the first execution information to determine whether the first execution information is correct.

8. The testing device for testing a vehicle fault diagnosis system according to claim 7, characterized in that: The testing device also includes: The vehicle fault environment simulation module is used to simulate the vehicle fault environment according to the fault signal input by the fault injection module to input preset fault information into the vehicle control system.

9. The testing device for testing a vehicle fault diagnosis system according to claim 7, characterized in that: The testing device also includes: A diagnostic vector injection module, used to sequentially input a first designated trigger diagnostic vector signal to a vehicle control system under a plurality of different operating conditions; The diagnostic vector acquisition module is also used to obtain a second diagnostic vector code sequentially generated by the vehicle control system under a plurality of different working conditions; wherein a second diagnostic vector code is used to represent a fault handling strategy; The fault processing related data acquisition module is also used to receive second execution information generated by the vehicle control system according to the second diagnostic vector code; wherein the second execution information is used to drive the vehicle control system to control an execution component or multiple execution components to change state; The data analysis module is also used to proofread a second diagnostic vector code to determine whether the second diagnostic vector code is correct; and is used to proofread the second execution information to determine whether the second execution information is correct.

10. The testing device for testing a vehicle fault diagnosis system according to claim 9, characterized in that: The diagnostic vector injection module is further used to input a plurality of second designated trigger diagnostic vector signals having conflicting fault handling strategies into the vehicle control system, or to input a plurality of second designated trigger diagnostic vector signals having a preset priority response level into the vehicle control system; The diagnostic vector acquisition module is further used to acquire at least one third diagnostic vector code generated by the vehicle control system; wherein a third diagnostic vector code is used to represent a fault handling strategy; The fault processing related data acquisition module is also used to receive third execution information generated by the vehicle control system according to at least one of the third diagnostic vector codes; wherein one third execution information is used to drive the vehicle control system to control one execution component or multiple execution components to change state; The data analysis module is further used to proofread at least one of the third diagnostic vector codes to determine whether the third diagnostic vector code is correct; and to proofread the third execution information to determine whether the third execution information is correct.

11. The testing device for testing a vehicle fault diagnosis system according to claim 7, characterized in that: The testing device also includes a test sequence generation module, which is used to generate a test sequence. The fault injection module, the fault code acquisition module, the diagnostic vector acquisition module, and the fault processing related data acquisition module are all connected to the test sequence generation module to respectively obtain the test sequence; wherein, the test sequence includes multiple fault numbers, multiple fault codes and multiple diagnostic vector categories, and multiple different fault numbers, multiple different fault codes and multiple different diagnostic vector categories are established in a one-to-one correspondence according to a table.

12. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the test method for detecting a vehicle fault diagnosis system according to any one of claims 1 to 6 is implemented.

Citation Information

Patent Citations

  • Whole vehicle fault diagnosis test system

    CN112859817A

  • Vehicle controller test system and method, electronic equipment and readable storage medium

    CN114690741A

  • Vehicle fault diagnosis test method and device, electronic equipment and storage medium

    CN116679683A

  • Vehicle control unit diagnosis test method, device and equipment and storage medium

    CN117950391A

  • Vehicle fault diagnosis method, controller and storage medium

    CN118012008A

Cited By

  • Vehicle maintenance method and system, computer equipment and computer readable storage medium

    CN121431100A