Vehicle fault identification function test method and device, electronic equipment and storage medium
By generating fault identification information tables and test sequences, the vehicle fault identification function test is automated, and the problem of low efficiency of fault identification function testing of hybrid vehicles is solved, and an efficient and intelligent test process is realized, which reduces manual participation and improves testing efficiency and accuracy.
Patent Information
- Application Number
- CN202411248004.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-06
- Publication Date
- 2024-12-06
- Estimated Expiration
- 2044-09-06
AI Technical Summary
In the prior art, the fault identification function test of hybrid vehicles is inefficient and dependent on labor, which can easily lead to false alarms or missed faults, affecting the safety and reliability of the vehicle.
By generating a fault identification information table and test sequence, the vehicle fault identification function test process is automated, the vehicle controller to be tested is used to test it, and the fault identification function test report is generated, which reduces manual participation steps and improves testing efficiency.
It realizes the automation and intelligence of vehicle fault identification function testing, reduces labor costs, improves testing efficiency, reduces human errors, and ensures the rigor and smoothness of the test process.
Smart Images

Figure CN119087983A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of vehicle testing technology, and in particular to a vehicle fault identification function testing method and device, electronic equipment and storage medium. Background Art
[0002] In the relevant technical field, hybrid vehicles usually have a fault identification function. The safety and reliability of hybrid vehicles can be ensured by diagnosing faults through the vehicle controller. However, once the fault identification function fails, it will lead to false alarms or missed faults, which may easily lead to unexpected fault handling, resulting in the inability to drive the vehicle normally, or failure to take timely measures to handle the fault, resulting in safety accidents. Therefore, it is particularly important to test the fault identification function of the vehicle. Summary of the invention
[0003] The main purpose of the embodiments of the present application is to propose a vehicle fault identification function testing method and device, electronic equipment and storage medium, which can automate the test process of the vehicle fault identification function, save labor costs while maintaining high efficiency.
[0004] To achieve the above object, one aspect of an embodiment of the present application provides a vehicle fault identification function testing method, the method comprising: generating a fault identification information table, wherein the fault identification information table includes a plurality of fault categories; Generate a test sequence corresponding to each fault category according to the fault identification information table; A test program is run based on the test sequence to test the vehicle controller to be tested, and a fault identification function test report is generated.
[0005] In some embodiments, the test sequence includes a plurality of test steps; The step of running a test program based on the test sequence to test the vehicle controller to be tested and generating a fault identification function test report includes: Execute each of the test steps according to a preset order to run the test program and obtain test result parameters; Comparing the test result parameters with the expected result parameters to determine the test result; The fault identification function test report is generated based on the test result.
[0006] In some embodiments, executing each of the test steps according to a preset order to run the test program and obtain test result parameters includes: Calling fault identification requirement information from the fault identification information table, wherein the fault identification requirement information includes fault injection conditions, fault recovery conditions, and fault parameters; When it is detected that the current state of the test program meets the fault injection condition, a fault injection process is performed based on the fault parameter to construct a simulated fault scenario; Obtaining feedback information of the vehicle controller to be tested when operating in the simulated fault scenario; When it is detected that the current state of the test program meets the fault recovery condition, the operation of the vehicle controller to be tested in the simulated fault scenario is stopped, and the test result parameter is generated based on the feedback information.
[0007] In some embodiments, the fault parameters include a sensor unit fault value, a battery management unit fault value, a controller unit fault value, and a communication unit fault value; The vehicle controller to be tested includes a plurality of control pins; When it is detected that the current state of the test program meets the fault injection condition, a fault injection process is performed based on the fault parameter to construct a simulated fault scenario, including: When it is detected that the current state of the test program meets the fault injection condition, the sensor unit fault value, the battery management unit fault value, the controller unit fault value and the communication unit fault value are respectively input into the target control pins of the vehicle controller to be tested to control the vehicle controller to be tested to be in a state of processing the fault signal and running in the simulated fault scenario.
[0008] In some embodiments, comparing the test result parameter with the expected result parameter to determine the test result includes: When the fault diagnosis function of the vehicle controller to be tested is in an enabled state, acquiring fault diagnosis information of the vehicle controller to be tested and using it as the test result parameter; The fault diagnosis information is compared with expected fault diagnosis information as the expected result parameter to determine a first test result.
[0009] In some embodiments, comparing the test result parameter with the expected result parameter to determine the test result includes: When the cooling system of the vehicle is controlled by the vehicle controller to be tested, an actual state flag value of the cooling system is obtained and used as the test result parameter; The actual state flag value of the cooling system is compared with the expected state flag value as the expected result parameter to determine a second test result.
[0010] In some embodiments, comparing the test result parameter with the expected result parameter to determine the test result includes: When the fault trigger flag information fed back by the controller of the vehicle to be tested is obtained, an actual fault injection threshold is obtained; Comparing the actual fault injection threshold with a preset threshold to determine a third test result; When the fault confirmation flag information fed back by the vehicle controller to be tested is obtained, if the fault code fed back by the vehicle controller to be tested is detected, it is determined that the fault code storage function of the vehicle controller to be tested is in a qualified state; When the fault code is obtained, the test time value is compared with the preset time value to determine a fourth test result, wherein the test time value is the difference between the time point when the fault trigger flag information is obtained and the time point when the fault confirmation flag information is obtained.
[0011] To achieve the above object, another aspect of the embodiment of the present application provides a vehicle fault identification function testing device, the device comprising: A first generating module, configured to generate a fault identification information table, wherein the fault identification information table includes a plurality of fault categories; A second generating module, configured to generate a test sequence corresponding to each of the fault categories according to the fault identification information table; The test module is used to run a test program based on the test sequence to test the vehicle controller to be tested and generate a fault identification function test report.
[0012] To achieve the above-mentioned purpose, another aspect of an embodiment of the present application provides an electronic device, the electronic device comprising a memory and a processor, the memory storing a computer program, and the processor implementing the above-mentioned method when executing the computer program.
[0013] To achieve the above objective, another aspect of an embodiment of the present application 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 method described above is implemented.
[0014] The embodiments of the present application include at least the following beneficial effects: The present application provides a vehicle fault identification function testing method and device, electronic device and storage medium. First, the present solution records abstract fault identification requirements in the form of specific numbers, texts and other requirement information by generating a fault identification information table, which is conducive to the implementation of digital and automated testing processes. Secondly, by generating a test sequence and defining the logic and sequence of the test process, it is conducive to improving the rigor and fluency of the test procedure. Finally, through the test procedure, the vehicle controller to be tested is tested, which realizes the intelligence and automation of the test process, reduces the steps of manual participation in the entire vehicle controller testing process, avoids human errors in tedious and complicated testing processes, and is conducive to reducing labor costs while improving the efficiency of testing the vehicle controller to be tested. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] Figure 1 is a flow chart of a vehicle fault identification function testing method provided by an embodiment of the present application; Figure 2 yes Figure 1 Flow chart of step S103 in FIG. Figure 3 yes Figure 2 Flow chart of step S201 in FIG. Figure 4 It is a schematic diagram of a hybrid vehicle control system HCU in an application scenario of a vehicle fault identification function test method; Figure 5 It is a structural schematic diagram of a vehicle fault identification function testing device provided in an embodiment of the present application; Figure 6 It is a schematic diagram of the hardware structure of the electronic device provided in the embodiment of the present application. DETAILED DESCRIPTION
[0016] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application is further described in detail below in conjunction with the accompanying drawings and examples. It should be understood that the specific embodiments described herein are only used to explain the present application and are not intended to limit the present application. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the embodiments of the present application. They are only examples of devices and methods consistent with some aspects of the embodiments of the present application as detailed in the attached claims.
[0017] It is understood that the terms "first", "second", etc. used in this application can be used to describe various concepts in this article, but unless otherwise specified, these concepts are not limited by these terms. These terms are only used to distinguish one concept from another concept. For example, without departing from the scope of the embodiment of the present application, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the words "if" and "if" as used herein can be interpreted as "at the time of" or "when" or "in response to determination".
[0018] The terms "at least one", "multiple", "each", "any", etc. used in this application, at least one includes one, two or more, multiple includes two or more, each refers to each of the corresponding multiple, and any refers to any one of the multiple.
[0019] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used herein are only for the purpose of describing the embodiments of this application and are not intended to limit this application.
[0020] It is understandable that vehicle controller fault diagnosis is an important guarantee for the safety and reliability of hybrid vehicles, but if the fault identification function fails, it will lead to false alarms or missed faults, which will either cause unexpected fault handling and make the vehicle unable to drive normally, or cause safety accidents if the fault handling measures are not taken in time. Therefore, the fault identification function needs to be fully tested in the development stage, so it is particularly important to develop a complete hybrid vehicle fault identification method and device.
[0021] In terms of fault identification, fault confirmation, fault recovery and other aspects, the traditional vehicle fault identification function testing method not only relies on the ability of the tester, but also has low testing efficiency. In addition, the existing testing methods either focus on the development of the fault identification function without involving automatic testing, or focus on the testing of the controller diagnostic service and fault handling function without mentioning the fault identification test. In order to meet the demand for testing the fault identification function, the present application provides the following embodiments, which can automate the test process of the vehicle fault identification function, save labor costs and maintain high efficiency.
[0022] Please refer to Figure 1 , Figure 1 is a flow chart of a vehicle fault identification function testing method provided in an embodiment of the present application, Figure 1 The method may include but is not limited to steps S101 to S103.
[0023] S101. Generate a fault identification information table, where the fault identification information table includes multiple fault categories.
[0024] S102: Generate a test sequence corresponding to each fault category according to the fault identification information table.
[0025] S103: Run a test program based on the test sequence to test the vehicle controller to be tested, and generate a fault identification function test report.
[0026] In this embodiment, firstly, this scheme records the abstract fault identification requirements in the form of specific numbers, texts and other requirement information by generating a fault identification information table, which is conducive to the implementation of digital and automated testing processes; secondly, by generating a test sequence and defining the logic and sequence of the test process, it is conducive to improving the rigor and fluency of the test procedure; finally, through the test procedure, the vehicle controller to be tested is tested, thereby realizing the intelligent and automated testing process, reducing the steps of manual participation in the entire vehicle controller testing process, avoiding human errors in tedious and complicated testing processes, and helping to reduce labor costs while improving the efficiency of testing the vehicle controller to be tested.
[0027] In step S101 of some embodiments, the fault identification requirements are described in the form of a table, mainly including factors such as the prerequisites for fault identification, fault judgment threshold, fault confirmation time, prerequisites for fault recovery, fault recovery judgment threshold, and fault recovery time. For example, in a specific embodiment, the fault identification information table is shown in Table 1.
[0028] Table 1-Fault identification information table
[0029] In step S102 of some embodiments, the test sequence mainly includes setting the prerequisites for fault identification, injecting faults, setting the prerequisites for fault recovery, and clearing faults. For example, in a specific embodiment, when testing whether the fault identification function of the vehicle can successfully detect fault Error1, the fault identification information table contains the fault code, fault identification prerequisites, fault judgment threshold, fault confirmation time, fault recovery prerequisites, fault recovery judgment threshold, and fault recovery time related to fault Error1, and a test sequence is generated based on this. The test sequence includes multiple test steps, and the execution order of each test step is set. Through the test sequence, it can be ensured that the test is performed according to the established logic and order.
[0030] In step S103 of some embodiments, a fault identification function test is performed according to a test sequence, including fault identification, fault confirmation, fault recovery, fault code storage, etc., and the test results are analyzed to determine whether the fault identification function of the vehicle passes the test. In some embodiments, when the fault identification test is performed according to the test sequence, the fault identification test includes multiple steps, and each step in the fault identification test is completed according to the step execution order preset in the test sequence.
[0031] Figure 2 yes Figure 1 Flowchart of step S103 in .
[0032] In some embodiments, step S103 includes: S201. Execute each test step according to a preset sequence to run the test program and obtain test result parameters.
[0033] S202: Compare the test result parameters with the expected result parameters to determine the test result.
[0034] S203: Generate a fault identification function test report based on the test results.
[0035] In the embodiment, a test report is generated to visualize the test results, so that the user can obtain the test result information, and the test result parameters are compared with the expected result parameters to determine the test results, so that the user can analyze the test results.
[0036] Figure 3 yes Figure 2 Flowchart of step S201 in .
[0037] In some embodiments, step S201 includes: S301. Call fault identification requirement information from a fault identification information table, where the fault identification requirement information includes fault injection conditions, fault recovery conditions, and fault parameters.
[0038] S302: When it is detected that the current state of the test program meets the fault injection condition, a fault injection process is performed based on the fault parameters to construct a simulated fault scenario.
[0039] S303: Obtain feedback information when the controller of the vehicle to be tested operates in a simulated fault scenario.
[0040] S304: When it is detected that the current state of the test program meets the fault recovery condition, the operation of the vehicle controller to be tested in the simulated fault scenario is stopped, and a test result parameter is generated based on the feedback information.
[0041] In some embodiments, the fault parameters include a sensor unit fault value, a battery management unit fault value, a controller unit fault value, and a communication unit fault value; and the vehicle controller to be tested includes a plurality of control pins.
[0042] In some embodiments, step S302 includes: When it is detected that the current state of the test program meets the fault injection conditions, the sensor unit fault value, battery management unit fault value, controller unit fault value and communication unit fault value are respectively input into the target control pins of the vehicle controller to be tested to control the vehicle controller to be tested to be in a state of processing the fault signal and running in a simulated fault scenario.
[0043] In step S302 of some embodiments, when injecting a fault, the related fault is not directly created, but a simulated fault scenario is constructed by changing the voltage of the input / output pin of the vehicle controller HCU, changing the state of the communication message of the MCU (micro control unit) / BMS (battery management system) / EMS (energy management system) in the vehicle system, changing the state of the fault signal received by the vehicle controller HCU, changing the state of the communication message of the PTC (heater switch) / charging indicator light in the vehicle system, changing the actual power supply environment of the vehicle controller HCU, etc., so as to further test the fault judgment threshold by simulating the real fault situation.
[0044] This embodiment tests the vehicle controller in the simulated fault scenario by simulating the fault scenario. Compared with the method of manufacturing faults for the vehicle controller to identify, this embodiment improves safety and improves test efficiency. The sensor unit fault value, battery management unit fault value, controller unit fault value and communication unit fault value are respectively input to the target control pin of the vehicle controller to be tested to control the vehicle controller to be tested in a state of processing the fault signal, which can restore the fault scenario to the greatest extent and ensure the high efficiency of the test. At the same time, the all-round fault identification ability of the vehicle controller is tested to ensure the effectiveness of the test.
[0045] In some embodiments, step S202 includes: When the fault diagnosis function of the vehicle controller to be tested is enabled, fault diagnosis information of the vehicle controller to be tested is obtained and used as the test result parameter, and the fault diagnosis information is compared with expected fault diagnosis information as the expected result parameter to determine a first test result.
[0046] In some embodiments, step S202 includes: When the cooling system of the vehicle is controlled by the vehicle controller to be tested, the actual state flag value of the cooling system is obtained and used as the test result parameter, and the actual state flag value of the cooling system is compared with the expected state flag value as the expected result parameter to determine a second test result.
[0047] In some embodiments, step S202 includes: When the fault trigger flag information fed back by the controller of the vehicle to be tested is obtained, the actual fault injection threshold is obtained, and the actual fault injection threshold is compared with the preset threshold to determine the third test result.
[0048] When the fault confirmation flag information fed back by the vehicle controller to be tested is obtained, if the fault code fed back by the vehicle controller to be tested is detected, it is determined that the fault code storage function of the vehicle controller to be tested is in a qualified state; if the fault code fed back by the vehicle controller to be tested is not detected, it is determined that the fault code storage function of the vehicle controller to be tested is in an unqualified state.
[0049] When a fault code is obtained, the test time value is compared with the preset time value to determine a fourth test result, wherein the test time value is the difference between the time point when the fault trigger flag information is obtained and the time point when the fault confirmation flag information is obtained.
[0050] It can be understood that when it is in the fault trigger flag position, if the actual fault injection threshold is consistent with the preset threshold, it means that the fault judgment threshold test is passed, and the third test result is output; when it is in the fault confirmation flag position, if the fault code can be read immediately, it means that the fault code storage function test is passed; when the fault code is read, if the time difference between the fault trigger flag and the fault confirmation flag of the fault is consistent with the expected time of fault confirmation, it means that the fault confirmation time test is passed, and the fourth test result is output.
[0051] It can be understood that this embodiment tests the fault identification function of the vehicle controller comprehensively by testing the fault identification, fault confirmation, fault recovery, fault code storage and other functions of the vehicle controller.
[0052] The present application also provides a specific implementation example of the application of a vehicle fault identification function testing method in a specific scenario. In this embodiment, although the object of the vehicle fault identification function testing method is the hybrid vehicle control system HCU, the automatic testing method and device are also applicable to other vehicle controllers, and they can be adapted by simply optimizing the fault identification requirement table and the test environment model according to actual conditions.
[0053] Figure 4The present invention is a schematic diagram of a hybrid vehicle control system HCU in an application scenario of a vehicle fault identification function test method.
[0054] The HCU of the hybrid vehicle control system is mainly responsible for identifying the driver's operation (accelerator pedal, brake pedal, gear information), calculating the driver's required torque, receiving relevant component information and fault information sent by the engine, drive motor, generator, battery and other controllers through CAN communication, sending control instructions to the relevant controllers, coordinating and controlling all components to operate in an orderly manner, realizing functions such as hybrid drive and brake energy recovery, and ensuring that the vehicle operates safely and reliably according to the driver's needs in the event of a fault. HCU can also control the motor water pump, battery water pump, heater water pump and water valve to ensure the normal operation of the vehicle cooling system, and when the motor water pump, battery water pump and heater water pump fail, they will be fed back to HCU by pulling down the PWM control pin, and HCU can judge the water pump failure through the control pin. Therefore, the fault identification function of HCU mainly includes sensor fault identification, IO control fault identification, CAN communication fault identification, LIN communication fault identification, assembly fault identification and self-fault identification.
[0055] The fault identification function of the vehicle control system HCU is tested through the vehicle fault identification function test method. First, the fault identification requirements are described in the form of a table, mainly including the prerequisites for fault identification, fault judgment threshold, fault confirmation time, prerequisites for fault recovery, fault recovery judgment threshold, fault recovery time and other factors, and the test sequence is automatically generated according to the fault identification requirement table, and the order of test execution is defined to ensure that the test is carried out according to the established logic and sequence; secondly, according to the test sequence, diagnostic service tests such as establishing communication, reading HCU controller information, writing controller-related information, reading fault information, and stopping communication are carried out in sequence to determine whether the test passes by collecting the diagnostic information fed back by the HCU; then, the control function of the HCU components is tested, mainly including sending a request to the HCU through the 2F service, the HCU responds to the request and controls the water pump, fan, water valve and charging indicator light to the expected state, and confirms the actual state of the HCU control-related components through the 22 service to determine whether the test passes. Finally, the fault injection module injects sensor faults, IO faults, PWM interface faults, CAN communication and LIN communication faults in turn, and the fault information is read through service 19 and cleared through service 14 to determine whether the test passes. This test method can comprehensively test the fault identification functions of the HCU, such as diagnostic services, fault identification offline process component control, fault identification, fault code storage, and fault code clearing, and effectively ensure the correctness of the HCU fault identification function.
[0056] See also Figure 5The embodiment of the present application also provides a vehicle fault identification function test device, which can implement the above-mentioned vehicle fault identification function test method, and the device includes: The first generating module 401 is used to generate a fault identification information table, wherein the fault identification information table includes multiple fault categories.
[0057] The second generating module 402 is used to generate a test sequence corresponding to each fault category.
[0058] The test module 403 is used to run the test program based on the test sequence to test the vehicle controller to be tested and generate a fault identification function test report.
[0059] It can be understood that the contents of the above method embodiments are all applicable to the present device embodiments, the functions specifically implemented by the present device embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.
[0060] The embodiment of the present application also provides an electronic device, the electronic device includes a memory and a processor, the memory stores a computer program, and the processor implements the above-mentioned vehicle fault identification function test method when executing the computer program. The electronic device can be any intelligent terminal including a tablet computer, a vehicle-mounted computer, etc.
[0061] It can be understood that the contents of the above method embodiments are all applicable to the present device embodiments, the functions specifically implemented by the present device embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.
[0062] See also Figure 6 , Figure 6 The hardware structure of an electronic device of another embodiment is illustrated, and the electronic device includes: The processor 501 may be implemented by a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present application; The memory 502 can be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 502 can store an operating system and other application programs. When the technical solution provided in the embodiment of this specification is implemented by software or firmware, the relevant program code is stored in the memory 502, and the processor 501 calls and executes the vehicle fault identification function test method of the embodiment of this application; Input / output interface 503, used to implement information input and output; Communication interface 504, used to realize communication interaction between the device and other devices, which can be realized through wired mode (such as USB, network cable, etc.) or wireless mode (such as mobile network, WIFI, Bluetooth, etc.); A bus 505 that transmits information between various components of the device (e.g., the processor 501, the memory 502, the input / output interface 503, and the communication interface 504); The processor 501 , the memory 502 , the input / output interface 503 and the communication interface 504 are connected to each other in communication within the device via the bus 505 .
[0063] An embodiment of the present application also provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the above-mentioned vehicle fault identification function testing method is implemented.
[0064] It can be understood that the contents of the above method embodiments are all applicable to the present storage medium embodiments, the functions specifically implemented by the present storage medium embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.
[0065] The memory, as a non-transient computer-readable storage medium, can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory may optionally include a memory remotely disposed relative to the processor, and these remote memories may be connected to the processor via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.
[0066] The vehicle fault identification function test method, vehicle fault identification function test device, electronic device and storage medium provided in the embodiments of the present application, firstly, this scheme records the abstract fault identification requirements in the form of specific numbers, texts and other requirement information by generating a fault identification information table, which is conducive to the implementation of digital and automated testing processes; secondly, by generating a test sequence and defining the logic and sequence of the test process, it is conducive to improving the rigor and fluency of the test procedure; finally, through the test procedure, the vehicle controller to be tested is tested, which realizes the intelligence and automation of the test process, reduces the steps of manual participation in the entire vehicle controller testing process, avoids human errors in tedious and complicated testing processes, and is conducive to reducing labor costs while improving the efficiency of testing the vehicle controller to be tested.
[0067] The embodiments described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Those skilled in the art will appreciate that with the evolution of technology and the emergence of new application scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.
[0068] Those skilled in the art will appreciate that the technical solutions shown in the figures do not constitute a limitation on the embodiments of the present application, and may include more or fewer steps than shown in the figures, or a combination of certain steps, or different steps.
[0069] The device embodiments described above are merely illustrative, and the units described as separate components may or may not be physically separated, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0070] Those skilled in the art will appreciate that all or some of the steps in the methods disclosed above, and the functional modules / units in the systems and devices may be implemented as software, firmware, hardware, or a suitable combination thereof.
[0071] In addition, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus that includes a series of steps or elements is not necessarily limited to those steps or elements explicitly listed, but may include other steps or elements not explicitly listed or inherent to such process, method, product, or apparatus.
[0072] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the above units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0073] The units described above as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0074] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.
[0075] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including multiple instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, referred to as ROM), random access memory (Random Access Memory, referred to as RAM), disk or optical disk and other media that can store programs.
[0076] The preferred embodiments of the present invention are described above with reference to the accompanying drawings, but the scope of the rights of the present invention is not limited thereto. Any modification, equivalent substitution and improvement made by a person skilled in the art without departing from the scope and essence of the present invention should be within the scope of the rights of the present invention.
Claims
1. A vehicle fault identification function testing method, characterized in that: The method comprises: generating a fault identification information table, wherein the fault identification information table includes a plurality of fault categories; Generate a test sequence corresponding to each fault category according to the fault identification information table; A test program is run based on the test sequence to test the vehicle controller to be tested, and a fault identification function test report is generated.
2. The method according to claim 1, characterized in that The test sequence includes a plurality of test steps; The step of running a test program based on the test sequence to test the vehicle controller to be tested and generating a fault identification function test report includes: Execute each of the test steps according to a preset order to run the test program and obtain test result parameters; Comparing the test result parameters with the expected result parameters to determine the test result; The fault identification function test report is generated based on the test result.
3. The method according to claim 2, characterized in that Executing each of the test steps according to a preset order to run the test program and obtain test result parameters includes: Calling fault identification requirement information from the fault identification information table, wherein the fault identification requirement information includes fault injection conditions, fault recovery conditions, and fault parameters; When it is detected that the current state of the test program meets the fault injection condition, a fault injection process is performed based on the fault parameter to construct a simulated fault scenario; Obtaining feedback information of the vehicle controller to be tested when operating in the simulated fault scenario; When it is detected that the current state of the test program meets the fault recovery condition, the operation of the vehicle controller to be tested in the simulated fault scenario is stopped, and the test result parameter is generated based on the feedback information.
4. The method according to claim 3, characterized in that The fault parameters include a sensor unit fault value, a battery management unit fault value, a controller unit fault value, and a communication unit fault value; The vehicle controller to be tested includes a plurality of control pins; When it is detected that the current state of the test program meets the fault injection condition, a fault injection process is performed based on the fault parameter to construct a simulated fault scenario, including: When it is detected that the current state of the test program meets the fault injection condition, the sensor unit fault value, the battery management unit fault value, the controller unit fault value and the communication unit fault value are respectively input into the target control pins of the vehicle controller to be tested to control the vehicle controller to be tested to be in a state of processing the fault signal and running in the simulated fault scenario.
5. The method according to claim 2, characterized in that: The comparing the test result parameter with the expected result parameter to determine the test result includes: When the fault diagnosis function of the vehicle controller to be tested is in an enabled state, acquiring fault diagnosis information of the vehicle controller to be tested and using it as the test result parameter; The fault diagnosis information is compared with expected fault diagnosis information as the expected result parameter to determine a first test result.
6. The method according to claim 2, characterized in that The comparing the test result parameter with the expected result parameter to determine the test result includes: When the cooling system of the vehicle is controlled by the vehicle controller to be tested, an actual state flag value of the cooling system is obtained and used as the test result parameter; The actual state flag value of the cooling system is compared with the expected state flag value as the expected result parameter to determine a second test result.
7. The method according to claim 2, characterized in that: The comparing the test result parameter with the expected result parameter to determine the test result includes: When the fault trigger flag information fed back by the controller of the vehicle to be tested is obtained, an actual fault injection threshold is obtained; Comparing the actual fault injection threshold with a preset threshold to determine a third test result; When the fault confirmation flag information fed back by the vehicle controller to be tested is obtained, if the fault code fed back by the vehicle controller to be tested is detected, it is determined that the fault code storage function of the vehicle controller to be tested is in a qualified state; When the fault code is obtained, the test time value is compared with the preset time value to determine a fourth test result, wherein the test time value is the difference between the time point when the fault trigger flag information is obtained and the time point when the fault confirmation flag information is obtained.
8. A vehicle fault identification function test device, characterized in that: The device comprises: A first generating module, configured to generate a fault identification information table, wherein the fault identification information table includes a plurality of fault categories; A second generating module, configured to generate a test sequence corresponding to each of the fault categories according to the fault identification information table; The test module is used to run a test program based on the test sequence to test the vehicle controller to be tested and generate a fault identification function test report.
9. An electronic device, characterized in that: The electronic device comprises a memory and a processor, the memory stores a computer program, and the processor implements the method according to any one of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.
Citation Information
Patent Citations
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
Function safety test method, device and equipment for vehicle control unit
CN117519073A
Vehicle control unit diagnosis test method, device and equipment and storage medium
CN117950391A
Vehicle fault code test method and device, electronic equipment and readable storage medium
CN118113541A
