Communication detection method of battery management system and battery management system

Abstract

The invention provides a communication detection method of a battery management system and the battery management system, the battery management system comprises a general control device, a plurality of main control devices and a plurality of slave control devices, the general control device is connected with the plurality of main control devices through an AUTBUS bus network, and each main control device is connected with the plurality of slave control devices through the AUTBUS bus network; the method comprises the following steps: the master control equipment broadcasts a heartbeat message to each master control equipment connected with the master control equipment according to a set sending frequency, and confirms a communication state with each master control equipment according to a heartbeat response message received within a set time; the plurality of slave control devices respectively report the collected battery cell state messages to the connected master control device according to the set time intervals, and the master control device confirms the communication state with each slave control device according to the battery cell state messages received within the set time. Through the heartbeat transceiving mechanism, communication faults in the battery management system can be effectively reduced, and the communication reliability of the whole system is improved.

Description

Technical Field

[0001] The present application relates to the technical field of battery monitoring and management, and in particular to a communication detection method for a battery management system and a battery management system. Background Art

[0002] In the Battery Management System (BMS), the heartbeat mechanism is a key communication detection protocol. During data transmission, the sender will periodically send a short signal to the receiver and respond immediately after receiving the response. This mechanism can detect whether the communication link is unobstructed. Once it is found that the signal is not responded to in time, it can be judged that the communication has failed. Therefore, the heartbeat mechanism plays an important role in ensuring data integrity and normal operation of the system.

[0003] At present, battery management systems usually use CAN or Modbus buses for communication, and generally adopt a heartbeat transmission and reception strategy that periodically sends heartbeat packets to detect the online status of each node in the network. This strategy sets a fixed interval time to allow each node to send a short heartbeat signal to other nodes or central servers to indicate its own active status. After receiving the heartbeat packet within the preset time, the receiver will reply with a confirmation message to complete a heartbeat detection. Although the existing heartbeat strategy can ensure the stability of the network in most cases, the fixed heartbeat packet sending frequency may cause network congestion, especially in large-scale energy storage systems, where frequent heartbeat signals will increase the network burden. In addition, the fixed heartbeat packet sending frequency may not adapt to changes in network conditions, resulting in heartbeat packet loss or delay, hindering the system's accurate judgment of the node status, resulting in insufficient identification and isolation of faulty nodes, which in turn reduces the response speed of the entire system. Summary of the invention

[0004] In view of this, the present application proposes a communication detection method for a battery management system, a battery management system, a device, and a storage medium. By constructing a heartbeat receiving and sending mechanism based on the AUTBUS bus network, the communication failures in the battery management system can be effectively reduced and the communication reliability of the entire system can be improved.

[0005] In a first aspect, the present application provides a communication detection method for a battery management system, the battery management system comprising a master control device, a plurality of master control devices and a plurality of slave control devices, the master control device being connected to a plurality of master control devices via an AUTBUS bus network, and each master control device being connected to a plurality of slave control devices via an AUTBUS bus network; the method comprising:

[0006] The master control device broadcasts heartbeat messages to each master control device connected to it according to the set sending frequency, and confirms the communication status with each master control device according to the heartbeat response message received within the set time. The heartbeat response message is generated by the master control device in response to the received heartbeat message according to its device address, and reported to the master control device according to the set time interval;

[0007] The plurality of slave control devices report the collected cell status messages to the connected master control device at the set time intervals respectively, and the master control device confirms the communication status with each slave control device according to the cell status messages received within the set time.

[0008] From the above, the battery management system in this application adopts AUTBUS bus network for networking. Based on the AUTBUS bus network, the master control device can regularly broadcast heartbeat messages to each master control device connected to it. After each master control device receives the heartbeat message, it can generate a heartbeat response message according to its device address response, and report it to the master control device at the time interval set by it, so that the master control device can confirm whether the communication status with each master control device is normal according to whether the heartbeat response message reported by the master control device is received within the set time. At the same time, the slave control device can also report the collected battery cell status message to the master control device connected to it according to the time interval set by it. The battery cell status message can be used as a heartbeat signal. The master control device can confirm whether the communication status with each slave control device is normal according to whether the battery cell status message reported by the slave control device is received within the set time. This application realizes the heartbeat transceiver mechanism through the AUTBUS bus network, thereby realizing the detection of the communication status between each device inside the battery management system, effectively reducing the communication failures in the battery management system and improving the communication reliability of the entire system.

[0009] Optionally, also include:

[0010] The master control device parses the received battery cell status message and confirms the operation status of each slave control device according to the real-time data updated in the battery cell status message, wherein the real-time data includes the real-time voltage and the real-time temperature of the battery cell.

[0011] From the above, the master control device can obtain key data such as the real-time voltage and real-time temperature of the battery cells connected to each slave control device by parsing the received battery cell status message. The master control device can determine whether the real-time data is updated based on the parsing result of the battery cell status message received each time, so as to confirm whether the operating status of the slave control device is normal, thereby realizing the ability to monitor the refined operating status of the battery management system and ensuring the safe and efficient operation of the battery pack.

[0012] Optionally, also include:

[0013] The master control device dynamically adjusts the sending frequency of the heartbeat message according to the number of devices in the system and the communication load of the AUTBUS bus network.

[0014] From the above, the master control device can dynamically adjust the sending frequency of the heartbeat message according to the number of devices in the entire system and the communication load of the AUTBUS bus network. When the number of devices increases or the communication load increases, the master control device can reduce the sending frequency of the heartbeat message accordingly. Conversely, when the number of devices decreases or the communication load is reduced, the master control device can increase the sending frequency of the heartbeat message accordingly. By dynamically adjusting the sending frequency of the heartbeat message, the battery management system can more flexibly adapt to application scenarios of different scales and loads, ensuring that the stability and reliability of the system are not affected.

[0015] Optionally, the master control device and the slave control device in the battery management system are respectively configured with their own unique device addresses according to their connection sequence in the AUTBUS bus network;

[0016] The master control device and the slave control device respectively determine the time interval for reporting the heartbeat response message or the battery cell status message by multiplying the device address by a specific time coefficient.

[0017] From the above, the master device and the slave device are respectively configured with their own unique device addresses according to their connection order in the AUTBUS bus network, ensuring that each device has a unique identity in the network, and the master device and the slave device respectively determine the time interval for reporting the heartbeat response message or the battery status message by multiplying their device addresses by a specific time coefficient, so that the reporting time interval of each device is dynamically calculated according to its device address, avoiding network congestion and data conflicts caused by multiple devices reporting at the same time. At the same time, by adjusting the specific time coefficient, the system can flexibly adjust the reporting frequency to adapt to different application scenarios and communication requirements. The present application realizes a non-uniform heartbeat interval response mechanism by calculating the differentiated time intervals for each device to report the heartbeat response message or the battery status message, thereby avoiding excessive bus resource occupation caused by all devices reporting the heartbeat response message or the battery status message at the same time, and reducing the potential interference to other data messages during the peak period of the heartbeat response, avoiding data packet loss.

[0018] Optionally, the heartbeat message, heartbeat response message and battery cell status message are packaged in a specific message format, and the specific message format includes a message service ID, a target device address, and a data length.

[0019] From the above, the heartbeat message, heartbeat response message and battery status message can be packaged in a message format that only contains necessary information, thereby reducing the message size and improving transmission efficiency. By defining a unified message format, the device does not need to perform complex preprocessing or format conversion on the message, and can directly read the key information in the message, such as the message type, target address and data content, thereby improving the efficiency and speed of message processing.

[0020] Optionally, also include:

[0021] When the master control device does not receive the heartbeat message broadcast by the master control device within the set time, it confirms that the communication with the master control device is abnormal and performs abnormal processing;

[0022] When the master control device does not receive the cell status message reported by the slave control device connected thereto within a set time, it is determined that an abnormality occurs in the communication with the slave control device and an abnormality processing is performed.

[0023] From the above, when the master device does not receive the heartbeat message broadcast by the master device within the set time, it can be confirmed that the communication with the master device is abnormal. Similarly, when the master device does not receive the battery cell status message reported by the slave device to which it is connected within the set time, it can also be confirmed that the communication with the slave device is abnormal. Timely communication fault detection can reduce the system downtime caused by communication faults, and adopt corresponding exception handling strategies according to different fault types and severity to ensure the reliability and stability of the battery management system.

[0024] Optionally, also include:

[0025] When the master control device does not receive the heartbeat response message reported by the connected master control device within a set time, it is confirmed that the communication with the master control device is abnormal and the abnormality is handled.

[0026] From the above, when the master control device does not receive the heartbeat response message reported by the connected master control device within the set time, it can confirm that the communication with the master control device is abnormal. This mechanism is combined with the mechanism of the master control device detecting the communication anomaly with the master control device and the slave control device to form a comprehensive communication fault detection network. Through this comprehensive detection mechanism, the system can timely discover and locate any fault on the communication link, whether it is between the master control device and the master control device, or between the master control device and the slave control device, and can be quickly responded and processed.

[0027] In a second aspect, the present application provides a battery management system, which adopts a three-layer architecture, including a master control device arranged in a master control layer, a plurality of master control devices arranged in a master control layer, and a plurality of slave control devices arranged in a slave control layer, wherein the master control device is connected to a plurality of master control devices via an AUTBUS bus network, and each master control device is connected to a plurality of slave control devices via an AUTBUS bus network;

[0028] The master control device broadcasts heartbeat messages to each master control device connected to it according to the set sending frequency, and confirms the communication status with each master control device according to the heartbeat response message received within the set time. The heartbeat response message is generated by the master control device in response to the received heartbeat message according to its device address, and reported to the master control device according to the set time interval;

[0029] The plurality of slave control devices report the collected cell status messages to the connected master control device at the set time intervals respectively, and the master control device confirms the communication status with each slave control device according to the cell status messages received within the set time.

[0030] In a third aspect, the present application provides a computing device, the computing device comprising:

[0031] processor;

[0032] A memory for storing one or more programs;

[0033] When the one or more programs are executed by the processor, the processor implements the above-mentioned communication detection method for a battery management system.

[0034] In a fourth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a computer, implements the above-mentioned communication detection method for a battery management system.

[0035] These and other aspects of the present application will become more apparent from the following description of the embodiment(s). BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1 A structural diagram of a battery management system provided in an embodiment of the present application;

[0037] Figure 2 A flow chart of a communication detection method for a battery management system provided in an embodiment of the present application;

[0038] Figure 3 A flow chart of communication detection between a master control device and a main control device provided in an embodiment of the present application;

[0039] Figure 4A flow chart of communication detection between a master control device and a slave control device provided in an embodiment of the present application;

[0040] Figure 5 A structural diagram of a computing device provided in an embodiment of the present application.

[0041] It should be understood that the size and shape of each block diagram in the above structural diagram are for reference only and should not constitute an exclusive interpretation of the embodiments of the present application. The relative positions and inclusion relationships between the blocks presented in the structural diagram are only schematic representations of the structural associations between the blocks, and do not limit the physical connection methods of the embodiments of the present application. DETAILED DESCRIPTION

[0042] The technical solution provided by the present application is further described below with reference to the accompanying drawings and examples. It should be understood that the system structure and business scenarios provided in the examples of the present application are mainly to illustrate the possible implementation methods of the technical solution of the present application and should not be interpreted as the only limitation on the technical solution of the present application. It is known to those of ordinary skill in the art that with the evolution of the system structure and the emergence of new business scenarios, the technical solution provided by the present application is also applicable to similar technical problems.

[0043] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art of the present application. In case of any inconsistency, the meaning described in this specification or the meaning derived from the contents recorded in this specification shall prevail. In addition, the terms used herein are only for the purpose of describing the embodiments of the present application and are not intended to limit the present application.

[0044] The embodiment of the present application proposes a communication detection method and a battery management system for a battery management system. By constructing a heartbeat receiving and sending mechanism based on the AUTBUS bus network, the problems of communication congestion and low efficiency faced by the heartbeat communication mechanism in the battery management system are effectively solved. The solution not only improves the communication efficiency and security of the system, but also reduces the risk of network congestion and heartbeat packet loss.

[0045] like Figure 1As shown, an embodiment of the present application provides a battery management system, which adopts a three-layer architecture, including a master control device 110 arranged in a master control layer (BAU), multiple master control devices 120 arranged in a master control layer (BCU), and multiple slave control devices 130 arranged in a slave control layer (BMU). The master control device 110 is connected to several master control devices 120 through an AUTBUS bus network, and each master control device 120 is connected to several slave control devices 130 through an AUTBUS bus network. Each device in the battery management system can realize heartbeat transmission and reception through the AUTBUS bus network, and judge the communication status between each device according to the heartbeat transmission and reception situation, thereby realizing the detection of the communication status between each device in the battery management system, effectively reducing the communication failure in the battery management system, and improving the communication reliability of the entire system.

[0046] like Figure 2 As shown, the embodiment of the present application provides a communication detection method for a battery management system, which can be Figure 1 The battery management system shown is implemented to detect the communication status between various devices in the battery management system. Figure 2 As shown, the method includes:

[0047] S210: The master control device broadcasts heartbeat messages to each connected master control device according to a set sending frequency, and confirms the communication status with each master control device according to the heartbeat response messages received within a set time.

[0048] In this embodiment, based on the AUTBUS bus network between the master control device and several main control devices, the master control device can broadcast heartbeat messages to each main control device connected to it according to its set sending frequency. The main control device can confirm whether the communication status between the master control device and the master control device is normal based on whether the heartbeat message is received within the set time (for example, 5 seconds). When the master control device does not receive the heartbeat message broadcast by the master control device within the set time, it can be confirmed that the communication with the master control device is abnormal. At this time, the master control device can start the preset fault handling process and alarm display to ensure that the system can respond and handle faults in a timely manner to ensure the safety of the system.

[0049] If the master control device receives the heartbeat message broadcast by the master control device within the set time, it can generate a heartbeat response message according to its device address response, and report it to the master control device at the set time interval. If the master control device receives the heartbeat response message reported by the master control device within the set time (for example, 5 seconds), it can be confirmed that the communication status with each master control device is normal. Otherwise, the master control device can also start the preset fault handling process and alarm display.

[0050] S220: Several slave control devices report their collected cell status messages to the connected master control device at set time intervals respectively, and the master control device confirms the communication status with each slave control device according to the cell status messages received within the set time.

[0051] In this embodiment, based on the AUTBUS bus network between the master device and several slave devices, each slave device can report the collected battery status message to the connected master device at the set time interval. The battery status message can be used as a heartbeat signal to detect the communication status between the master device and the slave device. If the master device receives the battery status message reported by the slave device within the set time (for example, 5 seconds), it can confirm that the communication status with each slave device is normal, and the master device can also parse the battery status message and confirm whether the operating status of the slave device is normal based on whether the real-time data in the battery status message (for example, the real-time voltage of the battery cell, the real-time temperature of the battery cell) is updated.

[0052] If the master device does not receive the cell status message reported by the slave device within the set time, it is confirmed that the communication with the slave device is abnormal. At this time, the master device can start the preset fault handling process and alarm display.

[0053] In some embodiments, the above-mentioned heartbeat message, heartbeat response message and battery status message can be packaged in a message format that contains only necessary information, and the message format includes a message service ID, a target device address and a data length, wherein the message service ID is used to identify the type of message to facilitate the execution of corresponding processing, and the target device address is used to determine the device address of the target of the message to ensure that the message is sent to the correct device. By setting a concise and effective message format, the message size is reduced and the transmission efficiency is improved. By defining a unified message format, the device does not need to perform complex preprocessing or format conversion on the message, and can directly read the key information in the message, such as the message type, target address and data content, thereby improving the efficiency and speed of message processing.

[0054] The embodiment of the present application builds an AUTBUS bus network between the various levels of the battery management system, and implements a heartbeat transceiver mechanism through the AUTBUS bus network. The master control device regularly broadcasts heartbeat messages and receives heartbeat responses from the master control device, and the slave control device regularly reports the cell status message and is confirmed by the master control device. It can monitor the communication status between the various levels of devices in the battery management system in real time. Once a communication link fails or is delayed, the system can quickly discover and trigger an early warning mechanism, thereby avoiding the impact of communication failures on the overall operation of the battery management system. In addition, by setting a reasonable message sending frequency and time interval, it is possible to avoid unnecessary communication overhead while ensuring the effectiveness of communication, thereby optimizing the allocation of internal communication resources in the battery management system and improving the communication reliability and stability of the entire system.

[0055] Refer to the following Figure 3-Figure 4 As shown, the heartbeat receiving and sending mechanism between the general control device, the master control device and the slave control device in the embodiment of the present application is described in detail.

[0056] like Figure 3 The figure shows a communication detection flow chart of a master control device and a main control device provided in an embodiment of the present application, referring to Figure 3 As shown, the communication detection process between the master control device and the main control device includes:

[0057] S310: The master control device broadcasts a heartbeat message to the AUTBUS bus network to which it is connected according to the set sending frequency.

[0058] In this step, the master control device can count the number of devices in the entire system in real time. During the transmission of the heartbeat message, the master control device can dynamically adjust the frequency of sending the heartbeat message according to the number of devices in the entire system and the communication load of the AUTBUS bus network. When the number of devices increases or the communication load increases, the master control device can reduce the frequency of sending the heartbeat message accordingly, which can help reduce communication overhead and extend network life. On the contrary, when the number of devices decreases or the communication load is reduced, the master control device can increase the frequency of sending the heartbeat message accordingly, which can help reduce communication delay and ensure the real-time nature of the data. Based on this, no matter how many devices there are, the master control device can ensure that the system has enough time to respond to the heartbeat message by dynamically adjusting the frequency of sending the heartbeat message, while avoiding excessive occupation of bus resources when the load is low, so that the master control device can better cope with the uncertainty factors in network communication, so that the battery management system can more flexibly adapt to application scenarios of different scales and loads, and ensure that the stability and reliability of the system are not affected.

[0059] S320: The master control device determines whether the heartbeat message broadcast by the master control device is received within a set time.

[0060] The master control device determines whether the heartbeat message broadcast by the master control device is received within the set time according to the set time, so as to determine whether the communication status between the master control device and the master control device is normal.

[0061] S330: The main control device performs exception processing.

[0062] If the master control device does not receive the heartbeat message broadcast by the master control device through the AUTBUS bus network within the set time, it can be confirmed that there is an abnormality in the communication with the master control device. At this time, the master control device can take corresponding measures according to the preset exception handling strategy. These measures may include retrying to establish a communication connection, recording a fault log, triggering an alarm mechanism, etc., to ensure the stability and reliability of the system.

[0063] S340: The master control device generates a heartbeat response message according to its own device address and reports it to the master control device.

[0064] If the master control device receives the heartbeat message broadcast by the master control device through the AUTBUS bus network within the set time, it can respond to the heartbeat message according to its own device address, generate a heartbeat response message, and report it to the master control device at the set time interval.

[0065] In this embodiment, the master control device can configure its own unique device address according to its connection sequence in the AUTBUS bus network to ensure that it has a unique identity in the network, and in order to prevent multiple master control devices from reporting heartbeat response messages at the same time, causing network congestion, this embodiment can generate differentiated time intervals for reporting heartbeat response messages according to the device address of each master control device, and realize a non-uniform heartbeat interval response mechanism, thereby avoiding excessive occupation of bus resources caused by all devices reporting heartbeat response messages at the same time, and reducing potential interference with other data messages during the peak period of heartbeat response, avoiding data packet loss. Specifically, the device address of each master control device can be multiplied by a specific time coefficient to calculate the time interval for each master control device to report the heartbeat response message. When the master control device receives the heartbeat message of the master control device and generates a heartbeat response message, it can report to the master control device according to the time interval set by it.

[0066] Exemplarily, after receiving the heartbeat message from the master control device, the master control device can multiply its own device address by a specific time coefficient to obtain a reporting period with a time interval of 8 AUTBUS data frames, which is about 32 milliseconds. Then, the master control device can report its heartbeat response message according to the 32 millisecond time interval, so that the master control device can judge the communication status with the master control device according to the heartbeat response signal. By adjusting the time interval for each master control device to report the heartbeat response message, network congestion and data conflicts caused by multiple master control devices reporting at the same time can be avoided. At the same time, the reporting frequency can be flexibly adjusted by adjusting the specific time coefficient to adapt to different application scenarios and communication requirements.

[0067] S350: The master control device determines whether the heartbeat response message reported by the master control device is received within a set time.

[0068] The master control device determines whether the heartbeat response message reported by the master control device is received within the set time according to the set time, so as to determine whether the communication status between the master control device and the master control device is normal.

[0069] S360: The master control device performs exception processing.

[0070] If the master control device does not receive the heartbeat response message reported by the main control device through the AUTBUS bus network within the set time, it can be confirmed that there is an abnormality in the communication with the main control device. At this time, the master control device can take corresponding measures according to the preset exception handling strategy. These measures may include retrying to establish a communication connection, recording a fault log, triggering an alarm mechanism, etc., to ensure the stability and reliability of the system.

[0071] S360: Enter the next heartbeat receiving and sending cycle.

[0072] If the master control device receives the heartbeat response message reported by the master control device through the AUTBUS bus network within the set time, it can be determined that the communication status between the master control device and the master control device is normal and enters the next heartbeat transmission and reception cycle.

[0073] Figure 4 The figure shows a communication detection flow chart of a master control device and a slave control device provided in an embodiment of the present application, referring to Figure 4 As shown, the communication detection process between the master device and the slave device includes:

[0074] S410: The slave control device reports the collected cell status message to the connected master control device at a set time interval.

[0075] In this embodiment, the slave control device can be configured with its own unique device address according to its connection order in the AUTBUS bus network to ensure that it has a unique identity in the network. In order to prevent multiple slave control devices from reporting battery status messages at the same time and causing network congestion, this embodiment can generate differentiated time intervals for reporting battery status messages according to the device address of each slave control device. Specifically, the time interval for each slave control device to report the battery status message can be calculated by multiplying the device address of each slave control device by a specific time coefficient.

[0076] After completing the configuration of the device address and time interval, the slave device can report its collected cell status message to the connected master device at the set time interval, so that the master device can determine the communication status with the slave device based on the cell status message.

[0077] S420: The master control device determines whether the cell status message reported by the slave control device is received within a set time.

[0078] The master device determines whether the cell status message reported by the slave device is received within the set time according to the set time, so as to determine whether the communication status between the master device and the slave device is normal.

[0079] If the master device receives the cell status message reported by the slave device within the set time, it can be confirmed that the communication status between the master device and the slave device is normal.

[0080] In some embodiments, the master control device can also parse the battery cell status message to obtain real-time data in the battery cell status message, such as key data such as the real-time voltage and real-time temperature of the battery cell connected to the slave control device. The master control device can determine whether the real-time data is updated based on the parsing results of the battery cell status message received each time, so as to confirm whether the operating status of the slave control device is normal, thereby realizing the capability of fine-grained monitoring of the operating status of the battery management system and ensuring the safe and efficient operation of the battery pack.

[0081] In some embodiments, the main control device can also dynamically adjust the charging and discharging strategies according to the real-time voltage and temperature data of the battery cell. For example, when the battery cell temperature is high, the main control device can reduce the charging current to avoid overheating; when the battery cell voltage is close to the upper limit, the main control device can adjust the charging mode to slow down the charging speed and protect the battery cell from damage. By dynamically adjusting the charging and discharging of the battery, the service life of the battery pack can be effectively extended and the overall energy efficiency of the system can be improved.

[0082] S430: The main control device performs exception processing.

[0083] If the master device does not receive the battery cell status message reported by the slave device through the AUTBUS bus network within the set time, it can be confirmed that the communication with the slave device is abnormal. At this time, the master device can take corresponding measures according to the preset exception handling strategy. These measures may include retrying to establish a communication connection, recording a fault log, triggering an alarm mechanism, etc., to ensure the stability and reliability of the system.

[0084] S440: Enter the next heartbeat receiving and sending cycle.

[0085] If the master device receives the cell status message reported by the slave device through the AUTBUS bus network within the set time, it can be determined that the communication status between the master device and the slave device is normal and enters the next heartbeat transmission and reception cycle.

[0086] In summary, the embodiment of the present application networks the devices of each level of the battery management system by using the AUTBUS bus network. Based on the AUTBUS bus network, the master control device can regularly broadcast heartbeat messages to the master control devices connected to it. After receiving the heartbeat message, each master control device can generate a heartbeat response message according to its device address response, and report it to the master control device at the time interval set by it, so that the master control device can confirm whether the communication status with each master control device is normal according to whether the heartbeat response message reported by the master control device is received within the set time. At the same time, the slave control device can also report the collected battery cell status message to the master control device connected to it at the time interval set by it. The battery cell status message can be used as a heartbeat signal. The master control device can confirm whether the communication status with each slave control device is normal according to whether the battery cell status message reported by the slave control device is received within the set time. The embodiment of the present application realizes the heartbeat transceiver mechanism through the AUTBUS bus network, thereby realizing the detection of the communication status between the devices inside the battery management system, effectively reducing the communication failures in the battery management system, and improving the communication reliability of the entire system.

[0087] Figure 5 5 is a structural diagram of a computing device 500 provided in an embodiment of the present application. The computing device 500 includes: a processor 510 , a memory 520 , a communication interface 530 , and a bus 540 .

[0088] It should be understood that Figure 5 The communication interface 530 in the computing device 500 shown may be used to communicate with other devices.

[0089] The processor 510 may be connected to a memory 520. The memory 520 may be used to store the program code and data. Therefore, the memory 520 may be a storage unit inside the processor 510, or an external storage unit independent of the processor 510, or a component including a storage unit inside the processor 510 and an external storage unit independent of the processor 510.

[0090] Optionally, the computing device 500 may further include a bus 540. The memory 520 and the communication interface 530 may be connected to the processor 510 via the bus 540. The bus 540 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The bus 540 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 5 The fact that only one line is used in the diagram does not mean that there is only one bus or only one type of bus.

[0091] It should be understood that in the embodiment of the present application, the processor 510 may adopt a central processing unit (CPU). The processor may also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. Alternatively, the processor 510 may adopt one or more integrated circuits to execute relevant programs to implement the technical solutions provided in the embodiment of the present application.

[0092] The memory 520 may include a read-only memory and a random access memory, and provides instructions and data to the processor 510. A portion of the processor 510 may also include a nonvolatile random access memory. For example, the processor 510 may also store information on the device type.

[0093] When the computing device 500 is running, the processor 510 executes the computer-executable instructions in the memory 520 to perform the operating steps of the above method.

[0094] It should be understood that the computing device 500 according to the embodiment of the present application can correspond to the corresponding subjects in the methods according to the embodiments of the present application, and the above-mentioned other operations and / or functions of each module in the computing device 500 are respectively for realizing the corresponding processes of each method of the present embodiment. For the sake of brevity, they will not be repeated here.

[0095] Those of ordinary skill 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 to be beyond the scope of this application.

[0096] Those skilled in the art can 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.

[0097] In the several embodiments provided in the present 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 only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, 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.

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

[0099] 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.

[0100] 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 can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods 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.

[0101] An embodiment of the present application also provides a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, it is used to execute the above method, which includes at least one of the solutions described in the above embodiments.

[0102] The computer storage medium of the embodiment of the present application can adopt any combination of one or more computer-readable media. Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable storage media can be, for example, but not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or devices, or any combination of the above. More specific examples (non-exhaustive lists) of computer-readable storage media include: electrical connections with one or more wires, portable computer disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), optical fibers, portable compact disk read-only memories (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the above. In this document, computer-readable storage media can be any tangible medium containing or storing programs, which can be used by instruction execution systems, devices or devices or used in combination with them.

[0103] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, which carry computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0104] The program code embodied on the computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0105] Computer program code for performing the operation of the present application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as an independent software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (e.g., using an Internet service provider to connect through the Internet).

[0106] It should be noted that the embodiments described in the present application are only a part of the embodiments of the present application, rather than all the embodiments. The components of the embodiments of the present application usually described and shown in the drawings can be arranged and designed in various different configurations. Therefore, the above detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application claimed for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present application.

[0107] The words "first, second, third, etc." or module A, module B, module C and other similar terms in the specification and claims are only used to distinguish similar objects and do not represent a specific ordering of the objects. It is understandable that the specific order or sequence can be interchanged where permitted so that the embodiments of the present application described herein can be implemented in an order other than that illustrated or described herein.

[0108] In the above description, the numbers representing the steps involved do not necessarily mean that the steps will be executed. Intermediate steps may be included or replaced by other steps. The order of the previous and next steps may be interchanged or executed simultaneously if permitted.

[0109] The term "comprising" as used in the description and claims should not be interpreted as being limited to what is listed thereafter; it does not exclude other elements or steps. Therefore, it should be interpreted as specifying the presence of the features, integers, steps or components mentioned, but does not exclude the presence or addition of one or more other features, integers, steps or components and groups thereof. Therefore, the expression "a device comprising means A and B" should not be limited to a device consisting of components A and B only.

[0110] The "one embodiment" or "embodiment" mentioned in this specification means that the specific features, structures or characteristics described in conjunction with the embodiment are included in at least one embodiment of the present application. Therefore, the terms "in one embodiment" or "in an embodiment" appearing in various places in this specification do not necessarily refer to the same embodiment, but may refer to the same embodiment. In addition, in the various embodiments of the present application, if there is no special explanation and logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form a new embodiment according to their inherent logical relationship.

[0111] Note that the above are only preferred embodiments of the present application and the technical principles used. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present application is described in more detail through the above embodiments, the present invention is not limited to the above embodiments, and may also include more other equivalent embodiments without departing from the concept of the present invention, all of which belong to the protection scope of the present invention.

Claims

1. A communication detection method for a battery management system, characterized in that: The battery management system includes a master control device, a plurality of master control devices and a plurality of slave control devices, wherein the master control device is connected to a plurality of master control devices via an AUTBUS bus network, and each master control device is connected to a plurality of slave control devices via an AUTBUS bus network; the method includes: The master control device broadcasts heartbeat messages to each master control device connected to it according to the set sending frequency, and confirms the communication status with each master control device according to the heartbeat response message received within the set time. The heartbeat response message is generated by the master control device in response to the received heartbeat message according to its device address, and reported to the master control device according to the set time interval; The plurality of slave control devices report the collected cell status messages to the connected master control device at the set time intervals respectively, and the master control device confirms the communication status with each slave control device according to the cell status messages received within the set time.

2. The method according to claim 1, characterized in that Also includes: The master control device parses the received battery cell status message and confirms the operation status of each slave control device according to the real-time data updated in the battery cell status message, wherein the real-time data includes the real-time voltage and the real-time temperature of the battery cell.

3. The method according to claim 1, characterized in that: Also includes: The master control device dynamically adjusts the sending frequency of the heartbeat message according to the number of devices in the system and the communication load of the AUTBUS bus network.

4. The method according to claim 1, characterized in that: The master control device and the slave control device in the battery management system are respectively configured with their own unique device addresses according to their connection sequence in the AUTBUS bus network; The master control device and the slave control device respectively determine the time interval for reporting the heartbeat response message or the battery cell status message by multiplying the device address by a specific time coefficient.

5. The method according to claim 1, characterized in that The heartbeat message, the heartbeat response message and the cell status message are packaged in a specific message format, and the specific message format includes a message service ID, a target device address and a data length.

6. The method according to claim 1, characterized in that Also includes: When the master control device does not receive the heartbeat message broadcast by the master control device within the set time, it confirms that the communication with the master control device is abnormal and performs abnormal processing; When the master control device does not receive the cell status message reported by the slave control device connected thereto within a set time, it is determined that an abnormality occurs in the communication with the slave control device and an abnormality processing is performed.

7. The method according to claim 1, characterized in that Also includes: When the master control device does not receive the heartbeat response message reported by the connected master control device within a set time, it is confirmed that the communication with the master control device is abnormal and the abnormality is handled.

8. A battery management system, characterized in that: The battery management system adopts a three-layer architecture, including a master control device arranged in the master control layer, multiple master control devices arranged in the master control layer, and multiple slave control devices arranged in the slave control layer. The master control device is connected to several master control devices through an AUTBUS bus network, and each master control device is connected to several slave control devices through an AUTBUS bus network. The master control device broadcasts heartbeat messages to each master control device connected to it according to the set sending frequency, and confirms the communication status with each master control device according to the heartbeat response message received within the set time. The heartbeat response message is generated by the master control device in response to the received heartbeat message according to its device address, and reported to the master control device according to the set time interval; The plurality of slave control devices report the collected cell status messages to the connected master control device at the set time intervals respectively, and the master control device confirms the communication status with each slave control device according to the cell status messages received within the set time.

9. A computing device, characterized in that include: processor; A memory for storing one or more programs; When the one or more programs are executed by the processor, the processor implements the communication detection method for a battery management system as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: A computer program is stored thereon, and when the computer program is executed by a computer, the communication detection method for a battery management system as claimed in any one of claims 1 to 7 is implemented.

Images