Battery management device and BMS data migration method

Abstract

A method for migrating battery management system (BMS) data between battery management devices according to an embodiment of the present invention comprises the steps of: receiving, by a first battery management device, a BMS data migration trigger signal and transmitting a migration preparation command to a second battery management device; reading BMS data stored in the entire address of a non-volatile memory of the first battery management device; and transmitting the BMS data stored in the non-volatile memory of the first battery management device to the second battery management device.

Description

Technical Field

[0001] This application claims priority and benefit to Korean Patent Application No. 10-2024-0062254, filed with the Korean Intellectual Property Office on May 13, 2024, the entire contents of which are incorporated herein by reference.

[0002] This invention relates to a battery management device and a method for migrating BMS data, and more particularly to a battery management device and a method for migrating BMS data between battery management devices. Background Technology

[0003] Rechargeable and reusable secondary batteries are manufactured into battery modules or battery packs by connecting multiple battery cells in series according to the output capacity required by the device, and are used as power sources for a variety of devices. These batteries are used in various fields, including small, high-tech electronic devices such as smartphones, as well as electric bicycles, electric vehicles, and energy storage systems (ESS).

[0004] A battery pack is a structure composed of multiple battery cells. If overvoltage, overcurrent, or overheating occurs in some of these cells, problems may arise in the safety and operational efficiency of the battery pack (or battery module). Therefore, the means to detect these problems are crucial. Thus, battery packs are equipped with a BMS (Battery Management System), which measures the voltage of each battery cell and monitors and controls the voltage state of the cells based on the measured values.

[0005] Simultaneously, a Battery Management System (BMS) can also be installed in energy storage systems that link renewable energy sources, batteries, and the power grid to monitor battery status, such as voltage, current, and temperature. The BMS processor uses software to perform these operations, and the BMS software needs to be copied (migrated) or updated for various reasons. In particular, efficient migration of the BMS software is required in energy storage systems with multiple battery racks installed in the field. Summary of the Invention

[0006] Technical issues

[0007] To avoid one or more problems of the prior art, embodiments of this disclosure provide a battery management device for performing BMS data migration.

[0008] To avoid one or more problems of the prior art, embodiments of this disclosure also provide a method for migrating BMS data between battery management devices.

[0009] Technical solution

[0010] To achieve the purposes of this disclosure, a battery management device is provided, configured to manage at least one battery, the battery management device comprising: a first battery management device including at least one processor; and a memory configured to store at least one instruction executed by the at least one processor.

[0011] Here, at least one instruction may include: an instruction for receiving a battery management system (BMS) data migration trigger signal and sending a migration preparation command to a second battery management device; an instruction for reading BMS data stored in the entire address of the non-volatile memory of the first battery management device; and an instruction for sending the BMS data stored in the non-volatile memory of the first battery management device to the second battery management device.

[0012] The BMS data migration trigger signal can be received via a migration trigger switch installed on the first battery management device or a user input device.

[0013] The non-volatile memory may include a first flash memory located within the controller of the first battery management device; and a second flash memory located outside the controller of the first battery management device.

[0014] The BMS data to be migrated may include at least one software binary code stored in the first flash memory; and quality assurance data and software operation-related configuration values ​​stored in the second flash memory.

[0015] At least one instruction may also include an instruction for sending a restart command to the second battery management device when the transfer of BMS data stored in the last address of the non-volatile memory of the first battery management device is completed.

[0016] The first and second battery management devices can use at least one of the Controller Area Network (CAN) and Modbus-CAN protocols to send and receive data.

[0017] According to another embodiment of this disclosure, a method for migrating battery management system (BMS) data between battery management devices may include: a first battery management device receiving a BMS data migration trigger signal and sending a migration preparation command to a second battery management device; the first battery management device reading BMS data stored in the entire address space of a non-volatile memory of the first battery management device; and the first battery management device sending the BMS data stored in the non-volatile memory of the first battery management device to the second battery management device.

[0018] The BMS data migration trigger signal can be generated by a migration trigger switch installed on the first battery management device or by a user input device.

[0019] The method may further include: receiving a migration preparation command from a first battery management device by a second battery management device; receiving BMS data from a first battery management device by a second battery management device; and storing the BMS data of the first battery management device into flash memory within the second battery management device according to each address of the BMS data.

[0020] The non-volatile memory may include: a first flash memory located within the controller of the first battery management device; and a second flash memory located outside the controller of the first battery management device.

[0021] The BMS data to be migrated may include: at least one software binary code stored in the first flash memory; and quality assurance data and software operation-related configuration values ​​stored in the second flash memory.

[0022] The method may further include: when the transmission of BMS data stored in the last address of the non-volatile memory of the first battery management device is completed, the first battery management device sends a restart command to the second battery management device.

[0023] The method may also include receiving a restart command from the first battery management device and performing a restart of the second battery management device by the second battery management device.

[0024] The first and second battery management devices can use at least one of the Controller Area Network (CAN) and Modbus-CAN protocols to send and receive data.

[0025] Beneficial effects

[0026] According to the embodiments of the present invention described above, simple BMS data migration from one BMS to another can be achieved without the need for a complex migration process using intermediate devices.

[0027] Therefore, greater efficiency in terms of cost and time savings can be expected, especially in the case of large battery systems in which multiple battery racks are used. Attached Figure Description

[0028] Figure 1 This illustrates a typical BMS software migration process.

[0029] Figure 2 An example of a battery system structure to which the present invention can be applied is shown.

[0030] Figure 3 This is a block diagram of a battery management device according to an embodiment of the present invention.

[0031] Figure 4This is a block diagram of a first BMS and a second BMS that perform BMS data migration according to an embodiment of the present invention.

[0032] Figure 5 This is a flowchart illustrating the operation of a BMS (Battery Management System) data migration method between battery management devices according to an embodiment of the present invention.

[0033] 100: Battery

[0034] 200, 200-1, 200-2: BMS

[0035] 210: Controller

[0036] 211: Internal Memory

[0037] 222: External memory

[0038] 230: Migration Trigger Switch

[0039] 210-1, 210-2: Processors

[0040] 220-1, 220-2: Memory

[0041] 250-1, 250-2: Communication modules Detailed Implementation

[0042] This invention can be modified in various forms and has various embodiments, and specific embodiments thereof are shown by way of example in the accompanying drawings and will be described in detail below. However, it should be understood that the invention is not intended to be limited to these specific embodiments, but rather, the invention should cover all modifications, equivalents, and substitutions falling within the spirit and scope of the invention. Throughout the description of the drawings, the same reference numerals refer to the same elements.

[0043] It should be understood that although terms such as first, second, A, B, etc., may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element may be referred to as a second element without departing from the scope of the invention, and similarly, a second element may be referred to as a first element. As used herein, the term "and / or" includes a combination of or any of the associated listed items.

[0044] It should be understood that when a component is described as "coupled" or "connected" to another component, it can be directly coupled or connected to the other component, or there may be intermediate components. Conversely, when a component is described as "directly coupled" or "directly connected" to another component, there are no intermediate components.

[0045] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the invention. As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the terms “comprising,” “including,” “containing,” “covering,” and / or “having,” when used herein, specify the presence of stated features, integers, steps, operations, constituent elements, components, and / or combinations thereof, but do not preclude the presence or addition of one or more other features, integers, steps, operations, constituent elements, components, and / or combinations thereof.

[0046] Unless otherwise defined, all terms used herein, including technical and scientific terms, shall have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains. It should also be understood that terms such as those defined in common dictionaries shall be interpreted as having the meaning consistent with their meaning in the context of the relevant field and shall not be interpreted in an idealized or overly formal sense unless so explicitly defined herein.

[0047] Some of the terms used in this article are defined as follows.

[0048] A battery cell is a basic unit used to store electricity, while a battery pack is an assembly in which multiple battery cells are electrically connected.

[0049] A battery rack is a system of single structures assembled by electrically connecting modular units configured by the battery manufacturer, and can be monitored and controlled by a battery management system (BMS). A battery rack may include multiple battery modules as well as battery protection units or any other protection devices.

[0050] A battery bank refers to a large system of battery racks configured by connecting multiple battery racks in parallel. A battery bank BMS can monitor and control several BMSs, each managing one battery rack.

[0051] In the following, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

[0052] Figure 1 This illustrates a typical BMS software migration process.

[0053] In sites where energy storage systems are installed, it may be necessary to replace the battery management system (BMS) deployed and operated in each battery pack or rack for various reasons. For example, if a battery pack, rack, or corresponding BMS is damaged due to fire or other damage, the damaged battery and / or BMS needs to be replaced with another battery and / or BMS.

[0054] When a problem occurs in the BMS used and operated in the battery system, and it is necessary to replace the BMS with another BMS, it is necessary to copy and transfer information such as software binary code, warranty data, operating software related data, and other necessary information (fault occurrence history, etc.) stored in the non-volatile memory (e.g., flash memory) of the operating BMS to the newly installed BMS.

[0055] Typically, BMS data migration is performed through a separate intermediate device. Figure 1 An example of a method for migrating BMS data from BMS #A to BMS #B using intermediate device 20 is shown. The intermediate device can be a computing device (e.g., a personal computer (PC)).

[0056] The intermediate device 20 is equipped with a migration tool for BMS data migration. Furthermore, the intermediate device 20 is connected to BMS#A or BMS#B and can communicate with BMS#A or BMS#B using the CAN communication protocol.

[0057] refer to Figure 1 In step 1, intermediate device 20 connects to BMS #A 10, and the migration tool in intermediate device 20 reads the BMS data stored in BMS #A 10 via CAN communication. Here, the data read by the migration tool is information stored in the flash memory of BMS #A.

[0058] In step 2, the migration tool of intermediate device 20 stores the BMS #A data read from the flash memory of BMS #A 10 into the internal storage device.

[0059] In step 3, the migration tool of intermediate device 20 connects to BMS #B and uses the CAN protocol to send the internally stored BMS data to BMS #B.

[0060] As described, the general method for copying BMS data is to use an intermediate device to read and store the BMS data stored in the non-volatile memory of BMS #A, and then send the BMS data stored in the intermediate device to BMS #B. This approach not only requires a separate intermediate device equipped with migration tools, but also presents the inconvenience of a cumbersome three-step process from the user's perspective. Furthermore, the burden of developing and installing migration tools also arises.

[0061] Therefore, the present invention provides a BMS data migration method that does not require a separate intermediate device for BMS data migration, and a battery management device using the method.

[0062] Figure 2 An example of a battery system structure to which the present invention can be applied is shown.

[0063] exist Figure 2 In the battery system, multiple battery packs can be included in the battery rack, and multiple battery racks can be included in the battery library. Figure 2 The battery system shown may be part of an energy storage system.

[0064] Here, the battery management system (BMS) can be installed in each of the battery packs, battery racks, and battery compartments. Figure 1 In a battery pack, multiple battery cells can be configured to be connected in series. These cells can be connected to a load via positive and negative terminals and can perform charging / discharging operations. The most commonly used battery cells are lithium-ion (Li-Ion) cells. A battery management system (BMS) can be installed in each of these battery packs.

[0065] A battery management system (BMS) can monitor the current, voltage, and temperature of each battery pack it manages, calculate the state of charge (SOC) based on the monitoring results, and control charging and discharging. Here, SOC can be the current state of charge of the battery, expressed as a percentage [%].

[0066] To perform such operations, a BMS can include various components such as fuses, current sensing elements, thermistors, switches, and balancers, and in most cases, it includes a microcontroller unit (MCU) or a battery monitoring integrated chip (BMIC) to connect to and control them. Here, the BMIC can be an IC-type component located inside the BMS that measures information such as voltage, temperature, and current of the battery cells / modules.

[0067] Simultaneously, each rack-based battery management system (RBMS) can manage each individual battery rack, and the battery bank management system (BBMS) can control the entire battery bank, including these racks, as a whole. Each RBMS can monitor the current, voltage, and temperature of each battery rack and calculate the state of charge (SOC) based on the monitoring results, controlling charging and discharging. Multiple rack-based BMSs can be connected to the battery system controller (or battery section controller; BSC), and the battery system controller can manage and control the entire battery system. Figure 1 In the embodiments described, the library BMS (BBMS) is shown to perform the same functions as the BSC, and depending on the system, it may be referred to as BBMS or BSC.

[0068] The BMS can also monitor individual battery cells, read their voltages, and transmit them to other systems connected to the battery. To this end, the BMS can include communication modules for communicating with other systems within the device, including the battery system. The BMS's communication modules can communicate with other systems within the device using a Controller Area Network (CAN). Components, modules, or systems within the BMS are interconnected via a CAN bus.

[0069] According to an embodiment of the present invention, the battery management device (BMS) may be one of a battery system controller (BSC) / library BMS (BBMS) that manages the entire battery library, a rack BMS that is connected to the BSC / BBMS and manages each battery rack, and a group BMS that is connected to the rack BMS and manages each battery pack.

[0070] Figure 3 This is a block diagram of a battery management device according to an embodiment of the present invention.

[0071] According to embodiments of the present invention, the battery management device 200 may be a group BMS for managing and controlling battery packs, a rack BMS for managing and controlling battery shelves, or a library BMS for managing and controlling battery storage. In other words, the batteries managed and controlled by the battery management device 200 may be battery packs (or battery modules), battery shelves, or battery storage.

[0072] refer to Figure 3 According to an embodiment of the present invention, the battery management device 200 may include a controller 210 and a migration trigger switch 230. The migration trigger switch 230 can generate a BMS data migration trigger signal through user or administrator operation and provide the generated BMS data to the controller 210. Meanwhile, the device generating the migration trigger signal can be implemented in the form of a switch, but it can also be provided on the BMS operation / touch panel or user interface in the form of an input button, menu, etc.

[0073] According to embodiments, in this specification, a controller may be referred to as a processor, controller, microcontroller (MCU), etc., and may also refer to a dedicated processor that performs the methods according to embodiments of the present invention.

[0074] The controller 210 may also refer to a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor that performs the methods according to embodiments of the present invention.

[0075] The controller 210 may include non-volatile memory (internal memory) 211. In one embodiment, the internal memory 211 of the controller 210 may be flash memory. Software (e.g., applications) for the operation of the battery management device 200 may be stored in the internal memory 211 of the controller 210. A bootloader may also be stored in the internal memory 211 of the controller 210 for booting the battery management system 200.

[0076] In another embodiment, the internal memory 211 of the controller 210 may be a programmable read-only memory (ROM). The programmable ROM may be, for example, an electrically erasable programmable ROM (EEPROM).

[0077] In addition to the internal memory 210 in the controller 210, the battery management device 200 may also include a separate external memory 222, such as non-volatile memory. In one embodiment, the external memory 222 may be a programmable ROM or flash memory.

[0078] External storage 222 can store configuration values ​​that determine the operation of the software, such as the number of battery packs, diagnostic thresholds, and fault occurrence history. External storage 222 can also store warranty data.

[0079] Figure 4 This is a block diagram of a first BMS and a second BMS that perform BMS data migration according to an embodiment of the present invention.

[0080] exist Figure 4 In this context, BMS #A (the first BMS) is the BMS that stores the BMS data to be copied, while BMS #B (the second BMS) is the BMS that replaces BMS #A and receives the BMS data copied from BMS #A.

[0081] According to an embodiment of the present invention, BMS #A (200-1) may include a processor 210-1, a memory 220-1 storing at least one command executed by the processor, and a communication module 250-1.

[0082] Here, memory 220-1 can be as follows: Figure 3 One of the internal memory 211 and the external memory 222 can be seen. The memory 220-1 may also include a portion of the internal memory 211 or a portion of the external memory 222, or it may include a portion of the internal memory 211 and a portion of the external memory 222.

[0083] BMS #B (200-2), which receives and uses copied BMS data from BMS #A (200-1), may also include a processor 210-2, a memory 220-2 storing at least one command executed by the processor, and a communication module 250-2.

[0084] Here, memory 220-2 can be as follows: Figure 3 One of the internal memory 211 and the external memory 222 can be seen. The memory 220-2 may also include a portion of the internal memory 211 or a portion of the external memory 222, or may include a portion of the internal memory 211 and a portion of the external memory 222.

[0085] Meanwhile, BMS #A (200-1) may additionally include a migration trigger switch 230-1. Furthermore, the present invention can be implemented using a migration trigger signal input by a user / administrator via a user interface panel, etc., without including a migration trigger switch 230-1. The migration trigger signal generated by the migration trigger switch 230-1 or the user interface panel can be provided to the controller 210-1.

[0086] Figure 4 The reason why BMS #B (200-2) is shown as not including the migration trigger switch is because, in Figure 4 In one embodiment, BMS #B (200-2) is the BMS of the BMS data to be migrated. In other words, in another embodiment, BMS #B (200-2) may also be configured to include a migration trigger switch, and BMS #B (200-2) may copy and transfer the BMS data of BMS #B to another BMS.

[0087] BMS #A (200-1) and BMS #B (200-2) can communicate with each other using the CAN and Modbus-CAN protocols. CAN communication is a standard communication standard designed to enable microcontrollers or devices to communicate with each other without a host. CAN communication is a message-based network protocol of the non-host bus type, primarily used for communication between controllers. Modbus-CAN is a modification of the Modbus protocol that operates on the CAN bus. Modbus-CAN enables communication between devices on the CAN bus network, thereby achieving distributed control and monitoring of equipment in automotive and industrial environments.

[0088] More specifically, BMS #A (200-1) may be a first battery management device and may include a processor, a memory storing at least one instruction executed by the processor, and a migration trigger switch providing a BMS data migration trigger signal to the processor.

[0089] At least one instruction may include: an instruction for receiving a battery management system (BMS) data migration trigger signal and sending a migration preparation command to a second battery management device; an instruction for reading BMS data stored in the entire address of the non-volatile memory of the first battery management device; and an instruction for sending the BMS data stored in the non-volatile memory of the first battery management device to the second battery management device.

[0090] Here, the non-volatile memory may include a first flash memory located within the controller of the first battery management device; and a second flash memory located outside the controller of the first battery management device.

[0091] Here, the copied BMS data may include at least one software binary code stored in the first flash memory; and quality assurance data and software operation-related configuration values ​​stored in the second flash memory.

[0092] In addition, at least one instruction may also include an instruction for sending a restart command to the second battery management unit when the transfer of BMS data stored in the last address of the non-volatile memory of the first battery management device is completed.

[0093] Meanwhile, BMS #B (200-2) may be a second battery management device, which may include a processor and a memory storing at least one instruction executed by the processor.

[0094] Here, when the second battery management device receives a migration preparation command from the first battery management device, the second battery management device can prepare to receive BMS data from the first battery management device. Subsequently, the second battery management device can receive the BMS data from the first battery management device and store the BMS data in the flash memory of the second battery management device at the address corresponding to the address where the BMS data was initially stored in the first battery management device (BMS #A). In other words, data stored in the internal memory of the first battery management device can be stored at the corresponding address in the internal memory of the second battery management device, and data stored in the external memory of the first battery management device can be stored at the corresponding address in the external memory of the second battery management device.

[0095] Simultaneously, the second battery management device can perform a reboot upon receiving a reboot command from the first battery management device. A bootloader for starting the battery management device can be stored in the internal memory of the processor of the second battery management device. Upon reboot, the second battery management device can perform a reboot by operating the bootloader. Operations performed during reboot may include, for example, initializing its operating system (OS) and hardware, reading BMS configuration-related values ​​stored in external flash memory, and performing BMS operations. Here, BMS configuration-related values ​​may include settings and related information for various components included in the BMS (various sensors, fans, BMICs, etc.).

[0096] Figure 5 This is a flowchart illustrating the operation of a BMS (Battery Management System) data migration method between battery management devices according to an embodiment of the present invention.

[0097] refer to Figure 5 When the first battery management device receives the BMS data migration trigger signal (Yes in S510), the first battery management device can send a migration preparation command to the second battery management device (S520). Here, in Figure 5In the case of the embodiment, a switch is used as an example of a device for generating a migration trigger signal, but the migration trigger signal generating device may also be provided on the operation / touch panel or user interface of the battery management device in the form of an input button, menu, etc.

[0098] Furthermore, the first battery management device can sequentially read BMS data stored in its non-volatile memory across the entire address range (S511) and send a software data write command to the second battery management device (S521). The BMS data write command can be repeatedly executed on the data stored at the last address of the non-volatile memory of the first battery management device (S512). In other words, all BMS data stored in the non-volatile memory of the first battery management device can be copied and sent to the second battery management device.

[0099] Meanwhile, when the second battery management device receives a migration preparation command from the first battery management device (Yes in S530), the second battery management device can sequentially receive BMS data from the first battery management device and write the received BMS data to the flash memory in the second battery management device according to each address (S531).

[0100] When the transfer of data stored at the last address of the non-volatile memory of the first battery management device is completed, the first battery management device may send a restart command to the second battery management device (S522).

[0101] When the second battery management device receives a restart command from the first battery management device (Yes in S532), the second battery management device can perform a restart (S533). After restarting, the second battery management device can initialize, for example, the OS (operating system) and hardware, read BMS configuration-related values ​​stored in external flash memory, and perform BMS operations. Here, the BMS configuration-related values ​​may include parameters and related information of various components included in the BMS (various sensors, fans, BMICs, etc.).

[0102] According to the embodiments of the present invention described above, a simple BMS data migration can be performed from one battery management device to another without the need for a complex multi-stage migration process using intermediate equipment.

[0103] The operation of the method according to embodiments of the present invention can be implemented as a computer-readable program or code on a computer-readable recording medium. The computer-readable recording medium includes all types of recording devices that store data readable by a computer system. Furthermore, the computer-readable recording medium can be distributed across networked computer systems to store and execute computer-readable programs or code in a distributed manner.

[0104] Furthermore, computer-readable recording media can include hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, and flash memory. Program instructions can include not only machine language code, such as code generated by a compiler, but also high-level language code that can be executed by a computer using an interpreter or similar tool.

[0105] Although some aspects of the invention have been described in the context of apparatus, they may also refer to, according to the description of the corresponding method, blocks or devices corresponding to method steps or features of method steps. Similarly, aspects described in the context of a method may also refer to features of corresponding blocks or items or corresponding devices. Some or all of the method steps may be executed by (or using) hardware devices such as, for example, microprocessors, programmable computers, or electronic circuits. In some embodiments, one or more of the most important method steps may be executed by such devices.

[0106] In the foregoing, the present invention has been described with reference to exemplary embodiments thereof; however, those skilled in the art will appreciate that various corrections and modifications may be made to the present invention without departing from the spirit and scope of the invention as described in the appended claims.

Claims

1. A first battery management device configured to manage at least one battery, the first battery management device comprising: at least one processor; and a memory configured to store at least one instruction executed by the at least one processor, wherein the at least one instruction comprises: an instruction to receive a BMS data migration trigger signal and send a migration preparation command to a second battery management device; an instruction to read BMS data stored in an entire address of a non-volatile memory of the first battery management device; and an instruction to send the BMS data stored in the non-volatile memory of the first battery management device to the second battery management device. The BMS data migration trigger signal is received through a migration trigger switch or a user input device installed on the first battery management device.

2. The first battery management device of claim 1, wherein, The non-volatile memory comprises:

3. The first battery management device of claim 1, wherein, a first flash memory located within a controller of the first battery management device; and a second flash memory located outside the controller of the first battery management device. The BMS data to be migrated comprises:

4. The first battery management device of claim 3, wherein, at least one software binary code stored in the first flash memory; and quality assurance data and software operation related configuration values stored in the second flash memory. The at least one instruction further comprises:

5. The first battery management device of claim 1, wherein, an instruction to send a restart command to the second battery management device when the transmission of BMS data to a last address of the non-volatile memory of the first battery management device is completed. The first battery management device and the second battery management device use at least one of CAN and Modbus-CAN protocol to send and receive data.

6. The first battery management device of claim 1, wherein, 7. A method of migrating BMS data between battery management devices, the method comprising: receiving, by a first battery management device, a BMS data migration trigger signal and sending a migration preparation command to a second battery management device; reading, by the first battery management device, BMS data stored in an entire address of a non-volatile memory of the first battery management device; and sending, by the first battery management device, the BMS data stored in the non-volatile memory of the first battery management device to the second battery management device. The BMS data migration trigger signal is generated by a migration trigger switch or a user input device installed on the first battery management device.

8. The method of claim 7, wherein, 9. The method of claim 7, further comprising: receiving, by the second battery management device, the migration preparation command from the first battery management device; receiving, by the second battery management device, the BMS data from the first battery management device; and storing, by the second battery management device, the BMS data of the first battery management device into a flash memory within the second battery management device according to each address of the BMS data. The non-volatile memory comprises:

10. The method of claim 7, wherein, a first flash memory located within a controller of the first battery management device; and a second flash memory located outside the controller of the first battery management device. ​ 11. The method of claim 10, wherein, The BMS data to be migrated includes: at least one software binary code stored in the first flash memory; and quality assurance data and software operation related configuration values stored in the second flash memory.

12. The method of claim 7, further comprising: sending, by the first battery management device, a restart command to the second battery management device when the transfer of the BMS data stored to the last address of the non-volatile memory of the first battery management device is completed.

13. The method of claim 12, further comprising: receiving, by the second battery management device, the restart command from the first battery management device and performing a restart of the second battery management device.

14. The method of claim 7, wherein, The first battery management device and the second battery management device use at least one of CAN and Modbus-CAN protocols to send and receive data.

Images