Abnormity identification method and device of battery management system, electronic equipment and medium

CN118947034APending Publication Date: 2024-11-12CONTEMPORARY AMPEREX TECHNOLOGY CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280094361.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-09-08
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

The existing battery management system cannot identify coding anomalies, leading to battery pack power supply failures or safety hazards.

Method used

By identifying the preset code of the main BMU and the message sent from the BMU, it is determined whether there is an abnormality in the battery management system. If there is an abnormality, measures are taken to prohibit the battery from providing external power supply.

Benefits of technology

Accurately identify abnormalities in the battery management system, avoid battery pack power supply failures and safety hazards, and ensure system safety.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118947034A_ABST
    Figure CN118947034A_ABST
Patent Text Reader

Abstract

The embodiment of the invention provides an abnormity identification method and device of a battery management system, electronic equipment and a medium. The abnormity identification method of the battery management system is applied to the battery management system BMS. The BMS comprises a master BMU and at least one slave BMU; in response to the switching of the parallel branches in the battery, the slave BMU communicating with the master BMU is correspondingly switched; the method comprises the following steps: identifying a preset code of a main BMU; receiving a message sent by the slave BMU; and identifying whether the BMS is abnormal or not according to the preset code of the main BMU and the message. According to the abnormity identification method of the battery management system provided by the embodiment of the invention, the preset code of the master BMU is identified, and whether the BMS is abnormal is identified according to the preset code of the master BMU and the message sent by the slave BMU, so that corresponding measures are taken when the BMS is abnormal, and the abnormity of the battery management system is identified. Therefore, the technical problems that the code abnormity in the battery management system cannot be identified and the abnormal condition of the battery management system cannot be identified in the prior art are solved.
Need to check novelty before this filing date? Find Prior Art

Description

Abnormal identification method, device, electronic equipment and medium for battery management system Technical Field

[0001] The present application relates to the field of battery technology, and in particular to a method, device, electronic device, and medium for identifying abnormalities in a battery management system. Background Art

[0002] With the development of new energy technologies, power battery packs with the advantages of high energy density, rechargeable, safe and environmentally friendly have been widely used in new energy vehicles such as electric vehicles and other fields. Usually, a power battery pack consists of dozens or even hundreds of battery cells. A battery management system is usually set up to achieve unified management of the power battery pack. The battery management system contains multiple battery management units BMU, and each BMU is used to monitor the status of multiple battery cells. The related art uses the method of encoding the BMU to manage each BMU, but it is impossible to identify the coding anomalies in the battery management system, and it is also impossible to identify the abnormal conditions in the battery management system, which leads to the problem that the battery management system is prone to power supply failure of the battery pack or safety hazards due to abnormal conditions in actual applications.

[0003] Summary of the Invention

[0004] The embodiments of the present application provide a method, device, electronic device and medium for identifying abnormal conditions in a battery management system, which can identify abnormal conditions in the battery management system so that corresponding measures can be taken when a BMS abnormality occurs, thereby solving the technical problem that related technologies cannot identify coding abnormalities in the battery management system and cannot identify abnormal conditions in the battery management system.

[0005] In a first aspect, a method for identifying anomalies in a battery management system is provided, which is applied to a master battery management unit (BMU) of a battery management system (BMS); the BMS includes the master BMU and at least one slave BMU in communication with the master BMU; the method includes:

[0006] Identify the master BMU preset code;

[0007] Receiving the message sent from the BMU;

[0008] According to the master BMU preset code and the message, it is identified whether the BMS has an abnormality.

[0009] The battery management system abnormality identification method provided in the embodiment of the present application identifies whether the BMS has an abnormality by identifying the preset code of the main BMU and, based on the preset code of the main BMU and the message sent by the slave BMU, identifies whether the BMS has an abnormality so that corresponding measures can be taken when the BMS has an abnormality, thereby overcoming the technical problems that the related art cannot identify coding abnormalities in the battery management system and cannot identify abnormal conditions in the battery management system.

[0010] In one implementation, identifying whether the BMS is abnormal based on the master BMU preset code and the message includes:

[0011] Extracting BMU coded information from each of the messages received within the current preset period;

[0012] It is determined whether the BMS has an abnormality according to the preset code of the master BMU and all the extracted code information of the slave BMUs.

[0013] By determining whether there is an abnormality in the BMS based on the preset code of the master BMU and all the extracted code information of the slave BMUs, it is possible to accurately identify the presence of abnormal situations, so as to solve the problem of battery pack power supply failure or safety hazards caused by abnormal conditions in actual applications of the battery management system.

[0014] In one implementation, determining whether the BMS has an abnormality based on the preset code of the master BMU and all extracted code information of the slave BMUs includes:

[0015] Determining the number of slave BMUs currently in the BMS that communicate with the master BMU according to a preset code of the master BMU;

[0016] Determining whether a preset normal encoding condition is currently met based on the number of slave BMUs and the BMU identifier and BMU type carried in the encoding information of each slave BMU;

[0017] If the preset coding normal condition is not satisfied, it is determined that the BMS has an abnormality; otherwise, it is determined that the BMS has no abnormality.

[0018] By determining whether the BMS has an abnormality based on whether the preset coding normal conditions are met based on the BMU quantity, BMU identification and BMU type, it is possible to accurately identify the existence of abnormal situations, so as to solve the problem of battery pack power supply failure or safety hazards caused by abnormal conditions in actual applications of the battery management system.

[0019] In one implementation, the preset normal encoding conditions include that all slave BMU encoding information is of the same BMU type, that all slave BMU encoding information has different BMU identifiers, and that the number of messages is equal to the number of slave BMUs. Determining whether a BMS is abnormal based on whether the preset normal encoding conditions are met can more accurately identify abnormalities.

[0020] In one implementation, before identifying whether the BMS is abnormal based on the master BMU preset code and the message, the method further includes:

[0021] determining whether there is the message carrying the self-test error information, where the self-test error information is set in a message sent by the slave BMU after the slave BMU determines that it has been erroneously coded as the master BMU;

[0022] If so, it is determined that the BMS is abnormal; otherwise, it is determined whether the BMS is abnormal according to the master BMU preset code and the message.

[0023] The slave BMU performs self-check on its own coding. After determining that its own coding is incorrectly coded as the master BMU, it sends a message containing the slave BMU coding self-check error information, avoiding the problem of system confusion, branch response disorder, and communication abnormality caused by the existence of multiple master BMUs in the BMS branch.

[0024] In one implementation, the method further includes:

[0025] If the BMS is abnormal, the battery is controlled to prohibit external power supply.

[0026] When an abnormality occurs in the BMS, the control prohibits the battery from supplying external power, thereby avoiding the problem of battery pack power supply failure or safety hazards caused by abnormal conditions in actual applications of the battery management system.

[0027] In one implementation, the controlling prohibiting the battery from supplying external power includes:

[0028] The control disconnects the main relay connected to the master BMU and sends a command to all slave BMUs to disable high voltage. When a BMS anomaly occurs, the control disables the high voltage supply of the slave BMU to prevent the battery from supplying power. This prevents battery pack power failure or safety hazards caused by abnormal conditions in actual applications of the battery management system.

[0029] In one implementation, the slave BMU coded information carries a BMU identifier and a BMU type; and if the BMS is abnormal, controlling to prohibit the battery from supplying external power includes:

[0030] If a master BMU type exists among all the BMU types, or the number of messages exceeds the number of slave BMUs, the battery is controlled to disable external power supply after a preset time. After the preset time, the main relay connected to the master BMU is controlled to disconnect, thereby reserving reaction time for the vehicle controller to meet battery management safety requirements.

[0031] In a second aspect, a battery management system abnormality identification device is provided, which is applied to a master BMU of a battery management system (BMS); the BMS includes the master BMU and at least one slave BMU in communication with the master BMU; the device includes:

[0032] An identification storage module, configured to identify the master BMU preset code;

[0033] A message receiving module, configured to receive the message sent from the BMU;

[0034] The abnormality identification module is used to identify whether the BMS has an abnormality according to the preset code of the master BMU and the message.

[0035] The abnormality identification device of the battery management system provided in the second aspect can identify whether the BMS has an abnormality by identifying the preset code of the main BMU and, based on the preset code of the main BMU and the message sent by the BMU, identify whether the BMS has an abnormality, so as to take corresponding measures when the BMS has an abnormality, thereby overcoming the technical problem that the related technology cannot identify the coding abnormality in the battery management system and cannot identify the abnormal conditions in the battery management system.

[0036] In a third aspect, an electronic device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement any of the above-described methods for identifying abnormalities in a battery management system.

[0037] The electronic device provided in the third aspect is capable of implementing the battery management system abnormality identification method described in any of the above items. By identifying the main BMU preset code, it identifies whether the BMS has an abnormality based on the main BMU preset code and the message sent from the BMU, so as to take corresponding measures when the BMS has an abnormality, thereby overcoming the technical problem that the related technology cannot identify coding abnormalities in the battery management system and cannot identify abnormal conditions in the battery management system.

[0038] In a fourth aspect, a computer-readable storage medium is provided, on which a computer program is stored. The program is executed by a processor to implement any of the above-mentioned abnormality identification methods for a battery management system.

[0039] The computer-readable storage medium provided in the fourth aspect, when implementing the abnormality identification method of the battery management system described in any of the above items, identifies whether the BMS has an abnormality by identifying the preset code of the main BMU and, based on the preset code of the main BMU and the message sent from the BMU, identifies whether the BMS has an abnormality, so as to take corresponding measures when the BMS has an abnormality, thereby overcoming the technical problem that the related technology cannot identify the coding abnormality in the battery management system and cannot identify the abnormal conditions in the battery management system. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments of the present application. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the drawings without creative work.

[0041] Figure 1 is a block diagram of the connection structure between the vehicle ECU and the battery management system.

[0042] FIG2 is a flow chart of a method for identifying an abnormality in a battery management system according to an embodiment of the present application.

[0043] FIG3 is a flow chart of an embodiment of step S30 in FIG2 .

[0044] FIG4 is a schematic diagram of hard-wired coding of each BMU in a battery management system according to an example of the present application.

[0045] FIG5 is a schematic diagram of the communication process between the slave BMU and the master BMU.

[0046] FIG6 is a structural block diagram of an abnormality identification device of a battery management system provided in an embodiment of the present application.

[0047] FIG7 is a structural block diagram of an electronic device provided in an embodiment of the present application.

[0048] FIG8 is a schematic diagram of a computer-readable storage medium provided in an embodiment of the present application.

[0049] The realization of the objectives, functional features and advantages of this application will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0050] The following detailed description of the embodiments of the present application is provided in conjunction with the accompanying drawings and examples. The following detailed description of the embodiments and the accompanying drawings are used to illustrate the principles of the present application, but are not intended to limit the scope of the present application, that is, the present application is not limited to the described embodiments.

[0051] In the description of this application, it should be noted that, unless otherwise specified, "multiple" means more than two; the terms "upper", "lower", "left", "right", "inside", "outside", etc., indicating directions or positional relationships, are only for the convenience of describing this application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific direction, be constructed and operated in a specific direction, and therefore cannot be understood as a limitation on this application. In addition, the terms "first", "second", "third", etc. are only used for descriptive purposes and cannot be understood as indicating or implying relative importance. "Vertical" is not strictly perpendicular, but is within the error starting range. "Parallel" is not strictly parallel, but is within the error starting range.

[0052] The directional words appearing in the following description are all directions shown in the figures, and do not limit the specific structure of this application. In the description of this application, it should also be noted that, unless otherwise clearly specified and limited, the terms "installed", "connected", and "connected" should be understood in a broad sense. For example, it can be a fixed connection, a detachable connection, or an integral connection; it can be directly connected or indirectly connected through an intermediate medium. For ordinary technicians in this field, the specific meanings of the above terms in this application can be understood according to the specific circumstances.

[0053] With the development of new energy technologies, power batteries are increasingly being used. They are not only used in energy storage systems such as hydropower, thermal, wind, and solar power plants, but are also widely used in electric vehicles like electric bicycles, electric motorcycles, and electric vehicles, as well as in military equipment and aerospace applications. As the application areas of power batteries continue to expand, market demand is also growing. In practical applications, battery management systems are often deployed to centrally manage power battery packs.

[0054] A battery management system (BMS) consists of a master BMU and multiple slave BMUs connected to the master BMU via CAN. The BMU manages battery cells; each BMU can monitor multiple cells. The BMS manages battery packs composed of multiple cells connected in series and parallel. The BMS obtains various parameters related to the status of each cell through each BMU. A BMU (Battery Management Unit) is typically connected to an ECU, transmitting the acquired status information and various parameters of each cell to the ECU. An ECU (Electronic Control Unit), also known as a "driving computer" or "onboard computer," consists of a microcontroller (MCU), memory (ROM, RAM), input / output (I / O) interfaces, an analog-to-digital converter (A / D), and large-scale integrated circuits such as shaping and drivers. As shown in Figure 1, the master BMU is connected to the vehicle's ECU via the CAN bus, the vehicle's communication bus. CAN stands for Controller Area Network (CAN).

[0055] The master BMU (Master Battery Management Unit) is connected to each slave BMU (Subordinate Battery Management Unit) via CAN. Each slave BMU reports branch status information to the master BCU at set intervals.

[0056] Each slave BMU has the same hardware structure and appearance, making it difficult to distinguish them from each other and easily causing confusion. Related technologies use a method of encoding the slave BMUs to manage each slave BMU. Each slave BMU is encoded and written into each slave BMU, and the encoding is used to define each slave BMU so that each slave BMU can be identified by the encoding. However, when an abnormality occurs in the battery management system (BMS), an abnormality in the slave BMU encoding may occur. Related technologies are unable to identify abnormalities in the encoding of each slave BMU, and therefore are unable to identify abnormalities in the battery management system. As a result, the battery management system is prone to battery pack power failures or safety hazards due to abnormalities in actual applications.

[0057] In order to solve the above-mentioned problems existing in the related art, an embodiment of the present application provides a battery management system abnormality identification method, which identifies whether the BMS has an abnormality by identifying the preset code of the main BMU and the message sent by the main BMU and the message sent from the BMU, thereby overcoming the technical problems that the related art cannot identify coding abnormalities in the battery management system and cannot identify abnormal conditions in the battery management system.

[0058] One embodiment of the present application provides a method for identifying anomalies in a battery management system, which is applied to the main BMU of the battery management system BMS; the BMS includes a main BMU and at least one slave BMU in communication with the main BMU. Generally speaking, a battery may include multiple parallel branches, each branch including multiple battery cells in series and / or parallel, and for a battery management system, a branch can be monitored by a slave BMU, for example, multiple slave BMUs in the battery management system are configured in a one-to-one correspondence with multiple parallel branches of the battery. When a branch is running, the slave BMU monitoring the branch communicates with the main BMU, and when the branch stops running, the slave BMU monitoring the branch stops communicating with the main BMU. In response to the switching of the running branch in the battery, the slave BMU communicating with the main BMU switches accordingly. As shown in Figure 2, the method for identifying anomalies may include steps S10 to S30:

[0059] S10. Identify the preset code of the master BMU.

[0060] In some embodiments, in a battery management system (BMS), hardwires are directly connected to chip pins (PINs), transmitting high and low level signals. After power-on initialization, the master BMU identifies its own hardware code, and the slave BMUs also identify the hardware code. The slave BMUs then send the code result and code ID to the master BMU via the internal communication CAN (DCAN). The master BMU then aggregates the code results from the slave BMUs to determine the system status.

[0061] The master BMU's preset code may include the number of slave BMUs in communication with the master BMU in the BMS. The master BMU identifies and stores its own preset code, where 1 represents a high level and 0 represents a low level. In a specific example, the master BMU's preset code may be 11000, 11100, 11010, 11001, or 11011. Code 11000 indicates that two slave BMUs are currently communicating with the master BMU; code 11100 indicates that zero slave BMUs are currently communicating with the master BMU, meaning no slave BMUs are currently communicating with the master BMU; code 11010 indicates that one slave BMU is currently communicating with the master BMU; code 11001 indicates that three slave BMUs are currently communicating with the master BMU; and code 11011 indicates that four slave BMUs are currently communicating with the master BMU. The master BMU identifies its own preset code and obtains information about the number of slave BMUs currently communicating with it. The master BMU identifies its own preset code and stores the preset code.

[0062] S20: Receive a message sent from the BMU.

[0063] Within a preset period, each slave BMU sends a message to the master BMU. This message includes slave BMU coding information. This can include the slave BMU's actual coding within the current preset period, or slave BMU coding self-test error information. This self-test error information is an error message set in a message sent by a slave BMU after it self-checks its own coding and determines that it has been miscoded to the master BMU. The preset period can be set based on actual needs, for example, to 10ms, 15ms, or 20ms.

[0064] S30. Identify whether the BMS has any abnormality based on the preset code and message of the master BMU.

[0065] In some embodiments, as shown in FIG3 , step S30 includes steps S301 to S302:

[0066] S301: Extract BMU coding information from each message received in a current preset period.

[0067] If the slave BMU code information includes the actual code of the slave BMU within the current preset period, the actual code of the slave BMU is extracted. If the slave BMU code information includes the slave BMU code self-test error information, the slave BMU code self-test error information is extracted. The master BMU preset code includes the number of slave BMUs in the BMS that communicate with the master BMU.

[0068] In a specific example, there are four slave BMUs currently communicating with the master BMU, namely the first slave BMU, the second slave BMU, the third slave BMU, and the fourth slave BMU, referred to as slave 1, slave 2, slave 3, and slave 4, respectively. The actual codes of the slave BMUs are:

[0069] From 1:01100; from 2:01010; from 3:01001; from 4:01110.

[0070] Specifically, refer to Figure 4, which shows the hard-wired encoding of 1 master 2 slaves, 1 master 0 slaves, 1 master 1 slave, 1 master 3 slaves, 1 master 4 slaves, slave 1, slave 2, slave 3, and slave 4. The hardware requires five analog signal loops, with V2 being a high-voltage circuit. Each encoding is achieved by selectively shorting the pins of the external connector.

[0071] S302 : Determine whether the BMS has an abnormality based on the preset code of the master BMU and all extracted code information of the slave BMUs.

[0072] The slave BMU code information includes a slave BMU code, and the slave BMU code may carry a BMU identifier and a BMU type.

[0073] In some implementations, step S302 may include:

[0074] According to the preset coding of the master BMU, the number of slave BMUs communicating with the master BMU in the current BMS is determined; according to the number of slave BMUs and the BMU identifier and BMU type carried in the coding information of each slave BMU, it is judged whether the preset coding normal conditions are currently met; if the preset coding normal conditions are not met, it is determined that there is an abnormality in the BMS; otherwise, it is determined that there is no abnormality in the BMS.

[0075] Exemplarily, the preset normal encoding conditions may include that the BMU types of all slave BMU encoding information are slave BMU types, the BMU identifiers of all slave BMU encoding information are different, and the number of messages is equal to the number of slave BMUs.

[0076] By determining whether the BMS has an abnormality based on whether the preset coding normal conditions are met based on the BMU quantity, BMU identification and BMU type, it is possible to accurately identify abnormal situations, greatly improving the accuracy of abnormality determination, so as to solve the problem of battery pack power supply failure or safety hazards caused by abnormal conditions in actual applications of the battery management system.

[0077] For example, if the number of messages actually received is less than the number of slave BMUs in the preset coding information of the master BMU, the master BMU determines that the message is lost, and the number of actual branches is less than the number of branches defined by the preset coding, then it is determined that there is an abnormality in the BMS.

[0078] If the number of messages actually received is less than the number of slave BMUs in the preset coding information of the master BMU, that is, the number of actual branches is greater than the number of branches defined by the preset coding, the master BMU determines that there is an abnormality in the BMS.

[0079] If the master BMU receives a branch message with the same code within a preset period (for example, the master BMU identifies from the preset code that there are two slave BMUs communicating with the master BMU, namely slave 1 and slave 2, but the code extracted from the received message is two slave 1 codes, that is, the two codes are the same), the master BMU determines that the message is abnormal and the BMS is abnormal.

[0080] If the information in the message actually received is inconsistent with the information identified by the master BMU from the preset code (for example, the information obtained by the master BMU from identifying the preset code is that there are two slave BMUs communicating with the master BMU, namely slave 1 and slave 2, but the codes extracted from the message actually received are 1 slave 1 code and 1 slave 3 code, which is an inconsistent situation), the master BMU determines that the BMS is abnormal.

[0081] In some implementations, before step S30, the method of this embodiment may further include:

[0082] Determine whether there is a message carrying self-test error information. The self-test error information is set in the message sent by the slave BMU after it determines that it has been erroneously coded as the master BMU. If so, it is determined that there is an abnormality in the BMS. Otherwise, execute the code and message preset by the master BMU to identify whether there is an abnormality in the BMS.

[0083] The slave BMU coding self-check error information is information set in the message sent by the slave BMU after the slave BMU performs self-check on its own coding and determines that its own coding is erroneously coded by the master BMU.

[0084] If a slave BMU is mistakenly coded as a master BMU, multiple master BMUs will exist in multiple branches of the BMS, leading to system confusion, branch response errors, and communication anomalies. The slave BMU performs a self-check of its own code. After confirming that it is mistakenly coded as a master BMU, it sends a message containing the slave BMU code self-check error information. This avoids the system confusion, branch response errors, and communication anomalies caused by the presence of multiple master BMUs in a BMS branch.

[0085] When a slave BMU in a battery management system is mistakenly encoded as a master BMU, the entire battery management system will be in chaos, resulting in problems such as branch response confusion and communication anomalies in the battery management system. Therefore, identifying whether a slave BMU has been mistakenly encoded as a master BMU within the current preset cycle is a crucial aspect of ensuring the safety of the battery management system.

[0086] When a slave BMU's coding information contains a slave BMU coding self-test error, it indicates that the corresponding slave BMU has mistakenly identified itself as the master BMU during coding self-test. The master BMU consists of four modules connected in sequence: the DCAN (Debug CAN communication module), MSCM (mechanic state control management module), ADER (Application Diagnostic Error Reaction module), and CTCC (contator control cell module). The slave BMU consists of three modules connected in sequence: the ATDC (bottom chip sampling module), MSCM, and DCAN.

[0087] For example, as shown in FIG5 , taking slave 1 being mistakenly encoded as the master BMU as an example, when slave 1 performs encoding self-detection, the MSCM module of slave 1 is awakened by the wake-up source DCAN fed back by the ATDC module, and recognizes that slave 1 is mistakenly encoded as the master BMU, and then sends a flag to the DCAN module of slave 1, triggering the logical broadcast to send a trigger message to the master BMU. The DCAN module of the master BMU receives the trigger message and sends the master BMU encoding duplication flag to the MSCM module of the master BMU. The MSCM module of the master BMU provides the exception type to the ADER module, and the ADER module performs corresponding processing.

[0088] When a slave BMU checks its own encoding and finds that it has not been mistakenly encoded as a master BMU, it continues to send the current encoding to the master BMU via a message. The master BMU then determines whether the encoding is incorrect based on the actual encoding extracted from the message. If the actual encoding is identified as the master BMU type, it determines that the actual encoding is inconsistent with the master BMU's preset encoding information.

[0089] When the battery management system is not experiencing an abnormality, the actual codes of each slave BMU are unique. If two or more slave BMUs have the same actual code, communication confusion within the battery management system will occur. The master BMU determines whether an abnormality exists by comparing the actual codes of each slave BMU to see if there are two or more identical codes. If two or more slave BMUs have the same actual code, a coding error is determined. Normally, each slave BMU only sends a message once per preset cycle. Therefore, the number of messages received by the master BMU in a preset cycle is equal to the number of slave BMUs, and the codes of each slave BMU are unique. If the number of received messages does not match the number of slave BMUs, an abnormality is determined.

[0090] By determining whether there is an abnormal condition in the BMS so that corresponding measures can be taken for the abnormal condition, the problem of battery pack power supply failure or safety hazard caused by abnormal conditions in actual application of the battery management system is solved.

[0091] The battery management system abnormality identification method provided in the embodiment of the present application identifies whether the BMS has an abnormality by identifying the preset code of the main BMU and, based on the preset code of the main BMU and the message sent by the slave BMU, identifies whether the BMS has an abnormality so that corresponding measures can be taken when the BMS has an abnormality, thereby overcoming the technical problems that the related art cannot identify coding abnormalities in the battery management system and cannot identify abnormal conditions in the battery management system.

[0092] In some implementations, the method of this embodiment may further include:

[0093] S40: If the BMS is abnormal, the battery is prohibited from supplying power to the outside.

[0094] In some implementations, controlling to prohibit the battery from supplying power to the outside includes: controlling to prohibit high voltage from the BMU to prohibit the battery from supplying power to the outside.

[0095] Specifically, controlling to prohibit the battery from supplying power externally includes: controlling to disconnect a main relay connected to the master BMU, and sending an instruction to prohibit high voltage application to all slave BMUs.

[0096] Specifically, the slave BMU encoding information carries a BMU identifier and a BMU type; step S40 may include: if a master BMU type exists among all BMU types, or the number of messages is greater than the number of slave BMUs, controlling to prohibit the battery from supplying power externally after a preset time.

[0097] In some embodiments, if the BMS is abnormal, the battery is controlled to prohibit external power supply, including:

[0098] If there is a master BMU type among all BMU types or the number of messages is greater than the number of slave BMUs, the main relay connected to the master BMU will be disconnected after a preset time, and a command to prohibit high voltage will be sent to all slave BMUs;

[0099] If the number of messages is less than the number of slave BMUs, all slave BMU coding information contains at least one slave BMU coding self-test error message, or there are at least two identical BMU identifiers, the main relay connected to the master BMU is controlled to be disconnected, and an instruction to prohibit high voltage is sent to all slave BMUs.

[0100] For example, if there is a master BMU type among all BMU types or the number of messages is greater than the number of slave BMUs, the master BMU controls the disconnection of the main relay connected to the master BMU after a preset time (the preset time can be, for example, 2s, 2.5s or 3s, which can be pre-set according to actual application needs) and sends an instruction to all slave BMUs to prohibit high voltage.

[0101] For example, if the number of messages received by the master BMU is less than the number of slave BMUs defined in the preset code, all slave BMU code information contains at least one slave BMU code self-test error message, or there are at least two identical BMU identifiers, the master BMU controls the disconnection of the main relay connected to the master BMU and sends an instruction to all slave BMUs to prohibit high voltage.

[0102] When an abnormality occurs in the BMS, the control prohibits the battery from supplying external power, thereby avoiding the problem of battery pack power supply failure or safety hazards caused by abnormal conditions in actual applications of the battery management system.

[0103] As shown in Figure 6, another embodiment of the present application provides an abnormality identification device for a battery management system, which is applied to the master BMU of a battery management system (BMS). The BMS includes a master BMU and at least one slave BMU in communication with the master BMU. The abnormality identification device includes:

[0104] Identification storage module, used to identify the main BMU preset code;

[0105] A message receiving module is used to receive messages sent from the BMU;

[0106] The abnormality identification module is used to identify whether the BMS has abnormalities based on the preset codes and messages of the main BMU.

[0107] The abnormality identification device for the battery management system provided in the embodiment of the present application can identify whether the BMS has an abnormality by identifying the preset code of the main BMU and, based on the preset code of the main BMU and the message sent by the slave BMU, so as to take corresponding measures when the BMS has an abnormality, thereby overcoming the technical problems that the related art cannot identify coding abnormalities in the battery management system and cannot identify abnormal conditions in the battery management system.

[0108] In some embodiments, the anomaly identification module includes:

[0109] A slave BMU code information extraction unit, configured to extract slave BMU code information from each message received within a current preset period;

[0110] The abnormality determination unit is used to determine whether the BMS has an abnormality based on the master BMU preset code and all the extracted slave BMU code information.

[0111] In some embodiments, the abnormality determination unit determines whether the BMS has an abnormality based on the master BMU preset code and all extracted slave BMU code information, including:

[0112] According to the preset coding of the master BMU, the number of slave BMUs communicating with the master BMU in the current BMS is determined; according to the number of slave BMUs and the BMU identifier and BMU type carried in the coding information of each slave BMU, it is judged whether the preset coding normal conditions are currently met; if the preset coding normal conditions are not met, it is determined that there is an abnormality in the BMS; otherwise, it is determined that there is no abnormality in the BMS.

[0113] In some implementations, the preset normal encoding conditions include that the BMU types of all slave BMU encoding information are slave BMU types, the BMU identifiers of all slave BMU encoding information are different, and the number of messages is equal to the number of slave BMUs.

[0114] In some embodiments, the apparatus of this embodiment further includes a self-test error information determination module configured to: determine whether a message containing self-test error information exists before identifying whether the BMS is abnormal based on the master BMU's preset code and message; if so, determine that the BMS is abnormal; otherwise, identify whether the BMS is abnormal based on the master BMU's preset code and message. The self-test error information is set in a message sent by a slave BMU after it determines that it has been erroneously coded as the master BMU.

[0115] In some implementations, the device of this embodiment further includes a power supply control module configured to control the battery from supplying external power if an abnormality occurs in the BMS.

[0116] When an abnormality occurs in the BMS, the control prohibits the battery from supplying external power, thereby avoiding the problem of battery pack power supply failure or safety hazards caused by abnormal conditions in actual applications of the battery management system.

[0117] In some embodiments, controlling to prohibit the battery from supplying external power includes:

[0118] The control disconnects the main relay connected to the master BMU and sends a command to all slave BMUs to prohibit high voltage application.

[0119] In some embodiments, the BMU code information carries a BMU identifier and a BMU type; if the BMS is abnormal, the battery is controlled to prohibit external power supply, including:

[0120] If a master BMU type exists among all BMU types, or the number of messages is greater than the number of slave BMUs, the battery is controlled to prohibit external power supply after a preset time.

[0121] Another embodiment of the present application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. The processor executes the computer program to implement any of the above-described methods for identifying abnormalities in a battery management system.

[0122] As shown in Figure 7, the electronic device 10 may include: a processor 100, a memory 101, a bus 102 and a communication interface 103, and the processor 100, the communication interface 103 and the memory 101 are connected through the bus 102; the memory 101 stores a computer program that can be run on the processor 100, and when the processor 100 runs the computer program, it executes the method provided in any of the aforementioned embodiments of the present application.

[0123] The memory 101 may include high-speed random access memory (RAM) and may also include non-volatile memory, such as at least one disk storage. The system network element communicates with at least one other network element via at least one communication interface 103 (which may be wired or wireless), and may utilize the Internet, a wide area network, a local area network, a metropolitan area network, or the like.

[0124] Bus 102 may be an ISA bus, a PCI bus, or an EISA bus. Buses may be classified as address buses, data buses, and control buses. Memory 101 is used to store programs, and processor 100 executes the programs upon receiving execution instructions. The methods disclosed in any of the aforementioned embodiments of the present application may be applied to or implemented by processor 100.

[0125] The processor 100 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by hardware integrated logic circuits in the processor 100 or by software instructions. The above processor 100 may be a general-purpose processor, which may include a central processing unit (CPU), a network processor (NP), etc.; it may also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an off-the-shelf field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The various methods, steps, and logic block diagrams disclosed in the embodiments of this application can be implemented or executed. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of this application can be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory 101 , and the processor 100 reads the information in the memory 101 and completes the steps of the above method in combination with its hardware.

[0126] The electronic device provided in the embodiments of the present application and the method provided in the embodiments of the present application are based on the same inventive concept and have the same beneficial effects as the methods adopted, operated or implemented by them.

[0127] Another embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, which is executed by a processor to implement any of the above-mentioned abnormality identification methods for a battery management system.

[0128] Referring to FIG. 8 , the computer-readable storage medium shown therein is an optical disc 20 on which a computer program (ie, a program product) is stored. When the computer program is executed by a processor, the method provided in any of the aforementioned embodiments is executed.

[0129] It should be noted that examples of computer-readable storage media may also include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other optical or magnetic storage media, which are not listed here one by one.

[0130] The computer-readable storage medium provided in the above-mentioned embodiments of the present application and the method provided in the embodiments of the present application are based on the same inventive concept and have the same beneficial effects as the method adopted, run or implemented by the application program stored therein.

[0131] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0132] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0133] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

[0135] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0136] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0137] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A method for identifying abnormalities in a battery management system, characterized in that: A master BMU applied to a battery management system (BMS); the BMS includes the master BMU and at least one slave BMU in communication with the master BMU; the method includes: Identify the master BMU preset code; Receiving the message sent from the BMU; According to the master BMU preset code and the message, it is identified whether the BMS has an abnormality.

2. The method according to claim 1, characterized in that The identifying whether the BMS is abnormal according to the master BMU preset code and the message includes: Extracting BMU coded information from each of the messages received within the current preset period; It is determined whether the BMS has an abnormality according to the preset code of the master BMU and all the extracted code information of the slave BMUs.

3. The method according to claim 2, characterized in that The determining whether the BMS has an abnormality according to the preset code of the master BMU and all the extracted code information of the slave BMUs includes: Determining the number of slave BMUs currently in the BMS that communicate with the master BMU according to a preset code of the master BMU; Determining whether a preset normal encoding condition is currently met based on the number of slave BMUs and the BMU identifier and BMU type carried in the encoding information of each slave BMU; If the preset coding normal condition is not satisfied, it is determined that the BMS has an abnormality; otherwise, it is determined that the BMS has no abnormality.

4. The method according to claim 3, characterized in that The preset normal encoding conditions include that the BMU types of all slave BMU encoding information are slave BMU types, the BMU identifiers of all slave BMU encoding information are different, and the number of the messages is equal to the number of slave BMUs.

5. The method according to any one of claims 1 to 4, characterized in that Before identifying whether the BMS is abnormal based on the master BMU preset code and the message, the method further includes: determining whether there is the message carrying the self-test error information, where the self-test error information is set in a message sent by the slave BMU after the slave BMU determines that it has been erroneously coded as the master BMU; If so, it is determined that the BMS is abnormal; otherwise, it is determined whether the BMS is abnormal according to the master BMU preset code and the message.

6. The method according to claims 1-5, characterized in that The method further comprises: If the BMS is abnormal, the battery is controlled to prohibit external power supply.

7. The method according to claim 6, characterized in that The controlling prohibiting the battery from supplying power externally includes: The main relay connected to the master BMU is controlled to be disconnected, and an instruction to prohibit high voltage is sent to all the slave BMUs.

8. The method according to claim 6, characterized in that The slave BMU coded information carries a BMU identifier and a BMU type; if the BMS is abnormal, controlling to prohibit the battery from supplying power externally includes: If a master BMU type exists among all the BMU types, or the number of the messages is greater than the number of the slave BMUs, the battery is controlled to be prohibited from supplying power to the outside after a preset time period.

9. An abnormality identification device for a battery management system, characterized in that: A master BMU applied to a battery management system (BMS); the BMS includes the master BMU and at least one slave BMU in communication with the master BMU; the device includes: An identification storage module, configured to identify a preset code of the master BMU; A message receiving module, configured to receive the message sent from the BMU; The abnormality identification module is used to identify whether the BMS has an abnormality according to the preset code of the master BMU and the message.

10. An electronic device, characterized in that: The system comprises a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the method according to any one of claims 1 to 8.

11. A computer-readable storage medium having a computer program stored thereon, characterized in that: The program is executed by a processor to implement the method according to any one of claims 1 to 8.