Patent Grant
8659261
The present invention relates to managing batteries for electric vehicles. More specifically, the present invention relates to registering battery pack components in a battery pack using an enumeration method.
For a multitude of reasons, it is advantageous to use electric vehicles having rechargeable batteries rather than vehicles using internal combustion engines. Electric vehicles are inherently more efficient, meaning more energy is used in locomotion than lost to heat than in conventional internal combustion engines. Also, electric vehicles do not exhaust any byproducts. However, the use of electric vehicles presents technical challenges. For example, the batteries in an electric vehicle must be monitored and managed. Electric vehicles having modular batteries can be particularly challenging, as they have multiple batteries or battery packs that must be monitored and managed.
The present invention introduces a method and system of registering battery pack components, such as Battery-Monitoring-Units (BMUs) that are configured to sense various battery module conditions. The present invention allows a user to register these battery pack components with a Battery-Management-System (BMS) using an enumeration method. As a result, a configuration table can easily be established, providing a linkage between the virtual address of the battery pack components and their physical setup.
In one aspect of the present invention, a method of registering a plurality of BMUs in a battery pack with a BMS is provided. The method comprises providing an indication to a user, wherein the indication prompts the user to register one of the BMUs with the BMS. The user then performs an action on a communication-initiating mechanism on one of the BMUs, wherein the communication-initiating mechanism is configured to initiate the sending of a communication by the BMU to the BMS in response to the user performing the action. The BMU sends a communication to the BMS in response to the user performing the action on the communication-initiating mechanism. The BMS receives the communication from the BMU, and the BMS registers the BMU in response to receiving the communication from the BMU.
In some embodiments, the steps of providing an indication, the user performing an action, the BMU sending a communication, the BMS receiving the communication, and the BMS registering the BMU are repeated for each BMU in the plurality of BMUs.
In some embodiments, the battery pack comprises a plurality of battery stacks, with each battery stack comprising a plurality of batteries. In some embodiments, each BMU corresponds to and is coupled to a distinct battery stack in the plurality of battery stacks, with each BMU being configured to monitor data about the plurality of batteries in the corresponding battery stack. In some embodiments, the BMS is coupled to the plurality of BMUs via a communication bus, wherein the BMS is configured to receive battery data from the BMUs and to send one or more commands to the BMUs via the communication bus. In some embodiments, the communication bus is a Controller-Area-Network (CAN) bus.
In some embodiments, the step of the BMS registering the BMU comprises the BMS storing a linkage between a virtual ID of the BMU and the physical configuration of the BMU. In some embodiments, the physical configuration of the BMU comprises identification of the batteries to which the BMU corresponds. In some embodiments, the linkage is stored in a lookup table. In some embodiments, the virtual ID is a CAN ID.
In some embodiments, the communication sent from the BMU to the BMS comprises a serial number that is unique to the BMU, and the step of the BMS registering the BMU comprises the BMS storing the serial number for the BMU.
In some embodiments, the communication-initiating mechanism is a push-button. In some embodiments, the step of providing an indication to a user comprises displaying an instruction on a screen.
In another aspect of the present invention, a registration system is provided. The registration system comprises: a plurality of battery stacks, each battery stack comprising a plurality of batteries; a plurality of BMUs, each BMU corresponding to and being coupled to a distinct battery stack in the plurality of battery stacks, wherein each BMU comprises a communication-initiating mechanism configured to initiate the sending of a communication in response to a user performing an action on the communication-initiating mechanism; and a BMS coupled to the plurality of BMUs, wherein the BMS is configured to receive the communication and to register the BMU from which it received the communication in response to receiving the communication.
In some embodiments, each BMU is configured to monitor data about the plurality of batteries in the corresponding battery stack, and the BMS is coupled to the plurality of BMUs via a communication bus, wherein the BMS is configured to receive battery data from the BMUs and to send one or more commands to the BMUs via the communication bus. In some embodiments, the communication bus is a CAN bus.
In some embodiments, the BMS is configured to register the BMU by storing a linkage between a virtual ID of the BMU and the physical configuration of the BMU. In some embodiments, the physical configuration of the BMU comprises identification of the batteries to which the BMU corresponds. In some embodiments, the linkage is stored in a lookup table. In some embodiments, the virtual ID is a CAN ID.
In some embodiments, the communication sent from the BMU to the BMS comprises a serial number that is unique to the BMU, and the BMS is configured to register the BMU by storing the serial number for the BMU.
In some embodiments, the communication-initiating mechanism is a push-button. In some embodiments, the system further comprises means for providing an indication to a user, wherein the indication prompts the user to register one of the BMUs with the BMS. In some embodiments, the means for providing an indication comprises a screen.
In yet another aspect of the present invention, a program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine to register a plurality of BMUs in a battery pack with a BMS is provided. The method comprising the steps of: providing an indication to a user, wherein the indication prompts the user to register one of the BMUs with the BMS; and registering the BMU with the BMS in response to the BMS receiving a communication from the BMU.
In some embodiments, the steps of providing an indication and registering the BMU are repeated for each BMU in the plurality of BMUs.
In some embodiments, the step of registering the BMU with the BMS comprises the storing a linkage between a virtual ID of the BMU and the physical configuration of the BMU. In some embodiments, the physical configuration of the BMU comprises identification of the batteries to which the BMU corresponds. In some embodiments, the linkage is stored in a lookup table. In some embodiments, the virtual ID is a CAN ID.
In some embodiments, the step of registering the BMU with the BMS comprises storing a serial number for the BMU.
In some embodiments, the step of providing an indication to a user comprises displaying an instruction on a screen.
The following description is presented to enable one of ordinary skill in the art to make and use the invention and is provided in the context of a patent application and its requirements. Various modifications to the described embodiments will be readily apparent to those skilled in the art and the generic principles herein may be applied to other embodiments. Thus, the present invention is not intended to be limited to the embodiment shown but is to be accorded the widest scope consistent with the principles and features described herein.
Various aspects of the disclosure may be described through the use of flowcharts. Often, a single instance of an aspect of the present disclosure may be shown. As is appreciated by those of ordinary skill in the art, however, the protocols, processes, and procedures described herein may be repeated continuously or as often as necessary to satisfy the needs described herein. Additionally, it is contemplated that certain method steps of the invention can be performed in alternative sequences to those disclosed in the flowcharts. Accordingly, the scope of the claims should not be limited to any specific order of method steps unless the order is required by the language of the claims.
In some embodiments, the present invention may be provided as a computer program product that may include a machine-readable medium having stored thereon instructions that may be used to program a computer (or other electronic devices) to perform a process according to the present invention. The machine-readable medium may include, but is not limited to, floppy diskettes, optical disks, CD-ROMs, ROMs, RAMs, magnet or optical cards, or other type of media/machine-readable medium suitable for storing electronic instructions.
BMS 110 is configured to communicate with several external modules. Each module is in communication with at least some of the full complement of battery packs available on the electric vehicle. The communication with the modules is enabled by communication bus 140, preferably as part of a Controller-Area-Network (CAN) 150. A CAN is a bus standard designed to allow microcontrollers and devices to communicate with each other within a vehicle without a host computer. CAN is a message based protocol, designed for automotive applications, as well as industrial automation and medical equipment. Advantageously, the CAN 150 enables the system 100 as a hardware-oriented system and provides a quasi-real-time link between controllers to allow for a distributed control system.
The first of the external modules communicating with the BMS 110 is HVFE 120. In series with the HVFE 120 are a plurality of BMUs 121-132. Each BMU 121-132 is electrically coupled to a battery stack 121A-132A. For example, the first BMU 121 is electrically coupled to a stack of batteries 121A. In the exemplary embodiment shown, the each stack of batteries 121A-132A has four batteries. In other embodiments, the BMU 121 has ports to electrically couple to 12 batteries. In some embodiments, each battery stack has one dedicated BMU and comprises several battery cells that are arranged in both parallel and series. In some embodiments, some of the battery stacks have two corresponding BMUs. It is contemplated that other battery cell numbers and configurations are within the scope of the present invention.
The BMUs 121-132 each monitor their respective battery stack 121A-132A and are configured to sense various battery module conditions, such as cell-group voltage, temperature, current, and other useful data of each stack and to report the data to the BMS 110. The HVFE 120 is electrically coupled to all battery stacks 121A-132A and is able to measure parameters like the total current, voltage, and power either produced or received by the battery stacks 121A-132A. For example, in some embodiments, the BMUs 121-132 are each configured to measure the voltage of the stack of batteries that the BMU is electrically coupled to, on the order of 1-10V per cell-group in some embodiments, and the HVFE 120 is configured to measure the entire voltage of all battery stacks 121A-132A, on the order of 320V in some embodiments. The HVFE 120 is then able to perform a current integration to calculate the total discharge from the battery modules 121A-132A in coulombs to determine the remaining charge relative to the total output voltage that the HVFE 120 is measuring.
In some embodiments, the BMS 110 sends commands to and requests information from the battery module components, such as the HVFE unit 120 or the BMUs 121-132, via the communication bus 140. Furthermore, in some embodiments, the communication bus 140 is used to send battery data from the battery module components to the BMS 110. Additionally, in some embodiments, commands and requests are also sent from one or more of the battery module components to the BMS 110, while data is sent from the BMS 110 to one or more of the battery module components. For example, a BMU or HVFE unit can request a new program image. In this case, the request would be issued from the BMU/HVFE unit and the data (i.e., program image) would be sent from the BMS 110. Other examples include the transmission of configuration tables or other data from the BMS 110 to a BMU/HVFE unit and requests for assignment of dynamic bus identifications from a BMU/HVFE unit to the BMS 110.
In some embodiments, the HVFE 120 comprises intelligence, such as a microprocessor and memory that holds a look up table for relation of remaining coulombs of charge in the batteries and the output voltage, and can therefore output a total remaining distance or time that the electric vehicle. Alternatively, the intelligence is on board the BMS 110 or elsewhere in the electric vehicle. The CAN 150 comprises a second bus line 160 that electrically couples the BMS 110 with the electric vehicle (not shown). The BMS 110 can send battery data to a vehicle display (not shown), and instructions and data can be sent to the BMUs 121-132 from the electric vehicle. For example, the electric vehicle may ping the BMS 110 to retrieve battery data from the BMUs 121-132. Alternatively, an instruction can require the BMUs 121-132 to continually broadcast their status.
The present invention provides a system and method of registering the battery module components, such as the BMUs and the battery cells, with the BMS using an enumeration method. As a result, a configuration table, such as a look-up table, can easily be established linking the virtual address of the battery module components with their physical setup. The configuration table can store a variety of information about the battery pack's configuration, such as how many module boards are in the battery pack (e.g., 8 module boards), how many BMUs are on each module board (e.g., 1 BMU on each of the first 4 module boards and 2 BMUs on each of the last 4 module boards), how many battery cells in series the battery pack has (e.g., 100 battery cells in series), how many battery cells in parallel the battery pack has (e.g., 32 battery cells in parallel), and which particular BMU corresponds to which particular module board and to which particular battery cells in the battery pack (e.g., BMU number 5 corresponds to: module board number 5, in-series battery cells 37-44, and in-parallel battery cells 1-8).
The present invention enables the establishment of the configuration table without the burden of creating custom BMUs. Instead of custom BMUs, the present invention allows for the BMUs to be manufactured identically, both in terms of their hardware and firmware. An enumeration method is used to register the battery module components with the BMS. Each BMU comprises a communication-initiating mechanism that is configured to initiate the sending of a communication in response to a user performing an action on the communication-initiating mechanism. For example, in
Before the configuration table is built, the BMS does not know where each BMU is physically located and to which battery cells each BMU corresponds. However, the human user or operator does know these details. The user is prompted to register a particular BMU with the BMS. The user then performs an action on the communication-initiating mechanism of that particular BMU, such as by pushing the push-button. In response to its communication-initiating mechanism being acted upon, the BMU sends a communication to the BMS, registering the BMU information with the BMS. In this fashion, the BMS can receive BMU information for each BMU in the battery pack. In some embodiments, each BMUs CAN ID is used to build the configuration table. In some embodiments, this communication includes the details of the battery cells to which the BMU corresponds (e.g., how many in-series battery cells, how many in-parallel battery cells, etc.). In some embodiments, each BMU has its own unique serial number that is sent to the BMS when the communication-initiating mechanism is activated, and the serial number is used to build the configuration table.
The present invention uses this enumeration method of prompting the user to initiate a communication from each BMU to the BMS, one by one, in order to build a configuration table in the BMS without the need for excessive setup and maintenance. As a result of this enumerative registration, it is not necessary to pre-code the BMS with a configuration table, which would then require a recoding of the BMS when the battery pack is changed. Therefore, the present invention simplifies the setup and maintenance of the BMS.
It is contemplated that the prompting of the user can be achieved in a variety of ways. In some embodiments, a computer 115 is connected to the BMS 110. This computer 115 can be a laptop, a dedicated system, or a variety of other suitable computing means. Software on the computer 115 is used to prompt the user to initiate a communication from each BMU to the BMS. For example, the software can instruct the user to press the button on the first BMU of the first module. Once the user presses the button (or otherwise activates the communication-initiating mechanism) on the appropriate BMU, the software then instructs the user to press the button on the second BMU, and so on and so forth until each one of the BMUs has had its button pressed. In some embodiments, each BMU has a light (not shown) that blinks until the user presses the button on the BMU, at which point, the blinking light goes away, thus making it easy for the user to see which BMUs have not yet been registered.
In some embodiments, the prompting is displayed on the screen of the computer 115. In some embodiments, the software is loaded onto the BMS and the prompting is displayed on a screen on the BMS. In some embodiments, the registration communications sent by the BMUs upon the actuation of the communication-initiating mechanisms are sent to the computer 115 prior to the BMS. The computer 115 then builds the configuration table using the registration communications, and loads the configuration table onto the BMS. In other embodiments, the registration communications are sent to the BMS where they are used to build the configuration table without the assistance of a computer that is external to the BMS.
At step 210, the battery component registration system, such as battery component registration system 100 discussed above, is provided having a BMS and a plurality of battery module components, such as a plurality of BMUs and corresponding battery stacks. In some embodiments, the system 100 may be coupled to a vehicle at this stage. In other embodiments, the system 100 may not yet be coupled to a vehicle at this stage. A user is prompted to register a particular BMU with the BMS. As discussed above, such prompting may be provided in the form of an instruction displayed on a screen on the BMS or on a computer external to the BMS.
At step 220, the user performs an action on a communication-initiating mechanism that is connected to the particular BMU. As discussed above, the communication-initiating mechanism can be provided in a variety of different forms, including, but not limited to, a push-button or switch mechanism. The action performed on the communication-initiating mechanism by the user can be the pressing of a button or any other form of actuating or activating a mechanism.
At step 230, the BMU sends a communication to the BMS. As discussed above, this communication includes information related to the BMU for use in building the configuration table. In some embodiments, this information is configured to be used in providing a linkage between a virtual ID of the BMU and the physical configuration of the BMU. In some embodiments, this information includes the BMU's CAN ID. In some embodiments, this information includes the BMU's unique serial number. In some embodiments, this information includes the details of the battery cells to which the BMU corresponds (e.g., how many in-series battery cells, how many in-parallel battery cells, etc.).
At step 240, the BMS receives the communication from the BMU. As discussed above, in some embodiments, the communication is sent to an external computer, for the establishment of the configuration table, prior to the BMS. However, the communication is preferably sent to the BMS without going through a computer external to the BMS.
At step 250, the BMS registers the BMU. As previously mentioned, a configuration table, such as a look-up table, is created in or loaded onto the BMS. The BMS registers the linkage between the virtual address of the BMUs and their physical setup. In some embodiments, the BMS registers each BMU's unique serial number. In some embodiments, the BMS registers each BMU's CAN ID. In some embodiments, the BMS registers the details of the battery cells to which each BMU corresponds (e.g., how many in-series battery cells, how many in-parallel battery cells, etc.). In some embodiments, the BMS registers each BMU one by one after each registration communication is sent by a BMU. In some embodiments, the BMS registers all of the BMUs together after all of the BMUs have sent the registration communications to a computer external to the BMS.
At step 260, it is determined whether or not there is another BMU that needs to be registered with the BMS. If it is determined that another BMU that needs to be registered with the BMS, then the method repeats at step 210, where the user is prompted to register the next BMU. If it is determined that there is not another BMU that needs to be registered with the BMS, then the method ends.
The present invention has been described in terms of specific embodiments incorporating details to facilitate the understanding of principles of construction and operation of the invention. Such reference herein to specific embodiments and details thereof is not intended to limit the scope of the claims appended hereto. It will be readily apparent to one skilled in the art that other various modifications may be made in the embodiment chosen for illustration without departing from the spirit and scope of the invention as defined by the claims.
This application claims priority to U.S. Provisional Patent Application Ser. No. 61/364,313, filed Jul. 14, 2010 and entitled “BATTERY MONITOR SYSTEM FOR AN ELECTRIC VEHICLE,” which is hereby incorporated by reference in its entirety as if set forth herein.
| Number | Name | Date | Kind |
|---|---|---|---|
| 2258221 | Rochow | Oct 1941 | A |
| 4135593 | Fowkes | Jan 1979 | A |
| 4652964 | Zigenbein | Mar 1987 | A |
| 4862243 | Welch et al. | Aug 1989 | A |
| 5059895 | Cataldi et al. | Oct 1991 | A |
| 5158841 | Mennicke et al. | Oct 1992 | A |
| 5207276 | Scofield | May 1993 | A |
| 5227259 | Weaver et al. | Jul 1993 | A |
| 5534759 | Evans et al. | Jul 1996 | A |
| 5542488 | Nixon | Aug 1996 | A |
| 5608304 | Okumura | Mar 1997 | A |
| 5624003 | Matsuki et al. | Apr 1997 | A |
| 5670861 | Nor | Sep 1997 | A |
| 5767659 | Farley | Jun 1998 | A |
| 5806618 | Luode | Sep 1998 | A |
| 5815824 | Saga et al. | Sep 1998 | A |
| 5834132 | Hasegawa et al. | Nov 1998 | A |
| 5861610 | Weiss | Jan 1999 | A |
| 5903154 | Zhang et al. | May 1999 | A |
| 5929741 | Nishimura et al. | Jul 1999 | A |
| 5948298 | Ijaz | Sep 1999 | A |
| 6132896 | Sunderland et al. | Oct 2000 | A |
| 6337559 | Sato | Jan 2002 | B1 |
| 6444350 | Toya et al. | Sep 2002 | B1 |
| 6531846 | Smith | Mar 2003 | B1 |
| 6631775 | Chaney | Oct 2003 | B1 |
| 6747437 | Chiu | Jun 2004 | B2 |
| 7262605 | Seo et al. | Aug 2007 | B2 |
| 7270910 | Yahnker et al. | Sep 2007 | B2 |
| 7507500 | Donnelly et al. | Mar 2009 | B2 |
| 7508171 | Carrier et al. | Mar 2009 | B2 |
| 7520355 | Chaney | Apr 2009 | B2 |
| 7667432 | West et al. | Feb 2010 | B2 |
| 7675263 | Kawasumi et al. | Mar 2010 | B2 |
| 7923967 | Hamaguchi et al. | Apr 2011 | B2 |
| 7952330 | Mori | May 2011 | B2 |
| 8004244 | Cromer et al. | Aug 2011 | B2 |
| 8058846 | Kim | Nov 2011 | B2 |
| 8198975 | Sha et al. | Jun 2012 | B2 |
| 8203312 | Yoshikawa | Jun 2012 | B2 |
| 20020188387 | Woestman et al. | Dec 2002 | A1 |
| 20030090855 | Chu et al. | May 2003 | A1 |
| 20030205421 | Allen et al. | Nov 2003 | A1 |
| 20040018417 | Stack | Jan 2004 | A1 |
| 20050069773 | Nakai | Mar 2005 | A1 |
| 20050089750 | Ng et al. | Apr 2005 | A1 |
| 20070054178 | Moon et al. | Mar 2007 | A1 |
| 20070089442 | Tsuchiya | Apr 2007 | A1 |
| 20070188147 | Straubel et al. | Aug 2007 | A1 |
| 20080053716 | Scheucher | Mar 2008 | A1 |
| 20080096072 | Fukasako et al. | Apr 2008 | A1 |
| 20080230288 | Shiomi et al. | Sep 2008 | A1 |
| 20080275600 | Rask et al. | Nov 2008 | A1 |
| 20080290080 | Weiss | Nov 2008 | A1 |
| 20090041992 | Umeda et al. | Feb 2009 | A1 |
| 20090123814 | Cabot et al. | May 2009 | A1 |
| 20100021802 | Yang et al. | Jan 2010 | A1 |
| 20100114512 | Cotton et al. | May 2010 | A1 |
| 20100136392 | Pulliam et al. | Jun 2010 | A1 |
| 20100194348 | Wang et al. | Aug 2010 | A1 |
| 20100275810 | Barbee et al. | Nov 2010 | A1 |
| 20100291418 | Zhou et al. | Nov 2010 | A1 |
| 20100291419 | Zhou | Nov 2010 | A1 |
| 20100291426 | Zhou | Nov 2010 | A1 |
| 20100291427 | Zhou | Nov 2010 | A1 |
| 20100295382 | Tae et al. | Nov 2010 | A1 |
| 20110050175 | Odaohhara et al. | Mar 2011 | A1 |
| 20110248684 | Zhou | Oct 2011 | A1 |
| 20120181988 | Uchibori | Jul 2012 | A1 |
| Number | Date | Country |
|---|---|---|
| 101141012 | Mar 2008 | CN |
| 101141012 | Mar 2008 | CN |
| 201117742 | Sep 2008 | CN |
| 2008288046 | Nov 2008 | JP |
| 2008288046 | Nov 2008 | JP |
| 2008288046 | Nov 2008 | JP |
| 2011171255 | Jan 2011 | JP |
| 2005086196 | Sep 2005 | WO |
| Entry |
|---|
| Article from Tyco Electronics that was published Apr. 14, 2008, entitled “Polymeric Positive Temperature Coefficient”. Retrieved form the Internet<http://tycoelectronics.custhelp.com/. 1 page. |
| International Search report dated Jun. 30, 2011, International Application No. PCT/US2011/031634, 6 pages. |
| SIPO Office action dated May 6, 2013 for application 201110208048.8. |
| Number | Date | Country | |
|---|---|---|---|
| 20120013290 A1 | Jan 2012 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61364313 | Jul 2010 | US |
