Battery management device and method for operating battery management device

Abstract

A method for operating a battery management device according to an embodiment of the present invention may include: reading update information of a battery management system (BMS) software-related setting value among BMS software-related data stored in a non-volatile memory of the battery management device when the battery management device is activated; comparing the update information of the BMS software related setting value with an update related value defined in the BMS software; and determining that the BMS cannot operate if the update information of the BMS software-related setting value does not match the update-related value defined in the software.

Description

Technical Field

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

[0002] This invention relates to a battery management device and its operating method, and more specifically to a battery management device and operating method related to BMS software settings information. Background Technology

[0003] As rechargeable and reusable secondary batteries, they 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 various devices. These batteries are used in a variety of 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, the safety and operational efficiency of the battery pack may be compromised. Therefore, means to detect these problems are necessary. 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 grid to monitor battery status, such as voltage, current, and temperature. The BMS processor uses software to perform these operations and requires defining the BMS configuration settings necessary for the software to function.

[0006] However, if the BMS configuration settings are not defined in the battery management system or if the battery management system stores configuration settings that do not correspond to the current BMS software version, the battery management system may malfunction. Summary of the Invention

[0007] Technical issues

[0008] To eliminate one or more problems of the related technologies, embodiments of this disclosure provide a battery management device.

[0009] To eliminate one or more problems in the related art, embodiments of this disclosure also provide a method for operating a battery management device related to BMS software settings information.

[0010] Technical solution

[0011] To achieve the objectives of this disclosure, a battery management device may include: 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 may include: instructions for reading update information of battery management system (BMS) software-related setting values ​​stored in the non-volatile memory of the battery management device upon startup; instructions for comparing the update information of the BMS software-related setting values ​​with update-related values ​​defined in the BMS software; and instructions for determining that the battery management device cannot operate when the update information of the BMS software-related setting values ​​does not match the update-related values ​​defined in the software.

[0012] Update-related values ​​defined in the BMS software are set to constant values ​​in the BMS software code.

[0013] At least one instruction may also include an instruction for performing normal operation of the battery management device when update information of the BMS software related setting values ​​matches update-related values ​​defined in the BMS software.

[0014] Instructions for performing normal operation of the battery management device include: instructions for reading one or more BMS software-related setting values ​​stored in non-volatile memory; and instructions for interpreting one or more BMS software-related setting values ​​according to the BMS software MAP.

[0015] Additionally, at least one instruction may include: an instruction for sequentially writing BMS software-related setting values ​​to non-volatile memory in BMS setting value input mode; and an instruction for recording update-related values ​​defined in the BMS software as update information of BMS software-related setting values ​​in non-volatile memory when one or more normal recordings are completed for all addresses of the non-volatile memory.

[0016] The non-volatile memory may include a first non-volatile memory that stores BMS software and update-related values, and the first non-volatile memory is located inside the processor.

[0017] The non-volatile memory may further include a second non-volatile memory that stores update information of BMS software-related settings and one or more BMS software-related settings, and the second non-volatile memory is located outside the processor.

[0018] According to another embodiment of this disclosure, an operation method of a battery management device may include: when the battery management device is started, reading update information of BMS software-related setting values ​​from the battery management system (BMS) software-related data stored in the non-volatile memory of the battery management device; comparing the update information of the BMS software-related setting values ​​with update-related values ​​defined in the BMS software; and if the update information of the BMS software-related setting values ​​does not match the update-related values ​​defined in the software, determining that the battery management device cannot operate.

[0019] Update-related values ​​defined in the BMS software can be set to constant values ​​in the BMS software code.

[0020] The operation method of the battery management device may also include: when the update information of the relevant setting value of the BMS software matches the update-related value defined in the BMS software, the normal operation of the battery management device is performed.

[0021] Performing normal operations of the battery management device may include: reading one or more BMS software-related settings stored in non-volatile memory; and interpreting one or more BMS software-related settings based on the BMS software's MAP.

[0022] The operation method of the battery management device may further include: when the battery management device is determined to be inoperable, entering the BMS setting value input mode; sequentially writing the BMS software-related setting values ​​to the non-volatile memory; and if one or more normal recordings are completed for all addresses of the non-volatile memory, recording the update-related values ​​defined in the BMS software as update information of the BMS software-related setting values ​​in the non-volatile memory.

[0023] Meanwhile, the non-volatile memory may include a first non-volatile memory that stores BMS software and update-related values, and the first non-volatile memory is located inside the processor.

[0024] In addition, the non-volatile memory may also include a second non-volatile memory that stores update information of BMS software-related settings and one or more BMS software-related settings, and the second non-volatile memory is located outside the processor.

[0025] Beneficial effects

[0026] According to the embodiments of the present invention described above, even when no BMS setting information is defined in the battery management device or when BMS setting information that does not correspond to the current BMS software version is stored in the battery management device, the battery management device can be prevented from malfunctioning by using the update information of the relevant setting values ​​of the BMS software to determine whether the battery management device can operate normally. Attached Figure Description

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

[0028] Figure 2 A block diagram illustrating a battery management device for BMS software updates is shown.

[0029] Figure 3 An example of a data identification error that may occur during a typical BMS software update process is shown.

[0030] Figure 4 An example of a BMS operation concept in a software update process according to an embodiment of the present invention is shown.

[0031] Figure 5 An operational sequence is shown when the battery management device is normally activated according to an embodiment of the present invention.

[0032] Figure 6 An operation sequence is shown when the battery management device operates in BMS setting value input mode according to an embodiment of the present invention.

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

[0034] 100: Battery

[0035] 200: Battery Management Device

[0036] 210: Controller

[0037] 211: First Memory

[0038] 222: Second memory

[0039] 250: Communication Unit

[0040] 270: User Interface Detailed Implementation

[0041] 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 the specific embodiments, but rather, the invention is intended to cover all modifications, equivalents, and substitutions falling within the spirit and technical scope of the invention. Throughout the description of the accompanying drawings, similar reference numerals refer to similar elements.

[0042] 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, and similarly, a second element may be referred to as a first element, without departing from the scope of the invention. As used herein, the term "and / or" includes a combination of a plurality of associated listed items or any one of a plurality of associated listed items.

[0043] It should be understood that when a component is described as being “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 being “directly coupled” or “directly connected” to another component, there are no intermediate components.

[0044] 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 also intended to include the plural forms unless the context clearly indicates otherwise. It will be further understood that the terms “comprising,” “including,” “containing,” “comprise,” and / or “having” as 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.

[0045] Unless otherwise defined, all terms used herein, including technical and scientific terms, 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 should be interpreted as having the same meaning as their meaning in the context of the relevant field, and will not be interpreted in an idealized or overly formal sense unless expressly defined herein.

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

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

[0048] A battery rack is a single-structure system assembled via electrical connections of modules provided by the battery manufacturer, and can be monitored and controlled by a battery management system (BMS). A battery rack may include multiple battery packs (modules) and battery protection units or any other protection devices.

[0049] 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, with each BMS managing a battery rack.

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

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

[0052] exist Figure 1 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 1 The battery system shown can be part of an energy storage system.

[0053] 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. Each battery cell can be connected to a load via positive and negative terminals and can perform charging / discharging operations. The most commonly used battery cell is the lithium-ion (Li-ion) battery cell. A battery management system (BMS) can be installed in each of these battery packs.

[0054] 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 [%].

[0055] To perform such operations, a BMS can include various components such as fuses, current sensing elements, thermistors, switches, and equalizers, 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 the voltage, temperature, and current of individual battery cells / modules.

[0056] 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. 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 to control charging and discharging. Multiple rack-based BMSs can be connected to a battery system controller (or battery segment controller; BSC), and the battery system controller can manage and control the entire battery system. Figure 1 In some embodiments, the library BMS (BBMS) is shown to perform the same functions as the BSC, and may be referred to as BBMS or BSC depending on the system.

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

[0058] According to an embodiment of the present invention, the battery management device (BMS) may be one of a battery system controller (BSC) / BBMS that manages the entire battery bank, 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.

[0059] Figure 2 A block diagram illustrating a battery management device for BMS software updates is shown.

[0060] As previously Figure 1 As discussed herein, battery management device 200 monitors and manages battery 100. Here, battery can refer to various types of battery components, such as battery packs (modules), battery racks, and battery banks. Battery management device 200 may include processor 210 and memories 211, 222, and may additionally include various components and circuits, such as battery monitoring circuitry (e.g., a battery monitoring integrated chip (BMIC)), although not shown for convenience.

[0061] Meanwhile, the battery management device 200 may include non-volatile memory (internal memory) 211 within the processor 210. In one embodiment, the internal memory 211 of the processor 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 processor 210. A bootloader may also be stored in the internal memory 211 of the processor 210 for booting the battery management device 200.

[0062] In addition to the internal memory 211 in the processor 210, the battery management device 200 may also include a separate external memory 222, such as non-volatile memory. The external memory 222 may store BMS settings that determine the operation of the BMS software, such as the number of battery packs, diagnostic thresholds, fault occurrence history, etc. The external memory 222 may also store warranty data.

[0063] Meanwhile, the battery management device requires software updates for various reasons, such as functional improvements and the addition of new features. In this invention, software updates can include the concepts of software upgrades and downgrades. The processor 210 can receive software update commands and new software from an external device. In one embodiment, the external device can receive new software from a computing device connected via a network.

[0064] In response to a software update command, processor 210 can overwrite the area in internal memory 211 where existing software is stored with new software 222. According to one embodiment, the processor can erase existing software from internal memory 211 and write new software. In some embodiments, the processor can perform a reset and jump to the boot loader to write new software to internal memory 211. Therefore, existing software can be deleted from internal memory 210, and new software can be written, enabling software updates.

[0065] When booting with new software, processor 210 can load and operate the software using configuration values ​​that determine its operation stored in external memory 222. Processor 210 can use a software MAP that defines configuration setting (NV: non-volatile) values ​​to interpret data (e.g., binary data) related to the BMS configuration setting values ​​stored in external memory 222. Simultaneously, the BMS software MAP can be stored in the software along with the BMS software.

[0066] Figure 3 An example of a data identification error that may occur during a typical BMS software update process is shown.

[0067] In having Figure 2 In the configured battery management device, when a typical software update is performed, the battery management device starts up and performs battery management operations based on the new software recorded in the internal memory 211.

[0068] Here, the processor 210 can use the software MAP to interpret and determine the setting values ​​for the operation of the BMS software and perform related operations. The BMS software-related setting values ​​35 used to determine the operation of the BMS software may include, for example, the number of battery packs, diagnostic thresholds, and fault occurrence history.

[0069] refer to Figure 3 For example, when the software version 30 before the update was 1.0.0.0, it can be seen that MAP 33 was defined according to version 1.0.0.0 in the order of "Group Count (unit8_t)", "OVF (Overvoltage Fault) Detection (unit16_t)", "OVF Release (unit16_t)", "UVF (Undervoltage) Detection (unit16_t)", and "UVF Release (unit16_t)".

[0070] Additionally, the BMS software-related setting values ​​35 stored in the external non-volatile memory are "Group Count = 16", "OVF (Overvoltage Fault) Detection = 38000", "OVF Release = 36000", "UVF (Undervoltage Fault) Detection = 29000", and "UVF Release = 29500". The processor can interpret the BMS software-related setting values ​​35 according to the defined MAP 33. Here, the BMS software-related setting values ​​35 can be stored in bundles by category (e.g., voltage diagnostic related, current diagnostic related, etc.) for each piece of data in the external non-volatile memory 222 area.

[0071] At the same time, if Figure 3 If the update is performed and the new software version 30 is changed to 1.0.0.1, the new software can interpret the values ​​set in external memory according to the software MAP 33-1 defined according to version 1.0.0.1. In other words, the processor 210 reads the same binary data as before the software update, but interprets the corresponding data according to the new software MAP, thus the processor obtains a completely different interpretation result than before the update.

[0072] refer to Figure 3 The updated data interpretation, according to the new software's MAP 33-1, includes relevant data defined in the order of "Fan Type," "Group Count," "OVF (Overvoltage Fault) Detection," "OVF Release," and "UVF (Undervoltage Fault) Detection." Therefore, if binary data related to BMS software settings previously stored in non-volatile memory is interpreted according to the order defined in MAP 33-1, data distortion (35') occurs.

[0073] To address this problem, the present invention can store information about the number of times information recorded in non-volatile memory has been updated in the event of software updates, and use the stored information about the number of updates to prevent data distortion and prevent BMS failures.

[0074] Figure 4 An example of a BMS operation concept in a software update process according to an embodiment of the present invention is shown.

[0075] exist Figure 4 In the example, if the software version 30 before the update is 1.0.0.0, then MAP 33 of version 1.0.0.0 is defined in the order of "Group Count (unit8_t)", "OVF (Overvoltage Fault) Detection (unit16_t)", "OVF Release (unit16_t)", "UVF (Undervoltage Fault) Detection (unit16_t)" and "UVF Release (unit16_t)".

[0076] The processor of the battery management device according to an embodiment of the present invention can interpret the BMS software-related setting values ​​35 according to the predefined MAP 33. Furthermore, according to an embodiment of the present invention, update information (NV revision) 410 of the BMS software-related setting values ​​can be stored in memory. Here, the update information of the BMS software-related setting values ​​can refer to the number of times the BMS software-related setting values ​​have been updated and recorded. Here, according to one embodiment, the update information (NV revision) 410 of the BMS software-related setting values ​​can be stored in external memory 222.

[0077] Furthermore, according to embodiments of the present invention, the setting value update information 310 can be included in the BMS software in the form of a constant value. A constant value defined in such software can be understood as a text value explicitly defined in the software code (fixed in the source code). For example, whenever new software is developed, the software developer can change and set the constant value (increasing the value proportionally to the version).

[0078] For example, if the BMS is initially manufactured in the factory and the setting value is recorded once, the setting value update information 410 can be recorded as "1 (0x01)", such as Figure 4 As shown in the image. Then, if as... Figure 4 If a software update is performed and software version 30 is changed to 1.0.0.1, then the update information 310', which is defined as a constant in the changed software, is also changed to "0x02".

[0079] However, even if the new software is stored in the internal memory according to the software update command, the existing settings values ​​previously recorded / stored for BMS software operations remain unchanged. Therefore, the update information (NV revision) 410 of the BMS software-related settings values ​​stored in the non-volatile memory is still maintained as "1 (0x01)".

[0080] According to an embodiment of the present invention, in the case where a value (Ox01) different from the update constant (Ox02) defined in the software is stored in non-volatile memory as update information of the BMS software-related setting value, the processor of the battery management device can determine that the value is not expected by the user and determine that the BMS cannot operate.

[0081] Figure 5 An operational sequence is shown when the battery management device is normally activated according to an embodiment of the present invention.

[0082] When the battery management device is normally started, for example, when the battery management device installed in the energy storage system (ESS) field is started and begins operation, the processor 210 can read update information of BMS software-related setting values ​​stored in the non-volatile memory (S510). Here, the non-volatile memory can be a memory located outside the processor 210. The non-volatile memory can also be flash memory.

[0083] According to one embodiment, the process by which processor 210 reads update information of BMS software-related setting values ​​stored in non-volatile memory may include a detailed process of reading all data stored in non-volatile memory and extracting update information of BMS software-related setting values ​​from the data. Meanwhile, according to another embodiment, processor 210 may first read data at at least one address of the storage update information (written in a designated area in memory) from the entire data stored in non-volatile memory. Here, the update information of BMS software-related setting values ​​stored in non-volatile memory may be stored in memory at a first address from all data stored in non-volatile memory.

[0084] The processor can compare the update information of BMS software-related settings recorded in non-volatile memory (NV data on flash memory) with the update constants defined in the software (constants defined in the SW) to determine whether the two values ​​are the same (S520). Here, the update-related values ​​defined in the BMS software can be set to constant values ​​in the BMS software code.

[0085] If the two values ​​are the same, the processor can perform normal operation according to the BMS software (S530). When the battery management device is operating normally, it can read one or more BMS software-related setting values ​​stored in the non-volatile memory, and can interpret one or more BMS software-related setting values ​​according to the MAP of the BMS software.

[0086] Meanwhile, if the update information of the BMS software-related settings recorded in the non-volatile memory is different from the update constant defined in the software, the processor can determine that the unexpected value is stored in the non-volatile memory and process it as BMS inoperability (S540).

[0087] More specifically, during normal operation (S530), the battery management device can perform overall BMS functions such as current data updates, diagnostics, cell balancing, and charging / discharging of the battery pack (module).

[0088] On the other hand, if the BMS is processed as inoperable (S540), the battery management device can enter the BMS setting value input mode (e.g., factory mode). The battery management device can then perform normal BMS operation after executing the process of recording the BMS setting value in the non-volatile memory through the BMS setting value input mode.

[0089] Figure 6 An operation sequence is shown when the battery management device operates in BMS setting value input mode according to an embodiment of the present invention.

[0090] In BMS setting value input mode (e.g., factory mode), setting values ​​such as "group count", "OVF (overvoltage fault) detection", "OVF release", "UVF (undervoltage fault) detection", and "UVF release" can be written sequentially to non-volatile memory. The BMS software setting values ​​written to non-volatile memory can be defined such that, for example, NV_Value[0] represents the group count setting value, NV_Value[1] represents the OVF detection value, and NV_Value[2] represents the OVF release value.

[0091] refer to Figure 6 As a preparatory step, the variable i associated with the BMS setting value is initialized to "0" (S610). Then, the NV value of the NV_Value[i] category is written to non-volatile memory (S620), and the corresponding NV value is verified (SET) (S630). It can be checked whether the NV value of the NV_Value[i] category is valid (S640), and if invalid, the writing and verification are reprocessed (S640 is no).

[0092] If the corresponding NV_Value[i] category value is valid, the value of variable i is incremented (S651), and a write (S620) and verification (SET) operation (S630) is performed for each category. The write (S620) and verification (SET) operation (S630) is performed for each category until the last set value to be written is reached (S650).

[0093] When one or more normal writes are completed for all addresses of the non-volatile memory, the processor can write an update information (NV data on flash memory) to the BMS software-related settings of the non-volatile memory (S660) with a value equal to the update constant defined in the software (the constant defined in SW).

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

[0095] A battery management device 200 according to an embodiment of the present invention may include: a controller 210; and a memory storing at least one instruction executable by a processor. Here, the memory may include... Figure 7 At least one of the first memory 211 and the second memory 222.

[0096] Here, at least one instruction may include: an instruction for reading update information of battery management system (BMS) software-related settings stored in the non-volatile memory of the battery management device at startup; an instruction for comparing the update information of the BMS software-related settings with update-related values ​​defined in the BMS software; and an instruction for determining that the battery management device cannot operate when the update information of the BMS software-related settings does not match the update-related values ​​defined in the software.

[0097] Update-related values ​​defined in the BMS software are set to constant values ​​in the BMS software code.

[0098] At least one instruction may also include an instruction for performing normal operation of the battery management device when update information of the BMS software related setting values ​​matches update-related values ​​defined in the BMS software.

[0099] Instructions for performing normal operation of the battery management device may include: instructions for reading one or more BMS software-related setting values ​​stored in non-volatile memory; and instructions for interpreting one or more BMS software-related setting values ​​according to the MAP of the BMS software.

[0100] Additionally, at least one instruction may include: an instruction for sequentially writing BMS software-related setting values ​​to non-volatile memory in BMS setting value input mode; and an instruction for recording update-related values ​​defined in the BMS software as update information of BMS software-related setting values ​​in non-volatile memory when one or more normal recordings are completed for all addresses of the non-volatile memory.

[0101] Additionally, the non-volatile memory may include a first non-volatile memory for storing BMS software and update-related values. Here, the first non-volatile memory may be located inside the controller, such as... Figure 7 The first memory 211 is shown in the figure. In one embodiment, the internal memory 211 of the controller 210 may be a programmable ROM or 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.

[0102] 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).

[0103] Furthermore, the non-volatile memory may also include a second non-volatile memory, which stores update information of BMS software-related settings and one or more BMS software-related settings. Here, the second non-volatile memory may be located external to the controller 210, such as... Figure 7 The second memory 222 in.

[0104] In one embodiment, external memory 222 may be a programmable ROM or flash memory. External memory 222 may store settings that determine the operation of the software, such as the number of battery packs, diagnostic thresholds, fault occurrence history, etc. External memory 222 may also store warranty data.

[0105] According to embodiments, the controller 210 may be referred to in this specification as a processor, control unit, microcontroller unit (MCU), etc., and may also refer to a dedicated processor on which the methods according to embodiments of the present invention are executed.

[0106] Additionally, the battery management device 200 may include a communication unit 250, a user interface 270 including input / output interfaces, etc. The communication unit 250 of the battery management device can communicate with internal components and other systems within the device using a controller local area network (CAN). Here, components, modules, or systems within the BMS can be connected to each other via a CAN bus.

[0107] According to the embodiments of the present invention described above, even when no BMS setting information is defined in the battery management device or when BMS setting information that does not correspond to the current BMS software version is stored in the battery management device, it is possible to determine whether the battery management device can operate normally by using the update information of the relevant setting values ​​of the BMS software, thereby preventing the battery management device from malfunctioning.

[0108] 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. A computer-readable recording medium includes all types of recording devices in which computer systems store data readable by the computer. Furthermore, the computer-readable recording medium can be distributed across network-connected computer systems to store and execute computer-readable programs or code in a distributed manner.

[0109] 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 created by a compiler, but also high-level language code that can be executed by a computer using an interpreter.

[0110] 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, a block or apparatus corresponding to a method step or a feature of a method step. Similarly, aspects described in the context of a method may also refer to features of a corresponding block or item or a corresponding apparatus. Some or all of the method steps may be performed by (or using) a hardware device, such as, for example, a microprocessor, a programmable computer, or an electronic circuit. In some embodiments, one or more of the most important method steps may be performed by such an apparatus.

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

Claims

1. A battery management device, comprising: At least one processor; as well as A memory configured to store at least one instruction executed by the at least one processor. Wherein, the at least one instruction includes: Instructions for reading update information of battery management system (BMS) software settings stored in the non-volatile memory of the battery management device during startup; Instructions for comparing the update information of the BMS software related settings with update-related values ​​defined in the BMS software; and An instruction for determining that the battery management device cannot operate when the update information of the BMS software related settings does not match the update-related values ​​defined in the software.

2. The apparatus according to claim 1, wherein, The update-related values ​​defined in the BMS software are set as constant values ​​in the BMS software code.

3. The apparatus according to claim 1, wherein, The at least one instruction further includes: Instructions for performing normal operation of the battery management device when the update information of the BMS software related settings matches the update related values ​​defined in the BMS software.

4. The apparatus according to claim 3, wherein, Instructions for performing normal operation of the battery management device include: Instructions for reading one or more BMS software-related setting values ​​stored in the non-volatile memory; and Instructions for interpreting one or more BMS software-related setting values ​​based on the MAP of the BMS software.

5. The apparatus according to claim 1, wherein, The at least one instruction further includes: Instructions for sequentially writing BMS software-related settings into the non-volatile memory in BMS setting value input mode; and Instructions for recording the update-related values ​​defined in the BMS software as update information of the BMS software-related settings values ​​of the non-volatile memory when one or more normal recordings are completed for all addresses of the non-volatile memory.

6. The apparatus according to claim 1, wherein, The non-volatile memory includes a first non-volatile memory, which stores the BMS software and the update-related values. The first non-volatile memory is located inside the processor.

7. The apparatus according to claim 6, wherein, The non-volatile memory further includes a second non-volatile memory, which stores the update information of the BMS software-related settings and one or more BMS software-related settings. The second non-volatile memory is located outside the processor.

8. A method of operating a battery management device, the method comprising: When the battery management device is started, it reads the update information of the BMS software related settings from the battery management system BMS software related data stored in the non-volatile memory of the battery management device; The update information of the relevant settings in the BMS software is compared with the update-related values ​​defined in the BMS software. as well as If the update information of the BMS software related settings does not match the update related values ​​defined in the software, then it is determined that the battery management device cannot operate.

9. The method according to claim 8, wherein, The update-related values ​​defined in the BMS software are set as constant values ​​in the BMS software code.

10. The method of claim 8, further comprising: When the update information of the BMS software related settings matches the update related values ​​defined in the BMS software, the normal operation of the battery management device is performed.

11. The method of claim 10, wherein performing normal operation of the battery management device comprises: Read one or more BMS software-related settings stored in the non-volatile memory; as well as Interpret the relevant settings of one or more BMS software based on the MAP of the BMS software.

12. The method according to claim 8, further comprising: When the battery management device is determined to be in an inoperable state. Enter BMS settings input mode; The relevant settings of the BMS software are sequentially written into the non-volatile memory; as well as If one or more normal recordings are completed for all addresses of the non-volatile memory, the update-related values ​​defined in the BMS software are recorded as update information for the BMS software-related settings of the non-volatile memory.

13. The method according to claim 8, wherein, The non-volatile memory includes a first non-volatile memory, which stores the BMS software and the update-related values. The first non-volatile memory is located inside the processor of the battery management device.

14. The method according to claim 13, wherein, The non-volatile memory further includes a second non-volatile memory, which stores the update information of the BMS software-related settings and one or more BMS software-related settings. The second non-volatile memory is located outside the processor.

Images