The present disclosure is generally related to battery management systems.
A more advanced battery system 200 is shown in
In one embodiment, a battery management system comprising a first circuit comprising a first plurality of circuit elements arranged in series, the first plurality of circuit elements comprising: a direct current (DC) voltage source, and first plural switching devices, each of the first plural switching devices connected to, and operably switched by, a first detection device associated with a battery module to cause a voltage difference responsive to detection of an event corresponding to operation of the battery module.
Many aspects of the systems and methods of the disclosure can be better understood with reference to the following drawings. The components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Moreover, in the drawings, like reference numerals designate corresponding parts throughout the several views.
Disclosed herein are certain embodiments of a battery management (BM) system and method (collectively or individually also referred to herein as a BM system) where data transmission through communication protocols, such as RS485 or controller area network (CAN), is replaced by analog means such as voltage detection. One or more embodiments of a BM system as disclosed herein possess a highly durability to noise since all signal detection is isolated to a main high-power carrying circuit (e.g., loop) by one or more switching devices (e.g., latch relays, etc.). Hence, one or more embodiments of a BM system establish a high voltage battery system that may exhibit simplicity (e.g., easy for maintenance, and may be available as a plug-and-play architecture in view of the absence of complicated communications), reliability (e.g., durable in service life), and/or affordability (e.g., cost effective).
Though certain embodiments of BM systems are described herein in the context of use with lithium ion batteries (e.g., lithium iron phosphorous batteries), it should be understood by one having ordinary skill in the art that the applicability of the BM systems disclosed herein is not limited to any particular type of battery system and hence other types of battery systems are contemplated to be within the scope of the disclosure.
Referring to
Associated with each of the switching devices 308 is a battery module, such as battery modules 310. The battery modules 310 may be of a similar configuration as that described in association with
Each battery module 310 powers (e.g., exclusively) one or more detection devices, such as detection devices 312. Each detection device 312 is connected to the respective switching device 308. In one embodiment, the detection device 312 may be an over charge/over discharge (OC/OD) detection device, which as the name implies, provides for charge/over discharge alarm detection. In some embodiments, the OC/OD device 312 may be replaced with another types, or types, of detection devices. Each OC/OD detection device 312 is used to monitor the voltages of each battery set connected (e.g., in series) within each battery module 310. For instance, in one embodiment, four (4) or eight (8) channels may be available in the monitoring function, although other quantities may be involved in some embodiments. In the case of eight (8) channels, eight (8) channels uses a total of nine (9) cables (e.g., though in some embodiments, a wireless configuration may be used) to detect the voltages of eight (8) cells or eight (8) battery sets connected in series. If any of the channels exceeds (or declines below) a given threshold (e.g., over charge or over discharge threshold), a voltage is provided by the OC/OD detection device 312 to the switching device 308 to drive the switching device open or close. In some cases, a reset current may be used to reset the over charge/over discharge boards (e.g., the OC/OD detection device 312) if a switching device 308 was opened previously. In other cases, if a known automatic resume function is available, then no reset activity (passing a reset current) should be necessary.
Each of the switching devices 308 in the circuit 302 (e.g., loop) is controlled by an associated “parasitic” detection device, such as the OC/OD detection device 312, and each battery module 310 may be implemented in some embodiments with one or more parasitic devices. Parasitic refers herein to the absence of ECU control (i.e., no ECU control is needed) and, in one embodiment, such parasitic devices are only powered by the batteries in the battery module 310. The parasitic devices may generate alarm signals to the ECU 304. As is explained in further detail below, examples of parasitic devices include, without limitation, the OC/OD detection devices 312, cell balancing devices, and temperature monitoring devices. Since the switching device 308 behaves as an electrical isolator, the 12V loop circuit 302 is isolated from the battery modules 310 connected in series, and thus no noise interference through each of the battery modules 310 is possible. In the example depicted in
Connections 322 and 324 between the switching devices 308 and the ECU 304 (e.g., between the ECU 304 and the first switching device 308 shown at the extreme left hand side of
Referring now to
Using a similar method to that employed for OC/OD monitoring, the temperature monitoring device 410 may be implemented in a separate circuit (e.g., the circuit 402 as compared to circuit 302) yet use the same voltage source 306. If any of the switching devices 408 of the circuit 402 is triggered by the temperature monitoring device 410, the ECU 304 detects a voltage difference according to the voltage across the source 306 (e.g., 12V in this example). Using the circuits 302 and 402 and corresponding circuit elements, the ECU 304 is able to identify the event (e.g., overcharge or over discharge, excessive temperature) that is detected by either the OC/OD detection devices 312 or the over temperature monitoring devices 410. Note that although two circuits (e.g., loops) are illustrated in
Note that the ECU 304 (or other controller, such as a controller board as described below) may be configured in some embodiments to carry out one or more of the following functions: accept an alarm for overcharge/over discharge of the battery sets; accept an alarm for over temperature of the battery modules; provide control of the switching devices implemented in the circuit that carries high power (the number of switching devices needed depending, for instance, on the safety considerations and can be configured with one or more, such as one for every battery module 310; and optionally, control of fans implemented for each of the battery modules 310.
Further, in one embodiment, the outputs generated by the battery modules 310 may include one or more of the following: the alarm signal of over charge or over discharge; the alarm signal of over temperature.
Referring now to
Attention is now directed to
The BM system 700 comprises cables 702 (e.g., 702A-702G) connected between each of the switching devices 308 and the ECU 304. In such a configuration, the ECU 304 is enabled to detect which switching device 308 is open by monitoring the voltage difference between each switching device. In the example depicted in
In
Note that in some embodiments, the 12V voltage source 306 used as an example throughout the disclosure may be replaced by batteries other than 12V if the current flowing through the circuit (e.g., 302) that connects the switching devices (e.g., 308) is sustainable. In some embodiments, the 12V voltage source 306 may be connected to a converter that converts high voltage (e.g. 316.8V) down to 12V, provided normal operation of the ECU 304 is unaffected (e.g., to any significant degree).
In some embodiments, a light-emitting diode (LED) may be included in series with a resistor and connected across each of the terminals of the switching devices (e.g., 308, the two terminals illustrated more clearly in
In certain embodiments of BM systems described herein, it is noted that the ECU 304 does not need to know all details of activities of each battery set. For example, the ECU 304 is concerned with activities to be taken when alarm signals are generated by the battery modules 310. From this perspective, complicated communications between the battery modules may be replaced by simple mechanical signals, such as voltages, and thus may be very reliable for long service life and also free from noises coming from an inverter, motor, or a high voltage-low voltage converter, among other sources of noise. In other words, the functions for the ECU 304 and the battery modules 310 described above are important for a high voltage battery system. However, in some embodiments, more sophisticated functions may be employed as well. Similarly, in some BM system embodiments, some functions described above may be omitted, and/or in some embodiments, features shown and described in association with the above-described figures may be mixed and matched.
Having described various embodiments of BM systems, some example implementations are described below to illustrate the utility of certain BM systems. In an example employing a BM system in an electric vehicle (EV), the following is assumed: (a) three (3) 18Ah cells are connected in parallel to form a 54Ah battery set; (b) sixteen (16) sets are connected in series to form a battery module (e.g., module 310); (c) six (6) battery modules are connected in series to form a battery system (similar to the arrangement illustrated in, for instance,
Now referring to an example operation, during driving, when any of the battery sets of one or more modules (e.g., 310) is low in voltage, an over discharge signal is generated by the associated OC/OD detection board. As a consequence, the switching device connected to the OC/OD detection board is opened, and responsively, the ECU detects a voltage difference from 12V to 0V and the ECU starts limiting the current to a motor until the vehicle is parked safely.
During charging, when any of the battery sets is high in voltage, an over charge signal is generated by the OC/OD detection board. As a consequence, the switching device connected to the OC/OD detection board is opened, and responsively, the ECU detects a voltage difference from 12V to 0V and the ECU starts limiting the charge current until the OC/OD detection board is resumed and the switching device connected to the OC/OD detection board closes again. The same activity is repeated until a preset charging voltage (e.g. 340V) is achieved. For instance, the charger may be resumed at a lower voltage (e.g. 318V) until the charger is removed from the vehicle.
In another example, such as for a BM system employed in a PHEV, the following is assumed: (a) three (3)18Ah cells are connected in parallel to form a 54Ah battery set; (b) sixteen (16) sets are connected in series to form a battery module; (c) six (6) battery modules are connected in series to form a battery system; (d) in each of the battery modules, two 8-channel OC/OD detection boards, four 4-channel balance boards, and one 8-channel temperature monitoring board are installed (as mentioned earlier, all these devices are parasitic); (e) all switching devices connected to the OC/OD detection boards are connected in series to form a first loop (e.g., a total of twelve (12) switching devices); and (f) all switching devices connected to the temperature monitoring boards are connected in another series that forms a second loop (e.g., a total of six (6) relays). In this example, a BM system similar to the BM system 700,
In one example operation, during driving, when any of the battery sets is low in voltage, an over discharge signal is generated by the OC/OD detection board. As a consequence, the switching device connected to the OC/OD detection board is opened, and responsively, the ECU detects a voltage difference from 0V to 12V and thus starts a genset (e.g., diesel electric generator) for recharging the battery system. The ECU may be further configured to present for display “maintenance required” on a screen of a display device once such problem is generated frequently when overall battery system is still high but the same module keeps showing over discharge problems.
During charging, when any of the battery sets is high in voltage, an over charge signal is generated by the OC/OD detection board. As a consequence, the switching device connected to the OC/OD detection board is opened. At this moment, the ECU detects a voltage difference from 0V to 12V and the ECU starts limiting the charging current either coming from the genset or the charger until the over OC/OD detection board is resumed and the switching device connected to the over OC/OD detection board closes again.
If the vehicle is “ON”, that means the charging is coming from the genset, so the genset is not triggered until the next time there is a condition of low in battery capacity (which may be monitored through a state of charge (SOC) monitor or through the determination of the battery system voltage). If the vehicle is in an “OFF” mode, the same charging activity may be repeated until a preset charging voltage (e.g. 340V) is achieved. For instance, the charger is resumed at a lower voltage (e.g. 318V) until the charger is removed from the vehicle. The ECU may be further designed to show “maintenance required” once such problem is generated frequently when overall battery system is still low but the same module keeps showing over charge problems. It should be noticed that all the functions' design can be conducted by the ECU, which may not be directly related to the battery system itself in some embodiments.
The examples described above are useful in demonstrating that certain BM system embodiments may work well for high voltage applications, such as in EV, PHEV, or HEV. It should be understood that certain BM system embodiments may be applicable to any applications that need high voltages, that possess several battery modules connected in series, and that require an ECU or PLC (or other) control for the applications.
In view of the above-description of certain embodiments of BM systems, it should be appreciated that one method embodiment, depicted in
Note that alternate implementations may be included within the scope of the disclosure, in which functions may be executed out of order from that shown or discussed in association with
It should be emphasized that the above-described embodiments of the present disclosure are merely possible examples of implementations, merely set forth for a clear understanding of the principles of the BM system and method embodiments. Many variations and modifications may be made to the above-described embodiment(s) without departing substantially in spirit and principles. All such modifications and variations are intended to be included herein within the scope of this disclosure and protected by the following claims.
Number | Name | Date | Kind |
---|---|---|---|
5391974 | Shiojima et al. | Feb 1995 | A |
5477126 | Shiojima | Dec 1995 | A |
5747970 | Johnson et al. | May 1998 | A |
5898291 | Hall | Apr 1999 | A |
6060864 | Ito et al. | May 2000 | A |
6064178 | Miller | May 2000 | A |
6236216 | Shimoyama et al. | May 2001 | B1 |
6271645 | Schneider et al. | Aug 2001 | B1 |
6291972 | Zhang | Sep 2001 | B1 |
6461764 | Nakamura | Oct 2002 | B1 |
6465986 | Haba | Oct 2002 | B1 |
6511764 | Marten | Jan 2003 | B1 |
6586909 | Trepka | Jul 2003 | B1 |
6642693 | Anzawa et al. | Nov 2003 | B2 |
6700350 | Formenti et al. | Mar 2004 | B2 |
6777908 | Thorne et al. | Aug 2004 | B2 |
6784638 | Yang | Aug 2004 | B2 |
6801014 | Chitsazan | Oct 2004 | B1 |
6825638 | Kim | Nov 2004 | B2 |
6841971 | Spee et al. | Jan 2005 | B1 |
6873134 | Canter et al. | Mar 2005 | B2 |
6882129 | Boskovitch et al. | Apr 2005 | B2 |
6891352 | Miyazaki et al. | May 2005 | B2 |
6933728 | Kim | Aug 2005 | B2 |
7061207 | Patel et al. | Jun 2006 | B2 |
7068011 | Yang | Jun 2006 | B2 |
7262605 | Seo et al. | Aug 2007 | B2 |
7508166 | Ishikawa et al. | Mar 2009 | B2 |
7598706 | Koski et al. | Oct 2009 | B2 |
7772799 | Wu | Aug 2010 | B2 |
7777451 | Chang et al. | Aug 2010 | B2 |
7782013 | Chang | Aug 2010 | B2 |
7808207 | Chang | Oct 2010 | B1 |
7821227 | Howell | Oct 2010 | B2 |
7821231 | Chang et al. | Oct 2010 | B1 |
7825632 | Chang | Nov 2010 | B1 |
8130000 | Botker et al. | Mar 2012 | B2 |
8350529 | Loncarevic | Jan 2013 | B2 |
8659261 | Pariseau et al. | Feb 2014 | B2 |
8872380 | Shim | Oct 2014 | B2 |
20040209161 | Dubac et al. | Oct 2004 | A1 |
20050029986 | Morgan | Feb 2005 | A1 |
20050134232 | Yamamoto | Jun 2005 | A1 |
20050231169 | Seo et al. | Oct 2005 | A1 |
20060186859 | Fujikawa et al. | Aug 2006 | A1 |
20070018780 | Furukawa et al. | Jan 2007 | A1 |
20080084182 | Oberlin et al. | Apr 2008 | A1 |
20080180106 | Gorbold | Jul 2008 | A1 |
20080258683 | Chang | Oct 2008 | A1 |
20100121511 | Onnerud | May 2010 | A1 |
20100253278 | Chang et al. | Oct 2010 | A1 |
20100315037 | Aiura et al. | Dec 2010 | A1 |
20120313560 | Hambitzer et al. | Dec 2012 | A1 |
20130066572 | Terashima et al. | Mar 2013 | A1 |
Number | Date | Country |
---|---|---|
1933443 | Jun 2008 | EP |
Entry |
---|
International Search Report and Written Opinion, mailed Jun. 22, 2012. |
Number | Date | Country | |
---|---|---|---|
20120248881 A1 | Oct 2012 | US |