Fault diagnosis method, device and equipment, vehicle and medium

By reading the vehicle event diagnosis marks and determining the fault code, and combining the cumulative generation times and the number of driving cycles for fault diagnosis, the problems of rough and misjudgment of fault diagnosis in the existing technology are solved, and the accuracy of vehicle fault diagnosis is improved and efficiency.

CN118938872APending Publication Date: 2024-11-12格至达智能科技(江苏)有限公司
View PDF 0 Cites 3 Cited by

Patent Information

Application Number
CN202411148248.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-21
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

The existing vehicle fault diagnosis methods are relatively rough, which can easily lead to misjudgment, resulting in diagnostic accuracy and inefficient efficiency.

Method used

By reading the identifier of the event diagnosis mark of the target vehicle, the target fault code is determined, and fault diagnosis is performed based on the accumulated generation times and the number of driving cycles, the accuracy and efficiency of diagnosis are improved.

Benefits of technology

It improves the accuracy of vehicle fault diagnosis, reduces the probability of misjudgment, improves the efficiency of fault diagnosis, and can more accurately reflect the frequency and possibility of faults.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118938872A_ABST
    Figure CN118938872A_ABST
Patent Text Reader

Abstract

The invention discloses a fault diagnosis method, device and equipment, a vehicle and a medium. The method comprises the following steps: reading an identification symbol of an event diagnosis flag bit of a target vehicle; determining a target fault code generated by the target vehicle in response to the condition that the identifier symbol is the preset fault identifier; counting the cumulative generation frequency of the same target fault code of the target vehicle and the driving cycle period number of the target vehicle; and performing fault diagnosis on the target vehicle according to the accumulated generation frequency and the driving cycle period number. In the technical scheme of the embodiment of the invention, the cumulative generation frequency is combined with the driving cycle period number, the occurrence frequency of the fault corresponding to the target fault code in one or more driving cycle periods is explained, the possibility of the fault of the target vehicle can be accurately reflected, the vehicle fault diagnosis accuracy is improved, and the vehicle fault diagnosis efficiency is improved. And the improvement of the accuracy is also beneficial to reducing the probability of fault misjudgment of the vehicle, so that the efficiency of vehicle fault diagnosis is also improved to a certain extent.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of smart vehicle technology, and in particular to a fault diagnosis method, device, equipment, vehicle and medium. Background Art

[0002] With the development of society and the continuous iteration of technology, smart vehicles have entered thousands of households. On the one hand, smart vehicles bring users many novel, convenient and more stable functions, allowing users to enjoy a more comfortable driving and riding experience; but on the other hand, the basis for supporting these smart functions also requires the vehicle itself to have a high degree of stability. Therefore, timely detection of vehicle fault information has become one of the research focuses of relevant technicians.

[0003] Currently, vehicle fault diagnosis generally involves collecting information through various sensors and making fault judgments according to established rules. However, such diagnostic methods are relatively crude and prone to misjudgment, which reduces the accuracy of fault diagnosis and indirectly leads to low efficiency in vehicle diagnosis. Summary of the invention

[0004] The present application provides a fault diagnosis method, apparatus, device, vehicle and medium to improve the efficiency and accuracy of fault diagnosis.

[0005] According to one aspect of the present application, a fault diagnosis method is provided, the method comprising:

[0006] Read the identification symbol of the event diagnosis flag of the target vehicle;

[0007] In response to the identification symbol being a preset fault identification, determining a target fault code generated by the target vehicle;

[0008] Count the cumulative number of times the same target fault code of the target vehicle is generated, as well as the number of driving cycles of the target vehicle;

[0009] Fault diagnosis is performed on the target vehicle based on the cumulative generation times and the number of driving cycles.

[0010] According to another aspect of the present application, a fault diagnosis device is provided, the device comprising:

[0011] A flag reading module is used to read the identification symbol of the event diagnosis flag of the target vehicle;

[0012] a fault code determination module, for determining a target fault code generated by a target vehicle in response to the identification symbol being a preset fault identification;

[0013] An information statistics module is used to count the cumulative number of times the same target fault code of the target vehicle is generated, and the number of driving cycles of the target vehicle;

[0014] The fault diagnosis module is used to perform fault diagnosis on the target vehicle according to the cumulative generation times and the number of driving cycle periods.

[0015] According to another aspect of the present application, an electronic device is provided, the electronic device comprising:

[0016] at least one processor; and

[0017] a memory communicatively connected to the at least one processor; wherein,

[0018] The memory stores a computer program that can be executed by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the fault diagnosis method described in any embodiment of the present application.

[0019] According to another aspect of the present application, a vehicle is provided, wherein the vehicle is provided with an electronic device as provided in an embodiment of the present application, so as to implement the fault diagnosis method provided in any embodiment of the present application.

[0020] According to another aspect of the present application, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the fault diagnosis method described in any embodiment of the present application when executed.

[0021] According to another aspect of the present application, a computer program product is provided, the computer program product comprising a computer program, and the computer program, when executed by a processor, implements the fault diagnosis method according to any embodiment of the present application.

[0022] In the technical solution of the embodiment of the present application, fault diagnosis is performed on the target vehicle based on the cumulative number of times a target fault code is generated in the target vehicle and the number of driving cycles of the target vehicle. The cumulative number of occurrences combined with the number of driving cycles indicates how frequently the fault corresponding to the target fault code occurs in one or more driving cycles, and can accurately reflect the possibility of such a fault occurring in the target vehicle, thereby helping the vehicle to determine the fault diagnosis, thereby further improving the accuracy of the vehicle fault diagnosis. The improvement in accuracy helps the vehicle to reduce the probability of misjudgment of faults, thereby improving the efficiency of vehicle fault diagnosis to a certain extent.

[0023] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present application, nor is it intended to limit the scope of the present application. Other features of the present application will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0025] Figure 1 is a flowchart of a fault diagnosis method provided according to Embodiment 1 of the present application;

[0026] Figure 2 is a schematic diagram of fault diagnosis applicable to the second embodiment of the present application;

[0027] Figure 3 is a structural schematic diagram of a fault diagnosis device provided according to Embodiment 3 of the present application;

[0028] Figure 4 It is a structural schematic diagram of an electronic device that implements the fault diagnosis method of an embodiment of the present application. DETAILED DESCRIPTION

[0029] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0030] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0031] Embodiment 1

[0032] Figure 1A flowchart of a fault diagnosis method is provided for the first embodiment of the present application. This embodiment is applicable to the case of performing fault diagnosis on internal equipment of a vehicle. The method can be executed by a fault diagnosis device, which can be implemented in the form of hardware and / or software. The fault diagnosis device can be configured in an electronic device, which can be set in a vehicle. Figure 1 As shown, the method includes:

[0033] S110, reading the identification symbol of the event diagnosis flag of the target vehicle.

[0034] The target vehicle may be any vehicle that needs to be diagnosed for a fault. The event diagnosis flag may be a flag used to characterize the event state of whether an event has occurred, and its identifier may be a number, letter, or any combination representing the occurrence or non-occurrence of the event, for example, 0 or 1, 0 represents that the event has not occurred, and 1 represents that the event has occurred. An event may be an operation or activity triggered by the target vehicle under specific conditions. In the embodiments and implementations of the present application, various types of faults will be used as examples of events for explanation.

[0035] It should be noted that for the identification of vehicle event diagnostic flags, the application layer of the vehicle platform can confirm the status of various events according to a pre-set de-bouncing algorithm (reducing frequent changes in event status due to network delays, system jitter or repeated triggering, etc.), and set flags corresponding to different abnormal situations accordingly; and the bottom layer of the vehicle platform obtains the identification symbols corresponding to these flags for subsequent fault diagnosis.

[0036] S120: In response to the identification symbol being a preset fault identification, determining a target fault code generated by the target vehicle.

[0037] Among them, the preset fault identification can be a symbol corresponding to the abnormal problem in the case of a pre-set identification symbol. For example, as mentioned above, 0 can represent that the abnormal problem does not occur, and 1 can represent that the abnormal problem occurs. It can be understood that the abnormal problem does not mean that the vehicle has a fault, but compared with the normal situation of all parts of the vehicle, all parts beyond the normal range can be regarded as abnormal problems, and the accumulation of abnormal problems may cause the vehicle to fail. The fault code can be a pre-set fault information corresponding to different situations of the indicators of each device in the target vehicle, which can be in the form of a code. The target fault code can be a fault code used for fault judgment in the target vehicle among all fault codes. Exemplarily, when the abnormal problem identification is set from 0 to 1, it means that there is a situation where a hidden fault occurs, and it is necessary to obtain a fault code for fault judgment. For example, the motor controller of the target vehicle is provided with a voltage sensor. When the voltage of the motor controller is monitored to be greater than 16v, the fault code corresponding to the voltage fault is triggered, for example, the flag bit of the voltage fault is set from 0 to 1.

[0038] In an optional embodiment, in response to the identification symbol being a preset fault identification, determining the target fault code generated by the target vehicle may include: in response to the identification symbol being a preset fault identification, obtaining the fault code to be checked of the target vehicle; in response to the fault code to be checked matching any one of the preset fault codes in the fault code screening set of the corresponding vehicle model of the target vehicle, taking the fault code to be checked as the target fault code.

[0039] Among them, the fault code to be checked can be any fault code generated by the target vehicle. It should be noted that the fault code generated by the vehicle can only indicate that some software and hardware of the vehicle have abnormal conditions, but not all abnormal conditions can affect the normal use of the vehicle (that is, not all abnormal conditions need to be identified as faults), and the same fault code is treated differently in different models. There is a situation where fault code X needs to be treated seriously in car A, but X can be used for fault diagnosis in car A, but not in car B, because even if the abnormal condition corresponding to X occurs in car B, it does not affect any normal use of car B. In reality, since the platforms used for the development of different models may be the same or different, the standards for whether the same fault code needs to be detected as a fault in different models may not be the same. If any fault code is detected, a lot of computing resources will be wasted. Therefore, fault codes can be identified for different models.

[0040] The fault code screening set can be a screening condition for fault code identification. The set stores the fault codes that can be used for fault identification corresponding to the target vehicle model. If the fault code to be checked meets any preset fault code in this set, it means that the fault code to be checked can be used to identify the fault of the target vehicle. Therefore, the fault codes to be checked that meet the fault code screening set are used as target fault codes for subsequent fault detection.

[0041] In the above implementation, before fault detection is performed, the fault codes to be detected are first screened to determine the target fault codes that can be used for fault diagnosis and correspond to the model of the target vehicle, thereby reducing the waste of computing resources and helping to improve the efficiency of fault diagnosis. Even if different vehicle products have incompatibility and major maintenance changes due to different development methods, different fault codes can be screened out based on the model information to determine the fault problem that needs to be detected corresponding to the target vehicle, which helps to improve the efficiency and accuracy of fault detection.

[0042] S130: Count the cumulative number of times the same target fault code of the target vehicle is generated, and the number of driving cycles of the target vehicle.

[0043] The cumulative number of times generated may be the number of times the same preset fault code occurs multiple times in the current vehicle. The number of driving cycles may be the number of cycles that occur in the target vehicle during the user's driving. Generally, in new energy vehicles, especially electric vehicles, a vehicle is considered to have completed a driving cycle after it is powered on and off once. Therefore, the number of times the current vehicle is powered on and off during the process of detecting the fault code determines the number of driving cycles of the current vehicle.

[0044] S140: Perform fault diagnosis on the target vehicle according to the accumulated generation times and the driving cycle number.

[0045] It is understandable that during the use of the vehicle, some equipment indicators may occasionally experience abnormal conditions, thereby triggering one or two fault codes to be recorded. However, these small cumulative occurrences do not indicate that the corresponding equipment in the target vehicle has a fault problem that is sufficient to affect the normal driving of the target vehicle.

[0046] Therefore, only when the cumulative number of generation times is large enough can it be explained to a certain extent that the target vehicle may have a fault problem corresponding to the target fault code. Similar to the cumulative number of generation times, the fault code generated by the vehicle in a certain driving cycle does not mean that the target vehicle will have the problem corresponding to the fault code in all driving processes. Therefore, the cumulative number of generation times and the number of driving cycles are combined to determine whether the target vehicle has a fault. For example, when the same fault code occurs more than ten times in three consecutive driving cycles, it can be determined that the vehicle equipment (software and hardware) corresponding to the equipment indicator of the target fault code has a fault problem.

[0047] In an optional implementation, the fault diagnosis of the target vehicle based on the cumulative number of generation times and the number of driving cycle cycles may include: if the cumulative number of generation times is greater than or equal to an intermediate judgment threshold and less than a fault judgment threshold, and the number of driving cycle cycles is one, it is determined that a level one fault occurs in the target vehicle; if the cumulative number of generation times is greater than or equal to the fault judgment threshold and the number of driving cycle cycles reaches the cycle threshold, it is determined that a level two fault occurs in the target vehicle; the severity of the level two fault is higher than the severity of the level one fault; if the cumulative number of generation times is less than the intermediate judgment threshold, it is determined that no fault occurs in the target vehicle.

[0048] Among them, the fault judgment threshold value can be a basis value for judging the cumulative number of occurrences, and the fault judgment threshold value can be a threshold value or an interval value. The cycle threshold value is used as a basis for fault diagnosis based on the number of driving cycle cycles. When the cumulative number of occurrences is greater than or equal to the fault judgment threshold value, and the number of driving cycle cycles reaches the cycle threshold value, the target vehicle is diagnosed to have a secondary fault. It can be understood that the secondary fault is described in the embodiment of the present application as a relatively serious fault situation. In this embodiment, the severity of the secondary fault is higher than the severity of the primary fault. Correspondingly, the primary fault can be a relatively non-serious fault situation. Exemplarily, the primary fault can be a fault type with a relatively small safety hazard that does not affect the normal driving of the vehicle, and the secondary fault can be a fault type with a relatively large safety hazard that is easy to affect the normal driving of the vehicle. The cycle threshold value can be 1. It can be understood that some fault codes occur multiple times in a driving cycle, that is, the fault problem corresponding to the fault code can be considered to be a more serious type, and therefore it is regarded as a secondary fault. Of course, the cycle threshold value can also be greater than 1 (for example, 3), that is, in multiple consecutive driving cycles, a certain fault code occurs multiple times, and the fault problem corresponding to the fault code can also be considered to be a more serious type, and is also regarded as a secondary fault.

[0049] The fault judgment threshold corresponds to a secondary fault, and the intermediate judgment threshold corresponds to a primary fault. The intermediate judgment threshold is less than the fault judgment threshold, and the intermediate judgment threshold can be a basis value for judging relatively minor faults based on the cumulative number of generation times. For example, assuming that the fault judgment threshold is 10 times, the intermediate judgment threshold can be 5 times. Of course, the specific fault judgment threshold and the intermediate judgment threshold can be set by relevant technical personnel according to actual conditions or manual experience, and the embodiments of the present application are not limited here.

[0050] If the cumulative number of generation times is greater than or equal to the intermediate judgment threshold and less than the fault judgment threshold, and the number of driving cycles is one, then it can be considered that the target vehicle has a level 1 fault. It can be understood that if a fault code generated by a device in the target vehicle appears multiple times in a driving cycle, and the cumulative number of generation times reaches the intermediate judgment threshold but does not reach the fault judgment threshold, then the fault corresponding to the fault code can be considered to be a level 2 fault.

[0051] In addition, if the cumulative number of generation times does not exceed the intermediate judgment threshold, it can be considered that the target vehicle has no fault regardless of how many driving cycles are counted.

[0052] In a specific example, taking the motor controller of an electric vehicle as an example, the fault code flag position of the motor controller of the target vehicle is 1 once, which is regarded as a cumulative number of occurrences of the fault code. For example, if the voltage of the motor controller exceeds 16v, the fault code flag position will be triggered to be 1, which corresponds to a cumulative number of occurrences. The fault judgment threshold is pre-set to 10 times, and the intermediate judgment threshold is 5 times. When the cumulative number of times the motor controller fault code is generated does not reach 5 times, it is always determined that the motor controller of the current vehicle does not have a fault or safety hazard that is sufficient to affect the normal driving of the vehicle. When the cumulative number of times the motor controller fault code is generated reaches 5 times (or more than 5 times but less than 10 times), the number of driving cycles of the current vehicle is checked. If the number of driving cycles is 1, it can be determined that the same abnormal problem has occurred 5 times in a driving cycle. In this case, it can be understood that the motor controller has a tendency to turn to a serious fault, which is regarded as a primary fault. When the cumulative generation times of the motor controller reaches 10 times or exceeds 10 times, the driving cycle number of the target vehicle is checked. If the preset cycle threshold (such as 3 cycles) is reached, it is confirmed that the motor controller has generated multiple identical abnormal problems in multiple consecutive cycles. In this case, it is considered that a serious fault has occurred in the motor controller and it is regarded as a secondary fault.

[0053] Of course, there is a special case in the secondary fault, that is, the preset cycle threshold is 1, that is, when the cumulative generation times of the motor controller reaches 10 times or exceeds 10 times, the number of driving cycle cycles checked at this time is 1 (meeting the preset cycle threshold), that is to say, within a driving cycle, a lot of abnormal problems occur, then the situation is even more serious, of course it needs to be regarded as a serious fault.

[0054] In the above implementation, the target fault code is differentiated based on its cumulative number of generation times, and the cumulative number of occurrences in multiple driving cycles is taken into consideration to classify the possible faults of the target vehicle, distinguish between relatively minor primary faults and relatively serious secondary faults, and provide a refined evaluation standard and diagnostic basis for vehicle fault diagnosis, thereby improving the accuracy of vehicle fault diagnosis.

[0055] In an optional implementation, after determining that a primary fault or a secondary fault occurs in the target vehicle, the method may include: acquiring fault environment reference data of the target vehicle; and determining the cause of the primary fault or the secondary fault based on the fault environment reference data.

[0056] Among them, the fault environment reference data can be data recorded when a fault occurs to assist in determining the cause of the fault. These data can be real-time data of various software and hardware when a vehicle fails. For example, when the target vehicle confirms that a primary fault or a secondary fault has occurred, the working status of each component of the vehicle at the time of the fault can be collected in a timely manner, and relevant data of these components can be recorded, such as vehicle speed, voltage, current and temperature of the motor controller, etc. The causes of these faults are determined by analyzing the fault environment reference data. Of course, the method for confirming the cause of the fault can adopt any fault analysis method in the relevant technology, and the embodiments of the present application are not limited to this.

[0057] In a further optional embodiment, determining the cause of a primary fault or a secondary fault based on the fault environment reference data may include: storing the fault environment reference data corresponding to the primary fault as first snapshot information in a temporary memory; when the target vehicle performs a power-off action, storing the first snapshot information in a non-volatile memory, and determining the cause of the primary fault based on the first snapshot information.

[0058] Among them, the snapshot information can be a way to save the fault environment reference data. The fault environment reference data of the first-level fault can be saved as the first snapshot information. Of course, the first snapshot information here is the first type of snapshot information. Correspondingly, the fault environment reference data of the second-level fault can be saved as the second snapshot information. Similarly, the second snapshot information here is the second type of snapshot information. The temporary memory can be a cache possessed by the vehicle itself, which is used to temporarily store relevant data during the use of the vehicle. It can be understood that since the first-level fault is not serious, the first snapshot information of the fault environment data corresponding to the first-level fault when it occurs can be first saved in the temporary memory. When the vehicle performs the power-off action, these first snapshot information are transferred to the non-volatile memory (NVM). Of course, this is done to ensure that the snapshot information in each driving cycle can be effectively retained, so as to continue to obtain and detect fault codes in subsequent driving cycles, as well as to provide reference for the diagnosis of target vehicle faults.

[0059] In another further optional implementation, the method of determining the cause of a primary fault or a secondary fault according to the fault environment reference data may also include: storing the fault environment reference data corresponding to the secondary fault as second snapshot information in a non-volatile memory; and determining the cause of the secondary fault according to the second snapshot information. The cause of a primary fault may be determined according to the first snapshot information by using any fault analysis method in the related art, and the embodiment of the present application does not limit this.

[0060] Unlike the aforementioned level 1 fault, the level 2 fault is a more serious fault, so the corresponding second snapshot information can be temporarily stored in a temporary storage device and then transferred to a non-volatile memory after the vehicle is powered off, or it can be directly stored in a non-volatile memory to prevent any incidents during the use of the vehicle from causing the temporary storage device to fail, so as to ensure that the information of each component of the corresponding vehicle can be fully recorded when a serious fault occurs. Accordingly, in the aforementioned implementation, the first snapshot information is first stored in a temporary storage device, because the level 1 fault is not a serious situation, and the reasonable use of the temporary storage device can reduce the storage pressure on the non-volatile memory. Any fault analysis method in the relevant technology can be used to determine the cause of the level 2 fault based on the second snapshot information, and the embodiments of the present application are not limited to this.

[0061] In the technical solution of the embodiment of the present application, fault diagnosis is performed on the target vehicle based on the cumulative number of times a target fault code is generated in the target vehicle and the number of driving cycles of the target vehicle. The cumulative number of occurrences combined with the number of driving cycles indicates how frequently the fault corresponding to the target fault code occurs in one or more driving cycles, and can accurately reflect the possibility of such a fault occurring in the target vehicle, thereby helping the vehicle to determine the fault diagnosis, thereby further improving the accuracy of the vehicle fault diagnosis. The improvement in accuracy helps the vehicle to reduce the probability of misjudgment of faults, thereby improving the efficiency of vehicle fault diagnosis to a certain extent.

[0062] Embodiment 2

[0063] Figure 2 This is a schematic diagram of fault diagnosis provided in Example 2 of the present application. This example is a preferred implementation method provided on the basis of the above-mentioned examples and implementation methods. Figure 2 As shown, the details are as follows:

[0064] First, obtain the fault codes to be detected of the target vehicle, and determine whether these fault codes to be detected meet the screening range of the target vehicle model, and use the fault codes to be detected that meet the requirements as the target fault codes. Then, count the cumulative occurrence times and driving cycle number of the target fault codes of the target vehicle. It should be noted that the fault information that needs to be detected for different models may be different. In order to prevent misjudgment, first determine whether the fault codes to be detected of the target vehicle currently obtained are consistent with the current model information. It can also be understood as whether these fault codes to be detected are among the detection indicators of the corresponding model of the target vehicle. If it is a fault code for detecting the target vehicle, a subsequent judgment is made. If not, cancel this judgment and obtain other fault codes.

[0065] If the fault code to be checked matches the model information of the target vehicle, it is used as the target fault code to determine the cumulative number of occurrences of the target fault code, X. If X < 5, that is, the cumulative number of occurrences of the fault code is less than 5 times, it is determined that the vehicle has not failed, and the corresponding flag is adjusted (for example, the flag of the vehicle not failing is adjusted to 0) to indicate the safety and normal state of the vehicle.

[0066] If 5≤X<10, that is, the cumulative occurrence of the fault code reaches 5 times, but less than 10 times, then determine whether the current driving cycle number is 1. If the current driving cycle number is 1, it means that the same abnormal situation has occurred more than 5 times in a driving cycle. It can be considered that the target vehicle has a minor fault and has a tendency to develop into a serious fault, which is equivalent to the first-level fault described in the above embodiment. In this case, the reference data such as vehicle speed, voltage, current and temperature of the equipment detected by various sensors of the vehicle are converted into snapshot information for array storage. If the current driving cycle number is not 1, return to the above process and continue to determine the cumulative occurrence of the fault code.

[0067] If X≥10, that is, the cumulative occurrence of the fault code has reached 10 times. In fact, at this time, it can be judged that the device corresponding to the fault code that has appeared more than 10 times has a relatively serious fault, which is equivalent to the second-level fault in the above embodiment. And the judgment can continue in the second-level fault. Figure 2 As shown, when the cumulative occurrence of the fault code reaches 10 times, is the driving cycle number of the target vehicle determined to be 1? If the driving cycle number is 1, it means that the fault code has been repeated more than 10 times in one driving cycle number, the fault condition is serious, and the reference data needs to be saved as snapshot information in time. If the driving cycle number is not 1, continue to determine whether the driving cycle number is equal to N, and N can be pre-set by relevant technical personnel, for example, it can be N=3. Exemplarily, if the driving cycle number is equal to 3, it means that the fault code has appeared more than 10 times in three driving cycle cycles, the fault condition is relatively serious, and the reference data needs to be saved as snapshot information in time. Different snapshot information can be saved in different arrays.

[0068] Then, it is determined whether the target vehicle meets the storage conditions of NVM, that is, whether it meets the conditions for saving these snapshot information to non-volatile memory. If the conditions are met, the snapshot information is saved in non-volatile storage for subsequent reference. If the conditions are not met, the judgment process ends, and all snapshot information is still temporarily saved in the array, waiting for the conditions to be met.

[0069] This condition can be set by relevant technicians, for example, the vehicle power-off is used as this condition for judgment. For example, when the target vehicle performs the power-off operation, all snapshot information is stored in the non-volatile memory. If the vehicle does not perform the power-off operation for a long time, all snapshot information is still temporarily stored in the array.

[0070] Embodiment 3

[0071] Figure 3 This is a schematic diagram of the structure of a fault diagnosis device provided in Example 3 of the present application. Figure 3As shown, the device 300 may include:

[0072] The flag reading module 310 is used to read the identification symbol of the event diagnosis flag of the target vehicle;

[0073] A fault code determination module 320 is used to determine a target fault code generated by a target vehicle in response to the identification symbol being a preset fault identification;

[0074] An information statistics module 330 is used to count the cumulative number of times the same target fault code of the target vehicle is generated, and the number of driving cycles of the target vehicle;

[0075] The fault diagnosis module 340 is used to perform fault diagnosis on the target vehicle according to the accumulated generation times and the driving cycle number.

[0076] In the technical solution of the embodiment of the present application, fault diagnosis is performed on the target vehicle based on the cumulative number of times a target fault code is generated in the target vehicle and the number of driving cycles of the target vehicle. The cumulative number of occurrences combined with the number of driving cycles indicates how frequently the fault corresponding to the target fault code occurs in one or more driving cycles, and can accurately reflect the possibility of such a fault occurring in the target vehicle, thereby helping the vehicle to determine the fault diagnosis, thereby further improving the accuracy of the vehicle fault diagnosis. The improvement in accuracy helps the vehicle to reduce the probability of misjudgment of faults, thereby improving the efficiency of vehicle fault diagnosis to a certain extent.

[0077] In an optional implementation, the fault diagnosis module 340 may include:

[0078] a primary fault determination unit, for determining that a primary fault occurs in the target vehicle if the cumulative number of generation times is greater than or equal to an intermediate determination threshold and less than a fault determination threshold, and the number of driving cycles is one;

[0079] A secondary fault determination unit, for determining that a secondary fault occurs in the target vehicle if the cumulative number of generation times is greater than or equal to a fault judgment threshold and the number of driving cycle periods reaches a cycle threshold; the severity of the secondary fault is higher than the severity of the primary fault;

[0080] The no-fault determination unit is used to determine that the target vehicle has no fault if the cumulative number of generation times is less than an intermediate judgment threshold.

[0081] In an optional implementation, the device 300 may include:

[0082] A reference data acquisition module, used to acquire fault environment reference data of a target vehicle;

[0083] The fault cause determination module is used to determine the fault cause of the primary fault or the secondary fault according to the fault environment reference data.

[0084] In an optional implementation manner, the fault cause determination module may include:

[0085] A temporary storage unit, used to store the fault environment reference data corresponding to the first-level fault as first snapshot information in a temporary storage;

[0086] The primary fault cause determination unit is used to store the first snapshot information in a non-volatile memory when the target vehicle performs a power-off action, and to determine the fault cause of the primary fault based on the first snapshot information.

[0087] In an optional implementation manner, the fault cause determination module may further include:

[0088] A non-volatile storage unit, used for storing the fault environment reference data corresponding to the secondary fault as second snapshot information in the non-volatile memory;

[0089] The second fault cause determination unit is used to determine the fault cause of the secondary fault according to the second snapshot information.

[0090] In an optional implementation, the fault code determination module 320 may include:

[0091] A to-be-detected fault code acquisition unit, used for acquiring the to-be-detected fault code of the target vehicle in response to the identification symbol being a preset fault identification;

[0092] The target fault code determination unit is used to take the fault code to be detected as the target fault code in response to the fault code to be detected being consistent with any preset fault code in the fault code screening set corresponding to the model of the target vehicle.

[0093] The fault diagnosis device provided in the embodiments of the present application can execute the fault diagnosis method provided in any embodiment of the present application, and has the corresponding functional modules and beneficial effects for executing each fault diagnosis method.

[0094] Embodiment 4

[0095] Figure 4A schematic diagram of an electronic device 10 that can be used to implement an embodiment of the present application is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workbenches, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present application described and / or required herein.

[0096] like Figure 4 As shown, the electronic device 10 includes at least one processor 11, and a memory connected to the at least one processor 11, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage unit 18 to the random access memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other through a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0097] A number of components in the electronic device 10 are connected to the I / O interface 15, including: an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a disk, an optical disk, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0098] The processor 11 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 11 executes the various methods and processes described above, such as a fault diagnosis method.

[0099] A vehicle is also provided in an embodiment of the present application. The vehicle may be provided with the above-mentioned electronic device to implement a fault diagnosis method provided in the above-mentioned embodiments and implementation methods.

[0100] In some embodiments, the fault diagnosis method may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the fault diagnosis method described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to perform the fault diagnosis method in any other appropriate manner (e.g., by means of firmware).

[0101] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0102] The computer programs for implementing the methods of the present application may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the computer programs are executed by the processor, the functions / operations specified in the flow charts and / or block diagrams are implemented. The computer programs may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0103] In the context of the present application, a computer readable storage medium may be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, device or equipment. A computer readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, a computer readable storage medium may be a machine readable signal medium. A more specific example of a machine readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0104] To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

[0105] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0106] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.

[0107] The present application also discloses a computer program product, which includes a computer program, and when the computer program is executed by a processor, the computer program implements the fault diagnosis method provided in any embodiment of the present application. The program product and the fault diagnosis method disclosed in each embodiment of the present application belong to the same inventive concept, so they are not described here.

[0108] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps recorded in this application can be executed in parallel, sequentially or in different orders, as long as the expected results of the technical solution of this application can be achieved, and this document is not limited here.

[0109] The above specific implementations do not constitute a limitation on the protection scope of this application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of this application should be included in the protection scope of this application.

Claims

1. A fault diagnosis method, characterized in that: The method comprises: Read the identification symbol of the event diagnosis flag of the target vehicle; In response to the identification symbol being a preset fault identification, determining a target fault code generated by the target vehicle; Counting the cumulative number of times the same target fault code of the target vehicle is generated, and the number of driving cycles of the target vehicle; Fault diagnosis is performed on the target vehicle according to the accumulated generation times and the driving cycle number.

2. The method according to claim 1, characterized in that: The performing fault diagnosis on the target vehicle according to the accumulated generation times and the driving cycle number includes: If the cumulative number of generation times is greater than or equal to the intermediate judgment threshold and less than the fault judgment threshold, and the number of driving cycle periods is one, it is determined that a primary fault occurs in the target vehicle; If the accumulated number of times is greater than or equal to the fault judgment threshold, and the number of driving cycle periods reaches the cycle threshold, it is determined that a secondary fault occurs on the target vehicle; the severity of the secondary fault is higher than the severity of the primary fault; If the cumulative number of generation times is less than the intermediate judgment threshold, it is determined that the target vehicle has not failed.

3. The method according to claim 2, characterized in that After determining that a primary fault or a secondary fault occurs in the target vehicle, the method includes: Acquiring fault environment reference data of the target vehicle; The fault cause of the primary fault or the secondary fault is determined according to the fault environment reference data.

4. The method according to claim 3, characterized in that The determining the fault cause of the primary fault or the secondary fault according to the fault environment reference data includes: The fault environment reference data corresponding to the primary fault is stored in a temporary storage device as first snapshot information; When the target vehicle performs a power-off action, the first snapshot information is stored in a non-volatile memory, and the fault cause of the primary fault is determined based on the first snapshot information.

5. The method according to claim 3, characterized in that: The determining the fault cause of the primary fault or the secondary fault according to the fault environment reference data further includes: The fault environment reference data corresponding to the secondary fault is stored in a non-volatile memory as second snapshot information; A fault cause of the secondary fault is determined according to the second snapshot information.

6. The method according to claim 1, characterized in that In response to the identification symbol being a preset fault identifier, determining a target fault code generated by the target vehicle includes: In response to the identification symbol being the preset fault identifier, obtaining a to-be-detected fault code of the target vehicle; In response to the fault code to be checked being consistent with any one of the preset fault codes in the fault code screening set corresponding to the model of the target vehicle, the fault code to be checked is used as the target fault code.

7. A fault diagnosis device, characterized in that: The device comprises: A flag reading module is used to read the identification symbol of the event diagnosis flag of the target vehicle; a fault code determination module, for determining a target fault code generated by a target vehicle in response to the identification symbol being a preset fault identification; An information statistics module, used to count the cumulative number of times the same target fault code of the target vehicle is generated, and the number of driving cycles of the target vehicle; A fault diagnosis module is used to perform fault diagnosis on the target vehicle according to the accumulated generation times and the driving cycle number.

8. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the fault diagnosis method according to any one of claims 1 to 6 is implemented.

9. A vehicle, characterized in that: The vehicle is provided with an electronic device as claimed in claim 8.

10. A computer-readable storage medium, characterized in that: A computer program is stored thereon, and when the computer program is executed in a computer, the computer is caused to execute and implement the fault diagnosis method as described in any one of claims 1-6.

Citation Information

Cited By

  • Engineering vehicle quality evaluation method, device, equipment and medium

    CN119919019A

  • Vehicle control method, vehicle control device, and vehicle

    CN121232676A

  • Fault recovery method and system, driving equipment and storage medium

    CN121626174A