Vehicle fault analysis method and device, upper computer, medium and product

Abstract

The invention relates to the technical field of vehicle faults, in particular to a vehicle fault analysis method and device, an upper computer, a medium and a product, and the method comprises the steps: obtaining the storage data of a target vehicle; identifying state change data, fault moment data and data before and after a fault in the storage data; at least one of the state change data, the fault moment data and the data before and after the fault is input into a whole-vehicle simulation model, the whole-vehicle simulation model outputs a fault analysis result of the target vehicle, and the whole-vehicle simulation model is established based on MWORKS. Therefore, the problems that in the prior art, freezing frame capacity is small, multi-fault processing is insufficient, cost is high, efficiency improvement is limited, and difference between simulation and a real vehicle is caused are solved.

Description

Technical Field

[0001] The present application relates to the field of vehicle failure technology, and in particular to a vehicle failure analysis method, device, host computer, medium and product. Background Art

[0002] As the popularity of cars increases, vehicle failures are becoming increasingly complex and diverse. Traditional fault diagnosis methods rely on reading fault codes and freeze frame data, but are limited by the limited storage capacity of freeze frames, only recording data at the moment of failure, and being unable to cover multiple faults occurring simultaneously. This leads to time-consuming and difficult challenges in troubleshooting.

[0003] In related technology 1, the remote diagnosis system based on the UDS protocol can collect CAN data in real time and support remote ECU upgrades, but it has high costs and technical barriers and is not suitable for household cars; in related technology 2, the fault diagnosis method based on external diagnostic equipment improves maintenance efficiency through priority sorting, but the fault troubleshooting efficiency is not significantly improved, and multi-fault processing is still difficult; in related technology 3, the miniature car fault diagnosis method improves the troubleshooting efficiency in a simulated environment, but does not solve the problem of real car data storage. Summary of the invention

[0004] The present application provides a vehicle fault analysis method, device, host computer, medium and product to solve the problems in the prior art such as small freeze frame capacity, insufficient multi-fault processing, high cost, limited efficiency improvement and differences between simulation and real vehicles.

[0005] The first aspect of the present application provides a vehicle fault analysis method, comprising the following steps: acquiring stored data of a target vehicle; identifying state change data, fault time data, and pre- and post-fault data in the stored data; inputting at least one of the state change data, fault time data, and pre- and post-fault data into a full-vehicle simulation model, and the full-vehicle simulation model outputs a fault analysis result of the target vehicle, wherein the full-vehicle simulation model is built based on MWORKS.

[0006] Optionally, the full vehicle simulation model includes a full vehicle model and a vehicle dynamics model, and at least one of the state change data, fault time data, and pre- and post-fault data is input into the full vehicle model and the vehicle dynamics model, a simulation environment is generated based on the full vehicle model and the vehicle dynamics model, road condition information and operating status of the target vehicle at the time of the fault are simulated based on the simulation environment, and a fault analysis result of the target vehicle is determined based on the road condition information and operating status of the target vehicle at the time of the fault.

[0007] Optionally, the full vehicle model includes the engine, transmission, chassis system and control system.

[0008] Optionally, the state change data and the fault time data are event-triggered data, and the data before and after the fault are log data.

[0009] Optionally, the state change data includes: at least one of the controller operating state, energy management mode, driving mode and CAN network management state, the fault time data includes the fault code and at least one of the fault change states, and the pre- and post-fault data includes the log data before the fault occurs and the log data after the fault occurs.

[0010] Optionally, the stored data is stored in a vehicle controller of the target vehicle.

[0011] The second aspect of the present application provides a vehicle fault analysis device, including: an acquisition module, used to acquire storage data of a target vehicle; an identification module, used to identify state change data, fault time data, and pre- and post-fault data in the stored data; an output module, used to input at least one of the state change data, fault time data, and pre- and post-fault data into a full-vehicle simulation model, and the full-vehicle simulation model outputs a fault analysis result of the target vehicle, wherein the full-vehicle simulation model is built based on MWORKS.

[0012] The third aspect of the present application provides a host computer, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor executes the program to implement the vehicle fault analysis method as described in the above embodiment.

[0013] The fourth aspect of the present application provides a computer-readable storage medium having a computer program stored thereon, which is executed by a processor to implement the vehicle fault analysis method as described in the above embodiment.

[0014] The fifth aspect of the present application provides a computer program product, which, when executed, is used to implement the vehicle fault analysis method as described in the above embodiment.

[0015] Therefore, this application includes the following beneficial effects:

[0016] The embodiment of the present application can comprehensively capture abnormal conditions that occur during the operation of the vehicle by identifying the state change data, fault time data, and pre- and post-fault data in the stored data, and input the data into the full-vehicle simulation model built based on MWORKS. The powerful computing power and simulation capabilities of the simulation model are used to simulate and analyze vehicle faults with high precision, thereby more accurately locating the cause of the fault; by integrating multiple data dimensions for comprehensive analysis, it can effectively deal with the situation of multiple concurrent faults and improve the efficiency and accuracy of complex fault handling. At the same time, it reduces dependence on physical equipment and reduces costs and time consumption in the diagnosis process. As a result, technical problems such as small freeze frame capacity, insufficient multi-fault handling, high cost, limited efficiency improvement, and differences between simulation and real vehicles in the prior art are solved.

[0017] Additional aspects and advantages of the present application will be given in part in the description below, and in part will become apparent from the description below, or will be learned through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The above and / or additional aspects and advantages of the present application will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0019] Figure 1 A flowchart of a vehicle fault analysis method provided according to an embodiment of the present application;

[0020] Figure 2 A flowchart of a vehicle fault analysis method provided according to an embodiment of the present application;

[0021] Figure 3 is an exemplary diagram of a vehicle fault analysis device according to an embodiment of the present application;

[0022] Figure 4 Schematic diagram of the structure of the host computer according to the embodiment of the present application. DETAILED DESCRIPTION

[0023] The embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present application, and should not be construed as limiting the present application.

[0024] The vehicle fault analysis method, device, host computer, medium and product of the embodiment of the present application are described below with reference to the accompanying drawings. In view of the problem that it takes a long time and is difficult to troubleshoot the cause of vehicle faults mentioned in the above background technology, the present application provides a vehicle fault analysis method, in which, by identifying the state change data, fault time data and pre- and post-fault data in the stored data, it is possible to fully capture the abnormal conditions that occur in the vehicle during operation, and input the data into the full-vehicle simulation model built based on MWORKS, and use the powerful computing power and simulation capabilities of the simulation model to simulate and analyze the vehicle fault with high precision, so as to more accurately locate the cause of the fault; by integrating multiple data dimensions for comprehensive analysis, it is possible to effectively deal with the situation of multiple faults occurring concurrently, and improve the efficiency and accuracy of complex fault handling. At the same time, it reduces the dependence on physical equipment and reduces the cost and time consumption in the diagnosis process. As a result, the problems of small freeze frame capacity, insufficient multi-fault handling, high cost, limited efficiency improvement and differences between simulation and real vehicles in the prior art are solved.

[0025] Specifically, Figure 1 A flow chart of a vehicle fault analysis method provided in an embodiment of the present application.

[0026] like Figure 1 As shown, the vehicle fault analysis method includes the following steps:

[0027] In step S101, the stored data of the target vehicle is obtained.

[0028] Among them, the target vehicle may be a vehicle that needs to be diagnosed or analyzed for faults, and the stored data may include the vehicle's operating status, sensor readings, user operation records, fault information, etc.

[0029] It can be understood that the embodiments of the present application obtain the storage data of the target vehicle, wherein the storage data is a true record of the vehicle operation process, providing a solid data foundation for subsequent fault analysis, performance evaluation and optimization.

[0030] In step S102, the state change data, the fault time data, and the pre- and post-fault data in the stored data are identified.

[0031] Among them, the state change data may include at least one of the controller operating state, energy management mode, driving mode and CAN network management state, the fault time data may include at least one of the fault code and the fault change state, and the pre- and post-fault data may include log data before the fault occurs and log data after the fault occurs.

[0032] It is understandable that the embodiments of the present application can track abnormal fluctuations in vehicle performance or status by identifying state change data, thereby preliminarily determining possible fault points. Fault time data directly indicates the exact time when the fault occurred, providing key time clues for fault diagnosis. Comparative analysis of data before and after the fault helps to further confirm the cause and development trend of the fault.

[0033] Specifically, the state change data records the state changes of the vehicle controller, including multiple operating states of the controller, such as the complete cycle from initialization to normal operation and then to power-off readiness, intelligent switching of energy management modes, such as smart hybrid, forced electric and power retention strategies, personalized adjustment of driving modes, such as economic, comfort and sports mode switching, and real-time update of CAN network management status, etc., providing a rich and accurate perspective for comprehensive and in-depth evaluation of the current state of the vehicle;

[0034] The fault time data adopts an efficient coding mechanism, in which the fault code occupies the first three digits to clearly identify the fault type; and the last digit dynamically reflects the fault status, realizing the fault occurrence mark from "0" to "1" and the fault clearance confirmation from "1" to "0", which not only speeds up the fault identification speed, but also greatly facilitates the tracking of the fault development trajectory and the monitoring of the resolution process;

[0035] The pre- and post-fault data recording function automatically starts at the critical moment of a fault, accurately capturing and saving detailed data within X seconds before and after the fault occurs. The recorded content is extensive and in-depth, covering the real-time status of the controller's internal variables and key interaction information between controllers, providing information for in-depth analysis of the root cause of the fault.

[0036] In the embodiment of the present application, the state change data and the fault time data are event-triggered data, and the data before and after the fault are log data.

[0037] It can be understood that the recording of fault time data in the embodiment of the present application helps to quickly locate the time point when the fault occurs, provide an accurate time reference for subsequent problem troubleshooting, and improve the efficiency of data storage and processing. Log-type data has timestamps and continuity, and can be traced back to any time point before and after the fault occurs, helping analysts to understand the process and causes of the fault in detail.

[0038] Specifically, during the troubleshooting process, the core role of the diagnostic service is to accurately read and parse various types of stored information for in-depth analysis. When the corresponding diagnostic service is requested, the controller will feedback data in different formats depending on the information type.

[0039] The first type of information is presented in a detailed event-triggered format, which records the timestamps and specific status changes of key events in detail. For example: "xxxx year xx month xx day xx hour xx minute xx second xx microsecond: the controller operation status variable changes from XX to initialization / running / power-off ready", and "xxxx year xx month xx day xx hour xx minute xx second xx microsecond: the driving mode variable is adjusted to economy / comfort / sport mode". This format not only provides time accuracy, but also clearly shows the dynamic changes of the status, providing intuitive clues for troubleshooting.

[0040] The second type of information also follows the event-triggered principle, but focuses on the marking and status change of the fault event, and its expression is more concise: "xxxx year xx month xx day xx hour xx minute xx second xx microsecond: fault code xxxx, where the first 3 digits identify the fault type, and the last digit indicates the fault status, from 0 to 1 to mark the occurrence of the fault, and from 1 to 0 to confirm the clearing of the fault. This type of information is directly related to the fault event and is the key to quickly locate and diagnose the fault.

[0041] The third type of log data records a lot of details before and after the failure, covering the internal status of the controller and interaction information. Due to the large amount of data, sufficient storage space must be reserved. These data are extremely valuable for fault root cause analysis, scene restoration and system performance optimization.

[0042] In an embodiment of the present application, the stored data is stored in a vehicle controller of the target vehicle.

[0043] It can be understood that the embodiment of the present application stores data in the vehicle controller of the target vehicle, which can collect and process various data during the operation of the vehicle in real time, ensuring the timeliness and accuracy of the data, and providing a reliable basis for subsequent troubleshooting and analysis.

[0044] In step S103, at least one of the state change data, the fault time data and the pre- and post-fault data is input into the full vehicle simulation model, and the full vehicle simulation model outputs the fault analysis result of the target vehicle, wherein the full vehicle simulation model is built based on MWORKS.

[0045] The full vehicle simulation model may include a full vehicle model and a vehicle dynamics model.

[0046] It can be understood that the embodiment of the present application can obtain comprehensive information before and after the vehicle failure by inputting state change data, fault time data and pre- and post-fault data through the full vehicle simulation model. The fault analysis based on the full vehicle simulation model can quickly locate the specific component where the fault occurs, thereby reducing the time and cost of troubleshooting.

[0047] In an embodiment of the present application, at least one of the state change data, the fault time data, and the pre- and post-fault data is input into the full vehicle model and the vehicle dynamics model, a simulation environment is generated based on the full vehicle model and the vehicle dynamics model, the road condition information and the operating status of the target vehicle at the time of the fault are simulated based on the simulation environment, and the fault analysis result of the target vehicle is determined based on the road condition information and the operating status of the target vehicle at the time of the fault.

[0048] Among them, the full vehicle model can include the engine, transmission system, chassis system and control system.

[0049] It can be understood that the embodiments of the present application construct a simulation environment to simulate fault scenarios by inputting multi-source data into the full vehicle and vehicle dynamics model, thereby achieving accurate and rapid fault analysis and location, promoting system optimization and fault prevention, and improving user experience.

[0050] Specifically, the MWORKS platform uses multi-domain unified modeling capabilities to build a detailed full-vehicle and dynamics model, and combines real fault data to create a realistic simulation environment. It can simulate the operating status of the vehicle under different working conditions, provide an accurate simulation environment for fault diagnosis, and significantly improve the efficiency and accuracy of complex fault troubleshooting. It enhances emergency response capabilities, optimizes controller strategies, improves vehicle performance and reliability, and brings users a safer and more stable driving experience.

[0051] According to the vehicle fault analysis method proposed in the embodiment of the present application, by identifying the state change data, fault time data and pre- and post-fault data in the stored data, it is possible to comprehensively capture the abnormal conditions that occur in the vehicle during operation, and input the data into the full-vehicle simulation model built based on MWORKS, and use the powerful computing power and simulation capabilities of the simulation model to simulate and analyze the vehicle fault with high precision, so as to more accurately locate the cause of the fault; by integrating multiple data dimensions for comprehensive analysis, it is possible to effectively deal with the situation of multiple concurrent faults and improve the efficiency and accuracy of complex fault handling. At the same time, it reduces the dependence on physical equipment and reduces the cost and time consumption in the diagnosis process. As a result, the problems of small freeze frame capacity, insufficient multi-fault handling, high cost, limited efficiency improvement, and differences between simulation and real vehicles in the prior art are solved.

[0052] The following will be combined Figure 2 The vehicle fault analysis method is specifically described as follows:

[0053] S1. During normal driving of the vehicle, a series of key status information and its timestamps are recorded in real time and accurately, including the energy management mode, driving mode selection and CAN network management status in the controller operation state;

[0054] S2. When the vehicle encounters multiple fault challenges in a single driving cycle, the controller will immediately capture and record the fault code and its state change time in detail. This recording mechanism marks the occurrence and removal time of the fault with extremely high accuracy, in the following form: xxxx year xx month xx day xx hour xx minute xx second xx microsecond: fault code xxxx, where the first 3 digits identify the specific fault, and the last digit indicates the state change, 0 to 1 means the fault has occurred, and 1 to 0 means the fault has been cleared;

[0055] For each fault event, the controller will also automatically collect and save the third type of data, which is a detailed log within the preset time window before and after the fault occurs. These log data are valuable resources for fault diagnosis and provide a direct basis for in-depth analysis of the cause and process of the fault;

[0056] S3. In the process of in-depth investigation of the cause of vehicle failure, the diagnostic service is used to accurately read and extract the information stored in the controller, including detailed status information, clear fault code records, and detailed data of the key time periods before and after the failure occurs;

[0057] S4. During simulation analysis, the read information and data are injected into the full vehicle and driving condition simulation model built by MWORKS to simulate the actual situation when the fault occurs, identify the cause, solve the problem, improve the controller strategy, and improve the vehicle status.

[0058] In summary, the embodiment of the present application effectively supports fault cause analysis and helps accurately build the MWORKS vehicle simulation model by recording the changes in vehicle and controller status, fault occurrence and clearing time, and key log data before and after the fault in real time. At the same time, using the MWORKS simulation model to import fault data for simulation analysis not only improves the efficiency and accuracy of fault diagnosis, but also facilitates the optimization of vehicle performance under different working conditions, achieving the dual goals of vehicle fault troubleshooting and performance improvement.

[0059] Next, the vehicle fault analysis device proposed according to the embodiment of the present application is described with reference to the accompanying drawings.

[0060] Figure 3 It is a block diagram of a vehicle fault analysis device according to an embodiment of the present application.

[0061] like Figure 3 As shown, the vehicle fault analysis device 10 includes: an acquisition module 100 , an identification module 200 and an output module 300 .

[0062] Among them, the acquisition module 100 is used to acquire the stored data of the target vehicle; the identification module 200 is used to identify the state change data, fault time data and pre- and post-fault data in the stored data; the output module 300 is used to input at least one of the state change data, fault time data and pre- and post-fault data into the full vehicle simulation model, and the full vehicle simulation model outputs the fault analysis result of the target vehicle, wherein the full vehicle simulation model is built based on MWORKS.

[0063] It should be noted that the above explanations of the vehicle fault analysis method embodiment are also applicable to the vehicle fault analysis device of this embodiment, and will not be repeated here.

[0064] According to the vehicle fault analysis device proposed in the embodiment of the present application, by identifying the state change data, fault time data and pre- and post-fault data in the stored data, it is possible to comprehensively capture the abnormal conditions that occur during the operation of the vehicle, and input the data into the full-vehicle simulation model built based on MWORKS, and use the powerful computing power and simulation capabilities of the simulation model to simulate and analyze the vehicle fault with high precision, so as to more accurately locate the cause of the fault; by integrating multiple data dimensions for comprehensive analysis, it is possible to effectively deal with the situation of multiple concurrent faults and improve the efficiency and accuracy of complex fault handling. At the same time, it reduces the dependence on physical equipment and reduces the cost and time consumption in the diagnosis process. As a result, the problems of small freeze frame capacity, insufficient multi-fault handling, high cost, limited efficiency improvement, and differences between simulation and real vehicles in the prior art are solved.

[0065] Figure 4 A schematic diagram of the structure of the host computer provided in the embodiment of the present application. The host computer may include:

[0066] Memory 401 , processor 402 , and a computer program stored in the memory 401 and executable on the processor 402 .

[0067] When the processor 402 executes the program, the vehicle fault analysis method provided in the above embodiment is implemented.

[0068] Furthermore, the host computer also includes:

[0069] The communication interface 403 is used for communication between the memory 401 and the processor 402 .

[0070] The memory 401 is used to store computer programs that can be executed on the processor 402 .

[0071] The memory 401 may include a high-speed RAM (Random Access Memory) memory, and may also include a non-volatile memory, such as at least one disk memory.

[0072] If the memory 401, the processor 402 and the communication interface 403 are implemented independently, the communication interface 403, the memory 401 and the processor 402 can be connected to each other through a bus and communicate with each other. The bus can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 4 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0073] Optionally, in a specific implementation, if the memory 401, the processor 402 and the communication interface 403 are integrated on a chip, the memory 401, the processor 402 and the communication interface 403 can communicate with each other through an internal interface.

[0074] The processor 402 may be a CPU (Central Processing Unit), or an ASIC (Application Specific Integrated Circuit), or one or more integrated circuits configured to implement the embodiments of the present application.

[0075] An embodiment of the present application also provides a computer-readable storage medium having a computer program stored thereon, which implements the above vehicle fault analysis method when executed by a processor.

[0076] An embodiment of the present application also provides a computer program product, which implements the above vehicle fault analysis method when the computer program is executed.

[0077] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. 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 application. In this specification, the schematic representations of the above terms are not necessarily directed to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or N embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.

[0078] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include at least one of the features. In the description of this application, "N" means at least two, such as two, three, etc., unless otherwise clearly and specifically defined.

[0079] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, fragment or portion of code comprising one or N executable instructions for implementing the steps of a custom logical function or process, and the scope of the preferred embodiments of the present application includes alternative implementations in which functions may not be performed in the order shown or discussed, including performing functions in a substantially simultaneous manner or in reverse order depending on the functions involved, which should be understood by technicians in the technical field to which the embodiments of the present application belong.

[0080] It should be understood that the various parts of the present application can be implemented in hardware, software, firmware or a combination thereof. In the above-mentioned embodiments, the steps or methods can be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented by any one of the following technologies known in the art or their combination: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array, a field programmable gate array, etc.

[0081] A person of ordinary skill in the art may understand that all or part of the steps carried by the method for implementing the above-mentioned embodiment may be completed by instructing related hardware through a program, and the above-mentioned program may be stored in a computer-readable storage medium, which, when executed, includes one of the steps of the method embodiment or a combination thereof.

[0082] Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and cannot be understood as limitations on the present application. Ordinary technicians in this field can change, modify, replace and modify the above embodiments within the scope of the present application.

Claims

1. A vehicle fault analysis method, characterized in that: The following steps are involved: Obtain the stored data of the target vehicle; Identifying state change data, fault time data, and pre- and post-fault data in the stored data; At least one of the state change data, the fault time data and the pre- and post-fault data is input into a full vehicle simulation model, and the full vehicle simulation model outputs a fault analysis result of the target vehicle, wherein the full vehicle simulation model is built based on MWORKS.

2. The vehicle fault analysis method according to claim 1, characterized in that: The full vehicle simulation model includes a full vehicle model and a vehicle dynamics model, at least one of the state change data, the fault time data and the pre- and post-fault data is input into the full vehicle model and the vehicle dynamics model, a simulation environment is generated based on the full vehicle model and the vehicle dynamics model, road condition information and operating status of the target vehicle at the time of the fault are simulated based on the simulation environment, and a fault analysis result of the target vehicle is determined based on the road condition information and operating status of the target vehicle at the time of the fault.

3. The vehicle fault analysis method according to claim 2, characterized in that: The full vehicle model includes an engine, a transmission system, a chassis system and a control system.

4. The vehicle fault analysis method according to claim 1, characterized in that: The state change data and the fault time data are event-triggered data, and the pre- and post-fault data are log data.

5. The vehicle fault analysis method according to claim 1 or 4, characterized in that: The state change data includes: at least one of the controller operating state, energy management mode, driving mode and CAN network management state; the fault time data includes at least one of the fault code and the fault change state; the pre- and post-fault data includes the log data before the fault occurs and the log data after the fault occurs.

6. The vehicle fault analysis method according to claim 1, characterized in that: The stored data is stored in the vehicle controller of the target vehicle.

7. A vehicle fault analysis device, characterized in that: include: An acquisition module, used to acquire the storage data of the target vehicle; An identification module, used to identify the state change data, the fault time data and the pre- and post-fault data in the stored data; The output module is used to input at least one of the state change data, the fault time data and the pre- and post-fault data into a full-vehicle simulation model, and the full-vehicle simulation model outputs the fault analysis result of the target vehicle, wherein the full-vehicle simulation model is built based on MWORKS.

8. A host computer, characterized in that: include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the vehicle fault analysis method according to any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program or instruction stored thereon, characterized in that: When the computer program or instruction is executed, the vehicle fault analysis method according to any one of claims 1 to 6 is implemented.

10. A computer program product comprising a computer program or instructions, characterized in that When the computer program or instruction is executed, the vehicle fault analysis method according to any one of claims 1 to 6 is implemented.

Images