Fault diagnosis method and system, controller and vehicle

Through the communication of the vehicle's on-board unit and the local fault diagnosis model, the problem of low diagnosis efficiency in the case of fault-free diagnostic instruments is solved, and fast and convenient fault information acquisition and processing is achieved, improving diagnostic efficiency and user experience.

CN120335429APending Publication Date: 2025-07-18BYD CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202510572909.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-04-30
Publication Date
2025-07-18

AI Technical Summary

Technical Problem

Without a fault diagnosis instrument, it is difficult to obtain vehicle fault information in a timely and accurate manner, resulting in inefficient diagnosis.

Method used

Through communication between on-board units within the vehicle, diagnostic requirements are sent and diagnostic responses are received to parse fault results, and fault information is obtained and processed using local fault diagnosis models, including model pruning and deployment of cloud-based training models with quantification.

Benefits of technology

Improves fault diagnosis efficiency and user experience, saves costs, avoids the use of special diagnostic instruments, and quickly and conveniently diagnoses and recovers when a fault occurs.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120335429A_ABST
    Figure CN120335429A_ABST
Patent Text Reader

Abstract

The invention discloses a fault diagnosis method and system, a controller and a vehicle, and the method comprises the steps that a first vehicle-mounted unit sends a diagnosis demand to a second vehicle-mounted unit in response to a diagnosis instruction; and receiving a diagnosis response related to the second on-board unit, and analyzing a diagnosis result according to the diagnosis response. Visibly, the fault information can be obtained through the vehicle-mounted unit in the vehicle, and the fault result is determined according to the fault information, so that the fault diagnosis efficiency and the user experience are improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the technical field of fault diagnosis, and particularly to a fault diagnosis method, system, controller and vehicle. Background Art

[0002] For vehicle fault diagnosis, it is generally carried out through an on-board diagnostics (OBD) device. With the OBD device, it is convenient to read fault information in some ways later and determine the fault diagnosis result according to the fault information, so as to facilitate vehicle maintenance. However, in some scenarios without a diagnostic instrument, it is difficult to timely and accurately obtain the fault situation, reducing the diagnostic efficiency.

[0003] Application Content

[0004] This application provides a fault diagnosis method, system, controller and vehicle, which can obtain fault information through the in-vehicle unit inside the vehicle and determine the fault result according to the fault information, improving the fault diagnosis efficiency and user experience.

[0005] To solve the above technical problems, in the first aspect of this application, a fault diagnosis method is disclosed, and the method includes:

[0006] In response to a diagnostic instruction, a first in-vehicle unit sends a diagnostic requirement to a second in-vehicle unit;

[0007] Receive a diagnostic response related to the second in-vehicle unit to parse the diagnostic result according to the diagnostic response.

[0008] As an optional implementation manner, in the first aspect of this application, the diagnostic requirement includes: an electronic controller diagnostic requirement, a microcontroller diagnostic requirement, a system-on-chip diagnostic requirement, and a display diagnostic requirement.

[0009] As an optional implementation manner, in the first aspect of this application, at least one of the first in-vehicle unit and the second in-vehicle unit is an in-vehicle host.

[0010] As an optional implementation manner, in the first aspect of this application, the in-vehicle host includes one or more of a central control in-vehicle host, a co-pilot in-vehicle host, a rear-seat in-vehicle host, a left-rear cabin in-vehicle host, a right-rear cabin in-vehicle host, and a ceiling in-vehicle host.

[0011] As an optional implementation manner, in the first aspect of this application, the responding to the diagnostic instruction includes:

[0012] Responding to a diagnostic instruction triggered by a user on the display interface of the first in-vehicle unit.

[0013] As an alternative implementation, in the first aspect of the present application, the method further includes:

[0014] Performing fault repair on the second vehicle-mounted unit whose diagnosis result indicates a fault state.

[0015] As an alternative implementation, in the first aspect of the present application, when both the first vehicle-mounted unit and the second vehicle-mounted unit are vehicle-mounted hosts, the performing fault repair on the second vehicle-mounted unit whose diagnosis result indicates a fault state includes:

[0016] If the diagnosis result indicates that the MCU of the second vehicle-mounted unit is abnormal, the first vehicle-mounted unit sends an MCU restart instruction to the second vehicle-mounted unit;

[0017] If the diagnosis result indicates that the SOC of the second vehicle-mounted unit is abnormal, the first vehicle-mounted unit sends an SOC restart instruction to the second vehicle-mounted unit.

[0018] As an alternative implementation, in the first aspect of the present application, before the first vehicle-mounted unit sends an SOC restart instruction to the second vehicle-mounted unit, the method further includes:

[0019] The first vehicle-mounted unit controls the second vehicle-mounted unit to enter the memory dump mode.

[0020] As an alternative implementation, in the first aspect of the present application, the parsing the diagnosis result according to the diagnosis response includes:

[0021] The first vehicle-mounted unit parses the diagnosis response based on a local fault diagnosis model to obtain a diagnosis result.

[0022] As an alternative implementation, in the first aspect of the present application, the method further includes:

[0023] The local fault diagnosis model is obtained by compressing a cloud fault diagnosis model trained in the cloud.

[0024] As an alternative implementation, in the first aspect of the present application, the compression method includes at least one of model pruning and model quantization.

[0025] As an alternative implementation, in the first aspect of the present application, the method further includes: the first vehicle-mounted unit sending the diagnosis result to the cloud so that the cloud updates the cloud fault diagnosis model.

[0026] The second aspect of the present application discloses another fault diagnosis method, and the method includes:

[0027] In response to the diagnostic requirement of the first vehicle-mounted unit, the second vehicle-mounted unit sends a diagnostic response to the first vehicle-mounted unit, so that the first vehicle-mounted unit can analyze the diagnostic result according to the diagnostic response.

[0028] The third aspect of the present application discloses a fault diagnosis system, which at least includes a first vehicle-mounted unit and a second vehicle-mounted unit.

[0029] The first vehicle-mounted unit is used to implement any one of the methods disclosed in the first aspect of the present application.

[0030] The second vehicle-mounted unit uses the method disclosed in the second aspect of the present application.

[0031] The fourth aspect of the present application discloses a controller, which includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor. When the program or instruction is executed by the processor, it implements any one of the methods described in the first aspect and the second aspect of the present application.

[0032] The fifth aspect of the present application discloses a computer-readable storage medium, in which a computer program or instruction is stored. When the computer program runs, it implements any one of the methods described in the first aspect and the second aspect of the present application.

[0033] The sixth aspect of the present application discloses a vehicle, which includes the fault diagnosis system of the third aspect of the present application, the controller of the fourth aspect of the present application, or the computer-readable storage medium of the fifth aspect of the present application.

[0034] The seventh aspect of the present application discloses a computer program product, which includes a computer program or instruction. When the computer program or instruction is executed by a processor, it implements the steps of any one of the methods described in the first aspect and the second aspect of the present application.

[0035] Compared with the prior art, the present application has the following beneficial effects:

[0036] In the present application, in response to a diagnostic instruction, the first vehicle-mounted unit sends a diagnostic requirement to the second vehicle-mounted unit; receives a diagnostic response related to the second vehicle-mounted unit to analyze the diagnostic result according to the diagnostic response. It can be seen that the present application can obtain fault information through the vehicle-mounted unit inside the vehicle and determine the fault result according to the fault information, improving the fault diagnosis efficiency and user experience. Description of the Drawings

[0037] To more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings required for the description of the embodiments. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other drawings can be obtained based on these drawings.

[0038] Figure 1 is a schematic flowchart of a fault diagnosis method disclosed according to an embodiment of the present application;

[0039] Figure 2 is a schematic structural diagram of a fault diagnosis system disclosed according to an embodiment of the present application;

[0040] Figure 3 is another schematic structural diagram of a fault diagnosis system disclosed according to an embodiment of the present application;

[0041] Figure 4 is a schematic flowchart of another fault diagnosis method disclosed according to an embodiment of the present application;

[0042] Figure 5 is a schematic flowchart of yet another fault diagnosis method disclosed according to an embodiment of the present application;

[0043] Figure 6 A schematic flowchart of yet another fault diagnosis method disclosed according to an embodiment of the present application. Detailed implementation manners

[0044] To enable those skilled in the art to better understand the solutions of the present application, the following will clearly and completely describe the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only some embodiments of the present application, rather than all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts belong to the scope of protection of the present application.

[0045] The terms "first", "second", etc. in the specification and claims of the present application and the above drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "comprising" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, device, product, or terminal that includes a series of steps or units is not limited to the listed steps or units, but optionally further includes steps or units not listed, or optionally further includes other steps or units inherent to these processes, methods, products, or terminals.

[0046] References to "embodiments" in this specification mean that the specific features, structures, or characteristics described in connection with the embodiments can be included in at least one embodiment of the present application. The phrase appears in various places in the specification and does not necessarily refer to the same embodiment each time, nor are they independent or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0047] According to a first aspect of the present application, embodiments of the present application provide a fault diagnosis method. This fault diagnosis method can obtain fault information through an in-vehicle unit inside the vehicle and can determine a fault result based on the fault information, improving the fault diagnosis efficiency and user experience. The following will be described in detail separately.

[0048] Please refer to Figure 1 , Figure 1 which is a flowchart of a fault diagnosis method disclosed in an embodiment of the present application. Among them, this fault diagnosis method may include the following operations:

[0049] 101. In response to a diagnosis instruction, a first in-vehicle unit sends a diagnosis requirement to a second in-vehicle unit.

[0050] In embodiments of the present application, the in-vehicle units inside the vehicle are interconnected. For example, the in-vehicle host is connected to the body CAN network through a CAN line. The present disclosure does not limit the specific manner of connection, and both wired and wireless connections are acceptable. For example, the in-vehicle host can receive CAN message information sent by other domain controls such as the body and / or an electronic control unit (ECU), or can control the in-vehicle host to send corresponding messages to other domain controls / ECU units such as the body. When vehicle fault diagnosis is required, the first in-vehicle unit can, in response to a diagnosis instruction from a user or the system itself, send a diagnosis requirement to the second in-vehicle unit to be diagnosed.

[0051] 102. Receive a diagnosis response related to the second in-vehicle unit to analyze the diagnosis result based on the diagnosis response.

[0052] In embodiments of the present application, after the first in-vehicle unit receives a diagnosis response related to the second in-vehicle unit, it can analyze the diagnosis result of the second in-vehicle unit based on this diagnosis response to determine whether the second in-vehicle unit has a fault or how to handle the fault.

[0053] It can be seen that the method described in embodiments of the present application can obtain fault information through the in-vehicle units inside the vehicle and can determine a fault result based on the fault information, eliminating the need for a dedicated fault diagnostic instrument, improving the fault diagnosis efficiency and user experience, and saving costs.

[0054] In an alternative embodiment, the diagnostic requirements include: electronic controller diagnostic requirements, microcontroller diagnostic requirements, system-on-chip diagnostic requirements, and display diagnostic requirements.

[0055] In the embodiments of the present application, please refer to Figure 2 , Figure 2 which is a schematic structural diagram of a fault diagnosis system disclosed in the embodiments of the present application. Exemplarily, the system structure includes a plurality of in-vehicle hosts interconnected, and can also be connected to a domain control node and an ECU unit in a wired connection form. Therefore, in this embodiment, fault diagnosis can be performed on the display, etc. of an electronic control unit ECU (Electronic Control Unit), a microcontroller unit MCU (Microcontroller Unit), a system-on-chip SOC (System on Chip), and a display screen, etc., and corresponding diagnostic requirements or instructions can be issued.

[0056] It can be seen that the method described in the embodiments of the present application can perform fault diagnosis on various types of in-vehicle units, with higher generality and adaptability, and further improve the efficiency of fault diagnosis.

[0057] In an alternative embodiment, at least one of the first in-vehicle unit and the second in-vehicle unit is an in-vehicle host. In the embodiments of the present application, the in-vehicle host can initiate diagnostic requirements as the first in-vehicle unit, and at the same time, the display of the host can be reused to display the corresponding diagnostic results. Correspondingly, the in-vehicle host can also be used as the second in-vehicle unit, as the unit to be diagnosed, and the faults of the MCU, SOC, and display screen, etc. therein can be diagnosed.

[0058] It can be seen that the method described in the embodiments of the present application can reuse the existing in-vehicle host and screen, eliminating the need for a dedicated fault diagnostic instrument, saving costs; on the other hand, it can facilitate users to perform fault diagnosis at any time, eliminating the need to take time to go to the store for diagnosis and repair when the vehicle breaks down, saving the time required for fault diagnosis.

[0059] In an alternative embodiment, refer to Figure 3 , Figure 3It is a schematic structural diagram of another fault diagnosis system disclosed in the embodiments of the present application. The in-vehicle host includes one or more of a central control in-vehicle host, a co-pilot in-vehicle host, a rear-row in-vehicle host, a left rear cockpit in-vehicle host, a right rear cockpit in-vehicle host, and a ceiling-mounted in-vehicle host. In the embodiments of the present application, existing multiple in-vehicle hosts in the vehicle can be utilized. For example, through the interconnection method of the central control in-vehicle host, the co-pilot in-vehicle host, and the left and right rear cockpit in-vehicle hosts, vehicle fault diagnosis can be achieved through any in-vehicle host, avoiding the problem that fault diagnosis cannot be performed when a single vehicle computer is abnormal. Further, by making full use of the characteristics of multiple in-vehicle hosts in the vehicle, the method of performing diagnosis through any in-vehicle host in the vehicle can avoid the defect that when using a single in-vehicle host for fault diagnosis, if the in-vehicle host used for fault diagnosis has an abnormality, including faults such as crashing, inability to power on, unresponsive screen touch, black screen, etc., fault diagnosis cannot be performed.

[0060] In an alternative embodiment, refer to Figure 4 , Figure 4 It is a schematic flowchart of a fault diagnosis method disclosed in the embodiments of the present application. The first vehicle-mounted unit can respond to a diagnosis instruction triggered by a user on the display interface of the first vehicle-mounted unit or a diagnosis instruction triggered by the system itself, such as periodic diagnosis, etc., and then perform fault diagnosis on the unit to be diagnosed. At the same time, the diagnosis result can be displayed through the display interface, which is intuitive and visible. It can be seen that the embodiments of the present application reuse the existing in-vehicle host and screen, eliminating the need for a dedicated fault diagnosis instrument and saving costs.

[0061] In an alternative embodiment, the method may further include the following operations:

[0062] Using the in-vehicle host, when a fault of a certain unit to be diagnosed is detected, measures such as log saving and restart recovery can be performed on the faulty unit through CAN message instructions, quickly realizing fault diagnosis and processing of the in-vehicle host. That is, in addition to diagnosis, it also has the function of fault repair for the second vehicle-mounted unit whose diagnosis result indicates a fault state.

[0063] It can be seen that through normal in-vehicle host diagnosis and recovery, the problem of having to enter the store for troubleshooting and recovery when the unit to be diagnosed has an abnormality is avoided, and the special diagnosis and recovery of the in-vehicle fault host are quickly and conveniently realized.

[0064] In an alternative embodiment, when both the first vehicle-mounted unit and the second vehicle-mounted unit are in-vehicle hosts, the fault repair of the second vehicle-mounted unit whose diagnosis result indicates a fault state includes:

[0065] If the diagnosis result indicates that the MCU of the second vehicle-mounted unit is abnormal, the first vehicle-mounted unit sends an MCU restart instruction to the second vehicle-mounted unit;

[0066] When the diagnostic result indicates that the SOC of the second vehicle-mounted unit is abnormal, the first vehicle-mounted unit sends a SOC restart instruction to the second vehicle-mounted unit.

[0067] In the embodiments of the present application, the first vehicle-mounted unit can perform different fault repair operations for different faults (such as MCU fault, SOC fault, display fault, etc.) of the second vehicle-mounted unit. Refer to Figure 5 , Figure 5 is a schematic flowchart of a fault diagnosis method disclosed in the embodiments of the present application. The first vehicle-mounted unit initiates a diagnostic requirement. When the unit to be diagnosed, that is, the second vehicle-mounted unit, is not the in-vehicle host, the general electronic control unit diagnostic process is executed. When the unit to be diagnosed is the in-vehicle host, first, it is diagnosed whether the MCU of the second vehicle-mounted unit is normal. If the MCU has a fault, a specific message is sent to keep the fault log, and / or a message is sent to restart the faulty in-vehicle host to recover its MCU. If the MCU is normal, the running information of the second vehicle-mounted unit, such as the passing state or the SOC voltage, can be obtained. Further, it continues to diagnose whether the state of the in-vehicle host SOC is normal. If the SOC has a fault, the SOC of the second vehicle-mounted unit is controlled to restart. If the SOC is normal, the display screen of the second vehicle-mounted unit can be further diagnosed, such as sending a series of specific messages to control the SOC to perform screen diagnosis, including: sending a specific image for display, reading screen node information, etc.

[0068] In the embodiments of the present application, specifically, when a certain host in the vehicle has a fault, a diagnostic message can be sent to the target faulty host through a normal vehicle computer, and fault diagnosis is performed through the fault code returned by the faulty host. The fault diagnosis software is installed in multiple hosts in the vehicle in the form of an APK and runs on the SOC. When performing fault diagnosis, the user clicks to run the fault diagnosis software, and specific operations to be executed are sent to the faulty host through the software interface, including but not limited to: the host saves the log, diagnoses the host MCU, controls the SOC to enter the dump (memory dump mode), queries the host screen display status, restarts and recovers the host, etc.:

[0069] 1. Sending a message to save the log: It means sending a specified CAN message to the faulty host MCU, and then controlling the SOC to save the SOC system log, MCU log, AutoHallog, etc.;

[0070] 2. Diagnosing the host MCU: It means sending a CAN message to the faulty host MCU to obtain hardware information such as the MCU running state, the communication state between the MCU and the SOC, and the SOC voltage;

[0071] 3. Control the SOC to enter the dump mode: When it is detected that the SOC system crashes, specific messages can be sent through CAN messages to enable the faulty host MCU to control specific pins of the SOC, thereby enabling the SOC to enter the DUMP memory dump mode, which is convenient for further diagnosing specific crash faults;

[0072] 4. Query the host screen display status: When the host screen display is abnormal or touch control is unavailable, specific messages can be sent to the faulty host MCU, and then the host SOC can be controlled to diagnose the screen status, including sending specific images to the display screen, reading screen register values, etc.;

[0073] 5. Restart and recover the host: The SOC host can be restarted and recovered by sending CAN messages to the faulty host MCU to control the SOC power key pin.

[0074] It can be seen that the method described in the embodiments of the present application can, when a fault occurs in the device to be diagnosed, not only diagnose whether the in-vehicle host MCU is abnormal, but also further obtain diagnostic information and perform recovery on components such as the in-vehicle host SOC and screen.

[0075] In an alternative embodiment, before the first vehicle unit sends an SOC restart instruction to the second vehicle unit, the method further includes:

[0076] The first vehicle unit controls the second vehicle unit to enter the memory dump mode. That is, as described above, by controlling the second vehicle unit to enter the memory dump mode, when a system-level error occurs in the SOC, the entire or part of the memory content is captured into a dump file, including the memory space of the CPU, cache content, etc. The cause of the fault can be better analyzed through the saved dump file, which is convenient for later analysis by diagnosticians.

[0077] In an alternative embodiment, parsing the diagnostic result according to the diagnostic response includes:

[0078] The first vehicle unit parses the diagnostic response based on the local fault diagnosis model to obtain the diagnostic result. The local fault diagnosis model: According to the actual requirements and characteristics of vehicle faults, model structures such as CNN, RNN, VAE, and Transformer in deep learning can be selected.

[0079] It can be seen that the in-vehicle host, as a fault diagnosis edge computing device, utilizes its own computing power to locally and real-time parse and analyze the collected fault diagnosis data, further improving the efficiency of vehicle fault diagnosis. At the same time, it avoids the security risks during data network transmission and improves data security.

[0080] In an alternative embodiment, the local fault diagnosis model is obtained by compressing a cloud-based fault diagnosis model trained in the cloud. Refer to Figure 6 , Figure 6 FIG. Figure 6 is a schematic flowchart of a fault diagnosis method disclosed in an embodiment of the present application. By collecting existing fault acquisition data and diagnosis results, data processing and training are performed on a cloud platform, and a fault diagnosis recognition model is constructed and model training is completed. The trained model is subjected to model pruning and model quantization processing to compress the trained fault diagnosis recognition model, and then it is deployed into the in-vehicle host through methods such as cloud distribution, version integration, or software Android.

[0081] It can be seen that by utilizing the computing power of the in-vehicle host of a new energy vehicle to act as an edge computing platform in vehicle fault diagnosis, there is no need to rely on acquisition devices and cloud platforms for diagnosis. By compressing and deploying the diagnosis model trained in the cloud into the in-vehicle host, the acquisition, processing, and analysis of fault data can be realized at the vehicle terminal, greatly improving the efficiency and real-time performance of fault diagnosis, and at the same time avoiding the data security risks brought by data transmission.

[0082] In an alternative embodiment, the model compression method includes at least one of model pruning and model quantization.

[0083] In the embodiment of the present application, two methods are included for compressing the model: model pruning and model compression. For the model pruning method, according to actual needs and the characteristics of the model structure, methods such as weight pruning, structured pruning, layer-wise pruning, and iterative pruning can be selected. For the model quantization method, different quantization granularities can be selected according to the performance of the in-vehicle host in different vehicle models, such as FP16 quantization, INT8 quantization, or mixed-precision quantization, which can improve the adaptability and generality of the present solution.

[0084] In an alternative embodiment, the method further includes: the first in-vehicle unit sending the diagnosis result to the cloud to enable the cloud to update the cloud-based fault diagnosis model. It can be seen that the model of the present solution can be continuously iterated and updated in the future, and the diagnosis effect will be better and better.

[0085] According to the second aspect of the present application, an embodiment of the present application provides another fault diagnosis method. An embodiment of the present application discloses a vehicle fault diagnosis method, which is applied to a second in-vehicle unit, that is, the unit to be diagnosed, and includes: the second in-vehicle unit responding to the diagnosis requirement of the first in-vehicle unit and sending a diagnosis response to the first in-vehicle unit to enable the first in-vehicle unit to analyze the diagnosis result according to the diagnosis response.

[0086] In the embodiments of the present application, the specific method steps of the first vehicle-mounted unit and the second vehicle-mounted unit have been described in the above embodiments and will not be elaborated here.

[0087] According to the third aspect of the present application, embodiments of the present application also disclose a fault diagnosis system, which at least includes a first vehicle-mounted unit and a second vehicle-mounted unit.

[0088] The first vehicle-mounted unit and the second vehicle-mounted unit are respectively used to implement the fault diagnosis method described in the above embodiments. All beneficial effects are not elaborated here in the present application.

[0089] According to the fourth aspect of the present application, embodiments of the present application also provide a controller, including: a memory and a processor, with a computer program stored on the memory; the processor is used to execute the computer program in the memory to implement the steps of the above fault diagnosis method. This controller has all the beneficial effects of the above fault diagnosis method and will not be elaborated here in the present application.

[0090] According to the fifth aspect of the present application, embodiments of the present application also provide a computer-readable storage medium, on which a computer program or instruction is stored, and when the program is executed by a processor, it implements the steps of the above fault diagnosis method. This computer-readable storage medium has all the beneficial effects of the above fault diagnosis method and will not be elaborated here in the present application.

[0091] According to the sixth aspect of the present application, embodiments of the present application also provide a vehicle, which includes the above fault diagnosis system, controller, or computer-readable storage medium. This vehicle has all the above beneficial effects and will not be elaborated here in the present application.

[0092] According to the seventh aspect of the present application, embodiments of the present application also provide a computer program product, including a computer program, which when executed by a processor, implements the above fault diagnosis method and has all the beneficial effects of the above fault diagnosis method. This will not be elaborated here in the present application.

[0093] The device embodiments described above are only illustrative. The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed to multiple network modules. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. A person of ordinary skill in the art can understand and implement it without creative labor.

[0094] Through the specific descriptions of the above embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, it can also be implemented by hardware. Based on such an understanding, the above technical solutions, in essence, or the parts that contribute to the prior art can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, and the storage medium includes read-only memory (ROM), random access memory (RAM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), one-time programmable read-only memory (OTPROM), electrically-erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc memories, magnetic disk memories, tape memories, or any other computer-readable medium capable of carrying or storing data.

[0095] It should be noted that the computer program codes required for the operations of each part of this specification can be written in any one or more programming languages, including object-oriented programming languages such as Java, Scala, Smalltalk, Eiffel, JADE, Emerald, C++, C#, VB.NET, Python, etc., conventional procedural programming languages such as C language, Visual Basic, Fortran2003, Perl, COBOL 2002, PHP, ABAP, dynamic programming languages such as Python, Ruby, and Groovy, or other programming languages. This program code can run entirely on a computer (PC, embedded intelligent device, etc.), or run as an independent software package on the user's computer, or part of it runs on the user's computer and part runs on a remote computer, or runs entirely on a remote computer or server. In the latter case, the remote computer can be connected to the user's computer in any network form, such as a local area network (LAN) or a wide area network (WAN), or connected to an external computer (for example, through the Internet), or in a cloud computing environment, or used as a service such as software as a service (SaaS).

[0096] Finally, it should be noted that what is disclosed by a fault diagnosis method and device disclosed in the embodiments of the present application is only the preferred embodiments of the present application, and is only used to illustrate the technical solutions of the present application, rather than limiting it; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions recorded in the foregoing embodiments, or perform equivalent replacements on some of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A fault diagnosis method, characterized in that, The method includes: In response to a diagnostic instruction, the first vehicle-mounted unit sends a diagnostic requirement to the second vehicle-mounted unit; Receives a diagnostic response related to the second vehicle-mounted unit to parse a diagnostic result according to the diagnostic response.

2. The fault diagnosis method according to claim 1, wherein The diagnostic requirements include: electronic controller diagnostic requirements, microcontroller diagnostic requirements, system-on-chip diagnostic requirements, and display diagnostic requirements.

3. The fault diagnosis method according to claim 1, wherein At least one of the first vehicle-mounted unit and the second vehicle-mounted unit is a vehicle-mounted host.

4. The fault diagnosis method according to claim 3, wherein, The vehicle-mounted host includes one or more of a central control vehicle-mounted host, a co-pilot vehicle-mounted host, a rear-row vehicle-mounted host, a left rear cockpit vehicle-mounted host, a right rear cockpit vehicle-mounted host, and a ceiling-mounted vehicle-mounted host.

5. The fault diagnosis method according to any one of claims 1-4, characterized in that, The "in response to a diagnostic instruction" includes: In response to a diagnostic instruction triggered by a user on the display interface of the first vehicle-mounted unit.

6. The fault diagnosis method according to claim 1, wherein The method further includes: Repairing a fault of the second vehicle-mounted unit whose diagnostic result indicates a fault state.

7. The fault diagnosis method according to claim 6, wherein When both the first vehicle-mounted unit and the second vehicle-mounted unit are vehicle-mounted hosts, the repairing a fault of the second vehicle-mounted unit whose diagnostic result indicates a fault state includes: If the diagnostic result indicates that the MCU of the second vehicle-mounted unit is abnormal, the first vehicle-mounted unit sends an MCU restart instruction to the second vehicle-mounted unit; If the diagnostic result indicates that the SOC of the second vehicle-mounted unit is abnormal, the first vehicle-mounted unit sends an SOC restart instruction to the second vehicle-mounted unit.

8. The fault diagnosis method according to claim 7, characterized in that, Before the first vehicle-mounted unit sends an SOC restart instruction to the second vehicle-mounted unit, the method further includes: The first vehicle-mounted unit controls the second vehicle-mounted unit to enter a memory dump mode.

9. The fault diagnosis method according to claim 1, wherein The "parsing a diagnostic result according to the diagnostic response" includes: The first vehicle-mounted unit parses the diagnostic response based on a local fault diagnosis model to obtain a diagnostic result.

10. The fault diagnosis method according to claim 9, wherein The method further includes: The local fault diagnosis model is obtained by compressing a cloud fault diagnosis model trained in the cloud.

11. The fault diagnosis method according to claim 10, wherein, The compression method includes at least one of model pruning and model quantization.

12. The fault diagnosis method according to any one of claims 9-11, characterized in that, The method further includes: the first vehicle-mounted unit sends the diagnostic result to the cloud to enable the cloud to update the cloud fault diagnosis model.

13. A fault diagnosis method, characterized in that The method includes: The second vehicle-mounted unit responds to the diagnostic requirement of the first vehicle-mounted unit and sends a diagnostic response to the first vehicle-mounted unit, so that the first vehicle-mounted unit parses the diagnostic result according to the diagnostic response.

14. A fault diagnosis system, characterized in that, The diagnostic system includes at least a first vehicle-mounted unit and a second vehicle-mounted unit, The first vehicle-mounted unit is used to implement the method according to any one of claims 1-12; The second vehicle-mounted unit is used to implement the method according to claim 13.

15. A controller, characterized in that, It includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor. When the program or instruction is executed by the processor, the method according to any one of claims 1-13 is implemented.

16. A computer-readable storage medium, characterized in that, A computer program or instruction is stored in the computer-readable storage medium. When the computer program runs, the method according to any one of claims 1-13 is implemented.

17. A vehicle, characterized in that, Comprising the fault diagnosis system according to claim 14, or the controller according to claim 15, or the computer-readable storage medium according to claim 16.

18. A computer program product, characterized in that, Comprising a computer program or instructions which, when executed by a processor, implement the steps of the method according to any one of claims 1 to 13.