Battery management device and method of operating the battery management device

Abstract

The operation method of the battery management device according to an embodiment of the present invention may include the steps of: reading update information of BMS software-related settings from BMS (Battery Management System) software-related data stored in the non-volatile memory of the battery management device when the battery management device is booted up; comparing the update information of the BMS software-related settings with update-related values ​​defined in the BMS software; and determining that the BMS cannot operate if the update information of the BMS software-related settings does not match the update-related values ​​defined in the software.

Description

TECHNICAL FIELD

[0001] This application claims the benefit of the filing date of Korean Patent Application No. 10-2024-0068946 filed with the Korean Intellectual Property Office on May 28, 2024, and the entire content disclosed in the documents of said Korean patent application is incorporated herein by reference.

[0002] The present invention relates to a battery management apparatus and an operation method of the battery management apparatus, and more specifically, to a battery management apparatus and an operation method of the battery management apparatus related to setting information of BMS software. BACKGROUND ART

[0003] A secondary battery, which is a battery that can be charged and reused after use, is fabricated as a battery module or a battery pack by connecting a plurality of battery cells in series according to the output capacity required by a device, and is used as a power supply source for various devices. Such batteries are used in various fields ranging from the field of small advanced electronic devices such as smartphones to electric bicycles, electric vehicles, and even Energy Storage Systems (ESS).

[0004] A battery pack is a structure in which a plurality of battery cells are combined. When overvoltage, overcurrent, overheating or the like occurs in some battery cells, problems arise in the safety and operation efficiency of the battery pack, so means for detecting these problems are essential. Accordingly, the battery pack is equipped with a BMS (Battery Management System) that measures the voltage value of each battery cell, and monitors and controls the voltage state of the battery cells based on the measured values.

[0005] On the other hand, energy storage systems that link renewable energy, batteries, and the power grid are also equipped with a battery management system (BMS) to monitor the status of the batteries, such as voltage, current, and temperature. The processor of such a battery management system uses software to perform related operations, and the BMS configuration information necessary for the BMS software to operate must be defined.

[0006] Incidentally, if BMS configuration information is not defined within the battery management device, or if configuration information that does not correspond to the current BMS software version is stored within the battery management device, the battery management device may malfunction. [Overview of the Initiative] [Problems that the invention aims to solve]

[0007] The objective of the present invention, which aims to solve the above-mentioned problems, is to provide a battery management device.

[0008] Another objective of the present invention to solve the above-mentioned problems is to provide a method for operating a battery management device related to the setting information of the BMS software. [Means for solving the problem]

[0009] A battery management device according to one embodiment of the present invention for achieving the above objective may include a processor; and a memory configured to store at least one instruction executed through the processor, wherein the at least one instruction may include a (Read) instruction for reading update information of BMS software-related setting values ​​from BMS (Battery Management System) software-related data stored in the non-volatile memory at boot time; an instruction for comparing the update information of the BMS software-related setting values ​​with update-related values ​​defined in the BMS software; and an instruction for determining that the BMS cannot operate if the update information of the BMS software-related setting values ​​does not match the update-related values ​​defined in the software.

[0010] The update-related values ​​defined in the BMS software can be set as constant values ​​in the BMS software code.

[0011] The above at least one instruction may further include an instruction for performing the normal operation of the battery management device if the update information for the BMS software-related settings matches the update-related values ​​defined in the software.

[0012] The commands for performing the normal operation of the battery management device described above may include commands for reading one or more BMS software-related settings stored in the non-volatile memory, and commands for interpreting the one or more BMS software-related settings based on the MAP of the BMS software.

[0013] On the other hand, at least one of the above instructions may further include an instruction for sequentially recording the BMS software-related setting values ​​in non-volatile memory in BMS setting value input mode; and an instruction for recording the update-related values ​​defined in the BMS software as update information for the BMS software-related setting values ​​in the non-volatile memory once or more successful recordings have been completed for all addresses in the non-volatile memory.

[0014] On the other hand, the non-volatile memory may further include a first non-volatile memory for storing the BMS software and the update-related values, and the first non-volatile memory may be located inside the processor.

[0015] Furthermore, the non-volatile memory may further include a second non-volatile memory that stores update information for the BMS software-related settings and one or more BMS software-related settings, and the second non-volatile memory may be located outside the processor.

[0016] An operating method for a battery management device according to one embodiment of the present invention for achieving the above-mentioned other objectives may include the steps of: reading update information of BMS software-related settings from BMS (Battery Management System) software-related data stored in the non-volatile memory of the battery management device when the battery management device is booted up; comparing the update information of the BMS software-related settings with update-related values ​​defined in the BMS software; and determining that the battery management device is inoperable if the update information of the BMS software-related settings does not match the update-related values ​​defined in the software.

[0017] The update-related values ​​defined in the BMS software can be set as constant values ​​in the BMS software code.

[0018] The operation method of the battery management device described above may further include the step of performing normal operation of the battery management device if the update information of the BMS software-related setting values ​​matches the update-related values ​​defined in the software.

[0019] The steps for performing the normal operation of the battery management device described above may include: reading one or more BMS software-related settings stored in the non-volatile memory; and interpreting the one or more BMS software-related settings based on the MAP of the BMS software.

[0020] The operation method of the battery management device may further comprise the steps of: entering a BMS setting value input mode when it is determined that the battery management device is in a BMS inoperable state; sequentially recording said BMS software-related setting values in a non-volatile memory; and recording an update-related value defined in said BMS software as update information of the BMS software-related setting values in said non-volatile memory when normal recording at least once is completed for all addresses of said non-volatile memory.

[0021] Meanwhile, said non-volatile memory may further comprise a first non-volatile memory for storing said BMS software and said update-related value, and said first non-volatile memory may be located inside said processor.

[0022] In addition, said non-volatile memory may further comprise a second non-volatile memory for storing update information of said BMS software-related setting values and one or more BMS software-related setting values, and said second non-volatile memory may be located outside said processor. Effects of the Invention

[0023] According to the embodiments of the present invention as described above, even when BMS setting information is not defined in the battery management device, or setting information that does not correspond to the current BMS software version is stored in the battery management device, determining whether the battery management device can operate normally by using the update information of BMS software-related setting values can block malfunctions of the battery management device. Brief Description of the Drawings

[0024] [Figure 1] 1 shows an example of a battery system structure to which the present invention can be applied. [Figure 2] 2 shows a block configuration of a battery management device for explaining BMS software update. [Figure 3]An example of a data recognition error that may occur in a general BMS software update process is shown. [Figure 4] According to an embodiment of the present invention, the figure shows an example of a BMS operation concept during a software update process. [Figure 5] According to an embodiment of the present invention, an operation flow when a battery management apparatus normally boots is shown. [Figure 6] According to an embodiment of the present invention, an operation flow when the battery management apparatus operates in a BMS set value input mode is shown. [Figure 7] It is a block diagram of the battery management apparatus according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0025] Since various modifications can be made to the present invention and the present invention can have various embodiments, specific embodiments will be illustrated in the drawings and described in detail in the following detailed description. However, it should be understood that this is not intended to limit the present invention to specific embodiments, and includes all modifications, equivalents and alternatives falling within the spirit and technical scope of the present invention. Like reference numerals refer to like elements throughout the description of the drawings.

[0026] Terms such as first, second, A, B, etc. may be used to describe various components, but the components should not be limited by the above terms. These terms are only used for the purpose of distinguishing one component from another. For example, a first component could be termed a second component without departing from the scope of the present invention, and similarly a second component could also be termed a first component. The term "and / or" includes a combination of a plurality of associated listed items or any one of the plurality of associated listed items.

[0027] When it is stated that one component is "combined" or "connected" to another component, it should be understood that this may mean that it is directly combined or connected to the other component, but that another component may exist in between. Conversely, when it is stated that one component is "directly combined" or "directly connected" to another component, it should be understood that there is no other component in between.

[0028] The terms used in this application are used solely to describe specific embodiments and are not intended to limit the invention. Singular expressions include plural expressions unless they are clearly different in context. In this application, terms such as “includes” or “having” are intended to specify the presence of features, figures, steps, actions, components, parts, or combinations thereof as described in the specification, and should not be understood to preemptively exclude the presence or possibility of adding one or more other features, figures, steps, actions, components, parts, or combinations thereof.

[0029] Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as those generally understood by a person of ordinary skill in the art to which this invention pertains. Terms as defined in commonly used dictionaries should be interpreted as having the meaning consistent with their meaning in the context of the relevant art, and not as ideal or overly formal unless explicitly defined herein.

[0030] Some terms used in this specification are defined as follows:

[0031] A battery cell is the smallest unit that stores electricity, while a battery pack refers to an assembly of multiple battery cells that are electrically connected.

[0032] A battery rack refers to a single-structure system assembled by electrically connecting modules configured by the battery manufacturer, and can be monitored and controlled by a Battery Management System (BMS). A battery rack can consist of multiple battery packs (or battery modules) and a battery protection unit (BPU) or other protective devices.

[0033] A battery bank refers to a large collection of battery rack systems, consisting of multiple battery racks connected in parallel. A bank BMS for a battery bank can monitor and control several rack BMSs, each of which manages its own battery rack.

[0034] Preferred embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0035] Figure 1 shows an example of a battery system structure to which the present invention can be applied.

[0036] In the battery system shown in Figure 1, multiple battery packs are contained within a battery rack, and multiple battery racks are contained within a battery bank. The battery system shown in Figure 1 can constitute part of an energy storage system.

[0037] In this configuration, a Battery Management System (BMS) may be provided for each of the battery packs, battery racks, and battery banks. In Figure 1, a battery pack may consist of multiple battery cells connected in series. The battery cells are connected to a load via positive and negative terminals and can perform charging and discharging operations. The most commonly used battery cells are lithium-ion (Li-Ion) battery cells. A Battery Management System (BMS) may be provided for each of these battery packs.

[0038] The battery management system (BMS) monitors the current, voltage, and temperature of each battery pack under its control, and calculates the State of Charge (SOC) based on the monitoring results to control charging and discharging. Here, SOC represents the current charge state of the battery as a percentage [%].

[0039] To perform such operations, a BMS can include a variety of components such as fuses, current sensing elements, thermistors, switches, and balancers, but in most cases it includes an MCU (Micro Controller Unit) or BMIC (Battery Monitoring Integrated Chip) to control them in conjunction. Here, the BMIC may be an IC-type component located inside the BMS that measures information such as the voltage, temperature, and current of the battery cells / modules.

[0040] On the other hand, each RBMS (Rack BMS) manages its own battery rack, and the BBMS (Bank BMS) can control the entire battery bank, including these battery racks. Each RBMS can monitor the current, voltage, and temperature from each battery rack, calculate the State of Charge (SOC) based on the monitoring results, and control charging and discharging. Multiple rack BMSs are connected to a Battery Section Controller (BSC), which can manage and control the entire battery system. In the embodiment shown in Figure 1, the Bank BMS (BBMS) is shown performing the same function as the BSC, and can be called either BBMS or BSC depending on the system.

[0041] A BMS can also monitor battery cells, read cell voltages, and transmit them to other systems connected to the battery. For this purpose, the BMS includes a communication module for communicating with other systems within the device containing the battery system. The BMS's communication module can communicate with other systems within the device using a Controller Area Network (CAN). In this case, components, modules, or systems within the BMS can be connected to each other via the CAN bus.

[0042] The battery management device (BMS) according to an embodiment of the present invention may be one of the following: a BSC (battery system controller) / BBMS that manages a battery bank, a rack BMS connected to the BSC / BBMS that manages each battery rack, or a pack BMS connected to the rack BMS that manages each battery pack.

[0043] Figure 2 shows the block configuration of the battery management device to illustrate the BMS software update.

[0044] As explained through Figure 1 above, the battery management device 200 monitors and manages the battery 100. Here, the battery can refer to various types of battery assemblies, such as battery packs (modules), battery racks, and battery banks. The battery management device 200 may include a processor 210 and memories 211 and 222, and may further include various components and circuits, such as a battery monitoring circuit (e.g., a BMIC (Battery Monitoring Integrated Chip)), although these are not shown for convenience.

[0045] On the other hand, the battery management device 200 may include non-volatile memory (internal memory) 211 inside the processor 210. In one embodiment, the internal memory 211 of the processor 210 may be flash memory. The internal memory 211 of the processor 210 may store software (e.g., an application) for the operation of the battery management device 200. The internal memory 211 of the processor 210 may also store a bootloader for booting the battery management system 200.

[0046] The battery management device 200 may include a separate external memory 222, such as non-volatile memory, in addition to the internal memory 210 in the control unit 210. The external memory 222 can store BMS setting values ​​that determine the operation of the software, such as the number of battery packs, diagnostic thresholds, fault occurrence history, etc. The external memory 222 can also store warranty data.

[0047] On the other hand, battery management devices require software updates for various reasons, such as functional improvements and the addition of new functions. In this invention, software updates may include the concepts of software upgrades and downgrades. The processor 210 can receive software update instructions 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.

[0048] In response to a software update command, the processor 210 can overwrite the area in internal memory 211 where the existing software is stored with the new software 222. In one embodiment, the processor can erase the existing software in internal memory 211 and write the new software. In one embodiment, the processor can perform a reset, jump to the boot loader, and write the new software to internal memory 211. This deletes the existing software from internal memory 210, records the new software, and updates the software.

[0049] When booting with new software, the processor 210 loads configuration values ​​that determine the operation of the software stored in external memory 222 and can operate using these configuration values. The processor 210 can interpret BMS configuration setting value-related data (e.g., binary data) stored in external memory 222 using a software MAP that defines configuration setting (NV (Non-Volatile)) values. On the other hand, the BMS software MAP can be stored within the software together with the BMS software.

[0050] Figure 3 shows an example of a data recognition error that may occur during a typical BMS software update process.

[0051] In the battery management device having the configuration shown in Figure 2, when a general software update is performed, the battery management device starts up with the new software stored in the internal memory 211 and performs battery management operations.

[0052] At this time, the processor 210 can interpret the setting values ​​that determine the operation of the BMS software using the software MAP and perform the associated operations. Here, the BMS software-related setting values ​​35 that determine the operation of the software may include, for example, the number of battery packs, diagnostic thresholds, fault history, etc.

[0053] Referring to the example in Figure 3, if the software version 30 before the update is 1.0.0.0, then MAP33 in version 1.0.0.0 is defined in the following order: "Pack count (unit8_t)", "OVF (Over Voltage Fault) Detect (unit16_t)", "OVF Release (unit16_t)", "UVF (Under Voltage Fault) Detect (unit16_t)", and "UVF Release (unit16_t)".

[0054] Furthermore, the BMS software-related settings 33 stored in the external non-volatile memory are: "Pack count = 16", "OVF (Over Voltage Fault) Detect = 38000", "OVF Release = 36000", "UVF (Under Voltage Fault) Detect = 29000", and "UVF Release = 29500". The processor can interpret the BMS software-related settings 35 based on the defined MAP 33. Here, the BMS software-related settings 35 can be stored in the external non-volatile memory area 222, grouped by data type and category (Voltage, voltage diagnostics, Current, current diagnostics, etc.).

[0055] On the other hand, if an update is performed as shown in Figure 3 and the new software version 30 is changed to 1.0.0.1, the new software will interpret the values ​​set in external memory based on the software MAP 33-1 defined by version 1.0.0.1. In other words, the processor 210 takes in the same binary data as before the software update, but interprets the data based on the MAP by the new software, so the processor obtains a completely different interpretation result than before the update.

[0056] Referring to the updated data interpretation in Figure 3, the new software defines the related data for MAP33-1 in the following order: "Fan Type", "Pack count", "OVF (Over Voltage Fault) Detect", "OVF Release", and "UVF (Under Voltage Fault) Detect". Therefore, it can be seen that interpreting the existing BMS software setting related binary data stored in non-volatile memory in this order results in data distortion 35'.

[0057] In this invention, to solve such problems, information regarding the number of times the information stored in the non-volatile memory is updated is recorded in memory during software updates and other similar events, and this information regarding the number of updates is used to prevent data distortion and block malfunctions of the BMS.

[0058] Figure 4 shows an example of the BMS operation concept during the software update process according to an embodiment of the present invention.

[0059] In the example in Figure 4, if the software version 30 before the update is 1.0.0.0, it can be seen that MAP33 in version 30 1.0.0.0 is defined in the following order: "Pack count (unit8_t)", "OVF (Over Voltage Fault) Detect (unit16_t)", "OVF Release (unit16_t)", "UVF (Under Voltage Fault) Detect (unit16_t)", and "UVF Release (unit16_t)".

[0060] The processor of the battery management device according to an embodiment of the present invention can interpret BMS software-related setting values ​​35 based on a predefined MAP 33. Furthermore, in 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 mean 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 an external memory 222.

[0061] On the other hand, according to an embodiment of the present invention, the setting value update information 310, which is defined as a constant value within the BMS software, can be included in the form of a constant value. A constant value defined in such software can be understood as a literal value (fixed in the source code) that is definitively defined in the software code. For example, a software developer can change the relevant constant value (increasing it in proportion to the version) each time new software is developed.

[0062] For example, when a BMS is first produced at the factory and the setting value is recorded once, the update information 410 is recorded as "1 (Ox01)" as shown in Figure 4. Subsequently, when a software update is performed as shown in Figure 4 and the software version 30 is changed to 1.0.0.1, it can be seen that the update information 310' defined as a constant within the modified software has also changed to "Ox02".

[0063] However, even if new software is stored in internal memory in accordance with a software update command, the existing settings previously recorded / stored for BMS software operation remain unchanged. Therefore, the update information (NV revision) 410 for BMS software-related settings stored in non-volatile memory remains at "1 (Ox01)".

[0064] According to the present invention, in such a case, that is, when a value (Ox01) different from the update constant (Ox02) defined in the software is recorded in the non-volatile memory as update information for BMS software-related settings, the processor of the battery management device can determine that the value in question is not a value intended by the user and process it as BMS operation impossible.

[0065] Figure 5 shows the operation flow when a battery management device is typically booted up according to one embodiment of the present invention.

[0066] During a typical boot-up of the battery management device, for example, when a battery management device is deployed to an ESS (Energy Storage System) site and begins operation, the processor 210 reads (Read) (S510) update information for BMS (Battery Management System) software-related settings stored in the non-volatile memory. Here, the non-volatile memory may be memory located outside the processor 210. The above non-volatile memory may also be flash memory.

[0067] In one embodiment, the process by which the processor 210 reads update information for BMS software-related settings stored in non-volatile memory may include a detailed process of reading all data stored in non-volatile memory and extracting the update information for BMS software-related settings from it. On the other hand, in another embodiment, the processor 210 may also read only the data at the address where the update information (recorded in a designated area in memory) is stored from the data stored in non-volatile memory. In this case, the update information for BMS software-related settings stored in non-volatile memory may be stored in the memory at the very beginning address of all data stored in non-volatile memory.

[0068] The processor compares the update information of BMS software-related settings recorded in non-volatile memory (NV Data on Flash) with software-defined update constants (SW Defined constants) to determine if the two values ​​are identical (S520). Here, the update-related values ​​defined in the BMS software can be set as constant values ​​in the BMS software code.

[0069] If the two values ​​are the same, the processor can operate normally using the BMS software (S530). During normal operation of the battery management device, one or more BMS software-related settings stored in the non-volatile memory can be read and interpreted based on the BMS software's MAP.

[0070] On the other hand, if the update information for BMS software-related settings recorded in non-volatile memory differs from the update constants defined in the software, the processor determines that a value not intended by the user is stored in non-volatile memory and processes it as BMS operation impossible (S540).

[0071] More specifically, during normal operation (S540), the battery management device can perform general BMS functions such as updating the current data of the battery pack (module), diagnosis, cell balancing, and charging / discharging.

[0072] On the other hand, if the BMS operation is deemed impossible (S540), the battery management device can enter BMS setting value input mode (for example, factory mode). After proceeding with the process of recording the BMS setting value in non-volatile memory through the BMS setting value input mode, the battery management device can perform normal BMS operation.

[0073] Figure 6 shows the operation flow when the battery management device operates in BMS setting value input mode according to an embodiment of the present invention.

[0074] In BMS setting value input mode (for example, factory mode), setting values ​​such as "Pack count", "OVF (Over Voltage Fault) Detect", "OVF Release", "UVF (Under Voltage Fault) Detect", and "UVF Release" can be sequentially recorded in non-volatile memory. The BMS software setting values ​​recorded in non-volatile memory can be defined in such a way that, for example, NV_Value[0] indicates the setting value for the pack count, NV_Value[1] indicates the OVF detection value, and NV_Value[2] indicates the OVF release value.

[0075] Referring to Figure 6, the BMS setting value related variable i is initialized to "0" in the preliminary work (S610). Then, the NV value of the NV_Value[i] category is written to non-volatile memory (S620), and the corresponding NV value is activated (SET) (S630). It is checked whether the NV value of the NV_Value[i] category is valid (S640), and if it is not valid (no in S640), the recording and activation process is repeated.

[0076] If the corresponding NV_Value[i] category value is valid, the variable i value is incremented (S651), and recording (Write) (S620) and activation (SET) (S630) operations are performed for each category. Recording (Write) (S620) and activation (SET) (S630) operations for each category are performed until the last setting value to be recorded is reached (S650).

[0077] Once at least one successful write operation has been completed for all non-volatile memory addresses, the processor can record the same value as the software-defined update constant (SW Defined constant) in the non-volatile memory BMS software-related setting information (NV Data on Flash) (S660).

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

[0079] The battery management device 200 according to an embodiment of the present invention may include a control unit 210 and a memory for storing at least one instruction executed through the processor. In this case, the memory may include one or more of the first memory 211 and the second memory 222 shown in Figure 7.

[0080] Here, at least one of the above instructions may include: an instruction to read (Read) update information of BMS (Battery Management System) software-related settings from BMS software-related data stored in non-volatile memory during boot; an instruction to compare the above update information of BMS software-related settings with update-related values ​​defined in the BMS software; and an instruction to determine that the BMS cannot operate if the above update information of BMS software-related settings does not match the update-related values ​​defined in the software.

[0081] The update-related values ​​defined in the BMS software can be set as constant values ​​in the BMS software code.

[0082] The above at least one instruction may further include an instruction for normal operation of the battery management device if the update information of the BMS software-related setting values ​​matches the update-related values ​​defined in the software.

[0083] The commands for performing the normal operation of the battery management device described above may include commands for reading one or more BMS software-related settings stored in the non-volatile memory, and commands for interpreting the one or more BMS software-related settings based on the MAP of the BMS software.

[0084] On the other hand, at least one of the above instructions may further include an instruction for sequentially recording the BMS software-related setting values ​​in non-volatile memory in BMS setting value input mode; and an instruction for recording the update-related values ​​defined in the BMS software as update information for the BMS software-related setting values ​​in the non-volatile memory once or more successful recordings have been completed for all addresses in the non-volatile memory.

[0085] On the other hand, the non-volatile memory may include a first non-volatile memory that stores the BMS software and the update-related values. Here, the first non-volatile memory may be located inside the control unit, as shown in Figure 7 as the first memory 211. In one embodiment, the internal memory 211 of the control unit 210 may be a programmable ROM or flash memory. The internal memory 211 of the control unit 210 may store software (e.g., an application) for the operation of the battery management device 200. The internal memory 211 of the control unit 210 may also store a bootloader for booting the battery management system 200.

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

[0087] Furthermore, the non-volatile memory may further include a second non-volatile memory that stores update information for the BMS software-related settings and one or more BMS software-related settings. Here, the second non-volatile memory may be located outside the control unit 210, as shown in the second memory 222 in Figure 7.

[0088] In one embodiment, the external memory 222 may be a programmable ROM or flash memory. The external memory 222 can store setting values ​​that determine the operation of the software, such as the number of battery packs, diagnostic thresholds, fault history, etc. Warranty data may also be stored in the external memory 222.

[0089] According to the embodiments, the control unit 210 may be referred to herein as a processor, controller, MCU (Micro Controller Unit), etc., and may also mean a dedicated processor on which the method according to the embodiments of the present invention is carried out.

[0090] On the other hand, the battery management device 200 may further include a communication unit 250, a user interface 270 including an input / output interface, and the like. The communication unit 250 of the battery management device can communicate not only with its internal components but also with other systems within the device using CAN (Controller Area Network). In this case, components, modules, or systems within the BMS can be connected to each other via the CAN bus.

[0091] According to the embodiments of the present invention described above, even if BMS setting information is not defined in the battery management device, or if setting information that does not correspond to the current BMS software version is stored in the battery management device, malfunctions of the battery management device can be prevented by determining whether the battery management device can operate normally using update information of BMS software-related setting values.

[0092] The operation of the method according to the embodiment of the present invention can be embodied as a computer-readable program or code on a computer-readable recording medium. A computer-readable recording medium includes all types of recording devices that store data that can be read by a computer system. Furthermore, computer-readable recording media can be distributed across networked computer systems, allowing computer-readable programs or code to be stored and executed in a distributed manner.

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

[0094] Some aspects of the present invention have been described in the context of apparatus, but they can also be described by corresponding methods, where a block or apparatus corresponds to a method step or a feature of a method step. Similarly, aspects described in the context of a method can be described by corresponding blocks or items or features of corresponding apparatus. Some or all of the method steps can be carried out by (or using) hardware devices 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 can be carried out by such devices.

[0095] While preferred embodiments of the present invention have been described above with reference to the present invention, those skilled in the art will understand that the present invention can be modified and altered in various ways without departing from the spirit and scope of the invention as set forth in the following claims. [Explanation of Symbols]

[0096] 100:Battery 200:Battery management device 210: Control Unit 211: First memory 222: Second memory 250: Communications Department 270: User Interface

Claims

1. Processor; and A battery management device including a memory for storing at least one instruction executed through the processor, The at least one instruction is, An instruction to read (Read) update information for BMS (Battery Management System) software-related settings stored in the non-volatile memory of the battery management device during boot-up; An instruction for comparing the update information of the BMS software-related setting values ​​with the update-related values ​​defined in the BMS software; and A battery management device that includes a command for determining that the BMS cannot operate if the update information of the BMS software-related setting values ​​does not match the update-related values ​​defined in the BMS software.

2. The battery management device 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 at least one instruction is, The battery management device according to claim 1, further comprising an instruction for performing normal operation of the battery management device when the update information of the BMS software-related setting values ​​matches the update-related values ​​defined in the software.

4. The commands for performing the normal operation of the aforementioned battery management device are: An instruction to read one or more BMS software-related setting values ​​stored in the non-volatile memory; and The battery management device according to claim 3, comprising an instruction for interpreting one or more BMS software-related settings based on the MAP of the BMS software.

5. The at least one instruction is, In BMS setting value input mode, an instruction for sequentially recording the BMS software-related setting values ​​in non-volatile memory; and The battery management device according to claim 1, further comprising an instruction to record the update-related values ​​defined in the BMS software as update information for the BMS software-related settings of the non-volatile memory when one or more successful recordings have been completed for all addresses of the non-volatile memory.

6. The aforementioned non-volatile memory is It includes the BMS software and a first non-volatile memory for storing the update-related values, The battery management device according to claim 1, wherein the first non-volatile memory is located inside the processor.

7. The aforementioned non-volatile memory is The system further includes a second non-volatile memory that stores update information for the BMS software-related settings and one or more BMS software-related settings. The battery management device according to claim 6, wherein the second non-volatile memory is located outside the processor.

8. During the boot-up of the battery management device, a Read step is performed to read update information for BMS (Battery Management System) software-related settings from the BMS (Battery Management System) software-related data stored in the non-volatile memory of the battery management device; A step of comparing the update information of the BMS software-related settings with the update-related values ​​defined in the BMS software; and A method for operating a battery management device, which includes the step of determining that the BMS cannot operate if the update information of the BMS software-related setting values ​​does not match the update-related values ​​defined in the BMS software.

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

10. The method for operating a battery management device according to claim 8, further comprising the step of performing normal operation of the battery management device when the update information of the BMS software-related setting values ​​matches the update-related values ​​defined in the software.

11. The step of performing the normal operation of the battery management device is: The steps of reading one or more BMS software-related setting values ​​stored in the non-volatile memory; and A method for operating a battery management device according to claim 10, comprising the step of interpreting one or more BMS software-related settings based on the MAP of the BMS software.

12. If the battery management device determines that the BMS is inoperable, it enters the BMS setting value input mode; The steps of sequentially recording the BMS software-related settings into non-volatile memory; and The method for operating a battery management device according to claim 8, further comprising the step of recording the update-related values ​​defined in the BMS software as update information for the BMS software-related settings of the non-volatile memory when one or more successful recordings have been completed for all addresses of the non-volatile memory.

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

14. The aforementioned non-volatile memory is The system further includes a second non-volatile memory that stores update information for the BMS software-related settings and one or more BMS software-related settings. The method of operating the battery management device according to claim 13, wherein the second non-volatile memory is located outside the processor.

Images