Battery management system and method for transferring data within the battery management system

Information

  • Patent Grant
  • 8341449
  • Patent Number
    8,341,449
  • Date Filed
    Thursday, June 24, 2010
    14 years ago
  • Date Issued
    Tuesday, December 25, 2012
    12 years ago
Abstract
A battery management system is provided. The system includes a battery monitoring device having a microprocessor and a hardware component. The microprocessor identifies a non-modifiable node ID from the hardware component. The microprocessor also obtains operational parameters associated with the at least one battery cell. The microprocessor computes a network ID for the battery monitoring device based on the non-modifiable node ID. The system further includes a main controller that communicates with the battery monitoring device via a communication bus utilizing the network ID.
Description
BACKGROUND

Battery systems typically have components that monitor a voltage of a battery cell. However, when the components are in a distributed network, typically DIP switches have been utilized to select addresses of the components. However, an inherent problem with the foregoing technique for selecting an address of a component is that a person may inadvertently select an incorrect address, or select an address that is already assigned to another component. Further, the DIP switch can become degraded or damaged which could result in an incorrect address being utilized by a component.


Accordingly, the inventors herein have recognized a need for an improved battery management system.


SUMMARY

A method for transferring data within a battery management system in accordance with an exemplary embodiment is provided. The battery management system has a battery monitoring device, a communication bus, and a main controller. The method includes identifying a non-modifiable node ID associated with the battery monitoring device from a hardware component of the battery monitoring device, utilizing a microprocessor of the battery monitoring device. The method further includes computing a network ID for the battery monitoring device based on the non-modifiable node ID, utilizing the microprocessor. The method further includes measuring operational parameters associated with at least one battery cell, utilizing the battery monitoring device. The method further includes transmitting data corresponding to the measured operational parameters from the microprocessor through the communication bus to the main controller, utilizing the network ID.


A battery management system in accordance with another exemplary embodiment is provided. The battery management system includes a battery monitoring device having a microprocessor and a hardware component. The microprocessor is configured to identify a non-modifiable node ID from the hardware component. The microprocessor is further configured to obtain operational parameters associated with the at least one battery cell. The microprocessor is further configured to compute a network ID for the battery monitoring device based on the non-modifiable node ID. The battery management system further includes a main controller configured to communicate with the battery monitoring device via a communication bus.


These and other advantages and features will become more apparent from the following description taken in conjunction with the drawings.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 is a block diagram of a battery management system in accordance with exemplary embodiment;



FIG. 2 is a diagram of a table utilized by the battery management system of FIG. 1;



FIG. 3 is a diagram of another table indicating a network ID;



FIG. 4 is a flowchart of a method for transferring data within the data management system of FIG. 1.





DETAILED DESCRIPTION

Referring to the FIG. 1, a block diagram of a battery management system 10 for monitoring battery cells and controlling operation of the battery cells in accordance with an exemplary embodiment is provided. The battery management system 10 includes a main controller 20, a memory device 22, battery monitoring devices 24, 26, a communication bus 28, and battery cells 30, 32, 34, 36. An advantage of the battery management system 10 is that the battery monitoring devices 24, 26 can each self assign a non-modifiable node ID and network ID for communicating through the communication bus 28 with the main controller 20.


The term “non-modifiable node ID” means a node identifier associated with a battery monitoring device that is set at the time of manufacture of the battery monitoring device and cannot be changed thereafter. The term “network ID” is an identifier associated with a device communicating over a communication bus.


The main controller 20 is provided to receive data corresponding to measured operational parameters associated with the battery cells 30, 32, 34, 36 from the battery monitoring devices 24, 26 for monitoring the battery cells and controlling operation of the battery cells. The main controller 20 is operably coupled to a memory device 22 that can store data corresponding to the received operational parameters and other data and software routines. The main controller 20 is further operably coupled to the communication bus 28 for communicating with the battery monitoring devices 24, 26. In one exemplary embodiment, the main controller 20 is implemented utilizing a computer or a microprocessor.


Referring to FIGS. 1 and 2, the main controller 20 is configured to access a table 200 in the memory device 22 that identifies the battery monitoring devices operably coupled to the communication bus 28. In one exemplary embodiment, the table 200 includes three columns: Device No., Node ID, Enabled Map, and Description. Further, the table 200 includes 12 rows corresponding to 12 different battery monitoring devices. For purposes of simplicity, only two battery monitoring devices 24, 26 will be discussed in the illustrated embodiment of FIG. 1. Each Node ID value (i.e., node ID) in the table 200 is a distinct value identifying a specific battery monitoring device. Each Device Number (No.) is a distinct value indicating an ordinal or position of a node ID in the table 200. Each Enabled Map value is a value indicating whether a specific battery monitoring device output is enabled or disabled. In other words, the Enabled Map values allows the main controller 20 to determine which outputs of a battery monitoring device are actually connected and will be reporting an appropriate measured parameter. The Enabled Map allows for increased flexibility for packaging of battery modules containing numerous battery cells since each battery monitoring device can be manufactured to disable particular outputs that become inaccessible due to battery shape and/or configuration. Further, each Description in the table 200 is a binary value indicating whether specific battery cell voltages and temperatures will be measured by a specific battery monitoring device. In one exemplary embodiment, each battery monitoring device is capable of measuring and reporting 10 battery cell voltages and four temperatures per battery module containing the battery cells.


The communication bus 28 routes data bi-directionally between the main controller 20 and the battery monitoring devices 24, 26. Of course, in alternative embodiments, additional battery monitoring devices could be operably coupled to the communication bus 28. In one exemplary embodiment, the communication bus 28 is a CAN bus. Of course, in alternative embodiments, other types of communication buses known to those skilled the art could be utilized.


The battery monitoring device 24 is provided to measure operational parameters associated with the battery cells 30, 32 and to transmit data corresponding to the measured operational parameters to the main controller 20 via the communication bus 28. The battery monitoring device 44 includes a hardware component 60, voltage sensors 62, 64, a temperature sensor 66, a microprocessor 68, and a memory device 70.


The hardware component 60 has non-modifiable node ID information stored therein. In one exemplary embodiment, the hardware component 60 is a set of resistors coupled to the microprocessor 68 and some of which are further coupled to electrical ground. The microprocessor 68 can sample voltages across the resistors to determine a binary value corresponding to the non-modifiable node ID associated with the battery monitoring device 24. In another exemplary embodiment, the hardware component 60 is a non-volatile memory device that has the non-modifiable node ID stored therein. The microprocessor 68 can read the non-volatile memory device to retrieve the node ID associated with the device 24. Of course, in alternative embodiments, other types of devices known to those skilled in the art could be utilized to set the non-modifiable node ID associated with the device 24.


The voltage sensors 62, 64 are provided to measure the output voltages of the battery cells 30, 32, respectively. The voltage sensors 62, 64 transmit signals to the microprocessor 68 indicative of the measured output voltages of the battery cells 30, 32, respectively.


The temperature sensor 66 is provided to measure a temperature level associated with the battery cells 30, 32. The temperature sensor 66 transmits a signal to the microprocessor 68 indicative of a measured temperature level of the battery cells 30, 32, respectively.


The battery cells 30, 32 are electrically coupled to the voltage sensors 62, 64, respectively. In one exemplary embodiment, the battery cells 30, 32 are pouch type lithium-ion battery cells. Of course, in alternative embodiments, the battery cells 30, 32 could be any type of battery cell known to those skilled in the art.


The microprocessor 68 is operably coupled to the hardware component 60, the voltage sensors 62, 64, the temperature sensor 66, and the memory device 70. As discussed above, the microprocessor 68 can sample or read the hardware component 60 to determine a node ID associated with the battery monitoring device 24. Further, the microprocessor 68 is configured to determine a network ID associated with the device 24 based on the node ID to allow bi-directional communication between the device 24 and the main controller 20 via the communication bus 28. In one exemplary embodiment, each node ID is an 8-bit or 1 byte number. Further, in one exemplary embodiment, the bus 28 is a controller-area network (“CAN”) bus and each network ID associated with a battery monitoring device is a CAN ID. A standard CAN ID is 11 bits in size. A unique starting CAN ID can be computed for each battery monitoring device by performing an arithmetic shift of a respective node ID to the left by three significant digits to obtain a unique 11-bit number. Further, referring to FIG. 3, an advantage obtained by utilizing the foregoing method for determining the CAN ID is that there is an exclusive range of 8 unique CAN IDs that can be used for each battery monitoring device between two consecutive battery monitoring devices.


It should be noted that a copy of the table 200 is also stored in the memory device 70 and is accessed by the microprocessor 68. The microprocessor 68 determines a device number (designated as Device No. in the table 200) associated with the battery monitoring device 24 utilizing the determined node ID and the table 200. It should be noted that in one exemplary embodiment, the main controller 20 to sends commands having a device number to the battery monitoring devices on the communication bus 28 and the battery monitoring device associated with the specific device number performs tasks in response to the command. For example, the microprocessor 68 can receive a command from the main controller 20 which requests measured operational parameters (e.g., voltage levels and a temperature level) associated with the battery cells 30, 32. In response to the command, the battery monitoring device 24 measures the operational parameters and transmits data corresponding to the operational parameters to the main controller 20.


The battery monitoring device 26 is provided to measure operational parameters associated with the battery cells 34, 36 and to transmit data corresponding to the measured operational parameters to the main controller 20 via the communication bus 28. The battery monitoring device 46 includes a hardware component 160, voltage sensors 162, 164, a temperature sensor 166, a microprocessor 168, and a memory device 170. The battery monitoring device 26 operates in a substantially similar manner as the battery monitoring device 24, except that the battery monitoring device 26 measures the operational parameters associated with the battery cells 34, 36 and reports the associated operational parameters to the main controller 20. Further, the battery monitoring device 46 utilizes a distinct device number, node ID and network ID associated with the battery monitoring device 46, for bi-directional to communication with the main controller 20.


Referring to FIG. 4, a flowchart of a method for transferring data within the battery management system 10 will be described. Also, for purposes of simplicity, the following method will be discussed with respect to the battery monitoring device 24.


At step 250, the microprocessor 68 of the battery monitoring device 24 determines the non-modifiable node ID associated with the battery monitoring device 24 by sampling or reading the hardware component 60.


At step 252, the microprocessor 68 determines a network ID associated with the battery monitoring device 24 based on the node ID associated with the device 24.


At step 254, the microprocessor 68 determines an ordinal position of the node ID associated with the device 24 in the table 200 that lists the node IDs of the battery monitoring devices coupled to the communication bus 28. In other words, the microprocessor 68 determines the device number associated with the device 24.


At step 256, the microprocessor 68 listens for a command sent to the battery monitoring device 24 from the main controller 20 via the communication bus 28.


At step 258, the microprocessor 68 processes a command sent to the battery monitoring device 24 by the main controller 20. For example, the microprocessor 68 can receive a command from the main controller 20 which requests measured operational parameters (e.g., voltage levels and a temperature level) associated with the battery cells 30, 32. In response to the command, the battery monitoring device 24 measures the operational parameters and transmits data corresponding to the measured operational parameters to the main controller 20.


At step 260, the microprocessor 68 broadcasts the result of the processed command to the main controller 20 using the network ID associated with the battery monitoring device 24. In other words, the microprocessor 68 transmits data corresponding to the measured operational parameters to the main controller 20 via the communication bus 20.


At step 262, the microprocessor 68 makes a determination as to whether a shutdown command was received from the main controller 20. If so, the microprocessor 68 shuts down the battery monitoring device 24. If not, the method returns to the step 256.


While the invention has been described in detail in connection with only a limited number of embodiments, it should be readily understood that the invention is not limited to such disclosed embodiments. Rather, the invention can be modified to incorporate any number of variations, alterations, substitutions or equivalent arrangements not heretofore described, but which are commensurate with the spirit and scope of the invention. Additionally, while various embodiments of the invention have been described, it is to be understood that aspects of the invention may include only some of the described embodiments. Accordingly, the invention is not to be seen as limited by the foregoing description.

Claims
  • 1. A method for transferring data within a battery management system, the battery management system having a battery monitoring device, a communication bus, and a main controller, the method comprising: identifying a non-modifiable node ID uniquely assigned to the battery monitoring device and stored in a hardware component of the battery monitoring device, by using a microprocessor of the battery monitoring device which accesses the hardware component;computing a network ID for the battery monitoring device based on the non-modifiable node ID, by using the microprocessor;measuring operational parameters associated with at least one battery cell, by using the battery monitoring device; andtransmitting data corresponding to the measured operational parameters from the microprocessor through the communication bus to the main controller, by using the network ID.
  • 2. The method of claim 1, further comprising: receiving, by the microprocessor, a command from the main controller which requests data corresponding to the operational parameters associated with the at least one battery cell; andmeasuring the operational parameters of the at least one battery cell in response to the command by using the battery monitoring device.
  • 3. The method of claim 1, wherein the battery management system further comprises a memory which stores a table listing a device number of the battery monitoring device in association with the non-modifiable node ID thereof, the method the further comprising: determining the device number by using the table based on the identified non-modifiable node ID.
  • 4. A battery management system, comprising: a battery monitoring device having a microprocessor and a hardware component, the microprocessor configured to identify a non-modifiable node ID uniquely assigned to the battery monitoring device and stored in the hardware component by accessing the hardware component, configured to obtain operational parameters associated with at least one battery cell, and configured to compute a network ID for the battery monitoring device based on the non-modifiable node ID; anda main controller configured to communicate with the battery monitoring device via a communication bus by using the network ID.
  • 5. The battery management system of claim 4, wherein the microprocessor is further configured to transmit data corresponding to the measured operational parameters through the communication bus to the main controller by using the network ID.
  • 6. The battery management system of claim 4, further comprising: a memory which stores a table listing a device number of the battery monitoring device in association with the non-modifiable node ID thereof, wherein the main controller is configured to determine the device number by using the table based on the identified non-modifiable node ID.
  • 7. A method for transferring data within a battery management system, the battery management system having a battery monitoring device, a communication bus, and a main controller, the method comprising: identifying a non-modifiable node ID associated with the battery monitoring device from a hardware component of the battery monitoring device, utilizing a microprocessor of the battery monitoring device;computing a network ID for the battery monitoring device based on the non-modifiable node ID, utilizing the microprocessor;calculating a device number associated with the battery monitoring device based on the non-modifiable node ID, utilizing the microprocessor of the battery monitoring device;receiving a command from the main controller at the microprocessor, the command having the device number associated with the battery monitoring device, the command requesting data corresponding to the operational parameters associated with at least one battery cell;measuring the operational parameters of the at least one battery cell in response to the command utilizing the battery monitoring device; andtransmitting data corresponding to the measured operational parameters from the microprocessor through the communication bus to the main controller, utilizing the network ID.
  • 8. The method of claim 7, wherein the microprocessor is configured to compute the network ID by performing an arithmetic shift of a plurality of bits of the non-modifiable node ID associated with the battery monitoring device.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent Application No. 61/324,788 filed on Apr. 16, 2010, the entire contents of which are hereby incorporated by reference herein.

US Referenced Citations (90)
Number Name Date Kind
4390841 Martin et al. Jun 1983 A
5578915 Crouch, Jr. et al. Nov 1996 A
5606242 Hull et al. Feb 1997 A
5644212 Takahashi Jul 1997 A
5652502 Van Phuoc et al. Jul 1997 A
5654623 Shiga et al. Aug 1997 A
5658682 Usuda et al. Aug 1997 A
5694335 Hollenberg Dec 1997 A
5701068 Baer et al. Dec 1997 A
5714866 S et al. Feb 1998 A
5739670 Brost et al. Apr 1998 A
5796239 van Phuoc et al. Aug 1998 A
5825155 Ito et al. Oct 1998 A
5936385 Patillon et al. Aug 1999 A
6016047 Notten et al. Jan 2000 A
6064180 Sullivan et al. May 2000 A
6160376 Kumar et al. Dec 2000 A
6232744 Kawai et al. May 2001 B1
6285163 Watanabe et al. Sep 2001 B1
6329823 Blessing et al. Dec 2001 B2
6353815 Vilim et al. Mar 2002 B1
6359419 Verbrugge et al. Mar 2002 B1
6362598 Laig-Horstebrock et al. Mar 2002 B2
6441586 Tate, Jr. et al. Aug 2002 B1
6515454 Schoch Feb 2003 B2
6534954 Plett Mar 2003 B1
6563318 Kawakami et al. May 2003 B2
6583606 Koike et al. Jun 2003 B2
6608482 Sakai et al. Aug 2003 B2
6646421 Kimura et al. Nov 2003 B2
6661201 Ueda et al. Dec 2003 B2
6724172 Koo Apr 2004 B2
6794849 Mori et al. Sep 2004 B2
6829562 Sarfert Dec 2004 B2
6832171 Barsoukov et al. Dec 2004 B2
6876175 Schoch Apr 2005 B2
6892148 Barsoukov et al. May 2005 B2
6919952 Kruit Jul 2005 B2
6927554 Tate, Jr. et al. Aug 2005 B2
6943528 Schoch Sep 2005 B2
6967466 Koch Nov 2005 B2
6984961 Kadouchi et al. Jan 2006 B2
7012434 Koch Mar 2006 B2
7039534 Ryno et al. May 2006 B1
7061246 Dougherty et al. Jun 2006 B2
7072871 Tinnemeyer Jul 2006 B1
7098665 Laig-Hoerstebrock Aug 2006 B2
7109685 Tate, Jr. et al. Sep 2006 B2
7126312 Moore Oct 2006 B2
7136762 Ono Nov 2006 B2
7138775 Sugimoto et al. Nov 2006 B2
7197487 Hansen et al. Mar 2007 B2
7199557 Anbuky et al. Apr 2007 B2
7228447 Day Jun 2007 B1
7233128 Brost et al. Jun 2007 B2
7250741 Koo et al. Jul 2007 B2
7253587 Meissner Aug 2007 B2
7315789 Plett Jan 2008 B2
7317300 Sada et al. Jan 2008 B2
7321220 Plett Jan 2008 B2
7327147 Koch Feb 2008 B2
7394394 Lockhart et al. Jul 2008 B2
7400115 Plett Jul 2008 B2
7424663 Mehalel Sep 2008 B2
7446504 Plett Nov 2008 B2
7518339 Schoch Apr 2009 B2
7521895 Plett Apr 2009 B2
7525285 Plett Apr 2009 B2
7558701 Andarawis et al. Jul 2009 B2
7576518 Sanders et al. Aug 2009 B2
7583059 Cho Sep 2009 B2
7589532 Plett Sep 2009 B2
7593821 Plett Sep 2009 B2
7710073 Yamauchi et al. May 2010 B2
20030015993 Misra et al. Jan 2003 A1
20030184307 Kozlowski et al. Oct 2003 A1
20050100786 Ryu et al. May 2005 A1
20050127874 Lim et al. Jun 2005 A1
20060017582 Lockhart et al. Jan 2006 A1
20060100833 Plett May 2006 A1
20070118301 Andarawis et al. May 2007 A1
20070120533 Plett May 2007 A1
20080071473 Choi Mar 2008 A1
20080094035 Plett Apr 2008 A1
20080143543 Vandensande et al. Jun 2008 A1
20080180106 Gorbold Jul 2008 A1
20080249726 Plett Oct 2008 A1
20100097034 Shu et al. Apr 2010 A1
20100241377 Kagawa Sep 2010 A1
20110154084 Vandwalle et al. Jun 2011 A1
Foreign Referenced Citations (18)
Number Date Country
9243716 Sep 1997 JP
9312901 Dec 1997 JP
11003505 Jan 1999 JP
11023676 Jan 1999 JP
11032442 Feb 1999 JP
11038105 Feb 1999 JP
2002228730 Aug 2002 JP
2002319438 Oct 2002 JP
2002325373 Nov 2002 JP
2003516618 May 2003 JP
2003249271 Sep 2003 JP
2003257501 Sep 2003 JP
2004031014 Jan 2004 JP
2004521365 Jul 2004 JP
2006516326 Jun 2009 JP
19970024432 May 1997 KR
20020026428 Apr 2002 KR
WO0067359 Nov 2000 WO
Related Publications (1)
Number Date Country
20110258471 A1 Oct 2011 US
Provisional Applications (1)
Number Date Country
61324788 Apr 2010 US