Patent Application
20230387696
A battery system comprises a plurality of battery packs. Each battery pack includes a battery management system in which one of the battery packs is flexibly configured as a master (e.g., primary) battery pack while the other battery packs are configured as slave (e.g., secondary) battery packs.
The battery management systems and methods described herein may be implemented in industrial and commercial vehicle applications, such as off-road utility vehicles, hybrid electric vehicles, battery-electric powered vehicles, burden carrier/tow tractors, forklift/pallet jacks, lawn and garden/outdoor power equipment, large mining equipment, automated guided vehicles, aerial work platforms, and other such applications. In addition, the systems and methods described herein may be implemented in other applications including, but not limited to cordless power tools (e.g., drills, saws, grinders, nail drivers, welders, and the like), aerospace/defense applications, appliances, and other such applications. Furthermore, the systems and methods described herein may be implemented in other applications including, but not limited to grid energy storage, solar-generated power storage systems, sustainably generated power storage systems, smart grid systems, telecom and data communication backup systems, uniform power supply (UPS) systems, server applications, and other such applications.
For example, in some industrial and commercial vehicle applications, a battery management system such as disclosed herein may desired to output a wide range of current—e.g., a high current when initially turning on an engine of the vehicle, however, less current during normal operation of the vehicle. The battery management system and methods may also, in some embodiments, include a limp home mode feature, as disclosed herein, to accommodate a failed battery in a large-format battery pack, such as in an industrial or commercial vehicle application. The battery management systems, including various battery pack configurations and one or more buses (e.g., a CAN bus), may integrated into the industrial and commercial vehicle application.
In another example, in some telecom and/or data communication backup systems and/or computer server applications, a battery management system such as disclosed herein may provide an alternative to lead acid battery installations that previously dominated these applications because of their low cost, straightforward scalability, accessible recycling infrastructure, and accessible manufacturers. In some embodiments, the battery management systems and methods disclosed herein provide high energy density, high rate of discharge capabilities, and low self-discharge characteristics that make for desirable integration into telecom and/or data communication backup systems, uniform power supply (UPS) systems, and/or computer server applications. For example, the aforementioned applications desire longer operational time frames that are made possible by the battery management system such as disclosed herein, which extend the usable life of batteries in the battery pack by implementing smart algorithms for charge, discharge, and balancing— e.g., smart converter balancing, start direct balancing, start staggered balancing, and others. In addition, the battery management systems and methods disclosed herein may be used in cooperation with, in some examples, technologies such as fuel cells, ultracapacitors, flywheels, and other electrochemical batteries for use in telecom/data communications backup applications.
In yet another example, in some grid energy storage systems, solar-generated power storage systems, sustainably generated power storage systems, smart grid systems, and/or uniform power supply (UPS) systems, a battery management system such as disclosed herein may optimize electricity grids and enable sustainable energy sources, such as wind and solar power, to be more economical. In one example, the system may be used to store solar energy received from photovoltaic panels and a bi-directional three-phase inverter system may be managed, in some embodiments, using the battery management system disclosed herein. The renewable energy storage system may include a plurality of batteries in a battery pack integrated into a rack mount chassis and enclosure. Solar integrators may use the disclosed battery management systems and methods with large-format battery chemistries to fill the needs of growing renewable energy storage requirements. While lead-acid, ultracapacitors, sodium sulfur, vanadium redox, flywheels, compressed air, fuel cells and pumped hydro have been used in solar energy storage applications, with the disclosed battery management systems and methods, solar integrators may conveniently use Lithium ion for large-format applications. In addition, solar integrators may desire ancillary services for the power markets that uses micro-pulses of energy to maintain the proper frequency of the current on the grid—e.g., frequency regulation, and advanced smart grid functionality such as micro grid operation, demand response, time shifting, and power dispatch. Lithium chemistry over previous battery technologies include weight reduction, volume/footprint reduction, longer cycle-life, ability to use a greater percent of capacity of lithium battery without shortening rated cycle life, faster charge times, and lower effective capacity loss at high rates of discharge. In some examples, an inverter and gateway interoperability may be coupled to the disclosed battery management systems to manage, distribute, and store energy within a smart grid. In some examples, the smart grid system may be housed in a mobile shipping container that is expandable.
In addition to grid energy storage systems, the battery management systems and methods disclosed herein may be integrated with off-grid power products suitable in consumer, recreational, automotive, maritime and/or industrial applications. In the automotive sector, auxiliary power units (APU) may be used for transportation, construction, and/or maintaining vital infrastructure. Battery APUs provides commercial vehicles with a rugged and dependable off-grid power source. Other off-grid power applications include maritime power, remote location power, traffic regulation, security surveillance and emergency power generators. Moreover, Battery APUs may be used for short and long-haul trucks, construction equipment, off-road transport (e.g., logging trucks), and buses. For example, commercial trucks may rely on Battery APUs for overnight comfort (e.g., air conditioning/heat/accessory) loads. For several off-grid applications, reliability is a major concern as failure and/or downtime is exceedingly costly.
Battery technology has evolved from the nascent era of automation when vehicle batteries were typically large and heavy affairs using lead-acid technology. Battery technology has evolved to provide more electrical energy with less space. For example, Lithium-ion (Li-ion) batteries are quickly replacing regular zinc carbon and lead batteries because they are smaller and lighter than traditional batteries and can hold charge for up to three times longer than big, heavy traditional batteries. Consequently, Li-ion batteries are finding applications for powering tools, appliances, and vehicles including forklifts, cars, trucks, and so forth. Moreover, battery technology is not stagnant. For example, new solid-state batteries use a glass electrolyte and lithium or sodium metal electrodes, providing approximately three times as much energy density as Li-ion batteries. In general, however, new technology batteries may be damaged or degraded if the sensitive chemistry of the battery is disrupted. For example, Li-ion batteries are known to malfunction/degrade if overcharged or charged/overcharged/discharged in inappropriate ways.
A battery management system (BMS) is sometimes included with new technology batteries (for example, nickel metal hydride or Li-ion) to provide battery protection, provide improved efficiency, and provide a better user experience than previous battery technologies. The battery management system may sometimes be implemented to further one or more goals. For example, the BMS may be used to protect a user of the application being powered by the battery. As a further example, the BMS may be used to protect the battery pack itself from damage and abuse because the battery may often an expensive investment. Furthermore, since the battery may be an expensive investment, the BMS may be used to maximize the performance that can be squeezed out of the battery system. Even further, the BMS may be used to maximize the life of the constituent battery cells.
A battery system may comprise a plurality of battery packs that may have the same or similar electrical and electronic components and/or chemistries. Each battery pack may support battery cells (often Li-ion). Battery packs need not require a specific configuration before the battery pack is installed in the battery system. Rather, the battery pack may assume a role of either a master (e.g., a primary) battery pack or a slave (e.g., a secondary) battery pack after the battery pack is inserted into the system and commences activity on the communication channel without user intervention.
With another aspect, the battery system need not utilize an external battery management system. Rather, each battery pack may include an internal battery management system that can manage a pack's battery cells and may coordinate via messaging with the other battery packs in the battery system via a communication channel.
With another aspect, a master battery pack may gather battery status information from one or more slave battery packs by messaging over a communication channel. Based on this status information, the master battery pack can appropriately initiate the enabling/disabling of the charging or discharging of battery cells located at the slave battery packs.
With another aspect, a configuration list may be sent by a master battery pack to slave battery packs over a communication channel (for example, serial communication channel such as a controller area network (CAN) bus), where the configuration list may include entries for each of the master and slave battery packs. The entry at the top position can serve as the master battery pack while the other battery packs can serve as slave battery packs. When a battery pack is added or removed, the configuration list can be revised to reflect the change.
With another aspect, battery packs in a battery system may be charge-balanced to mitigate and/or prevent in-rush electrical current that may occur for one or more of a plurality of battery packs in the battery system when there is significant variation of state of charge (SoC) among the battery packs. For example, a large SoC variation may occur when a new battery pack is installed in a battery system, such as when a SoC of the new battery pack is much different (e.g., discharged, fully charged) when compared to the existing battery packs in the battery system. In-rush electrical current can be particularly undesirable with Li-ion batteries since its life may be substantially reduced.
With another aspect, different balancing technique of battery packs are supported in a battery system. Based on the SoC characteristics of the battery packs, one of a plurality of balancing techniques may be selected. Balancing techniques may include, for example, a “smart converter balancing,” a “start direct balancing,” and/or a “start staggered balancing.”
With another aspect, a battery system may support a “limp home mode” when a battery pack in a battery system experiences a catastrophic failure, for example, when its battery cells are characterized by a very low voltage output. An internal battery management system may diagnose the failure and may mitigate the failure by configuring an unused battery pack (if available) in the battery system or by initiating a partial shutdown of the battery system, enabling operation of the equipment to “limp home” under at least partial power.
With another aspect, a battery system supports “smart discharge” in order to power equipment (end device). Battery packs with varying SoC's may be connected to an end device to provide electrical power to the device. However, battery packs that have a large SoC variation cannot be immediately connected together to power the end device and may necessitate charge balancing to be performed. Battery packs are then selectively enabled from a plurality of battery packs in the battery system so that the battery packs can properly discharge.
With another aspect, a battery system supports “smart charge” in order to restore charge to its battery cells. A battery system having battery packs with varying SoC's may be connected to a charger in order to restore the SoC's of each battery pack and to reduce the SoC variability among the battery packs. If the battery packs have a large SoC variation, the battery packs cannot be immediately connected to the charger at the same time. Measures are thus supported to circumvent this situation by enabling charging of selected battery packs at the appropriate time based on dynamic SoC characteristics.
The foregoing summary, as well as the following detailed description of exemplary embodiments, is better understood when read in conjunction with the accompanying drawings, which are included by way of example, and not by way of limitation with regard to the claimed invention.
According to an aspect of the embodiments, a battery system with a large-format battery (e.g., a Li-ion battery) powers attached equipment (an end device) by discharging battery cells distributed among a plurality of battery packs. The discharging of the battery cells is controlled in an efficient manner while preserving the expected life of the Li-ion battery cells.
According to another aspect of the embodiments, a battery system may support different advanced technology batteries of different chemistries and/or structures including, but not limited to, Li-ion batteries and solid state batteries.
Each battery pack internally supports a battery management system (BMS), thus circumventing the need of an external battery management in contrast to traditional approaches. Moreover, each of the battery packs may have identical electrical and electronics components, thus supporting an architecture that easily scales to higher power/energy output as needed by an end device. Battery packs may be individually added or removed, where one of the battery packs serves as a master battery pack and the remaining battery packs serve as slave battery packs. Moreover, configuration of the battery packs may be automatically performed without user interaction. When the master battery pack is removed, one of the slave battery packs is automatically reconfigured to become the master battery pack. Charging and discharging of the battery cells is coordinated by the master (e.g., primary) battery pack with the slave (e.g., secondary) battery packs over a communication channel such as a controller area controller (CAN) bus.
In addition, the battery system may be efficiently charged in order to restore charge to the battery cells while preserving the life expectancy of the battery cells.
Rechargeable medium-to-large format battery packs with battery management systems are providing power for small, portable devices and are also extending to larger mobile and stationary uses. Moreover, transportation applications spanning smaller uses such as scooters to larger ones such as full-size autos are contemplated with rechargeable batteries. Industrial applications are also contemplated as battery-based designs are replacing small internal combustion engines for lawn mowers and yard equipment in both commercial and consumer products. Enabling electrification has several advantages, including but not limited to, elimination of polluting emissions, reduced noise, and lower maintenance needs. Furthermore, self-contained backup power systems for residential and commercial sites are benefiting from battery-based designs which eliminate the issues associated with on-site hydrocarbon-based fuel storage.
End device 101 may assume different types of devices including, but not limited to, power tools, lawn mowers, garden tools, appliances, and vehicles including forklifts, cars, trucks, and so forth.
Battery management systems 112, 113, and 114 communicate with all of the battery packs as well as end device 101 and/or charger 1601 (as shown in
The CAN and Ethernet protocols support the lower two layers of the OSI model while the BLE protocol spans the lower layers as well as the higher layers including the application layer. Consequently, embodiments utilizing protocols such as CAN and Ethernet must support the equivalent higher layers by software applications built on top of the two lower layers.
Embodiments may support different messaging protocols. For example, a protocol may support node to node communication by supporting both a source address and a destination address. The destination address may specify a particular node address or may be a global address so that a message may be broadcast to more than one node. In some cases, a protocol (such as the CAN protocol, the Modbus protocol, etc.) may support only a single source address (e.g., a master address) so that all nodes may process a message broadcast over a communication channel.
Battery packs 102, 103, and 104 may each connect to communication channel 152 in a parallel fashion. However, embodiments may support different arrangements such as pack-to-pack communication on separate busses or a daisy chain connection through each battery pack.
Battery packs 102, 103, and 104 may have similar or identical electrical and electronic components. After being inserted into a battery system, one of the battery packs 102, 103, or 104 may be configured as a master battery pack or a slave battery pack. Moreover, if a battery pack initially serves as a slave battery pack, it may subsequently serve as a new master battery pack if the current master battery pack is removed.
As will be discussed, battery pack 200 may be configured as either a master battery pack or a slave battery pack without any change to the electrical or electronic components.
The power circuitry (including battery cells 203) of battery pack 200 interacts with power bus 151 through power bus interface circuit 206 when battery pack 200 is discharging, charging, and/or being balanced with respect to the other battery packs as will be discussed.
Battery pack 200 also interacts with communication channel 152 via communication channel interface circuit 205. For example, battery pack 200 may support messaging with other configured battery packs, with the end device being powered by the battery packs, or with a charger charging battery cells 203. Exemplary message flows are shown in
Battery pack 200 supports core battery monitoring and/or management functionality via core battery functions circuit 204. For example, core battery functions may include battery cell status, battery cell balancing, short circuit protection, high temperature cut-off, over-current cut-off, and over-charge protection.
Referring to
Status information may include the state of charge (SoC) information, state of health (SoH) information, temperature information, charging time information, discharge time information, and/or capacity information of the battery cells and/or of the battery pack.
As one with skill in the art would appreciate, the SoC is understood to be the level of charge of an electric battery relative to its capacity. The units of SoC are typically percentage points (0%=empty; 100%=full).
The SoH typically does not correspond to a particular physical quality since generally there is no consensus in the industry on how SoH should be determined. However, the SoH is indicative of internal resistance, battery storage capacity, battery output voltage, number of charge-discharge cycles, temperature of the battery cells during previous uses, total energy charged or discharged, and/or age of the battery cells to derive a value of the SoH. Knowing the SoH of the battery cells of battery pack 200 and the SoH threshold of a given end device (application) may provide a determination whether the present battery conditions are suitable for an application and an estimate about the battery pack's useful lifetime for that application.
When performing processes associated with battery management, battery pack 200 may receive or send values of at least the SoC and/or SoH from/to other battery packs as will discussed in further detail.
Power bus interface circuit 206 may comprise a switch circuit such as a semiconductor array 210 (for example, a MOSFET array or other power semiconductor switch device, such as an insulated gate bipolar transistor (IGBT) array, a thyristor array, etc.) that allows electrical current flow from battery pack 200 when battery pack 200 is discharging and semiconductor array 211 that allows electrical current flow to battery pack 200 when battery pack 200 is charging. Arrays 210, 211 are appropriately enabled by processor 201 in response to messaging from the master battery pack controller. (In a situation when battery pack is the master battery pack, messaging is internal to battery pack 200 rather via communication channel 152.) The power MOSFET arrays (e.g., N-Channel MOSFETs) may be used as switches to control power flow to and from the battery cells. The gates of the MOSFET arrays may be controlled by signals generated by a microcontroller and/or a battery management IC.
Power bus interface circuit 206 may be configured to prevent battery pack 200 from being charged or discharged through power bus 206 based on the status of battery cells 203 (for example, SoC, SoH, and/or voltage). Typically, arrays 210 and 211 are disabled when a battery pack is inserted into a battery system so that the battery pack does not charge or discharge until instructed and/or controlled by the master battery pack.
Battery pack 200 interacts with power bus 151 via electrical switch 208 (which may comprise one or more semiconductor devices). As shown in
Converter 207 may assume different forms capable of controlling power transfer between the power bus and the cells of the battery pack such as by providing a stepped-down output voltage with respect to the input voltage (e.g., a buck converter, a auk converter, a buck-boost converter, a single-ended primary-inductor converter (SEPIC) converter, etc.) to protect battery cells 203 from an electrical current in-rush and enable battery cells 203 to slowly charge (for example, corresponding to converter balancing flowchart 713 as shown in
Processor 201 may support battery management processes (for example, processes 500, 700, 713, 714, 715, 1700, 2000, and 2200 as shown in
Computer storage media may include volatile and nonvolatile and removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media include, but is not limited to, random access memory (RAM), read only memory (ROM), electronically erasable programmable read only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and that can be accessed by the computing device.
Communication media may include computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. Modulated data signal can be a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media may include wired media, such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.
While processor 201 and communication channel interface circuit 205 may be powered by battery cells 203, embodiments may have a separate power source for processor 201 and interface circuit 205. Consequently, battery pack 200 may continue to interact with the other battery packs over the communication channel regardless of the status of battery cells 203.
Controller 213 executes computer-executable instructions to perform processes discussed herein. For example, controller 213 obtains status information (for example, the SoC value) from battery cells 210 via battery monitor 211, provides battery pack status information via status display 215, and interacts with a communication channel (for example, a CAN bus) via communication bus interface 216.
In addition, a heater control circuit 212 may be used to ensure that the temperature of battery cells 210 does not drop below a minimum value so that battery cells 210 can properly operate as expected.
At block 301, end device 101 is activated. For example, a user may close a battery compartment of end device 101, turn a key, and/or flip a switch to generate an interlock signal.
At block 302, the battery management system of the master battery pack determines whether to balance the battery packs when the battery compartment has more than two battery packs. If so, the difference of charge of the battery packs may be reduced by one or more battery packs discharging to charge one or more of the other battery packs at block 303 as will be discussed in further detail.
After balancing (if needed), the end device is powered by discharging one or more of the battery packs at block 304. For example, based on the power requirements of the end device and the SoC values of the battery packs, the battery management system of the master battery pack may enable the appropriate battery packs.
If a catastrophic failure is detected at block 305 for one of the enabled battery packs while powering the end device, limp home mode operation at block 306 may be initiated in order to continue powering the end device as will be discussed in further detail.
When the user completes using the end device at block 307, block 308 determines whether charging is needed. If so, a charger may be connected to the battery system to restore the battery cells, where charging may be initiated at block 309.
While not explicitly shown, balancing of the battery packs may be performed before charging the battery packs at block 308 when the SoC values of the battery packs are sufficiently different.
With the embodiments, all of the plurality of battery packs may have the same electrical and electronic components. No configuration is typically needed to a battery pack when the battery pack is installed in the battery system. Rather, the battery pack assumes the role of either a master battery pack or a slave battery pack based on processes discussed herein after the battery pack is inserted into the system and the battery pack commences activity on the communication channel. As will be discussed in further detail, a configuration list may be conveyed over the communication channel, where the configuration includes entries for each of the master and slave battery packs.
The processes discussed herein are shown from the perspective of the master battery pack and are typically executed by the master battery pack in the battery system. The other installed battery packs in the battery system serve as slave battery packs. However, the slave battery packs interact with the master battery pack over the communication channel. For example, a slave battery pack provides its battery cell status information and activates/deactivates power switches to interact with the power bus (for example, allowing electrical current (charge) to flow into or from the battery pack) responsive to messaging from the master battery pack. Consequently, while not explicitly shown, there are corresponding processes executed by each of the slave battery packs.
As will be discussed in greater detail, the master battery pack gather status information about the other battery packs (the slave battery packs) and consequently instructs the slave battery packs, as well as itself, to discharge or charge in response to the operation situation.
With the embodiment shown in
Selecting the oldest (top) member of configuration list 401c may be advantageous to traditional approaches. For example, the number of changes of the master battery packs may be reduced with respect to determining the master battery pack based on the ID value. With the latter approach, a second change would occur from configuration list 401d, where pack 5 would become the master battery pack.
In the installation scenario shown in
Subsequently, pack 5 is inserted into the battery system resulting in a new entry being added to configuration list 401d, where ID 243 is the same ID for previously removed pack 1. With embodiment shown in
With some embodiments, when a battery pack is removed from a battery system, battery pack information may be lost. When the battery pack is reinserted, the reinserted battery pack may obtain battery information from the configured battery packs. However, some embodiments may support memory persistence (e.g., flash memory) so that battery pack information is retained at the battery pack even when the battery pack is removed and reinserted.
At block 504, a battery pack is removed from the battery system. If the battery pack is the first member of the configuration list, as determined at block 505, the entry is removed at block 506 and the battery pack corresponding to the next entry is designated as the master battery pack at block 507. Otherwise, the entry for the removed battery pack is deleted at block 508.
The message flow in
When pack 601 (pack 1) becomes the master battery pack at event 631, pack 601 sends periodic update messages 661a,661b,661c to packs 602, 603, and 604, respectively. If the message protocol supports a single broadcast message (for example, with a global destination address) that is received and processed by all battery packs connected to the communication channel, then only one message is sent by pack 601. Otherwise, pack 601 sends separate messages to packs 602, 603, and 604 (which are configured as slave battery packs).
With some embodiments, messages 661a, 661b, 661c may be sent repetitively but not periodically.
Periodic update message 661a, 661b, 661c may contain configuration information (for example configuration list 401a, 401b, 401c, 401d as shown in
When the disruption is detected by the oldest slave battery pack (pack 602) at event 633, pack 602 assumes the role of the master battery pack. Consequently, pack 602 removes the top entry of the configuration list (corresponding to pack 601) and periodically sends the revised configuration list via update message 662a,662b.
When pack 605 (pack 5) is added at event 634, pack 605 sends join request 663 in accordance with the SAE J1939 address claim procedure. Consequently, pack 605 is added by pack 602 (currently the master battery pack) at event 635, and pack 602 periodically sends update messages 664a, 664b, 664c and 665a, 665b, 665c.
The CAN communications protocol (ISO-11898: 2003) describes how information is passed between devices on a network and conforms to the Open Systems Interconnection (OSI) model that is defined in terms of layers. Actual communication between devices connected by the physical medium is defined by the physical layer of the model. The ISO 11898 architecture defines the lowest two layers of the seven-layer OSI/ISO model referred as the data-link layer and physical layer.
The CAN communication protocol supports both a standard version (11-bit identifier field) and an extended version (29-bit identifier field). However, embodiments typically use the standard version because the supported identifier space is typically more than enough.
The CAN bus is often referred to as a broadcast type of bus, where each message contains a source address (for example, a device ID) but not a destination address. Consequently, all battery packs (corresponding to nodes) can “hear” all transmissions. A battery pack may selectively ignore a message or may process the message by providing local filtering so that each battery pack may respond to pertinent messages.
Embodiments may use the data frame message specified in the CAN protocol. This message type carries a 0-8 byte payload, where the data field is interpreted at a higher protocol layer (typically by a software application executing at the battery packs). For example, the data field may convey SoC and/or SoH information when a slave battery pack sends status information back to the master battery pack.
In order to assign an identification value (address) to a battery pack, end device, or charger, embodiments may utilize an industry standard, such as the SAE J1939 address claim procedure. The SAE J1939 protocol is a higher protocol layer built on top the CAN data-link and physical layers.
Referring to
When pack 601 is removed (for example, corresponding to event 637), periodic transmission of the periodic data frame messages is disrupted.
When the disruption is detected by the oldest slave battery pack (pack 602) at event 638, pack 602 assumes the role of the master battery pack. Consequently, pack 602 removes the top entry of the configuration list (corresponding to pack 601) and periodically sends the revised configuration list via data frame message 672.
When pack 605 (pack 5) is added at event 639, pack 605 initiates the address claimed procedure 673 claiming its identification (ID) value. When successfully completed, an entry with the identification of pack 605 is added to the bottom of the configuration list by master battery pack 602 at event 640.
Subsequently, pack 602 (now the master battery pack) periodically sends broadcast data frame message 674.
At event 642, battery pack 604 is removed from the battery system. When battery pack 601 periodically sends message 683, only messages 684a-b are returned. Consequently, a message timeout occurs at event 643, and master battery pack 601 detects that battery pack 604 has been removed and removes the entry for battery pack 604 from the configuration list. The modified configuration list is included in the next periodic broadcast.
Battery pack 601 is distributed as the master battery pack at event 644. Rather than the master battery pack maintaining and sending the configuration list to the other battery packs, each of the active battery packs 601-604 maintains its own configuration list and broadcasts it via messages 691a-d to the other battery packs via the CAN bus, where list_1, list_2, list_3, and list_4 correspond to the configuration messages maintained at battery packs 601-604, respectively. As necessary, battery packs 601-604 may modify its own configuration list to be consistent with the configuration lists broadcast by the other battery packs. For example, a battery pack may have been recently inserted into a battery system and may need to revise its configuration list to be consistent with the current configuration.
When pack 601 is removed (for example, corresponding to event 645), periodic transmission of the periodic data frame messages from battery pack 601 terminates.
When the termination is detected by battery packs 602-604 at event 646, pack 602 assumes the role of the master battery pack. Consequently, packs 602-604 remove the top entry of the configuration list (corresponding to pack 601) that is locally maintained at the battery packs 602-604 and periodically send the revised configuration list via data frame messages 692a-c.
When pack 605 (pack 5) is added at event 647, pack 605 initiates the address claimed procedure 693 claiming its identification (ID) value. When successfully completed, battery packs 602-604 adds pack 5 to the bottom of the local copy of the configuration list. 605 at event 648, and subsequently the revised configuration list is broadcast via data frame messages 694a-d. With an aspect of the embodiments related to balancing, as will be discussed, the in-rush of electrical current among multiple Li-ion battery packs in a large-format battery pack system is an undesirable phenomenon arising with Li-ion battery cells since a large in-rush electrical current may reduce the life of Li-ion battery cells. This phenomenon may occur due to a large variation of SoC values among the battery packs in the battery system. For example, when a brand new Li-ion battery pack is added to a battery pack system, its capacity (e.g., energy level) at the beginning of its new life may be notably different than capacities of the battery cells of older battery packs already present in the battery pack system. This energy level differential between the cells of the new battery pack and the cells of the older battery packs can potentially damage the other Li-ion battery cells in the battery pack system. The aspect involves a balancing technique that leverages the internal (not external) battery management system and the master-slave topology.
As previously discussed, some embodiments order a configuration list based on the time that battery packs are connected to the communication channel (for example, CAN bus). With this approach, the oldest battery pack is designated as the master battery pack. However, other embodiments may use different approaches. For example, the members of the configuration list may be ordered from top to bottom by decreasing values of the open circuit voltages of the battery packs. The open circuit voltage of a battery pack may be measured when the battery pack's discharging array is disabled (in other words, the battery pack is not discharging onto the power bus of the battery system).
Each battery pack can share its measured open circuit voltage with the other battery packs that are connected to the communication channel. Based on the measured open circuit voltages, a configuration list is maintained, where entries for each battery pack are listed by decreasing order. The battery pack corresponding to the top entry has the largest open circuit voltage and serves as the master battery pack for battery system. With an exemplary embodiment, a battery system comprises first, second, and third battery packs having open circuit voltages Vopen1, Vopen2, and Vopen3, respectively, where Vopen2>Vopen3>Vopen1. The top entry of the configuration list is associated with the second battery pack (the master battery pack) followed by an entry for the third battery pack followed by an entry for the first battery pack. Consequently, if the second battery were to fail, the third battery pack would assume the role of the master battery pack.
With some embodiments, the battery packs in a battery system are assigned an ID and at the same time the open circuit voltage may be measured and stored in the configuration list. In the infrequent situation where the open circuit voltages of two battery packs are equal, one battery pack may be chosen randomly or may be chosen by the highest number ID.
The configuration list may be updated as battery packs are installed into the battery system. For example, a battery pack that is installed after discharging begins would initially enter in a standby mode (where the discharging array is disabled) so that an open circuit voltage can be measured by the battery pack. The newly installed battery pack could than share the measured open circuit voltage with the other battery packs via the communication channel. With some embodiments, the configuration list can then be updated with an entry for the newly installed battery pack based on the measured open circuit voltage. However, with some embodiments, the current configuration list may remain unchanged until the battery packs being discharged are disconnected from the battery system.
With some embodiments, the configuration list may be centrally maintained by the master battery pack. However, with some embodiments, each battery pack in the battery system may maintain its own copy of the configuration list based on information shared via the communication channel.
With an aspect of the embodiments related to balancing, as will be discussed, the in-rush of electrical current among multiple Li-ion battery packs in a large-format battery pack system is an undesirable phenomenon arising with Li-ion battery cells since a large in-rush electrical current may reduce the life of Li-ion battery cells. This phenomenon may occur due to a large variation of SoC values among the battery packs in the battery system. For example, when a brand new Li-ion battery pack is added to a battery pack system, its capacity (e.g., energy level) at the beginning of its new life may be notably different than capacities of the battery cells of older battery packs already present in the battery pack system. This energy level differential between the cells of the new battery pack and the cells of the older battery packs can potentially damage the other Li-ion battery cells in the battery pack system. The aspect involves a balancing technique that leverages the internal (not external) battery management system and the master-slave topology.
With an aspect of the embodiment, different balance techniques for Li-ion battery cells may be supported in a large-format battery pack system. For example, the aspect includes three balancing techniques: “smart converter balancing,” “start direct balancing,” and “start staggered balancing” that may be used in a medium-large battery pack implementation to ensure the safe use and longevity of the Li-ion battery cells. The aspect may utilize a converter (with a cell pre-charge circuit) for charge balancing each battery pack to prevent and/or limit in-rush electrical current, over-current faults, and/or short-circuit faults.
At block 701, the master battery pack transitions from a sleep state. For example, when an end device is not being used, the master battery pack may periodically wake up to determine whether there is a change in the operational state.
At block 702, the master battery pack determines the number of battery packs that are installed in the battery system. For example, the master pack may verify that all battery packs on the confirmation list are active on the communications channel.
At block 704, the master battery pack determines whether a minimum number of battery packs (including itself) are installed based on power requirements of a device (for example, obtained from the end device via the communication channel).
If there are not a minimum number of battery packs available to properly power the end device, then the configured battery packs are prevented from discharging at block 705 by the master battery pack instructing the slave battery packs (as well as itself) to open corresponding discharge arrays. A fault indicator is activated at block 706 that is indicative that not enough battery packs are installed to power the end device. If an additional battery pack is installed at block 707, the fault indicator is cleared at block 708. If the end device is activated or otherwise enabled at block 709 (for example, the key is in the “on” position), process 700 returns to block 704. Otherwise, process 700 returns to block 701.
Returning back to block 704, when the master battery pack determines that there are a sufficient number of battery packs, the master battery pack gathers battery pack information (for example, SoC, SoH, and voltage information) from each of the slave battery packs as well as for itself at block 710. For example, as will be discussed in further detail, the master battery pack may send a “Request for Pack Info” message to each of the configured slave battery packs and receive a “Pack Info” message from each slave battery pack in response with the requested information.
From the gathered SoC data, the master battery pack determines whether balancing is required at block 711. For example, some of the battery packs may have a high SoC while some may have a low SoC. By balancing the battery packs, a sufficient number of battery packs may be available to properly discharge in order to power the end device.
If balancing is not required, the battery system may discharge to power the end device at block 717.
If balancing is required, the type of balancing is determined at block 712. As will discussed in greater detail, embodiments may support three different types of balancing: converter balancing (block 713), direct balancing (block 714), and staggered balancing (block 715).
Tables 1 and 2 present examples of balancing in accordance with embodiments.
The above to examples illustrate that the type of balancing may change while the battery packs are being balanced. For example, with Table 1 the balancing type changes from converter balancing to staggered balancing while with Table 2 the balancing type changes from converter balancing to direct balancing.
After balancing, if the number of battery packs are available for discharging, as determined at block 716, the end device may be powered at block 717. Otherwise, the battery packs may be rebalanced based on the revised SoC values obtained from the previous balancing.
When rebalancing occurs, as determined at block 716, the rebalancing may utilize a different type of balancing than previously used. For example, converter balancing may be first applied while subsequent rebalancing may utilize staggered balancing.
At block 721, if the variability of the SoC values among the battery packs is sufficiently small, the battery system is able to power the end device at block 722. (For example, the SoC differences between all pairs of battery packs is less than a predetermined threshold.) Otherwise, process 712 proceeds with balancing the battery packs.
Block 723 identifies the battery pack with the highest SoC value so that the identified battery pack can discharge, thus providing charge to the other battery packs during balancing.
At block 724 process 712 determines whether direct balancing cannot be applied (for example, when the SoC difference between the highest SoC pack and an identified battery pack is above a predetermined SoC threshold). If so, converter balancing is applied to the identified battery pack (where the highest SoC battery pack discharges onto the power bus and the identified battery pack charges through the power bus via its converter) at block 728. When converter balancing is completed, process 712 may revert back to block 721 and determine whether balancing can be applied to a different combination of battery packs, where the balancing type may be the same or may be different (for example, direct balancing or staggered balancing).
Referring back to block 724, if direct balancing can be applied (for example, when the SoC difference between the highest SoC pack and the identified battery pack is below the predetermined SoC threshold), process 712 determines whether converter balancing can be applied to one or more other battery packs at block 725. If so, staggered balancing is applied with the highest SoC pack, the identified pack, and the one or more other packs at block 727. Otherwise, direct balancing is applied between the highest SoC pack and the identified battery pack at block 726.
Table 3 shows a relationship between an operational mode of a battery system and a safety interlock lock pin (indicator) and a wake pin (indicator). For example, the safety interlock pin is “On” when the battery packs are properly inserted into the battery system (as sensed by an interlocking connection through the battery pack connectors), and the wake pin is “On” when a user turns a key to activate a powered appliance (end device).
When in the off (sleep) mode, the discharging and charging arrays of the battery packs are disabled, and the battery packs consume only enough electrical power so that the battery pack may transition to another state (for example, balancing mode) when the battery pack detects an appropriate signal (for example, a wake indicator).
With some of the embodiments, as shown in Table 3, a battery system may support a plurality of operational modes: Off (Sleep), Balancing, and Charging/Discharging. While a single mode is shown for charging/discharging, charging and discharging are separate operations based on the interaction of the battery system with its external environment. For example, when the wake and safety interlock indicators are on and if charger (typically external to the battery system) is sensed via a CAN bus, the battery system enters the charging state. However, if the battery system senses an end device (for example, an appliance), the battery system enters the discharging state. As will be discussed in further detail, a battery system may support “smart charging” when in the charging mode and “smart discharging” when in the discharging mode.
End device 801 provides its power requirements in message 864 so that master battery pack 801 can determine the number of battery packs needed for end device 801 at event 852.
At event 853, master battery pack 802 gathers SoC data about the other battery packs via messages 865-868. (Master battery pack 802 may use internal messaging within the battery pack to obtain SoC about itself.) For example, in accordance with the CAN protocol, data contained in Request Pack Info message 865 may be interpreted as a request from the destination battery pack while the data in Pack Info message 866 may be interpreted as the requested data (for example, SoC data) from the destination battery pack.
Based on the gathered SoC data, master battery pack 801 determines the type of balancing required (if needed) and initiates the appropriate balancing process (for example, processes shown in
As previously discussed, embodiments may support different types of balancing, for example): converter balancing, direct balancing, and staggered balancing. Converter balancing typically requires a longer time period than direct balancing,
While the processes shown in
With converter balancing, charge of a single battery pack is transferred to one or more battery packs via converters on each of the charged battery packs. Consequently, two or more battery packs are involved with this type of balancing.
While not explicitly shown, the master battery pack gathers SoC data about all of the battery packs, including itself. For example, the master battery pack may request battery status information from the other battery packs via the CAN bus and internally obtain its own SoC data.
At block 902, the master battery pack enables the battery pack with the highest SoC for discharging by enabling the discharging array. The master battery pack also enables one or more of the battery packs with the lowest SoC to accept the charge from the discharging battery pack by enabling the charging array and the on-board converter.
The master battery pack obtains SoC values from the above battery packs at block 904 and continues the balancing process at block 905 until a desired charge balance is obtained at block 905. If the charge balance is sufficient, the battery pack may be used to power the end device. However, a faster mode of balancing (for example, direct balancing as will be discussed) may be subsequently applied.
At event 1051, master battery pack 1002 determines that packs 1003 and 1004 are to be charged by itself (pack 1002). To do so, master battery pack enables its own discharging array and enables the charging arrays and converters via messages 1061 and 1062. Balancing continues until a desired balancing charge obtained (80%, 75%, and 75%) at event 1052. At that time, the balancing ends so that master battery pack disables its charging array and disables the charging arrays and converters of battery packs 1003 and 1004 via messages 1063 and 1064.
With direct balancing, one of the battery packs is charging another battery pack through a low impedance electrical path. Consequently, only two battery packs are involved with type of balancing.
While not explicitly shown, the master battery pack obtains SoC values for all installed battery packs in the battery system. In order to do so, the master battery pack sends status requests to the slave battery packs and receives status information (for example, SoC values) from the slave battery packs via messaging on the communication channel. However, because the master battery knows about its own battery cell status, only internal messaging for the master battery is needed.
At block 1102 the master battery pack instructs the battery pack with the higher SoC to start discharging by enabling its discharging array and at block 1103 instructs one of the battery pack with the lower SoC to start charging by enabling its charging array.
At block 1104, the master battery pack gathers SoC data from the batter packs being charge balanced. When an acceptable SoC is reached at block 1105, direct balancing is terminated at block 1106.
Because pack 1202 has the lowest SoC and pack 1203 has the highest SoC, the master battery pack instructs battery pack 1202 to enable its charging array and battery pack 1203 to enable its discharging array via messages 1261 and 1262, respectively.
When the SoC values of battery packs 1202 and 1203 reach 80%, the master battery pack (pack 1202) determines that direct balancing is competed at event 1251 and consequently disables the charging array and the discharging array via messages 1263 and 1264, respectively.
Staggered balancing utilizes algorithmic direct balancing. With staggered balancing, one of the battery packs (typically the highest SoC value) direct charges another battery pack with a lower SoC while charges one or more other lower SoC battery packs through converter balancing (where the converter located on the charged battery pack is enabled). In order to keep the other lower SoC battery packs within an acceptable range, direct balancing may switch to a different lower SoC battery pack while the previous lower SoC battery pack is now converter balanced.
At blocks 1301 and 1302, direct balancing is established with a battery pack with the highest SOC with another battery pack in the group with a low SoC similar to blocks 1101 and 1102 as shown in
At block 1305, the master battery pack gathers the updated SoC values of the participating battery packs. When the battery pack being directed charge reaches a determined SoC threshold (for example, when an imbalance occurs one of the battery packs in the low SoC group), direct balancing is established with another battery pack in the low SoC group at block 1307.
When all of the battery packs are within an acceptable SoC range, as determined at block 1308, staggered balancing is terminated at block 1309.
At event 1451, master battery pack 1401 initiates direct balancing between battery packs 1402 (in the low SoC group) and 1403 (the highest SoC) and to establish converter balancing between battery 1403 and itself (also in the low SoC group). Consequently, master battery pack 1401 sends messages 1461 and 1462, corresponding to battery packs 1461 and 1462, respectively, over the communication channel and to generate any internal messaging, as necessary, to enable its charging array and converter.
As a result of the balancing, the SoC values of battery packs 1401, 1402, and 1403 change to 62%, 70%, and 88%, respectively. Because of the charge imbalance between battery packs 1401 and 1402, master battery pack 1401 establishes direct balancing between battery pack 1403 and itself and establishes converter balancing for pack 1402. Consequently, at event 1452, master battery pack 1401 instructs battery pack 1402 to enable its converter (so that charging occurs now via the converter rather than directly) via message 1463 and to disable its own converter so that its battery cells are directly exposed to charging.
Referring to
Referring to
Intelligent systems and algorithmic methods (for example, process 1700 as shown in
Still referring to
As shown in
At block 1702, an SoC threshold may be determined. The SoC threshold may be approximately equal to the SoC value of the group of one or more battery packs having SoC values just above the group of battery packs with the lowest SoC values. For example, the SoC threshold may be based on the SoC values of the second lowest level (e.g., an average of the SoC values of the battery packs of the second lowest level).
The battery packs of the group with the lowest levels of SoC can be enabled for charging at block 1703, e.g., facilitating the charging of the battery packs having the lowest level of SoC. In some aspects, the charging may be enabled if one or both of the safety interlock pin or the wake pin is set to “on,” as discussed previously.
When the SoC values of the charged battery packs reach the SoC threshold, as determined at block 1704, process 1700 may include determining whether to enlarge the list (e.g., the “Lower SoC Packs” list of step 1701) for subsequent charging at block 1705. The determination of whether to enlarge the list may be based on whether there is significant variability in to SoC of the battery packs (e.g., whether the SoC variability of the battery packs satisfies an SoC variability threshold), as will be described further in relation to
At event 1851b, charger 1801a may determine that the group of battery packs with the lowest level of SoC values includes battery packs 1802a and 1803a, and that the group of battery packs with a higher (e.g., second lowest) level of SoC values includes battery pack 1804a. A list of battery packs may be formed and may include the battery packs at the lowest levels of SoC and the battery pack at the higher (e.g., second lowest level).
At event 1851c, the charger 1801a may enable the charging of group of the battery packs with the lowest level of SoC values (e.g., battery packs 1802a and 1803a) via messages 1861 and 1862. Charging may continue until the SoC values for these battery packs satisfy an SoC threshold based on a group of one or more battery packs having higher SoC values (e.g., the battery pack having the second lowest level of SoC values (e.g., battery pack 1804a at 40%)).
At event 1852a, the charger 1801a may gather SoC values for all packs. As shown in
As discussed previously, each battery pack may have a state of charge (SoC) indicating, e.g., a degree or level of charge relative to its capacity. At step 1874, the computing device may receive a reading (e.g., first reading) of the SoC of each of the plurality of battery packs. The reading may be obtained via a sensor or a monitor at each battery pack. As discussed previously, the SoC's may vary among a plurality of battery packs or may remain relatively constant. An SoC variability (e.g., a first SoC variability) may be computed to indicate a degree of variability of the SoC of the plurality of battery packs (e.g., as in step 1875).
The SoC variability may be based on the SoC's of each of the respective battery packs obtained in step 1874. For example, an SoC variability may be based on one or more of a variance, a standard deviation, a range (e.g., an interquartile range), a mean absolute difference, a median absolute deviation, an average absolute deviation, a distance standard deviation, or a like metric based on the SoC values of each of the plurality of battery packs. For example, in Table 1 discussed above, which comprises a plurality of battery packs (e.g., Pack 1, Pack 2, Pack 3, and Pack 4), there is greater SoC variability at time TO than there is at time T6. In one aspect, where SoC variability is determined on the basis of a computed range of SoC values, the SoC variability of the battery packs at TO is 85 (i.e., 100%-15%), whereas the SoC variability at T6 is only 4 (e.g., 45%-41%). If “5” is set as an SoC variability threshold, then the SoC variability at T6 may be said to have satisfied (e.g., fall below) the threshold.
In some aspects, before the computing device can receive the SoC readings, an interlock safety pin may need to allow interaction with the battery packs to occur. For example, the computing device may initially determine that the interlock safety pin allows the receiving the SoC readings from the plurality of battery packs.
The computing device may store, e.g., in memory device 202, a metric indicating an SoC's variability threshold, e.g., to indicate whether variability of the SoC's is insignificant. For example, if an SoC of a battery pack (e.g., first battery pack) is significantly lower than an SoC of another battery pack (e.g., a second battery pack), it is likely that the SoC variability will be significant and therefore not satisfy the SoC variability threshold. At step 1876, the computing device may thus determine whether the SoC variability (e.g., as computed in step 1875) satisfies the SoC variability threshold.
If the SoC variability does not satisfy the SoC variability threshold (e.g., the variation in SoC's among the plurality of battery packs is significant) the computing device may establish an SoC threshold (e.g., as in step 1878) The SoC threshold may be based on the SoC reading of battery pack having the next higher SoC reading (e.g., the second battery pack) after the battery pack with the lowest SoC (e.g., the first battery pack). Thus, the computing device may identify the lowest SoC readings in order to determine the next higher SoC reading (e.g., as in 1877). For example, as discussed in relation to
Furthermore, at step 1879, the computing device may cause the charging of battery packs that have lower SoC's than the established SoC threshold, e.g., by enabling electric charge arrays from the charger to the battery packs. The charging may cause the SoC's of the battery packs to increase, e.g., so that it approaches, matches, and/or satisfies the SoC threshold.
In some aspects, before the computing device can cause the charging of any battery packs, a wake pin, as discussed previously, may need to allow for the charging to occur. For example, the wake pin may need to be set to “on” before a charging can occur. The computing device may initially determine that the wake pin is set to “on” before causing the charging of the battery packs.
This can be detected by the computing device via an additional reading (e.g., a second reading) of the SoC's of each of the plurality of battery packs. Furthermore, the computing device may determine or compute, based on the additional reading, a second SoC variability of the plurality of battery packs. The second SoC variability may be found to satisfy the SOC variability threshold.
If the second SoC variability is not found to satisfy the SoC variability threshold, one or more steps of method 1800C may be repeated until the SoC variability threshold is satisfied. For example, a new SoC threshold may be set based on the next higher SoC after the lowest SoC, and causing the charging of the battery packs with the lowest SoC's.
Thus, one or more iterations of the following can be performed after an updated SOC variability of the plurality of battery packs satisfies the SOC variability threshold: The computing device may identify an Nth group of one or more battery packs within the plurality of battery back devices, wherein the Nth group may have the lowest level of a previous reading of the SOC of the plurality of battery packs; the computing device may also identify an (N+1) group of one or more battery packs of the plurality of battery back devices, wherein the (N+1) group can have the second lowest level of the previous reading of the SOC of the plurality of battery packs; and the computing device may generate a list comprising the n group and the N+1 group. In each iteration, the computing device may determine that the SOC variability of the list in the current iteration does not satisfy the SOC variability threshold. If the SoC variability does satisfy the SoC threshold, the computing device may exit the iterations loop. However, assuming the SoC variability at each iteration does not satisfy the SoC variation threshold, the computing device may an SOC threshold using the previous reading of the SOC of the N+1 group. Subsequently, the computing device may cause, via electric charge arrays, the charging of the N group of battery packs to cause the SOC of the N group to increase and satisfy the SOC threshold. The computing device may receive a subsequent reading of an SOC of each of the plurality of battery packs. An updated SoC variability of the plurality of battery packs may thus be determined based on the subsequent reading of the SoC of each of the plurality of battery packs. As discussed, the above steps may be repeated until the SoC variability (updated at each iteration) satisfies the SoC variability threshold (e.g., the SoCs of the battery packs vary less than a specified range).
The following
When powering an end device (for example, a machine), connecting battery packs with varying SoC's may be problematic. Consequently, to prevent such problematic situations, a process (often implementing an intelligent method) may be needed to ensure that a required number of battery packs are connected for system discharge and enabled when appropriate.
Typically, when multiple battery packs are needed to power an end device, it may be advisable for battery packs with large SoC variations to not be connected at the same time. Rather, balancing of the battery packs may be performed initially.
Discharging may use one or more battery packs with higher SoC values first until passing a set threshold for lower SoC battery packs, at which point the lower SoC battery packs may be enabled.
Processes 2000 and 2010 shown in
Referring now to block 2001a, a power requirement of the end device may be obtained, and a first reading of a SoC of each of the plurality of battery packs may be obtained. The plurality of battery packs may include various battery packs or groups of battery packs with varying SoC values. At block 2001b, an SOC variability may be calculated to determine a degree to which the SoC values vary among the plurality of battery packs. Also or alternatively, the highest SoC level may be identified, and the computing device may determine that not all of the battery packs have SoC values the highest SoC level.
Depending on the SoC variability, the plurality of battery packs may pose a risk if they are used to concurrently power the end device. As discussed previously in relation to
Another way to address the above-described and similar risks may be to balance the battery packs, and thereby reduce the SoC variability of the plurality of battery packs, as discussed previously in relation to
The computing device may consequently determine whether or not a balancing is not required (e.g., “No” at block 2002). The decision may be a preference provided (e.g., configured) to the computing device by an operator of the computing device. Also or alternatively, the decision may be based on two or more SoC variability thresholds. For example, if the SoC variability of the plurality of battery packs is higher than a higher SoC variability threshold (e.g., a first SoC variability threshold), the pathway of balancing the battery packs may be triggered. If the SoC variability is not higher than the first SoC variability threshold but is still higher than a second SoC variability threshold (which is not as high as the first SoC variability threshold), the pathway depicted in bocks 2004-2008 may be triggered (e.g., causing battery pack(s) with higher SoCs to initially power the end device).
Referring now to blocks 2004-2005, a group of one or more battery packs may be identified and enabled (e.g., by enabling the corresponding discharge arrays) to power the end device. The group may be identified by identifying the battery packs with SoCs at the highest level, or at least at a higher level than other battery packs. The computing device may thus cause the group to power the end device, thereby beginning the discharging of the group of battery packs (e.g., as in block 2005). The group of discharging battery packs may reach an lower SoC level. The resulting lower SoC level of the group, which initially had a higher SoC level, may result in a lower SoC variability for the plurality of battery packs. The computing device may thus determine the updated SoC variability at block 2006. If the updated SoC variability fails to satisfy the SoC variability threshold (e.g., there are still battery packs with higher SoC levels), the additional battery packs may be similarly identified and enabled to power the end device at blocks 2004-2005. After the SoC variability of the plurality of battery packs satisfies the SoC variability threshold (e.g., there is not much variation in the SoC levels of the plurality of battery packs), the computing device may allow all battery packs to power the end device.
Also or alternatively, both of the above-described pathways (e.g., blocks 2002-2003 and blocks 2004-2008, respectively) may be combined. For example, after balancing has been performed at block 2003, a second reading of the SoC's of each of the plurality of battery packs may be obtained, and a second SoC variability may be calculated. The SoC variability may satisfy the SoC variability threshold, e.g., the SoC's of the plurality of battery packs may vary less and/or have a reduced range. Subsequently, the plurality of battery packs may concurrently power the end device.
At blocks 2011-2013, the SoC and SoH values of the battery packs may be gathered. The battery packs with SoH values that do not satisfy a predetermined SoH threshold may be sequestered, and in order to enabled after non-sequestered battery packs have been used. Non-sequestered battery packs (e.g., battery packs with SoH levels that satisfy the SoH threshold). may be used to initially power the end device based on the end device requirements and SoC values of the battery packs, as explained herein.
For example, at block 2013, the battery packs with SoC values that satisfy an SoC threshold (e.g., the SoC values are above the next highest level of SoC among the plurality of battery packs) may be enabled to power an end device, thereby resulting in the discharging of these battery packs at block 2014. As shown in blocks 2014-2016, the enabled battery packs can be discharged until a lower SoC value is reached (e.g., the SoC fail to satisfy the SoC threshold). At that time, additional non-sequestered battery packs may be enabled at block 2017. However, when no non-sequestered battery packs are available, the sequestered battery packs may be considered at 2018-2020.
Sequestering low SoH battery packs may be beneficial since usage of older battery packs (often associated with a low SoH value) may be reduced, thus extending the life of those battery packs.
When battery pack 2105 reaches the SoC value of the other battery packs, master battery pack 2102 enables battery packs 2103 and 2104 via messages 2163 and 2164 and may enable itself via internal messaging.
In some aspects, a process (for example, process 2200 as will be discussed) may be directed to a “limp home mode” operation for a failed Li-ion battery cell in a large-format battery pack system. A “Limp home mode” operation can safely mitigate a catastrophic failure in a system. For example, the voltage of a battery cell may become very low (e.g., below a predetermined voltage threshold), indicative of a failing battery cell. With a medium-large battery pack implementation, the internal battery management system may preemptively diagnose a failure and consequently may mitigate the failure by initiating a partial shutdown of the battery pack such that the equipment (end device) being powered by the battery system does not require a total shutdown and can still “limp home.”
When the master battery pack detects the catastrophic failure, the master battery pack determines whether an extra battery pack is needed at block 2202. For example, a battery system may have activated four battery packs when an end device needs only three battery packs with a given SoC level. If so, process 2200 disables the bad battery pack and continues operation at block 2203.
However, if the extra battery pack is needed, the master battery pack determines whether an unused battery pack (which may be the master battery pack itself) in the battery system is available at block 2204. If so, the master battery pack disables the bad battery pack (for example, disabling the discharging array) and enables the extra battery pack (for example, enabling the discharging array) at block 2205. If more than one extra battery pack is available, the master battery pack may select the extra battery pack having the largest SoC value in order to continue service for the largest possible time. However, when no extra battery packs are available and degraded operation of the end device is permitted, as determined at block 2206, the master battery pack disables the bad battery pack and sends a failure alert message to the end device about degraded operation at block 2208. However, if degraded operation is not acceptable for the end device, power is removed from the end device at block 2207 to shut down the end device.
When a fault occurs at a slave battery pack, it is possible that the slave battery pack does not send a message to the master battery pack under various failure modes. However, the master battery pack may determine that there is no longer communication from the slave battery pack and adjust a power level (derate) to the end device.
While the bad battery pack may be a slave battery pack, the master battery pack itself may be the bad battery pack. For example, a fault may occur with one of its battery cells while the processing capabilities of the master battery pack is not compromised. If so, the master battery pack may internally disable its own discharging array, attempt to enable the discharging array of a spare battery pack, and continue operating as the master battery pack.
With some embodiments, when the master battery pack has faulted, a new master battery pack may be assigned even if the faulty master battery pack is still operational. This approach ensures that the faulty master battery pack does not compromise the integrity of the overall handling of the other battery packs.
With some embodiments, when the master battery pack has faulted, a new master battery pack may be assigned to allow continued derated performance when communication to the faulty master battery is lost.
At event 2151a, master battery pack 2102a detects a catastrophic failure at battery pack 2103a in response to failure notification message 2161. For example, battery pack 2103a may provide battery status information indicative of a low battery cell voltage. The status information may be in response to a query from master battery pack 2102a or may be autonomously sent when a catastrophic event occurs. Consequently, master battery pack 2102a enables spare battery pack 2104a and disables bad battery pack 2103a via messages 2163 and 2162, respectively.
At event 2152, similar to the message scenario in
Referring to
With some embodiments, master battery pack 2102a,b may receive periodic battery status information from the other battery packs. When master battery pack 2102a,b detects a sudden drop (for example, more than a predetermined difference with respect to the previous value) in one of the battery parameters (for example, cell voltage), master battery pack 2102a,b may determine that a catastrophic failure at the corresponding battery pack is predicted or imminent and take preemptive action and/or generate a warning notification.
With some embodiments, battery cells 203 and 210 (shown in
Many illustrative embodiments are listed below in accordance with one or more aspects disclosed herein. Although many of the embodiments listed below are described as depending from other embodiments, the dependencies are not so limited. For example, embodiment #5 (below) is expressly described as incorporating the features of embodiment #1 (below), however, the disclosure is not so limited. For example, embodiment #5 may depend any one or more of the preceding embodiments (i.e., embodiment #1, embodiment #2, embodiment #3, and/or embodiment #4). Moreover, that any one or more of embodiments #2-#12 may be incorporated into embodiment #1 is contemplated by this disclosure. Likewise, any of embodiments #1, 14, 17, 22 may be combined with one or more of the features recited in embodiments #2-13, 15-16, 18-21, and/or 23-26. Further likewise, any of embodiments #27, 39, 43 may be combined with one or more of the features recited in embodiments #28-38, 40-42, 44-46. Further likewise, any of embodiments #47, 59, 64 may be combined with one or more of the features recited in embodiments #48-58, 60-63, 65-69. Further likewise, any of embodiments #70, 87, 92 may be combined with one or more of the features recited in embodiments #71-86, 88-91, 93-94. Further likewise, any of embodiments #95, 105, 109 may be combined with one or more of the features recited in embodiments #96-104, 106-108, 110-114. In addition, that any one or more of the features in embodiments #1, 14, 17, 22, 27, 39, 43, 47, 59, 64, 70, 87, 92, 95, 105, and 109 may be combined is contemplated by this disclosure. Moreover, that any one or more of the features in embodiments #1-114 can be combined is contemplated by this disclosure.
Embodiment #1. A first battery pack configured for installation in a battery system for electrically powering an end device, wherein all installed battery packs installed in the battery system have substantially identical electrical and electronic components, the first battery pack comprising:
Embodiment #2. The first battery pack of Embodiment #1, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:
Embodiment #3. The first battery pack of Embodiment #2, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:
Embodiment #4. The first battery pack of Embodiment #3, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:
Embodiment #5. The first battery pack of Embodiment #1, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:
Embodiment #6. The first battery pack of Embodiment #5, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:
Embodiment #7. The first battery pack of Embodiment #1, wherein the communication channel comprises a controller area network (CAN) bus and wherein the controller instructions, when executed by the at least one processor, further cause the controller to:
Embodiment #8. The first battery pack of Embodiment #5, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:
Embodiment #9. The first battery pack of Embodiment #1, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:
Embodiment #10. The first battery pack of Embodiment #1, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:
Embodiment #11. The first battery pack of Embodiment #1, the first battery pack comprising non-volatile memory and wherein the controller instructions, when executed by the at least one processor, further cause the controller to:
Embodiment #12. The first battery pack of Embodiment #2, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:
Embodiment #13. The first battery pack of Embodiment #12, wherein the repetitive broadcast message is sent periodically and wherein the controller instructions, when executed by the at least one processor, further cause the controller to:
Embodiment #14. A battery system configured for electrically powering an end device and comprising a plurality of battery packs, the battery system comprising:
Embodiment #15. The battery system of Embodiment #14, wherein the second battery pack comprises:
Embodiment #16. The battery system of Embodiment #15, wherein the first controller instructions, when executed by the one or more processors, further cause the first controller to:
Embodiment #17. A method of powering an end device by a battery system, the method comprising:
Embodiment #18. The method of Embodiment #17 further comprising:
Embodiment #19. The method of Embodiment #18 further comprising:
Embodiment #20. The method of Embodiment #17 further comprising:
Embodiment #21. The method of Embodiment #20 further comprising:
Embodiment #22. A battery system configured for electrically powering an end device and comprising a plurality of battery packs, the battery system comprising:
Embodiment #23. The battery system of Embodiment #22 comprising:
Embodiment #24. The battery system of Embodiment #23, wherein the third memory storing computer-executable instructions that, when executed by the third processor, cause the third battery pack to:
Embodiment #25. The battery system of Embodiment #24, wherein the updating occurs after the first and second battery packs are disconnected from the battery system.
Embodiment #26. The battery system of Embodiment #24, wherein the updating occurs while the first and second battery packs are discharging onto the power bus.
Embodiment #27. A method of powering an end device by a battery system, the battery system comprising a plurality of previously installed battery packs, wherein the plurality of previously installed battery packs include a master battery pack, the method comprising:
Embodiment #28. The method of Embodiment #27, wherein the preventing comprises:
Embodiment #29. The method of Embodiment #27, further comprising:
Embodiment #30. The method of Embodiment #29, further comprising:
Embodiment #31. The method of Embodiment #30, further comprising:
Embodiment #32. The method of Embodiment #31, further comprising:
Embodiment #33. The method of Embodiment #32, further comprising:
Embodiment #34. The method of Embodiment #32, wherein the determining whether to initiate charge balancing comprises:
Embodiment #35. The method of Embodiment #34, wherein the determining whether to initiate charge balancing further comprises:
Embodiment #36. The method of Embodiment #34, further comprising;
Embodiment #37. The method of Embodiment #36, further comprising:
Embodiment #38. The method of Embodiment #27, wherein the communication bus comprises a controller area network (CAN) bus.
Embodiment #39. A first battery pack configured for installation in a battery system for electrically powering an end device, wherein all installed battery packs installed in the battery system have identical electrical and electronic components, the first battery pack comprising:
Embodiment #40. The first battery pack of Embodiment #39, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:
Embodiment #41. The first battery pack of Embodiment #40, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:
Embodiment #42. The first battery pack of Embodiment #41, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:
Embodiment #43. A battery system configured for electrically powering an end device and comprising a plurality of battery packs, the battery system comprising:
Embodiment #44. The battery system of Embodiment #43, wherein the first memory storing controller instructions that, when executed by the at least one processor, cause the first controller to:
Embodiment #45. The battery system of Embodiment #44, wherein the second battery pack includes:
Embodiment #46. The battery system of Embodiment #45, wherein the second memory storing controller instructions that, when executed by the one or more processors, further cause the second controller to:
Embodiment #47. A first battery pack configured for installation in a battery system for electrically powering an end device, wherein all installed battery packs installed in the battery system have identical electrical and electronic components, the first battery pack comprising:
Embodiment #48. The first battery pack of Embodiment #47, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:
Embodiment #49. The first battery pack of Embodiment #48, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:
Embodiment #50. The first battery pack of Embodiment #49, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:
Embodiment #51. The first battery pack of Embodiment #47, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:
Embodiment #52. The first battery pack of Embodiment #47, wherein the communication channel comprises a controller area network (CAN) bus.
Embodiment #53. The first battery pack of Embodiment #47, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:
Embodiment #54. The first battery pack of Embodiment #47, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:
Embodiment #55. The first battery pack of Embodiment #54, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:
Embodiment #56. The first battery pack of Embodiment #47, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:
Embodiment #57. The first battery pack of Embodiment #47, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:
Embodiment #58. The first battery pack of Embodiment #47, wherein the controller instructions, when executed by the at least one processor, further cause the controller to:
Embodiment #59. A method of powering an end device by a battery system, the method comprising:
Embodiment #60. The method of Embodiment #59, comprising:
Embodiment #61. The method of Embodiment #59, comprising:
Embodiment #62. The method of Embodiment #59, comprising:
Embodiment #63. The method of Embodiment #62, comprising:
Embodiment #64. A battery system configured for electrically powering an end device and comprising a plurality of battery packs, the battery system comprising:
Embodiment #65. The battery system of Embodiment #64, wherein the first memory storing controller instructions that, when executed by the at least one processor, cause the first controller to:
Embodiment #66. The battery system of Embodiment #65, wherein the first memory storing controller instructions that, when executed by the at least one processor, cause the first controller to:
Embodiment #67. The battery system of Embodiment #64, wherein the first memory storing controller instructions that, when executed by the at least one processor, cause the first controller to:
Embodiment #68. The battery system of Embodiment #64, wherein the slave battery pack includes:
Embodiment #69. The battery system of Embodiment #68, wherein the second memory storing controller instructions that, when executed by the one or more processors, cause the second controller to
Embodiment #70. A method of powering an end device by a battery system, the battery system comprising a plurality of battery packs, the method comprising:
Embodiment #71. The method of Embodiment #70, wherein the plurality of balancing types comprise a converter balancing technique, a direct balancing technique, and a staggered balancing technique.
Embodiment #72. The method of Embodiment #71, comprising:
Embodiment #73. The method of Embodiment #72, comprising:
Embodiment #74. The method of Embodiment #73, comprising:
Embodiment #75. The method of Embodiment #73, comprising:
Embodiment #76. The method of Embodiment #75, wherein one of the first, second, and third battery packs serves as the master battery pack of the battery system.
Embodiment #77. The method of Embodiment #72, comprising:
Embodiment #78. The method of Embodiment #77, comprising:
Embodiment #79. The method of Embodiment #77, wherein one of the first and fourth battery packs serves as the master battery pack.
Embodiment #80. The method of Embodiment #72, comprising:
Embodiment #81. The method of Embodiment #80, comprising:
Embodiment #82. The method of Embodiment #81, comprising:
Embodiment #83. The method of Embodiment #82, comprising:
Embodiment #84. The method of Embodiment #75, wherein one of the first, fifth, and sixth battery packs serves as the master battery pack of the battery system.
Embodiment #85. The method Embodiment #70, further comprising:
Embodiment #86. The method Embodiment #70, wherein the applying comprises:
Embodiment #87. A first battery pack configured for installation in a battery system for electrically powering an end device, wherein all installed battery packs installed in the battery system have identical electrical and electronic components, the first battery pack comprising:
Embodiment #88. The first battery pack of Embodiment #87, wherein the memory storing controller instructions that, when executed by the at least one processor, cause the controller to:
Embodiment #89. The first battery pack of Embodiment #88, wherein the memory storing controller instructions that, when executed by the at least one processor, cause the controller to:
Embodiment #90. The first battery pack of Embodiment #88, wherein the memory storing controller instructions that, when executed by the at least one processor, cause the controller to:
Embodiment #91. The first battery pack of Embodiment #88, wherein the memory storing controller instructions that, when executed by the at least one processor, cause the controller to:
Embodiment #92. A battery system configured for electrically powering an end device and comprising a plurality of battery packs, the battery system comprising:
Embodiment #93. The battery system of Embodiment #92, wherein the memory storing controller instructions that, when executed by the at least one processor, cause the controller to:
Embodiment #94. The battery system of Embodiment #93, wherein the memory storing controller instructions that, when executed by the at least one processor, cause the controller to:
Embodiment #95. A method comprising:
Embodiment #96. The method of Embodiment #95, further comprising:
Embodiment #97. The method of Embodiment #95, wherein the receiving the first reading of the SOC of each of the plurality of battery packs further comprises:
Embodiment #98. The method of Embodiment #95, wherein the causing the charging further comprises enabling an electric discharge array from a charger to the one or more battery packs of the first group of one or more battery packs via a converter.
Embodiment #99. The method of Embodiment #95, wherein the plurality of battery packs further comprises at least a third group of one or more battery packs, and wherein the method further comprises:
Embodiment #100. The method of Embodiment #99, wherein the generating the second list comprises expanding the first list to include battery packs having the second lowest level for the second reading of the SOC.
Embodiment #101. The method of Embodiment #99, further comprising:
Embodiment #102. The method of Embodiment #101, further comprising:
Embodiment #103. The method of Embodiment #95, further comprising:
Embodiment #104. The method of Embodiment #95, further comprising:
Embodiment #105. A method comprising:
Embodiment #106. The method of Embodiment #105, further comprising:
Embodiment #107. The method of Embodiment #105, further comprising:
Embodiment #108. The method of Embodiment #105, wherein the receiving the first reading of the SOC of each of the plurality of battery packs further comprises:
Embodiment #109. A method comprising:
Embodiment #110. The method of Embodiment #109, further comprising:
Embodiment #111. The method of Embodiment #110, further comprising:
Embodiment #112. The method of Embodiment #109, further comprising:
Embodiment #113. The method of Embodiment #109, wherein the receiving the first reading of the SOC of each of the plurality of battery packs further comprises:
Embodiment #114. The method of Embodiment #109, wherein the causing the second group to charge the first battery pack occurs via one or more of a converter balancing, a direct connect balancing, or a staggered balancing.
With some embodiments, the term “large-format” encompasses medium-format battery embodiments and use cases. For example, medium-scale and large-scale applications are embodied by the numerous descriptions herein.
Although many of the systems and methods described herein reference Lithium ion battery storage chemistry, the disclosure is not so limited. In many instances, a person of ordinary skill in the art will appreciate that other major chemistries for rechargeable batteries may be appropriated substituted without substantially departing from the spirit of the solution: Lithium-ion (Li-ion), Nickel Cadmium (Ni—Cd), Nickel-Metal Hydride (Ni-MH), Lead-Acid, and other chemistries. With some embodiments, the battery management system disclosed herein may be included with these technology batteries to provide battery protection, provide improved efficiency, and provide a better user experience than previous battery technologies. Variants of the lithium cobalt cathode, such as nickel cobalt aluminum (NCA) and nickel manganese cobalt (NMC), may be desirable in electric vehicles and other applications. Other new cathode chemistries, such as lithium manganese spinel (LMO) and lithium iron phosphate (LFP), may be used where appropriate. Moreover, large-format battery packs offer lower system integration costs because, inter alia, it enables a reduced number of battery interconnections, further improving the reliability of the battery pack and providing for a much higher value proposition.
As can be appreciated by one skilled in the art, a computer system with an associated computer-readable medium containing instructions for controlling the computer system can be utilized to implement the exemplary embodiments that are disclosed herein. The computer system may include at least one computer such as a microprocessor, digital signal processor, and associated peripheral electronic circuitry.
This application is a continuation of U.S. patent application Ser. No. 17/395,987 (Attorney Docket No. 009231.00223), filed Aug. 6, 2021, which is a continuation of U.S. patent application Ser. No. 17/183,422 (Attorney Docket No. 009231.00208), filed Feb. 24, 2021, now U.S. Pat. No. 11,095,140, which is a continuation of U.S. patent application Ser. No. 16/937,931 (Attorney Docket No. 009231.00200), filed Jul. 24, 2020, now U.S. Pat. No. 10,944,278, which is a continuation of International Patent Application Serial No. PCT/CN2020/093886 with an international filing date of Jun. 2, 2020. U.S. patent application Ser. No. 17/395,987, filed Aug. 6, 2021, is also a continuation of U.S. patent application Ser. No. 16/937,979 (Attorney Docket No. 009231.00201), filed Jul. 24, 2020, now U.S. Pat. No. 10,944,279, which is a continuation of International Patent Application serial no. PCT/CN2020/093886 with an international filing date of Jun. 2, 2020. U.S. patent application Ser. No. 17/395,987, filed Aug. 6, 2021, is also a continuation of U.S. patent application Ser. No. 16/938,008 (Attorney Docket No. 009231.00202), filed Jul. 24, 2020, now U.S. Pat. No. 10,938,221, which is a continuation of International Patent Application serial no. PCT/CN2020/093886 with an international filing date of Jun. 2, 2020. U.S. patent application Ser. No. 17/395,987, filed Aug. 6, 2021, is also a continuation entitled to and claiming the benefit of priority to International Patent Application serial no. PCT/CN2020/093886 (Attorney Docket No. 009231.00205) with an international filing date of Jun. 2, 2020. All of the aforementioned are herein incorporated by reference in their entireties for all purposes.
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17395987 | Aug 2021 | US |
| Child | 18202612 | US | |
| Parent | 17183422 | Feb 2021 | US |
| Child | 17395987 | US | |
| Parent | 16937931 | Jul 2020 | US |
| Child | 17183422 | US | |
| Parent | PCT/CN20/93886 | Jun 2020 | US |
| Child | 16937931 | US | |
| Parent | 16937979 | Jul 2020 | US |
| Child | 17183422 | US | |
| Parent | 16938008 | Jul 2020 | US |
| Child | 16937979 | US |
