BMS (Battery Management System) communication abnormity judgment and data reorganization method, BMS system and storage medium
By realizing daisy chain communication exception determination and data reorganization methods in the BMS system, and automatically switch to the standby interface, the system interruption problem caused by communication link exceptions in the prior art is solved, and the automation and reliability of the system are improved.
Patent Information
- Application Number
- CN202411798521.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-09
- Publication Date
- 2025-03-21
AI Technical Summary
The existing battery management system cannot automatically switch to the standby interface when the communication link is abnormal, resulting in system communication interruption and manual intervention is required, affecting the stability and reliability of the system.
A BMS daisy chain communication abnormality determination and data reorganization method is proposed. By detecting the continuous offline state of the slave controller, it is determined that the main communication interface is in a disconnected state, and automatically switches to the backup communication interface to perform data reorganization and storage.
Automatic processing when abnormal situations are detected is realized, which improves the degree of automation of the system, reduces the need for manual intervention, improves the convenience and efficiency of operation, and enhances the stability and reliability of the system.
Smart Images

Figure CN119676064A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of electric vehicles, and in particular to a BMS communication abnormality determination and data reorganization method, a BMS system and a storage medium. Background Art
[0002] The existing battery management system (Battery Management System) usually adopts a master-slave communication interface design, that is, the master controller communicates with the slave controller in series via the communication interface. However, this design has significant defects: any abnormality in the communication link will cause the system communication to be interrupted, requiring manual intervention to restore.
[0003] First, when the communication line is interrupted, the system cannot obtain subsequent data, resulting in incomplete data, which affects the reliability and stability of the system. At the same time, the existing battery management system has insufficient data transmission exception handling capabilities. Abnormalities in the main communication interface will cause the system to crash and require manual intervention, which increases the complexity of operation and reduces the degree of automation. In addition, the system lacks the ability to automatically switch to the backup communication interface, which further limits the stability and reliability of the system. Summary of the invention
[0004] In order to solve the above technical problems, the present application proposes a BMS communication abnormality determination and data reorganization method, a BMS system and a storage medium.
[0005] In the first aspect, the present application provides a BMS daisy chain communication abnormality determination and data reorganization method, which adopts the following technical solutions: A BMS daisy chain communication abnormality determination and data reorganization method is used for a master controller and a slave controller communicating with the master controller through a master communication interface, wherein the method comprises: When an offline slave controller is detected in the BMS system, the number of the offline slave controller is recorded as an offline slave controller number array, and the number of the online slave controller is recorded as an online slave controller number array; If the number of the offline slave controller is in a continuous state, it is determined that the master communication interface is in a disconnected state; The cache array obtained by the main communication interface through the slave controller is temporarily stored in the record array, the backup communication interface of the main controller is called to obtain the cache array through the slave controller, the cache array and the record array are inserted and merged and stored in the record array, and the data in the record array is stored in the cache array.
[0006] Preferably, if the numbering of the offline slave controllers is in a continuous state, determining that the master communication interface is in a disconnected state comprises: The elements in the offline slave controller number array are weighted and summed to obtain a first element weighted sum, the elements in the online slave controller number array are weighted and summed to obtain a second element weighted sum, the first element weighted sum and the second element weighted sum are weighted and summed to obtain a first weighted sum, and the natural number numbers of the slave controllers are weighted and summed to obtain a second weighted sum, If the first weighted sum is equal to the second weighted sum, it is determined that the numbers of the offline slave controllers are in a continuous state.
[0007] Preferably, the cache array is used to store communication data between the master controller and the slave controller, and the communication data includes single cell voltage and temperature in the battery pack of the electric vehicle.
[0008] In a second aspect, the present application provides a BMS system, which adopts the following technical solution: A BMS system, wherein the BMS system uses the BMS daisy chain communication abnormality determination and data reorganization method as described in any one of the first aspects above, the BMS system includes the master controller and at least one slave controller, and the master controller communicates with the slave controller through the master communication interface and the backup communication interface.
[0009] In a third aspect, the present application provides a storage medium, which adopts the following technical solution: A storage medium, wherein the storage medium stores at least one instruction, at least one program, a code set or an instruction set, and the at least one instruction, the at least one program, the code set or the instruction set is loaded and executed by a processor to implement the BMS daisy chain communication abnormality determination and data reorganization method as described in any one of the first aspects above.
[0010] In summary, the method for starting a backup interface and the method for data reorganization of the present application can automatically handle abnormal situations when they are detected without the need for human intervention, thereby improving the degree of automation of the system, reducing the need for human intervention, and thus improving the convenience and efficiency of operation. BRIEF DESCRIPTION OF THE DRAWINGS
[0011] Figure 1 It is a schematic block diagram of a BMS system in the prior art; Figure 2 for Figure 1 The schematic block diagram of the BMS system communication abnormality shown; Figure 3 A flow chart of an embodiment of a BMS system of the present application; Figure 4 for Figure 3 A schematic diagram of a flow chart when communication is abnormal in the embodiment shown; Figure 5This is a flow chart of an embodiment of a method for determining abnormality in BMS daisy chain communication and reorganizing data according to the present application; Figure 6 for Figure 5 A schematic diagram showing the principle of the data reorganization process in the illustrated embodiment; Figure 7 A schematic block diagram of a method for determining abnormalities in BMS daisy chain communication and reorganizing data executed by the BMS system of the present application; Figure 8 The figure is a flow chart of an embodiment of a method for determining abnormality in BMS daisy chain communication of the present application. DETAILED DESCRIPTION
[0012] The present application is further described below in conjunction with the accompanying drawings, and the structure and principle of the present application are very clear to people in the field. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.
[0013] Figure 1 is a schematic block diagram of a BMS system in the prior art, Figure 2 for Figure 1 The block diagram of the BMS system communication abnormality shown in the figure. The battery management system (BMS) is a core component of electric vehicles, responsible for monitoring and managing the battery status to ensure safe, efficient and long-life operation of the battery. In medium and large power battery systems (system voltage exceeds 48V), the BMS often adopts a master-slave topology distributed structure, consisting of a master controller and multiple slave controllers, and obtains battery status information through communication. In BMS internal communication, daisy chain communication technology is favored because of its simple wiring and low cost, but it also has obvious defects: any failure in the communication interface of any device will cause the entire communication chain to be interrupted, affecting data transmission.
[0014] Existing BMS technology usually adopts a master-slave communication interface design, that is, the master controller communicates with the slave controller in sequence. This design has the problem that any abnormality in the communication link will cause the system communication to be interrupted, and the data cannot be transmitted further, requiring manual intervention to recover. At the same time, after the communication line is interrupted, the system cannot obtain subsequent data, resulting in incomplete data, affecting the reliability and stability of the system. In addition, when the main communication interface is abnormal, the system may be paralyzed and require manual intervention to recover, which increases the complexity of operation and reduces the degree of automation. In addition, when the main communication interface is abnormal, the system cannot automatically switch to the backup communication interface, further limiting the stability and reliability of the system.
[0015] Figure 3 This is a flow chart of an embodiment of the BMS system of the present application. Figure 4 for Figure 3 The flowchart of the embodiment shown is a flow chart of abnormal communication. Figure 5This is a flow chart of an embodiment of a method for determining abnormality in BMS daisy chain communication and reorganizing data in the present application. Figure 6 for Figure 5 The schematic diagram of the principle of the data reorganization process in the embodiment shown. Figure 3 , Figure 4 , Figure 5 and Figure 6 It can be understood that in a medium or large-scale distributed BMS system, it is generally composed of a BMS master controller and multiple slave controllers. With the development of integrated circuits, the slave controllers mostly use integrated chips with daisy chain communication interfaces to realize the acquisition of battery voltage and temperature and the realization of balancing functions. Since daisy chain communication is a serial communication method, if there is an abnormal disconnection in the middle of the communication line, a hardware failure of the slave controller (such as poor welding of the isolation transformer), or severe electromagnetic interference leading to communication interruption, the BMS master controller can only obtain the data at the normal end of the daisy chain line (normal online data), and cannot obtain the data after the daisy chain is broken. For this reason, the deployed daisy chain BMS should have a double-end daisy chain communication interface to achieve complete acquisition of slave controller data even if the communication line is interrupted, thereby improving the stability and reliability of the BMS system.
[0016] The daisy chain communication BMS data reorganization method of the present application, when the BMS main controller has two daisy chain physical interfaces (COM1 as the main communication interface, COM2 as the backup communication interface), under normal circumstances, only one of the main and backup communication interfaces is used to collect data, and the two are backups for each other. When an abnormal situation occurs, the backup communication interface is enabled to participate in data collection.
[0017] A BMS daisy chain communication abnormality determination and data reorganization method of the present application, which is used for a master controller and a slave controller communicating with the master controller through a master communication interface, may include the following steps: Step S1: When an offline slave controller is detected in the BMS system, the number of the offline slave controller is recorded as an offline slave controller number array, and the number of the online slave controller is recorded as an online slave controller number array. In step S1, the core communication interface function of the main controller runs smoothly and has a processing mechanism: once it is detected that the slave controller in the battery management system (BMS) is offline, a special logic response will be immediately initiated. Specifically, the system will record the offline slave controller numbers in detail. If these numbers are continuous, that is, after the first offline slave controller, all slave controllers arranged in sequence are displayed as offline, it can be reasonably inferred that the main communication interface has encountered a communication interruption. At this time, the system will quickly switch to the backup interface program to ensure that it can continue to obtain the key data of the slave controller after the interruption, and then enter the logical processing flow of data reorganization to ensure the stable operation of the system and data integrity.
[0018] Step S2: If the number of the offline slave controller is in a continuous state, it is determined that the main communication interface is in a disconnected state. In step S2, during the communication between the master controller and n slave controllers in a daisy chain manner, if the communication is interrupted due to a hardware failure of the slave controller or a line break, the following operations will be performed: the master controller can normally connect and identify the slave controllers before the interruption point, which are considered to be online; while the slave controllers after the interruption point cannot establish a connection and are in an offline state. The master controller will record the numbers of these online and offline BMS slave controllers in detail, marked as OnLineSubNodeREC[SubNodeNum] (online slave controller number record) and OffLineSubNodeREC[LineOpen_SubNodeNum] (offline slave controller number and disconnection position record). Due to the inherent characteristics of the daisy chain communication of the battery sampling chip, that is, the online slave controller numbers are always arranged continuously, therefore, it is only necessary to observe whether the offline BMS slave controller numbers are also continuous to accurately determine whether the communication interruption is caused by a disconnection somewhere in the link. This logic provides a basis for quickly locating and responding to communication anomalies.
[0019] Therefore, in step S2, the elements in the offline slave controller number array are weighted and summed to obtain the weighted sum of the first element, the elements in the online slave controller number array are weighted and summed to obtain the weighted sum of the second element, the weighted sum of the first element and the weighted sum of the second element are weighted and summed to obtain the first weighted sum, the natural number numbers of the slave controllers are weighted and summed to obtain the second weighted sum, and if the first weighted sum is equal to the second weighted sum, it is determined that the numbers of the offline slave controllers are in a continuous state.
[0020] Step S3: temporarily store the cache array obtained by the main communication interface from the slave controller in the record array, call the backup communication interface of the main controller to obtain the cache array from the slave controller, insert and merge the cache array and the record array and store them in the record array, and store the data in the record array in the cache array. In step S3, first define a two-dimensional array CellBuf[ ][ ] to cache the slave controller cell voltage and temperature data obtained by the main communication interface. When an interruption in the daisy chain line is detected, the system will first temporarily store the data in CellBuf[ ][ ] in a record array CellRec[ ][ ] to ensure the integrity of the original data.
[0021] The system will then call the backup interface to continue collecting the BMS slave controller data after the daisy chain line is disconnected, and cache the data in the form of single cell voltage and temperature in CellBuf[ ][ ]. At this time, there are two parts of data: one part is the data obtained through the main interface before the interruption (temporarily stored in the cache array CellRec[ ][ ]), and the other part is the data obtained through the backup interface after the interruption (stored in the record array CellBuf[ ][ ]). The cache array is used to store the communication data between the main controller and the slave controller, and the communication data includes the single cell voltage and temperature in the battery pack of the electric vehicle. The system will then insert and merge CellBuf[ ][ ] and CellRec[ ][ ] to ensure the continuity and integrity of the data. The result of this process will be stored in CellRec[ ][ ] and then verified to verify the accuracy and consistency of the data. After the verification is successful, the system will copy the data in CellRec[ ][ ] back to the original array CellBuf[ ][ ] to update and restore the data status of the system. Finally, the data in CellRec[ ][ ] will be cleared and released to complete the entire data reorganization process, ensuring the efficient operation of the system and the accuracy of the data.
[0022] The present application proposes a BMS system, which uses the above-mentioned BMS daisy chain communication abnormality judgment and data reorganization method. The BMS system includes a master controller and at least one slave controller. The master controller communicates with the slave controller through a master communication interface and a backup communication interface.
[0023] Next, the specific implementation of the above method will be introduced.
[0024] Figure 7 It is a schematic block diagram of the BMS system of the present application executing the BMS daisy chain communication abnormality determination and data reorganization method, Figure 8 This is a flow chart of an embodiment of the BMS daisy chain communication abnormality determination method of the present application. Figure 7 and Figure 8 It can be understood that the BMS system can be composed of a BMS master controller and 18 slave controllers. In order to achieve smooth information interaction, the BMS master controller is connected to each slave controller through the ISO_SPI bus. This connection method enables the BMS master controller to obtain the voltage and temperature data fed back by each slave controller in real time. In the current software configuration, SPI's COM1 has been selected as the main communication port. Accordingly, in order to enhance the flexibility and reliability of the system, COM2 can be set as an auxiliary communication port. In this way, when necessary, the system can switch to the auxiliary port to maintain the continuity of communication.
[0025] In order to achieve this function, this application designs two function call interfaces, corresponding to the main communication port and the auxiliary communication port respectively: LTC6813_sample_update(0,SubNodeNum,HMI_CellNum); / / / / This function call indicates the use of the master port (identified as 0) for data transmission, where SubNodeNum represents the number of slave controllers and HMI_CellNum represents the number of battery cells managed by each slave controller LTC6813_sample_update(1,LineOpen_SubNodeNum,HMI_CellNum); / / This function call indicates the use of the auxiliary port (marked as 1) for data transmission. LineOpen_SubNodeNum specifically refers to the number of slave controllers that have lost connection due to the SPI bus disconnection. There are two issues that need to be addressed at this time: ①When to call the auxiliary SPI port for execution? ②How to recombine the data? Regarding question ①: When to call the auxiliary SPI port for execution? First, the main controller should execute the function program of the main port normally. During the program running, if it is detected that a BMS slave controller is offline, it should be analyzed and processed immediately. The specific method is to record the numbers of the offline BMS slave controllers and carefully observe whether these numbers are continuous. If it is found that the numbers of the offline BMS slave controllers are arranged in sequence, for example, starting from a certain number, all subsequent BMS slave controllers are displayed as offline, then we can reasonably infer that this may be caused by the disconnection of the wiring harness of the main port communication.
[0026] In this case, the system will automatically start the auxiliary port program to ensure data continuity and integrity. Take SPICOM1 and SPICOM2 as an example, assuming that SPICOM1 is originally responsible for reading the data of BMS slave controllers 1 to 18. If at a certain moment, BMS slave controllers 15, 16, 17, and 18 are all displayed as offline, then the system will automatically switch to SPICOM2 to specifically read the data of these four offline slave controllers.
[0027] Subsequently, the system will piece together and reorganize the data read by SPICOM1 and SPICOM2 to ensure that all data from the controller can be obtained completely and accurately. Finally, the reorganized data will be used for subsequent calculations or uploaded to a higher-level management system for further analysis and application. This design not only improves the fault tolerance of the system, but also ensures the continuity and reliability of the data.
[0028] In addition, the offline BMS slave controller number can be recorded in the following ways: The BIOS_SubNodeConnectSta[SubNode_MAXNUM] array records the connection status of the BMS slave controller. When the element in the array is "0", it means offline, and when it is "1", it means online. Create an array OffLineSubNodeREC[SubNode_MAXNUM] to record the offline BMS slave controller number: For(uint8_t i=0;i <SubNodeNum,i++) { If(BIOS_SubNodeConnectSta[i]==0) { OffLineSubNodeREC[LineOpen_SubNodeNum]=i; LineOpen_SubNodeNum++; } } At this time, the offline BMS slave controller number is recorded, and the number of offline BMS slave controllers LineOpen_SubNodeNum is also recorded.
[0029] And the following methods can be used to determine whether the offline BMS slave controller numbers are continuous: If the offline BMS slave controller numbers are continuous, such as the case where BMS slave controller No. 15 and those after No. 15 are offline in the above example, the offline BMS slave controller numbers 15, 16, 17, and 18 can be summed up, and the online BMS slave controller numbers 1 to 14 can be summed up. The sum of the two equals the sum of 1 to 18, which can determine that the offline BMS slave controller numbers are continuous.
[0030] uint8_t SPILine_OpenCount = 1; If((Sum(1,18)==Sum(OffLineSubNodeREC[0],OffLineSubNodeREC[LineOpen_SubNodeNum-1])+Sum(1,18-LineOpen_SubNodeNum)) { SPILine_OpenCount++; }else { SPILine_OpenCount--; If(SPILine_OpenCount==0) { SPILine_OpenCount=1; LineOpen_SubNodeNum=0; / / Clear memset(OffLineSubNodeREC,0,sizeof(OffLineSubNodeREC) / sizeof(OffLineSubNodeREC[0])); / / Clear } } If SPILine_OpenCount is judged to be 3 times in a row, the auxiliary port is enabled to read the BMS slave controller data after the disconnection. If SPILine_OpenCount=0, the offline BMS slave controller number and offline number information will be cleared, and the main communication port will be restored at this time.
[0031] Regarding question ②: How to reorganize the data? Currently defined: extern uint16_t V_cell_temp[CHIP_NUM][CELL_NUM]; / *18-channel cell voltage collected by the chip* / extern uint16_t T_cell_temp_AD[CHIP_NUM][TEMP_NUM]; / *The temperature AD value collected by the chip, currently collecting 4 channels of temperature* / Here, the array size CHIP_NUM will be assigned to SubNodeNum when the function is called.
[0032] First define the cache array: uint16_t V_cell_Rec[CHIP_NUM][CELL_NUM]; uint16_t T_cell_Rec_AD[CHIP_NUM][TEMP_NUM]; When it is determined that the SPI line is disconnected, the data of the master port is temporarily stored in the Rec array.
[0033] memcpy(V_cell_Rec,V_cell_temp,sizeof(V_cell_temp) / sizeof(V_cell_temp[0][0])); memcpy(T_cell_Rec_AD,T_cell_temp_AD,sizeof(T_cell_temp_AD) / sizeof(T_cell_temp_AD[0][0])); Then call the auxiliary port to collect the BMS slave controller data after the SPI line is disconnected: LTC6813_sample_update(1,LineOpen_SubNodeNum,HMI_CellNum); Get the cell voltage and module temperature data again: V_cell_temp[CHIP_NUM][CELL_NUM]; T_cell_temp_AD[CHIP_NUM][TEMP_NUM]; Insert and merge arrays V_cell_temp and V_cell_Rec: memcpy(&V_cell_Rec[SubNodeNum-LineOpen_SubNodeNum][0],V_cell_temp,2*LineOpen_SubNodeNum*CELL_NUM); The data in the cache array is copied to V_cell_temp[CHIP_NUM][CELL_NUM] and the processing ends.
[0034] memcpy(V_cell_temp,V_cell_Rec,sizeof(V_cell_temp) / sizeof(V_cell_temp[0][0])); Similarly, the temperature array: memcpy(&T_cell_Rec_AD[SubNodeNum-LineOpen_SubNodeNum][0],T_cell_temp_AD,2*LineOpen_SubNodeNum*TEMP_NUM); memcpy(T_cell_temp_AD,T_cell_Rec_AD,sizeof(T_cell_temp_AD) / sizeof(T_cell_temp_AD[0][0])); The present application also proposes a storage medium, wherein the storage medium stores at least one instruction, at least one program, code set or instruction set, and the at least one instruction, at least one program, code set or instruction set is loaded and executed by a processor to implement the aforementioned BMS daisy chain communication abnormality judgment and data reorganization method.
[0035] Among them, the readable storage medium can be a computer storage medium or a communication medium. The communication medium includes any medium that facilitates the transmission of a computer program from one place to another. The computer storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer. For example, a readable storage medium is coupled to a processor so that the processor can read information from the readable storage medium and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can be located in an application-specific integrated circuit (Application Specific Integrated Circuits, abbreviated as: ASIC). In addition, the ASIC can be located in a user device. Of course, the processor and the readable storage medium can also exist in a communication device as discrete components. The readable storage medium can be a read-only memory (ROM), a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, and an optical data storage device, etc.
[0036] In summary, the beneficial effects of this technical solution are as follows: 1. Improve data integrity: The daisy chain communication BMS data reorganization method proposed in the present invention does not destroy or change the definition and memory size of the original cache data. It only adds a new memory for recording, which is used to temporarily save the temporary data of the main communication interface. At the same time, the newly added reorganization method logic only needs to add a small piece of code to realize the function, and there is no need to trim, modify or change the original code. As long as the logic of the newly added method is tested, the original reliability performance of the BMS system can be protected. In this way, even if the communication line is interrupted, the slave controller data can be fully collected, thereby ensuring data integrity.
[0037] 2. Rapid determination of abnormality: The method for determining the continuity of the BMS slave controller numbers proposed in the present invention can quickly locate whether it is a communication abnormality fault, and can clearly identify the slave controller number position where the communication is disconnected, thereby improving the degree of automatic fault location of the system.
[0038] 3. Enhanced system stability: The BMS main controller of the present invention has two daisy chain physical interfaces. When an abnormality occurs in the main communication interface, the backup communication interface can immediately intervene in the data collection work, thereby ensuring the stable operation of the system. Compared with the prior art, this improves the stability and reliability of the battery management system, because in the prior art, if an abnormality occurs in the main communication interface, the entire system may be paralyzed and manual intervention is required to restore normality, which not only increases the complexity of operation, but also reduces the degree of automation of the system.
[0039] 4. Automatically handle abnormal situations: The method for starting a backup interface and the method for data reorganization of the present invention can automatically handle abnormal situations when they are detected without manual intervention. Compared with the prior art, this improves the automation of the system, reduces the need for manual intervention, and thus improves the convenience and efficiency of operation.
[0040] 5. Wide scope of application: The daisy chain communication BMS data reorganization method of the present invention is not only applicable to the battery management system of electric vehicles, but also applicable to other fields that adopt this communication form, such as cascade drive converter equipment, and has broad application prospects.
Claims
1. A BMS daisy chain communication abnormality determination and data reorganization method, used for a master controller and a slave controller communicating with the master controller through a master communication interface, characterized in that: The method comprises: When an offline slave controller is detected in the BMS system, the number of the offline slave controller is recorded as an offline slave controller number array, and the number of the online slave controller is recorded as an online slave controller number array; If the number of the offline slave controller is in a continuous state, it is determined that the master communication interface is in a disconnected state; The cache array obtained by the main communication interface through the slave controller is temporarily stored in the record array, the backup communication interface of the main controller is called to obtain the cache array through the slave controller, the cache array and the record array are inserted and merged and stored in the record array, and the data in the record array is stored in the cache array.
2. The method according to claim 1, characterized in that If the number of the offline slave controllers is in a continuous state, determining that the master communication interface is in a disconnected state includes: The elements in the offline slave controller number array are weighted and summed to obtain a first element weighted sum, the elements in the online slave controller number array are weighted and summed to obtain a second element weighted sum, the first element weighted sum and the second element weighted sum are weighted and summed to obtain a first weighted sum, and the natural number numbers of the slave controllers are weighted and summed to obtain a second weighted sum, If the first weighted sum is equal to the second weighted sum, it is determined that the numbers of the offline slave controllers are in a continuous state.
3. The method according to claim 1, characterized in that The cache array is used to store communication data between the master controller and the slave controller, and the communication data includes the voltage and temperature of the cells in the battery pack of the electric vehicle.
4. A BMS system, characterized in that: The BMS system uses the BMS daisy chain communication abnormality determination and data reorganization method according to any one of claims 1 to 3, the BMS system includes the master controller and at least one slave controller, and the master controller communicates with the slave controller through the master communication interface and the backup communication interface.
5. A storage medium, characterized in that: The storage medium stores at least one instruction, at least one program, a code set or an instruction set, and the at least one instruction, the at least one program, the code set or the instruction set is loaded and executed by the processor to implement the BMS daisy chain communication abnormality determination and data reorganization method as described in any one of claims 1 to 3.
Citation Information
Cited By
Data caching method and device of electric vehicle driving system and storage medium
CN121166566A
Data caching method and device of electric vehicle driving system and storage medium
CN121166566B