Charge / discharge test system and program

Abstract

This technology provides a way to easily and accurately respond to abnormalities that occur during charge-discharge testing. [Solution] The charge-discharge test system comprises a charge-discharge control unit that controls the charging and discharging of a secondary battery for testing, an abnormality detection unit that detects abnormalities related to the test, an event identification unit that identifies the event occurring when an abnormality is detected, and a cause estimation unit that estimates the cause of the detected abnormality from the identified event by referring to cause example data that defines the correspondence between possible causes of the abnormality and events that may occur when an abnormality occurs due to said cause example.

Description

Technical Field

[0001] The present invention relates to a charge-discharge test of a secondary battery.

Background Art

[0002] In power-using products such as electric vehicles, secondary batteries may be used. To ensure the quality of electric vehicles, the evaluation of secondary batteries is essential. When examining changes in electrical characteristics and durability, charge-discharge simulating the behavior of an electric vehicle is performed to measure the electrical characteristics of the secondary battery. Therefore, a charge-discharge test system is used.

[0003] Tests using a charge-discharge test system often last for a long period. It is required that the charge-discharge test system operates stably during that test period.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] However, in reality, during the test period, abnormalities may occur and the test may be interrupted. In that case, the cause should be analyzed promptly and measures should be taken to recover. The causes of abnormalities occurring in the charge-discharge test system are diverse, and the analysis is not always easy.

[0006] Patent Document 1 discloses a technique for recording log data in addition to test data during a charge-discharge test of a secondary battery. When an unexpected abnormality occurs during the test, referring to the log data helps to grasp the situation.

[0007] However, even with reference to log data, analyzing the cause of an anomaly requires advanced knowledge of charge / discharge testing, and may only be possible for experienced maintenance personnel. In such cases, the test may be stopped for an extended period, which is undesirable.

[0008] This invention has been made in view of these circumstances, and one of its objectives is to provide a technology that makes it easier to respond simply and accurately to abnormalities that occur during charge-discharge testing. [Means for solving the problem]

[0009] A charge-discharge test system according to one aspect of the present invention comprises: a charge-discharge control unit that controls the charging and discharging of a secondary battery for testing; an abnormality detection unit that detects abnormalities related to the test; an event identification unit that identifies the event occurring when an abnormality is detected; and a cause estimation unit that estimates the cause of the detected abnormality from the identified event by referring to cause example data that defines the correspondence between possible causes of the abnormality and events that may occur when the abnormality occurs due to the cause example. [Effects of the Invention]

[0010] According to the present invention, it is possible to provide a technology that makes it easy to respond simply and accurately to abnormalities that occur during charge-discharge testing. [Brief explanation of the drawing]

[0011] [Figure 1] This is a diagram showing the configuration of the charge / discharge test system. [Figure 2] This is a functional block diagram of the control unit. [Figure 3] Figure 3(A) is a block diagram of the communications unit. Figure 3(B) is a block diagram of the data storage unit. [Figure 4] Figures 4(A) to 4(C) show the data structure diagrams of the event data storage unit. [Figure 5] This is a data structure diagram of the anomaly response list storage unit. [Figure 6] This is a data structure diagram of the cause case data storage unit. [Figure 7] It is a data structure diagram of a countermeasure example data storage unit. [Figure 8] It is a data structure diagram of a caution example data storage unit. [Figure 9] It is a data structure diagram of a maintenance history storage unit. [Figure 10] It is a flow chart of a failure self-diagnosis process. [Figure 11] It is a flow chart of a failure self-diagnosis process. [Figure 12] It is a flow chart of a failure self-diagnosis process. [Figure 13] It is a flow chart of a failure self-diagnosis process.

Mode for Carrying Out the Invention

[0012] Hereinafter, an embodiment of the present invention will be described while referring to the drawings. In the following embodiments and their modifications, substantially the same components are denoted by the same reference numerals, and the description thereof will be omitted as appropriate.

[0013] Secondary batteries are used in various products. A typical example is an electric vehicle. Automobile manufacturers evaluate the batteries provided by various battery manufacturers and decide which battery to adopt. In doing so, an evaluation of the secondary battery is performed.

[0014] An electric vehicle roughly discharges the secondary battery when accelerating and charges the secondary battery when decelerating. When these charge and discharge cycles are repeated, the secondary battery deteriorates and its performance decreases.

[0015] Automobile manufacturers need to investigate under what conditions and to what extent secondary batteries deteriorate when used. Therefore, equipment for testing secondary batteries is prepared. This equipment is called a charge-discharge test system. At the center of this system is the charge-discharge device main body that charges and discharges the secondary battery. The charge-discharge device main body not only performs the charge-discharge operation but also measures voltage, current, internal resistance, and SOC (State Of Charge). SOC is an index representing the charge rate or charge state. The evaluation of the secondary battery is performed based on these measured values.

[0016] The charge-discharge test system includes a control device that controls the charge-discharge device main body. The control device instructs the charge-discharge device main body to operate according to a test program in which the usage conditions of the secondary battery (charge-discharge current, charge-discharge voltage, charge-discharge time, etc.) are incorporated. The test program may instruct a simple repetition of charge and discharge, or may give instructions simulating the actual behavior of an electric vehicle.

[0017] The secondary battery mounted in an electric vehicle must have a certain degree of durability to be practical. Therefore, the evaluation by the test program also continues for a long time. Also, the life of the charge-discharge device main body itself is long.

[0018] During a test that is carried out for a long time, it is not desirable for the test to be interrupted in terms of test efficiency and evaluation objectivity. However, in reality, the test may be interrupted due to various reasons. The following are considered as possible causes, for example. · The tester is using the secondary battery or the charge-discharge test system incorrectly. · The test program created by the tester is not appropriate. · The test environment is not good. · The device of the charge-discharge test system is malfunctioning.

[0019] When the test is interrupted, the tester tries to recover, but may not be able to recover on their own. In that case, the tester contacts the support department of the vendor of the charge-discharge test system.

[0020] The support staff will inquire about the type of alarm emitted by the charging / discharging device itself, its external condition (e.g., whether there is an unusual odor), and the environment in which it is being used, in order to propose solutions.

[0021] If the issue cannot be resolved by the customer service representative, a veteran maintenance technician will take over. Reports from both the customer service representative and the maintenance technician are recorded in the case database. The case database primarily contains a set of information regarding the events, causes, and solutions that occurred during abnormal shutdowns. This information becomes the know-how of the support department. Customer service representatives and maintenance technicians strive to provide more accurate advice by referring to the case database.

[0022] This invention proposes performing fault self-diagnosis in a charge / discharge test system by utilizing the know-how accumulated in a case database. Specifically, it identifies the most likely cause based on the type of alarm from the control device and user input (hearing from the tester), and proposes a countermeasure to the tester according to the identified cause.

[0023] Figure 1 is a diagram showing the configuration of the charge / discharge test system. The charge / discharge test system includes a constant temperature chamber 200, a charge / discharge device main unit 300, a control device 400, a display 402, and an input device 404. The secondary battery 100 is the object of test in the charge / discharge test system. The constant temperature chamber 200 shields the secondary battery 100 in a space at a constant temperature.

[0024] The main body 300 of the charge / discharge device is connected to the secondary battery 100 by a power line 102 and also by a signal line 104. The main body 300 of the charge / discharge device causes the secondary battery 100 to perform charging and discharging.

[0025] The control device 400 is connected to the main unit 300 of the charge / discharge device, the constant temperature bath 200, and the secondary battery 100 by signal lines 104. The control device 400 mainly issues instructions to the main unit 300 of the charge / discharge device according to a test program, and acquires and stores information such as current and voltage during discharge and charging, and SOC, either directly from the secondary battery 100 or indirectly through the main unit 300 of the charge / discharge device.

[0026] Furthermore, the control device 400 acquires information such as the temperature and humidity inside the constant temperature chamber 200 directly or indirectly via the main unit 300 of the charge / discharge device. The control device 400 is also connected to a display 402 and an input device 404. The display 402 and input device 404 are used as a user interface with the tester.

[0027] Figure 2 is a functional block diagram of the control device 400. Each component of the control device 400 is realized by hardware including arithmetic units such as a CPU and various coprocessors, memory and storage devices, and wired or wireless communication lines connecting them, as well as software stored in the storage devices that supplies processing instructions to the arithmetic units. The computer program may consist of device drivers, an operating system, various application programs located at a higher layer, and libraries that provide common functions to these programs. The illustrated blocks represent functional units, not hardware units.

[0028] The control device 400 includes a user interface processing unit 410, a data storage unit 440, a communication unit 450, and a data processing unit 480. The user interface processing unit 410 is responsible for user interface processing via the display 402, input device 404 (such as a keyboard, mouse, or touch sensor), or touch panel integrating the display and touch sensor, all provided by the control device 400. The data storage unit 440 stores various types of data. The data storage unit 440 can be implemented using, for example, RAM, ROM, flash memory, SSD (Solid State Drive), hard disk, other storage devices, or a combination thereof. The communication unit 450 is responsible for communication processing with the charge / discharge device main unit 300, the constant temperature bath 200, and the secondary battery 100. The data processing unit 480 performs various processes based on the data acquired by the communication unit 450 and the data stored in the data storage unit 440. The data processing unit 480 also functions as an interface for the user interface processing unit 410, the data storage unit 440, and the communication unit 450.

[0029] The user interface processing unit 410 includes an input unit 420 for inputting data based on user (tester) operations and an output unit 430 for outputting data to be provided to the user. The input unit 420 includes an operation reception unit 422 that accepts data input based on events detected by an input device 404 such as a keyboard, mouse, touch sensor, or touch panel. The output unit 430 includes a display processing unit 432 that displays various screens on a display device such as a display 402 or touch panel.

[0030] The data processing unit 480 includes a charge / discharge control unit 482, an abnormality detection unit 484, and a fault self-diagnosis unit 498. The charge / discharge control unit 482 controls the charging and discharging of the secondary battery 100 for testing. The abnormality detection unit 484 detects abnormalities related to the testing of the secondary battery 100 and issues an alarm regarding the detected abnormality.

[0031] The fault self-diagnosis unit 498 is implemented by executing a fault self-diagnosis program (hereinafter referred to as the "diagnosis program") stored in the data storage unit 440 using a computing unit. The diagnosis program is an interactive program that identifies the most likely cause based on the type of alarm from the control device 400 and user input (hearing from the tester), and proposes a countermeasure to the user according to the identified cause.

[0032] Examples of alarms include the following: 1. The charge / discharge voltage is too high / too low (compared to the expected / set value). 2. The charge / discharge current is too high / too low (compared to the expected / set value). 3. The temperature of secondary battery 100 is abnormal. 4. The control device 400 is not working. 5. The temperature of the constant temperature chamber 200 is abnormal, or communication with the constant temperature chamber 200 has been lost. 6. The system was stopped by the on-site user (tester). 7. The door of the constant temperature bath 200 was unlocked / unlocked.

[0033] The self-diagnosis unit 498 includes an event identification unit 486, a cause estimation unit 488, a countermeasure proposal unit 490, a warning notification unit 492, a recording unit 494, and a maintenance history presentation unit 496.

[0034] The event identification unit 486 identifies the event that occurred when an abnormality related to the secondary battery test is detected (hereinafter referred to as the "occurring event"). The event identification unit 486 includes the abnormality details and alarm as a type of occurring event, asks questions about the alarm, and includes the tester's answers as a type of occurring event (Figure 4).

[0035] The cause estimation unit 488 refers to the cause case data (Figure 6) and estimates the cause of the abnormality related to the secondary battery test from the occurrence events. The cause estimation unit 488 may also estimate the cause based on a combination of multiple occurrence events. The cause estimation unit 488 may also estimate multiple causes by referring to the cause case data (Figure 6).

[0036] The countermeasure proposal unit 490 refers to the countermeasure case data (Figure 7) to identify a countermeasure corresponding to the estimated cause of the problem and proposes the countermeasure to the tester. The countermeasure proposal unit 490 sequentially proposes countermeasures in order of priority while the abnormality is not resolved. If multiple causes of the problem are estimated, the countermeasure proposal unit 490 identifies a first countermeasure corresponding to the first cause of the problem and proposes the first countermeasure to the tester. If the abnormality cannot be resolved with the first countermeasure, it identifies a second countermeasure corresponding to the estimated second cause of the problem and proposes the second countermeasure to the tester.

[0037] The warning notification unit 492 notifies the tester of any warnings. Specifically, the warning notification unit 492 refers to the warning case data (Figure 8), identifies the warning corresponding to the estimated cause, and notifies the tester of the warning. The recording unit 494 records the maintenance history (Figure 9) of the charge / discharge test system. The maintenance history presentation unit 496 presents the maintenance history to the user. Details of the maintenance history will be described later.

[0038] Figure 3(A) is a block diagram of the communications unit 450. The communication unit 450 includes a transmitting unit 460 that transmits data to the main unit 300 of the charge / discharge device, the constant temperature bath 200, and the secondary battery 100, and a receiving unit 470 that receives data from the main unit 300 of the charge / discharge device, the constant temperature bath 200, and the secondary battery 100.

[0039] Figure 3(B) is a block diagram of the data storage unit 440. The data storage unit 440 includes an event data storage unit 442, an anomaly response list storage unit 444, a cause case data storage unit 446, a countermeasure case data storage unit 447, a caution case data storage unit 448, and a maintenance history storage unit 449.

[0040] The event data storage unit 442 stores the event data (Figure 4). The abnormal response list storage unit 444 stores the abnormal response list (Figure 5). Details of the data will be described later.

[0041] The cause case data storage unit 446 stores cause case data (Figure 6). The cause case data defines the correspondence between possible cause examples that may cause abnormalities in the testing of the secondary battery 100 and the events that may occur when an abnormality occurs due to a given cause example. The cause case data can associate multiple cause examples with one event or a combination of multiple events.

[0042] The countermeasure example data storage unit 447 stores countermeasure example data (Figure 7). The countermeasure example data defines the correspondence between a cause example and a countermeasure related to that cause example. The countermeasure example data can associate multiple prioritized countermeasures with a cause example.

[0043] The caution case data storage unit 448 stores caution case data (Figure 8). The caution case data defines the correspondence between cause examples and precautions to be given to examiners.

[0044] The maintenance history storage unit 449 stores the maintenance history of the charge / discharge test system (Figure 9). The maintenance history of the charge / discharge test system includes the cause of the problem and the countermeasures taken for that cause. The details of the data are described below.

[0045] Figures 4(A) to 4(C) show the data structure diagrams of the event data storage unit 442. The event data can include the type of abnormality, alarm type, response type, and other event details. When the test is running normally, no event details are set, as shown in Figure 4(A).

[0046] When an anomaly is detected, the fault self-diagnosis unit 498 generates event data for analyzing the anomaly. First, the anomaly content and alarm type are set as shown in Figure 4(B). Then, if a question is asked to the tester and an answer is obtained, the answer type is added to the event data as shown in Figure 4(C). The information set in the event data is identified by the event identification unit 486. In this example, "Anomaly Content: Anomaly A", "Alarm Type: Alarm A", and "Answer Type: Answer A" correspond to the event.

[0047] Figure 5 is a data structure diagram of the anomaly response list storage unit 444. Various anomalies can occur during testing. The anomaly response list includes, for each type of anomaly, the type of alarm to notify the test administrator, the questions to ask the test administrator, and possible answers to those questions.

[0048] The abnormalities include not only severe abnormalities such as "charging current is 10% or more above the set value," but also minor abnormalities such as "unexpected interruption" when the tester manually stops the test.

[0049] Possible questions include, for example, "Was there an unusual smell?", "Is the outside temperature above 30 degrees Celsius?", "Is the humidity above 80%?", "Was there a lightning strike?", and "Are you using an uninterruptible power supply?".

[0050] Furthermore, answer options (for example, "unusual odor present" and "unusual odor absent") are set to be displayed along with the questions. In the example in Figure 5, if anomaly A is detected, alarm A is displayed. Then, question F is displayed, prompting the user to choose between answer F-1 or answer F-2. Then, question G is displayed, prompting the user to choose between answer G-1 or answer G-2. There may be one question or multiple questions. There may also be no questions at all.

[0051] Figure 6 is a data structure diagram of the cause case data storage unit 446. The cause case data is prepared in advance based on past cases, and cause examples corresponding to the occurrence of an event are set.

[0052] In the example in Figure 6, when the event is "Anomaly A, Alarm A, Response F-1, Response G-1", the probability that "Cause J" is the cause is "70%", and the probability that "Cause K" is the cause is "20%". The causes with a higher probability are given higher priority, and are listed in the order of first cause example, second cause example. In this example, we first try to resolve the issue assuming "Cause J", and if that fails, we move on to a solution assuming "Cause K".

[0053] In this way, the cause case data storage unit 446 defines the correspondence between possible cause cases that may cause abnormalities in the testing of the secondary battery 100 and the events that may occur when an abnormality occurs due to such a cause case. In the cause case data, one or more cause cases can be associated with one event or a combination of events.

[0054] Figure 7 is a data structure diagram of the countermeasure example data storage unit 447. The data on countermeasures is prepared in advance based on past cases, and countermeasures corresponding to the causes of occurrence are set.

[0055] In the example in Figure 7, if the cause of the problem is "Cause J," it is shown that it can potentially be resolved with "Solution J-1" or "Solution J-2." There may be one or more solutions, and they are prioritized. The priority can be based on the likelihood of resolution or on the ease of implementation. In this example, "Solution J-1" is proposed first, and if that fails, "Solution J-2" is proposed.

[0056] Figure 8 is a data structure diagram of the caution case data storage unit 448. The cautionary case data is prepared in advance based on past cases, and cautionary notes corresponding to the causes of occurrence are set. If testers follow the cautionary notes, it becomes easier to prevent abnormalities caused by those causes.

[0057] The example in Figure 8 shows that when the cause of the incident is "Cause J," "Caution P" and "Caution Q" may be effective. There may be one or more cautions. Furthermore, multiple cautions may be prioritized.

[0058] Figure 9 is a data structure diagram of the maintenance history storage unit 452. The maintenance history storage unit 452 stores a maintenance history that shows what kind of maintenance has been performed on the charge / discharge test system.

[0059] The maintenance history of the charge / discharge test system associates the incident identified by the fault self-diagnosis unit 498, the estimated cause, the implemented countermeasures, and the results of those countermeasures. When a countermeasure was successfully resolved, it is considered effective, and the estimated cause that led to that countermeasure is considered to be the cause of the incident.

[0060] In the example in Figure 9, the cause of the event "Anomaly A, Alarm A, Response F-1, Response G-1" is "Cause K," and "Solution K-1" was effective. If the maintenance history display unit 496 presents such maintenance history to the tester, it will provide a clue to resolving the issue. Specifically, the display processing unit 432 displays the maintenance history on the display 402.

[0061] The charge / discharge test system is characterized by its ability to estimate the most likely cause of a problem based on data obtained on-site (types of alarms generated by the test equipment, and responses from testers to environmental questions such as unusual odors and smoke), and to propose effective countermeasures for the estimated cause.

[0062] Specifically, the control device 400 automatically performs a diagnosis based on the content of the alarm when the main unit 300 of the charge / discharge device stops, the smoke sensor data inside the device, and measurement data before and after the stoppage, following the self-diagnosis process flow described later. In particular, it has the concept of getting closer to the cause of the failure by conducting interviews with the user in a dialogue format to determine aspects that cannot be determined from the on-site situation, the device's sensors, or data.

[0063] Before explaining the process of self-diagnosing a disability, let me introduce three case studies. [Case 1] (1) During the test, an abnormal noise and odor occurred, causing the main unit 300 of the charge / discharge device to stop. As a result, the abnormality detection unit 484 detected "Abnormality: Stoppage of the main unit of the charge / discharge device". (2) The display 402 shows "Converter malfunction" as an alarm. At this time, the abnormality detection unit 484 identifies "Alarm: Converter malfunction" based on the error code received from the charge / discharge device main unit 300. The event identification unit 486 also asks the questions "Was there an abnormal sound?" and "Was there an abnormal smell?" and obtains "Answer: Abnormal sound present" and "Answer: Abnormal smell present". In this situation, there is a high possibility that the converter is malfunctioning. (4) The control device 400 checks the installation environment of the charge / discharge test system. To this end, the event identification unit 486 asks questions about the number of years elapsed since the charge / discharge test system was installed, the amount of dust at the grounding location, and the humidity, and obtains "Answer: More than 10 years have passed", "Answer: A lot of dust", and "Answer: High humidity". (5) The cause estimation unit 488 estimates "Example cause: Damage to the converter circuit" based on the occurrence event "Abnormality: Stoppage of the main unit of the charge / discharge device", "Alarm: Converter failure", "Answer: Abnormal noise", "Answer: Unusual odor", "Answer: More than 10 years have passed", "Answer: Lots of dust", and "Answer: High humidity". In reality, conductive dust had accumulated inside the converter over many years. Because the power was turned off overnight, condensation occurred inside the converter, leading to insulation failure in the high-voltage circuit. Due to these factors, the circuit short-circuited and was damaged after testing began in the morning. (6) Solution Proposal Unit 490 proposes "Solution: Repair or replace the converter." (7) The warning notice section 492 will announce: "Precautions: Clean the inside of the unit, replace parts that have reached the end of their lifespan, and perform an overhaul," "Precautions: Do not turn off the air conditioning at night," and "Precautions: Do not leave the power ON to prevent condensation."

[0064] [Case Study 2] (1) Because the test cannot be started, the anomaly detection unit 484 detects "Anomaly: Inability to start the test". (2) The alarms "Interlock" and "Thermal Chamber Door Open" are displayed on the display 402. At this time, the abnormality detection unit 484 identifies "Alarm: Interlock" and "Alarm: Thermal Chamber Door Open" based on the error codes received from the charge / discharge device main unit 300 and the thermal chamber 200. (3) The event identification unit 486 asks the questions, "Is the door closed?" and "Are the door fastening bolts tightened?" and obtains the answers, "Answer: The door is closed" and "Answer: The door fastening bolts are tightened." In this situation, there is a high possibility that the door limit switch is damaged. (4) The cause estimation unit 488 estimates the cause to be "Example of cause: Damage to the door limit switch" based on the occurrence event "Abnormality: Inability to start the test", "Alarm: Interlock", "Alarm: Temperature chamber door open", "Answer: The door is closed", and "Answer: The door fastening bolts are tightened". It is possible that the door limit switch was damaged when the secondary battery 100 was inserted or removed. (5) Solution proposal unit 490 proposes "Solution: Replace the limit switch." (6) The warning section 492 displays the following warning: “Caution: Label to warn against hitting the limit switch.”

[0065] [Case Study 3] (1) The control device 400 stopped during the test. At this time, the abnormality detection unit 484 detects "Abnormality: Malfunction of the control device". (2) The display 402 shows "Control device malfunction" as an alarm. At this time, the malfunction detection unit 484 identifies "Alarm: Control device malfunction" from the status of the control device 400. (3) Even when the tester operated the mouse, the control device 400 remained frozen and unresponsive. However, when the power to the control device 400 was turned back on, it recovered. (4) The event identification unit 486 asks the question, "Will it be restored by restarting the power?" and obtains the answer, "Restored by restarting the power." Furthermore, the event identification unit 486 asks about the elapsed time of the charge / discharge test system and obtains the answer, "More than 5 years have passed." (5) The cause estimation unit 488 estimates either "Example 1 cause: HDD (hard disk drive) failure due to aging" or "Example 2 cause: Contact failure of expansion board connector" based on the occurrence event "Abnormality: Malfunction of control device", "Alarm: Control device abnormality", "Answer: Recovery is possible by restarting the power", and "Answer: More than 5 years have passed". (6) The solution proposal unit 490 proposes "Replace the PC (personal computer) of the control unit 400" for "Example 1 cause: HDD failure due to aging," and if that does not solve the problem, it proposes "Solution: Unplug and replug the expansion board" for "Example 2 cause: Contact failure of the expansion board connector" to resolve the contact problem. (7) The warning notification unit 492 will notify "First cause example: HDD failure due to aging" of "Precautions: Check the usage period of the control device 400", "Precautions: Clean the inside of the control device", "Precautions: Run check disk", "Precautions: Run disk defragmentation", and "Precautions: Replace the lifespan of the component (backup battery)".

[0066] Figures 10-13 show the flow chart of the self-diagnosis process for malfunctions. The charge / discharge control unit 482 starts controlling the charge and discharge of the secondary battery 100 for testing (S10). Specifically, the charge / discharge control unit 482 issues instructions to the charge / discharge device main unit 300 according to the test program. While the test is ongoing, the abnormality detection unit 484 repeatedly determines whether or not an abnormality has occurred in the test of the secondary battery 100, based on the information received by the receiving unit 470 and the information input by the operation reception unit 422. If the abnormality detection unit 484 detects an abnormality in the test of the secondary battery 100 (Y in S12), the process proceeds to S20 in Figure 11 via terminal A.

[0067] Until the charge / discharge control unit 482 finishes the test (Y in S14), the anomaly detection unit 484 continues the anomaly detection process (S12).

[0068] Now, let's move on to the explanation of Figure 11. The anomaly detection unit 484 issues an alarm related to the detected anomaly (S20). Specifically, the anomaly detection unit 484 refers to the anomaly response list (Figure 5) and identifies the alarm corresponding to the anomaly. The display processing unit 432 displays that alarm on the display 402.

[0069] The event identification unit 486 adds the abnormality details and alarm type to the event data (Figure 4(B)) as the occurrence event (S22). If a question regarding that abnormality is set in the abnormality response list (Figure 5) (Y in S24), the event identification unit 486 outputs the question and answer candidates (S26). Specifically, the display processing unit 432 displays the question and answer candidates on the display 402.

[0070] The event identification unit 486 accepts the response (S28). Specifically, the examiner operates the input device 404 to select one of the response candidates. The operation reception unit 422 accepts the response based on this user operation. The event identification unit 486 then adds the response type to the event data (Figure 4(C)) as an event that occurred (S30).

[0071] If there are multiple questions, the event identification unit 486 repeats the processing in S24 to S30. If there are no questions, the event identification unit 486 does not perform the processing in S24 to S30. After completing the processing related to the questions, the process moves to S40 in Figure 12 via terminal B.

[0072] The event identification unit 486 may automatically acquire other occurrences depending on the content of the alarm. For example, the event identification unit 486 may acquire values ​​(current values ​​or voltage values) measured by the charge / discharge device main unit 300 to identify occurrences of measurement abnormalities (for example, high current or high voltage) and add them to the occurrences data (Figure 4). The event identification unit 486 may also identify occurrences based on measurement values ​​obtained from the secondary battery 100 or the constant temperature bath 200.

[0073] Let's move on to the explanation of Figure 12. The cause estimation unit 488 estimates the cause of the occurrence by referring to the cause example data (Figure 6) (S40). Specifically, the cause estimation unit 488 identifies cause examples corresponding to the occurrence event (Figure 4). Starting with the first cause example with the highest probability of being applicable, the following are treated as causes for processing.

[0074] The countermeasure proposal unit 490 refers to the countermeasure case data (Figure 7) and identifies the countermeasure corresponding to the cause of the problem (S42). The countermeasures are then processed in order of priority, as follows:

[0075] The solution proposal unit 490 proposes a solution (S44). Specifically, the display processing unit 432 displays the solution on the display 402. The tester implements the solution.

[0076] The solution suggestion unit 490 receives the solution result (S46). Specifically, the tester operates the input device 404 to input the solution result ("resolved" or "unresolved"), and the operation reception unit 422 receives the solution result.

[0077] If the problem is resolved (Y in S48), the cause estimation process by the cause estimation unit 488 and the solution proposal process by the solution proposal unit 490 are completed, and the process proceeds to S60 in Figure 13 via terminal C.

[0078] If the problem is not resolved (N in S48), the solution suggestion unit 490 determines whether there are other solutions in the solution example data (Figure 7). If other solutions remain (Y in S50), the process returns to S44, and the solution suggestion unit 490 proposes the next solution.

[0079] If no other solutions remain (N in S50), the cause estimation unit 488 determines whether there are other cause examples in the cause example data (Figure 6) (S52). If other cause examples remain (Y in S52), the process returns to S40, and the cause estimation unit 488 identifies the next cause of occurrence.

[0080] If no other possible causes remain (N in S52), the cause estimation unit 488 determines that the problem cannot be resolved by the self-diagnosis process (S54). In this case, the display processing unit 432 displays a message on the display 402 prompting the tester to contact the support department because the problem cannot be resolved by the self-diagnosis process. Then, the process proceeds to S60 in Figure 13 via terminal C.

[0081] Now we move on to the explanation of Figure 13. The warning notification unit 492 refers to the warning case data (Figure 8) and determines whether or not there are any warnings corresponding to the cause of the incident (S60).

[0082] If there are any precautions (Y in S60), the caution notification unit 492 notifies the tester of the precautions (S62). Specifically, the display processing unit 432 displays the precautions on the display 402. If there are multiple precautions, the display processing unit 432 displays multiple precautions. If there are no precautions (N in S60), the process proceeds to S64.

[0083] The recording unit 494 stores the maintenance history (Figure 9) in the maintenance history storage unit 452 (S64). The process then proceeds to S14 in Figure 10 via terminal D.

[0084] [Differentiation] In the embodiment described above, an example was shown where the data was divided into items in a table format, but the data does not have to be in a table format. The self-diagnosis process for the failure described above may also be performed by extracting the necessary information from data written in text format.

[0085] Electric vehicles are an example of products that use rechargeable batteries. Rechargeable batteries may also be used in products other than electric vehicles.

[0086] [summary] In this invention, when an abnormality occurs in the charge / discharge test system, the cause of the abnormality is estimated from the events that occurred, using cause case data that describes the cause and the events. Therefore, it becomes easier for the tester to identify the cause.

[0087] Furthermore, because the cause is estimated not just from a single event, but from a combination of multiple events, testers can more accurately identify the cause.

[0088] Furthermore, by including the answers to questions posed to testers as a type of event, it becomes easier to more accurately identify the cause based on information that cannot be measured by sensors.

[0089] Furthermore, the type of alarm determines the questions asked to the tester, and the answers are used to define the events, making it easier to analyze the cause according to the situation.

[0090] Furthermore, by not only estimating the cause of the problem but also proposing countermeasures, it becomes possible to resolve the issue more quickly.

[0091] Furthermore, until the problem is resolved, the system will suggest solutions in order of priority, allowing for a more efficient approach to resolving the issue.

[0092] Furthermore, by informing testers of precautions corresponding to the suspected causes, it becomes easier to prevent abnormalities from occurring.

[0093] Furthermore, when multiple possible causes are considered for an anomaly, the system determines countermeasures in order of the most likely cause, enabling a comprehensive and efficient resolution.

[0094] Furthermore, since testers can view the maintenance history, it becomes easier to analyze anomalies and consider appropriate responses.

[0095] It should be noted that the present invention is not limited to the embodiments and modifications described above, and the components can be modified and implemented without departing from the spirit of the invention. Various inventions may be formed by appropriately combining the multiple components disclosed in the embodiments and modifications described above. In addition, some components may be deleted from all the components shown in the embodiments and modifications described above. [Explanation of Symbols]

[0096] 100 Secondary battery, 102 Power line, 104 Signal line, 200 Constant temperature bath, 300 Charge / discharge device main unit, 400 Control device, 402 Display, 404 Input device, 410 User interface processing unit, 420 Input unit, 422 Operation reception unit, 430 Output unit, 432 Display processing unit, 440 Data storage unit, 442 Occurrence event data storage unit, 444 Anomaly response list storage unit, 446 Cause case data storage unit, 447 Countermeasure case data storage unit, 448 Caution case data storage unit, 449 Maintenance history storage unit, 450 Communication unit, 460 Transmission unit, 470 Receiving unit, 480 Data processing unit, 498 Fault self-diagnosis unit, 482 Charge / discharge control unit, 484 Anomaly detection unit, 486 Event identification unit, 488 Cause estimation unit, 490 Countermeasure proposal unit, 492 Warning / Notification Section, 494 Recording Section, 496 Maintenance History Display Section.

Claims

1. A charge / discharge control unit that controls charging and discharging for testing of secondary batteries, An abnormality detection unit that detects abnormalities related to the aforementioned test, An event identification unit that identifies the event occurring when the aforementioned abnormality is detected, A charge-discharge test system comprising: a cause estimation unit that estimates the cause of the detected abnormality from the identified events by referring to cause example data that defines the correspondence between the cause example that may cause the abnormality and the events that may occur when the abnormality occurs due to the cause example.

2. The aforementioned cause example data associates the aforementioned cause examples with combinations of multiple events. The charge-discharge test system according to claim 1, characterized in that the cause estimation unit estimates the cause of occurrence based on the combination of the specified plurality of events.

3. The charge-discharge test system according to claim 2, characterized in that the event identification unit includes the answer to a question posed to the user as one of the events.

4. The anomaly detection unit issues an alarm related to the detected anomaly. The charge-discharge test system according to claim 3, characterized in that the event identification unit includes the alarm as a type of event, and further obtains the answer by the question relating to the alarm.

5. The charge-discharge test system according to claim 1, further comprising a countermeasure proposal unit that identifies a countermeasure corresponding to the estimated cause of occurrence by referring to countermeasure example data that defines the correspondence between the aforementioned cause example and the countermeasure for said cause example, and proposes said countermeasure to the user.

6. The aforementioned data on countermeasures is obtained by associating multiple countermeasures, which are given priority, with the aforementioned examples of causes. The charge / discharge test system according to claim 5, characterized in that the countermeasure suggestion unit sequentially suggests countermeasures in accordance with the priority order while the abnormality is not resolved.

7. The charge / discharge test system according to claim 1, further comprising a warning notification unit that identifies the warning corresponding to the estimated cause example by referring to warning example data that defines the correspondence between the aforementioned cause example and the warning to the user, and notifies the user of the said warning.

8. The aforementioned cause example data associates multiple cause examples with one of the aforementioned events or a combination of the aforementioned events. The cause estimation unit estimates a plurality of the causes of occurrence by referring to the cause case data, The charge-discharge test system according to claim 2, further comprising a countermeasure proposal unit that identifies a first countermeasure corresponding to a presumed first cause of occurrence, proposes the first countermeasure to the user, and, if the first countermeasure cannot resolve the abnormality, identifies a second countermeasure corresponding to a presumed second cause of occurrence and proposes the second countermeasure to the user.

9. A maintenance history storage unit that stores the maintenance history of the charge / discharge test system, including the cause of the occurrence and the countermeasures taken for that cause; The charge / discharge test system according to claim 1, further comprising a maintenance history presentation unit that presents the aforementioned maintenance history to the user.

10. A computer that controls the charging and discharging for testing secondary batteries, A function to detect abnormalities related to the aforementioned test, A function to identify the event occurring when the aforementioned anomaly is detected, A program characterized by having a function that estimates the cause of the detected abnormality from the identified events by referring to cause example data that defines the correspondence between the cause example that may cause the abnormality and the events that may occur when the abnormality occurs due to the cause example.

Images