A battery management system for a vehicle

Abstract

The application provides a battery management system and a vehicle, and belongs to the technical field of power batteries. The battery management system comprises a main controller and a plurality of battery subsystems. Each battery subsystem is provided with a slave controller. The slave controller in each battery subsystem is connected with the main controller. The main controller is configured to issue a detection instruction to the plurality of slave controllers in response to a wake-up instruction. The detection instruction comprises a position identification instruction and a plurality of state detection instructions. The slave controller is configured to obtain electrical position information of the battery subsystem in which the slave controller is located in response to the position identification instruction, and send the electrical position information to the main controller. In response to each state detection instruction, the slave controller collects corresponding battery state parameters in the battery subsystem in which the slave controller is located and sends the battery state parameters to the main controller. The main controller is further configured to determine whether a fault exists in the battery subsystem based on the electrical position information and the battery state parameters.

Description

Technical Field

[0001] This invention belongs to the field of power battery technology, specifically relating to a battery management system and a vehicle. Background Technology

[0002] Power battery systems typically consist of multiple battery packs connected in series and parallel, with a large number of cells and a complex electrical structure. Current battery management systems have complex architectures, high monitoring complexity, and are difficult to manage, often leading to data asynchrony. Inspection cycles and parameters are fixed and cannot be dynamically adjusted based on health status, making it difficult to detect early faults in a timely manner. Summary of the Invention

[0003] In view of the above problems, embodiments of this application provide a battery management system and a vehicle to overcome or at least partially solve the above problems.

[0004] In a first aspect, this application provides a battery management system, including a main controller and multiple battery subsystems. Each battery subsystem is equipped with a slave controller, and each slave controller in the battery subsystem is connected to the main controller. The main controller is configured to issue detection instructions to the multiple slave controllers in response to a wake-up command. The detection instructions include a location identification instruction and multiple state detection instructions. Each slave controller is configured to, in response to the location identification instruction, acquire electrical location information of the battery subsystem in which the slave controller is located and send the electrical location information to the main controller, and in response to each of the state detection instructions, collect battery state parameters corresponding to the battery subsystem in which the slave controller is located and send them to the main controller. The main controller is further configured to determine whether a fault exists in the battery subsystem based on the electrical location information and the battery state parameters.

[0005] In some embodiments, the electrical location information includes a slave controller number, and the master controller is further configured to compare the slave controller number included in the electrical location information with a pre-stored slave controller number; if they match, the master controller determines that the electrical location of the slave controller is normal and sends a successful identification command to the slave controller; if they do not match, the master controller determines that the electrical location of the slave controller is abnormal and sends an electrical location mismatch fault signal to the vehicle controller to display a fault prompt message to the user; and in response to a user-triggered re-identification command for a slave controller with an abnormal electrical location, the master controller sends the location identification command to the slave controller with the abnormal electrical location, so that the slave controller reacquires new electrical location information, and compares the slave controller number in the new electrical location information sent by the slave controller with the pre-stored slave controller number; if they match, the master controller sends a re-matching success signal to the vehicle controller to stop displaying the fault prompt message to the user.

[0006] In some embodiments, the slave controller is further configured to send the wake-up command to the master controller when an abnormal battery state of the battery subsystem is detected; wherein the abnormal battery state includes abnormal cell voltage, open circuit of cell sampling line, and abnormal internal air pressure of battery system.

[0007] In some embodiments, the multiple state detection commands include a cell state detection command; the slave controller is configured to, in response to the cell state detection command, collect the cell voltage, cell quantity, and sampling line status of the battery subsystem, and send them to the master controller; the master controller is further configured to determine whether the cell voltage is within a preset voltage threshold range, whether the cell quantity is consistent with a preset cell quantity, and whether there is an open circuit fault in the sampling line based on the status of the sampling line; if the cell voltage is not within the preset voltage threshold range, or the cell quantity is inconsistent with the preset cell quantity, or the sampling line has an open circuit fault, then the battery subsystem is determined to have a fault, and a thermal runaway fault signal is sent to the vehicle controller to prevent the vehicle from being powered on.

[0008] In some embodiments, the multiple state detection commands include a pressure detection command; the slave controller is further configured to, in response to the pressure detection command, activate a pressure sensor to detect the pressure within the battery subsystem, determine whether the pressure is abnormal, and send a pressure abnormality signal to the master controller if an abnormality is detected; the master controller is further configured to, in response to the pressure abnormality signal, send a thermal runaway fault signal to the vehicle controller to prevent the vehicle from being powered on.

[0009] In some embodiments, the slave controllers of two adjacent battery subsystems are connected in series via an anti-theft detection line, and the multiple status detection commands include an anti-theft detection command; the slave controller is also configured to perform battery anti-theft inspection in response to the anti-theft detection command and send an anti-theft line signal to the master controller; the master controller is also configured to send a battery system loss fault signal to the vehicle controller if it is determined based on the anti-theft line signal that at least one battery subsystem cannot be identified.

[0010] In some embodiments, the status detection command includes a high-voltage interlock detection command; the slave controller is further configured to send a loopback high-voltage interlock signal to the master controller in response to the high-voltage interlock detection command, and the master controller is further configured to determine whether there is an abnormality in the slave controller based on the high-voltage interlock signal, and if an abnormality is detected, send a high-voltage interlock fault to the vehicle controller and limit the vehicle's driving power.

[0011] In some embodiments, the main controller is further configured to periodically generate a wake-up command, switch from a sleep state to a working state in response to the wake-up command, and supply power to the slave controller.

[0012] In some embodiments, the master controller is further configured to output a sleep command to the slave controller if it determines that there is no fault in the battery subsystem; the slave controller is further configured to disable the wake-up trigger function and send a sleep preparation completion signal back to the master controller in response to the sleep command; the master controller is further configured to stop supplying power to the slave controller in response to the preparation completion signal.

[0013] In a second aspect of this application, a vehicle is provided, the vehicle including the battery management system described in the first aspect of this application.

[0014] This application provides a battery management system, which includes a main controller and multiple battery subsystems. The main controller is configured to issue detection commands to multiple slave controllers in response to a wake-up command, enabling the slave controllers to initiate responses at the same time reference and allowing multiple battery subsystems to be detected simultaneously. The detection commands include location identification commands and various state detection commands. In response to the location identification command, the slave controllers actively acquire and report the electrical location information of their respective battery subsystems. This allows the main controller to accurately correlate the state parameters of each battery subsystem with the vehicle's topology, solving the problem of difficult fault location in the discrete distribution of multiple battery packs. The slave controllers can respond to various state detection commands, collecting corresponding battery state parameters and reporting them to the main controller. Finally, the main controller performs a comprehensive fault determination based on the electrical location information and multi-source battery state parameters to determine whether a fault exists in the battery subsystem, enabling timely detection of early faults. Attached Figure Description

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

[0016] Figure 1 This is a schematic diagram of a battery management system provided in an embodiment of this application; Figure 2 This is a flowchart illustrating the execution of a position detection instruction according to an embodiment of this application; Figure 3 This is a schematic diagram of a wake-up trigger circuit provided in an embodiment of this application; Figure 4This is a schematic diagram of a process for performing cell status detection according to an embodiment of this application; Figure 5 This is a schematic flowchart illustrating the execution of a barometric pressure detection command according to an embodiment of this application; Figure 6 This is a schematic diagram of a high-voltage interlock circuit provided in an embodiment of this application. Detailed Implementation

[0017] Exemplary embodiments of this application will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of this application are shown in the drawings, it should be understood that this application may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided to enable a more thorough understanding of this application and to fully convey the scope of this application to those skilled in the art.

[0018] Figure 1 This is a schematic diagram of a battery management system provided in an embodiment of this application, such as... Figure 1 As shown, the battery management system includes a main controller and multiple battery subsystems. Each battery subsystem is equipped with a slave controller, and each slave controller in the battery subsystem is connected to the main controller. This enables a distributed management architecture in multi-battery pack scenarios, and the status of each battery subsystem can be independently collected and monitored.

[0019] The main controller is configured to issue detection commands to multiple slave controllers in response to a wake-up command. These detection commands include location identification commands and various status detection commands. The slave controllers are configured to, in response to the location identification command, acquire the electrical location information of the battery subsystem in which the slave controller resides and send the electrical location information to the main controller. They are also configured to, in response to each status detection command, collect the corresponding battery status parameters in the battery subsystem in which the slave controller resides and send them to the main controller. The main controller is further configured to determine whether a fault exists in the battery subsystem based on the electrical location information and the battery status parameters.

[0020] In this embodiment, the wake-up command can come from the vehicle controller, be generated periodically by the main controller, or come from the slave controller. The main controller responds to the wake-up command by switching from a sleep state to an operating state, which avoids the energy consumption problem caused by the main controller running for extended periods, providing a prerequisite for low-power sleep management of the battery management system.

[0021] The master controller can send detection commands to multiple slave controllers via the CAN bus. These commands include position identification commands and various status detection commands. A unified triggering of multi-dimensional detection can be achieved through the same command set, ensuring that each slave controller synchronously executes different types of detection tasks, thus improving inspection efficiency. The slave controller is configured to respond to the position identification command and automatically identify the electrical position information of the battery subsystem to which the slave controller is located. The electrical position information can be the corresponding number of each battery subsystem. The master controller then sends the electrical position information to the master controller so that it can determine whether there is an assembly mismatch problem in each battery subsystem based on the electrical position information, providing a location basis for subsequent fault location. The slave controllers respond to various state detection commands and collect corresponding battery state parameters, enabling each slave controller to collect multiple battery state parameters as needed, such as cell voltage, loop current, sampling line status, and system pressure. This achieves multi-dimensional data acquisition at the slave controller level. The slave controllers then send the battery state parameters and electrical location information to the master controller. The master controller can make a comprehensive judgment based on the location information and state parameters. It can identify various battery state faults, such as location mismatch faults, cell overvoltage or undervoltage, sampling line open circuit, abnormal pressure, anti-theft loss, and high-voltage interlock open circuit. If a fault is detected in the battery subsystem, the master controller will send a fault signal to the vehicle controller. If no fault is detected in the battery subsystem, the master controller will enter a sleep state and stop supplying power to the slave controllers.

[0022] In some embodiments, the electrical location information includes a slave controller number. The master controller is further configured to compare the slave controller number contained in the electrical location information with a pre-stored slave controller number; if they match, the master controller determines that the electrical location of the slave controller is normal and sends a successful identification command to the slave controller; if they do not match, the master controller determines that the electrical location of the slave controller is abnormal and sends an electrical location mismatch fault signal to the vehicle controller to display a fault prompt message to the user; and in response to a user-triggered re-identification command for a slave controller with an abnormal electrical location, the master controller sends a location identification command to the slave controller with the abnormal electrical location, so that the slave controller re-acquires new electrical location information and compares the slave controller number in the new electrical location information sent by the slave controller with a pre-stored slave controller number. If they match, the master controller sends a re-matching success signal to the vehicle controller to stop displaying the fault prompt message to the user.

[0023] In this embodiment, the main controller's storage module has been pre-written with the part number corresponding to each slave controller and its electrical location information to be installed.

[0024] A position detection circuit can be set in the controller. This position detection circuit is a voltage divider resistor identification circuit, where multiple voltage divider resistors are connected in series between the power supply terminal and the reference ground, forming a voltage divider network. Each slave controller is connected at a node between two adjacent resistors. The master controller supplies power to the voltage divider network, and the slave controller acquires the voltage value to ground at the node through an ADC. Based on the voltage value, it calculates its own ranking position in the series network, thereby determining the electrical position of its battery subsystem and obtaining the slave controller number (part number), such as Z100066881. In this embodiment, the position detection circuit can consist of voltage divider resistors and a sampling circuit. Specifically, it can be a sampling circuit of models such as LTC6804 or BQ79616-Q1.

[0025] Figure 2 This is a flowchart illustrating the execution of a position detection instruction according to an embodiment of this application, as shown below. Figure 2 As shown. After the slave controller completes electrical position identification in response to the position identification command, it sends the slave controller number to the master controller. The master controller compares the slave controller number with the pre-stored slave controller numbers. If the slave controller number matches the pre-stored slave controller number, the master controller determines that the electrical position of the slave controller is normal and sends an identification success command to the slave controller. If the slave controller number does not match the pre-stored slave controller number, the master controller determines that the electrical position of the slave controller is abnormal and sends an electrical position mismatch fault signal to the vehicle controller to display a fault prompt message to the user.

[0026] When a user triggers a re-identification command for a slave controller with an electrical position malfunction via an instrument cluster or a diagnostic tool by after-sales personnel, the master controller responds to the re-identification command by re-issuing a position identification command to the slave controller with the electrical position malfunction, so that the slave controller can obtain new electrical position information. The slave controller sends the slave controller number from the new electrical position information to the master controller. The master controller compares the new slave controller number with the pre-stored slave controller number again. If they match, the master controller sends a re-matching success signal to the vehicle controller to stop displaying fault prompt information to the user and clear the fault code.

[0027] In some embodiments, the slave controller is further configured to send a wake-up command to the master controller when an abnormal battery state of the battery subsystem is detected; wherein the abnormal battery state includes abnormal cell voltage, open circuit of cell sampling line, and abnormal internal air pressure of battery system.

[0028] In this embodiment, after power-on, the slave controller can monitor the cell voltage, sampling line connection status, and internal air pressure of the battery system in real time even without receiving a detection command. It can continuously perform local monitoring tasks even during the main controller's sleep period. Abnormal events detected by the slave controller can also be transmitted to the main controller, enabling the main controller to switch from sleep state to working state in a timely manner to respond. When the slave controller detects that the cell voltage exceeds the preset threshold range, it triggers reverse wake-up, enabling the main controller to handle cell overvoltage, undervoltage, and other faults in a timely manner to prevent battery damage or thermal runaway. When the air pressure sensor detects that the internal air pressure of the battery system exceeds the preset threshold, it triggers reverse wake-up through the slave controller, enabling the main controller to respond quickly to serious faults such as electrolyte leakage or thermal runaway.

[0029] Figure 3 This is a schematic diagram of a wake-up trigger circuit provided in an embodiment of this application, as shown below. Figure 3 As shown, the controller includes a wake-up trigger circuit, which includes switching transistors Q501 and Q530, and resistors R535 and R536. The control terminal of switching transistor Q501 receives the wake-up trigger signal IN:B-AFE1 generated by the controller when it detects an abnormal battery status. The first terminal of switching transistor Q501 is connected to the power supply terminal +12V-CONST, and the second terminal of switching transistor Q501 is grounded through resistors R535 and R536. The control terminal of switching transistor Q530 is connected to resistors R535 and R536. At the node between resistors R501 and R536, the first terminal of switch Q530 is grounded, and the second terminal of switch Q530 is used to connect to the wake-up pin HSAFE-WAKE of the main controller and send a wake-up signal to the main controller. When the controller detects an abnormal battery status, the wake-up trigger signal IN:B-AFE1 is active, switch Q501 is turned on, and the voltage change at the node between resistors R535 and R536 turns on switch Q530, pulling the level of the wake-up pin HSAFE-WAKE low, thereby waking up the main controller. Figure 3 The wake-up trigger circuit allows the slave controller to send a wake-up signal to the master controller when it detects an abnormal battery status. This achieves reverse wake-up of the master controller by the slave controller without the master controller's involvement.

[0030] Figure 3 The wake-up trigger signal IN:B-AFE1 (active low) → Q501 turns on → +12V-CONST power supply → R535 and R536 divide the voltage → Q530 turns on → HSAFE-WAKE is pulled low → the main controller is woken up.

[0031] In some embodiments, the multiple state detection commands include a cell state detection command; the slave controller is configured to, in response to the cell state detection command, collect the cell voltage, cell quantity, and sampling line status of the battery subsystem, and send them to the master controller; the master controller is further configured to determine whether the cell voltage is within a preset voltage threshold range, whether the cell quantity is consistent with a preset cell quantity, and whether there is an open circuit fault in the sampling line based on the sampling line status; if the cell voltage is not within the preset voltage threshold range, or the cell quantity is inconsistent with the preset cell quantity, or there is an open circuit fault in the sampling line, then it is determined that there is a fault in the battery subsystem, and a thermal runaway fault signal is sent to the vehicle controller to prevent the vehicle from being powered on.

[0032] In this embodiment, the main controller stores the total number of cells that each battery subsystem should contain (e.g., each battery subsystem consists of 12 cells connected in series), which serves as a benchmark value for cell quantity verification. This value is compared with the actual cell quantity reported by the slave controller to determine if there are any issues such as missing cells, detached sampling lines, or abnormal acquisition channels. The main controller's storage module stores preset voltage thresholds and the normal operating range of cell voltages (upper and lower limits, such as 2.8V~4.2V), which serve as a benchmark value for cell voltage verification. This value is compared with the actual cell voltage reported by the slave controller to determine if there are any overvoltage or undervoltage faults in the cells. The master controller sends a cell status detection command to the slave controller, triggering the slave controller to initiate the cell status detection process. This puts the slave controller into cell data acquisition mode, ensuring that all slave controllers execute cell detection tasks synchronously. Responding to the cell status detection command, the slave controller collects data on the cell voltage, cell quantity, and sampling line status of the battery subsystem. The slave controller uses a cell acquisition chip (such as an AFE chip like the LTC6804 or BQ79616) to measure the voltage of each cell, count the total number of cells, and simultaneously detect whether the cell sampling line is open-circuited, achieving multi-dimensional data acquisition of the cell's electrical status. The sampling line is the physical line that transmits the cell voltage signal to the slave controller. If the sampling line is open-circuited, the master controller will not be able to obtain the actual voltage value of the corresponding cell, therefore, its status needs to be detected separately.

[0033] The main controller determines whether the cell voltage is within the preset voltage threshold range. Specifically, it compares the actual voltage of each cell with the preset upper and lower voltage thresholds one by one to determine whether the cell has an overvoltage or undervoltage fault. Overvoltage may lead to thermal runaway, while undervoltage may lead to irreversible damage to the battery; both are serious faults.

[0034] The main controller determines whether the number of battery cells matches the preset number by comparing the actual number of battery cells collected with the preset number stored locally. This helps determine if there are any issues such as missing battery cells, detached sampling lines, or abnormal battery cell acquisition chip channels. If the two numbers do not match, it indicates an abnormality in the battery cell sampling circuit, which could result in some battery cells not being detected, posing a serious safety hazard.

[0035] The main controller determines whether there is an open circuit fault in the sampling line based on its status. Specifically, the slave controller determines whether an open circuit has occurred by injecting a detection signal into the sampling line or monitoring the loop impedance of the sampling line. If the sampling line is open, the main controller will be unable to obtain the true voltage value of the corresponding cell, resulting in the loss of battery cell monitoring. Therefore, an open circuit fault detection is required separately.

[0036] When any of the following abnormal conditions occur: cell voltage exceeding the limit, cell quantity mismatch, or sampling line open circuit, the main controller determines that there is a fault in the battery subsystem, reports the fault information to the vehicle level, and actively prevents the fault from worsening by prohibiting high voltage power supply, thus avoiding vehicle operation or charging under conditions of battery safety hazards and preventing thermal runaway accidents from the root.

[0037] Figure 4 This is a schematic diagram of a process for performing cell status detection according to an embodiment of this application, as shown below. Figure 4 As shown, after the main controller sends the cell status detection command, the following process is executed: The slave controller responds to the cell status detection command by collecting the cell voltage of the battery subsystem. The slave controller sends the collected cell voltage, cell quantity, and sampling line status to the main controller. The main controller determines whether the cell voltage is within the preset voltage threshold range and whether the cell quantity is consistent with the preset cell quantity. Based on the sampling line status, the main controller determines whether there is an open circuit fault in the sampling line. If the cell voltage is within the preset voltage threshold range, the cell quantity is consistent with the preset cell quantity, and there is no open circuit fault in the sampling line, the main controller determines that the battery subsystem is normal and completes the cell status detection.

[0038] In some embodiments, the multiple state detection commands include a pressure detection command; the slave controller is also configured to, in response to the pressure detection command, activate the pressure sensor to detect the pressure in the battery subsystem and determine whether the pressure is abnormal, and send a pressure abnormality signal to the master controller if an abnormality is determined; the master controller is also configured to, in response to the pressure abnormality signal, send a thermal runaway fault signal to the vehicle controller to prevent the vehicle from being powered on.

[0039] In this embodiment, Figure 5 This is a flowchart illustrating the execution of a barometric pressure detection command according to an embodiment of this application, as shown below. Figure 5As shown, the main controller sends a pressure detection command → the slave controller responds to the pressure detection command → activates the pressure sensor to detect the pressure in the battery subsystem, and the slave controller determines whether the pressure is abnormal.

[0040] 1: If the air pressure is normal → the controller reports the normal status to the main controller → the air pressure detection command is completed.

[0041] 2: If the air pressure is abnormal → the controller sends an abnormal air pressure signal to the main controller → the main controller responds to the abnormal air pressure signal and sends a thermal runaway fault signal to the vehicle controller, prohibiting the vehicle from being powered on.

[0042] The controller responds to the air pressure detection command, initiating air pressure detection to avoid increased power consumption and lifespan reduction caused by prolonged continuous operation of the sensor. The air pressure sensor is activated to detect the air pressure within the battery subsystem, sampling the internal air pressure in real time to obtain key physical parameters of the battery system's internal environment. The controller determines whether the air pressure is abnormal by directly comparing the air pressure value with a preset threshold, eliminating the need to report raw data to the master controller for remote judgment, thus shortening the detection and identification time. This also reduces the amount of communication data between the master and slave, lowering the bus load. After completing the judgment locally, the slave controller only reports the judgment result (abnormal signal) to the master controller, allowing the master controller to respond directly without further threshold judgment, saving processing time. Upon receiving an abnormal air pressure signal, the master controller reports the abnormal air pressure event to the vehicle controller, enabling the vehicle controller to obtain fault information and take appropriate measures. In cases where there is a risk of thermal runaway in the battery system, the controller actively blocks vehicle operation or charging by prohibiting high-voltage power supply, preventing further deterioration of the fault and ensuring the safety of personnel and the vehicle.

[0043] In some embodiments, the slave controllers of two adjacent battery subsystems are connected in series via an anti-theft detection line, and various status detection commands include an anti-theft detection command; the slave controller is also configured to perform battery anti-theft inspection in response to the anti-theft detection command and send an anti-theft line signal to the master controller; the master controller is also configured to send a battery system loss fault signal to the vehicle controller if it is determined based on the anti-theft line signal that at least one battery subsystem cannot be identified.

[0044] In this embodiment, the slave controllers are connected in series via an anti-theft detection line to form a complete detection loop. This series connection ensures that if any battery subsystem is removed or disconnected, the entire loop is broken. The main controller can determine whether a battery subsystem is missing by checking the continuity of the detection loop. Responding to the anti-theft detection command, the slave controllers perform battery anti-theft inspections. They check the continuity of the anti-theft detection line to determine if the anti-theft loop is complete and if there are any abnormal disconnections. The slave controllers report the detected anti-theft line status information to the main controller. The main controller, based on the reported anti-theft line signal, determines whether a battery subsystem is missing or has been removed. When the anti-theft line loop is complete, the main controller can correctly identify all slave controllers. When a slave controller is removed, the anti-theft line is broken, and the main controller cannot receive the corresponding anti-theft line signal, thus determining that a battery system is missing. The main controller then reports the battery system loss event to the vehicle controller, enabling the vehicle to obtain fault information and take appropriate measures (such as alarms, operation restrictions, etc.) to ensure the safety of the vehicle and battery system.

[0045] In some embodiments, the status detection command includes a high-voltage interlock detection command; the slave controller is further configured to send a loopback high-voltage interlock signal to the master controller in response to the high-voltage interlock detection command, and the master controller is further configured to determine whether there is an abnormality in the slave controller based on the high-voltage interlock signal, and if an abnormality is detected, send a high-voltage interlock fault to the vehicle controller and limit the vehicle's driving power.

[0046] In this embodiment, the slave controller responds to the high-voltage interlock detection command, entering the high-voltage interlock signal forwarding mode to cooperate with the master controller in completing the high-voltage interlock detection, ensuring the complete transmission of the signal along the loop. The high-voltage interlock signal is issued by the master controller, and the high-voltage interlock signal can specifically be a PWM signal. After passing through the high-voltage connector interlock terminals inside each slave controller, it loops back to the master controller. The master controller can determine whether the high-voltage connector is loose or disconnected by detecting whether the looped signal is complete, realizing remote diagnosis of the high-voltage loop integrity. The master controller detects parameters such as waveform, frequency, and amplitude of the looped high-voltage interlock signal to determine whether the signal is complete and whether there is an open circuit or short circuit abnormality, serving as the basis for determining whether the high-voltage connection loop is working properly. The high-voltage interlock fault is reported to the vehicle level, enabling the vehicle to obtain fault information and take corresponding measures, prompting the driver or after-sales personnel to check the high-voltage electrical connections. In cases where there is a risk of loosening or disconnection of the high-voltage connection, limiting the driving power rather than completely prohibiting power supply ensures driving safety and avoids the inconvenience caused by sudden vehicle breakdowns.

[0047] Figure 6 This is a schematic diagram of a high-voltage interlock circuit provided in an embodiment of this application, as shown below. Figure 6As shown, the controller includes a high-voltage interlock circuit, which includes a signal input terminal HIGH / LOCK1-IN, a first switching transistor Q58, a second switching transistor Q59, voltage divider resistors R393, R395, and R397, and a signal output terminal HIGH / LOCK1-CHECK. The signal input terminal HIGH / LOCK1-IN is used to receive the PWM high-voltage interlock signal sent by the main controller.

[0048] The control terminal of the first switch Q58 is connected to the signal input terminal HIGH / LOCK1-IN via resistor R393. The first terminal of the first switch Q58 is connected to the power supply terminal, and the second terminal of the first switch Q58 is connected to the control terminal of the second switch Q59 via resistor R395.

[0049] The first terminal of the second switch Q59 is grounded, and the second terminal of the second switch Q59 is connected to the signal output terminal HIGH / LOCK1-CHECK. The signal output terminal HIGH / LOCK1-CHECK is used to connect to the signal receiving terminal of the main controller and send a loopback high-voltage interlock signal to the main controller.

[0050] One end of resistor R397 is connected to the control terminal of the second switching transistor Q59, and the other end is grounded, used to provide bias voltage to the control terminal of the second switching transistor Q59; the first switching transistor Q58 is a PNP transistor, and the second switching transistor Q59 is an NPN transistor; the PWM high-voltage interlock signal is input through the signal input terminal HIGH / LOCK1-IN, and then sequentially passes through the first switching transistor Q58 and the second switching transistor Q59, looping back to the main controller from the signal output terminal HIGH / LOCK1-CHECK; when the high-voltage interlock circuit is normal, the PWM high-voltage interlock signal is transmitted completely from the signal input terminal to the signal output terminal; when there is an open circuit or short circuit in the high-voltage interlock circuit, the PWM high-voltage interlock signal will malfunction during transmission, and the main controller will determine that there is a fault in the high-voltage connection circuit based on the looped PWM high-voltage interlock signal.

[0051] Through the high-voltage interlock circuit, the PWM high-voltage interlock signal can be transmitted sequentially through the high-voltage connector interlock terminals of each slave controller, and finally loop back to the main controller. If any high-voltage connector becomes loose or falls off, the interlock circuit is broken, the signal transmission is interrupted, and the main controller can immediately identify and issue a fault signal.

[0052] In some embodiments, the master controller is also configured to periodically generate a wake-up command, switch from a sleep state to an operating state in response to the wake-up command, and supply power to the slave controller.

[0053] In this embodiment, the main controller has an internal timing module (such as an RTC real-time clock) that automatically generates wake-up commands at preset intervals (such as 30-60 minutes) without external triggering, enabling the battery management system to autonomously wake up at set intervals and providing a time reference and trigger source for periodic inspections. The main controller switches from a low-power sleep mode to a normal operating mode and begins executing inspection tasks. During sleep mode, the main controller uses a timed wake-up mechanism to keep it in a low-power sleep state most of the time, only briefly waking up when inspections are needed, effectively reducing the overall power consumption of the battery management system. After waking up, the main controller outputs power (such as a 12V linear power supply) to each slave controller, enabling them to power on from a power-off or standby state and ensuring they can respond to subsequent detection commands and collect data.

[0054] In some embodiments, the master controller is further configured to output a hibernation command to the slave controller if it determines that there is no fault in the battery subsystem; the slave controller is further configured to disable the wake-up trigger function and send a hibernation preparation completion signal back to the master controller in response to the hibernation command; the master controller is further configured to stop supplying power to the slave controller in response to the preparation completion signal.

[0055] In this embodiment, after completing location identification, cell status detection, air pressure detection, anti-theft detection, and high-voltage interlock detection commands to ensure the battery subsystem is fault-free, the main controller outputs a hibernation command to the slave controller. No further detection is needed. At this point, the slave controller responds to the hibernation command by disabling the wake-up trigger function and feeding back a hibernation preparation completion signal. The main controller responds to the hibernation preparation completion signal by stopping power supply to the slave controller, and the entire battery management system enters a low-power hibernation state, completing the inspection of each battery subsystem. This embodiment ensures a safe and orderly transition from the working state to the hibernation state through a complete process of fault confirmation → hibernation command → disabling the wake-up trigger function → handshake feedback → power-off hibernation. By cutting off power to the slave controller, the main controller achieves ultra-low power operation, effectively preventing the 12V battery from running out of power during long-term vehicle parking. By disabling the wake-up trigger function before hibernation, repeated system oscillations caused by accidental wake-ups are prevented. The master-slave hibernation handshake synchronization ensures the reliability and consistency of the hibernation process.

[0056] This application also provides a vehicle, which includes the battery management system of this embodiment.

[0057] In the vehicle provided in the embodiment, the main controller in the battery management system generates wake-up commands periodically according to a preset cycle, and switches from a dormant state to an active state in response to the wake-up commands, supplying power to the slave controllers. Then, the main controller sequentially sends out location identification commands, cell status detection commands, air pressure detection commands, anti-theft detection commands, and high-voltage interlock detection commands. The slave controllers respond to each command by collecting and reporting corresponding data. Based on the detection results reported by each slave controller, the main controller determines whether there is a fault in the battery subsystem, and performs corresponding processing (error prompts, power-off prohibition, or power limitation) according to the detection results. When it is determined that there is no fault in any battery subsystem, the main controller outputs a dormant command to the slave controllers. The slave controllers disable the wake-up trigger function and send back a dormant preparation completion signal. The main controller stops supplying power to the slave controllers, and the entire battery management system enters a dormant state, waiting for the next cycle to wake up.

[0058] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other.

[0059] Embodiments of the present invention are described with reference to flowchart illustrations and / or block diagrams of methods and apparatus according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing terminal device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal device, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0060] Although preferred embodiments of the present invention have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of the embodiments of the present invention.

[0061] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal device that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or terminal device. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or terminal device that includes said element.

[0062] The battery management system and vehicle provided by the present invention have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only for the purpose of helping to understand the method and core ideas of the present invention. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of the present invention. Therefore, the content of this specification should not be construed as a limitation of the present invention.

Claims

1. A battery management system, characterized in that, It includes a main controller and multiple battery subsystems, each battery subsystem is equipped with a slave controller, and the slave controller in each battery subsystem is connected to the main controller. The main controller is configured to send detection commands to the plurality of slave controllers in response to a wake-up command. The detection commands include location identification commands and various status detection commands. The slave controller is configured to, in response to the location identification command, acquire the electrical location information of the battery subsystem where the slave controller is located and send the electrical location information to the master controller, and in response to each of the state detection commands, collect the corresponding battery state parameters of the battery subsystem where the slave controller is located and send them to the master controller; The main controller is also configured to determine whether there is a fault in the battery subsystem based on the electrical location information and the battery state parameters.

2. The battery management system according to claim 1, characterized in that, The electrical location information includes a slave controller number, and the master controller is further configured to compare the slave controller number contained in the electrical location information with a pre-stored slave controller number; If they match, the electrical position of the slave controller is determined to be normal, and a recognition success command is sent to the slave controller. If there is a discrepancy, the electrical position of the controller is determined to be abnormal, and an electrical position mismatch fault signal is sent to the vehicle controller to display a fault prompt message to the user. In response to a user's re-identification command triggered by a slave controller for an electrical location anomaly, the system sends the location identification command to the slave controller for the electrical location anomaly, so that the slave controller can reacquire new electrical location information. The system then compares the slave controller number in the new electrical location information sent by the slave controller with the pre-stored slave controller number. If they match, the system sends a re-matching success signal to the vehicle controller to stop displaying fault prompt information to the user.

3. The battery management system according to claim 1, characterized in that, The slave controller is also configured to send the wake-up command to the master controller when an abnormal battery state of the battery subsystem is detected; wherein the abnormal battery state includes abnormal cell voltage, open circuit of cell sampling line and abnormal internal air pressure of battery system.

4. The battery management system according to claim 1, characterized in that, The various status detection commands include cell status detection commands; The slave controller is configured to, in response to the cell status detection command, collect the cell voltage, cell quantity, and sampling line status of the battery subsystem, and send them to the master controller; The main controller is further configured to determine whether the cell voltage is within a preset voltage threshold range, whether the number of cells is consistent with a preset number of cells, and whether there is an open circuit fault in the sampling line based on the state of the sampling line. If the cell voltage is not within the preset voltage threshold range, or the number of cells is inconsistent with the preset number of cells, or there is an open circuit fault in the sampling line, then the battery subsystem is determined to be faulty, and a thermal runaway fault signal is sent to the vehicle controller to prevent the vehicle from being powered on.

5. The battery management system according to claim 1, characterized in that, The various status detection commands include air pressure detection commands; The slave controller is also configured to, in response to the air pressure detection command, activate the air pressure sensor to detect the air pressure in the battery subsystem, determine whether the air pressure is abnormal, and send an abnormal air pressure signal to the master controller if the air pressure is abnormal. The main controller is also configured to send a thermal runaway fault signal to the vehicle controller in response to the abnormal air pressure signal, so as to prevent the vehicle from being powered on.

6. The battery management system according to claim 1, characterized in that, The slave controllers of two adjacent battery subsystems are connected in series via an anti-theft detection line, and the various status detection commands include anti-theft detection commands; The slave controller is also configured to perform battery anti-theft inspection in response to the anti-theft detection command and send an anti-theft line signal to the master controller; The main controller is also configured to send a battery system loss fault signal to the vehicle controller if it determines, based on the anti-theft cable signal, that at least one of the battery subsystems cannot be identified.

7. The battery management system according to claim 1, characterized in that, The status detection command includes a high-voltage interlock detection command; The slave controller is also configured to send a loopback high-voltage interlock signal to the master controller in response to the high-voltage interlock detection command. The main controller is also configured to determine whether there is an abnormality in the slave controller based on the high-voltage interlock signal. If an abnormality is detected, a high-voltage interlock fault is sent to the vehicle controller and the vehicle's driving power is limited.

8. The battery management system according to claim 1, characterized in that, The main controller is also configured to periodically generate wake-up commands, switch from a sleep state to a working state in response to the wake-up commands, and supply power to the slave controller.

9. The battery management system according to claim 1, characterized in that, The main controller is also configured to output a sleep command to the slave controller if it is determined that there is no fault in the battery subsystem. The slave controller is also configured to disable the wake-up trigger function and send a sleep preparation completion signal back to the master controller in response to the sleep command; The master controller is also configured to stop supplying power to the slave controller in response to the preparation completion signal.

10. A vehicle, characterized in that, The vehicle includes the battery management system according to any one of claims 1-9.

Images