A battery management embedded software system

Abstract

This application discloses an embedded software system for battery management, relating to the new energy field. The software system includes a human-machine interface layer that receives operation commands and displays the current status and battery data of the battery cluster; an interface encapsulation layer that encapsulates external interfaces and sends the encapsulation results to the human-machine interface layer, and receives operation commands; a logic processing layer that calls the corresponding battery model according to the operation commands, applies battery management strategies, generates control commands, determines the current status and battery data of the battery cluster, and sends them to the human-machine interface layer through the interface encapsulation layer; a device access layer that uniformly encapsulates the communication protocols of battery management systems from different manufacturers, accesses the corresponding device operation interface according to the control commands to obtain parameters of the preset hardware interface, and generates call commands; and a hardware interface layer that performs secondary encapsulation of the preset hardware interface and sends corresponding preset data to the preset hardware interface according to the call commands. This application facilitates maintenance of different projects.

Description

Technical Field

[0001] This application relates to the field of new energy, and in particular to an embedded software system for battery management. Background Technology

[0002] Currently, in the application fields of energy storage projects, the following main problems exist during project implementation and development:

[0003] 1. Different projects use different types of batteries, such as lithium iron phosphate batteries, ternary lithium batteries, and sodium-ion batteries. The battery parameters and models of different batteries are different.

[0004] 2. Different projects use different types and types of third-party BMS, energy storage converters, and other equipment, with various communication interfaces and protocols.

[0005] 3. Different projects and different application scenarios, such as power energy storage, industrial and commercial energy storage, and mobile base station backup power storage, require different battery management strategies and different needs.

[0006] Currently, different projects require a separate set of battery management software. As the number of projects increases, problems such as large maintenance workload, numerous maintenance contents, and difficulty in tracing and maintaining different software versions can easily arise. Summary of the Invention

[0007] The purpose of this application is to provide a battery management embedded software system that can more easily maintain different projects.

[0008] To achieve the above objectives, this application provides the following solution:

[0009] This application provides a battery management embedded software system, which includes, from top to bottom, a human-computer interaction layer, an interface encapsulation layer, a logic processing layer, a device access layer, and a hardware interface layer;

[0010] The human-computer interaction layer is used to receive operation commands and display the current status of the battery cluster and battery data;

[0011] The interface encapsulation layer is connected to the human-computer interaction layer; the interface encapsulation layer is used to encapsulate the external interfaces set by the hardware interface layer, the device access layer, and the logic processing layer, and send the encapsulation result to the human-computer interaction layer, as well as receive the operation instructions;

[0012] The logic processing layer is connected to the interface encapsulation layer. The logic processing layer is used to call the corresponding battery model according to the operation instruction, apply a battery management strategy to the battery model, generate control instructions based on the battery management strategy, determine the current state and battery data of the battery cluster, and send these instructions to the human-machine interaction layer through the interface encapsulation layer. The control instructions include acquiring data from a preset hardware interface and sending corresponding preset data to the preset hardware interface. The battery model describes the battery parameters using an XML-formatted description file. The parameters include the battery's charge / discharge cutoff voltage, the relationship between the battery's temperature and maximum charge / discharge power, and the battery's charge / discharge curve data.

[0013] The device access layer is connected to the logic processing layer; the device access layer is used to uniformly encapsulate the communication protocols of battery management systems from different manufacturers, and to access the corresponding device operation interface according to the control command to obtain the parameters of the preset hardware interface, and generate a call command.

[0014] The hardware interface layer is connected to the device access layer; the hardware interface layer is used to perform secondary encapsulation of the preset hardware interface and send corresponding preset data to the preset hardware interface according to the calling instruction.

[0015] Optionally, the preset hardware interface includes RS485, CAN, SPI, IIC and Ethernet interfaces.

[0016] Optionally, the battery management strategy is programmable.

[0017] Optionally, the battery management strategy describes the execution steps using an XML-formatted description file.

[0018] Optionally, the battery management strategy includes a power-on process, a power-off process, a charge / discharge process, a battery maintenance process, and a standby process.

[0019] Optionally, the logic processing layer further compares the battery data with a preset battery threshold and determines the current state of the battery cluster based on the comparison result; the current state includes a fault state, a fully charged state, and a discharged state.

[0020] Optionally, an XML configuration file is obtained; the XML configuration file is parsed to obtain battery attribute data, and the battery attribute data is stored in memory in a key-value format.

[0021] Optionally, during the charging process, if the voltage data of the battery module in the battery cluster exceeds the battery module charging cutoff voltage configuration value stored in memory, the battery module is marked as being fully charged.

[0022] During the discharge process, if the voltage data of the battery module in the battery cluster collected is lower than the battery module discharge cutoff voltage configuration value stored in memory, the battery module is marked as being in a discharged state.

[0023] During the charging and discharging process, if the voltage data of the battery module in the battery cluster is lower than the battery module fault voltage configuration value stored in memory, the battery module is marked as being in a fault state.

[0024] During the charging process, when the voltage data of each cell inside the battery module in the battery cluster exceeds the single-cell charging cutoff voltage configuration value stored in memory, the battery module is marked as fully charged.

[0025] During the discharge process, when the voltage data of each cell inside the battery module in the battery cluster is lower than the single cell discharge cutoff voltage configuration value stored in memory, the battery module is marked as being in a discharged state.

[0026] During the charging and discharging process, if the voltage data of each cell inside the battery module in the battery cluster is lower than the single cell fault voltage configuration value stored in memory, the battery module is marked as being in a fault state.

[0027] During the charging process, when any battery module in the battery cluster is fully charged, the battery cluster is marked as fully charged.

[0028] During the discharge process, when any battery module in the battery cluster is in a discharged state, the battery cluster is marked as being in a discharged state.

[0029] During the charging and discharging process, if any battery module in the battery cluster is in a fault state, the battery cluster is marked as faulty.

[0030] According to the specific embodiments provided in this application, the following technical effects are disclosed:

[0031] This application provides a battery management embedded software system that can quickly generate executable programs for different project requirements by dynamically editing the battery management strategy process; and can accept and manage different types of batteries by defining the battery model of each battery module in the system. Different battery types do not require software modification, making it easier to maintain different projects. Attached Figure Description

[0032] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0033] Figure 1 This application provides a schematic diagram of an embedded software system for battery management.

[0034] Figure 2 The energy storage battery management system architecture diagram provided for this application. Detailed Implementation

[0035] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0036] To make the above-mentioned objectives, features and advantages of this application more apparent and understandable, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0037] like Figures 1 to 2 As shown, a battery management embedded software system is provided, which includes, from top to bottom, a human-computer interaction layer, an interface encapsulation layer, a logic processing layer, a device access layer, and a hardware interface layer.

[0038] The human-computer interaction layer is used to receive operation commands and display the current status of the battery cluster and battery data.

[0039] The interface encapsulation layer is connected to the human-computer interaction layer; the interface encapsulation layer is used to encapsulate the external interfaces set by the hardware interface layer, the device access layer, and the logic processing layer, and send the encapsulation result to the human-computer interaction layer, as well as receive the operation instructions.

[0040] The logic processing layer is connected to the interface encapsulation layer. The logic processing layer is used to call the corresponding battery model according to the operation instruction, apply a battery management strategy to the battery model, generate control instructions based on the battery management strategy, determine the current state and battery data of the battery cluster, and send these to the human-machine interaction layer through the interface encapsulation layer. The control instructions include acquiring data from a preset hardware interface and sending corresponding preset data to the preset hardware interface. The battery model describes the battery parameters using an XML format description file. The parameters include the battery's charge / discharge cutoff voltage, the relationship between the battery's temperature and maximum charge / discharge power, and the battery's charge / discharge curve data.

[0041] The device access layer is connected to the logic processing layer; the device access layer is used to uniformly encapsulate the communication protocols of battery management systems from different manufacturers, and to access the corresponding device operation interface to obtain the parameters of the preset hardware interface according to the control command, and to generate a call command.

[0042] The hardware interface layer is connected to the device access layer; the hardware interface layer is used to perform secondary encapsulation of the preset hardware interface and send corresponding preset data to the preset hardware interface according to the calling instruction.

[0043] Specifically, the preset hardware interfaces include RS485, CAN, SPI, IIC, and Ethernet interfaces. The battery management strategy is programmable. The battery management strategy describes the execution steps through an XML format description file. The battery management strategy includes a power-on process, a power-off process, a charge / discharge process, a battery maintenance process, and a standby process.

[0044] Furthermore, the logic processing layer also compares the battery data with a preset battery threshold and determines the current state of the battery cluster based on the comparison result; the current state includes fault state, fully charged state, and discharged state.

[0045] Obtain the XML configuration file; parse the XML configuration file to obtain battery attribute data, and store the battery attribute data in memory in a key-value format.

[0046] During the charging process, when the voltage data of the battery module in the battery cluster exceeds the battery module charging cutoff voltage configuration value stored in memory, the battery module is marked as fully charged.

[0047] During the discharge process, if the voltage data of the battery module in the battery cluster is lower than the battery module discharge cutoff voltage configuration value stored in memory, the battery module is marked as being in a discharged state.

[0048] During the charging and discharging process, if the voltage data of the battery module in the battery cluster is lower than the battery module fault voltage configuration value stored in memory, the battery module is marked as being in a fault state.

[0049] During the charging process, when the voltage data of each cell inside the battery module in the battery cluster exceeds the single-cell charging cutoff voltage configuration value stored in memory, the battery module is marked as fully charged.

[0050] During the discharge process, when the voltage data of each cell inside the battery module in the battery cluster is lower than the single cell discharge cutoff voltage configuration value stored in memory, the battery module is marked as being in a discharged state.

[0051] During the charging and discharging process, if the voltage data of each cell inside the battery module in the battery cluster is lower than the single cell fault voltage configuration value stored in memory, the battery module is marked as being in a fault state.

[0052] During the charging process, when any battery module in the battery cluster is fully charged, the battery cluster is marked as fully charged.

[0053] During the discharge process, when any battery module in the battery cluster is in a discharged state, the battery cluster is marked as being in a discharged state.

[0054] During the charging and discharging process, if any battery module in the battery cluster is in a fault state, the battery cluster is marked as faulty.

[0055] As a specific implementation method, this software system adopts a layered architecture to reduce the software coupling between different functional levels and improve the maintainability and portability of the program architecture.

[0056] This software system is designed from the bottom up as follows:

[0057] BOS-HIL (Battery Operating System Hardware Interface Layer) is the hardware interface layer. This layer is responsible for the unified encapsulation of hardware interfaces.

[0058] BOS-HDL layer (Battery Operating System Hardware Device Layer) is the device access layer. This layer is responsible for encapsulating the communication protocol interfaces of various peripheral devices.

[0059] The BOS-CORE layer (battery operating system core) implements the business logic of the battery management system. This layer is responsible for the core business logic of the battery management system.

[0060] The BOS-API layer (Battery Operating System Application Programming Interface) is a wrapper layer for the API interfaces of the three layers mentioned above. This layer is responsible for uniformly encapsulating the functional interfaces of the BOS-HIL, BOS-HDL, and BOS-CORE layers.

[0061] BOS-APP layer (battery operating system application), human-computer interaction layer. This layer implements the human-computer interaction logic.

[0062] like Figure 2The diagram shows a typical battery management system architecture. The battery topology is a 3-parallel, n-series battery network. The total positive and negative terminals of the batteries are connected to the energy storage converter. The battery management system (BMS) inside the battery pack, the energy storage converter, and the battery management controller communicate via a CAN bus. The embedded software system described in this patent runs inside the battery management controller.

[0063] The battery pack's internal BMS includes functions for acquiring internal voltage, current, temperature, individual cell voltage, and open-circuit voltage. The BMS also includes functions for controlling the charging and discharging of the current pack.

[0064] The BOS-HIL layer provides secondary encapsulation for commonly used hardware interfaces, primarily RS485, CAN, SPI, IIC, and Ethernet interfaces. It also encapsulates network and file system operation interfaces to ensure compatibility with different operating systems. Furthermore, the BOS-HIL layer further encapsulates necessary operating system interfaces, including system-provided interfaces for semaphores, mutexes, system clock acquisition, and delay functions. This facilitates the portability and operation of software systems across different operating systems.

[0065] The BOS-HDL layer provides a unified encapsulation of communication protocols for BMS from different manufacturers, supporting data access and control for different BMS models.

[0066] The BOS-CORE layer supports inputting a battery model for each battery pack in the system. The battery model uses an XML-formatted description file to describe various parameters of the battery, including the battery's charge / discharge cutoff voltage, the relationship between the battery's temperature and maximum charge / discharge power, and the battery's charge / discharge curve data.

[0067] This software system is used to process model data for each battery in the subordinate battery pack array. The model data of each battery module is input to the battery data analysis and processing module of the BOS-CORE layer. The battery data analysis and processing module calculates the current charging and discharging power based on the model data of each battery and the real-time data of each battery module, and sends control commands to the corresponding device operation interface of the BOS-HDL layer. The device operation layer further calls the hardware interface layer of the BOS-HIL layer to send the data to the corresponding peripheral devices.

[0068] Data processing steps of the battery data analysis and processing module:

[0069] (1) The battery data analysis and processing module reads the XML configuration file during startup, parses the XML file, and stores the battery attribute data in memory in a key-value manner.

[0070] (2) The battery data analysis and processing module collects information such as voltage, current and temperature of each battery module and cell in the battery cluster through the interface provided by the BOS-HDL layer.

[0071] (3) During the charging process, the battery data analysis and processing module will compare the collected battery module pack voltage data with the battery module charging cutoff voltage configuration stored in memory in step (1). If the value exceeds the configuration value, the battery module will be marked as fully charged.

[0072] (4) During the discharge process, the battery data analysis and processing module will compare the collected battery module pack voltage data with the battery module discharge cutoff voltage configuration stored in memory in step (1). If it is lower than the configuration value, the battery module will be marked as being in a discharged state.

[0073] (5) During the charging and discharging process, the battery data analysis and processing module will compare the collected battery module pack voltage data with the battery module fault voltage configuration stored in memory in step (1). If it is lower than the configuration value, the battery module will be marked as being in a fault state.

[0074] (6) During the charging process, the battery data analysis and processing module compares the voltage data of each cell inside the battery module with the single cell charging cutoff voltage configuration stored in memory in step (1). If the voltage exceeds the configuration value, the battery module is marked as fully charged.

[0075] (7) During the discharge process, the battery data analysis and processing module compares the voltage data of each cell inside the battery module with the single cell discharge cutoff voltage configuration stored in memory in step (1). If the voltage is lower than the configuration value, the battery module is marked as being in a discharged state.

[0076] (8) During the charging and discharging process, the battery data analysis and processing module compares the voltage data of each cell inside the battery module with the single cell fault voltage configuration stored in memory in step (1). If the voltage is lower than the configuration value, the battery module is marked as being in a fault state.

[0077] (9) During the charging process, the battery data analysis and processing module determines that the battery cluster is fully charged if any battery module is fully charged. During the discharging process, it determines that the battery cluster is discharged if any battery module is discharged. If any battery module is detected to be in a fault state during the charging and discharging process, the battery cluster is determined to be faulty.

[0078] (10) The battery data analysis and processing module collects the DC bus voltage and current of the battery cluster through the interface provided by the BOS-HDL layer. The charging and discharging power value of the current system is obtained by multiplying the voltage by the current.

[0079] The battery management strategy implemented in this software system is programmable, not fixed and unmodifiable logic. It allows for dynamic editing and generation of battery management strategy steps to adapt to different project needs. The output of the battery data analysis and processing module serves as input to the battery management strategy execution module, providing a basis for strategy operation. Modifications to the battery management strategy are necessary because different projects have different requirements. For example, in projects without special requirements, the system will automatically adjust and reduce power at the end of charging and discharging to protect the battery. However, some projects require the battery management system to never reduce power, prioritizing power output. In such cases, automatic power reduction should not be implemented at the end of charging and discharging.

[0080] First, logic programming uses XML format description files to describe the steps. XML is a markup language for describing data, characterized by high readability, ease of parsing, and extensibility. Each command consists of a command word and command parameters.

[0081] This software system divides battery management strategies into several business scenarios, including power-on, power-off, charging / discharging, battery maintenance, and standby processes. Each process corresponds to an editable XML process description file. The description file contains a list of commands and parameters for the corresponding process.

[0082] For different project requirements, the steps of each business process in the project can be quickly generated through logic programming for different scenarios of BMS or energy storage converter PCS used in the project. It has strong compatibility and scalability, which can save manpower and time to a great extent and reduce maintenance costs.

[0083] The BOS-API layer mainly encapsulates the interfaces provided by the BOS-CORE, BOS-HDL, and BOS-HIL layers. It publishes telemetry and teleindication data to various apps via the MQTT protocol and subscribes to control commands and data published by each app.

[0084] The BOS-APP layer primarily implements the human-machine interface, displaying the current status and battery data of the battery cluster, and providing a user interface for manual operation. The current status includes: power on, power off, charging, discharging, and standby. Battery data includes: the maximum and minimum voltage of the battery module pack, and the specific topological position of the battery module within the battery cluster; the maximum and minimum voltage of individual battery cells, and their specific topological positions within the battery cluster; and the maximum and minimum temperature of the battery module, along with its location. The user interface for manual operation includes the following actions: power on, power off, standby, setting charge / discharge power, viewing the voltage and temperature of the battery cluster's battery modules, viewing the voltage and temperature of individual battery cells within the battery cluster, and viewing historical charge / discharge power curves.

[0085] The internal architecture of the software system in this invention is outlined in steps as follows:

[0086] Step 1: Implement a layered architecture for the software, dividing each layer into different modules according to their functions, defining the external API interfaces for each layer, and reducing the coupling between different layers.

[0087] Step 2: Define the battery data analysis and processing module. Use XML file configuration to define the battery attribute information in XML. This battery data analysis and processing module parses the XML data, imports the battery configuration information, and uses it as the basis for subsequent data analysis and processing.

[0088] Specifically, this includes defining the tag structure for each battery module in the XML file, and defining the tag name as...<pack n> …< / pack n> Where n represents the battery module serial number. <pack>The tag internally defines battery attribute tags, which include the following attributes:

[0089] 1. Battery module charging cutoff voltage <packfullvol>.

[0090] 2. Battery module discharge cutoff voltage <packlowvol>.

[0091] 3. Battery module fault voltage <packfaultvol>.

[0092] Each battery module <pack>The tag contains single-item attribute tags, such as the following:

[0093] 1. Number of individual battery cells <batnum>.

[0094] 2. Battery cell charging cutoff voltage <batfullvol>.

[0095] 3. Battery cell discharge cutoff voltage <batlowvol>.

[0096] 4. Battery cell fault voltage <batfaultvol>.

[0097] 5. Upper limit of battery cell temperature <battemphigh>.

[0098] 6. Lower limit of cell temperature <battemplow>.

[0099] During startup, the battery data analysis and processing module reads and parses the XML configuration file, storing battery attribute data in memory as key-value pairs. The module then collects information such as voltage, current, and temperature for each battery module and individual cell within the battery cluster through the interface provided by the BOS-HDL layer. Finally, the module compares the collected battery information with the key-value data stored in memory to determine the battery's fault status, as well as its fully charged and discharged states.

[0100] Step 3: Define the battery management strategy operation module. This involves defining various battery control sub-commands using XML configuration files, allowing for dynamic, programmable definition of the battery management strategy. The battery management strategy is broken down into sub-commands; different combinations of these sub-commands constitute a specific battery management strategy. The main sub-commands include: 1. Network card power on; 2. Adapter power on; 3. Energy storage converter power on; 4. Network card power off; 5. Adapter power off; 6. Energy storage converter power off; 7. Set current charging / discharging power; 8. Check if the battery cluster is fully charged; 9. Check if the battery cluster is fully discharged; 10. Check if there are faulty batteries in the battery cluster.

[0101] Step 4: The BOS-APP layer application calls the interfaces of the functional modules under it to realize the final business logic application.

[0102] The working process of this invention is described below using the example of issuing a charging command to the battery management system:

[0103] Human-Computer Interaction Layer: The operator clicks the charging button on the interface, enters the charging power value, such as 100kW, and clicks the OK button. This invokes the power setting command from the interface encapsulation layer.

[0104] Interface encapsulation layer: Power setting instructions in the interface encapsulation layer. These instructions invoke the power setting instructions in the logic processing layer.

[0105] Logic Processing Layer: When a power setting command enters the logic processing layer, it undergoes further logical processing and judgment. For example, based on the current battery cluster status, whether there are faulty batteries, and the current SOC state, it determines whether to allow 100kW charging power or to reduce the power. The final power setting command is then passed to the device access layer.

[0106] Device Access Layer: After the logic processing layer's judgment, the power setting command reaches the device access layer. At the device access layer, based on the current system configuration, a specified model of energy storage converter is selected, along with the hardware interface and communication protocol used by the energy storage converter. The command is then sent to the energy storage converter via the hardware interface layer's interface.

[0107] Hardware Interface Layer: The power setting command of the hardware interface layer will send the command to the specified hardware device, detect the device's response and confirmation, and return the setting result.

[0108] This application has the following advantages:

[0109] The software system provided in this application can run on different embedded operating systems, including but not limited to Linux, VxWorks, and various RTOS (ucos, freertos, etc.). It supports different types of batteries, including but not limited to lithium-ion and sodium-ion batteries. It supports the mixed use of different battery types and can effectively manage mixed battery systems. It supports inputting battery model data for each battery module in the system, supports expansion with different battery types, and supports the presence of different battery types in the system. The battery management strategy is designed as a logic programming approach, allowing for dynamic editing of the battery management strategy flow to meet different project requirements without requiring code modification.

[0110] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0111] This document uses specific examples to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the methods and core ideas of this application. Furthermore, those skilled in the art will recognize that, based on the ideas of this application, there will be changes in the specific implementation methods and application scope. Therefore, the content of this specification should not be construed as a limitation of this application.< / battemplow> < / battemphigh> < / batfaultvol> < / batlowvol> < / batfullvol> < / batnum> < / pack> < / packfaultvol> < / packlowvol> < / packfullvol> < / pack>

Claims

1. A battery management embedded software system, characterized in that, The battery management embedded software system comprises, from top to bottom, a human-computer interaction layer, an interface encapsulation layer, a logic processing layer, a device access layer and a hardware interface layer; The human-computer interaction layer is configured to receive operation instructions and display the current state of the battery cluster and battery data. The interface encapsulation layer is connected with the human-computer interaction layer; the interface encapsulation layer is configured to encapsulate the external interfaces set by the hardware interface layer, the device access layer and the logic processing layer, send the encapsulation results to the human-computer interaction layer, and receive the operation instructions. The logic processing layer is connected with the interface encapsulation layer; the logic processing layer is configured to call corresponding battery models according to the operation instructions, apply battery management strategies to the battery models, generate control instructions according to the battery management strategies, determine the current state of the battery cluster and battery data, and send the control instructions to the human-computer interaction layer through the interface encapsulation layer; the control instructions comprise obtaining data of a preset hardware interface and sending corresponding preset data to the preset hardware interface; the battery models are described by XML format description files; the parameters comprise battery charge / discharge cutoff voltage, battery temperature and maximum charge / discharge power corresponding relationship, and battery charge / discharge curve data. The device access layer is connected with the logic processing layer; the device access layer is configured to uniformly encapsulate communication protocols of battery management systems of different manufacturers, access corresponding device operation interfaces to obtain parameters of the preset hardware interface according to the control instructions, and generate calling instructions. The hardware interface layer is connected with the device access layer; the hardware interface layer is configured to perform secondary encapsulation on the preset hardware interface, and send corresponding preset data to the preset hardware interface according to the calling instructions.

2. The battery management embedded software system of claim 1, wherein, The preset hardware interface comprises RS485, CAN, SPI, IIC and Ethernet interfaces.

3. The battery management embedded software system of claim 1, wherein, The battery management strategies are programmable.

4. The battery management embedded software system of claim 1, wherein, The battery management strategies are described by XML format description files.

5. The battery management embedded software system of claim 1, wherein, The battery management strategies comprise boot-up procedures, shutdown procedures, charge / discharge procedures, battery maintenance procedures and standby procedures.

6. The battery management embedded software system of claim 1, wherein, The logic processing layer further compares the battery data with preset battery threshold values, and determines the current state of the battery cluster according to the comparison results; the current state comprises a fault state, a full state and an empty state.

7. The battery management embedded software system of claim 6, wherein, An XML configuration file is obtained; the XML configuration file is parsed to obtain battery attribute data, and the battery attribute data is stored in the memory in the form of key-value.

8. The battery management embedded software system of claim 1, wherein, In the charging process, when the collected voltage data of a battery module in the battery cluster exceeds the battery module charge cutoff voltage configuration value existing in the memory, the battery module is marked as being in a full state; In the discharging process, when the collected voltage data of a battery module in the battery cluster is lower than the battery module discharge cutoff voltage configuration value existing in the memory, the battery module is marked as being in an empty state. In the charging and discharging process, when the collected voltage data of the battery modules in the battery cluster is lower than the battery module failure voltage configuration value existing in the memory, the battery module is marked as being in a failure state; In the charging process, when the collected voltage data of each battery cell inside the battery module in the battery cluster exceeds the single battery charging cut-off voltage configuration value existing in the memory, the battery module is marked as being in a full state; In the discharging process, when the collected voltage data of each battery cell inside the battery module in the battery cluster is lower than the single battery discharging cut-off voltage configuration value existing in the memory, the battery module is marked as being in an empty state; In the charging and discharging process, when the collected voltage data of each battery cell inside the battery module in the battery cluster is lower than the single battery failure voltage configuration value existing in the memory, the battery module is marked as being in a failure state; In the charging process, when any battery module in the battery cluster is in a full state, the battery cluster is marked as being in a full state; In the discharging process, when any battery module in the battery cluster is in an empty state, the battery cluster is marked as being in an empty state; In the charging and discharging process, when any battery module in the battery cluster is in a failure state, the battery cluster is marked as being in a failure state.

Images