Battery system and power supply device

Abstract

The application provides a battery system and a power supply device. The battery system comprises at least two battery clusters; each battery cluster comprises at least one battery module and a module-level controller corresponding to the battery module, and the battery module is controlled by the corresponding module-level controller; the module-level controllers in the battery clusters are connected in communication through a first CAN bus; the first CAN buses in each battery cluster are connected in communication through a CAN extender, forming an extended CAN bus, so that the module-level controllers in the battery system can realize cross-cluster communication through the extended CAN bus and share cross-cluster information, thereby solving the problem that the battery modules in multiple battery clusters cannot realize cross-cluster information sharing and enabling the battery modules to cross the "cluster" limitation and be arranged without obstacles.

Description

Technical Field

[0001] This invention relates to the field of battery technology, and more particularly to a battery system and power supply device. Background Technology

[0002] Batteries, as energy storage tools, are widely used in various fields. Currently, a battery cabinet, as a battery cluster, can include multiple battery modules, which share information via a CAN (Controller Area Network) bus. However, the number of battery modules within a single battery cluster is limited. As demand increases, a single battery cluster cannot meet the needs, requiring multiple battery clusters to form a battery system. However, how to achieve cross-cluster information sharing among battery modules within multiple battery clusters is a pressing problem that needs to be solved. Summary of the Invention

[0003] This invention provides a battery system and power supply device to solve the problem that the prior art cannot achieve cross-cluster information sharing among battery modules within multiple battery clusters.

[0004] In a first aspect, embodiments of the present invention provide a battery system, comprising: at least two battery clusters; each battery cluster includes at least one battery module and a module-level controller corresponding to each battery module, wherein the battery module is controlled by the corresponding module-level controller;

[0005] The module-level controller in the battery cluster communicates via the first CAN bus;

[0006] The first CAN buses in each battery cluster are connected through CAN extenders to form an extended CAN bus, enabling cross-cluster communication and information sharing between the module-level controllers in the battery system.

[0007] In one possible implementation, the battery system also includes a cluster-level controller corresponding to each battery cluster; each cluster-level controller communicates with the others via a second CAN bus.

[0008] The CAN extender includes a second CAN bus between the cluster-level controller and the cluster-level controller;

[0009] The first CAN bus, the cluster-level controller, and the second CAN bus form an extended CAN bus;

[0010] Cluster-level controllers are used to pass through received data, enabling data relay.

[0011] In one possible implementation, the CAN extender includes a CAN bus connection interface;

[0012] The first CAN buses in each battery cluster are connected through a CAN bus connection interface to form an extended CAN bus.

[0013] In one possible implementation, each module-level controller in the battery system determines the synchronization master and synchronization slave through master-slave competition every preset time interval, and the synchronization master sends a synchronization frame to the extended CAN bus, and the synchronization slave obtains the synchronization frame from the extended CAN bus.

[0014] Synchronization master and synchronization slave synchronize modules through synchronization frames.

[0015] In one possible implementation, after synchronizing the modules, the synchronous master and synchronous slave calculate their own current sharing data and send their current sharing data to the extended CAN bus in the form of a current sharing information sharing frame.

[0016] In one possible implementation, when the synchronization master is lost, the synchronization slave still calculates its own current sharing data, sends its own current sharing data to the extended CAN bus in the form of a current sharing information sharing frame, and after a preset time, re-determines the synchronization master through master-slave competition.

[0017] In one possible implementation, the individual module-level controllers in the battery system receive current sharing information sharing frames during ADC interrupts.

[0018] In one possible implementation, each module-level controller in the battery system determines its own state value through its output state and ID address, and competes for master-slave status based on its own state value to determine the synchronization master and synchronization slave.

[0019] In one possible implementation, the more battery modules there are in the battery system, the higher the occupancy of the extended CAN bus.

[0020] Secondly, embodiments of the present invention also provide a power supply device, including the battery system described in the first aspect or any possible implementation thereof.

[0021] This invention provides a battery system and power supply device. The battery system includes at least two battery clusters. Each battery cluster includes at least one battery module and a module-level controller corresponding to each battery module. The battery module is controlled by the corresponding module-level controller. The module-level controllers in each battery cluster are connected via a first CAN bus. The first CAN buses in each battery cluster are connected via a CAN extender to form an extended CAN bus. This enables cross-cluster communication and cross-cluster information sharing between the module-level controllers in the battery system through the extended CAN bus. This solves the problem that battery modules in multiple battery clusters cannot share information across clusters, and enables battery modules to overcome cluster limitations and be matched without obstacles. Attached Figure Description

[0022] To more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0023] Figure 1 This is a schematic diagram of the structure of a battery system provided in an embodiment of the present invention;

[0024] Figure 2 This is a schematic diagram of the structure of a battery system provided in another embodiment of the present invention;

[0025] Figure 3 This is a schematic diagram of the structure of a battery system provided in another embodiment of the present invention;

[0026] Figure 4 This is a schematic diagram of synchronous sampling provided in an embodiment of the present invention. Detailed Implementation

[0027] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of the invention. However, those skilled in the art will understand that the invention can be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods are omitted so as not to obscure the description of the invention with unnecessary detail.

[0028] To make the objectives, technical solutions, and advantages of the present invention clearer, specific embodiments will be described below in conjunction with the accompanying drawings.

[0029] See Figure 1The diagram illustrates the structure of a battery system provided in an embodiment of the present invention. The battery system may include at least two battery clusters 10; each battery cluster 10 includes at least one battery module 11 and a module-level controller (PBMU) corresponding to each battery module 11, wherein the battery module 11 is controlled by the corresponding PBMU.

[0030] The module-level controller PBMU in battery cluster 10 is connected to the first CAN bus 12 for communication.

[0031] The first CAN bus 12 in each battery cluster 10 is connected to each other through CAN extender 20 to form an extended CAN bus, enabling cross-cluster communication and cross-cluster information sharing between the various module-level controllers (PBMUs) in the battery system.

[0032] See Figure 1 In order to realize cross-cluster communication and cross-cluster information sharing between different battery clusters 10, the first CAN bus 12 in each battery cluster 10 is connected by a CAN extender 20. Thus, the first CAN bus 12 in each battery cluster 10 and the CAN extender 20 can form an extended CAN bus. In this way, all module-level controllers (PBMUs) in the battery system can communicate and share information through the extended CAN bus, so that the module-level controllers (PBMUs) in different battery clusters 10 can communicate, thereby realizing the synchronous control of battery modules 11 in different battery clusters 10.

[0033] In each battery cluster 10, there is a one-to-one correspondence between the battery module 11 and the module-level controller (PBMU), and the battery module 11 is controlled by the corresponding module-level controller (PBMU). The number of battery modules 11 in each battery cluster 10 can be one, two, or more, and correspondingly, the number of module-level controllers (PBMUs) in each battery cluster 10 can be one, two, or more, without specific restrictions.

[0034] The module-level controller (PBMU) can share information via the extended CAN bus to achieve current sharing control, charge and discharge control, and other functions for the battery module 11. The battery cluster 10 can also be referred to as a battery cabinet.

[0035] Battery module 11 can be a lithium battery module or a rechargeable battery module; no specific restriction is imposed here. Battery modules 11 can be connected in parallel or in series; no specific restriction is imposed here.

[0036] The battery system provided in this application embodiment includes at least two battery clusters 10; each battery cluster 10 includes at least one battery module 11 and a module-level controller PBMU corresponding to each battery module 11. The battery module 11 is controlled by the corresponding module-level controller PBMU. The module-level controller PBMU in each battery cluster 10 is connected through a first CAN bus 12. The first CAN buses 12 in each battery cluster 10 are connected through a CAN extender 20 to form an extended CAN bus, so that the module-level controllers PBMU in the battery system can achieve cross-cluster communication and cross-cluster information sharing through the extended CAN bus. This can solve the problem that the battery modules 11 in multiple battery clusters 10 cannot achieve cross-cluster information sharing, and enable the battery modules 11 to cross the "cluster" limitation and be matched without obstacles. This allows the module-level controllers PBMU in the battery system to achieve cross-cluster master-slave control or cross-cluster masterless control, and enables cross-cluster parallel connection between modules.

[0037] In some embodiments, see Figure 2 The battery system also includes a cluster-level controller (SBMU) corresponding to each battery cluster 10; each cluster-level controller (SBMU) is connected to communicate via the second CAN bus 21.

[0038] CAN extender 20 includes a second CAN bus 21 between cluster level controller SBMU and cluster level controller SBMU;

[0039] The first CAN bus 12, the cluster level controller SBMU, and the second CAN bus 21 form an extended CAN bus;

[0040] The cluster-level controller SBMU is used to pass through the received data, realizing data relay.

[0041] In this embodiment, the cluster-level controller SBMU only relays data and does not perform any other processing on the data.

[0042] The first CAN bus 12 in each battery cluster 10, the cluster-level controller SBMU corresponding to each battery cluster 10, and the second CAN bus 21 connecting each cluster-level controller SBMU form an extended CAN bus, so that the module-level controllers PBMU in the same battery cluster 10 and different battery clusters 10 can communicate and share information through the extended CAN bus.

[0043] For example, when the module-level controller PBMU performs cross-cluster information sharing, when the module-level controller PBMU uploads data to the extended CAN bus, it sequentially uploads the data to the second CAN bus 21 through the first CAN bus 12 connected to it and the cluster-level controller SBMU corresponding to its battery cluster 10; when the module-level controller PBMU receives data from the extended CAN bus, the second CAN bus 21 sequentially transmits the data to the module-level controller PBMU through the cluster-level controller SBMU corresponding to its battery cluster 10 and the first CAN bus 12 connected to it.

[0044] When the module-level controller PBMU performs intra-cluster information sharing, it can share information only through the first CAN bus 12 connected to it, or as described above when sharing information across clusters, it can share information through the second CAN bus 21, the cluster-level controller SBMU, and the first CAN bus 12.

[0045] In some embodiments, see Figure 3 The CAN extender 20 includes a CAN bus connection interface 22;

[0046] The first CAN bus 12 in each battery cluster 10 is connected through the CAN bus connection interface 22 to form an extended CAN bus.

[0047] The number of CAN bus connection interfaces 22 can be one or more, depending on actual needs.

[0048] For example, all the first CAN buses 12 can be connected through a CAN bus connection interface 22 to form an extended CAN bus; or an extended CAN bus can be formed by connecting the first CAN buses 12 in adjacent battery clusters 10 through N-1 CAN bus connection interfaces 22, where N is the number of battery clusters 10; and so on.

[0049] This application does not impose specific restrictions on the structure of the CAN bus connection interface 22. Any interface structure that can connect to the CAN bus and realize information communication is acceptable.

[0050] This application provides two implementation schemes for the CAN extender 20 described above. In practical applications, any implementation scheme of the CAN extender 20 can be adopted. In a preferred embodiment, when the number of battery modules 11 in the battery system is small, the scheme of CAN bus connection interface 22 can be adopted; when the number of battery modules 11 in the battery system is large, the scheme of cluster level controller SBMU and second CAN bus 21 can be adopted.

[0051] In some embodiments, each module-level controller (PBMU) in the battery system determines the synchronization master and synchronization slave through master-slave competition every preset time interval, and the synchronization master sends a synchronization frame to the extended CAN bus, and the synchronization slave obtains the synchronization frame from the extended CAN bus.

[0052] The master and slave modules synchronize with each other via synchronization frames.

[0053] In this embodiment, to achieve sampling synchronization among battery modules 11, each module-level controller (PBMU) in the battery system can determine the synchronization master through master-slave competition. Module-level controllers (PBMUs) that are not determined as synchronization masters are defaulted to synchronization slaves. The synchronization master can send synchronization frames to the extended CAN bus, and the synchronization slaves receive the synchronization frames from the extended CAN bus. Thus, the synchronization master and synchronization slaves can achieve synchronized sampling among battery modules 11 through the synchronization frames.

[0054] The above process can be repeated at preset intervals to synchronize the battery modules 11. Alternatively, after determining the synchronization master, the synchronization master can send synchronization frames to the extended CAN bus at preset intervals until the synchronization master is lost, and then the master-slave competition is restarted to determine the synchronization master again.

[0055] The preset duration can be determined according to actual usage needs, such as 100ms, 200ms, etc.

[0056] In some embodiments, after synchronizing the modules, the synchronization master and synchronization slave calculate their own current sharing data and send their own current sharing data to the extended CAN bus in the form of a current sharing information sharing frame.

[0057] The self-current sharing data can include the average current of itself over a certain period of time (e.g., 10ms); it can also include its own SOC value and its own average current integral, etc.

[0058] After performing synchronous sampling, the synchronous master and synchronous slave will calculate the current sharing data of the corresponding battery module 11 and send the current sharing data to the extended CAN bus in the form of a current sharing information sharing frame. At the same time, they can receive current sharing data sent by other module-level controllers (PBMUs).

[0059] To avoid information congestion, each module-level controller (PBMU) can send its own flow sharing data in ascending or descending order of address, based on its own address.

[0060] For example, the preset duration can be used as a period. The period can be timed by a synchronization frame timer. When the module-level controller (PBMU) receives or sends a synchronization frame, it clears the synchronization frame timer and starts timing again. When the synchronization frame timer reaches the preset duration, it determines whether it is the synchronization master through master-slave competition, calculates and sends its own flow sharing data, and repeats the above process periodically.

[0061] In some embodiments, when the synchronization master is lost, the synchronization slave still calculates its own flow sharing data, sends its own flow sharing data to the extended CAN bus in the form of flow sharing information sharing frames, and after a preset time period, re-determines the synchronization master through master-slave competition.

[0062] In this embodiment, when a synchronization slave detects the loss of the synchronization master in a certain cycle, that is, when it detects that there is no synchronization master in the system, it can still rely on its own inertia to autonomously calculate and send its own flow sharing data. In the next cycle, each synchronization slave can compete for master and slave again to determine the synchronization master.

[0063] For example, see Figure 4 Assuming the preset duration is 100ms, 1, 2, ..., M on the left represent the addresses of each module-level controller (PBMU), and M is the number of module-level controllers (PBMUs) in the battery system.

[0064] At 0ms, the system has no synchronization master. At 100ms, all module-level controllers (PBMUs) send current sharing data to the extended CAN bus. At 200ms, a synchronization master is selected, with the PBMU at address 1 becoming the synchronization master. The synchronization master sends synchronization frames, and the synchronization slaves receive them. Each PBMU synchronizes and recalculates its own current sharing data. After calculation, it sends the current sharing data to the extended CAN bus. At 300ms, the process at 200ms is repeated. At 400ms, the PBMU at address 1 malfunctions, and the synchronization master is lost. At 420ms, each synchronization slave still autonomously calculates its own current sharing data and sends it to the extended CAN bus. The process involves several steps: At 520ms, the slave devices re-enter the master-slave competition to determine the master. The PBMU with address 2 becomes the master, sends a synchronization frame, and the slave devices receive it. Each PBMU synchronizes and recalculates its own current sharing data. After calculation, it sends the current sharing data to the extended CAN bus. At 620ms, the PBMU with address 1 returns to normal, becomes a slave, receives the synchronization frame, synchronizes, and sends the current sharing data. Other PBMUs repeat the actions of the previous cycle. At 720ms, the master-slave competition resumes, and the PBMU with address 1 becomes the master again, repeating the process from 200ms.

[0065] In some embodiments, each module-level controller (PBMU) in the battery system receives a current sharing information sharing frame during an ADC interrupt.

[0066] Because multiple PBMUs (Module Level Controllers) send data to the extended CAN bus, information congestion may occur. When one PBMU sends data to the extended CAN bus, other PBMUs must receive it promptly. If the data is not received in time, the next PBMU will send data to the extended CAN bus, overwriting the data sent by the previous PBMU. To solve this problem, in this embodiment, each PBMU receives the current sharing information frame during the ADC interrupt. The PBMUs iterate through and query the frames during the ADC interrupt, which improves the real-time performance of the current sharing information frame and prevents data from being overwritten and unreceived.

[0067] In some possible implementations, the synchronization frame has high real-time requirements, and the various module-level controllers (PBMUs) in the battery system can also receive the synchronization frame in the ADC interrupt.

[0068] In some embodiments, each module-level controller (PBMU) in the battery system determines its own state value through its own output state and ID address, and competes for master-slave status based on its own state value to determine the synchronization master and synchronization slave.

[0069] For example, the status value = output status value * first sovereign weight + ID address * second sovereign weight. The output status can include normal or abnormal. Each module-level controller (PBMU) can use the one with the smallest status value as the synchronization master. In this case, when the output status is normal, the output status value is 0; when the output status is abnormal, the output status value is 1. Alternatively, each module-level controller (PBMU) can use the one with the largest status value as the synchronization master. In this case, when the output status is normal, the output status value is 1; when the output status is abnormal, the output status value is 0. The first and second sovereign weights can be set according to actual needs; for example, the first sovereign weight can be 20, the second sovereign weight can be 1, and so on.

[0070] In some embodiments, the more battery modules 11 there are in the battery system, the higher the occupancy of the extended CAN bus.

[0071] In this embodiment, the more battery modules 11 there are in the battery system, the more module-level controllers (PBMUs) need to send data to the extended CAN bus in the same cycle, and the higher the occupancy rate of the extended CAN bus.

[0072] Corresponding to the battery system described above, this application also provides a power supply device, including any of the battery systems described above, and having the beneficial effects of any of the battery systems described above.

[0073] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0074] In the embodiments provided by this invention, it should be understood that the disclosed system / device can be implemented in other ways. For example, the device / controller embodiments described above are merely illustrative; multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interface, or the indirect coupling or communication connection of the device or unit may be electrical, mechanical, or other forms.

[0075] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0076] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0077] The above-described embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be included within the protection scope of the present invention.

Claims

1. A battery system, characterized in that, include: At least two battery clusters; each battery cluster includes at least one battery module and a module-level controller corresponding to each battery module, wherein the battery module is controlled by the corresponding module-level controller; The module-level controllers in the battery clusters communicate with each other via a first CAN bus; the first CAN buses in different battery clusters are not directly connected. The first CAN buses in each battery cluster are connected to each other through a CAN extender to form an extended CAN bus, enabling cross-cluster communication and cross-cluster information sharing between the module-level controllers in the battery system through the extended CAN bus. The battery system further includes cluster-level controllers corresponding to each battery cluster; each cluster-level controller is connected via a second CAN bus; the CAN extender includes a second CAN bus between the cluster-level controllers; the first CAN bus, the cluster-level controllers, and the second CAN bus form the extended CAN bus. The cluster-level controller is used to pass through the received data to achieve data relay; Alternatively, the CAN extender includes a CAN bus connection interface; the first CAN buses in each of the battery clusters are connected through the CAN bus connection interface to form an extended CAN bus.

2. The battery system according to claim 1, characterized in that, In the battery system, each module-level controller determines the synchronization master and synchronization slave through master-slave competition at preset intervals. The synchronization master sends a synchronization frame to the extended CAN bus, and the synchronization slave obtains the synchronization frame from the extended CAN bus. The synchronization master and the synchronization slave synchronize the modules through the synchronization frame.

3. The battery system according to claim 2, characterized in that, After synchronizing the modules, the synchronization master and the synchronization slave calculate their own current sharing data and send their current sharing data to the extended CAN bus in the form of a current sharing information sharing frame.

4. The battery system according to claim 3, characterized in that, When the synchronization master is lost, the synchronization slave still calculates its own flow sharing data, sends its own flow sharing data to the extended CAN bus in the form of flow sharing information sharing frames, and after the preset time period, re-determines the synchronization master through master-slave competition.

5. The battery system according to claim 3, characterized in that, Each module-level controller in the battery system receives the current sharing information sharing frame during an ADC interrupt.

6. The battery system according to claim 2, characterized in that, Each module-level controller in the battery system determines its own status value through its output status and ID address, and competes for master-slave status based on its own status value to determine the synchronization master and synchronization slave.

7. A power supply device, characterized in that, Includes the battery system as described in any one of claims 1 to 6.

Images