Battery fault diagnosis method, device and vehicle

Abstract

The application provides a battery fault diagnosis method and device and a vehicle. After a single fault of a vehicle-side battery is detected, the fault push accuracy and coverage are further upgraded through increased filtering conditions and mutual exclusion logic. If additional diagnosis passes, a combined fault is pushed, and the combined fault is re-diagnosed according to a first occurrence time. After re-diagnosis, the re-diagnosis result is pushed. The re-diagnosis improves the accuracy of fault diagnosis, which is beneficial to improving the timeliness of optimal allocation and processing of after-sales, quality, market, and R&D personnel resources, and significantly reduces after-sales and maintenance costs.

Description

Battery fault diagnosis methods, devices and vehicles Technical Field

[0001] This application relates to the field of vehicle technology, and in particular to a battery fault diagnosis method, device, and vehicle. Background Technology

[0002] Because fault diagnosis related to battery safety often involves multiple manifestations, adopting a single fault handling measure is likely to result in a high false alarm rate, creating excessive redundant workload for technicians, increasing remote / on-site costs for after-sales personnel, and incurring expenses for customers such as on-site visits and towing. Therefore, how to reduce the false alarm rate caused by a single fault handling measure is an urgent problem to be solved. Summary of the Invention

[0003] In view of this, the purpose of this application is to propose a battery fault diagnosis method, device and vehicle to solve the problem of high false alarm rate caused by single fault handling measures.

[0004] To achieve the above objectives, the first aspect of this application provides a battery fault diagnosis method, comprising:

[0005] In response to the detection of a single fault in the vehicle-side battery, determine the first occurrence time of the single fault;

[0006] Identify the single associated fault that is related to the single fault;

[0007] Determine the second occurrence time of the single associated fault;

[0008] A combined fault is obtained by combining the single fault and the single associated fault based on the first occurrence time and the second occurrence time.

[0009] A second aspect of this application provides a battery fault diagnosis device, comprising:

[0010] The fault detection module is configured to: in response to detecting a single fault in the vehicle-side battery, determine the first occurrence time of the single fault;

[0011] The fault association module is configured to: identify a single associated fault that is associated with the single fault;

[0012] The time confirmation module is configured to: determine the second occurrence time of the single associated fault;

[0013] The fault combination module is configured to combine the single fault and the single associated fault according to the first occurrence time to obtain a combined fault.

[0014] A third aspect of this application provides a vehicle that includes the battery fault diagnosis device provided in the second aspect.

[0015] As can be seen from the above, the battery fault diagnosis method, device, and vehicle provided in this application can determine the first occurrence time of the single fault and the single associated fault after detecting a single fault in the vehicle battery; then, based on the first occurrence time and the second occurrence time, combine the single fault and the single associated fault to obtain a combined fault; combine the single faults, and delete or not push single faults that cannot be combined, thereby reducing the pressure of fault diagnosis and processing and resource consumption, effectively reducing false alarms, and better alleviating after-sales and market pressure. Attached Figure Description

[0016] To more clearly illustrate the technical solutions in this application or related technologies, the drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0017] Figure 1a is a flowchart of a battery fault diagnosis method according to an embodiment of this application;

[0018] Figure 1b is a flowchart of another battery fault diagnosis method according to an embodiment of this application;

[0019] Figure 2 is a flowchart illustrating the determination of a single associated fault in an embodiment of this application;

[0020] Figure 3 is a flowchart illustrating the determination of combined faults in an embodiment of this application;

[0021] Figure 4 is a flowchart of the additional diagnostics in an embodiment of this application;

[0022] Figure 5 is a flowchart of the verification and diagnosis process according to an embodiment of this application;

[0023] Figure 6 is a schematic diagram of the battery fault diagnosis device according to an embodiment of this application;

[0024] Figure 7 is a schematic diagram of the structure of the electronic device according to an embodiment of this application. Detailed Implementation

[0025] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with specific embodiments and the accompanying drawings.

[0026] It should be noted that, unless otherwise defined, the technical or scientific terms used in the embodiments of this application should have the ordinary meaning understood by one of ordinary skill in the art to which this application pertains. The terms "first," "second," and similar terms used in the embodiments of this application do not indicate any order, quantity, or importance, but are merely used to distinguish different components. Terms such as "comprising" or "including" mean that the element or object preceding the word encompasses the elements or objects listed after the word and their equivalents, without excluding other elements or objects. Terms such as "connected" or "linked" are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. Terms such as "upper," "lower," "left," and "right" are only used to indicate relative positional relationships; when the absolute position of the described object changes, the relative positional relationship may also change accordingly.

[0027] It is important to understand in this article that any number of elements in the accompanying figures is for illustrative purposes and not for limitation, and that any naming is for distinction only and has no limiting meaning.

[0028] Based on the above background description, the following situations also exist in the related technologies:

[0029] The power battery system is one of the core components of an electric vehicle's three-electric system (battery, motor, and electronic control). The Battery Management System (BMS) is closely related to fault management, diagnosis, and vehicle performance and safety. Currently, fault management for automotive battery systems mainly relies on the established vehicle-side BMS fault system and the 18 types of BMS faults that must be uploaded to the cloud platform as stipulated in the national standard GB / T 32960: Technical Specifications for Remote Service and Management Systems for Electric Vehicles. In addition to vehicle-side identification and cloud platform uploading, fault levels are classified and handled according to fault source, triggering conditions, and impact. Meanwhile, after-sales and market quality departments implement corresponding on-site fault handling strategies based on the identified fault levels, which are also used as a reference factor for long-term in-store maintenance plans. However, even after classification, the faults are still considered single faults, and the false alarm rate remains high.

[0030] Based on the source of fault triggering, the BMS fault system is mainly divided into the following categories:

[0031] 1. Battery performance-related faults:

[0032] ① Voltage-related faults: such as individual battery overvoltage faults, battery pack overvoltage faults, individual battery undervoltage faults, battery voltage inconsistency faults, excessive battery voltage difference faults, and battery voltage initialization faults. These faults can be caused not only by battery malfunctions but also by indirect false alarms resulting from problems in the data acquisition circuit, sensors, communication systems, or controllers. Because voltage-related faults significantly impact battery performance and safety, their fault severity is generally high.

[0033] ② Current-related faults: such as battery overcurrent faults, battery current exceeding the range, failure to reduce high-voltage current after a timeout, excessive pre-charge current, excessive charging current, excessive discharging current, and excessive energy recovery current. Besides actual excessive circuit current, these faults may also be caused by indirect false alarms due to problems with the high-voltage circuit Hall sensor, partial connection problems (short circuits, etc.), or relay switch malfunctions. Because current-related faults have a significant impact on battery performance and safety, their fault severity is generally high.

[0034] ③Temperature-related faults: Temperature-related faults mainly include excessive battery temperature difference, excessively high battery temperature, excessively rapid battery temperature rise, and invalid temperature signal. The main causes are not only the actual abnormal increase in temperature at the corresponding location, but also indirect false alarms caused by faults in the temperature sensor NTC itself, the acquisition circuit, and signal communication. Because temperature-related faults have a significant impact on battery performance and safety, their fault level is generally high.

[0035] ④ SOX type: mainly involves the battery's state of charge (SOC), state of health (SOH), and state of function (SOF), such as excessively high SOC, excessively low SOC, SOC calibration failure, and SOC jump failure. In addition to the battery's own SOX problem, it may also be an indirect false alarm caused by communication problems. Since SOX, especially SOC, has a significant impact on battery life and other functions and performance, its fault level is generally high.

[0036] 2. Hardware failure:

[0037] Hardware failures mainly refer to various battery system-related measurement circuit faults, data acquisition disconnection faults, sensor circuit faults, temperature sensing faults, and relay-related short circuit / blocking faults. These are primarily caused by problems with the related acquisition and detection circuits and sensors. False alarms are rare, but their correlation with battery safety is low, and their fault severity is generally low.

[0038] 3. Communication-related faults:

[0039] Communication-related faults mainly refer to communication problems related to the reception of signals by various controllers, such as BMS_FD communication failure, HVC communication failure, fast charging CML message timeout and message loss failure, controller BXO message timeout and loss failure, etc. These are usually recoverable, directly related to safety, and generally have a relatively low fault level.

[0040] 4. High-voltage safety fault:

[0041] High-voltage safety typically refers to collision faults, insulation faults, thermal runaway faults, etc., which are usually directly related to battery system safety. They are generally the highest level (such as thermal runaway faults), and the handling measures are more stringent. False alarms are rare, and the triggering frequency is low.

[0042] Some of the aforementioned fault types have a high false alarm rate. However, fault diagnosis related to battery safety often involves more than one manifestation. Adopting a single fault handling measure may result in excessive redundant workload for technicians due to the high false alarm rate. Therefore, further refined secondary processing of the BMS fault system is needed. This includes adding different fault combinations with corresponding mutual exclusion logic, combination duration limits, and logic for combined fault overlap times. This would involve targeted fault reporting that is more directly related to real battery safety failure scenarios, reducing the false alarm rate and serving as an effective supplement to high-level faults such as thermal runaway.

[0043] Based on the above approach, the battery fault diagnosis method provided in this application can determine the first occurrence time of the detected single fault and the associated single fault after detecting a single fault in the vehicle battery. Then, it combines the single fault and the associated single fault based on the first and second occurrence times to obtain a combined fault. Single faults are combined, and those that cannot be combined are deleted, reducing the pressure and resource consumption of fault diagnosis and processing, effectively reducing false alarms, and better alleviating after-sales and market pressure. Next, the expected controller state corresponding to the combined fault is determined, and additional diagnosis is performed on the combined fault based on the expected controller state. The accuracy and coverage of fault push are further improved by adding filtering conditions and mutual exclusion logic. If the additional diagnosis passes, the combined fault is pushed, and a verification diagnosis is performed on the combined fault based on the first occurrence time. After the verification diagnosis, the verification result is pushed. Improving the accuracy of fault diagnosis through verification diagnosis helps to improve the optimal allocation and timeliness of resources for after-sales, quality, market, and R&D personnel, significantly reducing after-sales and maintenance costs.

[0044] It can be seen that the battery fault diagnosis method provided in this application optimizes the fault maintenance system and after-sales processing system without increasing hardware resources, improves the accuracy of fault reporting, facilitates the optimal allocation of resources and timely handling of after-sales, quality, market, and R&D personnel, and has the potential for continuous upgrades, making it suitable for long-term maintenance. It can be transferred to the after-sales market service system in the future to complete the closed loop of market issues.

[0045] In some embodiments, the battery fault diagnosis method provided in this application is preferentially executed in the cloud. Execution in the cloud reduces resource consumption on the vehicle side while allowing for more accurate fault diagnosis and classification from the underlying logic of the module, performed by the cloud model immediately. Execution on the vehicle side is also an option, and is not limited here. Specifically, as shown in Figure 1a, the battery fault diagnosis method includes:

[0046] Step 101: In response to the detection of a single fault in the vehicle-side battery, determine the first occurrence time of the single fault detection.

[0047] In practice, the vehicle-side battery management system monitors the vehicle battery's operating information in real time via the CAN bus. When the vehicle-side battery management system detects an abnormal signal in the battery's operating information, it generates a corresponding single fault signal. Then, according to the requirements of the Telematics Service Provider (TSP), the battery management system forwards the single fault information to the remote communication terminal (Telematics Box, T-BOX). The T-BOX sends the received single fault information to the cloud platform. At this point, the cloud platform detects the single fault in the vehicle-side battery and takes the time of occurrence of this single fault as the first occurrence time. Furthermore, since the transmission process before different single faults are detected is the same, the time consumed during the transmission of different faults is almost the same. Therefore, the time of detection of the single fault can also be taken as the first occurrence time, without any limitation.

[0048] It should be noted that the single faults in the embodiments of this application are generally low-level and medium-level faults. Because there are many types and numbers of low- and medium-level faults, the false alarm rate is relatively high. The battery fault diagnosis method provided in the embodiments of this application has a significant effect on improving the false alarm rate. High-level faults have stricter handling measures and generally rarely produce false alarms. Therefore, for high-level faults such as thermal runaway faults, which are almost the highest level, it is possible to choose not to use the battery fault diagnosis method provided in the embodiments of this application, or to choose to use the battery fault diagnosis method provided in the embodiments of this application to further reduce its false alarm rate; no limitation is made here.

[0049] Step 102: Identify the single associated fault that is linked to the single fault.

[0050] In practice, due to the numerous types and levels of single faults, there are many false alarms. Fault diagnosis, which is crucial for battery safety, often involves more than one manifestation. Adopting a single fault handling measure may result in a high false alarm rate and excessive workload for technicians. Therefore, the BMS fault system needs further refined secondary processing to increase the combinations of different fault types. Thus, after identifying a single fault, it is necessary to further identify at least one single associated fault that can be combined with it. For example, if the single fault is a partial voltage-related fault, the single associated fault could be an excessively rapid temperature rise fault; if the single fault is a voltage-related fault, the single associated fault could be an excessively high temperature fault; if the single fault is a battery short circuit fault, the single associated fault could be a battery short circuit fault, a data acquisition line breakage fault, or an excessively rapid temperature rise fault.

[0051] Step 103: Determine the second occurrence time of the single associated fault.

[0052] In practice, after identifying the single associated fault corresponding to the single fault, it is necessary to further determine the second occurrence time of the single associated fault to determine whether the single associated fault can be combined with the single fault. Optionally, the occurrence time of the single associated fault can be used as the second occurrence time; furthermore, since the transmission process before different single faults are detected is the same, the time consumed by different faults during transmission is almost the same, so the detection time of the single associated fault can also be used as the second occurrence time, as long as it is consistent with the method of determining the first occurrence time, and there is no limitation here.

[0053] Step 104: Combine the single fault and the single associated fault based on the first occurrence time and the second occurrence time to obtain the combined fault.

[0054] In practical implementation, since real battery faults in vehicles are often accompanied by combined changes in temperature and voltage status and magnitude, simultaneous superposition and judgment can effectively filter false alarms. Therefore, fault combination is necessary. Verifying the duration of individual faults and associated faults separately according to preset time determination conditions can reduce the possibility of false alarms. Simultaneously, verifying the combination of the first and second occurrence times according to preset time determination conditions checks whether the individual faults and associated faults meet the time conditions for fault combination. After the first and second occurrence times, as well as the individual faults and associated faults, all meet the time confirmation conditions, the individual faults and associated faults are combined based on the first and second occurrence times to obtain the combined fault. Individual faults that cannot be combined are deleted or not pushed. For example, a combined fault of battery pack overheating (level 3) + single cell undervoltage (level 4); or a combined fault of module temperature sensor validity (level 2) + single cell voltage sampling line disconnection; or a combined fault of single cell voltage overheating (level 2) + single cell voltage sampling line disconnection.

[0055] In some embodiments, as shown in FIG1b, after step 104, step 105 is further included: determining the controller desired state corresponding to the combined fault, and performing additional diagnostics on the combined fault based on the controller desired state.

[0056] In practice, when a real battery fault occurs in the vehicle, it is often necessary to simultaneously identify and filter the controller module status. For example, considering the numerous statuses and controller states generated by faults such as charging and discharging at high voltage, this can filter out false alarms caused by issues such as invalid data communication in the initial stage. Therefore, it is necessary to determine the expected controller state corresponding to the combined fault. This expected state is the state of the battery pack controller and the battery management system controller when the real fault corresponding to the combined fault occurs. Then, additional diagnostics are performed on the combined fault based on the expected controller state. If the corresponding expected controller state exists within a certain period after the combined fault occurs, it indicates a high probability of the fault actually occurring, and the combined fault is reported and pushed to the system so that users and after-sales management can understand the specific situation of the fault as soon as possible. If the corresponding expected controller state does not exist within a certain period after the combined fault occurs, it indicates a low probability of the fault actually occurring, and there may be a false alarm. In this case, the combined fault is not reported and pushed temporarily, but the fault detection will continue in the future to reduce the occupation of vehicle-side resources.

[0057] Step 106: In response to the passing of the additional diagnosis, push the combined fault, and perform a review diagnosis on the combined fault according to the first occurrence time, and push the review result after the review diagnosis.

[0058] In practice, if the corresponding expected controller state exists within a certain period of time after a combined fault occurs, it indicates a high probability that the fault has actually occurred. Therefore, a combined fault report is pushed to the system, allowing users and after-sales management to understand the specific situation of the fault immediately. However, the actual fault occurring in the vehicle's battery may be caused by an internal short circuit within the battery itself, or it may be a false alarm due to imperfect signal filtering. This is because there are time intervals in the vehicle's monitoring of the battery-to-battery and battery management system. For some single-frame data, which have extremely short occurrence times, these signals may not be detected when monitoring the vehicle's battery operation information in real time via the CAN bus. However, these extremely short-lived signals are recorded by the vehicle's control software and uploaded to the cloud. Therefore, the cloud can use these single-frame signals to perform a review and diagnosis of the combined fault based on the first occurrence time. After the review and diagnosis, the review results are pushed to the system, further improving the accuracy of combined fault judgment and reducing the false alarm rate.

[0059] In summary, the battery fault diagnosis method provided in this application can combine single faults and single associated faults based on the first and second occurrence times to obtain combined faults. It combines single faults and deletes or does not push single faults that cannot be combined, reducing the pressure and resource consumption of fault diagnosis processing, effectively reducing false alarms, and better alleviating after-sales and market pressure. Then, it performs additional diagnosis on the combined fault based on the expected controller state corresponding to the combined fault; by adding filtering conditions and mutual exclusion logic, it further upgrades the accuracy and coverage of fault push. If the additional diagnosis passes, the combined fault is pushed, and a verification diagnosis is performed on the combined fault based on the first occurrence time. After the verification diagnosis, the verification result is pushed. Improving the accuracy of fault diagnosis through verification diagnosis is beneficial for improving the optimal allocation and timeliness of resources for after-sales, quality, market, and R&D personnel. It further improves the accuracy of combined fault judgment, reduces false alarm rates, and significantly reduces after-sales and maintenance costs.

[0060] In some embodiments, as shown in FIG2, determining a single associated fault related to a single fault includes:

[0061] Step 201: Identify the battery fault corresponding to a single fault.

[0062] In practice, taking a single fault as a battery short circuit fault as an example, the corresponding real fault can be a battery failure fault or a battery smoking fault. This is because a battery short circuit causes the battery to be unable to work properly, resulting in a battery failure fault; or because a battery short circuit causes the battery to burn out and produce white smoke, resulting in a battery smoking fault.

[0063] Step 202: Determine the set of information corresponding to the battery fault.

[0064] In practice, the information set corresponding to a battery fault includes various information related to the battery fault that needs to be monitored in real time, such as temperature and voltage. For example, taking a real battery fault as a battery failure fault, the information set corresponding to a battery failure fault may include: battery temperature, battery temperature change rate, voltage value, voltage change value, whether the acquisition line is broken, etc.

[0065] Step 203: Determine at least one single associated fault in the information set based on the preset association relationship.

[0066] In practice, each piece of information in the information set corresponds to at least one fault. These correspondences are called associations. Therefore, based on these associations, a single associated fault can be determined within the information set. For example, if a sudden increase in the rate of temperature rise is detected in the information set, the single associated fault related to the battery short circuit can be identified as an excessively rapid temperature rise fault; if a certain signal suddenly disappears from the information set, the single associated fault related to the battery short circuit can be identified as a broken acquisition line fault; and if a sudden increase in voltage is detected in the information set, the single associated fault related to the battery short circuit can be identified as an excessively high single-cell voltage fault.

[0067] In some embodiments, as shown in FIG3, a combined fault is obtained by combining a single fault and a single associated fault based on a first occurrence time and a second occurrence time, including:

[0068] Step 301: Determine the combined time interval based on the first occurrence time, and determine whether the second occurrence time is within the combined time interval.

[0069] In some optional embodiments, taking a first occurrence time of 13:45:30 (assuming a detection is performed every 1 second) as an example, the process includes determining a combined time interval based on the first occurrence time and determining whether the second occurrence time is within the combined time interval, including:

[0070] Step 3011: Determine the second duration of the single fault;

[0071] Step 3012: In response to the second duration being greater than or equal to the preset first duration threshold, the combined time interval is determined with the first occurrence time as the interval start point and the preset combined duration as the interval length.

[0072] In practice, the first step is to determine the second duration of the single fault. Since battery faults are generally irreversible and have almost no possibility of self-repair, the detected faults usually last for a relatively long time. Therefore, the first step in reducing the probability of false alarms can be to start with the second duration of the single fault. If the preset first duration threshold is 20 seconds, the second duration is calculated when a single fault is detected. If the signal corresponding to the single fault does not disappear within 20 seconds, that is, the second duration is greater than or equal to the preset first duration threshold, it means that the single fault meets the time confirmation condition for fault combination and can be combined with other faults. If the detected single fault disappears within 20 seconds (the second duration is less than the preset first duration threshold), there is a probability of false alarms if the single fault is combined and reported. Therefore, only all the information corresponding to the single fault is saved for subsequent inspection, and the combination of faults for the single fault is stopped, thereby reducing the false alarm rate.

[0073] Because different fault indication signals usually appear simultaneously when a fault occurs, and the combined duration is generally not too long, under the premise that the signal corresponding to a single fault does not disappear within 20 seconds (i.e., the second duration is greater than or equal to the preset first duration threshold), if the preset combined duration is 60 seconds, taking the first occurrence time of 13:45:30 as the starting point and the preset combined duration of 60 seconds as the interval length, the combined time interval is [13:45:30, 13:46:30]. Single associated faults are detected within this time interval. Only single associated faults within this time interval meet the time confirmation condition for combining single associated faults; that is, a single fault and a single associated fault must be detected simultaneously within 60 seconds for fault combination to occur. Specifically, the time confirmation condition for fault combination is: the duration of both the single fault and the single associated fault must be greater than or equal to 20 seconds (assuming the first time threshold for the single fault and the second time threshold for the single associated fault are both 20 seconds); otherwise, no fault is pushed; and a single fault and a single associated fault must be detected simultaneously within 60 seconds.

[0074] Step 302: In response to the second occurrence time being within the combined time interval, determine the first duration of the single associated fault.

[0075] In practice, if a single associated fault is detected within 60 seconds after a single fault is detected, it can be determined that the second occurrence time is within the combined time interval. At this time, it is necessary to determine whether the second duration of the single associated fault meets the duration requirement in the time confirmation condition. Therefore, if the second occurrence time is within the combined time interval, the first duration of the single associated fault is determined.

[0076] It should be noted that the detection of single associated faults is performed 60 seconds after the first occurrence time because if a single associated fault occurs before a single fault, the occurrence time of the single associated fault needs to be used as the starting point to detect the single fault 60 seconds later. Therefore, when combining any single fault, it is not necessary to check whether there is a corresponding single associated fault in advance.

[0077] Step 303: Determine whether a single associated fault meets the time confirmation condition based on the first duration.

[0078] In some optional embodiments, determining whether a single associated fault meets the time confirmation condition based on a first duration includes:

[0079] Step 3031: Compare the first duration with the preset second duration threshold;

[0080] Step 3032: In response to the first duration being greater than or equal to the second duration threshold, determine that a single associated fault meets the time confirmation condition;

[0081] Step 3033: In response to the first duration being less than the second duration threshold, determine that the single associated fault does not meet the time confirmation condition.

[0082] In practice, if the first duration of a single associated fault is greater than or equal to a preset second duration threshold, the single associated fault is determined to meet the time confirmation condition; if the first duration of a single associated fault is less than the preset second duration threshold, the single associated fault is determined not to meet the time confirmation condition and cannot be combined into a fault group, and its corresponding information is saved.

[0083] For example, if the preset second duration threshold is also 20 seconds, the first duration is calculated when a single associated fault is detected. If the signal corresponding to the single associated fault does not disappear within 20 seconds, that is, the first duration is greater than or equal to the preset second duration threshold, it means that the single associated fault meets the time confirmation condition for fault combination, and subsequent fault combination can be performed. If the detected single associated fault disappears within 20 seconds (the first duration is less than the preset second duration threshold), there will be a high false alarm probability if the single associated fault is combined and reported. Therefore, only all the information corresponding to the single associated fault is saved for subsequent inspection, and fault combination of the single associated fault is stopped to reduce the false alarm rate.

[0084] Step 304: In response to the single associated fault meeting the time confirmation condition, combine the single fault and the single associated fault into a combined fault.

[0085] In practice, if a single associated fault meets the time confirmation condition, it means that the single associated fault meets the time confirmation condition for combining with a single fault, and the single fault and the single associated fault can be combined into a combined fault.

[0086] For example, if a single fault is a battery short circuit fault, and the power supply short circuit lasts for more than 20 seconds, within 60 seconds after the battery short circuit fault occurs, if any of the following faults are detected: a broken acquisition line fault, a rapid temperature rise fault, or an excessively high single cell voltage fault, it can be regarded as a single associated fault. After determining that the duration of the single associated fault exceeds 20 seconds, the single fault and the single associated fault are combined to obtain a combined fault. After initially reducing the false alarm rate by the duration, the probability of false alarms is further reduced by combining faults.

[0087] In some embodiments, as shown in FIG4, additional diagnostics are performed on combined faults based on the desired state of the controller, including:

[0088] Step 401: Detect the actual status of the controller based on the first occurrence time.

[0089] In practice, when a real fault occurs in the vehicle battery, it is often necessary to perform controller status identification and filtering at the same time. This requires determining whether the first occurrence time of the fault combination is within a state where the controller is prone to faults, such as the state that is frequently caused by faults such as charging and discharging at high voltage. Therefore, it is necessary to use the first occurrence time as the center and detect the actual state of the controller within a certain time range to filter out false alarms caused by problems such as invalid data communication in the initial stage.

[0090] Step 402: In response to the controller's actual state being the same as its expected state, confirm that the additional diagnostics have passed.

[0091] In practice, after determining the expected state of the controller corresponding to the combined fault, the expected state is the state that the battery pack controller and the battery management system controller should be in when the actual fault corresponding to the combined fault occurs. Then, additional diagnosis is performed on the combined fault based on the expected state of the controller. If the actual state of the controller detected within a certain period of time when the combined fault occurs is the same as the expected state of the controller, it indicates that the probability of the fault actually occurring is high. The combined fault can be reported and pushed to the system so that users and after-sales management can understand the specific situation of the fault as soon as possible.

[0092] Step 403: In response to the difference between the actual state of the controller and the expected state of the controller, determine that the additional diagnostic has failed.

[0093] In practice, if the actual state of the controller detected within a certain period of time is different from the expected state of the controller, it indicates that the probability of the actual occurrence of the fault is low and there may be false alarms. Therefore, the combined fault will not be reported and pushed temporarily, but the combined fault can be saved for subsequent detection to reduce the occupation of vehicle-side resources.

[0094] In some embodiments, as shown in FIG5, the combined fault is reviewed and diagnosed based on the first occurrence time, including:

[0095] Step 501: Obtain historical monitoring data from the vehicle.

[0096] In practical implementation, based on the time confirmation conditions for combining single faults and single associated faults, it can be understood that both single faults and single associated faults are detected and combined based on signals lasting for a certain period of time. The signal detection time interval is generally 1 second. Therefore, within adjacent 1-second time intervals, there may be single-frame signals with extremely short durations. Taking a power short-circuit fault as an example, its single associated fault is a broken acquisition line fault (a rapid temperature rise fault can also be considered a single associated fault of a power short-circuit fault; however, if the short-circuit location is far from the temperature sensor, both temperature rise and temperature propagation require a certain amount of time, which may result in the inability to detect the rapid temperature rise fault within 60 seconds, thus preventing the combination of single faults; it is also possible that a large voltage may quickly overheat the single fault. (Situations such as a blown body voltage sampling line causing a broken sampling line fault, a short temperature rise time resulting in the temperature not being detected by the temperature sensor, etc.) When the controller is actually in charging state, the combined fault of power short circuit fault and sampling line breakage fault has been pushed. At this time, it is necessary to review and cut off the power short circuit fault. When reviewing, the combined fault has already been reported and pushed, so it is necessary to obtain historical monitoring data from the vehicle to review. Since both power short circuit fault and sampling line breakage fault can be caused by abnormal high voltage, it is possible to select whether there is a single frame signal of abnormal high voltage in the period before the first occurrence time. And this high voltage single frame signal may not be effectively collected due to the signal acquisition interval of the vehicle. Therefore, the combined fault can be reviewed based on this high voltage single frame signal.

[0097] Step 502: Determine the review duration based on a single fault.

[0098] In practice, if the time interval between the occurrence time of the high-voltage single-frame signal and the first occurrence time is relatively large, the verification effect of the high-voltage single-frame signal will be greatly reduced. Therefore, it is necessary to set the verification time. This verification time can vary depending on the single fault. For power supply short circuit faults, the time required for high voltage to cause a power supply short circuit is relatively short. Therefore, the verification time can be set to 10 seconds, and the high-voltage single-frame signal can be detected within 10 seconds.

[0099] Step 503: Determine the review time interval by taking the first occurrence time as the interval end point and the review duration as the interval length.

[0100] In practice, high-voltage single-frame signals generally appear before power short-circuit faults. Therefore, the verification time interval is determined by taking the first occurrence time as the interval end and the verification duration as the interval length. Detecting high-voltage single-frame signals within this verification time interval can effectively improve the accuracy of the verification. For example, taking the first occurrence time of 13:45:30 as the end and the verification duration of 10 seconds as the interval length, the verification time interval is [13:45:20, 13:45:30].

[0101] Step 504: Within the review time interval, check whether the historical monitoring data contains any abnormal signals corresponding to a single fault.

[0102] In practice, during the review time interval [13:45:20, 13:45:30], it is checked whether the historical monitoring data contains an abnormal signal corresponding to a single fault. This abnormal signal can be a high-voltage single-frame signal.

[0103] Step 505: In response to the presence of an abnormal signal, the combined fault is reliably determined as the verification result.

[0104] In practice, if a high-voltage single-frame signal corresponding to a single fault is detected in the historical monitoring data within the review time interval [13:45:20, 13:45:30], the combined fault is reliably determined as the review result, further reducing the false alarm rate of the combined fault.

[0105] Step 506: In response to the absence of abnormal signals, the combined fault is identified as a possible result of the review.

[0106] In practice, if a high-voltage single-frame signal corresponding to a single fault is not detected in the historical monitoring data within the review time interval [13:45:20, 13:45:30], the combined fault is suspected and identified as the review result.

[0107] It should be noted that the method in this embodiment can be executed by a single device, such as a computer or server. The method can also be applied in a distributed scenario, where multiple devices cooperate to complete the task. In such a distributed scenario, one of these devices may execute only one or more steps of the method in this embodiment, and the multiple devices will interact with each other to complete the method described.

[0108] It should be noted that the above description describes some embodiments of this application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in a different order than that shown in the above embodiments and still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require a specific or sequential order to achieve the desired result. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0109] Based on the same inventive concept, corresponding to any of the above embodiments, this application also provides a battery fault diagnosis device.

[0110] Referring to Figure 6, the battery fault diagnosis device includes:

[0111] Fault detection module 10 is configured to: in response to detecting a single fault in the vehicle-side battery, determine the first occurrence time of the single fault.

[0112] The fault association module 20 is configured to: identify a single associated fault that is associated with a single fault;

[0113] The time confirmation module 30 is configured to: determine the second occurrence time of a single associated fault;

[0114] The fault combination module 40 is configured to combine a single fault and a single associated fault based on the first occurrence time and the first occurrence time to obtain a combined fault.

[0115] For ease of description, the above devices are described in terms of function, divided into various modules. Of course, in implementing this application, the functions of each module can be implemented in one or more software and / or hardware.

[0116] The apparatus of the above embodiments is used to implement the corresponding battery fault diagnosis method in any of the foregoing embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0117] Based on the same inventive concept, corresponding to the methods of any of the above embodiments, this application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the battery fault diagnosis method described in any of the above embodiments.

[0118] Figure 7 shows a more specific hardware structure diagram of an electronic device provided in this embodiment. The device may include: a processor 1010, a memory 1020, an input / output interface 1030, a communication interface 1040, and a bus 1050. The processor 1010, memory 1020, input / output interface 1030, and communication interface 1040 are interconnected internally via the bus 1050.

[0119] The processor 1010 can be implemented using a general-purpose CPU (Central Processing Unit), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this specification.

[0120] The memory 1020 can be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory 1020 can store the operating system and other applications. When the technical solutions provided in the embodiments of this specification are implemented by software or firmware, the relevant program code is stored in the memory 1020 and is called and executed by the processor 1010.

[0121] The input / output interface 1030 is used to connect input / output modules to realize information input and output. Input / output modules can be configured as components within the device (not shown in the figure) or externally connected to the device to provide corresponding functions. Input devices may include keyboards, mice, touchscreens, microphones, various sensors, etc., while output devices may include displays, speakers, vibrators, indicator lights, etc.

[0122] The communication interface 1040 is used to connect a communication module (not shown in the figure) to enable communication between this device and other devices. The communication module can communicate via wired means (such as USB, Ethernet cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.).

[0123] Bus 1050 includes a pathway for transmitting information between various components of the device, such as processor 1010, memory 1020, input / output interface 1030, and communication interface 1040.

[0124] It should be noted that although the above-described device only shows the processor 1010, memory 1020, input / output interface 1030, communication interface 1040, and bus 1050, in specific implementations, the device may also include other components necessary for normal operation. Furthermore, those skilled in the art will understand that the above-described device may only include the components necessary for implementing the embodiments of this specification, and not necessarily all the components shown in the figures.

[0125] The electronic devices described above are used to implement the corresponding battery fault diagnosis methods in any of the foregoing embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0126] Based on the same inventive concept, corresponding to the methods of any of the above embodiments, this application also provides a non-transitory computer-readable storage medium storing computer instructions for causing the computer to execute the battery fault diagnosis method as described in any of the above embodiments.

[0127] The computer-readable medium of this embodiment includes permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transfer medium that can be used to store information accessible by a computing device.

[0128] The computer instructions stored in the storage medium of the above embodiments are used to cause the computer to execute the battery fault diagnosis method as described in any of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0129] Those skilled in the art should understand that the discussion of any of the above embodiments is merely exemplary and is not intended to imply that the scope of this application (including the claims) is limited to these examples; within the framework of this application, the technical features of the above embodiments or different embodiments can also be combined, the steps can be implemented in any order, and there are many other variations of different aspects of the embodiments of this application as described above, which are not provided in the details for the sake of brevity.

[0130] Additionally, to simplify the description and discussion, and to avoid obscuring the embodiments of this application, the well-known power / ground connections to integrated circuit (IC) chips and other components may or may not be shown in the provided drawings. Furthermore, the apparatus may be shown in block diagram form to avoid obscuring the embodiments of this application, and this also takes into account the fact that the details of the implementation of these block diagram apparatuses are highly dependent on the platform on which the embodiments of this application will be implemented (i.e., these details should be fully understood by those skilled in the art). While specific details (e.g., circuits) have been set forth to describe exemplary embodiments of this application, it will be apparent to those skilled in the art that the embodiments of this application can be implemented without these specific details or with variations thereof. Therefore, these descriptions should be considered illustrative rather than restrictive.

[0131] Although this application has been described in conjunction with specific embodiments thereof, many substitutions, modifications, and variations of these embodiments will be apparent to those skilled in the art from the foregoing description. For example, other memory architectures (e.g., dynamic RAM (DRAM)) may be used with the embodiments discussed.

[0132] The embodiments of this application are intended to cover all such substitutions, modifications, and variations that fall within the broad scope of the appended claims. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the embodiments of this application should be included within the protection scope of this application.

Claims

1. A battery fault diagnosis method, characterized in that, include: In response to the detection of a single fault in the vehicle-side battery, determine the first occurrence time of the single fault; Identify the single associated fault that is related to the single fault; Determine the second occurrence time of the single associated fault; A combined fault is obtained by combining the single fault and the single associated fault based on the first occurrence time and the second occurrence time, including: in response to the second occurrence time being within the combined time interval and the single associated fault meeting the time confirmation condition, combining the single fault and the single associated fault into the combined fault; wherein the starting point of the combined time interval is the first occurrence time, and the interval length is a preset combined duration; determining the controller expected state corresponding to the combined fault, and performing additional diagnosis on the combined fault based on the controller expected state; in response to the additional diagnosis passing, pushing the combined fault, and performing a review diagnosis on the combined fault based on the first occurrence time, and pushing the review result after the review diagnosis; wherein performing a review diagnosis on the combined fault based on the first occurrence time includes: determining a review time interval with the first occurrence time as the interval end point and the review duration of the single fault as the interval length; when an abnormal signal is detected in the historical monitoring data within the review time interval, the combined fault is reliably determined as the review result.

2. The method according to claim 1, characterized in that, The step of determining the single associated fault includes: determining the battery fault corresponding to the single fault; determining the information set corresponding to the battery fault; and determining at least one single associated fault in the information set according to a preset association relationship.

3. The method according to claim 1, characterized in that, The step of combining the single fault and the single associated fault according to the first occurrence time and the second occurrence time to obtain a combined fault includes: determining a combined time interval according to the first occurrence time, and determining whether the second occurrence time is within the combined time interval; in response to the second occurrence time being within the combined time interval, determining a first duration of the single associated fault; determining whether the single associated fault meets a time confirmation condition according to the first duration; and in response to the single associated fault meeting the time confirmation condition, combining the single fault and the single associated fault into the combined fault.

4. The method according to claim 1, characterized in that, The additional diagnosis of the combined fault based on the expected state of the controller includes: detecting the actual state of the controller based on the first occurrence time; determining that the additional diagnosis passes when the actual state of the controller is the same as the expected state of the controller; and determining that the additional diagnosis fails when the actual state of the controller is different from the expected state of the controller.

5. The method according to claim 1, characterized in that, The step of reviewing and diagnosing the combined fault based on the first occurrence time includes: acquiring historical monitoring data from the vehicle; determining a review duration based on the single fault; determining a review time interval with the first occurrence time as the interval endpoint and the review duration as the interval length; detecting whether the historical monitoring data contains an abnormal signal corresponding to the single fault within the review time interval; in response to the presence of the abnormal signal, determining the combined fault as the review result; and in response to the absence of the abnormal signal, determining the combined fault as the review result.

6. The method according to claim 3, characterized in that, The step of determining the combined time interval based on the first occurrence time includes: determining the second duration of the single fault; in response to the second duration being greater than or equal to a preset first duration threshold, determining the combined time interval with the first occurrence time as the interval start point and the preset combined duration as the interval length.

7. The method according to claim 3, characterized in that, The step of determining whether the single associated fault meets the time confirmation condition based on the first duration includes: comparing the first duration with a preset second duration threshold; determining that the single associated fault meets the time confirmation condition in response to the first duration being greater than or equal to the second duration threshold; and determining that the single associated fault does not meet the time confirmation condition in response to the first duration being less than the second duration threshold.

8. A battery fault diagnosis device, characterized in that, include: The fault detection module is configured to: in response to detecting a single fault in the vehicle-side battery, determine the first occurrence time of the single fault; The fault association module is configured to: determine a single associated fault associated with the single fault; the time confirmation module is configured to: determine a second occurrence time of detecting the single associated fault; The fault combination module is configured to: combine the single fault and the single associated fault according to the first occurrence time to obtain a combined fault, including: in response to the second occurrence time being within the combined time interval and the single associated fault meeting the time confirmation condition, combining the single fault and the single associated fault into the combined fault; wherein, the starting point of the combined time interval is the first occurrence time, and the interval length is a preset combined duration; determining the controller expected state corresponding to the combined fault, and performing additional diagnosis on the combined fault according to the controller expected state; in response to the additional diagnosis passing, pushing the combined fault, and performing a review diagnosis on the combined fault according to the first occurrence time, and pushing the review result after the review diagnosis; wherein, performing a review diagnosis on the combined fault according to the first occurrence time includes: determining a review time interval with the first occurrence time as the interval end point and the review duration of the single fault as the interval length; when an abnormal signal is detected in the historical monitoring data within the review time interval, the combined fault is reliably determined as the review result.

9. A vehicle, characterized in that, Includes the battery fault diagnosis device as described in claim 8.

Images