Battery diagnosis device and battery diagnosis method

CN122603283APending Publication Date: 2026-08-18LG ENERGY SOLUTION LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202580010103.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2024-04-03
Filing Date
2025-03-20
Publication Date
2026-08-18

AI Technical Summary

Technical Problem

在这种收集数据不良的情况下,过热诊断的准确度的下降可能成为问题

Benefits of technology

[0027] According to the embodiments disclosed herein, a battery diagnostic device and a battery diagnostic method can be provided that can more accurately diagnose overheating events even when battery data collection is poor due to unstable communication conditions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122603283A_ABST
    Figure CN122603283A_ABST
Patent Text Reader

Abstract

According to some embodiments, a battery diagnostic device includes an interface to acquire battery data from a battery to be diagnosed at each collection period at a start of a current cycle, and a controller to determine whether the battery data passes a test item at each collection period to generate a first count value for the current cycle, accumulate a number of failures of the determination of the test item in the current cycle to generate a second count value for the current cycle, perform a first diagnosis of the battery to be diagnosed based on a first accumulation of the first count value for a first cycle number, and perform a second diagnosis of the battery to be diagnosed based on a second accumulation of the second count value for a second cycle number.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Cross-references to related applications

[0002] This application claims priority to Korean Patent Application No. 10-2024-0045416, filed on April 3, 2024, the disclosure of which is incorporated herein by reference. Technical Field

[0003] The embodiments disclosed herein relate to battery diagnostic devices and battery diagnostic methods. Background Technology

[0004] In recent years, research and development of rechargeable batteries have been actively pursued. Here, rechargeable batteries are batteries capable of charging and discharging, and can be interpreted as encompassing conventional Ni / Cd batteries, Ni / MH batteries, and more recently, lithium-ion batteries. Among rechargeable batteries, lithium-ion batteries can achieve higher energy density than conventional Ni / Cd and Ni / MH batteries, and can be manufactured in a smaller and lighter form, making them highly usable as power sources for mobile devices. In recent years, the application of lithium-ion batteries has expanded to power electric vehicles, making batteries a focus of attention as a next-generation energy storage medium.

[0005] To prevent battery accidents caused by overheating, the Battery Management System (BMS) can detect signs of thermal anomalies and warn the vehicle and driver. For example, it can measure battery voltage and temperature and execute early warnings of thermal events based on the measurement results. However, in cases where battery data collection is unstable due to communication issues with the BMS, overheating event testing is performed with limited data. In such cases of poor data collection, the accuracy of overheating diagnostics may suffer. Summary of the Invention

[0006] Technical issues

[0007] The purpose of the embodiments disclosed herein is to provide a battery diagnostic device and a battery diagnostic method that can more accurately diagnose overheating events even when battery data collection is poor due to unstable communication conditions.

[0008] The technical objectives of the embodiments disclosed herein are not limited to those described above, and other technical objectives not mentioned will be clearly understood by those skilled in the art from the following description.

[0009] Technical solution

[0010] According to some embodiments, a battery diagnostic apparatus includes: an interface configured to acquire battery data from a target battery for diagnosis at each collection interval when a current cycle begins; and a controller configured to: determine whether the battery data passes a test item at each collection interval and generate a first count value for the current cycle; accumulate the number of times the test item is determined to have failed in the current cycle and generate a second count value for the current cycle; perform a first diagnosis on the target battery for diagnosis based on a first accumulated value of the first count value for a first cycle number; and perform a second diagnosis on the target battery for diagnosis based on a second accumulated value of the second count value for a second cycle number.

[0011] According to some implementations, the target battery for diagnosis may include multiple battery cells, and the battery data may include the cell voltage and cell temperature of each of the multiple battery cells.

[0012] According to some implementation methods, the test items may include: a first item regarding whether the maximum cell voltage exceeds the upper limit of cell voltage, a second item regarding whether the minimum cell voltage is less than the lower limit of cell voltage, a third item regarding whether the cell voltage deviation relative to the average cell voltage exceeds a voltage deviation threshold, a fourth item regarding whether the maximum cell temperature exceeds the upper limit of cell temperature, and a fifth item regarding whether the cell temperature deviation relative to the average cell temperature exceeds a temperature deviation threshold.

[0013] According to some implementations, the controller can be configured to determine a detailed count value for each of the test items in each collection interval; check test items whose detailed count value exceeds a threshold count for each of the test items as defects in the current loop; and perform a first diagnosis based on the number of defects for the test items up to the first loop number of the current loop.

[0014] According to some implementations, the controller can be configured to perform a first diagnosis in a test item when a test item is found to be defective in all first loop iterations.

[0015] According to some implementations, the controller can be configured to perform a second diagnosis when the second cumulative value of the second count for the second cycle number exceeds a second diagnostic threshold for each of the test items.

[0016] According to some implementations, the second loop count can be greater than the first loop count, and the second diagnostic threshold for each of the test items can be the product of the threshold count for each of the test items and the first loop count.

[0017] According to some implementations, the controller can be configured to change the state of the target battery to an early warning state for a thermal event based on at least one of a first diagnosis and a second diagnosis.

[0018] According to some implementations, a battery diagnostic method includes the following steps: acquiring battery data from a target battery at each collection interval when the current cycle starts; determining whether the battery data passes a test item at each collection interval and generating a first count value for the current cycle; accumulating the number of times the test item is determined to have failed in the current cycle and generating a second count value for the current cycle; performing a first diagnosis on the target battery based on a first accumulated value of the first count value for a first cycle number; and performing a second diagnosis on the target battery based on a second accumulated value of the second count value for a second cycle number.

[0019] According to some implementations, the target battery for diagnosis may include multiple battery cells, and the battery data may include the cell voltage and cell temperature of each of the multiple battery cells.

[0020] According to some implementation methods, the test items may include: a first item regarding whether the maximum cell voltage exceeds the upper limit of cell voltage, a second item regarding whether the minimum cell voltage is less than the lower limit of cell voltage, a third item regarding whether the cell voltage deviation relative to the average cell voltage exceeds a voltage deviation threshold, a fourth item regarding whether the maximum cell temperature exceeds the upper limit of cell temperature, and a fifth item regarding whether the cell temperature deviation relative to the average cell temperature exceeds a temperature deviation threshold.

[0021] According to some implementations, the step of performing the first diagnosis may include the following steps: determining a detailed count value for each of the test items at each collection interval; checking test items whose detailed count value exceeds a threshold count for each of the test items as defects in the current loop; and performing the first diagnosis based on the number of defects for the test items up to the first loop number up to the current loop.

[0022] According to some implementations, the step of performing the first diagnosis may include the following steps: performing the first diagnosis when there is a test item that is found to be defective in all first cycle counts of the test items.

[0023] According to some implementations, the step of performing a second diagnosis may include the following steps: performing a second diagnosis when a second cumulative value of a second count for a second cycle number exceeds a second diagnostic threshold for each of the test items.

[0024] According to some implementations, the second loop count can be greater than the first loop count, and the second diagnostic threshold for each of the test items can be the product of the threshold count for each of the test items and the first loop count.

[0025] According to some implementations, the battery diagnostic method may further include the following steps: changing the state of the target battery to an early warning state of a thermal event based on at least one of a first diagnosis and a second diagnosis.

[0026] Beneficial effects

[0027] According to the embodiments disclosed herein, a battery diagnostic device and a battery diagnostic method can be provided that can more accurately diagnose overheating events even when battery data collection is poor due to unstable communication conditions.

[0028] The technical effects of the embodiments disclosed herein are not limited to the above-described technical effects, and those skilled in the art will clearly understand other effects not mentioned based on the disclosure herein. Attached Figure Description

[0029] Figure 1 Examples of components constituting a battery diagnostic system can be shown according to some implementations.

[0030] Figure 2 Examples of components constituting a battery diagnostic device according to some embodiments can be shown.

[0031] Figure 3 A process for performing early warnings for thermal events through first and second diagnostics, according to some implementations, can be illustrated.

[0032] Figure 4 Examples of test standards and detailed count values ​​for test items according to some implementation methods can be provided.

[0033] Figure 5 Examples can be given of how the count value for high-voltage testing of battery cells changes as cycles are performed, according to some implementation methods.

[0034] Figure 6 The steps of a battery diagnostic method according to some implementations can be illustrated. Detailed Implementation

[0035] In the following description, embodiments disclosed herein will be illustrated with reference to the accompanying drawings. However, this is not intended to limit the disclosure herein to the specific embodiments, and it will be construed as including various modifications, equivalents, and / or substitutions of the embodiments disclosed herein.

[0036] It should be understood that the embodiments and terminology used herein are not intended to limit the technical features set forth herein to a particular embodiment and include various changes, equivalents, or substitutions to the corresponding embodiments. Regarding the description of the drawings, similar or related reference numerals may be used to refer to similar or related elements. It should be understood that, unless the relevant context clearly indicates otherwise, the singular form of the noun corresponding to an item may include one or more things.

[0037] As used herein, each of the phrases such as “A or B,” “at least one of A and B,” “at least one of A or B,” “A, B or C,” “at least one of A, B and C,” and “at least one of A, B or C” may include any one or all possible combinations of the items listed together in the corresponding one of the phrases. Terms such as “first,” “second,” “firstly,” “secondarily,” “A,” “B,” “(a),” or “(b)” may be used merely to distinguish the corresponding component from another component and do not otherwise limit the component (e.g., in terms of importance or order) unless otherwise specifically stated.

[0038] In this specification, it should be understood that if an element (e.g., a first element) is referred to as "connected to," "coupled to," or "in contact with" another element (e.g., a second element) with or without the terms "operably" or "communically," it means that the element can be connected to the other element directly (e.g., via wired or wireless) or indirectly (e.g., via a third element).

[0039] Methods according to the various embodiments disclosed herein can be included and provided in a computer program product. The computer program product can be traded as a product between a seller and a buyer. The computer program product can be distributed in the form of a machine-readable storage medium (e.g., an optical disc read-only memory and a CD-ROM), or distributed online via an app store (e.g., downloaded or uploaded), or directly between two operator devices. If distributed online, at least a portion of the computer program product can be temporarily generated or at least temporarily stored in a machine-readable storage medium such as the memory of a manufacturer's server, an app store's server, or a relay server.

[0040] According to the embodiments disclosed herein, each of the above components (e.g., a module or program) may include a single entity or multiple entities, and some of the multiple entities may be configured separately from other components. According to the embodiments disclosed herein, one or more components or operations of the above components may be omitted, or one or more other components or operations may be added. Alternatively or additionally, multiple components (e.g., modules or programs) may be integrated into a single component. In this case, the integrated component may still perform one or more functions of each of the multiple components in the same or similar manner as performed by the corresponding component of the multiple components before integration. According to the embodiments disclosed herein, operations performed by a module, program, or other component may be implemented sequentially, in parallel, repeatedly, or heuristically, or may be performed in a different order, or one or more operations may be omitted, or one or more other operations may be added.

[0041] Figure 1 Examples of components constituting a battery management system according to some implementation methods can be given.

[0042] Reference Figure 1 The battery diagnostic system 100 may include a power-using device 110, a target battery 120 for diagnostics, and a battery diagnostic device 130. However, the battery diagnostic system is not limited to this, and some components may be omitted from the battery diagnostic system 100, or other general components may be included in the battery diagnostic system 100.

[0043] The battery diagnostic system 100 can refer to a system used to diagnose and manage the state of the target battery 120. When the target battery 120 is charged or discharged by the power-using device 110, the battery diagnostic device 130 can measure and analyze the battery data of the target battery 120.

[0044] The power consumption device 110 can be configured to charge or discharge the diagnostic target battery 120. The power consumption device 110 can discharge the diagnostic target battery 120 while consuming power, and can also charge the diagnostic target battery 120 while generating power. According to embodiments, the power consumption device 110 may include a mobility device such as an electric vehicle (EV), a hybrid electric vehicle (HEV), or an electric bicycle. The mobility device can drive a motor based on power from the diagnostic target battery 120 or charge the diagnostic target battery 120 using power generated through regenerative braking.

[0045] The target battery 120 for diagnosis may include a battery pack, etc., to be diagnosed by the battery diagnostic system 100. The battery pack of the target battery 120 may include multiple battery modules, and each battery module may include multiple battery cells. According to embodiments, the target battery 120 for diagnosis can be installed in various types of mobile devices.

[0046] The battery diagnostic device 130 can perform operations for diagnosing or managing the target battery 120. The battery diagnostic device 130 can measure battery data from the target battery 120 and diagnose or manage the state of the target battery 120 based on the battery data.

[0047] The battery diagnostic system 100 may also include a management server. The management server can manage the diagnostic results of the battery diagnostic device 130. The management server can exchange data with the battery diagnostic device 130 via wired / wireless communication. When a defect in the target battery 120 is diagnosed or its lifespan is predicted, the results can be sent to the management server and recorded in a database.

[0048] According to one embodiment, the management server can perform operations for managing and diagnosing the target battery 120, replacing the battery diagnostic device 130. According to another embodiment, the operation of the battery diagnostic device 130 can be performed by the charging device of the battery charging station. According to yet another embodiment, the battery diagnostic device 130 can perform diagnostic operations by executing battery management software, and the management server can provide the battery diagnostic device 130 with update information regarding the battery management software.

[0049] Figure 2 Examples of components constituting a battery diagnostic device according to some embodiments can be shown.

[0050] Reference Figure 2 The battery diagnostic device 130 may include an interface 131 and a controller 132. However, the battery diagnostic device is not limited to this, and some components may be omitted from the battery diagnostic device 130, or other general components may be included in the battery diagnostic device 130.

[0051] The battery diagnostic device 130 can be a battery management system (BMS) configured in an on-board configuration with the target battery 120, or it can be an external device remotely configured with the target battery 120 in a non-on-board configuration. According to embodiments, the external device may include a battery management server, a battery diagnostic device, a battery charging device, etc. The battery management server may include a cloud server operating in a cloud computing environment. According to embodiments, the interface 131 and controller 132 in the battery diagnostic device 130 can be electrically connected to each other via a device-to-device communication method. This device-to-device communication method may include a bus, general purpose input / output (GPIO), serial peripheral interface (SPI), and mobile industrial processor interface (MIPI).

[0052] Interface 131 can acquire battery data from the target battery 120 for diagnosis. According to an embodiment, interface 131 may include at least one of a communication unit configured to receive battery data and a sensor unit configured to measure battery data. According to an embodiment, when the battery diagnostic device 130 is implemented in a non-vehicle configuration, the communication unit may receive battery data via methods such as wired data communication or wireless data communication. Alternatively, when the battery diagnostic device 130 is implemented in a vehicle configuration, the sensor unit may be configured to generate various battery measurements from the target battery 120 for diagnosis. For this purpose, the sensor may include measuring devices such as voltage sensors, current sensors, and temperature sensors.

[0053] The controller 132 may have a structure for executing commands that implement the operation of the battery diagnostic device 130. The controller 132 may be implemented as an array of multiple logic gates or a general-purpose microprocessor for handling various operations, and may consist of a single processor or multiple processors. For example, the controller 132 may be implemented in the form of at least one of a microprocessor, a central processing unit (CPU), a graphics processing unit (GPU), and an application processor (AP).

[0054] The controller 132 can operate together with a memory configured to store various data, commands, mobile applications, computer programs, etc. The memory can be configured separately from or integrated with the controller 132. The controller 132 can process various operations by executing commands stored in the memory. The memory can be implemented as a non-volatile device such as read-only memory (ROM), programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable PROM (EEPROM), flash memory, parallel random access memory (PRAM), magnetoresistive RAM (MRAM), resistive RAM (RRAM), ferroelectric RAM (FRAM), etc., or as a volatile device such as dynamic RAM (DRAM), static RAM (SRAM), synchronous dynamic RAM (SDRAM), parallel RAM (PRAM), etc., or as a hard disk drive (HDD), solid-state drive (SSD), secure digital storage (SD), micro SD, or a combination thereof.

[0055] Interface 131 can be configured to acquire battery data from the diagnostic target battery 120 at each collection interval when the current cycle begins. The current cycle can be a driving cycle such as an electric vehicle (EV). Battery data can be collected during each collection interval of the current cycle. For example, the collection interval can be 1 second, or other suitable values ​​can be used depending on the design.

[0056] The controller 132 can be configured to determine whether battery data passes the test items at each collection interval and generate a first count value for the current cycle. For example, battery data may include cell voltage and cell temperature, the test items may include five items, and the collection interval may be one second. It can be determined every second whether any of the five items have failed the test, and this data can be recorded. For example, the current cycle may last for 30 minutes, and the first count value can be calculated based on the number of failed test items.

[0057] The controller 132 can be configured to accumulate the number of failed determinations for a test item in the current loop and generate a second count value for the current loop. Determination tests may fail for various reasons, such as diagnosing internal defects in the target battery 120, malfunctions in the interface 131, or communication problems with the battery diagnostic device 130. Since failures may result in missed opportunities to diagnose defects, a second count value can be generated based on the number of failures to account for this aspect of overheating diagnostics.

[0058] The controller 132 can be configured to perform a first diagnosis on the target battery 120 based on a first cumulative value of a first count for a first cycle number. The first cumulative value of the first count can indicate how many tests passed or failed, which can indicate the risk of overheating of the target battery 120. For example, the first cycle number can be 5, which may include four past cycles and one current cycle. The specific value of the first cycle number can vary depending on the diagnostic accuracy requirements.

[0059] The controller 132 can be configured to perform a second diagnostic on the target battery 120 based on a second cumulative value of a second count value for a second cycle number. A higher second cumulative value of the second count value can indicate more data collection failures, which may mean an increased risk of missing overheat diagnostics. By reflecting this, a second diagnostic based on the second cumulative value can be performed. For example, the second cycle number can be 10 times, and can be changed to other values ​​depending on the design. The second cycle number can be greater than the first cycle number.

[0060] According to an implementation, the target battery 120 for diagnosis may include multiple battery cells, and the battery data may include the cell voltage and cell temperature of each of the multiple battery cells. Battery diagnostic indicators can be derived based on the cell voltage and cell temperature of each battery cell, and the pass or fail of tests can be determined based on the battery diagnostic indicators. Battery diagnostic indicators may include maximum cell voltage, minimum cell voltage, cell voltage deviation relative to the average cell voltage, maximum cell temperature, and cell temperature deviation relative to the average cell temperature, etc.

[0061] According to the implementation method, the test items may include: a first item regarding whether the maximum cell voltage exceeds the upper limit of the cell voltage; a second item regarding whether the minimum cell voltage is less than the lower limit of the cell voltage; a third item regarding whether the cell voltage deviation relative to the average cell voltage exceeds a voltage deviation threshold; a fourth item regarding whether the maximum cell temperature exceeds the upper limit of the cell temperature; and a fifth item regarding whether the cell temperature deviation relative to the average cell temperature exceeds a temperature deviation threshold. These test items can be monitored to diagnose overheating events in the target battery 120.

[0062] According to an implementation, controller 132 can be configured to determine a detailed count value for each of the test items in each collection interval, check test items whose detailed count values ​​exceed a threshold count for each test item as defects in the current cycle, and perform a first diagnosis based on the number of defects for the test items up to the first cycle number. When the collection interval is one second and there are five test items, the pass / fail status of the five items can be determined every second. For example, when the number of test failures for the first test item is 25 during the current cycle of 30 minutes, the detailed count value for the first test item can be 25. When the threshold count for the first test item is 20, since the detailed count value exceeds the threshold count, the first test item can be checked as a defect in the current cycle. The first diagnosis can be performed based on the cumulative number of defects for the five items during the first cycle number.

[0063] According to an implementation, controller 132 can be configured to perform a first diagnosis when a test item is found to be defective across all first loop counts. For example, the first loop count can be five, which may include four past loops and one current loop. When any of the five test items across all five loops is found to be defective, the first diagnosis can be performed on the target battery 120, indicating that the target battery 120 is at risk of an overheating event.

[0064] According to an implementation, controller 132 can be configured to perform a second diagnosis when a second cumulative value of a second count for a second cycle exceeds a second diagnostic threshold for each of the test items. For example, the second cycle may be 10 cycles, and the second count may be accumulated over 10 cycles. A second cumulative value may be generated for each of the test items. For example, when there are five second cumulative values ​​for five test items, the five second cumulative values ​​may be compared with five second diagnostic thresholds respectively. Among the five test items, when there is a test item where the second cumulative value exceeds the second diagnostic threshold, a second diagnosis may be performed on the target battery 120. The second diagnosis may indicate that the target battery 120 is at risk of overheating due to missed data collection.

[0065] According to the implementation, the second number of loops is greater than the first number of loops, and the second diagnostic threshold for each of the test items can be the product of the threshold count for each of the test items and the first number of loops. The threshold count and the first number of loops can be used for the first diagnosis, while the second diagnostic threshold can be used for the second diagnosis. By setting the second diagnostic threshold to the product of the threshold count and the first number of loops, the parameters of the first diagnosis and the parameters of the second diagnosis can be correlated with each other. This makes the risk of overheating due to failure to pass a test item and the risk of overheating due to poor data collection correlated with each other.

[0066] According to an implementation, the controller 132 can be configured to change the state of the target battery 120 to an early thermal event alarm state based on at least one of a first diagnostic and a second diagnostic. Since the early thermal event alarm state reflects both the first and second diagnostics, the overheating risk due to failure to pass a test item and the overheating risk due to poor data collection can be considered together.

[0067] Figure 3 A process for performing early warning of thermal events through first and second diagnoses, according to some implementations, can be illustrated.

[0068] Reference Figure 3 Flowchart 300 can be exemplified, illustrating the process of executing an early alert for a thermal event through a first diagnostic and a second diagnostic. Flowchart 300 may include steps 310 through 380.

[0069] In step 310, a monitoring loop for the target battery 120 can be started. For example, the monitoring loop can respond to the movement of the electric vehicle and to the current cycle. In step 320, it can be determined whether a test item passed. In step 330, it can be determined whether there is a result of at least one failed item (result ≥ 1) or whether there are no failed items (result < 1). In step 340, it can be determined whether the cumulative failure count over 5 or more cycles is 5 or more, and if yes, an early thermal event alarm can be executed in step 370; if no, the monitoring loop can be terminated by proceeding to step 380. Continuous failure count can refer to the cumulative failure count.

[0070] In step 350, if no test items have failed, it can be determined whether 10 cycles (the second cycle count) have been completed. If so (No), the monitoring loop can be terminated in step 380. If not, the consecutive failure count value can be compared with a second diagnostic threshold in step 360. The second diagnostic threshold can be calculated as (detailed count value for each test × five times). This can be intended to account for the risk of overheating due to data collection failures related to the second diagnosis. If "Yes", an early thermal event alarm can be executed in step 370, and if "No", the monitoring loop can be terminated in step 380.

[0071] Figure 4 Examples of test standards and detailed count values ​​for test items according to some implementation methods can be provided.

[0072] Reference Figure 4 Figure 400 illustrates the testing standards and detailed count values ​​for the test items.

[0073] Chart 400 can display five test items. These five test items can be cell high voltage test, cell low voltage test, cell voltage deviation test, cell high temperature test, and cell temperature deviation test.

[0074] Chart 400 can show the testing standards for five test items. For example, in the case of high-voltage cell testing, it can be determined whether there are any battery cells among multiple battery cells with a cell voltage exceeding 4.5V. In a similar manner, the remaining four test items can be determined.

[0075] Chart 400 can display detailed counts for five test items. For example, in the case of cell high voltage testing, the number of times any battery cell exceeds 4.5V can be counted at each collection interval (e.g., one second) during the current cycle (e.g., 30 minutes of driving time for an electric vehicle). If the cell high voltage test count in the current cycle exceeds the detailed count value by 20 times, the cell high voltage test can be checked as a defect.

[0076] Furthermore, due to the nature of the tests, cell voltage deviation tests and cell temperature deviation tests can have relatively high detailed count values. The numerical values ​​and detailed count values ​​of the test standards shown in Figure 400 can be changed to other suitable values ​​according to the design.

[0077] Figure 5 Examples can be given of how the count value for high-voltage testing of battery cells changes as cycles are performed, according to some implementation methods.

[0078] Figure 500 illustrates how the count value used for high-voltage testing of battery cells changes as the cycle progresses.

[0079] The third row of Chart 500 can represent the consecutive failure count, which can mean the cumulative failure count. The fourth row of Chart 500 can represent the consecutive failure count, which can represent the cumulative value of the first count (e.g., the detailed count value in Chart 400).

[0080] Figure 500 can exemplarily show only the cell high-voltage test out of the five test items. Since the cell high-voltage test fails in all five cycles (driving cycles 1 to 5), the cumulative failure count in driving cycle 5 can be five. This can meet the criteria for the first diagnosis of the target battery 120 and can indicate that the target battery 120 is currently at risk of overheating.

[0081] Chart 500 can display the accumulation of the first count value in the lowest row. When the accumulated failure count in driving cycle 5 is less than 5, the first diagnostic may not be performed. In this case, the battery can undergo a second diagnostic when the number of battery data collection failures exceeds 100 (20 × 5) times during 10 cycles (the second cycle count). In this way, even if the risk is low from the perspective of the first diagnostic, the risk due to data collection failures can be analyzed through the second diagnostic.

[0082] Figure 6 The steps of a battery diagnostic method according to some implementations can be illustrated.

[0083] Reference Figure 6 The battery diagnostic method 600 may include steps 610 to 650. However, the battery diagnostic method is not limited to this, and some steps may be omitted or other general steps may be added, and the steps of the battery diagnostic method 600 may be performed in a different order than that shown.

[0084] The battery diagnostic method 600 may include steps performed in a time sequence within the battery diagnostic device 130. Therefore, even though the following description of the battery diagnostic device 130 is omitted, the same applies to the battery diagnostic method 600.

[0085] Steps 610 to 650 of the battery diagnostic method 600 can be executed by the interface 131 and controller 132 of the battery diagnostic device 130.

[0086] In step 610, the battery diagnostic device 130 may perform the step of acquiring battery data from the target battery for diagnosis at each collection interval when the current cycle starts.

[0087] In step 620, the battery diagnostic device 130 may perform the steps of determining whether the battery data passes the test item at each collection interval and generating a first count value for the current cycle.

[0088] In step 630, the battery diagnostic device 130 may perform the step of generating a second count value for the current cycle by accumulating the number of determined failures of the test items in the current cycle.

[0089] In step 640, the battery diagnostic device 130 may perform a first diagnostic step on the target battery based on a first cumulative value of a first count value for a first cycle number.

[0090] In step 650, the battery diagnostic device 130 may perform a second diagnostic step on the target battery based on a second cumulative value of a second count value for a second cycle number.

[0091] According to an embodiment, the battery diagnostic method 600 can be implemented as a computer program stored in a computer-readable storage medium. That is, the computer program may include commands for implementing the battery diagnostic method 600, and the commands of the program may be stored in a computer-readable storage medium. The computer program may include a mobile application.

[0092] In implementations, computer-readable storage media may include magnetic media such as hard disks, floppy disks, and magnetic tapes; optical media such as CD-ROMs and DVDs; magneto-optical media such as floppy disks; and hardware devices specifically configured to store and execute computer program instructions, such as ROMs, RAMs, and flash memory. Computer program instructions may include machine language code generated by a compiler and high-level language code that can be executed by a computer using an interpreter or similar means.

[0093] Unless otherwise stated, terms such as “comprising,” “including,” or “having” above imply the presence of corresponding components and should therefore be interpreted as potentially including, rather than excluding, other components. Unless otherwise defined, all terms, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which the embodiments disclosed herein pertain. Commonly used terms (such as those defined in dictionaries) should be interpreted as having the same meaning as they have in the context of the relevant art and should not be interpreted in an idealized or overly formal sense unless expressly defined herein.

[0094] The above description is merely an example of the technical concepts disclosed herein, and those skilled in the art to which the embodiments disclosed herein pertain can make various modifications and variations without departing from the basic characteristics of the embodiments disclosed herein. Therefore, the embodiments disclosed herein are not intended to limit the technical concepts of the embodiments disclosed herein, but rather to interpret them, and the scope of the technical concepts disclosed herein is not limited by these embodiments. The scope of protection disclosed herein should be interpreted by the appended claims, and all technical concepts within the same scope should be interpreted as including within the scope of the claims herein.

[0095] [List of reference numerals]

[0096] 100: Battery diagnostic system; 110: Power consumption device

[0097] 120: Target battery for diagnosis; 130: Battery diagnostic device

[0098] 131: Sensor 132: Controller

Claims

1. A battery diagnostic device, the battery diagnostic device comprising: An interface configured to acquire battery data from the target diagnostic battery at each collection interval upon the start of the current cycle; as well as The controller is configured to: At each collection interval, determine whether the battery data passes the test item and generate a first count value for the current cycle; The number of times the test item fails to be determined in the current loop is accumulated and a second count value for the current loop is generated; A first diagnosis is performed on the target battery based on a first cumulative value of the first count value for the first cycle number; and A second diagnosis is performed on the target battery based on a second cumulative value of the second count for the second cycle number.

2. The battery diagnostic device according to claim 1, wherein, The target battery for diagnosis includes multiple battery cells, and The battery data includes the cell voltage and cell temperature of each of the plurality of battery cells.

3. The battery diagnostic device according to claim 2, wherein, The test items include: a first item regarding whether the maximum cell voltage exceeds the upper limit of cell voltage; a second item regarding whether the minimum cell voltage is less than the lower limit of cell voltage; a third item regarding whether the cell voltage deviation relative to the average cell voltage exceeds the voltage deviation threshold; a fourth item regarding whether the maximum cell temperature exceeds the upper limit of cell temperature; and a fifth item regarding whether the cell temperature deviation relative to the average cell temperature exceeds the temperature deviation threshold.

4. The battery diagnostic device according to claim 1, wherein, The controller is configured to: Detailed count values ​​are determined for each of the test items at each collection interval; Test items whose detailed count values ​​exceed the threshold count for each of the test items are identified as defects in the current loop. The first diagnosis is performed based on the number of defects in the test item up to the first cycle number of the current cycle.

5. The battery diagnostic device according to claim 4, wherein, The controller is configured to perform the first diagnosis when a test item is identified as defective in all of the first cycle counts.

6. The battery diagnostic device according to claim 4, wherein, The controller is configured to perform the second diagnosis when the second cumulative value of the second count for the second cycle number exceeds a second diagnostic threshold for each of the test items.

7. The battery diagnostic device according to claim 6, wherein, The second loop count is greater than the first loop count, and the second diagnostic threshold for each of the test items is the product of the threshold count for each of the test items and the first loop count.

8. The battery diagnostic device according to claim 1, wherein, The controller is configured to change the state of the target battery to an early warning state for a thermal event based on at least one of the first diagnosis and the second diagnosis.

9. A battery diagnostic method, the battery diagnostic method comprising the following steps: At the start of the current cycle, acquire battery data from the target battery for diagnosis at each collection interval; At each collection interval, determine whether the battery data passes the test item and generate a first count value for the current cycle; The number of times the test item fails to be determined in the current loop is accumulated and a second count value for the current loop is generated; A first diagnosis is performed on the target battery based on a first cumulative value of the first count value for a first cycle number; as well as A second diagnosis is performed on the target battery based on a second cumulative value of the second count for the second cycle number.

10. The battery diagnostic method according to claim 9, wherein, The target battery for diagnosis includes multiple battery cells, and The battery data includes the cell voltage and cell temperature of each of the plurality of battery cells.

11. The battery diagnostic method according to claim 10, wherein, The test items include: a first item regarding whether the maximum cell voltage exceeds the upper limit of cell voltage; a second item regarding whether the minimum cell voltage is less than the lower limit of cell voltage; a third item regarding whether the cell voltage deviation relative to the average cell voltage exceeds the voltage deviation threshold; a fourth item regarding whether the maximum cell temperature exceeds the upper limit of cell temperature; and a fifth item regarding whether the cell temperature deviation relative to the average cell temperature exceeds the temperature deviation threshold.

12. The battery diagnostic method according to claim 9, wherein, The steps for performing the first diagnosis include the following: Detailed count values ​​are determined for each of the test items at each collection interval; Test items whose detailed count values ​​exceed the threshold count for each of the test items are identified as defects in the current loop; and The first diagnosis is performed based on the number of defects in the test item up to the first cycle number of the current cycle.

13. The battery diagnostic method according to claim 12, wherein, The step of performing the first diagnosis includes the following steps: among the test items, the first diagnosis is performed when there is a test item that is checked as defective in all the first cycle counts.

14. The battery diagnostic method according to claim 12, wherein, The steps of performing the second diagnosis include the following steps: performing the second diagnosis when the second cumulative value of the second count for the second cycle number exceeds the second diagnostic threshold for each of the test items.

15. The battery diagnostic method according to claim 14, wherein, The second loop count is greater than the first loop count, and the second diagnostic threshold for each of the test items is the product of the threshold count for each of the test items and the first loop count.

16. The battery diagnostic method according to claim 9, further comprising the following steps: The state of the target battery is changed to an early warning state for a thermal event based on at least one of the first diagnosis and the second diagnosis.

Citation Information

Patent Citations

  • Store identification system through signboard recognition and store identification method for using the same

    KR1020240045416A