Automobile fault processing method and device, storage medium and equipment
By classifying and predicting new energy vehicle failures, invalid fault judgments are reduced and fault reading and processing efficiency is improved, the problems of low fault reading efficiency and large computing load in new energy vehicle fault treatment solutions are solved.
Patent Information
- Application Number
- CN202411508042.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-28
- Publication Date
- 2025-02-11
AI Technical Summary
In the new energy vehicle fault treatment solution, the fault reading efficiency is low and the computing load is large, resulting in invalid fault judgment and increased computing load.
By classifying the faults on the target vehicle, multiple fault categories are obtained, and each fault category is prejudged to determine whether there is a fault set. When it is determined that a fault is set, a cycle judgment is performed and the corresponding fault processing action is performed.
Improves the efficiency of fault reading and processing, reduces invalid fault judgment, and reduces operation load.
Smart Images
Figure CN119416090A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of automobile data processing, and in particular to an automobile fault processing method, device, storage medium and equipment. Background Art
[0002] New energy vehicles often encounter some faults during operation. The current fault handling solution for new energy vehicles generally performs real-time cyclic judgment on all defined faults, including faults uploaded from the bottom layer and faults at the application layer. When a fault is judged to be set, the system searches for the corresponding handling measures for the fault through mapping mechanisms such as lookup tables and rule engines, and then activates or calls the corresponding functional modules to perform specific handling measures to eliminate or reduce the impact of the fault. However, in the real-time cyclic judgment process, most faults are actually not set, so invalid fault judgments will occur, resulting in low fault reading efficiency, and a large number of cyclic calculations will also increase the computing load. Summary of the invention
[0003] The purpose of this application is to provide a method, device, storage medium and equipment for handling automobile faults, aiming to solve the problems of low fault reading efficiency and heavy computing load in the fault handling solutions for new energy vehicles in the related art.
[0004] In a first aspect, the present application provides a method for handling automobile faults, comprising: classifying the faults that need to be handled on the target vehicle to obtain multiple fault categories; pre-judging each fault category to determine whether there is a fault position in the fault category; when it is determined that there is at least one fault position in any fault category, cyclically judging the faults contained in the fault category, and executing corresponding fault handling actions according to the cyclic judgment results.
[0005] In the above implementation process, the faults that need to be handled on the target vehicle are classified to obtain multiple fault categories. After that, each fault category is pre-judged to determine whether there is a fault set in each fault category. When it is determined that at least one fault is set in any fault category, the faults contained in the fault category are cyclically judged, and the corresponding fault handling action is performed according to the cyclic judgment result. In this way, by adding classification and pre-judgment of faults in fault reading, invalid fault judgments are reduced, thereby improving the efficiency of fault reading and processing, and at the calculation level, there is no need to cyclically judge whether all faults are set in real time, thereby effectively reducing the calculation load.
[0006] Furthermore, in some examples, it also includes: the multiple fault categories are obtained by classifying the faults that need to be handled on the target vehicle according to preset classification indicators; the preset classification indicators include any one of the following: the function of the fault location, the frequency of the fault, and the severity of the fault.
[0007] In the above implementation process, an optional method for classifying the faults that need to be handled is provided, that is, classification is performed according to the function of the fault occurrence site, the frequency of the fault occurrence, or the severity of the fault.
[0008] Further, in some examples, after determining whether there is a fault set in the fault category, it includes: determining a flag bit corresponding to the fault category according to a pre-judgment result; the flag bit is used to indicate whether there is a fault set in the fault category.
[0009] In the above implementation process, after pre-judgment of each fault category, the corresponding flag bit is output based on the pre-judgment result. In this way, the system can quickly locate the fault category with a fault position according to the flag bit, reduce unnecessary fault judgments, and improve the efficiency of fault detection.
[0010] Further, in some examples, determining the flag bit corresponding to the fault category based on the pre-judgment result includes: if the pre-judgment result shows that all faults included in the fault category are not set, determining the flag bit corresponding to the fault category as a first value; if the pre-judgment result shows that at least one fault in the fault category is set, determining the flag bit corresponding to the fault category as a second value.
[0011] In the above implementation process, when all faults contained in a certain fault category are not set, its flag bit output is a first value, and when one or more faults in a certain fault category are set, its flag bit output is a second value. In this way, an intuitive display of the pre-judgment results of each fault category is achieved.
[0012] Further, in some examples, when it is determined that at least one fault is set in any fault category, a loop judgment is performed on the faults included in the fault category, including: if the flag bit corresponding to any fault category is a second value, start to execute a loop judgment; during the loop judgment process, skip the faults included in the fault category whose flag bit is the first value, and loop judgment is performed on the faults included in the fault category whose flag bit is the second value.
[0013] In the above implementation process, when the flag bit corresponding to any one or more fault categories is output as the second value through the pre-judgment step, the system automatically skips the fault corresponding to the fault category with the flag bit output as the first value during the cyclic judgment according to the flag bit corresponding to each fault category, and directly judges the fault corresponding to the fault category with the flag bit output as the second value. In this way, the number of cycles is effectively reduced.
[0014] Furthermore, in some examples, it also includes: if the flag bits corresponding to all fault categories are the first value, no loop judgment is performed.
[0015] In the above implementation process, when the flag bits corresponding to all fault types are output as the first value through the pre-judgment step, the system does not need to perform cyclic judgment to map the processing measures corresponding to the set faults. In this way, invalid fault judgments are reduced and the computing load is lowered.
[0016] Furthermore, in some examples, it also includes: after executing the corresponding fault handling action, re-pre-judgment of each fault category.
[0017] In the above implementation process, after calling the function module to complete the fault processing, each fault category is pre-judged again, so as to avoid subsequent problems caused by untimely or erroneous status updates, and also to timely discover potential new faults.
[0018] In the second aspect, the present application provides an automobile fault handling device, including: a classification module, used to classify the faults that need to be handled on the target vehicle to obtain multiple fault categories; a judgment module, used to pre-judge each fault category to determine whether there is a fault setting in the fault category; an execution module, used to, when it is determined that there is at least one fault setting in any fault category, perform a cyclic judgment on the faults contained in the fault category, and execute corresponding fault handling actions according to the cyclic judgment results.
[0019] In a third aspect, the present application provides an electronic device, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the method described in any one of the first aspects when executing the computer program.
[0020] In a fourth aspect, the present application provides a computer-readable storage medium, on which instructions are stored. When the instructions are executed on a computer, the computer executes the method as described in any one of the first aspects.
[0021] In a fifth aspect, the present application provides a computer program product, which, when running on a computer, enables the computer to execute the method as described in any one of the first aspects.
[0022] Other features and advantages disclosed in the present application will be described in the following description, or some features and advantages can be inferred or determined without doubt from the description, or can be learned by implementing the above-mentioned technology disclosed in the present application.
[0023] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, preferred embodiments are specifically cited below and described in detail with reference to the attached drawings. BRIEF DESCRIPTION OF THE DRAWINGS
[0024] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments of the present application will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.
[0025] Figure 1 A flowchart of a method for handling automobile faults provided in an embodiment of the present application;
[0026] Figure 2 A schematic diagram of the workflow of a new energy vehicle fault reading and processing solution provided in an embodiment of the present application;
[0027] Figure 3 A block diagram of a vehicle fault handling device provided in an embodiment of the present application;
[0028] Figure 4 A structural block diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0029] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.
[0030] It should be noted that similar reference numerals and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings. At the same time, in the description of this application, the terms "first", "second", etc. are only used to distinguish the description and cannot be understood as indicating or implying relative importance.
[0031] As described in the background technology, the fault handling solutions for new energy vehicles in the related art have the problems of low fault reading efficiency and large computational load. Based on this, the embodiment of the present application provides a new vehicle fault handling solution to solve the above problems.
[0032] Next, the embodiments of the present application are introduced:
[0033] like Figure 1 As shown, Figure 1 The flowchart of a method for handling automobile faults provided in an embodiment of the present application is shown in FIG. The method can be applied to a system on an automobile responsible for reading and handling faults, such as an on-board diagnostic system (OBD).
[0034] The method comprises:
[0035] Step 101: classify the faults that need to be handled on the target vehicle to obtain multiple fault categories;
[0036] The target vehicle mentioned in this step may be a new energy vehicle, such as a pure electric vehicle, a hybrid vehicle, etc. Different from the traditional vehicle fault handling method, the present embodiment adds fault classification to fault reading, classifies various faults that need to be handled on new energy vehicles, and thus generates multiple fault categories.
[0037] In some embodiments, the multiple fault categories mentioned in this step can be obtained by classifying the faults that need to be handled on the target vehicle according to preset classification indicators; the preset classification indicators include any one of the following: the function of the fault location, the frequency of the fault, and the severity of the fault. That is to say, when classifying the fault, it can be classified according to the function of the fault location, that is, according to the functional characteristics of each system and component of the new energy vehicle, the possible faults can be classified. For example, according to the functional classification, single cell fault, battery management system fault, connector fault, motor fault, motor controller fault and other fault categories can be generated, wherein the single cell fault category may include low or high single cell SOC (State Of Charge), excessive battery internal resistance, internal short circuit of the battery, etc., these faults may affect the actual capacity of the battery pack; the battery management system fault category may include communication failure, data acquisition abnormality, etc., these faults may lead to the inability to accurately estimate the battery SOC. Alternatively, the faults can be classified according to their frequency of occurrence to generate multiple fault categories such as high-frequency faults, medium-frequency faults, and low-frequency faults. The faults can also be classified according to their severity to generate multiple fault categories such as minor faults, general faults, serious faults, and fatal faults. During implementation, for different vehicle models and projects, appropriate classification methods can be selected based on the definition of the fault and the needs of actual applications.
[0038] Step 102, pre-judge each fault category to determine whether there is a fault setting in the fault category;
[0039] Fault setting refers to setting a flag in a system or device to indicate the existence of a fault or error state. When the system detects a fault, it will set the flag to the active state so that the system can identify and handle the fault. In the traditional solution, the system collects, analyzes and confirms all fault signals through a loop judgment mechanism. In the scheme of this embodiment, a pre-judgment of the fault is added to the fault reading, that is, before the fault is cyclically judged, each fault category is pre-judged according to the fault classification result. When there is a classification of set faults, the system will perform a cyclic judgment on the faults that need to be handled, thereby improving the efficiency of fault reading and processing. At the operation level, there is no need to cyclically judge whether all faults are set in real time, which can effectively reduce the operation load.
[0040] In some embodiments, this step may include: determining the flag bit corresponding to the fault category according to the pre-judgment result; the flag bit is used to indicate whether there is a fault set in the fault category. That is, after pre-judgment of each fault category, the corresponding flag bit is output based on the pre-judgment result, that is, each fault category corresponds to a flag bit, and the flag bit indicates whether there is a fault set in the corresponding fault category. In this way, the system can quickly locate the fault category with a fault set according to the flag bit, reduce unnecessary fault judgments, and improve the efficiency of fault detection.
[0041] Further, in some embodiments, the aforementioned determination of the flag bit corresponding to the fault category according to the pre-judgment result may include: if the pre-judgment result shows that all faults included in the fault category are not set, the flag bit corresponding to the fault category is determined to be the first value; if the pre-judgment result shows that at least one fault in the fault category is set, the flag bit corresponding to the fault category is determined to be the second value. Take the first value as 0 and the second value as 1 as an example, that is, the flag bit corresponding to the fault category is a binary state. When all faults included in a certain fault category are not set, its flag bit output is 0. When one or more faults in a certain fault category are set, its flag bit output is 1. In this way, an intuitive display of the pre-judgment results of each fault category is achieved. Of course, the first value and the second value here can also be set differently according to the needs of the specific scenario.
[0042] Step 103: When it is determined that at least one fault is set in any fault category, a cyclic judgment is performed on the faults included in the fault category, and a corresponding fault processing action is executed according to the cyclic judgment result.
[0043] This step means: when a fault is set in a certain fault category through pre-judgment, the system performs a cyclic judgment on the faults that need to be handled. During the cyclic judgment, the fault corresponding to the fault category with the fault set is directly judged, and the set fault is read out, and then the corresponding fault handling measures are mapped according to the fault handling definition, and the corresponding functional module is called to complete the fault handling. In this way, the fault handling efficiency is improved.
[0044] In some embodiments, when it is determined that at least one fault is set in any fault category mentioned in this step, the cyclic judgment of the faults contained in the fault category may include: if the flag bit corresponding to any fault category is the second value, start to perform cyclic judgment; during the cyclic judgment process, skip the faults contained in the fault category whose flag bit is the first value, and cyclically judge the faults contained in the fault category whose flag bit is the second value. That is to say, when the flag bit corresponding to any one or more fault categories is output as 1 through the pre-judgment step, the system automatically skips the fault corresponding to the fault category with the output flag bit of 0 during the cyclic judgment according to the flag bit corresponding to each fault category, and directly judges the fault corresponding to the fault category with the output flag bit of 1. In this way, the number of cycles is effectively reduced.
[0045] Furthermore, in some embodiments, it further includes: if the flag bits corresponding to all fault categories are the first value, no loop judgment is performed. That is, when the flag bits corresponding to all fault categories are output as 0 through the pre-judgment step, the system does not need to perform loop judgment to map the processing measures corresponding to the set faults. In this way, invalid fault judgments are reduced and the computing load is reduced.
[0046] In addition, in some embodiments, it further includes: after executing the corresponding fault handling action, re-pre-judging each fault category. That is to say, after the system calls the function module to complete the fault handling, the status of each fault may change. Therefore, the system re-pre-judgments each fault category, so as to avoid subsequent problems caused by untimely or incorrect status updates, and also timely discover potential new faults.
[0047] In the embodiment of the present application, the faults that need to be handled on the target vehicle are classified to obtain multiple fault categories. After that, each fault category is pre-judged to determine whether there is a fault set in each fault category. When it is determined that at least one fault is set in any fault category, the faults contained in the fault category are cyclically judged, and the corresponding fault handling actions are performed according to the cyclic judgment results. In this way, by adding classification and pre-judgment of faults in fault reading, invalid fault judgments are reduced, thereby improving the efficiency of fault reading and processing, and at the calculation level, there is no need to cyclically judge whether all faults are set in real time, thereby effectively reducing the calculation load.
[0048] In order to explain the solution of this application in more detail, a specific embodiment is introduced below:
[0049] This embodiment provides a new energy vehicle fault reading and processing solution. The workflow of this embodiment is as follows: Figure 2 As shown, including:
[0050] S201, classifying faults on the new energy vehicle that need to be handled;
[0051] Specifically, the system can be classified according to function, or according to the frequency of fault occurrence, or according to the severity of the fault. Different models and projects need to choose the appropriate classification method based on the definition of the fault and the actual application requirements;
[0052] S202, for each category, pre-judge the faults included in the category, and output a flag of the pre-judgement result. Specifically, if none of the faults included in the category is set, the flag is output as 0; if one or more faults in the category are set, the flag is output as 1;
[0053] S203, determine whether there is a category with a flag bit of 1, if yes, execute S204, otherwise execute S206;
[0054] S204, performing cyclic judgment on the faults that need to be handled, automatically skipping the faults corresponding to the categories with the output flag bit of 0 during the cyclic judgment, and directly judging the faults corresponding to the categories with the output flag bit of 1;
[0055] S205, according to the result of the judgment in S204, read out the set fault, then map out the fault handling measure according to the fault handling definition, and call the corresponding function module to execute the fault handling measure;
[0056] S206: Do not execute loop judgment.
[0057] The scheme of this embodiment adds fault classification and pre-judgment to fault reading. Only when there is a classification of set faults will the faults be cyclically judged and mapped to corresponding fault processing actions, thereby improving the efficiency of fault reading and processing. At the operation level, there is no need to cyclically judge whether all faults are set in real time, thereby effectively reducing the operation load.
[0058] Corresponding to the embodiments of the aforementioned method, the present application also provides embodiments of a vehicle fault handling device and a terminal used therein:
[0059] like Figure 3 As shown, Figure 3: is a block diagram of a vehicle fault processing device provided in an embodiment of the present application, the device comprising:
[0060] A classification module 31 is used to classify the faults that need to be handled on the target vehicle to obtain multiple fault categories;
[0061] A judgment module 32, used to pre-judge each fault category and determine whether there is a fault setting in the fault category;
[0062] The execution module 33 is used to perform cyclic judgment on the faults included in any fault category when it is determined that at least one fault is set in any fault category, and execute corresponding fault processing actions according to the cyclic judgment result.
[0063] The implementation process of the functions and effects of each module in the above-mentioned device is specifically described in the implementation process of the corresponding steps in the above-mentioned method, which will not be repeated here.
[0064] This application also provides an electronic device, see Figure 4 , Figure 4 A block diagram of an electronic device provided in an embodiment of the present application. The electronic device may include a processor 410, a communication interface 420, a memory 430, and at least one communication bus 440. The communication bus 440 is used to realize direct connection and communication between these components. The communication interface 420 of the electronic device in the embodiment of the present application is used to communicate signaling or data with other node devices. The processor 410 may be an integrated circuit chip with signal processing capabilities.
[0065] The processor 410 mentioned above can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or the processor 410 can also be any conventional processor, etc.
[0066] The memory 430 may be, but is not limited to, a random access memory (RAM), a read only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electric erasable programmable read-only memory (EEPROM), etc. The memory 430 stores computer-readable instructions. When the computer-readable instructions are executed by the processor 410, the electronic device can execute the above-mentioned Figure 1 The method embodiment involves various steps.
[0067] Optionally, the electronic device may further include a storage controller and an input / output unit.
[0068] The memory 430, storage controller, processor 410, peripheral interface, input and output unit components are directly or indirectly electrically connected to each other to achieve data transmission or interaction. For example, these components can be electrically connected to each other via one or more communication buses 440. The processor 410 is used to execute executable modules stored in the memory 430, such as software function modules or computer programs included in the electronic device.
[0069] The input and output unit is used to provide users with the task creation and to create a start optional time period or preset execution time for the task to realize the interaction between the user and the server. The input and output unit can be, but is not limited to, a mouse and a keyboard.
[0070] Understandably, Figure 4 The structure shown is for illustration only, and the electronic device may also include Figure 4 More or fewer components as shown, or with Figure 4 Different configurations shown. Figure 4 Each component shown in the figure can be implemented by hardware, software or a combination thereof.
[0071] An embodiment of the present application further provides a storage medium having instructions stored thereon. When the instructions are run on a computer, the computer program is executed by a processor to implement the method described in the method embodiment. To avoid repetition, the method will not be described here.
[0072] The present application also provides a computer program product, which, when executed on a computer, enables the computer to execute the method described in the method embodiment.
[0073] In several embodiments provided in the present application, it should be understood that the disclosed devices and methods can also be implemented in other ways. The device embodiments described above are merely schematic. For example, the flowcharts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the devices, methods and computer program products according to multiple embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of a code, and the module, a program segment or a part of a code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of boxes in the block diagram and / or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.
[0074] In addition, the functional modules in the various embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
[0075] If the functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium, including several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
[0076] The above description is only an embodiment of the present application and is not intended to limit the scope of protection of the present application. For those skilled in the art, the present application may have various changes and variations. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application should be included in the scope of protection of the present application. It should be noted that similar reference numerals and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in the subsequent drawings.
[0077] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.
[0078] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.
Claims
1. A method for handling automobile failure, characterized in that: include: Classify the faults that need to be handled on the target vehicle to obtain multiple fault categories; Pre-judgment is performed on each fault category to determine whether there is a fault setting in the fault category; When it is determined that at least one fault is set in any fault category, a cyclic judgment is performed on the faults included in the fault category, and a corresponding fault processing action is executed according to the cyclic judgment result.
2. The method according to claim 1, characterized in that The multiple fault categories are obtained by classifying the faults that need to be handled on the target vehicle according to preset classification indicators; the preset classification indicators include any one of the following: The function of the fault location, the frequency of the fault, and the severity of the fault.
3. The method according to claim 1, characterized in that After determining whether there is a fault setting in the fault category, the method further comprises: The flag bit corresponding to the fault category is determined according to the pre-judgment result; the flag bit is used to indicate whether there is a fault set in the fault category.
4. The method according to claim 3, characterized in that The determining, according to the pre-judgment result, a flag bit corresponding to the fault category includes: If the pre-judgment result shows that all faults included in the fault category are not set, the flag bit corresponding to the fault category is determined to be a first value; If the pre-judgment result shows that at least one fault is set in the fault category, the flag bit corresponding to the fault category is determined to be a second value.
5. The method according to claim 4, characterized in that When it is determined that at least one fault is set in any fault category, a cyclic judgment is performed on the faults included in the fault category, including: If the flag bit corresponding to any fault category is the second value, a loop judgment is started; In the cyclic determination process, the faults included in the fault category whose flag bit is the first value are skipped, and the faults included in the fault category whose flag bit is the second value are cyclically determined.
6. The method according to claim 5, characterized in that Also includes: If the flag bits corresponding to all fault types are the first value, the loop judgment is not performed.
7. The method according to claim 1, characterized in that Also includes: After executing the corresponding fault handling actions, pre-judge each fault category again.
8. An automobile fault handling device, characterized in that: include: A classification module is used to classify the faults that need to be handled on the target vehicle to obtain multiple fault categories; A judgment module, used to pre-judge each fault category and determine whether there is a fault setting in the fault category; The execution module is used to perform cyclic judgment on the faults contained in any fault category when it is determined that at least one fault is set in any fault category, and execute corresponding fault processing actions according to the cyclic judgment result.
9. A computer-readable storage medium, characterized in that: A computer program is stored thereon, and when the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.
10. An electronic device, characterized in that: The method comprises a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the method according to any one of claims 1 to 7 is implemented.