Battery sub-pack monitoring device and server

Abstract

The utility model discloses a kind of battery sub-package monitoring device and server, device includes: controller, power module, bridging module and communication module;Power module is used to power supply controller, bridging module and communication module;Bridging module is connected with battery collector;Controller is configured to obtain the battery sub-package state information provided by battery collector through bridging module;Controller is further configured to upload battery sub-package state information and offline test information to server through communication module;Offline test information includes the test information generated when battery sub-package carries out offline test.

Description

Technical Field

[0001] This utility model relates to the field of battery management technology, and in particular to a battery subpack monitoring device and server. Background Technology

[0002] Battery modules are widely used across various industries today, and their life cycle covers multiple key stages, including production, storage, transportation, application, secondary use, and disposal.

[0003] Because battery modules have self-discharge characteristics, their charge levels can change even when not in use. Therefore, monitoring batteries in their non-operational state is particularly important. In practical applications, many non-operational battery modules lack a battery manager (for example, in most new energy commercial vehicles, the battery pack typically consists of multiple battery sub-packs, which only contain battery data acquisition units but lack a battery manager). In such cases, effective status monitoring of the battery sub-packs is difficult to achieve. Utility Model Content

[0004] This utility model provides a battery subpack monitoring device and server to achieve the purpose of monitoring the status of battery subpacks that are not in operation and do not have a battery manager.

[0005] In a first aspect, this utility model provides a battery pack monitoring device, including: a controller, a power module, a bridging module, and a communication module;

[0006] The power module is used to supply power to the controller, the bridge module, and the communication module;

[0007] The bridging module is connected to the battery collector;

[0008] The controller is configured to obtain battery sub-pack status information provided by the battery collector through the bridging module;

[0009] The controller is also configured to upload the battery subpack status information and offline test information to the server via the communication module;

[0010] The offline test information includes the test information generated when the battery subpack undergoes offline testing.

[0011] Optionally, the controller is configured with a reverse wake-up terminal;

[0012] The reverse wake-up terminal is connected to the bridging module, and the controller is configured to receive the reverse wake-up signal sent by the battery collector through the reverse wake-up terminal. The reverse wake-up information is used by the battery collector to reverse wake up the controller.

[0013] Optionally, the controller is also configured with a communication terminal;

[0014] The communication terminal is connected to the bridging module, and the controller is configured to obtain the battery subpack status information sent by the bridging module through the communication terminal.

[0015] Optionally, if the battery collector does not have non-volatile storage capability, the communication terminal is also used to connect to the offline test battery manager;

[0016] The controller is also configured to receive the offline test information sent by the offline test battery manager through the communication terminal;

[0017] The controller is also configured to store the offline test information.

[0018] Optionally, if the battery collector has non-volatile storage capability, the controller is further configured as follows:

[0019] The offline test information stored by the battery collector is obtained from the bridging module through the communication terminal.

[0020] Optionally, the bridging module is further configured with a first communication interface and a second communication interface;

[0021] The communication terminal is connected to the first communication interface, the first communication interface is connected to the second communication interface via a first communication line, and the second communication interface is connected to the bridging module.

[0022] The first communication interface, the second communication interface, and the first communication line are used for communication between the controller and the bridging module based on a differential communication protocol.

[0023] Optionally, the communication terminal is connected to the bridging module via a second communication line;

[0024] The second communication line is used for communication between the controller and the bridging module based on a serial communication protocol.

[0025] Optionally, the power module includes a power supply module and a power management module;

[0026] The power supply module is connected to the power management module, and the power supply module is used to provide power to the power management module;

[0027] The power management module is used to supply power to the controller, the bridging module, and the communication module.

[0028] Optionally, the bridging module is connected to the battery collector via a daisy chain.

[0029] Secondly, this utility model embodiment also provides a server, which is communicatively connected to any of the battery pack monitoring devices described in this utility model embodiment through a communication module;

[0030] The server is configured to receive battery subpacket status information and offline test information uploaded by the battery subpacket monitoring device, and to locate abnormal battery subpackets based on the battery subpacket status information and offline test information.

[0031] Compared with existing technologies, the advantages of this utility model are as follows: This utility model proposes a battery sub-pack monitoring device, which includes a bridging module for communicating with a battery data acquisition unit configured in the battery sub-pack. The bridging module can obtain independently stored status monitoring data of the battery sub-pack through the battery data acquisition unit, thus enabling status monitoring of the battery sub-pack even when a battery manager is not configured. The battery sub-pack monitoring device is also equipped with a communication module, which can be used to upload battery sub-pack status information and offline test information to a server. Based on the server, it can help maintenance personnel to remotely monitor the battery sub-pack. In addition, the server can also analyze the battery sub-pack status information, thereby providing data support for the maintenance and optimization of the battery sub-pack. The battery sub-pack monitoring device is also equipped with a power module to power the battery data acquisition unit, ensuring the basic operation of the battery data acquisition unit and ensuring that the battery data acquisition unit can obtain the status monitoring data of the battery sub-pack during storage. Attached Figure Description

[0032] Figure 1 This is a structural block diagram of the battery subpack monitoring device in the embodiment;

[0033] Figure 2 This is a structural block diagram of another battery pack monitoring device in the embodiment;

[0034] Figure 3 This is a structural block diagram of another battery pack monitoring device in the embodiment;

[0035] Figure 4 This is a structural block diagram of another battery pack monitoring device in the embodiment;

[0036] Figure 5 This is a flowchart illustrating the battery sub-pack outbound process in the embodiment. Detailed Implementation

[0037] The present invention will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present invention and not intended to limit it. Furthermore, it should be noted that, for ease of description, the accompanying drawings show only the parts relevant to the present invention, not the entire structure.

[0038] Figure 1 This is a structural block diagram of the battery pack monitoring device in the embodiment, for reference. Figure 1 The battery pack monitoring device includes: a controller 100, a power module 200, a bridging module 300, and a communication module 400.

[0039] The power supply module 200 is used to supply power to the controller 100, the bridge module 300, and the communication module 400.

[0040] The bridging module 300 is connected to the battery collector 1.

[0041] The controller 100 is configured to obtain the battery sub-pack status information provided by the battery collector 1 through the bridging module 300.

[0042] The controller 100 is also configured to upload battery subpack status information and offline test information to the server 2 via the communication module 400.

[0043] Offline testing information includes test information generated when battery subpacks undergo offline testing.

[0044] For example, in this solution, the battery sub-pack monitoring device is used to monitor one or more battery sub-packs when each battery sub-pack is stored independently in a battery warehouse before it is assembled into a battery module.

[0045] Specifically, a battery sub-pack is configured with a battery data acquisition unit 1. The battery sub-pack can be configured with a selected (vehicle-specific) Battery Management System (BMS) to form a power battery system. Depending on the actual design, the power battery system can be applied to power consumption scenarios such as high-capacity commercial vehicles, high-capacity engineering vehicles, energy storage systems, low-capacity commercial vehicles, and low-capacity engineering vehicles.

[0046] For example, in this solution, the battery collector 1 is a collector configured within the battery sub-pack itself, and the battery collector 1 is powered by the battery cells of the battery sub-pack. The specific design of the battery collector 1 is not limited.

[0047] The battery acquisition device 1 may include a control chip (such as a digital signal processor), a sampling chip (such as a voltage sampling chip, a current sampling chip), a sensor (such as a temperature sensor), and a memory (such as Flash, RAM).

[0048] The main function of battery data acquisition device 1 is to collect data from battery sub-packs. For example, battery data acquisition device 1 can collect parameters such as voltage, current, and temperature of battery sub-packs, and collect information such as capacity, remaining charge, and internal resistance of battery sub-packs.

[0049] For example, in this solution, the bridging module 300 is connected to the battery collector 1. The bridging module 1 is mainly used to realize signal conversion and adaptation between the controller 100 and the battery collector 1.

[0050] Since the controller 100 and the battery collector 1 may use different signal standards or communication protocols, a bridging module 300 is used to convert the signal format supported by the battery collector 1 to the signal format supported by the controller, so as to ensure that the two can communicate correctly.

[0051] For example, the bridging module 300 can convert signals of a specified protocol in the daisy chain into CAN (protocol) signals or SPI (protocol) signals, so that controllers 100 using different protocols can obtain signals generated by the battery acquisition unit 1.

[0052] In this solution, the bridging module 300 may include a protocol conversion chip, which can be used to convert between different communication protocols, depending on the actual needs.

[0053] Meanwhile, the bridging module 300 can also be configured with a power interface, input / output interface, and bus interface. The power interface can be used to connect the working power supply of the bridging module 300, the input / output interface can be used for signal input and output, and the bus interface can be used for the bridging module 300 to connect to a specified type of bus. The controller 100 can be configured to connect to the input / output interface or bus interface of the bridging module 300 through specified function pins, thereby realizing communication between the two.

[0054] For example, in this solution, the battery subpack status information may include voltage, current, internal resistance, temperature, etc.

[0055] Among them, voltage acquisition data can be used to determine whether there are problems such as over-discharge, battery aging or internal short circuit in the battery sub-pack; current acquisition data can be used to determine whether there is internal leakage or other faults in the battery sub-pack; internal resistance acquisition data can be used to determine the degree of aging and potential faults in the battery sub-pack; and temperature data can be used to determine whether there are safety issues such as thermal runaway in the battery sub-pack.

[0056] For example, in this solution, the offline test information is the relevant information generated when the battery sub-pack is offline tested. The specific content of the offline test is not limited. For example, the offline test may include voltage test, internal resistance test, capacity test, overcharge protection test, over-discharge protection test, short circuit protection test, high and low temperature performance test, etc.

[0057] Offline test information may specifically include battery sub-pack data (voltage, current, temperature, etc.), battery sub-pack protection parameters (overvoltage protection value, undervoltage protection value, overcurrent protection value, overtemperature protection value, etc.), fault codes, configuration parameters (communication protocol type, communication baud rate, physical address encoding, communication bus identifier), etc.

[0058] For example, in this solution, the battery collector 1 is powered by the battery cells in the battery sub-pack, so that the battery collector 1 (including the battery collector-related circuits and components) can maintain basic functions. The power supply connection method between the battery cells and the battery collector 1 is not limited. For example, the battery cells can be configured to be connected to the battery collector 1 through a power supply circuit.

[0059] For example, in this solution, the connection method between the bridging module 300 and the battery collector 1 is not limited. Depending on the usage requirements, a battery sub-pack monitoring device can monitor the status of one or more battery sub-packs. Correspondingly, the bridging module 300 can be connected to one or more battery collectors 1.

[0060] Depending on the communication interface type and the number of battery collectors 1, the bridging module 300 can be configured to form a specified topology (such as daisy chain topology, star topology, etc.) with one or more battery collectors 1, thereby enabling communication interaction.

[0061] For example, in this solution, the communication module 400 is electrically connected to the controller 100. The communication module 400 can communicate with the server 2 wirelessly. According to design requirements, the communication module 400 can be a WIFI module or a 2G / 3G / 4G / 5G communication module, etc.

[0062] This embodiment proposes a battery sub-pack monitoring device, which includes a bridging module for communicating with a battery data collector configured in the battery sub-pack. The bridging module can obtain independently stored status monitoring data of the battery sub-pack through the battery data collector, thereby enabling status monitoring of the battery sub-pack even when the battery sub-pack is not configured with a battery manager.

[0063] The battery sub-pack monitoring device is also equipped with a communication module, which can be used to upload battery sub-pack status information and offline test information to the server. Based on the server, it can help maintenance personnel to remotely monitor the battery sub-pack. In addition, the server can also analyze the battery sub-pack status information, thereby providing data support for the maintenance and optimization of the battery sub-pack.

[0064] Based on any of the aforementioned schemes, in one possible implementation, the controller is configured with a reverse wake-up terminal.

[0065] The reverse wake-up terminal is connected to the bridging module. The controller is configured to receive the reverse wake-up signal sent by the battery collector through the reverse wake-up terminal. The reverse wake-up information is used by the battery collector to reverse wake up the controller.

[0066] For example, in this solution, the controller can be a microcontroller chip, and the controller is configured to include multiple general purpose input / output (GPIO) pins, wherein one GPIO pin is configured as a reverse wake-up terminal to receive a reverse wake-up signal sent by the battery collector.

[0067] For example, in this solution, the bridging module may include a level conversion circuit, which is used to convert the reverse wake-up signal sent by the battery collector into a level signal that the controller can acquire.

[0068] For example, in this solution, when monitoring the battery sub-pack, the controller can be configured to include a sleep mode, in which the controller is configured to pause reading the battery sub-pack status information.

[0069] When a battery sub-pack malfunctions (e.g., undervoltage, overheating), the battery data acquisition unit detects the abnormality and generates a reverse wake-up signal. This signal is transmitted to the reverse wake-up terminal of the controller via the bridging module. Upon receiving the reverse wake-up signal, the controller immediately exits sleep mode and acquires the battery sub-pack status information in real time.

[0070] Based on any of the aforementioned solutions, in one possible implementation, the controller is also configured with a communication terminal.

[0071] The communication terminal is connected to the bridging module, and the controller is configured to obtain the battery sub-pack status information sent by the bridging module through the communication terminal.

[0072] For example, in this solution, the communication end may include one or more (hardware) communication interfaces configured by the controller. The types of different communication interfaces may be the same or different (for example, the controller may be configured with several GPIO interfaces, several SPI interfaces, and several CAN interfaces, etc.). One communication interface may be configured for data communication with the battery acquisition unit through the bridging module.

[0073] For example, in this solution, when monitoring the battery sub-pack, the controller can be configured to periodically read the battery sub-pack status information, and the battery sub-pack status information (after passing through the bridging module) is transmitted to the controller through the communication terminal (the specified communication interface).

[0074] Based on any of the aforementioned solutions, in one possible implementation, if the battery acquisition device does not have non-volatile storage capability, the communication terminal is also used to connect to the offline test battery manager.

[0075] The controller is also configured to receive offline test information sent by the offline test battery manager via a communication terminal.

[0076] The controller is also configured to store offline test information.

[0077] For example, in this solution, the selection of the battery collector can determine whether the battery collector has non-volatile storage capability. When the battery collector does not have non-volatile storage capability, the battery sub-pack monitoring device is connected to the battery test cabinet and the offline test battery manager when performing offline testing on the battery sub-pack. The battery sub-pack monitoring device receives the offline test information output by the offline test battery manager or the battery test cabinet.

[0078] For example, in this solution, the offline test battery manager can be a BMS, which is configured to collect battery sub-pack status data (such as voltage, current, temperature, etc.) during offline testing, and to evaluate the health status of the battery sub-pack (such as determining whether there is capacity decay, consistency issues, etc.).

[0079] The offline test battery manager is also used to interact with the battery test cabinet, uploading the status information of the battery sub-packs to the test cabinet in real time, and receiving control commands sent by the test cabinet, thereby controlling the test process.

[0080] For example, in this solution, the battery testing cabinet is mainly used to provide a testing environment that can simulate the working environment of the battery sub-pack under different application scenarios, such as different temperature, humidity, vibration and other conditions, so as to more comprehensively test the performance of the battery under various actual use conditions.

[0081] Specifically, the battery testing cabinet can uniformly control and manage various tests of battery sub-packs (such as charge-discharge cycle tests, capacity tests, internal resistance tests, etc.) according to preset test plans and procedures;

[0082] Collect battery sub-packet status data uploaded from various offline test battery managers, centralize the management of scattered data, and facilitate overall data analysis and evaluation.

[0083] For example, in this solution, the battery sub-pack monitoring device can be configured to connect to the offline test battery manager and the battery test cabinet respectively through different communication interfaces in the communication terminal, and receive the offline test information output by the offline test battery manager or the battery test cabinet through the communication interface.

[0084] There are no restrictions on the interface type used when connecting the battery subpack monitoring device with the offline test battery manager and the battery test cabinet. For example, the communication connection between the three can be achieved based on CAN bus and CAN interface.

[0085] For example, in this solution, when battery sub-packs are stored independently in a warehouse and a battery sub-pack monitoring device is used to monitor the battery sub-packs, the battery sub-pack monitoring device, which records the offline test information of the corresponding battery sub-packs, needs to be connected to the corresponding battery sub-packs to realize the monitoring process.

[0086] Based on any of the aforementioned solutions, in one possible implementation, if the battery collector has non-volatile storage capability, the controller is further configured as follows:

[0087] The offline test information is obtained from the battery collector (forwarded by the bridging module) through a designated communication interface in the communication terminal.

[0088] For example, in this solution, when the battery collector has non-volatile storage capability, when performing offline testing on the battery sub-pack, the battery test cabinet and the offline test battery manager can send the offline test information to the battery collector, and each battery collector stores the offline test information of the corresponding battery sub-pack.

[0089] Figure 2 This is a structural block diagram of another battery pack monitoring device in the embodiment, for reference. Figure 2 In one possible implementation, the bridging module 300 further includes a first communication interface 301 and a second communication interface 302.

[0090] The communication terminal 102 is connected to the first communication interface 301, the first communication interface 301 is connected to the second communication interface 302 through the first communication line, and the second communication interface 302 is connected to the bridging module 300.

[0091] The first communication interface 301, the second communication interface 302, and the first communication line are used for communication between the controller 100 and the bridging module 300 based on the differential communication protocol.

[0092] In this solution, the bridging module 300 is connected to the reverse wake-up terminal 101 of the controller 100 via a reverse wake-up line.

[0093] For example, in this solution, when the battery pack monitoring device is far from the battery pack and there are many battery packs, the bridging module 300 can be placed in the area where the battery pack is located. The bridging module 300 is configured to communicate with the communication terminal of the controller 100 through the first communication interface 301 and the second communication interface 302. For instance, the bridging module 300 and the second communication interface 302 can be designed inside the battery pack, and the first communication interface 301 can be designed on the control board where the controller 100 is located. The first communication interface 301 is designed to be connected to the second communication interface 302 through the first communication line. Based on this, the long-distance communication requirements between the battery pack monitoring device and the battery pack can be guaranteed.

[0094] For example, in this solution, the battery data acquisition unit 1 may include a front-end sampling chip, which may be an MC33775A chip. This chip has non-volatile storage capability, which can ensure that data is not lost in the event of power failure, etc. The front-end sampling chip is configured to be directly powered by the battery sub-pack to ensure its continuous and stable operation when the battery sub-pack is working.

[0095] For example, in this solution, the bridging module 300 can use a bridging chip, which can be an MC33665A. The bridging chip is configured to be powered by the power module 200. The bridging chip is designed at the battery acquisition unit and is mainly responsible for signal conversion and communication expansion. It organizes and forwards the data collected by the front-end sampling chip, so that the controller 100 can communicate with the battery acquisition unit through the CAN bus.

[0096] For example, in this solution, the first communication interface 301 and the second communication interface 302 can specifically adopt CAN transceivers, the first communication line is a CAN bus, and the controller 100 and the bridging module 300 communicate based on the CAN communication protocol.

[0097] The CAN transceiver can use the TJA1043 signal. The CAN transceiver can convert digital signals into differential signals suitable for CAN bus transmission, ensuring reliable data transmission on the CAN bus.

[0098] For example, in this solution, the front-end sampling chip and the bridging chip are configured to be connected via a daisy chain. Any front-end sampling chip can be configured to wake up the bridging chip via the daisy chain. The bridging chip can be configured to wake up the controller 100 via the GPIO port, so that the battery sub-pack monitoring device can respond to and handle abnormal situations of the battery sub-pack in a timely manner.

[0099] For example, in this solution, if the configuration controller receives offline test information output by the offline test battery manager or battery test cabinet through the first CAN interface, and the first communication interface 301 adopts a CAN transceiver, then the configuration controller is connected to the first communication interface 301 through the second CAN interface.

[0100] Figure 3 This is a structural block diagram of another battery pack monitoring device in the embodiments, see reference. Figure 3 In one possible implementation, the communication terminal is connected to the bridging module 300 via a second communication line; the second communication line is used for communication between the controller 100 and the bridging module 300 based on a serial communication protocol.

[0101] For example, in this solution, when the battery pack monitoring device is close to the battery pack and the number of battery packs is small, the bridging module 300 is set on the control board of the controller 100. The bridging module 300 is connected to the reverse wake-up terminal 101 through the reverse wake-up line and communicates with the communication terminal 102 of the controller 100 through the second communication line. This can reduce the number of components used and lower the cost.

[0102] For example, in this solution, the bridging module 300 can use a bridging chip, which can be an MC33665A. The bridging chip is powered by the power module 200 and is responsible for signal conversion and communication expansion. The bridging chip is directly connected to the communication terminal of the controller 100 through a second communication line, which can specifically be an SPI communication line. The controller 100 and the bridging module 300 communicate based on the SPI protocol.

[0103] For example, in this solution, the front-end sampling chip and the bridging chip are configured to be connected via a daisy chain. Any front-end sampling chip can be configured to wake up the bridging chip via the daisy chain. The bridging chip can be configured to wake up the controller 100 via the GPIO port, so that the battery sub-pack monitoring device can respond to and handle abnormal situations of the battery sub-pack in a timely manner.

[0104] Based on any of the aforementioned solutions, in one possible implementation, the power module includes a power supply module and a power management module.

[0105] The power supply module is connected to the power management module, and the power supply module is used to provide power to the power management module.

[0106] The power management module is used to supply power to the controller, bridging module, and communication module.

[0107] For example, in this solution, the power supply module can be a disposable battery or a rechargeable battery.

[0108] For example, in this solution, the power management module can be a power management chip or designed to be composed of power management circuits. The power management circuits may include input protection circuits, voltage conversion circuits, power distribution and control circuits, power monitoring and feedback circuits, etc.

[0109] The input protection circuit is designed to prevent high voltage from damaging subsequent circuits when the output voltage of the power supply module exceeds the set safety threshold, thus ensuring that the input voltage remains stable within a safe range.

[0110] The voltage conversion circuit is designed to convert the output voltage of the power supply module, converting the higher voltage output by the power supply module into a stable lower voltage, or raising the voltage of the power supply module to a suitable level to provide a stable power supply for the corresponding module.

[0111] The power distribution and control circuit design includes multiple power output ports, which supply power to the controller, bridge module, and communication module respectively. Each output port can be configured with an independent power switch. By controlling the on / off state of each power switch, the power supply to some modules can be cut off when the system is in standby or low power consumption state, thereby reducing system energy consumption.

[0112] The power monitoring and feedback circuit is designed to monitor the voltage or current of each output port and determine whether there are faults such as short circuits in the power circuit based on the voltage or current data.

[0113] Based on any of the aforementioned solutions, in one possible implementation, the bridging module is connected to the battery collector via a daisy chain.

[0114] In this solution, the bridging module is configured to be connected to the battery collector via a daisy chain, which can reduce the number and complexity of wiring between the bridging module and the battery collector, thereby reducing system cost and installation difficulty.

[0115] When it is necessary to increase the number of battery collectors, simply add new battery collectors to the daisy chain; no large-scale modifications to the system are required.

[0116] The daisy-chain port uses differential signal transmission, which effectively improves the anti-interference capability of data transmission and ensures the reliability of the system.

[0117] For example, in this solution, the interface type used when the bridging module and the battery collector are connected in a daisy chain is not limited. It can be determined according to the selection of the battery collector. For example, the interface can be a differential signal interface (e.g., CAN interface), a serial interface (e.g., SPI interface), etc.

[0118] Figure 4 This is a structural block diagram of another battery pack monitoring device in the embodiments. Figure 5 This is a flowchart of the battery sub-pack outbound process in the embodiment, for reference. Figure 4 and Figure 5 Based on any of the aforementioned solutions, in one possible implementation, the battery pack monitoring device includes:

[0119] The system includes a controller 100, a power supply module 201, a power management module 202, a bridging module 300, and a communication module 400.

[0120] The power supply module 201 is connected to the power management module 202, and the power supply module 201 is used to provide power to the power management module 202.

[0121] The power management module 202 is used to supply power to the controller 100, the bridging module 300, and the communication module 400.

[0122] The bridging module 300 is connected to the battery collector 1 via a CAN bus or daisy chain. The bridging module 300 is connected to the communication terminal 102 of the controller 100 via a communication line, and to the reverse wake-up terminal 101 of the controller 100 via a reverse wake-up line.

[0123] The controller 100 is configured to obtain the battery sub-pack status information provided by the battery collector 1 through the bridging module 300.

[0124] The controller 100 is also configured to upload battery subpack status information and offline test information to the server 2 via the communication module 400.

[0125] For example, in this solution, the power management module 202 is also used to provide a stable and reliable power supply to the controller 100, the bridging module 300, and the communication module 400, and the power supply module 201 is used to provide power supply. The power supply module 201 can use a disposable battery or a rechargeable battery.

[0126] The controller 100 and the bridging module 300 can be configured to have a sleep mode operation function. When running in sleep mode, the controller 100 and the bridging module 300 stop collecting battery sub-pack status data, which can greatly reduce the power consumption of the power supply module 201 and thus reduce the replacement frequency of the power supply module 201.

[0127] Based on the reverse wake-up line, when the battery collector detects an abnormality in the battery sub-pack, it can reverse wake up the bridging module 300, and then the bridging module 300 can reverse wake up the controller 100, thereby exiting the sleep mode.

[0128] The bridging module 300 is used to collect battery sub-pack status information. The communication protocol supported by the bridging module 300 is determined based on the model of the front-end sampling chip configured in the battery collector 1.

[0129] The communication module 400 communicates with the server 2 wirelessly. The configuration control 100 has a timed wake-up function, which can periodically wake up and upload battery sub-pack status information. The configuration server 2 is used for collecting, processing, and alarming battery sub-pack status information. In addition, the server 2 can be configured to remotely wake up the battery sub-pack monitoring device.

[0130] For example, in this solution, the usage of the battery sub-pack monitoring device and the battery sub-pack outbound process may include:

[0131] After the battery subpack is produced, it is tested off the production line. Before the off-line test, the off-line test environment is prepared by connecting the battery subpack, battery test cabinet, off-line test battery manager, etc.

[0132] If the battery collector has non-volatile storage capability, configure the offline test battery manager to write the offline test information into the battery collector.

[0133] If the battery acquisition unit does not have non-volatile storage capability, the offline test battery manager will be configured to write the offline test information into the controller in the battery sub-pack monitoring device.

[0134] After setting up the offline testing environment, execute the battery subpacket offline testing process.

[0135] Transfer the battery subpacks that have completed offline testing to the battery warehouse.

[0136] Install the battery sub-pack monitoring device onto the battery sub-pack. If the battery data acquisition unit does not have non-volatile storage capability, then a battery sub-pack monitoring device storing the lower limit test information of the corresponding battery sub-pack needs to be installed.

[0137] The status information of the battery sub-pack is monitored by the battery sub-pack monitoring device. If the controller or server detects an abnormal battery sub-pack, the location of the battery sub-pack is located based on the offline test information so as to execute the preset abnormal handling measures.

[0138] When a battery subpack needs to be shipped out, the server can determine whether the battery subpack meets the shipping criteria. If it meets the criteria, it will be shipped out. Otherwise, a shipping test will be performed on the battery subpack that does not meet the criteria. If the test is passed, it will be shipped out.

[0139] Example 2

[0140] This embodiment proposes a server that communicates with any of the battery pack monitoring devices described in Embodiment 1 via a communication module.

[0141] The server is configured to receive battery subpacket status information and offline test information uploaded by the battery subpacket monitoring device, and to locate abnormal battery subpackets based on the battery subpacket status information and offline test information.

[0142] For example, in this solution, the method for locating abnormal battery sub-packets by the server is not limited, and can be freely set according to requirements.

[0143] In this embodiment, the implementation method and beneficial effects of the battery pack monitoring device are the same as those described in Embodiment 1, and the specific details will not be repeated.

[0144] In this solution, the configuration server locates abnormal battery sub-packets based on their status information and offline test information, allowing users to monitor the status of battery sub-packets in real time via the cloud. Furthermore, if a battery sub-packet needs to be shipped out, the server can determine whether it meets the shipping criteria. If it does, it can be shipped directly; otherwise, further testing is conducted to determine whether it can be shipped. This avoids performing shipping tests on all battery sub-packets that need to be shipped, significantly improving the shipping efficiency of battery sub-packets.

[0145] Based on any of the aforementioned solutions, in one possible implementation, the server is further configured to remotely wake up the battery subpack monitoring device via a communication module.

[0146] Example 3

[0147] This embodiment proposes a battery subpack monitoring system, which includes a battery subpack monitoring device and a server.

[0148] In this solution, the battery sub-pack monitoring device can be any of the battery sub-pack monitoring devices described in Embodiment 1, and the battery sub-pack monitoring device and the server are configured to communicate.

[0149] In this solution, when it is necessary to perform offline testing on the battery sub-pack, the operator triggers the offline testing process of the battery sub-pack through specific testing equipment or system.

[0150] During the testing of the battery subpack, the relevant testing equipment generates offline test information, such as charge / discharge test data and internal resistance test data. This test information is stored by the controller of the battery subpack monitoring device or the battery data acquisition unit of the battery subpack.

[0151] In this solution, the battery pack monitoring system may operate in the following ways:

[0152] The battery data acquisition unit of the battery subpack collects the status information of the battery subpack in real time according to a preset sampling frequency (e.g., once per second).

[0153] The controller of the battery sub-pack monitoring device periodically receives the status information of the battery sub-pack sent by the battery data collector through the bridging module.

[0154] The controller of the battery sub-pack monitoring device packages the acquired battery sub-pack status information and offline test information into a package and encapsulates it according to a preset data format.

[0155] The controller uploads the encapsulated data to the server via the communication module. The communication module automatically selects the appropriate communication method for data transmission based on network conditions.

[0156] After receiving the data uploaded by the battery sub-packet monitoring device, the server first unpacks and verifies the data.

[0157] The server analyzes and processes the battery sub-packet status information and offline test information according to preset algorithms and rules to determine whether there are any anomalies in the battery sub-packets. Simultaneously, it further evaluates the performance and health status of the battery sub-packets by combining the offline test information.

[0158] If the server detects an anomaly in a battery sub-packet during data analysis, it will accurately locate the abnormal battery sub-packet based on its identification information (such as number, location, etc.).

[0159] The server sends alarm information to relevant operators or maintenance personnel through a preset alarm mechanism, such as SMS notifications, email notifications, or system pop-up prompts. The alarm information will include detailed information such as the specific location of the abnormal battery sub-packet and the type of abnormality, so that operators can handle it in a timely manner.

[0160] In this embodiment, the implementation method and beneficial effects of the battery pack monitoring device are the same as those described in Embodiment 1, and the specific details will not be repeated.

[0161] Note that the above description is merely a preferred embodiment of the present invention and the technical principles employed. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions can be made without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in detail through the above embodiments, the present invention is not limited to the above embodiments, and may include many other equivalent embodiments without departing from the concept of the present invention. The scope of the present invention is determined by the scope of the appended claims.

Claims

1. A battery pack monitoring device, characterized in that, include: Controller, power supply module, bridging module, and communication module; The power module is used to supply power to the controller, the bridge module, and the communication module; The bridging module is connected to the battery collector; The controller is configured to obtain battery sub-pack status information provided by the battery collector through the bridging module; The controller is also configured to upload the battery subpack status information and offline test information to the server via the communication module; The offline test information includes the test information generated when the battery subpack undergoes offline testing.

2. The battery pack monitoring device as described in claim 1, characterized in that, The controller is equipped with a reverse wake-up terminal; The reverse wake-up terminal is connected to the bridging module, and the controller is configured to receive a reverse wake-up signal sent by the battery collector through the reverse wake-up terminal. The reverse wake-up signal is used by the battery collector to reverse wake up the controller.

3. The battery pack monitoring device as described in claim 1, characterized in that, The controller is also equipped with a communication terminal; The communication terminal is connected to the bridging module, and the controller is configured to obtain the battery subpack status information sent by the bridging module through the communication terminal.

4. The battery pack monitoring device as described in claim 3, characterized in that, If the battery acquisition device does not have non-volatile storage capability, the communication terminal is also used to connect to the offline test battery manager; The controller is also configured to receive the offline test information sent by the offline test battery manager through the communication terminal; The controller is also configured to store the offline test information.

5. The battery pack monitoring device as described in claim 3, characterized in that, If the battery collector has non-volatile storage capability, the controller is further configured as follows: The offline test information stored by the battery collector is obtained from the bridging module through the communication terminal.

6. The battery pack monitoring device as described in claim 3, characterized in that, The bridging module is also equipped with a first communication interface and a second communication interface; The communication terminal is connected to the first communication interface, the first communication interface is connected to the second communication interface via a first communication line, and the second communication interface is connected to the bridging module. The first communication interface, the second communication interface, and the first communication line are used for communication between the controller and the bridging module based on a differential communication protocol.

7. The battery pack monitoring device as described in claim 3, characterized in that, The communication terminal is connected to the bridging module via a second communication line; The second communication line is used for communication between the controller and the bridging module based on a serial communication protocol.

8. The battery pack monitoring device as described in claim 1, characterized in that, The power module includes a power supply module and a power management module; The power supply module is connected to the power management module, and the power supply module is used to provide power to the power management module; The power management module is used to supply power to the controller, the bridging module, and the communication module.

9. The battery pack monitoring device as described in claim 1, characterized in that, The bridging module is connected to the battery collector via a daisy chain.

10. A server, characterized in that, The battery subpack monitoring device according to any one of claims 1 to 9 is connected via a communication module; The server is configured to receive battery subpacket status information and offline test information uploaded by the battery subpacket monitoring device, and to locate abnormal battery subpackets based on the battery subpacket status information and offline test information.

Images