JP2014241694A - Charging management device and charging management program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To be capable of managing in more details concerning an operation of a charger of charging to a secondary battery.SOLUTION: The charging management device includes generation means and control means. The generation means generates a log that represents in a time sequence at least one piece of status information representing an implementation status of an operation for charging a secondary battery with a charger. The control means controls a storage device to store the log generated by the generation means.

Description

  Embodiments described herein relate generally to a charge management device and a charge management program.

  In general, the charging operation of the secondary battery in the charger is managed based on instantaneous detection values of voltage, current, temperature, and the like.

  For example, when the detected value of the charging current exceeds a specified value, it is determined that the state is abnormal.

  However, in such a management method, an abnormal state cannot be detected unless a relatively steep change occurs.

JP 2007-18761 A

  In the management based on the instantaneous detection value, the management target is very limited.

  Under such circumstances, it has been desired that more detailed management can be performed regarding the charging operation to the secondary battery in the charger.

  The charge management device of the embodiment includes a generation unit and a control unit. The generation unit generates a log that represents at least one piece of status information representing an implementation status of the operation for charging the secondary battery by the charger in time series. The control unit controls the storage device so as to store the log generated by the generation unit.

The block diagram of the charger system which concerns on one Embodiment. The perspective view of the external appearance of the charger and secondary battery which are shown in FIG. The flowchart of the process by the controller shown in FIG. The flowchart of the log production | generation process by CPU shown in FIG. The schematic diagram of the data structure of a log. The flowchart of the log analysis process by CPU shown in FIG. The block diagram of the charger system as a modification. The schematic diagram of the data structure of the log in a modification.

  Hereinafter, an example of the embodiment will be described with reference to the drawings.

  FIG. 1 is a block diagram of a charger system 100 according to the present embodiment.

  The charger system 100 includes a charger 1, a secondary battery 2, and a charge management device 3.

  The charger 1 charges the secondary battery 2.

  The secondary battery 2 accumulates power supplied from outside and outputs the accumulated power when a load is connected. Any type of secondary battery 2 may be used. For example, a lithium ion type battery is assumed.

  The charge management device 3 manages the implementation status of the charging operation for the charger 1 to charge the secondary battery 2.

  The charger 1 includes a plurality of charge control units 10, a plurality of terminals 11 v, 11 t, 11 g, a plurality of detection circuits 12, a plurality of LEDs (light emitting diodes) 13, an LED driver 14, a power supply circuit 15, a controller 16, and an interface 17. And a bus line 18.

  FIG. 2 is a perspective view of the external appearance of the charger 1 and the secondary battery 2. In FIG. 2, the same elements as those shown in FIG. 1 are denoted by the same reference numerals.

  As shown in FIG. 2, the charger 1 further includes a housing 19. The housing 19 accommodates a plurality of charging controllers 10, a plurality of terminals 11v, 11t, 11g, a plurality of detection circuits 12, a plurality of LEDs 13, an LED driver 14, a power supply circuit 15, a controller 16, an interface 17 and a bus line 18. To do. A plurality of slots 19a are formed in a row on the upper side surface of the housing 19 in a state of being parallel to each other. In FIG. 2, ten slots 19a are illustrated, but the number of slots 19a may be an arbitrary number of one or more. The slot 19a can receive the secondary battery 2 as shown in the figure, and holds the inserted secondary battery 2. The LEDs 13 are arranged in the rows of the slots 19a at almost the same intervals as the slots 19a. The number of LEDs 13 is the same as the number of slots 19a, and the LEDs 13 are positioned in a one-to-one relationship on the sides of the slots 19a.

  A communication port 19 b is formed on the side surface of the housing 19. A plug 4a provided at the end of the communication cable 4 is inserted into the communication port 19b. The communication port 19b physically supports the plug 4a and electrically connects the communication cable 4 and the interface 17.

  The secondary battery 2 includes three electrodes 21v, 21t, and 21g as shown in FIG. Terminals 11v, 11t, and 11g are disposed below the slot 19a, and the terminals 11v, 11t, and 11g are in contact with the electrodes 21v, 21t, and 21g of the secondary battery 2 inserted into the slot 19a. Terminals 11v, 11t, and 11g are connected to the charging control unit 10. Thus, the secondary battery 2 inserted into the slot 19 a is electrically connected to the charge control unit 10. In addition, the charge control part 10 and the terminals 11v, 11t, and 11g are provided with the same number as the slot 19a. As described above, the slot 19a and the terminals 11v, 11t, and 11g constitute a connection port to which the secondary battery 2 can be connected.

  The charging control unit 10 supplies power to the secondary battery 2 by generating a voltage between the terminal 11v and the terminal 11g when the secondary battery 2 is connected and should be charged. To do. The charging control unit 10 includes a status register 10a. The status register 10a stores a plurality of types of status information related to the implementation status of the charging operation. The situation information is roughly classified into setting information and status information. The setting information represents a setting for the charging operation and is written by the controller 16. The status information represents a status related to the charging operation, and is written by the charging control unit 10. As the charging control unit 10, a known device having the above function can be used. As this known device, for example, there is a lithium ion secondary battery charging control IC / MM3439 manufactured by Mitsumi Electric Co., Ltd. (registered trademark). Note that a thermistor voltage that is changed by a thermistor built in the secondary battery 2 is generated between the terminal 11t and the terminal 11g.

  The same number of the detection circuits 12 as the slots 19a are provided, and each of the detection circuits 12 is associated with the slot 19a on a one-to-one basis. Each detection circuit 12 further includes a resistor 12a, an operational amplifier 12b, and an A / D converter 12c.

  The resistor 12a is interposed between the terminal V and the terminal 11v of the charging control unit 10. The resistor 12 a generates a voltage corresponding to the current supplied from the charge control unit 10 to the secondary battery 2. The resistance value of the resistor 12a may be arbitrary, but it is desirable that the resistance value be as small as possible in order to reduce power consumption loss. The resistance value of the resistor 12a is assumed to be 1Ω, for example.

  The differential amplifier 12b outputs a detection signal having a magnitude corresponding to the potential difference between both ends of the resistor 12a.

  The A / D converter 12c digitizes the detection signal output from the differential amplifier 12b to obtain detection information.

  Thus, the detection circuit 12 outputs detection information representing a voltage corresponding to the magnitude of the charging current supplied from the charging control unit 10 to the secondary battery 2.

  The LED 13 displays the implementation status of the charging operation in the corresponding slot 19a according to the lighting state.

  The LED driver 14 drives the LED 13 to realize the above display under the control of the controller 16.

  The power supply circuit 15 obtains the operating power of each part in the charger 1 from the AC power supplied from the commercial power supply via the power cable 15a through DC conversion and voltage conversion, and supplies this to each part.

  The controller 16 has a processor such as a CPU (central processing unit) and controls each unit in the charger 1 according to a program prepared in advance.

  The interface 17 performs processing for the controller 16 to perform communication via the communication cable 4. As the interface 17, for example, a known device such as a USB (universal serial bus) controller can be used. However, the communication method used for communication via the communication cable 4 is not limited to USB, and other serial communication methods and parallel communication methods can be used as appropriate. It is also possible to use a wireless communication system without using the communication cable 4.

  The bus line 18 connects the controller 16, the charging control unit 10, and the LED driver 14 so that communication between them is possible.

  The charge management device 3 includes a CPU 31, a read-only memory (ROM) 32, a random-access memory (RAM) 33, an auxiliary storage device 34, an input device 35, a display device 36, an interface 37, and a bus line 38.

  The CPU 31 corresponds to the central part of the computer. CPU31 controls each part in order to implement | achieve various functions as the charge management apparatus 3 according to an operating system or an application program.

  The ROM 32 corresponds to the main storage portion of the computer. The ROM 32 stores the above operating system and application programs. The ROM 32 may store data necessary for the CPU 31 to execute various processes.

  The RAM 33 corresponds to a main storage part of the computer. The RAM 33 stores data necessary for the CPU 31 to execute various processes as necessary. The RAM 33 is also used as a work area when the CPU 31 performs various processes.

  The auxiliary storage device 34 corresponds to the auxiliary storage portion of the computer. The auxiliary storage device 34 is, for example, an EEPROM (electrically erasable programmable read-only memory), a hard disk drive, or an SSD (solid state drive). The auxiliary storage device 34 stores data used when the CPU 31 performs various processes and data generated by the processes performed by the CPU 31. The auxiliary storage device 34 may store the above application program.

  The input device 35 inputs various instructions by the user. The input device 35 may include various known input devices such as a keyboard and a mouse. Instead of providing the input device 35 in the charge management device 3, a general-purpose input device attached externally may be used instead.

  The display device 36 displays an image for allowing the user to browse various information. As the display device 36, various known display devices such as a liquid crystal display can be used. The display device 36 may not be provided in the charge management device 3 but may be replaced with a general-purpose display device attached externally.

  The interface 37 performs processing for the CPU 31 to perform communication via the communication cable 4. As the interface 37, for example, a known device such as a USB controller can be used.

  The bus line 38 connects the CPU 31, the ROM 32, the RAM 33, the auxiliary storage device 34, the input device 35, the display device 36, and the interface 37 so as to enable communication therebetween.

  The application program stored in the ROM 32 or the auxiliary storage device 34 includes a charge management program including program modules each describing a log generation process and a log analysis process described later. The charge management device 3 is generally transferred in a state where the charge management program is stored in the ROM 32 or the auxiliary storage device 34. However, a charge management program individually assigned to the computer apparatus may be written in a writable storage device included in the computer apparatus in response to an operation by a user or the like. The transfer of the charge management program can be performed by recording on a removable recording medium or by communication via a network. The storage medium may be in any form, such as a magnetic disk, a magneto-optical disk, an optical disk, or a semiconductor memory, as long as it can be read by a reading device built in or connected to the computer device. In addition, as said computer apparatus, general purpose computer apparatuses, such as a personal computer, a general purpose server apparatus, etc. can be utilized.

  Next, the operation of the charger system 100 as described above will be described.

  When the power supply cable 15a is connected to a commercial power supply or when a power switch (not shown) provided in the charger 1 is turned on, the controller 16 is initialized. Is done. If this initialization is completed, the controller 16 starts the processing shown in FIG. Note that the content of the processing described below is an example, and various processing that can obtain the same result can be used as appropriate.

  In Act1, the controller 16 instructs the power supply circuit 15 to start supplying power to the charging control unit 10. In response to this instruction, the power supply circuit 15 starts supplying power to the charge control unit 10.

  In Act 2, the controller 16 initializes the charging control unit 10. At this time, an area for storing status information in the status register 10a is also initialized.

  After the initialization is completed, the charging control unit 10 performs charging for charging the secondary battery 2 if the secondary battery 2 is inserted into the corresponding slot 19a and should be charged. Perform the operation. In performing this charging operation, the charging control unit 10 refers to the setting information stored in the status register 10a.

  Setting information includes, for example, full charge detection setting, charging permission, timer setting, low temperature CV value set, normal temperature CV value set, high temperature CV value set, low temperature CC value set, normal temperature CC value set and high temperature CC value Includes set. In the full charge detection setting, for example, a threshold for detecting full charge is expressed by 2 bits, which is one of “Vref × 1”, “Vref × 2”, “Vref × 3”, and “Vref × 4”. The charge permission represents, for example, prohibition / permission of charging by 1 bit. The timer setting represents, for example, whether the setting related to the timer is 0.25 times, 0.5 times, 1 time, or reset with 2 bits. The low-temperature CV value set, the normal-temperature CV value set, and the high-temperature CV value set include, for example, charging voltage values (CV values) of 4.20V, 4.10V, and 4.10V at low temperatures, normal temperatures, and high temperatures, respectively. Whether it is either 05V or unused is indicated by 2 bits. The low temperature CC value set, the normal temperature CC value set, and the high temperature CC value set are, for example, current values (CC values) during constant current charging at low temperatures, normal temperatures, and high temperatures in increments of 100 mA from “0”. Which of the 21 values up to “2000 mA” is represented by 5 bits. Such setting information is rewritten by the controller 16 as necessary.

  In the charging control unit 10, the status information regarding the implementation status of the charging operation is written in the status register 10a.

  The status information written in the status register 10a includes, for example, a charging state, a reason for charging abnormality, a connection state between the charging voltage terminal and the battery electrode, a connection state between the thermistor voltage terminal and the battery electrode, or a detection result of the battery temperature range. is there. For example, the charge state is represented by 3 bits, for example, any one of charge OFF, battery connection determination, preliminary charge, quick charge, full charge, and recharge. The reason for the charging abnormality is represented by 3 bits, for example, no error, preliminary charging timeout, rapid charging timeout, battery overvoltage, battery overdischarge, battery overcurrent, battery temperature abnormality, or thermal shutdown. For example, one of eight predetermined temperature ranges is represented by 3 bits in the detection result of the battery temperature range. As for the connection state between the charging voltage terminal and the battery electrode, for example, the presence or absence of connection is represented by 1 bit. As for the connection state between the thermistor voltage terminal and the battery electrode, for example, the presence or absence of connection is represented by 1 bit.

  In a situation where the charging operation under the control of the charging control unit 10 as described above is performed as necessary, the controller 16 repeatedly executes a loop of Act3 to Act9 as described below.

  In Act 3, the controller 16 sets “1” to the variable n.

  In Act 4, the controller 16 reads the status information regarding the slot 19a of the slot number n. Here, an integer slot number is assigned in advance from “1” to the plurality of slots 19a, and each of the plurality of slots 19a can be identified by this slot number. Since the plurality of slots 19a and the plurality of charge control units 10 correspond one-to-one, each of the plurality of charge control units 10 can be identified by the slot number. Therefore, the controller 16 reads the status information stored in the status register 10a included in the charge control unit 10 identified from the slot number. In addition, the controller 16 reads detection information related to the charging current of the secondary battery 2 mounted in the slot 19a of the slot number n from the detection circuit 12 associated with the slot 19a of the slot number n.

  In Act 5, the controller 16 controls the LED 13 corresponding to the slot number n. Specifically, based on the status information read in Act 4, the current implementation status of the charging operation related to the slot number n is determined, and the target LED 13 is set to a lighting state representing the implementation status. The LED driver 14 is instructed.

  In Act 6, the controller 16 checks whether or not the determined execution status is an abnormal status. If the situation is abnormal, the controller 16 takes measures such as stopping the charging operation.

  In Act 7, the controller 16 transmits notification information to the charge management device 3 from the interface 17. The notification information is information including the slot number n, the status information and detection information read in Act4, and the date and time when the status information and detection information were read.

  In Act 8, the controller 16 increases the variable n by one.

  In Act 9, the controller 16 checks whether or not the variable n is larger than the number of slots. If it is determined NO because the variable n is equal to or less than the number of slots, the controller 16 returns to Act 4 and executes Acts 4 to 7 for the slot number increased by one as described above. Thus, Acts 4 to 7 are executed sequentially for each of the plurality of slots 19a. Then, after executing Acts 4 to 7 for all of the plurality of slots 19a, the variable n is increased by one in Act 8, so that the variable n becomes a value larger than the number of slots. As a result, the controller 16 determines YES in Act 9. In this case, the controller 16 returns to Act3 and repeats the processes after Act3. That is, the variable n is returned to “1”, and the process of repeating Acts 4 to 7 is executed from the beginning for each of the plurality of slots 19a in order.

  Thus, the controller 16 sequentially reads the status information stored in the plurality of status registers 10a, and transmits notification information associated with the slot number to the charge management device 3.

  When the notification information is transmitted to the charge management device 3 via the communication cable 4, this is detected by the interface 37 and notified to the CPU 31. Upon receiving this notification, the CPU 31 starts the log generation process shown in FIG. 4 according to the charge management program stored in the ROM 32 or the auxiliary storage device 34. Note that the content of the processing described below is an example, and various processing that can obtain the same result can be used as appropriate.

  In Act 11, the CPU 31 receives the notification information via the interface 37.

  In Act 12, the CPU 31 extracts the slot number from the notification information.

  In Act 13, the CPU 31 extracts date and time, status information, and detection information from the notification information, and adds a log element composed of these to the log stored in the auxiliary storage device 34.

  FIG. 5 is a schematic diagram of a log data structure.

  The log includes a plurality of records identified by slot numbers. One record includes an arbitrary number of log elements in addition to the slot number. The log element is configured by a combination of date and time information and the like.

  Therefore, in Act 13, the CPU 31 adds a new log element to the record identified by the slot number extracted in Act 12.

  In this way, a new log updated based on the newly received notification information is generated and written to the auxiliary storage device 34. That is, the CPU 31 functions as a generation unit and a control unit by executing the log generation process. The auxiliary storage device 34 is an example of a storage device for storing a log.

  When the Act 13 ends, the CPU 31 once ends the log generation process. However, since the charger 1 repeatedly transmits notification information, the CPU 31 repeatedly executes log generation processing for each piece of the notification information. As a result, the log is updated sequentially. If the amount of log information is excessive, the amount of processing in log analysis processing described later increases. Therefore, the CPU 31 may perform compression processing on the log. Various known compression processes can be applied as appropriate. For example, if there is no change in the status information of the log element to be newly added to the status information of the log element previously added to the same record, the new log element may not be added to the log. Conceivable. When executing such compression processing, the CPU 31 functions as compression means.

  If the user performs a predetermined operation for requesting the display of the operating state of the charger 1 by using the input device 35, for example, the CPU 31 shows the charging management program stored in the ROM 32 or the auxiliary storage device 34 as shown in FIG. Start the log analysis process. Note that the content of the processing described below is an example, and various processing that can obtain the same result can be used as appropriate. Further, the CPU 31 executes the log analysis process in parallel with the log generation process by executing the log analysis process as a task process different from the log generation process.

  In Act 21, the CPU 31 analyzes the state of the secondary battery 2 based on the log stored in the auxiliary storage device 34.

  For example, the deterioration degree of the secondary battery 2 can be determined from the charging capacity, the charging time, the length of the constant current charging (CC) section, and the like. The charge capacity can be obtained as an area (mA · h) represented by a time change of the charge current profile during rapid charging in a normal state.

  Here, it can be confirmed at which point in time the normal charging operation has been performed by whether or not the reason for abnormal charging included in the status information indicates “no error”. It can be confirmed at which point the quick charge is performed by checking whether or not the state of charge included in the situation information indicates “rapid charge”. Then, the date and time when the normal state quick charge was started as the date and time paired with the first status information in which the reason for the charge abnormality represents “no error” and the charge state represents “rapid charge” ( Start timing). After that, the date and time (end timing) when the quick charge in the normal state is completed can be confirmed by the date and time when the charge state indicates “full charge”.

  On the other hand, among the low temperature CC value set, the normal temperature CC value set, and the high temperature CC value set included in the situation information, the one corresponding to the temperature range represented by the detection result of the battery temperature range included in the situation information is represented. As the CC value, the CC value at each time point can be confirmed. Furthermore, the date and time when the low current control (CC control) is shifted to the low voltage control (CV control) can be confirmed by monitoring the change in voltage represented by the detection information.

  That is, since the voltage represented by the detection information corresponds to the potential difference between both ends of the resistor 12a, the charging current can be obtained by dividing this voltage by the resistance value of the resistor 12a. If this charging current changes below the CC value at that time, it means that the control has shifted to CV control.

  The end date and time of CV control is, of course, the date and time when “full charge” is detected.

  In this way, the lengths of the CC section and the CV section can be detected.

  As described above, the charging capacity, the charging time, the length of the CC section, and the length of the CV section can all be obtained based on the log stored in the auxiliary storage device 34.

  The CC value is appropriately changed by the charge control unit 10 according to the ambient temperature from the viewpoint of safety. Furthermore, when it is determined that a certain amount or more of charge has been performed, the process proceeds to CV charging, and the charging current value is gradually gradually lowered. When the charging current value reaches a certain value or less, the charging control unit 10 determines that the battery is fully charged and the charging is terminated.

  When the secondary battery 2 deteriorates under such prescribed control, the CC section tends to be shortened. In other words, when a sufficient capacity is charged with the deteriorated secondary battery 2, it takes longer to charge than the secondary battery 2 without deterioration. Therefore, the deterioration state of the secondary battery 2 can be roughly determined based on the charging time.

  As another method, the state (mainly abnormal) of the secondary battery 2 can be determined based on the charging voltage. That is, an abnormal state can be diagnosed by how many volts the fully charged voltage of the secondary battery 2 after charging has become with respect to the charging voltage value (CV value).

  In Act 22, the CPU 31 analyzes the state of the charger 1 based on the log stored in the auxiliary storage device 34.

  For example, in the analysis of the charger state, among various information included in the notification information, the charging state, the reason for the charging abnormality, the detection result of the battery temperature range, the connection state between the charging voltage terminal and the battery electrode, the thermistor voltage The connection state between the terminal and the battery electrode, and charging permission can be used.

  These pieces of information are the contents indicated by the values, and the state of the charger 1 can be roughly grasped. That is, based on the state of charge and the reason for abnormal charging, it can be estimated whether charging is being performed normally and what is causing abnormal charging. Further, by referring to the connection state between the charging voltage terminal and the battery electrode and the connection state between the thermistor voltage terminal and the battery electrode, it is possible to know whether or not there is an abnormality in the connection of the battery terminal.

  In Act 23, the CPU 31 generates a result image representing the analysis results in Act 21 and Act 22, and controls the display device 36 to display it. In the result image, events that can be identified from only a single log element, such as overvoltage, overdischarge, overcurrent, and the occurrence date and time of battery temperature abnormality, may be represented.

  In Act 24, the CPU 31 confirms whether or not an instruction has been given by the user. If no determination is made because no instruction is given, the CPU 31 returns to Act 24. Thus, in Act 24, the CPU 31 waits for an instruction from the user. If the user performs a predetermined operation for instruction with the input device 35, the CPU 31 determines YES and proceeds to Act 25.

  In Act 25, the CPU 31 confirms the content of the user instruction. If the user instructs reanalysis, the CPU 31 executes the processes after Act 21 in the same manner as described above. However, since the log is updated by performing the log generation process even during the standby period in Act 24, a new analysis is performed.

  When the CPU 31 is in the standby state for Act 24 and the user instructs to end, the CPU 31 ends the log analysis process.

  Thus, according to the charger system 100, the determination of abnormalities that occur relatively abruptly, such as precharge timeout, quick charge timeout, battery overvoltage, battery overdischarge, battery overcurrent, battery temperature abnormality, or thermal shutdown, is charge control. This is done in part 10.

  On the other hand, in the charge management device 3, a log representing the status information repeatedly acquired with respect to the implementation status of the operation for charging the secondary battery 2 by the charger 1 in time series is generated. By referring to this log, it is possible to determine an abnormality caused by a relatively gradual change such as the deterioration of the secondary battery 2 described above.

  Further, the charge management device 3 further executes processing for determining abnormality by analyzing the log, and displays a result image representing the determination result, so that the user is caused by a relatively gradual change as described above. It is possible to easily recognize the occurrence of abnormalities.

  Further, in the charge management device 3, since the log is generated so that the execution status of the operation for each of the plurality of slots 19a can be distinguished, each of the plurality of slots 19a and the plurality of secondary batteries 2 inserted into them is respectively provided. It is possible to recognize the occurrence status of abnormalities individually.

  By the way, although the charging capacity is an index for determining the deterioration state of the secondary battery 2, it may be difficult to recognize the degree of deterioration based on the charging capacity. However, if the charge capacities for each of the plurality of secondary batteries 2 are obtained as described above, the degree of deterioration can be recognized by comparing them.

  Thus, according to the charge management device 3, more detailed management can be performed with respect to the charging operation to the secondary battery 2 in the charger 1.

  This embodiment can be variously modified as follows.

  The charge management device 3 may collect notification information from the plurality of chargers 1 and generate a log reflecting these information.

  FIG. 7 is a block diagram of a charger system 200 as a modification of the charger system 100. In FIG. 7, the same elements as those in FIG. 1 are denoted by the same reference numerals.

  The charger system 200 includes a plurality of chargers 1, a plurality of secondary batteries 2, a charge management device 3, a communication network 5, a communication device 6, a portable information terminal 7, and a communication device 8.

  As the communication network 5, for example, the Internet, a local area network (LAN), an in-company communication network, or the like can be used as appropriate.

  The communication device 6 is connected to the charger 1 via the communication cable 4 and to the communication network 5. The communication device 6 performs processing for enabling the charger 1 to perform communication via the communication network 5. As the communication device 6, an existing router adapted to the communication method of the communication network 5 can be used.

  The portable information terminal 7 is connected to the charger 1 via the communication cable 4 and can access the communication network 5 via a portable communication network (not shown). The portable information terminal 7 performs processing for enabling the charger 1 to perform communication via the communication network 5. As the portable information terminal 7, an existing mobile phone, a smartphone, a tablet terminal, a mobile router, or the like having a tethering function can be used as appropriate.

  The communication device 8 is connected to the charge management device 3 via the communication cable 4 and is connected to the communication network 5. The communication device 8 performs processing for enabling the charge management device 3 to perform communication via the communication network 5. As the communication device 8, an existing router that is compatible with the communication method of the communication network 5 can be used.

  The connection between the charger 1 and the communication device 6, the connection between the charger 1 and the portable information terminal 7, or the connection between the charge management device 3 and the communication device 8 can be made by wireless connection without using the communication cable 4. There may be.

  In the charger system 200 configured as described above, the charge management device 3 collects notification information transmitted by each of the plurality of chargers 1, and generates and stores a log based on the notification information.

  Therefore, a charger number for identifying each of the plurality of chargers 1 is determined in advance. In each charger 1, the controller 16 includes the charging number of the charger 1 including the controller 16 in the notification information. Other operations in the charger 1 are the same as those in the above embodiment.

  The notification information transmitted from the charger 1 by the controller 16 is sent from the communication device 6 or the portable information terminal 7 to the charge management device 3 to the communication network 5. When the notification information is transmitted to the charge management device 3 side via the communication network 5, the charge management device 3 receives the notification information via the communication device 8.

  In the charge management device 3, the CPU 31 generates a log as shown in FIG. 8, for example, in which the record can be identified by the combination of the charger number and the slot number, and this log is stored in the auxiliary storage device 34. Other operations in the charge management device 3 are the same as those in the embodiment. However, the specific process of the analysis of the battery state or the charger state may be changed to a process adapted to include information on the plurality of chargers 1 in the log.

  According to the charger system 200 modified as described above, it is also possible to manage the charging operation by comparing the tendency of each operation of the plurality of chargers 1, thereby making it possible to trust various diagnoses. It is possible to improve the performance and accuracy.

  For example, since there are variations in the characteristics of the individual chargers 1 and there are changes in the ambient temperature, it is not possible to appropriately determine an abnormality in the operation only from the state of the operation related to one charger 1. In some cases. However, according to the charger system 200, for example, if an average or standard deviation between a plurality of chargers 1 is taken with respect to an arbitrary numerical value included in the log, and various analyzes are performed based on the average or standard deviation, It is possible to perform more appropriate management in consideration of such situations.

  Either or both of the battery state analysis and the charger state analysis may not be performed.

  An image representing the information included in the log as it is may be displayed.

  The execution subject of the log generation process and the log analysis process is not limited to the CPU 31 and may be any hardware having a function of executing information processing based on a program.

  Each function realized by the CPU 31 by the log generation process and the log analysis process can be realized by hardware that executes information processing that is not based on a program such as a logic circuit. Each of the above functions can be realized by combining software control with hardware such as the logic circuit.

  A part or all of the processing for obtaining each function realized by the CPU 31 by the log generation processing and the log analysis processing is performed on the MW (OS (Operating System) running on the computer, database management software, network software, etc. Middleware) or the like.

  The storage medium for storing the charge management program is not limited to one, and the charge management program may be divided into a plurality of program modules, and the plurality of program modules may be distributed and stored in a plurality of storage media.

  Log generation processing and log analysis processing may be realized by distributed processing by a plurality of CPUs. In this case, the plurality of CPUs may be mounted on a single device or may be mounted on a plurality of different devices.

  Although several embodiments of the present invention have been described, these embodiments are presented by way of example and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the scope of the invention. These embodiments and modifications thereof are included in the scope and gist of the invention, and are included in the invention described in the claims and the equivalents thereof.

  DESCRIPTION OF SYMBOLS 1 ... Charger, 2 ... Secondary battery, 3 ... Charge management apparatus, 4 ... Communication cable, 5 ... Communication network, 6 ... Communication device, 7 ... Portable information terminal, 8 ... Communication device, 10 ... Charge control part, 10a ... Status register, 12 ... Detection circuit, 16 ... Controller, 19a ... Slot, 31 ... CPU, 32 ... RAM, 33 ... ROM, 34 ... Auxiliary storage device, 35 ... Input device, 36 ... Display device, 100, 200 ... Charging System.

Claims (6)

Generating means for generating a log representing time series of at least one status information representing an implementation status of an operation for charging a secondary battery by a charger;
A charge management apparatus comprising: a control unit that controls a storage device so as to store the log generated by the generation unit.   The charge management apparatus according to claim 1, further comprising a diagnosis unit that diagnoses at least one of the charger and the secondary battery based on a change with time of the status information represented in the log. The charger includes a plurality of connection ports to which the different secondary batteries can be connected,
The said production | generation means produces | generates the said log as what represents the said status information acquired regarding each of these connection ports with each of the said connection ports by the said charger in time series. The charge management device according to 1 or 2.   The said production | generation means produces | generates the said log as what represents the said status information each acquired by several said chargers in time series in relation with each of these several chargers, The said log | history is produced | generated. The charge management device according to 1. A compression unit for compressing the log;
5. The charge management apparatus according to claim 1, wherein the control unit stores the log compressed by the compression unit in the storage device. 6. A computer that can access the storage device
Generating means for generating a log representing time series of at least one status information representing an implementation status of an operation for charging a secondary battery by a charger;
The charge management program for functioning as a control means to control the storage device so as to store the log generated by the generation means.

Images